From: Andrew Morton <akpm@osdl.org>
To: Horms <horms@verge.net.au>
Cc: chris@zankel.net, tony.luck@intel.com,
linux-ia64@vger.kernel.org, discuss@x86-64.org, ak@suse.de,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
paulus@samba.org, anton@samba.org, rmk@arm.linux.org.uk
Subject: Re: [PATCH] panic_on_oops: remove ssleep()
Date: Mon, 17 Jul 2006 17:23:41 -0700 [thread overview]
Message-ID: <20060717172341.6d49f109.akpm@osdl.org> (raw)
In-Reply-To: <20060717231056.GC12463@verge.net.au>
On Mon, 17 Jul 2006 19:10:59 -0400
Horms <horms@verge.net.au> wrote:
> On Tue, Jul 18, 2006 at 12:27:51AM +0200, Andi Kleen wrote:
> > On Monday 17 July 2006 18:17, Horms wrote:
> > ...
> > Keeping the delay might be actually useful so that you can see the panic
> > before system reboots when reboot on panic is enabled. I would just use a loop
> > of mdelays(1) with touch_nmi_watchdog/touch_softirq_watchdog()s
> > inbetween.
>
> Ok, I will look into making that happen. I agree that the pause is
> quite useful.
It's kind-of already implemented, via pause_on_oops. Perhaps doing
something like
if (panic_on_oops)
pause_on_oops = max(pause_on_oops, 5*HZ);
would be sufficient.
next prev parent reply other threads:[~2006-07-18 0:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 16:17 [PATCH] panic_on_oops: remove ssleep() Horms
2006-07-17 22:27 ` Andi Kleen
2006-07-17 23:10 ` Horms
2006-07-18 0:23 ` Andrew Morton [this message]
2006-07-18 19:13 ` Horms
2006-07-20 16:03 ` Paul Mackerras
-- strict thread matches above, loose matches on Subject: below --
2006-07-18 1:22 Chuck Ebbert
2006-07-18 19:15 ` Horms
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=20060717172341.6d49f109.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@suse.de \
--cc=anton@samba.org \
--cc=chris@zankel.net \
--cc=discuss@x86-64.org \
--cc=horms@verge.net.au \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=rmk@arm.linux.org.uk \
--cc=tony.luck@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).