Bug 803099 - radeon: sudden blackscreen on switching vt-x
Summary: radeon: sudden blackscreen on switching vt-x
Status: RESOLVED WONTFIX
Alias: None
Product: openSUSE 12.3
Classification: openSUSE
Component: Kernel (show other bugs)
Version: RC 1
Hardware: x86-64 SUSE Other
: P5 - None : Minor (vote)
Target Milestone: ---
Assignee: Takashi Iwai
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-11 15:24 UTC by Elmar Stellnberger
Modified: 2015-01-05 15:55 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
/var/log/messages (65.08 KB, application/x-bzip2)
2013-02-11 15:24 UTC, Elmar Stellnberger 		Details
/var/log/messages (frontman; another crash) (117.96 KB, application/x-bzip2)
2013-02-13 12:23 UTC, Elmar Stellnberger 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Elmar Stellnberger 2013-02-11 15:24:10 UTC 
User-Agent:       Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:18.0) Gecko/20100101 Firefox/18.0

During bootup I have been switching the virtual terminal from vt-8 to vt-x. Suddenly I got a black screen the backlight flashing (once on, then off). Please have a look at the dmesg to see what has been happening. It was still possible to escape via the SysRq-keys Ctrl-PrScr-S/U/B. To me it looks like if something with the KMS would be screwed up.

Reproducible: Couldn't Reproduce
Comment 1 Elmar Stellnberger 2013-02-11 15:24:35 UTC 
Created attachment 524135 [details]
/var/log/messages
Comment 2 Elmar Stellnberger 2013-02-13 12:23:21 UTC 
Created attachment 524457 [details]
/var/log/messages (frontman; another crash)

  Now, that does not only happend on my FS Amilo/x86_64 notebook but also on my GC Frontman/i686.
  Please have a look.
Comment 3 Elmar Stellnberger 2013-02-13 12:24:23 UTC 
/var/log/messages (frontman; another crash): it was possible to shut down the computer with ctrl-alt-entf after it had blackscreened; messages was taken on next bootup.
Comment 4 Elmar Stellnberger 2013-02-20 10:40:23 UTC 
The same occurrence can evoked by initiating a hibernation deterministically. Please care about this bug at Bug 804649.
Comment 5 Takashi Iwai 2014-03-11 10:54:18 UTC 
Is the problem still present with openSUSE 13.1?
Comment 6 Takashi Iwai 2014-04-14 15:30:33 UTC 
.
Comment 7 Elmar Stellnberger 2014-07-07 15:52:41 UTC 
Well, there still is a similar issue with openSUSE 13.1. If KDE has finished to boot then the screen turns black  suddenly and stays black until I switch multiple times to another vt-X and back. The error has persisted since long and still occurs given the newest updates having been applied recently to oS13.1.
Comment 8 Jeff Mahoney 2015-01-05 15:55:42 UTC 
openSUSE 12.3 has passed out of maintenance. The final openSUSE 12.3 kernel update was released 19 Dec 2014.

The final commit in the changelog reads:
Source Timestamp: 2014-12-16 21:27:58 +0100
GIT Revision: 4c885a114e790eff4a123e7617a06547021a5fb2
GIT Branch: openSUSE-12.3
Distribution: openSUSE 12.3
* Tue Dec 16 2014 bp@suse.de
- Update config files.
- commit 4c885a1

* Tue Dec 16 2014 bp@suse.de
- x86-64, espfix: Don't leak bits 31:16 of %esp returning to
  16-bit stack (bsc#907818,CVE-2014-9090).
- x86, espfix: Make espfix64 a Kconfig option, fix UML
  (bsc#907818,CVE-2014-9090).
- x86, espfix: Make it possible to disable 16-bit support
  (bsc#907818,CVE-2014-9090).
- x86_64/entry/xen: Do not invoke espfix64 on Xen
  (bsc#907818,CVE-2014-9090).
- x86_64, traps: Fix the espfix64 #DF fixup and rewrite it in C
  (bsc#907818,CVE-2014-9090).
- x86_64, traps: Rework bad_iret (bsc#909077,CVE-2014-8133).
- x86_64, traps: Stop using IST for #SS (bsc#907818,
  CVE-2014-9090, CVE-2014-9322).
- Update config files.
- Refresh
  patches.arch/stack-unwind-cfi_ignore-takes-more-arguments.
- Refresh patches.arch/x86_64-unwind-annotations.
- Refresh patches.xen/xen3-patch-2.6.31.
- commit 23e4e06

If you are still experiencing the reported issue, please re-test with openSUSE 13.1, 13.2, or (ideally) openSUSE Factory. If the issue still exists