Red Hat Bugzilla – Bug 471937
"disabling IRQ #16" -> hang
Last modified: 2009-01-27 12:55:59 EST
When running kernel-188.8.131.52-109.fc10.x86_64 I get random system-wide hangs and need to hard-reboot my laptop. It appears that just before the hang I'm getting "disabling IRQ #16" from syslog.
Booting into 184.108.40.206-68.fc10.x86_64 has no issues that I can see (well, except for apparently not having a working bluetooth on my laptop ...).
This sounds something like what Luke saw this morning
Yep, I hit that same issue yesterday with 220.127.116.11-109.fc10.x86_64.
I'm having the same issue as well.
Created attachment 323962 [details]
I had a lockup on kernel 18.104.22.168-68.fc10.x86_64 as well. I was flipping desktops in compiz and the laptop hard locked. Upon reboot, I noticed the following in /var/log/Xorg.0.log.old:
exaCopyDirty: Pending damage region empty!
[mi] EQ overflowing. The server is probably stuck in an infinite loop.
(repeated lots of times).
(In reply to comment #5)
> I had a lockup on kernel 22.214.171.124-68.fc10.x86_64 as well. I was flipping
> desktops in compiz and the laptop hard locked. Upon reboot, I noticed the
> following in /var/log/Xorg.0.log.old:
> exaCopyDirty: Pending damage region empty!
> [mi] EQ overflowing. The server is probably stuck in an infinite loop.
If I understand correctly that's a different bug - you have no "disabling IRQ" message, and a much older kernel. Perhaps it matches one of the bugs in the 'eq-overflow' tracker: https://bugzilla.redhat.com/showdependencytree.cgi?id=465884&hide_resolved=1
FWIW I can reproduce the "disabling IRQ #16" behavior here as well, on kernel -113 (intel cantiga graphics)
See also bug 471162, which describes the same symptoms but on i945GME. Appears to be fixed for those users now.
(In reply to comment #7)
> See also bug 471162, which describes the same symptoms but on i945GME. Appears
> to be fixed for those users now.
FWIW, not all of those that commented on bug 471162 have a 945GME -- tree of them seem to have a intel 965 chipset (to be precise: a GM965 according to two of the three reports)
I have the same problem recently with latest f10 kernels (I'm using intel GM 965 graphics card).
It happened while I didn't use any 3D applications or desktop effects.
I'm pretty sure I encountered the same issue again today. Both times happened while I was spinning a livecd using the livecd-creator, under fairly heavy disk i/o. This time, I was able to switch to a console and see some ext3 errors (picture attached). I'm not 100% sure that this is the same issue, but it did produce the same symptoms as before.
Created attachment 324073 [details]
Picture of various ext3 errors
You can work around the IRQ disable problem by adding "noirqdebug" to the kernel boot options.
I had similar ext3 errors to Luke when I ran into this issue.
This is still happening with kernel-126.96.36.199-113.fc10.x86_64.
(In reply to comment #14)
> This is still happening with kernel-188.8.131.52-113.fc10.x86_64.
Did you try with 184.108.40.206-116.fc10.x86_64 or newer? That is out for two days now and solved the problem for a few users in Bug 471162
I'm running 220.127.116.11-117.fc10.x86_64 now. To get some disk churn I cleaned and rebuilt all of my projects in Eclipse. I have a lot so this wasn't a small task. I also started up Firefox and did some stuff in an terminal at the same time. I haven't seen a hang yet.
Yesterday I had many hangs. But since I've updated my kernel to 18.104.22.168-117.fc10.x86_64 I had no crashes. Seems to be fixed now. :)
I've been running 22.214.171.124-117.fc10.x86_64 all day under high i/o load without any problems.
*** This bug has been marked as a duplicate of bug 471162 ***