|
|
Thread Tools | Search this Thread | Display Modes |
|
05-18-2016, 11:47 AM | #1 |
Senior Member
Join Date: Feb 2010
Posts: 386
|
[drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0xA, supported mask 0xB
Hi,
Some of you are experiencing these appearing in kernel logs a lot, probably drastically reducing the overall performance. Unfortunately, this looks like nothing specific to DisplayLink, but something that needs to be fixed in upstream as it's affecting general dual GPU setup: See for example: https://bugs.freedesktop.org/show_bug.cgi?id=92327 https://bugzilla.redhat.com/show_bug.cgi?id=1243432 If you experience this too, subscribe this thread. If you have a workaround, please share it with others. Thanks, Michal |
06-21-2016, 11:00 AM | #2 |
Junior Member
Join Date: Jun 2016
Posts: 1
|
I have this issue on a Dell XPS 13 9350 with the Dell D3100 dock running Ubuntu 16.04 (4.4.0-24-generic). Error in the syslog is slightly different:
[drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0x75, supported mask 0x7400003f [drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0x4000074, supported mask 0x7400003f This message is generated hundreds of times times per second and massively impacts performance when the displays are connected. This only happens when the primary display is set to one of the external displays. Keeping the laptop display as primary is a workable if annoying workaround. GPU info: lspci -vnn | grep VGA -A 12 00:02.0 VGA compatible controller [0300]: Intel Corporation Sky Lake Integrated Graphics [8086:1926] (rev 0a) (prog-if 00 [VGA controller]) DeviceName: Onboard IGD Subsystem: Dell Skylake Integrated Graphics [1028:0704] Flags: bus master, fast devsel, latency 0, IRQ 277 Memory at db000000 (64-bit, non-prefetchable) [size=16M] Memory at 90000000 (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_bpo Kernel modules: i915_bpo |
07-15-2016, 11:53 PM | #3 |
Junior Member
Join Date: Mar 2016
Posts: 14
|
Interesting, I can confirm this doesn't happen while my laptop display is turned on (although it doesn't have to be set as Primary).
Here's my GPU info, currently leave nvidia card off using Bumblebee: lspci -vnn | grep VGA -A 9 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:5140] Flags: bus master, fast devsel, latency 0, IRQ 27 Memory at f1000000 (64-bit, non-prefetchable) [size=4M] Memory at e0000000 (64-bit, prefetchable) [size=256M] I/O ports at 5000 [size=64] [virtual] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: i915 Kernel modules: i915 -- 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev ff) (prog-if ff) !!! Unknown header type 7f Kernel modules: nouveau |
08-25-2016, 07:12 AM | #4 |
Junior Member
Join Date: Sep 2015
Posts: 4
|
Dell Inspiron 5749. Toshiba dynadock. Ubuntu 16.04.1 LTS. Gnome flashback metacity. Displaylink driver v1.1.68.
4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux 00:02.0 VGA compatible controller [0300]: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) 3 Monitor configuration; 2x BenQ GL2760B, normal orientation (Left & Right) 1x Samsung B2440, left rotation (Center) 1x Laptop display (Disabled) Took a three day trip down the rabbit hole to get this display configuration working. I am now being held against my will in a large gated institution, where I have been given a comfortable padded cell. They tell me it's for my own protection. My cell mate likes to keep raw chicken under his bed. I like to draw Ubuntu symbols on the cell walls. I often fantasise about a persistent monitors.xml file, and what could have been, but that's only when nurse ratched isn't on duty. Ubuntu + >2 monitors = Fail. Getting these messages in syslog @ rate of about 2 log lines per second, if I do not move my mouse. If I move my mouse around on the displaylink monitor to my right, this jumps to around 20 of these log lines per second. If I move my mouse around on the displaylink monitor to my left, or the center monitor, the log lines continue to be generated at around 2 per second. [drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0x40000a3, supported mask 0x7400003f Aug 25 16:51:59 rnd30-pc kernel: [26031.341973] [drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0xa3, supported mask 0x7400003f Aug 25 16:51:59 rnd30-pc kernel: [26031.342294] [drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0xa3, supported mask 0x7400003f Aug 25 16:51:59 rnd30-pc kernel: [26031.342316] [drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0x40000a3, supported mask 0x7400003f I keep telling myself it's all just in my head, that display support can't possibly be this farcical in an aspiring mainstream distribution, that things will get better soon. Then my cell mate just starts laughing manically while stroking his...erm...better not mention that. It's time to get my meds. |
09-23-2016, 10:14 AM | #5 |
Junior Member
Join Date: Jun 2016
Posts: 8
|
Having the same issue
Log is full of that message
|
10-03-2016, 11:45 PM | #6 |
Junior Member
Join Date: Oct 2016
Posts: 2
|
same issue
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. |
10-08-2016, 08:07 PM | #7 |
Junior Member
Join Date: Oct 2016
Posts: 2
|
upstream partial fix
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... |
10-11-2016, 01:41 PM | #8 |
Junior Member
Join Date: Oct 2016
Posts: 6
|
Confirming same issue as well.
Workaround is to set laptop as primary display. not ideal |
10-17-2016, 04:19 AM | #9 |
Junior Member
Join Date: Sep 2015
Posts: 4
|
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. |
10-31-2016, 02:44 PM | #10 |
Junior Member
Join Date: Oct 2016
Posts: 2
|
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 |
Tags |
drm_wait_vblank |
|
|