Date: Sun, 3 Sep 2000 12:17:36 +0300 (EEST) From: Ivan Khilko <ivan@ins.dn.ua> To: Brian Somers <brian@Awfulhak.org> Cc: "Kenneth D. Merry" <ken@kdm.org>, freebsd-isp@FreeBSD.ORG Subject: Re: da0? Message-ID: <Pine.BSF.4.10.10009031148440.46244-100000@anchor.udnt.donetsk.ua> In-Reply-To: <200009012101.e81L1x715440@hak.lan.Awfulhak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 1 Sep 2000, Brian Somers wrote: > > On Fri, Sep 01, 2000 at 01:02:35 +0100, Brian Somers wrote: > > > > On Wed, Aug 30, 2000 at 10:24:52 +0300, Ivan Khilko wrote: > > > > > > > > > > I read the archive of this mail-list. I see mail about problem on > > > > > SCSI disk. > > > > > I have same problem with my disk > > > > > > > > > > da0: <QUANTUM FIREBALL_TM2110S 300X> Fixed Direct Access SCSI-2 device > > > > > da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled > > > > > da0: 2014MB (4124736 512 byte sectors: 255H 63S/T 256C) > > > > > > > > > > kernel say > > > > > (da0:ahc0:0:0:0): SCB 0xc - timed out in datain phase, SEQADDR == 0x110 > > > > > (da0:ahc0:0:0:0): BDR message in message buffer > > > > > (da0:ahc0:0:0:0): no longer in timeout, status = 353 > > > > > Unexpected busfree. LASTPHASE == 0xa0 > > > > > SEQADDR == 0x153 > > > > > > > > > > and any disk operation disabled :( > > > > > > > > > > What you may tell about it? > > > > > > > > > > I've been seeing this recently too. In fact, with a kernel built > > > with the latest (1.48) aic7xxx.c, The first resets never seem to > > > happen and the machine just hangs... > > > > > I've now reverted to a kernel from last night and can get a login > > > again.... (albeit with lots of resets). I'm going to drop back to > > > 20000726 and see if that makes things sane again (I recently opened > > > the machine - around the same time that the problems began, so > > > there's a marginal chance that I damaged/moved the cabling or > > > something....) On this machine ~2 year work FreeBSD 2.2.8 without any errors. Same month ago I mast quickly install on it FreeBSD 3.3-RELEASE (I not have any other system on that time). From this moment problem exist. In 1-2 week system have this problem, and I mast it reboot... > > I'm sure Justin will want to hear about it if going back to an older kernel > > fixes your problem. > > Well, first let me apologise. My hang was due to kern/uipc_socket2.c > 1.63 (now fixed). Nothing to do with the scsi code. What I mast fix? I am novice user FreeBSD. What I mast read for to do it? Ivan. e-mail:ivan@ins.dn.ua To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" 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.4.10.10009031148440.46244-100000>