Re: OpenBSD 6.3 kernel panic

2018-04-15 Thread Juan Morado 
On Sun, Apr 15, 2018 at 1:02 AM, Mike Larkin  wrote:

> On Sat, Apr 14, 2018 at 11:32:00PM -0500, Juan Morado wrote:
> > Here's the text as best I can see it.
> >
> > uvm_fault (0xc1afca80, 0x808ca000, 0, 1) -> e
> > kernel: page fault trap, code=0
> > Stopped atihidev_intr+0x18a:  movzbl   0(%rsi,%rax,1),%eax
> > ddb{0}>
> >
> > On the same hardware, I did occasionally get some errors logged to the
> > console running 6.2, IIRC something about an invalid value from ihiddev,
> > but it didn't crash or hang.
> >
>
> Can you show the output of "show reg" at ddb?
>
> PS, this bug report leaves a lot to be desired...
>

https://www.openbsd.org/report.html

I think responding with the link above would have been most gracious.
I'll try to get all that information together and take the discussion over
to b...@openbsd.org Thanks for the help thus far.

Re: OpenBSD 6.3 kernel panic

2018-04-15 Thread IL Ka 
Technically, you can debug your real machine kernel using serial (aka com)
port, but I do not think you need to do that.
When your kernel panics, it takes your to ddb, right?

You got "uvm_fault  page fault trap": it means kernel tries to access some
invalid memory address.
It happens in  "ihidev_intr" (HID-over-i2c driver) at offset 0x18a.
This address is stored in registry, that is why Mike Larkin aksed you to do
"show reg": get registers values, and send them to list.

So, there is some bug in ihidev_intr driver, you need to post whole
text + "show
reg" output to bugs@ along with your laptop name.




On Mon, Apr 16, 2018 at 4:13 AM, Juan Morado  wrote:

> Rupert, that's a great article, thanks for sharing. I don't see how that
> helps when my OpenBSD host machine would crash (not the QEMU guest) when I
> so much as touch the track pad.
>
> On Sun, Apr 15, 2018 at 2:05 AM, Rupert Gallagher 
> wrote:
>
> > http://bijanebrahimi.github.io/blog/remote-debugging-the-
> > running-openbsd-kernel.html
> >
> > On Sun, Apr 15, 2018 at 08:02, Mike Larkin  wrote:
> >
> > PS, this bug report leaves a lot to be desired... -ml
> >
> >
>

Re: OpenBSD 6.3 kernel panic

2018-04-15 Thread Juan Morado 
Rupert, that's a great article, thanks for sharing. I don't see how that
helps when my OpenBSD host machine would crash (not the QEMU guest) when I
so much as touch the track pad.

On Sun, Apr 15, 2018 at 2:05 AM, Rupert Gallagher 
wrote:

> http://bijanebrahimi.github.io/blog/remote-debugging-the-
> running-openbsd-kernel.html
>
> On Sun, Apr 15, 2018 at 08:02, Mike Larkin  wrote:
>
> PS, this bug report leaves a lot to be desired... -ml
>
>

Re: OpenBSD 6.3 kernel panic

2018-04-15 Thread Rupert Gallagher 
http://bijanebrahimi.github.io/blog/remote-debugging-the-running-openbsd-kernel.html

On Sun, Apr 15, 2018 at 08:02, Mike Larkin  wrote:

> PS, this bug report leaves a lot to be desired... -ml

Re: OpenBSD 6.3 kernel panic

2018-04-15 Thread Mike Larkin 
On Sat, Apr 14, 2018 at 11:32:00PM -0500, Juan Morado wrote:
> Here's the text as best I can see it.
> 
> uvm_fault (0xc1afca80, 0x808ca000, 0, 1) -> e
> kernel: page fault trap, code=0
> Stopped atihidev_intr+0x18a:  movzbl   0(%rsi,%rax,1),%eax
> ddb{0}>
> 
> On the same hardware, I did occasionally get some errors logged to the
> console running 6.2, IIRC something about an invalid value from ihiddev,
> but it didn't crash or hang.
> 

Can you show the output of "show reg" at ddb?

PS, this bug report leaves a lot to be desired...

-ml

> On Sat, Apr 14, 2018 at 8:06 PM, Mike Larkin  wrote:
> 
> > On Sat, Apr 14, 2018 at 04:47:32PM -0500, Juan Morado wrote:
> > > On Fri, Apr 13, 2018 at 1:18 PM, Mike Larkin 
> > wrote:
> > >
> > > > On Thu, Apr 12, 2018 at 10:19:23PM -0500, Juan Morado wrote:
> > > > > Hi all,
> > > > >
> > > > > I searched the mail archives briefly but couldn't find a related
> > issue.
> > > > > Apologies if this is a duplicate.
> > > > >
> > > > > Since upgrading to OpenBSD 6.3 on my amd64 laptop, it has been
> > crashing
> > > > > whenever I touch the track pad.
> > > > >
> > > > > Touching the track pad after X starts generally causes the machine to
> > > > just
> > > > > hang, however, it also crashes during boot if the track pad is
> > touched
> > > > so I
> > > > > was able to get a dump from ddb.
> > > > >
> > > > > Output from dmesg follows. I also have bsd.0.core, bsd.0, bounds,
> > minfree
> > > > > files from the crash dump. If there is any interest in looking at
> > these,
> > > > > please advise the best way to share them.
> > > > >
> > > > > - JM
> > > > >
> > > > > ---
> > > >
> > > > Where's the panic string?
> > > >
> > >
> > > Hell if I know.
> > >
> > > Maybe kernel panic isn't the correct terminology? ddb is invoked anytime
> > I
> >
> > So what does it say on the screen when you are in ddb?
> >
> > > touch the track pad while booting. Touching the track pad once X starts
> > > causes the machine to become unresponsive. I don't recall if the dmesg
> > was
> > > taken immediately following the crash or not. As I mentioned I was able
> > to
> > > generate a dump and I can share those dump files.
> >
> >
> >

Re: OpenBSD 6.3 kernel panic

2018-04-14 Thread Juan Morado 
Here's the text as best I can see it.

uvm_fault (0xc1afca80, 0x808ca000, 0, 1) -> e
kernel: page fault trap, code=0
Stopped atihidev_intr+0x18a:  movzbl   0(%rsi,%rax,1),%eax
ddb{0}>

On the same hardware, I did occasionally get some errors logged to the
console running 6.2, IIRC something about an invalid value from ihiddev,
but it didn't crash or hang.

On Sat, Apr 14, 2018 at 8:06 PM, Mike Larkin  wrote:

> On Sat, Apr 14, 2018 at 04:47:32PM -0500, Juan Morado wrote:
> > On Fri, Apr 13, 2018 at 1:18 PM, Mike Larkin 
> wrote:
> >
> > > On Thu, Apr 12, 2018 at 10:19:23PM -0500, Juan Morado wrote:
> > > > Hi all,
> > > >
> > > > I searched the mail archives briefly but couldn't find a related
> issue.
> > > > Apologies if this is a duplicate.
> > > >
> > > > Since upgrading to OpenBSD 6.3 on my amd64 laptop, it has been
> crashing
> > > > whenever I touch the track pad.
> > > >
> > > > Touching the track pad after X starts generally causes the machine to
> > > just
> > > > hang, however, it also crashes during boot if the track pad is
> touched
> > > so I
> > > > was able to get a dump from ddb.
> > > >
> > > > Output from dmesg follows. I also have bsd.0.core, bsd.0, bounds,
> minfree
> > > > files from the crash dump. If there is any interest in looking at
> these,
> > > > please advise the best way to share them.
> > > >
> > > > - JM
> > > >
> > > > ---
> > >
> > > Where's the panic string?
> > >
> >
> > Hell if I know.
> >
> > Maybe kernel panic isn't the correct terminology? ddb is invoked anytime
> I
>
> So what does it say on the screen when you are in ddb?
>
> > touch the track pad while booting. Touching the track pad once X starts
> > causes the machine to become unresponsive. I don't recall if the dmesg
> was
> > taken immediately following the crash or not. As I mentioned I was able
> to
> > generate a dump and I can share those dump files.
>
>
>

Re: OpenBSD 6.3 kernel panic

2018-04-14 Thread Mike Larkin 
On Sat, Apr 14, 2018 at 04:47:32PM -0500, Juan Morado wrote:
> On Fri, Apr 13, 2018 at 1:18 PM, Mike Larkin  wrote:
> 
> > On Thu, Apr 12, 2018 at 10:19:23PM -0500, Juan Morado wrote:
> > > Hi all,
> > >
> > > I searched the mail archives briefly but couldn't find a related issue.
> > > Apologies if this is a duplicate.
> > >
> > > Since upgrading to OpenBSD 6.3 on my amd64 laptop, it has been crashing
> > > whenever I touch the track pad.
> > >
> > > Touching the track pad after X starts generally causes the machine to
> > just
> > > hang, however, it also crashes during boot if the track pad is touched
> > so I
> > > was able to get a dump from ddb.
> > >
> > > Output from dmesg follows. I also have bsd.0.core, bsd.0, bounds, minfree
> > > files from the crash dump. If there is any interest in looking at these,
> > > please advise the best way to share them.
> > >
> > > - JM
> > >
> > > ---
> >
> > Where's the panic string?
> >
> 
> Hell if I know.
> 
> Maybe kernel panic isn't the correct terminology? ddb is invoked anytime I

So what does it say on the screen when you are in ddb?

> touch the track pad while booting. Touching the track pad once X starts
> causes the machine to become unresponsive. I don't recall if the dmesg was
> taken immediately following the crash or not. As I mentioned I was able to
> generate a dump and I can share those dump files.

Re: OpenBSD 6.3 kernel panic

2018-04-14 Thread IL Ka 
>
> Maybe kernel panic isn't the correct terminology? ddb is invoked anytime I
> touch the track pad while booting.

 You are right: it is kernel panic.

Accroding to ddb(4):
"ddb is invoked upon a kernel panic when the sysctl(8) ddb.panic is set to
1."

I am not sure, but I believe you can disable it and get kernel panic
message on console instead of ddb by disabling this option in
"/etc/sysctl.conf" and reboot
But even with ddb you can get some useful information to report to bugs@.
See https://www.openbsd.org/ddb.html
I think "traceback" and "show panic" could be useful

Re: OpenBSD 6.3 kernel panic

2018-04-14 Thread Juan Morado 
On Fri, Apr 13, 2018 at 1:18 PM, Mike Larkin  wrote:

> On Thu, Apr 12, 2018 at 10:19:23PM -0500, Juan Morado wrote:
> > Hi all,
> >
> > I searched the mail archives briefly but couldn't find a related issue.
> > Apologies if this is a duplicate.
> >
> > Since upgrading to OpenBSD 6.3 on my amd64 laptop, it has been crashing
> > whenever I touch the track pad.
> >
> > Touching the track pad after X starts generally causes the machine to
> just
> > hang, however, it also crashes during boot if the track pad is touched
> so I
> > was able to get a dump from ddb.
> >
> > Output from dmesg follows. I also have bsd.0.core, bsd.0, bounds, minfree
> > files from the crash dump. If there is any interest in looking at these,
> > please advise the best way to share them.
> >
> > - JM
> >
> > ---
>
> Where's the panic string?
>

Hell if I know.

Maybe kernel panic isn't the correct terminology? ddb is invoked anytime I
touch the track pad while booting. Touching the track pad once X starts
causes the machine to become unresponsive. I don't recall if the dmesg was
taken immediately following the crash or not. As I mentioned I was able to
generate a dump and I can share those dump files.

Re: OpenBSD 6.3 kernel panic

2018-04-13 Thread Mike Larkin 
On Thu, Apr 12, 2018 at 10:19:23PM -0500, Juan Morado wrote:
> Hi all,
> 
> I searched the mail archives briefly but couldn't find a related issue.
> Apologies if this is a duplicate.
> 
> Since upgrading to OpenBSD 6.3 on my amd64 laptop, it has been crashing
> whenever I touch the track pad.
> 
> Touching the track pad after X starts generally causes the machine to just
> hang, however, it also crashes during boot if the track pad is touched so I
> was able to get a dump from ddb.
> 
> Output from dmesg follows. I also have bsd.0.core, bsd.0, bounds, minfree
> files from the crash dump. If there is any interest in looking at these,
> please advise the best way to share them.
> 
> - JM
> 
> ---

Where's the panic string?

> 
> OpenBSD 6.3 (GENERIC.MP) #107: Sat Mar 24 14:21:59 MDT 2018
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 4157906944 (3965MB)
> avail mem = 4024819712 (3838MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xeced0 (18 entries)
> bios0: vendor American Megatrends Inc. version "X541SA.301" date 09/14/2016
> bios0: ASUSTeK COMPUTER INC. X541SA
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP APIC FPDT FIDT ECDT MCFG SSDT SSDT SSDT UEFI LPIT
> TPM2 CSRT SSDT SSDT MSDM
> acpi0: wakeup devices BRC1(S0) XHC1(S4) HDEF(S4) PXSX(S4) RP01(S4) PXSX(S4)
> RP02(S4) PXSX(S4) RP03(S4) 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: Intel(R) Pentium(R) CPU N3710 @ 1.60GHz, 1680.32 MHz
> cpu0:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT,MELTDOWN
> cpu0: 1MB 64b/line 16-way L2 cache
> acpitimer0: recalibrated TSC frequency 1599952018 Hz
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> cpu0: apic clock running at 80MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE
> cpu1 at mainbus0: apid 2 (application processor)
> cpu1: Intel(R) Pentium(R) CPU N3710 @ 1.60GHz, 1680.01 MHz
> cpu1:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT,MELTDOWN
> cpu1: 1MB 64b/line 16-way L2 cache
> cpu1: smt 0, core 1, package 0
> cpu2 at mainbus0: apid 4 (application processor)
> cpu2: Intel(R) Pentium(R) CPU N3710 @ 1.60GHz, 1600.01 MHz
> cpu2:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT,MELTDOWN
> cpu2: 1MB 64b/line 16-way L2 cache
> cpu2: smt 0, core 2, package 0
> cpu3 at mainbus0: apid 6 (application processor)
> cpu3: Intel(R) Pentium(R) CPU N3710 @ 1.60GHz, 1600.01 MHz
> cpu3:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT,MELTDOWN
> cpu3: 1MB 64b/line 16-way L2 cache
> cpu3: smt 0, core 3, package 0
> ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 115 pins
> acpiec0 at acpi0
> acpimcfg0 at acpi0 addr 0xe000, bus 0-255
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus 1 (RP01)
> acpiprt2 at acpi0: bus -1 (RP02)
> acpiprt3 at acpi0: bus 2 (RP03)
> acpiprt4 at acpi0: bus 3 (RP04)
> acpiec at acpi0 not configured
> acpicpu0 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58),
> C1(1000@1 mwait.1), PSS
> acpicpu1 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58),
> C1(1000@1 mwait.1), PSS
> acpicpu2 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58),
> C1(1000@1 mwait.1), PSS
> acpicpu3 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58),
> C1(1000@1 mwait.1), PSS
> acpipwrres0 at acpi0: ID3C, resource for ISP3
> acpipwrres1 at acpi0: CLK0
> acpipwrres2 at acpi0: CLK0
> acpipwrres3 at acpi0: CLK1
> acpipwrres4 at acpi0: USBC, resource for XHC1
> acpipwrres5 at acpi0: FN00, resource for FAN0
> acpitz0 at acpi0: critical temperature is 95 degC
> acpitz1 at acpi0: critical temperature is 94 degC
> "ATK3001" at acpi0 not configured
> "INTL9C60" at acpi0 not configured
> dwiic0 at acpi0: I2C4 addr 0x8141c000/0x1000 irq 35
> iic0 at dwiic0
> ihidev0 at iic0 addr 0x15 irq 0, vendor 0xb05

OpenBSD 6.3 kernel panic

2018-04-12 Thread Juan Morado 
Hi all,

I searched the mail archives briefly but couldn't find a related issue.
Apologies if this is a duplicate.

Since upgrading to OpenBSD 6.3 on my amd64 laptop, it has been crashing
whenever I touch the track pad.

Touching the track pad after X starts generally causes the machine to just
hang, however, it also crashes during boot if the track pad is touched so I
was able to get a dump from ddb.

Output from dmesg follows. I also have bsd.0.core, bsd.0, bounds, minfree
files from the crash dump. If there is any interest in looking at these,
please advise the best way to share them.

- JM

---

OpenBSD 6.3 (GENERIC.MP) #107: Sat Mar 24 14:21:59 MDT 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4157906944 (3965MB)
avail mem = 4024819712 (3838MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xeced0 (18 entries)
bios0: vendor American Megatrends Inc. version "X541SA.301" date 09/14/2016
bios0: ASUSTeK COMPUTER INC. X541SA
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT ECDT MCFG SSDT SSDT SSDT UEFI LPIT
TPM2 CSRT SSDT SSDT MSDM
acpi0: wakeup devices BRC1(S0) XHC1(S4) HDEF(S4) PXSX(S4) RP01(S4) PXSX(S4)
RP02(S4) PXSX(S4) RP03(S4) 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: Intel(R) Pentium(R) CPU N3710 @ 1.60GHz, 1680.32 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT,MELTDOWN
cpu0: 1MB 64b/line 16-way L2 cache
acpitimer0: recalibrated TSC frequency 1599952018 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 80MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Pentium(R) CPU N3710 @ 1.60GHz, 1680.01 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT,MELTDOWN
cpu1: 1MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Pentium(R) CPU N3710 @ 1.60GHz, 1600.01 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT,MELTDOWN
cpu2: 1MB 64b/line 16-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Pentium(R) CPU N3710 @ 1.60GHz, 1600.01 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT,MELTDOWN
cpu3: 1MB 64b/line 16-way L2 cache
cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 115 pins
acpiec0 at acpi0
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus -1 (RP02)
acpiprt3 at acpi0: bus 2 (RP03)
acpiprt4 at acpi0: bus 3 (RP04)
acpiec at acpi0 not configured
acpicpu0 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58),
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58),
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58),
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58),
C1(1000@1 mwait.1), PSS
acpipwrres0 at acpi0: ID3C, resource for ISP3
acpipwrres1 at acpi0: CLK0
acpipwrres2 at acpi0: CLK0
acpipwrres3 at acpi0: CLK1
acpipwrres4 at acpi0: USBC, resource for XHC1
acpipwrres5 at acpi0: FN00, resource for FAN0
acpitz0 at acpi0: critical temperature is 95 degC
acpitz1 at acpi0: critical temperature is 94 degC
"ATK3001" at acpi0 not configured
"INTL9C60" at acpi0 not configured
dwiic0 at acpi0: I2C4 addr 0x8141c000/0x1000 irq 35
iic0 at dwiic0
ihidev0 at iic0 addr 0x15 irq 0, vendor 0xb05 product 0x201, FTE1200
ihidev0: 14 report ids
imt0 at ihidev0: clickpad, 5 contacts
wsmouse0 at imt0 mux 0
acpiac0 at acpi0: AC unit offline
acpibat0 at acpi0: BAT0 model "X550A26" serial   type LIon oem "ASUSTeK"
chvgpio0 at acpi0: GPO0 uid 1 addr 0xfed8/0x8000 irq 49, 56 pins