From: Erik Mouw <J.A.K.Mouw@its.tudelft.nl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "John W. M. Stevens" <john@betelgeuse.us>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Defect (Bug) Report
Date: Sun, 2 Feb 2003 14:35:01 +0100 [thread overview]
Message-ID: <20030202133501.GA32041@arthur.ubicom.tudelft.nl> (raw)
In-Reply-To: <1044195694.16853.22.camel@irongate.swansea.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
On Sun, Feb 02, 2003 at 02:21:35PM +0000, Alan Cox wrote:
> On Sun, 2003-02-02 at 12:49, Erik Mouw wrote:
> > Exact BIOS revision doesn't seem to matter. Any more suggestions?
>
> BIOS revision matters too. With 1004 you need to set MP 1.1 not MP 1.4
> and APIC works reliably. With 1007 it seems that isnt needed but people
> report weird hangs. 1004 also won't POST with a broadcom ethernet card
> in it.
Yes, I've seen weird hangs with 1007 and MP 1.4. "noapic" fixes it. Do
you suggest using MP 1.1 even with 1007?
> The proper fix for the PS/2 mouse/IDE problem appears to be always
> mapping out the page at 636-640K. Andi posted an ugly patch to handle
> that, but doing it cleanly is trickier.
I think I missed his patch, but a dirty trick I could think of would be
to put a "reserved" entry in the e820 RAM map we got from the BIOS.
Erik
--
J.A.K. (Erik) Mouw
Email: J.A.K.Mouw@its.tudelft.nl mouw@nl.linux.org
WWW: http://www-ict.its.tudelft.nl/~erik/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-02-02 13:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-02 1:12 John W. M. Stevens
2003-02-02 9:42 ` Alan Cox
2003-02-02 12:49 ` Erik Mouw
2003-02-02 12:57 ` Willy Tarreau
2003-02-02 14:21 ` Alan Cox
2003-02-02 13:35 ` Erik Mouw [this message]
2003-02-02 14:52 ` Alan Cox
2003-02-02 14:05 ` Jens Axboe
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=20030202133501.GA32041@arthur.ubicom.tudelft.nl \
--to=j.a.k.mouw@its.tudelft.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=john@betelgeuse.us \
--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®