From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Stefan Ringel <stefan.ringel@arcor.de>, linux-media@vger.kernel.org
Subject: Re: Hauppauge WinTV HVR-900H
Date: Tue, 30 Mar 2010 15:46:25 -0300 [thread overview]
Message-ID: <4BB24701.6080702@redhat.com> (raw)
In-Reply-To: <20100330181306.GA2392@joro.homelinux.org>
George Tellalov wrote:
> On Mon, Mar 29, 2010 at 08:06:40PM +0200, Stefan Ringel wrote:
>>
>> Can you scan a cannel list? If yes, then have you the right audio and video setting in vlc? And if you use Kaffeine? The log looks ok, dvb signal has it, streams and feed is on.
>>
>
> For some reason I can't get the dvbscan tool and the vlc to work. However
> kaffeine works just fine - it performed the scan and played the channels, so I
> can confirm now that dvb works.
>
> Now back to analog. Is there anything I can do to help debugging the oops?
The bug is somewhere in the code that fills the video buffers, at tm6000-video.
In order to fix, you'll likely need to have a separate machine, and use a
serial cable for console, since you may eventually convert the bug into a
Panic again and, without the console, you'll loose the error dumps.
Alternatively, you may try to start your machine on text mode and use some program
to capture the traffic, like capture-example (on v4l-utils tree).
It should be noticed that older versions of the code worked without generating
panic or oops. So, maybe digging into tm6000-video history, you may be able to
find a code that won't cause panic/oops. The problem with the old code is that sometimes
the code weren't able to produce an entire frame (lots of dropped/missed URB's).
It should also be noticed that videobuf-vmalloc suffered a few changes along the time.
So, if you backport a really old code, you'll likely need to re-apply some fixes on
the code, due to the videobuf changes.
--
Cheers,
Mauro
next prev parent reply other threads:[~2010-03-30 18:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 10:51 Hauppauge WinTV HVR-900H George Tellalov
2010-03-28 11:51 ` Aw: " Stefan Ringel
2010-03-28 12:07 ` George Tellalov
2010-03-28 12:12 ` Aw: " Stefan Ringel
2010-03-28 12:35 ` George Tellalov
2010-03-28 15:37 ` George Tellalov
2010-03-28 16:36 ` Aw: " Stefan Ringel
2010-03-28 17:57 ` George Tellalov
2010-03-28 18:44 ` Stefan Ringel
2010-03-29 16:58 ` Re: " George Tellalov
2010-03-29 18:06 ` Stefan Ringel
2010-03-30 18:13 ` George Tellalov
2010-03-30 18:46 ` Mauro Carvalho Chehab [this message]
2010-03-28 18:11 ` Stefan Ringel
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=4BB24701.6080702@redhat.com \
--to=mchehab@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=stefan.ringel@arcor.de \
/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