Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3185945imu; Fri, 23 Nov 2018 23:36:31 -0800 (PST) X-Google-Smtp-Source: AFSGD/W6oKCjK+TEUThw/Kf4qMfIhhYIWNni/b8etmHPRe1B10keRRVz5wJug+ho0+3aP1Jja5jK X-Received: by 2002:a17:902:4523:: with SMTP id m32mr18894921pld.53.1543044991095; Fri, 23 Nov 2018 23:36:31 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543044991; cv=none; d=google.com; s=arc-20160816; b=PuND4dLdJZ97sps/gcsAl/kjBQGbIKYdjQ9i6XecjiblfjRn/mmB9lPr2tpiIL5q1E Y5t17eLCnBJyw+nXfXp9ApmPvs1aLWrxjTXVfUiua3rEU5jN/Xd7V4zZkaTsyaV+xpM5 GLXL6eRZULgqIc2WLzm+D0aQY4tU15nrqZH1nD523pjlwA702VKaXAmDSKnjObToW7bD b7jTltcTBgx3mpo1iRTxTGrTvRoOWgSh8Buzygbko2gB+aZjW5b6PYZ34/qi+5QyW4W9 l9abW1euLcDbhIDcdRrXec4++rhe/RQ1Z9rW/s3gWAH4Bc7afo9CrUmAByK2NEBNX763 wcPQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dkim-signature; bh=gPXhfSh7YtHd0eTt0Kr8G0AH7JX63P7S4BhOWRASTMQ=; b=w2XU6LqgY6Vb57j8Qg9g3qdkW7ycERyeodinp1IgTMAg7d1K5cupaEDHgDO3BUpIMY EUm0+Y8tMh5Ih2lbZVPs26JHGO9rxZwQOT62MApXblPNXStJZtNH0Goxr4zW08scBUwk 55la/wBsc3TRPQTFAXs47/e+x12+V+4ZpI3+/HbT3HVXpXbbGmn6P2g3KLn5DjM3jrCu N+kxIzY/NJejkAzbJTc1zsLQscs1F1Ylg2qH1OI2WLHzQ6fyZsE+nTu2Oeav3zUTN66+ tTKapremI3g/fvJvPV4Jglbzv07wLQOrRw+qGWoUJnE6sghUcvzCNiLUtXO5fo14yJO2 Uhzw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=casper.20170209 header.b=QHY9cqEg; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 97si14828222plb.3.2018.11.23.23.36.16; Fri, 23 Nov 2018 23:36:31 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@infradead.org header.s=casper.20170209 header.b=QHY9cqEg; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2405086AbeKWHQ5 (ORCPT + 99 others); Fri, 23 Nov 2018 02:16:57 -0500 Received: from casper.infradead.org ([85.118.1.10]:47932 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730632AbeKWHQ5 (ORCPT ); Fri, 23 Nov 2018 02:16:57 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=gPXhfSh7YtHd0eTt0Kr8G0AH7JX63P7S4BhOWRASTMQ=; b=QHY9cqEghBCLztan5bmkurShFY zu0pvKoxPRsL+564kj8vMCvcgL3b+fRF/7Nqo97A6TsGQcemS7/brna66F9KCFzPmcmZA8h3vskYJ WJoFZ05RMn0LVldqqy3LZcDi7EWP+i039wwz4EZLHB9qYqZ/9/5v6J/7JU2acbCa+ArusMmnjt2yw XMKh4F037IUZFNWHODKulpxVMJTpaD7Ojp5E7ohNI0Jr571wCYLZJqCWxqE8D8oyvPC0NqBd8Oycl tdo8ZRP4aTLYQBnN13acYeQbiXTLEp5/J9lvjEA8VXqFpgCwAos5bBYIweOQhkOIVNsgWMIw1oWHO iBLtSeJQ==; Received: from 201.47.163.210.dynamic.adsl.gvt.net.br ([201.47.163.210] helo=coco.lan) by casper.infradead.org with esmtpsa (Exim 4.90_1 #2 (Red Hat Linux)) id 1gPvhZ-0006L0-BM; Thu, 22 Nov 2018 20:35:53 +0000 Date: Thu, 22 Nov 2018 18:35:49 -0200 From: Mauro Carvalho Chehab To: stakanov Cc: Takashi Iwai , linux-media@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: DVB-S PCI card regression on 4.19 / 4.20 Message-ID: <20181122183549.331ecbc4@coco.lan> In-Reply-To: <12757009.r0OKxgvFl0@roadrunner.suse> References: <4e0356d6303c128a3e6d0bcc453ba1be@mail.eclipso.de> <2836654.gWKGMNFOG2@roadrunner.suse> <20181122180611.2e7f1123@coco.lan> <12757009.r0OKxgvFl0@roadrunner.suse> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Em Thu, 22 Nov 2018 21:19:49 +0100 stakanov escreveu: > Hello Mauro.=20 >=20 > Thank you so much, for this fast reply and especially for the detailed=20 > indications. I expected to have a lack of knowledge.=20 >=20 > Well, I am replying to the question as of below: (for convenience I did = cut=20 > the before text, if you deem it useful for the list I can then correct th= at in=20 > the next posts). >=20 > In data gioved=C3=AC 22 novembre 2018 21:06:11 CET, Mauro Carvalho Chehab= ha=20 > scritto: > > Are you sure that the difference is just the Kernel version? Perhaps you > > also updated some other package. =20 >=20 > To be clear: I had the same system(!) with all three kernel 4.18.15-1, 4.= 19.1 =20 > (when the problem did arise) and 4.20.2 rc3 from Takashi's repo) installe= d.=20 Ok, so rebooting to 4.18.15-1 solves the issue? Also, what GPU driver are you using? In any case, by using the old "Universal" LNBf, you're likely missing some transponders, and missing several channels. > In this very configuration: if one booted in 4.18 (that is in perfect par= ity=20 > with all other packages) the card worked. 4.19.1 no. And the last kernel = the=20 > same. So whatever might be different, forcefully it has to be in the kern= el.=20 > (Which is not really a problem if I manage to make it work, so settings w= ill=20 > be known to others or, if not, we will find out what is different, and al= l=20 > will be happy. As you see I am still optimist). =20 Well, we don't want regressions in Kernel. If there's an issue there, it should be fixed. However, I can't think on any other changes since 4.18 that would be causing troubles for b2c2 driver. See, the only change at the driver itself is just a simple API replacement that wouldn't cause this kind of problems: $ git log --oneline v4.18.. drivers/media/common/b2c2/ c0decac19da3 media: use strscpy() instead of strlcpy() There were a few changes at the DVB core: $ git log --no-merges --oneline v4.18.. drivers/media/dvb-core/ f3efe15a2f05 media: dvb: use signal types to discover pads b5d3206112dd media: dvb: dmxdev: move compat_ioctl handling to dmxdev.c cc1e6315e83d media: replace strcpy() by strscpy() c0decac19da3 media: use strscpy() instead of strlcpy() fd89e0bb6ebf media: videobuf2-core: integrate with media requests db6e8d57e2cd media: vb2: store userspace data in vb2_v4l2_buffer 6a2a1ca34ca6 media: dvb_frontend: ensure that the step is ok for both FE a= nd tuner f1b1eabff0eb media: dvb: represent min/max/step/tolerance freqs in Hz a3f90c75b833 media: dvb: convert tuner_info frequencies to Hz 6706fe55af6f media: dvb_ca_en50221: off by one in dvb_ca_en50221_io_do_ioc= tl() 4d1e4545a659 media: mark entity-intf links as IMMUTABLE But, on a first glance, the only ones that has potential to cause issues were the ones addressed that the patch I wrote (merged by Takashi). If you're really receiving data from EPG (you may just have it cached), it means that the DVB driver is doing the right thing. Btw, to be sure that you're not just seeing the old EPG data, you should move or remove this file: ~/.local/share/kaffeine/epgdata.dvb Kaffeine will generate a new one again once it tunes into a TV channel. > I will proceed as indicated and report back here tomorrow.=20 Ok. Thanks, Mauro