vkernel's tap/bridge use causing panics on real kernel.
Sepherosa Ziehau
sepherosa at gmail.com
Sat May 17 19:33:17 PDT 2008
On Sun, May 18, 2008 at 5:06 AM, Matthew Dillon
<dillon at apollo.backplane.com> wrote:
> Whoop, something done to the network stack has blown up bridge/tap
> operation.
>
> This will generate the 'mbuf ... was not tracked' messages, and
> eventually panics.
>
> kldload if_bridge.ko
> kldload if_tap.ko
> ifconfig bridge0 create
> ifconfig bridge0 addm nfe0
You got following message, even when vkernel is not started?
>
> bridge0: MAC address: ba:d1:a7:3b:5b:bc
> mbufuntrack: mbuf 0xd5b28400 was not tracked
> mbufuntrack: mbuf 0xd5b28500 was not tracked
> mbufuntrack: mbuf 0xd5b28600 was not tracked
> mbufuntrack: mbuf 0xd5b28700 was not tracked
> mbufuntrack: mbuf 0xd5b28a00 was not tracked
> tap0: MAC address: 00:bd:86:14:00:00
> mbufuntrack: mbuf 0xd5b28d00 was not tracked
> mbufuntrack: mbuf 0xd5b29000 was not tracked
> mbufuntrack: mbuf 0xd5b29200 was not tracked
> mbufuntrack: mbuf 0xd5b29500 was not tracked
> mbufuntrack: mbuf 0xd5b29700 was not tracked
> mbufuntrack: mbuf 0xd5b29a00 was not tracked
> mbufuntrack: mbuf 0xd5b29c00 was not tracked
> mbufuntrack: mbuf 0xd5b25100 was not tracked
> mbufuntrack: mbuf 0xd5b24f00 was not tracked
> mbufuntrack: mbuf 0xd5b23c00 was not tracked
> mbufuntrack: mbuf 0xd5b24200 was not tracked
> mbufuntrack: mbuf 0xd5b23e00 was not tracked
> mbufuntrack: mbuf 0xd5b32100 was not tracked
> mbufuntrack: mbuf 0xd5b32300 was not tracked
> mbufuntrack: mbuf 0xd5b31f00 was not tracked
> mbufuntrack: mbuf 0xd5b31b00 was not tracked
> mbufuntrack: mbuf 0xd5b3ed00 was not tracked
> mbufuntrack: mbuf 0xd5b23500 was not tracked
> mbufuntrack: mbuf 0xd5b22d00 was not tracked
> mbufuntrack: mbuf 0xd5b21100 was not tracked
> mbufuntrack: mbuf 0xd5b3eb00 was not tracked
> mbufuntrack: mbuf 0xd5b3e700 was not tracked
> mbufuntrack: mbuf 0xd5b3e400 was not tracked
> mbufuntrack: mbuf 0xd5b3e100 was not tracked
> mbufuntrack: mbuf 0xd5b3df00 was not tracked
> mbufuntrack: mbuf 0xd5b3dc00 was not tracked
> mbufuntrack: mbuf 0xd5b3da00 was not tracked
> mbufuntrack: mbuf 0xd5b3d600 was not tracked
> mbufuntrack: mbuf 0xd5b3d400 was not tracked
> mbufuntrack: mbuf 0xd5b3d200 was not tracked
> mbufuntrack: mbuf 0xd5b3c500 was not tracked
> mbufuntrack: mbuf 0xd5b3be00 was not tracked
> mbufuntrack: mbuf 0xc26a3200 was not tracked
> mbufuntrack: mbuf 0xd5b2a000 was not tracked
> mbufuntrack: mbuf 0xd5b2a200 was not tracked
> mbufuntrack: mbuf 0xd5b2a500 was not tracked
> mbufuntrack: mbuf 0xd5b2a700 was not tracked
> mbufuntrack: mbuf 0xd5b2aa00 was not tracked
> mbufuntrack: mbuf 0xd5b2ac00 was not tracked
> mbufuntrack: mbuf 0xd5b2af00 was not tracked
> mbufuntrack: mbuf 0xd5b2b100 was not tracked
> mbufuntrack: mbuf 0xd5b2b400 was not tracked
> mbufuntrack: mbuf 0xd5b2b600 was not tracked
> mbufuntrack: mbuf 0xd5b2b900 was not tracked
> panic: mbuftrack: mbuf 0xd5b29500 already being tracked
>
> mp_lock = 00000001; cpuid = 1
> Trace beginning at frame 0xd5adcb74
> panic(d5adcb98,cffd5d00,d5b29500,8,d5adcba4) at panic+0x14d
> panic(c0538da8,d5b29500,ff808000,d5b29500,d5adcbc4) at panic+0x14d
> mbuftrack(cffd1500,ff808000,cffd5d00,30,76d8) at mbuftrack+0x50
> m_gethdr(8,1,adcc08,d5adcc10,30) at m_gethdr+0x95
> sosend(d32a2a00,0,d5adcca0,0,0) at sosend+0x490
> soo_write(cff6ddd0,d5adcca0,d5e0dc08,0,cff6ddd0) at soo_write+0x4e
> kern_pwritev(3,d5adcca0,0,d5adccf0) at kern_pwritev+0xf6
> sys_write(d5adccf0,6,3d08,0,d281fb18) at sys_write+0x68
> syscall2(d5adcd40) at syscall2+0x25f
> Xint0x80_syscall() at Xint0x80_syscall+0x36
> Debugger("panic")
>
> CPU1 stopping CPUs: 0x00000001
> stopped
> Stopped at Debugger+0x34: movb $0,in_Debugger.4464
>
>
>
--
Live Free or Die
More information about the Commits
mailing list