Red Hat Bugzilla – Bug 531874
SELinux has prevented vbetool from performing unsafe memory operation
Last modified: 2013-01-10 03:03:43 EST
Created attachment 366669 [details]
Description of problem:
See attache file for details.
Note I was not offered to report this through SELinux Gui however I was offered to turn off memory protection.
I left the laptop suspended ( closed the lid ) overnight and I think this is the cause for the gui not return after staying suspended for so long ( all I got was a black screen with the mouse pointer keyboard was responding and switching to tty2 work fine and switching back to tty1 ( desktop ) still gave me black screen with only the mouse pointer visible.. then again this all might be a xorg-x11-drv-ati issue note this only seems to happen when the laptop has been suspended for a long period of time..
Version-Release number of selected component (if applicable):
Steps to Reproduce:
There is an effort to remove the need for mmap_zero from vbetool. For now set the boolean and see if suspend/resume works correctly.
Uhum it did return after a while with vbetool hogging the cpu.
It's been running like that for quite a while now which makes one wonder if vbetool is looping..
Created attachment 366774 [details]
Screenshot showing the load on vbetool
Created attachment 366776 [details]
gdb of vbetool
Note GPU ATI M22 Mobility Radeon X300 and this with "nomodeset" redoing the test with KMS ON...
The supported suspend/resume configuration for intel, nvidia and radeon is with KMS enabled, at which point vbetool won't be run.