mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: davej@redhat.com, davej@codemonkey.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [patch] halt_on_oops command line option
Date: Thu, 19 Jan 2006 15:40:28 -0800	[thread overview]
Message-ID: <20060119154028.4f1347c5.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0601191520480.11660@shark.he.net>

"Randy.Dunlap" <rdunlap@xenotime.net> wrote:
>
> On Thu, 19 Jan 2006, Andrew Morton wrote:
> 
> > diff -puN Documentation/kernel-parameters.txt~pause_on_oops-command-line-option Documentation/kernel-parameters.txt
> > --- 25/Documentation/kernel-parameters.txt~pause_on_oops-command-line-option	Thu Jan 19 14:42:25 2006
> > +++ 25-akpm/Documentation/kernel-parameters.txt	Thu Jan 19 14:51:35 2006
> > @@ -544,6 +544,11 @@ running once the system is up.
> >
> >  	gvp11=		[HW,SCSI]
> >
> > +	pause_on_oops=
> > +			Halt all CPUs after the first oops has been printed for
> > +			the specified number of seconds.  This is to be used if
> > +			your oopses keep scrolling off the screen.
> > +
> >  	hashdist=	[KNL,NUMA] Large hashes allocated during boot
> >  			are distributed across NUMA nodes.  Defaults on
> >  			for IA-64, off otherwise.
> 
> Why there?

Coz I did s/halt_on_oops/pause_on_oops/ on the original patch ;)

      reply	other threads:[~2006-01-19 23:39 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
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 [this message]

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=20060119154028.4f1347c5.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=davej@codemonkey.org.uk \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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®