Re: hwsusp defunct

From: Rafael J. Wysocki
Date: Tue Feb 06 2007 - 12:56:39 EST


On Tuesday, 6 February 2007 12:18, Jiri Slaby wrote:
> Rafael J. Wysocki napsal(a):
> > Hi,
> >
> > On Sunday, 4 February 2007 14:12, Jiri Slaby wrote:
> >> Hi.
> >>
> >> When I'm trying to suspend to mem one machine, it wakes immediatly back with
> >> nothing notable in dmesg:
> > [--snip--]
> >> Will PM_DEBUG or ACPI_DEBUG help somehow? Or later kernel?
> >
> > Later kernel might help, some important fixes have gone in since 2.6.19,
> > PCI quirks-related etc.
> >
> > Please try 2.6.20-rc7 and if that doesn't help, try the latest -mm.
>
> 2.6.20 from init 2 is no go either, -mm (-rc6-mm3) with minimal config [1]
> suspends, no key was able to resume it back, only power button, but monitor
> doesn't wake (actually I've this problem on another machine when X is not
> running) -- how to debug both of this? Do not suspend consoles? PM_TRACE (this
> won't help since it completely resumes, I guess)?

First, you can try s2ram if you haven't done it already (http://en.opensuse.org/s2ram).
It may help to get your video back after the resume.

If you have a COM port, it is also possible to use a serial console throughout the
suspend/resume cycle.

> This is blindly written dmesg after resume. See it whole at [2]:
> Suspending device 0.0
> ACPI Exception (exoparg2-0442): AE_AML_PACKAGE_LIMIT, Index (000000007) is beyon
> d end of object [20070126]
> ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.GTM_]
> (Node dfe64fcc), AE_AML_PACKAGE_LIMIT
> ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.CHN0._
> GTM] (Node dfe649f0), AE_AML_PACKAGE_LIMIT
> ...
> hda: selected mode 0x45
> ACPI Error (dsopcode-0481): Attempt to CreateField of length zero [20070126]
> ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.RATA]
> (Node dfe64ec8), AE_AML_OPERAND_VALUE
> ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.CHN0.D
> RV1._GTF] (Node dfe64964), AE_AML_OPERAND_VALUE
> do_drive_get_GTF: Run _GTF error: status = 0x3006

This looks like an ACPI-vs-IDE problem. You can try to use libata drivers instead
of the "old IDE" ones.

> $ ls -l /sys/block/hda/device
> lrwxrwxrwx 1 root root 0 Ãno 6 12:14 /sys/block/hda/device ->
> ../../devices/pci0000:00/0000:00:1f.1/ide0/0.0
> $ ls -l /sys/block/hda/device/driver
> lrwxrwxrwx 1 root root 0 Ãno 6 12:15 /sys/block/hda/device/driver ->
> ../../../../../bus/ide/drivers/ide-disk
> $ ls -l /sys/block/hda/device/driver/0.0
> lrwxrwxrwx 1 root root 0 Ãno 6 12:16 /sys/block/hda/device/driver/0.0 ->
> ../../../../devices/pci0000:00/0000:00:1f.1/ide0/0.0
> # lspci -vvvxxs 0000:00:1f.1
> 00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller
> (rev 02) (prog-if 8a [Master SecP PriP])
> Subsystem: ASUSTeK Computer Inc. P5P800-MX Mainboard
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
> Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
> Latency: 0
> Interrupt: pin A routed to IRQ 5
> Region 0: I/O ports at 01f0 [size=8]
> Region 1: I/O ports at 03f4 [size=1]
> Region 2: I/O ports at 0170 [size=8]
> Region 3: I/O ports at 0374 [size=1]
> Region 4: I/O ports at fc00 [size=16]
> Region 5: Memory at 30100000 (32-bit, non-prefetchable) [size=1K]
> 00: 86 80 db 24 07 00 80 02 02 8a 01 01 00 00 00 00
> 10: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00
> 20: 01 fc 00 00 00 00 10 30 00 00 00 00 43 10 a6 80
> 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00
>
> Do you want acpidump?

I'm not an ACPI expert, it won't tell me a lot, but perhaps you should add
linux-acpi to the Cc list. ;-)

> Should I test 2.6.20 with minimal config?

I think it's better to try the -mm with the minimal config.

Greetings,
Rafael


--
If you don't have the time to read,
you don't have the time or the tools to write.
- Stephen King
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/