i686 quirk for AMD Geode
in [Kernel]
|
Prev: [PATCH 1/1] PM: Thaws refrigerated and to be exited kernel threads
Next: drm/ksm -> s2disk -> resume -> [drm:r100_ring_test] *ERROR* radeon: ring test failed (sracth(0x15E4)=0xCAFEDEAD)
From: Lennart Sorensen on 17 Nov 2009 09:40 On Tue, Nov 17, 2009 at 11:59:29AM +0000, Alan Cox wrote: > > Trying rdmsr from msr-tools 1.2 gives me: > > > > # ./rdmsr -x 0x00001810 > > rdmsr: CPU 0 cannot read MSR 0x00001810 > > > > Hmm, now what? > > Beats me - I thought the region registers were read/write. Actually it seems I can't read any MSRs on it. Using the same kernel, same msr module, same rdmsr on a Geode LX system works fine. I can read MSRs no problem. Seems the msr module isn't working on the Geode SC1200 (and hence possibly the GX1). -- Len Sorensen -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Valdis.Kletnieks on 17 Nov 2009 11:50 On Tue, 17 Nov 2009 11:59:29 GMT, Alan Cox said: > > Trying rdmsr from msr-tools 1.2 gives me: > > > > # ./rdmsr -x 0x00001810 > > rdmsr: CPU 0 cannot read MSR 0x00001810 > > > > Hmm, now what? > > Beats me - I thought the region registers were read/write. Umm... 'modprobe msr'? (Recently I had what *looked* like an xorg server bug, turned out to be a missing CONFIG_INPUT_EVDEV.. Whoops. ;)
From: H. Peter Anvin on 17 Nov 2009 11:50 On 11/17/2009 06:34 AM, Lennart Sorensen wrote: > On Tue, Nov 17, 2009 at 11:59:29AM +0000, Alan Cox wrote: >>> Trying rdmsr from msr-tools 1.2 gives me: >>> >>> # ./rdmsr -x 0x00001810 >>> rdmsr: CPU 0 cannot read MSR 0x00001810 >>> >>> Hmm, now what? >> >> Beats me - I thought the region registers were read/write. > > Actually it seems I can't read any MSRs on it. > > Using the same kernel, same msr module, same rdmsr on a Geode LX system > works fine. I can read MSRs no problem. Seems the msr module isn't > working on the Geode SC1200 (and hence possibly the GX1). > That would seem highly unlikely ... unless the MSR flag isn't exposed in CPUID. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Lennart Sorensen on 17 Nov 2009 12:20 On Tue, Nov 17, 2009 at 08:43:45AM -0800, H. Peter Anvin wrote: > On 11/17/2009 06:34 AM, Lennart Sorensen wrote: > > On Tue, Nov 17, 2009 at 11:59:29AM +0000, Alan Cox wrote: > >>> Trying rdmsr from msr-tools 1.2 gives me: > >>> > >>> # ./rdmsr -x 0x00001810 > >>> rdmsr: CPU 0 cannot read MSR 0x00001810 > >>> > >>> Hmm, now what? > >> > >> Beats me - I thought the region registers were read/write. > > > > Actually it seems I can't read any MSRs on it. > > > > Using the same kernel, same msr module, same rdmsr on a Geode LX system > > works fine. I can read MSRs no problem. Seems the msr module isn't > > working on the Geode SC1200 (and hence possibly the GX1). > > > > That would seem highly unlikely ... unless the MSR flag isn't exposed in > CPUID. That would be odd yes. # cat /proc/cpuinfo processor : 0 vendor_id : CyrixInstead cpu family : 5 model : 9 model name : Geode(TM) Integrated Processor by National Semi stepping : 1 cpu MHz : 266.612 cache size : 16 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu tsc msr cx8 cmov mmx cxmmx bogomips : 534.41 clflush size : 32 power management: That part looks OK. So why is reading MSRs not working on this stupid CPU at any of the addresses the data book says should work. -- Len Sorensen -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Lennart Sorensen on 17 Nov 2009 12:30
On Tue, Nov 17, 2009 at 11:48:47AM -0500, Valdis.Kletnieks(a)vt.edu wrote: > Umm... 'modprobe msr'? > > (Recently I had what *looked* like an xorg server bug, turned out to be a > missing CONFIG_INPUT_EVDEV.. Whoops. ;) I did. Makes no difference. If I unload it I get the same error. # modinfo msr filename: /lib/modules/2.6.26-2-gx1/kernel/arch/x86/kernel/msr.ko author: H. Peter Anvin <hpa(a)zytor.com> description: x86 generic MSR driver license: GPL vermagic: 2.6.26-2-gx1 mod_unload GEODEGX1 depends: # lsmod |grep msr msr 2692 0 I don't get it. -- Len Sorensen -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |