public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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
Date: Sat, 16 Oct 2004 00:14:45 -0700	[thread overview]
Message-ID: <20041016001445.41cbd2db.akpm@osdl.org> (raw)
In-Reply-To: <4170C946.5020800@lbsd.net>

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.

  parent reply	other threads:[~2004-10-16  7:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-15 13:36 2.6.9-rc4-bk2 bug report Nigel Kukard
2004-10-16  5:53 ` Andrew Morton
     [not found]   ` <4170C946.5020800@lbsd.net>
2004-10-16  7:14     ` Andrew Morton [this message]
2004-10-17  9:42       ` Nigel Kukard

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=20041016001445.41cbd2db.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nkukard@lbsd.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