Failed resuming IDE from S3 on Abit NF7 (nForce2)

Failed resuming IDE from S3 on Abit NF7 (nForce2)

[Andreas Saur]

Topic: Failed resuming IDE from S3 on Abit NF7 (nForce2)

Hello all,
as already reported on bugzilla 
(http://bugzilla.kernel.org/show_bug.cgi?id=6326) and on this mailing 
list (http://marc.theaimsgroup.com/?l=linux-acpi&m=114461011901806&w=2), 
I've finally made it to get some more or less usefull logs about this 
bug. After a accidentally building a kernel with an initrd(*), I was 
able to resume from S3, but only until the system didn't perform a disk 
access on IDE. But that was enough to make a dmesg with an interesting 
entry:

"pnp: Failed to activate device 00:09.", where 00:09 is IDE!

With the first access to IDE the system was instantly frozen.

The only workaround I've found was here:
    http://lkml.org/lkml/2006/2/21/280
I've applied the mentioned kernel-patch:
    
http://www.xenotime.net/linux/SATA/2.6.16-rc3/libata-rollup-2616-rc3.patch
, but it didn't work for me. In the mail was also said, that there is a 
trivial "4-hooks" patch, that also has to be applied, but reading all 
the mails I couldn't find this patch.

Doest anybody know something about libata concerning ACPI problems? Btw. 
I've got an "sata_nv" mnodule loaded in the single-user-mode, but my 
sata is switched off in BIOS.

Help appreciated! Thanks.

----dmesg---Linux version 2.6.17-rc1-mm2a (root@vulcan) (gcc version 
4.0.3 20060304 ------
PM: Preparing system for mem sleep
Stopping tasks: =========|
[ACPI Debug]  String: [0x15] "==== SST Working ===="
Suspending device 1.0
Suspending device ide1
Suspending device eisa.0
Suspending device serio1
Suspending device serio0
Suspending device i8042
Suspending device serial8250
Suspending device pnp1
Suspending device pcspkr
Suspending device 00:09
Suspending device 00:08
Suspending device 00:07
Suspending device 00:06
Suspending device 00:05
Suspending device 00:04
Suspending device 00:03
Suspending device 00:02
Suspending device 00:01
Suspending device 00:00
Suspending device pnp0
Suspending device 0000:02:00.1
Suspending device 0000:02:00.0
Suspending device 0000:00:1e.0
Suspending device 0000:00:09.0
Suspending device 0000:00:08.0
Suspending device 0000:00:04.0
Suspending device 0000:00:01.1
Suspending device 0000:00:01.0
Suspending device 0000:00:00.5
Suspending device 0000:00:00.4
Suspending device 0000:00:00.3
Suspending device 0000:00:00.2
Suspending device 0000:00:00.1
Suspending device 0000:00:00.0
Suspending device pci0000:00
Suspending device platform
PM: Entering mem sleep
 hwsleep-0285 [11] enter_sleep_state     : Entering sleep state [S3]
Back to C!
PM: Finishing wakeup.
ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [LMAC] -> GSI 11 (level,
low) -> IRQ 11
PCI: Setting latency timer of device 0000:00:04.0 to 64
PCI: Setting latency timer of device 0000:00:08.0 to 64
pnp: Failed to activate device 00:09.
Restarting tasks... done
[ACPI Debug]  String: [0x15] "==== SST Working ===="
ACPI Error (evevent-0314): No installed handler for fixed event
[00000002] [20060310]
[ACPI Debug]  String: [0x15] "==== SST Working ===="

(*) don't know if initrd is the reason, but I've tried so much, that I 
don't correctly remember anymore.

RE: Failed resuming IDE from S3 on Abit NF7 (nForce2)

[Yu, Luming]

I'm wondering if http://bugzilla.kernel.org/show_bug.cgi?id=5604  is related
to your problem. But it would be worthy to try.
http://bugzilla.kernel.org/show_bug.cgi?id=5604#c19

--Luming

>-----Original Message-----
>From: linux-acpi-owner@vger.kernel.org 
>[mailto:linux-acpi-owner@vger.kernel.org] On Behalf Of Andreas Saur
>Sent: 2006年4月13日 13:28
>To: linux-acpi@vger.kernel.org
>Subject: Failed resuming IDE from S3 on Abit NF7 (nForce2)
>
>Topic: Failed resuming IDE from S3 on Abit NF7 (nForce2)
>
>Hello all,
>as already reported on bugzilla 
>(http://bugzilla.kernel.org/show_bug.cgi?id=6326) and on this mailing 
>list 
>(http://marc.theaimsgroup.com/?l=linux-acpi&m=114461011901806&w=2), 
>I've finally made it to get some more or less usefull logs about this 
>bug. After a accidentally building a kernel with an initrd(*), I was 
>able to resume from S3, but only until the system didn't 
>perform a disk 
>access on IDE. But that was enough to make a dmesg with an interesting 
>entry:
>
>"pnp: Failed to activate device 00:09.", where 00:09 is IDE!
>
>With the first access to IDE the system was instantly frozen.
>
>The only workaround I've found was here:
>    http://lkml.org/lkml/2006/2/21/280
>I've applied the mentioned kernel-patch:
>    
>http://www.xenotime.net/linux/SATA/2.6.16-rc3/libata-rollup-261
>6-rc3.patch
>, but it didn't work for me. In the mail was also said, that 
>there is a 
>trivial "4-hooks" patch, that also has to be applied, but reading all 
>the mails I couldn't find this patch.
>
>Doest anybody know something about libata concerning ACPI 
>problems? Btw. 
>I've got an "sata_nv" mnodule loaded in the single-user-mode, but my 
>sata is switched off in BIOS.
>
>Help appreciated! Thanks.
>
>----dmesg---Linux version 2.6.17-rc1-mm2a (root@vulcan) (gcc version 
>4.0.3 20060304 ------
>PM: Preparing system for mem sleep
>Stopping tasks: =========|
>[ACPI Debug]  String: [0x15] "==== SST Working ===="
>Suspending device 1.0
>Suspending device ide1
>Suspending device eisa.0
>Suspending device serio1
>Suspending device serio0
>Suspending device i8042
>Suspending device serial8250
>Suspending device pnp1
>Suspending device pcspkr
>Suspending device 00:09
>Suspending device 00:08
>Suspending device 00:07
>Suspending device 00:06
>Suspending device 00:05
>Suspending device 00:04
>Suspending device 00:03
>Suspending device 00:02
>Suspending device 00:01
>Suspending device 00:00
>Suspending device pnp0
>Suspending device 0000:02:00.1
>Suspending device 0000:02:00.0
>Suspending device 0000:00:1e.0
>Suspending device 0000:00:09.0
>Suspending device 0000:00:08.0
>Suspending device 0000:00:04.0
>Suspending device 0000:00:01.1
>Suspending device 0000:00:01.0
>Suspending device 0000:00:00.5
>Suspending device 0000:00:00.4
>Suspending device 0000:00:00.3
>Suspending device 0000:00:00.2
>Suspending device 0000:00:00.1
>Suspending device 0000:00:00.0
>Suspending device pci0000:00
>Suspending device platform
>PM: Entering mem sleep
> hwsleep-0285 [11] enter_sleep_state     : Entering sleep state [S3]
>Back to C!
>PM: Finishing wakeup.
>ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [LMAC] -> GSI 11 (level,
>low) -> IRQ 11
>PCI: Setting latency timer of device 0000:00:04.0 to 64
>PCI: Setting latency timer of device 0000:00:08.0 to 64
>pnp: Failed to activate device 00:09.
>Restarting tasks... done
>[ACPI Debug]  String: [0x15] "==== SST Working ===="
>ACPI Error (evevent-0314): No installed handler for fixed event
>[00000002] [20060310]
>[ACPI Debug]  String: [0x15] "==== SST Working ===="
>
>(*) don't know if initrd is the reason, but I've tried so much, that I 
>don't correctly remember anymore.
>-
>To unsubscribe from this list: send the line "unsubscribe 
>linux-acpi" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Failed resuming IDE from S3 on Abit NF7 (nForce2)

[acme]

Hello Luming,

well, I've tried your patch and it work, - sort of. The system resumes 
from S3 now, but the generic ide driver seems to be DMA-less. This is of 
course a no go solution. I've also tried the amd74xx driver, and this 
one is running into a time out, and comes back after a while also 
without DMA. Setting DMA afterward doesn't work anymore. Is it possible 
to apply your patch into the amd74xx driver somehow?

And a very strange situation I do also have here. I've compiled the 
kernel without framebuffer (otherwise it doesn't work at all), then I've 
accidentaly booted the system with the following kernel parameters:
  "vga=0x317 screen=1024x768 splash root=/dev/hda1 init=/bin/bash"
The result was a blank screen, because I do not have a framebuffer. Now 
you perhaps begin to wonder, why do I mention that here? Well, this 
kernel parameters are my only possibility to S3 my system! When I leave 
out "vga=0x317 screen=1024x768" my keyboard is instantly dead after S3. 
In other words: I can only S3 the box with a black screen, and have to 
ssh into the box from another mashine. How can it be, that booting the 
box in text mode ( videomode 3 ) S3 doesn't work at all?

btw: I can't use vbetool (v5.1) to restore the video mode either. Here 
is the result:

  #root@(none):~# vbetool vbestate save
  #Get video state buffer size failed
  #Allocated buffer at 0x11010 (base is 0x0)
  #ES: 0x1101 EBX: 0x0000
  #Save video state failed

It seems that it doesn't work with radeon cards. I've tried this with a 
Radeon 9200 (RV280), Radeon 9550 SE (RV350) and an nVidia TI4200. Only 
the last one could save the state correctly. Perhapt the internet is 
full of warnigs and signs saying: "vbetool doesn't work with Radeon", 
and I was only to stupid to use google the right way ;-)

Three weeks ago, I said "Hi, let's try the S3 stuff, could be fun". Now 
I am lucky to S3 the box with a black screen, and my only wish is to 
have DMA working also, well a working display would be the suger on the 
top of it. ;-)

I feel like beeing in the wrong movie, and it makes me more and more 
wonder why all things I try do not work the way they should. Never the 
less, thank you very much for your support, and I certainly won't give 
up. Now it's a challange! ;-)

Thanks and bye


Yu, Luming schrieb:

 >>the bug you are refering to, seems pretty much the same bug like I do
 >>have here. But I've got two questions. Could you please help me? And I
 >>do asume, that this patch isn't in the resent kernel yet, isn't it?
 >
 >
 >I didn't check it, Probably Not.
 >
 >>1) If I want to adopt your patch, I should use the values from my
 >>acpidump, but I can't find anything reasonable. What should my values
 >>look like? (see here:
 >>http://bugzilla.kernel.org/attachment.cgi?id=7762&action=view )
 >>
 >\\_SB.PCI0.IDE0.PRI0  (It's zero)
 >\\_SB.PCI0.IDE0.SEC0 (It's zero)
 >
 >
 >>2) How do I ensure, that this native IDE driver is really used? Do I
 >>have to uncheck all non-native IDE drivers in the kernel
 >>config? (In my
 >>case it's the amd71xx, I guess)
 >>
 >
 >You can try only CONFIG_IDE_GENERIC.
 >
 >
 >>Please excuse the silly questions, but I am pretty new to game
 >>of kernel
 >>configuration and compilation, but steady learning :-)
 >
 >
 >happy hacking. :-)
 >
 >--Luming
 >