Bug 538238
| Summary: | Configuring display results in logout | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | A. Mani <a.mani.cms> | ||||||||||||||
| Component: | xorg-x11-drv-nouveau | Assignee: | Ben Skeggs <bskeggs> | ||||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||||
| Priority: | low | ||||||||||||||||
| Version: | 12 | CC: | airlied, ajax, awilliam, bskeggs, fedora, kevin, lorenzo, ltinkl, mcepl, rdieter, smparrish, than | ||||||||||||||
| Target Milestone: | --- | Keywords: | Triaged | ||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | All | ||||||||||||||||
| OS: | Linux | ||||||||||||||||
| Whiteboard: | card_NV4C | ||||||||||||||||
| Fixed In Version: | 0.0.15-18.20091105gite1c2efd.fc12 | Doc Type: | Bug Fix | ||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2010-01-12 23:39:58 UTC | Type: | --- | ||||||||||||||
| 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
A. Mani
2009-11-18 00:21:11 UTC
It's likely a display driver bug, where the xrandr probe crashes the X server. What video hardware and driver are you using? 00:0d.0 VGA compatible controller: nVidia Corporation GeForce 6100 nForce 405 (rev a2) (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device d000 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 21 Region 0: Memory at f8000000 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at e0000000 (64-bit, prefetchable) [size=256M] Region 3: Memory at f9000000 (64-bit, non-prefetchable) [size=16M] [virtual] Expansion ROM at 80000000 [disabled] [size=128K] Capabilities: [48] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Kernel driver in use: nouveau Kernel modules: nouveau, nvidiafb _______________________________ The system was updated from rawhide to F12 (stable) (but that should not matter most probably). Looks like nouveau is the likely suspect then, re-assigning. Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf, if available), output of the dmesg command, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. We will review this issue again once you've had a chance to attach this information. Thanks in advance. Created attachment 372367 [details]
Xorg log
xorg log
Created attachment 372368 [details]
xorg.conf
Created attachment 372369 [details]
xorg log with NO xorg.conf
older Xorg log file with no xorg.conf file
Created attachment 372371 [details]
dmesg
Please don't compress attachments that are plain text and reasonably short, it makes them far less convenient to work with. Can you please reproduce the issue and then attach /var/log/Xorg.0.log.old , which should be from the crashed session and hence contain the crash information? Thanks. Also, please do not set the priority field when reporting bugs. Per policy, it is reserved for the maintainers to use however they find most useful. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Created attachment 373900 [details]
xorg log with crash
xorg log with crash
One thing I notice, why are you using ShadowFB? Can you try removing that option and seeing how things work without it? xorg-x11-drv-nouveau-0.0.15-18.20091105gite1c2efd.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/xorg-x11-drv-nouveau-0.0.15-18.20091105gite1c2efd.fc12 Problem is solved by commenting out ShadowFB line can you also test _with_ the ShadowFB line, and the updated package from comment #13? Thanks. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers xorg-x11-drv-nouveau-0.0.15-18.20091105gite1c2efd.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update xorg-x11-drv-nouveau'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2009-12271 With updated package and updates-testing enabled, and ShadowFB line, clicking on system-settings --> Display is OK, but changing resolution results in login screen. I will attach the log Created attachment 374333 [details]
crash log with latest nouveau and shadowfb on
can you also provide this feedback to the Bodhi page? http://admin.fedoraproject.org/updates/F12/FEDORA-2009-12271 . thanks! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers xorg-x11-drv-nouveau-0.0.15-18.20091105gite1c2efd.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. |