linux-kernel - cpufreq longhaul locks up

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-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.61.0705041200370.18504@yvahk01.tjqt.qr>
Date:	Fri, 4 May 2007 12:16:21 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	davej@...emonkey.org.uk
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	cpufreq@...ts.linux.org.uk
Subject: cpufreq longhaul locks up

Hi,

I found that setting the cpufreq governor to ondemand making the box 
lock up solid in 2.6.20.2 and 2.6.21 after a few seconds. Sysrq 
does not work anymore, and the last messages are:

May  3 19:16:58 cn kernel: longhaul: VIA C3 'Nehemiah C' [C5P] CPU 
detected.  Powersaver supported.
May  3 19:16:58 cn kernel: longhaul: Using northbridge support.
May  3 19:17:22 cn kernel: Time: acpi_pm clocksource has been installed.
May  3 19:17:22 cn kernel: Clocksource tsc unstable (delta = -136422685 
ns)

I have also tried 2.6.20.2 in single-user mode (so that I can have 
the disk readonly), and it take a little longer (magnitude: minutes) 
to lock up; not sure if it's 20.2 or the single-user mode but I suspect 
the latter since nothing is running then that could potentially 
contribute to quickly changing workloads/frequencies.

If you need more info, please let me know.

Thanks,
Jan
-- 
-
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/