Project

General

Profile

Actions

Bug #5174

open

PowerUp fails after a very long delay: 17 seconds

Added by rousseau 6 months ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
-
Start date:
06/09/2021
Due date:
% Done:

0%

Spec Reference:

Description

I am using the simbank96 (remotely) and I have issues with some slots.

When the Power Up fails the reader answers after a very long delay of 17 seconds.
The pcscd trace contains:

12181476 [140119642187520] <- 00000F 80 00 00 00 00 07 3D 41 FE 00 
00000075 [140119642187520] commands.c:246:CmdPowerOn Card absent or mute
00000045 [140119642187520] commands.c:275:CmdPowerOn() Power up with 5V failed. Try with auto.
00000048 [140119642187520] -> 00000F 62 00 00 00 00 07 3E 03 00 00 
17178026 [140119642187520] <- 00000F 80 00 00 00 00 07 3E 41 FE 00 
00000090 [140119642187520] commands.c:246:CmdPowerOn Card absent or mute
00000035 [140119642187520] commands.c:275:CmdPowerOn() Power up with 1.8V failed. Try with 3V.
00000091 [140119642187520] -> 00000F 62 00 00 00 00 07 3F 02 00 00 
17177975 [140119642187520] <- 00000F 80 00 00 00 00 07 3F 41 FE 00 
00000069 [140119642187520] commands.c:246:CmdPowerOn Card absent or mute
00000046 [140119642187520] commands.c:275:CmdPowerOn() Power up with 3V failed. Try with 5V.
00000038 [140119642187520] ifdhandler.c:1252:IFDHPowerICC() PowerUp failed

I don't know if the card is faulty or if the problem is elsewhere. Electrical issue?
My problem is that a timeout of 17 seconds is very long.

I already reported a similar problem in https://osmocom.org/issues/4815. The timeout was changed from 60 seconds to 1.4 second.
I don't know why I get a 17 seconds timeout here.

I have the problem for the following readers (from pcsc_scan):

 Reader 9: sysmocom - s.f.m.c. GmbH sysmoOCTSIM [CCID] (6b44014933353553202020341b3815ff) 01 01
  Event number: 0
  Card state: Card inserted, Unresponsive card, 
 Reader 10: sysmocom - s.f.m.c. GmbH sysmoOCTSIM [CCID] (6b44014933353553202020341b3815ff) 01 02
  Event number: 0
  Card state: Card inserted, Unresponsive card, 
 Reader 15: sysmocom - s.f.m.c. GmbH sysmoOCTSIM [CCID] (6b44014933353553202020341b3815ff) 01 07
  Event number: 0
  Card state: Card inserted, Unresponsive card, 

These are slots 2, 3 & 8 of the second sysmoOCTSIM.

Actions #1

Updated by roh 6 months ago

  • Assignee set to Hoernchen

currently installed firmware version on the readers is 0.2.56-26b8

Actions #2

Updated by Hoernchen 6 months ago

Please take a look at the usb ccid exchanges using wireshark: is this actually a delay related to messages from/to the device, or pcscd being overly patient? (if in doubt attach a capture please)

Actions #3

Updated by rousseau 6 months ago

Hoernchen wrote:

Please take a look at the usb ccid exchanges using wireshark: is this actually a delay related to messages from/to the device, or pcscd being overly patient? (if in doubt attach a capture please)

The response RDR_to_PC_DataBlock (80h) is coming from the reader after 17178026 μs (around 17 seconds). pcscd is patient and waits for the reader to answer. The driver does not fail after a USB read timeout for example.
The reader is very slow to answer the PC_to_RDR_IccPowerOn command (62h).

I don't know if the problem is a dead SIM card, or a problem with the reader.
Joachim Steiger already replaced the 3 problematic cards but the problem is still present. Joachim will replace the complete octsim reader board2 on Friday.

In any case a delay of 17 seconds is very long. Since the driver tries to power up using 5V, 1.8V and 3V the total is 17 * 3 = 51 seconds.

Actions #4

Updated by Hoernchen 2 months ago

So, what happened to this? Was the board replaced? I can't reproduce the issue, but it's quite possible that I accidentally fixed this already...

Actions #5

Updated by Hoernchen 2 months ago

ping roh ?

Actions #6

Updated by roh about 2 months ago

i think these slots have mechanical issues which require disassembly of the whole unit to resolve
the boards have not been replaced yet.

but feel free to update the fw and see if the handling of the issue gets better - this may be an interesting testcase?

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)