Re: netbsd 8 (beta) failing to load ixg device
On Thu, Nov 09, 2017 at 09:15:53AM -0500, Derrick Lobo wrote: > The daily beta version of nebtsd 8 does not support ixg 5gb NIC's, the > support was enabled in 7.99 That doesn't make sense - if it's in 7.anything, it's in 8. When we cut the 8 branch, we move the version number on HEAD to 8.99. Thor
daily CVS update output
Updating src tree: P src/common/dist/zlib/inflate.c P src/doc/3RDPARTY P src/doc/CHANGES P src/external/bsd/acpica/bin/iasl/Makefile P src/external/bsd/nvi/dist/cl/cl_funcs.c P src/external/bsd/nvi/dist/common/cut.h P src/external/bsd/nvi/dist/common/multibyte.h P src/external/bsd/nvi/dist/common/put.c P src/external/bsd/nvi/dist/common/util.c P src/external/bsd/nvi/dist/ex/ex.c P src/external/bsd/nvi/dist/ex/ex_cscope.c P src/external/bsd/nvi/dist/ex/ex_print.c P src/external/bsd/nvi/dist/regex/regcomp.c P src/external/bsd/nvi/usr.bin/nvi/Makefile P src/external/bsd/tre/dist/lib/regexec.c P src/share/man/man3/__insn_barrier.3 P src/share/man/man9/bus_dma.9 P src/share/man/man9/bus_space.9 P src/share/man/man9/condvar.9 P src/share/man/man9/intro.9 P src/share/man/man9/mb.9 P src/share/man/man9/rwlock.9 P src/sys/arch/luna68k/stand/boot/Makefile P src/sys/arch/xen/xenbus/xenbus_comms.c P src/sys/dev/pci/ixgbe/ixgbe.c P src/sys/external/bsd/acpica/dist/common/dmtbdump.c P src/sys/external/bsd/acpica/dist/common/dmtbinfo.c P src/sys/external/bsd/acpica/dist/compiler/aslcompile.c P src/sys/external/bsd/acpica/dist/compiler/aslcompiler.h P src/sys/external/bsd/acpica/dist/compiler/aslcompiler.l P src/sys/external/bsd/acpica/dist/compiler/aslerror.c P src/sys/external/bsd/acpica/dist/compiler/aslfiles.c P src/sys/external/bsd/acpica/dist/compiler/aslload.c P src/sys/external/bsd/acpica/dist/compiler/aslopt.c P src/sys/external/bsd/acpica/dist/compiler/asloptions.c P src/sys/external/bsd/acpica/dist/compiler/aslsupport.l P src/sys/external/bsd/acpica/dist/compiler/aslutils.c P src/sys/external/bsd/acpica/dist/compiler/dtcompile.c P src/sys/external/bsd/acpica/dist/compiler/dtfield.c P src/sys/external/bsd/acpica/dist/compiler/dtparser.y P src/sys/external/bsd/acpica/dist/compiler/dtsubtable.c P src/sys/external/bsd/acpica/dist/compiler/dttable.c P src/sys/external/bsd/acpica/dist/compiler/dtutils.c P src/sys/external/bsd/acpica/dist/compiler/prparser.y P src/sys/external/bsd/acpica/dist/compiler/prutils.c P src/sys/external/bsd/acpica/dist/debugger/dbexec.c P src/sys/external/bsd/acpica/dist/debugger/dbinput.c P src/sys/external/bsd/acpica/dist/dispatcher/dscontrol.c P src/sys/external/bsd/acpica/dist/dispatcher/dsutils.c P src/sys/external/bsd/acpica/dist/events/evregion.c P src/sys/external/bsd/acpica/dist/include/acapps.h P src/sys/external/bsd/acpica/dist/include/acdebug.h P src/sys/external/bsd/acpica/dist/include/acdisasm.h P src/sys/external/bsd/acpica/dist/include/acexcep.h P src/sys/external/bsd/acpica/dist/include/aclocal.h P src/sys/external/bsd/acpica/dist/include/acmacros.h P src/sys/external/bsd/acpica/dist/include/acnamesp.h P src/sys/external/bsd/acpica/dist/include/acpixf.h P src/sys/external/bsd/acpica/dist/include/actbl1.h P src/sys/external/bsd/acpica/dist/include/actypes.h P src/sys/external/bsd/acpica/dist/include/acutils.h P src/sys/external/bsd/acpica/dist/namespace/nsaccess.c P src/sys/external/bsd/acpica/dist/tools/acpixtract/acpixtract.c P src/sys/external/bsd/acpica/dist/utilities/utdecode.c P src/sys/external/bsd/acpica/dist/utilities/utmutex.c P src/sys/external/bsd/acpica/dist/utilities/uttrack.c P src/sys/kern/kern_condvar.c P src/sys/sys/param.h Updating xsrc tree: Killing core files: Updating release-6 src tree (netbsd-6): Updating release-6 xsrc tree (netbsd-6): Updating release-7 src tree (netbsd-7): Updating release-7 xsrc tree (netbsd-7): Updating release-8 src tree (netbsd-8): Updating release-8 xsrc tree (netbsd-8): Updating file list: -rw-rw-r-- 1 srcmastr netbsd 54767779 Nov 13 03:11 ls-lRA.gz
Re: dmesg spam: ahcisata0 port 1: active 2 is 0x40000001 tfd 0x2051
Okay, so it is triggered by a ATAPI command. I've had concern that maybe code mishandle ATAPI failures, but the recovery code seems to be okay as far as I can read it. I've changed the message to not show unless debugging, so it should not spam you again. Jaromir 2017-11-10 23:03 GMT+01:00 Stefan Hertenberger : > Am Fri, 10 Nov 2017 18:43:19 +0100 > schrieb Jaromír Doleček : > > > TFES usually means an unsupported command was sent to the device, or a > > command was sent while previous was finished. > > > > Could you please try to figure out what is the command sent to the cd0 > > device just before that error? It should be possible to turn the debug > > messages on via the ahcdebug_mask variable in ddb, set it to > > DEBUG_XFERS (0x02). > > Hope this helps > > ahcisata0 port 0 header 0x80008e01f020 > ahci_bio_complete bcount 32768 now 0 > ahci_ata_bio port 0 CI 0x0 > ahci_bio_start CI 0x0 > ahcisata0 port 0 tbl 0x80008e021200 > ahcisata0 port 0 header 0x80008e01f020 > ahci_bio_complete bcount 16384 now 0 > ahci_ata_bio port 0 CI 0x0 > ahci_bio_start CI 0x0 > ahcisata0 port 0 tbl 0x80008e021200 > ahcisata0 port 0 header 0x80008e01f020 > ahci_bio_complete bcount 16384 now 0 > ahci_ata_bio port 0 CI 0x0 > ahci_bio_start CI 0x0 > ahcisata0 port 0 tbl 0x80008e021200 > ahcisata0 port 0 header 0x80008e01f020 > ahci_bio_complete bcount 32768 now 0 > ahci_ata_bio port 0 CI 0x0 > ahci_bio_start CI 0x0 > ahcisata0 port 0 tbl 0x80008e021200 > ahcisata0 port 0 header 0x80008e01f020 > ahci_bio_complete bcount 32768 now 0 > ahci_ata_bio port 0 CI 0x0 > ahci_bio_start CI 0x0 > ahcisata0 port 0 tbl 0x80008e021200 > ahcisata0 port 0 header 0x80008e01f020 > ahci_bio_complete bcount 16384 now 0 > ahci_ata_bio port 0 CI 0x0 > ahci_bio_start CI 0x0 > ahcisata0 port 0 tbl 0x80008e021200 > ahcisata0 port 0 header 0x80008e01f020 > ahci_bio_complete bcount 16384 now 0 > ahci_ata_bio port 0 CI 0x0 > ahci_bio_start CI 0x0 > ahcisata0 port 0 tbl 0x80008e021200 > ahcisata0 port 0 header 0x80008e01f020 > ahci_bio_complete bcount 32768 now 0 > ahci_ata_bio port 0 CI 0x0 > ahci_bio_start CI 0x0 > ahcisata0 port 0 tbl 0x80008e021200 > ahcisata0 port 0 header 0x80008e01f020 > ahci_bio_complete bcount 32768 now 0 > ahci_ata_bio port 0 CI 0x0 > ahci_bio_start CI 0x0 > ahcisata0 port 0 tbl 0x80008e021200 > ahcisata0 port 0 header 0x80008e01f020 > ahci_bio_complete bcount 16384 now 0 > ahci_ata_bio port 0 CI 0x0 > ahci_bio_start CI 0x0 > ahcisata0 port 0 tbl 0x80008e021200 > ahcisata0 port 0 header 0x80008e01f020 > ahci_bio_complete bcount 16384 now 0 > ahci_ata_bio port 0 CI 0x0 > ahci_bio_start CI 0x0 > ahcisata0 port 0 tbl 0x80008e021200 > ahcisata0 port 0 header 0x80008e01f020 > ahci_bio_complete bcount 32768 now 0 > ahci_ata_bio port 0 CI 0x0 > ahci_bio_start CI 0x0 > ahcisata0 port 0 tbl 0x80008e021200 > ahcisata0 port 0 header 0x80008e01f020 > ahci_bio_complete bcount 32768 now 0 > ahci_ata_bio port 0 CI 0x0 > ahci_bio_start CI 0x0 > ahcisata0 port 0 tbl 0x80008e021200 > ahcisata0 port 0 header 0x80008e01f020 > ahci_bio_complete bcount 16384 now 0 > ahci_ata_bio port 0 CI 0x0 > ahci_bio_start CI 0x0 > ahcisata0 port 0 tbl 0x80008e021200 > ahcisata0 port 0 header 0x80008e01f020 > ahci_bio_complete bcount 16384 now 0 > ahci_ata_bio port 0 CI 0x0 > ahci_bio_start CI 0x0 > ahcisata0 port 0 tbl 0x80008e021200 > ahcisata0 port 0 header 0x80008e01f020 > ahci_bio_complete bcount 32768 now 0 > ahci_ata_bio port 0 CI 0x0 > ahci_bio_start CI 0x0 > ahcisata0 port 0 tbl 0x80008e021200 > ahcisata0 port 0 header 0x80008e01f020 > ahci_bio_complete bcount 32768 now 0 > ahci_ata_bio port 0 CI 0x0 > ahci_bio_start CI 0x0 > ahcisata0 port 0 tbl 0x80008e021200 > ahcisata0 port 0 header 0x80008e01f020 > ahci_bio_complete bcount 16384 now 0 > ahci_ata_bio port 0 CI 0x0 > ahci_bio_start CI 0x0 > ahcisata0 port 0 tbl 0x80008e021200 > ahcisata0 port 0 header 0x80008e01f020 > ahci_bio_complete bcount 16384 now 0 > ahci_ata_bio port 0 CI 0x0 > ahci_bio_start CI 0x0 > ahcisata0 port 0 tbl 0x80008e021200 > ahcisata0 port 0 header 0x80008e01f020 > ahci_bio_complete bcount 32768 now 0 > ahci_ata_bio port 0 CI 0x0 > ahci_bio_start CI 0x0 > ahcisata0 port 0 tbl 0x80008e021200 > ahcisata0 port 0 header 0x80008e01f020 > ahci_bio_complete bcount 32768 now 0 > ahci_ata_bio port 0 CI 0x0 > ahci_bio_start CI 0x0 > ahcisata0 port 0 tbl 0x80008e021200 > ahcisata0 port 0 header 0x80008e01f020 > ahci_bio_complete bcount 16384 now 0 > ahci_ata_bio port 0 CI 0x0 > ahci_bio_start CI 0x0 > ahcisata0 port 0 tbl 0x80008e021200 > ahcisata0 port 0 header 0x80008e01f020 > ahci_bio_complete bcount 16384 now 0 > ahci_ata_bio port 0 CI 0x0 > ahci_bio_start CI 0x0 > ahcisata0 port 0 tbl 0x80008e021200 > ahcisata0 port 0 header 0x80008e01f020 > ahci_bio_complete bcount 32768 now 0 > ahci_ata_bio port 0 C
Re: dmesg spam: ahcisata0 port 1: active 2 is 0x40000001 tfd 0x2051
TFES usually means an unsupported command was sent to the device, or a command was sent while previous was finished. Could you please try to figure out what is the command sent to the cd0 device just before that error? It should be possible to turn the debug messages on via the ahcdebug_mask variable in ddb, set it to DEBUG_XFERS (0x02). It could also be asynchronous notification from the device, which gets mishandled as error. I see both your and Martin's device supports them (SNTF capability). If there is no preceding command, it could be this. Jaromir 2017-11-10 14:21 GMT+01:00 Stefan Hertenberger : > > > Am 10. November 2017 14:16:51 MEZ schrieb Martin Husemann < > mar...@duskware.de>: >> >> On Fri, Nov 10, 2017 at 02:11:12PM +0100, Jaromír Dole?ek wrote: >> >>> The TFD 0x2051 corresponds to Media Changed error, with DRDY/ERR status >>> bits. Is it possible this message appears every time you change media in >>> the cd0? >>> >>> Alternatively, I imagine this could be generated if the drive is setup to >>> hibernate/suspend. >>> >> >> For me it happens w/o any medium and never touching the drive. >> >> Martin >> >> > For me too, starts while booting w/o interaction from me. > > Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet
RE: netbsd 8 (beta) failing to load ixg device
Im fine with not supporting the hardware interface(I wasn't using it anyways), but the kernel should not go in a panic state, since I cant upgrade the server or use it From: port-amd64-ow...@netbsd.org [mailto:port-amd64-ow...@netbsd.org] On Behalf Of Derrick Lobo Sent: Thursday, November 9, 2017 9:16 AM To: port-am...@netbsd.org; current-users@netbsd.org Subject: netbsd 8 (beta) failing to load ixg device The daily beta version of nebtsd 8 does not support ixg 5gb NIC's, the support was enabled in 7.99 I have added the dmesg below for both versions. -- NetBSD 8.0_BETA (GENERIC.201711070830Z) ixg0: device x540 ixg0: clearing prefetchable bit ixg0: using NSIX interrupts with 1 vectors ixg0: NVM image version 4.4 IS 0x0 PHY FW Revision 4.3 ID 0x0 EtrackID 03e1 ixg0: PHY OUI 0x00aa00 model 0x0020, rev.0 ixg0: interrupting at msi0 vec 0 fatal integer divide fault in supervisor mode trap type 0 code rip 0x0031e273 cs 0x8 rflags 0x10246 cr2 0 ilevel 0x8 rsp 0x81884460 curlup 0x81884460 pid 0.1 lowest kstack 0x818812c0 kernel:integer divide fault trap, code=0 stopped in pid 0.1 (system) at netbsd:ixgbe_update_stats_count+0x94: d iv1 e40(%r14),%eax db(0)> Last login: Fri Jun 2 11:03:58 2017 from 192.168.36.146 NetBSD 7.99.71 (GENERIC) #0: Mon May 8 10:00:41 UTC 2017 Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 7.99.71 (GENERIC) #0: Mon May 8 10:00:41 UTC 2017 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC total memory = 143 GB avail memory = 139 GB cpu_rng: RDSEED timecounter: Timecounters tick every 10.000 msec Kernelized RAIDframe activated running cgd selftest aes-xts-256 aes-xts-512 done timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100 Supermicro SYS-1028R-MCTR (0123456789) mainbus0 (root) mainbus0: Intel MP Specification (Version 1.4) (SMCI--MB SUPERM) cpu0 at mainbus0 apid 0 cpu0: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu1 at mainbus0 apid 2 cpu1: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu2 at mainbus0 apid 4 cpu2: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu3 at mainbus0 apid 6 cpu3: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu4 at mainbus0 apid 8 cpu4: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu5 at mainbus0 apid 10 cpu5: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu6 at mainbus0 apid 12 cpu6: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu7 at mainbus0 apid 16 cpu7: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu8 at mainbus0 apid 18 cpu8: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu9 at mainbus0 apid 20 cpu9: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu10 at mainbus0 apid 22 cpu10: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu11 at mainbus0 apid 24 cpu11: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu12 at mainbus0 apid 26 cpu12: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu13 at mainbus0 apid 28 cpu13: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu14 at mainbus0 apid 32 cpu14: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu15 at mainbus0 apid 34 cpu15: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu16 at mainbus0 apid 36 cpu16: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu17 at mainbus0 apid 38 cpu17: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu18 at mainbus0 apid 40 cpu18: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu19 at mainbus0 apid 42 cpu19: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu20 at mainbus0 apid 44 cpu20: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu21 at mainbus0 apid 48 cpu21: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu22 at mainbus0 apid 50 cpu22: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu23 at mainbus0 apid 52 cpu23: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu24 at mainbus0 apid 54 cpu24: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu25 at mainbus0 apid 56 cpu25: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu26 at mainbus0 apid 58 cpu26: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 cpu27 at mainbus0 apid 60 cpu27: Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz, id 0x406f1 mpbios: bus 0 is type PCI mpbios: bus 128 is type PCI mpbios: bus 1 is type PCI mpbios: bus 2 is type PCI mpbios: bus 3 is type PCI mpbios: bus 4 is type PCI mpbios: bus 5 is type PCI mpbios: bus 6 is type PCI mpbios: bus 7 is type PCI mpbios: bus 8 is type PCI mpbios: bus 129 is type ISA ioapic0 at mainbus
Re: dmesg spam: ahcisata0 port 1: active 2 is 0x40000001 tfd 0x2051
Am 10. November 2017 14:16:51 MEZ schrieb Martin Husemann : >On Fri, Nov 10, 2017 at 02:11:12PM +0100, Jaromír Dole?ek wrote: >> The TFD 0x2051 corresponds to Media Changed error, with DRDY/ERR >status >> bits. Is it possible this message appears every time you change media >in >> the cd0? >> >> Alternatively, I imagine this could be generated if the drive is >setup to >> hibernate/suspend. > >For me it happens w/o any medium and never touching the drive. > >Martin For me too, starts while booting w/o interaction from me. Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
Re: dmesg spam: ahcisata0 port 1: active 2 is 0x40000001 tfd 0x2051
The TFD 0x2051 corresponds to Media Changed error, with DRDY/ERR status bits. Is it possible this message appears every time you change media in the cd0? Alternatively, I imagine this could be generated if the drive is setup to hibernate/suspend. Jaromir 2017-11-10 10:49 GMT+01:00 : > Am 2017-11-10 10:22, schrieb Martin Husemann: > >> On Fri, Nov 10, 2017 at 10:11:43AM +0100, stefan@hertenberger.bayern >> wrote: >> >>> Am 2017-11-10 09:57, schrieb Martin Husemann: >>> > Can you show the dmesg part describing your ahcisata devices? >>> >>> ahcisata0 at pci0 dev 31 function 2: vendor 8086 product 1c03 (rev. 0x04) >>> ahcisata0: interrupting at ioapic0 pin 19 >>> ahcisata0: 64-bit DMA >>> ahcisata0: AHCI revision 1.30, 6 ports, 32 slots, CAP >>> 0xef30ff45>> SSNTF,SNCQ,S64A> >>> atabus0 at ahcisata0 channel 0 >>> atabus1 at ahcisata0 channel 1 >>> >> >> And the device at atabus1? >> >> Martin >> > > The complete dmesg out put was attached on the first mail. > > Regards Stefan > > Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, > 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017 > The NetBSD Foundation, Inc. All rights reserved. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > > NetBSD 8.99.6 (GENERIC) #8: Thu Nov 9 23:16:37 UTC 2017 > root@packard:/usr/build/obj/sys/arch/amd64/compile/GENERIC > total memory = 8043 MB > avail memory = 7788 MB > rnd: seeded with 128 bits > timecounter: Timecounters tick every 10.000 msec > Kernelized RAIDframe activated > running cgd selftest aes-xts-256 aes-xts-512 done > RTC BIOS diagnostic error 0x80 > timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100 > Packard Bell EasyNote TS11HR (V1.20) > mainbus0 (root) > ACPI: RSDP 0x000FE020 24 (v02 ACRSYS) > ACPI: XSDT 0x96FFE120 7C (v01 ACRSYS ACRPRDCT 0001 > 0113) > ACPI: FACP 0x96FFC000 F4 (v04 ACRSYS ACRPRDCT 0001 1025 > 0004) > ACPI: DSDT 0x96FF 008F53 (v01 ACRSYS ACRPRDCT 1025 > 0004) > ACPI: FACS 0x96F6D000 40 > ACPI: ASF! 0x96FFD000 A5 (v32 ACRSYS ACRPRDCT 0001 1025 > 0004) > ACPI: HPET 0x96FFB000 38 (v01 ACRSYS ACRPRDCT 0001 1025 > 0004) > ACPI: APIC 0x96FFA000 8C (v02 ACRSYS ACRPRDCT 0001 1025 > 0004) > ACPI: MCFG 0x96FF9000 3C (v01 ACRSYS ACRPRDCT 0001 1025 > 0004) > ACPI: SLIC 0x96FEF000 000176 (v01 ACRSYS ACRPRDCT 0001 1025 > 0004) > ACPI: SSDT 0x96FEE000 000BC2 (v01 ACRSYS ACRPRDCT 1000 1025 > 0004) > ACPI: BOOT 0x96FEC000 28 (v01 ACRSYS ACRPRDCT 0001 1025 > 0004) > ACPI: ASPT 0x96FE9000 34 (v07 ACRSYS ACRPRDCT 0001 1025 > 0004) > ACPI: SSDT 0x96FE8000 00090C (v01 ACRSYS ACRPRDCT 3000 1025 > 0004) > ACPI: SSDT 0x96FE7000 000996 (v01 ACRSYS ACRPRDCT 3000 1025 > 0004) > ACPI: Executed 1 blocks of module-level executable AML code > ACPI: 4 ACPI AML tables successfully acquired and loaded > ioapic0 at mainbus0 apid 0: pa 0xfec0, version 0x20, 24 pins > cpu0 at mainbus0 apid 0 > cpu0: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz, id 0x206a7 > cpu0: package 0, core 0, smt 0 > cpu1 at mainbus0 apid 1 > cpu1: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz, id 0x206a7 > cpu1: package 0, core 0, smt 1 > cpu2 at mainbus0 apid 2 > cpu2: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz, id 0x206a7 > cpu2: package 0, core 1, smt 0 > cpu3 at mainbus0 apid 3 > cpu3: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz, id 0x206a7 > cpu3: package 0, core 1, smt 1 > cpu4 at mainbus0 apid 4 > cpu4: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz, id 0x206a7 > cpu4: package 0, core 2, smt 0 > cpu5 at mainbus0 apid 5 > cpu5: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz, id 0x206a7 > cpu5: package 0, core 2, smt 1 > cpu6 at mainbus0 apid 6 > cpu6: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz, id 0x206a7 > cpu6: package 0, core 3, smt 0 > cpu7 at mainbus0 apid 7 > cpu7: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz, id 0x206a7 > cpu7: package 0, core 3, smt 1 > acpi0 at mainbus0: Intel ACPICA 20170831 > acpi0: X/RSDT: OemId , AslId <,0113> > acpi0: MCFG: segment 0, bus 0-255, address 0xe000 > ACPI: Dynamic OEM Table Load: > ACPI: SSDT 0xE4010E761810 00067C (v01 PmRef Cpu0Cst 3001 INTL > 20100121) > ACPI: Dynamic OEM Table Load: > ACPI: SSDT 0xE4025DC6F410 000303 (v01 PmRef ApIst3000 INTL > 20100121) > ACPI: Dynamic OEM Table Load: > ACPI: SSDT 0xE4010E6915D0 000119 (v01 PmRef ApCst3000 INTL > 20100121) > acpi0: SCI interrupting at int 9 > timecounter: Timecounter "ACPI-Safe" frequency 3579545 Hz quality 900 > hpet0 at acpi0: high precision event timer (mem 0xfed0-0xfed00400) > timecounter: Timecounter "hpet0" frequency 14318180 Hz quality 2000 > acpiec0 at acpi0 (EC0, PNP0C09): io 0x62,0x66 > FWHD (IN
