[Kernel-packages] [Bug 1890618] Re: [GeForce 6100 / nForce 405] Pantalla difusa o erronea
It appears only the 'nouveau' open source driver supports this GPU. The official Nvidia drivers don't support it. Your logs seem to suggest that the 'nouveau' driver is working but is connected via analog VGA, which might lead to some blurriness if not adjusted properly. Are you able to attach a photo of the problem? I also note you're in recovery mode which you must be using as a workaround. If you just want to use that as the default then you can add "nomodeset" to /etc/default/grub here: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" and then run: sudo update-grub ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1890618 Title: [GeForce 6100 / nForce 405] Pantalla difusa o erronea Status in linux package in Ubuntu: Incomplete Bug description: Es para una pc de uso en el hogar como respaldo a mis hijas que se encuentran estudiando. Se a intentando cambiando las resoluciones y continua igual. Pero si ingresamos con Gnome por la segunda opcion y al interior de esta ingresamos por la segunda opcion el trabaja muy bien no se distorsiona y mucho menos se bloquea o como podre hacer para que esta configuracion sea siempre la predeterminada. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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.6 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 09:32:29 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation C61 [GeForce 6100 nForce 405] [10de:03d1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] C61 [GeForce 6100 nForce 405] [1462:7309] InstallationDate: Installed on 2020-04-22 (105 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 001 Device 004: ID 04a9:1746 Canon, Inc. PIXMA MP280 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 002 Device 002: ID 05ab:1001 In-System Design BAYI Printer Class Support Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7309 ProcEnviron: LANGUAGE=es_CO:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CO.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=08709502-5c82-4ec8-82cd-d1d16c89ffc6 ro recovery nomodeset SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2007 dmi.bios.vendor: MS-7309 dmi.bios.version: V1.9 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7309 dmi.board.vendor: MSI dmi.board.version: 1.0 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:bvnMS-7309:bvrV1.9:bd08/31/2007:svnMSI:pnMS-7309:pvr1.0:rvnMSI:rnMS-7309:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7309 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890618/+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 1880365] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880365 Title: Dell Vostro 5391 trackpad loses functionality after sleep Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: On 18.04 and 19.10, the Dell Vostro 5391 would lose the trackpad cursor control completely, manifesting as a frozen cursor. On 20.04, it comes back from sleep as a regular mouse, but tracks motion differently and doesn't recognize any normal gestures or the right- click. Plugging a USB mouse in is a workaround, but having the trackpad: DELL096F:00 27C6:01F0 Mouse: Applying InputClass "libinput pointer catchall" work properly through sleep/wake cycles would be ideal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sun May 24 02:29:48 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-21-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed nvidia, 440.64, 5.4.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:096f] Subsystem: Dell GP108M [GeForce MX250] [1028:096f] InstallationDate: Installed on 2020-04-06 (48 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5538 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 5391 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vgubuntu--budgie-root ro mitigations=off transparent_hugepage=always SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 055C5P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/25/2020:svnDellInc.:pnVostro5391:pvr:rvnDellInc.:rn055C5P:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5391 dmi.product.sku: 096F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1880365/+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 1890618] Re: [GeForce 6100 / nForce 405] Pantalla difusa o erronea
** Summary changed: - Pantalla difusa o erronea + [GeForce 6100 / nForce 405] Pantalla difusa o erronea ** Package changed: xorg (Ubuntu) => linux (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/1890618 Title: [GeForce 6100 / nForce 405] Pantalla difusa o erronea Status in linux package in Ubuntu: New Bug description: Es para una pc de uso en el hogar como respaldo a mis hijas que se encuentran estudiando. Se a intentando cambiando las resoluciones y continua igual. Pero si ingresamos con Gnome por la segunda opcion y al interior de esta ingresamos por la segunda opcion el trabaja muy bien no se distorsiona y mucho menos se bloquea o como podre hacer para que esta configuracion sea siempre la predeterminada. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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.6 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 09:32:29 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation C61 [GeForce 6100 nForce 405] [10de:03d1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] C61 [GeForce 6100 nForce 405] [1462:7309] InstallationDate: Installed on 2020-04-22 (105 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 001 Device 004: ID 04a9:1746 Canon, Inc. PIXMA MP280 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 002 Device 002: ID 05ab:1001 In-System Design BAYI Printer Class Support Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7309 ProcEnviron: LANGUAGE=es_CO:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CO.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=08709502-5c82-4ec8-82cd-d1d16c89ffc6 ro recovery nomodeset SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2007 dmi.bios.vendor: MS-7309 dmi.bios.version: V1.9 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7309 dmi.board.vendor: MSI dmi.board.version: 1.0 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:bvnMS-7309:bvrV1.9:bd08/31/2007:svnMSI:pnMS-7309:pvr1.0:rvnMSI:rnMS-7309:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7309 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890618/+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 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
** Summary changed: - Some external 4K monitor is not working properly + No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 -- 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/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: Triaged Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1890772/+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 1880365] Re: Dell Vostro 5391 trackpad loses functionality after sleep
** Changed in: libinput (Ubuntu) Status: Expired => New ** Changed in: linux (Ubuntu) Status: Expired => 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/1880365 Title: Dell Vostro 5391 trackpad loses functionality after sleep Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: On 18.04 and 19.10, the Dell Vostro 5391 would lose the trackpad cursor control completely, manifesting as a frozen cursor. On 20.04, it comes back from sleep as a regular mouse, but tracks motion differently and doesn't recognize any normal gestures or the right- click. Plugging a USB mouse in is a workaround, but having the trackpad: DELL096F:00 27C6:01F0 Mouse: Applying InputClass "libinput pointer catchall" work properly through sleep/wake cycles would be ideal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sun May 24 02:29:48 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-21-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed nvidia, 440.64, 5.4.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:096f] Subsystem: Dell GP108M [GeForce MX250] [1028:096f] InstallationDate: Installed on 2020-04-06 (48 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5538 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 5391 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vgubuntu--budgie-root ro mitigations=off transparent_hugepage=always SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 055C5P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/25/2020:svnDellInc.:pnVostro5391:pvr:rvnDellInc.:rn055C5P:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5391 dmi.product.sku: 096F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1880365/+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 1890618] [NEW] [GeForce 6100 / nForce 405] Pantalla difusa o erronea
You have been subscribed to a public bug: Es para una pc de uso en el hogar como respaldo a mis hijas que se encuentran estudiando. Se a intentando cambiando las resoluciones y continua igual. Pero si ingresamos con Gnome por la segunda opcion y al interior de esta ingresamos por la segunda opcion el trabaja muy bien no se distorsiona y mucho menos se bloquea o como podre hacer para que esta configuracion sea siempre la predeterminada. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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.6 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 09:32:29 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation C61 [GeForce 6100 nForce 405] [10de:03d1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] C61 [GeForce 6100 nForce 405] [1462:7309] InstallationDate: Installed on 2020-04-22 (105 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 001 Device 004: ID 04a9:1746 Canon, Inc. PIXMA MP280 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 002 Device 002: ID 05ab:1001 In-System Design BAYI Printer Class Support Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7309 ProcEnviron: LANGUAGE=es_CO:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CO.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=08709502-5c82-4ec8-82cd-d1d16c89ffc6 ro recovery nomodeset SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2007 dmi.bios.vendor: MS-7309 dmi.bios.version: V1.9 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7309 dmi.board.vendor: MSI dmi.board.version: 1.0 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:bvnMS-7309:bvrV1.9:bd08/31/2007:svnMSI:pnMS-7309:pvr1.0:rvnMSI:rnMS-7309:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7309 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal possible-manual-nvidia-install ubuntu -- [GeForce 6100 / nForce 405] Pantalla difusa o erronea https://bugs.launchpad.net/bugs/1890618 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887734] Re: soc/amd/renoir: detect dmic from acpi table
** Changed in: linux-oem-5.6 (Ubuntu) Status: New => Invalid -- 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/1887734 Title: soc/amd/renoir: detect dmic from acpi table Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed 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 Committed Bug description: Groovy kernel already merged the patchset [Impact] On the amd renoir machines, there is possibility that they have no dmic from the hardware desgin, but the driver register a dmic unconditionally, to avoid it, add the dmic detection code in the driver. [Fix] Backport 3 patches from upstream. [Test Case] On the 3 Lenovo ADM renoir machines, boot the kernel with this patchset, all dmic could be detected and registered as before. Disable the dmic in the BIOS, the driver can't detect the dmic and the dmic is not registered in the driver. [Regression Risk] Low, this SRU are only specific to soc/amd/renoir, and we already tested on 3 lenovo machines, they worked as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1887734/+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 1880365] Re: Dell Vostro 5391 trackpad loses functionality after sleep
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880365 Title: Dell Vostro 5391 trackpad loses functionality after sleep Status in libinput package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: On 18.04 and 19.10, the Dell Vostro 5391 would lose the trackpad cursor control completely, manifesting as a frozen cursor. On 20.04, it comes back from sleep as a regular mouse, but tracks motion differently and doesn't recognize any normal gestures or the right- click. Plugging a USB mouse in is a workaround, but having the trackpad: DELL096F:00 27C6:01F0 Mouse: Applying InputClass "libinput pointer catchall" work properly through sleep/wake cycles would be ideal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sun May 24 02:29:48 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-21-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed nvidia, 440.64, 5.4.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:096f] Subsystem: Dell GP108M [GeForce MX250] [1028:096f] InstallationDate: Installed on 2020-04-06 (48 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5538 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 5391 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vgubuntu--budgie-root ro mitigations=off transparent_hugepage=always SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 055C5P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/25/2020:svnDellInc.:pnVostro5391:pvr:rvnDellInc.:rn055C5P:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5391 dmi.product.sku: 096F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1880365/+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 1880365] Re: Dell Vostro 5391 trackpad loses functionality after sleep
[Expired for libinput (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libinput (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880365 Title: Dell Vostro 5391 trackpad loses functionality after sleep Status in libinput package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: On 18.04 and 19.10, the Dell Vostro 5391 would lose the trackpad cursor control completely, manifesting as a frozen cursor. On 20.04, it comes back from sleep as a regular mouse, but tracks motion differently and doesn't recognize any normal gestures or the right- click. Plugging a USB mouse in is a workaround, but having the trackpad: DELL096F:00 27C6:01F0 Mouse: Applying InputClass "libinput pointer catchall" work properly through sleep/wake cycles would be ideal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sun May 24 02:29:48 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-21-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed nvidia, 440.64, 5.4.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:096f] Subsystem: Dell GP108M [GeForce MX250] [1028:096f] InstallationDate: Installed on 2020-04-06 (48 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5538 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 5391 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vgubuntu--budgie-root ro mitigations=off transparent_hugepage=always SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 055C5P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/25/2020:svnDellInc.:pnVostro5391:pvr:rvnDellInc.:rn055C5P:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5391 dmi.product.sku: 096F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1880365/+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 1861219] Re: QLogic FC paths added when issue_lip
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861219 Title: QLogic FC paths added when issue_lip Status in linux package in Ubuntu: Expired Bug description: My QLogic direct-connect SANboot host with Ubuntu Server 18.04 LTS is seeing paths added during testing. Specifically added when running the command below: echo 1 > /sys/class/fc_host/host15/issue_lip There should be four paths total but if I run the command above five times, I will see nine total paths. The server will hang and require a reboot eventually as multiple hung_task_timeout errors show up in logs. Information on HBAs below: root@ICTM1607S02H4:~# cat /sys/class/fc_host/host*/symbolic_name QLE2742 FW:v8.08.231 DVR:v10.00.00.02-k QLE2742 FW:v8.08.231 DVR:v10.00.00.02-k QLE2692 FW:v8.08.231 DVR:v10.00.00.02-k QLE2692 FW:v8.08.231 DVR:v10.00.00.02-k An example of what a volume looks like in multipath -ll after the issue_lip occurs: root@ICTM1607S02H4:~# multipath -ll 36d039ea0003ebb14009e58b1fabf dm-3 NETAPP,INF-01-00 size=160G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw |-+- policy='service-time 0' prio=50 status=active | |- 13:0:0:0 sdl 8:176 active ready running | |- 15:0:0:0 sdq 65:0 active ready running | `- 15:0:1:0 sdv 65:80 active ready running `-+- policy='service-time 0' prio=10 status=enabled |- 12:0:0:0 sdb 8:16 active ready running `- 14:0:0:0 sdc 8:32 active ready running Notice how a path is added after issue_lip. 1) version_signature.log Ubuntu 4.15.0-74.84-generic 4.15.18 2) lspci -vnvn output is in a file attached. root@ICTM1607S02H4:~# lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 root@ICTM1607S02H4:~# apt-cache policy linux-image-generic linux-image-generic: Installed: 4.15.0.74.76 Candidate: 4.15.0.74.76 Version table: *** 4.15.0.74.76 500 500 http://repomirror-ict.eng.netapp.com/ubuntu bionic-updates/main amd64 Packages 500 http://repomirror-ict.eng.netapp.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.20.23 500 500 http://repomirror-ict.eng.netapp.com/ubuntu bionic/main amd64 Packages I expected the bus reset to quickly add and remove, but it seems removal is not happening. The number of paths grow after each bus reset causing instability with the OS. I have attached logs.zip which contains four files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861219/+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 1883058] Re: post-installation script error
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883058 Title: post-installation script error Status in linux package in Ubuntu: Expired Bug description: linux-image-5.4.0-37 generic package post-installation script subprocess returned error exit status 1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883058/+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 1883127] Re: next installing kernel 4.15.0-106 an't boot
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883127 Title: next installing kernel 4.15.0-106 an't boot Status in linux package in Ubuntu: Expired Bug description: https://termbin.com/9njr kernel 4.15.0-101 does work Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883127/+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 1830151] Re: ebb: cycles_test in powerpc from ubuntu_kernel_selftests failed on B-hwe P9
Hello Desnes,
thanks for the info!
As Eoan has already reached its end-of-life, I will see if we need this patch
for other releases.
--
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/1830151
Title:
ebb: cycles_test in powerpc from ubuntu_kernel_selftests failed on
B-hwe P9
Status in ubuntu-kernel-tests:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Bug description:
This test has passed with Cosmic kernel on the same node ("baltar"),
but not with the 4.18 kernel on Bionic.
selftests: ebb: cycles_test
test: cycles
tags: git_version:unknown
EBB Handler is at 0x10004170
ebb_state:
ebb_count = 10
spurious = 0
negative = 0
no_overflow = 0
pmc[1] count = 0x2843f
pmc[2] count = 0x0
pmc[3] count = 0x0
pmc[4] count = 0x0
pmc[5] count = 0x0
pmc[6] count = 0x0
HW state:
MMCR0 0x8400 FC PMAE
MMCR2 0x
EBBHR 0x10004170
BESCR 0x8000 GE
PMC1 0x4000
PMC2 0x
PMC3 0x
PMC4 0x
PMC5 0x00028b3f
PMC6 0x0002ac80
SIAR 0x100035d4
Trace buffer dump:
address 0x71a628a2
tail 0x71a628a201f6
size 1048576
overflow false
Content:
[0]: counter = 1
[1]: register SPRN_MMCR0 = 0x8080
[2]: register SPRN_PMC1 = 0x8004
[3]: counter = 2
[4]: register SPRN_MMCR0 = 0x8080
[5]: register SPRN_PMC1 = 0x8004
[6]: counter = 3
[7]: register SPRN_MMCR0 = 0x8080
[8]: register SPRN_PMC1 = 0x8004
[FAIL] Test FAILED on line 52
[9]: counter = 4
[10]: register SPRN_MMCR0 = 0x8080
[11]: register SPRN_PMC1 = 0x8004
[12]: counter = 5
[13]: register SPRN_MMCR0 = 0x8080
[14]: register SPRN_PMC1 = 0x8004
[15]: counter = 6
[16]: register SPRN_MMCR0 = 0x8080
[17]: register SPRN_PMC1 = 0x8004
[18]: counter = 7
[19]: register SPRN_MMCR0 = 0x8080
[20]: register SPRN_PMC1 = 0x8004
[21]: counter = 8
[22]: register SPRN_MMCR0 = 0x8080
[23]: register SPRN_PMC1 = 0x8004
[24]: counter = 9
[25]: register SPRN_MMCR0 = 0x8080
[26]: register SPRN_PMC1 = 0x8004
[27]: counter = 10
[28]: register SPRN_MMCR0 = 0x8080
[29]: register SPRN_PMC1 = 0x8004
[30]: register SPRN_PMC1 = 0x4417
PMC1 count (0x2843f) above upper limit 0x283e8 (+0x57)
failure: cycles
not ok 1..3 selftests: ebb: cycles_test [FAIL]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830151/+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 1729674]
Install via: sudo fwupdmgr install ~/Downloads/WD19FirmwareUpdateLinux_01.00.14.cab -- 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/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Status in linux package in Fedora: Confirmed Bug description: It looks like TCP rx and tx checksum offloading is broken on the TB16 dock's ethernet adapter. For example downloading a large file such as the Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. This is because rx-checksumming: on tx-checksumming: on and both set to on by default. Running sudo ethtool -K tx off rx off, allows the download to complete correctly. This is very bad since this can cause very bad untrustworthy behavior. This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- generic-hwe-16.04-edge. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+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 1729674]
(In reply to Alex Grönholm from comment #47) > Thanks for the info (I own a WD19TB dock too) but that hardly helps with the > TB16 problem. The WD19 series docks have working USB controllers, unlike > TB16. It was a long night and TB16 looked like WD19 to me :) That said, I experience exactly the same issues with Dell Precision 5540 + WD19 as in comment42 and comment44. -- 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/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Status in linux package in Fedora: Confirmed Bug description: It looks like TCP rx and tx checksum offloading is broken on the TB16 dock's ethernet adapter. For example downloading a large file such as the Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. This is because rx-checksumming: on tx-checksumming: on and both set to on by default. Running sudo ethtool -K tx off rx off, allows the download to complete correctly. This is very bad since this can cause very bad untrustworthy behavior. This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- generic-hwe-16.04-edge. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+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 1729674]
Thanks for the info (I own a WD19TB dock too) but that hardly helps with the TB16 problem. The WD19 series docks have working USB controllers, unlike TB16. -- 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/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Status in linux package in Fedora: Confirmed Bug description: It looks like TCP rx and tx checksum offloading is broken on the TB16 dock's ethernet adapter. For example downloading a large file such as the Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. This is because rx-checksumming: on tx-checksumming: on and both set to on by default. Running sudo ethtool -K tx off rx off, allows the download to complete correctly. This is very bad since this can cause very bad untrustworthy behavior. This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- generic-hwe-16.04-edge. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+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 1729674]
Seeing a similar issue on a Dell XPS 9300 (2020) with Linux 5.4: [ 110.467608] xhci_hcd :08:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13 [ 110.467613] xhci_hcd :08:00.0: Looking for event-dma 00086900cfd0 trb-start 00086900cfb0 trb-end 00086900cfb0 seg-start 00086900c000 seg-end 00086900cff0 [ 110.478406] xhci_hcd :08:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13 [ 110.478412] xhci_hcd :08:00.0: Looking for event-dma 00086900cfe0 trb-start 00086900cfb0 trb-end 00086900cfb0 seg-start 00086900c000 seg-end 00086900cff0 [ 110.479937] xhci_hcd :08:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13 [ 110.479942] xhci_hcd :08:00.0: Looking for event-dma 000861c06000 trb-start 00086900cfb0 trb-end 00086900cfb0 seg-start 00086900c000 seg-end 00086900cff0 [ 110.482654] xhci_hcd :08:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13 [ 110.482660] xhci_hcd :08:00.0: Looking for event-dma 000861c06010 trb-start 00086900cfb0 trb-end 00086900cfb0 seg-start 00086900c000 seg-end 00086900cff0 [ 110.499173] xhci_hcd :08:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13 [ 110.499178] xhci_hcd :08:00.0: Looking for event-dma 000861c06020 trb-start 00086900cfb0 trb-end 00086900cfb0 seg-start 00086900c000 seg-end 00086900cff0 [ 110.505613] xhci_hcd :08:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13 [ 110.505618] xhci_hcd :08:00.0: Looking for event-dma 000861c06030 trb-start 00086900cfb0 trb-end 00086900cfb0 seg-start 00086900c000 seg-end 00086900cff0 [ 110.505676] xhci_hcd :08:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13 [ 110.505678] xhci_hcd :08:00.0: Looking for event-dma 000861c06040 trb-start 00086900cfb0 trb-end 00086900cfb0 seg-start 00086900c000 seg-end 00086900cff0 [ 110.505764] xhci_hcd :08:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13 [ 110.505766] xhci_hcd :08:00.0: Looking for event-dma 000861c06050 trb-start 00086900cfb0 trb-end 00086900cfb0 seg-start 00086900c000 seg-end 00086900cff0 [ 110.507398] xhci_hcd :08:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13 [ 110.507405] xhci_hcd :08:00.0: Looking for event-dma 000861c06060 trb-start 00086900cfb0 trb-end 00086900cfb0 seg-start 00086900c000 seg-end 00086900cff0 [ 110.509353] xhci_hcd :08:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13 [ 110.509359] xhci_hcd :08:00.0: Looking for event-dma 000861c06070 trb-start 00086900cfb0 trb-end 00086900cfb0 seg-start 00086900c000 seg-end 00086900cff0 [ 110.510017] xhci_hcd :08:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13 [ 110.510021] xhci_hcd :08:00.0: Looking for event-dma 000861c06080 trb-start 00086900cfb0 trb-end 00086900cfb0 seg-start 00086900c000 seg-end 00086900cff0 [ 110.516799] xhci_hcd :08:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13 [ 110.516806] xhci_hcd :08:00.0: Looking for event-dma 000861c06090 trb-start 00086900cfb0 trb-end 00086900cfb0 seg-start 00086900c000 seg-end 00086900cff0 [ 110.516930] xhci_hcd :08:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13 [ 110.516934] xhci_hcd :08:00.0: Looking for event-dma 000861c060a0 trb-start 00086900cfb0 trb-end 00086900cfb0 seg-start 00086900c000 seg-end 00086900cff0 [ 110.521145] xhci_hcd :08:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13 [ 110.521151] xhci_hcd :08:00.0: Looking for event-dma 000861c060b0 trb-start 00086900cfb0 trb-end 00086900cfb0 seg-start 00086900c000 seg-end 00086900cff0 [ 110.546425] xhci_hcd :08:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13 [ 110.546431] xhci_hcd :08:00.0: Looking for event-dma 000861c060c0 trb-start 00086900cfb0 trb-end 00086900cfb0 seg-start 00086900c000 seg-end 00086900cff0 [ 110.546773] xhci_hcd :08:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13 [ 110.546778] xhci_hcd :08:00.0: Looking for event-dma 000861c060d0 trb-start 00086900cfb0 trb-end 00086900cfb0 seg-start 00086900c000 seg-end 00086900cff0 [ 110.546945] xhci_hcd :08:00.0: ERROR Transfer event TRB DMA ptr not part of current TD
[Kernel-packages] [Bug 1729674]
There is Dell TB19 firmware available that is installable via fwupdmgr on Linux: https://www.dell.com/support/home/en- bm/drivers/driversdetails?driverid=cwcf9=rhl80=dell- wd19tb-dock -- 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/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Status in linux package in Fedora: Confirmed Bug description: It looks like TCP rx and tx checksum offloading is broken on the TB16 dock's ethernet adapter. For example downloading a large file such as the Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. This is because rx-checksumming: on tx-checksumming: on and both set to on by default. Running sudo ethtool -K tx off rx off, allows the download to complete correctly. This is very bad since this can cause very bad untrustworthy behavior. This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- generic-hwe-16.04-edge. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+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 1729674]
The issue is not unique to the integrated NIC in the dock (so the current workaround in r8152 is not sufficient). I have a r8152-based TP- LINK UE300 USB3-to-GigE dongle connected to my TB16 dock and I'm getting the same packet corruption when I don't turn off rx checksum offloading. usb 4-1.1.1: new SuperSpeed Gen 1 USB device number 5 using xhci_hcd usb 4-1.1.1: New USB device found, idVendor=2357, idProduct=0601, bcdDevice=30.00 usb 4-1.1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=6 usb 4-1.1.1: Product: USB 10/100/1000 LAN usb 4-1.1.1: Manufacturer: TP-LINK usb 4-1.1.1: SerialNumber: 0100 /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/7p, 5000M |__ Port 1: Dev 3, If 0, Class=Hub, Driver=hub/4p, 5000M |__ Port 1: Dev 5, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M |__ Port 4: Dev 6, If 0, Class=Hub, Driver=hub/2p, 5000M |__ Port 2: Dev 4, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M The dongle is plugged into the internal USB hub in my Dell U2715H screen, which is in turn plugged into the TB16 (latest firmware 1.0.0), connected to my XPS 15 9560 (latest BIOS 1.11.0, Linux 4.18.7-200.fc28.x86_64 at the moment). I've also seen someone mentioning that (some) USB3 ports on the TB16 are in fact Alpine Ridge pass-through. That does not seem to be the case here, all three ports on my TB16 go through the ASMedia host controller: 0e:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller The r8152 workaround triggers just fine for the integrated NIC in the dock: usb 4-1.2: reset SuperSpeed Gen 1 USB device number 4 using xhci_hcd usb 4-1.2: Dell TB16 Dock, disable RX aggregation -- 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/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Status in linux package in Fedora: Confirmed Bug description: It looks like TCP rx and tx checksum offloading is broken on the TB16 dock's ethernet adapter. For example downloading a large file such as the Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. This is because rx-checksumming: on tx-checksumming: on and both set to on by default. Running sudo ethtool -K tx off rx off, allows the download to complete correctly. This is very bad since this can cause very bad untrustworthy behavior. This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- generic-hwe-16.04-edge. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+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 1729674]
Indeed, I found the mention of the pass-through only applying to the USB-C like a minute after I wrote my previous comment. Sorry for the noise. I don't have a C-A adapter at hand, but I've tried using the Dell DA200 adapter instead (not exactly the same thing as it's an extra hub, but hopefully it helps anyway). So the topology is: Dongle -> DA200 (hub) -> USB-C port on the TB16 -> AR host controller /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M |__ Port 1: Dev 5, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M |__ Port 4: Dev 3, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M 0f:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine Ridge] This setup works fine without any corruption with all offloads on (default). -- 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/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Status in linux package in Fedora: Confirmed Bug description: It looks like TCP rx and tx checksum offloading is broken on the TB16 dock's ethernet adapter. For example downloading a large file such as the Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. This is because rx-checksumming: on tx-checksumming: on and both set to on by default. Running sudo ethtool -K tx off rx off, allows the download to complete correctly. This is very bad since this can cause very bad untrustworthy behavior. This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- generic-hwe-16.04-edge. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+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 1891062] Re: Lenovo X1 Tablet Gen3 trackpoint and buttons not working
Commit 8d5037dca7c2 is being merged from 5.1-rc1, so focal 5.4 kernel already got it. Trackpad still doesn't work right? -- 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/1891062 Title: Lenovo X1 Tablet Gen3 trackpoint and buttons not working Status in linux package in Ubuntu: Confirmed Bug description: Upon clean install of Ubuntu 20.04 LTS my trackpoint and trackpad buttons are not working. From my investigation, a patch has been applied to the 5.4.y branch (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=8d5037dca7c2089f27e5903c2aecfc5bb10d7806). I followed the steps listed in here: https://github.com/da-cali/linux-x1-tablet#fix-the-trackpoint-and-trackpad-buttons using v5.4.57, but now my GRUB has two options: * Ubuntu w/ 5.4.57+ (not working. Stuck "Loading initial ramdisk") * Ubuntu w/ 5.4.0-42-generic (working) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 12:53:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 1392 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20KJCTO1WW Package: linux (not installed) 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=/boot/vmlinuz-5.4.0-42-generic root=UUID=5187b79d-6bc7-455c-9c28-0876bcb85a3b ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 StagingDrivers: ipu3_imgu Tags: focal staging Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1ZET79W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KJCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1ZET79W(1.35):bd11/28/2019:svnLENOVO:pn20KJCTO1WW:pvrThinkPadX1TabletGen3:rvnLENOVO:rn20KJCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone: dmi.product.family: ThinkPad X1 Tablet Gen 3 dmi.product.name: 20KJCTO1WW dmi.product.sku: LENOVO_MT_20KJ_BU_Think_FM_ThinkPad X1 Tablet Gen 3 dmi.product.version: ThinkPad X1 Tablet Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891062/+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 1729674]
This seems to help for me (Dell XPS13 2-in-1 7390 , kernel 5.6.15-300.fc32.x86_64) when switching (exact chain of events undetermined) between Dell DA300 (r8152 : Tx status -71) and Dell WD19TB ThunderBolt docking adapters : https://askubuntu.com/questions/1081128/usb-3-0-ethernet-adapter-not- working-ubuntu-18-04 # echo 0bda:8153:k > /sys/module/usbcore/parameters/quirks -- 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/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Status in linux package in Fedora: Confirmed Bug description: It looks like TCP rx and tx checksum offloading is broken on the TB16 dock's ethernet adapter. For example downloading a large file such as the Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. This is because rx-checksumming: on tx-checksumming: on and both set to on by default. Running sudo ethtool -K tx off rx off, allows the download to complete correctly. This is very bad since this can cause very bad untrustworthy behavior. This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- generic-hwe-16.04-edge. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+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 1729674]
https://lkml.org/lkml/2018/8/20/42 There is a patch in upstream. Turn off the checksum offloading. -- 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/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Status in linux package in Fedora: Confirmed Bug description: It looks like TCP rx and tx checksum offloading is broken on the TB16 dock's ethernet adapter. For example downloading a large file such as the Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. This is because rx-checksumming: on tx-checksumming: on and both set to on by default. Running sudo ethtool -K tx off rx off, allows the download to complete correctly. This is very bad since this can cause very bad untrustworthy behavior. This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- generic-hwe-16.04-edge. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+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 1729674]
Our bug report from Launchpad: Hi. Large amount of data gets corrupted when using the TB16 ethernet port. (rsync synchronization, etc... ) Linux E7490 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux On my Fedora is this still an issue even with announced bugfix (link copied from this discussion #78. Linux username-localdomain 4.17.9-200.fc28.x86_64 #1 SMP Mon Jul 23 21:41:29 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux It's fixed by turning the checksum offload off (tested on the Fedora . sudo ethtool --offload enp11s0u1u2 rx off https://bugs.launchpad.net/dell-sputnik/+bug/1729674 related in bugzilla: -- 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/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Status in linux package in Fedora: Confirmed Bug description: It looks like TCP rx and tx checksum offloading is broken on the TB16 dock's ethernet adapter. For example downloading a large file such as the Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. This is because rx-checksumming: on tx-checksumming: on and both set to on by default. Running sudo ethtool -K tx off rx off, allows the download to complete correctly. This is very bad since this can cause very bad untrustworthy behavior. This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- generic-hwe-16.04-edge. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+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 1729674]
Ref. bug # 1600126 I updated r8152 to v2.11 per https://aur.archlinux.org/packages/r8152-dkms/ makes things more stable. # cd /usr/src/r8152-2.11.0 # patch -p1 <./linux-4.20.0-add-guard-fix.patch # more /usr/src/r8152-2.11.0/dkms.conf PACKAGE_NAME="r8152" PACKAGE_VERSION="2.11.0" BUILT_MODULE_NAME[0]="r8152" DEST_MODULE_LOCATION[0]="/kernel/drivers/net/usb" AUTOINSTALL="yes" # ll /var/lib/dkms/r8152/2.11.0/source lrwxrwxrwx. 1 root root 21 Mar 1 15:22 /var/lib/dkms/r8152/2.11.0/source -> /usr/src/r8152-2.11.0 # dracut -f At least my kbd is still working after 30 minutes. A record on kernels above 4.18.18-300.fc29. -- 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/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Status in linux package in Fedora: Confirmed Bug description: It looks like TCP rx and tx checksum offloading is broken on the TB16 dock's ethernet adapter. For example downloading a large file such as the Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. This is because rx-checksumming: on tx-checksumming: on and both set to on by default. Running sudo ethtool -K tx off rx off, allows the download to complete correctly. This is very bad since this can cause very bad untrustworthy behavior. This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- generic-hwe-16.04-edge. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+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 1729674]
cc -- 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/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Status in linux package in Fedora: Confirmed Bug description: It looks like TCP rx and tx checksum offloading is broken on the TB16 dock's ethernet adapter. For example downloading a large file such as the Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. This is because rx-checksumming: on tx-checksumming: on and both set to on by default. Running sudo ethtool -K tx off rx off, allows the download to complete correctly. This is very bad since this can cause very bad untrustworthy behavior. This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- generic-hwe-16.04-edge. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+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 1729674]
@Tomas, It sounds like the topology needs to be looked at then for applying this quirk. Can you connect the dongle to the USB-C port with C-A adapter? That is the AR pass through port. -- 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/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Status in linux package in Fedora: Confirmed Bug description: It looks like TCP rx and tx checksum offloading is broken on the TB16 dock's ethernet adapter. For example downloading a large file such as the Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. This is because rx-checksumming: on tx-checksumming: on and both set to on by default. Running sudo ethtool -K tx off rx off, allows the download to complete correctly. This is very bad since this can cause very bad untrustworthy behavior. This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- generic-hwe-16.04-edge. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+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 1729674]
IIRC, I tested this scenario, and I didn't observe the issue on external r8152 dongle over the ASMedia xHC host. The v1 patch I sent was using topology to check, but maintainers didn't like it. I'll see if I can come up a "better" version of it so maintainers will accept it. -- 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/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Status in linux package in Fedora: Confirmed Bug description: It looks like TCP rx and tx checksum offloading is broken on the TB16 dock's ethernet adapter. For example downloading a large file such as the Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. This is because rx-checksumming: on tx-checksumming: on and both set to on by default. Running sudo ethtool -K tx off rx off, allows the download to complete correctly. This is very bad since this can cause very bad untrustworthy behavior. This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- generic-hwe-16.04-edge. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+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 1729674]
The same issue still happens to me on kernel 5.5.6-201.fc31.x86_64 Hardware is a Dell XPS 13 9370 with a Lenovo Thunderbolt 3 dock. My dmesg is full of these messages: [12696.189484] r8152 6-1:1.0 enp10s0u1: Tx timeout [12702.333456] r8152 6-1:1.0 enp10s0u1: Tx timeout [12707.965422] r8152 6-1:1.0 enp10s0u1: Tx timeout [12713.085385] r8152 6-1:1.0 enp10s0u1: Tx timeout [12718.205360] r8152 6-1:1.0 enp10s0u1: Tx timeout [12724.349321] r8152 6-1:1.0 enp10s0u1: Tx timeout [12729.981295] r8152 6-1:1.0 enp10s0u1: Tx timeout [12735.101256] r8152 6-1:1.0 enp10s0u1: Tx timeout [12740.221235] r8152 6-1:1.0 enp10s0u1: Tx timeout [12746.365199] r8152 6-1:1.0 enp10s0u1: Tx timeout [12751.997171] r8152 6-1:1.0 enp10s0u1: Tx timeout [12757.117155] r8152 6-1:1.0 enp10s0u1: Tx timeout -- 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/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Status in linux package in Fedora: Confirmed Bug description: It looks like TCP rx and tx checksum offloading is broken on the TB16 dock's ethernet adapter. For example downloading a large file such as the Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. This is because rx-checksumming: on tx-checksumming: on and both set to on by default. Running sudo ethtool -K tx off rx off, allows the download to complete correctly. This is very bad since this can cause very bad untrustworthy behavior. This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- generic-hwe-16.04-edge. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+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 1890988] Re: Intel Ethernet Controller X7l0-AT2 can not be identified all ports in Ubuntu 20.04 (inbox driver i40e)
** Attachment added: "sosreport-AS-1124US-TNRP-2020-08-11-ixuoqqw.tar.xz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890988/+attachment/5400554/+files/sosreport-AS-1124US-TNRP-2020-08-11-ixuoqqw.tar.xz ** 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/1890988 Title: Intel Ethernet Controller X7l0-AT2 can not be identified all ports in Ubuntu 20.04 (inbox driver i40e) Status in linux package in Ubuntu: Confirmed Bug description: [Ubuntu Version] Ubuntu 20.04 LTS [Package Version] http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages release v=20.04,o=Ubuntu,a=focal,n=focal,l=Ubuntu,c=main,b=amd64 http://ppa.launchpad.net/hardware-certification/public/ubuntu focal/main amd64 Packages release v=20.04,o=LP-PPA-hardware-certification-public,a=focal,n=focal,l=Public PPA for Hardware Certification,c=main,b=amd64 [Expect Result] Intel Ethernet Controller X710-AT2 all ports can be identified under Ubuntu 20.04 via inbox driver i40e and workable normally. [Symptom] The Intel Ethernet Controller X710-AT2 has [Dual 10GBase-T and Dual 10G SFP+ LAN ports] but in Ubuntu 20.04 that cannot be identified all ports. I want to execute hardware-certification and the system only can identify dual 10G SFP+ LAN ports via inbox driver i40e. Please help clarify this issue or provide me solution Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890988/+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 1890988] Re: Intel Ethernet Controller X7l0-AT2 can not be identified all ports in Ubuntu 20.04 (inbox driver i40e)
Hi The Ubuntu 20.04 I install via MAAS server and it doesn't have GUI. I can't execute this command and it will occur error message. apport-collect 1890988 ERROR: connecting to Launchpad failed: b 'Request token has not yet been reviewed. Try again later.' You can reset the credentials by removing the file "/root/.cache/apport/launchpad.credentials" So I provide you "sosreport" for check it. Thanks for your help. -- 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/1890988 Title: Intel Ethernet Controller X7l0-AT2 can not be identified all ports in Ubuntu 20.04 (inbox driver i40e) Status in linux package in Ubuntu: Confirmed Bug description: [Ubuntu Version] Ubuntu 20.04 LTS [Package Version] http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages release v=20.04,o=Ubuntu,a=focal,n=focal,l=Ubuntu,c=main,b=amd64 http://ppa.launchpad.net/hardware-certification/public/ubuntu focal/main amd64 Packages release v=20.04,o=LP-PPA-hardware-certification-public,a=focal,n=focal,l=Public PPA for Hardware Certification,c=main,b=amd64 [Expect Result] Intel Ethernet Controller X710-AT2 all ports can be identified under Ubuntu 20.04 via inbox driver i40e and workable normally. [Symptom] The Intel Ethernet Controller X710-AT2 has [Dual 10GBase-T and Dual 10G SFP+ LAN ports] but in Ubuntu 20.04 that cannot be identified all ports. I want to execute hardware-certification and the system only can identify dual 10G SFP+ LAN ports via inbox driver i40e. Please help clarify this issue or provide me solution Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890988/+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 1812620] Re: msg_zerocopy.sh in net from ubuntu_kernel_selftests failed
The net test was skipped on all of the instances with B-gke-5.3.0-1033.35 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1812620 Title: msg_zerocopy.sh in net from ubuntu_kernel_selftests failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in linux source package in Disco: Won't Fix Status in linux-aws source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-azure source package in Eoan: Won't Fix Status in linux source package in Focal: Fix Committed Status in linux-aws source package in Focal: New Status in linux-azure source package in Focal: New Bug description: == SRU Justification [ FOCAL ] == The msg_zerocopy.sh kernel self test will fail on machines that don't have 2 or 3 CPUs such as 1 CPU cloud instances since the C test program tries to set CPU affinity to CPUs 2 and 3 and bails out if it fails. == Fix == Upstream linux-next commit commit 16f6458f2478b55e2b628797bc81a4455045c74e Author: Willem de Bruijn Date: Wed Aug 5 04:40:45 2020 -0400 selftests/net: relax cpu affinity requirement in msg_zerocopy test The fix now just emits a warning that CPU affinity can't be set rather than cause an exit(1) termination. == Test cast == Run the msg_zerocopy.sh test from the kernel net selftest on a 1 CPU system. Without the fix the test fails. With the fix it runs successfully as expected. == Regression Potential == The original test pinned the CPUs for a benchmarking metric, for our testing we are using this to test to see if the operations in the test work successfully. There is a potential that users using this test will not notice the warning if they are using this test as a benchmark on a 1 CPU system and may get more jittery timing in their benchmarks rather than a test failing and complaining they are not running it on a suitable multi-CPU system. However, the likelyhood of a user using this test on a single CPU system for benchmarking is small and as it stands the test will now run and produce potentially jittery benchmarks on a 1 CPU system compared to previously where it never ran. This test will return 1 $ sudo ./msg_zerocopy.sh ipv4 tcp -t 1 ./msg_zerocopy: setaffinity 2 ./msg_zerocopy: setaffinity 3 $ echo $? 1 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: User Name 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 21 07:41 seq crw-rw 1 root audio 116, 33 Jan 21 07:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jan 21 07:50:33 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.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/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812620/+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 1891086] Re: Xorg crash Display bug Nvidia
It sounds like gnome-shell was frozen: ago 10 22:44:55 Pitx-PC systemd[1742]: gnome-shell-x11.service: Killing process 2047 (gnome-shell) with signal SIGKILL. But maybe some useful crash also preceded that so please check /var/crash for any crash files. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-440 (Ubuntu) ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1891086 Title: Xorg crash Display bug Nvidia Status in nvidia-graphics-drivers-440 package in Ubuntu: Incomplete Bug description: Hi, I have got a Nvidia GTX 1080 Ti and when I was playing Just cause 3 (with Steam Proton) and finish the game, all looks well, but 30-60 seconds later, the system crash turning my screen in black. I couldn't watch nothing and I needed to restart the system. I attach some logs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 22:48:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-37-generic, x86_64: installed nvidia, 440.100, 5.4.0-40-generic, x86_64: installed nvidia, 440.100, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP102 [GeForce GTX 1080 Ti] [1458:3752] InstallationDate: Installed on 2020-04-24 (108 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. X470 AORUS GAMING 7 WIFI ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=de8f79b3-6f06-4293-9d8c-ed2a147342a5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: X470 AORUS GAMING 7 WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSGAMING7WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSGAMING7WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X470 AORUS GAMING 7 WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1891086/+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 1891086] [NEW] Xorg crash Display bug Nvidia
You have been subscribed to a public bug: Hi, I have got a Nvidia GTX 1080 Ti and when I was playing Just cause 3 (with Steam Proton) and finish the game, all looks well, but 30-60 seconds later, the system crash turning my screen in black. I couldn't watch nothing and I needed to restart the system. I attach some logs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 22:48:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-37-generic, x86_64: installed nvidia, 440.100, 5.4.0-40-generic, x86_64: installed nvidia, 440.100, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP102 [GeForce GTX 1080 Ti] [1458:3752] InstallationDate: Installed on 2020-04-24 (108 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. X470 AORUS GAMING 7 WIFI ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=de8f79b3-6f06-4293-9d8c-ed2a147342a5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: X470 AORUS GAMING 7 WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSGAMING7WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSGAMING7WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X470 AORUS GAMING 7 WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash focal ubuntu -- Xorg crash Display bug Nvidia https://bugs.launchpad.net/bugs/1891086 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890956] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1890956 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1890956 Title: [Gateway NE722] Mouse and keyboard stop working after suspend Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 dm3: Installed: 3.34.1-1ubuntu1 Candidate: 3.34.1-1ubuntu1 Version table: *** 3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Booting off of a live usb, the trackpad, external mouse, and internal keyboard stop responding to input after suspend. On my updated install, the laptop trackpad works, but the other two inputs do not after suspend/wake. I can log in using the on screen keyboard. Unplugging the mouse and plugging it in does not fix it. The inputs don't respond while logged in either. Only a reboot fixes it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 9 14:00:59 2020 ExecutablePath: /usr/lib/gdm3/gdm-x-session InstallationDate: Installed on 2020-06-20 (50 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1890956/+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 1890956] Re: [Gateway NE722] Mouse and keyboard stop working after suspend
Thanks. I can't find any easy explanation in that log... I suggest the next thing to try is the latest kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8/amd64/ which is probably the component most likely at fault here. ** Summary changed: - Mouse and keyboard stop working after suspend + [Gateway NE722] Mouse and keyboard stop working after suspend ** Changed in: libinput (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: xserver-xorg-input-libinput (Ubuntu) Status: Incomplete => 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/1890956 Title: [Gateway NE722] Mouse and keyboard stop working after suspend Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 dm3: Installed: 3.34.1-1ubuntu1 Candidate: 3.34.1-1ubuntu1 Version table: *** 3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Booting off of a live usb, the trackpad, external mouse, and internal keyboard stop responding to input after suspend. On my updated install, the laptop trackpad works, but the other two inputs do not after suspend/wake. I can log in using the on screen keyboard. Unplugging the mouse and plugging it in does not fix it. The inputs don't respond while logged in either. Only a reboot fixes it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 9 14:00:59 2020 ExecutablePath: /usr/lib/gdm3/gdm-x-session InstallationDate: Installed on 2020-06-20 (50 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1890956/+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 1877757] Re: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1877757 Title: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU Status in linux package in Ubuntu: Confirmed 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: In Progress Bug description: [Impact] On this machine, after booting up, there is no valid sound card, the gnome-control-center shows a dummy output only. check the dmesg, the alsa sof driver fails to initialize. [Fix] Backport a patch from upstream, after applying this patch, the sof driver will not fail anymore even the codec driver is hda_generic [Test Case] A couple of users already test this patch on their machines, after booting up, there is a valid sound card, and could output sound from output devices. [Regression Risk] Low, this is cherry-picked from upstream, and this just adds a new kind of codec (generic) support, and a couple of ubuntu users already verified this patch. New focal installation on a new Acer Swift 3 laptop with core i7-1065G7. No sound detected, KDE/pavucontrol shows Dummy output. External headset also not detected. I've googled around and tried to reinstall alsa and pulseaudio, tried alsa force-reload as well. Nothing helps. With snd_hda_intel.dmic_detect=0 speakers start working but microphone is not detected. External headset detected with both headphones and mic. I use this as a workaround for a time being. I've checked https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697 bug. It is closed and use recent kernel and firmware but it does not fix my issue. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 18:56:15 2020 InstallationDate: Installed on 2020-04-24 (15 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Swift SF314-57G ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=faf6a132-de60-44fa-a1a7-4cce8ef83b87 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: 09/24/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Floris_IL dmi.board.vendor: IL dmi.board.version: V1.09 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd09/24/2019:svnAcer:pnSwiftSF314-57G:pvrV1.09:rvnIL:rnFloris_IL:rvrV1.09:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-57G dmi.product.sku: dmi.product.version: V1.09 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877757/+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 1890220] Re: ASoC:amd:renoir: the dmic can't record sound after suspend and resume
Boot with the -proposed kernel on the lenovo amd renoir machine, open the gnome-sound-setting, let the dmic work, then suspend and resume, check the dmic, it still works. Verified done with the focal kernel. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1890220 Title: ASoC:amd:renoir: the dmic can't record sound after suspend and resume Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Triaged Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Triaged Bug description: [Impact] We have backported the amd renoir audio driver to oem-5.6 and focal kernel, recently we found if the dmic is working and we suspend and resume, the dmic can't record the sound after resume. [Fix] After resuming, the driver needs to restore 2 more registers, then the dmic could record the sound. [Test Case] Boot the kernel with this patch, open the sound-setting and run suspend and resume, then use arecord to record the sound, verify the sound is successfully recorded by aplaying it. [Regression Risk] Low, this patch is verified on the amd renoir machine, and this patch got ack from AMD engineer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890220/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
I am now working on this issue. I can confirm the solution provided by https://www.cnblogs.com/mikeguan/p/13126497.html works. What the solution does is, - blacklist hid_multitouch - Add the vendor id and product id of this touchpad device to hid_device_id in drivers/hid/hid-rmi.c I've posted the patch to https://github.com/coiby/linux/commit/cca37387d87a874824040c946f43cecce2679d70. You needn't to re-build the whole kernel to test if it works. You simple build the hid_rmi module and load it with insmod. But this is not an perfect solution. I'm now working on a solution that doesn't need to blacklist hid_multitouch. I've figured out how hid- core.c let the hid_multitouch driver handle this device. -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
it seems not yet... :( -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME
[Kernel-packages] [Bug 1891100] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1891100 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1891100 Title: hp notebook 15-da0001nk sound mute led not working Status in linux package in Ubuntu: Incomplete Bug description: I install Ubuntu 20.04 with kernel 5.4 on my new HP Notebook - 15-da0001nk , the system run flawlessly except the Sound Mute LED on the F6 key. I try many solution after a humble search on the net but without success. The output of pactl list sinks/lscpi is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891100/+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 1891100] [NEW] hp notebook 15-da0001nk sound mute led not working
Public bug reported: I install Ubuntu 20.04 with kernel 5.4 on my new HP Notebook - 15-da0001nk , the system run flawlessly except the Sound Mute LED on the F6 key. I try many solution after a humble search on the net but without success. The output of pactl list sinks/lscpi is attached. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "HP Notebook - 15-da0001nk Mute led not working.txt" https://bugs.launchpad.net/bugs/1891100/+attachment/5400545/+files/HP%20Notebook%20-%2015-da0001nk%20Mute%20led%20not%20working.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891100 Title: hp notebook 15-da0001nk sound mute led not working Status in linux package in Ubuntu: New Bug description: I install Ubuntu 20.04 with kernel 5.4 on my new HP Notebook - 15-da0001nk , the system run flawlessly except the Sound Mute LED on the F6 key. I try many solution after a humble search on the net but without success. The output of pactl list sinks/lscpi is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891100/+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 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward
Attached is a rebased debdiff for util-linux, which implements the permission changes to the dmesg binary. ** Patch removed: "util-linux debdiff for Groovy" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886112/+attachment/5395389/+files/lp1886112_util-linux_groovy.debdiff ** Patch added: "util-linux debdiff for Groovy" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886112/+attachment/5400541/+files/lp1886112_util-linux_groovy.debdiff -- 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/1886112 Title: Enabling DMESG_RESTRICT in Groovy Onward Status in linux package in Ubuntu: Fix Committed Status in procps package in Ubuntu: In Progress Status in util-linux package in Ubuntu: In Progress Status in linux source package in Groovy: Fix Committed Status in procps source package in Groovy: In Progress Status in util-linux source package in Groovy: In Progress Bug description: [Impact] This bug implements the enablement of CONFIG_SECURITY_DMESG_RESTRICT feature by default for Groovy onward, proposed to ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html The kernel log buffer contains a wealth of sensitive information, such as detailed call traces and kernel addresses found in register dumps in kernel oops messages. Exploit developers and attackers can leverage these information leaks to get past KASLR, and they can use the kernel log buffer to get instant feedback on their privilege escalation attacks, as failures will be shown as further oops messages, which attackers can use to fix and tune their programs until they work. Currently, if I create a new, unprivileged user on a Focal system, they cannot access /var/log/kern.log, /var/log/syslog or see system events in journalctl. But yet, they are given free reign to the kernel log buffer. $ sudo adduser dave $ su dave $ groups dave $ cat /var/log/kern.log cat: /var/log/kern.log: Permission denied $ cat /var/log/syslog cat: /var/log/syslog: Permission denied $ journalctl Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Jun 16 23:44:59 ubuntu systemd[2328]: Reached target Main User Target. Jun 16 23:44:59 ubuntu systemd[2328]: Startup finished in 69ms. $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... I propose that we restrict access to dmesg to users in group 'adm' like so: 1) Add kernel.dmesg_restrict = 1 to /etc/sysctl.d/10-kernel-hardening.conf 2) Following changes to /bin/dmesg permissions in package 'util-linux' - Ownership changes to root:adm - Permissions changed to 0750 (-rwxr-x---) - Add cap_syslog capability to binary. For most users, they will use the initial admin account, which is in the 'adm' group already, and will see no impact to these changes. If a log scraper type program needs access to dmesg, the user the daemon runs as can simply be added to the 'adm' group. [Testcase] Currently, all users can run /usr/bin/dmesg to view the kernel log buffer: $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... When the changes are applied, the default admin user will be able to view dmesg (since they are in group 'adm'), while new unprivileged users will not. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1886112-test $ whoami ubuntu $ groups ubuntu adm cdrom sudo dip plugdev $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... $ sudo adduser dave $ su dave $ groups dave $ dmesg -bash: /usr/bin/dmesg: Permission denied [Regression Potential] Some users or log scraper type programs may need to view the kernel log buffer, or have access to dmesg. In this case, the underlying service user would need to be added to the 'adm' group. Users have the ability to disable
[Kernel-packages] [Bug 1226855] Re: Cannot use open-iscsi inside LXC container
Adding Bootstack to watch this bug, as we are taking ownership of charm- iscsi-connector which would be ideal to test within lxd confinement, but requires VM or metal for functional tests. -- 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/1226855 Title: Cannot use open-iscsi inside LXC container Status in linux package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Confirmed Bug description: Trying to use open-iscsi from within an LXC container, but the iscsi netlink socket does not support multiple namespaces, causing: "iscsid: sendmsg: bug? ctrl_fd 6" error and failure. Command attempted: iscsiadm -m node -p $ip:$port -T $target --login Results in: Exit code: 18 Stdout: 'Logging in to [iface: default, target: $target, portal: $ip,$port] (multiple)' Stderr: 'iscsiadm: got read error (0/0), daemon died? iscsiadm: Could not login to [iface: default, target: $target, portal: $ip,$port]. iscsiadm: initiator reported error (18 - could not communicate to iscsid) iscsiadm: Could not log into all portals' ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lxc 0.9.0-0ubuntu3.4 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Tue Sep 17 14:38:08 2013 InstallationDate: Installed on 2013-01-15 (245 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: lxc UpgradeStatus: Upgraded to raring on 2013-05-16 (124 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1226855/+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 1885271] Re: kernel oops xr-usb-serial
** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885271 Title: kernel oops xr-usb-serial Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: # Steps to reproduce # Working case uname -a Linux ubuntu 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:09:48 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsusb -d 04e2:1411 -v > xr-usb-serial-devices.txt lsusb -t >> xr-usb-serial-devices.txt # Unbind 2 xr-usb-serial devices echo '3-14.1' | tee /sys/bus/usb/drivers/usb/unbind echo '3-14.3' | tee /sys/bus/usb/drivers/usb/unbind dmesg > dmesg.txt # Non working case uname -a Linux ubuntu 4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsusb -d 04e2:1411 -v > xr-usb-serial-devices.txt dmesg > dmesg.txt This regression is almost certainly caused by one of the 2020-03-11 commits: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/log/ubuntu/xr-usb-serial?h=Ubuntu-4.15.0-99.100=5966ed54d467fa77e7dbd7355177a5a6d1db7004 files attached in tar file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885271/+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 1856433] Re: do_IRQ: 1.55 No irq handler for vector
AGESA V2 1.0.0.2 introduced this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856433 Title: do_IRQ: 1.55 No irq handler for vector Status in linux package in Ubuntu: Confirmed Bug description: 1) Ubuntu 19.10 2) system 3) no error. 4) Error in log app. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: htpc 9157 F pulseaudio /dev/snd/controlC1: htpc 9157 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-28 (48 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lxcbr0no wireless extensions. lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA780G-UD3H Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=0fa008d8-2279-4e78-9043-161b7f514243 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: Tags: wayland-session eoan Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/13/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6b dmi.board.name: GA-MA780G-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6b:bd07/13/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA780G-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA780G-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA780G-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856433/+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 1891062] Re: Lenovo X1 Tablet Gen3 trackpoint and buttons not working
I've updated my kernel to mainline 5.8.0 using https://github.com/pimlie /ubuntu-mainline-kernel.sh, but the trackpoint and trackpad buttons are still not working. -- 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/1891062 Title: Lenovo X1 Tablet Gen3 trackpoint and buttons not working Status in linux package in Ubuntu: Confirmed Bug description: Upon clean install of Ubuntu 20.04 LTS my trackpoint and trackpad buttons are not working. From my investigation, a patch has been applied to the 5.4.y branch (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=8d5037dca7c2089f27e5903c2aecfc5bb10d7806). I followed the steps listed in here: https://github.com/da-cali/linux-x1-tablet#fix-the-trackpoint-and-trackpad-buttons using v5.4.57, but now my GRUB has two options: * Ubuntu w/ 5.4.57+ (not working. Stuck "Loading initial ramdisk") * Ubuntu w/ 5.4.0-42-generic (working) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 12:53:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 1392 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20KJCTO1WW Package: linux (not installed) 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=/boot/vmlinuz-5.4.0-42-generic root=UUID=5187b79d-6bc7-455c-9c28-0876bcb85a3b ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 StagingDrivers: ipu3_imgu Tags: focal staging Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1ZET79W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KJCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1ZET79W(1.35):bd11/28/2019:svnLENOVO:pn20KJCTO1WW:pvrThinkPadX1TabletGen3:rvnLENOVO:rn20KJCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone: dmi.product.family: ThinkPad X1 Tablet Gen 3 dmi.product.name: 20KJCTO1WW dmi.product.sku: LENOVO_MT_20KJ_BU_Think_FM_ThinkPad X1 Tablet Gen 3 dmi.product.version: ThinkPad X1 Tablet Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891062/+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'
@Tomaž: No idea. Sorry. -- 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 1890796] Re: ipsec: policy priority management is broken
** Changed in: linux (Ubuntu Focal)
Status: Triaged => Fix Committed
** Changed in: linux-hwe (Ubuntu Bionic)
Status: Triaged => Fix Committed
--
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/1890796
Title:
ipsec: policy priority management is broken
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Triaged
Status in linux-hwe source package in Xenial:
Invalid
Status in linux source package in Bionic:
Triaged
Status in linux-hwe source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux-hwe source package in Focal:
Invalid
Bug description:
[Impact]
When the user tries to update the priority field of a SP, the SP is
not updated *AND* a new SP is created. This results to a broken IPsec
configuration.
This problem has been fixed in the upstream commit 4f47e8ab6ab7 ("xfrm:
policy: match with both mark and mask on user interfaces"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4f47e8ab6ab7
[Test Case]
root@dut-vm:~# uname -a
Linux dut-vm 5.4.0-42-generic #46~18.04.1-Ubuntu SMP Fri Jul 10 07:21:24 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
root@dut-vm:~# ip xfrm policy flush
root@dut-vm:~# ip xfrm policy
root@dut-vm:~# ip xfrm policy add src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp dir
in action allow priority 9 tmpl src 3.3.3.3 dst 4.4.4.4 proto esp mode tunnel
reqid 1
root@dut-vm:~# ip xfrm policy
src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp
dir in priority 9
tmpl src 3.3.3.3 dst 4.4.4.4
proto esp reqid 1 mode tunnel
root@dut-vm:~# ip xfrm policy update src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp
dir in priority 5 tmpl src 3.3.3.3 dst 4.4.4.4 proto esp mode tunnel reqid 1
root@dut-vm:~# ip xfrm policy
src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp
dir in priority 5
tmpl src 3.3.3.3 dst 4.4.4.4
proto esp reqid 1 mode tunnel
src 1.1.1.1/24 dst 2.2.2.2/24 proto tcp
dir in priority 9
tmpl src 3.3.3.3 dst 4.4.4.4
proto esp reqid 1 mode tunnel
root@dut-vm:~#
=> Now, there is 2 SP instead of 1.
[Regression Potential]
The patch affects the xfrm stack only. Thus, the potential regressions
are limited to this area.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890796/+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 1873677] Re: Lenovo Ideapad S145 - Touchpad not recognized at all
*** This bug is a duplicate of bug 1885573 *** https://bugs.launchpad.net/bugs/1885573 It is working now! Using kernel 5.4.0-42-generic and adding the "i8042.nopnp=1 pci=nocrs" kernel parameters to grub made the touchpad work. (I also tried the solution proposed by Ferenc in Bug #1861610. It didn't work, but I cannot be sure if only using the kernel parameter works, so if it doesn't look there). ** Description changed: Touchpad not working and does not show in /proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: hockenberry 1405 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: hockenberry 1405 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 18:55:43 2020 InstallationDate: Installed on 2020-04-14 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 046d:c542 Logitech, Inc. Wireless Receiver - Bus 001 Device 002: ID 13d3:5a08 IMC Networks Integrated Camera - Bus 001 Device 004: ID 8087:0aaa Intel Corp. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 046d:c542 Logitech, Inc. Wireless Receiver + Bus 001 Device 002: ID 13d3:5a08 IMC Networks Integrated Camera + Bus 001 Device 004: ID 8087:0aaa Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81W8 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + 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-24-generic root=UUID=13de703e-a708-4fe2-a00d-136215c4176a ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.4.0-24-generic N/A - linux-backports-modules-5.4.0-24-generic N/A - linux-firmware1.187 + linux-restricted-modules-5.4.0-24-generic N/A + linux-backports-modules-5.4.0-24-generic N/A + linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN24WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN24WW:bd11/26/2019:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO -- 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/1873677 Title: Lenovo Ideapad S145 - Touchpad not recognized at all Status in linux package in Ubuntu: Confirmed Bug description: Touchpad not working and does not show in /proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hockenberry 1405 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 18:55:43 2020 InstallationDate: Installed on 2020-04-14 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c542 Logitech, Inc. Wireless Receiver Bus 001 Device 002: ID 13d3:5a08 IMC Networks Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81W8 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-24-generic root=UUID=13de703e-a708-4fe2-a00d-136215c4176a ro quiet splash
[Kernel-packages] [Bug 1877757] Re: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU
I've tested the kernel from focal-proposed Linux swift 5.4.0-43-generic #47-Ubuntu SMP Sat Aug 8 06:34:35 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Sound works perfectly! -- 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/1877757 Title: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU Status in linux package in Ubuntu: Confirmed 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: In Progress Bug description: [Impact] On this machine, after booting up, there is no valid sound card, the gnome-control-center shows a dummy output only. check the dmesg, the alsa sof driver fails to initialize. [Fix] Backport a patch from upstream, after applying this patch, the sof driver will not fail anymore even the codec driver is hda_generic [Test Case] A couple of users already test this patch on their machines, after booting up, there is a valid sound card, and could output sound from output devices. [Regression Risk] Low, this is cherry-picked from upstream, and this just adds a new kind of codec (generic) support, and a couple of ubuntu users already verified this patch. New focal installation on a new Acer Swift 3 laptop with core i7-1065G7. No sound detected, KDE/pavucontrol shows Dummy output. External headset also not detected. I've googled around and tried to reinstall alsa and pulseaudio, tried alsa force-reload as well. Nothing helps. With snd_hda_intel.dmic_detect=0 speakers start working but microphone is not detected. External headset detected with both headphones and mic. I use this as a workaround for a time being. I've checked https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697 bug. It is closed and use recent kernel and firmware but it does not fix my issue. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 18:56:15 2020 InstallationDate: Installed on 2020-04-24 (15 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Swift SF314-57G ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=faf6a132-de60-44fa-a1a7-4cce8ef83b87 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: 09/24/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Floris_IL dmi.board.vendor: IL dmi.board.version: V1.09 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd09/24/2019:svnAcer:pnSwiftSF314-57G:pvrV1.09:rvnIL:rnFloris_IL:rvrV1.09:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-57G dmi.product.sku: dmi.product.version: V1.09 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877757/+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 1859873] Re: Reapply "usb: handle warm-reset port requests on hub resume"
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859873 Title: Reapply "usb: handle warm-reset port requests on hub resume" Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Bug description: BugLink: https://bugs.launchpad.net/bugs/1859873 [Impact] We wish to reapply "usb: handle warm-reset port requests on hub resume". We reverted "usb: handle warm-reset port requests on hub resume" from the Ubuntu kernels due to a perceived regression it introduced (bug 1856608). Only one customer saw this regression, and only in very specific systems. We have now determined that the root cause of the regression was that the systems used defective USB cables, which had Tx and Rx lines mixed up. Signals were being sent down the wrong wires, placing the USB devices into a SS_INVALID link state, and this patch simply revealed the problems going on in the USB3 subsystem. USB3 devices never worked with these cables, but for some reason USB2 worked, which led to the long drawn out debugging timeframe. We have confirmation from device hardware teams that USB cables on affected systems have their Tx and Rx wires mixed up, and this has also been confirmed by the USB cable manufacturer that these cables are a bad batch. New USB cables fix the problem, and "usb: handle warm-reset port requests on hub resume" is safe to reapply. [Fix] We reapply upstream commit: commit 4fdc1790e6a9ef22399c6bc6e63b80f4609f3b7e Author: Jan-Marek Glogowski Date: Fri Feb 1 13:52:31 2019 +0100 Subject: usb: handle warm-reset port requests on hub resume To the Bionic and Eoan kernels. This commit fixes a real problem for users of a particular external hard disk, so it has value for Ubuntu users, and we do not want to diverge from upstream stable patches. [Testcase] For users with defective non-complaint USB cables: dmesg | grep "Cannot enable" For users with a particular USB-C external hard disk: The disk will work as expected when it is plugged in. [Regression Potential] If any users in the community happen to use USB cables with Tx and Rx lines mixed up, they may see messages like: "usb usb2-port2: Cannot enable. Maybe the USB cable is bad?" These users need to swap out their USB cables for a non-defective one. The commit landed in 5.1, and was backported to all stable kernels. As of 5.8-rc6, the commit is still in place, and has no fixup commits. I believe that re-introducing this commit will not cause any regressions for users with USB compliant hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859873/+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 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1856387
Title:
Freezing on boot since kernel 4.15.0-72-generic release
Status in linux package in Ubuntu:
Invalid
Status in linux-oem package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in linux-oem source package in Bionic:
Fix Released
Bug description:
[SRU Justification]
[Impact]
In bug 1840239, HPET is disabled on some systems for they caused TSC
being marked unstable while it is not. This caused an regression as bug
1851216 that some systems may then hang at early, so a fix cherry picked
back from v5.3-rc1. However, this fix also introduce yet another
regression that some other users may hang at boot while PIT is diabled
in the previous fix.
[Fix]
Commit 979923871f69 ("x86/timer: Don't skip PIT setup when APIC is
disabled or in legacy mode") from v5.6-rc1, also backported to v5.4.19
and v5.5.3, fixes PIT setup in this case.
[Test Case]
Simply boot a patch kernel on systems affected and it shouldn't hang.
[Regression Potential]
Low. Stable patch and trivial backport.
[Other Info]
The same fix for bug 1851216 was also backported to Disco and Eoan, but
they were then fixed with this 979923871f69 commit backported in bug
1866858 and bug 1867051, which pulls v5.4 stable patches into Disco and
Eoan correspondingly, leaving B/OEM-B the only victims so far.
== Original Bug Description ==
After the update to install kernel 4.15.0-72-generic (a bit over a week ago)
my computer will not boot. On boot, all I see is the purple screen with:
Loading Linux 4.15.0-72-generic ...
Loading initial ramdisk ...
and nothing happens. Just sits there. I've waited about 5-10 minutes on
occasion but to no avail.
I've checked a number of logs in /var/log but not found anything.
If I go into the advanced options and select kernel
4.15.0-70-generic, the computer boots normally.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-72-generic 4.15.0-72.81
ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
Uname: Linux 4.15.0-70-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tony 1977 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec 14 21:53:14 2019
HibernationDevice: RESUME=UUID=5475ce25-e091-45e2-9811-9b5cddc08dd1
InstallationDate: Installed on 2018-09-16 (454 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd
Bus 001 Device 002: ID 046d:c063 Logitech, Inc. DELL Laser Mouse
Bus 001 Device 004: ID 8087:0aaa Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: GIGABYTE Sabre 17WV8
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic
root=UUID=9455257c-d3b7-4d61-853d-ab0b0ee40013 ro acpi=off
RelatedPackageVersions:
linux-restricted-modules-4.15.0-70-generic N/A
linux-backports-modules-4.15.0-70-generic N/A
linux-firmware 1.173.13
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/22/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F05
dmi.board.asset.tag: Tag 12345
dmi.board.name: Sabre 17WV8
dmi.board.vendor: GIGABYTE
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: GIGABYTE
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF05:bd05/22/2018:svnGIGABYTE:pnSabre17WV8:pvrNotApplicable:rvnGIGABYTE:rnSabre17WV8:rvrNotApplicable:cvnGIGABYTE:ct10:cvrN/A:
dmi.product.family: Sabre
dmi.product.name: Sabre 17WV8
dmi.product.version: Not Applicable
dmi.sys.vendor: GIGABYTE
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to :
[Kernel-packages] [Bug 1859756] Re: [hns3-0115] add 8 BD limit for tx flow
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859756 Title: [hns3-0115] add 8 BD limit for tx flow Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04 series: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: [Impact] We get reports that iscsi and spark tests fail on hns3 [Fix] Cherry-pick/backport patches from upstream. net: hns3: add 8 BD limit for tx flow net: hns3: avoid mult + div op in critical data path net: hns3: remove some ops in struct hns3_nic_ops net: hns3: fix for not calculating tx bd num correctly net: hns3: unify maybe_stop_tx for TSO and non-TSO case net: hns3: add check for max TX BD num for tso and non-tso case net: hns3: fix for TX queue not restarted problem net: hns3: fix a use after free problem in hns3_nic_maybe_stop_tx() [Test] No known way to reproduce it in our lab. Regression test only. [Regression Potential] Patchset only affects hns3 driver. Minimal risk for other drivers and platform. [Bug Description] A single transmit packet can span up to 8 descriptors, TSO transmit packet can be stored up to 63 descriptors and each segment within the TSO should be spanned up to 8 descriptors. If the packet needs more than 8 BD, and the total size of every 7 continuous frags more than MSS, HW does not support it, and it need driver makes SKB Linearized. [Actual Results] iscsi and bigdata spark test OK [Expected Results] iscsi and bigdata spark test OK [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA DTS2018091810050 [Resolution] SW use skb_copy to merge frag; 51e8439f3496 net: hns3: add 8 BD limit for tx flow 5f543a54eec0 net: hns3: fix for not calculating tx bd num correctly To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859756/+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 1882039] Re: The thread level parallelism would be a bottleneck when searching for the shared pmd by using hugetlbfs
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882039 Title: The thread level parallelism would be a bottleneck when searching for the shared pmd by using hugetlbfs Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Committed Bug description: [Impact] There is performance overhead observed when many threads are using hugetlbfs in the database environment. [Fix] bdfbd98bc018 hugetlbfs: take read_lock on i_mmap for PMD sharing The patch improves the locking by using the read lock instead of the write lock. And it allows multiple threads searching the suitable shared VMA. As there is no modification inside the searching process. The improvement increases the parallelism and decreases the waiting time of the other threads. [Test] The customer stand-up a database with seed data. Then they have a loading "driver" which makes a bunch of connections that look like user workflows from the database perspective. Finally, the measuring response times improvement can be observed for these "users" as well as various other metrics at the database level. [Regression Potential] The modification is only in replacing the write lock to a read one. And there is no modification inside the loop. The regression probability is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882039/+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 1884766] Re: use-after-free in af_alg_accept() due to bh_lock_sock()
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884766
Title:
use-after-free in af_alg_accept() due to bh_lock_sock()
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Eoan:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Won't Fix
Bug description:
[Impact]
* Users of the Linux kernel's crypto userspace API
reported BUG() / kernel NULL pointer dereference
errors after kernel upgrades.
* The stack trace signature is an accept() syscall
going through af_alg_accept() and hitting errors
usually in one of:
- apparmor_sk_clone_security()
- apparmor_sock_graft()
- release_sock()
[Fix]
* This is a regression introduced by upstream commit
37f96694cf73 ("crypto: af_alg - Use bh_lock_sock
in sk_destruct") which made its way through stable.
* The offending patch allows the critical regions
of af_alg_accept() and af_alg_release_parent() to
run concurrently; now with the "right" events on 2
CPUs it might drop the non-atomic reference counter
of the alg_sock then the sock, thus release a sock
that is still in use.
* The fix is upstream commit 34c86f4c4a7b ("crypto:
af_alg - fix use-after-free in af_alg_accept() due
to bh_lock_sock()") [1]. It changes alg_sock's ref
counter to atomic, which addresses the root cause.
[Test Case]
* There is a synthetic test case available, which
uses a kprobes kernel module to synchronize the
concurrent CPUs on the instructions responsible
for the problem; and a userspace part to run it.
* The organic reproducer is the Varnish Cache Plus
software with the Crypto vmod (which uses kernel
crypto userspace API) under long, very high load.
* The patch has been verified on both reproducers
with the 4.15 and 5.7 kernels.
* More tests performed with 'stress-ng --af-alg'
with 11 CPUs on Xenial/Bionic/Disco/Eoan/Focal
(all on same version of stress-ng, V0.11.14)
No regressions observed from original kernel.
(the af-alg stressor can exercise almost all
kernel crypto modules shipped with the kernel;
so it checks more paths/crypto alg interfaces.)
[Regression Potential]
* The fix patch does a fundamental change in how
alg_sock reference counters work, plus another
change to the 'nokey' counting. This of course
*has* a risk of regression.
* Regressions theoretically could manifest as use
after free errors (in case of undercounting) in
the af_alg functions or silent memory leaks (in
case of overcounting), but also other behaviors
since reference counting is key to many things.
* FWIW, this patch has been written by the crypto
subsystem maintainer, who certainly knows a lot
of the normal and corner cases, thus giving the
patch more credit.
* Testing with the organic reproducer ran as long
as 5 days, without issues, so it does look good.
[Other Info]
* Not sending for Groovy (should get via Unstable).
* [1] Patch:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=34c86f4c4a7be3b3e35aa48bd18299d4c756064d
[Stack Trace Examples]
Examples:
BUG: unable to handle kernel NULL pointer dereference at
...
RIP: 0010:apparmor_sk_clone_security+0x26/0x70
...
Call Trace:
security_sk_clone+0x33/0x50
af_alg_accept+0x81/0x1c0 [af_alg]
alg_accept+0x15/0x20 [af_alg]
SYSC_accept4+0xff/0x210
SyS_accept+0x10/0x20
do_syscall_64+0x73/0x130
entry_SYSCALL_64_after_hwframe+0x3d/0xa2
general protection fault: [#1] SMP PTI
...
RIP: 0010:__release_sock+0x54/0xe0
...
Call Trace:
release_sock+0x30/0xa0
af_alg_accept+0x122/0x1c0 [af_alg]
alg_accept+0x15/0x20 [af_alg]
SYSC_accept4+0xff/0x210
SyS_accept+0x10/0x20
do_syscall_64+0x73/0x130
entry_SYSCALL_64_after_hwframe+0x3d/0xa2
To manage
[Kernel-packages] [Bug 1882478] Re: smpboot: don't call topology_sane() when Sub-NUMA-Clustering is enabled
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882478 Title: smpboot: don't call topology_sane() when Sub-NUMA-Clustering is enabled Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1882478 [Impact] Intel Skylake server processors and onward have a different Last Level Cache (LLC) topology than earlier processors, and such processors have a new feature called Sub-NUMA-Clustering (SNC) which is similar to the existing Cluster-On-Die (CoD) feature earlier server processors has. Sub-NUMA-Clustering divides the system into two "slices", each of which are allocated half the CPU cores, half the Last Level Cache and one memory controller. Each slice is enumerated as a NUMA node. The difference between Sub-NUMA-Clustering and Cluster-On-Die is how the Last Level Cache is exposed to each NUMA node. CoD had the same cache line present in each half of the LLC. In SNC, each cache line is only present in its respective slice. Because of this, the semantics around accessing LLC changes, with a process accessing NUMA-local memory only seeing half the LLC capacity. On systems with Sub-NUMA-Clustering enabled, on the Xenial 4.4 and Bionic 4.15 kernels we see the following oops during NUMA node enumeration: node #0, CPUs: #1 #2 #3 #4 #5 #6 node #1, CPUs: #7 sched: CPU #7's llc-sibling CPU #0 is not on the same node! [node: 1 != 0]. Ignoring dependency. WARNING: CPU: 7 PID: 0 at /build/linux-hwe-F5opqf/linux-hwe-4.15.0/arch/x86/kernel/smpboot.c:375 topology_sane.isra.4+0x6c/0x70 Modules linked in: CPU: 7 PID: 0 Comm: swapper/7 Not tainted 4.15.0-47-generic #50~16.04.1-Ubuntu Hardware name: HPE ProLiant DL360 Gen10/ProLiant DL360 Gen10, BIOS U32 10/02/2018 RIP: 0010:topology_sane.isra.4+0x6c/0x70 Call Trace: set_cpu_sibling_map+0x153/0x540 start_secondary+0xb2/0x200 secondary_startup_64+0xa5/0xb0 #8 #9 #10 #11 #12 #13 node #0, CPUs: #14 #15 #16 #17 #18 #19 #20 node #1, CPUs: #21 #22 #23 #24 #25 #26 #27 smp: Brought up 2 nodes, 28 CPUs This was with a Intel Xeon Gold 5120 CPU on a HP DL360 Gen10. The oops happens because topology_sane() checks to see if the Last Level Cache line matches across different CPUs, which it no longer does. [Fix] The fix comes in the form of the following upstream commit, which landed in Linux 4.17: commit 1340ccfa9a9afefdbab90d7935d4ed19817e37c2 Author: Alison Schofield Date: Fri Apr 6 17:21:30 2018 -0700 Subject: x86,sched: Allow topologies where NUMA nodes share an LLC Link: https://github.com/torvalds/linux/commit/1340ccfa9a9afefdbab90d7935d4ed19817e37c2 The commit adds a check for this particular family of Intel processors, and if the CPU family matches, it simply skips the check to topology_sane(). The commit needs minor backports to Xenial 4.4 and Bionic 4.15, with the only remarks being re-arranging #includes and small context fixups. [Testcase] Unfortunately, this is hardware specific. To test this, you need a Intel Skylake server processor which supports Sub-NUMA-Clustering. We have a customer with a Intel Xeon Gold 5120 CPU on a HP DL360 Gen10 that has successfully tested the below test kernels, with good results. Xenial 4.4 ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf280048-test-ga Xenial 4.15 HWE ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf280048-test-hwe Running the test kernel, the oops does not reproduce: smp: Bringing up secondary CPUs ... x86: Booting SMP configuration: node #0, CPUs: #1 NMI watchdog: Enabled. Permanently consumes one hw-PMU counter. #2 #3 #4 #5 #6 node #1, CPUs: #7 #8 #9 #10 #11 #12 #13 node #0, CPUs: #14 #15 #16 #17 #18 #19 #20 node #1, CPUs: #21 #22 #23 #24 #25 #26 #27 smp: Brought up 2 nodes, 28 CPUs smpboot: Max logical packages: 1 smpboot: Total of 28 processors activated [Regression Potential] The commit modifies a small section of smpboot code, which every machine will execute on boot. The majority
[Kernel-packages] [Bug 1889735] Re: tap: use after free
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889735 Title: tap: use after free Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: [Impact] If the socket buffer array of a tap queue is full, a received package needs to be dropped. Currently, the check for the array being full is performed lockless, which might lead to use-after-free errors if the socket buffer array has been resized. [Test Case] TBD. [Regression Potential] The check for the array being full is simply dropped. In case the array is full, subsequent frame handling will fail and the frame is eventually dropped. A regression would manifest itself if the frame is not dropped for whatever reason and inserted into the full (ring) buffer, overwriting the oldest frame in the buffer. So we'd end up with frame/packet loss. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889735/+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 1887607] Re: NFSv4.1: Interrupted connections cause high bandwidth RPC ping-pong between client and server
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887607 Title: NFSv4.1: Interrupted connections cause high bandwidth RPC ping-pong between client and server Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1887607 [Impact] There is a bug in NFS v4.1 that causes a large amount of RPC calls between a client and server when a previous RPC call is interrupted. This uses a large amount of bandwidth and can saturate the network. The symptoms are so: * On NFS clients: Attempts to access mounted NFS shares associated with the affected server block indefinitely. * On the network: A storm of repeated RPCs between NFS client and server uses a lot of bandwidth. Each RPC is acknowledged by the server with an NFS4ERR_SEQ_MISORDERED error. * Other NFS clients connected to the same NFS server: Performance drops dramatically. This occurs during a "false retry", when a client attempts to make a new RPC call using a slot+sequence number that references an older, cached call. This happens when a user process interrupts an RPC call that is in progress. I had previously fixed this for Disco in bug 1828978, and now a customer has run into the issue in Bionic. A reproducer is supplied in the testcase section, which was something missing from bug 1828978, since we never determined how the issue actually occurred back then. [Fix] This was fixed in 5.1 upstream with the below commit: commit 3453d5708b33efe76f40eca1c0ed60923094b971 Author: Trond Myklebust Date: Wed Jun 20 17:53:34 2018 -0400 Subject: NFSv4.1: Avoid false retries when RPC calls are interrupted The fix is to pre-emptively increment the sequence number if an RPC call is interrupted, and to address corner cases we interpret the NFS4ERR_SEQ_MISORDERED error as a sign we need to locate an appropriate sequence number between the value we sent, and the last successfully acked SEQUENCE call. The commit also requires two fixup commits, which landed in 5.5 and 5.8-rc6 respectively: commit 5c441544f045e679afd6c3c6d9f7aaf5fa5f37b0 Author: Trond Myklebust Date: Wed Nov 13 08:34:00 2019 +0100 Subject: NFSv4.x: Handle bad/dead sessions correctly in nfs41_sequence_process() commit 913fadc5b105c3619d9e8d0fe8899ff1593cc737 Author: Anna Schumaker Date: Wed Jul 8 10:33:40 2020 -0400 Subject: NFS: Fix interrupted slots by sending a solo SEQUENCE operation Commits 3453d5708b33efe76f40eca1c0ed60923094b971 and 913fadc5b105c3619d9e8d0fe8899ff1593cc737 require small backports to bionic, as struct rpc_cred changed to const struct cred in 5.0, and the backports swap them back to struct rpc_cred since that is how 4.15 works. [Testcase] You will need four machines. The first, is a kerberos KDC. Set up Kerberos correctly and create new service principals for the NFS server and for the client. I used: nfs/nfskerb.mydomain.com and nfs/client.mydomain.com. The second machine will be a NFS server with the krb5p share. Add the nfs server kerberos keys to the system's keytab, and set up a NFS server that exports a directory with sec=krb5p. Example export: /mnt/secretfolder *.mydomain.com(rw,sync,no_subtree_check,sec=krb5p) The third machine is a regular NFS server. Export a directory with normal sec=sys security. Example export: /mnt/sharedfolder *.mydomain.com(rw,sync) The fourth is a desktop machine. Add the client kerberos keys to the system's keytab. Mount both NFS shares, making sure to use the NFS v4.2 protocol. I used the commands: mount -t nfs4 nfskerb.mydomain.com:/mnt/secretfolder /mnt/secretfolder_client/ mount -t nfs4 nfs.mydomain.com:/mnt/sharedfolder /mnt/sharedfolder_client Check "mount -l" to ensure that NFS v4.2 is used: nfskerb.mydomain.com:/mnt/secretfolder on /mnt/secretfolder_client type nfs4 (rw,relatime,vers=4.2,<...>,sec=krb5p,<...>) nfs.mydomain.com:/mnt/sharedfolder on /mnt/sharedfolder_client type nfs4 (rw,relatime,vers=4.2,<...>,sec=sys,<...>) Generate some files full of random data. I found 20MB from /dev/random works great. Open each NFS share
[Kernel-packages] [Bug 1883962] Re: apparmor reference leak causes refcount_t overflow with af_alg_accept()
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883962 Title: apparmor reference leak causes refcount_t overflow with af_alg_accept() Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Invalid Bug description: [Impact] * Users of the Crypto (user-space) API (i.e., AF_ALG) can trigger refcount errors in AppArmor under high load (might lead to memory leak or use after free.) * There is a reference leak in AppArmor when af_alg_accept() calls security_sock_graft() and then security_sk_clone(). * Both acquire a reference to a label, to assign it to the same pointer, but the latter does not release the former's acquired reference (before overwriting the pointer value.) * This reference leak builds up over time, and under high load can eventually overflow/underflow/saturate refcount, depending on which value it has when a program hits that. * The fix just checks if the pointer has an assigned label, then releases its acquired reference. [Test Case] * See comment #1 for the test-case 'aa-refcnt-af_alg.c'. * Exercise that code path indefinitely until it hits the refcount_t overflow/underflow/saturate message (or not, with the patch.) (see comment #4) * It's possible to monitor refcount values with kprobes, to confirm whether or not the problem is happening. (see comments #2 and #3) [Other Info] * Patch applied upstream on v5.8-rc1 [1] * Applied on Unstable (tag Ubuntu-5.8-5.8.0-0.1) * Not required on Groovy (still 5.4; should sync from Unstable) * Not required on Eoan (EOL date before SRU cycle release date) * Required on Bionic and Focal. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=3b646abc5bc6c0df649daea4c2c976bd4d47e4c8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883962/+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 1885271] Re: kernel oops xr-usb-serial
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885271 Title: kernel oops xr-usb-serial Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: # Steps to reproduce # Working case uname -a Linux ubuntu 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:09:48 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsusb -d 04e2:1411 -v > xr-usb-serial-devices.txt lsusb -t >> xr-usb-serial-devices.txt # Unbind 2 xr-usb-serial devices echo '3-14.1' | tee /sys/bus/usb/drivers/usb/unbind echo '3-14.3' | tee /sys/bus/usb/drivers/usb/unbind dmesg > dmesg.txt # Non working case uname -a Linux ubuntu 4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsusb -d 04e2:1411 -v > xr-usb-serial-devices.txt dmesg > dmesg.txt This regression is almost certainly caused by one of the 2020-03-11 commits: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/log/ubuntu/xr-usb-serial?h=Ubuntu-4.15.0-99.100=5966ed54d467fa77e7dbd7355177a5a6d1db7004 files attached in tar file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885271/+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: I have similar results as Filip. Followed the fix (#66), used the correct sed command (with backslash #86) and updated grub... still no touchpad, even though output of 'lsmod | grep i2c' is: i2c_algo_bit 16384 1 i915 elan_i2c 40960 0 i2c_i801 32768 And output of 'll /sys/bus/i2c/drivers/elan_i2c/' is: total 0 drwxr-xr-x 2 root root0 avg 10 20:26 ./ drwxr-xr-x 40 root root0 avg 10 20:26 ../ --w--- 1 root root 4096 avg 10 20:44 bind lrwxrwxrwx 1 root root0 avg 10 20:44 module -> ../../../../module/elan_i2c/ --w--- 1 root root 4096 avg 10 20:26 uevent --w--- 1 root root 4096 avg 10 20:44 unbind I have ubuntu 20.04 kernel 5.4.0-42-generic, although my laptop is Thinkpad 14 IIL. Any ideas? -- 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 1890873] Re: no intel_backlight file
dmesg shows "video.use_native_backlight=1" is used. This kernel parameter is no longer available. You can replace with "acpi_video" acpi_backlight= [HW,ACPI] acpi_backlight=vendor acpi_backlight=video If set to vendor, prefer vendor specific driver (e.g. thinkpad_acpi, sony_acpi, etc.) instead of the ACPI video.ko driver. -- 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/1890873 Title: no intel_backlight file Status in linux package in Ubuntu: Confirmed Bug description: i am a noob, can't find the intel_backlight 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kira 1573 F pulseaudio /dev/snd/controlC1: kira 1573 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 13:32:31 2020 InstallationDate: Installed on 2020-08-01 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Nitro AN515-54 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=53af6216-e431-4dba-8753-614cbe9fa7ca ro nomodeset_ quiet splash video.use_native_backlight=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2020 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.30 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Octavia_CFS dmi.board.vendor: CFL dmi.board.version: V1.30 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.30 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.30:bd05/11/2020:svnAcer:pnNitroAN515-54:pvrV1.30:rvnCFL:rnOctavia_CFS:rvrV1.30:cvnAcer:ct10:cvrV1.30: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-54 dmi.product.sku: dmi.product.version: V1.30 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890873/+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 1890873] Re: no intel_backlight file
Do you mean you cannot adjust brightness with either hotkeys or GUI? intel_backlight is one of possible backlight interfaces. You can run "ls /sys/class/backlight" to find out what your system has. -- 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/1890873 Title: no intel_backlight file Status in linux package in Ubuntu: Confirmed Bug description: i am a noob, can't find the intel_backlight 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kira 1573 F pulseaudio /dev/snd/controlC1: kira 1573 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 13:32:31 2020 InstallationDate: Installed on 2020-08-01 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Nitro AN515-54 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=53af6216-e431-4dba-8753-614cbe9fa7ca ro nomodeset_ quiet splash video.use_native_backlight=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2020 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.30 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Octavia_CFS dmi.board.vendor: CFL dmi.board.version: V1.30 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.30 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.30:bd05/11/2020:svnAcer:pnNitroAN515-54:pvrV1.30:rvnCFL:rnOctavia_CFS:rvrV1.30:cvnAcer:ct10:cvrV1.30: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-54 dmi.product.sku: dmi.product.version: V1.30 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890873/+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 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
Seeing I can't make work the second monitor I installed on 20.04 the 4.15 kernel. Now it works, so this is for sure something about the kernel. On 4.15 and higher, the second monitor doesn't work. Tested on 5.8. And it doesn't work neither. ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #2181 https://gitlab.freedesktop.org/drm/intel/-/issues/2181 -- 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/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). WORKAROUND: I installed the 4.15 kernel, so at the moment I can work with this. Higher than 4.15 the second monitor doesn't work. Tested until 5.8 and without good results. Just with 4.15. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio:
[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
"On 4.15 and higher, the second monitor doesn't work." Sorry, *HIGHER THAN 4.15, NOT 4.15*, with 4.15 this works as it should be. ** Description changed: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) - PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). - --- + PD: When you select a specific resolution, the second monitor "works", + but it blinks, the image showed via HDMI on the second monitor blinks. + So is impossible to work with it. Since all this time I was searching + about this and I'm almost sure this is a problem of the GPU's Intel. But + I saw this problem on askubuntu just with laptops with hybrid graphics. + Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if + they have the same problem here). + + + WORKAROUND: I installed the 4.15 kernel, so at the moment I can work + with this. Higher than 4.15 the second monitor doesn't work. Tested + until 5.8 and without good results. Just with 4.15. + + + --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: ""
[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
PD: There's the link to see this bug posted on freedesktop.org: https://gitlab.freedesktop.org/drm/intel/-/issues/2181#note_580910 -- 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/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). WORKAROUND: I installed the 4.15 kernel, so at the moment I can work with this. Higher than 4.15 the second monitor doesn't work. Tested until 5.8 and without good results. Just with 4.15. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel
[Kernel-packages] [Bug 1891062] Re: Lenovo X1 Tablet Gen3 trackpoint and buttons not working
I've updated my BIOS to 1.40 and have performed a clean install of Ubuntu 20.04 LTS but the trackpoint and trackpad buttons are still not working. -- 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/1891062 Title: Lenovo X1 Tablet Gen3 trackpoint and buttons not working Status in linux package in Ubuntu: Confirmed Bug description: Upon clean install of Ubuntu 20.04 LTS my trackpoint and trackpad buttons are not working. From my investigation, a patch has been applied to the 5.4.y branch (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=8d5037dca7c2089f27e5903c2aecfc5bb10d7806). I followed the steps listed in here: https://github.com/da-cali/linux-x1-tablet#fix-the-trackpoint-and-trackpad-buttons using v5.4.57, but now my GRUB has two options: * Ubuntu w/ 5.4.57+ (not working. Stuck "Loading initial ramdisk") * Ubuntu w/ 5.4.0-42-generic (working) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 12:53:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 1392 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20KJCTO1WW Package: linux (not installed) 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=/boot/vmlinuz-5.4.0-42-generic root=UUID=5187b79d-6bc7-455c-9c28-0876bcb85a3b ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 StagingDrivers: ipu3_imgu Tags: focal staging Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1ZET79W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KJCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1ZET79W(1.35):bd11/28/2019:svnLENOVO:pn20KJCTO1WW:pvrThinkPadX1TabletGen3:rvnLENOVO:rn20KJCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone: dmi.product.family: ThinkPad X1 Tablet Gen 3 dmi.product.name: 20KJCTO1WW dmi.product.sku: LENOVO_MT_20KJ_BU_Think_FM_ThinkPad X1 Tablet Gen 3 dmi.product.version: ThinkPad X1 Tablet Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891062/+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 1888570] Re: poweroff not working after apt upgrade
** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu) Status: Won't Fix => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Invalid Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+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 1890884] Re: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D06 arm64 arch
Marking as impacting subiquity, because being unable to mount root is unlikely a problem with the kernel itself. ** Also affects: subiquity 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/1890884 Title: kernel trace of 18.04.5 daily image (20200806.1) on Hisilicon D06 arm64 arch Status in subiquity: New Status in linux package in Ubuntu: Incomplete Bug description: image: 18.04.5 daily image (20200806.1) bionic-live-server-arm64.iso kernel: 4.15.0-112-generic #113-Ubuntu platform: Hisilicon D06 arm64 arch [Reproducing Steps] 1. setup pxe boot by following https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510 2. pxe boot the machine with the image [Expected Result] Boot to subiquity [Actual Result] Kernel trace happened during booting process. Reproducing rate: 2 out of 2. [8.375118] md: ... autorun DONE. [8.378478] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 [8.385955] Please append a correct "root=" boot option; here are the available partitions: [8.394303] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [8.402554] CPU: 32 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic #113-Ubuntu [8.410369] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - V1.20.01 04/26/2019 [8.418879] Call trace: [8.421316] dump_backtrace+0x0/0x198 [8.424965] show_stack+0x24/0x30 [8.428269] dump_stack+0x98/0xbc [8.431572] panic+0x128/0x2a4 [8.434615] mount_block_root+0x210/0x2e8 [8.438610] mount_root+0x7c/0x8c [8.441912] prepare_namespace+0x144/0x1dc [8.445995] kernel_init_freeable+0x218/0x23c [8.450341] kernel_init+0x18/0x110 [8.453817] ret_from_fork+0x10/0x18 [8.457486] SMP: stopping secondary CPUs [8.461836] Kernel Offset: disabled [8.465312] CPU features: 0x03200a38 [8.468873] Memory Limit: none [8.473291] Unable to handle kernel paging request at virtual address 09865034 [8.481192] Mem abort info: [8.483972] ESR = 0x9661 [8.487013] Exception class = DABT (current EL), IL = 32 bits [8.492918] SET = 0, FnV = 0 [8.495958] EA = 0, S1PTW = 0 [8.499086] Data abort info: [8.501953] ISV = 0, ISS = 0x0061 [8.505774] CM = 0, WnR = 1 [8.508729] swapper pgtable: 4k pages, 48-bit VAs, pgd = (ptrval) [8.515502] [09865034] *pgd=0a5fe003, *pud=0a5fd003, *pmd=0a5f7003, *pte=006894110703 [8.526445] Internal error: Oops: 9661 [#1] SMP [8.531310] Modules linked in: [8.534351] Process swapper/0 (pid: 1, stack limit = 0x(ptrval)) [8.541039] CPU: 32 PID: 1 Comm: swapper/0 Not tainted 4.15.0-112-generic #113-Ubuntu [8.548854] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - V1.20.01 04/26/2019 [8.557363] pstate: 60800089 (nZCv daIf -PAN +UAO) [8.562144] pc : acpi_os_write_memory+0xac/0x158 [8.566749] lr : apei_write+0xb0/0xc0 [8.570397] sp : 09afb900 [8.573698] x29: 09afb900 x28: fffe [8.578996] x27: x26: ffa5 [8.584294] x25: ffbe x24: 0080 [8.589592] x23: 0005 x22: 0008 [8.594890] x21: 0040 x20: 0010 [8.600188] x19: 94110034 x18: 0003 [8.605486] x17: x16: 0009 [8.610784] x15: 001f x14: 8205169d4225fc6e [8.616082] x13: 34650f577629d387 x12: 9c021ee3f3d0bcca [8.621380] x11: b1ae83ff50c19148 x10: b6b91ab42ae87562 [8.626678] x9 : f469cb78cb1add9d x8 : a16fcb806efa3dd5 [8.631976] x7 : 0001 x6 : 94110034 [8.637274] x5 : 9411003c x4 : 09639fb8 [8.642571] x3 : x2 : 0034 [8.647869] x1 : 0010 x0 : 09865034 [8.653167] Call trace: [8.655601] acpi_os_write_memory+0xac/0x158 [8.659858] apei_write+0xb0/0xc0 [8.663160] __apei_exec_write_register+0x88/0xb0 [8.667851] apei_exec_write_register_value+0x2c/0x38 [8.672888] __apei_exec_run+0xac/0x108 [8.676711] erst_write+0x154/0x268 [8.680186] erst_writer+0x26c/0x3b0 [8.683751] pstore_dump+0x1b4/0x330 [8.687313] kmsg_dump+0xd0/0x100 [8.690615] panic+0x164/0x2a4 [8.693656] mount_block_root+0x210/0x2e8 [8.697652] mount_root+0x7c/0x8c [8.700953] prepare_namespace+0x144/0x1dc [8.705035] kernel_init_freeable+0x218/0x23c [8.709380] kernel_init+0x18/0x110 [8.712855] ret_from_fork+0x10/0x18 [8.716418] Code: 54000380
[Kernel-packages] [Bug 1875199] Re: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all
@Kai-Heng, Thank you for the explanation of the error, and thank you once again for your help throughout the process it is very much appreciated. -- 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/1875199 Title: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all Status in linux package in Ubuntu: Incomplete Bug description: No sound output. Only a 'Dummy' audio output device is listed in the Gnome Sound application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 12:12:49 2020 InstallationDate: Installed on 2020-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1215 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel(R) Client Systems NUC8CCHK Package: linux (not installed) 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=/boot/vmlinuz-5.4.0-28-generic root=UUID=afbb0f64-e729-46a8-82e4-a060e9e729c4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/+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'
@Aleksandar: I can't believe it: it works!! Thank you so much. Thank you Ferenc! Back in the game... -- 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 1891063] Re: Focal update: v5.4.56 upstream stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.56 upstream stable release + from git://git.kernel.org/ -v5.4.56 upstream stable release -from git://git.kernel.org/ + crypto: ccp - Release all allocated memory if sha type is invalid + media: rc: prevent memory leak in cx23888_ir_probe + sunrpc: check that domain table is empty at module unload. + ath10k: enable transmit data ack RSSI for QCA9884 + PCI/ASPM: Disable ASPM on ASMedia ASM1083/1085 PCIe-to-PCI bridge + mm/filemap.c: don't bother dropping mmap_sem for zero size readahead + ALSA: usb-audio: Add implicit feedback quirk for SSL2 + ALSA: hda/realtek: enable headset mic of ASUS ROG Zephyrus G15(GA502) series with ALC289 + ALSA: hda/realtek: typo_fix: enable headset mic of ASUS ROG Zephyrus G14(GA401) series with ALC289 + ALSA: hda/realtek: Fix add a "ultra_low_power" function for intel reference board (alc256) + ALSA: hda/hdmi: Fix keep_power assignment for non-component devices + IB/rdmavt: Fix RQ counting issues causing use of an invalid RWQE + vhost/scsi: fix up req type endian-ness + 9p/trans_fd: Fix concurrency del of req_list in p9_fd_cancelled/p9_read_work + wireless: Use offsetof instead of custom macro. + ARM: 8986/1: hw_breakpoint: Don't invoke overflow handler on uaccess watchpoints + ARM: dts: imx6sx-sabreauto: Fix the phy-mode on fec2 + ARM: dts: imx6sx-sdb: Fix the phy-mode on fec2 + ARM: dts: imx6qdl-icore: Fix OTG_ID pin and sdcard detect + virtio_balloon: fix up endian-ness for free cmd id + Revert "drm/amdgpu: Fix NULL dereference in dpm sysfs handlers" + drm/amd/display: Clear dm_state for fast updates + drm/amdgpu: Prevent kernel-infoleak in amdgpu_info_ioctl() + drm/dbi: Fix SPI Type 1 (9-bit) transfer + drm: hold gem reference until object is no longer accessed + rds: Prevent kernel-infoleak in rds_notify_queue_get() + libtraceevent: Fix build with binutils 2.35 + net/x25: Fix x25_neigh refcnt leak when x25 disconnect + net/x25: Fix null-ptr-deref in x25_disconnect + xfrm: policy: match with both mark and mask on user interfaces + ARM: dts sunxi: Relax a bit the CMA pool allocation range + xfrm: Fix crash when the hold queue is used. + ARM: dts: armada-38x: fix NETA lockup when repeatedly switching speeds + nvme-tcp: fix possible hang waiting for icresp response + selftests/net: rxtimestamp: fix clang issues for target arch PowerPC + selftests/net: psock_fanout: fix clang issues for target arch PowerPC + selftests/net: so_txtime: fix clang issues for target arch PowerPC + sh/tlb: Fix PGTABLE_LEVELS > 2 + sh: Fix validation of system call number + net: hns3: fix a TX timeout issue + net: hns3: fix aRFS FD rules leftover after add a user FD rule + net/mlx5: E-switch, Destroy TSAR when fail to enable the mode + net/mlx5e: Fix error path of device attach + net/mlx5: Verify Hardware supports requested ptp function on a given pin + net/mlx5e: Modify uplink state on interface up/down + net/mlx5e: Fix kernel crash when setting vf VLANID on a VF dev + net: lan78xx: add missing endpoint sanity check + net: lan78xx: fix transfer-buffer memory leak + rhashtable: Fix unprotected RCU dereference in __rht_ptr + mlx4: disable device on shutdown + mlxsw: core: Increase scope of RCU read-side critical section + mlxsw: core: Free EMAD transactions using kfree_rcu() + ibmvnic: Fix IRQ mapping disposal in error path + bpf: Fix map leak in HASH_OF_MAPS map + mac80211: mesh: Free ie data when leaving mesh + mac80211: mesh: Free pending skb when destroying a mpath + arm64/alternatives: move length validation inside the subsection + arm64: csum: Fix handling of bad packets + Bluetooth: fix kernel oops in store_pending_adv_report + net: nixge: fix potential memory leak in nixge_probe() + net: gemini: Fix missing clk_disable_unprepare() in error path of gemini_ethernet_port_probe() + net/mlx5e: fix bpf_prog reference count leaks in mlx5e_alloc_rq + perf tools: Fix record failure when mixed with ARM SPE event + vxlan: fix memleak of fdb + usb: hso: Fix debug compile warning on sparc32 + selftests:
[Kernel-packages] [Bug 1891062] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891062 Title: Lenovo X1 Tablet Gen3 trackpoint and buttons not working Status in linux package in Ubuntu: Confirmed Bug description: Upon clean install of Ubuntu 20.04 LTS my trackpoint and trackpad buttons are not working. From my investigation, a patch has been applied to the 5.4.y branch (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=8d5037dca7c2089f27e5903c2aecfc5bb10d7806). I followed the steps listed in here: https://github.com/da-cali/linux-x1-tablet#fix-the-trackpoint-and-trackpad-buttons using v5.4.57, but now my GRUB has two options: * Ubuntu w/ 5.4.57+ (not working. Stuck "Loading initial ramdisk") * Ubuntu w/ 5.4.0-42-generic (working) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 12:53:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 1392 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20KJCTO1WW Package: linux (not installed) 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=/boot/vmlinuz-5.4.0-42-generic root=UUID=5187b79d-6bc7-455c-9c28-0876bcb85a3b ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 StagingDrivers: ipu3_imgu Tags: focal staging Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1ZET79W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KJCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1ZET79W(1.35):bd11/28/2019:svnLENOVO:pn20KJCTO1WW:pvrThinkPadX1TabletGen3:rvnLENOVO:rn20KJCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone: dmi.product.family: ThinkPad X1 Tablet Gen 3 dmi.product.name: 20KJCTO1WW dmi.product.sku: LENOVO_MT_20KJ_BU_Think_FM_ThinkPad X1 Tablet Gen 3 dmi.product.version: ThinkPad X1 Tablet Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891062/+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 1891064] Re: Focal update: v5.4.57 upstream stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.57 upstream stable release + from git://git.kernel.org/ -v5.4.57 upstream stable release -from git://git.kernel.org/ + random32: update the net random state on interrupt and activity + ARM: percpu.h: fix build error + random: fix circular include dependency on arm64 after addition of percpu.h + random32: remove net_rand_state from the latent entropy gcc plugin + random32: move the pseudo-random 32-bit definitions to prandom.h + arm64: Workaround circular dependency in pointer_auth.h + ext4: fix direct I/O read error + selftests: bpf: Fix detach from sockmap tests + bpf: sockmap: Require attach_bpf_fd when detaching a program + Linux 5.4.57 + UBUNTU: upstream stable to v5.4.57 -- 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/1891064 Title: Focal update: v5.4.57 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.57 upstream stable release from git://git.kernel.org/ random32: update the net random state on interrupt and activity ARM: percpu.h: fix build error random: fix circular include dependency on arm64 after addition of percpu.h random32: remove net_rand_state from the latent entropy gcc plugin random32: move the pseudo-random 32-bit definitions to prandom.h arm64: Workaround circular dependency in pointer_auth.h ext4: fix direct I/O read error selftests: bpf: Fix detach from sockmap tests bpf: sockmap: Require attach_bpf_fd when detaching a program Linux 5.4.57 UBUNTU: upstream stable to v5.4.57 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891064/+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 1891062] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1891062/+attachment/5400446/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891062 Title: Lenovo X1 Tablet Gen3 trackpoint and buttons not working Status in linux package in Ubuntu: Confirmed Bug description: Upon clean install of Ubuntu 20.04 LTS my trackpoint and trackpad buttons are not working. From my investigation, a patch has been applied to the 5.4.y branch (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=8d5037dca7c2089f27e5903c2aecfc5bb10d7806). I followed the steps listed in here: https://github.com/da-cali/linux-x1-tablet#fix-the-trackpoint-and-trackpad-buttons using v5.4.57, but now my GRUB has two options: * Ubuntu w/ 5.4.57+ (not working. Stuck "Loading initial ramdisk") * Ubuntu w/ 5.4.0-42-generic (working) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 12:53:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 1392 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20KJCTO1WW Package: linux (not installed) 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=/boot/vmlinuz-5.4.0-42-generic root=UUID=5187b79d-6bc7-455c-9c28-0876bcb85a3b ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 StagingDrivers: ipu3_imgu Tags: focal staging Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1ZET79W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KJCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1ZET79W(1.35):bd11/28/2019:svnLENOVO:pn20KJCTO1WW:pvrThinkPadX1TabletGen3:rvnLENOVO:rn20KJCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone: dmi.product.family: ThinkPad X1 Tablet Gen 3 dmi.product.name: 20KJCTO1WW dmi.product.sku: LENOVO_MT_20KJ_BU_Think_FM_ThinkPad X1 Tablet Gen 3 dmi.product.version: ThinkPad X1 Tablet Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891062/+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 1891062] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1891062/+attachment/5400438/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891062 Title: Lenovo X1 Tablet Gen3 trackpoint and buttons not working Status in linux package in Ubuntu: Confirmed Bug description: Upon clean install of Ubuntu 20.04 LTS my trackpoint and trackpad buttons are not working. From my investigation, a patch has been applied to the 5.4.y branch (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=8d5037dca7c2089f27e5903c2aecfc5bb10d7806). I followed the steps listed in here: https://github.com/da-cali/linux-x1-tablet#fix-the-trackpoint-and-trackpad-buttons using v5.4.57, but now my GRUB has two options: * Ubuntu w/ 5.4.57+ (not working. Stuck "Loading initial ramdisk") * Ubuntu w/ 5.4.0-42-generic (working) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 12:53:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 1392 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20KJCTO1WW Package: linux (not installed) 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=/boot/vmlinuz-5.4.0-42-generic root=UUID=5187b79d-6bc7-455c-9c28-0876bcb85a3b ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 StagingDrivers: ipu3_imgu Tags: focal staging Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1ZET79W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KJCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1ZET79W(1.35):bd11/28/2019:svnLENOVO:pn20KJCTO1WW:pvrThinkPadX1TabletGen3:rvnLENOVO:rn20KJCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone: dmi.product.family: ThinkPad X1 Tablet Gen 3 dmi.product.name: 20KJCTO1WW dmi.product.sku: LENOVO_MT_20KJ_BU_Think_FM_ThinkPad X1 Tablet Gen 3 dmi.product.version: ThinkPad X1 Tablet Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891062/+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 1891062] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1891062/+attachment/5400445/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891062 Title: Lenovo X1 Tablet Gen3 trackpoint and buttons not working Status in linux package in Ubuntu: Confirmed Bug description: Upon clean install of Ubuntu 20.04 LTS my trackpoint and trackpad buttons are not working. From my investigation, a patch has been applied to the 5.4.y branch (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=8d5037dca7c2089f27e5903c2aecfc5bb10d7806). I followed the steps listed in here: https://github.com/da-cali/linux-x1-tablet#fix-the-trackpoint-and-trackpad-buttons using v5.4.57, but now my GRUB has two options: * Ubuntu w/ 5.4.57+ (not working. Stuck "Loading initial ramdisk") * Ubuntu w/ 5.4.0-42-generic (working) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 12:53:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 1392 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20KJCTO1WW Package: linux (not installed) 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=/boot/vmlinuz-5.4.0-42-generic root=UUID=5187b79d-6bc7-455c-9c28-0876bcb85a3b ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 StagingDrivers: ipu3_imgu Tags: focal staging Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1ZET79W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KJCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1ZET79W(1.35):bd11/28/2019:svnLENOVO:pn20KJCTO1WW:pvrThinkPadX1TabletGen3:rvnLENOVO:rn20KJCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone: dmi.product.family: ThinkPad X1 Tablet Gen 3 dmi.product.name: 20KJCTO1WW dmi.product.sku: LENOVO_MT_20KJ_BU_Think_FM_ThinkPad X1 Tablet Gen 3 dmi.product.version: ThinkPad X1 Tablet Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891062/+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 1891062] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1891062/+attachment/5400434/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891062 Title: Lenovo X1 Tablet Gen3 trackpoint and buttons not working Status in linux package in Ubuntu: Confirmed Bug description: Upon clean install of Ubuntu 20.04 LTS my trackpoint and trackpad buttons are not working. From my investigation, a patch has been applied to the 5.4.y branch (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=8d5037dca7c2089f27e5903c2aecfc5bb10d7806). I followed the steps listed in here: https://github.com/da-cali/linux-x1-tablet#fix-the-trackpoint-and-trackpad-buttons using v5.4.57, but now my GRUB has two options: * Ubuntu w/ 5.4.57+ (not working. Stuck "Loading initial ramdisk") * Ubuntu w/ 5.4.0-42-generic (working) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 12:53:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 1392 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20KJCTO1WW Package: linux (not installed) 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=/boot/vmlinuz-5.4.0-42-generic root=UUID=5187b79d-6bc7-455c-9c28-0876bcb85a3b ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 StagingDrivers: ipu3_imgu Tags: focal staging Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1ZET79W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KJCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1ZET79W(1.35):bd11/28/2019:svnLENOVO:pn20KJCTO1WW:pvrThinkPadX1TabletGen3:rvnLENOVO:rn20KJCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone: dmi.product.family: ThinkPad X1 Tablet Gen 3 dmi.product.name: 20KJCTO1WW dmi.product.sku: LENOVO_MT_20KJ_BU_Think_FM_ThinkPad X1 Tablet Gen 3 dmi.product.version: ThinkPad X1 Tablet Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891062/+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 1891062] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1891062/+attachment/5400439/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891062 Title: Lenovo X1 Tablet Gen3 trackpoint and buttons not working Status in linux package in Ubuntu: Confirmed Bug description: Upon clean install of Ubuntu 20.04 LTS my trackpoint and trackpad buttons are not working. From my investigation, a patch has been applied to the 5.4.y branch (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=8d5037dca7c2089f27e5903c2aecfc5bb10d7806). I followed the steps listed in here: https://github.com/da-cali/linux-x1-tablet#fix-the-trackpoint-and-trackpad-buttons using v5.4.57, but now my GRUB has two options: * Ubuntu w/ 5.4.57+ (not working. Stuck "Loading initial ramdisk") * Ubuntu w/ 5.4.0-42-generic (working) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 12:53:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 1392 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20KJCTO1WW Package: linux (not installed) 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=/boot/vmlinuz-5.4.0-42-generic root=UUID=5187b79d-6bc7-455c-9c28-0876bcb85a3b ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 StagingDrivers: ipu3_imgu Tags: focal staging Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1ZET79W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KJCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1ZET79W(1.35):bd11/28/2019:svnLENOVO:pn20KJCTO1WW:pvrThinkPadX1TabletGen3:rvnLENOVO:rn20KJCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone: dmi.product.family: ThinkPad X1 Tablet Gen 3 dmi.product.name: 20KJCTO1WW dmi.product.sku: LENOVO_MT_20KJ_BU_Think_FM_ThinkPad X1 Tablet Gen 3 dmi.product.version: ThinkPad X1 Tablet Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891062/+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 1891062] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1891062/+attachment/5400436/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891062 Title: Lenovo X1 Tablet Gen3 trackpoint and buttons not working Status in linux package in Ubuntu: Confirmed Bug description: Upon clean install of Ubuntu 20.04 LTS my trackpoint and trackpad buttons are not working. From my investigation, a patch has been applied to the 5.4.y branch (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=8d5037dca7c2089f27e5903c2aecfc5bb10d7806). I followed the steps listed in here: https://github.com/da-cali/linux-x1-tablet#fix-the-trackpoint-and-trackpad-buttons using v5.4.57, but now my GRUB has two options: * Ubuntu w/ 5.4.57+ (not working. Stuck "Loading initial ramdisk") * Ubuntu w/ 5.4.0-42-generic (working) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 12:53:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 1392 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20KJCTO1WW Package: linux (not installed) 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=/boot/vmlinuz-5.4.0-42-generic root=UUID=5187b79d-6bc7-455c-9c28-0876bcb85a3b ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 StagingDrivers: ipu3_imgu Tags: focal staging Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1ZET79W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KJCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1ZET79W(1.35):bd11/28/2019:svnLENOVO:pn20KJCTO1WW:pvrThinkPadX1TabletGen3:rvnLENOVO:rn20KJCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone: dmi.product.family: ThinkPad X1 Tablet Gen 3 dmi.product.name: 20KJCTO1WW dmi.product.sku: LENOVO_MT_20KJ_BU_Think_FM_ThinkPad X1 Tablet Gen 3 dmi.product.version: ThinkPad X1 Tablet Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891062/+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 1891062] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1891062/+attachment/5400441/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891062 Title: Lenovo X1 Tablet Gen3 trackpoint and buttons not working Status in linux package in Ubuntu: Confirmed Bug description: Upon clean install of Ubuntu 20.04 LTS my trackpoint and trackpad buttons are not working. From my investigation, a patch has been applied to the 5.4.y branch (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=8d5037dca7c2089f27e5903c2aecfc5bb10d7806). I followed the steps listed in here: https://github.com/da-cali/linux-x1-tablet#fix-the-trackpoint-and-trackpad-buttons using v5.4.57, but now my GRUB has two options: * Ubuntu w/ 5.4.57+ (not working. Stuck "Loading initial ramdisk") * Ubuntu w/ 5.4.0-42-generic (working) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 12:53:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 1392 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20KJCTO1WW Package: linux (not installed) 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=/boot/vmlinuz-5.4.0-42-generic root=UUID=5187b79d-6bc7-455c-9c28-0876bcb85a3b ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 StagingDrivers: ipu3_imgu Tags: focal staging Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1ZET79W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KJCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1ZET79W(1.35):bd11/28/2019:svnLENOVO:pn20KJCTO1WW:pvrThinkPadX1TabletGen3:rvnLENOVO:rn20KJCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone: dmi.product.family: ThinkPad X1 Tablet Gen 3 dmi.product.name: 20KJCTO1WW dmi.product.sku: LENOVO_MT_20KJ_BU_Think_FM_ThinkPad X1 Tablet Gen 3 dmi.product.version: ThinkPad X1 Tablet Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891062/+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 1891062] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1891062/+attachment/5400431/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891062 Title: Lenovo X1 Tablet Gen3 trackpoint and buttons not working Status in linux package in Ubuntu: Confirmed Bug description: Upon clean install of Ubuntu 20.04 LTS my trackpoint and trackpad buttons are not working. From my investigation, a patch has been applied to the 5.4.y branch (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=8d5037dca7c2089f27e5903c2aecfc5bb10d7806). I followed the steps listed in here: https://github.com/da-cali/linux-x1-tablet#fix-the-trackpoint-and-trackpad-buttons using v5.4.57, but now my GRUB has two options: * Ubuntu w/ 5.4.57+ (not working. Stuck "Loading initial ramdisk") * Ubuntu w/ 5.4.0-42-generic (working) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 12:53:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 1392 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20KJCTO1WW Package: linux (not installed) 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=/boot/vmlinuz-5.4.0-42-generic root=UUID=5187b79d-6bc7-455c-9c28-0876bcb85a3b ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 StagingDrivers: ipu3_imgu Tags: focal staging Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1ZET79W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KJCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1ZET79W(1.35):bd11/28/2019:svnLENOVO:pn20KJCTO1WW:pvrThinkPadX1TabletGen3:rvnLENOVO:rn20KJCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone: dmi.product.family: ThinkPad X1 Tablet Gen 3 dmi.product.name: 20KJCTO1WW dmi.product.sku: LENOVO_MT_20KJ_BU_Think_FM_ThinkPad X1 Tablet Gen 3 dmi.product.version: ThinkPad X1 Tablet Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891062/+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 1891062] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1891062/+attachment/5400440/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891062 Title: Lenovo X1 Tablet Gen3 trackpoint and buttons not working Status in linux package in Ubuntu: Confirmed Bug description: Upon clean install of Ubuntu 20.04 LTS my trackpoint and trackpad buttons are not working. From my investigation, a patch has been applied to the 5.4.y branch (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=8d5037dca7c2089f27e5903c2aecfc5bb10d7806). I followed the steps listed in here: https://github.com/da-cali/linux-x1-tablet#fix-the-trackpoint-and-trackpad-buttons using v5.4.57, but now my GRUB has two options: * Ubuntu w/ 5.4.57+ (not working. Stuck "Loading initial ramdisk") * Ubuntu w/ 5.4.0-42-generic (working) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 12:53:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 1392 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20KJCTO1WW Package: linux (not installed) 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=/boot/vmlinuz-5.4.0-42-generic root=UUID=5187b79d-6bc7-455c-9c28-0876bcb85a3b ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 StagingDrivers: ipu3_imgu Tags: focal staging Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1ZET79W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KJCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1ZET79W(1.35):bd11/28/2019:svnLENOVO:pn20KJCTO1WW:pvrThinkPadX1TabletGen3:rvnLENOVO:rn20KJCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone: dmi.product.family: ThinkPad X1 Tablet Gen 3 dmi.product.name: 20KJCTO1WW dmi.product.sku: LENOVO_MT_20KJ_BU_Think_FM_ThinkPad X1 Tablet Gen 3 dmi.product.version: ThinkPad X1 Tablet Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891062/+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 1891062] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1891062/+attachment/5400432/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891062 Title: Lenovo X1 Tablet Gen3 trackpoint and buttons not working Status in linux package in Ubuntu: Confirmed Bug description: Upon clean install of Ubuntu 20.04 LTS my trackpoint and trackpad buttons are not working. From my investigation, a patch has been applied to the 5.4.y branch (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=8d5037dca7c2089f27e5903c2aecfc5bb10d7806). I followed the steps listed in here: https://github.com/da-cali/linux-x1-tablet#fix-the-trackpoint-and-trackpad-buttons using v5.4.57, but now my GRUB has two options: * Ubuntu w/ 5.4.57+ (not working. Stuck "Loading initial ramdisk") * Ubuntu w/ 5.4.0-42-generic (working) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 12:53:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 1392 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20KJCTO1WW Package: linux (not installed) 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=/boot/vmlinuz-5.4.0-42-generic root=UUID=5187b79d-6bc7-455c-9c28-0876bcb85a3b ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 StagingDrivers: ipu3_imgu Tags: focal staging Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1ZET79W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KJCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1ZET79W(1.35):bd11/28/2019:svnLENOVO:pn20KJCTO1WW:pvrThinkPadX1TabletGen3:rvnLENOVO:rn20KJCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone: dmi.product.family: ThinkPad X1 Tablet Gen 3 dmi.product.name: 20KJCTO1WW dmi.product.sku: LENOVO_MT_20KJ_BU_Think_FM_ThinkPad X1 Tablet Gen 3 dmi.product.version: ThinkPad X1 Tablet Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891062/+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 1891062] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1891062/+attachment/5400443/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891062 Title: Lenovo X1 Tablet Gen3 trackpoint and buttons not working Status in linux package in Ubuntu: Confirmed Bug description: Upon clean install of Ubuntu 20.04 LTS my trackpoint and trackpad buttons are not working. From my investigation, a patch has been applied to the 5.4.y branch (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=8d5037dca7c2089f27e5903c2aecfc5bb10d7806). I followed the steps listed in here: https://github.com/da-cali/linux-x1-tablet#fix-the-trackpoint-and-trackpad-buttons using v5.4.57, but now my GRUB has two options: * Ubuntu w/ 5.4.57+ (not working. Stuck "Loading initial ramdisk") * Ubuntu w/ 5.4.0-42-generic (working) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 12:53:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 1392 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20KJCTO1WW Package: linux (not installed) 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=/boot/vmlinuz-5.4.0-42-generic root=UUID=5187b79d-6bc7-455c-9c28-0876bcb85a3b ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 StagingDrivers: ipu3_imgu Tags: focal staging Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1ZET79W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KJCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1ZET79W(1.35):bd11/28/2019:svnLENOVO:pn20KJCTO1WW:pvrThinkPadX1TabletGen3:rvnLENOVO:rn20KJCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone: dmi.product.family: ThinkPad X1 Tablet Gen 3 dmi.product.name: 20KJCTO1WW dmi.product.sku: LENOVO_MT_20KJ_BU_Think_FM_ThinkPad X1 Tablet Gen 3 dmi.product.version: ThinkPad X1 Tablet Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891062/+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 1891062] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1891062/+attachment/5400435/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891062 Title: Lenovo X1 Tablet Gen3 trackpoint and buttons not working Status in linux package in Ubuntu: Confirmed Bug description: Upon clean install of Ubuntu 20.04 LTS my trackpoint and trackpad buttons are not working. From my investigation, a patch has been applied to the 5.4.y branch (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=8d5037dca7c2089f27e5903c2aecfc5bb10d7806). I followed the steps listed in here: https://github.com/da-cali/linux-x1-tablet#fix-the-trackpoint-and-trackpad-buttons using v5.4.57, but now my GRUB has two options: * Ubuntu w/ 5.4.57+ (not working. Stuck "Loading initial ramdisk") * Ubuntu w/ 5.4.0-42-generic (working) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 12:53:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 1392 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20KJCTO1WW Package: linux (not installed) 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=/boot/vmlinuz-5.4.0-42-generic root=UUID=5187b79d-6bc7-455c-9c28-0876bcb85a3b ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 StagingDrivers: ipu3_imgu Tags: focal staging Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1ZET79W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KJCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1ZET79W(1.35):bd11/28/2019:svnLENOVO:pn20KJCTO1WW:pvrThinkPadX1TabletGen3:rvnLENOVO:rn20KJCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone: dmi.product.family: ThinkPad X1 Tablet Gen 3 dmi.product.name: 20KJCTO1WW dmi.product.sku: LENOVO_MT_20KJ_BU_Think_FM_ThinkPad X1 Tablet Gen 3 dmi.product.version: ThinkPad X1 Tablet Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891062/+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 1891062] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1891062/+attachment/5400433/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891062 Title: Lenovo X1 Tablet Gen3 trackpoint and buttons not working Status in linux package in Ubuntu: Confirmed Bug description: Upon clean install of Ubuntu 20.04 LTS my trackpoint and trackpad buttons are not working. From my investigation, a patch has been applied to the 5.4.y branch (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=8d5037dca7c2089f27e5903c2aecfc5bb10d7806). I followed the steps listed in here: https://github.com/da-cali/linux-x1-tablet#fix-the-trackpoint-and-trackpad-buttons using v5.4.57, but now my GRUB has two options: * Ubuntu w/ 5.4.57+ (not working. Stuck "Loading initial ramdisk") * Ubuntu w/ 5.4.0-42-generic (working) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 12:53:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 1392 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20KJCTO1WW Package: linux (not installed) 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=/boot/vmlinuz-5.4.0-42-generic root=UUID=5187b79d-6bc7-455c-9c28-0876bcb85a3b ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 StagingDrivers: ipu3_imgu Tags: focal staging Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1ZET79W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KJCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1ZET79W(1.35):bd11/28/2019:svnLENOVO:pn20KJCTO1WW:pvrThinkPadX1TabletGen3:rvnLENOVO:rn20KJCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone: dmi.product.family: ThinkPad X1 Tablet Gen 3 dmi.product.name: 20KJCTO1WW dmi.product.sku: LENOVO_MT_20KJ_BU_Think_FM_ThinkPad X1 Tablet Gen 3 dmi.product.version: ThinkPad X1 Tablet Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891062/+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 1891062] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1891062/+attachment/5400442/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891062 Title: Lenovo X1 Tablet Gen3 trackpoint and buttons not working Status in linux package in Ubuntu: Confirmed Bug description: Upon clean install of Ubuntu 20.04 LTS my trackpoint and trackpad buttons are not working. From my investigation, a patch has been applied to the 5.4.y branch (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=8d5037dca7c2089f27e5903c2aecfc5bb10d7806). I followed the steps listed in here: https://github.com/da-cali/linux-x1-tablet#fix-the-trackpoint-and-trackpad-buttons using v5.4.57, but now my GRUB has two options: * Ubuntu w/ 5.4.57+ (not working. Stuck "Loading initial ramdisk") * Ubuntu w/ 5.4.0-42-generic (working) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 12:53:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 1392 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20KJCTO1WW Package: linux (not installed) 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=/boot/vmlinuz-5.4.0-42-generic root=UUID=5187b79d-6bc7-455c-9c28-0876bcb85a3b ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 StagingDrivers: ipu3_imgu Tags: focal staging Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1ZET79W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KJCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1ZET79W(1.35):bd11/28/2019:svnLENOVO:pn20KJCTO1WW:pvrThinkPadX1TabletGen3:rvnLENOVO:rn20KJCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone: dmi.product.family: ThinkPad X1 Tablet Gen 3 dmi.product.name: 20KJCTO1WW dmi.product.sku: LENOVO_MT_20KJ_BU_Think_FM_ThinkPad X1 Tablet Gen 3 dmi.product.version: ThinkPad X1 Tablet Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891062/+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 1891062] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1891062/+attachment/5400437/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891062 Title: Lenovo X1 Tablet Gen3 trackpoint and buttons not working Status in linux package in Ubuntu: Confirmed Bug description: Upon clean install of Ubuntu 20.04 LTS my trackpoint and trackpad buttons are not working. From my investigation, a patch has been applied to the 5.4.y branch (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=8d5037dca7c2089f27e5903c2aecfc5bb10d7806). I followed the steps listed in here: https://github.com/da-cali/linux-x1-tablet#fix-the-trackpoint-and-trackpad-buttons using v5.4.57, but now my GRUB has two options: * Ubuntu w/ 5.4.57+ (not working. Stuck "Loading initial ramdisk") * Ubuntu w/ 5.4.0-42-generic (working) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 12:53:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 1392 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20KJCTO1WW Package: linux (not installed) 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=/boot/vmlinuz-5.4.0-42-generic root=UUID=5187b79d-6bc7-455c-9c28-0876bcb85a3b ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 StagingDrivers: ipu3_imgu Tags: focal staging Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1ZET79W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KJCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1ZET79W(1.35):bd11/28/2019:svnLENOVO:pn20KJCTO1WW:pvrThinkPadX1TabletGen3:rvnLENOVO:rn20KJCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone: dmi.product.family: ThinkPad X1 Tablet Gen 3 dmi.product.name: 20KJCTO1WW dmi.product.sku: LENOVO_MT_20KJ_BU_Think_FM_ThinkPad X1 Tablet Gen 3 dmi.product.version: ThinkPad X1 Tablet Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891062/+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 1891062] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1891062/+attachment/5400444/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891062 Title: Lenovo X1 Tablet Gen3 trackpoint and buttons not working Status in linux package in Ubuntu: Confirmed Bug description: Upon clean install of Ubuntu 20.04 LTS my trackpoint and trackpad buttons are not working. From my investigation, a patch has been applied to the 5.4.y branch (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=8d5037dca7c2089f27e5903c2aecfc5bb10d7806). I followed the steps listed in here: https://github.com/da-cali/linux-x1-tablet#fix-the-trackpoint-and-trackpad-buttons using v5.4.57, but now my GRUB has two options: * Ubuntu w/ 5.4.57+ (not working. Stuck "Loading initial ramdisk") * Ubuntu w/ 5.4.0-42-generic (working) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 12:53:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 1392 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20KJCTO1WW Package: linux (not installed) 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=/boot/vmlinuz-5.4.0-42-generic root=UUID=5187b79d-6bc7-455c-9c28-0876bcb85a3b ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 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 StagingDrivers: ipu3_imgu Tags: focal staging Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1ZET79W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KJCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1ZET79W(1.35):bd11/28/2019:svnLENOVO:pn20KJCTO1WW:pvrThinkPadX1TabletGen3:rvnLENOVO:rn20KJCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone: dmi.product.family: ThinkPad X1 Tablet Gen 3 dmi.product.name: 20KJCTO1WW dmi.product.sku: LENOVO_MT_20KJ_BU_Think_FM_ThinkPad X1 Tablet Gen 3 dmi.product.version: ThinkPad X1 Tablet Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891062/+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 1891062] Re: Lenovo X1 Tablet Gen3 trackpoint and buttons not working
apport information ** Package changed: ubuntu => linux (Ubuntu) ** Tags added: apport-collected staging ** Description changed: Upon clean install of Ubuntu 20.04 LTS my trackpoint and trackpad buttons are not working. From my investigation, a patch has been applied to the 5.4.y branch (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=8d5037dca7c2089f27e5903c2aecfc5bb10d7806). I followed the steps listed in here: https://github.com/da-cali/linux-x1-tablet#fix-the-trackpoint-and-trackpad-buttons using v5.4.57, but now my GRUB has two options: * Ubuntu w/ 5.4.57+ (not working. Stuck "Loading initial ramdisk") * Ubuntu w/ 5.4.0-42-generic (working) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 12:53:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.6 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: justin 1392 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-08-10 (0 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + MachineType: LENOVO 20KJCTO1WW + Package: linux (not installed) + 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=/boot/vmlinuz-5.4.0-42-generic root=UUID=5187b79d-6bc7-455c-9c28-0876bcb85a3b ro quiet splash + ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 + 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 + StagingDrivers: ipu3_imgu + Tags: focal staging + Uname: Linux 5.4.0-42-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/28/2019 + dmi.bios.vendor: LENOVO + dmi.bios.version: N1ZET79W(1.35 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20KJCTO1WW + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40697 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 32 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvnLENOVO:bvrN1ZET79W(1.35):bd11/28/2019:svnLENOVO:pn20KJCTO1WW:pvrThinkPadX1TabletGen3:rvnLENOVO:rn20KJCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrNone: + dmi.product.family: ThinkPad X1 Tablet Gen 3 + dmi.product.name: 20KJCTO1WW + dmi.product.sku: LENOVO_MT_20KJ_BU_Think_FM_ThinkPad X1 Tablet Gen 3 + dmi.product.version: ThinkPad X1 Tablet Gen 3 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1891062/+attachment/5400430/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891062 Title: Lenovo X1 Tablet Gen3 trackpoint and buttons not working Status in linux package in Ubuntu: Confirmed Bug description: Upon clean install of Ubuntu 20.04 LTS my trackpoint and trackpad buttons are not working. From my investigation, a patch has been applied to the 5.4.y branch (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=8d5037dca7c2089f27e5903c2aecfc5bb10d7806). I followed the steps listed in here: https://github.com/da-cali/linux-x1-tablet#fix-the-trackpoint-and-trackpad-buttons using v5.4.57, but now my GRUB has two options: * Ubuntu w/ 5.4.57+ (not working. Stuck "Loading initial ramdisk") * Ubuntu w/ 5.4.0-42-generic (working) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 12:53:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-08-10 (0 days ago)
[Kernel-packages] [Bug 1812620] Re: msg_zerocopy.sh in net from ubuntu_kernel_selftests failed
** Changed in: ubuntu-kernel-tests Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1812620 Title: msg_zerocopy.sh in net from ubuntu_kernel_selftests failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in linux source package in Disco: Won't Fix Status in linux-aws source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-azure source package in Eoan: Won't Fix Status in linux source package in Focal: Fix Committed Status in linux-aws source package in Focal: New Status in linux-azure source package in Focal: New Bug description: == SRU Justification [ FOCAL ] == The msg_zerocopy.sh kernel self test will fail on machines that don't have 2 or 3 CPUs such as 1 CPU cloud instances since the C test program tries to set CPU affinity to CPUs 2 and 3 and bails out if it fails. == Fix == Upstream linux-next commit commit 16f6458f2478b55e2b628797bc81a4455045c74e Author: Willem de Bruijn Date: Wed Aug 5 04:40:45 2020 -0400 selftests/net: relax cpu affinity requirement in msg_zerocopy test The fix now just emits a warning that CPU affinity can't be set rather than cause an exit(1) termination. == Test cast == Run the msg_zerocopy.sh test from the kernel net selftest on a 1 CPU system. Without the fix the test fails. With the fix it runs successfully as expected. == Regression Potential == The original test pinned the CPUs for a benchmarking metric, for our testing we are using this to test to see if the operations in the test work successfully. There is a potential that users using this test will not notice the warning if they are using this test as a benchmark on a 1 CPU system and may get more jittery timing in their benchmarks rather than a test failing and complaining they are not running it on a suitable multi-CPU system. However, the likelyhood of a user using this test on a single CPU system for benchmarking is small and as it stands the test will now run and produce potentially jittery benchmarks on a 1 CPU system compared to previously where it never ran. This test will return 1 $ sudo ./msg_zerocopy.sh ipv4 tcp -t 1 ./msg_zerocopy: setaffinity 2 ./msg_zerocopy: setaffinity 3 $ echo $? 1 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: User Name 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 21 07:41 seq crw-rw 1 root audio 116, 33 Jan 21 07:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jan 21 07:50:33 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.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/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812620/+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 1891062] [NEW] Lenovo X1 Tablet Gen3 trackpoint and buttons not working
You have been subscribed to a public bug: Upon clean install of Ubuntu 20.04 LTS my trackpoint and trackpad buttons are not working. From my investigation, a patch has been applied to the 5.4.y branch (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.4.y=8d5037dca7c2089f27e5903c2aecfc5bb10d7806). I followed the steps listed in here: https://github.com/da-cali/linux-x1-tablet#fix-the-trackpoint-and-trackpad-buttons using v5.4.57, but now my GRUB has two options: * Ubuntu w/ 5.4.57+ (not working. Stuck "Loading initial ramdisk") * Ubuntu w/ 5.4.0-42-generic (working) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) 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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 10 12:53:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-08-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 -- Lenovo X1 Tablet Gen3 trackpoint and buttons not working https://bugs.launchpad.net/bugs/1891062 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891064] [NEW] Focal update: v5.4.57 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.57 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- 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/1891064 Title: Focal update: v5.4.57 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.57 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891064/+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 1891063] [NEW] Focal update: v5.4.56 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.56 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- 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/1891063 Title: Focal update: v5.4.56 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.56 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891063/+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 1812620] Re: msg_zerocopy.sh in net from ubuntu_kernel_selftests failed
Ran the tests with -proposed kernel on a 1 CPU system, tests now pass: 17:52:02 DEBUG| [stdout] # OK. All tests passed 17:52:02 DEBUG| [stdout] ok 21 selftests: net: msg_zerocopy.sh ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1812620 Title: msg_zerocopy.sh in net from ubuntu_kernel_selftests failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in linux source package in Disco: Won't Fix Status in linux-aws source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-azure source package in Eoan: Won't Fix Status in linux source package in Focal: Fix Committed Status in linux-aws source package in Focal: New Status in linux-azure source package in Focal: New Bug description: == SRU Justification [ FOCAL ] == The msg_zerocopy.sh kernel self test will fail on machines that don't have 2 or 3 CPUs such as 1 CPU cloud instances since the C test program tries to set CPU affinity to CPUs 2 and 3 and bails out if it fails. == Fix == Upstream linux-next commit commit 16f6458f2478b55e2b628797bc81a4455045c74e Author: Willem de Bruijn Date: Wed Aug 5 04:40:45 2020 -0400 selftests/net: relax cpu affinity requirement in msg_zerocopy test The fix now just emits a warning that CPU affinity can't be set rather than cause an exit(1) termination. == Test cast == Run the msg_zerocopy.sh test from the kernel net selftest on a 1 CPU system. Without the fix the test fails. With the fix it runs successfully as expected. == Regression Potential == The original test pinned the CPUs for a benchmarking metric, for our testing we are using this to test to see if the operations in the test work successfully. There is a potential that users using this test will not notice the warning if they are using this test as a benchmark on a 1 CPU system and may get more jittery timing in their benchmarks rather than a test failing and complaining they are not running it on a suitable multi-CPU system. However, the likelyhood of a user using this test on a single CPU system for benchmarking is small and as it stands the test will now run and produce potentially jittery benchmarks on a 1 CPU system compared to previously where it never ran. This test will return 1 $ sudo ./msg_zerocopy.sh ipv4 tcp -t 1 ./msg_zerocopy: setaffinity 2 ./msg_zerocopy: setaffinity 3 $ echo $? 1 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: User Name 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 21 07:41 seq crw-rw 1 root audio 116, 33 Jan 21 07:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jan 21 07:50:33 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.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/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1891020] Re: iptable_filter and ip6table_filter cannot be loaded with 5.8 kernel
Can you load the modules using insmod? E.g. 'insmod
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/iptable_filter.ko'
--
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/1891020
Title:
iptable_filter and ip6table_filter cannot be loaded with 5.8 kernel
Status in linux package in Ubuntu:
Incomplete
Bug description:
Ubuntu groovy
linux-modules-5.8.0-12-generic 5.8.0-12.13
# uname -r
5.8.0-12-generic
After reboot,
1) no IPv4 iptable kernel module are loaded:
# lsmod|grep iptable
#
2) all IPv4 iptable kernel modules are present:
# find /lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter -name
"iptable_*"
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/iptable_filter.ko
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/iptable_nat.ko
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/iptable_mangle.ko
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/iptable_raw.ko
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/iptable_security.ko
3) No IPv4 iptable kernel modules can be loaded:
# for module in iptable_filter iptable_nat iptable_mangle; do modprobe
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/${module}.ko; done
modprobe: FATAL: Module
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/iptable_filter.ko not
found in directory /lib/modules/5.8.0-12-generic
modprobe: FATAL: Module
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/iptable_nat.ko not
found in directory /lib/modules/5.8.0-12-generic
modprobe: FATAL: Module
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/iptable_mangle.ko not
found in directory /lib/modules/5.8.0-12-generic
4) Same issue after re-creating the module dependency:
# depmod
# for module in iptable_filter iptable_nat iptable_mangle; do modprobe
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/${module}.ko; done
modprobe: FATAL: Module
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/iptable_filter.ko not
found in directory /lib/modules/5.8.0-12-generic
modprobe: FATAL: Module
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/iptable_nat.ko not
found in directory /lib/modules/5.8.0-12-generic
modprobe: FATAL: Module
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/iptable_mangle.ko not
found in directory /lib/modules/5.8.0-12-generic
No such issue with linux-modules-5.4.0-42-generic.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891020/+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'
@Niko since you have an S145 you might want to try this: https://www.reddit.com/r/linuxquestions/comments/f9h0q4/touchpad_issue_lenovo_s14515iil/ Just adding the "i8042.nopnp=1 pci=nocrs" kernel parameters to grub made the touchpad work on a IdeaPad S145-15IIL 81W80025YA I had in my hands. However, the above does not work on a ThinkBook 15IIL. -- 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 1891020] Re: iptable_filter and ip6table_filter cannot be loaded with 5.8 kernel
I cannot confirm this with the 5.8.0-12 kernel. Eg, with the 5.4 kernel
in groovy, things work fine:
$ cat /proc/version_signature
Ubuntu 5.4.0-42.46-generic 5.4.44
$ sudo modprobe iptable_filter
$ sudo modprobe ip6table_filter
$ lsmod|grep table_filter
ip6table_filter16384 0
ip6_tables 32768 1 ip6table_filter
iptable_filter 16384 0
ip_tables 32768 1 iptable_filter
x_tables 40960 4
ip6table_filter,iptable_filter,ip6_tables,ip_tables
and booting into the current 5.8 kernel in groovy-proposed, it still
works ok:
$ cat /proc/version_signature
Ubuntu 5.8.0-12.13-generic 5.8.0-rc7
$ lsmod|grep table_filter
$ sudo modprobe iptable_filter
$ sudo modprobe ip6table_filter
$ lsmod|grep table_filter
ip6table_filter16384 0
ip6_tables 32768 1 ip6table_filter
iptable_filter 16384 0
ip_tables 32768 1 iptable_filter
x_tables 45056 4
ip6table_filter,iptable_filter,ip6_tables,ip_tables
I upgraded to this kernel by using 'sudo apt-get install linux-generic'.
Did you fetch all the necessary packages?
Eg, in my non-secure-boot VM:
ii linux-generic 5.8.0.12.14
amd64Complete Generic Linux kernel and headers
ii linux-headers-5.8.0-12 5.8.0-12.13
all Header files related to Linux kernel version 5.8.0
ii linux-headers-5.8.0-12-generic 5.8.0-12.13
amd64Linux kernel headers for version 5.8.0 on 64 bit x86 SMP
ii linux-headers-generic 5.8.0.12.14
amd64Generic Linux kernel headers
ii linux-image-5.8.0-12-generic 5.8.0-12.13
amd64Signed kernel image generic
ii linux-image-generic5.8.0.12.14
amd64Generic Linux kernel image
ii linux-modules-5.8.0-12-generic 5.8.0-12.13
amd64Linux kernel extra modules for version 5.8.0 on 64 bit x86 SMP
ii linux-modules-extra-5.8.0-12-generic 5.8.0-12.13
amd64Linux kernel extra modules for version 5.8.0 on 64 bit x86 SMP
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
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/1891020
Title:
iptable_filter and ip6table_filter cannot be loaded with 5.8 kernel
Status in linux package in Ubuntu:
Incomplete
Bug description:
Ubuntu groovy
linux-modules-5.8.0-12-generic 5.8.0-12.13
# uname -r
5.8.0-12-generic
After reboot,
1) no IPv4 iptable kernel module are loaded:
# lsmod|grep iptable
#
2) all IPv4 iptable kernel modules are present:
# find /lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter -name
"iptable_*"
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/iptable_filter.ko
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/iptable_nat.ko
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/iptable_mangle.ko
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/iptable_raw.ko
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/iptable_security.ko
3) No IPv4 iptable kernel modules can be loaded:
# for module in iptable_filter iptable_nat iptable_mangle; do modprobe
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/${module}.ko; done
modprobe: FATAL: Module
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/iptable_filter.ko not
found in directory /lib/modules/5.8.0-12-generic
modprobe: FATAL: Module
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/iptable_nat.ko not
found in directory /lib/modules/5.8.0-12-generic
modprobe: FATAL: Module
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/iptable_mangle.ko not
found in directory /lib/modules/5.8.0-12-generic
4) Same issue after re-creating the module dependency:
# depmod
# for module in iptable_filter iptable_nat iptable_mangle; do modprobe
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/${module}.ko; done
modprobe: FATAL: Module
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/iptable_filter.ko not
found in directory /lib/modules/5.8.0-12-generic
modprobe: FATAL: Module
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/iptable_nat.ko not
found in directory /lib/modules/5.8.0-12-generic
modprobe: FATAL: Module
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/iptable_mangle.ko not
found in directory /lib/modules/5.8.0-12-generic
No such issue with linux-modules-5.4.0-42-generic.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891020/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
