From owner-freebsd-questions@FreeBSD.ORG  Wed Apr 23 19:47:47 2003
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1A44237B401
	for <freebsd-questions@FreeBSD.ORG>;
	Wed, 23 Apr 2003 19:47:47 -0700 (PDT)
Received: from dragoncrest.jasnetworks.net (dragoncrest.jasnetworks.net
	[65.194.254.12])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5F3A343F75
	for <freebsd-questions@FreeBSD.ORG>;
	Wed, 23 Apr 2003 19:47:46 -0700 (PDT)
	(envelope-from dragoncrest@voyager.net)
Received: from works.voyager.net (works.jasnetworks.net [192.168.0.2])
	h3NLxV2K067160
	for <freebsd-questions@FreeBSD.ORG>; Wed, 23 Apr 2003 21:59:31 GMT
	(envelope-from dragoncrest@voyager.net)
Message-Id: <5.2.0.9.2.20030423225525.00a04670@pop.voyager.net>
X-Sender: dragoncrest@pop.voyager.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 23 Apr 2003 22:58:24 -0400
To: freebsd-questions@FreeBSD.ORG
From: Dragoncrest <dragoncrest@voyager.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Strange Dmesg error
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Apr 2003 02:47:47 -0000

	Today after recompiling my kernel I noticed something on my screen that 
caught my curiousity.  I got the following message:

Apr 23 22:22:05 bsdbox /kernel: ppi0: <Parallel I/O> on ppbus0
Apr 23 22:22:05 bsdbox /kernel: unknown: <PNP0000> can't assign resources
Apr 23 22:22:05 bsdbox /kernel: unknown: <PNP0303> can't assign resources
Apr 23 22:22:05 bsdbox /kernel: unknown: <PNP0c02> can't assign resources
Apr 23 22:22:05 bsdbox /kernel: unknown: <PNP0501> can't assign resources
Apr 23 22:22:05 bsdbox /kernel: unknown: <PNP0700> can't assign resources
Apr 23 22:22:05 bsdbox /kernel: unknown: <PNP0401> can't assign resources
Apr 23 22:22:05 bsdbox /kernel: unknown: <PNP0501> can't assign resources

	Anyone know what this means?  All I did was add the following lines to my 
kernel config.

options         VESA
device          pcm
options         PNPBIOS
options         USER_LDT

	Would any of those have generated the said errors, and are they something 
to be concerned about, or can I safely ignore them?