From owner-freebsd-current@FreeBSD.ORG Fri Apr 9 11:04:58 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 701C316A4CE; Fri, 9 Apr 2004 11:04:58 -0700 (PDT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id F40F643D1D; Fri, 9 Apr 2004 11:04:57 -0700 (PDT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (localhost [127.0.0.1]) i39I4ttE053966; Fri, 9 Apr 2004 14:04:55 -0400 (EDT) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)i39I4t5D053963; Fri, 9 Apr 2004 14:04:55 -0400 (EDT) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Fri, 9 Apr 2004 14:04:55 -0400 (EDT) From: Andre Guibert de Bruet To: Nik Clayton In-Reply-To: <20040408113549.GA15150@clan.nothing-going-on.org> Message-ID: <20040409140410.W37257@alpha.siliconlandmark.com> References: <20040406124641.GA800@clan.nothing-going-on.org> <20040406160551.GD800@clan.nothing-going-on.org> <20040407183259.GB741@clan.nothing-going-on.org> <20040408113549.GA15150@clan.nothing-going-on.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: current@freebsd.org Subject: Re: USB issues -- dodgy motherboard? 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: Fri, 09 Apr 2004 18:04:58 -0000 On Thu, 8 Apr 2004, Nik Clayton wrote: > On Thu, Apr 08, 2004 at 11:55:41AM +0200, Bernd Walter wrote: > > On Wed, Apr 07, 2004 at 07:32:59PM +0100, Nik Clayton wrote: > > > On Tue, Apr 06, 2004 at 10:45:22AM -0700, Doug White wrote: > > > > I have an IBM machine at work with this southbridge and it happily talks > > > > to a Lexar usb key, so I suspect interrupt problems. > > > > > > > > Have you tried it after booting with ACPI disabled? > > > > > > I just tried with > > > > > > hint.acpi.0.disabled="1" > > > > > > in /boot/device hints. The boot got this far through the process: > > > > > > [...] > > > uhci0: port 0xc000-0xc01f irq 10 at device 7.2 on pci0 > > > 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 > > > > > > and then hung. I left it for five minutes, no activity, and no response > > > on the keyboard, so I hit the reset button. For reference, the next > > > lines in the boot sequence with ACPI enabled are: > > > > > uhub1: Atmel Standard USB Hub, class 9/0, rev 1.10/3.00, addr 2 > > > uhub1: 4 ports with 4 removable, self powered > > > > So here is the difference - the Atmel hub don't show up in the problem > > case. > > Not exactly. The machine locked solid before it printed the probe line > for the Atmel hub. Trying to drop to the debugger did nothing, no > response to Caps-Lock keys, and so on. > > > It's having problems with the connected hub device. > > Is this 100% reproduceable or just from time to time? > > I only tried booting with ACPI disabled once. Without the line > > hint.acpi.0.disabled="1" > > in /boot/device.hints, the system boots fine, but plugging in USB > devices does nothing -- my original message, at > > http://lists.freebsd.org/pipermail/freebsd-current/2004-April/025164.html > > has more details. > > With that line (following a suggestion to disable ACPI) the system hangs > at boot. > > > Does the hub really have it's own power supply as it claims? > > Yes. The hub is integrated in to the monitor. Note, however, that I'm > seeing problems with devices plugged in to the motherboard's USB ports, > *and* the hub's USB ports. > > > Please retry with a USB_DEBUG kernel - in case of a broken device the > > probing may take serveral minutes - maybe we should give some output > > without USB_DEBUG too in this case. > > Will do. Silly question: Are you running with the latest firmware for your motherboard? Regards, Andy > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ >