[drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0xA, supported mask 0xB

[ajl7]

regrets, but I am experiencing this problem as well.

setup:
Dell XPS 13 9350 with the Dell D3100 dock running Ubuntu 16.04 (4.4.0-38-generic)

DisplayLink Ubuntu Software Version: 1.2.58

to reproduce:

- plug in d3100 dock with external monitor attached via displaylink
- note monitor is enabled as secondary
- close top on laptop
- expect: external monitor becomes primary.

observed:
display not visible.

dmesg output completely spammed with messages like:

[10380.071195] [drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0x1f3, supported mask 0x7400003f
[10380.071239] [drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0x40001f3, supported mask 0x7400003f


imo, after reading the referenced defect reports, it may be a little bit of a reach to say this is a bug in the upstream. the scenarios referenced are all specific to the nouveau driver.


workaround is to leave laptop display open, I guess.

[ajl7]

updates to xserver-common and xserver-xorg-core partially address this problem:

after installing these updates, you can finally make the external desktop monitor primary.
this means you can close the laptop if you want, and you will have a single display visible.

updates are:
xserver-common:amd64 (2:1.18.3-1ubuntu2.3, 2:1.18.4-0ubuntu0.1),
xserver-xorg-core:amd64 (2:1.18.3-1ubuntu2.3, 2:1.18.4-0ubuntu0.1)

see:
https://bugs.launchpad.net/ubuntu/+s...r/+bug/1586260

note that the dmesg spam remains unaffected:

the dmesg buffer is completely swamped with messages like:
[drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value...

[jb25]

Confirming same issue as well.

Workaround is to set laptop as primary display. not ideal

[MisterFlicker]

Workaround for myself is diverting these log messages away from syslog:

1) Create a new rsyslog config file, e.g.-

sudo vi /etc/rsyslog.d/30-displaylink.conf

2) Add the following to the new configuration file:

# Divert noisy drm spam away from syslog
:msg,contains,"drm_wait_vblank" /var/log/displaylink.err

# Uncomment the following to stop logging anything that matches the last rule.
& stop

3) Restart rsyslog daemon;
sudo service rsyslog restart

The spam messages will now be diverted to the new log file '/var/log/displaylink.err'.

Have a nice DOS.

[quantumnaut]

Thanks MisterFlicker for the workaround for the logs.

Until now, I have not been able to troubleshoot this due to my syslog being full. Several times per day some process will lock up my keyboard, mouse and video for about 10 seconds. Then I assume some process crashes and restarts. My screens go blank and then come back. I am then back to normal.

I am running a desktop, not a laptop on Ubuntu 16.04. FWIW, below is the info on my integrated graphics.

00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller])
Subsystem: ASRock Incorporation Motherboard [1849:0162]
Flags: bus master, fast devsel, latency 0, IRQ 29
Memory at f7800000 (64-bit, non-prefetchable) [size=4M]
Memory at e0000000 (64-bit, prefetchable) [size=256M]
I/O ports at f000 [size=64]
Expansion ROM at <unassigned> [disabled]
Capabilities: <access denied>
Kernel driver in use: i915
Kernel modules: i915

[micsnare]

is there any update on that?
I receive exactly the same error message as well......

[seshadribpl]

Thanks a lot, MisterFlicker !