From: Disconnect <lkml@sigkill.net>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: APIC on Dell Laptops - WAS: Re: [RFC] Fix NMI watchdog documentation
Date: 27 May 2003 16:25:20 -0400 [thread overview]
Message-ID: <1054067120.6085.4.camel@slappy> (raw)
In-Reply-To: <1053978298.6152.25.camel@slappy>
On Mon, 2003-05-26 at 14:38, mikpe@csd.uu.se wrote:
> Disconnect writes:
> > Local APIC disabled by BIOS -- reenabling.
> > Found and enabled local APIC!
> >
> > And now /proc/cpuinfo and cpuid both show APIC support.
> >
> > Removed/replaced power, triggered lid-switch/battery-status/etc with no
> > issues. (The only thing that caused trouble was Fn-F10, the "eject cd"
> > button. Never tried it under Linux before, and the cd isn't in it at
> > the moment anyway, so I'm betting thats unrelated. But it did cause a
> > lockup that even sysrq couldn't recover.)
>
> Nice.
..and it gets better. Not sure what the exact problem is (updated DRM, X
etc) but Fn-F8 (CRT/LCD) hardlocks. With the no-APIC kernel (same new
DRM and so forth) it just hesitates (not sure if it works or not,
haven't got a monitor handy.) It worked (or at least didn't lock up)
when I initially tried it, but now I can reproduce it well before X
comes up.
Looks like it should be dropped from the whitelist :( (To recap, this
is the Inspiron 8500 w/ A02 bios)
--
Disconnect <lkml@sigkill.net>
next prev parent reply other threads:[~2003-05-27 20:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-26 9:21 [RFC] Fix NMI watchdog documentation mikpe
2003-05-26 16:40 ` APIC on Dell Laptops - WAS: " Disconnect
2003-05-26 18:38 ` mikpe
2003-05-26 19:44 ` Disconnect
2003-05-27 20:25 ` Disconnect [this message]
2003-05-27 3:19 ` Valdis.Kletnieks
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=1054067120.6085.4.camel@slappy \
--to=lkml@sigkill.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.