[Kernel-packages] [Bug 1767292] [NEW] The bluetooth mouse cannot connect after sleep mode.
You have been subscribed to a public bug: The bluetooth mouse cannot connect after sleep mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giacomo1998 F pulseaudio CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Fri Apr 27 09:49:41 2018 InstallationDate: Installed on 2017-04-13 (378 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to bionic on 2018-04-13 (13 days ago) dmi.bios.date: 07/27/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R08ET43W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FU001PMC dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR08ET43W(1.17):bd07/27/2016:svnLENOVO:pn20FU001PMC:pvrThinkPadL460:rvnLENOVO:rn20FU001PMC:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L460 dmi.product.name: 20FU001PMC dmi.product.version: ThinkPad L460 dmi.sys.vendor: LENOVO ** Affects: bluez (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic wayland-session -- The bluetooth mouse cannot connect after sleep mode. https://bugs.launchpad.net/bugs/1767292 You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774387] Re: inotify07 and inotify08 in LTP syscall test failed with X-LTS / A kernel
** Summary changed: - inotify07 and inotify08 in LTP syscall test failed with X-LTS kernel + inotify07 and inotify08 in LTP syscall test failed with X-LTS / A kernel -- 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/1774387 Title: inotify07 and inotify08 in LTP syscall test failed with X-LTS / A kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-lts-xenial package in Ubuntu: New Bug description: The "inotify07" and "inotify08" from the LTP syscall tests have failed on a testing node with X-LTS i386 kernel installed (they were not tested on amd64/arm64 because the test was not ready when the SRU starts). <<>> tag=inotify07 stime=1527762360 cmdline="inotify07" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s inotify07.c:206: INFO: ovl/test_dir ino=27918358 inotify07.c:216: INFO: ovl/test_dir ino=27918358 inotify07.c:157: FAIL: didn't get event: mask=4004 inotify07.c:157: FAIL: didn't get event: mask=0020 inotify07.c:157: FAIL: didn't get event: mask=0008 inotify07.c:157: FAIL: didn't get event: mask=0004 Summary: passed 0 failed 4 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=37 <<>> <<>> tag=inotify08 stime=1527762360 cmdline="inotify08" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s inotify08.c:201: INFO: ovl/test_file ino=27918358, dev=8:1 inotify08.c:212: INFO: ovl/test_file ino=27918363, dev=8:1 inotify08.c:150: FAIL: didn't get event: mask=4 inotify08.c:150: FAIL: didn't get event: mask=20 inotify08.c:150: FAIL: didn't get event: mask=8 Summary: passed 0 failed 3 skipped 0 warnings 0 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153~14.04.1 ProcVersionSignature: User Name 4.4.0-127.153~14.04.1-generic 4.4.128 Uname: Linux 4.4.0-127-generic i686 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: i386 Date: Thu May 31 10:19:30 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1774387/+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 1771780] Comment bridged from LTC Bugzilla
--- Comment From aksad...@in.ibm.com 2018-06-06 03:08 EDT--- Patch has been accepted upstream and is available https://git.kernel.org/powerpc/c/ac9816dcbab53c57bcf1d7b15370b0 -- 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/1771780 Title: [LTCTest][OPAL][OP920] cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: == SRU Justification == During testing, IBM found that cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded. A patch has been submitted upstream by IBM. However, the patch has not landed in linux-next or mainline as of yet. For that reason, this SRU request is being sent as a SAUCE patch request. == Fix == UBUNTU: SAUCE: cpuidle/powernv : init all present cpus for deep states == Regression Potential == Low. Limited to powerpc. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2018-05-16 04:07:59 == ---Problem Description--- cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded ---uname output--- Linux ltc-wspoon11 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install a P9 Open Power Hardware with Ubuntu 18.04 OS. root@ltc-wspoon11:~# uname -a Linux ltc-wspoon11 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@ltc-wspoon11:~# cat /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic Then guard an entire processor and also guard all the CORES in the processor 0 except for 1 single core. root@ltc-wspoon11:~# opal-gard list ID | Error| Type | Path --- 0001 | | Manual | /Sys0/Node0/Proc0/EQ1/EX0/Core0 0002 | | Manual | /Sys0/Node0/Proc0/EQ1/EX0/Core1 0003 | | Manual | /Sys0/Node0/Proc1 0004 | | Manual | /Sys0/Node0/Proc0/EQ2/EX0/Core1 0005 | | Manual | /Sys0/Node0/Proc0/EQ2/EX0/Core0 0006 | | Manual | /Sys0/Node0/Proc0/EQ2/EX1/Core0 0007 | | Manual | /Sys0/Node0/Proc0/EQ2/EX1/Core1 0008 | | Manual | /Sys0/Node0/Proc0/EQ3/EX0/Core0 0009 | | Manual | /Sys0/Node0/Proc0/EQ3/EX0/Core1 000a | | Manual | /Sys0/Node0/Proc0/EQ3/EX1/Core0 000b | | Manual | /Sys0/Node0/Proc0/EQ3/EX1/Core1 000c | | Manual | /Sys0/Node0/Proc0/EQ4/EX0/Core0 000d | | Manual | /Sys0/Node0/Proc0/EQ4/EX0/Core1 000e | | Manual | /Sys0/Node0/Proc0/EQ4/EX1/Core0 000f | | Manual | /Sys0/Node0/Proc0/EQ4/EX1/Core1 0010 | | Manual | /Sys0/Node0/Proc0/EQ5/EX0/Core0 0011 | | Manual | /Sys0/Node0/Proc0/EQ5/EX0/Core1 0012 | | Manual | /Sys0/Node0/Proc0/EQ5/EX1/Core0 0013 | | Manual | /Sys0/Node0/Proc0/EQ5/EX1/Core1 0014 | | Manual | /Sys0/Node0/Proc0/EQ1/EX1/Core0 0015 | | Manual | /Sys0/Node0/Proc0/EQ1/EX1/Core1 0016 | | Manual | /Sys0/Node0/Proc0/EQ0/EX1/Core1 0017 | | Manual | /Sys0/Node0/Proc0/EQ0/EX1/Core0 === Then execute the cpupower idle-info command to check the idle states being shown in the OS. root@ltc-wspoon11:~# cpupower idle-info CPUidle driver: powernv_idle CPUidle governor: menu analyzing CPU 0: Number of idle states: 7 Available idle states: snooze stop0_lite stop0 stop1_lite stop1 stop2_lite stop2 snooze: Flags/Description: snooze Latency: 0 Usage: 774653 Duration: 7698954 stop0_lite: Flags/Description: stop0_lite Latency: 1 Usage: 2751 Duration: 11363825 stop0: Flags/Description: stop0 Latency: 2 Usage: 2343 Duration: 915084 stop1_lite:
[Kernel-packages] [Bug 1774191] Re: linux-lts-trusty: 3.13.0-151.201~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1774191 Title: linux-lts-trusty: 3.13.0-151.201~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid 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 Released 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1774190 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774191/+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 1767124] Re: bluetoothd crashed with SIGILL in agent_get() from adapter_register()
I can't find any other reports of this crash globally. But also the stack in comment #3 may be wrong. Please upgrade to Ubuntu 18.04 if you can. Otherwise there is little we can do (also because the upstream BlueZ developers won't want to help while you're on an old version). -- 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/1767124 Title: bluetoothd crashed with SIGILL in agent_get() from adapter_register() Status in bluez package in Ubuntu: New Bug description: systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Don 2018-04-26 16:16:36 CEST; 2min 25s ago Docs: man:bluetoothd(8) Process: 1458 ExecStart=/usr/lib/bluetooth/bluetoothd (code=dumped, signal=ILL) Main PID: 1458 (code=dumped, signal=ILL) Status: "Running" Apr 26 16:16:35 tiger systemd[1]: Starting Bluetooth service... Apr 26 16:16:35 tiger bluetoothd[1458]: Bluetooth daemon 5.37 Apr 26 16:16:35 tiger systemd[1]: Started Bluetooth service. Apr 26 16:16:35 tiger bluetoothd[1458]: Starting SDP server Apr 26 16:16:35 tiger bluetoothd[1458]: Bluetooth management interface 1.14 initialized Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Main process exited, code=dumped, status=4/ILL Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Unit entered failed state. Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Failed with result 'core-dump'. Apr 26 16:16:36 tiger systemd[1]: bluetooth.service: Start request repeated too quickly. Apr 26 16:16:36 tiger systemd[1]: Failed to start Bluetooth service. sudo gdb /usr/lib/bluetooth/bluetoothd ... Program received signal SIGILL, Illegal instruction. agent_get (owner=owner@entry=0x0) at src/agent.c:267 267 src/agent.c: Datei oder Verzeichnis nicht gefunden. (gdb) bt #0 agent_get (owner=owner@entry=0x0) at src/agent.c:267 #1 0x555d861b in adapter_register (adapter=0x5587fed0) at src/adapter.c:7434 #2 read_info_complete (status=, length=, param=, user_data=0x5587fed0) at src/adapter.c:7897 #3 0x55602656 in request_complete (mgmt=mgmt@entry=0x55879ef0, status=, opcode=opcode@entry=4, index=index@entry=0, length=length@entry=280, param=0x55879f79) at src/shared/mgmt.c:261 #4 0x5560311c in can_read_data (io=, user_data=0x55879ef0) at src/shared/mgmt.c:353 #5 0x5560ee25 in watch_callback (channel=, cond=, user_data=) at src/shared/io-glib.c:170 #6 0x77b1004a in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x77b103f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x77b10712 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x5557009d in main (argc=1, argv=0x7fffe658) at src/main.c:687 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1767124/+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 1246981] Re: Bluetooth mouse fails to re-connect after sleep.
** Tags added: 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/1246981 Title: Bluetooth mouse fails to re-connect after sleep. Status in bluez package in Ubuntu: Confirmed Bug description: This exact harware was working faultlessly in 13.04. Since re- installing at 13.10 the mouse consistently failes to reconnect after the device either hybernates or ever goes to screen saver sleep. I have to remove the dive and re-add it each time (which works well). There are other issues with the bluetooth stack as well in that I have not found any way to use bluetooth tethering to my mobile which again worked well and was easy to configure in 13.04 Peter. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 1 16:44:37 2013 InstallationDate: Installed on 2013-10-19 (13 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. Latitude E6530 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 20:16:D8:9C:38:E5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0 TX bytes:37955 acl:131 sco:0 commands:5096 errors:0 syslog: Nov 1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 0x7f6489f7b450 with :1.582 activated Nov 1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command complete for opcode 37 Nov 1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29 Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+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 1775187] syslog.txt
apport information ** Attachment added: "syslog.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149226/+files/syslog.txt -- 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/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 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 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packa
[Kernel-packages] [Bug 1775187] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149223/+files/UdevDb.txt -- 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/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 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 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packa
[Kernel-packages] [Bug 1646029] Re: bluetooth stopped working on upgrade to 16.10
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: bluez (Ubuntu) Status: New => Invalid -- 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/1646029 Title: bluetooth stopped working on upgrade to 16.10 Status in bluez package in Ubuntu: Invalid Bug description: prior had working system in 16.04 had installed sudo apt-get pulseaudio-module-bluetooth sudo apt-get install pulseaudio pulseaudio-module-bluetooth pavucontrol bluez-firmware sudo apt-get install pulseaudio-module-bluetooth for use with bluetooth headset ad2p and it was working well. Upgrade and the bluetooth using usb dongle stopped working syslog == Nov 30 08:30:21 betelgeuse pulseaudio[1927]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Nov 30 09:01:00 betelgeuse pulseaudio[1927]: message repeated 3 times: [ [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended.] Nov 30 09:05:45 betelgeuse systemd[1]: Starting Daily apt activities... Nov 30 09:05:46 betelgeuse systemd[1]: Started Daily apt activities. Nov 30 09:05:46 betelgeuse systemd[1]: apt-daily.timer: Adding 7h 32min 41.100513s random time. Nov 30 09:05:46 betelgeuse systemd[1]: apt-daily.timer: Adding 2h 14min 40.439253s random time. Nov 30 09:10:37 betelgeuse pulseaudio[1927]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Nov 30 09:10:37 betelgeuse pulseaudio[1927]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Nov 30 09:17:01 betelgeuse CRON[18210]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 30 09:17:29 betelgeuse pulseaudio[1927]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Nov 30 09:34:18 betelgeuse pulseaudio[1927]: message repeated 3 times: [ [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended.] Nov 30 10:17:01 betelgeuse CRON[18428]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 30 10:45:18 betelgeuse pulseaudio[1927]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Nov 30 10:45:18 betelgeuse pulseaudio[1927]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Nov 30 11:17:01 betelgeuse CRON[18635]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 30 11:42:44 betelgeuse pulseaudio[1927]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Nov 30 11:42:44 betelgeuse pulseaudio[1927]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended dpkg.log 2016-11-23 19:37:07 startup archives unpack 2016-11-23 19:37:07 upgrade bluez:amd64 5.37-0ubuntu5 5.41-0ubuntu3 2016-11-23 19:37:07 status half-configured bluez:amd64 5.37-0ubuntu5 2016-11-23 19:37:07 status unpacked bluez:amd64 5.37-0ubuntu5 2016-11-23 19:37:07 status half-installed bluez:amd64 5.37-0ubuntu5 2016-11-23 19:41:58 startup packages remove 2016-11-23 19:41:58 status installed pulseaudio-module-x11:amd64 1:8.0-0ubuntu3 2016-11-23 19:41:59 remove pulseaudio-module-x11:amd64 1:8.0-0ubuntu3 2016-11-23 19:41:59 status half-configured pulseaudio-module-x11:amd64 1:8.0-0ubuntu3 2016-11-23 19:41:59 status half-installed pulseaudio-module-x11:amd64 1:8.0-0ubuntu3 2016-11-23 19:41:59 status config-files pulseaudio-module-x11:amd64 1:8.0-0ubuntu3 2016-11-23 19:41:59 status config-files pulseaudio-module-x11:amd64 1:8.0-0ubuntu3 2016-11-23 19:41:59 status config-files pulseaudio-module-x11:amd64 1:8.0-0ubuntu3 2016-11-23 19:41:59 status not-installed pulseaudio-module-x11:amd64 2016-11-23 19:41:59 startup archives unpack 2016-11-23 19:42:09 upgrade pulseaudio-module-zeroconf:amd64 1:8.0-0ubuntu3 1:9.0-2ubuntu2.1 2016-11-23 19:42:09 status half-configured pulseaudio-module-zeroconf:amd64 1:8.0-0ubuntu3 2016-11-23 19:42:10 status unpacked pulseaudio-module-zeroconf:amd64 1:8.0-0ubuntu3 2016-11-23 19:42:10 status half-installed pulseaudio-module-zeroconf:amd64 1:8.0-0ubuntu3 2016-11-23 19:42:10 status half-installed pulseaudio-module-zeroconf:amd64 1:8.0-0ubuntu3 2016-11-23 19:42:10 status unpacked pulseaudio-module-zeroconf:amd64 1:9.0-2ubuntu2.1 2016-11-23 19:42:10 status unpacked pulseaudio-module-zeroconf:amd64 1:9.0-2ubuntu2.1 2016-11-23 19:42:10 upgrade pu
[Kernel-packages] [Bug 1767292] Re: The bluetooth mouse cannot connect after sleep mode.
*** This bug is a duplicate of bug 1246981 *** https://bugs.launchpad.net/bugs/1246981 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1246981, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: alsa-driver (Ubuntu) => bluez (Ubuntu) ** This bug has been marked a duplicate of bug 1246981 Bluetooth mouse fails to re-connect after sleep. -- 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/1767292 Title: The bluetooth mouse cannot connect after sleep mode. Status in bluez package in Ubuntu: Confirmed Bug description: The bluetooth mouse cannot connect after sleep mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: giacomo1998 F pulseaudio CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Fri Apr 27 09:49:41 2018 InstallationDate: Installed on 2017-04-13 (378 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to bionic on 2018-04-13 (13 days ago) dmi.bios.date: 07/27/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R08ET43W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FU001PMC dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR08ET43W(1.17):bd07/27/2016:svnLENOVO:pn20FU001PMC:pvrThinkPadL460:rvnLENOVO:rn20FU001PMC:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L460 dmi.product.name: 20FU001PMC dmi.product.version: ThinkPad L460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1767292/+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 1775187] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149221/+files/ProcInterrupts.txt -- 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/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 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 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1775187] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149219/+files/ProcCpuinfoMinimal.txt -- 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/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 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 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages P
[Kernel-packages] [Bug 1775187] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149222/+files/ProcModules.txt -- 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/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 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 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : k
[Kernel-packages] [Bug 1775187] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149220/+files/ProcEnviron.txt -- 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/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 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 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : k
[Kernel-packages] [Bug 1775187] Re: bluetooth headset gets imitatively disconnected
** Changed in: bluez (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: New Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 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 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages Mo
[Kernel-packages] [Bug 1775187] getfacl.txt
apport information ** Attachment added: "getfacl.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149224/+files/getfacl.txt -- 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/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 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 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-pa
[Kernel-packages] [Bug 1775187] rfkill.txt
apport information ** Attachment added: "rfkill.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149225/+files/rfkill.txt -- 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/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 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 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packa
[Kernel-packages] [Bug 1775187] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149215/+files/Dependencies.txt -- 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/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 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 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1775187] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149218/+files/ProcCpuinfo.txt -- 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/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 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 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : k
[Kernel-packages] [Bug 1775187] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149216/+files/Lspci.txt -- 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/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 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 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-package
[Kernel-packages] [Bug 1775187] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149217/+files/Lsusb.txt -- 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/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-11-09 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FWCTO1WW Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 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 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark _MarkForUpload: True dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FWCTO1WW dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1775187/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-package
[Kernel-packages] [Bug 1775187] Re: bluetooth headset gets imitatively disconnected
apport information ** Tags added: apport-collected bionic third-party-packages ** Description changed: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing the below) and since then my sennheiser pxc550 was immediately disconnected after a connect. Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8 Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an error: org.bluez.Error.InvalidArguments, Unable to handle new connection Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: org.bluez.Error.InvalidArguments Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete (0x0f) [...same message a few more time until I had a new version installed ...] I since then applied the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> https://marc.info/?l=linux-bluetooth&m=151801178209679&q=raw to bluez (apt source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now my headset works again. + --- + ApportVersion: 2.20.9-0ubuntu7.1 + Architecture: amd64 + CurrentDesktop: GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2017-11-09 (209 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) + InterestingModules: rfcomm bnep btusb bluetooth + MachineType: LENOVO 20FWCTO1WW + Package: bluez 5.48-0ubuntu3 + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=128d75b0-64fc-468a-95fc-0aaf631bf4fe ro rootflags=subvol=@ quiet splash cgroup_enable=memory swapaccount=1 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 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm bluetooth cdrom dip docker lpadmin plugdev sambashare sudo systemd-journal wireshark + _MarkForUpload: True + dmi.bios.date: 06/07/2016 + dmi.bios.vendor: LENOVO + dmi.bios.version: R07ET67W (2.07 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20FWCTO1WW + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40705 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FWCTO1WW:pvrThinkPadT460p:rvnLENOVO:rn20FWCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad T460p + dmi.product.name: 20FWCTO1WW + dmi.product.version: ThinkPad T460p + dmi.sys.vendor: LENOVO + hciconfig: + hci0:Type: Primary Bus: USB + BD Address: E4:A7:A0:14:18:46 ACL MTU: 1021:4 SCO MTU: 96:6 + UP RUNNING PSCAN ISCAN + RX bytes:4394393 acl:135 sco:0 events:618416 errors:0 + TX bytes:524957211 acl:614106 sco:0 commands:2823 errors:0 ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1775187/+attachment/5149214/+files/CurrentDmesg.txt -- 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/1775187 Title: bluetooth headset gets imitatively disconnected Status in bluez package in Ubuntu: Incomplete Bug description: I upgraded from artful to bionic (just run apt update && apt upgrade and rebooted before testing th
[Kernel-packages] [Bug 1775316] Re: add_key04 in LTP syscall test cause kernel oops (NULL pointer dereference) with T kernel
** Description changed: + [SRU Justification] + The assoc_array_insert_into_terminal_node function in lib/assoc_array.c in + the Linux kernel before 4.13.11 mishandles node splitting, which allows + local users to cause a denial of service (NULL pointer dereference and + panic) via a crafted application, as demonstrated by the keyring key type, + and key addition and link creation operations. + The "add_key04" from the LTP syscall tests will cause kernel oops on a testing node with Trusty kernel installed. And it will make incoming ssh connection hang (bug 1775158) + [Test Case] + This issue can easily be reproduced with the "add_key04" test from the LTP syscall test suite. + Steps (with root): - 1. sudo apt-get install git xfsprogs -y - 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git - 3. cd ltp - 4. make autotools - 5. ./configure - 6. make; make install - 7. cd /opt/ltp/testcases/bin - 8. ./add_key04 + 1. sudo apt-get install git -y + 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git + 3. cd ltp + 4. make autotools + 5. ./configure + 6. make; make install + 7. /opt/ltp/testcases/bin/add_key04 - Test result: + Test result before the patch: ubuntu@amaura:/opt/ltp/testcases/bin$ sudo ./add_key04 tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s add_key04.c:82: FAIL: kernel oops while filling keyring Summary: passed 0 failed 1 skipped 0 warnings 0 [52399.298894] BUG: unable to handle kernel NULL pointer dereference at 0010 [52399.298918] IP: [] assoc_array_apply_edit+0x67/0x110 - [52399.298938] PGD 800455a3a067 PUD 45725f067 PMD 0 - [52399.298952] Oops: 0002 [#1] SMP + [52399.298938] PGD 800455a3a067 PUD 45725f067 PMD 0 + [52399.298952] Oops: 0002 [#1] SMP [52399.298963] Modules linked in: cfg80211 ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt joydev hid_generic x86_pkg_temp_thermal coretemp kvm_intel kvm usbhid hid lpc_ich shpchp mac_hid crct10dif_pclmul crc32_pclmul i915_bdw ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper igb cryptd ahci dca ptp libahci pps_core intel_ips i2c_algo_bit drm_kms_helper video drm [52399.299100] CPU: 7 PID: 9559 Comm: add_key04 Not tainted 3.13.0-149-generic #199-Ubuntu [52399.299118] Hardware name: Intel Corporation S1200RP/S1200RP, BIOS S1200RP.86B.03.02.0003.070120151022 07/01/2015 [52399.299142] task: 880457b43000 ti: 88045a2e2000 task.ti: 88045a2e2000 [52399.299159] RIP: 0010:[] [] assoc_array_apply_edit+0x67/0x110 [52399.299182] RSP: 0018:88045a2e3df0 EFLAGS: 00010202 [52399.299194] RAX: 0010 RBX: 88045a2e3e78 RCX: [52399.299211] RDX: 88045a1d1741 RSI: 880456028880 RDI: 880456028800 [52399.299228] RBP: 88045a2e3df0 R08: 00016880 R09: 812dba97 [52399.299244] R10: 880460803c00 R11: ddf32900 R12: 880456f7f680 [52399.299261] R13: 88045a1d09c0 R14: R15: [52399.299278] FS: 7ff43fc39740() GS:8804704e() knlGS: [52399.299297] CS: 0010 DS: ES: CR0: 80050033 [52399.299311] CR2: 0010 CR3: 00045514c000 CR4: 00360770 [52399.299328] DR0: DR1: DR2: [52399.299344] DR3: DR6: fffe0ff0 DR7: 0400 [52399.299361] Stack: [52399.299366] 88045a2e3e08 812d7a33 88045a2e3e50 [52399.299387] 812d57a7 88045a1d0a30 88045a2e3e78 880456f7f681 [52399.299407] 3f01 880456f7f380 88045a1d09c0 880457b43000 [52399.299427] Call Trace: [52399.299436] [] __key_link+0x33/0x40 [52399.299450] [] __key_instantiate_and_link+0x87/0xf0 [52399.299467] [] key_create_or_update+0x32e/0x420 [52399.299482] [] SyS_add_key+0x110/0x210 [52399.299497] [] ? schedule_tail+0x5c/0xb0 [52399.299512] [] system_call_fastpath+0x1a/0x1f - [52399.299526] Code: 48 85 d2 74 0a 48 8b 8f e8 00 00 00 48 89 0a 48 83 c0 08 48 39 f0 75 e4 48 8b 87 00 01 00 00 48 85 c0 74 0a 48 8b 97 08 01 00 00 <48> 89 10 48 8b 87 10 01 00 00 48 85 c0 74 0a 48 8b 97 18 01 00 + [52399.299526] Code: 48 85 d2 74 0a 48 8b 8f e8 00 00 00 48 89 0a 48 83 c0 08 48 39 f0 75 e4 48 8b 87 00 01 00 00 48 85 c0 74 0a 48 8b 97 08 01 00 00 <48> 89 10 48 8b 87 10 01 00 00 48 85 c0 74 0a 48 8b 97 18 01 00 [52399.299625] RIP [] assoc_array_apply_edit+0x67/0x110 [52399.299642] RSP [52399.299650] CR2: 0010 [52399.302015] ---[ end trace 0f3e00901ea9f056 ]--- + + Test result after the patch: + $ sudo /opt/ltp/testcases/bin/add_key04 + tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s + add_key04.c:80: PASS: didn't crash while filling keyring + + Summary
[Kernel-packages] [Bug 1759961] Re: Update to 5.50 (mostly bug-fix release)
** Attachment added: "bluez_5.50.orig.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+attachment/5149238/+files/bluez_5.50.orig.tar.xz -- 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/1759961 Title: Update to bluez 5.50 (mostly bug-fix release) Status in bluez package in Ubuntu: In Progress Bug description: From upstream: http://www.bluez.org/release-of-bluez-5-49/ Release of BlueZ 5.49 This is mostly a bug fix release, with fixes to features such as AVCTP, OBEX, GATT and Mesh. There are however some notable new features also, such as improved heartbeat management support in meshctl as well as a new experimental ConnectDevice D-Bus method on the Adapter interface, which can be used for quick device object creation for testing purpose or when information about the device has been received over some Out-of-Band channel. Upstream changelog: https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog ver 5.49: Fix issue with configuring discoverable advertising flag. Fix issue with bearer selection and single mode controllers. Fix issue with Connect and ConnectProfile returning in progress. Fix issue with missing Paired property change when not bonded. Fix issue with storage for controllers without public address. Fix issue with handling AVCTP disconnecting the channel queue. Fix issue with not clearing connectable setting on power off. Fix issue with creating multiple mgmt socket instances. Fix issue with GATT server and BR/EDR only devices. Fix issue with InterfaceAdded event ordering. Add support for generic ConnectDevice method call. Add support for Mesh heartbeat client functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+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 1759961] Re: Update to 5.50 (mostly bug-fix release)
** Attachment added: "bluez_5.50-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+attachment/5149239/+files/bluez_5.50-0ubuntu1.debian.tar.xz -- 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/1759961 Title: Update to bluez 5.50 (mostly bug-fix release) Status in bluez package in Ubuntu: In Progress Bug description: From upstream: http://www.bluez.org/release-of-bluez-5-49/ Release of BlueZ 5.49 This is mostly a bug fix release, with fixes to features such as AVCTP, OBEX, GATT and Mesh. There are however some notable new features also, such as improved heartbeat management support in meshctl as well as a new experimental ConnectDevice D-Bus method on the Adapter interface, which can be used for quick device object creation for testing purpose or when information about the device has been received over some Out-of-Band channel. Upstream changelog: https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog ver 5.49: Fix issue with configuring discoverable advertising flag. Fix issue with bearer selection and single mode controllers. Fix issue with Connect and ConnectProfile returning in progress. Fix issue with missing Paired property change when not bonded. Fix issue with storage for controllers without public address. Fix issue with handling AVCTP disconnecting the channel queue. Fix issue with not clearing connectable setting on power off. Fix issue with creating multiple mgmt socket instances. Fix issue with GATT server and BR/EDR only devices. Fix issue with InterfaceAdded event ordering. Add support for generic ConnectDevice method call. Add support for Mesh heartbeat client functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+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 1759961] Re: Update to 5.50 (mostly bug-fix release)
** Attachment added: "bluez_5.50-0ubuntu1.dsc" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+attachment/5149240/+files/bluez_5.50-0ubuntu1.dsc ** Summary changed: - Update to 5.50 (mostly bug-fix release) + Update to bluez 5.50 (mostly bug-fix release) ** Tags added: bluez-5.50 -- 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/1759961 Title: Update to bluez 5.50 (mostly bug-fix release) Status in bluez package in Ubuntu: In Progress Bug description: From upstream: http://www.bluez.org/release-of-bluez-5-49/ Release of BlueZ 5.49 This is mostly a bug fix release, with fixes to features such as AVCTP, OBEX, GATT and Mesh. There are however some notable new features also, such as improved heartbeat management support in meshctl as well as a new experimental ConnectDevice D-Bus method on the Adapter interface, which can be used for quick device object creation for testing purpose or when information about the device has been received over some Out-of-Band channel. Upstream changelog: https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog ver 5.49: Fix issue with configuring discoverable advertising flag. Fix issue with bearer selection and single mode controllers. Fix issue with Connect and ConnectProfile returning in progress. Fix issue with missing Paired property change when not bonded. Fix issue with storage for controllers without public address. Fix issue with handling AVCTP disconnecting the channel queue. Fix issue with not clearing connectable setting on power off. Fix issue with creating multiple mgmt socket instances. Fix issue with GATT server and BR/EDR only devices. Fix issue with InterfaceAdded event ordering. Add support for generic ConnectDevice method call. Add support for Mesh heartbeat client functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+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 1774150] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1774150/+attachment/5149249/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774150 Title: 3.13.0-149-generic: suspend/resume issue on 14.04 Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04.5 LTS, the most recent kernel update to 3.13.0-149-generic means that my laptop (Acer Aspire V5) does not resume once suspended - all I get is a blank screen, unresponsive to keypresses, and I need to reboot. The 144 kernel is OK, and this question: https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04 suggests that 147 is OK too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774150/+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 1775217] Re: bluetooth controller fail after suspend with USB autosuspend on XPS 13 9360
I don't see any regression with this kernel and Bluetooth is working fine with USBautosuspend after a suspend. :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775217 Title: bluetooth controller fail after suspend with USB autosuspend on XPS 13 9360 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: More information here: https://bugzilla.redhat.com/show_bug.cgi?id=1514836 Patch: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git/commit/?id=596b07a9a22656493726edf1739569102bd3e136 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic 4.15.0.22.23 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guilhem2319 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jun 5 18:19:20 2018 HibernationDevice: RESUME=UUID=bfa874ab-9c2f-4228-9fd1-51267b4ea3c3 InstallationDate: Installed on 2018-02-26 (99 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:670c Microdia Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic root=UUID=287736d3-3b35-4262-a175-3254aa366f41 ro rootflags=subvol=@ quiet splash i915.enable_rc6=1 i915.enable_psr=2 i915.enable_guc_loading=1 i915.enable_guc_submission=1 i915.semaphores=1 i915.disable_power_well=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.2 dmi.board.name: 02PG84 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.2:bd02/26/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775217/+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 1774150] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1774150/+attachment/5149244/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774150 Title: 3.13.0-149-generic: suspend/resume issue on 14.04 Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04.5 LTS, the most recent kernel update to 3.13.0-149-generic means that my laptop (Acer Aspire V5) does not resume once suspended - all I get is a blank screen, unresponsive to keypresses, and I need to reboot. The 144 kernel is OK, and this question: https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04 suggests that 147 is OK too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774150/+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 1774150] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1774150/+attachment/5149246/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774150 Title: 3.13.0-149-generic: suspend/resume issue on 14.04 Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04.5 LTS, the most recent kernel update to 3.13.0-149-generic means that my laptop (Acer Aspire V5) does not resume once suspended - all I get is a blank screen, unresponsive to keypresses, and I need to reboot. The 144 kernel is OK, and this question: https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04 suggests that 147 is OK too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774150/+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 1774150] Re: 3.13.0-149-generic: suspend/resume issue on 14.04
ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bav2145 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=a9a9ea54-d360-476c-b598-fd19723969cf InstallationDate: Installed on 2014-07-24 (1412 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Shuttle Inc. DS437 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic root=UUID=8395af97-4ad8-4e0c-8fd4-ac1f64aaa902 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-149-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.01 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FS437 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.01:bd09/25/2013:svnShuttleInc.:pnDS437:pvrV1.0:rvnShuttleInc.:rnFS437:rvr1.0:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: DS437 dmi.product.version: V1.0 dmi.sys.vendor: Shuttle Inc. ** Tags added: apport-collected -- 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/1774150 Title: 3.13.0-149-generic: suspend/resume issue on 14.04 Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04.5 LTS, the most recent kernel update to 3.13.0-149-generic means that my laptop (Acer Aspire V5) does not resume once suspended - all I get is a blank screen, unresponsive to keypresses, and I need to reboot. The 144 kernel is OK, and this question: https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04 suggests that 147 is OK too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774150/+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 1774150] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1774150/+attachment/5149245/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774150 Title: 3.13.0-149-generic: suspend/resume issue on 14.04 Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04.5 LTS, the most recent kernel update to 3.13.0-149-generic means that my laptop (Acer Aspire V5) does not resume once suspended - all I get is a blank screen, unresponsive to keypresses, and I need to reboot. The 144 kernel is OK, and this question: https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04 suggests that 147 is OK too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774150/+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 1774150] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1774150/+attachment/5149247/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774150 Title: 3.13.0-149-generic: suspend/resume issue on 14.04 Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04.5 LTS, the most recent kernel update to 3.13.0-149-generic means that my laptop (Acer Aspire V5) does not resume once suspended - all I get is a blank screen, unresponsive to keypresses, and I need to reboot. The 144 kernel is OK, and this question: https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04 suggests that 147 is OK too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774150/+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 1774150] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1774150/+attachment/5149248/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774150 Title: 3.13.0-149-generic: suspend/resume issue on 14.04 Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04.5 LTS, the most recent kernel update to 3.13.0-149-generic means that my laptop (Acer Aspire V5) does not resume once suspended - all I get is a blank screen, unresponsive to keypresses, and I need to reboot. The 144 kernel is OK, and this question: https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04 suggests that 147 is OK too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774150/+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 1774150] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1774150/+attachment/5149243/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774150 Title: 3.13.0-149-generic: suspend/resume issue on 14.04 Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04.5 LTS, the most recent kernel update to 3.13.0-149-generic means that my laptop (Acer Aspire V5) does not resume once suspended - all I get is a blank screen, unresponsive to keypresses, and I need to reboot. The 144 kernel is OK, and this question: https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04 suggests that 147 is OK too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774150/+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 1774150] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1774150/+attachment/5149255/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774150 Title: 3.13.0-149-generic: suspend/resume issue on 14.04 Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04.5 LTS, the most recent kernel update to 3.13.0-149-generic means that my laptop (Acer Aspire V5) does not resume once suspended - all I get is a blank screen, unresponsive to keypresses, and I need to reboot. The 144 kernel is OK, and this question: https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04 suggests that 147 is OK too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774150/+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 1774150] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1774150/+attachment/5149258/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774150 Title: 3.13.0-149-generic: suspend/resume issue on 14.04 Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04.5 LTS, the most recent kernel update to 3.13.0-149-generic means that my laptop (Acer Aspire V5) does not resume once suspended - all I get is a blank screen, unresponsive to keypresses, and I need to reboot. The 144 kernel is OK, and this question: https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04 suggests that 147 is OK too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774150/+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 1774150] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1774150/+attachment/5149254/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774150 Title: 3.13.0-149-generic: suspend/resume issue on 14.04 Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04.5 LTS, the most recent kernel update to 3.13.0-149-generic means that my laptop (Acer Aspire V5) does not resume once suspended - all I get is a blank screen, unresponsive to keypresses, and I need to reboot. The 144 kernel is OK, and this question: https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04 suggests that 147 is OK too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774150/+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 1774150] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1774150/+attachment/5149257/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774150 Title: 3.13.0-149-generic: suspend/resume issue on 14.04 Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04.5 LTS, the most recent kernel update to 3.13.0-149-generic means that my laptop (Acer Aspire V5) does not resume once suspended - all I get is a blank screen, unresponsive to keypresses, and I need to reboot. The 144 kernel is OK, and this question: https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04 suggests that 147 is OK too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774150/+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 1774150] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1774150/+attachment/5149256/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774150 Title: 3.13.0-149-generic: suspend/resume issue on 14.04 Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04.5 LTS, the most recent kernel update to 3.13.0-149-generic means that my laptop (Acer Aspire V5) does not resume once suspended - all I get is a blank screen, unresponsive to keypresses, and I need to reboot. The 144 kernel is OK, and this question: https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04 suggests that 147 is OK too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774150/+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 1774150] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1774150/+attachment/5149253/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774150 Title: 3.13.0-149-generic: suspend/resume issue on 14.04 Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04.5 LTS, the most recent kernel update to 3.13.0-149-generic means that my laptop (Acer Aspire V5) does not resume once suspended - all I get is a blank screen, unresponsive to keypresses, and I need to reboot. The 144 kernel is OK, and this question: https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04 suggests that 147 is OK too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774150/+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 1774150] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1774150/+attachment/5149251/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774150 Title: 3.13.0-149-generic: suspend/resume issue on 14.04 Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04.5 LTS, the most recent kernel update to 3.13.0-149-generic means that my laptop (Acer Aspire V5) does not resume once suspended - all I get is a blank screen, unresponsive to keypresses, and I need to reboot. The 144 kernel is OK, and this question: https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04 suggests that 147 is OK too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774150/+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 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"
Maybe it's https://bugzilla.gnome.org/show_bug.cgi?id=789110 ? ** Bug watch added: GNOME Bug Tracker #789110 https://bugzilla.gnome.org/show_bug.cgi?id=789110 ** Bug watch added: GNOME Bug Tracker #789110 https://bugzilla.gnome.org/show_bug.cgi?id=789110 ** Changed in: gnome-bluetooth Importance: Medium => Unknown ** Changed in: gnome-bluetooth Status: Fix Released => Unknown ** No longer affects: bluez (Ubuntu) ** Also affects: gnome-shell via https://bugzilla.gnome.org/show_bug.cgi?id=789110 Importance: Unknown Status: Unknown ** No longer affects: gnome-control-center (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1738838 Title: Bluetooth icon shows "Off" and the only option given below it is "Turn Off" Status in GNOME Bluetooth: Unknown Status in GNOME Shell: Unknown Status in gnome-bluetooth package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: See video. I have installed bluetooth, blueman, bluez but it makes no difference to a broken interface to control bluetooth under Gnome 17.10, as shown in the attached video. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluetooth 5.46-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 17 22:32:30 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-18 (30 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: bnep btusb bluetooth MachineType: LENOVO 20BXCTO1WW PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash psmouse.synaptics_intertouch=0 vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET54WW (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1738838/+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 1774150] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1774150/+attachment/5149252/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774150 Title: 3.13.0-149-generic: suspend/resume issue on 14.04 Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04.5 LTS, the most recent kernel update to 3.13.0-149-generic means that my laptop (Acer Aspire V5) does not resume once suspended - all I get is a blank screen, unresponsive to keypresses, and I need to reboot. The 144 kernel is OK, and this question: https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04 suggests that 147 is OK too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774150/+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 1774150] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1774150/+attachment/5149250/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774150 Title: 3.13.0-149-generic: suspend/resume issue on 14.04 Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04.5 LTS, the most recent kernel update to 3.13.0-149-generic means that my laptop (Acer Aspire V5) does not resume once suspended - all I get is a blank screen, unresponsive to keypresses, and I need to reboot. The 144 kernel is OK, and this question: https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04 suggests that 147 is OK too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774150/+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 1774150] Re: 3.13.0-149-generic: suspend/resume issue on 14.04
This affects me too. No laptop here, but a Shuttle FS437. Used to work rock solid all the time. I ran apport-collect 1774150 succesfully. ** 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/1774150 Title: 3.13.0-149-generic: suspend/resume issue on 14.04 Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04.5 LTS, the most recent kernel update to 3.13.0-149-generic means that my laptop (Acer Aspire V5) does not resume once suspended - all I get is a blank screen, unresponsive to keypresses, and I need to reboot. The 144 kernel is OK, and this question: https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04 suggests that 147 is OK too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774150/+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 1774394] Re: fcntl35 / fcntl35_64 in LTP syscall test failed with T/X/X-LTS kernel
** Summary changed: - fcntl35 / fcntl35_64 in LTP syscall test failed with X/X-LTS kernel + fcntl35 / fcntl35_64 in LTP syscall test failed with T/X/X-LTS kernel -- 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/1774394 Title: fcntl35 / fcntl35_64 in LTP syscall test failed with T/X/X-LTS kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-lts-xenial package in Ubuntu: New Bug description: The "fcntl35" and "fcntl35_64" from the LTP syscall tests have failed on a testing node with X-LTS i386 kernel installed (they were not tested on amd64/arm64 because the test was not ready when the SRU starts). <>> tag=fcntl35 stime=1527764565 cmdline="fcntl35" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536 unexpectedly, expected 4096 fcntl35.c:101: PASS: a privileged user init the capacity of a pipe to 65536 successfully Summary: passed 1 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> <<>> tag=fcntl35_64 stime=1527764565 cmdline="fcntl35_64" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536 unexpectedly, expected 4096 fcntl35.c:101: PASS: a privileged user init the capacity of a pipe to 65536 successfully Summary: passed 1 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-128-generic 4.4.0-128.154~14.04.1 ProcVersionSignature: User Name 4.4.0-128.154~14.04.1-generic 4.4.131 Uname: Linux 4.4.0-128-generic i686 ApportVersion: 2.14.1-0ubuntu3.28 Architecture: i386 Date: Thu May 31 11:05:58 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1774394/+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 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
I'm affected by this bug, too. System is Acer E13 Laptop with 250G SSD, Intel Celeron N2940, 4GB RAM Initial and only install on this system was Ubuntu 16.04(where I had to insert a parameter into GRUB to prevent another system freeze bug to occur), uprgaded flawlessly to 17.10 and then to 18.04. And since the upgrade to 18.04, this bug, as extensively described above, with the same symptoms, was present. I fiddled a around a lot, with some hints directing me to either the fishy power management of the cpu (the above-mentioned, different bug, ostensibly originated from there) or the still-faulty new graphics driver, albeit I don't really know if that nouveau Graphics driver is even compatible with my Intel cpu graphics. What finally solved the bug for me was the above-recommended downgrade (via ukuu) to kernel 4.14 - so no I'm running 18.04 with Kernel 4.41.41 with this bug no longer occuring What's left to do now, I believe, is to klick away the kernel upgrade notifications and hoping for a fix in a newer kernel :) -- 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/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Confirmed Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+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 1775370] [NEW] request_key03 in LTP syscall test cause kernel oops with T kernel
Public bug reported: The "request_key03" from the LTP syscall tests will cause kernel oops with Trusty kernel. Steps (with root): 1. sudo apt-get install git xfsprogs -y 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git 3. cd ltp 4. make autotools 5. ./configure 6. make; make install 7. /opt/ltp/testcases/bin/request_key03 $ sudo /opt/ltp/testcases/bin/request_key03 tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s request_key03.c:158: FAIL: kernel oops while updating key of type 'encrypted' request_key03.c:168: PASS: didn't crash while requesting key of type 'encrypted' request_key03.c:158: FAIL: kernel oops while updating key of type 'trusted' request_key03.c:168: PASS: didn't crash while requesting key of type 'trusted' request_key03.c:154: PASS: didn't crash while updating key of type 'user' request_key03.c:168: PASS: didn't crash while requesting key of type 'user' Summary: passed 4 failed 2 skipped 0 warnings 0 [14180.795675] encrypted_key: keyword 'update' not allowed when called from .instantiate method [14180.796205] BUG: unable to handle kernel NULL pointer dereference at 0018 [14180.796230] IP: [] encrypted_update+0xa6/0x160 [14180.796248] PGD 80045383e067 PUD 4568c5067 PMD 0 [14180.796263] Oops: [#1] SMP [14180.796273] Modules linked in: ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt joydev hid_generic x86_pkg_temp_thermal coretemp kvm_intel kvm usbhid hid mac_hid lpc_ich shpchp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul i915_bdw glue_helper ablk_helper cryptd igb dca ptp ahci intel_ips pps_core libahci i2c_algo_bit drm_kms_helper drm video [14180.796407] CPU: 6 PID: 1888 Comm: request_key03 Not tainted 3.13.0-151-generic #201 [14180.796425] Hardware name: Intel Corporation S1200RP/S1200RP, BIOS S1200RP.86B.03.02.0003.070120151022 07/01/2015 [14180.796449] task: 880458463000 ti: 880454b16000 task.ti: 880454b16000 [14180.796466] RIP: 0010:[] [] encrypted_update+0xa6/0x160 [14180.796488] RSP: 0018:880454b17e18 EFLAGS: 00010246 [14180.796502] RAX: RBX: 880455db1a40 RCX: [14180.796518] RDX: 0005 RSI: 880455db1a4c RDI: 818400a3 [14180.796535] RBP: 880454b17e50 R08: R09: 880455db1a4f [14180.796552] R10: 0020 R11: 81388b44 R12: [14180.796568] R13: R14: 88045553a240 R15: 880455db1a47 [14180.796585] FS: 7faf78341740() GS:8804704c() knlGS: [14180.796604] CS: 0010 DS: ES: CR0: 80050033 [14180.796618] CR2: 0018 CR3: 0004550c8000 CR4: 00360770 [14180.796635] DR0: DR1: DR2: [14180.796652] DR3: DR6: fffe0ff0 DR7: 0400 [14180.796668] Stack: [14180.796674] 880455db1a47 88045553a240 88045553a260 [14180.796695] 880459c092c0 88045553a241 880458463000 880454b17f00 [14180.796715] 812d761b 0286 880459c09980 [14180.796735] Call Trace: [14180.796744] [] key_create_or_update+0x27b/0x420 [14180.796760] [] SyS_add_key+0x110/0x210 [14180.796775] [] system_call_fastpath+0x1a/0x1f [14180.796789] Code: 89 c7 e8 7e de 09 00 48 8d 55 c8 48 8d 75 d0 45 31 c0 31 c9 48 89 df e8 19 f3 ff ff 85 c0 41 89 c4 0f 88 88 00 00 00 4c 8b 7d c8 <49> 8b 75 18 4c 89 ff e8 fe f1 ff ff 85 c0 41 89 c4 78 71 49 8b [14180.796888] RIP [] encrypted_update+0xa6/0x160 [14180.796904] RSP [14180.796913] CR2: 0018 [14180.799331] ---[ end trace 4fc59232fdc581c7 ]--- [14180.805266] BUG: unable to handle kernel NULL pointer dereference at 0018 [14180.805303] IP: [] trusted_update+0x28/0x1e0 [14180.805334] PGD 80045a2b7067 PUD 45710b067 PMD 0 [14180.805361] Oops: [#2] SMP [14180.805379] Modules linked in: ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt joydev hid_generic x86_pkg_temp_thermal coretemp kvm_intel kvm usbhid hid mac_hid lpc_ich shpchp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul i915_bdw glue_helper ablk_helper cryptd igb dca ptp ahci intel_ips pps_core libahci i2c_algo_bit drm_kms_helper drm video [14180.806196] CPU: 6 PID: 1893 Comm: request_key03 Tainted: G D 3.13.0-151-generic #201 [14180.806881] Hardware name: Intel Corporation S1200RP/S1200RP, BIOS S1200RP.86B.03.02.0003.070120151022 07/01/2015 [14180.807578] task: 880455966000 ti: 880454004000 task.ti: 880454004000 [14180.808273] RIP: 0010:[] [] trusted_update+0x28/0x1e0 [14180.808970] RSP: 0018:880454005e18 EFLAGS: 00010286 [14180.809661] RAX: 812df6a0 RBX: 88045553a600 RC
[Kernel-packages] [Bug 1775372] [NEW] Unable to delete encrypted volume (barbican)
Public bug reported: Devstack isntallation , local cinder LVM + babbican. Managed to create an encrypted volume but when trying to delete the volume with admin tenants, action fails with Error : Delete for volume a1bc0685-81e9-44e8-8965-323c402139e7 failed: Invalid volume: Unable to delete encryption key for volume. (HTTP 400) (Request-ID: req-1b715dad-c9ce-4422-a506-191f84bc7d9e) ERROR: Unable to delete any of the specified volumes. Here are the errors: /opt/stack/logs/barbican.log:66:2018-06-06 08:29:51.683 ERROR barbican.api.controllers [req-101bb298-6d7c-485d-91ad-3c185ece5e04 demo admin] Secret deletion attempt not allowed - please review your user/project privileges: PolicyNotAuthorized: secret:delete is disallowed by policy /opt/stack/logs/barbican.log:70:2018-06-06 08:29:51.861 ERROR barbican.api.controllers [req-850f78ef-c7ed-416a-8042-c1f0fd80c233 service cinder] Secret deletion attempt not allowed - please review your user/project privileges: PolicyNotAuthorized: secret:delete is disallowed by policy ** Affects: cinder Importance: Undecided Status: New ** Attachment added: "barbican logs" https://bugs.launchpad.net/bugs/1775372/+attachment/5149290/+files/barbican.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775372 Title: Unable to delete encrypted volume (barbican) Status in Cinder: New Bug description: Devstack isntallation , local cinder LVM + babbican. Managed to create an encrypted volume but when trying to delete the volume with admin tenants, action fails with Error : Delete for volume a1bc0685-81e9-44e8-8965-323c402139e7 failed: Invalid volume: Unable to delete encryption key for volume. (HTTP 400) (Request-ID: req-1b715dad-c9ce-4422-a506-191f84bc7d9e) ERROR: Unable to delete any of the specified volumes. Here are the errors: /opt/stack/logs/barbican.log:66:2018-06-06 08:29:51.683 ERROR barbican.api.controllers [req-101bb298-6d7c-485d-91ad-3c185ece5e04 demo admin] Secret deletion attempt not allowed - please review your user/project privileges: PolicyNotAuthorized: secret:delete is disallowed by policy /opt/stack/logs/barbican.log:70:2018-06-06 08:29:51.861 ERROR barbican.api.controllers [req-850f78ef-c7ed-416a-8042-c1f0fd80c233 service cinder] Secret deletion attempt not allowed - please review your user/project privileges: PolicyNotAuthorized: secret:delete is disallowed by policy To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1775372/+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 1775372] Re: Unable to delete encrypted volume (barbican)
Latest devstack queens. ** Package changed: linux (Ubuntu) => cinder -- 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/1775372 Title: Unable to delete encrypted volume (barbican) Status in Cinder: New Bug description: Devstack isntallation , local cinder LVM + babbican. Managed to create an encrypted volume but when trying to delete the volume with admin tenants, action fails with Error : Delete for volume a1bc0685-81e9-44e8-8965-323c402139e7 failed: Invalid volume: Unable to delete encryption key for volume. (HTTP 400) (Request-ID: req-1b715dad-c9ce-4422-a506-191f84bc7d9e) ERROR: Unable to delete any of the specified volumes. Here are the errors: /opt/stack/logs/barbican.log:66:2018-06-06 08:29:51.683 ERROR barbican.api.controllers [req-101bb298-6d7c-485d-91ad-3c185ece5e04 demo admin] Secret deletion attempt not allowed - please review your user/project privileges: PolicyNotAuthorized: secret:delete is disallowed by policy /opt/stack/logs/barbican.log:70:2018-06-06 08:29:51.861 ERROR barbican.api.controllers [req-850f78ef-c7ed-416a-8042-c1f0fd80c233 service cinder] Secret deletion attempt not allowed - please review your user/project privileges: PolicyNotAuthorized: secret:delete is disallowed by policy To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1775372/+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 1775370] Re: request_key03 in LTP syscall test cause kernel oops with T kernel
This might be related to CVE-2017-15299 and CVE-2017-15951 But from our CVE tracker, CVE-2017-15951 has gone (and not affecting Trusty), I will mark this as affected by CVE-2017-15299 only. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15299 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15951 -- 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/1775370 Title: request_key03 in LTP syscall test cause kernel oops with T kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: The "request_key03" from the LTP syscall tests will cause kernel oops with Trusty kernel. Steps (with root): 1. sudo apt-get install git xfsprogs -y 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git 3. cd ltp 4. make autotools 5. ./configure 6. make; make install 7. /opt/ltp/testcases/bin/request_key03 $ sudo /opt/ltp/testcases/bin/request_key03 tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s request_key03.c:158: FAIL: kernel oops while updating key of type 'encrypted' request_key03.c:168: PASS: didn't crash while requesting key of type 'encrypted' request_key03.c:158: FAIL: kernel oops while updating key of type 'trusted' request_key03.c:168: PASS: didn't crash while requesting key of type 'trusted' request_key03.c:154: PASS: didn't crash while updating key of type 'user' request_key03.c:168: PASS: didn't crash while requesting key of type 'user' Summary: passed 4 failed 2 skipped 0 warnings 0 [14180.795675] encrypted_key: keyword 'update' not allowed when called from .instantiate method [14180.796205] BUG: unable to handle kernel NULL pointer dereference at 0018 [14180.796230] IP: [] encrypted_update+0xa6/0x160 [14180.796248] PGD 80045383e067 PUD 4568c5067 PMD 0 [14180.796263] Oops: [#1] SMP [14180.796273] Modules linked in: ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt joydev hid_generic x86_pkg_temp_thermal coretemp kvm_intel kvm usbhid hid mac_hid lpc_ich shpchp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul i915_bdw glue_helper ablk_helper cryptd igb dca ptp ahci intel_ips pps_core libahci i2c_algo_bit drm_kms_helper drm video [14180.796407] CPU: 6 PID: 1888 Comm: request_key03 Not tainted 3.13.0-151-generic #201 [14180.796425] Hardware name: Intel Corporation S1200RP/S1200RP, BIOS S1200RP.86B.03.02.0003.070120151022 07/01/2015 [14180.796449] task: 880458463000 ti: 880454b16000 task.ti: 880454b16000 [14180.796466] RIP: 0010:[] [] encrypted_update+0xa6/0x160 [14180.796488] RSP: 0018:880454b17e18 EFLAGS: 00010246 [14180.796502] RAX: RBX: 880455db1a40 RCX: [14180.796518] RDX: 0005 RSI: 880455db1a4c RDI: 818400a3 [14180.796535] RBP: 880454b17e50 R08: R09: 880455db1a4f [14180.796552] R10: 0020 R11: 81388b44 R12: [14180.796568] R13: R14: 88045553a240 R15: 880455db1a47 [14180.796585] FS: 7faf78341740() GS:8804704c() knlGS: [14180.796604] CS: 0010 DS: ES: CR0: 80050033 [14180.796618] CR2: 0018 CR3: 0004550c8000 CR4: 00360770 [14180.796635] DR0: DR1: DR2: [14180.796652] DR3: DR6: fffe0ff0 DR7: 0400 [14180.796668] Stack: [14180.796674] 880455db1a47 88045553a240 88045553a260 [14180.796695] 880459c092c0 88045553a241 880458463000 880454b17f00 [14180.796715] 812d761b 0286 880459c09980 [14180.796735] Call Trace: [14180.796744] [] key_create_or_update+0x27b/0x420 [14180.796760] [] SyS_add_key+0x110/0x210 [14180.796775] [] system_call_fastpath+0x1a/0x1f [14180.796789] Code: 89 c7 e8 7e de 09 00 48 8d 55 c8 48 8d 75 d0 45 31 c0 31 c9 48 89 df e8 19 f3 ff ff 85 c0 41 89 c4 0f 88 88 00 00 00 4c 8b 7d c8 <49> 8b 75 18 4c 89 ff e8 fe f1 ff ff 85 c0 41 89 c4 78 71 49 8b [14180.796888] RIP [] encrypted_update+0xa6/0x160 [14180.796904] RSP [14180.796913] CR2: 0018 [14180.799331] ---[ end trace 4fc59232fdc581c7 ]--- [14180.805266] BUG: unable to handle kernel NULL pointer dereference at 0018 [14180.805303] IP: [] trusted_update+0x28/0x1e0 [14180.805334] PGD 80045a2b7067 PUD 45710b067 PMD 0 [14180.805361] Oops: [#2] SMP [14180.805379] Modules linked in: ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt j
[Kernel-packages] [Bug 1775370] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775370 Title: request_key03 in LTP syscall test cause kernel oops with T kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: The "request_key03" from the LTP syscall tests will cause kernel oops with Trusty kernel. Steps (with root): 1. sudo apt-get install git xfsprogs -y 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git 3. cd ltp 4. make autotools 5. ./configure 6. make; make install 7. /opt/ltp/testcases/bin/request_key03 $ sudo /opt/ltp/testcases/bin/request_key03 tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s request_key03.c:158: FAIL: kernel oops while updating key of type 'encrypted' request_key03.c:168: PASS: didn't crash while requesting key of type 'encrypted' request_key03.c:158: FAIL: kernel oops while updating key of type 'trusted' request_key03.c:168: PASS: didn't crash while requesting key of type 'trusted' request_key03.c:154: PASS: didn't crash while updating key of type 'user' request_key03.c:168: PASS: didn't crash while requesting key of type 'user' Summary: passed 4 failed 2 skipped 0 warnings 0 [14180.795675] encrypted_key: keyword 'update' not allowed when called from .instantiate method [14180.796205] BUG: unable to handle kernel NULL pointer dereference at 0018 [14180.796230] IP: [] encrypted_update+0xa6/0x160 [14180.796248] PGD 80045383e067 PUD 4568c5067 PMD 0 [14180.796263] Oops: [#1] SMP [14180.796273] Modules linked in: ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt joydev hid_generic x86_pkg_temp_thermal coretemp kvm_intel kvm usbhid hid mac_hid lpc_ich shpchp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul i915_bdw glue_helper ablk_helper cryptd igb dca ptp ahci intel_ips pps_core libahci i2c_algo_bit drm_kms_helper drm video [14180.796407] CPU: 6 PID: 1888 Comm: request_key03 Not tainted 3.13.0-151-generic #201 [14180.796425] Hardware name: Intel Corporation S1200RP/S1200RP, BIOS S1200RP.86B.03.02.0003.070120151022 07/01/2015 [14180.796449] task: 880458463000 ti: 880454b16000 task.ti: 880454b16000 [14180.796466] RIP: 0010:[] [] encrypted_update+0xa6/0x160 [14180.796488] RSP: 0018:880454b17e18 EFLAGS: 00010246 [14180.796502] RAX: RBX: 880455db1a40 RCX: [14180.796518] RDX: 0005 RSI: 880455db1a4c RDI: 818400a3 [14180.796535] RBP: 880454b17e50 R08: R09: 880455db1a4f [14180.796552] R10: 0020 R11: 81388b44 R12: [14180.796568] R13: R14: 88045553a240 R15: 880455db1a47 [14180.796585] FS: 7faf78341740() GS:8804704c() knlGS: [14180.796604] CS: 0010 DS: ES: CR0: 80050033 [14180.796618] CR2: 0018 CR3: 0004550c8000 CR4: 00360770 [14180.796635] DR0: DR1: DR2: [14180.796652] DR3: DR6: fffe0ff0 DR7: 0400 [14180.796668] Stack: [14180.796674] 880455db1a47 88045553a240 88045553a260 [14180.796695] 880459c092c0 88045553a241 880458463000 880454b17f00 [14180.796715] 812d761b 0286 880459c09980 [14180.796735] Call Trace: [14180.796744] [] key_create_or_update+0x27b/0x420 [14180.796760] [] SyS_add_key+0x110/0x210 [14180.796775] [] system_call_fastpath+0x1a/0x1f [14180.796789] Code: 89 c7 e8 7e de 09 00 48 8d 55 c8 48 8d 75 d0 45 31 c0 31 c9 48 89 df e8 19 f3 ff ff 85 c0 41 89 c4 0f 88 88 00 00 00 4c 8b 7d c8 <49> 8b 75 18 4c 89 ff e8 fe f1 ff ff 85 c0 41 89 c4 78 71 49 8b [14180.796888] RIP [] encrypted_update+0xa6/0x160 [14180.796904] RSP [14180.796913] CR2: 0018 [14180.799331] ---[ end trace 4fc59232fdc581c7 ]--- [14180.805266] BUG: unable to handle kernel NULL pointer dereference at 0018 [14180.805303] IP: [] trusted_update+0x28/0x1e0 [14180.805334] PGD 80045a2b7067 PUD 45710b067 PMD 0 [14180.805361] Oops: [#2] SMP [14180.805379] Modules linked in: ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt joydev hid_generic x86_pkg_temp_thermal coretemp kvm_intel kvm usbhid hid mac_hid lpc_ich shpchp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul i915_bdw glue_helper ablk_helper cryptd igb dca ptp ahci i
[Kernel-packages] [Bug 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29
Update to #138: My problem seems to be related to Bug #1752053 and Bug #1773113. And for me now everything more or less works again by using this workaround from Bug #1752053 posting #123: -snip I found a silly workaround (after trying many many other suggestions / driver re-installs), now using nvidia-driver-396 or nvidia-driver-390; create (if not exists) a file /etc/rc.local, with this content: #!/bin/bash sleep 1 exit 0 And make it executable: chmod 755 /etc/rc.local -snip Maybe this helps some people. -- 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/1743094 Title: [regression] hibernation (freezes on resume) since 4.13.0-25.29 Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: After hibernating the system and than resuming it the system reboots notifying that it is resuming and than stops/freezes. The system does not respond to anything (no tty's other notifying textg are available). After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep functions as proposed. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jb 1717 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478 InstallationDate: Installed on 2017-12-10 (34 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: Acer Aspire S3-391 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-26-generic N/A linux-backports-modules-4.13.0-26-generic N/A linux-firmware 1.157.14 Tags: sylvia Uname: Linux 4.13.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/31/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Hummingbird2 dmi.board.vendor: Acer dmi.board.version: V2.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S3-391 dmi.product.version: V2.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/+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 1775378] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775378 Title: fanotify06 in LTP syscall test failed with T kernel Status in linux package in Ubuntu: Confirmed Bug description: The "fanotify06" from the LTP syscall tests has failed on a testing node with T kernel installed. Steps (with root): 1. sudo apt-get install git xfsprogs -y 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git 3. cd ltp 4. make autotools 5. ./configure 6. make; make install 7. /opt/ltp/testcases/bin/fanotify06 <<>> tag=fanotify06 stime=1528269991 cmdline="fanotify06" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fanotify06.c:147: PASS: group 0 get event: mask 2 pid=22619 fd=29 fanotify06.c:147: PASS: group 1 get event: mask 2 pid=22619 fd=29 fanotify06.c:147: PASS: group 2 get event: mask 2 pid=22619 fd=29 fanotify06.c:197: FAIL: group 3 got event fanotify06.c:197: FAIL: group 4 got event fanotify06.c:197: FAIL: group 5 got event fanotify06.c:208: PASS: group 6 got no event fanotify06.c:208: PASS: group 7 got no event fanotify06.c:197: FAIL: group 8 got event Summary: passed 5 failed 4 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-149-generic 3.13.0-149.199 ProcVersionSignature: User Name 3.13.0-149.199-generic 3.13.11-ckt39 Uname: Linux 3.13.0-149-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 6 10:09 seq crw-rw 1 root audio 116, 33 Jun 6 10:09 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [3.472391] init: plymouth-upstart-bridge main process ended, respawning Date: Wed Jun 6 10:12:15 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775378/+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 1775378] [NEW] fanotify06 in LTP syscall test failed with T kernel
Public bug reported: The "fanotify06" from the LTP syscall tests has failed on a testing node with T kernel installed. Steps (with root): 1. sudo apt-get install git xfsprogs -y 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git 3. cd ltp 4. make autotools 5. ./configure 6. make; make install 7. /opt/ltp/testcases/bin/fanotify06 <<>> tag=fanotify06 stime=1528269991 cmdline="fanotify06" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fanotify06.c:147: PASS: group 0 get event: mask 2 pid=22619 fd=29 fanotify06.c:147: PASS: group 1 get event: mask 2 pid=22619 fd=29 fanotify06.c:147: PASS: group 2 get event: mask 2 pid=22619 fd=29 fanotify06.c:197: FAIL: group 3 got event fanotify06.c:197: FAIL: group 4 got event fanotify06.c:197: FAIL: group 5 got event fanotify06.c:208: PASS: group 6 got no event fanotify06.c:208: PASS: group 7 got no event fanotify06.c:197: FAIL: group 8 got event Summary: passed 5 failed 4 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-149-generic 3.13.0-149.199 ProcVersionSignature: User Name 3.13.0-149.199-generic 3.13.11-ckt39 Uname: Linux 3.13.0-149-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 6 10:09 seq crw-rw 1 root audio 116, 33 Jun 6 10:09 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [3.472391] init: plymouth-upstart-bridge main process ended, respawning Date: Wed Jun 6 10:12:15 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty uec-images -- 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/1775378 Title: fanotify06 in LTP syscall test failed with T kernel Status in linux package in Ubuntu: New Bug description: The "fanotify06" from the LTP syscall tests has failed on a testing node with T kernel installed. Steps (with root): 1. sudo apt-get install git xfsprogs -y 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git 3. cd ltp 4. make autotools 5. ./configure 6. make; make install 7. /opt/ltp/testcases/bin/fanotify06 <<>> tag=fanotify06 stime=1528269991 cmdline="fanotify06" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fanotify06.c:147: PASS: group 0 get event: mask 2 pid=22619 fd=29 fanotify06.c:147: PASS: group 1 get event: mask 2 pid=22619 fd=29 fanotify06.c:147: PASS: group 2 get event: mask 2 pid=22619 fd=29 fanotify06.c:197: FAIL: group 3 got event fanotify06.c:197: FAIL: group 4 got event fanotify06.c:197: FAIL: group 5 got event fanotify06.c:208: PASS: group 6 got no event fanotify06.c:208: PASS: group 7 got no event fanotify06.c:197: FAIL: group 8 got event Summary: passed 5 failed 4 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-149-gen
[Kernel-packages] [Bug 1775378] Re: fanotify06 in LTP syscall test failed with T kernel
This issue cannot be reproduced with Trusty ppc64le and ARM64 ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Tags added: i386 -- 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/1775378 Title: fanotify06 in LTP syscall test failed with T kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: The "fanotify06" from the LTP syscall tests has failed on a testing node with T kernel installed. Steps (with root): 1. sudo apt-get install git xfsprogs -y 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git 3. cd ltp 4. make autotools 5. ./configure 6. make; make install 7. /opt/ltp/testcases/bin/fanotify06 <<>> tag=fanotify06 stime=1528269991 cmdline="fanotify06" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fanotify06.c:147: PASS: group 0 get event: mask 2 pid=22619 fd=29 fanotify06.c:147: PASS: group 1 get event: mask 2 pid=22619 fd=29 fanotify06.c:147: PASS: group 2 get event: mask 2 pid=22619 fd=29 fanotify06.c:197: FAIL: group 3 got event fanotify06.c:197: FAIL: group 4 got event fanotify06.c:197: FAIL: group 5 got event fanotify06.c:208: PASS: group 6 got no event fanotify06.c:208: PASS: group 7 got no event fanotify06.c:197: FAIL: group 8 got event Summary: passed 5 failed 4 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-149-generic 3.13.0-149.199 ProcVersionSignature: User Name 3.13.0-149.199-generic 3.13.11-ckt39 Uname: Linux 3.13.0-149-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 6 10:09 seq crw-rw 1 root audio 116, 33 Jun 6 10:09 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [3.472391] init: plymouth-upstart-bridge main process ended, respawning Date: Wed Jun 6 10:12:15 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1775378/+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 1775165] Re: fanotify07/fanotify08 in LTP syscall test generates kernel trace with T kernel
** Summary changed: - fanotify07 in LTP syscall test generates kernel trace with T kernel + fanotify07/fanotify08 in LTP syscall test generates kernel trace with T kernel ** Description changed: - The "fanotify07" from the LTP syscall tests has failed on a testing node - with Trusty kernel installed. + The "fanotify07" and "fanotify08" from the LTP syscall tests has failed + on a testing node with Trusty kernel installed. Steps (with root): - 1. sudo apt-get install git xfsprogs -y - 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git - 3. cd ltp - 4. make autotools - 5. ./configure - 6. make; make install - 7. cd /opt/ltp - 8. echo "fanotify07 fanotify07" > /tmp/jobs - 9. ./runltp -f /tmp/jobs + 1. sudo apt-get install git xfsprogs -y + 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git + 3. cd ltp + 4. make autotools + 5. ./configure + 6. make; make install + 7. cd /opt/ltp + 8. echo -e "fanotify07 fanotify07 \nfanotify08 fanotify08" > /tmp/jobs + 9. ./runltp -f /tmp/jobs <<>> tag=fanotify07 stime=1528197132 cmdline="fanotify07" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Cannot kill test processes! Congratulation, likely test hit a kernel bug. Exitting uncleanly... <<>> initiation_status="ok" duration=350 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> INFO: ltp-pan reported some tests FAIL LTP Version: 20180515 [ 841.063676] INFO: task fanotify07:3660 blocked for more than 120 seconds. [ 841.063692] Not tainted 3.13.0-149-generic #199-Ubuntu [ 841.063705] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 841.063723] fanotify07 D 8804584742f0 0 3660 3652 0x [ 841.063724] 880459e9bd00 0086 88045556b000 00013b00 [ 841.063726] 880459e9bfd8 00013b00 88045556b000 880459b4e690 [ 841.063728] 880458474200 8804584742f0 0002 [ 841.063730] Call Trace: [ 841.063731] [] schedule+0x29/0x70 [ 841.063733] [] fanotify_handle_event+0x110/0x1d0 [ 841.063735] [] ? prepare_to_wait_event+0x100/0x100 [ 841.063737] [] send_to_group+0x166/0x240 [ 841.063738] [] ? touch_atime+0x71/0x140 [ 841.063740] [] fsnotify+0x2e5/0x320 [ 841.063742] [] security_file_permission+0x94/0xb0 [ 841.063743] [] rw_verify_area+0x52/0xd0 [ 841.063745] [] vfs_read+0x6a/0x160 [ 841.063746] [] SyS_read+0x49/0xa0 [ 841.063748] [] system_call_fastpath+0x1a/0x1f [ 1304.848642] ltp-pan[3809]: segfault at 0 ip 7f07c8aafdfa sp 7ffc1da92078 error 4 in libc-2.19.so[7f07c8a27000+1be000] dmesg: http://paste.ubuntu.com/p/FRZnV5smGh/ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-149-generic 3.13.0-149.199 ProcVersionSignature: User Name 3.13.0-149.199-generic 3.13.11-ckt39 Uname: Linux 3.13.0-149-generic x86_64 AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Jun 5 11:01 seq - crw-rw 1 root audio 116, 33 Jun 5 11:01 timer + total 0 + crw-rw 1 root audio 116, 1 Jun 5 11:01 seq + crw-rw 1 root audio 116, 33 Jun 5 11:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [3.553366] init: plymouth-upstart-bridge main process ended, respawning Date: Tue Jun 5 11:06:45 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: - + ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: - linux-restricted-modules-3.13.0-149-generic N/A - linux-backports-modules-3.13.0-149-generic N/A - linux-firmware 1.127.24 + linux-restricted-modules-3.13.0-149-generic N/A + linux-backports-modules-3.13.0-149-generic N/A + linux-firmware 1.127.24 RfKi
[Kernel-packages] [Bug 1774883] Re: GPF using CIFS and ACQ107 under heavy use
Arch has aslo the same issue, looks like some kernel bug: https://bugs.archlinux.org/task/57474 -- 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/1774883 Title: GPF using CIFS and ACQ107 under heavy use Status in linux package in Ubuntu: Confirmed Bug description: using aquanta 10GBE ethernet I get a GPF when scanning CIFS-mounted library, works fine using 1GBE intel nic. GPF follows: Jun 2 12:55:28 klimt kernel: [ 2112.707816] general protection fault: [#1] SMP PTI Jun 2 12:55:28 klimt kernel: [ 2112.709215] Modules linked in: cmac md4 nls_utf8 cifs ccm fscache binfmt_misc snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp ar c4 kvm_intel iwlmvm kvm snd_hda_codec_realtek irqbypass snd_hda_codec_generic mac80211 intel_cstate iwlwifi intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core cfg80211 intel_wmi_thunde rbolt mxm_wmi snd_hwdep snd_pcm snd_timer snd soundcore mei_me ioatdma mei shpchp wmi mac_hid nvidia_uvm(POE) sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear r aid1 nvidia_drm(POE) nvidia_modeset(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel Jun 2 12:55:28 klimt kernel: [ 2112.728235] pcbc nvidia(POE) aesni_intel aes_x86_64 crypto_simd glue_helper cryptd drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm ipmi_dev intf ipmi_msghandler igb e1000e nvme dca nvme_core i2c_algo_bit atlantic ptp pps_core ahci libahci Jun 2 12:55:28 klimt kernel: [ 2112.734257] CPU: 8 PID: 1499 Comm: EmbyServer Tainted: P OE4.15.0-22-generic #24-Ubuntu Jun 2 12:55:28 klimt kernel: [ 2112.736705] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X299 Professional Gaming i9 XE, BIOS P1.00 09/28/2017 Jun 2 12:55:28 klimt kernel: [ 2112.739735] RIP: 0010:prefetch_freepointer+0x15/0x30 Jun 2 12:55:28 klimt kernel: [ 2112.741050] RSP: 0018:aa9a0823bd20 EFLAGS: 00010206 Jun 2 12:55:28 klimt kernel: [ 2112.742434] RAX: RBX: 217a77ddff956e69 RCX: 8789 Jun 2 12:55:28 klimt kernel: [ 2112.744329] RDX: 8788 RSI: 217a77ddff956e69 RDI: 9da1d110ab80 Jun 2 12:55:28 klimt kernel: [ 2112.746222] RBP: aa9a0823bd20 R08: ca99fe822eb0 R09: 9da1d31275a0 Jun 2 12:55:28 klimt kernel: [ 2112.748113] R10: 0007fcbd8002 R11: 9da1ca4d9e00 R12: 014000c0 Jun 2 12:55:28 klimt kernel: [ 2112.750006] R13: 9da1ddc04780 R14: 9da1ca4d9000 R15: 9da1d110ab80 Jun 2 12:55:28 klimt kernel: [ 2112.794382] FS: 7fcc33fff700() GS:9da1de40() knlGS: Jun 2 12:55:28 klimt kernel: [ 2112.884578] CS: 0010 DS: ES: CR0: 80050033 Jun 2 12:55:28 klimt kernel: [ 2112.930582] CR2: 7fcc7e5bf000 CR3: 002012cdc006 CR4: 003606e0 Jun 2 12:55:28 klimt kernel: [ 2112.976554] DR0: DR1: DR2: Jun 2 12:55:28 klimt kernel: [ 2113.021459] DR3: DR6: fffe0ff0 DR7: 0400 Jun 2 12:55:28 klimt kernel: [ 2113.064959] Call Trace: Jun 2 12:55:28 klimt kernel: [ 2113.106986] kmem_cache_alloc+0xa2/0x1b0 Jun 2 12:55:28 klimt kernel: [ 2113.148571] ? anon_vma_fork+0x97/0x130 Jun 2 12:55:28 klimt kernel: [ 2113.189139] anon_vma_fork+0x97/0x130 Jun 2 12:55:28 klimt kernel: [ 2113.228632] copy_process.part.35+0xdce/0x1af0 Jun 2 12:55:28 klimt kernel: [ 2113.267459] _do_fork+0xdf/0x400 Jun 2 12:55:28 klimt kernel: [ 2113.305090] ? get_unused_fd_flags+0x30/0x40 Jun 2 12:55:28 klimt kernel: [ 2113.342027] SyS_clone+0x19/0x20 Jun 2 12:55:28 klimt kernel: [ 2113.377704] do_syscall_64+0x73/0x130 Jun 2 12:55:28 klimt kernel: [ 2113.412455] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jun 2 12:55:28 klimt kernel: [ 2113.446867] RIP: 0033:0x7fcd1de5ab1c Jun 2 12:55:28 klimt kernel: [ 2113.480134] RSP: 002b:7fcc33ffb630 EFLAGS: 0246 ORIG_RAX: 0038 Jun 2 12:55:28 klimt kernel: [ 2113.546601] RAX: ffda RBX: 7fcc33ffb630 RCX: 7fcd1de5ab1c Jun 2 12:55:28 klimt kernel: [ 2113.581224] RDX: RSI: RDI: 01200011 Jun 2 12:55:28 klimt kernel: [ 2113.615346] RBP: 7fcc33ffb6a0 R08: 7fcc33fff700 R09: Jun 2 12:55:28 klimt kernel: [ 2113.648651] R10: 7fcc33fff9d0 R11: 0246 R12: Jun 2 12:55:28 klimt kernel: [ 2113.681308] R13: 0020 R14: 0001 R15: 7fcc281345f0 Jun 2 12:55:28 klimt kernel: [ 2113.713887] Code: eb bb 49 8b 74 24 60 48 c7 c7 08 b2 8e b8 e8 53
[Kernel-packages] [Bug 1774883] Re: GPF using CIFS and ACQ107 under heavy use
I have similar problem at my LAN on some PC running ubuntu 18.04: Jun 6 08:04:05 hostname kernel: [173372.298108]general protection fault: [#1] SMP PTI Jun 6 08:04:05 hostname kernel: [173372.298180] CPU: 1 PID: 8954 Comm: cifsd Not tainted 4.15.0-20-generic #21-Ubuntu The problem seems to be appear randomly. -- 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/1774883 Title: GPF using CIFS and ACQ107 under heavy use Status in linux package in Ubuntu: Confirmed Bug description: using aquanta 10GBE ethernet I get a GPF when scanning CIFS-mounted library, works fine using 1GBE intel nic. GPF follows: Jun 2 12:55:28 klimt kernel: [ 2112.707816] general protection fault: [#1] SMP PTI Jun 2 12:55:28 klimt kernel: [ 2112.709215] Modules linked in: cmac md4 nls_utf8 cifs ccm fscache binfmt_misc snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp ar c4 kvm_intel iwlmvm kvm snd_hda_codec_realtek irqbypass snd_hda_codec_generic mac80211 intel_cstate iwlwifi intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core cfg80211 intel_wmi_thunde rbolt mxm_wmi snd_hwdep snd_pcm snd_timer snd soundcore mei_me ioatdma mei shpchp wmi mac_hid nvidia_uvm(POE) sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear r aid1 nvidia_drm(POE) nvidia_modeset(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel Jun 2 12:55:28 klimt kernel: [ 2112.728235] pcbc nvidia(POE) aesni_intel aes_x86_64 crypto_simd glue_helper cryptd drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm ipmi_dev intf ipmi_msghandler igb e1000e nvme dca nvme_core i2c_algo_bit atlantic ptp pps_core ahci libahci Jun 2 12:55:28 klimt kernel: [ 2112.734257] CPU: 8 PID: 1499 Comm: EmbyServer Tainted: P OE4.15.0-22-generic #24-Ubuntu Jun 2 12:55:28 klimt kernel: [ 2112.736705] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X299 Professional Gaming i9 XE, BIOS P1.00 09/28/2017 Jun 2 12:55:28 klimt kernel: [ 2112.739735] RIP: 0010:prefetch_freepointer+0x15/0x30 Jun 2 12:55:28 klimt kernel: [ 2112.741050] RSP: 0018:aa9a0823bd20 EFLAGS: 00010206 Jun 2 12:55:28 klimt kernel: [ 2112.742434] RAX: RBX: 217a77ddff956e69 RCX: 8789 Jun 2 12:55:28 klimt kernel: [ 2112.744329] RDX: 8788 RSI: 217a77ddff956e69 RDI: 9da1d110ab80 Jun 2 12:55:28 klimt kernel: [ 2112.746222] RBP: aa9a0823bd20 R08: ca99fe822eb0 R09: 9da1d31275a0 Jun 2 12:55:28 klimt kernel: [ 2112.748113] R10: 0007fcbd8002 R11: 9da1ca4d9e00 R12: 014000c0 Jun 2 12:55:28 klimt kernel: [ 2112.750006] R13: 9da1ddc04780 R14: 9da1ca4d9000 R15: 9da1d110ab80 Jun 2 12:55:28 klimt kernel: [ 2112.794382] FS: 7fcc33fff700() GS:9da1de40() knlGS: Jun 2 12:55:28 klimt kernel: [ 2112.884578] CS: 0010 DS: ES: CR0: 80050033 Jun 2 12:55:28 klimt kernel: [ 2112.930582] CR2: 7fcc7e5bf000 CR3: 002012cdc006 CR4: 003606e0 Jun 2 12:55:28 klimt kernel: [ 2112.976554] DR0: DR1: DR2: Jun 2 12:55:28 klimt kernel: [ 2113.021459] DR3: DR6: fffe0ff0 DR7: 0400 Jun 2 12:55:28 klimt kernel: [ 2113.064959] Call Trace: Jun 2 12:55:28 klimt kernel: [ 2113.106986] kmem_cache_alloc+0xa2/0x1b0 Jun 2 12:55:28 klimt kernel: [ 2113.148571] ? anon_vma_fork+0x97/0x130 Jun 2 12:55:28 klimt kernel: [ 2113.189139] anon_vma_fork+0x97/0x130 Jun 2 12:55:28 klimt kernel: [ 2113.228632] copy_process.part.35+0xdce/0x1af0 Jun 2 12:55:28 klimt kernel: [ 2113.267459] _do_fork+0xdf/0x400 Jun 2 12:55:28 klimt kernel: [ 2113.305090] ? get_unused_fd_flags+0x30/0x40 Jun 2 12:55:28 klimt kernel: [ 2113.342027] SyS_clone+0x19/0x20 Jun 2 12:55:28 klimt kernel: [ 2113.377704] do_syscall_64+0x73/0x130 Jun 2 12:55:28 klimt kernel: [ 2113.412455] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Jun 2 12:55:28 klimt kernel: [ 2113.446867] RIP: 0033:0x7fcd1de5ab1c Jun 2 12:55:28 klimt kernel: [ 2113.480134] RSP: 002b:7fcc33ffb630 EFLAGS: 0246 ORIG_RAX: 0038 Jun 2 12:55:28 klimt kernel: [ 2113.546601] RAX: ffda RBX: 7fcc33ffb630 RCX: 7fcd1de5ab1c Jun 2 12:55:28 klimt kernel: [ 2113.581224] RDX: RSI: RDI: 01200011 Jun 2 12:55:28 klimt kernel: [ 2113.615346] RBP: 7fcc33ffb6a0 R08: 7fcc33fff700 R09: Jun 2 12:55:28 klimt kernel: [ 2113.648651] R10: 7fcc33fff9d0 R11: 0246 R12: 000
[Kernel-packages] [Bug 1775137] Re: Prevent speculation on user controlled pointer
** Description changed:
- Upstream's Spectre v1 mitigation prevents speculation on a user
- controlled pointer. This part of the Spectre v1 patchset was never
- backported to 4.4 (for unknown reasons) so Xenial is lacking it as well.
- All the other stable upstream kernels include it, so add it to Xenial.
- Specifically, the following patches are needed:
+ == SRU Justification ==
+ Upstream's Spectre v1 mitigation prevents speculation on a user controlled
pointer. This part of the Spectre v1 patchset was never backported to 4.4 (for
unknown reasons) so Xenial/Trusty/Precise are lacking it as well. All the other
stable upstream kernels include it, so add it to our older kernels.
- c7f631cb07e7 x86/get_user: Use pointer masking to limit speculation
- 304ec1b05031 x86/uaccess: Use __uaccess_begin_nospec() and uaccess_try_nospec
- b5c4ae4f3532 x86/usercopy: Replace open coded stac/clac with
__uaccess_{begin, end}
- b3bbfb3fb5d2 x86: Introduce __uaccess_begin_nospec() and uaccess_try_nospec
+ == Fix ==
+ Backport the following patches:
+ x86/uaccess: Use __uaccess_begin_nospec() and uaccess_try_nospec
+ x86/usercopy: Replace open coded stac/clac with __uaccess_{begin, end}
+ x86: Introduce __uaccess_begin_nospec() and uaccess_try_nospec
+
+ == Regression Potential ==
+ Low. Patches have been in upstream (and other distro kernels) for quite a
while now and the changes only introduce a barrier on copy_from_user operations.
+
+ == Test Case ==
+ TBD.
--
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/1775137
Title:
Prevent speculation on user controlled pointer
Status in linux package in Ubuntu:
Incomplete
Bug description:
== SRU Justification ==
Upstream's Spectre v1 mitigation prevents speculation on a user controlled
pointer. This part of the Spectre v1 patchset was never backported to 4.4 (for
unknown reasons) so Xenial/Trusty/Precise are lacking it as well. All the other
stable upstream kernels include it, so add it to our older kernels.
== Fix ==
Backport the following patches:
x86/uaccess: Use __uaccess_begin_nospec() and uaccess_try_nospec
x86/usercopy: Replace open coded stac/clac with __uaccess_{begin, end}
x86: Introduce __uaccess_begin_nospec() and uaccess_try_nospec
== Regression Potential ==
Low. Patches have been in upstream (and other distro kernels) for quite a
while now and the changes only introduce a barrier on copy_from_user operations.
== Test Case ==
TBD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775137/+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 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29
Just to clarify above comment from hans005: from what I can read here his problem (#138, #145) was a completely different issue: standby with nvidia GPU. This regression relates to *hibernation* (not mere standby) and AFAIK, has been experienced with a variety of GPUs (included Intel integrated GPUs as in my case) so it's quite likely *not* a condition related to GPU drivers or model in use - although it's common for less run-of-the- mill dGPUs to exacerbate such issues I suppose. I don't believe there are any workarounds to the issue accurately captured by the bug's headline. -- 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/1743094 Title: [regression] hibernation (freezes on resume) since 4.13.0-25.29 Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: After hibernating the system and than resuming it the system reboots notifying that it is resuming and than stops/freezes. The system does not respond to anything (no tty's other notifying textg are available). After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep functions as proposed. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jb 1717 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478 InstallationDate: Installed on 2017-12-10 (34 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: Acer Aspire S3-391 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-26-generic N/A linux-backports-modules-4.13.0-26-generic N/A linux-firmware 1.157.14 Tags: sylvia Uname: Linux 4.13.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/31/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Hummingbird2 dmi.board.vendor: Acer dmi.board.version: V2.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S3-391 dmi.product.version: V2.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/+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 1775390] [NEW] kernel: Fix memory leak on CCA and EP11 CPRB processing.
You have been subscribed to a public bug: Description: kernel: Fix memory leak on CCA and EP11 CPRB processing. Symptom: Kernel memory not freed when CCA or EP11 CPRB processing fails. Problem: kfree() in code error path missing. Solution: Slight rework of the malloc and free places. Reproduction: Run application which sends CCA or EP11 crypto requests to the crypto card(s). Now switch the cards offline with the help of chzcrypt. Monitor top or free output. Upstream commit(s): kernel 4.18 89a0c0ec0d2e3ce0ee9caa00f60c0c26ccf11c21 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-168539 severity-high targetmilestone-inin1804 -- kernel: Fix memory leak on CCA and EP11 CPRB processing. https://bugs.launchpad.net/bugs/1775390 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775391] [NEW] kernel: Fix arch random implementation
You have been subscribed to a public bug: Description: kernel: Fix arch random implementation Symptom: arch_get_random_seed_long() invocations may slow down the interrupt handling on heavy interrupt producing loads. Problem: The existing random device driver calls arch_get_random_seed_long() in interrupt context. The current implementation of this function uses the PRNO(TRNG) instruction to provide good entropy. This instruction is relatively slow and expensive and may slow down the capacity of interrupts which can be handled per cpu. Solution: This fix reworks the arch_get_random_seed implementation. It introduces a buffer concept to decouple the delivery of random data via arch_get_random_seed*() from the generation of new random bytes and so does not limit the interrupt handling per cpu any more. Reproduction: Systems with heavy irq load show performance decrease. Component:kernel Upstream commit(s): kernel 4.18 966f53e750aedc5f59f9ccae6bbfb8f671c7c842 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-168538 severity-high targetmilestone-inin1804 -- kernel: Fix arch random implementation https://bugs.launchpad.net/bugs/1775391 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775391] upstream patch
Default Comment by Bridge ** Attachment added: "upstream patch" https://bugs.launchpad.net/bugs/1775391/+attachment/5149333/+files/s390-archrandom-rework.patch ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775391 Title: kernel: Fix arch random implementation Status in linux package in Ubuntu: New Bug description: Description: kernel: Fix arch random implementation Symptom: arch_get_random_seed_long() invocations may slow down the interrupt handling on heavy interrupt producing loads. Problem: The existing random device driver calls arch_get_random_seed_long() in interrupt context. The current implementation of this function uses the PRNO(TRNG) instruction to provide good entropy. This instruction is relatively slow and expensive and may slow down the capacity of interrupts which can be handled per cpu. Solution: This fix reworks the arch_get_random_seed implementation. It introduces a buffer concept to decouple the delivery of random data via arch_get_random_seed*() from the generation of new random bytes and so does not limit the interrupt handling per cpu any more. Reproduction: Systems with heavy irq load show performance decrease. Component:kernel Upstream commit(s): kernel 4.18 966f53e750aedc5f59f9ccae6bbfb8f671c7c842 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775391/+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 1775235] Re: Ubuntu 16.04 (4.4.0-127) hangs on boot with virtio-scsi MQ enabled
** Description changed:
We noticed that Ubuntu 16.04 guests running on Nutanix AHV stopped
booting after they were upgraded to the latest kernel (4.4.0-127). Only
guests with scsi mq enabled suffered from this problem. AHV is one of
the few hypervisor products to offer multiqueue for virtio-scsi devices.
Upon further investigation, we could see that the kernel would hang
during the scanning of scsi targets. More specifically, immediately
after coming across a target without any luns present. That's the first
time the kernel destroys a target (given it doesn't have luns). This
could be confirmed with gdb (attached to qemu's gdbserver):
#0 0xc0045039 in ?? ()
#1 0x88022c753c98 in ?? ()
#2 0x815d1de6 in scsi_target_destroy (starget=0x88022ad62400)
- at /build/linux-E14mqW/linux-4.4.0/drivers/scsi/scsi_scan.c:322
+ at /build/linux-E14mqW/linux-4.4.0/drivers/scsi/scsi_scan.c:322
This shows the guest vCPU stuck on virtio-scsi's implementation of
target_destroy. Despite lacking symbols, we managed to examine the
virtio_scsi_target_state to see that the 'reqs' counter was invalid:
(gdb) p *(struct virtio_scsi_target_state *)starget->hostdata
$6 = {tgt_seq = {sequence = 0}, reqs = {counter = -1}, req_vq =
0x88022cbdd9e8}
(gdb)
This drew our attention to the following patch which is exclusive to the
Ubuntu kernel:
commit f1f609d8015e1d34d39458924dcd9524fccd4307
Author: Jay Vosburgh
Date: Thu Apr 19 21:40:00 2018 +0200
In a nutshell, the patch spins on the target's 'reqs' counter waiting for the
target to quiesce:
--- a/drivers/scsi/virtio_scsi.c
+++ b/drivers/scsi/virtio_scsi.c
@@ -785,6 +785,10 @@ static int virtscsi_target_alloc(struct scsi_target
*starget)
- static void virtscsi_target_destroy(struct scsi_target *starget)
- {
- struct virtio_scsi_target_state *tgt = starget->hostdata;
+ static void virtscsi_target_destroy(struct scsi_target *starget)
+ {
+ struct virtio_scsi_target_state *tgt = starget->hostdata;
+
+ /* we can race with concurrent virtscsi_complete_cmd */
+ while (atomic_read(&tgt->reqs))
+ cpu_relax();
- kfree(tgt);
- }
+ kfree(tgt);
+ }
Personally, I think this is a catastrophic way of waiting for a target
to quiesce since virtscsi_target_destroy() is called with IRQs disabled
from scsi_scan.c:scsi_target_destroy(). Devices which take a long time
to quiesce during a target_destroy() could hog the CPU for relatively
long periods of time.
Nevertheless, further study revealed that virtio-scsi itself is broken
in a way that it doesn't increment the 'reqs' counter when submitting
requests on MQ in certain conditions. That caused the counter to go to
-1 (on the completion of the first request) and the CPU to hang
indefinitely.
The following patch fixes the issue:
- --- new/linux-4.4.0/drivers/scsi/virtio_scsi.c2018-06-05
10:03:29.083428545 -0700
- +++ old/linux-4.4.0/drivers/scsi/virtio_scsi.c2018-06-04
10:23:07.0 -0700
- @@ -641,10 +641,9 @@
+ --- old/linux-4.4.0/drivers/scsi/virtio_scsi.c2018-06-04
10:23:07.0 -0700
+ +++ new/linux-4.4.0/drivers/scsi/virtio_scsi.c2018-06-05
10:03:29.083428545 -0700
+ @@ -641,9 +641,10 @@
scsi_target(sc->device)->hostdata;
struct virtio_scsi_vq *req_vq;
- - if (shost_use_blk_mq(sh)) {
- + if (shost_use_blk_mq(sh))
+ - if (shost_use_blk_mq(sh))
+ + if (shost_use_blk_mq(sh)) {
req_vq = virtscsi_pick_vq_mq(vscsi, sc);
- - atomic_inc(&tgt->reqs);
- - } else
- + else
+ - else
+ + atomic_inc(&tgt->reqs);
+ + } else
req_vq = virtscsi_pick_vq(vscsi, tgt);
return virtscsi_queuecommand(vscsi, req_vq, sc);
Signed-off-by: Felipe Franciosi
-
- Please consider this a urgent fix as all of our customers which use Ubuntu
16.04 and have MQ enabled for better performance will be affected by your
latest update. Our workaround is to recommend that they disable SCSI MQ while
you work on the issue.
+ Please consider this a urgent fix as all of our customers which use
+ Ubuntu 16.04 and have MQ enabled for better performance will be affected
+ by your latest update. Our workaround is to recommend that they disable
+ SCSI MQ while you work on the issue.
Best regards,
Felipe
--
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/1775235
Title:
Ubuntu 16.04 (4.4.0-127) hangs on boot with virtio-scsi MQ enabled
Status in linux package in Ubuntu:
Confirmed
Bug description:
We noticed that Ubuntu 16.04 guests running on Nutanix AHV stopped
booting after they were upgraded to the latest kernel (4.4.0-127).
Only guests with sc
[Kernel-packages] [Bug 1775390] upstream patch
Default Comment by Bridge ** Attachment added: "upstream patch" https://bugs.launchpad.net/bugs/1775390/+attachment/5149332/+files/s390-zcrypt-fix-CCA-and-EP11-CPRB-memory-leak.patch ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775390 Title: kernel: Fix memory leak on CCA and EP11 CPRB processing. Status in linux package in Ubuntu: New Bug description: Description: kernel: Fix memory leak on CCA and EP11 CPRB processing. Symptom: Kernel memory not freed when CCA or EP11 CPRB processing fails. Problem: kfree() in code error path missing. Solution: Slight rework of the malloc and free places. Reproduction: Run application which sends CCA or EP11 crypto requests to the crypto card(s). Now switch the cards offline with the help of chzcrypt. Monitor top or free output. Upstream commit(s): kernel 4.18 89a0c0ec0d2e3ce0ee9caa00f60c0c26ccf11c21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775390/+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 1771238] Re: Not able to passthrough > 32 PCIe devices to a KVM Guest
Thanks Alex for cross checking.
I got handed a seabios change that was mentioned to make this work.
I'll clean it up and build/test on my own.
Once I have a good feeling I'll submit an RFC upstream for review and
set you on CC.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771238
Title:
Not able to passthrough > 32 PCIe devices to a KVM Guest
Status in linux package in Ubuntu:
Confirmed
Status in qemu package in Ubuntu:
New
Bug description:
Using an Ubuntu Server 16.04-based host with KVM hypervisor installed,
we are unable to launch a vanilla Ubuntu Server 16.04.4 guest with >=
32 PCIe devices. It is 100% reproducible. Using fewer PCIe devices
works fine. We are using the vanilla kvm and qemu packages from the
Canonical repos.
The ultimate goal is to create a KVM Guest wherein I can passthrough
44 PCI devices.
When a KVM Guest launches, it also has some internal PCIe devices
including host bridge, USB, IDE (for virtual disk), and virtual nic
etc.
Script used to launch all devices looks like this:
#!/bin/bash
NAME=16gpuvm
sudo qemu-img create -f qcow2 /home/lab/kvm/images/${NAME}.img 40G &&
sudo virt-install \
--name ${NAME} \
--ram 716800 \
--vcpus 88 \
--disk path=/home/lab/kvm/images/${NAME}.img,format=qcow2 \
--network bridge=virbr0 \
--graphics none \
--host-device 34:00.0 \
--host-device 36:00.0 \
--host-device 39:00.0 \
--host-device 3b:00.0 \
--host-device 57:00.0 \
--host-device 59:00.0 \
--host-device 5c:00.0 \
--host-device 5e:00.0 \
--host-device 61:00.0 \
--host-device 62:00.0 \
--host-device 63:00.0 \
--host-device 65:00.0 \
--host-device 66:00.0 \
--host-device 67:00.0 \
--host-device 35:00.0 \
--host-device 3a:00.0 \
--host-device 58:00.0 \
--host-device 5d:00.0 \
--host-device 2e:00.0 \
--host-device 2f:00.0 \
--host-device 51:00.0 \
--host-device 52:00.0 \
--host-device b7:00.0 \
--host-device b9:00.0 \
--host-device bc:00.0 \
--host-device be:00.0 \
--host-device e0:00.0 \
--host-device e2:00.0 \
--host-device e5:00.0 \
--host-device e7:00.0 \
--host-device c1:00.0 \
--host-device c2:00.0 \
--host-device c3:00.0 \
--host-device c5:00.0 \
--host-device c6:00.0 \
--host-device c7:00.0 \
--host-device b8:00.0 \
--host-device bd:00.0 \
--host-device e1:00.0 \
--host-device e6:00.0 \
--host-device b1:00.0 \
--host-device b2:00.0 \
--host-device da:00.0 \
--host-device db:00.0 \
--console pty,target_type=serial \
--location http://ftp.ubuntu.com/ubuntu/dists/xenial/main/installer-amd64 \
--initrd-inject=/home/lab/kvm/images/preseed.cfg \
--extra-args="
console=ttyS0,115200
locale=en_US
console-keymaps-at/keymap=us
console-setup/ask_detect=false
console-setup/layoutcode=us
keyboard-configuration/layout=USA
keyboard-configuration/variant=USA
hostname=${NAME}
file=file:/preseed.cfg
"
Passing > 32 device causes this issue: 32nd device hits a DPC error
and the host/HV crashes:
Apr 25 22:34:35 xpl-evt-16 kernel: [18125.977496] dpc :5b:10.0:pcie210:
DPC containment event, status:0x0009 source:0x
Apr 25 22:34:35 xpl-evt-16 kernel: [18125.977500] dpc :5b:10.0:pcie210:
DPC unmasked uncorrectable error detected, remove downstream devices
Apr 25 22:34:35 xpl-evt-16 kernel: [18125.994326] vfio-pci :5e:00.0:
Refused to change power state, currently in D3
Apr 25 22:34:35 xpl-evt-16 kernel: [18125.994427] iommu: Removing device
:5e:00.0 from group 92
From syslog (attached)
Apr 25 22:37:13 xpl-evt-16 kernel: [2.194358] dpc :bb:04.0:pcie210:
DPC error containment capabilities: Int Msg #3, RPExt- PoisonedTLP+ SwTrigger+
RP PIO Log 0, DL_ActiveErr+
Apr 25 22:37:13 xpl-evt-16 kernel: [2.194387] dpc :bb:10.0:pcie210:
DPC error containment capabilities: Int Msg #3, RPExt- PoisonedTLP+ SwTrigger+
RP PIO Log 0, DL_ActiveErr+
Apr 25 22:37:13 xpl-evt-16 kernel: [2.194413] dpc :d9:00.0:pcie210:
DPC error containment capabilities: Int Msg #3, RPExt- PoisonedTLP+ SwTrigger+
RP PIO Log 0, DL_ActiveErr+
Apr 25 22:37:13 xpl-evt-16 kernel: [2.194439] dpc :d9:01.0:pcie210:
DPC error containment capabilities: Int Msg #3, RPExt- PoisonedTLP+ SwTrigger+
RP PIO Log 0, DL_ActiveErr+
Apr 25 22:37:13 xpl-evt-16 kernel: [2.194472] dpc :d9:02.0:pcie210:
DPC error containment capabilities: Int Msg #3, RPExt- PoisonedTLP+ SwTrigger+
RP PIO Log 0, DL_ActiveErr+
Apr 25 22:37:13 xpl-evt-16 kernel: [2.194499] dpc :d9:03.0:pcie210:
DPC error containment capabilities: Int Msg #3, RPExt- PoisonedTLP+ SwTrigger+
RP PIO Log 0, DL_ActiveErr+
Apr 25 22:37:13 xpl-evt-16 kernel: [2.194526] dpc :d9:04.0:pcie210:
DPC error containment capabilities: Int Msg #3, RPExt- PoisonedTLP
[Kernel-packages] [Bug 1773392] Re: zfs hangs on mount/unmount
Another experiment: 1) Setting new ubuntu 18.04 server with LXD on ZFS - zfs hangs on ct restart 2) Install 4.13.0-36 (from 16.04 HWE install disk) kernel + zfs 0.6.5 from xenial repo (because 0.7.5 not compatible with old kernel) 3) Setup grub to load old kernel and reboot 4) And... everything is fine :) I will use this method on my servers because I have no idea when this bug will be fixed... -- 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/1773392 Title: zfs hangs on mount/unmount Status in linux package in Ubuntu: Confirmed Bug description: I am running lxd 3.0 on ubuntu 18.04 with kernel 4.15.0-22-generic and 4.15.0-20-generic (same behaviour) with zfs backend (0.7.5-1ubuntu16; also tried 0.7.9). Sometimes lxd hangs when I try to stop / restart or "stop && move" some containers. Furhter investigation showed that problem is in zfs mount or unmount: it just hangs and lxd just wait it. Also commands like "zfs list" hangs to. It seems that it is not lxd or zfs issue, but kernel bug? https://github.com/lxc/lxd/issues/4104#issuecomment-392072939 I have one test ct that always hangs on restart, so here is info: dmesg: [ 1330.390938] INFO: task txg_sync:9944 blocked for more than 120 seconds. [ 1330.390994] Tainted: P O 4.15.0-22-generic #24-Ubuntu [ 1330.391044] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1330.391101] txg_syncD0 9944 2 0x8000 [ 1330.391105] Call Trace: [ 1330.391117] __schedule+0x297/0x8b0 [ 1330.391122] schedule+0x2c/0x80 [ 1330.391136] cv_wait_common+0x11e/0x140 [spl] [ 1330.391141] ? wait_woken+0x80/0x80 [ 1330.391152] __cv_wait+0x15/0x20 [spl] [ 1330.391234] rrw_enter_write+0x3c/0xa0 [zfs] [ 1330.391306] rrw_enter+0x13/0x20 [zfs] [ 1330.391380] spa_sync+0x7c9/0xd80 [zfs] [ 1330.391457] txg_sync_thread+0x2cd/0x4a0 [zfs] [ 1330.391534] ? txg_quiesce_thread+0x3d0/0x3d0 [zfs] [ 1330.391543] thread_generic_wrapper+0x74/0x90 [spl] [ 1330.391549] kthread+0x121/0x140 [ 1330.391558] ? __thread_exit+0x20/0x20 [spl] [ 1330.391562] ? kthread_create_worker_on_cpu+0x70/0x70 [ 1330.391566] ? kthread_create_worker_on_cpu+0x70/0x70 [ 1330.391569] ret_from_fork+0x35/0x40 [ 1330.391582] INFO: task lxd:12419 blocked for more than 120 seconds. [ 1330.391630] Tainted: P O 4.15.0-22-generic #24-Ubuntu [ 1330.391679] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1330.391735] lxd D0 12419 1 0x [ 1330.391739] Call Trace: [ 1330.391745] __schedule+0x297/0x8b0 [ 1330.391749] schedule+0x2c/0x80 [ 1330.391752] rwsem_down_write_failed+0x162/0x360 [ 1330.391808] ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs] [ 1330.391814] call_rwsem_down_write_failed+0x17/0x30 [ 1330.391817] ? call_rwsem_down_write_failed+0x17/0x30 [ 1330.391821] down_write+0x2d/0x40 [ 1330.391825] grab_super+0x30/0x90 [ 1330.391901] ? zpl_create+0x160/0x160 [zfs] [ 1330.391905] sget_userns+0x91/0x490 [ 1330.391908] ? get_anon_bdev+0x100/0x100 [ 1330.391983] ? zpl_create+0x160/0x160 [zfs] [ 1330.391987] sget+0x7d/0xa0 [ 1330.391990] ? get_anon_bdev+0x100/0x100 [ 1330.392066] zpl_mount+0xa8/0x160 [zfs] [ 1330.392071] mount_fs+0x37/0x150 [ 1330.392077] vfs_kern_mount.part.23+0x5d/0x110 [ 1330.392080] do_mount+0x5ed/0xce0 [ 1330.392083] ? copy_mount_options+0x2c/0x220 [ 1330.392086] SyS_mount+0x98/0xe0 [ 1330.392092] do_syscall_64+0x73/0x130 [ 1330.392096] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 1330.392099] RIP: 0033:0x4db36a [ 1330.392101] RSP: 002b:00c4207fa768 EFLAGS: 0216 ORIG_RAX: 00a5 [ 1330.392104] RAX: ffda RBX: RCX: 004db36a [ 1330.392106] RDX: 00c4205984cc RSI: 00c420a6ee00 RDI: 00c420a23b60 [ 1330.392108] RBP: 00c4207fa808 R08: 00c4209d4960 R09: [ 1330.392110] R10: R11: 0216 R12: [ 1330.392112] R13: 0039 R14: 0038 R15: 0080 [ 1330.392123] INFO: task lxd:16725 blocked for more than 120 seconds. [ 1330.392171] Tainted: P O 4.15.0-22-generic #24-Ubuntu [ 1330.392220] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1330.392276] lxd D0 16725 1 0x0002 [ 1330.392279] Call Trace: [ 1330.392284] __schedule+0x297/0x8b0 [ 1330.392289] ? irq_work_queue+0x8d/0xa0 [ 1330.392293] schedule+0x2c/0x80 [ 1330.392297] io_schedule+0x16/0x40 [ 1330.392302] wait_on_page_bit_common+0xd8/0x160 [ 1330.392305] ? page_cache_tree_insert+0xe0/0xe0 [ 1330.392309] __filemap_fdatawait_range+0xfa/0x160 [ 1330.392313] ? _cond_resched+0x19/0x40 [ 1330.3923
[Kernel-packages] [Bug 1775378] Re: fanotify06 in LTP syscall test failed with T kernel
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Trusty) Importance: Undecided => Medium -- 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/1775378 Title: fanotify06 in LTP syscall test failed with T kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Bug description: The "fanotify06" from the LTP syscall tests has failed on a testing node with T kernel installed. Steps (with root): 1. sudo apt-get install git xfsprogs -y 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git 3. cd ltp 4. make autotools 5. ./configure 6. make; make install 7. /opt/ltp/testcases/bin/fanotify06 <<>> tag=fanotify06 stime=1528269991 cmdline="fanotify06" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fanotify06.c:147: PASS: group 0 get event: mask 2 pid=22619 fd=29 fanotify06.c:147: PASS: group 1 get event: mask 2 pid=22619 fd=29 fanotify06.c:147: PASS: group 2 get event: mask 2 pid=22619 fd=29 fanotify06.c:197: FAIL: group 3 got event fanotify06.c:197: FAIL: group 4 got event fanotify06.c:197: FAIL: group 5 got event fanotify06.c:208: PASS: group 6 got no event fanotify06.c:208: PASS: group 7 got no event fanotify06.c:197: FAIL: group 8 got event Summary: passed 5 failed 4 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-149-generic 3.13.0-149.199 ProcVersionSignature: User Name 3.13.0-149.199-generic 3.13.11-ckt39 Uname: Linux 3.13.0-149-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 6 10:09 seq crw-rw 1 root audio 116, 33 Jun 6 10:09 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [3.472391] init: plymouth-upstart-bridge main process ended, respawning Date: Wed Jun 6 10:12:15 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1775378/+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 1775235] Re: Ubuntu 16.04 (4.4.0-127) hangs on boot with virtio-scsi MQ enabled
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
--
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/1775235
Title:
Ubuntu 16.04 (4.4.0-127) hangs on boot with virtio-scsi MQ enabled
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
Confirmed
Bug description:
We noticed that Ubuntu 16.04 guests running on Nutanix AHV stopped
booting after they were upgraded to the latest kernel (4.4.0-127).
Only guests with scsi mq enabled suffered from this problem. AHV is
one of the few hypervisor products to offer multiqueue for virtio-scsi
devices.
Upon further investigation, we could see that the kernel would hang
during the scanning of scsi targets. More specifically, immediately
after coming across a target without any luns present. That's the
first time the kernel destroys a target (given it doesn't have luns).
This could be confirmed with gdb (attached to qemu's gdbserver):
#0 0xc0045039 in ?? ()
#1 0x88022c753c98 in ?? ()
#2 0x815d1de6 in scsi_target_destroy (starget=0x88022ad62400)
at /build/linux-E14mqW/linux-4.4.0/drivers/scsi/scsi_scan.c:322
This shows the guest vCPU stuck on virtio-scsi's implementation of
target_destroy. Despite lacking symbols, we managed to examine the
virtio_scsi_target_state to see that the 'reqs' counter was invalid:
(gdb) p *(struct virtio_scsi_target_state *)starget->hostdata
$6 = {tgt_seq = {sequence = 0}, reqs = {counter = -1}, req_vq =
0x88022cbdd9e8}
(gdb)
This drew our attention to the following patch which is exclusive to the
Ubuntu kernel:
commit f1f609d8015e1d34d39458924dcd9524fccd4307
Author: Jay Vosburgh
Date: Thu Apr 19 21:40:00 2018 +0200
In a nutshell, the patch spins on the target's 'reqs' counter waiting for the
target to quiesce:
--- a/drivers/scsi/virtio_scsi.c
+++ b/drivers/scsi/virtio_scsi.c
@@ -785,6 +785,10 @@ static int virtscsi_target_alloc(struct scsi_target
*starget)
static void virtscsi_target_destroy(struct scsi_target *starget)
{
struct virtio_scsi_target_state *tgt = starget->hostdata;
+
+ /* we can race with concurrent virtscsi_complete_cmd */
+ while (atomic_read(&tgt->reqs))
+ cpu_relax();
kfree(tgt);
}
Personally, I think this is a catastrophic way of waiting for a target
to quiesce since virtscsi_target_destroy() is called with IRQs
disabled from scsi_scan.c:scsi_target_destroy(). Devices which take a
long time to quiesce during a target_destroy() could hog the CPU for
relatively long periods of time.
Nevertheless, further study revealed that virtio-scsi itself is broken
in a way that it doesn't increment the 'reqs' counter when submitting
requests on MQ in certain conditions. That caused the counter to go to
-1 (on the completion of the first request) and the CPU to hang
indefinitely.
The following patch fixes the issue:
--- old/linux-4.4.0/drivers/scsi/virtio_scsi.c2018-06-04
10:23:07.0 -0700
+++ new/linux-4.4.0/drivers/scsi/virtio_scsi.c2018-06-05
10:03:29.083428545 -0700
@@ -641,9 +641,10 @@
scsi_target(sc->device)->hostdata;
struct virtio_scsi_vq *req_vq;
- if (shost_use_blk_mq(sh))
+ if (shost_use_blk_mq(sh)) {
req_vq = virtscsi_pick_vq_mq(vscsi, sc);
- else
+ atomic_inc(&tgt->reqs);
+ } else
req_vq = virtscsi_pick_vq(vscsi, tgt);
return virtscsi_queuecommand(vscsi, req_vq, sc);
Signed-off-by: Felipe Franciosi
Please consider this a urgent fix as all of our customers which use
Ubuntu 16.04 and have MQ enabled for better performance will be
affected by your latest update. Our workaround is to recommend that
they disable SCSI MQ while you work on the issue.
Best regards,
Felipe
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775235/+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 1775370] Re: request_key03 in LTP syscall test cause kernel oops with T kernel
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Trusty) Importance: Undecided => Medium -- 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/1775370 Title: request_key03 in LTP syscall test cause kernel oops with T kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Bug description: The "request_key03" from the LTP syscall tests will cause kernel oops with Trusty kernel. Steps (with root): 1. sudo apt-get install git xfsprogs -y 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git 3. cd ltp 4. make autotools 5. ./configure 6. make; make install 7. /opt/ltp/testcases/bin/request_key03 $ sudo /opt/ltp/testcases/bin/request_key03 tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s request_key03.c:158: FAIL: kernel oops while updating key of type 'encrypted' request_key03.c:168: PASS: didn't crash while requesting key of type 'encrypted' request_key03.c:158: FAIL: kernel oops while updating key of type 'trusted' request_key03.c:168: PASS: didn't crash while requesting key of type 'trusted' request_key03.c:154: PASS: didn't crash while updating key of type 'user' request_key03.c:168: PASS: didn't crash while requesting key of type 'user' Summary: passed 4 failed 2 skipped 0 warnings 0 [14180.795675] encrypted_key: keyword 'update' not allowed when called from .instantiate method [14180.796205] BUG: unable to handle kernel NULL pointer dereference at 0018 [14180.796230] IP: [] encrypted_update+0xa6/0x160 [14180.796248] PGD 80045383e067 PUD 4568c5067 PMD 0 [14180.796263] Oops: [#1] SMP [14180.796273] Modules linked in: ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt joydev hid_generic x86_pkg_temp_thermal coretemp kvm_intel kvm usbhid hid mac_hid lpc_ich shpchp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul i915_bdw glue_helper ablk_helper cryptd igb dca ptp ahci intel_ips pps_core libahci i2c_algo_bit drm_kms_helper drm video [14180.796407] CPU: 6 PID: 1888 Comm: request_key03 Not tainted 3.13.0-151-generic #201 [14180.796425] Hardware name: Intel Corporation S1200RP/S1200RP, BIOS S1200RP.86B.03.02.0003.070120151022 07/01/2015 [14180.796449] task: 880458463000 ti: 880454b16000 task.ti: 880454b16000 [14180.796466] RIP: 0010:[] [] encrypted_update+0xa6/0x160 [14180.796488] RSP: 0018:880454b17e18 EFLAGS: 00010246 [14180.796502] RAX: RBX: 880455db1a40 RCX: [14180.796518] RDX: 0005 RSI: 880455db1a4c RDI: 818400a3 [14180.796535] RBP: 880454b17e50 R08: R09: 880455db1a4f [14180.796552] R10: 0020 R11: 81388b44 R12: [14180.796568] R13: R14: 88045553a240 R15: 880455db1a47 [14180.796585] FS: 7faf78341740() GS:8804704c() knlGS: [14180.796604] CS: 0010 DS: ES: CR0: 80050033 [14180.796618] CR2: 0018 CR3: 0004550c8000 CR4: 00360770 [14180.796635] DR0: DR1: DR2: [14180.796652] DR3: DR6: fffe0ff0 DR7: 0400 [14180.796668] Stack: [14180.796674] 880455db1a47 88045553a240 88045553a260 [14180.796695] 880459c092c0 88045553a241 880458463000 880454b17f00 [14180.796715] 812d761b 0286 880459c09980 [14180.796735] Call Trace: [14180.796744] [] key_create_or_update+0x27b/0x420 [14180.796760] [] SyS_add_key+0x110/0x210 [14180.796775] [] system_call_fastpath+0x1a/0x1f [14180.796789] Code: 89 c7 e8 7e de 09 00 48 8d 55 c8 48 8d 75 d0 45 31 c0 31 c9 48 89 df e8 19 f3 ff ff 85 c0 41 89 c4 0f 88 88 00 00 00 4c 8b 7d c8 <49> 8b 75 18 4c 89 ff e8 fe f1 ff ff 85 c0 41 89 c4 78 71 49 8b [14180.796888] RIP [] encrypted_update+0xa6/0x160 [14180.796904] RSP [14180.796913] CR2: 0018 [14180.799331] ---[ end trace 4fc59232fdc581c7 ]--- [14180.805266] BUG: unable to handle kernel NULL pointer dereference at 0018 [14180.805303] IP: [] trusted_update+0x28/0x1e0 [14180.805334] PGD 80045a2b7067 PUD 45710b067 PMD 0 [14180.805361] Oops: [#2] SMP [14180.805379] Modules linked in: ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib
[Kernel-packages] [Bug 1775412] [NEW] no internet on resume from suspend
Public bug reported: Whenever I suspend my system (in Ubuntu Budgie 18.04) and then resume from suspend, I have no internet connection until I reboot. Restarting the networking service and unplugging/replugging doesn't fix it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed Jun 6 10:31:10 2018 InstallationDate: Installed on 2018-06-04 (1 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (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 linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1775412 Title: no internet on resume from suspend Status in linux-signed package in Ubuntu: New Bug description: Whenever I suspend my system (in Ubuntu Budgie 18.04) and then resume from suspend, I have no internet connection until I reboot. Restarting the networking service and unplugging/replugging doesn't fix it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed Jun 6 10:31:10 2018 InstallationDate: Installed on 2018-06-04 (1 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1775412/+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 1762259] Re: Ubuntu 18.04 is not booting without adding the nomodeset parameter to the linux commandline
But Fedora also uses grub... -- 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/1762259 Title: Ubuntu 18.04 is not booting without adding the nomodeset parameter to the linux commandline Status in linux package in Ubuntu: Incomplete Bug description: I have an DVI-I to VGA adapter on my videocard. Usually I just need to put video=1440x900 because the linux kernel fails to recognize the correct resolution, but I couldn't make it display on the screen even setting video=DVI-I:1440x900. I believe it switches to HDMI because I could experience no issues like this on my television. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: boot/vmlinuz-4.15.0-13-generic] ProcVersionSignature: hostname 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lucio 1485 F pulseaudio /dev/snd/controlC1: lucio 1485 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 8 19:40:31 2018 InstallationDate: Installed on 2018-04-08 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=db8a4afa-dec3-45b6-a84f-9a702c6f96ad ro quiet splash nomodeset RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: 980DE3/U3S3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd04/09/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn980DE3/U3S3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762259/+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 1762259] Re: Ubuntu 18.04 is not booting without adding the nomodeset parameter to the linux commandline
It's easy to get the patches from Fedora and apply them on Ubuntu, isn't it? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762259 Title: Ubuntu 18.04 is not booting without adding the nomodeset parameter to the linux commandline Status in linux package in Ubuntu: Incomplete Bug description: I have an DVI-I to VGA adapter on my videocard. Usually I just need to put video=1440x900 because the linux kernel fails to recognize the correct resolution, but I couldn't make it display on the screen even setting video=DVI-I:1440x900. I believe it switches to HDMI because I could experience no issues like this on my television. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: boot/vmlinuz-4.15.0-13-generic] ProcVersionSignature: hostname 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lucio 1485 F pulseaudio /dev/snd/controlC1: lucio 1485 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 8 19:40:31 2018 InstallationDate: Installed on 2018-04-08 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=db8a4afa-dec3-45b6-a84f-9a702c6f96ad ro quiet splash nomodeset RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: 980DE3/U3S3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd04/09/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn980DE3/U3S3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762259/+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 1775137] Re: Prevent speculation on user controlled pointer
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1775137
Title:
Prevent speculation on user controlled pointer
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
New
Bug description:
== SRU Justification ==
Upstream's Spectre v1 mitigation prevents speculation on a user controlled
pointer. This part of the Spectre v1 patchset was never backported to 4.4 (for
unknown reasons) so Xenial/Trusty/Precise are lacking it as well. All the other
stable upstream kernels include it, so add it to our older kernels.
== Fix ==
Backport the following patches:
x86/uaccess: Use __uaccess_begin_nospec() and uaccess_try_nospec
x86/usercopy: Replace open coded stac/clac with __uaccess_{begin, end}
x86: Introduce __uaccess_begin_nospec() and uaccess_try_nospec
== Regression Potential ==
Low. Patches have been in upstream (and other distro kernels) for quite a
while now and the changes only introduce a barrier on copy_from_user operations.
== Test Case ==
TBD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775137/+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 1665935] Re: CVE-2017-6074
** Information type changed from Private Security to Public Security -- 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/1665935 Title: CVE-2017-6074 Status in linux package in Ubuntu: Fix Released Bug description: Patch: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=5edabca9d4cff7f1f2b68f0bac55ef99d9798ba4 Kernels affected: all of them :( MITIGATION: Disable autoloading the DCCP ipv4 and ipv6 module autoloading by creating /etc/modprobe.d/blacklist-dccp.conf with the following contents: alias net-pf-2-proto-0-type-6 off alias net-pf-2-proto-33-type-6 off alias net-pf-10-proto-0-type-6 off alias net-pf-10-proto-33-type-6 off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665935/+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 1759961] Re: Update to bluez 5.50
** Summary changed: - Update to bluez 5.50 (mostly bug-fix release) + Update to bluez 5.50 -- 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/1759961 Title: Update to bluez 5.50 Status in bluez package in Ubuntu: In Progress Bug description: From upstream: http://www.bluez.org/release-of-bluez-5-49/ Release of BlueZ 5.49 This is mostly a bug fix release, with fixes to features such as AVCTP, OBEX, GATT and Mesh. There are however some notable new features also, such as improved heartbeat management support in meshctl as well as a new experimental ConnectDevice D-Bus method on the Adapter interface, which can be used for quick device object creation for testing purpose or when information about the device has been received over some Out-of-Band channel. Upstream changelog: https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog ver 5.49: Fix issue with configuring discoverable advertising flag. Fix issue with bearer selection and single mode controllers. Fix issue with Connect and ConnectProfile returning in progress. Fix issue with missing Paired property change when not bonded. Fix issue with storage for controllers without public address. Fix issue with handling AVCTP disconnecting the channel queue. Fix issue with not clearing connectable setting on power off. Fix issue with creating multiple mgmt socket instances. Fix issue with GATT server and BR/EDR only devices. Fix issue with InterfaceAdded event ordering. Add support for generic ConnectDevice method call. Add support for Mesh heartbeat client functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+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 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
@Matze thanks for adding to the bug report - Here's where it starts to get interesting :) My problem laptop is an HP Pavilion x360 11-n013na with a quadcore Intel Pentium N3540 4GB of DDR3 Ram 250GB SSD (Samsung 850 EVO) I also have an HP Stream 11 with an Intel Celeron N2840 that does NOT have any suspend problems. The HP Stream is almost identical hardware-wise. Components such as the entire screen assembly, battery and USB board are inter-changeable (which I know because I have actually swapped them over!) So for the Stream to be fine, but the Pavilion to have suspend problems makes me curious about the differences. The Stream that suspends has eMMc storage and 2GB Ram (soldered to the main board :( ) With your Acer E13, you have an Intel Celeron based Atom CPU (N2940) coupled with an SSD. My Pavilion also has an Intel Celeron based Atom CPU (N3540) coupled with an SSD. (The 'Pentium' title for the N3540 is just a branding thing I believe - same architecture) So it is pure conjecture at the moment, but if we gather more people experiencing the same problem, I wonder if there might be a significant number of these Atom-style Celeron variant CPU's with an SSD as their main storage experiencing problems with suspend. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Confirmed Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+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 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
Matalak's Acer Aspire ES1-511 (from https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend where I found the 4.14 kernel solution) is also an Intel Celeron (N2830) CPU as far as I can tell from the specs. I've asked him to contribute to the bug report, but don't think he's seen my requests yet. I'll ask if he's using an SSD as well. -- 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/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Confirmed Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+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 1313279] Re: xHCI host not responding to stop endpoint command
I'm way out of date on this, but that patch looks like it was committed into the Linux kernel in Mach 2015: https://github.com/torvalds/linux/commit/227a4fd801c8a9fa2c4700ab98ec1aec06e3b44d ... which would suggest that it would have appeared "in the wild" with 3.19.2 or thereabouts? Even if my timeline isn't completely accurate, and if that patch fixes the problem, then it should be ancient history by your 4.4.0 kernel. -- 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/1313279 Title: xHCI host not responding to stop endpoint command Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 Hardware: Intel NUC D34010WYK (Core i3 4010U) Memory: 4 gigabytes USD device: PCTV 292e DVB-T tuner I have 2 PCTV 292e DVB-T tuners connected to the system. When I start to use either of the tuner, the xHCI host crashes. Since I'm booting from an USB disk. If I only connect 1 of the tuners, the system works ok. It does not matter which one of the tuners I connect. [ 68.990396] xhci_hcd :00:14.0: xHCI host not responding to stop endpoint command. [ 68.990402] xhci_hcd :00:14.0: Assuming host is dying, halting host. Sometimes this also leads to this: [ 638.183002] IP: [] usb_enable_link_state+0x2d/0x2f0 [ 638.183057] PGD 0 [ 638.183077] Oops: [#1] SMP I can also observe the same fault with OpenELEC Linux distribution that runs kernel 3.14 when I run the system from an internal SATA SSD drive (not from an external USB disk). lsusb -v: http://paste.ubuntu.com/7343384/ dmesg: http://sprunge.us/HMXH dmesg (crash type 2): http://sprunge.us/PSiX ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lubuntu-desktop 0.55 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Sun Apr 27 11:12:22 2014 InstallationDate: Installed on 2014-04-07 (19 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: lubuntu-meta UpgradeStatus: Upgraded to trusty on 2014-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1313279/+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 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
(collisionTwo from the same forum question above says he was experiencing this issue with an XPS 9560, mind you, which is a Kaby Lake Mobile CPU, so it's still a bit of conjecture until we get more specs from others experiencing the 'doesn't actually suspend and needs a hard reset to do anything' probem.) -- 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/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Confirmed Bug description: I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+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 1772960] Re: linux: 4.4.0-128.154 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772960 Title: linux: 4.4.0-128.154 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress 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 Released 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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: 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 1772962 (linux-lts-xenial), bug 1772963 (linux-aws) derivatives: bug 1772964 (linux-kvm), bug 1772965 (linux-snapdragon), bug 1772966 (linux-aws), bug 1772968 (linux-raspi2), bug 1772969 (linux-euclid) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772960/+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 1759723] Re: ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle hangs after hotplug CPU add operation.
(just for completeness reasons) Patches that were sent over: https://lists.ubuntu.com/archives/kernel-team/2018-May/thread.html#92233 -- 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/1759723 Title: ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle hangs after hotplug CPU add operation. Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: Problem Description: === Performed HOTPLUG cpu attach operation for the guest and guest console becomes unresponsive. Steps to re-create: == 1. updated boslcp3 host BMC :116 & PNOR: 20180302 levels 2. Installed Ubuntu1804 on boslcp3 host & guests with trap issue fixes root@boslcp3:/home# uname -a Linux boslcp3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:/home# uname -r 4.15.0-12-generic root@boslcp3g3:/kte/tools/setup.d# uname -a Linux boslcp3g3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3g3:/kte/tools/setup.d# uname -r 4.15.0-12-generic 3. Started HTX & stress-ng for on guest for 10-15 min 4. Cleaned up the tests to perform hot-plug and ensure enough memory and cpu was there (killed all Process using kill) 5. Performed cpu hot-plug and guest went into hung state Before Hotplug: root@boslcp3:~# virsh dumpxml boslcp3g3 | grep vcpu 64 root@boslcp3:~# 6. After this operation, guest becomes unrepsonsive as below root@boslcp3g3:~# [ 3626.140773] INFO: task jbd2/vda2-8:584 blocked for more than 120 seconds. [ 3626.146375] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.146457] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.146624] INFO: task systemd-journal:665 blocked for more than 120 seconds. [ 3626.146699] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.146768] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.146939] INFO: task rs:main Q:Reg:1995 blocked for more than 120 seconds. [ 3626.147016] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147088] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147285] INFO: task kworker/u128:2:57691 blocked for more than 120 seconds. [ 3626.147361] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147434] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147622] INFO: task smbd:1449 blocked for more than 120 seconds. [ 3626.147686] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147760] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147875] INFO: task smbd:1452 blocked for more than 120 seconds. [ 3626.147937] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148010] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.148110] INFO: task smbd:1454 blocked for more than 120 seconds. [ 3626.148173] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148245] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.148344] INFO: task cron:1461 blocked for more than 120 seconds. [ 3626.148406] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148488] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. root@boslcp3g3:~# root@boslcp3g3:~# ps -ef | grep stress-ng [ 3746.978098] INFO: task jbd2/vda2-8:584 blocked for more than 120 seconds. [ 3746.978221] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3746.978301] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3746.978447] INFO: task systemd-journal:665 blocked for more than 120 seconds. [ 3746.978534] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3746.978607] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4446.361899] systemd[1]: Failed to start Journal Service. [ 4897.632142] systemd[1]: Failed to start Journal Service.
[Kernel-packages] [Bug 1772931] Re: linux-aws: 4.15.0-1010.10 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1772931 Title: linux-aws: 4.15.0-1010.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid 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 promote-to-proposed series: Fix Released 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772927 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772931/+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 1775391] Re: kernel: Fix arch random implementation
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: New => Triaged ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- 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/1775391 Title: kernel: Fix arch random implementation Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: Description: kernel: Fix arch random implementation Symptom: arch_get_random_seed_long() invocations may slow down the interrupt handling on heavy interrupt producing loads. Problem: The existing random device driver calls arch_get_random_seed_long() in interrupt context. The current implementation of this function uses the PRNO(TRNG) instruction to provide good entropy. This instruction is relatively slow and expensive and may slow down the capacity of interrupts which can be handled per cpu. Solution: This fix reworks the arch_get_random_seed implementation. It introduces a buffer concept to decouple the delivery of random data via arch_get_random_seed*() from the generation of new random bytes and so does not limit the interrupt handling per cpu any more. Reproduction: Systems with heavy irq load show performance decrease. Component:kernel Upstream commit(s): kernel 4.18 966f53e750aedc5f59f9ccae6bbfb8f671c7c842 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775391/+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 1775390] Re: kernel: Fix memory leak on CCA and EP11 CPRB processing.
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: New => Triaged ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- 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/1775390 Title: kernel: Fix memory leak on CCA and EP11 CPRB processing. Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: Description: kernel: Fix memory leak on CCA and EP11 CPRB processing. Symptom: Kernel memory not freed when CCA or EP11 CPRB processing fails. Problem: kfree() in code error path missing. Solution: Slight rework of the malloc and free places. Reproduction: Run application which sends CCA or EP11 crypto requests to the crypto card(s). Now switch the cards offline with the help of chzcrypt. Monitor top or free output. Upstream commit(s): kernel 4.18 89a0c0ec0d2e3ce0ee9caa00f60c0c26ccf11c21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775390/+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 1729337] Re: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config
I'm happy to create a new bug report for this, however before I do I wanted to follow up here first. I've been working on a bionic VM template this week and the issue has resurfaced. Client (18.04) reboots daily at 3:00 a.m., and somewhere between 30 minutes and 2 hours later, the CIFS mount point stops responding. Meanwhile other clients (16.04, and Windows) continue chugging along merrily. A reboot sometimes fixes the problem, and sometimes the problem has fixed itself by 8am when I arrive. Here's some syslog debug output after the machine finishes booting. Yesterday it cleared up on its own. Today the server is still down 10 hours later. I would blame Java, except that the whole mount point becomes non- responsive when this happens, not just for that one process. Jun 6 03:00:37 localhost systemd[1]: Reached target Multi-User System. Jun 6 03:00:37 localhost systemd[1]: Starting Execute cloud user/final scripts... Jun 6 03:00:37 localhost systemd[1]: Reached target Graphical Interface. Jun 6 03:00:37 localhost systemd[1]: Starting Update UTMP about System Runlevel Changes... Jun 6 03:00:38 localhost systemd[1]: Started Update UTMP about System Runlevel Changes. Jun 6 03:00:38 localhost cloud-init[1531]: Cloud-init v. 18.2 running 'modules:final' at Wed, 06 Jun 2018 03:00:38 +. Up 23.72 seconds. Jun 6 03:00:38 localhost cloud-init[1531]: Cloud-init v. 18.2 finished at Wed, 06 Jun 2018 03:00:38 +. Datasource DataSourceNoCloud [seed=/var/lib/cloud/seed/nocloud-net][dsmode=net]. Up 23.84 seconds Jun 6 03:00:38 localhost systemd[1]: Started Execute cloud user/final scripts. Jun 6 03:00:38 localhost systemd[1]: Reached target Cloud-init target. Jun 6 03:00:38 localhost systemd[1]: Startup finished in 2.806s (kernel) + 21.078s (userspace) = 23.885s. Jun 6 03:00:39 localhost kernel: [ 24.927412] TCP: ens160: Driver has suspect GRO implementation, TCP performance may be compromised. Jun 6 03:00:51 localhost systemd-timesyncd[574]: Synchronized to time server 91.189.91.157:123 (ntp.ubuntu.com). Jun 6 03:14:28 localhost systemd[1]: Starting Message of the Day... Jun 6 03:14:30 localhost 50-motd-news[1699]: * Meltdown, Spectre and Ubuntu: What are the attack vectors, Jun 6 03:14:30 localhost 50-motd-news[1699]:how the fixes work, and everything else you need to know Jun 6 03:14:30 localhost 50-motd-news[1699]:- https://ubu.one/u2Know Jun 6 03:14:30 localhost systemd[1]: Started Message of the Day. Jun 6 03:15:48 localhost systemd[1]: Starting Cleanup of Temporary Directories... Jun 6 03:15:48 localhost systemd[1]: Started Cleanup of Temporary Directories. Jun 6 03:17:01 localhost CRON[1770]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jun 6 04:00:01 localhost CRON[1878]: (root) CMD (/mnt/www/config/backup_config.sh) Jun 6 04:17:01 localhost CRON[1916]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jun 6 04:17:33 localhost nslcd[1438]: [b141f2] failed to bind to LDAP server ldap://dc01.example.com: Can't contact LDAP server Jun 6 04:17:33 localhost nslcd[1438]: [b141f2] connected to LDAP server ldap://dc02.example.com Jun 6 04:30:01 localhost CRON[1938]: (root) CMD (/usr/sbin/ntpdate time-a.nist.gov time-b.nist.gov 0.pool.ntp.org 1.pool.ntp.org) Jun 6 04:30:01 localhost CRON[1937]: (CRON) info (No MTA installed, discarding output) Jun 6 05:12:02 localhost kernel: [ 7906.798052] CIFS VFS: Server cifshost.example.com has not responded in 120 seconds. Reconnecting... Jun 6 05:12:02 localhost kernel: [ 7906.800726] CIFS VFS: Free previous auth_key.response = 3e802799 Jun 6 05:13:10 localhost kernel: [ 7975.657719] INFO: task java:1672 blocked for more than 120 seconds. Jun 6 05:13:10 localhost kernel: [ 7975.657741] Not tainted 4.15.0-22-generic #24-Ubuntu Jun 6 05:13:10 localhost kernel: [ 7975.657757] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 6 05:13:10 localhost kernel: [ 7975.657779] javaD0 1672 1 0x8000 Jun 6 05:13:10 localhost kernel: [ 7975.657781] Call Trace: Jun 6 05:13:10 localhost kernel: [ 7975.657788] __schedule+0x297/0x8b0 Jun 6 05:13:10 localhost kernel: [ 7975.657791] ? __wake_up+0x13/0x20 Jun 6 05:13:10 localhost kernel: [ 7975.657792] schedule+0x2c/0x80 Jun 6 05:13:10 localhost kernel: [ 7975.657795] io_schedule+0x16/0x40 Jun 6 05:13:10 localhost kernel: [ 7975.657798] wait_on_page_bit_common+0xd8/0x160 Jun 6 05:13:10 localhost kernel: [ 7975.657800] ? page_cache_tree_insert+0xe0/0xe0 Jun 6 05:13:10 localhost kernel: [ 7975.657801] __filemap_fdatawait_range+0xfa/0x160 Jun 6 05:13:10 localhost kernel: [ 7975.657803] filemap_write_and_wait+0x4d/0x90 Jun 6 05:13:10 localhost kernel: [ 7975.657826] cifs_flush+0x43/0x90 [cifs] Jun 6 05:13:10 localhost kernel: [ 7975.657830] filp_close+0x2f/0x80 Jun 6 05:13:10 localhost kernel: [ 7975.657832] __close_fd+0x85/0xa0 Jun 6 05:13:10 localhost ker
[Kernel-packages] [Bug 1687791] Re: Install of kdump-tools fails
Still an issue on Bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1687791 Title: Install of kdump-tools fails Status in makedumpfile package in Ubuntu: Confirmed Bug description: When installing Ubuntu xenial via netimage, installation fails because of an error, when configuring the kdump-tools. /var/log/syslog says: ... May 2 22:15:17 in-target: Setting up grub2 (2.02~beta2-36ubuntu3.9) ...^M May 2 22:15:17 in-target: Setting up lxc-common (2.0.7-0ubuntu1~16.04.2) ...^M May 2 22:15:17 in-target: Running in chroot, ignoring request.^M May 2 22:15:17 in-target: invoke-rc.d: policy-rc.d denied execution of reload.^M May 2 22:15:17 in-target: Setting up grub-gfxpayload-lists (0.7) ...^M May 2 22:15:17 in-target: Processing triggers for libc-bin (2.23-0ubuntu7) ...^M May 2 22:15:17 in-target: Processing triggers for systemd (229-4ubuntu17) ...^M May 2 22:15:17 in-target: Processing triggers for ureadahead (0.100.0-19) ...^M May 2 22:15:17 in-target: Processing triggers for dbus (1.10.6-1ubuntu3.3) ...^M May 2 22:15:17 in-target: Errors were encountered while processing:^M May 2 22:15:17 in-target: kdump-tools^M May 2 22:15:17 in-target: linux-crashdump^M May 2 22:15:18 in-target: E: Sub-process /usr/bin/dpkg returned an error code (1) May 2 22:15:18 in-target: Setting up kdump-tools (1:1.5.9-5ubuntu0.4) ... May 2 22:15:18 in-target: dpkg: error processing package kdump-tools (--configure): May 2 22:15:18 in-target: subprocess installed post-installation script returned error exit status 1 May 2 22:15:18 in-target: dpkg: dependency problems prevent configuration of linux-crashdump: May 2 22:15:18 in-target: linux-crashdump depends on kdump-tools; however: May 2 22:15:18 in-target: Package kdump-tools is not configured yet. May 2 22:15:18 in-target: May 2 22:15:18 in-target: dpkg: error processing package linux-crashdump (--configure): May 2 22:15:18 in-target: dependency problems - leaving unconfigured May 2 22:15:18 in-target: Errors were encountered while processing: May 2 22:15:18 in-target: kdump-tools May 2 22:15:18 in-target: linux-crashdump May 2 22:15:18 main-menu[616]: WARNING **: Configuring 'pkgsel' failed with error code 100 May 2 22:15:18 main-menu[616]: WARNING **: Menu item 'pkgsel' failed. After this the 'Select and install software' dialog pops up and says, that 'Installation step failed'. If one presses '', one gets bombed back into the 'Ubuntu installer main menu'. Now you get into a loop, when choosing the 'Select and install software' item from the menu. Installer image is 'Linux foo 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 GNU/Linux'. The only workaround found so far is: cp -p /target/var/lib/dpkg/info/kdump-tools.postinst \ /target/var/lib/dpkg/info/kdump-tools.postinst.suck printf '#!/bin/sh\nexit 0\n' \ >/target/var/lib/dpkg/info/kdump-tools.postinst To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1687791/+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 1766857] Re: [Hyper-V] KVP daemon fails to start
In my own VMs, this does not affect linux-azure, it only affects the generic 4.15 kernel. -- 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/1766857 Title: [Hyper-V] KVP daemon fails to start Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-azure source package in Bionic: Confirmed Bug description: While testing Bionic daily build with kernel 4.15.0-20-generic we saw that there are 2 issues with the KVP daemon: 1. KVP daemon crashes after approximatively 2 minutes of uptime and it enters in a failed state. The daemon can be manually started and it enters back in active (running) state. The error messages from /var/log/syslog after the daemon enters the failed state are the following: Apr 25 04:28:46 bionicDaily KVP: read failed; error:9 Bad file descriptor Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Failed with result 'exit-code'. Apr 25 04:28:59 bionicDaily systemd[1]: Started Hyper-V KVP Protocol Daemon. Note: There was a simmilar issue discussed on this thread https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664663, but the fixing commit seems to be inclued in this Bionic build. 2. After the KVP daemon is being started the following messages appear: Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: /usr/libexec/hypervkvpd/hv_get_dns_info: not found Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: /usr/libexec/hypervkvpd/hv_get_dhcp_info: not found The above binaries are present on the system, but the their actual path is /usr/sbin/hv_get_dns_info and /usr/sbin/hv_get_dhcp_info. Either the hv_get_dhcp_info and hv_get_dns_info binaries should be placed in the location where the daemon is looking for (/usr/libexec/hypervkvpd/), or the daemon should be set to search for the binaries in the /usr/sbin directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766857/+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 1775443] [NEW] Ubuntu 18.04 Bluetooth Crash
Public bug reported: Posted a question here and it was recommended that I file a kernel bug report: https://askubuntu.com/questions/1044235/18-04-bluetooth-crashing $ lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 $ apt-cache policy bluez bluez: Installed: 5.48-0ubuntu3 Candidate: 5.48-0ubuntu3 Version table: *** 5.48-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy blueman blueman: Installed: 2.0.5-1ubuntu1 Candidate: 2.0.5-1ubuntu1 Version table: *** 2.0.5-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 6 10:48:07 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-01-12 (145 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-06-01 (4 days ago) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 bionic kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1775443 Title: Ubuntu 18.04 Bluetooth Crash Status in linux-signed package in Ubuntu: New Bug description: Posted a question here and it was recommended that I file a kernel bug report: https://askubuntu.com/questions/1044235/18-04-bluetooth- crashing $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy bluez bluez: Installed: 5.48-0ubuntu3 Candidate: 5.48-0ubuntu3 Version table: *** 5.48-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy blueman blueman: Installed: 2.0.5-1ubuntu1 Candidate: 2.0.5-1ubuntu1 Version table: *** 2.0.5-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 6 10:48:07 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-01-12 (145 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-06-01 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1775443/+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 1774126] Re: linux-oem: 4.13.0-1030.33 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1774126 Title: linux-oem: 4.13.0-1030.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed 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 Released 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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1774124 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774126/+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 1772927] Re: linux: 4.15.0-23.25 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772927 Title: linux: 4.15.0-23.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed 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 Released 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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: 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 1772935 (linux-hwe-edge), bug 1772940 (linux-azure), bug 1772942 (linux-azure-edge) derivatives: bug 1772929 (linux-raspi2), bug 1772930 (linux-azure), bug 1772931 (linux-aws), bug 1772932 (linux-kvm), bug 1772933 (linux-oem), bug 1772934 (linux-gcp) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772927/+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 1772934] Re: linux-gcp: 4.15.0-1009.9 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released -- 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/1772934 Title: linux-gcp: 4.15.0-1009.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid 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 promote-to-proposed series: Fix Released 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1772927 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772934/+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 1766857] Re: [Hyper-V] KVP daemon fails to start
Commit 7fa32e5ec28b was mentioned in the descriptions. However, that commit has been in mainlien since 4.15-rc3, so it's always been in 18.04. We may want to split the two issues in to two separate bugs, so they each get addressed. Do both issues still happen with the latest Bionic kernel? Per comment #6, it sounds liek the second issues still happens. How about the first issue, where the KVP daemon crashes after approximatively 2 minutes of uptime? -- 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/1766857 Title: [Hyper-V] KVP daemon fails to start Status in linux package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux-azure source package in Bionic: Invalid Bug description: While testing Bionic daily build with kernel 4.15.0-20-generic we saw that there are 2 issues with the KVP daemon: 1. KVP daemon crashes after approximatively 2 minutes of uptime and it enters in a failed state. The daemon can be manually started and it enters back in active (running) state. The error messages from /var/log/syslog after the daemon enters the failed state are the following: Apr 25 04:28:46 bionicDaily KVP: read failed; error:9 Bad file descriptor Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Failed with result 'exit-code'. Apr 25 04:28:59 bionicDaily systemd[1]: Started Hyper-V KVP Protocol Daemon. Note: There was a simmilar issue discussed on this thread https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664663, but the fixing commit seems to be inclued in this Bionic build. 2. After the KVP daemon is being started the following messages appear: Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: /usr/libexec/hypervkvpd/hv_get_dns_info: not found Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: /usr/libexec/hypervkvpd/hv_get_dhcp_info: not found The above binaries are present on the system, but the their actual path is /usr/sbin/hv_get_dns_info and /usr/sbin/hv_get_dhcp_info. Either the hv_get_dhcp_info and hv_get_dns_info binaries should be placed in the location where the daemon is looking for (/usr/libexec/hypervkvpd/), or the daemon should be set to search for the binaries in the /usr/sbin directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766857/+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 1766857] Re: [Hyper-V] KVP daemon fails to start
Commit 7fa32e5ec28b was actually mentioned in bug 1664663, an I don't think it factors into this bug. ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux-azure (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-azure (Ubuntu Bionic) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766857 Title: [Hyper-V] KVP daemon fails to start Status in linux package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux-azure source package in Bionic: Invalid Bug description: While testing Bionic daily build with kernel 4.15.0-20-generic we saw that there are 2 issues with the KVP daemon: 1. KVP daemon crashes after approximatively 2 minutes of uptime and it enters in a failed state. The daemon can be manually started and it enters back in active (running) state. The error messages from /var/log/syslog after the daemon enters the failed state are the following: Apr 25 04:28:46 bionicDaily KVP: read failed; error:9 Bad file descriptor Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Failed with result 'exit-code'. Apr 25 04:28:59 bionicDaily systemd[1]: Started Hyper-V KVP Protocol Daemon. Note: There was a simmilar issue discussed on this thread https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664663, but the fixing commit seems to be inclued in this Bionic build. 2. After the KVP daemon is being started the following messages appear: Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: /usr/libexec/hypervkvpd/hv_get_dns_info: not found Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: /usr/libexec/hypervkvpd/hv_get_dhcp_info: not found The above binaries are present on the system, but the their actual path is /usr/sbin/hv_get_dns_info and /usr/sbin/hv_get_dhcp_info. Either the hv_get_dhcp_info and hv_get_dns_info binaries should be placed in the location where the daemon is looking for (/usr/libexec/hypervkvpd/), or the daemon should be set to search for the binaries in the /usr/sbin directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766857/+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 1772972] Re: linux: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/prepare-package-lbm Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux (Ubuntu Precise) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772972 Title: linux: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-lbm series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: Invalid 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: derivatives: To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772972/+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 1775443] Re: Ubuntu 18.04 Bluetooth Crash
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1775443 Title: Ubuntu 18.04 Bluetooth Crash Status in linux package in Ubuntu: New Status in linux-signed package in Ubuntu: New Bug description: Here's the output of `grep blue /var/log/syslog`: Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:dev_class_changed_callback() Class: 0x00 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:new_settings_callback() Settings: 0x0ada Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:settings_changed() Changed settings: 0x0001 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:cancel_passive_scanning() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove_connection() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_stop() adapter /org/bluez/hci0 has been disabled Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:att_disconnected_cb() Software caused connection abort (103) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: connected -> disconnecting (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=1 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150: device F9:9B:77:D9:08:61 profile input-hog state changed: disconnecting -> disconnected (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/gatt-client.c:btd_gatt_client_disconnected() Device disconnected. Cleaning up. Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: attrib/gattrib.c:g_attrib_unref() 0x565278add490: g_attrib_unref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:index_removed() index 0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_unregister() Unregister path: /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/adapter.c:adapter_remove() Removing adapter /org/bluez/hci0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/device.c:device_remove() Removing device /org/bluez/hci0/dev_F9_9B_77_D9_08_61 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2320: device F9:9B:77:D9:08:61 profile batt-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/battery/battery.c:batt_remove() BATT profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2320: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278ad2230: device F9:9B:77:D9:08:61 profile deviceinfo state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278ad2230: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adce30: device F9:9B:77:D9:08:61 profile gap-profile state changed: disconnected -> unavailable (0) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: profiles/gap/gas.c:gap_remove() GAP profile remove (F9:9B:77:D9:08:61) Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:btd_service_unref() 0x565278adce30: ref=0 Jun 6 09:12:41 Precision-5520 bluetoothd[3189]: src/service.c:change_state() 0x565278adc150
[Kernel-packages] [Bug 1775390] Re: kernel: Fix memory leak on CCA and EP11 CPRB processing.
** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Joseph Salisbury (jsalisbury) ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- 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/1775390 Title: kernel: Fix memory leak on CCA and EP11 CPRB processing. Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Description: kernel: Fix memory leak on CCA and EP11 CPRB processing. Symptom: Kernel memory not freed when CCA or EP11 CPRB processing fails. Problem: kfree() in code error path missing. Solution: Slight rework of the malloc and free places. Reproduction: Run application which sends CCA or EP11 crypto requests to the crypto card(s). Now switch the cards offline with the help of chzcrypt. Monitor top or free output. Upstream commit(s): kernel 4.18 89a0c0ec0d2e3ce0ee9caa00f60c0c26ccf11c21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775390/+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 1775391] Re: kernel: Fix arch random implementation
** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Joseph Salisbury (jsalisbury) -- 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/1775391 Title: kernel: Fix arch random implementation Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: In Progress Bug description: Description: kernel: Fix arch random implementation Symptom: arch_get_random_seed_long() invocations may slow down the interrupt handling on heavy interrupt producing loads. Problem: The existing random device driver calls arch_get_random_seed_long() in interrupt context. The current implementation of this function uses the PRNO(TRNG) instruction to provide good entropy. This instruction is relatively slow and expensive and may slow down the capacity of interrupts which can be handled per cpu. Solution: This fix reworks the arch_get_random_seed implementation. It introduces a buffer concept to decouple the delivery of random data via arch_get_random_seed*() from the generation of new random bytes and so does not limit the interrupt handling per cpu any more. Reproduction: Systems with heavy irq load show performance decrease. Component:kernel Upstream commit(s): kernel 4.18 966f53e750aedc5f59f9ccae6bbfb8f671c7c842 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775391/+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
