Date: Thu, 19 Jan 2006 02:39:51 -0500
From: Dave Jones <davej@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Dave Jones <davej@codemonkey.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [patch] halt_on_oops command line option
Message-ID: <20060119073951.GC21663@redhat.com>
Mail-Followup-To: Dave Jones <davej@redhat.com>,
	Andrew Morton <akpm@osdl.org>, Dave Jones <davej@codemonkey.org.uk>,
	linux-kernel@vger.kernel.org
References: <20060118232255.3814001b.akpm@osdl.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060118232255.3814001b.akpm@osdl.org>
User-Agent: Mutt/1.4.2.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 902
Lines: 22

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).

		Dave

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