Bug 1215329
| Summary: | repeatable freeze with nouveau | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Matthew Miller <mattdm> |
| Component: | libdrm | Assignee: | Adam Jackson <ajax> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 22 | CC: | airlied, ajax, awilliam, bskeggs, irlapati, omarth, rclark |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | libdrm-2.4.61-3.fc22 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-05-10 23:38:33 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Attachments: | |||
|
Description
Matthew Miller
2015-04-25 13:43:32 UTC
This is a Thinkpad W530, and the boot log says Chipset: GK107 (NVE7) I should also add that this is a regression -- no problem in F21. Created attachment 1018842 [details]
system log from crash
Recreated again and got a possibly more helpful log, including some kind of numeric dump.
Also of note: running under Gnome shell. I can reproduce this to at least some extent on my 9600 GT (10DE:0622). The first time I tried, on a regular boot, it happened right away, and stayed frozen for some time, and I rebooted remotely via ssh. Then I booted with 'drm.debug=14', and at first I couldn't reproduce it - but after several tries, I did hit a *temporary* freeze. After some seconds, though - 15-30 - the system started responding again. I'll attach logs from both boots. Created attachment 1019408 [details]
drm.debug=14 log of a reproduction which led to a temporary (15-30 second) freeze
Created attachment 1019409 [details]
trimmed log of first attempt to reproduce (without drm.debug=14)
Note, it would probably be a good idea to report this to upstream (bugs.freedesktop.org), as more devs will see it there. Thanks Adam! https://bugs.freedesktop.org/show_bug.cgi?id=90201 This appears to be related to a regression in libdrm. See https://bugs.freedesktop.org/show_bug.cgi?id=89842 http://cgit.freedesktop.org/mesa/drm/commit/?id=812e8fe6ce46d733c30207ee26c788c61f546294 is intended to fix this, I'll backport it to Rawhide and F22 (seems like a good idea to get this fixed). (In reply to Adam Williamson from comment #11) > http://cgit.freedesktop.org/mesa/drm/commit/ > ?id=812e8fe6ce46d733c30207ee26c788c61f546294 is intended to fix this, I'll > backport it to Rawhide and F22 (seems like a good idea to get this fixed). I plan on trying to get a libdrm 2.4.61 released today, and into Fedora. oh cool, in that case I'll skip the backport :) there's 6 days till F22 freeze so it should be fine (and we can propose a freeze exception if needed). I did test the backport as a scratch build and it seems to fix the problem, I couldn't reproduce it with the geeqie reproducer. libdrm-2.4.61-3.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/libdrm-2.4.61-3.fc22 libdrm-2.4.61-3.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. The problems still persist. I'm running in to this same problem with Fedora 22 even though I have updated libdrm to version libdrm-2.4.61-3.fc22. |