From owner-freebsd-stable Fri May 28 15: 8:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D1EA14E53 for ; Fri, 28 May 1999 15:08:52 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id QAA28095; Fri, 28 May 1999 16:08:24 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905282208.QAA28095@panzer.plutotech.com> Subject: Re: SMP and SCSI problems in 3.2 In-Reply-To: <3.0.5.32.19990528173920.01508100@staff.sentex.ca> from Mike Tancsa at "May 28, 1999 05:39:20 pm" To: mike@sentex.net (Mike Tancsa) Date: Fri, 28 May 1999 16:08:24 -0600 (MDT) Cc: marcus@miami.edu, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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