kernel-packages team mailing list archive

[Brad Figg <brad.figg@xxxxxxxxxxxxx>]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1578528

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1578528

Title:
  inteldrmfb: blank VT consoles after many suspend/resume cycles

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  16.04 on an Asus T300CHI (Intel GPU).

  $ uname -a
  Linux T300CHI 4.4.0-21-lowlatency #37-Ubuntu SMP PREEMPT Mon Apr 18 20:20:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

  I found today that switching from X to the VT consoles resulted in a
  blank screen. Switching between VTs likewise. Switching back to the
  GUI on tty7 the (GUI) display returns.

  The system was last booted 4 or 5 days ago and has been through
  several suspend/resume cycles since then.

  Whilst switched to tty1 using a remote SSH shell I adjusted the
  backlight brightness but without revealing any text.

  I then did a blind login and the remote SSH shell showed  a login and
  shell process were started. This seems to indicate the problem is in
  the framebuffer driver.

  I did a system restart and found the VT consoles working fine. I did
  several suspend/resume cycles but so far was unable to reproduce the
  issue.

  I suspect I've not done enough cycles yet, or alternatively the issue
  is triggered by something I did during the previous 5-day boot session
  although I cannot think of anything obvious that could have this
  effect.

  $ lspci -nn
  00:00.0 Host bridge [0600]: Intel Corporation Broadwell-U Host Bridge -OPI [8086:1604] (rev 09)
  00:02.0 VGA compatible controller [0300]: Intel Corporation Broadwell-U Integrated Graphics [8086:161e] (rev 09)
  00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller [8086:160c] (rev 09)
  00:04.0 Signal processing controller [1180]: Intel Corporation Broadwell-U Camarillo Device [8086:1603] (rev 09)
  00:14.0 USB controller [0c03]: Intel Corporation Wildcat Point-LP USB xHCI Controller [8086:9cb1] (rev 03)
  00:16.0 Communication controller [0780]: Intel Corporation Wildcat Point-LP MEI Controller #1 [8086:9cba] (rev 03)
  00:1b.0 Audio device [0403]: Intel Corporation Wildcat Point-LP High Definition Audio Controller [8086:9ca0] (rev 03)
  00:1c.0 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 [8086:9c90] (rev e3)
  00:1c.3 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root Port #4 [8086:9c96] (rev e3)
  00:1f.0 ISA bridge [0601]: Intel Corporation Wildcat Point-LP LPC Controller [8086:9cc7] (rev 03)
  00:1f.2 SATA controller [0106]: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] [8086:9c83] (rev 03)
  00:1f.3 SMBus [0c05]: Intel Corporation Wildcat Point-LP SMBus Controller [8086:9ca2] (rev 03)
  02:00.0 Network controller [0280]: Intel Corporation Wireless 7265 [8086:095a] (rev 59)

  [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-4.4.0-21-lowlatency root=/dev/mapper/VG02-rootfs ro no_console_suspend initcall_debug debug acpi_osi=! "acpi_osi=Windows 2013" splash vt.handoff=7
  [    0.000000] console [tty0] enabled
  [    0.058719] calling  early_efi_map_fb+0x0/0x38 @ 1
  [    0.058721] initcall early_efi_map_fb+0x0/0x38 returned 0 after 0 usecs
  [    0.092260] calling  vtconsole_class_init+0x0/0xbd @ 1
  [    0.092273] initcall vtconsole_class_init+0x0/0xbd returned 0 after 0 usecs
  [    0.111130] calling  fbmem_init+0x0/0x94 @ 1
  [    0.111138] initcall fbmem_init+0x0/0x94 returned 0 after 0 usecs
  [    0.147791] vgaarb: setting as boot device: PCI:0000:00:02.0
  [    0.147793] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
  [    0.147795] vgaarb: loaded
  [    0.147796] vgaarb: bridge control possible 0000:00:02.0
  [    0.158091] calling  proc_consoles_init+0x0/0x22 @ 1
  [    0.158096] initcall proc_consoles_init+0x0/0x22 returned 0 after 0 usecs
  [    0.158293] calling  fb_console_init+0x0/0xfc @ 1
  [    0.158316] initcall fb_console_init+0x0/0xfc returned 0 after 20 usecs
  [    0.158319] calling  simplefb_init+0x0/0x14 @ 1
  [    0.158335] initcall simplefb_init+0x0/0x14 returned 0 after 14 usecs
  [    0.504272] calling  sysfb_init+0x0/0x92 @ 1
  [    0.504292] initcall sysfb_init+0x0/0x92 returned 0 after 15 usecs
  [    0.509020] calling  imsttfb_init+0x0/0x10b @ 1
  [    0.509031] initcall imsttfb_init+0x0/0x10b returned 0 after 8 usecs
  [    0.509033] calling  asiliantfb_init+0x0/0x34 @ 1
  [    0.509042] initcall asiliantfb_init+0x0/0x34 returned 0 after 6 usecs
  [    0.509045] calling  vesafb_driver_init+0x0/0x14 @ 1
  [    0.509055] initcall vesafb_driver_init+0x0/0x14 returned 0 after 6 usecs
  [    0.509058] calling  efifb_driver_init+0x0/0x14 @ 1
  [    0.509063] efifb: probing for efifb
  [    0.509071] efifb: framebuffer at 0xe0000000, mapped to 0xffffc90001000000, using 14400k, total 14400k
  [    0.509073] efifb: mode is 2560x1440x32, linelength=10240, pages=1
  [    0.509073] efifb: scrolling: redraw
  [    0.509075] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
  [    0.509204] fb0: EFI VGA frame buffer device
  [    0.509211] initcall efifb_driver_init+0x0/0x14 returned 0 after 147 usecs
  [    0.696228] fb: switching to inteldrmfb from EFI VGA
  [    0.696355] [drm] Replacing VGA console driver
  [    0.708165] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [    0.810884] fbcon: inteldrmfb (fb0) is primary device
  [    0.811207] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578528/+subscriptions