[Bug 1626394] Re: 4.8 dropped CONFIG_ATA=y (breaks systemd's TEST-08-ISSUE-2730 upstream test)

Andy Whitcroft apw at canonical.com
Thu Sep 22 09:49:45 UTC 2016


We long ago decided on four "most common" drivers for disks and included
those to make things work in the majority of places without epic bloat.
We should check those four are still present at the same time.

** Tags added: kernel-4.8

** Changed in: linux (Ubuntu)
   Importance: Undecided => Critical

** Changed in: linux (Ubuntu)
     Assignee: (unassigned) => Tim Gardner (timg-tpi)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1626394

Title:
  4.8 dropped CONFIG_ATA=y (breaks systemd's TEST-08-ISSUE-2730 upstream
  test)

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Won't Fix

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/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -kernel /boot/vmlinuz-4.8.0-14-generic -drive format=raw,cache=unsafe,file=/var/tmp/systemd-test.4jlHRw/rootdisk.img -append 'root=/dev/sda1 raid=noautodetect loglevel=2 init=/lib/systemd/systemd ro console=ttyS0 selinux=0 systemd.unified_cgroup_hierarchy=no  '
  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.8.2-1ubuntu1 04/01/2014
  [    1.492153]  0000000000000086 0000000035700369 ffffffffa8b59c24 ffff97201dd45000
  [    1.492153]  ffff97201e9afea0 ffffffffa8987431 0000000000000010 ffff97201e9afeb0
  [    1.492153]  ffff97201e9afe48 0000000035700369 ffff97201e9afe58 ffff97201e9afeb8
  [    1.492153] Call Trace:
  [    1.492153]  [<ffffffffa8b59c24>] ? dump_stack+0x5c/0x78
  [    1.492153]  [<ffffffffa8987431>] ? panic+0xe4/0x226
  [    1.492153]  [<ffffffffa95724f9>] ? mount_block_root+0x284/0x2c0
  [    1.492153]  [<ffffffffa957187b>] ? set_debug_rodata+0xc/0xc
  [    1.492153]  [<ffffffffa957268f>] ? prepare_namespace+0x12b/0x180
  [    1.492153]  [<ffffffffa9572161>] ? kernel_init_freeable+0x1dd/0x1ed
  [    1.492153]  [<ffffffffa8e2c0ea>] ? kernel_init+0xa/0x100
  [    1.492153]  [<ffffffffa8e3949f>] ? ret_from_fork+0x1f/0x40
  [    1.492153]  [<ffffffffa8e2c0e0>] ? rest_init+0x80/0x80
  [    1.492153] Kernel Offset: 0x27800000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
  [    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://autopkgtest.ubuntu.com/packages/systemd/yakkety/amd64

  I'll investigate more details, filing this for getting a reference for
  the britney hint.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626394/+subscriptions



More information about the foundations-bugs mailing list