regression on 4.3.x: i945/Display corruption (before X, X never starts))

Bug #1525509 reported by Dave Gilbert
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
High
Unassigned
Nominated for Xenial by Alberto Salvia Novella

Bug Description

This laptop works with 4.2.0-19 and fails with 4.3.0-2.

At boot (before X) the display is corrupt - with the entire screen shifted halfway across the screen with the kernel boot text mostly readable, just shifted over (and some crud at the top). X doesn't start. Returning to 4.2.0-19 (as now) and it's fine.

In the 4.3.0-2 world I see the following warning in the dmesg:
[ 14.118080] WARNING: CPU: 1 PID: 14 at /build/linux-Os09TY/linux-4.3.0/drivers/gpu/drm/drm_atomic.c:491 drm_atomic_check_only+0x46e/0x540 [drm]()
[ 14.119902] Modules linked in: parport_pc ppdev lp parport autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea firewire_ohci sysfillrect sysimgblt fb_sys_fops psmouse firewire_core sdhci_pci e100 pata_acpi mii sdhci crc_itu_t drm fjes video
[ 14.123614] CPU: 1 PID: 14 Comm: kworker/1:0 Tainted: G W 4.3.0-2-generic #11-Ubuntu
[ 14.125467] Hardware name: TOSHIBA Equium A100/MPAD-MSAE Customer Reference Boards, BIOS 2.10 10/23/2006
[ 14.127339] Workqueue: events output_poll_execute [drm_kms_helper]
[ 14.129181] 0000000000000000 00000000fe15c8fd ffff8800bb01ba38 ffffffff813d23a4
[ 14.131009] 0000000000000000 ffff8800bb01ba70 ffffffff8107d082 ffff88003590a000
[ 14.132820] ffff8800b4d61400 0000000000000001 0000000000000000 ffff8800ba182e00
[ 14.134621] Call Trace:
[ 14.136413] [<ffffffff813d23a4>] dump_stack+0x44/0x60
[ 14.138207] [<ffffffff8107d082>] warn_slowpath_common+0x82/0xc0
[ 14.139990] [<ffffffff8107d1ca>] warn_slowpath_null+0x1a/0x20
[ 14.141782] [<ffffffffc004ab9e>] drm_atomic_check_only+0x46e/0x540 [drm]
[ 14.143569] [<ffffffffc004ad5d>] ? drm_atomic_set_fb_for_plane+0x2d/0x90 [drm]
[ 14.145374] [<ffffffffc004ac87>] drm_atomic_commit+0x17/0x60 [drm]
[ 14.147211] [<ffffffffc01b3ba5>] intel_get_load_detect_pipe+0x3d5/0x530 [i915]
[ 14.149029] [<ffffffffc01eac8d>] intel_tv_detect+0x13d/0x5f0 [i915]
[ 14.150801] [<ffffffffc004546e>] ? drm_get_edid+0x3e/0x3f0 [drm]
[ 14.152543] [<ffffffff817f9d36>] ? schedule_hrtimeout_range_clock.part.23+0xa6/0x150
[ 14.154271] [<ffffffffc011dd05>] drm_helper_probe_single_connector_modes_merge_bits+0x235/0x4d0 [drm_kms_helper]
[ 14.156025] [<ffffffffc011dfb3>] drm_helper_probe_single_connector_modes+0x13/0x20 [drm_kms_helper]
[ 14.157757] [<ffffffffc01297fc>] drm_fb_helper_hotplug_event+0x8c/0x120 [drm_kms_helper]
[ 14.159513] [<ffffffffc01c39fe>] intel_fbdev_output_poll_changed+0x1e/0x30 [i915]
[ 14.161261] [<ffffffffc011d657>] drm_kms_helper_hotplug_event+0x27/0x30 [drm_kms_helper]
[ 14.163031] [<ffffffffc011d857>] output_poll_execute+0x197/0x1e0 [drm_kms_helper]
[ 14.164808] [<ffffffff810961aa>] process_one_work+0x1aa/0x440
[ 14.166567] [<ffffffff8109648b>] worker_thread+0x4b/0x4c0
[ 14.168326] [<ffffffff81096440>] ? process_one_work+0x440/0x440
[ 14.170068] [<ffffffff8109c6e8>] kthread+0xd8/0xf0
[ 14.171821] [<ffffffff8109c610>] ? kthread_create_on_node+0x1e0/0x1e0
[ 14.173577] [<ffffffff817fae8f>] ret_from_fork+0x3f/0x70
[ 14.175317] [<ffffffff8109c610>] ? kthread_create_on_node+0x1e0/0x1e0
[ 14.177081] ---[ end trace cdd47054bd68533c ]---

This is running an up to date Xenial.

Dave

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.3.0-2-generic 4.3.0-2.11
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: dg 1407 F.... pulseaudio
CurrentDesktop: KDE
Date: Sat Dec 12 12:41:55 2015
HibernationDevice: RESUME=/dev/mapper/davros--vg-swap_1
InstallationDate: Installed on 2013-11-15 (756 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131115)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: TOSHIBA Equium A100
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-19-generic root=/dev/mapper/hostname--vg-root ro
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-19-generic N/A
 linux-backports-modules-4.2.0-19-generic N/A
 linux-firmware 1.154
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: yes
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2015-11-08 (33 days ago)
dmi.bios.date: 10/23/2006
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 2.10
dmi.board.name: MPAD-MSAE Customer Reference Boards
dmi.board.vendor: Intel Corporation
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr2.10:bd10/23/2006:svnTOSHIBA:pnEquiumA100:pvrPSAABE-00J008EN:rvnIntelCorporation:rnMPAD-MSAECustomerReferenceBoards:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: Equium A100
dmi.product.version: PSAABE-00J008EN
dmi.sys.vendor: TOSHIBA

Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :
Download full text (22.3 KiB)

The 4.4.0-999-generic daily (201512120150) seems to work.
Although there's a whole bunch of slowpath warnings in the logs.
(I say seems to work - I'm running it now in KDE apparently OK; on the first boot the desktop didn't complete starting up but ti wasn't obvious why, X was still responsive just apps didn't start; but that seems different?)

Here's the current boot warnings in the working 4.4:
[ 4.012238] ------------[ cut here ]------------
[ 4.012339] WARNING: CPU: 0 PID: 143 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:1407 assert_planes_disabled+0x102/0x140 [i915]()
[ 4.012358] plane B assertion failure, should be off on pipe B but is still active
[ 4.012373] Modules linked in: psmouse sdhci_pci pata_acpi(+) i915(+) e100 mii firewire_ohci i2c_algo_bit drm_kms_helper sdhci syscopyarea sysfillrect firewire_core sysimgblt crc_itu_t fb_sys_fops drm fjes video
[ 4.012436] CPU: 0 PID: 143 Comm: systemd-udevd Not tainted 4.4.0-999-generic #201512120150
[ 4.012452] Hardware name: TOSHIBA Equium A100/MPAD-MSAE Customer Reference Boards, BIOS 2.10 10/23/2006
[ 4.012468] 0000000000000000 000000009cbb9ea2 ffff8800354a3608 ffffffff813c8b04
[ 4.012487] ffff8800354a3650 ffff8800354a3640 ffffffff8107d692 ffff880035670000
[ 4.012506] 0000000000000001 0000000000000042 0000000000000042 ffff880035670034
[ 4.012525] Call Trace:
[ 4.012541] [<ffffffff813c8b04>] dump_stack+0x44/0x60
[ 4.012555] [<ffffffff8107d692>] warn_slowpath_common+0x82/0xc0
[ 4.012567] [<ffffffff8107d72c>] warn_slowpath_fmt+0x5c/0x80
[ 4.012626] [<ffffffffc016be38>] ? gen2_read32+0x28/0x90 [i915]
[ 4.012670] [<ffffffffc017b692>] assert_planes_disabled+0x102/0x140 [i915]
[ 4.012715] [<ffffffffc01860fb>] intel_disable_pipe+0x4b/0x2c0 [i915]
[ 4.012745] [<ffffffffc003f0ec>] ? drm_crtc_vblank_get+0x1c/0x20 [drm]
[ 4.012790] [<ffffffffc018a12f>] i9xx_crtc_disable+0x7f/0x450 [i915]
[ 4.012834] [<ffffffffc01820fc>] ? intel_crtc_disable_planes+0xdc/0xf0 [i915]
[ 4.012881] [<ffffffffc018f256>] intel_crtc_disable_noatomic+0x66/0xe0 [i915]
[ 4.012928] [<ffffffffc0196051>] intel_modeset_setup_hw_state+0xac1/0xdd0 [i915]
[ 4.012977] [<ffffffffc0197db9>] intel_modeset_init+0x939/0x11e0 [i915]
[ 4.013026] [<ffffffffc01d0bd8>] i915_driver_load+0xaf8/0xf30 [i915]
[ 4.013036] [<ffffffff81724217>] ? netlink_broadcast_filtered+0x137/0x3c0
[ 4.013044] [<ffffffff813cbfa0>] ? cleanup_uevent_env+0x10/0x10
[ 4.013052] [<ffffffff813cc34b>] ? kobject_uevent_env+0x15b/0x640
[ 4.013060] [<ffffffff815234c7>] ? get_device+0x17/0x20
[ 4.013068] [<ffffffff81529755>] ? klist_class_dev_get+0x15/0x20
[ 4.013077] [<ffffffff817ef5a7>] ? klist_node_init+0x37/0x50
[ 4.013084] [<ffffffff817ef630>] ? klist_add_tail+0x20/0x50
[ 4.013091] [<ffffffff815251e2>] ? device_add+0x232/0x680
[ 4.013112] [<ffffffffc00411e7>] drm_dev_register+0xa7/0xb0 [drm]
[ 4.013133] [<ffffffffc004377d>] drm_get_pci_dev+0x8d/0x1e0 [drm]
[ 4.013169] [<ffffffffc01161e4>] i915_pci_probe+0x34/0x50 [i915]
[ 4.013179] [<ffffffff81418905>] local_pci_probe+0x45/0xa0
[ 4.013187] [<ffffffff81419d43>] pci_dev...

Changed in linux (Ubuntu):
importance: Undecided → Critical
Changed in linux (Ubuntu):
importance: Critical → High
penalvch (penalvch)
tags: added: bios-outdated-6.00
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in steam (Ubuntu):
status: New → Confirmed
Changed in steam (Ubuntu):
importance: Undecided → Critical
Changed in linux (Ubuntu):
importance: High → Critical
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Does it happen if the "intel-microcode" package is installed?

When answered, please set this bug status back to "confirmed". Thank you.

no longer affects: steam (Ubuntu)
tags: added: kernel-graphics
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Also please check if bug #1522922 is a duplicate.

penalvch (penalvch)
Changed in linux (Ubuntu):
importance: Critical → High
Revision history for this message
Felix Schwarz (felix-schwarz) wrote :

While I can't claim any authority on the subject I don't think bug #1522922 is a duplicate because this bug is a regression starting from 4.3 without any mentioning of Displaylink.

There are similar reports for Fedora (https://bugzilla.redhat.com/show_bug.cgi?id=1298878), Debian (http://bugs.debian.org/808916) and upstream (https://bugs.freedesktop.org/show_bug.cgi?id=92718).

If you're experiencing the problem can you please check if upgrading the kernel to 4.4 helps?

Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

I can confirm this is fixed in 4.4.0-4, except that is by the WARN_ON(!connector_state->crtc) warn/backtrace.

Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Brad Figg (brad-figg) wrote :

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Dave Gilbert, would you need a backport to a release prior to Xenial?

If not, please mark this as Status Invalid.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

No, not needed on earlier than xenial (utopic worked fine) - someone should probably look at the oops though that backtrace that I still see in the logs - but it's only a low, since everything apparently works.

penalvch (penalvch)
Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.