Kernel trap when booting inside VirtualBox

[Paul Wootton]

On Tue, Apr 12, 2016 at 08:56AM, Konstantin Belousov wrote:
>On Tue, Apr 12, 2016 at 07:14:47AM +0100, paulw at fisheyehq.com wrote:
>> Hi,
>> 
>> Has anyone else got an issue with running FreeBSD SVN r297810 inside a 
>> VirtualBox session?
>> 
>> I installed 10.3, booting under EFI on my second harddrive (Windows in 
>> on the first drive). FreeBSD would boot correctly from UEFI boot or from 
>> inside VirtualBox. I SVNed up to head (r297810), compiled and installed 
>> it.
>> It will now boot correctly from UEFI boot, but kernel traps very early 
>> on when booted from VirtualBox.
>> 
>> As a side note, I am using booting from zfs.
>> I am starting FreeBSD by calling boot1.efi from inside EFIShell (from 
>> both UEFI boot and VirtualBox)
>> 
>> Has anyone else seen this? Is it my setup?
>> 
>> real memory  = 4831838208 (4608 MB)
>> avail memory = 4096802816 (3907 MB)
>> Event timer "LAPIC" quality 400
>> APIC APIC Table: <VBOX   VBOXAPIC>
>> Random: unblocking device.
>> Loapic0 <Version 1.1> irqs 0-23 on motherboard Kernel trap 1 with 
>> interrupts disabled
>> 
>> 
>> Fatal trap 1: privileged instruction fault while in kernel mode cpuid = 
>> 0: apic id = 00
>> instruction pointer     = 0x20:0xffffffff80fed419
>> stack pointer           = 0x28:0xffffffff824d9c00
>> frame pointer           = 0x28:0xffffffff824d9c80
>> code segment            = base 0x0, Limit 0xfffff, type 0x1b
>>                           = DPL 0, pres 1, long 1, def32 0, gran 1
>> Processor eflags        = resume, IOPL = 0
>> Current process         = 0 (swapper)
>> [ thread pid 0 tid 100000 ]
>> Stopped as      native_lapic_setup+0x99:         lesl    %edx,%esp
>> db>bt
>> Tracing pis 0 tid 100000 td 0xffffffff81d351b0
>> native_lapic_setup() at native_lapic_setup+0x99/frame 0xffffffff8249c80
>> apic_setup_io() at apic_setup_io+0x53/frame 0xffffffff824d9c90
>> mi_startup() at mi_startup+0x118/frame 0xffffffff824d9cb0
>> btext() at btext+0x2c
>> db>
>> 
>Was the panic text above trascribed from the screen manually ?
>
>Anyway, please do 'kgdb kernel.debug' for your HEAD kernel, and
>send me the disassemble of the native_lapic_setup function.

Yeah, I typed the panic out by hand

"
Dump of assembler code for function native_lapic_setup:
0xffffffff80fd1320 <native_lapic_setup+0>:      add    %al,(%rax)
0xffffffff80fd1322 <native_lapic_setup+2>:      add    %al,(%rax)
0xffffffff80fd1324 <native_lapic_setup+4>:      add    %al,(%rax)
0xffffffff80fd1326 <native_lapic_setup+6>:      add    %al,(%rax)
0xffffffff80fd1328 <native_lapic_setup+8>:      add    %al,(%rax)
...
...
0xffffffff80fd1880 <native_lapic_setup+1376>:   add    %al,(%rax)
0xffffffff80fd1882 <native_lapic_setup+1378>:   add    %al,(%rax)
0xffffffff80fd1884 <native_lapic_setup+1380>:   add    %al,(%rax)
0xffffffff80fd1886 <native_lapic_setup+1382>:   add    %al,(%rax)
End of assembler dump
"
Every line is the same instruction, add %al,(%rax)

I downloaded an ISO of r294499 and that booted correctly inside VBox.
I SVNed down to r294499, compiled and that did not boot. Did a disassembley
and it's the same as above.
I downloaded an ISO of r297692 and that booted correctly.

So it's got to be either my kernel conf or my enviroment

Im going to try and compile a generic kernel and see if that works


Paul


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus