From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Linux Kernel List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: 2.6.0-test6: APM unable to suspend (the 2.6.0-test2 saga continues)
Date: Sun, 28 Dec 2003 18:25:45 +0000 [thread overview]
Message-ID: <20031228182545.B20278@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20031228174622.A20278@flint.arm.linux.org.uk>; from rmk+lkml@arm.linux.org.uk on Sun, Dec 28, 2003 at 05:46:22PM +0000
On Sun, Dec 28, 2003 at 05:46:22PM +0000, Russell King wrote:
> Alan Cox has shed some light on this problem. He mentions that the
> x86 GDT/LDT stuff changed around 2.5.30, which is the time when others
> have also reported that their APM has stopped working. I've not
> confirmed whether that is the case for me as well, but it seems to
> be highly likely.
>
> I also asked Alan if there's the possibility of backing this out or
> making it configurable, but the answer seems to be a most definite
> no. However, maybe Ingo can say otherwise?
>
> This effectively means that people with laptops which do not work
> with 2.6 APM nor ACPI can expect their machines to be stuck with 2.4
> for the future, unless someone with the necessary knowledge sees this
> problem as important enough to solve.
A quick follow-up from a discussion I've just had with Andi Kleen...
Note that I know nothing about the x86 internals of LDT/GDT/APM stuff,
so I'm clutching at straws here...
Would it be possible to switch LDT/GDT to whatever the APM BIOS expects
just before calling the APM BIOS to suspend/hibernate, and restore them
to whatever Linux requires after the APM BIOS returns from resume?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2003-12-28 18:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-05 16:10 2.6.0-test6: APM unable to suspend (the 2.6.0-test2 saga continues) Russell King
2003-12-28 17:46 ` Russell King
2003-12-28 18:25 ` Russell King [this message]
2003-12-28 20:49 ` Linus Torvalds
2003-12-30 11:43 ` Russell King
2003-12-30 16:50 ` Russell King
2003-12-30 18:17 ` Russell King
2003-12-30 18:47 ` Linus Torvalds
2003-12-30 19:40 ` Russell King
2003-12-30 19:53 ` Russell King
2003-12-30 23:00 ` Vojtech Pavlik
2003-12-31 1:45 ` Dmitry Torokhov
2003-12-31 12:40 ` Vojtech Pavlik
2004-01-03 3:43 ` Rusty Russell
2004-01-03 18:28 ` 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=20031228182545.B20278@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
/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