[Kernel-packages] [Bug 1798583] Re: the new Steam Controller driver breaks it on Steam

[Kai-Heng Feng]

kisak, in addition to the fix, do you think backport the hid-steam
driver to Bionic's v4.15 kernel useful to the users?

** Description changed:

- The new hid_steam driver in kernel 4.18 breaks the use of it within
- Steam.
+ ===SRU Justification===
+ [Impact]
+ New steam-hid driver breaks Unity games.
+ 
+ [Fix]
+ Quote from the commit message:
+ "With this commit, when a HID client starts, the input device is removed;
+ when the HID client ends the input device is recreated."
+ 
+ [Test]
+ A guy from Valve comfirms the backport works.
+ 
+ [Regression Potential]
+ Low. This fix is specific to hid-steam, which is a new driver introduced
+ in v4.18.
+ 
+ ===Original Bug Report===
+ The new hid_steam driver in kernel 4.18 breaks the use of it within Steam.
  
  Games either:
  - Crash
  - Don't detect it at all
  - Only pick it up as player 2
  
  To get it working as normal, it needs blacklisting currently.
  
  See here: https://www.gamingonlinux.com/articles/the-steam-controller-
  on-ubuntu-1810-and-other-distributions-using-linux-kernel-418-needs-
  quick-a-fix.12775
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC2:  liam   2492 F pulseaudio
-  /dev/snd/controlC0:  liam   2492 F pulseaudio
-  /dev/snd/controlC1:  liam   2492 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  liam   2492 F pulseaudio
+  /dev/snd/controlC0:  liam   2492 F pulseaudio
+  /dev/snd/controlC1:  liam   2492 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 18 12:49:44 2018
  InstallationDate: Installed on 2017-10-18 (364 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  IwConfig:
-  lono wireless extensions.
-  
-  enp5s0no wireless extensions.
-  
-  eno1  no wireless extensions.
+  lono wireless extensions.
+ 
+  enp5s0no wireless extensions.
+ 
+  eno1  no wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2a8676f3-0045-4e66-9cd1-186ffc6a8c2a ro quiet splash vt.handoff=1
  RelatedPackageVersions:
-  linux-restricted-modules-4.18.0-10-generic N/A
-  linux-backports-modules-4.18.0-10-generic  N/A
-  linux-firmware 1.175
+  linux-restricted-modules-4.18.0-10-generic N/A
+  linux-backports-modules-4.18.0-10-generic  N/A
+  linux-firmware 1.175
  RfKill:
-  
+ 
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago)
  dmi.bios.date: 08/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1901
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH X99
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: PCS
  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.:bvr1901:bd08/10/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

-- 
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/1798583

Title:
  the new Steam Controller driver breaks it on Steam

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  New steam-hid driver breaks Unity games.

  [Fix]
  Quote from the commit message:
  "With this commit, when a HID client starts, the input device is removed;
  when the HID client ends the input device is recreated."

  [Test]
  A guy from Valve comfirms the backport works.

  [Regression Potential]
  Low. This fix is specific to hid-steam, which is a new driver introduced
  in v4.18.

  ===Original Bug Report===
  The new hid_steam driver in kernel 4.18 breaks the use of it within Steam.

  Games either:
  - Crash
  - Don't detect it at all
  - Only pick it up as player 2

  To get it working as normal, it needs blacklisting currently.

  See here: https://www.gamingonlinux.com/articles/the-steam-controller-
  on-ubuntu-1810-and-other-distributions-using-linux-kernel-418-needs-
  quick-a-fix.12775

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4

[Kernel-packages] [Bug 1806663] Re: linux-oem: 4.15.0-1030.35 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Released

** 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
  -- swm properties --
  kernel-stable-master-bug: 1806659
- phase: Packaging
- phase-changed: Thursday, 06. December 2018 15:06 UTC
+ phase: Uploaded
+ phase-changed: Saturday, 08. December 2018 05:03 UTC
  reason:
-   prepare-package: Package not yet uploaded
-   prepare-package-meta: Package not yet uploaded
-   prepare-package-signed: Package not yet uploaded
+   promote-to-proposed: Builds not complete

-- 
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/1806663

Title:
  linux-oem: 4.15.0-1030.35 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806659
  phase: Uploaded
  phase-changed: Saturday, 08. December 2018 05:03 UTC
  reason:
promote-to-proposed: Builds not complete

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806663/+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 1806850] Re: Fix Terminus USB hub that may breaks connected USB devices after S3

[AceLan Kao]

** Also affects: linux-oem (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1806850

Title:
  Fix Terminus USB hub that may breaks connected USB devices after S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  New

Bug description:
  [Impact]
  USB devices connected to Terminus USB hub stop working after S3.

  [Fix]
  The Terminus hub seems to have a rather slow reset command, so we need to 
wait for extra time before doing any further action.

  [Test]
  After applying the fix, USB devices connected to the HUB no longer stop 
functioning after S3.

  [Regression Potential]
  Low. Although the fix affects all devices connect to the HUB, it has no 
functional change other than imposes longer delay time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806850/+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 1788807] Re: Bluetooth device not detected after resume from suspend [Qualcomm Atheros QCA9565]

[Launchpad Bug Tracker]

[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Expired

-- 
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/1788807

Title:
  Bluetooth device not detected after resume from suspend [Qualcomm
  Atheros QCA9565]

Status in bluez package in Ubuntu:
  Expired
Status in gnome-bluetooth package in Ubuntu:
  Expired

Bug description:
  When I suspend my laptop, it often happens that the bluetooth stops
  working. From gnome settings it is shown like if I had no bluetooth
  device at all.

  $ lspci -nnk | grep -iA3 net; lsusb; rfkill list; uname -r; dmesg | egrep -i 
'blue|firm'
  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter [168c:0036] (rev 01)
Subsystem: AzureWave QCA9565 / AR9565 Wireless Network Adapter 
[1a3b:2130]
Kernel driver in use: ath9k
Kernel modules: ath9k
  04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI 
Express Card Reader [10ec:5287] (rev 01)
  --
  04:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12)
Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit 
Ethernet Controller [1043:200f]
Kernel driver in use: r8169
Kernel modules: r8169
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. 
  Bus 001 Device 006: ID 13d3:3408 IMC Networks 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  4.15.0-32-generic
  [0.024000] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.048030] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [2.758768] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS
  [   35.407491] Bluetooth: Core ver 2.22
  [   35.407504] Bluetooth: HCI device and connection manager initialized
  [   35.407506] Bluetooth: HCI socket layer initialized
  [   35.407507] Bluetooth: L2CAP socket layer initialized
  [   35.407510] Bluetooth: SCO socket layer initialized
  [   53.501780] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   53.501780] Bluetooth: BNEP filters: protocol multicast
  [   53.501783] Bluetooth: BNEP socket layer initialized
  [   87.220137] Bluetooth: RFCOMM TTY layer initialized
  [   87.220143] Bluetooth: RFCOMM socket layer initialized
  [   87.220149] Bluetooth: RFCOMM ver 1.11
  [ 1675.503865] usb 1-5: device firmware changed
  [ 1681.095543] Bluetooth: Can't get version to change to load ram patch err
  [ 1681.095546] Bluetooth: Loading patch file failed
  [ 4105.994687] audit: type=1107 audit(1534926184.213:339): pid=1258 uid=105 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name="org.bluez" pid=10248 
label="snap.signal-desktop.signal-desktop" peer_pid=1314 peer_label="unconfined"


  Trying to use bluetooth from bluetoothctl
  $ bluetoothctl
  Agent registered
  [bluetooth]# scan on
  No default controller available

  
  Trying to restart the bluetooth service doesn't produce any effect:
  $ sudo service bluetooth restart

  
  Getting bluetooth service status:
  $ sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Fri 2018-08-24 11:23:17 EEST; 1min 35s ago
   Docs: man:bluetoothd(8)
   Main PID: 24999 (bluetoothd)
 Status: "Running"
  Tasks: 1 (limit: 4915)
 CGroup: /system.slice/bluetooth.service
 └─24999 /usr/lib/bluetooth/bluetoothd

  elo 24 11:23:17 fabio-X550JK systemd[1]: Stopping Bluetooth service...
  elo 24 11:23:17 fabio-X550JK systemd[1]: Stopped Bluetooth service.
  elo 24 11:23:17 fabio-X550JK systemd[1]: Starting Bluetooth service...
  elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth daemon 5.48
  elo 24 11:23:17 fabio-X550JK systemd[1]: Started Bluetooth service.
  elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Starting SDP server
  elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth management 
interface 1
  lines 1-17/17 (END)

  
  Reloading the driver:
  $ sudo modprobe -r btusb; sudo modprobe btusb;
  $ sudo service bluetooth restart

  
  None of these attempts could solve the issue.


  What happens?
  Bluetooth is working, I suspend my laptop, I resume my laptop -> Bluetooth 
controller is no longer recognised and bluetooth service cannot be used anymore.

  What would you expect?
  Bluetooth controller to be recognised and working also after resume.

  ProblemType: Bug
  DistroRelease: 

[Kernel-packages] [Bug 1788807] Re: Bluetooth device not detected after resume from suspend [Qualcomm Atheros QCA9565]

[Launchpad Bug Tracker]

[Expired for gnome-bluetooth (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: gnome-bluetooth (Ubuntu)
   Status: Incomplete => Expired

-- 
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/1788807

Title:
  Bluetooth device not detected after resume from suspend [Qualcomm
  Atheros QCA9565]

Status in bluez package in Ubuntu:
  Expired
Status in gnome-bluetooth package in Ubuntu:
  Expired

Bug description:
  When I suspend my laptop, it often happens that the bluetooth stops
  working. From gnome settings it is shown like if I had no bluetooth
  device at all.

  $ lspci -nnk | grep -iA3 net; lsusb; rfkill list; uname -r; dmesg | egrep -i 
'blue|firm'
  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter [168c:0036] (rev 01)
Subsystem: AzureWave QCA9565 / AR9565 Wireless Network Adapter 
[1a3b:2130]
Kernel driver in use: ath9k
Kernel modules: ath9k
  04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI 
Express Card Reader [10ec:5287] (rev 01)
  --
  04:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12)
Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit 
Ethernet Controller [1043:200f]
Kernel driver in use: r8169
Kernel modules: r8169
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. 
  Bus 001 Device 006: ID 13d3:3408 IMC Networks 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  4.15.0-32-generic
  [0.024000] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.048030] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [2.758768] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS
  [   35.407491] Bluetooth: Core ver 2.22
  [   35.407504] Bluetooth: HCI device and connection manager initialized
  [   35.407506] Bluetooth: HCI socket layer initialized
  [   35.407507] Bluetooth: L2CAP socket layer initialized
  [   35.407510] Bluetooth: SCO socket layer initialized
  [   53.501780] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   53.501780] Bluetooth: BNEP filters: protocol multicast
  [   53.501783] Bluetooth: BNEP socket layer initialized
  [   87.220137] Bluetooth: RFCOMM TTY layer initialized
  [   87.220143] Bluetooth: RFCOMM socket layer initialized
  [   87.220149] Bluetooth: RFCOMM ver 1.11
  [ 1675.503865] usb 1-5: device firmware changed
  [ 1681.095543] Bluetooth: Can't get version to change to load ram patch err
  [ 1681.095546] Bluetooth: Loading patch file failed
  [ 4105.994687] audit: type=1107 audit(1534926184.213:339): pid=1258 uid=105 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name="org.bluez" pid=10248 
label="snap.signal-desktop.signal-desktop" peer_pid=1314 peer_label="unconfined"


  Trying to use bluetooth from bluetoothctl
  $ bluetoothctl
  Agent registered
  [bluetooth]# scan on
  No default controller available

  
  Trying to restart the bluetooth service doesn't produce any effect:
  $ sudo service bluetooth restart

  
  Getting bluetooth service status:
  $ sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Fri 2018-08-24 11:23:17 EEST; 1min 35s ago
   Docs: man:bluetoothd(8)
   Main PID: 24999 (bluetoothd)
 Status: "Running"
  Tasks: 1 (limit: 4915)
 CGroup: /system.slice/bluetooth.service
 └─24999 /usr/lib/bluetooth/bluetoothd

  elo 24 11:23:17 fabio-X550JK systemd[1]: Stopping Bluetooth service...
  elo 24 11:23:17 fabio-X550JK systemd[1]: Stopped Bluetooth service.
  elo 24 11:23:17 fabio-X550JK systemd[1]: Starting Bluetooth service...
  elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth daemon 5.48
  elo 24 11:23:17 fabio-X550JK systemd[1]: Started Bluetooth service.
  elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Starting SDP server
  elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth management 
interface 1
  lines 1-17/17 (END)

  
  Reloading the driver:
  $ sudo modprobe -r btusb; sudo modprobe btusb;
  $ sudo service bluetooth restart

  
  None of these attempts could solve the issue.


  What happens?
  Bluetooth is working, I suspend my laptop, I resume my laptop -> Bluetooth 
controller is no longer recognised and bluetooth service cannot be used anymore.

  What would you expect?
  Bluetooth controller to be recognised and working also after resume.

  ProblemType: B

[Kernel-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work

[AceLan Kao]

** Also affects: linux-oem (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1806532

Title:
  The line-out on the Dell Dock station can't work

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New

Bug description:
  [Impact]
  On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback
  devices, one is headphone, the other is line-out, but there is no UCM for
  these docks yet, so the pluseaudio only can handle the 1st playback device,
  need us to add the UCM for them, before adding UCM, we need to set the
  longname of the sound card in the linux kernel.

  [Fix]
  Cherry-picked 3 upstream patches, these patches add the longname of the sound
  card for the dock station.

  
  [Test Case]
  Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from
  UI, and play sound via these devices

  [Regression Potential]
  Very low, these patches come from upstream, and the change is only specific
  to WD15 and WD19 dock station.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806532/+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 1753198] Re: package libnvidia-gl-390 (not installed) failed to install/upgrade: new libnvidia-gl-390:amd64 package pre-installation script subprocess returned error exit status

[amarnadh]

yes this bug is still there

-- 
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/1753198

Title:
  package libnvidia-gl-390 (not installed) failed to install/upgrade:
  new libnvidia-gl-390:amd64 package pre-installation script subprocess
  returned error exit status 2

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released

Bug description:
  The 340 driver also failed.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libnvidia-gl-390 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sat Mar  3 22:44:50 2018
  ErrorMessage: new libnvidia-gl-390:amd64 package pre-installation script 
subprocess returned error exit status 2
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu2
  SourcePackage: nvidia-graphics-drivers-390
  Title: package libnvidia-gl-390 (not installed) failed to install/upgrade: 
new libnvidia-gl-390:amd64 package pre-installation script subprocess returned 
error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1753198/+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 1806663] Re: linux-oem: 4.15.0-1030.35 -proposed tracker

[Brad Figg]

** 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
  -- swm properties --
  kernel-stable-master-bug: 1806659
  phase: Packaging
  phase-changed: Thursday, 06. December 2018 15:06 UTC
  reason:
-   prepare-package: Version not specified
+   prepare-package: Package not yet uploaded
+   prepare-package-meta: Package not yet uploaded
+   prepare-package-signed: Package not yet uploaded

-- 
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/1806663

Title:
  linux-oem: 4.15.0-1030.35 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806659
  phase: Packaging
  phase-changed: Thursday, 06. December 2018 15:06 UTC
  reason:
prepare-package: Package not yet uploaded
prepare-package-meta: Package not yet uploaded
prepare-package-signed: Package not yet uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806663/+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 1806663] Re: linux-oem: 4.15.0-1030.35 -proposed tracker

[AceLan Kao]

** Summary changed:

- linux-oem:  -proposed tracker
+ linux-oem: 4.15.0-1030.35 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => AceLan Kao 
(acelankao)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => AceLan Kao 
(acelankao)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => AceLan Kao 
(acelankao)

-- 
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/1806663

Title:
  linux-oem: 4.15.0-1030.35 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1806659
  phase: Packaging
  phase-changed: Thursday, 06. December 2018 15:06 UTC
  reason:
prepare-package: Version not specified

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806663/+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 1806667] Re: linux-kvm: 4.15.0-1028.28 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Fix Released

** 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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 23:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Testing in progress
regression-testing: Testing in progress
security-signoff: Waiting for signoff
verification-testing: Testing in progress

-- 
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/1806667

Title:
  linux-kvm: 4.15.0-1028.28 -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:
  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-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 23:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress
security-signoff: Waiting for signoff
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806667/+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 1807469] Re: Bionic update: upstream stable patchset 2018-12-07

[Kamal Mostafa]

** Changed in: linux (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    upstream stable patchset 2018-12-07 (ported from v4.14.53 and v4.17.4)
+    from git://git.kernel.org/
  
-upstream stable patchset 2018-12-07
-from git://git.kernel.org/
+ x86/e820: put !E820_TYPE_RAM regions into memblock.reserved
+ dm: use bio_split() when splitting out the already processed bio
+ dm: rename 'bio' member of dm_io structure to 'orig_bio'
+ dm: ensure bio submission follows a depth-first tree walk
+ kasan: depend on CONFIG_SLUB_DEBUG
+ i2c: gpio: initialize SCL to HIGH again
+ ALSA: hda - Force to link down at runtime suspend on ATI/AMD HDMI
+ Input: silead - add MSSL0002 ACPI HID
+ Input: silead - add Chuwi Hi8 support
+ media: rc: mce_kbd decoder: fix stuck keys
+ remoteproc: Prevent incorrect rproc state on xfer mem ownership failure
+ mfd: twl-core: Fix clock initialization
+ f2fs: don't use GFP_ZERO for page caches
+ libnvdimm, pmem: Unconditionally deep flush on *sync
+ scsi: qla2xxx: Spinlock recursion in qla_target
+ scsi: scsi_debug: Fix memory leak on module unload
+ locking/rwsem: Fix up_read_non_owner() warning with DEBUG_RWSEMS
+ MIPS: pb44: Fix i2c-gpio GPIO descriptor table
+ pinctrl: armada-37xx: Fix spurious irq management
+ PCI: Account for all bridges on bus when distributing bus numbers
+ mtd: rawnand: mxc: set spare area size register explicitly
+ mtd: rawnand: fix return value check for bad block status
+ of: overlay: validate offset from property fixups
+ ARM64: dts: meson-gx: fix ATF reserved memory region
+ softirq: Reorder trace_softirqs_on to prevent lockdep splat
+ hwrng: core - Always drop the RNG in hwrng_unregister()
+ powerpc/e500mc: Set assembler machine type to e500mc
+ powerpc/64s: Set assembler machine type to POWER4
+ libnvdimm, pmem: Do not flush power-fail protected CPU caches
+ ASoC: mediatek: preallocate pages use platform device
+ PCI / PM: Do not clear state_saved for devices that remain suspended
+ mtd: spi-nor: intel-spi: Fix atomic sequence handling
+ spi-nor: intel-spi: Remove unused preopcodes field
+ hwmon: (k10temp) Add support for Stoney Ridge and Bristol Ridge CPUs
+ platform/chrome: cros_ec_lpc: do not try DMI match when ACPI device found
+ platform/chrome: cros_ec_lpc: Register the driver if ACPI entry is missing.
+ x86/platform/UV: Add kernel parameter to set memory block size
+ x86/platform/UV: Use new set memory block size function
+ dm thin: handle running out of data space vs concurrent discard
+ dm zoned: avoid triggering reclaim from inside dmz_map()
+ x86/efi: Fix efi_call_phys_epilog() with CONFIG_X86_5LEVEL=y
+ block: Fix cloning of requests with a special payload
+ block: Fix transfer when chunk sectors exceeds max
+ slub: fix failure when we delete and create a slab cache
+ ALSA: hda/realtek - Add a quirk for FSC ESPRIMO U9210
+ ALSA: hda/realtek - Fix pop noise on Lenovo P50 & co
+ ALSA: timer: Fix UBSAN warning at SNDRV_TIMER_IOCTL_NEXT_DEVICE ioctl
+ Input: elan_i2c_smbus - fix more potential stack buffer overflows
+ Input: xpad - fix GPD Win 2 controller name
+ udf: Detect incorrect directory size
+ xen: Remove unnecessary BUG_ON from __unbind_from_irq()
+ mm: fix devmem_is_allowed() for sub-page System RAM intersections
+ mm/ksm.c: ignore STABLE_FLAG of rmap_item->address in rmap_walk_ksm()
+ rbd: flush rbd_dev->watch_dwork after watch is unregistered
+ pwm: lpss: platform: Save/restore the ctrl register over a suspend/resume
+ Input: elan_i2c - add ELAN0618 (Lenovo v330 15IKB) ACPI ID
+ ACPI / LPSS: Add missing prv_offset setting for byt/cht PWM devices
+ NFSv4: Fix a typo in nfs41_sequence_process
+ NFSv4: Revert commit 5f83d86cf531d ("NFSv4.x: Fix wraparound issues..")
+ NFSv4: Fix possible 1-byte stack overflow in nfs_idmap_read_and_verify_message
+ nfsd: restrict rd_maxcount to svc_max_payload in nfsd_encode_readdir
+ media: dvb_frontend: fix locking issues at dvb_frontend_get_eve

[Kernel-packages] [Bug 1807469] [NEW] Bionic update: upstream stable patchset 2018-12-07

[Kamal Mostafa]

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   upstream stable patchset 2018-12-07
   from git://git.kernel.org/

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Status: New


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Bionic)
   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/1807469

Title:
  Bionic update: upstream stable patchset 2018-12-07

Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  New

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 upstream stable patchset 2018-12-07
 from git://git.kernel.org/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807469/+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 1806667] Re: linux-kvm: 4.15.0-1028.28 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-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 => In Progress

** 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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
- phase: Uploaded
- phase-changed: Friday, 07. December 2018 09:34 UTC
+ phase: Promoted to proposed
+ phase-changed: Friday, 07. December 2018 23:05 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Packages waiting in -proposed for mirror sync
+   automated-testing: Testing in progress
+   regression-testing: Testing in progress
+   security-signoff: Waiting for signoff
+   verification-testing: Testing in progress

-- 
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/1806667

Title:
  linux-kvm: 4.15.0-1028.28 -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 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-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 23:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing in progress
regression-testing: Testing in progress
security-signoff: Waiting for signoff
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806667/+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 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

[ALinuxUser]

Extra information - namely, the output of several relevant commands.

** Attachment added: "report"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+attachment/5220212/+files/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/1791427

Title:
  Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
  Carbon 6th

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04.1

  Terminology in case we use different terms:
  touchpad - just the rectangular touch-sensitive surface below the keyboard 
(xinput lists it as Synaptics TM3288-011)
  trackpoint - the red thingy built into the keyboard + 3 physical buttons 
below the keyboard (trackpoint and buttons are integrated together; listed in 
xinput as TPPS/2 Elan TrackPoint)

  On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which
  enables proper S3 deep sleep state - users no longer have to patch
  DSDT tables to get it. It can be enabled in the BIOS settings. In X1
  carbon 6th generation models that have NFC, when laptop wakes from
  suspend by opening the lid, in most cases both touchpad and trackpoint
  stop working completely. They are also no longer listed when running
  xinput command. Sometimes just one of them stops working, usually the
  trackpoint. In some rare cases it is possible to bring them back by
  using these commands:

  echo -n none > /sys/devices/platform/i8042/serio1/drvctl
  echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl
  rmmod psmouse
  modprobe psmouse

  These worked properly when waking up from S2Idle sleep state (had
  these in a script that runs after waking the machine from suspend),
  but with S3 deep sleep these rarely work and the only way to bring
  back touchpad and/or trackpoint is turning off the machine and turning
  it on (restart does not help).

  I could not find any pattern that would show when the input devices
  stop working or start working again using the commands mentioned
  above. It's completely random from my perspective.

  This is happening on the standard issue 4.15.0-33-generic kernel that
  shipped with my Ubuntu 18.04 (with updates), as well as with newer
  mainline kernels, such as the newest point versions of 4.17, 4.18 and
  4.19 RC2.

  This happens regardless of whether "blacklist i2c_i801" is commented
  out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of
  whether "psmouse.synaptics_intertouch=1" is passed as grub parameter.
  Presence of TLP does not make it better, nor worse.

  It appears that non-NFC models are not affected. I know at least one
  Arch Linux user who has the exact same model, but without this issue.
  I'm using synaptics driver (no libinput installed), he uses libinput
  and doesn't have synaptics, if that information is of any use.
  Libinput does not seem to help.

  This forum thread also has more details from users who updated their
  BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux-
  Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka-
  Suspend-to/td-p/3998182/page/27

  Another related thread:
  https://bbs.archlinux.org/viewtopic.php?id=236367

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   maciej 2651 F...m pulseaudio
   /dev/snd/controlC0:  maciej 2651 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Sep  8 13:45:43 2018
  HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e
  InstallationDate: Installed on 2018-07-21 (49 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56b2 IMC Networks 
   Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless 
optical mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KH006KPB
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET55W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KH006KPB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.t

[Kernel-packages] [Bug 1803960] Re: 4.18.0 kernels hang system randomly

[TJ]

Five days running on 4.16.18-041618-lowlatency and had no problems so
I'm going to try the mainline build of v4.17.19.

-- 
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/1803960

Title:
  4.18.0 kernels hang system randomly

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Cosmic:
  Triaged

Bug description:
  I've been using 18.04 on an Asus T300CHI without issue until I decided
  to switch to the v4.18 kernels from 18.10 via linux-image-lowlatency-
  hwe-18.04-edge.

  Since then the system randomly but regularly completely hangs. Only a
  hard power-off resolves it.

  Frustratingly there are never any clues in the kernel logs so it is
  very difficult to point to anything that might cause it; there is
  never any obvious pattern in the workload, the user interaction, or
  state of the PC when the hang occurs.

  A week ago I switched to the Ubuntu mainline v4.19 builds and that
  resolved the issue.

  I was reminded of it again today when it hung a few minutes ago. After
  the reboot I checked the previous boot log and realised the PC had
  accidentally been booted with the default v4.18 kernel rather than
  v4.19.

  I don't think this report can be debugged but it is worth having a
  tracking bug in case other people experience the same issue with
  v4.18.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803960/+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 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

[ALinuxUser]

My dmesg output immediately after resuming from suspend. I had enabled
S3 in BIOS and consequently the touchpad was not working. However, I had
a USB mouse on the go - for, otherwise, I would have trouble using the
computer in that state.

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+attachment/5220211/+files/dmesg.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/1791427

Title:
  Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
  Carbon 6th

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04.1

  Terminology in case we use different terms:
  touchpad - just the rectangular touch-sensitive surface below the keyboard 
(xinput lists it as Synaptics TM3288-011)
  trackpoint - the red thingy built into the keyboard + 3 physical buttons 
below the keyboard (trackpoint and buttons are integrated together; listed in 
xinput as TPPS/2 Elan TrackPoint)

  On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which
  enables proper S3 deep sleep state - users no longer have to patch
  DSDT tables to get it. It can be enabled in the BIOS settings. In X1
  carbon 6th generation models that have NFC, when laptop wakes from
  suspend by opening the lid, in most cases both touchpad and trackpoint
  stop working completely. They are also no longer listed when running
  xinput command. Sometimes just one of them stops working, usually the
  trackpoint. In some rare cases it is possible to bring them back by
  using these commands:

  echo -n none > /sys/devices/platform/i8042/serio1/drvctl
  echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl
  rmmod psmouse
  modprobe psmouse

  These worked properly when waking up from S2Idle sleep state (had
  these in a script that runs after waking the machine from suspend),
  but with S3 deep sleep these rarely work and the only way to bring
  back touchpad and/or trackpoint is turning off the machine and turning
  it on (restart does not help).

  I could not find any pattern that would show when the input devices
  stop working or start working again using the commands mentioned
  above. It's completely random from my perspective.

  This is happening on the standard issue 4.15.0-33-generic kernel that
  shipped with my Ubuntu 18.04 (with updates), as well as with newer
  mainline kernels, such as the newest point versions of 4.17, 4.18 and
  4.19 RC2.

  This happens regardless of whether "blacklist i2c_i801" is commented
  out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of
  whether "psmouse.synaptics_intertouch=1" is passed as grub parameter.
  Presence of TLP does not make it better, nor worse.

  It appears that non-NFC models are not affected. I know at least one
  Arch Linux user who has the exact same model, but without this issue.
  I'm using synaptics driver (no libinput installed), he uses libinput
  and doesn't have synaptics, if that information is of any use.
  Libinput does not seem to help.

  This forum thread also has more details from users who updated their
  BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux-
  Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka-
  Suspend-to/td-p/3998182/page/27

  Another related thread:
  https://bbs.archlinux.org/viewtopic.php?id=236367

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   maciej 2651 F...m pulseaudio
   /dev/snd/controlC0:  maciej 2651 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Sep  8 13:45:43 2018
  HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e
  InstallationDate: Installed on 2018-07-21 (49 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56b2 IMC Networks 
   Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless 
optical mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KH006KPB
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.

[Kernel-packages] [Bug 1806664] Re: linux-aws: 4.15.0-1031.33 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Incomplete

** 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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 21:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Testing in progress
+   automated-testing: Testing FAILED
regression-testing: Testing in progress
security-signoff: Waiting for signoff
snap-release-to-beta: Snap not in 18/beta channel
snap-release-to-edge: Snap not in 18/edge channel
verification-testing: Testing in progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1806664

Title:
  linux-aws: 4.15.0-1031.33 -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:
  Confirmed
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-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 21:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
regression-testing: Testing in progress
security-signoff: Waiting for signoff
snap-release-to-beta: Snap not in 18/beta channel
snap-release-to-edge: Snap not in 18/edge channel
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806664/+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 1807393] Re: nvme - Polling on timeout

[Guilherme G. Piccoli]

Patch sent to Ubuntu kernel mailing-list:
https://lists.ubuntu.com/archives/kernel-team/2018-December/097208.html

** Changed in: linux (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu Xenial)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1807393

Title:
  nvme - Polling on timeout

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  [Impact]
  * NVMe controllers potentially could miss to send an interrupt, specially
  due to bugs in virtual devices(which are common those days - qemu has its
  own NVMe virtual device, so does AWS). This would be a difficult to
  debug situation, because NVMe driver only reports the request timeout,
  not the reason.

  * The upstream patch proposed to SRU here here, 7776db1ccc12
  ("NVMe/pci: Poll CQ on timeout") was designed to provide more information
  in these cases, by pro-actively polling the CQEs on request timeouts, to
  check if the specific request was completed and some issue (probably a
  missed interrupt) prevented the driver to notice, or if the request really
  wasn't completed, which indicates more severe issues.

  * Although quite useful for debugging, this patch could help to mitigate
  issues in cloud environments like AWS, in case we may have jitter in
  request completion and the i/o timeout was set to low values, or even
  in case of atypical bugs in the virtual NVMe controller. With this patch,
  if polling succeeds the NVMe driver will continue working instead of
  trying a reset controller procedure, which may lead to fails in the 
  rootfs - refer to https://launchpad.net/bugs/1788035.

  
  [Test Case]

  * It's a bit tricky to artificially create a situation of missed interrupt;
  one idea was to implement a small hack in the NVMe qemu virtual device
  that given a trigger in guest kernel, will induce the virtual device to
  skip an interrupt. The hack patch is present in comment #1 below.

  * To trigger such hack from guest kernel, all is needed is to issue a
  raw admin command from nvme-cli: "nvme admin-passthru -o 0xff /dev/nvme0"
  After that, just perform some I/Os to see one of them aborting - one could
  use dd for this goal, like "dd if=/dev/zero of=/dev/nvme0n1 count=5".

  
  [Regression Potential]

  * There are no clear risks in adding such polling mechanism to the NVMe 
driver; one bad thing that was neverreported but could happen with this patch 
is the device could be in a bad state IRQ-wise that a reset would fix, but
  the patch could cause all requests to be completed via polling, which
  prevents the adapter reset. This is however a very hypothetical situation,
  which would also happen in the mainline kernel (since it has the patch).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807393/+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 1806667] Re: linux-kvm: 4.15.0-1028.28 -proposed tracker

[Brad Figg]

** 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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Uploaded
  phase-changed: Friday, 07. December 2018 09:34 UTC
  reason:
-   promote-to-proposed: Ready for review
+   promote-to-proposed: Packages waiting in -proposed for mirror sync

-- 
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/1806667

Title:
  linux-kvm: 4.15.0-1028.28 -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:
  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 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-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Uploaded
  phase-changed: Friday, 07. December 2018 09:34 UTC
  reason:
promote-to-proposed: Packages waiting in -proposed for mirror sync

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806667/+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 1806664] Re: linux-aws: 4.15.0-1031.33 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-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 => In Progress

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-edge
   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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
- phase: Uploaded
- phase-changed: Friday, 07. December 2018 10:08 UTC
+ phase: Promoted to proposed
+ phase-changed: Friday, 07. December 2018 21:32 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Packages waiting in -proposed for mirror sync
+   automated-testing: Testing in progress
+   regression-testing: Testing in progress
+   security-signoff: Waiting for signoff
+   snap-release-to-beta: Snap not in 18/beta channel
+   snap-release-to-edge: Snap not in 18/edge channel
+   verification-testing: Testing in progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1806664

Title:
  linux-aws: 4.15.0-1031.33 -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 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:
  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-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 21:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing in progress
regression-testing: Testing in progress
security-signoff: Waiting for signoff
snap-release-to-beta: Snap not in 18/beta channel
snap-release-to-edge: Snap not in 18/edge channel
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806664/+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 1773363] Missing required logs.

[Ubuntu Kernel Bot]

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 1773363

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

** Changed in: linux (Ubuntu Bionic)
   Status: New => Incomplete

** Changed in: linux (Ubuntu Cosmic)
   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/1773363

Title:
  glibc tst-preadvwritev2 and tst-preadvwritev64v2 fail with Linux 4.16+

Status in GLibC:
  Fix Released
Status in glibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in glibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Incomplete
Status in glibc source package in Cosmic:
  New
Status in linux source package in Cosmic:
  Incomplete

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-bootstrap/cosmic/amd64/g/glibc/20180524_160944_1abf8@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-bootstrap/cosmic/ppc64el/g/glibc/20180524_155206_1abf8@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1773363/+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 1806667] Re: linux-kvm: 4.15.0-1028.28 -proposed tracker

[Steve Langasek]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve 
Langasek (vorlon)

-- 
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/1806667

Title:
  linux-kvm: 4.15.0-1028.28 -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:
  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 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-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Uploaded
  phase-changed: Friday, 07. December 2018 09:34 UTC
  reason:
promote-to-proposed: Ready for review

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806667/+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 1773363] Re: glibc tst-preadvwritev2 and tst-preadvwritev64v2 fail with Linux 4.16+

[Seth Forshee]

Kernel patch:

https://lore.kernel.org/patchwork/patch/995145/

Seems to not be getting any attention at all upstream however.

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Seth Forshee (sforshee)

-- 
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/1773363

Title:
  glibc tst-preadvwritev2 and tst-preadvwritev64v2 fail with Linux 4.16+

Status in GLibC:
  Fix Released
Status in glibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in glibc source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in glibc source package in Cosmic:
  New
Status in linux source package in Cosmic:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-bootstrap/cosmic/amd64/g/glibc/20180524_160944_1abf8@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-bootstrap/cosmic/ppc64el/g/glibc/20180524_155206_1abf8@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1773363/+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 1806659] Re: linux: 4.15.0-43.46 -proposed tracker

[Steve Beattie]

** 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/1806659

Title:
  linux: 4.15.0-43.46 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow 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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1806670 (linux-azure), bug 1806671 (linux-aws-hwe), bug 
1806672 (linux-azure), bug 1806673 (linux-gcp), bug 1806674 (linux-hwe), bug 
1806675 (linux-hwe-edge)
  derivatives: bug 1806661 (linux-raspi2), bug 1806663 (linux-oem), bug 1806664 
(linux-aws), bug 1806665 (linux-azure), bug 180 (linux-gcp), bug 1806667 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 12:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
certification-testing: Testing in progress
regression-testing: Testing in progress
security-signoff: Waiting for signoff
snap-release-to-beta: Snap not in 18/beta channel
snap-release-to-edge: Snap not in 18/edge channel
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806659/+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 1806665] Re: linux-azure: 4.15.0-1036.38 -proposed tracker

[Steve Beattie]

** 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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1806665

Title:
  linux-azure: 4.15.0-1036.38 -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 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:
  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 stakeholder-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-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 11:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
regression-testing: Testing in progress
security-signoff: Waiting for signoff
snap-release-to-beta: Snap not in 18/beta channel
snap-release-to-edge: Snap not in 18/edge channel
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806665/+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 1806666] Re: linux-gcp: 4.15.0-1026.27 -proposed tracker

[Steve Beattie]

** 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-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/180

Title:
  linux-gcp: 4.15.0-1026.27 -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 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:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 11:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
promote-to-updates: Nvidia GCP object not found -- 4.15.0-1026
regression-testing: Testing in progress
security-signoff: Waiting for signoff
snap-release-to-beta: Snap not in 18/beta channel
snap-release-to-edge: Snap not in 18/edge channel
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/180/+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 1806670] Re: linux-azure: 4.15.0-1036.38~14.04.2 -proposed tracker

[Steve Beattie]

** 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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1806670

Title:
  linux-azure: 4.15.0-1036.38~14.04.2 -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 stakeholder-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-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 11:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress
security-signoff: Waiting for signoff
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806670/+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 1806672] Re: linux-azure: 4.15.0-1036.38~16.04.1 -proposed tracker

[Steve Beattie]

** 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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1806672

Title:
  linux-azure: 4.15.0-1036.38~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:
  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 stakeholder-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-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 15:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress
security-signoff: Waiting for signoff
snap-release-to-beta: Snap not in beta channel
snap-release-to-edge: Snap not in edge channel
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806672/+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 1806664] Re: linux-aws: 4.15.0-1031.33 -proposed tracker

[Steve Langasek]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve 
Langasek (vorlon)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1806664

Title:
  linux-aws: 4.15.0-1031.33 -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:
  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 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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
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:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Uploaded
  phase-changed: Friday, 07. December 2018 10:08 UTC
  reason:
promote-to-proposed: Packages waiting in -proposed for mirror sync

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806664/+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 1802481] Re: cryptsetup waits for zvol /dev/zvol/rpool/swap with no zpool imported during boot. Timing problem?

[Richard Laager]

Try adding initramfs as an option in /etc/crypttab. That's the approach
I use when putting the whole pool on a LUKS device, and is necessary due
to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1612906

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802481

Title:
  cryptsetup waits for zvol /dev/zvol/rpool/swap with no zpool imported
  during boot. Timing problem?

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Hi,
  first of all: I don't know if it is a bug in cryptsetup-initramfs or 
zfs-initramfs or another one.

  The problem is that since my upgrade from bionic to cosmic the
  cryptsetup tries too early to setup my cryptswap device which is on a
  zvol.

cryptsetup: Waiting for encrypted source device /dev/zvol/rpool/swap...
 ALERT! encrypted source device /dev/zvol/rpool/swap does not exist, 
can't unlock cryptswap1.
...

  After timeout I find myself in a initramfs-shell (initramfs).
  When I do zpool list there is no zpool importet.
  After

zpool import -N rpool
^D

  the cryptsetup succeeds.
  Greetings,

 Lars

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: cryptsetup-initramfs 2:2.0.4-2ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov  9 10:01:19 2018
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.logrotate.d.apport: [modified]
  mtime.conffile..etc.default.apport: 2015-03-15T20:01:19.851334
  mtime.conffile..etc.logrotate.d.apport: 2018-05-18T08:58:12.902005

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1802481/+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 1806664] Re: linux-aws: 4.15.0-1031.33 -proposed tracker

[Brad Figg]

** 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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Uploaded
  phase-changed: Friday, 07. December 2018 10:08 UTC
  reason:
-   promote-to-proposed: Ready for review
+   promote-to-proposed: Packages waiting in -proposed for mirror sync

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1806664

Title:
  linux-aws: 4.15.0-1031.33 -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:
  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 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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
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:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Uploaded
  phase-changed: Friday, 07. December 2018 10:08 UTC
  reason:
promote-to-proposed: Packages waiting in -proposed for mirror sync

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806664/+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 1806673] Re: linux-gcp: 4.15.0-1026.27~16.04.1 -proposed tracker

[Brad Figg]

** 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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Uploaded
  phase-changed: Friday, 07. December 2018 15:37 UTC
  reason:
-   promote-to-proposed: Packages copied but not yet published to -proposed
-   promote-to-updates: Nvidia GCP object not found -- 4.15.0-1026
+   promote-to-proposed: Packages copies requested

-- 
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/1806673

Title:
  linux-gcp: 4.15.0-1026.27~16.04.1 -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:
  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 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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
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:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Uploaded
  phase-changed: Friday, 07. December 2018 15:37 UTC
  reason:
promote-to-proposed: Packages copies requested

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806673/+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 1807432] Re: /proc/diskstats does not rollup queue depth from partitions

[Albert Autin]

These are all the logs I have...

** 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/1807432

Title:
  /proc/diskstats does not rollup queue depth from partitions

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Tested in Ubuntu 18.04LTS and Ubuntu 18.10, with the same result. The
  queue size rollup works in Centos 7 though.

  root@vagrant:~# uname -a
  Linux vagrant 4.18.0-12-generic #13-Ubuntu SMP Wed Nov 14 15:17:05 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  root@vagrant:~# lsb_release -rd
  Description:Ubuntu 18.10
  Release:18.10

  root@vagrant:~# cat /proc/diskstats 
 7   0 loop0 5 0 16 0 0 0 0 0 0 0 0
 7   1 loop1 0 0 0 0 0 0 0 0 0 0 0
 7   2 loop2 0 0 0 0 0 0 0 0 0 0 0
 7   3 loop3 0 0 0 0 0 0 0 0 0 0 0
 7   4 loop4 0 0 0 0 0 0 0 0 0 0 0
 7   5 loop5 0 0 0 0 0 0 0 0 0 0 0
 7   6 loop6 0 0 0 0 0 0 0 0 0 0 0
 7   7 loop7 0 0 0 0 0 0 0 0 0 0 0
   259   0 nvme0n1 813340 0 10963704 274028 4075 44 1040576 46884 0 18012 
908472
   259   5 nvme0n1p1 203838 0 2749463 65696 986 0 252416 11696 13 14360 
218028
   259   6 nvme0n1p2 202672 0 2713358 67924 1015 0 259840 11696 20 14372 
220388
   259   7 nvme0n1p3 202961 0 2717301 70464 1034 0 264704 11652 19 14344 
226248
   259   8 nvme0n1p4 203216 0 2730974 69944 1028 0 263168 11840 16 14340 
224992
 8   0 sda 11622 783 612090 16416 6529 9730 607624 52912 0 7964 76940
 8   1 sda1 11543 783 607954 16408 4731 9730 607624 52844 0 7380 76304
   253   0 dm-0 12083 0 598666 25540 16198 0 613808 137252 0 7936 162808
   253   1 dm-1 186 0 8696 104 0 0 0 0 0 80 104

  We expect the queue depth of 'nvme0n1' to increase when the partitions
  it has increase, but this never happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807432/+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 1789227] Re: nvme devices namespace assigned to the wrong controller

[dann frazier]

No regression here (tested ubuntu-server daily on x86 VM)

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

** Tags removed: verification-needed
** Tags added: verification-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/1789227

Title:
  nvme devices namespace assigned to the wrong controller

Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == Impact ==

  During device discovery, when multipath is disabled, nvme multipath
  module will very likely think that the name space on one nvme
  controller belongs to the other controller.

  
  == Fix ==

  Commit a785dbccd95c37606c720580714f5a7a8b3255f1 upstream

  From: Keith Busch 

  When CONFIG_NVME_MULTIPATH is set, but we're not using nvme to multipath,
  namespaces with multiple paths were not creating unique names due to
  reusing the same instance number from the namespace's head.

  This patch fixes this by falling back to the non-multipath naming method
  when the parameter disabled using multipath.

  Reported-by: Mike Snitzer 
  Signed-off-by: Keith Busch 
  Reviewed-by: Christoph Hellwig 
  Signed-off-by: Jens Axboe 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1789227/+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 1789227] Re: nvme devices namespace assigned to the wrong controller

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-core-dev/debian-installer/bionic-proposed

-- 
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/1789227

Title:
  nvme devices namespace assigned to the wrong controller

Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == Impact ==

  During device discovery, when multipath is disabled, nvme multipath
  module will very likely think that the name space on one nvme
  controller belongs to the other controller.

  
  == Fix ==

  Commit a785dbccd95c37606c720580714f5a7a8b3255f1 upstream

  From: Keith Busch 

  When CONFIG_NVME_MULTIPATH is set, but we're not using nvme to multipath,
  namespaces with multiple paths were not creating unique names due to
  reusing the same instance number from the namespace's head.

  This patch fixes this by falling back to the non-multipath naming method
  when the parameter disabled using multipath.

  Reported-by: Mike Snitzer 
  Signed-off-by: Keith Busch 
  Reviewed-by: Christoph Hellwig 
  Signed-off-by: Jens Axboe 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1789227/+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 1805920] Re: iPXE ignores vlan 0 traffic

[Mike Pontillo]

Sorry for the confusion.

To be clear, the idea of using MAAS on Xenial was in order to test if
the newly-modified iPXE (on Bionic) can support iSCSI boot.

But come to think of it, I don't think that's a good test. If I remember
correctly, MAAS used TFTP to transfer the kernel and initrd, /then/
iSCSI was used in order to mount the rootfs. So iPXE's iSCSI
functionality wouldn't be exercised in this case.

-- 
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/1805920

Title:
  iPXE ignores vlan 0 traffic

Status in MAAS:
  Invalid
Status in ipxe package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have three MAAS rack/region nodes which are blades in a Cisco UCS
  chassis. This is an FCE deployment where MAAS has two DHCP servers,
  infra1 is the primary and infra3 is the secondary. The pod VMs on
  infra1 and infra3 PXE boot fine but the pod VMs on infra2 fail to PXE
  boot. If I reconfigure the subnet to provide DHCP on infra2 (either as
  primary or secondary) then the pod VMs on infra2 will PXE boot but the
  pod VMs on the demoted infra node (that no longer serves DHCP) now
  fail to PXE boot.

  While commissioning a pod VM on infra2 I captured network traffic with
  tcpdump on the vnet interface.

  Here is the dump when the PXE boot fails (no dhcp server on infra2):
  https://pastebin.canonical.com/p/THW2gTSv4S/

  Here is the dump when PXE boot succeeds (when infra2 is serving dhcp):
  https://pastebin.canonical.com/p/HH3XvZtTGG/

  The only difference I can see is that in the unsuccessful scenario,
  the reply is an 802.1q packet -- it's got a vlan tag for vlan 0.
  Normally vlan 0 traffic is passed as if it is not tagged and indeed, I
  can ping between the blades with no problem. Outgoing packets are
  untagged but incoming packets are tagged vlan 0 -- but the ping works.
  It seems vlan 0 is used as a part of 802.1p to set priority of
  packets. This is separate from vlan, it just happens to use that
  ethertype to do the priority tagging.

  Someone confirmed to me that, in the iPXE source, it drops all packets
  if they are vlan tagged.

  The customer is unable to figure out why the packets between blades is
  getting vlan tagged so we either need to figure out how to allow iPXE
  to accept vlan 0 or the customer will need to use different equipment
  for the MAAS nodes.

  I found a conversation on the ipxe-devel mailing list that suggested a
  commit was submitted and signed off but that was from 2016 so I'm not
  sure what became of it. Notable messages in the thread:

  http://lists.ipxe.org/pipermail/ipxe-devel/2016-April/004916.html
  http://lists.ipxe.org/pipermail/ipxe-devel/2016-July/005099.html

  Would it be possible to install a local patch as part of the FCE
  deployment? I suspect the patch(es) mentioned in the above thread
  would require some modification to apply properly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1805920/+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 1806673] Re: linux-gcp: 4.15.0-1026.27~16.04.1 -proposed tracker

[Brad Figg]

** 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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Uploaded
  phase-changed: Friday, 07. December 2018 15:37 UTC
  reason:
-   promote-to-proposed: Ready for review
+   promote-to-proposed: Packages copied but not yet published to -proposed
+   promote-to-updates: Nvidia GCP object not found -- 4.15.0-1026

-- 
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/1806673

Title:
  linux-gcp: 4.15.0-1026.27~16.04.1 -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:
  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 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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
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:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Uploaded
  phase-changed: Friday, 07. December 2018 15:37 UTC
  reason:
promote-to-proposed: Packages copied but not yet published to -proposed
promote-to-updates: Nvidia GCP object not found -- 4.15.0-1026

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806673/+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 1807432] Missing required logs.

[Ubuntu Kernel Bot]

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 1807432

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

** Tags added: cosmic

-- 
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/1807432

Title:
  /proc/diskstats does not rollup queue depth from partitions

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Tested in Ubuntu 18.04LTS and Ubuntu 18.10, with the same result. The
  queue size rollup works in Centos 7 though.

  root@vagrant:~# uname -a
  Linux vagrant 4.18.0-12-generic #13-Ubuntu SMP Wed Nov 14 15:17:05 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  root@vagrant:~# lsb_release -rd
  Description:Ubuntu 18.10
  Release:18.10

  root@vagrant:~# cat /proc/diskstats 
 7   0 loop0 5 0 16 0 0 0 0 0 0 0 0
 7   1 loop1 0 0 0 0 0 0 0 0 0 0 0
 7   2 loop2 0 0 0 0 0 0 0 0 0 0 0
 7   3 loop3 0 0 0 0 0 0 0 0 0 0 0
 7   4 loop4 0 0 0 0 0 0 0 0 0 0 0
 7   5 loop5 0 0 0 0 0 0 0 0 0 0 0
 7   6 loop6 0 0 0 0 0 0 0 0 0 0 0
 7   7 loop7 0 0 0 0 0 0 0 0 0 0 0
   259   0 nvme0n1 813340 0 10963704 274028 4075 44 1040576 46884 0 18012 
908472
   259   5 nvme0n1p1 203838 0 2749463 65696 986 0 252416 11696 13 14360 
218028
   259   6 nvme0n1p2 202672 0 2713358 67924 1015 0 259840 11696 20 14372 
220388
   259   7 nvme0n1p3 202961 0 2717301 70464 1034 0 264704 11652 19 14344 
226248
   259   8 nvme0n1p4 203216 0 2730974 69944 1028 0 263168 11840 16 14340 
224992
 8   0 sda 11622 783 612090 16416 6529 9730 607624 52912 0 7964 76940
 8   1 sda1 11543 783 607954 16408 4731 9730 607624 52844 0 7380 76304
   253   0 dm-0 12083 0 598666 25540 16198 0 613808 137252 0 7936 162808
   253   1 dm-1 186 0 8696 104 0 0 0 0 0 80 104

  We expect the queue depth of 'nvme0n1' to increase when the partitions
  it has increase, but this never happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807432/+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 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered

[Carl Reinke]

v4.17 final has the bug.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1752961

Title:
  With kernel 4.13 btrfs scans for devices before all devices have been
  discovered

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  See attached dmesg outputs for booting kernels 4.11.x (working) and
  4.13.x (not working).

  dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
  btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have 
been discovered by the kernel.  The btrfs RAID1 filesystem mounts, and 
everything is good.

  dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
  btrfs scans for devices after only 2 (sda, sdb) of the devices have been 
discovered by the kernel.  The btrfs RAID1 filesystem fails to mount ("failed 
to read the system array: -5").  The remaining 2 devices (sdc, sdd) are 
discovered by the kernel immediately afterward.  At the end of the log, I run 
`btrfs device scan` and mount the filesystem manually.

  Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2015-10-15 (933 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: HP ProLiant MicroServer Gen8
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@ 
rootdelay=10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  bionic apport-hook-error
  Uname: Linux 4.15.0-20-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: J06
  dmi.chassis.type: 7
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant MicroServer Gen8
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+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 1807432] Re: /proc/diskstats does not rollup queue depth from partitions

[Albert Autin]

Here is the details on a bare metal ubuntu 18.04 LTS server running an IO 
benchmark:
# uname -a
Linux xxx 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

# lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04

# cat /proc/diskstats 
   7   0 loop0 0 0 0 0 0 0 0 0 0 0 0
   7   1 loop1 0 0 0 0 0 0 0 0 0 0 0
   7   2 loop2 0 0 0 0 0 0 0 0 0 0 0
   7   3 loop3 0 0 0 0 0 0 0 0 0 0 0
   7   4 loop4 0 0 0 0 0 0 0 0 0 0 0
   7   5 loop5 0 0 0 0 0 0 0 0 0 0 0
   7   6 loop6 0 0 0 0 0 0 0 0 0 0 0
   7   7 loop7 0 0 0 0 0 0 0 0 0 0 0
   8   0 sda 42531 5065 2097514 177892 7213856 2831260 295763362 4616524 0 
1535632 4790132
   8   1 sda1 221 30 11808 632 2 0 2 0 0 436 632
   8   2 sda2 42146 5033 2077442 176336 7213854 2831260 295763360 4616524 0 
1535412 4788584
   8  16 sdb 77529 0 39360314 52284 613197 114047 198167776 23144 0 29212 
74964
   8  17 sdb1 77078 0 39335602 52052 613197 114047 198167776 23144 0 29100 
74732
 259   0 nvme0n1 28201525398 0 488820005576 207589544 862135419 98 
226957567536 127289372 0 389795644 709789780
 259  11 nvme0n1p1 2417230384 0 71713692888 554246764 155623487 0 
39839572992 14866796 7 116086276 414538992
 259  12 nvme0n1p2 2417484200 0 71743882112 553922380 155595754 0 
39832473344 14030424 8 115793704 412547176
 259  13 nvme0n1p3 2415958954 0 71634470992 554243464 155462257 0 
39798298112 14474168 10 115988052 413090312
 259  14 nvme0n1p4 2416615620 0 71693490456 554028440 155535038 0 
39816930048 13413172 5 115578348 412099184
 259   5 nvme1n1 9665715778 0 286976448416 2212243248 622132262 98 
165516759344 56229716 0 296178992 2019232932
 259  20 nvme1n1p1 2415904567 0 71636878008 552917888 155454273 0 
39796254208 14455924 5 116082548 412220948
 259  21 nvme1n1p2 2415512074 0 71650757824 552297300 155569570 0 
39825770240 13910420 5 115679536 412130316
 259  22 nvme1n1p3 2416548713 0 71678672568 553555664 155500210 0 
39808014080 14275504 3 116157680 412450228
 259  23 nvme1n1p4 2416416216 0 71684681400 553144864 155607183 0 
39835399168 13506844 9 115654900 412532936
 253   0 dm-0 46520 0 2049706 243712 9679815 0 295763360 4748384 0 1543256 
4994124
 259  10 nvme2n1 9667389541 0 287031008544 2207928032 622164931 98 
165525122608 56921664 0 295218964 2002099520
 259   6 nvme2n1p1 2417118800 0 71696213648 552051652 155532183 0 
39816199168 14594732 12 115840944 412346808
 259   7 nvme2n1p2 2416691746 0 71684078312 551562408 155534110 0 
39816692480 14208680 7 115539968 410287704
 259   8 nvme2n1p3 2416582480 0 71718109272 552480036 155634065 0 
39842280960 14504168 5 115924508 411293804
 259   9 nvme2n1p4 2415651523 0 71604404864 551508236 155463547 0 
39798628352 13532972 7 115275812 409783788
 259  15 nvme3n1 9667640590 0 287047711752 2205542280 622265688 98 
165550916400 56371312 0 295252232 2008945404
 259   1 nvme3n1p1 2417190392 0 71723552872 551558532 155625698 0 
39840139008 14546232 1 115786248 410727612
 259   2 nvme3n1p2 2415650590 0 71604369040 550597652 155449331 0 
39794989056 13932652 1 115166100 409314844
 259   3 nvme3n1p3 2417003647 0 71696320488 551775976 155590921 0 
39831236096 14276596 5 115725292 410703296
 259   4 nvme3n1p4 2416453707 0 71695930384 551283044 155598712 0 
39833230592 13534668 7 115246604 409574764
 253   1 dm-1 587 0 26368 828 0 0 0 0 0 656 828

-- 
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/1807432

Title:
  /proc/diskstats does not rollup queue depth from partitions

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Tested in Ubuntu 18.04LTS and Ubuntu 18.10, with the same result. The
  queue size rollup works in Centos 7 though.

  root@vagrant:~# uname -a
  Linux vagrant 4.18.0-12-generic #13-Ubuntu SMP Wed Nov 14 15:17:05 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  root@vagrant:~# lsb_release -rd
  Description:Ubuntu 18.10
  Release:18.10

  root@vagrant:~# cat /proc/diskstats 
 7   0 loop0 5 0 16 0 0 0 0 0 0 0 0
 7   1 loop1 0 0 0 0 0 0 0 0 0 0 0
 7   2 loop2 0 0 0 0 0 0 0 0 0 0 0
 7   3 loop3 0 0 0 0 0 0 0 0 0 0 0
 7   4 loop4 0 0 0 0 0 0 0 0 0 0 0
 7   5 loop5 0 0 0 0 0 0 0 0 0 0 0
 7   6 loop6 0 0 0 0 0 0 0 0 0 0 0
 7   7 loop7 0 0 0 0 0 0 0 0 0 0 0
   259   0 nvme0n1 813340 0 10963704 274028 4075 44 1040576 46884 0 18012 
908472
   259   5 nvme0n1p1 203838 0 2749463 65696 986 0 252416 11696 13 14360 
218028
   259   6 nvme0n1p2 202672 0 2713358 67924 1015 0 259840 11696 20 14372 
220388
   259   7 nvme0n1p3 202961 0 2717301 70464 1034 0 264704 11652 19 14344 
226248
   259   8 nvme0n1p4 203216 0 2730974 69944 1028 0 263168 11840 16 14340 
224992
 8   0 sda 11622 783 612090 16416 6529 9730 607624 52

[Kernel-packages] [Bug 1807393] Re: nvme - Polling on timeout

[Guilherme G. Piccoli]

** Description changed:

- Description to be updated
+ [Impact]
+ * NVMe controllers potentially could miss to send an interrupt, specially
+ due to bugs in virtual devices(which are common those days - qemu has its
+ own NVMe virtual device, so does AWS). This would be a difficult to
+ debug situation, because NVMe driver only reports the request timeout,
+ not the reason.
  
- [Impact]
+ * The upstream patch proposed to SRU here here, 7776db1ccc12
+ ("NVMe/pci: Poll CQ on timeout") was designed to provide more information
+ in these cases, by pro-actively polling the CQEs on request timeouts, to
+ check if the specific request was completed and some issue (probably a
+ missed interrupt) prevented the driver to notice, or if the request really
+ wasn't completed, which indicates more severe issues.
  
-  * 1
+ * Although quite useful for debugging, this patch could help to mitigate
+ issues in cloud environments like AWS, in case we may have jitter in
+ request completion and the i/o timeout was set to low values, or even
+ in case of atypical bugs in the virtual NVMe controller. With this patch,
+ if polling succeeds the NVMe driver will continue working instead of
+ trying a reset controller procedure, which may lead to fails in the 
+ rootfs - refer to https://launchpad.net/bugs/1788035.
+ 
  
  [Test Case]
  
-  * 2
+ * It's a bit tricky to artificially create a situation of missed interrupt;
+ one idea was to implement a small hack in the NVMe qemu virtual device
+ that given a trigger in guest kernel, will induce the virtual device to
+ skip an interrupt. The hack patch is present in comment #1 below.
+ 
+ * To trigger such hack from guest kernel, all is needed is to issue a
+ raw admin command from nvme-cli: "nvme admin-passthru -o 0xff /dev/nvme0"
+ After that, just perform some I/Os to see one of them aborting - one could
+ use dd for this goal, like "dd if=/dev/zero of=/dev/nvme0n1 count=5".
+ 
  
  [Regression Potential]
  
-  * 3
+ * There are no clear risks in adding such polling mechanism to the NVMe 
driver; one bad thing that was neverreported but could happen with this patch 
is the device could be in a bad state IRQ-wise that a reset would fix, but
+ the patch could cause all requests to be completed via polling, which
+ prevents the adapter reset. This is however a very hypothetical situation,
+ which would also happen in the mainline kernel (since it has the patch).

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1807393

Title:
  nvme - Polling on timeout

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  [Impact]
  * NVMe controllers potentially could miss to send an interrupt, specially
  due to bugs in virtual devices(which are common those days - qemu has its
  own NVMe virtual device, so does AWS). This would be a difficult to
  debug situation, because NVMe driver only reports the request timeout,
  not the reason.

  * The upstream patch proposed to SRU here here, 7776db1ccc12
  ("NVMe/pci: Poll CQ on timeout") was designed to provide more information
  in these cases, by pro-actively polling the CQEs on request timeouts, to
  check if the specific request was completed and some issue (probably a
  missed interrupt) prevented the driver to notice, or if the request really
  wasn't completed, which indicates more severe issues.

  * Although quite useful for debugging, this patch could help to mitigate
  issues in cloud environments like AWS, in case we may have jitter in
  request completion and the i/o timeout was set to low values, or even
  in case of atypical bugs in the virtual NVMe controller. With this patch,
  if polling succeeds the NVMe driver will continue working instead of
  trying a reset controller procedure, which may lead to fails in the 
  rootfs - refer to https://launchpad.net/bugs/1788035.

  
  [Test Case]

  * It's a bit tricky to artificially create a situation of missed interrupt;
  one idea was to implement a small hack in the NVMe qemu virtual device
  that given a trigger in guest kernel, will induce the virtual device to
  skip an interrupt. The hack patch is present in comment #1 below.

  * To trigger such hack from guest kernel, all is needed is to issue a
  raw admin command from nvme-cli: "nvme admin-passthru -o 0xff /dev/nvme0"
  After that, just perform some I/Os to see one of them aborting - one could
  use dd for this goal, like "dd if=/dev/zero of=/dev/nvme0n1 count=5".

  
  [Regression Potential]

  * There are no clear risks in adding such polling mechanism to the NVMe 
driver; one bad thing that was neverreported but could happen with this patch 
is the device could be in a bad state IRQ-wise that a reset would fix, but
  the patch could cause all requests to be completed via polling, which
  prevents the adapter reset. This is however a very hypothetical sit

[Kernel-packages] [Bug 1807393] Re: nvme - Polling on timeout

[Guilherme G. Piccoli]

** Changed in: linux (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

-- 
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/1807393

Title:
  nvme - Polling on timeout

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  [Impact]
  * NVMe controllers potentially could miss to send an interrupt, specially
  due to bugs in virtual devices(which are common those days - qemu has its
  own NVMe virtual device, so does AWS). This would be a difficult to
  debug situation, because NVMe driver only reports the request timeout,
  not the reason.

  * The upstream patch proposed to SRU here here, 7776db1ccc12
  ("NVMe/pci: Poll CQ on timeout") was designed to provide more information
  in these cases, by pro-actively polling the CQEs on request timeouts, to
  check if the specific request was completed and some issue (probably a
  missed interrupt) prevented the driver to notice, or if the request really
  wasn't completed, which indicates more severe issues.

  * Although quite useful for debugging, this patch could help to mitigate
  issues in cloud environments like AWS, in case we may have jitter in
  request completion and the i/o timeout was set to low values, or even
  in case of atypical bugs in the virtual NVMe controller. With this patch,
  if polling succeeds the NVMe driver will continue working instead of
  trying a reset controller procedure, which may lead to fails in the 
  rootfs - refer to https://launchpad.net/bugs/1788035.

  
  [Test Case]

  * It's a bit tricky to artificially create a situation of missed interrupt;
  one idea was to implement a small hack in the NVMe qemu virtual device
  that given a trigger in guest kernel, will induce the virtual device to
  skip an interrupt. The hack patch is present in comment #1 below.

  * To trigger such hack from guest kernel, all is needed is to issue a
  raw admin command from nvme-cli: "nvme admin-passthru -o 0xff /dev/nvme0"
  After that, just perform some I/Os to see one of them aborting - one could
  use dd for this goal, like "dd if=/dev/zero of=/dev/nvme0n1 count=5".

  
  [Regression Potential]

  * There are no clear risks in adding such polling mechanism to the NVMe 
driver; one bad thing that was neverreported but could happen with this patch 
is the device could be in a bad state IRQ-wise that a reset would fix, but
  the patch could cause all requests to be completed via polling, which
  prevents the adapter reset. This is however a very hypothetical situation,
  which would also happen in the mainline kernel (since it has the patch).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807393/+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 1807393] Re: nvme - Polling on timeout

[Eric Desrochers]

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1807393

Title:
  nvme - Polling on timeout

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  [Impact]
  * NVMe controllers potentially could miss to send an interrupt, specially
  due to bugs in virtual devices(which are common those days - qemu has its
  own NVMe virtual device, so does AWS). This would be a difficult to
  debug situation, because NVMe driver only reports the request timeout,
  not the reason.

  * The upstream patch proposed to SRU here here, 7776db1ccc12
  ("NVMe/pci: Poll CQ on timeout") was designed to provide more information
  in these cases, by pro-actively polling the CQEs on request timeouts, to
  check if the specific request was completed and some issue (probably a
  missed interrupt) prevented the driver to notice, or if the request really
  wasn't completed, which indicates more severe issues.

  * Although quite useful for debugging, this patch could help to mitigate
  issues in cloud environments like AWS, in case we may have jitter in
  request completion and the i/o timeout was set to low values, or even
  in case of atypical bugs in the virtual NVMe controller. With this patch,
  if polling succeeds the NVMe driver will continue working instead of
  trying a reset controller procedure, which may lead to fails in the 
  rootfs - refer to https://launchpad.net/bugs/1788035.

  
  [Test Case]

  * It's a bit tricky to artificially create a situation of missed interrupt;
  one idea was to implement a small hack in the NVMe qemu virtual device
  that given a trigger in guest kernel, will induce the virtual device to
  skip an interrupt. The hack patch is present in comment #1 below.

  * To trigger such hack from guest kernel, all is needed is to issue a
  raw admin command from nvme-cli: "nvme admin-passthru -o 0xff /dev/nvme0"
  After that, just perform some I/Os to see one of them aborting - one could
  use dd for this goal, like "dd if=/dev/zero of=/dev/nvme0n1 count=5".

  
  [Regression Potential]

  * There are no clear risks in adding such polling mechanism to the NVMe 
driver; one bad thing that was neverreported but could happen with this patch 
is the device could be in a bad state IRQ-wise that a reset would fix, but
  the patch could cause all requests to be completed via polling, which
  prevents the adapter reset. This is however a very hypothetical situation,
  which would also happen in the mainline kernel (since it has the patch).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807393/+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 1807432] [NEW] /proc/diskstats does not rollup queue depth from partitions

[Albert Autin]

Public bug reported:

Tested in Ubuntu 18.04LTS and Ubuntu 18.10, with the same result. The
queue size rollup works in Centos 7 though.

root@vagrant:~# uname -a
Linux vagrant 4.18.0-12-generic #13-Ubuntu SMP Wed Nov 14 15:17:05 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

root@vagrant:~# lsb_release -rd
Description:Ubuntu 18.10
Release:18.10

root@vagrant:~# cat /proc/diskstats 
   7   0 loop0 5 0 16 0 0 0 0 0 0 0 0
   7   1 loop1 0 0 0 0 0 0 0 0 0 0 0
   7   2 loop2 0 0 0 0 0 0 0 0 0 0 0
   7   3 loop3 0 0 0 0 0 0 0 0 0 0 0
   7   4 loop4 0 0 0 0 0 0 0 0 0 0 0
   7   5 loop5 0 0 0 0 0 0 0 0 0 0 0
   7   6 loop6 0 0 0 0 0 0 0 0 0 0 0
   7   7 loop7 0 0 0 0 0 0 0 0 0 0 0
 259   0 nvme0n1 813340 0 10963704 274028 4075 44 1040576 46884 0 18012 
908472
 259   5 nvme0n1p1 203838 0 2749463 65696 986 0 252416 11696 13 14360 218028
 259   6 nvme0n1p2 202672 0 2713358 67924 1015 0 259840 11696 20 14372 
220388
 259   7 nvme0n1p3 202961 0 2717301 70464 1034 0 264704 11652 19 14344 
226248
 259   8 nvme0n1p4 203216 0 2730974 69944 1028 0 263168 11840 16 14340 
224992
   8   0 sda 11622 783 612090 16416 6529 9730 607624 52912 0 7964 76940
   8   1 sda1 11543 783 607954 16408 4731 9730 607624 52844 0 7380 76304
 253   0 dm-0 12083 0 598666 25540 16198 0 613808 137252 0 7936 162808
 253   1 dm-1 186 0 8696 104 0 0 0 0 0 80 104

We expect the queue depth of 'nvme0n1' to increase when the partitions
it has increase, but this never happens.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: cosmic disk diskstats queue

** Package changed: apport (Ubuntu) => ubuntu

** 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/1807432

Title:
  /proc/diskstats does not rollup queue depth from partitions

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Tested in Ubuntu 18.04LTS and Ubuntu 18.10, with the same result. The
  queue size rollup works in Centos 7 though.

  root@vagrant:~# uname -a
  Linux vagrant 4.18.0-12-generic #13-Ubuntu SMP Wed Nov 14 15:17:05 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  root@vagrant:~# lsb_release -rd
  Description:Ubuntu 18.10
  Release:18.10

  root@vagrant:~# cat /proc/diskstats 
 7   0 loop0 5 0 16 0 0 0 0 0 0 0 0
 7   1 loop1 0 0 0 0 0 0 0 0 0 0 0
 7   2 loop2 0 0 0 0 0 0 0 0 0 0 0
 7   3 loop3 0 0 0 0 0 0 0 0 0 0 0
 7   4 loop4 0 0 0 0 0 0 0 0 0 0 0
 7   5 loop5 0 0 0 0 0 0 0 0 0 0 0
 7   6 loop6 0 0 0 0 0 0 0 0 0 0 0
 7   7 loop7 0 0 0 0 0 0 0 0 0 0 0
   259   0 nvme0n1 813340 0 10963704 274028 4075 44 1040576 46884 0 18012 
908472
   259   5 nvme0n1p1 203838 0 2749463 65696 986 0 252416 11696 13 14360 
218028
   259   6 nvme0n1p2 202672 0 2713358 67924 1015 0 259840 11696 20 14372 
220388
   259   7 nvme0n1p3 202961 0 2717301 70464 1034 0 264704 11652 19 14344 
226248
   259   8 nvme0n1p4 203216 0 2730974 69944 1028 0 263168 11840 16 14340 
224992
 8   0 sda 11622 783 612090 16416 6529 9730 607624 52912 0 7964 76940
 8   1 sda1 11543 783 607954 16408 4731 9730 607624 52844 0 7380 76304
   253   0 dm-0 12083 0 598666 25540 16198 0 613808 137252 0 7936 162808
   253   1 dm-1 186 0 8696 104 0 0 0 0 0 80 104

  We expect the queue depth of 'nvme0n1' to increase when the partitions
  it has increase, but this never happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807432/+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 1806673] Re: linux-gcp: 4.15.0-1026.27~16.04.1 -proposed tracker

[Steve Langasek]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve 
Langasek (vorlon)

-- 
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/1806673

Title:
  linux-gcp: 4.15.0-1026.27~16.04.1 -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:
  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 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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
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:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Uploaded
  phase-changed: Friday, 07. December 2018 15:37 UTC
  reason:
promote-to-proposed: Ready for review

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806673/+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 1807432] [NEW] /proc/diskstats does not rollup queue depth from partitions

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Tested in Ubuntu 18.04LTS and Ubuntu 18.10, with the same result. The
queue size rollup works in Centos 7 though.

root@vagrant:~# uname -a
Linux vagrant 4.18.0-12-generic #13-Ubuntu SMP Wed Nov 14 15:17:05 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

root@vagrant:~# lsb_release -rd
Description:Ubuntu 18.10
Release:18.10

root@vagrant:~# cat /proc/diskstats 
   7   0 loop0 5 0 16 0 0 0 0 0 0 0 0
   7   1 loop1 0 0 0 0 0 0 0 0 0 0 0
   7   2 loop2 0 0 0 0 0 0 0 0 0 0 0
   7   3 loop3 0 0 0 0 0 0 0 0 0 0 0
   7   4 loop4 0 0 0 0 0 0 0 0 0 0 0
   7   5 loop5 0 0 0 0 0 0 0 0 0 0 0
   7   6 loop6 0 0 0 0 0 0 0 0 0 0 0
   7   7 loop7 0 0 0 0 0 0 0 0 0 0 0
 259   0 nvme0n1 813340 0 10963704 274028 4075 44 1040576 46884 0 18012 
908472
 259   5 nvme0n1p1 203838 0 2749463 65696 986 0 252416 11696 13 14360 218028
 259   6 nvme0n1p2 202672 0 2713358 67924 1015 0 259840 11696 20 14372 
220388
 259   7 nvme0n1p3 202961 0 2717301 70464 1034 0 264704 11652 19 14344 
226248
 259   8 nvme0n1p4 203216 0 2730974 69944 1028 0 263168 11840 16 14340 
224992
   8   0 sda 11622 783 612090 16416 6529 9730 607624 52912 0 7964 76940
   8   1 sda1 11543 783 607954 16408 4731 9730 607624 52844 0 7380 76304
 253   0 dm-0 12083 0 598666 25540 16198 0 613808 137252 0 7936 162808
 253   1 dm-1 186 0 8696 104 0 0 0 0 0 80 104

We expect the queue depth of 'nvme0n1' to increase when the partitions
it has increase, but this never happens.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: disk diskstats queue
-- 
/proc/diskstats does not rollup queue depth from partitions
https://bugs.launchpad.net/bugs/1807432
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 1491494] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From cdead...@us.ibm.com 2018-12-07 12:55 EDT---
This CMVC defect is being cancelled by the CDE Bridge because the corresponding 
CQ Defect [SW317564] was transferred out of the bridge domain.
Here are the additional details:
New Subsystem = ppc_triage
New Release = unspecified
New Component = ubuntu_linux
New OwnerInfo = Chavez, Luciano (cha...@us.ibm.com)
To continue tracking this issue, please follow CQ defect [SW317564].

-- 
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/1491494

Title:
  Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed
  from profile

Status in linux package in Ubuntu:
  Triaged

Bug description:
  -- Problem Description --

  The failure related to the BELL-3 (2 port-Async EIA-232 adapter).
  Ubuntu always hit exception when the adapter is not present. See my
  test scenarios below.

  Test #1: Boot Ubuntu with BELL-3 adapter 
  ===

  - The Ubuntu LPAR was running with the BELL-3 (2 port-Async EIA-232 adapter) 
before. So I assigned the BELL-3 adapter to Ubuntu LPAR profile and powered on 
the LPAR. 
  => Ubuntu boot fine this time.

   
  Test #2: Boot Ubuntu with BELL-3 adapter removed from LPAR profile
  ===

  - I powered down the Ubuntu partition and removed the BELL-3 adapter from 
LPAR profile then powered on the LPAR.
  => Ubuntu hit the exception.

  Elapsed time since release of system processors: 0 mins 9 secs
  error: no suitable video mode found.
  OF stdout device is: /vdevice/vty@3000
  Preparing to boot Linux version 3.19.0-23-generic (buildd@denneed03) (gcc 
version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #24~14.04.1-Ubuntu SMP Wed Jul 8 
11:17:19 UTC 2015 (Ubuntu 3.19.0-23.24~14.04.1-generic 3.19.8-ckt2)
  Detected machine type: 0101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/boot/vmlinux-3.19.0-23-generic 
root=UUID=768190e7-f633-4c63-a1e3-588d12dea265 ro quiet splash vt.handoff=7
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0b42
alloc_top: 1000
alloc_top_hi : 1000
rmo_top  : 1000
ram_top  : 1000
  instantiating rtas at 0x0ecb... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x0b43 -> 0x0b4316b1
  Device tree struct  0x0b44 -> 0x0b47
  Calling quiesce...
  returning from prom_init
   -> smp_release_cpus()
  spinning_secondaries = 15
   <- smp_release_cpus()
   <- setup_system()
  [0.661510] 
/build/linux-lts-vivid-uV14Ja/linux-lts-vivid-3.19.0/drivers/rtc/hctosys.c: 
unable to open rtc device (rtc0)
  [0.672826] sd 0:0:1:0: [sda] Assuming drive cache: write through
  [4.658302] device-mapper: table: 252:0: multipath: error getting device
  [4.691990] device-mapper: table: 252:0: multipath: error getting device
  [4.934034] device-mapper: table: 252:0: multipath: error getting device
  [4.951977] device-mapper: table: 252:0: multipath: error getting device
   * Discovering and coalescing multipaths...  [ OK 
] 
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
   * Starting AppArmor profiles[ OK 
] 
  Loading the saved-state of the serial devices... 
  [5.109665] Unable to handle kernel paging request for data at address 
0xd803
  [5.109677] Faulting instruction address: 0xc060fec4
  [5.109685] Oops: Kernel access of bad area, sig: 11 [#1]
  [5.109691] SMP NR_CPUS=2048 NUMA pSeries
  [5.109699] Modules linked in: dm_round_robin dm_multipath scsi_dh 
pseries_rng rtc_generic knem(OE) nfsd auth_rpcgss nfs_acl nfs lockd grace 
sunrpc fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) configfs 
ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) mlx5_core(OE) 
mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) ib_addr(OE) mlx4_en(OE) 
mlx4_core(OE) mlx_compat(OE)
  [5.109759] CPU: 1 PID: 1816 Comm: setserial Tainted: G   OE  
3.19.0-23-generic #24~14.04.1-Ubuntu
  [5.109769] task: c000f389c880 ti: c000f0528000 task.ti: 
c000f0528000
  [5.109777] NIP: c060fec4 LR: c0617498 CTR: 
c060fe20
  [5.109785] REGS: c000f052b6b0 TRAP: 0300   Tainted: G   OE   
(3.19.0-23-generic)
  [5.109793] MSR: 80009033   CR: 84002022  
XER: 
  [5.109814] CFAR: c0008468 DAR: d803 DSISR: 4200 
SOFTE: 1 
  GPR00: c0617498 c000f052b930 c144c700 00bf 
  GPR04: d803 00bf c000f399 0141 
  GPR08: c0611d20 c000

[Kernel-packages] [Bug 1491494] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From bjki...@us.ibm.com 2018-12-07 12:38 EDT---
Rejecting this very old bug. Please reopen if this issue occurs on a current 
version of 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/1491494

Title:
  Ubuntu 14.04.03 LPAR hits kernel oops after serial adapter is removed
  from profile

Status in linux package in Ubuntu:
  Triaged

Bug description:
  -- Problem Description --

  The failure related to the BELL-3 (2 port-Async EIA-232 adapter).
  Ubuntu always hit exception when the adapter is not present. See my
  test scenarios below.

  Test #1: Boot Ubuntu with BELL-3 adapter 
  ===

  - The Ubuntu LPAR was running with the BELL-3 (2 port-Async EIA-232 adapter) 
before. So I assigned the BELL-3 adapter to Ubuntu LPAR profile and powered on 
the LPAR. 
  => Ubuntu boot fine this time.

   
  Test #2: Boot Ubuntu with BELL-3 adapter removed from LPAR profile
  ===

  - I powered down the Ubuntu partition and removed the BELL-3 adapter from 
LPAR profile then powered on the LPAR.
  => Ubuntu hit the exception.

  Elapsed time since release of system processors: 0 mins 9 secs
  error: no suitable video mode found.
  OF stdout device is: /vdevice/vty@3000
  Preparing to boot Linux version 3.19.0-23-generic (buildd@denneed03) (gcc 
version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #24~14.04.1-Ubuntu SMP Wed Jul 8 
11:17:19 UTC 2015 (Ubuntu 3.19.0-23.24~14.04.1-generic 3.19.8-ckt2)
  Detected machine type: 0101
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/boot/vmlinux-3.19.0-23-generic 
root=UUID=768190e7-f633-4c63-a1e3-588d12dea265 ro quiet splash vt.handoff=7
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0b42
alloc_top: 1000
alloc_top_hi : 1000
rmo_top  : 1000
ram_top  : 1000
  instantiating rtas at 0x0ecb... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x0b43 -> 0x0b4316b1
  Device tree struct  0x0b44 -> 0x0b47
  Calling quiesce...
  returning from prom_init
   -> smp_release_cpus()
  spinning_secondaries = 15
   <- smp_release_cpus()
   <- setup_system()
  [0.661510] 
/build/linux-lts-vivid-uV14Ja/linux-lts-vivid-3.19.0/drivers/rtc/hctosys.c: 
unable to open rtc device (rtc0)
  [0.672826] sd 0:0:1:0: [sda] Assuming drive cache: write through
  [4.658302] device-mapper: table: 252:0: multipath: error getting device
  [4.691990] device-mapper: table: 252:0: multipath: error getting device
  [4.934034] device-mapper: table: 252:0: multipath: error getting device
  [4.951977] device-mapper: table: 252:0: multipath: error getting device
   * Discovering and coalescing multipaths...  [ OK 
] 
  Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
   * Starting AppArmor profiles[ OK 
] 
  Loading the saved-state of the serial devices... 
  [5.109665] Unable to handle kernel paging request for data at address 
0xd803
  [5.109677] Faulting instruction address: 0xc060fec4
  [5.109685] Oops: Kernel access of bad area, sig: 11 [#1]
  [5.109691] SMP NR_CPUS=2048 NUMA pSeries
  [5.109699] Modules linked in: dm_round_robin dm_multipath scsi_dh 
pseries_rng rtc_generic knem(OE) nfsd auth_rpcgss nfs_acl nfs lockd grace 
sunrpc fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) configfs 
ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) mlx5_core(OE) 
mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) ib_addr(OE) mlx4_en(OE) 
mlx4_core(OE) mlx_compat(OE)
  [5.109759] CPU: 1 PID: 1816 Comm: setserial Tainted: G   OE  
3.19.0-23-generic #24~14.04.1-Ubuntu
  [5.109769] task: c000f389c880 ti: c000f0528000 task.ti: 
c000f0528000
  [5.109777] NIP: c060fec4 LR: c0617498 CTR: 
c060fe20
  [5.109785] REGS: c000f052b6b0 TRAP: 0300   Tainted: G   OE   
(3.19.0-23-generic)
  [5.109793] MSR: 80009033   CR: 84002022  
XER: 
  [5.109814] CFAR: c0008468 DAR: d803 DSISR: 4200 
SOFTE: 1 
  GPR00: c0617498 c000f052b930 c144c700 00bf 
  GPR04: d803 00bf c000f399 0141 
  GPR08: c0611d20 c13539e0 d800 c1351ba8 
  GPR12: c060fe20 ce830900   
  GPR16:     
  GPR20: 007d 0040   
  GPR2

[Kernel-packages] [Bug 1798583] Re: the new Steam Controller driver breaks it on Steam

[kisak]

Hello Kai-Heng Feng, on Ubuntu 18.04.1, I grabbed
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18.20/ and your build.
With 4.18.20 mainline I can confirm Rocket League's main menu can not be
navigated via the Steam Controller, and can be with your test build. No
game play was tested and only one game was tested. Game was launched
from Steam's Big Picture Mode.

-- 
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/1798583

Title:
  the new Steam Controller driver breaks it on Steam

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  The new hid_steam driver in kernel 4.18 breaks the use of it within
  Steam.

  Games either:
  - Crash
  - Don't detect it at all
  - Only pick it up as player 2

  To get it working as normal, it needs blacklisting currently.

  See here: https://www.gamingonlinux.com/articles/the-steam-controller-
  on-ubuntu-1810-and-other-distributions-using-linux-kernel-418-needs-
  quick-a-fix.12775

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  liam   2492 F pulseaudio
   /dev/snd/controlC0:  liam   2492 F pulseaudio
   /dev/snd/controlC1:  liam   2492 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 18 12:49:44 2018
  InstallationDate: Installed on 2017-10-18 (364 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS All Series
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2a8676f3-0045-4e66-9cd1-186ffc6a8c2a ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago)
  dmi.bios.date: 08/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1901
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH X99
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: PCS
  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.:bvr1901:bd08/10/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1798583/+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 1807406] Re: hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device

[Bug Watch Updater]

Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=201929.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-12-07T15:46:45+00:00 caravena wrote:

Hello,

Open bug in laucnhpad.net
https://bugs.launchpad.net/bugs/1807406

"Message after returning from suspension"

dmesg:
hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP 
device

Best regards,
--
Cristian Aravena Romero (caravena)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807406/comments/3


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => 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/1807406

Title:
  hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from
  ISHTP device

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Message after returning from suspension

  dmesg:
  [13383.967611] hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for 
response from ISHTP device
  [13383.967615] hid-sensor-hub 001F:8086:22D8.0002: timeout waiting for 
response from ISHTP device

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-8-generic 4.19.0-8.9
  ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6
  Uname: Linux 4.19.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2769 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  7 12:02:26 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.19.0-8-generic N/A
   linux-backports-modules-4.19.0-8-generic  N/A
   linux-firmware1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1807406/+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 1447664] Re: 14e4:1687 broadcom tg3 network driver disconnects under high load

[Wu]

Hi,

the commit 3a498606bb04af603a46ebde8296040b2de350d1 mentioned in #54 has
been integrated to my current customized RHEL(CentOS)-7 for a certain
time. This fix can also be found in the new kernel releases, however
even with the 4.19 mainline kernel the bug is still not solved.

- For a 1Gbps ethernet, nothing was changed with this commit. There was
immediately the crash after some transmission.

- With the 100M ethernet, the crash is not very often triggered even
without the above fix. I cannot judge yet.


Best regards

-- 
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/1447664

Title:
  14e4:1687 broadcom tg3 network driver disconnects under high load

Status in linux package in Ubuntu:
  Triaged
Status in linux package in Debian:
  New

Bug description:
  The tg3 broadcom network driver that binds with chipset 5762 goes offline and 
unable to recover (even with tg3 watchdog timeout) when network transmit is 
under high load.  Call trace:
  https://launchpadlibrarian.net/204185480/dmesg

  When this happens, only a reboot would be able to fix it.  Sometimes,
  however, bringing the interface offline and online (via ifconfig)
  would recover networking.  I've also tested with the latest tg3 driver
  (dec 2014 version) and networking is still problematic.  I have also
  disabled TSO, GSO etc... with ethtool and the bug still surfaces.
  This bug may be related to the integrated Firmware.

  Here is the procedure to replicate the issue because it is hard to
  replicate it under moderate network load.

  1. Bootup a machine with a broadcom 5762 NIC (ie. HP DeskElite 705) using a 
Ubuntu/Kubunu Live CD 14.04-15.04.
  2. from another machine: start 5 sessions, repetitively copy (scp with public 
key authentication) a 70 meg file back and forth to the tg3 machine in each 
session. (not sure if this is necessary)
  3. create a 1GB file on the tg3 machine, with something like dd 
if=/dev/urandom of=/my/test/file bs=1024 count=$((1024*1000))
  4. from another machine: repetitively scp copy that 1GB file from the tg3 
machine. This can be done with something like:

  while [ 0 ]; do
     scp -i /my/scp/private.key u...@ip.of.tg3:/my/test/file /tmp
  done;

  Networking will mostly goes offline in about 10-30 minutes.

  WORKAROUND: Add udev rule to make the changes permanent in 
/etc/udev/rules.d/80-tg3-fix.rules :
  ACTION=="add", SUBSYSTEM=="net", ATTRS{vendor}=="0x14e4", 
ATTRS{device}=="0x1687", RUN+="/sbin/ethtool -K %k highdma off"

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-15-generic 3.19.0-15.15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kubuntu3748 F pulseaudio
   /dev/snd/controlC0:  kubuntu3748 F pulseaudio
  CasperVersion: 1.360
  Date: Thu Apr 23 11:16:24 2015
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  LiveMediaBuild: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard HP EliteDesk 705 G1 MT
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper maybe-ubiquity quiet splash ---
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  RfKill:

  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L06 v02.15
  dmi.board.asset.tag: 2UA5041TG4
  dmi.board.name: 2215
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA5041TG4
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL06v02.15:bd10/22/2014:svnHewlett-Packard:pnHPEliteDesk705G1MT:pvr:rvnHewlett-Packard:rn2215:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP EliteDesk 705 G1 MT
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447664/+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 1805920] Re: iPXE ignores vlan 0 traffic

[Andres Rodriguez]

Just to clarify the above statements as it has been source of confusion.

MAAS 2.3+ (which is the latest available in Xenial), no longer uses nor
supports iSCSI. While the option to fallback to old behavior does exist,
it is not enabled by default, its obscured and, given that is not
supported, it is to be used at users risk.

That said, I'm not sure whether this change should be backported all the
way to Xenial. It would seem to be that it should be backported to
Bionic only.

-- 
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/1805920

Title:
  iPXE ignores vlan 0 traffic

Status in MAAS:
  Invalid
Status in ipxe package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have three MAAS rack/region nodes which are blades in a Cisco UCS
  chassis. This is an FCE deployment where MAAS has two DHCP servers,
  infra1 is the primary and infra3 is the secondary. The pod VMs on
  infra1 and infra3 PXE boot fine but the pod VMs on infra2 fail to PXE
  boot. If I reconfigure the subnet to provide DHCP on infra2 (either as
  primary or secondary) then the pod VMs on infra2 will PXE boot but the
  pod VMs on the demoted infra node (that no longer serves DHCP) now
  fail to PXE boot.

  While commissioning a pod VM on infra2 I captured network traffic with
  tcpdump on the vnet interface.

  Here is the dump when the PXE boot fails (no dhcp server on infra2):
  https://pastebin.canonical.com/p/THW2gTSv4S/

  Here is the dump when PXE boot succeeds (when infra2 is serving dhcp):
  https://pastebin.canonical.com/p/HH3XvZtTGG/

  The only difference I can see is that in the unsuccessful scenario,
  the reply is an 802.1q packet -- it's got a vlan tag for vlan 0.
  Normally vlan 0 traffic is passed as if it is not tagged and indeed, I
  can ping between the blades with no problem. Outgoing packets are
  untagged but incoming packets are tagged vlan 0 -- but the ping works.
  It seems vlan 0 is used as a part of 802.1p to set priority of
  packets. This is separate from vlan, it just happens to use that
  ethertype to do the priority tagging.

  Someone confirmed to me that, in the iPXE source, it drops all packets
  if they are vlan tagged.

  The customer is unable to figure out why the packets between blades is
  getting vlan tagged so we either need to figure out how to allow iPXE
  to accept vlan 0 or the customer will need to use different equipment
  for the MAAS nodes.

  I found a conversation on the ipxe-devel mailing list that suggested a
  commit was submitted and signed off but that was from 2016 so I'm not
  sure what became of it. Notable messages in the thread:

  http://lists.ipxe.org/pipermail/ipxe-devel/2016-April/004916.html
  http://lists.ipxe.org/pipermail/ipxe-devel/2016-July/005099.html

  Would it be possible to install a local patch as part of the FCE
  deployment? I suspect the patch(es) mentioned in the above thread
  would require some modification to apply properly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1805920/+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 1807259] Re: sky2 ethernet card doesn't work after returning from suspend

[Richard]

I am using Linux Mint, where apport is not installed. Does it make sense
to install and run the 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/1807259

Title:
  sky2 ethernet card doesn't work after returning from suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am on "Linux Mint 18.2 Sonya".

  Upgrading to Kernel 4.15.0-39.42~16.04.1 leaves the ethernet adapter
  inactive after resume from suspend. I reverted to a 4.13 kernel for
  this reason for which it works.

  the bug seems to be similar to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921.

  $ lshw -class network
  WARNUNG: Sie sollten dieses Programm mit Systemverwalterrechten (root) 
ausführen.
*-network DEAKTIVIERT
 Beschreibung: Kabellose Verbindung
 Produkt: BCM4312 802.11b/g LP-PHY
 Hersteller: Broadcom Corporation
 Physische ID: 0
 Bus-Informationen: pci@:0c:00.0
 Logischer Name: wlp12s0
 Version: 01
 Seriennummer: 00:26:5e:33:a9:6d
 Breite: 64 bits
 Takt: 33MHz
 Fähigkeiten: bus_master cap_list ethernet physical wireless
 Konfiguration: broadcast=yes driver=wl0 driverversion=6.30.223.271 
(r587334) latency=0 multicast=yes wireless=IEEE 802.11
 Ressourcen: irq:17 memory:f69fc000-f69f
*-network
 Beschreibung: Ethernet interface
 Produkt: 88E8040 PCI-E Fast Ethernet Controller
 Hersteller: Marvell Technology Group Ltd.
 Physische ID: 0
 Bus-Informationen: pci@:09:00.0
 Logischer Name: enp9s0
 Version: 13
 Seriennummer: 00:25:64:4a:26:00
 Größe: 100Mbit/s
 Kapazität: 100Mbit/s
 Breite: 64 bits
 Takt: 33MHz
 Fähigkeiten: bus_master cap_list ethernet physical tp 10bt 10bt-fd 
100bt 100bt-fd autonegotiation
 Konfiguration: autonegotiation=on broadcast=yes driver=sky2 
driverversion=1.30 duplex=full ip=192.168.1.7 latency=0 link=yes multicast=yes 
port=twisted pair speed=100Mbit/s
 Ressourcen: irq:24 memory:f68fc000-f68f ioport:de00(Größe=256)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807259/+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 1807416] Status changed to Confirmed

[Ubuntu Kernel Bot]

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/1807416

Title:
  secureboot: Secure boot could not be determined (mode 0)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  dmesg:
  [0.00] secureboot: Secure boot could not be determined (mode 0)

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-8-generic 4.19.0-8.9
  ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6
  Uname: Linux 4.19.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2769 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   2769 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  7 12:58:49 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.19.0-8-generic N/A
   linux-backports-modules-4.19.0-8-generic  N/A
   linux-firmware1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807416/+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 1798921] Re: sky2 ethernet card don't work after returning from suspension

[Richard]

Sorry, didn't realize what was meant. I don't use WoL, only suspend
(manually or by closing the lid). Resume works for me with the 4.13
kernels Mint provided so far. All of the 4.15 kernels I tried so far
didn't work.

I've also filed
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807259 for this
issue.

-- 
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/1798921

Title:
  sky2 ethernet card don't work after returning from suspension

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bug very similar to #1752772
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772) but
  affecting the sky2 driver instead of r8169.

  After system suspend the ethernet connection stops working. The card
  is still up and the modem can see it is connected, but the card
  doesn't get an ip address. Ifconfig down/up and restarting network-
  manager does not solve the issue. Similarly to the other bug, "sudo
  modprobe sky2 -r" an then "sudo modprobe sky2" solves the issue.

  Relevant: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/107
  

  Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018
  x86_64 x86_64 x86_64 GNU/Linux

    *-network
     description: Ethernet interface
     product: 88E8040 PCI-E Fast Ethernet Controller
     vendor: Marvell Technology Group Ltd.
     physical id: 0
     bus info: pci@:09:00.0
     logical name: enp9s0
     version: 13
     serial:
     size: 100Mbit/s
     capacity: 100Mbit/s
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=sky2 
driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted 
pair speed=100Mbit/s
     resources: irq:24 memory:f68fc000-f68f ioport:de00(size=256)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/+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 1807416] [NEW] secureboot: Secure boot could not be determined (mode 0)

[Cristian Aravena Romero]

Public bug reported:

Hello,

dmesg:
[0.00] secureboot: Secure boot could not be determined (mode 0)

Best regards,
--
Cristian Aravena Romero (caravena)

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-4.19.0-8-generic 4.19.0-8.9
ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6
Uname: Linux 4.19.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caravena   2769 F pulseaudio
 /dev/snd/pcmC0D0p:   caravena   2769 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec  7 12:58:49 2018
HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
InstallationDate: Installed on 2018-12-02 (4 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.19.0-8-generic N/A
 linux-backports-modules-4.19.0-8-generic  N/A
 linux-firmware1.176
SourcePackage: linux
UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago)
dmi.bios.date: 06/14/2018
dmi.bios.vendor: Insyde
dmi.bios.version: F.13
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8486
dmi.board.vendor: HP
dmi.board.version: 72.19
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
dmi.product.sku: 3PX63LA#ABM
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: 3px63la amd64 apport-bug disco hp hp-pavilion-x360-14-cd0008la 
package-from-proposed wayland-session

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1807416

Title:
  secureboot: Secure boot could not be determined (mode 0)

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  dmesg:
  [0.00] secureboot: Secure boot could not be determined (mode 0)

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-8-generic 4.19.0-8.9
  ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6
  Uname: Linux 4.19.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2769 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   2769 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  7 12:58:49 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.19.0-8-generic N/A
   linux-backports-modules-4.19.0-8-generic  N/A
   linux-firmware1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807416/+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 1807406] Re: hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device

[Cristian Aravena Romero]

** Bug watch added: Linux Kernel Bug Tracker #201929
   https://bugzilla.kernel.org/show_bug.cgi?id=201929

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=201929
   Importance: Unknown
   Status: Unknown

-- 
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/1807406

Title:
  hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from
  ISHTP device

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Message after returning from suspension

  dmesg:
  [13383.967611] hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for 
response from ISHTP device
  [13383.967615] hid-sensor-hub 001F:8086:22D8.0002: timeout waiting for 
response from ISHTP device

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-8-generic 4.19.0-8.9
  ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6
  Uname: Linux 4.19.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2769 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  7 12:02:26 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.19.0-8-generic N/A
   linux-backports-modules-4.19.0-8-generic  N/A
   linux-firmware1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1807406/+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 1806672] Re: linux-azure: 4.15.0-1036.38~16.04.1 -proposed tracker

[Brad Figg]

** 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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 15:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ready
regression-testing: Testing in progress
security-signoff: Waiting for signoff
snap-release-to-beta: Snap not in beta channel
snap-release-to-edge: Snap not in edge channel
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1806672

Title:
  linux-azure: 4.15.0-1036.38~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:
  Confirmed
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 stakeholder-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-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 15:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress
security-signoff: Waiting for signoff
snap-release-to-beta: Snap not in beta channel
snap-release-to-edge: Snap not in edge channel
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806672/+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 1806673] Re: linux-gcp: 4.15.0-1026.27~16.04.1 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-xenial

** 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
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1806659
- phase: Packaging
- phase-changed: Friday, 07. December 2018 10:33 UTC
+ phase: Uploaded
+ phase-changed: Friday, 07. December 2018 15:37 UTC
  reason:
-   prepare-package-meta: Package not yet uploaded
-   prepare-package-signed: Package not yet uploaded
+   promote-to-proposed: Ready for review

-- 
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/1806673

Title:
  linux-gcp: 4.15.0-1026.27~16.04.1 -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:
  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:
  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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
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:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Uploaded
  phase-changed: Friday, 07. December 2018 15:37 UTC
  reason:
promote-to-proposed: Ready for review

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806673/+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 1807406] Status changed to Confirmed

[Ubuntu Kernel Bot]

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/1807406

Title:
  hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from
  ISHTP device

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Message after returning from suspension

  dmesg:
  [13383.967611] hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for 
response from ISHTP device
  [13383.967615] hid-sensor-hub 001F:8086:22D8.0002: timeout waiting for 
response from ISHTP device

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-8-generic 4.19.0-8.9
  ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6
  Uname: Linux 4.19.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2769 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  7 12:02:26 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.19.0-8-generic N/A
   linux-backports-modules-4.19.0-8-generic  N/A
   linux-firmware1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807406/+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 1802481] Re: cryptsetup waits for zvol /dev/zvol/rpool/swap with no zpool imported during boot. Timing problem?

[Lars]

** Package changed: cryptsetup (Ubuntu) => zfs-linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802481

Title:
  cryptsetup waits for zvol /dev/zvol/rpool/swap with no zpool imported
  during boot. Timing problem?

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Hi,
  first of all: I don't know if it is a bug in cryptsetup-initramfs or 
zfs-initramfs or another one.

  The problem is that since my upgrade from bionic to cosmic the
  cryptsetup tries too early to setup my cryptswap device which is on a
  zvol.

cryptsetup: Waiting for encrypted source device /dev/zvol/rpool/swap...
 ALERT! encrypted source device /dev/zvol/rpool/swap does not exist, 
can't unlock cryptswap1.
...

  After timeout I find myself in a initramfs-shell (initramfs).
  When I do zpool list there is no zpool importet.
  After

zpool import -N rpool
^D

  the cryptsetup succeeds.
  Greetings,

 Lars

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: cryptsetup-initramfs 2:2.0.4-2ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov  9 10:01:19 2018
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.logrotate.d.apport: [modified]
  mtime.conffile..etc.default.apport: 2015-03-15T20:01:19.851334
  mtime.conffile..etc.logrotate.d.apport: 2018-05-18T08:58:12.902005

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1802481/+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 1807408] Status changed to Confirmed

[Ubuntu Kernel Bot]

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/1807408

Title:
  usb 1-1.3: device descriptor read/64, error -11

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Message after returning from suspension

  dmesg:
  [13386.879710] usb 1-1.3: device descriptor read/64, error -110

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-8-generic 4.19.0-8.9
  ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6
  Uname: Linux 4.19.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2769 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  7 12:09:12 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.19.0-8-generic N/A
   linux-backports-modules-4.19.0-8-generic  N/A
   linux-firmware1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807408/+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 1807411] [NEW] VLAN stripping function will be called after running "ethtool -K rx off" to change the rx checksum setting

[Alex Wang]

Private bug reported:

check the ftrace ,it shows VLAN stripping setting was changed

Description of problem:
When running “ethtool –K rx off” for VF, the i40evf will also change the VLAN 
stripping setting unexpectedly. 
We tried to create a VF on Ubuntu18.04.1 in-tree i40e driver then ran "ethtool 
-K rx off" for it with the in-tree i40evf driver. The ftrace showed as below:

i40evf_set_features [i40evf] -> i40evf_enable_vlan_stripping
[i40evf]-> i40e_vlan_stripping_enable [i40e].

Version-Release number of selected component (if applicable):
RHEL7.6 Alpha kernel: 3.10.0-924.el7.x86_64
i40e driver: 2.1.14-k
i40evf driver: 3.0.1-k
ethtool version 4.15

repro steps and logs:

root@unassigned-hostname:~#  echo i40evf_set_features >> 
/sys/kernel/debug/tracing/set_graph_function
root@unassigned-hostname:~#  echo i40evf_enable_vlan_stripping >> 
/sys/kernel/debug/tracing/set_graph_function
root@unassigned-hostname:~#  echo 20 > /sys/kernel/debug/tracing/max_graph_depth
root@unassigned-hostname:~#  echo function_graph > 
/sys/kernel/debug/tracing/current_tracer
root@unassigned-hostname:~#  echo 1 > /sys/kernel/debug/tracing/tracing_on
root@unassigned-hostname:~#  cat /sys/kernel/debug/tracing/trace # tracer: 
function_graph #
# CPU  DURATION  FUNCTION CALLS
# | |   | |   |   |   |
root@unassigned-hostname:~#  ethtool -K enp175s2 rx off 
root@unassigned-hostname:~#  cat /sys/kernel/debug/tracing/trace # tracer: 
function_graph #
# CPU  DURATION  FUNCTION CALLS
# | |   | |   |   |   |
 60)   0.254 us|  i40evf_set_features [i40evf]();
 20)   |  i40evf_enable_vlan_stripping [i40evf]() {
 20)   |i40evf_send_pf_msg [i40evf]() {
 20)   |  i40e_aq_send_msg_to_pf [i40evf]() {
 20)   0.137 us|i40evf_fill_default_direct_cmd_desc [i40evf]();
 20)   |i40evf_asq_send_command [i40evf]() {
 20)   |  mutex_lock() {
 20)   |_cond_resched() {
 20)   0.144 us|  rcu_all_qs();
 20)   1.215 us|}
 20)   2.350 us|  }
 20)   0.145 us|  i40evf_debug_d [i40evf]();
 20)   0.105 us|  i40evf_debug_d [i40evf]();
 20)   0.148 us|  i40evf_debug_aq [i40evf]();
 20)   0.112 us|  i40evf_debug_d [i40evf]();
 20)   0.117 us|  i40evf_debug_aq [i40evf]();
 20)   0.163 us|  mutex_unlock();
 20) + 13.471 us   |}
 20) + 15.886 us   |  }
 20) + 17.167 us   |}
 20) + 18.831 us   |  }
 22)   |  i40e_vlan_stripping_enable [i40e]() {
 22)   |i40e_vlan_stripping_enable.part.86 [i40e]() {
 22)   |  i40e_aq_update_vsi_params [i40e]() {
 22)   0.172 us|i40e_fill_default_direct_cmd_desc [i40e]();
 22)   |i40e_asq_send_command [i40e]() {
 22)   |  mutex_lock() {
 22)   |_cond_resched() {
 22)   0.124 us|  rcu_all_qs();
 22)   1.183 us|}
 22)   2.220 us|  }
 22)   0.124 us|  i40e_debug_aq [i40e]();
 22) + 49.861 us   |  delay_tsc();
 22)   0.121 us|  i40e_debug_aq [i40e]();
 22)   0.113 us|  mutex_unlock();
 22) + 61.631 us   |}
 22) + 63.982 us   |  }
 22) + 65.264 us   |}
 22) + 66.720 us   |  }

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Information type changed from Public to Private

-- 
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/1807411

Title:
  VLAN stripping function will be called after running "ethtool -K rx
  off" to change the rx checksum setting

Status in linux package in Ubuntu:
  New

Bug description:
  check the ftrace ,it shows VLAN stripping setting was changed

  Description of problem:
  When running “ethtool –K rx off” for VF, the i40evf will also change the VLAN 
stripping setting unexpectedly. 
  We tried to create a VF on Ubuntu18.04.1 in-tree i40e driver then ran 
"ethtool -K rx off" for it with the in-tree i40evf driver. The ftrace showed as 
below:

  i40evf_set_features [i40evf] -> i40evf_enable_vlan_stripping
  [i40evf]-> i40e_vlan_stripping_enable [i40e].

  Version-Release number of selected component (if applicable):
  RHEL7.6 Alpha kernel: 3.10.0-924.el7.x86_64
  i40e driver: 2.1.14-k
  i40evf driver: 3.0.1-k
  ethtool version 4.15

  repro steps and logs:

  root@unassigned-hostname:~#  echo i40evf_set_features >> 
/sys/kernel/debug/tracing/set_graph_function
  root@unassigned-hostname:~#  echo i40evf_enable_vlan_stripping >> 
/sys/kernel/debug/tracing/set_graph_function
  root@unassigned-hostname:~#  echo 20 > 
/sys/kernel/debug/tracing/max_graph_depth
  root@unassigned-hostname:~#  echo function_graph > 
/sys/kernel/debu

[Kernel-packages] [Bug 1802481] [NEW] cryptsetup waits for zvol /dev/zvol/rpool/swap with no zpool imported during boot. Timing problem?

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hi,
first of all: I don't know if it is a bug in cryptsetup-initramfs or 
zfs-initramfs or another one.

The problem is that since my upgrade from bionic to cosmic the
cryptsetup tries too early to setup my cryptswap device which is on a
zvol.

  cryptsetup: Waiting for encrypted source device /dev/zvol/rpool/swap...
   ALERT! encrypted source device /dev/zvol/rpool/swap does not exist, 
can't unlock cryptswap1.
  ...
  
After timeout I find myself in a initramfs-shell (initramfs).
When I do zpool list there is no zpool importet.
After

  zpool import -N rpool
  ^D

the cryptsetup succeeds.
Greetings,

   Lars

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: cryptsetup-initramfs 2:2.0.4-2ubuntu2
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Nov  9 10:01:19 2018
EcryptfsInUse: Yes
PackageArchitecture: all
SourcePackage: cryptsetup
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport: [modified]
modified.conffile..etc.logrotate.d.apport: [modified]
mtime.conffile..etc.default.apport: 2015-03-15T20:01:19.851334
mtime.conffile..etc.logrotate.d.apport: 2018-05-18T08:58:12.902005

** Affects: zfs-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cosmic wayland-session
-- 
cryptsetup waits for zvol /dev/zvol/rpool/swap with no zpool imported during 
boot. Timing problem?
https://bugs.launchpad.net/bugs/1802481
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to zfs-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 1807406] [NEW] hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device

[Cristian Aravena Romero]

Public bug reported:

Hello,

Message after returning from suspension

dmesg:
[13383.967611] hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response 
from ISHTP device
[13383.967615] hid-sensor-hub 001F:8086:22D8.0002: timeout waiting for response 
from ISHTP device

Best regards,
--
Cristian Aravena Romero (caravena)

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-4.19.0-8-generic 4.19.0-8.9
ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6
Uname: Linux 4.19.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caravena   2769 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec  7 12:02:26 2018
HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
InstallationDate: Installed on 2018-12-02 (4 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.19.0-8-generic N/A
 linux-backports-modules-4.19.0-8-generic  N/A
 linux-firmware1.176
SourcePackage: linux
UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago)
dmi.bios.date: 06/14/2018
dmi.bios.vendor: Insyde
dmi.bios.version: F.13
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8486
dmi.board.vendor: HP
dmi.board.version: 72.19
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
dmi.product.sku: 3PX63LA#ABM
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: 3px63la amd64 apport-bug disco hp hp-pavilion-x360-14-cd0008la 
package-from-proposed wayland-session

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1807406

Title:
  hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from
  ISHTP device

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  Message after returning from suspension

  dmesg:
  [13383.967611] hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for 
response from ISHTP device
  [13383.967615] hid-sensor-hub 001F:8086:22D8.0002: timeout waiting for 
response from ISHTP device

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-8-generic 4.19.0-8.9
  ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6
  Uname: Linux 4.19.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2769 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  7 12:02:26 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.19.0-8-generic N/A
   linux-backports-modules-4.19.0-8-generic  N/A
   linux-firmware1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807406/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Un

[Kernel-packages] [Bug 1807408] [NEW] usb 1-1.3: device descriptor read/64, error -11

[Cristian Aravena Romero]

Public bug reported:

Hello,

Message after returning from suspension

dmesg:
[13386.879710] usb 1-1.3: device descriptor read/64, error -110

Best regards,
--
Cristian Aravena Romero (caravena)

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-4.19.0-8-generic 4.19.0-8.9
ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6
Uname: Linux 4.19.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caravena   2769 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec  7 12:09:12 2018
HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
InstallationDate: Installed on 2018-12-02 (4 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.19.0-8-generic N/A
 linux-backports-modules-4.19.0-8-generic  N/A
 linux-firmware1.176
SourcePackage: linux
UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago)
dmi.bios.date: 06/14/2018
dmi.bios.vendor: Insyde
dmi.bios.version: F.13
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8486
dmi.board.vendor: HP
dmi.board.version: 72.19
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
dmi.product.sku: 3PX63LA#ABM
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: 3px63la amd64 apport-bug disco hp hp-pavilion-x360-14-cd0008la 
package-from-proposed wayland-session

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1807408

Title:
  usb 1-1.3: device descriptor read/64, error -11

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  Message after returning from suspension

  dmesg:
  [13386.879710] usb 1-1.3: device descriptor read/64, error -110

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-8-generic 4.19.0-8.9
  ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6
  Uname: Linux 4.19.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2769 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  7 12:09:12 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.19.0-8-generic N/A
   linux-backports-modules-4.19.0-8-generic  N/A
   linux-firmware1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807408/+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 1806672] Re: linux-azure: 4.15.0-1036.38~16.04.1 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-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/snap-release-to-beta
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Fix Released

** 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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
- phase: Uploaded
- phase-changed: Friday, 07. December 2018 03:38 UTC
+ phase: Promoted to proposed
+ phase-changed: Friday, 07. December 2018 15:03 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Packages copies requested
+   automated-testing: Ready
+   regression-testing: Testing in progress
+   security-signoff: Waiting for signoff
+   snap-release-to-beta: Snap not in beta channel
+   snap-release-to-edge: Snap not in edge channel
+   stakeholder-signoff: Waiting for signoff
+   verification-testing: Testing in progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1806672

Title:
  linux-azure: 4.15.0-1036.38~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:
  Confirmed
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 stakeholder-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-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 15:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ready
regression-testing: Testing in progress
security-signoff: Waiting for signoff
snap-release-to-beta: Snap not in beta channel
snap-release-to-edge: Snap not in edge channel
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806672/+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 1807393] Re: nvme - Polling on timeout

[Guilherme G. Piccoli]

** Patch added: "TEST patch for qemu nvme virtual device"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807393/+attachment/5220068/+files/0001-hw-block-nvme-NVMe-hack-to-forcibly-miss-an-interrup.patch

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1807393

Title:
  nvme - Polling on timeout

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description to be updated

  [Impact]

   * 1

  [Test Case]

   * 2

  [Regression Potential]

   * 3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807393/+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 1639675] Re: [X555UB, Realtek ALC256, Speaker, Internal] No sound at all

[Sebastien Bacher]

The issue was fixed in the kernel
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/sound/pci/hda/patch_realtek.c?id=c1732ede5

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1639675

Title:
  [X555UB, Realtek ALC256, Speaker, Internal] No sound at all

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  On ubuntu 16.04 only mic does not work but now 16.10  sounds don`t
  play too

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrey 2177 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov  7 05:17:43 2016
  InstallationDate: Installed on 2016-11-07 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrey 2177 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [X555UB, Realtek ALC256, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UB.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UB.300:bd07/06/2016:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1639675/+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] 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

[Aroiu Ovidiu]

By the way, freebsd isn't booting eighter...

-- 
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:
  Fix Released
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 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

[Aroiu Ovidiu]

Please keep us up to date. Thanks!

-- 
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:
  Fix Released
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 1639675] [NEW] [X555UB, Realtek ALC256, Speaker, Internal] No sound at all

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

On ubuntu 16.04 only mic does not work but now 16.10  sounds don`t play
too

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  andrey 2177 F pulseaudio
CurrentDesktop: Unity
Date: Mon Nov  7 05:17:43 2016
InstallationDate: Installed on 2016-11-07 (0 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  andrey 2177 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [X555UB, Realtek ALC256, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/06/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X555UB.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X555UB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UB.300:bd07/06/2016:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X555UB
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: linux (Ubuntu)
 Importance: High
 Status: Fix Released


** Tags: amd64 apport-bug yakkety
-- 
[X555UB, Realtek ALC256, Speaker, Internal] No sound at all
https://bugs.launchpad.net/bugs/1639675
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 1791758] Re: ldisc crash on reopened tty

[Eric Desrochers]

** Also affects: linux (Ubuntu Cosmic)
   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/1791758

Title:
  ldisc crash on reopened tty

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  [Impact]

  The following Oops was discovered by user:

  [684766.39] BUG: unable to handle kernel paging request at 
2268
  [684766.667642] IP: [] n_tty_receive_buf_common+0x6a/0xae0
  [684766.668487] PGD 8019574fe067 PUD 19574ff067 PMD 0
  [684766.669194] Oops:  [#1] SMP
  [684766.669687] Modules linked in: xt_nat dccp_diag dccp tcp_diag udp_diag 
inet_diag unix_diag xt_connmark ipt_REJECT nf_reject_ipv4 nf_conntrack_netlink 
nfnetlink veth ip6table_filter ip6_tables xt_tcpmss xt_multiport xt_conntrack 
iptable_filter xt_CHECKSUM xt_tcpudp iptable_mangle xt_CT iptable_raw 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment iptable_nat ip_tables x_tables 
target_core_mod configfs softdog scini(POE) ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
openvswitch(OE) nf_nat_ipv6 nf_nat_ipv4 nf_nat gre kvm_intel kvm irqbypass ttm 
crct10dif_pclmul drm_kms_helper crc32_pclmul ghash_clmulni_intel drm 
aesni_intel aes_x86_64 i2c_piix4 lrw gf128mul fb_sys_fops syscopyarea 
glue_helper sysfillrect ablk_helper cryptd sysimgblt joydev
  [684766.679406]  input_leds mac_hid serio_raw 8250_fintek br_netfilter bridge 
stp llc nf_conntrack_proto_gre nf_conntrack_ipv6 nf_defrag_ipv6 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack xfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 psmouse multipath floppy pata_acpi linear dm_multipath
  [684766.683585] CPU: 15 PID: 7470 Comm: kworker/u40:1 Tainted: P   OE 
  4.4.0-124-generic #148~14.04.1-Ubuntu
  [684766.684967] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
  [684766.686062] Workqueue: events_unbound flush_to_ldisc
  [684766.686703] task: 88165e5d8000 ti: 88170dc2c000 task.ti: 
88170dc2c000
  [684766.687670] RIP: 0010:[]  [] 
n_tty_receive_buf_common+0x6a/0xae0
  [684766.688870] RSP: 0018:88170dc2fd28  EFLAGS: 00010202
  [684766.689521] RAX:  RBX: 88162c895000 RCX: 
0001
  [684766.690488] RDX:  RSI: 88162c895020 RDI: 
8819c2d3d4d8
  [684766.691518] RBP: 88170dc2fdc0 R08: 0001 R09: 
81ec2ba0
  [684766.692480] R10: 0004 R11:  R12: 
8819c2d3d400
  [684766.693423] R13: 8819c45b2670 R14: 8816a358c028 R15: 
8819c2d3d400
  [684766.694390] FS:  () GS:8819d73c() 
knlGS:
  [684766.695484] CS:  0010 DS:  ES:  CR0: 80050033
  [684766.696182] CR2: 2268 CR3: 00195752 CR4: 
00360670
  [684766.697141] DR0:  DR1:  DR2: 

  [684766.698114] DR3:  DR6: fffe0ff0 DR7: 
0400
  [684766.699079] Stack:
  [684766.699412]   8819c2d3d4d8  
8819c2d3d648
  [684766.700467]  8819c2d3d620 8819c9c10400 88170dc2fd68 
8106312e
  [684766.701501]  88170dc2fd78 0001  
88162c895020
  [684766.702534] Call Trace:
  [684766.702905]  [] ? kvm_sched_clock_read+0x1e/0x30
  [684766.703685]  [] n_tty_receive_buf2+0x14/0x20
  [684766.704505]  [] flush_to_ldisc+0xd5/0x120
  [684766.705269]  [] process_one_work+0x156/0x400
  [684766.706008]  [] worker_thread+0x11a/0x480
  [684766.706686]  [] ? rescuer_thread+0x310/0x310
  [684766.707386]  [] kthread+0xd8/0xf0
  [684766.707993]  [] ? kthread_park+0x60/0x60
  [684766.708664]  [] ret_from_fork+0x55/0x80
  [684766.709335]  [] ? kthread_park+0x60/0x60
  [684766.709998] Code: 85 70 ff ff ff e8 97 5f 33 00 49 8d 87 20 02 00 00 c7 
45 b4 00 00 00 00 48 89 45 88 49 8d 87 48 02 00 00 48 89 45 80 48 8b 45 b8 <48> 
8b b0 68 22 00 00 48 8b 08 89 f0 29 c8 41 f6 87 30 01 00 00
  [684766.713290] RIP  [] n_tty_receive_buf_common+0x6a/0xae0
  [684766.714105]  RSP 
  [684766.714609] CR2: 2268

  The issue happened in a VM
  KDUMP was configured, so a full Kernel crashdump was created

  User has Ubuntu Trusty, Kernel 4.4.0-124 on its VM

  [Test Case]

  * Deploy a Trusty KVM instance with a LTS Xenial kernel (v4.4 series)
  * SSH in frequently while system is under load, send commands before the 
prompt has returned.
  

  Check comment #5 for a summary about the upstream proposals to resolve
  this issue.

To manage notificati

[Kernel-packages] [Bug 1791758] Re: ldisc crash on reopened tty

[Guilherme G. Piccoli]

** Changed in: linux (Ubuntu Cosmic)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Cosmic)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

-- 
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/1791758

Title:
  ldisc crash on reopened tty

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  [Impact]

  The following Oops was discovered by user:

  [684766.39] BUG: unable to handle kernel paging request at 
2268
  [684766.667642] IP: [] n_tty_receive_buf_common+0x6a/0xae0
  [684766.668487] PGD 8019574fe067 PUD 19574ff067 PMD 0
  [684766.669194] Oops:  [#1] SMP
  [684766.669687] Modules linked in: xt_nat dccp_diag dccp tcp_diag udp_diag 
inet_diag unix_diag xt_connmark ipt_REJECT nf_reject_ipv4 nf_conntrack_netlink 
nfnetlink veth ip6table_filter ip6_tables xt_tcpmss xt_multiport xt_conntrack 
iptable_filter xt_CHECKSUM xt_tcpudp iptable_mangle xt_CT iptable_raw 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment iptable_nat ip_tables x_tables 
target_core_mod configfs softdog scini(POE) ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
openvswitch(OE) nf_nat_ipv6 nf_nat_ipv4 nf_nat gre kvm_intel kvm irqbypass ttm 
crct10dif_pclmul drm_kms_helper crc32_pclmul ghash_clmulni_intel drm 
aesni_intel aes_x86_64 i2c_piix4 lrw gf128mul fb_sys_fops syscopyarea 
glue_helper sysfillrect ablk_helper cryptd sysimgblt joydev
  [684766.679406]  input_leds mac_hid serio_raw 8250_fintek br_netfilter bridge 
stp llc nf_conntrack_proto_gre nf_conntrack_ipv6 nf_defrag_ipv6 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack xfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 psmouse multipath floppy pata_acpi linear dm_multipath
  [684766.683585] CPU: 15 PID: 7470 Comm: kworker/u40:1 Tainted: P   OE 
  4.4.0-124-generic #148~14.04.1-Ubuntu
  [684766.684967] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
  [684766.686062] Workqueue: events_unbound flush_to_ldisc
  [684766.686703] task: 88165e5d8000 ti: 88170dc2c000 task.ti: 
88170dc2c000
  [684766.687670] RIP: 0010:[]  [] 
n_tty_receive_buf_common+0x6a/0xae0
  [684766.688870] RSP: 0018:88170dc2fd28  EFLAGS: 00010202
  [684766.689521] RAX:  RBX: 88162c895000 RCX: 
0001
  [684766.690488] RDX:  RSI: 88162c895020 RDI: 
8819c2d3d4d8
  [684766.691518] RBP: 88170dc2fdc0 R08: 0001 R09: 
81ec2ba0
  [684766.692480] R10: 0004 R11:  R12: 
8819c2d3d400
  [684766.693423] R13: 8819c45b2670 R14: 8816a358c028 R15: 
8819c2d3d400
  [684766.694390] FS:  () GS:8819d73c() 
knlGS:
  [684766.695484] CS:  0010 DS:  ES:  CR0: 80050033
  [684766.696182] CR2: 2268 CR3: 00195752 CR4: 
00360670
  [684766.697141] DR0:  DR1:  DR2: 

  [684766.698114] DR3:  DR6: fffe0ff0 DR7: 
0400
  [684766.699079] Stack:
  [684766.699412]   8819c2d3d4d8  
8819c2d3d648
  [684766.700467]  8819c2d3d620 8819c9c10400 88170dc2fd68 
8106312e
  [684766.701501]  88170dc2fd78 0001  
88162c895020
  [684766.702534] Call Trace:
  [684766.702905]  [] ? kvm_sched_clock_read+0x1e/0x30
  [684766.703685]  [] n_tty_receive_buf2+0x14/0x20
  [684766.704505]  [] flush_to_ldisc+0xd5/0x120
  [684766.705269]  [] process_one_work+0x156/0x400
  [684766.706008]  [] worker_thread+0x11a/0x480
  [684766.706686]  [] ? rescuer_thread+0x310/0x310
  [684766.707386]  [] kthread+0xd8/0xf0
  [684766.707993]  [] ? kthread_park+0x60/0x60
  [684766.708664]  [] ret_from_fork+0x55/0x80
  [684766.709335]  [] ? kthread_park+0x60/0x60
  [684766.709998] Code: 85 70 ff ff ff e8 97 5f 33 00 49 8d 87 20 02 00 00 c7 
45 b4 00 00 00 00 48 89 45 88 49 8d 87 48 02 00 00 48 89 45 80 48 8b 45 b8 <48> 
8b b0 68 22 00 00 48 8b 08 89 f0 29 c8 41 f6 87 30 01 00 00
  [684766.713290] RIP  [] n_tty_receive_buf_common+0x6a/0xae0
  [684766.714105]  RSP 
  [684766.714609] CR2: 2268

  The issue happened in a VM
  KDUMP was configured, so a full Kernel crashdump was created

  User has Ubuntu Trusty, Kernel 4.4.0-124 on its VM

  [Test Case]

  * Deploy a Trusty KVM instance with a LTS Xenial kernel (v4.4 series)
  * SSH in frequently while system is under load, send commands before the 
prompt has returned.
  

  Check comment #5 fo

[Kernel-packages] [Bug 1791758] Re: ldisc crash on reopened tty

[Guilherme G. Piccoli]

There's news - a V6 patchset was proposed recently, that address this issue
and there are good chances to get merged: 
https://marc.info/?l=linux-kernel&m=154103190111795
("[PATCHv6 0/7] tty: Hold write ldisc sem in tty_reopen()").

Will update here with SRU request when it gets merged.

Cheers,


Guilherme

-- 
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/1791758

Title:
  ldisc crash on reopened tty

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  [Impact]

  The following Oops was discovered by user:

  [684766.39] BUG: unable to handle kernel paging request at 
2268
  [684766.667642] IP: [] n_tty_receive_buf_common+0x6a/0xae0
  [684766.668487] PGD 8019574fe067 PUD 19574ff067 PMD 0
  [684766.669194] Oops:  [#1] SMP
  [684766.669687] Modules linked in: xt_nat dccp_diag dccp tcp_diag udp_diag 
inet_diag unix_diag xt_connmark ipt_REJECT nf_reject_ipv4 nf_conntrack_netlink 
nfnetlink veth ip6table_filter ip6_tables xt_tcpmss xt_multiport xt_conntrack 
iptable_filter xt_CHECKSUM xt_tcpudp iptable_mangle xt_CT iptable_raw 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment iptable_nat ip_tables x_tables 
target_core_mod configfs softdog scini(POE) ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
openvswitch(OE) nf_nat_ipv6 nf_nat_ipv4 nf_nat gre kvm_intel kvm irqbypass ttm 
crct10dif_pclmul drm_kms_helper crc32_pclmul ghash_clmulni_intel drm 
aesni_intel aes_x86_64 i2c_piix4 lrw gf128mul fb_sys_fops syscopyarea 
glue_helper sysfillrect ablk_helper cryptd sysimgblt joydev
  [684766.679406]  input_leds mac_hid serio_raw 8250_fintek br_netfilter bridge 
stp llc nf_conntrack_proto_gre nf_conntrack_ipv6 nf_defrag_ipv6 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack xfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 psmouse multipath floppy pata_acpi linear dm_multipath
  [684766.683585] CPU: 15 PID: 7470 Comm: kworker/u40:1 Tainted: P   OE 
  4.4.0-124-generic #148~14.04.1-Ubuntu
  [684766.684967] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
  [684766.686062] Workqueue: events_unbound flush_to_ldisc
  [684766.686703] task: 88165e5d8000 ti: 88170dc2c000 task.ti: 
88170dc2c000
  [684766.687670] RIP: 0010:[]  [] 
n_tty_receive_buf_common+0x6a/0xae0
  [684766.688870] RSP: 0018:88170dc2fd28  EFLAGS: 00010202
  [684766.689521] RAX:  RBX: 88162c895000 RCX: 
0001
  [684766.690488] RDX:  RSI: 88162c895020 RDI: 
8819c2d3d4d8
  [684766.691518] RBP: 88170dc2fdc0 R08: 0001 R09: 
81ec2ba0
  [684766.692480] R10: 0004 R11:  R12: 
8819c2d3d400
  [684766.693423] R13: 8819c45b2670 R14: 8816a358c028 R15: 
8819c2d3d400
  [684766.694390] FS:  () GS:8819d73c() 
knlGS:
  [684766.695484] CS:  0010 DS:  ES:  CR0: 80050033
  [684766.696182] CR2: 2268 CR3: 00195752 CR4: 
00360670
  [684766.697141] DR0:  DR1:  DR2: 

  [684766.698114] DR3:  DR6: fffe0ff0 DR7: 
0400
  [684766.699079] Stack:
  [684766.699412]   8819c2d3d4d8  
8819c2d3d648
  [684766.700467]  8819c2d3d620 8819c9c10400 88170dc2fd68 
8106312e
  [684766.701501]  88170dc2fd78 0001  
88162c895020
  [684766.702534] Call Trace:
  [684766.702905]  [] ? kvm_sched_clock_read+0x1e/0x30
  [684766.703685]  [] n_tty_receive_buf2+0x14/0x20
  [684766.704505]  [] flush_to_ldisc+0xd5/0x120
  [684766.705269]  [] process_one_work+0x156/0x400
  [684766.706008]  [] worker_thread+0x11a/0x480
  [684766.706686]  [] ? rescuer_thread+0x310/0x310
  [684766.707386]  [] kthread+0xd8/0xf0
  [684766.707993]  [] ? kthread_park+0x60/0x60
  [684766.708664]  [] ret_from_fork+0x55/0x80
  [684766.709335]  [] ? kthread_park+0x60/0x60
  [684766.709998] Code: 85 70 ff ff ff e8 97 5f 33 00 49 8d 87 20 02 00 00 c7 
45 b4 00 00 00 00 48 89 45 88 49 8d 87 48 02 00 00 48 89 45 80 48 8b 45 b8 <48> 
8b b0 68 22 00 00 48 8b 08 89 f0 29 c8 41 f6 87 30 01 00 00
  [684766.713290] RIP  [] n_tty_receive_buf_common+0x6a/0xae0
  [684766.714105]  RSP 
  [684766.714609] CR2: 2268

  The issue happened in a VM
  KDUMP was configured, so a full Kernel crashdump was created

  User has Ubuntu Trusty, Kernel 4.4.0-124 on its VM

  [Test Case]

  * Deploy a Trusty KVM instance with a LTS Xenial kernel (

[Kernel-packages] [Bug 1807388] Re: Issue with wifi on 4.18.0-12-generic

[Chris A Moody]

Wifi card: 
06:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 
802.11a/b/g/n/ac WiFi adapter [10ec:b822]
Subsystem: Hewlett-Packard Company RTL8822BE 802.11a/b/g/n/ac WiFi 
adapter [103c:831b]
Kernel driver in use: r8822be
Kernel modules: r8822be

-- 
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/1807388

Title:
  Issue with wifi on  4.18.0-12-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My system has a built in WiFi card, and I've found that under
  4.18.0-10-generic its detected and works with out issue out of the
  box. However Under  4.18.0-12-generic the wifi card is not seen in the
  system via the gui.

  lspci still shows it there though.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  chris  2810 F pulseaudio
   /dev/snd/controlC1:  chris  2810 F pulseaudio
   /dev/snd/controlC0:  chris  2810 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  7 07:55:16 2018
  InstallationDate: Installed on 2018-12-04 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: HP OMEN by HP Desktop PC 880-p0xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=7a680d02-7ca0-4406-a1ef-32880d15ef42 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  StagingDrivers: r8822be
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2017
  dmi.bios.vendor: AMI
  dmi.bios.version: F.10
  dmi.board.name: 8309
  dmi.board.vendor: HP
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.10:bd11/15/2017:svnHP:pnOMENbyHPDesktopPC880-p0xx:pvr:rvnHP:rn8309:rvr1.0:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53311M HP Omen
  dmi.product.name: OMEN by HP Desktop PC 880-p0xx
  dmi.product.sku: Z5P63AA#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807388/+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 1803929] Re: Summary: Kernel bug (unhandled paging request) on "udisksctl power-off"

[David Jao]

I built 4.4.0-141.167 with the one-line patch from
https://www.spinics.net/lists/linux-usb/msg168861.html and it does
indeed fix this problem.

-- 
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/1803929

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803929/+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 1807393] [NEW] nvme - Polling on timeout

[Guilherme G. Piccoli]

Public bug reported:

Description to be updated

[Impact]

 * 1

[Test Case]

 * 2

[Regression Potential]

 * 3

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: Confirmed


** Tags: sts

-- 
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/1807393

Title:
  nvme - Polling on timeout

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description to be updated

  [Impact]

   * 1

  [Test Case]

   * 2

  [Regression Potential]

   * 3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807393/+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 1807388] Status changed to Confirmed

[Ubuntu Kernel Bot]

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/1807388

Title:
  Issue with wifi on  4.18.0-12-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My system has a built in WiFi card, and I've found that under
  4.18.0-10-generic its detected and works with out issue out of the
  box. However Under  4.18.0-12-generic the wifi card is not seen in the
  system via the gui.

  lspci still shows it there though.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  chris  2810 F pulseaudio
   /dev/snd/controlC1:  chris  2810 F pulseaudio
   /dev/snd/controlC0:  chris  2810 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  7 07:55:16 2018
  InstallationDate: Installed on 2018-12-04 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: HP OMEN by HP Desktop PC 880-p0xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=7a680d02-7ca0-4406-a1ef-32880d15ef42 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  StagingDrivers: r8822be
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2017
  dmi.bios.vendor: AMI
  dmi.bios.version: F.10
  dmi.board.name: 8309
  dmi.board.vendor: HP
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.10:bd11/15/2017:svnHP:pnOMENbyHPDesktopPC880-p0xx:pvr:rvnHP:rn8309:rvr1.0:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53311M HP Omen
  dmi.product.name: OMEN by HP Desktop PC 880-p0xx
  dmi.product.sku: Z5P63AA#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807388/+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 1806666] Re: linux-gcp: 4.15.0-1026.27 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Incomplete

** Changed in: kernel-sru-workflow/security-signoff
   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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 11:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Testing in progress
+   automated-testing: Testing FAILED
promote-to-updates: Nvidia GCP object not found -- 4.15.0-1026
regression-testing: Testing in progress
+   security-signoff: Waiting for signoff
snap-release-to-beta: Snap not in 18/beta channel
snap-release-to-edge: Snap not in 18/edge channel
verification-testing: Testing in progress

-- 
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/180

Title:
  linux-gcp: 4.15.0-1026.27 -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 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:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 11:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
promote-to-updates: Nvidia GCP object not found -- 4.15.0-1026
regression-testing: Testing in progress
security-signoff: Waiting for signoff
snap-release-to-beta: Snap not in 18/beta channel
snap-release-to-edge: Snap not in 18/edge channel
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/180/+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 1807388] [NEW] Issue with wifi on 4.18.0-12-generic

[Chris A Moody]

Public bug reported:

My system has a built in WiFi card, and I've found that under
4.18.0-10-generic its detected and works with out issue out of the box.
However Under  4.18.0-12-generic the wifi card is not seen in the system
via the gui.

lspci still shows it there though.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-10-generic 4.18.0-10.11
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  chris  2810 F pulseaudio
 /dev/snd/controlC1:  chris  2810 F pulseaudio
 /dev/snd/controlC0:  chris  2810 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec  7 07:55:16 2018
InstallationDate: Installed on 2018-12-04 (2 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: HP OMEN by HP Desktop PC 880-p0xx
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=7a680d02-7ca0-4406-a1ef-32880d15ef42 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-10-generic N/A
 linux-backports-modules-4.18.0-10-generic  N/A
 linux-firmware 1.175.1
SourcePackage: linux
StagingDrivers: r8822be
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2017
dmi.bios.vendor: AMI
dmi.bios.version: F.10
dmi.board.name: 8309
dmi.board.vendor: HP
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnAMI:bvrF.10:bd11/15/2017:svnHP:pnOMENbyHPDesktopPC880-p0xx:pvr:rvnHP:rn8309:rvr1.0:cvnHP:ct3:cvr:
dmi.product.family: 103C_53311M HP Omen
dmi.product.name: OMEN by HP Desktop PC 880-p0xx
dmi.product.sku: Z5P63AA#ABA
dmi.sys.vendor: HP

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cosmic staging

-- 
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/1807388

Title:
  Issue with wifi on  4.18.0-12-generic

Status in linux package in Ubuntu:
  New

Bug description:
  My system has a built in WiFi card, and I've found that under
  4.18.0-10-generic its detected and works with out issue out of the
  box. However Under  4.18.0-12-generic the wifi card is not seen in the
  system via the gui.

  lspci still shows it there though.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  chris  2810 F pulseaudio
   /dev/snd/controlC1:  chris  2810 F pulseaudio
   /dev/snd/controlC0:  chris  2810 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  7 07:55:16 2018
  InstallationDate: Installed on 2018-12-04 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: HP OMEN by HP Desktop PC 880-p0xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=7a680d02-7ca0-4406-a1ef-32880d15ef42 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  StagingDrivers: r8822be
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2017
  dmi.bios.vendor: AMI
  dmi.bios.version: F.10
  dmi.board.name: 8309
  dmi.board.vendor: HP
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.10:bd11/15/2017:svnHP:pnOMENbyHPDesktopPC880-p0xx:pvr:rvnHP:rn8309:rvr1.0:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53311M HP Omen
  dmi.product.name: OMEN by HP Desktop PC 880-p0xx
  dmi.product.sku: Z5P63AA#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807388/+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 1803929] Re: Summary: Kernel bug (unhandled paging request) on "udisksctl power-off"

[Norbert]

Went to this problem on 139 and 140 kernels.
Safely remove of USB3 drive freezes the system completely.
I was very lucky that I have saved all documents before the freeze.

The temporary solution is to use 138 ( 4.4.0-138-generic ) kernel.

Please fix this bug as soon as possible.

-- 
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/1803929

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803929/+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 1807375] Re: Bluetooth: hci0: RTL: rtl: unknown IC info, lmp subver a99e, hci rev 826c, hci ver 0008

[Bug Watch Updater]

Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=201921.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-12-07T11:43:32+00:00 caravena wrote:

Hello,

Open bug in launchpad.net
https://bugs.launchpad.net/bugs/1807375

dmesg:
Bluetooth: hci0: RTL: rtl: unknown IC info, lmp subver a99e, hci rev 826c, hci 
ver 0008

Best regards,
--
Cristian Aravena Romero (caravena)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807375/comments/2


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => 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/1807375

Title:
  Bluetooth: hci0: RTL: rtl: unknown IC info, lmp subver a99e, hci rev
  826c, hci ver 0008

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  dmesg:
  [   13.388386] Bluetooth: hci0: RTL: rtl: unknown IC info, lmp subver a99e, 
hci rev 826c, hci ver 0008

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-8-generic 4.19.0-8.9
  ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6
  Uname: Linux 4.19.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2769 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   2769 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  7 08:30:39 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.19.0-8-generic N/A
   linux-backports-modules-4.19.0-8-generic  N/A
   linux-firmware1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1807375/+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 1806659] Re: linux: 4.15.0-43.46 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Incomplete

** 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: bug 1806670 (linux-azure), bug 1806671 (linux-aws-hwe), bug 
1806672 (linux-azure), bug 1806673 (linux-gcp), bug 1806674 (linux-hwe), bug 
1806675 (linux-hwe-edge)
  derivatives: bug 1806661 (linux-raspi2), bug 1806663 (linux-oem), bug 1806664 
(linux-aws), bug 1806665 (linux-azure), bug 180 (linux-gcp), bug 1806667 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 12:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Testing in progress
+   automated-testing: Testing FAILED
certification-testing: Testing in progress
regression-testing: Testing in progress
security-signoff: Waiting for signoff
snap-release-to-beta: Snap not in 18/beta channel
snap-release-to-edge: Snap not in 18/edge channel
verification-testing: Testing 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/1806659

Title:
  linux: 4.15.0-43.46 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1806670 (linux-azure), bug 1806671 (linux-aws-hwe), bug 
1806672 (linux-azure), bug 1806673 (linux-gcp), bug 1806674 (linux-hwe), bug 
1806675 (linux-hwe-edge)
  derivatives: bug 1806661 (linux-raspi2), bug 1806663 (linux-oem), bug 1806664 
(linux-aws), bug 1806665 (linux-azure), bug 180 (linux-gcp), bug 1806667 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 12:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
certification-testing: Testing in progress
regression-testing: Testing in progress
security-signoff: Waiting for signoff
snap-release-to-beta: Snap not in 18/beta channel
snap-release-to-edge: Snap not in 18/edge channel
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806659/+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 1458204] Re: removing kernels should not require a restart afterward

[Timo Aaltonen]

Hello Daniel, or anyone else affected,

Accepted update-notifier into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/update-
notifier/3.168.10 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: update-notifier (Ubuntu Xenial)
   Status: New => 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/1458204

Title:
  removing kernels should not require a restart afterward

Status in unattended-upgrades:
  New
Status in update notifier:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in update-notifier source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Won't Fix
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in update-notifier source package in Artful:
  Won't Fix

Bug description:
  [Impact]

  The rationale behind the SRU to Xenial is that with latest unattended-
  upgrades SRU it starts removing unused kernels, but all older kernels
  are not removed in a single run. With update-notifier and u-u not
  fixed they place /var/run/reboot-required asking for a reboot when it
  is not needed.

  
  [Test Case]

  1. Perform a kernel upgrade normally via "apt-get dist-upgrade".
  2. Reboot.
  3. Run "apt-get autoremove" to delete the old kernel packages.
  4. "System Notification Helper" now reports that the computer requires a 
reboot.

  The "autoremove" operation shouldn't require a reboot, logically
  speaking, because it's just removing files that are unused by the OS.

  [ Regression Potential ]

  If the check for skipping placing the /var/run/reboot-required file is too 
broad it may make kernel upgrades fail to ask for reboot. The fix changes a 
hook called by maintainer scripts and a failure in the hook can make kernel 
package installations fail.
  The fix is simple and was tested in several releases thus regressing in these 
ways is unlikely.

  [ Original Bug Text ]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat May 23 12:47:15 2015
  InstallationDate: Installed on 2013-08-31 (629 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago)
  ---
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308
  InstallationDate: Installed on 2013-08-31 (632 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-53-generic N/A
   linux-backports-modules-3.13.0-53-generic  N/A
   linux-firmware 1.127.12
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago)
  UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo
  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 08/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4210
  dmi.board.asset.tag: To be filled by O.E.M.
  

[Kernel-packages] [Bug 1803929] Re: Summary: Kernel bug (unhandled paging request) on "udisksctl power-off"

[Norbert]

Temporary fixed on my system with hacky way:

sudo rm /boot/*139*
sudo rm /boot/*140*
sudo update-grub
sudo reboot

But still waiting for official update.

-- 
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/1803929

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803929/+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 1807377] Re: i2c_hid i2c-ELAN2514:00: failed to change power setting.

[Bug Watch Updater]

Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=201923.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-12-07T11:46:23+00:00 caravena wrote:

Hello,

Open bug in launchpad.net
https://bugs.launchpad.net/bugs/1807377

dmesg:
i2c_hid i2c-ELAN2514:00: failed to change power setting.

Best regards,
--
Cristian Aravena Romero (caravena)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807377/comments/2


** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => 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/1807377

Title:
  i2c_hid i2c-ELAN2514:00: failed to change power setting.

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  dmesg:
  [1.862577] i2c_hid i2c-ELAN2514:00: failed to change power setting.

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-8-generic 4.19.0-8.9
  ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6
  Uname: Linux 4.19.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2769 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   2769 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  7 08:35:57 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.19.0-8-generic N/A
   linux-backports-modules-4.19.0-8-generic  N/A
   linux-firmware1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1807377/+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 1805195] Re: linux: 4.19.0-6.7 -proposed tracker

[Seth Forshee]

*** This bug is a duplicate of bug 1806952 ***
https://bugs.launchpad.net/bugs/1806952

** This bug is no longer a duplicate of bug 1805465
   linux: 4.19.0-7.8 -proposed tracker
** This bug has been marked a duplicate of bug 1806952
   linux: 4.19.0-8.9 -proposed tracker

-- 
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/1805195

Title:
  linux: 4.19.0-6.7 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 
  derivatives:
  -- swm properties --
  reason:
prepare-package: Package not yet uploaded
prepare-package-meta: Package not yet uploaded
prepare-package-signed: Package not yet uploaded
promote-to-release: Testing not complete

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805195/+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 1802283] Re: system freezes

[jnns]

So far today, the laptop hasn't crashed completely but Firefox and
Thundebird are crashing constantly making it impossible to get work
done. As soon as I restore the crashed Firefox session the whole program
crashes again.

I attached that part of syslog of the last hour.

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802283/+attachment/5220026/+files/syslog

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802283

Title:
  system freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My system freezes once every second day or so.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jnns   2519 F pulseaudio
   /dev/snd/controlC0:  jnns   2519 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Nov  8 12:07:32 2018
  HibernationDevice: RESUME=UUID=18edd09d-0a58-4464-accb-11ff57fc4327
  InstallationDate: Installed on 2018-08-05 (95 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KGS5DU00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-10 (29 days ago)
  dmi.bios.date: 09/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KGS5DU00
  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:bvrN23ET56W(1.31):bd09/17/2018:svnLENOVO:pn20KGS5DU00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS5DU00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KGS5DU00
  dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802283/+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 1805465] Re: linux: 4.19.0-7.8 -proposed tracker

[Seth Forshee]

*** This bug is a duplicate of bug 1806952 ***
https://bugs.launchpad.net/bugs/1806952

** This bug has been marked a duplicate of bug 1806952
   linux: 4.19.0-8.9 -proposed tracker

-- 
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/1805465

Title:
  linux: 4.19.0-7.8 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
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-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 
  derivatives:
  -- swm properties --
  phase: Promoted to proposed
  phase-changed: Friday, 30. November 2018 15:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
regression-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805465/+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 1770256] Re: linux packages should own /usr/lib/linux/triggers

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1770256

Title:
  linux packages should own /usr/lib/linux/triggers

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  In Progress

Bug description:
  Rather than randomly mkdir/rmdir'ing /usr/lib/linux/triggers all of
  the binary packages that use triggers should contain this directory.
  This will allow dpkg to reference count the directory and detect left
  over files correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770256/+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 1774359] Re: could not find module by name='off'

[Matthias]

Same problem here, with Ubuntu 18.04, Nvidia drivers 410.
After commenting the following lines:

#alias nvidia off
#alias nvidia-drm off
#alias nvidia-modeset off

either in /usr/bin/prime-select (as suggested above) or directly in
/lib/modprobe.d/blacklist-nvidia.conf I can load the driver, however,
that also leads to crashing my system (as described by Vladislav
Dalechin.

Any news on this?

-- 
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/1774359

Title:
  could not find module by name='off'

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  When I try to load the nvidia module it doesn't load.

  $ sudo modprobe nvidia
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
  $ sudo prime-select query
  intel
  $ sudo prime-offload
  $ cat /var/log/prime-supported.log 
  Requires offloading 
  $ cat /var/log/prime-offload.log 
  Sorry the nvidia kernel module is not is loaded

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-kernel-common-390 390.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 31 09:42:42 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-05-30 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1774359/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1803942] Re: System randomly hangs during suspend when mei_wdt is loaded

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1803942

Title:
  System randomly hangs during suspend when mei_wdt is loaded

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Problem description:
  System randomly hangs during suspend when mei_wdt is loaded.

  Platform:
  Intel Dawson Canyon I5 (NUC7i5DNHE) and I7 (NUC7i7DNHE)

  Test procedure:
  1. Install Ubuntu 18.04 and do apt full-upgrade

  2. Enable mei_wdt:
  $ sudo modprobe mei_wdt

  3. Do system S3 test:
  $ sudo systemctl suspend
  or
  $ sudo rtcwake -v -m mem -s 15

  4. Afterward, I noticed that somehow system will hang during
  suspend/resume.

  Expect result:
  Suspend/resume won't impact system.

  Actual result:
  System will hang during S3 test.

  Additional info:
  - BIOS version: V57
  - Another i3 platform (NUC7i3DNHNC) doesn't have this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1803942/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1806380] Re: linux-buildinfo: pull out ABI information into its own package

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1806380

Title:
  linux-buildinfo: pull out ABI information into its own package

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  In Progress

Bug description:
  We have an increasing amount of ABI information which is currently
  exposed via the primary binary packages.  Little to none of this is
  relevant to the end-user and does not deserve to use up space on their
  system.  Also the kernel developer who needs to update this data does
  not want to downloads 10s of Megabytes of binary packages to extract
  this information.  Pull it all out and generate all data that would
  require the actual binaries at kernel build time, package all of this
  information into a new linux-buildinfo package for consumption.  This
  package is not installed by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806380/+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 1806664] Re: linux-aws: 4.15.0-1031.33 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-bionic

** 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
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Uploaded
  phase-changed: Friday, 07. December 2018 10:08 UTC
  reason:
-   promote-to-proposed: Builds not complete
+   promote-to-proposed: Ready for review

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1806664

Title:
  linux-aws: 4.15.0-1031.33 -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:
  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:
  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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
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:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Uploaded
  phase-changed: Friday, 07. December 2018 10:08 UTC
  reason:
promote-to-proposed: Ready for review

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806664/+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 1806659] Re: linux: 4.15.0-43.46 -proposed tracker

[Brad Figg]

** 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/snap-release-to-beta
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-edge
   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: bug 1806670 (linux-azure), bug 1806671 (linux-aws-hwe), bug 
1806672 (linux-azure), bug 1806673 (linux-gcp), bug 1806674 (linux-hwe), bug 
1806675 (linux-hwe-edge)
  derivatives: bug 1806661 (linux-raspi2), bug 1806663 (linux-oem), bug 1806664 
(linux-aws), bug 1806665 (linux-azure), bug 180 (linux-gcp), bug 1806667 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- phase-changed: Thursday, 06. December 2018 15:02 UTC
+ bugs-spammed: true
+ phase: Promoted to proposed
+ phase-changed: Friday, 07. December 2018 12:36 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Packages waiting in -proposed for mirror sync
+   automated-testing: Testing in progress
+   certification-testing: Testing in progress
+   regression-testing: Testing in progress
+   security-signoff: Waiting for signoff
+   snap-release-to-beta: Snap not in 18/beta channel
+   snap-release-to-edge: Snap not in 18/edge channel
+   verification-testing: Testing 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/1806659

Title:
  linux: 4.15.0-43.46 -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-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:
  Confirmed
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1806670 (linux-azure), bug 1806671 (linux-aws-hwe), bug 
1806672 (linux-azure), bug 1806673 (linux-gcp), bug 1806674 (linux-hwe), bug 
1806675 (linux-hwe-edge)
  derivatives: bug 1806661 (linux-raspi2), bug 1806663 (linux-oem), bug 1806664 
(linux-aws), bug 1806665 (linux-azure), bug 180 (linux-gcp), bug 1806667 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 12:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing in progress
certification-testing: Testing in progress
regression-testing: Testing in progress
security-signoff: Waiting for signoff
snap-release-to-beta: Snap not in 18/beta channel
snap-release-to-edge: Snap not in 18/edge channel
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806659/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : ht

[Kernel-packages] [Bug 1806670] Re: linux-azure: 4.15.0-1036.38~14.04.2 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/security-signoff
   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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 11:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Testing in progress
regression-testing: Testing in progress
+   security-signoff: Waiting for signoff
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1806670

Title:
  linux-azure: 4.15.0-1036.38~14.04.2 -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:
  Confirmed
Status in Kernel SRU Workflow stakeholder-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-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 11:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Testing in progress
security-signoff: Waiting for signoff
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806670/+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 1806838] Re: Workaround CSS timeout on AMD SNPS 3.0 xHC

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

-- 
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/1806838

Title:
  Workaround CSS timeout on AMD SNPS 3.0 xHC

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  New
Status in linux source package in Cosmic:
  Fix Committed
Status in linux-oem source package in Cosmic:
  New
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  New

Bug description:
  [Impact]
  Raven Ridge xHC may fail to suspend, causes the USB stops working, and blocks 
the system entering system-wide suspend.

  [Fix]
  It's a hardware/firmware bug, workarounded by bailing out suspend function if 
it ever fails, and reset the xHC in next resume function.

  [Test]
  After applying the patch, the USB works, and the system can enter S3 
consecutively.

  [Regression Potential]
  Minimal. This workaround only applies to AMD Raven Ridge xHC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806838/+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 1806665] Re: linux-azure: 4.15.0-1036.38 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/security-signoff
   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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 11:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
regression-testing: Testing in progress
+   security-signoff: Waiting for signoff
snap-release-to-beta: Snap not in 18/beta channel
snap-release-to-edge: Snap not in 18/edge channel
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1806665

Title:
  linux-azure: 4.15.0-1036.38 -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 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:
  Confirmed
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 stakeholder-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-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 11:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
regression-testing: Testing in progress
security-signoff: Waiting for signoff
snap-release-to-beta: Snap not in 18/beta channel
snap-release-to-edge: Snap not in 18/edge channel
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806665/+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 1806672] Re: linux-azure: 4.15.0-1036.38~16.04.1 -proposed tracker

[Brad Figg]

** 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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Uploaded
  phase-changed: Friday, 07. December 2018 03:38 UTC
  reason:
-   promote-to-proposed: Packages copied but not yet published to -proposed
+   promote-to-proposed: Packages copies requested

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1806672

Title:
  linux-azure: 4.15.0-1036.38~16.04.1 -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:
  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 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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-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-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Uploaded
  phase-changed: Friday, 07. December 2018 03:38 UTC
  reason:
promote-to-proposed: Packages copies requested

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806672/+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