From: David Weinehall <tao@acc.umu.se>
To: Nickolai Zeldovich <kolya@MIT.EDU>
Cc: linux-kernel@vger.kernel.org, csapuntz@stanford.edu
Subject: Re: [patch] Fix GDT re-load on ACPI resume
Date: Tue, 16 Nov 2004 00:02:49 +0100 [thread overview]
Message-ID: <20041115230249.GR29980@khan.acc.umu.se> (raw)
In-Reply-To: <Pine.GSO.4.58L.0411151525540.28749@contents-vnder-pressvre.mit.edu>
On Mon, Nov 15, 2004 at 03:35:14PM -0500, Nickolai Zeldovich wrote:
> The ACPI resume code currently uses a real-mode 16-bit lgdt instruction to
> reload the GDT. This only restores the lower 24 bits of the GDT base
> address. In recent kernels, the GDT seems to have moved out of the lower
> 16 megs, thereby causing the ACPI resume to fail -- an invalid GDT was
> being loaded.
>
> This simple patch adds the 0x66 prefix to lgdt, which forces it to load
> all 32 bits of the GDT base address, thereby removing any restrictions on
> where the GDT can be placed in memory. This makes ACPI resume work for me
> on a Thinkpad T40 laptop.
Sadly doesn't work for me. ACPI resume broke for me with
2.6.10-rc1-bk15 (possibly 14, but that one didn't compile), and this
patch does not fix it.
Regards: David Weinehall
--
/) David Weinehall <tao@acc.umu.se> /) Northern lights wander (\
// Maintainer of the v2.0 kernel // Dance across the winter sky //
\) http://www.acc.umu.se/~tao/ (/ Full colour fire (/
next prev parent reply other threads:[~2004-11-15 23:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 20:35 [patch] Fix GDT re-load on ACPI resume Nickolai Zeldovich
2004-11-15 23:02 ` David Weinehall [this message]
2004-11-15 23:13 ` Nickolai Zeldovich
2004-11-15 23:26 ` Maciej W. Rozycki
2004-11-15 23:52 ` Nickolai Zeldovich
-- strict thread matches above, loose matches on Subject: below --
2004-11-16 5:37 Li, Shaohua
2004-11-16 12:42 ` Maciej W. Rozycki
2004-11-16 17:46 ` Hiroshi Itoh
2004-11-17 1:02 ` Maciej W. Rozycki
2004-11-17 18:57 ` Pavel Machek
2004-11-18 1:59 Li, Shaohua
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=20041115230249.GR29980@khan.acc.umu.se \
--to=tao@acc.umu.se \
--cc=csapuntz@stanford.edu \
--cc=kolya@MIT.EDU \
--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