Ticket #5954 (new defect)
oom-killer during olpc-update
|Reported by:||DanKrejsa||Owned by:||cscott|
|Priority:||high||Milestone:||8.2.0 (was Update.2)|
|Keywords:||oom-killer olpc-update blocks-:8.2.0||Cc:||kimquirk, chihyu, rsmith, ridderman, mtd, joe, gregorio|
|Action Needed:||test in release||Verified:||yes|
|Deployments affected:||Blocked By:|
I just tried olpc update from joyride-1500 to joyride-1525, on a G1G1 XO. I ran
sudo olpc-update joyride-1500
from the terminal activity, and sometime during (or after) the irsync-dirty part of the update, X restarted. I thought the laptop was rebooting, but examining /var/log/messages later I saw that 'NetworkManager invoked oom-killer'.
I've put the log at http://pastebin.ca/849111 . (Also attached.)
I had no other activities than terminal (& Journal) running at the time, and wasn't touching the laptop. I suspect there may be something random to this that may make it hard to reproduce.
I later succeeded doing the update from a usb key using
olpc-update --full --usb
That could be a workaround if this happens frequently.
I would guess there are two aspects to this -- the general handling of out-of-memory conditions by the XO, and the particular usage of memory during olpc-update that made the system run into the limit.