Date: Wed, 16 Feb 2011 12:08:30 -0500 From: Andrew Boyer <aboyer@averesystems.com> To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Cc: Eugene Grosbein <egrosbein@rdtc.ru>, Mike Tancsa <mike@sentex.net> Subject: Re: About "panic: bufwrite: buffer is not busy???" Message-ID: <4FD1B1C3-08A7-4F48-A30A-DE5A8F3D3834@averesystems.com> In-Reply-To: <4D4A38FD.7000607@rdtc.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> <4D4A38FD.7000607@rdtc.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Moving this to -current and -stable and following up... Something is broken with coredumps on stable/8 amd64. I tried a vanilla = 8.2-RC3 and yesterday's csup of stable/8; neither can dump a core with = 'sysctl debug.kdb.panic=3D1'. For the 8.2-RC3 / amd64 / GENERIC install, I used the memstick image, = installed on ad7 (a 250GB SATA drive), used the default partition map, = and set dumpdev to AUTO. I added enough tracing to show that the second panic is due to the = syncer process flushing buffers to the other filesystems in parallel = with the dump. I've seen this panic and a similar one 'buffer not = locked' coming from ffs_write(). One time out of about 30 the core ran = to completion, but slowly (~1MB/sec). Other times the dump just locks = up completely with no other output. Does anyone know what might have changed to expose this problem? I don't ever see it under 7.1. Thanks, Andrew On Feb 3, 2011, at 12:11 AM, Eugene Grosbein wrote: > On 02.02.2011 00:50, Gleb Smirnoff wrote: >=20 >> 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 =3D 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. >=20 > I see Mike Tancsa's box has "bufwrite: buffer is not busy???" problem = too. > Has anyone a thought how to fix generation of crashdumps? >=20 > Eugene Grosbein >=20 >=20 > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" -------------------------------------------------- Andrew Boyer aboyer@averesystems.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FD1B1C3-08A7-4F48-A30A-DE5A8F3D3834>