Date: Tue, 18 Aug 2015 14:46:10 +0200 From: Hans Petter Selasky <hps@selasky.org> To: Svatopluk Kraus <onwahe@gmail.com> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: DWC OTG TX path optimisation for 11-current Message-ID: <55D32912.1070707@selasky.org> In-Reply-To: <CAFHCsPXbBSpkDtggN%2BiBm=vpYwOTpi7nH=Z0G4RiyvoVXuw7_g@mail.gmail.com> References: <55A7D8CE.4020809@selasky.org> <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> <55B8F5EC.2050908@selasky.org> <46ad096c958.1a82a175@mail.schwarzes.net> <55B9C3E2.5040501@selasky.org> <46ae815c7c3.447237c8@mail.schwarzes.net> <46aece00b53.3c1cdc1f@mail.schwarzes.net> <55BB2A5F.9000502@selasky.org> <46baa16c4ce.6efd29ef@mail.schwarzes.net> <55CF31A1.5080205@selasky.org> <CAFHCsPUKwNLkeSPSHHUs=vwFFAnBd_9HRPxaS6tEC0cR3y_C6Q@mail.gmail.com> <55D31D11.3050509@selasky.org> <CAFHCsPXbBSpkDtggN%2BiBm=vpYwOTpi7nH=Z0G4RiyvoVXuw7_g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/18/15 14:31, Svatopluk Kraus wrote: > On Tue, Aug 18, 2015 at 1:54 PM, Hans Petter Selasky <hps@selasky.org> wrote: >> Hi, >> >> On 08/18/15 13:22, Svatopluk Kraus wrote: >>> >>> Do I understand it well that you are not able to trigger the problem? >> >> >> Maybe I haven't been trying hard enough. I've been using a kernel built from >> "projects/hps_head" which I just updated to include the latest DWC OTG >> patches, instead of "head". There was today a timer subsystem fix, not sure >> if it makes any difference: >> >> https://svnweb.freebsd.org/changeset/base/286880 >> >> I will try to buildworld from an external USB disk later today and see what >> happens. >> >>> >>> and still the system response time is terrible. >> >> >> If you can do: >> >> usbconfig -d 0.1 set_config 255 >> >> And verify that the IRQ rate goes to zero for DWC OTG, then we maybe could >> rule out USB. >> > > Note that my root filesystem was on usb disk. > Is the console still not responding properly after this command? --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55D32912.1070707>