Bug 489575
| Summary: | opengl screensaver hangs/crashes system with xorg-x11-drv-ati-6.10.0-2.fc10.i386 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Eddie Lania <eddie> | ||||||||
| Component: | xorg-x11-drv-ati | Assignee: | Dave Airlie <airlied> | ||||||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | low | Docs Contact: | |||||||||
| Priority: | low | ||||||||||
| Version: | 10 | CC: | apodtele, fdc, mcepl, xgl-maint | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | i686 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2009-05-14 08:52:30 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
Eddie Lania
2009-03-10 18:19:33 UTC
To be precise, the crash happens when starting: gnome-screensaver-preferences. After the crash when I restart, I cannot find anything strange in the /var/log/messages or /var/log/Xorg.0.log.old. I would like to debug this so that I can report some debug log here, but I don't know how to do that. Using gconf-editor I edited the settings for gnome-screensaver. I was using "blocktube" as the preferred screensaver and changed that. Now, when I start "gnome-screensaver-prefences" the system does not lock-up anymore. But I do however see the following message in the terminal from where I start gnome-screensaver-preferences: gnome-screensaver-preferences ** (gnome-screensaver-preferences:3698): DEBUG: Found best visual for GL: 0x21 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) 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. Could you please also try to run without any /etc/X11/xorg.conf (if you have one) whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please. We will review this issue again once you've had a chance to attach this information. Thanks in advance. Created attachment 334834 [details]
Xorg.0.log.old from after a crash
I have removed xorg.conf and tested again per as requested.
The same error/crash still occurs.
The attachment is the xorg.0.log.old from afther the crash.
Eddie, Could you also add "dmesg" output as uncompressed text/plain attachment to the bug ? If you are not yet using this, could you please try adding the nomodeset kernel parameter and report if it fixes the problem ? --- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Created attachment 334960 [details]
dmesg with nomodeset kernel parameter in grub
Hereby my dmesg after adding parameter "nomodeset" to kernel.
It solves the problem.
It also enables the "rage theatre" chip.
I will also send the xorg.0.log.
Must I make a new initrd? I recently changed back from the fglrx driver which blacklists radeon. After this switch I have not created a new initrd image.
Do you understand what I mean?
regards.
Eddie.
Created attachment 334961 [details]
xorg.0.log from after adding nomodeset kernel parameter.
xorg.0.log from after setting "nomodeset" kernel parameter.
Thanks for providing the needed data. No signs of fglrx in your logs, good. NB: KMS (modesetting) + AGP do not easily match... Switching to assigned, severity set to low since there is a workaround. --- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers I am on F11 now. No problems here with the screen-saver. Heh. F12 reliably locks up. |