From owner-freebsd-stable Thu Apr 1 7:35: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from Homer.Web-Ex.com (homer.web-ex.com [209.54.66.254]) by hub.freebsd.org (Postfix) with ESMTP id 9125E14E75 for ; Thu, 1 Apr 1999 07:35:02 -0800 (PST) (envelope-from jim@web-ex.com) Received: from localhost (jim@localhost) by Homer.Web-Ex.com (8.9.3/8.9.3) with ESMTP id KAA06904 for ; Thu, 1 Apr 1999 10:34:46 -0500 (EST) X-Authentication-Warning: Homer.Web-Ex.com: jim owned process doing -bs Date: Thu, 1 Apr 1999 10:34:45 -0500 (EST) From: Jim Cassata To: stable@FreeBSD.ORG Subject: Re: SCSI problem this morning In-Reply-To: <199904011436.GAA04439@cwsys.cwsent.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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: 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: 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