Bug 1204513

Summary:

cannot switch to console, display freezes, kernel BUG at drivers/gpu/drm/drm_crtc.c:530!, drm_framebuffer_free_bug+0x9/0x10 [drm]

Product:

[Fedora] Fedora

Reporter:

Chris Murphy <bugzilla>

Component:

xorg-x11-drv-intel

Assignee:

Adam Jackson <ajax>

Status:

CLOSED DUPLICATE

QA Contact:

Fedora Extras Quality Assurance <extras-qa>

Severity:

unspecified

Docs Contact:

Priority:

unspecified

Version:

CC:

ajax, fedora, xgl-maint, znmeb

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:

2015-05-27 15:13:02 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
dmesg	none
journal	none

Description Chris Murphy 2015-03-22 20:13:39 UTC

Description of problem:
When trying to to switch from gnome-shell or gdm (login window) to a console (tty2), nothing happens and then the display is no longer responsive and system appears to be completely frozen. Remote access is still functional, but even a reboot -f will fail.

Version-Release number of selected component (if applicable):
4.0.0-0.rc4.git2.1.fc22.x86_64
This has been happening with 3.19 kernels as well, it could be related to gdm+Wayland. Reboot at first instance of login window, there's a lot of display flicker.


How reproducible:
Always


Steps to Reproduce:
1. Boot, login, then either logout and switch to console or just switch to console from gnome-shell.

Actual results:
Crash/hang.


Expected results:
No crash or hang.

Additional info:

Comment 1 Chris Murphy 2015-03-22 20:14:15 UTC

Created attachment 1005079 [details]
dmesg

Includes drm.debug=0x06

Comment 2 Chris Murphy 2015-03-22 20:15:14 UTC

Created attachment 1005080 [details]
journal

journalctl -b -l -o short-monotonic

Comment 3 Chris Murphy 2015-03-22 20:23:01 UTC

re: comment 1,  Fn+F2+ctrl+alt was pressed somewhere around 200-203s.

I have no idea what this is because nothing on the local computer was working...

[  205.190928] f22m.localdomain gdm-password][2718]: pam_unix(gdm-password:auth): conversation failed
[  205.191832] f22m.localdomain gdm-password][2718]: pam_unix(gdm-password:auth): auth could not identify password for [chris]
[  205.192653] f22m.localdomain gdm-password][2718]: gkr-pam: no password is available for user
[  205.192861] f22m.localdomain unknown[2718]: <audit-1100> pid=2718 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=? acct="chris" exe="/usr/libexec/gdm-session-worker" hostname=? addr=? terminal=? res=failed'
[  205.193100] f22m.localdomain unknown[2718]: <audit-1112> pid=2718 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='uid=1000 exe="/usr/libexec/gdm-session-worker" hostname=? addr=? terminal=? res=failed'

Comment 4 Chris Murphy 2015-03-24 21:47:11 UTC

This problem doesn't happen with 3.18.9 kernel.

I also get this back trace with normal reboot attempts, which then makes the system unrecoverable and I have to force power off.

Comment 5 Adam Jackson 2015-05-27 15:13:02 UTC


*** This bug has been marked as a duplicate of bug 1203852 ***