From: "Frédéric L. W. Meunier" <fredlwm@fredlwm.net>
To: 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 19:03:51 -0200 [thread overview]
Message-ID: <20121211210351.GB19943@pervalidus> (raw)
On Tue, Dec 11, 2012 at 20:16:47, Borislav Petkov wrote:
> What family is that? Can you give /proc/cpuinfo?
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 107
model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4000+
stepping : 1
cpu MHz : 1000.000
cache size : 512 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good nopl extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch lbrv
bogomips : 2004.56
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc 100mhzsteps
processor : 1
vendor_id : AuthenticAMD
cpu family : 15
model : 107
model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4000+
stepping : 1
cpu MHz : 1000.000
cache size : 512 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good nopl extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch lbrv
bogomips : 2004.56
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc 100mhzsteps
>> 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?
It always happens when I compile MPlayer. It was always cc1, but yasm
once.
>> 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.
I'll see what I can do. I'm compiling with -j3, so it's hard to see
before the kernel reports it.
next reply other threads:[~2012-12-11 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 21:03 Frédéric L. W. Meunier [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=20121211210351.GB19943@pervalidus \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.