From: Matthew Garrett <mjg59@srcf.ucam.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andi Kleen <andi@firstfloor.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Andy Lutomirski <luto@myrealbox.com>, Ingo Molnar <mingo@elte.hu>,
public-kernel-testers-u79uwXL29TY76Z2rM5mHXA@lo.gmane.org,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: [RFT] x86 acpi: normalize segment descriptor register on resume
Date: Mon, 14 Jul 2008 02:31:25 +0100 [thread overview]
Message-ID: <20080714013125.GA3681@srcf.ucam.org> (raw)
In-Reply-To: <487A67C3.50000@zytor.com>
On Sun, Jul 13, 2008 at 01:38:27PM -0700, H. Peter Anvin wrote:
> The most likely explanation for this is that the VESA BIOS expects to be
> entered in Big Real Mode (*.limit = 0xffffffff) instead of ordinary Real
> Mode. Here is a completely untested patch which changes the segment
> descriptors to Big Real Mode instead. It would be worth testing out.
Recent Lenovo BIOSes will read from somewhere just under the 4GB
boundary if the video BIOS is called, so this sounds likely.
Unfortunately my T61 is, uh, unhappy right now, so I can't test this.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-07-14 1:31 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 23:48 [RFT] x86 acpi: normalize segment descriptor register on resume Rafael J. Wysocki
[not found] ` <200807010148.02135.rjw-KKrjLPT3xs0@public.gmane.org>
2008-07-01 0:05 ` H. Peter Anvin
2008-07-01 6:31 ` Ingo Molnar
[not found] ` <20080701063133.GC16642-X9Un+BFzKDI@public.gmane.org>
2008-07-01 6:54 ` H. Peter Anvin
2008-07-01 9:19 ` Pavel Machek
2008-07-01 20:39 ` Rafael J. Wysocki
2008-07-01 20:42 ` Andi Kleen
2008-07-01 20:50 ` Rafael J. Wysocki
2008-07-01 20:52 ` Andi Kleen
[not found] ` <486A96C1.2020106-Vw/NltI1exuRpAAqCnN02g@public.gmane.org>
2008-07-12 6:29 ` Andy Lutomirski
2008-07-12 12:08 ` Andi Kleen
[not found] ` <48789EC3.2070701-Vw/NltI1exuRpAAqCnN02g@public.gmane.org>
2008-07-12 15:08 ` Andy Lutomirski
[not found] ` <48784F51.1010407-YSGFQ8SKJZVDPfheJLI6IQ@public.gmane.org>
2008-07-12 18:51 ` Rafael J. Wysocki
2008-07-12 20:31 ` Andy Lutomirski
2008-07-12 20:47 ` Rafael J. Wysocki
2008-07-12 20:39 ` Andy Lutomirski
2008-07-12 20:53 ` Rafael J. Wysocki
2008-07-12 23:11 ` Andy Lutomirski
2008-07-12 23:33 ` Rafael J. Wysocki
2008-07-13 8:56 ` Pavel Machek
2008-07-13 18:16 ` H. Peter Anvin
2008-07-14 6:36 ` Pavel Machek
2008-07-13 9:15 ` Ingo Molnar
2008-07-13 12:02 ` Matthew Garrett
2008-07-13 15:50 ` Andy Lutomirski
2008-07-13 18:43 ` Andi Kleen
2008-07-13 19:15 ` Rafael J. Wysocki
2008-07-13 20:11 ` Andi Kleen
2008-07-13 20:29 ` Rafael J. Wysocki
2008-07-14 2:35 ` H. Peter Anvin
2008-07-14 20:10 ` Rafael J. Wysocki
2008-07-13 20:38 ` H. Peter Anvin
2008-07-14 1:31 ` Matthew Garrett [this message]
2008-07-14 4:18 ` H. Peter Anvin
2008-07-14 7:39 ` Pavel Machek
2008-07-14 20:09 ` Rafael J. Wysocki
2008-07-16 14:13 ` Andrew Lutomirski
2008-07-16 14:23 ` Ingo Molnar
2008-07-13 20:16 ` H. Peter Anvin
2008-07-13 20:21 ` Andi Kleen
2008-07-13 20:32 ` Rafael J. Wysocki
2008-07-14 1:22 ` Henrique de Moraes Holschuh
2008-07-14 6:14 ` Pavel Machek
2008-07-14 11:22 ` Henrique de Moraes Holschuh
2008-07-13 18:02 ` Rafael J. Wysocki
2008-07-01 7:02 ` H. Peter Anvin
2008-07-01 13:01 ` Andi Kleen
2008-07-01 15:55 ` H. Peter Anvin
[not found] ` <486A5378.7020601-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2008-07-01 16:21 ` Andi Kleen
2008-07-01 17:28 ` H. Peter Anvin
2008-07-01 7:20 ` Ingo Molnar
[not found] ` <20080701072024.GB26601-X9Un+BFzKDI@public.gmane.org>
2008-07-01 7:28 ` Andrew Morton
2008-07-01 7:45 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2008-07-12 23:07 H. Peter Anvin
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=20080714013125.GA3681@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=luto@myrealbox.com \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=public-kernel-testers-u79uwXL29TY76Z2rM5mHXA@lo.gmane.org \
--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;
as well as URLs for NNTP newsgroup(s).