mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IO-APIC -- lockup on machine if enabled
Date: Fri, 15 Mar 2002 14:07:00 +0100	[thread overview]
Message-ID: <15505.61940.536141.204015@kim.it.uu.se> (raw)
In-Reply-To: <20020315100502.GA12793@merlin.emma.line.org>
In-Reply-To: <200203132052.VAA08581@harpo.it.uu.se> <20020315100502.GA12793@merlin.emma.line.org>

Matthias Andree writes:
 > On Wed, 13 Mar 2002, Mikael Pettersson wrote:
 > 
 > > p.s. The update for 2.4.19-pre3 and the full kit for 2.4.18 are
 > > at <http://www.csd.uu.se/~mikpe/linux/patches/2.4/> as usual.
 > 
 > Does that also fix the "crashes on switch back from X11 to text (or
 > frame buffer) console" that's been around since 2.4.9 or 2.4.10, but not
 > before, that bites so many users of SuSE Linux 7.3?
 > de.comp.os.unix.linux.* has at least one report every week. SuSE shipped
 > kernel 2.4.10 with 7.3.

The dmi-apic-fixups patch ONLY deals with disabling use of the local
APIC (or parts of it in some cases, e.g. AL440LX) when a known broken
BIOS or machine is detected by the DMI scan.

Without an adequate analysis of the problem you describe above I can't
even guess what the fix might be.

/Mikael

  parent reply	other threads:[~2002-03-15 13:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-13 20:52 Mikael Pettersson
2002-03-13 22:41 ` Alan Cox
2002-03-15 10:05 ` Matthias Andree
2002-03-15 13:07 ` Mikael Pettersson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-13 20:53 Mikael Pettersson
2002-03-13 13:34 Josh Fryman
2002-03-13 14:10 ` Dave Jones
2002-03-13 15:58   ` Jonathan H N Chin

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=15505.61940.536141.204015@kim.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.andree@stud.uni-dortmund.de \
    /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®