yet another ppb
Found on Soekris Engineering net1841 quad nic card.
Index: sys/dev/pci/pcidevs
===
RCS file: /cvs/src/sys/dev/pci/pcidevs,v
retrieving revision 1.1670
diff -u -r1.1670 pcidevs
--- sys/dev/pci/pcidevs 14 Mar 2013 14:47:00 - 1.1670
+++ sys/dev/pci/pcidevs 24 Mar 2013 18:52:19 -
@@ -2397,8 +2397,9 @@
product IDT 89HPES24N3A0x801c 89HPES24N3A
product IDT 89HPES24T6 0x802e 89HPES24T6
product IDT 89HPES4T4 0x803a 89HPES4T4
+product IDT 89HPES5T5ZB0x803c 89HPES5T5ZB
product IDT 89HPES24T3G2 0x806a 89HPES24T3G2
/* Industrial Computer Source */
product INDCOMPSRC WDT50x 0x22c0 WDT 50x Watchdog Timer
-
The above change changes this
ppb22 at pci19 dev 5 function 0 vendor "IDT", unknown product 0x803c rev
0x0e
pci23 at ppb22 bus 23
em11 at pci23 dev 0 function 0 "Intel PRO/1000 MT (82574L)" rev 0x00: msi,
address 00:00:24:cf:2d:03
into this
ppb22 at pci19 dev 5 function 0 "IDT 89HPES5T5ZB" rev 0x0e
pci23 at ppb22 bus 23
em11 at pci23 dev 0 function 0 "Intel PRO/1000 MT (82574L)" rev 0x00: msi,
address 00:00:24:cf:2d:03
It's a purely cosmetic change, but can someone please commit this?
Regards, Mitja
(and yes, it's a 12 nic Soekris ne6501 :)
OpenBSD 5.3-current (GENERIC) #15: Thu Nov 15 04:15:36 CET 2012
r...@msata.muzenic.net:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Genuine Intel(R) CPU @ 1.60GHz ("GenuineIntel" 686-class) 1.61 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,
ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,E
ST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,LAHF,PERF
real mem = 2146873344 (2047MB)
avail mem = 2100387840 (2003MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 20/21/15, BIOS32 rev. 0 @ 0xfac40
mpbios0 at bios0: Intel MP Specification 1.4
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 100MHz
cpu at mainbus0: not configured
mpbios0: bus 0 is type PCI
mpbios0: bus 64 is type ISA
ioapic0 at mainbus0: apid 0 pa 0xfec0, version 20, 24 pins
pcibios0 at bios0: rev 2.0 @ 0xf/0x1
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf3880/96 (4 entries)
pcibios0: no compatible PCI ICU found: ICU vendor 0x8086 product 0x8186
pcibios0: Warning, unable to fix up PCI interrupt routing
pcibios0: PCI bus #23 is the last bus
bios0: ROM list: 0xc8000/0x2400 0xca800/0x4c00 0xcf800/0xee00
cpu0: unknown Enhanced SpeedStep CPU, msr 0x0616101d0600101d
cpu0: using only highest and lowest power states
cpu0: Enhanced SpeedStep 1601 MHz: speeds: 1600, 600 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel E600 Host" rev 0x05
pchb1 at pci0 dev 1 function 0 "Intel E600 Config" rev 0x00
ppb0 at pci0 dev 23 function 0 "Intel E600 PCIE" rev 0x00
pci1 at ppb0 bus 1
ppb1 at pci1 dev 0 function 0 "Intel EG20T PCIE" rev 0x01
pci2 at ppb1 bus 2
"Intel EG20T Packet Hub" rev 0x01 at pci2 dev 0 function 0 not configured
"Intel EG20T Ethernet" rev 0x01 at pci2 dev 0 function 1 not configured
"Intel EG20T GPIO" rev 0x00 at pci2 dev 0 function 2 not configured
ohci0 at pci2 dev 2 function 0 "Intel EG20T USB" rev 0x01: apic 0 int 19,
version 1.0, legacy support
ohci1 at pci2 dev 2 function 1 "Intel EG20T USB" rev 0x01: apic 0 int 19,
version 1.0, legacy support
ohci2 at pci2 dev 2 function 2 "Intel EG20T USB" rev 0x01: apic 0 int 19,
version 1.0, legacy support
ehci0 at pci2 dev 2 function 3 "Intel EG20T USB" rev 0x01: apic 0 int 19
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
"Intel EG20T USB Client" rev 0x01 at pci2 dev 2 function 4 not configured
sdhc0 at pci2 dev 4 function 0 "Intel EG20T SDIO" rev 0x01: apic 0 int 18
sdmmc0 at sdhc0
sdhc1 at pci2 dev 4 function 1 "Intel EG20T SDIO" rev 0x01: apic 0 int 18
sdmmc1 at sdhc1
ahci0 at pci2 dev 6 function 0 "Intel EG20T AHCI" rev 0x01: msi, AHCI 1.1
scsibus0 at ahci0: 32 targets
sd0 at scsibus0 targ 0 lun 0: SCSI3 0/direct
fixed t10.ATA_KingSpec_KSM-mSATA.5-008SJ_MSA051109192_
sd0: 7641MB, 512 bytes/sector, 15649200 sectors
ohci3 at pci2 dev 8 function 0 "Intel EG20T USB" rev 0x01: apic 0 int 16,
version 1.0, legacy support
ohci4 at pci2 dev 8 function 1 "Intel EG20T USB" rev 0x01: apic 0 int 16,
version 1.0, legacy support
ohci5 at pci2 dev 8 function 2 "Intel EG20T USB" rev 0x01: apic 0 int 16,
version 1.0, legacy support
ehci1 at pci2 dev 8 function 3 "Intel EG20T USB" rev 0x01: apic 0 int 16
usb1 at ehci1: USB revision 2.0
uhub1 at usb1 "Intel EHCI root hub" rev 2.00/1.00 addr 1
"Intel EG20T DMA" rev 0x00 at pci2 dev 10 function 0 not configured
puc0 at pci2 dev 10 function 1 "Intel EG20T Serial" rev 0x00: ports: 1 com
com3 at puc0 port 0 apic 0 int 19: ti16750, 64 byte fifo
puc1 at pci2 dev 10 function 2 "Intel EG20T Serial" rev 0x00: ports: 1 com
com4 at puc1 port 0 apic 0 int 19: ti16750, 64 byte fifo
puc2 at
Re: Intel Atom E600 watchdog(4) support
Works for me on net6501 on i386 GENERIC and GENERIC.MP after a succesfull watchdog fire: e600pcib0 at pci0 dev 31 function 0 "Intel E600 LPC" rev 0x00: watchdog, reboot on timeout It did fire a bit too early though, my watchdog period was set to 32 seconds and the machine did reset after 26 seconds on my stopwatch. Similarly, with a 60 second period it fired after ~50 seconds. Don't know if it really matters though Finally, can you mention that the valid period range is 1-600 seconds? The code does it right by silently lowering a too-high period to 600, but it would be nice to have it mentioned in the manpages too. [msata] # sysctl kern.watchdog.period=1 kern.watchdog.period: 0 -> 1 [msata] # sysctl kern.watchdog.period kern.watchdog.period=1 [msata] # sysctl kern.watchdog.period=1 kern.watchdog.period: 1 -> 1 [msata] # sysctl kern.watchdog.period kern.watchdog.period=600 Regards, Mitja P.S. While I was composing this reply some other mails have come through. How about esixoopcib ? :) > -Original Message- > From: owner-t...@openbsd.org [mailto:owner-t...@openbsd.org] On Behalf > Of Jonathan Gray > Sent: Thursday, May 24, 2012 7:23 AM > To: Matt Dainty > Cc: tech@openbsd.org > Subject: Re: Intel Atom E600 watchdog(4) support > > As a general policy drivers do not have numbers in their name, > so it will have to be renamed. > > I'll have a look into trying it on a net6501 I have here with i386. > > On Wed, May 23, 2012 at 04:52:03PM -0400, Matt Dainty wrote: > > Attached are some patches that add support for the watchdog device on > > boards based on the Intel Atom E600 series such as the Soekris > net6501. > > > > Based on existing drivers such as amdpcib(4), ichpcib(4) and > ichwdt(4) > > I've created an e600pcib(4) to override the standard pcib(4) which > can > > then access the watchdog device. > > > > Here's the original dmesg: > > > > ---8<--- > > pcib0 at pci0 dev 31 function 0 "Intel E600 LPC" rev 0x00 > > isa0 at pcib0 > > ---8<--- > > > > Here's with my changes: > > > > ---8<--- > > e600pcib0 at pci0 dev 31 function 0 "Intel E600 LPC" rev 0x00: > watchdog > > isa0 at e600pcib0 > > ---8<--- > > > > I tested the watchdog by setting kern.watchdog.period to 60 and then > > breaking into ddb and starting a stopwatch and timing until my > net6501 > > resets, it take near enough to 60 seconds that I'm happy it's > working. > > > > On a watchdog-triggered reboot, I've done similar to ichwdt(4): > > > > ---8<--- > > e600pcib0 at pci0 dev 31 function 0 "Intel E600 LPC" rev 0x00: > watchdog, reboot on timeout > > isa0 at e600pcib0 > > ---8<--- > > > > I've included the driver itself, man pages, changes to GENERIC and > the > > various infrastructure files. > > > > I'm using it with GENERIC.MP on amd64 and I compile tested it on > i386. > > > > Any comments? > > > > Matt > > > > --- /dev/null Wed May 23 21:01:50 2012 > > +++ sys/dev/pci/e600pcib.c Wed May 23 21:00:44 2012 > > @@ -0,0 +1,220 @@ > > +/* $OpenBSD$ */ > > + > > +/* > > + * Copyright (c) 2012 Matt Dainty > > + * > > + * Permission to use, copy, modify, and distribute this software for > any > > + * purpose with or without fee is hereby granted, provided that the > above > > + * copyright notice and this permission notice appear in all copies. > > + * > > + * THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL > WARRANTIES > > + * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF > > + * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE > LIABLE FOR > > + * ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY > DAMAGES > > + * WHATSOEVER RESULTING FROM LOSS OF MIND, USE, DATA OR PROFITS, > WHETHER IN > > + * AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, > ARISING OUT > > + * OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. > > + */ > > + > > +/* > > + * Intel Atom E600 series LPC bridge also containing watchdog > > + */ > > + > > +#include > > +#include > > +#include > > + > > +#include > > + > > +#include > > +#include > > +#include > > + > > +#defineE600_LPC_SMBA 0x40/* SMBus Base Address */ > > +#defineE600_LPC_GBA0x44/* GPIO Base Address */ > > +#defineE600_LPC_WDTBA 0x84/* WDT Base Address */ > > + > > +#defineE600_WDT_SIZE 64 /* I/O region size */ > > +#defineE600_WDT_PV10x00/* Preload Value 1 > Register */ > > +#defineE600_WDT_PV20x04/* Preload Value 2 > Register */ > > +#defineE600_WDT_RR00x0c/* Reload Register 0 */ > > +#defineE600_WDT_RR10x0d/* Reload Register 1 */ > > +#defineE600_WDT_RR1_RELOAD (1 << 0)/* WDT Reload Flag */ > > +#defineE600_WDT_RR1_TIMEOUT(1 << 1)/* WDT Timeout Flag */ > > +#defineE600_WDT_WDTCR 0x10/* WDT Configuration > Re
pf pptp nat
Hey, there was a longish thread here roughly 4 years ago titled "[patch] pf PPTP nat passthrough patch." [1] And it was said back then that it's close to getting committed. Anybody knows the state of this? I know that pf changed significantly since, so I doubt those patches still apply [1] http://marc.info/?t=12054892454&r=1&w=2 Regards, Mitja
Re: tcpdump IKE dissector: print UDP_ENCAP_*_DRAFT
For what it's worth, I like the idea.
Mitja
> -Original Message-
> From: owner-t...@openbsd.org [mailto:owner-t...@openbsd.org] On Behalf Of
> Stuart Henderson
> Sent: Saturday, January 28, 2012 10:54 AM
> To: tech
> Subject: tcpdump IKE dissector: print UDP_ENCAP_*_DRAFT
>
> cizco still use the IDs from the draft for nat-t, let tcpdump
> print them, useful for diagnosis even if the isakmpd patches are too
> messy. OK?
>
> Index: ike.h
> ===
> RCS file: /cvs/src/usr.sbin/tcpdump/ike.h,v
> retrieving revision 1.23
> diff -u -p -r1.23 ike.h
> --- ike.h 7 Jun 2010 16:20:58 - 1.23
> +++ ike.h 28 Jan 2012 09:52:30 -
> @@ -382,10 +382,6 @@
> #define IPSEC_ATTR_DURATION_INITIALIZER \
> { "NONE", "SECONDS", "KILOBYTES", \
> }
> -#define IPSEC_ATTR_ENCAP_INITIALIZER \
> - { "NONE", "TUNNEL", "TRANSPORT", "UDP_ENCAP_TUNNEL",\
> - "UDP_ENCAP_TRANSPORT" \
> - }
> #define IPSEC_ATTR_AUTH_INITIALIZER \
> { "NONE", "HMAC_MD5", "HMAC_SHA", "DES_MAC", "KPDK",\
> "HMAC_SHA2_256", "HMAC_SHA2_384", "HMAC_SHA2_512",\
> @@ -403,6 +399,15 @@
> #define IPCOMP_INITIALIZER \
> { "NONE", "OUI", "DEFLATE", "LZS", "V42BIS",\
> }
> +static struct tok ipsec_attr_encap[] = {
> + { 0,"NONE" },
> + { 1,"TUNNEL" },
> + { 2,"TRANSPORT" },
> + { 3,"UDP_ENCAP_TUNNEL" },
> + { 4,"UDP_ENCAP_TRANSPORT" },
> + { 61443, "UDP_ENCAP_TUNNEL_DRAFT" },/*
draft-ietf-ipsec-nat-t-ike */
> + { 61444, "UDP_ENCAP_TRANSPORT_DRAFT" } /*
draft-ietf-ipsec-nat-t-ike */
> +};
>
> /*
> * IKE mode config.
> Index: print-ike.c
> ===
> RCS file: /cvs/src/usr.sbin/tcpdump/print-ike.c,v
> retrieving revision 1.35
> diff -u -p -r1.35 print-ike.c
> --- print-ike.c 7 Jun 2010 16:20:58 - 1.35
> +++ print-ike.c 28 Jan 2012 09:52:30 -
> @@ -303,7 +303,6 @@ ike_attribute_print (u_int8_t *buf, u_in
> static char *attr_gtype[] = IKE_ATTR_GROUP_INITIALIZER;
> static char *attr_ltype[] = IKE_ATTR_SA_DURATION_INITIALIZER;
> static char *ipsec_attrs[] = IPSEC_ATTR_INITIALIZER;
> - static char *ipsec_attr_encap[] = IPSEC_ATTR_ENCAP_INITIALIZER;
> static char *ipsec_attr_auth[] = IPSEC_ATTR_AUTH_INITIALIZER;
> static char *ipsec_attr_ltype[] = IPSEC_ATTR_DURATION_INITIALIZER;
>
> @@ -357,10 +356,12 @@ ike_attribute_print (u_int8_t *buf, u_in
> else
> switch(type) {
> CASE_PRINT(IPSEC_ATTR_SA_LIFE_TYPE,
ipsec_attr_ltype);
> - CASE_PRINT(IPSEC_ATTR_ENCAPSULATION_MODE,
> - ipsec_attr_encap);
> CASE_PRINT(IPSEC_ATTR_AUTHENTICATION_ALGORITHM,
> ipsec_attr_auth);
> + case IPSEC_ATTR_ENCAPSULATION_MODE:
> + printf("%s", tok2str(ipsec_attr_encap,
> + "%d", val));
> + break;
> default:
> printf("%d", val);
> }
Re: isakmpd(8) man page: clarify IKE packet capture file
For what it's worth, I'd like to see this mentioned, not necessarly in those exact words though. How about " optionally, an alternate file inside /var/run/ can be specified." ? Mitja > -Original Message- > From: owner-t...@openbsd.org [mailto:owner-t...@openbsd.org] On Behalf Of > Lawrence Teo > Sent: Sunday, June 05, 2011 4:20 AM > To: tech@openbsd.org > Subject: isakmpd(8) man page: clarify IKE packet capture file > > isakmpd(8)'s -L command-line option enables IKE packet capture. It is > documented on the isakmpd(8) man page as follows: > > -L Enable IKE packet capture. When this option is given, isakmpd >will capture to file an unencrypted copy of the negotiation >packets it is sending and receiving. This file can later be read >by tcpdump(8) and other utilities using pcap(3). > > The documentation is currently not clear exactly which file isakmpd > will use to log the packet captures. The correct file *is* listed in > the FILES section (it is /var/run/isakmpd.pcap); however, I think it > would be helpful to mention that file in the description of -L itself, > so that the reader would not have to hunt for it throughout the entire > man page. > > Similarly, the "p on/off" FIFO commands to enable IKE packet capture > are documented as follows: > > p on[=] > p off Enable or disable cleartext IKE packet capture. > When enabling, optionally specify which file isakmpd should > capture the packets to. > > Again, the default file is not mentioned. What is also not documented > is, if an alternate file is specified via "p on=/path/to/altfile", its > path must begin with /var/run (I found out the hard way :)). > > The following diff improves the documentation by specifying the default > packet capture file in the text for -L itself, and also documents the > restriction about the alternate file path for the "p on" FIFO command > (borrowing some text from the -l option). > > Any thoughts or comments? > > Lawrence > > > Index: isakmpd.8 > === > RCS file: /cvs/src/sbin/isakmpd/isakmpd.8,v > retrieving revision 1.107 > diff -u -p -r1.107 isakmpd.8 > --- isakmpd.8 7 Jun 2010 08:38:09 - 1.107 > +++ isakmpd.8 5 Jun 2011 02:09:21 - > @@ -249,7 +249,9 @@ or > Enable IKE packet capture. > When this option is given, > .Nm > -will capture to file an unencrypted copy of the negotiation packets it > +will capture to > +.Pa /var/run/isakmpd.pcap > +an unencrypted copy of the negotiation packets it > is sending and receiving. > This file can later be read by > .Xr tcpdump 8 > @@ -469,9 +471,12 @@ In passive mode no packets are sent to p > .Xc > .It Ic p off > Enable or disable cleartext IKE packet capture. > -When enabling, optionally specify which file > -.Nm > -should capture the packets to. > +When enabling, packets are captured to > +.Pa /var/run/isakmpd.pcap ; > +optionally, an alternate file can be specified but > +note that only paths beginning with > +.Pa /var/run > +are allowed. > .Pp > .It Ic Q > Cleanly shutdown the daemon, as when sent a
new pcidevs and W83627DHG-P attach
While testing a new machine I came across some new pcidevs (apologies if
tabs change to spaces):
Index: pcidevs
===
RCS file: /cvs/src/sys/dev/pci/pcidevs,v
retrieving revision 1.1563
diff -u -r1.1563 pcidevs
--- pcidevs 1 Jul 2010 23:09:39 - 1.1563
+++ pcidevs 18 Jul 2010 11:25:52 -
@@ -3031,6 +3031,7 @@
product INTEL 82801JD_PCIE_5 0x3a78 82801JD PCIE
product INTEL 82801JD_PCIE_6 0x3a7a 82801JD PCIE
product INTEL 82801JD_LAN 0x3a7c 82801JD LAN
+product INTEL 3400_LPC_3 0x3b00 3400 LPC
product INTEL P55_LPC 0x3b02 P55 LPC
product INTEL 3400_LPC_1 0x3b07 3400 LPC
product INTEL 3400_LPC_2 0x3b10 3400 LPC
@@ -4530,6 +4531,7 @@
product PLX PEX_8533 0x8533 PEX 8533
product PLX PEX_8547 0x8547 PEX 8547
product PLX PEX_8548 0x8548 PEX 8548
+product PLX PEX_8616 0x8616 PEX 8616
product PLX PEX_8624 0x8624 PEX 8624
product PLX PEX_8648 0x8648 PEX 8648
product PLX 9016 0x9016 I/O 9016
There's a third one, but I have no idea what it is - some sort of PCIe
bridge?
ppb5 at pci0 dev 6 function 0 vendor "Intel", unknown product 0x0043
rev 0x12: apic 6 int 16 (irq 10)
Also, the following makes the wbsio attach and the sensors show up:
Index: sys/dev/isa/wbsio.c
===
RCS file: /cvs/src/sys/dev/isa/wbsio.c,v
retrieving revision 1.5
diff -u -r1.5 wbsio.c
--- sys/dev/isa/wbsio.c 29 Mar 2009 21:53:52 - 1.5
+++ sys/dev/isa/wbsio.c 18 Jul 2010 11:31:09 -
@@ -47,6 +47,7 @@
#define WBSIO_ID_W83627THF 0x82
#define WBSIO_ID_W83627EHF 0x88
#define WBSIO_ID_W83627DHG 0xa0
+#define WBSIO_ID_W83627DHGP0xb0
#define WBSIO_ID_W83627SF 0x59
#define WBSIO_ID_W83637HF 0x70
#define WBSIO_ID_W83697HF 0x60
@@ -135,6 +136,7 @@
case WBSIO_ID_W83627THF:
case WBSIO_ID_W83627EHF:
case WBSIO_ID_W83627DHG:
+ case WBSIO_ID_W83627DHGP:
case WBSIO_ID_W83637HF:
case WBSIO_ID_W83697HF:
ia->ipa_nio = 1;
@@ -182,6 +184,9 @@
break;
case WBSIO_ID_W83627DHG:
printf(": W83627DHG");
+ break;
+ case WBSIO_ID_W83627DHGP:
+ printf(": W83627DHG-P");
break;
case WBSIO_ID_W83637HF:
printf(": W83637HF");
I get:
wbsio0 at isa0 port 0x2e/2: W83627DHG-P rev 0x73
lm1 at wbsio0 port 0xa10/8: W83627DHG
and
# sysctl hw.sensors
hw.sensors.cpu0.temp0=44.00 degC
hw.sensors.lm1.temp0=57.00 degC
hw.sensors.lm1.temp1=45.50 degC
hw.sensors.lm1.temp2=41.00 degC
hw.sensors.lm1.fan2=84375 RPM
hw.sensors.lm1.volt0=0.92 VDC (VCore)
hw.sensors.lm1.volt1=5.02 VDC (+12V)
hw.sensors.lm1.volt2=3.33 VDC (+3.3V)
hw.sensors.lm1.volt3=3.33 VDC (+3.3V)
hw.sensors.lm1.volt4=-16.73 VDC (-12V)
hw.sensors.lm1.volt5=1.11 VDC
hw.sensors.lm1.volt6=1.51 VDC
hw.sensors.lm1.volt7=3.34 VDC (3.3VSB)
hw.sensors.lm1.volt8=1.64 VDC (VBAT)
Full dmesg for the archives:
OpenBSD 4.7-current (GENERIC.MP) #1: Sun Jul 18 13:26:37 CEST 2010
r...@lanner.kerberos.si:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz ("GenuineIntel" 686-class) 3.06
GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLU
SH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSS
E3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT
real mem = 2071158784 (1975MB)
avail mem = 2027278336 (1933MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 02/22/10, BIOS32 rev. 0 @ 0xf0010,
SMBIOS rev. 2.6 @ 0xfc880 (66 entries)
bios0: vendor American Megatrends Inc. version "080015" date 02/22/2010
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP APIC MCFG OEMB GSCI SSDT
acpi0: wakeup devices P0P1(S4) P0P3(S4) P0P4(S4) P0P5(S4) P0P6(S4) BR1E(S4)
USB0(S4) USB1(S4) USB2(S4) USB3(S4) USB4(S4) USB5(S4) USB6(S4) GBE_(S4)
BR20(S4) BR21(S4) BR22(S4) BR23(S4) BR24(S4) BR25(S4) BR26(S4) BR27(S4)
EUSB(S1) USBE(S1) SLPB(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 132MHz
cpu1 at mainbus0: apid 4 (application processor)
cpu1: Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz ("GenuineIntel" 686-class) 3.06
GHz
cpu1:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLU
SH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSS
E3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz ("GenuineIntel" 686-class) 3.06
GHz
cpu2:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLU
SH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,SSS
E3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT
cpu3 at mainbus0:
