Date: Sat, 16 Oct 2004 00:14:45 -0700
From: Andrew Morton <akpm@osdl.org>
To: Nigel Kukard <nkukard@lbsd.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9-rc4-bk2 bug report
Message-Id: <20041016001445.41cbd2db.akpm@osdl.org>
In-Reply-To: <4170C946.5020800@lbsd.net>
References: <416FD24C.7020007@lbsd.net>
	<20041015225306.10bbbc69.akpm@osdl.org>
	<4170C946.5020800@lbsd.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1264
Lines: 40

Nigel Kukard <nkukard@lbsd.net> wrote:
>
> Andrew Morton wrote:
> 
> >Nigel Kukard <nkukard@lbsd.net> wrote:
> >  
> >
> >>While booting with 2.6.9rc4-bk2 I seem to get the below OOPS, I copied 
> >> the modules & System.map file over to another box of mine where i used 
> >> serial-console to grab the oops.
> >>
> >> Anyone know what I can try to debug the below problem?
> >>    
> >>
> >
> >I'd suggest that you strip your .config down to the bare minimum which is
> >needed to boot and see if the crash goes away.  If it does, then it's just
> >a matter of reintroducing .config options until you find which one caused
> >the crash.  Code inspection should then lead us to the bug.
> >  
> >
> 
> Could it be caused by loading a module?
> 

Yes.  Or by unloading a module.  The oops will happen some time _after_ the
buggy module has done its buggy thing.  Maybe you could change your
modprobe command to be:

	echo running modprobe $*
	modprobe.old $*
	sleep 5
	echo finished modprobe $*

or something like that.
-
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/