Date: Mon, 29 Jun 2009 18:50:10 +0400 From: Kamigishi Rei <spambox@haruhiism.net> To: Lawrence Stewart <lstewart@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: r194546 amd64: kernel panic in tcp_sack.c Message-ID: <4A48D4A2.8010207@haruhiism.net> In-Reply-To: <4A48CE02.5000200@freebsd.org> References: <4A45ABB1.7040506@haruhiism.net> <4A48CE02.5000200@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Lawrence Stewart wrote: > I'm not intimately familiar with our SACK implementation, and these > things are often extremely painful to track down. First step: is the > panic reproducible? So far I couldn't reproduce it, but I think the fact that I couldn't reproduce it has something to do with frequent reboots due to buildworld/buildkernel lately because of other problems. > How did you try to get it to save the core? A dump would be very > useful to have around. Since I'm not much of an expert in the kernel debugger, I tried to let it continue with the panic, i.e. typed 'continue' which produced a fatal trap 12 right after "Dumping XXXX MB: (~3 values were here)". -- Kamigishi Rei KREI-RIPE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A48D4A2.8010207>