From owner-freebsd-current Mon Nov 6 7:48:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id 3D69837B4C5 for ; Mon, 6 Nov 2000 07:48:47 -0800 (PST) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id QAA13547; Mon, 6 Nov 2000 16:38:16 +0100 (MET) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 13soOX-0004vz-00; Mon, 06 Nov 2000 16:41:13 +0100 Date: Mon, 6 Nov 2000 16:41:13 +0100 From: Szilveszter Adam To: Soren Schmidt Cc: freebsd-current@FreeBSD.ORG Subject: Re: ad1 is not detected. Message-ID: <20001106164113.B18026@petra.hos.u-szeged.hu> Mail-Followup-To: Soren Schmidt , freebsd-current@FreeBSD.ORG References: <20001106162328.A18026@petra.hos.u-szeged.hu> <200011061527.QAA37316@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.0.1i In-Reply-To: <200011061527.QAA37316@freebsd.dk>; from sos@freebsd.dk on Mon, Nov 06, 2000 at 04:27:32PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 :-) Relax. We will sort this out somehow. I will try what I can. For now, further hardware details: 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? -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message