From owner-freebsd-stable Mon May 20 7:29:56 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.dt.e-technik.uni-dortmund.de (krusty.dt.E-Technik.Uni-Dortmund.DE [129.217.163.1]) by hub.freebsd.org (Postfix) with ESMTP id 230F137B406; Mon, 20 May 2002 07:29:41 -0700 (PDT) Received: from merlin.emma.line.org (localhost [127.0.0.1]) by mail.dt.e-technik.uni-dortmund.de (Postfix) with ESMTP id AD042A3831; Mon, 20 May 2002 16:29:38 +0200 (CEST) Received: by merlin.emma.line.org (Postfix, from userid 500) id 1832337B48; Mon, 20 May 2002 16:29:35 +0200 (CEST) X-Draft-From: ("nnml+private:freebsd-stab" 26756) To: freebsd-stable@freebsd.org Cc: sos@freebsd.org Subject: Re: ATA observations in FreeBSD 4.6-RC References: <20020520171102.C80338-100000@woozle.rinet.ru> In-Reply-To: <20020520171102.C80338-100000@woozle.rinet.ru> (Dmitry Morozovsky's message of "Mon, 20 May 2002 17:15:20 +0400 (MSD)") From: Matthias Andree Date: Mon, 20 May 2002 16:29:35 +0200 Message-ID: Lines: 48 User-Agent: Gnus/5.090007 (Oort Gnus v0.07) Emacs/21.1 (i686-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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 NOTE: Please Cc: me on replies. Dmitry Morozovsky writes: > SS> This is a known problem (for some) but until now I havn't been able > SS> to reproduce it here at all, and hence have not been able to > SS> work on a fix. The solution would be to make a note in the docs > SS> somewhere that there is potential problems on some HW wtih this.. > > Well, Soren, I already told I have test box with serial console and > would be very happy to help track these bugs down (actually, I've already > made an account for you there -- so just contact me privately, please > ;-) Dmitry, please apologize for using your mail as a stepping stone, but I did not get Soeren's reply. If my PR #37060 lacks ANY information that may help tracking this down. I just filed a followup noting that I'm using ATA_STATIC_ID today because I found it lacked from my original report. It MAY be because I don't have an ad1 drive and use ATA_STATIC_ID. It MAY be because ATA initialization is hosed. It MAY be because ad1 is not there regardless of STATIC_ID state. I am willing to help find the bug, to use ata-disk.c kernel debugging patches to track this bug down, and I have two computers here, I can certainly use a serial debugger if instructed what I am to look for. Full kernel compilation for my machine with my configuration takes less than 10 minutes. I'm a C/C++ programmer, but I'm not acquainted with ata(4) or ata-disk.c or FreeBSD kernel hacking, and I'm not really aware of DDB or FreeBSD kernel debugging tools. > I realize that at the very moment it would be inappropriate to deep > digging due to RC stage for 4.6. But, sooner or later (and I personally > prefer sooner, you know :) this should be fixed. Show stopper and "panic at boot-up" are best fixed before the release. If the release schedule is not met, that's still better than a hosed ATA/IDE sub system and a spoiled reputation. If this issue cannot be nailed down, then tagged queueing should be a compile-time option and be removed from the GENERIC kernel. -- Matthias Andree To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message