All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brannon Klopfer <bklopfer@stanford.edu>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-acpi@vger.kernel.org, acpi@linux.intel.com, pavel@suse.cz
Subject: Re: hp dv8000t dead on resume from RAM
Date: Wed, 09 Aug 2006 11:01:58 -0700	[thread overview]
Message-ID: <44DA2316.1060006@stanford.edu> (raw)
In-Reply-To: <200608082230.54788.rjw@sisk.pl>

Rafael J. Wysocki wrote:
> On Tuesday 08 August 2006 19:15, Brannon Barrett Klopfer wrote:
>   
>> Howdy,
>>
>> My hp dv8000t (core duo) is completely dead on resume from RAM (no caps
>> lock, sysrq, netconsole,
>> nothing). I've tried a recent (2.6.18-rc4) kernel running almost entirely
>> naked, so to speak (~990K) -- no support for:
>>
>> SMP
>> preempt
>> modules
>> networking (+ enet drivers, unless running netconsole)
>> USB and SATA (not at same time; rootfs is either usb drive or SATA [ext2/3])
>> FireWire
>> cpufreq
>> framebuffer (vga=0)
>> audio
>> PCMCIA
>> IDE (for cdrom)
>>
>> I've tried both native SATA (ahci) and legacy (ata_piix), but same result
>> w/both -- completely dead on resume from RAM. Blindly entering commands
>> does nothing, and running "$suspend ; $shutdown" does nothing either. I've
>> also tried with and without noapic, and a number of other kernel
>> paramaters, but nothing seems to work.
>>
>> Be more than happy to try out patches, etc. to get this thing working.
>> Additionally, if someone could point me to that "beep on resume" patch,
>> that'd be great.
>>     
>
> First, please apply the appended patch and try the following:
>
> (1)
> # echo testproc > /sys/power/disk
> # echo disk > /sys/power/state
>
> This should turn off the non-boot CPU, freeze all processes, wait for 5
> seconds and then thaw the processes and the CPU.
>   
Works fine. FWIW, after applying the patchs (so as to have 
2.6.18-rc3-mm2), my internal keyboard didn't work, so I used a USB one. 
It could be my simple .config'ing error, didn't spend much time with it, 
but know that I did use a USB keyboard, hence USB support in the kernel.
> (2)
> # echo test > /sys/power/disk
> # echo disk > /sys/power/state
>
> This should turn off the non-boot CPU, freeze all processes, shrink
> memory, suspend all devices, wait for 5 seconds, resume the devices etc.
> IOW it does everything that's needed for a suspend except for actually
> suspending.
>   
With *legacy* ata_piix, it works fine, as does a "real" suspend-to-disk. 
It still *will not* resume properly from suspend-to-RAM, with and 
without noapic. FWIW, somehow the built-in keyboard managed to get its 
caps lock light on (I couldn't get it off again), and it *did* come back 
on when the machine resumed from RAM, though nothing else (network, usb, 
etc.) worked.

Using native ahci and the "test" suspend-to-disk, the system hangs. I 
did this from init=/bin/bash with vga=794 (so I could see all output), 
however, at least the last few lines match w/vga=0 (i.e., fb didn't 
affect problem). The hand-copied (pardon any typos) output is:
---
Disabling non-boot CPUs ...
CPU 1 is now offline
SMP alternatives: switching to UP code
CPU1 is down
Stopping tasks: =======|
Shrinking memory... done (0 pages freed)
Suspending device usbdev4.5
Suspending device usbdev4p5_ep82
Suspending device 4-2.1:1.1
Suspending device usbdev4.5_ep81
Suspending device 4-2.1:1.0
Suspending device usbdev4.5_ep00
Suspending device 4-2.1
Suspending device usbdev4.4
Suspending device usbdev4.4_ep81
Suspending device 4-2:1.0
Suspending device usbdev4.4_ep00
Suspending device 4-2
Suspending device vcsa1
Suspending device vcs1
Suspending device eisa.0
Suspending device i2c-0
Suspending device i2c-0
Suspending device psaux
Suspending device serio4
Suspending device serio3
Suspending device serio2
Suspending device serio1
Suspending device serio0
Suspending device i8042
# Short pause here...
atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying 
access hardware directly.
Suspending device usbdev5.1
Suspending device usbdev5.1_ep81
Suspending device 5-0:1.0
Suspending device usbdev5.1_ep00
Suspending device usb5
Suspending device usbdev4.1
Suspending device usbdev4.1_ep81
Suspending device 4-0:1.0
Suspending device usbdev4.1_ep00
Suspending device usb4
Suspending device usbdev3.1
Suspending device usbdev3.1_ep81
Suspending device 3-0:1.0
Suspending device usbdev3.1_ep00
Suspending device usb3
Suspending device usbdev2.1
Suspending device usbdev2.1_ep81
Suspending device 2-0:1.0
Suspending device usbdev2.1_ep00
Suspending device usb2
Suspending device usbdev1.1
Suspending device usbdev1.1_ep81
Suspending device 1-0:1.0
Suspending device usbdev1.1_ep00
Suspending device usb1
Suspending device 0:0:0:0
Suspending device target0:0:0
Suspending device host3
Suspending device host2
Suspending device host1
Suspending device host0
Suspending device 0.0
# Hangs here. Screen blanks in maybe 5-10min, won't turn back on; I 
assume this is the hardware doing something. Again, this is only with ahci.
---

I'll try to get that beep patch, to further diagnose things...

Thanks,
Brannon
> Greetings,
> Rafael
>
> ---
>  include/linux/pm.h  |    4 +++-
>  kernel/power/disk.c |   37 ++++++++++++++++++++++++++++---------
>  2 files changed, 31 insertions(+), 10 deletions(-)
<snip...patch applied cleanly>


  reply	other threads:[~2006-08-09 18:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08 17:15 hp dv8000t dead on resume from RAM Brannon Barrett Klopfer
2006-08-08 20:30 ` Rafael J. Wysocki
2006-08-09 18:01   ` Brannon Klopfer [this message]
2006-08-09 19:59     ` Rafael J. Wysocki
  -- strict thread matches above, loose matches on Subject: below --
2006-08-10 18:29 Brannon Barrett Klopfer
2006-08-10 19:19 ` Rafael J. Wysocki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44DA2316.1060006@stanford.edu \
    --to=bklopfer@stanford.edu \
    --cc=acpi@linux.intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=rjw@sisk.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.