Bug 1104371 - i915 intel display got black screen and needs ssh from another box + reset to back to work
Summary: i915 intel display got black screen and needs ssh from another box + reset to...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-03 20:53 UTC by Filipe Rosset
Modified: 2014-07-27 23:57 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-27 23:57:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
current 3.16rc1git4.1 boot tail of journalctl --lines=3000 logged in via telnet (85.06 KB, text/plain)
2014-06-23 02:06 UTC, Felix Miata
no flags Details
dmesg from current 3.16rc1git4.1 boot (43.42 KB, text/plain)
2014-06-23 02:21 UTC, Felix Miata
no flags Details


Links
System ID Private Priority Status Summary Last Updated
FreeDesktop.org 79607 0 None None None Never

Description Filipe Rosset 2014-06-03 20:53:43 UTC
Hi guys, I'm not sure if this issue is kernel related or the culprit is intel driver... Let's see if someone can help me.

The issue is, my old macbook running rawhide suddenly got a black screen (numlock + caps lock still working, I'm able to Ctrl + Alt + F2 then log in and reboot, all the time w/ black screen. SSH into this macbook + reboot also works.

The only log I was able to catch is here, stack trace from /var/log/messages:

Jun  3 17:19:41 rosset-server kernel: ------------[ cut here ]------------
Jun  3 17:19:41 rosset-server kernel: WARNING: CPU: 1 PID: 1 at drivers/gpu/drm/i915/intel_display.c:931 assert_pll+0x6f/0x80 [i915]()
Jun  3 17:19:41 rosset-server kernel: PLL state assertion failure (expected on, current off)
Jun  3 17:19:41 rosset-server kernel: Modules linked in: bnep bluetooth fuse xt_CHECKSUM ipt_MASQUERADE ip6t_rpfilter ip6t_REJECT xt_conntrack ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw nls_utf8 hfsplus arc4 b43 bcma uvcvideo mac80211 videobuf2_vmalloc videobuf2_memops videobuf2_core cfg80211 videodev joydev rfkill media hid_appleir appletouch iTCO_wdt iTCO_vendor_support coretemp applesmc i915 ssb snd_hda_codec_realtek kvm_intel input_polldev snd_hda_codec_generic snd_hda_intel mmc_core kvm microcode snd_hda_controller i2c_algo_bit i2c_i801 lpc_ich mfd_core
Jun  3 17:19:41 rosset-server kernel: snd_hda_codec snd_hwdep snd_seq snd_seq_device drm_kms_helper snd_pcm snd_timer snd soundcore drm sbs sbshc shpchp apple_bl i2c_core video acpi_cpufreq sunrpc binfmt_misc firewire_ohci firewire_core sky2 ata_generic pata_acpi crc_itu_t
Jun  3 17:19:41 rosset-server kernel: CPU: 1 PID: 1 Comm: systemd Tainted: G        W     3.15.0-0.rc8.git0.1.fc21.x86_64 #1
Jun  3 17:19:41 rosset-server kernel: Hardware name: Apple Inc. MacBook4,1/Mac-F22788A9, BIOS     MB41.88Z.00C1.B00.0802091535 02/09/08
Jun  3 17:19:41 rosset-server kernel: 0000000000000000 00000000dce7dce6 ffff880139b2f920 ffffffff817019c4
Jun  3 17:19:41 rosset-server kernel: ffff880139b2f968 ffff880139b2f958 ffffffff8108a20d 0000000000000001
Jun  3 17:19:41 rosset-server kernel: ffff8800bcfc1000 000000000000a000 0000000000000000 ffff8800bceed000
Jun  3 17:19:41 rosset-server kernel: Call Trace:
Jun  3 17:19:41 rosset-server kernel: [<ffffffff817019c4>] dump_stack+0x45/0x56
Jun  3 17:19:41 rosset-server kernel: [<ffffffff8108a20d>] warn_slowpath_common+0x7d/0xa0
Jun  3 17:19:41 rosset-server kernel: [<ffffffff8108a28c>] warn_slowpath_fmt+0x5c/0x80
Jun  3 17:19:41 rosset-server kernel: [<ffffffffa0372dab>] ? gen4_read32+0x4b/0xc0 [i915]
Jun  3 17:19:41 rosset-server kernel: [<ffffffffa0380d9f>] assert_pll+0x6f/0x80 [i915]
Jun  3 17:19:41 rosset-server kernel: [<ffffffffa03869c1>] intel_crtc_load_lut+0x1d1/0x1f0 [i915]
Jun  3 17:19:41 rosset-server kernel: [<ffffffffa01731ee>] drm_fb_helper_setcmap+0x38e/0x480 [drm_kms_helper]
Jun  3 17:19:41 rosset-server kernel: [<ffffffff813cca9c>] fb_set_cmap+0x6c/0x150
Jun  3 17:19:41 rosset-server kernel: [<ffffffff813bf0fc>] fbcon_set_palette+0x14c/0x180
Jun  3 17:19:41 rosset-server kernel: [<ffffffff813c1b1d>] fbcon_switch+0x3bd/0x5e0
Jun  3 17:19:41 rosset-server kernel: [<ffffffff8143ffe9>] redraw_screen+0x1a9/0x250
Jun  3 17:19:41 rosset-server kernel: [<ffffffff814401c6>] csi_J+0x136/0x140
Jun  3 17:19:41 rosset-server kernel: [<ffffffff8144366f>] do_con_trol+0x12cf/0x1580
Jun  3 17:19:41 rosset-server kernel: [<ffffffff813bfe61>] ? fbcon_cursor+0x111/0x190
Jun  3 17:19:41 rosset-server kernel: [<ffffffff81443b2e>] do_con_write.part.20+0x20e/0xaa0
Jun  3 17:19:41 rosset-server kernel: [<ffffffff81706ed2>] ? down_read+0x12/0x30
Jun  3 17:19:41 rosset-server kernel: [<ffffffff8144447d>] con_write+0x6d/0x80
Jun  3 17:19:41 rosset-server kernel: [<ffffffff8142cafd>] n_tty_write+0x1fd/0x560
Jun  3 17:19:41 rosset-server kernel: [<ffffffff810beba0>] ? wake_up_state+0x20/0x20
Jun  3 17:19:41 rosset-server kernel: [<ffffffff81429314>] tty_write+0x174/0x300
Jun  3 17:19:41 rosset-server kernel: [<ffffffff8142c900>] ? process_echoes+0x70/0x70
Jun  3 17:19:41 rosset-server kernel: [<ffffffff811eedda>] vfs_write+0xba/0x1d0
Jun  3 17:19:41 rosset-server kernel: [<ffffffff811ef9a5>] SyS_write+0x55/0xd0
Jun  3 17:19:41 rosset-server kernel: [<ffffffff812034db>] ? SyS_ioctl+0x6b/0xa0
Jun  3 17:19:41 rosset-server kernel: [<ffffffff81711729>] system_call_fastpath+0x16/0x1b
Jun  3 17:19:41 rosset-server kernel: ---[ end trace 748d7e01904abe69 ]---




[filiperosset@rosset-server ~]$ rpm -qa | grep xorg | grep intel
xorg-x11-drv-intel-2.99.911-2.fc21.x86_64

[filiperosset@rosset-server ~]$ rpm -qa | grep kernel | grep rc8 | sort
kernel-3.15.0-0.rc8.git0.1.fc21.x86_64
kernel-core-3.15.0-0.rc8.git0.1.fc21.x86_64
kernel-devel-3.15.0-0.rc8.git0.1.fc21.x86_64
kernel-headers-3.15.0-0.rc8.git0.1.fc21.x86_64
kernel-modules-3.15.0-0.rc8.git0.1.fc21.x86_64
kernel-modules-extra-3.15.0-0.rc8.git0.1.fc21.x86_64
kernel-tools-3.15.0-0.rc8.git0.1.fc21.x86_64
kernel-tools-libs-3.15.0-0.rc8.git0.1.fc21.x86_64

Comment 1 Filipe Rosset 2014-06-03 21:04:19 UTC
I'm also available to validate any other patch/issue/bug in this hardware (MacBook4,1), just let me know if I can help in any way.

Comment 2 Felix Miata 2014-06-23 02:06:13 UTC
Created attachment 911236 [details]
current 3.16rc1git4.1 boot tail of journalctl --lines=3000 logged in via telnet

This sounds a bit like what just happened to me on i865G host gx270 I last updated 8 May to 3.15rc4git2.1. Upgrading a bit ago I got 3.16rc1git4.1. Rebooting via my master Grub Legacy loading kernel with 'noplymouth (and/or) plymouth.enable=0 noresume vga=791 video=1024x768@60 3' on cmdline and initrd directly (same as always since I install no bootloader to any Fedora since Grub Legacy was dropped) boot messages appear to get near init completion, then the screen goes black and stays black. I can log in, but have no idea what to try to do flying blind. Prior kernel still works as expected.

Comment 3 Felix Miata 2014-06-23 02:14:46 UTC
Comment on attachment 911236 [details]
current 3.16rc1git4.1 boot tail of journalctl --lines=3000 logged in via telnet

lspci output:
00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)
00:06.0 System peripheral: Intel Corporation 82865G/PE/P Processor to I/O Memory Interface (rev 02)
00:1d.0 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 (rev 02)
00:1d.3 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 (rev 02)
00:1d.7 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
01:0c.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)

Comment 4 Filipe Rosset 2014-06-23 02:17:25 UTC
Hi guys, 

I'm unable to reproduce the issue since 3.15 final. I'm still running 3.15 over rawhide, because I need this macbook a bit more stable to finish some work from my side, so I'm planning to upgrade it again in next week.

There are more details here in upstrea bug:
http://bugs.freedesktop.org/show_bug.cgi?id=79607

Comment 5 Felix Miata 2014-06-23 02:21:47 UTC
Created attachment 911237 [details]
dmesg from current 3.16rc1git4.1 boot

Comment 6 Hans de Goede 2014-06-23 06:18:25 UTC
Hi,

(In reply to Felix Miata from comment #2)
> Created attachment 911236 [details]
> current 3.16rc1git4.1 boot tail of journalctl --lines=3000 logged in via
> telnet
> 
> This sounds a bit like what just happened to me on i865G host gx270

Please don't jump on to bugs about hardware issues because "This sounds a bit like what just happened", unless you've the exact same hardware as the reporter.

Please file a new bug for this.

Regards,

Hans

Comment 7 Adam Williamson 2014-06-25 17:07:15 UTC
Felix: I'm still trying to figure out your situation precisely, but you definitely aren't seeing the same thing as Filipe: none of the logs you've provided here and on test@ show a stack trace. My current theory is your video= parameter is causing your problem, but in any case, please do file it as a new bug, it is not this bug. Thanks.

Comment 8 Filipe Rosset 2014-07-27 23:57:24 UTC
I can't reproduce the issue anymore. Upstream also closed the report because we find no way to reproduce this behavior. I'll re-open if needed.


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