All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: Mark Tiefenbruck <mark@fluxbox.org>
Cc: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: PROBLEM: Dell Inspiron 1501 fails to boot in 2.6.21+
Date: Thu, 02 Aug 2007 13:34:05 -0400	[thread overview]
Message-ID: <46B2158D.4000709@redhat.com> (raw)
In-Reply-To: <c96265a60707201937t39f9b69ep48e76ed61ce1044e@mail.gmail.com>

On 07/20/2007 10:37 PM, Mark Tiefenbruck wrote:
> I'd appreciate any help on getting this report sent to the appropriate
> list and, of course, getting this fixed. I don't know what's useful,
> so you're getting everything. This will be a very long e-mail.
> 
> My new laptop won't boot with kernel versions 2.6.21 or 2.6.22 . No
> oops. No panic. It just stops printing messages. Maybe it would
> eventually continue if I wait long enough, but it's unacceptable
> either way. I include below the contents of dmesg for a working kernel
> up to the point where it halts. I'm also including what it usually
> does for a few lines after that point.
> 

Does it continue booting if you keep pressing the Ctrl key repeatedly?

I have one that does, with kernel 2.6.23-rc1-git9 -- otherwise it just
sits there indefinitely. As soon as I press a key it continues. This is
even with 'nohz=off highres=off'.

Using 'nolapic_timer' (by itself) fixes it, though.


  parent reply	other threads:[~2007-08-02 17:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-21  2:37 PROBLEM: Dell Inspiron 1501 fails to boot in 2.6.21+ Mark Tiefenbruck
2007-07-21  2:53 ` Glauber de Oliveira Costa
2007-07-21 11:33 ` Thomas Gleixner
2007-07-22  4:56   ` Mark Tiefenbruck
2007-07-21 11:59 ` Ingo Molnar
2007-07-21 15:58   ` Daniel Walker
2007-07-22  8:36 ` Lexington Luthor
2007-08-02 17:34 ` Chuck Ebbert [this message]
     [not found] <1186302113.3264.3.camel@localhost.localdomain>
     [not found] ` <c96265a60708122156o4e355540v9a91c795f8c8c4bd@mail.gmail.com>
2007-08-13  4:57   ` Mark Tiefenbruck

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=46B2158D.4000709@redhat.com \
    --to=cebbert@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@fluxbox.org \
    --cc=tglx@linutronix.de \
    /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.