From owner-freebsd-usb@FreeBSD.ORG  Fri Mar 25 01:17:24 2005
Return-Path: <owner-freebsd-usb@FreeBSD.ORG>
Delivered-To: freebsd-usb@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0313016A4CF; Fri, 25 Mar 2005 01:17:24 +0000 (GMT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id CAC2243D39; Fri, 25 Mar 2005 01:17:23 +0000 (GMT)
	(envelope-from iedowse@FreeBSD.org)
Received: from freefall.freebsd.org (iedowse@localhost [127.0.0.1])
	by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j2P1HNuY098350;
	Fri, 25 Mar 2005 01:17:23 GMT
	(envelope-from iedowse@freefall.freebsd.org)
Received: (from iedowse@localhost)
	by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j2P1HNV2098346;
	Fri, 25 Mar 2005 01:17:23 GMT
	(envelope-from iedowse)
Date: Fri, 25 Mar 2005 01:17:23 GMT
From: Ian Dowse <iedowse@FreeBSD.org>
Message-Id: <200503250117.j2P1HNV2098346@freefall.freebsd.org>
To: hnaz@buetow.org, iedowse@FreeBSD.org, freebsd-usb@FreeBSD.org
Subject: Re: usb/78371: Philips Wearable Audio Player (128) fails to attach
X-BeenThere: freebsd-usb@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: FreeBSD support for USB <freebsd-usb.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
	<mailto:freebsd-usb-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-usb>
List-Post: <mailto:freebsd-usb@freebsd.org>
List-Help: <mailto:freebsd-usb-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
	<mailto:freebsd-usb-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Mar 2005 01:17:24 -0000

Synopsis: Philips Wearable Audio Player (128) fails to attach

State-Changed-From-To: open->feedback
State-Changed-By: iedowse
State-Changed-When: Fri Mar 25 01:14:32 GMT 2005
State-Changed-Why: 

Could you supply the USB host controller and probe messages from
dmesg? If possible could you also re-test this with a recent -CURRENT?

http://www.freebsd.org/cgi/query-pr.cgi?pr=78371