From owner-freebsd-mips@FreeBSD.ORG Sun Jan 4 06:39:51 2015 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 47D61A24 for ; Sun, 4 Jan 2015 06:39:51 +0000 (UTC) Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CC8633FF4 for ; Sun, 4 Jan 2015 06:39:50 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id n3so1494077wiv.11 for ; Sat, 03 Jan 2015 22:39:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=PHT4tVwzEE/JmPi1iEnXgjJQAMdxWKFiTtH/8Gv0dcE=; b=pENrrpRu6orTmr0rA/vp7QC2P/H0HUdBez0p74dKCCHf1EM/aS12KbzoJEGh2Zllmy IKH+0omWkz1nG9tfdOK+ffWf2l1jgFBpQUl3/QP2g95m8L+7wmyhDefBy1ncsZWskrQK N4mMPmaJDei2th0Ztrvhq6w8pLQi1ZnNZ2c8dIUgsyuu3Ld0ZW3uU0IvKTIXO3mR4XXt ouKdkAdqzxdPb8RgbKbqFVtZGAvABfew26hGs6XI2U38ZyjCpodzB6fjGMmb2N18zxxI aYEIQvKJC2vcxWKZdT4xCGyauiKGVZQq7I30+Qw4VEDxKVK0wpAHN0KajrinN6tCqdb7 XKgg== MIME-Version: 1.0 X-Received: by 10.194.108.9 with SMTP id hg9mr163364438wjb.68.1420353589285; Sat, 03 Jan 2015 22:39:49 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.41.136 with HTTP; Sat, 3 Jan 2015 22:39:49 -0800 (PST) In-Reply-To: <20150103214818.GJ3265@cicely7.cicely.de> References: <20150103023713.GB3265@cicely7.cicely.de> <20150103114302.GD3265@cicely7.cicely.de> <20150103140918.GF3265@cicely7.cicely.de> <20150103214818.GJ3265@cicely7.cicely.de> Date: Sat, 3 Jan 2015 22:39:49 -0800 X-Google-Sender-Auth: tou9BfrHQDJdd7j5gj0apaoDYuA Message-ID: Subject: Re: USB stability problem on AR9331 with stable/10 From: Adrian Chadd To: ticso@cicely.de Content-Type: text/plain; charset=UTF-8 Cc: Bernd Walter , "freebsd-mips@freebsd.org" X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jan 2015 06:39:51 -0000 On 3 January 2015 at 13:48, Bernd Walter wrote: > On Sat, Jan 03, 2015 at 03:09:18PM +0100, Bernd Walter wrote: >> On Sat, Jan 03, 2015 at 12:43:02PM +0100, Bernd Walter wrote: >> > On Sat, Jan 03, 2015 at 12:54:58AM -0800, Adrian Chadd wrote: >> > > Hi! >> > > >> > > Can you try FreeBSD-HEAD? See if it's more stable? >> > > >> > > There may be some USB PLL related stuff that isn't in stable/10. >> > > (I remember general USB instability on the AR933x chips that was >> > > finally resolved in ath9k/linux and I /think/ I ported it all to >> > > FreeBSD-HEAD.) >> > >> > Ah - great. >> > PLL makes somewhat sense, because in some cases the USB device even >> > seem to have crashed and needed a power cycle. >> > Unfortunately head doesn't compile for me right now because of missing >> > dnstap/dnstap_config.h in libunbound, but I will retry later or go back >> > a few revs. >> >> Didn't get very far: >> ELF ldconfig path: /lib /usr/lib /usr/lib/compat >> Clearing /tmp (X related). >> Updating motd:. >> Mounting late file systems:. >> Starting ntpd. >> Starting rtadvd. >> swapon: mdconfig (attach) error: md99 on file=/home/swap0 >> Generating RSA1 host key. >> 2048 9c:59:9c:a9:83:bf:d2:c0:b6:31:b3:dc:a0:4b:00:2a root@apx2.cicely.de (RSA1) >> Generating RSA host key. >> 2048 ec:5a:29:76:7d:4a:8d:8e:f0:ca:06:d1:e2:a6:78:af root@apx2.cicely.de (RSA) >> Generating DSA host key. >> 1024 c3:f8:2d:98:0c:a1:5b:40:f8:2c:98:be:dd:53:3f:5f root@apx2.cicely.de (DSA) >> Generating ECDSA host key. >> 256 b7:75:c3:53:76:cd:77:22:a5:95:be:36:39:a8:97:6c root@apx2.cicely.de (ECDSA) >> Generating ED25519 host key. >> 256 0d:ff:70:65:f5:69:43:26:84:f2:22:d2:52:16:ec:bf root@apx2.cicely.de (ED25519) >> Performing sanity check on sshd configuration. >> Starting sshd. >> Starting sendmail_submit. >> (da0:umass-sim0:0:0:0): . CDB: 28 00 00 19 5a c0 00 00 50 00 >> (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error >> (da0:umass-sim0:0:0:0): Retrying command >> (da0:umass-sim0:0:0:0): . CDB: 28 00 00 19 5a c0 00 00 50 00 >> (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error >> (da0:umass-sim0:0:0:0): Retrying command >> (da0:umass-sim0:0:0:0): . CDB: 28 00 00 19 5a c0 00 00 50 00 >> (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error >> (da0:umass-sim0:0:0:0): Retrying command >> (da0:umass-sim0:0:0:0): . CDB: 28 00 00 19 5a c0 00 00 50 00 >> (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error >> (da0:umass-sim0:0:0:0): Retrying command >> (da0:umass-sim0:0:0:0): . CDB: 28 00 00 19 5a c0 00 00 50 00 >> (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error >> (da0:umass-sim0:0:0:0): Error 5, Retries exhausted >> g_vfs_done():da0a[WRITE(offset=3988025344, length=4096)]error = 5 >> g_vfs_done():da0a[WRITE(offset=3988492288, length=4096)]error = 5 >> g_vfs_done():da0a[WRITE(offset=3988496384, length=4096)]error = 5 >> g_vfs_done():da0a[WRITE(offset=3988500480, length=4096)]error = 5 >> g_vfs_done():da0a[WRITE(offset=3988504576, length=4096)]error = 5 >> g_vfs_done():da0a[WRITE(offset=3988594688, length=4096)]error = 5 >> g_vfs_done():da0a[READ(offset=4651474944, length=57344)]error = 5 >> g_vfs_done():da0a[WRITE(offset=6618730496, length=4096)]error = 5 >> g_vfs_done():da0a[WRITE(offset=6625198080, length=12288)]error = 5 >> g_vfs_done():da0a[WRITE(offset=6625234944, length=4096)]error = 5 >> g_vfs_done():da0a[READ(offset=850747392, length=40960)]error = 5 >> vnode_pager_generic_getpages_done: I/O read error 5 >> vm_fault: pager read error, pid 768 (sshd) >> vnode_pager_generic_getpages_done: I/O read error 5 >> >> I will swap for another board now. >> Reason is that I have one board running on a OS version, which is about >> 1.5 years old and it shows this problem only from time to time. >> I even use it to copy the rootfs from nfs to the stick because of the >> endian issue with mips. >> It is very hard to say when this happens, because copying usually works, >> but once you put some additional load, like compiling, or in this case >> creating host keys. >> Now this board with recent stable/current shows this problem extremly >> often. >> I want to rule out that I put a broken board into my test mix, because >> it was a new one. > > Ok, I can't tell for sure if there is some hardware related influence, > but I'd tested 3 Dragino MS14-P (likely same batch) and retested with one > Carambola 2, which all showed the problem sooner or later. Hm, I wonder which particular AR933x revision they're using. Are you providing them enough power? -adrian