Strange behavior of several instances of getstream I tried to run several instances of getstream to multicast DVB-T into network. First instance was started ok and I was able to see stream. Second also was ok. Third version start throwing following error messages: 2009-03-06 01:34:45.897 streamudp: send didnt send all -1 of 1316 byte - Resource temporarily unavailable After this i put all configs for 3 adapters into single file and tried to run one getstream but stopped to do this after set of errors: 2009-03-06 01:34:45.897 streamudp: send didnt send all -1 of 1316 byte - Resource temporarily unavailable 2009-03-06 01:34:45.897 streamudp: send didnt send all -1 of 1316 byte - Resource temporarily unavailable 2009-03-06 01:34:45.897 streamudp: send didnt send all -1 of 1316 byte - Resource temporarily unavailable 2009-03-06 01:34:47.037 fe: Adapter 1 Status: 0x00 () 2009-03-06 01:34:47.037 demux: read in dvr_read returned with errno 75 / Value too large for defined data type 2009-03-06 01:34:47.037 demux: read in dvr_read returned with errno 75 / Value too large for defined data type 2009-03-06 01:34:49.456 demux: read in dvr_read returned with errno 75 / Value too large for defined data type 2009-03-06 01:34:49.456 demux: read in dvr_read returned with errno 75 / Value too large for defined data type 2009-03-06 01:34:49.456 dvr: lockup of DVB card detected - trying to reanimate via bouncing filter 2009-03-06 01:34:50.337 demux: read in dvr_read returned with errno 75 / Value too large for defined data type 2009-03-06 01:34:50.337 demux: read in dvr_read returned with errno 75 / Value too large for defined data type 2009-03-06 01:34:52.876 fe: Adapter 1 Status: 0x00 () 2009-03-06 01:34:52.876 demux: read in dvr_read returned with errno 75 / Value too large for defined data typ What is this? Is this problems with configuration? Or hardware? Any suggestions are welcome.
On Thu, Mar 05, 2009 at 04:51:42PM +0200, Serg Gulko wrote:
Strange behavior of several instances of getstream
I tried to run several instances of getstream to multicast DVB-T into network. First instance was started ok and I was able to see stream. Second also was ok. Third version start throwing following error messages:
2009-03-06 01:34:45.897 streamudp: send didnt send all -1 of 1316 byte - Resource temporarily unavailable
I am seeing similar things happen on a Celeron 1000 starting the 3rd DVB-S Card - it starts loosing TS packets and complains about CC discontinuity and read/write errors. CPU will not be saturated but even shoveling 3 DVB-S feeds via a normal 33Mhz 32bit PCI bus can be challenging depending on the used hardware.
What is this? Is this problems with configuration? Or hardware? Any suggestions are welcome.
So my best guess is that your hardware has a bottleneck somewhere. Flo -- Florian Lohoff flo@rfc822.org +49-171-2280134 Those who would give up a little freedom to get a little security shall soon have neither - Benjamin Franklin
participants (2)
-
Florian Lohoff -
Serg Gulko