[DragonFlyBSD - Bug #2528] (Closed) In VirtualBox one of possible network interfaces fails to attach

Sascha Wildner via Redmine bugtracker-admin at leaf.dragonflybsd.org
Mon Apr 15 12:44:14 PDT 2013

Issue #2528 has been updated by swildner.

Status changed from New to Closed

Bug #2528: In VirtualBox one of possible network interfaces fails to attach

Author: kworr
Status: Closed
Priority: Low
Target version: 

After updating to current HEAD and recompiling machine fails to boot trapping at device detection:

lnc0: <AMD PCnet-PCI> port 0xd000-0xd01f mem 0xf0080000-0xf00fffff,0xf0000000-0xf0000fff irq 19 at device 3.0 on pci0
lnc0: 16 receive buffers, 4 transmit buffers

Fatal trap 12: page fault while in kernel mode
cpuid = 0; lapic->id = 00000000
fault virtual address = 0x74
fault code = supervisor write data, page not present
instruction pointer = 0x8:0xffffffff80767f8f
stack pointer = 0x10:0xffffffff824e5570
frame pointer = 0x10:0xffffffff824e5570
code segment = base 0x0. limit 0xfffff, type 0x1b
 = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 0
current thread = pri 12
kernel: type 12 trap, code=2

CPU0 stopping CPOUs: 0x0000000e
Stopped at lance_stop+0x19: movl $0,0x74(%rdx)

You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account

More information about the Bugs mailing list