From owner-freebsd-current@FreeBSD.ORG Wed Sep 8 07:36:26 2004 Return-Path: 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 A6EC616A4CE for ; Wed, 8 Sep 2004 07:36:26 +0000 (GMT) Received: from axe-inc.co.jp (axegw.axe-inc.co.jp [61.199.217.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD44F43D5D for ; Wed, 8 Sep 2004 07:36:25 +0000 (GMT) (envelope-from takawata@axe-inc.co.jp) Received: from localhost (localhost [127.0.0.1]) by axe-inc.co.jp (8.9.3+3.2W/3.7W) with SMTP id QAA05148; Wed, 8 Sep 2004 16:36:20 +0900 (JST) Message-Id: <200409080736.QAA05148@axe-inc.co.jp> X-Authentication-Warning: axegw.axe-inc.co.jp: localhost [127.0.0.1] didn't use HELO protocol To: Mike Tancsa From: takawata@jp.freebsd.org In-reply-to: Your message of "Wed, 08 Sep 2004 03:30:06 -0400." <6.1.2.0.0.20040908032814.062d9860@64.7.153.2> Date: Wed, 08 Sep 2004 16:36:20 +0900 Sender: takawata@axe-inc.co.jp cc: freebsd-current@freebsd.org Subject: Re: can't re-use a leaf ? (with boot -v) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 08 Sep 2004 07:36:26 -0000 In message <6.1.2.0.0.20040908032814.062d9860@64.7.153.2>, Mike Tancsa wrote: >--=====================_-894073640==_ >Content-Type: text/plain; charset="us-ascii"; format=flowed > >At 02:18 PM 07/09/2004, Mike Tancsa wrote: > >>In my dmesg, I get this rather odd message in a freshly installed RELENG_5 >>(beta 3) box >> >>can't re-use a leaf (%desc)! >>can't re-use a leaf (%driver)! >>can't re-use a leaf (%location)! >>can't re-use a leaf (%pnpinfo)! >>can't re-use a leaf (%parent)! Generally it is appear when a driver attempt to register MIB on existing sysctl node. >>What do they mean ? >> >>(acpidump -d -v) can be found at www.sentex.net/~mdtancsa/acpidump.txt > >Someone suggested I post a boot -v. Attached are the results. >sio0: Reserved 0x8 bytes for rid 0x10 type 4 at 0xa400 >sio0: irq maps: 0x1 0x1001 0x1 0x1 >sio0: port 0xa400-0xa407 irq 12 at device 5.0 on pci1 >sio0: moving to sio4 >pcib1: device sio4 requested decoded I/O range 0xa400-0xa407 >sio4: type 16550A .... >sio0: irq maps: 0x1 0x11 0x1 0x1 >can't re-use a leaf (%desc)! >can't re-use a leaf (%driver)! >can't re-use a leaf (%location)! >can't re-use a leaf (%pnpinfo)! >can't re-use a leaf (%parent)! >sio0 port 0x3f8-0x3ff irq 4 on acpi0 >sio0: type 16550A, console Hmm it is because the unit tweak is not handled properly.