From owner-freebsd-current Thu Oct 8 08:22:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15138 for freebsd-current-outgoing; Thu, 8 Oct 1998 08:22:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uop.cs.uop.edu (uop.cs.uop.edu [138.9.200.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA15037 for ; Thu, 8 Oct 1998 08:22:15 -0700 (PDT) (envelope-from bford@uop.cs.uop.edu) Received: from heather (user209.pop2.cwia.com [209.142.32.209]) by uop.cs.uop.edu (8.8.8/8.8.8) with SMTP id IAA12236 for ; Thu, 8 Oct 1998 08:22:06 -0700 (PDT) Message-ID: <000901bdf2cf$68be5ca0$0100a8c0@heather.my.domain> From: "Bret Ford" To: Subject: Seagate drive lockup Date: Thu, 8 Oct 1998 08:22:03 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, I'm using a recent (around Sep 29) -current world with a kernel compiled fresh today. I'm having some "lock-up" problems with my Seagate 9gb drive. This occurs whenever the disk gets used with some intensity (eg. rm -fr obj or most 'cvsup's). I will get a couple iterations of kernel messages like these: Oct 8 07:51:31 plover /kernel.test: (da1:ahc0:0:3:0): SCB 0xc - timed out in dataout phase, SCSISIGI == 0x4 Oct 8 07:51:31 plover /kernel.test: SEQADDR == 0x10d Oct 8 07:51:31 plover /kernel.test: SSTAT1 == 0x2 Oct 8 07:51:31 plover /kernel.test: (da1:ahc0:0:3:0): BDR message in message buffer Oct 8 07:51:33 plover /kernel.test: (da1:ahc0:0:3:0): SCB 0x9 - timed out in dataout phase, SCSISIGI == 0x14 Oct 8 07:51:33 plover /kernel.test: SEQADDR == 0x10e Oct 8 07:51:33 plover /kernel.test: SSTAT1 == 0x2 Oct 8 07:51:33 plover /kernel.test: (da1:ahc0:0:3:0): no longer in timeout, status = 34b Oct 8 07:51:33 plover /kernel.test: ahc0: Issued Channel A Bus Reset. 47 SCBs aborted ...and then my ^C or ^Z command will finally take. It usually takes a minute or more to get out of this lock-up condition. Below is a dmesg description of my SCSI hardware. Hope this is helpful. Bret Ford ahc0: at 0x4c00-0x4cff irq 15 on eisa0 slot 4 ahc0: aic7770 >= Rev E, Wide Channel A, SCSI Id=7, 4/255 SCBs aha0 at 0x130-0x133 irq 11 drq 7 on isa aha0: AHA-1542C FW Rev. 0.1 (ID=44) SCSI Host Adapter, SCSI ID 7, 17 CCBs da1 at ahc0 bus 0 target 3 lun 0 da1: Fixed Direct Access SCSI2 device da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da1: 8347MB (17096357 512 byte sectors: 64H 32S/T 8347C) da0 at aha0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 3.333MB/s transfers (3.333MHz, offset 8) da0: 496MB (1015812 512 byte sectors: 64H 32S/T 496C) cd0 at aha0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 3.300MB/s transfers cd0: cd present [191673 x 2048 byte records] da2 at aha0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI2 device da2: 3.300MB/s transfers da2: 1910MB (3912172 512 byte sectors: 64H 32S/T 1910C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message