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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1877657

Title:
  bionic snapdragon 4.15 snap failed Certification testing

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  snap certification testing failed with bionic/linux-snapdragon

  https://bugs.launchpad.net/bugs/1874763

  After investigations by Kleber, failure was found to be from a drm
  driver which is compiled when CONFIG_DRM_MSM is set.

  Information reported from Paul Larson [1]:

  We have a cold reboot test in checkbox that seems to be failing with this 
kernel. The test runs the following commands to try to trigger a cold reboot:
   rtcwake --mode no -s 120
   sleep 5
   rtcwake -m show
   sleep 5
   dbus-send --system --print-reply --dest=org.freedesktop.login1 
/org/freedesktop/login1 "org.freedesktop.login1.Manager.PowerOff" boolean:true

  However, the system never fully reboots. On the serial console, I just see:
  ...
  Press enter to configure.
  [ 137.402465] systemd-shutdown[1]: Failed to wait for process: Protocol error
  [ 137.406163] systemd-shutdown[1]: Failed to wait for process: Protocol error

  I do have the ability to remotely remove power from the device and
  restore it, however after doing that, I get an oops on the serial
  console and the system never comes up.

  [1] https://bugs.launchpad.net/kernel-sru-
  workflow/+bug/1874763/comments/1

  [Test]
  Run Certification Testing

  The tests are ran only with UC18, so a kernel snap is needed to either
  build a new image or promote it to edge.

  [Fix]

  The affected drm driver is set by CONFIG_DRM_MSM which is also set on
  bionic/linux

  Revert upstream commits on Bionic/linux:

  0519bad6f34f drm/msm: Use the correct dma_sync calls in msm_gem
  7318c5ef642b drm/msm: stop abusing dma_map/unmap for cache

  [Risk of Regression]

  Alternative solutions would need to be found for dma_sync calls in
  msm_gem and to avoid abusing dma_map/unmap for cache. The commits both
  came from upstream stable.

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

-- 
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