Hi, i got an info that my issue was caused by this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=217491487c43892318c18b6dcafe33b6353efd40 Patch is in progress... Regards Frank Am 4. September 2018 13:16:12 MESZ schrieb Frank Wunderlich <FrankWu@xxxxxx>: >Hi, thank you for quick answer. >i will try it, but afaik git bisect resets full git tree to the commit, >right? >i need to do some adjustments to get system booting (config,swap mmc in >dts). > > >is there another way to show more debug-messages? > >i have a working 4.16-tree, maybe i can merge newer versions (go >forward from it instead of backwards). > >regards frank > >Gesendet: Dienstag, 04. September 2018 um 07:26 Uhr >Von: "Greg KH" <gregkh@xxxxxxxxxxxxxxxxxxx> >An: "Frank Wunderlich" <FrankWu@xxxxxx> >Cc: linux-usb@xxxxxxxxxxxxxxx >Betreff: Re: Fw: keyboard-problem on bpi-r2 since 4.17 >On Tue, Sep 04, 2018 at 06:39:20AM +0200, Frank Wunderlich wrote: >> >> >> >> Hi, >> >> i have problems with usb-keyboard on bananapi-r2 since 4.17. same >keyboard works till 4.16. >> In 4.19-rc1 same issue occours. Keyboard is recognized and on >keypress it is disconnected >> and connected again without anything written to console. >> >> dmesg (printk-debuglevel=8) looks like this: >> >> [ 77.292068] usb 1-1: USB disconnect, device number 2 >> [ 77.292068] usb 1-1: USB disconnect, device number 2 >> [ 77.472554] evbug: Disconnected device: input0 >> [ 77.472554] evbug: Disconnected device: input0 >> [ 77.632390] evbug: Disconnected device: input1 >> [ 77.632390] evbug: Disconnected device: input1 >> [ 77.773255] evbug: Disconnected device: input2 >> [ 77.773255] evbug: Disconnected device: input2 >> [ 78.342590] usb 1-1: new low-speed USB device number 3 using >xhci-mtk >> [ 78.342590] usb 1-1: new low-speed USB device number 3 using >xhci-mtk >> [ 78.545576] input: USB USB Keykoard as >> >/devices/platform/1a1c0000.usb/usb1/1-1/1-1:1.0/0003:1C4F:0002.0003/input/input4 >> [ 78.545576] input: USB USB Keykoard as >> >/devices/platform/1a1c0000.usb/usb1/1-1/1-1:1.0/0003:1C4F:0002.0003/input/input4 >> [ 78.627589] evbug: Connected device: input4 (USB USB Keykoard at >> usb-1a1c0000.usb-1/input0) >> [ 78.636266] hid-generic 0003:1C4F:0002.0003: input,hidraw0: USB HID >> v1.10 Keyboard [USB USB Keykoard] on usb-1a1c0000.usb-1/input0 >> [ 78.627589] evbug: Connected device: input4 (USB USB Keykoard at >> usb-1a1c0000.usb-1/input0) >> [ 78.655044] input: USB USB Keykoard Consumer Control as >> >/devices/platform/1a1c0000.usb/usb1/1-1/1-1:1.1/0003:1C4F:0002.0004/input/input5 >> [ 78.636266] hid-generic 0003:1C4F:0002.0003: input,hidraw0: USB HID >> v1.10 Keyboard [USB USB Keykoard] on usb-1a1c0000.usb-1/input0 >> [ 78.655044] input: USB USB Keykoard Consumer Control as >> >/devices/platform/1a1c0000.usb/usb1/1-1/1-1:1.1/0003:1C4F:0002.0004/input/input5 >> [ 78.734340] evbug: Connected device: input5 (USB USB Keykoard >> Consumer Control at usb-1a1c0000.usb-1/input1) >> [ 78.746118] input: USB USB Keykoard System Control as >> >/devices/platform/1a1c0000.usb/usb1/1-1/1-1:1.1/0003:1C4F:0002.0004/input/input6 >> [ 78.734340] e[ 78.760069] evbug: Connected device: input6 (USB USB >> Keykoard System Control at usb-1a1c0000.usb-1/input1) >> vbug: Connected [ 78.770893] hid-generic 0003:1C4F:0002.0004: >> input,hidraw1: USB HID v1.10 Device [USB USB Keykoard] on >> usb-1a1c0000.usb-1/inpu >> t1 >> device: input5 (USB USB Keykoard Consumer Control at >> usb-1a1c0000.usb-1/input1) >> [ 78.746118] input: USB USB Keykoard System Control as >> >/devices/platform/1a1c0000.usb/usb1/1-1/1-1:1.1/0003:1C4F:0002.0004/input/input6 >> [ 78.760069] evbug: Connected device: input6 (USB USB Keykoard System >> Control at usb-1a1c0000.usb-1/input1) >> [ 78.770893] hid-generic 0003:1C4F:0002.0004: input,hidraw1: USB HID >> v1.10 Device [USB USB Keykoard] on usb-1a1c0000.usb-1/input1 >> >> can i debug this further? >> >> i see that mtk_xhci-driver was rewritten to use new api >> >> >https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/usb/host/xhci-mtk.c?h=v4.17-rc1&id=6ae9f5062aa6f5a301c16715c601c05bc9aa450e >> >> maybe this is the reason, but i don't know how to debug it. i tried >> disabling acpi and apic via cmdline to exclude anything acpi-related. >> >> maybe you have an idea... > >Can you use 'git bisect' to track down the offending commit? > >thanks, > >greg k-h Mit freundlichen Grüßen Frank Wunderlich
