Date: Wed, 25 Apr 2007 22:20:25 +0400 (MSD) From: Oleg Derevenetz <oleg@vsi.ru> To: Kris Kennaway <kris@obsecurity.org> Cc: LI Xin <delphij@delphij.net>, Kris Kennaway <kris@obsecurity.org>, freebsd-stable@freebsd.org, Oleg Derevenetz <oleg@vsi.ru> Subject: Re: How to report bugs (Re: 6.2-STABLE deadlock?) Message-ID: <1177525225.462f9be9adad8@webmail.vsi.ru> In-Reply-To: <20070425180843.GA72881@xor.obsecurity.org> References: <20070313140848.GA89182@steerpike.hanley.stade.co.uk> <20070423025631.GA33256@steerpike.hanley.stade.co.uk> <20070423113912.GE2052@deviant.kiev.zoral.com.ua> <462DDB4D.8080507@delphij.net> <1177442585.462e5919c71f0@webmail.vsi.ru> <462EC294.3040001@delphij.net> <20070425035316.GB44054@xor.obsecurity.org> <1177488860.462f0ddc6ce8c@webmail.vsi.ru> <20070425180843.GA72881@xor.obsecurity.org>
index | next in thread | previous in thread | raw e-mail
Цитирую Kris Kennaway <kris@obsecurity.org>: > On Wed, Apr 25, 2007 at 12:14:20PM +0400, Oleg Derevenetz wrote: > > > > Until you (or a developer) have analyzed the resulting information, > > > you cannot definitively determine whether or not your problem is > the > > > same as a given random other problem, and you may just confuse the > > > issue by making claims of similarity when you are really reporting > a > > > completely separate problem. > > > > Not all people can do deadlock debugging, though. In my case turning > on > > INVARIANTS and WITNESS leads to unacceptable performance penalty due > to heavily > > loaded server. So I can only describe my case, actions and result > without > > providing any debug information. > > But you can still do *some* things, e.g. backtraces and/or a coredump: > every little bit helps. > > Ultimately, though, you have to understand and accept that the less > information you provide, the less chance there is that a developer > will be able to track down your problem. In fact a developer may have > to effectively ignore your problem report altogether, because of what > I explained about "symptoms" usually not being enough to tell one bug > from another. > > In general, when you encounter a bug in FreeBSD, you have a little bit > of work to do on your side before we can start doing the rest. I > understand that you may not be in a position to do that work, but that > means you also need to understand that we can't do it either. In fact, I solved (or workarounded) this problem for me, so in this thread I provide my workaround as possible workaround for users that experiences the same problem. This only hint for them, and not a bugreport for you. I could not provide a full (or only partial) debug information because I will not back out cvsuped sources, will not replace unionfs with nullfs again and will not wait week or more for another stuck.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1177525225.462f9be9adad8>