linux-kernel - Re: [Bug #10369] The never ending BEEEEP/__smp_call_function

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]

Message-ID: <alpine.LFD.1.10.0804140940200.3261@apollo.tec.linutronix.de>
Date:	Mon, 14 Apr 2008 14:51:50 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Chr <chunkeey@....de>
cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [Bug #10369] The never ending BEEEEP/__smp_call_function_mask
 with 2.6.25-rc7

On Sun, 13 Apr 2008, Chr wrote:
> On Sunday 13 April 2008 22:02:08 Thomas Gleixner wrote:
> >
> > The problem still persists and I have no clue at all what's the root
> > cause. The symptom is a stuck local apic timer interrupt as we have
> > seen it on those AMD X2 systems with C1E enabled. This box does not
> > advertise C1E, but the behaviour is the same.
> >
> > Christian, it would be great if you could bisect the git tree so we
> > get an idea which patch is exposing this problem. My feeling is that
> > the problem itself is there with 2.6.24 as well but not
> > exposed. That's just a gut feeling and I could be wrong as usual.
> 
> Ok! The biggest problem however is: I can only run bisects on weekends. :-(
> And even then: it takes up to 2 hours until the timer gets stuck... and the 
> system freezes...

Oh well, that's a bad idea then.

> But, on the other hand... does ANYBODY know a way how I can see if the 
> apictimer drifts/(getting slower and slower)?

Well, it does not drift. It's stopped by some magic, but I do not
understand why we do not see that behaviour in 2.6.24. The code logic
in this area is really unchanged.

Can you disable CPUIDLE for a test please ?

Thanks,
	tglx


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/