From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Willy Tarreau <willy@w.ods.org>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Flashing keyboard LEDS upon boot.
Date: Wed, 4 Feb 2004 09:19:02 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.53.0402040912480.4254@chaos> (raw)
In-Reply-To: <20040203231352.GA29363@alpha.home.local>
On Wed, 4 Feb 2004, Willy Tarreau wrote:
> Hi Dick,
>
> On Mon, Feb 02, 2004 at 11:06:50AM -0500, Richard B. Johnson wrote:
> > > Sometimes, when booting Linux-2.3.24 from bzImage, machines
> > ^
> > Typo Linux-2.4.24
> >
> > > display "Uncompressing Linux ..., Ok. Booting the kernel."
> > > Then the machine just sits there with the keyboard LEDS
> > > (Num-Lock, Caps-lock, and Scroll-lock) flashing at about
> > > a 1-second interval. It will do this "forever".
>
> Flashing leds indicate a kernel panic on recent kernels (was in -ac for
> a while).
>
> > > Can anybody tell me what it has found "wrong" that prevents
> > > it from continuing the boot? A whole bunch of new Dell Computers
> > > display this problem. The second boot will always work, but
> > > the first cold-start boot will often result in this problem.
>
> Hmmm. perhaps ACPI or a broken driver ?
>
> Cheers,
> Willy
>
Well I modified the kernel to write 0 to the printer port
when it starts uncompressing the RAM disk and subsequent
numbers after. It never gets beyond 1, which means it crashed
immediately after or during the printing of "OK. Booting the
kernel"
Cheers,
Dick Johnson
Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2004-02-04 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 15:55 Richard B. Johnson
2004-02-02 16:06 ` Richard B. Johnson
2004-02-03 23:13 ` Willy Tarreau
2004-02-04 14:19 ` Richard B. Johnson [this message]
[not found] <BF1FE1855350A0479097B3A0D2A80EE0023E85DF@hdsmsx402.hd.intel.com>
2004-02-04 8:21 ` Len Brown
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=Pine.LNX.4.53.0402040912480.4254@chaos \
--to=root@chaos.analogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@w.ods.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®