From owner-freebsd-stable Sun Jan 14 8: 8:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cj409896-a.reston1.va.home.com (cj409896-a.reston1.va.home.com [24.23.165.156]) by hub.freebsd.org (Postfix) with ESMTP id 734CE37B401; Sun, 14 Jan 2001 08:08:12 -0800 (PST) Received: from localhost (dwagner@localhost) by cj409896-a.reston1.va.home.com (8.11.1/8.11.1) with ESMTP id f0EG84x47121; Sun, 14 Jan 2001 11:08:04 -0500 (EST) (envelope-from dawagner@vt.edu) Date: Sun, 14 Jan 2001 11:08:04 -0500 (EST) From: David Wagner X-X-Sender: To: Odhiambo Washington Cc: FBSD-STABLE , FBSD-Q Subject: Re: Strange device probe behavior In-Reply-To: <20010114122845.A400@poeza.iconnect.co.ke> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 14 Jan 2001, Odhiambo Washington wrote: > atapci0: port 0x1860-0x186f at device > 4.1 on pci0 > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > This is where 15 or so seconds lapse before the probe continues!! Well, if it makes you feel any better, my system does this too. It has: atapci0: port 0x18a0-0x18af at device 7.1 on pci0 Mine's a Gateway system I bought a couple years ago and recently turned into a FreeBSD box. I've never noticed any problems with it -- once the probe continues everything seems to be fine. I certainly have no idea _why_ it does it, but at least it doesn't seem to be cause for panic. :) ______________________________________________________________________ David Wagner dawagner@vt.edu Reston, Virginia ICQ: 9963339 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message