Date: Sun, 8 Nov 2015 11:20:56 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Eugene Grosbein <eugen@grosbein.net>, Jeff Roberson <jeff@freebsd.org>, Konstantin Belousov <kib@freebsd.org>, benno <benno@freebsd.org> Cc: "freebsd-mips@freebsd.org" <freebsd-mips@freebsd.org> Subject: Re: USB-related problem Message-ID: <CAJ-VmomUvoUerMS20qQsQujcjULVA=_jaLp9Mh3fU1fEpdwzZA@mail.gmail.com> In-Reply-To: <563F91A8.9080702@grosbein.net> References: <56348063.3090508@grosbein.net> <56348239.3050701@grosbein.net> <CAJ-Vmok%2BgKXcpzpxNCBhxX8sYSh%2BQO7OaeojB4MCufO%2BA4zceg@mail.gmail.com> <563500FC.8020201@grosbein.net> <CAJ-Vmo=EpmG6OJxq_v_mqKMF48h_B3K7vKqnnaKAi3x1s-uaWQ@mail.gmail.com> <5635148B.2070307@grosbein.net> <CAJ-VmomzkG8ZB0h1Qc=Oeny2ZOzQg1UirUprM_gmMy64F5ZRYw@mail.gmail.com> <56351AA6.80903@grosbein.net> <CAJ-VmomLen5p7ELejU7QtC5CO2j8hydb_CvdOqQsfaaMAtmdkA@mail.gmail.com> <563523CA.3040207@grosbein.net> <CAJ-Vmonpd8R5C%2BNvhOGFD1okkkit990DV8c4Dm%2BLmpZ2uFfVkA@mail.gmail.com> <56367686.4090801@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>
next in thread | previous in thread | raw e-mail | index | archive | help
Sigh. I think this is more fallout from the changes to the buffer management code. I'll go add a ddb command to at least let us inspect the state of the buffer cache so we can do some further debugging. Thanks, -adrian On 8 November 2015 at 10:17, Eugene Grosbein <eugen@grosbein.net> wrote: > On 09.11.2015 00:44, Adrian Chadd wrote: >> hiya, >> >> try updating. I committed a workaround fix yesterday. > > I've updated today, its r290541. But I have custom kernel config > and custom build script, it uses nanobsd(8). > > I cannot make the kernel to panic anymore, it just freezes while writing to UFS/USB. > Userland stops responding to console and kernel stops responding to pings. > But I can break to KDB using ALT_BREAK_TO_DEBUGGER sequence: > > db> show alllock > Process v87 (pkg-static) thread 0x82c5c000 (100057) > exclusive lockmgr ufs (ufs) r = 0 (0x84cc54b4) locked @ /home/src/sys/kern/vfs_vnops.c:873 > Process 14 (syncer) thread 0x809f4360 (100036) > exclusive lockmgr bufwait (bufwait) r = 0 (0xc3036450) locked @ /home/src/sys/kern/vfs_bio.c:1454 > exclusive lockmgr bufwait (bufwait) r = 0 (0xc30366e0) locked @ /home/src/sys/kern/vfs_default.c:671 > exclusive lockmgr devfs (devfs) r = 0 (0x82c72c94) locked @ /home/src/sys/kern/vfs_subr.c:1779 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomUvoUerMS20qQsQujcjULVA=_jaLp9Mh3fU1fEpdwzZA>