>>>>> Do you know how this panic is triggered ? Are you able to >>>>> create it on demand ? >>>> >>>> no i do not. bring server up and it'll happen in half an hour. >>>> and the server was happy for two months. so i am thinking hardware. >>> >>> Perhaps. The reason I ask is that I had a box go down last night with >>> the same set of errors. The box has a number of ipv6 routes, but its >>> next hop was down and the problems started soon after. So I wonder if >>> it has something to do with that. Do you have ipv6 on this box and >>> are all the next hop addresses correct / reachable ? >>> >>> Oct 22 02:06:02 i4 kernel: em1: discard frame w/o packet header >>> Oct 22 02:06:10 i4 kernel: em2: discard frame w/o packet header >>> Oct 22 02:06:21 i4 kernel: em1: discard frame w/o packet header >> >>it was co-incident with a border router being taken down for new router >>install. that router was the v6 exit the servers was using. i have now >>pointed default6 to a different exit. the server seems happy. > > > Are you servers still up ? I guess the question now is how to > trigger this problem on demand. Perhaps lots of inbound ipv6 traffic > with a bad next hop out ? How recent are you sources ? The kernel > said Oct 21st. Were the sources from then too ?
yes, kernel and world from 21 oct chris had an idea on retrigger, install a static for a small dest that points to a hole. send a packet to the small dest. randy _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
