From: "Cyrill Gorcunov" <gorcunov@gmail.com>
To: "Adrian Bunk" <bunk@kernel.org>,
"Sitsofe Wheeler" <sitsofe@yahoo.com>,
linux-kernel@vger.kernel.org, kernel-testers@vger.kernel.org,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@elte.hu>
Subject: Re: [REGRESSION][BISECTED][X86] next-20080526 hangs on boot
Date: Wed, 28 May 2008 07:21:43 +0400 [thread overview]
Message-ID: <aa79d98a0805272021v7cc73d26p9714d0c5b0b9fc77@mail.gmail.com> (raw)
In-Reply-To: <20080527225042.GG11310@cs181133002.pp.htv.fi>
Hi,
thanks a lot for checking this!
I'll take a look today evening.
On 5/28/08, Adrian Bunk <bunk@kernel.org> wrote:
> On Tue, May 27, 2008 at 10:35:43AM +0400, Cyrill Gorcunov wrote:
>> On 5/26/08, Sitsofe Wheeler <sitsofe@yahoo.com> wrote:
>> > <posted & mailed>
>> >
>> > Sitsofe Wheeler wrote:
>> >
>> > > Cyrill Gorcunov wrote:
>> > >
>> > >> [Sitsofe Wheeler - Mon, May 26, 2008 at 03:04:54PM +0100]
>> > >> | When using a 32 bit linux-next-20080526 the bootup process will
>> > >> hang at
>> > >> | a random point (not even sysrq helps) with no additional output on
>> > >> the
>> > >> | screen (whereas linux-next-20080523 did boot). Mysteriously,
>> > >> booting
>> > >> | with nmi_watchdog=2 allows the boot to finish (booting with
>> > >> | nmi_watchdog=1 still stalls). I have bisected it down to commit
>> > >> | [d1b946b97d71423f365fa797d1428e1847c0bec1]:
>> > >>
>> > >> Hi, so it helps by reverting only that commit? I mean all further
>> > >> commits
>> > >> are still appiled?
>> > >
>> > > Ah that I hadn't tested. I believe I might need to revert
>> > > 4b82b277707a39b97271439c475f186f63ec4692 too if later commits are
>> > > applied
>> > > (but I'm still testing)
>> > >
>> > >> and, btw, could you post your config, please?
>> > >
>> > > http://sucs.org/~sits/test/config-20080526.txt
>> >
>> > OK applying the following patch (which is more or less a revert of
>> > [4b82b277707a39b97271439c475f186f63ec4692]) resolves the problem:
>>...
>>
>> Hi Sitsofe, actually I can't imagine how this revert have helped you
>> from hang. Newly introduced nmi_watchdog_default() didn't change
>> the logic of the code being used before this merge-series.
>>
>> Thomas, Ingo, maybe I've overlooked something (hard to believe ;)?
>> Only the change is the adding of new call for nmi_watchdog_default()
>> which was say 'inlined' before.
>>...
>
> arch/x86/kernel/smpboot.c:native_smp_prepare_cpus() also calls
> the no longer empty nmi_watchdog_default() on 32bit.
>
> cu
> Adrian
>
> --
>
> "Is there not promise of rain?" Ling Tan asked suddenly out
> of the darkness. There had been need of rain for many days.
> "Only a promise," Lao Er said.
> Pearl S. Buck - Dragon Seed
>
>
prev parent reply other threads:[~2008-05-28 3:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 14:04 Sitsofe Wheeler
2008-05-26 14:41 ` Cyrill Gorcunov
2008-05-26 16:16 ` Cyrill Gorcunov
2008-05-26 19:11 ` Sitsofe Wheeler
2008-05-26 19:36 ` Sitsofe Wheeler
2008-05-26 19:44 ` Cyrill Gorcunov
2008-05-27 6:35 ` Cyrill Gorcunov
2008-05-27 22:16 ` Sitsofe Wheeler
2008-05-27 22:50 ` Adrian Bunk
2008-05-28 3:21 ` Cyrill Gorcunov [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=aa79d98a0805272021v7cc73d26p9714d0c5b0b9fc77@mail.gmail.com \
--to=gorcunov@gmail.com \
--cc=bunk@kernel.org \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sitsofe@yahoo.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®