From owner-freebsd-arm@FreeBSD.ORG Fri May 9 15:06:37 2014 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0B578598; Fri, 9 May 2014 15:06:37 +0000 (UTC) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B8C80F03; Fri, 9 May 2014 15:06:36 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1WimNY-000KID-UJ; Fri, 09 May 2014 15:06:29 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id s49F6Q94030467; Fri, 9 May 2014 09:06:26 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX191hyW7KEpDlLyNrT+jsF16 Subject: Re: USB isochronous traffic with Rasberry Pi [WAS: Re: USB audio device on Raspberry Pi] From: Ian Lepore To: Hans Petter Selasky In-Reply-To: <536CE5E9.8020408@selasky.org> References: <20140425154430.GA76168@utility-01.thismonkey.com> <535A8AEA.1000100@selasky.org> <20140425204134.GA458@cicely7.cicely.de> <20140430091411.GA45015@utility-01.thismonkey.com> <5360C0A7.9010407@selasky.org> <1398867266.22079.51.camel@revolution.hippie.lan> <5362638B.1080104@selasky.org> <5363C133.2000304@selasky.org> <53677CB8.5000800@selasky.org> <1399303695.22079.239.camel@revolution.hippie.lan> <1399304157.22079.243.camel@revolution.hippie.lan> <5368A93D.3070608@selasky.org> <5368AC03.8080401@selasky.org> <536CE5E9.8020408@selasky.org> Content-Type: text/plain; charset="us-ascii" Date: Fri, 09 May 2014 09:06:26 -0600 Message-ID: <1399647986.22079.367.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 May 2014 15:06:37 -0000 On Fri, 2014-05-09 at 16:27 +0200, Hans Petter Selasky wrote: > Hi, > > I've tried to dig through the DWC OTG controller to make it work better > in host mode. Can you test the latest code after: > > http://svnweb.freebsd.org/changeset/base/265777 > > And report any errors/regression issues when using USB devices? > > --HPS After updating to r265780 and building clean, I consitantly get this when the rpi boots: KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2014 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 11.0-CURRENT #0 r265780M: Fri May 9 08:44:47 MDT 2014 ilepore@revolution.hippie.lan:/local/build/staging/freebsd/rpi/obj/arm.armv6/local/build/staging/freebsd/rpi/src/sys/RPI-B-serial arm gcc version 4.2.1 20070831 patched [FreeBSD] CPU: ARM1176JZ-S rev 7 (ARM11J core) Supported features: ARM_ISA THUMB2 JAZELLE ARMv4 Security_Ext WB enabled LABT branch prediction enabled 16KB/32B 4-way instruction cache 16KB/32B 4-way write-back-locking-C data cache real memory = 134213632 (127 MB) avail memory = 123858944 (118 MB) random device not loaded; using insecure entropy random: initialized ofwbus0: simplebus0: mem 0x20000000-0x20ffffff on ofwbus0 intc0: mem 0xb200-0xb3ff on simplebus0 systimer0: mem 0x3000-0x3fff irq 8,9,10,11 on simplebus0 Event timer "BCM2835 Event Timer 3" frequency 1000000 Hz quality 1000 Timecounter "BCM2835 Timecounter" frequency 1000000 Hz quality 1000 bcmwd0: mem 0x10001c-0x100027 on simplebus0 gpio0: mem 0x200000-0x2000af irq 57,59,58,60 on simplebus0 gpio0: read-only pins: 46,47,48,49,50,51,52,53. gpio0: reserved pins: 48,49,50,51,52,53. gpioc0: on gpio0 gpiobus0: on gpio0 gpioled0: at pin(s) 16 on gpiobus0 bcm_dma0: mem 0x7000-0x7fff,0xe05000-0xe05fff irq 24,25,26,27,28,29,30,31,32,33,34,35,36 on simplebus0 mbox0: mem 0xb880-0xb8bf irq 1 on simplebus0 sdhci_bcm0: mem 0x300000-0x3000ff irq 70 on simplebus0 mmc0: on sdhci_bcm0 uart0: mem 0x201000-0x201fff irq 65 on simplebus0 uart0: console (115200,n,8,1) dwcotg0: mem 0x980000-0x99ffff irq 17 on simplebus0 usbus0 on dwcotg0 simplebus1: on ofwbus0 simplebus1: could not get ranges device_attach: simplebus1 attach returned 6 Timecounters tick every 10.000 msec usbus0: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 mmcsd0: 8GB at mmc0 50.0MHz/4bit/65535-block bootpc_init: wired to interface 'ue0' mmcsd0: Error indicated: 2 Bad CRC uhub0: 1 port with 1 removable, self powered ugen0.2: at usbus0 uhub1: on usbus0 uhub1: MTT enabled uhub1: 3 ports with 2 removable, self powered random: unblocking device. ugen0.3: at usbus0 smsc0: on usbus0 uhub_reattach_port: device problem (USB_ERR_STALLED), disabling port 3 smsc0: chip 0xec00, rev. 0002 miibus0: on smsc0 ukphy0: PHY 1 on miibus0 ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ue0: on smsc0 ue0: Ethernet address: 1e:b3:27:cd:38:f3 smsc0: chip 0xec00, rev. 0002 ue0: link state changed to DOWN Sending DHCP Discover packet from interface ue0 (1e:b3:27:cd:38:f3) ue0: link state changed to UP Received DHCP Offer packet on ue0 from 0.0.0.0 (accepted) Sending DHCP Request packet from interface ue0 (1e:b3:27:cd:38:f3) Received DHCP Ack packet on ue0 from 0.0.0.0 (accepted) ue0 at 172.22.42.71 server 0.0.0.0 subnet mask 255.255.255.0 router 172.22.42.254 rootfs 172.22.42.240:/rpi Adjusted interface ue0 Trying to mount root from nfs:172.22.42.240:/rpi [ro,noatime]... NFS ROOT: 172.22.42.240:/rpi warning: no time-of-day clock registered, system time will not be set accurately warning: no time-of-day clock registered, system time will not be set accurately smsc0: error: usb error on tx: USB_ERR_IOERROR smsc0: warning: bulk read error, USB_ERR_IOERROR smsc0: warning: Failed to read register 0x114 smsc0: warning: MII is busy smsc0: warning: Failed to read register 0x114 smsc0: warning: MII is busy smsc0: warning: Failed to read register 0x114 smsc0: warning: MII is busy smsc0: warning: Failed to read register 0x114 smsc0: warning: MII is busy smsc0: warning: Failed to read register 0x114 smsc0: warning: MII is busy ue0: link state changed to DOWN smsc0: warning: Failed to read register 0x114 smsc0: warning: MII is busy smsc0: warning: Failed to read register 0x114 smsc0: warning: MII is busy smsc0: warning: Failed to read register 0x114 smsc0: warning: MII is busy smsc0: at uhub1, port 1, addr 3 (disconnected) smsc0: warning: Failed to read register 0x114 smsc0: warning: MII is busy ukphy0: detached miibus0: detached smsc0: on usbus0 smsc0: chip 0xec00, rev. 0002 miibus0: on smsc0 ukphy0: PHY 1 on miibus0 ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ue0: on smsc0 ue0: Ethernet address: be:a4:34:6d:c5:2a newnfs server 172.22.42.240:/rpi: not responding newnfs server 172.22.42.240:/rpi: not responding newnfs server 172.22.42.240:/rpi: not responding It's interesting that it worked well enough to mount the nfsroot filesystem, then went bad after that. -- Ian