From owner-freebsd-current@FreeBSD.ORG Thu Sep 18 09:38:31 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8667716A4B3 for ; Thu, 18 Sep 2003 09:38:31 -0700 (PDT) Received: from spider.deepcore.dk (cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB33243FCB for ; Thu, 18 Sep 2003 09:38:29 -0700 (PDT) (envelope-from sos@spider.deepcore.dk) Received: from spider.deepcore.dk (localhost [127.0.0.1]) by spider.deepcore.dk (8.12.9/8.12.9) with ESMTP id h8IGcPj5025308; Thu, 18 Sep 2003 18:38:25 +0200 (CEST) (envelope-from sos@spider.deepcore.dk) Received: (from sos@localhost) by spider.deepcore.dk (8.12.9/8.12.9/Submit) id h8IGcPox025307; Thu, 18 Sep 2003 18:38:25 +0200 (CEST) From: Soren Schmidt Message-Id: <200309181638.h8IGcPox025307@spider.deepcore.dk> In-Reply-To: <20030918155125.GC22643@student.agh.edu.pl> To: w@dream.vg Date: Thu, 18 Sep 2003 18:38:25 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL99f (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 X-mail-scanned: by DeepCore Virus & Spam killer v1.3 cc: freebsd-current@FreeBSD.ORG Subject: Re: ATAng still problematic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2003 16:38:31 -0000 It seems Jan Srzednicki wrote: > > > First of all, the drive still does not get detected properly. Funny > > > thing is that after some playing with atacontrol attach/detach, it > > > finally gets detected. And later on, it is normally detected, before. > > > Same scenario happened like 3 times with ATAng and newer and newer > > > kernels. I don't know whether some device hints or anything are just > > > updated; yet, I didn't have _any_ drive detection problems with ATAold. > > > > > > The problem is with the second drive. There's still some randomness in > > > it, as it gets undetected from time to time. > > > > Try the below patch and let me know if that changes anything.. > > It seems that things have changed a bit (the drive gets detected more > often), but still, it's not perfect. Perfect ? hmm - I'd settle for works :) Anyhow, what I need to be able to tell what may be going on, is that you boot verbose and get me the output from dmesg from a boot that found all device, and from a boot that missed. > Anyway, here's backtrace for atapicam panic I've mentioned. It's > triggered by: No idea, atapicam is not my area, maybe thomas@ can help... -Søren