LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Jike Song <albcamus@gmail.com>
Cc: Chr <chunkeey@web.de>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	venkatesh.pallipadi@intel.com, Ingo Molnar <mingo@elte.hu>,
	len.brown@intel.com
Subject: Re: endless loop in native_flush_tlb_others in smp_64.c
Date: Tue, 11 Mar 2008 12:09:24 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.1.00.0803111205250.3781@apollo.tec.linutronix.de> (raw)
In-Reply-To: <df9815e70803110255s1c8323a8xf05b132ecc406bd0@mail.gmail.com>

On Tue, 11 Mar 2008, Jike Song wrote:
> >  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?

Any chance that you can capture SYSRQ-T output via serial or
netconsole, so we can see the stacktrace and what the other CPUs are
doing, if they are doing anything.

Thanks,
	tglx

      parent reply	other threads:[~2008-03-11 11:10 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
2008-03-11 21:43       ` Chr
2008-03-11 11:09   ` Thomas Gleixner [this message]

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=alpine.LFD.1.00.0803111205250.3781@apollo.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=albcamus@gmail.com \
    --cc=chunkeey@web.de \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=venkatesh.pallipadi@intel.com \
    --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).