Bug 703907

Summary:

[JUNIPER] gdm graphical switch user broken, X outputs message 'conflicting memory types'

Product:

[Fedora] Fedora

Reporter:

abugreporter

Component:

xorg-x11

Assignee:

X/OpenGL Maintenance List <xgl-maint>

Status:

CLOSED CANTFIX

QA Contact:

Severity:

unspecified

Docs Contact:

Priority:

unspecified

Version:

CC:

mcepl

Target Milestone:

---

Target Release:

---

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2011-05-14 13:08:00 UTC

Type:

---

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Attachments:

Description	Flags
Output dmesg command	none
/var/log/messages	none
xorg.conf	none
Xorg.2.log	none

Description abugreporter 2011-05-11 16:00:24 UTC

Description of problem:

I left my machine running for more than 24 hours, more than 8 of which the machine was in a locked state (gdm) as desired. Then another user wanted to switch user, by pressing some button designed for this in gdm. 


When the user clicks in a state I will call A, the fan of the graphics card makes a lot of noise, a black screen is generated, and we are back in state A again. 

These messages are in my dmesg: 

[500819.172025] Xorg:4745 conflicting memory types e0000000-f0000000 uncached-minus<->write-combining
[500819.172028] reserve_memtype failed 0xe0000000-0xf0000000, track uncached-minus, req uncached-minus
[500825.417310] Xorg:4899 conflicting memory types e0000000-f0000000 uncached-minus<->write-combining
[500825.417313] reserve_memtype failed 0xe0000000-0xf0000000, track uncached-minus, req uncached-minus
[500839.871124] Xorg:5107 conflicting memory types e0000000-f0000000 uncached-minus<->write-combining
[500839.871127] reserve_memtype failed 0xe0000000-0xf0000000, track uncached-minus, req uncached-minus
[500856.958354] Xorg:5354 conflicting memory types e0000000-f0000000 uncached-minus<->write-combining
[500856.958357] reserve_memtype failed 0xe0000000-0xf0000000, track uncached-minus, req uncached-minus
[500871.462483] Xorg:5561 conflicting memory types e0000000-f0000000 uncached-minus<->write-combining
[500871.462485] reserve_memtype failed 0xe0000000-0xf0000000, track uncached-minus, req uncached-minus
[500941.516970] Xorg:6378 conflicting memory types e0000000-f0000000 uncached-minus<->write-combining
[500941.516972] reserve_memtype failed 0xe0000000-0xf0000000, track uncached-minus, req uncached-minus
[503697.844019] Xorg:4078 conflicting memory types e0000000-f0000000 uncached-minus<->write-combining
[503697.844021] reserve_memtype failed 0xe0000000-0xf0000000, track uncached-minus, req uncached-minus
[503728.530295] Xorg:4521 conflicting memory types e0000000-f0000000 uncached-minus<->write-combining
[503728.530298] reserve_memtype failed 0xe0000000-0xf0000000, track uncached-minus, req uncached-minus
[503757.606147] Xorg:4903 conflicting memory types e0000000-f0000000 uncached-minus<->write-combining
[503757.606149] reserve_memtype failed 0xe0000000-0xf0000000, track uncached-minus, req uncached-minus
[503856.263936] Xorg:6219 conflicting memory types e0000000-f0000000 uncached-minus<->write-combining
[503856.263939] reserve_memtype failed 0xe0000000-0xf0000000, track uncached-minus, req uncached-minus

Version-Release number of selected component (if applicable):


How reproducible:
No idea. 

Actual results:
Like above.


Expected results:
A working implementation of 'switch user' in gdm without X outputting all kinds of messages. 

On some Ubuntu page it is said that adding 'nopat' 'solves' the issue, but that is just a work around. Just get a real fix into both F14 and F15.

Comment 1 Matěj Cepl 2011-05-12 11:27:11 UTC

Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 2 abugreporter 2011-05-14 10:22:23 UTC

Created attachment 498915 [details]
Output dmesg command

Comment 3 abugreporter 2011-05-14 10:22:55 UTC

Created attachment 498916 [details]
/var/log/messages

Comment 4 abugreporter 2011-05-14 10:23:25 UTC

Created attachment 498917 [details]
xorg.conf

Comment 5 abugreporter 2011-05-14 10:23:50 UTC

Created attachment 498918 [details]
Xorg.2.log

Comment 6 abugreporter 2011-05-14 10:24:58 UTC

Is there no way to add multiple attachments in one "Comment"?

Comment 7 Matěj Cepl 2011-05-14 13:08:00 UTC

Thanks for the report. We are sorry that we cannot help you with your problem, but we are not able to support binary-only drivers. If you would be able to reproduce this issue using only open source software (i.e., radeon driver in this case), please, reopen this bug with the additional information, but in meantime I have no choice than to close this bug as CANTFIX (because we really cannot fix it).