Summary: | Signal repeatedly lost with USB-C connection to monitor | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | nico-freedesktop.org | ||||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||
Status: | CLOSED WORKSFORME | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||
Severity: | normal | ||||||||
Priority: | medium | CC: | intel-gfx-bugs, jani.nikula | ||||||
Version: | unspecified | ||||||||
Hardware: | Other | ||||||||
OS: | All | ||||||||
Whiteboard: | |||||||||
i915 platform: | KBL | i915 features: | display/atomic | ||||||
Attachments: |
|
Description
nico-freedesktop.org
2018-01-15 08:29:21 UTC
(In reply to nico-freedesktop.org from comment #0) > I am connecting a Dell Latitude 5285 to a Samsung S27H850 by a USB-C cable > (Hama USB 3.1, "full featured"). > > It turns out to be stable working until the first time I suspend. > > Digging through the logs around the time the problem occured, I see the > following (not sure if related or even the reason): > > Jan 14 12:51:35 manager kernel: RSP: 002b:00007fff80429728 EFLAGS: 00000246 > Jan 14 12:51:35 manager kernel: Failed to release pages: bind_count=1, > pages_pin_count=1, pin_display=0 That's an unrelated, mild warning. > And later: > > Jan 14 14:43:44 manager kernel: [drm] Reducing the compressed framebuffer > size. This may lead to less power savings than a non-reduced-size. Try to > increase stolen memory size if available in BIOS. > Jan 14 14:43:51 manager kernel: usb 1-3: new high-speed USB device number 31 > using xhci_hcd > Jan 14 14:43:52 manager kernel: acpi INT3400:00: Unsupported event [0x86] Indicates that the USB connection dropped and triggered an interrupt that the acpi driver didn't handle. That maybe relevant. Please attach the drm.debug=0xe dmesg from across the suspend to see if their is a problem closer to home. Created attachment 136807 [details]
dmesg.txt
Just rebooted with dmesg.debug=0xe and had the screen connected on boot. Funnily this time it does not require a suspend at all for the flacky behaviour. Attached above is the dmesg output. Created attachment 136830 [details]
dmesg post crash
After disconnecting the monitor from the display port adapter and then connecting it directly via usb-c, the connection is also stable.
Until I suspend, then xorg crashes. Attached is the dmesg after the crash.
First of all. Sorry about spam. This is mass update for our bugs. Sorry if you feel this annoying but with this trying to understand if bug still valid or not. If bug investigation still in progress, please ignore this and I apologize! If you think this is not anymore valid, please comment to the bug that can be closed. If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug. Yes, the problem still exists in 4.15.11-1-ARCH with the following xorg components: [root@manager ~]# pacman -Q | grep xorg xorg-appres 1.0.5-1 xorg-bdftopcf 1.1-1 xorg-font-util 1.3.1-1 xorg-font-utils 7.6-4 xorg-fonts-alias 1.0.3-1 xorg-fonts-encodings 1.0.4-4 xorg-fonts-misc 1.0.3-5 xorg-luit 1.1.1-2 xorg-mkfontdir 1.0.7-8 xorg-mkfontscale 1.1.3-1 xorg-server 1.19.6+13+gd0d1a694f-1 xorg-server-common 1.19.6+13+gd0d1a694f-1 xorg-server-xvfb 1.19.6+13+gd0d1a694f-1 xorg-setxkbmap 1.3.1-1 xorg-xauth 1.0.10-1 xorg-xbacklight 1.2.2-1 xorg-xdpyinfo 1.3.2-1 xorg-xev 1.2.2-1 xorg-xinit 1.4.0-3 xorg-xinput 1.6.2-1 xorg-xkbcomp 1.4.1-1 xorg-xkill 1.0.5-1 xorg-xmodmap 1.0.9-1 xorg-xrandr 1.5.0-1 xorg-xrdb 1.1.1-1 xorg-xset 1.2.4-1 xorg-xwd 1.0.7-1 xorg-xwininfo 1.1.4-1 xorgproto 2018.4-1 [root@manager ~]# Jani, do you have a link to the latst upstream git repo? And it only requires to replace the .so from the intel driver & xorg restart or full system reboot? Latest drm-tip from here: https://cgit.freedesktop.org/drm-tip Closing, please re-open is issue still exists. It still exists on the same device. Cannot reproduce it on Lenovo X1 carbon, but certainly exists for the Dell Latidute 5285. Did you test latest drm-tip mentioned on comment #7? Jani, any advice here? No feedback from many months, closing as resolved works for me. Please try to reproduce the error using drm-tip (https://cgit.freedesktop.org/drm-tip) and kernel parameters drm.debug=0x1e log_buf_len=4M, and if the problem persists attach the full dmesg from boot. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.