Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 31 Aug 2000 18:12:21 -0600
From:      "Kenneth D. Merry" <ken@kdm.org>
To:        Brian Somers <brian@Awfulhak.org>
Cc:        Ivan Khilko <ivan@dvl.udnt.donetsk.ua>, freebsd-isp@FreeBSD.ORG
Subject:   Re: da0?
Message-ID:  <20000831181221.A57539@panzer.kdm.org>
In-Reply-To: <200009010002.e8102Z707253@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Fri, Sep 01, 2000 at 01:02:35AM %2B0100
References:  <ken@kdm.org> <200009010002.e8102Z707253@hak.lan.Awfulhak.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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?
> > 
> > You've probably got a cabling or termination problem.
> 
> 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...

What do you mean the "first resets"?

If you're seeing timed out in datain phase messages, you've likely got a
cabling or termination problem as well.

If it is another sort of timeout message, it's hard to say what that means
without seeing it.

> 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....).

I'm sure Justin will want to hear about it if going back to an older kernel
fixes your problem.

Ken
-- 
Kenneth Merry
ken@kdm.org


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?20000831181221.A57539>