From owner-freebsd-current Sun Aug 26 10: 9:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3]) by hub.freebsd.org (Postfix) with ESMTP id 2317137B409 for ; Sun, 26 Aug 2001 10:09:40 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from nantai.utsunomiya-u.ac.jp by nasu.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/26Jan01-1134AM) id f7QH9T5153949; Mon, 27 Aug 2001 02:09:29 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp by nantai.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/30Jan01-0241PM) id f7QH9Tc272071; Mon, 27 Aug 2001 02:09:29 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:aBS8yiijyTFQY9g8EDd7W+v8P6cX2Aih@zodiac.mech.utsunomiya-u.ac.jp [160.12.43.7]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id CAA15944; Mon, 27 Aug 2001 02:19:12 +0900 (JST) Message-Id: <200108261719.CAA15944@zodiac.mech.utsunomiya-u.ac.jp> To: Warner Losh Cc: current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: unknown PNP hardware In-reply-to: Your message of "Sun, 26 Aug 2001 09:51:57 CST." <200108261551.f7QFpvW11269@harmony.village.org> References: <200108261112.UAA14768@zodiac.mech.utsunomiya-u.ac.jp> <20010823172813.A69940@leviathan.inethouston.net> <200108251636.f7PGabW05246@harmony.village.org> <200108261551.f7QFpvW11269@harmony.village.org> Date: Mon, 27 Aug 2001 02:19:11 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >In message <200108261112.UAA14768@zodiac.mech.utsunomiya-u.ac.jp> Kazutaka YOK >OTA writes: >: Shouldn't we just suppress the message? It just confuses users. >: >: The attached patch will print this message only when we boot >: the kernel by 'boot -v'. > >They are there to remind certain folks that the ISA PnP code is broken >slightly and to please fix :-). If we get closer to 5.0 RC1, then >yes. > >Warner Um, we see these messages not only because our ISA PnP driver needs some update, but also because we create ISA device instances TWICE for each motherboard ISA devices, such as sio and atkbdc, due to /boot/device.hints. We need to have /boot/device.hints for those systems without PnP BIOS. On the system with the PnP BIOS, we shall have one ISA device instance (say, sio0) created by the isahint driver based on hints described in /boot/device.hints, and the pnpbios driver will create another instance (sio%d) for the very same device, based on information from the PnP BIOS. Then, we will see "unknown: can't assing resources" when the second device instance is probed. This happens even if the device driver understands PnP IDs. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message