I am testing FX30S with Sierra VZN ECC SIM.
I loaded the latest Verizon Firmware found on the Sierra source site:
FX30_WP77xx_full_R14.1.1.002-verizon-SWI9X06Y_02.22.12.00.cwe
After resolving dial script CID to correspond to context ID #3, I am able to ping 8.8.8.8 (thanks for advice on earlier issue).
Many errors are generated on legato syslog (logread), some of which correspond to access and data sent on serial port (9 pin DIN connector).
When usign terminal app (i.e., minicom) on linux host, intermittent responses are received to commands sent when these errors are generated. Frequently no response is received - no keystrokes echoed (even after ate1 is sent). The Following is an example of the errors received on sending an AT command:
Mar 29 12:35:08 fx30s user.err DS_MUX:[948]: Timer 2 set successfully
Mar 29 12:35:08 fx30s user.err DS_MUX:[948]: Listening FD set 7
Mar 29 12:35:08 fx30s user.err DS_MUX:[948]: Listening FD set 8
Mar 29 12:35:08 fx30s user.err DS_MUX:[948]: Listening FD set 10
Mar 29 12:35:08 fx30s user.err DS_MUX:[948]: Listening FD set 12
Mar 29 12:35:08 fx30s user.err DS_MUX:[948]: Listening FD set 13
Mar 29 12:35:08 fx30s user.err DS_MUX:[948]: Listening FD set 14
Mar 29 12:35:08 fx30s user.err DS_MUX:[948]: Num FD set 6
Mar 29 12:35:08 fx30s user.warn kernel: [ 8635.830219] irq 50, desc: ce99bd80, depth: 0, count: 0, unhandled: 0
Mar 29 12:35:08 fx30s user.warn kernel: [ 8635.830252] ->handle_irq(): c0232e34, msm_gpio_irq_handler+0x0/0x150
Mar 29 12:35:08 fx30s user.warn kernel: [ 8635.830298] ->irq_data.chip(): c0e18ba8, gic_chip+0x0/0x74
Mar 29 12:35:08 fx30s user.warn kernel: [ 8635.830336] ->action(): (null)
Mar 29 12:35:08 fx30s user.warn kernel: [ 8635.830356] IRQ_NOPROBE set
Mar 29 12:35:08 fx30s user.warn kernel: [ 8635.830374] IRQ_NOREQUEST set
Mar 29 12:35:08 fx30s user.warn kernel: [ 8635.830392] IRQ_NOTHREAD set
Mar 29 12:35:09 fx30s user.err DS_MUX:[948]: Timer 2 set successfully
Mar 29 12:35:09 fx30s user.err DS_MUX:[948]: Listening FD set 7
Mar 29 12:35:09 fx30s user.err DS_MUX:[948]: Listening FD set 8
Mar 29 12:35:09 fx30s user.err DS_MUX:[948]: Listening FD set 10
Mar 29 12:35:09 fx30s user.err DS_MUX:[948]: Listening FD set 12
Mar 29 12:35:09 fx30s user.err DS_MUX:[948]: Listening FD set 13
Mar 29 12:35:09 fx30s user.err DS_MUX:[948]: Listening FD set 14
Mar 29 12:35:09 fx30s user.err DS_MUX:[948]: Num FD set 6
Mar 29 12:35:09 fx30s user.err DS_MUX:[948]: Timer 2 set successfully
Mar 29 12:35:09 fx30s user.err DS_MUX:[948]: Listening FD set 7
Mar 29 12:35:09 fx30s user.err DS_MUX:[948]: Listening FD set 8
Mar 29 12:35:09 fx30s user.err DS_MUX:[948]: Listening FD set 10
Mar 29 12:35:09 fx30s user.err DS_MUX:[948]: Listening FD set 12
Mar 29 12:35:09 fx30s user.err DS_MUX:[948]: Listening FD set 13
Mar 29 12:35:09 fx30s user.err DS_MUX:[948]: Listening FD set 14
Mar 29 12:35:09 fx30s user.err DS_MUX:[948]: Num FD set 6
These errors wer not seen on the same device with the same test usign other FW/SIMs (ATT FW and ATT SIM tested).
Also, after encountering the same issue yesterday, simiar errors were received. Leaving the FX30 up overnight and found syslog spewing errors not stop overnight. The logs being sent were all the same. An example follows:
<...>
Mar 29 09:50:36 fx30s user.err kernel: [52757.861990] ul_timeout: UL delayed ts=13062.081206785
Mar 29 09:50:36 fx30s user.err kernel: [52757.960445] ul_timeout: UL delayed ts=13062.081206785
<...>
Customer use case would involve use of VZN on FX30S with ppp connection.
Can you provide analysis of errors observed?
Is a FW update available to correct the condition?
Thanks
