From owner-freebsd-current  Mon Nov  6  8: 8: 1 2000
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP id 2AEBD37B4E5
	for <freebsd-current@FreeBSD.ORG>; Mon,  6 Nov 2000 08:07:58 -0800 (PST)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id RAA47558;
	Mon, 6 Nov 2000 17:08:04 +0100 (CET)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <200011061608.RAA47558@freebsd.dk>
Subject: Re: ad1 is not detected.
In-Reply-To: <20001106164113.B18026@petra.hos.u-szeged.hu> from Szilveszter Adam at "Nov 6, 2000 04:41:13 pm"
To: sziszi@petra.hos.u-szeged.hu (Szilveszter Adam)
Date: Mon, 6 Nov 2000 17:08:04 +0100 (CET)
Cc: freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It seems Szilveszter Adam wrote:
> On Mon, Nov 06, 2000 at 04:27:32PM +0100, Soren Schmidt wrote:
>  
> > Damn, why cant I reproduce this misbehavior, please feel free to investigate
> > why the probe code fails, and then please tell me...
> > 
> > -Søren

> Machine is on a Spacewalker mobo with Intel LX 440 chipset. (so no VIA @
> work this time) and a PII233. The probe code worked correctly on a world &
> kernel from 3rd November. No Promise etc or similar cards in the system just
> the on-board controller.
> 
> This narrows down the window to the last couple of days, there were not many
> files changed there wrt to ata. I will try things and will get back to you
> immediately. (unfortunately machine cannot send mail directly because of
> stupid university firewall.)
> 
> The only interesting thing is: Why were there no reports from -CURRENT users
> this far when this thing bit at least one person on -STABLE already? Is this
> such a rare occurence?

The problem has been around for at least a couble of month both in
current and stable, but only a select few has seen it, I've chased
it with any drive/controller I have access to, but hasn't been able
to reproduce it..
If you can find a way that I can reproduce it, I'm sure I can
fix the problem in a few minutes.. ssh access to a box that has
this problem could also help, but "hands on" are often much better
for this kind of problems...

-Søren


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message