slinky2004 |
10-25-2005 11:28 PM |
Hard Drive errors on S3 wakeup
When i suspend to ram with "echo mem > /sys/power/state", it takes my laptop a long time to resume. i think it's caused by these errors, that i find recorded in dmesg after a sleep/wakeup:
Quote:
ACPI: PCI Interrupt 0000:02:04.2[C] -> Link [LNKG] -> GSI 9 (level, low) -> IRQ 9
eth0: Coming out of suspend...
PCI: Enabling device 0000:02:0b.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:02:0b.0[A] -> Link [LNKD] -> GSI 9 (level, low) -> IRQ 9
hda: lost interrupt
evevent-0299: *** Error: No installed handler for fixed event [00000002]
Restarting tasks... done
hda: dma_timer_expiry: dma status == 0x21
hda: DMA timeout error
hda: dma timeout error: status=0x50 { DriveReady SeekComplete }
ide: failed opcode was: unknown
hda: status error: status=0x50 { DriveReady SeekComplete }
ide: failed opcode was: unknown
hda: no DRQ after issuing MULTWRITE_EXT
hda: status error: status=0x50 { DriveReady SeekComplete }
ide: failed opcode was: unknown
hda: no DRQ after issuing MULTWRITE_EXT
hda: lost interrupt
hda: status error: status=0x50 { DriveReady SeekComplete }
ide: failed opcode was: unknown
hda: no DRQ after issuing MULTWRITE_EXT
hda: status error: status=0x50 { DriveReady SeekComplete }
ide: failed opcode was: unknown
hda: no DRQ after issuing MULTWRITE_EXT
ide0: reset: success
|
can anybody help me solve this problem? it seems like it might be an issue with my hard drive setup.
btw, i'm running slackware 10.2, kernel 2.6.13.4, and i have to use the "acpi_sleep=s3_bios" boot parameter in order to get s3 to resume at all.
|