Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 10 Nov 2015 07:39:47 -0800
From:      Adrian Chadd <adrian@freebsd.org>
To:        Eugene Grosbein <eugen@grosbein.net>
Cc:        "freebsd-mips@freebsd.org" <freebsd-mips@freebsd.org>
Subject:   Re: USB-related problem
Message-ID:  <CAJ-VmokoTx1wNNgqaSQf0bcmPnP%2B7FON=10qMBmHF=CA=%2Bjy2Q@mail.gmail.com>
In-Reply-To: <5641A130.30703@grosbein.net>
References:  <56348063.3090508@grosbein.net> <CAJ-VmomtJ9eKfAJYfn4e2S1xWN8-YHo0M0KH-9V=VjNBf6vVVA@mail.gmail.com> <563707A0.3040700@grosbein.net> <CANCZdfrB0hkjmTU-9NzimBv=X_h-=bF0D2azBxg=9B=kmitv7Q@mail.gmail.com> <56370E1D.3040801@grosbein.net> <CAJ-Vmo=0vOAq8db_GeLWmdXr7xJdzUh44ZZJrQ9vVdpvzT9hiQ@mail.gmail.com> <563F5630.2000407@grosbein.net> <563F6F6F.1010807@grosbein.net> <CAJ-Vmo=fPSi7yZO5Xjodg8HPtTLd44Y9Y_8qg4EgTGwEpHO10A@mail.gmail.com> <563F91A8.9080702@grosbein.net> <CAJ-VmomUvoUerMS20qQsQujcjULVA=_jaLp9Mh3fU1fEpdwzZA@mail.gmail.com> <CAJ-Vmo=eUUZ928KgQbyOi8EdDFSmxhjvDOyAMvfXsqwDbO96ng@mail.gmail.com> <5640C0FD.2040803@grosbein.net> <CAJ-Vmo=6mztfvvBd91LPO5H418K8vW=%2BLk=6V5Z_y5DHu7v7HA@mail.gmail.com> <5640F315.5020303@grosbein.net> <CAJ-VmokpWM=d%2BtEFv8a8eU91UimVZ9W8da2QkKCTDjd%2B2ZM_LQ@mail.gmail.com> <56410214.3070901@grosbein.net> <CAJ-Vmo=QUUkTfQ7pvr_V%2BCQ8zQWOoqp3H8hD9LUR8C5U-5N=Ag@mail.gmail.com> <CAJ-VmomA27NcNCjx00DrZzFOU9bGYucUhbPXodH2uvNd8eJ3wg@mail.gmail.com> <5641A130.30703@grosbein.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On 9 November 2015 at 23:48, Eugene Grosbein <eugen@grosbein.net> wrote:
> On 10.11.2015 04:43, Adrian Chadd wrote:
>> Hi,
>>
>> How much C do you know? Are you able to add some debugging to
>> sched_sync() (which IIRC is the syncer thread) and work out where it's
>> getting stuck and spinning?
>>
>> (The MIPS debugger implementation unfortunately doesn't unwind through
>> the serial break, so "syncer" in backtrace looks like it started at
>> the hardware interrupt that triggered it..)
>
> I've found that "continue" ddb command does nothing for MIPS32. Why?

Someone broke it :( I've asked on freebsd-mips@ for help figuring it out.




-adrian



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokoTx1wNNgqaSQf0bcmPnP%2B7FON=10qMBmHF=CA=%2Bjy2Q>