Date: Sun, 20 Dec 1998 20:02:32 -0700 (MST) From: "Kenneth D. Merry" <ken@plutotech.com> To: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai) Cc: skynyrd@opus.cts.cwu.edu, freebsd-scsi@FreeBSD.ORG Subject: Re: Problem with SCSI-bus and high diskaccess? Message-ID: <199812210302.UAA94802@panzer.plutotech.com> In-Reply-To: <XFMail.981220221957.asmodai@wxs.nl> from Jeroen Ruigrok/Asmodai at "Dec 20, 98 10:19:57 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Jeroen Ruigrok/Asmodai wrote... > 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. Well, if you were swapping at the time, it would certainly cause problems if your disk stopped responding. > 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 =) Good idea. If you've got a second machine, it might be worthwhile to setup a serial console to catch any error messages that are printed out. I find it quite helpful with one of my machines at home. (I was having NMI problems, generally while in X, but I couldn't figure out exactly why until I put a serial console on the box. It turned out that although I was within the specs as far as the number of memory chips per SIMM, I was probably > > 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/ Bummer. You might want to talk to Quantum about it...more below. > ahc0: <Adaptec 2940 Ultra SCSI adapter> 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: <QUANTUM FIREBALL ST6.4S 0F0C> 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) I know there is later firmware than that for the Fireball ST. I believe the drives we have at work that "work" have the 0F0J firmware revision. (the machine with the drives in question is down at the moment, so I can't check to be sure) Try calling Quantum Tech support and see if you can get them to give you a newer firmware revision. > da0 at ahc0 bus 0 target 0 lun 0 > da0: <QUANTUM FIREBALL_TM3200S 300X> 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) Dunno about this one. I'm not sure what sort of Fireball it is. > > 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 Well, don't worry about the Rev E/Rev B problem, Justin worked around it last summer, so what you're running is certainly new enough. > > 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... Then you've probably never pushed them very hard. I'm personally curious to see whether their newer drives (e.g. Atlas III, Atlas IV, Atlas 10K) have the same sorts of problems that their older drives did. I'm certainly not willing, however, to spend any money to find out. :) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812210302.UAA94802>