initramfs kernel bunzip2 boot crash
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-initramfs-tools |
Expired
|
Undecided
|
Unassigned |
Bug Description
From the most recent kernel pull from Linus's tree tonight using the config-
[ 0.676119] Trying to unpack rootfs image as initramfs...
[ 3.312822] swapper/0 invoked oom-killer: gfp_mask=0x24200c2, order=0, oom_score_adj=0
[ 3.314181] swapper/0 cpuset=/ mems_allowed=0
[ 3.314935] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.4.0+ #2
[ 3.315739] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-
[ 3.317029] 0000000000000000 000000003504fa35 ffff88003e2fb7e8 ffffffff813d2e94
[ 3.318291] ffff88003e2fb970 ffff88003e2fb850 ffffffff8120a726 0000000000000000
[ 3.319557] 000000003504fa35 00000000024200c2 0000000000000000 ffff88003e2fb970
[ 3.320816] Call Trace:
[ 3.321245] [<ffffffff813d2
[ 3.321941] [<ffffffff8120a
[ 3.322691] [<ffffffff8118d
[ 3.323558] [<ffffffff81192
[ 3.324419] [<ffffffff811de
[ 3.325253] [<ffffffff811df
[ 3.326069] [<ffffffff81188
[ 3.326876] [<ffffffff81189
[ 3.327690] [<ffffffff81189
[ 3.328568] [<ffffffff81236
[ 3.330165] [<ffffffff81188
[ 3.330976] [<ffffffff8118b
[ 3.331813] [<ffffffff8118b
[ 3.332633] [<ffffffff81fb5
[ 3.333358] [<ffffffff8120d
[ 3.334090] [<ffffffff8120e
[ 3.334813] [<ffffffff813f1
[ 3.335614] [<ffffffff81fb5
[ 3.336334] [<ffffffff8120f
[ 3.337045] [<ffffffff81f74
[ 3.337766] [<ffffffff81f74
[ 3.338450] [<ffffffff81f74
[ 3.339134] [<ffffffff81f73
[ 3.339859] [<ffffffff81f73
[ 3.340589] [<ffffffff81f73
[ 3.341343] [<ffffffff81fb6
[ 3.342059] [<ffffffff81fb6
[ 3.342801] [<ffffffff81fb6
[ 3.343475] [<ffffffff81f73
[ 3.344225] [<ffffffff81f74
[ 3.345022] [<ffffffff81f73
[ 3.345771] [<ffffffff81f74
[ 3.346549] [<ffffffff81f74
[ 3.347327] [<ffffffff81002
[ 3.348102] [<ffffffff81f72
[ 3.348934] [<ffffffff817fe
[ 3.349662] [<ffffffff817fe
[ 3.350378] [<ffffffff8180b
[ 3.351127] [<ffffffff817fe
[ 3.351845] Mem-Info:
affects: | openstack-ansible → cloud-initramfs-tools |
Hi,
is this still an issue?
I suspect that if it is, its in the overlay filesystem upstream.
overlayroot should now properly use the 'overlay' filesystem if its present, no longer relying on the 'overlayfs' name from Ubuntu.
If its still a problem for you, please provide that info, and mark 'New' again.