mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jon Schindler" <jonschindler@hotmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Kernel Oops with dual core athlon 64 (quick question)
Date: Thu, 7 Jul 2005 11:41:34 -0500	[thread overview]
Message-ID: <BAY103-DAV217585FF946492DCAC9FFC4D80@phx.gbl> (raw)
In-Reply-To: <200507071129.38714.rjw@sisk.pl>

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?  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?

Thanks,

Jon

----- Original Message ----- 

From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Jon Schindler" <jonschindler@hotmail.com>
Cc: <linux-kernel@vger.kernel.org>
Sent: Thursday, July 07, 2005 4:29 AM
Subject: Re: Kernel Oops with dual core athlon 64


> Hi,
>
> On Thursday, 7 of July 2005 07:58, Jon Schindler wrote:
>> The dmesg is below.  After I get this Oops, I am unable to use my (PS/2)
>> keyboard, and had to ssh to my machine in order to save a copy of dmesg
>> before rebooting the machine.  I've seen a couple of other users of dual
>> core machings having this problem.  The suggestion so far has been to 
>> remove
>> the binary nvidia driver and repoducde the bug.  So, I went ahead and
>> removed the nvidia driver and used the deprecated nv driver that comes 
>> with
>> X11 and I still have this issue.  Does anyone have any ideas what might 
>> be
>> causing this?  Thanks in advance for the help.  I don't know my way 
>> around
>> the kernel, but I do have experience with C and should be able to apply 
>> any
>> SMP patches if you want me to test it
>
> It seems to be a cpufreq issue.  You can try to apply the attached patch 
> from
> Mark Langsdorf.
>
> 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"
> 

  parent reply	other threads:[~2005-07-07 16:44 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   ` Jon Schindler [this message]
2005-07-07 19:04     ` Kernel Oops with dual core athlon 64 (quick question) Rafael J. Wysocki
2005-07-08  4:48       ` Jon Schindler

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=BAY103-DAV217585FF946492DCAC9FFC4D80@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®