Comment # 11 on bug 898395 from Bit Juggler

Sorry, i'm not very familiar with bug reporting and the like. Nevertheless i
really would like to do as much as i can to help solving this bug. May be you
can give me some assistance:

At bugzilla.kernel.org it says "This is the Kernel Tracker system (based on
Bugzilla) for posting bugs against the mainline Linux kernels (not distribution
kernels)." How can i prove, that the bug reported by me is NOT distribution
specific? Is there any thing special (like referencing this bug here) i have to
do?

In the meantime i used YAST to install "vmlinuz-3.17.0-1.gc467423-debug".

"ls -a /boot" returns
lrwxrwxrwx  1 root root 31 13. Okt 16:01 vmlinuz ->
vmlinuz-3.17.0-1.gc467423-debug

But after reboot "uname -a" returns
Linux XXXXX 3.16.4-1.g7a8842b-default #1 SMP Mon Oct 6 07:18:42 UTC 2014
(7a8842b) x86_64 x86_64 x86_64 GNU/Linux

Why shows "uname" a kernel version 3.16.4 while the symlink in /boot points to
a kernel version 3.17.0 ?

When i plug in the USB2.0 device dmesg still returns an error:

[   27.188135] usb 1-4: new full-speed USB device number 4 using xhci_hcd
[   27.300150] usb 1-4: device descriptor read/64, error -71
[   27.404118] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for
slot 3.
[   27.404121] usb 1-4: hub failed to enable device, error -22
[   27.516105] usb 1-4: new full-speed USB device number 5 using xhci_hcd
[   27.628152] usb 1-4: device descriptor read/64, error -71
[   27.732118] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for
slot 4.
[   27.732121] usb 1-4: hub failed to enable device, error -22
[   28.028098] usb 1-4: new full-speed USB device number 7 using xhci_hcd
[   28.160291] usb 1-4: New USB device found, idVendor=0400, idProduct=080a
[   28.160293] usb 1-4: New USB device strings: Mfr=0, Product=0,
SerialNumber=0
[   28.165626] usbcore: registered new interface driver btusb


So here i probably need some guidance too, to provide the information you need.