linux-kernel - Re: BUG: soft lockup with 3.7.0 but not 3.6.10

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] [day] [month] [year] [list]

Date:	Tue, 11 Dec 2012 21:16:47 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Frédéric L. W. Meunier <fredlwm@...dlwm.net>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: BUG: soft lockup with 3.7.0 but not 3.6.10

On Tue, Dec 11, 2012 at 07:36:36PM -0200, Frédéric L. W. Meunier wrote:
> While compiling MPlayer git on 3.7.0, I noticed the attached messages. I 
> then compiled 3.6.10, without any message being printed by the kernel, 
> and thought it could be due to MPlayer being compiled on tmpfs, while 
> the kernel on ext4. But compiling MPlayer on ext4 didn't change 
> anything.
> 
> I booted on 3.6.10 and couldn't reproduce it.
> 
> According to 'free', swap isn't used at all during the compilation.
> 
> I'm also attaching my .config.
> 
> It's an Athlon 64 X2 Dual Core Processor 4000+ with 2Gb of DDR2.

What family is that? Can you give /proc/cpuinfo?

> Dec 11 16:02:15 pervalidus kernel: [11260.096015] BUG: soft lockup - CPU#1 stuck for 22s! [cc1:20906]

Hmm, this says that gcc gets stuck at some point. Is this always
reproducible on 3.7?

What about using another version of gcc, can you repro it then too?

It would be interesting to know where all those cc1 processes get stuck.
Can you break into them with gdb and dump the code around RIP everytime
those tasks gets stuck? Try doing a couple of them to see whether it is
repeatable.

Thanks.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/