Hello,
since the upgrade to VDR version 1.6.0 the entire system will randomly freeze when using multiple instances of VDR. This issue could be reproduced by using the commandline switch -D to specify the DVB devices.
Unfortunately there are no logs which could identify the problem .. it only freezes.
Example: * vdr = "-D 0 -D 1" * vdrdevel = "-D 2 -D 3"
I am running the very latest version from e-tobi (multipatch). vdrdevel is the same version as vdr, but repacked by using the buildpackage option SPECIAL_VDR_SUFFIX=devel. Using the older 1.5.13 setup with the same hardware (4x cinergy c ~ mantis) is working like charm.
I don't think it is a driver / module problem, because running a single VDR instance with all devices attached to it won't crash. But when starting one instance which is only using two devices, the system will freeze .. even if there's no other vdr process running.
Regards, Matthias
On 04/30/08 09:24, Matthias Kortstiege wrote:
Hello,
since the upgrade to VDR version 1.6.0 the entire system will randomly freeze when using multiple instances of VDR. This issue could be reproduced by using the commandline switch -D to specify the DVB devices.
Unfortunately there are no logs which could identify the problem .. it only freezes.
Example:
- vdr = "-D 0 -D 1"
- vdrdevel = "-D 2 -D 3"
I am running the very latest version from e-tobi (multipatch). vdrdevel is the same version as vdr, but repacked by using the buildpackage option SPECIAL_VDR_SUFFIX=devel. Using the older 1.5.13 setup with the same hardware (4x cinergy c ~ mantis) is working like charm.
Does this mean that version 1.5.13 worked, but 1.5.14 doesn't?
Klaus
Klaus Schmidinger schrieb:
On 04/30/08 09:24, Matthias Kortstiege wrote:
Hello,
since the upgrade to VDR version 1.6.0 the entire system will randomly freeze when using multiple instances of VDR. This issue could be reproduced by using the commandline switch -D to specify the DVB devices.
Unfortunately there are no logs which could identify the problem .. it only freezes.
Example:
- vdr = "-D 0 -D 1"
- vdrdevel = "-D 2 -D 3"
I am running the very latest version from e-tobi (multipatch). vdrdevel is the same version as vdr, but repacked by using the buildpackage option SPECIAL_VDR_SUFFIX=devel. Using the older 1.5.13 setup with the same hardware (4x cinergy c ~ mantis) is working like charm.
Does this mean that version 1.5.13 worked, but 1.5.14 doesn't?
Klaus
Did not tested it with other versions. I've updated from 1.5.13 to 1.6.0. Could this be an issue of the mantis dvb modules (jusst.de/hg/mantis) and ca changes made to vdr in version 1.6.0 ?
Matthias
On 05/02/08 09:54, Matthias Kortstiege wrote:
Klaus Schmidinger schrieb:
On 04/30/08 09:24, Matthias Kortstiege wrote:
Hello,
since the upgrade to VDR version 1.6.0 the entire system will randomly freeze when using multiple instances of VDR. This issue could be reproduced by using the commandline switch -D to specify the DVB devices.
Unfortunately there are no logs which could identify the problem .. it only freezes.
Example:
- vdr = "-D 0 -D 1"
- vdrdevel = "-D 2 -D 3"
I am running the very latest version from e-tobi (multipatch). vdrdevel is the same version as vdr, but repacked by using the buildpackage option SPECIAL_VDR_SUFFIX=devel. Using the older 1.5.13 setup with the same hardware (4x cinergy c ~ mantis) is working like charm.
Does this mean that version 1.5.13 worked, but 1.5.14 doesn't?
Klaus
Did not tested it with other versions. I've updated from 1.5.13 to 1.6.0. Could this be an issue of the mantis dvb modules (jusst.de/hg/mantis) and ca changes made to vdr in version 1.6.0 ?
In order to further track down the problem, please verify that version 1.5.13 works, and then try 1.5.14, 1.5.15 etc., until you find a version that doesn't work. Do all tests with exactly the same driver, so that a driver problem can be ruled out.
Klaus
-
Klaus Schmidinger -
Matthias Kortstiege