mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Hamish Moffatt <hamish@cloud.net.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: general protection fault with powernow-k8 frequency scaling on x86-64
Date: 20 Aug 2007 01:46:27 +0200	[thread overview]
Message-ID: <p73d4xj1418.fsf@bingen.suse.de> (raw)
In-Reply-To: <20070819034558.GB9431@cloud.net.au>

Hamish Moffatt <hamish@cloud.net.au> writes:

> I'm running 2.6.22.1 (Debian's package) although this started happening
> at first with about 2.6.17.

If you can reproduce it you could bisect it. But it's unlikely that it is a 
software problem.

However it might just be that powernow wasn't used in the old kernel
and some change made it work. Also newer kernels tend to change
frequencies more often especially with ondemand; that might have also 
triggered it.


> 
> Here's an example fault; a few more occur a few minutes after that, then
> the whole system locks up soon after. The complete kernel log is below.
> 
> Any ideas?

It sounds like some kind of hardware issue. The Voltage Regulation Module
on the motherboard could have problems with the power supply to the
CPU and that can then cause all kinds of weird effects. On K7 such
problems were fairly common; on K8 less so because powernow 
is more widdespread but can happen occasionally.

It might also be that your hardware degenerated (e.g cheap boards
often have not very long lived components). You could double check
that by running the 2.6.17 kernel again (making sure it does powernow) 

Exchanging the motherboard could potentially safe a lot of trouble.
Or not run powernow anymore.

-Andi

      reply	other threads:[~2007-08-19 22:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-19  3:45 Hamish Moffatt
2007-08-19 23:46 ` Andi Kleen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=p73d4xj1418.fsf@bingen.suse.de \
    --to=andi@firstfloor.org \
    --cc=hamish@cloud.net.au \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome