Closed
Bug 991408
Opened 11 years ago
Closed 11 years ago
[tarako] b2g-info returns "Fatal error: B2G main process not found" on pvtbuilds
Categories
(Firefox OS Graveyard :: GonkIntegration, defect)
Tracking
(blocking-b2g:-, b2g-v1.3 unaffected, b2g-v1.3T affected)
RESOLVED
INVALID
blocking-b2g | - |
Tracking | Status | |
---|---|---|
b2g-v1.3 | --- | unaffected |
b2g-v1.3T | --- | affected |
People
(Reporter: nhirata, Unassigned)
Details
1. adb shell b2g-info
Expected: some output
Actual: Fatal error: B2G main process not found
Note:
1. works with taipei builds.
Gaia 578fdccea89a88b417d296f8cf20b39099d44be4
Gecko https://hg.mozilla.org/releases/mozilla-b2g28_v1_3t/rev/34ed4cbc5a59
BuildID 20140402094402
Version 28.1
ro.build.version.incremental=eng.cltbld.20140402.132109
ro.build.date=Wed Apr 2 13:21:16 EDT 2014
Buri
![]() |
Reporter | |
Comment 1•11 years ago
|
||
er. I meant Tarako not Buri.
For 1.3 Buri:
Gaia c5cd3a11e91339163b351d50769eaca0067da860
Gecko https://hg.mozilla.org/releases/mozilla-b2g28_v1_3/rev/5045a67b47ed
BuildID 20140401164001
Version 28.0
ro.build.version.incremental=324
ro.build.date=Thu Dec 19 14:04:55 CST 2013
It's not affected.
status-b2g-v1.3:
--- → unaffected
![]() |
Reporter | |
Comment 2•11 years ago
|
||
we need tooling that works in order to monitor the memory since most of the bugs are based on issues with memory.
blocking-b2g: --- → 1.3T?
Comment 3•11 years ago
|
||
I just checked this on the same build where you are seeing the issue and I did not see the error - I am seeing the information dump as expected. Are you still seeing the same problem after a reboot?
![]() |
Reporter | |
Comment 4•11 years ago
|
||
Are you using a Taipei build? Can you place your info please?
Flags: needinfo?(jhammink)
Comment 5•11 years ago
|
||
It was a PVT build from yesterday.
Gaia 578fdccea89a88b417d296f8cf20b39099d44be4
Gecko https://hg.mozilla.org/releases/mozilla-b2g28_v1_3t/rev/34ed4cbc5a59
BuildID 20140402094402
Version 28.1
ro.build.version.incremental=76
ro.build.date=Tue Apr 1 06:43:27 CST 2014
Here's what I get:
Johns-MacBook-Pro-3:B2G-flash-tool johnhammink$ adb shell b2g-info
| megabytes |
NAME PID PPID CPU(s) NICE USS PSS RSS VSIZE OOM_ADJ USER
b2g 84 1 20.6 0 33.4 37.1 44.7 129.9 0 root
(Nuwa) 339 84 0.8 0 2.9 5.4 11.6 50.5 0 root
Homescreen 370 339 2.9 18 9.0 13.4 22.3 63.7 8 app_370
(Preallocated a 440 339 0.7 18 5.0 8.1 15.6 57.5 1 root
System memory info:
Total 98.1 MB
Used - cache 63.7 MB
B2G procs (PSS) 64.0 MB
Non-B2G procs -0.3 MB
Free + cache 34.5 MB
Free 5.1 MB
Cache 29.3 MB
Low-memory killer parameters:
notify_trigger 14336 KB
oom_adj min_free
0 4096 KB
1 5120 KB
2 6144 KB
6 7168 KB
8 8192 KB
10 20480 KB
That said let me flash up today's PVT build and come back on this bug.
Flags: needinfo?(jhammink)
Comment 6•11 years ago
|
||
Alas, it's working for me also after flashing today's build:
Gaia 8d212f640014db62c622e8c939ddbf8595f00438
Gecko https://hg.mozilla.org/releases/mozilla-b2g28_v1_3t/rev/ddd7ba612cfe
BuildID 20140403004001
Version 28.1
ro.build.version.incremental=76
ro.build.date=Tue Apr 1 06:43:27 CST 2014
Is it posssible after installing from PVT that somehow I am picking up bits from the original Taipei build? Of course, resetting the Tarako doesn't work. I am wondering what could be different about our setups.
![]() |
Reporter | |
Comment 7•11 years ago
|
||
How are you flashing the device? Are you using the tarako.zip file? Or are you just flashing gecko/gaia?
![]() |
Reporter | |
Comment 8•11 years ago
|
||
Actually nevermind I saw the bottom part of your information.
You're using Taipei's gonk level and flashed gecko/gaia from the pvt builds on top. This makes a difference.
Comment 9•11 years ago
|
||
Sure. The device previously had a Taipei build on it.
To be clear, I copied
b2g-28.1.en-US.android-arm.tar.gz
b2g-28.1.en-US.android-arm.crashreporter-symbols.zip
gaia.zip
and
tarako.zip
from PVT builds /latest folder.
I extracted each folder, and ran
./flash_Gg.sh -n
So probably, yes.
May I ask how are you getting full pvt build on the device?
Comment 11•11 years ago
|
||
Is PVT build "user" or "userdebug" build? If it's user build, b2g-info can't work. Taipei build has a hack to enable adb root in user build, so we can use more tools to debug.
Flags: needinfo?(ttsai)
![]() |
Reporter | |
Updated•11 years ago
|
Component: Gaia::System → GonkIntegration
![]() |
Reporter | |
Comment 12•11 years ago
|
||
Thomas,
This is for both production and engineering builds:
Gaia acd18bbd94ebfa534e252a24a75a0617e4b5d5ae
Gecko https://hg.mozilla.org/releases/mozilla-b2g28_v1_3t/rev/91a1b54da4a6
BuildID 20140404004001
Version 28.1
ro.build.version.incremental=eng.cltbld.20140404.045138
ro.build.date=Fri Apr 4 04:51:46 EDT 2014
Tarako
I think we would need the hack in the production builds to help us since there are different variables set for the production builds...
John, since we are working with the vendor and the pulls are being built from their repo, we should be able to flash the gonk level as well. This means downloading the tarako.zip and flashing with that should be the better option for the device than just flashing gecko/gaia.
Comment 14•11 years ago
|
||
how about "adb shell"'s prompt? Is it "#" ?
Comment 15•11 years ago
|
||
how about "su" in adb shell?
A root permission is necessary to use b2g-info.
Flags: needinfo?(ttsai)
Comment 16•11 years ago
|
||
ni? Naoki for the last 2 comments
![]() |
Reporter | |
Comment 17•11 years ago
|
||
adb shell
su
will cause b2g-info to work.
Status: NEW → RESOLVED
blocking-b2g: 1.3T? → -
Closed: 11 years ago
Resolution: --- → INVALID
This caused by reading /proc/pid/exe, it is supposed to be link to /system/b2g/b2g, but it was updated (usually by adb remount and adb push), because the file changed, so that real file is deleted.
lrwxrwxrwx 1 root root 0 2025-01-21 09:11 exe -> /system/b2g/b2g (deleted)
Then b2g processes is not added into process list because b2g-info can't read /proc/[pid]/exe correctly.
adb reboot device should be able to recovered.
"Fatal error: B2G main process not found".
You need to log in
before you can comment on or make changes to this bug.
Description
•