This bug was fixed in the package linux - 4.4.0-98.121
---
linux (4.4.0-98.121) xenial; urgency=low
* linux: 4.4.0-98.121 -proposed tracker (LP: #1722299)
* Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller
(LP: #1720359)
- scsi: hpsa: limit transfer
Since I no longer run Xenial, I can't directly verify the fix on that
distribution, so I'm not changing the tags. However, I'm confident the
fix will work there as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
** Changed in: linux (Ubuntu Xenial)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1678477
Title:
Kernel has troule recognizing Corsair Strafe RGB ke
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1678477
Title:
Kernel has troule recognizing Corsair Str
This bug was fixed in the package linux - 4.10.0-37.41
---
linux (4.10.0-37.41) zesty; urgency=low
* CVE-2017-1000255
- SAUCE: powerpc/64s: Use emergency stack for kernel TM Bad Thing program
checks
- SAUCE: powerpc/tm: Fix illegal TM state in signal handler
linux (4.
This bug was fixed in the package linux - 4.10.0-37.41
---
linux (4.10.0-37.41) zesty; urgency=low
* CVE-2017-1000255
- SAUCE: powerpc/64s: Use emergency stack for kernel TM Bad Thing program
checks
- SAUCE: powerpc/tm: Fix illegal TM state in signal handler
linux (4.
I am on 17.04 - I've just installed the proposed kernel (4.10.36) and
verified that it does indeed solve my problem. My keyboard works through
multiple reboots and "re-pluggings" as described above.
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1678477
Title:
Kernel has troule recognizing Corsair Strafe RGB keyb
** Changed in: linux (Ubuntu Zesty)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1678477
Title:
Kernel has troule recognizing Corsair Strafe RGB key
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1678477
Title:
Kernel has troule recognizing Corsair Stra
@Piotr,
File a new bug, thanks!
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1678477
Title:
Ke
I'm using a slightly different variant of this keyboard - Corsair Strafe
(without RGB; product ID is 1b15). I had more or less the same problem
(error -110). I tried your solution (USB_QUIRK_DELAY_INIT) and it seems
to work every time. I did a quick test - previously keyboard worked 5
out of 10 reb
https://lkml.org/lkml/2017/8/15/817
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1678477
Title:
Kernel has troule recognizing Corsair Strafe RGB keyboard
Status in linux package in Ub
Now we can confirm that USB_QUIRK_DELAY_INIT along can workaround this
issue, I'll send a patch to Linux upstream.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1678477
Title:
Kernel h
The "devicequalifier" kernel doesn't appear to work. It presents a
similar error either on boot or when hot-plugging the keyboard:
[ 37.680914] usb 3-3: new full-speed USB device number 5 using xhci_hcd
[ 48.097499] usb 3-3: New USB device found, idVendor=1b1c, idProduct=1b20
[ 48.097505] us
The "delayinit" kernel seems to work! The keyboard is usable when the
computer first boots, and every time I unplug and plug it back in. I did
that while following the output of dmesg -w and got the following:
[ 80.205969] usb 3-3: new full-speed USB device number 5 using xhci_hcd
[ 81.468240]
Try these two:
http://people.canonical.com/~khfeng/lp1678477-dealyinit/
http://people.canonical.com/~khfeng/lp1678477-devicequalifier/
Basically, the one that worked has three quirks applied:
diff --git a/drivers/usb/core/quirks.c b/drivers/usb/core/quirks.c
index 3116edfcdc18..ff3c70fd919e 10064
With the kernels from
http://people.canonical.com/~khfeng/lp1678477-nolpm/ , the problem seems
to have returned. I got the following error on boot:
[1.273005] usb 3-9: new full-speed USB device number 3 using xhci_hcd
[ 11.740700] usb 3-9: string descriptor 0 read error: -110
[ 11.740733]
The endpoint issue will probably need another quirk in usbhid, like this
commit:
commit 282bf1fe6dca4b768d6bedc14aea1b82c36241c1
Author: Trent Lloyd
Date: Thu Jul 9 13:38:50 2015 +0800
HID: usbhid: quirks for Corsair RGB keyboard & mice (K70R, K95RGB,
M65RGB, K70RGB, K65RGB)
But let's dea
I added three quirks for the keyboard. Thanks to comment #13, I guess
the keyboard doesn't like LPM.
Let's try if USB_QUIRK_NO_LPM alone can make the keyboard work:
http://people.canonical.com/~khfeng/lp1678477-nolpm/
--
You received this bug notification because you are a member of Kernel
Packa
I've also installed the linked kernel today, and verified it works for
me as well! The keyboard was detected correctly every time through
multiple unpluggings and reboots, with output similar to what Frits
pasted above. I too always get the "couldn't find an interrupt endpoint"
message, but other t
Thanks @Kai-Heng Feng for your help. I have installed your kernel and it
does seem to work. The boot does not delay for 30 or more seconds
anymore, and the keyboard is usable immediately after boot. It still
nags a bit:
[2.249880] usb 3-1: New USB device found, idVendor=1b1c, idProduct=1b20
[
I can also confirm that I've never experienced the problem on Windows or
on the GRUB menu, both with the keyboard plugged into a single USB 3.0
and into 2 USB 2.0 ports.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
Please try kernel here:
http://people.canonical.com/~khfeng/lp1678477-corequirks/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1678477
Title:
Kernel has troule recognizing Corsair Stra
@Kai-Heng Feng,
i had this keyb for more than one year, and in windows I never had a problem
like this. I often switch OS rebooting the whole machine, and no problem
occures even in UEFI and/or GRUB menu at boot...
Problem occures only in Ubuntu after kernel module loading.
I started using an ex
@Luca,
Does the issue happen on Windows, if there's no auxiliary power?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1678477
Title:
Kernel has troule recognizing Corsair Strafe RGB ke
I'm using the keyboard using Ubuntu 17.04 stock kernel with an external,
independent powered, usb 2.0. It has a 3.0 Ampere power supply, not so big for
these days, but powerful enough to avoid power problems for this keyboard.
I'm using it for a while, several reboots and power-cycles, and I have
I upgraded to Ubuntu 17.04 a couple of weeks ago, and the problem
persisted under its version of kernel 4.10.
I just installed all the four packages in the link above, and booted
into the new Kernel on Ubuntu 17.04. The problem still persists. This is
the output of 'dmesg | grep "usb 3-3"' shortly
Please try this kernel:
http://people.canonical.com/~khfeng/lp1678477/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1678477
Title:
Kernel has troule recognizing Corsair Strafe RGB key
Same problem for me using Ubuntu Zesty (17.04)
I noticed two different types of error:
The first one has error code -71, and I don't know what does it means:
Jul 15 10:15:17 achille kernel: [ 202.060450] usb 3-14: new full-speed USB
device number 14 using xhci_hcd
Jul 15 10:15:18 achille kernel:
For me, whether the keyboard will work or not seems random: sometimes it
works right away, sometimes it works after replugging it once, sometimes
it takes multiple attempts. The error messages are the same ones you
posted.
--
You received this bug notification because you are a member of Kernel
P
I can confirm the bug (also with it plugged into 2 USB 3.0 ports btw).
Interestingly I can get it recognised by unplugging it and then
replugging it in at the log on screen:
$ dmesg | grep 'usb 3-6'
[1.679455] usb 3-6: new full-speed USB device number 4 using xhci_hcd
[6.871136] usb 3-6:
s/"Complete"/"Confirmed"/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1678477
Title:
Kernel has troule recognizing Corsair Strafe RGB keyboard
Status in linux package in Ubuntu:
Co
I tested it a few days ago but forgot to mark it as "Complete", sorry
about that. To further add information to my previous comment here, the
bug I described occurs both when the keyboard is plugged into a USB 3.0
port and when it's plugged into 2 USB 2.0 ports.
** Changed in: linux (Ubuntu)
Another possibly useful bit of information: I have the keyboard
connected to a USB 3.0 port - this model requires either a USB 3.0 port
or 2 USB 2.0 ports, because it draws more power than a USB 2.0 port
provides.
--
You received this bug notification because you are a member of Kernel
Packages,
Tested with 4.11.rc5, and still found this issue. Took me three tries to
get the keyboard to work, with the same messages and all the same config
options as above.
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which i
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 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 t
39 matches
Mail list logo