On Wed, 18 Oct 2000, Gary E. Miller wrote:
> Yo Mike!
>
> On Wed, 18 Oct 2000, Mike Galbraith wrote:
>
> > > Help! See below for my kernel oops. I have not been able to use any
> > > kernel after 2.4.0-test5 due to this problem. It happens shortly
> > > after booting the kernel and is very repeatable.
>
> > Are you sure that you used the right System.map?
> Yes, I just rechecked the date and time of all the files. I will
> re-run the whole test in the morning just to be sure.
>
> > > Trace; c01df362 <scsi_dispatch_cmd+1c6/26c>
> > ^^^
> > Here, scsi_dispatch_cmd() isn't that large.. it's only 0x168 in size.
> Mine is 0x26c, maybe you have a different compiler or different config?
Ok, I don't _see_ what could make such a big difference, but something
obviously does.
> > If you want to try some light troubleshooting, grab kdb..
> > ftp://oss.sgi.com/www/projects/kdb/download/ix86/kdb-v1.5-2.4.0-test9-pre9.gz
> > .. and check what both cpus were up to at lock time. A stack trace of
> > both cpus might help developers locate the trouble.
>
> I thought Linus was not a big fan of kernel debuggers? I will look into
> it if I get no better suggestions.
Linus doesn't need a supporter (nads of steel;), but the vast majority
of folks out there aren't in the same league as Linus. Heck, some of
us aren't even sure we're playing the same sport.
-Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
