Re: -current build crashing at startup under bhyve (ACPICA?)

[Dustin Marquess <dmarquess%gmail.com@localhost>]

Actually, I think you're right, sorry.  Looks like it's not the NetBSD
kernel crashing, it's the bhyve hypervisor itself crashing.

Sorry, about that, brain wasn't entirely functional late at night.
Forgive the spam!

-Dustin

On Thu, May 26, 2016 at 9:45 AM, Christos Zoulas <christos%astron.com@localhost> wrote:
> In article <CAJpsHY7jLOH-QTLxy_gvjV3AtuKkTpy9LFJN4CANjfUN9Tam2A%mail.gmail.com@localhost>,
> Dustin Marquess  <dmarquess%gmail.com@localhost> wrote:
>>Hello,
>>
>>I just recently upgraded a VM running under bhyve to a -current build
>>from ~8 hours ago.  Booting it now instantly crashes at boot right
>>after ACPICA:
>>
>>Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
>>    2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016
>>    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.29 (XXX) #0: Wed May 25 17:44:40 CDT 2016
>>        root@xxx:/usr/obj/sys/arch/amd64/compile/XXX
>>total memory = 8191 MB
>>avail memory = 7946 MB
>>mainbus0 (root)
>>ACPI: RSDP 0x00000000000F2400 000024 (v02 BHYVE )
>>ACPI: XSDT 0x00000000000F2480 000044 (v01 BHYVE  BVXSDT   00000001
>>INTL 20160422)
>>ACPI: APIC 0x00000000000F2500 0000D2 (v01 BHYVE  BVMADT   00000001
>>INTL 20160422)
>>ACPI: FACP 0x00000000000F2600 00010C (v05 BHYVE  BVFACP   00000001
>>INTL 20160422)
>>ACPI: DSDT 0x00000000000F2800 0008FD (v02 BHYVE  BVDSDT   00000001
>>INTL 20160422)
>>ACPI: FACS 0x00000000000F27C0 000040
>>ACPI: FACS 0x00000000000F27C0 000040
>>ACPI: HPET 0x00000000000F2740 000038 (v01 BHYVE  BVHPET   00000001
>>INTL 20160422)
>>ACPI: MCFG 0x00000000000F2780 00003C (v01 BHYVE  BVMCFG   00000001
>>INTL 20160422)
>>ACPI: 1 ACPI AML tables successfully acquired and loaded
>>
>>ioapic0 at mainbus0 apid 0
>>cpu0 at mainbus0 apid 0
>>cpu0: AMD Opteron(TM) Processor 6220                 , id 0x600f12
>>cpu1 at mainbus0 apid 1
>>cpu1: AMD Opteron(TM) Processor 6220                 , id 0x600f12
>>cpu2 at mainbus0 apid 2
>>cpu2: AMD Opteron(TM) Processor 6220                 , id 0x600f12
>>cpu3 at mainbus0 apid 3
>>cpu3: AMD Opteron(TM) Processor 6220                 , id 0x600f12
>>cpu4 at mainbus0 apid 4
>>cpu4: AMD Opteron(TM) Processor 6220                 , id 0x600f12
>>cpu5 at mainbus0 apid 5
>>cpu5: AMD Opteron(TM) Processor 6220                 , id 0x600f12
>>cpu6 at mainbus0 apid 6
>>cpu6: AMD Opteron(TM) Processor 6220                 , id 0x600f12
>>cpu7 at mainbus0 apid 7
>>cpu7: AMD Opteron(TM) Processor 6220                 , id 0x600f12
>>cpu8 at mainbus0 apid 8
>>cpu8: AMD Opteron(TM) Processor 6220                 , id 0x600f12
>>cpu9 at mainbus0 apid 9
>>cpu9: AMD Opteron(TM) Processor 6220                 , id 0x600f12
>>cpu10 at mainbus0 apid 10
>>cpu10: AMD Opteron(TM) Processor 6220                 , id 0x600f12
>>cpu11 at mainbus0 apid 11
>>cpu11: AMD Opteron(TM) Processor 6220                 , id 0x600f12
>>cpu12 at mainbus0 apid 12
>>cpu12: AMD Opteron(TM) Processor 6220                 , id 0x600f12
>>cpu13 at mainbus0 apid 13
>>cpu13: AMD Opteron(TM) Processor 6220                 , id 0x600f12
>>cpu14 at mainbus0 apid 14
>>cpu14: AMD Opteron(TM) Processor 6220                 , id 0x600f12
>>cpu15 at mainbus0 apid 15
>>cpu15: AMD Opteron(TM) Processor 6220                 , id 0x600f12
>>acpi0 at mainbus0: Intel ACPICA 20160422
>>Unhandled inl 0x0402 at 0xffffffff80114b86
>>                                          Abort trap (core dumped)
>>
>
> I am confused. IS the kernel crashing or userland?
>
> christos
>