mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jon Schindler" <jonschindler@hotmail.com>
To: rjw@sisk.pl
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Oops with dual core athlon 64 (quick question)
Date: Fri, 08 Jul 2005 00:48:31 -0400	[thread overview]
Message-ID: <BAY20-F22F887E749670F2B2BB7DDC4DB0@phx.gbl> (raw)
In-Reply-To: <200507072104.26034.rjw@sisk.pl>

Rafael,

Thanks a lot for the quick reply and patch.  I have tested the patch tonight 
and things are looking good so far.  For the first time since I upgraded 
from my single core athlon 64 3500+ my cpu fan isn't a tornado.  Also, my 
CPU frequency isn't pegged at full throttle 24/7 (it's dropping down to 1000 
Mhz at idle as it should).  This is a good sign that your patch did fix the 
cpufreq driver in addition to the oopses I've been experiencing.

Thanks again for the patch, I'll let you know if the oopses reappear, but so 
far things are looking very good.

Jon

>From: "Rafael J. Wysocki" <rjw@sisk.pl>
>To: "Jon Schindler" <jonschindler@hotmail.com>
>CC: linux-kernel@vger.kernel.org
>Subject: Re: Kernel Oops with dual core athlon 64 (quick question)
>Date: Thu, 7 Jul 2005 21:04:25 +0200
>
>Hi,
>
>On Thursday, 7 of July 2005 18:41, Jon Schindler wrote:
> > Hi Rafael,
> > I looked at the patch and noticed that it's changing a file inside
> > linux-2.6.12-rc6/arch/i386/kernel/cpu/cpufreq/powernow-k8.c
> > So, basically, it's modifying the powernow driver in the i386 arch
> > directory, but shouldn't that file be in "arch/x86_64/....", or am I 
>missing
> > something?
>
>Yes. :-)
>
> > I'm compiling the kernel for x86_64, so will my 64 bit kernel
> > use this file even though it's in the i386 directory?
>
>Yes, it will.  x86-64 uses some sources from i386 directly, including
>cpufreq (they would be identical anyway).
>
>Greets,
>Rafael
>
>
>--
>- Would you tell me, please, which way I ought to go from here?
>- That depends a good deal on where you want to get to.
>		-- Lewis Carroll "Alice's Adventures in Wonderland"
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/



      reply	other threads:[~2005-07-08  4:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-07  5:58 Kernel Oops with dual core athlon 64 Jon Schindler
2005-07-07  9:29 ` Rafael J. Wysocki
2005-07-07 16:34   ` Jon Schindler
2005-07-07 16:41   ` Kernel Oops with dual core athlon 64 (quick question) Jon Schindler
2005-07-07 19:04     ` Rafael J. Wysocki
2005-07-08  4:48       ` Jon Schindler [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=BAY20-F22F887E749670F2B2BB7DDC4DB0@phx.gbl \
    --to=jonschindler@hotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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

all inboxes | Powered by JetHome®