Bug 187571 - HDMI unplug undetected, dmesg shows `WARNING: CPU: 0 PID: 38 at drivers/gpu/drm/i915/intel_dp.c:1062 intel_dp_aux_transfer+0x1dc/0x220 [i915] WARN_ON(!msg->buffer != !msg->size)` on boot
Summary: HDMI unplug undetected, dmesg shows `WARNING: CPU: 0 PID: 38 at drivers/gpu/d...
Status: RESOLVED INVALID
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(Other) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_video-other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-13 23:02 UTC by Leho Kraav
Modified: 2016-11-16 19:08 UTC (History)
0 users

See Also:
Kernel Version: 4.9-rc5
Tree: Mainline
Regression: No


Attachments
dmesg.txt (230.85 KB, text/plain)
2016-11-13 23:02 UTC, Leho Kraav
Details

Description Leho Kraav 2016-11-13 23:02:26 UTC
Created attachment 244341 [details]
dmesg.txt

I'm getting a flood of these WARNINGs on boot. Did not happen on 4.8-series.

...
nov   14 00:52:46 papaya kernel: [drm] Memory usable by graphics device = 2048M
nov   14 00:52:46 papaya kernel: [drm] VT-d active for gfx access
nov   14 00:52:46 papaya kernel: [drm] Replacing VGA console driver
nov   14 00:52:46 papaya kernel: [drm] DMAR active, disabling use of stolen memory
nov   14 00:52:46 papaya kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
nov   14 00:52:46 papaya kernel: [drm] Driver supports precise vblank timestamp query.
nov   14 00:52:46 papaya kernel: vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
nov   14 00:52:46 papaya kernel: ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
nov   14 00:52:46 papaya kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6
nov   14 00:52:46 papaya kernel: [drm] Initialized i915 1.6.0 20160919 for 0000:00:02.0 on minor 0
nov   14 00:52:46 papaya kernel: ------------[ cut here ]------------
nov   14 00:52:46 papaya kernel: WARNING: CPU: 0 PID: 38 at drivers/gpu/drm/i915/intel_dp.c:1062 intel_dp_aux_transfer+0x1dc/0x220 [i915]
nov   14 00:52:46 papaya kernel: WARN_ON(!msg->buffer != !msg->size)
nov   14 00:52:46 papaya kernel: Modules linked in:
nov   14 00:52:46 papaya kernel:  crc32_pclmul i915 fbcon bitblit softcursor font intel_gtt sdhci_pci sdhci mmc_core drm_kms_helper cfbfillrect syscopyarea cfbimgblt ehci_pci sysfillrect sysimgblt ehci_hcd fb_sys_
nov   14 00:52:46 papaya kernel: CPU: 0 PID: 38 Comm: kworker/0:1 Tainted: G     U          4.9.0-rc5-bfq-gentoo+ #20
nov   14 00:52:46 papaya kernel: Hardware name: Dell Inc. Latitude E7440/0PC4X0, BIOS A18 04/28/2016
nov   14 00:52:46 papaya kernel: Workqueue: events i915_hotplug_work_func [i915]
nov   14 00:52:46 papaya kernel:  ffffc90000167b98 ffffffff8137adfb ffffc90000167be8 0000000000000000
nov   14 00:52:46 papaya kernel:  ffffc90000167bd8 ffffffff810523cc 00000426607500e1 ffffc90000167ca8
nov   14 00:52:46 papaya kernel:  ffff880407a800e0 0000000000000003 0000000000000000 ffff880407a80158
nov   14 00:52:46 papaya kernel: Call Trace:
nov   14 00:52:46 papaya kernel:  [<ffffffff8137adfb>] dump_stack+0x4d/0x72
nov   14 00:52:46 papaya kernel:  [<ffffffff810523cc>] __warn+0xcc/0xf0
nov   14 00:52:46 papaya kernel:  [<ffffffff8105243a>] warn_slowpath_fmt+0x4a/0x50
nov   14 00:52:46 papaya kernel:  [<ffffffffa021a31c>] ? intel_dp_aux_transfer+0xcc/0x220 [i915]
nov   14 00:52:46 papaya kernel:  [<ffffffffa021a42c>] intel_dp_aux_transfer+0x1dc/0x220 [i915]
nov   14 00:52:46 papaya kernel:  [<ffffffffa00f0bc8>] drm_dp_dpcd_access+0x58/0xf0 [drm_kms_helper]
nov   14 00:52:46 papaya kernel:  [<ffffffffa00f0c76>] drm_dp_dpcd_write+0x16/0x20 [drm_kms_helper]
nov   14 00:52:46 papaya kernel:  [<ffffffffa0215cc8>] intel_dp_start_link_train+0x2a8/0x4c0 [i915]
nov   14 00:52:46 papaya kernel:  [<ffffffffa0217106>] intel_dp_check_link_status+0xb6/0xf0 [i915]
nov   14 00:52:46 papaya kernel:  [<ffffffffa021ba0b>] intel_dp_detect+0x72b/0xbb0 [i915]
nov   14 00:52:46 papaya kernel:  [<ffffffffa02049ff>] i915_hotplug_work_func+0x1df/0x2b0 [i915]
nov   14 00:52:46 papaya kernel:  [<ffffffff8106a3a0>] process_one_work+0x140/0x3e0
nov   14 00:52:46 papaya kernel:  [<ffffffff8106a689>] worker_thread+0x49/0x480
nov   14 00:52:46 papaya kernel:  [<ffffffff8106a640>] ? process_one_work+0x3e0/0x3e0
nov   14 00:52:46 papaya kernel:  [<ffffffff8106a640>] ? process_one_work+0x3e0/0x3e0
nov   14 00:52:46 papaya kernel:  [<ffffffff8106f9a5>] kthread+0xc5/0xe0
nov   14 00:52:46 papaya kernel:  [<ffffffff8106f8e0>] ? kthread_park+0x60/0x60
nov   14 00:52:46 papaya kernel:  [<ffffffff81632fd2>] ret_from_fork+0x22/0x30
nov   14 00:52:46 papaya kernel: ---[ end trace 60f064180c1be639 ]---
nov   14 00:52:46 papaya kernel: ------------[ cut here ]------------
Comment 1 Leho Kraav 2016-11-14 14:51:04 UTC
Another worrying artifact of 4.9-rc4+ is that my laptop is not able to detect a HDMI connection unplugging anymore. When looking at the stack trace of the WARNING, `hotplug` and `link_status` stuff is involved in the chain. I wonder if these symptoms are related to each other.
Comment 2 Leho Kraav 2016-11-14 14:55:05 UTC
One suspend/resume cycle seems to properly reset the connector status. Gnome Display settings only shows the laptop panel now.
Comment 3 Jani Nikula 2016-11-16 15:30:23 UTC
Please file drm/i915 bugs at https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel
Comment 4 Leho Kraav 2016-11-16 19:08:13 UTC
Thanks. I wonder if https://bugs.freedesktop.org/show_bug.cgi?id=97344 is already the right one.

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