public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Norbert Preining <preining@logic.at>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Olaf Dietsche <olaf+list.linux-acpi@olafdietsche.de>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6.22-rc3][ACPI?] Resume from s2r doesn't work.
Date: Sun, 22 Jul 2007 11:10:10 +0200	[thread overview]
Message-ID: <20070722091010.GH3701@elf.ucw.cz> (raw)
In-Reply-To: <20070614181329.GA31277@gamma.logic.tuwien.ac.at>

On Thu 2007-06-14 20:13:29, Norbert Preining wrote:
> Hi all!
> 
> On Die, 12 Jun 2007, Pavel Machek wrote:
> > > When I resume, everything seems to come up (fan becomes busy, disk and
> > > dvd spin up for a short time), but the machine is not responding to
> > > anything - neither keyboard, mouse nor ping from another machine. The
> > > laptop is effectively dead and only a power cycle helps.
> > > 
> > > I've tried a minimal config and init=/bin/bash as well, but the result
> > > is the same.
> > 
> > Beeping patch? It is in -mm now. noapic nolapic and nosmp are useful,
> > too.
> 
> 
> Ok, no beeping at all. Nothing after resume, only fan. And I did not
> forget to activate the BEEP line.
> 
> So where can I go from here? DSDT hacking? Anything else?

Hmm, it was 'hardware debugger' time when I hit similar problem few
years ago :-(.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2007-07-22  9:10 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070613173925.GA20628@gamma.logic.tuwien.ac.at>
2007-06-01 20:27 ` [2.6.22-rc3][ACPI?] Resume from s2r doesn't work Olaf Dietsche
2007-06-01 20:37   ` Rafael J. Wysocki
2007-06-01 21:12     ` Olaf Dietsche
2007-06-01 21:40       ` Rafael J. Wysocki
2007-06-01 22:17         ` Olaf Dietsche
2007-06-01 22:37           ` Rafael J. Wysocki
2007-06-01 23:31             ` Nigel Cunningham
2007-06-02 11:08             ` Mitch Davis
2007-06-03 21:20             ` Olaf Dietsche
2007-06-04  8:13               ` Rafael J. Wysocki
2007-06-04 16:43                 ` Olaf Dietsche
2007-06-04 21:02                   ` Rafael J. Wysocki
2007-06-07 19:50                     ` Olaf Dietsche
2007-06-08 13:07                       ` Olaf Dietsche
2007-06-07 12:23               ` Pavel Machek
2007-06-07 19:54                 ` Olaf Dietsche
2007-06-07 21:15                   ` Pavel Machek
2007-06-02  0:07           ` Indan Zupancic
2007-06-02  4:36   ` Andrey Borzenkov
2007-06-12 15:31   ` Pavel Machek
2007-06-13 19:56     ` Olaf Dietsche
2007-06-14 19:56       ` Pavel Machek
2007-06-15 12:35         ` Richard Hughes
2007-06-15 15:55         ` Olaf Dietsche
2007-06-14 18:13     ` Norbert Preining
2007-07-22  9:10       ` Pavel Machek [this message]
2007-08-12 16:52         ` Norbert Preining
2007-08-14 10:09           ` Pavel Machek

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=20070722091010.GH3701@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf+list.linux-acpi@olafdietsche.de \
    --cc=preining@logic.at \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox