http://bugzilla.novell.com/show_bug.cgi?id=506790 User mail@cynapses.org added comment http://bugzilla.novell.com/show_bug.cgi?id=506790#c1 --- Comment #1 from Andreas Schneider 2009-05-25 09:58:30 MDT --- This happened again in 24h now. I hope unloading the powernow_k8 module helps as a workaround. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=506790 User mail@cynapses.org added comment http://bugzilla.novell.com/show_bug.cgi?id=506790#c3 --- Comment #3 from Andreas Schneider 2009-05-25 10:11:26 MDT --- Created an attachment (id=294260) --> (http://bugzilla.novell.com/attachment.cgi?id=294260) acpidump of the machine -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=506790 User trenn@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=506790#c5 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |mark.langsdorf@amd.com Info Provider| |mail@cynapses.org --- Comment #5 from Thomas Renninger 2009-06-03 06:38:49 MDT --- This is really weird. There is no cpufreq information in the ACPI BIOS tables. So about comment #2: No the patch should not affect you (unless there is a really big hammer of bug in it). This is a single core system? Then the information seem to come from a deprecated/old PSB table. I cannot see any printk which could verify this in syslog, though. Maybe a warning/notice should be added if PSB table is used... Did this ever work (powernow-k8 driver) on this machine? What does: cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_transition_latency tell us? Adding Mark, he might be interested or could tell us more about PSB and whether it could/should get used at all. If this never worked or powernow-k8 never got tested on this machine, then better upgrade the BIOS, otherwise I'd like to dig a bit more and find the regression. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=506790 User mail@cynapses.org added comment http://bugzilla.novell.com/show_bug.cgi?id=506790#c6 --- Comment #6 from Andreas Schneider 2009-06-03 06:45:58 MDT --- Yes, this is a single core system, AMD Athlon(tm) 64 Processor 3800+, 2400 MHz. milliways:~ # modprobe powernow_k8 milliways:~ # cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_transition_latency 1240000 I'm not able to do a BIOS update, this is a server at a ISP. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=506790 User trenn@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=506790#c7 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #7 from Thomas Renninger 2009-06-03 07:20:06 MDT --- The transition latency of: 1240000 corresponds to the wrongly calculated one if no ACPI table is used. This will result in an ondemand governor sampling rate of 1,24 seconds which makes PowerNow! rather useless or say will introduce a sever performance regression without manually lowering the ondemand governor sampling rate. On the other hand, this high sampling rate should be save and not the reason for powernow-k8 driver breaking/freezing the machine. I expect this comes from wrong PSB table values which I am not willing to debug any further. I also expect powernow-k8 driver never worked on this machine and this is not a regression. Please reopen if powernow-k8 already worked. Blacklisting powernow-k8 for this machine is IMO the right thing to do for this BIOS. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.