LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Marcin Slusarz <marcin.slusarz@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.25-rc: complete lockup on boot/start of X (bisected)
Date: Sun, 2 Mar 2008 12:00:10 -0800	[thread overview]
Message-ID: <20080302120010.79d19405@laptopd505.fenrus.org> (raw)
In-Reply-To: <20080302185935.GA6100@joi>

On Sun, 2 Mar 2008 20:00:05 +0100
Marcin Slusarz <marcin.slusarz@gmail.com> wrote:

> Hi
> Since early 2.6.25 days I'm having strange lockup on boot. As it
> happens rarely (in ~10% of boots), I couldn't bisect it. No kernel
> panic, SysRq didn't work, so I couldn't provide any useful
> informations to LK community. I hoped someone else would fix it... :)
> 
> It's rc3 so I decided to narrow it down myself. I enabled netconsole 
> to see whether some other informations are printed before lockup.
> It didn't help, but I noticed that lockup happens much more
> frequenly! (~50%) So I bisected it down to:
> 
> 8f4d37ec073c17e2d4aa8851df5837d798606d6f is first bad commit
> commit 8f4d37ec073c17e2d4aa8851df5837d798606d6f
> Author: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Date:   Fri Jan 25 21:08:29 2008 +0100
> 
>     sched: high-res preemption tick
> 
>     Use HR-timers (when available) to deliver an accurate preemption
> tick.


the only unusual/suspect thing you have is nvidiafb driver; that's not very commonly used.
Can you do a quick try with that thing disabled? Maybe it has some races that are more likely
to trigger after this patch...


-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  parent reply	other threads:[~2008-03-02 20:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-02 19:00 Marcin Slusarz
2008-03-02 19:11 ` Peter Zijlstra
2008-03-02 19:47   ` Marcin Slusarz
2008-03-02 19:58     ` Peter Zijlstra
2008-03-23 15:44       ` Marcin Slusarz
2008-03-23 15:54         ` Peter Zijlstra
2008-03-23 18:46           ` Marcin Slusarz
2008-03-23 19:06             ` Peter Zijlstra
2008-03-23 19:09               ` Peter Zijlstra
2008-03-23 19:57                 ` Marcin Slusarz
2008-03-23 20:06               ` [PATCH] documentation: nmi_watchdog=2 works on x86_64 (was: 2.6.25-rc: complete lockup on boot/start of X (bisected)) Marcin Slusarz
2008-03-23 20:15                 ` Yinghai Lu
2008-03-27  9:51                 ` Ingo Molnar
2008-03-02 20:00 ` Arjan van de Ven [this message]
2008-03-02 20:08   ` 2.6.25-rc: complete lockup on boot/start of X (bisected) Marcin Slusarz

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=20080302120010.79d19405@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcin.slusarz@gmail.com \
    --cc=mingo@elte.hu \
    --subject='Re: 2.6.25-rc: complete lockup on boot/start of X (bisected)' \
    /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

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).