Bug 161180
Summary: | (POWER MANAGEMENT?) Kernel hangs after flood of Atapi errors | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Arthur Pemberton <pembo13> |
Component: | kernel | Assignee: | Alan Cox <alan> |
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | davej, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-08-04 05:47:33 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: |
Description
Arthur Pemberton
2005-06-21 06:09:16 UTC
I installed the latest kernel at 09:33 today: Jul 10 09:33:04 Installed: kernel.i686 2.6.12-1.1390_FC4 By 16:00 the kernel had crashed and burned again: Jul 10 16:00:24 Juilet kernel: ide: failed opcode was: unknown Jul 10 16:00:24 Juilet kernel: ATAPI device hdc: Jul 10 16:00:24 Juilet kernel: Error: Illegal request -- (Sense key=0x05) Jul 10 16:00:24 Juilet kernel: Command sequence error -- (asc=0x2c, ascq=0x00) Jul 10 16:00:24 Juilet kernel: The failed "Prevent/Allow Medium Removal" packet command was: Jul 10 16:00:24 Juilet kernel: "1e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 " Jul 10 16:00:24 Juilet kernel: hdc: packet command error: status=0x51 { DriveReady SeekComplete Error } Jul 10 16:00:24 Juilet kernel: hdc: packet command error: error=0x50 { LastFailedSense=0x05 } Most of that time was low usage time as I was out for morning, and sleeping in the afternoon. Niether did I have anything to do with the cdrom during that time. Is the machine going into power saving state when left idle like this ? Yes it does in fact. However, this is also true for kernel 2.6.12-1.1387_FC4 which I have regressed to. And what ever power saving settings are the stock settings, as I have not reconfigured these settings. What ever the problem is, it is taking my machine down with all FC4 kernels. This did not happen in FC3. Furthermore, fsck does not launch on reboot. I do not think this a power management issue. My machine froze literally within seconds of runnign dmesg. Only the following relevant log messages showed up. Jul 14 23:55:43 Juilet kernel: hdc: irq timeout: status=0xd0 { Busy } Jul 14 23:55:43 Juilet kernel: ide: failed opcode was: unknown Jul 14 23:55:43 Juilet kernel: hdc: DMA disabled Jul 14 23:56:13 Juilet kernel: hdc: ATAPI reset timed-out, status=0xd0 Jul 14 23:56:13 Juilet kernel: hdd: DMA disabled Jul 14 23:56:43 Juilet kernel: ide1: reset timed-out, status=0xd0 Jul 14 23:56:48 Juilet kernel: hdc: status timeout: status=0xd0 { Busy } Jul 14 23:56:48 Juilet kernel: ide: failed opcode was: unknown Jul 14 23:56:48 Juilet kernel: hdc: drive not ready for command Jul 14 23:57:18 Juilet kernel: hdc: ATAPI reset timed-out, status=0xd0 Jul 14 23:57:48 Juilet kernel: ide1: reset timed-out, status=0xd0 Then the machine froze. I had to had reboot. Again. And fsck did not run on reboot, again. Also my CDRW (hdd) does not respond to its eject button while FC4 is on. [This comment has been added as a mass update for all FC4 kernel bugs. If you have migrated this bug from an FC3 bug today, ignore this comment.] Please retest your problem with todays 2.6.12-1.1398_FC4 update. If your problem involved being unable to boot, or some hardware not being detected correctly, please make sure your /etc/modprobe.conf is correct *BEFORE* installing any kernel updates. If in doubt, you can recreate this file using.. mv /etc/sysconfig/hwconf /etc/sysconfig/hwconf.bak mv /etc/modprobe.conf /etc/modprobe.conf.bak kudzu Thank you. Gentlemen, I am running kernel.i686 2.6.12-1.1398_FC4 and proud. As promised, this seemed to have solved my issue. I am nolonger crashing when the machine is idle, and my cdrw can open, my final test would be to burn a cd. Thanks to all for the fix. |