DVB Card doesn't work after upgrade to 17.10 with new kernel

Asked by TauSo on 2018-01-06

Hello,

after upgrading Ubuntu from Xenial (16.04.) to Artful (17.10) with the 4.13 kernel my PCI DVB Card Terratec DVB-C 1200 doesn't work anymore.
In the syslog I found a kernel bug message, so I switched to the old 4.4.0 kernel and now it's working again.
Now I don't know if it's really a Kernel bug or some firmware or driver issuer with my card. Here is the (hopefully) relevant part of the kernel.log:

Jan 6 14:32:13 hostname kernel: [ 6.077530] ------------[ cut here ]------------
Jan 6 14:32:13 hostname kernel: [ 6.077535] kernel BUG at /build/linux-WZjiV8/linux-4.13.0/drivers/media/common/saa7146/saa7146_core.c:163!
Jan 6 14:32:13 hostname kernel: [ 6.077548] invalid opcode: 0000 [#1] SMP
Jan 6 14:32:13 hostname kernel: [ 6.077680] Modules linked in: budget_av(+) saa7146_vv snd_hda_codec_hdmi budget_core ttpci_eeprom snd_hda_codec_realtek saa7146 snd_hda_codec_generic videobuf_dma_sg intel_powerclamp snd_hda_intel videobuf_core snd_hda_codec dvb_core snd_hda_core v4l2_common snd_hwdep snd_pcm videodev snd_timer joydev input_leds media lpc_ich snd soundcore shpchp parport_pc nuvoton_cir parport rc_core mac_hid nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 hid_generic usbhid hid gma500_gfx i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt fb_sys_fops libahci drm r8169 mii video
Jan 6 14:32:13 hostname kernel: [ 6.079363] CPU: 0 PID: 300 Comm: systemd-udevd Not tainted 4.13.0-21-generic #24-Ubuntu
Jan 6 14:32:13 hostname kernel: [ 6.079626] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./AD2700-ITX, BIOS P1.00 12/15/2011
Jan 6 14:32:13 hostname kernel: [ 6.079921] task: f48c1d40 task.stack: f4a1c000
Jan 6 14:32:13 hostname kernel: [ 6.080027] EIP: saa7146_vmalloc_build_pgtable+0x180/0x1020 [saa7146]
Jan 6 14:32:13 hostname kernel: [ 6.080027] EFLAGS: 00010246 CPU: 0
Jan 6 14:32:13 hostname kernel: [ 6.080027] EAX: f21ec2a8 EBX: f527e800 ECX: 00000002 EDX: fff1b000
Jan 6 14:32:13 hostname kernel: [ 6.080027] ESI: 00000000 EDI: f8881000 EBP: f4a1dc44 ESP: f4a1dc20
Jan 6 14:32:13 hostname kernel: [ 6.080027] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Jan 6 14:32:13 hostname kernel: [ 6.080027] CR0: 80050033 CR2: 00f0bb74 CR3: 350590a0 CR4: 000006f0
Jan 6 14:32:13 hostname kernel: [ 6.080027] Call Trace:
Jan 6 14:32:13 hostname kernel: [ 6.080027] ttpci_budget_init+0x26c/0x530 [budget_core]
Jan 6 14:32:13 hostname kernel: [ 6.080027] budget_av_attach+0x75/0x4e8 [budget_av]
Jan 6 14:32:13 hostname kernel: [ 6.080027] ? vprintk_func+0x29/0x70
Jan 6 14:32:13 hostname kernel: [ 6.080027] ? printk+0x13/0x15
Jan 6 14:32:13 hostname kernel: [ 6.080027] ? saa7146_init_one+0x69f/0x770 [saa7146]
Jan 6 14:32:13 hostname kernel: [ 6.080027] saa7146_init_one+0x70b/0x770 [saa7146]
Jan 6 14:32:13 hostname kernel: [ 6.080027] ? __pm_runtime_resume+0x51/0x80
Jan 6 14:32:13 hostname kernel: [ 6.082325] pci_device_probe+0xc2/0x160
Jan 6 14:32:13 hostname kernel: [ 6.082325] driver_probe_device+0x2b9/0x410
Jan 6 14:32:13 hostname kernel: [ 6.082325] __driver_attach+0x99/0xe0
Jan 6 14:32:13 hostname kernel: [ 6.082325] ? driver_probe_device+0x410/0x410
Jan 6 14:32:13 hostname kernel: [ 6.082325] bus_for_each_dev+0x57/0x90
Jan 6 14:32:13 hostname kernel: [ 6.082325] driver_attach+0x19/0x20
Jan 6 14:32:13 hostname kernel: [ 6.082325] ? driver_probe_device+0x410/0x410
Jan 6 14:32:13 hostname kernel: [ 6.082325] bus_add_driver+0x187/0x230
Jan 6 14:32:13 hostname kernel: [ 6.082325] ? 0xf86d0000
Jan 6 14:32:13 hostname kernel: [ 6.082325] driver_register+0x56/0xd0
Jan 6 14:32:13 hostname kernel: [ 6.082325] ? 0xf86d0000
Jan 6 14:32:13 hostname kernel: [ 6.082325] __pci_register_driver+0x33/0x40
Jan 6 14:32:13 hostname kernel: [ 6.082325] saa7146_register_extension+0x50/0x80 [saa7146]
Jan 6 14:32:13 hostname kernel: [ 6.082325] budget_av_init+0xd/0x1000 [budget_av]
Jan 6 14:32:13 hostname kernel: [ 6.082325] do_one_initcall+0x46/0x180
Jan 6 14:32:13 hostname kernel: [ 6.082325] ? kfree+0x134/0x140
Jan 6 14:32:13 hostname kernel: [ 6.082325] ? kfree+0x134/0x140
Jan 6 14:32:13 hostname kernel: [ 6.082325] ? kfree+0x134/0x140
Jan 6 14:32:13 hostname kernel: [ 6.082325] ? kmem_cache_alloc_trace+0x13d/0x1a0
Jan 6 14:32:13 hostname kernel: [ 6.082325] ? do_init_module+0x21/0x1cc
Jan 6 14:32:13 hostname kernel: [ 6.082325] ? do_init_module+0x21/0x1cc
Jan 6 14:32:13 hostname kernel: [ 6.082325] do_init_module+0x50/0x1cc
Jan 6 14:32:13 hostname kernel: [ 6.082325] load_module+0x1533/0x1aa0
Jan 6 14:32:13 hostname kernel: [ 6.082325] ? kernel_read_file+0x26e/0x2a0
Jan 6 14:32:13 hostname kernel: [ 6.082325] SyS_finit_module+0x8a/0xe0
Jan 6 14:32:13 hostname kernel: [ 6.082325] do_fast_syscall_32+0x71/0x150
Jan 6 14:32:13 hostname kernel: [ 6.082325] entry_SYSENTER_32+0x4e/0x7c
Jan 6 14:32:13 hostname kernel: [ 6.082325] EIP: 0xb7ee0cf9
Jan 6 14:32:13 hostname kernel: [ 6.082325] EFLAGS: 00000296 CPU: 0
Jan 6 14:32:13 hostname kernel: [ 6.082325] EAX: ffffffda EBX: 00000018 ECX: b7cd0a71 EDX: 00000000
Jan 6 14:32:13 hostname kernel: [ 6.082325] ESI: 00ee3dd0 EDI: 00ee22a0 EBP: 00000000 ESP: bfa897dc
Jan 6 14:32:13 hostname kernel: [ 6.082325] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b
Jan 6 14:32:13 hostname kernel: [ 6.082325] Code: e4 e8 c5 eb ff ff 85 c0 59 75 6b 8b 45 ec 8d 65 f4 5b 5e 5f 5d c3 90 8d 74 26 00 83 3d f0 7c e1 ca 02 0f 85 0c ff ff ff 8d 76 00 <0f> 0b 8d b6 00 00 00 00 0f 0b 8d b6 00 00 00 00 c7 45 dc 00 00
Jan 6 14:32:13 hostname kernel: [ 6.082325] EIP: saa7146_vmalloc_build_pgtable+0x180/0x1020 [saa7146] SS:ESP: 0068:f4a1dc20
Jan 6 14:32:13 hostname kernel: [ 6.082764] ---[ end trace 56c9869885a2ef31 ]---

Is there something I can do about this issue (new driver, firmware?) or should I file a bug for this?

Thomas

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
2018-01-07
Last reply:
2018-01-07

Did you upgrade to 17.04 in between?

TauSo (tauso) said : #2

No, I just changed the sources.list from xenial to artful and did a apt dist-upgrade.

Then you haven't upgraded in the official way. You don't upgrade Ubuntu that way and you have also leapfrogged a release which is also not how to upgrade ubuntu.

TauSo (tauso) said : #4

Yes for sure it's not the official way, but I have done that a several times on (other systems) since 12.04 and never had such an issue.

Do you suppose that's related to how I did the update? Maybe I could try to boot the system with a live cd/usb stick with a fresh 17.10 image.

TauSo (tauso) said : #5

Unfortunately there is no 17.10 Desktop iso for i386 architecture, so I cannot try without installing. But I've found this bugreport for ther redhat 4.13 kernel with the exact same issue:

https://bugzilla.redhat.com/show_bug.cgi?id=1515428

so it seems more like an kernel bug for me.

Manfred Hampl (m-hampl) said : #6

1. If you think that it is a kernel bug, then you should report it.

2. Can't you try the 17.10 Desktop iso for amd64 in a live system? Almost all CPUs from the past decade are able to use 64 bit computing, and it would astonish me very much if your CPU were unable to run a 64 bit operating system.

TauSo (tauso) said : #7

1. Thanks, I reported it.

2. No I can't. It's an Asrock Intel Atom D2700 mini-itx system which lacks 64-bit graphics drivers for windows, so unfourtunatly the manufacturer decided to cut the 64bit-support completely.

Can you help with this problem?

Provide an answer of your own, or ask TauSo for more information if necessary.

To post a message you must log in.