Date: Fri, 22 Oct 2010 13:27:36 -0700 From: Joel Jaeggli <joelja@bogus.com> To: Randy Bush <randy@psg.com> Cc: Chris Morrow <morrowc@ops-netman.net>, stable <stable@freebsd.org> Subject: Re: repeating crashes with 8.1 Message-ID: <4CC1F3B8.3010302@bogus.com> In-Reply-To: <m2y69q9e38.wl%randy@psg.com> References: <m2zku7cqt5.wl%randy@psg.com> <m2y69rcqjc.wl%randy@psg.com> <201010221416.o9MEGSa0094817@lava.sentex.ca> <m2tykeb9ac.wl%randy@psg.com> <201010221425.o9MEPcWC094867@lava.sentex.ca> <m2k4lab6nh.wl%randy@psg.com> <201010221848.o9MIm7WF096197@lava.sentex.ca> <m2y69q9e38.wl%randy@psg.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ok I'll try testing that on some box I can reach with both hands. fyi nagasaki is: [root@nagasaki ~]# uname -a FreeBSD nagasaki.bogus.com 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #13: Sun May 30 22:19:23 UTC 2010 root@nagasaki.bogus.com:/usr/obj/usr/src/sys/GENERIC i386 [root@nagasaki ~]# On 10/22/10 1:17 PM, Randy Bush wrote: >>>>>> 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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CC1F3B8.3010302>