From: Peter Zijlstra <peterz@infradead.org>
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 16:39:11 +0200 [thread overview]
Message-ID: <1184337551.20032.89.camel@twins> (raw)
In-Reply-To: <6d4bc9fc0707130702l41f58c20l72423be27292d884@mail.gmail.com>
On Fri, 2007-07-13 at 16:02 +0200, 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.
>
> I have included the config file that does work (so dynticks and
> hr_timers are disabled).
>
> Please CC any replies, as i am not a member of this mailinglist.
Try -rt3, that solved this issue for me.
next prev parent reply other threads:[~2007-07-13 14:39 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 [this message]
2007-07-14 10:49 ` Maarten Maathuis
2007-07-14 10:56 ` Peter Zijlstra
2007-07-13 15:04 ` Mark Lord
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=1184337551.20032.89.camel@twins \
--to=peterz@infradead.org \
--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