Description of problem:
I see an oops in avc_has_perm_noaudit in my logs. When I installed
RHEL4beta2, my machine locked up when gdm first started. Not sure if
this was just the display, or the entire system... can retry and
provide more info on request.
On the second run, gdm started correctly, and I was able to use the
desktop. gconf didn't get configured correctly (probably due to the
lock up), and so I find myself getting a lot of gconf-related errors.
I had previously installed RHEL4beta1, and had not noticed this problem.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install RHEL4beta2 on a system with hardware matching the attached
2. Note oops
3. Note lock-up on first gdm run.
Created attachment 106602 [details]
Created attachment 106603 [details]
Could you try both the following:
(a) disable dri by commenting out the line "Load dri" in your
and, if that makes the problem go away,
(b) re-enable dri by uncommenting "load dri", and then
disabling Render acceleration by adding
Option "RenderAccel" "False"
to videocard section of /etc/X11/xorg.conf
It's not clear that this is even DRI related, but worth a shot. Thanks.
Also, with DRI enabled, try disabling SElinux to see if this is
SElinux specific problem. You can do that by booting with
selinux=0 on the kernel commandline.
Mike, with selinux disabled from the installer everything seems to
Soeren, I tried to do another SELinux-enabled install. The install
worked to the point where gdm came up with a login screen. At this
point, I switched to the console and tried to login. I got a kernel
panic on login:
Kernel panic - not syncing. Fatal exception in interrupt. Process
mingetty, stack pointer is garbage.
I think there might be two selinux-related bugs here:
1. Fatal kernel panic, somehow login related
2. Non-fatal oops, ati/X related
Both of these don't seem to happen in a non-SELinux install.
I don't have a functional RHEL4+SELinux install right now, will report
back what I find out regarding disabling dri when I do.
Is this still a problem, or can it be closed?
It can be closed.