From owner-freebsd-bugs Wed Jan 17 10:30:24 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id DCCB037B6C9 for ; Wed, 17 Jan 2001 10:30:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0HIU2D81853; Wed, 17 Jan 2001 10:30:02 -0800 (PST) (envelope-from gnats) Date: Wed, 17 Jan 2001 10:30:02 -0800 (PST) Message-Id: <200101171830.f0HIU2D81853@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Ronald F. Guilmette" Subject: Re: kern/24401: Advansys SCSI driver crashes random userland progs w/SIGPROF Reply-To: "Ronald F. Guilmette" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24401; it has been noted by GNATS. From: "Ronald F. Guilmette" To: "Justin T. Gibbs" Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/24401: Advansys SCSI driver crashes random userland progs w/SIGPROF Date: Wed, 17 Jan 2001 10:23:36 -0800 In message <200101171817.f0HIHOs01442@aslan.scsiguy.com>, you wrote: >>>Synopsis: Advansys SCSI driver crashes random userland progs w/SIGPROF > >In all likelyhood, this has nothing to do with the AdvanSys controller. >It smells like a faulty or overclocked CPU... The CPU is definitely *not* overclocked. It an AMD K6-II/450 running at its rated speed in a well-cooled system. >... or faulty RAM. Performing disk >I/O is quite memory intensive (lots of DMA active), so RAM is where I >would start looking first. OK, so why does it fail consistantly with the Advansys controller, and yet it NEVER seems to fail with an Adaptec controller? I think that your theory about it being bad RAM is clearly incorrect, but I'm willing to try additional tests to rule out this possibility entirely. What would you suggest? I have memtest-86 here. If I run that for several hours and it shows now errors, then will you be convinced that there's a problem with the Advansys controller driver? P.S. I would like to get to the bottom of this as much as anyone, and I'm willing to do anything and everything on my end to aid the FreeBSD maintainers to isolate and then solve this problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message