How to report bugs (Re: 6.2-STABLE deadlock?)
kris at obsecurity.org
Thu Apr 26 01:05:35 UTC 2007
On Wed, Apr 25, 2007 at 10:20:25PM +0400, Oleg Derevenetz wrote:
> ??????? Kris Kennaway <kris at 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.
OK. FYI I use nullfs on a few dozen heavily loaded machines without
issue for the past year or so, so if you are seeing a nullfs issue it
is probably an obscure one.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20070426/6312f111/attachment.pgp
More information about the freebsd-stable