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
| ||
|
Date: Wed, 13 Aug 2008 12:08:23 +0300 From: Denys Fedoryshchenko <denys@...p.net.lb> To: Jarek Poplawski <jarkao2@...il.com> Cc: netdev@...r.kernel.org Subject: Re: NMI lockup, 2.6.26 release On Wednesday 13 August 2008, Jarek Poplawski wrote: > I don't think it's right: there could be probably some small time > differences between cpus on SMP or even some inaccuracy related to > hardware, but I don't think it's the right place or method to verify > this. And eg. re-scheduling with the same time shouldn't be wrong too. OK! Got you. Difference possible, on that machine it is using TSC from Core 2 Duo. I tried to run some code from Ingo Molnar to check is TSC synchronised - after 2 days it doesn't detect anything. > > Anyway, narrowing the problem with such tests should give us better > understanding what could be a real problem here. BTW, could you > "remind" us the .config on this box (especially various *HZ*, *TIME* > and *TIMERS* settings). http://www.nuclearcat.com/files/config_2.6.26.2.txt Same used for 2.6.26.2, this config from 2.6.26.1 -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists