On Wed, Jan 18, 2006 at 11:59:58PM -0800, Andrew Morton wrote:
> Dave Jones <[email protected]> wrote:
> >
> > On Wed, Jan 18, 2006 at 11:22:55PM -0800, Andrew Morton wrote:
> > >
> > > How's this look?
> > > Attempt to fix the problem wherein people's oops reports scroll off the screen
> > > due to repeated oopsing or to oopses on other CPUs.
> > >
> > > If this happens the user can reboot with the `halt_on_oops' option. It will
> > > allow the first oopsing CPU to print an oops record just a single time. Second
> > > oopsing attempts, or oopses on other CPUs will cause those CPUs to enter a
> > > tight loop.
> >
> > seems a bit aggressive for UP. Now if my sound driver oopses, I don't
> > just lose sound, I lock up. (That's why I made it a pause, not a halt
> > in my earlier patch).
> >
>
> Well I'm assuming people would only enable the option if they are
> experiencing persistently-scrolling-off oopses.
For this to be useful for me, I'd want it always on. The majority of
oopses our users hit are one offs, and they don't usually know when
they're going to get an oops ;-)
> We could make the boot option be number-of-seconds-to-pause I guess. Do
> you think it's really worth it?
Beats locking up indefinitly on UP.
Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
