public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Gregor Jasny <gjasny@googlemail.com>
To: Marcel Heinz <quisquilia@gmx.de>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
	mchehab@osg.samsung.com
Subject: Re: Bug#854100: libdvbv5-0: fails to tune / scan
Date: Fri, 10 Feb 2017 22:02:01 +0100	[thread overview]
Message-ID: <458abbd2-a98b-243b-bf2f-48d5e5a8060b@googlemail.com> (raw)
In-Reply-To: <ba755934-7946-59ea-e900-fe76d4ea2f0a@gmx.de>

Hello Mauro & DVB-S maintainers,

could you please have a look at the bug report below? Marcel was so kind
to bisect the problem to the following commit:

https://git.linuxtv.org/v4l-utils.git/commit/?id=d982b0d03b1f929269104bb716c9d4b50c945125

Bug report against libdvbv5 is here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854100

On 2/4/17 5:43 PM, Marcel Heinz wrote:
> Am 04.02.2017 um 15:57 schrieb Gregor Jasny:
>> Thanks for sharing! Maybe you could try to bisect to find the breaking
>> commit?
> 
> OK, I ended up with
> 
> d982b0d03b1f929269104bb716c9d4b50c945125 is the first bad commit
> commit d982b0d03b1f929269104bb716c9d4b50c945125
> Author: Mauro Carvalho Chehab <mchehab@s-opensource.com>
> Date:   Tue Dec 13 16:43:28 2016 -0200
> 
>     dvb-sat: change the LNBf logic to make it more generic
> 
>     There are some new LNBf models with more than two frequency
>     ranges. Change the logic there to allow adding those new
>     LNBf types.
> 
>     Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
> 
> :040000 040000 5c0591da94959207f4b1573a40383b8143d12278
> 34df9c19cb42119706fce20dec00d18552ddf058 M      lib
> 
> 
> This looks very related to the frequency range error I got from the kernel:
> 
>> | [42607.855196] b2c2_flexcop_pci 0000:09:00.0: DVB: adapter 0 frontend
>> 0 frequency 12551500 out of range (950000..2150000)
>>
>> This frequency range doesn't look like DVB-S at all...

Thanks,
Gregor


  reply	other threads:[~2017-02-10 21:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <148617570740.6827.6324247760769667383.reportbug@ixtlilton.netz.invalid>
2017-02-04  9:08 ` Bug#854100: libdvbv5-0: fails to tune / scan Gregor Jasny
2017-02-04 12:35   ` Marcel Heinz
     [not found]     ` <CAJxGH0-ewWzxSJ1vE+n4FMkqv+pnmT9G0uAZS5oUYkhxWm+=5A@mail.gmail.com>
2017-02-04 16:43       ` Marcel Heinz
2017-02-10 21:02         ` Gregor Jasny [this message]
2017-02-13 10:04           ` Mauro Carvalho Chehab
2017-02-15 13:13             ` Mauro Carvalho Chehab
2017-02-15 14:37               ` Mauro Carvalho Chehab
2017-02-17 21:50 Marcel Heinz
2017-02-20  9:52 ` Mauro Carvalho Chehab

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=458abbd2-a98b-243b-bf2f-48d5e5a8060b@googlemail.com \
    --to=gjasny@googlemail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@osg.samsung.com \
    --cc=quisquilia@gmx.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