Kernel Oops - unable to handle kernel NULL pointer dereference; RIP is at xpad_probe+0x33d/0x9d0

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1514505

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

apport-collect doesn't work: "dpkg-query: no packages found matching linux"

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.3 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-wily/

Gonna do that!

Issue doesn't exist on a 14.04 system.
uname -a: Linux mango 3.13.0-67-generic #110-Ubuntu SMP Fri Oct 23 13:24:41 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/diff/drivers/input/joystick/xpad.c?id=v3.13&id2=v3.19

We have a lot of changes for xpad between the 14.04 and 15.04 system!

linux-headers-4.3.0-040300-generic_4.3.0-040300.201511020949_amd64.deb

Is this the right kernel?

Also exists with the upstream kernel. Wasn't able to boot into graphical interface but in workspace 1 (ctrl+alt+F1) I got the same error after plugging the controller in. I also confirmed with uname -a that I was running 4.3

Jonathan, please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1514505

As I already wrote further up https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514505/comments/6

I know it would be useful but it's not possible!

Jonathan, then boot with an alternative environment instead. For example, http://cdimage.ubuntu.com/daily-live/current/ .

If I boot a live system and then plug the controller in, the system freezes/crashes. Switching onto workspace 1 also isn't also possible.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

hmm... now it somehow worked on my main system...

But only as long as I haven't plugged the controller in.

After plugging the controller in, the apport-collect doesn't work. It's already running for 5+ minutes now... I'm gonna let it run/collect infos and see if it is finished in 1h.

What could be causing apport-collect to not work after plugging the controller in could be that lsusb gets broken. (If I run lsusb in a terminal, lsusb doesn't output anything and also doesn't stop running and it isn't possible to kill lsusb.)

Jonathan, the next step is to fully commit bisect from kernel 3.13 to 3.19 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Oops.. just realized that what I wrote in #8 and #9 is wrong. Xpad doesn't crash because it doesn't even know that the new device is a Xbox controller.

The following commit adds my controller USB Id as a controller detectable by Xpad: https://github.com/torvalds/linux/commit/39a7a88872df98f0c3c50fe278fd1a1f597afd95

So we were running in the wrong direction...

With every kernel that includes commit 39a7a8 the controller will crash Xpad when plugging it in. "Older" kernels will just not detect the controller as a controller and Xpad just "ignores" it.

Or in other words:
My controller gets only detected since commit 39a7a8 and causes Xpad to crash. "Older" kernels just don't "see" the controller as such.

https://github.com/torvalds/linux/commit/39a7a88872df98f0c3c50fe278fd1a1f597afd95
It's included in the "newer" ubuntu kernels as well as in the upstream (I don't know how to check in which "pre-built" kernels it's included)

Jonathan, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate venue (TO Pavel Rojtberg, and Dmitry Torokhov CC linux-input))?

Please provide a direct URL to your newly made report when it becomes available so that it may be tracked.

Thank you for your understanding.

I had issues getting my message on the mailing list...

https://<email address hidden>/msg20607.html

Somehow only the reply of Dmitry got on the list.

Jonathan, as noted in https://wiki.ubuntu.com/Bugs/Upstream/kernel that link isn't the official archives of linux-input. Instead you would want to review http://vger.kernel.org/vger-lists.html .

http://www.spinics.net/lists/linux-input/msg42336.html

Jonathan, to clarify https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514505/comments/39 which newer Ubuntu kernel is this available in?

None... Dimitry said he had opened a pull request for rc3 (No idea what that exactly stands for)

The original issue has been fixed already.

Now it's just that the Input is static but it has nothing to do with the original issue so I'm gonna close this.

Jonathan:
>"The original issue has been fixed already."

Where precisely, in the Ubuntu kernel from Vivid?

https://github.com/torvalds/linux/commit/39a7a88872df98f0c3c50fe278fd1a1f597afd95

This commit fixes the crashing. It isn't included anywhere yet (AFAIK) so I'm running my own custom build.

But:
The Input isn't correct yet but I don't think this would belong to this bug report. https://<email address hidden>/msg20758.html