I looked at the patch and noticed that it's changing a file inside
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?
----- Original Message -----
From: "Rafael J. Wysocki" <[email protected]>
To: "Jon Schindler" <[email protected]>
Cc: <[email protected]>
Sent: Thursday, July 07, 2005 4:29 AM
Subject: Re: Kernel Oops with dual core athlon 64
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
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
X11 and I still have this issue. Does anyone have any ideas what might
causing this? Thanks in advance for the help. I don't know my way
the kernel, but I do have experience with C and should be able to apply
SMP patches if you want me to test it
It seems to be a cpufreq issue. You can try to apply the attached patch
- 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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Video 4 Linux]
[Linux for the blind]