On Fri, 29 Oct 2010, Mike Tancsa wrote:
Hi Mike,
Actually,
I dont think its an em bug as I can trigger this crash with the igb
nic. Perhaps these are 2 different issues being hit ? Anyways, I tried with
Yes what you have down there looks *sigh* hopefully like a different
issue thought it mbuf fiddling again but way further up the stack.
Could you please concentrate on only reproducing the
if<n>: discard frame w/o packet header
issue rather than breaking things left and right as well? ;-)
igb from HEAD in case there is some common code path between em and igb
(2.0.1 vs 2.0.4). But the issue is still there
In the netperf cluster its trivial to trigger this bug. Try this on camel and
leopard1. Note bear1 is still on the console debugger as well in case you
want to compare 2 different machines.
I shall when returning home tonight.
camel1# route add -inet6 2607:f3e0:0:80::290 2607:f3e0:9::107
add host 2607:f3e0:0:80::290: gateway 2607:f3e0:9::107
camel1#
Then start a ping on camel1. Then, with the ping is going, on leopard1 do an
ifconfig em0 down. A few seconds later, the panic below
just to confirm, it's camel1 that paniced in this test, right?
ip6_input() at ip6_input+0x28f
Could you look that up? feel free to reboot camel1. I would guess
it's the MCLGET() in the code with the "L2 bridge ..." comment on top?
Probably a m_clget() call if you look it up in gdb.
/bz
--
Bjoern A. Zeeb Welcome a new stage of life.
<ks> Going to jail sucks -- <bz> All my daemons like it!
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails.html
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-head
To unsubscribe, send any mail to "[email protected]"
