The other day, I reported to linux-kernel a kernel oops in 2.0.33 that
was a protection fault at 0040 during boot. Upon further
investigation, it appears that the Debian boot disks do not suffer
from this problem.
Today, I stumbled across the following in the configure help for APM:
because they don't have compliant BIOSes. Many "green" desktop
machines also don't have compliant BIOSes, and this driver will
cause those machines to panic during the boot phase (typically,
these machines are using a data segment of 0040, which is reserved
for the Linux kernel). If you get random kernel OOPSes that don't
My laptop is an IBM Thinkpad 310ED (I believe this model was
introduced last fall. It is a P133 MMX). I am getting protection
faults at 0040. Is it possible to make the Linux kernel use a
different location for whatever it is trying to store at 0040? Would
one of the exclude kernel parameters that I seem to recall hearing
about at one time fix this, and if so, what exactly should I exclude?
(How much RAM, etc.)
I am suspecting that this problem is why I cannot suspend or hibernate
my laptop under Linux. It will do either of those fine under bare DOS
(no config.sys, autoexec.bat, etc) or Windows.
Further, it seems that apm_bios.c in even 2.1.82 was last updated in
1996 -- and there may well be more laptops appearing since then that
may need special support. Is anybody still working on the APM driver?
It seems somewhat out of date.
Thanks for any insight.
John Goerzen
-- John Goerzen Southwind Internet Access, Inc, Business e-mail: jgoerzen@southwind.netPersonal e-mail: jgoerzen@complete.org Wichita State University e-mail: jgoerzen@cs.twsu.edu Developer, Debian GNU/Linux <http://www.debian.org>