public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: matthieu castet <castet.matthieu@free.fr>,
	linux-acpi@vger.kernel.org,
	pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: suspend to ram problem
Date: Sun, 3 Feb 2008 19:22:02 +0100	[thread overview]
Message-ID: <200802031922.02877.rjw@sisk.pl> (raw)
In-Reply-To: <20080203181855.GB1629@elf.ucw.cz>

On Sunday, 3 of February 2008, Pavel Machek wrote:
> On Sun 2008-02-03 18:39:01, Rafael J. Wysocki wrote:
> > On Sunday, 3 of February 2008, matthieu castet wrote:
> > > matthieu castet wrote:
> > > > Hi,
> > > > 
> > > > I am trying to make work suspend to ram on a MSI MS-6380E with a 2.6.23 
> > > > kernel.
> > > > 
> > > > Standby mode works.
> > > > S2ram suspend seems to work : the computer turn off and I can wake up it 
> > > > with the keyboard.
> > > > 
> > > > But when the computer wakeup, I see the video card POST on the screen, 
> > > > but after that the computer hangs : black screen, no working numlock.
> > > > 
> > > > I tried to compile PM_TRACE, but it give no result. So this means the 
> > > > resume hang very early.
> > > > 
> > > > What can I do to debug this ?
> > > >
> > > I play with the s2_beep feature and :
> > > - echo 4 > /proc/sys/kernel/acpi_video_flags make the computer beep
> > > - echo 4 > /proc/sys/kernel/acpi_video_flags make the computer not beep
> > > - adding a beep in bogus_real_magic, make the computer not beep
> > > 
> > > So the hang seems located in wakeup_start.
> > 
> > Hm.  Can you add unconditional BEEP after "jne bogus_real_magic" in
> > arch/x86/kernel/acpi/wakeup.S and see if it beeps?
> 
> Hmm, maybe I know where problem could be. Try
> 
>         movl     $(wakeup_stack - wakeup_code), %esp              # Private stack is needed for ASUS bo\
> 
> instead of existing stack setup. That helped on one of my test-boxes
> -- I uncovered that during rewrite.

Well, that could explain some mysterious failures reported from time to time by
ASUS users.

Rafael

  reply	other threads:[~2008-02-03 18:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-03 13:37 suspend to ram problem matthieu castet
2008-02-03 15:31 ` matthieu castet
2008-02-03 17:39   ` Rafael J. Wysocki
2008-02-03 18:18     ` Pavel Machek
2008-02-03 18:22       ` Rafael J. Wysocki [this message]
2008-02-03 18:40       ` matthieu castet
2008-02-04  6:57         ` matthieu castet
2008-02-05 23:02           ` matthieu castet
2008-02-05 23:20             ` Rafael J. Wysocki
2008-02-06 22:40               ` matthieu castet
2008-02-06 22:43                 ` Pavel Machek
2008-02-06 23:03                   ` Rafael J. Wysocki
2008-02-07 20:12                     ` Cacy Rodney
2008-02-06 22:43                 ` Pavel Machek
2008-02-06 23:17                   ` matthieu castet
2008-02-07  9:20                     ` Pavel Machek
2008-02-07 19:49                       ` matthieu castet
2008-02-07 20:00                         ` Rafael J. Wysocki
2008-02-08 22:10                           ` Pavel Machek
2008-02-07  9:23             ` Pavel Machek
2008-02-07 18:39               ` 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=200802031922.02877.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=castet.matthieu@free.fr \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox