4.8 dropped CONFIG_ATA=y (breaks systemd's TEST-08-ISSUE-2730 upstream test)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Critical
|
Tim Gardner | ||
Yakkety |
Fix Released
|
Critical
|
Tim Gardner | ||
systemd (Ubuntu) |
Won't Fix
|
Undecided
|
Martin Pitt | ||
Yakkety |
Won't Fix
|
Undecided
|
Martin Pitt |
Bug Description
Since the kernel upgrade from 4.4 to 4.8 in yakkety, systemd's TEST-08-ISSUE-2730 upstream test now consistently fails with:
+ timeout --foreground 180 /usr/bin/
warning: TCG doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
[ 1.491760] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 1.492153] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-14-generic #15-Ubuntu
[ 1.492153] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-
[ 1.492153] 0000000000000086 0000000035700369 ffffffffa8b59c24 ffff97201dd45000
[ 1.492153] ffff97201e9afea0 ffffffffa8987431 0000000000000010 ffff97201e9afeb0
[ 1.492153] ffff97201e9afe48 0000000035700369 ffff97201e9afe58 ffff97201e9afeb8
[ 1.492153] Call Trace:
[ 1.492153] [<ffffffffa8b59
[ 1.492153] [<ffffffffa8987
[ 1.492153] [<ffffffffa9572
[ 1.492153] [<ffffffffa9571
[ 1.492153] [<ffffffffa9572
[ 1.492153] [<ffffffffa9572
[ 1.492153] [<ffffffffa8e2c
[ 1.492153] [<ffffffffa8e39
[ 1.492153] [<ffffffffa8e2c
[ 1.492153] Kernel Offset: 0x27800000 from 0xffffffff81000000 (relocation range: 0xffffffff80000
[ 1.492153] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
qemu-system-x86_64: terminating on signal 15 from pid 8784
This only happens on amd64, i386 and ppc64el are fine.
http://
I'll investigate more details, filing this for getting a reference for the britney hint.
Changed in systemd (Ubuntu): | |
assignee: | nobody → Martin Pitt (pitti) |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
tags: | added: bot-stop-nagging |
description: | updated |
Changed in systemd (Ubuntu): | |
status: | New → In Progress |
milestone: | none → ubuntu-16.09 |
Changed in linux (Ubuntu Yakkety): | |
status: | Confirmed → Fix Committed |
This is the first test that boots the root disk without an initrd. Indeed booting it with debug shows that the kernel detects no hard disks then (in particular not /dev/sda1), thus the boot fails like that.
With 4.4, or with 4.8 and booting with an initrd it detects the sda hard drive again:
[ 2.374065] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc000 irq 14
[ 2.383381] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc008 irq 15
[ 2.563557] ata2.01: NODEV after polling detection
[ 2.583452] ata1.01: NODEV after polling detection
[ 2.600806] ata1.00: ATA-7: QEMU HARDDISK, 2.5+, max UDMA/100
[ 2.617551] ata1.00: 819200 sectors, multi 16: LBA48
[ 2.632337] ata2.00: ATAPI: QEMU DVD-ROM, 2.5+, max UDMA/100
[ 2.649576] ata2.00: configured for MWDMA2
[ 2.662298] ata1.00: configured for MWDMA2
[ 2.671218] scsi 0:0:0:0: Direct-Access ATA QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5
I think this is due to this config change:
$ grep CONFIG_ATA= config-4.* 4.4.0-9136- generic: CONFIG_ ATA=y 4.8.0-14- generic: CONFIG_ ATA=m
config-
config-
Which would by and large mean that it is now impossible to boot without an initrd. I don't think this is desirable, as it could actually lead to regressions on existing machines.