From: "Jike Song" <albcamus@gmail.com>
To: Chr <chunkeey@web.de>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>,
venkatesh.pallipadi@intel.com, "Ingo Molnar" <mingo@elte.hu>,
"Thomas Gleixner" <tglx@linutronix.de>,
len.brown@intel.com
Subject: Re: endless loop in native_flush_tlb_others in smp_64.c
Date: Tue, 11 Mar 2008 17:55:40 +0800 [thread overview]
Message-ID: <df9815e70803110255s1c8323a8xf05b132ecc406bd0@mail.gmail.com> (raw)
In-Reply-To: <200803102316.54457.chunkeey@web.de>
CC added
On Tue, Mar 11, 2008 at 6:16 AM, Chr <chunkeey@web.de> wrote:
> Hi,
Hi Chr,
>
> ever since I moved to 2.6.25-rcY (Y should be between 2 and 5!).
> I've seen several, but really hard-to-catch instant freezes on my
> AMD64 Athlon X2 4200+ system...
Here I guess 2.6.24 is fine for you?
>
> Most of them happend in X.org so at first I thought it had something to do
> with the NVIDIA module... BUT, one time it froze "a way before" the module
> could get loaded (and desynced my raid.......).
>
> ---
> SYSRQ-P revealed that the CPU were looping inside:
>
> smp_64.c native_flush_tlb_others:
> assembler code:
> < 1ee: f3 90 pause
> < 1f0: f6 45 00 03 testb $0x3,0x0(%rbp)
> < 1f4: 75 f8 jne 1ee <native_flush_tlb_others+0x5f>
>
> also known as: (in C)
>
> while (!cpus_empty(f->flush_cpumask))
> cpu_relax();
>
> So... has anyone a good idea what's happening here exactly? Or is there
> already another topic or even a patch available?
>
> Regards,
> Chr.
> --
Would you please attach your config file? Do you have CONFIG_CPU_IDLE set?
Regards,
next prev parent reply other threads:[~2008-03-11 9:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 22:16 Chr
2008-03-11 9:55 ` Jike Song [this message]
2008-03-11 10:30 ` Chr
2008-03-11 14:01 ` Pallipadi, Venkatesh
2008-03-11 21:43 ` Chr
2008-03-11 11:09 ` Thomas Gleixner
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=df9815e70803110255s1c8323a8xf05b132ecc406bd0@mail.gmail.com \
--to=albcamus@gmail.com \
--cc=chunkeey@web.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
/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
all inboxes | Powered by JetHome®