From: Antti Palosaari <crope@iki.fi>
To: Marx <acc.for.news@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: How to make bug report
Date: Wed, 20 Jun 2012 19:42:35 +0300 [thread overview]
Message-ID: <4FE1FD7B.4050108@iki.fi> (raw)
In-Reply-To: <p4v2b9-nd7.ln1@wuwek.kopernik.gliwice.pl>
On 06/18/2012 09:40 AM, Marx wrote:
> Hello
> I have four DVB cards:
> DVB-S2:
> -Pinnacle PCTV SAT HDTV 452E PRO USB (main kernel support)
> -Terratec Cinergy S2 USB HD v.2
> -Prof Revolution DVB-S2 8000 PCIe
> DVB-T:
> -AF9015 noname USB (main kernel support)
>
> on AMD Brazos platform (Asrock E350M1) with Debian (lately with 3.4
> kernel).
>
> While I could be able to make all of them working via different drivers
> (media-build, patches, vendor drivers, Igor Liplianin's repo, yavdr dkms
> package etc) none of this card works stable (unlike Twinhan PCI I had
> previously). Prof hangs system, Pinnacle doesn't work with DVB-S2,
> Terratec records streams partially unplayable, AF9015 stops working
> after and hour or so etc. Often I see errors of I2C subsystem.
As author of the AF9015 I would like to see some of those errors. And
your driver version. Use latest v4l-dvb if possible as I have changed it
very much recently.
> While I'm in process of testing it on different hardware (laptop) I
> would like to know if it's good place to write about dvb drivers bugs.
> Or maybe should I write directly to developer? or write bugs in
> Debian/kernel bugzilla or sth similair?
> How to properly report bugs? What kernel should I use, which driverset?
> What logs to attach (kernel.log)? how to enable debug options (if needed)?
Maybe best to contact driver author directly and CC this mailing list.
> I think it's rather unusual all of cards doesn't work, so I suspect that
> there can be something wrong with my system. Maybe you, as skilled
> developers, can direct me what can be wrong, what can I test?
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2012-06-20 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 6:40 How to make bug report Marx
2012-06-20 16:42 ` Antti Palosaari [this message]
2012-06-22 5:03 ` Marx
2012-06-22 5:08 ` Marx
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=4FE1FD7B.4050108@iki.fi \
--to=crope@iki.fi \
--cc=acc.for.news@gmail.com \
--cc=linux-media@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.