I'd like to know if the 2nd CPU is being used. I'm confused because
of the lack of Flags on cpu1 while cpu0 is loaded with them. It looks
like the 2nd CPU is actually a virtual CPU via Hyperthreading.
If you look at the dmesg I posted, and compare the top with this dmesg
(
http://www.nycbug.org/?NAV=dmesgd;f_dmesg=Xeon%20&%20cpu1%20&%20OpenBSD;f_bsd=;f_nick=;f_descr=;dmesgid=1787#1787
), it's a little wierd that my dmesg lists all the flags for the first
CPU and 4 for the 2nd, while this one that I just linked lists all the
flags for both CPUs.
I also did re-enable Hyperthreading, and the dmesg didn't change, but
the whole "lack of flags" thing is what's throwing me off.
-Jesse
On 6/13/06, Maxim Bourmistrov <[EMAIL PROTECTED]> wrote:
> What are you trying to accomplish?
> AFAIK, HTT is not supported in OpenBSD.
> So re-enable it in BIOS - OS will ignore it anyway.
>
> On Tuesday 13 June 2006 06:01, Jesse Gumm wrote:
> > Hello,
> >
> > I'm booting a Dual Xeon 2.4 Machine (just got it a few days ago), and having
> > a bit of difficulty discerning of the 2nd CPU is actually being used by
> > OpenBSD 3.9.
> >
> > Before posting the dmesg, I'll quick state what I've done so far, and why I
> > don't actually think the 2nd cpu is taking.
> >
> > I started with FreeBSD (I'm traditionally an OpenBSD user, but I thought I'd
> > give FreeBSD a try), and when FreeBSD booted with SMP support, it found 4
> > processors (2 Xeons each acting like 2 because of Hyperthreading, hence 4
> > processors). Which was fine, but after a bit I decided I didn't
> > particularly like FreeBSD, and decided to go back to OpenBSD.
> >
> > When Booting OpenBSD from bsd.mp, however, I noticed that it only detected 2
> > CPUs. I thought that was odd, and that either
> > 1) OpenBSD was ignoring Hyperthreading, or
> > 2) OpenBSD recognized Hyperthreading but didn't give it it's own CPU, or
> > 3) OpenBSD only recognized 1 processor, but gave the "Virtual CPU" it's own
> > CPU.
> >
> > After reading a bit and determining that BSD doesn't like Hyperthreading, I
> > disabled it in BIOS, and booted again, and the dmesg didn't change, which I
> > found suspicious.
> >
> > It still says only 2 CPUs, however, the dmesg doesn't look....right, and I
> > don't particularly want to take the processor off to test this, but I can, I
> > figured maybe someone can give me a better answer.
> >
> > In short, the dmesg looks off. Notice how cpu0 lists a whole slew of bits
> > "FPU, MMC, SSE, etc" while cpu1 lists 4 bits: FPU,CX8,APIC,CNXT-ID
> >
> > I tried compiling a fresh GENERIC.MP kernel to see if that'd resolve the
> > situation, but it did nothing to help with this.
> >
> > My question, then, is: Is my 2nd CPU actually being recognized, and if not,
> > why is OpenBSD still seeing the Hyperthreading processor when HT is disabled
> > from BIOS, and what can I do to fix/troubleshoot this?
> >
> > Here's the dmesg below (I posted the whole thing instead of just the cpu and
> > bus parts in case there might be something I'm missing):
> >
> > cpu0: Intel(R) Xeon(TM) CPU 2.40GHz ("GenuineIntel" 686-class) 2.40 GHz
> > cpu0:
> >
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,CNXT-ID
> > real mem = 1073233920 (1048080K)
> > avail mem = 972546048 (949752K)
> > using 4278 buffers containing 53764096 bytes (52504K) of memory
> > mainbus0 (root)
> > bios0 at mainbus0: AT/286+(40) BIOS, date 09/17/03, BIOS32 rev. 0 @ 0xfd7d1
> > pcibios0 at bios0: rev 2.1 @ 0xf0000/0xffff
> > pcibios0: PCI BIOS has 8 Interrupt Routing table entries
> > pcibios0: PCI Exclusive IRQs: 9 10 11 15
> > pcibios0: PCI Interrupt Router at 000:15:0 ("ServerWorks CSB5" rev 0x00)
> > pcibios0: PCI bus #0 is the last bus
> > bios0: ROM list: 0xc0000/0x8000 0xc8000/0x1800 0xc9800/0x4000 0xcd800/0x1800
> > mainbus0: Intel MP Specification (Version 1.4) (IBM ENSW TURQUIOSESMP)
> > cpu0 at mainbus0: apid 0 (boot processor)
> > cpu0: apic clock running at 99 MHz
> > cpu1 at mainbus0: apid 6 (application processor)
> > cpu1: Intel(R) Xeon(TM) CPU 2.40GHz ("GenuineIntel" 686-class)
> > cpu1: FPU,CX8,APIC,CNXT-ID
> > mainbus0: bus 0 is type PCI
> > mainbus0: bus 1 is type PCI
> > mainbus0: bus 2 is type PCI
> > mainbus0: bus 3 is type ISA
> > ioapic0 at mainbus0: apid 14 pa 0xfec00000, version 11, 16 pins
> > ioapic1 at mainbus0: apid 13 pa 0xfec01000, version 11, 16 pins
> > ioapic2 at mainbus0: apid 12 pa 0xfec02000, version 11, 16 pins
> > pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
> > pchb0 at pci0 dev 0 function 0 "ServerWorks CMIC-WS Host (GC-LE)" rev 0x13
> > pchb1 at pci0 dev 0 function 1 "ServerWorks CMIC-WS Host (GC-LE)" rev 0x00
> > pchb2 at pci0 dev 0 function 2 "ServerWorks CMIC-LE" rev 0x00
> > pci1 at pchb2 bus 1
> > mpt0 at pci1 dev 1 function 0 "Symbios Logic 53c1030" rev 0x07: apic 13 int
> > 6 (irq 9)
> > scsibus0 at mpt0: 16 targets
> > sd0 at scsibus0 targ 0 lun 0: <LSILOGIC, 1030 IM, 1000> SCSI2 0/direct fixed
> > sd0: 69878MB, 69879 cyl, 16 head, 127 sec, 512 bytes/sec, 143110145 sec
> > total
> > mpt0: target 0 Asynchronous at 0MHz width 8bit offset 0 QAS 0 DT 0 IU 0
> > fxp0 at pci1 dev 2 function 0 "Intel 8255x" rev 0x0c, i82550: apic 13 int 2
> > (irq 3), address 00:07:e9:0c:15:c7
> > inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 4
> > vga1 at pci0 dev 1 function 0 "ATI Rage XL" rev 0x27
> > wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> > wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> > piixpm0 at pci0 dev 15 function 0 "ServerWorks CSB5" rev 0x93
> > iic0 at piixpm0
> > pciide0 at pci0 dev 15 function 1 "ServerWorks CSB5 IDE" rev 0x93: DMA
> > atapiscsi0 at pciide0 channel 1 drive 0
> > scsibus1 at atapiscsi0: 2 targets
> > cd0 at scsibus1 targ 0 lun 0: <LG, CD-ROM CRN-8245B, 1.16> SCSI0 5/cdrom
> > removable
> > cd0(pciide0:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 2
> > ohci0 at pci0 dev 15 function 2 "ServerWorks OSB4/CSB5 USB" rev 0x05ioapic0:
> > conflicting map entries for pin 11
> > : irq 11, version 1.0, legacy support
> > usb0 at ohci0: USB revision 1.0
> > uhub0 at usb0
> > uhub0: ServerWorks OHCI root hub, rev 1.00/1.00, addr 1
> > uhub0: 4 ports with 4 removable, self powered
> > pcib0 at pci0 dev 15 function 3 "ServerWorks CSB5 LPC" rev 0x00
> > pchb3 at pci0 dev 17 function 0 "ServerWorks CIOB-X2 PCIX" rev 0x03
> > pchb4 at pci0 dev 17 function 2 "ServerWorks CIOB-X2 PCIX" rev 0x03
> > pci2 at pchb4 bus 2
> > bge0 at pci2 dev 1 function 0 "Broadcom BCM5703X" rev 0x02, BCM5703 A2
> > (0x1002): apic 13 int 8 (irq 4), address 00:09:6b:8c:b3:fc
> > brgphy0 at bge0 phy 1: BCM5703 10/100/1000baseT PHY, rev. 2
> > bge1 at pci2 dev 2 function 0 "Broadcom BCM5703X" rev 0x02, BCM5703 A2
> > (0x1002): apic 13 int 9 (irq 5), address 00:09:6b:8c:b3:fd
> > brgphy1 at bge1 phy 1: BCM5703 10/100/1000baseT PHY, rev. 2
> > isa0 at pcib0
> > isadma0 at isa0
> > pckbc0 at isa0 port 0x60/5
> > pckbd0 at pckbc0 (kbd slot)
> > pckbc0: using irq 1 for kbd slot
> > wskbd0 at pckbd0: console keyboard, using wsdisplay0
> > pcppi0 at isa0 port 0x61
> > midi0 at pcppi0: <PC speaker>
> > spkr0 at pcppi0
> > npx0 at isa0 port 0xf0/16: using exception 16
> > fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
> > fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
> > biomask 0 netmask 0 ttymask 0
> > pctr: user-level cycle counter enabled
> > uhidev0 at uhub0 port 3 configuration 1 interface 0
> > uhidev0: Chicony USB Gaming Keyboard Pro, rev 2.00/4.03, addr 2, iclass 3/1
> > ukbd0 at uhidev0: 8 modifier keys, 6 key codes
> > wskbd1 at ukbd0 mux 1
> > wskbd1: connecting to wsdisplay0
> > uhidev1 at uhub0 port 3 configuration 1 interface 1
> > uhidev1: Chicony USB Gaming Keyboard Pro, rev 2.00/4.03, addr 2, iclass 3/0
> > uhidev1: 3 report ids
> > uhid0 at uhidev1 reportid 1: input=4, output=0, feature=0
> > uhid1 at uhidev1 reportid 2: input=1, output=0, feature=0
> > uhid2 at uhidev1 reportid 3: input=0, output=0, feature=4
> > uhidev2 at uhub0 port 3 configuration 1 interface 2
> > uhidev2: Chicony USB Gaming Keyboard Pro, rev 2.00/4.03, addr 2, iclass 3/0
> > uhid3 at uhidev2: input=2, output=0, feature=0
> > dkcsum: sd0 matches BIOS drive 0x80
> >
> > Thank you,
> > -Jesse Gumm
