Date: Sun, 20 Dec 1998 12:34:22 -0800 (PST) From: Chris Timmons <skynyrd@opus.cts.cwu.edu> To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Problem with SCSI-bus and high diskaccess? Message-ID: <Pine.BSF.3.96.981220122334.9871A-100000@opus.cts.cwu.edu> In-Reply-To: <XFMail.981220193725.asmodai@wxs.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
[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.) 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. 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. I find that IBM and Seagate drives work very well and come with firmware that works right the first time. Your mileage may vary :) -Chris On Sun, 20 Dec 1998, Jeroen Ruigrok/Asmodai wrote: > Hi, > > I just want some thoughts on this: > > In the last 24 hours my workstation is been going nuts, whereas it has been > running along nicely for weeks before. > > The things that kept me bugging today were these happy messages: > > Dec 20 10:51:14 chronias /kernel: Unexpected busfree. LASTPHASE == 0xa0 > Dec 20 10:51:15 chronias /kernel: SEQADDR == 0x157 > Dec 20 10:51:15 chronias /kernel: (da1:ahc0:0:1:0): SCB 0x5 - timed out while > idle, LASTPHASE == 0x1, SEQADDR == 0xc > Dec 20 10:51:15 chronias /kernel: (da1:ahc0:0:1:0): Queuing a BDR SCB > Dec 20 10:51:15 chronias /kernel: (da1:ahc0:0:1:0): Bus Device Reset Message Sent > Dec 20 10:51:15 chronias /kernel: (da1:ahc0:0:1:0): no longer in timeout, status > = 353 > > After which page and swap process were running wild. > > The weird thing is, these HD's (two SCSI Quantum Fireballs) have been checked, the > HA (AHA 2940UW) is likewise in good shape and the memory chips have been tested as > well... The mainboard is also in good shape and is cooled by a few fans (3) which > all work, including the one on the CPU. > > The circumstances when this happened was when I did a locate.updatedb at the same > time as downloading a PDF file to the HD, and then I opened a mailbox at which > time the whole time went haywire... > > Unfortunately I wasn't able to write down the pager messages since they went by > with warpspeed 9 and they weren't logged in /var/log/messages =\ > > Does anybody have any ideas what to check to narrow down the problem? > > --- > Jeroen Ruigrok van der Werven Life is the only Pain > asmodai(at)wxs.nl we endeavour... > Network/Security Specialist <http://home.wxs.nl/~asmodai>; > BSD & picoBSD: The Power to Serve <http://www.freebsd.org>; > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > 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?Pine.BSF.3.96.981220122334.9871A-100000>