Oops with AVerTV DVB-T Volar (mt2060)
In the last few days I've installed a old AVerTV DVB-T Volar USB stick into my mythtv backend. The system is running debian squeeze with the 3.2 debian backport kernel. The motherboard in the sytem uses an AMD 760G/SB710 chipset. The USB stick is plugged into a mains powered (usb2) hub (NEC chipset). EIT active scan is enabled in MythTv (0.24) the tuner/signal timeouts are set to 1000ms/3000ms in mythbackend Since installing the stick I've started getting I2C read from the mt2060, shortly afterwards I get an oops (see below). I've googled a bit and I've come across similar reports from some years ago in regards to Hauppage Nova-T sticks. Whether they are the same or not I'm unsure, but the feedback to these issues appears to have been that a fix was committed (presumably long before kernel 3.2) Any suggestions here? A bit of background, I've just picked up this dib7000 stick after a couple of years of getting I2C errors from a pair of AF9015 sticks. I've finally gotten sick of the issues and am trying to get a more stable system. The powered hub is connected to the system as it seemed that the AF9015 sticks seemed more stable when plugged into this hub, rather than the motherboard root hubs. Also installed in the system are 2 atheros ar9280 cards (pci-e), an RTL8139 based adsl router(pci) and a Hauppauge WinTV-HVR-4000(pci). I've never had any problems with any of these pci/pci-e cards, only the dvb-t usb sticks. FYI, I'm suspicious that the USB on the amd 760/710 usb is buggy (suspicions arise from some googling I did around this some years ago). I'm considering changing the motherboard for one based on an AMD 970/SB950 chipset. Is this likely to be wise or just throwing more money away? Sep 5 20:13:47 beta kernel: [118265.068117] mt2060 I2C write failed (len=2) Sep 5 20:13:52 beta kernel: [118270.080113] mt2060 I2C write failed (len=6) Sep 5 20:13:57 beta kernel: [118275.092086] mt2060 I2C read failed Sep 5 20:14:02 beta kernel: [118280.112092] mt2060 I2C read failed Sep 5 20:14:07 beta kernel: [118285.132114] mt2060 I2C read failed Sep 5 20:14:12 beta kernel: [118290.152113] mt2060 I2C read failed Sep 5 20:14:17 beta kernel: [118295.172076] mt2060 I2C read failed Sep 5 20:14:22 beta kernel: [118300.192128] mt2060 I2C read failed Sep 5 20:14:27 beta kernel: [118305.212088] mt2060 I2C read failed Sep 5 20:14:32 beta kernel: [118310.232110] mt2060 I2C read failed Sep 5 20:14:38 beta kernel: [118315.252090] mt2060 I2C read failed Sep 5 20:14:43 beta kernel: [118320.272110] mt2060 I2C read failed Sep 5 20:16:43 beta kernel: [118440.932153] mythbackend D 880037790ea0 0 15174 1 0x Sep 5 20:16:43 beta kernel: [118440.932166] 880037790ea0 0086 88007af66240 8160d020 Sep 5 20:16:43 beta kernel: [118440.932178] 00013740 880037449fd8 880037449fd8 00013740 Sep 5 20:16:43 beta kernel: [118440.932188] 880037790ea0 00013740 00013740 880037448010 Sep 5 20:16:43 beta kernel: [118440.932197] Call Trace: Sep 5 20:16:43 beta kernel: [118440.932212] [8110f5b6] ? complete_walk+0x87/0xd4 Sep 5 20:16:43 beta kernel: [118440.932272] [81369130] ? __mutex_lock_common+0x10c/0x172 Sep 5 20:16:43 beta kernel: [118440.932300] [8136925c] ? mutex_lock+0x1a/0x2c Sep 5 20:16:43 beta kernel: [118440.932323] [a048b1fd] ? dvb_usercopy+0xb6/0x14a [dvb_core] Sep 5 20:16:43 beta kernel: [118440.932346] [a0493306] ? dvb_frontend_ioctl_legacy+0x981/0x981 [dvb_core] Sep 5 20:16:43 beta kernel: [118440.932357] [8110a77a] ? cp_new_stat+0xe6/0xfa Sep 5 20:16:43 beta kernel: [118440.932377] [a048b2b8] ? dvb_generic_ioctl+0x27/0x2c [dvb_core] Sep 5 20:16:43 beta kernel: [118440.932386] [8111499f] ? do_vfs_ioctl+0x464/0x4b1 Sep 5 20:16:43 beta kernel: [118440.932395] [8110a906] ? sys_newstat+0x24/0x2d Sep 5 20:16:43 beta kernel: [118440.932403] [81114a37] ? sys_ioctl+0x4b/0x70 Sep 5 20:16:43 beta kernel: [118440.932411] [8136f2d2] ? system_call_fastpath+0x16/0x1b ...reboot... Sep 6 00:24:01 beta kernel: [11206.193885] usb 1-5: USB disconnect, device number 2 Sep 6 00:24:01 beta kernel: [11206.193887] usb 1-5.7: USB disconnect, device number 3 Sep 6 00:24:01 beta kernel: [11206.194055] mt2060 I2C write failed Sep 6 00:27:16 beta kernel: [11400.928123] khubd D 880037b6d550 0 149 2 0x Sep 6 00:27:16 beta kernel: [11400.928135] 880037b6d550 0046 0001 880079e39510 Sep 6 00:27:16 beta kernel: [11400.928147] 00013740 880037b6ffd8 880037b6ffd8 00013740 Sep 6 00:27:16 beta kernel: [11400.928156] 880037b6d550 00013740 00013740 880037b6e010 Sep 6 00:27:16 beta kernel: [11400.928165] Call Trace: Sep 6 00:27:16 beta kernel: [11400.928244] [a03d289c] ? dvb_unregister_frontend+0xab/0xea
Re: [PATCH] af9013 frontend tuner bus lock
In message cal9g6wxx2egmot+ozv1f0jqdsv5jpwbb0vn70ul+ghgklgs...@mail.gmail.com, Josu Lazkano wrote snip I get this I2C messages: # tail -f /var/log/messages Oct 5 20:16:44 htpc kernel: [ 534.168957] af9013: I2C read failed reg:d330 Oct 5 20:16:49 htpc kernel: [ 538.626152] af9013: I2C read failed reg:d330 Oct 5 21:22:15 htpc kernel: [ 4464.930734] af9013: I2C write failed reg:d2e2 len:1 Oct 5 21:40:46 htpc kernel: [ 5576.241897] af9013: I2C read failed reg:d2e6 Oct 5 23:07:33 htpc kernel: [10782.852522] af9013: I2C read failed reg:d2e6 Oct 5 23:20:11 htpc kernel: [11540.824515] af9013: I2C read failed reg:d07c Oct 6 00:11:41 htpc kernel: [14631.122384] af9013: I2C read failed reg:d2e6 Oct 6 00:26:13 htpc kernel: [15502.900549] af9013: I2C read failed reg:d2e6 Oct 6 00:39:58 htpc kernel: [16328.273015] af9013: I2C read failed reg:d330 I have two af9013 sticks in my mythtv backend. One is a KWorld 399U, the other a single tuner Tevion stick. When I originally setup this system I had major problems with these sticks and also a pair of Freecom WT-220U (which worked perfectly in an older system - I've since disposed of these). I was seeing I2C read fails similar to the above. The system in question has an AMD760G southbridge. After a lot of googling I came across a post somewhere which said that the USB host controller on the 760G is problematic and suggested getting a NEC or VIA hub and using this between the DVB sticks and the root hub. I bought a cheap hub with an NEC chip on and since then (6 months maybe) I've had no problems with the system. Having said this I probably don't use all three frontends that often (I also have a DVB-S card and this takes precedence) though I certainly have on occasion and don't recall any problems. -- Dave Cunningham PGP KEY ID: 0xA78636DC signature.asc Description: PGP signature
Re: AF9015 Problem
In message aanlktimfae4pu4r3xk2hji0syjh22qmc-fyd23oqh...@mail.gmail.com, Juan Jesús García de Soria Lucena wrote El 30/01/2011 14:03, David Ondracek david.ondra...@gmx.de escribió: Hi there, Hi. I have a problem using my DIGITRADE DVB-T stick, which is marked as fully supported in the wiki. It works fine for a while, but after some time it crashes and I have to reboot and disconnect the stick to make it work again (for a while) The same thing happens to me with two different af9015 tuner sticks, an Avermedia Volar Black and a dual KWorld DVB-T-USB 399U (which happens to have other problems too due to its dual nature not being completely supported). In the end, I had to look for a tuner stick with a different chip set (and that proved to be a challenge itself due to the apparent popularity of af9015 among manufacturers) so that my mythtv rig would be dependable. Do you mind me asking what you ended up with? I've got similar problems with af9015. I have a Tevion stick that works with the V4L HG tree and 4.65 firmware but locks up the machine with the git tree and/or any other firmware version. I also have a KWorld 399U which causes the machine to lock up with any firmware/driver version I've tried. Previous to these I had 3 WT-220U sticks running stable in an Epia mythtv backend. I 'upgraded' the backend to an AMD system and all 3 started locking up the system - hence the move to af9015! Regards, -- Dave Cunningham dave at upsilon org uk PGP KEY ID: 0xA78636DC -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: AF9013/15 I2C problems
In message 4cbb1982.4050...@iki.fi, Antti Palosaari wrote On 10/17/2010 01:47 PM, dave cunningham wrote: I'm currently on hg version 14319:37581bb7e6f1, on a debian-squeeze system, kernel 2.6.32. I've googled and found various people seeing similar problems but have yet to come across a solution. Would anyone have any suggestions (note if I switch back to firmware 4.65 with just the Tevion stick things are fine - I'd like to use the KWorld stick if possible though)? I have strong feeling this issue is fixed already. Install latest Git master driver from Linuxtv.org I've compiled the git media-master, commit 1c8c51f7413ec522c7b729c8ebc5ce815fb7d4a8 and still have problems. With the Tevion Stick I now see the following at boot (with both firmware 4.65.0 and 4.95.0): [6.257795] DVB: registering adapter 0 frontend 0 (STB0899 Multistandard)... [6.264875] TDA18271HD/C1 detected @ 1-00c0 [6.902293] af9015: command failed:1 [6.902789] tda18271_write_regs: [1-00c0|M] ERROR: idx = 0x0, len = 39, i2c_t ransfer returned: -1 [7.540215] af9015: command failed:1 [7.540707] tda18271_write_regs: [1-00c0|M] ERROR: idx = 0x20, len = 1, i2c_t ransfer returned: -1 [8.178133] af9015: command failed:1 [8.178747] tda18271_write_regs: [1-00c0|M] ERROR: idx = 0x20, len = 1, i2c_t ransfer returned: -1 [8.816417] af9015: command failed:1 [8.817039] tda18271_write_regs: [1-00c0|M] ERROR: idx = 0x20, len = 1, i2c_transfer returned: -1 [9.454467] af9015: command failed:1 [9.455080] tda18271_write_regs: [1-00c0|M] ERROR: idx = 0x20, len = 1, i2c_transfer returned: -1 [ 10.092508] af9015: command failed:1 [ 10.093122] tda18271_write_regs: [1-00c0|M] ERROR: idx = 0x23, len = 1, i2c_transfer returned: -1 [ 10.730542] af9015: command failed:1 ... The KWorld stick comes up OK and can be used but after changing channels/sources a few times in mythtv I get (firmware 4.95.0): Oct 19 23:52:32 beta dhcpd: DHCPACK on 192.168.0.9 to 00:1c:c0:8c:88:7d via eth0 Oct 19 23:58:04 beta kernel: [ 480.140076] af9013: I2C read failed reg:d507 Oct 19 23:58:06 beta kernel: [ 482.152089] af9013: I2C read failed reg:d507 Oct 19 23:58:08 beta kernel: [ 484.164077] af9013: I2C read failed reg:d507 Oct 19 23:58:10 beta kernel: [ 486.176076] af9013: I2C read failed reg:d507 Oct 19 23:58:12 beta kernel: [ 488.188128] af9013: I2C read failed reg:d507 ... -- Dave Cunningham dave at upsilon org uk PGP KEY ID: 0xA78636DC -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
AF9013/15 I2C problems
A few months ago I switched systems and started having problems with a pair of WT-220U sticks http://www.spinics.net/lists/linux-media/msg22309.html. I got nowhere with this problem so gave up changing to a pair of AT9015 sticks. I started with a Tevion DK-5203 using firmware 4.65. I have no problems in this configuration. I then added a KWorld 399U. On insertion I got a kernel message saying firmware 4.95 is required so I switched to this. Now neither stick works correctly (either individually or with the other stick). At boot things are fine and I can use either stick (and both tuners on the 399U). At some point however I get a flood of message in the syslog like this: Oct 16 18:43:18 beta dhcpd: DHCPACK on 192.168.0.9 to 00:1c:c0:8c:88:7d via eth0 Oct 16 19:47:10 beta kernel: [ 8510.288055] af9013: I2C write failed reg:ae00 len:1 Oct 16 19:47:14 beta kernel: [ 8514.312050] af9013: I2C read failed reg:d330 Oct 16 19:47:18 beta kernel: [ 8518.336048] af9013: I2C read failed reg:9bee Oct 16 19:47:22 beta kernel: [ 8522.360053] af9013: I2C read failed reg:d330 Oct 16 19:47:26 beta kernel: [ 8526.384054] af9013: I2C read failed reg:d330 Oct 16 19:47:31 beta kernel: [ 8530.408060] af9013: I2C read failed reg:d330 Oct 16 19:47:35 beta kernel: [ 8534.432060] af9013: I2C read failed reg:9bee Oct 16 19:47:39 beta kernel: [ 8538.456051] af9013: I2C read failed reg:d330 Oct 16 19:47:43 beta kernel: [ 8542.480055] af9013: I2C read failed reg:d330 Oct 16 19:47:47 beta kernel: [ 8546.504050] af9013: I2C read failed reg:d330 Oct 16 19:47:51 beta kernel: [ 8550.528048] af9013: I2C read failed reg:9bee Oct 16 19:47:55 beta kernel: [ 8554.552056] af9013: I2C read failed reg:d330 Oct 16 19:47:59 beta kernel: [ 8558.576062] af9013: I2C read failed reg:d330 Oct 16 19:48:03 beta kernel: [ 8562.600056] af9013: I2C read failed reg:d330 Oct 16 19:48:07 beta kernel: [ 8566.624074] af9013: I2C read failed reg:9bee Oct 16 19:48:11 beta kernel: [ 8570.648052] af9013: I2C read failed reg:d330 Oct 16 19:48:15 beta kernel: [ 8574.672053] af9013: I2C read failed reg:d330 Oct 16 19:48:19 beta kernel: [ 8578.696059] af9013: I2C read failed reg:d330 Oct 16 19:48:23 beta kernel: [ 8582.720039] af9013: I2C read failed reg:9bee Oct 16 19:48:27 beta kernel: [ 8586.744056] af9013: I2C read failed reg:d330 Oct 16 19:48:31 beta kernel: [ 8590.768039] af9013: I2C read failed reg:d330 Oct 16 19:48:35 beta kernel: [ 8594.792053] af9013: I2C read failed reg:d330 Oct 16 19:48:39 beta kernel: [ 8598.816066] af9013: I2C read failed reg:9bee Oct 16 19:48:43 beta kernel: [ 8602.840054] af9013: I2C read failed reg:9bee Oct 16 19:48:47 beta kernel: [ 8606.864133] af9013: I2C read failed reg:d330 Oct 16 19:48:51 beta kernel: [ 8610.888106] af9013: I2C write failed reg:ae00 len:1 Oct 16 19:48:55 beta kernel: [ 8614.912052] af9013: I2C read failed reg:9bee Oct 16 19:48:59 beta kernel: [ 8618.936056] af9013: I2C read failed reg:9bee The host machine has now slowed to a crawl and I have to remove the stick(s) and reboot to recover. I'm currently on hg version 14319:37581bb7e6f1, on a debian-squeeze system, kernel 2.6.32. I've googled and found various people seeing similar problems but have yet to come across a solution. Would anyone have any suggestions (note if I switch back to firmware 4.65 with just the Tevion stick things are fine - I'd like to use the KWorld stick if possible though)? Thanks, -- Dave Cunningham dave at upsilon org uk PGP KEY ID: 0xA78636DC -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [linux-dvb] [bug] AF9015 message WARNING: tuning failed!!!
39723 4 snd_seq_oss,snd_seq_midi_event snd_seq_device 4109 2 snd_seq_oss,snd_seq snd_pcm_oss30331 0 snd_mixer_oss 12481 1 snd_pcm_oss snd_hda_codec_realtek 187652 1 qt1010 4461 1 snd_hda_intel 16732 2 af9013 17817 1 snd_hda_codec 42659 2 snd_hda_codec_realtek,snd_hda_intel snd_pcm50564 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec dvb_usb_af9015 24963 0 snd_timer 14785 2 snd_seq,snd_pcm snd39369 14 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_co dec_realtek,snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer dvb_usb15353 1 dvb_usb_af9015 dvb_core 72670 1 dvb_usb snd_page_alloc 5445 2 snd_hda_intel,snd_pcm Syslog when connecting cold device (debug level 3) : usb 1-3: new high speed USB device using ehci_hcd and address 22 af9015_usb_probe: interface:0 af9015_eeprom_hash: eeprom sum=37ec4ddf af9015_read_config: IR mode:4 af9015_read_config: TS mode:0 af9015_read_config: [0] xtal:2 set adc_clock:28000 af9015_read_config: [0] IF1:36125 af9015_read_config: [0] MT2060 IF1:5888 af9015_read_config: [0] tuner id:134 af9015_identify_state: reply:01 af9015_download_firmware: dvb-usb: found a 'KWorld USB DVB-T TV Stick II (VS-DVB-T 395U)' in cold state, will try to load a firmware usb 1-3: firmware: requesting dvb-usb-af9015.fw dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw' dvb-usb: found a 'KWorld USB DVB-T TV Stick II (VS-DVB-T 395U)' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (KWorld USB DVB-T TV Stick II (VS-DVB-T 395U)) af9013: firmware version:4.95.0 af9015_af9013_frontend_attach: init I2C af9015_i2c_init: Quantek QT1010 successfully identified. input: IR-receiver inside an USB DVB receiver as /devices/pci:00/:00:1d.7/usb1/1-3/input/input12 dvb-usb: schedule remote query interval to 150 msecs. dvb-usb: KWorld USB DVB-T TV Stick II (VS-DVB-T 395U) successfully initialized and connected. DVB: registering adapter 0 frontend 0 (Afatech AF9013 DVB-T)... af9015_tuner_attach: af9015_init: af9015_init_endpoint: USB speed:3 af9015_download_ir_table: and on disconnection: usb 1-3: USB disconnect, address 22 dvb-usb: KWorld USB DVB-T TV Stick II (VS-DVB-T 395U) successfully deinitialized and disconnected. af9015_usb_device_exit: af9015_i2c_exit: input device has been disconnected ls -l /dev/dvb/adapter0/ : total 0 crw-rw 1 root video 212, 4 Oct 6 12:43 demux0 crw-rw 1 root video 212, 5 Oct 6 12:43 dvr0 crw-rw 1 root video 212, 3 Oct 6 12:43 frontend0 crw-rw 1 root video 212, 7 Oct 6 12:43 net0 dvbscan -uvvt1 /usr/share/dvb/dvb-t/uk-Rowridge : scanning /usr/share/dvb/dvb-t/uk-Rowridge using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 489833000 0 3 9 1 0 0 0 initial transponder 53000 0 2 9 3 0 0 0 initial transponder 545833000 0 2 9 3 0 0 0 initial transponder 562167000 0 3 9 1 0 0 0 initial transponder 513833000 0 3 9 1 0 0 0 initial transponder 570167000 0 3 9 1 0 0 0 tune to: 489833000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_16:TRANSM ISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE tuning status == 0x03 tuning status == 0x03 tuning status == 0x03 tuning status == 0x03 tuning status == 0x03 tuning status == 0x03 tuning status == 0x03 tuning status == 0x03 tuning status == 0x03 tuning status == 0x03 WARNING: tuning failed!!! tune to: 489833000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_16:TRANSM ISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) tuning status == 0x03 tuning status == 0x03 tuning status == 0x03 tuning status == 0x03 tuning status == 0x03 tuning status == 0x03 tuning status == 0x03 tuning status == 0x03 tuning status == 0x03 tuning status == 0x03 WARNING: tuning failed!!! ... repeated for each frequency ERROR: initial tuning failed dumping lists (0 services) Done. Thanks for any help. -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Dave Cunningham dave at upsilon org uk PGP KEY ID: 0xA78636DC -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problems with Freecom USB DVB-T dongles
In message +ay15vcwvxdmf...@echelon.upsilon.org.uk, dave cunningham wrote Hi, I'm having problems with a pair of Freecom USB dongles and am wondering if anyone has any pointers? snip In dmesg at boot I see one message for each device dvb-usb: recv bulk message failed: -110 Other than this everything seems OK. The system is running MythTV Backend (0.23) and I can have them both recording simultaneously as I would expect. At some point however I start to get floods of messages to the console (repeats of dvb-usb: recv bulk message failed: -110) and the system slows down to a crawl. snip I'm still looking for any suggestions. From a brief look at the source this message seems to be coming from a call to usb_bulk_msg. Given that the dongles are OK in a via system does this likely suggest a compatibility issue with the USB host controller on the AMD 760G board? I'm I likely to get anywhere trying to debug the code or will a USB analyser be required to work out what's going on? -- Dave Cunningham dave at upsilon org uk PGP KEY ID: 0xA78636DC -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Problems with Freecom USB DVB-T dongles
Hi, I'm having problems with a pair of Freecom USB dongles and am wondering if anyone has any pointers? The dongles appear identical, Freecom Art No. 25452. and have the same USB descriptors, ID 14aa:0221. In the boot log they show as WideView WT-220U PenType Receiver (Typhoon/Freecom), using firmware dvb-usb-wt220u-02.fw. I have been using these dongles in a Via Epia 15000 system, running Debian Lenny i686 for the last 18ish months without issue. I've just moved them to an AMD 760 based motherboard (Sempron processor) running Debian Squeeze x86_64. The dongles do function up to a point. In dmesg at boot I see one message for each device dvb-usb: recv bulk message failed: -110 Other than this everything seems OK. The system is running MythTV Backend (0.23) and I can have them both recording simultaneously as I would expect. At some point however I start to get floods of messages to the console (repeats of dvb-usb: recv bulk message failed: -110) and the system slows down to a crawl. The only way I've found to recover from this is to shutdown mythbackend and physically remove the dongles from the system. At this point I get a few messages dvb-usb: recv bulk message failed: -23 then I guess the driver is unloaded and the system appears to recover fully. I can now plug the dongles back in and they appear to function again until the next time. I've tried unloading the dvb_usb_dtt200u when I get the flood but I get an error saying the device is in use. I'm not sure what's triggering the problem - sometimes it'll kick in after 10 minutes, the last fail came after ~10 hours. I've tried a few versions of the V4L code base but am seeing the same in each. From googling it seems that various people have experienced similar issues but I've yet to find anyone offering a solution. Any ideas? -- Dave Cunningham dave at upsilon org uk PGP KEY ID: 0xA78636DC -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
kernel oops with TT S2-3200
May 22 23:19:31 beta kernel: [ 98.472002] 0 88007c1a5630 88007c1a5608 88007cf66000 88007cf4a000 May 22 23:19:31 beta kernel: [ 98.472002] [a068d9b6] ? __ir_input_register+0x264/0x308 [ir_core] May 22 23:19:31 beta kernel: [ 98.472002] [a069848e] ? budget_ci_attach+0x25c/0xc52 [budget_ci] May 22 23:19:31 beta kernel: [ 98.472002] [a065988c] ? saa7146_init_one+0x442/0x566 [saa7146] May 22 23:19:31 beta kernel: [ 98.472002] [81060e3c] ? do_work_for_cpu+0x0/0x1b May 22 23:19:31 beta kernel: [ 98.472002] [81197ad5] ? local_pci_probe+0x12/0x16 May 22 23:19:31 beta kernel: [ 98.472002] [81060e47] ? do_work_for_cpu+0xb/0x1b May 22 23:19:31 beta kernel: [ 98.472002] [81063ea5] ? kthread+0x75/0x7d May 22 23:19:31 beta kernel: [ 98.472002] [81011aea] ? child_rip+0xa/0x20 May 22 23:19:31 beta kernel: [ 98.472002] [81063e30] ? kthread+0x0/0x7d May 22 23:19:31 beta kernel: [ 98.472002] [81011ae0] ? child_rip+0x0/0x20 May 22 23:19:31 beta kernel: [ 98.472002] RSP 88007cf67db0 May 22 23:19:31 beta kernel: [ 98.476558] ---[ end trace fef3457bebe88aec ]--- -- Dave Cunningham dave at upsilon org uk PGP KEY ID: 0xA78636DC -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
