Thread: firewire issue when running dvswitch/dvgrab
Brought to you by:
aeb,
bencollins
From: Erwann T. <erw...@su...> - 2014-12-02 11:01:40
|
Hello list, I am facing a problem when using dvswitch and a firewire cam. After having started dvswitch and dvsource, i wait for 2 or 3 minutes (sometimes less), and dvsource looses the firewire stream, with this message in log files: firewire_ohci 0000:05:00.0: DMA context IR0 has stopped, error code: evt_descriptor_read I tried to turn on debugging messages: # rmmod firewire_ohci # modprobe firewire_ohci debug=7 # echo 8 > /proc/sysrq-trigger ... no crashes anymore! (except filling debug files, it works like a charm for hours) <- that is what i wrote to dvswitch-devel ML, but it eventually crashes, much more lately though. After this error, the computer usually freezes for about 5 minutes and then comes back to life. Upon advices of Carl@dvswitch-devel, i ran dvgrab -debug video instead of using the whole dvswitch suite. The problem still happens, and i don't have more information from dvgrab's debug output. Finally, on more information i've discovered this morning: these issues happens when the laptop is on battery. Until now, i don't face any issue when plugged to AC. My setup is as follow: Macbook pro with debian stable (wheezy + backports) Sony HVR-A1E firewire cam linux-image-3.16-0.bpo.3-amd64 (it used to be 3.2.0, i tried to upgrade to get rid of these crashes) dvswitch, dvsink, dvsource 0.8.3.6-1+b2 dvgrab 3.5-2 05:00.0 FireWire (IEEE 1394): LSI Corporation FW643 [TrueFire] PCIe 1394b Controller (rev 07) Is there something wrong with my setup? Any idea about how to find the issue? Any help would be greatly appreciated :) Cheers, Erwann |
From: Carl K. <ca...@pe...> - 2014-12-02 14:53:27
|
ignore dvswitch for now, just use dvgrab until this is worked out. For the list: dvswitch wraps dvgrab. > these issues > happens when the laptop is on battery. Until now, i don't face any issue > when plugged to AC. How good is the laptop's battery? Like will it run the laptop for more than 20 minutes? The only thing I can really think of that should matter is power management, like the CPU slows down after a few minutes. Can you disable anything like that? Or change everything to go into power save mode sooner, like 30 seconds and see if the problem starts sooner. What is powering the DV camera? (camera battery or power adaptor) Can you change the power source of the DV cam and try dvgrab again (ignore dvswitch for now) On Tue, Dec 2, 2014 at 4:43 AM, Erwann Thoraval < erw...@su...> wrote: > Hello list, > > I am facing a problem when using dvswitch and a firewire cam. > > After having started dvswitch and dvsource, i wait for 2 or 3 minutes > (sometimes less), and dvsource looses the firewire stream, with this > message in log files: > > firewire_ohci 0000:05:00.0: DMA context IR0 has stopped, error code: > evt_descriptor_read > > I tried to turn on debugging messages: > # rmmod firewire_ohci > # modprobe firewire_ohci debug=7 > # echo 8 > /proc/sysrq-trigger > > ... no crashes anymore! (except filling debug files, it works like a > charm for hours) <- that is what i wrote to dvswitch-devel ML, but it > eventually crashes, much more lately though. > > After this error, the computer usually freezes for about 5 minutes and > then comes back to life. > > Upon advices of Carl@dvswitch-devel, i ran dvgrab -debug video instead > of using the whole dvswitch suite. The problem still happens, and i > don't have more information from dvgrab's debug output. > > Finally, on more information i've discovered this morning: these issues > happens when the laptop is on battery. Until now, i don't face any issue > when plugged to AC. > > > My setup is as follow: > Macbook pro with debian stable (wheezy + backports) > Sony HVR-A1E firewire cam > > linux-image-3.16-0.bpo.3-amd64 (it used to be 3.2.0, i tried to upgrade > to get rid of these crashes) > dvswitch, dvsink, dvsource 0.8.3.6-1+b2 > dvgrab 3.5-2 > 05:00.0 FireWire (IEEE 1394): LSI Corporation FW643 [TrueFire] PCIe > 1394b Controller (rev 07) > > > Is there something wrong with my setup? > Any idea about how to find the issue? > > Any help would be greatly appreciated :) > > Cheers, > Erwann > > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > > http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk > _______________________________________________ > mailing list Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux1394-user > -- Carl K Aaron Swartz believed that you literally ought to be asking yourself all the time: "What is most important thing I could be working on in the world right now, and if you're not working on it, why aren't you?" |
From: Clemens L. <cl...@la...> - 2014-12-02 18:35:00
|
Erwann Thoraval wrote: > firewire_ohci: DMA context IR0 has stopped, error code: evt_descriptor_read This message means that the controller tried to read something from main memory, but failed. Complete memory read failures are not really possible, so the most likely cause is that the response from the memory controller was not received fast enough. > After this error, the computer usually freezes for about 5 minutes and > then comes back to life. Strange. Any other messages in the system log when this happens? > Finally, on more information i've discovered this morning: these issues > happens when the laptop is on battery. Until now, i don't face any issue > when plugged to AC. It might be possible that the CPU goes into a deeper sleep mode when on battery, and takes longer to wake up and serve DMA requests. > I tried to turn on debugging messages: > ... no crashes anymore! (except filling debug files, it works like a > charm for hours) <- that is what i wrote to dvswitch-devel ML, but it > eventually crashes, much more lately though. If the CPU has more work, it goes to sleep less often. Could you try to disable CPU frequency switching? Regards, Clemens |