USB-related problem

Adrian Chadd adrian at freebsd.org
Sun Nov 8 19:20:57 UTC 2015


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 at 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
>


More information about the freebsd-mips mailing list