From owner-freebsd-bugs Tue May 11 10:30: 5 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 2CF4815001 for ; Tue, 11 May 1999 10:30:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id KAA61223; Tue, 11 May 1999 10:30:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Tue, 11 May 1999 10:30:02 -0700 (PDT) Message-Id: <199905111730.KAA61223@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Peter Wemm Subject: kern/10872: Panic in sorecieve() Reply-To: Peter Wemm 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: Peter Wemm To: Pierre Beyssac Cc: freebsd-bugs@freebsd.org, bob@pmr.com, FreeBSD-gnats-submit@freebsd.org Subject: kern/10872: Panic in sorecieve() Date: Wed, 12 May 1999 01:28:42 +0800 Pierre Beyssac wrote: > I was looking into PR kern/10872, hoping to find an easily fixable > occurence of NULL mbuf pointer. But it doesn't seem to be. I just looked at the PR. He's running: ahc0: rev 0x00 int a irq 12 on pci0.10.0 ahc0: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs ncr0: rev 0x01 int a irq 11 on pci0.12.0 ncr1: rev 0x03 int a irq 9 on pci0.13.0 It should be noted that freefall had a severe case of problems like this that all but disappeared when the ncr cards were swapped for an ahc2940U2W. Quite how this should make such a dramatic difference is a bit of a mystery. We were seeing really strange things like a bit of the kernel stack being partly trashed and messing up some local variables.. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message