| Summary: | [NVac] nouveau display locks up - /usr/bin/Xorg (xorg_backtrace+0x2f) [0x4a120f] | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | James Laska <jlaska> | ||||||
| Component: | xorg-x11-drv-nouveau | Assignee: | Ben Skeggs <bskeggs> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 15 | CC: | airlied, ajax, brendan.jones.it, bskeggs, jturner, mcepl, vengmd | ||||||
| Target Milestone: | --- | Keywords: | Reopened, Triaged | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | kernel-2.6.38-0.rc8.git2.1.fc15 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2011-03-27 22:33:19 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
|
Description
James Laska
2011-02-22 20:51:12 UTC
Also experienced this hang with: xorg-x11-server-Xorg-1.9.99.1-6.20101201.fc15.x86_64 xorg-x11-drv-nouveau-0.0.16-20.20110224gitbc5dec2.fc15.x86_64 kernel-2.6.38-0.rc6.git6.1.fc15.x86_64 I've got debuginfo packages installed for each of the files in the backtrace, I'm not sure why not all of the addresses have symbol information. Any thoughts as to what might be causing this? I seem to hit this fairly regularly (5+ times a day) Could we get output of dmesg command after this happens, please? (In reply to comment #3) > Could we get output of dmesg command after this happens, please? I didn't post it originally, since with drm.debug enabled, the dmesg output is completely filled up with: [ 4726.845178] [drm] nouveau 0000:02:00.0: nouveau_sgdma_clear:62 - [ 4726.845916] [drm] nouveau 0000:02:00.0: nouveau_sgdma_populate:28 - num_pages = 1 [ 4726.854098] [drm] nouveau 0000:02:00.0: nouveau_sgdma_destroy:83 - [ 4726.854109] [drm] nouveau 0000:02:00.0: nouveau_sgdma_clear:62 - [ 4726.876367] [drm] nouveau 0000:02:00.0: nouveau_sgdma_populate:28 - num_pages = 1 [ 4726.876531] [drm] nouveau 0000:02:00.0: nouveau_sgdma_destroy:83 - [ 4726.876537] [drm] nouveau 0000:02:00.0: nouveau_sgdma_clear:62 - [ 4726.877553] [drm] nouveau 0000:02:00.0: nouveau_sgdma_populate:28 - num_pages = 1 [ 4726.885200] [drm] nouveau 0000:02:00.0: nouveau_sgdma_destroy:83 - I understand from Ben that this is "just system memory being bound/unbound from the GPU". Can you update to http://koji.fedoraproject.org/koji/buildinfo?buildID=232757 (kernel-2.6.38-0.rc8.git0.2.fc15) and retry? I'm not sure it'll help, but one of the bugs fixed since the kernel you used resulted in unpredictable behaviour on some systems, so it's worth a try :) (In reply to comment #5) > Can you update to http://koji.fedoraproject.org/koji/buildinfo?buildID=232757 > (kernel-2.6.38-0.rc8.git0.2.fc15) and retry? > > I'm not sure it'll help, but one of the bugs fixed since the kernel you used > resulted in unpredictable behaviour on some systems, so it's worth a try :) Great thanks, I just grabbed a slightly newer kernel (kernel-2.6.38-0.rc8.git2.1.fc15), which includes the fix you mentioned. I'll post back after a few days of usage wit h this kernel. (In reply to comment #6) > (In reply to comment #5) > > Can you update to http://koji.fedoraproject.org/koji/buildinfo?buildID=232757 > > (kernel-2.6.38-0.rc8.git0.2.fc15) and retry? > > > > I'm not sure it'll help, but one of the bugs fixed since the kernel you used > > resulted in unpredictable behaviour on some systems, so it's worth a try :) > I'll post back after a few days of usage wit h this kernel. I'm closing this bug. I've been running with kernel-2.6.38-0.rc8.git2.1.fc15 and kernel-2.6.38-1.fc15 for a few days and have *not* seen this problem. I'll reopen if the problem resurfaces Created attachment 487951 [details]
Xorg.0.log.old
Hi
I am still experiencing this bug under the suggestd build from koji and the latest kernel update 2.6.38.1-6
xorg-x11-drv-nouveau.x86_64 1:0.0.16-24.20110324git8378443.fc15 @updates-testing
Attached Xorg.0.log.old
(In reply to comment #8) > Created attachment 487951 [details] > Xorg.0.log.old > > Hi > > I am still experiencing this bug under the suggestd build from koji and the > latest kernel update 2.6.38.1-6 This bug is not relevant to your chipset. 679319 is the one you want to track. > > xorg-x11-drv-nouveau.x86_64 1:0.0.16-24.20110324git8378443.fc15 > @updates-testing > > Attached Xorg.0.log.old |