powernow-k8 cpufreq driver problems (fails to load on MSI k8n neo2 w/3500+)
Hi, I have two machines with similar specs (same motherboard and bios version), and one works fine with the cpufreq driver while the other machine is giving me the following messages below. powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.40.4) cpufreq-core: trying to register driver powernow-k8 cpufreq-core: adding CPU 0 powernow-k8: register performance failed: bad ACPI data powernow-k8: BIOS error - no PSB or ACPI _PSS objects cpufreq-core: initialization failed cpufreq-core: no CPU initialized for driver powernow-k8 cpufreq-core: unregistering CPU 0 I have done roughly 8 hours of google searching and research, have tried various kernel options, tried updating to the latest kernel, tried reverting to an earlier bios, but nothing seems to work. At this point, I think there may be an issue with the kernel. However, it doesn't make sense that the bios and powernow would work with a bleeding edge dual core processor, but not work with an older processor model on the same motherboard. I've obviously run out of ideas. If anyone has any suggestions or ideas, (or even better, a patch) I would really appreciate it. Strangely enough, the machine that works with powernow has a leading edge athlon 4800+, while the one that is broken is running an Athlon 3500+. Anyway, here are the details. Machine 1: (works with powernow) OS: Fedora Core 4 64 bit version, kernel 2.6.12.3 AMD Athlon 4800+ 3GB of RAM MSI K8N Neo2 Platinum motherboard with bios version 1.9 Nvidia Geforce 6800 GT video card (AGP) 3 hard drives, 2 SATA, 1 ATA ATI Tv Wonder PCI 1 Plextor DVD burner Machine 2:(fails to load powernow driver) OS: Fedora Cord 4 32 bit version, kernel 2.6.12.4 AMD Athlon 3500+ (venice core, stepping 2) MSI K8N Neo2 Platinum motherboard with bios version 1.9 1 GB of RAM Trident PCI video card (it's a file/mail server) 4 SATA drives in a RAID 5 array (data drives) 2 ATA drives in a RAID 1 array (boot drive) 1 NEC DVD RW (model 3504?) Here is the dmesg for machine 1: Bootdata ok (command line is ro root=LABEL=/1 rhgb quiet) Linux version 2.6.12.3 ([EMAIL PROTECTED]) (gcc version 4.0.0 20050519 (Red Hat 4.0.0-8)) #2 SMP Thu Jul 21 03:48:06 CDT 2005 BIOS-provided physical RAM map: BIOS-e820: - 0009f000 (usable) BIOS-e820: 0009f000 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - bfff (usable) BIOS-e820: bfff - bfff3000 (ACPI NVS) BIOS-e820: bfff3000 - c000 (ACPI data) BIOS-e820: fec0 - 0001 (reserved) ACPI: RSDP (v000 Nvidia) @ 0x000f8f30 ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x) @ 0xbfff3040 ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x) @ 0xbfff30c0 ACPI: SSDT (v001 PTLTD POWERNOW 0x0001 LTP 0x0001) @ 0xbfff7b80 ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x) @ 0xbfff7ac0 ACPI: DSDT (v001 NVIDIA AWRDACPI 0x1000 MSFT 0x010e) @ 0x On node 0 totalpages: 786416 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 782320 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:1 Nvidia board detected. Ignoring ACPI timer override. ACPI: PM-Timer IO Port: 0x4008 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 15:3 APIC version 16 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) Processor #1 15:3 APIC version 16 ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 2, version 17, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: BIOS IRQ0 pin2 override ignored. ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge) ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge) ACPI: IRQ9 used by override. ACPI: IRQ14 used by override. ACPI: IRQ15 used by override. Setting APIC routing to flat Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at c000 (gap: c000:3ec0) Checking aperture... CPU 0: aperture @ e000 size 256 MB Built 1 zonelists Kernel command line: ro root=LABEL=/1 rhgb quiet Initializing CPU#0 PID hash table entries: 4096 (order: 12, 131072 bytes) time.c: Using 3.579545 MHz PM timer. time.c: Detected 2411.790 MHz processor. Console: colour VGA+ 80x25 Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) Memory: 3088432k/3145664k available (2361k kernel code, 56304k reserved, 1585k data, 220k init) Calibrating delay loop... 4784.12 BogoMIPS (lpj=2392064) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in
powernow-k8 cpufreq driver problems (fails to load on MSI k8n neo2 w/3500+)
Hi, I have two machines with similar specs (same motherboard and bios version), and one works fine with the cpufreq driver while the other machine is giving me the following messages below. powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.40.4) cpufreq-core: trying to register driver powernow-k8 cpufreq-core: adding CPU 0 powernow-k8: register performance failed: bad ACPI data powernow-k8: BIOS error - no PSB or ACPI _PSS objects cpufreq-core: initialization failed cpufreq-core: no CPU initialized for driver powernow-k8 cpufreq-core: unregistering CPU 0 I have done roughly 8 hours of google searching and research, have tried various kernel options, tried updating to the latest kernel, tried reverting to an earlier bios, but nothing seems to work. At this point, I think there may be an issue with the kernel. However, it doesn't make sense that the bios and powernow would work with a bleeding edge dual core processor, but not work with an older processor model on the same motherboard. I've obviously run out of ideas. If anyone has any suggestions or ideas, (or even better, a patch) I would really appreciate it. Strangely enough, the machine that works with powernow has a leading edge athlon 4800+, while the one that is broken is running an Athlon 3500+. Anyway, here are the details. Machine 1: (works with powernow) OS: Fedora Core 4 64 bit version, kernel 2.6.12.3 AMD Athlon 4800+ 3GB of RAM MSI K8N Neo2 Platinum motherboard with bios version 1.9 Nvidia Geforce 6800 GT video card (AGP) 3 hard drives, 2 SATA, 1 ATA ATI Tv Wonder PCI 1 Plextor DVD burner Machine 2:(fails to load powernow driver) OS: Fedora Cord 4 32 bit version, kernel 2.6.12.4 AMD Athlon 3500+ (venice core, stepping 2) MSI K8N Neo2 Platinum motherboard with bios version 1.9 1 GB of RAM Trident PCI video card (it's a file/mail server) 4 SATA drives in a RAID 5 array (data drives) 2 ATA drives in a RAID 1 array (boot drive) 1 NEC DVD RW (model 3504?) Here is the dmesg for machine 1: Bootdata ok (command line is ro root=LABEL=/1 rhgb quiet) Linux version 2.6.12.3 ([EMAIL PROTECTED]) (gcc version 4.0.0 20050519 (Red Hat 4.0.0-8)) #2 SMP Thu Jul 21 03:48:06 CDT 2005 BIOS-provided physical RAM map: BIOS-e820: - 0009f000 (usable) BIOS-e820: 0009f000 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - bfff (usable) BIOS-e820: bfff - bfff3000 (ACPI NVS) BIOS-e820: bfff3000 - c000 (ACPI data) BIOS-e820: fec0 - 0001 (reserved) ACPI: RSDP (v000 Nvidia) @ 0x000f8f30 ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x) @ 0xbfff3040 ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x) @ 0xbfff30c0 ACPI: SSDT (v001 PTLTD POWERNOW 0x0001 LTP 0x0001) @ 0xbfff7b80 ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x) @ 0xbfff7ac0 ACPI: DSDT (v001 NVIDIA AWRDACPI 0x1000 MSFT 0x010e) @ 0x On node 0 totalpages: 786416 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 782320 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:1 Nvidia board detected. Ignoring ACPI timer override. ACPI: PM-Timer IO Port: 0x4008 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 15:3 APIC version 16 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) Processor #1 15:3 APIC version 16 ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 2, version 17, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: BIOS IRQ0 pin2 override ignored. ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge) ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge) ACPI: IRQ9 used by override. ACPI: IRQ14 used by override. ACPI: IRQ15 used by override. Setting APIC routing to flat Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at c000 (gap: c000:3ec0) Checking aperture... CPU 0: aperture @ e000 size 256 MB Built 1 zonelists Kernel command line: ro root=LABEL=/1 rhgb quiet Initializing CPU#0 PID hash table entries: 4096 (order: 12, 131072 bytes) time.c: Using 3.579545 MHz PM timer. time.c: Detected 2411.790 MHz processor. Console: colour VGA+ 80x25 Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) Memory: 3088432k/3145664k available (2361k kernel code, 56304k reserved, 1585k data, 220k init) Calibrating delay loop... 4784.12 BogoMIPS (lpj=2392064) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in
Re: USB storage does not work with 3GB of RAM, but does with 2G of RAM
I tried this last night and enabling the OS2 memory hole in the bios doesn't work. That's the only memory hole option available. If I were more savvy with the kernel memory layout, I might try passing it a set of memmap options, but I'm not very familiar with what address spaces I need to set up for the kernel or how much space they need, or if there are any rules concerning what goes where. (i.e. the difference between reserved, ACPI, etc.) Thanks anyway for the suggestion, Jon From: Oliver Weihe <[EMAIL PROTECTED]> To: linux-kernel@vger.kernel.org Subject: Re: USB storage does not work with 3GB of RAM, but does with 2G of RAM Date: Mon, 11 Jul 2005 17:03:24 +0200 (CEST) Tried different settings for "Soft-/Hardware Memory Hole" in BIOS? - 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/ - 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/
Re: USB storage does not work with 3GB of RAM, but does with 2G of RAM
I tried this last night and enabling the OS2 memory hole in the bios doesn't work. That's the only memory hole option available. If I were more savvy with the kernel memory layout, I might try passing it a set of memmap options, but I'm not very familiar with what address spaces I need to set up for the kernel or how much space they need, or if there are any rules concerning what goes where. (i.e. the difference between reserved, ACPI, etc.) Thanks anyway for the suggestion, Jon From: Oliver Weihe [EMAIL PROTECTED] To: linux-kernel@vger.kernel.org Subject: Re: USB storage does not work with 3GB of RAM, but does with 2G of RAM Date: Mon, 11 Jul 2005 17:03:24 +0200 (CEST) Tried different settings for Soft-/Hardware Memory Hole in BIOS? - 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/ - 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/
Re: USB storage does not work with 3GB of RAM, but does with 2G of RAM
are you referring to the "OS/2" memory hole option? No, I haven't tried it, but it's an interesting idea. I'm pretty sure the only memory hole that my bios has is the option for OS/2, which I will try tonight. Thanks, Jon From: Oliver Weihe <[EMAIL PROTECTED]> To: linux-kernel@vger.kernel.org Subject: Re: USB storage does not work with 3GB of RAM, but does with 2G of RAM Date: Mon, 11 Jul 2005 17:03:24 +0200 (CEST) Tried different settings for "Soft-/Hardware Memory Hole" in BIOS? - 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/ - 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/
Re: USB storage does not work with 3GB of RAM, but does with 2G of RAM
are you referring to the OS/2 memory hole option? No, I haven't tried it, but it's an interesting idea. I'm pretty sure the only memory hole that my bios has is the option for OS/2, which I will try tonight. Thanks, Jon From: Oliver Weihe [EMAIL PROTECTED] To: linux-kernel@vger.kernel.org Subject: Re: USB storage does not work with 3GB of RAM, but does with 2G of RAM Date: Mon, 11 Jul 2005 17:03:24 +0200 (CEST) Tried different settings for Soft-/Hardware Memory Hole in BIOS? - 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/ - 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/
Re: USB storage does not work with 3GB of RAM, but does with 2G of RAM
Do you know if there is a way to tell the ehci driver to do the DMA at a lower memory address? i.e. tell the kernel to reserve a block of memory (as a boot option) and then tell the ehci driver to use that area of RAM instead? Thanks again for your help, Jon From: Andi Kleen <[EMAIL PROTECTED]> To: Jon Schindler <[EMAIL PROTECTED]> CC: [EMAIL PROTECTED], linux-kernel@vger.kernel.org Subject: Re: USB storage does not work with 3GB of RAM, but does with 2G of RAM Date: Sat, 9 Jul 2005 02:56:38 +0200 On Fri, Jul 08, 2005 at 08:49:12PM -0400, Jon Schindler wrote: > Hi Andi, > > As you suggested, removing ehci_hcd (using rmmod ehci_hcd) allows the USB > storage device to work. So, to answer your question, yes, the ohci_hcd > driver does work with 3GB's of RAM. Still, knoppix 3.9 IS able to work > with both ehci and 3GB's of RAM, so it still sounds like it's a software > problem, not an nvidia hardware issue. Knoppix is 32bit I guess. The 32bit kernel will do a lot of DMA only in the first 800-900MB (lowmem) -Andi - 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/ - 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/
Re: USB storage does not work with 3GB of RAM, but does with 2G of RAM
Hi Andi, As you suggested, removing ehci_hcd (using rmmod ehci_hcd) allows the USB storage device to work. So, to answer your question, yes, the ohci_hcd driver does work with 3GB's of RAM. Still, knoppix 3.9 IS able to work with both ehci and 3GB's of RAM, so it still sounds like it's a software problem, not an nvidia hardware issue. Jon From: Andi Kleen <[EMAIL PROTECTED]> To: "Jon Schindler" <[EMAIL PROTECTED]> CC: linux-kernel@vger.kernel.org Subject: Re: USB storage does not work with 3GB of RAM, but does with 2G of RAM Date: 08 Jul 2005 21:29:37 +0200 "Jon Schindler" <[EMAIL PROTECTED]> writes: > > This mainly seems to be an issue with USB mass storage devices like > USB memory sticks and USB hard drives (I've tried both, and neither is > assigned a scsi device properly). I am still able to use my USB mouse > when I have 3GB installed. I'm not sure if that makes it a USB 1.1 > issue or a USB storage issue, but hopefully someone will have some > insight after looking at the logs. Thanks in advance for any help. It sounds like the Nvidia EHCI controller has trouble DMAing to high addresses. Would be a bad bug if true. Does it work when you disable EHCI and only enable OHCI? (this will limit you to USB 1.1) -Andi - 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/ - 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/
Re: USB storage does not work with 3GB of RAM, but does with 2G of RAM
I just thought that I would add, USB works fine if I boot with knoppix 3.9, or with Windows XP, even with 3GB's of RAM installed. It's only if I try to use USB mass storage devices, Fedora Core 4 64 bit, and 3GB's of RAM at the same time that I get this issue with USB. If I change the OS to XP, but keep the RAM at 3GB, it works fine. If I remove some RAM and only run 2GB's of RAM, then FC4 with the 2.6.12.1 64 bit kernel works fine. So, to sum things up: RAM amountOS64or32bit USB storage works? 3GBFC4 2.6.12.164 no 2GBFC4 2.6.12.164 yes 3GB XP SP2 32 yes 2GB XP SP2 32 yes 3GB Knoppix 3.9 32 yes 2GB Knoppix 3.9 32 yes Thanks again, Jon From: Andi Kleen <[EMAIL PROTECTED]> To: "Jon Schindler" <[EMAIL PROTECTED]> CC: linux-kernel@vger.kernel.org Subject: Re: USB storage does not work with 3GB of RAM, but does with 2G of RAM Date: 08 Jul 2005 21:29:37 +0200 "Jon Schindler" <[EMAIL PROTECTED]> writes: > > This mainly seems to be an issue with USB mass storage devices like > USB memory sticks and USB hard drives (I've tried both, and neither is > assigned a scsi device properly). I am still able to use my USB mouse > when I have 3GB installed. I'm not sure if that makes it a USB 1.1 > issue or a USB storage issue, but hopefully someone will have some > insight after looking at the logs. Thanks in advance for any help. It sounds like the Nvidia EHCI controller has trouble DMAing to high addresses. Would be a bad bug if true. Does it work when you disable EHCI and only enable OHCI? (this will limit you to USB 1.1) -Andi - 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/
Re: USB storage does not work with 3GB of RAM, but does with 2G of RAM
bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge (rev a2) (prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=128 I/O behind bridge: 8000-8fff Memory behind bridge: fdf0-fdff Prefetchable memory behind bridge: fde0-fdef 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration Flags: fast devsel Capabilities: [80] HyperTransport: Host or Secondary Interface 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map Flags: fast devsel 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller Flags: fast devsel 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control Flags: fast devsel 01:00.0 VGA compatible controller: nVidia Corporation NV40 [GeForce 6800 GT] (rev a1) (prog-if 00 [VGA]) Flags: bus master, 66Mhz, medium devsel, latency 248, IRQ 201 Memory at fa00 (32-bit, non-prefetchable) [size=16M] Memory at e000 (32-bit, prefetchable) [size=256M] Memory at fb00 (32-bit, non-prefetchable) [size=16M] Capabilities: [60] Power Management version 2 Capabilities: [44] AGP version 3.0 02:0a.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 02) Subsystem: ATI Technologies Inc: Unknown device 0001 Flags: bus master, medium devsel, latency 32, IRQ 217 Memory at fdeff000 (32-bit, prefetchable) [size=4K] 02:0a.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 02) Subsystem: ATI Technologies Inc TV-Wonder Flags: bus master, medium devsel, latency 32, IRQ 217 Memory at fdefe000 (32-bit, prefetchable) [size=4K] 02:0c.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46) (prog-if 10 [OHCI]) Subsystem: Unknown device 0574:086c Flags: bus master, stepping, medium devsel, latency 32, IRQ 225 Memory at fdfff000 (32-bit, non-prefetchable) [size=2K] I/O ports at 8c00 [size=128] Capabilities: [50] Power Management version 2 02:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) Subsystem: Micro-Star International Co., Ltd.: Unknown device 025c Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 201 I/O ports at 8800 [size=256] Memory at fdffe000 (32-bit, non-prefetchable) [size=256] Capabilities: [dc] Power Management version 2 From: Andi Kleen <[EMAIL PROTECTED]> To: "Jon Schindler" <[EMAIL PROTECTED]> CC: linux-kernel@vger.kernel.org Subject: Re: USB storage does not work with 3GB of RAM, but does with 2G of RAM Date: 08 Jul 2005 21:29:37 +0200 "Jon Schindler" <[EMAIL PROTECTED]> writes: > > This mainly seems to be an issue with USB mass storage devices like > USB memory sticks and USB hard drives (I've tried both, and neither is > assigned a scsi device properly). I am still able to use my USB mouse > when I have 3GB installed. I'm not sure if that makes it a USB 1.1 > issue or a USB storage issue, but hopefully someone will have some > insight after looking at the logs. Thanks in advance for any help. It sounds like the Nvidia EHCI controller has trouble DMAing to high addresses. Would be a bad bug if true. Does it work when you disable EHCI and only enable OHCI? (this will limit you to USB 1.1) -Andi - 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/
Re: USB storage does not work with 3GB of RAM, but does with 2G of RAM
bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge (rev a2) (prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=128 I/O behind bridge: 8000-8fff Memory behind bridge: fdf0-fdff Prefetchable memory behind bridge: fde0-fdef 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration Flags: fast devsel Capabilities: [80] HyperTransport: Host or Secondary Interface 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map Flags: fast devsel 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller Flags: fast devsel 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control Flags: fast devsel 01:00.0 VGA compatible controller: nVidia Corporation NV40 [GeForce 6800 GT] (rev a1) (prog-if 00 [VGA]) Flags: bus master, 66Mhz, medium devsel, latency 248, IRQ 201 Memory at fa00 (32-bit, non-prefetchable) [size=16M] Memory at e000 (32-bit, prefetchable) [size=256M] Memory at fb00 (32-bit, non-prefetchable) [size=16M] Capabilities: [60] Power Management version 2 Capabilities: [44] AGP version 3.0 02:0a.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 02) Subsystem: ATI Technologies Inc: Unknown device 0001 Flags: bus master, medium devsel, latency 32, IRQ 217 Memory at fdeff000 (32-bit, prefetchable) [size=4K] 02:0a.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 02) Subsystem: ATI Technologies Inc TV-Wonder Flags: bus master, medium devsel, latency 32, IRQ 217 Memory at fdefe000 (32-bit, prefetchable) [size=4K] 02:0c.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46) (prog-if 10 [OHCI]) Subsystem: Unknown device 0574:086c Flags: bus master, stepping, medium devsel, latency 32, IRQ 225 Memory at fdfff000 (32-bit, non-prefetchable) [size=2K] I/O ports at 8c00 [size=128] Capabilities: [50] Power Management version 2 02:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) Subsystem: Micro-Star International Co., Ltd.: Unknown device 025c Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 201 I/O ports at 8800 [size=256] Memory at fdffe000 (32-bit, non-prefetchable) [size=256] Capabilities: [dc] Power Management version 2 From: Andi Kleen [EMAIL PROTECTED] To: Jon Schindler [EMAIL PROTECTED] CC: linux-kernel@vger.kernel.org Subject: Re: USB storage does not work with 3GB of RAM, but does with 2G of RAM Date: 08 Jul 2005 21:29:37 +0200 Jon Schindler [EMAIL PROTECTED] writes: This mainly seems to be an issue with USB mass storage devices like USB memory sticks and USB hard drives (I've tried both, and neither is assigned a scsi device properly). I am still able to use my USB mouse when I have 3GB installed. I'm not sure if that makes it a USB 1.1 issue or a USB storage issue, but hopefully someone will have some insight after looking at the logs. Thanks in advance for any help. It sounds like the Nvidia EHCI controller has trouble DMAing to high addresses. Would be a bad bug if true. Does it work when you disable EHCI and only enable OHCI? (this will limit you to USB 1.1) -Andi - 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/
Re: USB storage does not work with 3GB of RAM, but does with 2G of RAM
I just thought that I would add, USB works fine if I boot with knoppix 3.9, or with Windows XP, even with 3GB's of RAM installed. It's only if I try to use USB mass storage devices, Fedora Core 4 64 bit, and 3GB's of RAM at the same time that I get this issue with USB. If I change the OS to XP, but keep the RAM at 3GB, it works fine. If I remove some RAM and only run 2GB's of RAM, then FC4 with the 2.6.12.1 64 bit kernel works fine. So, to sum things up: RAM amountOS64or32bit USB storage works? 3GBFC4 2.6.12.164 no 2GBFC4 2.6.12.164 yes 3GB XP SP2 32 yes 2GB XP SP2 32 yes 3GB Knoppix 3.9 32 yes 2GB Knoppix 3.9 32 yes Thanks again, Jon From: Andi Kleen [EMAIL PROTECTED] To: Jon Schindler [EMAIL PROTECTED] CC: linux-kernel@vger.kernel.org Subject: Re: USB storage does not work with 3GB of RAM, but does with 2G of RAM Date: 08 Jul 2005 21:29:37 +0200 Jon Schindler [EMAIL PROTECTED] writes: This mainly seems to be an issue with USB mass storage devices like USB memory sticks and USB hard drives (I've tried both, and neither is assigned a scsi device properly). I am still able to use my USB mouse when I have 3GB installed. I'm not sure if that makes it a USB 1.1 issue or a USB storage issue, but hopefully someone will have some insight after looking at the logs. Thanks in advance for any help. It sounds like the Nvidia EHCI controller has trouble DMAing to high addresses. Would be a bad bug if true. Does it work when you disable EHCI and only enable OHCI? (this will limit you to USB 1.1) -Andi - 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/
Re: USB storage does not work with 3GB of RAM, but does with 2G of RAM
Hi Andi, As you suggested, removing ehci_hcd (using rmmod ehci_hcd) allows the USB storage device to work. So, to answer your question, yes, the ohci_hcd driver does work with 3GB's of RAM. Still, knoppix 3.9 IS able to work with both ehci and 3GB's of RAM, so it still sounds like it's a software problem, not an nvidia hardware issue. Jon From: Andi Kleen [EMAIL PROTECTED] To: Jon Schindler [EMAIL PROTECTED] CC: linux-kernel@vger.kernel.org Subject: Re: USB storage does not work with 3GB of RAM, but does with 2G of RAM Date: 08 Jul 2005 21:29:37 +0200 Jon Schindler [EMAIL PROTECTED] writes: This mainly seems to be an issue with USB mass storage devices like USB memory sticks and USB hard drives (I've tried both, and neither is assigned a scsi device properly). I am still able to use my USB mouse when I have 3GB installed. I'm not sure if that makes it a USB 1.1 issue or a USB storage issue, but hopefully someone will have some insight after looking at the logs. Thanks in advance for any help. It sounds like the Nvidia EHCI controller has trouble DMAing to high addresses. Would be a bad bug if true. Does it work when you disable EHCI and only enable OHCI? (this will limit you to USB 1.1) -Andi - 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/ - 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/
Re: USB storage does not work with 3GB of RAM, but does with 2G of RAM
Do you know if there is a way to tell the ehci driver to do the DMA at a lower memory address? i.e. tell the kernel to reserve a block of memory (as a boot option) and then tell the ehci driver to use that area of RAM instead? Thanks again for your help, Jon From: Andi Kleen [EMAIL PROTECTED] To: Jon Schindler [EMAIL PROTECTED] CC: [EMAIL PROTECTED], linux-kernel@vger.kernel.org Subject: Re: USB storage does not work with 3GB of RAM, but does with 2G of RAM Date: Sat, 9 Jul 2005 02:56:38 +0200 On Fri, Jul 08, 2005 at 08:49:12PM -0400, Jon Schindler wrote: Hi Andi, As you suggested, removing ehci_hcd (using rmmod ehci_hcd) allows the USB storage device to work. So, to answer your question, yes, the ohci_hcd driver does work with 3GB's of RAM. Still, knoppix 3.9 IS able to work with both ehci and 3GB's of RAM, so it still sounds like it's a software problem, not an nvidia hardware issue. Knoppix is 32bit I guess. The 32bit kernel will do a lot of DMA only in the first 800-900MB (lowmem) -Andi - 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/ - 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/
Re: Kernel Oops with dual core athlon 64 (quick question)
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" <[EMAIL PROTECTED]> To: "Jon Schindler" <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - 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/
Re: Kernel Oops with dual core athlon 64 (quick question)
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" <[EMAIL PROTECTED]> To: "Jon Schindler" <[EMAIL PROTECTED]> Cc: 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" - 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/
Re: Kernel Oops with dual core athlon 64
Thanks, I'll recompile tonight and let you know if I still experience any issues. Jon - Original Message - From: "Rafael J. Wysocki" <[EMAIL PROTECTED]> To: "Jon Schindler" <[EMAIL PROTECTED]> Cc: 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" - 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/
Kernel Oops with dual core athlon 64
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 Jon Bootdata ok (command line is ro root=LABEL=/1 rhgb 3) Linux version 2.6.12.1 ([EMAIL PROTECTED]) (gcc version 4.0.0 20050519 (Red Hat 4.0.0-8)) #14 SMP Tue Jul 5 00:33:42 CDT 2005 BIOS-provided physical RAM map: BIOS-e820: - 0009f000 (usable) BIOS-e820: 0009f000 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - bfff (usable) BIOS-e820: bfff - bfff3000 (ACPI NVS) BIOS-e820: bfff3000 - c000 (ACPI data) BIOS-e820: fec0 - 0001 (reserved) ACPI: RSDP (v000 Nvidia) @ 0x000f8e80 ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x) @ 0xbfff3040 ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x) @ 0xbfff30c0 ACPI: SSDT (v001 PTLTD POWERNOW 0x0001 LTP 0x0001) @ 0xbfff7b80 ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x) @ 0xbfff7ac0 ACPI: DSDT (v001 NVIDIA AWRDACPI 0x1000 MSFT 0x010e) @ 0x Scanning NUMA topology in Northbridge 24 Number of nodes 1 Node 0 MemBase Limit bfff Using node hash shift of 24 Bootmem setup node 0 -bfff On node 0 totalpages: 786416 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 782320 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:1 Nvidia board detected. Ignoring ACPI timer override. ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 15:3 APIC version 16 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) Processor #1 15:3 APIC version 16 ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 2, version 17, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: BIOS IRQ0 pin2 override ignored. ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge) ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge) ACPI: IRQ9 used by override. ACPI: IRQ14 used by override. ACPI: IRQ15 used by override. Setting APIC routing to flat Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at c000 (gap: c000:3ec0) Checking aperture... CPU 0: aperture @ f000 size 128 MB Built 1 zonelists Kernel command line: ro root=LABEL=/1 rhgb 3 Initializing CPU#0 PID hash table entries: 4096 (order: 12, 131072 bytes) time.c: Using 1.193182 MHz PIT timer. time.c: Detected 2411.039 MHz processor. Console: colour VGA+ 80x25 Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) Memory: 3088372k/3145664k available (2382k kernel code, 0k reserved, 1584k data, 228k init) Calibrating delay loop... 4767.74 BogoMIPS (lpj=2383872) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 256 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU 0(2) -> Node 0 -> Core 0 Using local APIC timer interrupts. Detected 12.557 MHz APIC timer. Booting processor 1/1 rip 6000 rsp 810004171f58 Initializing CPU#1 Calibrating delay loop... 4816.89 BogoMIPS (lpj=2408448) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU 1(2) -> Node 0 -> Core 1 AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ stepping 02 CPU 1: Syncing TSC to CPU 0. Brought up 2 CPUs CPU 1: synchronized TSC with CPU 0 (last diff -75 cycles, maxerr 541 cycles) time.c: Using PIT/TSC based timekeeping. testing NMI watchdog ... OK. CPU0 attaching sched-domain: domain 0: span 0001 groups: 0001 domain 1: span 0003 groups: 0001 0002 domain 2: span 0003 groups: 0003 CPU1 attaching sched-domain: domain 0: span 0002 groups: 0002 domain 1: span 0003 groups:
Kernel Oops with dual core athlon 64
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 Jon Bootdata ok (command line is ro root=LABEL=/1 rhgb 3) Linux version 2.6.12.1 ([EMAIL PROTECTED]) (gcc version 4.0.0 20050519 (Red Hat 4.0.0-8)) #14 SMP Tue Jul 5 00:33:42 CDT 2005 BIOS-provided physical RAM map: BIOS-e820: - 0009f000 (usable) BIOS-e820: 0009f000 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - bfff (usable) BIOS-e820: bfff - bfff3000 (ACPI NVS) BIOS-e820: bfff3000 - c000 (ACPI data) BIOS-e820: fec0 - 0001 (reserved) ACPI: RSDP (v000 Nvidia) @ 0x000f8e80 ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x) @ 0xbfff3040 ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x) @ 0xbfff30c0 ACPI: SSDT (v001 PTLTD POWERNOW 0x0001 LTP 0x0001) @ 0xbfff7b80 ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x) @ 0xbfff7ac0 ACPI: DSDT (v001 NVIDIA AWRDACPI 0x1000 MSFT 0x010e) @ 0x Scanning NUMA topology in Northbridge 24 Number of nodes 1 Node 0 MemBase Limit bfff Using node hash shift of 24 Bootmem setup node 0 -bfff On node 0 totalpages: 786416 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 782320 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:1 Nvidia board detected. Ignoring ACPI timer override. ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 15:3 APIC version 16 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) Processor #1 15:3 APIC version 16 ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 2, version 17, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: BIOS IRQ0 pin2 override ignored. ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge) ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge) ACPI: IRQ9 used by override. ACPI: IRQ14 used by override. ACPI: IRQ15 used by override. Setting APIC routing to flat Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at c000 (gap: c000:3ec0) Checking aperture... CPU 0: aperture @ f000 size 128 MB Built 1 zonelists Kernel command line: ro root=LABEL=/1 rhgb 3 Initializing CPU#0 PID hash table entries: 4096 (order: 12, 131072 bytes) time.c: Using 1.193182 MHz PIT timer. time.c: Detected 2411.039 MHz processor. Console: colour VGA+ 80x25 Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) Memory: 3088372k/3145664k available (2382k kernel code, 0k reserved, 1584k data, 228k init) Calibrating delay loop... 4767.74 BogoMIPS (lpj=2383872) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 256 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU 0(2) - Node 0 - Core 0 Using local APIC timer interrupts. Detected 12.557 MHz APIC timer. Booting processor 1/1 rip 6000 rsp 810004171f58 Initializing CPU#1 Calibrating delay loop... 4816.89 BogoMIPS (lpj=2408448) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU 1(2) - Node 0 - Core 1 AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ stepping 02 CPU 1: Syncing TSC to CPU 0. Brought up 2 CPUs CPU 1: synchronized TSC with CPU 0 (last diff -75 cycles, maxerr 541 cycles) time.c: Using PIT/TSC based timekeeping. testing NMI watchdog ... OK. CPU0 attaching sched-domain: domain 0: span 0001 groups: 0001 domain 1: span 0003 groups: 0001 0002 domain 2: span 0003 groups: 0003 CPU1 attaching sched-domain: domain 0: span 0002 groups: 0002 domain 1: span 0003 groups: 0002
Re: Kernel Oops with dual core athlon 64
Thanks, I'll recompile tonight and let you know if I still experience any issues. Jon - Original Message - From: Rafael J. Wysocki [EMAIL PROTECTED] To: Jon Schindler [EMAIL PROTECTED] 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 - 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/
Re: Kernel Oops with dual core athlon 64 (quick question)
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 [EMAIL PROTECTED] To: Jon Schindler [EMAIL PROTECTED] 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 - 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/
Re: Kernel Oops with dual core athlon 64 (quick question)
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 [EMAIL PROTECTED] To: Jon Schindler [EMAIL PROTECTED] 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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - 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/
