From: "Dale E Martin" <dmartin@cliftonlabs.com>
Date: Wed, 3 Sep 2003 08:41:31 -0400
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)
Message-ID: <20030903124131.GA842@cliftonlabs.com>
References: <20030902123050.GA854@cliftonlabs.com> <20030902130323.41d2fdca.akpm@osdl.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030902130323.41d2fdca.akpm@osdl.org>
User-Agent: Mutt/1.5.4i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1544
Lines: 40

> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/