From owner-freebsd-current@FreeBSD.ORG Thu Oct 28 18:13:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12A7716A4CE for ; Thu, 28 Oct 2004 18:13:25 +0000 (GMT) Received: from crumpet.united-ware.com (ddsl-66-42-172-210.fuse.net [66.42.172.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A8FF43D66 for ; Thu, 28 Oct 2004 18:13:24 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.0.6] (adsl-69-211-137-113.dsl.wotnoh.ameritech.net [69.211.137.113]) (authenticated bits=0)i9SHtaUJ041444 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Thu, 28 Oct 2004 13:55:38 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: "Daan Vreeken [PA4DAN]" Date: Thu, 28 Oct 2004 14:15:48 -0400 User-Agent: KMail/1.7 References: <200410272315.29299.mistry.7@osu.edu> <200410281608.22225.Danovitsch@Vitsch.net> In-Reply-To: <200410281608.22225.Danovitsch@Vitsch.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart5877876.qNxCPxJ4RO"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200410281415.55928.mistry.7@osu.edu> X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on crumpet.united-ware.com cc: freebsd-current@freebsd.org Subject: Re: kern/73000: UHCI driver fails to detect (certain) interrupts on boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Oct 2004 18:13:25 -0000 --nextPart5877876.qNxCPxJ4RO Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 28 October 2004 10:08 am, you wrote: > On Thursday 28 October 2004 05:15, you wrote: > > uhci0: port 0xd800-0xd81f irq 3 at device > > 17.2 on pci0 > > uhci0: [GIANT-LOCKED] > > usb0: on uhci0 > > usb0: USB revision 1.0 > > uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > > uhub0: 2 ports with 2 removable, self powered > > uhub1: Texas Instruments TUSB2046 hub, class 9/0, rev 1.10/1.25, addr > > 2 uhub1: 4 ports with 4 removable, self powered > > uhci1: port 0xdc00-0xdc1f irq 3 at device > > 17.3 on pci0 > > uhci1: [GIANT-LOCKED] > > usb1: on uhci1 > > usb1: USB revision 1.0 > > uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > > uhub2: 2 ports with 2 removable, self powered > > uhci2: port 0xe000-0xe01f irq 3 at device > > 17.4 on pci0 > > uhci2: [GIANT-LOCKED] > > usb2: on uhci2 > > usb2: USB revision 1.0 > > uhub3: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > > uhub3: 2 ports with 2 removable, self powered > > > > This patch causes problems with my system and plugging in usb devices, > > they are most of the time not detected. > > It could be that this patch causes you problems, but to know for sure > and to find out where it's going wrong I need more information. Could > you please be more specific in what you could do without the patch, and > what doesn't work with the patch? > > Can you provide the dmesg log events of a kernel with and without the > patch and show what you think goes wrong there? > > thanks, > Daan Well I guess it must have been some freak occurance since I tried the patch= =20 again today and everything seems to be working. =2D-=20 Anish Mistry --nextPart5877876.qNxCPxJ4RO Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBgTdbxqA5ziudZT0RAi1qAJ0XySCKqHHleeOZvNLvLEKRLcP6BQCg1wE0 TqclvOz7ko0IyTstwqYcJJk= =kkc6 -----END PGP SIGNATURE----- --nextPart5877876.qNxCPxJ4RO--