touch-packages team mailing list archive

[James Hunt <james.hunt@xxxxxxxxxxxxx>]

Ondrej - aha! with the debug, this is making more sense now. Yes, since
the ureadahead-touch job spawns a process in the background (ureadahead)
and then the job itself exits, the log associated with the main job
process gets added to the unflushed list. ureadahead then writes output
and the NihIo is automatically serviced to flush the log to disk and set
log->unflushed->len to zero. Later, 'initctl notify-disk-writable' gets
called and the assert fires as all the output from both /etc/init
/ureadahead-touch.conf and from the ureadahead daemon itself has already
been logged.

Could you try the following which should be a minimal fix:
http://paste.ubuntu.com/11095313/

Another point - the fact that ureadahead-touch is triggering the problem
does point to an issue with that job - as can be seen, even when the
script section ends (and that associated shell dies), 'ureadahead
--daemon' continues and if it produces output, that gets logged. A
simple work-around is to remove --daemon so that the job process and the
log never become detached.

-- 
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:
  Fix Committed
Status in Upstart:
  New
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