From owner-freebsd-scsi Sun Dec 20 13:14:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21907 for freebsd-scsi-outgoing; Sun, 20 Dec 1998 13:14:08 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21866 for ; Sun, 20 Dec 1998 13:13:47 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.56.171]) by smtp01.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA69C0; Sun, 20 Dec 1998 22:13:38 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 20 Dec 1998 22:19:57 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Chris Timmons Subject: Re: Problem with SCSI-bus and high diskaccess? Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 20-Dec-98 Chris Timmons wrote: > > [moved to -scsi] > > I am assuming that you posted to -current because you just cvsupped the > latest 3.0-current bits and are running that. Else freebsd-scsi would be > a good list for this kind of problem (be sure to say what version of > FreeBSD you are running.) Sorry, my bad... I did it because I thought I might be more related to current than scsi =\ Especially regarding the following pager messages, which might be in effect of not being able to write to the HD after the problem occured. I did some heavy disk access later on again and now my X completely froze, moused as well and after some seconds the whole thing rebooted spontaneously. No logs. As I said, the memory is fine, I never got SIG 11's, plus it has been tested recently. I reseated all the crap that can be reseated =) > Although I haven't seen this sort of thing with a fireball, it reeks of > quantum firmware. I have had similar problems with atlas-I and atlas-II > drives. So you will want to check your firmware revision and see if there > is something newer out at ftp.quantum.com (upgrading firmware is a fun way > to waste a day.) You might try www.dejanews.com and search for your drive > name and firmware revision. Chances are somebody else has already seen > and documented a similar problem if it is indeed the drives. OK, I am not dirty of updating firmware... Didn't even know HD's could be updated ;) And offcourse... Fireballs don't have firmware updates =\ ftp://ftp.quantum.com/Disk_Firmware/ ahc0: rev 0x00 int a irq 11 on pci0.17.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da1: 6180MB (12657717 512 byte sectors: 255H 63S/T 787C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da0: 3067MB (6281856 512 byte sectors: 255H 63S/T 391C) > There is also a slight possibility that you are using an old enough > version of FreeBSD and perhaps an integrated aha-2940UW on your mb (or > perhaps the dreaded rev e(?) of the pci card. In that case, Justin > committed fixes to the drivers months ago. Update your system. Sorry, I forgot to post my version: [chronias] asmodai $ uname -a FreeBSD chronias.ninth-circle.org 3.0-CURRENT FreeBSD 3.0-CURRENT #20: Wed Dec 16 07:21:00 CET 1998 asmodai@chronias.ninth-circle.org:/work/cvs/src/sys/compile/CHRONIAS i386 And no, it ain't an integrated AHA... It's a PCI card, from the original kit, not the OEM version. I think the BIOS version is 1.2x just don't know what the x was, I thought 6 or 7 > I find that IBM and Seagate drives work very well and come with firmware > that works right the first time. Your mileage may vary :) Never had problems with Quantums before... --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message