From: Pavel Machek <pavel@ucw.cz>
To: Alessandro Guido <alessandro.guido@gmail.com>
Cc: ACPI mailing list <linux-acpi@vger.kernel.org>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Kohjinsha sleep problems
Date: Sat, 5 Jan 2008 22:44:40 +0100 [thread overview]
Message-ID: <20080105214440.GA10292@elf.ucw.cz> (raw)
In-Reply-To: <20080105213536.GA2307@elf.ucw.cz>
Hi!
> > > On kohjinsha, wakeup code does not seem to be reached at all. I tried
> > > looking around FACS, but it seems very empty:
> > >
> > > ...
> >
> > The same on my laptop:
> >
> > FACS @ 0x2fefafc0
signature length hwsignature waking_vector
> > 0000: 46 41 43 53 40 00 00 00 62 12 00 00 00 00 00 00 FACS@...b.......
> > 0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> > 0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> > 0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> >
> >
> > I've never been able to resume from STR with Linux (works with Windows Vista).
> > STD works, although I have to press the power button in order to
> > resume.
Hmm, that is strange. firmware_waking_vector seems to be all
zeros. How can that work?
struct acpi_table_facs {
char signature[4]; /* ASCII table signature */
u32 length; /* Length of structure, in bytes */
u32 hardware_signature; /* Hardware configuration signature */
u32 firmware_waking_vector; /* 32-bit physical address of
the Firmware Waking Vector */
...aha, firmware_waking_vector is to be filled by Linux, so I guess
this was false alarm.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2008-01-05 21:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-01 23:19 Kohjinsha sleep problems Pavel Machek
2008-01-04 21:33 ` Alessandro Guido
2008-01-05 21:35 ` Pavel Machek
2008-01-05 21:44 ` Pavel Machek [this message]
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=20080105214440.GA10292@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=alessandro.guido@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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