From owner-freebsd-stable@FreeBSD.ORG Sun Oct 12 01:42:45 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C746816A4B3 for ; Sun, 12 Oct 2003 01:42:45 -0700 (PDT) Received: from grummit.biaix.org (86.Red-213-97-212.pooles.rima-tde.net [213.97.212.86]) by mx1.FreeBSD.org (Postfix) with SMTP id 1C11C43F85 for ; Sun, 12 Oct 2003 01:42:44 -0700 (PDT) (envelope-from joan@grummit.biaix.org) Received: (qmail 70132 invoked by uid 1000); 12 Oct 2003 08:37:26 -0000 Date: Sun, 12 Oct 2003 10:37:26 +0200 From: Joan Picanyol To: freebsd-stable@freebsd.org Message-ID: <20031012083726.GA69586@grummit.biaix.org> Mail-Followup-To: freebsd-stable@freebsd.org References: <20031010103339.GA1093@grummit.biaix.org> <20031010201612.O70199@carver.gumbysoft.com> <20031011152824.GA1175@grummit.biaix.org> <20031012033759.GA2319@doom.homeunix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031012033759.GA2319@doom.homeunix.org> User-Agent: Mutt/1.4.1i Subject: Re: help needed debugging SCSI bus problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Oct 2003 08:42:45 -0000 * Igor Pokrovsky [20031012 05:40]: > On Sat, Oct 11, 2003 at 05:28:24PM +0200, Joan Picanyol wrote: > > > This isn't that useful, unfortunately :( > > How do I setup my system to save the console messages? Since it > > freezes absolutely I have no way of accurate error reporting. > You can always edit your /etc/syslog.conf to redirect console messages > wherever you want. Also don't forget about /var/log/messages. Anything written to disk get's lost (I have to press the reset button). In fact I don't believe I could write anything to disk, since it looks like the SCSI bus freezes. tks -- pica From owner-freebsd-stable@FreeBSD.ORG Sun Oct 12 03:15:41 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E11316A4B3 for ; Sun, 12 Oct 2003 03:15:41 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id AEF3D43F85 for ; Sun, 12 Oct 2003 03:15:39 -0700 (PDT) (envelope-from shreds-of-sanity@gmx.net) Received: (qmail 14008 invoked by uid 65534); 12 Oct 2003 10:15:38 -0000 Received: from pD9E55881.dip.t-dialin.net (EHLO thor) (217.229.88.129) by mail.gmx.net (mp016) with SMTP; 12 Oct 2003 12:15:38 +0200 X-Authenticated: #3934535 From: shreds-of-sanity@gmx.net To: freebsd-stable@freebsd.org In-Reply-To: <20031010103339.GA1093@grummit.biaix.org> References: <20031010103339.GA1093@grummit.biaix.org> X-Mailer: n/a Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20031012101539.AEF3D43F85@mx1.FreeBSD.org> Date: Sun, 12 Oct 2003 03:15:39 -0700 (PDT) Subject: Re: help needed debugging SCSI bus problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Oct 2003 10:15:41 -0000 hi, i'm using 4.8-release[1] and experienced a similar problem last week using the same scsi-adapter[2] and the same drive[3]: my system froze during boottime just like yours. it stopped after detecting the dnes-309170w. i've successfully tested the controller, the cable and the termination with another scsi-drive[4]. desperate as i was i decided to low-level format the "broken" drive via the controllers buildin scsi-tools ... the drive got detected afterwards and is up and running since then. - worldi [1] %uname -srm FreeBSD 4.8-RELEASE-p13 i386 [2] ahc0: port 0xa800-0xa8ff mem 0xed001000-0xed001fff irq 11 at device 9.0 on pci0 [3] da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 30, 16bit), Tagged Queueing Enabled da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) [4] da1 at ahc0 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: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) -- Look what has become of your world... > [not subscribed to -scsi, if OT for stable please keep me in > Mail-Followup-To:] > > Hi, > > I can hang my system at will reading from my SCSI CD-RW. My hardware > is(excerpt from dmesg): > > ahc0: port 0x1000-0x10ff mem > 0xd0020000-0xd00 > 20fff irq 11 at device 14.0 on pci0 > aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs > [...] > cd0 at ahc0 bus 0 target 2 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 20.000MB/s transfers (20.000MHz, offset 7) > [...] > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-3 device > da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged > Queueing Enabled da0: 19001MB (38914049 512 byte sectors: 255H 63S/T > 2422C)[...] > da1 at ahc0 bus 0 target 6 lun 0 > da1: Fixed Direct Access SCSI-3 device > da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged > Queueing Enabled da1: 8748MB (17916240 512 byte sectors: 255H 63S/T > 1115C) > > I can't paste the error messages, but I see a Dumping Card Ends. The > first error is an SCB timeout (0x25) on 0:6:0 (the IBM drive). I also > see other SCB timeout on 0:0:0 (the Seagate drive). > > I can break into the debugger, but that's not much use (I'm always on > the keyboard interrupt handling routine) and I wouldn't know where to > go from there anyway. Would a panic be helpful (I'd would be painful > to setup but I would if needed)? > > Oh, I'm running -stable from last week: > (12:26:50 <~>) 0 $ uname -v > FreeBSD 4.9-RC #1: Fri Oct 3 21:02:09 CEST 2003 > joan@grummit.biaix.org:/fs/ > tmp/mount/tmp/build/obj/fs/bulk/mount/FreeBSD/src/sys/GRUMMITD > > I really don't know how to go on, any hints on what to do to help > debugging or what the source of the problem might be are most > welcomed. > > tks > -- > pica > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org" > > . From owner-freebsd-stable@FreeBSD.ORG Sun Oct 12 05:07:05 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1130E16A4B3 for ; Sun, 12 Oct 2003 05:07:05 -0700 (PDT) Received: from lmsmtp04.st1.spray.net (lmsmtp04.st1.spray.net [212.78.202.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79F6B43F85 for ; Sun, 12 Oct 2003 05:07:03 -0700 (PDT) (envelope-from jordi_yc@lycos.es) Received: from lycos.es (pcp04235215pcs.nrockv01.md.comcast.net [68.48.136.236]) by lmsmtp04.st1.spray.net (Postfix) with ESMTP id 6B16A47EBA for ; Sun, 12 Oct 2003 14:07:01 +0200 (MEST) Message-ID: <3F8943DF.4010806@lycos.es> Date: Sun, 12 Oct 2003 08:06:55 -0400 From: Jordi User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4; FreeBSD) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: 4.9-RC2: ad0: timeout waiting for DRQ problems. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Oct 2003 12:07:05 -0000 Hi, I am experiencing some issues with 4.9-RC2. /var/log/messages shows: Oct 12 00:16:05 thinkbsd /kernel: ad0: WRITE command timeout tag=0 serv=0 - resetting Oct 12 00:16:06 thinkbsd /kernel: ata0: resetting devices .. ata0-slave: ATA identify retries exce eded Oct 12 00:16:06 thinkbsd /kernel: done Oct 12 00:16:06 thinkbsd /kernel: ad0: timeout waiting for DRQ - resetting Oct 12 00:16:06 thinkbsd /kernel: ata0: resetting devices .. done Oct 12 00:16:06 thinkbsd /kernel: ad0: timeout waiting for DRQ - resetting Oct 12 00:16:06 thinkbsd /kernel: ata0: resetting devices .. done Oct 12 00:16:06 thinkbsd /kernel: ad0: timeout waiting for DRQ - resetting Oct 12 00:16:06 thinkbsd /kernel: ata0: resetting devices .. done Oct 12 00:25:16 thinkbsd /kernel: ad0: WRITE command timeout tag=0 serv=0 - resetting Oct 12 00:25:16 thinkbsd /kernel: ata0: resetting devices .. ata0-slave: ATA identify retries exce eded Oct 12 00:25:16 thinkbsd /kernel: done Oct 12 00:25:34 thinkbsd /kernel: ad0: WRITE command timeout tag=0 serv=0 - resetting Oct 12 00:25:35 thinkbsd /kernel: ata0: resetting devices .. ata0-slave: ATA identify retries exce eded The kernel is GENERIC (i686 only) + device pcm - firewire This happened with hw.ata.ata_dma=1 and now with 0 thinkbsd# sysctl -a | grep hw.ata hw.ata.ata_dma: 0 hw.ata.wc: 1 hw.ata.tags: 0 hw.ata.atapi_dma: 0 It also occured on Current with a snapshot from 2003 10 06. I run the "Disk Fitness Test" several times without any problems. If it is not a disk failure what could it be? Any hints on how to troubleshoot this? Searching the archives revealed possible issues with ATA/ATAng code. Is there any other additional info I can provide? The machine is an IBM Thinkpad T30. dmesg: ... ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ichsmb0: port 0x1880-0x189f irq 5 at device 31.3 on pci0 smbus0: on ichsmb0 smb0: on smbus0 pcm0: port 0x18c0-0x18ff,0x1c00-0x1cff irq 5 at device 31.5 on pci0 pcm0: pci0: (vendor=0x8086, dev=0x2486) at 31.6 irq 5 orm0: