kernel-packages team mailing list archive

[Joseph Salisbury <joseph.salisbury@xxxxxxxxxxxxx>]

Commit c50bfd08 does not pick cleanly in the Vivid(3.19) kernel.  The
3.19 kernel does not have intel_fbdev_blank() or
intel_fbdev_pan_display().   intel_fbdev_blank() was added by commit
03e515f7 in v4.1-rc1.  intel_fbdev_pan_display() was added by commit
d9a946b5 in v4.2-rc1.

Can you confirm where or not commit c50bfd08 is needed in the 3.19 Wily
kernel?  If it is, I can backport the commit.

Thanks in advance!

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

Title:
   drm/fbdev: Return -EBUSY when oopsing

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Issue: 
  Between upstream kernel v3.19 to v4.2,when Intel SMEP/SMAP protection was triggered by some wild function call or data access,  the screen would be frozen and never come back,but the system does not hang.

  Generally, an SMEP/SMAP violation should cause the involved process
  killed, an oops from page fault exception generated to the syslog, and
  the system survived.

  Fix:
  One patch from 4.3 kernel fix this issue
  commit c50bfd08d60cefbe1714c4a53b1c325982858549
  Author: Daniel Vetter <daniel.vetter@xxxxxxxx>
  Date:   Tue Jul 28 13:18:40 2015 +0200

      drm/fbdev: Return -EBUSY when oopsing

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