Bug 998096 - Black screen when Xorg starts after kernel upgrade to 3.10.6-100
Summary: Black screen when Xorg starts after kernel upgrade to 3.10.6-100
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 18
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-17 08:43 UTC by Thomas Lehmann
Modified: 2013-09-28 15:20 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-23 14:31:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
lspci -vvv (24.24 KB, text/plain)
2013-08-17 08:43 UTC, Thomas Lehmann
no flags Details
/proc/cpuinfo (5.15 KB, text/plain)
2013-08-17 08:43 UTC, Thomas Lehmann
no flags Details

Description Thomas Lehmann 2013-08-17 08:43:04 UTC
Created attachment 787527 [details]
lspci -vvv

Description of problem:

Since I've ran "yum update" the screen turned black when Xorg was starting. 

Even switching to the terminals was not possible through Ctrl+Alt-F3 or Shift-Ctrl-Alt-F3. 

I examined the logfiles "messages" and "Xorg.0.log" after booting into single user mode (and later through ssh): noting suspicious found.

When using the older kernel 3.9.11-200 (selected in Grub) Xorg and the logon screen correctly appear. So it has to do with the new kernel.



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

How reproducible: N/A
Steps to Reproduce: N/A
Actual results: N/A
Expected results:  N/A


Additional info:

I've attached my lspci and cpuinfo output.
My hardware is an Asus "UX32VD".
The system is running EFI.

Comment 1 Thomas Lehmann 2013-08-17 08:43:53 UTC
Created attachment 787528 [details]
/proc/cpuinfo

Comment 2 Thomas Lehmann 2013-08-19 20:25:38 UTC
I should clarify my description:

The black screen did not happen during or just after "yum update". I happened each (re)boot of the system.

The "yum update" itself ran without errors.

Please ask, if the description is not clear enough or if further information is necessary.

Comment 3 Greg Sheppard 2013-08-22 02:31:28 UTC
(In reply to Thomas Lehmann from comment #2)
> I should clarify my description:

The black screen did not happen during or
> just after "yum update". I happened each (re)boot of the system.

The "yum
> update" itself ran without errors.

Please ask, if the description is not
> clear enough or if further information is necessary.

My wife is suffering the identical problem on an ASUS TaiChi (Fedora 18). It occurs on boot, after the GRUB screen, in every instance - the Fedora splash displays and then the screen blanks and can only be reset by switching off.

It occurred immediately after an update early August 2013; reverting to the earlier kernel version in GRUB enables normal boot-up - it would therefore appear that something in the upgrade is broken.

Traffic on other sites indicates it may be something to do with one of the xorg-X11 or nouveau files. I have not yet been able to access her logs for any other clues.

Any leads appreciated.

Comment 4 Fredrik Chabot 2013-08-27 13:00:50 UTC
Same problem with all 3.10. series so far (tested 3.10.4, 6 & 7)

Acer Aspire 7535

# lspci
00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge
00:01.0 PCI bridge: Acer Incorporated [ALI] AMD RS780/RS880 PCI to PCI bridge (int gfx)
00:02.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (ext gfx port 0)
00:04.0 PCI bridge: Advanced Micro Devices [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 0)
00:05.0 PCI bridge: Advanced Micro Devices [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 1)
00:11.0 SATA controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode]
00:12.0 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:12.1 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0 USB OHCI1 Controller
00:12.2 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:13.0 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:13.2 USB controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:14.0 SMBus: Advanced Micro Devices [AMD] nee ATI SBx00 SMBus Controller (rev 3a)
00:14.2 Audio device: Advanced Micro Devices [AMD] nee ATI SBx00 Azalia (Intel HDA)
00:14.3 ISA bridge: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 LPC host controller
00:14.4 PCI bridge: Advanced Micro Devices [AMD] nee ATI SBx00 PCI to PCI Bridge
00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 11h Processor HyperTransport Configuration (rev 40)
00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 11h Processor Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 11h Processor DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 11h Processor Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 11h Processor Link Control
01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS780M/RS780MN [Mobility Radeon HD 3200 Graphics]
02:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV710 [Mobility Radeon HD 4500/5100 Series] (rev ff)
02:00.1 Audio device: Advanced Micro Devices [AMD] nee ATI RV710/730 HDMI Audio [Radeon HD 4000 series] (rev ff)
03:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5784M Gigabit Ethernet PCIe (rev 10)
06:00.0 Network controller: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) (rev 01)

Comment 5 Lars S. Jensen 2013-09-20 15:06:19 UTC
(In reply to Thomas Lehmann from comment #0)
> My hardware is an Asus "UX32VD".
> The system is running EFI.

This is a kernel problem on all version fedora running 3.1X:
last kernel tested 3.11.1-200.fc19.x86_64 same issue:-(
Workaround: Disable secure boot and enable Launch CSM

I found the kernel bug that are related to display goes blank:
Issue: bw/lanes/clocks required for bpp=24 and then clamps it down to 18
https://bugzilla.kernel.org/show_bug.cgi?id=59841

UEFI: Boot > Launch CSM don't work in secure boot mode on my Asus Zenbook UX32VD:-(.

Workaround: Disable secure boot and enable Launch CSM
Disable: Boot > Secure Boot and enable: Boot > Launch CSM.
And it works: boot 3.10.7-200 with drm.debug=0xe:

[    1.618948] [drm:intel_modeset_stage_output_state], [CONNECTOR:12:eDP-1] to [CRTC:3]
[    1.618962] [drm:intel_modeset_pipe_config], [CRTC:3]
[    1.618963] [drm:intel_modeset_pipe_config], plane bpp: 24, pipe bpp: 24, dithering: 0

I boot 3.10.7-200 with drm.debug=0xe and CSM disabled then the timing match when display goes blank:

[    1.633515] [drm:intel_modeset_stage_output_state], [CONNECTOR:12:eDP-1] to [CRTC:3]
[    1.633516] [drm:intel_modeset_stage_output_state], crtc changed, full mode switch
[    1.633517] [drm:intel_crtc_set_config], attempting to set mode from userspace
[    1.633519] [drm:drm_mode_debug_printmodeline], Modeline 13:"1920x1080" 60 138780 1920 1966 1996 2080 1080 1082 1086 1112 0x48 0xa
[    1.633522] [drm:intel_dp_compute_config], DP link computation with max lane count 2 max bw 0a pixel clock 138780KHz
[    1.633523] [drm:intel_dp_compute_config], DP link bw 06 lane count 2 clock 162000 bpp 18
[    1.633525] [drm:intel_dp_compute_config], DP link bw required 249804 available 259200
[    1.633526] [drm:intel_modeset_pipe_config], [CRTC:3]
[    1.633527] [drm:intel_modeset_pipe_config], plane bpp: 24, pipe bpp: 18, dithering: 1

And from 3.11.1-200.fc19.x86_64:
[    1.529198] [drm:connected_sink_compute_bpp], [CONNECTOR:12:eDP-1] checking for sink bpp constrains
[    1.529200] [drm:intel_dp_compute_config], DP link computation with max lane count 2 max bw 0a pixel clock 138780KHz
[    1.529201] [drm:intel_dp_compute_config], DP link bw 06 lane count 2 clock 162000 bpp 18
[    1.529203] [drm:intel_dp_compute_config], DP link bw required 249804 available 259200
[    1.529204] [drm:intel_modeset_pipe_config], plane bpp: 24, pipe bpp: 18, dithering: 1
[    1.529206] [drm:intel_dump_pipe_config], [CRTC:3][modeset] config for pipe A
[    1.529206] [drm:intel_dump_pipe_config], cpu_transcoder: A
[    1.529207] [drm:intel_dump_pipe_config], pipe bpp: 18, dithering: 1
[    1.529209] [drm:intel_dump_pipe_config], fdi/pch: 0, lanes: 0, gmch_m: 0, gmch_n: 0, link_m: 0, link_n: 0, tu: 0
[    1.529209] [drm:intel_dump_pipe_config], requested mode:
[    1.529212] [drm:drm_mode_debug_printmodeline], Modeline 0:"1920x1080" 60 138780 1920 1966 1996 2080 1080 1082 1086 1112 0x48 0xa
[    1.529212] [drm:intel_dump_pipe_config], adjusted mode:
[    1.529215] [drm:drm_mode_debug_printmodeline], Modeline 0:"1920x1080" 60 138780 1920 1966 1996 2080 1080 1082 1086 1112 0x48 0xa
[    1.529216] [drm:intel_dump_pipe_config], gmch pfit: control: 0x00000000, ratios: 0x00000000, lvds border: 0x00000000
[    1.529217] [drm:intel_dump_pipe_config], pch pfit: pos: 0x00000000, size: 0x00000000
[    1.529218] [drm:intel_dump_pipe_config], ips: 0
[    1.529220] [drm:ironlake_edp_panel_vdd_on], Turn eDP VDD on
[    1.529221] [drm:ironlake_edp_panel_vdd_on], eDP VDD already on
[    1.529223] [drm:intel_panel_actually_set_backlight], set backlight PWM = 0
[    1.529227] [drm:ironlake_edp_backlight_off],

Comment 6 Garrett Mitchener 2013-09-20 20:22:55 UTC
Related to bug #989763

Comment 7 Garrett Mitchener 2013-09-22 20:39:37 UTC
Cautiously optimistic here... I upgraded my Asus Zenbook UX31A to kernel 3.11.1-200, and I haven't seen the black screen problem.

FYI: I've disabled secure boot, but it's booting through EFI otherwise.

Comment 8 Josh Boyer 2013-09-23 14:31:44 UTC
Let's close this out then.  If you do see it happening again, please reopen.


Note You need to log in before you can comment on or make changes to this bug.