Re: athn0: device timeout

2023-12-23 Thread Masanori Ogino
I sent a message only to Crystal by mistake. Sorry.

On Saturday, December 23rd, 2023 at 20:07, Masanori Ogino  
wrote: 
> 
> On Saturday, December 23rd, 2023 at 18:37, Crystal Kolipe 
> kolip...@exoticsilicon.com wrote:
> 
> > On Sat, Dec 23, 2023 at 09:30:34AM +, Masanori Ogino wrote:
> > 
> > > I can work around this problem by running `ifconfig athn0 down up` for 
> > > now.
> > > Any suggestions and debugging tips for finding the root cause are 
> > > welcome, though.
> > 
> > Have you tested it as a client as well as an access point?
> 
> 
> Yes, I had tried for few minutes before changing to hostap mode and it worked.
> Thank you for pointing out the missing information.
> 
> > I've used several athn devices, mostly AR9287 with OpenBSD for many years in
> > both AP and client modes and although performance is not good in AP mode, 
> > they
> > do mostly work.
> 
> 
> Thanks, that is good to hear.
> Higher throughput is nice to have, but stability has priority to me.
> 
> Best,
> Masanori



Re: athn0: device timeout

2023-12-23 Thread Masanori Ogino
On Saturday, December 23rd, 2023 at 17:54, Masanori Ogino  
wrote:
> 
> 
> >Synopsis: Wi-Fi disconnects repeatedly with Atheros AR9285
> 
> > Category: system
> > Environment:
> 
> System : OpenBSD 7.4
> Details : OpenBSD 7.4 (GENERIC.MP) #2: Fri Dec 8 15:39:04 MST 2023
> r...@syspatch-74-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> 
> Architecture: OpenBSD.amd64
> Machine : amd64
> 
> > Description:
> 
> I set up PC Engines APU2 as a home router with Wi-Fi AP.
> The router runs for hours but the AP disappears several times. When I
> connect a PC to the LAN port of router for debugging, the AP appears
> again before I log in. dmesg emits "athn0: device timeout" repeatedly.
> 
> > How-To-Repeat:
> 
> Launch the system and wait.
> 
> > Fix:
> 
> Unknown.
> 

I can work around this problem by running `ifconfig athn0 down up` for now.
Any suggestions and debugging tips for finding the root cause are welcome, 
though.

Best,
Masanori



athn0: device timeout

2023-12-23 Thread Masanori Ogino
>Synopsis:  Wi-Fi disconnects repeatedly with Atheros AR9285
>Category:  system
>Environment:
System  : OpenBSD 7.4
Details : OpenBSD 7.4 (GENERIC.MP) #2: Fri Dec  8 15:39:04 MST 2023
 
r...@syspatch-74-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

Architecture: OpenBSD.amd64
Machine : amd64
>Description:
I set up PC Engines APU2 as a home router with Wi-Fi AP.
The router runs for hours but the AP disappears several times. When I
connect a PC to the LAN port of router for debugging, the AP appears
again before I log in. dmesg emits "athn0: device timeout" repeatedly.
>How-To-Repeat:
Launch the system and wait.
>Fix:
Unknown.

dmesg:
OpenBSD 7.4 (GENERIC.MP) #2: Fri Dec  8 15:39:04 MST 2023

r...@syspatch-74-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4259930112 (4062MB)
avail mem = 4111097856 (3920MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xcfe97040 (13 entries)
bios0: vendor coreboot version "v4.19.0.1" date 01/31/2023
bios0: PC Engines apu2
acpi0 at bios0: ACPI 6.0
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP SSDT MCFG TPM2 APIC HEST SSDT SSDT DRTM HPET
acpi0: wakeup devices PBR4(S4) PBR5(S4) PBR6(S4) PBR7(S4) PBR8(S4) UOH1(S3) 
UOH2(S3) UOH3(S3) UOH4(S3) UOH5(S3) UOH6(S3) XHC0(S4)
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimcfg0 at acpi0
acpimcfg0: addr 0xf800, bus 0-63
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD GX-412TC SOC, 998.17 MHz, 16-30-01, patch 07030105
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,HWPSTATE,ITSC,BMI1,XSAVEOPT
cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 2-way I-cache, 2MB 64b/line 
16-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: AMD GX-412TC SOC, 998.20 MHz, 16-30-01, patch 07030105
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,HWPSTATE,ITSC,BMI1,XSAVEOPT
cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 2-way I-cache, 2MB 64b/line 
16-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: AMD GX-412TC SOC, 998.43 MHz, 16-30-01, patch 07030105
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,HWPSTATE,ITSC,BMI1,XSAVEOPT
cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 2-way I-cache, 2MB 64b/line 
16-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: AMD GX-412TC SOC, 998.36 MHz, 16-30-01, patch 07030105
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,HWPSTATE,ITSC,BMI1,XSAVEOPT
cpu3: 32KB 64b/line 8-way D-cache, 32KB 64b/line 2-way I-cache, 2MB 64b/line 
16-way L2 cache
cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 4 pa 0xfec0, version 21, 24 pins
ioapic1 at mainbus0: apid 5 pa 0xfec2, version 21, 32 pins
acpihpet0 at acpi0: 14318180 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (PBR4)
acpiprt2 at acpi0: bus 2 (PBR5)
acpiprt3 at acpi0: bus 3 (PBR6)
acpiprt4 at acpi0: bus 4 (PBR7)
acpiprt5 at acpi0: bus -1 (PBR8)
acpicpu0 at acpi0: C2(0@400 io@0x1771), C1(@1 halt!), PSS
acpicpu1 at acpi0: C2(0@400 io@0x1771), C1(@1 halt!), PSS
acpicpu2 at acpi0: C2(0@400 io@0x1771), C1(@1 halt!), PSS
acpicpu3 at acpi0: C2(0@400 io@0x1771), C1(@1 halt!), PSS
acpicpu4 at acpi0: no cpu matching ACPI ID 4
acpicpu5 at acpi0: no cpu matching ACPI ID 5
acpicpu6 at acpi0: no cpu matching ACPI ID 6
acpicpu7 at acpi0: no cpu matching ACPI ID 7
acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001
acpicmos0 at acpi0
com0 at acpi0 COM1 addr 0x3f8/0x8 irq 4: ns16550a, 16 byte fifo

Re: "athn0: device timeout"

2014-06-10 Thread Stefan Sperling
On Mon, Jun 09, 2014 at 11:23:47AM -0400, kbenjamin Coplon wrote:
> On 6/8/14, kbenjamin Coplon  wrote:
> > I'm using an ALIX board with a WLM200NX as a 802.11g access point
> > using OpenBSD 5.5.
> > It works great for a while until i get "athn0: device timeout" a few
> > times, then it stops working until i reboot it.
> > The athn man page says:
> > " athn0: device timeout A frame dispatched to the hardware for
> > transmission did not complete in time. The driver will reset the
> > hardware. This should not happen."
> >
> > That last line makes me think i've found a bug.

Perhaps, and it could be a bug in the hardware, firmware, or driver.
So that message alone doesn't help with narrowing it down to anything.

> > I'm sorry i don't know whether this is the right place to ask, i
> > didn't see any offcial OpenBSD noob list,
> > if this is the wrong place please point me in the right direction.
> >
> > Thank you
> > passstab
> >
> 
> I've tried fw_update which didn't help.
> 
> here is dmesg
 
> athn0 at pci0 dev 12 function 0 "Atheros AR9280" rev 0x01: irq 9
> athn0: AR9280 rev 2 (2T2R), ROM rev 22, address 04:f0:21:0e:84:6a

I have a very similar athn model in a soekris net5501 and I'm also
seeing this message in the logs very occasionally. However in my
case a reboot doesn't seem to be necessary to recover.

athn0 at pci0 dev 17 function 0 "Atheros AR9280" rev 0x01: irq 15
athn0: AR9280 rev 2 (2T2R), ROM rev 16, address 00:0e:8e:24:52:7d

Jun  9 21:09:29 dougal /bsd: athn0: device timeout

This AP works fine as I'm writing this, with no reboot in between.

Does it self-heal if you wait longer after it happened?

Have you tried re-associating the client (i.e. ifconfig down; ifconfig up;
dhclient, on the associated device) instead of rebooting the AP?

Do you know of a way of triggering the message at will?



Re: "athn0: device timeout"

2014-06-09 Thread kbenjamin Coplon
On 6/8/14, kbenjamin Coplon  wrote:
> I'm using an ALIX board with a WLM200NX as a 802.11g access point
> using OpenBSD 5.5.
> It works great for a while until i get "athn0: device timeout" a few
> times, then it stops working until i reboot it.
> The athn man page says:
> " athn0: device timeout A frame dispatched to the hardware for
> transmission did not complete in time. The driver will reset the
> hardware. This should not happen."
>
> That last line makes me think i've found a bug.
>
> I'm sorry i don't know whether this is the right place to ask, i
> didn't see any offcial OpenBSD noob list,
> if this is the wrong place please point me in the right direction.
>
> Thank you
> passstab
>

I've tried fw_update which didn't help.

here is dmesg


"
cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX,MMXX,3DNOW2,3DNOW
real mem  = 267943936 (255MB)
avail mem = 251260928 (239MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 11/05/08, BIOS32 rev. 0 @ 0xfd088
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: pcibios_get_intr_routing - function not supported
pcibios0: PCI IRQ Routing information unavailable.
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xe/0xa800
cpu0 at mainbus0: (uniprocessor)
mtrr: K6-family MTRR support (2 registers)
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 1 function 0 "AMD Geode LX" rev 0x33
glxsb0 at pci0 dev 1 function 2 "AMD Geode LX Crypto" rev 0x00: RNG AES
vr0 at pci0 dev 9 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 10,
address 00:0d:b9:22:1f:dc
ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
0x004063, model 0x0034
vr1 at pci0 dev 10 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 11,
address 00:0d:b9:22:1f:dd
ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
0x004063, model 0x0034
vr2 at pci0 dev 11 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 15,
address 00:0d:b9:22:1f:de
ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI
0x004063, model 0x0034
athn0 at pci0 dev 12 function 0 "Atheros AR9280" rev 0x01: irq 9
athn0: AR9280 rev 2 (2T2R), ROM rev 22, address 04:f0:21:0e:84:6a
glxpcib0 at pci0 dev 15 function 0 "AMD CS5536 ISA" rev 0x03: rev 3,
32-bit 3579545Hz timer, watchdog, gpio, i2c
gpio0 at glxpcib0: 32 pins
iic0 at glxpcib0
maxtmp0 at iic0 addr 0x4c: lm86
pciide0 at pci0 dev 15 function 2 "AMD CS5536 IDE" rev 0x01: DMA,
channel 0 wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0: 
wd0: 1-sector PIO, LBA, 1907MB, 3906560 sectors
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2
pciide0: channel 1 ignored (disabled)
ohci0 at pci0 dev 15 function 4 "AMD CS5536 USB" rev 0x02: irq 12,
version 1.0, legacy support
ehci0 at pci0 dev 15 function 5 "AMD CS5536 USB" rev 0x02: irq 12
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "AMD EHCI root hub" rev 2.00/1.00 addr 1
isa0 at glxpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
usb1 at ohci0: USB revision 1.0
uhub1 at usb1 "AMD OHCI root hub" rev 1.00/1.00 addr 1
nvram: invalid checksum
vscsi0 at root
scsibus0 at vscsi0: 256 targets
softraid0 at root
scsibus1 at softraid0: 256 targets
root on wd0a (72df31a55cbd4e5e.a) swap on wd0b dump on wd0b
clock: unknown CMOS layout
athn0: device timeout
vr0: restarting
athn0: device timeout
athn0: device timeout
#
"



"athn0: device timeout"

2014-06-08 Thread kbenjamin Coplon
I'm using an ALIX board with a WLM200NX as a 802.11g access point
using OpenBSD 5.5.
It works great for a while until i get "athn0: device timeout" a few
times, then it stops working until i reboot it.
The athn man page says:
" athn0: device timeout A frame dispatched to the hardware for
transmission did not complete in time. The driver will reset the
hardware. This should not happen."

That last line makes me think i've found a bug.

I'm sorry i don't know whether this is the right place to ask, i
didn't see any offcial OpenBSD noob list,
if this is the wrong place please point me in the right direction.

Thank you
passstab



Re: athn0: device timeout with the last 2 snapshots

2013-11-15 Thread Josh Grosse
On Fri, Nov 15, 2013 at 01:04:54PM -0500, Kenneth R Westerback wrote:
> Fix committed (to dev/ic/athn.c if you want the one liner itself), should
> be in snaps dated after today.

It's working fine now on i386.  Thanks!



Re: athn0: device timeout with the last 2 snapshots

2013-11-15 Thread Kenneth R Westerback
On Fri, Nov 15, 2013 at 08:14:47AM -0500, Josh Grosse wrote:
> On Thu, Nov 14, 2013 at 11:09:14PM +0100, Stefan Sperling wrote:
> 
> > So the previous version was fine?
> 
> I can confirm the problem also occurs on i386, with both a Nov 12 snapshot
> kernal and with a kernel built 12 hours ago.  The Nov 7 snapshot kernel
> works fine with athn0. 
> 

Fix committed (to dev/ic/athn.c if you want the one liner itself), should
be in snaps dated after today.

 Ken



Re: athn0: device timeout with the last 2 snapshots

2013-11-15 Thread Vigdis
On Fri, 15 Nov 2013 08:14:47 -0500,
Josh Grosse  wrote:

> On Thu, Nov 14, 2013 at 11:09:14PM +0100, Stefan Sperling wrote:
> 
> > So the previous version was fine?
> 
> I can confirm the problem also occurs on i386, with both a Nov 12
> snapshot kernal and with a kernel built 12 hours ago.  The Nov 7
> snapshot kernel works fine with athn0. 
> 

I just built a new kernel (with
http://marc.info/?l=openbsd-cvs&m=138447996908659&w=2) and no more
timeout.

Thanks a lot !

-- 
Vigdis



Re: athn0: device timeout with the last 2 snapshots

2013-11-15 Thread Josh Grosse
On Thu, Nov 14, 2013 at 11:09:14PM +0100, Stefan Sperling wrote:

> So the previous version was fine?

I can confirm the problem also occurs on i386, with both a Nov 12 snapshot
kernal and with a kernel built 12 hours ago.  The Nov 7 snapshot kernel
works fine with athn0. 



Re: athn0: device timeout with the last 2 snapshots

2013-11-14 Thread Vigdis
On Thu, 14 Nov 2013 23:09:14 +0100,
Stefan Sperling  wrote:

> On Thu, Nov 14, 2013 at 09:25:40PM +0100, vigdis+o...@chown.me wrote:
> > >Synopsis:  athn timeout Category:  athn timeout
> > >Environment:
> > System  : OpenBSD 5.4 Details : OpenBSD 5.4-current
> > (GENERIC.MP) #150: Thu Nov 14 00:30:57 MST 2013
> > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> > 
> > Architecture: OpenBSD.amd64 Machine : amd64
> > >Description:
> > I upgrade a couple of hours ago to the last snapshot (it
> > was at the time the Nov 12 one, iirc) and I had some athn device
> > timeout.
> 
> So the previous version was fine?

Yes, I didn't have any problem before today.

> Can you tell us what you were running before this upgrade?
> Stock 5.3 or 5.4? Or something else?

I'm using -current so it was the snapshot before the Nov 12 one. The
firmware didn't change though, it has been athn-firmware-1.1p0 since
my first install on Oct 12 (I looked in my old mail for the rc.firsttime
output). 


-- 
Vigdis



Re: athn0: device timeout with the last 2 snapshots

2013-11-14 Thread Stefan Sperling
On Thu, Nov 14, 2013 at 09:25:40PM +0100, vigdis+o...@chown.me wrote:
> >Synopsis:athn timeout Category:  athn timeout Environment:
>   System  : OpenBSD 5.4 Details : OpenBSD 5.4-current
>   (GENERIC.MP) #150: Thu Nov 14 00:30:57 MST 2013
>   dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> 
>   Architecture: OpenBSD.amd64 Machine : amd64
> >Description:
>   I upgrade a couple of hours ago to the last snapshot (it was at
>   the time the Nov 12 one, iirc) and I had some athn device
>   timeout.

So the previous version was fine?
Can you tell us what you were running before this upgrade?
Stock 5.3 or 5.4? Or something else?



athn0: device timeout with the last 2 snapshots

2013-11-14 Thread vigdis+obsd
>Synopsis:  athn timeout
>Category:  athn timeout
>Environment:
System  : OpenBSD 5.4
Details : OpenBSD 5.4-current (GENERIC.MP) #150: Thu Nov 14 
00:30:57 MST 2013
 
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

Architecture: OpenBSD.amd64
Machine : amd64
>Description:
I upgrade a couple of hours ago to the last snapshot (it was at the 
time the Nov 12 one, iirc) and I had some athn device timeout. I began a 
bugreport but I saw there was a fresh snapshot so I tried it, but I still have 
these device timeouts. I looked in the log and also found "/bsd: athn0: Michael 
MIC failure" but I don't know what it means. FWIW I don't use any encryption on 
the WIFI I connect to.  
>How-To-Repeat:



dmesg:
OpenBSD 5.4-current (GENERIC.MP) #150: Thu Nov 14 00:30:57 MST 2013
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 1047068672 (998MB)
avail mem = 103984 (964MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xf0760 (31 entries)
bios0: vendor American Megatrends Inc. version "0904" date 08/12/2010
bios0: ASUSTeK Computer INC. 1005PX
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC MCFG ECDT OEMB HPET GSCI SSDT SLIC
acpi0: wakeup devices P0P1(S4) P0P4(S4) P0P5(S4) P0P6(S4) P0P7(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Atom(TM) CPU N450 @ 1.66GHz, 1666.69 MHz
cpu0: 
FPU,VME,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,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF
cpu0: 512KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
cpu0: apic clock running at 166MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.0.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Atom(TM) CPU N450 @ 1.66GHz, 1666.48 MHz
cpu1: 
FPU,VME,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,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF
cpu1: 512KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 1, remapped to apid 2
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpiec0 at acpi0
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 4 (P0P4)
acpiprt2 at acpi0: bus 2 (P0P5)
acpiprt3 at acpi0: bus -1 (P0P6)
acpiprt4 at acpi0: bus 1 (P0P7)
acpicpu0 at acpi0: C2, C1, PSS
acpicpu1 at acpi0: C2, C1, PSS
acpitz0 at acpi0: critical temperature is 98 degC
acpibat0 at acpi0: BAT0 model "1001PX" serial   type LION oem "ASUS"
acpiac0 at acpi0: AC unit online
acpiasus0 at acpi0
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpibtn2 at acpi0: PWRB
cpu0: Enhanced SpeedStep 1666 MHz: speeds: 1667, 1333, 1000 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Pineview DMI" rev 0x00
vga1 at pci0 dev 2 function 0 "Intel Pineview Video" rev 0x00
intagp0 at vga1
agp0 at intagp0: aperture at 0xd000, size 0x1000
inteldrm0 at vga1
drm0 at inteldrm0
composite sync not supported
intel_overlay_map_regs partial stub
composite sync not supported
inteldrm0: 1024x600
wsdisplay0 at vga1 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
"Intel Pineview Video" rev 0x00 at pci0 dev 2 function 1 not configured
azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x02: msi
azalia0: codecs: Realtek ALC269
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: msi
pci1 at ppb0 bus 4
ppb1 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: msi
pci2 at ppb1 bus 2
athn0 at pci2 dev 0 function 0 "Atheros AR9285" rev 0x01: apic 2 int 17
athn0: AR9285 rev 2 (1T1R), ROM rev 13, address 48:5d:60:32:25:40
ppb2 at pci0 dev 28 function 3 "Intel 82801GB PCIE" rev 0x02: msi
pci3 at ppb2 bus 1
alc0 at pci3 dev 0 function 0 "Attansic Technology L2C" rev 0xc0: msi, address 
bc:ae:c5:02:e2:87
atphy0 at alc0 phy 0: F1 10/100/1000 PHY, rev. 11
uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x02: apic 2 int 23
uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x02: apic 2 int 19
uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x02: apic 2 int 18
uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x02: apic 2 int 16
ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x02: apic 2 int 23
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb3 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xe2
pci4 at ppb3 bus 5
pcib0 at pci0 dev 31 function 0 "Intel NM10 LPC" rev 0x02
ahci0 at pci0 dev 31 function 2 "Intel 82801GR AHCI" rev 0x02: msi, AHCI 1.1
scsibus0 at ahci0: 32 targets
sd0 at scsibu