lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1306426675.2497.84.camel@laptop>
Date:	Thu, 26 May 2011 18:17:55 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Laurent Riffard <laurent.riffard@...e.fr>
Cc:	netdev@...r.kernel.org
Subject: Re: [BUG] netconsole broken by scheduler updates

On Thu, 2011-05-26 at 18:12 +0200, Laurent Riffard wrote:
> 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@...llo.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.

OK, thanks for trying, I shall try and reproduce locally.


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ