| Summary: | [Turks PRO/Radeon HD 6570/7570/8550] CPU lockup after ring 0 stalled | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | guiscaranse |
| Component: | Drivers/Gallium/r600 | Assignee: | Default DRI bug account <dri-devel> |
| Status: | RESOLVED MOVED | QA Contact: | Default DRI bug account <dri-devel> |
| Severity: | critical | ||
| Priority: | high | CC: | pmenzel+bugs.freedesktop.org |
| Version: | 17.1 | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| See Also: |
https://bugs.freedesktop.org/show_bug.cgi?id=102909 https://bugs.freedesktop.org/show_bug.cgi?id=107545 https://bugs.freedesktop.org/show_bug.cgi?id=104307 |
||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
Error log about the crash
DSMEG (more detailed log) Dmesg after boot |
||
|
Description
guiscaranse
2017-07-06 23:03:35 UTC
It's turning the OS completely unsable, that is why I marked as urgent Created attachment 132488 [details]
DSMEG (more detailed log)
Here it is a more detailed log
Can you try to 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. (see also https://bugs.freedesktop.org/show_bug.cgi?id=101325) (In reply to Julien Isorce from comment #3) > Can you try to 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. (see also > https://bugs.freedesktop.org/show_bug.cgi?id=101325) I was able to reproduce the issue and record it using apitrace (https://mega.nz/#!8M0TDRaJ!Uvh0V8B10JwZqRxAuN2PTUwfoQUN4mteeb-ks2P2mio). Also read the otter issue and i think that probably are related, but no idea how to solve it. Thx for the apitrace. I could not reproduce the issue with radeonsi/capverde using apitrace replay darkest.bin.x86_64.trace, can you ?. Though I could see the VRAM increasing a lot at the end. Could you attach full output of dmesg just after boot ? At least to see the vram size. Try to run the app with R600_DEBUG=check_vm GALLIUM_DDEBUG="pipelined 5000" It should generate infos in ~/ddebug_dumps/ Created attachment 132618 [details] Dmesg after boot (In reply to Julien Isorce from comment #5) > Thx for the apitrace. I could not reproduce the issue with radeonsi/capverde > using apitrace replay darkest.bin.x86_64.trace, can you ?. Though I could > see the VRAM increasing a lot at the end. > Could you attach full output of dmesg just after boot ? At least to see the > vram size. > > Try to run the app with R600_DEBUG=check_vm GALLIUM_DDEBUG="pipelined 5000" > It should generate infos in ~/ddebug_dumps/ Added the dmesg output, will try running the app with the env variables, but I am sure that I can reproduce the issue with apitrace replay Same issue with Radeon HD 5970 for mesa 18.2.2 -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/606. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.