Date: Sun, 30 Mar 2008 23:47:59 -0700 (PDT) From: Nick Sayer <nsayer@kfu.com> To: FreeBSD-gnats-submit@FreeBSD.org Subject: kern/122283: Panic in ip_output related to IPv6 routes Message-ID: <200803310647.m2V6lxIp012832@quack.kfu.com> Resent-Message-ID: <200803310650.m2V6o1IR093200@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 122283 >Category: kern >Synopsis: Panic in ip_output related to IPv6 routes >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Mar 31 06:50:01 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Nick Sayer >Release: FreeBSD 7.0-RELEASE i386 >Organization: self >Environment: System: FreeBSD quack.kfu.com 7.0-RELEASE FreeBSD 7.0-RELEASE #2: Sun Feb 24 11:38:42 PST 2008 root@quack.kfu.com:/usr/obj/usr/src/sys/QUACK i386 The machine is a Core 2 Duo based desktop machine (configured for SMP). It has a single interface connected to a DSL modem. It has the stf nterface configured as its means of IPv6 connectivity. There is a non-trivial amount of IPv6 traffic hitting this machine. >Description: About every 7-10 days, the machine panics. Almost always the panic is in line 169 of ip_output.c, although a recent example had the panic in line 235. In every case, *ro was an IPv6 route, and ro->ro_rt->rt_flags was a crap address. I haven't really tried to tackle this one by myself yet. I'm instead hoping that someone else has already done the heavy lifting. >How-To-Repeat: Just wait a week. >Fix: Unknown. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200803310647.m2V6lxIp012832>