From: Laurent Riffard <laurent.riffard@free•fr>
To: Peter Zijlstra <a.p.zijlstra@chello•nl>
Cc: netdev@vger•kernel.org
Subject: Re: [BUG] netconsole broken by scheduler updates
Date: Thu, 26 May 2011 18:12:27 +0200 [thread overview]
Message-ID: <4DDE7BEB.1050507@free.fr> (raw)
In-Reply-To: <alpine.DEB.2.02.1105261217240.5114@localhost6.localdomain6>
Le 26/05/2011 12:35, Laurent Riffard a écrit :
> On Thu, 26 May 2011, Peter Zijlstra wrote:
>> On Thu, 2011-05-26 at 11:21 +0200, Laurent Riffard wrote:
>>> Hi,
>>>
>>> Recently, netconsole was broken by some scheduler updates. Kernel hangs
>>> on boot near the network card initialization. I noticed that it does
>>> hang just where a "inconsistent lock state" message normally appears.
>>>
>>> I did a bisection : e4a52bcb9a18142d79e231b6733cabdbf2e67c1f is the
>>> first bad commit.
>>> commit e4a52bcb9a18142d79e231b6733cabdbf2e67c1f
>>> Author: Peter Zijlstra <a.p.zijlstra@chello•nl>
>>> Date: Tue Apr 5 17:23:54 2011 +0200
>>>
>>> sched: Remove rq->lock from the first half of ttwu()
>>>
>>>
>>> Before this commit, kernel was booting succesfully despite the
>>> "inconsistent lock state" message. After this commit, the kernel does
>>> hang on boot, I have to push the reset button.
>>
>> Do you have CONFIG_HARDLOCKUP_DETECTOR=y, and do you get an NMI splat
>> after some 10 seconds? It would be interesting to see where its stuck.
>
> CONFIG_HARDLOCKUP_DETECTOR is not set for now. I'll give it a try.
I activated CONFIG_HARDLOCKUP_DETECTOR, but failed to obtain more
information. During the boot, the kernel hangs just after bringing up
the NIC. I waited 2 minutes, without getting any more messages.
~~
laurent
next prev parent reply other threads:[~2011-05-26 16:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 9:21 [BUG] netconsole broken by scheduler updates Laurent Riffard
2011-05-26 9:48 ` Peter Zijlstra
2011-05-26 10:35 ` Laurent Riffard
2011-05-26 16:12 ` Laurent Riffard [this message]
2011-05-26 16:17 ` Peter Zijlstra
2011-06-03 21:15 ` Laurent Riffard
2011-05-26 20:18 ` David Miller
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=4DDE7BEB.1050507@free.fr \
--to=laurent.riffard@free$(echo .)fr \
--cc=a.p.zijlstra@chello$(echo .)nl \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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