[Kernel-packages] [Bug 1776879] Re: system hangs on boot at "Cryptography Setup for cryptswap1"
ok, strange! Now I have booted the 4.4.0-128-generic kernel. And now the system booted! But in the syslog I also have the above message. ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776879/+attachment/5152879/+files/syslog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776879 Title: system hangs on boot at "Cryptography Setup for cryptswap1" Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Hi, I have updated my kubuntu from 4.4.0-127-generic to 4.4.0-128-generic. When I try to boot with the new kernel, the system hangs during the Flash-Screen. When I try booting in recovery mode, I can see, that the boot hangs with the following message: Dependency failed for Cryptography Setup for cryptswap1 Dependency failed for Encrypted Volumes Dependency failed for dev-mapper-cryptswap1.device Dependency failed for /dev/mapper/cryptswap1 Dependency failed for Swap Dependency failed for /dev/disk/by-uuid/fea3e83b-933d-49fc-a3d0-88448a0b7871 When I boot with the old kernel everything works fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leon 2229 F pulseaudio /dev/snd/controlC0: leon 2229 F pulseaudio CurrentDesktop: KDE Date: Thu Jun 14 11:57:45 2018 EcryptfsInUse: Yes HibernationDevice: #RESUME=/dev/sda5 #RESUME=UUID="4eeadd76-5400-4026-994f-7a27deaf56d2" RESUME=UUID="fea3e83b-933d-49fc-a3d0-88448a0b7871" InstallationDate: Installed on 2016-01-25 (870 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) MachineType: Acer Aspire V3-371 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic root=UUID=f42e701d-6b34-4d69-b115-e5c9b6c2fed6 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware 1.157.19 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V3-371 dmi.board.vendor: Acer dmi.board.version: V1.28 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/21/2015:svnAcer:pnAspireV3-371:pvrV1.28:rvnAcer:rnAspireV3-371:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.name: Aspire V3-371 dmi.product.version: V1.28 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776879/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776819] Re: linux: 3.13.0-153.203 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776819 Title: linux: 3.13.0-153.203 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1776820 (linux-lts-trusty) derivatives: kernel-stable-phase-changed:Thursday, 14. June 2018 09:02 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
*** This bug is a duplicate of bug 1773897 *** https://bugs.launchpad.net/bugs/1773897 That might be premature. Bug 1773897 regressed in 17.10, not 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 :
[Kernel-packages] [Bug 1776819] Re: linux: 3.13.0-153.203 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776819 Title: linux: 3.13.0-153.203 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1776820 (linux-lts-trusty) derivatives: kernel-stable-phase-changed:Thursday, 14. June 2018 09:02 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1776819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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: Unknown 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 1777038] Re: msgstress04 test in ubuntu_ltp_syscalls will hang on GCP 4.15
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1777038 Title: msgstress04 test in ubuntu_ltp_syscalls will hang on GCP 4.15 Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: The msgstress04 will timed out for the GCP kernel. (another one failed with nanosleep01) Need to check if this is caused by the insufficient timeout threshold 12:18:00 DEBUG| [stdout] <<>> 12:18:00 DEBUG| [stdout] tag=msgstress04 stime=1528978680 12:18:00 DEBUG| [stdout] cmdline="msgstress04" 12:18:00 DEBUG| [stdout] contacts="" 12:18:00 DEBUG| [stdout] analysis=exit 12:18:00 DEBUG| [stdout] <<>> 12:18:00 DEBUG| [stdout] msgctl110 TINFO : Found 31851 available message queues 12:18:00 DEBUG| [stdout] msgctl110 TINFO : Using upto 15467 pids 12:35:02 INFO | Timer expired (2400 sec.), nuking pid 2737 syslog: Jun 14 12:14:53 b-lgcp-gcp-4-15-0-n1-highcpu-64-ltp-syscalls kernel: [ 1341.360648] LTP: starting msgctl07 Jun 14 12:15:13 b-lgcp-gcp-4-15-0-n1-highcpu-64-ltp-syscalls kernel: [ 1361.390202] LTP: starting msgstress01 Jun 14 12:15:16 b-lgcp-gcp-4-15-0-n1-highcpu-64-ltp-syscalls kernel: [ 1364.001571] LTP: starting msgstress02 Jun 14 12:15:16 b-lgcp-gcp-4-15-0-n1-highcpu-64-ltp-syscalls kernel: [ 1364.409053] LTP: starting msgstress03 Jun 14 12:17:01 b-lgcp-gcp-4-15-0-n1-highcpu-64-ltp-syscalls CRON[12969]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jun 14 12:17:58 b-lgcp-gcp-4-15-0-n1-highcpu-64-ltp-syscalls kernel: [ 1526.131580] cgroup: fork rejected by pids controller in /user.slice/user-1005.slice/session-19.scope Jun 14 12:18:00 b-lgcp-gcp-4-15-0-n1-highcpu-64-ltp-syscalls kernel: [ 1527.710081] LTP: starting msgstress04 Jun 14 13:17:01 b-lgcp-gcp-4-15-0-n1-highcpu-64-ltp-syscalls CRON[15005]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1010-gcp 4.15.0-1010.10 ProcVersionSignature: Ubuntu 4.15.0-1010.10-gcp 4.15.18 Uname: Linux 4.15.0-1010-gcp x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Fri Jun 15 02:59:31 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-gcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1777038/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
*** 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 1777063] Re: Xenial update to 4.4.137 stable release
** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The 4.4.137 upstream stable + patch set is now available. It should be included in the Ubuntu + kernel as well. - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The 4.4.137 upstream stable -patch set is now available. It should be included in the Ubuntu -kernel as well. + git://git.kernel.org/ -git://git.kernel.org/ + TEST CASE: TBD - TEST CASE: TBD + The following patches from the 4.4.137 stable release shall be + applied: -The following patches from the 4.4.137 stable release shall be - applied: + * Linux 4.4.137 + * net: metrics: add proper netlink validation + * net: phy: broadcom: Fix bcm_write_exp() + * rtnetlink: validate attributes in do_setlink() + * team: use netdev_features_t instead of u32 + * net/mlx4: Fix irq-unsafe spinlock usage + * qed: Fix mask for physical address in ILT entry + * packet: fix reserve calculation + * net: usb: cdc_mbim: add flag FLAG_SEND_ZLP + * net/packet: refine check for priv area size + * netdev-FAQ: clarify DaveM's position for stable backports + * isdn: eicon: fix a missing-check bug + * ipv4: remove warning in ip_recv_error + * ip6mr: only set ip6mr_table from setsockopt when ip6mr_new_table succeeds + * enic: set DMA mask to 47 bit + * dccp: don't free ccid2_hc_tx_sock struct in dccp_disconnect() + * bnx2x: use the right constant + * brcmfmac: Fix check for ISO3166 code + * drm: set FMODE_UNSIGNED_OFFSET for drm files + * xfs: fix incorrect log_flushed on fsync + * kconfig: Avoid format overflow warning from GCC 8.1 + * mmap: relax file size limit for regular files + * mmap: introduce sane default mmap limits + * tpm: self test failure should not cause suspend to fail + * tpm: do not suspend/resume if power stays on -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777063 Title: Xenial update to 4.4.137 stable release Status in linux package in Ubuntu: Invalid Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.137 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.137 stable release shall be applied: * Linux 4.4.137 * net: metrics: add proper netlink validation * net: phy: broadcom: Fix bcm_write_exp() * rtnetlink: validate attributes in do_setlink() * team: use netdev_features_t instead of u32 * net/mlx4: Fix irq-unsafe spinlock usage * qed: Fix mask for physical address in ILT entry * packet: fix reserve calculation * net: usb: cdc_mbim: add flag FLAG_SEND_ZLP * net/packet: refine check for priv area size * netdev-FAQ: clarify DaveM's position for stable backports * isdn: eicon: fix a missing-check bug * ipv4: remove warning in ip_recv_error * ip6mr: only set ip6mr_table from setsockopt when ip6mr_new_table succeeds * enic: set DMA mask to 47 bit * dccp: don't free ccid2_hc_tx_sock struct in dccp_disconnect() * bnx2x: use the right constant * brcmfmac: Fix check for ISO3166 code * drm: set FMODE_UNSIGNED_OFFSET for drm files * xfs: fix incorrect log_flushed on fsync * kconfig: Avoid format overflow warning from GCC 8.1 * mmap: relax file size limit for regular files * mmap: introduce sane default mmap limits * tpm: self test failure should not cause suspend to fail * tpm: do not suspend/resume if power stays on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777063/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04
** Changed in: linux (Ubuntu) Assignee: damiano (damiano1996) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1594023 Title: Poweroff or reboot hangs. Laptop won't shutdown. 16.04 Status in linux package in Ubuntu: Confirmed Bug description: This is about a fresh Ubuntu 16.04 install on a new laptop (asus x540sa). After pressing the shutdown button in the start menu; the shutdown procedure starts and in the final splash screen the system just hangs. Tried a second time by pressing Esc once the splash screen showed up and I saw that it reaches the line "Reached target shutdown" and just stops there, no matter how long I leave it there the machine won't turn off. I also tried a Kubuntu 16.04 fresh install on the same machine and it hanged too at the final splash screen where the pulsating logo stopped. Then I tried with Esc only to see the exact same line in the end. The issue seems to affect lately quite many users as shown by the google results of the past month / week or so. I have also tried shutting down from the console with shutdown -and all the parameters after that suggested online- and sudo poweroff but unfortunately they didn't do the trick. The exact same situation occurred. Unmounting the swap as suggested online doesn't work. Also rebooting the system is not working either due to the same issue. So right now the only way for me to poweroff the machine is to press the power button on the keyboard continuously. Reproducible: Always Steps to Reproduce: 1.Install OS 2.Do something, anything or nothing 3.Try to shutdown or reboot Actual Results: The computer is not shutting down: "Reached target shutdown" and hangs there. Expected Results: Powering off the machine. For what it's worth, closing the lid won't suspend the system, but using the menu buttons for suspension will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1763685] Re: Fix for flushing TM on coredump only if CPU has TM feature
** Changed in: ubuntu-power-systems Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1763685 Title: Fix for flushing TM on coredump only if CPU has TM feature Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Artful: Fix Released Bug description: Problem description == Fix for flushing TM on coredump only if CPU has TM feature ---Additional Hardware Info--- POWER9/POWER8/compat mode Machine Type = P9 baremetal + VM (POWER9, POWER8, Compat mode) ---Steps to Reproduce--- On POWER9 machines it's possible that TM is disabled for use by the VMs and if a coredump is generated in the VM it will crash since it will execute TM instructions when coredumping if a check is not present on the VM's kernel. Since POWER9 can run VM on P8 compatibility mode, it's necessary to patch all kernels that run on compat mode as well. Stack trace output: na Oops output: PID: 16438 TASK: c00272f515e0 CPU: 3 COMMAND: "vma05_vdso" #0 [c002711f7050] crash_kexec at c01a07e4 #1 [c002711f7080] die at c0025278 #2 [c002711f7120] _exception at c0025594 #3 [c002711f72b0] program_check_exception at c0a0e1b8 #4 [c002711f7330] program_check_common at c0006308 Program Check [700] exception frame: R0: R1: c002711f7620R2: c1274700 R3: c00272f51af0R4: 80010280b033R5: R6: 0100R7: R8: R9: 0002R10: R11: R12: c0010720R13: c7b81b00R14: R15: R16: c002711f7db0R17: 00040006 R18: c0002ab95800R19: 0100R20: 0001 R21: 0002R22: c0bfc1c8R23: c002711f79b8 R24: c0a30480R25: c0a30478R26: 0018 R27: R28: c0002ab95800R29: R30: 0100R31: c00272f515e0 NIP: c005b10cMSR: 80010288b033OR3: c00108e0 CTR: c0010720LR: c00108e4XER: 2000 CCR: 28002448MQ: 0001DAR: c00275599748 DSISR: c00274092988 Syscall Result: #5 [c002711f7620] tm_save_sprs at c005b10c [Link Register] [c002711f7620] vsr_get at c00108e4 #6 [c002711f7770] fill_thread_core_info at c03d8b44 #7 [c002711f7820] fill_note_info at c03d8e94 #8 [c002711f78b0] elf_core_dump at c03d94d4 #9 [c002711f7a90] do_coredump at c03dfcf4 #10 [c002711f7c20] get_signal_to_deliver at c01061d4 #11 [c002711f7d10] do_signal at c001beac #12 [c002711f7e00] do_notify_resume at c001c2cc #13 [c002711f7e30] ret_from_except_lite at c000a7b0 System Call [c00] exception frame: R0: 00faR1: 3fffd0470f00R2: 3fffa8af7f00 R3: R4: 4036R5: 000b R6: 3fffd0471428R7: 1770R8: 4036 R9: R10: R11: R12: R13: 3fffa8babb80R14: R15: R16: R17: R18: R19: R20: R21: R22: R23: R24: R25: R26: R27: 3fffa8b9fbb8R28: 3fffa8baR29: 3fffa8b9f550 R30: R31: NIP: 3fffa8ad54c8MSR: 8000d033OR3: 4036 CTR: LR: 155cXER: CCR: 42000442MQ: 0001DAR: 3fffa89b2100 DSISR: 4000 Syscall Result: == Comment: #1 - Gustavo Bueno Romero - 2018-04-12 17:24:21 == Dear maintainer, please cherry-pick the fix alreayd available upstream containing the additional check to avoid the issue here described. It must apply cleanly on stable kernels: "powerpc/tm: Flush TM only if CPU has TM feature": https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c1fa0768a8713b135848f78fd43ffc208d8ded70 Please cherry-pick the pointed out fix and apply it to kernel: HWE 4.x HWE 4.13 HWE-edge
[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04
@JohnDoe_71Rus are you running a kernel 4.9 or higher? Per discussion above, 4.9 seems to have solved the problem for many peoples. I wonder if the problem is resolved for OP, and, if somebody still affected, it should be opened as a separate bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1594023 Title: Poweroff or reboot hangs. Laptop won't shutdown. 16.04 Status in linux package in Ubuntu: Confirmed Bug description: This is about a fresh Ubuntu 16.04 install on a new laptop (asus x540sa). After pressing the shutdown button in the start menu; the shutdown procedure starts and in the final splash screen the system just hangs. Tried a second time by pressing Esc once the splash screen showed up and I saw that it reaches the line "Reached target shutdown" and just stops there, no matter how long I leave it there the machine won't turn off. I also tried a Kubuntu 16.04 fresh install on the same machine and it hanged too at the final splash screen where the pulsating logo stopped. Then I tried with Esc only to see the exact same line in the end. The issue seems to affect lately quite many users as shown by the google results of the past month / week or so. I have also tried shutting down from the console with shutdown -and all the parameters after that suggested online- and sudo poweroff but unfortunately they didn't do the trick. The exact same situation occurred. Unmounting the swap as suggested online doesn't work. Also rebooting the system is not working either due to the same issue. So right now the only way for me to poweroff the machine is to press the power button on the keyboard continuously. Reproducible: Always Steps to Reproduce: 1.Install OS 2.Do something, anything or nothing 3.Try to shutdown or reboot Actual Results: The computer is not shutting down: "Reached target shutdown" and hangs there. Expected Results: Powering off the machine. For what it's worth, closing the lid won't suspend the system, but using the menu buttons for suspension will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775230] Re: TP-LINK TL-WN722N causes 100% CPU usage due to trace logging
1)The manufacturer is "VIA Apollo Pro" and the model is "693-596A-DD" 2)"4.51 PG" and "04/07/00" 3) Tried 4.17.1-041701-generic and the problem still persists. 4a)Two USB ports, both free (no USB keyboard/mouse in use). 4b)The problem persists no matter the USB port the device is connected to. The problem still persists if I use a small (working) USB extension cord between the PC and the device. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775230 Title: TP-LINK TL-WN722N causes 100% CPU usage due to trace logging Status in linux package in Ubuntu: Incomplete Bug description: Hello. Running Ubuntu 18.04 (4.15.0-22-generic), after plugging my TP-LINK TL-WN722N into the USB port, the CPU usage goes to 100%, and there are multiple reports of "stack traces" in dmesg. The attached snippet repeats multiple consecutive times in the dmesg output (albeit with a different trace id). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Summary changed: - [regression] Bluetooth 3.0 mouses are automatically disconnected after connected + [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/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: New 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
What Ubuntu version did you upgrade from? -- 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 : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777062] Re: Logitech M535 mouse only pairs successfully after 4-5 tries
I wonder if there is any relation to bug 1773897 here... ** Summary changed: - Mouse only pairs successfully after 4-5 tries + Logitech M535 mouse only pairs successfully after 4-5 tries -- 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 :
[Kernel-packages] [Bug 1777063] [NEW] Xenial update to 4.4.137 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.137 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.137 stable release shall be applied: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777063 Title: Xenial update to 4.4.137 stable release Status in linux package in Ubuntu: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.137 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.137 stable release shall be applied: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 1768431] Comment bridged from LTC Bugzilla
--- Comment From mainam...@in.ibm.com 2018-06-15 01:44 EDT---
UMA,
Can you please verify and update the bug
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1768431
Title:
Request to revert SAUCE patches in the 18.04 SRU and update with
upstream version
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
This SRU was requested by IBM. It contains one SAUCE patch and three
commits from linux.next.
IBM requested that we revert a set of SAUCE patches from 18.04 and
replace them with patches from linux-next. Based on review comments,
there has been minor changes from the original SAUCE patches and the
versions in linux-next.
The first SAUCE patch contains all the changes between the current version
of SAUCE patches for latest cxlflash patches in bionic and the latest
version accepted by the community. This only has the needed changes and
makes it so we don't have to revert and re-apply a high number of patches.
In addition to the SAUCE patch, IBM requested the 3 additional new patches
from the linux-next tree.
== Fixes ==
UBUNTU: SAUCE: (no-up) cxlflash: OCXL diff between v2 and v3
a3feb6ef50de ("scsi: cxlflash: Synchronize reset and remove ops")
9a597cd4c0ce ("scsi: cxlflash: Remove commmands from pending list on timeout)"
d2d354a606d5 ("scsi: cxlflash: Handle spurious interrupts")
== Regression Potential ==
Medium. All the patches are specific to the cxlflash driver, but there
are four of them and one is a SAUCE patch.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - UMA KRISHNAN - 2018-04-30 14:41:30 ==
---Problem Description---
Request to revert SAUCE patches from 18.04 and apply the patches from
next/master.
Below set of cxlflash patches were submitted to Canonical after they
were sent to the community. Based on review comments, there has been
minor changes from that version. This BZ is to request reverting those
SAUCE patches with the ones that are queued in next/master tree for
4.18.
- SAUCE: cxlflash: Preserve number of interrupts for master contexts
- SAUCE: cxlflash: Avoid clobbering context control register value
- SAUCE: cxlflash: Add argument identifier names
- SAUCE: cxlflash: Introduce OCXL backend
- SAUCE: cxlflash: Hardware AFU for OCXL
- SAUCE: cxlflash: Read host function configuration
- SAUCE: cxlflash: Setup function acTag range
- SAUCE: cxlflash: Read host AFU configuration
- SAUCE: cxlflash: Setup AFU acTag range
- SAUCE: cxlflash: Setup AFU PASID
- SAUCE: cxlflash: Adapter context support for OCXL
- SAUCE: cxlflash: Use IDR to manage adapter contexts
- SAUCE: cxlflash: Support adapter file descriptors for OCXL
- SAUCE: cxlflash: Support adapter context discovery
- SAUCE: cxlflash: Support image reload policy modification
- SAUCE: cxlflash: MMIO map the AFU
- SAUCE: cxlflash: Support starting an adapter context
- SAUCE: cxlflash: Support process specific mappings
- SAUCE: cxlflash: Support AFU state toggling
- SAUCE: cxlflash: Support reading adapter VPD data
- SAUCE: cxlflash: Setup function OCXL link
- SAUCE: cxlflash: Setup OCXL transaction layer
- SAUCE: cxlflash: Support process element lifecycle
- SAUCE: cxlflash: Support AFU interrupt management
- SAUCE: cxlflash: Support AFU interrupt mapping and registration
- SAUCE: cxlflash: Support starting user contexts
- SAUCE: cxlflash: Support adapter context polling
- SAUCE: cxlflash: Support adapter context reading
- SAUCE: cxlflash: Support adapter context mmap and release
- SAUCE: cxlflash: Support file descriptor mapping
- SAUCE: cxlflash: Introduce object handle fop
- SAUCE: cxlflash: Setup LISNs for user contexts
- SAUCE: cxlflash: Setup LISNs for master contexts
- SAUCE: cxlflash: Update synchronous interrupt status bits
- SAUCE: cxlflash: Introduce OCXL context state machine
- SAUCE: cxlflash: Register for translation errors
- SAUCE: cxlflash: Support AFU reset
- SAUCE: cxlflash: Enable OCXL operations
Also, there are 3 additional patches added to end of this series that we
would like to request being pulled into the SRU stream. These 3 patches address
bug fixes.
The commit ids for the patches queued in next/master tree are,
768999d6b1eadc6a13b1fba1886f1708f433d82b scsi: cxlflash: Preserve number of
interrupts for master contexts
6c2b116dd38e3fbda10c3e3d5ac80ea7442e4f4d scsi: cxlflash: Avoid clobbering
context control register value
fcace1d5e11f518c6f91dd245fa1ac37393b47d3 scsi: cxlflash: Add argument
identifier names
863dbdc0552f8bc100df48bb231089c382b89004
