Opened 13 years ago
Closed 12 years ago
#1841 closed defect (wontfix)
one reader works, same two reader always timeout after "random" time /PCSC or Phoenix/
Reported by: | RoboSK | Owned by: | |
---|---|---|---|
Priority: | major | Component: | Reader |
Severity: | medium | Keywords: | |
Cc: | robo.info.mail@… | Sensitive: | no |
Description
Revision
svn5190 / svn1809_0.99.4a / svn3144_1.00 - same problem...
When the issue occurs
always after "random" time
problem:
-one card reader works perfect, no timeout, always +-200ms
-two reader always problem -> reader timeout after "random" time
HW:
2x card cryptowors (Skylink)
HW: tested on 3xPC, different USB (Nvidia,Intel,Via/NEC - PCI card)
kernel:2.6.32 / 2.6.37 / 2.6.37 / 2.6.39-rc6
readers - both same problem:
a) 2x PCSC reader (but i have 4 - all combination same problem), blacklisted ftdi_sio,
ccid-1.4.3, pcsclite-1.7.2 (tested on older version too)
b) 2x Crystal Phoenix (TBS-3102V13 - i have 3 - all combination same problem) - ftdio_sio enabled
combination a) /2x PCSC/
uname -a
Linux TV 2.6.39-rc6-ARCH-dirty #1 SMP PREEMPT Wed May 4 20:49:48 CEST 2011 i686 Intel(R) Atom(TM) CPU 330 @ 1.60GHz GenuineIntel GNU/Linux
lsmod | grep -i ftdi
-nothing-
oscam.conf
[newcamd]
port = 10000@0d03:000004,000008;10001@0d03:000004,000008
oscam.server
[reader]
label = pcsc-001
enable = 1
protocol = pcsc
detect = CD
device = 0
group = 3
emmcache = 1,1,2
caid = 0D03
cardmhz = 357
mhz = 357
services = skylink_cz_free,!skylink_sk_free,skylink_multi
ecmwhitelist = 0D03@04,08,24,28:9C,9F,A5
[reader]
label = pcsc-002
enable = 1
protocol = pcsc
detect = CD
device = 1
group = 4
emmcache = 1,1,2
caid = 0D03
cardmhz = 357
mhz = 357
services = !skylink_cz_free,skylink_sk_free,!skylink_multi
ecmwhitelist = 0D03@04,08,24,28:9C,9F,A5
oscam.user
[account]
user = *
pwd = *
disabled = 0
group = 3
au = pcsc-001
services = skylink_cz_free,!skylink_sk_free,skylink_multi
[account]
user = *
pwd = *
disabled = 0
group = 4
au = pcsc-002
services = !skylink_cz_free,skylink_sk_free,!skylink_multi
oscam.services
[skylink_cz_free]
caid = 0D03
provid = 000004
srvid = 36F6,1F47,13D1,3353,13B4,3338,3355,13D3
[skylink_sk_free]
caid = 0D03
provid = 000004
srvid = 1F42,1F43,1F44,1F41,1F45,13A6,13A7
[skylink_multi]
caid = 0D03
provid = 000008
srvid = 07E9,3360,3351,334D,332D,13AD,5156,13AC,13AE,232F,2330,2334,3334,2329,232B,2333,13BD,2331,2336,3354,13D5,13BA,332C
Attachments (4)
Change History (18)
by , 13 years ago
Attachment: | oscam-log-short.txt added |
---|
comment:1 by , 13 years ago
full debug log = 2.5MB -> upload "413 Request Entity Too Large" - try later...
comment:2 by , 13 years ago
The problem I see in the log is, that user dummy-003 doesn't have the service allowed that he requests. That's why he doesn't get a response.
I doubt that such a huge log is necessary. If it is then you can still use compression.
Edit: Please also note that negative services (those with !) seem to be not necessary in your configuration. Just define the positive ones and all others will be blocked automatically. You would only need negative ones here if you would say something like: Allow all from services x but disallow the few which are defined in services y (they then need to be overlapping obviously). In most setups, it is enough to either define only positive or only negative services.
comment:3 by , 13 years ago
thaks for reply
...dummy-003 doesn't have the service allowed that he requests...
but it is allowed, no ?
2011/05/08 9:47:49 B7801280 c dummy-003 (0D03&000004/13D1/9C:7B7C): timeout (3006 ms) by pcsc-001 (of 1 avail 1) - Nova
dummy-003 -> "skylink_cz_free" -> 13D1
and problem is that channel is tunned example 20min, decoding works and then timeout...
why i remove user name ? :)
[account]
user = dummy-003
pwd = *
disabled = 0
group = 3
au = pcsc-001
services = skylink_cz_free,!skylink_sk_free,skylink_multi
[account]
user = dummy-004
pwd = *
disabled = 0
group = 4
au = pcsc-002
services = !skylink_cz_free,skylink_sk_free,!skylink_multi
comment:4 by , 13 years ago
test with #5230 and changed config without "!" - same problem...
+tested with one PCSC reader and one Phoenix - same problem...
oscam.user
[account]
user = dummy-003
pwd = *
disabled = 0
group = 3
au = pcsc-001
services = skylink_cz_free
[account]
user = dummy-004
pwd = *
disabled = 0
group = 4
au = pcsc-002
services = skylink_sk_free
oscam.server
[reader]
label = pcsc-001
enable = 1
protocol = pcsc
detect = CD
device = 0
group = 3
emmcache = 1,1,2
caid = 0D03
cardmhz = 357
mhz = 357
services = skylink_cz_free
ecmwhitelist = 0D03@04,08,24,28:9C,9F,A5
[reader]
label = pcsc-002
enable = 1
protocol = pcsc
detect = CD
device = 1
group = 4
emmcache = 1,1,2
caid = 0D03
cardmhz = 357
mhz = 357
services = skylink_sk_free
ecmwhitelist = 0D03@04,08,24,28:9C,9F,A5
2011/05/14 9:24:51 B645D280 c dummy-003 (0D03&000004/13D1/9C:CC5D): timeout (3006 ms) by pcsc-001 (of 1 avail 1) - Nova
2011/05/14 9:25:01 B645D280 c dummy-003 (0D03&000004/13D1/9C:660E): timeout (3006 ms) by pcsc-001 (of 1 avail 1) - Nova
2011/05/14 9:25:11 B645D280 c dummy-003 (0D03&000004/13D1/9C:61D5): timeout (3006 ms) by pcsc-001 (of 1 avail 1) - Nova
2011/05/14 9:25:21 B645D280 c dummy-003 (0D03&000004/13D1/9C:CD81): timeout (3005 ms) by pcsc-001 (of 1 avail 1) - Nova
2011/05/14 9:25:31 B645D280 c dummy-003 (0D03&000004/13D1/9C:7EA4): timeout (3005 ms) by pcsc-001 (of 1 avail 1) - Nova
comment:5 by , 13 years ago
If you look at the log, you can always see an entry with a very high ecm time like
2011/05/08 9:47:55 B7477B70 r reader: pcsc-001 ecm: 7B7C real time: 8605 ms
As client timeout is set at 3000ms, you get the timeout before the smartcard returns an answer.
The strange thing is that the fallback reader is asked and gets the answer at the same time as the originally asked one. Why this takes so long? No idea...maybe it's dependend on the card system? Especially if this also happens with phoenix readers, I would doubt that this is an issue of the OSCam implementation of PCSC. The long waiting happens when calling the PCSC API function SCardTransmit so OSCam can't do anything against that. Maybe it's an OS or driver issue.
comment:6 by , 13 years ago
What I just noticed: The syntax of your ecmwhitelist is totally wrong and so it is NOT working at all (just look into WebIf to see the parsed result). Look into the docs or wiki for the correct syntax! Ident should be 6 characters long and you can't define multiple idents separated by a comma. If you define ecmwhitelist for a physical reader it should be absolutely enough to just specify "9C,9F,A5". You normally won't need ident/caid here at all.
comment:7 by , 13 years ago
next weekend i try this:
ecmwhitelist = 0D03@000004:9C,9F,A5;0D03@000008:9C,9F,A5;0D03@000024:9C,9F,A5;0D03@000028:9C,9F,A5
and if problem still exist then it is time to buy 2x smargo...
if is used only one card (A or B) then newer timeout (search log with one week logs) and no one timeout...
thanks
comment:8 by , 13 years ago
I'm having exactly the same issue with 2 Smargo 1.3 with an HD+ (CAID 1843) card each... I have to use 4xxx builds. All new builds just start to produce timeouts, usually after 2-3 days. I'll try to get a full debug log soon.
comment:10 by , 13 years ago
Cc: | added |
---|
comment:11 by , 13 years ago
I think I'm a having a similar problem. And it appeared in mid-May and it only happens on my Skylink ICE card, other cards work just fine. Check this (non-verbose) log: http://pastebin.com/TLHERzUb
Does it look the same?
Right now I'm trying some tricks such as disabling global EMMs, because I've seen global EMMs causing trouble on other of my cards.
comment:13 by , 13 years ago
ccid: 1.4.4-1
for LubosD: cau, kupil som 2x smargo (original) a po uvodnych problemoch #1929 mam po 2 tyzdnoch 0 timeoutou a 0 problemou - snazil som sa rozchodit 2 karty rok, mam kupene 3xPhopenix/Smarmouse(USB), cca 4x PCSC a nic :) -> moja rada, kup origo smargo...
comment:14 by , 12 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Probably this libusb-bug: http://www.libusb.org/ticket/56
Install libusb-1.0.9-rc3 or later.
short debug 255 PCSC