Closed Bug 802214 Opened 9 years ago Closed 9 years ago

Unagi phones are using an unrepresentative amount of memory, affecting testing


(Firefox OS Graveyard :: General, defect, P1)




B2G C2 (20nov-10dec)
blocking-basecamp +


(Reporter: akeybl, Assigned: mwu)


(Whiteboard: [fota])

Unagi phones are using an unrepresentative amount of memory. We need to limit that.
A new kernel with memory usage clamped to otoro levels is up.
Closed: 9 years ago
Resolution: --- → FIXED
The kernel was pulled out of nightlies until QA can take a look at builds with the new Kernel.
Resolution: FIXED → ---
I think this is borderline dogfooding-blocker.  Without this change, we're not going to be getting realistic reporting of lowmem problems.  It's going to take a fair bit of time to set up a FOTA server that meets all our constraints, so saying "we can just fix this in a FOTA update" is not a reasonable answer.

On the other hand, we have lots of known dumb excessive memory usage that will be fixed by the time FOTA is ready.  We may suffer from lots of dups if we ship a kernel with realistic memory allocations before all the dumb stuff is fixed.  And if those dumb bugs cause us to lose dogfooders, it would be a massive net loss.

I think the risk from the latter is greater than the potential benefit from the former, so I wouldn't block dogfooding on this.
mwu, do we have any idea when we'll get a new Unagi kernel that limits the amount of memory available?
(In reply to Chris Lee [:clee] from comment #4)
> mwu, do we have any idea when we'll get a new Unagi kernel that limits the
> amount of memory available?

We already have one. It was pulled so QA can take a look at it.
Vlad was asking about CPU differences; do we know what they'll be?
He already asked me about that.  But there's nothing to worry about CPU-wise.  Ping me privately for details.
Whiteboard: [fota]
FYI, there is

which lets you grab a certain amount of memory.
That's not quite enough because we want to tweak static pmem allocations too.

There's nothing to do here, we already have a kernel build that's configured to look just like otoro.  I'm running it on my dogfooding phone.  We just need the FOTA support to push it out.
Marking for C2, given this meets the criteria of known P1/P2 blocking-basecamp+ bugs at the end of C1.
Target Milestone: --- → B2G C2 (20nov-10dec)
Has this been pushed out via FOTA yet?
We missed the boat when we distributed phones without this.  Mozilla can't push it out now.  We need to get updates through the vendor set up and the vendor push it.

I'm going to go ahead and close this because there's nothing left that we can do.
Closed: 9 years ago9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.