Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 30 Jul 2015 11:43:53 +0200
From:      Hans Petter Selasky <hps@selasky.org>
To:        Svatopluk Kraus <onwahe@gmail.com>,  John-Mark Gurney <jmg@funkthat.com>
Cc:        "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>
Subject:   Re: [RPI-B] [HEADS UP] DWC OTG TX path optimisation for 11-current
Message-ID:  <55B9F1D9.5070503@selasky.org>
In-Reply-To: <CAFHCsPWEN7J=h-ZGYzW-OGajFV4UOcpumHp=JRnYOiz3GQ-OJw@mail.gmail.com>
References:  <55A7D8CE.4020809@selasky.org>	<CAHNYxxMp9jGDbV-5=-cE6daR-O3eN5pdvO1s-=QfX=A9XYqYmA@mail.gmail.com>	<55B23276.8090703@selasky.org>	<CAHNYxxNc9uB62hHEv1PM9PcsGgUs=zsvNgatqLD0p%2BiiDA3Aiw@mail.gmail.com>	<55B73113.2020308@selasky.org>	<CAFHCsPVaPZpqXLS7OApa=Xz5VLnLjVpV5dYV8Pn2uHh1Lcz7Tg@mail.gmail.com>	<55B8AB76.7030603@selasky.org>	<CAFHCsPUMaYEwJsaGUFuw9yZi_5bmraSBsOYpRWvSeuebpXBJUA@mail.gmail.com>	<55B8B297.1010008@selasky.org>	<CAFHCsPVGLs8j6LAV%2Bg4rP_ueTOd8pUOupYFGvmgC3XGcJC720Q@mail.gmail.com>	<20150729154516.GH78154@funkthat.com> <CAFHCsPWEN7J=h-ZGYzW-OGajFV4UOcpumHp=JRnYOiz3GQ-OJw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 07/30/15 11:32, Svatopluk Kraus wrote:
> I do not think that it's problem of smsc driver. The messages are just
> indicator that something else (it's most propably usb disk related) is
> generating big load so other clients on usb are restrained. However,
> when it happens, this big load does not stop even if system is "idle",
> so it looks that it's generated "internally" somewhere. For example,
> it could be a try to recover from some "problems" which never
> recovers.

Hi,

If other USB requests continue working while this is happening, it is a 
bug in the SMSC driver. I see at least the miibus read/write access is 
not sequential. If multiple threads try to access the miibus via 
ifconfig IOCTLs for example, there can be a race which the driver 
doesn't handle.

BTW: "usbdump" will tell the actual USB error code, if any. If the USB 
hardware is responding correctly, it is for sure a driver bug. Else I'll 
investigate.

--HPS



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55B9F1D9.5070503>