Date: Fri, 26 Aug 2011 00:53:49 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Charlie Martin <crmartin@sgi.com> Cc: freebsd-hackers@freebsd.org Subject: Re: Where to ask about a 7.2 bug, and debugging sys/queue.h errors Message-ID: <20110825215348.GW17489@deviant.kiev.zoral.com.ua> In-Reply-To: <4E56BB99.6030706@sgi.com> References: <4E56BB99.6030706@sgi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Thu, Aug 25, 2011 at 03:16:09PM -0600, Charlie Martin wrote: > We're having a crash in some internal code running on FreeBSD 7.2 > (specifically 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE and yeah, I know > it's quite a bit behind) in which after 18-30 hours of running load > tests, the code panics with: > > panic: Bad link elm 0xffffff0044c09600 next->prev != elm > cpuid = 0 > KDB: stack backtrace: > db_trace_self_wrapper() at 0xffffffff8019119a = db_trace_self_wrapper+0x2a > panic() at 0xffffffff80307c72 = panic+0x182 > devfs_populate_loop() at 0xffffffff802a43a8 = devfs_populate_loop+0x548 > > > First question: where's the most appropriate place to ask about this > kind of bug on a back version. It is fine to ask there. > > Second: does this remind anyone of any bugs? Googling came up with a > few somewhat similar things but hasn't provided much insight so far. In 99% of the cases, it means that you forgot to dev_ref() some cdev. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk5WxGwACgkQC3+MBN1Mb4iOvgCg5v6t/Xmr7axl/G6cCBPFTD9k IzgAoKbFdo3Nj5cNcJP9XnX/wnQTbnNW =1nG/ -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110825215348.GW17489>