← Back to team overview

kernel-packages team mailing list archive

[Bug 1520427] Re: drm/fbdev: Return -EBUSY when oopsing

 

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

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

** Also affects: linux (Ubuntu Xenial)
   Importance: Medium
       Status: Triaged

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

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

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

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

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

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

** Tags added: vivid wily xenial

-- 
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:
  Triaged
Status in linux source package in Vivid:
  Triaged
Status in linux source package in Wily:
  Triaged
Status in linux source package in Xenial:
  Triaged

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


References