[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729618
> On 7 Nov 2017, at 9:33 PM, Ivan Chernyshev <1729...@bugs.launchpad.net> wrote:
>
> Аt the moment i have:
>
> [ 16.365650] usb 4-1: new full-speed USB device number 3 using ohci-pci
> [ 16.538098] usb 4-1: string descriptor 0 read error: -22
> [ 16.538109] usb 4-1: New USB device found,
Аt the moment i have:
[ 16.365650] usb 4-1: new full-speed USB device number 3 using ohci-pci
[ 16.538098] usb 4-1: string descriptor 0 read error: -22
[ 16.538109] usb 4-1: New USB device found, idVendor=0cf3, idProduct=3004
[ 16.538113] usb 4-1: New USB device strings: Mfr=1, Product=2,
> On 6 Nov 2017, at 5:34 PM, Ivan Chernyshev <1729...@bugs.launchpad.net> wrote:
>
> Yes. The USB device still works correctly. With Windows and with
> elementary.
We should lower its log level so people won’t panic about this message.
>
> В Понедельник, 6 ноя. 2017 в 4:44 , Kai-Heng Feng
>
Yes. The USB device still works correctly. With Windows and with
elementary.
В Понедельник, 6 ноя. 2017 в 4:44 , Kai-Heng Feng
написал:
> IIUC the USB device still works correctly, right?
--
You received this bug notification because you are a member of Ubuntu
> On 4 Nov 2017, at 7:05 AM, Ivan Chernyshev <1729...@bugs.launchpad.net> wrote:
>
> 'kernel-bug-exists-upstream'
>
> I INSTALL linux-
> headers-4.14.0-041400rc7_4.14.0-041400rc7.201710292231_all.deb
>
> BUT - kernel-bug-exists-upstream
IIUC the USB device still works correctly, right?
>
>
'kernel-bug-exists-upstream'
I INSTALL linux-
headers-4.14.0-041400rc7_4.14.0-041400rc7.201710292231_all.deb
BUT - kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729618
I do not know English very well, I communicate through an interpreter
Google. So I always had this problem before. I just ignore it, because
it looks like it's not visible to Linux. You can see only by command
dmesg, but when you install other distributions it appears when you
download grub. Now
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.14