public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Mark Tiefenbruck <mark@fluxbox.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Dell Inspiron 1501 fails to boot in 2.6.21+
Date: Sat, 21 Jul 2007 13:59:48 +0200	[thread overview]
Message-ID: <20070721115948.GA29178@elte.hu> (raw)
In-Reply-To: <c96265a60707201937t39f9b69ep48e76ed61ce1044e@mail.gmail.com>


* Mark Tiefenbruck <mark@fluxbox.org> wrote:

>  IO window: disabled.
>  MEM window: c0200000-c02fffff
>  PREFETCH window: disabled.
> PCI: Bridge: 0000:00:14.4
>  IO window: disabled.
>  MEM window: c0300000-c03fffff
>  PREFETCH window: disabled.
> PCI: Setting latency timer of device 0000:00:05.0 to 64
> PCI: Setting latency timer of device 0000:00:06.0 to 64
> NET: Registered protocol family 2
> 
> The next few lines are usually as follows, but recent kernels never 
> get to them:

thanks for the detailed report and bisection test! The above hang 
strongly implicates some sort of high-res timers, dynticks or 
clocksource problem. Most likely timer interrupts do not come as 
expected, and the above place is one of the first spots where the kernel 
waits for a (short) timeout - so you see it hang indefinitely.

Besides the options Thomas suggested, you could also try 
clocksource=pm_timer?

	Ingo

  parent reply	other threads:[~2007-07-21 12:00 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 [this message]
2007-07-21 15:58   ` Daniel Walker
2007-07-22  8:36 ` Lexington Luthor
2007-08-02 17:34 ` Chuck Ebbert
     [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=20070721115948.GA29178@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@fluxbox.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