Bug 808997

Summary: Hauppauge WinTV-HVR4000 DVB-S/S2/T/Hybrid no longer works properly with kernel 3.3
Product: [Fedora] Fedora Reporter: thestonewell
Component: kernelAssignee: Mauro Carvalho Chehab <mchehab>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 16CC: gansalmon, hektor, itamar, jonathan, kernel-maint, lwang, madhu.chinakonda, shwetha.h.panduranga
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-09 13:32:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description thestonewell 2012-04-02 07:52:18 UTC
Description of problem:

I have got 2 Hauppauge WinTV-HVR4000 DVB-S/S2/T/Hybrid cards in my
system. They worked perfectly fine with kernel 3.2 (e.g. the last
Fedora 16 kernel that worked is 3.2.10-3.fc16.x86_64).

As soon as Fedora went kernel 3.3 (kernel 3.3.0-4.fc16.x86_64) the
problems started. The cards are still recognized and you can tune
them. But trying to watch any DVB-S (or DVB-S2) channel just results
in block artefacts, loss of audio-video sychronization etc. The only
thing /var/log/messages or dmesg tells me is:


cx8802_start_dma() Failed. Unsupported value in .mpeg (0x00000001)

Same machine, same everything, just rebooting back into the 3.2 kernel
the problem is gone.


Version-Release number of selected component (if applicable):

3.3.0-4.fc16.x86_64 or later

How reproducible:

always

Steps to Reproduce:
1. boot into kernel 3.3
2. watch dvb-s with hardware
3.
  
Actual results:


Expected results:


Additional info:

I got pointed to the patch at http://www.spinics.net/lists/linux-media/msg45592.html

Comment 1 Jens Hektor 2012-04-09 07:17:01 UTC
Should be a duplicate of bug #808871

Comment 2 Josh Boyer 2012-04-09 13:32:46 UTC

*** This bug has been marked as a duplicate of bug 808871 ***

Comment 3 shishir gowda 2012-05-08 04:35:53 UTC
*** Bug 810103 has been marked as a duplicate of this bug. ***