i386 4.9 in -proposed fails to boot in cloud instances

Bug #1642192 reported by Martin Pitt
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Tim Gardner
Zesty
Fix Released
Undecided
Tim Gardner

Bug Description

I noticed a forever-looping test of linuxinfo on i386 this morning. This test upgrades the kernel to 4.9 in -proposed; as soon as that reboots, the VM never comes back. nova console-log shows:

[ 1.581188] Freeing unused kernel memory: 996K (dcc37000 - dcd30000)
[ 1.582525] Write protecting the kernel text: 8300k
[ 1.583624] Write protecting the kernel read-only data: 3344k
[ 1.584845] NX-protecting the kernel data: 6036k
[ 1.585921] ------------[ cut here ]------------
[ 1.586861] WARNING: CPU: 0 PID: 1 at /build/linux-UWDXbt/linux-4.9.0/arch/x86/mm/dump_pagetables.c:225 note_page+0x6a1/0x880
[ 1.589199] x86/mm: Found insecure W+X mapping at address c00a0000/0xc00a0000
[ 1.590657] Modules linked in:
[ 1.591305] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.0-1-generic #2-Ubuntu
[ 1.592809] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Bochs 01/01/2011
[ 1.593188] dae89e70 dc3e0b05 dae89eb4 dca47958 dae89ea0 dc07299a dca47920 dae89ed4
[ 1.593188] 00000001 dca47958 000000e1 dc068db1 000000e1 dae89f34 80000000 00000000
[ 1.593188] dae89ec0 dc072a06 00000009 00000000 dae89eb4 dca47920 dae89ed4 76601e21
[ 1.593188] Call Trace:
[ 1.593188] [<dc3e0b05>] dump_stack+0x58/0x73
[ 1.593188] [<dc07299a>] __warn+0xea/0x110
[ 1.593188] [<dc068db1>] ? note_page+0x6a1/0x880
[ 1.593188] [<dc072a06>] warn_slowpath_fmt+0x46/0x60
[ 1.593188] [<dc068db1>] note_page+0x6a1/0x880
[ 1.593188] [<dc069185>] ptdump_walk_pgd_level_core+0x1f5/0x300
[ 1.593188] [<dc0692c6>] ptdump_walk_pgd_level_checkwx+0x16/0x20
[ 1.593188] [<dc05eafd>] mark_rodata_ro+0xfd/0x130
[ 1.593188] [<dc80d800>] ? rest_init+0x70/0x70
[ 1.593188] [<dc80d82c>] kernel_init+0x2c/0x100
[ 1.593188] [<dc09d641>] ? schedule_tail+0x11/0x50
[ 1.593188] [<dc80d800>] ? rest_init+0x70/0x70
[ 1.593188] [<dc8185c3>] ret_from_fork+0x1b/0x28
[ 1.613361] ---[ end trace d63b34644638754d ]---
[ 1.614368] x86/mm: Checked W+X mappings: FAILED, 96 W+X pages found.
...
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
[... repeating some 50 times... ]
Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for root device. Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT! UUID=ac6eb865-17d6-469d-b58e-8c0d49174fe4 does not exist. Dropping to a shell!

BusyBox v1.22.1 (Ubuntu 1:1.22.0-19ubuntu2) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)

Martin Pitt (pitti)
tags: added: bot-stop-nagging
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1642192

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Martin Pitt (pitti)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Tim Gardner (timg-tpi) wrote :

Martin - I see the same result under QEMU. There is a bunch of weird stuff in the log. Note the lack of installed modules. This is just an -rc5 kernel, so its likely worth waiting until next week.

Changed in linux (Ubuntu Zesty):
assignee: nobody → Tim Gardner (timg-tpi)
status: Confirmed → In Progress
Revision history for this message
Tim Gardner (timg-tpi) wrote :

It is worth noting that I see the same warning ('WARNING: CPU: 1 PID: 1 at /build/linux-yFroJZ/linux-4.8.0/arch/x86/mm/dump_pagetables.c:225 note_page+0x6a1/0x880') with a 4.8 kernel. This is more likely a build problem with modules, e.g.,

Nov 17 09:56:49 ubuntu kernel: [ 10.354579] scsi_transport_iscsi: disagrees about version of symbol mcount
Nov 17 09:56:49 ubuntu kernel: [ 10.354581] scsi_transport_iscsi: Unknown symbol mcount (err -22)

Revision history for this message
volker kempter (v-kempter) wrote :

No boot with any of the the available 4.9 kernels, in particular 4.9.0-1, under Lubuntu-17.04 and 16.04.

Find similar lines in the console log, in particular the following which was mentioned above:

Begin: Waiting for root file system ... Begin: running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
[... repeating some 50 times... ]
Begin: Running /scripts/local-block ... done.
done.

Revision history for this message
volker kempter (v-kempter) wrote :

at #4:

with the newest version of kernel 4.9, namely 4.9-rc7, the problem mentioned above has disappeared: I can boot correctly with this new kernel version for lubuntu-17.04. This holds for a lubuntu-17.04 VM under virtualbox.

Revision history for this message
volker kempter (v-kempter) wrote :

ad #5:
with the kernel 4.9-rc8 the boot problem described above has returned! No boot possible; same behaviour as for the kernel versions BEFORE 4.9-rc7.

Revision history for this message
Tim Gardner (timg-tpi) wrote :

Linus turned CONFIG_MODVERSIONS back on in the mainline kernel. I've disabled it in Ubuntu Zesty, so the next Ubuntu mainline build should pick that config change.

Revision history for this message
volker kempter (v-kempter) wrote :

ad #7:
I confirm that your recent build 4.9.0-8 in ppa:canonical-kernel-team/unstable boots properly.

Tim Gardner (timg-tpi)
Changed in linux (Ubuntu Zesty):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.