We should probably also report this upstream, since it still affects
current mainline.  https://wiki.ubuntu.com/Bugs/Upstream/kernel

We can also perform a kernel bisect to identify the commit that
introduced this bug.  We would first need to identify the last kernel
version that did not have the bug and the first version that did.  Can
you test the following kernels:

v4.6 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/
v4.8 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8/
v4.10 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10/

You don't have to test every kernel, just up until the kernel that first
has this bug.

Thanks in advance!

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

** Tags added: kernel-da-key

** Also affects: linux (Ubuntu Bionic)
   Importance: High
       Status: Confirmed

** Also affects: linux (Ubuntu Artful)
   Importance: Undecided
       Status: New

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

** Changed in: linux (Ubuntu Artful)
       Status: New => Triaged

** Changed in: linux (Ubuntu Bionic)
       Status: Confirmed => Triaged

** Tags added: kernel-key

** Tags added: performing-bisect

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  [regression] bionic 4.15.0-13-generic panics on qemu ppc64el

Status in linux package in Ubuntu:
Status in linux source package in Artful:
Status in linux source package in Bionic:

Bug description:
  When upgrading to bionic on a qemu ppc64el instance, the 4.15.0 kernel
  panics before initrd.  Going back to xenial 4.4.0 works correctly.

    Installed: 4.15.0-13.14
    Candidate: 4.15.0-13.14
    Version table:
   *** 4.15.0-13.14 500
          500 http://nibbler.snowman.lan/deb-proxy/ubuntu-ports bionic/main 
ppc64el Packages
          100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic ppc64le
  .var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform'
   total 0
   crw-rw---- 1 root audio 116,  1 Apr  5 16:11 seq
   crw-rw---- 1 root audio 116, 33 Apr  5 16:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Apr  5 16:13:28 2018
  HibernationDevice: RESUME=UUID=2e904a57-3ce7-4b31-97ed-6c63b81b2221
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-119-generic 
root=UUID=294515c8-75f2-4996-8e4f-a838e6c75804 ro
  ProcLoadAvg: 3.04 2.18 0.92 3/119 1643
   1: POSIX  ADVISORY  WRITE 1225 00:12:470 0 EOF
   2: POSIX  ADVISORY  WRITE 841 00:12:459 0 EOF
   3: FLOCK  ADVISORY  WRITE 832 00:12:449 0 EOF
   4: POSIX  ADVISORY  WRITE 802 00:12:432 0 EOF
   5: POSIX  ADVISORY  WRITE 350 00:12:294 0 EOF
   Filename                             Type            Size    Used    Priority
   /dev/vda3                               partition    1408960 0       -1
  ProcVersion: Linux version 4.4.0-119-generic (buildd@bos02-ppc64el-006) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #143-Ubuntu SMP 
Mon Apr 2 16:08:02 UTC 2018
   linux-restricted-modules-4.4.0-119-generic N/A
   linux-backports-modules-4.4.0-119-generic  N/A
   linux-firmware                             1.173
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-04-05 (0 days ago)
  cpu_cores: Number of cores present = 1
  cpu_coreson: Number of cores online = 1
  cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: 
Machine is not SMT capable

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to