From owner-freebsd-usb@FreeBSD.ORG Mon Jan 5 18:00:09 2009 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1B92106564A for ; Mon, 5 Jan 2009 18:00:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 96C4C8FC19 for ; Mon, 5 Jan 2009 18:00:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n05I09wT016409 for ; Mon, 5 Jan 2009 18:00:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n05I097i016408; Mon, 5 Jan 2009 18:00:09 GMT (envelope-from gnats) Date: Mon, 5 Jan 2009 18:00:09 GMT Message-Id: <200901051800.n05I097i016408@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: =?ISO-8859-15?Q?Dorian_B=FCttner?= Cc: Subject: Re: usb/107827: [ohci] [panic] ohci_add_done addr not found X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?ISO-8859-15?Q?Dorian_B=FCttner?= List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jan 2009 18:00:10 -0000 The following reply was made to PR usb/107827; it has been noted by GNATS. From: =?ISO-8859-15?Q?Dorian_B=FCttner?= To: bug-followup@FreeBSD.org, fstoffel@gmx.de Cc: Subject: Re: usb/107827: [ohci] [panic] ohci_add_done addr not found Date: Mon, 05 Jan 2009 17:24:59 +0000 Same thing here on an amd64 with sb600 chipset, despite the addr value in the error message might differ. First thaught was that it would relate especially to my keyboard, but the kernel crashes with nearly everything I attach to the usb ports. Leaving the ports empty during boot however will let the kernel pass through, and I can safely attach everything I want once the machine is up. Another point that drives me nuts since I totally have no idea how it fits into the scene: I have a case with front side usb connectors. These can connect to internal usb connectors via 4 pin loose wires that are marked as ground, vcc2, usb2- and usb2+. Using that connector, the kernel does not panic. Anyone an idea what could the issue?