From owner-freebsd-stable Fri May 28 15:24:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from i.caniserv.com (i.caniserv.com [139.142.95.1]) by hub.freebsd.org (Postfix) with SMTP id B5E3A14DBB for ; Fri, 28 May 1999 15:24:11 -0700 (PDT) (envelope-from Darcy@ok-connect.com) Received: (qmail 4711 invoked from network); 28 May 1999 22:24:18 -0000 Received: from ccliii.caniserv.com (HELO dbitech) (darcyb@139.142.95.253) by 139.142.95.10 with SMTP; 28 May 1999 22:24:18 -0000 Message-Id: <3.0.32.19990528152604.023c79f0@mail.ok-connect.com> X-Sender: darcyb@mail.ok-connect.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Fri, 28 May 1999 15:26:05 -0700 To: freebsd-stable@FreeBSD.ORG From: Darcy Buskermolen Subject: Re: SMP and SCSI problems in 3.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since we are on the topic 3.2 scsi problems, here is my dmsg output on a system I can't mount the SCSI drives on ( yes this box worked as an NT box), I'm able to newfs them ect, but when I go to mount I get an error of mount: Device is busy. Intel L440GX+ Server board single Intel Petium III 450MHz (not over clocked) 2x 256MB ECC DIMMS 4 Seagate 18.2 GB Cheetah Hotswap SCA Hard drives. 1 6.4 GB IDE (boot device) 1 IDE cd rom master on secondary chain. Intel Astor case (if that helps since it has an adaptec Hotswap cage controller on it) 3.2 release with a CVSup as of 10PM-PDT last night. dmsg to follow: Waiting 15 seconds for SCSI devices to settle (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x49 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:1): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 Unexpected busfree. LASTPHASE == 0x40 SEQADDR == 0x87 Unexpected busfree. LASTPHASE == 0xa0 SEQADDR == 0x15c Unexpected busfree. LASTPHASE == 0xa0 SEQADDR == 0x15c (probe0:ahc1:0:6:4): parity error during Command phase. SEQADDR == 0x15d SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x86 SCSIRATE == 0x0 (probe0:ahc1:0:6:4): parity error during Data-In phase. SEQADDR == 0x87 SCSIRATE == 0x0 Unexpected busfree. LASTPHASE == 0x40 SEQADDR == 0x86 Unexpected busfree. LASTPHASE == 0xa0 SEQADDR == 0x15c Unexpected busfree. LASTPHASE == 0xa0 SEQADDR == 0x15c pass4 at ahc1 bus 0 target 6 lun 0 pass4: Fixed Processor SCSI-2 device pass4: 3.300MB/s transfers da0 at ahc1 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da3 at ahc1 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da3: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da2 at ahc1 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da2: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da1 at ahc1 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) At 04:08 PM 5/28/99 -0600, you wrote: >Mike Tancsa wrote... >> At 09:11 AM 5/28/99 -0600, Kenneth D. Merry wrote: >> >What kind of drives do you have in the system? Can you send dmesg output >> >from the machine? >> > >> >The timed out while idle messages mean that a read or write command from >> >the da driver timed out. Since the timeout is 60 seconds, this generally >> >indicates a drive problem of some sort. (could be bad firmware) >> > >> >There are some disks that are known to cause problems, so the dmesg might >> >help us determine the problem. >> > >> >> >> >> Perhaps its an unrelated problem, but on a machine that was ~ 3.2BETA, I got >> >> May 20 11:56:21 proxy /kernel: (sa0:ahc0:0:4:0): WRITE(06). CDB: a 0 0 80 0 0 >> May 20 11:56:21 proxy /kernel: (sa0:ahc0:0:4:0): ILLEGAL REQUEST asc:30,0 >> May 20 11:56:21 proxy /kernel: (sa0:ahc0:0:4:0): Incompatible medium installed >> May 20 17:27:18 proxy /kernel: (da0:ahc0:0:0:0): SCB 0x2 - timed out in >> message in phase, SEQADDR == 0x153 >> May 20 17:27:18 proxy /kernel: (da0:ahc0:0:0:0): Other SCB Timeout >> May 20 17:27:18 proxy /kernel: (da0:ahc0:0:0:0): SCB 0xf - timed out in >> message in phase, SEQADDR == 0x153 > >[ ... ] > >> when doing an rdump to it. >> >> I have since updated to 3.2STABLE as of today, and the same rdump does not >> induce those nasty messages... > >[ ... ] > >> sa0 at ahc0 bus 0 target 4 lun 0 >> sa0: Removable Sequential Access SCSI-2 device >> sa0: 10.000MB/s transfers (10.000MHz, offset 15) >> da0 at ahc0 bus 0 target 0 lun 0 >> da0: Fixed Direct Access SCSI-2 device >> da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing >> Enabled >> da0: 8703MB (17824700 512 byte sectors: 255H 63S/T 1109C) >> changing root device to da0s1a > >It looks like the tape drive was causing the timeouts. My guess is that >some of the fixes that Matt put in the tape driver may have fixed your >problem. > >This doesn't look like the same problem other folks were having. > >Ken >-- >Kenneth Merry >ken@plutotech.com > > >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