Date: Fri, 20 Nov 2015 02:37:31 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: Adrian Chadd <adrian@freebsd.org> Cc: benno <benno@freebsd.org>, Jeff Roberson <jeff@freebsd.org>, Konstantin Belousov <kib@freebsd.org>, "freebsd-mips@freebsd.org" <freebsd-mips@freebsd.org> Subject: Re: USB-related problem Message-ID: <564E24FB.5000705@grosbein.net> In-Reply-To: <CAJ-VmonKMssNCs0v%2BUr67%2BLiifF_AJipVjTEW5%2BPi07h=BrHFA@mail.gmail.com> References: <56348063.3090508@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> <564231DE.7090308@grosbein.net> <56423D82.5030203@grosbein.net> <CAJ-VmomOeSyQGxKPvaa9TiBENCcdvTJiTLvSi2FfbCH9c6CGAA@mail.gmail.com> <564512A8.1000006@grosbein.net> <CAJ-VmomByUr3-XgqYPg0VoxirnUS%2BBc6-zdxCx6-Am8P4iBVUw@mail.gmail.com> <564AE210.3050804@grosbein.net> <CAJ-VmonKMssNCs0v%2BUr67%2BLiifF_AJipVjTEW5%2BPi07h=BrHFA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 20.11.2015 02:05, Adrian Chadd wrote: > On 17 November 2015 at 00:15, Eugene Grosbein <eugen@grosbein.net> wrote: >> On 17.11.2015 14:44, Adrian Chadd wrote: >>> hiya, >>> >>> any updates? I caan't trigger this one myself :( >> >> No updates. Yesterday I've spent some time to discover if KASSERT is guilty >> but finally found sysctl debug.kassert.kassert and it works as expected, no hangs. >> Working backtrace in KDB would be invaluable. >> > > Yeah. When it happens, do "show registers" ? I'd like to see if the > registers show anything useful. Just reproduced the deadlock: [4/17] Extracting pcre-8.37_4: 24%KDB: enter: Break to debugger [ thread pid 14 tid 100036 ] Stopped at kdb_enter+0x4c: lui at,0x8044 db> show registers at 0x80440000 cc_cpu+0xa0c0 v0 0x1e _DYNAMIC_LINKING+0x1d v1 0x1e _DYNAMIC_LINKING+0x1d a0 0 a1 0x4 _DYNAMIC_LINKING+0x3 a2 0x803756b8 a3 0x12f _DYNAMIC_LINKING+0x12e t0 0x8046afec t1 0 t2 0 t3 0 t4 0 t5 0 t6 0 t7 0 s0 0x80362bb8 mips_event_codes_size+0x7638 s1 0x8058cc00 s2 0x40000 s3 0x8058cc00 s4 0x803ec4dc uart_ipend_desc s5 0 s6 0x803ec500 uart_receive_desc s7 0x8058cc88 t8 0x18006 t9 0x7e2290 k0 0x805d4390 k1 0x8031a2a4 spinlock_exit+0x1c gp 0x80421c80 _gp sp 0xc3adb8e8 s8 0x803ec4b8 uart_flush_desc ra 0x801be69c kdb_enter+0x40 sr 0xec02 _DYNAMIC_LINKING+0xec01 lo 0x1 _DYNAMIC_LINKING hi 0x5135 _DYNAMIC_LINKING+0x5134 bad 0xc083d950 cs 0x4000c024 pc 0x801be6a8 kdb_enter+0x4c kdb_enter+0x4c: lui at,0x8044 db>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?564E24FB.5000705>