From owner-freebsd-stable Tue Jul 9 16:56:59 2002 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 8135137B400 for ; Tue, 9 Jul 2002 16:56:54 -0700 (PDT) Received: from cultdeadsheep.org (charon.cultdeadsheep.org [80.65.226.72]) by mx1.FreeBSD.org (Postfix) with SMTP id C92D243E3B for ; Tue, 9 Jul 2002 16:56:52 -0700 (PDT) (envelope-from sheep.killer@cultdeadsheep.org) Received: (qmail 43179 invoked from network); 9 Jul 2002 23:56:50 -0000 Received: from unknown (HELO satan.cultdeadsheep.org) (192.168.0.4) by goofy.cultdeadsheep.org with SMTP; 9 Jul 2002 23:56:50 -0000 Date: Wed, 10 Jul 2002 01:56:49 +0200 From: Clement Laforet To: stable@freebsd.org Subject: strange ATA behavior with -STABLE Message-Id: <20020710015649.0592a44a.sheep.killer@cultdeadsheep.org> Organization: tH3 cUlt 0f tH3 d3@d sH33p X-Mailer: Sylpheed version 0.7.8 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi guys :) I "recently" upgraded one of my server from 4.5 (RELENG_4_5) to stable (RELENG_4) on the 4th july (nearly 9am CEST). And I noticed few hours ago, a little difference with the ata drivers. I know they have changed but there is something which "disturbs" me. Here a piece of log I have when "ATA failled". I don't know why. Disks seems to be ok, maybe the heat ;) so... Jul 4 09:00:40 goofy /kernel: ad0: READ command timeout tag=0 serv=0 - resetting Jul 4 09:00:40 goofy /kernel: ata0: resetting devices .. done Jul 4 09:00:50 goofy /kernel: ad0: READ command timeout tag=0 serv=0 - resetting Jul 4 09:01:10 goofy last message repeated 2 times Jul 4 09:01:10 goofy /kernel: ata0-master: timeout waiting for command=ef s=00 e=00 Jul 4 09:01:10 goofy /kernel: ad0: trying fallback to PIO mode Jul 4 09:01:20 goofy /kernel: ad0: READ command timeout tag=0 serv=0 - resetting After this, the system was still up, even if I was unable to access ad0 and ad2, processes "simply became dead". (system an 'sensible data' are on SCSI disks) Without happiness, I deal with this ;) This was before I upgrade ;) I thought (bad ?) that upgrading to newer version of ata driver, allows me to reset ata buses, and repair this "on the fly". I was wrong ! Now my FreeBSD system freezes. The last console info is (like): ad2: read command timeout tag=0 serv=0 - resetting ata-1 resetting *FREEZE* and then hard reboot Nothing in syslog :) And now the question :o) Before considering what that happened (four times in 8hours today), I would like to know how I can trace this (kernel options, soft, daemon). Or maybe I've done a bad things ;) here's my uname -a : FreeBSD goofy.cultdeadsheep.org 4.6-STABLE FreeBSD 4.6-STABLE #0: Thu Jul 4 10:05:12 CEST 2002 root@goofy.cultdeadsheep.org:/usr/obj/usr/src/sys/GOOFY i386 here's my ata (standard) kernel conf : device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering Thanks a lot in advanced, and I hope this "report" could be useful ;) clem PS: like other french people, sorry for my english ;) and sorry to post if I've done something bad ;) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message