All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Gardner <timg@tpi.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: nigel@nigel.suspend2.net, linux-kernel@vger.kernel.org,
	Ben Collins <ben.collins@ubuntu.com>
Subject: Re: Resume from S2R fails after dpm_resume()
Date: Fri, 02 Mar 2007 07:25:49 -0700	[thread overview]
Message-ID: <45E833ED.2070402@tpi.com> (raw)
In-Reply-To: <20070302141259.GJ2156@elf.ucw.cz>

Pavel Machek wrote:
> Hi!
> 
>> I instrumented 2.6.21-rc1 base/power/resume.c device_resume() with
>> TRACE_RESUME(0) as the last statement in the function. Sure enough it
>> was the last hash value in the RTC after a hard reboot when resume failed:
>>
>> [   12.028820]   hash matches drivers/base/power/resume.c:104
>>
>> The machine appears to be absolutely wedged after initiating resume by
>> pressing the power button. The disk flashes for a half second or so,
>> then thats it.
>>
>> It is a Dell XPS, BIOS rev A04. I'm using 'echo 1 > /sys/power/pm_trace;
>> echo mem > /sys/power/state' to initiate the S2R sequence.
>>
>> Any suggestions on where to go from here?
> 
> Did it work ok in 2.6.20? Can you try to get video working/get serial
> console/something?
> 									Pavel

Pavel,

The last version that worked well was Ubuntu Edgy (2.6.17). It was
broken by 2.6.18. I have not started the 'git bisect' process, instead
I've been trying to figure out why it doesn't work in 2.6.21-rc2. Using
the TRACE_RESUME macro I've drilled down to
kernel/printk.c:__call_console_drivers. So far the last trace info that
I have is just before the call to con->write(). I'm trying to figure out
what driver has registered as the console (intel_agp or agpgart?).

Am I banging my head on a known problem?

rtg

-- 
Tim Gardner timg@tpi.com www.tpi.com
OR 503-601-0234 x102 MT 406-443-5357

  reply	other threads:[~2007-03-02 14:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-28 20:35 Resume from S2R fails after dpm_resume() Tim Gardner
2007-03-02 14:12 ` Pavel Machek
2007-03-02 14:25   ` Tim Gardner [this message]
2007-03-02 14:39     ` Pavel Machek
2007-03-02 14:55       ` Ben Collins
2007-03-02 15:00         ` Pavel Machek
2007-03-02 21:32     ` Nigel Cunningham

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=45E833ED.2070402@tpi.com \
    --to=timg@tpi.com \
    --cc=ben.collins@ubuntu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nigel@nigel.suspend2.net \
    --cc=pavel@ucw.cz \
    /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.