1131892 - [MTBF][B2G] phone crashed

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Wifi, defect)

Description

[Walter Chen[:ypwalter][:wachen]]

Crash report address: https://crash-stats.mozilla.com/report/index/7ef52ace-7c00-4e3c-bad5-757eb2150211
adb was still normal. phone was slow and I had bad time controlling it. However, adb lost connection after I sent the crash report over air.

b2g-ps:
APPLICATION    SEC USER     PID   PPID  VSIZE  RSS     WCHAN    PC         NAME
Camera           2 u0_a10052 10052 14654 98956  3632  ffffffff b6ef7894 S /system/b2g/b2g
Browser          2 u0_a10403 10403 14654 83532  4348  ffffffff b6ef7894 S /system/b2g/b2g
Browser          2 u0_a10745 10745 14654 82364  14572 ffffffff b6ef7894 S /system/b2g/b2g
Usage            2 u0_a10852 10852 14654 71604  5240  ffffffff b6ef7894 S /system/b2g/b2g
b2g              0 root      14631 1     258484 49544 ffffffff b6ef7894 S /system/b2g/b2g
(Nuwa)           0 root      14654 14631 65256  560   ffffffff b6ef7894 S /system/b2g/b2g
Homescreen       2 u0_a23679 23679 14631 117580 3536  ffffffff b6f2d894 S /system/b2g/plugin-container
(Preallocated a  2 u0_a25153 25153 14654 69396  4248  ffffffff b6ef7894 S /system/b2g/b2g
FM Radio         2 u0_a27625 27625 14654 79136  2720  ffffffff b6ef7894 S /system/b2g/b2g

b2g-info:
                           |     megabytes     |
           NAME   PID  PPID CPU(s) NICE  USS  PSS  RSS SWAP VSIZE OOM_ADJ USER     
            b2g 14631     1 2365.7    0 41.5 43.4 48.3 31.4 252.6       0 root     
         Camera 10052 14654   30.5   18  0.3  0.9  3.6 21.2  96.6      12 u0_a10052
        Browser 10403 14654   10.3   18  0.8  1.3  4.3 18.4  81.6      11 u0_a10403
        Browser 10745 14654   40.4   18  9.2 10.5 14.3  7.3  80.6      11 u0_a10745
          Usage 10852 14654    2.5   18  0.6  1.5  5.1 13.0  69.9      10 u0_a10852
         (Nuwa) 14654 14631    5.2    0  0.0  0.1  0.6 11.2  63.7     -16 root     
     Homescreen 23679 14631  199.4    1  0.2  0.8  3.5 22.5 114.8       2 u0_a23679
(Preallocated a 25153 14654    0.5   18  0.2  0.9  4.2 10.8  67.8       1 u0_a25153
       FM Radio 27625 14654   16.5    7  0.2  0.5  2.7 12.0  77.3       6 u0_a27625

System memory info:

            Total 214.6 MB
        SwapTotal 192.0 MB
     Used - cache 174.5 MB
  B2G procs (PSS)  59.7 MB
    Non-B2G procs 114.7 MB
     Free + cache  40.2 MB
             Free  23.1 MB
            Cache  17.1 MB
         SwapFree  55.3 MB

Low-memory killer parameters:

  notify_trigger 9216 KB

  oom_adj min_free
        0  4096 KB
       58  5120 KB
      117  6144 KB
      352  7168 KB
      470  8192 KB
      588 10240 KB

Comment 1

[Walter Chen[:ypwalter][:wachen]]

I believe I met this problem twice.

Comment 2

[Brian Huang [:brianhuang][:brhuang]]

It is happened on 2.2 while running MTBF. Nominate to 2.2?

Comment 3

[Walter Chen[:ypwalter][:wachen]]

http://mtbf-1.corp.tpe1.mozilla.com:8080/job/flamekk.v2.2.moztwlab01.319.mtbf_op/label=moztwlab-01/35/consoleFull

Comment 4

[Gregor Wagner [:gwagner]]

Crash report suggests this is happening in wifi.

Comment 5

[Gregor Wagner [:gwagner]]

This looks a lot like bug 1025414

Comment 6

[Michael Vines [:m1] [:evilmachines]]

Yep, looks like it.

Comment 7

[Gregor Wagner [:gwagner]]

Is this something we have to fix on our end? Updating the flame manifest?

Comment 8

[Michael Vines [:m1] [:evilmachines]]

Yep, the fix is on CAF.  Details in the other bug

Comment 9

[Paul Yang [:pyang] (away)]

bug 1025414 resolved half years ago but we still encountered it.  Do we need some way to apply this modification?

Comment 10

[Vincent Chang[:vchang][changyihsin]]

Hi Selin, can you help to update the Flame manifest. The fix is in [1] on CAF.

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1025414#c15

Comment 11

[Kai-Zhen Li [:seinlin][:kli]]

Michael, Now flame-kk's libhardware_legacy is using "LNX.LA.3.5.2.1.1" branch. But The fix mentioned in comment 10 is in LNX.LF.3.5.2.1_1 branch. 

Can we use 'LNX.LF.3.5.2.1_1' branch for flame-kk?

OR

Could you pick this commit to "LNX.LA.3.5.2.1.1" branch?

https://www.codeaurora.org/cgit/quic/la/platform/hardware/libhardware_legacy/commit/?h=LNX.LF.3.5.2.1_1&id=cac4f50ce59697be2c2b9001eb31f4be210f3756

Thanks!

Comment 12

[Michael Vines [:m1] [:evilmachines]]

Please use the 'LNX.LF.3.5.2.1_1' branch.  

Ref: https://www.codeaurora.org/cgit/quic/lf/b2g/manifest/tree/caf_AU_LINUX_GECKO_B2G_KK_3.6.01.04.00.000.188.xml?id=fa64bb6d0c84870c34c4cb46fac16c5a3067df66#n550

Comment 13

[bhavana bajaj [:bajaj]]

waiting for confirmation from mtbf team that this is fixed.

Comment 14

[Kai-Zhen Li [:seinlin][:kli]]

Clear POVB as fix is already in partner's repo. We need to update flame-kk manifest.

Comment 15

[Kai-Zhen Li [:seinlin][:kli]]

Attachment: [master] Override libhardware_legacy to fix device crashed by wifi.

Viral, We need to update the branch of libhardware_legacy. Could you review this patch? Thanks!

Comment 16

[Kai-Zhen Li [:seinlin][:kli]]

Attachment: [v2.2] Override libhardware_legacy to fix device crashed by wifi.

Comment 17

[viral [:viralwang]]

Comment on attachment 8563832 [details] [review]
[master] Override libhardware_legacy to fix device crashed by wifi.

It looks like we can't find all the repositories for LNX.LF.3.5.2.1_1
I think update the necessary repository only should be low risk now.
 
Fetching project platform/external/tagsoup
fatal: Couldn't find remote ref refs/heads/LNX.LF.3.5.2.1_1

Comment 18

[Kai-Zhen Li [:seinlin][:kli]]

(In reply to viral [:viralwang] from comment #17)
> It looks like we can't find all the repositories for LNX.LF.3.5.2.1_1
> I think update the necessary repository only should be low risk now.

Yes, I also think update necessary could be better, because not all repos get LNX.LF.3.5.2.1_1 branch.

Comment 19

[Kai-Zhen Li [:seinlin][:kli]]

master: https://github.com/mozilla-b2g/b2g-manifest/commit/36317e07ed8ed0206f4887022d91e96e71b8b4a9
v2.2: https://github.com/mozilla-b2g/b2g-manifest/commit/41d0cbe3a1de9f03012cc311d4688915d44cfaf0