From owner-freebsd-bugs@FreeBSD.ORG Mon Jul 14 22:50:19 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4CE837B401 for ; Mon, 14 Jul 2003 22:50:19 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BF4243FBD for ; Mon, 14 Jul 2003 22:50:19 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h6F5oJUp055785 for ; Mon, 14 Jul 2003 22:50:19 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h6F5oJo0055783; Mon, 14 Jul 2003 22:50:19 -0700 (PDT) Date: Mon, 14 Jul 2003 22:50:19 -0700 (PDT) Message-Id: <200307150550.h6F5oJo0055783@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: JacobRhoden Subject: Re: kern/54490: Intel D845EPT2 Motherboard USB driver problem X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: JacobRhoden List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2003 05:50:19 -0000 The following reply was made to PR kern/54490; it has been noted by GNATS. From: JacobRhoden To: freebsd-gnats-submit@FreeBSD.org, jrhoden@elkanah.its.unimelb.edu.au Cc: Subject: Re: kern/54490: Intel D845EPT2 Motherboard USB driver problem Date: Tue, 15 Jul 2003 15:38:06 +1000 Further investigation revealed the following. Whenever you attach ANY device to ANY port you recieve the following error in dmesg: uhub0: device problem, disabling port 1 uhub2: device problem, disabling port 1 uhub2: device problem, disabling port 2 uhub2: device problem, disabling port 1 uhub0: device problem, disabling port 1 This is a message generated in: /usr/src/sys/dev/usb/uhub.c I am not experienced in debugging so I am not sure exactly how to work out why this is happening.