Linux Wacom Tablet Project / Bugs / #311 Kernel panic, system freeze since kernel4.4 til 4.5rc6

Ping Cheng - 2016-03-11

The issue must be in kernel. So, X driver won't thelp. Did you update kernel driver from http://linuxwacom.sourceforge.net/wiki/index.php/Input-wacom?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Antonín Dach - 2016-03-11

Hi, my version of input-wacom

Name : input-wacom-dkms
Version : 0.30.0-1

xf86 version,

Name : xf86-input-wacom
Version : 0.31.0-1

hid/wacom.co.gz kernel module,

version: v2.00
srcversion: DE7C71BF8A5310E0B060C82

I will try downgrade this xf86 soon to see if it helps,
xf86-input-wacom 0.30.0-1
I did not update from the page site,

How am I supose to proceed in debuging?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ping Cheng - 2016-03-11

It's a kernel issue. Why do you want to downgrade xf86-input-wacom? Update input-wacom from the link I gave you should make a difference.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Antonín Dach - 2016-03-15

I have succesfully build input-wacom 0.32 and xf86 input 0.32, SO the system now no longers Kernel Panic, however my tablet doesn't work. No input is registered with xev and thus I can't draw with it. The error code -32 is still returned. :( should i create new thread?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ping Cheng - 2016-03-15

So, the updated driver did make a difference ;-). Please unplug the tablet. Reboot your system. Then plug the tablet in and post your "dmesg" here. I'll take a look.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Antonín Dach - 2016-03-15
  
  I did restart the computer, the module was loaded. The tablet doesn't work.
  Error -32 is still returned.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Antonín Dach - 2016-03-15
  
  out.txt
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ping Cheng - 2016-03-16

The error means driver can not switch the tablet to wacom mode. That could be caused by a malfuntion hardware or some corrupted command. Since your tablet worked on older kernels before, you can switch back to see if it still works on those kernels. That would tell us if it is now a hardware issue or not.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Antonín Dach - 2016-03-16
  
  It's not a hardware issue, the tablet worked on kernel 4.3 and that was not very long ago I updated.
  
  I just plugged it in my debian 8 machine and the tablet works plug and play.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ping Cheng - 2016-03-16

I don't have your tablet model. I have a Bamboo pen only though. It works on a kernel 4.5-rc1+, out of box.

Your following message made me wonder which driver your system is running:

" my version of input-wacom
Name : input-wacom-dkms
Version : 0.30.0-1

hid/wacom.co.gz kernel module,
version: v2.00"

Under the compiled input-wacom, can you try "sudo rmmod wacom; sudo insmod 3.17/wacom,ko" to see what happens?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Antonín Dach - 2016-03-16
  
  The system came with xf86-input-wacom 0.30.0-1 installed, then it got upgraded to 0.31 (that might be the point of breakage)
  
  Before 2015-10-05 I am 100% sure it was working
  
  [2015-10-05 14:22] [ALPM] upgraded xf86-input-wacom (0.30.0-1 -> 0.31.0-1)
  
  To be frank, I am not 100% sure if the tablet performed well before the kernel upgrade though. at this point input-wacom is 0.30 still and was not updated.
  
  Pretty sure tablet was, and as you said xf86-input-wacom doesn' matter at this point, so having version missmatch between those two shouldn't be a problem??
  
  [2016-01-13 15:42] [ALPM] installed linux44 (4.4.0-1)
  
  after kernel 4.4 the tablet doesn't work. and I have no idea what input-wacom version was at this point cause I didn't check.
  
  Now I am running xf86-input-wacom and input-wacom 0.32, it would help to know the difference between those two. Do I really need xf86-input-wacom?
  
  i did remove the wacom succesfuly "sudo rmmod wacom"
  
  but the second module is not found :( what "insmod: ERROR: could not load module 3.17/wacom.ko: No such file or directory"
  
  What should I do? Try uninstalling and downgrading to 0.30 ??
  
  I might check kernel 4.5 soon as I am currently involved in resolving horrible AMD ACPI kernel bug that makes me inpossible to use journalctl so I could only test if the pointer reacts on input.
  
  Last edit: Antonín Dach 2016-03-16
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ping Cheng - 2016-03-17

Antonín, we got a kernel panic report from a Fedora user for the same device on kernel 4.4.4. If you have time and know how to bisect, please provide a bisect result here. That would give us a hint on the issue.

Regarding to your questions above, if insmod can not find wacom.ko under 3.17, it means the driver was not built. So, you are not using the latest driver from input-wacom. But, that may not be the issue since I have built and tested the driver directly from kernel 4.4.4, it works with my "Wacom Bamboo Pen", which goes through the same code path as your device.

We have to see where your device fails to understand the issue.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Antonín Dach - 2016-03-17
  
  Ok I will try to Bisect and find the commits that breaks the driver for me.
  
  But should I do it on input-wacom and xf86 aswell? I am not sure if I even need the xorg input, would make it more efficient for me if I could uninstall it.
  
  I'll do my best
  
  EDIT: It's so frustrating! I see I make a difference if I compile 0.28.0 then the error -32 is no more and if i compile 0.30.0 I get the error -32 (neither of them works with my tablet in this kernel) and the module 3.17/wacom.ko is found only sometimes and sometimes is not? WHat the? Should I do sh autogen.sh and then sudo make? or just make, I always do sudo make install and I am not sure if I sudo make or just make.. gosh I can't find the working tags :(
  
  EDIT2: I am done for now, I see the after ./configure and make and sudo make install that something is changing with the wacom driver, however the 3.17/wacom.ko is not found no matter what I do, once it did I and I did the usuall. I need a break from this crazyness :D Should I find where the error -32 is occuring? the driver still doesnt work with any version I try.
  
  Last edit: Antonín Dach 2016-03-17
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ping Cheng - 2016-03-17

Don't worry about X driver or input-wacom at this moment. I know where error -32 occured. But, we don't why it happened. The issue is in kernel. So, let's focus on the kernel crash when you touch tablet issue first. You need to build and install a kernel 4.4 from a git repo to bisect it.

Take a break when you feel exhausted. But, we need the bisect result, eventually :-).

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ping Cheng - 2016-03-22

Hi Antonín,

I guess bisect is too much work for you. I have good news. Benjamin, Red Hat kernel developer, made a patch that could fix your issue. Can you test it for us? Thanks!

0001-HID-wacom-fix-Bamboo-ONE-oops.patch

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Antonín Dach - 2016-03-22
  
  Ok I will test it :) sorry about bisect I was somehow occupied with school stuff and compilation took me off my mind track. I will test the patch.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Antonín Dach - 2016-03-22
  
  Ok, I tell you what I did, I compiled kernel 45 with this patch it booted up and I have plugged the tablet in but the results was that cursor didn't move, I have build agian the input-wacom from repository and successfully insmod 3.17/wacom.ko.. The tablet still doesn't work :/ I can't tell you what kernel said cause my ACPI on kernel 4.5 is doing some crazy stuff. Should I try compile kernel 4.4 with this patch? I think It might tell me what is wrong in my log.. I don't know about the bisect cause it takes me 3h to compile a kernel and doing it multiple times is time consuming..
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ping Cheng - 2016-03-22

Thank you for your effort. Can you try the patch on 4.4? If it still doesn't work, please share your dmesg from both kernels.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Antonín Dach - 2016-03-23
  
  I did few dmesg on kernel 4.4.6, I named them after what I did, they should be helpful.
  Firstly i booted and do one dmesq, then I've plugged the tablet in and did another and then I compiled input-wacom and insmod it adn did two, one right after compilation and the second after replugging it to usb2 again. :) Is kernel 4.5 dmesg necessary? It's broken with ACPI messages (my other bug) so it's crap repeating to infinity. It might produce something after I remove the acpi debug flags so I might get to that but kernel 4.4.6 behaves the same and could be enought ?
  
  [ 109.503385] ACPI Error: No handler or method for GPE 0D, disabling event (20160108/evgpe-790) [ 109.503401] ACPI Error: No handler or method for GPE 0F, disabling event (20160108/evgpe-790) [ 109.503407] evgpe-0423 ev_gpe_detect : Read registers for GPE 10-17: Status=FF, Enable=FF, RunEnable=41, WakeEnable=00 [ 109.503429] ACPI Error: No handler or method for GPE 12, disabling event (20160108/evgpe-790) [ 109.503436] ACPI Error: No handler or method for GPE 13, disabling event (20160108/evgpe-790)
  
  Last edit: Antonín Dach 2016-03-23
  
  after_building_input-wacom.txt
  
  after_building_input-wacom_replug.txt
  
  after_pluging_to_usb2.txt
  
  before_pluging.txt
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ping Cheng - 2016-03-23

Those dmesg outputs are enough. No need to test 4.5. However, we don't know why your cursor still doesn't move. Benjamin's testing suite moves the cursor with that patch applied. Can you provide us with evemu records (https://www.archlinux.org/packages/community/x86_64/evemu/)? You can get an idea of evemu tool here: https://www.freedesktop.org/wiki/Evemu.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Antonín Dach - 2016-03-23
  
  HI, I did evemu record.
  
  I noticed, MAYBE very important that the Bamboo pen is there TWICE? huh is that ok?
  
  Anyway notice I tried to record the pen on event14 and I GOT kernel panic! I get it If and only if emevu record event14, if I record event13 it's OK and I see that it has content and some movement is recorded, no cursor movement. :D
  
  I have no idea what is going on.? Could it be that kernel comes with wacom driver and then the input-wacom kicks in? I thing I am going crazy with this tablet. Why would it freeze only when I try to record evemu-record :D
  
  PS: I included the patched driver file if you would Like to check if i am not compelete idiot :D
  
  bamboo_one_s_pen13_evemu_describe.txt
  
  bamboo_one_s_pen14_evemu_describe.txt
  
  event13.events
  
  event14.events
  
  wacom_wac.c
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ping Cheng - 2016-03-24

Antonín, your wacom_wac.c is correct. Thank you for your effort.

It's ok to have two logical ports (event#). But, one of them (most likely event14) should do nothing since it is just a dumb port.

The same patch has made Fedora user's Wacom One tablet work properly. We want to figure out what's stopping your cursor movement.

Since we had issue to launch the right wacom.ko on your system, I want to make sure we are running the newly built driver. Can you update wacom.h by #define DRIVER_VERSION "v2.00-k4.4", then rebuild, install the driver and post "modinfo wacom | grep version".

Please also share the output of "xinput list" and the /var/log/Xorg.0.log file on your system, while tablet is plugged in and wacom.ko is loaded.

Last edit: Ping Cheng 2016-03-24

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Antonín Dach - 2016-03-24
  
  Hi, I compiled again the latest input_wacom and loaded module 3.17/wacom.ko (I am able to load it only if I make install it.)
  
  I smell problem now, the xinput have no Wacom entry :D how is that possible? And should I not care about the error -32 that is still returned in journal ?
  
  Xorg0log_whilelastestinput_wacom.txt
  
  xinput_list_whilelatestinput_wacom.txt
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Antonín Dach - 2016-03-24
  
  Yes, I figured it out, I had patched the kernel driver for wacom, so when I was confused I isntalled and compiled the driver from git "input_wacom" and that must override the patched driver since I was confused and didn't know that patching the input_wacom was necessary.. So I uninstall input_wacom 0.32 and xf86_input_wacom a heureka the tablet now works :)) May I aks when you will ship this fix into the kernel mainline OR the driver itself in git? input_wacom?
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ping Cheng - 2016-03-24

Thank you Antonín! We'll get the fix in as soon as we can.

Can you test kernel 4.5, without the patch, to see if your device works or not? We need to see if the patch is only needed for 4.4 or not.

Last edit: Ping Cheng 2016-03-24

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Kernel panic, system freeze since kernel4.4 til 4.5rc6

Searches

Help

#311 Kernel panic, system freeze since kernel4.4 til 4.5rc6

Discussion