Bug #2958
Kernel tainted
0%
Description
Hi,
today tvheadend crashed with the following log entry:
Jun 20 12:52:41 NAS kernel: [ 1423.755328] divide error: 0000 [#1] SMP Jun 20 12:52:41 NAS kernel: [ 1423.755335] Modules linked in: xt_multiport xt_nat xt_tcpudp iptable_mangle ipt_MASQUERADE xt_conntrack iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_filter ip_tables x_tables bnep rfcomm bluetooth nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache ts2020(OX) m88ds3103(OX) i2c_mux cx25840(OX) cx23885(OX) altera_ci(OX) tda18271(OX) altera_stapl(OX) videobuf2_dvb(OX) tveeprom(OX) cx2341x(OX) videobuf2_dma_sg(OX) ftdi_sio rc_core(OX) usbserial videobuf2_memops(OX) stv6110x(OX) lnbp21(OX) videobuf2_core(OX) joydev hid_generic v4l2_common(OX) videodev(OX) snd_pcm stv090x(OX) snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore parport_pc gpio_ich ppdev divas ngene(OX) divadidd i3200_edac bonding serio_raw edac_core dvb_core(OX) coretemp kvm_intel kvm mac_hid media(OX) lpc_ich lp parport shpchp usbhid hid psmouse 8139too ahci e1000 8139cp libahci e1000e mii ptp pps_core floppy Jun 20 12:52:41 NAS kernel: [ 1423.755420] CPU: 1 PID: 1190 Comm: tvheadend Tainted: G IOX 3.13.0-55-generic #94-Ubuntu Jun 20 12:52:41 NAS kernel: [ 1423.755423] Hardware name: Wortmann AG TERRA Server/S3210SH, BIOS S3200X38.86B.00.00.0042.042820081723 04/28/2008 Jun 20 12:52:41 NAS kernel: [ 1423.755427] task: ffff8800c9a20000 ti: ffff8800c9b00000 task.ti: ffff8800c9b00000 Jun 20 12:52:41 NAS kernel: [ 1423.755430] RIP: 0010:[<ffffffffa03f018a>] [<ffffffffa03f018a>] m88ds3103_read_snr+0x1ba/0x270 [m88ds3103] Jun 20 12:52:41 NAS kernel: [ 1423.755439] RSP: 0018:ffff8800c9b01c50 EFLAGS: 00010246 Jun 20 12:52:41 NAS kernel: [ 1423.755442] RAX: 0000000000000036 RBX: 0000000000000000 RCX: 00000000aaaaaaab Jun 20 12:52:41 NAS kernel: [ 1423.755444] RDX: 0000000000000000 RSI: ffff8800c9b01bf0 RDI: ffff8800c9b01c68 Jun 20 12:52:41 NAS kernel: [ 1423.755447] RBP: ffff8800c9b01c90 R08: 0000000000000000 R09: 0000000000000000 Jun 20 12:52:41 NAS kernel: [ 1423.755449] R10: 0000000000000003 R11: ffff8800c9b01c00 R12: ffff8800ca879000 Jun 20 12:52:41 NAS kernel: [ 1423.755452] R13: ffff8800c9b01c65 R14: 00000000000000a2 R15: 0000000000000000 Jun 20 12:52:41 NAS kernel: [ 1423.755455] FS: 00007f8c9b9e5c40(0000) GS:ffff88011fc80000(0000) knlGS:0000000000000000 Jun 20 12:52:41 NAS kernel: [ 1423.755458] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 20 12:52:41 NAS kernel: [ 1423.755460] CR2: 00007f8dd40698d8 CR3: 00000000d86a7000 CR4: 00000000000007e0 Jun 20 12:52:41 NAS kernel: [ 1423.755462] Stack: Jun 20 12:52:41 NAS kernel: [ 1423.755465] 0000000016b8d400 ffff8800c9b01e00 120000ffa03eea16 0000000080026f48 Jun 20 12:52:41 NAS kernel: [ 1423.755470] ffff8800c9b01e00 ffff880116b8d400 ffff8800ca879038 ffff880116b8d400 Jun 20 12:52:41 NAS kernel: [ 1423.755474] ffff8800c9b01d88 ffffffffa01e84eb 0000000000013180 0000000000013180 Jun 20 12:52:41 NAS kernel: [ 1423.755479] Call Trace: Jun 20 12:52:41 NAS kernel: [ 1423.755493] [<ffffffffa01e84eb>] dvb_frontend_ioctl_legacy.isra.8+0x9b/0xce0 [dvb_core] Jun 20 12:52:41 NAS kernel: [ 1423.755501] [<ffffffff8108e715>] ? lock_hrtimer_base.isra.19+0x25/0x50 Jun 20 12:52:41 NAS kernel: [ 1423.755505] [<ffffffff8108e7d8>] ? hrtimer_try_to_cancel+0x48/0xe0 Jun 20 12:52:41 NAS kernel: [ 1423.755510] [<ffffffff8108e88a>] ? hrtimer_cancel+0x1a/0x30 Jun 20 12:52:41 NAS kernel: [ 1423.755515] [<ffffffff810d8852>] ? futex_wait+0x1b2/0x290 Jun 20 12:52:41 NAS kernel: [ 1423.755525] [<ffffffffa01e9dc2>] dvb_frontend_ioctl+0x132/0x1240 [dvb_core] Jun 20 12:52:41 NAS kernel: [ 1423.755534] [<ffffffffa01dee55>] dvb_usercopy+0x115/0x190 [dvb_core] Jun 20 12:52:41 NAS kernel: [ 1423.755544] [<ffffffffa01e9c90>] ? dvb_register_frontend+0x1f0/0x1f0 [dvb_core] Jun 20 12:52:41 NAS kernel: [ 1423.755549] [<ffffffff810d9351>] ? futex_wake+0x1b1/0x1d0 Jun 20 12:52:41 NAS kernel: [ 1423.755558] [<ffffffffa01deef3>] dvb_generic_ioctl+0x23/0x40 [dvb_core] Jun 20 12:52:41 NAS kernel: [ 1423.755563] [<ffffffff811d14b0>] do_vfs_ioctl+0x2e0/0x4c0 Jun 20 12:52:41 NAS kernel: [ 1423.755567] [<ffffffff811d1711>] SyS_ioctl+0x81/0xa0 Jun 20 12:52:41 NAS kernel: [ 1423.755572] [<ffffffff81733d5d>] system_call_fastpath+0x1a/0x1f Jun 20 12:52:41 NAS kernel: [ 1423.755575] Code: 44 89 e1 48 8b 75 c8 48 8d 14 80 48 8d 14 92 48 8d 04 95 00 00 00 00 31 d2 48 f7 f1 66 89 06 31 c0 e9 b3 fe ff ff 0f 1f 00 31 d2 <66> 41 f7 f1 0f b7 f8 e8 ba d7 df ff 89 c0 48 8b 7d c8 48 8d 04 Jun 20 12:52:41 NAS kernel: [ 1423.755617] RIP [<ffffffffa03f018a>] m88ds3103_read_snr+0x1ba/0x270 [m88ds3103] Jun 20 12:52:41 NAS kernel: [ 1423.755623] RSP <ffff8800c9b01c50> Jun 20 12:52:41 NAS kernel: [ 1423.755627] ---[ end trace f4df75eef93bd63f ]---
I can't imagine if I "produced" this by using it in a special way, but I clicked around the web ui. This happend on a Ubuntu 14.04 (LTS) machine with rel. newly upgraded TvHeadend 4.0.4 (from repository), upgraded from 3.4. This happened never before as I can remember.
I you need some special informations, please contact me.
Thanks.
History
Updated by Mark Clarkstone over 9 years ago
Johann Reisner wrote:
Hi,
today tvheadend crashed with the following log entry:
[...]
I can't imagine if I "produced" this by using it in a special way, but I clicked around the web ui. This happend on a Ubuntu 14.04 (LTS) machine with rel. newly upgraded TvHeadend 4.0.4 (from repository), upgraded from 3.4. This happened never before as I can remember.
I you need some special informations, please contact me.
Thanks.
I don't think this is a bug caused by Tvheadend but a dodgy driver, I got the same divide error on my system at some point (it was caused by the ts2020 driver) upgrading to the latest media_tree fixed the issue (I now run the longterm kernel (3.18) and haven't had any issues in a long time).
However I could be totally wrong in your case & it might be something completely different (I'm no expert, you'll have to wait for one to reply ).
Updated by Johann Reisner over 9 years ago
Sure, this could be. But I'm no expert in this, too. And the stacktrace doesn't point in a clear direction for me, except the word "tvheadend" :-) We'll see...
Updated by Jaroslav Kysela over 9 years ago
- Status changed from New to Rejected
Yes, upgrade the driver (kernel) and if it does not not help, report this issue to the driver author.