From: Andi Kleen <ak@suse.de>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH -ac] Panicking in morse code v3
Date: 21 Jul 2002 11:29:06 +0200 [thread overview]
Message-ID: <p73u1mttonx.fsf@oldwotan.suse.de> (raw)
In-Reply-To: Russell King's message of "21 Jul 2002 11:10:18 +0200"
Russell King <rmk@arm.linux.org.uk> writes:
> Hmm. I thought the original idea for the "flash LEDs on panic" was
> so you knew something had gone wrong early in the boot, at the kind
> of places where you don't have a console initialised. If you don't
> have the console initialised, you sure as hell don't have the input
> layer or keyboard drivers initialised.
[having written the original code...]
The idea was to distingush panic from lockup when you are in X and cannot
see the console and X is dead so you cannot switch to the console.
Handling early panic is probably better done by an "early console", like
x86-64 supports one.
-Andi
next prev parent reply other threads:[~2002-07-21 9:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020719011300.548d72d5.arodland@noln.com.suse.lists.linux.kernel>
2002-07-19 10:38 ` [PATCH -ac] Panicking in morse code Andi Kleen
2002-07-20 7:05 ` Ville Herva
2002-07-20 11:49 ` Neale Banks
2002-07-20 11:55 ` Thunder from the hill
[not found] ` <20020720173222.3286fcbb.arodland@noln.com.suse.lists.linux.kernel>
[not found] ` <200207211849.56076.bhards@bigpond.net.au.suse.lists.linux.kernel>
[not found] ` <20020721100818.A22176@flint.arm.linux.org.uk.suse.lists.linux.kernel>
2002-07-21 9:29 ` Andi Kleen [this message]
2002-07-19 5:13 Andrew Rodland
2002-07-20 21:32 ` [PATCH -ac] Panicking in morse code v3 Andrew Rodland
2002-07-21 8:49 ` Brad Hards
2002-07-21 9:08 ` Russell King
2002-07-21 10:50 ` Zwane Mwaikambo
2002-07-21 15:43 ` Daniel Phillips
2002-07-22 17:18 ` Andrew Rodland
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=p73u1mttonx.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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
Powered by JetHome