Kernel has troule recognizing Corsair Harpoon RGB mouse

Bug #1740438 reported by TuxRocks
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I recently started using a Corsair Harpoon RGB mouse and the kernel is having trouble recognizing it. About half of the time when I boot, I see messages like this:

[ 7.132078] usb 1-14: unable to read config index 0 descriptor/all
[ 7.132081] usb 1-14: can't read configurations, error -110

Occasionally they repeat after a few seconds. The mouse will not function until I unplug the mouse and plug it back in. So far, one unplug and plug has fixed it every time. I am running Xubuntu 17.10 on 4.13.0-21.24-generic 4.13.13. I have attached the extra debug information that is generated by ubuntu-bug linux. I can provide additional information, if needed, and I am available to troubleshoot this issue.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-21-generic 4.13.0-21.24
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: ben 937 F.... pulseaudio
 /dev/snd/controlC0: ben 937 F.... pulseaudio
 /dev/snd/controlC1: ben 937 F.... pulseaudio
CurrentDesktop: XFCE
Date: Thu Dec 28 14:13:19 2017
InstallationDate: Installed on 2017-12-20 (8 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
IwConfig:
 enp0s31f6 no wireless extensions.

 lo no wireless extensions.
MachineType: MSI MS-7A59
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed root=UUID=ce80946f-0157-40fa-8410-c866a1e5c481 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-21-generic N/A
 linux-backports-modules-4.13.0-21-generic N/A
 linux-firmware 1.169.1
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/20/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.80
dmi.board.asset.tag: Default string
dmi.board.name: Z270 SLI (MS-7A59)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd11/20/2017:svnMSI:pnMS-7A59:pvr1.0:rvnMSI:rnZ270SLI(MS-7A59):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: Default string
dmi.product.name: MS-7A59
dmi.product.version: 1.0
dmi.sys.vendor: MSI

Revision history for this message
TuxRocks (tuxrocks) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 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.15-rc6/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
TuxRocks (tuxrocks) wrote :
Download full text (127.6 KiB)

This issue has been present since I installed a fresh copy of Xubuntu 17.10 about 3 weeks ago.

I believe that Xubuntu came with 4.13.0-16 and I upgraded to 4.13.0-21.

I installed the latest upstream kernel (4.15-rc6) and I am still experiencing the issue. Out of 15 boots, 3 were bad and 3 took longer than normal to recognize the mouse. I have included the dmesg outputs from both scenarios below.

Dmesg output when mouse doesn't work:
[ 0.000000] Linux version 4.15.0-041500rc6-generic (kernel@kathleen) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)) #201712312330 SMP Sun Dec 31 23:31:15 UTC 2017
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-041500rc6-generic root=UUID=ce80946f-0157-40fa-8410-c866a1e5c481 ro quiet splash vt.handoff=7
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
[ 0.000000] x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64
[ 0.000000] x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64
[ 0.000000] x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000059000-0x000000000009efff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000086120fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000086121000-0x0000000086121fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x0000000086122000-0x0000000086122fff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000086123000-0x000000008e6e9fff] usable
[ 0.000000] BIOS-e820: [mem 0x000000008e6ea000-0x000000008eb71fff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000008eb72000-0x000000008ec18fff] usable
[ 0.000000] BIOS-e820: [mem 0x000000008ec19000-0x000000008efc0fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x000000008efc1000-0x000000008fb42fff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000008fb43000-0x000000008fbfefff] type 20
[ 0.000000] BIOS-e820: [mem 0x000000008fbff000-0x000000008fbfffff] usable
[ 0.000000] BIOS-e820: [mem 0x000000008fc00000-0x000000008fffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fe...

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Revision history for this message
TuxRocks (tuxrocks) wrote :
Download full text (65.9 KiB)

kaihengfeng, it seems to happen a little less often with the linked kernel, but I'm still experiencing the error. I have copied my dmesg output below.

[ 0.000000] random: get_random_bytes called from start_kernel+0x42/0x4e1 with crng_init=0
[ 0.000000] Linux version 4.13.0-22-generic (root@Precision-3520) (gcc version 7.2.0 (Ubuntu 7.2.0-18ubuntu2)) #25~lp1740438 SMP Wed Jan 3 12:06:33 CST 2018 (Ubuntu 4.13.0-22.25~lp1740438-generic 4.13.13)
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.13.0-22-generic root=UUID=ce80946f-0157-40fa-8410-c866a1e5c481 ro quiet splash vt.handoff=7
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
[ 0.000000] x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64
[ 0.000000] x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64
[ 0.000000] x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000059000-0x000000000009efff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000086120fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000086121000-0x0000000086121fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x0000000086122000-0x0000000086122fff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000086123000-0x000000008e6e9fff] usable
[ 0.000000] BIOS-e820: [mem 0x000000008e6ea000-0x000000008eb71fff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000008eb72000-0x000000008ec18fff] usable
[ 0.000000] BIOS-e820: [mem 0x000000008ec19000-0x000000008efc0fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x000000008efc1000-0x000000008fb42fff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000008fb43000-0x000000008fbfefff] type 20
[ 0.000000] BIOS-e820: [mem 0x000000008fbff000-0x000000008fbfffff] usable
[ 0.000000] BIOS-e820: [mem 0x000000008fc00000-0x000000008fffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000046...

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Revision history for this message
TuxRocks (tuxrocks) wrote :

I tested the above kernel over 15 reboots and the mouse activated successfully every time. Great work! You're a legend. Let me know if you need any additional information.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Before sending the patch to upstream, can you try [1] again? Thanks!

[1] http://people.canonical.com/~khfeng/lp1740438-3/

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.