From owner-freebsd-bugs Tue Dec 21 12: 0: 3 1999 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 ABEB1154E2 for ; Tue, 21 Dec 1999 12:00:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id MAA50744; Tue, 21 Dec 1999 12:00:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Tue, 21 Dec 1999 12:00:01 -0800 (PST) Message-Id: <199912212000.MAA50744@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Terry Kennedy Subject: Re: kern/10872: Panic in soreceive() due to NULL mbuf pointer Reply-To: Terry Kennedy 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: Terry Kennedy To: freebsd-gnats-submit@freebsd.org, bob@pmr.com Cc: Subject: Re: kern/10872: Panic in soreceive() due to NULL mbuf pointer Date: Tue, 21 Dec 1999 14:42:29 -0500 (EST) > What would be interesting to find out is if you can still reproduce > it on -CURRENT and 3.3-STABLE. This time, I would ask for you to try > printing out the value of the mmbfree mbuf pointer as well as the mclfree > mcluster pointer from the debugger. Also, if you ever end up crashing > somewhere else (besides for in soreceive or sbdrop), e.g. somewhere > directly from the if_fxp code, or if something has significantly changed > from the first two traces that you provided, if you could get a new trace > and post that along as well. I have a news server (Diablo) that moves about .3TB/day. After being down (due to an unrelated problem) for about 4 hours, I am getting these panics pretty much continuously (about 1 every 5 minutes) now. The FreeBSD version is 3.3-RELEASE from the WC CDROM. I'm using an NCR 875 controller and a DEC 21140 Ethernet chip on a full- duplex 100Mbit segment. NMBCLUSTERS is 32768 due to an earlier problem with running out of mbufs with maxusers=256. Most of the panics are the sbdrop panic, but some of them are a trap 12 in tulip_rx_intr(). Unfortunately, my kernel wasn't config'd with -g. I'm building a new one now and will report back with any additional info I come up with. If any of the developers would find access to the box to be helpful and can respond rapidly, I'd be glad to give them access. But once it gets caught up, it will likely stop crashing. Terry Kennedy http://www.tmk.com terry@tmk.com Jersey City, NJ USA +1 201 451 4554 (voice) +1 201 451 0900 (FAX) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message