Date: Sat, 3 Jan 2015 22:39:49 -0800 From: Adrian Chadd <adrian@freebsd.org> To: ticso@cicely.de Cc: Bernd Walter <ticso@cicely7.cicely.de>, "freebsd-mips@freebsd.org" <freebsd-mips@freebsd.org> Subject: Re: USB stability problem on AR9331 with stable/10 Message-ID: <CAJ-Vmo=NHV-smV-iTKJTRKL%2BcN7mT_qbfUCmDJq8h6_aXDJ9OA@mail.gmail.com> In-Reply-To: <20150103214818.GJ3265@cicely7.cicely.de> References: <20150103023713.GB3265@cicely7.cicely.de> <CAJ-VmokgPvoUftwPCg4%2B6VGkAFTz7Gi-%2BFFAQkQYO=NO2LssQg@mail.gmail.com> <20150103114302.GD3265@cicely7.cicely.de> <20150103140918.GF3265@cicely7.cicely.de> <20150103214818.GJ3265@cicely7.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3 January 2015 at 13:48, Bernd Walter <ticso@cicely7.cicely.de> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=NHV-smV-iTKJTRKL%2BcN7mT_qbfUCmDJq8h6_aXDJ9OA>