[Kernel-packages] [Bug 2055805] Re: touchpad not working with kernel 6.8
@arighi Yes it's working with 6.8.0-22.22. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2055805 Title: touchpad not working with kernel 6.8 Status in linux package in Ubuntu: Confirmed Bug description: After the standard update procedure and installation of a new version of the kernel, the touchpad on the MacBook Pro 13 - 2014 stopped working. Even the mouse cursor does not appear on the screen. If you select the old kernel version 6.6 in the bootloader options, then everything works correctly Ubuntu 24.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Mar 3 11:11:43 2024 InstallationDate: Installed on 2023-11-06 (118 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Apple Inc. MacBookPro11,1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.6.0-14-generic root=UUID=2075733d-58de-4836-9c71-04dd00378200 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.6.0-14-generic N/A linux-backports-modules-6.6.0-14-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 430.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr430.0.0.0.0:bd12/17/2020:br0.1:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055805/+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 2055805] Re: touchpad not working with kernel 6.8
Somehow I can't get 6.8.0-20 after adding the ppa and updating. But in some way I got the 6.8.0-19 kernel now (from proposed?) and that's working fine with the touchpad. -- 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/2055805 Title: touchpad not working with kernel 6.8 Status in linux package in Ubuntu: Confirmed Bug description: After the standard update procedure and installation of a new version of the kernel, the touchpad on the MacBook Pro 13 - 2014 stopped working. Even the mouse cursor does not appear on the screen. If you select the old kernel version 6.6 in the bootloader options, then everything works correctly Ubuntu 24.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Mar 3 11:11:43 2024 InstallationDate: Installed on 2023-11-06 (118 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Apple Inc. MacBookPro11,1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.6.0-14-generic root=UUID=2075733d-58de-4836-9c71-04dd00378200 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.6.0-14-generic N/A linux-backports-modules-6.6.0-14-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 430.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr430.0.0.0.0:bd12/17/2020:br0.1:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055805/+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 2055805] Re: touchpad not working with kernel 6.8
Latest mainline build of kernel 6.8.1 is working. Touchpad on MacbookPro 2012 is working now. Thanks! This kernel is coming to Ubuntu 24.04? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2055805 Title: touchpad not working with kernel 6.8 Status in linux package in Ubuntu: Confirmed Bug description: After the standard update procedure and installation of a new version of the kernel, the touchpad on the MacBook Pro 13 - 2014 stopped working. Even the mouse cursor does not appear on the screen. If you select the old kernel version 6.6 in the bootloader options, then everything works correctly Ubuntu 24.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Mar 3 11:11:43 2024 InstallationDate: Installed on 2023-11-06 (118 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Apple Inc. MacBookPro11,1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.6.0-14-generic root=UUID=2075733d-58de-4836-9c71-04dd00378200 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.6.0-14-generic N/A linux-backports-modules-6.6.0-14-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 430.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr430.0.0.0.0:bd12/17/2020:br0.1:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055805/+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 2055805] Re: touchpad do not working with kernel 6.8
** Summary changed: - tochpad do not working with kernel 6.8 + touchpad do not working with kernel 6.8 ** Summary changed: - touchpad do not working with kernel 6.8 + touchpad not working with kernel 6.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/2055805 Title: touchpad not working with kernel 6.8 Status in linux package in Ubuntu: Confirmed Bug description: After the standard update procedure and installation of a new version of the kernel, the touchpad on the MacBook Pro 13 - 2014 stopped working. Even the mouse cursor does not appear on the screen. If you select the old kernel version 6.6 in the bootloader options, then everything works correctly Ubuntu 24.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Mar 3 11:11:43 2024 InstallationDate: Installed on 2023-11-06 (118 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Apple Inc. MacBookPro11,1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.6.0-14-generic root=UUID=2075733d-58de-4836-9c71-04dd00378200 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.6.0-14-generic N/A linux-backports-modules-6.6.0-14-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 430.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr430.0.0.0.0:bd12/17/2020:br0.1:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055805/+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 2055805] Re: tochpad do not working with kernel 6.8
Same problem (and solution) for MacBook Pro 2012 -- 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/2055805 Title: tochpad do not working with kernel 6.8 Status in linux package in Ubuntu: Confirmed Bug description: After the standard update procedure and installation of a new version of the kernel, the touchpad on the MacBook Pro 13 - 2014 stopped working. Even the mouse cursor does not appear on the screen. If you select the old kernel version 6.6 in the bootloader options, then everything works correctly Ubuntu 24.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Mar 3 11:11:43 2024 InstallationDate: Installed on 2023-11-06 (118 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Apple Inc. MacBookPro11,1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.6.0-14-generic root=UUID=2075733d-58de-4836-9c71-04dd00378200 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.6.0-14-generic N/A linux-backports-modules-6.6.0-14-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 430.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr430.0.0.0.0:bd12/17/2020:br0.1:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055805/+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 1983519] Re: [linux 5.19] rcu_preempt detected expedited stalls on CPUs/tasks: { 0-... } 272 jiffies s: 49 root: 0x1/.
I'm experiencing the same issue.
I am running Ubuntu 20.04 with kernel 5.19.7-051907-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1983519
Title:
[linux 5.19] rcu_preempt detected expedited stalls on CPUs/tasks: {
0-... } 272 jiffies s: 49 root: 0x1/.
Status in linux package in Ubuntu:
Confirmed
Bug description:
A lot of traces in dmesg from RCU in released 5.19.0-051900-generic
(from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.19/):
[ 11.878971] rcu: INFO: rcu_preempt detected expedited stalls on
CPUs/tasks: { 0-... } 6 jiffies s: 49 root: 0x1/.
[ 11.879016] rcu: blocking rcu_node structures (internal RCU debug):
[ 11.879037] Task dump for CPU 0:
[ 11.879038] task:systemd-udevd state:R running task stack:0
pid: 383 ppid: 357 flags:0x400a
[ 11.879043] Call Trace:
[ 11.879045]
[ 11.879050] ? find_kallsyms_symbol+0x92/0x1a0
[ 11.879056] ? amdgpu_ras_query_err_status+0x100/0x100 [amdgpu]
[ 11.879370] ? xgpu_ai_request_full_gpu_access+0x20/0x20 [amdgpu]
[ 11.879590] ? module_address_lookup+0x68/0xc0
[ 11.879593] ? xgpu_ai_request_init_data+0x50/0x50 [amdgpu]
[ 11.879813] ? kallsyms_lookup_buildid+0xf7/0x180
[ 11.879817] ? kallsyms_lookup+0x14/0x20
[ 11.879819] ? test_for_valid_rec+0x38/0x80
[ 11.879822] ? change_page_attr_set_clr+0x150/0x1c0
[ 11.879826] ? ftrace_module_enable+0xa6/0x210
[ 11.879829] ? load_module+0xa93/0xd30
[ 11.879831] ? security_kernel_post_read_file+0x5c/0x70
[ 11.879834] ? kernel_read_file+0x230/0x290
[ 11.879837] ? __do_sys_finit_module+0xc8/0x140
[ 11.879839] ? __do_sys_finit_module+0xc8/0x140
[ 11.879842] ? __x64_sys_finit_module+0x18/0x20
[ 11.879844] ? do_syscall_64+0x5c/0x90
[ 11.879848] ? entry_SYSCALL_64_after_hwframe+0x63/0xcd
[ 11.879851]
[ 11.954966] rcu: INFO: rcu_preempt detected expedited stalls on
CPUs/tasks: { 0-... } 25 jiffies s: 49 root: 0x1/.
[ 11.955002] rcu: blocking rcu_node structures (internal RCU debug):
[ 11.955022] Task dump for CPU 0:
[ 11.955023] task:systemd-udevd state:R running task stack:0
pid: 383 ppid: 357 flags:0x400a
[ 11.955027] Call Trace:
[ 11.955028]
[ 11.955030] ? find_kallsyms_symbol+0x9a/0x1a0
[ 11.955033] ? amdgpu_ras_query_err_status+0x100/0x100 [amdgpu]
[ 11.955249] ? tonga_ih_check_soft_reset+0x60/0x60 [amdgpu]
[ 11.955474] ? module_address_lookup+0x68/0xc0
[ 11.955476] ? tonga_ih_disable_interrupts+0x70/0x70 [amdgpu]
[ 11.955701] ? kallsyms_lookup_buildid+0xf7/0x180
[ 11.955704] ? kallsyms_lookup+0x14/0x20
[ 11.955707] ? test_for_valid_rec+0x38/0x80
[ 11.955710] ? change_page_attr_set_clr+0x150/0x1c0
[ 11.955713] ? ftrace_module_enable+0xa6/0x210
[ 11.955715] ? load_module+0xa93/0xd30
[ 11.955717] ? security_kernel_post_read_file+0x5c/0x70
[ 11.955719] ? kernel_read_file+0x230/0x290
[ 11.955722] ? __do_sys_finit_module+0xc8/0x140
[ 11.955724] ? __do_sys_finit_module+0xc8/0x140
[ 11.955727] ? __x64_sys_finit_module+0x18/0x20
[ 11.955729] ? do_syscall_64+0x5c/0x90
[ 11.955732] ? entry_SYSCALL_64_after_hwframe+0x63/0xcd
[ 11.955735]
[ 12.030963] rcu: INFO: rcu_preempt detected expedited stalls on
CPUs/tasks: { 0-... } 44 jiffies s: 49 root: 0x1/.
[ 12.031003] rcu: blocking rcu_node structures (internal RCU debug):
[ 12.031025] Task dump for CPU 0:
[ 12.031027] task:systemd-udevd state:R running task stack:0
pid: 383 ppid: 357 flags:0x400a
[ 12.031031] Call Trace:
[ 12.031033]
[ 12.031035] ? find_kallsyms_symbol+0x92/0x1a0
[ 12.031040] ? amdgpu_ras_query_err_status+0x100/0x100 [amdgpu]
[ 12.031326] ? gfx_v9_0_fault.isra.0+0xd0/0xd0 [amdgpu]
[ 12.031634] ? module_address_lookup+0x68/0xc0
[ 12.031638] ? gfx_v9_0_set_clockgating_state+0xe0/0xe0 [amdgpu]
[ 12.031945] ? kallsyms_lookup_buildid+0xf7/0x180
[ 12.031949] ? kallsyms_lookup+0x14/0x20
[ 12.031952] ? test_for_valid_rec+0x38/0x80
[ 12.031956] ? change_page_attr_set_clr+0x150/0x1c0
[ 12.031960] ? ftrace_module_enable+0xa6/0x210
[ 12.031963] ? load_module+0xa93/0xd30
[ 12.031966] ? security_kernel_post_read_file+0x5c/0x70
[ 12.031969] ? kernel_read_file+0x230/0x290
[ 12.031972] ? __do_sys_finit_module+0xc8/0x140
[ 12.031975] ? __do_sys_finit_module+0xc8/0x140
[ 12.031979] ? __x64_sys_finit_module+0x18/0x20
[ 12.031982] ? do_syscall_64+0x5c/0x90
[ 12.031985] ? entry_SYSCALL_64_after_hwframe+0x63/0xcd
[ 12.031989]
[ 12.106963] rcu: INFO: rcu_preempt detected expedited stalls on
CPUs/tasks: { 0-... } 63 jiffies s: 49 root: 0x1/.
[ 12.107003] rcu: blocking rcu_node structures (internal RCU debug):
[ 12.107025] Task dump for
[Kernel-packages] [Bug 1792309] Re: Fix I2C touchpanels' interrupt storms after system suspend
It seems this fix also fixes the touch screen not working (no irq storm) after a suspend on an Acer Aspire Switch 11 (and possibly also other modules). See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796580 -- 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/1792309 Title: Fix I2C touchpanels' interrupt storms after system suspend Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Fix Released Bug description: [Impact] Some I2C touchpanels generate IRQ storm after system suspend/resume. [Test] After applying the fix, the IRQ storm stops generated by Raydium touchpanels. [Fix] Instead of requesting i2c reset, simply requesting the device to power on. The HID over I2C spec doesn't specify how the device should do upon resume from suspend, so some devices expect a power on instead of reset. [Regression Potential] Low. I tested other vendors' touchpanels, didn't observe any side effect. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1792309/+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 1796580] Re: Touchscreen breaks after suspend on Acer Aspire Switch 11
Good call, thanks! This turns out to be fixed in the latest mainline kernel. Looking at the git log for the i2c_hid driver, I found this commit which I suspect is the fix for my problem. https://github.com/torvalds/linux/commit/52cf93e63ee672a92f349edc6ddad86ec8808fd8 https://patchwork.kernel.org/patch/10589793/ This fix first appeared in the 4.19-rc4 kernel. I tested 4.19-rc3, which is broken while 4.19-rc4 works, which supports my suspicion. I also tested 4.15.0-37.40 (from bionic proposed), which has this same fix backported and also works. I guess this issue can be closed / marked as fix released, but I'm not sure how exactly, so I'll leave that to others. -- 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/1796580 Title: Touchscreen breaks after suspend on Acer Aspire Switch 11 Status in linux package in Ubuntu: Incomplete Bug description: I'm not entirely sure this bug belongs in package xinput, but I'm following the lead of https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1275416, which describes the same symptoms (but on other hardware, so likely a different underlying problem). On this notebook, the touchscreen works well out of the box. But as soon as I suspend (by pressing the power button or closing the lid) and resume again, the touch screen no longer works. Kernel and Xorg logs show no indication of any problem, xinput still lists the touchscreen, but it just no longer works. The touchscreen can be made to work again by reloading the hid_multitouch module (that works by unloading and reloading after a resume, or by unloading the module before suspend and reloading it after resume). I tried updating the bios from v1.03 to the latest v1.04 (no changelog available), but that did not change the problem. I'm attaching a dmesg.txt in addition to the stuff ubuntu-bug collected. In this dmesg log, I've shown a full boot, a suspend (breaking the touchscreen), a module reload (fixing the touchscreen), then a module unload, suspend and module reload, after which the touchscreen also works (I've added annotations to the log to indicate what happens when). The log also shows some USB-related errors after suspend, but that seems to be about the bluetooth adapter (looking at the usb ids), so I think these are unrelated. The touchscreen in question seems to be connected through I2c, according to dmesg: [4.561527] input: SYNA7508:00 06CB:77B2 Pen as /devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7508:00/0018:06CB:77B2.0002/input/input8 [4.561741] input: SYNA7508:00 06CB:77B2 as /devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7508:00/0018:06CB:77B2.0002/input/input9 [4.561917] hid-multitouch 0018:06CB:77B2.0002: input,hidraw1: I2C HID v1.00 Mouse [SYNA7508:00 06CB:77B2] on i2c-SYNA7508:00 I realize that this is not enough information to diagnose and fix the problem, but I'd gladly receive some suggestions on debug strategies to dig into this issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xinput 1.6.2-1build1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 19:40:05 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:0a1e] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0930] InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Acer Aspire SW5-171P ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=4893a2e6-84af-4d45-8e31-773e622c36c6 ro quiet splash vt.handoff=1 SourcePackage: xinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/7/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Longchamp_S dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd11/7/2014:svnAcer:pnAspireSW5-171P:pvrV1.04:rvnAcer:rnLongchamp_S:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Haswell-Y System dmi.product.name: Aspire SW5-171P dmi.product.version: V1.04 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
[Kernel-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets
Even with the script a shutdown/reboot takes a very long time. Any expectations when a fix will be ready? I hit this all the time on 2 installed servers. -- 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/1569925 Title: Shutdown hang on 16.04 with iscsi targets Status in linux package in Ubuntu: In Progress Status in open-iscsi package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in open-iscsi source package in Xenial: In Progress Status in linux source package in Zesty: In Progress Status in open-iscsi source package in Zesty: In Progress Status in linux source package in Artful: In Progress Status in open-iscsi source package in Artful: In Progress Bug description: I have 4 servers running the latest 16.04 updates from the development branch (as of right now). Each server is connected to NetApp storage using iscsi software initiator. There are a total of 56 volumes spread across two NetApp arrays. Each volume has 4 paths available to it which are being managed by device mapper. While logged into the iscsi sessions all I have to do is reboot the server and I get a hang. I see a message that says: "Reached target Shutdown" followed by "systemd-shutdown[1]: Failed to finalize DM devices, ignoring" and then I see 8 lines that say: "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" NOTE: the actual values of the *'s differ for each line above. This seems like a bug somewhere but I am unaware of any additional logging that I could turn on to pinpoint the problem. Note I also have similar setups that are not doing iscsi and they don't have this problem. Here is a screenshot of what I see on the shell when I try to reboot: (https://launchpadlibrarian.net/291303059/Screenshot.jpg) This is being tracked in NetApp bug tracker CQ number 860251. If I log out of all iscsi sessions before rebooting then I do not experience the hang: iscsiadm -m node -U all We are wondering if this could be some kind of shutdown ordering problem. Like the network devices have already disappeared and then iscsi tries to perform some operation (hence the ping timeouts). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1569925/+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
