Date: Thu, 5 Jul 2007 14:49:32 +0200 From: Nikola Lecic <nlecic@EUnet.yu> To: Zhang Weiwu <zhangweiwu@realss.com> Cc: freebsd-questions@freebsd.org Subject: Re: unknown: <PNP0f13> can't assign resources (irq) Message-ID: <200707051249.l65CnYmg000752@smtpclu-6.eunet.yu> In-Reply-To: <1183638103.9913.28.camel@esmeralda> References: <1183638103.9913.28.camel@esmeralda>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 05 Jul 2007 20:21:42 +0800 Zhang Weiwu <zhangweiwu@realss.com> wrote: > Dear list >=20 > I have seen strange message in my dmesg which says it cannot assign > resources to PNP device: >=20 > [snip] > sc0: VGA <16 virtual consoles, flags=3D0x300> > vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on > isa0 > unknown: <PNP0303> can't assign resources (port) > unknown: <PNP0f13> can't assign resources (irq) > unknown: <PNP0700> can't assign resources (port) > unknown: <PNP0c02> can't assign resources (memory) > unknown: <PNP0400> can't assign resources (port) > pcm0: <CS423x> at port 0x530-0x537,0x388-0x38b,0x220-0x233 irq 5 drq > 1,0 on isa0 [/snip] >=20 > I have googled around and discussion around the the topic of "PNPxxx > cannot assign resouce" mostly happen in 2002 ~ 2005, they have > suggested not to use PNPBIOS option in kernel, which I didn't use at > all and cannot see references to this kernel option (so should be a > removed option). Others on the forums suggested (in 2003) that I > should disable PNP feature in BIOS, which is impossible for me > because my old IBM Thinkpad don't offer such config option (the only > config option had been change system date/time and > start-up-sequence). Even if it doesn't affect the use of the system > I'd like to know a bit about the background knowledge. At least two > devices on my FreeBSD doesn't work, the COM port and the second > PCMCIA slot (anything on that slot doesn't work), though I don't > think the two devices are related to this kernel message. Hello Zhang, Those messages are completely harmless (as you have surely already read, resources can't be assigned because certain driver(s) are already using them). There is no elegant way to disable them AFAIK. The fact that your devices are not working properly is not related to them but to something else in your installation. Nikola Le=C4=8Di=C4=87
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200707051249.l65CnYmg000752>