From owner-freebsd-stable@FreeBSD.ORG Mon Jun 2 13:50:27 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D601837B43E for ; Mon, 2 Jun 2003 13:50:26 -0700 (PDT) Received: from dn.farlep.net (ns.dn.farlep.net [213.130.10.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACB7A43FAF for ; Mon, 2 Jun 2003 13:50:16 -0700 (PDT) (envelope-from admin@dru.dn.ua) Received: from dru.dn.ua (dru.dn.ua [195.5.21.149] (may be forged)) h52Knsje053684 for ; Mon, 2 Jun 2003 23:49:55 +0300 (EEST) Received: (from admin@localhost) by dru.dn.ua (8.12.9/8.12.9) id h52KnOPn003496; Mon, 2 Jun 2003 23:49:24 +0300 (EEST) (envelope-from admin) Date: Mon, 2 Jun 2003 23:49:24 +0300 From: "Vladislav V. Zhuk" To: Matthias Andree Message-ID: <20030602204924.GA2697@dru.dn.ua> References: Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i cc: stable@freebsd.org Subject: Re: "disable ata" in kernel configuration not working? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jun 2003 20:50:27 -0000 On Mon, Jun 02, 2003 at 09:22:21PM +0200, Matthias Andree wrote: > I have an up-to-date FreeBSD 4-STABLE system with onboard ATA controller > (VIA 82C586-mumble) but no ATA/ATAPI devices (SCSI only). > > I tried putting > > disable ata > disable ata0 > disable ata1 > quit > > into /boot/kernel.conf to skip probing these devices (it hangs until > timeout), but to no avail, the kernel still sees ata0 and ata1 and > probes for drives (which takes several dozen seconds). > > I see at boot-up that these disable instructions are executed (the > corresponding loader.conf flag is set). > > I also tried disabling atapci0 which is what I see, but that one is > rejected with something like "no such device". > > Is this a known issue or should I file a PR? It's one of well known demonstration of bugs new ATA driver. This BUG is very strong and don't resolve in kernel.conf. I wrote about this 3 times, but Soren Schmidt is very busy for resolving this problem more than 1 year or don't read stable@ and e-mail. -- Vladislav V. Zhuk (06267)3-60-03 admin@dru.dn.ua 2:465/197@FidoNet.org