Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 01 Apr 1999 10:52:01 -0800
From:      Cy Schubert <cschuber@uumail.gov.bc.ca>
To:        Jim Cassata <jim@web-ex.com>
Cc:        stable@FreeBSD.ORG
Subject:   Re: SCSI problem this morning 
Message-ID:  <199904011852.KAA08875@passer.osg.gov.bc.ca>
In-Reply-To: Your message of "Thu, 01 Apr 1999 10:34:45 EST." <Pine.BSF.4.10.9904011029440.6893-100000@Homer.Web-Ex.com> 

next in thread | previous in thread | raw e-mail | index | archive | help
I used to have these symptoms too when all of my SCSI devices were 
attached to the 1542CF.  This problem only occurred under 
moderately heavy load.  I've been told that the 1542 was not 
designed for use in a multi-user/multi-process environment.

Now that all of my SCSI devices are attached to the 2940UW, except 
for a ZIP drive which is still attached to the 1542CF, all of the 
timeouts have gone away (once the BIOS problem had been fixed).

I used to have numerous timeouts under 2.x.x as well, execpt 2.x.x 
wasn't as verbose about it, and would crash more often, because of 
a swap slice on a SCSI disk, because of it.  I believe that in case 
of the 1542CF the timeouts were probably just as many as under 
2.x.x but 3.1 tends recover better from the error.


Regards,                       Phone:  (250)387-8437
Cy Schubert                      Fax:  (250)387-5766
Open Systems Group          Internet:  Cy.Schubert@uumail.gov.bc.ca
ITSD                                   Cy.Schubert@gems8.gov.bc.ca
Province of BC            
                      "e**(i*pi)+1=0"

In message <Pine.BSF.4.10.9904011029440.6893-100000@Homer.Web-Ex.com
>, Jim Cass
ata writes:
> 
> I call mine "scsi problem everyday." I dont know for sure if this is
> related.  I have 2 systems that went from 3.0 SNAPs to 3.0 RELEASE, and in
> doing so, introduced scsi bus timeouts on the Buslogic BT948 cards.  My
> initial response was to report it as a bug to the proper FreeBSD
> developers, who responded that they were aware of a problem with the code
> for that card and that I should grab a SNAP of at that time 2 weeks after
> 3.0 RELEASE.  The 2 boxes are now up to 3.1 STABLE with the same errors
> (6.4 Quantum Ultra SCSI drives)
> 
> (da0:bt0:0:0:0): CCB 0xf554cc00 - timed out
> (da0:bt0:0:0:0): CCB 0xf554cc00 - timed out
> bt0: No longer in timeout
> swap_pager: indefinite wait buffer: device: 0x20401, blkno: 1160, size:
> 4096
> (da0:bt0:0:0:0): CCB 0xf554d480 - timed out
> (da0:bt0:0:0:0): CCB 0xf554d480 - timed out
> bt0: No longer in timeout
> swap_pager: indefinite wait buffer: device: 0x20401, blkno: 1160, size:
> 4096
> (da0:bt0:0:0:0): CCB 0xf554d400 - timed out
> (da0:bt0:0:0:0): CCB 0xf554d400 - timed out
> bt0: No longer in timeout
> (da0:bt0:0:0:0): CCB 0xf554b5c0 - timed out
> (da0:bt0:0:0:0): CCB 0xf554b5c0 - timed out
> bt0: No longer in timeout
> (da0:bt0:0:0:0): CCB 0xf554d100 - timed out
> (da0:bt0:0:0:0): CCB 0xf554d100 - timed out
> bt0: No longer in timeout
> (da0:bt0:0:0:0): CCB 0xf554cd40 - timed out
> (da0:bt0:0:0:0): CCB 0xf554cd40 - timed out
> bt0: No longer in timeout
> (da0:bt0:0:0:0): CCB 0xf554ba00 - timed out
> (da0:bt0:0:0:0): CCB 0xf554ba00 - timed out
> bt0: No longer in timeout
> (da0:bt0:0:0:0): CCB 0xf554b440 - timed out
> (da0:bt0:0:0:0): CCB 0xf554b440 - timed out
> bt0: No longer in timeout
> 
> Jim Cassata
> 
> 516.421.6000
> jim@web-ex.com
> 
> Web Express
> 20 Broadhollow Road
> Suite 3011
> Melville, NY 11747
> 
> On Thu, 1 Apr 1999, Cy Schubert - ITSD Open Systems Group wrote:
> 
> > In message <37037565.D4E1F0DB@clearsail.net>, Jason McNew writes:
> > > This is a multi-part message in MIME format.
> > > --------------E591BA8549CC69E41981C0B0
> > > Content-Type: text/plain; charset=us-ascii
> > > Content-Transfer-Encoding: 7bit
> > > 
> > > I had errors this morning with a world and kernel built last night.  I
> > > was doing cd /usr/ports/x11/kde at the time.   I've attached my dmesg
> > > output. Any ideas?
> > [dmesg output deleted]
> > > ahc0: <Adaptec 2940 Ultra2 SCSI adapter> rev 0x00 int a irq 10 on pci0.9.
> 0
> > > ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs
> > [dmesg output deleted]
> > > da0 at ahc0 bus 0 target 0 lun 0
> > > da0: <SEAGATE ST39102LW 0004> Fixed Direct Access SCSI-2 device 
> > > da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing 
> Enab
> > > led
> > > da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C)
> > > (da0:ahc0:0:0:0): SCB 0xa - timed out in datain phase, SEQADDR == 0x86
> > > (da0:ahc0:0:0:0): BDR message in message buffer
> > > (da0:ahc0:0:0:0): SCB 0xa - timed out in datain phase, SEQADDR == 0x86
> > > (da0:ahc0:0:0:0): no longer in timeout, status = 34b
> > > ahc0: Issued Channel A Bus Reset. 5 SCBs aborted
> > > ahc0: Signaled a Target Abort
> > > (da0:ahc0:0:0:0): SCB 0xa - timed out in datain phase, SEQADDR == 0x2
> > > (da0:ahc0:0:0:0): SCB 10: Immediate reset.  Flags = 0x4040
> > > (da0:ahc0:0:0:0): no longer in timeout, status = 34b
> > > ahc0: Issued Channel A Bus Reset. 5 SCBs aborted
> > 
> > I had this problem when I replaced my old 1542CF with a 2940UW.  The 
> > previous week I had replaced my bios with a BIOS with a Y2K fix in it.  
> > Backing out of the Y2K bios fixed the problem.  (All this means is that 
> > I need to manually set the bios date sometime Jan 1 then it should work 
> > to 2099.  A small price to pay to get the 2940UW to work.)
> > 
> > 
> > Regards,                       Phone:  (250)387-8437
> > Cy Schubert                      Fax:  (250)387-5766
> > Open Systems Group          Internet:  Cy.Schubert@uumail.gov.bc.ca
> > ITSD                                   Cy.Schubert@gems8.gov.bc.ca
> > Province of BC
> > 
> > 
> > 
> > 
> > 
> > 
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-stable" in the body of the message
> > 
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199904011852.KAA08875>