Date: Sat, 30 Sep 2017 19:16:24 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Andriy Gapon <avg@FreeBSD.org> Cc: Li-Wen Hsu <lwhsu@FreeBSD.org>, Jung-uk Kim <jkim@FreeBSD.org>, src-committers@FreeBSD.org, svn-src-all@FreeBSD.org, svn-src-head@FreeBSD.org Subject: Re: svn commit: r324109 - in head: sys/contrib/dev/acpica sys/contrib/dev/acpica/common sys/contrib/dev/acpica/compiler sys/contrib/dev/acpica/components/dispatcher sys/contrib/dev/acpica/components/ha... Message-ID: <20170930161624.GK95911@kib.kiev.ua> In-Reply-To: <71b114f5-0482-6e69-9c8d-e7f81abcacda@FreeBSD.org> References: <201709292302.v8TN2nTl002342@repo.freebsd.org> <20170930105841.GA25789@freefall.freebsd.org> <20170930120436.GJ95911@kib.kiev.ua> <71b114f5-0482-6e69-9c8d-e7f81abcacda@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Sep 30, 2017 at 05:42:55PM +0300, Andriy Gapon wrote: > On 30/09/2017 15:04, Konstantin Belousov wrote: > > On Sat, Sep 30, 2017 at 10:58:41AM +0000, Li-Wen Hsu wrote: > >> On Fri, Sep 29, 2017 at 23:02:49 +0000, Jung-uk Kim wrote: > >>> Author: jkim > >>> Date: Fri Sep 29 23:02:49 2017 > >>> New Revision: 324109 > >>> URL: https://svnweb.freebsd.org/changeset/base/324109 > >>> > >>> Log: > >>> Merge ACPICA 20170929. > >>> > >>> Added: > >>> head/sys/contrib/dev/acpica/compiler/aslallocate.c > >>> - copied, changed from r324104, vendor-sys/acpica/dist/source/compiler/aslallocate.c > >> > >> Hi Jung-uk, > >> > >> After this change, the test machine booting in bhyve panics with this > >> message: > >> > >> panic: acpi: timer op not yet supported during boot > >> > >> Could you help to check what happened here? The full boot log can be > >> found here: > >> > >> https://ci.freebsd.org/job/FreeBSD-head-amd64-test/4496/console > >> > > > > This happens for me on the real hardware as well. > > > > SMP: passed TSC synchronization test > > Timecounter "TSC" frequency 2095144854 Hz quality 1000 > > random: entropy device external interface > > io: <I/O> > > nfslock: pseudo-device > > mem: <memory> > > null: <full device, null device, zero device> > > nexus0 > > random: harvesting attach, 8 bytes (4 bits) from ram0 > > acpi0: <ALASKA A M I > on motherboard > > ACPI: 4 ACPI AML tables successfully acquired and loaded > > panic: acpi: timer op not yet supported during boot > > Seems like it's triggered by the code that's supposed to limit execution time of > loops. > After your comment I thought that this is another case of an update requiring EARLY_AP_STARTUP option, but apparently the kernel config on this box does contain it already. > > cpuid = 17 > > time = 1 > > KDB: stack backtrace: > > db_trace_self_wrapper() at 0xffffffff802ac6fb = db_trace_self_wrapper+0x2b/frame 0xffffffff80de9da0 > > vpanic() at 0xffffffff80380e0c = vpanic+0x19c/frame 0xffffffff80de9e20 > > kassert_panic() at 0xffffffff80380c6f = kassert_panic+0x16f/frame 0xffffffff80de9e90 > > AcpiOsGetTimer() at 0xffffffff802b1b08 = AcpiOsGetTimer+0x48/frame 0xffffffff80de9eb0 > > AcpiDsExecBeginControlOp() at 0xffffffff80276f40 = AcpiDsExecBeginControlOp+0x80/frame 0xffffffff80de9ee0 > > AcpiPsCreateOp() at 0xffffffff80290c83 = AcpiPsCreateOp+0x1b3/frame 0xffffffff80de9f30 > > AcpiPsParseLoop() at 0xffffffff8029047f = AcpiPsParseLoop+0x1bf/frame 0xffffffff80de9fa0 > > AcpiPsParseAml() at 0xffffffff80291540 = AcpiPsParseAml+0x80/frame 0xffffffff80de9fe0 > > AcpiDsExecuteArguments() at 0xffffffff80276d4d = AcpiDsExecuteArguments+0x13d/frame 0xffffffff80dea040 > > AcpiDsGetRegionArguments() at 0xffffffff80276e96 = AcpiDsGetRegionArguments+0x36/frame 0xffffffff80dea060 > > AcpiNsInitOneObject() at 0xffffffff8028b153 = AcpiNsInitOneObject+0xd3/frame 0xffffffff80dea0a0 > > AcpiNsWalkNamespace() at 0xffffffff8028e673 = AcpiNsWalkNamespace+0xc3/frame 0xffffffff80dea100 > > AcpiWalkNamespace() at 0xffffffff8028ebf9 = AcpiWalkNamespace+0x99/frame 0xffffffff80dea160 > > AcpiNsInitializeObjects() at 0xffffffff8028b052 = AcpiNsInitializeObjects+0x42/frame 0xffffffff80dea1c0 > > AcpiLoadTables() at 0xffffffff80296648 = AcpiLoadTables+0x78/frame 0xffffffff80dea1e0 > > acpi_attach() at 0xffffffff802b59cc = acpi_attach+0x31c/frame 0xffffffff80dea290 > > device_attach() at 0xffffffff803b7833 = device_attach+0x3f3/frame 0xffffffff80dea2d0 > > bus_generic_attach() at 0xffffffff803b898a = bus_generic_attach+0x5a/frame 0xffffffff80dea2f0 > > nexus_acpi_attach() at 0xffffffff805b3593 = nexus_acpi_attach+0x73/frame 0xffffffff80dea320 > > device_attach() at 0xffffffff803b7833 = device_attach+0x3f3/frame 0xffffffff80dea360 > > bus_generic_new_pass() at 0xffffffff803b9016 = bus_generic_new_pass+0x116/frame 0xffffffff80dea390 > > bus_set_pass() at 0xffffffff803b4e1c = bus_set_pass+0x8c/frame 0xffffffff80dea3c0 > > configure() at 0xffffffff806283a9 = configure+0x9/frame 0xffffffff80dea3d0 > > mi_startup() at 0xffffffff8031f4cc = mi_startup+0x9c/frame 0xffffffff80dea3f0 > > btext() at 0xffffffff80268e8c = btext+0x2c > > KDB: enter: panic > > [ thread pid 0 tid 100000 ] > > Stopped at 0xffffffff803c4d9b = kdb_enter+0x3b: movq $0,0xffffffff80a3e260 = kdb_why > > > -- > Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170930161624.GK95911>