public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dale E Martin" <dmartin@cliftonlabs.com>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>
Subject: Re: repeatable, hard lockup on boot in linux-2.6.0-test4 (more details)
Date: Wed, 3 Sep 2003 08:41:31 -0400	[thread overview]
Message-ID: <20030903124131.GA842@cliftonlabs.com> (raw)
In-Reply-To: <20030902130323.41d2fdca.akpm@osdl.org>

> Looks like it.  Please add a DB() to the start of i8042_interrupt(),
> see if we locked up in an interrupt storm.

I believe this is what's happening - i8042_interrupt is getting called at a
very fast rate and we never do anything else.  (I suppose that's the
definition of an interrupt storm - this is my first foray into kernel
programming aside from fixing compiler errors.)

As others have suggested, booting with "pci=noacpi" fixes the problem.
(Leaving the debug statement in there, I'd estimate that i8042_interrupt
gets called at about 25 times a second - about a screenfull a second or
so.)

So, anyone else with this problem can plug in a PS/2 mouse or boot with
"pci=noacpi" to work around it.

The last thing I would mention is that 2.5.75 ran fine on this machine, so
I guess this problem has crept in since then.

> There's an ugly in the irq code there: if i8042_check_mux() or
> i8042_check_mux() are called while the device is open we end up freeing
> the wrong IRQ.  It is unlikely to help though.

I did apply this patch, and it did not visibly help.

Thanks for the help, let me know if you'd like me to try anything else.

Take care,
     Dale
-- 
Dale E. Martin, Clifton Labs, Inc.
Senior Computer Engineer
dmartin@cliftonlabs.com
http://www.cliftonlabs.com
pgp key available

  parent reply	other threads:[~2003-09-03 12:41 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
2003-09-03 12:41                 ` Dale E Martin [this message]
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=20030903124131.GA842@cliftonlabs.com \
    --to=dmartin@cliftonlabs.com \
    --cc=akpm@osdl.org \
    --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