mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Martin Aspeli <optilude@gmx.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Horrible ordeals with ACPI, APIC and HIGHMEM (2.6.0-test* and -ac kernels)
Date: Thu, 9 Oct 2003 14:58:39 -0700	[thread overview]
Message-ID: <20031009145839.A18072@build.pdx.osdl.net> (raw)
In-Reply-To: <oprwsoirf09y0cdf@mail.gmx.net>; from optilude@gmx.net on Thu, Oct 09, 2003 at 10:26:41PM +0100

* Martin Aspeli (optilude@gmx.net) wrote:
> On Thu, 9 Oct 2003 14:05:23 -0700, Chris Wright <chrisw@osdl.org> wrote:
> 
> > Which 2.6.0-test kernels?  Have you tried 2.6.0-test7?  A fix for this
> > type of problem went into -test7.
> 
> Sadly, yes. My most recent and most comprehensive tests (today) were with 
> the -test7 kernel. Could you give me some details as to what the fix is 
> supposed to do and why it may not work?

fixes acpi pci link allocation which could pick a bad irq causing an
interrupt storm.  typical symptom was hang on boot.  

If you see:

ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 6 7 10 *11 12)
...
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 6

where the link is not enabled at the current setting (11 in this case,
marked by *), you might experience this kind of hang.

> Also, I'd still be interested to know - what is "events/0"?

events/0 is a kernel thread (keventd) used for scheduling work into process
context.  acpi uses keventd for handling acpi events, for example, so
runaway apci events will cause events/0 to chew up cpu.

> And why do 
> things run like a 286 when I enable HIGHMEM? 

I don't know, it shouldn't.

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

  reply	other threads:[~2003-10-09 21:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-09 18:50 Martin Aspeli
2003-10-09 21:05 ` Chris Wright
2003-10-09 21:26   ` Martin Aspeli
2003-10-09 21:58     ` Chris Wright [this message]
2003-10-09 22:14       ` Martin Aspeli

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=20031009145839.A18072@build.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=optilude@gmx.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®