Re: Nehalem with NetBSD?

[Paul Goyette <paul%whooppee.com@localhost>]

I've got a Core i7 920 that is running without any issues...

{101} cpuctl identify 0
cpu0: Intel Core i7 (Nehalem) (686-class), 2672.91 MHz, id 0x106a5
cpu0: features  0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR>
cpu0: features  0xbfebfbff<PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR>
cpu0: features  0xbfebfbff<SSE,SSE2,SS,HTT,TM,SBF>
cpu0: features2 0x98e3bd<SSE3,DTES64,MONITOR,DS-CPL,VMX,EST,TM2,SSSE3,CX16>
cpu0: features2 0x98e3bd<xTPR,PDCM,SSE41,SSE42,POPCNT>
cpu0: features3 0x28100800<SYSCALL/SYSRET,XD,EM64T>
cpu0: features4 0x1<LAHF>
cpu0: "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
cpu0: I-cache 32KB 64B/line 4-way, D-cache 32KB 64B/line 8-way
cpu0: L2 cache 256KB 64B/line 8-way
cpu0: ITLB 64 4KB entries 4-way
cpu0: DTLB 64 4KB entries 4-way
cpu0: L3 cache 8MB 64B/line 16-way
cpu0: Initial APIC ID 4
cpu0: Cluster/Package ID 0
cpu0: Core ID 2
cpu0: SMT ID 0
cpu0: family 06 model 0a extfamily 00 extmodel 01
{102}

On Thu, 29 Oct 2009, Thor Lancelot Simon wrote:

> Is anyone successfully using a Nehalem ("Core i7") CPU with NetBSD/amd64?
> I get panics trying to access various MSRs early in system boot -- the
> first from est_init_once, but if we build a custom kernel with EST
> disabled, then trying to read the core temperature sensor:
>
> db{0}> sh reg
> ds          0xa1
> es          0x1000
> fs          0
> gs          0x5442
> rdi         0xee
> rsi         0x8
> rbp         0xffffffff80ef1cc0
> rbx         0xffff8000670db0d0
> rdx         0x4
> rcx         0xee
> rax         0
> r8          0x64
> r9          0
> r10         0xffffffff80ef1bb0
> r11         0
> r12         0xffffffff80c90600  cpu_info_primary
> r13         0xffff8000670db140
> r14         0xffff8000672dc818
> r15         0xffff8000672dc418
> rip         0xffffffff80228326  rdmsr+0x6
> cs          0x8
> rflags      0x10246
> rsp         0xffffffff80ef1c88
> ss          0x10
> netbsd:rdmsr+0x6:       rdmsr
> db{0}> trace
> rdmsr() at netbsd:rdmsr+0x6
> cpu_attach() at netbsd:cpu_attach+0x21a
> config_attach_loc() at netbsd:config_attach_loc+0x160
> mpacpi_config_cpu() at netbsd:mpacpi_config_cpu+0x6d
> acpi_madt_walk() at netbsd:acpi_madt_walk+0x3f
> mpacpi_scan_apics() at netbsd:mpacpi_scan_apics+0x67
> mainbus_attach() at netbsd:mainbus_attach+0x253
> config_attach_loc() at netbsd:config_attach_loc+0x160
> cpu_configure() at netbsd:cpu_configure+0x26
> main() at netbsd:main+0x20c
>
> The cpu is an X3450.
>
> --
> Thor Lancelot Simon                                        
> tls%rek.tjls.com@localhost
>    "Even experienced UNIX users occasionally enter rm *.* at the UNIX
>     prompt only to realize too late that they have removed the wrong
>     segment of the directory structure." - Microsoft WSS whitepaper

-------------------------------------------------------------------------
|   Paul Goyette   | PGP DSS Key fingerprint: |  E-mail addresses:      |
| Customer Service | FA29 0E3B 35AF E8AE 6651 |  paul at whooppee.com   |
| Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net |
| Kernel Developer |                          | pgoyette at netbsd.org  |
-------------------------------------------------------------------------