Red Hat Bugzilla – Bug 135612
system hang, not responsive to ping or alt-syrq-*
Last modified: 2015-01-04 17:10:36 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.3) Gecko/20040803 Description of problem: System will lockup, or hang after some arbitrary time after boot. I attached a serial console and found the following messages coming from the kernel indefinitely during this hang: _timer_expiry: dma status == 0x64 hda: DMA interrupt recovery hda: lost interrupt hda: dma_timer_expiry: dma status == 0x64 hda: DMA interrupt recovery hda: lost interrupt hda: dma_timer_expiry: dma status == 0x64 hda: DMA interrupt recovery hda: lost interrupt hda: dma_timer_expiry: dma status == 0x64 hda: DMA interrupt recovery hda: lost interrupt hda: dma_timer_expiry: dma status == 0x64 hda: DMA interrupt recovery hda: lost interrupt Version-Release number of selected component (if applicable): kernel-2.6.8-1.610smp How reproducible: Always Steps to Reproduce: 1. install latest rawhide 2. boot 3. Actual Results: hangs after up for some time Expected Results: no hang Additional info: related to bugzilla #133526?
Adding Alan to the 'cc list for this one.
Also, this isn't a h/w problem since i've been running rhel2.1 for 2 plus years on this system...
What sort of IDE hardware?
Created attachment 105165 [details] dmesg listing
Talk to Bartlomiej. There have been a couple of reports like this and he's fixed at least one race in 2.6.9rc related to that kind of crash.
Just as a sanity check too please try both booting with acpi=off disabling USB legacy support
Those options didn't resolve this issue for me
is this still occuring with current kernels too ? (I guess this should be cloned as a RHEL4 bug now too)
I am seeing this on a FC4 box with the latest 2.6.16-1.2096 kernel. I also experienced the same problems with 2.6.16-1.2069. This machine is currently running 2.6.14-1.1656_FC4 which does not appear to suffer. The machine is my central storage server, I can't afford to take it off-line very often, but will assist where possible.
I'm happy to help with this in terms of testing, but I could really do with some assistance here.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you.
I haven't seen this in a long time, and I no longer have the hardware that seemed to be susceptible to this, is anyone actually seeing this error any more?
(this is a mass-close to kernel bugs in NEEDINFO state) As indicated previously there has been no update on the progress of this bug therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue still occurs for you and I will try to assist in its resolution. Thank you for taking the time to report the initial bug. If you believe that this bug was closed in error, please feel free to reopen this bug.