mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Dave Jones <davej@redhat.com>
Cc: davej@codemonkey.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [patch] halt_on_oops command line option
Date: Wed, 18 Jan 2006 23:59:58 -0800	[thread overview]
Message-ID: <20060118235958.6b466a86.akpm@osdl.org> (raw)
In-Reply-To: <20060119073951.GC21663@redhat.com>

Dave Jones <davej@redhat.com> 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.

We could make the boot option be number-of-seconds-to-pause I guess.  Do
you think it's really worth it?

  reply	other threads:[~2006-01-19  8:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-19  7:22 Andrew Morton
2006-01-19  7:39 ` Dave Jones
2006-01-19  7:59   ` Andrew Morton [this message]
2006-01-19 19:26     ` Dave Jones
2006-01-19 23:18       ` Andrew Morton
2006-01-19 23:24         ` Randy.Dunlap
2006-01-19 23:40           ` Andrew Morton

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=20060118235958.6b466a86.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=davej@codemonkey.org.uk \
    --cc=davej@redhat.com \
    --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

all inboxes | Powered by JetHome®