bsd.rd failure in VirtualBox

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

bsd.rd failure in VirtualBox

David Higgs
I often use VirtualBox (version 5.2.18 on OS X) to familiarize myself
with new features in snapshots, before upgrading my physical hardware.

This afternoon, I tried updating bsd.rd (amd64, 6.4-beta RAMDISK_CD
#281) and wasn't able to successfully boot it.  I had to rely on the
video capture ability of VirtualBox to even notice there was a panic
(typed out below) before it rebooted to the "BIOS" splash screen.

<snip>
Welcome to the OpenBSD/amd64 6.4 installation program.
fatal protection fault in supervisor mode
trap type 4 code 0 rip ffffffff810f24e4 cs 8 rflags 10206 cr2 6c1fed
cpl a rsp ffff800022098a10
gsbase 0xffffffff8186eff0 kgsbase 0x0
panic: trap type 4, code 0, pc=0xffffffff810f24e4
syncing disks... done

dump to dev 17,1 not possible
rebooting...
</snip>

Also attached is the dmesg from a prior working snapshot.  I haven't
tried updating since this prior snapshot, so I don't have further
insight into when the issue first appeared.

--david

dmesg.txt (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: bsd.rd failure in VirtualBox

Philip Guenther-2
On Sat, Sep 15, 2018 at 11:59 AM David Higgs <[hidden email]> wrote:

> I often use VirtualBox (version 5.2.18 on OS X) to familiarize myself
> with new features in snapshots, before upgrading my physical hardware.
>
> This afternoon, I tried updating bsd.rd (amd64, 6.4-beta RAMDISK_CD
> #281) and wasn't able to successfully boot it.  I had to rely on the
> video capture ability of VirtualBox to even notice there was a panic
> (typed out below) before it rebooted to the "BIOS" splash screen.
>
...

> Also attached is the dmesg from a prior working snapshot.  I haven't
> tried updating since this prior snapshot, so I don't have further
> insight into when the issue first appeared.
>

Thank you for the complete and clear report!

I have a diff in the amd64 snapshots to use the CPU's PCID support in many
cases and this VirtualBox setup found a bug in it.  I've generated a new
diff that should fix this, so a future snap should fix this, though when
that'll happend depends on the snap builder's schedule.


Philip Guenther
Reply | Threaded
Open this post in threaded view
|

Re: bsd.rd failure in VirtualBox

David Higgs
On Sat, Sep 15, 2018 at 10:05 PM, Philip Guenther <[hidden email]> wrote:

> On Sat, Sep 15, 2018 at 11:59 AM David Higgs <[hidden email]> wrote:
>>
>> I often use VirtualBox (version 5.2.18 on OS X) to familiarize myself
>> with new features in snapshots, before upgrading my physical hardware.
>>
>> This afternoon, I tried updating bsd.rd (amd64, 6.4-beta RAMDISK_CD
>> #281) and wasn't able to successfully boot it.  I had to rely on the
>> video capture ability of VirtualBox to even notice there was a panic
>> (typed out below) before it rebooted to the "BIOS" splash screen.
>
> ...
>>
>> Also attached is the dmesg from a prior working snapshot.  I haven't
>> tried updating since this prior snapshot, so I don't have further
>> insight into when the issue first appeared.
>
>
> Thank you for the complete and clear report!
>
> I have a diff in the amd64 snapshots to use the CPU's PCID support in many
> cases and this VirtualBox setup found a bug in it.  I've generated a new
> diff that should fix this, so a future snap should fix this, though when
> that'll happend depends on the snap builder's schedule.
>

Not sure if the fix made it into RAMDISK_CD #282, but this panic is
slightly different.  I haven't tried reproducing to see if the panic
message differs between boots.

<snip>
root on rd0a swap on rd0b dump on rd0b
uvm_fault(0xffffff011f73ac60, 0x208, 0, 1) -> e
fatal page fault in supervisor mode
trap type 6 code 0 rip ffffffff8135510b cs 8 rflags 10246 cr2 208 cpl
0 rsp ffff800022026c90
gsbase 0xffffffff81870ff0 kgsbase 0x0
panic: trap type 6, code=0, pc=ffffffff8135510b
syncing disk... done

dump to dev 17,1 not possible
rebooting...
</snip>

Hope this helps.

--david

Reply | Threaded
Open this post in threaded view
|

Re: bsd.rd failure in VirtualBox

David Higgs
On Sun, Sep 16, 2018 at 10:17 AM, David Higgs <[hidden email]> wrote:

> On Sat, Sep 15, 2018 at 10:05 PM, Philip Guenther <[hidden email]> wrote:
>> On Sat, Sep 15, 2018 at 11:59 AM David Higgs <[hidden email]> wrote:
>>>
>>> I often use VirtualBox (version 5.2.18 on OS X) to familiarize myself
>>> with new features in snapshots, before upgrading my physical hardware.
>>>
>>> This afternoon, I tried updating bsd.rd (amd64, 6.4-beta RAMDISK_CD
>>> #281) and wasn't able to successfully boot it.  I had to rely on the
>>> video capture ability of VirtualBox to even notice there was a panic
>>> (typed out below) before it rebooted to the "BIOS" splash screen.
>>
>> ...
>>>
>>> Also attached is the dmesg from a prior working snapshot.  I haven't
>>> tried updating since this prior snapshot, so I don't have further
>>> insight into when the issue first appeared.
>>
>>
>> Thank you for the complete and clear report!
>>
>> I have a diff in the amd64 snapshots to use the CPU's PCID support in many
>> cases and this VirtualBox setup found a bug in it.  I've generated a new
>> diff that should fix this, so a future snap should fix this, though when
>> that'll happend depends on the snap builder's schedule.
>>
>
> Not sure if the fix made it into RAMDISK_CD #282, but this panic is
> slightly different.  I haven't tried reproducing to see if the panic
> message differs between boots.
>
> <snip>
> root on rd0a swap on rd0b dump on rd0b
> uvm_fault(0xffffff011f73ac60, 0x208, 0, 1) -> e
> fatal page fault in supervisor mode
> trap type 6 code 0 rip ffffffff8135510b cs 8 rflags 10246 cr2 208 cpl
> 0 rsp ffff800022026c90
> gsbase 0xffffffff81870ff0 kgsbase 0x0
> panic: trap type 6, code=0, pc=ffffffff8135510b
> syncing disk... done
>
> dump to dev 17,1 not possible
> rebooting...
> </snip>
>
> Hope this helps.
>

FWIW, the vbox capture feature is pretty buggy - it doesn't create the
file when it says it is recording, and it frequently crashes.  It is
possible the panic above is from #281 instead, because I deleted the
video before I realizing this.

Below is definitely from #282.

<snip>
Welcome to the OpenBSD/amd64 6.4 installation program.
fatal protection fault in supervisor mode
trap type 4 code 0 rip ffffffff810f4244 cs 8 rflags 10286 cr2 6c1fed
cpl a rsp ffff800022098800
gsbase 0xffffffff81870ff0 kgsbase 0x0
panic: trap type 4, code 0, pc=0x ffffffff810f4244
syncing disks... done

dump to dev 17,1 not possible
rebooting...
</snip>

Hope this is actually useful and not another stupid VirtualBox bug.

--david

Reply | Threaded
Open this post in threaded view
|

Re: bsd.rd failure in VirtualBox

Johan Huldtgren-2
On 2018/09/16 10:52, David Higgs wrote:

> On Sun, Sep 16, 2018 at 10:17 AM, David Higgs <[hidden email]> wrote:
>> On Sat, Sep 15, 2018 at 10:05 PM, Philip Guenther <[hidden email]> wrote:
>>> On Sat, Sep 15, 2018 at 11:59 AM David Higgs <[hidden email]> wrote:
>>>>
>>>> I often use VirtualBox (version 5.2.18 on OS X) to familiarize myself
>>>> with new features in snapshots, before upgrading my physical hardware.
>>>>
>>>> This afternoon, I tried updating bsd.rd (amd64, 6.4-beta RAMDISK_CD
>>>> #281) and wasn't able to successfully boot it.  I had to rely on the
>>>> video capture ability of VirtualBox to even notice there was a panic
>>>> (typed out below) before it rebooted to the "BIOS" splash screen.
>>>
>>> ...
>>>>
>>>> Also attached is the dmesg from a prior working snapshot.  I haven't
>>>> tried updating since this prior snapshot, so I don't have further
>>>> insight into when the issue first appeared.
>>>
>>>
>>> Thank you for the complete and clear report!
>>>
>>> I have a diff in the amd64 snapshots to use the CPU's PCID support in many
>>> cases and this VirtualBox setup found a bug in it.  I've generated a new
>>> diff that should fix this, so a future snap should fix this, though when
>>> that'll happend depends on the snap builder's schedule.
>>>
>>
>> Not sure if the fix made it into RAMDISK_CD #282, but this panic is
>> slightly different.  I haven't tried reproducing to see if the panic
>> message differs between boots.
>>
>> <snip>
>> root on rd0a swap on rd0b dump on rd0b
>> uvm_fault(0xffffff011f73ac60, 0x208, 0, 1) -> e
>> fatal page fault in supervisor mode
>> trap type 6 code 0 rip ffffffff8135510b cs 8 rflags 10246 cr2 208 cpl
>> 0 rsp ffff800022026c90
>> gsbase 0xffffffff81870ff0 kgsbase 0x0
>> panic: trap type 6, code=0, pc=ffffffff8135510b
>> syncing disk... done
>>
>> dump to dev 17,1 not possible
>> rebooting...
>> </snip>
>>
>> Hope this helps.
>>
>
> FWIW, the vbox capture feature is pretty buggy - it doesn't create the
> file when it says it is recording, and it frequently crashes.  It is
> possible the panic above is from #281 instead, because I deleted the
> video before I realizing this.
>
> Below is definitely from #282.
>
> <snip>
> Welcome to the OpenBSD/amd64 6.4 installation program.
> fatal protection fault in supervisor mode
> trap type 4 code 0 rip ffffffff810f4244 cs 8 rflags 10286 cr2 6c1fed
> cpl a rsp ffff800022098800
> gsbase 0xffffffff81870ff0 kgsbase 0x0
> panic: trap type 4, code 0, pc=0x ffffffff810f4244
> syncing disks... done
>
> dump to dev 17,1 not possible
> rebooting...
> </snip>
>
> Hope this is actually useful and not another stupid VirtualBox bug.

I see this an almost identical panic on real hardware too, the only difference
being the string after 'rsp'

Welcome to the OpenBSD/amd64 6.4 installation program.
fatal protection fault in supervisor mode
trap type 4 code 0 rip ffffffff810f4244 cs 8 rflags 10286 cr2 6c1fed cpl a rsp ffff8000220ba9e0
gsbase 0xffffffff81870ff0 kgsbase 0x0
panic: trap type 4, code 0, pc=ffffffff810f4244
syncing disks... done

dump to dev 17,1 not possible
rebooting...

Below is first the working dmesg snapshot, and then one from booting bsd.rd, note
the ACPI error about not being able to load tables, that's not there on the working
snap. That might be the culprit at least in my case?

thanks,

.jh

dmesg from the working snapshot:

OpenBSD 6.3-current (GENERIC.MP) #180: Fri Aug  3 20:53:10 MDT 2018
    [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 16838430720 (16058MB)
avail mem = 16318918656 (15562MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xec820 (29 entries)
bios0: vendor American Megatrends Inc. version "P2.10" date 05/12/2015
bios0: ASRock Z97 Extreme4
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT SSDT SSDT SSDT MCFG HPET SSDT SSDT AAFT UEFI
acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PS2K(S4) UAR1(S4) USB1(S3) PXSX(S4) RP01(S4) PXSX(S4) PXSX(S4) PXSX(S4) RP04(S4) PXSX(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Pentium(R) CPU G3258 @ 3.20GHz, 3199.54 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,SDBG,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Pentium(R) CPU G3258 @ 3.20GHz, 3199.08 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,SDBG,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 8 pa 0xfec00000, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xf8000000, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (PEG0)
acpiprt2 at acpi0: bus 2 (PEG1)
acpiprt3 at acpi0: bus 3 (PEG2)
acpiprt4 at acpi0: bus 4 (RP01)
acpiprt5 at acpi0: bus 5 (RP04)
acpiprt6 at acpi0: bus 6 (RP06)
acpiprt7 at acpi0: bus 7 (RP07)
acpiec0 at acpi0: not present
acpicpu0 at acpi0: C2(500@67 mwait.1@0x10), C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C2(500@67 mwait.1@0x10), C1(1000@1 mwait.1), PSS
acpicmos0 at acpi0
"INT3F0D" at acpi0 not configured
"MSFT0001" at acpi0 not configured
"INT33CA" at acpi0 not configured
"PNP0C14" at acpi0 not configured
acpibtn0 at acpi0: PWRB
acpibtn1 at acpi0: SLPB
acpivideo0 at acpi0: GFX0
acpivout0 at acpivideo0: DD1F
cpu0: Enhanced SpeedStep 3199 MHz: speeds: 3201, 3200, 3000, 2900, 2700, 2500, 2300, 2200, 2000, 1800, 1700, 1500, 1300, 1100, 1000, 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Core 4G Host" rev 0x06
ppb0 at pci0 dev 1 function 0 "Intel Core 4G PCIE" rev 0x06: msi
pci1 at ppb0 bus 1
ppb1 at pci0 dev 1 function 1 "Intel Core 4G PCIE" rev 0x06: msi
pci2 at ppb1 bus 2
ppb2 at pci0 dev 1 function 2 "Intel Core 4G PCIE" rev 0x06: msi
pci3 at ppb2 bus 3
mfii0 at pci3 dev 0 function 0 "Symbios Logic MegaRAID SAS2208" rev 0x05: msi
mfii0: "LSI MegaRAID SAS 9271-8i", firmware 23.34.0-0017, 1024MB cache
scsibus1 at mfii0: 64 targets
sd0 at scsibus1 targ 0 lun 0: <LSI, MR9271-8i, 3.46> SCSI3 0/direct fixed naa.600605b00a74c2a01e622aec123aced2
sd0: 13344758MB, 512 bytes/sector, 27330064384 sectors
scsibus2 at mfii0: 256 targets
inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics" rev 0x06
drm0 at inteldrm0
inteldrm0: msi
inteldrm0: 1280x1024, 32bpp
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
azalia0 at pci0 dev 3 function 0 "Intel Core 4G HD Audio" rev 0x06: msi
azalia0: No codecs found
xhci0 at pci0 dev 20 function 0 "Intel 9 Series xHCI" rev 0x00: msi, xHCI 1.0
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 addr 1
"Intel 9 Series MEI" rev 0x00 at pci0 dev 22 function 0 not configured
em0 at pci0 dev 25 function 0 "Intel I218-V" rev 0x00: msi, address d0:50:99:5a:09:1c
ehci0 at pci0 dev 26 function 0 "Intel 9 Series USB" rev 0x00: apic 8 int 16
usb1 at ehci0: USB revision 2.0
uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
azalia1 at pci0 dev 27 function 0 "Intel 9 Series HD Audio" rev 0x00: msi
azalia1: codecs: Realtek ALC1150
audio0 at azalia1
ppb3 at pci0 dev 28 function 0 "Intel 9 Series PCIE" rev 0xd0
pci4 at ppb3 bus 4
ppb4 at pci0 dev 28 function 3 "Intel 9 Series PCIE" rev 0xd0: msi
pci5 at ppb4 bus 5
ahci0 at pci5 dev 0 function 0 "ASMedia ASM1061 AHCI" rev 0x02: msi, AHCI 1.2
scsibus3 at ahci0: 32 targets
ppb5 at pci0 dev 28 function 5 "Intel 9 Series PCIE" rev 0xd0: msi
pci6 at ppb5 bus 6
ahci1 at pci6 dev 0 function 0 "ASMedia ASM1061 AHCI" rev 0x01: msi, AHCI 1.2
ahci1: port 0: 6.0Gb/s
scsibus4 at ahci1: 32 targets
sd1 at scsibus4 targ 0 lun 0: <ATA, SanDisk SDSSDA12, Z220> SCSI3 0/direct fixed naa.5001b44e915e1444
sd1: 114473MB, 512 bytes/sector, 234441648 sectors, thin
ppb6 at pci0 dev 28 function 6 "Intel 9 Series PCIE" rev 0xd0: msi
pci7 at ppb6 bus 7
xhci1 at pci7 dev 0 function 0 "ASMedia ASM1042A xHCI" rev 0x00: msi, xHCI 1.0
usb2 at xhci1: USB revision 3.0
uhub2 at usb2 configuration 1 interface 0 "ASMedia xHCI root hub" rev 3.00/1.00 addr 1
ehci1 at pci0 dev 29 function 0 "Intel 9 Series USB" rev 0x00: apic 8 int 23
usb3 at ehci1: USB revision 2.0
uhub3 at usb3 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
pcib0 at pci0 dev 31 function 0 "Intel Z97 LPC" rev 0x00
ichiic0 at pci0 dev 31 function 3 "Intel 9 Series SMBus" rev 0x00: apic 8 int 18
iic0 at ichiic0
spdmem0 at iic0 addr 0x51: 8GB DDR3 SDRAM PC3-12800
spdmem1 at iic0 addr 0x53: 8GB DDR3 SDRAM PC3-12800
isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
vmm0 at mainbus0: VMX/EPT
ugen0 at uhub0 port 7 "American Power Conversion Back-UPS RS 1300G FW:863.L3 .D USB FW:L3" rev 2.00/0.90 addr 2
uhub4 at uhub1 port 1 configuration 1 interface 0 "Intel Rate Matching Hub" rev 2.00/0.00 addr 2
uhub5 at uhub3 port 1 configuration 1 interface 0 "Intel Rate Matching Hub" rev 2.00/0.00 addr 2
vscsi0 at root
scsibus5 at vscsi0: 256 targets
softraid0 at root
scsibus6 at softraid0: 256 targets
root on sd1a (10906fca8f4bb5bf.a) swap on sd1b dump on sd1b

dmesg from the buffer when booting bsd.rd (but doesn't show panic)

OpenBSD 6.4-beta (RAMDISK_CD) #282: Sat Sep 15 19:43:32 MDT 2018
    [hidden email]:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
real mem = 16838430720 (16058MB)
avail mem = 16324325376 (15568MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xec820 (29 entries)
bios0: vendor American Megatrends Inc. version "P2.10" date 05/12/2015
bios0: ASRock Z97 Extreme4
acpi0 at bios0: rev 196couldn't map rsdt
, can't load tables
cpu0 at mainbus0: (uniprocessor)
cpu0: Intel(R) Pentium(R) CPU G3258 @ 3.20GHz, 3199.52 MHz, 06-3c-03
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,SDBG,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,ERMS,INVPCID,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: mwait min=64, max=64, C-substates=0.2.1.2, IBE
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Core 4G Host" rev 0x06
ppb0 at pci0 dev 1 function 0 "Intel Core 4G PCIE" rev 0x06: irq 11
pci1 at ppb0 bus 1
ppb1 at pci0 dev 1 function 1 "Intel Core 4G PCIE" rev 0x06: irq 11
pci2 at ppb1 bus 2
ppb2 at pci0 dev 1 function 2 "Intel Core 4G PCIE" rev 0x06: irq 11
pci3 at ppb2 bus 3
mfii0 at pci3 dev 0 function 0 "Symbios Logic MegaRAID SAS2208" rev 0x05: irq 10
mfii0: "LSI MegaRAID SAS 9271-8i", firmware 23.34.0-0017, 1024MB cache
scsibus0 at mfii0: 64 targets
sd0 at scsibus0 targ 0 lun 0: <LSI, MR9271-8i, 3.46> SCSI3 0/direct fixed naa.600605b00a74c2a01e622aec123aced2
sd0: 13344758MB, 512 bytes/sector, 27330064384 sectors
scsibus1 at mfii0: 256 targets
vga1 at pci0 dev 2 function 0 "Intel HD Graphics" rev 0x06
wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation)
"Intel Core 4G HD Audio" rev 0x06 at pci0 dev 3 function 0 not configured
xhci0 at pci0 dev 20 function 0 "Intel 9 Series xHCI" rev 0x00: irq 11, xHCI 1.0
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 addr 1
"Intel 9 Series MEI" rev 0x00 at pci0 dev 22 function 0 not configured
em0 at pci0 dev 25 function 0 "Intel I218-V" rev 0x00: irq 3, address d0:50:99:5a:09:1c
ehci0 at pci0 dev 26 function 0 "Intel 9 Series USB" rev 0x00: irq 11
usb1 at ehci0: USB revision 2.0
uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
"Intel 9 Series HD Audio" rev 0x00 at pci0 dev 27 function 0 not configured
ppb3 at pci0 dev 28 function 0 "Intel 9 Series PCIE" rev 0xd0
pci4 at ppb3 bus 4
ppb4 at pci0 dev 28 function 3 "Intel 9 Series PCIE" rev 0xd0: irq 5
pci5 at ppb4 bus 5
ahci0 at pci5 dev 0 function 0 "ASMedia ASM1061 AHCI" rev 0x02: irq 5, AHCI 1.2
scsibus2 at ahci0: 32 targets
ppb5 at pci0 dev 28 function 5 "Intel 9 Series PCIE" rev 0xd0: irq 10
pci6 at ppb5 bus 6
ahci1 at pci6 dev 0 function 0 "ASMedia ASM1061 AHCI" rev 0x01: irq 10, AHCI 1.2
ahci1: port 0: 6.0Gb/s
scsibus3 at ahci1: 32 targets
sd1 at scsibus3 targ 0 lun 0: <ATA, SanDisk SDSSDA12, Z220> SCSI3 0/direct fixed naa.5001b44e915e1444
sd1: 114473MB, 512 bytes/sector, 234441648 sectors, thin
ppb6 at pci0 dev 28 function 6 "Intel 9 Series PCIE" rev 0xd0: irq 10
pci7 at ppb6 bus 7
xhci1 at pci7 dev 0 function 0 "ASMedia ASM1042A xHCI" rev 0x00: irq 10, xHCI 1.0
usb2 at xhci1: USB revision 3.0
uhub2 at usb2 configuration 1 interface 0 "ASMedia xHCI root hub" rev 3.00/1.00 addr 1
ehci1 at pci0 dev 29 function 0 "Intel 9 Series USB" rev 0x00: irq 5
usb3 at ehci1: USB revision 2.0
uhub3 at usb3 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
"Intel Z97 LPC" rev 0x00 at pci0 dev 31 function 0 not configured
"Intel 9 Series SMBus" rev 0x00 at pci0 dev 31 function 3 not configured
isa0 at mainbus0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay1
uhidev0 at uhub0 port 7 configuration 1 interface 0 "American Power Conversion Back-UPS RS 1300G FW:863.L3 .D USB FW:L3" rev 2.00/0.90 addr 2
uhidev0: iclass 3/0, 146 report ids
uhid at uhidev0 reportid 1 not configured
uhid at uhidev0 reportid 2 not configured
uhid at uhidev0 reportid 3 not configured
uhid at uhidev0 reportid 4 not configured
uhid at uhidev0 reportid 5 not configured
uhid at uhidev0 reportid 6 not configured
uhid at uhidev0 reportid 7 not configured
uhid at uhidev0 reportid 8 not configured
uhid at uhidev0 reportid 9 not configured
uhid at uhidev0 reportid 10 not configured
uhid at uhidev0 reportid 11 not configured
uhid at uhidev0 reportid 12 not configured
uhid at uhidev0 reportid 13 not configured
uhid at uhidev0 reportid 14 not configured
uhid at uhidev0 reportid 15 not configured
uhid at uhidev0 reportid 16 not configured
uhid at uhidev0 reportid 17 not configured
uhid at uhidev0 reportid 18 not configured
uhid at uhidev0 reportid 19 not configured
uhid at uhidev0 reportid 20 not configured
uhid at uhidev0 reportid 21 not configured
uhid at uhidev0 reportid 22 not configured
uhid at uhidev0 reportid 23 not configured
uhid at uhidev0 reportid 24 not configured
uhid at uhidev0 reportid 28 not configured
uhid at uhidev0 reportid 32 not configured
uhid at uhidev0 reportid 33 not configured
uhid at uhidev0 reportid 34 not configured
uhid at uhidev0 reportid 35 not configured
uhid at uhidev0 reportid 36 not configured
uhid at uhidev0 reportid 37 not configured
uhid at uhidev0 reportid 38 not configured
uhid at uhidev0 reportid 39 not configured
uhid at uhidev0 reportid 40 not configured
uhid at uhidev0 reportid 48 not configured
uhid at uhidev0 reportid 49 not configured
uhid at uhidev0 reportid 50 not configured
uhid at uhidev0 reportid 51 not configured
uhid at uhidev0 reportid 52 not configured
uhid at uhidev0 reportid 53 not configured
uhid at uhidev0 reportid 54 not configured
uhid at uhidev0 reportid 64 not configured
uhid at uhidev0 reportid 65 not configured
uhid at uhidev0 reportid 66 not configured
uhid at uhidev0 reportid 80 not configured
uhid at uhidev0 reportid 81 not configured
uhid at uhidev0 reportid 82 not configured
uhid at uhidev0 reportid 96 not configured
uhid at uhidev0 reportid 97 not configured
uhid at uhidev0 reportid 98 not configured
uhid at uhidev0 reportid 116 not configured
uhid at uhidev0 reportid 117 not configured
uhid at uhidev0 reportid 120 not configured
uhid at uhidev0 reportid 121 not configured
uhid at uhidev0 reportid 122 not configured
uhid at uhidev0 reportid 123 not configured
uhid at uhidev0 reportid 124 not configured
uhid at uhidev0 reportid 125 not configured
uhid at uhidev0 reportid 126 not configured
uhid at uhidev0 reportid 127 not configured
uhid at uhidev0 reportid 128 not configured
uhid at uhidev0 reportid 140 not configured
uhid at uhidev0 reportid 141 not configured
uhid at uhidev0 reportid 142 not configured
uhid at uhidev0 reportid 143 not configured
uhid at uhidev0 reportid 144 not configured
uhid at uhidev0 reportid 145 not configured
uhid at uhidev0 reportid 146 not configured
uhub4 at uhub1 port 1 configuration 1 interface 0 "vendor 0x8087 product 0x8009" rev 2.00/0.00 addr 2
uhub5 at uhub3 port 1 configuration 1 interface 0 "vendor 0x8087 product 0x8001" rev 2.00/0.00 addr 2
softraid0 at root
scsibus4 at softraid0: 256 targets
root on rd0a swap on rd0b dump on rd0b

Reply | Threaded
Open this post in threaded view
|

Re: bsd.rd failure in VirtualBox

David Higgs
On Sun, Sep 16, 2018 at 1:15 PM, Johan Huldtgren
<[hidden email]> wrote:

> On 2018/09/16 10:52, David Higgs wrote:
>> On Sun, Sep 16, 2018 at 10:17 AM, David Higgs <[hidden email]> wrote:
>>> On Sat, Sep 15, 2018 at 10:05 PM, Philip Guenther <[hidden email]> wrote:
>>>> On Sat, Sep 15, 2018 at 11:59 AM David Higgs <[hidden email]> wrote:
>>>>>
>>>>> I often use VirtualBox (version 5.2.18 on OS X) to familiarize myself
>>>>> with new features in snapshots, before upgrading my physical hardware.
>>>>>
>>>>> This afternoon, I tried updating bsd.rd (amd64, 6.4-beta RAMDISK_CD
>>>>> #281) and wasn't able to successfully boot it.  I had to rely on the
>>>>> video capture ability of VirtualBox to even notice there was a panic
>>>>> (typed out below) before it rebooted to the "BIOS" splash screen.
>>>>
>>>> ...
>>>>>
>>>>> Also attached is the dmesg from a prior working snapshot.  I haven't
>>>>> tried updating since this prior snapshot, so I don't have further
>>>>> insight into when the issue first appeared.
>>>>
>>>>
>>>> Thank you for the complete and clear report!
>>>>
>>>> I have a diff in the amd64 snapshots to use the CPU's PCID support in many
>>>> cases and this VirtualBox setup found a bug in it.  I've generated a new
>>>> diff that should fix this, so a future snap should fix this, though when
>>>> that'll happend depends on the snap builder's schedule.
>>>>
>>>
>>> Not sure if the fix made it into RAMDISK_CD #282, but this panic is
>>> slightly different.  I haven't tried reproducing to see if the panic
>>> message differs between boots.
>>>
>>> <snip>
>>> root on rd0a swap on rd0b dump on rd0b
>>> uvm_fault(0xffffff011f73ac60, 0x208, 0, 1) -> e
>>> fatal page fault in supervisor mode
>>> trap type 6 code 0 rip ffffffff8135510b cs 8 rflags 10246 cr2 208 cpl
>>> 0 rsp ffff800022026c90
>>> gsbase 0xffffffff81870ff0 kgsbase 0x0
>>> panic: trap type 6, code=0, pc=ffffffff8135510b
>>> syncing disk... done
>>>
>>> dump to dev 17,1 not possible
>>> rebooting...
>>> </snip>
>>>
>>> Hope this helps.
>>>
>>
>> FWIW, the vbox capture feature is pretty buggy - it doesn't create the
>> file when it says it is recording, and it frequently crashes.  It is
>> possible the panic above is from #281 instead, because I deleted the
>> video before I realizing this.
>>
>> Below is definitely from #282.
>>
>> <snip>
>> Welcome to the OpenBSD/amd64 6.4 installation program.
>> fatal protection fault in supervisor mode
>> trap type 4 code 0 rip ffffffff810f4244 cs 8 rflags 10286 cr2 6c1fed
>> cpl a rsp ffff800022098800
>> gsbase 0xffffffff81870ff0 kgsbase 0x0
>> panic: trap type 4, code 0, pc=0x ffffffff810f4244
>> syncing disks... done
>>
>> dump to dev 17,1 not possible
>> rebooting...
>> </snip>
>>
>> Hope this is actually useful and not another stupid VirtualBox bug.
>
> I see this an almost identical panic on real hardware too, the only difference
> being the string after 'rsp'
>
> Welcome to the OpenBSD/amd64 6.4 installation program.
> fatal protection fault in supervisor mode
> trap type 4 code 0 rip ffffffff810f4244 cs 8 rflags 10286 cr2 6c1fed cpl a rsp ffff8000220ba9e0
> gsbase 0xffffffff81870ff0 kgsbase 0x0
> panic: trap type 4, code 0, pc=ffffffff810f4244
> syncing disks... done
>
> dump to dev 17,1 not possible
> rebooting...
>
> Below is first the working dmesg snapshot, and then one from booting bsd.rd, note
> the ACPI error about not being able to load tables, that's not there on the working
> snap. That might be the culprit at least in my case?
>

FYI - successfully booted with RAMDISK_CD #283 and installed a
successfully-booting GENERIC #284 within VirtualBox.

Thanks again.

--david