xc5000 driver/firmware intermittent failure

[AtoZog]

xc5000 driver fails to load intermittently in up-to-date 16.04

On reboot, sometimes driver loads, sometimes it does not. Timing seems to be the issue

I am attaching dmesg output from a successful and an unsuccessful boot.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-70-generic 4.4.0-70.91
ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
Uname: Linux 4.4.0-70-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: a_herzog 1372 F.... pulseaudio
 /dev/snd/controlC2: a_herzog 1372 F.... pulseaudio
 /dev/snd/controlC1: a_herzog 1372 F.... pulseaudio
CurrentDesktop: XFCE
Date: Tue Mar 28 12:16:52 2017
HibernationDevice: RESUME=UUID=4b66b4c4-fbb2-4948-b3d5-91af7705f20d
InstallationDate: Installed on 2016-06-14 (286 days ago)
InstallationMedia: Mythbuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-70-generic root=UUID=ec52f45a-20fb-4d15-aee5-5fef0c006149 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-70-generic N/A
 linux-backports-modules-4.4.0-70-generic N/A
 linux-firmware 1.157.8
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: To be filled by O.E.M.
dmi.board.vendor: To be filled by O.E.M.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd10/12/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Brad Figg (brad-figg)]

This change was made by a bot.

[AtoZog (ereagle33)]

Linux aeh-htpc 4.4.0-70-generic #91-Ubuntu SMP Wed Mar 22 12:47:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc4

[AtoZog (ereagle33)]

Joseph,

This has been happening since at least last Fall. I entered a question,
https://answers.launchpad.net/ubuntu/+question/403642, but got no responses.

That was after I upgraded to 16.04 (from 12.04) sometime last summer,
but I don't remember exactly. I also don't remember whether this problem
occurred immediately after the upgrade or at some other point in time.
That was the same time I added an 955Q tuner (required the 4.* kernel)
to the 950Q.

I will give the latest upstream kernel a try later today/tomorrow and
update the bug report.

Thanks,

Art

On 3/29/2017 10:38 AM, Joseph Salisbury wrote:
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular problem?
>
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.11 kernel[0].
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc4
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>

[AtoZog (ereagle33)]

Confirmed in 4.11.00 rc4

[Kai-Heng Feng (kaihengfeng)]

Do you still keep Precise kernel (3.2) installed? Does the issue happen on 3.2?

[AtoZog (ereagle33)]

I do have a 12.04 system with 3.2.0.26 kernel and I was NOT able to reproduce the problem.

I have attached a dmesg from that system for your reference.

One potential issue is that my other tuner (955Q) is not supported in the 3.2 kernel, so that might be a clue.

Of course, there are many other changes in the software that are equally likely culprits at this point.

It I have time, I may remove that other tuner from the current system and see what happens.

I'd also note that in the new system, the device seems "busier" and/or is just more verbose.

[Kai-Heng Feng (kaihengfeng)]

Can you try Trusty kernel (3.13)?

You can install it by this command:
$ sudo apt-get install --install-recommends linux-generic-lts-trusty

[AtoZog (ereagle33)]

I was not able to try the 3.13 kernel... Using your command, some issue
with missing kernel mods or something (sorry, not at the machine right
now) when booting. I will try again later as time allows.

I will also note that I tried removing the 2nd tuner and there was no
change in behavior. Since this was added at the same time as the
upgrade, I just wanted to eliminate that as a possible cause.

On 4/6/2017 9:49 AM, Kai-Heng Feng wrote:
> Can you try Trusty kernel (3.13)?
>
> You can install it by this command:
> $ sudo apt-get install --install-recommends linux-generic-lts-trusty
>

[AtoZog (ereagle33)]

Random update: the issue seems to have disappear in a recent kernel, somewhere between 4.4.0.89 and 4.4.0.93. Just an FYI for anyone who is still paying attention.

Of course, it could be a random unrelated software change elsewhere, but there have been no hardware changes to the machine.

[AtoZog (ereagle33)]

Based on further discussion, this seems to have been fixed by changes delivered for https://patchwork.kernel.org/patch/9689195/