From: Mark Lord <lkml@rtr.ca>
To: tglx@linutronix.de
Cc: Daniel Walker <dwalker@mvista.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [BUG] 2.6.21: Kernel won't boot with either/both of CONFIG_NO_HZ, CONFIG_HIGH_RES_TIMERS
Date: Tue, 01 May 2007 12:52:37 -0400 [thread overview]
Message-ID: <46377055.2060605@rtr.ca> (raw)
In-Reply-To: <1178035058.5791.333.camel@localhost.localdomain>
Thomas Gleixner wrote:
> On Tue, 2007-05-01 at 10:13 -0400, Mark Lord wrote:
>> Of possible interest is that the bottom of the 25line screen capture
>> differs somewhat from the 50line capture.. see for yourself.
>> This is 100% consistent from boot to boot.
>>
>> Using CONFIG_DETECT_SOFTLOCKUP=y eliminates the problem,
>> so that's really got to be a huge clue, somehow ?
>
> I twisted my brain, why the watchdog thread might change the problem and
> I think I have a rough idea of the scenario.
>
> Can you apply the following patch, which prints out the CPU on which the
> kernel messages are generated and upload the screenshot when the hang
> happens ? Oh, please enable CONFIG_PRINTK_TIME or add "time" to the
> kernel commandline.
Done, and done.
And I managed to capture more of the boot messages, too.
This new capture is in the "sequence" subdir at the previous link.
Cheers
next prev parent reply other threads:[~2007-05-01 16:52 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 20:17 [BUG] 2.6.21: Kernel won't boot with either/both of CONFIG_NO_HZ, CONFIG_HIGH_RES_TIMERS Mark Lord
2007-04-30 20:19 ` Mark Lord
2007-04-30 20:37 ` Mark Lord
2007-04-30 23:36 ` Mark Lord
2007-04-30 23:45 ` Thomas Gleixner
2007-04-30 23:46 ` Daniel Walker
2007-05-01 0:02 ` Mark Lord
2007-05-01 0:07 ` Michal Piotrowski
2007-05-01 0:11 ` Mark Lord
2007-05-01 0:13 ` Daniel Walker
2007-05-01 3:33 ` Mark Lord
2007-05-01 4:32 ` Daniel Walker
2007-05-01 4:34 ` Daniel Walker
2007-05-01 13:34 ` Thomas Gleixner
2007-05-01 13:33 ` Mark Lord
2007-05-01 13:34 ` Mark Lord
2007-05-01 13:48 ` Thomas Gleixner
2007-05-01 14:13 ` Mark Lord
2007-05-01 14:26 ` Michal Piotrowski
2007-05-01 14:41 ` Mark Lord
2007-05-01 15:24 ` Thomas Gleixner
2007-05-01 16:31 ` Mark Lord
2007-05-01 16:42 ` Daniel Walker
2007-05-01 15:57 ` Thomas Gleixner
2007-05-01 16:52 ` Mark Lord [this message]
2007-05-02 7:47 ` Thomas Gleixner
2007-05-02 8:05 ` Andrew Morton
2007-05-02 12:53 ` Mark Lord
2007-05-02 15:40 ` Thomas Gleixner
2007-05-02 22:29 ` Mark Lord
2007-05-02 22:41 ` Thomas Gleixner
2007-05-03 2:29 ` Mark Lord
2007-05-08 18:46 ` 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=46377055.2060605@rtr.ca \
--to=lkml@rtr.ca \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@osdl.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 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.