From owner-freebsd-current Thu Apr 18 9:16:30 2002 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 8285237B429 for ; Thu, 18 Apr 2002 09:15:57 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.12.2/8.12.2) id g3IGFttE048811; Thu, 18 Apr 2002 18:15:55 +0200 (CEST) (envelope-from sos) From: Søren Schmidt Message-Id: <200204181615.g3IGFttE048811@freebsd.dk> Subject: Re: ATA errors on recent -current In-Reply-To: <200204181611.g3IGBN5Z000628@Magelan.Leidinger.net> To: Alexander Leidinger Date: Thu, 18 Apr 2002 18:15:55 +0200 (CEST) Cc: tlambert2@mindspring.com, msch@snafu.de, freebsd-current@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It seems Alexander Leidinger wrote: > On 18 Apr, Søren Schmidt wrote: > > >> What's your theory on it? > > > > None so far, I've instrumented the code here, and I simply cannot > > see what should go wrong (yet). > > Does it make sense to give this instrumentation to someone who can > reproduce it? Not directly since its tied in with special HW to look for interrupts etc, a real hackers delight setup :) Now I have this patch that fixes the mess from the busdma integration that will go in later tonight when my test machine has finished its current test round. When thats done I need -current users with tag problems to upgrade and those with problems should mail me thers dmesg so I can try to get a grasp on what HW fails exactly. Semilar for -stable users, if you have problems with tags, mail me your dmesg... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message