[Kernel-packages] [Bug 2062576] Re: Keyboard stops working after suspend 5.15.0-105
I have the same issue on Ubuntu 22.04.4 LTS after the kernel update from: Linux laptop 6.5.0-26-generic to Linux laptop 6.5.0-27-generic -- 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/2062576 Title: Keyboard stops working after suspend 5.15.0-105 Status in linux package in Ubuntu: Confirmed Bug description: Kernel updates on Apr 8 '24 started the issue of keyboard not working after sleep/suspend. Kernel 5.15.0-97 works, other kernels after 97 need grub modified to make them work. Changed: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.dumbkbd=1 i8042.nomux=1 i8042.noaux=1" Only negative side effect of the i8042.dumbkbd entry is that the caps- lock light does not work. Otherwise on suspend and wake the keyboard works. I even tried the 6.6.0-26 kernel with same issue. version.log: Ubuntu 5.15.0-105.115-generic 5.15.148 alan: ~ $ lsb_release -rd Description: Linux Mint 21.3 Release: 21.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062576/+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 2052441] Re: 2024.01.23 new upstream release
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/2052441 Title: 2024.01.23 new upstream release Status in wireless-regdb package in Ubuntu: New Bug description: Would it be possible to update the wireless-regdb on all active ubuntu releases to the latest upstream (2024-01.23) release? New regulations have been published. One of those is the 6GHz Wifi in Switzerland. The current package, 2022.06.06 is quite outdated. With an update I'd be able to connect to Wifi 6E networks in the CH regdomain. Without, I can't see the 6GHz band with iw reg get. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/2052441/+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 2039773] Re: package linux-image-6.2.0-31-generic 6.2.0-31.31 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
*** This bug is a duplicate of bug 2039772 *** https://bugs.launchpad.net/bugs/2039772 ** This bug has been marked a duplicate of bug 2039772 package linux-image-6.2.0-31-generic 6.2.0-31.31 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2039773 Title: package linux-image-6.2.0-31-generic 6.2.0-31.31 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: New Bug description: package linux-image-6.2.0-31-generic 6.2.0-31.31 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-31-generic 6.2.0-31.31 ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: beyagu 1865 F pulseaudio /dev/snd/pcmC0D0p: beyagu 1865 F...m pulseaudio /dev/snd/controlC1: beyagu 1865 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Wed Oct 18 06:39:04 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2023-06-28 (112 days ago) InstallationMedia: Ubuntu-Unity 23.04 "Lunar Lobster" - Release amd64 (20230419) IwConfig: lono wireless extensions. enp3s0no wireless extensions. docker0 no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=603facbe-a5f3-4d8a-b62d-bd59c2ddf5c4 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.4, python-is-python3, 3.11.1-3 RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: SourcePackage: dkms Title: package linux-image-6.2.0-31-generic 6.2.0-31.31 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2017 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61 dmi.board.vendor: INTEL Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/19/2017:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnH61:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2039773/+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 1973434] Re: massive performance issues since 22.04 upgrade
I conquer with chris (platoscave). Pretty all my problems went a away with time by magic. It is obvious that many bugs plagued us and where fixed by the different projects composing Ubuntu as time passed by. 22.04 just wasn't ready went it came out. My only issue that remains is when waking up my laptop from S3, everything is (almost) frozen for at least 5 seconds; seams that the CPU hits 100% (no confirmation) for some reason. But that should be another bug report. I am running under Wayland now, btw. System: Dell Latitude E7470 (2016), Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, Skylake GT2 [HD Graphics 520], 32 GiB Ram, 1 TiB SSD, 1900x1080 screen. -- 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/1973434 Title: massive performance issues since 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, After upgrading to 22.04 i had to fight with massive performance issues. Browsers appeared to hang every other minute, youtube videos being laggy and hang in between, applications in a virtualbox VM where slow and also hanging every other minute to a level of not being useable. On a pretty recent and powerful system just 2 years old. I noticed CPU jumps in top, but also somehow thought it could be a graphics issue so invested some time installing nvidia drivers properly. Also I wondered if it might be the lowlatency kernel I normally use because I do audio stuff, and switched to generic. But nothing helped. ThenI had the idea it could be a kernel/scheduler issue because the system wasn't always slow, but it appeared certain things kept hanging when other processed had a lot of cpu for a few seconds. So I got a recent mainline kernel, configured it with my last running config from 21.10 before the update, made the debs and installed them, and now can tell that a mainline kernel 5.17.7 with all the dkms modules that i had before which got compiled automatically at installation brings back a "normal" performance. I can browse the web, run multiple youtube vids at once, even in another browser, have thunderbird running, and a virtualbox machine open with another browser for some web app testing and everything runs fine and smooth, no lagging. Not sure yet what the real reason is - either the kernel version, or a patch in the ubuntu version, or the 22.04 kernel config so far, or some configuration made in 21.10 that isn't good with 22.04 and it's kernel anymore. I will go ahead tomorrow and see if I can build a vanilla kernel with the config from the ubuntu 22.04 kernel and "make oldconfig", then I will be able to tell if only the config is making the difference. Please let me know of there is anything I should test to further analyze this issue, or any ideas I can try to solve it without having to run a mainline manually installed kernel. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.30.33 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henning6198 F pulseaudio /dev/snd/controlC1: henning6198 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 14 23:02:38 2022 InstallationDate: Installed on 2020-04-12 (761 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QV00CEGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=/dev/mapper/vgubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET55W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QV00CEGE dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor:
[Kernel-packages] [Bug 2000431] Re: package nvidia-fabricmanager-515 (not installed) failed to install/upgrade: trying to overwrite '/lib/systemd/system/nvidia-fabricmanager.service', which is also in
** Also affects: fabric-manager-510 (Ubuntu) Importance: Undecided Status: New ** Tags added: package-conflict -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to fabric-manager-515 in Ubuntu. https://bugs.launchpad.net/bugs/2000431 Title: package nvidia-fabricmanager-515 (not installed) failed to install/upgrade: trying to overwrite '/lib/systemd/system/nvidia- fabricmanager.service', which is also in package nvidia- fabricmanager-510 515.86.01-0ubuntu0.22.04.1 Status in fabric-manager-510 package in Ubuntu: New Status in fabric-manager-515 package in Ubuntu: New Bug description: jacques@ubuntu-jds:~$ df Filesystem 1K-blocks Used Available Use% Mounted on tmpfs1600152 2400 1597752 1% /run /dev/nvme0n1p9 82772264 75967972 2553668 97% / tmpfs800074460108 7940636 1% /dev/shm tmpfs 51204 5116 1% /run/lock tmpfs80007440 8000744 0% /run/qemu /dev/nvme0n1p2 9830467147 31157 69% /boot/efi tmpfs1600148 136 1600012 1% /run/user/1000 jacques@ubuntu-jds:/usr/local/applications/Zoiper5$ sudo apt install iptraf-ng Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: cuda-drivers-fabricmanager-515 : Depends: nvidia-fabricmanager-515 (= 515.86.01-0ubuntu0.22.04.1) but it is not going to be installed nvidia-fabricmanager-510 : Depends: nvidia-fabricmanager-515 but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). jacques@ubuntu-jds:/usr/local/applications/Zoiper5$ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: libflashrom1 libftdi1-2 nvidia-fabricmanager-510 Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: nvidia-fabricmanager-515 The following NEW packages will be installed: nvidia-fabricmanager-515 0 upgraded, 1 newly installed, 0 to remove and 62 not upgraded. 3 not fully installed or removed. Need to get 0 B/1,568 kB of archives. After this operation, 8,005 kB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 292422 files and directories currently installed.) Preparing to unpack .../nvidia-fabricmanager-515_515.86.01-0ubuntu0.22.04.1_amd6 4.deb ... Unpacking nvidia-fabricmanager-515 (515.86.01-0ubuntu0.22.04.1) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-fabricmanager-515_ 515.86.01-0ubuntu0.22.04.1_amd64.deb (--unpack): trying to overwrite '/lib/systemd/system/nvidia-fabricmanager.service', which i s also in package nvidia-fabricmanager-510 515.86.01-0ubuntu0.22.04.1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/nvidia-fabricmanager-515_515.86.01-0ubuntu0.22.04.1_amd 64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) jacques@ubuntu-jds:/usr/local/applications/Zoiper5$ ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-fabricmanager-515 (not installed) ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.2 AptOrdering: nvidia-fabricmanager-515:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Dec 25 10:16:45 2022 DpkgTerminalLog: Preparing to unpack .../nvidia-fabricmanager-515_515.86.01-0ubuntu0.22.04.1_amd64.deb ... Unpacking nvidia-fabricmanager-515 (515.86.01-0ubuntu0.22.04.1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/nvidia-fabricmanager-515_515.86.01-0ubuntu0.22.04.1_amd64.deb (--unpack): trying to overwrite '/lib/systemd/system/nvidia-fabricmanager.service', which is also in package nvidia-fabricmanager-510 515.86.01-0ubuntu0.22.04.1 ErrorMessage: trying to overwrite '/lib/systemd/system/nvidia-fabricmanager.service', which is also in package nvidia-fabricmanager-510 515.86.01-0ubuntu0.22.04.1 InstallationDate: Installed on 2022-06-07 (201 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: fabric-manager-515 Title: package nvidia-fabricmanager-515 (not installed)
[Kernel-packages] [Bug 1996678] Re: containerd sporadic timeouts
The conclusion at https://github.com/prometheus/node_exporter/issues/2500 was that the relevant kernel change that caused this was `- epoll: autoremove wakers even more aggressively`. There is a small bug reproduction script in that issue too. ** Bug watch added: github.com/prometheus/node_exporter/issues #2500 https://github.com/prometheus/node_exporter/issues/2500 -- 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/1996678 Title: containerd sporadic timeouts Status in containerd package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in containerd source package in Focal: New Status in linux source package in Focal: In Progress Bug description: This morning I routinely upgraded security upgrades on number of machines. Containerd has upgraded from `1.5.9-0ubuntu1~20.04.4` for me `1.5.9-0ubuntu1~20.04.5`. What happened next: at some random time on machines with new containerd something happens with containerd tasks and/or cgroups. This is how it's seen in syslog: containerd[710]: time="2022-11-16T03:21:21.004153517Z" level=error msg="get state for 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a" error="context deadline exceeded: unknown" And some ctr commands: # ctr --namespace k8s.io task ls|grep 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a0 UNKNOWN See that the status of the task is UNKNOWN (!!!) # ctr --namespace k8s.io container ls|grep 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a k8s.gcr.io/pause:3.5 io.containerd.runc.v2 Cgroups: ├─kubepods-besteffort-pod3fdc0061_bbf6_47d1_97f5_b1f271b46e23.slice │ ├─cri-containerd-5f78e0cb957de97fd8465cc42c842bdd764d981ca7a903a2515bbc6bb06796a9.scope … │ │ └─2677 /csi-node-driver-registrar --v=0 --csi-address=/csi/csi.sock --k… │ ├─cri-containerd-af070f16c1f0ff22eb16661e787e85db3810727909abd23d69a6a43578c1dced.scope … │ │ └─3264 /usr/local/bin/cephcsi --type=liveness --endpoint=unix:///csi/cs… │ ├─cri-containerd-4e063ef0c8f768dbf34cf7a179bca5cc98a04fa7e00b29d20c17d3031d409f86.scope … │ │ └─2960 /usr/local/bin/cephcsi --nodeid=nas-decent-bobcat.dev-k8s-1.hq.w… │ └─cri-containerd-2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a.scope … │ └─2414 /pause # ps auxf|grep 2414 -B 2 root2279 0.1 0.0 114100 4956 ?Sl Nov15 0:42 /usr/bin/containerd-shim-runc-v2 -namespace k8s.io -id 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a -address /run/containerd/containerd.sock 65535 2414 0.0 0.0964 4 ?Ss Nov15 0:00 \_ /pause It happens not immediately - but after some random time. Sometimes it's several minutes, sometimes it's around an hour. But nonetheless - all machines with the new package get into this weird state. As long as I revert package - it all returns to run as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1996678/+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 1973434] Re: massive performance issues since 22.04 upgrade
I just noticed that when I simply move the mouse, gnome-shell CPU jumps up 30% CPU. For those of you suffering from this problem, this is the issue to follow: https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/4130 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4130 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4130 -- 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/1973434 Title: massive performance issues since 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, After upgrading to 22.04 i had to fight with massive performance issues. Browsers appeared to hang every other minute, youtube videos being laggy and hang in between, applications in a virtualbox VM where slow and also hanging every other minute to a level of not being useable. On a pretty recent and powerful system just 2 years old. I noticed CPU jumps in top, but also somehow thought it could be a graphics issue so invested some time installing nvidia drivers properly. Also I wondered if it might be the lowlatency kernel I normally use because I do audio stuff, and switched to generic. But nothing helped. ThenI had the idea it could be a kernel/scheduler issue because the system wasn't always slow, but it appeared certain things kept hanging when other processed had a lot of cpu for a few seconds. So I got a recent mainline kernel, configured it with my last running config from 21.10 before the update, made the debs and installed them, and now can tell that a mainline kernel 5.17.7 with all the dkms modules that i had before which got compiled automatically at installation brings back a "normal" performance. I can browse the web, run multiple youtube vids at once, even in another browser, have thunderbird running, and a virtualbox machine open with another browser for some web app testing and everything runs fine and smooth, no lagging. Not sure yet what the real reason is - either the kernel version, or a patch in the ubuntu version, or the 22.04 kernel config so far, or some configuration made in 21.10 that isn't good with 22.04 and it's kernel anymore. I will go ahead tomorrow and see if I can build a vanilla kernel with the config from the ubuntu 22.04 kernel and "make oldconfig", then I will be able to tell if only the config is making the difference. Please let me know of there is anything I should test to further analyze this issue, or any ideas I can try to solve it without having to run a mainline manually installed kernel. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.30.33 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henning6198 F pulseaudio /dev/snd/controlC1: henning6198 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 14 23:02:38 2022 InstallationDate: Installed on 2020-04-12 (761 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QV00CEGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=/dev/mapper/vgubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET55W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QV00CEGE dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1973434] Re: massive performance issues since 22.04 upgrade
Three days after I commented here (2022-09-26), after and update with reboot and switching back to Wayland, I notice a good performance improvement. I cannot explain why. I still suffer from Video stuttering and lagging across all players (probably another bug though) and when my system resume from suspend (S3), it is almost "frozen" for 5s at least because the CPU spikes very high for that brief period of time. I cannot figure out what process hugs the CPU like that though. System: Dell Latitude E7470 (2016), Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, Skylake GT2 [HD Graphics 520], 32 GiB Ram, 1 TiB SSD, 1900x1080 screen. -- 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/1973434 Title: massive performance issues since 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, After upgrading to 22.04 i had to fight with massive performance issues. Browsers appeared to hang every other minute, youtube videos being laggy and hang in between, applications in a virtualbox VM where slow and also hanging every other minute to a level of not being useable. On a pretty recent and powerful system just 2 years old. I noticed CPU jumps in top, but also somehow thought it could be a graphics issue so invested some time installing nvidia drivers properly. Also I wondered if it might be the lowlatency kernel I normally use because I do audio stuff, and switched to generic. But nothing helped. ThenI had the idea it could be a kernel/scheduler issue because the system wasn't always slow, but it appeared certain things kept hanging when other processed had a lot of cpu for a few seconds. So I got a recent mainline kernel, configured it with my last running config from 21.10 before the update, made the debs and installed them, and now can tell that a mainline kernel 5.17.7 with all the dkms modules that i had before which got compiled automatically at installation brings back a "normal" performance. I can browse the web, run multiple youtube vids at once, even in another browser, have thunderbird running, and a virtualbox machine open with another browser for some web app testing and everything runs fine and smooth, no lagging. Not sure yet what the real reason is - either the kernel version, or a patch in the ubuntu version, or the 22.04 kernel config so far, or some configuration made in 21.10 that isn't good with 22.04 and it's kernel anymore. I will go ahead tomorrow and see if I can build a vanilla kernel with the config from the ubuntu 22.04 kernel and "make oldconfig", then I will be able to tell if only the config is making the difference. Please let me know of there is anything I should test to further analyze this issue, or any ideas I can try to solve it without having to run a mainline manually installed kernel. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.30.33 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henning6198 F pulseaudio /dev/snd/controlC1: henning6198 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 14 23:02:38 2022 InstallationDate: Installed on 2020-04-12 (761 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QV00CEGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=/dev/mapper/vgubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET55W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QV00CEGE dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To manage notifications
[Kernel-packages] [Bug 1973434] Re: massive performance issues since 22.04 upgrade
Like everyone else, I am experiencing the same issues. "intel_iommu=off" in Grub does not help. Here are some symptoms I suffer; not sure if they are related to this bug or not, but worth mentioning since they all degrade my Ubuntu experience since I upgraded from 20.04 to 22.04. - Overall stuttering; Alt-tab, switch workspace or switch to another application by selecting it and typing lags a few 100ms. - Gnome animations are not smooth. - Video stuttering and tearing with any piece of software (VLC, Chrome, Xine...). Have a Skylake GT2 [HD Graphics 520]. Is hardware acceleration enabled? I have no clue how to figure this out. - gnome-shell always running at more than 6% CPU, jumping often up to 20%, under Xorg. It was way worse when under Wayland. Lets say the average is about 11% CPU. - System is "frozen" for 5s every time it wakes up from Suspend to RAM (S3). Under 20.04, response was instantaneous. You can move the mouse during that 5s period, but nothing responds to the keyboard or mouse buttons. System: Dell Latitude E7470 (2016), Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, Skylake GT2 [HD Graphics 520], 32 GiB Ram, 1 TiB SSD, 1900x1080 screen. My CPU profile is always set at "High Performance" and my CPU clock is always around 2.7x GHz. -- 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/1973434 Title: massive performance issues since 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, After upgrading to 22.04 i had to fight with massive performance issues. Browsers appeared to hang every other minute, youtube videos being laggy and hang in between, applications in a virtualbox VM where slow and also hanging every other minute to a level of not being useable. On a pretty recent and powerful system just 2 years old. I noticed CPU jumps in top, but also somehow thought it could be a graphics issue so invested some time installing nvidia drivers properly. Also I wondered if it might be the lowlatency kernel I normally use because I do audio stuff, and switched to generic. But nothing helped. ThenI had the idea it could be a kernel/scheduler issue because the system wasn't always slow, but it appeared certain things kept hanging when other processed had a lot of cpu for a few seconds. So I got a recent mainline kernel, configured it with my last running config from 21.10 before the update, made the debs and installed them, and now can tell that a mainline kernel 5.17.7 with all the dkms modules that i had before which got compiled automatically at installation brings back a "normal" performance. I can browse the web, run multiple youtube vids at once, even in another browser, have thunderbird running, and a virtualbox machine open with another browser for some web app testing and everything runs fine and smooth, no lagging. Not sure yet what the real reason is - either the kernel version, or a patch in the ubuntu version, or the 22.04 kernel config so far, or some configuration made in 21.10 that isn't good with 22.04 and it's kernel anymore. I will go ahead tomorrow and see if I can build a vanilla kernel with the config from the ubuntu 22.04 kernel and "make oldconfig", then I will be able to tell if only the config is making the difference. Please let me know of there is anything I should test to further analyze this issue, or any ideas I can try to solve it without having to run a mainline manually installed kernel. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.30.33 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henning6198 F pulseaudio /dev/snd/controlC1: henning6198 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 14 23:02:38 2022 InstallationDate: Installed on 2020-04-12 (761 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QV00CEGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=/dev/mapper/vgubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET55W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861
[Kernel-packages] [Bug 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot
Note if someone wants to build a kernel with: https://lore.kernel.org/linux-pci/20220512202511.34197-2-hdego...@redhat.com/ This patch applies on top of the 3 patches from: https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/log/?h=pci/resource -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1878279 Title: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot Status in Linux: Confirmed Status in Ubuntu: Confirmed Status in linux-signed-hwe package in Ubuntu: In Progress Status in linux-signed-hwe package in Fedora: New Bug description: Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5 14IIL05 81YH' from first system start on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tilman 1607 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 21:22:22 2020 InstallationDate: Installed on 2020-05-12 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN23WW(V1.09) 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 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05: dmi.product.family: IdeaPad 5 14IIL05 dmi.product.name: 81YH dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05 dmi.product.version: IdeaPad 5 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1878279/+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 1931715] Re: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices"
Sorry that it is taking so long to fix this. There have been several attempts at fixing this upstream already, but all of them had to be reverted/dropped because they were causing issues on other laptop models. The latest attempt at fixing this is here: https://lore.kernel.org/linux-pci/20220512202511.34197-2-hdego...@redhat.com/ And this patch, or something close to it will hopefully go upstream soon. Perhaps one of the Ubuntu kernel devs can provide a test kernel with this patch for Ubuntu users with this problem to test? -- 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/1931715 Title: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices" Status in linux package in Ubuntu: Confirmed Bug description: Laptop model: Lenovo Ideapad S145 82DJ0001BR Manufacturer of the Touchpad: Elan, Synaptics When the symptom first appeared: At the time I installed Ubuntu on my notebook (dual-boot) - it works fine on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 11:58:39 2021 InstallationDate: Installed on 2021-06-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931715/+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 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot
Sorry that it is taking so long to fix this. There have been several attempts at fixing this upstream already, but all of them had to be reverted/dropped because they were causing issues on other laptop models. The latest attempt at fixing this is here: https://lore.kernel.org/linux-pci/20220512202511.34197-2-hdego...@redhat.com/ And this patch, or something close to it will hopefully go upstream soon. Perhaps one of the Ubuntu kernel devs can provide a test kernel with this patch for Ubuntu users with this problem to test? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1878279 Title: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot Status in Linux: Confirmed Status in Ubuntu: Confirmed Status in linux-signed-hwe package in Ubuntu: In Progress Status in linux-signed-hwe package in Fedora: New Bug description: Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5 14IIL05 81YH' from first system start on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tilman 1607 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 21:22:22 2020 InstallationDate: Installed on 2020-05-12 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN23WW(V1.09) 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 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05: dmi.product.family: IdeaPad 5 14IIL05 dmi.product.name: 81YH dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05 dmi.product.version: IdeaPad 5 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1878279/+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 1884232] Re: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N)
Sorry that it is taking so long to fix this. There have been several attempts at fixing this upstream already, but all of them had to be reverted/dropped because they were causing issues on other laptop models. The latest attempt at fixing this is here: https://lore.kernel.org/linux-pci/20220512202511.34197-2-hdego...@redhat.com/ And this patch, or something close to it will hopefully go upstream soon. Perhaps one of the Ubuntu kernel devs can provide a test kernel with this patch for Ubuntu users with this problem to test? -- 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/1884232 Title: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N) Status in linux package in Ubuntu: Confirmed Bug description: Touchpad is not working at all on ACER Spin 5 SP513-54N. According to https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29 I am creating this kernel bug issue. There are more issues, too, like touchscreen not working and Ubuntu not installable - see here if interrested https://askubuntu.com/questions/1251719/ I would like to run Ubuntu on this machine and I am willing to help with any debug or kernel tweaking... Please let me know. 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4195 F pulseaudio CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 10:44:58 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Spin SP513-54N ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2020 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.00 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.00 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.00 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.00 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+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 1921649] Re: 'Ideapad S145 Touchpad' not working at all. Not even detected after a fresh Ubuntu 20.10 install.
Sorry that it is taking so long to fix this. There have been several attempts at fixing this upstream already, but all of them had to be reverted/dropped because they were causing issues on other laptop models. The latest attempt at fixing this is here: https://lore.kernel.org/linux-pci/20220512202511.34197-2-hdego...@redhat.com/ And this patch, or something close to it will hopefully go upstream soon. Perhaps one of the Ubuntu kernel devs can provide a test kernel with this patch for Ubuntu users with this problem to test? -- 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/1921649 Title: 'Ideapad S145 Touchpad' not working at all. Not even detected after a fresh Ubuntu 20.10 install. Status in linux package in Ubuntu: Expired Bug description: Just installed Ubuntu 20.10 in a new Lenovo Ideapad S145 82DJBR and touchpad does not work. It's not detected as seen here: $ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Ideapad extra buttons id=11 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-48-generic 5.8.0-48.54 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: netto 1359 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 28 17:30:14 2021 InstallationDate: Installed on 2021-03-20 (7 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 003: ID 174f:1176 Syntek Integrated Camera Bus 001 Device 002: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL (B) [Dell Laser Mouse] Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 82DJ ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-48-generic root=UUID=8f45bc43-cd22-4cfa-83ee-4cb09fd58f0c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-48-generic N/A linux-backports-modules-5.8.0-48-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2020 dmi.bios.release: 1.48 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN48WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IIL dmi.ec.firmware.release: 1.48 dmi.modalias: dmi:bvnLENOVO:bvrDKCN48WW:bd07/22/2020:br1.48:efr1.48:svnLENOVO:pn82DJ:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 82DJ dmi.product.sku: LENOVO_MT_82DJ_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921649/+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 1932069] Re: Touchpad not working at all
Sorry that it is taking so long to fix this. There have been several attempts at fixing this upstream already, but all of them had to be reverted/dropped because they were causing issues on other laptop models. The latest attempt at fixing this is here: https://lore.kernel.org/linux-pci/20220512202511.34197-2-hdego...@redhat.com/ And this patch, or something close to it will hopefully go upstream soon. Perhaps one of the Ubuntu kernel devs can provide a test kernel with this patch for Ubuntu users with this problem to test? -- 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/1932069 Title: Touchpad not working at all Status in linux package in Ubuntu: Confirmed Bug description: Notebook Lenovo BS-145 15 HL ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cesar 1314 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 15 16:36:11 2021 InstallationDate: Installed on 2021-06-15 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:1176 Syntek Integrated Camera Bus 001 Device 005: ID 10c4:8105 Silicon Labs USB OPTICAL MOUSE Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 82HB ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-18-generic root=UUID=2ff10f98-8e1f-42ac-98b7-284459b8d285 ro quiet splash vt.handoff=7 RebootRequiredPkgs: gnome-shell RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo BS145-15IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82HB:pvrLenovoBS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoBS145-15IIL: dmi.product.family: BS145-15IIL dmi.product.name: 82HB dmi.product.sku: LENOVO_MT_82HB_BU_idea_FM_BS145-15IIL dmi.product.version: Lenovo BS145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932069/+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 1971209] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common
** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags added: package-conflict -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1971209 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.147-0ubuntu0.18.04.1 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: package nvidia-390 (not installed) failed to install/upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.15.0-176.185-generic 4.15.18 Uname: Linux 4.15.0-176-generic i686 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: i386 Date: Tue May 3 02:28:55 2022 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.147-0ubuntu0.18.04.1 InstallationDate: Installed on 2022-05-02 (0 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.14 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.147-0ubuntu0.18.04.1 UpgradeStatus: Upgraded to bionic on 2022-05-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1971209/+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 1954320] Re: Add privacy screen modules to the initrd
** Package changed: linux (Ubuntu) => initramfs-tools (Ubuntu) ** Changed in: initramfs-tools (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/1954320 Title: Add privacy screen modules to the initrd Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Starting with kernel 5.17 the kernel supports the builtin privacy screens built into the LCD panel of some new laptop models. This means that the drm drivers will now return -EPROBE_DEFER from their probe() method on models with a builtin privacy screen when the privacy screen provider driver has not been loaded yet. To avoid any regressions Ubuntu should modify its initrd generation tool to include privacy screen provider drivers in the initrd (at least on systems with a privacy screen), before 5.17 kernels start showing up in the Ubuntu repos. If this change is not made, then users using a graphical bootsplash (plymouth) will get an extra boot-delay of up to 8 seconds (DeviceTimeout in plymouthd.defaults) before plymouth will show and when using disk-encryption where the LUKS password is requested from the initrd, the system may fallback to text-mode after these 8 seconds. I've written a patch with the necessary changes for dracut, which might be useful as an example for how to deal with this, see: https://github.com/dracutdevs/dracut/pull/1666 ATM the only kms driver using privacy screens is the i915 driver and the only provider is the thinkpad_acpi driver. But both are likely to change (and change soon!), so the detection really should be made dynamic as has been done in the dracut patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1954320/+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 1954320] Re: Add privacy screen modules to the initrd
Note I've also filed a bug against initramfs-tools in Debian for this, see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001409 ** Bug watch added: Debian Bug tracker #1001409 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001409 -- 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/1954320 Title: Add privacy screen modules to the initrd Status in linux package in Ubuntu: New Bug description: Starting with kernel 5.17 the kernel supports the builtin privacy screens built into the LCD panel of some new laptop models. This means that the drm drivers will now return -EPROBE_DEFER from their probe() method on models with a builtin privacy screen when the privacy screen provider driver has not been loaded yet. To avoid any regressions Ubuntu should modify its initrd generation tool to include privacy screen provider drivers in the initrd (at least on systems with a privacy screen), before 5.17 kernels start showing up in the Ubuntu repos. If this change is not made, then users using a graphical bootsplash (plymouth) will get an extra boot-delay of up to 8 seconds (DeviceTimeout in plymouthd.defaults) before plymouth will show and when using disk-encryption where the LUKS password is requested from the initrd, the system may fallback to text-mode after these 8 seconds. I've written a patch with the necessary changes for dracut, which might be useful as an example for how to deal with this, see: https://github.com/dracutdevs/dracut/pull/1666 ATM the only kms driver using privacy screens is the i915 driver and the only provider is the thinkpad_acpi driver. But both are likely to change (and change soon!), so the detection really should be made dynamic as has been done in the dracut patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954320/+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 1954320] Re: Add privacy screen modules to the initrd
The component here should be initramfs-tools which I selected at the "Report a bug" page, but I got at that page from the link at: https://bugs.launchpad.net/ubuntu/+source/linux/ so I guess launchpad just decided to ignore my answer to "In what package did you find this bug?", because I came from the /ubuntu/+source/linux/ page ... -- 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/1954320 Title: Add privacy screen modules to the initrd Status in linux package in Ubuntu: New Bug description: Starting with kernel 5.17 the kernel supports the builtin privacy screens built into the LCD panel of some new laptop models. This means that the drm drivers will now return -EPROBE_DEFER from their probe() method on models with a builtin privacy screen when the privacy screen provider driver has not been loaded yet. To avoid any regressions Ubuntu should modify its initrd generation tool to include privacy screen provider drivers in the initrd (at least on systems with a privacy screen), before 5.17 kernels start showing up in the Ubuntu repos. If this change is not made, then users using a graphical bootsplash (plymouth) will get an extra boot-delay of up to 8 seconds (DeviceTimeout in plymouthd.defaults) before plymouth will show and when using disk-encryption where the LUKS password is requested from the initrd, the system may fallback to text-mode after these 8 seconds. I've written a patch with the necessary changes for dracut, which might be useful as an example for how to deal with this, see: https://github.com/dracutdevs/dracut/pull/1666 ATM the only kms driver using privacy screens is the i915 driver and the only provider is the thinkpad_acpi driver. But both are likely to change (and change soon!), so the detection really should be made dynamic as has been done in the dracut patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954320/+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 1954320] [NEW] Add privacy screen modules to the initrd
Public bug reported: Starting with kernel 5.17 the kernel supports the builtin privacy screens built into the LCD panel of some new laptop models. This means that the drm drivers will now return -EPROBE_DEFER from their probe() method on models with a builtin privacy screen when the privacy screen provider driver has not been loaded yet. To avoid any regressions Ubuntu should modify its initrd generation tool to include privacy screen provider drivers in the initrd (at least on systems with a privacy screen), before 5.17 kernels start showing up in the Ubuntu repos. If this change is not made, then users using a graphical bootsplash (plymouth) will get an extra boot-delay of up to 8 seconds (DeviceTimeout in plymouthd.defaults) before plymouth will show and when using disk-encryption where the LUKS password is requested from the initrd, the system may fallback to text-mode after these 8 seconds. I've written a patch with the necessary changes for dracut, which might be useful as an example for how to deal with this, see: https://github.com/dracutdevs/dracut/pull/1666 ATM the only kms driver using privacy screens is the i915 driver and the only provider is the thinkpad_acpi driver. But both are likely to change (and change soon!), so the detection really should be made dynamic as has been done in the dracut patch. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954320 Title: Add privacy screen modules to the initrd Status in linux package in Ubuntu: New Bug description: Starting with kernel 5.17 the kernel supports the builtin privacy screens built into the LCD panel of some new laptop models. This means that the drm drivers will now return -EPROBE_DEFER from their probe() method on models with a builtin privacy screen when the privacy screen provider driver has not been loaded yet. To avoid any regressions Ubuntu should modify its initrd generation tool to include privacy screen provider drivers in the initrd (at least on systems with a privacy screen), before 5.17 kernels start showing up in the Ubuntu repos. If this change is not made, then users using a graphical bootsplash (plymouth) will get an extra boot-delay of up to 8 seconds (DeviceTimeout in plymouthd.defaults) before plymouth will show and when using disk-encryption where the LUKS password is requested from the initrd, the system may fallback to text-mode after these 8 seconds. I've written a patch with the necessary changes for dracut, which might be useful as an example for how to deal with this, see: https://github.com/dracutdevs/dracut/pull/1666 ATM the only kms driver using privacy screens is the i915 driver and the only provider is the thinkpad_acpi driver. But both are likely to change (and change soon!), so the detection really should be made dynamic as has been done in the dracut patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954320/+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 1951634] Re: package iotop missing
Thanks for reporting. I was unable to reproduce this bug, iotop installed without any issues for me. I suspect that this and bug 1951578 might have some common root cause. Could you please attach the output from `apt policy iotop` to see if it knows about the package at all? Also could you check `software- properties-gtk` if you have at least main and universe archives enabled? ** Package changed: linux (Ubuntu) => iotop (Ubuntu) -- 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/1951634 Title: package iotop missing Status in iotop package in Ubuntu: Incomplete Bug description: Hello sudo apt full-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.3 LTS" iotop Command 'iotop' not found, but can be installed with: sudo apt install iotop sudo apt install iotop Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package iotop Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iotop/+bug/1951634/+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 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot
Kai-Heng, thank you for providing the test kernel. Folks, if you need to add pci=nocrs to your kernel-commandline to get your touchpad to work, please test this kernel: https://people.canonical.com/~khfeng/lp1878279/ With pci=no_e820 on the kernel commandline (replacing pci=nocrs). If the touchpad works this way, please provide DMI strings for your laptop, so that I can add a quirk to the kernel to automatically enable "pci=no_e820" on your laptop model. Run the following command *as normal user* to collect the DMI strings for your laptop: grep . /sys/class/dmi/id/* 2> /dev/null And copy and paste the output here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1878279 Title: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot Status in Linux: Confirmed Status in Ubuntu: Confirmed Status in linux-signed-hwe package in Ubuntu: In Progress Status in linux-signed-hwe package in Fedora: New Bug description: Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5 14IIL05 81YH' from first system start on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tilman 1607 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 21:22:22 2020 InstallationDate: Installed on 2020-05-12 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN23WW(V1.09) 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 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05: dmi.product.family: IdeaPad 5 14IIL05 dmi.product.name: 81YH dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05 dmi.product.version: IdeaPad 5 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1878279/+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 1946109] Re: touchpad is not wokring at all, does not get recognized
*** This bug is a duplicate of bug 1946108 *** https://bugs.launchpad.net/bugs/1946108 ** This bug has been marked a duplicate of bug 1946108 touchpad is not wokring at all, does not get recognized -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1946109 Title: touchpad is not wokring at all, does not get recognized Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: Touchpad does not show after: cat /proc/bus/input/devices > ~/devices All drivers are up to date. Laptop is a: Fujitsu Lifebook U-7510 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 5 10:04:33 2021 InstallationDate: Installed on 2021-09-22 (13 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1946109/+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 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot
Please test a kernel build with this patch, combined with adding "pci=no_e820" added to the kernel commandline. See comment 133 for more details. ** Patch added: "[PATCH] x86/PCI: Add pci=no_e820 cmdline option to ignore E820 reservations for bridge windows" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1878279/+attachment/5530683/+files/0001-x86-PCI-Add-pci-no_e820-cmdline-option-to-ignore-E82.patch ** Patch removed: "[PATCH] PCI/ACPI: Make acpi_pci_root_validate_resources() reject IOMEM resources which start at address 0" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1878279/+attachment/5504784/+files/0001-PCI-ACPI-Make-acpi_pci_root_validate_resources-rejec.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1878279 Title: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot Status in Linux: Confirmed Status in Ubuntu: Confirmed Status in linux-signed-hwe package in Ubuntu: In Progress Status in linux-signed-hwe package in Fedora: New Bug description: Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5 14IIL05 81YH' from first system start on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tilman 1607 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 21:22:22 2020 InstallationDate: Installed on 2020-05-12 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN23WW(V1.09) 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 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05: dmi.product.family: IdeaPad 5 14IIL05 dmi.product.name: 81YH dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05 dmi.product.version: IdeaPad 5 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1878279/+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 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot
This is a follow-up to comment #123 Sorry for the long silence on this bug. I was hoping one of the upstream pci-subsys devs would help out with this... Since that did not happen I've been looking into fixing this myself now. I've come up with a solution which still involves a kernel cmdline option for now, but this one is a much smaller hammer (almost a scalpel) and once it is confirmed that this works I can enable this by default through a DMI quirk. I also hope that this option will not cause the stability issues seen when using pci=nocrs and that it will remove the need to specify i8042.nopnp=1 . I'll attach my patch here and then hopefully one of the Ubuntu devs can build a test-kernel for people who need pci=nocrs to test. Alternatively you can build your own kernel with this patch added, see the Ubuntu docs for how to do this. Once you have a kernel with this patch, remove pci=nocrs and i8042.nopnp=1 from the kernel-commandline and instead add only "pci=no_e820". If this helps please provide DMI strings for your laptop, so that I can add a quirk to the kernel to automatically enable "pci=no_e820" on your laptop model. Run the following command *as normal user* to collect the DMI strings for your laptop: grep . /sys/class/dmi/id/* 2> /dev/null And copy and paste the output here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1878279 Title: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot Status in Linux: Confirmed Status in Ubuntu: Confirmed Status in linux-signed-hwe package in Ubuntu: In Progress Status in linux-signed-hwe package in Fedora: New Bug description: Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5 14IIL05 81YH' from first system start on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tilman 1607 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 21:22:22 2020 InstallationDate: Installed on 2020-05-12 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN23WW(V1.09) 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 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05: dmi.product.family: IdeaPad 5 14IIL05 dmi.product.name: 81YH dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05 dmi.product.version: IdeaPad 5 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1878279/+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 1894017] Re: Keyboard not working
I just typed a long email in reply to someone asking about the keyboard not working by email. The contents of that email are likely useful for other people who are still experiencing the keyboard not working too, so I've copy and pasted my entire reply below. If you still need help with this please follow the provided debug instructions and provide the requested info. ### First of all lets see if we can find the root cause. Bug 1894017 is about the keyboard events being discarded in userspace, because userspace thinks the device is folded in tablet mode with the keyboard behind the display (and any key-presses are thus done accidentally). Please install evemu and then run: sudo evemu-record This will give you a list of available input devices. The problems reported in bug #1894017 are caused by a false-positive reporting of SW_TABLET_MODE with a value of 1. By one of the following input-devices: "Intel HID events" "Intel HID switches" "Intel Virtual Buttons" "Intel Virtual Switches" Or something like this, you can select a device by typing the number of its /dev/input/event# node. After selecting a device evemu-record will print which events the device can report. If it can report SW_TABLET_MODE then the output will also contain the current value of SW_TABLET_MODE, if this is 1 then that is the cause. (press CTRL+c to exit evemu-record) But you write "seems to stop responding at random" where as with the SW_TABLET_MODE problem I would expect it to simply not work at all (with certain kernel versions). So you may very well have a different problem then the one described in launchpad issue 1894017. What you can also try is running "sudo evemu-record" and then selecting the "AT Translated Set 2 keyboard" keyboard. After this if you type some keys on the keyboard they should show up in evemu-record as key-presses. If this works, then try doing it again (over e.g. ssh, or with an external usb kbd) when the keyboard has stopped responding. I suspect that you will find that at this point evemu-record will also no longer report keys, which means that the problem is happening at a lower level. I suspect that you will find that the problem indeed is happening at a lower-level and that you need something like this: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=addab6febc42ed94e4eee1abbe486150e4f8b9e9 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e5b1032a656e9aa4c7a4df77cb9156a2a651a5f9 In order to determine what is necessary to fix things I need a number of things: 1. output of: "grep . /sys/class/dmi/id/* 2> /dev/null" run from a terminal 2. Install acpica-tools and then run: "sudo acpidump -o acpidump.txt" and then attach the generated acpidump.txt file to your next email 3. It would help a lot if we can go from "seems to stop responding at random" to "stops responding when I do a, followed by b..." some ideas here are: 3.1 perhaps it stops responding after folding the display past 180 degrees (so a little beyond it lyinf fully flat on the table) and then back again? 3.2 perhaps it stops responding after folding the display all the way back so that the device is fully in tablet mode; and then back to laptop mode again ? 3.3 perhaps it stops responding after a suspend/resume? Regards, Hans -- 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/1894017 Title: Keyboard not working Status in linux package in Ubuntu: Fix Released Bug description: The laptop keyboard doesn't work at login or in the de. If I ctrl+alt+F3 from an external usb keyboard to a terminal the laptop keyboard works. An external usb keyboard works everywhere. The laptop's keyboard does work everywhere with the previous kernel 5.4.0.42. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55 Uname: Linux 5.4.0-45-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Sep 3 03:09:49 2020 InstallationDate: Installed on 2019-08-07 (392 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Hewlett-Packard HP Pavilion 11 x360 PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency root=UUID=6035c42c-766d-44fd-b45c-6cdf9c74e0b5 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-lowlatency N/A linux-backports-modules-5.4.0-45-lowlatency N/A linux-firmware 1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-06 (149 days ago) dmi.bios.date: 03
[Kernel-packages] [Bug 1935679] Re: crash: build failure on RISC-V
Possibly fixes the issue reported in bug 1931432 as wel... -- 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/1935679 Title: crash: build failure on RISC-V Status in crash package in Ubuntu: New Bug description: version: 7.3.0-1ubuntu1 Building crash for RISC-V fails with a segfault. This segfault is due to missing support for architecture RISC-V in file configure.c. configure is used to update Makefile. It replaces "TARGET " by "(NULL)". A patch is at https://github.com/xypron/crash/commit/2391175c7936a3d873b7b7f1b6c6cae2f4c166b8 Current upstream crash uses an version 7.6 for gdb which does not support RISC-V. Patch series https://listman.redhat.com/archives/crash- utility/2021-March/msg00078.html provides an update to gdb 10.1. https://github.com/YustasSwamp/crash/tree/crash-gdb10.2-devel-temp provides patches for using gdb 10.2. For building we need command makeinfo which is provided by missing package texinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1935679/+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 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot
I've been working with a Fedora reporter to try and solve the case where pci=nocrs helps to get a working touchpad, see: https://bugzilla.redhat.com/show_bug.cgi?id=1868899 Thanks to the latest set of logs attached there, I now am finally starting to understand what is going on here. Your BIOS claims that any memory between 0x4bc5-0xcfff is reserved: [0.00] BIOS-e820: [mem 0x4bc5-0xcfff] reserved But then continuous with placing the iomem window for PCI devices inside that reserved range: [0.609988] pci_bus :00: root bus resource [mem 0x6540-0xbfff window] This confuses the kernel and makes it unable to assign PCI iomem to devices which have not already been assigned iomem by the BIOS, like the I2C-controller used for the touchpad. If you are interested in / curious about the low level details, I'm discussing this with the kernel PCI developers (including figuring out how to deal with this) here: https://lore.kernel.org/linux-pci/7d80f639-0768-850b-5313-3bdedf0a5...@redhat.com/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1878279 Title: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot Status in Linux: Confirmed Status in Ubuntu: Confirmed Status in linux-signed-hwe package in Ubuntu: In Progress Status in linux-signed-hwe package in Fedora: New Bug description: Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5 14IIL05 81YH' from first system start on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tilman 1607 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 21:22:22 2020 InstallationDate: Installed on 2020-05-12 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN23WW(V1.09) 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 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05: dmi.product.family: IdeaPad 5 14IIL05 dmi.product.name: 81YH dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05 dmi.product.version: IdeaPad 5 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1878279/+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 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot
Ratul, the patch which I attached won 't help you. The patch is basically no good, because the problem is not what I thought it was. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1878279 Title: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot Status in Linux: Confirmed Status in Ubuntu: Confirmed Status in linux-signed-hwe package in Ubuntu: In Progress Status in linux-signed-hwe package in Fedora: New Bug description: Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5 14IIL05 81YH' from first system start on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tilman 1607 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 21:22:22 2020 InstallationDate: Installed on 2020-05-12 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN23WW(V1.09) 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 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05: dmi.product.family: IdeaPad 5 14IIL05 dmi.product.name: 81YH dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05 dmi.product.version: IdeaPad 5 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1878279/+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 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot
Bernhard, no in the mean time I've learned that my patch is no good. I'm currently debugging this with a Fedora user who also needs pci=nocrs to get the touchpad to work: https://bugzilla.redhat.com/show_bug.cgi?id=1868899 But this is going quite slow because the cycle between me providing the user with a kernel with some extra debugging logging added; and me getting a dmesg output for that test kernel back is quite slow. ** Bug watch added: Red Hat Bugzilla #1868899 https://bugzilla.redhat.com/show_bug.cgi?id=1868899 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1878279 Title: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot Status in Linux: Confirmed Status in Ubuntu: Confirmed Status in linux-signed-hwe package in Ubuntu: In Progress Status in linux-signed-hwe package in Fedora: New Bug description: Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5 14IIL05 81YH' from first system start on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tilman 1607 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 21:22:22 2020 InstallationDate: Installed on 2020-05-12 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN23WW(V1.09) 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 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05: dmi.product.family: IdeaPad 5 14IIL05 dmi.product.name: 81YH dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05 dmi.product.version: IdeaPad 5 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1878279/+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 1933761] Re: Brightness hotkeys(Fn+F5 for decrease and Fn+F6 for Increase) are not working on Ubuntu 20.04. Hardware Lenovo Ideapad-5-15ITL05
*** This bug is a duplicate of bug 1933762 *** https://bugs.launchpad.net/bugs/1933762 ** This bug has been marked a duplicate of bug 1933762 Brightness hotkeys(Fn+F5 for decrease and Fn+F6 for Increase) are not working on Ubuntu 20.04. Hardware Lenovo Ideapad-5-15ITL05 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1933761 Title: Brightness hotkeys(Fn+F5 for decrease and Fn+F6 for Increase) are not working on Ubuntu 20.04. Hardware Lenovo Ideapad-5-15ITL05 Status in linux-oem-5.10 package in Ubuntu: New Bug description: I used the command "watch -n1 cat /proc/interrupts". But when i pressed the brightness hot keys id didn't increased the interruptions. I also used the "acpi_listen" at that time it didn't feedback any output when i pressed the brightness hotkeys. Again I used "sudo showkey -s" it also didn't feedback any output. But it's working on windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1933761/+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 1933762] Re: Brightness hotkeys(Fn+F5 for decrease and Fn+F6 for Increase) are not working on Ubuntu 20.04. Hardware Lenovo Ideapad-5-15ITL05
** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1933762 Title: Brightness hotkeys(Fn+F5 for decrease and Fn+F6 for Increase) are not working on Ubuntu 20.04. Hardware Lenovo Ideapad-5-15ITL05 Status in linux-oem-5.10 package in Ubuntu: New Status in linux-signed-oem-5.10 package in Ubuntu: New Bug description: I used the command "watch -n1 cat /proc/interrupts". But when i pressed the brightness hot keys id didn't increased the interruptions. I also used the "acpi_listen" at that time it didn't feedback any output when i pressed the brightness hotkeys. Again I used "sudo showkey -s" it also didn't feedback any output. But it was working on windows 10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.10.0-1034-oem 5.10.0-1034.35 ProcVersionSignature: Ubuntu 5.10.0-1034.35-oem 5.10.41 Uname: Linux 5.10.0-1034-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 27 19:30:42 2021 InstallationDate: Installed on 2021-06-27 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-oem-5.10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1933762/+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 1931431] Re: crash FTBFS on riscv64
*** This bug is a duplicate of bug 1931432 *** https://bugs.launchpad.net/bugs/1931432 ** This bug has been marked a duplicate of bug 1931432 crash FTBFS on riscv64 -- 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/1931431 Title: crash FTBFS on riscv64 Status in crash package in Ubuntu: New Bug description: Crash fails to build from source on riscv at least for Focal and Groovy, later releases may also be affected but I haven't confirm it. Examples of failed builds : Groovy : https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.10.1/+build/21630864 Focal : https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.04.1/+build/21630885 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931431/+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 1931432] Re: crash FTBFS on riscv64
Seems to fail with a seg fault on the version in 21.04, https://bugs.launchpad.net/ubuntu/+source/crash/7.2.9-2ubuntu2 . Not rebuilt on Impish, but would assume the same might happen there. ** Tags added: focal ftbfs groovy hirsute impish -- 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/1931432 Title: crash FTBFS on riscv64 Status in crash package in Ubuntu: Confirmed Status in crash source package in Focal: Confirmed Status in crash source package in Groovy: Confirmed Bug description: Crash fails to build from source on riscv at least for Focal and Groovy, later releases may also be affected but I haven't confirm it. Examples of failed builds : Groovy : https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.10.1/+build/21630864 Focal : https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.04.1/+build/21630885 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931432/+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 1930868] Re: Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firm
** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- 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/1930868 Title: Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 Status in firmware-sof package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Bug description: (Reading database ... 220533 files and directories currently installed.) Preparing to unpack .../firmware-sof-signed_1.6.1-2_all.deb ... Unpacking firmware-sof-signed (1.6.1-2) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 Errors were encountered while processing: /var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb Is there a work around? ProblemType: Package DistroRelease: Ubuntu 21.04 Package: firmware-sof-signed (not installed) ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 AptOrdering: firmware-sof-signed:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jun 4 17:22:54 2021 DpkgTerminalLog: Preparing to unpack .../firmware-sof-signed_1.6.1-2_all.deb ... Unpacking firmware-sof-signed (1.6.1-2) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 DuplicateSignature: package:firmware-sof-signed:(not installed) Unpacking firmware-sof-signed (1.6.1-2) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 ErrorMessage: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 InstallationDate: Installed on 2021-06-02 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: firmware-sof Title: package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1930868/+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 1923564] Re: BlueZ 5.58 release
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1923564 Title: BlueZ 5.58 release Status in bluez package in Ubuntu: New Bug description: BlueZ 5.58 has been released. We should look at it for the 21.10 cycle... http://www.bluez.org/release-of-bluez-5-58-and-5-57/ https://mirrors.edge.kernel.org/pub/linux/bluetooth/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1923564/+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 1894017] Re: Keyboard not working
@kaihengfeng, can you perhaps build a 5.9.xx kernel with: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d823346876a970522ff9e4d2b323c9b734dcc4de added for @dacto from comment 25 to test ? His device gets intel-vbtn SW_TABLET_MODE support enabled based on the chassis-type, yet it seems to always report SW_TABLET_MODE=1, I want to know if the mentioned commit fixes this. This commit was a workaround introduced before we switched to an allow list (which includes certain chassis-types). This workaround was reverted after switching to the allow list, but since @dacto is still seeing this with 5.9.10 it looks like we may need the workaround even with the new allow-list approach. @dacto, 2 questions: 1. What happens with 5.9.10 if you fold the 2-in-1 into tablet mode and then back into laptop/clamshell mode again, does that fix the kbd and touchpad not working ? 2. Can you provide an acpidump of your device? Run: sudo acpidump -o acpidump.HP-Convertible-x360-11-ab0XX And then attach the generated acpidump.HP-Convertible-x360-11-ab0XX file here, or send it directly to me: hdego...@redhat.com . ### So looking closer at the difference between 5.4.75 and 5.9.10, 5.9.10 has: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=21d64817c72470ed69483f59279ce557c0658826 Which 5.4.75 does not have, so this strongly suggests that despite switching to the allow list we still need the workaround for some HP models and it should be re-added (undoing the revert / undoing the dropping of the workaround). I can take care of getting this re-added but first I would like to see some confirmation that this is indeed the problem. Ideally you (@dacto) would test a 5.9.10 (or .11 or .12) kernel with the patch added, but I can also confirm that this patch needs to be re-added by looking at an acpidump. -- 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/1894017 Title: Keyboard not working Status in linux package in Ubuntu: Confirmed Bug description: The laptop keyboard doesn't work at login or in the de. If I ctrl+alt+F3 from an external usb keyboard to a terminal the laptop keyboard works. An external usb keyboard works everywhere. The laptop's keyboard does work everywhere with the previous kernel 5.4.0.42. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55 Uname: Linux 5.4.0-45-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Sep 3 03:09:49 2020 InstallationDate: Installed on 2019-08-07 (392 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Hewlett-Packard HP Pavilion 11 x360 PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency root=UUID=6035c42c-766d-44fd-b45c-6cdf9c74e0b5 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-lowlatency N/A linux-backports-modules-5.4.0-45-lowlatency N/A linux-firmware 1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-06 (149 days ago) dmi.bios.date: 03/13/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2209 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.30:bd03/13/2018:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097710405F00010420180:rvnHewlett-Packard:rn2209:rvr57.57:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN dmi.product.name: HP Pavilion 11 x360 PC dmi.product.sku: M0B61EA#ACQ dmi.product.version: 097710405F00010420180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894017/+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 1894017] Re: Keyboard not working
chassis_type 31 is "Convertible", so we expect the intel-vbtn
SW_TABLET_MODE reporting to work there.
There was one other HP model which had a bit of a weird issue, this was
fixed by:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d823346876a970522ff9e4d2b323c9b734dcc4de
But that workaround got dropped when we switched to ignoring
SW_TABLET_MODE on all devices where the chassis_type is not 31 or 32,
since the model which needed that fix ("HP Pavilion 11 x360") uses a
chassis_type of 10, so that workaround was no longer needed.
So now it seems that we should not have dropped the workaround as
possibly more HP models need it. If you can build your own 5.9.10 kernel
with the linked workaround applied, and test it that would be great.
There should be docs somewhere on how to build an ubuntu kernel with
patches applied yourself. If you do not feel up to doing this yourself,
then please say so, then one of the Ubuntu devs should be able to
provide a test kernel with the patch added for 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/1894017
Title:
Keyboard not working
Status in linux package in Ubuntu:
Confirmed
Bug description:
The laptop keyboard doesn't work at login or in the de. If I
ctrl+alt+F3 from an external usb keyboard to a terminal the laptop
keyboard works. An external usb keyboard works everywhere. The
laptop's keyboard does work everywhere with the previous kernel
5.4.0.42.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49
ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55
Uname: Linux 5.4.0-45-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Thu Sep 3 03:09:49 2020
InstallationDate: Installed on 2019-08-07 (392 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: Hewlett-Packard HP Pavilion 11 x360 PC
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency
root=UUID=6035c42c-766d-44fd-b45c-6cdf9c74e0b5 ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-5.4.0-45-lowlatency N/A
linux-backports-modules-5.4.0-45-lowlatency N/A
linux-firmware 1.187.3
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-04-06 (149 days ago)
dmi.bios.date: 03/13/2018
dmi.bios.vendor: Insyde
dmi.bios.version: F.30
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2209
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 57.57
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.30:bd03/13/2018:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097710405F00010420180:rvnHewlett-Packard:rn2209:rvr57.57:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN
dmi.product.name: HP Pavilion 11 x360 PC
dmi.product.sku: M0B61EA#ACQ
dmi.product.version: 097710405F00010420180
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894017/+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 1904295] Re: package linux-firmware 1.157.23 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1904294 *** https://bugs.launchpad.net/bugs/1904294 ** This bug has been marked a duplicate of bug 1904294 package linux-firmware 1.157.23 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- 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/1904295 Title: package linux-firmware 1.157.23 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in linux-firmware package in Ubuntu: New Bug description: I have this update on updating my Ubuntu version from 14.04 to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.23 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.27 Architecture: amd64 Date: Sat Nov 14 22:08:05 2020 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2020-08-12 (94 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SourcePackage: linux-firmware Title: package linux-firmware 1.157.23 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2020-11-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1904295/+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 1894017] Re: Keyboard not working
@burritojohn, if you are seeing this on an Asus device then you are hit by a different variant of what is in essence the same bug. The Asus case is fixed by this upstream commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1797d588af15174d4a4e7159dac8c800538e4f8c Which has also been cherry-picked into the 5.8.y stable series (it is there since the v5.8.15 release). So to fix this for you (and many many other Asus users!) the Ubuntu kernels should pickup the upstream fix for this. -- 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/1894017 Title: Keyboard not working Status in linux package in Ubuntu: Confirmed Bug description: The laptop keyboard doesn't work at login or in the de. If I ctrl+alt+F3 from an external usb keyboard to a terminal the laptop keyboard works. An external usb keyboard works everywhere. The laptop's keyboard does work everywhere with the previous kernel 5.4.0.42. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55 Uname: Linux 5.4.0-45-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Sep 3 03:09:49 2020 InstallationDate: Installed on 2019-08-07 (392 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Hewlett-Packard HP Pavilion 11 x360 PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency root=UUID=6035c42c-766d-44fd-b45c-6cdf9c74e0b5 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-lowlatency N/A linux-backports-modules-5.4.0-45-lowlatency N/A linux-firmware 1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-06 (149 days ago) dmi.bios.date: 03/13/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2209 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.30:bd03/13/2018:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097710405F00010420180:rvnHewlett-Packard:rn2209:rvr57.57:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN dmi.product.name: HP Pavilion 11 x360 PC dmi.product.sku: M0B61EA#ACQ dmi.product.version: 097710405F00010420180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894017/+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 1894017] Re: Keyboard not working
This has been fixed in the upstream 5.4.71 stable series release, so as soon as the Ubuntu kernels pick up the fixes from that release then this should be resolved. -- 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/1894017 Title: Keyboard not working Status in linux package in Ubuntu: Confirmed Bug description: The laptop keyboard doesn't work at login or in the de. If I ctrl+alt+F3 from an external usb keyboard to a terminal the laptop keyboard works. An external usb keyboard works everywhere. The laptop's keyboard does work everywhere with the previous kernel 5.4.0.42. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55 Uname: Linux 5.4.0-45-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Sep 3 03:09:49 2020 InstallationDate: Installed on 2019-08-07 (392 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Hewlett-Packard HP Pavilion 11 x360 PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency root=UUID=6035c42c-766d-44fd-b45c-6cdf9c74e0b5 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-lowlatency N/A linux-backports-modules-5.4.0-45-lowlatency N/A linux-firmware 1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-06 (149 days ago) dmi.bios.date: 03/13/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2209 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.30:bd03/13/2018:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097710405F00010420180:rvnHewlett-Packard:rn2209:rvr57.57:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN dmi.product.name: HP Pavilion 11 x360 PC dmi.product.sku: M0B61EA#ACQ dmi.product.version: 097710405F00010420180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894017/+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 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
@tjaalton, note the fix which I originally wrote for this causes regressions on some devices, a follow up fix is necessary, see: https://lore.kernel.org/linux-i2c/20201014144158.18036-1-hdego...@redhat.com/ https://lore.kernel.org/linux-i2c/20201014144158.18036-2-hdego...@redhat.com/ -- 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/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Released Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: == SRU Justification == [Impact] Touchpad on sereval Lenovo ThinkBook doesn't work. [Fix] Maintain method calling ordering by calling _REG before issuing _STA, as ACPI spec suggested, for I2C ACPI devices. [Test] Positive feedback from several users. [Regression Potential] If there are some systems that rely on the wrong calling ordering then there's a regression risk. However it's rather unlikely. == Original Bug Report == This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+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 1899522] Re: package libnvidia-common-450-server 450.51.06-0ubuntu0.20.04.2 failed to install/upgrade: trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.80.
The underlying problem is that the file '/usr/share/nvidia/nvidia- application-profiles-450.80.02-key-documentation' is present in both packages, so they run into a conflict when attempting to install both. ** Also affects: nvidia-graphics-drivers-450 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450-server in Ubuntu. https://bugs.launchpad.net/bugs/1899522 Title: package libnvidia-common-450-server 450.51.06-0ubuntu0.20.04.2 failed to install/upgrade: trying to overwrite '/usr/share/nvidia/nvidia- application-profiles-450.80.02-key-documentation', which is also in package libnvidia-common-450 450.80.02-0ubuntu0.20.04.2 Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-450-server package in Ubuntu: Confirmed Bug description: During sudo apt-get upgrade, there was an error while this package was installing. On restarting my computer, the resolution was set to 800*600 and my gpu (nvidia 1060 6gb) wasn't recognized. Uninstalling the driver and reverting to the nouveu drivers fixed the resolution issue and reinstalling the nvidia-450 drivers via software & updates allowed for everything to go back to normal. Steps to reproduce: On a machine with an nvidia 1060 6gb, run sudo apt-get update followed by sudo apt-get upgrade, this should result in an error during dpkg. Restart the computer to see the driver issue with display resolution and gpu not labelled correctly. Steps to resolve for the time being: Uninstall and reinstall nvidia-450 via software & updates, restart computer. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-common-450-server 450.51.06-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 12 18:12:58 2020 Dependencies: DuplicateSignature: package:libnvidia-common-450-server:450.51.06-0ubuntu0.20.04.2 Unpacking libnvidia-common-450-server (450.80.02-0ubuntu0.20.04.3) over (450.51.06-0ubuntu0.20.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-OfgM3I/33-libnvidia-common-450-server_450.80.02-0ubuntu0.20.04.3_all.deb (--unpack): trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.80.02-key-documentation', which is also in package libnvidia-common-450 450.80.02-0ubuntu0.20.04.2 ErrorMessage: trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.80.02-key-documentation', which is also in package libnvidia-common-450 450.80.02-0ubuntu0.20.04.2 InstallationDate: Installed on 2020-10-01 (11 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-450-server Title: package libnvidia-common-450-server 450.51.06-0ubuntu0.20.04.2 failed to install/upgrade: trying to overwrite '/usr/share/nvidia/nvidia-application-profiles-450.80.02-key-documentation', which is also in package libnvidia-common-450 450.80.02-0ubuntu0.20.04.2 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-450/+bug/1899522/+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 1894017] Re: Keyboard not working
I just got an email from gkh that both patches have also been added to the various stable kernel series, including 5.4.x and 5.8.y, so they should show up in the next stable series release for those kernels. Thus if the Ubuntu kernel follows the stable series then this will get fixed through that. -- 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/1894017 Title: Keyboard not working Status in linux package in Ubuntu: Confirmed Bug description: The laptop keyboard doesn't work at login or in the de. If I ctrl+alt+F3 from an external usb keyboard to a terminal the laptop keyboard works. An external usb keyboard works everywhere. The laptop's keyboard does work everywhere with the previous kernel 5.4.0.42. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55 Uname: Linux 5.4.0-45-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Sep 3 03:09:49 2020 InstallationDate: Installed on 2019-08-07 (392 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Hewlett-Packard HP Pavilion 11 x360 PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency root=UUID=6035c42c-766d-44fd-b45c-6cdf9c74e0b5 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-lowlatency N/A linux-backports-modules-5.4.0-45-lowlatency N/A linux-firmware 1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-06 (149 days ago) dmi.bios.date: 03/13/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2209 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.30:bd03/13/2018:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097710405F00010420180:rvnHewlett-Packard:rn2209:rvr57.57:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN dmi.product.name: HP Pavilion 11 x360 PC dmi.product.sku: M0B61EA#ACQ dmi.product.version: 097710405F00010420180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894017/+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 1894017] Re: Keyboard not working
@handyboy, my fix for this has been merged by Linus for inclusion into 5.9. If one of the Ubuntu devs can add the 2 mentioned fixes to the next 20.04 kernel build then this issue should be resolved/fixed. -- 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/1894017 Title: Keyboard not working Status in linux package in Ubuntu: Confirmed Bug description: The laptop keyboard doesn't work at login or in the de. If I ctrl+alt+F3 from an external usb keyboard to a terminal the laptop keyboard works. An external usb keyboard works everywhere. The laptop's keyboard does work everywhere with the previous kernel 5.4.0.42. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55 Uname: Linux 5.4.0-45-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Sep 3 03:09:49 2020 InstallationDate: Installed on 2019-08-07 (392 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Hewlett-Packard HP Pavilion 11 x360 PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency root=UUID=6035c42c-766d-44fd-b45c-6cdf9c74e0b5 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-lowlatency N/A linux-backports-modules-5.4.0-45-lowlatency N/A linux-firmware 1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-06 (149 days ago) dmi.bios.date: 03/13/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2209 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.30:bd03/13/2018:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097710405F00010420180:rvnHewlett-Packard:rn2209:rvr57.57:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN dmi.product.name: HP Pavilion 11 x360 PC dmi.product.sku: M0B61EA#ACQ dmi.product.version: 097710405F00010420180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894017/+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 1894017] Re: Keyboard not working
For everyone who is seeing this issue with the intel-vbtn driver, if you do: cat /sys/class/dmi/id/chassis_type On your laptop, and the output is NOT "31" or "32" then the fix, which I linked above, should work for you. If the output actually is "31" or "32 (which I do not expect), then please let me know, because then we need a different fix. -- 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/1894017 Title: Keyboard not working Status in linux package in Ubuntu: Confirmed Bug description: The laptop keyboard doesn't work at login or in the de. If I ctrl+alt+F3 from an external usb keyboard to a terminal the laptop keyboard works. An external usb keyboard works everywhere. The laptop's keyboard does work everywhere with the previous kernel 5.4.0.42. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55 Uname: Linux 5.4.0-45-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Sep 3 03:09:49 2020 InstallationDate: Installed on 2019-08-07 (392 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Hewlett-Packard HP Pavilion 11 x360 PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency root=UUID=6035c42c-766d-44fd-b45c-6cdf9c74e0b5 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-lowlatency N/A linux-backports-modules-5.4.0-45-lowlatency N/A linux-firmware 1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-06 (149 days ago) dmi.bios.date: 03/13/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2209 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.30:bd03/13/2018:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097710405F00010420180:rvnHewlett-Packard:rn2209:rvr57.57:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN dmi.product.name: HP Pavilion 11 x360 PC dmi.product.sku: M0B61EA#ACQ dmi.product.version: 097710405F00010420180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894017/+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 1894017] Re: Keyboard not working
This should be fixed by this upstream commit, which landed in Linus' tree a couple of hours ago: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/platform/x86?id=8169bd3e6e193497cab781acddcff8fde5d0c416 Note for the Ubuntu kernel devs: a similar bug was introduced in 5.8 in the asus-nb-wmi code, so when fixing this you really should also pick-up this fix: https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform- drivers-x86.git/commit/?h=fixes=1797d588af15174d4a4e7159dac8c800538e4f8c This one will hopefully be merged by Linus real soon (I have send out a pull-req for it to Linus). -- 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/1894017 Title: Keyboard not working Status in linux package in Ubuntu: Confirmed Bug description: The laptop keyboard doesn't work at login or in the de. If I ctrl+alt+F3 from an external usb keyboard to a terminal the laptop keyboard works. An external usb keyboard works everywhere. The laptop's keyboard does work everywhere with the previous kernel 5.4.0.42. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55 Uname: Linux 5.4.0-45-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Sep 3 03:09:49 2020 InstallationDate: Installed on 2019-08-07 (392 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Hewlett-Packard HP Pavilion 11 x360 PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency root=UUID=6035c42c-766d-44fd-b45c-6cdf9c74e0b5 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-lowlatency N/A linux-backports-modules-5.4.0-45-lowlatency N/A linux-firmware 1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-06 (149 days ago) dmi.bios.date: 03/13/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2209 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.30:bd03/13/2018:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097710405F00010420180:rvnHewlett-Packard:rn2209:rvr57.57:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN dmi.product.name: HP Pavilion 11 x360 PC dmi.product.sku: M0B61EA#ACQ dmi.product.version: 097710405F00010420180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894017/+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 1897389] [NEW] Touchpad not detected in Lenovo Thinkbook
Public bug reported: hans@hans-Lenovo-ThinkBook-14-IIL:~$ cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=275d Product=0ba6 Version=0111 N: Name="USB OPTICAL MOUSE " P: Phys=usb-:00:14.0-3/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/0003:275D:0BA6.0001/input/input4 U: Uniq= H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=903 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input5 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0003 Vendor=5986 Product=2130 Version=5609 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:00:14.0-6/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-6/3-6:1.0/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input7 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=4 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: hans 1750 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 26 16:23:26 2020 InstallationDate: Installed on 2020-09-26 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20SL ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=6b85afff-021d-4aa5-9738-5c8720860630 ro recovery nomodeset 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: 04/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DJCN17WW dmi.board.name: LVAC/LVAD dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 14-IIL dmi.modalias: dmi:bvnLENOVO:bvrDJCN17WW:bd04/15/2020:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL: dmi.product.family: Thinkbook 14-IIL dmi.product.name: 20SL dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL dmi.product.version: Lenovo ThinkBook 14-IIL dmi.sys.vendor: LENOVO ** Affects: 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 linux in Ubuntu. https://bugs.launchpad.net/bugs/1897389 Title: Touchpad not detected in Lenovo Thinkbook Status in linux package in Ubuntu: New Bug description: hans@hans-Lenovo-ThinkBook-14-IIL:~$ cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version=
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Gaurav, did you reboot into the patched kernel? And what is the output of "uname -r" in a terminal (after rebooting), does that show that you are running the patched kernel now? -- 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/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in linux-oem-5.6 source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: == SRU Justification == [Impact] Touchpad on sereval Lenovo ThinkBook doesn't work. [Fix] Maintain method calling ordering by calling _REG before issuing _STA, as ACPI spec suggested, for I2C ACPI devices. [Test] Positive feedback from several users. [Regression Potential] If there are some systems that rely on the wrong calling ordering then there's a regression risk. However it's rather unlikely. == Original Bug Report == This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+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 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
@ferenc-szabo, thank you for figuring out the issue with the _STA method. @kaihengfeng, it looks like we are both working on the same issue again :) I've written a simple, clean kernel patch fixing this, and I just got confirmation from the reporter of: https://bugzilla.redhat.com/show_bug.cgi?id=1842039 That this patch fixes this: --- a/drivers/i2c/i2c-core-base.c +++ b/drivers/i2c/i2c-core-base.c @@ -1464,8 +1464,8 @@ static int i2c_register_adapter(struct i2c_adapter *adap) /* create pre-declared device nodes */ of_i2c_register_devices(adap); - i2c_acpi_register_devices(adap); i2c_acpi_install_space_handler(adap); + i2c_acpi_register_devices(adap); if (adap->nr < __i2c_first_dynamic_bus_num) i2c_scan_static_board_info(adap); I'll Cc you on the upstream submission. ** Bug watch added: Red Hat Bugzilla #1842039 https://bugzilla.redhat.com/show_bug.cgi?id=1842039 -- 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/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+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 1893694] Re: Latest update breaks booting
** Tags added: regression-update -- 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/1893694 Title: Latest update breaks booting Status in linux-firmware package in Ubuntu: New Bug description: Regular package updates today brought these packages (and a few libpam-XXX): grub-common:amd64 (2.04-1ubuntu26.2, 2.04-1ubuntu26.3) grub2-common:amd64 (2.04-1ubuntu26.2, 2.04-1ubuntu26.3) grub-pc:amd64 (2.04-1ubuntu26.2, 2.04-1ubuntu26.3) grub-pc-bin:amd64 (2.04-1ubuntu26.2, 2.04-1ubuntu26.3) linux-firmware:amd64 (1.187.2, 1.187.3) After the following reboot, the machine would no longer come up. It got past Grub, but instead of Ubuntu logo appearing a second later, screen would stay entirely black. I waited at least 5 minutes, no change. I ended this with the power button. Subsequent tries in recovery mode and/or with the previous kernel didn't boot, either. The same machine would boot off an installation medium (USB pen drive) or the other connected hard disk just fine. Boot drive selection was done in BIOS. After a lot of back and forth, I ended up downgrading the above packages using the root shell in recovery mode: linux-firmware to v1.187 (v1.187.2 was not available), all four Grub packages to 2.04-1ubuntu26.2. With this, machine boots fine again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 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.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mah1487 F pulseaudio /dev/snd/pcmC0D0p: mah1487 F...m pulseaudio /dev/snd/controlC1: mah1487 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 31 22:20:10 2020 Dependencies: InstallationDate: Installed on 2016-05-04 (1580 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Vostro 200 PackageArchitecture: all ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=0e33bd99-d89c-4abe-8f18-10d9206ef547 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 RfKill: SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.16 dmi.board.name: 0CU409 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.16:bd09/20/2008:svnDellInc.:pnVostro200:pvr:rvnDellInc.:rn0CU409:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Vostro 200 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1893694/+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 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
It was solved, yet I am now on kernel 5.4.0-43 and I am hitting this now again since a week when using Jetbrains products. Clearly a regression, how could this 've happened. The linux-image* package changelog is pretty much worthless to investigate this. -- 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/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Fix Released Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: tricia Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
You still can't edit comments on LP :S? I am running kernel 5.4.0-42 instead of the earlier mentioned 5.4.0-43 -- 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/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Fix Released Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: tricia Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0K0DFT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1887622] Re: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04
*** This bug is a duplicate of bug 1887623 *** https://bugs.launchpad.net/bugs/1887623 ** This bug has been marked a duplicate of bug 1887623 Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 -- 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/1887622 Title: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 Status in linux package in Ubuntu: New Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887622/+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 1887623] Re: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04
** 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/1887623 Title: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 Status in linux package in Ubuntu: New Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887623/+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 516602] Re: [needs-packaging] owfs
Thanks for reporting this. owfs was packaged in Debian (see the attached bug watch) and has been available in Ubuntu for a while https://launchpad.net/ubuntu/+source/owfs ** Bug watch added: Debian Bug tracker #606189 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606189 ** Also affects: debian via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606189 Importance: Unknown Status: Unknown ** Changed in: linux (Ubuntu) Status: In Progress => 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/516602 Title: [needs-packaging] owfs Status in linux package in Ubuntu: Fix Released Status in Debian: Unknown Bug description: [needs-packaging] OWFS is set of drivers and applications for using the 1-wire devices from Dallas Instruments. Potential uses include environments monitoring applications URL: http://www.owfs.org License: GPL Notes: Nil To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/516602/+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 1850439] Re: No sound on ASUS UX534FT
Hi All, We (upstream kernel devs) are currently working with Realtek to get to the bottom of this, once we know what the exact settings are which need to be applied we can then add a quirk to the kernel to do this automatically. Realtek is asking for people with an affected laptop model to test the following 4 commands / register settings: hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf hda-verb /dev/snd/hwC0D0 0x20 0x400 0x7774 hda-verb /dev/snd/hwC0D0 0x20 0x500 0x45 hda-verb /dev/snd/hwC0D0 0x20 0x400 0x5289 If possible please check all 4 of: 1. Speakers 2. Headphones output 3. Internal mic. 4. Headset mic. (using a phone headset with builtin mic with a single T-R-R-S connector) After testing please report back here what works (and what does not work) after issueing the 4 above commands; and please do not forget to also let us know what model laptop you have. -- 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/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+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 1873280] Re: package libnvidia-compute-435 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package n
** Also affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags added: focal package-conflict -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1873280 Title: package libnvidia-compute-435 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu /libnvidia-ml.so', which is also in package nvidia-340 340.107-0ubuntu7 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: Trying to install nvidia-cuda-toolkit for a nvidia-820 ProblemType: Package DistroRelease: Ubuntu 19.10 Package: libnvidia-compute-435 (not installed) ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Tue Apr 14 22:10:50 2020 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package nvidia-340 340.107-0ubuntu7 InstallationDate: Installed on 2020-04-12 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: nvidia-graphics-drivers-435 Title: package libnvidia-compute-435 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package nvidia-340 340.107-0ubuntu7 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-340/+bug/1873280/+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 1879142] Re: package libnvidia-compute-435 (not installed) failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/libnvidia-ml.so« zu überschreiben, welches auch in Pake
*** This bug is a duplicate of bug 1873280 *** https://bugs.launchpad.net/bugs/1873280 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1873280, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1873280 package libnvidia-compute-435 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package nvidia-340 340.107-0ubuntu7 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1879142 Title: package libnvidia-compute-435 (not installed) failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/libnvidia-ml.so« zu überschreiben, welches auch in Paket nvidia-340 340.108-0ubuntu2 ist Status in nvidia-graphics-drivers-435 package in Ubuntu: New Bug description: I want to install CUDA, but it always puts this error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-compute-435 (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun May 17 12:49:47 2020 ErrorMessage: Versuch, »/usr/lib/x86_64-linux-gnu/libnvidia-ml.so« zu überschreiben, welches auch in Paket nvidia-340 340.108-0ubuntu2 ist InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-435 Title: package libnvidia-compute-435 (not installed) failed to install/upgrade: Versuch, »/usr/lib/x86_64-linux-gnu/libnvidia-ml.so« zu überschreiben, welches auch in Paket nvidia-340 340.108-0ubuntu2 ist 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-435/+bug/1879142/+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 1878206] Re: will not load firmware on 20.04
Ok, good :) Thanks for checking. I must admit I am not sure what caused the lock in the first place, though it may have been a check for updates running in the backgorund. I believe this sometimes happens right after booting, so if it became ok after waiting a while that might have been it. In any case, since the issue seems to have been resolved, I've taken the liberty of closing this issue. If it should happen again, please leave a comment and we'll reopen it. If the error message lists a process as in the first example " It is held by process 4155 (apt-get)", please run `ps -ef | grep 4155` (replace the number with the process id given). That way, we can take a look at what is happening. ** Changed in: b43-fwcutter (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to b43-fwcutter in Ubuntu. https://bugs.launchpad.net/bugs/1878206 Title: will not load firmware on 20.04 Status in b43-fwcutter package in Ubuntu: Invalid Bug description: tryimg to update firmware the following happens. -network description: Network controller product: BCM43217 802.11b/g/n vendor: Broadcom Inc. and subsidiaries physical id: 0 bus info: pci@:06:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: bus_master cap_list configuration: driver=bcma-pci-bridge latency=0 resources: irq:37 memory:f750-f7507fff PCI-ID Supported? Chip ID Modes PHY version Alternative 14e4:43a9 yes (3.17+) BCM43217 b/g/n N (r17) bill@bill-computer:~$ sudo apt-get install firmware-b43-installer [sudo] password for bill: E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 4155 (apt-get) N: Be aware that removing the lock file is not a solution and may break your system. E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firmware-b43-installer (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 14:17:28 2020 SourcePackage: b43-fwcutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1878206/+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 1878206] Re: will not load firmware on 20.04
Thanks for reporting. Based on the error message, this doesn't seem to be directly caused by firmware-b43-installer. It looks like there's a different apt-get process currently running, perhaps installing other packages in a different terminal? Could you check if all other apt-get processes are finished and if you still get the same error? Normally it is only possible to run one apt-get process at the time, though it should remove the lock once finished. If a lock is still "left behind" that might be a bug in apt. ** Changed in: b43-fwcutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to b43-fwcutter in Ubuntu. https://bugs.launchpad.net/bugs/1878206 Title: will not load firmware on 20.04 Status in b43-fwcutter package in Ubuntu: Incomplete Bug description: tryimg to update firmware the following happens. -network description: Network controller product: BCM43217 802.11b/g/n vendor: Broadcom Inc. and subsidiaries physical id: 0 bus info: pci@:06:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: bus_master cap_list configuration: driver=bcma-pci-bridge latency=0 resources: irq:37 memory:f750-f7507fff PCI-ID Supported? Chip ID Modes PHY version Alternative 14e4:43a9 yes (3.17+) BCM43217 b/g/n N (r17) bill@bill-computer:~$ sudo apt-get install firmware-b43-installer [sudo] password for bill: E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 4155 (apt-get) N: Be aware that removing the lock file is not a solution and may break your system. E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firmware-b43-installer (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 14:17:28 2020 SourcePackage: b43-fwcutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1878206/+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 1874519] Re: ZFS installation on Raspberry Pi is problematic
Looks like `zfsutils-linux` is part of the source package `zfs-linux` ** Package changed: zfsutils (Ubuntu) => zfs-linux (Ubuntu) ** Tags added: 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/1874519 Title: ZFS installation on Raspberry Pi is problematic Status in zfs-linux package in Ubuntu: New Bug description: Version: Ubuntu Server 20.04 - preinstalled 64-bit image for Raspberry Pi. ZFS on the Pi under 20.04 is currently a bit problematic. Upon issuing the command 'zpool status', I'm helpfully directed to install zfsutils-linux. When I do this, it complains that it cannot find the ZFS module, then errors out. Worse than that, the zfsutils-linux package does not depend on the zfs-dkms package, so it doesn't attempt to build the ZFS kernel modules automatically. The workaround is to install zfs-dkms, which builds the required kernel modules. (Once this has been done, the usual errors when installing the zfsutils-linux package, caused by there being no ZFS pools on the system, can be worked around by creating a zpool, then rerunning 'sudo apt install zfsutils-linux', as with previous versions of Ubuntu and Debian). I have not tested on other hardware platforms - this problem may also exist on other platforms where the user has not selected to install to ZFS. I have selected 'zfsutils' as the affected package, which is not the name of an actual current package, since launchpad won't let me submit the bug without selecting a package, however it's not clear to me that the problem is caused by that package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1874519/+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 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
#57 this works. Hard to install on 18.04 though, you need the headers package (linux- headers-5.3.0-48_5.3.0-48.41_all.deb) from eoan -- 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/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: In Progress Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: tricia Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0K0DFT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell
[Kernel-packages] [Bug 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
Well the "[drm:intel_dsi_vbt_gpio_init [i915]] *ERROR* Failed to own gpio for panel control" error is gone. I just noticed you describe the problem as "blank screen with a cursor" , I should have noticed this before. I assume with a cursor you mean a mouse cursor (and not a Linux text console cursor. So you are likely hitting the issue I mentioned before where we hit a GPU freeze and indeed looking closer at the logs that is exactly what is going on: Apr 09 08:34:55 SrLungACI kernel: i915 :00:02.0: GPU HANG: ecode 8:1:85db, in Xorg [938] Apr 09 08:34:55 SrLungACI kernel: GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. I have checked and there already is an upstream bug report for this: https://gitlab.freedesktop.org/drm/intel/-/issues/1605 To which I have added some details about the times when I hit this + a link to this bug. What might be helpful is if you can configure ssh on your machine, then ssh in while it hangs (that should still work) and do: sudo cp /sys/class/drm/card0/error i915-crash-dump And then attach both the dmesg output from that boot as well as the i915-crash-dump file to the upstream bug report: https://gitlab.freedesktop.org/drm/intel/-/issues/1605 ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #1605 https://gitlab.freedesktop.org/drm/intel/-/issues/1605 -- 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/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN 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.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/1860754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
p.s. There is another issue with 5.5.y and 5.6 kernels on Cherry Trail hardware, at least with Fedora I'm seeing regular GPU freezes; and specifically on the T100HAN also spontaneous reboots. I've seen the GPU freezes on multiple Cherry Trail devices (these require ssh-ing in and killing gnome-shell to recover from them). I have seen these with both mesa 19.2 and mesa 20.0, so I suspect this is a kernel issue, I still need to investigate these further. -- 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/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN 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.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/1860754/+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 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
I have a T100HAN in my personal hw collection, so I just booted up a nightly build of the Fedora 32 workstation livecd on it and that works fine for me. This nightly build is using a 5.6 kernel. So the 5.6 kernel can work on this hardware. AFAIK Ubuntu, like Fedora puts the i915 driver in the initrd. I guess either a module is missing from the initrd, or there is a module loading ordering issue going on here. The T100HAN uses a Crystal Cove PMIC. Here are the setting from a couple of relevant Kconfig options which Fedora uses: CONFIG_INTEL_SOC_PMIC=y CONFIG_PWM_CRC=y CONFIG_GPIO_CRYSTAL_COVE=y CONFIG_PMIC_OPREGION=y CONFIG_BYTCRC_PMIC_OPREGION=y CONFIG_CHTCRC_PMIC_OPREGION=y Note these are all builtin for Fedora, perhaps you can do a test build of an Ubuntu kernel with the same settings? Also can you attach, or email me the .config Ubuntu is using for building their kernels? -- 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/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN 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.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/1860754/+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 1863222] Re: Please update to hwdata 0.332
** Bug watch added: Debian Bug tracker #947191 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947191 ** Also affects: hwdata (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947191 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1863222 Title: Please update to hwdata 0.332 Status in hwdata package in Ubuntu: New Status in hwdata package in Debian: Unknown Bug description: Please update hwdata to 0.332, and update the homepage and watch file to better track newer versions. https://github.com/vcrhonek/hwdata/releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1863222/+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 1789589] Re: USB-SATA resets when UAS is used
>From the original report: "When the device is under load and more than 1 hardrive is acessed, the USB enclosure frequently restarts." So this very much sounds like a hardware problem. UAS allows having multiple outstanding commands (read/write requests) and thus *actually* accessing multiple disks at once. If you disable UAS then there can be only 1 read *or* write requests be done at a time and only when that requests has fully completed, which requires 3 round-trips to the device, then the next request can be send. So, especially when accessing multiple drives (or a SSD) using the old mass-storage USB protocol is much much slower. The slowness has one advantage though, if only 1 thing is done at a time / only 1 drive accesses at a time, then much less power is consumed by the driver. Unfortunately this often causes people to believe that there is a bug in the UAS driver, where as the real problem is the power-supply of their disk enclosure not providing enough power. "the USB enclosure frequently restarts." is exactly what one would expect with brown-out (voltage level getting too low) issues like this. So I'm 90% sure that this an issue with the power-supply used to power the enclosure either being bad, or simply not being powerful enough. Note I used to be the upstream kernel maintainer for the Linux UAS driver for a number of years. @kaihengfeng, this issue should probably be closed as not a bug or some such. -- 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/1789589 Title: USB-SATA resets when UAS is used Status in linux package in Ubuntu: Confirmed Bug description: Dear developers, I have a Icybox 4 HDD enclosure with a JMicrom JMS567 SATA to USB converter. When the device is under load and more than 1 hardrive is acessed, the USB enclosure frequently restarts. This leaves often a corrup filesystem. I tried to switch off UAS by creating a file in /etc/modprobe.d/blacklist_uas.conf with the following content: options usb-storage quirks=152d:0567:u This disables UAS, and I did not exerinecs restarts of the box. But of course thios laves only USB speeds on the USB3 connector, which is quite slow. I think this suggest this is a kernel bug and not a hardware issues. I aasume the problem is in the linux-image-4.15.0-33-generic package. Similar has been reported: https://www.spinics.net/lists/linux-usb/msg157550.html Any help would be greatly appreciated. Best regards Michael lsusb -vvv -s 003:004 Bus 003 Device 004: ID 152d:0567 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 9 idVendor 0x152d JMicron Technology Corp. / JMicron USA Technology Corp. idProduct 0x0567 JMS567 SATA 6Gb/s bridge bcdDevice2.05 iManufacturer 10 iProduct 11 iSerial 5 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 44 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower2mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 res3stockm@brix:~$ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 --- ProblemType: Bug
[Kernel-packages] [Bug 1575334] Re: Docking thinkpad laptop causes a complete system freeze
I've been dealing with this issue for two years now, happens about 30% of the time when I put it on the dock, after a restart it works fine. Since I don't have the time or knowledge to help identify this issue, at least I wanted to share the workaround I recently found: - Just never dock or undock when the laptop is suspended. Turn it on first, then dock/undock. Otherwise you're in trouble next time. Linux 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u5 (2019-08-11) x86_64 GNU/Linux -- 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/1575334 Title: Docking thinkpad laptop causes a complete system freeze Status in linux package in Ubuntu: Expired Bug description: Since upgrading to Xenial, about 80% of the time when I dock my thinkpad laptop I get a complete system freeze. The symptoms of the freeze are: * The two external monitors connected to the dock seem to be in a half-configured state - they're powered on, and display some graphics from my desktop, but do not yet show the correct contents. * I can't get to a console with Ctrl+Alt+F1. * I can't kill X with Ctrl+Alt+Backspace * I can't get the mouse cursor to appear or move, either with the trackpad or the external mouse. * Undocking the laptop doesn't help. The only thing I *can* do at this point is to hold down the power button. I seem to recall similar issues in the past (perhaps in Vivid?), where the fix ended up being in the graphics driver. The laptop is a T540p. The docking station is an "ultra dock pro" - not a USB dock, but rather one of those ones where the laoptop clicks into a base. This bug makes the docking station rather useless, and makes me sad :( ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: thomi 3196 F pulseaudio /dev/snd/controlC0: thomi 3196 F pulseaudio /dev/snd/controlC1: thomi 3196 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 27 07:35:58 2016 HibernationDevice: RESUME=UUID=d27c9b15-955a-4bff-b4a7-e6116a8b30bb InstallationDate: Installed on 2015-10-12 (197 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 20BECTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-21 (5 days ago) dmi.bios.date: 09/01/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GMET72WW (2.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BECTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGMET72WW(2.20):bd09/01/2015:svnLENOVO:pn20BECTO1WW:pvrThinkPadT540p:rvnLENOVO:rn20BECTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20BECTO1WW dmi.product.version: ThinkPad T540p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575334/+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 1848008] Re: eoan needs iproute2 v5.3.0
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1848008 Title: eoan needs iproute2 v5.3.0 Status in iproute2 package in Ubuntu: New Bug description: As eoan will ship a 5.3 kernel it needs iproute v5.3.0. There are important updates, e.g. to the 'rdma' command which are needed in order to activate certain kernel features. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1848008/+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 1830440] Re: Xen guest time corrupted after live migration in linux-image-4.15.0-50-generic and linux-image-generic-hwe-18.04
Hi, I can confirm that this report makes sense. I was the person reporting it upstream and doing some debugging/bisecting to find the cause. https://lists.xenproject.org/archives/html/xen- devel/2018-12/msg02403.html The bug causes the uptime of the two dom0s that live migration is done from/to to have an effect on the uptime counter (as seen in dmesg output) of the domU. This causes TCP timestamps to bork all over the place and cause network connections to stall. I'd advise the reporter to test this kernel with the patch applied and use it in a reproduction scenario, where live migrate hits the bug all the time, and where it doesn't hit it anymore with the patch. Thanks, Hans -- 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/1830440 Title: Xen guest time corrupted after live migration in linux- image-4.15.0-50-generic and linux-image-generic-hwe-18.04 Status in linux package in Ubuntu: Confirmed Bug description: Effects observed after migration include: * Stalled SSH connections. * A crashed or unresponsive virtual machine. * Inability to properly shut down the virtual machine. * Incorrect timestamps in dmesg output. The only effect that is really guaranteed is incorrect timestamps, but the rest are reproducible. This issue was fixed in version 5.0.0 of the Linux kernel, and the fix was backported to older supported kernels such as 4.14 and 4.19. Please cherry-pick the following commit from the master branch of the Linux kernel's git repo: 867cefb4cb1012f42cada1c7d1f35ac8dd276071 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830440/+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 1822913] Re: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at 0000000000000000
@Maurizio, could you test a newer Kernel? 5.1 for example to see if it's already solved, it is in my case. -- 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/1822913 Title: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: New Bug description: With Kernel 5.0.0-8 I have strange behaivour. I have no wifi and no sound, typing sudo doesn't work. kern.log attached, include a boot with kernel 5 and one with 4.19 (which works ok) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822913/+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 1821564] Re: b44 Ethernet driver null pointer during initialization
@Boris please test kernel 5.1.0-050100rc3-generic (or above) at least #1822913 was solved with this kernel -- 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/1821564 Title: b44 Ethernet driver null pointer during initialization Status in linux package in Ubuntu: Confirmed Bug description: This problem started after upgrading to Ubuntu 19.04. It was not present with 4.18.0-16-generic kernel and is present in the 4.18.0-15-generic kernel. Ever time during boot there is a null pointer dereference in the b44 driver for the on-board Ethernet on this Dell Inspiron 6400. After that I can log in but networking related commands hang and the computer eventually locks up. Blacklisting the b44 module so it doesn't load works as a workaround, though of course the on board Ethernet can't be used that way. The b43 WiFi still works then. The following is pasted from the log of one crash: 6.483003] BUG: unable to handle kernel NULL pointer dereference at 6.483052] #PF error: [normal kernel read fault] 6.483093] PGD 0 P4D 0 6.483133] Oops: [#1] SMP PTI 6.483175] CPU: 0 PID: 725 Comm: NetworkManager Tainted: GW 5.0.0-7-generic #8-Ubuntu 6.483217] Hardware name: Dell Inc. MM061 /0XD720, BIOS A17 06/13/2007 6.483267] RIP: 0010:swiotlb_tbl_map_single+0x120/0x310 6.483310] Code: 4c 8b 45 a8 4c 8b 1d 0f b2 a9 01 89 d3 45 31 d2 44 8b 4d a4 44 89 c7 41 89 dc 4b 8d 44 25 00 48 21 f0 48 01 f8 49 39 c7 72 0a <47> 39 0c a3 0f 83 cb 00 00 00 42 8d 04 33 48 89 c3 48 39 c1 41 0f 6.483368] RSP: 0018:bc7040c7f3c0 EFLAGS: 00010016 6.483416] RAX: 0001 RBX: RCX: 6.483467] RDX: RSI: 001f RDI: 0001 6.483521] RBP: bc7040c7f420 R08: 0001 R09: 0001 6.483572] R10: R11: R12: 6.483621] R13: R14: 0001 R15: 0020 6.483670] FS: 7f2cb49ccbc0() GS:9d8a4c40() knlGS: 6.483726] CS: 0010 DS: ES: CR0: 80050033 6.483773] CR2: CR3: c72ce000 CR4: 06f0 6.483820] Call Trace: 6.483869] swiotlb_map+0x6c/0x1c0 6.483915] dma_direct_map_page+0xc5/0x160 6.483965] b44_alloc_rx_skb+0x18e/0x3f0 [b44] 6.484013] b44_init_rings+0xbe/0x1b0 [b44] 6.484060] b44_open+0xfc/0x3f0 [b44] 6.484107] __dev_open+0xd4/0x170 6.484153] __dev_change_flags+0x18f/0x200 6.484199] dev_change_flags+0x27/0x60 6.484246] do_setlink+0x31c/0xe30 6.484292] ? __nla_parse+0xf1/0x120 6.484340] ? cpumask_next+0x1b/0x20 6.484388] ? __snmp6_fill_stats64.isra.57+0xf6/0x120 6.484439] ? __nla_parse+0x38/0x120 6.484488] __rtnl_newlink+0x531/0x910 6.484535] ? __nla_put+0x20/0x30 6.484586] ? __kmalloc_node_track_caller+0x1e6/0x2b0 6.484636] ? pskb_expand_head+0x70/0x2e0 6.484693] ? __kmalloc_reserve.isra.53+0x31/0x90 6.484751] ? apparmor_inet_conn_request+0x40/0x40 6.484822] ? security_sock_rcv_skb+0x2f/0x50 6.484879] ? skb_queue_tail+0x43/0x50 6.484934] ? __netlink_sendskb+0x53/0x70 6.484992] ? syscall_return_via_sysret+0xf/0x7f 6.485043] ? __switch_to_asm+0x40/0x70 6.485097] ? syscall_return_via_sysret+0xf/0x7f 6.485153] ? _cond_resched+0x19/0x30 6.485204] ? kmem_cache_alloc_trace+0x153/0x1d0 6.485253] rtnl_newlink+0x48/0x70 6.485301] rtnetlink_rcv_msg+0x213/0x300 6.485348] ? __d_lookup+0x126/0x140 6.485393] ? rtnl_calcit.isra.31+0x100/0x100 6.485440] netlink_rcv_skb+0x4f/0x120 6.485485] rtnetlink_rcv+0x15/0x20 6.485518] netlink_unicast+0x1a1/0x260 6.485518] netlink_sendmsg+0x20d/0x3c0 6.485518] sock_sendmsg+0x3e/0x50 6.485518] ___sys_sendmsg+0x295/0x2f0 6.485518] ? rtnl_unlock+0xe/0x10 6.485518] ? addrconf_sysctl_forward+0x114/0x280 6.485518] ? dev_forward_change+0x140/0x140 6.485518] ? __fget_light+0x54/0x60 6.485518] __sys_sendmsg+0x5c/0xa0 6.485518] __x64_sys_sendmsg+0x1f/0x30 6.485518] do_syscall_64+0x5a/0x110 6.485518] entry_SYSCALL_64_after_hwframe+0x44/0xa9 6.485518] RIP: 0033:0x7f2cb6153cb7 6.485518] Code: 44 00 00 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 3b ed ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 74 ed ff ff 48 6.485518] RSP: 002b:7ffe93a35c80 EFLAGS: 0293 ORIG_RAX: 002e 6.485518] RAX: ffda RBX: 0008 RCX: 7f2cb6153cb7 6.485518] RDX: RSI: 7ffe93a35cd0 RDI: 0008 6.485518] RBP: 7ffe93a35cd0 R08: R09: 6.485518] R10: 7f2cb6139ca0 R11: 0293 R12: 6.485518] R13: 5598b029e880 R14:
[Kernel-packages] [Bug 1822913] Re: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at 0000000000000000
problem is solved in kernel 5.1.0-050100rc3-generic Is it necessary the bisect? -- 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/1822913 Title: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at Status in linux package in Ubuntu: Confirmed Bug description: With Kernel 5.0.0-8 I have strange behaivour. I have no wifi and no sound, typing sudo doesn't work. kern.log attached, include a boot with kernel 5 and one with 4.19 (which works ok) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822913/+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 1821564] Re: b44 Ethernet driver null pointer during initialization
I just tested Kernel 4.20.17 an it is good. I will do the bisect but I don't have much time at this moment -- 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/1821564 Title: b44 Ethernet driver null pointer during initialization Status in linux package in Ubuntu: Confirmed Bug description: This problem started after upgrading to Ubuntu 19.04. It was not present with 4.18.0-16-generic kernel and is present in the 4.18.0-15-generic kernel. Ever time during boot there is a null pointer dereference in the b44 driver for the on-board Ethernet on this Dell Inspiron 6400. After that I can log in but networking related commands hang and the computer eventually locks up. Blacklisting the b44 module so it doesn't load works as a workaround, though of course the on board Ethernet can't be used that way. The b43 WiFi still works then. The following is pasted from the log of one crash: 6.483003] BUG: unable to handle kernel NULL pointer dereference at 6.483052] #PF error: [normal kernel read fault] 6.483093] PGD 0 P4D 0 6.483133] Oops: [#1] SMP PTI 6.483175] CPU: 0 PID: 725 Comm: NetworkManager Tainted: GW 5.0.0-7-generic #8-Ubuntu 6.483217] Hardware name: Dell Inc. MM061 /0XD720, BIOS A17 06/13/2007 6.483267] RIP: 0010:swiotlb_tbl_map_single+0x120/0x310 6.483310] Code: 4c 8b 45 a8 4c 8b 1d 0f b2 a9 01 89 d3 45 31 d2 44 8b 4d a4 44 89 c7 41 89 dc 4b 8d 44 25 00 48 21 f0 48 01 f8 49 39 c7 72 0a <47> 39 0c a3 0f 83 cb 00 00 00 42 8d 04 33 48 89 c3 48 39 c1 41 0f 6.483368] RSP: 0018:bc7040c7f3c0 EFLAGS: 00010016 6.483416] RAX: 0001 RBX: RCX: 6.483467] RDX: RSI: 001f RDI: 0001 6.483521] RBP: bc7040c7f420 R08: 0001 R09: 0001 6.483572] R10: R11: R12: 6.483621] R13: R14: 0001 R15: 0020 6.483670] FS: 7f2cb49ccbc0() GS:9d8a4c40() knlGS: 6.483726] CS: 0010 DS: ES: CR0: 80050033 6.483773] CR2: CR3: c72ce000 CR4: 06f0 6.483820] Call Trace: 6.483869] swiotlb_map+0x6c/0x1c0 6.483915] dma_direct_map_page+0xc5/0x160 6.483965] b44_alloc_rx_skb+0x18e/0x3f0 [b44] 6.484013] b44_init_rings+0xbe/0x1b0 [b44] 6.484060] b44_open+0xfc/0x3f0 [b44] 6.484107] __dev_open+0xd4/0x170 6.484153] __dev_change_flags+0x18f/0x200 6.484199] dev_change_flags+0x27/0x60 6.484246] do_setlink+0x31c/0xe30 6.484292] ? __nla_parse+0xf1/0x120 6.484340] ? cpumask_next+0x1b/0x20 6.484388] ? __snmp6_fill_stats64.isra.57+0xf6/0x120 6.484439] ? __nla_parse+0x38/0x120 6.484488] __rtnl_newlink+0x531/0x910 6.484535] ? __nla_put+0x20/0x30 6.484586] ? __kmalloc_node_track_caller+0x1e6/0x2b0 6.484636] ? pskb_expand_head+0x70/0x2e0 6.484693] ? __kmalloc_reserve.isra.53+0x31/0x90 6.484751] ? apparmor_inet_conn_request+0x40/0x40 6.484822] ? security_sock_rcv_skb+0x2f/0x50 6.484879] ? skb_queue_tail+0x43/0x50 6.484934] ? __netlink_sendskb+0x53/0x70 6.484992] ? syscall_return_via_sysret+0xf/0x7f 6.485043] ? __switch_to_asm+0x40/0x70 6.485097] ? syscall_return_via_sysret+0xf/0x7f 6.485153] ? _cond_resched+0x19/0x30 6.485204] ? kmem_cache_alloc_trace+0x153/0x1d0 6.485253] rtnl_newlink+0x48/0x70 6.485301] rtnetlink_rcv_msg+0x213/0x300 6.485348] ? __d_lookup+0x126/0x140 6.485393] ? rtnl_calcit.isra.31+0x100/0x100 6.485440] netlink_rcv_skb+0x4f/0x120 6.485485] rtnetlink_rcv+0x15/0x20 6.485518] netlink_unicast+0x1a1/0x260 6.485518] netlink_sendmsg+0x20d/0x3c0 6.485518] sock_sendmsg+0x3e/0x50 6.485518] ___sys_sendmsg+0x295/0x2f0 6.485518] ? rtnl_unlock+0xe/0x10 6.485518] ? addrconf_sysctl_forward+0x114/0x280 6.485518] ? dev_forward_change+0x140/0x140 6.485518] ? __fget_light+0x54/0x60 6.485518] __sys_sendmsg+0x5c/0xa0 6.485518] __x64_sys_sendmsg+0x1f/0x30 6.485518] do_syscall_64+0x5a/0x110 6.485518] entry_SYSCALL_64_after_hwframe+0x44/0xa9 6.485518] RIP: 0033:0x7f2cb6153cb7 6.485518] Code: 44 00 00 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 3b ed ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 74 ed ff ff 48 6.485518] RSP: 002b:7ffe93a35c80 EFLAGS: 0293 ORIG_RAX: 002e 6.485518] RAX: ffda RBX: 0008 RCX: 7f2cb6153cb7 6.485518] RDX: RSI: 7ffe93a35cd0 RDI: 0008 6.485518] RBP: 7ffe93a35cd0 R08: R09: 6.485518] R10: 7f2cb6139ca0 R11: 0293 R12: 6.485518] R13: 5598b029e880 R14:
[Kernel-packages] [Bug 1822913] Re: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at 0000000000000000
I saw in the comments that #1821564 was with kernel 5 it might be a dupe of it then. -- 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/1822913 Title: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at Status in linux package in Ubuntu: Confirmed Bug description: With Kernel 5.0.0-8 I have strange behaivour. I have no wifi and no sound, typing sudo doesn't work. kern.log attached, include a boot with kernel 5 and one with 4.19 (which works ok) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822913/+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 1822913] Re: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at 0000000000000000
I cannot run apport-collect because when I have this issue I don't have wifi connectiom. I will try to connect via cable an do apport-collect, but It will take some time. Giving that 19.04 with Kernel 5 is almost ready to be delivered, I will change to confirm anyway. I'm not sure is a dupe of #1821564 because it's a different Kernel (5) and in 4.19 it works ok, symptoms are very similar though. ** 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/1822913 Title: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at Status in linux package in Ubuntu: Confirmed Bug description: With Kernel 5.0.0-8 I have strange behaivour. I have no wifi and no sound, typing sudo doesn't work. kern.log attached, include a boot with kernel 5 and one with 4.19 (which works ok) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822913/+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 1822913] Re: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at 0000000000000000
forgot to add info about the audio and wifi: *-multimedia description: Audio device product: NM10/ICH7 Family High Definition Audio Controller vendor: Intel Corporation physical id: 1b bus info: pci@:00:1b.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:25 memory:efebc000-efeb *-network description: Wireless interface product: PRO/Wireless 3945ABG [Golan] Network Connection vendor: Intel Corporation physical id: 0 bus info: pci@:0c:00.0 logical name: wlp12s0 version: 02 serial: 00:18:de:8a:64:ec width: 32 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwl3945 driverversion=4.19.0-13-generic firmware=15.32.2.9 ip=192.168.0.18 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:24 memory:efdff000-efdf -- 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/1822913 Title: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at Status in linux package in Ubuntu: New Bug description: With Kernel 5.0.0-8 I have strange behaivour. I have no wifi and no sound, typing sudo doesn't work. kern.log attached, include a boot with kernel 5 and one with 4.19 (which works ok) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822913/+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 1822913] [NEW] Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at 0000000000000000
Public bug reported: With Kernel 5.0.0-8 I have strange behaivour. I have no wifi and no sound, typing sudo doesn't work. kern.log attached, include a boot with kernel 5 and one with 4.19 (which works ok) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel kernel-bug ** Attachment added: "kern.log" https://bugs.launchpad.net/bugs/1822913/+attachment/5252319/+files/kern.log -- 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/1822913 Title: Kernel 5.0.0-8 unable to handle kernel NULL pointer dereference at Status in linux package in Ubuntu: New Bug description: With Kernel 5.0.0-8 I have strange behaivour. I have no wifi and no sound, typing sudo doesn't work. kern.log attached, include a boot with kernel 5 and one with 4.19 (which works ok) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822913/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Robert, There are some patches pending upstream to fix the "incomplete report" errors in the mean time these can be safely ignored. As for you needing to do a 2-finger-click to get a right click, that means that libinput is configured for clickfinger behavior rather then click areas. To change this run gnome-tweaks and go to: "Keyboard & Mouse" then under "Mouse Click Emulation" select "Area" that should give you a right click at the bottom right area of the touchpad. Regards, Hans -- 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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Good news (hopefully) it looks like we finally have found a fix which is not an ugly hack / does not disable runtime pm for other devices which will hopefully fix this. Kai-Heng Feng, can you build a kernel with this patch: https://patchwork.kernel.org/patch/10597519/ Added for reporters of this bug to test ? That patch hopefully resolves this in a supportable/maintainable way. -- 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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1788844] Re: -Excessive undersized/giant packets with intel nic's
As Bas already told: we have a production site with 2 (identical) servers, configured as loadbalancer. At first the network problems occurred at the primary loadbalancer, but after rebooting that one the problems migrated to the second server. Only after rebooting both servers with the previous kernel our servers became accessible 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/1788844 Title: -Excessive undersized/giant packets with intel nic's Status in linux package in Ubuntu: Confirmed Bug description: With new kernel we get on our switch the following error: W 08/24/18 12:34:47 00327 FFI: ST2-CMDR: port 2/31-Excessive undersized/giant packets. See help. W 08/24/18 12:35:28 00327 FFI: ST2-CMDR: port 2/34-Excessive undersized/giant packets. See help. W 08/24/18 12:37:10 00327 FFI: ST2-CMDR: port 2/33-Excessive undersized/giant packets. See help. The problem is resolved by booting back to kernel 4.15.0-32-generic These are network specifications: root@lb1:~# lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 06) 00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31) 00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31) 00:16.1 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #2 (rev 31) 00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] (rev 31) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #5 (rev f1) 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #6 (rev f1) 00:1c.6 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #7 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31) 00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31) 01:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200e [Pilot] ServerEngines (SEP1) (rev 05) 01:00.1 Co-processor: Emulex Corporation ServerView iRMC HTI 02:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) 03:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) 04:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) 04:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) 04:00.2 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) 04:00.3 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-headers-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 24 12:39 seq crw-rw 1 root audio 116, 33 Aug 24 12:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 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: Fri Aug 24 12:57:11 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: FUJITSU PRIMERGY RX1330 M3 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=d69c3457-31e5-4daf-8d31-1d2022f93c25 ro text RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.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/26/2018 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V5.0.0.11 R1.18.0 for D3375-B1x dmi.board.name: D3375-B1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3375-B12 WGS03 GS01 dmi.chassis.asset.tag: LB1 dmi.chassis.type: 23
[Kernel-packages] [Bug 1740143] Re: backport btrfs ssd mount option fix
Hi, patch author here. You can ask BTRFS maintainers by mailing to the linux-bt...@vger.kernel.org mailing list. Also, the patch author email address is in the commit itself, for quick questions. :-) I just stumbled across this ubuntu issue while being bored and reading https://wiki.debian.org/Btrfs where it's linked. If you're using btrfs, I would personally not recommend using a linux 4.4 kernel, but at least 4.9 and preferably 4.14. The btrfs project does not really have enough resources to properly manage tracking and sorting out fixes and updating older kernels than the latest LTS. The latest LTS (4.14 now) has the highest chance of getting important fixes, for all other versions it depends on the knowledge and decisions of the patch author what happens. (By the way, this is also the reason Redhat dropped btrfs support: if you don't really know what you're doing (which means investing in having a bunch of serious btrfs developers in your team) then trying to selectively backports things becomes a real mine field quickly.) Aside from that, the "has a negative impact on usability" is certainly true, and including this change in kernels < 4.14 that are used by Joe Average who wants to use btrfs is certainly useful. Backporting this one is not risky, the change doesn't bite much. Apart from the mount option behaviour change that's mentioned (which can either be picked or ignored) the old code has pretty much been there since 2008. Disclaimer: I'm a Debian user, so I don't follow ubuntu kernels closely. When looking at... https://wiki.ubuntu.com/Kernel/FAQ#Kernel.2FSupport.Ubuntu_Kernel_Support ...I would recommend btrfs users to just move to Ubuntu 18.x. -- 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/1740143 Title: backport btrfs ssd mount option fix Status in linux package in Ubuntu: Triaged Bug description: Hello, It appears that all kernels before 4.14 had a problem with btrfs ssd mount option. According to https://btrfs.wiki.kernel.org/index.php/Gotchas#ssd_mount_option, it has a negative impact on usability and lifetime of modern SSDs. Since it is enabled by default when SSD is detected, it affects all systems with SSD drives. Please backport this commit to normal and HWE kernels: https://github.com/torvalds/linux/commit/583b723151794e2ff1691f1510b4e43710293875 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.104.109 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 дек 17 10:50 seq crw-rw 1 root audio 116, 33 дек 17 10:50 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-104-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.14 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: CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Dec 26 18:57:10 2017 InstallationDate: Installed on 2011-04-14 (2448 days ago) InstallationMedia: Ubuntu-Server 10.04.2 LTS "Lucid Lynx" - Release amd64 (20110211.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. PciMultimedia: ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic root=UUID=c7605446-0bf3-11e7-bfa0-f91abd974ce1 ro quiet bootdegraded=true RelatedPackageVersions: linux-restricted-modules-4.4.0-104-generic N/A linux-backports-modules-4.4.0-104-generic N/A linux-firmware 1.157.14 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-07-30 (513 days ago) WifiSyslog: dmi.bios.date: 02/20/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: 4Core1333-eSATA2. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd02/20/2008:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvn:rn4Core1333-eSATA2.:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1773718] Re: mouse pointer disappear after screen off
I haven't tried with other DE, since it is an old computer I have only tried lxde. I could easily try with openbox alone, installing another DE could be a little longer. Is there one better to test with? -- 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/1773718 Title: mouse pointer disappear after screen off Status in linux package in Ubuntu: Confirmed Bug description: With nouveau driver (doesn't happened with propietary nvidia) after screen switch off because of power management, the mouse pointer disappear. Mouse still works, you can hover, select, click, but the pointer is invisible. In a dual monitor configuration, this only happened in the screen where the mouse was when it turned off. If It firs happened in one monitor and tehn I left the mouse in the other and it also turn off, mouse end up disappearing in both. My video card is an nvidia GeForce Go6150 (NV4E C51). Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773718/+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 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29
Update to #138: My problem seems to be related to Bug #1752053 and Bug #1773113. And for me now everything more or less works again by using this workaround from Bug #1752053 posting #123: -snip I found a silly workaround (after trying many many other suggestions / driver re-installs), now using nvidia-driver-396 or nvidia-driver-390; create (if not exists) a file /etc/rc.local, with this content: #!/bin/bash sleep 1 exit 0 And make it executable: chmod 755 /etc/rc.local -snip Maybe this helps some people. -- 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/1743094 Title: [regression] hibernation (freezes on resume) since 4.13.0-25.29 Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: After hibernating the system and than resuming it the system reboots notifying that it is resuming and than stops/freezes. The system does not respond to anything (no tty's other notifying textg are available). After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep functions as proposed. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jb 1717 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478 InstallationDate: Installed on 2017-12-10 (34 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: Acer Aspire S3-391 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-26-generic N/A linux-backports-modules-4.13.0-26-generic N/A linux-firmware 1.157.14 Tags: sylvia Uname: Linux 4.13.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/31/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Hummingbird2 dmi.board.vendor: Acer dmi.board.version: V2.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S3-391 dmi.product.version: V2.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/+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 1773718] Re: mouse pointer disappear after screen off
I just realize that it only happen after login (lxde, lubuntu) in lightdm this does not happen. -- 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/1773718 Title: mouse pointer disappear after screen off Status in linux package in Ubuntu: Confirmed Bug description: With nouveau driver (doesn't happened with propietary nvidia) after screen switch off because of power management, the mouse pointer disappear. Mouse still works, you can hover, select, click, but the pointer is invisible. In a dual monitor configuration, this only happened in the screen where the mouse was when it turned off. If It firs happened in one monitor and tehn I left the mouse in the other and it also turn off, mouse end up disappearing in both. My video card is an nvidia GeForce Go6150 (NV4E C51). Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773718/+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 1773718] Re: mouse ponter disappear after screen off
Hi, I've seen this problem since I install linux in this computer (2 years ago), but my workaround was to use the nvidia propietary driver. Now that nvidia stop developing the 304 driver, I will have to use nouveau. I installed 4.17.0-041700rc7-generic and the problem still is there. It might be that I had to wait a couple of minutes more oafter the screen switch off or suspended, but the problem is still there. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream ** Summary changed: - mouse ponter disappear after screen off + mouse pointer disappear after screen off -- 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/1773718 Title: mouse pointer disappear after screen off Status in linux package in Ubuntu: Confirmed Bug description: With nouveau driver (doesn't happened with propietary nvidia) after screen switch off because of power management, the mouse pointer disappear. Mouse still works, you can hover, select, click, but the pointer is invisible. In a dual monitor configuration, this only happened in the screen where the mouse was when it turned off. If It firs happened in one monitor and tehn I left the mouse in the other and it also turn off, mouse end up disappearing in both. My video card is an nvidia GeForce Go6150 (NV4E C51). Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773718/+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 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29
I have a variant of this problem that I can not find anywhere else: I have the same problem of black screen (white cursor not blinking in the left upper corner) when I do a lock screen! Suspend problem is also present. Computer goes down correctly after pressing suspend, but when it is supposed to wake up, I get the above described screen (NO splash screen, NO message from grub). I am not sure if I should open a new bug for this Kernel: 4.15.0-22 OS: Xubuntu bionic PC: Lenovo P51 GDriver: NVidia proprietry, Lenovo BIOS already set to NOT use CPU internal graphics Happy to provide further infos if anybody is interested. -- 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/1743094 Title: [regression] hibernation (freezes on resume) since 4.13.0-25.29 Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: After hibernating the system and than resuming it the system reboots notifying that it is resuming and than stops/freezes. The system does not respond to anything (no tty's other notifying textg are available). After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep functions as proposed. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jb 1717 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478 InstallationDate: Installed on 2017-12-10 (34 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: Acer Aspire S3-391 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-26-generic N/A linux-backports-modules-4.13.0-26-generic N/A linux-firmware 1.157.14 Tags: sylvia Uname: Linux 4.13.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/31/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Hummingbird2 dmi.board.vendor: Acer dmi.board.version: V2.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S3-391 dmi.product.version: V2.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/+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 1773718] Re: mouse ponter disappear after screen off
I didn't knew which log to attach. Already done what you asked for. I'm also attaching lspci -vnvn log ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Attachment added: "lspci -vnv" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773718/+attachment/5145369/+files/lspci-vnvn.log -- 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/1773718 Title: mouse ponter disappear after screen off Status in linux package in Ubuntu: Confirmed Bug description: With nouveau driver (doesn't happened with propietary nvidia) after screen switch off because of power management, the mouse pointer disappear. Mouse still works, you can hover, select, click, but the pointer is invisible. In a dual monitor configuration, this only happened in the screen where the mouse was when it turned off. If It firs happened in one monitor and tehn I left the mouse in the other and it also turn off, mouse end up disappearing in both. My video card is an nvidia GeForce Go6150 (NV4E C51). Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773718/+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 1773718] [NEW] mouse ponter disappear after screen off
Public bug reported: With nouveau driver (doesn't happened with propietary nvidia) after screen switch off because of power management, the mouse pointer disappear. Mouse still works, you can hover, select, click, but the pointer is invisible. In a dual monitor configuration, this only happened in the screen where the mouse was when it turned off. If It firs happened in one monitor and tehn I left the mouse in the other and it also turn off, mouse end up disappearing in both. My video card is an nvidia GeForce Go6150 (NV4E C51). Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: disappear mouse nouveau nvidia pointer ** Description changed: With nouveau driver (doesn't happened with propietary nvidia) after screen switch off because of power management, the mouse pointer disappear. Mouse still works, you can hover, select, click, but the pointer is invisible. In a dual monitor configuration, this only happened in the screen where the mouse was when it turned off. If It firs happened in one monitor and tehn I left the mouse in the other and it also turn off, mouse end up disappearing in both. My video card is an nvidia GeForce Go6150 (NV4E C51). + + Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 -- 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/1773718 Title: mouse ponter disappear after screen off Status in linux package in Ubuntu: New Bug description: With nouveau driver (doesn't happened with propietary nvidia) after screen switch off because of power management, the mouse pointer disappear. Mouse still works, you can hover, select, click, but the pointer is invisible. In a dual monitor configuration, this only happened in the screen where the mouse was when it turned off. If It firs happened in one monitor and tehn I left the mouse in the other and it also turn off, mouse end up disappearing in both. My video card is an nvidia GeForce Go6150 (NV4E C51). Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773718/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
David Perez Millan, Please run gnome-tweaks and go to: "Keyboard & Mouse" then under "Mouse Click Emulation" select "Area" that should give you a right click at the bottom right area of the touchpad. Regards, Hans -- 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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Olivier, thank you excellent work. I've mailed the upstream developers and the author of the patch of which the older version fixes things. Kai-Heng, can you perhaps do a test Ubuntu kernel build with the patch from comment 158, then other users with different (but similar) model laptops can test and hopefully confirm that this fixes things for them too. Note I don't believe that this is the proper fix, but it will be good to have confirmation that this fixes things for others too. -- 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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Olivier Fock, Thanks, so it seems that: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/base?h=v4.14-rc7=0cc2b4e5a020fc7f4d1795741c116c983e9467d7 on top of 4.17-rc8 fixes things again, that is very interesting. You may want to try a recent kernel and then do: git revert 0759e80b84e34a84e7e46e2b1adb528c83d84a47 git cherry-pick 0cc2b4e5a020fc7f4d1795741c116c983e9467d7 And see what that does (assuming this applies cleanly). At this point I think that we need to get some upstream kernel developers involved. Can you send me an email at: hdego...@redhat.com please? (I need your email address) then I will start an email discussion about this with you in the Cc. Regards, Hans -- 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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
What would also be helpful is an acpidump of your Thomson X6 as well the output of: ls -l /sys/bus/i2c/devices -- 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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Olivier Fock, Thanks for your work on this, that is some excellent detective work. Also good to know that the "incomplete report" errors are also happening in a working setup. The buttons starting to work after you updating the drivers/hid directory is expected, I have done several fixes to the hid-mt button handling, so I was already hoping that was fixed, but the other problem was blocking testing this. So now I think we need to figure out which change exactly between the 4.14-rc7 and 4.14-rc8 drivers/base directory is causing the problem. To be clear are you talking vanilla 4.14-rc7 and 4.14-rc8 here, or Ubuntu kernel builds. Looking at your diff, one thing which you could try is reverting this in your kernel / reapplying this fix from 4.14-rc8: --- a/drivers/base/regmap/regmap.c 2018-05-16 10:10:32.0 +0200 +++ b/drivers/base/regmap/regmap.c 2017-10-29 21:58:38.0 +0100 @@ -1739,7 +1739,7 @@ return -EINVAL; if (val_len % map->format.val_bytes) return -EINVAL; - if (map->max_raw_write && map->max_raw_write < val_len) + if (map->max_raw_write && map->max_raw_write > val_len) return -E2BIG; map->lock(map->lock_arg); The fix which went into your 4.14-rc8 (I don't see this in the vanilla 4.14-rc8) is obviously correct, but it could be that this is allowing some other driver to do something somewhere which is making the touchpad not work. Something else to try is to revert this commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/base?h=v4.14-rc7=0cc2b4e5a020fc7f4d1795741c116c983e9467d7 Which is in 4.17-rc7 but not in any later kernels, so your copying over of the drivers/base dir from 4.17-rc7 adds that commit and it would be interesting to see if dropping that commit from your special working kernel makes it non working again. Eventually a different version of that commit did go upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=0759e80b84e34a84e7e46e2b1adb528c83d84a47 But that is slightly different, so perhaps the original fix happens to somehow make the touchpad work. Note there is no need to try reverting this commit if changing the max_raw_write check breaks/unbreaks the touchpad, then that is likely the cause and we need to debug further from there. -- 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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
And a dmesg directly after boot with the non-working 4.14-rc7 + another one with the working 4.14-rc8 based one would also be good. -- 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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Can people with this problem please boot with: i2c_designware_core.dyndbg=+p i2c-hid.debug=1 Added to their kernel commandline and then directly after boot run: dmesg > dmesg.log And attach the generated dmesg.log file here? -- 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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+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 1769913] Re: package linux-image-4.4.0-109-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
** 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/1769913 Title: package linux-image-4.4.0-109-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: sorry, but Iḿ not very versed in ubuntu hans@hans-NUC:~$ hans@hans-NUC:~$ cat/proc/version>version.log bash: cat/proc/version: No such file or directory hans@hans-NUC:~$ sudo lspci-vnvn.log [sudo] password for hans: sudo: lspci-vnvn.log: command not found hans@hans-NUC:~$ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-109-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sat Jan 20 19:27:25 2018 ErrorMessage: subprocess new pre-installation script returned error exit status 128 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic root=UUID=97dda6f4-e126-4583-a120-80c283d0f120 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: linux Title: package linux-image-4.4.0-109-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.board.name: NUC6i3SYB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769913/+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 1769913] [NEW] package linux-image-4.4.0-109-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Public bug reported: sorry, but Iḿ not very versed in ubuntu hans@hans-NUC:~$ hans@hans-NUC:~$ cat/proc/version>version.log bash: cat/proc/version: No such file or directory hans@hans-NUC:~$ sudo lspci-vnvn.log [sudo] password for hans: sudo: lspci-vnvn.log: command not found hans@hans-NUC:~$ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-109-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sat Jan 20 19:27:25 2018 ErrorMessage: subprocess new pre-installation script returned error exit status 128 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic root=UUID=97dda6f4-e126-4583-a120-80c283d0f120 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: linux Title: package linux-image-4.4.0-109-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.board.name: NUC6i3SYB ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1769913 Title: package linux-image-4.4.0-109-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: New Bug description: sorry, but Iḿ not very versed in ubuntu hans@hans-NUC:~$ hans@hans-NUC:~$ cat/proc/version>version.log bash: cat/proc/version: No such file or directory hans@hans-NUC:~$ sudo lspci-vnvn.log [sudo] password for hans: sudo: lspci-vnvn.log: command not found hans@hans-NUC:~$ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-109-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sat Jan 20 19:27:25 2018 ErrorMessage: subprocess new pre-installation script returned error exit status 128 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic root=UUID=97dda6f4-e126-4583-a120-80c283d0f120 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: linux Title: package linux-image-4.4.0-109-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.board.name: NUC6i3SYB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769913/+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 1767971] Re: No such man page: kernel_lockdown.7
** Tags added: bionic manpage -- 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/1767971 Title: No such man page: kernel_lockdown.7 Status in linux package in Ubuntu: New Bug description: When booting in secure boot mode, the Bionic kernel emits the following message: [ 52.035055] Lockdown: Loading of unsigned modules is restricted; see man kernel_lockdown.7 But there is no such man page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767971/+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
