If I turn off Cintiq 22HD, xorg hangs for about 20 seconds.
After xorg becomes responsive again, ~59MB of two error messages fill /var/log/Xorg.0.log.
[ 46.197] (EE) Wacom Cintiq 22HD Pad pad: Error reading wacom device : No such device
....
[ 67.525] (EE) Wacom Cintiq 22HD Pen eraser: Error reading wacom device : No such device
Thus, if I turn Cintiq on and off several times, /var/log/Xorg.0.log can occupy ~500MB.
While tail -f /var/log/Xorg.0.log is running, Xorg doesn't hang, but I still see those error messages. I don't know why.
I surmise Xorg hung for ~20 seconds because it had to write ~59MB of error messages at once.
dev-libs/libwacom-0.24:0
x11-drivers/xf86-input-wacom-0.34.0:0
linux kernel 4.9.16-gentoo
"Device Drivers -> HID support -> Special HID drivers -> Wacom Intuos/Graphire tablet support (USB)" was compiled as a kernel module.
Last edit: crocket 2017-06-23
The error message isn't the root cause. When we disconnect/turn off a device, it would be inaccessible by the driver. That's what the messages are telling us. But, you are right. Driver should not overwhelm the log with duplicated messages. We'll take a look and figure out what's going on.
I tested a few models. I got about 10 lines of "(EE) Wacom Cintiq 22HD" before "removing device Wacom Cintiq 22HD" showed up, which is less than 10k. How many lines of "(EE)" do you get? Maybe you have a faster system?
Before turning off Cintiq 22HD, the size of /var/log/Xorg.0.log was ~48KB.
After turning it off, its size became ~58MB.
655,792 errors caused by turning it off once.
The error messages span 20~22 seconds in /var/log/Xorg.0.log. Xorg hangs for 20~22 seconds.
It is obvious that Xorg hangs while error messages are emitted in a huge burst.
CPU : AMD Athlon(tm) II X4 640
GPU : AMD Radeon HD6450
RAM : 32GB
Last edit: crocket 2017-06-27
That's a lot of output. Are those EE all from Wacom Cintiq? Do you have another Linux system to test with?
According to the output, two errors account for the vast majority of lines. In the next comment, I'll report the result of testing Cintiq 22HD with a laptop.
If you add up the counts in the output above, you get 655792 errors.
Last edit: crocket 2017-06-30
My laptop's specifications:
GPU : Radeon R4
CPU : AMD A6-7310 APU with AMD Radeon R4 Graphics
RAM : 4GB
OS : Manjaro Linux
Linux Kernel : 4.9.33-1-MANJARO
libwacom 0.24 is installed, but xf86-input-wacom is not installed on my laptop.
When I plugged Cintiq 22HD's USB cable in my laptop without connecting the display to the laptop and turned Cintiq 22HD on and off, I got the following output in /var/log/Xorg.0.log
Without xf86-input-wacom, there was no error. There was no freeze.
After installing xf86-input-wacom 0.34.2 on my laptop, the issue was reproduced for a shorter duration than 20 seconds.
Last edit: crocket 2017-06-30
Werid! I want to make sure we are not dealing with a hardware issue. When the tablet is connected and Wacom driver is installed, does the tablet work? That is, can you move the cursor by your Wacom pen?
Yes, it's weird.
When the tablet connected and the driver installed, I can move the mouse cursor with my wacom pen.
If I couldn't draw properly, the issue would have been differently reported.
Today, my laptop froze for ~55 seconds when I turned off Cintiq 22HD. There were more of the same errors in Xorg.0.log
To be absolutely sure that it's not a hardware problem, I'd have to have access to another Cintiq 22HD device.
Last edit: crocket 2017-07-01
It helps to troubleshoot the issue if we have the same driver versions. Is it possible to update your drivers, wacom.ko from input-wacom and wacom_drv.so from xf86-input-wacom, to the lastest? If you can not update the X driver, updating the kernel driver itself may help...
How do I obtain the latest of input-wacom and xf86-input-wacom?
Links to installation instructions can be found here:
http://linuxwacom.sourceforge.net/wiki/index.php/Downloads
On Fri, Jul 7, 2017 at 4:40 AM, crocket crochery@users.sf.net wrote:
Should I compile the latest commit or the latest stable version?
For troubleshooting the latest commit will be probably the most helpful here.
On Fri, Jul 7, 2017 at 6:10 PM, crocket crochery@users.sf.net wrote:
Related
Bugs:
#337Today, I compiled and installed the latest commits of input-wacom and xf86-input-wacom.
The issue is still reproduced.
Please check the version of wacom.ko and wacom_drv.so that are running on your system. "modinfo wacom | grep version" should give you wacom.ko's; check your Xorg.0.log to see the X driver version. Sometime the newly built driver won't get loaded...
..
..
-9999 means xf86-input-wacom was built from git.
Last edit: crocket 2017-07-13
OK, you are running with the latest drivers. I have two more questions.
I revisited your previous messages. I see you didn't have issues when xf86-input-wacom was not instslled. At that time, did your pen work?
The other question is: is the Cintiq 22HD a new device? By new I mean if it has been run on other platforms or version of Linux before you try it on your system?
The pen works without xf86-input-wacom. But, without xf86-input-wacom, I can't feed the calibration data into Cintiq 22HD via xsetweacom. I set various tablet parameters via a shell script that invokes a list of xsetwacom commands.
Cintiq 22HD had the same issue on ArchLinux, too. By the way, Manjaro Linux is a derivative of ArchLinux. The choice of the desktop environment(XFCE, GNOME, XMonad, ...) doesn't change the outcome.
From your log file, I see your device is driven by x86-input-lininput. So, you can set parameters through "xinput set-prop". Meanwhile, Peter Hutterer, our input device driver expert in Xorg is working on a patch to fix the issue in x86-input-wacom. He may need your help to test the patch when he is ready.
Please apply the attached patch and test it. Let us know your result so we can merge it upstream. I emailed the patch to you at crochery@users.sf.net. It failed with "Address not found"...
It turns out that
"Only SourceForge can send to crochery@users.sourceforge.net. This includes the Send Message web form on your profile page."
I tested the patch. It worked fantastically.
Here's the result.
Last edit: crocket 2017-07-22
That's great! Can we use your name as Tested-by? If yes, I need your name and email. Something: Tested-by: first, last email@address.com
Tested-by: crocket crockabiscuit@gmail.com