From owner-freebsd-current Fri Oct 11 11:09:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA15093 for current-outgoing; Fri, 11 Oct 1996 11:09:49 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA15087; Fri, 11 Oct 1996 11:09:46 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id LAA29261; Fri, 11 Oct 1996 11:09:37 -0700 (PDT) Message-Id: <199610111809.LAA29261@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Paul Traina cc: dyson@FreeBSD.org, current@FreeBSD.org Subject: Re: recent kernel panics in the vm system In-reply-to: Your message of "Fri, 11 Oct 1996 10:55:50 PDT." <199610111755.KAA01433@base.jnx.com> From: David Greenman Reply-To: dg@root.com Date: Fri, 11 Oct 1996 11:09:37 -0700 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >I found at least two bugs in my recent tcp/socket changes, but those don't >seem to be the cause of my recent crashes. I wasn't aware there was any >unstability with the PCB hashing, I'll look there next, thanks. > >Paul > > From: John Dyson > Subject: Re: recent kernel panics in the vm system > > > > John, > > Have you received reports of kernel instability in -current as of Oct 10th? > > I'm seeing a number of panics, and they all started in the last 2 days. > > > The only problem that is severe that I know of (right now -- might have > forgotten though) is the PCB hashing thing. I would love to see a > traceback so we can narrow things down. The VM code itself should be > fairly stable, but a bit slow for low level benchmarks. John is a bit confused, I think. There is nothing wrong with the PCB hashing as far as I'm aware. The problem is with the SYN-flood drop code dereferencing a NULL. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project