Date: Thu, 25 Nov 2010 19:50:11 +0300 From: Ivan Panachev <ivan.panachev@gmail.com> To: FreeBSD-gnats-submit@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: kern/133786: ip_input might cause kernel panic Message-ID: <AANLkTimzeE=4GsaHS9oRtUQnGSyVM1QsOQ9fY_xqqpG5@mail.gmail.com> In-Reply-To: <200904161740.n3GHe7jD054031@freefall.freebsd.org> References: <200904161733.n3GHXnRd013108@www.freebsd.org> <200904161740.n3GHe7jD054031@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Sorry for such a late answer. In fact this box didn't stop panicking after my workaround, just panicked less than before. I've spent a lot of time debugging the issue, tried the same hardware, etc. Finally I've become convinced that it's a bad hardware of this specific box= . I suppose this ticket should be closed. On Thu, Apr 16, 2009 at 9:40 PM, <FreeBSD-gnats-submit@freebsd.org> wrote: > Thank you very much for your problem report. > It has the internal identification `kern/133786'. > The individual assigned to look at your > report is: freebsd-bugs. > > You can access the state of your problem report at any time > via this link: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D133786 > >>Category: =A0 =A0 =A0 kern >>Responsible: =A0 =A0freebsd-bugs >>Synopsis: =A0 =A0 =A0 ip_input might cause kernel panic >>Arrival-Date: =A0 Thu Apr 16 17:40:07 UTC 2009 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimzeE=4GsaHS9oRtUQnGSyVM1QsOQ9fY_xqqpG5>