From owner-freebsd-current Thu Oct 10 14:13:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA15890 for current-outgoing; Thu, 10 Oct 1996 14:13:08 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA15868; Thu, 10 Oct 1996 14:12:56 -0700 (PDT) Received: from alpha.Xerox.COM by mail.crl.com with SMTP id AA24434 (5.65c/IDA-1.5); Thu, 10 Oct 1996 14:13:16 -0700 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15993(3)>; Thu, 10 Oct 1996 14:09:40 PDT Received: by crevenia.parc.xerox.com id <177476>; Thu, 10 Oct 1996 14:09:32 -0700 From: Bill Fenner To: current@freebsd.org, hackers@freebsd.org, karl@mcs.net Subject: Re: Crash in -current (from the current SNAP) Message-Id: <96Oct10.140932pdt.177476@crevenia.parc.xerox.com> Date: Thu, 10 Oct 1996 14:09:31 PDT Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>> (*inetsw[ip_protox[ip->ip_p]].pr_input)(m, hlen); >What's going on here? Either ip_protox[ip->ip_p] is out of range (should be 1..7 or 8 depending on if what options you have in your kernel), or inetsw[ip_protox[ip->ip_p]].pr_input is. >Given that it is a timeout call that is generating this, why do I think >this has something to do with the anti-syn patches? Nope, this is a software interrupt causing IP to service its input queue. Bill