From owner-freebsd-questions Sun Jul 23 10:25:31 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail.rz.uni-ulm.de (sirius-ether.rz.uni-ulm.de [134.60.1.36]) by hub.freebsd.org (Postfix) with ESMTP id 2EEE137BCFF for ; Sun, 23 Jul 2000 10:25:22 -0700 (PDT) (envelope-from siegbert.baude@gmx.de) Received: from gmx.de (lilith.wohnheim.uni-ulm.de [134.60.106.64]) by mail.rz.uni-ulm.de (8.9.3/8.9.3) with ESMTP id TAA00232; Sun, 23 Jul 2000 19:24:41 +0200 (MEST) Message-ID: <397B2A45.4BAD7ABF@gmx.de> Date: Sun, 23 Jul 2000 19:24:21 +0200 From: Siegbert Baude X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.1-RC i386) X-Accept-Language: de, en MIME-Version: 1.0 To: Sean-Paul Rees , "freebsd-questions@freebsd.org" Subject: Re: dmesg questions References: <20000722141507.A59837@seanrees.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Sean-Paul, > A few "odd" messages have been appearing in my dmesg's on my 4.1-RC workstation. > This has been happening since I first installed 4.0-RELEASE on it a few weeks > ago. > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > uhub0: port 1 power on failed, IOERROR > uhub0: port 2 power on failed, IOERROR I have exactly the same IOERROR on an ASUS P2B, also on 4.1RC of Thu Jul 20, which wasn't in my /var/log/messages, when running 4.0 STABLE. (Don't know, if USB actually works as I don't have any device for the moment.) Anyone knows, if this is supposed to be correct? > uhub1: KC Technology, Inc. USB Compound Hub, class 9/0, rev 1.00/2.00, addr 2 > uhub1: 5 ports with 4 removable, self powered > (referring to IOERROR) > isab0: at device 2.0 on pci0 > isa0: on isab0 > isa0: too many dependant configs (8) This one won't harm you. It's because any ISA-device (Soundblaster AWE 64, I guess?) gives too many proposals for possible PnP-Configurations. I think there was a patch posted here to get rid of these messages. You can verify this, when booting with with verbose option. (Interrupt boot process, then type boot -v) > ppc0: cannot reserve I/O port range Are you still able to print? Ciao Siegbert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message