From owner-freebsd-current Thu May 4 10:52:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (adsl-63-202-176-114.dsl.snfc21.pacbell.net [63.202.176.114]) by hub.freebsd.org (Postfix) with ESMTP id BEB7337B557 for ; Thu, 4 May 2000 10:52:09 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA00936; Thu, 4 May 2000 11:00:38 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005041800.LAA00936@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: tsikora@powerusersbbs.com Cc: Trent Nelson , "current@FreeBSD.ORG" Subject: Re: can't assign resources In-reply-to: Your message of "Thu, 04 May 2000 02:34:41 EDT." <39111A01.44BBE15A@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 May 2000 11:00:38 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Could someone please either take a look at this, or give an > > authoritative comment as to why it's happening. This is the ISA PnP code reporting devices enumerated via the PnP BIOS. At the moment, our support code isn't smart enough to use either the PnP interface or the resource manager, so the unknown device claims these resources to prevent anyone else trying to use them. It's quite harmless, and once things are cleaned up, you won't even see the messages. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message