linux-kernel - Re: endless loop in native_flush_tlb_others in smp

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 11 Mar 2008 11:30:54 +0100
From:	Chr <chunkeey@....de>
To:	"Jike Song" <albcamus@...il.com>
Cc:	"Linux Kernel" <linux-kernel@...r.kernel.org>,
	venkatesh.pallipadi@...el.com, "Ingo Molnar" <mingo@...e.hu>,
	"Thomas Gleixner" <tglx@...utronix.de>, len.brown@...el.com
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@....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?! ;-) 

Regards,
	Chr.

View attachment "config-2.6.25-rc5" of type "text/plain" (47421 bytes)