All of lore.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: Willy Tarreau <willy@w.ods.org>
Cc: "Richard B. Johnson" <root@chaos.analogic.com>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Flashing keyboard LEDS upon boot.
Date: 04 Feb 2004 03:21:26 -0500	[thread overview]
Message-ID: <1075882885.13728.2055.camel@dhcppc4> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE0023E85DF@hdsmsx402.hd.intel.com>

Richard,

Curious that the 2nd boot works...

In any case, if the kernel dies in the early ACPI table parsing code
you'd never get any console output -- so Willy may be right.

Let me know if the system boots with "acpi=off", but does not boot
without.

thanks,
-Len

On Tue, 2004-02-03 at 18:13, 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
> 
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
> 


       reply	other threads:[~2004-02-04  8:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BF1FE1855350A0479097B3A0D2A80EE0023E85DF@hdsmsx402.hd.intel.com>
2004-02-04  8:21 ` Len Brown [this message]
2004-02-02 15:55 Flashing keyboard LEDS upon boot 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

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=1075882885.13728.2055.camel@dhcppc4 \
    --to=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.com \
    --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 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.