From: Richard A Nelson <cowboy@vnet.ibm.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.1ac20
Date: Fri, 23 Feb 2001 10:12:33 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.33.0102231005220.2402-100000@badlands.lexington.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0102211815210.2261-100000@badlands.lexington.ibm.com>
On Wed, 21 Feb 2001, Richard A Nelson wrote:
> On Wed, 21 Feb 2001, Alan Cox wrote:
>
> >
> > Can you stick an if(dev!=NULL) in front of that and let me know if that
> > fixes it - just to verify thats the problem spot
>
> Compiling now, will reboot in the am (if it aint done soon) -
> don't want it rebooting all night if this isn't it ;-}
Sigh, it appears that the problem is actually neither of the above
lines.
I even tried 2.4.2 and had the same problem, then I noticed that 2.4.2
also contains the same update ;-}
I put an if(dev == NULL)printk...else in both spots and rebooted.
Then (I gotta start drinking more coffee, or increase Copenhagen
intake), I noticed that the actual oops is from modprobe!!!!
I've not been able to get a oops trace because the error either causes
a reboot, or hang (either case, e2fsck is run at reboot).
Heres some system info that might be useful:
Kernel modules 2.4.2
Gnu C 2.95.3
Gnu Make 3.79.1
Binutils 2.10.91.0.2
Linux C Library 2.2.2
Dynamic linker ldd (GNU libc) 2.2.2
Procps 2.0.7
Mount 2.10s
Net-tools 2.05
Console-tools 0.2.3
Sh-utils 2.0.11
I'll be happy to reboot and capture the oops, if someone can help me
make sure it gets logged (serial console not a possibility, the other
box is currently in pieces).
--
Rick Nelson
Life'll kill ya -- Warren Zevon
Then you'll be dead -- Life'll kill ya
next prev parent reply other threads:[~2001-02-23 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 0:16 Linux 2.4.1ac20 Alan Cox
2001-02-21 23:06 ` Richard A Nelson
2001-02-21 23:13 ` Alan Cox
2001-02-21 23:17 ` Richard A Nelson
2001-02-23 15:12 ` Richard A Nelson [this message]
2001-02-27 18:50 ` olympic (tokenring) & IPv6 (was Re: Linux 2.4.1ac20) Richard A Nelson
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=Pine.LNX.4.33.0102231005220.2402-100000@badlands.lexington.ibm.com \
--to=cowboy@vnet.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).