[Kernel-packages] [Bug 1790454] [NEW] Bluetooth (btintel) stops working aster suspend/resume
Public bug reported: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1790454 Title: Bluetooth (btintel) stops working aster suspend/resume Status in linux package in Ubuntu: New Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btu
[Kernel-packages] [Bug 1790454] Re: Bluetooth (btintel) stops working aster suspend/resume
** Attachment added: "lsusb-v.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5183918/+files/lsusb-v.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/1790454 Title: Bluetooth (btintel) stops working aster suspend/resume Status in linux package in Ubuntu: New Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+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 1790454] Re: Bluetooth (btintel) stops working aster suspend/resume
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5183919/+files/lspci-vnvn.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/1790454 Title: Bluetooth (btintel) stops working aster suspend/resume Status in linux package in Ubuntu: New Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+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 1790454] Re: Bluetooth (btintel) stops working aster suspend/resume
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5183920/+files/version.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/1790454 Title: Bluetooth (btintel) stops working aster suspend/resume Status in linux package in Ubuntu: New Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+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 1790445] Re: growfile in ubunt_ltp test will eat up all the disk space
** Description changed: - This is a KVM node with 8G disk space, running with linux-kvm kernel + There are 4 different KVM node, all deployed with Bionic + 8G disk + space: + A: 18.04 + Disk space: + /dev/vda1 7.3G 4.7G 2.3G 68% / + + B: 18.04 + proposed packages + Disk space: + /dev/vda1 7.3G 5.2G 1.7G 76% / + + C: 18.04 + linux-kvm kernel + Disk space: + /dev/vda1 7.3G 4.9G 2.1G 71% / + + D: 18.04 + linux-kvm kernel + proposed packages: + Disk space: + /dev/vda1 7.3G 5.5G 1.5G 79% / + + For node A, C (2.3, 2.1G free space), only the gf18 test will fail: <<>> - tag=gf01 stime=1535956550 - cmdline="growfiles -W gf01 -b -e 1 -u -i 0 -L 20 -w -C 1 -l -I r -T 10 -f glseek20 -S 2 -d $TMPDIR" + tag=gf18 stime=1535959767 + cmdline="growfiles -W gf18 -b -e 1 -i 0 -L 120 -w -u -r 10-5000 -I r -l -S 2 -f Lgf04_ -d $TMPDIR" contacts="" analysis=exit <<>> - growfiles(gf01): 1628 growfiles.c/2037: 176574 tlibio.c/994 pwrite(6, buf, 1, 723247103) ret:-1, errno=28 No space left on device - gf011 TFAIL : growfiles.c:132: Test failed + growfiles(gf18): 1218 growfiles.c/2037: 523098 tlibio.c/735 write(6, buf, 1) ret:-1, errno=28 No space left on device + gf181 TFAIL : growfiles.c:132: Test failed <<>> initiation_status="ok" - duration=12 termination_type=exited termination_id=1 corefile=no - cutime=416 cstime=707 + duration=62 termination_type=exited termination_id=1 corefile=no + cutime=1247 cstime=2400 <<>> + + For node B (1.7G free space), gf15 and gf18 will fail + The failure in gf15 is not "No space left on device": + <<>> + tag=gf15 stime=1535960672 + cmdline="growfiles -W gf15 -b -e 1 -u -r 1-49600 -I r -u -i 0 -L 120 -f Lgfile1 -d $TMPDIR" + contacts="" + analysis=exit + <<>> + growfiles(gf15): 1140 growfiles.c/2249: 78642 tlibio.c/1002 pwrite(6, buf, 46818, 1951330224) returned=80 + growfiles(gf15): 1140 growfiles.c/1752: 78642 Hit max errors value of 1 + gf151 TFAIL : growfiles.c:132: Test failed + <<>> + initiation_status="ok" + duration=17 termination_type=exited termination_id=1 corefile=no + cutime=1306 cstime=302 + <<>> + + + For node D (1.5G free space), gf14, gf15 and gf18 will fail ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1020-kvm 4.15.0-1020.20 ProcVersionSignature: User Name 4.15.0-1020.20-kvm 4.15.18 Uname: Linux 4.15.0-1020-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Mon Sep 3 06:15:36 2018 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1790445 Title: growfile in ubunt_ltp test will eat up all the disk space Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: There are 4 different KVM node, all deployed with Bionic + 8G disk space: A: 18.04 Disk space: /dev/vda1 7.3G 4.7G 2.3G 68% / B: 18.04 + proposed packages Disk space: /dev/vda1 7.3G 5.2G 1.7G 76% / C: 18.04 + linux-kvm kernel Disk space: /dev/vda1 7.3G 4.9G 2.1G 71% / D: 18.04 + linux-kvm kernel + proposed packages: Disk space: /dev/vda1 7.3G 5.5G 1.5G 79% / For node A, C (2.3, 2.1G free space), only the gf18 test will fail: <<>> tag=gf18 stime=1535959767 cmdline="growfiles -W gf18 -b -e 1 -i 0 -L 120 -w -u -r 10-5000 -I r -l -S 2 -f Lgf04_ -d $TMPDIR" contacts="" analysis=exit <<>> growfiles(gf18): 1218 growfiles.c/2037: 523098 tlibio.c/735 write(6, buf, 1) ret:-1, errno=28 No space left on device gf181 TFAIL : growfiles.c:132: Test failed <<>> initiation_status="ok" duration=62 termination_type=exited termination_id=1 corefile=no cutime=1247 cstime=2400 <<>> For node B (1.7G free space), gf15 and gf18 will fail The failure in gf15 is not "No space left on device": <<>> tag=gf15 stime=1535960672 cmdline="growfiles -W gf15 -b -e 1 -u -r 1-49600 -I r -u -i 0 -L 120 -f Lgfile1 -d $TMPDIR" contacts="" analysis=exit <<>> growfiles(gf15): 1140 growfiles.c/2249: 78642 tlibio.c/1002 pwrite(6, buf, 46818, 1951330224) returned=80 growfiles(gf15): 1140 growfiles.c/1752: 78642 Hit max errors value of 1 gf151 TFAIL : growfiles.c:132: Test failed <<>> initiation_status="ok" duration=17 termination_type=exited termination_id=1 corefile=no cutime=1306 cstime=302 <<>> For node D (1.5G free space), gf14, gf15 and gf18 will fail ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1020-kvm 4.15.0-1020.20 ProcVersionSignature: User Name 4.15.0-1020.20-kvm 4.15.18 Uname: Linux 4.15.0-1020-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Mon Sep 3 06:15:36 2018 SourcePackage: linux-kvm UpgradeStatus: No upgrade log pre
[Kernel-packages] [Bug 1790454] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1790454 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790454 Title: Bluetooth (btintel) stops working aster suspend/resume Status in linux package in Ubuntu: Incomplete Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1763144] Re: Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows
I think, we have a problem here, that needs to be solved on multiple issues. * there's throttling hitting in to avoid a dGPU reach its fall-off limit which is 76° (T580, i7-8550u, MX150). The only possible way to stay below this thermal limit is to power down the CPU massively, which leads to => * the dGPU isn't throttling down itself enough. In tests (glxsphere) my findings are: dGPU runs at about 1600-1700Mhz, not going down further. I guess this is a result of the gpu itself has a thermal limit of around 95° and gpu's own throttling will kick in much later than 76°, making the gpu not helping in cooling down with slowing down more. I wasn't able to get a reading of the power consumed by gpu, nvidia-smi does not offer these (nvidia-396). Thus leading to => * There's an imbalance between gpu's and cpu's abilities to thermal adapt. As gpu isn't able to, cpu is and does which leads to => a) a system running on brakes to manage heat, for to stay below a poosible gpu fall-off (full gpu power and frequency stable along time with cpu going down to only 3-5W or b) a system running at the possible performance with using the cpu's full potential, but only being able to use ⅓ of dGPU's capacities Conclusion from my perspective: There's a need to balance :-) * there's a need to have influence on gpu's abilities to throttle earlier (=> nvidia) * Lenovo-fix being enhanced to provide some kind of profiles, which are dynamically providing usecase profiles (easiest way to test is: set temp in Lenovo-fix to max 75°. As both, cpu & dGPU producing heat and 76° is fall-off, staying below that keeps system from throttling.) -- 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/1763144 Title: Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows Status in linux package in Ubuntu: Confirmed Bug description: A ThinkPad T480s under windows has a power limit of 44W, both short and long term, with a thermal maximum of about 93C or so. Under Linux, the power limits are 44W and 15W (short) or so, and the thermal limit is 80C, causing a significant performance loss. Looking at MSR and MCHBAR values, we can see that the values are correctly at 44W in the MSR, but the MCHBAR is set to a lower value: $ sudo rdmsr -a 0x610 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0 0x0042816000dd8078 Setting the MCHBAR to the same value as the MSR register solves the problem. At some point intel-rapl seems to reduce overall frequency to 600 MHz, though. The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24 -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting in performance comparative to Windows. Most of the analysis is based on the analysis in https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/ This applies to all bionic kernels I have tested so far, including Ubuntu 4.15.0-13.14-generic 4.15.10 --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0p: jak5881 F...m pulseaudio /dev/snd/controlC2: jak5881 F pulseaudio /dev/snd/controlC1: jak5881 F pulseaudio /dev/snd/controlC0: jak5881 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-14 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 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 Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET31W (1.08 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00
[Kernel-packages] [Bug 1790219] Re: Stuck on boot of my PC after switching to Nvidia-driver-390 proprietary driver and rebooting
Thanks for your report. Could you please attach the journal from the boot that failed? You can get a list of the boots with the command: journalctl --list-boots Then the journal of a given boot with: journalctl -b [id] Where id is correspond to the id of the boot returned by list-boots Thanks. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1790219 Title: Stuck on boot of my PC after switching to Nvidia-driver-390 proprietary driver and rebooting Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: I was carrying out this testcase for proprietary Nvidia drivers testing: http://xorg.qa.ubuntu.com/qatracker/testcases/1704/info. After having installed Ubuntu 18.10 on a new partition on my PC, I switched to Nvidia-driver-390 proprietary driver from Additional Drivers tab of Software & Update and rebooted my PC. On reboot I got low resolution Ubuntu logo, pressing F1 I could read this message: (1 of 2) A start Job is running for Hold until snapd is fully seeded (15 min 23s/ no limit). (2 of 2) A start Job is running for Hold until snapd is fully seeded (15 min 25s/ no limit). I rebooted after waiting 15 minutes as I was tired of waiting. This is my display hardware: *-display description: VGA compatible controller product: GM206 [GeForce GTX 960] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:125 memory:de00-deff memory:c000-cfff memory:d000-d1ff ioport:e000(size=128) memory:c-d Link to the testcase revision Edit result My PC is a: product: XPS 8900 (06B8) vendor: Dell Inc. width: 64 bits To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1790219/+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 1790457] [NEW] kernel: improve spectre mitigation
You have been subscribed to a public bug: Description will follow ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-171040 severity-high targetmilestone-inin--- -- kernel: improve spectre mitigation https://bugs.launchpad.net/bugs/1790457 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 1790445] Re: growfiles in ubunt_ltp test will eat up all the disk space
** Summary changed: - growfile in ubunt_ltp test will eat up all the disk space + growfiles in ubunt_ltp test will eat up all the disk space -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1790445 Title: growfiles in ubunt_ltp test will eat up all the disk space Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: There are 4 different KVM node, all deployed with Bionic + 8G disk space: A: 18.04 Disk space: /dev/vda1 7.3G 4.7G 2.3G 68% / B: 18.04 + proposed packages Disk space: /dev/vda1 7.3G 5.2G 1.7G 76% / C: 18.04 + linux-kvm kernel Disk space: /dev/vda1 7.3G 4.9G 2.1G 71% / D: 18.04 + linux-kvm kernel + proposed packages: Disk space: /dev/vda1 7.3G 5.5G 1.5G 79% / For node A, C (2.3, 2.1G free space), only the gf18 test will fail: <<>> tag=gf18 stime=1535959767 cmdline="growfiles -W gf18 -b -e 1 -i 0 -L 120 -w -u -r 10-5000 -I r -l -S 2 -f Lgf04_ -d $TMPDIR" contacts="" analysis=exit <<>> growfiles(gf18): 1218 growfiles.c/2037: 523098 tlibio.c/735 write(6, buf, 1) ret:-1, errno=28 No space left on device gf181 TFAIL : growfiles.c:132: Test failed <<>> initiation_status="ok" duration=62 termination_type=exited termination_id=1 corefile=no cutime=1247 cstime=2400 <<>> For node B (1.7G free space), gf15 and gf18 will fail The failure in gf15 is not "No space left on device": <<>> tag=gf15 stime=1535960672 cmdline="growfiles -W gf15 -b -e 1 -u -r 1-49600 -I r -u -i 0 -L 120 -f Lgfile1 -d $TMPDIR" contacts="" analysis=exit <<>> growfiles(gf15): 1140 growfiles.c/2249: 78642 tlibio.c/1002 pwrite(6, buf, 46818, 1951330224) returned=80 growfiles(gf15): 1140 growfiles.c/1752: 78642 Hit max errors value of 1 gf151 TFAIL : growfiles.c:132: Test failed <<>> initiation_status="ok" duration=17 termination_type=exited termination_id=1 corefile=no cutime=1306 cstime=302 <<>> For node D (1.5G free space), gf14, gf15 and gf18 will fail ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1020-kvm 4.15.0-1020.20 ProcVersionSignature: User Name 4.15.0-1020.20-kvm 4.15.18 Uname: Linux 4.15.0-1020-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Mon Sep 3 06:15:36 2018 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1790445/+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 1766565] Re: Unable to insert sysdig_probe module on B-KVM kernel
http://kernel.ubuntu.com/git/ubuntu/kernel-testing.git/commit/?h=master- next&id=7101478d334d9a816b1d7d6bc72f1348d170b884 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1766565 Title: Unable to insert sysdig_probe module on B-KVM kernel Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in sysdig package in Ubuntu: New Bug description: The sysdig-dkms module cannot be installed on the B-KVM kernel once before (bug 1764693), but now the installation works since 4.15.0-1007 However, when you try to insert the module, it will complain about: $ sudo modprobe sysdig-probe modprobe: ERROR: could not insert 'sysdig_probe': Unknown symbol in module, or unknown parameter (see dmesg) Log in dmesg: [ 1989.967807] sysdig_probe: loading out-of-tree module taints kernel. [ 1989.967924] sysdig_probe: module verification failed: signature and/or required key missing - tainting kernel [ 1989.967986] sysdig_probe: Unknown symbol tracepoint_probe_unregister (err 0) [ 1989.968090] sysdig_probe: Unknown symbol for_each_kernel_tracepoint (err 0) [ 1989.968094] sysdig_probe: Unknown symbol tracepoint_probe_register (err 0) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1007-kvm 4.15.0-1007.7 ProcVersionSignature: User Name 4.15.0-1007.7-kvm 4.15.17 Uname: Linux 4.15.0-1007-kvm x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Tue Apr 24 11:31:08 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1766565/+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 1790445] Re: growfiles in ubunt_ltp test will eat up all the disk space
Issue reported upstream: https://github.com/linux-test-project/ltp/issues/389 ** Bug watch added: github.com/linux-test-project/ltp/issues #389 https://github.com/linux-test-project/ltp/issues/389 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1790445 Title: growfiles in ubunt_ltp test will eat up all the disk space Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: There are 4 different KVM node, all deployed with Bionic + 8G disk space: A: 18.04 Disk space: /dev/vda1 7.3G 4.7G 2.3G 68% / B: 18.04 + proposed packages Disk space: /dev/vda1 7.3G 5.2G 1.7G 76% / C: 18.04 + linux-kvm kernel Disk space: /dev/vda1 7.3G 4.9G 2.1G 71% / D: 18.04 + linux-kvm kernel + proposed packages: Disk space: /dev/vda1 7.3G 5.5G 1.5G 79% / For node A, C (2.3, 2.1G free space), only the gf18 test will fail: <<>> tag=gf18 stime=1535959767 cmdline="growfiles -W gf18 -b -e 1 -i 0 -L 120 -w -u -r 10-5000 -I r -l -S 2 -f Lgf04_ -d $TMPDIR" contacts="" analysis=exit <<>> growfiles(gf18): 1218 growfiles.c/2037: 523098 tlibio.c/735 write(6, buf, 1) ret:-1, errno=28 No space left on device gf181 TFAIL : growfiles.c:132: Test failed <<>> initiation_status="ok" duration=62 termination_type=exited termination_id=1 corefile=no cutime=1247 cstime=2400 <<>> For node B (1.7G free space), gf15 and gf18 will fail The failure in gf15 is not "No space left on device": <<>> tag=gf15 stime=1535960672 cmdline="growfiles -W gf15 -b -e 1 -u -r 1-49600 -I r -u -i 0 -L 120 -f Lgfile1 -d $TMPDIR" contacts="" analysis=exit <<>> growfiles(gf15): 1140 growfiles.c/2249: 78642 tlibio.c/1002 pwrite(6, buf, 46818, 1951330224) returned=80 growfiles(gf15): 1140 growfiles.c/1752: 78642 Hit max errors value of 1 gf151 TFAIL : growfiles.c:132: Test failed <<>> initiation_status="ok" duration=17 termination_type=exited termination_id=1 corefile=no cutime=1306 cstime=302 <<>> For node D (1.5G free space), gf14, gf15 and gf18 will fail ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1020-kvm 4.15.0-1020.20 ProcVersionSignature: User Name 4.15.0-1020.20-kvm 4.15.18 Uname: Linux 4.15.0-1020-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Mon Sep 3 06:15:36 2018 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1790445/+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 1790457] [NEW] kernel: improve spectre mitigation
Public bug reported: Description will follow ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-171040 severity-high targetmilestone-inin--- ** Tags added: architecture-s39064 bugnameltc-171040 severity-high targetmilestone-inin--- ** 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/1790457 Title: kernel: improve spectre mitigation Status in linux package in Ubuntu: New Bug description: Description will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790457/+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 1788567] Re: System takes long time to read device via Thunderbolt 3 port
This commit has been included in 4.15.0-1018.21 and 4.15.0-34.37 ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: hwe-next Status: New => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: New => 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/1788567 Title: System takes long time to read device via Thunderbolt 3 port Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: [Impact] On Dell XPS 13 with Dell TB16 docking station, sometimes the devices on docking station do not show up or takes couple minutes to be recognized. [Fix] This issue doesn't exist in 4.16 vanilla kernel, and after bisected the kernel and found below commit fixes this issue. cc5db3150e87 net: qcom/emac: Use proper free methods during TX Applied this commit on top of Bionic 4.15 kernel and confirmed it works. [Regression Potential] Low, this commit is more like a patch fixes a bug which has been introduced since the driver was created. It aligns the dma_map and dma_unmap methods which might cause issue in some cases. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1788567/+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 1763144] Re: Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows
This bug was about different power limits for the non-dGPU version compared to Windows. It turned out that the power limits in Windows are broken, and the ones in Linux are correct, so this bug is in fact Invalid. For the dGPU, I'm not sure what the intention is. Maybe report a bug against the nvidia driver if you think it's wrong? -- 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/1763144 Title: Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows Status in linux package in Ubuntu: Invalid Bug description: A ThinkPad T480s under windows has a power limit of 44W, both short and long term, with a thermal maximum of about 93C or so. Under Linux, the power limits are 44W and 15W (short) or so, and the thermal limit is 80C, causing a significant performance loss. Looking at MSR and MCHBAR values, we can see that the values are correctly at 44W in the MSR, but the MCHBAR is set to a lower value: $ sudo rdmsr -a 0x610 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0 0x0042816000dd8078 Setting the MCHBAR to the same value as the MSR register solves the problem. At some point intel-rapl seems to reduce overall frequency to 600 MHz, though. The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24 -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting in performance comparative to Windows. Most of the analysis is based on the analysis in https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/ This applies to all bionic kernels I have tested so far, including Ubuntu 4.15.0-13.14-generic 4.15.10 --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0p: jak5881 F...m pulseaudio /dev/snd/controlC2: jak5881 F pulseaudio /dev/snd/controlC1: jak5881 F pulseaudio /dev/snd/controlC0: jak5881 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-14 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 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 Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET31W (1.08 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763144/+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 1763144] Re: Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows
This bug was about different power limits for the non-dGPU version compared to Windows. It turned out that the power limits in Windows are broken, and the ones in Linux are correct, so this bug is in fact Invalid. For the dGPU, I'm not sure what the intention is. Maybe report a bug against the nvidia driver if you think it's wrong? ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1763144 Title: Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows Status in linux package in Ubuntu: Invalid Bug description: A ThinkPad T480s under windows has a power limit of 44W, both short and long term, with a thermal maximum of about 93C or so. Under Linux, the power limits are 44W and 15W (short) or so, and the thermal limit is 80C, causing a significant performance loss. Looking at MSR and MCHBAR values, we can see that the values are correctly at 44W in the MSR, but the MCHBAR is set to a lower value: $ sudo rdmsr -a 0x610 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0 0x0042816000dd8078 Setting the MCHBAR to the same value as the MSR register solves the problem. At some point intel-rapl seems to reduce overall frequency to 600 MHz, though. The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24 -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting in performance comparative to Windows. Most of the analysis is based on the analysis in https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/ This applies to all bionic kernels I have tested so far, including Ubuntu 4.15.0-13.14-generic 4.15.10 --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0p: jak5881 F...m pulseaudio /dev/snd/controlC2: jak5881 F pulseaudio /dev/snd/controlC1: jak5881 F pulseaudio /dev/snd/controlC0: jak5881 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-14 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 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 Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET31W (1.08 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763144/+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 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04
Same problem. Version: Lubuntu 18.04.01 Kernel: 4.15.0.33-generic Dell Vostro 1000, AMD Athlon 64 x2 Dual core TK-55 Kingston SSD -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1594023 Title: Poweroff or reboot hangs. Laptop won't shutdown. 16.04 Status in linux package in Ubuntu: Confirmed Bug description: This is about a fresh Ubuntu 16.04 install on a new laptop (asus x540sa). After pressing the shutdown button in the start menu; the shutdown procedure starts and in the final splash screen the system just hangs. Tried a second time by pressing Esc once the splash screen showed up and I saw that it reaches the line "Reached target shutdown" and just stops there, no matter how long I leave it there the machine won't turn off. I also tried a Kubuntu 16.04 fresh install on the same machine and it hanged too at the final splash screen where the pulsating logo stopped. Then I tried with Esc only to see the exact same line in the end. The issue seems to affect lately quite many users as shown by the google results of the past month / week or so. I have also tried shutting down from the console with shutdown -and all the parameters after that suggested online- and sudo poweroff but unfortunately they didn't do the trick. The exact same situation occurred. Unmounting the swap as suggested online doesn't work. Also rebooting the system is not working either due to the same issue. So right now the only way for me to poweroff the machine is to press the power button on the keyboard continuously. Reproducible: Always Steps to Reproduce: 1.Install OS 2.Do something, anything or nothing 3.Try to shutdown or reboot Actual Results: The computer is not shutting down: "Reached target shutdown" and hangs there. Expected Results: Powering off the machine. For what it's worth, closing the lid won't suspend the system, but using the menu buttons for suspension will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790454] Re: Bluetooth (btintel) stops working aster suspend/resume
apport information ** Tags added: apport-collected cosmic ** Description changed: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. - The first kernel on which this error occurred was 4.17.0-6-generic. - Before that, I used 4.15.0-25-generic which works perfectly. + The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu9 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/pcmC0D0p: bas4871 F...m pulseaudio + /dev/snd/controlC0: bas4871 F pulseaudio + CurrentDesktop: GNOME + DistroRelease: Ubuntu 18.10 + HibernationDevice: + RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 + #RESUME=/dev/dm-2 + #RESUME=/dev/mapper/regan-swap + InstallationDate: Installed on 2016-12-22 (619 days ago) + InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) + MachineType: Dell Inc. Latitude E7470 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.17.0-7-generic root=/dev/mapper/hostname-root ro resume=/dev/mapper/hostname-swap nospl
[Kernel-packages] [Bug 1790454] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1790454/+attachment/5183933/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790454 Title: Bluetooth (btintel) stops working aster suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bas4871 F...m pulseaudio /dev/snd/controlC0: bas4871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 #RESUME=/dev/dm-2 #RESUME=/dev/mapper/regan-swap InstallationDate: Installed on 2016-12-22 (619 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude E7470 Pa
[Kernel-packages] [Bug 1790454] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1790454/+attachment/5183931/+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/1790454 Title: Bluetooth (btintel) stops working aster suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bas4871 F...m pulseaudio /dev/snd/controlC0: bas4871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 #RESUME=/dev/dm-2 #RESUME=/dev/mapper/regan-swap InstallationDate: Installed on 2016-12-22 (619 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude
[Kernel-packages] [Bug 1790454] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1790454/+attachment/5183925/+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/1790454 Title: Bluetooth (btintel) stops working aster suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bas4871 F...m pulseaudio /dev/snd/controlC0: bas4871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 #RESUME=/dev/dm-2 #RESUME=/dev/mapper/regan-swap InstallationDate: Installed on 2016-12-22 (619 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude E7470
[Kernel-packages] [Bug 1790454] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1790454/+attachment/5183923/+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/1790454 Title: Bluetooth (btintel) stops working aster suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bas4871 F...m pulseaudio /dev/snd/controlC0: bas4871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 #RESUME=/dev/dm-2 #RESUME=/dev/mapper/regan-swap InstallationDate: Installed on 2016-12-22 (619 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude E7470 Packag
[Kernel-packages] [Bug 1790454] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1790454/+attachment/5183932/+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/1790454 Title: Bluetooth (btintel) stops working aster suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bas4871 F...m pulseaudio /dev/snd/controlC0: bas4871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 #RESUME=/dev/dm-2 #RESUME=/dev/mapper/regan-swap InstallationDate: Installed on 2016-12-22 (619 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude E74
[Kernel-packages] [Bug 1790454] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1790454/+attachment/5183924/+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/1790454 Title: Bluetooth (btintel) stops working aster suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bas4871 F...m pulseaudio /dev/snd/controlC0: bas4871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 #RESUME=/dev/dm-2 #RESUME=/dev/mapper/regan-swap InstallationDate: Installed on 2016-12-22 (619 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitu
[Kernel-packages] [Bug 1790454] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1790454/+attachment/5183927/+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/1790454 Title: Bluetooth (btintel) stops working aster suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bas4871 F...m pulseaudio /dev/snd/controlC0: bas4871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 #RESUME=/dev/dm-2 #RESUME=/dev/mapper/regan-swap InstallationDate: Installed on 2016-12-22 (619 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude E7470 Pack
[Kernel-packages] [Bug 1790454] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1790454/+attachment/5183930/+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/1790454 Title: Bluetooth (btintel) stops working aster suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bas4871 F...m pulseaudio /dev/snd/controlC0: bas4871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 #RESUME=/dev/dm-2 #RESUME=/dev/mapper/regan-swap InstallationDate: Installed on 2016-12-22 (619 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. La
[Kernel-packages] [Bug 1790454] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1790454/+attachment/5183928/+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/1790454 Title: Bluetooth (btintel) stops working aster suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bas4871 F...m pulseaudio /dev/snd/controlC0: bas4871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 #RESUME=/dev/dm-2 #RESUME=/dev/mapper/regan-swap InstallationDate: Installed on 2016-12-22 (619 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell
[Kernel-packages] [Bug 1790454] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1790454/+attachment/5183934/+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/1790454 Title: Bluetooth (btintel) stops working aster suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bas4871 F...m pulseaudio /dev/snd/controlC0: bas4871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 #RESUME=/dev/dm-2 #RESUME=/dev/mapper/regan-swap InstallationDate: Installed on 2016-12-22 (619 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude E7470 Pa
[Kernel-packages] [Bug 1788753] Re: linux-kvm: 4.15.0-1021.21 -proposed tracker
4.15.0-1021.21 - kvm Regression test CMPL, RTB. Issue to note in amd64: ubuntu_fan_smoke_test - ubuntu_fan_smoke_test failed on 4.4/4.15 kvm kernel (bug 1763323) ubuntu_kvm_unit_tests - 15 failed on harpo ubuntu_ltp - gropfiles test failed (bug 1790445) ubuntu_ltp_syscalls - bind03 failed (bug 1788351) execveat03 failed (bug 1786729) inotify08 failed with X/X-LTS/X-HWE/A/B kernel (bug 1775784) quotactl01 failed (bug 1790028) ubuntu_qrt_apparmor - mmap timed out on groucho (bug 1783922) ubuntu_quota_smoke_test - failed with KVM kernel (bug 1784535) ubuntu_sysdig_smoke_test - Unable to insert sysdig_probe module on B-KVM kernel (bug 1766565) ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1788753 Title: linux-kvm: 4.15.0-1021.21 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: New 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: 1788744 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/1788753/+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 1788321] Re: swapon failed: invalid argument
This is the failing "swapon" sequence from updated Xenial i386 on
vmware:
3915 open("/dev/sda2", O_RDONLY|O_LARGEFILE) = 3
3915 uname({sysname="Linux", nodename="v3ls1717", ...}) = 0
3915 ioctl(3, BLKGETSIZE64, [535822336]) = 0
3915 read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
65536) = 65536
3915 close(3) = 0
3915 swapon("/dev/sda2", 0)= -1 EINVAL (Invalid argument)
Sequence is identical to other, native/amd64 system with same kernel
version but without the problem where swapon() will return 0.
--
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/1788321
Title:
swapon failed: invalid argument
Status in linux package in Ubuntu:
Confirmed
Status in util-linux package in Ubuntu:
Invalid
Bug description:
Environment:
- Ubuntu 18.04.1 LTS
- Linux 4.15.0-32-generic i686
Description:
When I try to mount my swap partition or my swap file, I get "swapon failed:
invalid argument" .
Steps to reproduce:
1) sudo bash
2) dd if=/dev/zero of=/swapfile bs=1024 count=524288
3) mkswap /swapfile
4) chown root:root /swapfile
5) chmod 0600 /swapfile
6) swapon /swapfile
Last execution returns "swapon failed: invalid argument" .
I'm almost sure it's a bug because I have no problems using Linux
4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no
problems using Ubuntu 18.04.1 LTS Live CD.
Regards.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788321/+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 1788762] Re: linux: 3.2.0-135.181 -proposed tracker
** Changed in: kernel-sru-workflow Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788762 Title: linux: 3.2.0-135.181 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Precise: New 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: -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788762/+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 1788762] Re: linux: 3.2.0-135.181 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-lbm Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-precise ** Tags added: block-proposed ** Description changed: 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: - kernel-stable-phase-changed:Monday, 27. August 2018 21:32 UTC - kernel-stable-phase:Packaging - -- swm properties -- phase: Packaging + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Monday, 03. September 2018 08:53 UTC ** Description changed: 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: -- swm properties -- - phase: Packaging - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Monday, 03. September 2018 08:53 UTC + boot-testing-requested: true + phase: Uploaded -- 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/1788762 Title: linux: 3.2.0-135.181 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Precise: New 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: -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788762/+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 1790454] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1790454/+attachment/5183929/+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/1790454 Title: Bluetooth (btintel) stops working aster suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bas4871 F...m pulseaudio /dev/snd/controlC0: bas4871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 #RESUME=/dev/dm-2 #RESUME=/dev/mapper/regan-swap InstallationDate: Installed on 2016-12-22 (619 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude
[Kernel-packages] [Bug 1730331] Re: ath10k_pci: firmware crashed!
The deep sleep kernel command-line parameter had no discernible effect. The laptop ran for me for 3 days on mains without the firmware crashing and now just has after the first sleep. This was running 1.173.1 firmware so I will now downgrade and test. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1730331 Title: ath10k_pci: firmware crashed! Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: ... Nov 4 18:35:50 akane kernel: [ 10.216896] ath10k_pci :04:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043222ff sub : Nov 4 18:35:50 akane kernel: [ 10.216908] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 Nov 4 18:35:50 akane kernel: [ 10.217641] ath10k_pci :04:00.0: firmware ver 10.2.4.70.63-2 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 4ff9e14d Nov 4 18:35:50 akane kernel: [ 10.228600] kvm: Nested Virtualization enabled Nov 4 18:35:50 akane kernel: [ 10.228611] kvm: Nested Paging enabled Nov 4 18:35:50 akane kernel: [ 10.258913] ath10k_pci :04:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08 Nov 4 18:35:50 akane kernel: [ 10.263535] MCE: In-kernel MCE decoding enabled. Nov 4 18:35:50 akane kernel: [ 10.271401] EDAC amd64: Node 0: DRAM ECC enabled. Nov 4 18:35:50 akane kernel: [ 10.271416] EDAC amd64: F16h_M30h detected (node 0). Nov 4 18:35:50 akane kernel: [ 10.271491] EDAC MC: DCT0 chip selects: Nov 4 18:35:50 akane kernel: [ 10.271494] EDAC amd64: MC: 0: 4096MB 1: 0MB Nov 4 18:35:50 akane kernel: [ 10.271523] EDAC amd64: MC: 2: 0MB 3: 0MB Nov 4 18:35:50 akane kernel: [ 10.271526] EDAC amd64: MC: 4: 0MB 5: 0MB Nov 4 18:35:50 akane kernel: [ 10.271528] EDAC amd64: MC: 6: 0MB 7: 0MB Nov 4 18:35:50 akane kernel: [ 10.271530] EDAC MC: DCT1 chip selects: Nov 4 18:35:50 akane kernel: [ 10.271532] EDAC amd64: MC: 0: 0MB 1: 0MB Nov 4 18:35:50 akane kernel: [ 10.271534] EDAC amd64: MC: 2: 0MB 3: 0MB Nov 4 18:35:50 akane kernel: [ 10.271537] EDAC amd64: MC: 4: 0MB 5: 0MB Nov 4 18:35:50 akane kernel: [ 10.271539] EDAC amd64: MC: 6: 0MB 7: 0MB Nov 4 18:35:50 akane kernel: [ 10.271541] EDAC amd64: using x4 syndromes. Nov 4 18:35:50 akane kernel: [ 10.271542] EDAC amd64: MCT channel count: 1 Nov 4 18:35:50 akane kernel: [ 10.271829] EDAC MC0: Giving out device to module amd64_edac controller F16h_M30h: DEV :00:18.3 (INTERRUPT) Nov 4 18:35:50 akane kernel: [ 10.271892] EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI controller: DEV :00:18.2 (POLLED) Nov 4 18:35:50 akane kernel: [ 10.271894] AMD64 EDAC driver v3.5.0 Nov 4 18:35:50 akane kernel: [ 10.532131] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: errors=remount-ro Nov 4 18:35:50 akane kernel: [ 10.575859] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: errors=remount-ro Nov 4 18:35:50 akane kernel: [ 11.397803] ath10k_pci :04:00.0: firmware crashed! (uuid f75dd562-d1bb-40a7-8454-fdc5f86cb8aa) Nov 4 18:35:50 akane kernel: [ 11.407389] ath10k_pci :04:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043222ff sub : Nov 4 18:35:50 akane kernel: [ 11.407395] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 Nov 4 18:35:50 akane kernel: [ 11.408085] ath10k_pci :04:00.0: firmware ver 10.2.4.70.63-2 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 4ff9e14d Nov 4 18:35:50 akane kernel: [ 11.408148] ath10k_pci :04:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08 Nov 4 18:35:50 akane kernel: [ 11.408156] ath10k_pci :04:00.0: htt-ver 0.0 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1 Nov 4 18:35:50 akane kernel: [ 11.410197] ath10k_pci :04:00.0: firmware register dump: Nov 4 18:35:50 akane kernel: [ 11.416213] ath10k_pci :04:00.0: [00]: 0x4100016C 0x15B3 0x009BFF84 0x00955B31 Nov 4 18:35:50 akane kernel: [ 11.424559] ath10k_pci :04:00.0: [04]: 0x009BFF84 0x00060130 0x0013 0x Nov 4 18:35:50 akane kernel: [ 11.432767] ath10k_pci :04:00.0: [08]: 0x009C8EA4 0x7170 0x0001 0x00435300 Nov 4 18:35:50 akane kernel: [ 11.441059] ath10k_pci :04:00.0: [12]: 0x0009 0x 0x00958360 0x0095836B Nov 4 18:35:50 akane kernel: [ 11.449397] ath10k_pci :04:00.0: [16]: 0x00958080 0x0094078E 0x 0x Nov 4 18:35:50 akane kernel: [ 11.457686] ath10k_pci :04:00.0: [20]: 0x409BFF84 0x0040AB44 0x004101E0 0x000C Nov 4 18:35:50 akane kernel: [ 11.466132] ath10k_pci :04:00.0: [24]: 0x809BFE1C 0x0040ABA4 0x0006 0xC09BFF84 Nov 4 18:35:50 a
[Kernel-packages] [Bug 1790454] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1790454/+attachment/5183935/+files/WifiSyslog.txt ** 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/1790454 Title: Bluetooth (btintel) stops working aster suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bas4871 F...m pulseaudio /dev/snd/controlC0: bas4871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 #RESUME=/dev/dm-2 #RESUME=/dev/mapper/regan-swap InstallationDate: Installed on 2016-12-22 (619 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety
[Kernel-packages] [Bug 1790454] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1790454/+attachment/5183926/+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/1790454 Title: Bluetooth (btintel) stops working aster suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bas4871 F...m pulseaudio /dev/snd/controlC0: bas4871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 #RESUME=/dev/dm-2 #RESUME=/dev/mapper/regan-swap InstallationDate: Installed on 2016-12-22 (619 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude E7470 Pack
[Kernel-packages] [Bug 1788762] Re: linux: 3.2.0-135.181 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788762 Title: linux: 3.2.0-135.181 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Precise: New 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: -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788762/+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 1789215] Re: i40e NIC not recognized
** Also affects: linux (Ubuntu Trusty) 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/1789215 Title: i40e NIC not recognized Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: New Bug description: == SRU Justification == Booting Trusty with kernel 3.13.0-156-generic on a fairly new Intel box with a i40e NIC results in no network. The 3.13 i40e driver doesn't support the following HW: 3d:00.0 Ethernet controller: Intel Corporation Device 37d2 (rev 02) Subsystem: Intel Corporation Device 35ce Flags: bus master, fast devsel, latency 0, IRQ 37 Memory at ac00 (64-bit, prefetchable) [size=16M] Memory at ad808000 (64-bit, prefetchable) [size=32K] Expansion ROM at ad98 [disabled] [size=512K] Capabilities: Base Board Information Manufacturer: Intel Corporation Product Name: S2600WFT This is a Canonical test system and having functional networking with a Trusty kernel would help with - well - testing :-) == Fix == Add a backport driver in addition to the in-tree driver that supports newer versions of the i40e NIC. == Regression Potential == Low. The new driver will only load for NICs that are not supported by the current in-tree driver. == Test Case == Boot a patched kernel and verify the NIC is recognized and the network comes up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789215/+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)
On my Acer Aspire ES-512 suspend as well as hibernate freeze the kubuntu 18.04 that I installed the day before yesterday on a 18G deleted partition. The latest kernel where suspend and hibernate work is 3.17, which however has problems with touchpad. That is, I use 3.16.57. From 3.18 and all later kernels suspend and hibernate do not work. It does not help that I change /etc/default/grup adding RESUME=UUID= or nouveau.modeset=0 to GRUB_CMDLINE_LINUX. Nor does it help that I enable hibernate in /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla. Feng's fixed kernel did not work either (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/comments/61). If anyone want additional information, just let me know. I have tried the following kernels: Found installed: 3.17.1-031701.201410150735 Found installed: 3.18.120-0318120.201808280231 Found installed: 4.15.0.33.35 Found installed: 3.18.18-031818.201507101433 Found installed: 4.15.0-33.36 Found installed: 3.16.45-031645.201707030336 Found installed: 4.18.5-041805.201808241320 Found installed: 3.18.1-031801.201412170637 Found installed: 3.18.36-031836.201606230133 Found installed: 4.15.0-29.31 Found installed: 4.1.11-040111.201510261146 Found installed: 3.17.8-031708.201501081837 Found installed: 4.14.41-041441.201806042208 Found installed: 3.16.57-031657.201806170831 Found installed: 3.18.2-031802.201501082011 uname -a Linux baren 3.16.57-031657-generic #201806170831 SMP Sun Jun 17 08:33:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lshw -short H/W path Device Class Description == system Aspire ES1-512 (EA53_BM_083D_1.09) /0 busAspire ES1-512 /0/0memory 64KiB BIOS /0/4processor Intel(R) Celeron(R) CPU N2840 @ 2.16GHz /0/4/8 memory 32KiB L1 cache /0/4/9 memory 1MiB L2 cache /0/7memory 24KiB L1 cache /0/fmemory 8GiB System Memory /0/f/0 memory 8GiB SODIMM DDR3 Synchronous 1333 MHz (0,8 ns) /0/f/1 memory SODIMM [empty] /0/100 bridge Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register /0/100/2displayAtom Processor Z36xxx/Z37xxx Series Graphics & Display /0/100/13 storageAtom Processor E3800 Series SATA AHCI Controller /0/100/14 busAtom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI /0/100/14/0 usb3 busxHCI Host Controller /0/100/14/1 usb2 busxHCI Host Controller /0/100/14/1/3 busUSB2.0 Hub /0/100/14/1/3/1 communication Atheros AR3012 Bluetooth /0/100/14/1/3/2 input USB Receiver /0/100/14/1/3/4 genericUSB2.0-CRW /0/100/14/1/4 multimedia VGA Webcam /0/100/1a genericAtom Processor Z36xxx/Z37xxx Series Trusted Execution Engine /0/100/1b multimedia Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller /0/100/1c bridge Atom Processor E3800 Series PCI Express Root Port 1 /0/100/1c.2 bridge Atom Processor E3800 Series PCI Express Root Port 3 /0/100/1c.2/0wls2 networkQCA9565 / AR9565 Wireless Network Adapter /0/100/1c.3 bridge Atom Processor E3800 Series PCI Express Root Port 4 /0/100/1c.3/0ens3 networkRTL8111/8168/8411 PCI Express Gigabit Ethernet Controller /0/100/1d busAtom Processor Z36xxx/Z37xxx Series USB EHCI /0/100/1d/1 usb1 busEHCI Host Controller /0/100/1f bridge Atom Processor Z36xxx/Z37xxx Series Power Control Unit /0/100/1f.3 busAtom Processor E3800 Series SMBus Controller /0/1 scsi0 storage /0/1/0.0.0 /dev/sda disk 1TB WDC WD10JPVX-22J /0/1/0.0.0/1 /dev/sda1 volume 4095KiB BIOS Boot partition /0/1/0.0.0/2 /dev/sda2 volume 18GiB EXT4 volume /0/1/0.0.0/3 /dev/sda3 volume 18GiB EXT4 volume /0/1/0.0.0/4 /dev/sda4 volume 18GiB Linux swap volume /0/1/0.0.0/5 /dev/sda5 volume 875GiB EXT4 volume ** Attachment added: "Acer Aspire ES-512 cannot hibernate/suspend on newer kernels that 3.17" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+attachment/5183963/+files/hwinfo.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/1774950 Title: Suspend fails in Ubuntu and
[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)
If the acpi-lpss fix doesn't work for you, please file a new bug report. -- 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: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Bug description: ===SRU Justification=== [Impact] Systems with acpi-lpss can't do S3/S4 on Bionic. [Test] Users confirmed these patches work for them. [Fix] Commit a192aa923b66a (ACPI / LPSS: Consolidate runtime PM and system sleep handling) applies quirks for both runtime and system suspend. This causes problems for some systems, so avoid using quirks on S3 and S4. [Regression Potential] Low. These patches are in upstream stable, and it brings back driver's old behavior. ===Original Bug Report=== 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 1788748] Re: linux-oem: 4.15.0-1018.21 -proposed tracker
** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => Invalid -- 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/1788748 Title: linux-oem: 4.15.0-1018.21 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed 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: 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 Bionic: New 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: 1788744 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/1788748/+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 1788762] Re: linux: 3.2.0-135.181 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788762 Title: linux: 3.2.0-135.181 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: New Status in linux source package in Precise: New 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: -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1788762/+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 787210] Re: ath9k drivers freeze the system when changing state
Closing this old bug. Newer versions should not see this issue anymore.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/787210
Title:
ath9k drivers freeze the system when changing state
Status in linux package in Ubuntu:
Fix Committed
Bug description:
Binary package hint: linux-image-generic
The ath9k driver freezes the laptop when the adapter changes state.
Reproduceable by enabling/disabling wireless adapter using the network
manager applet, or by suspending the system. The issue exists at least
in 10.10 as well, but never had issues running 10.04. Since applicable
in several kernel versions, reported this against linux-image-generic.
It's 32 bit stock kernel, latest updates, Natty 11.04 i386.
On 10.10 the system got freezes randomly just while browsing, which
was even worse. Used compat-wireless which made it much better but not
perfect (only freezes on state changes as mentioned above).
I am 100% sure it is triggered by the wireless driver: issuing "rmmod
ath9k ath9k_common ath9k_hw ath" prior to suspending the laptop,
followed by "modprobe ath9k" after resume, makes the freeze disappear.
I actually added a script in /etc/pm.d/sleep.d issuing these commands
and now laptop works normal.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-generic 2.6.38.8.22
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: NVidia [HDA NVidia], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sam1773 F xfce4-volumed
sam1794 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'NVidia'/'HDA NVidia at 0x9310 irq 23'
Mixer name : 'Nvidia MCP79/7A HDMI'
Components : 'HDA:111d7605,103c3651,00100402
HDA:10de0007,10de0101,00100100'
Controls : 18
Simple ctrls : 10
Date: Mon May 23 22:55:40 2011
InstallationMedia: Xubuntu 11.04 "Natty Narwhal" - Release i386 (20110426.1)
MachineType: Hewlett-Packard Compaq Mini 311-1100
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic
root=UUID=76ad9066-c058-4318-95ea-d214f8737341 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-2.6.38-8-generic N/A
linux-backports-modules-2.6.38-8-generic N/A
linux-firmware1.52
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/07/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.12
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3651
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 49.18
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnHewlett-Packard:bvrF.12:bd11/07/2009:svnHewlett-Packard:pnCompaqMini311-1100:pvr048F11201C032:rvnHewlett-Packard:rn3651:rvr49.18:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: Compaq Mini 311-1100
dmi.product.version: 048F11201C032
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/787210/+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 1790480] [NEW] random oopses on s390 systems using NVMe devices
You have been subscribed to a public bug: Random oopses on s390 systems using NVMe and running the Ubuntu 18.04.1 kernel have been reported. Bisect of the upstream kernel points to: 16ccfff28976 nvme: pci: pass max vectors as num_possible_cpus() to pci_alloc_irq_vectors This commit is correct but reveals a bug in s390s IRQ setup routine. A fix is available fixed via: Commit-ID : 866f3576a72b2233a76dffb80290f8086dc49e17 Need also be applied for Ubuntu 18.10 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-170595 severity-high targetmilestone-inin1804 -- random oopses on s390 systems using NVMe devices https://bugs.launchpad.net/bugs/1790480 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 1790480] [NEW] random oopses on s390 systems using NVMe devices
Public bug reported: Random oopses on s390 systems using NVMe and running the Ubuntu 18.04.1 kernel have been reported. Bisect of the upstream kernel points to: 16ccfff28976 nvme: pci: pass max vectors as num_possible_cpus() to pci_alloc_irq_vectors This commit is correct but reveals a bug in s390s IRQ setup routine. A fix is available fixed via: Commit-ID : 866f3576a72b2233a76dffb80290f8086dc49e17 Need also be applied for Ubuntu 18.10 ** Affects: ubuntu-z-systems Importance: High Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Triaged ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-170595 severity-high targetmilestone-inin1804 ** Tags added: architecture-s39064 bugnameltc-170595 severity-high targetmilestone-inin1804 ** 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/1790480 Title: random oopses on s390 systems using NVMe devices Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: Random oopses on s390 systems using NVMe and running the Ubuntu 18.04.1 kernel have been reported. Bisect of the upstream kernel points to: 16ccfff28976 nvme: pci: pass max vectors as num_possible_cpus() to pci_alloc_irq_vectors This commit is correct but reveals a bug in s390s IRQ setup routine. A fix is available fixed via: Commit-ID : 866f3576a72b2233a76dffb80290f8086dc49e17 Need also be applied for Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1790480/+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 1790480] Re: random oopses on s390 systems using NVMe devices
** 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/1790480 Title: random oopses on s390 systems using NVMe devices Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: Random oopses on s390 systems using NVMe and running the Ubuntu 18.04.1 kernel have been reported. Bisect of the upstream kernel points to: 16ccfff28976 nvme: pci: pass max vectors as num_possible_cpus() to pci_alloc_irq_vectors This commit is correct but reveals a bug in s390s IRQ setup routine. A fix is available fixed via: Commit-ID : 866f3576a72b2233a76dffb80290f8086dc49e17 Need also be applied for Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1790480/+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 1789934] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2018-09-03 08:44 EDT--- IBM Bugzilla status -> closed; Fix Released by Canonical -- 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/1789934 Title: [18.10 FEAT] Add kernel config options for SMC-R/D Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Add folliowing options for SMC-R/D CONFIG_SMC=m CONFIG_SMC_DIAG=m CONFIG_ISM=m Already provided CONFIG_HAVE_PNETID with bugzilla https://bugzilla.linux.ibm.com/show_bug.cgi?id=167251 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786902 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1789934/+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 1788762] Re: linux: 3.2.0-135.181 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: 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: -- swm properties -- boot-testing-requested: true phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Monday, 03. September 2018 13:05 UTC ** Description changed: 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: -- swm properties -- boot-testing-requested: true - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Monday, 03. September 2018 13:05 UTC + bugs-spammed: true + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1788762 Title: linux: 3.2.0-135.181 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed 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-lbm 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: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: New Status in linux source package in Precise: New 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: -- 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/1788762/+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 1788762] Re: linux: 3.2.0-135.181 -proposed tracker
** Changed in: kernel-sru-workflow/certification-testing 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/1788762 Title: linux: 3.2.0-135.181 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed 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-lbm 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: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: New Status in linux source package in Precise: New 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: -- 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/1788762/+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 1789638] Re: azure 4.15 kernel: reading sysfs file causing oops
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux (Ubuntu Bionic) 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/1789638 Title: azure 4.15 kernel: reading sysfs file causing oops Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Bug description: Kernel: 4.15.0-1021-azure, in Xenial VM on Azure. How to reproduce: git clone git://kernel.ubuntu.com/cking/stress-ng cd stress-ng make ./stress-ng --sysfs 0 -t 120 One gets the following: [ 22.451885] BUG: unable to handle kernel NULL pointer dereference at 0004 [ 22.455286] IP: read_avail_show+0x1c/0x40 [ 22.455286] PGD 80042d59e067 P4D 80042d59e067 PUD 42eb8c067 PMD 0 [ 22.455286] Oops: [#1] SMP PTI [ 22.455286] Modules linked in: nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_security ip_tables x_tables serio_raw joydev hv_balloon ib_iser iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd hyperv_fb hid_hyperv pata_acpi cfbfillrect hyperv_keyboard cfbimgblt hid cfbcopyarea hv_netvsc hv_utils [ 22.455286] CPU: 1 PID: 1670 Comm: cat Not tainted 4.15.0-1021-azure #21~16.04.1-Ubuntu [ 22.455286] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 22.455286] RIP: 0010:read_avail_show+0x1c/0x40 [ 22.455286] RSP: 0018:afa4c4eafdb0 EFLAGS: 00010286 [ 22.455286] RAX: RBX: 9db36c93e880 RCX: 9db36f136908 [ 22.860062] RDX: RSI: 9db364548000 RDI: 9db364548000 [ 22.888042] RBP: afa4c4eafdb0 R08: 9db364548000 R09: 9db36c049840 [ 22.920041] R10: 9db364548000 R11: R12: 92ae9440 [ 22.948058] R13: 9db36c22d200 R14: 0001 R15: 9db36c93e880 [ 22.972043] FS: 7f67eeec6700() GS:9db37fd0() knlGS: [ 23.004046] CS: 0010 DS: ES: CR0: 80050033 [ 23.024016] CR2: 0004 CR3: 00042c37a003 CR4: 001606e0 [ 23.048014] Call Trace: [ 23.060019] vmbus_chan_attr_show+0x21/0x30 [ 23.076018] sysfs_kf_seq_show+0xa2/0x130 [ 23.088030] kernfs_seq_show+0x27/0x30 [ 23.100020] seq_read+0xb7/0x480 [ 23.112014] kernfs_fop_read+0x111/0x190 [ 23.128017] ? security_file_permission+0xa1/0xc0 [ 23.144013] __vfs_read+0x1b/0x40 [ 23.156019] vfs_read+0x93/0x130 [ 23.168013] SyS_read+0x55/0xc0 [ 23.180021] do_syscall_64+0x73/0x130 [ 23.192014] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 23.212022] RIP: 0033:0x7f67ee9d8260 [ 23.224016] RSP: 002b:7fffdc193ff8 EFLAGS: 0246 ORIG_RAX: [ 23.252022] RAX: ffda RBX: 0002 RCX: 7f67ee9d8260 [ 23.276019] RDX: 0002 RSI: 7f67eed0c000 RDI: 0003 [ 23.300020] RBP: 0002 R08: R09: [ 23.328025] R10: 037b R11: 0246 R12: 7f67eed0c000 [ 23.352036] R13: 0003 R14: R15: 0002 [ 23.376678] Code: fb 3a 17 00 48 98 5d c3 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 8b 87 38 01 00 00 49 89 f0 8b 97 48 01 00 00 4c 89 c7 48 89 e5 <8b> 48 04 8b 00 29 ca 89 c6 29 ce 01 c2 39 c1 0f 46 d6 48 c7 c6 [ 23.444022] RIP: read_avail_show+0x1c/0x40 RSP: afa4c4eafdb0 [ 23.468021] CR2: 0004 [ 23.481135] ---[ end trace 348a4b7d5a6747d1 ]--- Cornered this down to just reading: cat /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBUS:01/99221fa0 -24ad-11e2-be98-001aa01bbf6e/channels/4/read_avail There are various /sysfs VMBUS files that trigger this, see a fix on comment #5 below that addresses all the ones I could find. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789638/+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 1788758] Re: linux-gcp: 4.15.0-1019.20~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => Invalid -- 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/1788758 Title: linux-gcp: 4.15.0-1019.20~16.04.1 -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 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-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released 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: New Status in linux-gcp source package in Xenial: New 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: 1788744 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/1788758/+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 1790506] [NEW] Upgrading to 18.04.1 from 17.10
Public bug reported: I have a HP Mini 210-1170NR that I have been using since Ubuntu 14 I believe. I have at it at 16 and currently (recently re-install 17.10 because of the possible "bug" in upgrading to 18.10.1 or even a fresh install of 18.10.1 on this same system. I believe I do remembering upgrading to 18.10 with success, but when it tries to go to 18.10.1 that is where the issue occurs. Through at least 3 attempts to upgrade my laptop to 18.10.1 it will go through the upgrade with out any errors or warnings until it does the last reboot into the updated version. It will bring up the screen that just has Ubuntu on it with the row of dots, it will go through at least one cycle of changing the colors of the dots, it will display the mouse pointer, which will not move when the mouse is moved, there will be some activity on the drive (the drive light will flash for about 5 minutes, but not sure of the exact time) then even it will not flash anymore. The screen will go blank after no activity, but moving the mouse or clicking on keys will not cause the screen to turn the display back on. Since the information gathered here is more for a working system and not the system that is having issues, and I seem to be able to re-create the issue at will, I will try and proceed with the upgrade to 18.10.1 and see if it "works" this time. What I can use from you is maybe an iso or instructions to possibly gather additional information that could be used to determine why it is not completing the update process. Any assistants you can provide will be gratefully appreciated. This is an old windows system that I put Ubuntu on and it could be I go back to 16.. and leave it there. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-46-generic 4.13.0-46.51 ProcVersionSignature: Ubuntu 4.13.0-46.51-generic 4.13.16 Uname: Linux 4.13.0-46-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: james 1317 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 3 09:08:40 2018 HibernationDevice: RESUME=UUID=393e2e20-215e-4082-bca5-cc6f1a2f5b85 InstallationDate: Installed on 2018-09-02 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Hewlett-Packard HP Mini 210-1100 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-4.13.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-46-generic N/A linux-backports-modules-4.13.0-46-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3660 dmi.board.vendor: Hewlett-Packard dmi.board.version: 48.26 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.24:bd03/18/2011:svnHewlett-Packard:pnHPMini210-1100:pvr049111202B030:rvnHewlett-Packard:rn3660:rvr48.26:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Mini 210-1100 dmi.product.version: 049111202B030 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1790506/+attachment/5184077/+files/lspci-vnvn.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/1790506 Title: Upgrading to 18.04.1 from 17.10 Status in linux package in Ubuntu: New Bug description: I have a HP Mini 210-1170NR that I have been using since Ubuntu 14 I believe. I have at it at 16 and currently (recently re-install 17.10 because of the possible "bug" in upgrading to 18.10.1 or even a fresh install of 18.10.1 on this same system. I believe I do remembering upgrading to 18.10 with success, but when it tries to go to 18.10.1 that is where the issue occurs. Through at least 3 attempts to upgrade my laptop to 18.10.1 it will go through the upgrade with out any errors or warnings until it does the last reboot into the updated version. It will bring up the screen that just has Ubuntu on it with the row of dots, it will go through at least one cycle of changing the colors of the dots, it will display the mouse pointer, which will not move when the mouse is moved, there will be some activity on the drive (the drive light will flash for about 5 minutes, but not sure of the exact time) then even it will not flash anymore. The scr
[Kernel-packages] [Bug 1780817] Re: kernel panic in nested VM with latest 4.15 kernel (4.15.0-24-generic)
those image also related to xenial. apt-cache policy linux-image-virtual-hwe-16.04 linux-image-virtual-hwe-16.04: Installed: 4.15.0.33.55 Candidate: 4.15.0.33.55 Version table: *** 4.15.0.33.55 500 500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status Probably, it should be also marked to xenial ? -- 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/1780817 Title: kernel panic in nested VM with latest 4.15 kernel (4.15.0-24-generic) Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: When starting a nested VM in a Bionic VM, the "host" VM kernel panics following a simple drop to QEMU monitor by hitting A-c. For some reason kdump is unable to capture the kernel panic so I only have a screen capture of the panic. It also happens on the latest mainline kernel(4.18-rc4). It is fairly trivial to reproduce. In a Bionic VM, install qemu & ovmf and run the following : qemu-system-x86_64 -enable-kvm \ -name balloontest \ -display none \ -monitor none \ -nographic \ -nodefaults \ -m 2048M \ -serial mon:stdio \ -smp 2 \ -cpu host \ -drive if=pflash,format=raw,readonly,file=/usr/share/OVMF/OVMF_CODE.fd \ -drive if=pflash,format=raw,file=/home/caribou/balloon/efi.vars Use A-c to drop to QEMU monitor and . ^[]0;/opt/ocs/gotty-serial/nolp-cli^G^[]2;Loading...^G^[]2;avogadro^G[ 267.784299] general protection fault: [#1] SMP PTI [ 267.785834] Modules linked in: nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype ip6t_MASQUERADE nf_nat_masquerade_ipv6 ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter i> [ 267.804312] xor raid6_pq libcrc32c raid1 raid0 multipath linear floppy aesni_intel pata_acpi aes_x86_64 crypto_simd cryptd glue_helper psmouse i2c_piix4 virtio_net virtio_blk [ 267.807946] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-24-generic #26-Ubuntu [ 267.809710] Hardware name: Scaleway Standard PC (i440FX + PIIX, 1996), BIOS 0.0.0 02/06/2015 [ 267.811666] RIP: 0010:native_write_cr4+0x4/0x10 [ 267.812727] RSP: 0018:8c01ffd83f48 EFLAGS: 00010006 [ 267.813960] RAX: 003626e0 RBX: 0046 RCX: 8c01ffd8 [ 267.815582] RDX: 8c01ffd94020 RSI: 8c01ffda5040 RDI: 003606e0 [ 267.817095] RBP: 8c01ffd83f48 R08: 00478079a547 R09: [ 267.818625] R10: R11: R12: 00025040 [ 267.820130] R13: 0001 R14: R15: [ 267.821638] FS: () GS:8c01ffd8() knlGS: [ 267.823352] CS: 0010 DS: ES: CR0: 80050033 [ 267.824592] CR2: CR3: 00058c00a006 CR4: 003626e0 [ 267.826108] DR0: DR1: DR2: [ 267.827567] DR3: DR6: fffe0ff0 DR7: 0400 [ 267.828973] Call Trace: [ 267.829470] [ 267.829893] hardware_disable+0xaa/0xc0 [kvm_intel] [ 267.830897] kvm_arch_hardware_disable+0x19/0x40 [kvm] [ 267.831928] hardware_disable_nolock+0x2b/0x30 [kvm] [ 267.832912] flush_smp_call_function_queue+0x4c/0xf0 [ 267.833911] generic_smp_call_function_single_interrupt+0x13/0x30 [ 267.835121] smp_call_function_interrupt+0x36/0xd0 [ 267.836069] call_function_interrupt+0x84/0x90 [ 267.836950] [ 267.837396] RIP: 0010:native_safe_halt+0x6/0x10 [ 267.838272] RSP: 0018:a2e1431afe80 EFLAGS: 0246 ORIG_RAX: ff03 [ 267.839698] RAX: acd97150 RBX: 0006 RCX: [ 267.840978] RDX: RSI: RDI: [ 267.842258] RBP: a2e1431afe80 R08: 0002 R09: [ 267.843554] R10: 00b3 R11: 00a6 R12: 0006 [ 267.844826] R13: R14: R15: [ 267.846107] ? __cpuidle_text_start+0x8/0x8 [ 267.846875] default_idle+0x20/0x100 [ 267.847533] arch_cpu_idle+0x15/0x20 [ 267.848186] default_idle_call+0x23/0x30 [ 267.848917] do_idle+0x172/0x1f0 [ 267.849516] cpu_startup_entry+0x73/0x80 [ 267.850255] start_secondary+0x1ab/0x200 [ 267.850971] secondary_startup_64+0xa5/0xb0 [ 267.851700] Code: 0f 1f 80 00 00 00 00 55 48 89 e5 0f 20 d8 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 0f 22 df 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 <0f> 22 e7 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 44 0f 20
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
Richard barka please send me your tweaked dsdt tables, i would like to test them my laptop is a315-41g-r1n2 and my email is eutychio...@gmail.com -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: New Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+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 1699772] Re: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic | Regressio
Still crashing in cosmic on i386 with libreoffice 6.0.6 and kernel 4.17.0.9.12, and libreoffice 6.1.0 and kernel 4.18.0.7.8. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1699772 Title: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux- image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux- image-3.13.0-121-generic | Regression: many user-space apps crashing Status in LibreOffice: Won't Fix Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Incomplete Status in linux package in Debian: Fix Released Bug description: Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10) linux-image-4.4.0-81-generic appears to contain a regression, probably related to the CVE-2017-1000364 fix backport / patch. Using this kernel, the Oracle Java browser plugin always crashes during stack-related actions on initialization. This means, the plugin completely stopped working. It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also contains a fix for CVE-2017-1000364. uname -a: > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as well as Iceweasel / Firefox/3.5.16 in a chroot. Using linux-image-4.4.0-81-generic it crashes in all combinations while with both other kernels it works. I was not able to obtain any detailed crash information from Firefox 51.0.1, but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace which shows the relation to stack operations performed by the plugin, even without proper debug symbols: > (gdb) bt full > #0 0x7fa06d805307 in _expand_stack_to(unsigned char*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #1 0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, unsigned char*) () >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #2 0x7fa06d80cf0b in JVM_handle_linux_signal () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #3 0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #4 I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6. The crash will be triggered by any applet, for example the test applet at: * https://java.com/en/download/installed8.jsp I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow apparently does not allow me to use apport to report this bug: > $ LANG= apport-cli linux-image-4.4.0-81-generic > > *** Collecting problem information > > The collected information can be sent to the developers to improve the > application. This might take a few minutes. > . > > *** Problem in linux-image-4.4.0-81-generic > > The problem cannot be reported: > > This is not an official KDE package. Please remove any third party package and try again. If someone can tell me how to get apport working for this package, I can use it to collect additional information, but (unfortunately?) the problem should be fairly easy to reproduce... To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+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 1790506] 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/1790506 Title: Upgrading to 18.04.1 from 17.10 Status in linux package in Ubuntu: Confirmed Bug description: I have a HP Mini 210-1170NR that I have been using since Ubuntu 14 I believe. I have at it at 16 and currently (recently re-install 17.10 because of the possible "bug" in upgrading to 18.10.1 or even a fresh install of 18.10.1 on this same system. I believe I do remembering upgrading to 18.10 with success, but when it tries to go to 18.10.1 that is where the issue occurs. Through at least 3 attempts to upgrade my laptop to 18.10.1 it will go through the upgrade with out any errors or warnings until it does the last reboot into the updated version. It will bring up the screen that just has Ubuntu on it with the row of dots, it will go through at least one cycle of changing the colors of the dots, it will display the mouse pointer, which will not move when the mouse is moved, there will be some activity on the drive (the drive light will flash for about 5 minutes, but not sure of the exact time) then even it will not flash anymore. The screen will go blank after no activity, but moving the mouse or clicking on keys will not cause the screen to turn the display back on. Since the information gathered here is more for a working system and not the system that is having issues, and I seem to be able to re-create the issue at will, I will try and proceed with the upgrade to 18.10.1 and see if it "works" this time. What I can use from you is maybe an iso or instructions to possibly gather additional information that could be used to determine why it is not completing the update process. Any assistants you can provide will be gratefully appreciated. This is an old windows system that I put Ubuntu on and it could be I go back to 16.. and leave it there. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-46-generic 4.13.0-46.51 ProcVersionSignature: Ubuntu 4.13.0-46.51-generic 4.13.16 Uname: Linux 4.13.0-46-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: james 1317 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 3 09:08:40 2018 HibernationDevice: RESUME=UUID=393e2e20-215e-4082-bca5-cc6f1a2f5b85 InstallationDate: Installed on 2018-09-02 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Hewlett-Packard HP Mini 210-1100 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-4.13.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-46-generic N/A linux-backports-modules-4.13.0-46-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3660 dmi.board.vendor: Hewlett-Packard dmi.board.version: 48.26 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.24:bd03/18/2011:svnHewlett-Packard:pnHPMini210-1100:pvr049111202B030:rvnHewlett-Packard:rn3660:rvr48.26:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Mini 210-1100 dmi.product.version: 049111202B030 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790506/+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 1753510] Re: Cannot boot/install AMD Ryzen 2400G
tried again with 4.19rc2. Stripped off all other usb peripherals (including existing mouse & kb), only had the internal (windows) SSD and the usb one I am plugging in. Now using a logitech K400 or so, which seems compatible with everything. When I boot, it dumps me into (initramfs) prompt, and I can use it. If I do ls /dev, I see sda, sda1, sda2, sda3 and no other disk partitions. When I try to mount them, I find they are the windows SSD that is SATA connected. It doesn't see the externally USB connected drive. So I disconnected the windows SSD, removed the other SSD from the enclosure and connected it the ubuntu SSD via SATA. Now I can get a reproducible crash. picture coming. -- 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/1753510 Title: Cannot boot/install AMD Ryzen 2400G Status in linux package in Ubuntu: Confirmed Bug description: Did a motherboard swap on a trusty old computer that ran ubuntu for 10 years or so. Now it only runs windows (same hardware fresh installs windows with no issue). brand new ryzen 2nd gen with graphics. I know about graphics drivers issues, wasn't expecting that to be dealt with. Just trying to use it as a cpu. So I put in an older (RADEON HD 7850 pitcairn) video card to get some functionality. Without the video card, it boots, but the display is unusable. I can ssh in and see that it works fine as a server, but cannot use terminal or graphical display. With the video card, Put daily ubuntu Bionic image, and "Try Ubuntu", and it goes into an infinite loop. photo attached. I tried 16.04.4 and I think it just went into a blank screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753510/+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 1788748] Re: linux-oem: 4.15.0-1018.21 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => 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/1788748 Title: linux-oem: 4.15.0-1018.21 -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 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 Bionic: New 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: 1788744 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/1788748/+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 1753510] Re: Cannot boot/install AMD Ryzen 2400G
** Attachment added: "Second crash, not identical." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753510/+attachment/5184094/+files/P_20180903_111405_vHDR_Auto.jpg -- 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/1753510 Title: Cannot boot/install AMD Ryzen 2400G Status in linux package in Ubuntu: Confirmed Bug description: Did a motherboard swap on a trusty old computer that ran ubuntu for 10 years or so. Now it only runs windows (same hardware fresh installs windows with no issue). brand new ryzen 2nd gen with graphics. I know about graphics drivers issues, wasn't expecting that to be dealt with. Just trying to use it as a cpu. So I put in an older (RADEON HD 7850 pitcairn) video card to get some functionality. Without the video card, it boots, but the display is unusable. I can ssh in and see that it works fine as a server, but cannot use terminal or graphical display. With the video card, Put daily ubuntu Bionic image, and "Try Ubuntu", and it goes into an infinite loop. photo attached. I tried 16.04.4 and I think it just went into a blank screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753510/+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 1709889] Re: Ubuntu 18.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time.
Is this behaviour also seen with a vanilla upstream 4.15 kernel, or is
it unique to the Ubuntu 4.15 bionic 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/1709889
Title:
Ubuntu 18.04: Bug in cfq scheduler, I/Os do not get submitted to
adapter for a very long time.
Status in Linux:
Unknown
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
New
Status in linux source package in Zesty:
Won't Fix
Status in linux source package in Bionic:
Triaged
Bug description:
---Problem Description---
When running stress test, sometimes seeing IO hung in dmesg or seeing "Host
adapter abort request" error.
---Steps to Reproduce---
There are two ways to re-create the issues:
(1)running HTX, you will see IO timeout backtrace in dmesg in several hours
(2)running some IO test, then reboot system, repeat this two steps, it takes
long time to re-create the issue.
---uname output---
4.10.0-11-generic
The bulk of the effort for this issue is currently being worked in
MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.
Ran an interesting test: Ran HTX until I started getting the "stall"
messages on the console, then shutdown HTX and examined the I/O
counters for the tested disks in sysfs:
root@bostonp15:~# for i in
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
0:2:2:0 0x5eba3d 0x5eba3d
0:2:3:0 0x773cc9 0x773cc9
0:2:4:0 0x782c61 0x782c61
0:2:5:0 0x5ca134 0x5ca134
root@bostonp15:~#
So, none of the disks showed any evidence of having lost an I/O. I
then restarted HTX and aside from having to manually restart one of
the disks, see no problems with the testing. It appears that what was
"hung" was purely in userland.
This does not absolve the kernel or aacraid driver from blame, but it
shows that the OS "believes" that it completed the I/O and thus
removed it from the queue. What we don't know is whether the OS truly
notified HTX about the completion, or if HTX (or userland libraries)
just failed to process the notification.
Tests are running again, will see what happens next.
Update from JIRA:
I have run some more experiments. Not sure what it tells us, but
here's what I've seen.
First test, ran until I got kernel messages about stalled tasks, then
shutdown HTX. After HTX was down, I checked the above mentioned
counters and found that on each disk iorequest_cnt matched iodone_cnt.
The disks were usable and I could restart HTX. This suggests that the
problem is not in the PM8069 firmware, and makes the case for the
aacraid driver having a bug somewhat weaker. However, this merely says
that the driver "completed" the I/O as far as the kernel is concerned,
not that a completion rippled back to the application.
I restarted HTX and have run until errors. This time, I am leaving HTX
running and observing. Two of the disks reached the HTX error
threshold and the testers stopped (those 2 disks are now idle).
Another disks saw errors but then stopped and appears to be running
fine now. The last disk has not seen any errors (yet). On the two idle
(errored-out) disks I see iorequest_cnt matches iodone_cnt. I am able
to "terminate and restart" the two idle disks and HTX appears to be
testing them again "normally". Note that no reboot was required,
further supporting the evidence that, as far as the kernel is
concerned, there is nothing wrong with the disks and their I/O paths.
So, I don't believe this completely eliminates aacraid from the
picture, especially given we don't see this behavior on other
systems/drivers. But, it probably moves the focus of the investigation
away form the adapter firmware.
Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
1.2.1[50792]-custom.
Good new/bad news... While doing an initial evaluation of the LSI-3008
SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
So, it appears to have nothing specific to do with the PM8069 or
aacraid driver.
Some notes on reproduce this. I have been using the github release of
HTX, built using the following steps:
1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev
(others may be required)
2. git clone https://github.com/open-power/HTX
3. cd HTX
4. make
5. make deb
Then install the resulting "htxubuntu.deb" package.
Note, HTX will not test disks that have a filesystem or OS installed,
so there must be at least two disks made available to HTX by clearing
any previous data. A partition table is optional, in my testing I have
none.
Also, it may be desirable to run HTX somewhere other than the console,
leaving the console
[Kernel-packages] [Bug 1753510] Re: Cannot boot/install AMD Ryzen 2400G
** Attachment added: "sample crash" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753510/+attachment/5184093/+files/P_20180903_103208_vHDR_Auto.jpg -- 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/1753510 Title: Cannot boot/install AMD Ryzen 2400G Status in linux package in Ubuntu: Confirmed Bug description: Did a motherboard swap on a trusty old computer that ran ubuntu for 10 years or so. Now it only runs windows (same hardware fresh installs windows with no issue). brand new ryzen 2nd gen with graphics. I know about graphics drivers issues, wasn't expecting that to be dealt with. Just trying to use it as a cpu. So I put in an older (RADEON HD 7850 pitcairn) video card to get some functionality. Without the video card, it boots, but the display is unusable. I can ssh in and see that it works fine as a server, but cannot use terminal or graphical display. With the video card, Put daily ubuntu Bionic image, and "Try Ubuntu", and it goes into an infinite loop. photo attached. I tried 16.04.4 and I think it just went into a blank screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753510/+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 1790513] [NEW] kdump-config status - not ready to kdump with v4.18 kernel
Public bug reported: As part of the makedumpfile autopkgtest, a test is done to make sure one can dump the kernel. The test executes $ kdump-config status and expects to find that it is ready to kdump, however it is not. The check fails at: $ cat /sys/kernel/kexec_crash_loaded Previously it was 1, but now it is 0. Is this intentional? Do we need to change something in makedumpfile? Or is something missing in the kernel? ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xnox 9240 F pulseaudio /dev/snd/controlC1: xnox 9240 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 3 17:07:41 2018 HibernationDevice: RESUME=UUID=2bf263f1-753f-4b2e-92a6-b00381515e0c InstallationDate: Installed on 2012-01-12 (2425 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. 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-4.18.0-7-generic root=UUID=6669d411-80c3-41cc-a629-ad84e1ee6854 ro splash crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-:128M vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-06-25 (69 days ago) dmi.bios.date: 08/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F18g dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF18g:bd08/13/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic package-from-proposed 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/1790513 Title: kdump-config status - not ready to kdump with v4.18 kernel Status in linux package in Ubuntu: New Bug description: As part of the makedumpfile autopkgtest, a test is done to make sure one can dump the kernel. The test executes $ kdump-config status and expects to find that it is ready to kdump, however it is not. The check fails at: $ cat /sys/kernel/kexec_crash_loaded Previously it was 1, but now it is 0. Is this intentional? Do we need to change something in makedumpfile? Or is something missing in the kernel? ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xnox 9240 F pulseaudio /dev/snd/controlC1: xnox 9240 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 3 17:07:41 2018 HibernationDevice: RESUME=UUID=2bf263f1-753f-4b2e-92a6-b00381515e0c InstallationDate: Installed on 2012-01-12 (2425 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. 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-4.18.0-7-generic root=UUID=6669d411-80c3-41cc-a629-ad84e1ee6854 ro splash crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-:128M vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 RfKill: SourcePackage: li
[Kernel-packages] [Bug 1790513] Re: kdump-config status - not ready to kdump with v4.18 kernel
** Branch linked: lp:~xnox/britney/hints-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/1790513 Title: kdump-config status - not ready to kdump with v4.18 kernel Status in linux package in Ubuntu: Confirmed Bug description: As part of the makedumpfile autopkgtest, a test is done to make sure one can dump the kernel. The test executes $ kdump-config status and expects to find that it is ready to kdump, however it is not. The check fails at: $ cat /sys/kernel/kexec_crash_loaded Previously it was 1, but now it is 0. Is this intentional? Do we need to change something in makedumpfile? Or is something missing in the kernel? ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xnox 9240 F pulseaudio /dev/snd/controlC1: xnox 9240 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 3 17:07:41 2018 HibernationDevice: RESUME=UUID=2bf263f1-753f-4b2e-92a6-b00381515e0c InstallationDate: Installed on 2012-01-12 (2425 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. 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-4.18.0-7-generic root=UUID=6669d411-80c3-41cc-a629-ad84e1ee6854 ro splash crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-:128M vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-06-25 (69 days ago) dmi.bios.date: 08/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F18g dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF18g:bd08/13/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790513/+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 1776211] Re: kdump fails to take dump with smt set to 2, hmc dumpstart
** Changed in: ubuntu-power-systems
Status: In Progress => Invalid
--
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/1776211
Title:
kdump fails to take dump with smt set to 2, hmc dumpstart
Status in The Ubuntu-power-systems project:
Invalid
Status in linux package in Ubuntu:
Invalid
Status in makedumpfile package in Ubuntu:
Invalid
Status in linux source package in Artful:
Invalid
Status in makedumpfile source package in Artful:
Invalid
Bug description:
== SRU Justification ==
IBM has requested these three commits in Artful. In Artful, kdump fails to
capture dump when smt=2 or off.
Including these three commits allows kdump to work properly.
== Fixes ==
4388c9b3a6ee ("powerpc: Do not send system reset request through the oops
path")
04b9c96eae72 ("powerpc/crash: Remove the test for cpu_online in the IPI
callback")
4552d128c26e ("powerpc: System reset avoid interleaving oops using die
synchronisation")
== Regression Potential ==
Low. Fixes are limited to powerpc.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
--Problem Description---
kdump fails to take dump with smt set to 2, hmc dumpstart
---Issue observed---
[0.004111] Oops: Exception in kernel mode, sig: 4 [#1]
[0.004118] SMP NR_CPUS=2048
[0.004120] NUMA
[0.004125] pSeries
[0.004132] Modules linked in:
[0.004142] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.13.0-12-generic
#13-Ubuntu
[0.004153] task: c00046715900 task.stack: c00046134000
[0.004162] NIP: c0006468 LR: c801764c CTR:
006cdc70
[0.004173] REGS: c00047fe3ce0 TRAP: 0700 Not tainted
(4.13.0-12-generic)
[0.004181] MSR: 80081031
[0.004193] CR: 8804 XER: 2003
[0.004204] CFAR: c0006454 SOFTE: 0
[0.004204] GPR00: c801764c c00047fe3f60 c95e3000
[0.004204] GPR04: 0001 0002
ffdf
[0.004204] GPR08: 2804 0002
0002
[0.004204] GPR12: cfff c00046137f90
0b5452d8
[0.004204] GPR16: fffd 089ffd10 0136
0b55d378
[0.004204] GPR20: 0060 1eca 0a6c
0007
[0.004204] GPR24: c9621ed0
[0.004204] GPR28: c00046134000 c00046137c80
c9105df8
[0.004328] NIP [c0006468] 0xc0006468
[0.004338] LR [c801764c] __do_irq+0x4c/0x1c0
[0.004345] Call Trace:
[0.004354] [c00047fe3f60] [c801764c] __do_irq+0x4c/0x1c0
(unreliable)
[0.004368] [c00047fe3f90] [c802ab70] call_do_irq+0x14/0x24
[0.004380] [c00046137bc0] [c801785c] do_IRQ+0x9c/0x130
[0.004393] [c00046137c10] [c8008ac4]
hardware_interrupt_common+0x114/0x120
[0.004409] --- interrupt: 501 at arch_local_irq_restore+0x5c/0x90
[0.004409] LR = arch_local_irq_restore+0x40/0x90
[0.004423] [c00046137f00] [0005] 0x5 (unreliable)
[0.004436] [c00046137f20] [c8049824]
start_secondary+0x324/0x350
[0.004450] [c00046137f90] [c800aa6c]
start_secondary_prolog+0x10/0x14
[0.004460] Instruction dump:
[0.004467]
[0.004484]
[0.004506] ---[ end trace 3e5a2a9047ef3cd0 ]---
[0.004512]
[0.004518] Oops: Exception in kernel mode, sig: 4 [#2]
[0.004525] SMP NR_CPUS=2048
[0.004526] NUMA
[0.004532] pSeries
[0.004540] Modules linked in:
[0.004550] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G D
4.13.0-12-generic #13-Ubuntu
[0.004561] task: c9579f00 task.stack: c95dc000
[0.004569] NIP: c0006460 LR: c80b6e80 CTR:
[0.004580] REGS: c95dfb20 TRAP: 0700 Tainted: G D
(4.13.0-12-generic)
[0.004589] MSR: 80081031
[0.004599] CR: 22002228 XER: 2004
[0.004611] CFAR: c000493c SOFTE: 0
[0.004611] GPR00: c95dfda0 c95e3000
[0.004611] GPR04:
[0.004611] GPR08: 22002228 7fff
0008
[0.004611] GPR12: cfff0a80 c00c7e137f90
09980600
[
[Kernel-packages] [Bug 1790513] 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/1790513 Title: kdump-config status - not ready to kdump with v4.18 kernel Status in linux package in Ubuntu: Confirmed Bug description: As part of the makedumpfile autopkgtest, a test is done to make sure one can dump the kernel. The test executes $ kdump-config status and expects to find that it is ready to kdump, however it is not. The check fails at: $ cat /sys/kernel/kexec_crash_loaded Previously it was 1, but now it is 0. Is this intentional? Do we need to change something in makedumpfile? Or is something missing in the kernel? ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xnox 9240 F pulseaudio /dev/snd/controlC1: xnox 9240 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 3 17:07:41 2018 HibernationDevice: RESUME=UUID=2bf263f1-753f-4b2e-92a6-b00381515e0c InstallationDate: Installed on 2012-01-12 (2425 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. 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-4.18.0-7-generic root=UUID=6669d411-80c3-41cc-a629-ad84e1ee6854 ro splash crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-:128M vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-06-25 (69 days ago) dmi.bios.date: 08/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F18g dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF18g:bd08/13/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790513/+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 1790515] [NEW] black screen on ubuntu GTX 1050 eGPU
Public bug reported: I'm using a laptop lenovo thinkpad T410 with intel graphics and egpu + GTX 1050. (using expresscard or mini pcie both failed) When I install the 390 driver my graphical display fails. I know that egpu is not the best solution but worked with some people. ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1790515 Title: black screen on ubuntu GTX 1050 eGPU Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I'm using a laptop lenovo thinkpad T410 with intel graphics and egpu + GTX 1050. (using expresscard or mini pcie both failed) When I install the 390 driver my graphical display fails. I know that egpu is not the best solution but worked with some people. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1790515/+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 1788752] Re: linux-gcp: 4.15.0-1019.20 -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/1788752 Title: linux-gcp: 4.15.0-1019.20 -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 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 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: New 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: 1788744 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/1788752/+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 1790511] [NEW] General protection fault while trying to discover a nvmeof target
You have been subscribed to a public bug: nvme discover command times out and results in general protection fault in kernel. # nvme discover -t rdma -a 10.1.1.6 -s 4420 Failed to write to /dev/nvme-fabrics: Input/output error^M # # [16900.248129] nvme nvme0: Connect command failed, error wo/DNR bit: 7 [16900.248182] nvme nvme0: failed to connect queue: 0 ret=7 [16900.253138] nvme nvme0: Reconnecting in 10 seconds... [16910.300029] general protection fault: [#1] SMP PTI [16910.300069] Modules linked in: mlx4_en mlx4_ib mlx4_core nvme_rdma nvme_fabrics nvme_core rdma_ucm ib_umad ib_ucm ib_uverbs xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_addrtype overlay aufs joydev input_leds ipmi_ssif intel_rapl skx_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass intel_cstate intel_rapl_perf mei_me mei ioatdma lpc_ich shpchp sch_fq_codel ipmi_si ipmi_devintf ipmi_msghandler acpi_pad mac_hid acpi_power_meter iptable_filter ip6table_filter ip6_tables br_netfilter bridge stp llc arp_tables ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov [16910.300534] async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_core hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd mlx5_core ast mlxfw i2c_algo_bit devlink ttm drm_kms_helper ixgbe syscopyarea sysfillrect sysimgblt fb_sys_fops dca ptp drm pps_core mdio ahci libahci wmi [last unloaded: nvme_core] [16910.300794] CPU: 33 PID: 3173 Comm: kworker/u146:1 Not tainted 4.15.0-33-generic #36-Ubuntu [16910.300845] Hardware name: Supermicro SYS-6019U-TN4RT/X11DPU, BIOS 2.0b 02/24/2018 [16910.300898] Workqueue: nvme-wq nvme_rdma_reconnect_ctrl_work [nvme_rdma] [16910.300945] RIP: 0010:nvme_rdma_alloc_queue+0x3c/0x190 [nvme_rdma] [16910.300984] RSP: 0018:9ba8a037be08 EFLAGS: 00010206 [16910.301019] RAX: RBX: 52404d65f5994178 RCX: 8a0f78002820 [16910.301063] RDX: c0b58600 RSI: c0b573ab RDI: 8a0f70aec000 [16910.301108] RBP: 9ba8a037be28 R08: 0334 R09: [16910.301152] R10: R11: 0337 R12: 8a0f70aec000 [16910.301195] R13: R14: 0020 R15: [16910.301240] FS: () GS:8a0f7efc() knlGS: [16910.301289] CS: 0010 DS: ES: CR0: 80050033 [16910.301326] CR2: 7ffc4e5cadb8 CR3: 00123ba0a003 CR4: 007606e0 [16910.301370] DR0: DR1: DR2: [16910.301414] DR3: DR6: fffe0ff0 DR7: 0400 [16910.301458] PKRU: 5554 [16910.301477] Call Trace: [16910.301504] nvme_rdma_configure_admin_queue+0x22/0x2d0 [nvme_rdma] [16910.301548] nvme_rdma_reconnect_ctrl_work+0x27/0xd0 [nvme_rdma] [16910.301591] process_one_work+0x1de/0x410 [16910.301620] worker_thread+0x32/0x410 [16910.301651] kthread+0x121/0x140 [16910.301676] ? process_one_work+0x410/0x410 [16910.301707] ? kthread_create_worker_on_cpu+0x70/0x70 [16910.301744] ? do_syscall_64+0x73/0x130 [16910.301774] ? SyS_exit_group+0x14/0x20 [16910.301805] ret_from_fork+0x35/0x40 [16910.301831] Code: 89 e5 41 56 41 55 41 54 53 48 8d 1c c5 00 00 00 00 49 89 fc 49 89 c5 49 89 d6 48 29 c3 48 c7 c2 00 86 b5 c0 48 c1 e3 04 48 03 1f <48> 89 7b 18 48 8d 7b 58 c7 43 50 00 00 00 00 e8 20 d4 57 ef 45 [16910.305367] RIP: nvme_rdma_alloc_queue+0x3c/0x190 [nvme_rdma] RSP: 9ba8a037be08 [16910.307146] ---[ end trace 3ae215b72b2ac870 ]--- # # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic # # uname -a Linux esdev005 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 bionic bot-comment kernel-bug nvme nvmeof rdma -- General protection fault while trying to discover a nvmeof target https://bugs.launchpad.net/bugs/1790511 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 1790511] Re: General protection fault while trying to discover a nvmeof target
** 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/1790511 Title: General protection fault while trying to discover a nvmeof target Status in linux package in Ubuntu: Incomplete Bug description: nvme discover command times out and results in general protection fault in kernel. # nvme discover -t rdma -a 10.1.1.6 -s 4420 Failed to write to /dev/nvme-fabrics: Input/output error^M # # [16900.248129] nvme nvme0: Connect command failed, error wo/DNR bit: 7 [16900.248182] nvme nvme0: failed to connect queue: 0 ret=7 [16900.253138] nvme nvme0: Reconnecting in 10 seconds... [16910.300029] general protection fault: [#1] SMP PTI [16910.300069] Modules linked in: mlx4_en mlx4_ib mlx4_core nvme_rdma nvme_fabrics nvme_core rdma_ucm ib_umad ib_ucm ib_uverbs xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_addrtype overlay aufs joydev input_leds ipmi_ssif intel_rapl skx_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass intel_cstate intel_rapl_perf mei_me mei ioatdma lpc_ich shpchp sch_fq_codel ipmi_si ipmi_devintf ipmi_msghandler acpi_pad mac_hid acpi_power_meter iptable_filter ip6table_filter ip6_tables br_netfilter bridge stp llc arp_tables ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov [16910.300534] async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_core hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd mlx5_core ast mlxfw i2c_algo_bit devlink ttm drm_kms_helper ixgbe syscopyarea sysfillrect sysimgblt fb_sys_fops dca ptp drm pps_core mdio ahci libahci wmi [last unloaded: nvme_core] [16910.300794] CPU: 33 PID: 3173 Comm: kworker/u146:1 Not tainted 4.15.0-33-generic #36-Ubuntu [16910.300845] Hardware name: Supermicro SYS-6019U-TN4RT/X11DPU, BIOS 2.0b 02/24/2018 [16910.300898] Workqueue: nvme-wq nvme_rdma_reconnect_ctrl_work [nvme_rdma] [16910.300945] RIP: 0010:nvme_rdma_alloc_queue+0x3c/0x190 [nvme_rdma] [16910.300984] RSP: 0018:9ba8a037be08 EFLAGS: 00010206 [16910.301019] RAX: RBX: 52404d65f5994178 RCX: 8a0f78002820 [16910.301063] RDX: c0b58600 RSI: c0b573ab RDI: 8a0f70aec000 [16910.301108] RBP: 9ba8a037be28 R08: 0334 R09: [16910.301152] R10: R11: 0337 R12: 8a0f70aec000 [16910.301195] R13: R14: 0020 R15: [16910.301240] FS: () GS:8a0f7efc() knlGS: [16910.301289] CS: 0010 DS: ES: CR0: 80050033 [16910.301326] CR2: 7ffc4e5cadb8 CR3: 00123ba0a003 CR4: 007606e0 [16910.301370] DR0: DR1: DR2: [16910.301414] DR3: DR6: fffe0ff0 DR7: 0400 [16910.301458] PKRU: 5554 [16910.301477] Call Trace: [16910.301504] nvme_rdma_configure_admin_queue+0x22/0x2d0 [nvme_rdma] [16910.301548] nvme_rdma_reconnect_ctrl_work+0x27/0xd0 [nvme_rdma] [16910.301591] process_one_work+0x1de/0x410 [16910.301620] worker_thread+0x32/0x410 [16910.301651] kthread+0x121/0x140 [16910.301676] ? process_one_work+0x410/0x410 [16910.301707] ? kthread_create_worker_on_cpu+0x70/0x70 [16910.301744] ? do_syscall_64+0x73/0x130 [16910.301774] ? SyS_exit_group+0x14/0x20 [16910.301805] ret_from_fork+0x35/0x40 [16910.301831] Code: 89 e5 41 56 41 55 41 54 53 48 8d 1c c5 00 00 00 00 49 89 fc 49 89 c5 49 89 d6 48 29 c3 48 c7 c2 00 86 b5 c0 48 c1 e3 04 48 03 1f <48> 89 7b 18 48 8d 7b 58 c7 43 50 00 00 00 00 e8 20 d4 57 ef 45 [16910.305367] RIP: nvme_rdma_alloc_queue+0x3c/0x190 [nvme_rdma] RSP: 9ba8a037be08 [16910.307146] ---[ end trace 3ae215b72b2ac870 ]--- # # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic # # uname -a Linux esdev005 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790511/+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 1790511] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1790511 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790511 Title: General protection fault while trying to discover a nvmeof target Status in linux package in Ubuntu: Incomplete Bug description: nvme discover command times out and results in general protection fault in kernel. # nvme discover -t rdma -a 10.1.1.6 -s 4420 Failed to write to /dev/nvme-fabrics: Input/output error^M # # [16900.248129] nvme nvme0: Connect command failed, error wo/DNR bit: 7 [16900.248182] nvme nvme0: failed to connect queue: 0 ret=7 [16900.253138] nvme nvme0: Reconnecting in 10 seconds... [16910.300029] general protection fault: [#1] SMP PTI [16910.300069] Modules linked in: mlx4_en mlx4_ib mlx4_core nvme_rdma nvme_fabrics nvme_core rdma_ucm ib_umad ib_ucm ib_uverbs xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_addrtype overlay aufs joydev input_leds ipmi_ssif intel_rapl skx_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass intel_cstate intel_rapl_perf mei_me mei ioatdma lpc_ich shpchp sch_fq_codel ipmi_si ipmi_devintf ipmi_msghandler acpi_pad mac_hid acpi_power_meter iptable_filter ip6table_filter ip6_tables br_netfilter bridge stp llc arp_tables ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov [16910.300534] async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_core hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd mlx5_core ast mlxfw i2c_algo_bit devlink ttm drm_kms_helper ixgbe syscopyarea sysfillrect sysimgblt fb_sys_fops dca ptp drm pps_core mdio ahci libahci wmi [last unloaded: nvme_core] [16910.300794] CPU: 33 PID: 3173 Comm: kworker/u146:1 Not tainted 4.15.0-33-generic #36-Ubuntu [16910.300845] Hardware name: Supermicro SYS-6019U-TN4RT/X11DPU, BIOS 2.0b 02/24/2018 [16910.300898] Workqueue: nvme-wq nvme_rdma_reconnect_ctrl_work [nvme_rdma] [16910.300945] RIP: 0010:nvme_rdma_alloc_queue+0x3c/0x190 [nvme_rdma] [16910.300984] RSP: 0018:9ba8a037be08 EFLAGS: 00010206 [16910.301019] RAX: RBX: 52404d65f5994178 RCX: 8a0f78002820 [16910.301063] RDX: c0b58600 RSI: c0b573ab RDI: 8a0f70aec000 [16910.301108] RBP: 9ba8a037be28 R08: 0334 R09: [16910.301152] R10: R11: 0337 R12: 8a0f70aec000 [16910.301195] R13: R14: 0020 R15: [16910.301240] FS: () GS:8a0f7efc() knlGS: [16910.301289] CS: 0010 DS: ES: CR0: 80050033 [16910.301326] CR2: 7ffc4e5cadb8 CR3: 00123ba0a003 CR4: 007606e0 [16910.301370] DR0: DR1: DR2: [16910.301414] DR3: DR6: fffe0ff0 DR7: 0400 [16910.301458] PKRU: 5554 [16910.301477] Call Trace: [16910.301504] nvme_rdma_configure_admin_queue+0x22/0x2d0 [nvme_rdma] [16910.301548] nvme_rdma_reconnect_ctrl_work+0x27/0xd0 [nvme_rdma] [16910.301591] process_one_work+0x1de/0x410 [16910.301620] worker_thread+0x32/0x410 [16910.301651] kthread+0x121/0x140 [16910.301676] ? process_one_work+0x410/0x410 [16910.301707] ? kthread_create_worker_on_cpu+0x70/0x70 [16910.301744] ? do_syscall_64+0x73/0x130 [16910.301774] ? SyS_exit_group+0x14/0x20 [16910.301805] ret_from_fork+0x35/0x40 [16910.301831] Code: 89 e5 41 56 41 55 41 54 53 48 8d 1c c5 00 00 00 00 49 89 fc 49 89 c5 49 89 d6 48 29 c3 48 c7 c2 00 86 b5 c0 48 c1 e3 04 48 03 1f <48> 89 7b 18 48 8d 7b 58 c7 43 50 00 00 00 00 e8 20 d4 57 ef 45 [16910.305367] RIP: nvme_rdma_alloc_queue+0x3c/0x190 [nvme_rdma] RSP: 9ba8a037be08 [16910.307146] ---[ end trace 3ae215b72b2ac870 ]--- # # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic # # uname -a
[Kernel-packages] [Bug 1523088] Re: WARN_ON(!wm_changed) warning and stacktrace in kernel log
Following on 4.2.0-generic (16.04 does not boot at all. At least most of the time): [ 601.848346] WARNING: CPU: 0 PID: 50 at /build/linux-lts-wily-Ejb_ce/linux-lts-wily-4.2.0/drivers/gpu/drm/i915/intel_pm.c:3404 skl_update_other_pipe_wm+0x205/0x210 [i915]() [ 601.848349] WARN_ON(!wm_changed) [ 601.848390] Modules linked in: bridge stp llc intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm i915 crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd drm_kms_helper binfmt_misc shpchp input_leds drm mei_me mei nls_iso8859_1 8250_fintek i2c_hid video pinctrl_sunrisepoint intel_lpss_acpi pinctrl_intel intel_lpss acpi_als wmi kfifo_buf industrialio acpi_pad lp mac_hid parport hid_generic igb e1000e i2c_algo_bit dca usbhid ptp ahci hid pps_core libahci [ 601.848395] CPU: 0 PID: 50 Comm: kworker/0:1 Tainted: GW 4.2.0-42-generic #49~14.04.1-Ubuntu [ 601.848397] Hardware name: Default string Default string/SKYBAY, BIOS 5.11 09/25/2017 [ 601.848406] Workqueue: events console_callback [ 601.848411] 88042f0a3618 817bc281 88042f0a3668 [ 601.848414] c0385370 88042f0a3658 8107998a 88042f0a3790 [ 601.848418] 88042ba23000 88042f0a3700 88042f0a37b4 88042ba22000 [ 601.848419] Call Trace: [ 601.848426] [] dump_stack+0x63/0x81 [ 601.848435] [] warn_slowpath_common+0x8a/0xc0 [ 601.848440] [] warn_slowpath_fmt+0x46/0x50 [ 601.848468] [] skl_update_other_pipe_wm+0x205/0x210 [i915] [ 601.848497] [] skl_update_wm+0x1f6/0x810 [i915] [ 601.848501] [] ? __schedule+0x358/0x930 [ 601.848530] [] intel_update_watermarks+0x1e/0x30 [i915] [ 601.848578] [] haswell_crtc_disable+0x167/0x330 [i915] [ 601.848623] [] intel_crtc_control+0x5e/0x110 [i915] [ 601.848662] [] intel_crtc_update_dpms+0x5e/0x80 [i915] [ 601.848703] [] intel_connector_dpms+0x5e/0x70 [i915] [ 601.848719] [] drm_fb_helper_dpms.isra.6+0x95/0xe0 [drm_kms_helper] [ 601.848730] [] drm_fb_helper_blank+0x32/0x80 [drm_kms_helper] [ 601.848773] [] intel_fbdev_blank+0x1a/0x60 [i915] [ 601.848779] [] ? blocking_notifier_call_chain+0x16/0x20 [ 601.848784] [] fb_blank+0x57/0xb0 [ 601.848789] [] fbcon_blank+0x1fe/0x2b0 [ 601.848794] [] ? dequeue_entity+0x152/0x690 [ 601.848799] [] ? get_color.isra.15+0x35/0x110 [ 601.848804] [] ? lock_timer_base.isra.35+0x58/0x80 [ 601.848807] [] ? try_to_del_timer_sync+0x4f/0x70 [ 601.848812] [] do_blank_screen+0x1bd/0x260 [ 601.848817] [] console_callback+0x68/0x150 [ 601.848819] [] ? __schedule+0x358/0x930 [ 601.848826] [] process_one_work+0x150/0x3f0 [ 601.848831] [] worker_thread+0x11a/0x470 [ 601.848837] [] ? rescuer_thread+0x310/0x310 [ 601.848840] [] kthread+0xc9/0xe0 [ 601.848845] [] ? kthread_create_on_node+0x1c0/0x1c0 [ 601.848849] [] ret_from_fork+0x3f/0x70 [ 601.848853] [] ? kthread_create_on_node+0x1c0/0x1c0 [ 601.848856] ---[ end trace 3cea3aacb2b553b0 ]--- -- 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/1523088 Title: WARN_ON(!wm_changed) warning and stacktrace in kernel log Status in X.Org X server: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I always get an warning and stacktrace (and it seems to hang a little bit). This occurs after reboot as well as when I move with the cursor between my hdmi monitor and my laptop. (This only occurs when HDMI is connected) Default Kubuntu install version 15.10 with kernel 4.2.0-19-generic Processor: i5 6300hq Graphics: gtx950m WARNING: CPU: 1 PID: 827 at /build/linux-26_gwp/linux-4.2.0/drivers/gpu/drm/i915/intel_pm.c:3404 skl_update_other_pipe_wm+0x1de/0x1f0 [i915]() [Sam Dez 5 12:34:46 2015] WARN_ON(!wm_changed) [Sam Dez 5 12:34:46 2015] Modules linked in: [Sam Dez 5 12:34:46 2015] nls_iso8859_1 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) drbg ansi_cprng ctr ccm rfcomm bnep arc4 rtsx_usb_ms memstick i2c_designware_platform i2c_designware_core acer_wmi sparse_keymap snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core intel_rapl snd_hwdep iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul snd_seq_device glue_helper snd_timer ablk_helper cryptd ath10k_pci ath10k_core snd ath mac80211 serio_raw soundcore idma64 virt_dma cfg80211 joydev input_leds uvcvideo mei_me videobuf2_vmalloc videobuf2_memops mei videobuf2_core v4l2_common intel_lpss_pci videodev media [Sam Dez 5 12:34:46 2015] btusb btrtl btbcm btintel bluetooth shpchp dell_smo8800 intel_lpss_acpi intel_lpss tpm_crb acpi_pad mac_hid parport_pc ppdev lp parport autofs4 hid_generic hid_logitech_hidpp hid_logitech_
[Kernel-packages] [Bug 1523088] Re: WARN_ON(!wm_changed) warning and stacktrace in kernel log
And that one goes for darn PICO500 machine >_< -- 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/1523088 Title: WARN_ON(!wm_changed) warning and stacktrace in kernel log Status in X.Org X server: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I always get an warning and stacktrace (and it seems to hang a little bit). This occurs after reboot as well as when I move with the cursor between my hdmi monitor and my laptop. (This only occurs when HDMI is connected) Default Kubuntu install version 15.10 with kernel 4.2.0-19-generic Processor: i5 6300hq Graphics: gtx950m WARNING: CPU: 1 PID: 827 at /build/linux-26_gwp/linux-4.2.0/drivers/gpu/drm/i915/intel_pm.c:3404 skl_update_other_pipe_wm+0x1de/0x1f0 [i915]() [Sam Dez 5 12:34:46 2015] WARN_ON(!wm_changed) [Sam Dez 5 12:34:46 2015] Modules linked in: [Sam Dez 5 12:34:46 2015] nls_iso8859_1 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) drbg ansi_cprng ctr ccm rfcomm bnep arc4 rtsx_usb_ms memstick i2c_designware_platform i2c_designware_core acer_wmi sparse_keymap snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core intel_rapl snd_hwdep iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul snd_seq_device glue_helper snd_timer ablk_helper cryptd ath10k_pci ath10k_core snd ath mac80211 serio_raw soundcore idma64 virt_dma cfg80211 joydev input_leds uvcvideo mei_me videobuf2_vmalloc videobuf2_memops mei videobuf2_core v4l2_common intel_lpss_pci videodev media [Sam Dez 5 12:34:46 2015] btusb btrtl btbcm btintel bluetooth shpchp dell_smo8800 intel_lpss_acpi intel_lpss tpm_crb acpi_pad mac_hid parport_pc ppdev lp parport autofs4 hid_generic hid_logitech_hidpp hid_logitech_dj usbhid rtsx_usb_sdmmc rtsx_usb uas usb_storage nouveau i915 mxm_wmi ttm i2c_algo_bit drm_kms_helper r8169 mii drm ahci libahci i2c_hid hid wmi pinctrl_sunrisepoint video pinctrl_intel [Sam Dez 5 12:34:46 2015] CPU: 1 PID: 827 Comm: Xorg Tainted: GW OE 4.2.0-19-generic #23-Ubuntu [Sam Dez 5 12:34:46 2015] Hardware name: Acer Aspire V5-591G/Usopp_SLS, BIOS V1.03 10/23/2015 [Sam Dez 5 12:34:46 2015] a287b8f0 880071b03518 817e93f9 [Sam Dez 5 12:34:46 2015] 880071b03570 880071b03558 8107b3d6 [Sam Dez 5 12:34:46 2015] 880071b03620 880071b036c4 880279bf2000 880279bf7000 [Sam Dez 5 12:34:46 2015] Call Trace: [Sam Dez 5 12:34:46 2015] [] dump_stack+0x45/0x57 [Sam Dez 5 12:34:46 2015] [] warn_slowpath_common+0x86/0xc0 [Sam Dez 5 12:34:46 2015] [] warn_slowpath_fmt+0x55/0x70 [Sam Dez 5 12:34:46 2015] [] skl_update_other_pipe_wm+0x1de/0x1f0 [i915] [Sam Dez 5 12:34:46 2015] [] skl_update_wm+0x1bb/0x740 [i915] [Sam Dez 5 12:34:46 2015] [] ? gen9_read32+0xf7/0x2d0 [i915] [Sam Dez 5 12:34:46 2015] [] ? i915_get_vblank_timestamp+0x62/0xa0 [i915] [Sam Dez 5 12:34:46 2015] [] intel_update_watermarks+0x1e/0x30 [i915] [Sam Dez 5 12:34:46 2015] [] intel_finish_crtc_commit+0x169/0x190 [i915] [Sam Dez 5 12:34:46 2015] [] drm_atomic_helper_commit_planes_on_crtc+0x143/0x260 [drm_kms_helper] [Sam Dez 5 12:34:46 2015] [] intel_atomic_commit+0x6b/0x100 [i915] [Sam Dez 5 12:34:46 2015] [] drm_atomic_commit+0x37/0x60 [drm] [Sam Dez 5 12:34:46 2015] [] drm_atomic_helper_disable_plane+0xef/0x130 [drm_kms_helper] [Sam Dez 5 12:34:46 2015] [] __setplane_internal+0x23a/0x2f0 [drm] [Sam Dez 5 12:34:46 2015] [] drm_mode_cursor_universal+0x12b/0x210 [drm] [Sam Dez 5 12:34:46 2015] [] ? __ww_mutex_lock+0x5f/0xa0 [Sam Dez 5 12:34:46 2015] [] drm_mode_cursor_common+0x81/0x180 [drm] [Sam Dez 5 12:34:46 2015] [] drm_mode_cursor_ioctl+0x50/0x70 [drm] [Sam Dez 5 12:34:46 2015] [] drm_ioctl+0x125/0x610 [drm] [Sam Dez 5 12:34:46 2015] [] ? drm_mode_setcrtc+0x500/0x500 [drm] [Sam Dez 5 12:34:46 2015] [] do_vfs_ioctl+0x295/0x480 [Sam Dez 5 12:34:46 2015] [] ? __set_task_blocked+0x41/0xa0 [Sam Dez 5 12:34:46 2015] [] SyS_ioctl+0x79/0x90 [Sam Dez 5 12:34:46 2015] [] entry_SYSCALL_64_fastpath+0x16/0x75 [Sam Dez 5 12:34:46 2015] ---[ end trace c72c2dc92b88cd01 ]--- ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg-core 2:1.17.2-1ubuntu9.1 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Sat Dec 5 12:35:24 2015 ExecutablePath: /usr/bin/Xorg InstallationDate: Installed on 2015-12-04 (0 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: xor
[Kernel-packages] [Bug 1782544] Re: tcpreplay and veth device; extra transmit bytes on 4.4.0-130-generic kernel
I just upgraded my system and the bug is there. kernel 4.15.0-33-generic Ubuntu 18.04.1 LTS -- 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/1782544 Title: tcpreplay and veth device; extra transmit bytes on 4.4.0-130-generic kernel Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Issue found in a test harness for some code running on Ubuntu 16.04.4 LTS where we use a veth device to play in packets to the code under test. Essentially we see an extra 14 bytes being transmitted at the end of every packet that is just random garbage. Problem came in with the 4.4.0-130 kernel; if I revert to the 4.4.0-128 kernel the issue goes away. I have verified the issue on several different boxes running 16.04 The following steps reproduce the problem: 1) Veth setup sudo ip link add name nic1 type veth peer name nic2 sudo sysctl -q -w net.ipv6.conf.nic1.disable_ipv6=1 sudo sysctl -q -w net.ipv6.conf.nic2.disable_ipv6=1 sudo ip link set nic1 up sudo ip link set nic2 up 2) Configure tcpdump to collect packets on one interface: sudo tcpdump -i nic1 -w outPkts.pcap 3) Play in packets on the other (Any pcap will do): sudo tcpreplay -q -i nic2 inPkts.pcap When I check ifconfig I can see nic2/nic1 transmitting/receiving more bytes than expected. Opening the capture seen by tcpdump shows an extra 14 bytes received for every packet when compared to the input. tcpreplay version info: tcpreplay version: 3.4.4 (build 2450) (debug) Copyright 2000-2010 by Aaron Turner Cache file supported: 04 Not compiled with libdnet. Compiled against libpcap: 1.7.4 64 bit packet counters: enabled Verbose printing via tcpdump: enabled Packet editing: disabled Fragroute engine: disabled Injection method: PF_PACKET send() tcpdump version info tcpdump version 4.9.2 libpcap version 1.7.4 OpenSSL 1.0.2g 1 Mar 2016 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-130-generic 4.4.0-130.156 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: spw3336 F pulseaudio /dev/snd/controlC0: spw3336 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 19 10:30:07 2018 HibernationDevice: RESUME=UUID=032369ab-18b8-41c3-a386-4ed08706f461 InstallationDate: Installed on 2016-11-03 (622 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. OptiPlex 7010 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic root=UUID=7b20f97c-4edc-4af1-bdbb-72ccb26cfbec ro quiet splash intel_iommu=on RelatedPackageVersions: linux-restricted-modules-4.4.0-130-generic N/A linux-backports-modules-4.4.0-130-generic N/A linux-firmware 1.157.20 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0KRC95 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/12/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0KRC95:rvrA02:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 7010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782544/+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 1788753] Re: linux-kvm: 4.15.0-1021.21 -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-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1788753 Title: linux-kvm: 4.15.0-1021.21 -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-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: New 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: 1788744 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/1788753/+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 1790515] Re: black screen on ubuntu GTX 1050 eGPU
** Description changed: I'm using a laptop lenovo thinkpad T410 with intel graphics and egpu + GTX 1050. (using expresscard or mini pcie both failed) - When I install the 390 driver my graphical display fails. I know that egpu is not the best solution but worked with some people. + When I install the 390 driver my graphical display fails. I know that egpu is not the best solution but for some people it works. + + I tried: + 390, 396, 384 nvidia drivers from ppa and from NVIDIA (.run) + Ubuntu and Xubuntu (18, 17, 16) using gdm3 and lightgdm + blacklist nouveau and everything similar + + Sometimes Ubuntu 18.04 freeze using live usb. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1790515 Title: black screen on ubuntu GTX 1050 eGPU Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I'm using a laptop lenovo thinkpad T410 with intel graphics and egpu + GTX 1050. (using expresscard or mini pcie both failed) When I install the 390 driver my graphical display fails. I know that egpu is not the best solution but for some people it works. I tried: 390, 396, 384 nvidia drivers from ppa and from NVIDIA (.run) Ubuntu and Xubuntu (18, 17, 16) using gdm3 and lightgdm blacklist nouveau and everything similar Sometimes Ubuntu 18.04 freeze using live usb. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1790515/+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 1752053] Re: nvidia-390 fails to boot graphical display
I am affected by this bug, too. Using an nVidia GTX 660 with legacy nvidia-340 (both mainline as well as graphics-driver ppa) my system is working as before. Switching to 390 or even 396 leaves me at a blinking cursor DM both on sddm and gdm3. The only DM I could use has been lightdm but only after I chowned the .Xauthority file of my user home dir whilst it was running (sadly this is a no go for me as I rely on multi user sessions which do not work anymore since the upgrade to bionic). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1790219] Re: Stuck on boot of my PC after switching to Nvidia-driver-390 proprietary driver and rebooting
** Attachment added: "boot1" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1790219/+attachment/5184179/+files/boot-1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1790219 Title: Stuck on boot of my PC after switching to Nvidia-driver-390 proprietary driver and rebooting Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: I was carrying out this testcase for proprietary Nvidia drivers testing: http://xorg.qa.ubuntu.com/qatracker/testcases/1704/info. After having installed Ubuntu 18.10 on a new partition on my PC, I switched to Nvidia-driver-390 proprietary driver from Additional Drivers tab of Software & Update and rebooted my PC. On reboot I got low resolution Ubuntu logo, pressing F1 I could read this message: (1 of 2) A start Job is running for Hold until snapd is fully seeded (15 min 23s/ no limit). (2 of 2) A start Job is running for Hold until snapd is fully seeded (15 min 25s/ no limit). I rebooted after waiting 15 minutes as I was tired of waiting. This is my display hardware: *-display description: VGA compatible controller product: GM206 [GeForce GTX 960] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:125 memory:de00-deff memory:c000-cfff memory:d000-d1ff ioport:e000(size=128) memory:c-d Link to the testcase revision Edit result My PC is a: product: XPS 8900 (06B8) vendor: Dell Inc. width: 64 bits To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1790219/+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 1790219] Re: Stuck on boot of my PC after switching to Nvidia-driver-390 proprietary driver and rebooting
** Attachment added: "boot0" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1790219/+attachment/5184180/+files/boot-0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1790219 Title: Stuck on boot of my PC after switching to Nvidia-driver-390 proprietary driver and rebooting Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: I was carrying out this testcase for proprietary Nvidia drivers testing: http://xorg.qa.ubuntu.com/qatracker/testcases/1704/info. After having installed Ubuntu 18.10 on a new partition on my PC, I switched to Nvidia-driver-390 proprietary driver from Additional Drivers tab of Software & Update and rebooted my PC. On reboot I got low resolution Ubuntu logo, pressing F1 I could read this message: (1 of 2) A start Job is running for Hold until snapd is fully seeded (15 min 23s/ no limit). (2 of 2) A start Job is running for Hold until snapd is fully seeded (15 min 25s/ no limit). I rebooted after waiting 15 minutes as I was tired of waiting. This is my display hardware: *-display description: VGA compatible controller product: GM206 [GeForce GTX 960] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:125 memory:de00-deff memory:c000-cfff memory:d000-d1ff ioport:e000(size=128) memory:c-d Link to the testcase revision Edit result My PC is a: product: XPS 8900 (06B8) vendor: Dell Inc. width: 64 bits To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1790219/+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 1790219] Re: Stuck on boot of my PC after switching to Nvidia-driver-390 proprietary driver and rebooting
Hello Jean-Baptiste, I am attaching the three boots I have detected with journalctl --list-boots. ** Attachment added: "boot2" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1790219/+attachment/5184178/+files/boot-2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1790219 Title: Stuck on boot of my PC after switching to Nvidia-driver-390 proprietary driver and rebooting Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: I was carrying out this testcase for proprietary Nvidia drivers testing: http://xorg.qa.ubuntu.com/qatracker/testcases/1704/info. After having installed Ubuntu 18.10 on a new partition on my PC, I switched to Nvidia-driver-390 proprietary driver from Additional Drivers tab of Software & Update and rebooted my PC. On reboot I got low resolution Ubuntu logo, pressing F1 I could read this message: (1 of 2) A start Job is running for Hold until snapd is fully seeded (15 min 23s/ no limit). (2 of 2) A start Job is running for Hold until snapd is fully seeded (15 min 25s/ no limit). I rebooted after waiting 15 minutes as I was tired of waiting. This is my display hardware: *-display description: VGA compatible controller product: GM206 [GeForce GTX 960] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:125 memory:de00-deff memory:c000-cfff memory:d000-d1ff ioport:e000(size=128) memory:c-d Link to the testcase revision Edit result My PC is a: product: XPS 8900 (06B8) vendor: Dell Inc. width: 64 bits To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1790219/+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 1788762] Re: linux: 3.2.0-135.181 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1788762 Title: linux: 3.2.0-135.181 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed 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-lbm 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: 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 package in Ubuntu: New Status in linux source package in Precise: New 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: -- 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/1788762/+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 1726299]
Created attachment 278265 UCSI trace It looks like on XPS13, the UCSI notifications are broken. Attached is a ftrace log that shows what happens if I enable UCSI tracing, plug in the device, insmod ucsi_acpi, then remove the device, then plug it back in. The ACPI notification works, but after the first notification, the UCSI SET_NOTIFICATION_ENABLE command fails: rmmod-5920 [001] 846293.522800: ucsi_command: control=00010005 (SET_NOTIFICATION_ENABLE) kworker/0:1-4132 [000] 846293.695298: ucsi_notify: CCI=0002 Connector Change rmmod-5920 [002] 846298.845856: ucsi_run_command: SET_NOTIFICATION_ENABLE -> FAIL (err=-110) kworker/0:1-4132 [000] 846298.845870: ucsi_command: control=00010012 (GET_CONNECTOR_STATUS) kworker/0:0-31458 [000] .N.. 846299.011370: ucsi_notify: CCI=8902 Event pending (command completed) kworker/0:1-4132 [000] 846299.043161: ucsi_ack: ACK command kworker/0:0-31458 [000] .N.. 846299.213819: ucsi_notify: CCI=2000 ACK completed kworker/0:1-4132 [000] 846299.213823: ucsi_run_command: GET_CONNECTOR_STATUS -> OK (err=0) kworker/0:1-4132 [000] 846299.213824: typec_set_pwr_role <-ucsi_connector_change kworker/0:1-4132 [000] 846299.213824: typec_set_data_role <-ucsi_connector_change kworker/0:1-4132 [000] 846299.213825: ucsi_ack: ACK event kworker/0:1-4132 [000] 846299.239159: ucsi_connector_change: port0 status: change=4040, opmode=1, connected=0, sourcing=0, partner_flags=0, partner_type=1, request_data_obj=, BC status=1 -- 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/1726299 Title: Apple Thunderbolt 2 to FireWire adapter not working Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The adapter is connected through an Apple Thunderbolt 3 to Thunderbolt 2 adapter. Ubuntu seems not to recognize the Firewire adapter. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.04 Release:17.04 Codename: zesty uname -r 4.10.0-19-generic sudo lshw -short H/W-Pfad Gerät Klasse Beschreibung === system Z170N-Gaming 5 (Default string) /0 busZ170N-Gaming 5 /0/0memory 64KiB BIOS /0/3d memory 16GiB Systemspeicher /0/3d/0 memory 8GiB DIMM DDR4 Synchron 2133 MHz (0,5 ns) /0/3d/1 memory Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME POT-Creatio /0/3d/2 memory 8GiB DIMM DDR4 Synchron 2133 MHz (0,5 ns) /0/3d/3 memory Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME POT-Creatio /0/43 memory 128KiB L1 Cache /0/44 memory 512KiB L2 Cache /0/45 memory 3MiB L3 Cache /0/46 processor Intel(R) Core(TM) i3-6100T CPU @ 3.20GHz /0/100 bridge Skylake Host Bridge/DRAM Registers /0/100/1bridge Skylake PCIe Controller (x16) /0/100/1/0 displayOland GL [FirePro W2100] /0/100/1/0.1multimedia Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] /0/100/14 busSunrise Point-H USB 3.0 xHCI Controller /0/100/14/0 usb1 busxHCI Host Controller /0/100/14/0/6 input USB Gaming Keyboard /0/100/14/0/d communication Bluetooth-Schnittstelle /0/100/14/1 usb2 busxHCI Host Controller /0/100/14/1/5scsi6 storageStorage Media /0/100/14/1/5/0.0.0 /dev/sdb disk 15GB Storage Media /0/100/14/1/5/0.0.0/0/dev/sdb disk 15GB /0/100/14/1/5/0.0.0/0/2 /dev/sdb2 volume 15EiB Windows FAT Laufwerk /0/100/16 communication Sunrise Point-H CSME HECI #1 /0/100/17 storageSunrise Point-H SATA controller [AHCI mode] /0/100/1b bridge Sunrise Point-H PCI Root Port #17 /0/100/1b.2 bridge Sunrise Point-H PCI Root Port #19 /0/100/1b.3 bridge Sunrise Point-H PCI Root Port #20 /0/100/1c bridge Sunrise Point-H PCI Expres
[Kernel-packages] [Bug 1719795]
Indeed. I wonder if you can unload (or blacklist) those drivers and see if the interrupt count goes low? -- 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/1719795 Title: Dell 7140 avarage power consumption in idle increased by 1.3-1.5 times due to events by INT3432 Status in Linux: Incomplete Status in linux package in Ubuntu: New Bug description: On Dell Venue 11 Pro 7140 average power consumption in idle increased by 1.3-1.5 times due to events coming from INT343A. According to powertop since Linux 4.10 INT3432:00 generate around two hundred events on average, in /sys/devices/pci:00/INT3432:00/i2c-6 there is two devices: INT343A and SMO91D0. AFAIK INT343A is rt286. With Linux 4.9.0-4.9.45, Linux 4.11.0-4.11.12 in idle there is around 100 wakeups per second in sum, battery discharge rate around 3-3.5 Watts per second. But with Linux 4.9.46-4.9.51, Linux 4.10.0-4.10.17, Linux 4.12.0rc1-4.13.3 - around 300 wakeups per second on average, due to events coming from INT3432:00. With Linux 4.13.3 battery discharge rate around 4.5 Watts per second. Probably some commit was backported to Linux 4.9 between .45 and .46 releases. I have no idea why issue is not reproducible on any Linux 4.11 release I tried. Sometimes INT3432 events rate fall from two hundred to one hundred for shorts period of time (for example I observe this right now on Linux 4.10.0 while removing/installing packages). Message like this sometimes appear in dmesg: [ 731.226730] i2c_hid i2c-SMO91D0:00: i2c_hid_get_input: incomplete report (53/13568) Complete dmesg with Linux 4.13.3 is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1719795/+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 1776563]
can confirm bug is also present on Acer Aspire A315-41G with ryzen 3 2200u and radeon 535. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: New Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+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 1719795]
I see SMO91D0:00 (Sensor Hub) is also generating some amount of interrupts. Maybe something is generating a lot of events from there and that causes a lot of I2C traffic from drivers? -- 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/1719795 Title: Dell 7140 avarage power consumption in idle increased by 1.3-1.5 times due to events by INT3432 Status in Linux: Incomplete Status in linux package in Ubuntu: New Bug description: On Dell Venue 11 Pro 7140 average power consumption in idle increased by 1.3-1.5 times due to events coming from INT343A. According to powertop since Linux 4.10 INT3432:00 generate around two hundred events on average, in /sys/devices/pci:00/INT3432:00/i2c-6 there is two devices: INT343A and SMO91D0. AFAIK INT343A is rt286. With Linux 4.9.0-4.9.45, Linux 4.11.0-4.11.12 in idle there is around 100 wakeups per second in sum, battery discharge rate around 3-3.5 Watts per second. But with Linux 4.9.46-4.9.51, Linux 4.10.0-4.10.17, Linux 4.12.0rc1-4.13.3 - around 300 wakeups per second on average, due to events coming from INT3432:00. With Linux 4.13.3 battery discharge rate around 4.5 Watts per second. Probably some commit was backported to Linux 4.9 between .45 and .46 releases. I have no idea why issue is not reproducible on any Linux 4.11 release I tried. Sometimes INT3432 events rate fall from two hundred to one hundred for shorts period of time (for example I observe this right now on Linux 4.10.0 while removing/installing packages). Message like this sometimes appear in dmesg: [ 731.226730] i2c_hid i2c-SMO91D0:00: i2c_hid_get_input: incomplete report (53/13568) Complete dmesg with Linux 4.13.3 is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1719795/+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 1726299]
Created attachment 278257 USB PD trace I've sniffed the USB PD communication (see attachment) that happens when the adapter is plugged in. It goes as follows: -> REQ Disc Ident SVID:0xff00 <- ACK Disc Ident SVID:0xff00 VDO:0x6c0005ac VDO:0x VDO:0x16570348 VDO:100a (this carries the USB VID/PID and identifies the dongle as an alternate mode adapter) -> REQ Disc SVID SVID:0xff00 <- GOOD CRC <- ACK Disc SVID SVID:0xff00 VDO:0x808705ac VDO:0x -> GOOD CRC -> REQ Disc Mode SVID:0x8087 <- GOOD CRC <- ACK Disc Mode SVID:0x8087 VDO:0x00010001 -> GOOD CRC No further communication happens. I'm not yet sure why the PD controller in XPS13 doesn't send an Enter Mode command. -- 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/1726299 Title: Apple Thunderbolt 2 to FireWire adapter not working Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The adapter is connected through an Apple Thunderbolt 3 to Thunderbolt 2 adapter. Ubuntu seems not to recognize the Firewire adapter. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.04 Release:17.04 Codename: zesty uname -r 4.10.0-19-generic sudo lshw -short H/W-Pfad Gerät Klasse Beschreibung === system Z170N-Gaming 5 (Default string) /0 busZ170N-Gaming 5 /0/0memory 64KiB BIOS /0/3d memory 16GiB Systemspeicher /0/3d/0 memory 8GiB DIMM DDR4 Synchron 2133 MHz (0,5 ns) /0/3d/1 memory Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME POT-Creatio /0/3d/2 memory 8GiB DIMM DDR4 Synchron 2133 MHz (0,5 ns) /0/3d/3 memory Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME POT-Creatio /0/43 memory 128KiB L1 Cache /0/44 memory 512KiB L2 Cache /0/45 memory 3MiB L3 Cache /0/46 processor Intel(R) Core(TM) i3-6100T CPU @ 3.20GHz /0/100 bridge Skylake Host Bridge/DRAM Registers /0/100/1bridge Skylake PCIe Controller (x16) /0/100/1/0 displayOland GL [FirePro W2100] /0/100/1/0.1multimedia Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] /0/100/14 busSunrise Point-H USB 3.0 xHCI Controller /0/100/14/0 usb1 busxHCI Host Controller /0/100/14/0/6 input USB Gaming Keyboard /0/100/14/0/d communication Bluetooth-Schnittstelle /0/100/14/1 usb2 busxHCI Host Controller /0/100/14/1/5scsi6 storageStorage Media /0/100/14/1/5/0.0.0 /dev/sdb disk 15GB Storage Media /0/100/14/1/5/0.0.0/0/dev/sdb disk 15GB /0/100/14/1/5/0.0.0/0/2 /dev/sdb2 volume 15EiB Windows FAT Laufwerk /0/100/16 communication Sunrise Point-H CSME HECI #1 /0/100/17 storageSunrise Point-H SATA controller [AHCI mode] /0/100/1b bridge Sunrise Point-H PCI Root Port #17 /0/100/1b.2 bridge Sunrise Point-H PCI Root Port #19 /0/100/1b.3 bridge Sunrise Point-H PCI Root Port #20 /0/100/1c bridge Sunrise Point-H PCI Express Root Port #1 /0/100/1c/0 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/0 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/1 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/2 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/2/0 busDSL6540 USB 3.1 Controller [Alpine Ridge] /0/100/1c/0/2/0/0usb3 busxHCI Host Controller /0/100/1c/0/2/0/0/1 genericThunderbolt 3 (USB-C) to Thunderbolt 2 Adapter /0/100/1c/0/2/0/0/2 input USB Optical Mouse /0/100/1c/0/2/0/1usb4 busxHCI Host Controller /0/100/1c/0/4 bridge DSL6540 Thunderbolt
[Kernel-packages] [Bug 1726299]
Created attachment 278267 UCSI altmode support patch The previous comment isn't entirely correct. UCSI notifications are broken, but the command failure I quoted has nothing to do with it, it was just an artefact. I do not know why they are broken. It looks like the Linux UCSI driver does not support alternate modes. I wrote a patch against kernel tag 4.17 (attached) that adds support for requesting and setting alternate modes, if advertised by UCSI. It's hacky (more than one MID per SVID is probably broken, and activating modes via port partner sysfs node doesn't work) but it's sufficient for testing. Here's what I get in dmesg with the patch when plugging in the adapter: [856816.978580] ucsi_acpi USBC000:00: con1: found port altmode 8087:0001 [856816.978606] ucsi_acpi USBC000:00: con1: found port altmode ff01:1c46 [856817.128092] ucsi_acpi USBC000:00: con1: found port altmode 413c:0001 [856817.282308] ucsi_acpi USBC000:00: con1: in altmode index 0 [856818.277557] ucsi_acpi USBC000:00: con1: found partner altmode 8087:0001 It looks like the USB PD controller in XPS13 ignores the 05ac SVID in the ACK Disc PD message, and doesn't even try to request the altmode list for that SVID. This makes sense, because it doesn't support any Apple-specific altmodes. I'm now looking into reflashing the adapter such that it would advertise some SVID:MID pair that is recognized by XPS13. I don't actually know if there's any; if you know what other Thunderbolt adapters use, please share. -- 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/1726299 Title: Apple Thunderbolt 2 to FireWire adapter not working Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The adapter is connected through an Apple Thunderbolt 3 to Thunderbolt 2 adapter. Ubuntu seems not to recognize the Firewire adapter. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.04 Release:17.04 Codename: zesty uname -r 4.10.0-19-generic sudo lshw -short H/W-Pfad Gerät Klasse Beschreibung === system Z170N-Gaming 5 (Default string) /0 busZ170N-Gaming 5 /0/0memory 64KiB BIOS /0/3d memory 16GiB Systemspeicher /0/3d/0 memory 8GiB DIMM DDR4 Synchron 2133 MHz (0,5 ns) /0/3d/1 memory Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME POT-Creatio /0/3d/2 memory 8GiB DIMM DDR4 Synchron 2133 MHz (0,5 ns) /0/3d/3 memory Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME POT-Creatio /0/43 memory 128KiB L1 Cache /0/44 memory 512KiB L2 Cache /0/45 memory 3MiB L3 Cache /0/46 processor Intel(R) Core(TM) i3-6100T CPU @ 3.20GHz /0/100 bridge Skylake Host Bridge/DRAM Registers /0/100/1bridge Skylake PCIe Controller (x16) /0/100/1/0 displayOland GL [FirePro W2100] /0/100/1/0.1multimedia Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] /0/100/14 busSunrise Point-H USB 3.0 xHCI Controller /0/100/14/0 usb1 busxHCI Host Controller /0/100/14/0/6 input USB Gaming Keyboard /0/100/14/0/d communication Bluetooth-Schnittstelle /0/100/14/1 usb2 busxHCI Host Controller /0/100/14/1/5scsi6 storageStorage Media /0/100/14/1/5/0.0.0 /dev/sdb disk 15GB Storage Media /0/100/14/1/5/0.0.0/0/dev/sdb disk 15GB /0/100/14/1/5/0.0.0/0/2 /dev/sdb2 volume 15EiB Windows FAT Laufwerk /0/100/16 communication Sunrise Point-H CSME HECI #1 /0/100/17 storageSunrise Point-H SATA controller [AHCI mode] /0/100/1b bridge Sunrise Point-H PCI Root Port #17 /0/100/1b.2 bridge Sunrise Point-H PCI Root Port #19 /0/100/1b.3 bridge Sunrise Point-H PCI Root Port #20 /0/100/1c bridge Sunrise Point-H PCI Express Root Port #1 /0/100/1c/0 bridge DSL6540 Thunderbolt 3 Bridge [Alpine
[Kernel-packages] [Bug 1790560] [NEW] package linux-headers-4.4.0-47-generic 4.4.0-47.68 failed to install/upgrade: package linux-headers-4.4.0-47-generic is not ready for configuration cannot configu
Public bug reported: can't boot up Ubuntu in regular startup mode ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Uname: Linux 4.4.0-134-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jp 1816 F pulseaudio Date: Mon Sep 3 21:03:59 2018 DpkgHistoryLog: Start-Date: 2018-09-03 21:02:47 Requested-By: jp (1000) Upgrade: update-manager-core:amd64 (1:16.04.12, 1:16.04.13), libsystemd0:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), update-manager:amd64 (1:16.04.12, 1:16.04.13), gnome-software:amd64 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11), udev:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), libudev1:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), ubuntu-software:amd64 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11), python3-update-manager:amd64 (1:16.04.12, 1:16.04.13), systemd-sysv:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), libpam-systemd:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), systemd:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), gnome-software-common:amd64 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11) DuplicateSignature: package:linux-headers-4.4.0-47-generic:4.4.0-47.68 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1.1) ... dpkg: error processing package linux-headers-4.4.0-47-generic (--configure): package linux-headers-4.4.0-47-generic is not ready for configuration ErrorMessage: package linux-headers-4.4.0-47-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=e6421112-f714-4d3d-8304-e7118d3a9a84 InstallationDate: Installed on 2016-08-03 (761 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Vostro 1000 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-134-generic root=UUID=aeb7db14-ed22-4d5e-9a0f-58f0b72e8be5 ro recovery nomodeset PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18 SourcePackage: linux Title: package linux-headers-4.4.0-47-generic 4.4.0-47.68 failed to install/upgrade: package linux-headers-4.4.0-47-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.3 dmi.board.name: 0WY383 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.6.3:bd12/07/2007:svnDellInc.:pnVostro1000:pvrNotSpecified:rvnDellInc.:rn0WY383:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 1000 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1790560 Title: package linux-headers-4.4.0-47-generic 4.4.0-47.68 failed to install/upgrade: package linux-headers-4.4.0-47-generic is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: New Bug description: can't boot up Ubuntu in regular startup mode ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Uname: Linux 4.4.0-134-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jp 1816 F pulseaudio Date: Mon Sep 3 21:03:59 2018 DpkgHistoryLog: Start-Date: 2018-09-03 21:02:47 Requested-By: jp (1000) Upgrade: update-manager-core:amd64 (1:16.04.12, 1:16.04.13), libsystemd0:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), update-manager:amd64 (1:16.04.12, 1:16.04.13), gnome-software:amd64 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11), udev:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), libudev1:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), ubuntu-software:amd64 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11), python3-update-manager:amd64 (1:16.04.12, 1:16.04.13), systemd-sysv:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), libpam-systemd:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), systemd:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), gnome-software-common:amd64 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11) DuplicateSignature: package:linux-headers-4.4.0-47-generic:4.4.0-47.68 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1
[Kernel-packages] [Bug 1790560] Re: package linux-headers-4.4.0-47-generic 4.4.0-47.68 failed to install/upgrade: package linux-headers-4.4.0-47-generic is not ready for configuration cannot configure
** Tags removed: need-duplicate-check -- 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/1790560 Title: package linux-headers-4.4.0-47-generic 4.4.0-47.68 failed to install/upgrade: package linux-headers-4.4.0-47-generic is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: New Bug description: can't boot up Ubuntu in regular startup mode ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Uname: Linux 4.4.0-134-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jp 1816 F pulseaudio Date: Mon Sep 3 21:03:59 2018 DpkgHistoryLog: Start-Date: 2018-09-03 21:02:47 Requested-By: jp (1000) Upgrade: update-manager-core:amd64 (1:16.04.12, 1:16.04.13), libsystemd0:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), update-manager:amd64 (1:16.04.12, 1:16.04.13), gnome-software:amd64 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11), udev:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), libudev1:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), ubuntu-software:amd64 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11), python3-update-manager:amd64 (1:16.04.12, 1:16.04.13), systemd-sysv:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), libpam-systemd:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), systemd:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), gnome-software-common:amd64 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11) DuplicateSignature: package:linux-headers-4.4.0-47-generic:4.4.0-47.68 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1.1) ... dpkg: error processing package linux-headers-4.4.0-47-generic (--configure): package linux-headers-4.4.0-47-generic is not ready for configuration ErrorMessage: package linux-headers-4.4.0-47-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=e6421112-f714-4d3d-8304-e7118d3a9a84 InstallationDate: Installed on 2016-08-03 (761 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Vostro 1000 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-134-generic root=UUID=aeb7db14-ed22-4d5e-9a0f-58f0b72e8be5 ro recovery nomodeset PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18 SourcePackage: linux Title: package linux-headers-4.4.0-47-generic 4.4.0-47.68 failed to install/upgrade: package linux-headers-4.4.0-47-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.3 dmi.board.name: 0WY383 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.6.3:bd12/07/2007:svnDellInc.:pnVostro1000:pvrNotSpecified:rvnDellInc.:rn0WY383:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 1000 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790560/+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 1790560] 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/1790560 Title: package linux-headers-4.4.0-47-generic 4.4.0-47.68 failed to install/upgrade: package linux-headers-4.4.0-47-generic is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: Confirmed Bug description: can't boot up Ubuntu in regular startup mode ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Uname: Linux 4.4.0-134-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jp 1816 F pulseaudio Date: Mon Sep 3 21:03:59 2018 DpkgHistoryLog: Start-Date: 2018-09-03 21:02:47 Requested-By: jp (1000) Upgrade: update-manager-core:amd64 (1:16.04.12, 1:16.04.13), libsystemd0:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), update-manager:amd64 (1:16.04.12, 1:16.04.13), gnome-software:amd64 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11), udev:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), libudev1:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), ubuntu-software:amd64 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11), python3-update-manager:amd64 (1:16.04.12, 1:16.04.13), systemd-sysv:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), libpam-systemd:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), systemd:amd64 (229-4ubuntu21.2, 229-4ubuntu21.4), gnome-software-common:amd64 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11) DuplicateSignature: package:linux-headers-4.4.0-47-generic:4.4.0-47.68 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1.1) ... dpkg: error processing package linux-headers-4.4.0-47-generic (--configure): package linux-headers-4.4.0-47-generic is not ready for configuration ErrorMessage: package linux-headers-4.4.0-47-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=e6421112-f714-4d3d-8304-e7118d3a9a84 InstallationDate: Installed on 2016-08-03 (761 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Vostro 1000 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-134-generic root=UUID=aeb7db14-ed22-4d5e-9a0f-58f0b72e8be5 ro recovery nomodeset PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18 SourcePackage: linux Title: package linux-headers-4.4.0-47-generic 4.4.0-47.68 failed to install/upgrade: package linux-headers-4.4.0-47-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.3 dmi.board.name: 0WY383 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr2.6.3:bd12/07/2007:svnDellInc.:pnVostro1000:pvrNotSpecified:rvnDellInc.:rn0WY383:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 1000 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790560/+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 1685794] Re: Boot delayed for about 90 seconds until 'random: crng init done'
** Tags added: bionic ** Tags added: performance -- 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/1685794 Title: Boot delayed for about 90 seconds until 'random: crng init done' Status in linux package in Ubuntu: Confirmed Bug description: Shortened dmesg output, notice the unnaturally long delay before crng init finishes: [8.533630] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated [8.542239] input: HDA Intel PCH Mic as /devices/pci:00/:00:1b.0/sound/card1/input18 [8.542313] input: HDA Intel PCH Line as /devices/pci:00/:00:1b.0/sound/card1/input19 [8.542382] input: HDA Intel PCH Dock Line Out as /devices/pci:00/:00:1b.0/sound/card1/input20 [8.542449] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1b.0/sound/card1/input21 [8.544240] cdc_ether 2-6:2.0 usb0: register 'cdc_ether' at usb-:00:14.0-6, CDC Ethernet Device, 02:1e:10:1f:00:00 [8.544271] usbcore: registered new interface driver cdc_ether [8.637660] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' [8.654022] input: HP WMI hotkeys as /devices/virtual/input/input22 [8.688226] cdc_ether 2-6:2.0 enp0s20u6c2: renamed from usb0 [8.713288] iwlwifi :02:00.0 wlo1: renamed from wlan0 [9.804308] input: ST LIS3LV02DL Accelerometer as /devices/platform/lis3lv02d/input/input23 [ 98.327857] random: crng init done [ 98.330072] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 98.330073] Bluetooth: BNEP filters: protocol multicast [ 98.330077] Bluetooth: BNEP socket layer initialized [ 98.443281] kauditd_printk_skb: 90 callbacks suppressed [ 98.492927] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready [ 98.681030] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready [ 98.685672] IPv6: ADDRCONF(NETDEV_UP): enp0s20u6c2: link is not ready [ 98.685789] cdc_ether 2-6:2.0 enp0s20u6c2: kevent 12 may have been dropped [ 98.688384] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready [ 98.690915] iwlwifi :02:00.0: L1 Enabled - LTR Enabled ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: boot/vmlinuz-4.10.0-19-generic] ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7 Date: Mon Apr 24 14:58:33 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-04-18 (5 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=9fb9fc1d-15a4-4e98-a2ae-bf572e0900d5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.37 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: USH452L0B1 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685794/+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 1767782] Re: Ubuntu 18.04 : delay during boot - waiting for resume device - message : random: crng init
*** This bug is a duplicate of bug 1685794 *** https://bugs.launchpad.net/bugs/1685794 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 1685794, 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. ** Summary changed: - Xubuntu 18.04 : delay during boot - waiting for resume device - message : random: crng init + Ubuntu 18.04 : delay during boot - waiting for resume device - message : random: crng init ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed ** This bug has been marked a duplicate of bug 1685794 Boot delayed for about 90 seconds until 'random: crng init done' -- 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/1767782 Title: Ubuntu 18.04 : delay during boot - waiting for resume device - message : random: crng init Status in linux package in Ubuntu: Confirmed Status in plymouth package in Ubuntu: Confirmed Bug description: Xubuntu 18.04 : delay during boot [3.155746] sd 5:0:0:1: [sde] Attached SCSI removable disk [ 32.221209] random: crng init done ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: plymouth 0.9.3-1ubuntu7 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 BootLog: Error: [Errno 2] No such file or directory: '/var/log/boot.log' CurrentDesktop: XFCE Date: Sun Apr 29 12:14:19 2018 DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/sda11 ro ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/sda11 ro SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: H110M-HDS 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:bd01/25/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-HDS: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/1767782/+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 1765761] Re: Missing documentation for lockdown
Also: [ 5.277619] new mount options do not match the existing superblock, will be ignored [ 95.502081] random: crng init done is bug 1685794 :) -- 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/1765761 Title: Missing documentation for lockdown Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: When attempting to load unsigned modules and the signatures are enforced, a message shows in dmesg pointing to an inexistant manpage: [...] [5.154346] Adding 1003516k swap on /dev/mapper/10--3--99--105--vg-swap_1. Priority:-2 extents:1 across:1003516k FS [5.277619] new mount options do not match the existing superblock, will be ignored [ 95.502081] random: crng init done [ 110.298603] PKCS#7 signature not signed with a trusted key [ 110.298628] Lockdown: Loading of unsigned modules is restricted; see man kernel_lockdown.7 ubuntu@sacred-civet:~$ man kernel_lockdown.7 man: can't set the locale; make sure $LC_* and $LANG are correct No manual entry for kernel_lockdown.7 ubuntu@sacred-civet:~$ man 7 kernel_lockdown man: can't set the locale; make sure $LC_* and $LANG are correct No manual entry for kernel_lockdown in section 7 ubuntu@sacred-civet:~$ man kernel_lockdown man: can't set the locale; make sure $LC_* and $LANG are correct No manual entry for kernel_lockdown ubuntu@sacred-civet:~$ ubuntu@sacred-civet:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 Codename: bionic ubuntu@sacred-civet:~$ cat /proc/version_signature Ubuntu 4.15.0-13.14-generic 4.15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765761/+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 430809] Re: [Dell Latitude D430, iwl3945] Wireless can't be activated after disabling kill switch
Bug= 430809 is long fixed now but those who getting charger issue in there laptop can always get through https://laptopcharger.ae.they have also very wide range to select the desires product -- 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/430809 Title: [Dell Latitude D430, iwl3945] Wireless can't be activated after disabling kill switch Status in linux package in Ubuntu: Fix Released Status in linux source package in Karmic: Fix Released Bug description: It seems that this problem keeps reappearing. This is exactly the same as bug 193970, but opening a new bug since the first one is very big and noisy already. Summary: If I boot with the kill switch off (i. e. wifi enabled), the kill switch works just fine. But if I boot with kill switch on (i. e. wifi disabled), changing the kill switch doesn't do anything and network-manager keeps insisting that the network is disabled. ProblemType: Bug Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: martin 2634 F pulseaudio /dev/snd/controlC0: martin 2634 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xefebc000 irq 21' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:83847690,10280201,00102201' Controls : 7 Simple ctrls : 5 Card1.Amixer.info: Card hw:1 'Headset'/'Logitech Logitech USB Headset at usb-:00:1d.7-8.3.4, full speed' Mixer name : 'USB Mixer' Components : 'USB046d:0a01' Controls : 6 Simple ctrls : 2 CheckboxSubmission: 526c13623eeda7bcc3936c7be57b2d29 CheckboxSystem: c8e8edcc4d15e0d55af04774be77e330 Date: Wed Sep 16 17:49:06 2009 DistroRelease: Ubuntu 9.10 HibernationDevice: RESUME=UUID=5df2daed-eb83-4d60-a87c-9b71ff6b703f MachineType: Dell Inc. Latitude D430 Package: linux-image-2.6.31-10-generic 2.6.31-10.32lp429241apw2 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-10-generic root=UUID=e43b0104-23d3-4bb8-9710-effa762ca2f6 ro quiet splash ProcEnviron: PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-10.32lp429241apw2-generic RelatedPackageVersions: linux-backports-modules-2.6.31-10-generic N/A linux-firmware 1.18 SourcePackage: linux Uname: Linux 2.6.31-10-generic i686 dmi.bios.date: 05/21/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0HU754 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA00:bd05/21/2007:svnDellInc.:pnLatitudeD430:pvr:rvnDellInc.:rn0HU754:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D430 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/430809/+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 1780013] Re: Keyboard Backlight not working
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1780013 Title: Keyboard Backlight not working Status in linux package in Ubuntu: Expired Bug description: Tryed to set up /etc/default/grub with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor" and created /usr/share/X11/xorg.conf.d/80-backlight.conf with: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "sna" Option "Backlight" "acpi_video0" BusID "PCI:0:2:0" EndSection Still not working! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-24-generic 4.15.0-24.26 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tprigas1679 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jul 4 05:37:45 2018 InstallationDate: Installed on 2018-06-27 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: TOSHIBA QOSMIO X770 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=3ce7f2da-4fdf-4100-b7d3-0a9be1c0d836 ro quiet splash acpi_backlight=vendor vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: 2.10 dmi.board.asset.tag: NULL dmi.board.name: PGRAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvr2.10:bd10/30/2012:svnTOSHIBA:pnQOSMIOX770:pvrPSBY5E-02Q00NEP:rvnTOSHIBA:rnPGRAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: QOSMIO X770 dmi.product.version: PSBY5E-02Q00NEP dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780013/+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 1770475] Re: linux 4.15.0-21-generic messes up plymouth and no logo on luks password prompt
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1770475 Title: linux 4.15.0-21-generic messes up plymouth and no logo on luks password prompt Status in kubuntu-default-settings package in Ubuntu: Expired Status in kubuntu-settings package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in plymouth package in Ubuntu: Expired Bug description: Old problem with 4.15.0-20-generic: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768647 New problem with 4.15.0-21-generic: installing packages as specified in mentioned bug, the kde logo does not display properly at password prompt for luks. See attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-default-settings/+bug/1770475/+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 1770475] Re: linux 4.15.0-21-generic messes up plymouth and no logo on luks password prompt
[Expired for plymouth (Ubuntu) because there has been no activity for 60 days.] ** Changed in: plymouth (Ubuntu) Status: Incomplete => Expired -- 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/1770475 Title: linux 4.15.0-21-generic messes up plymouth and no logo on luks password prompt Status in kubuntu-default-settings package in Ubuntu: Expired Status in kubuntu-settings package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in plymouth package in Ubuntu: Expired Bug description: Old problem with 4.15.0-20-generic: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768647 New problem with 4.15.0-21-generic: installing packages as specified in mentioned bug, the kde logo does not display properly at password prompt for luks. See attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-default-settings/+bug/1770475/+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 1770475] Re: linux 4.15.0-21-generic messes up plymouth and no logo on luks password prompt
[Expired for kubuntu-settings (Ubuntu) because there has been no activity for 60 days.] ** Changed in: kubuntu-settings (Ubuntu) Status: Incomplete => Expired -- 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/1770475 Title: linux 4.15.0-21-generic messes up plymouth and no logo on luks password prompt Status in kubuntu-default-settings package in Ubuntu: Expired Status in kubuntu-settings package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in plymouth package in Ubuntu: Expired Bug description: Old problem with 4.15.0-20-generic: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768647 New problem with 4.15.0-21-generic: installing packages as specified in mentioned bug, the kde logo does not display properly at password prompt for luks. See attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-default-settings/+bug/1770475/+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 1770475] Re: linux 4.15.0-21-generic messes up plymouth and no logo on luks password prompt
[Expired for kubuntu-default-settings (Ubuntu) because there has been no activity for 60 days.] ** Changed in: kubuntu-default-settings (Ubuntu) Status: Incomplete => Expired -- 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/1770475 Title: linux 4.15.0-21-generic messes up plymouth and no logo on luks password prompt Status in kubuntu-default-settings package in Ubuntu: Expired Status in kubuntu-settings package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in plymouth package in Ubuntu: Expired Bug description: Old problem with 4.15.0-20-generic: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768647 New problem with 4.15.0-21-generic: installing packages as specified in mentioned bug, the kde logo does not display properly at password prompt for luks. See attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-default-settings/+bug/1770475/+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 1780250] Re: package linux-modules-4.15.0-24-generic 4.15.0-24.26~16.04.1 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-4.15.0-24-generi
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1780250 Title: package linux-modules-4.15.0-24-generic 4.15.0-24.26~16.04.1 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux- modules-4.15.0-24-generic.list-new': Operation not permitted Status in linux package in Ubuntu: Expired Bug description: This bug came up after an update and restart. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-modules-4.15.0-24-generic 4.15.0-24.26~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon Jul 2 09:38:36 2018 Dependencies: DpkgHistoryLog: Start-Date: 2018-07-02 09:38:34 Commandline: aptdaemon role='role-commit-packages' sender=':1.317' Install: linux-headers-4.15.0-24:amd64 (4.15.0-24.26~16.04.1, automatic), linux-headers-4.15.0-24-generic:amd64 (4.15.0-24.26~16.04.1, automatic), linux-modules-extra-4.15.0-24-generic:amd64 (4.15.0-24.26~16.04.1, automatic), linux-modules-4.15.0-24-generic:amd64 (4.15.0-24.26~16.04.1, automatic), linux-image-4.15.0-24-generic:amd64 (4.15.0-24.26~16.04.1, automatic) Upgrade: linux-libc-dev:amd64 (4.4.0-128.154, 4.4.0-130.156), linux-image-generic-hwe-16.04:amd64 (4.13.0.45.64, 4.15.0.24.46), linux-signed-generic-hwe-16.04:amd64 (4.13.0.45.64, 4.15.0.24.46), linux-generic-hwe-16.04:amd64 (4.13.0.45.64, 4.15.0.24.46), linux-signed-image-generic-hwe-16.04:amd64 (4.13.0.45.64, 4.15.0.24.46), linux-headers-generic-hwe-16.04:amd64 (4.13.0.45.64, 4.15.0.24.46) DpkgTerminalLog: Preparing to unpack .../linux-modules-4.15.0-24-generic_4.15.0-24.26~16.04.1_amd64.deb ... Unpacking linux-modules-4.15.0-24-generic (4.15.0-24.26~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/linux-modules-4.15.0-24-generic_4.15.0-24.26~16.04.1_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-4.15.0-24-generic.list-new': Operation not permitted DuplicateSignature: package:linux-modules-4.15.0-24-generic:4.15.0-24.26~16.04.1 Unpacking linux-modules-4.15.0-24-generic (4.15.0-24.26~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/linux-modules-4.15.0-24-generic_4.15.0-24.26~16.04.1_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-4.15.0-24-generic.list-new': Operation not permitted ErrorMessage: unable to create new file '/var/lib/dpkg/info/linux-modules-4.15.0-24-generic.list-new': Operation not permitted InstallationDate: Installed on 2018-03-25 (101 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: linux-hwe Title: package linux-modules-4.15.0-24-generic 4.15.0-24.26~16.04.1 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-4.15.0-24-generic.list-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780250/+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 1553669] Re: Annoying "call from" message when connecting Bose devices
I seems that HSP/HFP doesn't work at all on 18.04. I've tried a variety of different Pulseaudio modules/settings, and also ofono. @vanvugt do you know if a different issue tracks that? -- 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/1553669 Title: Annoying "call from" message when connecting Bose devices Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each time I initially connect to listen to an audio or video, I hear an annoying "Call from" on my headset. My headset seems to think a connection to a phone call is taking place. This is annoying because the audio will start to play and after a little while the "call from" voice talks over the audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+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
