Red Hat Bugzilla – Bug 712533
[CYPRESS] System locks up randomly when opening/closing/resizing windows after recent kernel update to kernel-188.8.131.52-30.fc15.x86_64
Last modified: 2012-08-06 16:01:18 EDT
Description of problem:
I'm having these system lock ups since the kernel update if my memory doesn't betray me. It doesn't always happen, just randomly once in a while while doing things with windows (nothing happened yet when just dragging them around). Audio playback stops, I can't move the mouse pointer and pressing the reset button once doesn't work, I have to hold it for a while so that the system forcibly powers off and back on again.
Version-Release number of selected component (if applicable):
(Fully updated F15 system as of the time of this writing)
Steps to Reproduce:
1. Open/close/resize windows repeatedly.
System locks up eventually.
No lock up.
My System is a Core i5-2500 on an Intel DH67CL (BIOS version 5/23/2011), 8GB of RAM with a Radeon 5870 (/sys/class/drm/card0/device/power_profile is set to auto, hovers at about 50°C)
Ugh, I was using kernel-184.108.40.206-27.fc15.x86_64 when writing the bug report, where I previously had no lock ups. After submitting the bug and clicking on "Bug 712533" at the top, the system froze again... so now I'm not sure if I categorized the bug report right. At first I thought this was related to the radeon-updates shipped with the newest kernel, but maybe it's something else. Sorry if this is noise :(
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 add drm.debug=0x04 to the kernel command line, restart computer, and attach
* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)
to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Fedora Bugzappers volunteer triage team
Created attachment 504277 [details]
Created attachment 504278 [details]
Created attachment 504279 [details]
Comment on attachment 504279 [details]
(side note: Xorg seems to configure my USB Audio DAC as a keyboard :D)
Created attachment 504281 [details]
The only xorg.conf file I have, in xorg.conf.d
Comment on attachment 504278 [details]
fixed wrong mime type
Happened again with kernel-220.127.116.11-32.fc15.x86_64, this time while switching virtual desktops in Gnome 3.
What can I do to help getting this fixed faster?
Lockup are not easy to fix, just update regulary, there have been some change lately that might help in this area.
There is no debug instruction that one can follow.
Still happens with xorg-x11-drv-ati-6.14.1-2.20110525gitfe5c42f51.fc15.x86_64.
Moving back to xorg-x11-drv-ati, I have no idea why you've moved it to the completely unrelated component 0xFFFF.
Fedora Bugzappers volunteer triage team
Me? Didn't move anything, at least not knowingly.
Still happens with kernel-18.104.22.168-35.fc15.x86_64.
And it still happens with mesa-*-7.11-0.16.20110709.0.fc15.x86_64 from updates-testing.
I've recently installed Fedora 15 on my Mac Pro with ATI 5870 and it appears I'm hitting the same bug. It's a real show stopper as otherwise everything is great.
madigens: Are you saying that this *didn't* happen for you with a certain kernel and driver version? If so which versions?
FYI I'm using:
I'm a bit concerned with the log files, there seems to be nothing useful related to the lock-up. Mine show pretty much the same stuff relating to madigens entries. Happy to attach mine as well if it might help....
@Lester Wade: Yes, 22.214.171.124-27.fc15.x86_64 worked great and still does, because that's what I'm still running :) Would love to run the newest one, but this bug really is a show-stopper. only experienced 1 or maybe 2 lockups with this one. 38.7 and upwards all lock up randomly. Updating xorg-x11-drv-ati or mesa didn't help. So either it's a bug in the radeon patchset introduced in .7 or or the patchset is fine and exposes a bug in some other component.
By the way, I got a Netbook sitting here. Is there a way to redirect the logging from this PC to the Netbook via USB or something? Maybe something turns up just before the hang...
Still getting hangs in kernel-2.6.40-4.fc15.x86_64...
Still happens in kernel-126.96.36.199-0.fc15.x86_64.
Still happens with kernel-188.8.131.52-5.fc15.x86_64.
Still happens with kernel-184.108.40.206-0.fc15.x86_64.
Still happens with xorg-x11-drv-ati-6.14.2-1.20110921gitd78860ba5.fc15 and setting the power profile to low.
Apparently it's enough to load a webpage in Firefox 7.0.1 to hang the system.
I would like to also add that this still happens, mirroring the information madigens has given. I admire your persistence but I'm not sure anyone is paying attention to this one :(
Nobody paying attention would mean I won't be able to use F16 and others which I refuse to believe. DAMMIT. Surely we can't be the only ones with these problems? I guess I'll go test Ubuntu 11.10 when it comes out this week. Maybe I'll have more luck there? And if not, Catalyst should be working with Unity...
Or I would have to rip out the changes after .38.6 somehow... could be a chance to learn about the kernel, git and maybe bisect, but I'd like to have my priorities elsewhere.
I've been using Ubuntu 11.10 (modified kernel 3.0.4 afaik) for a few days and had no hangs as of yet despite browsing the web and doing things!
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here: