[Kernel-packages] [Bug 1808768] Re: Initrd of pc-kernel snap contains out-of-date packages
** 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/1808768 Title: Initrd of pc-kernel snap contains out-of-date packages Status in linux package in Ubuntu: Confirmed Bug description: The build script does not install package updates during generate the pc-kernel snap. I met this bug #1783810 when I was verify my Ubuntu Core 18 image on KVM. The system stuck at resizing the writable partition. the resize script of initrd called sgdisk to achieve the resizing. Inside sgdisk, it use libuuid1 to get random bytes and generate UUIDs. After I extracted the kernel snap, I found it is still using libuuid1 2.31.1-0.4ubuntu3 which is not the latest version. At this moment, Bionic has 2.31.1-0.4ubuntu3.2. Then I added commands to make the build script installing package updates. After that, the system can boot correctly without any problem. I am wondering if there is any concern to pull updates before building? The attachment is my patch to pull updates. Snippet of console output, before patch [2.491404] usbcore: registered new interface driver usb-storage [2.503788] sdhci: Secure Digital Host Controller Interface driver [2.505627] sdhci: Copyright(c) Pierre Ossman [2.548485] initrd: found more than 10% free space on disk, resizing /dev/sda3 [2.550345] initrd: partition to full disk size, see /dev/kmsg for details [2.912472] clocksource: tsc: mask: 0x max_cycles: 0x255b2dea34c, max_idle_ns: 440795243480 ns ## several keystrokes here, or the boot process won't continue [ 351.361426] random: crng init done [ 351.423462] fixing backup GPT [ 352.435735] systemd-udevd[240]: passed device to netlink monitor 0x55e45653e330 [ 352.443221] sda: sda1 sda2 sda3 [ 352.445486] The operation has completed successfully. Snippet of console output, after patch [2.548203] usbcore: registered new interface driver usb-storage [2.561439] sdhci: Secure Digital Host Controller Interface driver [2.562878] sdhci: Copyright(c) Pierre Ossman [2.602093] initrd: found more than 10% free space on disk, resizing /dev/sda3 [2.603900] initrd: partition to full disk size, see /dev/kmsg for details ## block a few seconds, until timeout. [2.912418] clocksource: tsc: mask: 0x max_cycles: 0x255b2dea34c, max_idle_ns: 440795243480 ns [9.174552] random: fast init done [9.179127] random: parted: uninitialized urandom read (16 bytes read) [9.183726] random: parted: uninitialized urandom read (16 bytes read) [9.190606] random: parted: uninitialized urandom read (16 bytes read) [9.230419] fixing backup GPT [9.236989] random: crng init done [9.238102] random: 5 urandom warning(s) missed due to ratelimiting [ 10.245047] systemd-udevd[259]: passed device to netlink monitor 0x56376c45b150 [ 10.253093] sda: sda1 sda2 sda3 [ 10.256202] The operation has completed successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808768/+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 1808768] [NEW] Initrd of pc-kernel snap contains out-of-date packages
Public bug reported: The build script does not install package updates during generate the pc-kernel snap. I met this bug #1783810 when I was verify my Ubuntu Core 18 image on KVM. The system stuck at resizing the writable partition. the resize script of initrd called sgdisk to achieve the resizing. Inside sgdisk, it use libuuid1 to get random bytes and generate UUIDs. After I extracted the kernel snap, I found it is still using libuuid1 2.31.1-0.4ubuntu3 which is not the latest version. At this moment, Bionic has 2.31.1-0.4ubuntu3.2. Then I added commands to make the build script installing package updates. After that, the system can boot correctly without any problem. I am wondering if there is any concern to pull updates before building? The attachment is my patch to pull updates. Snippet of console output, before patch [2.491404] usbcore: registered new interface driver usb-storage [2.503788] sdhci: Secure Digital Host Controller Interface driver [2.505627] sdhci: Copyright(c) Pierre Ossman [2.548485] initrd: found more than 10% free space on disk, resizing /dev/sda3 [2.550345] initrd: partition to full disk size, see /dev/kmsg for details [2.912472] clocksource: tsc: mask: 0x max_cycles: 0x255b2dea34c, max_idle_ns: 440795243480 ns ## several keystrokes here, or the boot process won't continue [ 351.361426] random: crng init done [ 351.423462] fixing backup GPT [ 352.435735] systemd-udevd[240]: passed device to netlink monitor 0x55e45653e330 [ 352.443221] sda: sda1 sda2 sda3 [ 352.445486] The operation has completed successfully. Snippet of console output, after patch [2.548203] usbcore: registered new interface driver usb-storage [2.561439] sdhci: Secure Digital Host Controller Interface driver [2.562878] sdhci: Copyright(c) Pierre Ossman [2.602093] initrd: found more than 10% free space on disk, resizing /dev/sda3 [2.603900] initrd: partition to full disk size, see /dev/kmsg for details ## block a few seconds, until timeout. [2.912418] clocksource: tsc: mask: 0x max_cycles: 0x255b2dea34c, max_idle_ns: 440795243480 ns [9.174552] random: fast init done [9.179127] random: parted: uninitialized urandom read (16 bytes read) [9.183726] random: parted: uninitialized urandom read (16 bytes read) [9.190606] random: parted: uninitialized urandom read (16 bytes read) [9.230419] fixing backup GPT [9.236989] random: crng init done [9.238102] random: 5 urandom warning(s) missed due to ratelimiting [ 10.245047] systemd-udevd[259]: passed device to netlink monitor 0x56376c45b150 [ 10.253093] sda: sda1 sda2 sda3 [ 10.256202] The operation has completed successfully. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "Makefile.diff" https://bugs.launchpad.net/bugs/1808768/+attachment/5222896/+files/Makefile.diff -- 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/1808768 Title: Initrd of pc-kernel snap contains out-of-date packages Status in linux package in Ubuntu: Incomplete Bug description: The build script does not install package updates during generate the pc-kernel snap. I met this bug #1783810 when I was verify my Ubuntu Core 18 image on KVM. The system stuck at resizing the writable partition. the resize script of initrd called sgdisk to achieve the resizing. Inside sgdisk, it use libuuid1 to get random bytes and generate UUIDs. After I extracted the kernel snap, I found it is still using libuuid1 2.31.1-0.4ubuntu3 which is not the latest version. At this moment, Bionic has 2.31.1-0.4ubuntu3.2. Then I added commands to make the build script installing package updates. After that, the system can boot correctly without any problem. I am wondering if there is any concern to pull updates before building? The attachment is my patch to pull updates. Snippet of console output, before patch [2.491404] usbcore: registered new interface driver usb-storage [2.503788] sdhci: Secure Digital Host Controller Interface driver [2.505627] sdhci: Copyright(c) Pierre Ossman [2.548485] initrd: found more than 10% free space on disk, resizing /dev/sda3 [2.550345] initrd: partition to full disk size, see /dev/kmsg for details [2.912472] clocksource: tsc: mask: 0x max_cycles: 0x255b2dea34c, max_idle_ns: 440795243480 ns ## several keystrokes here, or the boot process won't continue [ 351.361426] random: crng init done [ 351.423462] fixing backup GPT [ 352.435735] systemd-udevd[240]: passed device to netlink monitor 0x55e45653e330 [ 352.443221] sda: sda1 sda2 sda3 [ 352.445486] The operation has completed successfully. Snippet of console output, after patch [2.548203] usbcore: registered new interface driver usb-storage [
[Kernel-packages] [Bug 1803942] Re: System randomly hangs during suspend when mei_wdt is loaded
With the proposed kernel, my system passed a 30-run stress. 1. Enable the -proposed repository 2. Install the proposed kernel and reboot 3. uname -r 4.15.0-43-generic 4. sudo modprobe mei_wdt 5. for s in $(seq 30); do sudo rtcwake -v -m mem -s 15; sleep 15; done 6. verify the result is success ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1803942 Title: System randomly hangs during suspend when mei_wdt is loaded Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Committed Bug description: Problem description: System randomly hangs during suspend when mei_wdt is loaded. Platform: Intel Dawson Canyon I5 (NUC7i5DNHE) and I7 (NUC7i7DNHE) Test procedure: 1. Install Ubuntu 18.04 and do apt full-upgrade 2. Enable mei_wdt: $ sudo modprobe mei_wdt 3. Do system S3 test: $ sudo systemctl suspend or $ sudo rtcwake -v -m mem -s 15 4. Afterward, I noticed that somehow system will hang during suspend/resume. Expect result: Suspend/resume won't impact system. Actual result: System will hang during S3 test. Additional info: - BIOS version: V57 - Another i3 platform (NUC7i3DNHNC) doesn't have this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1803942/+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 1803942] Re: System randomly hangs during suspend when mei_wdt is loaded
I commented out this patch of 876dcb and cannot reproduce the issue afterward. diff --git a/drivers/base/dd.c b/drivers/base/dd.c index 2c964f5..37c0105 100644 --- a/drivers/base/dd.c +++ b/drivers/base/dd.c @@ -868,6 +868,13 @@ static void __device_release_driver(struct device *dev, struct device *parent) dev->bus->remove(dev); else if (drv->remove) drv->remove(dev); + /* +* A concurrent invocation of the same function might +* have released the driver successfully while this one +* was waiting, so check for that. +*/ + if (dev->driver != drv) + return; device_links_driver_cleanup(dev); dma_deconfigure(dev); -- 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/1803942 Title: System randomly hangs during suspend when mei_wdt is loaded Status in linux package in Ubuntu: Confirmed Bug description: Problem description: System randomly hangs during suspend when mei_wdt is loaded. Platform: Intel Dawson Canyon I5 (NUC7i5DNHE) and I7 (NUC7i7DNHE) Test procedure: 1. Install Ubuntu 18.04 and do apt full-upgrade 2. Enable mei_wdt: $ sudo modprobe mei_wdt 3. Do system S3 test: $ sudo systemctl suspend or $ sudo rtcwake -v -m mem -s 15 4. Afterward, I noticed that somehow system will hang during suspend/resume. Expect result: Suspend/resume won't impact system. Actual result: System will hang during S3 test. Additional info: - BIOS version: V57 - Another i3 platform (NUC7i3DNHNC) doesn't have this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803942/+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 1803942] Re: System randomly hangs during suspend when mei_wdt is loaded
I tried mainline kernel 4.20-rc2, 4.18, 4.17, 4.16 and 4.15. They all passed a 50 run test. To validate when the issue is introduced, I installed several Ubuntu kernel packages and address the issue/regression happens between 4.15.0-34 and 4.15.0-36. Finished the kernel bisect and probably found the first bad commit. $ git bisect log # bad: [fd01374000c83b59d3ce234fbb970cb91404bd42] UBUNTU: Ubuntu-4.15.0-36.39 # good: [ffaad0a9f46742f6d71af975a6a061ffe6963aca] UBUNTU: Ubuntu-4.15.0-34.37 git bisect start 'Ubuntu-4.15.0-36.39' 'Ubuntu-4.15.0-34.37' # good: [003ae88ae88d48643e71dc69c18d4eda598339d5] Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox receiving unknown message" git bisect good 003ae88ae88d48643e71dc69c18d4eda598339d5 # good: [d3d4b20788eee72dcb1ed5ace7dbee6aafbe65cf] net: hns3: Fix for mac pause not disable in pfc mode git bisect good d3d4b20788eee72dcb1ed5ace7dbee6aafbe65cf # good: [8e499f213175b65bcc08a3c685ea6717e7668cec] arm64: ssbd: Introduce thread flag to control userspace mitigation git bisect good 8e499f213175b65bcc08a3c685ea6717e7668cec # good: [11cdaf61c1986ea682398b48e238fd915393b2e6] KVM: PPC: Check if IOMMU page is contained in the pinned physical page git bisect good 11cdaf61c1986ea682398b48e238fd915393b2e6 # good: [db6800337d38a5b2adbaa78fcb2c29936e1d] s390: fix br_r1_trampoline for machines without exrl git bisect good db6800337d38a5b2adbaa78fcb2c29936e1d # good: [f1f016ed54582502d59de991ddbecfe2373722c0] x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+ git bisect good f1f016ed54582502d59de991ddbecfe2373722c0 # good: [f1f016ed54582502d59de991ddbecfe2373722c0] x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+ git bisect good f1f016ed54582502d59de991ddbecfe2373722c0 # bad: [cb3b0751997c8bd45c76a7401e2edb019cdaaab3] UBUNTU: Start new release git bisect bad cb3b0751997c8bd45c76a7401e2edb019cdaaab3 # bad: [cb3b0751997c8bd45c76a7401e2edb019cdaaab3] UBUNTU: Start new release git bisect bad cb3b0751997c8bd45c76a7401e2edb019cdaaab3 # bad: [d5bad4136d14cda66cb7c06b10b80c64ae695c78] UBUNTU: Ubuntu-4.15.0-35.38 git bisect bad d5bad4136d14cda66cb7c06b10b80c64ae695c78 # bad: [876dcb5f4576934a1a11b091b40ce548f048340e] UBUNTU: SAUCE: vfio -- release device lock before userspace requests git bisect bad 876dcb5f4576934a1a11b091b40ce548f048340e # first bad commit: [876dcb5f4576934a1a11b091b40ce548f048340e] UBUNTU: SAUCE: vfio -- release device lock before userspace requests -- 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/1803942 Title: System randomly hangs during suspend when mei_wdt is loaded Status in linux package in Ubuntu: Confirmed Bug description: Problem description: System randomly hangs during suspend when mei_wdt is loaded. Platform: Intel Dawson Canyon I5 (NUC7i5DNHE) and I7 (NUC7i7DNHE) Test procedure: 1. Install Ubuntu 18.04 and do apt full-upgrade 2. Enable mei_wdt: $ sudo modprobe mei_wdt 3. Do system S3 test: $ sudo systemctl suspend or $ sudo rtcwake -v -m mem -s 15 4. Afterward, I noticed that somehow system will hang during suspend/resume. Expect result: Suspend/resume won't impact system. Actual result: System will hang during S3 test. Additional info: - BIOS version: V57 - Another i3 platform (NUC7i3DNHNC) doesn't have this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803942/+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 1803942] [NEW] System randomly hangs during suspend when mei_wdt is loaded
Public bug reported: Problem description: System randomly hangs during suspend when mei_wdt is loaded. Platform: Intel Dawson Canyon I5 (NUC7i5DNHE) and I7 (NUC7i7DNHE) Test procedure: 1. Install Ubuntu 18.04 and do apt full-upgrade 2. Enable mei_wdt: $ sudo modprobe mei_wdt 3. Do system S3 test: $ sudo systemctl suspend or $ sudo rtcwake -v -m mem -s 15 4. Afterward, I noticed that somehow system will hang during suspend/resume. Expect result: Suspend/resume won't impact system. Actual result: System will hang during S3 test. Additional info: - BIOS version: V57 - Another i3 platform (NUC7i3DNHNC) doesn't have this issue. ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1803942 Title: System randomly hangs during suspend when mei_wdt is loaded Status in linux package in Ubuntu: Incomplete Bug description: Problem description: System randomly hangs during suspend when mei_wdt is loaded. Platform: Intel Dawson Canyon I5 (NUC7i5DNHE) and I7 (NUC7i7DNHE) Test procedure: 1. Install Ubuntu 18.04 and do apt full-upgrade 2. Enable mei_wdt: $ sudo modprobe mei_wdt 3. Do system S3 test: $ sudo systemctl suspend or $ sudo rtcwake -v -m mem -s 15 4. Afterward, I noticed that somehow system will hang during suspend/resume. Expect result: Suspend/resume won't impact system. Actual result: System will hang during S3 test. Additional info: - BIOS version: V57 - Another i3 platform (NUC7i3DNHNC) doesn't have this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803942/+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 1802260] Re: Please include modules for NVMe and USB HID in pc-kernel snap initrd
applied this patch against lp:~ubuntu-kernel/ubuntu/+source/linux- snap/+git/bionic then the issue is gone. ** Patch added: "add-nvme-and-usbhid.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802260/+attachment/5210613/+files/add-nvme-and-usbhid.patch -- 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/1802260 Title: Please include modules for NVMe and USB HID in pc-kernel snap initrd Status in linux package in Ubuntu: Confirmed Bug description: When trying Ubuntu Core with the pc-kernel snap, the system showed 'cannot find writable partition'. The system was stopped at the initrd stage and didn't accept any input. My system is using a NVMe disk and it seems the pc-kernel doesn't provide the related modules in its initrd. Also, it's not possible to enter the initramfs environment because of the lacking of USB HID modules. Is it possible to include these two categories of drivers in the initrd of pc-kernel, please? Verified both 4.4 and 4.15 (track 18) have the same issue. $ squashfuse pc-kernel_162.snap pc-kernel $ lsinitramfs pc-kernel/initrd.img |grep -E 'nvme|usbhid' [nothing is showed] $ fusermount -u pc-kernel $ squashfuse pc-kernel_165.snap pc-kernel $ lsinitramfs pc-kernel/initrd.img |grep -E 'nvme|usbhid' [nothing is showed] $ fusermount -u pc-kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802260/+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 1802260] Re: Please include modules for NVMe and USB HID in pc-kernel snap initrd
The fix would be similar with this bug #1794279 ** 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/1802260 Title: Please include modules for NVMe and USB HID in pc-kernel snap initrd Status in linux package in Ubuntu: Confirmed Bug description: When trying Ubuntu Core with the pc-kernel snap, the system showed 'cannot find writable partition'. The system was stopped at the initrd stage and didn't accept any input. My system is using a NVMe disk and it seems the pc-kernel doesn't provide the related modules in its initrd. Also, it's not possible to enter the initramfs environment because of the lacking of USB HID modules. Is it possible to include these two categories of drivers in the initrd of pc-kernel, please? Verified both 4.4 and 4.15 (track 18) have the same issue. $ squashfuse pc-kernel_162.snap pc-kernel $ lsinitramfs pc-kernel/initrd.img |grep -E 'nvme|usbhid' [nothing is showed] $ fusermount -u pc-kernel $ squashfuse pc-kernel_165.snap pc-kernel $ lsinitramfs pc-kernel/initrd.img |grep -E 'nvme|usbhid' [nothing is showed] $ fusermount -u pc-kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802260/+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 1802260] [NEW] Please include modules for NVMe and USB HID in pc-kernel snap initrd
Public bug reported: When trying Ubuntu Core with the pc-kernel snap, the system showed 'cannot find writable partition'. The system was stopped at the initrd stage and didn't accept any input. My system is using a NVMe disk and it seems the pc-kernel doesn't provide the related modules in its initrd. Also, it's not possible to enter the initramfs environment because of the lacking of USB HID modules. Is it possible to include these two categories of drivers in the initrd of pc-kernel, please? Verified both 4.4 and 4.15 (track 18) have the same issue. $ squashfuse pc-kernel_162.snap pc-kernel $ lsinitramfs pc-kernel/initrd.img |grep -E 'nvme|usbhid' [nothing is showed] $ fusermount -u pc-kernel $ squashfuse pc-kernel_165.snap pc-kernel $ lsinitramfs pc-kernel/initrd.img |grep -E 'nvme|usbhid' [nothing is showed] $ fusermount -u pc-kernel ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Summary changed: - Please include modules for NVMe and USBHID in pc-kernel snap initrd + Please include modules for NVMe and USB HID in pc-kernel snap initrd -- 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/1802260 Title: Please include modules for NVMe and USB HID in pc-kernel snap initrd Status in linux package in Ubuntu: Incomplete Bug description: When trying Ubuntu Core with the pc-kernel snap, the system showed 'cannot find writable partition'. The system was stopped at the initrd stage and didn't accept any input. My system is using a NVMe disk and it seems the pc-kernel doesn't provide the related modules in its initrd. Also, it's not possible to enter the initramfs environment because of the lacking of USB HID modules. Is it possible to include these two categories of drivers in the initrd of pc-kernel, please? Verified both 4.4 and 4.15 (track 18) have the same issue. $ squashfuse pc-kernel_162.snap pc-kernel $ lsinitramfs pc-kernel/initrd.img |grep -E 'nvme|usbhid' [nothing is showed] $ fusermount -u pc-kernel $ squashfuse pc-kernel_165.snap pc-kernel $ lsinitramfs pc-kernel/initrd.img |grep -E 'nvme|usbhid' [nothing is showed] $ fusermount -u pc-kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802260/+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 1510570] Re: BLE pairing fail
I tried to specify the udev rule more precisely, i.e. only power up a host
controller.
Is there anybody could give it a try?
#/lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules
# Set bluetooth power up
ACTION=="add", SUBSYSTEM=="bluetooth", KERNEL=="hci[0-9]*",
ENV{DEVTYPE}=="host", RUN+="/bin/hciconfig %k up"
--
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/1510570
Title:
BLE pairing fail
Status in bluez package in Ubuntu:
Confirmed
Bug description:
On 15.10 we now have bluez 5 so we can pair BLE devices like the
Microsoft Arc Touch Bluetooth Mouse.
But this pairing doesn't work very well. Mouse is seen but pairing fail.
More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5
This is due to udev rule that use "hcitool" to power on device.
Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used
instead of udev rules.
here is a commit with this parameter:
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138
And a ppa to test it:
https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+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
