touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #72925
[Bug 1447756] Re: segfault in log.c code causes phone reboot loops
I think I understand what's happening now - it's not the log that isn't
being freed, it's the list entry the log is attached to that is not
freed. The effect is the same though - calling log_clear_unflushed()
multiple times could trigger this issue since the still-valid (but
incorectly so) list entry is now pointing at potentially garbage memory
where a Log used to be.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1447756
Title:
segfault in log.c code causes phone reboot loops
Status in the base for Ubuntu mobile products:
Confirmed
Status in upstart package in Ubuntu:
Confirmed
Bug description:
We recently started getting reprots from phone users that their
devices go into a reboot loop after changing the language or getting
an OTA upgrade (either of both end with a reboot of the phone)
after a bit of research we collected the log at
http://pastebin.ubuntu.com/10872934/
this shows a segfault of upstarts init binary in the log.c code:
[ 6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log->unflushed->len
[ 7.000279]init: Caught abort, core dumped
[ 7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000600
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions
References