Date: Thu, 03 Feb 2011 11:11:25 +0600 From: Eugene Grosbein <egrosbein@rdtc.ru> To: Gleb Smirnoff <glebius@freebsd.org> Cc: freebsd-net@freebsd.org, John Baldwin <jhb@freebsd.org> Subject: About "panic: bufwrite: buffer is not busy???" Message-ID: <4D4A38FD.7000607@rdtc.ru> In-Reply-To: <20110201185026.GB62007@glebius.int.ru> References: <4D3011DB.9050900@frasunek.com> <4D30458D.30007@sentex.net> <4D309983.70709@rdtc.ru> <201101141437.55421.jhb@freebsd.org> <4D46575A.802@rdtc.ru> <4D4670C2.4050500@freebsd.org> <4D48513C.40503@rdtc.ru> <20110201185026.GB62007@glebius.int.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02.02.2011 00:50, Gleb Smirnoff wrote: > E> Uptime: 8h3m51s > E> Dumping 4087 MB (3 chunks) > E> chunk 0: 1MB (150 pages) ... ok > E> chunk 1: 3575MB (915088 pages) 3559 3543panic: bufwrite: buffer is not busy??? > E> cpuid = 3 > E> Uptime: 8h3m52s > E> Automatic reboot in 15 seconds - press a key on the console to abort > Can you add KDB_TRACE option to kernel? Your boxes for some reason can't > dump core, but with this option we will have at least trace. I see Mike Tancsa's box has "bufwrite: buffer is not busy???" problem too. Has anyone a thought how to fix generation of crashdumps? Eugene Grosbein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D4A38FD.7000607>