mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Dale E Martin <dmartin@cliftonlabs.com>, linux-kernel@vger.kernel.org
Subject: Re: repeatable, hard lockup on boot in linux-2.6.0-test4 (more details)
Date: Tue, 2 Sep 2003 16:45:25 -0700	[thread overview]
Message-ID: <20030902164525.A11944@osdlab.pdx.osdl.net> (raw)
In-Reply-To: <20030902130323.41d2fdca.akpm@osdl.org>; from akpm@osdl.org on Tue, Sep 02, 2003 at 01:03:23PM -0700

* Andrew Morton (akpm@osdl.org) wrote:
> Looks like it.  Please add a DB() to the start of i8042_interrupt(),
> see if we locked up in an interrupt storm.  Also sprinkle some in 
> request_irq() I guess.  You know the deal ;)

I have similar issue with:
floppy_init()
  floppy_grab_irq_and_dma()
    fd_request_irq()
      request_irq()

      floppy_hardint()
      ...
      floppy_hardint()

This causes interrupt storm, hanging the machine on bootup.  Booting with
pci=noacpi fixes this.  So, I'm assuming acpi pci irq routing problem.
This is irq 6, which ACPI is disabling.  Perhaps disabling leaves it in
a bogus state?

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

  reply	other threads:[~2003-09-02 23:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-01 15:33 repeatable, hard lockup on boot in linux-2.6.0-test4 Dale E Martin
2003-09-01 18:23 ` repeatable, hard lockup on boot in linux-2.6.0-test4 (more details) Dale E Martin
2003-09-01 19:04   ` Andrew Morton
2003-09-01 19:57     ` Dale E Martin
2003-09-01 22:28       ` Andrew Morton
2003-09-02  0:31         ` Dale E Martin
2003-09-02  1:23           ` Andrew Morton
2003-09-02 12:30             ` Dale E Martin
2003-09-02 20:03               ` Andrew Morton
2003-09-02 23:45                 ` Chris Wright [this message]
2003-09-03 12:41                 ` Dale E Martin
2003-09-02 11:04 ` repeatable, hard lockup on boot in linux-2.6.0-test4 Maciej Freudenheim

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=20030902164525.A11944@osdlab.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=akpm@osdl.org \
    --cc=dmartin@cliftonlabs.com \
    --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®