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 <Daniel.van.Eeden@myname.nl> wrote:
> 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?
> 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?