Comment # 3
on bug 101325
from Julien Isorce
This (In reply to Luke from comment #0) > > Then the log repeats a few hundred times the non-utf-8 character "\00" > before it cuts off. > Hello, just some naive comments: I also get some "^@" character after reboot sometimes, this happen because the kernel is not functional enough to properly write all messages on disk. One solution is to read these messages just before it freezes (does it freeze btw ?). For example ssh from another machine and type: "dmesg -w" before to start the test. This will read from the ring buffer directly. Though the real problem here is "radeon 0000:07:00.0: ring 4 stalled for more than 10024msec" so it is not really worth to get more messages in this case. Do you require to hard reboot after these gpu reset failures ? Alternatively you can try radeon.hard_reset=1 as a kernel param to do a pci reset instead of a soft reset. Also maybe you could generate an apitrace (apt-get install apitrace, apitrace trace /path/to/application ). Then if you reproduce the issue with apitrace replay application.trace you can attach it to this bug. About the amdgpu issue maybe you could try to build this kernel https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-4.9 (set CONFIG_DRM_AMDGPU_SI=y in the .config) which contains some up to date fixes for amdgpu (and radeon).
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
