From: Mark Lord <lkml@rtr.ca>
To: Maarten Maathuis <madman2003@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [realtime-preempt] [x86_64] HR_TIMER and/or DYNTICKS cause an early boot freeze
Date: Fri, 13 Jul 2007 11:04:35 -0400 [thread overview]
Message-ID: <46979483.2090502@rtr.ca> (raw)
In-Reply-To: <6d4bc9fc0707130702l41f58c20l72423be27292d884@mail.gmail.com>
Maarten Maathuis wrote:
> I have determined that version 2.6.22.1-rt2 freeze after:
>
> NET: Register protocol family 2
>
> This is very early in the boot stage, and i cannot determine what
> exactly causes it.
>
> It happens if either high resolution timers or dynamic ticks are active.
There's a race in there somewhere, and it seems to come and go
depending upon exactly how the kernel is configured, and possibly
on which things end up on which cache lines.
First reported by me here (below), and never resolved.
Currently it's not happening with my kernels, but it does reappear
from time to time:
> -------- Original Message --------
> Subject: [BUG] 2.6.21: Kernel won't boot with either/both of CONFIG_NO_HZ, CONFIG_HIGH_RES_TIMERS
> Date: Mon, 30 Apr 2007 16:17:00 -0400
> From: Mark Lord <lkml@rtr.ca>
> To: Linux Kernel <linux-kernel@vger.kernel.org>, tglx@linutronix.de
> CC: Linus Torvalds <torvalds@osdl.org>
>
> I have a new notebook (Dell Inspiron 9400) with Core2-Duo T7400 @ 2.1Ghz.
> When either/both of CONFIG_NO_HZ, CONFIG_HIGH_RES_TIMERS is used,
> the 2.6.21 kernel hangs on startup just after printing one/both of these:
>
> kernel: switched to high resolution mode on cpu 1
> kernel: switched to high resolution mode on cpu 0
>
> 100% of the time. The only fix I've found is to rebuild
> the kernel without those two options.
>
> The failed kernel.config is attached.
> Here is /proc/cpuinfo and lspci -v.
>
> Any help appreciated.
prev parent reply other threads:[~2007-07-13 15:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 14:02 [realtime-preempt] [x86_64] HR_TIMER and/or DYNTICKS cause an early boot freeze Maarten Maathuis
2007-07-13 14:39 ` Peter Zijlstra
2007-07-14 10:49 ` Maarten Maathuis
2007-07-14 10:56 ` Peter Zijlstra
2007-07-13 15:04 ` Mark Lord [this message]
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=46979483.2090502@rtr.ca \
--to=lkml@rtr.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=madman2003@gmail.com \
/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