> On Fri, 26 Mar 1999, Catalin BOIE wrote:
>
> > I didn't. This is all I see in that moment. You don't think this is
> > possible?!
>
> Find the place in the kernel that logs only a stack trace, then we'll talk
> some more about it.
>
> Your report lacks current program counter, stack values, register values,
> reason for the crash, etc. So yes it's worth precisely zilch.
I don't know if this is the same thing I saw in the 2.2.2pre2, but I
got a couple of weird OOPSen which had corrupted, partial OOPS reports
in the syslog. My OOPS problem seems to have gone away in 2.2.{2,3},
but there may be some conditions under which only part of the oops is
logged... in my case, I got a bunch of NULLs followed by the bottom
half of an OOPS in syslog. For reference, this was debian 2.1 as of
mid-Feb...
So un-harsh a bit-- maybe there is only half an OOPS. Catalin?
For reference, look for this message:
Subject: 2.2.2-pre2 lockups and partial(?) OOPS(?)
From: Mark Montague <monty@gg.caltech.edu>
Date: 19 Feb 1999 22:55:29 -0800
in the archives, if anyone wants to see my half-oops. It's in
kernel.9902.2 on the indiana list archive.
- M
-=-=-=-=-=-=-=-=-=-=-=+=-=-=-=-=-=-=-=-=-=-=-=+=-=-=-=-=-=-=-=-=-=-=-=-
Mark "Monty" Montague | monty@gg.caltech.edu | I don't do Windows(tm)
-=-=-=-=-=-=-=-=-=-=-=+=-=-=-=-=-=-=-=-=-=-=-=+=-=-=-=-=-=-=-=-=-=-=-=-
DON'T PANIC! I'm a trained professional, and far more | *Why* question
qualified to panic in this situation than you are. | authority?
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/