| 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
| ||
|
Message-Id: <200803302309.52493.chunkeey@web.de> Date: Sun, 30 Mar 2008 23:09:52 +0200 From: Chr <chunkeey@....de> To: Thomas Gleixner <tglx@...utronix.de> Cc: "Rafael J. Wysocki" <rjw@...k.pl>, linux-kernel@...r.kernel.org, Andi Kleen <andi-suse@...stfloor.org>, Andrew Morton <akpm@...ux-foundation.org>, Ingo Molnar <mingo@...e.hu> Subject: Re: The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7 On Sunday 30 March 2008 22:37:29 Thomas Gleixner wrote: > On Sun, 30 Mar 2008, Chr wrote: > > On Sunday 30 March 2008 21:59:51 Thomas Gleixner wrote: > > > On Sun, 30 Mar 2008, Rafael J. Wysocki wrote: > > > > > So. take a look at stuck_task... that's best backtrace I could > > > > > get... (I have other logs too. (Task-list / Lockdep / ... ) but > > > > > it's too much and I hope the _logs_ are already enough. > > > > > > The cores of those AMD beasts are never in sync. That's a chip feature > > > :) > > > > > > Can you please provide the output of: > > > /sys/devices/system/clocksource/clocksource0/current_clocksource > > > > > > for both 2.6.24 and 2.6.25-rc7 > > > > it's "hpet" (in both cases...) > > Hmm. That should be stable. Which clock is jumping back and forth ? > The one in the logs or the system clock ? The one in the logs... (but it's because of the TSC, right?) Regards, Chr -- 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/
Powered by blists - more mailing lists