From: Borislav Petkov <bp@alien8.de>
To: "Frédéric L. W. Meunier" <fredlwm@fredlwm.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: BUG: soft lockup with 3.7.0 but not 3.6.10
Date: Tue, 11 Dec 2012 21:16:47 +0100 [thread overview]
Message-ID: <20121211201647.GD8873@liondog.tnic> (raw)
In-Reply-To: <20121211213636.GA19943@pervalidus>
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.
--
next prev parent reply other threads:[~2012-12-11 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 21:36 BUG: soft lockup with 3.7.0 but not 3.6.10 Frédéric L. W. Meunier
2012-12-11 20:16 ` Borislav Petkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-12-11 21:03 Frédéric L. W. Meunier
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=20121211201647.GD8873@liondog.tnic \
--to=bp@alien8.de \
--cc=fredlwm@fredlwm.net \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox