Bug 1273558

Summary:	4.2.3-200.fc22.armv7hl breaks dvb-s with M88DS3103
Product:	[Fedora] Fedora	Reporter:	Joerg <joerg>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	22	CC:	gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab
Target Milestone:	---
Target Release:	---
Hardware:	armv7hl
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-19 18:16:37 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Joerg 2015-10-20 17:04:21 UTC

Description of problem:
Latest Kernel does not allow to tune to High Frequence Range (22kHz Tone) on Astra 19.2E. No Data is received.

Version-Release number of selected component (if applicable):
4.2.3-200.fc22.armv7hl

How reproducible:
Try to tune to a Sat station in the high band. Either Horizontal or Vertical. Use dvbstream, tvheadend or any other tool.

Steps to Reproduce:
1.
2.
3.

Actual results:
No broadcast

Expected results:
Get Data from broadcast

Additional info:
Low Band works without issues.

Going back to Fedora (4.1.10-200.fc22.armv7hl) 22 (Twenty Two) solves the issue.

Comment 1 Fedora End Of Life 2016-07-19 18:16:37 UTC

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.