To complete the list of products: In addition to games, this change is
also useful for users of Elasticsearch and/or Opensearch and Apache
Lucene/Solr on large clusters.
Elasticsearch also suggests raising the value, although not so high:
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
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
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
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
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
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,
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
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
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
O
> dmi.board.vendor: ZOTAC
> dmi.board.version: XX
> dmi.chassis.asset.tag: Default string
> dmi.chassis.type: 2
> dmi.chassis.vendor: Default string
> dmi.chassis.version: Default string
>dmi.modalias:
>dmi:bvnAmericanMegatrendsInc.:bvrB301P021:bd03/07/2017:svnZOTAC:pnZB
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:
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
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.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1838886/+attachment/5280766/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838886
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1838886/+attachment/5280768/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1838886/+attachment/5280767/+files/UdevDb.txt
--
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:
apport information
** Attachment added: "Card0.Codecs.codec.2.txt"
https://bugs.launchpad.net/bugs/1838886/+attachment/5280758/+files/Card0.Codecs.codec.2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Card0.Codecs.codec.0.txt"
https://bugs.launchpad.net/bugs/1838886/+attachment/5280757/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1838886/+attachment/5280764/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1838886/+attachment/5280765/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1838886/+attachment/5280763/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838886
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1838886/+attachment/5280761/+files/Lspci.txt
--
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
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1838886/+attachment/5280759/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/1838886/+attachment/5280762/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1838886/+attachment/5280760/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838886
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
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1838886/+attachment/5280756/+files/CRDA.txt
--
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
Public bug reported:
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 you have
to insert the card on booting or shortly after booting to
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693854
Title:
linux-image-4.8.0-53-generic on 64bit Ubuntu installations causes
problems with 32bit Java (e.g., ThreadLocal
** Changed in: lucene
Assignee: (unassigned) => Uwe Schindler (uwe-thetaphi)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693854
Title:
linux-image-4.8.0-53-generic on 64bit Ubu
** Bug watch added: Email to dev@lucene #
mailto:d...@lucene.apache.org
** Also affects: lucene via
mailto:d...@lucene.apache.org
Importance: Undecided
Status: New
** Bug watch added: Email to rory.odonnell@oracle #
mailto:rory.odonn...@oracle.com
** Also affects: openjdk via
Public bug reported:
I am running the famous Jenkins server that tests Oracle's Java releases
with Apache Lucene. When migrating to new hardware and installing Ubuntu
16.04.2, the tests failed with strange errors:
The system is Ubuntu 16.04.2 (64bits) with linux-image-4.8.0-53-generic. Java
7,
This link may also be related, it tells about same problems, but without
CISCO hardware: https://askubuntu.com/questions/475700/application-
stuck-in-tcp-retransmit/563984
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm this bug with the 3.13 kernel shipped with Ubuntu 14.04.
The 3.2 kernel shipped with Ubuntu 12.04 did not have the problem, all
download were succeeding. The problem started after upgrade to 14.04.
The problem also solved after downgrading the kernel to 3.2 by
downloading the latest
42 matches
Mail list logo
