All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Oeser <netdev@axxeo.de>
To: Andi Kleen <ak@suse.de>
Cc: Meelis Roos <mroos@linux.ee>,
	kernel list <linux-kernel@vger.kernel.org>,
	netdev@vger.kernel.org
Subject: Re: Safe remote kernel install howto (Re: [Bugme-new] [Bug 6613] New: iptables broken on 32-bit PReP (ARCH=ppc))
Date: Fri, 26 May 2006 15:21:53 +0200	[thread overview]
Message-ID: <200605261521.53884.netdev@axxeo.de> (raw)
In-Reply-To: <200605261442.32319.ak@suse.de>

Hi Andi,

Andi Kleen wrote:
> > 4. Put "sysctl -w kernel.panic_on_oops=1" as early as possible
> >      in your boot scripts[1].
> 
> You can as well boot with oops=panic

Only on x86_64 as of Linux 2.6.16.
But maybe this could be put into kernel/panic.c instead :-)

Regards

Ingo Oeser

  reply	other threads:[~2006-05-26 13:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200605251004.k4PA4Lek007751@fire-2.osdl.org>
2006-05-25 14:03 ` [Bugme-new] [Bug 6613] New: iptables broken on 32-bit PReP (ARCH=ppc) Andrew Morton
2006-05-25 18:52   ` Patrick McHardy
2006-05-25 19:12     ` Meelis Roos
2006-05-25 20:15     ` Meelis Roos
2006-05-26  7:11     ` Meelis Roos
2006-05-26 12:29       ` Safe remote kernel install howto (Re: [Bugme-new] [Bug 6613] New: iptables broken on 32-bit PReP (ARCH=ppc)) Ingo Oeser
2006-05-26 12:34         ` Meelis Roos
2006-05-31 20:25           ` Bill Davidsen
2006-05-26 12:42         ` Michael Tokarev
2006-05-26 12:42         ` Andi Kleen
2006-05-26 13:21           ` Ingo Oeser [this message]
2006-06-01  7:03     ` [Bugme-new] [Bug 6613] New: iptables broken on 32-bit PReP (ARCH=ppc) Meelis Roos
2006-06-01 17:44       ` Patrick McHardy
2006-06-01 20:50         ` Meelis Roos
2006-06-02 13:08           ` Patrick McHardy
2006-06-02 13:18             ` Meelis Roos
2006-06-02 13:56               ` Patrick McHardy
2006-06-04 12:39                 ` Meelis Roos

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=200605261521.53884.netdev@axxeo.de \
    --to=netdev@axxeo.de \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    --cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.