From owner-freebsd-current@FreeBSD.ORG Fri Oct 21 18:00:50 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.ORG Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E427816A420 for ; Fri, 21 Oct 2005 18:00:50 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7CA2843D48 for ; Fri, 21 Oct 2005 18:00:50 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id j9LI0VA8027354; Fri, 21 Oct 2005 12:00:31 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Fri, 21 Oct 2005 12:01:55 -0600 (MDT) Message-Id: <20051021.120155.26928265.imp@bsdimp.com> To: terry@tmk.com From: "M. Warner Losh" In-Reply-To: <01LUGIEOVCHY0005PA@tmk.com> References: <01LUG3XKETWK000G07@tmk.com> <20051021.093800.127812213.imp@bsdimp.com> <01LUGIEOVCHY0005PA@tmk.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Fri, 21 Oct 2005 12:00:31 -0600 (MDT) Cc: freebsd-current@FreeBSD.ORG Subject: Re: 6.0-RC1 new message: "atapci0: failed to enable memory mapping!" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Oct 2005 18:00:51 -0000 In message: <01LUGIEOVCHY0005PA@tmk.com> Terry Kennedy writes: : > In message: <01LUG3XKETWK000G07@tmk.com> : > Terry Kennedy writes: : > : The message seems to be harmless, but is confusing. : > : > The message is harmless and can be ignored. You'll only see this in : > bootverbose. : : Actually, I get it with a regular non-verbose boot. I turned on the verbose : messages to see if any related messages would print (they didn't) before re- : porting this. Hmmm, it is supposed to only be printed in the verbose case. I'll double check to see why that isn't happening, and fix as appropriate. Warner