From owner-freebsd-bugs Thu Jan 6 22:30: 4 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 90C3714F72 for ; Thu, 6 Jan 2000 22:30:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id WAA79475; Thu, 6 Jan 2000 22:30:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Thu, 6 Jan 2000 22:30:02 -0800 (PST) Message-Id: <200001070630.WAA79475@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Bosko Milekic Subject: Re: kern/10872: Panic in soreceive() due to NULL mbuf pointer Reply-To: Bosko Milekic Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/10872; it has been noted by GNATS. From: Bosko Milekic To: terry@tmk.com, freebsd-gnats-submit@freebsd.org Cc: Subject: Re: kern/10872: Panic in soreceive() due to NULL mbuf pointer Date: Fri, 7 Jan 2000 01:20:29 -0500 (EST) > Most of the panics are the sbdrop panic, but some of them are a trap 12 > in tulip_rx_intr(). Terry, Do you think you could provide a trace of particularily the crash that you're getting in tulip_rx_intr() ? This is the first time that I hear of the Tulip cards puking out in conjunction with the ncr and quite honestly, I'm really desperate trying to figure out what could cause the inconsistency between sb_cc and sb_mb. Perhaps this could shed some light on the issue as it would eliminate the sole blame on the fxp driver. -- Bosko Milekic Email: bmilekic@dsuper.net WWW: http://pages.infinit.net/bmilekic/ -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message