[Kernel-packages] [Bug 1235649] Re: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch
The above can be applied straight on device, in /usr/share/unity8/. -- 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/1235649 Title: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch Status in “linux” package in Ubuntu: Incomplete Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Incomplete Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Confirmed Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235649/+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 1332885] [NEW] [Apple Inc. MacBookAir5, 1] suspend/resume failure
Public bug reported: The machine fails to suspend every 1 in 5 times or so, after rebooting forcefully this report is created. This forum user reports the same, suggesting the video driver (switching to vt before suspend seems to work around it for him). http://ubuntuforums.org/showthread.php?t=2224410 This is really frustrating as it drains battery while you think it's asleep... ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1423 F pulseaudio ola2266 F pulseaudio Date: Sun Jun 22 00:20:50 2014 DuplicateSignature: suspend/resume:Apple Inc. MacBookAir5,1:MBA51.88Z.00EF.B02.1211271028 ExecutablePath: /usr/share/apport/apportcheckresume ExecutableTimestamp: 1400281919 Failure: suspend/resume InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookAir5,1 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcCwd: / ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-29-generic root=UUID=b5d11eef-0dcc-4d93-b8ab-4d4cb808f5ac ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux Title: [Apple Inc. MacBookAir5,1] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/27/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA51.88Z.00EF.B02.1211271028 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-66F35F19FE2A0D05 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir5,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-66F35F19FE2A0D05 dmi.modalias: dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B02.1211271028:bd11/27/2012:svnAppleInc.:pnMacBookAir5,1:pvr1.0:rvnAppleInc.:rnMac-66F35F19FE2A0D05:rvrMacBookAir5,1:cvnAppleInc.:ct10:cvrMac-66F35F19FE2A0D05: dmi.product.name: MacBookAir5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kerneloops need-duplicate-check resume suspend trusty -- 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/1332885 Title: [Apple Inc. MacBookAir5,1] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: The machine fails to suspend every 1 in 5 times or so, after rebooting forcefully this report is created. This forum user reports the same, suggesting the video driver (switching to vt before suspend seems to work around it for him). http://ubuntuforums.org/showthread.php?t=2224410 This is really frustrating as it drains battery while you think it's asleep... ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1423 F pulseaudio ola2266 F pulseaudio Date: Sun Jun 22 00:20:50 2014 DuplicateSignature: suspend/resume:Apple Inc. MacBookAir5,1:MBA51.88Z.00EF.B02.1211271028 ExecutablePath: /usr/share/apport/apportcheckresume ExecutableTimestamp: 1400281919 Failure: suspend/resume InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookAir5,1 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcCwd: / ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-29-generic root=UUID=b5d11eef-0dcc-4d93-b8ab-4d4cb808f5ac ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux Title: [Apple Inc. MacBookAir5,1] suspend/resume
[Kernel-packages] [Bug 1332885] Re: [Apple Inc. MacBookAir5, 1] suspend/resume failure
** Description changed: The machine fails to suspend every 1 in 5 times or so, after rebooting forcefully this report is created. This forum user reports the same, suggesting the video driver (switching to vt before suspend seems to work around it for him). + + http://ubuntuforums.org/showthread.php?t=2224410 This is really frustrating as it drains battery while you think it's asleep... ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: lightdm1423 F pulseaudio - ola2266 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: lightdm1423 F pulseaudio + ola2266 F pulseaudio Date: Sun Jun 22 00:20:50 2014 DuplicateSignature: suspend/resume:Apple Inc. MacBookAir5,1:MBA51.88Z.00EF.B02.1211271028 ExecutablePath: /usr/share/apport/apportcheckresume ExecutableTimestamp: 1400281919 Failure: suspend/resume InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookAir5,1 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcCwd: / ProcEnviron: - TERM=linux - PATH=(custom, no user) + TERM=linux + PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-29-generic root=UUID=b5d11eef-0dcc-4d93-b8ab-4d4cb808f5ac ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-3.13.0-29-generic N/A - linux-backports-modules-3.13.0-29-generic N/A - linux-firmware 1.127.2 + linux-restricted-modules-3.13.0-29-generic N/A + linux-backports-modules-3.13.0-29-generic N/A + linux-firmware 1.127.2 SourcePackage: linux Title: [Apple Inc. MacBookAir5,1] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: - + dmi.bios.date: 11/27/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA51.88Z.00EF.B02.1211271028 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-66F35F19FE2A0D05 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir5,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-66F35F19FE2A0D05 dmi.modalias: dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B02.1211271028:bd11/27/2012:svnAppleInc.:pnMacBookAir5,1:pvr1.0:rvnAppleInc.:rnMac-66F35F19FE2A0D05:rvrMacBookAir5,1:cvnAppleInc.:ct10:cvrMac-66F35F19FE2A0D05: dmi.product.name: MacBookAir5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. -- 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/1332885 Title: [Apple Inc. MacBookAir5,1] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: The machine fails to suspend every 1 in 5 times or so, after rebooting forcefully this report is created. This forum user reports the same, suggesting the video driver (switching to vt before suspend seems to work around it for him). http://ubuntuforums.org/showthread.php?t=2224410 This is really frustrating as it drains battery while you think it's asleep... ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1423 F pulseaudio ola2266 F pulseaudio Date: Sun Jun 22 00:20:50 2014 DuplicateSignature: suspend/resume:Apple Inc. MacBookAir5,1:MBA51.88Z.00EF.B02.1211271028 ExecutablePath: /usr/share/apport/apportcheckresume ExecutableTimestamp: 1400281919 Failure: suspend/resume InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookAir5,1 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcCwd: / ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-29-generic root=UUID=b5d11eef-0dcc-4d93-b8ab-4d4cb808f5ac ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
[Kernel-packages] [Bug 1362694] [NEW] Can't pair with car kit (reverse mode)
Private bug reported: My car kit is the party initiating the connection when pairing with the phone. But the request fails, no PIN dialog is displayed and the kit says that pairing failed. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: bluez 4.101-0ubuntu19 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.6-0ubuntu2 Architecture: armhf CurrentDmesg: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Aug 28 16:25:44 2014 InstallationDate: Installed on 2014-08-28 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140828-030204) Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' ProcKernelCmdLine: console=ttyMT0,921600n1 vmalloc=496M slub_max_order=0 lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=2665 bootprof.lk_t=1663 printk.disable_uart=0 boot_reason=4 datapart=/dev/mmcblk0p7 systempart=/dev/mmcblk0p6 androidboot.serialno=JB011540 lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=2665 bootprof.lk_t=1663 printk.disable_uart=0 boot_reason=4 datapart=/dev/mmcblk0p7 systempart=/dev/mmcblk0p6 androidboot.serialno=JB011540 ProcModules: SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) hciconfig: hci0: Type: BR/EDR Bus: UART BD Address: B8:64:91:48:2B:21 ACL MTU: 1021:4 SCO MTU: 184:1 UP RUNNING PSCAN RX bytes:3229 acl:65 sco:0 events:147 errors:0 TX bytes:3516 acl:66 sco:0 commands:46 errors:0 syslog: ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: 14.09 apport-bug armhf ** Information type changed from Public to Private -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1362694 Title: Can't pair with car kit (reverse mode) Status in “bluez” package in Ubuntu: New Bug description: My car kit is the party initiating the connection when pairing with the phone. But the request fails, no PIN dialog is displayed and the kit says that pairing failed. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: bluez 4.101-0ubuntu19 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.6-0ubuntu2 Architecture: armhf CurrentDmesg: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Aug 28 16:25:44 2014 InstallationDate: Installed on 2014-08-28 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140828-030204) Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' ProcKernelCmdLine: console=ttyMT0,921600n1 vmalloc=496M slub_max_order=0 lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=2665 bootprof.lk_t=1663 printk.disable_uart=0 boot_reason=4 datapart=/dev/mmcblk0p7 systempart=/dev/mmcblk0p6 androidboot.serialno=JB011540 lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=2665 bootprof.lk_t=1663 printk.disable_uart=0 boot_reason=4 datapart=/dev/mmcblk0p7 systempart=/dev/mmcblk0p6 androidboot.serialno=JB011540 ProcModules: SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) hciconfig: hci0:Type: BR/EDR Bus: UART BD Address: B8:64:91:48:2B:21 ACL MTU: 1021:4 SCO MTU: 184:1 UP RUNNING PSCAN RX bytes:3229 acl:65 sco:0 events:147 errors:0 TX bytes:3516 acl:66 sco:0 commands:46 errors:0 syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1362694/+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 1389592] [NEW] [Dell Inc. XPS 12-9Q33] suspend/resume failure
Public bug reported: Related to bug #1389589 I think, my laptop started hanging on suspend from time to time. ProblemType: KernelOops DistroRelease: Ubuntu 15.04 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 3023 F pulseaudio /dev/snd/controlC0: michal 3023 F pulseaudio Date: Wed Nov 5 10:25:33 2014 DuplicateSignature: suspend/resume:Dell Inc. XPS 12-9Q33:A06 ExecutablePath: /usr/share/apport/apportcheckresume ExecutableTimestamp: 1415063431 Failure: suspend/resume HibernationDevice: RESUME=/dev/mapper/sda3_crypt InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. XPS 12-9Q33 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcCwd: / ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=f6fef09e-9f1a-40ad-aeaa-7d7a67fb86f2 ro rootflags=subvol=@ splash quiet vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 SourcePackage: linux Title: [Dell Inc. XPS 12-9Q33] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/15/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/15/2014:svnDellInc.:pnXPS12-9Q33:pvrA06:rvnDellInc.:rnXPS12-9Q33:rvrA06:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops need-duplicate-check resume suspend -- 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/1389592 Title: [Dell Inc. XPS 12-9Q33] suspend/resume failure Status in “linux” package in Ubuntu: New Bug description: Related to bug #1389589 I think, my laptop started hanging on suspend from time to time. ProblemType: KernelOops DistroRelease: Ubuntu 15.04 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 3023 F pulseaudio /dev/snd/controlC0: michal 3023 F pulseaudio Date: Wed Nov 5 10:25:33 2014 DuplicateSignature: suspend/resume:Dell Inc. XPS 12-9Q33:A06 ExecutablePath: /usr/share/apport/apportcheckresume ExecutableTimestamp: 1415063431 Failure: suspend/resume HibernationDevice: RESUME=/dev/mapper/sda3_crypt InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. XPS 12-9Q33 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcCwd: / ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=f6fef09e-9f1a-40ad-aeaa-7d7a67fb86f2 ro rootflags=subvol=@ splash quiet vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 SourcePackage: linux Title: [Dell Inc. XPS 12-9Q33] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/15/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/15/2014:svnDellInc.:pnXPS12-9Q33:pvrA06:rvnDellInc.:rnXPS12-9Q33:rvrA06:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1389592/+subscriptions -- Mailing
[Kernel-packages] [Bug 1389592] Re: [Dell Inc. XPS 12-9Q33] suspend/resume failure
I actually have yet to reproduce this issue. What does happen seems to be a compiz issue instead. I'll make sure to follow up on this bug if it resurfaces. -- 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/1389592 Title: [Dell Inc. XPS 12-9Q33] suspend/resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: Related to bug #1389589 I think, my laptop started hanging on suspend from time to time. ProblemType: KernelOops DistroRelease: Ubuntu 15.04 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 3023 F pulseaudio /dev/snd/controlC0: michal 3023 F pulseaudio Date: Wed Nov 5 10:25:33 2014 DuplicateSignature: suspend/resume:Dell Inc. XPS 12-9Q33:A06 ExecutablePath: /usr/share/apport/apportcheckresume ExecutableTimestamp: 1415063431 Failure: suspend/resume HibernationDevice: RESUME=/dev/mapper/sda3_crypt InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. XPS 12-9Q33 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcCwd: / ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=f6fef09e-9f1a-40ad-aeaa-7d7a67fb86f2 ro rootflags=subvol=@ splash quiet vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 SourcePackage: linux Title: [Dell Inc. XPS 12-9Q33] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/15/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/15/2014:svnDellInc.:pnXPS12-9Q33:pvrA06:rvnDellInc.:rnXPS12-9Q33:rvrA06:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1389592/+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 1389592] Re: [Dell Inc. XPS 12-9Q33] suspend/resume failure
OK I'm saying this is fixed in the new kernel, have been running it for some time and the suspend/resume behaviour was much more stable. When I switched to the vivid kernel (due to overlayfs incompatibility), susres was all over the place again. ** Tags added: kernel-fixed-upstream ** 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/1389592 Title: [Dell Inc. XPS 12-9Q33] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: Related to bug #1389589 I think, my laptop started hanging on suspend from time to time. ProblemType: KernelOops DistroRelease: Ubuntu 15.04 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 3023 F pulseaudio /dev/snd/controlC0: michal 3023 F pulseaudio Date: Wed Nov 5 10:25:33 2014 DuplicateSignature: suspend/resume:Dell Inc. XPS 12-9Q33:A06 ExecutablePath: /usr/share/apport/apportcheckresume ExecutableTimestamp: 1415063431 Failure: suspend/resume HibernationDevice: RESUME=/dev/mapper/sda3_crypt InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. XPS 12-9Q33 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcCwd: / ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=f6fef09e-9f1a-40ad-aeaa-7d7a67fb86f2 ro rootflags=subvol=@ splash quiet vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 SourcePackage: linux Title: [Dell Inc. XPS 12-9Q33] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/15/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/15/2014:svnDellInc.:pnXPS12-9Q33:pvrA06:rvnDellInc.:rnXPS12-9Q33:rvrA06:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1389592/+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 1362694] Re: Can't pair with car kit (reverse mode)
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1362694 Title: Can't pair with car kit (reverse mode) Status in bluez package in Ubuntu: New Bug description: My car kit is the party initiating the connection when pairing with the phone. But the request fails, no PIN dialog is displayed and the kit says that pairing failed. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: bluez 4.101-0ubuntu19 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.6-0ubuntu2 Architecture: armhf CurrentDmesg: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Aug 28 16:25:44 2014 InstallationDate: Installed on 2014-08-28 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140828-030204) Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' ProcKernelCmdLine: console=ttyMT0,921600n1 vmalloc=496M slub_max_order=0 lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=2665 bootprof.lk_t=1663 printk.disable_uart=0 boot_reason=4 datapart=/dev/mmcblk0p7 systempart=/dev/mmcblk0p6 androidboot.serialno=JB011540 lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=2665 bootprof.lk_t=1663 printk.disable_uart=0 boot_reason=4 datapart=/dev/mmcblk0p7 systempart=/dev/mmcblk0p6 androidboot.serialno=JB011540 ProcModules: SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) hciconfig: hci0:Type: BR/EDR Bus: UART BD Address: B8:64:91:48:2B:21 ACL MTU: 1021:4 SCO MTU: 184:1 UP RUNNING PSCAN RX bytes:3229 acl:65 sco:0 events:147 errors:0 TX bytes:3516 acl:66 sco:0 commands:46 errors:0 syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1362694/+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 1479445] Re: IN CAR: Signal Strength not shown in car display
I found this working in my car with rc-proposed, so it must've landed in the overlay? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1479445 Title: IN CAR: Signal Strength not shown in car display Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Fix Released Status in bluez package in Ubuntu RTM: New Bug description: STEPS: Requirement: DUT with active sim and car that supports Bluetooth phones (Skoda Superb 2013 in my case) 1. Connect the DUT to the car 2. Check the console display for the strength of signal EXPECTED: I expect the display to show a similar strength to that on the phone ACTUAL: The signal strength is always at 0% however the display does show the Network connected to so there is some sort of feedback via bluetooth that there is a connection. VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479445/+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 1506774] [NEW] package bluez 5.35-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Bluez installation fails on vivid and wily without linux-image-extra* because BT kernel modules are unavailable. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 Date: Thu Oct 15 22:06:50 2015 DuplicateSignature: package:bluez:5.35-0ubuntu1:subprocess installed post-installation script returned error exit status 1 Ec2AMI: ami-0f6e Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: cpu10-ram10-disk10-ephemeral20 Ec2Kernel: aki-022a Ec2Ramdisk: ari-022a ErrorMessage: subprocess installed post-installation script returned error exit status 1 InterestingModules: bnep bluetooth Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: dpkg 1.18.2ubuntu4 apt 1.0.10.2ubuntu1 SourcePackage: bluez Title: package bluez 5.35-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.3:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.2.3 dmi.sys.vendor: OpenStack Foundation hciconfig: ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package ec2-images wily -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1506774 Title: package bluez 5.35-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in bluez package in Ubuntu: New Bug description: Bluez installation fails on vivid and wily without linux-image-extra* because BT kernel modules are unavailable. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 Date: Thu Oct 15 22:06:50 2015 DuplicateSignature: package:bluez:5.35-0ubuntu1:subprocess installed post-installation script returned error exit status 1 Ec2AMI: ami-0f6e Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: cpu10-ram10-disk10-ephemeral20 Ec2Kernel: aki-022a Ec2Ramdisk: ari-022a ErrorMessage: subprocess installed post-installation script returned error exit status 1 InterestingModules: bnep bluetooth Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: dpkg 1.18.2ubuntu4 apt 1.0.10.2ubuntu1 SourcePackage: bluez Title: package bluez 5.35-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.3:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.2.3 dmi.sys.vendor: OpenStack Foundation hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1506774/+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 1519325] [NEW] Car kit reports "No network" when two SIMs are present but just one is online
Public bug reported: I've a second SIM that won't register because it has no roaming enabled. The car kit says "No network" even though I can make and receive calls. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 5.35+15.04.20151023-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Nov 24 13:03:40 2015 InstallationDate: Installed on 2015-11-24 (0 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20151124-020303) Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' ProcKernelCmdLine: console=ttyMT0,921600n1 vmalloc=496M slub_max_order=0 fixrtc lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=459 bootprof.lk_t=1724 printk.disable_uart=1 boot_reason=4 datapart=/dev/mmcblk0p7 systempart=/dev/mmcblk0p6 androidboot.serialno=JB011540 � lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=459 bootprof.lk_t=1724 printk.disable_uart=1 boot_reason=4 datapart=/dev/mmcblk0p7 systempart=/dev/mmcblk0p6 androidboot.serialno=JB011540 � ProcModules: SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) hciconfig: hci0: Type: BR/EDR Bus: UART BD Address: B8:64:91:48:2B:21 ACL MTU: 1021:4 SCO MTU: 184:1 UP RUNNING PSCAN RX bytes:774 acl:0 sco:0 events:53 errors:0 TX bytes:3722 acl:0 sco:0 commands:53 errors:0 syslog: ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1519325 Title: Car kit reports "No network" when two SIMs are present but just one is online Status in bluez package in Ubuntu: New Bug description: I've a second SIM that won't register because it has no roaming enabled. The car kit says "No network" even though I can make and receive calls. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 5.35+15.04.20151023-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Nov 24 13:03:40 2015 InstallationDate: Installed on 2015-11-24 (0 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20151124-020303) Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' ProcKernelCmdLine: console=ttyMT0,921600n1 vmalloc=496M slub_max_order=0 fixrtc lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=459 bootprof.lk_t=1724 printk.disable_uart=1 boot_reason=4 datapart=/dev/mmcblk0p7 systempart=/dev/mmcblk0p6 androidboot.serialno=JB011540 � lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=459 bootprof.lk_t=1724 printk.disable_uart=1 boot_reason=4 datapart=/dev/mmcblk0p7 systempart=/dev/mmcblk0p6 androidboot.serialno=JB011540 � ProcModules: SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) hciconfig: hci0:Type: BR/EDR Bus: UART BD Address: B8:64:91:48:2B:21 ACL MTU: 1021:4 SCO MTU: 184:1 UP RUNNING PSCAN RX bytes:774 acl:0 sco:0 events:53 errors:0 TX bytes:3722 acl:0 sco:0 commands:53 errors:0 syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1519325/+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 1491340] Re: Bluetooth keyboard is configured with wrong keyboard layout
This is blocked by bug #1530946 atm. ** Branch linked: lp:~jonas-drange/ubuntu-system- settings/hwKeyboardMinimal ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Also affects: avila Importance: Undecided Status: New ** Also affects: canonical-pocket-desktop Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Milestone: None => ww04-2016 ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Michał Sawicz (saviq) ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Status: New => Triaged ** Changed in: canonical-pocket-desktop Status: New => Triaged ** Changed in: canonical-pocket-desktop Importance: Undecided => High ** Changed in: canonical-pocket-desktop Assignee: (unassigned) => Michał Sawicz (saviq) ** Changed in: ubuntu-system-settings (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-system-settings (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-system-settings (Ubuntu) Assignee: (unassigned) => Jonas G. Drange (jonas-drange) ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Lukáš Tinkl (lukas-kde) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1491340 Title: Bluetooth keyboard is configured with wrong keyboard layout Status in The Avila project: New Status in Canonical System Image: Triaged Status in canonical-pocket-desktop: Triaged Status in bluez package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Triaged Bug description: Phone: Meizu MX4 (15.04 r4) OS Language: German What you expected to happen: When connecting a Bluetooth keyboard I expect that the keyboard layout is the same as the keyboard hardware key layout (German) or that it is possible to change the keyboard layout in the Bluetooth setting for the connected Bluetooth device. What happened instead: The Bluetooth keyboard worked, but wasn't set to German key layout. In the Bluetooth device setting I couldn't find any option to change the Bluetooth keyboard key layout. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1491340/+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 1491340] Re: Bluetooth keyboard is configured with wrong keyboard layout
** Changed in: unity8 (Ubuntu) Status: Confirmed => Triaged ** Changed in: unity8 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1491340 Title: Bluetooth keyboard is configured with wrong keyboard layout Status in Canonical System Image: New Status in bluez package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: New Status in unity8 package in Ubuntu: Triaged Bug description: Phone: Meizu MX4 (15.04 r4) OS Language: German What you expected to happen: When connecting a Bluetooth keyboard I expect that the keyboard layout is the same as the keyboard hardware key layout (German) or that it is possible to change the keyboard layout in the Bluetooth setting for the connected Bluetooth device. What happened instead: The Bluetooth keyboard worked, but wasn't set to German key layout. In the Bluetooth device setting I couldn't find any option to change the Bluetooth keyboard key layout. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491340/+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 1491340] Re: Bluetooth keyboard is configured with wrong keyboard layout
** Changed in: unity8 (Ubuntu) Status: Triaged => In Progress ** Changed in: canonical-devices-system-image Status: Triaged => In Progress ** Changed in: canonical-pocket-desktop Status: Triaged => In Progress ** Changed in: avila Assignee: (unassigned) => Michał Sawicz (saviq) ** Changed in: avila Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1491340 Title: Bluetooth keyboard is configured with wrong keyboard layout Status in The Avila project: In Progress Status in Canonical System Image: In Progress Status in canonical-pocket-desktop: In Progress Status in bluez package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: Phone: Meizu MX4 (15.04 r4) OS Language: German What you expected to happen: When connecting a Bluetooth keyboard I expect that the keyboard layout is the same as the keyboard hardware key layout (German) or that it is possible to change the keyboard layout in the Bluetooth setting for the connected Bluetooth device. What happened instead: The Bluetooth keyboard worked, but wasn't set to German key layout. In the Bluetooth device setting I couldn't find any option to change the Bluetooth keyboard key layout. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1491340/+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 1519681] Re: Some media keys on BT keyboard do not work as expected
I don't think this is AVRCP actually. These are likely standard media key events delivered to the shell that just passes them down to apps today. ** Changed in: unity8 (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1519681 Title: Some media keys on BT keyboard do not work as expected Status in The Avila project: Confirmed Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: New Status in bluez package in Ubuntu: New Status in qtubuntu-media package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: $ system-image-cli -i current build number: 75 device name: mako channel: ubuntu-touch/rc-proposed/ubuntu-pd last update: 2015-11-24 05:39:02 version version: 75 version ubuntu: 20151124 version device: 20150911 version custom: 20150929-2-vivid Steps to reproduce: 1. Windowed mode is enabled with BT mouse/keyboard connected 2. Launch music app to play all of a playlist 3. Press Pause/Play, Fast forward/Rewind keys on BT keyboard Actual results: Press media keys(Pause/Play, Fast forward/Rewind) on BT keyboard has no control for playback currently only Volume Up/ Down and Mute/Unmute media keys work BT keyboard type: Logitech K480 and Rapoo E6350 To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1519681/+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 1529049] Re: Switch bluetooth keyboard from qwerty to azerty
*** This bug is a duplicate of bug 1491340 *** https://bugs.launchpad.net/bugs/1491340 ** This bug has been marked a duplicate of bug 1491340 Bluetooth keyboard is configured with wrong keyboard layout -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1529049 Title: Switch bluetooth keyboard from qwerty to azerty Status in ubuntu-keyboard: New Status in bluez package in Ubuntu: Invalid Bug description: Trying convergence, I've noticed that : When a bluetooth keyboard is paired, the keyboard is by default in Qwerty (even if it's an Azerty keyboard and the settings of UT are on French Azerty keyboard layout) We should have an option to set the Azerty / Qwerty option in bluetooth settings. Or a better solution could be that the bluetooth keyboard layout is set to the default keyboard layout we have put in Language settings. Does someone know a way to set correctly the layout of the bluetooth keyboard ? (I've tried : 'loadkeys fr' in terminal but this didn't work, I suspect that the default layout was already on fr but the bluetooth keyboard doesn't detect it) Device : mako rc-proposed last revision of 24 dec 2015 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1529049/+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 1491340] Re: Bluetooth keyboard is configured with wrong keyboard layout
Tomas, that's quite likely - can you please file a new bug against unity8 for this? Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1491340 Title: Bluetooth keyboard is configured with wrong keyboard layout Status in The Avila project: In Progress Status in Canonical System Image: Fix Committed Status in Canonical Pocket Desktop: Fix Committed Status in bluez package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: Phone: Meizu MX4 (15.04 r4) OS Language: German What you expected to happen: When connecting a Bluetooth keyboard I expect that the keyboard layout is the same as the keyboard hardware key layout (German) or that it is possible to change the keyboard layout in the Bluetooth setting for the connected Bluetooth device. What happened instead: The Bluetooth keyboard worked, but wasn't set to German key layout. In the Bluetooth device setting I couldn't find any option to change the Bluetooth keyboard key layout. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1491340/+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 1552371] Re: Bluetooth connection turns on the device
** Package changed: unity8 (Ubuntu) => unity-system-compositor (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1552371 Title: Bluetooth connection turns on the device Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: New Bug description: I have been noticing my phone and tablet occasionally turning on without interaction. Several times with my phone in my pocket I found it in the emergency call UI I also see the tablet display turn on while lying idle on the desk. I have reproduced one case such that turning on a BT device (headset) causes the phone to light up and display the volume slider. Similarly turning on the BT keyboard while the tablet screen is off caused the display to turn on.These may be as intended. I suspect other BT events can similarly resume the device and/or turn on the display if it happens to be awake due to the 5 min polling timer. The proximity sensor is also not honored when this happens, if its covered the screen still comes on. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552371/+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 1572577] syslog.txt
apport information ** Attachment added: "syslog.txt" https://bugs.launchpad.net/bugs/1572577/+attachment/4640729/+files/syslog.txt ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1572577 Title: Can't pair with a Volvo car kit Status in bluez package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: For a while now I'm unable to pair with my car kit. It's a reverse- pair procedure, so the car is trying to initiate the pairing, shows the PIN to enter and goes "failed" - with the phone never showing anything. Syslog shows, possibly relevant: Apr 20 15:21:40 ubuntu-phablet bluetoothd[891]: src/device.c:new_auth() Requesting agent authentication for 00:1A:77:F6:D5:2B [...] Apr 20 15:21:40 ubuntu-phablet bluetoothd[891]: Agent /com/canonical/SettingsBluetoothAgent/adapteragent replied with an error: org.bluez.Error.Rejected, The request was rejected: RequestPinCode [...] Apr 20 15:21:40 ubuntu-phablet bluetoothd[891]: src/device.c:device_cancel_authentication() Canceling authentication request for 00:1A:77:F6:D5:2B Please find logs, as directed by https://wiki.ubuntu.com/DebuggingBluetooth, attached. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubuntu-system-settings 0.3+15.04.20160407-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.4.67 armv7l ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Wed Apr 20 15:31:32 2016 InstallationDate: Installed on 2016-04-14 (6 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160414-020305) SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2016-04-14 (6 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160414-020305) Lsusb: Error: [Errno 2] No such file or directory Package: bluez 5.37-0ubuntu5~overlay1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] PackageArchitecture: armhf ProcKernelCmdLine: console=ttyMT0,921600n1 vmalloc=496M slub_max_order=0 fixrtc lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=511 bootprof.lk_t=1724 printk.disable_uart=1 boot_reason=4 datapart=/dev/mmcblk0p7 systempart=/dev/mmcblk0p6 androidboot.serialno=JB011540 � lcm=1-hx8389_qhd_dsi_vdo_truly fps=6657 bootprof.pl_t=511 bootprof.lk_t=1724 printk.disable_uart=1 boot_reason=4 datapart=/dev/mmcblk0p7 systempart=/dev/mmcblk0p6 androidboot.serialno=JB011540 � ProcModules: Tags: vivid third-party-packages UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.4.67 armv7l UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video _MarkForUpload: True hciconfig: hci0:Type: BR/EDR Bus: UART BD Address: B8:64:91:48:2B:21 ACL MTU: 1021:4 SCO MTU: 184:1 UP RUNNING PSCAN RX bytes:4361 acl:59 sco:0 events:213 errors:0 TX bytes:6120 acl:60 sco:0 commands:131 errors:0 modified.conffile..etc.init.bluetooth.conf: [modified] mtime.conffile..etc.init.bluetooth.conf: 2016-04-20T15:11:43.487387 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1572577/+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 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
FWIW I still can't pair with my hands-free system. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Committed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+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 1630906] Re: QML segfault on arm64 due to builder kernel change
** Changed in: ubuntu-push-qml (Ubuntu) Status: New => 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/1630906 Title: QML segfault on arm64 due to builder kernel change Status in linux package in Ubuntu: Invalid Status in online-accounts-api package in Ubuntu: Invalid Status in qmenumodel package in Ubuntu: Invalid Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in ubuntu-push-qml package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Status in webbrowser-app package in Ubuntu: Invalid Status in qtdeclarative-opensource-src package in Ubuntu RTM: Fix Released Bug description: Builders were changed from wily to xenial (4.4) kernel for arm64, and likely due to this the following kind of errors started happening: https://launchpadlibrarian.net/288487533/buildlog_ubuntu-yakkety-arm64 .ubuntu-push-qml_0.1+15.10.20150826.1-0ubuntu2_BUILDING.txt.gz They happen when executing QML code. I've ruled out that reverting to previous qtbase and qtdeclarative versions don't affect this, so it's not coming from a Qt change. I've also verified there's no problem eg on our Bq tablet running the same tests on xenial+overlay. There are currently no found changes at least in Qt upstream to backport arm64 related fixes. Cause is unknown. But the same problem is there on vivid, xenial and yakkety builds: https://launchpadlibrarian.net/288516465/buildlog_ubuntu-yakkety-arm64.online-accounts-api_0.1+16.10.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515705/buildlog_ubuntu-xenial-arm64.online-accounts-api_0.1+16.04.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515510/buildlog_ubuntu-vivid-arm64.online-accounts-api_0.1+15.04.20161006.1-0ubuntu1_BUILDING.txt.gz This means it does not matter if it's Qt 5.4 or 5.6, GCC 4.9, 5 or 6, or glibc 2.21, 2.23 or 2.24. More logs from affected packages: https://launchpadlibrarian.net/288493058/buildlog_ubuntu-yakkety-arm64.qtdeclarative-opensource-src_5.6.1-7ubuntu3~1_BUILDING.txt.gz https://launchpadlibrarian.net/288347391/buildlog_ubuntu-xenial-arm64.webbrowser-app_0.23+16.04.20161005.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288385063/buildlog_ubuntu-vivid-arm64.qmenumodel_0.2.10+15.04.20161005.1-0ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630906/+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 1630906] Re: QML segfault on arm64 due to builder kernel change
** Changed in: qtdeclarative-opensource-src (Ubuntu RTM) Status: In Progress => Fix Released ** Changed in: unity8 (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: online-accounts-api (Ubuntu) Status: New => Invalid ** Changed in: qmenumodel (Ubuntu) Status: New => Invalid ** Changed in: webbrowser-app (Ubuntu) Status: New => 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/1630906 Title: QML segfault on arm64 due to builder kernel change Status in linux package in Ubuntu: Invalid Status in online-accounts-api package in Ubuntu: Invalid Status in qmenumodel package in Ubuntu: Invalid Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in ubuntu-push-qml package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Status in webbrowser-app package in Ubuntu: Invalid Status in qtdeclarative-opensource-src package in Ubuntu RTM: Fix Released Bug description: Builders were changed from wily to xenial (4.4) kernel for arm64, and likely due to this the following kind of errors started happening: https://launchpadlibrarian.net/288487533/buildlog_ubuntu-yakkety-arm64 .ubuntu-push-qml_0.1+15.10.20150826.1-0ubuntu2_BUILDING.txt.gz They happen when executing QML code. I've ruled out that reverting to previous qtbase and qtdeclarative versions don't affect this, so it's not coming from a Qt change. I've also verified there's no problem eg on our Bq tablet running the same tests on xenial+overlay. There are currently no found changes at least in Qt upstream to backport arm64 related fixes. Cause is unknown. But the same problem is there on vivid, xenial and yakkety builds: https://launchpadlibrarian.net/288516465/buildlog_ubuntu-yakkety-arm64.online-accounts-api_0.1+16.10.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515705/buildlog_ubuntu-xenial-arm64.online-accounts-api_0.1+16.04.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515510/buildlog_ubuntu-vivid-arm64.online-accounts-api_0.1+15.04.20161006.1-0ubuntu1_BUILDING.txt.gz This means it does not matter if it's Qt 5.4 or 5.6, GCC 4.9, 5 or 6, or glibc 2.21, 2.23 or 2.24. More logs from affected packages: https://launchpadlibrarian.net/288493058/buildlog_ubuntu-yakkety-arm64.qtdeclarative-opensource-src_5.6.1-7ubuntu3~1_BUILDING.txt.gz https://launchpadlibrarian.net/288347391/buildlog_ubuntu-xenial-arm64.webbrowser-app_0.23+16.04.20161005.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288385063/buildlog_ubuntu-vivid-arm64.qmenumodel_0.2.10+15.04.20161005.1-0ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630906/+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 1673197] [NEW] Upgrading zfs-initramfs breaks booting from a zfs root
Public bug reported: Upgrading to zfs-initramfs 0.6.5.9-4ubuntu1 breaks my boot. I've EFI and a small ext2 boot partition, and the rest of my SDD is a zfs pool. After upgrade I'm dropped in the initramfs shell and no zpools are available. Downgrading to 0.6.5.8-0ubuntu9 makes it boot again. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: zfs-initramfs 0.6.5.9-4ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Mar 15 18:29:04 2017 InstallationDate: Installed on 2016-05-06 (312 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to zesty on 2016-11-22 (113 days ago) ** Affects: zfs-linux (Ubuntu) Importance: Critical Status: New ** Tags: amd64 apport-bug zesty ** Description changed: Upgrading to zfs-initramfs 0.6.5.9-4ubuntu1 breaks my boot. I've EFI and a small ext2 boot partition, and the rest of my SDD is a zfs pool. After upgrade I'm dropped in the initramfs shell and no zpools are available. + + Downgrading to 0.6.5.8-0ubuntu9 makes it boot again. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: zfs-initramfs 0.6.5.9-4ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Mar 15 18:29:04 2017 InstallationDate: Installed on 2016-05-06 (312 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to zesty on 2016-11-22 (113 days ago) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1673197 Title: Upgrading zfs-initramfs breaks booting from a zfs root Status in zfs-linux package in Ubuntu: New Bug description: Upgrading to zfs-initramfs 0.6.5.9-4ubuntu1 breaks my boot. I've EFI and a small ext2 boot partition, and the rest of my SDD is a zfs pool. After upgrade I'm dropped in the initramfs shell and no zpools are available. Downgrading to 0.6.5.8-0ubuntu9 makes it boot again. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: zfs-initramfs 0.6.5.9-4ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Mar 15 18:29:04 2017 InstallationDate: Installed on 2016-05-06 (312 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to zesty on 2016-11-22 (113 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1673197/+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 1777062] [NEW] Mouse only pairs successfully after 4-5 tries
Public bug reported: I've had my mouse (Logitech M535) paired and working since upgrading to 18.04. I had to re-do the pairing after connecting to a different machine and now it takes 4-5 tries of pair/remove to connect the mouse, on every reboot / sleep cycle. The logs show: cze 15 07:45:37 michal-laptop bluetoothd[4168]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 07:46:14 michal-laptop bluetoothd[4168]: Can't get HIDP connection info But neither actually seem critical as this is shown upon successful pairing as well. a bluetoothctl session of a failed pairing: [bluetooth]# pair 34:88:5D:3E:A1:A4 Attempting to pair with 34:88:5D:3E:A1:A4 [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes Pairing successful [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: no [CHG] Device 34:88:5D:3E:A1:A4 Connected: no The mouse continues in pairing mode. When using the gnome-control-center Bluetooth module: cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:43 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) Finally when it connects: [NEW] Device 34:88:5D:3E:A1:A4 Bluetooth Mouse M336/M337/M535 [CHG] Device 34:88:5D:3E:A1:A4 Trusted: yes [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 15 07:46:38 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 12-9Q33 ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic root=ZFS=username-laptop/ROOT/ubuntu ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-02-07 (127 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 5C:51:4F:1D:50:3C ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN ISCAN RX bytes:16702 acl:290 sco:0 events:716 errors:0 TX bytes:44162 acl:142 sco:0 commands:427 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1777062 Title: Mouse only pairs successfully after 4-5 tries Status in bluez package in Ubuntu: New Bug description: I've had my mouse (Logitech M535) paired and working since upgrading to 18.04. I had to re-do the pairing after connecting to a different machine and now it takes 4-5 tries of pair/remove to connect the mouse, on every reboot / sleep cycle. The logs show: cze 15 07:45:37 michal-laptop bluetoothd[4168]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 07:46:14 michal-laptop bluetoothd[4168]: Can't get HIDP connection info
[Kernel-packages] [Bug 1777062] Re: Logitech M535 mouse only pairs successfully after 4-5 tries
*** This bug is a duplicate of bug 1773897 *** https://bugs.launchpad.net/bugs/1773897 It does look similar to that other bug, will dupe and we'll see if it improves when that's fixed. ** This bug has been marked a duplicate of bug 1773897 [regression] Logitech M337 mice are automatically disconnected after connected -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1777062 Title: Logitech M535 mouse only pairs successfully after 4-5 tries Status in bluez package in Ubuntu: New Bug description: I've had my mouse (Logitech M535) paired and working since upgrading to 18.04. I had to re-do the pairing after connecting to a different machine and now it takes 4-5 tries of pair/remove to connect the mouse, on every reboot / sleep cycle. The logs show: cze 15 07:45:37 michal-laptop bluetoothd[4168]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 07:46:14 michal-laptop bluetoothd[4168]: Can't get HIDP connection info But neither actually seem critical as this is shown upon successful pairing as well. a bluetoothctl session of a failed pairing: [bluetooth]# pair 34:88:5D:3E:A1:A4 Attempting to pair with 34:88:5D:3E:A1:A4 [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes Pairing successful [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: no [CHG] Device 34:88:5D:3E:A1:A4 Connected: no The mouse continues in pairing mode. When using the gnome-control-center Bluetooth module: cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:43 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) Finally when it connects: [NEW] Device 34:88:5D:3E:A1:A4 Bluetooth Mouse M336/M337/M535 [CHG] Device 34:88:5D:3E:A1:A4 Trusted: yes [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 15 07:46:38 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 12-9Q33 ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic root=ZFS=username-laptop/ROOT/ubuntu ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-02-07 (127 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 5C:51:4F:1D:50:3C ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN ISCAN RX bytes:16702 acl:290 sco:0 events:716 errors:0 TX bytes:44162 acl:142 sco:0 commands:427 errors:0 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1777062] Re: Logitech M535 mouse only pairs successfully after 4-5 tries
*** This bug is a duplicate of bug 1773897 *** https://bugs.launchpad.net/bugs/1773897 Most recently from 17.10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1777062 Title: Logitech M535 mouse only pairs successfully after 4-5 tries Status in bluez package in Ubuntu: New Bug description: I've had my mouse (Logitech M535) paired and working since upgrading to 18.04. I had to re-do the pairing after connecting to a different machine and now it takes 4-5 tries of pair/remove to connect the mouse, on every reboot / sleep cycle. The logs show: cze 15 07:45:37 michal-laptop bluetoothd[4168]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 07:46:14 michal-laptop bluetoothd[4168]: Can't get HIDP connection info But neither actually seem critical as this is shown upon successful pairing as well. a bluetoothctl session of a failed pairing: [bluetooth]# pair 34:88:5D:3E:A1:A4 Attempting to pair with 34:88:5D:3E:A1:A4 [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes Pairing successful [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: no [CHG] Device 34:88:5D:3E:A1:A4 Connected: no The mouse continues in pairing mode. When using the gnome-control-center Bluetooth module: cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:43 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) Finally when it connects: [NEW] Device 34:88:5D:3E:A1:A4 Bluetooth Mouse M336/M337/M535 [CHG] Device 34:88:5D:3E:A1:A4 Trusted: yes [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 15 07:46:38 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 12-9Q33 ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic root=ZFS=username-laptop/ROOT/ubuntu ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-02-07 (127 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 5C:51:4F:1D:50:3C ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN ISCAN RX bytes:16702 acl:290 sco:0 events:716 errors:0 TX bytes:44162 acl:142 sco:0 commands:427 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1777062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1718654] Re: Touchpad input doesn't work after longer suspend.
Confirmed, I haven't seen this issue in a while. -- 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/1718654 Title: Touchpad input doesn't work after longer suspend. Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: When I resume my laptop from a longer (not sure what the threshold is yet) suspend, I don't get input from the touchpad, a short suspend cycle fixes it. Touchscreen works all the time. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 21 14:20:56 2017 DisplayManager: gdm3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718654/+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 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected
Not sure what's changed, but I've recently had much better luck with the mouse connecting properly by itself. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Confirmed Status in OEM Priority Project: New Status in bluez package in Ubuntu: Confirmed Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic 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 dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+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 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected
lsusb says "Bus 002 Device 003: ID 8087:07dc Intel Corp." here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Confirmed Status in OEM Priority Project: New Status in bluez package in Ubuntu: Confirmed Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic 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 dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+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 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected
I'm back to having to re-pair a handful of times each boot. It seems every once in a while the pairing "sticks" and works until I have to reconnect it again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Confirmed Status in OEM Priority Project: New Status in bluez package in Ubuntu: Confirmed Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic 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 dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+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 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected
@Feng could you please rebuild for cosmic, too? I'll try it out then. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Confirmed Status in OEM Priority Project: New Status in bluez package in Ubuntu: Confirmed Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic 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 dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+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 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected
Ah indeed... $ LANG=C apt policy bluez bluez: Installed: 5.50-0ubuntu1 Candidate: 5.50-0ubuntu1 Version table: *** 5.50-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status In that case I don't think I can confirm this fixes it, or maybe mine is a different issue (M535 mouse here). I've certainly had trouble pairing since I've upgraded to cosmic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Confirmed Status in OEM Priority Project: New Status in bluez package in Ubuntu: Confirmed Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic 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 dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+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 1777062] Re: Logitech M535 mouse only pairs successfully after 4-5 tries
Yes, I just removed the mouse under gnome-control-center, went into `bluetoothctl` and tried to pair it again: [bluetooth]# scan on Discovery started [NEW] Device 49:4E:A7:0B:A0:51 49-4E-A7-0B-A0-51 [NEW] Device 34:88:5D:3E:A1:A4 Bluetooth Mouse M336/M337/M535 [bluetooth]# pair 34:88:5D:3E:A1:A4 Attempting to pair with 34:88:5D:3E:A1:A4 [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes Pairing successful [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: no [CHG] Device 34:88:5D:3E:A1:A4 Connected: no [bluetooth]# pair 34:88:5D:3E:A1:A4 Attempting to pair with 34:88:5D:3E:A1:A4 Failed to pair: org.bluez.Error.AlreadyExists [bluetooth]# connect 34:88:5D:3E:A1:A4 Attempting to connect to 34:88:5D:3E:A1:A4 Failed to connect: org.bluez.Error.Failed [bluetooth]# version Version 5.50 [bluetooth]# quit $ uname -a Linux michal-laptop 4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux bluetoothctl claims it pairs it, but then disconnects again. The mouse continues to blink, remaining in pairing mode. Even when it does pair successfully, only every 10 times or so does the pairing "persist" across suspend/reboot cycles. Most often I have to re- pair from scratch every boot/resume. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1777062 Title: Logitech M535 mouse only pairs successfully after 4-5 tries Status in bluez package in Ubuntu: Incomplete Bug description: I've had my mouse (Logitech M535) paired and working since upgrading to 18.04. I had to re-do the pairing after connecting to a different machine and now it takes 4-5 tries of pair/remove to connect the mouse, on every reboot / sleep cycle. The logs show: cze 15 07:45:37 michal-laptop bluetoothd[4168]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 07:46:14 michal-laptop bluetoothd[4168]: Can't get HIDP connection info But neither actually seem critical as this is shown upon successful pairing as well. a bluetoothctl session of a failed pairing: [bluetooth]# pair 34:88:5D:3E:A1:A4 Attempting to pair with 34:88:5D:3E:A1:A4 [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes Pairing successful [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: no [CHG] Device 34:88:5D:3E:A1:A4 Connected: no The mouse continues in pairing mode. When using the gnome-control-center Bluetooth module: cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:43 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) Finally when it connects: [NEW] Device 34:88:5D:3E:A1:A4 Bluetooth Mouse M336/M337/M535 [CHG] Device 34:88:5D:3E:A1:A4 Trusted: yes [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion:
[Kernel-packages] [Bug 1777062] Re: Logitech M535 mouse only pairs successfully after 4-5 tries
When it does pair, bluetoothctl doesn't report "ServicesResolved: no" or "Connected: no". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1777062 Title: Logitech M535 mouse only pairs successfully after 4-5 tries Status in bluez package in Ubuntu: Incomplete Bug description: I've had my mouse (Logitech M535) paired and working since upgrading to 18.04. I had to re-do the pairing after connecting to a different machine and now it takes 4-5 tries of pair/remove to connect the mouse, on every reboot / sleep cycle. The logs show: cze 15 07:45:37 michal-laptop bluetoothd[4168]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 07:46:14 michal-laptop bluetoothd[4168]: Can't get HIDP connection info But neither actually seem critical as this is shown upon successful pairing as well. a bluetoothctl session of a failed pairing: [bluetooth]# pair 34:88:5D:3E:A1:A4 Attempting to pair with 34:88:5D:3E:A1:A4 [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes Pairing successful [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: no [CHG] Device 34:88:5D:3E:A1:A4 Connected: no The mouse continues in pairing mode. When using the gnome-control-center Bluetooth module: cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:43 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) Finally when it connects: [NEW] Device 34:88:5D:3E:A1:A4 Bluetooth Mouse M336/M337/M535 [CHG] Device 34:88:5D:3E:A1:A4 Trusted: yes [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 15 07:46:38 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 12-9Q33 ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic root=ZFS=username-laptop/ROOT/ubuntu ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-02-07 (127 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 5C:51:4F:1D:50:3C ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN ISCAN RX bytes:16702 acl:290 sco:0 events:716 errors:0 TX bytes:44162 acl:142 sco:0 commands:427 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1777062/+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 1777062] Re: Logitech M535 mouse only pairs successfully after 4-5 tries
Hey @vanvugt, just upgraded to 19.04 and indeed the problems seem to have gone. The mouse pairs every time, and persistently. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1777062 Title: Logitech M535 mouse only pairs successfully after 4-5 tries Status in bluez package in Ubuntu: Incomplete Bug description: I've had my mouse (Logitech M535) paired and working since upgrading to 18.04. I had to re-do the pairing after connecting to a different machine and now it takes 4-5 tries of pair/remove to connect the mouse, on every reboot / sleep cycle. The logs show: cze 15 07:45:37 michal-laptop bluetoothd[4168]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 07:46:14 michal-laptop bluetoothd[4168]: Can't get HIDP connection info But neither actually seem critical as this is shown upon successful pairing as well. a bluetoothctl session of a failed pairing: [bluetooth]# pair 34:88:5D:3E:A1:A4 Attempting to pair with 34:88:5D:3E:A1:A4 [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes Pairing successful [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: no [CHG] Device 34:88:5D:3E:A1:A4 Connected: no The mouse continues in pairing mode. When using the gnome-control-center Bluetooth module: cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) cze 15 08:23:43 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error updating services: Device or resource busy (16) Finally when it connects: [NEW] Device 34:88:5D:3E:A1:A4 Bluetooth Mouse M336/M337/M535 [CHG] Device 34:88:5D:3E:A1:A4 Trusted: yes [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200 [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 15 07:46:38 2018 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 12-9Q33 ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic root=ZFS=username-laptop/ROOT/ubuntu ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-02-07 (127 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 5C:51:4F:1D:50:3C ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN ISCAN RX bytes:16702 acl:290 sco:0 events:716 errors:0 TX bytes:44162 acl:142 sco:0 commands:427 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1777062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1840484] Re: linux-oem 4.15 can not suspend to idle XPS-13-9380
Hey, Can you confirm whether this was when you had Multipass instances running (multipass list), or just when Multipass is installed? Multipass just manages qemu/kvm VM - the same bug is likely to be caused by libvirt or a manually started qemu VM. In essence, this would be a bug in KVM (especially if a different kernel makes the issue go away), not in Multipass? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem in Ubuntu. https://bugs.launchpad.net/bugs/1840484 Title: linux-oem 4.15 can not suspend to idle XPS-13-9380 Status in OEM Priority Project: New Status in linux-signed-oem package in Ubuntu: New Bug description: it somehow s2i failed, from message , it seems the s2i process be blocked by thunderbolt device. dmesg: [193139.391652] pciehp :04:04.0:pcie204: pcie_do_write_cmd: no response from device [193139.391703] pciehp :04:01.0:pcie204: pcie_do_write_cmd: no response from device [193141.012736] PM: noirq suspend of devices failed [193141.772467] ath10k_pci :02:00.0: Unknown eventid: 118809 [193141.775359] ath10k_pci :02:00.0: Unknown eventid: 90118 [193141.872317] thunderbolt :05:00.0: control channel starting... Not sure is it relative that I hot plug out WD19 docking before suspend. reproduce rate: random ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1045-oem 4.15.0-1045.50 ProcVersionSignature: Ubuntu 4.15.0-1045.50-oem 4.15.18 Uname: Linux 4.15.0-1045-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 17 00:02:08 2019 InstallationDate: Installed on 2019-08-11 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1840484/+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 1840484] Re: linux-oem 4.15 can not suspend to idle XPS-13-9380
If it doesn't require an instance to break S2I, that suggests something in our daemon after all. I wouldn't think we'd be doing anything low-level enough to cause this, though… -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem in Ubuntu. https://bugs.launchpad.net/bugs/1840484 Title: linux-oem 4.15 can not suspend to idle XPS-13-9380 Status in OEM Priority Project: New Status in linux-signed-oem package in Ubuntu: New Bug description: it somehow s2i failed, from message , it seems the s2i process be blocked by thunderbolt device. dmesg: [193139.391652] pciehp :04:04.0:pcie204: pcie_do_write_cmd: no response from device [193139.391703] pciehp :04:01.0:pcie204: pcie_do_write_cmd: no response from device [193141.012736] PM: noirq suspend of devices failed [193141.772467] ath10k_pci :02:00.0: Unknown eventid: 118809 [193141.775359] ath10k_pci :02:00.0: Unknown eventid: 90118 [193141.872317] thunderbolt :05:00.0: control channel starting... Not sure is it relative that I hot plug out WD19 docking before suspend. reproduce rate: random ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1045-oem 4.15.0-1045.50 ProcVersionSignature: Ubuntu 4.15.0-1045.50-oem 4.15.18 Uname: Linux 4.15.0-1045-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 17 00:02:08 2019 InstallationDate: Installed on 2019-08-11 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1840484/+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 1860512] Re: Suspend unreliable (possibly FUSE related)
This was https://rclone.org/ - but I've not had this issue in a while. Will close for now. ** 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/1860512 Title: Suspend unreliable (possibly FUSE related) Status in linux package in Ubuntu: Incomplete Bug description: Since updating to Focal my laptop stopped suspending reliably. It will sit there either without display or with the desktop stuck for almost a minute before it goes back to work again. Looking at the kernel logs this seems to be related to a FUSE mount that I have running: sty 22 09:00:49 michal-laptop kernel: Call Trace: sty 22 09:00:49 michal-laptop kernel: __schedule+0x2e3/0x740 sty 22 09:00:49 michal-laptop kernel: schedule+0x42/0xb0 sty 22 09:00:49 michal-laptop kernel: request_wait_answer+0xa0/0x200 sty 22 09:00:49 michal-laptop kernel: ? wait_woken+0x80/0x80 sty 22 09:00:49 michal-laptop kernel: fuse_simple_request+0x177/0x260 sty 22 09:00:49 michal-laptop kernel: fuse_send_readpages.isra.0+0xea/0xf0 sty 22 09:00:49 michal-laptop kernel: fuse_readpages+0xbc/0x110 sty 22 09:00:49 michal-laptop kernel: read_pages+0x71/0x1a0 sty 22 09:00:49 michal-laptop kernel: __do_page_cache_readahead+0x180/0x1a0 sty 22 09:00:49 michal-laptop kernel: ondemand_readahead+0x192/0x2d0 sty 22 09:00:49 michal-laptop kernel: page_cache_sync_readahead+0x78/0xc0 sty 22 09:00:49 michal-laptop kernel: generic_file_buffered_read+0x571/0xc00 sty 22 09:00:49 michal-laptop kernel: ? ima_file_check+0x5a/0x80 sty 22 09:00:49 michal-laptop kernel: ? do_last+0x194/0x940 sty 22 09:00:49 michal-laptop kernel: generic_file_read_iter+0xdc/0x140 sty 22 09:00:49 michal-laptop kernel: fuse_file_read_iter+0x101/0x130 sty 22 09:00:49 michal-laptop kernel: ? do_filp_open+0xa5/0x100 sty 22 09:00:49 michal-laptop kernel: new_sync_read+0x122/0x1b0 sty 22 09:00:49 michal-laptop kernel: __vfs_read+0x29/0x40 sty 22 09:00:49 michal-laptop kernel: vfs_read+0xab/0x160 sty 22 09:00:49 michal-laptop kernel: ksys_read+0x67/0xe0 sty 22 09:00:49 michal-laptop kernel: __x64_sys_read+0x1a/0x20 sty 22 09:00:49 michal-laptop kernel: do_syscall_64+0x57/0x190 sty 22 09:00:49 michal-laptop kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 sty 22 09:00:49 michal-laptop kernel: RIP: 0033:0x7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: Code: Bad RIP value. sty 22 09:00:49 michal-laptop kernel: RSP: 002b:7f430bffda28 EFLAGS: 0246 ORIG_RAX: sty 22 09:00:49 michal-laptop kernel: RAX: ffda RBX: 492a RCX: 7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: RDX: 1000 RSI: 7f430bffda40 RDI: 0011 sty 22 09:00:49 michal-laptop kernel: RBP: 7f430bffda40 R08: R09: 7f430bffd9a8 sty 22 09:00:49 michal-laptop kernel: R10: R11: 0246 R12: 7f434670 sty 22 09:00:49 michal-laptop kernel: R13: 562dc32aaac0 R14: 0011 R15: 562dc32aaac0 A longer kernel log is attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 6829 F pulseaudio /dev/snd/controlC0: michal 6829 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 08:54:14 2020 InstallationDate: Installed on 2019-11-19 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i2bkio@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_i2bkio ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-20 (1 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.sku: XPS 12-9Q33
[Kernel-packages] [Bug 1860512] Re: Suspend unreliable (possibly FUSE related)
tracker-extract on Ubuntu is probably what is keeping it busy here, as I get it crashing from time to time when I mess about with the mountpoint (like unmount to get it to suspend). -- 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/1860512 Title: Suspend unreliable (possibly FUSE related) Status in linux package in Ubuntu: Confirmed Bug description: Since updating to Focal my laptop stopped suspending reliably. It will sit there either without display or with the desktop stuck for almost a minute before it goes back to work again. Looking at the kernel logs this seems to be related to a FUSE mount that I have running: sty 22 09:00:49 michal-laptop kernel: Call Trace: sty 22 09:00:49 michal-laptop kernel: __schedule+0x2e3/0x740 sty 22 09:00:49 michal-laptop kernel: schedule+0x42/0xb0 sty 22 09:00:49 michal-laptop kernel: request_wait_answer+0xa0/0x200 sty 22 09:00:49 michal-laptop kernel: ? wait_woken+0x80/0x80 sty 22 09:00:49 michal-laptop kernel: fuse_simple_request+0x177/0x260 sty 22 09:00:49 michal-laptop kernel: fuse_send_readpages.isra.0+0xea/0xf0 sty 22 09:00:49 michal-laptop kernel: fuse_readpages+0xbc/0x110 sty 22 09:00:49 michal-laptop kernel: read_pages+0x71/0x1a0 sty 22 09:00:49 michal-laptop kernel: __do_page_cache_readahead+0x180/0x1a0 sty 22 09:00:49 michal-laptop kernel: ondemand_readahead+0x192/0x2d0 sty 22 09:00:49 michal-laptop kernel: page_cache_sync_readahead+0x78/0xc0 sty 22 09:00:49 michal-laptop kernel: generic_file_buffered_read+0x571/0xc00 sty 22 09:00:49 michal-laptop kernel: ? ima_file_check+0x5a/0x80 sty 22 09:00:49 michal-laptop kernel: ? do_last+0x194/0x940 sty 22 09:00:49 michal-laptop kernel: generic_file_read_iter+0xdc/0x140 sty 22 09:00:49 michal-laptop kernel: fuse_file_read_iter+0x101/0x130 sty 22 09:00:49 michal-laptop kernel: ? do_filp_open+0xa5/0x100 sty 22 09:00:49 michal-laptop kernel: new_sync_read+0x122/0x1b0 sty 22 09:00:49 michal-laptop kernel: __vfs_read+0x29/0x40 sty 22 09:00:49 michal-laptop kernel: vfs_read+0xab/0x160 sty 22 09:00:49 michal-laptop kernel: ksys_read+0x67/0xe0 sty 22 09:00:49 michal-laptop kernel: __x64_sys_read+0x1a/0x20 sty 22 09:00:49 michal-laptop kernel: do_syscall_64+0x57/0x190 sty 22 09:00:49 michal-laptop kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 sty 22 09:00:49 michal-laptop kernel: RIP: 0033:0x7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: Code: Bad RIP value. sty 22 09:00:49 michal-laptop kernel: RSP: 002b:7f430bffda28 EFLAGS: 0246 ORIG_RAX: sty 22 09:00:49 michal-laptop kernel: RAX: ffda RBX: 492a RCX: 7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: RDX: 1000 RSI: 7f430bffda40 RDI: 0011 sty 22 09:00:49 michal-laptop kernel: RBP: 7f430bffda40 R08: R09: 7f430bffd9a8 sty 22 09:00:49 michal-laptop kernel: R10: R11: 0246 R12: 7f434670 sty 22 09:00:49 michal-laptop kernel: R13: 562dc32aaac0 R14: 0011 R15: 562dc32aaac0 A longer kernel log is attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 6829 F pulseaudio /dev/snd/controlC0: michal 6829 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 08:54:14 2020 InstallationDate: Installed on 2019-11-19 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i2bkio@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_i2bkio ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-20 (1 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.sku: XPS
[Kernel-packages] [Bug 1389592] Re: [Dell Inc. XPS 12-9Q33] suspend/resume failure
** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1389592 Title: [Dell Inc. XPS 12-9Q33] suspend/resume failure Status in linux package in Ubuntu: Fix Released Bug description: Related to bug #1389589 I think, my laptop started hanging on suspend from time to time. ProblemType: KernelOops DistroRelease: Ubuntu 15.04 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 3023 F pulseaudio /dev/snd/controlC0: michal 3023 F pulseaudio Date: Wed Nov 5 10:25:33 2014 DuplicateSignature: suspend/resume:Dell Inc. XPS 12-9Q33:A06 ExecutablePath: /usr/share/apport/apportcheckresume ExecutableTimestamp: 1415063431 Failure: suspend/resume HibernationDevice: RESUME=/dev/mapper/sda3_crypt InterpreterPath: /usr/bin/python3.4 MachineType: Dell Inc. XPS 12-9Q33 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcCwd: / ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=f6fef09e-9f1a-40ad-aeaa-7d7a67fb86f2 ro rootflags=subvol=@ splash quiet vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 SourcePackage: linux Title: [Dell Inc. XPS 12-9Q33] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/15/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/15/2014:svnDellInc.:pnXPS12-9Q33:pvrA06:rvnDellInc.:rnXPS12-9Q33:rvrA06:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1389592/+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 1863411] [NEW] Suspend broken, tasks refuzing to freeze
Public bug reported: My laptop stopped suspending recently. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 15 10:55:21 2020 InstallationDate: Installed on 2020-02-10 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/usr/bin/zsh SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-5.4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug champagne focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1863411 Title: Suspend broken, tasks refuzing to freeze Status in linux-signed-5.4 package in Ubuntu: New Bug description: My laptop stopped suspending recently. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 15 10:55:21 2020 InstallationDate: Installed on 2020-02-10 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/usr/bin/zsh SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-5.4/+bug/1863411/+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 1860512] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1860512/+attachment/5328390/+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/1860512 Title: Suspend unreliable (possibly FUSE related) Status in linux package in Ubuntu: Confirmed Bug description: Since updating to Focal my laptop stopped suspending reliably. It will sit there either without display or with the desktop stuck for almost a minute before it goes back to work again. Looking at the kernel logs this seems to be related to a FUSE mount that I have running: sty 22 09:00:49 michal-laptop kernel: Call Trace: sty 22 09:00:49 michal-laptop kernel: __schedule+0x2e3/0x740 sty 22 09:00:49 michal-laptop kernel: schedule+0x42/0xb0 sty 22 09:00:49 michal-laptop kernel: request_wait_answer+0xa0/0x200 sty 22 09:00:49 michal-laptop kernel: ? wait_woken+0x80/0x80 sty 22 09:00:49 michal-laptop kernel: fuse_simple_request+0x177/0x260 sty 22 09:00:49 michal-laptop kernel: fuse_send_readpages.isra.0+0xea/0xf0 sty 22 09:00:49 michal-laptop kernel: fuse_readpages+0xbc/0x110 sty 22 09:00:49 michal-laptop kernel: read_pages+0x71/0x1a0 sty 22 09:00:49 michal-laptop kernel: __do_page_cache_readahead+0x180/0x1a0 sty 22 09:00:49 michal-laptop kernel: ondemand_readahead+0x192/0x2d0 sty 22 09:00:49 michal-laptop kernel: page_cache_sync_readahead+0x78/0xc0 sty 22 09:00:49 michal-laptop kernel: generic_file_buffered_read+0x571/0xc00 sty 22 09:00:49 michal-laptop kernel: ? ima_file_check+0x5a/0x80 sty 22 09:00:49 michal-laptop kernel: ? do_last+0x194/0x940 sty 22 09:00:49 michal-laptop kernel: generic_file_read_iter+0xdc/0x140 sty 22 09:00:49 michal-laptop kernel: fuse_file_read_iter+0x101/0x130 sty 22 09:00:49 michal-laptop kernel: ? do_filp_open+0xa5/0x100 sty 22 09:00:49 michal-laptop kernel: new_sync_read+0x122/0x1b0 sty 22 09:00:49 michal-laptop kernel: __vfs_read+0x29/0x40 sty 22 09:00:49 michal-laptop kernel: vfs_read+0xab/0x160 sty 22 09:00:49 michal-laptop kernel: ksys_read+0x67/0xe0 sty 22 09:00:49 michal-laptop kernel: __x64_sys_read+0x1a/0x20 sty 22 09:00:49 michal-laptop kernel: do_syscall_64+0x57/0x190 sty 22 09:00:49 michal-laptop kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 sty 22 09:00:49 michal-laptop kernel: RIP: 0033:0x7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: Code: Bad RIP value. sty 22 09:00:49 michal-laptop kernel: RSP: 002b:7f430bffda28 EFLAGS: 0246 ORIG_RAX: sty 22 09:00:49 michal-laptop kernel: RAX: ffda RBX: 492a RCX: 7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: RDX: 1000 RSI: 7f430bffda40 RDI: 0011 sty 22 09:00:49 michal-laptop kernel: RBP: 7f430bffda40 R08: R09: 7f430bffd9a8 sty 22 09:00:49 michal-laptop kernel: R10: R11: 0246 R12: 7f434670 sty 22 09:00:49 michal-laptop kernel: R13: 562dc32aaac0 R14: 0011 R15: 562dc32aaac0 A longer kernel log is attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 6829 F pulseaudio /dev/snd/controlC0: michal 6829 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 08:54:14 2020 InstallationDate: Installed on 2019-11-19 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i2bkio@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_i2bkio ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-20 (1 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.sku: XPS 12-9Q33 dmi.product.version: A08
[Kernel-packages] [Bug 1860512] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1860512/+attachment/5328396/+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/1860512 Title: Suspend unreliable (possibly FUSE related) Status in linux package in Ubuntu: Confirmed Bug description: Since updating to Focal my laptop stopped suspending reliably. It will sit there either without display or with the desktop stuck for almost a minute before it goes back to work again. Looking at the kernel logs this seems to be related to a FUSE mount that I have running: sty 22 09:00:49 michal-laptop kernel: Call Trace: sty 22 09:00:49 michal-laptop kernel: __schedule+0x2e3/0x740 sty 22 09:00:49 michal-laptop kernel: schedule+0x42/0xb0 sty 22 09:00:49 michal-laptop kernel: request_wait_answer+0xa0/0x200 sty 22 09:00:49 michal-laptop kernel: ? wait_woken+0x80/0x80 sty 22 09:00:49 michal-laptop kernel: fuse_simple_request+0x177/0x260 sty 22 09:00:49 michal-laptop kernel: fuse_send_readpages.isra.0+0xea/0xf0 sty 22 09:00:49 michal-laptop kernel: fuse_readpages+0xbc/0x110 sty 22 09:00:49 michal-laptop kernel: read_pages+0x71/0x1a0 sty 22 09:00:49 michal-laptop kernel: __do_page_cache_readahead+0x180/0x1a0 sty 22 09:00:49 michal-laptop kernel: ondemand_readahead+0x192/0x2d0 sty 22 09:00:49 michal-laptop kernel: page_cache_sync_readahead+0x78/0xc0 sty 22 09:00:49 michal-laptop kernel: generic_file_buffered_read+0x571/0xc00 sty 22 09:00:49 michal-laptop kernel: ? ima_file_check+0x5a/0x80 sty 22 09:00:49 michal-laptop kernel: ? do_last+0x194/0x940 sty 22 09:00:49 michal-laptop kernel: generic_file_read_iter+0xdc/0x140 sty 22 09:00:49 michal-laptop kernel: fuse_file_read_iter+0x101/0x130 sty 22 09:00:49 michal-laptop kernel: ? do_filp_open+0xa5/0x100 sty 22 09:00:49 michal-laptop kernel: new_sync_read+0x122/0x1b0 sty 22 09:00:49 michal-laptop kernel: __vfs_read+0x29/0x40 sty 22 09:00:49 michal-laptop kernel: vfs_read+0xab/0x160 sty 22 09:00:49 michal-laptop kernel: ksys_read+0x67/0xe0 sty 22 09:00:49 michal-laptop kernel: __x64_sys_read+0x1a/0x20 sty 22 09:00:49 michal-laptop kernel: do_syscall_64+0x57/0x190 sty 22 09:00:49 michal-laptop kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 sty 22 09:00:49 michal-laptop kernel: RIP: 0033:0x7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: Code: Bad RIP value. sty 22 09:00:49 michal-laptop kernel: RSP: 002b:7f430bffda28 EFLAGS: 0246 ORIG_RAX: sty 22 09:00:49 michal-laptop kernel: RAX: ffda RBX: 492a RCX: 7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: RDX: 1000 RSI: 7f430bffda40 RDI: 0011 sty 22 09:00:49 michal-laptop kernel: RBP: 7f430bffda40 R08: R09: 7f430bffd9a8 sty 22 09:00:49 michal-laptop kernel: R10: R11: 0246 R12: 7f434670 sty 22 09:00:49 michal-laptop kernel: R13: 562dc32aaac0 R14: 0011 R15: 562dc32aaac0 A longer kernel log is attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 6829 F pulseaudio /dev/snd/controlC0: michal 6829 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 08:54:14 2020 InstallationDate: Installed on 2019-11-19 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i2bkio@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_i2bkio ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-20 (1 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.sku: XPS 12-9Q33 dmi.product.version: A08 dmi.sys.vendor:
[Kernel-packages] [Bug 1860512] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1860512/+attachment/5328397/+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/1860512 Title: Suspend unreliable (possibly FUSE related) Status in linux package in Ubuntu: Confirmed Bug description: Since updating to Focal my laptop stopped suspending reliably. It will sit there either without display or with the desktop stuck for almost a minute before it goes back to work again. Looking at the kernel logs this seems to be related to a FUSE mount that I have running: sty 22 09:00:49 michal-laptop kernel: Call Trace: sty 22 09:00:49 michal-laptop kernel: __schedule+0x2e3/0x740 sty 22 09:00:49 michal-laptop kernel: schedule+0x42/0xb0 sty 22 09:00:49 michal-laptop kernel: request_wait_answer+0xa0/0x200 sty 22 09:00:49 michal-laptop kernel: ? wait_woken+0x80/0x80 sty 22 09:00:49 michal-laptop kernel: fuse_simple_request+0x177/0x260 sty 22 09:00:49 michal-laptop kernel: fuse_send_readpages.isra.0+0xea/0xf0 sty 22 09:00:49 michal-laptop kernel: fuse_readpages+0xbc/0x110 sty 22 09:00:49 michal-laptop kernel: read_pages+0x71/0x1a0 sty 22 09:00:49 michal-laptop kernel: __do_page_cache_readahead+0x180/0x1a0 sty 22 09:00:49 michal-laptop kernel: ondemand_readahead+0x192/0x2d0 sty 22 09:00:49 michal-laptop kernel: page_cache_sync_readahead+0x78/0xc0 sty 22 09:00:49 michal-laptop kernel: generic_file_buffered_read+0x571/0xc00 sty 22 09:00:49 michal-laptop kernel: ? ima_file_check+0x5a/0x80 sty 22 09:00:49 michal-laptop kernel: ? do_last+0x194/0x940 sty 22 09:00:49 michal-laptop kernel: generic_file_read_iter+0xdc/0x140 sty 22 09:00:49 michal-laptop kernel: fuse_file_read_iter+0x101/0x130 sty 22 09:00:49 michal-laptop kernel: ? do_filp_open+0xa5/0x100 sty 22 09:00:49 michal-laptop kernel: new_sync_read+0x122/0x1b0 sty 22 09:00:49 michal-laptop kernel: __vfs_read+0x29/0x40 sty 22 09:00:49 michal-laptop kernel: vfs_read+0xab/0x160 sty 22 09:00:49 michal-laptop kernel: ksys_read+0x67/0xe0 sty 22 09:00:49 michal-laptop kernel: __x64_sys_read+0x1a/0x20 sty 22 09:00:49 michal-laptop kernel: do_syscall_64+0x57/0x190 sty 22 09:00:49 michal-laptop kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 sty 22 09:00:49 michal-laptop kernel: RIP: 0033:0x7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: Code: Bad RIP value. sty 22 09:00:49 michal-laptop kernel: RSP: 002b:7f430bffda28 EFLAGS: 0246 ORIG_RAX: sty 22 09:00:49 michal-laptop kernel: RAX: ffda RBX: 492a RCX: 7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: RDX: 1000 RSI: 7f430bffda40 RDI: 0011 sty 22 09:00:49 michal-laptop kernel: RBP: 7f430bffda40 R08: R09: 7f430bffd9a8 sty 22 09:00:49 michal-laptop kernel: R10: R11: 0246 R12: 7f434670 sty 22 09:00:49 michal-laptop kernel: R13: 562dc32aaac0 R14: 0011 R15: 562dc32aaac0 A longer kernel log is attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 6829 F pulseaudio /dev/snd/controlC0: michal 6829 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 08:54:14 2020 InstallationDate: Installed on 2019-11-19 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i2bkio@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_i2bkio ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-20 (1 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.sku: XPS 12-9Q33 dmi.product.version: A08
[Kernel-packages] [Bug 1860512] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1860512/+attachment/5328391/+files/AudioDevicesInUse.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/1860512 Title: Suspend unreliable (possibly FUSE related) Status in linux package in Ubuntu: Confirmed Bug description: Since updating to Focal my laptop stopped suspending reliably. It will sit there either without display or with the desktop stuck for almost a minute before it goes back to work again. Looking at the kernel logs this seems to be related to a FUSE mount that I have running: sty 22 09:00:49 michal-laptop kernel: Call Trace: sty 22 09:00:49 michal-laptop kernel: __schedule+0x2e3/0x740 sty 22 09:00:49 michal-laptop kernel: schedule+0x42/0xb0 sty 22 09:00:49 michal-laptop kernel: request_wait_answer+0xa0/0x200 sty 22 09:00:49 michal-laptop kernel: ? wait_woken+0x80/0x80 sty 22 09:00:49 michal-laptop kernel: fuse_simple_request+0x177/0x260 sty 22 09:00:49 michal-laptop kernel: fuse_send_readpages.isra.0+0xea/0xf0 sty 22 09:00:49 michal-laptop kernel: fuse_readpages+0xbc/0x110 sty 22 09:00:49 michal-laptop kernel: read_pages+0x71/0x1a0 sty 22 09:00:49 michal-laptop kernel: __do_page_cache_readahead+0x180/0x1a0 sty 22 09:00:49 michal-laptop kernel: ondemand_readahead+0x192/0x2d0 sty 22 09:00:49 michal-laptop kernel: page_cache_sync_readahead+0x78/0xc0 sty 22 09:00:49 michal-laptop kernel: generic_file_buffered_read+0x571/0xc00 sty 22 09:00:49 michal-laptop kernel: ? ima_file_check+0x5a/0x80 sty 22 09:00:49 michal-laptop kernel: ? do_last+0x194/0x940 sty 22 09:00:49 michal-laptop kernel: generic_file_read_iter+0xdc/0x140 sty 22 09:00:49 michal-laptop kernel: fuse_file_read_iter+0x101/0x130 sty 22 09:00:49 michal-laptop kernel: ? do_filp_open+0xa5/0x100 sty 22 09:00:49 michal-laptop kernel: new_sync_read+0x122/0x1b0 sty 22 09:00:49 michal-laptop kernel: __vfs_read+0x29/0x40 sty 22 09:00:49 michal-laptop kernel: vfs_read+0xab/0x160 sty 22 09:00:49 michal-laptop kernel: ksys_read+0x67/0xe0 sty 22 09:00:49 michal-laptop kernel: __x64_sys_read+0x1a/0x20 sty 22 09:00:49 michal-laptop kernel: do_syscall_64+0x57/0x190 sty 22 09:00:49 michal-laptop kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 sty 22 09:00:49 michal-laptop kernel: RIP: 0033:0x7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: Code: Bad RIP value. sty 22 09:00:49 michal-laptop kernel: RSP: 002b:7f430bffda28 EFLAGS: 0246 ORIG_RAX: sty 22 09:00:49 michal-laptop kernel: RAX: ffda RBX: 492a RCX: 7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: RDX: 1000 RSI: 7f430bffda40 RDI: 0011 sty 22 09:00:49 michal-laptop kernel: RBP: 7f430bffda40 R08: R09: 7f430bffd9a8 sty 22 09:00:49 michal-laptop kernel: R10: R11: 0246 R12: 7f434670 sty 22 09:00:49 michal-laptop kernel: R13: 562dc32aaac0 R14: 0011 R15: 562dc32aaac0 A longer kernel log is attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 6829 F pulseaudio /dev/snd/controlC0: michal 6829 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 08:54:14 2020 InstallationDate: Installed on 2019-11-19 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i2bkio@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_i2bkio ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-20 (1 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.sku: XPS 12-9Q33
[Kernel-packages] [Bug 1860512] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1860512/+attachment/5328393/+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/1860512 Title: Suspend unreliable (possibly FUSE related) Status in linux package in Ubuntu: Confirmed Bug description: Since updating to Focal my laptop stopped suspending reliably. It will sit there either without display or with the desktop stuck for almost a minute before it goes back to work again. Looking at the kernel logs this seems to be related to a FUSE mount that I have running: sty 22 09:00:49 michal-laptop kernel: Call Trace: sty 22 09:00:49 michal-laptop kernel: __schedule+0x2e3/0x740 sty 22 09:00:49 michal-laptop kernel: schedule+0x42/0xb0 sty 22 09:00:49 michal-laptop kernel: request_wait_answer+0xa0/0x200 sty 22 09:00:49 michal-laptop kernel: ? wait_woken+0x80/0x80 sty 22 09:00:49 michal-laptop kernel: fuse_simple_request+0x177/0x260 sty 22 09:00:49 michal-laptop kernel: fuse_send_readpages.isra.0+0xea/0xf0 sty 22 09:00:49 michal-laptop kernel: fuse_readpages+0xbc/0x110 sty 22 09:00:49 michal-laptop kernel: read_pages+0x71/0x1a0 sty 22 09:00:49 michal-laptop kernel: __do_page_cache_readahead+0x180/0x1a0 sty 22 09:00:49 michal-laptop kernel: ondemand_readahead+0x192/0x2d0 sty 22 09:00:49 michal-laptop kernel: page_cache_sync_readahead+0x78/0xc0 sty 22 09:00:49 michal-laptop kernel: generic_file_buffered_read+0x571/0xc00 sty 22 09:00:49 michal-laptop kernel: ? ima_file_check+0x5a/0x80 sty 22 09:00:49 michal-laptop kernel: ? do_last+0x194/0x940 sty 22 09:00:49 michal-laptop kernel: generic_file_read_iter+0xdc/0x140 sty 22 09:00:49 michal-laptop kernel: fuse_file_read_iter+0x101/0x130 sty 22 09:00:49 michal-laptop kernel: ? do_filp_open+0xa5/0x100 sty 22 09:00:49 michal-laptop kernel: new_sync_read+0x122/0x1b0 sty 22 09:00:49 michal-laptop kernel: __vfs_read+0x29/0x40 sty 22 09:00:49 michal-laptop kernel: vfs_read+0xab/0x160 sty 22 09:00:49 michal-laptop kernel: ksys_read+0x67/0xe0 sty 22 09:00:49 michal-laptop kernel: __x64_sys_read+0x1a/0x20 sty 22 09:00:49 michal-laptop kernel: do_syscall_64+0x57/0x190 sty 22 09:00:49 michal-laptop kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 sty 22 09:00:49 michal-laptop kernel: RIP: 0033:0x7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: Code: Bad RIP value. sty 22 09:00:49 michal-laptop kernel: RSP: 002b:7f430bffda28 EFLAGS: 0246 ORIG_RAX: sty 22 09:00:49 michal-laptop kernel: RAX: ffda RBX: 492a RCX: 7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: RDX: 1000 RSI: 7f430bffda40 RDI: 0011 sty 22 09:00:49 michal-laptop kernel: RBP: 7f430bffda40 R08: R09: 7f430bffd9a8 sty 22 09:00:49 michal-laptop kernel: R10: R11: 0246 R12: 7f434670 sty 22 09:00:49 michal-laptop kernel: R13: 562dc32aaac0 R14: 0011 R15: 562dc32aaac0 A longer kernel log is attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 6829 F pulseaudio /dev/snd/controlC0: michal 6829 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 08:54:14 2020 InstallationDate: Installed on 2019-11-19 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i2bkio@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_i2bkio ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-20 (1 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.sku: XPS 12-9Q33 dmi.product.version: A08
[Kernel-packages] [Bug 1860512] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1860512/+attachment/5328398/+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/1860512 Title: Suspend unreliable (possibly FUSE related) Status in linux package in Ubuntu: Confirmed Bug description: Since updating to Focal my laptop stopped suspending reliably. It will sit there either without display or with the desktop stuck for almost a minute before it goes back to work again. Looking at the kernel logs this seems to be related to a FUSE mount that I have running: sty 22 09:00:49 michal-laptop kernel: Call Trace: sty 22 09:00:49 michal-laptop kernel: __schedule+0x2e3/0x740 sty 22 09:00:49 michal-laptop kernel: schedule+0x42/0xb0 sty 22 09:00:49 michal-laptop kernel: request_wait_answer+0xa0/0x200 sty 22 09:00:49 michal-laptop kernel: ? wait_woken+0x80/0x80 sty 22 09:00:49 michal-laptop kernel: fuse_simple_request+0x177/0x260 sty 22 09:00:49 michal-laptop kernel: fuse_send_readpages.isra.0+0xea/0xf0 sty 22 09:00:49 michal-laptop kernel: fuse_readpages+0xbc/0x110 sty 22 09:00:49 michal-laptop kernel: read_pages+0x71/0x1a0 sty 22 09:00:49 michal-laptop kernel: __do_page_cache_readahead+0x180/0x1a0 sty 22 09:00:49 michal-laptop kernel: ondemand_readahead+0x192/0x2d0 sty 22 09:00:49 michal-laptop kernel: page_cache_sync_readahead+0x78/0xc0 sty 22 09:00:49 michal-laptop kernel: generic_file_buffered_read+0x571/0xc00 sty 22 09:00:49 michal-laptop kernel: ? ima_file_check+0x5a/0x80 sty 22 09:00:49 michal-laptop kernel: ? do_last+0x194/0x940 sty 22 09:00:49 michal-laptop kernel: generic_file_read_iter+0xdc/0x140 sty 22 09:00:49 michal-laptop kernel: fuse_file_read_iter+0x101/0x130 sty 22 09:00:49 michal-laptop kernel: ? do_filp_open+0xa5/0x100 sty 22 09:00:49 michal-laptop kernel: new_sync_read+0x122/0x1b0 sty 22 09:00:49 michal-laptop kernel: __vfs_read+0x29/0x40 sty 22 09:00:49 michal-laptop kernel: vfs_read+0xab/0x160 sty 22 09:00:49 michal-laptop kernel: ksys_read+0x67/0xe0 sty 22 09:00:49 michal-laptop kernel: __x64_sys_read+0x1a/0x20 sty 22 09:00:49 michal-laptop kernel: do_syscall_64+0x57/0x190 sty 22 09:00:49 michal-laptop kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 sty 22 09:00:49 michal-laptop kernel: RIP: 0033:0x7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: Code: Bad RIP value. sty 22 09:00:49 michal-laptop kernel: RSP: 002b:7f430bffda28 EFLAGS: 0246 ORIG_RAX: sty 22 09:00:49 michal-laptop kernel: RAX: ffda RBX: 492a RCX: 7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: RDX: 1000 RSI: 7f430bffda40 RDI: 0011 sty 22 09:00:49 michal-laptop kernel: RBP: 7f430bffda40 R08: R09: 7f430bffd9a8 sty 22 09:00:49 michal-laptop kernel: R10: R11: 0246 R12: 7f434670 sty 22 09:00:49 michal-laptop kernel: R13: 562dc32aaac0 R14: 0011 R15: 562dc32aaac0 A longer kernel log is attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 6829 F pulseaudio /dev/snd/controlC0: michal 6829 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 08:54:14 2020 InstallationDate: Installed on 2019-11-19 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i2bkio@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_i2bkio ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-20 (1 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.sku: XPS 12-9Q33 dmi.product.version: A08
[Kernel-packages] [Bug 1863411] Re: Suspend broken, tasks refuzing to freeze
*** This bug is a duplicate of bug 1860512 *** https://bugs.launchpad.net/bugs/1860512 dmesg: [72058.342902] PM: suspend entry (deep) [72062.442159] Filesystems sync: 5.099 seconds [72062.448722] Freezing user space processes ... [72082.451003] Freezing of tasks failed after 20.002 seconds (1 tasks refusing to freeze, wq_busy=0): [72082.451106] single D0 6208 4845 0x4324 [72082.45] Call Trace: [72082.451125] __schedule+0x2e3/0x740 [72082.451131] schedule+0x42/0xb0 [72082.451135] io_schedule+0x16/0x40 [72082.451144] __lock_page+0x128/0x230 [72082.451151] ? file_fdatawait_range+0x30/0x30 [72082.451160] invalidate_inode_pages2_range+0x3a5/0x540 [72082.451167] ? fuse_put_request+0x42/0xb0 [72082.451176] invalidate_inode_pages2+0x17/0x20 [72082.451182] fuse_finish_open+0x86/0x100 [72082.451187] ? fuse_open_common+0x110/0x110 [72082.451192] fuse_open_common+0xe2/0x110 [72082.451196] ? fuse_open_common+0x110/0x110 [72082.451201] fuse_open+0x10/0x20 [72082.451206] do_dentry_open+0x143/0x3a0 [72082.451211] vfs_open+0x2d/0x30 [72082.451216] do_last+0x194/0x900 [72082.451221] path_openat+0x8d/0x290 [72082.451226] do_filp_open+0x91/0x100 [72082.451247] ? __alloc_fd+0x46/0x150 [72082.451252] do_sys_open+0x17e/0x290 [72082.451257] __x64_sys_openat+0x20/0x30 [72082.451266] do_syscall_64+0x57/0x190 [72082.451274] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [72082.451278] RIP: 0033:0x7fce91985064 [72082.451289] Code: Bad RIP value. [72082.451292] RSP: 002b:7fce4bffe670 EFLAGS: 0293 ORIG_RAX: 0101 [72082.451296] RAX: ffda RBX: 7fce40005210 RCX: 7fce91985064 [72082.451299] RDX: RSI: 7fce4004a290 RDI: ff9c [72082.451301] RBP: 7fce4004a290 R08: R09: 0001 [72082.451303] R10: R11: 0293 R12: [72082.451305] R13: 7fce4bffe810 R14: 7fce4bffea90 R15: 7fce4bffea70 [72082.451408] OOM killer enabled. [72082.451410] Restarting tasks ... done. [72082.662534] PM: suspend exit [72082.662610] PM: suspend entry (s2idle) [72082.760296] Filesystems sync: 0.097 seconds [72082.760532] Freezing user space processes ... [72102.767130] Freezing of tasks failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0): [72102.767229] single D0 6208 4845 0x4324 [72102.767234] Call Trace: [72102.767248] __schedule+0x2e3/0x740 [72102.767254] schedule+0x42/0xb0 [72102.767258] io_schedule+0x16/0x40 [72102.767268] __lock_page+0x128/0x230 [72102.767275] ? file_fdatawait_range+0x30/0x30 [72102.767285] invalidate_inode_pages2_range+0x3a5/0x540 [72102.767291] ? fuse_put_request+0x42/0xb0 [72102.767301] invalidate_inode_pages2+0x17/0x20 [72102.767306] fuse_finish_open+0x86/0x100 [72102.767311] ? fuse_open_common+0x110/0x110 [72102.767316] fuse_open_common+0xe2/0x110 [72102.767321] ? fuse_open_common+0x110/0x110 [72102.767325] fuse_open+0x10/0x20 [72102.767330] do_dentry_open+0x143/0x3a0 [72102.767335] vfs_open+0x2d/0x30 [72102.767340] do_last+0x194/0x900 [72102.767345] path_openat+0x8d/0x290 [72102.767350] do_filp_open+0x91/0x100 [72102.767358] ? __alloc_fd+0x46/0x150 [72102.767363] do_sys_open+0x17e/0x290 [72102.767368] __x64_sys_openat+0x20/0x30 [72102.767377] do_syscall_64+0x57/0x190 [72102.767384] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [72102.767388] RIP: 0033:0x7fce91985064 [72102.767400] Code: Bad RIP value. [72102.767402] RSP: 002b:7fce4bffe670 EFLAGS: 0293 ORIG_RAX: 0101 [72102.767407] RAX: ffda RBX: 7fce40005210 RCX: 7fce91985064 [72102.767409] RDX: RSI: 7fce4004a290 RDI: ff9c [72102.767411] RBP: 7fce4004a290 R08: R09: 0001 [72102.767413] R10: R11: 0293 R12: [72102.767415] R13: 7fce4bffe810 R14: 7fce4bffea90 R15: 7fce4bffea70 [72102.767521] OOM killer enabled. [72102.767523] Restarting tasks ... done. [72102.978599] PM: suspend exit ** This bug has been marked a duplicate of bug 1860512 Suspend unreliable (possibly FUSE related) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1863411 Title: Suspend broken, tasks refuzing to freeze Status in linux-signed-5.4 package in Ubuntu: New Bug description: My laptop stopped suspending recently. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 15 10:55:21 2020 InstallationDate: Installed on 2020-02-10 (4 days ago) InstallationMedia: Ubuntu 20.04
[Kernel-packages] [Bug 1860512] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1860512/+attachment/5328399/+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/1860512 Title: Suspend unreliable (possibly FUSE related) Status in linux package in Ubuntu: Confirmed Bug description: Since updating to Focal my laptop stopped suspending reliably. It will sit there either without display or with the desktop stuck for almost a minute before it goes back to work again. Looking at the kernel logs this seems to be related to a FUSE mount that I have running: sty 22 09:00:49 michal-laptop kernel: Call Trace: sty 22 09:00:49 michal-laptop kernel: __schedule+0x2e3/0x740 sty 22 09:00:49 michal-laptop kernel: schedule+0x42/0xb0 sty 22 09:00:49 michal-laptop kernel: request_wait_answer+0xa0/0x200 sty 22 09:00:49 michal-laptop kernel: ? wait_woken+0x80/0x80 sty 22 09:00:49 michal-laptop kernel: fuse_simple_request+0x177/0x260 sty 22 09:00:49 michal-laptop kernel: fuse_send_readpages.isra.0+0xea/0xf0 sty 22 09:00:49 michal-laptop kernel: fuse_readpages+0xbc/0x110 sty 22 09:00:49 michal-laptop kernel: read_pages+0x71/0x1a0 sty 22 09:00:49 michal-laptop kernel: __do_page_cache_readahead+0x180/0x1a0 sty 22 09:00:49 michal-laptop kernel: ondemand_readahead+0x192/0x2d0 sty 22 09:00:49 michal-laptop kernel: page_cache_sync_readahead+0x78/0xc0 sty 22 09:00:49 michal-laptop kernel: generic_file_buffered_read+0x571/0xc00 sty 22 09:00:49 michal-laptop kernel: ? ima_file_check+0x5a/0x80 sty 22 09:00:49 michal-laptop kernel: ? do_last+0x194/0x940 sty 22 09:00:49 michal-laptop kernel: generic_file_read_iter+0xdc/0x140 sty 22 09:00:49 michal-laptop kernel: fuse_file_read_iter+0x101/0x130 sty 22 09:00:49 michal-laptop kernel: ? do_filp_open+0xa5/0x100 sty 22 09:00:49 michal-laptop kernel: new_sync_read+0x122/0x1b0 sty 22 09:00:49 michal-laptop kernel: __vfs_read+0x29/0x40 sty 22 09:00:49 michal-laptop kernel: vfs_read+0xab/0x160 sty 22 09:00:49 michal-laptop kernel: ksys_read+0x67/0xe0 sty 22 09:00:49 michal-laptop kernel: __x64_sys_read+0x1a/0x20 sty 22 09:00:49 michal-laptop kernel: do_syscall_64+0x57/0x190 sty 22 09:00:49 michal-laptop kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 sty 22 09:00:49 michal-laptop kernel: RIP: 0033:0x7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: Code: Bad RIP value. sty 22 09:00:49 michal-laptop kernel: RSP: 002b:7f430bffda28 EFLAGS: 0246 ORIG_RAX: sty 22 09:00:49 michal-laptop kernel: RAX: ffda RBX: 492a RCX: 7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: RDX: 1000 RSI: 7f430bffda40 RDI: 0011 sty 22 09:00:49 michal-laptop kernel: RBP: 7f430bffda40 R08: R09: 7f430bffd9a8 sty 22 09:00:49 michal-laptop kernel: R10: R11: 0246 R12: 7f434670 sty 22 09:00:49 michal-laptop kernel: R13: 562dc32aaac0 R14: 0011 R15: 562dc32aaac0 A longer kernel log is attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 6829 F pulseaudio /dev/snd/controlC0: michal 6829 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 08:54:14 2020 InstallationDate: Installed on 2019-11-19 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i2bkio@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_i2bkio ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-20 (1 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.sku: XPS 12-9Q33 dmi.product.version: A08
[Kernel-packages] [Bug 1860512] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1860512/+attachment/5328392/+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/1860512 Title: Suspend unreliable (possibly FUSE related) Status in linux package in Ubuntu: Confirmed Bug description: Since updating to Focal my laptop stopped suspending reliably. It will sit there either without display or with the desktop stuck for almost a minute before it goes back to work again. Looking at the kernel logs this seems to be related to a FUSE mount that I have running: sty 22 09:00:49 michal-laptop kernel: Call Trace: sty 22 09:00:49 michal-laptop kernel: __schedule+0x2e3/0x740 sty 22 09:00:49 michal-laptop kernel: schedule+0x42/0xb0 sty 22 09:00:49 michal-laptop kernel: request_wait_answer+0xa0/0x200 sty 22 09:00:49 michal-laptop kernel: ? wait_woken+0x80/0x80 sty 22 09:00:49 michal-laptop kernel: fuse_simple_request+0x177/0x260 sty 22 09:00:49 michal-laptop kernel: fuse_send_readpages.isra.0+0xea/0xf0 sty 22 09:00:49 michal-laptop kernel: fuse_readpages+0xbc/0x110 sty 22 09:00:49 michal-laptop kernel: read_pages+0x71/0x1a0 sty 22 09:00:49 michal-laptop kernel: __do_page_cache_readahead+0x180/0x1a0 sty 22 09:00:49 michal-laptop kernel: ondemand_readahead+0x192/0x2d0 sty 22 09:00:49 michal-laptop kernel: page_cache_sync_readahead+0x78/0xc0 sty 22 09:00:49 michal-laptop kernel: generic_file_buffered_read+0x571/0xc00 sty 22 09:00:49 michal-laptop kernel: ? ima_file_check+0x5a/0x80 sty 22 09:00:49 michal-laptop kernel: ? do_last+0x194/0x940 sty 22 09:00:49 michal-laptop kernel: generic_file_read_iter+0xdc/0x140 sty 22 09:00:49 michal-laptop kernel: fuse_file_read_iter+0x101/0x130 sty 22 09:00:49 michal-laptop kernel: ? do_filp_open+0xa5/0x100 sty 22 09:00:49 michal-laptop kernel: new_sync_read+0x122/0x1b0 sty 22 09:00:49 michal-laptop kernel: __vfs_read+0x29/0x40 sty 22 09:00:49 michal-laptop kernel: vfs_read+0xab/0x160 sty 22 09:00:49 michal-laptop kernel: ksys_read+0x67/0xe0 sty 22 09:00:49 michal-laptop kernel: __x64_sys_read+0x1a/0x20 sty 22 09:00:49 michal-laptop kernel: do_syscall_64+0x57/0x190 sty 22 09:00:49 michal-laptop kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 sty 22 09:00:49 michal-laptop kernel: RIP: 0033:0x7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: Code: Bad RIP value. sty 22 09:00:49 michal-laptop kernel: RSP: 002b:7f430bffda28 EFLAGS: 0246 ORIG_RAX: sty 22 09:00:49 michal-laptop kernel: RAX: ffda RBX: 492a RCX: 7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: RDX: 1000 RSI: 7f430bffda40 RDI: 0011 sty 22 09:00:49 michal-laptop kernel: RBP: 7f430bffda40 R08: R09: 7f430bffd9a8 sty 22 09:00:49 michal-laptop kernel: R10: R11: 0246 R12: 7f434670 sty 22 09:00:49 michal-laptop kernel: R13: 562dc32aaac0 R14: 0011 R15: 562dc32aaac0 A longer kernel log is attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 6829 F pulseaudio /dev/snd/controlC0: michal 6829 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 08:54:14 2020 InstallationDate: Installed on 2019-11-19 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i2bkio@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_i2bkio ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-20 (1 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.sku: XPS 12-9Q33 dmi.product.version: A08 dmi.sys.vendor:
[Kernel-packages] [Bug 1860512] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1860512/+attachment/5328395/+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/1860512 Title: Suspend unreliable (possibly FUSE related) Status in linux package in Ubuntu: Confirmed Bug description: Since updating to Focal my laptop stopped suspending reliably. It will sit there either without display or with the desktop stuck for almost a minute before it goes back to work again. Looking at the kernel logs this seems to be related to a FUSE mount that I have running: sty 22 09:00:49 michal-laptop kernel: Call Trace: sty 22 09:00:49 michal-laptop kernel: __schedule+0x2e3/0x740 sty 22 09:00:49 michal-laptop kernel: schedule+0x42/0xb0 sty 22 09:00:49 michal-laptop kernel: request_wait_answer+0xa0/0x200 sty 22 09:00:49 michal-laptop kernel: ? wait_woken+0x80/0x80 sty 22 09:00:49 michal-laptop kernel: fuse_simple_request+0x177/0x260 sty 22 09:00:49 michal-laptop kernel: fuse_send_readpages.isra.0+0xea/0xf0 sty 22 09:00:49 michal-laptop kernel: fuse_readpages+0xbc/0x110 sty 22 09:00:49 michal-laptop kernel: read_pages+0x71/0x1a0 sty 22 09:00:49 michal-laptop kernel: __do_page_cache_readahead+0x180/0x1a0 sty 22 09:00:49 michal-laptop kernel: ondemand_readahead+0x192/0x2d0 sty 22 09:00:49 michal-laptop kernel: page_cache_sync_readahead+0x78/0xc0 sty 22 09:00:49 michal-laptop kernel: generic_file_buffered_read+0x571/0xc00 sty 22 09:00:49 michal-laptop kernel: ? ima_file_check+0x5a/0x80 sty 22 09:00:49 michal-laptop kernel: ? do_last+0x194/0x940 sty 22 09:00:49 michal-laptop kernel: generic_file_read_iter+0xdc/0x140 sty 22 09:00:49 michal-laptop kernel: fuse_file_read_iter+0x101/0x130 sty 22 09:00:49 michal-laptop kernel: ? do_filp_open+0xa5/0x100 sty 22 09:00:49 michal-laptop kernel: new_sync_read+0x122/0x1b0 sty 22 09:00:49 michal-laptop kernel: __vfs_read+0x29/0x40 sty 22 09:00:49 michal-laptop kernel: vfs_read+0xab/0x160 sty 22 09:00:49 michal-laptop kernel: ksys_read+0x67/0xe0 sty 22 09:00:49 michal-laptop kernel: __x64_sys_read+0x1a/0x20 sty 22 09:00:49 michal-laptop kernel: do_syscall_64+0x57/0x190 sty 22 09:00:49 michal-laptop kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 sty 22 09:00:49 michal-laptop kernel: RIP: 0033:0x7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: Code: Bad RIP value. sty 22 09:00:49 michal-laptop kernel: RSP: 002b:7f430bffda28 EFLAGS: 0246 ORIG_RAX: sty 22 09:00:49 michal-laptop kernel: RAX: ffda RBX: 492a RCX: 7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: RDX: 1000 RSI: 7f430bffda40 RDI: 0011 sty 22 09:00:49 michal-laptop kernel: RBP: 7f430bffda40 R08: R09: 7f430bffd9a8 sty 22 09:00:49 michal-laptop kernel: R10: R11: 0246 R12: 7f434670 sty 22 09:00:49 michal-laptop kernel: R13: 562dc32aaac0 R14: 0011 R15: 562dc32aaac0 A longer kernel log is attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 6829 F pulseaudio /dev/snd/controlC0: michal 6829 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 08:54:14 2020 InstallationDate: Installed on 2019-11-19 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i2bkio@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_i2bkio ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-20 (1 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.sku: XPS 12-9Q33 dmi.product.version: A08 dmi.sys.vendor:
[Kernel-packages] [Bug 1860512] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1860512/+attachment/5328394/+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/1860512 Title: Suspend unreliable (possibly FUSE related) Status in linux package in Ubuntu: Confirmed Bug description: Since updating to Focal my laptop stopped suspending reliably. It will sit there either without display or with the desktop stuck for almost a minute before it goes back to work again. Looking at the kernel logs this seems to be related to a FUSE mount that I have running: sty 22 09:00:49 michal-laptop kernel: Call Trace: sty 22 09:00:49 michal-laptop kernel: __schedule+0x2e3/0x740 sty 22 09:00:49 michal-laptop kernel: schedule+0x42/0xb0 sty 22 09:00:49 michal-laptop kernel: request_wait_answer+0xa0/0x200 sty 22 09:00:49 michal-laptop kernel: ? wait_woken+0x80/0x80 sty 22 09:00:49 michal-laptop kernel: fuse_simple_request+0x177/0x260 sty 22 09:00:49 michal-laptop kernel: fuse_send_readpages.isra.0+0xea/0xf0 sty 22 09:00:49 michal-laptop kernel: fuse_readpages+0xbc/0x110 sty 22 09:00:49 michal-laptop kernel: read_pages+0x71/0x1a0 sty 22 09:00:49 michal-laptop kernel: __do_page_cache_readahead+0x180/0x1a0 sty 22 09:00:49 michal-laptop kernel: ondemand_readahead+0x192/0x2d0 sty 22 09:00:49 michal-laptop kernel: page_cache_sync_readahead+0x78/0xc0 sty 22 09:00:49 michal-laptop kernel: generic_file_buffered_read+0x571/0xc00 sty 22 09:00:49 michal-laptop kernel: ? ima_file_check+0x5a/0x80 sty 22 09:00:49 michal-laptop kernel: ? do_last+0x194/0x940 sty 22 09:00:49 michal-laptop kernel: generic_file_read_iter+0xdc/0x140 sty 22 09:00:49 michal-laptop kernel: fuse_file_read_iter+0x101/0x130 sty 22 09:00:49 michal-laptop kernel: ? do_filp_open+0xa5/0x100 sty 22 09:00:49 michal-laptop kernel: new_sync_read+0x122/0x1b0 sty 22 09:00:49 michal-laptop kernel: __vfs_read+0x29/0x40 sty 22 09:00:49 michal-laptop kernel: vfs_read+0xab/0x160 sty 22 09:00:49 michal-laptop kernel: ksys_read+0x67/0xe0 sty 22 09:00:49 michal-laptop kernel: __x64_sys_read+0x1a/0x20 sty 22 09:00:49 michal-laptop kernel: do_syscall_64+0x57/0x190 sty 22 09:00:49 michal-laptop kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 sty 22 09:00:49 michal-laptop kernel: RIP: 0033:0x7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: Code: Bad RIP value. sty 22 09:00:49 michal-laptop kernel: RSP: 002b:7f430bffda28 EFLAGS: 0246 ORIG_RAX: sty 22 09:00:49 michal-laptop kernel: RAX: ffda RBX: 492a RCX: 7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: RDX: 1000 RSI: 7f430bffda40 RDI: 0011 sty 22 09:00:49 michal-laptop kernel: RBP: 7f430bffda40 R08: R09: 7f430bffd9a8 sty 22 09:00:49 michal-laptop kernel: R10: R11: 0246 R12: 7f434670 sty 22 09:00:49 michal-laptop kernel: R13: 562dc32aaac0 R14: 0011 R15: 562dc32aaac0 A longer kernel log is attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 6829 F pulseaudio /dev/snd/controlC0: michal 6829 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 08:54:14 2020 InstallationDate: Installed on 2019-11-19 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i2bkio@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_i2bkio ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-20 (1 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.sku: XPS 12-9Q33 dmi.product.version: A08
[Kernel-packages] [Bug 1860512] Re: Suspend unreliable (possibly FUSE related)
This came back with bug #1863411. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: apport-collected staging ** Description changed: Since updating to Focal my laptop stopped suspending reliably. It will sit there either without display or with the desktop stuck for almost a minute before it goes back to work again. Looking at the kernel logs this seems to be related to a FUSE mount that I have running: sty 22 09:00:49 michal-laptop kernel: Call Trace: sty 22 09:00:49 michal-laptop kernel: __schedule+0x2e3/0x740 sty 22 09:00:49 michal-laptop kernel: schedule+0x42/0xb0 sty 22 09:00:49 michal-laptop kernel: request_wait_answer+0xa0/0x200 sty 22 09:00:49 michal-laptop kernel: ? wait_woken+0x80/0x80 sty 22 09:00:49 michal-laptop kernel: fuse_simple_request+0x177/0x260 sty 22 09:00:49 michal-laptop kernel: fuse_send_readpages.isra.0+0xea/0xf0 sty 22 09:00:49 michal-laptop kernel: fuse_readpages+0xbc/0x110 sty 22 09:00:49 michal-laptop kernel: read_pages+0x71/0x1a0 sty 22 09:00:49 michal-laptop kernel: __do_page_cache_readahead+0x180/0x1a0 sty 22 09:00:49 michal-laptop kernel: ondemand_readahead+0x192/0x2d0 sty 22 09:00:49 michal-laptop kernel: page_cache_sync_readahead+0x78/0xc0 sty 22 09:00:49 michal-laptop kernel: generic_file_buffered_read+0x571/0xc00 sty 22 09:00:49 michal-laptop kernel: ? ima_file_check+0x5a/0x80 sty 22 09:00:49 michal-laptop kernel: ? do_last+0x194/0x940 sty 22 09:00:49 michal-laptop kernel: generic_file_read_iter+0xdc/0x140 sty 22 09:00:49 michal-laptop kernel: fuse_file_read_iter+0x101/0x130 sty 22 09:00:49 michal-laptop kernel: ? do_filp_open+0xa5/0x100 sty 22 09:00:49 michal-laptop kernel: new_sync_read+0x122/0x1b0 sty 22 09:00:49 michal-laptop kernel: __vfs_read+0x29/0x40 sty 22 09:00:49 michal-laptop kernel: vfs_read+0xab/0x160 sty 22 09:00:49 michal-laptop kernel: ksys_read+0x67/0xe0 sty 22 09:00:49 michal-laptop kernel: __x64_sys_read+0x1a/0x20 sty 22 09:00:49 michal-laptop kernel: do_syscall_64+0x57/0x190 sty 22 09:00:49 michal-laptop kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 sty 22 09:00:49 michal-laptop kernel: RIP: 0033:0x7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: Code: Bad RIP value. sty 22 09:00:49 michal-laptop kernel: RSP: 002b:7f430bffda28 EFLAGS: 0246 ORIG_RAX: sty 22 09:00:49 michal-laptop kernel: RAX: ffda RBX: 492a RCX: 7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: RDX: 1000 RSI: 7f430bffda40 RDI: 0011 sty 22 09:00:49 michal-laptop kernel: RBP: 7f430bffda40 R08: R09: 7f430bffd9a8 sty 22 09:00:49 michal-laptop kernel: R10: R11: 0246 R12: 7f434670 sty 22 09:00:49 michal-laptop kernel: R13: 562dc32aaac0 R14: 0011 R15: 562dc32aaac0 A longer kernel log is attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 6829 F pulseaudio /dev/snd/controlC0: michal 6829 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 08:54:14 2020 InstallationDate: Installed on 2019-11-19 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i2bkio@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_i2bkio ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-20 (1 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.sku: XPS 12-9Q33 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu16 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-02-10 (4 days ago) + InstallationMedia:
[Kernel-packages] [Bug 1860512] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1860512/+attachment/5328406/+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/1860512 Title: Suspend unreliable (possibly FUSE related) Status in linux package in Ubuntu: Confirmed Bug description: Since updating to Focal my laptop stopped suspending reliably. It will sit there either without display or with the desktop stuck for almost a minute before it goes back to work again. Looking at the kernel logs this seems to be related to a FUSE mount that I have running: sty 22 09:00:49 michal-laptop kernel: Call Trace: sty 22 09:00:49 michal-laptop kernel: __schedule+0x2e3/0x740 sty 22 09:00:49 michal-laptop kernel: schedule+0x42/0xb0 sty 22 09:00:49 michal-laptop kernel: request_wait_answer+0xa0/0x200 sty 22 09:00:49 michal-laptop kernel: ? wait_woken+0x80/0x80 sty 22 09:00:49 michal-laptop kernel: fuse_simple_request+0x177/0x260 sty 22 09:00:49 michal-laptop kernel: fuse_send_readpages.isra.0+0xea/0xf0 sty 22 09:00:49 michal-laptop kernel: fuse_readpages+0xbc/0x110 sty 22 09:00:49 michal-laptop kernel: read_pages+0x71/0x1a0 sty 22 09:00:49 michal-laptop kernel: __do_page_cache_readahead+0x180/0x1a0 sty 22 09:00:49 michal-laptop kernel: ondemand_readahead+0x192/0x2d0 sty 22 09:00:49 michal-laptop kernel: page_cache_sync_readahead+0x78/0xc0 sty 22 09:00:49 michal-laptop kernel: generic_file_buffered_read+0x571/0xc00 sty 22 09:00:49 michal-laptop kernel: ? ima_file_check+0x5a/0x80 sty 22 09:00:49 michal-laptop kernel: ? do_last+0x194/0x940 sty 22 09:00:49 michal-laptop kernel: generic_file_read_iter+0xdc/0x140 sty 22 09:00:49 michal-laptop kernel: fuse_file_read_iter+0x101/0x130 sty 22 09:00:49 michal-laptop kernel: ? do_filp_open+0xa5/0x100 sty 22 09:00:49 michal-laptop kernel: new_sync_read+0x122/0x1b0 sty 22 09:00:49 michal-laptop kernel: __vfs_read+0x29/0x40 sty 22 09:00:49 michal-laptop kernel: vfs_read+0xab/0x160 sty 22 09:00:49 michal-laptop kernel: ksys_read+0x67/0xe0 sty 22 09:00:49 michal-laptop kernel: __x64_sys_read+0x1a/0x20 sty 22 09:00:49 michal-laptop kernel: do_syscall_64+0x57/0x190 sty 22 09:00:49 michal-laptop kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 sty 22 09:00:49 michal-laptop kernel: RIP: 0033:0x7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: Code: Bad RIP value. sty 22 09:00:49 michal-laptop kernel: RSP: 002b:7f430bffda28 EFLAGS: 0246 ORIG_RAX: sty 22 09:00:49 michal-laptop kernel: RAX: ffda RBX: 492a RCX: 7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: RDX: 1000 RSI: 7f430bffda40 RDI: 0011 sty 22 09:00:49 michal-laptop kernel: RBP: 7f430bffda40 R08: R09: 7f430bffd9a8 sty 22 09:00:49 michal-laptop kernel: R10: R11: 0246 R12: 7f434670 sty 22 09:00:49 michal-laptop kernel: R13: 562dc32aaac0 R14: 0011 R15: 562dc32aaac0 A longer kernel log is attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 6829 F pulseaudio /dev/snd/controlC0: michal 6829 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 08:54:14 2020 InstallationDate: Installed on 2019-11-19 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i2bkio@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_i2bkio ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-20 (1 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.sku: XPS 12-9Q33 dmi.product.version: A08
[Kernel-packages] [Bug 1860512] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1860512/+attachment/5328402/+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/1860512 Title: Suspend unreliable (possibly FUSE related) Status in linux package in Ubuntu: Confirmed Bug description: Since updating to Focal my laptop stopped suspending reliably. It will sit there either without display or with the desktop stuck for almost a minute before it goes back to work again. Looking at the kernel logs this seems to be related to a FUSE mount that I have running: sty 22 09:00:49 michal-laptop kernel: Call Trace: sty 22 09:00:49 michal-laptop kernel: __schedule+0x2e3/0x740 sty 22 09:00:49 michal-laptop kernel: schedule+0x42/0xb0 sty 22 09:00:49 michal-laptop kernel: request_wait_answer+0xa0/0x200 sty 22 09:00:49 michal-laptop kernel: ? wait_woken+0x80/0x80 sty 22 09:00:49 michal-laptop kernel: fuse_simple_request+0x177/0x260 sty 22 09:00:49 michal-laptop kernel: fuse_send_readpages.isra.0+0xea/0xf0 sty 22 09:00:49 michal-laptop kernel: fuse_readpages+0xbc/0x110 sty 22 09:00:49 michal-laptop kernel: read_pages+0x71/0x1a0 sty 22 09:00:49 michal-laptop kernel: __do_page_cache_readahead+0x180/0x1a0 sty 22 09:00:49 michal-laptop kernel: ondemand_readahead+0x192/0x2d0 sty 22 09:00:49 michal-laptop kernel: page_cache_sync_readahead+0x78/0xc0 sty 22 09:00:49 michal-laptop kernel: generic_file_buffered_read+0x571/0xc00 sty 22 09:00:49 michal-laptop kernel: ? ima_file_check+0x5a/0x80 sty 22 09:00:49 michal-laptop kernel: ? do_last+0x194/0x940 sty 22 09:00:49 michal-laptop kernel: generic_file_read_iter+0xdc/0x140 sty 22 09:00:49 michal-laptop kernel: fuse_file_read_iter+0x101/0x130 sty 22 09:00:49 michal-laptop kernel: ? do_filp_open+0xa5/0x100 sty 22 09:00:49 michal-laptop kernel: new_sync_read+0x122/0x1b0 sty 22 09:00:49 michal-laptop kernel: __vfs_read+0x29/0x40 sty 22 09:00:49 michal-laptop kernel: vfs_read+0xab/0x160 sty 22 09:00:49 michal-laptop kernel: ksys_read+0x67/0xe0 sty 22 09:00:49 michal-laptop kernel: __x64_sys_read+0x1a/0x20 sty 22 09:00:49 michal-laptop kernel: do_syscall_64+0x57/0x190 sty 22 09:00:49 michal-laptop kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 sty 22 09:00:49 michal-laptop kernel: RIP: 0033:0x7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: Code: Bad RIP value. sty 22 09:00:49 michal-laptop kernel: RSP: 002b:7f430bffda28 EFLAGS: 0246 ORIG_RAX: sty 22 09:00:49 michal-laptop kernel: RAX: ffda RBX: 492a RCX: 7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: RDX: 1000 RSI: 7f430bffda40 RDI: 0011 sty 22 09:00:49 michal-laptop kernel: RBP: 7f430bffda40 R08: R09: 7f430bffd9a8 sty 22 09:00:49 michal-laptop kernel: R10: R11: 0246 R12: 7f434670 sty 22 09:00:49 michal-laptop kernel: R13: 562dc32aaac0 R14: 0011 R15: 562dc32aaac0 A longer kernel log is attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 6829 F pulseaudio /dev/snd/controlC0: michal 6829 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 08:54:14 2020 InstallationDate: Installed on 2019-11-19 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i2bkio@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_i2bkio ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-20 (1 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.sku: XPS 12-9Q33 dmi.product.version: A08
[Kernel-packages] [Bug 1860512] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1860512/+attachment/5328404/+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/1860512 Title: Suspend unreliable (possibly FUSE related) Status in linux package in Ubuntu: Confirmed Bug description: Since updating to Focal my laptop stopped suspending reliably. It will sit there either without display or with the desktop stuck for almost a minute before it goes back to work again. Looking at the kernel logs this seems to be related to a FUSE mount that I have running: sty 22 09:00:49 michal-laptop kernel: Call Trace: sty 22 09:00:49 michal-laptop kernel: __schedule+0x2e3/0x740 sty 22 09:00:49 michal-laptop kernel: schedule+0x42/0xb0 sty 22 09:00:49 michal-laptop kernel: request_wait_answer+0xa0/0x200 sty 22 09:00:49 michal-laptop kernel: ? wait_woken+0x80/0x80 sty 22 09:00:49 michal-laptop kernel: fuse_simple_request+0x177/0x260 sty 22 09:00:49 michal-laptop kernel: fuse_send_readpages.isra.0+0xea/0xf0 sty 22 09:00:49 michal-laptop kernel: fuse_readpages+0xbc/0x110 sty 22 09:00:49 michal-laptop kernel: read_pages+0x71/0x1a0 sty 22 09:00:49 michal-laptop kernel: __do_page_cache_readahead+0x180/0x1a0 sty 22 09:00:49 michal-laptop kernel: ondemand_readahead+0x192/0x2d0 sty 22 09:00:49 michal-laptop kernel: page_cache_sync_readahead+0x78/0xc0 sty 22 09:00:49 michal-laptop kernel: generic_file_buffered_read+0x571/0xc00 sty 22 09:00:49 michal-laptop kernel: ? ima_file_check+0x5a/0x80 sty 22 09:00:49 michal-laptop kernel: ? do_last+0x194/0x940 sty 22 09:00:49 michal-laptop kernel: generic_file_read_iter+0xdc/0x140 sty 22 09:00:49 michal-laptop kernel: fuse_file_read_iter+0x101/0x130 sty 22 09:00:49 michal-laptop kernel: ? do_filp_open+0xa5/0x100 sty 22 09:00:49 michal-laptop kernel: new_sync_read+0x122/0x1b0 sty 22 09:00:49 michal-laptop kernel: __vfs_read+0x29/0x40 sty 22 09:00:49 michal-laptop kernel: vfs_read+0xab/0x160 sty 22 09:00:49 michal-laptop kernel: ksys_read+0x67/0xe0 sty 22 09:00:49 michal-laptop kernel: __x64_sys_read+0x1a/0x20 sty 22 09:00:49 michal-laptop kernel: do_syscall_64+0x57/0x190 sty 22 09:00:49 michal-laptop kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 sty 22 09:00:49 michal-laptop kernel: RIP: 0033:0x7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: Code: Bad RIP value. sty 22 09:00:49 michal-laptop kernel: RSP: 002b:7f430bffda28 EFLAGS: 0246 ORIG_RAX: sty 22 09:00:49 michal-laptop kernel: RAX: ffda RBX: 492a RCX: 7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: RDX: 1000 RSI: 7f430bffda40 RDI: 0011 sty 22 09:00:49 michal-laptop kernel: RBP: 7f430bffda40 R08: R09: 7f430bffd9a8 sty 22 09:00:49 michal-laptop kernel: R10: R11: 0246 R12: 7f434670 sty 22 09:00:49 michal-laptop kernel: R13: 562dc32aaac0 R14: 0011 R15: 562dc32aaac0 A longer kernel log is attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 6829 F pulseaudio /dev/snd/controlC0: michal 6829 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 08:54:14 2020 InstallationDate: Installed on 2019-11-19 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i2bkio@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_i2bkio ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-20 (1 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.sku: XPS 12-9Q33 dmi.product.version: A08
[Kernel-packages] [Bug 1860512] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1860512/+attachment/5328401/+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/1860512 Title: Suspend unreliable (possibly FUSE related) Status in linux package in Ubuntu: Confirmed Bug description: Since updating to Focal my laptop stopped suspending reliably. It will sit there either without display or with the desktop stuck for almost a minute before it goes back to work again. Looking at the kernel logs this seems to be related to a FUSE mount that I have running: sty 22 09:00:49 michal-laptop kernel: Call Trace: sty 22 09:00:49 michal-laptop kernel: __schedule+0x2e3/0x740 sty 22 09:00:49 michal-laptop kernel: schedule+0x42/0xb0 sty 22 09:00:49 michal-laptop kernel: request_wait_answer+0xa0/0x200 sty 22 09:00:49 michal-laptop kernel: ? wait_woken+0x80/0x80 sty 22 09:00:49 michal-laptop kernel: fuse_simple_request+0x177/0x260 sty 22 09:00:49 michal-laptop kernel: fuse_send_readpages.isra.0+0xea/0xf0 sty 22 09:00:49 michal-laptop kernel: fuse_readpages+0xbc/0x110 sty 22 09:00:49 michal-laptop kernel: read_pages+0x71/0x1a0 sty 22 09:00:49 michal-laptop kernel: __do_page_cache_readahead+0x180/0x1a0 sty 22 09:00:49 michal-laptop kernel: ondemand_readahead+0x192/0x2d0 sty 22 09:00:49 michal-laptop kernel: page_cache_sync_readahead+0x78/0xc0 sty 22 09:00:49 michal-laptop kernel: generic_file_buffered_read+0x571/0xc00 sty 22 09:00:49 michal-laptop kernel: ? ima_file_check+0x5a/0x80 sty 22 09:00:49 michal-laptop kernel: ? do_last+0x194/0x940 sty 22 09:00:49 michal-laptop kernel: generic_file_read_iter+0xdc/0x140 sty 22 09:00:49 michal-laptop kernel: fuse_file_read_iter+0x101/0x130 sty 22 09:00:49 michal-laptop kernel: ? do_filp_open+0xa5/0x100 sty 22 09:00:49 michal-laptop kernel: new_sync_read+0x122/0x1b0 sty 22 09:00:49 michal-laptop kernel: __vfs_read+0x29/0x40 sty 22 09:00:49 michal-laptop kernel: vfs_read+0xab/0x160 sty 22 09:00:49 michal-laptop kernel: ksys_read+0x67/0xe0 sty 22 09:00:49 michal-laptop kernel: __x64_sys_read+0x1a/0x20 sty 22 09:00:49 michal-laptop kernel: do_syscall_64+0x57/0x190 sty 22 09:00:49 michal-laptop kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 sty 22 09:00:49 michal-laptop kernel: RIP: 0033:0x7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: Code: Bad RIP value. sty 22 09:00:49 michal-laptop kernel: RSP: 002b:7f430bffda28 EFLAGS: 0246 ORIG_RAX: sty 22 09:00:49 michal-laptop kernel: RAX: ffda RBX: 492a RCX: 7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: RDX: 1000 RSI: 7f430bffda40 RDI: 0011 sty 22 09:00:49 michal-laptop kernel: RBP: 7f430bffda40 R08: R09: 7f430bffd9a8 sty 22 09:00:49 michal-laptop kernel: R10: R11: 0246 R12: 7f434670 sty 22 09:00:49 michal-laptop kernel: R13: 562dc32aaac0 R14: 0011 R15: 562dc32aaac0 A longer kernel log is attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 6829 F pulseaudio /dev/snd/controlC0: michal 6829 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 08:54:14 2020 InstallationDate: Installed on 2019-11-19 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i2bkio@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_i2bkio ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-20 (1 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.sku: XPS 12-9Q33 dmi.product.version:
[Kernel-packages] [Bug 1860512] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1860512/+attachment/5328400/+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/1860512 Title: Suspend unreliable (possibly FUSE related) Status in linux package in Ubuntu: Confirmed Bug description: Since updating to Focal my laptop stopped suspending reliably. It will sit there either without display or with the desktop stuck for almost a minute before it goes back to work again. Looking at the kernel logs this seems to be related to a FUSE mount that I have running: sty 22 09:00:49 michal-laptop kernel: Call Trace: sty 22 09:00:49 michal-laptop kernel: __schedule+0x2e3/0x740 sty 22 09:00:49 michal-laptop kernel: schedule+0x42/0xb0 sty 22 09:00:49 michal-laptop kernel: request_wait_answer+0xa0/0x200 sty 22 09:00:49 michal-laptop kernel: ? wait_woken+0x80/0x80 sty 22 09:00:49 michal-laptop kernel: fuse_simple_request+0x177/0x260 sty 22 09:00:49 michal-laptop kernel: fuse_send_readpages.isra.0+0xea/0xf0 sty 22 09:00:49 michal-laptop kernel: fuse_readpages+0xbc/0x110 sty 22 09:00:49 michal-laptop kernel: read_pages+0x71/0x1a0 sty 22 09:00:49 michal-laptop kernel: __do_page_cache_readahead+0x180/0x1a0 sty 22 09:00:49 michal-laptop kernel: ondemand_readahead+0x192/0x2d0 sty 22 09:00:49 michal-laptop kernel: page_cache_sync_readahead+0x78/0xc0 sty 22 09:00:49 michal-laptop kernel: generic_file_buffered_read+0x571/0xc00 sty 22 09:00:49 michal-laptop kernel: ? ima_file_check+0x5a/0x80 sty 22 09:00:49 michal-laptop kernel: ? do_last+0x194/0x940 sty 22 09:00:49 michal-laptop kernel: generic_file_read_iter+0xdc/0x140 sty 22 09:00:49 michal-laptop kernel: fuse_file_read_iter+0x101/0x130 sty 22 09:00:49 michal-laptop kernel: ? do_filp_open+0xa5/0x100 sty 22 09:00:49 michal-laptop kernel: new_sync_read+0x122/0x1b0 sty 22 09:00:49 michal-laptop kernel: __vfs_read+0x29/0x40 sty 22 09:00:49 michal-laptop kernel: vfs_read+0xab/0x160 sty 22 09:00:49 michal-laptop kernel: ksys_read+0x67/0xe0 sty 22 09:00:49 michal-laptop kernel: __x64_sys_read+0x1a/0x20 sty 22 09:00:49 michal-laptop kernel: do_syscall_64+0x57/0x190 sty 22 09:00:49 michal-laptop kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 sty 22 09:00:49 michal-laptop kernel: RIP: 0033:0x7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: Code: Bad RIP value. sty 22 09:00:49 michal-laptop kernel: RSP: 002b:7f430bffda28 EFLAGS: 0246 ORIG_RAX: sty 22 09:00:49 michal-laptop kernel: RAX: ffda RBX: 492a RCX: 7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: RDX: 1000 RSI: 7f430bffda40 RDI: 0011 sty 22 09:00:49 michal-laptop kernel: RBP: 7f430bffda40 R08: R09: 7f430bffd9a8 sty 22 09:00:49 michal-laptop kernel: R10: R11: 0246 R12: 7f434670 sty 22 09:00:49 michal-laptop kernel: R13: 562dc32aaac0 R14: 0011 R15: 562dc32aaac0 A longer kernel log is attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 6829 F pulseaudio /dev/snd/controlC0: michal 6829 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 08:54:14 2020 InstallationDate: Installed on 2019-11-19 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i2bkio@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_i2bkio ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-20 (1 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.sku: XPS 12-9Q33
[Kernel-packages] [Bug 1860512] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1860512/+attachment/5328405/+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/1860512 Title: Suspend unreliable (possibly FUSE related) Status in linux package in Ubuntu: Confirmed Bug description: Since updating to Focal my laptop stopped suspending reliably. It will sit there either without display or with the desktop stuck for almost a minute before it goes back to work again. Looking at the kernel logs this seems to be related to a FUSE mount that I have running: sty 22 09:00:49 michal-laptop kernel: Call Trace: sty 22 09:00:49 michal-laptop kernel: __schedule+0x2e3/0x740 sty 22 09:00:49 michal-laptop kernel: schedule+0x42/0xb0 sty 22 09:00:49 michal-laptop kernel: request_wait_answer+0xa0/0x200 sty 22 09:00:49 michal-laptop kernel: ? wait_woken+0x80/0x80 sty 22 09:00:49 michal-laptop kernel: fuse_simple_request+0x177/0x260 sty 22 09:00:49 michal-laptop kernel: fuse_send_readpages.isra.0+0xea/0xf0 sty 22 09:00:49 michal-laptop kernel: fuse_readpages+0xbc/0x110 sty 22 09:00:49 michal-laptop kernel: read_pages+0x71/0x1a0 sty 22 09:00:49 michal-laptop kernel: __do_page_cache_readahead+0x180/0x1a0 sty 22 09:00:49 michal-laptop kernel: ondemand_readahead+0x192/0x2d0 sty 22 09:00:49 michal-laptop kernel: page_cache_sync_readahead+0x78/0xc0 sty 22 09:00:49 michal-laptop kernel: generic_file_buffered_read+0x571/0xc00 sty 22 09:00:49 michal-laptop kernel: ? ima_file_check+0x5a/0x80 sty 22 09:00:49 michal-laptop kernel: ? do_last+0x194/0x940 sty 22 09:00:49 michal-laptop kernel: generic_file_read_iter+0xdc/0x140 sty 22 09:00:49 michal-laptop kernel: fuse_file_read_iter+0x101/0x130 sty 22 09:00:49 michal-laptop kernel: ? do_filp_open+0xa5/0x100 sty 22 09:00:49 michal-laptop kernel: new_sync_read+0x122/0x1b0 sty 22 09:00:49 michal-laptop kernel: __vfs_read+0x29/0x40 sty 22 09:00:49 michal-laptop kernel: vfs_read+0xab/0x160 sty 22 09:00:49 michal-laptop kernel: ksys_read+0x67/0xe0 sty 22 09:00:49 michal-laptop kernel: __x64_sys_read+0x1a/0x20 sty 22 09:00:49 michal-laptop kernel: do_syscall_64+0x57/0x190 sty 22 09:00:49 michal-laptop kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 sty 22 09:00:49 michal-laptop kernel: RIP: 0033:0x7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: Code: Bad RIP value. sty 22 09:00:49 michal-laptop kernel: RSP: 002b:7f430bffda28 EFLAGS: 0246 ORIG_RAX: sty 22 09:00:49 michal-laptop kernel: RAX: ffda RBX: 492a RCX: 7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: RDX: 1000 RSI: 7f430bffda40 RDI: 0011 sty 22 09:00:49 michal-laptop kernel: RBP: 7f430bffda40 R08: R09: 7f430bffd9a8 sty 22 09:00:49 michal-laptop kernel: R10: R11: 0246 R12: 7f434670 sty 22 09:00:49 michal-laptop kernel: R13: 562dc32aaac0 R14: 0011 R15: 562dc32aaac0 A longer kernel log is attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 6829 F pulseaudio /dev/snd/controlC0: michal 6829 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 08:54:14 2020 InstallationDate: Installed on 2019-11-19 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i2bkio@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_i2bkio ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-20 (1 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.sku: XPS 12-9Q33 dmi.product.version: A08
[Kernel-packages] [Bug 1860512] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1860512/+attachment/5328403/+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/1860512 Title: Suspend unreliable (possibly FUSE related) Status in linux package in Ubuntu: Confirmed Bug description: Since updating to Focal my laptop stopped suspending reliably. It will sit there either without display or with the desktop stuck for almost a minute before it goes back to work again. Looking at the kernel logs this seems to be related to a FUSE mount that I have running: sty 22 09:00:49 michal-laptop kernel: Call Trace: sty 22 09:00:49 michal-laptop kernel: __schedule+0x2e3/0x740 sty 22 09:00:49 michal-laptop kernel: schedule+0x42/0xb0 sty 22 09:00:49 michal-laptop kernel: request_wait_answer+0xa0/0x200 sty 22 09:00:49 michal-laptop kernel: ? wait_woken+0x80/0x80 sty 22 09:00:49 michal-laptop kernel: fuse_simple_request+0x177/0x260 sty 22 09:00:49 michal-laptop kernel: fuse_send_readpages.isra.0+0xea/0xf0 sty 22 09:00:49 michal-laptop kernel: fuse_readpages+0xbc/0x110 sty 22 09:00:49 michal-laptop kernel: read_pages+0x71/0x1a0 sty 22 09:00:49 michal-laptop kernel: __do_page_cache_readahead+0x180/0x1a0 sty 22 09:00:49 michal-laptop kernel: ondemand_readahead+0x192/0x2d0 sty 22 09:00:49 michal-laptop kernel: page_cache_sync_readahead+0x78/0xc0 sty 22 09:00:49 michal-laptop kernel: generic_file_buffered_read+0x571/0xc00 sty 22 09:00:49 michal-laptop kernel: ? ima_file_check+0x5a/0x80 sty 22 09:00:49 michal-laptop kernel: ? do_last+0x194/0x940 sty 22 09:00:49 michal-laptop kernel: generic_file_read_iter+0xdc/0x140 sty 22 09:00:49 michal-laptop kernel: fuse_file_read_iter+0x101/0x130 sty 22 09:00:49 michal-laptop kernel: ? do_filp_open+0xa5/0x100 sty 22 09:00:49 michal-laptop kernel: new_sync_read+0x122/0x1b0 sty 22 09:00:49 michal-laptop kernel: __vfs_read+0x29/0x40 sty 22 09:00:49 michal-laptop kernel: vfs_read+0xab/0x160 sty 22 09:00:49 michal-laptop kernel: ksys_read+0x67/0xe0 sty 22 09:00:49 michal-laptop kernel: __x64_sys_read+0x1a/0x20 sty 22 09:00:49 michal-laptop kernel: do_syscall_64+0x57/0x190 sty 22 09:00:49 michal-laptop kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 sty 22 09:00:49 michal-laptop kernel: RIP: 0033:0x7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: Code: Bad RIP value. sty 22 09:00:49 michal-laptop kernel: RSP: 002b:7f430bffda28 EFLAGS: 0246 ORIG_RAX: sty 22 09:00:49 michal-laptop kernel: RAX: ffda RBX: 492a RCX: 7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: RDX: 1000 RSI: 7f430bffda40 RDI: 0011 sty 22 09:00:49 michal-laptop kernel: RBP: 7f430bffda40 R08: R09: 7f430bffd9a8 sty 22 09:00:49 michal-laptop kernel: R10: R11: 0246 R12: 7f434670 sty 22 09:00:49 michal-laptop kernel: R13: 562dc32aaac0 R14: 0011 R15: 562dc32aaac0 A longer kernel log is attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 6829 F pulseaudio /dev/snd/controlC0: michal 6829 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 08:54:14 2020 InstallationDate: Installed on 2019-11-19 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i2bkio@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_i2bkio ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-20 (1 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.sku: XPS 12-9Q33 dmi.product.version: A08
[Kernel-packages] [Bug 1860512] [NEW] Suspend unreliable (possibly FUSE related)
Public bug reported: Since updating to Focal my laptop stopped suspending reliably. It will sit there either without display or with the desktop stuck for almost a minute before it goes back to work again. Looking at the kernel logs this seems to be related to a FUSE mount that I have running: sty 22 09:00:49 michal-laptop kernel: Call Trace: sty 22 09:00:49 michal-laptop kernel: __schedule+0x2e3/0x740 sty 22 09:00:49 michal-laptop kernel: schedule+0x42/0xb0 sty 22 09:00:49 michal-laptop kernel: request_wait_answer+0xa0/0x200 sty 22 09:00:49 michal-laptop kernel: ? wait_woken+0x80/0x80 sty 22 09:00:49 michal-laptop kernel: fuse_simple_request+0x177/0x260 sty 22 09:00:49 michal-laptop kernel: fuse_send_readpages.isra.0+0xea/0xf0 sty 22 09:00:49 michal-laptop kernel: fuse_readpages+0xbc/0x110 sty 22 09:00:49 michal-laptop kernel: read_pages+0x71/0x1a0 sty 22 09:00:49 michal-laptop kernel: __do_page_cache_readahead+0x180/0x1a0 sty 22 09:00:49 michal-laptop kernel: ondemand_readahead+0x192/0x2d0 sty 22 09:00:49 michal-laptop kernel: page_cache_sync_readahead+0x78/0xc0 sty 22 09:00:49 michal-laptop kernel: generic_file_buffered_read+0x571/0xc00 sty 22 09:00:49 michal-laptop kernel: ? ima_file_check+0x5a/0x80 sty 22 09:00:49 michal-laptop kernel: ? do_last+0x194/0x940 sty 22 09:00:49 michal-laptop kernel: generic_file_read_iter+0xdc/0x140 sty 22 09:00:49 michal-laptop kernel: fuse_file_read_iter+0x101/0x130 sty 22 09:00:49 michal-laptop kernel: ? do_filp_open+0xa5/0x100 sty 22 09:00:49 michal-laptop kernel: new_sync_read+0x122/0x1b0 sty 22 09:00:49 michal-laptop kernel: __vfs_read+0x29/0x40 sty 22 09:00:49 michal-laptop kernel: vfs_read+0xab/0x160 sty 22 09:00:49 michal-laptop kernel: ksys_read+0x67/0xe0 sty 22 09:00:49 michal-laptop kernel: __x64_sys_read+0x1a/0x20 sty 22 09:00:49 michal-laptop kernel: do_syscall_64+0x57/0x190 sty 22 09:00:49 michal-laptop kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 sty 22 09:00:49 michal-laptop kernel: RIP: 0033:0x7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: Code: Bad RIP value. sty 22 09:00:49 michal-laptop kernel: RSP: 002b:7f430bffda28 EFLAGS: 0246 ORIG_RAX: sty 22 09:00:49 michal-laptop kernel: RAX: ffda RBX: 492a RCX: 7f432f9e4b1d sty 22 09:00:49 michal-laptop kernel: RDX: 1000 RSI: 7f430bffda40 RDI: 0011 sty 22 09:00:49 michal-laptop kernel: RBP: 7f430bffda40 R08: R09: 7f430bffd9a8 sty 22 09:00:49 michal-laptop kernel: R10: R11: 0246 R12: 7f434670 sty 22 09:00:49 michal-laptop kernel: R13: 562dc32aaac0 R14: 0011 R15: 562dc32aaac0 A longer kernel log is attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 6829 F pulseaudio /dev/snd/controlC0: michal 6829 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 08:54:14 2020 InstallationDate: Installed on 2019-11-19 (63 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i2bkio@/vmlinuz-5.4.0-9-generic root=ZFS=rpool/ROOT/ubuntu_i2bkio ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-20 (1 days ago) dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.sku: XPS 12-9Q33 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug champagne focal ** Attachment added: "kernel.log" https://bugs.launchpad.net/bugs/1860512/+attachment/5322102/+files/kernel.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860512 Title: Suspend unreliable (possibly FUSE related) Status in linux package in Ubuntu: New Bug description: Since updating to Focal my laptop
[Kernel-packages] [Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
Hey all, will we get backports of this to previous releases? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: Make linux-kvm bootable in LXD VMs Status in cloud-images: Invalid Status in linux-kvm package in Ubuntu: Triaged Status in linux-kvm source package in Focal: Fix Released Bug description: The `disk-kvm.img` images which are to be preferred when run under virtualization, currently completely fail to boot under UEFI. A workaround was put in place such that LXD instead will pull generic- based images until this is resolved, this however does come with a much longer boot time (as the kernel panics, reboots and then boots) and also reduced functionality from cloud-init, so we'd still like this fixed in the near future. To get things behaving, it looks like we need the following config options to be enable in linux-kvm: - CONFIG_EFI_STUB - CONFIG_VSOCKETS - CONFIG_VIRTIO_VSOCKETS - CONFIG_VIRTIO_VSOCKETS_COMMON == Rationale == We'd like to be able to use the linux-kvm based images for LXD, those will directly boot without needing the panic+reboot behavior of generic images and will be much lighter in general. We also need the LXD agent to work, which requires functional virtio vsock. == Test case == - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809 - lxc launch bug1873809 v1 - lxc console v1 - - - lxc exec v1 bash To validate a new kernel, you'll need to manually repack the .img file and install the new kernel in there. == Regression potential == I don't know who else is using those kvm images right now, but those changes will cause a change to the kernel binary such that it contains the EFI stub bits + a signature. This could cause some (horribly broken) systems to no longer be able to boot that kernel. Though considering that such a setup is common to our other kernels, this seems unlikely. Also, this will be introducing virtio vsock support which again, could maybe confused some horribly broken systems? In either case, the kernel conveniently is the only package which ships multiple versions concurently, so rebooting on the previous kernel is always an option, mitigating some of the risks. -- Details from original report -- User report on the LXD side: https://github.com/lxc/lxd/issues/7224 I've reproduced this issue with: - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda focal-server-cloudimg-amd64-disk-kvm.img -m 1G On the graphical console, you'll see EDK2 load (TianoCore) followed by basic boot messages and then a message from grub (error: can't find command `hwmatch`). Those also appear on successful boots of other images so I don't think there's anything concerning that. However it'll hang indefinitely and eat up all your CPU. Switching to the text console view (serial0), you'll see the same issue as that LXD report: BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) error: can't find command `hwmatch'. e X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - ExceptionData - RIP - 3FF2DA12, CS - 0038, RFLAGS - 00200202 RAX - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF RBX - 0398, RSP - 3FF1C638, RBP - 3FF34360 RSI - 3FF343B8, RDI - 1000 R8 - 3E80F108, R9 - 3E815B98, R10 - 0065 R11 - 2501, R12 - 0004, R13 - 3E80F100 R14 - , R15 - DS - 0030, ES - 0030, FS - 0030 GS - 0030, SS - 0030 CR0 - 80010033, CR2 - , CR3 - 3FC01000 CR4 - 0668, CR8 - DR0 - , DR1 - , DR2 - DR3 - , DR6 - 0FF0, DR7 - 0400 GDTR - 3FBEEA98 0047, LDTR - IDTR - 3F2D8018 0FFF, TR - FXSAVE_STATE - 3FF1C290 Find image based on
[Kernel-packages] [Bug 1964471] Re: 5.13.0-36 fails to boot on Parallels on Mac M1 eg aarch64
We can confirm the same through Multipass on QEMU rather than Parallels. We found that using a different version of QEMU does help, we're trying to narrow it down to a QEMU commit now. There are a number of changes that can be seen in the recent kernel pertaining to aarch64: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/impish/log/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964471 Title: 5.13.0-36 fails to boot on Parallels on Mac M1 eg aarch64 Status in linux package in Ubuntu: Confirmed Bug description: After allowing an Ubuntu Impish system running under Parallels Desktop on M1 Mac (aarch64) to update, and rebooting for a new kernel it gets stuck after loading kernel and ramdisk, no further output on 5.13.0-36 Reverting to 5.13.0-20 by selecting it at the grub screen allows the system to boot as normal. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: moon1272538 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 10 11:42:47 2022 InstallationDate: Installed on 2021-02-18 (385 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release arm64 (20210218) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci-vt: -[:00]-+-01.0 Intel Corporation 82801I (ICH9 Family) HD Audio Controller +-02.0 Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller +-03.0 NEC Corporation uPD720200 USB 3.0 Host Controller +-09.0 Parallels, Inc. Virtual Machine Communication Interface \-0a.0 Red Hat, Inc. Virtio GPU MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-19 (142 days ago) acpidump: dmi.bios.date: Wed, 24 Nov 2021 19:24:24 dmi.bios.release: 0.1 dmi.bios.vendor: Parallels International GmbH. dmi.bios.version: 17.1.1 (51537) dmi.board.asset.tag: None dmi.board.name: Parallels ARM Virtual Platform dmi.board.vendor: Parallels ARM Virtual Machine dmi.board.version: 0.1 dmi.chassis.type: 2 dmi.chassis.vendor: Parallels International GmbH. dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr17.1.1(51537):bdWed,24Nov2021192424:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:skuParallels_ARM_VM:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr: dmi.product.family: Parallels VM dmi.product.name: Parallels ARM Virtual Machine dmi.product.sku: Parallels_ARM_VM dmi.product.version: 0.1 dmi.sys.vendor: Parallels International GmbH. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964471/+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 1964471] Re: 5.13.0-36 fails to boot on Parallels on Mac M1 eg aarch64
And this is the kernel side trigger for the issue: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/impish/commit/?id=7936f2a576f1d7c3e1a80f8a07a217cdfa2b7338 -- 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/1964471 Title: 5.13.0-36 fails to boot on Parallels on Mac M1 eg aarch64 Status in linux package in Ubuntu: Confirmed Bug description: After allowing an Ubuntu Impish system running under Parallels Desktop on M1 Mac (aarch64) to update, and rebooting for a new kernel it gets stuck after loading kernel and ramdisk, no further output on 5.13.0-36 Reverting to 5.13.0-20 by selecting it at the grub screen allows the system to boot as normal. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: moon1272538 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 10 11:42:47 2022 InstallationDate: Installed on 2021-02-18 (385 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release arm64 (20210218) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci-vt: -[:00]-+-01.0 Intel Corporation 82801I (ICH9 Family) HD Audio Controller +-02.0 Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller +-03.0 NEC Corporation uPD720200 USB 3.0 Host Controller +-09.0 Parallels, Inc. Virtual Machine Communication Interface \-0a.0 Red Hat, Inc. Virtio GPU MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-19 (142 days ago) acpidump: dmi.bios.date: Wed, 24 Nov 2021 19:24:24 dmi.bios.release: 0.1 dmi.bios.vendor: Parallels International GmbH. dmi.bios.version: 17.1.1 (51537) dmi.board.asset.tag: None dmi.board.name: Parallels ARM Virtual Platform dmi.board.vendor: Parallels ARM Virtual Machine dmi.board.version: 0.1 dmi.chassis.type: 2 dmi.chassis.vendor: Parallels International GmbH. dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr17.1.1(51537):bdWed,24Nov2021192424:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:skuParallels_ARM_VM:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr: dmi.product.family: Parallels VM dmi.product.name: Parallels ARM Virtual Machine dmi.product.sku: Parallels_ARM_VM dmi.product.version: 0.1 dmi.sys.vendor: Parallels International GmbH. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964471/+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 1964471] Re: 5.13.0-36 fails to boot on Parallels on Mac M1 eg aarch64
For reference, this is what fixes it on QEMU: https://github.com/qemu/qemu/compare/48006e0...7f6c295 I doubt this is a reason to do anything to the Ubuntu kernel, then. Filing a bug with Parallels referencing that may be good. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964471 Title: 5.13.0-36 fails to boot on Parallels on Mac M1 eg aarch64 Status in linux package in Ubuntu: Confirmed Bug description: After allowing an Ubuntu Impish system running under Parallels Desktop on M1 Mac (aarch64) to update, and rebooting for a new kernel it gets stuck after loading kernel and ramdisk, no further output on 5.13.0-36 Reverting to 5.13.0-20 by selecting it at the grub screen allows the system to boot as normal. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: moon1272538 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 10 11:42:47 2022 InstallationDate: Installed on 2021-02-18 (385 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release arm64 (20210218) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci-vt: -[:00]-+-01.0 Intel Corporation 82801I (ICH9 Family) HD Audio Controller +-02.0 Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller +-03.0 NEC Corporation uPD720200 USB 3.0 Host Controller +-09.0 Parallels, Inc. Virtual Machine Communication Interface \-0a.0 Red Hat, Inc. Virtio GPU MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-19 (142 days ago) acpidump: dmi.bios.date: Wed, 24 Nov 2021 19:24:24 dmi.bios.release: 0.1 dmi.bios.vendor: Parallels International GmbH. dmi.bios.version: 17.1.1 (51537) dmi.board.asset.tag: None dmi.board.name: Parallels ARM Virtual Platform dmi.board.vendor: Parallels ARM Virtual Machine dmi.board.version: 0.1 dmi.chassis.type: 2 dmi.chassis.vendor: Parallels International GmbH. dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr17.1.1(51537):bdWed,24Nov2021192424:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:skuParallels_ARM_VM:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr: dmi.product.family: Parallels VM dmi.product.name: Parallels ARM Virtual Machine dmi.product.sku: Parallels_ARM_VM dmi.product.version: 0.1 dmi.sys.vendor: Parallels International GmbH. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964471/+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 1975840] [NEW] WiFi not roaming to a much stronger/faster AP
Public bug reported: I have spotty WiFi reception around the house, and I've noticed that once I roam to a 2.4GHz because I've moved out of range, coming back I'm stuck at it with very low signal despite there being much more powerful and faster BSSIDs around. `nmcli d wifi` reports: $ nmcli d wifi IN-USE BSSID SSID MODE CHAN RATESIGNAL BARS SECURITY 74:83:C2:19:7E:BA wifi Infra 1 130 Mbit/s 82 ▂▄▆█ WPA2 * 74:83:C2:19:7E:BB wifi Infra 44540 Mbit/s 55 ▂▄__ WPA2 4C:E6:76:F9:5E:AF wifi Infra 52130 Mbit/s 39 ▂▄__ WPA2 If I didn't reconnect, I'd be stuck on the 4C: BSSID still. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-33-generic 5.15.0-33.34 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michal 6270 F pulseaudio /dev/snd/controlC1: michal 6270 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 26 17:12:34 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2022-04-29 (27 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_6u8k7k@/vmlinuz-5.15.0-33-generic root=ZFS=rpool/ROOT/ubuntu_6u8k7k ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2015 dmi.bios.release: 0.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.ec.firmware.release: 0.8 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:br0.8:efr0.8:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:skuXPS12-9Q33: dmi.product.name: XPS 12-9Q33 dmi.product.sku: XPS 12-9Q33 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy wayland-session -- 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/1975840 Title: WiFi not roaming to a much stronger/faster AP Status in linux package in Ubuntu: Confirmed Bug description: I have spotty WiFi reception around the house, and I've noticed that once I roam to a 2.4GHz because I've moved out of range, coming back I'm stuck at it with very low signal despite there being much more powerful and faster BSSIDs around. `nmcli d wifi` reports: $ nmcli d wifi IN-USE BSSID SSID MODE CHAN RATESIGNAL BARS SECURITY 74:83:C2:19:7E:BA wifi Infra 1 130 Mbit/s 82 ▂▄▆█ WPA2 * 74:83:C2:19:7E:BB wifi Infra 44540 Mbit/s 55 ▂▄__ WPA2 4C:E6:76:F9:5E:AF wifi Infra 52130 Mbit/s 39 ▂▄__ WPA2 If I didn't reconnect, I'd be stuck on the 4C: BSSID still. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-33-generic 5.15.0-33.34 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michal 6270 F pulseaudio /dev/snd/controlC1: michal 6270 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 26 17:12:34 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2022-04-29 (27 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_6u8k7k@/vmlinuz-5.15.0-33-generic root=ZFS=rpool/ROOT/ubuntu_6u8k7k ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A
[Kernel-packages] [Bug 1988989] [NEW] HDMI over USB-C unstable since kernel 5.19 on Intel 12th Gen.
Public bug reported: Having upgraded to 5.19.0-15, my display connected over a USB-C → HDMI connection goes off and on multiple times a minute, rendering it unusable. Downgrading back to 5.15.0-27 makes it work again. I've bisected mainline kernels from https://kernel.ubuntu.com/~kernel- ppa/mainline/ to reach: v5.18.19 GOOD v5.19-rc3 BAD ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 7948 F wireplumber /dev/snd/controlC0: michal 7948 F wireplumber /dev/snd/seq:michal 7939 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 7 14:28:48 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2022-08-31 (6 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) MachineType: Framework Laptop (12th Gen Intel Core) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_zw6n2j@/vmlinuz-5.19.0-15-generic root=ZFS=rpool/ROOT/ubuntu_zw6n2j ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220831.gitd3c92280-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA42321000N dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- 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/1988989 Title: HDMI over USB-C unstable since kernel 5.19 on Intel 12th Gen. Status in linux package in Ubuntu: New Bug description: Having upgraded to 5.19.0-15, my display connected over a USB-C → HDMI connection goes off and on multiple times a minute, rendering it unusable. Downgrading back to 5.15.0-27 makes it work again. I've bisected mainline kernels from https://kernel.ubuntu.com/~kernel- ppa/mainline/ to reach: v5.18.19 GOOD v5.19-rc3 BAD ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 7948 F wireplumber /dev/snd/controlC0: michal 7948 F wireplumber /dev/snd/seq:michal 7939 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 7 14:28:48 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2022-08-31 (6 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) MachineType: Framework Laptop (12th Gen Intel Core) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_zw6n2j@/vmlinuz-5.19.0-15-generic root=ZFS=rpool/ROOT/ubuntu_zw6n2j ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220831.gitd3c92280-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04
[Kernel-packages] [Bug 1975840] Re: WiFi not roaming to a much stronger/faster AP
** Also affects: wpasupplicant (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975840 Title: WiFi not roaming to a much stronger/faster AP Status in linux package in Ubuntu: Confirmed Status in wpasupplicant package in Ubuntu: New Bug description: I have spotty WiFi reception around the house, and I've noticed that once I roam to a 2.4GHz because I've moved out of range, coming back I'm stuck at it with very low signal despite there being much more powerful and faster BSSIDs around. `nmcli d wifi` reports: $ nmcli d wifi IN-USE BSSID SSID MODE CHAN RATESIGNAL BARS SECURITY 74:83:C2:19:7E:BA wifi Infra 1 130 Mbit/s 82 ▂▄▆█ WPA2 * 74:83:C2:19:7E:BB wifi Infra 44540 Mbit/s 55 ▂▄__ WPA2 4C:E6:76:F9:5E:AF wifi Infra 52130 Mbit/s 39 ▂▄__ WPA2 If I didn't reconnect, I'd be stuck on the 4C: BSSID still. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-33-generic 5.15.0-33.34 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michal 6270 F pulseaudio /dev/snd/controlC1: michal 6270 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 26 17:12:34 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2022-04-29 (27 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_6u8k7k@/vmlinuz-5.15.0-33-generic root=ZFS=rpool/ROOT/ubuntu_6u8k7k ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2015 dmi.bios.release: 0.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.ec.firmware.release: 0.8 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:br0.8:efr0.8:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:skuXPS12-9Q33: dmi.product.name: XPS 12-9Q33 dmi.product.sku: XPS 12-9Q33 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975840/+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 1988989] Re: HDMI/DisplayPort over USB-C unstable since kernel 5.19 on Intel 12th Gen.
> Kernel 6.0 seems to have fixed it for me: > https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.0/amd64/ Not here, still 5.15 is the newest kernel that doesn't put the external screen into a frenzy. -- 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/1988989 Title: HDMI/DisplayPort over USB-C unstable since kernel 5.19 on Intel 12th Gen. Status in linux package in Ubuntu: Confirmed Bug description: Having upgraded to 5.19.0-15, my display connected over a USB-C → HDMI connection goes off and on multiple times a minute, rendering it unusable. Downgrading back to 5.15.0-27 makes it work again. I've bisected mainline kernels from https://kernel.ubuntu.com/~kernel- ppa/mainline/ to reach: v5.18.19 GOOD v5.19-rc3 BAD ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 7948 F wireplumber /dev/snd/controlC0: michal 7948 F wireplumber /dev/snd/seq:michal 7939 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 7 14:28:48 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2022-08-31 (6 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) MachineType: Framework Laptop (12th Gen Intel Core) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_zw6n2j@/vmlinuz-5.19.0-15-generic root=ZFS=rpool/ROOT/ubuntu_zw6n2j ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220831.gitd3c92280-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA42321000N dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988989/+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 1988989] Re: HDMI over USB-C unstable since kernel 5.19 on Intel 12th Gen.
Oh man. This turned out to be a hardware issue. A replacement adapter works fine. I'd never have thought, when the kernel changed so much. I'm on 5.19 now, didn't see a glitch yet, where I'd normally couldn't work. Phew. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988989 Title: HDMI over USB-C unstable since kernel 5.19 on Intel 12th Gen. Status in linux package in Ubuntu: Invalid Bug description: Having upgraded to 5.19.0-15, my display connected over a USB-C → HDMI connection goes off and on multiple times a minute, rendering it unusable. Downgrading back to 5.15.0-27 makes it work again. I've bisected mainline kernels from https://kernel.ubuntu.com/~kernel- ppa/mainline/ to reach: v5.18.19 GOOD v5.19-rc3 BAD ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michal 7948 F wireplumber /dev/snd/controlC0: michal 7948 F wireplumber /dev/snd/seq:michal 7939 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 7 14:28:48 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2022-08-31 (6 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) MachineType: Framework Laptop (12th Gen Intel Core) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_zw6n2j@/vmlinuz-5.19.0-15-generic root=ZFS=rpool/ROOT/ubuntu_zw6n2j ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220831.gitd3c92280-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2022 dmi.bios.release: 3.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.04 dmi.board.asset.tag: * dmi.board.name: FRANMACP04 dmi.board.vendor: Framework dmi.board.version: A4 dmi.chassis.asset.tag: FRANDACPA42321000N dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A4 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd07/15/2022:br3.4:svnFramework:pnLaptop(12thGenIntelCore):pvrA4:rvnFramework:rnFRANMACP04:rvrA4:cvnFramework:ct10:cvrA4:skuFRANDACP04: dmi.product.family: 13in Laptop dmi.product.name: Laptop (12th Gen Intel Core) dmi.product.sku: FRANDACP04 dmi.product.version: A4 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988989/+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
