mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: andersg@0x63.nu
Cc: linux-kernel@vger.kernel.org
Subject: Re: Local APIC option (CONFIG_X86_UP_APIC) locks up Inspiron 8100
Date: Wed, 31 Oct 2001 23:17:16 +0100 (MET)	[thread overview]
Message-ID: <200110312217.XAA28976@harpo.it.uu.se> (raw)

On Wed, 31 Oct 2001 22:42:01 +0100, andersg@0x63.nu wrote:
> > > > Not all BIOS firmware can cope when we switch to UP-APIC. Some laptops 
> > > > really don't like it one bit.
> > >
> > >Correct, and the I8x00 is the prime example of that.
> > >
> > >I have a fix, but it involves fairly major surgery:
> > >- Implement bt_ioremap()/bt_iounmap() which work at early boot-time (the
> > >  normal ioremap doesn't work yet).
> > >...
> > >The patch is still _very_ rough, but it seems to work. Let me know if you want it.
> > 
> > The patch is now available at
> > http://www.csd.uu.se/~mikpe/linux/patch-2.4.13ac5-init-order-5
> 
> The same problem appears on "Dell Latitude C810". So that should probably be
> added to the dmi-backlist too. 

You have confirmed that allowing the local APIC to be enabled
causes it to lock up at system management events, and that keeping
the local APIC disabled prevents those lockups?

Send me the DMI scan output (change the dmi_printk #define in dmi_scan.c
to actually do a printk) and I'll add the C810 to the blacklist.

/Mikael

             reply	other threads:[~2001-10-31 22:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-31 22:17 Mikael Pettersson [this message]
2001-10-31 22:24 ` andersg
  -- strict thread matches above, loose matches on Subject: below --
2001-10-31 20:11 Mikael Pettersson
2001-10-31 21:42 ` andersg
2001-10-31  5:06 Stevie O
2001-10-31 10:44 ` Alan Cox
2001-10-31 11:26 ` Mikael Pettersson
2001-10-31 23:49 ` Stevie O

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=200110312217.XAA28976@harpo.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=andersg@0x63.nu \
    --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

all inboxes | Powered by JetHome®