** Changed in: linux (Ubuntu Vivid)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Wily)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Vivid)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Wily)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Confirmed
--
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:
Confirmed
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:
Confirmed
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.vet...@ffwll.ch>
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
--
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
