From: john@grabjohn.com
To: jpo234@netscape.net, pavel@ucw.cz
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dead machine, blinking Keyboard and no Oops on console
Date: Tue, 27 May 2003 15:12:44 +0100 [thread overview]
Message-ID: <200305271412.h4RECibF000738@81-2-122-30.bradfords.org.uk> (raw)
> > > Blinking keyboard lights means kernel panic.
> > Shouldn't a panic cause some message on the console?
> > Does the missing message provide a clue?
> I'd go for serial console at this point...
...or the morse code output patch...
John.
next reply other threads:[~2003-05-27 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 14:12 john [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-23 19:33 Dead machine, blinking Keyboard and no Oops on console jpo234
2003-05-25 21:52 ` Pavel Machek
2003-05-23 19:11 jpo234
2003-05-23 19:24 ` Jeff Garzik
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=200305271412.h4RECibF000738@81-2-122-30.bradfords.org.uk \
--to=john@grabjohn.com \
--cc=jpo234@netscape.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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).