| 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: Mon, 16 Oct 2006 15:32:38 +0100 From: David Johnson <dj@...id-web.co.uk> To: Jarek Poplawski <jarkao2@...pl> Cc: Linux Kernel <linux-kernel@...r.kernel.org>, netdev@...r.kernel.org Subject: Re: Hardware bug or kernel bug? On Monday 16 October 2006 11:25, Jarek Poplawski wrote: > > Was this lock-up effect visible during above 2.6.19-rc1 tests? No, I've not seen anything in Linux other than the reboots, which are instant without any preceding lock-up. > If not I'd try to continue linux debbuging: > - is 2.6.19-rc1 working with "normal" config (use make oldconfig > to "upgrade" .config), With 2.6.19-rc1 and a normal config, I get the reboots as usual. > - is 2.6.17 working with "minimal" config (use make oldconfig), Yes. > - changing one or two options at a time try to find which one makes > the effect returns (acpi, smp...). I've found the culprit - CPU Frequency Scaling. With it enabled I get the reboots, with it disabled I don't. That's the same with every kernel version I've tried (2.6.19-rc1+rc2, 2.6.17.13 & Centos' 2.6.9) The system was using the p4-clockmod driver and the ondemand governor. I'm still not sure exactly what the problem is - the reboots only happen in the circumstances I've mentioned and are not triggered by changes in clock speed alone - but disabling cpufreq seems to make it go away... Thanks for your help, David. - 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