Crash while playing mindustry
Note, I'm trying my best to follow https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs
A clear subject describing the issue.
After playing for a good while, the whole graphical interface will stop responding. It blinks very fast, and although the mouse is clear, nothing displays, it's a black screen with blinks of others windows mixed in
Steps to reproduce the issue.
Play mindustry (mindustry-bin 1:6.0_124.1), latest release, and after a good while (one hour/two), it will happen.
How often does the steps listed above trigger the issue? For example: always, 1 out 3 times.
Everytime I play the game, haven't seen it happen before or elsewhere
Which platforms and features are affected (if you can).
x64 intel chipset, using Dell XPS 13 (9310)
The following information about your system:
- -- system architecture: ("uname -m")
x86_64
- -- kernel version: ("uname -r"). Again, please consider using latest drm-tip from http://cgit.freedesktop.org/drm-tip
5.10.10-arch1-1
- -- Linux distribution
Arch linux, updated 2020-02-11
- -- Machine or mother board model (use dmidecode if needed)
Not sure if this part is what you are looking for but:
Base Board Information
Manufacturer: Dell Inc.
Product Name: 0GG9PT
Version: A00
-- Display connector: (such as HDMI, DP, eDP, ...)
Using USB-C with Dell P2720DC
- A full dmesg with debug information and/or a GPU crash dump:
- To obtain a dmesg with debug information, add
drm.debug=0x1e log_buf_len=1M
to your kernel command line, then reboot and reproduce the issue again. Make sure to attach the full dmesg all the way from boot.
Will try to reproduce again with these options
- In the case of a GPU hang, dmesg will contain a "GPU crash dump saved to /sys/class/drm/card0/error" message. The contents of that file are crucial to debugging the issue. Note that the contents of that file are generated by the kernel when it is read, so it will appear to have zero bytes. Reading the file contents with cat will produce the expected result. For example, use
See attached file crash.dump.bz2
I will report back once I am able to reproduce this while using the two kernel options suggested