This bug was fixed in the package linux - 4.4.0-166.195
---
linux (4.4.0-166.195) xenial; urgency=medium
* xenial/linux: 4.4.0-166.195 -proposed tracker (LP: #1846069)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* CVE-2017-18232
- scsi:
This bug was fixed in the package linux - 4.15.0-66.75
---
linux (4.15.0-66.75) bionic; urgency=medium
* bionic/linux: 4.15.0-66.75 -proposed tracker (LP: #1846131)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* CVE-2018-21008
- rsi: add fix
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838886
Title:
New ID in ums-realtek module breaks cardreader
To
Based on the feedback in comment #52, I manually re-added the '
verification-done-bionic ' tag to make the bots happy.
Thanks for the feedback @Uwe Schindler !!
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug was fixed in the package linux - 5.0.0-32.34
---
linux (5.0.0-32.34) disco; urgency=medium
* disco/linux: 5.0.0-32.34 -proposed tracker (LP: #1846097)
* CVE-2019-14814 // CVE-2019-14815 // CVE-2019-14816
- mwifiex: Fix three heap overflow at parsing element in
It would be good that somebody else adds the correct tags so this fix
gets delivered to all distributions using the 5.x kernels. I am not sure
if 4.x needs the fix at all, as according to the latest non-hwe kernel I
used in bionic, the bad realtek IDs were not added to the unusual
devices. But
Hi,
using the "-proposed" thingie in Bionic with the HWE kernel did not work even
after the last query.
So I did it the hard way (without any PPA used with APT/APT-GET). I
downloaded the kernel manually and installed the following files:
root@sirius:~/kernel-pkg# ls -l
total 66160
-rw-r--r-- 1
For confirmation that my auto_delink_en setting was kept by the default
after rebooting (so I made sure that initramfs was containing correct
settings):
root@sirius:~# cat /sys/module/ums_realtek/parameters/auto_delink_en
1
So it looks like the module boots correctly and having the default
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-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag
Because the fix is in Bionic kernel so the bot send the message.
The 5.0 based kernel you are using is from Disco, so it'll use
verification-needed-disco instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
OK, so how comes that the bot sent me this message that I should test
"-proposed"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838886
Title:
New ID in ums-realtek module breaks cardreader
To
It's not in 5.0.0-31. It's included in 5.0.0-32.34.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838886
Title:
New ID in ums-realtek module breaks cardreader
To manage notifications about this
Hi,
I installed the latest -proposed kernel image in bionic (HWE variant), but the
bug is not fixed there. It looks like it's not merged into the 5.0 kernel
there. That's easy to see, because modinfo, still shows the old parameter
description:
root@sirius:~# modinfo ums-realtek
filename:
This is the kernel that was installed from "-proposed":
Linux sirius 5.0.0-31-generic #33~18.04.1-Ubuntu SMP Tue Oct 1 10:20:39 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
** Tags removed: verification-needed-bionic
** Tags added: verification-failed-bionic
--
You received this bug notification
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-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
These kernel commits:
* USB: storage: ums-realtek: Update module parameter description for
auto_delink_en
* USB: storage: ums-realtek: Whitelist auto-delink support
have already been applied to Bionic as part of bug #1843338 (Bionic
update: upstream stable patchset 2019-09-09) and to Disco as
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Disco)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838886
** Description changed:
- When installing the latest HWE stack (Linux 5.0) to Ubuntu 18.04, the
- Realtek cardreader in my ZOTAC ZBOX-CI323NANO stops working correctly.
+ === SRU Justification ===
+ [Impact]
+ Some ums-realtek card readers may dropped from USB bus after using
+ ums-realtek driver
Thanks, looks fine, well understood. It would be good to keep me in CC
once Realtek provides a new patch. I can help to test. Of course this
issue is solved after the workaround with limiting auto-delink to the
three "original IDs" only.
--
You received this bug notification because you are a
https://lore.kernel.org/lkml/20190827173450.13572-2-kai.heng.f...@canonical.com/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838886
Title:
New ID in ums-realtek module breaks cardreader
To
Hi Kai-Heng,
I installed your kernel, removed module parameters, recreated initramfs and
rebooted with full shutdown/powerplugged.
It looks like it's coming up without any warnings showing. It also
detects no phantom cards. I was also able to insert a SD card and was
able to mount it.
So looks
Hi Kai-Heng,
I was on vacation last week, will test this soon!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838886
Title:
New ID in ums-realtek module breaks cardreader
To manage notifications
Can you please test this kernel:
https://people.canonical.com/~khfeng/lp1838886/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838886
Title:
New ID in ums-realtek module breaks cardreader
To
Here is the full output attached.
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838886/+attachment/5282471/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
Can you please attach full dmesg? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838886
Title:
New ID in ums-realtek module breaks cardreader
To manage notifications about this bug go
Hi,
after enabling that option, there were not many additional lines in dmesg.
Asking the debugfs was not possible due to kernel-lockdown.
[3.632200] usb 1-5.1: New USB device found, idVendor=0bda, idProduct=0153,
bcdDevice=57.13
Can you boot with module option:
options ums-realtek dyndbg=+p
And attach dmesg? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838886
Title:
New ID in ums-realtek module breaks cardreader
I am currently sorting this out with Realtek. I'll let you know when
there's any progress.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838886
Title:
New ID in ums-realtek module breaks
Should I maybe disable selective suspend and try again?
root@sirius:~# cat /sys/module/ums_realtek/parameters/ss_en
1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838886
Title:
New ID in
Of course, I forgot to add: I did the test with current stable 5.0
kernel. If I should repeat all tests with latest (unsigned) kernel,
please tell me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
I can confirm, if I add this parameter to /etc/modprobe.d/realtek.conf:
options ums-realtek auto_delink_en=0
...and rebuild the initramfs, after a full shutdown with power coord
removed, it works correctly - but only initially!!! FYI, just rebooting
is not enough and brings crazy error
Does "ums_realtek.auto_delink_en=0" kernel parameter help?
I don't see the issue after adding the option.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838886
Title:
New ID in ums-realtek module
Hi,
I was able to try the 5.3.0 kernel from the PPA as stated above. It was a bit
complicated, as I had to disable secure boot first, so it was good that I did
not try it from remote (my wife would have killed me!).
In short: The problem persists. The ums-realtek driver does not work
with this
Ok, I will try newer kernel on the weekend. Until then I can't check it.
Sorry.
Uwe
Am August 5, 2019 12:55:30 PM UTC schrieb Kai-Heng Feng
:
>I asked that because I've observed that on my machine if I reboot the
>system from older kernel.
>New kernels have a fix for USB2 LPM shutdown, exactly
I asked that because I've observed that on my machine if I reboot the system
from older kernel.
New kernels have a fix for USB2 LPM shutdown, exactly for issues like this one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As said before I have no physical access anymore.
But yes, it was all tested. I am developer like you, so I know what I am
doing.
Uwe
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838886
Title:
Can you fully power off your system, unplug the power plug and see if
the issue disappears after a cold boot?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838886
Title:
New ID in ums-realtek
Ok, does this build contain any changes regarding to this? Since the
commit on upstream mentioned above there were no changes in ums-realtek
so I don't think this will help. IMHO, reverting the patch is the only
right thing to do. The device id used for this device is much older than
the other
For starter, please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc2/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838886
Title:
New ID in ums-realtek module
Reply #18:
It looks like after the id is added to unusual_realtek.h(USB: usb-
storage: Add new ID to ums-realtek ), the uas will not handle this
device anymore since it calls usb_usual_ignore_device() and this device
is ignored by the uas.
That is the reason for the result of #18.
--
You
Some more info: I was not able to run the device with new kernel, not
even with blacklisted ums-realtek. It looks like the native usb-storage
driver ignores the device id.
On 4.17 kernel I verified that the device loads perfectly with the
default usb-storage driver uas.
I have no idea why this
Thanks. If you need any more information, I am happy to help.
Is there any way to tell usb-storage to not use the realtek driver and
instead the default one?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok, as the commit author, I'll raise the issue to Realtek.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected bionic
** Description changed:
When installing the latest HWE stack (Linux 5.0) to Ubuntu 18.04, the
Realtek cardreader in my ZOTAC ZBOX-CI323NANO stops working correctly.
Previously it accepted SD cards all the time. Now it looks like
45 matches
Mail list logo
