Re: System crash caused by the powernow-k8 kernel module
On Sun, Dec 02, 2007 at 11:11:14PM +0200, Teodor wrote: On Sat, 1 Dec 2007 22:33:30 +0900 Mattia Dongili [EMAIL PROTECTED] wrote: On Sun, Nov 25, 2007 at 10:34:53AM +0100, Daniel van Eeden wrote: modinfo powernow-k8 on my machine does not show any parms for debugging. Some modules can be loaded with a debug option enabled. booting with cpufreq.debug=7 should enable (a lot) more messages. This is what is shows in the boot log: Dec 2 23:03:33 piti kernel: Kernel command line: root=/dev/sda1 ro quiet vga=791 panic=20 cpufreq.debug=7 Dec 2 23:03:33 piti kernel: Unknown boot option `cpufreq.debug=7': ignoring Where else should I try to add this parameter? sorry for the very late reply, you need CONFIG_CPU_FREQ_DEBUG=y to be able to use the aforementioned parameter cheers -- mattia :wq! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: System crash caused by the powernow-k8 kernel module
On Sat, 1 Dec 2007 22:33:30 +0900 Mattia Dongili [EMAIL PROTECTED] wrote: On Sun, Nov 25, 2007 at 10:34:53AM +0100, Daniel van Eeden wrote: modinfo powernow-k8 on my machine does not show any parms for debugging. Some modules can be loaded with a debug option enabled. booting with cpufreq.debug=7 should enable (a lot) more messages. This is what is shows in the boot log: Dec 2 23:03:33 piti kernel: Kernel command line: root=/dev/sda1 ro quiet vga=791 panic=20 cpufreq.debug=7 Dec 2 23:03:33 piti kernel: Unknown boot option `cpufreq.debug=7': ignoring Where else should I try to add this parameter? Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: System crash caused by the powernow-k8 kernel module
On Sun, Nov 25, 2007 at 10:34:53AM +0100, Daniel van Eeden wrote: Teodor, ... modinfo powernow-k8 on my machine does not show any parms for debugging. Some modules can be loaded with a debug option enabled. booting with cpufreq.debug=7 should enable (a lot) more messages. cheers -- mattia :wq! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: System crash caused by the powernow-k8 kernel module
On Sun, Nov 25, 2007 at 10:32:31PM +0200, Teodor wrote: A few minutes ago I've upgraded the BIOS to the latest version available 1601beta and the system is freezing immediately after I start the firefox browser, probably caused by a growing load on the CPUs. Unfortunately I don't have a serial cable around but I'll try to buy one. Can you direct me to a good howto on setting a serial console? I'll search on Internet but you might know a short one. Paul and Mark, do you have any suggestions for fixing this? If it is locking up as soon as you start putting load on it, perhaps you have a crappy power supply or bad ram. I know many people on this list have had strange lockups and in the end it always seemed to come down to using bad ram (where bad ram is defined as any ram that isn't perfectly within it's claimed specifications since the memory controller on AMD cpus _will_ try to use it to the limits of the claimed spec). Power supplies that are under powered or just badly designed may also have trouble dealing with sudden changes in demand on power (which certainly would happen when the cpu decides to change frequency and voltage level due to change in demand when powernow is enabled). What kind of power supply are you using? -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: System crash caused by the powernow-k8 kernel module
Teodor, You could set your machine up for serial console and connect another machine to capture the messages it generates during the crash. Sometimes the most useful messages are not logged to syslog but only to the console. modinfo powernow-k8 on my machine does not show any parms for debugging. Some modules can be loaded with a debug option enabled. Cheers, Daniel On Sat, 2007-11-24 at 20:21 +0200, Teodor wrote: Hi, I'm having Debian GNU/Linux installed on my workstation with AMD Athlon(tm) 64 X2 4800+ (actually 2.5GHz). From the very beginning after the install I was getting multiple system freezes. This happens with both linux images from unstable (2.6.22-3-amd64) and testing (2.6.22-2-amd64). Recently I've found that is caused by the powernow-k8 kernel module. I can reproduce the problem easily by activating the 'Cool n Quiet' option in the BIOS and just reboot the system. The freeze usually happens after I'm logged in the X session probably when the load is growing. As a temporary workaround I've blacklisted the powernow-k8 module and no more system freezes. I would like to fill a bug report but I'm afraid I don't have enough useful information to give. Can you tell me how can I debug a kernel panic/crash? Thanks for your help. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: System crash caused by the powernow-k8 kernel module
CC to the authors of the powernow-k8 linux kernel module. On Sun, 25 Nov 2007 10:34:53 +0100 Daniel van Eeden [EMAIL PROTECTED] wrote: Teodor, You could set your machine up for serial console and connect another machine to capture the messages it generates during the crash. Sometimes the most useful messages are not logged to syslog but only to the console. modinfo powernow-k8 on my machine does not show any parms for debugging. Some modules can be loaded with a debug option enabled. A few minutes ago I've upgraded the BIOS to the latest version available 1601beta and the system is freezing immediately after I start the firefox browser, probably caused by a growing load on the CPUs. Unfortunately I don't have a serial cable around but I'll try to buy one. Can you direct me to a good howto on setting a serial console? I'll search on Internet but you might know a short one. Paul and Mark, do you have any suggestions for fixing this? Thanks On Sat, 2007-11-24 at 20:21 +0200, Teodor wrote: Hi, I'm having Debian GNU/Linux installed on my workstation with AMD Athlon(tm) 64 X2 4800+ (actually 2.5GHz). From the very beginning after the install I was getting multiple system freezes. This happens with both linux images from unstable (2.6.22-3-amd64) and testing (2.6.22-2-amd64). Recently I've found that is caused by the powernow-k8 kernel module. I can reproduce the problem easily by activating the 'Cool n Quiet' option in the BIOS and just reboot the system. The freeze usually happens after I'm logged in the X session probably when the load is growing. As a temporary workaround I've blacklisted the powernow-k8 module and no more system freezes. I would like to fill a bug report but I'm afraid I don't have enough useful information to give. Can you tell me how can I debug a kernel panic/crash? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
System crash caused by the powernow-k8 kernel module
Hi, I'm having Debian GNU/Linux installed on my workstation with AMD Athlon(tm) 64 X2 4800+ (actually 2.5GHz). From the very beginning after the install I was getting multiple system freezes. This happens with both linux images from unstable (2.6.22-3-amd64) and testing (2.6.22-2-amd64). Recently I've found that is caused by the powernow-k8 kernel module. I can reproduce the problem easily by activating the 'Cool n Quiet' option in the BIOS and just reboot the system. The freeze usually happens after I'm logged in the X session probably when the load is growing. As a temporary workaround I've blacklisted the powernow-k8 module and no more system freezes. I would like to fill a bug report but I'm afraid I don't have enough useful information to give. Can you tell me how can I debug a kernel panic/crash? Thanks for your help. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
