From: Willy Tarreau <willy@w.ods.org>
To: Folkert van Heusden <folkert@vanheusden.com>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
linux-kernel@vger.kernel.org, lnx4us@gmail.com
Subject: Re: bug reports ignored?
Date: Thu, 5 Jan 2006 22:17:15 +0100 [thread overview]
Message-ID: <20060105211715.GC7142@w.ods.org> (raw)
In-Reply-To: <20060105185319.GB10923@vanheusden.com>
On Thu, Jan 05, 2006 at 07:53:20PM +0100, Folkert van Heusden wrote:
> > > Last couple of weeks I sent 2 bug-reports. They seem to be ignored. I was
> > > wondering: what is missing in them? Am I sending them to the incorrect
> > > address? One I also put into bugzilla (no reactions either).
> > Perhaps you could let us know the subjects & dates of those two
> > previous mails so they are easier to locate in the archives?
>
> 20051219190137.GA13923@vanheusden.com
> Mon, 19 Dec 2005 20:01:47 +0100
> [2.6.13.3] occasional oops mostly in iget_locked
>
> It seems that those oopses in iget_locked are gone since I ran 2.6.14.4
> and currently run 2.6.15.
>
>
> Other message:
> 20060103210252.GA2043@vanheusden.com
> Tue, 3 Jan 2006 22:03:36 +0100
> [2.6.15] reproducable hang
>
> this one still happens. System loses total network connectivity. When I
> dial the system (by phone), asterisk (the software pabx) picks up the
> phone and plays a sample, then it becomes mute. After that, the system
> doesn't respond to anything at all. Even sysreq+t is ignored.
> The last message on the console is:
> eth1: transmit error tx status register 82
Then you're in the situation where you have to narrow the bug down to
something more reproduceable for other people. Possibly very few people
on the list have 2.6.15 + asterisk + a sample to play + etc...
Try to strace asterisk when this happens for instance, try to remove
a lot of loaded modules and configured options from your system, then
you will finally reach a case where you can simply reproduce it with
a 10-line C prog without a complex setup. With those info, it will be
too complex and boring to try to reproduce your problem on any
developer's system.
> > - Sometimes bugs are reported with a *demand* that it be fixed *right
> > now* or with other abusive language towards developers in the email.
> > Such reports are usually ignored or, if responded to, don't get very
> > positive replies.
>
> Haha no I did not do that :-)
>
>
> Folkert van Heusden
Willy
next prev parent reply other threads:[~2006-01-05 21:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 16:08 bug reports ignored? Folkert van Heusden
2006-01-05 16:52 ` Jesper Juhl
2006-01-05 18:53 ` Folkert van Heusden
2006-01-05 21:17 ` Willy Tarreau [this message]
2006-01-05 21:41 ` Folkert van Heusden
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060105211715.GC7142@w.ods.org \
--to=willy@w.ods.org \
--cc=folkert@vanheusden.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lnx4us@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox