Re: [OOPS, usbcore, releaseintf] 2.6.0-test10-mm1

[Vince]

Duncan Sands wrote:
> > > That explains why this relatively harmless Oops was
> > > freezing Vince's box.  I guess he should turn it off.
> >
> > Well, I don't find this oops harmless at all : my box is usually
> > freezing while in a huge number of other oopses that directly follow this one,
> > and then nothing makes it into the logs. I had to set this sysctl once
> > in order to get the first oops, but that's not related to the other
> > freeze...
>
>
> What is the second Oops?

No idea... without the sysctl, the screen keeps scrolling printing new 
oopes (49 of them in my last attempt), in which case nothing about it 
ever reaches the disk log (and it looks like the kernel buffer is too 
short when using kmsgdump).
 Could it be possible to have something like:
echo 2 > /proc/sys/kernel/panic_on_oops
...and have the system panic at the 2nd oops ?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/