Date: Mon, 20 May 2002 16:29:35 +0200 From: Matthias Andree <ma@dt.e-technik.uni-dortmund.de> To: freebsd-stable@freebsd.org Cc: sos@freebsd.org Subject: Re: ATA observations in FreeBSD 4.6-RC Message-ID: <m3it5iyjsg.fsf@merlin.emma.line.org> In-Reply-To: <20020520171102.C80338-100000@woozle.rinet.ru> (Dmitry Morozovsky's message of "Mon, 20 May 2002 17:15:20 %2B0400 (MSD)") References: <20020520171102.C80338-100000@woozle.rinet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
NOTE: Please Cc: me on replies. Dmitry Morozovsky <marck@rinet.ru> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m3it5iyjsg.fsf>