On 17.01.2015 13:09, Hans Verkuil wrote:
Thanks. This was with one frontend? And what was the exact sequence of commands
used to replicate this?
Sorry, but I need precise details of how you reproduce this, especially since I
can't reproduce it.
This test was run on first front end.
I just started "w_scan -fs -s S13E0 -D0c -a 4" (which mean: do satellite
channel
scan using S13E0 initial transponder list on first DiSEqC port on
adapter 4) and
waited until error appeared in "dmesg --follow". It may take some time
(for me
in average 5-15 minutes)
I'm pretty sure there are multiple issues here, one of them is fixed by my vb2
patch, but this page fault is almost certainly a separate problem.
Based on past reports there is also a possible problem with multiple frontends,
but I don't have hardware like that and even if I had I am not sure I would be
able to test it properly. Besides, that issue seemed to be unrelated to the
vb2 conversion. It's all pretty vague, though.
IMHO: I also think problem is with multiple front ends,
because on some usage patterns problem almost go away
IMHO: page fault problem IS related to the vb2 conversion, because
1) I did not have this problem on kernel 3.13.10
2) during bisection this error appeared exactly on conversation commit
Can we test multiple front ends version? Because you do not have hardware
I propose to test it other way around: can you make patch which disables or
ignores one front end on my hardware (TBS 6981)?
Raimonds Cicans
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
