Bug 10104

Summary:	Regression: Radeon: System hang when switching back from VT
Product:	Mageia	Reporter:	Morgan Leijström <fri>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	critical
Priority:	release_blocker	CC:	tmb
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	fglrx-kernel-3.8.13-desktop-1.mga3	CVE:
Status comment:

Description Morgan Leijström 2013-05-15 11:01:03 CEST

Now updated to latest kernel and driver, reboot, login to KDE.
Then decided to Ctrl-Alt-F12 to check if bug 10033 is better. Nope.
Ctrl-Alt-F1 to get back to KDE.
Black. And screen powers off.
No reaction on Ctrl-Alt-F2, enter root, password, poweroff
No reaction on pressing power button a second (use to make system shut down)

Reboot, enter safe mode. Did not see anything interesting in messages nor kernel logs. Last line in xorg.0.log is:
AIGLX: Resuming AIGLX clients after VT switch

Last lines in .xsession-errors:
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:189:21: QML TextEdit: MÃÃÂ¶jlig fÃÃÂ¶rankringssnurra detekterad vid ifyllnad.
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:143:13: QML Item: Bindningssnurra detekterades fÃÃÂ¶r egenskap "height"
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:143:13: QML Item: Bindningssnurra detekterades fÃÃÂ¶r egenskap "height"
file:///usr/lib64/kde4/imports/org/kde/plasma/components/TabBar.qml:150:5: QML Item: MÃÃÂ¶jlig fÃÃÂ¶rankringssnurra detekterad vid ifyllnad.
file:///usr/lib64/kde4/imports/org/kde/plasma/components/TabBar.qml:150:5: QML Item: MÃÃÂ¶jlig fÃÃÂ¶rankringssnurra detekterad vid ifyllnad.

Translations:
MÃÃÂ¶jlig fÃÃÂ¶rankringssnurra detekterad vid ifyllnad.
Possible anchoring loop detected during filling in.

Bindningssnurra detekterades fÃÃÂ¶r egenskap
Binding loop was detected for property

Before last update i have also had other problems:
Garbled VT: Bug 10033, Bug 9877

Reproducible:

Steps to Reproduce:

Morgan Leijström 2013-05-15 11:01:44 CEST

Priority: Normal => release_blocker
Summary: Regression: System hang when switching back from VT => Regression: Radeon: System hang when switching back from VT

Comment 1 Morgan Leijström 2013-05-15 11:19:03 CEST

Repeatability: i can log in to KDE, Ctrl-Alt-F12, Ctrl-Alt-F1, bang.

I do  not know what to set this bug against really;

Using 
  fglrx-kernel-3.8.13-desktop-1.mga3
  kernel-desktop-3.8.13-1.mga3

Graphic card: Radeon HD 6850

Reported crash is with driver 
  Radeon HD 6400 and later (radeon/fglrx)

I now changed to 
  ATI Radeon HD 5000 and later without free driver (vesa/fglrx)
And it do not crash, though still it say fglrx.
(and still see bug 10033, but not bug 9877)
(and everything is OK using xorg ati, except power handling)

So problem is with "radeon" but i do not know which package that is.

Source RPM: (none) => fglrx-kernel-3.8.13-desktop-1.mga3

Comment 2 Thomas Backlund 2013-05-16 12:15:52 CEST

do you have latest fglrx ?

what does "rpm -qa |grep fglrx" show?

what exact card do you have?

(check with "lspcidrake -v |grep Card")

CC: (none) => tmb

Comment 3 Morgan Leijström 2013-05-16 14:39:53 CEST

Ah, great, it is fixed by fglrx i think.
Do not crash now, but as noted in Bug 10033 there ought to be many lines and rows, now i have very big characters.

[root@svarten morgan]# rpm -qa |grep fglrx
fglrx-control-center-12.104-2.mga3.nonfree
fglrx-kernel-3.8.11-desktop-1.mga3-12.104-3.mga3.nonfree
fglrx-kernel-desktop-latest-12.104-7.mga3.nonfree
fglrx-kernel-3.8.12-desktop-2.mga3-12.104-5.mga3.nonfree
fglrx-kernel-3.8.13-desktop-1.mga3-12.104-7.mga3.nonfree
x11-driver-video-fglrx-12.104-2.mga3.nonfree
fglrx-kernel-3.8.12-desktop-1.mga3-12.104-4.mga3.nonfree
dkms-fglrx-12.104-2.mga3.nonfree
[root@svarten morgan]# lspcidrake -v |grep Card
Card:ATI Radeon HD 6400 and later (radeon/fglrx): Advanced Micro Devices [AMD] nee ATI|Barts PRO [Radeon HD 6850] [DISPLAY_VGA] (vendor:1002 device:6739 subv:1787 subd:200f)

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 4 Morgan Leijström 2013-05-22 11:46:56 CEST

Maybe not solved completely, but i opened a new: Bug 10216