[Kernel-packages] [Bug 1880631] Re: l2tp.sh from net in ubuntu_kernel_selftests failed on F-OEM-5.6
** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1880631 Title: l2tp.sh from net in ubuntu_kernel_selftests failed on F-OEM-5.6 Status in ubuntu-kernel-tests: In Progress Status in linux-oem-5.6 package in Ubuntu: New Bug description: Issue found on 5.6.0-1011.11-oem # selftests: net: l2tp.sh # Warning: file l2tp.sh is not executable, correct this. not ok 32 selftests: net: l2tp.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1880631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919277] Re: l2tp.sh from net in ubuntu_kernel_selftests cause dmesg flooded with "unregister_netdevice: waiting for eth0 to become free. Usage count = 1" on F-OEM-5.6
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1919277 Title: l2tp.sh from net in ubuntu_kernel_selftests cause dmesg flooded with "unregister_netdevice: waiting for eth0 to become free. Usage count = 1" on F-OEM-5.6 Status in ubuntu-kernel-tests: New Status in linux-signed-oem-5.6 package in Ubuntu: New Bug description: Issue found with 5.6.0-1048-oem While debugging bug 1880631, I found that this test will cause dmesg flooded with: "unregister_netdevice: waiting for eth0 to become free. Usage count = 1" for about every 10 secondes. Test log: $ sudo ./l2tp.sh TEST: IPv4 basic L2TP tunnel[ OK ] TEST: IPv4 route through L2TP tunnel[ OK ] TEST: IPv6 basic L2TP tunnel[ OK ] TEST: IPv6 route through L2TP tunnel[ OK ] TEST: IPv4 basic L2TP tunnel - with IPsec [ OK ] TEST: IPv4 route through L2TP tunnel - with IPsec [ OK ] TEST: IPv6 basic L2TP tunnel - with IPsec [ OK ] TEST: IPv6 route through L2TP tunnel - with IPsec [ OK ] TEST: IPv4 basic L2TP tunnel[ OK ] TEST: IPv4 route through L2TP tunnel[ OK ] TEST: IPv6 basic L2TP tunnel - with IPsec [ OK ] TEST: IPv6 route through L2TP tunnel - with IPsec [ OK ] TEST: IPv4 basic L2TP tunnel - after IPsec teardown [ OK ] TEST: IPv4 route through L2TP tunnel - after IPsec teardown [ OK ] TEST: IPv6 basic L2TP tunnel - after IPsec teardown [ OK ] TEST: IPv6 route through L2TP tunnel - after IPsec teardown [ OK ] Tests passed: 16 Tests failed: 0 dmesg output: $ dmesg Message from syslogd@glameow at Mar 16 05:01:40 ... kernel:[ 739.608359] unregister_netdevice: waiting for eth0 to become free. Usage count = 1 [ 708.560589] eth1: renamed from tmp [ 708.587396] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 708.587472] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 708.616950] eth2: renamed from tmp [ 708.643341] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 708.687057] l2tp_core: L2TP core driver, V2.0 [ 708.689380] l2tp_netlink: L2TP netlink interface [ 708.695479] l2tp_ip: L2TP IP encapsulation support (L2TPv3) [ 708.700061] l2tp_eth: L2TP ethernet pseudowire support (L2TPv3) [ 708.726295] l2tp_ip6: L2TP IP encapsulation support for IPv6 (L2TPv3) [ 708.788973] Initializing XFRM netlink socket [ 719.448364] unregister_netdevice: waiting for eth0 to become free. Usage count = 1 [ 729.528359] unregister_netdevice: waiting for eth0 to become free. Usage count = 1 [ 739.608359] unregister_netdevice: waiting for eth0 to become free. Usage count = 1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.6.0-1048-oem 5.6.0-1048.52 ProcVersionSignature: User Name 5.6.0-1048.52-oem 5.6.19 Uname: Linux 5.6.0-1048-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Mar 16 05:20:45 2021 SourcePackage: linux-signed-oem-5.6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1919277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919277] [NEW] l2tp.sh from net in ubuntu_kernel_selftests cause dmesg flooded with "unregister_netdevice: waiting for eth0 to become free. Usage count = 1" on F-OEM-5.6
Public bug reported: Issue found with 5.6.0-1048-oem While debugging bug 1880631, I found that this test will cause dmesg flooded with: "unregister_netdevice: waiting for eth0 to become free. Usage count = 1" for about every 10 secondes. Test log: $ sudo ./l2tp.sh TEST: IPv4 basic L2TP tunnel[ OK ] TEST: IPv4 route through L2TP tunnel[ OK ] TEST: IPv6 basic L2TP tunnel[ OK ] TEST: IPv6 route through L2TP tunnel[ OK ] TEST: IPv4 basic L2TP tunnel - with IPsec [ OK ] TEST: IPv4 route through L2TP tunnel - with IPsec [ OK ] TEST: IPv6 basic L2TP tunnel - with IPsec [ OK ] TEST: IPv6 route through L2TP tunnel - with IPsec [ OK ] TEST: IPv4 basic L2TP tunnel[ OK ] TEST: IPv4 route through L2TP tunnel[ OK ] TEST: IPv6 basic L2TP tunnel - with IPsec [ OK ] TEST: IPv6 route through L2TP tunnel - with IPsec [ OK ] TEST: IPv4 basic L2TP tunnel - after IPsec teardown [ OK ] TEST: IPv4 route through L2TP tunnel - after IPsec teardown [ OK ] TEST: IPv6 basic L2TP tunnel - after IPsec teardown [ OK ] TEST: IPv6 route through L2TP tunnel - after IPsec teardown [ OK ] Tests passed: 16 Tests failed: 0 dmesg output: $ dmesg Message from syslogd@glameow at Mar 16 05:01:40 ... kernel:[ 739.608359] unregister_netdevice: waiting for eth0 to become free. Usage count = 1 [ 708.560589] eth1: renamed from tmp [ 708.587396] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 708.587472] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 708.616950] eth2: renamed from tmp [ 708.643341] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 708.687057] l2tp_core: L2TP core driver, V2.0 [ 708.689380] l2tp_netlink: L2TP netlink interface [ 708.695479] l2tp_ip: L2TP IP encapsulation support (L2TPv3) [ 708.700061] l2tp_eth: L2TP ethernet pseudowire support (L2TPv3) [ 708.726295] l2tp_ip6: L2TP IP encapsulation support for IPv6 (L2TPv3) [ 708.788973] Initializing XFRM netlink socket [ 719.448364] unregister_netdevice: waiting for eth0 to become free. Usage count = 1 [ 729.528359] unregister_netdevice: waiting for eth0 to become free. Usage count = 1 [ 739.608359] unregister_netdevice: waiting for eth0 to become free. Usage count = 1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.6.0-1048-oem 5.6.0-1048.52 ProcVersionSignature: User Name 5.6.0-1048.52-oem 5.6.19 Uname: Linux 5.6.0-1048-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Mar 16 05:20:45 2021 SourcePackage: linux-signed-oem-5.6 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-signed-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1919277 Title: l2tp.sh from net in ubuntu_kernel_selftests cause dmesg flooded with "unregister_netdevice: waiting for eth0 to become free. Usage count = 1" on F-OEM-5.6 Status in ubuntu-kernel-tests: New Status in linux-signed-oem-5.6 package in Ubuntu: New Bug description: Issue found with 5.6.0-1048-oem While debugging bug 1880631, I found that this test will cause dmesg flooded with: "unregister_netdevice: waiting for eth0 to become free. Usage count = 1" for about every 10 secondes. Test log: $ sudo ./l2tp.sh TEST: IPv4 basic L2TP tunnel[ OK ] TEST: IPv4 route through L2TP tunnel[ OK ] TEST: IPv6 basic L2TP tunnel[ OK ] TEST: IPv6 route through L2TP tunnel[ OK ] TEST: IPv4 basic L2TP tunnel - with IPsec [ OK ] TEST: IPv4 route through L2TP tunnel - with IPsec [ OK ] TEST: IPv6 basic L2TP tunnel - with IPsec [ OK ] TEST: IPv6 route through L2TP tunnel - with IPsec [ OK ] TEST: IPv4 basic L2TP tunnel[ OK ] TEST: IPv4 route through L2TP tunnel[ OK ] TEST: IPv6 basic L2TP tunnel - with IPsec [ OK ] TEST: IPv6 route through L2TP tunnel - with IPsec [ OK ] TEST: IPv4 basic L2TP tunnel - after IPsec teardown [ OK ] TEST: IPv4 route through L2TP tunnel - after IPsec teardown [ OK ] TES
[Kernel-packages] [Bug 1880631] Re: l2tp.sh from net in ubuntu_kernel_selftests failed on F-OEM-5.6
With further investigation, this was disabled in the test case:
#
# this test breaks 5.0+ (and maybe earlier), disable it for now
# 5/12/2019, LP#1854968
#
print("Disabling l2tp.sh")
fn = 'linux/tools/testing/selftests/net/l2tp.sh'
if os.path.exists(fn):
cmd = 'chmod -x ' + fn
utils.system(cmd)
With bug 1854968 fixed, we can see if this test can be added back.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1880631
Title:
l2tp.sh from net in ubuntu_kernel_selftests failed on F-OEM-5.6
Status in ubuntu-kernel-tests:
New
Status in linux-oem-5.6 package in Ubuntu:
New
Bug description:
Issue found on 5.6.0-1011.11-oem
# selftests: net: l2tp.sh
# Warning: file l2tp.sh is not executable, correct this.
not ok 32 selftests: net: l2tp.sh
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1880631/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880631] Re: l2tp.sh from net in ubuntu_kernel_selftests failed on F-OEM-5.6
** Tags added: sru-20210222 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1880631 Title: l2tp.sh from net in ubuntu_kernel_selftests failed on F-OEM-5.6 Status in ubuntu-kernel-tests: New Status in linux-oem-5.6 package in Ubuntu: New Bug description: Issue found on 5.6.0-1011.11-oem # selftests: net: l2tp.sh # Warning: file l2tp.sh is not executable, correct this. not ok 32 selftests: net: l2tp.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1880631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919275] [NEW] crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
Public bug reported: On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility 7.2.8-1ubuntu0.18.04 fails with: crash: cannot determine VA_BITS_ACTUAL This bug/change in crash provides a workaround for 5.4+ https://github.com/crash-utility/crash/issues/52 kernels. While it appears as though it this was fixed it https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still doesn't seem to work with a 5.4 kernel including. I also tested https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb and it exhibits the same problem. ** Affects: crash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL Status in crash package in Ubuntu: New Bug description: On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility 7.2.8-1ubuntu0.18.04 fails with: crash: cannot determine VA_BITS_ACTUAL This bug/change in crash provides a workaround for 5.4+ https://github.com/crash-utility/crash/issues/52 kernels. While it appears as though it this was fixed it https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still doesn't seem to work with a 5.4 kernel including. I also tested https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb and it exhibits the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885862] Re: Add in-tree Realtek 8821CE wireless module support
verified 5.10.0-1017.18 from focal-proposed.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1885862
Title:
Add in-tree Realtek 8821CE wireless module support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux-firmware source package in Focal:
In Progress
Status in linux-oem-5.10 source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
Won't Fix
Status in linux source package in Groovy:
Won't Fix
Status in linux-firmware source package in Groovy:
Invalid
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
[SRU Justification]
[Impact]
RTL8821CE RFE Type 2 PCIE module is not supported by new rtw88 driver
in kernel version v5.11 or older. Dmesg gives:
rtw_8821ce :01:00.0: enabling device ( -> 0003)
rtw_8821ce :01:00.0: Firmware version 24.8.0, H2C version 12
rtw_8821ce :01:00.0: rfe 2 isn't supported
rtw_8821ce :01:00.0: failed to setup chip efuse info
rtw_8821ce :01:00.0: failed to setup chip information
Such modules are previosly covered by rtl8821ce-dkms.
[Fix]
Patch set
https://lore.kernel.org/linux-wireless/20210202055012.8296-1-pks...@realtek.com/
landed in v5.12-rc1, as well as WLAN firmware updates in commit
c5e3240eff0f ("rtw88: RTL8821C: Update firmware to v24.8"), which is
already available in Hirsute version 1.195. Bluetooth firmware should
have been the latest 0x829a_7644 in both Focal/Hirsute.
[Test Case]
With patched kernel, wlan interface should be up and running:
rtw_8821ce :01:00.0: enabling device ( -> 0003)
rtw_8821ce :01:00.0: Firmware version 24.8.0, H2C version 12
rtw_8821ce :01:00.0 wlp1s0: renamed from wlan0
[Where problems could occur]
Previously this hardware piece can only be driven by external DKMS
modules, so with this driver patched, users can now use in-tree driver,
but may experience the difference between them in power consumption or
feature supportness.
[Other Info]
While Bionic/Focal LTS is still using rtl8821ce-dkms for RFE Type 2
cards, there is no plan to introduce such change to them. So they'll be
upgraded only at the next point release with kernel >= 5.11.
== original bug description ==
8821ce is being upstreamed in https://lore.kernel.org/linux-
wireless/20200603094218.19942-1-yhchu...@realtek.com/ . To backport it
to ubuntu kernel so that we may obsolete the usage of rtl8821ce-dkms
from https://bugs.launchpad.net/ubuntu/+source/rtl8821ce .
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1885862/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911828] Re: Ubuntu 18.04.5/20.04 kernel doesn't have latest i40e driver for X710-T2L module
[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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911828 Title: Ubuntu 18.04.5/20.04 kernel doesn't have latest i40e driver for X710-T2L module Status in linux package in Ubuntu: Expired Bug description: Ubuntu 18.04.5/20.04 kernel doesn't have latest i40e driver for X710-T2L module,Please add the driver on next kernel version release. More details please refer to https://bugs.launchpad.net/quantatw/+bug/1905673 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919245] Re: [Lenovo Ideapad 5-15ARE05] Touchpad does not work at all
Upstream bug https://bugzilla.kernel.org/show_bug.cgi?id=207759 I think this is the possible fix https://lore.kernel.org/linux- input/20210310105151.80628-1-hdego...@redhat.com/ which is pending review now. ** Summary changed: - Touchpad does not work at all + [Lenovo Ideapad 5-15ARE05] Touchpad does not work at all ** Bug watch added: Linux Kernel Bug Tracker #207759 https://bugzilla.kernel.org/show_bug.cgi?id=207759 -- 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/1919245 Title: [Lenovo Ideapad 5-15ARE05] Touchpad does not work at all Status in linux package in Ubuntu: Confirmed Bug description: I just installed ubuntu, but the touchpad doesn't work at all, it didn't work since the installation process and it's not detected. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-45-generic 5.8.0-45.51 ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alessio 39892 F pulseaudio /dev/snd/controlC0: alessio 39892 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Mar 15 21:26:07 2021 InstallationDate: Installed on 2021-03-15 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 81YQ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=UUID=403466ca-3551-431b-bcd9-d06dbcfff352 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-45-generic N/A linux-backports-modules-5.8.0-45-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2020 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN36WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Ideapad 5-15ARE05 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnLENOVO:bvrE7CN36WW:bd11/23/2020:br1.36:efr1.36:svnLENOVO:pn81YQ:pvrIdeapad5-15ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeapad5-15ARE05: dmi.product.family: IDEAPAD dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IDEAPAD dmi.product.version: Ideapad 5-15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919051] Re: ch341 USB-Serial converter only receives, does not send
Hello Luzemário Thanks for the test and quick response. Since we don't have this device, we will need your help to report this issue to the upstream: https://bugzilla.kernel.org/ Once the fix has landed we can backport it to Ubuntu kernel. Thank you. -- 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/1919051 Title: ch341 USB-Serial converter only receives, does not send Status in linux package in Ubuntu: Confirmed Bug description: This device works flawlessly on Windows XP with native driver, both as a physical machine or inside a VM. It appears on XP's device management as "USB 2.0" name. On Ubuntu, Shorting pins 2 and 3 of DB9 connector does not give back characters sent (no echo), nor typed strings are sent to other RS232 devices, despite of communication settings. Characters from remote devices are correctly received. Using a null modem cable to other RS232 terminal shows that the local terminal receives, but does not transmit. Its worth to mention: passing through the device to a guest virtual machine (KVM) running Windows XP makes it work correctly with XP driver inside the guest OS. Bringing back the device stops transmitting. Only receive works. Tested with the version below: NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal Kernel: Linux host 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Device ID: ID 4348:5523 WinChipHead USB->RS 232 adapter with Prolifec PL 2303 chipset Modinfo: filename: /lib/modules/5.4.0-66-generic/kernel/drivers/usb/serial/ch341.ko license:GPL v2 srcversion: 8F5F64E72BDA4E76E6F4F4D alias: usb:v4348p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7522d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5512d*dc*dsc*dp*ic*isc*ip*in* depends:usbserial retpoline: Y intree: Y name: ch341 vermagic: 5.4.0-66-generic SMP mod_unload sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:1E:07:0D:94:23:77:98:99:05:31:F3:76:E8:6B:76:12:7C:83:9E:05 sig_hashalgo: sha512 signature: 50:CE:79:92:87:EA:82:77:A9:25:A3:B7:F2:B3:ED:63:FE:85:EB:61: 7A:31:C5:9E:E5:78:E5:44:C6:FE:5D:74:4A:60:B6:0A:94:3F:C3:70: 0B:6D:27:A6:89:F7:D2:AC:8E:71:AC:0D:AF:5D:3A:19:07:18:F9:7C: B8:3C:47:DF:18:4D:13:C9:F8:45:AC:81:19:B0:DE:57:16:1A:F5:C6: AC:41:7E:E7:F2:6D:29:9C:14:A3:04:F8:9B:DF:8D:2E:9F:34:44:18: A8:FF:C6:A4:AF:04:86:D5:6D:F2:4C:AD:D2:65:4C:63:0F:C1:82:E3: 28:20:F2:D4:80:86:1A:67:1D:A2:56:18:87:E2:AB:40:E6:6A:48:E5: D7:D2:6F:6F:DB:05:20:B2:76:81:5C:0C:36:02:37:E9:A2:08:4E:53: 5E:9C:18:03:50:11:2D:E4:62:74:6E:CB:42:67:25:22:0C:F6:55:D8: 6F:E3:5A:15:AC:10:B7:F2:B7:C9:20:6C:19:ED:CC:7D:CC:CB:48:3B: B0:5E:E3:ED:05:DF:DF:65:FF:19:AD:76:6E:40:D2:0B:F0:11:65:D5: 92:7D:C9:3A:32:BE:A8:13:CE:C1:DE:D9:73:0F:0A:0B:8A:08:55:2E: 41:9D:B9:9A:AD:EC:4C:7D:98:3A:52:38:DF:78:DE:33:F1:14:A2:1B: AC:93:FD:30:76:A5:7C:AF:13:16:B8:5E:0B:73:A7:1F:20:E4:54:44: 07:A2:11:7F:D7:0E:B3:1C:A9:AA:73:76:0E:89:E0:D5:74:39:66:2F: E8:14:93:EC:7A:B2:23:E0:CC:77:9F:CD:D9:99:CB:B0:14:21:1C:1F: 0C:E9:30:B8:C3:55:8F:49:FC:88:5D:EF:20:B9:0E:F2:88:28:5A:93: 08:4D:2B:76:64:85:D1:E0:1C:9C:4B:86:2C:DB:65:F6:D8:23:A0:8D: 1B:22:74:0C:B9:41:9E:57:5A:67:4C:CC:1F:E2:43:5F:C2:21:82:E6: D4:C1:66:6F:30:54:27:2E:1D:22:8C:65:7F:93:C8:1D:C0:51:F0:7D: 7A:96:3A:3B:3D:C4:6E:69:DF:83:8A:85:0D:35:15:F9:5E:89:0F:D5: 9E:6F:A1:5F:39:CE:2A:88:57:97:DF:42:5C:70:12:4E:91:9E:1A:92: 49:99:C3:7B:38:12:B0:3A:D0:92:38:45:C7:74:3C:66:0F:A1:9C:C2: 9F:DC:A2:1B:DF:20:BB:F5:A5:F0:10:D6:6F:4F:C1:90:00:C3:F9:D8: 42:96:D2:28:FD:DE:21:33:6C:F4:7F:18:B2:ED:F9:A6:A4:4A:A5:4F: 26:7C:C0:F7:8B:A9:B3:2F:5A:5B:E2:B8 Demsg entries: usb 4-3: new full-speed USB device number 6 using ohci-pci usb 4-3: New USB device found, idVendor=4348, idProduct=5523, bcdDevice= 2.50 usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=
[Kernel-packages] [Bug 1919042] Re: Touchpad not working on HP Pavilion Laptop 14-dv0xxx
Hello, please refer to the "How do I install an upstream kernel?" section in https://wiki.ubuntu.com/Kernel/MainlineBuilds After booting with the mainline kernel (you can check the kernel version with `uname -a` command) please check the touchpad function again. Testing mainline kernel will allow us know if your hardware works in the Linux world. If your touchpad is still not working with the latest mainline kernel, it means that your hardware is not supported at all. You will have to report this issue to https://bugzilla.kernel.org/ -- 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/1919042 Title: Touchpad not working on HP Pavilion Laptop 14-dv0xxx Status in linux package in Ubuntu: Incomplete Bug description: HP Imagepad not detected in 'HP Pavilion 14-DV00054TU' after installing Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hp 1523 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 14 00:45:36 2021 InstallationDate: Installed on 2021-03-08 (5 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Pavilion Laptop 14-dv0xxx ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=84f5a50d-8a8e-4afc-8e8c-3245f566346a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2021 dmi.bios.vendor: Insyde dmi.bios.version: F.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 87C9 dmi.board.vendor: HP dmi.board.version: 34.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.11:bd01/15/2021:svnHP:pnHPPavilionLaptop14-dv0xxx:pvrType1ProductConfigId:rvnHP:rn87C9:rvr34.27:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 14-dv0xxx dmi.product.sku: 2N1L0PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919267] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1919267 Title: ubuntu 20.10 Status in linux package in Ubuntu: Confirmed Bug description: can't use fingerprint ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-44-generic 5.8.0-44.50 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sigma1413 1693 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 16 09:16:54 2021 InstallationDate: Installed on 2021-02-22 (21 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04ca:3018 Lite-On Technology Corp. Bus 001 Device 002: ID 13d3:5a11 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook 15_ASUS Laptop X507UAR ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=d2f833e3-a267-4389-b9c3-ba4a60076d8e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X507UAR.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X507UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX507UAR.303:bd05/21/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnVivoBook15_ASUSLaptopX507UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX507UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook 15_ASUS Laptop X507UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919250] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1919250 Title: [ASUS TUF Gaming FX505DT] [ELAN1200:00 04F3:30BA] touchpad freeze or disable itself after laptop go to suspend Status in linux package in Ubuntu: Confirmed Bug description: touchpad freeze or disable itself after laptop go to suspend... and non of the solutions like "modprobe -r psmouse"/ "modprobe psmouse" do work (doesn't work). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: None CurrentDesktop: MATE Date: Mon Mar 15 16:58:29 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev ff) (prog-if ff) Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Picasso [1043:18f1] InstallationDate: Installed on 2017-06-21 (1363 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=UUID=5a4a3b87-22ad-46cb-b313-e45f053e558e ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX505DT.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX505DT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 12.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX505DT.310:bd12/24/2019:br5.14:efr12.0:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DT_FX505DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming dmi.product.name: TUF Gaming FX505DT_FX505DT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919250] Re: [ASUS TUF Gaming FX505DT] touchpad freeze
** Summary changed: - touchpad freeze + [ASUS TUF Gaming FX505DT] touchpad freeze ** Summary changed: - [ASUS TUF Gaming FX505DT] touchpad freeze + [ASUS TUF Gaming FX505DT] touchpad freeze or disable itself after laptop go to suspend ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - [ASUS TUF Gaming FX505DT] touchpad freeze or disable itself after laptop go to suspend + [ASUS TUF Gaming FX505DT] [ELAN1200:00 04F3:30BA] touchpad freeze or disable itself after laptop go to suspend ** Tags added: resume suspend-resume -- 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/1919250 Title: [ASUS TUF Gaming FX505DT] [ELAN1200:00 04F3:30BA] touchpad freeze or disable itself after laptop go to suspend Status in linux package in Ubuntu: Confirmed Bug description: touchpad freeze or disable itself after laptop go to suspend... and non of the solutions like "modprobe -r psmouse"/ "modprobe psmouse" do work (doesn't work). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: None CurrentDesktop: MATE Date: Mon Mar 15 16:58:29 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev ff) (prog-if ff) Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Picasso [1043:18f1] InstallationDate: Installed on 2017-06-21 (1363 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=UUID=5a4a3b87-22ad-46cb-b313-e45f053e558e ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX505DT.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX505DT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 12.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX505DT.310:bd12/24/2019:br5.14:efr12.0:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DT_FX505DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming dmi.product.name: TUF Gaming FX505DT_FX505DT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919267] [NEW] ubuntu 20.10
Public bug reported: can't use fingerprint ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-44-generic 5.8.0-44.50 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sigma1413 1693 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 16 09:16:54 2021 InstallationDate: Installed on 2021-02-22 (21 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04ca:3018 Lite-On Technology Corp. Bus 001 Device 002: ID 13d3:5a11 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook 15_ASUS Laptop X507UAR ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=d2f833e3-a267-4389-b9c3-ba4a60076d8e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X507UAR.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X507UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX507UAR.303:bd05/21/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnVivoBook15_ASUSLaptopX507UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX507UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook 15_ASUS Laptop X507UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug groovy -- 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/1919267 Title: ubuntu 20.10 Status in linux package in Ubuntu: Confirmed Bug description: can't use fingerprint ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-44-generic 5.8.0-44.50 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sigma1413 1693 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 16 09:16:54 2021 InstallationDate: Installed on 2021-02-22 (21 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04ca:3018 Lite-On Technology Corp. Bus 001 Device 002: ID 13d3:5a11 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook 15_ASUS Laptop X507UAR ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=d2f833e3-a267-4389-b9c3-ba4a60076d8e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X507UAR.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X507UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX507UAR.303:bd05/21/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnVivoBook15_ASUSLaptopX507UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX507UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook 15_ASUS Laptop X507UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919248] Re: (nvidia) ubuntu-drivers - no autoinstall, no luck.
Thanks for the bug report. There only appears to be one GPU installed so can we assume you would like to run two monitors off the same graphics card? It looks like one of the problems might be a bad Xorg config file is in use (the log says it's been forced to make some choices due to a config file). Maybe such a file was created by "sudo ubuntu-drivers autoinstall"? What files do you have in /usr/share/X11/xorg.conf.d ? Please also run this command: lspci -kv > lspcikv.txt and attach the resulting text file here so that we can confirm the kernel driver in use. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-460 (Ubuntu) ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1919248 Title: (nvidia) ubuntu-drivers - no autoinstall, no luck. Status in nvidia-graphics-drivers-460 package in Ubuntu: Incomplete Bug description: Hello, i used to install on my pc with a Nvidia GTX 1650 running 18.04 or 20.04 LTS the correct drivers with "sudo ubuntu-drivers autoinstall" which would download alot of packages and correct the single display output to dualmonitor setup after a reboot. now, after a fresh installation i find that "autoinstall" no longer works, as obsolete, but this prevents me from getting a dual-monitor setup nearly out-of- the-box. according to "additional drivers", i have "no proprietary drivers in use", but after loading the driver list, it switches to "1 propietary driver in use" and it says "nvidia-driver-460" if i would try to install this driver with "apt install nvidia-driver-460" it would download, nothing, so i guess it is already installed. however, no dualmonitor setup, and also the other monitor is not really recognized. as said, before , with the "sudo ubuntu-driver autoinstall" command, really alot of packages got downloaded and afterwards it functioned everytime; so now i wonder how such a routine could become obsolete and be replaced by somehting apparently not functioning so well. anyway, if i did something, wrong, please let me know. ah yes, and i did install Ubuntu 20.04 LTS with the option "safe graphics" , maybe the error is because of this? Thank youo very much. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 15 21:46:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. TU117 [GeForce GTX 1650] [19da:1546] InstallationDate: Installed on 2021-03-15 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Micro-Star International Co., Ltd. MS-7A38 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=UUID=8ada1912-76fa-46ce-9dcb-e2c21f5f1238 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 9.90 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M PRO-VDH PLUS (MS-7A38) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 7.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr9.90:bd06/11/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A38:pvr7.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-VDHPLUS(MS-7A38):rvr7.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr7.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A38 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 7.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-vide
[Kernel-packages] [Bug 1919250] [NEW] [ASUS TUF Gaming FX505DT] touchpad freeze or disable itself after laptop go to suspend
You have been subscribed to a public bug: touchpad freeze or disable itself after laptop go to suspend... and non of the solutions like "modprobe -r psmouse"/ "modprobe psmouse" do work (doesn't work). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: None CurrentDesktop: MATE Date: Mon Mar 15 16:58:29 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev ff) (prog-if ff) Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Picasso [1043:18f1] InstallationDate: Installed on 2017-06-21 (1363 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=UUID=5a4a3b87-22ad-46cb-b313-e45f053e558e ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX505DT.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX505DT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 12.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX505DT.310:bd12/24/2019:br5.14:efr12.0:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DT_FX505DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming dmi.product.name: TUF Gaming FX505DT_FX505DT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug false-gpu-hang freeze groovy third-party-packages ubuntu -- [ASUS TUF Gaming FX505DT] touchpad freeze or disable itself after laptop go to suspend https://bugs.launchpad.net/bugs/1919250 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919248] [NEW] (nvidia) ubuntu-drivers - no autoinstall, no luck.
You have been subscribed to a public bug: Hello, i used to install on my pc with a Nvidia GTX 1650 running 18.04 or 20.04 LTS the correct drivers with "sudo ubuntu-drivers autoinstall" which would download alot of packages and correct the single display output to dualmonitor setup after a reboot. now, after a fresh installation i find that "autoinstall" no longer works, as obsolete, but this prevents me from getting a dual-monitor setup nearly out-of- the-box. according to "additional drivers", i have "no proprietary drivers in use", but after loading the driver list, it switches to "1 propietary driver in use" and it says "nvidia-driver-460" if i would try to install this driver with "apt install nvidia-driver-460" it would download, nothing, so i guess it is already installed. however, no dualmonitor setup, and also the other monitor is not really recognized. as said, before , with the "sudo ubuntu-driver autoinstall" command, really alot of packages got downloaded and afterwards it functioned everytime; so now i wonder how such a routine could become obsolete and be replaced by somehting apparently not functioning so well. anyway, if i did something, wrong, please let me know. ah yes, and i did install Ubuntu 20.04 LTS with the option "safe graphics" , maybe the error is because of this? Thank youo very much. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 15 21:46:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. TU117 [GeForce GTX 1650] [19da:1546] InstallationDate: Installed on 2021-03-15 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Micro-Star International Co., Ltd. MS-7A38 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=UUID=8ada1912-76fa-46ce-9dcb-e2c21f5f1238 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 9.90 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M PRO-VDH PLUS (MS-7A38) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 7.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr9.90:bd06/11/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A38:pvr7.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-VDHPLUS(MS-7A38):rvr7.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr7.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A38 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 7.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal ubuntu -- (nvidia) ubuntu-drivers - no autoinstall, no luck. https://bugs.launchpad.net/bugs/1919248 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported
Also impacts the bionic 18.04-aws kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1879214 Title: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Focal: Confirmed Status in makedumpfile source package in Groovy: Confirmed Status in makedumpfile source package in Hirsute: Confirmed Bug description: [Impact] On arm64 and kernels 5.4+ makedumpfile fails. Upstream patches solve this bug : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option https://github.com/makedumpfile/makedumpfile/commit/d8b701796f0491f2ac4b06c7a5b795c29399efab [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo https://github.com/makedumpfile/makedumpfile/commit/67d0e1d68f28c567a704fd6b9b8fd696ad3df183 [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA https://github.com/makedumpfile/makedumpfile/commit/a0216b678a95f099a16172cc4a67ad5aa6a89583 [Test Case] OS: Ubuntu 20.04 LTS kernel: 5.4.0-21-generic arch:arm64 Description: When testing kdump on Ubuntu 20.04 LTS (arm64), makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The error logs are as follows: [ 26.599161] kdump-tools[653]: Starting kdump-tools: [ 26.612761] kdump-tools[659]: Starting kdump-tools: [ 26.628565] kdump-tools[659]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.648621] kdump-tools[676]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.668445] kdump-tools[676]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 26.678199] kdump-tools[676]: get_machdep_info_arm64 [ 26.692518] kdump-tools[659]: get_machdep_info_arm64 [ 26.852221] hns3 :7d:00.0: get link status cmd failed -16 [ 94.351303] kdump-tools[659]: * kdump-tools: makedumpfile failed, * kdump-tools: saved vmcore in /var/crash/202005061048 [ 94.435510] kdump-tools[659]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/202005061048/dmesg.202005061048 [ 94.457103] kdump-tools[688]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 94.476228] kdump-tools[688]: get_machdep_info_arm64: Can't determine platform config values [ 94.485912] kdump-tools[688]: makedumpfile Failed. [ 94.500760] kdump-tools[659]: * kdump-tools: makedumpfile --dump-dmesg failed. dmesg content will be unavailable [ 94.520225] kdump-tools[659]: * kdump-tools: failed to save dmesg content in /var/crash/202005061048 [ 94.544205] kdump-tools[691]: Wed, 06 May 2020 10:49:42 -0400 [ 94.564597] kdump-tools[692]: Rebooting. [ 94.678709] reboot: Restarting systemlpc uart init Done [Regression Potential] Patch 1 : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option removes get_elf_loads function this function was only used with --mem-usage option , since kernel commit kernel commit 23c85094fe18 (kernel versions >4.19) the information needed is in vmcoreinfo Any regression potential would affect the --mem-usage only Patch 2 : [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo arm64 only make use of NUMBER(VA_BITS) in vmcoreinfo as the current way of guessing VA_BITS does not work on Linux 5.4 and later. Before this commit VA_BITS would be calculated in get_versiondep_info_arm64, however this way of calculation breaks after 5.4. This commit gets the VA_BITS from vmcoreinfo and as a safeguard it uses the old way of deriving VA_BITS only if reading from vmcoreinfo doesn't work. From the kernel side VA_BITS is in vmcoreinfo since kernel 4.12, F and later use later kernel so not great regression potentional and if any it would only affect arm64. Patch 3 : [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA arm64 only Linux 5.4 and later kernels for arm64 changed the kernel VA space arrangement and introduced 52-bit kernel VAs by merging branch commit b333b0ba2346. Support 5.9+ kernels with vmcoreinfo entries and 5.4+ kernels with best guessing. This patch makes adjustemnt to properly calculate vabits_actual, max_physmem_bits, page_offset Any regression potential would affect only arm64 and the calculation of the above variables. [Other] For H only the 3 commits are needed and they cherry-pick. For G and F the 3rd commit does not apply and an extra commit is needed : commit da0d25ffa585c9a1adb94562c815daa393b1ee5e [PATCH] arm64: Add support for ARMv8.2-LPA (52-bit PA support) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+subscriptions --
[Kernel-packages] [Bug 1902457] Re: regression: no sound cards detected on lenovo yoga c930 after focal->groovy upgrade
** Changed in: fedora 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/1902457 Title: regression: no sound cards detected on lenovo yoga c930 after focal->groovy upgrade Status in linux package in Ubuntu: Confirmed Status in Fedora: Fix Released Bug description: After upgrading to Groovy, my sound cards no longer work. Alsa-info says "no soundcards detected" --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (465 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 006: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 6, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 8: Dev 7, If 1, Class=Wireless, Driver=btusb, 12M |__ Port 8: Dev 7, If 0, Class=Wireless, Driver=btusb, 12M MachineType: LENOVO 81C4 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-26-generic root=/dev/mapper/xubuntu--c930-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-26-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to groovy on 2020-10-30 (2 days ago) UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sambashare sudo video _MarkForUpload: False dmi.bios.date: 10/09/2018 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: 8GCN32WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA C930-13IKB dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvr8GCN32WW:bd10/09/2018:br1.32:efr1.32:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB: dmi.product.family: YOGA C930-13IKB dmi.product.name: 81C4 dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB dmi.product.version: Lenovo YOGA C930-13IKB dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (487 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: linux (not installed) Tags: groovy Uname: Linux 5.10.0-051000rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to groovy on 2020-10-30 (24 days ago) UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sambashare sudo video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (496 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 007: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 001 Device 006: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81C4 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-31-generic root=/dev/mapper/xubuntu--c930-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 RelatedPackageVersions: linux-restricted-modules-5.8.0-31-generic N/A linux-backports-modules-5.8.0-31-generic N/A linux-firmware1.190.1 Tags: groovy Uname: Linux 5.8.0-31-generic x86_64
[Kernel-packages] [Bug 1918427] Re: curtin: install flash-kernel in arm64 UEFI unexpected
Attached is a patch for curtin that works for me, though it could use some cleanup. It installs flash-kernel in the same place GRUB gets installed for EFI-based systems, which seems like the appropriate place. Before installint it, it diverts /usr/sbin/flash-kernel so that flash- kernel's postinst doesn't try (and fail) to flash a kernel that isn't yet installed. There's existing code in enable_update_initramfs() that will undo this diversion. I suspect we should refactor disable_update_initramfs() somehow instead of duplicating this code like I've done here. I've tested this w/ a locally-hacked squash image that has flash-kernel purged and a PPA kernel that allows grub-efi-arm64 to satisfy the bootloader Recommends. On an EFI-based system, flash-kernel never gets installed. On a Moonshot m400, flash-kernel gets installed as expected. Once curtin has been updated with a fix like this, and MAAS has been refreshed to include it, I think we should then be able to remove flash- kernel from the arm64 cloud images. ** Patch added: "curtin.patch" https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1918427/+attachment/5476956/+files/curtin.patch ** Changed in: curtin (Ubuntu) Status: New => Confirmed ** Changed in: cloud-images Status: Incomplete => Confirmed ** Changed in: curtin (Ubuntu) Status: Confirmed => Triaged ** Changed in: curtin (Ubuntu) Status: Triaged => 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/1918427 Title: curtin: install flash-kernel in arm64 UEFI unexpected Status in cloud-images: Confirmed Status in curtin package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Bug description: I used APM Mustang which flash-kernel supported in u-boot mode. But I used it with UEFI environment. It will cause fatal error when I used ARM64 ubuntu live server ISO to install system. In code[1], this will not install `flash-kernel` for APM Mustang because of UEFI. So that means code[2] will not disable `flash-kernel` in target system, only disable `update-initramfs`. When curtin execute to `install_kernel` stage, code[3,4] will not install `flash-kernel` either. But in code[5], it will install `linux-generic`. `linux-generic` has a long dependency tree and it will get `flash-kernel` in Recommended field. Apt by default will install Recommended package before kernel is installed.[6] So it will still execute `zz-flash-kernel` and `flash-kernel` when installing kernel. But system didn't create any `initrd.img` ever because curtin disable `update-initramfs` in code[2]. This will cause that `flash-kernel` cannot find `initrd.img.` and fail when installing it. This issue didn't effect all ARM64 UEFI platform because `flash-kernel` didn't support them and skip.[7] I'm not sure which is best solution for this. But I think we should apply PR-27 in `flash-kernel`[8] for enhancement and fix curtin process with this patch both. If we only apply PR-27, it should work fine as well because it will be skipped when detecting UEFI and install `flash-kernel` before `disable_update_initranfs` in ARM platform without UEFI.[9] [Patch-1,2,3] might have side effect. Picking one patch for curtin should be enough. But I need your advice for this to determine which one is better for curtin. There are two categories 1. avoid installing flash-kernel if no need, [Patch1,2] 2. always install flash-kernel in arm/arm64 and make sure it be installed before code[2] [Patch3] (I will attach patch in reply.) Thanks a lot Regards, Date [1] https://github.com/canonical/curtin/blob/master/curtin/deps/__init__.py#L57-L58 [2] https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L1693-L1699 [3] https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L365-L370 [4] https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L311-L327 [5] https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L372-L374 [6] https://github.com/Debian/apt/blob/master/apt-pkg/init.cc#L132 [7] https://salsa.debian.org/installer-team/flash-kernel/-/blob/master/functions#L787 [8] https://salsa.debian.org/installer-team/flash-kernel/-/merge_requests/27 [9] curtin will insert `flash-kernel` into `REQUIRED_EXECUTABLES` when system is arm/arm64 without UEFI. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1918427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1664072] Re: TCP: wlp1s0: Driver has suspect GRO implementation, TCP performance may be compromised.
** Changed in: linux (Debian) 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/1664072 Title: TCP: wlp1s0: Driver has suspect GRO implementation, TCP performance may be compromised. Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux package in Debian: Fix Released Bug description: dmesg: [ 7578.057461] TCP: wlp1s0: Driver has suspect GRO implementation, TCP performance may be compromised. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.9.0-15-generic 4.9.0-15.16 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2378 F...m pulseaudio /dev/snd/controlC0: caravena 2378 F pulseaudio CurrentDesktop: GNOME Date: Sun Feb 12 19:34:40 2017 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (567 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-15-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.9.0-15-generic N/A linux-backports-modules-4.9.0-15-generic N/A linux-firmware1.162 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2016-10-29 (106 days ago) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1664072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1918427] Re: curtin: install flash-kernel in arm64 UEFI unexpected
On Fri, Mar 12, 2021 at 10:45 PM Date Huang <1918...@bugs.launchpad.net> wrote: > > After reading log in #14, and some code from cloud-init and maas > I still cannot find any code that will let cloud-init try to install > flash-kernel wtih zfsutils-linux. > and it seems the error because squashfs didn't have any kernel installed. > So `linux-version` cannot find any kernel version to pass to flash-kernel to > process postinst script. > `Can't find /boot/vmlinuz- (see /tmp/flash-kernel-no-kernel-error.log)` > $kvers is empty. I added some debugging and found that this is what causes flash-kernel to be installed: https://git.launchpad.net/curtin/tree/curtin/deps/__init__.py?h=21.2#n57 I'm not sure what the point of that is - it probably should be removed. > and as I know, squashfs only for temp utils? > It will create an environment for curtin to install real system into disk > Am I correct? Yes, the failure in comment #14 is occurring in what we call the "ephemeral image", which only exists in memory to install an OS to the disk. Though the same image is also what is written to the disk. > Do you have any custom cloud-init config for xgene? No -dann -- 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/1918427 Title: curtin: install flash-kernel in arm64 UEFI unexpected Status in cloud-images: Incomplete Status in curtin package in Ubuntu: New Status in linux package in Ubuntu: In Progress Bug description: I used APM Mustang which flash-kernel supported in u-boot mode. But I used it with UEFI environment. It will cause fatal error when I used ARM64 ubuntu live server ISO to install system. In code[1], this will not install `flash-kernel` for APM Mustang because of UEFI. So that means code[2] will not disable `flash-kernel` in target system, only disable `update-initramfs`. When curtin execute to `install_kernel` stage, code[3,4] will not install `flash-kernel` either. But in code[5], it will install `linux-generic`. `linux-generic` has a long dependency tree and it will get `flash-kernel` in Recommended field. Apt by default will install Recommended package before kernel is installed.[6] So it will still execute `zz-flash-kernel` and `flash-kernel` when installing kernel. But system didn't create any `initrd.img` ever because curtin disable `update-initramfs` in code[2]. This will cause that `flash-kernel` cannot find `initrd.img.` and fail when installing it. This issue didn't effect all ARM64 UEFI platform because `flash-kernel` didn't support them and skip.[7] I'm not sure which is best solution for this. But I think we should apply PR-27 in `flash-kernel`[8] for enhancement and fix curtin process with this patch both. If we only apply PR-27, it should work fine as well because it will be skipped when detecting UEFI and install `flash-kernel` before `disable_update_initranfs` in ARM platform without UEFI.[9] [Patch-1,2,3] might have side effect. Picking one patch for curtin should be enough. But I need your advice for this to determine which one is better for curtin. There are two categories 1. avoid installing flash-kernel if no need, [Patch1,2] 2. always install flash-kernel in arm/arm64 and make sure it be installed before code[2] [Patch3] (I will attach patch in reply.) Thanks a lot Regards, Date [1] https://github.com/canonical/curtin/blob/master/curtin/deps/__init__.py#L57-L58 [2] https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L1693-L1699 [3] https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L365-L370 [4] https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L311-L327 [5] https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L372-L374 [6] https://github.com/Debian/apt/blob/master/apt-pkg/init.cc#L132 [7] https://salsa.debian.org/installer-team/flash-kernel/-/blob/master/functions#L787 [8] https://salsa.debian.org/installer-team/flash-kernel/-/merge_requests/27 [9] curtin will insert `flash-kernel` into `REQUIRED_EXECUTABLES` when system is arm/arm64 without UEFI. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1918427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912509] Re: usci_acpi USBC000:00: PPM init failed (-110)
Thanks for the reply. -- 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/1912509 Title: usci_acpi USBC000:00: PPM init failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: When booting with kernel 5.8.0-38-generic on my Asus Tuf 15 with 2 NVMe drives I get: usci_acpi USBC000:00: PPM init failed (-110) and the laptop freezes. kernel 5.4.0-26-generic usually boots (but get an occasional freeze). Since I cannot boot in the 5.8 kernel I cannot file the bug with that kernel running. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vincent1381 F pulseaudio /dev/snd/controlC0: vincent1381 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 20 17:28:23 2021 InstallationDate: Installed on 2021-01-20 (0 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 003: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F15 FX506LI_FX506LI ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=74589408-5655-4728-b040-86c06177a989 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX506LI.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX506LI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX506LI.307:bd12/17/2020:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF15FX506LI_FX506LI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX506LI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ASUS TUF Gaming F15 dmi.product.name: ASUS TUF Gaming F15 FX506LI_FX506LI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912509/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917194] Re: [Dell G5 5590] lspci freezes computer on Ubuntu 20.04
OK, so how about if you install the kernel version 5.8.0-43 in your system? In order to do that, I suggest you to boot using the Live CD and use chroot - there are goos instructions here : https://askubuntu.com/a/28100 The only thing to change is step 6: please run "sudo apt-get install linux-image-5.8.0-43-generic linux-modules-extra-5.8.0-43-generic". After that, try to boot your regular system using the kernel that seems to work for you, from the Live CD experience. Thanks, Guilherme -- 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/1917194 Title: [Dell G5 5590] lspci freezes computer on Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 18.04 to 20.04 my computer started to freeze when running lspci. I ended up noticing that it happened when trying to query device '1f:00.0' a USB port. After some kernel and bios updates the problem got worse. Now the computer freezes ~5 seconds after booting up. I tried: 1) Running in recovery mode, also freezes 2) Running an older kernel version (5.4.0-66-generic), also freezes 3) Removing nvidia drivers (just in case), also freezes 4) Running all combinations nodemodeset, acpi=off an nouveau blacklisting 5) Updating all drivers The computer freezes for ever, I can't switch TTYs, move the mouse, anything, the only way to leave was to force shutdown. On the last cases after switching to a tty I could see this messages before the freeze ocurred: kernel: xhci_hcd :1f:00.0: PCI post-resume error -19! kernel: xhci_hcd :1f:00.0: HC died; cleaning up Running Ubuntu 20.04 from a USB sticks works fine, as well as doing a fresh install. All logs were obtained by chrooting to the faulty partition from a fresh install, if there are any more logs that would be helpful, let me know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919252] [NEW] zfs-dkms on Focal still allow building on Linux kernel version 5.10+
Public bug reported: Due to a mistake in the BUILD_EXCLUSIVE_KERNEL regex in dkms.conf, dkms will still consider zfs-dkms to be buildable on kernel version 5.10+. This can happen if one installs a mainline kernel from the mainline PPA for one reason or another [1]. The following patch to dkms.conf should fix the issue: --- ./dkms.conf.orig2021-03-16 04:15:55.077568974 +0700 +++ /usr/src/zfs-0.8.3/dkms.conf2021-03-16 04:17:16.598219797 +0700 @@ -1,6 +1,6 @@ PACKAGE_NAME="zfs" PACKAGE_VERSION="0.8.3" -BUILD_EXCLUSIVE_KERNEL="^(4.[0-9]+|5.[01234])." +BUILD_EXCLUSIVE_KERNEL='^(4.[0-9]+|5.[01234])\.' PACKAGE_CONFIG="/etc/sysconfig/zfs" PRE_BUILD="configure --prefix=/usr Although it's not convenient for me at the moment to create a debdiff. Related: LP: #1902701 [1] For me it's to get a complete fix for LP: #1887190, as Focal's HWE kernel doesn't seem to work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zfs-dkms 0.8.3-1ubuntu12.6 Uname: Linux 5.11.6-051106-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Mar 16 04:26:08 2021 InstallationDate: Installed on 2021-03-15 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=th_TH.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1919252 Title: zfs-dkms on Focal still allow building on Linux kernel version 5.10+ Status in zfs-linux package in Ubuntu: New Bug description: Due to a mistake in the BUILD_EXCLUSIVE_KERNEL regex in dkms.conf, dkms will still consider zfs-dkms to be buildable on kernel version 5.10+. This can happen if one installs a mainline kernel from the mainline PPA for one reason or another [1]. The following patch to dkms.conf should fix the issue: --- ./dkms.conf.orig 2021-03-16 04:15:55.077568974 +0700 +++ /usr/src/zfs-0.8.3/dkms.conf 2021-03-16 04:17:16.598219797 +0700 @@ -1,6 +1,6 @@ PACKAGE_NAME="zfs" PACKAGE_VERSION="0.8.3" -BUILD_EXCLUSIVE_KERNEL="^(4.[0-9]+|5.[01234])." +BUILD_EXCLUSIVE_KERNEL='^(4.[0-9]+|5.[01234])\.' PACKAGE_CONFIG="/etc/sysconfig/zfs" PRE_BUILD="configure --prefix=/usr Although it's not convenient for me at the moment to create a debdiff. Related: LP: #1902701 [1] For me it's to get a complete fix for LP: #1887190, as Focal's HWE kernel doesn't seem to work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zfs-dkms 0.8.3-1ubuntu12.6 Uname: Linux 5.11.6-051106-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Mar 16 04:26:08 2021 InstallationDate: Installed on 2021-03-15 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=th_TH.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1919252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
It is extremely unlikely that this would cause problems, it would have to match
exactly another bus command interpreted differently by another device, and we
all have almost the same laptop.
However, here is the same command improved to take into account your remarks,
and thus send the commands only to the numpad:
sudo apt-get install -y i2c-tools;for f in `sudo i2cdetect -l | grep
DesignWare | cut -f 1`; do sudo i2ctransfer -f -y ${f:4} w13@0x15 0x05
0x00 0x3d 0x03 0x06 0x00 0x07 0x00 0x0d 0x14 0x03 0x01 0xad; done
--
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/1810183
Title:
numpad on touchpad doesn't work in ASUS Zenbook 14
Status in Linux:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside
windows 10.
The numeric keypads are within the touchpad and are supposed to be turned on
by a button on the touchpad. This works well in Windows but doesn't work in
Ubuntu.
I have tried to search for any related problems/solutions online but I
haven't been able to.
I will appreciate any suggestion or help.
Thanks,
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-30 (4 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
Package: linux (not installed)
Tags: cosmic
Uname: Linux 4.19.11-041911-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-30 (4 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
Package: linux (not installed)
Tags: cosmic
Uname: Linux 4.18.10-041810-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
At this point I would like to point out that i2ctransfer can, as stated in the manpages, cause serious damage to your i2c devices. Again, I'm not an expert at this and please correct me, if I'm wrong, but trying all bus addresses seems kind of risky to me. Instead, you can try to use the following: sudo i2cdetect -l This will print out a list of all available i2c bus addresses. In my case one of the lines is: i2c-0 i2c Synopsys DesignWare I2C adapter This is the touchpad and you should see something similar. After that you can try the original command with the correct address. With this knowledge one should be able to use the python script, which was linked earlier in this bug report and use a python library to incorporate the command. However, I won't follow that approach and instead, I will try to keep on working on a driver. If anyone has experience in this, I would greatly appreciate any help or advice. -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919245] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1919245 Title: Touchpad does not work at all Status in linux package in Ubuntu: Confirmed Bug description: I just installed ubuntu, but the touchpad doesn't work at all, it didn't work since the installation process and it's not detected. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-45-generic 5.8.0-45.51 ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alessio 39892 F pulseaudio /dev/snd/controlC0: alessio 39892 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Mar 15 21:26:07 2021 InstallationDate: Installed on 2021-03-15 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 81YQ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=UUID=403466ca-3551-431b-bcd9-d06dbcfff352 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-45-generic N/A linux-backports-modules-5.8.0-45-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2020 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN36WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Ideapad 5-15ARE05 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnLENOVO:bvrE7CN36WW:bd11/23/2020:br1.36:efr1.36:svnLENOVO:pn81YQ:pvrIdeapad5-15ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeapad5-15ARE05: dmi.product.family: IDEAPAD dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IDEAPAD dmi.product.version: Ideapad 5-15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919245] [NEW] Touchpad does not work at all
Public bug reported: I just installed ubuntu, but the touchpad doesn't work at all, it didn't work since the installation process and it's not detected. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-45-generic 5.8.0-45.51 ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alessio 39892 F pulseaudio /dev/snd/controlC0: alessio 39892 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Mar 15 21:26:07 2021 InstallationDate: Installed on 2021-03-15 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 81YQ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=UUID=403466ca-3551-431b-bcd9-d06dbcfff352 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-45-generic N/A linux-backports-modules-5.8.0-45-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2020 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN36WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Ideapad 5-15ARE05 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnLENOVO:bvrE7CN36WW:bd11/23/2020:br1.36:efr1.36:svnLENOVO:pn81YQ:pvrIdeapad5-15ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeapad5-15ARE05: dmi.product.family: IDEAPAD dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IDEAPAD dmi.product.version: Ideapad 5-15ARE05 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug groovy -- 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/1919245 Title: Touchpad does not work at all Status in linux package in Ubuntu: Confirmed Bug description: I just installed ubuntu, but the touchpad doesn't work at all, it didn't work since the installation process and it's not detected. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-45-generic 5.8.0-45.51 ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alessio 39892 F pulseaudio /dev/snd/controlC0: alessio 39892 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Mar 15 21:26:07 2021 InstallationDate: Installed on 2021-03-15 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 81YQ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=UUID=403466ca-3551-431b-bcd9-d06dbcfff352 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-45-generic N/A linux-backports-modules-5.8.0-45-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2020 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN36WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Ideapad 5-15ARE05 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnLENOVO:bvrE7CN36WW:bd11/23/2020:br1.36:efr1.36:svnLENOVO:pn81YQ:pvrIdeapad5-15ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeapad5-15ARE05: dmi.product.family: IDEAPAD dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IDEAPAD dmi.product.version: Ideapad 5-15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
It is normal to see these errors, this command sends the instruction to turn on the digital pad to all bus number. However, if this command did not turn on the numpad, it means that none of the bus number are compatible, you should have the same problem manually. -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
I used this command :
for f in /dev/i2c-*; do sudo i2ctransfer -f -y ${f:9} w13@0x15 0x05 0x00 0x3d
0x03 0x06 0x00 0x07 0x00 0x0d 0x14 0x03 0x01 0xad; done
And I get theses errors :
Error: Adapter does not have I2C transfers capability
Error: Adapter does not have I2C transfers capability
Error: Adapter does not have I2C transfers capability
Error: Sending messages failed: Input/output error
Error: Sending messages failed: Input/output error
Error: Sending messages failed: Remote I/O error
I've tried to replace f by 1 to 6 to find what is the unique command
that is working for me... it seems I don't understand how to do that.
Can somebody explain me ? I just want to find the right command for my
computer to help all the people who have the same computer to illuminate
it. Just for the eyes actually but so nice !
--
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/1810183
Title:
numpad on touchpad doesn't work in ASUS Zenbook 14
Status in Linux:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside
windows 10.
The numeric keypads are within the touchpad and are supposed to be turned on
by a button on the touchpad. This works well in Windows but doesn't work in
Ubuntu.
I have tried to search for any related problems/solutions online but I
haven't been able to.
I will appreciate any suggestion or help.
Thanks,
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-30 (4 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
Package: linux (not installed)
Tags: cosmic
Uname: Linux 4.19.11-041911-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-30 (4 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
Package: linux (not installed)
Tags: cosmic
Uname: Linux 4.18.10-041810-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909814] Re: Keyboard not working
I brought my laptop back to the store... :-( -- 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/1909814 Title: Keyboard not working Status in linux package in Ubuntu: Confirmed Bug description: Hello, Brand new laptop (Medion), keyboard is only working with the grub menu. Mouse is now working since 20.10 have been installed. Only the luminosity key are working on the keyboard. External usb keyboard works fine. I tried to install with usb keyboard disconnected but doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: did4364 F pulseaudio /dev/snd/pcmC0D0p: did4364 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 1 16:24:12 2021 InstallationDate: Installed on 2021-01-01 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MEDION S15450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 209 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring: dmi.product.family: Akoya dmi.product.name: S15450 dmi.product.sku: ML-230008 30030452 dmi.product.version: Default string dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
Waouh ! It works ! I never thought it will be possible on Linux since there is no Asus support. I don't think there is special command to display the numbers. I think that when the command is sent to illuminate the pad, a program detect where the user tap on the numpad to display the number. The solution is near. Congratulation to you ! I'm very happy ! -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909814] Re: Keyboard not working
Welcome to the club :) So far, no news. I tried everything possible avail. on the web with no success. I tried several different Linux flavor with same results. Ex: With Mint, the mouse was not even working, at least mouse is working with Ubuntu 20.10. I update 20.10 at every update hoping that something will change but no success. I guess we have to wait. I suggest that we post any positive update here to keep us informed. -- 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/1909814 Title: Keyboard not working Status in linux package in Ubuntu: Confirmed Bug description: Hello, Brand new laptop (Medion), keyboard is only working with the grub menu. Mouse is now working since 20.10 have been installed. Only the luminosity key are working on the keyboard. External usb keyboard works fine. I tried to install with usb keyboard disconnected but doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: did4364 F pulseaudio /dev/snd/pcmC0D0p: did4364 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 1 16:24:12 2021 InstallationDate: Installed on 2021-01-01 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MEDION S15450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 209 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring: dmi.product.family: Akoya dmi.product.name: S15450 dmi.product.sku: ML-230008 30030452 dmi.product.version: Default string dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893624] Re: Ryzen 4800u, kernel 5.8.5 boot errors (AMD-Vi, ACPI, HDCP, Bluetooth)
I don't run Ubuntu myself, but Linux is Linux: ``` [ 14.934677] ACPI Error: No handler for Region [ECSI] (24032c9e) [EmbeddedControl] (20201113/evregion-128) [ 14.937851] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20201113/exfldio-261) [ 14.941080] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20201113/psparse-529) [ 14.944321] ACPI Error: Aborting method \_SB.UBTC._DSM due to previous error (AE_NOT_EXIST) (20201113/psparse-529) [ 14.948265] ucsi_acpi USBC000:00: ucsi_acpi_dsm: failed to evaluate _DSM 2 [ 17.200797] amdgpu :04:00.0: amdgpu: Unsupported power profile mode 0 on RENOIR ``` kernel: 5.11.5 -- 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/1893624 Title: Ryzen 4800u, kernel 5.8.5 boot errors (AMD-Vi, ACPI, HDCP, Bluetooth) Status in linux package in Ubuntu: Invalid Bug description: Lenovo Ideapad S540 13ARE (AMD Ryzen 4800U). Ubuntu Budgie 20.04.1 LTS, updated kernel to 5.8.5. Secure Boot disabled. Clean install with entire disk (Windows came preinstalled) wiped out. Most things work just fine. If not for the errors shown during boot, I would not have noticed the issues.Video (native resolutions works), audio, wifi, suspend, the quick buttons (brightness, volume etc) all work fine. However during boot, errors are shortly shown: asterix@Idefix:~$ sudo dmesg -l err [3.204455] pci :00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter. [4.901524] I2C multi instantiate pseudo device driver INT3515:00: IRQ index 1 not found [4.919327] snd_pci_acp3x :03:00.5: Invalid ACP audio mode : 0 [4.939476] ACPI Error: No handler for Region [ECSI] (bf2d92b9) [EmbeddedControl] (20200528/evregion-127) [4.939724] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20200528/exfldio-261) [4.939929] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20200528/psparse-529) [4.940212] ACPI Error: Aborting method \_SB.UBTC._DSM due to previous error (AE_NOT_EXIST) (20200528/psparse-529) [4.940517] ucsi_acpi USBC000:00: ucsi_acpi_dsm: failed to evaluate _DSM 2 [5.235689] acp_pdm_mach acp_pdm_mach.0: snd_soc_register_card(acp) failed: -517 [6.273068] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find connector for link! [6.273591] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find connector for link! [6.273748] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find connector for link! [7.036019] [drm:mod_hdcp_add_display_to_topology [amdgpu]] *ERROR* Failed to add display topology, DTM TA is not initialized. [7.891436] Bluetooth: hci0: Failed to send Intel_Write_DDC (-22)``` lspci-vnvn.log: https://pastebin.com/Kygie8nu What can I do to help solve this? Note I am not a developer and a Linux novice. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-30 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: linux (not installed) Tags: focal Uname: Linux 5.8.5-050805-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
For those who want to test if it works, just enter the following
command:
sudo apt-get install -y i2c-tools;for f in /dev/i2c-*; do sudo
i2ctransfer -f -y ${f:9} w13@0x15 0x05 0x00 0x3d 0x03 0x06 0x00 0x07
0x00 0x0d 0x14 0x03 0x01 0xad; done
--
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/1810183
Title:
numpad on touchpad doesn't work in ASUS Zenbook 14
Status in Linux:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside
windows 10.
The numeric keypads are within the touchpad and are supposed to be turned on
by a button on the touchpad. This works well in Windows but doesn't work in
Ubuntu.
I have tried to search for any related problems/solutions online but I
haven't been able to.
I will appreciate any suggestion or help.
Thanks,
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-30 (4 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
Package: linux (not installed)
Tags: cosmic
Uname: Linux 4.19.11-041911-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-30 (4 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
Package: linux (not installed)
Tags: cosmic
Uname: Linux 4.18.10-041810-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
worked changing address to 1: light on: sudo i2ctransfer -f -y 1 w13@0x15 0x05 0x00 0x3d 0x03 0x06 0x00 0x07 0x00 0x0d 0x14 0x03 0x01 0xad light off: sudo i2ctransfer -f -y 1 w13@0x15 0x05 0x00 0x3d 0x03 0x06 0x00 0x07 0x00 0x0d 0x14 0x03 0x00 0xad nothing else but big progress! :) Thanks Il giorno lun 15 mar 2021 alle ore 18:56 VanVan <1810...@bugs.launchpad.net> ha scritto: > I can confirm that it's working for me by changing the bus number from 0 > to 2. > > i2ctransfer -f -y 2 w13@0x15 0x05 0x00 0x3d 0x03 0x06 0x00 0x07 0x00 > 0x0d 0x14 0x03 0x01 0xad > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1823320). > https://bugs.launchpad.net/bugs/1810183 > > Title: > numpad on touchpad doesn't work in ASUS Zenbook 14 > > Status in Linux: > New > Status in linux package in Ubuntu: > Confirmed > > Bug description: > I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 > alongside windows 10. > The numeric keypads are within the touchpad and are supposed to be > turned on by a button on the touchpad. This works well in Windows but > doesn't work in Ubuntu. > I have tried to search for any related problems/solutions online but I > haven't been able to. > I will appreciate any suggestion or help. > Thanks, > --- > ProblemType: Bug > ApportVersion: 2.20.10-0ubuntu13.1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > DistroRelease: Ubuntu 18.10 > InstallationDate: Installed on 2018-12-30 (4 days ago) > InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.3) > Package: linux (not installed) > Tags: cosmic > Uname: Linux 4.19.11-041911-generic x86_64 > UnreportableReason: The running kernel is not an Ubuntu kernel > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > --- > ProblemType: Bug > ApportVersion: 2.20.10-0ubuntu13.1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > DistroRelease: Ubuntu 18.10 > InstallationDate: Installed on 2018-12-30 (4 days ago) > InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.3) > Package: linux (not installed) > Tags: cosmic > Uname: Linux 4.18.10-041810-generic x86_64 > UnreportableReason: The running kernel is not an Ubuntu kernel > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > > To manage notifications about this bug go to: > https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions > -- -- Andrea Mattana -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
I can confirm that it's working for me by changing the bus number from 0 to 2. i2ctransfer -f -y 2 w13@0x15 0x05 0x00 0x3d 0x03 0x06 0x00 0x07 0x00 0x0d 0x14 0x03 0x01 0xad -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919042] Re: Touchpad not working on HP Pavilion Laptop 14-dv0xxx
Hi, I updated to the latest focal kernel as mentioned. I rebooted but still the touchpad is not functioning. My system is actually having multi boot with Ubuntu and Windows and I am just trying out my hand using a Linux distro. So, could you please elaborate more on the steps that I need to try out. -- 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/1919042 Title: Touchpad not working on HP Pavilion Laptop 14-dv0xxx Status in linux package in Ubuntu: Incomplete Bug description: HP Imagepad not detected in 'HP Pavilion 14-DV00054TU' after installing Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hp 1523 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 14 00:45:36 2021 InstallationDate: Installed on 2021-03-08 (5 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Pavilion Laptop 14-dv0xxx ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=84f5a50d-8a8e-4afc-8e8c-3245f566346a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2021 dmi.bios.vendor: Insyde dmi.bios.version: F.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 87C9 dmi.board.vendor: HP dmi.board.version: 34.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.11:bd01/15/2021:svnHP:pnHPPavilionLaptop14-dv0xxx:pvrType1ProductConfigId:rvnHP:rn87C9:rvr34.27:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 14-dv0xxx dmi.product.sku: 2N1L0PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919042/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909814] Re: Keyboard not working
I have the same issue with a recently bought medion laptop. Function keys like sound and backlight work. However typing does not work. Somebody has an update on this issue? -- 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/1909814 Title: Keyboard not working Status in linux package in Ubuntu: Confirmed Bug description: Hello, Brand new laptop (Medion), keyboard is only working with the grub menu. Mouse is now working since 20.10 have been installed. Only the luminosity key are working on the keyboard. External usb keyboard works fine. I tried to install with usb keyboard disconnected but doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: did4364 F pulseaudio /dev/snd/pcmC0D0p: did4364 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 1 16:24:12 2021 InstallationDate: Installed on 2021-01-01 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MEDION S15450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 209 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring: dmi.product.family: Akoya dmi.product.name: S15450 dmi.product.sku: ML-230008 30030452 dmi.product.version: Default string dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919173] Re: PC freeze under 5.8.0-45.51
Thanks for the report Hassan! Can you please add "ignore_loglevel" to you GRUB configuration, run "sudo update-grub" and try to boot with 5.8.0-45? We'll need to get some information from kernel log to understand what's possibly going wrong. Thanks, Guilherme -- 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/1919173 Title: PC freeze under 5.8.0-45.51 Status in linux package in Ubuntu: Confirmed Bug description: Can't boot under kernel 5.8.0-45.51. Complet freeze ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-45-generic 5.8.0-45.51 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: waver 3942 F pulseaudio /dev/snd/pcmC0D0p: waver 3942 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Mar 15 16:55:21 2021 HibernationDevice: RESUME=UUID=2d0d3638-45f8-42fd-984d-a1da2aecf660 InstallationDate: Installed on 2018-01-01 (1168 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221) MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-44-generic root=UUID=6108dfff-7ad7-497e-950e-aad003c33b82 ro ipv6.disable=1 net.ifnames=0 fsck.mode=force fsck.repair=yes drm.edid_firmware=edid/G2420HDBL.bin quiet splash nvme_core.default_ps_max_latency_us=5500 nvidia-drm.modeset=1 pci=noaer vt.handoff=7 RebootRequiredPkgs: linux-image-5.8.0-45-generic linux-base RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2019-10-19 (512 days ago) dmi.bios.date: 07/12/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z370-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2401:bd07/12/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ370-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917674] Re: [amdgpu] kernel crash when resuming from automatic suspension to RAM
Nevermind, I was running 5.8, not 5.0.0. I forgot to select 5.0.0 in the boot menu. -- 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/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM Status in linux package in Ubuntu: Incomplete Bug description: Automatic suspension causes the system to freeze on resume. This doesn't happen if I suspend it manually by opening the system menu and pressing the suspend button. Suspension works flawlessly when it is triggered manually. When the system resumes from automatic suspension, the lock screen is visible but does not respond. It's frozen. A notification says something like "system will suspend shortly due to inactivity". It never goes away. The keyboard responds during this (at least for a while). The CAPS LOCK LED turns on and off as I press it (with no delay). Sometimes I can even switch to another TTY and kill the X server, which is why I'm reporting it against gnome-shell. When switching TTY is impossible, I use the "REISUB" combination to shut down. Either way, I always lose the running session. This is reproducible about 60% of the time. Eventually I ended up disabling it and relying only on manual suspension. # Additional information: 1) Ubuntu 20.04.2 LTS / Release: 20.04 2) gnome-shell 3.36.4-1ubuntu1~20.04.2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 3 16:56:01 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-01-31 (31 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
same bug in ubuntu 20.10... last post seems to be a progress.. Thanks -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917674] Re: [amdgpu] kernel crash when resuming from automatic suspension to RAM
I was able to reproduce this with kernel 5.0.0 too. Isn't it possible that this is not caused by the kernel? I don't think I had this issue back then - it's something more recent. ** Attachment added: "Logs from a previous session that crashed with kernel 5.0.0" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+attachment/5476815/+files/prevboot.txt -- 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/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM Status in linux package in Ubuntu: Incomplete Bug description: Automatic suspension causes the system to freeze on resume. This doesn't happen if I suspend it manually by opening the system menu and pressing the suspend button. Suspension works flawlessly when it is triggered manually. When the system resumes from automatic suspension, the lock screen is visible but does not respond. It's frozen. A notification says something like "system will suspend shortly due to inactivity". It never goes away. The keyboard responds during this (at least for a while). The CAPS LOCK LED turns on and off as I press it (with no delay). Sometimes I can even switch to another TTY and kill the X server, which is why I'm reporting it against gnome-shell. When switching TTY is impossible, I use the "REISUB" combination to shut down. Either way, I always lose the running session. This is reproducible about 60% of the time. Eventually I ended up disabling it and relying only on manual suspension. # Additional information: 1) Ubuntu 20.04.2 LTS / Release: 20.04 2) gnome-shell 3.36.4-1ubuntu1~20.04.2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 3 16:56:01 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-01-31 (31 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919174] Re: nvidia drivers will not load
I've added an excerpt from the apt log. There were errors rebuilding the kernel modules during the kernel upgrade ** Attachment added: "apt term.log excerpt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1919174/+attachment/5476814/+files/term.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1919174 Title: nvidia drivers will not load Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: nvidia drivers will no longer load after upgrade to kernel 5.8.0-45. This is an OPTIMUS laptop. Before, Intel and nvidia GPUs would be active; now, nvidia drivers will not load and external monitors will not be detected. Everything works correctly if I switch to nouveau. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-460 460.39-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Mar 15 15:50:27 2021 InstallationDate: Installed on 2021-03-08 (7 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) SourcePackage: nvidia-graphics-drivers-460 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1919174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919173] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1919173 Title: PC freeze under 5.8.0-45.51 Status in linux package in Ubuntu: Confirmed Bug description: Can't boot under kernel 5.8.0-45.51. Complet freeze ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-45-generic 5.8.0-45.51 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: waver 3942 F pulseaudio /dev/snd/pcmC0D0p: waver 3942 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Mar 15 16:55:21 2021 HibernationDevice: RESUME=UUID=2d0d3638-45f8-42fd-984d-a1da2aecf660 InstallationDate: Installed on 2018-01-01 (1168 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221) MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-44-generic root=UUID=6108dfff-7ad7-497e-950e-aad003c33b82 ro ipv6.disable=1 net.ifnames=0 fsck.mode=force fsck.repair=yes drm.edid_firmware=edid/G2420HDBL.bin quiet splash nvme_core.default_ps_max_latency_us=5500 nvidia-drm.modeset=1 pci=noaer vt.handoff=7 RebootRequiredPkgs: linux-image-5.8.0-45-generic linux-base RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2019-10-19 (512 days ago) dmi.bios.date: 07/12/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z370-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2401:bd07/12/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ370-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919164] Re: can't use mSata Adapter (with and without uas quirks)
** Description changed: I tried to access an mSata disk with Ubuntu 20.04 using the ASMedia AS2115 adapter. This did not work with - 5.4.0-26-generic (Lenovo T14s, AMD) - 5.8.0-44-generic (Lenovo T14s, AMD) + - 5.11.6-generic from Kernel PPA (Lenovo T14s, AMD, tested quirks only) - 5.8.0-44-lowlatency (Toshiba C70, Intel, tried USB 2.0 and USB 3.0 port) trying both uas and usb-quirks 174c:1153:u, ie. disabling uas The errors have been similar on all configurations. Logs are from the C70 with 5.8.0-44-lowlatency and the USB 3.0 port. I removed the modules uas and usb-storage in both cases and modprobed them again. -- 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/1919164 Title: can't use mSata Adapter (with and without uas quirks) Status in linux package in Ubuntu: Confirmed Bug description: I tried to access an mSata disk with Ubuntu 20.04 using the ASMedia AS2115 adapter. This did not work with - 5.4.0-26-generic (Lenovo T14s, AMD) - 5.8.0-44-generic (Lenovo T14s, AMD) - 5.11.6-generic from Kernel PPA (Lenovo T14s, AMD, tested quirks only) - 5.8.0-44-lowlatency (Toshiba C70, Intel, tried USB 2.0 and USB 3.0 port) trying both uas and usb-quirks 174c:1153:u, ie. disabling uas The errors have been similar on all configurations. Logs are from the C70 with 5.8.0-44-lowlatency and the USB 3.0 port. I removed the modules uas and usb-storage in both cases and modprobed them again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907421] Re: [UBUNTU 21.04] vfio: pass DMA availability information to userspace
Patch "vfio iommu: Add dma available capability" now landed as 6507174efc67 in focal-updates and is part of Ubuntu-5.4.0-67. Hence updating the 'affects focal' entry as Fix Released and with that closing the entire ticket. ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => 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/1907421 Title: [UBUNTU 21.04] vfio: pass DMA availability information to userspace Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: Description: vfio: pass DMA availability information to userspace Symptom: vfio-pci device on s390 enters error state Problem: Commit 492855939bdb added a limit to the number of concurrent DMA requests for a vfio container. However, lazy unmapping in s390 can in fact cause quite a large number of outstanding DMA requests to build up prior to being purged, potentially the entire guest DMA space. This results in unexpected errors seen in qemu such as 'VFIO_MAP_DMA failed: No space left on device' Solution: The solution requires a change to both kernel and qemu - For the kernel, add the ability to provide the number of allowable DMA requests via the VFIO_IOMMU_GET_INFO ioctl. Reproduction: Put a vfio-pci device on s390 under I/O load Upstream-ID: a717072007e8aedd3f951726d8cf55454860b30d 7d6e1329652ed971d1b6e0e7bea66fba5044e271 Need also to be integrated into 20.10 and 20.04. OK, just to clarify we don't need to fix bionic for this one, but rather focal (20.04) and groovy (20.10). Furthermore, for 20.04, 20.10 and 21.04 ONLY commit 7d6e1329652ed971d1b6e0e7bea66fba5044e271 is needed, the other was a pre-req that is already present. __ SRU Justification: [Impact] * In case a vfio-pci device on s390x is under I/O load, vfio-pci device may end up in error state. * The commit 492855939bdb added a limit to the number of concurrent DMA requests for a vfio container. * However, lazy unmapping in s390x can in fact cause quite a large number of outstanding DMA requests to build up prior to being purged - potentially the entire guest DMA space. * This results in unexpected errors seen in qemu such as 'VFIO_MAP_DMA failed: No space left on device'. * The solution requires a change to both kernel and qemu. * The kernel side of things is addressed by this SRU. * The fix adds the ability to provide the number of allowable DMA requests via VFIO_IOMMU_GET_INFO ioctl. * The actual fix comes with commit 7d6e1329652e, but another fix ccd59dce1a21 is needed to get it cleanly applied. [Fix] * ccd59dce1a21f473518bf273bdf5b182bab955b3 ccd59dce1a21 "vfio/type1: Refactor vfio_iommu_type1_ioctl()" * 7d6e1329652ed971d1b6e0e7bea66fba5044e271 7d6e1329652e "vfio iommu: Add dma available capability" [Test Case] * IBM Z or LinuxONE hardware with Ubuntu Server 20.10 installed. * PCIe adapters in place that provide vfio, like RoCE Express 2. * A KVM host needs to be setup and a KVM guest (use again 20.10) that uses vfio. * Generate I/O that flows through the vf and watch out for error like 'VFIO_MAP_DMA failed: No space left on device' in the log. [Regression Potential] * The first patch ccd59dce1a21 modifies the common code file drivers/vfio/vfio_iommu_type1.c quity significantly. * But the reason is not that it introduces a lot of new things, it's a refactoring patch. * Nevertheless if done in a bad way it can significantly harm the IO memory management of virtual function adapters. * In worst case it may break them entirely, instead of 'just' exeeding the entire DMA space. * Things could also go wrong while doing the mapping and unmapping of DMA, that may even have an impact beyond vf adapters - harming other DMA devices. * The handling of dirty pages is also touched and the ioctl itself - which is important to keep the control of the devices. * But as said before, it re-factoring work, it's upstream accepted since 5.9 and the provenance shows that many engineers had an eye on these changes. * The second patch 7d6e1329652e - that inclides the needed fix - comes with far less modifications. * It also tounches drivers/vfio/vfio_iommu_type1.c but in a way that it mainly add one new function (vfio_iommu_dma_avail_build_caps) and an add. if statement in vfio_iommu_type1_get_info. * That allows to provide the current allowable
[Kernel-packages] [Bug 1919173] [NEW] PC freeze under 5.8.0-45.51
Public bug reported: Can't boot under kernel 5.8.0-45.51. Complet freeze ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-45-generic 5.8.0-45.51 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: waver 3942 F pulseaudio /dev/snd/pcmC0D0p: waver 3942 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Mar 15 16:55:21 2021 HibernationDevice: RESUME=UUID=2d0d3638-45f8-42fd-984d-a1da2aecf660 InstallationDate: Installed on 2018-01-01 (1168 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221) MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-44-generic root=UUID=6108dfff-7ad7-497e-950e-aad003c33b82 ro ipv6.disable=1 net.ifnames=0 fsck.mode=force fsck.repair=yes drm.edid_firmware=edid/G2420HDBL.bin quiet splash nvme_core.default_ps_max_latency_us=5500 nvidia-drm.modeset=1 pci=noaer vt.handoff=7 RebootRequiredPkgs: linux-image-5.8.0-45-generic linux-base RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2019-10-19 (512 days ago) dmi.bios.date: 07/12/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z370-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2401:bd07/12/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ370-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1919173 Title: PC freeze under 5.8.0-45.51 Status in linux package in Ubuntu: New Bug description: Can't boot under kernel 5.8.0-45.51. Complet freeze ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-45-generic 5.8.0-45.51 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: waver 3942 F pulseaudio /dev/snd/pcmC0D0p: waver 3942 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Mar 15 16:55:21 2021 HibernationDevice: RESUME=UUID=2d0d3638-45f8-42fd-984d-a1da2aecf660 InstallationDate: Installed on 2018-01-01 (1168 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221) MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-44-generic root=UUID=6108dfff-7ad7-497e-950e-aad003c33b82 ro ipv6.disable=1 net.ifnames=0 fsck.mode=force fsck.repair=yes drm.edid_firmware=edid/G2420HDBL.bin quiet splash nvme_core.default_ps_max_latency_us=5500 nvidia-drm.modeset=1 pci=noaer vt.handoff=7 RebootRequiredPkgs: linux-image-5.8.0-45-generic linux-base RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2019-10-19 (512 days ago) dmi.bios.date: 07/12/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z370-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2401:bd07/12/2019:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ370-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.v
[Kernel-packages] [Bug 1919174] [NEW] nvidia drivers will not load
Public bug reported: nvidia drivers will no longer load after upgrade to kernel 5.8.0-45. This is an OPTIMUS laptop. Before, Intel and nvidia GPUs would be active; now, nvidia drivers will not load and external monitors will not be detected. Everything works correctly if I switch to nouveau. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-460 460.39-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Mar 15 15:50:27 2021 InstallationDate: Installed on 2021-03-08 (7 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) SourcePackage: nvidia-graphics-drivers-460 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1919174 Title: nvidia drivers will not load Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: nvidia drivers will no longer load after upgrade to kernel 5.8.0-45. This is an OPTIMUS laptop. Before, Intel and nvidia GPUs would be active; now, nvidia drivers will not load and external monitors will not be detected. Everything works correctly if I switch to nouveau. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-460 460.39-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Mar 15 15:50:27 2021 InstallationDate: Installed on 2021-03-08 (7 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) SourcePackage: nvidia-graphics-drivers-460 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1919174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911376] Re: [ssbs-0118] backport SSBS bug (arm64: cpufeature: Detect SSBS and advertise to userspace)
** Changed in: kunpeng920/ubuntu-18.04
Status: Fix Committed => Fix Released
** Changed in: kunpeng920
Status: Fix Committed => 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/1911376
Title:
[ssbs-0118] backport SSBS bug (arm64: cpufeature: Detect SSBS and
advertise to userspace)
Status in kunpeng920:
Fix Released
Status in kunpeng920 ubuntu-18.04 series:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Released
Bug description:
[Impact]
The SSBS patch in 4.14 stable kernel, and mainline kernel adds snippet
into arm64_cpufeatures but in bionic kernel, it is landed into
arm64_elf_hwcaps.
[Fix]
Move SSBS snippet from arm64_elf_hwcaps back to arm64_features
[Test]
No known tool for SSB attack. Regression test only.
[Regression Potential]
Regression might be on all arm64 platforms. Regression test on all arm64
platform we have is recommended.
=
[Bug Description]
ubuntu 18.04.1 fail to enable this SSBS function, this sys log will call
trace as follow:
[0.662089] Call trace:
[0.662870] setup_elf_hwcaps+0xb8/0xd4
[0.664023] setup_cpu_features+0x60/0xf8
[0.665216] smp_cpus_done+0x34/0xa8
[0.666547] smp_init+0x120/0x138
[0.667555] kernel_init_freeable+0xf4/0x260
[0.668860] kernel_init+0x18/0x110
[0.670025] ret_from_fork+0x10/0x18
[Steps to Reproduce]
1) boot this system
2) uname -a
Ubuntu 4.15.0-99.100-generic 4.15.18
[Actual Results]
boot error:
[0.662089] Call trace:
[0.662870] setup_elf_hwcaps+0xb8/0xd4
[0.664023] setup_cpu_features+0x60/0xf8
[0.665216] smp_cpus_done+0x34/0xa8
[0.666547] smp_init+0x120/0x138
[0.667555] kernel_init_freeable+0xf4/0x260
[0.668860] kernel_init+0x18/0x110
[0.670025] ret_from_fork+0x10/0x18
[Expected Results]
no error
[Reproducibility]
NA
[Additional information]
(Firmware version, kernel version, affected hardware, etc. if required):
arm64: cpufeature: Detect SSBS and advertise to userspace
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d71be2b6c0e19180b5f80a6d42039cc074a693a2
backport this following code into "static const struct
arm64_cpu_capabilities arm64_elf_hwcaps[]" which will be error.
1274 #ifdef CONFIG_ARM64_SSBD
1275 {
1276 .desc = "Speculative Store Bypassing Safe (SSBS)",
1277 .capability = ARM64_SSBS,
1278 .type = ARM64_CPUCAP_WEAK_LOCAL_CPU_FEATURE,
1279 .matches = has_cpuid_feature,
1280 .sys_reg = SYS_ID_AA64PFR1_EL1,
1281 .field_pos = ID_AA64PFR1_SSBS_SHIFT,
1282 .sign = FTR_UNSIGNED,
1283 .min_field_value = ID_AA64PFR1_SSBS_PSTATE_ONLY,
1284 .cpu_enable = cpu_enable_ssbs,
1285 },
[Resolution]
Can you backport aboving code into "static const struct
arm64_cpu_capabilities arm64_features[] = {"?
To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1911376/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1914919] Re: UC20 initrd misses modules to boot from USB disk
The initrd for UC20 is generated by ubuntu-core-initramfs. ** Also affects: ubuntu-core-initramfs Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1914919 Title: UC20 initrd misses modules to boot from USB disk Status in ubuntu-core-initramfs: New Status in linux-raspi package in Ubuntu: Invalid Bug description: Trying to use a default USB boot on a Raspberry Pi using either an USB3 UAS SSD enclosure or even a simple USB 2 stick fails (due to the missing console output it simply hangs indefinitely with a black screen https://bugs.launchpad.net/ubuntu/+source/linux- raspi/+bug/1914608). seemingly neither the usb_storage module nor uas, enclosure or required scsi drivers are included in the initrd, this makes using the UC20 images with a fast USB3 disk impossible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-core-initramfs/+bug/1914919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917528] Re: bcmwl-kernel-source fails to build on Linux 5.10
Yes, confirmed on my'12 cMP . . . after running an apt dist-upgrade, I was then able to use Add'l Driver app to install wifi drivers and wifi networks appeared in networkmanager applet?? Lubuntu hirsute edition. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1917528 Title: bcmwl-kernel-source fails to build on Linux 5.10 Status in bcmwl package in Ubuntu: Fix Released Bug description: OS: Kubuntu 21.04 Installing bcmwl-kernel-source on Linux 5.10 kernel will fail. This didn't happen on Kubuntu 20.10. During the installation the messages are: Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.10.0-14-generic Building for architecture x86_64 Building initial module for 5.10.0-14-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Bad return status for module build on kernel: 5.10.0-14-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. dpkg: errore nell'elaborare il pacchetto bcmwl-kernel-source (--configure): il sottoprocesso installato pacchetto bcmwl-kernel-source script post-installation ha restituito lo stato di errore 10 Si sono verificati degli errori nell'elaborazione: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) Logs report: $ cat /var/crash/bcmwl-kernel-source.0.crash ProblemType: Package DKMSBuildLog: DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.10.0-14-generic (x86_64) Tue Mar 2 08:50:04 PM CET 2021 make: Entering directory '/usr/src/linux-headers-5.10.0-14-generic' CFG80211 API is prefered for this kernel version Using CFG80211 API CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_pci_probe’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:784:2: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 784 | if ((val & 0xff00) != 0) | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:786:3: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 786 | bar1_size = pci_resource_len(pdev, 2); | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: In function ‘wl_dev_ioctl’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:461:7: error: implicit declaration of function ‘get_fs’; did you mean ‘get_ds’? [-Werror=implicit-function-declaration] 461 | fs = get_fs(); | ^~ | get_ds /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:461:7: error: incompatible types when assigning to type ‘mm_segment_t’ from type ‘int’ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:2: error: implicit declaration of function ‘set_fs’; did you mean ‘sget_fc’? [-Werror=implicit-function-declaration] 462 | set_fs(get_ds()); | ^~ | sget_fc In file included from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:26: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:600:19: error: ‘KERNEL_DS’ undeclared (first use in this function); did you mean ‘KERNFS_NS’? 600 | #define get_ds() (KERNEL_DS) | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:9: note: in expansion of macro ‘get_ds’ 462 | set_fs(get_ds()); | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:600:19: note: each undeclared identifier is reported only once for each function it appears in 600 | #define get_ds() (KERNEL_DS) | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:9: note: in expansion of macro ‘get_ds’ 462 | set_fs(get_ds()); | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_ioctl’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:1662:6: error: implicit declaration of function ‘segment_eq’ [-Werror=implicit-function-declaration] 1662 | if (segment_eq(get_fs(), KERNEL_DS)) | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:1662:17: error: implicit declaration of function ‘get_fs’; did you mean ‘get_ds’? [-W
[Kernel-packages] [Bug 1919164] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: focal -- 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/1919164 Title: can't use mSata Adapter (with and without uas quirks) Status in linux package in Ubuntu: Confirmed Bug description: I tried to access an mSata disk with Ubuntu 20.04 using the ASMedia AS2115 adapter. This did not work with - 5.4.0-26-generic (Lenovo T14s, AMD) - 5.8.0-44-generic (Lenovo T14s, AMD) - 5.8.0-44-lowlatency (Toshiba C70, Intel, tried USB 2.0 and USB 3.0 port) trying both uas and usb-quirks 174c:1153:u, ie. disabling uas The errors have been similar on all configurations. Logs are from the C70 with 5.8.0-44-lowlatency and the USB 3.0 port. I removed the modules uas and usb-storage in both cases and modprobed them again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919051] Re: ch341 USB-Serial converter only receives, does not send
This issue appears to be in the kernel driver itself. I guess it is some type of regression. There was no difference using the mainline kernel or the default kernel inside another host with Alpine Linux distro (Linux alpine 5.10.16-0-lts #1-Alpine SMP Wed, 17 Feb 2021 08:17:06 UTC i586 Linux). The device still receives, but does not send. Please report this bug 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/1919051 Title: ch341 USB-Serial converter only receives, does not send Status in linux package in Ubuntu: Confirmed Bug description: This device works flawlessly on Windows XP with native driver, both as a physical machine or inside a VM. It appears on XP's device management as "USB 2.0" name. On Ubuntu, Shorting pins 2 and 3 of DB9 connector does not give back characters sent (no echo), nor typed strings are sent to other RS232 devices, despite of communication settings. Characters from remote devices are correctly received. Using a null modem cable to other RS232 terminal shows that the local terminal receives, but does not transmit. Its worth to mention: passing through the device to a guest virtual machine (KVM) running Windows XP makes it work correctly with XP driver inside the guest OS. Bringing back the device stops transmitting. Only receive works. Tested with the version below: NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal Kernel: Linux host 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Device ID: ID 4348:5523 WinChipHead USB->RS 232 adapter with Prolifec PL 2303 chipset Modinfo: filename: /lib/modules/5.4.0-66-generic/kernel/drivers/usb/serial/ch341.ko license:GPL v2 srcversion: 8F5F64E72BDA4E76E6F4F4D alias: usb:v4348p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7522d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5512d*dc*dsc*dp*ic*isc*ip*in* depends:usbserial retpoline: Y intree: Y name: ch341 vermagic: 5.4.0-66-generic SMP mod_unload sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:1E:07:0D:94:23:77:98:99:05:31:F3:76:E8:6B:76:12:7C:83:9E:05 sig_hashalgo: sha512 signature: 50:CE:79:92:87:EA:82:77:A9:25:A3:B7:F2:B3:ED:63:FE:85:EB:61: 7A:31:C5:9E:E5:78:E5:44:C6:FE:5D:74:4A:60:B6:0A:94:3F:C3:70: 0B:6D:27:A6:89:F7:D2:AC:8E:71:AC:0D:AF:5D:3A:19:07:18:F9:7C: B8:3C:47:DF:18:4D:13:C9:F8:45:AC:81:19:B0:DE:57:16:1A:F5:C6: AC:41:7E:E7:F2:6D:29:9C:14:A3:04:F8:9B:DF:8D:2E:9F:34:44:18: A8:FF:C6:A4:AF:04:86:D5:6D:F2:4C:AD:D2:65:4C:63:0F:C1:82:E3: 28:20:F2:D4:80:86:1A:67:1D:A2:56:18:87:E2:AB:40:E6:6A:48:E5: D7:D2:6F:6F:DB:05:20:B2:76:81:5C:0C:36:02:37:E9:A2:08:4E:53: 5E:9C:18:03:50:11:2D:E4:62:74:6E:CB:42:67:25:22:0C:F6:55:D8: 6F:E3:5A:15:AC:10:B7:F2:B7:C9:20:6C:19:ED:CC:7D:CC:CB:48:3B: B0:5E:E3:ED:05:DF:DF:65:FF:19:AD:76:6E:40:D2:0B:F0:11:65:D5: 92:7D:C9:3A:32:BE:A8:13:CE:C1:DE:D9:73:0F:0A:0B:8A:08:55:2E: 41:9D:B9:9A:AD:EC:4C:7D:98:3A:52:38:DF:78:DE:33:F1:14:A2:1B: AC:93:FD:30:76:A5:7C:AF:13:16:B8:5E:0B:73:A7:1F:20:E4:54:44: 07:A2:11:7F:D7:0E:B3:1C:A9:AA:73:76:0E:89:E0:D5:74:39:66:2F: E8:14:93:EC:7A:B2:23:E0:CC:77:9F:CD:D9:99:CB:B0:14:21:1C:1F: 0C:E9:30:B8:C3:55:8F:49:FC:88:5D:EF:20:B9:0E:F2:88:28:5A:93: 08:4D:2B:76:64:85:D1:E0:1C:9C:4B:86:2C:DB:65:F6:D8:23:A0:8D: 1B:22:74:0C:B9:41:9E:57:5A:67:4C:CC:1F:E2:43:5F:C2:21:82:E6: D4:C1:66:6F:30:54:27:2E:1D:22:8C:65:7F:93:C8:1D:C0:51:F0:7D: 7A:96:3A:3B:3D:C4:6E:69:DF:83:8A:85:0D:35:15:F9:5E:89:0F:D5: 9E:6F:A1:5F:39:CE:2A:88:57:97:DF:42:5C:70:12:4E:91:9E:1A:92: 49:99:C3:7B:38:12:B0:3A:D0:92:38:45:C7:74:3C:66:0F:A1:9C:C2: 9F:DC:A2:1B:DF:20:BB:F5:A5:F0:10:D6:6F:4F:C1:90:00:C3:F9:D8: 42:96:D2:28:FD:DE:21:33:6C:F4:7F:18:B2:ED:F9:A6:A4:4A:A5:4F: 26:7C:C0:F7:8B:A9:B3:2F:5A:5B:E2:B8 Demsg entries: usb 4-3: new full-speed USB device number 6 using ohci-pci usb 4-3: New USB dev
[Kernel-packages] [Bug 1919164] Re: can't use mSata Adapter (with and without uas quirks)
** Attachment added: "lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919164/+attachment/5476766/+files/lsusb.txt -- 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/1919164 Title: can't use mSata Adapter (with and without uas quirks) Status in linux package in Ubuntu: New Bug description: I tried to access an mSata disk with Ubuntu 20.04 using the ASMedia AS2115 adapter. This did not work with - 5.4.0-26-generic (Lenovo T14s, AMD) - 5.8.0-44-generic (Lenovo T14s, AMD) - 5.8.0-44-lowlatency (Toshiba C70, Intel, tried USB 2.0 and USB 3.0 port) trying both uas and usb-quirks 174c:1153:u, ie. disabling uas The errors have been similar on all configurations. Logs are from the C70 with 5.8.0-44-lowlatency and the USB 3.0 port. I removed the modules uas and usb-storage in both cases and modprobed them again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919164] Re: can't use mSata Adapter (with and without uas quirks)
** Attachment added: "dmesg-uas.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919164/+attachment/5476765/+files/dmesg-uas.txt -- 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/1919164 Title: can't use mSata Adapter (with and without uas quirks) Status in linux package in Ubuntu: New Bug description: I tried to access an mSata disk with Ubuntu 20.04 using the ASMedia AS2115 adapter. This did not work with - 5.4.0-26-generic (Lenovo T14s, AMD) - 5.8.0-44-generic (Lenovo T14s, AMD) - 5.8.0-44-lowlatency (Toshiba C70, Intel, tried USB 2.0 and USB 3.0 port) trying both uas and usb-quirks 174c:1153:u, ie. disabling uas The errors have been similar on all configurations. Logs are from the C70 with 5.8.0-44-lowlatency and the USB 3.0 port. I removed the modules uas and usb-storage in both cases and modprobed them again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919164] Re: can't use mSata Adapter (with and without uas quirks)
** Attachment added: "lspci-v.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919164/+attachment/5476768/+files/lspci-v.txt ** Description changed: - I tried to access an mSata disk using the ASMedia AS2115 adapter. + I tried to access an mSata disk with Ubuntu 20.04 using the ASMedia + AS2115 adapter. This did not work with - 5.4.0-26-generic (Lenovo T14s, AMD) - 5.8.0-44-generic (Lenovo T14s, AMD) - 5.8.0-44-lowlatency (Toshiba C70, Intel, tried USB 2.0 and USB 3.0 port) - using uas and using usb-quirks 174c:1153:u, ie. disabling uas + - 5.4.0-26-generic (Lenovo T14s, AMD) + - 5.8.0-44-generic (Lenovo T14s, AMD) + - 5.8.0-44-lowlatency (Toshiba C70, Intel, tried USB 2.0 and USB 3.0 port) + trying both uas and usb-quirks 174c:1153:u, ie. disabling uas - The errors have been similiar on all configurations. + The errors have been similar on all configurations. Logs are from the C70 with 5.8.0-44-lowlatency and the USB 3.0 port. I removed the modules uas and usb-storage in both cases and modprobed them again. -- 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/1919164 Title: can't use mSata Adapter (with and without uas quirks) Status in linux package in Ubuntu: New Bug description: I tried to access an mSata disk with Ubuntu 20.04 using the ASMedia AS2115 adapter. This did not work with - 5.4.0-26-generic (Lenovo T14s, AMD) - 5.8.0-44-generic (Lenovo T14s, AMD) - 5.8.0-44-lowlatency (Toshiba C70, Intel, tried USB 2.0 and USB 3.0 port) trying both uas and usb-quirks 174c:1153:u, ie. disabling uas The errors have been similar on all configurations. Logs are from the C70 with 5.8.0-44-lowlatency and the USB 3.0 port. I removed the modules uas and usb-storage in both cases and modprobed them again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919164] Re: can't use mSata Adapter (with and without uas quirks)
** Attachment added: "lsusb-v.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919164/+attachment/5476767/+files/lsusb-v.txt -- 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/1919164 Title: can't use mSata Adapter (with and without uas quirks) Status in linux package in Ubuntu: New Bug description: I tried to access an mSata disk with Ubuntu 20.04 using the ASMedia AS2115 adapter. This did not work with - 5.4.0-26-generic (Lenovo T14s, AMD) - 5.8.0-44-generic (Lenovo T14s, AMD) - 5.8.0-44-lowlatency (Toshiba C70, Intel, tried USB 2.0 and USB 3.0 port) trying both uas and usb-quirks 174c:1153:u, ie. disabling uas The errors have been similar on all configurations. Logs are from the C70 with 5.8.0-44-lowlatency and the USB 3.0 port. I removed the modules uas and usb-storage in both cases and modprobed them again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919164] [NEW] can't use mSata Adapter (with and without uas quirks)
Public bug reported: I tried to access an mSata disk with Ubuntu 20.04 using the ASMedia AS2115 adapter. This did not work with - 5.4.0-26-generic (Lenovo T14s, AMD) - 5.8.0-44-generic (Lenovo T14s, AMD) - 5.8.0-44-lowlatency (Toshiba C70, Intel, tried USB 2.0 and USB 3.0 port) trying both uas and usb-quirks 174c:1153:u, ie. disabling uas The errors have been similar on all configurations. Logs are from the C70 with 5.8.0-44-lowlatency and the USB 3.0 port. I removed the modules uas and usb-storage in both cases and modprobed them again. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg log when using quirks aka disabling uas" https://bugs.launchpad.net/bugs/1919164/+attachment/5476764/+files/dmesg-quirks.txt -- 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/1919164 Title: can't use mSata Adapter (with and without uas quirks) Status in linux package in Ubuntu: New Bug description: I tried to access an mSata disk with Ubuntu 20.04 using the ASMedia AS2115 adapter. This did not work with - 5.4.0-26-generic (Lenovo T14s, AMD) - 5.8.0-44-generic (Lenovo T14s, AMD) - 5.8.0-44-lowlatency (Toshiba C70, Intel, tried USB 2.0 and USB 3.0 port) trying both uas and usb-quirks 174c:1153:u, ie. disabling uas The errors have been similar on all configurations. Logs are from the C70 with 5.8.0-44-lowlatency and the USB 3.0 port. I removed the modules uas and usb-storage in both cases and modprobed them again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919070] Re: Unstable and frequent crashes kernel 5.4.0-66-generic on ASUS E201NAS (5.4.0-65-generic is good)
Hi Guilherme, The laptop is pretty underpowered and occasionally freezes but only for a split second but when running on linux-5.4.0-66-generic freezes are frequent and long. Zoom calls crash the system and require a hard reset - on <= linux-5.4.0.65 zoom calls works perfectly. It also needs a hard reset when plugging in HMDI amongst other seemingly unrelated things. I see no on screen errors. I'll enabled kdump and post the logs when I can. -- 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/1919070 Title: Unstable and frequent crashes kernel 5.4.0-66-generic on ASUS E201NAS (5.4.0-65-generic is good) Status in linux package in Ubuntu: Confirmed Bug description: Version: Kubuntu 20.04.1 System: ASUS E201NAS KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-66-generic OS Type: 64-bit Processors: 2 × Intel® Celeron® CPU N3350 @ 1.10GHz Memory: 3.7 GiB of RAM Notes: linux-image-5.4.0-65-generic and prior versions are excellent. Since the kernel update to 5.4.0-66-generic the system is very unstable, freezes and has frequent crashes. I'm using to linux- image-5.4.0-65-generic for this report. This is my first Ubuntu bug report. Let me know if you need information. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sam1157 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-05 (160 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:5a06 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 13d3:3496 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E201NAS Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=6c2a5e29-03e2-41c6-a0fa-80222b2350d9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 Tags: focal Uname: Linux 5.4.0-66-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E201NAS.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E201NAS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE201NAS.311:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnE201NAS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE201NAS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: E201NAS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919154] [NEW] Enable CONFIG_NO_HZ_FULL on supported architectures
Public bug reported: [Impact] The CONFIG_NO_HZ_FULL=y Kconfig option causes the kernel to avoid sending scheduling-clock interrupts to CPUs with a single runnable task, and such CPUs are said to be "adaptive-ticks CPUs". This is important for applications with aggressive real-time response constraints because it allows them to improve their worst-case response times by the maximum duration of a scheduling-clock interrupt. It is also important for computationally intensive short-iteration workloads: If any CPU is delayed during a given iteration, all the other CPUs will be forced to wait idle while the delayed CPU finishes. Thus, the delay is multiplied by one less than the number of CPUs. In these situations, there is again strong motivation to avoid sending scheduling-clock interrupts. [Test Plan] In order to verify the change will not cause performance issues in context switch we should compare the results for: ./stress-ng --seq 0 --metrics-brief -t 15 Running on a dedicated machine and with the following services disabled: smartd.service, iscsid.service, apport.service, cron.service, anacron.timer, apt-daily.timer, apt-daily-upgrade.timer, fstrim.timer, logrotate.timer, motd-news.timer, man-db.timer. [Where problems could occur] Performance degradation might happen for workloads with intensive context switching. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Marcelo Cerri (mhcerri) Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Assignee: Marcelo Cerri (mhcerri) Status: In Progress ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Assignee: Marcelo Cerri (mhcerri) Status: In Progress -- 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/1919154 Title: Enable CONFIG_NO_HZ_FULL on supported architectures Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: New Status in linux source package in Groovy: New Status in linux source package in Hirsute: In Progress Bug description: [Impact] The CONFIG_NO_HZ_FULL=y Kconfig option causes the kernel to avoid sending scheduling-clock interrupts to CPUs with a single runnable task, and such CPUs are said to be "adaptive-ticks CPUs". This is important for applications with aggressive real-time response constraints because it allows them to improve their worst-case response times by the maximum duration of a scheduling-clock interrupt. It is also important for computationally intensive short-iteration workloads: If any CPU is delayed during a given iteration, all the other CPUs will be forced to wait idle while the delayed CPU finishes. Thus, the delay is multiplied by one less than the number of CPUs. In these situations, there is again strong motivation to avoid sending scheduling-clock interrupts. [Test Plan] In order to verify the change will not cause performance issues in context switch we should compare the results for: ./stress-ng --seq 0 --metrics-brief -t 15 Running on a dedicated machine and with the following services disabled: smartd.service, iscsid.service, apport.service, cron.service, anacron.timer, apt-daily.timer, apt-daily-upgrade.timer, fstrim.timer, logrotate.timer, motd-news.timer, man-db.timer. [Where problems could occur] Performance degradation might happen for workloads with intensive context switching. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916871] Re: linux-image-virtual package missing key network qdisc/TCP CC modules
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- 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/1916871 Title: linux-image-virtual package missing key network qdisc/TCP CC modules Status in linux package in Ubuntu: Invalid Bug description: At present the Ubuntu 20.04 linux-image-virtual kernel package don't include the tcp_bbr, sch_cake and sch_fq_codel kernel modules. The latter has been default on desktop for a number of release cycles; cake improves on this. These queueing disciplines are instrumental to reducing queueing latency [bufferbloat.net]; the TCP congestion control algo elevates bandwidth on lossy paths (think clients on radio networks). Enabling these kernel modules will ensure Ubuntu has an optimally competitive network stack in cloud/VM systems. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 25 19:47 seq crw-rw 1 root audio 116, 33 Feb 25 19:47 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-05-18 (1013 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (Q35 + ICH9, 2009) NonfreeKernelModules: bochs_drm i2c_i801 lpc_ich Package: linux (not installed) PciMultimedia: ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=/dev/sda ro console=ttyS0,19200n8 net.ifnames=0 cgroup_disable=cpuset,cpu,cpuacct,blkio,memory nmi_watchdog=0 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-66-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-03 (298 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-3.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918698] Re: Stale firmware symlink
** Changed in: linux-firmware (Ubuntu Groovy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1918698 Title: Stale firmware symlink Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Groovy: Fix Committed Bug description: [Impact] On Groovy with linux-firmware 1.190.3: lrwxrwxrwx 1 root root 54 Jan 7 15:40 brcmfmac43455-sdio.raspberrypi,3-model-a-plus.txt -> brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt That link target is wrong and doesn't exist, it should be without the 'brcm/' prefix. [Test Case] $ ls -la /lib/firmware/brcm/brcmfmac43455* [Fix] The upstream fix is: commit a9993f8d3b241f70a691a5b81bf2cdb442c0e184 Author: Takashi Iwai Date: Tue Sep 8 12:16:56 2020 +0200 brcm: Fix a stale symlink for RPi3 model b+ The symlink for brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt was wrongly listed with the same subdirectory brcm, and this resulted in a stale symlink. Fix it. Signed-off-by: Takashi Iwai Signed-off-by: Josh Boyer [Where Problems Could Occur] Firmware is now loaded on Pi 3A+ at boot which didn't happen before so theoretically that could crash the kernel if it's buggy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1918698/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919051] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1919051/+attachment/5476753/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1919051 Title: ch341 USB-Serial converter only receives, does not send Status in linux package in Ubuntu: Confirmed Bug description: This device works flawlessly on Windows XP with native driver, both as a physical machine or inside a VM. It appears on XP's device management as "USB 2.0" name. On Ubuntu, Shorting pins 2 and 3 of DB9 connector does not give back characters sent (no echo), nor typed strings are sent to other RS232 devices, despite of communication settings. Characters from remote devices are correctly received. Using a null modem cable to other RS232 terminal shows that the local terminal receives, but does not transmit. Its worth to mention: passing through the device to a guest virtual machine (KVM) running Windows XP makes it work correctly with XP driver inside the guest OS. Bringing back the device stops transmitting. Only receive works. Tested with the version below: NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal Kernel: Linux host 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Device ID: ID 4348:5523 WinChipHead USB->RS 232 adapter with Prolifec PL 2303 chipset Modinfo: filename: /lib/modules/5.4.0-66-generic/kernel/drivers/usb/serial/ch341.ko license:GPL v2 srcversion: 8F5F64E72BDA4E76E6F4F4D alias: usb:v4348p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7522d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5512d*dc*dsc*dp*ic*isc*ip*in* depends:usbserial retpoline: Y intree: Y name: ch341 vermagic: 5.4.0-66-generic SMP mod_unload sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:1E:07:0D:94:23:77:98:99:05:31:F3:76:E8:6B:76:12:7C:83:9E:05 sig_hashalgo: sha512 signature: 50:CE:79:92:87:EA:82:77:A9:25:A3:B7:F2:B3:ED:63:FE:85:EB:61: 7A:31:C5:9E:E5:78:E5:44:C6:FE:5D:74:4A:60:B6:0A:94:3F:C3:70: 0B:6D:27:A6:89:F7:D2:AC:8E:71:AC:0D:AF:5D:3A:19:07:18:F9:7C: B8:3C:47:DF:18:4D:13:C9:F8:45:AC:81:19:B0:DE:57:16:1A:F5:C6: AC:41:7E:E7:F2:6D:29:9C:14:A3:04:F8:9B:DF:8D:2E:9F:34:44:18: A8:FF:C6:A4:AF:04:86:D5:6D:F2:4C:AD:D2:65:4C:63:0F:C1:82:E3: 28:20:F2:D4:80:86:1A:67:1D:A2:56:18:87:E2:AB:40:E6:6A:48:E5: D7:D2:6F:6F:DB:05:20:B2:76:81:5C:0C:36:02:37:E9:A2:08:4E:53: 5E:9C:18:03:50:11:2D:E4:62:74:6E:CB:42:67:25:22:0C:F6:55:D8: 6F:E3:5A:15:AC:10:B7:F2:B7:C9:20:6C:19:ED:CC:7D:CC:CB:48:3B: B0:5E:E3:ED:05:DF:DF:65:FF:19:AD:76:6E:40:D2:0B:F0:11:65:D5: 92:7D:C9:3A:32:BE:A8:13:CE:C1:DE:D9:73:0F:0A:0B:8A:08:55:2E: 41:9D:B9:9A:AD:EC:4C:7D:98:3A:52:38:DF:78:DE:33:F1:14:A2:1B: AC:93:FD:30:76:A5:7C:AF:13:16:B8:5E:0B:73:A7:1F:20:E4:54:44: 07:A2:11:7F:D7:0E:B3:1C:A9:AA:73:76:0E:89:E0:D5:74:39:66:2F: E8:14:93:EC:7A:B2:23:E0:CC:77:9F:CD:D9:99:CB:B0:14:21:1C:1F: 0C:E9:30:B8:C3:55:8F:49:FC:88:5D:EF:20:B9:0E:F2:88:28:5A:93: 08:4D:2B:76:64:85:D1:E0:1C:9C:4B:86:2C:DB:65:F6:D8:23:A0:8D: 1B:22:74:0C:B9:41:9E:57:5A:67:4C:CC:1F:E2:43:5F:C2:21:82:E6: D4:C1:66:6F:30:54:27:2E:1D:22:8C:65:7F:93:C8:1D:C0:51:F0:7D: 7A:96:3A:3B:3D:C4:6E:69:DF:83:8A:85:0D:35:15:F9:5E:89:0F:D5: 9E:6F:A1:5F:39:CE:2A:88:57:97:DF:42:5C:70:12:4E:91:9E:1A:92: 49:99:C3:7B:38:12:B0:3A:D0:92:38:45:C7:74:3C:66:0F:A1:9C:C2: 9F:DC:A2:1B:DF:20:BB:F5:A5:F0:10:D6:6F:4F:C1:90:00:C3:F9:D8: 42:96:D2:28:FD:DE:21:33:6C:F4:7F:18:B2:ED:F9:A6:A4:4A:A5:4F: 26:7C:C0:F7:8B:A9:B3:2F:5A:5B:E2:B8 Demsg entries: usb 4-3: new full-speed USB device number 6 using ohci-pci usb 4-3: New USB device found, idVendor=4348, idProduct=5523, bcdDevice= 2.50 usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 ch341 4-3:1.0: ch341-uart converter det
[Kernel-packages] [Bug 1919051] Re: ch341 USB-Serial converter only receives, does not send
In response to #4: Attached apport logs. Please wait while I make a test with mainline kernel. Thanks for the clue. -- 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/1919051 Title: ch341 USB-Serial converter only receives, does not send Status in linux package in Ubuntu: Confirmed Bug description: This device works flawlessly on Windows XP with native driver, both as a physical machine or inside a VM. It appears on XP's device management as "USB 2.0" name. On Ubuntu, Shorting pins 2 and 3 of DB9 connector does not give back characters sent (no echo), nor typed strings are sent to other RS232 devices, despite of communication settings. Characters from remote devices are correctly received. Using a null modem cable to other RS232 terminal shows that the local terminal receives, but does not transmit. Its worth to mention: passing through the device to a guest virtual machine (KVM) running Windows XP makes it work correctly with XP driver inside the guest OS. Bringing back the device stops transmitting. Only receive works. Tested with the version below: NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal Kernel: Linux host 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Device ID: ID 4348:5523 WinChipHead USB->RS 232 adapter with Prolifec PL 2303 chipset Modinfo: filename: /lib/modules/5.4.0-66-generic/kernel/drivers/usb/serial/ch341.ko license:GPL v2 srcversion: 8F5F64E72BDA4E76E6F4F4D alias: usb:v4348p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7522d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5512d*dc*dsc*dp*ic*isc*ip*in* depends:usbserial retpoline: Y intree: Y name: ch341 vermagic: 5.4.0-66-generic SMP mod_unload sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:1E:07:0D:94:23:77:98:99:05:31:F3:76:E8:6B:76:12:7C:83:9E:05 sig_hashalgo: sha512 signature: 50:CE:79:92:87:EA:82:77:A9:25:A3:B7:F2:B3:ED:63:FE:85:EB:61: 7A:31:C5:9E:E5:78:E5:44:C6:FE:5D:74:4A:60:B6:0A:94:3F:C3:70: 0B:6D:27:A6:89:F7:D2:AC:8E:71:AC:0D:AF:5D:3A:19:07:18:F9:7C: B8:3C:47:DF:18:4D:13:C9:F8:45:AC:81:19:B0:DE:57:16:1A:F5:C6: AC:41:7E:E7:F2:6D:29:9C:14:A3:04:F8:9B:DF:8D:2E:9F:34:44:18: A8:FF:C6:A4:AF:04:86:D5:6D:F2:4C:AD:D2:65:4C:63:0F:C1:82:E3: 28:20:F2:D4:80:86:1A:67:1D:A2:56:18:87:E2:AB:40:E6:6A:48:E5: D7:D2:6F:6F:DB:05:20:B2:76:81:5C:0C:36:02:37:E9:A2:08:4E:53: 5E:9C:18:03:50:11:2D:E4:62:74:6E:CB:42:67:25:22:0C:F6:55:D8: 6F:E3:5A:15:AC:10:B7:F2:B7:C9:20:6C:19:ED:CC:7D:CC:CB:48:3B: B0:5E:E3:ED:05:DF:DF:65:FF:19:AD:76:6E:40:D2:0B:F0:11:65:D5: 92:7D:C9:3A:32:BE:A8:13:CE:C1:DE:D9:73:0F:0A:0B:8A:08:55:2E: 41:9D:B9:9A:AD:EC:4C:7D:98:3A:52:38:DF:78:DE:33:F1:14:A2:1B: AC:93:FD:30:76:A5:7C:AF:13:16:B8:5E:0B:73:A7:1F:20:E4:54:44: 07:A2:11:7F:D7:0E:B3:1C:A9:AA:73:76:0E:89:E0:D5:74:39:66:2F: E8:14:93:EC:7A:B2:23:E0:CC:77:9F:CD:D9:99:CB:B0:14:21:1C:1F: 0C:E9:30:B8:C3:55:8F:49:FC:88:5D:EF:20:B9:0E:F2:88:28:5A:93: 08:4D:2B:76:64:85:D1:E0:1C:9C:4B:86:2C:DB:65:F6:D8:23:A0:8D: 1B:22:74:0C:B9:41:9E:57:5A:67:4C:CC:1F:E2:43:5F:C2:21:82:E6: D4:C1:66:6F:30:54:27:2E:1D:22:8C:65:7F:93:C8:1D:C0:51:F0:7D: 7A:96:3A:3B:3D:C4:6E:69:DF:83:8A:85:0D:35:15:F9:5E:89:0F:D5: 9E:6F:A1:5F:39:CE:2A:88:57:97:DF:42:5C:70:12:4E:91:9E:1A:92: 49:99:C3:7B:38:12:B0:3A:D0:92:38:45:C7:74:3C:66:0F:A1:9C:C2: 9F:DC:A2:1B:DF:20:BB:F5:A5:F0:10:D6:6F:4F:C1:90:00:C3:F9:D8: 42:96:D2:28:FD:DE:21:33:6C:F4:7F:18:B2:ED:F9:A6:A4:4A:A5:4F: 26:7C:C0:F7:8B:A9:B3:2F:5A:5B:E2:B8 Demsg entries: usb 4-3: new full-speed USB device number 6 using ohci-pci usb 4-3: New USB device found, idVendor=4348, idProduct=5523, bcdDevice= 2.50 usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 ch341 4-3:1.0: ch341-uart converter detected usb 4-3: ch341-uart converter now attached to ttyUSB0 --- ProblemType: Bug App
[Kernel-packages] [Bug 1919051] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1919051/+attachment/5476752/+files/WifiSyslog.txt -- 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/1919051 Title: ch341 USB-Serial converter only receives, does not send Status in linux package in Ubuntu: Confirmed Bug description: This device works flawlessly on Windows XP with native driver, both as a physical machine or inside a VM. It appears on XP's device management as "USB 2.0" name. On Ubuntu, Shorting pins 2 and 3 of DB9 connector does not give back characters sent (no echo), nor typed strings are sent to other RS232 devices, despite of communication settings. Characters from remote devices are correctly received. Using a null modem cable to other RS232 terminal shows that the local terminal receives, but does not transmit. Its worth to mention: passing through the device to a guest virtual machine (KVM) running Windows XP makes it work correctly with XP driver inside the guest OS. Bringing back the device stops transmitting. Only receive works. Tested with the version below: NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal Kernel: Linux host 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Device ID: ID 4348:5523 WinChipHead USB->RS 232 adapter with Prolifec PL 2303 chipset Modinfo: filename: /lib/modules/5.4.0-66-generic/kernel/drivers/usb/serial/ch341.ko license:GPL v2 srcversion: 8F5F64E72BDA4E76E6F4F4D alias: usb:v4348p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7522d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5512d*dc*dsc*dp*ic*isc*ip*in* depends:usbserial retpoline: Y intree: Y name: ch341 vermagic: 5.4.0-66-generic SMP mod_unload sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:1E:07:0D:94:23:77:98:99:05:31:F3:76:E8:6B:76:12:7C:83:9E:05 sig_hashalgo: sha512 signature: 50:CE:79:92:87:EA:82:77:A9:25:A3:B7:F2:B3:ED:63:FE:85:EB:61: 7A:31:C5:9E:E5:78:E5:44:C6:FE:5D:74:4A:60:B6:0A:94:3F:C3:70: 0B:6D:27:A6:89:F7:D2:AC:8E:71:AC:0D:AF:5D:3A:19:07:18:F9:7C: B8:3C:47:DF:18:4D:13:C9:F8:45:AC:81:19:B0:DE:57:16:1A:F5:C6: AC:41:7E:E7:F2:6D:29:9C:14:A3:04:F8:9B:DF:8D:2E:9F:34:44:18: A8:FF:C6:A4:AF:04:86:D5:6D:F2:4C:AD:D2:65:4C:63:0F:C1:82:E3: 28:20:F2:D4:80:86:1A:67:1D:A2:56:18:87:E2:AB:40:E6:6A:48:E5: D7:D2:6F:6F:DB:05:20:B2:76:81:5C:0C:36:02:37:E9:A2:08:4E:53: 5E:9C:18:03:50:11:2D:E4:62:74:6E:CB:42:67:25:22:0C:F6:55:D8: 6F:E3:5A:15:AC:10:B7:F2:B7:C9:20:6C:19:ED:CC:7D:CC:CB:48:3B: B0:5E:E3:ED:05:DF:DF:65:FF:19:AD:76:6E:40:D2:0B:F0:11:65:D5: 92:7D:C9:3A:32:BE:A8:13:CE:C1:DE:D9:73:0F:0A:0B:8A:08:55:2E: 41:9D:B9:9A:AD:EC:4C:7D:98:3A:52:38:DF:78:DE:33:F1:14:A2:1B: AC:93:FD:30:76:A5:7C:AF:13:16:B8:5E:0B:73:A7:1F:20:E4:54:44: 07:A2:11:7F:D7:0E:B3:1C:A9:AA:73:76:0E:89:E0:D5:74:39:66:2F: E8:14:93:EC:7A:B2:23:E0:CC:77:9F:CD:D9:99:CB:B0:14:21:1C:1F: 0C:E9:30:B8:C3:55:8F:49:FC:88:5D:EF:20:B9:0E:F2:88:28:5A:93: 08:4D:2B:76:64:85:D1:E0:1C:9C:4B:86:2C:DB:65:F6:D8:23:A0:8D: 1B:22:74:0C:B9:41:9E:57:5A:67:4C:CC:1F:E2:43:5F:C2:21:82:E6: D4:C1:66:6F:30:54:27:2E:1D:22:8C:65:7F:93:C8:1D:C0:51:F0:7D: 7A:96:3A:3B:3D:C4:6E:69:DF:83:8A:85:0D:35:15:F9:5E:89:0F:D5: 9E:6F:A1:5F:39:CE:2A:88:57:97:DF:42:5C:70:12:4E:91:9E:1A:92: 49:99:C3:7B:38:12:B0:3A:D0:92:38:45:C7:74:3C:66:0F:A1:9C:C2: 9F:DC:A2:1B:DF:20:BB:F5:A5:F0:10:D6:6F:4F:C1:90:00:C3:F9:D8: 42:96:D2:28:FD:DE:21:33:6C:F4:7F:18:B2:ED:F9:A6:A4:4A:A5:4F: 26:7C:C0:F7:8B:A9:B3:2F:5A:5B:E2:B8 Demsg entries: usb 4-3: new full-speed USB device number 6 using ohci-pci usb 4-3: New USB device found, idVendor=4348, idProduct=5523, bcdDevice= 2.50 usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 ch341 4-3:1.0: ch341-uart converter detected usb 4-3: ch341-uart converter now attached to ttyUSB0 --
[Kernel-packages] [Bug 1919051] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1919051/+attachment/5476751/+files/UdevDb.txt -- 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/1919051 Title: ch341 USB-Serial converter only receives, does not send Status in linux package in Ubuntu: Confirmed Bug description: This device works flawlessly on Windows XP with native driver, both as a physical machine or inside a VM. It appears on XP's device management as "USB 2.0" name. On Ubuntu, Shorting pins 2 and 3 of DB9 connector does not give back characters sent (no echo), nor typed strings are sent to other RS232 devices, despite of communication settings. Characters from remote devices are correctly received. Using a null modem cable to other RS232 terminal shows that the local terminal receives, but does not transmit. Its worth to mention: passing through the device to a guest virtual machine (KVM) running Windows XP makes it work correctly with XP driver inside the guest OS. Bringing back the device stops transmitting. Only receive works. Tested with the version below: NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal Kernel: Linux host 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Device ID: ID 4348:5523 WinChipHead USB->RS 232 adapter with Prolifec PL 2303 chipset Modinfo: filename: /lib/modules/5.4.0-66-generic/kernel/drivers/usb/serial/ch341.ko license:GPL v2 srcversion: 8F5F64E72BDA4E76E6F4F4D alias: usb:v4348p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7522d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5512d*dc*dsc*dp*ic*isc*ip*in* depends:usbserial retpoline: Y intree: Y name: ch341 vermagic: 5.4.0-66-generic SMP mod_unload sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:1E:07:0D:94:23:77:98:99:05:31:F3:76:E8:6B:76:12:7C:83:9E:05 sig_hashalgo: sha512 signature: 50:CE:79:92:87:EA:82:77:A9:25:A3:B7:F2:B3:ED:63:FE:85:EB:61: 7A:31:C5:9E:E5:78:E5:44:C6:FE:5D:74:4A:60:B6:0A:94:3F:C3:70: 0B:6D:27:A6:89:F7:D2:AC:8E:71:AC:0D:AF:5D:3A:19:07:18:F9:7C: B8:3C:47:DF:18:4D:13:C9:F8:45:AC:81:19:B0:DE:57:16:1A:F5:C6: AC:41:7E:E7:F2:6D:29:9C:14:A3:04:F8:9B:DF:8D:2E:9F:34:44:18: A8:FF:C6:A4:AF:04:86:D5:6D:F2:4C:AD:D2:65:4C:63:0F:C1:82:E3: 28:20:F2:D4:80:86:1A:67:1D:A2:56:18:87:E2:AB:40:E6:6A:48:E5: D7:D2:6F:6F:DB:05:20:B2:76:81:5C:0C:36:02:37:E9:A2:08:4E:53: 5E:9C:18:03:50:11:2D:E4:62:74:6E:CB:42:67:25:22:0C:F6:55:D8: 6F:E3:5A:15:AC:10:B7:F2:B7:C9:20:6C:19:ED:CC:7D:CC:CB:48:3B: B0:5E:E3:ED:05:DF:DF:65:FF:19:AD:76:6E:40:D2:0B:F0:11:65:D5: 92:7D:C9:3A:32:BE:A8:13:CE:C1:DE:D9:73:0F:0A:0B:8A:08:55:2E: 41:9D:B9:9A:AD:EC:4C:7D:98:3A:52:38:DF:78:DE:33:F1:14:A2:1B: AC:93:FD:30:76:A5:7C:AF:13:16:B8:5E:0B:73:A7:1F:20:E4:54:44: 07:A2:11:7F:D7:0E:B3:1C:A9:AA:73:76:0E:89:E0:D5:74:39:66:2F: E8:14:93:EC:7A:B2:23:E0:CC:77:9F:CD:D9:99:CB:B0:14:21:1C:1F: 0C:E9:30:B8:C3:55:8F:49:FC:88:5D:EF:20:B9:0E:F2:88:28:5A:93: 08:4D:2B:76:64:85:D1:E0:1C:9C:4B:86:2C:DB:65:F6:D8:23:A0:8D: 1B:22:74:0C:B9:41:9E:57:5A:67:4C:CC:1F:E2:43:5F:C2:21:82:E6: D4:C1:66:6F:30:54:27:2E:1D:22:8C:65:7F:93:C8:1D:C0:51:F0:7D: 7A:96:3A:3B:3D:C4:6E:69:DF:83:8A:85:0D:35:15:F9:5E:89:0F:D5: 9E:6F:A1:5F:39:CE:2A:88:57:97:DF:42:5C:70:12:4E:91:9E:1A:92: 49:99:C3:7B:38:12:B0:3A:D0:92:38:45:C7:74:3C:66:0F:A1:9C:C2: 9F:DC:A2:1B:DF:20:BB:F5:A5:F0:10:D6:6F:4F:C1:90:00:C3:F9:D8: 42:96:D2:28:FD:DE:21:33:6C:F4:7F:18:B2:ED:F9:A6:A4:4A:A5:4F: 26:7C:C0:F7:8B:A9:B3:2F:5A:5B:E2:B8 Demsg entries: usb 4-3: new full-speed USB device number 6 using ohci-pci usb 4-3: New USB device found, idVendor=4348, idProduct=5523, bcdDevice= 2.50 usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 ch341 4-3:1.0: ch341-uart converter detected usb 4-3: ch341-uart converter now attached to ttyUSB0 --- Prob
[Kernel-packages] [Bug 1919051] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1919051/+attachment/5476750/+files/PulseList.txt -- 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/1919051 Title: ch341 USB-Serial converter only receives, does not send Status in linux package in Ubuntu: Confirmed Bug description: This device works flawlessly on Windows XP with native driver, both as a physical machine or inside a VM. It appears on XP's device management as "USB 2.0" name. On Ubuntu, Shorting pins 2 and 3 of DB9 connector does not give back characters sent (no echo), nor typed strings are sent to other RS232 devices, despite of communication settings. Characters from remote devices are correctly received. Using a null modem cable to other RS232 terminal shows that the local terminal receives, but does not transmit. Its worth to mention: passing through the device to a guest virtual machine (KVM) running Windows XP makes it work correctly with XP driver inside the guest OS. Bringing back the device stops transmitting. Only receive works. Tested with the version below: NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal Kernel: Linux host 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Device ID: ID 4348:5523 WinChipHead USB->RS 232 adapter with Prolifec PL 2303 chipset Modinfo: filename: /lib/modules/5.4.0-66-generic/kernel/drivers/usb/serial/ch341.ko license:GPL v2 srcversion: 8F5F64E72BDA4E76E6F4F4D alias: usb:v4348p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7522d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5512d*dc*dsc*dp*ic*isc*ip*in* depends:usbserial retpoline: Y intree: Y name: ch341 vermagic: 5.4.0-66-generic SMP mod_unload sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:1E:07:0D:94:23:77:98:99:05:31:F3:76:E8:6B:76:12:7C:83:9E:05 sig_hashalgo: sha512 signature: 50:CE:79:92:87:EA:82:77:A9:25:A3:B7:F2:B3:ED:63:FE:85:EB:61: 7A:31:C5:9E:E5:78:E5:44:C6:FE:5D:74:4A:60:B6:0A:94:3F:C3:70: 0B:6D:27:A6:89:F7:D2:AC:8E:71:AC:0D:AF:5D:3A:19:07:18:F9:7C: B8:3C:47:DF:18:4D:13:C9:F8:45:AC:81:19:B0:DE:57:16:1A:F5:C6: AC:41:7E:E7:F2:6D:29:9C:14:A3:04:F8:9B:DF:8D:2E:9F:34:44:18: A8:FF:C6:A4:AF:04:86:D5:6D:F2:4C:AD:D2:65:4C:63:0F:C1:82:E3: 28:20:F2:D4:80:86:1A:67:1D:A2:56:18:87:E2:AB:40:E6:6A:48:E5: D7:D2:6F:6F:DB:05:20:B2:76:81:5C:0C:36:02:37:E9:A2:08:4E:53: 5E:9C:18:03:50:11:2D:E4:62:74:6E:CB:42:67:25:22:0C:F6:55:D8: 6F:E3:5A:15:AC:10:B7:F2:B7:C9:20:6C:19:ED:CC:7D:CC:CB:48:3B: B0:5E:E3:ED:05:DF:DF:65:FF:19:AD:76:6E:40:D2:0B:F0:11:65:D5: 92:7D:C9:3A:32:BE:A8:13:CE:C1:DE:D9:73:0F:0A:0B:8A:08:55:2E: 41:9D:B9:9A:AD:EC:4C:7D:98:3A:52:38:DF:78:DE:33:F1:14:A2:1B: AC:93:FD:30:76:A5:7C:AF:13:16:B8:5E:0B:73:A7:1F:20:E4:54:44: 07:A2:11:7F:D7:0E:B3:1C:A9:AA:73:76:0E:89:E0:D5:74:39:66:2F: E8:14:93:EC:7A:B2:23:E0:CC:77:9F:CD:D9:99:CB:B0:14:21:1C:1F: 0C:E9:30:B8:C3:55:8F:49:FC:88:5D:EF:20:B9:0E:F2:88:28:5A:93: 08:4D:2B:76:64:85:D1:E0:1C:9C:4B:86:2C:DB:65:F6:D8:23:A0:8D: 1B:22:74:0C:B9:41:9E:57:5A:67:4C:CC:1F:E2:43:5F:C2:21:82:E6: D4:C1:66:6F:30:54:27:2E:1D:22:8C:65:7F:93:C8:1D:C0:51:F0:7D: 7A:96:3A:3B:3D:C4:6E:69:DF:83:8A:85:0D:35:15:F9:5E:89:0F:D5: 9E:6F:A1:5F:39:CE:2A:88:57:97:DF:42:5C:70:12:4E:91:9E:1A:92: 49:99:C3:7B:38:12:B0:3A:D0:92:38:45:C7:74:3C:66:0F:A1:9C:C2: 9F:DC:A2:1B:DF:20:BB:F5:A5:F0:10:D6:6F:4F:C1:90:00:C3:F9:D8: 42:96:D2:28:FD:DE:21:33:6C:F4:7F:18:B2:ED:F9:A6:A4:4A:A5:4F: 26:7C:C0:F7:8B:A9:B3:2F:5A:5B:E2:B8 Demsg entries: usb 4-3: new full-speed USB device number 6 using ohci-pci usb 4-3: New USB device found, idVendor=4348, idProduct=5523, bcdDevice= 2.50 usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 ch341 4-3:1.0: ch341-uart converter detected usb 4-3: ch341-uart converter now attached to ttyUSB0 ---
[Kernel-packages] [Bug 1919051] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1919051/+attachment/5476748/+files/ProcInterrupts.txt -- 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/1919051 Title: ch341 USB-Serial converter only receives, does not send Status in linux package in Ubuntu: Confirmed Bug description: This device works flawlessly on Windows XP with native driver, both as a physical machine or inside a VM. It appears on XP's device management as "USB 2.0" name. On Ubuntu, Shorting pins 2 and 3 of DB9 connector does not give back characters sent (no echo), nor typed strings are sent to other RS232 devices, despite of communication settings. Characters from remote devices are correctly received. Using a null modem cable to other RS232 terminal shows that the local terminal receives, but does not transmit. Its worth to mention: passing through the device to a guest virtual machine (KVM) running Windows XP makes it work correctly with XP driver inside the guest OS. Bringing back the device stops transmitting. Only receive works. Tested with the version below: NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal Kernel: Linux host 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Device ID: ID 4348:5523 WinChipHead USB->RS 232 adapter with Prolifec PL 2303 chipset Modinfo: filename: /lib/modules/5.4.0-66-generic/kernel/drivers/usb/serial/ch341.ko license:GPL v2 srcversion: 8F5F64E72BDA4E76E6F4F4D alias: usb:v4348p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7522d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5512d*dc*dsc*dp*ic*isc*ip*in* depends:usbserial retpoline: Y intree: Y name: ch341 vermagic: 5.4.0-66-generic SMP mod_unload sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:1E:07:0D:94:23:77:98:99:05:31:F3:76:E8:6B:76:12:7C:83:9E:05 sig_hashalgo: sha512 signature: 50:CE:79:92:87:EA:82:77:A9:25:A3:B7:F2:B3:ED:63:FE:85:EB:61: 7A:31:C5:9E:E5:78:E5:44:C6:FE:5D:74:4A:60:B6:0A:94:3F:C3:70: 0B:6D:27:A6:89:F7:D2:AC:8E:71:AC:0D:AF:5D:3A:19:07:18:F9:7C: B8:3C:47:DF:18:4D:13:C9:F8:45:AC:81:19:B0:DE:57:16:1A:F5:C6: AC:41:7E:E7:F2:6D:29:9C:14:A3:04:F8:9B:DF:8D:2E:9F:34:44:18: A8:FF:C6:A4:AF:04:86:D5:6D:F2:4C:AD:D2:65:4C:63:0F:C1:82:E3: 28:20:F2:D4:80:86:1A:67:1D:A2:56:18:87:E2:AB:40:E6:6A:48:E5: D7:D2:6F:6F:DB:05:20:B2:76:81:5C:0C:36:02:37:E9:A2:08:4E:53: 5E:9C:18:03:50:11:2D:E4:62:74:6E:CB:42:67:25:22:0C:F6:55:D8: 6F:E3:5A:15:AC:10:B7:F2:B7:C9:20:6C:19:ED:CC:7D:CC:CB:48:3B: B0:5E:E3:ED:05:DF:DF:65:FF:19:AD:76:6E:40:D2:0B:F0:11:65:D5: 92:7D:C9:3A:32:BE:A8:13:CE:C1:DE:D9:73:0F:0A:0B:8A:08:55:2E: 41:9D:B9:9A:AD:EC:4C:7D:98:3A:52:38:DF:78:DE:33:F1:14:A2:1B: AC:93:FD:30:76:A5:7C:AF:13:16:B8:5E:0B:73:A7:1F:20:E4:54:44: 07:A2:11:7F:D7:0E:B3:1C:A9:AA:73:76:0E:89:E0:D5:74:39:66:2F: E8:14:93:EC:7A:B2:23:E0:CC:77:9F:CD:D9:99:CB:B0:14:21:1C:1F: 0C:E9:30:B8:C3:55:8F:49:FC:88:5D:EF:20:B9:0E:F2:88:28:5A:93: 08:4D:2B:76:64:85:D1:E0:1C:9C:4B:86:2C:DB:65:F6:D8:23:A0:8D: 1B:22:74:0C:B9:41:9E:57:5A:67:4C:CC:1F:E2:43:5F:C2:21:82:E6: D4:C1:66:6F:30:54:27:2E:1D:22:8C:65:7F:93:C8:1D:C0:51:F0:7D: 7A:96:3A:3B:3D:C4:6E:69:DF:83:8A:85:0D:35:15:F9:5E:89:0F:D5: 9E:6F:A1:5F:39:CE:2A:88:57:97:DF:42:5C:70:12:4E:91:9E:1A:92: 49:99:C3:7B:38:12:B0:3A:D0:92:38:45:C7:74:3C:66:0F:A1:9C:C2: 9F:DC:A2:1B:DF:20:BB:F5:A5:F0:10:D6:6F:4F:C1:90:00:C3:F9:D8: 42:96:D2:28:FD:DE:21:33:6C:F4:7F:18:B2:ED:F9:A6:A4:4A:A5:4F: 26:7C:C0:F7:8B:A9:B3:2F:5A:5B:E2:B8 Demsg entries: usb 4-3: new full-speed USB device number 6 using ohci-pci usb 4-3: New USB device found, idVendor=4348, idProduct=5523, bcdDevice= 2.50 usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 ch341 4-3:1.0: ch341-uart converter detected usb 4-3: ch341-uart converter now attached to ttyU
[Kernel-packages] [Bug 1919051] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1919051/+attachment/5476749/+files/ProcModules.txt -- 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/1919051 Title: ch341 USB-Serial converter only receives, does not send Status in linux package in Ubuntu: Confirmed Bug description: This device works flawlessly on Windows XP with native driver, both as a physical machine or inside a VM. It appears on XP's device management as "USB 2.0" name. On Ubuntu, Shorting pins 2 and 3 of DB9 connector does not give back characters sent (no echo), nor typed strings are sent to other RS232 devices, despite of communication settings. Characters from remote devices are correctly received. Using a null modem cable to other RS232 terminal shows that the local terminal receives, but does not transmit. Its worth to mention: passing through the device to a guest virtual machine (KVM) running Windows XP makes it work correctly with XP driver inside the guest OS. Bringing back the device stops transmitting. Only receive works. Tested with the version below: NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal Kernel: Linux host 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Device ID: ID 4348:5523 WinChipHead USB->RS 232 adapter with Prolifec PL 2303 chipset Modinfo: filename: /lib/modules/5.4.0-66-generic/kernel/drivers/usb/serial/ch341.ko license:GPL v2 srcversion: 8F5F64E72BDA4E76E6F4F4D alias: usb:v4348p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7522d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5512d*dc*dsc*dp*ic*isc*ip*in* depends:usbserial retpoline: Y intree: Y name: ch341 vermagic: 5.4.0-66-generic SMP mod_unload sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:1E:07:0D:94:23:77:98:99:05:31:F3:76:E8:6B:76:12:7C:83:9E:05 sig_hashalgo: sha512 signature: 50:CE:79:92:87:EA:82:77:A9:25:A3:B7:F2:B3:ED:63:FE:85:EB:61: 7A:31:C5:9E:E5:78:E5:44:C6:FE:5D:74:4A:60:B6:0A:94:3F:C3:70: 0B:6D:27:A6:89:F7:D2:AC:8E:71:AC:0D:AF:5D:3A:19:07:18:F9:7C: B8:3C:47:DF:18:4D:13:C9:F8:45:AC:81:19:B0:DE:57:16:1A:F5:C6: AC:41:7E:E7:F2:6D:29:9C:14:A3:04:F8:9B:DF:8D:2E:9F:34:44:18: A8:FF:C6:A4:AF:04:86:D5:6D:F2:4C:AD:D2:65:4C:63:0F:C1:82:E3: 28:20:F2:D4:80:86:1A:67:1D:A2:56:18:87:E2:AB:40:E6:6A:48:E5: D7:D2:6F:6F:DB:05:20:B2:76:81:5C:0C:36:02:37:E9:A2:08:4E:53: 5E:9C:18:03:50:11:2D:E4:62:74:6E:CB:42:67:25:22:0C:F6:55:D8: 6F:E3:5A:15:AC:10:B7:F2:B7:C9:20:6C:19:ED:CC:7D:CC:CB:48:3B: B0:5E:E3:ED:05:DF:DF:65:FF:19:AD:76:6E:40:D2:0B:F0:11:65:D5: 92:7D:C9:3A:32:BE:A8:13:CE:C1:DE:D9:73:0F:0A:0B:8A:08:55:2E: 41:9D:B9:9A:AD:EC:4C:7D:98:3A:52:38:DF:78:DE:33:F1:14:A2:1B: AC:93:FD:30:76:A5:7C:AF:13:16:B8:5E:0B:73:A7:1F:20:E4:54:44: 07:A2:11:7F:D7:0E:B3:1C:A9:AA:73:76:0E:89:E0:D5:74:39:66:2F: E8:14:93:EC:7A:B2:23:E0:CC:77:9F:CD:D9:99:CB:B0:14:21:1C:1F: 0C:E9:30:B8:C3:55:8F:49:FC:88:5D:EF:20:B9:0E:F2:88:28:5A:93: 08:4D:2B:76:64:85:D1:E0:1C:9C:4B:86:2C:DB:65:F6:D8:23:A0:8D: 1B:22:74:0C:B9:41:9E:57:5A:67:4C:CC:1F:E2:43:5F:C2:21:82:E6: D4:C1:66:6F:30:54:27:2E:1D:22:8C:65:7F:93:C8:1D:C0:51:F0:7D: 7A:96:3A:3B:3D:C4:6E:69:DF:83:8A:85:0D:35:15:F9:5E:89:0F:D5: 9E:6F:A1:5F:39:CE:2A:88:57:97:DF:42:5C:70:12:4E:91:9E:1A:92: 49:99:C3:7B:38:12:B0:3A:D0:92:38:45:C7:74:3C:66:0F:A1:9C:C2: 9F:DC:A2:1B:DF:20:BB:F5:A5:F0:10:D6:6F:4F:C1:90:00:C3:F9:D8: 42:96:D2:28:FD:DE:21:33:6C:F4:7F:18:B2:ED:F9:A6:A4:4A:A5:4F: 26:7C:C0:F7:8B:A9:B3:2F:5A:5B:E2:B8 Demsg entries: usb 4-3: new full-speed USB device number 6 using ohci-pci usb 4-3: New USB device found, idVendor=4348, idProduct=5523, bcdDevice= 2.50 usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 ch341 4-3:1.0: ch341-uart converter detected usb 4-3: ch341-uart converter now attached to ttyUSB0
[Kernel-packages] [Bug 1919051] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1919051/+attachment/5476747/+files/ProcEnviron.txt -- 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/1919051 Title: ch341 USB-Serial converter only receives, does not send Status in linux package in Ubuntu: Confirmed Bug description: This device works flawlessly on Windows XP with native driver, both as a physical machine or inside a VM. It appears on XP's device management as "USB 2.0" name. On Ubuntu, Shorting pins 2 and 3 of DB9 connector does not give back characters sent (no echo), nor typed strings are sent to other RS232 devices, despite of communication settings. Characters from remote devices are correctly received. Using a null modem cable to other RS232 terminal shows that the local terminal receives, but does not transmit. Its worth to mention: passing through the device to a guest virtual machine (KVM) running Windows XP makes it work correctly with XP driver inside the guest OS. Bringing back the device stops transmitting. Only receive works. Tested with the version below: NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal Kernel: Linux host 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Device ID: ID 4348:5523 WinChipHead USB->RS 232 adapter with Prolifec PL 2303 chipset Modinfo: filename: /lib/modules/5.4.0-66-generic/kernel/drivers/usb/serial/ch341.ko license:GPL v2 srcversion: 8F5F64E72BDA4E76E6F4F4D alias: usb:v4348p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7522d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5512d*dc*dsc*dp*ic*isc*ip*in* depends:usbserial retpoline: Y intree: Y name: ch341 vermagic: 5.4.0-66-generic SMP mod_unload sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:1E:07:0D:94:23:77:98:99:05:31:F3:76:E8:6B:76:12:7C:83:9E:05 sig_hashalgo: sha512 signature: 50:CE:79:92:87:EA:82:77:A9:25:A3:B7:F2:B3:ED:63:FE:85:EB:61: 7A:31:C5:9E:E5:78:E5:44:C6:FE:5D:74:4A:60:B6:0A:94:3F:C3:70: 0B:6D:27:A6:89:F7:D2:AC:8E:71:AC:0D:AF:5D:3A:19:07:18:F9:7C: B8:3C:47:DF:18:4D:13:C9:F8:45:AC:81:19:B0:DE:57:16:1A:F5:C6: AC:41:7E:E7:F2:6D:29:9C:14:A3:04:F8:9B:DF:8D:2E:9F:34:44:18: A8:FF:C6:A4:AF:04:86:D5:6D:F2:4C:AD:D2:65:4C:63:0F:C1:82:E3: 28:20:F2:D4:80:86:1A:67:1D:A2:56:18:87:E2:AB:40:E6:6A:48:E5: D7:D2:6F:6F:DB:05:20:B2:76:81:5C:0C:36:02:37:E9:A2:08:4E:53: 5E:9C:18:03:50:11:2D:E4:62:74:6E:CB:42:67:25:22:0C:F6:55:D8: 6F:E3:5A:15:AC:10:B7:F2:B7:C9:20:6C:19:ED:CC:7D:CC:CB:48:3B: B0:5E:E3:ED:05:DF:DF:65:FF:19:AD:76:6E:40:D2:0B:F0:11:65:D5: 92:7D:C9:3A:32:BE:A8:13:CE:C1:DE:D9:73:0F:0A:0B:8A:08:55:2E: 41:9D:B9:9A:AD:EC:4C:7D:98:3A:52:38:DF:78:DE:33:F1:14:A2:1B: AC:93:FD:30:76:A5:7C:AF:13:16:B8:5E:0B:73:A7:1F:20:E4:54:44: 07:A2:11:7F:D7:0E:B3:1C:A9:AA:73:76:0E:89:E0:D5:74:39:66:2F: E8:14:93:EC:7A:B2:23:E0:CC:77:9F:CD:D9:99:CB:B0:14:21:1C:1F: 0C:E9:30:B8:C3:55:8F:49:FC:88:5D:EF:20:B9:0E:F2:88:28:5A:93: 08:4D:2B:76:64:85:D1:E0:1C:9C:4B:86:2C:DB:65:F6:D8:23:A0:8D: 1B:22:74:0C:B9:41:9E:57:5A:67:4C:CC:1F:E2:43:5F:C2:21:82:E6: D4:C1:66:6F:30:54:27:2E:1D:22:8C:65:7F:93:C8:1D:C0:51:F0:7D: 7A:96:3A:3B:3D:C4:6E:69:DF:83:8A:85:0D:35:15:F9:5E:89:0F:D5: 9E:6F:A1:5F:39:CE:2A:88:57:97:DF:42:5C:70:12:4E:91:9E:1A:92: 49:99:C3:7B:38:12:B0:3A:D0:92:38:45:C7:74:3C:66:0F:A1:9C:C2: 9F:DC:A2:1B:DF:20:BB:F5:A5:F0:10:D6:6F:4F:C1:90:00:C3:F9:D8: 42:96:D2:28:FD:DE:21:33:6C:F4:7F:18:B2:ED:F9:A6:A4:4A:A5:4F: 26:7C:C0:F7:8B:A9:B3:2F:5A:5B:E2:B8 Demsg entries: usb 4-3: new full-speed USB device number 6 using ohci-pci usb 4-3: New USB device found, idVendor=4348, idProduct=5523, bcdDevice= 2.50 usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 ch341 4-3:1.0: ch341-uart converter detected usb 4-3: ch341-uart converter now attached to ttyUSB0
[Kernel-packages] [Bug 1919051] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1919051/+attachment/5476746/+files/ProcCpuinfoMinimal.txt -- 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/1919051 Title: ch341 USB-Serial converter only receives, does not send Status in linux package in Ubuntu: Confirmed Bug description: This device works flawlessly on Windows XP with native driver, both as a physical machine or inside a VM. It appears on XP's device management as "USB 2.0" name. On Ubuntu, Shorting pins 2 and 3 of DB9 connector does not give back characters sent (no echo), nor typed strings are sent to other RS232 devices, despite of communication settings. Characters from remote devices are correctly received. Using a null modem cable to other RS232 terminal shows that the local terminal receives, but does not transmit. Its worth to mention: passing through the device to a guest virtual machine (KVM) running Windows XP makes it work correctly with XP driver inside the guest OS. Bringing back the device stops transmitting. Only receive works. Tested with the version below: NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal Kernel: Linux host 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Device ID: ID 4348:5523 WinChipHead USB->RS 232 adapter with Prolifec PL 2303 chipset Modinfo: filename: /lib/modules/5.4.0-66-generic/kernel/drivers/usb/serial/ch341.ko license:GPL v2 srcversion: 8F5F64E72BDA4E76E6F4F4D alias: usb:v4348p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7522d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5512d*dc*dsc*dp*ic*isc*ip*in* depends:usbserial retpoline: Y intree: Y name: ch341 vermagic: 5.4.0-66-generic SMP mod_unload sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:1E:07:0D:94:23:77:98:99:05:31:F3:76:E8:6B:76:12:7C:83:9E:05 sig_hashalgo: sha512 signature: 50:CE:79:92:87:EA:82:77:A9:25:A3:B7:F2:B3:ED:63:FE:85:EB:61: 7A:31:C5:9E:E5:78:E5:44:C6:FE:5D:74:4A:60:B6:0A:94:3F:C3:70: 0B:6D:27:A6:89:F7:D2:AC:8E:71:AC:0D:AF:5D:3A:19:07:18:F9:7C: B8:3C:47:DF:18:4D:13:C9:F8:45:AC:81:19:B0:DE:57:16:1A:F5:C6: AC:41:7E:E7:F2:6D:29:9C:14:A3:04:F8:9B:DF:8D:2E:9F:34:44:18: A8:FF:C6:A4:AF:04:86:D5:6D:F2:4C:AD:D2:65:4C:63:0F:C1:82:E3: 28:20:F2:D4:80:86:1A:67:1D:A2:56:18:87:E2:AB:40:E6:6A:48:E5: D7:D2:6F:6F:DB:05:20:B2:76:81:5C:0C:36:02:37:E9:A2:08:4E:53: 5E:9C:18:03:50:11:2D:E4:62:74:6E:CB:42:67:25:22:0C:F6:55:D8: 6F:E3:5A:15:AC:10:B7:F2:B7:C9:20:6C:19:ED:CC:7D:CC:CB:48:3B: B0:5E:E3:ED:05:DF:DF:65:FF:19:AD:76:6E:40:D2:0B:F0:11:65:D5: 92:7D:C9:3A:32:BE:A8:13:CE:C1:DE:D9:73:0F:0A:0B:8A:08:55:2E: 41:9D:B9:9A:AD:EC:4C:7D:98:3A:52:38:DF:78:DE:33:F1:14:A2:1B: AC:93:FD:30:76:A5:7C:AF:13:16:B8:5E:0B:73:A7:1F:20:E4:54:44: 07:A2:11:7F:D7:0E:B3:1C:A9:AA:73:76:0E:89:E0:D5:74:39:66:2F: E8:14:93:EC:7A:B2:23:E0:CC:77:9F:CD:D9:99:CB:B0:14:21:1C:1F: 0C:E9:30:B8:C3:55:8F:49:FC:88:5D:EF:20:B9:0E:F2:88:28:5A:93: 08:4D:2B:76:64:85:D1:E0:1C:9C:4B:86:2C:DB:65:F6:D8:23:A0:8D: 1B:22:74:0C:B9:41:9E:57:5A:67:4C:CC:1F:E2:43:5F:C2:21:82:E6: D4:C1:66:6F:30:54:27:2E:1D:22:8C:65:7F:93:C8:1D:C0:51:F0:7D: 7A:96:3A:3B:3D:C4:6E:69:DF:83:8A:85:0D:35:15:F9:5E:89:0F:D5: 9E:6F:A1:5F:39:CE:2A:88:57:97:DF:42:5C:70:12:4E:91:9E:1A:92: 49:99:C3:7B:38:12:B0:3A:D0:92:38:45:C7:74:3C:66:0F:A1:9C:C2: 9F:DC:A2:1B:DF:20:BB:F5:A5:F0:10:D6:6F:4F:C1:90:00:C3:F9:D8: 42:96:D2:28:FD:DE:21:33:6C:F4:7F:18:B2:ED:F9:A6:A4:4A:A5:4F: 26:7C:C0:F7:8B:A9:B3:2F:5A:5B:E2:B8 Demsg entries: usb 4-3: new full-speed USB device number 6 using ohci-pci usb 4-3: New USB device found, idVendor=4348, idProduct=5523, bcdDevice= 2.50 usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 ch341 4-3:1.0: ch341-uart converter detected usb 4-3: ch341-uart converter now attached
[Kernel-packages] [Bug 1919051] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1919051/+attachment/5476745/+files/ProcCpuinfo.txt -- 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/1919051 Title: ch341 USB-Serial converter only receives, does not send Status in linux package in Ubuntu: Confirmed Bug description: This device works flawlessly on Windows XP with native driver, both as a physical machine or inside a VM. It appears on XP's device management as "USB 2.0" name. On Ubuntu, Shorting pins 2 and 3 of DB9 connector does not give back characters sent (no echo), nor typed strings are sent to other RS232 devices, despite of communication settings. Characters from remote devices are correctly received. Using a null modem cable to other RS232 terminal shows that the local terminal receives, but does not transmit. Its worth to mention: passing through the device to a guest virtual machine (KVM) running Windows XP makes it work correctly with XP driver inside the guest OS. Bringing back the device stops transmitting. Only receive works. Tested with the version below: NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal Kernel: Linux host 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Device ID: ID 4348:5523 WinChipHead USB->RS 232 adapter with Prolifec PL 2303 chipset Modinfo: filename: /lib/modules/5.4.0-66-generic/kernel/drivers/usb/serial/ch341.ko license:GPL v2 srcversion: 8F5F64E72BDA4E76E6F4F4D alias: usb:v4348p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7522d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5512d*dc*dsc*dp*ic*isc*ip*in* depends:usbserial retpoline: Y intree: Y name: ch341 vermagic: 5.4.0-66-generic SMP mod_unload sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:1E:07:0D:94:23:77:98:99:05:31:F3:76:E8:6B:76:12:7C:83:9E:05 sig_hashalgo: sha512 signature: 50:CE:79:92:87:EA:82:77:A9:25:A3:B7:F2:B3:ED:63:FE:85:EB:61: 7A:31:C5:9E:E5:78:E5:44:C6:FE:5D:74:4A:60:B6:0A:94:3F:C3:70: 0B:6D:27:A6:89:F7:D2:AC:8E:71:AC:0D:AF:5D:3A:19:07:18:F9:7C: B8:3C:47:DF:18:4D:13:C9:F8:45:AC:81:19:B0:DE:57:16:1A:F5:C6: AC:41:7E:E7:F2:6D:29:9C:14:A3:04:F8:9B:DF:8D:2E:9F:34:44:18: A8:FF:C6:A4:AF:04:86:D5:6D:F2:4C:AD:D2:65:4C:63:0F:C1:82:E3: 28:20:F2:D4:80:86:1A:67:1D:A2:56:18:87:E2:AB:40:E6:6A:48:E5: D7:D2:6F:6F:DB:05:20:B2:76:81:5C:0C:36:02:37:E9:A2:08:4E:53: 5E:9C:18:03:50:11:2D:E4:62:74:6E:CB:42:67:25:22:0C:F6:55:D8: 6F:E3:5A:15:AC:10:B7:F2:B7:C9:20:6C:19:ED:CC:7D:CC:CB:48:3B: B0:5E:E3:ED:05:DF:DF:65:FF:19:AD:76:6E:40:D2:0B:F0:11:65:D5: 92:7D:C9:3A:32:BE:A8:13:CE:C1:DE:D9:73:0F:0A:0B:8A:08:55:2E: 41:9D:B9:9A:AD:EC:4C:7D:98:3A:52:38:DF:78:DE:33:F1:14:A2:1B: AC:93:FD:30:76:A5:7C:AF:13:16:B8:5E:0B:73:A7:1F:20:E4:54:44: 07:A2:11:7F:D7:0E:B3:1C:A9:AA:73:76:0E:89:E0:D5:74:39:66:2F: E8:14:93:EC:7A:B2:23:E0:CC:77:9F:CD:D9:99:CB:B0:14:21:1C:1F: 0C:E9:30:B8:C3:55:8F:49:FC:88:5D:EF:20:B9:0E:F2:88:28:5A:93: 08:4D:2B:76:64:85:D1:E0:1C:9C:4B:86:2C:DB:65:F6:D8:23:A0:8D: 1B:22:74:0C:B9:41:9E:57:5A:67:4C:CC:1F:E2:43:5F:C2:21:82:E6: D4:C1:66:6F:30:54:27:2E:1D:22:8C:65:7F:93:C8:1D:C0:51:F0:7D: 7A:96:3A:3B:3D:C4:6E:69:DF:83:8A:85:0D:35:15:F9:5E:89:0F:D5: 9E:6F:A1:5F:39:CE:2A:88:57:97:DF:42:5C:70:12:4E:91:9E:1A:92: 49:99:C3:7B:38:12:B0:3A:D0:92:38:45:C7:74:3C:66:0F:A1:9C:C2: 9F:DC:A2:1B:DF:20:BB:F5:A5:F0:10:D6:6F:4F:C1:90:00:C3:F9:D8: 42:96:D2:28:FD:DE:21:33:6C:F4:7F:18:B2:ED:F9:A6:A4:4A:A5:4F: 26:7C:C0:F7:8B:A9:B3:2F:5A:5B:E2:B8 Demsg entries: usb 4-3: new full-speed USB device number 6 using ohci-pci usb 4-3: New USB device found, idVendor=4348, idProduct=5523, bcdDevice= 2.50 usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 ch341 4-3:1.0: ch341-uart converter detected usb 4-3: ch341-uart converter now attached to ttyUSB0
[Kernel-packages] [Bug 1919051] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1919051/+attachment/5476744/+files/Lsusb-v.txt -- 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/1919051 Title: ch341 USB-Serial converter only receives, does not send Status in linux package in Ubuntu: Confirmed Bug description: This device works flawlessly on Windows XP with native driver, both as a physical machine or inside a VM. It appears on XP's device management as "USB 2.0" name. On Ubuntu, Shorting pins 2 and 3 of DB9 connector does not give back characters sent (no echo), nor typed strings are sent to other RS232 devices, despite of communication settings. Characters from remote devices are correctly received. Using a null modem cable to other RS232 terminal shows that the local terminal receives, but does not transmit. Its worth to mention: passing through the device to a guest virtual machine (KVM) running Windows XP makes it work correctly with XP driver inside the guest OS. Bringing back the device stops transmitting. Only receive works. Tested with the version below: NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal Kernel: Linux host 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Device ID: ID 4348:5523 WinChipHead USB->RS 232 adapter with Prolifec PL 2303 chipset Modinfo: filename: /lib/modules/5.4.0-66-generic/kernel/drivers/usb/serial/ch341.ko license:GPL v2 srcversion: 8F5F64E72BDA4E76E6F4F4D alias: usb:v4348p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7522d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5512d*dc*dsc*dp*ic*isc*ip*in* depends:usbserial retpoline: Y intree: Y name: ch341 vermagic: 5.4.0-66-generic SMP mod_unload sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:1E:07:0D:94:23:77:98:99:05:31:F3:76:E8:6B:76:12:7C:83:9E:05 sig_hashalgo: sha512 signature: 50:CE:79:92:87:EA:82:77:A9:25:A3:B7:F2:B3:ED:63:FE:85:EB:61: 7A:31:C5:9E:E5:78:E5:44:C6:FE:5D:74:4A:60:B6:0A:94:3F:C3:70: 0B:6D:27:A6:89:F7:D2:AC:8E:71:AC:0D:AF:5D:3A:19:07:18:F9:7C: B8:3C:47:DF:18:4D:13:C9:F8:45:AC:81:19:B0:DE:57:16:1A:F5:C6: AC:41:7E:E7:F2:6D:29:9C:14:A3:04:F8:9B:DF:8D:2E:9F:34:44:18: A8:FF:C6:A4:AF:04:86:D5:6D:F2:4C:AD:D2:65:4C:63:0F:C1:82:E3: 28:20:F2:D4:80:86:1A:67:1D:A2:56:18:87:E2:AB:40:E6:6A:48:E5: D7:D2:6F:6F:DB:05:20:B2:76:81:5C:0C:36:02:37:E9:A2:08:4E:53: 5E:9C:18:03:50:11:2D:E4:62:74:6E:CB:42:67:25:22:0C:F6:55:D8: 6F:E3:5A:15:AC:10:B7:F2:B7:C9:20:6C:19:ED:CC:7D:CC:CB:48:3B: B0:5E:E3:ED:05:DF:DF:65:FF:19:AD:76:6E:40:D2:0B:F0:11:65:D5: 92:7D:C9:3A:32:BE:A8:13:CE:C1:DE:D9:73:0F:0A:0B:8A:08:55:2E: 41:9D:B9:9A:AD:EC:4C:7D:98:3A:52:38:DF:78:DE:33:F1:14:A2:1B: AC:93:FD:30:76:A5:7C:AF:13:16:B8:5E:0B:73:A7:1F:20:E4:54:44: 07:A2:11:7F:D7:0E:B3:1C:A9:AA:73:76:0E:89:E0:D5:74:39:66:2F: E8:14:93:EC:7A:B2:23:E0:CC:77:9F:CD:D9:99:CB:B0:14:21:1C:1F: 0C:E9:30:B8:C3:55:8F:49:FC:88:5D:EF:20:B9:0E:F2:88:28:5A:93: 08:4D:2B:76:64:85:D1:E0:1C:9C:4B:86:2C:DB:65:F6:D8:23:A0:8D: 1B:22:74:0C:B9:41:9E:57:5A:67:4C:CC:1F:E2:43:5F:C2:21:82:E6: D4:C1:66:6F:30:54:27:2E:1D:22:8C:65:7F:93:C8:1D:C0:51:F0:7D: 7A:96:3A:3B:3D:C4:6E:69:DF:83:8A:85:0D:35:15:F9:5E:89:0F:D5: 9E:6F:A1:5F:39:CE:2A:88:57:97:DF:42:5C:70:12:4E:91:9E:1A:92: 49:99:C3:7B:38:12:B0:3A:D0:92:38:45:C7:74:3C:66:0F:A1:9C:C2: 9F:DC:A2:1B:DF:20:BB:F5:A5:F0:10:D6:6F:4F:C1:90:00:C3:F9:D8: 42:96:D2:28:FD:DE:21:33:6C:F4:7F:18:B2:ED:F9:A6:A4:4A:A5:4F: 26:7C:C0:F7:8B:A9:B3:2F:5A:5B:E2:B8 Demsg entries: usb 4-3: new full-speed USB device number 6 using ohci-pci usb 4-3: New USB device found, idVendor=4348, idProduct=5523, bcdDevice= 2.50 usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 ch341 4-3:1.0: ch341-uart converter detected usb 4-3: ch341-uart converter now attached to ttyUSB0 --- P
[Kernel-packages] [Bug 1919051] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1919051/+attachment/5476743/+files/Lsusb-t.txt -- 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/1919051 Title: ch341 USB-Serial converter only receives, does not send Status in linux package in Ubuntu: Confirmed Bug description: This device works flawlessly on Windows XP with native driver, both as a physical machine or inside a VM. It appears on XP's device management as "USB 2.0" name. On Ubuntu, Shorting pins 2 and 3 of DB9 connector does not give back characters sent (no echo), nor typed strings are sent to other RS232 devices, despite of communication settings. Characters from remote devices are correctly received. Using a null modem cable to other RS232 terminal shows that the local terminal receives, but does not transmit. Its worth to mention: passing through the device to a guest virtual machine (KVM) running Windows XP makes it work correctly with XP driver inside the guest OS. Bringing back the device stops transmitting. Only receive works. Tested with the version below: NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal Kernel: Linux host 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Device ID: ID 4348:5523 WinChipHead USB->RS 232 adapter with Prolifec PL 2303 chipset Modinfo: filename: /lib/modules/5.4.0-66-generic/kernel/drivers/usb/serial/ch341.ko license:GPL v2 srcversion: 8F5F64E72BDA4E76E6F4F4D alias: usb:v4348p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7522d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5512d*dc*dsc*dp*ic*isc*ip*in* depends:usbserial retpoline: Y intree: Y name: ch341 vermagic: 5.4.0-66-generic SMP mod_unload sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:1E:07:0D:94:23:77:98:99:05:31:F3:76:E8:6B:76:12:7C:83:9E:05 sig_hashalgo: sha512 signature: 50:CE:79:92:87:EA:82:77:A9:25:A3:B7:F2:B3:ED:63:FE:85:EB:61: 7A:31:C5:9E:E5:78:E5:44:C6:FE:5D:74:4A:60:B6:0A:94:3F:C3:70: 0B:6D:27:A6:89:F7:D2:AC:8E:71:AC:0D:AF:5D:3A:19:07:18:F9:7C: B8:3C:47:DF:18:4D:13:C9:F8:45:AC:81:19:B0:DE:57:16:1A:F5:C6: AC:41:7E:E7:F2:6D:29:9C:14:A3:04:F8:9B:DF:8D:2E:9F:34:44:18: A8:FF:C6:A4:AF:04:86:D5:6D:F2:4C:AD:D2:65:4C:63:0F:C1:82:E3: 28:20:F2:D4:80:86:1A:67:1D:A2:56:18:87:E2:AB:40:E6:6A:48:E5: D7:D2:6F:6F:DB:05:20:B2:76:81:5C:0C:36:02:37:E9:A2:08:4E:53: 5E:9C:18:03:50:11:2D:E4:62:74:6E:CB:42:67:25:22:0C:F6:55:D8: 6F:E3:5A:15:AC:10:B7:F2:B7:C9:20:6C:19:ED:CC:7D:CC:CB:48:3B: B0:5E:E3:ED:05:DF:DF:65:FF:19:AD:76:6E:40:D2:0B:F0:11:65:D5: 92:7D:C9:3A:32:BE:A8:13:CE:C1:DE:D9:73:0F:0A:0B:8A:08:55:2E: 41:9D:B9:9A:AD:EC:4C:7D:98:3A:52:38:DF:78:DE:33:F1:14:A2:1B: AC:93:FD:30:76:A5:7C:AF:13:16:B8:5E:0B:73:A7:1F:20:E4:54:44: 07:A2:11:7F:D7:0E:B3:1C:A9:AA:73:76:0E:89:E0:D5:74:39:66:2F: E8:14:93:EC:7A:B2:23:E0:CC:77:9F:CD:D9:99:CB:B0:14:21:1C:1F: 0C:E9:30:B8:C3:55:8F:49:FC:88:5D:EF:20:B9:0E:F2:88:28:5A:93: 08:4D:2B:76:64:85:D1:E0:1C:9C:4B:86:2C:DB:65:F6:D8:23:A0:8D: 1B:22:74:0C:B9:41:9E:57:5A:67:4C:CC:1F:E2:43:5F:C2:21:82:E6: D4:C1:66:6F:30:54:27:2E:1D:22:8C:65:7F:93:C8:1D:C0:51:F0:7D: 7A:96:3A:3B:3D:C4:6E:69:DF:83:8A:85:0D:35:15:F9:5E:89:0F:D5: 9E:6F:A1:5F:39:CE:2A:88:57:97:DF:42:5C:70:12:4E:91:9E:1A:92: 49:99:C3:7B:38:12:B0:3A:D0:92:38:45:C7:74:3C:66:0F:A1:9C:C2: 9F:DC:A2:1B:DF:20:BB:F5:A5:F0:10:D6:6F:4F:C1:90:00:C3:F9:D8: 42:96:D2:28:FD:DE:21:33:6C:F4:7F:18:B2:ED:F9:A6:A4:4A:A5:4F: 26:7C:C0:F7:8B:A9:B3:2F:5A:5B:E2:B8 Demsg entries: usb 4-3: new full-speed USB device number 6 using ohci-pci usb 4-3: New USB device found, idVendor=4348, idProduct=5523, bcdDevice= 2.50 usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 ch341 4-3:1.0: ch341-uart converter detected usb 4-3: ch341-uart converter now attached to ttyUSB0 --- P
[Kernel-packages] [Bug 1919051] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1919051/+attachment/5476742/+files/Lsusb.txt -- 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/1919051 Title: ch341 USB-Serial converter only receives, does not send Status in linux package in Ubuntu: Confirmed Bug description: This device works flawlessly on Windows XP with native driver, both as a physical machine or inside a VM. It appears on XP's device management as "USB 2.0" name. On Ubuntu, Shorting pins 2 and 3 of DB9 connector does not give back characters sent (no echo), nor typed strings are sent to other RS232 devices, despite of communication settings. Characters from remote devices are correctly received. Using a null modem cable to other RS232 terminal shows that the local terminal receives, but does not transmit. Its worth to mention: passing through the device to a guest virtual machine (KVM) running Windows XP makes it work correctly with XP driver inside the guest OS. Bringing back the device stops transmitting. Only receive works. Tested with the version below: NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal Kernel: Linux host 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Device ID: ID 4348:5523 WinChipHead USB->RS 232 adapter with Prolifec PL 2303 chipset Modinfo: filename: /lib/modules/5.4.0-66-generic/kernel/drivers/usb/serial/ch341.ko license:GPL v2 srcversion: 8F5F64E72BDA4E76E6F4F4D alias: usb:v4348p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7522d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5512d*dc*dsc*dp*ic*isc*ip*in* depends:usbserial retpoline: Y intree: Y name: ch341 vermagic: 5.4.0-66-generic SMP mod_unload sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:1E:07:0D:94:23:77:98:99:05:31:F3:76:E8:6B:76:12:7C:83:9E:05 sig_hashalgo: sha512 signature: 50:CE:79:92:87:EA:82:77:A9:25:A3:B7:F2:B3:ED:63:FE:85:EB:61: 7A:31:C5:9E:E5:78:E5:44:C6:FE:5D:74:4A:60:B6:0A:94:3F:C3:70: 0B:6D:27:A6:89:F7:D2:AC:8E:71:AC:0D:AF:5D:3A:19:07:18:F9:7C: B8:3C:47:DF:18:4D:13:C9:F8:45:AC:81:19:B0:DE:57:16:1A:F5:C6: AC:41:7E:E7:F2:6D:29:9C:14:A3:04:F8:9B:DF:8D:2E:9F:34:44:18: A8:FF:C6:A4:AF:04:86:D5:6D:F2:4C:AD:D2:65:4C:63:0F:C1:82:E3: 28:20:F2:D4:80:86:1A:67:1D:A2:56:18:87:E2:AB:40:E6:6A:48:E5: D7:D2:6F:6F:DB:05:20:B2:76:81:5C:0C:36:02:37:E9:A2:08:4E:53: 5E:9C:18:03:50:11:2D:E4:62:74:6E:CB:42:67:25:22:0C:F6:55:D8: 6F:E3:5A:15:AC:10:B7:F2:B7:C9:20:6C:19:ED:CC:7D:CC:CB:48:3B: B0:5E:E3:ED:05:DF:DF:65:FF:19:AD:76:6E:40:D2:0B:F0:11:65:D5: 92:7D:C9:3A:32:BE:A8:13:CE:C1:DE:D9:73:0F:0A:0B:8A:08:55:2E: 41:9D:B9:9A:AD:EC:4C:7D:98:3A:52:38:DF:78:DE:33:F1:14:A2:1B: AC:93:FD:30:76:A5:7C:AF:13:16:B8:5E:0B:73:A7:1F:20:E4:54:44: 07:A2:11:7F:D7:0E:B3:1C:A9:AA:73:76:0E:89:E0:D5:74:39:66:2F: E8:14:93:EC:7A:B2:23:E0:CC:77:9F:CD:D9:99:CB:B0:14:21:1C:1F: 0C:E9:30:B8:C3:55:8F:49:FC:88:5D:EF:20:B9:0E:F2:88:28:5A:93: 08:4D:2B:76:64:85:D1:E0:1C:9C:4B:86:2C:DB:65:F6:D8:23:A0:8D: 1B:22:74:0C:B9:41:9E:57:5A:67:4C:CC:1F:E2:43:5F:C2:21:82:E6: D4:C1:66:6F:30:54:27:2E:1D:22:8C:65:7F:93:C8:1D:C0:51:F0:7D: 7A:96:3A:3B:3D:C4:6E:69:DF:83:8A:85:0D:35:15:F9:5E:89:0F:D5: 9E:6F:A1:5F:39:CE:2A:88:57:97:DF:42:5C:70:12:4E:91:9E:1A:92: 49:99:C3:7B:38:12:B0:3A:D0:92:38:45:C7:74:3C:66:0F:A1:9C:C2: 9F:DC:A2:1B:DF:20:BB:F5:A5:F0:10:D6:6F:4F:C1:90:00:C3:F9:D8: 42:96:D2:28:FD:DE:21:33:6C:F4:7F:18:B2:ED:F9:A6:A4:4A:A5:4F: 26:7C:C0:F7:8B:A9:B3:2F:5A:5B:E2:B8 Demsg entries: usb 4-3: new full-speed USB device number 6 using ohci-pci usb 4-3: New USB device found, idVendor=4348, idProduct=5523, bcdDevice= 2.50 usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 ch341 4-3:1.0: ch341-uart converter detected usb 4-3: ch341-uart converter now attached to ttyUSB0 --- Proble
[Kernel-packages] [Bug 1919051] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1919051/+attachment/5476741/+files/Lspci-vt.txt -- 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/1919051 Title: ch341 USB-Serial converter only receives, does not send Status in linux package in Ubuntu: Confirmed Bug description: This device works flawlessly on Windows XP with native driver, both as a physical machine or inside a VM. It appears on XP's device management as "USB 2.0" name. On Ubuntu, Shorting pins 2 and 3 of DB9 connector does not give back characters sent (no echo), nor typed strings are sent to other RS232 devices, despite of communication settings. Characters from remote devices are correctly received. Using a null modem cable to other RS232 terminal shows that the local terminal receives, but does not transmit. Its worth to mention: passing through the device to a guest virtual machine (KVM) running Windows XP makes it work correctly with XP driver inside the guest OS. Bringing back the device stops transmitting. Only receive works. Tested with the version below: NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal Kernel: Linux host 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Device ID: ID 4348:5523 WinChipHead USB->RS 232 adapter with Prolifec PL 2303 chipset Modinfo: filename: /lib/modules/5.4.0-66-generic/kernel/drivers/usb/serial/ch341.ko license:GPL v2 srcversion: 8F5F64E72BDA4E76E6F4F4D alias: usb:v4348p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7522d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5512d*dc*dsc*dp*ic*isc*ip*in* depends:usbserial retpoline: Y intree: Y name: ch341 vermagic: 5.4.0-66-generic SMP mod_unload sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:1E:07:0D:94:23:77:98:99:05:31:F3:76:E8:6B:76:12:7C:83:9E:05 sig_hashalgo: sha512 signature: 50:CE:79:92:87:EA:82:77:A9:25:A3:B7:F2:B3:ED:63:FE:85:EB:61: 7A:31:C5:9E:E5:78:E5:44:C6:FE:5D:74:4A:60:B6:0A:94:3F:C3:70: 0B:6D:27:A6:89:F7:D2:AC:8E:71:AC:0D:AF:5D:3A:19:07:18:F9:7C: B8:3C:47:DF:18:4D:13:C9:F8:45:AC:81:19:B0:DE:57:16:1A:F5:C6: AC:41:7E:E7:F2:6D:29:9C:14:A3:04:F8:9B:DF:8D:2E:9F:34:44:18: A8:FF:C6:A4:AF:04:86:D5:6D:F2:4C:AD:D2:65:4C:63:0F:C1:82:E3: 28:20:F2:D4:80:86:1A:67:1D:A2:56:18:87:E2:AB:40:E6:6A:48:E5: D7:D2:6F:6F:DB:05:20:B2:76:81:5C:0C:36:02:37:E9:A2:08:4E:53: 5E:9C:18:03:50:11:2D:E4:62:74:6E:CB:42:67:25:22:0C:F6:55:D8: 6F:E3:5A:15:AC:10:B7:F2:B7:C9:20:6C:19:ED:CC:7D:CC:CB:48:3B: B0:5E:E3:ED:05:DF:DF:65:FF:19:AD:76:6E:40:D2:0B:F0:11:65:D5: 92:7D:C9:3A:32:BE:A8:13:CE:C1:DE:D9:73:0F:0A:0B:8A:08:55:2E: 41:9D:B9:9A:AD:EC:4C:7D:98:3A:52:38:DF:78:DE:33:F1:14:A2:1B: AC:93:FD:30:76:A5:7C:AF:13:16:B8:5E:0B:73:A7:1F:20:E4:54:44: 07:A2:11:7F:D7:0E:B3:1C:A9:AA:73:76:0E:89:E0:D5:74:39:66:2F: E8:14:93:EC:7A:B2:23:E0:CC:77:9F:CD:D9:99:CB:B0:14:21:1C:1F: 0C:E9:30:B8:C3:55:8F:49:FC:88:5D:EF:20:B9:0E:F2:88:28:5A:93: 08:4D:2B:76:64:85:D1:E0:1C:9C:4B:86:2C:DB:65:F6:D8:23:A0:8D: 1B:22:74:0C:B9:41:9E:57:5A:67:4C:CC:1F:E2:43:5F:C2:21:82:E6: D4:C1:66:6F:30:54:27:2E:1D:22:8C:65:7F:93:C8:1D:C0:51:F0:7D: 7A:96:3A:3B:3D:C4:6E:69:DF:83:8A:85:0D:35:15:F9:5E:89:0F:D5: 9E:6F:A1:5F:39:CE:2A:88:57:97:DF:42:5C:70:12:4E:91:9E:1A:92: 49:99:C3:7B:38:12:B0:3A:D0:92:38:45:C7:74:3C:66:0F:A1:9C:C2: 9F:DC:A2:1B:DF:20:BB:F5:A5:F0:10:D6:6F:4F:C1:90:00:C3:F9:D8: 42:96:D2:28:FD:DE:21:33:6C:F4:7F:18:B2:ED:F9:A6:A4:4A:A5:4F: 26:7C:C0:F7:8B:A9:B3:2F:5A:5B:E2:B8 Demsg entries: usb 4-3: new full-speed USB device number 6 using ohci-pci usb 4-3: New USB device found, idVendor=4348, idProduct=5523, bcdDevice= 2.50 usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 ch341 4-3:1.0: ch341-uart converter detected usb 4-3: ch341-uart converter now attached to ttyUSB0 ---
[Kernel-packages] [Bug 1919051] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1919051/+attachment/5476740/+files/Lspci.txt -- 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/1919051 Title: ch341 USB-Serial converter only receives, does not send Status in linux package in Ubuntu: Confirmed Bug description: This device works flawlessly on Windows XP with native driver, both as a physical machine or inside a VM. It appears on XP's device management as "USB 2.0" name. On Ubuntu, Shorting pins 2 and 3 of DB9 connector does not give back characters sent (no echo), nor typed strings are sent to other RS232 devices, despite of communication settings. Characters from remote devices are correctly received. Using a null modem cable to other RS232 terminal shows that the local terminal receives, but does not transmit. Its worth to mention: passing through the device to a guest virtual machine (KVM) running Windows XP makes it work correctly with XP driver inside the guest OS. Bringing back the device stops transmitting. Only receive works. Tested with the version below: NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal Kernel: Linux host 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Device ID: ID 4348:5523 WinChipHead USB->RS 232 adapter with Prolifec PL 2303 chipset Modinfo: filename: /lib/modules/5.4.0-66-generic/kernel/drivers/usb/serial/ch341.ko license:GPL v2 srcversion: 8F5F64E72BDA4E76E6F4F4D alias: usb:v4348p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7522d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5512d*dc*dsc*dp*ic*isc*ip*in* depends:usbserial retpoline: Y intree: Y name: ch341 vermagic: 5.4.0-66-generic SMP mod_unload sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:1E:07:0D:94:23:77:98:99:05:31:F3:76:E8:6B:76:12:7C:83:9E:05 sig_hashalgo: sha512 signature: 50:CE:79:92:87:EA:82:77:A9:25:A3:B7:F2:B3:ED:63:FE:85:EB:61: 7A:31:C5:9E:E5:78:E5:44:C6:FE:5D:74:4A:60:B6:0A:94:3F:C3:70: 0B:6D:27:A6:89:F7:D2:AC:8E:71:AC:0D:AF:5D:3A:19:07:18:F9:7C: B8:3C:47:DF:18:4D:13:C9:F8:45:AC:81:19:B0:DE:57:16:1A:F5:C6: AC:41:7E:E7:F2:6D:29:9C:14:A3:04:F8:9B:DF:8D:2E:9F:34:44:18: A8:FF:C6:A4:AF:04:86:D5:6D:F2:4C:AD:D2:65:4C:63:0F:C1:82:E3: 28:20:F2:D4:80:86:1A:67:1D:A2:56:18:87:E2:AB:40:E6:6A:48:E5: D7:D2:6F:6F:DB:05:20:B2:76:81:5C:0C:36:02:37:E9:A2:08:4E:53: 5E:9C:18:03:50:11:2D:E4:62:74:6E:CB:42:67:25:22:0C:F6:55:D8: 6F:E3:5A:15:AC:10:B7:F2:B7:C9:20:6C:19:ED:CC:7D:CC:CB:48:3B: B0:5E:E3:ED:05:DF:DF:65:FF:19:AD:76:6E:40:D2:0B:F0:11:65:D5: 92:7D:C9:3A:32:BE:A8:13:CE:C1:DE:D9:73:0F:0A:0B:8A:08:55:2E: 41:9D:B9:9A:AD:EC:4C:7D:98:3A:52:38:DF:78:DE:33:F1:14:A2:1B: AC:93:FD:30:76:A5:7C:AF:13:16:B8:5E:0B:73:A7:1F:20:E4:54:44: 07:A2:11:7F:D7:0E:B3:1C:A9:AA:73:76:0E:89:E0:D5:74:39:66:2F: E8:14:93:EC:7A:B2:23:E0:CC:77:9F:CD:D9:99:CB:B0:14:21:1C:1F: 0C:E9:30:B8:C3:55:8F:49:FC:88:5D:EF:20:B9:0E:F2:88:28:5A:93: 08:4D:2B:76:64:85:D1:E0:1C:9C:4B:86:2C:DB:65:F6:D8:23:A0:8D: 1B:22:74:0C:B9:41:9E:57:5A:67:4C:CC:1F:E2:43:5F:C2:21:82:E6: D4:C1:66:6F:30:54:27:2E:1D:22:8C:65:7F:93:C8:1D:C0:51:F0:7D: 7A:96:3A:3B:3D:C4:6E:69:DF:83:8A:85:0D:35:15:F9:5E:89:0F:D5: 9E:6F:A1:5F:39:CE:2A:88:57:97:DF:42:5C:70:12:4E:91:9E:1A:92: 49:99:C3:7B:38:12:B0:3A:D0:92:38:45:C7:74:3C:66:0F:A1:9C:C2: 9F:DC:A2:1B:DF:20:BB:F5:A5:F0:10:D6:6F:4F:C1:90:00:C3:F9:D8: 42:96:D2:28:FD:DE:21:33:6C:F4:7F:18:B2:ED:F9:A6:A4:4A:A5:4F: 26:7C:C0:F7:8B:A9:B3:2F:5A:5B:E2:B8 Demsg entries: usb 4-3: new full-speed USB device number 6 using ohci-pci usb 4-3: New USB device found, idVendor=4348, idProduct=5523, bcdDevice= 2.50 usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 ch341 4-3:1.0: ch341-uart converter detected usb 4-3: ch341-uart converter now attached to ttyUSB0 --- Proble
[Kernel-packages] [Bug 1919051] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1919051/+attachment/5476739/+files/IwConfig.txt -- 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/1919051 Title: ch341 USB-Serial converter only receives, does not send Status in linux package in Ubuntu: Confirmed Bug description: This device works flawlessly on Windows XP with native driver, both as a physical machine or inside a VM. It appears on XP's device management as "USB 2.0" name. On Ubuntu, Shorting pins 2 and 3 of DB9 connector does not give back characters sent (no echo), nor typed strings are sent to other RS232 devices, despite of communication settings. Characters from remote devices are correctly received. Using a null modem cable to other RS232 terminal shows that the local terminal receives, but does not transmit. Its worth to mention: passing through the device to a guest virtual machine (KVM) running Windows XP makes it work correctly with XP driver inside the guest OS. Bringing back the device stops transmitting. Only receive works. Tested with the version below: NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal Kernel: Linux host 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Device ID: ID 4348:5523 WinChipHead USB->RS 232 adapter with Prolifec PL 2303 chipset Modinfo: filename: /lib/modules/5.4.0-66-generic/kernel/drivers/usb/serial/ch341.ko license:GPL v2 srcversion: 8F5F64E72BDA4E76E6F4F4D alias: usb:v4348p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7522d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5512d*dc*dsc*dp*ic*isc*ip*in* depends:usbserial retpoline: Y intree: Y name: ch341 vermagic: 5.4.0-66-generic SMP mod_unload sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:1E:07:0D:94:23:77:98:99:05:31:F3:76:E8:6B:76:12:7C:83:9E:05 sig_hashalgo: sha512 signature: 50:CE:79:92:87:EA:82:77:A9:25:A3:B7:F2:B3:ED:63:FE:85:EB:61: 7A:31:C5:9E:E5:78:E5:44:C6:FE:5D:74:4A:60:B6:0A:94:3F:C3:70: 0B:6D:27:A6:89:F7:D2:AC:8E:71:AC:0D:AF:5D:3A:19:07:18:F9:7C: B8:3C:47:DF:18:4D:13:C9:F8:45:AC:81:19:B0:DE:57:16:1A:F5:C6: AC:41:7E:E7:F2:6D:29:9C:14:A3:04:F8:9B:DF:8D:2E:9F:34:44:18: A8:FF:C6:A4:AF:04:86:D5:6D:F2:4C:AD:D2:65:4C:63:0F:C1:82:E3: 28:20:F2:D4:80:86:1A:67:1D:A2:56:18:87:E2:AB:40:E6:6A:48:E5: D7:D2:6F:6F:DB:05:20:B2:76:81:5C:0C:36:02:37:E9:A2:08:4E:53: 5E:9C:18:03:50:11:2D:E4:62:74:6E:CB:42:67:25:22:0C:F6:55:D8: 6F:E3:5A:15:AC:10:B7:F2:B7:C9:20:6C:19:ED:CC:7D:CC:CB:48:3B: B0:5E:E3:ED:05:DF:DF:65:FF:19:AD:76:6E:40:D2:0B:F0:11:65:D5: 92:7D:C9:3A:32:BE:A8:13:CE:C1:DE:D9:73:0F:0A:0B:8A:08:55:2E: 41:9D:B9:9A:AD:EC:4C:7D:98:3A:52:38:DF:78:DE:33:F1:14:A2:1B: AC:93:FD:30:76:A5:7C:AF:13:16:B8:5E:0B:73:A7:1F:20:E4:54:44: 07:A2:11:7F:D7:0E:B3:1C:A9:AA:73:76:0E:89:E0:D5:74:39:66:2F: E8:14:93:EC:7A:B2:23:E0:CC:77:9F:CD:D9:99:CB:B0:14:21:1C:1F: 0C:E9:30:B8:C3:55:8F:49:FC:88:5D:EF:20:B9:0E:F2:88:28:5A:93: 08:4D:2B:76:64:85:D1:E0:1C:9C:4B:86:2C:DB:65:F6:D8:23:A0:8D: 1B:22:74:0C:B9:41:9E:57:5A:67:4C:CC:1F:E2:43:5F:C2:21:82:E6: D4:C1:66:6F:30:54:27:2E:1D:22:8C:65:7F:93:C8:1D:C0:51:F0:7D: 7A:96:3A:3B:3D:C4:6E:69:DF:83:8A:85:0D:35:15:F9:5E:89:0F:D5: 9E:6F:A1:5F:39:CE:2A:88:57:97:DF:42:5C:70:12:4E:91:9E:1A:92: 49:99:C3:7B:38:12:B0:3A:D0:92:38:45:C7:74:3C:66:0F:A1:9C:C2: 9F:DC:A2:1B:DF:20:BB:F5:A5:F0:10:D6:6F:4F:C1:90:00:C3:F9:D8: 42:96:D2:28:FD:DE:21:33:6C:F4:7F:18:B2:ED:F9:A6:A4:4A:A5:4F: 26:7C:C0:F7:8B:A9:B3:2F:5A:5B:E2:B8 Demsg entries: usb 4-3: new full-speed USB device number 6 using ohci-pci usb 4-3: New USB device found, idVendor=4348, idProduct=5523, bcdDevice= 2.50 usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 ch341 4-3:1.0: ch341-uart converter detected usb 4-3: ch341-uart converter now attached to ttyUSB0 ---
[Kernel-packages] [Bug 1919051] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1919051/+attachment/5476738/+files/CurrentDmesg.txt -- 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/1919051 Title: ch341 USB-Serial converter only receives, does not send Status in linux package in Ubuntu: Confirmed Bug description: This device works flawlessly on Windows XP with native driver, both as a physical machine or inside a VM. It appears on XP's device management as "USB 2.0" name. On Ubuntu, Shorting pins 2 and 3 of DB9 connector does not give back characters sent (no echo), nor typed strings are sent to other RS232 devices, despite of communication settings. Characters from remote devices are correctly received. Using a null modem cable to other RS232 terminal shows that the local terminal receives, but does not transmit. Its worth to mention: passing through the device to a guest virtual machine (KVM) running Windows XP makes it work correctly with XP driver inside the guest OS. Bringing back the device stops transmitting. Only receive works. Tested with the version below: NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal Kernel: Linux host 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Device ID: ID 4348:5523 WinChipHead USB->RS 232 adapter with Prolifec PL 2303 chipset Modinfo: filename: /lib/modules/5.4.0-66-generic/kernel/drivers/usb/serial/ch341.ko license:GPL v2 srcversion: 8F5F64E72BDA4E76E6F4F4D alias: usb:v4348p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7522d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5512d*dc*dsc*dp*ic*isc*ip*in* depends:usbserial retpoline: Y intree: Y name: ch341 vermagic: 5.4.0-66-generic SMP mod_unload sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:1E:07:0D:94:23:77:98:99:05:31:F3:76:E8:6B:76:12:7C:83:9E:05 sig_hashalgo: sha512 signature: 50:CE:79:92:87:EA:82:77:A9:25:A3:B7:F2:B3:ED:63:FE:85:EB:61: 7A:31:C5:9E:E5:78:E5:44:C6:FE:5D:74:4A:60:B6:0A:94:3F:C3:70: 0B:6D:27:A6:89:F7:D2:AC:8E:71:AC:0D:AF:5D:3A:19:07:18:F9:7C: B8:3C:47:DF:18:4D:13:C9:F8:45:AC:81:19:B0:DE:57:16:1A:F5:C6: AC:41:7E:E7:F2:6D:29:9C:14:A3:04:F8:9B:DF:8D:2E:9F:34:44:18: A8:FF:C6:A4:AF:04:86:D5:6D:F2:4C:AD:D2:65:4C:63:0F:C1:82:E3: 28:20:F2:D4:80:86:1A:67:1D:A2:56:18:87:E2:AB:40:E6:6A:48:E5: D7:D2:6F:6F:DB:05:20:B2:76:81:5C:0C:36:02:37:E9:A2:08:4E:53: 5E:9C:18:03:50:11:2D:E4:62:74:6E:CB:42:67:25:22:0C:F6:55:D8: 6F:E3:5A:15:AC:10:B7:F2:B7:C9:20:6C:19:ED:CC:7D:CC:CB:48:3B: B0:5E:E3:ED:05:DF:DF:65:FF:19:AD:76:6E:40:D2:0B:F0:11:65:D5: 92:7D:C9:3A:32:BE:A8:13:CE:C1:DE:D9:73:0F:0A:0B:8A:08:55:2E: 41:9D:B9:9A:AD:EC:4C:7D:98:3A:52:38:DF:78:DE:33:F1:14:A2:1B: AC:93:FD:30:76:A5:7C:AF:13:16:B8:5E:0B:73:A7:1F:20:E4:54:44: 07:A2:11:7F:D7:0E:B3:1C:A9:AA:73:76:0E:89:E0:D5:74:39:66:2F: E8:14:93:EC:7A:B2:23:E0:CC:77:9F:CD:D9:99:CB:B0:14:21:1C:1F: 0C:E9:30:B8:C3:55:8F:49:FC:88:5D:EF:20:B9:0E:F2:88:28:5A:93: 08:4D:2B:76:64:85:D1:E0:1C:9C:4B:86:2C:DB:65:F6:D8:23:A0:8D: 1B:22:74:0C:B9:41:9E:57:5A:67:4C:CC:1F:E2:43:5F:C2:21:82:E6: D4:C1:66:6F:30:54:27:2E:1D:22:8C:65:7F:93:C8:1D:C0:51:F0:7D: 7A:96:3A:3B:3D:C4:6E:69:DF:83:8A:85:0D:35:15:F9:5E:89:0F:D5: 9E:6F:A1:5F:39:CE:2A:88:57:97:DF:42:5C:70:12:4E:91:9E:1A:92: 49:99:C3:7B:38:12:B0:3A:D0:92:38:45:C7:74:3C:66:0F:A1:9C:C2: 9F:DC:A2:1B:DF:20:BB:F5:A5:F0:10:D6:6F:4F:C1:90:00:C3:F9:D8: 42:96:D2:28:FD:DE:21:33:6C:F4:7F:18:B2:ED:F9:A6:A4:4A:A5:4F: 26:7C:C0:F7:8B:A9:B3:2F:5A:5B:E2:B8 Demsg entries: usb 4-3: new full-speed USB device number 6 using ohci-pci usb 4-3: New USB device found, idVendor=4348, idProduct=5523, bcdDevice= 2.50 usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 ch341 4-3:1.0: ch341-uart converter detected usb 4-3: ch341-uart converter now attached to ttyUSB0
[Kernel-packages] [Bug 1919051] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1919051/+attachment/5476737/+files/CRDA.txt -- 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/1919051 Title: ch341 USB-Serial converter only receives, does not send Status in linux package in Ubuntu: Confirmed Bug description: This device works flawlessly on Windows XP with native driver, both as a physical machine or inside a VM. It appears on XP's device management as "USB 2.0" name. On Ubuntu, Shorting pins 2 and 3 of DB9 connector does not give back characters sent (no echo), nor typed strings are sent to other RS232 devices, despite of communication settings. Characters from remote devices are correctly received. Using a null modem cable to other RS232 terminal shows that the local terminal receives, but does not transmit. Its worth to mention: passing through the device to a guest virtual machine (KVM) running Windows XP makes it work correctly with XP driver inside the guest OS. Bringing back the device stops transmitting. Only receive works. Tested with the version below: NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal Kernel: Linux host 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Device ID: ID 4348:5523 WinChipHead USB->RS 232 adapter with Prolifec PL 2303 chipset Modinfo: filename: /lib/modules/5.4.0-66-generic/kernel/drivers/usb/serial/ch341.ko license:GPL v2 srcversion: 8F5F64E72BDA4E76E6F4F4D alias: usb:v4348p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7522d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5512d*dc*dsc*dp*ic*isc*ip*in* depends:usbserial retpoline: Y intree: Y name: ch341 vermagic: 5.4.0-66-generic SMP mod_unload sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:1E:07:0D:94:23:77:98:99:05:31:F3:76:E8:6B:76:12:7C:83:9E:05 sig_hashalgo: sha512 signature: 50:CE:79:92:87:EA:82:77:A9:25:A3:B7:F2:B3:ED:63:FE:85:EB:61: 7A:31:C5:9E:E5:78:E5:44:C6:FE:5D:74:4A:60:B6:0A:94:3F:C3:70: 0B:6D:27:A6:89:F7:D2:AC:8E:71:AC:0D:AF:5D:3A:19:07:18:F9:7C: B8:3C:47:DF:18:4D:13:C9:F8:45:AC:81:19:B0:DE:57:16:1A:F5:C6: AC:41:7E:E7:F2:6D:29:9C:14:A3:04:F8:9B:DF:8D:2E:9F:34:44:18: A8:FF:C6:A4:AF:04:86:D5:6D:F2:4C:AD:D2:65:4C:63:0F:C1:82:E3: 28:20:F2:D4:80:86:1A:67:1D:A2:56:18:87:E2:AB:40:E6:6A:48:E5: D7:D2:6F:6F:DB:05:20:B2:76:81:5C:0C:36:02:37:E9:A2:08:4E:53: 5E:9C:18:03:50:11:2D:E4:62:74:6E:CB:42:67:25:22:0C:F6:55:D8: 6F:E3:5A:15:AC:10:B7:F2:B7:C9:20:6C:19:ED:CC:7D:CC:CB:48:3B: B0:5E:E3:ED:05:DF:DF:65:FF:19:AD:76:6E:40:D2:0B:F0:11:65:D5: 92:7D:C9:3A:32:BE:A8:13:CE:C1:DE:D9:73:0F:0A:0B:8A:08:55:2E: 41:9D:B9:9A:AD:EC:4C:7D:98:3A:52:38:DF:78:DE:33:F1:14:A2:1B: AC:93:FD:30:76:A5:7C:AF:13:16:B8:5E:0B:73:A7:1F:20:E4:54:44: 07:A2:11:7F:D7:0E:B3:1C:A9:AA:73:76:0E:89:E0:D5:74:39:66:2F: E8:14:93:EC:7A:B2:23:E0:CC:77:9F:CD:D9:99:CB:B0:14:21:1C:1F: 0C:E9:30:B8:C3:55:8F:49:FC:88:5D:EF:20:B9:0E:F2:88:28:5A:93: 08:4D:2B:76:64:85:D1:E0:1C:9C:4B:86:2C:DB:65:F6:D8:23:A0:8D: 1B:22:74:0C:B9:41:9E:57:5A:67:4C:CC:1F:E2:43:5F:C2:21:82:E6: D4:C1:66:6F:30:54:27:2E:1D:22:8C:65:7F:93:C8:1D:C0:51:F0:7D: 7A:96:3A:3B:3D:C4:6E:69:DF:83:8A:85:0D:35:15:F9:5E:89:0F:D5: 9E:6F:A1:5F:39:CE:2A:88:57:97:DF:42:5C:70:12:4E:91:9E:1A:92: 49:99:C3:7B:38:12:B0:3A:D0:92:38:45:C7:74:3C:66:0F:A1:9C:C2: 9F:DC:A2:1B:DF:20:BB:F5:A5:F0:10:D6:6F:4F:C1:90:00:C3:F9:D8: 42:96:D2:28:FD:DE:21:33:6C:F4:7F:18:B2:ED:F9:A6:A4:4A:A5:4F: 26:7C:C0:F7:8B:A9:B3:2F:5A:5B:E2:B8 Demsg entries: usb 4-3: new full-speed USB device number 6 using ohci-pci usb 4-3: New USB device found, idVendor=4348, idProduct=5523, bcdDevice= 2.50 usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 ch341 4-3:1.0: ch341-uart converter detected usb 4-3: ch341-uart converter now attached to ttyUSB0 --- ProblemT
[Kernel-packages] [Bug 1919051] Re: ch341 USB-Serial converter only receives, does not send
apport information ** Tags added: apport-collected ** Description changed: This device works flawlessly on Windows XP with native driver, both as a physical machine or inside a VM. It appears on XP's device management as "USB 2.0" name. On Ubuntu, Shorting pins 2 and 3 of DB9 connector does not give back characters sent (no echo), nor typed strings are sent to other RS232 devices, despite of communication settings. Characters from remote devices are correctly received. Using a null modem cable to other RS232 terminal shows that the local terminal receives, but does not transmit. Its worth to mention: passing through the device to a guest virtual machine (KVM) running Windows XP makes it work correctly with XP driver inside the guest OS. Bringing back the device stops transmitting. Only receive works. Tested with the version below: NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal Kernel: Linux host 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Device ID: ID 4348:5523 WinChipHead USB->RS 232 adapter with Prolifec PL 2303 chipset Modinfo: filename: /lib/modules/5.4.0-66-generic/kernel/drivers/usb/serial/ch341.ko license:GPL v2 srcversion: 8F5F64E72BDA4E76E6F4F4D alias: usb:v4348p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p7522d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5523d*dc*dsc*dp*ic*isc*ip*in* alias: usb:v1A86p5512d*dc*dsc*dp*ic*isc*ip*in* depends:usbserial retpoline: Y intree: Y name: ch341 vermagic: 5.4.0-66-generic SMP mod_unload sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:1E:07:0D:94:23:77:98:99:05:31:F3:76:E8:6B:76:12:7C:83:9E:05 sig_hashalgo: sha512 signature: 50:CE:79:92:87:EA:82:77:A9:25:A3:B7:F2:B3:ED:63:FE:85:EB:61: 7A:31:C5:9E:E5:78:E5:44:C6:FE:5D:74:4A:60:B6:0A:94:3F:C3:70: 0B:6D:27:A6:89:F7:D2:AC:8E:71:AC:0D:AF:5D:3A:19:07:18:F9:7C: B8:3C:47:DF:18:4D:13:C9:F8:45:AC:81:19:B0:DE:57:16:1A:F5:C6: AC:41:7E:E7:F2:6D:29:9C:14:A3:04:F8:9B:DF:8D:2E:9F:34:44:18: A8:FF:C6:A4:AF:04:86:D5:6D:F2:4C:AD:D2:65:4C:63:0F:C1:82:E3: 28:20:F2:D4:80:86:1A:67:1D:A2:56:18:87:E2:AB:40:E6:6A:48:E5: D7:D2:6F:6F:DB:05:20:B2:76:81:5C:0C:36:02:37:E9:A2:08:4E:53: 5E:9C:18:03:50:11:2D:E4:62:74:6E:CB:42:67:25:22:0C:F6:55:D8: 6F:E3:5A:15:AC:10:B7:F2:B7:C9:20:6C:19:ED:CC:7D:CC:CB:48:3B: B0:5E:E3:ED:05:DF:DF:65:FF:19:AD:76:6E:40:D2:0B:F0:11:65:D5: 92:7D:C9:3A:32:BE:A8:13:CE:C1:DE:D9:73:0F:0A:0B:8A:08:55:2E: 41:9D:B9:9A:AD:EC:4C:7D:98:3A:52:38:DF:78:DE:33:F1:14:A2:1B: AC:93:FD:30:76:A5:7C:AF:13:16:B8:5E:0B:73:A7:1F:20:E4:54:44: 07:A2:11:7F:D7:0E:B3:1C:A9:AA:73:76:0E:89:E0:D5:74:39:66:2F: E8:14:93:EC:7A:B2:23:E0:CC:77:9F:CD:D9:99:CB:B0:14:21:1C:1F: 0C:E9:30:B8:C3:55:8F:49:FC:88:5D:EF:20:B9:0E:F2:88:28:5A:93: 08:4D:2B:76:64:85:D1:E0:1C:9C:4B:86:2C:DB:65:F6:D8:23:A0:8D: 1B:22:74:0C:B9:41:9E:57:5A:67:4C:CC:1F:E2:43:5F:C2:21:82:E6: D4:C1:66:6F:30:54:27:2E:1D:22:8C:65:7F:93:C8:1D:C0:51:F0:7D: 7A:96:3A:3B:3D:C4:6E:69:DF:83:8A:85:0D:35:15:F9:5E:89:0F:D5: 9E:6F:A1:5F:39:CE:2A:88:57:97:DF:42:5C:70:12:4E:91:9E:1A:92: 49:99:C3:7B:38:12:B0:3A:D0:92:38:45:C7:74:3C:66:0F:A1:9C:C2: 9F:DC:A2:1B:DF:20:BB:F5:A5:F0:10:D6:6F:4F:C1:90:00:C3:F9:D8: 42:96:D2:28:FD:DE:21:33:6C:F4:7F:18:B2:ED:F9:A6:A4:4A:A5:4F: 26:7C:C0:F7:8B:A9:B3:2F:5A:5B:E2:B8 Demsg entries: usb 4-3: new full-speed USB device number 6 using ohci-pci usb 4-3: New USB device found, idVendor=4348, idProduct=5523, bcdDevice= 2.50 usb 4-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 ch341 4-3:1.0: ch341-uart converter detected usb 4-3: ch341-uart converter now attached to ttyUSB0 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.16 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: luzemario 1370 F pulseaudio + /dev/snd/controlC0: luzemario 1370 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: KDE + DistroRelease: Ubuntu 20.04 + InstallationDat
[Kernel-packages] [Bug 1911055] Re: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed
Reporting a nVIDIA issue in an Ubuntu bug report is probably not as efficient as contacting nVIDIA directly. I made a report in the Linux forum: https://forums.developer.nvidia.com/t/460-56-no-desktop-on- resume-from-suspend-to-ram/170275 but I did not get a response yet. Could some of the people affected by this bug add their nvidia_bug_report.log.gz ? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1911055 Title: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: After a recent update to nvidia-460, suspend then resume results in a black screen, then a hang for around 120 seconds, and then the text: nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer dmesg shows: [ 188.352670] ACPI: Waking up from system sleep state S3 ... [ 309.142164] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 309.142319] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.142165] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 313.142348] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.151885] acpi LNXPOWER:08: Turning OFF [ 313.151898] acpi LNXPOWER:04: Turning OFF [ 313.152351] acpi LNXPOWER:03: Turning OFF [ 313.153064] acpi LNXPOWER:02: Turning OFF ... [ 325.010192] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DELL 2209WA (HDMI-0) [ 325.010577] BUG: kernel NULL pointer dereference, address: 0050 [ 325.010579] #PF: supervisor read access in kernel mode [ 325.010580] #PF: error_code(0x) - not-present page [ 325.010580] PGD 0 P4D 0 [ 325.010582] Oops: [#1] SMP PTI [ 325.010583] CPU: 9 PID: 2247 Comm: Xorg Tainted: P O 5.4.0-60-generic #67-Ubuntu [ 325.010584] Hardware name: Razer Blade/DANA_MB, BIOS 01.01 08/31/2018 [ 325.010595] RIP: 0010:_nv000112kms+0xd/0x30 [nvidia_modeset] [ 325.010596] Code: 16 00 74 06 83 7e 0c 02 77 03 31 c0 c3 c7 46 0c 01 00 00 00 b8 01 00 00 00 c3 0f 1f 00 0f b7 46 04 0f b7 56 08 39 d0 0f 47 c2 <3b> 47 18 77 06 83 7e 10 02 77 08 31 c0 c3 0f 1f 44 00 00 c7 46 10 [ 325.010597] RSP: 0018:b89542e5b8a8 EFLAGS: 00010246 [ 325.010598] RAX: 0280 RBX: 0038 RCX: 03ff [ 325.010598] RDX: 0280 RSI: b89542e5bba0 RDI: 0038 [ 325.010599] RBP: b89542e5b9c8 R08: R09: c379e440 [ 325.010600] R10: R11: R12: b89542e5b948 [ 325.010600] R13: b89542e5b948 R14: b89542e5b930 R15: c3a50e60 [ 325.010601] FS: 7feb4c09ea80() GS:8e46ada4() knlGS: [ 325.010602] CS: 0010 DS: ES: CR0: 80050033 [ 325.010602] CR2: 0050 CR3: 0004772e2006 CR4: 003606e0 [ 325.010603] Call Trace: [ 325.010610] ? _nv002768kms+0x96/0xd0 [nvidia_modeset] [ 325.010616] ? _nv002328kms+0xb5/0x110 [nvidia_modeset] [ 325.010624] ? _nv000742kms+0x168/0x370 [nvidia_modeset] [ 325.010823] ? _nv036002rm+0x62/0x70 [nvidia] [ 325.010910] ? os_get_current_tick+0x2c/0x50 [nvidia] [ 325.010921] ? _nv002771kms+0x433/0x600 [nvidia_modeset] [ 325.010928] ? _nv002771kms+0x3fc/0x600 [nvidia_modeset] [ 325.010930] ? __schedule+0x2eb/0x740 [ 325.010935] ? _nv000742kms+0x40/0x40 [nvidia_modeset] [ 325.010939] ? nvkms_alloc+0x6a/0xa0 [nvidia_modeset] [ 325.010944] ? _nv000742kms+0x40/0x40 [nvidia_modeset] [ 325.010948] ? _nv000744kms+0x2a/0x40 [nvidia_modeset] [ 325.010952] ? nvKmsIoctl+0x96/0x1d0 [nvidia_modeset] [ 325.010957] ? nvkms_ioctl_common+0x42/0x80 [nvidia_modeset] [ 325.010961] ? nvkms_ioctl+0xc4/0x100 [nvidia_modeset] [ 325.011016] ? nvidia_frontend_unlocked_ioctl+0x3b/0x50 [nvidia] [ 325.011017] ? do_vfs_ioctl+0x407/0x670 [ 325.011019] ? do_user_addr_fault+0x216/0x450 [ 325.011020] ? ksys_ioctl+0x67/0x90 [ 325.011021] ? __x64_sys_ioctl+0x1a/0x20 [ 325.011023] ? do_syscall_64+0x57/0x190 [ 325.011024] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 325.011025] Modules linked in: rfcomm ccm aufs overlay
[Kernel-packages] [Bug 1912679] Re: Xenial update: v4.4.250 upstream stable release
This bug was fixed in the package linux - 4.4.0-204.236
---
linux (4.4.0-204.236) xenial; urgency=medium
* xenial/linux: 4.4.0-204.236 -proposed tracker (LP: #1916222)
* Xenial update: v4.4.254 upstream stable release (LP: #1914648)
- ALSA: seq: oss: Fix missing error check in snd_seq_oss_synth_make_info()
- ALSA: hda/via: Add minimum mute flag
- ACPI: scan: Make acpi_bus_get_device() clear return pointer on error
- dm: avoid filesystem lookup in dm_get_dev_t()
- ASoC: Intel: haswell: Add missing pm_ops
- scsi: ufs: Correct the LUN used in eh_device_reset_handler() callback
- drm/nouveau/bios: fix issue shadowing expansion ROMs
- drm/nouveau/i2c/gm200: increase width of aux semaphore owner fields
- can: dev: can_restart: fix use after free bug
- iio: ad5504: Fix setting power-down state
- ehci: fix EHCI host controller initialization sequence
- usb: bdc: Make bdc pci driver depend on BROKEN
- [Config] updateconfigs for USB_BDC_PCI
- xhci: make sure TRB is fully written before giving it to the controller
- compiler.h: Raise minimum version of GCC to 5.1 for arm64
- netfilter: rpfilter: mask ecn bits before fib lookup
- sh: dma: fix kconfig dependency for G2_DMA
- sh_eth: Fix power down vs. is_opened flag ordering
- skbuff: back tiny skbs with kmalloc() in __netdev_alloc_skb() too
- ipv6: create multicast route with RTPROT_KERNEL
- net_sched: avoid shift-out-of-bounds in tcindex_set_parms()
- Revert "mm/slub: fix a memory leak in sysfs_slab_add()"
- tracing: Fix race in trace_open and buffer resize call
- xen-blkback: set ring->xenblkd to NULL after kthread_stop()
- x86/boot/compressed: Disable relocation relaxation
- Linux 4.4.254
* Xenial update: v4.4.253 upstream stable release (LP: #1914647)
- ASoC: dapm: remove widget from dirty list on free
- mm/hugetlb: fix potential missing huge page size info
- ext4: fix bug for rename with RENAME_WHITEOUT
- ARC: build: add boot_targets to PHONY
- ethernet: ucc_geth: fix definition and size of ucc_geth_tx_global_pram
- arch/arc: add copy_user_page() to to fix build error on ARC
- misdn: dsp: select CONFIG_BITREVERSE
- net: ethernet: fs_enet: Add missing MODULE_LICENSE
- ACPI: scan: add stub acpi_create_platform_device() for !CONFIG_ACPI
- ARM: picoxcell: fix missing interrupt-parent properties
- Input: uinput - avoid FF flush when destroying device
- dump_common_audit_data(): fix racy accesses to ->d_name
- NFS: nfs_igrab_and_active must first reference the superblock
- ext4: fix superblock checksum failure when setting password salt
- RDMA/usnic: Fix memleak in find_free_vf_and_create_qp_grp
- mm, slub: consider rest of partial list if acquire_slab() fails
- net: sunrpc: interpret the return value of kstrtou32 correctly
- usb: ohci: Make distrust_firmware param default to false
- iio: buffer: Fix demux update
- nfsd4: readdirplus shouldn't return parent of export
- net: cdc_ncm: correct overhead in delayed_ndp_size
- netxen_nic: fix MSI/MSI-x interrupts
- rndis_host: set proper input size for OID_GEN_PHYSICAL_MEDIUM request
- net: dcb: Validate netlink message in DCB handler
- net: dcb: Accept RTM_GETDCB messages carrying set-like DCB commands
- net: sit: unregister_netdevice on newlink's error path
- rxrpc: Fix handling of an unsupported token type in rxrpc_read()
- net: avoid 32 x truesize under-estimation for tiny skbs
- spi: cadence: cache reference clock rate during probe
- Linux 4.4.253
* Xenial update: v4.4.252 upstream stable release (LP: #1913479)
- Revert "UBUNTU: SAUCE: target: fix XCOPY NAA identifier lookup"
- target: add XCOPY target/segment desc sense codes
- target: bounds check XCOPY segment descriptor list
- target: use XCOPY segment descriptor CSCD IDs
- xcopy: loop over devices using idr helper
- scsi: target: Fix XCOPY NAA identifier lookup
- powerpc: Fix incorrect stw{, ux, u, x} instructions in __set_pte_at
- net: ip: always refragment ip defragmented packets
- net: fix pmtu check in nopmtudisc mode
- vmlinux.lds.h: Add PGO and AutoFDO input sections
- ubifs: wbuf: Don't leak kernel memory to flash
- spi: pxa2xx: Fix use-after-free on unbind
- cpufreq: powernow-k8: pass policy rather than use cpufreq_cpu_get()
- wil6210: select CONFIG_CRC32
- block: rsxx: select CONFIG_CRC32
- iommu/intel: Fix memleak in intel_irq_remapping_alloc
- block: fix use-after-free in disk_part_iter_next
- net: drop bogus skb with CHECKSUM_PARTIAL and offset beyond end of trimmed
packet
- Linux 4.4.252
* Xenial update: v4.4.251 upstream stable release (LP: #1913478)
- kbuild: don't hardcode depmod path
- workqueue: Kick a worker based on the actual activation of delayed works
- lib/genalloc: fix the overflow when size is too b
[Kernel-packages] [Bug 1913478] Re: Xenial update: v4.4.251 upstream stable release
This bug was fixed in the package linux - 4.4.0-204.236
---
linux (4.4.0-204.236) xenial; urgency=medium
* xenial/linux: 4.4.0-204.236 -proposed tracker (LP: #1916222)
* Xenial update: v4.4.254 upstream stable release (LP: #1914648)
- ALSA: seq: oss: Fix missing error check in snd_seq_oss_synth_make_info()
- ALSA: hda/via: Add minimum mute flag
- ACPI: scan: Make acpi_bus_get_device() clear return pointer on error
- dm: avoid filesystem lookup in dm_get_dev_t()
- ASoC: Intel: haswell: Add missing pm_ops
- scsi: ufs: Correct the LUN used in eh_device_reset_handler() callback
- drm/nouveau/bios: fix issue shadowing expansion ROMs
- drm/nouveau/i2c/gm200: increase width of aux semaphore owner fields
- can: dev: can_restart: fix use after free bug
- iio: ad5504: Fix setting power-down state
- ehci: fix EHCI host controller initialization sequence
- usb: bdc: Make bdc pci driver depend on BROKEN
- [Config] updateconfigs for USB_BDC_PCI
- xhci: make sure TRB is fully written before giving it to the controller
- compiler.h: Raise minimum version of GCC to 5.1 for arm64
- netfilter: rpfilter: mask ecn bits before fib lookup
- sh: dma: fix kconfig dependency for G2_DMA
- sh_eth: Fix power down vs. is_opened flag ordering
- skbuff: back tiny skbs with kmalloc() in __netdev_alloc_skb() too
- ipv6: create multicast route with RTPROT_KERNEL
- net_sched: avoid shift-out-of-bounds in tcindex_set_parms()
- Revert "mm/slub: fix a memory leak in sysfs_slab_add()"
- tracing: Fix race in trace_open and buffer resize call
- xen-blkback: set ring->xenblkd to NULL after kthread_stop()
- x86/boot/compressed: Disable relocation relaxation
- Linux 4.4.254
* Xenial update: v4.4.253 upstream stable release (LP: #1914647)
- ASoC: dapm: remove widget from dirty list on free
- mm/hugetlb: fix potential missing huge page size info
- ext4: fix bug for rename with RENAME_WHITEOUT
- ARC: build: add boot_targets to PHONY
- ethernet: ucc_geth: fix definition and size of ucc_geth_tx_global_pram
- arch/arc: add copy_user_page() to to fix build error on ARC
- misdn: dsp: select CONFIG_BITREVERSE
- net: ethernet: fs_enet: Add missing MODULE_LICENSE
- ACPI: scan: add stub acpi_create_platform_device() for !CONFIG_ACPI
- ARM: picoxcell: fix missing interrupt-parent properties
- Input: uinput - avoid FF flush when destroying device
- dump_common_audit_data(): fix racy accesses to ->d_name
- NFS: nfs_igrab_and_active must first reference the superblock
- ext4: fix superblock checksum failure when setting password salt
- RDMA/usnic: Fix memleak in find_free_vf_and_create_qp_grp
- mm, slub: consider rest of partial list if acquire_slab() fails
- net: sunrpc: interpret the return value of kstrtou32 correctly
- usb: ohci: Make distrust_firmware param default to false
- iio: buffer: Fix demux update
- nfsd4: readdirplus shouldn't return parent of export
- net: cdc_ncm: correct overhead in delayed_ndp_size
- netxen_nic: fix MSI/MSI-x interrupts
- rndis_host: set proper input size for OID_GEN_PHYSICAL_MEDIUM request
- net: dcb: Validate netlink message in DCB handler
- net: dcb: Accept RTM_GETDCB messages carrying set-like DCB commands
- net: sit: unregister_netdevice on newlink's error path
- rxrpc: Fix handling of an unsupported token type in rxrpc_read()
- net: avoid 32 x truesize under-estimation for tiny skbs
- spi: cadence: cache reference clock rate during probe
- Linux 4.4.253
* Xenial update: v4.4.252 upstream stable release (LP: #1913479)
- Revert "UBUNTU: SAUCE: target: fix XCOPY NAA identifier lookup"
- target: add XCOPY target/segment desc sense codes
- target: bounds check XCOPY segment descriptor list
- target: use XCOPY segment descriptor CSCD IDs
- xcopy: loop over devices using idr helper
- scsi: target: Fix XCOPY NAA identifier lookup
- powerpc: Fix incorrect stw{, ux, u, x} instructions in __set_pte_at
- net: ip: always refragment ip defragmented packets
- net: fix pmtu check in nopmtudisc mode
- vmlinux.lds.h: Add PGO and AutoFDO input sections
- ubifs: wbuf: Don't leak kernel memory to flash
- spi: pxa2xx: Fix use-after-free on unbind
- cpufreq: powernow-k8: pass policy rather than use cpufreq_cpu_get()
- wil6210: select CONFIG_CRC32
- block: rsxx: select CONFIG_CRC32
- iommu/intel: Fix memleak in intel_irq_remapping_alloc
- block: fix use-after-free in disk_part_iter_next
- net: drop bogus skb with CHECKSUM_PARTIAL and offset beyond end of trimmed
packet
- Linux 4.4.252
* Xenial update: v4.4.251 upstream stable release (LP: #1913478)
- kbuild: don't hardcode depmod path
- workqueue: Kick a worker based on the actual activation of delayed works
- lib/genalloc: fix the overflow when size is too b
[Kernel-packages] [Bug 1913479] Re: Xenial update: v4.4.252 upstream stable release
This bug was fixed in the package linux - 4.4.0-204.236
---
linux (4.4.0-204.236) xenial; urgency=medium
* xenial/linux: 4.4.0-204.236 -proposed tracker (LP: #1916222)
* Xenial update: v4.4.254 upstream stable release (LP: #1914648)
- ALSA: seq: oss: Fix missing error check in snd_seq_oss_synth_make_info()
- ALSA: hda/via: Add minimum mute flag
- ACPI: scan: Make acpi_bus_get_device() clear return pointer on error
- dm: avoid filesystem lookup in dm_get_dev_t()
- ASoC: Intel: haswell: Add missing pm_ops
- scsi: ufs: Correct the LUN used in eh_device_reset_handler() callback
- drm/nouveau/bios: fix issue shadowing expansion ROMs
- drm/nouveau/i2c/gm200: increase width of aux semaphore owner fields
- can: dev: can_restart: fix use after free bug
- iio: ad5504: Fix setting power-down state
- ehci: fix EHCI host controller initialization sequence
- usb: bdc: Make bdc pci driver depend on BROKEN
- [Config] updateconfigs for USB_BDC_PCI
- xhci: make sure TRB is fully written before giving it to the controller
- compiler.h: Raise minimum version of GCC to 5.1 for arm64
- netfilter: rpfilter: mask ecn bits before fib lookup
- sh: dma: fix kconfig dependency for G2_DMA
- sh_eth: Fix power down vs. is_opened flag ordering
- skbuff: back tiny skbs with kmalloc() in __netdev_alloc_skb() too
- ipv6: create multicast route with RTPROT_KERNEL
- net_sched: avoid shift-out-of-bounds in tcindex_set_parms()
- Revert "mm/slub: fix a memory leak in sysfs_slab_add()"
- tracing: Fix race in trace_open and buffer resize call
- xen-blkback: set ring->xenblkd to NULL after kthread_stop()
- x86/boot/compressed: Disable relocation relaxation
- Linux 4.4.254
* Xenial update: v4.4.253 upstream stable release (LP: #1914647)
- ASoC: dapm: remove widget from dirty list on free
- mm/hugetlb: fix potential missing huge page size info
- ext4: fix bug for rename with RENAME_WHITEOUT
- ARC: build: add boot_targets to PHONY
- ethernet: ucc_geth: fix definition and size of ucc_geth_tx_global_pram
- arch/arc: add copy_user_page() to to fix build error on ARC
- misdn: dsp: select CONFIG_BITREVERSE
- net: ethernet: fs_enet: Add missing MODULE_LICENSE
- ACPI: scan: add stub acpi_create_platform_device() for !CONFIG_ACPI
- ARM: picoxcell: fix missing interrupt-parent properties
- Input: uinput - avoid FF flush when destroying device
- dump_common_audit_data(): fix racy accesses to ->d_name
- NFS: nfs_igrab_and_active must first reference the superblock
- ext4: fix superblock checksum failure when setting password salt
- RDMA/usnic: Fix memleak in find_free_vf_and_create_qp_grp
- mm, slub: consider rest of partial list if acquire_slab() fails
- net: sunrpc: interpret the return value of kstrtou32 correctly
- usb: ohci: Make distrust_firmware param default to false
- iio: buffer: Fix demux update
- nfsd4: readdirplus shouldn't return parent of export
- net: cdc_ncm: correct overhead in delayed_ndp_size
- netxen_nic: fix MSI/MSI-x interrupts
- rndis_host: set proper input size for OID_GEN_PHYSICAL_MEDIUM request
- net: dcb: Validate netlink message in DCB handler
- net: dcb: Accept RTM_GETDCB messages carrying set-like DCB commands
- net: sit: unregister_netdevice on newlink's error path
- rxrpc: Fix handling of an unsupported token type in rxrpc_read()
- net: avoid 32 x truesize under-estimation for tiny skbs
- spi: cadence: cache reference clock rate during probe
- Linux 4.4.253
* Xenial update: v4.4.252 upstream stable release (LP: #1913479)
- Revert "UBUNTU: SAUCE: target: fix XCOPY NAA identifier lookup"
- target: add XCOPY target/segment desc sense codes
- target: bounds check XCOPY segment descriptor list
- target: use XCOPY segment descriptor CSCD IDs
- xcopy: loop over devices using idr helper
- scsi: target: Fix XCOPY NAA identifier lookup
- powerpc: Fix incorrect stw{, ux, u, x} instructions in __set_pte_at
- net: ip: always refragment ip defragmented packets
- net: fix pmtu check in nopmtudisc mode
- vmlinux.lds.h: Add PGO and AutoFDO input sections
- ubifs: wbuf: Don't leak kernel memory to flash
- spi: pxa2xx: Fix use-after-free on unbind
- cpufreq: powernow-k8: pass policy rather than use cpufreq_cpu_get()
- wil6210: select CONFIG_CRC32
- block: rsxx: select CONFIG_CRC32
- iommu/intel: Fix memleak in intel_irq_remapping_alloc
- block: fix use-after-free in disk_part_iter_next
- net: drop bogus skb with CHECKSUM_PARTIAL and offset beyond end of trimmed
packet
- Linux 4.4.252
* Xenial update: v4.4.251 upstream stable release (LP: #1913478)
- kbuild: don't hardcode depmod path
- workqueue: Kick a worker based on the actual activation of delayed works
- lib/genalloc: fix the overflow when size is too b
[Kernel-packages] [Bug 1914647] Re: Xenial update: v4.4.253 upstream stable release
This bug was fixed in the package linux - 4.4.0-204.236
---
linux (4.4.0-204.236) xenial; urgency=medium
* xenial/linux: 4.4.0-204.236 -proposed tracker (LP: #1916222)
* Xenial update: v4.4.254 upstream stable release (LP: #1914648)
- ALSA: seq: oss: Fix missing error check in snd_seq_oss_synth_make_info()
- ALSA: hda/via: Add minimum mute flag
- ACPI: scan: Make acpi_bus_get_device() clear return pointer on error
- dm: avoid filesystem lookup in dm_get_dev_t()
- ASoC: Intel: haswell: Add missing pm_ops
- scsi: ufs: Correct the LUN used in eh_device_reset_handler() callback
- drm/nouveau/bios: fix issue shadowing expansion ROMs
- drm/nouveau/i2c/gm200: increase width of aux semaphore owner fields
- can: dev: can_restart: fix use after free bug
- iio: ad5504: Fix setting power-down state
- ehci: fix EHCI host controller initialization sequence
- usb: bdc: Make bdc pci driver depend on BROKEN
- [Config] updateconfigs for USB_BDC_PCI
- xhci: make sure TRB is fully written before giving it to the controller
- compiler.h: Raise minimum version of GCC to 5.1 for arm64
- netfilter: rpfilter: mask ecn bits before fib lookup
- sh: dma: fix kconfig dependency for G2_DMA
- sh_eth: Fix power down vs. is_opened flag ordering
- skbuff: back tiny skbs with kmalloc() in __netdev_alloc_skb() too
- ipv6: create multicast route with RTPROT_KERNEL
- net_sched: avoid shift-out-of-bounds in tcindex_set_parms()
- Revert "mm/slub: fix a memory leak in sysfs_slab_add()"
- tracing: Fix race in trace_open and buffer resize call
- xen-blkback: set ring->xenblkd to NULL after kthread_stop()
- x86/boot/compressed: Disable relocation relaxation
- Linux 4.4.254
* Xenial update: v4.4.253 upstream stable release (LP: #1914647)
- ASoC: dapm: remove widget from dirty list on free
- mm/hugetlb: fix potential missing huge page size info
- ext4: fix bug for rename with RENAME_WHITEOUT
- ARC: build: add boot_targets to PHONY
- ethernet: ucc_geth: fix definition and size of ucc_geth_tx_global_pram
- arch/arc: add copy_user_page() to to fix build error on ARC
- misdn: dsp: select CONFIG_BITREVERSE
- net: ethernet: fs_enet: Add missing MODULE_LICENSE
- ACPI: scan: add stub acpi_create_platform_device() for !CONFIG_ACPI
- ARM: picoxcell: fix missing interrupt-parent properties
- Input: uinput - avoid FF flush when destroying device
- dump_common_audit_data(): fix racy accesses to ->d_name
- NFS: nfs_igrab_and_active must first reference the superblock
- ext4: fix superblock checksum failure when setting password salt
- RDMA/usnic: Fix memleak in find_free_vf_and_create_qp_grp
- mm, slub: consider rest of partial list if acquire_slab() fails
- net: sunrpc: interpret the return value of kstrtou32 correctly
- usb: ohci: Make distrust_firmware param default to false
- iio: buffer: Fix demux update
- nfsd4: readdirplus shouldn't return parent of export
- net: cdc_ncm: correct overhead in delayed_ndp_size
- netxen_nic: fix MSI/MSI-x interrupts
- rndis_host: set proper input size for OID_GEN_PHYSICAL_MEDIUM request
- net: dcb: Validate netlink message in DCB handler
- net: dcb: Accept RTM_GETDCB messages carrying set-like DCB commands
- net: sit: unregister_netdevice on newlink's error path
- rxrpc: Fix handling of an unsupported token type in rxrpc_read()
- net: avoid 32 x truesize under-estimation for tiny skbs
- spi: cadence: cache reference clock rate during probe
- Linux 4.4.253
* Xenial update: v4.4.252 upstream stable release (LP: #1913479)
- Revert "UBUNTU: SAUCE: target: fix XCOPY NAA identifier lookup"
- target: add XCOPY target/segment desc sense codes
- target: bounds check XCOPY segment descriptor list
- target: use XCOPY segment descriptor CSCD IDs
- xcopy: loop over devices using idr helper
- scsi: target: Fix XCOPY NAA identifier lookup
- powerpc: Fix incorrect stw{, ux, u, x} instructions in __set_pte_at
- net: ip: always refragment ip defragmented packets
- net: fix pmtu check in nopmtudisc mode
- vmlinux.lds.h: Add PGO and AutoFDO input sections
- ubifs: wbuf: Don't leak kernel memory to flash
- spi: pxa2xx: Fix use-after-free on unbind
- cpufreq: powernow-k8: pass policy rather than use cpufreq_cpu_get()
- wil6210: select CONFIG_CRC32
- block: rsxx: select CONFIG_CRC32
- iommu/intel: Fix memleak in intel_irq_remapping_alloc
- block: fix use-after-free in disk_part_iter_next
- net: drop bogus skb with CHECKSUM_PARTIAL and offset beyond end of trimmed
packet
- Linux 4.4.252
* Xenial update: v4.4.251 upstream stable release (LP: #1913478)
- kbuild: don't hardcode depmod path
- workqueue: Kick a worker based on the actual activation of delayed works
- lib/genalloc: fix the overflow when size is too b
[Kernel-packages] [Bug 1914648] Re: Xenial update: v4.4.254 upstream stable release
This bug was fixed in the package linux - 4.4.0-204.236
---
linux (4.4.0-204.236) xenial; urgency=medium
* xenial/linux: 4.4.0-204.236 -proposed tracker (LP: #1916222)
* Xenial update: v4.4.254 upstream stable release (LP: #1914648)
- ALSA: seq: oss: Fix missing error check in snd_seq_oss_synth_make_info()
- ALSA: hda/via: Add minimum mute flag
- ACPI: scan: Make acpi_bus_get_device() clear return pointer on error
- dm: avoid filesystem lookup in dm_get_dev_t()
- ASoC: Intel: haswell: Add missing pm_ops
- scsi: ufs: Correct the LUN used in eh_device_reset_handler() callback
- drm/nouveau/bios: fix issue shadowing expansion ROMs
- drm/nouveau/i2c/gm200: increase width of aux semaphore owner fields
- can: dev: can_restart: fix use after free bug
- iio: ad5504: Fix setting power-down state
- ehci: fix EHCI host controller initialization sequence
- usb: bdc: Make bdc pci driver depend on BROKEN
- [Config] updateconfigs for USB_BDC_PCI
- xhci: make sure TRB is fully written before giving it to the controller
- compiler.h: Raise minimum version of GCC to 5.1 for arm64
- netfilter: rpfilter: mask ecn bits before fib lookup
- sh: dma: fix kconfig dependency for G2_DMA
- sh_eth: Fix power down vs. is_opened flag ordering
- skbuff: back tiny skbs with kmalloc() in __netdev_alloc_skb() too
- ipv6: create multicast route with RTPROT_KERNEL
- net_sched: avoid shift-out-of-bounds in tcindex_set_parms()
- Revert "mm/slub: fix a memory leak in sysfs_slab_add()"
- tracing: Fix race in trace_open and buffer resize call
- xen-blkback: set ring->xenblkd to NULL after kthread_stop()
- x86/boot/compressed: Disable relocation relaxation
- Linux 4.4.254
* Xenial update: v4.4.253 upstream stable release (LP: #1914647)
- ASoC: dapm: remove widget from dirty list on free
- mm/hugetlb: fix potential missing huge page size info
- ext4: fix bug for rename with RENAME_WHITEOUT
- ARC: build: add boot_targets to PHONY
- ethernet: ucc_geth: fix definition and size of ucc_geth_tx_global_pram
- arch/arc: add copy_user_page() to to fix build error on ARC
- misdn: dsp: select CONFIG_BITREVERSE
- net: ethernet: fs_enet: Add missing MODULE_LICENSE
- ACPI: scan: add stub acpi_create_platform_device() for !CONFIG_ACPI
- ARM: picoxcell: fix missing interrupt-parent properties
- Input: uinput - avoid FF flush when destroying device
- dump_common_audit_data(): fix racy accesses to ->d_name
- NFS: nfs_igrab_and_active must first reference the superblock
- ext4: fix superblock checksum failure when setting password salt
- RDMA/usnic: Fix memleak in find_free_vf_and_create_qp_grp
- mm, slub: consider rest of partial list if acquire_slab() fails
- net: sunrpc: interpret the return value of kstrtou32 correctly
- usb: ohci: Make distrust_firmware param default to false
- iio: buffer: Fix demux update
- nfsd4: readdirplus shouldn't return parent of export
- net: cdc_ncm: correct overhead in delayed_ndp_size
- netxen_nic: fix MSI/MSI-x interrupts
- rndis_host: set proper input size for OID_GEN_PHYSICAL_MEDIUM request
- net: dcb: Validate netlink message in DCB handler
- net: dcb: Accept RTM_GETDCB messages carrying set-like DCB commands
- net: sit: unregister_netdevice on newlink's error path
- rxrpc: Fix handling of an unsupported token type in rxrpc_read()
- net: avoid 32 x truesize under-estimation for tiny skbs
- spi: cadence: cache reference clock rate during probe
- Linux 4.4.253
* Xenial update: v4.4.252 upstream stable release (LP: #1913479)
- Revert "UBUNTU: SAUCE: target: fix XCOPY NAA identifier lookup"
- target: add XCOPY target/segment desc sense codes
- target: bounds check XCOPY segment descriptor list
- target: use XCOPY segment descriptor CSCD IDs
- xcopy: loop over devices using idr helper
- scsi: target: Fix XCOPY NAA identifier lookup
- powerpc: Fix incorrect stw{, ux, u, x} instructions in __set_pte_at
- net: ip: always refragment ip defragmented packets
- net: fix pmtu check in nopmtudisc mode
- vmlinux.lds.h: Add PGO and AutoFDO input sections
- ubifs: wbuf: Don't leak kernel memory to flash
- spi: pxa2xx: Fix use-after-free on unbind
- cpufreq: powernow-k8: pass policy rather than use cpufreq_cpu_get()
- wil6210: select CONFIG_CRC32
- block: rsxx: select CONFIG_CRC32
- iommu/intel: Fix memleak in intel_irq_remapping_alloc
- block: fix use-after-free in disk_part_iter_next
- net: drop bogus skb with CHECKSUM_PARTIAL and offset beyond end of trimmed
packet
- Linux 4.4.252
* Xenial update: v4.4.251 upstream stable release (LP: #1913478)
- kbuild: don't hardcode depmod path
- workqueue: Kick a worker based on the actual activation of delayed works
- lib/genalloc: fix the overflow when size is too b
[Kernel-packages] [Bug 1919070] Re: Unstable and frequent crashes kernel 5.4.0-66-generic on ASUS E201NAS (5.4.0-65-generic is good)
Hi Sam, thanks for the report. Is there any activity that you can do in order to trigger the crashes, or are them of nowhere? Also, what do you consider a crash - the machine reboots? Can you see something in the screen? I'd like to see a kernel log when that crash happens - one alternative is to enable kdump, are you willing to do that? If so, please run: sudo apt-get update sudo apt-get install linux-crashdump (and stick with the defaults during installation questions). After that, reboot the system and execute "kdump-config show" and check if it mentions "ready to kdump". If so, when next time you have a crash event and machine reboots, please check if you have a file created in /var/crash/ and submit such files to us. Cheers, Guilherme -- 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/1919070 Title: Unstable and frequent crashes kernel 5.4.0-66-generic on ASUS E201NAS (5.4.0-65-generic is good) Status in linux package in Ubuntu: Confirmed Bug description: Version: Kubuntu 20.04.1 System: ASUS E201NAS KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-66-generic OS Type: 64-bit Processors: 2 × Intel® Celeron® CPU N3350 @ 1.10GHz Memory: 3.7 GiB of RAM Notes: linux-image-5.4.0-65-generic and prior versions are excellent. Since the kernel update to 5.4.0-66-generic the system is very unstable, freezes and has frequent crashes. I'm using to linux- image-5.4.0-65-generic for this report. This is my first Ubuntu bug report. Let me know if you need information. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sam1157 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-05 (160 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:5a06 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 13d3:3496 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E201NAS Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=6c2a5e29-03e2-41c6-a0fa-80222b2350d9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 Tags: focal Uname: Linux 5.4.0-66-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E201NAS.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E201NAS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE201NAS.311:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnE201NAS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE201NAS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: E201NAS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919150] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1919150 Title: My keybord does not work Status in linux package in Ubuntu: Confirmed Bug description: I am using UBUNTU 18. My keyboard and mouse do not work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-136-generic 4.15.0-136.140 ProcVersionSignature: Ubuntu 4.15.0-136.140-generic 4.15.18 Uname: Linux 4.15.0-136-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: elham 1797 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Mar 15 13:24:06 2021 HibernationDevice: RESUME=UUID=0cd3cd69-2564-4117-a21b-1c28c2a83019 InstallationDate: Installed on 2018-11-15 (850 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20L8S02D00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-136-generic root=UUID=17a0324e-ead9-4861-bdd0-60ece73973f5 ro quiet splash atkbd.reset vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-136-generic N/A linux-backports-modules-4.15.0-136-generic N/A linux-firmware 1.173.18 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET48W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET48W(1.25):bd07/18/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919150/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919150] [NEW] My keybord does not work
Public bug reported: I am using UBUNTU 18. My keyboard and mouse do not work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-136-generic 4.15.0-136.140 ProcVersionSignature: Ubuntu 4.15.0-136.140-generic 4.15.18 Uname: Linux 4.15.0-136-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: elham 1797 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Mar 15 13:24:06 2021 HibernationDevice: RESUME=UUID=0cd3cd69-2564-4117-a21b-1c28c2a83019 InstallationDate: Installed on 2018-11-15 (850 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20L8S02D00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-136-generic root=UUID=17a0324e-ead9-4861-bdd0-60ece73973f5 ro quiet splash atkbd.reset vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-136-generic N/A linux-backports-modules-4.15.0-136-generic N/A linux-firmware 1.173.18 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET48W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET48W(1.25):bd07/18/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1919150 Title: My keybord does not work Status in linux package in Ubuntu: New Bug description: I am using UBUNTU 18. My keyboard and mouse do not work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-136-generic 4.15.0-136.140 ProcVersionSignature: Ubuntu 4.15.0-136.140-generic 4.15.18 Uname: Linux 4.15.0-136-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: elham 1797 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Mar 15 13:24:06 2021 HibernationDevice: RESUME=UUID=0cd3cd69-2564-4117-a21b-1c28c2a83019 InstallationDate: Installed on 2018-11-15 (850 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20L8S02D00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-136-generic root=UUID=17a0324e-ead9-4861-bdd0-60ece73973f5 ro quiet splash atkbd.reset vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-136-generic N/A linux-backports-modules-4.15.0-136-generic N/A linux-firmware 1.173.18 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET48W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET48W(1.25):bd07/18/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919150/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916046] Re: cve-2020-29373 in cve from ubuntu_ltp failed
Here is the log for this test on F-OEM-5.6 (node spitfire) startup='Sat Mar 13 04:58:36 2021' tst_test.c:1289: TINFO: Timeout per run is 0h 05m 00s Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Cannot kill test processes! Congratulation, likely test hit a kernel bug. Exitting uncleanly... tag=cve-2020-29373 stime=1615611516 dur=350 exit=exited stat=1 core=no cu=0 cs=0 -- 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/1916046 Title: cve-2020-29373 in cve from ubuntu_ltp failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: New Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: Not a regression, this is a new test added Feb 8, 2021: https://github.com/linux-test- project/ltp/commit/c4f669f13106862b6d8be38adf7825ae00ca7ac5 The log shows: 13260.02/08 21:37:31 DEBUG| utils:0153| [stdout] startup='Mon Feb 8 21:37:30 2021' 13261.02/08 21:37:31 DEBUG| utils:0153| [stdout] tst_test.c:1261: TINFO: Timeout per run is 0h 05m 00s 13262.02/08 21:37:31 DEBUG| utils:0153| [stdout] io_uring02.c:148: TFAIL: Write outside chroot succeeded. 13263.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13264.02/08 21:37:31 DEBUG| utils:0153| [stdout] HINT: You _MAY_ be missing kernel fixes, see: 13265.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13266.02/08 21:37:31 DEBUG| utils:0153| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9392a27d88b9 13267.02/08 21:37:31 DEBUG| utils:0153| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff002b30181d 13268.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13269.02/08 21:37:31 DEBUG| utils:0153| [stdout] HINT: You _MAY_ be vulnerable to CVE(s), see: 13270.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13271.02/08 21:37:31 DEBUG| utils:0153| [stdout] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29373 13272.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13273.02/08 21:37:31 DEBUG| utils:0153| [stdout] Summary: 13274.02/08 21:37:31 DEBUG| utils:0153| [stdout] passed 0 13275.02/08 21:37:31 DEBUG| utils:0153| [stdout] failed 1 13276.02/08 21:37:31 DEBUG| utils:0153| [stdout] broken 0 13277.02/08 21:37:31 DEBUG| utils:0153| [stdout] skipped 0 13278.02/08 21:37:31 DEBUG| utils:0153| [stdout] warnings 0 13279.02/08 21:37:31 DEBUG| utils:0153| [stdout] tag=cve-2020-29373 stime=1612820250 dur=0 exit=exited stat=1 core=no cu=0 As of Feb 18, 2021, this CVE is not mitigated yet: https://ubuntu.com/security/CVE-2020-29373 Seen with linux-kvm 5.4.0-1033.34. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1916046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919070] Re: Unstable and frequent crashes kernel 5.4.0-66-generic on ASUS E201NAS (5.4.0-65-generic is good)
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1919070 Title: Unstable and frequent crashes kernel 5.4.0-66-generic on ASUS E201NAS (5.4.0-65-generic is good) Status in linux package in Ubuntu: Confirmed Bug description: Version: Kubuntu 20.04.1 System: ASUS E201NAS KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-66-generic OS Type: 64-bit Processors: 2 × Intel® Celeron® CPU N3350 @ 1.10GHz Memory: 3.7 GiB of RAM Notes: linux-image-5.4.0-65-generic and prior versions are excellent. Since the kernel update to 5.4.0-66-generic the system is very unstable, freezes and has frequent crashes. I'm using to linux- image-5.4.0-65-generic for this report. This is my first Ubuntu bug report. Let me know if you need information. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sam1157 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-05 (160 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:5a06 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 13d3:3496 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E201NAS Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=6c2a5e29-03e2-41c6-a0fa-80222b2350d9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 Tags: focal Uname: Linux 5.4.0-66-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E201NAS.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E201NAS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE201NAS.311:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnE201NAS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE201NAS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: E201NAS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916046] Re: cve-2020-29373 in cve from ubuntu_ltp failed
Interesting thing on that CVE page is that this is marked as "Not vulnerable" to most of our kernels. Or even with "Does not exist". This might needs to be investigated. ** Tags added: 5.4 -- 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/1916046 Title: cve-2020-29373 in cve from ubuntu_ltp failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: New Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: Not a regression, this is a new test added Feb 8, 2021: https://github.com/linux-test- project/ltp/commit/c4f669f13106862b6d8be38adf7825ae00ca7ac5 The log shows: 13260.02/08 21:37:31 DEBUG| utils:0153| [stdout] startup='Mon Feb 8 21:37:30 2021' 13261.02/08 21:37:31 DEBUG| utils:0153| [stdout] tst_test.c:1261: TINFO: Timeout per run is 0h 05m 00s 13262.02/08 21:37:31 DEBUG| utils:0153| [stdout] io_uring02.c:148: TFAIL: Write outside chroot succeeded. 13263.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13264.02/08 21:37:31 DEBUG| utils:0153| [stdout] HINT: You _MAY_ be missing kernel fixes, see: 13265.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13266.02/08 21:37:31 DEBUG| utils:0153| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9392a27d88b9 13267.02/08 21:37:31 DEBUG| utils:0153| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff002b30181d 13268.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13269.02/08 21:37:31 DEBUG| utils:0153| [stdout] HINT: You _MAY_ be vulnerable to CVE(s), see: 13270.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13271.02/08 21:37:31 DEBUG| utils:0153| [stdout] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29373 13272.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13273.02/08 21:37:31 DEBUG| utils:0153| [stdout] Summary: 13274.02/08 21:37:31 DEBUG| utils:0153| [stdout] passed 0 13275.02/08 21:37:31 DEBUG| utils:0153| [stdout] failed 1 13276.02/08 21:37:31 DEBUG| utils:0153| [stdout] broken 0 13277.02/08 21:37:31 DEBUG| utils:0153| [stdout] skipped 0 13278.02/08 21:37:31 DEBUG| utils:0153| [stdout] warnings 0 13279.02/08 21:37:31 DEBUG| utils:0153| [stdout] tag=cve-2020-29373 stime=1612820250 dur=0 exit=exited stat=1 core=no cu=0 As of Feb 18, 2021, this CVE is not mitigated yet: https://ubuntu.com/security/CVE-2020-29373 Seen with linux-kvm 5.4.0-1033.34. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1916046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916046] Re: cve-2020-29373 in cve from ubuntu_ltp failed
Described commit for the fix: * commit 9392a27d88b9707145d713654eb26f0c29789e50 * Author: Jens Axboe * Date: Thu Feb 6 21:42:51 2020 -0700 * * io-wq: add support for inheriting ->fs * * commit ff002b30181d30cdfbca316dadd099c3ca0d739c * Author: Jens Axboe * Date: Fri Feb 7 16:05:21 2020 -0700 * * io_uring: grab ->fs as part of async preparation Can be found in G/H. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags added: ubuntu-ltp-syscalls ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Groovy) Status: New => Fix Released ** Changed in: linux (Ubuntu Hirsute) Status: New => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-29373 -- 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/1916046 Title: cve-2020-29373 in cve from ubuntu_ltp failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: New Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: Not a regression, this is a new test added Feb 8, 2021: https://github.com/linux-test- project/ltp/commit/c4f669f13106862b6d8be38adf7825ae00ca7ac5 The log shows: 13260.02/08 21:37:31 DEBUG| utils:0153| [stdout] startup='Mon Feb 8 21:37:30 2021' 13261.02/08 21:37:31 DEBUG| utils:0153| [stdout] tst_test.c:1261: TINFO: Timeout per run is 0h 05m 00s 13262.02/08 21:37:31 DEBUG| utils:0153| [stdout] io_uring02.c:148: TFAIL: Write outside chroot succeeded. 13263.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13264.02/08 21:37:31 DEBUG| utils:0153| [stdout] HINT: You _MAY_ be missing kernel fixes, see: 13265.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13266.02/08 21:37:31 DEBUG| utils:0153| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9392a27d88b9 13267.02/08 21:37:31 DEBUG| utils:0153| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff002b30181d 13268.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13269.02/08 21:37:31 DEBUG| utils:0153| [stdout] HINT: You _MAY_ be vulnerable to CVE(s), see: 13270.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13271.02/08 21:37:31 DEBUG| utils:0153| [stdout] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29373 13272.02/08 21:37:31 DEBUG| utils:0153| [stdout] 13273.02/08 21:37:31 DEBUG| utils:0153| [stdout] Summary: 13274.02/08 21:37:31 DEBUG| utils:0153| [stdout] passed 0 13275.02/08 21:37:31 DEBUG| utils:0153| [stdout] failed 1 13276.02/08 21:37:31 DEBUG| utils:0153| [stdout] broken 0 13277.02/08 21:37:31 DEBUG| utils:0153| [stdout] skipped 0 13278.02/08 21:37:31 DEBUG| utils:0153| [stdout] warnings 0 13279.02/08 21:37:31 DEBUG| utils:0153| [stdout] tag=cve-2020-29373 stime=1612820250 dur=0 exit=exited stat=1 core=no cu=0 As of Feb 18, 2021, this CVE is not mitigated yet: https://ubuntu.com/security/CVE-2020-29373 Seen with linux-kvm 5.4.0-1033.34. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1916046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
UX433F Ubuntu 18.04 doesn't work sudo i2ctransfer -f -y 0 w13@0x15 0x05 0x00 0x3d 0x03 0x06 0x00 0x07 0x00 0x0d 0x14 0x03 0x00 0xad Error: Sending messages failed: Remote I/O error Cheers, Andrea Il giorno lun 15 mar 2021 alle ore 11:01 Pilot6 <1810...@bugs.launchpad.net> ha scritto: > I confirm that the command works for me too. But the numberpad doesn't > seem to send input events. > In this state a python script should work, but it is not a way of doing it > properly. The numberpad should work as a keyboard. It is detected already > as one. Maybe another command is needed to enable input. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1823320). > https://bugs.launchpad.net/bugs/1810183 > > Title: > numpad on touchpad doesn't work in ASUS Zenbook 14 > > Status in Linux: > New > Status in linux package in Ubuntu: > Confirmed > > Bug description: > I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 > alongside windows 10. > The numeric keypads are within the touchpad and are supposed to be > turned on by a button on the touchpad. This works well in Windows but > doesn't work in Ubuntu. > I have tried to search for any related problems/solutions online but I > haven't been able to. > I will appreciate any suggestion or help. > Thanks, > --- > ProblemType: Bug > ApportVersion: 2.20.10-0ubuntu13.1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > DistroRelease: Ubuntu 18.10 > InstallationDate: Installed on 2018-12-30 (4 days ago) > InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.3) > Package: linux (not installed) > Tags: cosmic > Uname: Linux 4.19.11-041911-generic x86_64 > UnreportableReason: The running kernel is not an Ubuntu kernel > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > --- > ProblemType: Bug > ApportVersion: 2.20.10-0ubuntu13.1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > DistroRelease: Ubuntu 18.10 > InstallationDate: Installed on 2018-12-30 (4 days ago) > InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.3) > Package: linux (not installed) > Tags: cosmic > Uname: Linux 4.18.10-041810-generic x86_64 > UnreportableReason: The running kernel is not an Ubuntu kernel > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > > To manage notifications about this bug go to: > https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions > -- -- Andrea Mattana -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830585] Re: cpuset_memory_spread from controllers test suite in LTP failed (hog the memory on the unexpected node)
Found on F-OEM-5.6 5.6.0-1050.54 ** Summary changed: - cpuset_memory_spread from controllers test suite in LTP failed + cpuset_memory_spread from controllers test suite in LTP failed (hog the memory on the unexpected node) ** Tags added: 5.6 focal oem sru-20210222 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1830585 Title: cpuset_memory_spread from controllers test suite in LTP failed (hog the memory on the unexpected node) Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Bug description: Test failed with: cpuset_memory_spread 7 TFAIL: hog the memory on the unexpected node(FilePages_For_Nodes(KB): _0: 2276 _1: 102428, Expect Nodes: 1). <<>> tag=cpuset_memory_spread stime=1558937747 cmdline=" cpuset_memory_spread_testset.sh" contacts="" analysis=exit <<>> 100+0 records in 100+0 records out 104857600 bytes (105 MB, 100 MiB) copied, 0.0993112 s, 1.1 GB/s cpuset_memory_spread 1 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 3 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 5 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 7 TFAIL: hog the memory on the unexpected node(FilePages_For_Nodes(KB): _0: 2276 _1: 102428, Expect Nodes: 1). cpuset_memory_spread 9 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 11 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 13 TPASS: Cpuset memory spread page test succeeded. <<>> initiation_status="ok" duration=10 termination_type=exited termination_id=1 corefile=no cutime=364 cstime=383 <<>> ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-15-generic 5.0.0-15.16 ProcVersionSignature: User Name 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 27 05:39 seq crw-rw 1 root audio 116, 33 May 27 05:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon May 27 06:16:49 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.product.sku: 780020-S01 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1914283] Re: Enable CONFIG_PCI_MSI in the linux-kvm derivative
This bug was fixed in the package linux-kvm - 4.15.0-1086.88 --- linux-kvm (4.15.0-1086.88) bionic; urgency=medium * bionic/linux-kvm: 4.15.0-1086.88 -proposed tracker (LP: #1916190) * Enable CONFIG_PCI_MSI in the linux-kvm derivative (LP: #1914283) - [Config] kvm: enable PCI_MSI [ Ubuntu: 4.15.0-137.141 ] * bionic/linux: 4.15.0-137.141 -proposed tracker (LP: #1916199) * Fix oops in skb_segment for Bionic series (LP: #1915552) - net: permit skb_segment on head_frag frag_list skb - net: bpf: add a test for skb_segment in test_bpf module - test_bpf: Fix NULL vs IS_ERR() check in test_skb_segment() * Bionic update: upstream stable patchset 2021-02-10 (LP: #1915328) - net: cdc_ncm: correct overhead in delayed_ndp_size - net: vlan: avoid leaks on register_vlan_dev() failures - net: ip: always refragment ip defragmented packets - net: fix pmtu check in nopmtudisc mode - x86/resctrl: Use an IPI instead of task_work_add() to update PQR_ASSOC MSR - x86/resctrl: Don't move a task to the same resource group - vmlinux.lds.h: Add PGO and AutoFDO input sections - drm/i915: Fix mismatch between misplaced vma check and vma insert - spi: pxa2xx: Fix use-after-free on unbind - iio: imu: st_lsm6dsx: flip irq return logic - iio: imu: st_lsm6dsx: fix edge-trigger interrupts - ARM: OMAP2+: omap_device: fix idling of devices during probe - i2c: sprd: use a specific timeout to avoid system hang up issue - cpufreq: powernow-k8: pass policy rather than use cpufreq_cpu_get() - spi: stm32: FIFO threshold level - fix align packet size - dmaengine: xilinx_dma: check dma_async_device_register return value - dmaengine: xilinx_dma: fix mixed_enum_type coverity warning - wil6210: select CONFIG_CRC32 - block: rsxx: select CONFIG_CRC32 - iommu/intel: Fix memleak in intel_irq_remapping_alloc - net/mlx5e: Fix memleak in mlx5e_create_l2_table_groups - net/mlx5e: Fix two double free cases - wan: ds26522: select CONFIG_BITREVERSE - KVM: arm64: Don't access PMCR_EL0 when no PMU is available - block: fix use-after-free in disk_part_iter_next - net: drop bogus skb with CHECKSUM_PARTIAL and offset beyond end of trimmed packet - net: hns3: fix the number of queues actually used by ARQ - net: stmmac: dwmac-sun8i: Balance internal PHY resource references - net: stmmac: dwmac-sun8i: Balance internal PHY power - net/sonic: Fix some resource leaks in error handling paths - net: ipv6: fib: flush exceptions when purging route - dmaengine: xilinx_dma: fix incompatible param warning in _child_probe() - lightnvm: select CONFIG_CRC32 - ASoC: dapm: remove widget from dirty list on free - MIPS: boot: Fix unaligned access with CONFIG_MIPS_RAW_APPENDED_DTB - MIPS: relocatable: fix possible boot hangup with KASLR enabled - ACPI: scan: Harden acpi_device_add() against device ID overflows - mm/hugetlb: fix potential missing huge page size info - dm snapshot: flush merged data before committing metadata - r8152: Add Lenovo Powered USB-C Travel Hub - ext4: fix bug for rename with RENAME_WHITEOUT - ARC: build: remove non-existing bootpImage from KBUILD_IMAGE - ARC: build: add uImage.lzma to the top-level target - ARC: build: add boot_targets to PHONY - btrfs: fix transaction leak and crash after RO remount caused by qgroup rescan - ethernet: ucc_geth: fix definition and size of ucc_geth_tx_global_pram - arch/arc: add copy_user_page() to to fix build error on ARC - misdn: dsp: select CONFIG_BITREVERSE - net: ethernet: fs_enet: Add missing MODULE_LICENSE - ACPI: scan: add stub acpi_create_platform_device() for !CONFIG_ACPI - ARM: picoxcell: fix missing interrupt-parent properties - dump_common_audit_data(): fix racy accesses to ->d_name - ASoC: Intel: fix error code cnl_set_dsp_D0() - NFS4: Fix use-after-free in trace_event_raw_event_nfs4_set_lock - pNFS: Mark layout for return if return-on-close was not sent - NFS: nfs_igrab_and_active must first reference the superblock - ext4: fix superblock checksum failure when setting password salt - RDMA/usnic: Fix memleak in find_free_vf_and_create_qp_grp - mm, slub: consider rest of partial list if acquire_slab() fails - net: sunrpc: interpret the return value of kstrtou32 correctly - dm: eliminate potential source of excessive kernel log noise - ALSA: firewire-tascam: Fix integer overflow in midi_port_work() - ALSA: fireface: Fix integer overflow in transmit_midi_msg() - netfilter: conntrack: fix reading nf_conntrack_buckets - usb: ohci: Make distrust_firmware param default to false - nfsd4: readdirplus shouldn't return parent of export - netxen_nic: fix MSI/MSI-x interrupts - rndis_host: set proper input size for OID_GEN_PHYSICAL_MEDIUM request - esp: avoid unneeded kmap_atomic call - net: dcb: Val
