From owner-freebsd-current@FreeBSD.ORG Thu Oct 28 18:53:23 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 2348C16A4CE for ; Thu, 28 Oct 2004 18:53:23 +0000 (GMT) Received: from amsfep19-int.chello.nl (amsfep19-int.chello.nl [213.46.243.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id B47E043D2D for ; Thu, 28 Oct 2004 18:53:21 +0000 (GMT) (envelope-from Danovitsch@Vitsch.net) Received: from Vitsch.net ([212.187.78.35]) by amsfep19-int.chello.nl (InterMail vM.6.01.03.04 201-2131-111-106-20040729) with ESMTP id <20041028185319.VEFI24789.amsfep19-int.chello.nl@Vitsch.net>; Thu, 28 Oct 2004 20:53:19 +0200 Received: from 192.168.1.36 (f59122.upc-f.chello.nl [80.56.59.122]) by Vitsch.net (8.12.3p2/8.11.3) with ESMTP id i9SIrAun088604; Thu, 28 Oct 2004 20:53:12 +0200 (CEST) (envelope-from Danovitsch@Vitsch.net) From: "Daan Vreeken [PA4DAN]" To: Anish Mistry Date: Thu, 28 Oct 2004 20:52:39 +0200 User-Agent: KMail/1.5.2 References: <200410272315.29299.mistry.7@osu.edu> <200410281608.22225.Danovitsch@Vitsch.net> <200410281415.55928.mistry.7@osu.edu> In-Reply-To: <200410281415.55928.mistry.7@osu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200410282052.39849.Danovitsch@Vitsch.net> 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:53:23 -0000 On Thursday 28 October 2004 20:15, you wrote: > 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 > again today and everything seems to be working. Ok, thanks for trying the patch again. It would have wonderd me if the patch killed something, since the patch handles more interrupts, not less. But having it verified on more machines is always a good thing. grtz, Daan