Closed Bug 858611 Opened 12 years ago Closed 12 years ago

[Leo] Unable to connect to data network on AT&T Network

Categories

(Core :: DOM: Device Interfaces, defect)

Product:
Core
Component:
DOM: Device Interfaces
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME
Project Flags:
blocking-b2g leo+

People

(Reporter: tchung, Assigned: mwu)

Details

Attachments

(2 files)

logcat
117.94 KB, text/x-log
Details
radio log
1.74 KB, text/x-log
Details
On the Leo devices, i am unable to connect to the data networks using a AT&T Sim card. with the same SIM, this works on the Unagi. Logcat: 04-05 08:42:42.539: A/libc(140): Fatal signal 11 (SIGSEGV) at 0x34303133 (code=1) 04-05 08:42:42.949: I/DEBUG(139): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 04-05 08:42:42.949: I/DEBUG(139): Build fingerprint: 'qcom/full_leo/leo:4.0.4.0.4.0.4/OPENMASTER/eng.cltbld.20130403.021133:user/test-keys' 04-05 08:42:42.949: I/DEBUG(139): pid: 140, tid: 236 >>> /system/bin/rild <<< 04-05 08:42:42.949: I/DEBUG(139): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 34303133 04-05 08:42:42.949: I/DEBUG(139): r0 34303133 r1 100ff3d8 r2 00000003 r3 00000000 04-05 08:42:42.949: I/DEBUG(139): r4 100ff3d4 r5 00000002 r6 00000000 r7 100feb00 04-05 08:42:42.949: I/DEBUG(139): r8 100ff144 r9 34303133 10 00000073 fp 100feba8 04-05 08:42:42.949: I/DEBUG(139): ip ffffffff sp 100fea38 lr 400e388f pc 400dcab0 cpsr 20000010 04-05 08:42:42.949: I/DEBUG(139): d0 6f742073646e6f20 d1 5f5445535f545361 04-05 08:42:42.949: I/DEBUG(139): d2 5f4b524f57544573 d3 4f495443454c455f 04-05 08:42:42.949: I/DEBUG(139): d4 0000000000000000 d5 0000000000000000 04-05 08:42:42.959: I/DEBUG(139): d6 0000000000000000 d7 0000000000000000 04-05 08:42:42.959: I/DEBUG(139): d8 0000000000000000 d9 0000000000000000 04-05 08:42:42.959: I/DEBUG(139): d10 0000000000000000 d11 0000000000000000 04-05 08:42:42.959: I/DEBUG(139): d12 0000000000000000 d13 0000000000000000 04-05 08:42:42.959: I/DEBUG(139): d14 0000000000000000 d15 0000000000000000 04-05 08:42:42.959: I/DEBUG(139): d16 0000000000000000 d17 0000000000000000 04-05 08:42:42.959: I/DEBUG(139): d18 0000000000000000 d19 0000000000000000 04-05 08:42:42.959: I/DEBUG(139): d20 0000000000000000 d21 0000000000000000 04-05 08:42:42.959: I/DEBUG(139): d22 0000000000000000 d23 0000000000000000 04-05 08:42:42.959: I/DEBUG(139): d24 0000000000000000 d25 0000000000000000 04-05 08:42:42.959: I/DEBUG(139): d26 0000000000000000 d27 0000000000000000 04-05 08:42:42.959: I/DEBUG(139): d28 0000000000000000 d29 0000000000000000 04-05 08:42:42.959: I/DEBUG(139): d30 0000000000000000 d31 0000000000000000 04-05 08:42:42.959: I/DEBUG(139): scr 00000010 04-05 08:42:42.999: I/DEBUG(139): #00 pc 00016ab0 /system/lib/libc.so (strlen) 04-05 08:42:42.999: I/DEBUG(139): #01 pc 0001d88c /system/lib/libc.so (__vfprintf) 04-05 08:42:42.999: I/DEBUG(139): code around pc: 04-05 08:42:42.999: I/DEBUG(139): 400dca90 f7fffc9d bd10fcff e24dd008 e2102003 ..........M.. .. 04-05 08:42:42.999: I/DEBUG(139): 400dcaa0 f5d0f000 f5d0f020 e58d0004 0a00000f .... ........... 04-05 08:42:42.999: I/DEBUG(139): 400dcab0 e5d02000 e3520000 12803001 13a02000 . ....R..0... .. 04-05 08:42:42.999: I/DEBUG(139): 400dcac0 158d3004 1a000004 ea00003e e4d31001 .0......>....... 04-05 08:42:42.999: I/DEBUG(139): 400dcad0 e3510000 0a00003b e58d3004 e59d0004 ..Q.;....0...... 04-05 08:42:42.999: I/DEBUG(139): code around lr: 04-05 08:42:42.999: I/DEBUG(139): 400e386c c010f8cd f8f8f005 c010f8dd b14846e3 .............FH. 04-05 08:42:42.999: I/DEBUG(139): 400e387c 0b00ebc9 bfa845e3 e00346e3 f7f94648 .....E...F..HF.. 04-05 08:42:42.999: I/DEBUG(139): 400e388c 4683e906 f50d9c06 f04f7eb4 f80e0c00 ...F.....~O..... 04-05 08:42:42.999: I/DEBUG(139): 400e389c f8cdcc01 e15bc018 46d09709 9f0646dc ......[....F.F.. 04-05 08:42:42.999: I/DEBUG(139): 400e38ac f0464692 e0040610 46d09709 46dc9f06 .FF........F...F 04-05 08:42:42.999: I/DEBUG(139): memory map around addr 34303133: 04-05 08:42:42.999: I/DEBUG(139): 10001000-10100000 04-05 08:42:42.999: I/DEBUG(139): (no map for address) 04-05 08:42:42.999: I/DEBUG(139): 40005000-40010000 /system/lib/libril.so 04-05 08:42:42.999: I/DEBUG(139): stack: 04-05 08:42:42.999: I/DEBUG(139): 100fe9f8 ffff0208 [vectors] 04-05 08:42:42.999: I/DEBUG(139): 100fe9fc 00000000 04-05 08:42:42.999: I/DEBUG(139): 100fea00 00000000 04-05 08:42:42.999: I/DEBUG(139): 100fea04 100ff244 04-05 08:42:42.999: I/DEBUG(139): 100fea08 00000007 04-05 08:42:42.999: I/DEBUG(139): 100fea0c 00000000 04-05 08:42:42.999: I/DEBUG(139): 100fea10 3539eaf0 04-05 08:42:42.999: I/DEBUG(139): 100fea14 000fe9a8 04-05 08:42:42.999: I/DEBUG(139): 100fea18 00000000 04-05 08:42:42.999: I/DEBUG(139): 100fea1c 00000000 04-05 08:42:42.999: I/DEBUG(139): 100fea20 4000e56d /system/lib/libril.so 04-05 08:42:42.999: I/DEBUG(139): 100fea24 00000001 04-05 08:42:42.999: I/DEBUG(139): 100fea28 100feb2c 04-05 08:42:42.999: I/DEBUG(139): 100fea2c 100ff26c 04-05 08:42:42.999: I/DEBUG(139): 100fea30 df0027ad 04-05 08:42:42.999: I/DEBUG(139): 100fea34 00000000 04-05 08:42:42.999: I/DEBUG(139): #00 100fea38 40100ee1 /system/lib/libc.so 04-05 08:42:42.999: I/DEBUG(139): 100fea3c 34303133 04-05 08:42:42.999: I/DEBUG(139): #01 100fea40 100feb2e 04-05 08:42:42.999: I/DEBUG(139): 100fea44 100ff284 04-05 08:42:42.999: I/DEBUG(139): 100fea48 4000efb8 /system/lib/libril.so 04-05 08:42:42.999: I/DEBUG(139): 100fea4c 00000000 04-05 08:42:42.999: I/DEBUG(139): 100fea50 4000d6fe /system/lib/libril.so 04-05 08:42:42.999: I/DEBUG(139): 100fea54 00000008 04-05 08:42:42.999: I/DEBUG(139): 100fea58 100ff3d8 04-05 08:42:42.999: I/DEBUG(139): 100fea5c 00000002 04-05 08:42:42.999: I/DEBUG(139): 100fea60 100feb98 04-05 08:42:42.999: I/DEBUG(139): 100fea64 402cb1dd /system/lib/libril-qc-1.so 04-05 08:42:42.999: I/DEBUG(139): 100fea68 000001ff 04-05 08:42:42.999: I/DEBUG(139): 100fea6c 100feba8 04-05 08:42:42.999: I/DEBUG(139): 100fea70 0000001b 04-05 08:42:42.999: I/DEBUG(139): 100fea74 00000000 04-05 08:42:42.999: I/DEBUG(139): 100fea78 00000000 04-05 08:42:43.009: I/DEBUG(139): 100fea7c 100feb94 04-05 08:42:43.009: I/DEBUG(139): 100fea80 100feb84 04-05 08:42:43.009: I/DEBUG(139): 100fea84 402cb1c0 /system/lib/libril-qc-1.so 04-05 08:42:43.329: I/Diag_Lib(140): rpc_handle_rpc_call: for Xid: 676, Prog: 31000000, Vers: d17ed9ea, Proc: 00000014 04-05 08:42:43.329: D/QCRIL_RPC(140): Enter qcril_cm_srvsys_event_callback 04-05 08:42:43.329: D/QCRIL_RPC(140): Exit qcril_cm_srvsys_event_callback 04-05 08:42:43.329: I/Diag_Lib(140): rpc_handle_rpc_call: Find Status: 0 Xid: 676 04-05 08:42:43.329: I/ONCRPC(140): oncrpc_proxy_handle_cmd_rpc_call: Dispatching xid: 676 04-05 08:42:43.329: I/ONCRPC(140): oncrpc_xdr_reply_msg_start: Prog: 00000000, Ver: 00000000, Proc: 00000000 Xid: 00000676 04-05 08:42:43.329: I/ONCRPC(140): oncrpc_msg_reply: Prog: 00000000, Ver: 00000000, Proc: 00000000 Xid: 00000676 04-05 08:42:43.329: I/ONCRPC(140): oncrpc_proxy_handle_cmd_rpc_call: Dispatch returned for xid: 676 04-05 08:42:43.619: I/Gonk(131): Cannot read from network, error 0 04-05 08:42:43.619: I/Gonk(131): Socket open for RIL REpro: 1) install 2013-04-03 nightly build on Leo; use a AT&T Sim Card Gecko http://hg.mozilla.org/releases/mozilla-b2g18/rev/d467369d1b0c Gaia 06e0e5ce42bdfb62bdbe38271de6b5b2d9e40e75 BuildID 20130403070204 Version 18.0 2) settings > Cellular & Data > Data Connection = Check 3) select Network Operator > Uncheck Auto selection > and choose search 4) Choose AT&T in the Network operator list 5) Verify it never connects to data Expected: - connects to a valid AT&T data plan Actual: - unable to connect, see logcat snippet.
Triage decision was that since AT&T SIMs are used so much and this will negatively affect testing, we should block on this.
blocking-b2g: leo? → leo+
vincent, are you the right person to take this?
Flags: needinfo?(vchang)
Summary: [Leo] Unable to connect to data plan on AT&T Network → [Leo] Unable to connect to data network on AT&T Network
Michael/Anshul should be the right person to look at this. Does this issue happen on build with Mozilla RIL too?
Flags: needinfo?(vchang)
A rild crash like this is a partner issue. You can try updating your blobs. FYI, above crash is with the reference RIL.
Vincent Liu said he can take a look at this issue.
Please attach QXDM and radio log.
I will try to reproduce this issue in my side. But please still attach detailed log if possible. Thanks.
Attached file logcat —
I can reproduce this issue. The detailed log files are attached. Before crashing, I found some error messages. I/Gecko ( 132): RIL Worker: Error processing operator tuple: Error: Invalid network tuple (should be 5 or 6 digits): TWM I/Gecko ( 132): RIL Worker: Error processing operator tuple: Error: Invalid network tuple (should be 5 or 6 digits): VIBO I/Gecko ( 132): RIL Worker: Error processing operator tuple: Error: MCC could not be parsed from network tuple: WCDMA I/Gecko ( 132): RIL Worker: Error processing operator tuple: Error: Invalid network tuple (should be 5 or 6 digits): forbidden I/Gecko ( 132): RIL Worker: Error processing operator tuple: Error: Invalid network tuple (should be 5 or 6 digits): CHT I/Gecko ( 132): RIL Worker: Error processing operator tuple: Error: Invalid network tuple (should be 5 or 6 digits): Far EasTone I/Gecko ( 132): RIL Worker: Error processing operator tuple: Error: Invalid network tuple (should be 5 or 6 digits): GSM I think we should figure out these errors. Welcome to leave comments if you have any hint. Thanks
Attached file radio log —
radio log file is attached.
assigning to Vincent Liu
Assignee: nobody → vliu
Tony, could you please try with commercial RIL too to and let us know if we need to look at the issue as well?
Could you explain extact your test image?
(In reply to Vincent Liu[:vliu] from comment #8) > Created attachment 734983 [details] > logcat > > I can reproduce this issue. The detailed log files are attached. Before > crashing, I found some error messages. > > I/Gecko ( 132): RIL Worker: Error processing operator tuple: Error: > Invalid network tuple (should be 5 or 6 digits): TWM > I/Gecko ( 132): RIL Worker: Error processing operator tuple: Error: > Invalid network tuple (should be 5 or 6 digits): VIBO > I/Gecko ( 132): RIL Worker: Error processing operator tuple: Error: MCC > could not be parsed from network tuple: WCDMA > I/Gecko ( 132): RIL Worker: Error processing operator tuple: Error: > Invalid network tuple (should be 5 or 6 digits): forbidden > I/Gecko ( 132): RIL Worker: Error processing operator tuple: Error: > Invalid network tuple (should be 5 or 6 digits): CHT > I/Gecko ( 132): RIL Worker: Error processing operator tuple: Error: > Invalid network tuple (should be 5 or 6 digits): Far EasTone > I/Gecko ( 132): RIL Worker: Error processing operator tuple: Error: > Invalid network tuple (should be 5 or 6 digits): GSM > > I think we should figure out these errors. Welcome to leave comments if you > have any hint. Thanks Yes, something wrong on these messages. According to below log, only first entry of "networks" was correct. I/Gecko ( 132): -*- RadioInterfaceLayer: Received message from worker: {"rilMessageType":"getAvailableNetworks","requestId":"id{9022803d-08a9-4d7a-bf16-fbe00df002a3}","rilRequestType":48,"rilRequestError":0,"networks":[{"longName":"TW Mobile","shortName":"TWM","mcc":466,"mnc":97,"state":"current"},{"longName":"WCDMA","shortName":"TW Mobile","mcc":0,"mnc":0,"state":"46697"},{"longName":"available","shortName":"GSM","mcc":0,"mnc":0,"state":"VIBO"},{"longName":"46689","shortName":"forbidden","mcc":0,"mnc":0,"state":"Far EasTone"},{"longName":"FET","shortName":"46601","mcc":0,"mnc":0,"state":"WCDMA"},{"longName":"Chunghwa","shortName":"CHT","mcc":466,"mnc":92,"state":"forbidden"},{"longName":"WCDMA","shortName":"Chunghwa","mcc":0,"mnc":0,"state":"46692"},{"longName":"forbidden","shortName":"GSM","mcc":0,"mnc":0,"state":"FET"},{"longName":"46601","shortName":"forbidden","mcc":0,"mnc":0}]}
From comment 8 and 13, it seems we need help from partner for getting more information in rild. I will contact our PM to get more help.
(In reply to leo.bugzilla.gecko from comment #12) > Could you explain extact your test image? I assume you asked me for the test image I used. The test image I used was built by "./config.sh leo". Besides it, I think there is nothing special. Through the log attached, I need more help from partner side to clarify what I saw. Comment 8 showed the length of tuple should be 5 or 6 digit numeric code to meet the spec. Please see below. /** * RIL_REQUEST_QUERY_AVAILABLE_NETWORKS * * Scans for available networks * * "data" is NULL * "response" is const char ** that should be an array of n*4 strings, where * n is the number of available networks * For each available network: * * ((const char **)response)[n+0] is long alpha ONS or EONS * ((const char **)response)[n+1] is short alpha ONS or EONS * ((const char **)response)[n+2] is 5 or 6 digit numeric code (MCC + MNC) * ((const char **)response)[n+3] is a string value of the status: Can you please help me to verify? Thanks!
Leo doesn't use RIL_worker.js. You have to use AU048 patch for RIL Interface.
(In reply to leo.bugzilla.gecko from comment #16) > Leo doesn't use RIL_worker.js. > You have to use AU048 patch for RIL Interface. After flashing AU048 patch, I can still reproduce the issue. From log observation, I can still see the log I saw in Comment 8 and Comment 13. I/Gecko ( 131): RIL Worker: Handling parcel as REQUEST_QUERY_AVAILABLE_NETWORKS I/Gecko ( 131): RIL Worker: Error processing operator tuple: Error: Invalid network tuple (should be 5 or 6 digits): FET I/Gecko ( 131): RIL Worker: Error processing operator tuple: Error: Invalid network tuple (should be 5 or 6 digits): VIBO I/Gecko ( 131): RIL Worker: Error processing operator tuple: Error: MCC could not be parsed from network tuple: WCDMA I/Gecko ( 131): RIL Worker: Error processing operator tuple: Error: Invalid network tuple (should be 5 or 6 digits): forbidden I/Gecko ( 131): -*- RadioInterfaceLayer: Received message from worker: {"rilMessageType":"getAvailableNetworks","requestId":"id{23ca7ac7-9394-4301-966e-16aa97fd5287}","rilRequestType":48,"rilRequestError":0,"networks":[{"longName":"TW Mobile","shortName":"TWM","mcc":466,"mnc":97,"state":"current"}, {"longName":"WCDMA","shortName":"Far EasTone","mcc":0,"mnc":0,"state":"46601"}, {"longName":"forbidden","shortName":"WCDMA","mcc":0,"mnc":0,"state":"VIBO"}, {"longName":"46689","shortName":"forbidden","mcc":0,"mnc":0,"state":"Chunghwa"}, {"longName":"CHT","shortName":"46692","mcc":0,"mnc":0,"state":"WCDMA"}]} I am not sure why I can still see the message from ril_worker. But even so, RadioInterfaceLayer also show error message like Comment 13 said. These clues show it might be a partner issue. May I get more help from you? Thanks.
From the analysis in Comment 17, it might be a partner issue. Can you please help on this?
Flags: needinfo?(leo.bugzilla.gecko)
Dear Vincent Liu, Loe does not use RIL Worker and RadioInterfaceLayer but use QCContentHelper and nsRadioInterfaceLayer. ( QCContentHelper.js in b2g\vendor\qcom\proprietary\b2g_telephony\content_helper nsRadioInterfaceLayer in b2g\vendor\qcom\proprietary\b2g_telephony ) I cannot understand why you can see RIL Worker and RadioInterfaceLayer logs. I could not see RIL Worker and RadioInterfaceLayer logs in LGE Leo. Please check again your S/W with QCT. Thanks.
Flags: needinfo?(leo.bugzilla.gecko)
Hi Michael, May I confirm with you the AU048 patch? The images I used were in the leo-20130410070209-ril01.01.00.19.060.zip file. flash.sh in this zip file was used to flash. When I ended up image flashing and reboot, I could still reproduce this issue. Because there was nothing I can check in logcat file, I tried to enable ril log by modifying /system/b2g/defaults/pref/user.js in adb shell. When I enabled it, I can see ril log in gecko. It is wierd that I can still see ril log in Gecko even the image is leo-20130410070209-ril01.01.00.19.060.zip(I assume this image uses vendor RIL). Besides, if I can reproduce it by using vendor RIL but not seeing any ril message to analysis, I don't know what I should do for this issue. Thanks
Flags: needinfo?(mvines)
Sorry, I don't know what leo-20130410070209-ril01.01.00.19.060.zip is, or how Moz is repacking the leo builds. Does this issue manifest on the *original* leo build?
Flags: needinfo?(mvines)
Hi Michael Vines, I will change the assignee to you because 1. In Mozilla build, I found the problem came from modem. 2. Even it can be reproduced in leo build, I can't do anything because I don't have any source code. It need to be fixed in partner side.
Assignee: vliu → mvines
Clearing assignee because this issue seems to only occur in the customized Mozilla builds so I have no way to fix as I have no control, or even access, to these builds. Sorry.
Assignee: mvines → nobody
I will test this once we have a new leo build.
Assignee: nobody → mwu
Tested with a new leo build and everything worked as expected. We'll need to make it easier to install things the right way, but it works. Nhirata was also able to update the gecko/gaia/ril and have things work.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: