General

Profile

Victor S

  • Registered on: 2019-11-11
  • Last connection: 2020-05-31

Issues

Activity

2020-05-16

03:35 Tvheadend Bug #5898: TBS 6909x PCIE + Hauppauge QuadHD PCIE same host Crash
Flole Systems wrote:
> Just don't use tvheadend, if you need the code write it yourself.
>
> Let me guess: No mod...
Victor S
03:28 Tvheadend Bug #5898: TBS 6909x PCIE + Hauppauge QuadHD PCIE same host Crash
Very well, I fixed it. Due to such attitude here, if someone needs a fix for it too, guess what? *Figure out and do i... Victor S

2020-05-15

15:17 Tvheadend Bug #5898: TBS 6909x PCIE + Hauppauge QuadHD PCIE same host Crash
Great. Problem is not personal, neither a driver problem, apparently. You could then just close this forum https://tv... Victor S
14:57 Tvheadend Bug #5898: TBS 6909x PCIE + Hauppauge QuadHD PCIE same host Crash
Flole Systems wrote:
> It's a complete dump of all memory related to tvheadend at the time of the crash. You need to...
Victor S
14:48 Tvheadend Bug #5898: TBS 6909x PCIE + Hauppauge QuadHD PCIE same host Crash
Whatever it wrote in core.5027 is 3.8 GB. OMG! Victor S
14:45 Tvheadend Bug #5898: TBS 6909x PCIE + Hauppauge QuadHD PCIE same host Crash
Here, just crashed when scanned 18 out of 64 freqs.
2020-05-15 15:42:20.177 [ DEBUG] mpegts: 11262H in Eutelsat...
Victor S
14:42 Tvheadend Bug #5898: TBS 6909x PCIE + Hauppauge QuadHD PCIE same host Crash
Flole Systems wrote:
> The first one is just a deadlock, as we know the source for that now (that was the card overh...
Victor S
14:33 Tvheadend Bug #5898: TBS 6909x PCIE + Hauppauge QuadHD PCIE same host Crash
Flole Systems wrote:
> It will produce a stacktrace in gdb and halt, you need to manually dump the core then if you ...
Victor S
14:30 Tvheadend Bug #5898: TBS 6909x PCIE + Hauppauge QuadHD PCIE same host Crash
saen acro wrote:
> Just to be clear. exact model of CPU and Mother board?
> Is latest bios installed?
P7P55 Pro,...
Victor S
14:28 Tvheadend Bug #5898: TBS 6909x PCIE + Hauppauge QuadHD PCIE same host Crash
Flole Systems wrote:
> Did you type "run" after doing that to start it up?
Sure did. It ran, crashed and I see no...
Victor S

Also available in: Atom