mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: stevie@qrpff.net (Stevie O)
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Local APIC option (CONFIG_X86_UP_APIC) locks up Inspiron 8100
Date: Wed, 31 Oct 2001 12:26:29 +0100	[thread overview]
Message-ID: <15327.57317.942272.629551@harpo.it.uu.se> (raw)
In-Reply-To: <E15ysre-0003FD-00@the-village.bc.nu>
In-Reply-To: <5.1.0.14.2.20011030235723.022818d8@whisper.qrpff.net> <E15ysre-0003FD-00@the-village.bc.nu>

Alan Cox writes:
 > > 2) Anytime I change the plugged-in status of the AC adapter (if it wasn't 
 > > plugged in, if I plug it in; if it was plugged in, if I unplug it), the 
 > > machine locks up completely.
 > 
 > 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). This is done by adding 16 boot-time
  only fixmap entries, and using those for temporary mappings. These
  fixmap entries are reclaimed once vmalloc() is initialised, so they
  don't steal address space permanently.
  This would also help some other code which wants to scan arbitrary
  physical memory at early boot-time.
- Move dmi_scan from main to the i386 setup_arch(). To permit this, ioremap()
  is changed to bt_ioremap(), and vmalloc() to alloc_bootmem().
- Add a blacklist entry in dmi_scan, which sets a "don't enable local APIC"
  flag if the I8000 or any problematic machine is found.
- Move init_apic_mappings() from setup_arch() to trap_init(). This is
  so that kernel command-line parameters can be used to override stuff.
- Change detect_init_apic() to refuse to enable the local APIC if the
  blacklist flag is set.

The patch is still _very_ rough, but it seems to work. Let me know if you want it.

/Mikael

  parent reply	other threads:[~2001-10-31 11:26 UTC|newest]

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

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=15327.57317.942272.629551@harpo.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stevie@qrpff.net \
    /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®