Date: Wed, 5 Jan 2000 16:20:03 -0800 (PST) From: Bob Willcox <bob@luke.immure.com> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/10872: Panic in soreceive() due to NULL mbuf pointer Message-ID: <200001060020.QAA87602@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/10872; it has been noted by GNATS. From: Bob Willcox <bob@luke.immure.com> To: Terry Kennedy <terry@tmk.com> Cc: freebsd-gnats-submit@freebsd.org, bob@pmr.com Subject: Re: kern/10872: Panic in soreceive() due to NULL mbuf pointer Date: Wed, 5 Jan 2000 18:13:55 -0600 I have recently put together a test system running 3.4-stable (as of 1/4/2000) and am able to easily reproduce the sbdrop panic by running the little test script that I included in the bug report last summer. I run the script on 4 other systems, targetting the test system. Within a few minutes I consistently get the panic. I have my system built with debug symbols and it dutifully creates a crash dump. I haven't had much time to go any further than this with it right now, though (we are in the middle of renumbering our company's entire network and somehow I got stuck with planning and driving the effort:-(). Bob On Tue, Dec 21, 1999 at 02:42:29PM -0500, Terry Kennedy wrote: > > 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) -- Bob Willcox Don't tell me that worry doesn't do any good. bob@pmr.com I know better. The things I worry about don't Austin, TX happen. -- Watchman Examiner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001060020.QAA87602>