LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
To: <chunkeey@web.de>, "Jike Song" <albcamus@gmail.com>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>,
	"Ingo Molnar" <mingo@elte.hu>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Brown, Len" <len.brown@intel.com>
Subject: RE: endless loop in native_flush_tlb_others in smp_64.c
Date: Tue, 11 Mar 2008 07:01:56 -0700	[thread overview]
Message-ID: <924EFEDD5F540B4284297C4DC59F3DEEAF9755@orsmsx423.amr.corp.intel.com> (raw)
In-Reply-To: <200803111130.55355.chunkeey@web.de>

 

>-----Original Message-----
>From: chunkeey@web.de [mailto:chunkeey@web.de] 
>Sent: Tuesday, March 11, 2008 3:31 AM
>To: Jike Song
>Cc: Linux Kernel; Pallipadi, Venkatesh; Ingo Molnar; Thomas 
>Gleixner; Brown, Len
>Subject: Re: endless loop in native_flush_tlb_others in smp_64.c
>
>On Tuesday 11 March 2008 10:55:40 Jike Song wrote:
>> On Tue, Mar 11, 2008 at 6:16 AM, Chr <chunkeey@web.de> wrote:
>> > Hi,
>> >  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?
>Yes, 2.6.24(.3) is fine!
>
>> >  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...
>> >
>> >  ---
>> >  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?
>>
>> Would you please attach your config file?  Do you have 
>CONFIG_CPU_IDLE set?
>(Attached). Yes, CONFIG_CPU_IDLE is enabled! I guess I should 
>now disable it, 
>try again and report back, right?! ;-) 

I don't think it is related to CPU_IDLE. SYSRQ-T that Thomas asked
should give more clues.

Thanks,
Venki

  reply	other threads:[~2008-03-11 14:00 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
2008-03-11 10:30   ` Chr
2008-03-11 14:01     ` Pallipadi, Venkatesh [this message]
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=924EFEDD5F540B4284297C4DC59F3DEEAF9755@orsmsx423.amr.corp.intel.com \
    --to=venkatesh.pallipadi@intel.com \
    --cc=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 \
    --subject='RE: endless loop in native_flush_tlb_others in smp_64.c' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).