Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 24 Jul 2017 20:28:03 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 220980] [panic] panic when destroying vlan interface with traffic
Message-ID:  <bug-220980-8@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220980

            Bug ID: 220980
           Summary: [panic] panic when destroying vlan interface with
                    traffic
           Product: Base System
           Version: 11.0-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: kxie@xiplink.com

When running around 30MBps bridge-over-vlan traffic on a virtualbox vm base=
d on
FreeBSD 11-Release live CD, I tried to destroy one of the VLAN interfaces  =
of
the bridge with "ifconfig vlanX destroy". Sometimes(~25%), a panic happened.
The panic info is as follows:

Fatal trap 12: page fault while in kernel mode
cpuid =3D 0; apic id =3D 00
fault virtual address   =3D 0x3b0
fault code              =3D supervisor read data, page not present
instruction pointer     =3D 0x20:0xffffffff80ab48ca
stack pointer           =3D 0x28:0xfffffe003c947550
frame pointer           =3D 0x28:0xfffffe003c9475d0
code segment            =3D base 0x0, limit 0xfffff, type 0x1b
                        =3D DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        =3D interrupt enabled, resume, IOPL =3D 0
current process         =3D 12 (irq19: virtio_pci0)
trap number             =3D 12
panic: page fault
cpuid =3D 0
KDB: stack backtrace:
#0 0xffffffff80b24077 at kdb_backtrace+0x67
#1 0xffffffff80ad93e2 at vpanic+0x182
#2 0xffffffff80ad9253 at panic+0x43
#3 0xffffffff80fa0d31 at trap_fatal+0x351
#4 0xffffffff80fa0f23 at trap_pfault+0x1e3
#5 0xffffffff80fa04cc at trap+0x26c
#6 0xffffffff80f84141 at calltrap+0x8
#7 0xffffffff80ad35a6 at _rm_rlock+0x3c6
#8 0xffffffff80beb6d9 at vlan_input+0xb9
#9 0xffffffff80be2a65 at ether_demux+0x95
#10 0xffffffff80be3752 at ether_nh_input+0x322
#11 0xffffffff80bfa095 at netisr_dispatch_src+0xa5
#12 0xffffffff80be2d76 at ether_input+0x26
#13 0xffffffff8091ea8c at vtnet_rxq_eof+0x84c
#14 0xffffffff8091f643 at vtnet_rx_vq_intr+0x93
#15 0xffffffff8091b4d0 at vtpci_legacy_intr+0xb0
#16 0xffffffff80a9340f at intr_event_execute_handlers+0x20f
#17 0xffffffff80a93676 at ithread_loop+0xc6

There is another bug #198580 similar to mine, but it's in 9.2-STABLE so I p=
ost
a new one.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-220980-8>