Bug 5673 - hda and ide0 errors on resume from acpi s3 using ich4-m and PIIX driver
Summary: hda and ide0 errors on resume from acpi s3 using ich4-m and PIIX driver
Status: REJECTED INSUFFICIENT_DATA
Alias: None
Product: IO/Storage
Classification: Unclassified
Component: IDE (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Bartlomiej Zolnierkiewicz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-28 18:54 UTC by slinky1776
Modified: 2006-04-22 10:20 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.14.3
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description slinky1776 2005-11-28 18:54:43 UTC
Most recent kernel where this bug did not occur:2.6.13.4
Distribution:slackware 10.2
Hardware Environment:
00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to
I/O Controller (rev 02)
00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor
to I/O Controller (rev 02)
00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor
to I/O Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated
Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics
Device (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
USB UHCI Controller #2 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI
Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 83)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge
(rev 03)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus
Controller (rev 03)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97
Modem Controller (rev 03)
02:04.0 CardBus bridge: Texas Instruments PCI7420 CardBus Controller
02:04.2 FireWire (IEEE 1394): Texas Instruments PCI7x20 1394a-2000 OHCI Two-Port
PHY/Link-Layer Controller
02:04.3 Mass storage controller: Texas Instruments PCI7420/PCI7620 Dual Socket
CardBus and Smart Card Cont. w/ 1394a-2000 OHCI Two-Port  PHY/Link-Layer Cont.
an02:08.0 Ethernet controller: Intel Corporation 82801DB PRO/100 VE (MOB)
Ethernet Controller (rev 83)
02:0b.0 Network controller: Intel Corporation PRO/Wireless 2200BG (rev 05)
Software Environment:
Problem Description:
after resume from acpi s3, dmesg shows these errors:
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

it causes the resume to take a very long time, and those lost interrupts can't
be good news can they? after discussing the issue on the acpi-devel mailing
list, I believe that this is an issue concerning the ide driver(PIIX), the s3
resume sequence, and/or ich4/ich4-m ide controllers. i have encountered other
people with ich4 controllers that have the same and similar issues.
Steps to reproduce:
on a machine with an ich4 ide controller:
*the acpi_sleep=s3_bios boot parameter may be required in order for s3 to work
at all(it is for me at least)
1. enter s3: echo mem > /sys/power/state
2. wake it up: hit a key
3. after resume(should take a while), check dmesg for the errors
Comment 1 slinky1776 2005-11-28 22:53:01 UTC
sry, typed the wrong kernel version, i meant 2.6.14.3.
Comment 2 Bartlomiej Zolnierkiewicz 2006-01-12 08:56:01 UTC
Please send output for 'lspci -vvv -xxx' command obtained:
- before suspend
- after resume
Comment 3 Bartlomiej Zolnierkiewicz 2006-01-19 03:14:39 UTC
Did any previous kernel work OK?
Comment 4 Adrian Bunk 2006-04-22 10:20:49 UTC
Please reopen this bug if:
- it is still present in kernel 2.6.16 and
- you can provide the requested information.

Note You need to log in before you can comment on or make changes to this bug.