Starting chromium freezes Me-TV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Hi There
I have the problem that every time when chromium starts, my running me-tv session freezes.
STEPS TO REPRODUCE
1. everything closed
2. Start me-tv, wait for playback
3. Start chromium
4. me-tv picture freezes and audio playback stops. dmesg prints "tda9887 8-0043: i2c i/o error: rc == -6 (should be 4)"
5. close me-tv while chromium is still running
6. dmesg prints stack trace (see below)
7. Stop me-tv by pressing Ctrl+Q
8. Start me-tv again
9. me-tv works without problems, chromium is still running
LOG MESSAGES
I wasn't ably to find any helpful log messages but these:
dmesg after starting chromium
[ 7214.127110] tda9887 8-0043: i2c i/o error: rc == -6 (should be 4)
dmesg after quitting chromium
[ 7236.212694] ------------[ cut here ]------------
[ 7236.212705] WARNING: CPU: 5 PID: 7784 at /build/
[ 7236.212707] name 'fs/nfsfs'
[ 7236.212709] Modules linked in: dm_crypt snd_hrtimer pci_stub vboxpci(OX) vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) cuse veth xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables autofs4 bnep deflate ctr twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common camellia_generic camellia_
[ 7236.212772] CPU: 5 PID: 7784 Comm: kworker/u16:0 Tainted: G W OX 3.13.0-37-generic #64-Ubuntu
[ 7236.212773] Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./H77-DS3H, BIOS F5 05/14/2012
[ 7236.212776] Workqueue: netns cleanup_net
[ 7236.212777] 0000000000000009 ffff8801fca47c80 ffffffff8171ed09 ffff8801fca47cc8
[ 7236.212779] ffff8801fca47cb8 ffffffff8106773d 0000000000000000 0000000000000005
[ 7236.212780] ffffffffa067c8a8 ffff880216805b30 0000000000000200 ffff8801fca47d18
[ 7236.212782] Call Trace:
[ 7236.212785] [<ffffffff8171e
[ 7236.212787] [<ffffffff81067
[ 7236.212789] [<ffffffff81067
[ 7236.212792] [<ffffffff81229
[ 7236.212800] [<ffffffffa065c
[ 7236.212805] [<ffffffffa0662
[ 7236.212807] [<ffffffff8161b
[ 7236.212808] [<ffffffff8161b
[ 7236.212811] [<ffffffff81083
[ 7236.212812] [<ffffffff81084
[ 7236.212814] [<ffffffff81084
[ 7236.212816] [<ffffffff8108b
[ 7236.212817] [<ffffffff8108b
[ 7236.212819] [<ffffffff8172f
[ 7236.212820] [<ffffffff8108b
[ 7236.212821] ---[ end trace 91c959672924c77b ]---
RESEARCH
I tried to find information about fs/nfsfs which looks like a file system driver, but even google didn't find a result for this. I know nfs (the network protocol) but it is not in use on my system.
FURTHER INFORMATION
- My video card is a Hauppauge HVR-1300. This device already made problems in the past, but these problems were about startup and initializing.
- The only one connection which I see between these two application are audio and probably direct graphics output. For audio I would expect some helpful log messages, but there is not more information than the kernel stack trace and the i2c message.
- I think there is somthing in the initialization sequence of chromium. First I thought it's the pepper flash plugin but I have the same problem when I remove the plugin.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: chromium-browser 37.0.2062.
ProcVersionSign
Uname: Linux 3.13.0-37-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Oct 24 22:26:17 2014
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to trusty on 2014-04-18 (189 days ago)
modified.
mtime.conffile.
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Your problem may have been fixed with some of the updates.
It would help us a lot if you could test on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once in a terminal:
apport-collect 1385482
and add any additional information that you think relevant. Alternatively, please confirm that this is no longer a problem and that we can close the report. If we do not hear from you the bug report will close itself in approximately two months time.
Thank you again for helping make Ubuntu better.
Paul White
[Ubuntu Bug Squad]