[Kernel-packages] [Bug 1836622] Re: Eoan update: v5.2.1 upstream stable release

2019-07-15 Thread Seth Forshee
** Changed in: linux (Ubuntu Eoan)
   Status: In Progress => Fix Committed

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

Title:
  Eoan update: v5.2.1 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

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:

 v5.2.1 upstream stable release
 from git://git.kernel.org/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836622/+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 1836622] [NEW] Eoan update: v5.2.1 upstream stable release

2019-07-15 Thread Seth Forshee
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:

   v5.2.1 upstream stable release
   from git://git.kernel.org/

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Affects: linux (Ubuntu Eoan)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

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

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: Confirmed

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

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

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

Title:
  Eoan update: v5.2.1 upstream stable release

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

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:

 v5.2.1 upstream stable release
 from git://git.kernel.org/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836622/+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 1835345] Re: [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)

2019-07-15 Thread Seth Forshee
@AceLan: Why did you change the status to fix released when the packages
are still in proposed? Setting them back to fix committed. If you want
the package to release you need to mark verification done, not change
the status.

** Changed in: linux-firmware (Ubuntu Bionic)
   Status: Fix Released => Fix Committed

** Changed in: linux-firmware (Ubuntu Disco)
   Status: Fix Released => Fix Committed

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

Title:
  [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  BT fails to enable again after disabled it by hotkey with the following 
message
     Bus 001 Device 004: ID 8087:0029 Intel Corp.
  [248987.643125] usb 1-10: device descriptor read/64, error -110
  [249003.247721] usb 1-10: device descriptor read/64, error -110
  [249003.483611] usb 1-10: reset full-speed USB device number 4 using xhci_hcd
  [249018.855466] usb 1-10: device descriptor read/64, error -110
  [249034.467589] usb 1-10: device descriptor read/64, error -110
  [249034.703574] usb 1-10: reset full-speed USB device number 4 using xhci_hcd
  [249045.299399] usb 1-10: device not accepting address 4, error -62
  [249045.427510] usb 1-10: reset full-speed USB device number 4 using xhci_hcd
  [249050.675715] usb 1-10: Device not responding to setup address.
  [249050.883541] usb 1-10: device not accepting address 4, error -71

  [Fix]
  Found the updated firmware fixes the issue

  [Test]
  Verify on the machine couple days, and can't duplicate the issue anymore.

  [Regression Potential]
  Low, the system keeps running for 5 days, and pass s3 tests 30 times, 
everything works well.

  [Misc]
  The firmware for the wifi/bt card is intel/ibt-20-0-3.*, but 
intel/ibt-20-0-4.* have identical md5sum. To avoid the following new cards 
require the new fw_revision, so SRU both of them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1835345/+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 1836372] Re: Update firmware in nic-firmware udeb for 5.0 hwe kernel

2019-07-15 Thread Seth Forshee
Confirmed that the new files are now present in nic-
firmware_1.173.9_all.udeb, marking verification done.

** Tags added: verification-done-bionic

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

Title:
  Update firmware in nic-firmware udeb for 5.0 hwe kernel

Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-firmware source package in Bionic:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Recent updates to linux-firmware means that there are new and
  updated firmware files relevant to the 5.0 hwe kernel from disco.
  Adding these files to give a better install experience for the 18.04.3
  release.

  Fix: Add the new firmware files to the nic-firmware udeb.

  Test Case: Confirm that the new files are present in the nic-firmware
  udeb.

  Regression Potential: New firmware versions could contain regressions.
  These versions have already been released into bionic with no reported
  regressions though, and are known to fix actual problems, so the
  benefit seems to outweigh the potential risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836372/+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 1829737] Re: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9462/9560)

2019-07-13 Thread Seth Forshee
@Warren - If you still experience the issue with linux-firmware 1.173.8
then it must not be exactly the same issue, so please open a new bug.

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

Title:
  Bluetooth: hci0: request failed to create LE connection: status 0x0c
  (Intel 9462/9560)

Status in HWE Next:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Released

Bug description:
  SRU Justification

  [Impact]
  The firmware blob for Intel Bluetooth 9560/9462 is versioned 20.30.0.1 is not 
compatible with kernel version >= 4.19 and will cause failure to pair BT 4.0 
devices.

  [Fix]
  29a536a02cad linux-firmware: Update firmware file for Intel Bluetooth 9560

  Above upstream change contains latest firmware file for Intel
  Bluetooth 9560 that fixes HID pairing in recent kernel versions.

  [Test Case]
  Copy ibt-17-16-1.sfi blob to /lib/firmware/intel and do a cold boot to reload 
firmware. One should find following message in dmesg:

Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015

  This indicates firmware reload has been activated. For further warm
  boots, kernel would dump updated revision:

Bluetooth: hci0: Firmware revision 0.1 build 184 week 15 2019

  And perform BT 4.0 device pairing for functional tests.

  Tested blob against following kernel versions:

  * 5.0.0-1004-oem-osp1
  * 5.0.0-15-generic
  * 4.18.0-20-generic
  * 4.15.0-1038-oem
  * 4.15.0-50-generic

  [Regression Risk]
  Low. This affects only Intel JeffersonPeak Bluetooth chip series, namely 
9461/9462/9560, which are the hardware variants to be fixed.

  ---

  For kernel version >= 4.19, it fails to pair with BT4.0 HID devices
  and leave error messages in syslog:

    Bluetooth: hci0: request failed to create LE connection: status 0x0c

  Which can be detailed by btmon:

    < HCI Command: LE Extended Create Connection (0x08|0x0043) plen 26 #800 
[hci0] 30.895622
  Filter policy: White list is not used (0x00)
  Own address type: Public (0x00)
  Peer address type: Random (0x01)
  Peer address: DB:DD:51:2D:1C:CC (Static)
  Initiating PHYs: 0x01
  Entry 0: LE 1M
    Scan interval: 60.000 msec (0x0060)
    Scan window: 60.000 msec (0x0060)
    Min connection interval: 30.00 msec (0x0018)
    Max connection interval: 50.00 msec (0x0028)
    Connection latency: 0 (0x)
    Supervision timeout: 420 msec (0x002a)
    Min connection length: 0.000 msec (0x)
    Max connection length: 0.000 msec (0x)
    > HCI Event: Command Status (0x0f) plen 4 #801 [hci0] 30.896453
    LE Extended Create Connection (0x08|0x0043) ncmd 1
  Status: Command Disallowed (0x0c)

  Indicating this is actually a firmware problem.

  Verified this has been fixed at least in upstream linux-firmware
  commit 29a536a02cadb75b84c6c0b5d7af22d34d278563, firmware release
  version 21.10.0.6. With that firmware blob placed under
  /lib/firmware/intel and a cold boot, dmesg gives updated revision and
  device pairing works as expected:

    Firmware revision 0.1 build 184 week 15 2019

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1829737/+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 1836372] Re: Update firmware in nic-firmware udeb for 5.0 hwe kernel

2019-07-12 Thread Seth Forshee
** Changed in: linux-firmware (Ubuntu)
   Status: Invalid => Fix Committed

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

Title:
  Update firmware in nic-firmware udeb for 5.0 hwe kernel

Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-firmware source package in Bionic:
  In Progress

Bug description:
  SRU Justification

  Impact: Recent updates to linux-firmware means that there are new and
  updated firmware files relevant to the 5.0 hwe kernel from disco.
  Adding these files to give a better install experience for the 18.04.3
  release.

  Fix: Add the new firmware files to the nic-firmware udeb.

  Test Case: Confirm that the new files are present in the nic-firmware
  udeb.

  Regression Potential: New firmware versions could contain regressions.
  These versions have already been released into bionic with no reported
  regressions though, and are known to fix actual problems, so the
  benefit seems to outweigh the potential risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836372/+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 1836372] Re: Update firmware in nic-firmware udeb for 5.0 hwe kernel

2019-07-12 Thread Seth Forshee
** Description changed:

  SRU Justification
  
  Impact: Recent updates to linux-firmware means that there are new and
  updated firmware files relevant to the 5.0 hwe kernel from disco. Adding
- these files may give a better install experience for the 18.04.3
- release.
+ these files to give a better install experience for the 18.04.3 release.
  
  Fix: Add the new firmware files to the nic-firmware udeb.
  
  Test Case: Confirm that the new files are present in the nic-firmware
  udeb.
  
  Regression Potential: New firmware versions could contain regressions.
  These versions have already been released into bionic with no reported
  regressions though, and are known to fix actual problems, so the benefit
  seems to outweigh the potential risk.

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

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

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

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

** Changed in: linux-firmware (Ubuntu Bionic)
   Importance: High => Medium

** Changed in: linux-firmware (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  Update firmware in nic-firmware udeb for 5.0 hwe kernel

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Bionic:
  In Progress

Bug description:
  SRU Justification

  Impact: Recent updates to linux-firmware means that there are new and
  updated firmware files relevant to the 5.0 hwe kernel from disco.
  Adding these files to give a better install experience for the 18.04.3
  release.

  Fix: Add the new firmware files to the nic-firmware udeb.

  Test Case: Confirm that the new files are present in the nic-firmware
  udeb.

  Regression Potential: New firmware versions could contain regressions.
  These versions have already been released into bionic with no reported
  regressions though, and are known to fix actual problems, so the
  benefit seems to outweigh the potential risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836372/+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 1836372] [NEW] Update firmware in nic-firmware udeb for 5.0 hwe kernel

2019-07-12 Thread Seth Forshee
Public bug reported:

SRU Justification

Impact: Recent updates to linux-firmware means that there are new and
updated firmware files relevant to the 5.0 hwe kernel from disco. Adding
these files to give a better install experience for the 18.04.3 release.

Fix: Add the new firmware files to the nic-firmware udeb.

Test Case: Confirm that the new files are present in the nic-firmware
udeb.

Regression Potential: New firmware versions could contain regressions.
These versions have already been released into bionic with no reported
regressions though, and are known to fix actual problems, so the benefit
seems to outweigh the potential risk.

** Affects: linux-firmware (Ubuntu)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

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

Title:
  Update firmware in nic-firmware udeb for 5.0 hwe kernel

Status in linux-firmware package in Ubuntu:
  In Progress

Bug description:
  SRU Justification

  Impact: Recent updates to linux-firmware means that there are new and
  updated firmware files relevant to the 5.0 hwe kernel from disco.
  Adding these files to give a better install experience for the 18.04.3
  release.

  Fix: Add the new firmware files to the nic-firmware udeb.

  Test Case: Confirm that the new files are present in the nic-firmware
  udeb.

  Regression Potential: New firmware versions could contain regressions.
  These versions have already been released into bionic with no reported
  regressions though, and are known to fix actual problems, so the
  benefit seems to outweigh the potential risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836372/+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 1835345] Re: [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)

2019-07-10 Thread Seth Forshee
** Changed in: linux-firmware (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Changed in: linux-firmware (Ubuntu Disco)
   Status: In Progress => Fix Committed

** Changed in: linux-firmware (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  BT fails to enable again after disabled it by hotkey with the following 
message
     Bus 001 Device 004: ID 8087:0029 Intel Corp.
  [248987.643125] usb 1-10: device descriptor read/64, error -110
  [249003.247721] usb 1-10: device descriptor read/64, error -110
  [249003.483611] usb 1-10: reset full-speed USB device number 4 using xhci_hcd
  [249018.855466] usb 1-10: device descriptor read/64, error -110
  [249034.467589] usb 1-10: device descriptor read/64, error -110
  [249034.703574] usb 1-10: reset full-speed USB device number 4 using xhci_hcd
  [249045.299399] usb 1-10: device not accepting address 4, error -62
  [249045.427510] usb 1-10: reset full-speed USB device number 4 using xhci_hcd
  [249050.675715] usb 1-10: Device not responding to setup address.
  [249050.883541] usb 1-10: device not accepting address 4, error -71

  [Fix]
  Found the updated firmware fixes the issue

  [Test]
  Verify on the machine couple days, and can't duplicate the issue anymore.

  [Regression Potential]
  Low, the system keeps running for 5 days, and pass s3 tests 30 times, 
everything works well.

  [Misc]
  The firmware for the wifi/bt card is intel/ibt-20-0-3.*, but 
intel/ibt-20-0-4.* have identical md5sum. To avoid the following new cards 
require the new fw_revision, so SRU both of them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1835345/+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 1835449] Re: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9260)

2019-07-10 Thread Seth Forshee
** Changed in: linux-firmware (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Changed in: linux-firmware (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  Bluetooth: hci0: request failed to create LE connection: status 0x0c
  (Intel 9260)

Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Intel Wireless-AC 9260 Bluetooth doesn't pair to Bluetooth 5.0 HID
  devices.

  [Fix]
  Bluetooth FW Build REL0329 or newer is known to have fixed this problem
  on Cosmic, and for Disco we have REL0420. On Bionic and Xenial it takes
  a firmware backport from upstream commit
  c2d8f1b7f820b31b6120d741c23db23340a72821. Original patch modified to fix
  conflicts in the WHENCE file.

  [Test Case]
  Verified on hardware platforms with Intel Wireless AC 9260 installed,
  e.g. Dell Precision 7530. Copied the two blobs to /lib/firmware/intel
  and power off the device completely to trigger firmware reload at the
  next boot.

  [Regression Risk]
  Low. Tried following kernels with REL0329 firmware blobs:

* 4.4.0-154-generic: Xenial, WiFi/Bluetooth doesn't work
* 4.8.0-58-generic: Xenial, even doesn't boot to console
* 4.10.0-42-generic: Xenial, WiFi/Bluetooth doesn't work
* 4.11.0-14-generic: Xenial, WiFi/Bluetooth doesn't work
* 4.13.0-45-generic: Xenial
* 4.15.0-54-generic: Xenial, Bionic
* 4.15.0-1043-oem: Xenial, Bionic

  For those WiFi/Bluetooth doesn't work versions, WiFi/Bluetooth doesn't
  work even with current firmware blobs shipped in Xenial's linux-firmware
  REL0186. So overall, these updated blobs are only loaded by hardware
  requires them, and they doesn't bring harm to known working
  configurations.

   Original Bug Description 

  Same problem exactly as encountered with Intel 9560 is also happening
  with Intel 9260.

  Update to linux-firmware 1.173.8 did not fix the problem.

  Everything is working fine when using 4.15 kernel, but not for 4.18+
  5.0+.

  Reference problem:
  https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1829737

  You-Sheng Yang advised to do this by email and it fixed my issue, so I
  think the 9260 driver would need to be updated in the bionic branch
  (it seems to be updated in newer branches).

  --
  Basically you should try copy the latest firmware (ibt-*) under
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/intel
  , power off the device completely and power on, then have a check on
  bluetooth pairing.
  --

  Linux ideapad 5.0.0-20-generic #21~18.04.1-Ubuntu SMP Thu Jun 27
  04:04:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  OS: Linux Mint 19.1 Tessa x86_64
  Host: 81JB Lenovo ideapad 730S-13IWL
  Wifi/Bluetooth card is Intel 9260

  @:/etc$ dmesg | egrep -i 'blue|firm'
  [0.099619] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.173124] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [2.379392] [Firmware Bug]: Invalid critical threshold (0)
  [2.699758] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin 
(v1.4)
  [6.259427] iwlwifi :73:00.0: loaded firmware version 43.95eb4e97.0 
op_mode iwlmvm
  [6.337749] Bluetooth: Core ver 2.22
  [6.337767] Bluetooth: HCI device and connection manager initialized
  [6.337770] Bluetooth: HCI socket layer initialized
  [6.337773] Bluetooth: L2CAP socket layer initialized
  [6.33] Bluetooth: SCO socket layer initialized
  [6.368073] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017
  [7.309936] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [7.309938] Bluetooth: BNEP filters: protocol multicast
  [7.309943] Bluetooth: BNEP socket layer initialized
  [   17.197268] Bluetooth: RFCOMM TTY layer initialized
  [   17.197275] Bluetooth: RFCOMM socket layer initialized
  [   17.197284] Bluetooth: RFCOMM ver 1.11
  [  104.453159] Bluetooth: hci0: request failed to create LE connection: 
status 0x0c
  [  104.509148] Bluetooth: hci0: request failed to create LE connection: 
status 0x0c
  [  104.551340] Bluetooth: hci0: request failed to create LE connection: 
status 0x0c
  [  104.589338] Bluetooth: hci0: request failed to create LE connection: 
status 0x0c
  [  104.623323] Bluetooth: hci0: request failed to create LE connection: 
status 0x0c

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

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

[Kernel-packages] [Bug 1836045] Re: ftbfs: gnat cross targeting powerpc

2019-07-10 Thread Seth Forshee
That's not true; most architectures don't have a match for SO_RCVTIMEO,
as they're using the definition from asm-generic, just as powerpc should
be. The others were updated differently because they do not include asm-
generic/socket.h. And powerpc clearly does have a definition for it,
since the build complains that SO_RCVTIMEO_OLD is not defined and not
SO_RCVTIMEO. The question is why isn't SO_RCVTIMEO_OLD defined.

I tried cross-compiling the following for ppc64el and did not receive
any errors about SO_RCVTIMEO or SO_RCVTIMEO_OLD being undefined, nor did
it complain when I used SO_RCVTIMEO_OLD, so it seems like it's working
as intended. That leaves me wondering whether something isn't including
asm-generic/socket.h when it should be including asm/socket.h, or
something like that. I don't see any such mistakes in linux-libc-dev
though.

#include 
#include 

int main(void)
{
printf("%d\n", SO_RCVTIMEO);
return 0;
}

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

Title:
  ftbfs: gnat cross targeting powerpc

Status in gcc-8-cross package in Ubuntu:
  Confirmed
Status in gcc-9-cross package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  both seen with gcc-8-cross and gcc-9-cross (search the build logs for
  "unfinished":

  /<>/gcc/build/./gcc/xgcc -B/<>/gcc/build/./gcc/ 
-B/usr/powerpc-linux-gnu/bin/ -B/usr/powerpc-li
  nux-gnu/lib/ -isystem /usr/powerpc-linux-gnu/include -isystem 
/usr/powerpc-linux-gnu/sys-include -isystem /<
  >/gcc/build/sys-include-c -g -O2   -W -Wall -gnatpg -nostdinc  -gnatn  
a-direct.adb -o a-direct.o
  a-direct.adb:734:27: "NAME_MAX" is undefined
  a-direct.adb:743:28: "SIZEOF_struct_dirent_alloc" is undefined
  a-direct.adb:1210:24: "ENOENT" is undefined
  s-filatt.ads:62:18: "SIZEOF_struct_file_attributes" not declared in 
"OS_Constants"
  s-oscons.ads:50:26: "Target_OS" is undefined
  s-oscons.ads:54:01: (style) multiple blank lines
  s-oscons.ads:59:01: (style) multiple blank lines
  s-oscons.ads:64:01: (style) multiple blank lines
  s-oscons.ads:69:01: (style) multiple blank lines
  s-oscons.ads:74:01: (style) multiple blank lines
  s-oscons.ads:79:01: (style) multiple blank lines
  s-oscons.ads:86:01: (style) multiple blank lines
  s-oscons.ads:91:01: (style) multiple blank lines
  s-oscons.ads:96:01: (style) multiple blank lines
  s-oscons.ads:101:01: (style) multiple blank lines
  s-oscons.ads:106:01: (style) multiple blank lines
  s-oscons.ads:111:01: (style) multiple blank lines
  s-oscons.ads:116:01: (style) multiple blank lines
  s-oscons.ads:121:01: (style) multiple blank lines
  s-oscons.ads:126:01: (style) multiple blank lines
  s-oscons.ads:131:01: (style) multiple blank lines
  s-oscons.ads:136:01: (style) multiple blank lines
  s-oscons.ads:147:01: (style) multiple blank lines
  s-oscons.ads:166:01: (style) multiple blank lines
  s-oscons.ads:173:01: (style) multiple blank lines
  s-oscons.ads:176:01: (style) multiple blank lines
  s-oscons.ads:181:01: (style) multiple blank lines
  make[9]: *** [../gcc-interface/Makefile:299: a-direct.o] Error 1
  make[9]: Leaving directory '/<>/gcc/build/gcc/ada/rts'
  make[8]: *** [gcc-interface/Makefile:623: gnatlib] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-8-cross/+bug/1836045/+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 1836064] Re: linux-5.2 (?) breaks the c-t-b builds

2019-07-10 Thread Seth Forshee
I can confirm that a definition of __NR_osf_shmat was added during the
5.1 cycle:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=12b57c5c70f397a9410411d4e348096edada20f9

Looks like a fix has been applied to upstream glibc:

https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=d5ecee822e72a2fd156338ab2be2f2e70a1da55a

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

Title:
  linux-5.2 (?) breaks the c-t-b builds

Status in glibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  as seen in 
  
https://launchpad.net/ubuntu/+source/cross-toolchain-base-ports/30ubuntu2/+build/17249410

  the c-t-b-ports package ftbfs:

  /bin/bash ../scripts/move-if-change 
/<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.T 
/<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.h
  touch /<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.stmp
  if test -r 
/<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h.new; then mv -f 
/<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h.new 
/<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h; \
  else echo >&2 'This configuration not matched in ../abi-tags'; exit 1; fi
  In file included from :1:
  ../sysdeps/unix/sysv/linux/alpha/sysdep.h:54: error: "__NR_osf_shmat" 
redefined [-Werror]
   #define __NR_osf_shmat  209
   
  In file included from ../sysdeps/unix/sysv/linux/sys/syscall.h:24,
   from ../sysdeps/unix/sysdep.h:20,
   from ../sysdeps/unix/alpha/sysdep.h:19,
   from ../sysdeps/unix/sysv/linux/alpha/sysdep.h:29,
   from :1:
  /<>/glibc-2.29/debian/include/asm/unistd.h:8: note: this is the 
location of the previous definition
   #define __NR_osf_shmat __NR_shmat
   
  cc1: all warnings being treated as errors
  Traceback (most recent call last):
File "../scripts/gen-as-const.py", line 120, in 
  main()
File "../scripts/gen-as-const.py", line 116, in main
  consts = glibcextract.compute_c_consts(sym_data, args.cc)
File "/<>/glibc-2.29/scripts/glibcextract.py", line 62, in 
compute_c_consts
  subprocess.check_call(cmd, shell=True)
File "/usr/lib/python3.7/subprocess.py", line 347, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command 'alpha-linux-gnu-gcc-8 -no-pie 
-fno-PIE -std=gnu11 -fgnu89-inline  -pipe -O2 -g -Wall -Wwrite-strings -Wundef 
-Werror -fmerge-all-constants -frounding-math -fno-stack-protector 
-Wstrict-prototypes -Wold-style-definition -fmath-errno -mlong-double-128 
-mieee -mfp-rounding-mode=d-ftls-model=initial-exec   -U_FORTIFY_SOURCE 
-isystem /<>/glibc-2.29/debian/include  -I../include 
-I/<>/glibc-2.29/build-tree/alpha-libc/csu  
-I/<>/glibc-2.29/build-tree/alpha-libc  
-I../sysdeps/unix/sysv/linux/alpha/alpha  
-I../sysdeps/unix/sysv/linux/alpha/fpu  -I../sysdeps/alpha/fpu  
-I../sysdeps/unix/sysv/linux/alpha  -I../sysdeps/alpha/nptl  
-I../sysdeps/unix/sysv/linux/wordsize-64  -I../sysdeps/ieee754/ldbl-64-128  
-I../sysdeps/ieee754/ldbl-opt  -I../sysdeps/unix/sysv/linux/include 
-I../sysdeps/unix/sysv/linux  -I../sysdeps/nptl  -I../sysdeps/pthread  
-I../sysdeps/gnu  -I../sysdeps/unix/inet  -I../sysdeps/unix/sysv  
-I../sysdeps/unix/alpha  -I../sysdeps/unix  -I../sysdeps/posix  
-I../sysdeps/alpha  -I../sysdeps/wordsize-64  -I../sysdeps/ieee754/ldbl-128  
-I../sysdeps/ieee754/dbl-64/wordsize-64  -I../sysdeps/ieee754/dbl-64  
-I../sysdeps/ieee754/flt-32  -I../sysdeps/ieee754  -I../sysdeps/generic  -I.. 
-I../libio -I. -nostdinc -isystem 
/<>/debian/tmp.alpha/usr/bin/../lib/gcc-cross/alpha-linux-gnu/8/include
 -isystem 
/<>/debian/tmp.alpha/usr/bin/../lib/gcc-cross/alpha-linux-gnu/8/include-fixed
 -isystem /<>/glibc-2.29/debian/include  -D_LIBC_REENTRANT 
-include /<>/glibc-2.29/build-tree/alpha-libc/libc-modules.h 
-DMODULE_NAME=libc -include ../include/libc-symbols.h   
-DTOP_NAMESPACE=glibc -DGEN_AS_CONST_HEADERS-MD -MP -MF 
/<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h.dT  
-MT '/<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h.d 
/<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h' -S -o 
/tmp/tmpq06grbcg/test.s -x c - < /tmp/tmpq06grbcg/test.c' returned non-zero 
exit status 1.
  make[4]: *** [../Makerules:271: 
/<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h] Error 1
  make[4]: Leaving directory '/<>/glibc-2.29/csu'
  make[3]: *** [Makefile:275: csu/subdir_lib] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1836064/+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 1835700] Re: linux: 5.2.0-8.9 -proposed tracker

2019-07-08 Thread Seth Forshee
** Summary changed:

- linux:  -proposed tracker
+ linux: 5.2.0-8.9 -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) => Seth Forshee 
(sforshee)

** 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) => Seth Forshee 
(sforshee)

** 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) => 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/1835700

Title:
  linux: 5.2.0-8.9 -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:
  New
Status in linux source package in Eoan:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  phase: Ready for Packaging
  phase-changed: Monday, 08. July 2019 05:44 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835700/+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 1835700] [NEW] linux: -proposed tracker

2019-07-07 Thread Seth Forshee
Public bug reported:

This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.

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

-- swm properties --
variant: debs

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Eoan)
 Importance: Medium
 Status: New


** Tags: eoan kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-d2019.07.07-1

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Tags added: eoan kernel-release-tracking-bug

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-sru-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

** Tags added: kernel-release-tracking-bug-live

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ -- swm properties --
+ variant: debs

** Tags added: kernel-sru-cycle-d2019.07.07-1

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:

[Kernel-packages] [Bug 1834315] Re: Revert x86/vdso linker changes from #1830890 as this causes glibc 2.29-0ubuntu3 FTBFS on eoan

2019-06-28 Thread Seth Forshee
Okay, thanks for explaining. I'll remove the reverts from 5.2.

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

** Changed in: linux (Ubuntu)
   Status: Fix Committed => Invalid

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

Title:
  Revert x86/vdso linker changes from #1830890 as this causes glibc
  2.29-0ubuntu3 FTBFS on eoan

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

Bug description:
  [Impact]
  As reported in #1833067 and 
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1830890/comments/7 some 
glibc testcases are still regressing on i386 after applying both the following 
commits:

  commit 379d98ddf41344273d9718556f761420f4dc80b3
  Author: Alistair Strachan 
  Date: Fri Aug 3 10:39:31 2018 -0700

  x86: vdso: Use $LD instead of $CC to link

  commit cd01544a268ad8ee5b1dfe42c4393f1095f86879
  Author: Alistair Strachan 
  Date: Fri Dec 14 14:36:37 2018 -0800

  x86/vdso: Pass --eh-frame-hdr to the linker

  
  [Fix]
  Revert both these patches to restore the original behaviour.

  [Test]
  ADT tests for glibc.

  [Regression Potential]
  Low. This restores the status quo before the original change to 
vdso/x86/Makefile to restore the original linker behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834315/+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 1833387] Re: Add pointstick support on HP ZBook 17 G5

2019-06-27 Thread Seth Forshee
** Changed in: linux (Ubuntu)
   Status: Incomplete => Fix Committed

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

Title:
  Add pointstick support on HP ZBook 17 G5

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Cosmic:
  Fix Committed
Status in linux-oem source package in Cosmic:
  Won't Fix
Status in linux-oem-osp1 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Won't Fix
Status in linux-oem-osp1 source package in Disco:
  Won't Fix

Bug description:
  [Impact]
  Pointstick on HP ZBook 17 G5 doesn't work.

  [Fix]
  Let hid-multitouch know it has a pointstick, and exposes it as a mouse.

  [Test]
  With the fix applied the pointstick starts to work.

  [Regression Potential]
  Low. It's limited to one driver and limited to one specific device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1833387/+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 1834315] Re: Revert x86/vdso linker changes from #1830890 as this causes glibc 2.29-0ubuntu3 FTBFS on eoan

2019-06-27 Thread Seth Forshee
Applied reverts to the 5.2 kernel tree.

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

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

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

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

** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Revert x86/vdso linker changes from #1830890 as this causes glibc
  2.29-0ubuntu3 FTBFS on eoan

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Incomplete

Bug description:
  [Impact]
  As reported in #1833067 and 
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1830890/comments/7 some 
glibc testcases are still regressing on i386 after applying both the following 
commits:

  commit 379d98ddf41344273d9718556f761420f4dc80b3
  Author: Alistair Strachan 
  Date: Fri Aug 3 10:39:31 2018 -0700

  x86: vdso: Use $LD instead of $CC to link

  commit cd01544a268ad8ee5b1dfe42c4393f1095f86879
  Author: Alistair Strachan 
  Date: Fri Dec 14 14:36:37 2018 -0800

  x86/vdso: Pass --eh-frame-hdr to the linker

  
  [Fix]
  Revert both these patches to restore the original behaviour.

  [Test]
  ADT tests for glibc.

  [Regression Potential]
  Low. This restores the status quo before the original change to 
vdso/x86/Makefile to restore the original linker behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834315/+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 1834315] Re: Revert x86/vdso linker changes from #1830890 as this causes glibc 2.29-0ubuntu3 FTBFS on eoan

2019-06-27 Thread Seth Forshee
Just to be clear, these are both upstream commits. Is there any work
going on upstream to resolve the issue?

Currently eoan is using a kernel copied forward from disco, but we
should be putting a 5.2 kernel into eoan-proposed within the next couple
of weeks. This is likely to be before we could expect to see them in a
disco-proposed kernel, as the patch deadline for the next kernel SRU
cycle has passed.

I agree that the likelihood of regressions is slim for us, as the
changes were made only to support builds using clang. So I will go ahead
and revert these in our 5.2 tree.

I'm not sure why there's a xenial nomination here for a ftbfs in eoan
though ...

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

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

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

Title:
  Revert x86/vdso linker changes from #1830890 as this causes glibc
  2.29-0ubuntu3 FTBFS on eoan

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

Bug description:
  [Impact]
  As reported in #1833067 and 
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1830890/comments/7 some 
glibc testcases are still regressing on i386 after applying both the following 
commits:

  commit 379d98ddf41344273d9718556f761420f4dc80b3
  Author: Alistair Strachan 
  Date: Fri Aug 3 10:39:31 2018 -0700

  x86: vdso: Use $LD instead of $CC to link

  commit cd01544a268ad8ee5b1dfe42c4393f1095f86879
  Author: Alistair Strachan 
  Date: Fri Dec 14 14:36:37 2018 -0800

  x86/vdso: Pass --eh-frame-hdr to the linker

  
  [Fix]
  Revert both these patches to restore the original behaviour.

  [Test]
  ADT tests for glibc.

  [Regression Potential]
  Low. This restores the status quo before the original change to 
vdso/x86/Makefile to restore the original linker behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834315/+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 1834479] [NEW] depmod may prefer unsigned l-r-m nvidia modules to signed modules

2019-06-27 Thread Seth Forshee
Public bug reported:

Impact: When testing patches for bug 1834476, a bug was observed whereby
modprobe was someties attempting to load the unsigned nvidia modules in
/lib/modules/$(uname -r)/kernel/nvidia-N/bits rather than the signed
modules from /lib/modules/$(uname -r)/kernel/nvidia-N. This appears to
be because depmod is not deterministic in which module will be preferred
when duplicate modules of the same name exist.

Fix: The unsigned modules are no longer needed after the signed modules
have been generated, so update the build script to remove the unsigned
modules.

Test Case: Confirm that the ko files are found in /lib/modules/$(uname
-r)/kernel/nvidia-N but not in /lib/modules/$(uname
-r)/kernel/nvidia-N/bits. Confirm that the modules are signed and
loadable by the kernel under lockdown (or when booted with
modules.sig_enforce=y), and that modprobe consistently loads the modules
from the expected path after depmod.

Regression Potential: The modules being removed are an intermediate
build artifact and not meant to be loaded, so no regressions are
expected. However, if for some reason linking the intermediate unsigned
module was successful but generation of the signed module was not, the
user would have been left with a module that could potentially be loaded
(if not booted under UEFI secure boot) and would now be left with no
modules. This is not the intended behavior and never occurred in my
testing, so it's not a case we should be concerned about.

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: Fix Committed

** Affects: linux (Ubuntu Disco)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

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

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

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

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

** Summary changed:

- depmod may prefer unsigne l-r-m nvidia modules to signed modules
+ depmod may prefer unsigned l-r-m nvidia modules to signed modules

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

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

Title:
  depmod may prefer unsigned l-r-m nvidia modules to signed modules

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

Bug description:
  Impact: When testing patches for bug 1834476, a bug was observed
  whereby modprobe was someties attempting to load the unsigned nvidia
  modules in /lib/modules/$(uname -r)/kernel/nvidia-N/bits rather than
  the signed modules from /lib/modules/$(uname -r)/kernel/nvidia-N. This
  appears to be because depmod is not deterministic in which module will
  be preferred when duplicate modules of the same name exist.

  Fix: The unsigned modules are no longer needed after the signed
  modules have been generated, so update the build script to remove the
  unsigned modules.

  Test Case: Confirm that the ko files are found in /lib/modules/$(uname
  -r)/kernel/nvidia-N but not in /lib/modules/$(uname
  -r)/kernel/nvidia-N/bits. Confirm that the modules are signed and
  loadable by the kernel under lockdown (or when booted with
  modules.sig_enforce=y), and that modprobe consistently loads the
  modules from the expected path after depmod.

  Regression Potential: The modules being removed are an intermediate
  build artifact and not meant to be loaded, so no regressions are
  expected. However, if for some reason linking the intermediate
  unsigned module was successful but generation of the signed module was
  not, the user would have been left with a module that could
  potentially be loaded (if not booted under UEFI secure boot) and would
  now be left with no modules. This is not the intended behavior and
  never occurred in my testing, so it's not a case we should be
  concerned about.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834479/+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 1834476] [NEW] Add nvidia-418 dkms build support to disco

2019-06-27 Thread Seth Forshee
Public bug reported:

SRU Justification

Impact: The nvidia-graphics-drivers-418 package landed in disco shortly
before release and was not included in linux-restricted-modules, though
it is wanted there.

Fix: Update the linux and linux-restricted-modules packages to include
nvidia-graphics-drivers-418.

Test Case: Confirm that binary packages for nvidia-418 are built and
function as expected, and confirm that nvidia-390 continue to work as
before. A test build is available in ppa:sforshee/test-builds.

Regression Potential: The nvidia-418 packages are new binary packages
which must be installed by the user, so they cannot cause regressions.
There is a risk of inadvertent errors affecting the nvidia-390 packages,
however regression testing has turned up no such regressions.

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: Fix Committed

** Affects: linux-restricted-modules (Ubuntu)
 Importance: Undecided
 Status: Fix Committed

** Affects: linux (Ubuntu Disco)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Affects: linux-restricted-modules (Ubuntu Disco)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

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

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

** Also affects: linux-restricted-modules (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

** Changed in: linux-restricted-modules (Ubuntu)
   Status: New => Fix Committed

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

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

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

** Changed in: linux-restricted-modules (Ubuntu Disco)
   Importance: Undecided => Medium

** Changed in: linux-restricted-modules (Ubuntu Disco)
   Status: New => In Progress

** Changed in: linux-restricted-modules (Ubuntu Disco)
 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/1834476

Title:
  Add nvidia-418 dkms build support to disco

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-restricted-modules package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  In Progress
Status in linux-restricted-modules source package in Disco:
  In Progress

Bug description:
  SRU Justification

  Impact: The nvidia-graphics-drivers-418 package landed in disco
  shortly before release and was not included in linux-restricted-
  modules, though it is wanted there.

  Fix: Update the linux and linux-restricted-modules packages to include
  nvidia-graphics-drivers-418.

  Test Case: Confirm that binary packages for nvidia-418 are built and
  function as expected, and confirm that nvidia-390 continue to work as
  before. A test build is available in ppa:sforshee/test-builds.

  Regression Potential: The nvidia-418 packages are new binary packages
  which must be installed by the user, so they cannot cause regressions.
  There is a risk of inadvertent errors affecting the nvidia-390
  packages, however regression testing has turned up no such
  regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834476/+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 1833065] Re: Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]

2019-06-24 Thread Seth Forshee
** Changed in: linux-oem-osp1 (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Changed in: linux-oem-osp1 (Ubuntu Cosmic)
   Status: Won't Fix => Fix Committed

** Changed in: linux-oem-osp1 (Ubuntu Disco)
   Status: Won't Fix => Fix Committed

** Changed in: linux-oem-osp1 (Ubuntu Eoan)
   Status: Won't Fix => Fix Committed

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

Title:
  Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  New
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Cosmic:
  New
Status in linux-oem-osp1 source package in Cosmic:
  Fix Committed
Status in linux-firmware source package in Disco:
  New
Status in linux-oem-osp1 source package in Disco:
  Fix Committed
Status in linux-firmware source package in Eoan:
  New
Status in linux-oem-osp1 source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  Intel Wireless-AC 9560 requires additional driver support as well as new 
firmware blobs to function. Without them iwlwifi cannot correctly recognize the 
device on systems with Comet Lake cpu.

  [Fix]
  These changes are cherry-picked from either mainline kernel or 
backport-iwlwifi. Firmware blob iwlwifi-QuZ-a0-jf-b0-*.ucode is also necessary.

  [Test]
  Verified on hardware 02f0:4234 with fw rev 48.

  [Regression Potential]
  Low. These changes includes only necessary changes to enable Intel 
Wireless-AC 9560.

  == Original Bug Description ==

  Wireless module not detected by the system with the following error
  messages in the log:

  00:14.3 Network controller [0280]: Intel Corporation Device [8086:02f0]
   Subsystem: Intel Corporation Device [8086:4030]
  ...
  [ 4.195232] iwlwifi :00:14.3: enabling device ( -> 0002)
  [ 4.207011] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 
op_mode iwlmvm
  [ 4.286392] iwlwifi :00:14.3: Detected Intel(R) Dual Band Wireless AC 
9560, REV=0x354
  [ 9.355720] iwlwifi :00:14.3: Failed to load firmware chunk!
  [ 9.355722] iwlwifi :00:14.3: iwlwifi transaction failed, dumping 
registers
  [ 9.355723] iwlwifi :00:14.3: iwlwifi device config registers:
  [ 9.355759] iwlwifi :00:14.3: : 02f08086 00100406 0280 
0080 c2218004   
  [ 9.355761] iwlwifi :00:14.3: 0020:    
40308086  00c8  01ff
  [ 9.355761] iwlwifi :00:14.3: iwlwifi device memory mapped registers:
  [ 9.355792] iwlwifi :00:14.3: : 18489004 0040  
    
  [ 9.355793] iwlwifi :00:14.3: 0020: 0011 0c040005 0351 
d5d5 d5d5 d5d5 80008040 001f0040
  [ 9.355822] iwlwifi :00:14.3: Could not load the [0] uCode section
  [ 9.355825] iwlwifi :00:14.3: Failed to start INIT ucode: -110
  [ 9.355827] iwlwifi :00:14.3: Collecting data: trigger 15 fired.
  [ 9.576115] iwlwifi :00:14.3: Failing on timeout while stopping DMA 
channel 8 [0x0bad1122]
  [ 9.588329] iwlwifi :00:14.3: Failed to run INIT ucode: -110

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1833065/+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 1833405] Re: add firmware and topology file for sound sof driver [cml/cnl]

2019-06-24 Thread Seth Forshee
** Changed in: linux-firmware (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: linux-firmware (Ubuntu Disco)
   Status: New => Fix Committed

** Changed in: linux-firmware (Ubuntu Eoan)
   Status: New => Fix Committed

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

** Changed in: linux-firmware (Ubuntu Cosmic)
   Status: New => Fix Committed

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

Title:
  add firmware and topology file for sound sof driver [cml/cnl]

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Cosmic:
  Fix Committed
Status in linux-firmware source package in Disco:
  Fix Committed
Status in linux-firmware source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  We have a couple dell and lenovo laptops which have dmic directly connected
  to PCH, this needs intel sof driver to work, and intel sof driver is merged
  oem-osp1-b kernel and it needs to load firmware and topology file to work.

  [Fix]
  Intel provides two binary files to us, one is firmware, the other is
  topology file, these two files are built from
  https://github.com/thesofproject/sof.git, and the license is BSD 3.

  [Test Case]
  put the firmware and topology to rootfs and boot with the oem-osp1-b
  kernel on those machines, the sof driver works well.

  [Regression Risk]
  Low. just adding two new binary files, no change to existing files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1833405/+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 1832048] Re: hinic: fix oops due to race in set_rx_mode

2019-06-18 Thread Seth Forshee
** Changed in: linux (Ubuntu Eoan)
   Status: In Progress => Fix Committed

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

Title:
  hinic: fix oops due to race in set_rx_mode

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

Bug description:
  [Impact]
  It is possible for the hinic driver to oops after the module is removed and 
reinserted.

  [Test Case]
  while :; do sudo modprobe -r hinic; modprobe hinic; done

  [Fix]
  From linux-next:
66350023d5756 hinic: fix a bug in set rx mode

  [Regression Risk]
  Patch is local to the hinic driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832048/+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 1757218] Re: QCA9377 isn't being recognized sometimes

2019-06-17 Thread Seth Forshee
** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  QCA9377 isn't being recognized sometimes

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  Fix Committed

Bug description:
  === SRU Justification ===
  [Impact]
  Qualcomm WiFi/Bluetooth may disappear after boot. 

  [Fix]
  Disable USB2 LPM at shutdown phase, to prevent it from lingering in LPM
  L1. Pull back the device to full power before shutdown imitates the
  behavior on Windows.

  [Test] 
  The affected user confimed it fixes the issue.
  I can also confirm that
  a) The power drain in S5 is much lower,
  b) Both WiFi and Bluetooth are always present during reboot stress test.

  [Regression Potential]
  Low. Only a limited number of USB2 devices that support LPM.

  === Original Bug Report ===
  Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This 
caused, on prior versions, a kernel panic at boot. With Bionic, the system 
boots but is unable to use wireless network. On dmesg there are messages like:

  [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
  [2.808640] usb 1-7: device descriptor read/64, error -71
  [3.044337] usb 1-7: device descriptor read/64, error -71
  [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
  [3.408245] usb 1-7: device descriptor read/64, error -71
  [3.644244] usb 1-7: device descriptor read/64, error -71
  [3.752193] usb usb1-port7: attempt power cycle
  [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
  [4.404904] usb 1-7: Device not responding to setup address.
  [4.612478] usb 1-7: Device not responding to setup address.
  [4.820588] usb 1-7: device not accepting address 9, error -71
  [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
  [4.949109] usb 1-7: Device not responding to setup address.
  [5.156893] usb 1-7: Device not responding to setup address.
  [5.364589] usb 1-7: device not accepting address 10, error -71
  [5.364655] usb usb1-port7: unable to enumerate USB device

  And lspci and lsusb don't show the wireless network card. The
  alternative is to turn the system off. Reboot don't work and reboot to
  Windows 10 also don't. The system must be powered off to restore
  functionality. Then, on the next boot, it works properly.

  However, after the system is turned off, it may cause the issue again.
  This is not 100% consistent, but mostly it cycles between powering off
  and powering on the notebook as:

  Work -> Don't work -> Work -> Don't work

  On Windows 10 this doesn't happen but when happens on Ubuntu, it's
  possible to reboot and see the status on Windows 10 too: on Device
  Manager it's shown a unidentified USB device at 1-7. Sometimes, on
  Windows 10's Network Devices it's shown, instead of the QCA9377, from
  four to six different devices with generic names and Bluetooth and/or
  Wireless don't work.

  When turning Ubuntu off, there are messages that appears a few
  instants before the system is turned off:

  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] 
ath10k_pci :02:00.0: failed to install key for vdev 0 peer 
xx:xx:xx:xx:xx:xx: -110
  Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] 
wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)

  Generally, only the second message appears (but both are recorded on
  kern.log). The MAC adress is the one from the router, not from the
  wireless card.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1364 F pulseaudio
   /dev/snd/seq:usuario1258 F timidity
  CurrentDesktop: XFCE
  Date: Tue Mar 20 14:43:42 2018
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2017-06-13 (279 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days 

[Kernel-packages] [Bug 1831833] Re: [SRU][B/C] Add the firmwares of RTL8822BE and RTL8822CE

2019-06-17 Thread Seth Forshee
** Changed in: linux-firmware (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: linux-firmware (Ubuntu Cosmic)
   Status: New => Fix Committed

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

Title:
  [SRU][B/C] Add the firmwares of RTL8822BE and RTL8822CE

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Cosmic:
  Fix Committed

Bug description:
  SRU justification:

  [Impact]
  Add new firmwares of RTL8822BE/RTL8822CE.

  [Fix]
  rtw88 and these new firmwares will support RTL8822BE/RTL8822CE

  [Test]
  Verified on hardware. Tests result are good.

  [Regression Potential]
  Low, it introducs the new firmwares to enable new wifi chips supports.
  These firmwares are already in disco.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1831833/+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 1832316] Re: shiftfs: allow changing ro/rw for subvolumes

2019-06-14 Thread Seth Forshee
** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

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

Title:
  shiftfs: allow changing ro/rw for subvolumes

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  New

Bug description:
  SRU Justification

  Impact: Stéphane reported regression for btrfs workloads employing shiftfs.
  Unprivileged users can already toggle whether a subvolume will be ro or
  rw. This is broken on current shiftfs as we haven't whitelisted these
  ioctls().

  Fix: To enable this with shiftfs we need to whitelist BTRFS_IOC_FS_INFO,
  BTRFS_IOC_SUBVOL_GETFLAGS, BTRFS_IOC_SUBVOL_SETFLAGS. All of them should
  be safe for unprivileged users.

  Regression Potential: Limited to shiftfs.

  Test Case: Tested with LXD running shiftfs on top of btrfs and verified
  btrfs subvolumes can be made ro or rw.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832316/+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 1804183] Re: netronome firmware symlinks are overwritten by package upgrade

2019-06-12 Thread Seth Forshee
This seems like a bit of an abuse of conffiles, as those files aren't
really intended for user modification. It seems like this is a pretty
niche use case that doesn't apply to the vast majority of users.

Have you looked at dpkg-divert? This can be used to force packages to
install specific files to a diverted location. For example, 'dpkg-divert
--add --rename --divert /lib/firmware/nic_AMDA0058-0011_2x40.nffw.foo
/lib/firmware/nic_AMDA0058-0011_2x40.nffw' should cause the
nic_AMDA0058-0011_2x40.nffw file from linux-firmware updates to be
written to nic_AMDA0058-0011_2x40.nffw.foo.

https://debian-administration.org/article/118
/Replacing_binaries_with_dpkg-divert

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

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

Title:
  netronome firmware symlinks are overwritten by package upgrade

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  The linux-firmware package includes symlinks to installed Netronome
  firmware files. These links may be updated by a user but are
  overwritten when the linux-firmware package is upgraded whereas the
  desired behaviour is to leave existing symlinks unmodified.

  # apt install linux-firmware 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following package was automatically installed and is no longer required:
grub-pc-bin
  Use 'apt autoremove' to remove it.
  The following NEW packages will be installed:
linux-firmware
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 64.6 MB of archives.
  After this operation, 278 MB of additional disk space will be used.
  Get:1 http://lon1.mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 
linux-firmware all 1.173.1 [64.6 MB]
  Fetched 64.6 MB in 1s (43.8 MB/s) 
  Selecting previously unselected package linux-firmware.
  (Reading database ... 59988 files and directories currently installed.)
  Preparing to unpack .../linux-firmware_1.173.1_all.deb ...
  Unpacking linux-firmware (1.173.1) ...
  Setting up linux-firmware (1.173.1) ...
  update-initramfs: Generating /boot/initrd.img-4.15.0-38-generic
  # cd /lib/firmware/netronome/
  # ls -l
  total 8
  drwxr-xr-x 2 root root 4096 Nov 20 09:07 flower
  drwxr-xr-x 2 root root 4096 Nov 20 09:07 nic
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0081-0001_1x40.nffw -> 
nic/nic_AMDA0081-0001_1x40.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0081-0001_4x10.nffw -> 
nic/nic_AMDA0081-0001_4x10.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0096-0001_2x10.nffw -> 
nic/nic_AMDA0096-0001_2x10.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0097-0001_2x40.nffw -> 
nic/nic_AMDA0097-0001_2x40.nffw
  lrwxrwxrwx 1 root root   36 May 18  2018 nic_AMDA0097-0001_4x10_1x40.nffw -> 
nic/nic_AMDA0097-0001_4x10_1x40.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0097-0001_8x10.nffw -> 
nic/nic_AMDA0097-0001_8x10.nffw
  lrwxrwxrwx 1 root root   36 May 18  2018 nic_AMDA0099-0001_1x10_1x25.nffw -> 
nic/nic_AMDA0099-0001_1x10_1x25.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0099-0001_2x10.nffw -> 
nic/nic_AMDA0099-0001_2x10.nffw
  lrwxrwxrwx 1 root root   31 May 18  2018 nic_AMDA0099-0001_2x25.nffw -> 
nic/nic_AMDA0099-0001_2x25.nffw
  # for i in $(find flower/ -type l); do ln -sf $i $(basename $i); done
  # ls -l
  total 8
  drwxr-xr-x 2 root root 4096 Nov 20 09:07 flower
  drwxr-xr-x 2 root root 4096 Nov 20 09:07 nic
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0081-0001_1x40.nffw -> 
flower/nic_AMDA0081-0001_1x40.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0081-0001_4x10.nffw -> 
flower/nic_AMDA0081-0001_4x10.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0096-0001_2x10.nffw -> 
flower/nic_AMDA0096-0001_2x10.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0097-0001_2x40.nffw -> 
flower/nic_AMDA0097-0001_2x40.nffw
  lrwxrwxrwx 1 root root   39 Nov 20 09:09 nic_AMDA0097-0001_4x10_1x40.nffw -> 
flower/nic_AMDA0097-0001_4x10_1x40.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0097-0001_8x10.nffw -> 
flower/nic_AMDA0097-0001_8x10.nffw
  lrwxrwxrwx 1 root root   36 May 18  2018 nic_AMDA0099-0001_1x10_1x25.nffw -> 
nic/nic_AMDA0099-0001_1x10_1x25.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0099-0001_2x10.nffw -> 
flower/nic_AMDA0099-0001_2x10.nffw
  lrwxrwxrwx 1 root root   34 Nov 20 09:09 nic_AMDA0099-0001_2x25.nffw -> 
flower/nic_AMDA0099-0001_2x25.nffw
  # apt update
  ...
  # apt install linux-firmware
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following package was automatically installed and is no longer required:
grub-pc-bin
  Use 'apt autoremove' to remove it.
  The following packages will be upgraded:

[Kernel-packages] [Bug 1823753] Re: arm64: cma_alloc errors at boot

2019-06-07 Thread Seth Forshee
** Changed in: linux (Ubuntu Eoan)
   Status: In Progress => Fix Committed

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

Title:
  arm64: cma_alloc errors at boot

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

Bug description:
  [Impact]
  We enabled CONFIG_DMA_CMA to fix bug 1803206, but that led to a regression
  on other arm64 systems that began spewing these messages on boot - sometimes 
> 10K of them:

  [   19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12

  In a previous SRU (bug 1828092), we worked around this by just rate-
  limiting these messages. These are "err" priority messages though, so
  even a lower number of them is still disconcerting.

  [Fix]
  1) Bump up the amount of available CMA on arm64 to 32M (same as upstream 
defconfig)
  2) A patch-set from linux-next that redirects dma-direct contiguous 
allocations to alloc_pages() for single page allocations (single pages are by 
definition contiguous), avoiding CMA usage/fragmentation.

  [Test Case]
  dmesg | grep "cma_alloc: alloc failed"
  Some system configs will still have some of these errors even after this fix 
- but this should reduce them significantly. Per-driver optimizations can be 
used to make further improvements, but we should track those in other bugs.

  [Regression Risk]
  Tested on a HiSilicon D06 and HP m400 (Hi1620 & X-Gene arm64).
  Regression tested on:
   - Raspberry Pi 3B (see Comment #22)
   - Power9 system (ppc64el)
   - z/VM instance (s390x)
   - Intel Centerton system (amd64)

  Test builds are staged at http://ppa.launchpad.net/~dannf/ubuntu/cma

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+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 1830883] Re: iwlwifi Intel 8265 firmware crashing in powersave mode

2019-06-05 Thread Seth Forshee
No problem, glad we were able to help get it resolved.

** Changed in: linux-firmware (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
   iwlwifi Intel 8265 firmware crashing in powersave mode

Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  When I disconnect my AC adapter or run `sudo tlp bat` to switch to
  battery mode my wifi stops working. Reconnecting the AC adapter or
  running `sudo tlp ac` returns the wifi adapter to a functioning state.

  I use the default TLP configuration without modifications and at first
  I was thinking that this is a bug in TLP. The FAQs already have an
  entry about this and state that this is due to the "kernel driver does
  not implement power saving properly" [1]. This is why I'm reporting
  the issue here.

  I'm using Ubuntu Disco and I remember this working in previous Ubuntu
  versions / kernels. This happened on kernel 5.0.0-15-generic but also
  on the 5.1.5-050105-generic mainline kernel.

  Below is a snippet of /var/log/syslog at the moment of switching TLP
  to battery mode. Battery mode was activated at 11:25 and AC mode was
  re-activated around 11:27.

  Please let me know if this is actually the right place to submit this
  bug report and whether I can provide more information.

  ---

  May 29 11:23:40 x1cbn systemd-resolved[1037]: message repeated 3 times: [ 
Server returned error NXDOMAIN, mitigating potential DNS violation 
DVE-2018-0001, retrying transaction with reduced feature level UDP.]
  May 29 11:23:41 x1cbn colord[1285]: failed to get session [pid 1158]: Keine 
Daten verfügbar
  May 29 11:25:37 x1cbn wpa_supplicant[1144]: wlp2s0: CTRL-EVENT-SCAN-FAILED 
ret=-110
  May 29 11:25:37 x1cbn geoclue[1741]: WiFi scan failed
  May 29 11:25:37 x1cbn kernel: [ 4645.773659] iwlwifi :02:00.0: Error 
sending SCAN_REQ_UMAC: time out after 2000ms.
  May 29 11:25:37 x1cbn kernel: [ 4645.773670] iwlwifi :02:00.0: Current 
CMD queue read_ptr 229 write_ptr 230
  May 29 11:25:37 x1cbn kernel: [ 4645.775119] iwlwifi :02:00.0: Start IWL 
Error Log Dump:
  May 29 11:25:37 x1cbn kernel: [ 4645.775125] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  May 29 11:25:37 x1cbn kernel: [ 4645.775130] iwlwifi :02:00.0: Loaded 
firmware version: 36.9f0a2d68.0
  May 29 11:25:37 x1cbn kernel: [ 4645.775137] iwlwifi :02:00.0: 0x0084 
| NMI_INTERRUPT_UNKNOWN   
  May 29 11:25:37 x1cbn kernel: [ 4645.775142] iwlwifi :02:00.0: 0x0200 
| trm_hw_status0
  May 29 11:25:37 x1cbn kernel: [ 4645.775147] iwlwifi :02:00.0: 0x 
| trm_hw_status1
  May 29 11:25:37 x1cbn kernel: [ 4645.775152] iwlwifi :02:00.0: 0x0002485C 
| branchlink2
  May 29 11:25:37 x1cbn kernel: [ 4645.775157] iwlwifi :02:00.0: 0x0003A7CA 
| interruptlink1
  May 29 11:25:37 x1cbn kernel: [ 4645.775161] iwlwifi :02:00.0: 0x5D56 
| interruptlink2
  May 29 11:25:37 x1cbn kernel: [ 4645.775166] iwlwifi :02:00.0: 0x 
| data1
  May 29 11:25:37 x1cbn kernel: [ 4645.775171] iwlwifi :02:00.0: 0x0080 
| data2
  May 29 11:25:37 x1cbn kernel: [ 4645.775175] iwlwifi :02:00.0: 0x07A3 
| data3
  May 29 11:25:37 x1cbn kernel: [ 4645.775180] iwlwifi :02:00.0: 0xBBC109E2 
| beacon time
  May 29 11:25:37 x1cbn kernel: [ 4645.775185] iwlwifi :02:00.0: 0x10C87621 
| tsf low
  May 29 11:25:37 x1cbn kernel: [ 4645.775190] iwlwifi :02:00.0: 0x019F 
| tsf hi
  May 29 11:25:37 x1cbn kernel: [ 4645.775194] iwlwifi :02:00.0: 0x 
| time gp1
  May 29 11:25:37 x1cbn kernel: [ 4645.775199] iwlwifi :02:00.0: 0xCC95B750 
| time gp2
  May 29 11:25:37 x1cbn kernel: [ 4645.775204] iwlwifi :02:00.0: 0x0001 
| uCode revision type
  May 29 11:25:37 x1cbn kernel: [ 4645.775209] iwlwifi :02:00.0: 0x0024 
| uCode version major
  May 29 11:25:37 x1cbn kernel: [ 4645.775214] iwlwifi :02:00.0: 0x9F0A2D68 
| uCode version minor
  May 29 11:25:37 x1cbn kernel: [ 4645.775219] iwlwifi :02:00.0: 0x0230 
| hw version
  May 29 11:25:37 x1cbn kernel: [ 4645.775224] iwlwifi :02:00.0: 0x0008 
| board version
  May 29 11:25:37 x1cbn kernel: [ 4645.775228] iwlwifi :02:00.0: 0x001C 
| hcmd
  May 29 11:25:37 x1cbn kernel: [ 4645.775233] iwlwifi :02:00.0: 0x24022000 
| isr0
  May 29 11:25:37 x1cbn kernel: [ 4645.775238] iwlwifi :02:00.0: 0x0180 
| isr1
  May 29 11:25:37 x1cbn kernel: [ 4645.775242] iwlwifi :02:00.0: 0x0800180A 
| isr2
  May 29 11:25:37 x1cbn kernel: [ 4645.775247] iwlwifi :02:00.0: 0x00417CC0 
| isr3
  May 29 11:25:37 x1cbn kernel: [ 4645.775252] iwlwifi :02:00.0: 0x 
| isr4
  May 29 11:25:37 x1cbn kernel: [ 4645.775257] iwlwifi :02:00.0: 0x0AD9001C 
| last cmd Id
  May 29 11:25:37 x1cbn kernel: [ 4645.775262] iwlwifi :02:00.0: 0x 
| wait_event
 

Re: [Kernel-packages] [Bug 1830883] Re: iwlwifi Intel 8265 firmware crashing in powersave mode

2019-06-05 Thread Seth Forshee
On Wed, Jun 05, 2019 at 07:36:50AM -, Emmanuel Grumbach wrote:
> Hi Seth,
> 
> we debugged this and we found out that d0i3 was not disabled in iwlwifi.
> This is a kind of power saving thing that requires integration with the
> platform / kernel that should be enabled only for specific platform. Not
> something that should be enabled in a distribution kernel.
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/net/wireless/intel/iwlwifi
> /iwl-drv.c?h=linux-5.1.y#n1670
> 
> In mainline, it is disabled by default.
> Not sure what happened here.

It's also disabled by default in our kernels.

https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/disco/tree/drivers/net/wireless/intel/iwlwifi
/iwl-drv.c#n1643

And the 5.1.5-050105-generic kernel which was tested and also has the
problem is an unmodified upstream build. My system has nothing specified
for the module parameter in /etc/modprobe.d, and I get Y from
/sys/module/iwlwifi/parameters/d0i3_disable.

@jnns, is it possible you've done something to your system to change the
module parameter? Could have been by adding it in in /etc/modprobe.d or
changing the kernel command line (cat /proc/cmdline). Not sure what else
might be changing it.

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

Title:
   iwlwifi Intel 8265 firmware crashing in powersave mode

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  When I disconnect my AC adapter or run `sudo tlp bat` to switch to
  battery mode my wifi stops working. Reconnecting the AC adapter or
  running `sudo tlp ac` returns the wifi adapter to a functioning state.

  I use the default TLP configuration without modifications and at first
  I was thinking that this is a bug in TLP. The FAQs already have an
  entry about this and state that this is due to the "kernel driver does
  not implement power saving properly" [1]. This is why I'm reporting
  the issue here.

  I'm using Ubuntu Disco and I remember this working in previous Ubuntu
  versions / kernels. This happened on kernel 5.0.0-15-generic but also
  on the 5.1.5-050105-generic mainline kernel.

  Below is a snippet of /var/log/syslog at the moment of switching TLP
  to battery mode. Battery mode was activated at 11:25 and AC mode was
  re-activated around 11:27.

  Please let me know if this is actually the right place to submit this
  bug report and whether I can provide more information.

  ---

  May 29 11:23:40 x1cbn systemd-resolved[1037]: message repeated 3 times: [ 
Server returned error NXDOMAIN, mitigating potential DNS violation 
DVE-2018-0001, retrying transaction with reduced feature level UDP.]
  May 29 11:23:41 x1cbn colord[1285]: failed to get session [pid 1158]: Keine 
Daten verfügbar
  May 29 11:25:37 x1cbn wpa_supplicant[1144]: wlp2s0: CTRL-EVENT-SCAN-FAILED 
ret=-110
  May 29 11:25:37 x1cbn geoclue[1741]: WiFi scan failed
  May 29 11:25:37 x1cbn kernel: [ 4645.773659] iwlwifi :02:00.0: Error 
sending SCAN_REQ_UMAC: time out after 2000ms.
  May 29 11:25:37 x1cbn kernel: [ 4645.773670] iwlwifi :02:00.0: Current 
CMD queue read_ptr 229 write_ptr 230
  May 29 11:25:37 x1cbn kernel: [ 4645.775119] iwlwifi :02:00.0: Start IWL 
Error Log Dump:
  May 29 11:25:37 x1cbn kernel: [ 4645.775125] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  May 29 11:25:37 x1cbn kernel: [ 4645.775130] iwlwifi :02:00.0: Loaded 
firmware version: 36.9f0a2d68.0
  May 29 11:25:37 x1cbn kernel: [ 4645.775137] iwlwifi :02:00.0: 0x0084 
| NMI_INTERRUPT_UNKNOWN   
  May 29 11:25:37 x1cbn kernel: [ 4645.775142] iwlwifi :02:00.0: 0x0200 
| trm_hw_status0
  May 29 11:25:37 x1cbn kernel: [ 4645.775147] iwlwifi :02:00.0: 0x 
| trm_hw_status1
  May 29 11:25:37 x1cbn kernel: [ 4645.775152] iwlwifi :02:00.0: 0x0002485C 
| branchlink2
  May 29 11:25:37 x1cbn kernel: [ 4645.775157] iwlwifi :02:00.0: 0x0003A7CA 
| interruptlink1
  May 29 11:25:37 x1cbn kernel: [ 4645.775161] iwlwifi :02:00.0: 0x5D56 
| interruptlink2
  May 29 11:25:37 x1cbn kernel: [ 4645.775166] iwlwifi :02:00.0: 0x 
| data1
  May 29 11:25:37 x1cbn kernel: [ 4645.775171] iwlwifi :02:00.0: 0x0080 
| data2
  May 29 11:25:37 x1cbn kernel: [ 4645.775175] iwlwifi :02:00.0: 0x07A3 
| data3
  May 29 11:25:37 x1cbn kernel: [ 4645.775180] iwlwifi :02:00.0: 0xBBC109E2 
| beacon time
  May 29 11:25:37 x1cbn kernel: [ 4645.775185] iwlwifi :02:00.0: 0x10C87621 
| tsf low
  May 29 11:25:37 x1cbn kernel: [ 4645.775190] iwlwifi :02:00.0: 0x019F 
| tsf hi
  May 29 11:25:37 x1cbn kernel: [ 4645.775194] iwlwifi :02:00.0: 0x 
| time gp1
  May 29 11:25:37 x1cbn kernel: [ 4645.775199] iwlwifi :02:00.0: 0xCC95B750 
| time gp2
  May 29 11:25:37 x1cbn kernel: [ 4645.775204] iwlwifi :02:00.0: 0x0001 
| uCode 

Re: [Kernel-packages] [Bug 1830350] Re: System freezes repeatedly for several seconds; wifi driver related errors

2019-06-03 Thread Seth Forshee
On Mon, Jun 03, 2019 at 12:26:44PM -, Frank van Wensveen wrote:
> OK. The "modinfo -F" command you gave me returns a list of files:
> 
> ath10k/QCA9377/hw1.0/board.bin
> ath10k/QCA9377/hw1.0/firmware-5.bin
> ath10k/QCA6174/hw3.0/board-2.bin
> ath10k/QCA6174/hw3.0/board.bin
> ath10k/QCA6174/hw3.0/firmware-6.bin
> ath10k/QCA6174/hw3.0/firmware-5.bin
> ath10k/QCA6174/hw3.0/firmware-4.bin
> ath10k/QCA6174/hw2.1/board-2.bin
> ath10k/QCA6174/hw2.1/board.bin
> ath10k/QCA6174/hw2.1/firmware-5.bin
> ath10k/QCA6174/hw2.1/firmware-4.bin
> ath10k/QCA9887/hw1.0/board-2.bin
> ath10k/QCA9887/hw1.0/board.bin
> ath10k/QCA9887/hw1.0/firmware-5.bin
> ath10k/QCA988X/hw2.0/board-2.bin
> ath10k/QCA988X/hw2.0/board.bin
> ath10k/QCA988X/hw2.0/firmware-5.bin
> ath10k/QCA988X/hw2.0/firmware-4.bin
> ath10k/QCA988X/hw2.0/firmware-3.bin
> ath10k/QCA988X/hw2.0/firmware-2.bin
> 
> but not all these files exist in the updated firmware build I downloaded
> as per Kai-Heng Feng's instructions above.

It's possible not all the files will be there. I would do something like
this:

 $ sudo mv /lib/firmware/ath10k /lib/firmware/ath10k.bak
 $ sudo cp -r /ath10k /lib/firmware

Then when you're finished you can restore the old files:

 $ sudo rm -r /lib/firmware/ath10k
 $ sudo mv /lib/firmware/ath10k.bak /lib/firmware/ath10k

> And in the directory you had
> me check are only *.ko files. So I'm not sure what to replace with what
> here.

Firmware files are located under /lib/firmware.

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

Title:
  System freezes repeatedly for several seconds; wifi driver related
  errors

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I updated my system about a month ago (Fri 26 April 2019). This was
  the first update in several weeks and installed fresh versions of a
  whole truck load of applications including a kernel update. Since this
  latest bunch of updates the system freezes for a few seconds at
  regular intervals. Not fatal, but very annoying.

  Output from "journalctl -f" shows the following errors occurring at
  the same time as these freezes:

  May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED 
ret=-110
  May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to receive 
scan abortion completion: timed out
  May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to stop scan: 
-110
  May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to start hw 
scan: -110

  Corresponding lines in /var/log/syslog:

  May 24 10:29:16 dellfvw avahi-daemon[1053]: Registering new address record 
for fe80::424:c75b:2a2d:52e2 on wlp3s0.*.
  May 24 10:29:55 dellfvw avahi-daemon[1053]: Withdrawing address record for 
fe80::424:c75b:2a2d:52e2 on wlp3s0.
  May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED 
ret=-110
  May 24 10:31:18 dellfvw kernel: [45569.661175] ath10k_pci :03:00.0: 
failed to receive scan abortion completion: timed out
  May 24 10:31:18 dellfvw kernel: [45569.661183] ath10k_pci :03:00.0: 
failed to stop scan: -110
  May 24 10:31:18 dellfvw kernel: [45569.661187] ath10k_pci :03:00.0: 
failed to start hw scan: -110

  I do note the interval between the avahi-daemon entry and the
  subsequent errors related to the wireless network interface, but the
  former precede the latter consistently in syslog, suggesting they may
  be related, which is why I'm including it in this report.

  The freezes last a few seconds. Keyboard input is preserved at this
  time and typed input appears after the freeze is resolved. Mouse
  cursor continues to move during freezes but mouse clicks are only
  processed after the freeze is resolved, i.e. the result of the mouse
  click is suspended (e.g. buffered) until the system becomes responsive
  again. For example, clicking on a window during the freeze will focus
  that window after the freeze has been resolved.

  The system is a Dell Inspiron 15 3576. Relevant output of lspci -nnk:

  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac
  Wireless Network Adapter [168c:0042] (rev 31)

  Output of lsb_release -rd:
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  Output of uname -a:
  Linux dellfvw 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  As already said, this is a new issue that has began occurring only
  after the recent batch of updates that included a kernel update. I
  reported the bug (maybe in the wrong place) but so far I have received
  no response. I've lived with this for a month or so hoping that
  further updates would fix the problem but it still persists.
  Installing the latest firmware update (14 Mar 2019) has no effect. No
  other changes were made to either hardware or OS configuration.

 

[Kernel-packages] [Bug 1830883] Re: iwlwifi Intel 8265 firmware crashing in powersave mode

2019-05-31 Thread Seth Forshee
That does appear to be the latest firmware. There's some information
about debugging and reporting bugs here:

https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging

There are some things there to try, but given that this appears to be a
firmware crash I don't know that they will be of much help. Your best
bet is to follow the instructions there to report a bug for the
developers at Intel to look at.

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

Title:
   iwlwifi Intel 8265 firmware crashing in powersave mode

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  When I disconnect my AC adapter or run `sudo tlp bat` to switch to
  battery mode my wifi stops working. Reconnecting the AC adapter or
  running `sudo tlp ac` returns the wifi adapter to a functioning state.

  I use the default TLP configuration without modifications and at first
  I was thinking that this is a bug in TLP. The FAQs already have an
  entry about this and state that this is due to the "kernel driver does
  not implement power saving properly" [1]. This is why I'm reporting
  the issue here.

  I'm using Ubuntu Disco and I remember this working in previous Ubuntu
  versions / kernels. This happened on kernel 5.0.0-15-generic but also
  on the 5.1.5-050105-generic mainline kernel.

  Below is a snippet of /var/log/syslog at the moment of switching TLP
  to battery mode. Battery mode was activated at 11:25 and AC mode was
  re-activated around 11:27.

  Please let me know if this is actually the right place to submit this
  bug report and whether I can provide more information.

  ---

  May 29 11:23:40 x1cbn systemd-resolved[1037]: message repeated 3 times: [ 
Server returned error NXDOMAIN, mitigating potential DNS violation 
DVE-2018-0001, retrying transaction with reduced feature level UDP.]
  May 29 11:23:41 x1cbn colord[1285]: failed to get session [pid 1158]: Keine 
Daten verfügbar
  May 29 11:25:37 x1cbn wpa_supplicant[1144]: wlp2s0: CTRL-EVENT-SCAN-FAILED 
ret=-110
  May 29 11:25:37 x1cbn geoclue[1741]: WiFi scan failed
  May 29 11:25:37 x1cbn kernel: [ 4645.773659] iwlwifi :02:00.0: Error 
sending SCAN_REQ_UMAC: time out after 2000ms.
  May 29 11:25:37 x1cbn kernel: [ 4645.773670] iwlwifi :02:00.0: Current 
CMD queue read_ptr 229 write_ptr 230
  May 29 11:25:37 x1cbn kernel: [ 4645.775119] iwlwifi :02:00.0: Start IWL 
Error Log Dump:
  May 29 11:25:37 x1cbn kernel: [ 4645.775125] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  May 29 11:25:37 x1cbn kernel: [ 4645.775130] iwlwifi :02:00.0: Loaded 
firmware version: 36.9f0a2d68.0
  May 29 11:25:37 x1cbn kernel: [ 4645.775137] iwlwifi :02:00.0: 0x0084 
| NMI_INTERRUPT_UNKNOWN   
  May 29 11:25:37 x1cbn kernel: [ 4645.775142] iwlwifi :02:00.0: 0x0200 
| trm_hw_status0
  May 29 11:25:37 x1cbn kernel: [ 4645.775147] iwlwifi :02:00.0: 0x 
| trm_hw_status1
  May 29 11:25:37 x1cbn kernel: [ 4645.775152] iwlwifi :02:00.0: 0x0002485C 
| branchlink2
  May 29 11:25:37 x1cbn kernel: [ 4645.775157] iwlwifi :02:00.0: 0x0003A7CA 
| interruptlink1
  May 29 11:25:37 x1cbn kernel: [ 4645.775161] iwlwifi :02:00.0: 0x5D56 
| interruptlink2
  May 29 11:25:37 x1cbn kernel: [ 4645.775166] iwlwifi :02:00.0: 0x 
| data1
  May 29 11:25:37 x1cbn kernel: [ 4645.775171] iwlwifi :02:00.0: 0x0080 
| data2
  May 29 11:25:37 x1cbn kernel: [ 4645.775175] iwlwifi :02:00.0: 0x07A3 
| data3
  May 29 11:25:37 x1cbn kernel: [ 4645.775180] iwlwifi :02:00.0: 0xBBC109E2 
| beacon time
  May 29 11:25:37 x1cbn kernel: [ 4645.775185] iwlwifi :02:00.0: 0x10C87621 
| tsf low
  May 29 11:25:37 x1cbn kernel: [ 4645.775190] iwlwifi :02:00.0: 0x019F 
| tsf hi
  May 29 11:25:37 x1cbn kernel: [ 4645.775194] iwlwifi :02:00.0: 0x 
| time gp1
  May 29 11:25:37 x1cbn kernel: [ 4645.775199] iwlwifi :02:00.0: 0xCC95B750 
| time gp2
  May 29 11:25:37 x1cbn kernel: [ 4645.775204] iwlwifi :02:00.0: 0x0001 
| uCode revision type
  May 29 11:25:37 x1cbn kernel: [ 4645.775209] iwlwifi :02:00.0: 0x0024 
| uCode version major
  May 29 11:25:37 x1cbn kernel: [ 4645.775214] iwlwifi :02:00.0: 0x9F0A2D68 
| uCode version minor
  May 29 11:25:37 x1cbn kernel: [ 4645.775219] iwlwifi :02:00.0: 0x0230 
| hw version
  May 29 11:25:37 x1cbn kernel: [ 4645.775224] iwlwifi :02:00.0: 0x0008 
| board version
  May 29 11:25:37 x1cbn kernel: [ 4645.775228] iwlwifi :02:00.0: 0x001C 
| hcmd
  May 29 11:25:37 x1cbn kernel: [ 4645.775233] iwlwifi :02:00.0: 0x24022000 
| isr0
  May 29 11:25:37 x1cbn kernel: [ 4645.775238] iwlwifi :02:00.0: 0x0180 
| isr1
  May 29 11:25:37 x1cbn kernel: [ 4645.775242] iwlwifi :02:00.0: 0x0800180A 
| isr2
  May 29 11:25:37 x1cbn kernel: [ 4645.775247] iwlwifi :02:00.0: 

Re: [Kernel-packages] [Bug 1830350] Re: System freezes repeatedly for several seconds; wifi driver related errors

2019-05-31 Thread Seth Forshee
On Fri, May 31, 2019 at 10:41:17AM -, Frank van Wensveen wrote:
> 1. The latest linux-firmware that you directed me to (linux-
> firmware-20190514.tar.gz) is obviously intended for those who know what
> they're doing. It is just a matter of "make install" or is there more to
> installing this version? I'm a little concerned about hosing my system,
> seeing as it's my production machine.

I think you would be better off making backup copies of the specific
files the driver uses, then replace the original files with the versions
from the link. Running "modinfo -F firmware /lib/modules/$(uname
-r)/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko" in a terminal
will give you a list of the firmware files the driver may be using. Note
that the paths it prints need to have /lib/firmware/ prepended.

> 2. Can I simply install:
> linux-image-unsigned-5.2.0-050200rc2-generic_5.2.0-050200rc2.201905262130_amd64.deb
> linux-modules-5.2.0-050200rc2-generic_5.2.0-050200rc2.201905262130_amd64.deb
> linux-headers-5.2.0-050200rc2-generic_5.2.0-050200rc2.201905262130_amd64.deb
> or are there other dependencies as well?

You might also need the linux-headers-*_all.deb package. You probably
only need the headers packages if you are using dkms modules, but if the
*_amd64 package without the *_all package won't do you much good. If
you're unsure whether you need them just go ahead and install them; they
won't hurt anything.

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

Title:
  System freezes repeatedly for several seconds; wifi driver related
  errors

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I updated my system about a month ago (Fri 26 April 2019). This was
  the first update in several weeks and installed fresh versions of a
  whole truck load of applications including a kernel update. Since this
  latest bunch of updates the system freezes for a few seconds at
  regular intervals. Not fatal, but very annoying.

  Output from "journalctl -f" shows the following errors occurring at
  the same time as these freezes:

  May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED 
ret=-110
  May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to receive 
scan abortion completion: timed out
  May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to stop scan: 
-110
  May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to start hw 
scan: -110

  Corresponding lines in /var/log/syslog:

  May 24 10:29:16 dellfvw avahi-daemon[1053]: Registering new address record 
for fe80::424:c75b:2a2d:52e2 on wlp3s0.*.
  May 24 10:29:55 dellfvw avahi-daemon[1053]: Withdrawing address record for 
fe80::424:c75b:2a2d:52e2 on wlp3s0.
  May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED 
ret=-110
  May 24 10:31:18 dellfvw kernel: [45569.661175] ath10k_pci :03:00.0: 
failed to receive scan abortion completion: timed out
  May 24 10:31:18 dellfvw kernel: [45569.661183] ath10k_pci :03:00.0: 
failed to stop scan: -110
  May 24 10:31:18 dellfvw kernel: [45569.661187] ath10k_pci :03:00.0: 
failed to start hw scan: -110

  I do note the interval between the avahi-daemon entry and the
  subsequent errors related to the wireless network interface, but the
  former precede the latter consistently in syslog, suggesting they may
  be related, which is why I'm including it in this report.

  The freezes last a few seconds. Keyboard input is preserved at this
  time and typed input appears after the freeze is resolved. Mouse
  cursor continues to move during freezes but mouse clicks are only
  processed after the freeze is resolved, i.e. the result of the mouse
  click is suspended (e.g. buffered) until the system becomes responsive
  again. For example, clicking on a window during the freeze will focus
  that window after the freeze has been resolved.

  The system is a Dell Inspiron 15 3576. Relevant output of lspci -nnk:

  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac
  Wireless Network Adapter [168c:0042] (rev 31)

  Output of lsb_release -rd:
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  Output of uname -a:
  Linux dellfvw 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  As already said, this is a new issue that has began occurring only
  after the recent batch of updates that included a kernel update. I
  reported the bug (maybe in the wrong place) but so far I have received
  no response. I've lived with this for a month or so hoping that
  further updates would fix the problem but it still persists.
  Installing the latest firmware update (14 Mar 2019) has no effect. No
  other changes were made to either hardware or OS configuration.

  Logfile snippets attached.
  --- 
  

[Kernel-packages] [Bug 1830050] Re: nvidia-graphics-drivers-390 390.116-0ubuntu1 ADT test failure with linux 5.2.0-0.1

2019-05-31 Thread Seth Forshee
** Attachment added: "make.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1830050/+attachment/5268059/+files/make.log

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

Title:
  nvidia-graphics-drivers-390 390.116-0ubuntu1 ADT test failure with
  linux 5.2.0-0.1

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

Bug description:
  Testing failed on:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1830050/+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 1830053] Re: nvidia-graphics-drivers-418 418.74-0ubuntu1 ADT test failure with linux 5.2.0-0.1

2019-05-31 Thread Seth Forshee
** Attachment added: "make.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1830053/+attachment/5268058/+files/make.log

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

Title:
  nvidia-graphics-drivers-418 418.74-0ubuntu1 ADT test failure with
  linux 5.2.0-0.1

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

Bug description:
  Testing failed on:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1830053/+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 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu

2019-05-30 Thread Seth Forshee
** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common
  deb on Ubuntu

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
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
Status in linux source package in Disco:
  In Progress

Bug description:
  [Impact]
  File libperf-jvmti.so is missing in linux-tools-common deb making it 
impossible to use perf for the JVM JITed methods.

  [Test case]
  $ sudo perf record -k 1 -e instructions:u ./java 
-agentpath:/usr/lib/linux-tools-5.0.0-8/libperf-jvmti.so crc32
  $ sudo perf inject -i ./perf.data -j -o ./perf.data.jitted
  $ sudo perf report -f -i ./perf.data.jitted

  [Fix]
  Include java build dependencies and install the library into linux-tools 
package.

  [Regression potential]
  Small regression potential, an extra file is distributed and is not 
automatically linked to anything. It could impact the build, which was tested.

  ---Problem Description---
  File libperf-jvmti.so is missing in linux-tools-common deb making it 
impossible to use perf for the JVM JITed methods

  ---uname output---
  linux-image-4.13.0-36-generic

  Machine Type = not relevant

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   File libperf-jvmti.so is missing in linux-tools-common deb provided for 
Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also 
checked if the file is available on launchpad 
(https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) 
at it's also absent there:

  gromero@ltc-wspoon3:~/download$ dpkg -c 
linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm
  gromero@ltc-wspoon3:~/download$ dpkg -c 
linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm

  I do see the file in tools/perf/jvmti dir in the source .tar.gz, but
  apparently it's no being packaged in any .deb file?

  Thanks.

  Userspace tool common name: perf

  The userspace tool has the following bit modes: 64-bit

  Userspace tool obtained from project website:  na

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+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 1829737] Re: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9462/9560)

2019-05-29 Thread Seth Forshee
** Description changed:

+ SRU Justification
+ 
+ [Impact]
+ The firmware blob for Intel Bluetooth 9560/9462 is versioned 20.30.0.1 is not 
compatible with kernel version >= 4.19 and will cause failure to pair BT 4.0 
devices.
+ 
+ [Fix]
+ 29a536a02cad linux-firmware: Update firmware file for Intel Bluetooth 9560
+ 
+ Above upstream change contains latest firmware file for Intel Bluetooth
+ 9560 that fixes HID pairing in recent kernel versions.
+ 
+ [Test Case]
+ Copy ibt-17-16-1.sfi blob to /lib/firmware/intel and do a cold boot to reload 
firmware. One should find following message in dmesg:
+ 
+   Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015
+ 
+ This indicates firmware reload has been activated. For further warm
+ boots, kernel would dump updated revision:
+ 
+   Bluetooth: hci0: Firmware revision 0.1 build 184 week 15 2019
+ 
+ And perform BT 4.0 device pairing for functional tests.
+ 
+ Tested blob against following kernel versions:
+ 
+ * 5.0.0-1004-oem-osp1
+ * 5.0.0-15-generic
+ * 4.18.0-20-generic
+ * 4.15.0-1038-oem
+ * 4.15.0-50-generic
+ 
+ [Regression Risk]
+ Low. This affects only Intel JeffersonPeak Bluetooth chip series, namely 
9461/9462/9560, which are the hardware variants to be fixed.
+ 
+ ---
+ 
  For kernel version >= 4.19, it fails to pair with BT4.0 HID devices and
  leave error messages in syslog:
  
    Bluetooth: hci0: request failed to create LE connection: status 0x0c
  
  Which can be detailed by btmon:
  
    < HCI Command: LE Extended Create Connection (0x08|0x0043) plen 26 #800 
[hci0] 30.895622
  Filter policy: White list is not used (0x00)
  Own address type: Public (0x00)
  Peer address type: Random (0x01)
  Peer address: DB:DD:51:2D:1C:CC (Static)
  Initiating PHYs: 0x01
  Entry 0: LE 1M
    Scan interval: 60.000 msec (0x0060)
    Scan window: 60.000 msec (0x0060)
    Min connection interval: 30.00 msec (0x0018)
    Max connection interval: 50.00 msec (0x0028)
    Connection latency: 0 (0x)
    Supervision timeout: 420 msec (0x002a)
    Min connection length: 0.000 msec (0x)
    Max connection length: 0.000 msec (0x)
    > HCI Event: Command Status (0x0f) plen 4 #801 [hci0] 30.896453
    LE Extended Create Connection (0x08|0x0043) ncmd 1
  Status: Command Disallowed (0x0c)
  
  Indicating this is actually a firmware problem.
  
  Verified this has been fixed at least in upstream linux-firmware commit
  29a536a02cadb75b84c6c0b5d7af22d34d278563, firmware release version
  21.10.0.6. With that firmware blob placed under /lib/firmware/intel and
  a cold boot, dmesg gives updated revision and device pairing works as
  expected:
  
    Firmware revision 0.1 build 184 week 15 2019

** Changed in: linux-firmware (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Changed in: linux-firmware (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Bluetooth: hci0: request failed to create LE connection: status 0x0c
  (Intel 9462/9560)

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]
  The firmware blob for Intel Bluetooth 9560/9462 is versioned 20.30.0.1 is not 
compatible with kernel version >= 4.19 and will cause failure to pair BT 4.0 
devices.

  [Fix]
  29a536a02cad linux-firmware: Update firmware file for Intel Bluetooth 9560

  Above upstream change contains latest firmware file for Intel
  Bluetooth 9560 that fixes HID pairing in recent kernel versions.

  [Test Case]
  Copy ibt-17-16-1.sfi blob to /lib/firmware/intel and do a cold boot to reload 
firmware. One should find following message in dmesg:

Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015

  This indicates firmware reload has been activated. For further warm
  boots, kernel would dump updated revision:

Bluetooth: hci0: Firmware revision 0.1 build 184 week 15 2019

  And perform BT 4.0 device pairing for functional tests.

  Tested blob against following kernel versions:

  * 5.0.0-1004-oem-osp1
  * 5.0.0-15-generic
  * 4.18.0-20-generic
  * 4.15.0-1038-oem
  * 4.15.0-50-generic

  [Regression Risk]
  Low. This affects only Intel JeffersonPeak Bluetooth chip series, namely 
9461/9462/9560, which are the hardware variants to be fixed.

  ---

  For kernel version >= 4.19, it fails to pair with BT4.0 HID devices
  and leave error messages in syslog:

    Bluetooth: hci0: request failed to create LE connection: status 0x0c

  Which can be detailed by btmon:

    < HCI Command: LE Extended Create Connection (0x08|0x0043) plen 26 #800 
[hci0] 30.895622
  Filter policy: White list is not used 

[Kernel-packages] [Bug 1830883] Re: iwlwifi Intel 8265 firmware crashing in powersave mode

2019-05-29 Thread Seth Forshee
Can you please run 'apport-collect 1830883' in a terminal to attach
relevant logs and system information to this bug?

It's likely you'll need to get support from Intel for this issue since
it is a firmware crash, but one thing you should check is that you have
the newest firmware available for your hardware. I can point you at the
specific file once you've attached your system information, but if you
know which file you need you can find it here:

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/tree/

If you still have this problem with the newest firmware available, you
should report the bug here:

https://bugzilla.kernel.org
Product: Networking
Component: Wireless

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

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

Title:
   iwlwifi Intel 8265 firmware crashing in powersave mode

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  When I disconnect my AC adapter or run `sudo tlp bat` to switch to
  battery mode my wifi stops working. Reconnecting the AC adapter or
  running `sudo tlp ac` returns the wifi adapter to a functioning state.

  I use the default TLP configuration without modifications and at first
  I was thinking that this is a bug in TLP. The FAQs already have an
  entry about this and state that this is due to the "kernel driver does
  not implement power saving properly" [1]. This is why I'm reporting
  the issue here.

  I'm using Ubuntu Disco and I remember this working in previous Ubuntu
  versions / kernels. This happened on kernel 5.0.0-15-generic but also
  on the 5.1.5-050105-generic mainline kernel.

  Below is a snippet of /var/log/syslog at the moment of switching TLP
  to battery mode. Battery mode was activated at 11:25 and AC mode was
  re-activated around 11:27.

  Please let me know if this is actually the right place to submit this
  bug report and whether I can provide more information.

  ---

  May 29 11:23:40 x1cbn systemd-resolved[1037]: message repeated 3 times: [ 
Server returned error NXDOMAIN, mitigating potential DNS violation 
DVE-2018-0001, retrying transaction with reduced feature level UDP.]
  May 29 11:23:41 x1cbn colord[1285]: failed to get session [pid 1158]: Keine 
Daten verfügbar
  May 29 11:25:37 x1cbn wpa_supplicant[1144]: wlp2s0: CTRL-EVENT-SCAN-FAILED 
ret=-110
  May 29 11:25:37 x1cbn geoclue[1741]: WiFi scan failed
  May 29 11:25:37 x1cbn kernel: [ 4645.773659] iwlwifi :02:00.0: Error 
sending SCAN_REQ_UMAC: time out after 2000ms.
  May 29 11:25:37 x1cbn kernel: [ 4645.773670] iwlwifi :02:00.0: Current 
CMD queue read_ptr 229 write_ptr 230
  May 29 11:25:37 x1cbn kernel: [ 4645.775119] iwlwifi :02:00.0: Start IWL 
Error Log Dump:
  May 29 11:25:37 x1cbn kernel: [ 4645.775125] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  May 29 11:25:37 x1cbn kernel: [ 4645.775130] iwlwifi :02:00.0: Loaded 
firmware version: 36.9f0a2d68.0
  May 29 11:25:37 x1cbn kernel: [ 4645.775137] iwlwifi :02:00.0: 0x0084 
| NMI_INTERRUPT_UNKNOWN   
  May 29 11:25:37 x1cbn kernel: [ 4645.775142] iwlwifi :02:00.0: 0x0200 
| trm_hw_status0
  May 29 11:25:37 x1cbn kernel: [ 4645.775147] iwlwifi :02:00.0: 0x 
| trm_hw_status1
  May 29 11:25:37 x1cbn kernel: [ 4645.775152] iwlwifi :02:00.0: 0x0002485C 
| branchlink2
  May 29 11:25:37 x1cbn kernel: [ 4645.775157] iwlwifi :02:00.0: 0x0003A7CA 
| interruptlink1
  May 29 11:25:37 x1cbn kernel: [ 4645.775161] iwlwifi :02:00.0: 0x5D56 
| interruptlink2
  May 29 11:25:37 x1cbn kernel: [ 4645.775166] iwlwifi :02:00.0: 0x 
| data1
  May 29 11:25:37 x1cbn kernel: [ 4645.775171] iwlwifi :02:00.0: 0x0080 
| data2
  May 29 11:25:37 x1cbn kernel: [ 4645.775175] iwlwifi :02:00.0: 0x07A3 
| data3
  May 29 11:25:37 x1cbn kernel: [ 4645.775180] iwlwifi :02:00.0: 0xBBC109E2 
| beacon time
  May 29 11:25:37 x1cbn kernel: [ 4645.775185] iwlwifi :02:00.0: 0x10C87621 
| tsf low
  May 29 11:25:37 x1cbn kernel: [ 4645.775190] iwlwifi :02:00.0: 0x019F 
| tsf hi
  May 29 11:25:37 x1cbn kernel: [ 4645.775194] iwlwifi :02:00.0: 0x 
| time gp1
  May 29 11:25:37 x1cbn kernel: [ 4645.775199] iwlwifi :02:00.0: 0xCC95B750 
| time gp2
  May 29 11:25:37 x1cbn kernel: [ 4645.775204] iwlwifi :02:00.0: 0x0001 
| uCode revision type
  May 29 11:25:37 x1cbn kernel: [ 4645.775209] iwlwifi :02:00.0: 0x0024 
| uCode version major
  May 29 11:25:37 x1cbn kernel: [ 4645.775214] iwlwifi :02:00.0: 0x9F0A2D68 
| uCode version minor
  May 29 11:25:37 x1cbn kernel: [ 4645.775219] iwlwifi :02:00.0: 0x0230 
| hw version
  May 29 11:25:37 x1cbn kernel: [ 4645.775224] iwlwifi :02:00.0: 0x0008 
| board version
  May 29 11:25:37 x1cbn kernel: [ 4645.775228] iwlwifi :02:00.0: 

[Kernel-packages] [Bug 1827111] Re: nvidia-graphics-drivers-390 390.116-0ubuntu1 ADT test failure with linux 5.1.0-1.1

2019-05-22 Thread Seth Forshee
*** This bug is a duplicate of bug 1830050 ***
https://bugs.launchpad.net/bugs/1830050

** This bug has been marked a duplicate of bug 1830050
   nvidia-graphics-drivers-390 390.116-0ubuntu1 ADT test failure with linux 
5.2.0-0.1

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

Title:
  nvidia-graphics-drivers-390 390.116-0ubuntu1 ADT test failure with
  linux 5.1.0-1.1

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

Bug description:
  Testing failed on:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1827111/+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 1827112] Re: nvidia-graphics-drivers-418 418.56-0ubuntu1 ADT test failure with linux 5.1.0-1.1

2019-05-22 Thread Seth Forshee
*** This bug is a duplicate of bug 1830053 ***
https://bugs.launchpad.net/bugs/1830053

** This bug has been marked a duplicate of bug 1830053
   nvidia-graphics-drivers-418 418.74-0ubuntu1 ADT test failure with linux 
5.2.0-0.1

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

Title:
  nvidia-graphics-drivers-418 418.56-0ubuntu1 ADT test failure with
  linux 5.1.0-1.1

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

Bug description:
  Testing failed on:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1827112/+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 1827117] Re: zfs-linux 0.7.12-1ubuntu5 ADT test failure with linux 5.1.0-1.1

2019-05-22 Thread Seth Forshee
*** This bug is a duplicate of bug 1830064 ***
https://bugs.launchpad.net/bugs/1830064

** This bug has been marked a duplicate of bug 1830064
   zfs-linux 0.7.12-1ubuntu5 ADT test failure with linux 5.2.0-0.1

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

Title:
  zfs-linux 0.7.12-1ubuntu5 ADT test failure with linux 5.1.0-1.1

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/z/zfs-linux/20190429_124800_98faf@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/arm64/z/zfs-linux/20190430_162709_2c370@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/ppc64el/z/zfs-linux/20190429_155705_2c370@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/s390x/z/zfs-linux/20190429_152755_2c370@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1827117/+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 1830053] [NEW] nvidia-graphics-drivers-418 418.74-0ubuntu1 ADT test failure with linux 5.2.0-0.1

2019-05-22 Thread Seth Forshee
Public bug reported:

Testing failed on:

** Affects: nvidia-graphics-drivers-418 (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  nvidia-graphics-drivers-418 418.74-0ubuntu1 ADT test failure with
  linux 5.2.0-0.1

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

Bug description:
  Testing failed on:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1830053/+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 1830064] [NEW] zfs-linux 0.7.12-1ubuntu5 ADT test failure with linux 5.2.0-0.1

2019-05-22 Thread Seth Forshee
Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/amd64/z/zfs-linux/20190522_042907_e25a7@/log.gz
arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/arm64/z/zfs-linux/20190522_122048_e25a7@/log.gz
ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/ppc64el/z/zfs-linux/20190522_043554_e25a7@/log.gz
s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/s390x/z/zfs-linux/20190522_043345_e25a7@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  zfs-linux 0.7.12-1ubuntu5 ADT test failure with linux 5.2.0-0.1

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/amd64/z/zfs-linux/20190522_042907_e25a7@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/arm64/z/zfs-linux/20190522_122048_e25a7@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/ppc64el/z/zfs-linux/20190522_043554_e25a7@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/s390x/z/zfs-linux/20190522_043345_e25a7@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1830064/+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 1830050] [NEW] nvidia-graphics-drivers-390 390.116-0ubuntu1 ADT test failure with linux 5.2.0-0.1

2019-05-22 Thread Seth Forshee
Public bug reported:

Testing failed on:

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  nvidia-graphics-drivers-390 390.116-0ubuntu1 ADT test failure with
  linux 5.2.0-0.1

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

Bug description:
  Testing failed on:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1830050/+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 1827100] Re: bcmwl 6.30.223.271+bdcom-0ubuntu4 ADT test failure with linux 5.1.0-1.1

2019-05-17 Thread Seth Forshee
** Changed in: bcmwl (Ubuntu)
   Importance: Undecided => Medium

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

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

** Patch added: "bcmwl_6.30.223.271+bdcom-0ubuntu5.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1827100/+attachment/5264575/+files/bcmwl_6.30.223.271+bdcom-0ubuntu5.debdiff

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

Title:
  bcmwl 6.30.223.271+bdcom-0ubuntu4 ADT test failure with linux
  5.1.0-1.1

Status in bcmwl package in Ubuntu:
  In Progress

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/b/bcmwl/20190429_132741_e6057@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/i386/b/bcmwl/20190429_124054_e6057@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1827100/+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 1829050] [NEW] Eoan update: v5.1.2 upstream stable release

2019-05-14 Thread Seth Forshee
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:

   v5.1.2 upstream stable release
   from git://git.kernel.org/


Linux 5.1.2
x86/speculation/mds: Fix documentation typo
Documentation: Correct the possible MDS sysfs values
x86/mds: Add MDSUM variant to the MDS documentation
x86/speculation/mds: Add 'mitigations=' support for MDS
s390/speculation: Support 'mitigations=' cmdline option
powerpc/speculation: Support 'mitigations=' cmdline option
x86/speculation: Support 'mitigations=' cmdline option
cpu/speculation: Add 'mitigations=' cmdline option
x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off
x86/speculation/mds: Fix comment
x86/speculation/mds: Add SMT warning message
x86/speculation: Move arch_smt_update() call to after mitigation decisions
x86/speculation/mds: Add mds=full,nosmt cmdline option
Documentation: Add MDS vulnerability documentation
Documentation: Move L1TF to separate directory
x86/speculation/mds: Add mitigation mode VMWERV
x86/speculation/mds: Add sysfs reporting for MDS
x86/speculation/mds: Add mitigation control for MDS
x86/speculation/mds: Conditionally clear CPU buffers on idle entry
x86/kvm/vmx: Add MDS protection when L1D Flush is not active
x86/speculation/mds: Clear CPU buffers on exit to user
x86/speculation/mds: Add mds_clear_cpu_buffers()
x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests
x86/speculation/mds: Add BUG_MSBDS_ONLY
x86/speculation/mds: Add basic bug infrastructure for MDS
x86/speculation: Consolidate CPU whitelists
x86/msr-index: Cleanup bit defines

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Fix Committed

** Affects: linux (Ubuntu Eoan)
 Importance: Undecided
 Status: Fix Committed


** Tags: kernel-stable-tracking-bug

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

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

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: Confirmed

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

Title:
  Eoan update: v5.1.2 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

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:

 v5.1.2 upstream stable release
 from git://git.kernel.org/

  
  Linux 5.1.2
  x86/speculation/mds: Fix documentation typo
  Documentation: Correct the possible MDS sysfs values
  x86/mds: Add MDSUM variant to the MDS documentation
  x86/speculation/mds: Add 'mitigations=' support for MDS
  s390/speculation: Support 'mitigations=' cmdline option
  powerpc/speculation: Support 'mitigations=' cmdline option
  x86/speculation: Support 'mitigations=' cmdline option
  cpu/speculation: Add 'mitigations=' cmdline option
  x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off
  x86/speculation/mds: Fix comment
  x86/speculation/mds: Add SMT warning message
  x86/speculation: Move arch_smt_update() call to after mitigation decisions
  x86/speculation/mds: Add mds=full,nosmt cmdline option
  Documentation: Add MDS vulnerability documentation
  Documentation: Move L1TF to separate directory
  x86/speculation/mds: Add mitigation mode VMWERV
  x86/speculation/mds: Add sysfs reporting for MDS
  x86/speculation/mds: Add mitigation control for MDS
  x86/speculation/mds: Conditionally clear CPU buffers on idle entry
  x86/kvm/vmx: Add MDS protection when L1D Flush is not active
  x86/speculation/mds: Clear CPU buffers on exit to user
  x86/speculation/mds: Add mds_clear_cpu_buffers()
  x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests
  x86/speculation/mds: Add BUG_MSBDS_ONLY
  x86/speculation/mds: Add basic bug infrastructure for MDS
  x86/speculation: Consolidate CPU whitelists
  x86/msr-index: Cleanup bit defines

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1829046] Re: Eoan update: v5.1.1 upstream stable release

2019-05-14 Thread Seth Forshee
** Changed in: linux (Ubuntu Eoan)
   Status: In Progress => Fix Committed

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

Title:
  Eoan update: v5.1.1 upstream stable release

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

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:

     v5.1.1 upstream stable release
     from git://git.kernel.org/

  Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup()
  ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings
  staging: greybus: power_supply: fix prop-descriptor request size
  staging: wilc1000: Avoid GFP_KERNEL allocation from atomic context.
  staging: most: cdev: fix chrdev_region leak in mod_exit
  staging: most: sound: pass correct device when creating a sound card
  usb: dwc3: Allow building USB_DWC3_QCOM without EXTCON
  usb: dwc3: Fix default lpm_nyet_threshold value
  USB: serial: f81232: fix interrupt worker not stop
  USB: cdc-acm: fix unthrottle races
  usb-storage: Set virt_boundary_mask to avoid SG overflows
  genirq: Prevent use-after-free and work list corruption
  intel_th: pci: Add Comet Lake support
  iio: adc: qcom-spmi-adc5: Fix of-based module autoloading
  cpufreq: armada-37xx: fix frequency calculation for opp
  ACPI / LPSS: Use acpi_lpss_* instead of acpi_subsys_* functions for hibernate
  soc: sunxi: Fix missing dependency on REGMAP_MMIO
  scsi: lpfc: change snprintf to scnprintf for possible overflow
  scsi: qla2xxx: Fix incorrect region-size setting in optrom SYSFS routines
  scsi: qla2xxx: Set remote port devloss timeout to 0
  scsi: qla2xxx: Fix device staying in blocked state
  Bluetooth: hidp: fix buffer overflow
  Bluetooth: Align minimum encryption key size for LE and BR/EDR connections
  Bluetooth: Fix not initializing L2CAP tx_credits
  Bluetooth: hci_bcm: Fix empty regulator supplies for Intel Macs
  UAS: fix alignment of scatter/gather segments
  ASoC: Intel: avoid Oops if DMA setup fails
  i3c: Fix a shift wrap bug in i3c_bus_set_addr_slot_status()
  locking/futex: Allow low-level atomic operations to return -EAGAIN
  arm64: futex: Bound number of LDXR/STXR loops in FUTEX_WAKE_OP
  Linux 5.1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829046/+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 1829046] [NEW] Eoan update: v5.1.1 upstream stable release

2019-05-14 Thread Seth Forshee
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:

   v5.1.1 upstream stable release
   from git://git.kernel.org/

Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup()
ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings
staging: greybus: power_supply: fix prop-descriptor request size
staging: wilc1000: Avoid GFP_KERNEL allocation from atomic context.
staging: most: cdev: fix chrdev_region leak in mod_exit
staging: most: sound: pass correct device when creating a sound card
usb: dwc3: Allow building USB_DWC3_QCOM without EXTCON
usb: dwc3: Fix default lpm_nyet_threshold value
USB: serial: f81232: fix interrupt worker not stop
USB: cdc-acm: fix unthrottle races
usb-storage: Set virt_boundary_mask to avoid SG overflows
genirq: Prevent use-after-free and work list corruption
intel_th: pci: Add Comet Lake support
iio: adc: qcom-spmi-adc5: Fix of-based module autoloading
cpufreq: armada-37xx: fix frequency calculation for opp
ACPI / LPSS: Use acpi_lpss_* instead of acpi_subsys_* functions for hibernate
soc: sunxi: Fix missing dependency on REGMAP_MMIO
scsi: lpfc: change snprintf to scnprintf for possible overflow
scsi: qla2xxx: Fix incorrect region-size setting in optrom SYSFS routines
scsi: qla2xxx: Set remote port devloss timeout to 0
scsi: qla2xxx: Fix device staying in blocked state
Bluetooth: hidp: fix buffer overflow
Bluetooth: Align minimum encryption key size for LE and BR/EDR connections
Bluetooth: Fix not initializing L2CAP tx_credits
Bluetooth: hci_bcm: Fix empty regulator supplies for Intel Macs
UAS: fix alignment of scatter/gather segments
ASoC: Intel: avoid Oops if DMA setup fails
i3c: Fix a shift wrap bug in i3c_bus_set_addr_slot_status()
locking/futex: Allow low-level atomic operations to return -EAGAIN
arm64: futex: Bound number of LDXR/STXR loops in FUTEX_WAKE_OP
Linux 5.1.1

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Affects: linux (Ubuntu Eoan)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

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

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: Confirmed

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

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

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

** 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:
+    v5.1.1 upstream stable release
+    from git://git.kernel.org/
  
-v5.1.1 upstream stable release
-from git://git.kernel.org/
+ Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup()
+ ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings
+ staging: greybus: power_supply: fix prop-descriptor request size
+ staging: wilc1000: Avoid GFP_KERNEL allocation from atomic context.
+ staging: most: cdev: fix chrdev_region leak in mod_exit
+ staging: most: sound: pass correct device when creating a sound card
+ usb: dwc3: Allow building USB_DWC3_QCOM without EXTCON
+ usb: dwc3: Fix default lpm_nyet_threshold value
+ USB: serial: f81232: fix interrupt worker not stop
+ USB: cdc-acm: fix unthrottle races
+ usb-storage: Set virt_boundary_mask to avoid SG overflows
+ genirq: Prevent use-after-free and work list corruption
+ intel_th: pci: Add Comet Lake support
+ iio: adc: qcom-spmi-adc5: Fix of-based module autoloading
+ cpufreq: armada-37xx: fix frequency calculation fo

[Kernel-packages] [Bug 1826410] Re: Please package libbpf (which is done out of the kernel src) in Debian [for 19.10]

2019-05-14 Thread Seth Forshee
** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1826410

Title:
  Please package libbpf (which is done out of the kernel src) in Debian
  [for 19.10]

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  Hi,
  Debian packages libbpf and so far does so out of the kernel source [1].
  There is some movement to separate that from the kernel source [2] but this 
isn't ready yet. So far it is just a sync of the subtree out of the kernel 
sources.

  Since we do not share our kernel packaging we will not get this for-free 
without doing anything.
  If there will be an ITP about it in Debian I'll let you know and we can abort 
this, but unless that really happens I wanted to ask if you could as well build 
the libbpf* packages for 19.10 and onward?

  Note: this is not the same bpf lib as [3] despite the similarity in
  names.

  Reasoning:
  BPF becomes more and more important in general and is used in the kernel for 
many things. In the case that brought it to my attention it will be a PMD of 
DPDK that will need it to control XDP [4]. And XDP in general is an interesting 
and rising feature for network acceleration - I'd think it would be helpful to 
have this package around in Ubuntu.

  [1]: https://packages.debian.org/sid/libbpf-dev
  [2]: https://github.com/libbpf/libbpf
  [3]: https://github.com/iovisor/bcc
  [4]: https://www.iovisor.org/technology/xdp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826410/+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 1827122] Re: shiftfs: lock security sensitive superblock flags

2019-05-14 Thread Seth Forshee
** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  shiftfs: lock security sensitive superblock flags

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  New

Bug description:
  Felix Abecassis from Nvidia recently reported the following bug:

  "I recently upgraded to Ubuntu 19.04, and decided to experiment with shiftfs 
and unprivileged overlay.
  My goal was to have root (in my case, the docker daemon) download overlay 
layers and then have multiple users leveraging shiftfs + unprivileged overlay 
to assemble the rootfs without copying and chowning.
  For obvious security reasons, I want root to expose these layers as 
read-only, any change will be to the user-owned "upper" filesystem.

  Here's what I'm currently doing:
  # Exposing the root-owned docker layers, the "ro" option seems to have no 
impact on later userns mounts.
  sudo mount -t shiftfs -o mark,ro /var/lib/docker/overlay2 /mnt

  # Creating a userns as uid 1000, then mounting the shiftfs.
  unshare -U -m -r
  cd $(mktemp -d)
  mkdir shiftfs upper work merged
  # I can pass "ro" to the mount to get the behavior I want.
  mount -t shiftfs -o ro /mnt shiftfs

  mount -t overlay overlay -o
  
'lowerdir=shiftfs/c34c048514dcab5fc1bddf6d99681645786021e4a5b239972ec688386852a666/diff:[...],upperdir=upper,workdir=work'
  merged

  This works fine (excluding the xattrs issue with unprivileged
  overlay), but I can't rely on users to pass the "ro" option to their
  mounts. Without it, any user would be able to write to
  /var/lib/docker/overlay2 through the shiftfs mountpoint.

  I couldn't find a way to enforce do that, is there one? Is it possible to 
have one?
  I quickly attempted to have root do the shiftfs mounts for the users, but it 
seems the shift is always for the root of the current userns, and can't be done 
for another user."

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


Re: [Kernel-packages] [Bug 1828564] Re: Update brcmfmac43455-sdio for rpi3b+/a+

2019-05-10 Thread Seth Forshee
On Fri, May 10, 2019 at 03:19:01PM -, Jonathan Cave wrote:
> Thanks for the info, I wasn't aware of what policy was for firmware.

It's the same as for the rest of the distro.

> As far as I can tell this firmware is all non-free, for example it
> appears to come from this repo https://github.com/RPi-Distro/firmware-
> nonfree and be in a non-free package in debian:
> https://packages.debian.org/sid/firmware-brcm80211. You would have to
> let me know what constitutes upstream for linux-firmware.

This is upstream:

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/

There are updates to brcmfmac firmware files since bionic, but I'm not
sure which specific files raspi2 uses.

> At this time I'm just investigating why we see regular failures on some
> of our devices when attempting to connect to APs in our certification
> lab, but haven't been able to identify any cause or solid reproduction
> scenario as yet. Given I spotted this information I thought I would
> raise it in case it was an omission.

We've had repeated requests for raspi2 firmware files, but most of the
time there isn't a clear license for distribution.

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

Title:
  Update brcmfmac43455-sdio for rpi3b+/a+

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  The firmware identified is used on Raspberry Pi devices that are
  reference devices for Ubuntu Core. The firmware currently carried in
  Bionic is quite old:

  brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Mar  1 2015
  07:29:38 version 7.45.18 (r538002) FWID 01-6a2c8ad4

  For comparison Raspbian has:

  brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Feb 27 2018
  03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04

  Could the newer firmware be made available in bionic updates?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1828564/+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 1828564] Re: Update brcmfmac43455-sdio for rpi3b+/a+

2019-05-10 Thread Seth Forshee
For SRU we need a justification -- fixing specific bugs, important new
functionality, etc. Having "quite old" firmware is not sufficient
justification. If you wish for newer firmware to be included in bionic
please specify what bugs or features necessitate the update.

We also have to be sure that the firmware has been licensed in a way
that allows distribution in our linux-firmware package. We can be sure
that the firmware in upstream linux-firmware has been, but we've found
in the past that sometimes the licensing situation with raspi firmware
files is unclear. Please specify which specific firmware files are
required, and if not from upstream linux-firmware what license they have
for distribution. Thanks!

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

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

Title:
  Update brcmfmac43455-sdio for rpi3b+/a+

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  The firmware identified is used on Raspberry Pi devices that are
  reference devices for Ubuntu Core. The firmware currently carried in
  Bionic is quite old:

  brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Mar  1 2015
  07:29:38 version 7.45.18 (r538002) FWID 01-6a2c8ad4

  For comparison Raspbian has:

  brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Feb 27 2018
  03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04

  Could the newer firmware be made available in bionic updates?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1828564/+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 1782608] Re: Fresh Ubuntu 18.04 install uses wrong Realtek wired network driver.

2019-05-08 Thread Seth Forshee
This bug has nothing to do with linux-firmware, changing to affect
linux.

I don't know that I'd say the "wrong" driver is being selected here. It
sounds like there is an in-kernel driver that supports the NIC, but does
not seem to support it at full speed. So there is a kernel issue here,
but you're likely to make more headway reporting it to the upstream
driver maintainer. We can help you do that if you like.

Your complaint seems to be that you weren't offered the dkms driver by
default. I know there used to be a system that offered extra drivers
during installation. I assume it's still there, but I'm struggling to
remember what it was named, and I don't know what the procedure is for
updating it.

** Package changed: linux-firmware (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/1782608

Title:
  Fresh Ubuntu 18.04 install uses wrong Realtek wired network driver.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi there,

  Installing Ubuntu 18.04 on my newish laptop which contains a Realtek
  8168 NIC seems to use the r8169 driver by default, and should use the
  r8168 in order to work properly. To fix, I removed or blocked the 8169
  driver, installed the 8168 driver and then reconfigured NetworkManager
  - which was quite difficult for a new user like me. I've included
  details from my system since I addressed the issue yesterday.

  Please let me know if there's anything I can do to help more.

  ~$ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  ~$ apt-cache policy r8168-dkms 
  r8168-dkms:
Installed: 8.045.08-2
Candidate: 8.045.08-2
Version table:
   *** 8.045.08-2 500
  500 http://ca.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://ca.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  100 /var/lib/dpkg/status


  ~$ neofetch
  OS: Ubuntu 18.04 LTS x86_64 
  Host: Aspire A515-51G V1.10 
  Kernel: 4.15.0-23-generic 
  Uptime: 30 mins 
  Packages: 2124 
  Shell: bash 4.4.19 
  Resolution: 1920x1080 
  Terminal: gnome-terminal 
  CPU: Intel i5-8250U (8) @ 3.400GHz 
  GPU: Intel UHD Graphics 620 
  GPU: NVIDIA GeForce MX150 
  Memory: 3457MiB / 7725MiB 

  ~$ sudo lshw -c network
*-network 
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0.1
 bus info: pci@:02:00.1
 logical name: enp2s0f1
 version: 12
 serial: 98:29:a6:40:b5:f1
 size: 10Mbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8168 
driverversion=8.045.08-NAPI duplex=half latency=0 link=no multicast=yes 
port=twisted pair speed=10Mbit/s
 resources: irq:128 ioport:3000(size=256) memory:a4204000-a4204fff 
memory:a420-a4203fff

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Thu Jul 19 09:56:08 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-07-16 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782608/+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 1823753] Re: arm64: cma_alloc errors at boot

2019-05-03 Thread Seth Forshee
That wastage is pretty awful.

You might want try a patch to at least ratelimit the cma_alloc errors.
Not that it's a real solution, but it might be something we can apply to
mitigate the problem short-term while continuing to search for something
better.

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

Title:
  arm64: cma_alloc errors at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On some arm64 systems[*] we are seeing a spew of messages on the
  console:

  [   19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12

  This appears to be non-fatal - impacted systems all eventually boot.
  But, at least in the case of the HP m400, it slows down boot enough
  that MAAS' default timeout will expire before completing deployment.

  [*] Observed on a HiSilicon D06 w/ SMMU disabled in the BIOS, as well
  as an HP m400 (APM X-Gene) cartridge - although, not on another one
  that - in theory - should be identical.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+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 1827112] [NEW] nvidia-graphics-drivers-418 418.56-0ubuntu1 ADT test failure with linux 5.1.0-1.1

2019-04-30 Thread Seth Forshee
Public bug reported:

Testing failed on:

** Affects: nvidia-graphics-drivers-418 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  nvidia-graphics-drivers-418 418.56-0ubuntu1 ADT test failure with
  linux 5.1.0-1.1

Status in nvidia-graphics-drivers-418 package in Ubuntu:
  New

Bug description:
  Testing failed on:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1827112/+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 1827108] [NEW] linux 5.1.0-1.1 ADT test failure with linux 5.1.0-1.1

2019-04-30 Thread Seth Forshee
Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/l/linux/20190426_194249_63a8b@/log.gz
arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/arm64/l/linux/20190429_154801_63a8b@/log.gz
ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/ppc64el/l/linux/20190429_180436_06106@/log.gz
s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/s390x/l/linux/20190429_170728_06106@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  linux 5.1.0-1.1 ADT test failure with linux 5.1.0-1.1

Status in linux package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/l/linux/20190426_194249_63a8b@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/arm64/l/linux/20190429_154801_63a8b@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/ppc64el/l/linux/20190429_180436_06106@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/s390x/l/linux/20190429_170728_06106@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827108/+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 1827111] [NEW] nvidia-graphics-drivers-390 390.116-0ubuntu1 ADT test failure with linux 5.1.0-1.1

2019-04-30 Thread Seth Forshee
Public bug reported:

Testing failed on:

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  nvidia-graphics-drivers-390 390.116-0ubuntu1 ADT test failure with
  linux 5.1.0-1.1

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

Bug description:
  Testing failed on:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1827111/+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 1827117] [NEW] zfs-linux 0.7.12-1ubuntu5 ADT test failure with linux 5.1.0-1.1

2019-04-30 Thread Seth Forshee
Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/z/zfs-linux/20190429_124800_98faf@/log.gz
arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/arm64/z/zfs-linux/20190430_162709_2c370@/log.gz
ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/ppc64el/z/zfs-linux/20190429_155705_2c370@/log.gz
s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/s390x/z/zfs-linux/20190429_152755_2c370@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  zfs-linux 0.7.12-1ubuntu5 ADT test failure with linux 5.1.0-1.1

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/z/zfs-linux/20190429_124800_98faf@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/arm64/z/zfs-linux/20190430_162709_2c370@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/ppc64el/z/zfs-linux/20190429_155705_2c370@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/s390x/z/zfs-linux/20190429_152755_2c370@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1827117/+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 1827100] [NEW] bcmwl 6.30.223.271+bdcom-0ubuntu4 ADT test failure with linux 5.1.0-1.1

2019-04-30 Thread Seth Forshee
Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/b/bcmwl/20190429_132741_e6057@/log.gz
i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/i386/b/bcmwl/20190429_124054_e6057@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  bcmwl 6.30.223.271+bdcom-0ubuntu4 ADT test failure with linux
  5.1.0-1.1

Status in bcmwl package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/b/bcmwl/20190429_132741_e6057@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/i386/b/bcmwl/20190429_124054_e6057@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1827100/+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 1823753] Re: arm64: cma_alloc errors at boot

2019-04-25 Thread Seth Forshee
I only had time to look briefly, but here's a few notes. Firstly, a
workaround for now is passing cma=0 on the kernel command line.

I feel like there must be something wrong here if everything just works
fine with CMA turned off, because obviously devices are getting CMA
allocations when they don't really need them. I'm not familiar with CMA,
but my assumption would be that you want as small a region as possible
for it and thus you want to only use it for devices where it's actually
necessary. Shooting from the hip I'd guess that one of two things is
wrong, either some devices are doing their allocations wrong and getting
CMA memory when they don't need it, or the DMA allocator is over zealous
in its use of CMA.

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

Title:
  arm64: cma_alloc errors at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On some arm64 systems[*] we are seeing a spew of messages on the
  console:

  [   19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
  [   19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
  [   19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12

  This appears to be non-fatal - impacted systems all eventually boot.
  But, at least in the case of the HP m400, it slows down boot enough
  that MAAS' default timeout will expire before completing deployment.

  [*] Observed on a HiSilicon D06 w/ SMMU disabled in the BIOS, as well
  as an HP m400 (APM X-Gene) cartridge - although, not on another one
  that - in theory - should be identical.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+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 1825993] Re: iwlwifi microcode error detected using hostapd with Intel 3168 in a NUC6CAYH

2019-04-24 Thread Seth Forshee
Have you already tested newer firmware to see if it fixes the issue? The
latest firmware can be downloaded from here:

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/plain/iwlwifi-3168-29.ucode

Then you need to place the file in /lib/firmware. I recommend you keep a
backup of the old file:

# mv /lib/firmware/iwlwifi-3168-29.ucode 
/lib/firmware/iwlwifi-3168-29.ucode.orig
# mv iwlwifi-3168-29.ucode /lib/firmware

Then reboot to start using the new firmware. Let me know if that fixes
the issue. If not, I suggest you follow up filing a bug as Emmanuel
suggested as only Intel can help you resolve this issue.

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

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

Title:
  iwlwifi microcode error detected using hostapd with Intel  3168 in a
  NUC6CAYH

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  I found a similar, fixed, bug with another Intel chip.  I believe the
  upstream fix from Intel addressed my 3168, but it looks like the fix
  released in linux-firmware only addresses the 8265.

  https://bugs.launchpad.net/ubuntu/+bug/1808389

  I only see this occur in AP mode, and not in managed mode (i.e.,
  hostapd triggers it, but wpa_supplicant does not).  The following
  repeats a couple times a second indefinitely:

  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.817625] iwlwifi 
:02:00.0: Microcode SW error detected.  Restarting 0x200.
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.818642] iwlwifi 
:02:00.0: Start IWL Error Log Dump:
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.819698] iwlwifi 
:02:00.0: Status: 0x0100, count: 6
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.821046] iwlwifi 
:02:00.0: Loaded firmware version: 27.541033.0
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.822370] iwlwifi 
:02:00.0: 0x3068 | ADVANCED_SYSASSERT  
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.823725] iwlwifi 
:02:00.0: 0x0230 | trm_hw_status0
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.825086] iwlwifi 
:02:00.0: 0x | trm_hw_status1
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.826426] iwlwifi 
:02:00.0: 0x00043D2C | branchlink2
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.827790] iwlwifi 
:02:00.0: 0x0004AEDE | interruptlink1
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.828751] iwlwifi 
:02:00.0: 0x | interruptlink2
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.829679] iwlwifi 
:02:00.0: 0x0064 | data1
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.830606] iwlwifi 
:02:00.0: 0x0032 | data2
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.831523] iwlwifi 
:02:00.0: 0x00FF | data3
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.832442] iwlwifi 
:02:00.0: 0x | beacon time
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.833355] iwlwifi 
:02:00.0: 0x0002920C | tsf low
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.834266] iwlwifi 
:02:00.0: 0x | tsf hi
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.835177] iwlwifi 
:02:00.0: 0x | time gp1
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.836098] iwlwifi 
:02:00.0: 0x0002920C | time gp2
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.837013] iwlwifi 
:02:00.0: 0x0001 | uCode revision type
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.837939] iwlwifi 
:02:00.0: 0x001B | uCode version major
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.838864] iwlwifi 
:02:00.0: 0x00084169 | uCode version minor
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.839792] iwlwifi 
:02:00.0: 0x0220 | hw version
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.840715] iwlwifi 
:02:00.0: 0x00C89200 | board version
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.841660] iwlwifi 
:02:00.0: 0x0028011C | hcmd
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.842605] iwlwifi 
:02:00.0: 0x24022000 | isr0
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.843545] iwlwifi 
:02:00.0: 0x0100 | isr1
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.844498] iwlwifi 
:02:00.0: 0x0002 | isr2
  /var/log/syslog.5.gz:Apr 18 15:59:54 pinot kernel: [137784.845435] iwlwifi 
:02:00.0: 0x4041FCC0 | isr3

  lshw output:

 *-network
  description: Wireless interface
  product: Dual Band Wireless-AC 3168NGW [Stone Peak]
  vendor: Intel Corporation

[Kernel-packages] [Bug 1817518] Re: Bluetooth not working (Intel CyclonePeak)

2019-04-24 Thread Seth Forshee
** Changed in: linux-firmware (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Changed in: linux-firmware (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Changed in: linux-firmware (Ubuntu Disco)
   Status: In Progress => Fix Committed

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

Title:
  Bluetooth not working (Intel CyclonePeak)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Won't Fix
Status in linux-firmware source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released
Status in linux-firmware source package in Cosmic:
  Fix Committed
Status in linux-firmware source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  New Intel bluetooth device 8087:0029 takes a new ID to be enabled, or the 
device will not work.

  [Fix]
  2da711bcebe81 Bluetooth: btusb: Add support for Intel bluetooth device 
8087:0029

  This change requires new firmware blob as well, which is to be
  upstreamed & backported from linux-firmware.

  [Test Case]
  Verified on AX200NGW & 22560NGW chips. Use hciconfig to list probed hci 
device.

  [Regression Risk]
  Low. This patch effectively adds new id match for a unsupported (yet) device. 
The most lines of the patches actually introduces an helper function that 
generates firmware blob name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1817518/+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


Re: [Kernel-packages] [Bug 1825413] Re: mdadm, mkfs, other io commands hang, stuck task, bad rip

2019-04-22 Thread Seth Forshee
On Mon, Apr 22, 2019 at 08:20:30PM -, Ryan Harper wrote:
> Hi Seth,
> 
> notice only one of the stack tracks have the floppy, the mdadm one does
> not.  I've also recreated this on a qemu q35 machine type which does not
> include the floppy device.

I looked at the madm stack trace, and I was assuming that it occurred
during the same boot as the other one. I suppose I shouldn't have, but
it would make sense. mdadm appears to be blocked on a block device's
bd_mutex, so the cause is probably something else that has hung while
holding that mutex. The mkfs stack trace would be just the kind of thing
to create the mdadm stack trace, if it were trying to open the same
device.

So, were those traces from a single boot or from different boots?

Can you provide stack trace(s) from the q35 machine type for comparison?
Thanks!

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

Title:
  mdadm, mkfs, other io commands hang, stuck task, bad rip

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  1. disco
  2. # apt-cache policy linux-image-virtual
  linux-image-virtual:
Installed: 5.0.0.13.14
Candidate: 5.0.0.13.14
Version table:
   *** 5.0.0.13.14 500
  500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status
  3. installation completes sucessfully
  4. Running an installation of Disco creating filesystems and probing things 
will hang (stuck task) every so often.  When it happens, the kernel throws an 
oops and bad rip value.

  [  967.810391] INFO: task mdadm:12213 blocked for more than 120 seconds.
  [  967.811787]   Tainted: P   O  5.0.0-13-generic #14-Ubuntu
  [  967.813330] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.815500] mdadm   D0 12213  12207 0x
  [  967.815503] Call Trace:
  [  967.815509]  __schedule+0x2d0/0x840
  [  967.815511]  ? __switch_to_asm+0x40/0x70
  [  967.815512]  ? __switch_to_asm+0x34/0x70
  [  967.815514]  schedule+0x2c/0x70
  [  967.815516]  schedule_preempt_disabled+0xe/0x10
  [  967.815518]  __mutex_lock.isra.10+0x2e4/0x4c0
  [  967.815522]  ? exact_lock+0x11/0x20
  [  967.815524]  __mutex_lock_slowpath+0x13/0x20
  [  967.815528]  mutex_lock+0x2c/0x30
  [  967.815530]  __blkdev_get+0x7b/0x550
  [  967.815532]  ? bd_acquire+0xd0/0xd0
  [  967.815533]  blkdev_get+0x10c/0x330
  [  967.815535]  ? bd_acquire+0xd0/0xd0
  [  967.815537]  blkdev_open+0x92/0x100
  [  967.815539]  do_dentry_open+0x143/0x3a0
  [  967.815540]  vfs_open+0x2d/0x30
  [  967.815542]  path_openat+0x2d4/0x16d0
  [  967.815547]  ? put_device+0x17/0x20
  [  967.815552]  ? scsi_device_put+0x2b/0x30
  [  967.815553]  do_filp_open+0x93/0x100
  [  967.81]  ? strncpy_from_user+0x56/0x1b0
  [  967.815558]  ? __alloc_fd+0x46/0x140
  [  967.815560]  do_sys_open+0x177/0x280
  [  967.815561]  ? _cond_resched+0x19/0x30
  [  967.815563]  __x64_sys_openat+0x20/0x30
  [  967.815566]  do_syscall_64+0x5a/0x110
  [  967.815567]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  967.815568] RIP: 0033:0x7faa36406cce
  [  967.815572] Code: Bad RIP value.
  [  967.815573] RSP: 002b:7ffedb663f80 EFLAGS: 0246 ORIG_RAX: 
0101
  [  967.815574] RAX: ffda RBX: 4000 RCX: 
7faa36406cce
  [  967.815575] RDX: 4000 RSI: 564df70257b0 RDI: 
ff9c
  [  967.815576] RBP: 564df70257b0 R08: 564df70257b0 R09: 

  [  967.815576] R10:  R11: 0246 R12: 
7ffedb664240
  [  967.815577] R13:  R14: 0001 R15: 
564df7023e00

  [  967.799227] INFO: task mkfs.btrfs:3767 blocked for more than 120 seconds.
  [  967.803509]   Tainted: P   O  5.0.0-13-generic #14-Ubuntu
  [  967.807192] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.810235] mkfs.btrfs  D0  3767   1866 0x
  [  967.810239] Call Trace:
  [  967.810251]  __schedule+0x2d0/0x840
  [  967.810254]  ? __switch_to_asm+0x34/0x70
  [  967.810256]  ? __switch_to_asm+0x40/0x70
  [  967.810258]  schedule+0x2c/0x70
  [  967.810260]  schedule_timeout+0x258/0x360
  [  967.810277]  wait_for_completion+0xb7/0x140
  [  967.810281]  ? wake_up_q+0x80/0x80
  [  967.810293]  __floppy_read_block_0+0x138/0x190 [floppy]
  [  967.810298]  ? floppy_cmos_show+0x30/0x30 [floppy]
  [  967.810302]  floppy_revalidate+0xf8/0x230 [floppy]
  [  967.810307]  check_disk_change+0x62/0x70
  [  967.810309]  floppy_open+0x2ae/0x380 [floppy]
  [  967.810311]  __blkdev_get+0xe5/0x550
  [  967.810313]  ? bd_acquire+0xd0/0xd0
  [  967.810315]  blkdev_get+0x10c/0x330
  [  967.810316]  ? bd_acquire+0xd0/0xd0
  [  967.810318]  blkdev_open+0x92/0x100
  [  967.810321]  do_dentry_open+0x143/0x3a0
  [  967.810323]  vfs_open+0x2d/0x30
  [  967.810326]  

[Kernel-packages] [Bug 1825413] Re: mdadm, mkfs, other io commands hang, stuck task, bad rip

2019-04-19 Thread Seth Forshee
Looks like something going wrong with the floppy driver. From the
description this sounds like a race. I note that a bug with essentially
the same stack trace was fixed in 4.20, de7b75d82f70 "floppy: fix race
condition in __floppy_read_block_0()." We have that fix though, so not
sure what is causing it here.

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

Title:
  mdadm, mkfs, other io commands hang, stuck task, bad rip

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  1. disco
  2. # apt-cache policy linux-image-virtual
  linux-image-virtual:
Installed: 5.0.0.13.14
Candidate: 5.0.0.13.14
Version table:
   *** 5.0.0.13.14 500
  500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status
  3. installation completes sucessfully
  4. Running an installation of Disco creating filesystems and probing things 
will hang (stuck task) every so often.  When it happens, the kernel throws an 
oops and bad rip value.

  [  967.810391] INFO: task mdadm:12213 blocked for more than 120 seconds.
  [  967.811787]   Tainted: P   O  5.0.0-13-generic #14-Ubuntu
  [  967.813330] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.815500] mdadm   D0 12213  12207 0x
  [  967.815503] Call Trace:
  [  967.815509]  __schedule+0x2d0/0x840
  [  967.815511]  ? __switch_to_asm+0x40/0x70
  [  967.815512]  ? __switch_to_asm+0x34/0x70
  [  967.815514]  schedule+0x2c/0x70
  [  967.815516]  schedule_preempt_disabled+0xe/0x10
  [  967.815518]  __mutex_lock.isra.10+0x2e4/0x4c0
  [  967.815522]  ? exact_lock+0x11/0x20
  [  967.815524]  __mutex_lock_slowpath+0x13/0x20
  [  967.815528]  mutex_lock+0x2c/0x30
  [  967.815530]  __blkdev_get+0x7b/0x550
  [  967.815532]  ? bd_acquire+0xd0/0xd0
  [  967.815533]  blkdev_get+0x10c/0x330
  [  967.815535]  ? bd_acquire+0xd0/0xd0
  [  967.815537]  blkdev_open+0x92/0x100
  [  967.815539]  do_dentry_open+0x143/0x3a0
  [  967.815540]  vfs_open+0x2d/0x30
  [  967.815542]  path_openat+0x2d4/0x16d0
  [  967.815547]  ? put_device+0x17/0x20
  [  967.815552]  ? scsi_device_put+0x2b/0x30
  [  967.815553]  do_filp_open+0x93/0x100
  [  967.81]  ? strncpy_from_user+0x56/0x1b0
  [  967.815558]  ? __alloc_fd+0x46/0x140
  [  967.815560]  do_sys_open+0x177/0x280
  [  967.815561]  ? _cond_resched+0x19/0x30
  [  967.815563]  __x64_sys_openat+0x20/0x30
  [  967.815566]  do_syscall_64+0x5a/0x110
  [  967.815567]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  967.815568] RIP: 0033:0x7faa36406cce
  [  967.815572] Code: Bad RIP value.
  [  967.815573] RSP: 002b:7ffedb663f80 EFLAGS: 0246 ORIG_RAX: 
0101
  [  967.815574] RAX: ffda RBX: 4000 RCX: 
7faa36406cce
  [  967.815575] RDX: 4000 RSI: 564df70257b0 RDI: 
ff9c
  [  967.815576] RBP: 564df70257b0 R08: 564df70257b0 R09: 

  [  967.815576] R10:  R11: 0246 R12: 
7ffedb664240
  [  967.815577] R13:  R14: 0001 R15: 
564df7023e00

  [  967.799227] INFO: task mkfs.btrfs:3767 blocked for more than 120 seconds.
  [  967.803509]   Tainted: P   O  5.0.0-13-generic #14-Ubuntu
  [  967.807192] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  967.810235] mkfs.btrfs  D0  3767   1866 0x
  [  967.810239] Call Trace:
  [  967.810251]  __schedule+0x2d0/0x840
  [  967.810254]  ? __switch_to_asm+0x34/0x70
  [  967.810256]  ? __switch_to_asm+0x40/0x70
  [  967.810258]  schedule+0x2c/0x70
  [  967.810260]  schedule_timeout+0x258/0x360
  [  967.810277]  wait_for_completion+0xb7/0x140
  [  967.810281]  ? wake_up_q+0x80/0x80
  [  967.810293]  __floppy_read_block_0+0x138/0x190 [floppy]
  [  967.810298]  ? floppy_cmos_show+0x30/0x30 [floppy]
  [  967.810302]  floppy_revalidate+0xf8/0x230 [floppy]
  [  967.810307]  check_disk_change+0x62/0x70
  [  967.810309]  floppy_open+0x2ae/0x380 [floppy]
  [  967.810311]  __blkdev_get+0xe5/0x550
  [  967.810313]  ? bd_acquire+0xd0/0xd0
  [  967.810315]  blkdev_get+0x10c/0x330
  [  967.810316]  ? bd_acquire+0xd0/0xd0
  [  967.810318]  blkdev_open+0x92/0x100
  [  967.810321]  do_dentry_open+0x143/0x3a0
  [  967.810323]  vfs_open+0x2d/0x30
  [  967.810326]  path_openat+0x2d4/0x16d0
  [  967.810328]  ? filename_lookup.part.60+0xe0/0x170
  [  967.810332]  ? strncpy_from_user+0x56/0x1b0
  [  967.810333]  do_filp_open+0x93/0x100
  [  967.810353]  ? strncpy_from_user+0x56/0x1b0
  [  967.810358]  ? __alloc_fd+0x46/0x140
  [  967.810360]  do_sys_open+0x177/0x280
  [  967.810362]  ? _cond_resched+0x19/0x30
  [  967.810364]  __x64_sys_openat+0x20/0x30
  [  967.810368]  do_syscall_64+0x5a/0x110
  [  967.810369]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  967.810372] RIP: 0033:0x7f46b99374db
  [ 

[Kernel-packages] [Bug 1825210] Re: [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel update

2019-04-18 Thread Seth Forshee
https://lists.ubuntu.com/archives/kernel-team/2019-April/100221.html

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

** Also affects: linux (Ubuntu Disco)
   Importance: High
 Assignee: Seth Forshee (sforshee)
   Status: 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/1825210

Title:
  [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel
  update

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

Bug description:
  [SRU Justification]

  Impact: The virtualbox package was updated in disco just prior to
  release, with numerous bug fixes. It is standard practice during
  development to sync our in-kernel source with the latest version of
  the virtualbox-guest-dkms package, however this upload was done so
  late in the release that there was not time to update the source in
  our kernel tree.

  Fix: Re-sync the vbox guest dkms drivers from virtualbox 6.0.6-dfsg-1.

  Regression Potential: This is a sync from the dkms package in the
  disco-release pocket, thus the code has presumably been tested against
  the Ubuntu Disco kernel. However, this is a very large pile of
  changes, and contains more than just bug fixes, so regressions are
  possible.

  Test Case: Boot a kernel with the updated driver in virtualbox and
  confirm that the guest drier functionality works as expected.

  ---

  * the changes are already in disco (vbox-guest-dkms), and they are fixes for 
the kernel 5.0.
  They might seem a lot of changes, but they are needed, and probably some of 
them are even CVE fixes...

  As said, vbox 6.0.6 includes lots of fixes for host/guest kernel modules, and 
they should be syncd when possible.
  thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825210/+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 1825210] Re: [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel update

2019-04-18 Thread Seth Forshee
** Description changed:

  [SRU Justification]
+ 
+ Impact: The virtualbox package was updated in disco just prior to
+ release, with numerous bug fixes. It is standard practice during
+ development to sync our in-kernel source with the latest version of the
+ virtualbox-guest-dkms package, however this upload was done so late in
+ the release that there was not time to update the source in our kernel
+ tree.
+ 
+ Fix: Re-sync the vbox guest dkms drivers from virtualbox 6.0.6-dfsg-1.
+ 
+ Regression Potential: This is a sync from the dkms package in the disco-
+ release pocket, thus the code has presumably been tested against the
+ Ubuntu Disco kernel. However, this is a very large pile of changes, and
+ contains more than just bug fixes, so regressions are possible.
+ 
+ Test Case: Boot a kernel with the updated driver in virtualbox and
+ confirm that the guest drier functionality works as expected.
+ 
+ ---
+ 
  * the changes are already in disco (vbox-guest-dkms), and they are fixes for 
the kernel 5.0.
  They might seem a lot of changes, but they are needed, and probably some of 
them are even CVE fixes...
  
  As said, vbox 6.0.6 includes lots of fixes for host/guest kernel modules, and 
they should be syncd when possible.
  thanks

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

Title:
  [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel
  update

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

Bug description:
  [SRU Justification]

  Impact: The virtualbox package was updated in disco just prior to
  release, with numerous bug fixes. It is standard practice during
  development to sync our in-kernel source with the latest version of
  the virtualbox-guest-dkms package, however this upload was done so
  late in the release that there was not time to update the source in
  our kernel tree.

  Fix: Re-sync the vbox guest dkms drivers from virtualbox 6.0.6-dfsg-1.

  Regression Potential: This is a sync from the dkms package in the
  disco-release pocket, thus the code has presumably been tested against
  the Ubuntu Disco kernel. However, this is a very large pile of
  changes, and contains more than just bug fixes, so regressions are
  possible.

  Test Case: Boot a kernel with the updated driver in virtualbox and
  confirm that the guest drier functionality works as expected.

  ---

  * the changes are already in disco (vbox-guest-dkms), and they are fixes for 
the kernel 5.0.
  They might seem a lot of changes, but they are needed, and probably some of 
them are even CVE fixes...

  As said, vbox 6.0.6 includes lots of fixes for host/guest kernel modules, and 
they should be syncd when possible.
  thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825210/+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 1824953] Re: package linux-image-5.0.0-11-generic 5.0.0-11.12 failed to install/upgrade: triggers looping, abandoned

2019-04-17 Thread Seth Forshee
There should have been some output about the triggers involved in the
loop; did you capture that? If not you might find it in
/var/log/apt/term.log.

My suspicion is that the problem lies in some other package's triggers
since the kernel triggers haven't changes since cosmic.

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

Title:
  package linux-image-5.0.0-11-generic 5.0.0-11.12 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Upgrade from cosmic to disco.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-11-generic 5.0.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniel 3431 F pulseaudio
  Date: Tue Apr 16 09:01:08 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2018-04-14 (366 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=0af0a12d-3b1e-4708-89c4-73f666ddc618 ro quiet splash vt.handoff=1
  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.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  SourcePackage: linux
  Title: package linux-image-5.0.0-11-generic 5.0.0-11.12 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-16 (0 days ago)
  dmi.bios.date: 02/21/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824953/+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 1824819] Re: linux: 5.0.0-13.14 -proposed tracker

2019-04-16 Thread Seth Forshee
** Tags added: regression-testing-passed

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

Title:
  linux: 5.0.0-13.14 -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-lrm 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:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1824889 (bionic/linux-hwe-edge)
  derivatives: bug 1824833 (linux-aws), bug 1824834 (linux-azure), bug 1824835 
(linux-gcp), bug 1824836 (linux-kvm)

  -- swm properties --
  phase: Testing
  phase-changed: Tuesday, 16. April 2019 09:29 UTC
  reason:
automated-testing: Stalled -- testing FAILED

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

2019-04-16 Thread Seth Forshee
** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: Confirmed => Invalid

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

Title:
  linux-azure: 5.0.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Invalid
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1824383
  phase: Ready for Signoff
  phase-changed: Saturday, 13. April 2019 01:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
stakeholder-signoff: Pending -- waiting for signoff

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

2019-04-16 Thread Seth Forshee
** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: Confirmed => Invalid

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

Title:
  linux-azure: 5.0.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Invalid
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1824819
  phase: Holding before Release
  phase-changed: Tuesday, 16. April 2019 13:54 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-release: Holding -- master bug not ready for release

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

2019-04-16 Thread Seth Forshee
** Tags added: regression-testing-passed

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

Title:
  linux-azure: 5.0.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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 Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1824819
  phase: Ready for Testing
  phase-changed: Tuesday, 16. April 2019 11:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Pending -- waiting for signoff

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

2019-04-16 Thread Seth Forshee
** Tags added: regression-testing-passed

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

Title:
  linux-gcp: 5.0.0-1004.4 -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:
  Fix Released
Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1824819
  phase: Testing
  phase-changed: Tuesday, 16. April 2019 07:11 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED

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

2019-04-16 Thread Seth Forshee
** Tags added: regression-testing-passed

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

Title:
  linux-aws: 5.0.0-1004.4 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1824819
  phase: Holding before Release
  phase-changed: Tuesday, 16. April 2019 12:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-release: Holding -- master bug not ready for release

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

2019-04-16 Thread Seth Forshee
** Tags added: regression-testing-passed

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

Title:
  linux-kvm: 5.0.0-1004.4 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1824819
  phase: Holding before Release
  phase-changed: Tuesday, 16. April 2019 12:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-release: Holding -- master bug not ready for release

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824836/+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 1824921] Re: package linux-firmware 1.175.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 2

2019-04-16 Thread Seth Forshee
>From the logs:

Setting up linux-firmware (1.175.1) ...
update-initramfs: Generating /boot/initrd.img-4.18.0-17-generic
/usr/sbin/mkinitramfs: 165: /usr/sbin/mkinitramfs: Cannot fork
/usr/sbin/mkinitramfs: 225: /usr/sbin/mkinitramfs: Cannot fork
/usr/sbin/mkinitramfs: 183: /usr/sbin/mkinitramfs: Cannot fork
/usr/sbin/update-initramfs: 145: /usr/sbin/update-initramfs: Cannot fork

This could be a systems resource issue, for example if you set a limit
on the number of processes allowed and reached that limit. It's hard to
pinpoint a cause with the limited information attached to this bug. If
you continue to have this issue, please collect dmesg output and attach
it here as that might provide some clues.

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

Title:
  package linux-firmware 1.175.3 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 2

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  System is a new build. Right off the lastest ISO. Updates were
  applied. There were issues applying updates. This system does have a
  mobile i7 and a Geforce 960m 4GB edition.

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: linux-firmware 1.175.3
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  Date: Thu Apr 11 20:06:27 2019
  Dependencies:
   
  Df:
   
  Dmesg:
   
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 2
  InstallationDate: Installed on 2019-04-11 (4 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.4
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.175.3 failed to install/upgrade: installed 
linux-firmware package post-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/linux-firmware/+bug/1824921/+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 1824834] Re: linux-azure: 5.0.0-1004.4 -proposed tracker

2019-04-15 Thread Seth Forshee
** Summary changed:

- linux-azure:  -proposed tracker
+ linux-azure: 5.0.0-1004.4 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

** 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) => Seth Forshee 
(sforshee)

** 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) => Seth Forshee 
(sforshee)

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

Title:
  linux-azure: 5.0.0-1004.4 -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 Kernel SRU Workflow stakeholder-signoff series:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1824819

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

2019-04-15 Thread Seth Forshee
** Summary changed:

- linux-aws:  -proposed tracker
+ linux-aws: 5.0.0-1004.4 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

** 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) => Seth Forshee 
(sforshee)

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

Title:
  linux-aws: 5.0.0-1004.4 -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 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-aws package in Ubuntu:
  New
Status in linux-aws source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1824819

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

2019-04-15 Thread Seth Forshee
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ derivatives: bug 1824833 (linux-aws)
  
  -- swm properties --
  phase: Packaging
  phase-changed: Monday, 15. April 2019 14:42 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- derivatives: bug 1824833 (linux-aws)
+ derivatives: bug 1824833 (linux-aws), bug 1824834 (linux-azure)
  
  -- swm properties --
  phase: Packaging
  phase-changed: Monday, 15. April 2019 14:42 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- derivatives: bug 1824833 (linux-aws), bug 1824834 (linux-azure)
+ derivatives: bug 1824833 (linux-aws), bug 1824834 (linux-azure), bug
+ 1824835 (linux-gcp)
  
  -- swm properties --
  phase: Packaging
  phase-changed: Monday, 15. April 2019 14:42 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  derivatives: bug 1824833 (linux-aws), bug 1824834 (linux-azure), bug
- 1824835 (linux-gcp)
+ 1824835 (linux-gcp), bug 1824836 (linux-kvm)
  
  -- swm properties --
  phase: Packaging
  phase-changed: Monday, 15. April 2019 14:42 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

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

Title:
  linux: 5.0.0-13.14 -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:
  New
Status in linux source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  derivatives: bug 1824833 (linux-aws), bug 1824834 (linux-azure), bug
  1824835 (linux-gcp), bug 1824836 (linux-kvm)

  -- swm properties --
  phase: Packaging
  phase-changed: Monday, 15. April 2019 14:42 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824819/+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 1824834] [NEW] linux-azure: -proposed tracker

2019-04-15 Thread Seth Forshee
Public bug reported:

This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.

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: 1824819

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/stakeholder-signoff
 Importance: Medium
 Assignee: linux-azure stakeholder signoff (linux-azure-signoff)
 Status: New

** Affects: linux-azure (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-azure (Ubuntu Disco)
 Importance: Medium
 Status: New


** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-d2019.04.15-1 kernel-sru-derivative-of-1824819

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/stakeholder-signoff
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-sru-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/stakeholder-signoff
 Assignee: (unassigned) => linux-azure stakeholder signoff 
(linux-azure-signoff)

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

** Tags added: disco

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

** Tags added: kernel-release-tracking-bug-live

** Tags added: kernel-sru-cycle-d2019.04.15-1

** Description changed:

  This bug will contain status and test results 

[Kernel-packages] [Bug 1824833] [NEW] linux-aws: -proposed tracker

2019-04-15 Thread Seth Forshee
Public bug reported:

This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.

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: 1824819

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-aws (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-aws (Ubuntu Disco)
 Importance: Medium
 Status: New


** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-d2019.04.15-1 kernel-sru-derivative-of-1824819

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-sru-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

** Tags added: disco

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

** Tags added: kernel-release-tracking-bug-live

** Tags added: kernel-sru-cycle-d2019.04.15-1

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1824819

** Tags added: kernel-sru-derivative-of-1824819

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

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

Title:
  linux-aws:  -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:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New

[Kernel-packages] [Bug 1824835] [NEW] linux-gcp: -proposed tracker

2019-04-15 Thread Seth Forshee
Public bug reported:

This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.

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: 1824819

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-gcp (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-gcp (Ubuntu Disco)
 Importance: Medium
 Status: New


** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-d2019.04.15-1 kernel-sru-derivative-of-1824819

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-sru-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

** Tags added: disco

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

** Tags added: kernel-release-tracking-bug-live

** Tags added: kernel-sru-cycle-d2019.04.15-1

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1824819

** Tags added: kernel-sru-derivative-of-1824819

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1824836] [NEW] linux-kvm: 5.0.0-1004.4 -proposed tracker

2019-04-15 Thread Seth Forshee
Public bug reported:

This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.

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: 1824819

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-kvm (Ubuntu)
 Importance: Medium
 Status: New

** Affects: linux-kvm (Ubuntu Disco)
 Importance: Medium
 Status: New


** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-d2019.04.15-1 kernel-sru-derivative-of-1824819

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-sru-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

** Tags added: disco

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

** Tags added: kernel-release-tracking-bug-live

** Tags added: kernel-sru-cycle-d2019.04.15-1

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1824819

** Tags added: kernel-sru-derivative-of-1824819

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

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

Title:
  linux-kvm: 5.0.0-1004.4 -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 promote-to-proposed series:
  New
Status in Kernel SRU Workflow 

[Kernel-packages] [Bug 1824726] Re: linux: 5.0.0-12.13 -proposed tracker

2019-04-15 Thread Seth Forshee
*** This bug is a duplicate of bug 1824819 ***
https://bugs.launchpad.net/bugs/1824819

** This bug has been marked a duplicate of bug 1824819
   linux: 5.0.0-13.14 -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/1824726

Title:
  linux: 5.0.0-12.13 -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:
  New
Status in linux source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  -- swm properties --
  phase: Packaging
  phase-changed: Sunday, 14. April 2019 18:42 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824726/+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 1824819] [NEW] linux: 5.0.0-13.14 -proposed tracker

2019-04-15 Thread Seth Forshee
Public bug reported:

This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.

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

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Disco)
 Importance: Medium
 Status: New


** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-d2019.04.15-1

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-sru-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

** Tags added: disco

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

** Tags added: kernel-release-tracking-bug-live

** Tags added: kernel-sru-cycle-d2019.04.15-1

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Summary changed:

- linux:  -proposed tracker
+ linux: 5.0.0-13.14 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

** 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) =&g

[Kernel-packages] [Bug 1824726] Re: linux: 5.0.0-12.13 -proposed tracker

2019-04-14 Thread Seth Forshee
** Summary changed:

- linux:  -proposed tracker
+ linux: 5.0.0-12.13 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

** 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) => Seth Forshee 
(sforshee)

** 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) => 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/1824726

Title:
  linux: 5.0.0-12.13 -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:
  New
Status in linux source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824726/+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 1824717] Re: kernel BUG at fs/attr.c:287 when using shiftfs

2019-04-14 Thread Seth Forshee
** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  kernel BUG at fs/attr.c:287 when using shiftfs

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  SRU Justification

  Impact: It is possible to hit a BUG statement in notify_change() with
  shiftfs (below). This occurs when one of ATTR_KILL_SUID or
  ATTR_KILL_SGID is set in the attrs and notify_change() sets ATTR_MODE
  before calling shiftfs_setattr(). shiftfs_setattr() passes the attrs
  to notify_change(), and the BUG statement is hit due to ATTR_MODE
  being set with one of ATTR_KILL_SUID or ATTR_KILL_SGID set.

  Fix: Copy the logic used by ecryptfs and overlayfs to clear ATTR_MODE
  if one of these bits is set, allowning the lower fs to interpret the
  kill bits in its own way. Also fix a bug where changes to the attrs
  from setattr_prepare() are not propagated to the attrs used for the
  lower fs.

  Regression Potential: Limited to shiftfs, matches the behavior of
  other stacked filesystems, and has been tested (see below).

  Test Case: Tested in the lxd CI environment where the bug was
  originally discovered. No regressions were seen, and the BUG statement
  was not hit.

  ---

  [18558.819079] [ cut here ]
  [18558.819082] kernel BUG at fs/attr.c:287!
  [18558.823490] invalid opcode:  [#1] SMP PTI
  [18558.828038] CPU: 2 PID: 26728 Comm: dpkg Tainted: P   O  
5.0.0-10-generic #11+shiftfsv201904110736
  [18558.838152] Hardware name: Google Google Compute Engine/Google Compute 
Engine, BIOS Google 01/01/2011
  [18558.872092] RIP: 0010:notify_change+0x412/0x460
  [18558.876843] Code: 55 00 e9 35 fe ff ff 48 3b 50 30 0f 85 88 fd ff ff e9 bf 
fe ff ff 41 83 ce 04 e9 21 ff ff ff 41 ba ff ff ff ff e9 ac fd ff ff <0f> 0b 4c 
89 fe 4c 89 e7 e8 b1 af 00 00 41 89 c2 e9 b5 fe ff ff f6
  [18558.896179] RSP: 0018:b706dbaf7d00 EFLAGS: 00010202
  [18558.901984] RAX: 5cb1105d RBX: 1847 RCX: 

  [18558.909241] RDX: 165a9c4b RSI: 165a9c4b RDI: 
5cb1105d
  [18558.916491] RBP: b706dbaf7d38 R08:  R09: 

  [18558.923741] R10:  R11:  R12: 
89fa79f756c0
  [18558.931350] R13: 89fa43d89230 R14: 85ed R15: 
b706dbaf7d50
  [18558.938616] FS:  7fe41f039040() GS:89fc61a8() 
knlGS:
  [18558.946928] CS:  0010 DS:  ES:  CR0: 80050033
  [18558.952826] CR2: 5614215be0a8 CR3: 0007594fc002 CR4: 
001606e0
  [18558.960078] DR0:  DR1:  DR2: 

  [18558.967395] DR3:  DR6: fffe0ff0 DR7: 
0400
  [18558.975018] Call Trace:
  [18558.977810]  ? setattr_prepare+0x178/0x200
  [18558.982160]  shiftfs_setattr+0xec/0x140
  [18558.986149]  notify_change+0x2d9/0x460
  [18558.990014]  chown_common+0x1c8/0x1e0
  [18558.993917]  do_fchownat+0x93/0xf0
  [18558.997551]  __x64_sys_chown+0x22/0x30
  [18559.001522]  do_syscall_64+0x5a/0x110
  [18559.005481]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [18559.010652] RIP: 0033:0x7fe41e9193e7
  [18559.014343] Code: 39 84 24 98 00 00 00 75 a1 48 89 df e8 d2 c5 f8 ff eb a0 
e8 ab 38 02 00 66 2e 0f 1f 84 00 00 00 00 00 90 b8 5c 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 71 9a 2d 00 f7 d8 64 89 01 48
  [18559.033294] RSP: 002b:7fff73c89d48 EFLAGS: 0297 ORIG_RAX: 
005c
  [18559.041365] RAX: ffda RBX: 5614237e0190 RCX: 
7fe41e9193e7
  [18559.048820] RDX: 0008 RSI:  RDI: 
5614237e0190
  [18559.056290] RBP: 5614237df110 R08: 001b R09: 
002e
  [18559.063681] R10: f32f R11: 0297 R12: 
7fff73c8a210
  [18559.071386] R13: 561424166360 R14: 5614237e0190 R15: 

  [18559.078773] Modules linked in: binfmt_misc veth ebtable_filter ebtables 
ip6t_MASQUERADE ip6table_nat nf_nat_ipv6 ipt_MASQUERADE xt_CHECKSUM xt_comment 
xt_tcpudp iptable_nat nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 iptable_mangle bridge stp llc unix_diag ip6table_filter 
ip6_tables iptable_filter bpfilter zfs(PO) zunicode(PO) zavl(PO) icp(PO) 
zcommon(PO) nls_iso8859_1 znvpair(PO) spl(O) input_leds serio_raw sb_edac 
pvpanic mac_hid intel_rapl_perf sch_fq_codel ib_iser rdma_cm iw_cm ib_cm 
ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel virtio_net 
aes_x86_64 nvme crypto_simd cryptd glue_helper net_failover psmouse 

[Kernel-packages] [Bug 1824216] Re: Linux 5.0 black screen on boot, display flickers (i915 regression with certain laptop panels)

2019-04-14 Thread Seth Forshee
** Changed in: linux (Ubuntu Disco)
   Status: Confirmed => 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/1824216

Title:
  Linux 5.0 black screen on boot, display flickers (i915 regression with
  certain laptop panels)

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  On my Dell XPS 9575, I get a black screen on boot when running the 19.04 live 
image, OR after updating from 18.10 to 19.04.  It appears to be a kernel 
related bug that was introduced in 5.0 that is affected by certain laptop 
panels not conforming to their stated specifications.

  Several other Dell systems exhibit the same issue, and it's very
  possible that there are other panels used on other systems that will
  also have the same issues.

  Intel is aware of this issue and has already created a patch.  You can
  see the relevant threads here:

  https://bugs.freedesktop.org/show_bug.cgi?id=109959

  And the patch here:

  https://patchwork.freedesktop.org/patch/296411/

  It would be fantastic to get this patch applied before release, as it
  would be very difficult install 19.04 on the affected systems
  otherwise.  I was able to get the live image booted by adding the
  nomodeset kernel parameter to grub, so as a work around you can use
  this approach to install.

  [Test case]
  boot a kernel with the revert

  [Regression potential]
  shouldn't be any, since this reverts to what was used on kernels before 5.0

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

2019-04-14 Thread Seth Forshee
Public bug reported:

This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.

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

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Disco)
 Importance: Medium
 Status: New


** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-d2019.04.14-1

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-sru-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

** Tags added: disco

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

** Tags added: kernel-release-tracking-bug-live

** Tags added: kernel-sru-cycle-d2019.04.14-1

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

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

Title:
  linux:  -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:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed 

[Kernel-packages] [Bug 1824717] [NEW] kernel BUG at fs/attr.c:287 when using shiftfs

2019-04-14 Thread Seth Forshee
005cb1105d RBX: 1847 RCX: 
[18559.204362] RDX: 165a9c4b RSI: 165a9c4b RDI: 5cb1105d
[18559.211720] RBP: b706dbaf7d38 R08:  R09: 
[18559.220358] R10:  R11:  R12: 89fa79f756c0
[18559.227648] R13: 89fa43d89230 R14: 85ed R15: b706dbaf7d50
[18559.236285] FS:  7fe41f039040() GS:89fc61a8() 
knlGS:
[18559.244522] CS:  0010 DS:  ES:  CR0: 80050033
[18559.251941] CR2: 5614215be0a8 CR3: 0007594fc002 CR4: 001606e0
[18559.259242] DR0:  DR1:  DR2: 
[18559.266702] DR3:  DR6: fffe0ff0 DR7: 0400

** Affects: linux (Ubuntu)
 Importance: High
     Assignee: Seth Forshee (sforshee)
 Status: 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/1824717

Title:
  kernel BUG at fs/attr.c:287 when using shiftfs

Status in linux package in Ubuntu:
  In Progress

Bug description:
  SRU Justification

  Impact: It is possible to hit a BUG statement in notify_change() with
  shiftfs (below). This occurs when one of ATTR_KILL_SUID or
  ATTR_KILL_SGID is set in the attrs and notify_change() sets ATTR_MODE
  before calling shiftfs_setattr(). shiftfs_setattr() passes the attrs
  to notify_change(), and the BUG statement is hit due to ATTR_MODE
  being set with one of ATTR_KILL_SUID or ATTR_KILL_SGID set.

  Fix: Copy the logic used by ecryptfs and overlayfs to clear ATTR_MODE
  if one of these bits is set, allowning the lower fs to interpret the
  kill bits in its own way. Also fix a bug where changes to the attrs
  from setattr_prepare() are not propagated to the attrs used for the
  lower fs.

  Regression Potential: Limited to shiftfs, matches the behavior of
  other stacked filesystems, and has been tested (see below).

  Test Case: Tested in the lxd CI environment where the bug was
  originally discovered. No regressions were seen, and the BUG statement
  was not hit.

  ---

  [18558.819079] [ cut here ]
  [18558.819082] kernel BUG at fs/attr.c:287!
  [18558.823490] invalid opcode:  [#1] SMP PTI
  [18558.828038] CPU: 2 PID: 26728 Comm: dpkg Tainted: P   O  
5.0.0-10-generic #11+shiftfsv201904110736
  [18558.838152] Hardware name: Google Google Compute Engine/Google Compute 
Engine, BIOS Google 01/01/2011
  [18558.872092] RIP: 0010:notify_change+0x412/0x460
  [18558.876843] Code: 55 00 e9 35 fe ff ff 48 3b 50 30 0f 85 88 fd ff ff e9 bf 
fe ff ff 41 83 ce 04 e9 21 ff ff ff 41 ba ff ff ff ff e9 ac fd ff ff <0f> 0b 4c 
89 fe 4c 89 e7 e8 b1 af 00 00 41 89 c2 e9 b5 fe ff ff f6
  [18558.896179] RSP: 0018:b706dbaf7d00 EFLAGS: 00010202
  [18558.901984] RAX: 5cb1105d RBX: 1847 RCX: 

  [18558.909241] RDX: 165a9c4b RSI: 165a9c4b RDI: 
5cb1105d
  [18558.916491] RBP: b706dbaf7d38 R08:  R09: 

  [18558.923741] R10:  R11:  R12: 
89fa79f756c0
  [18558.931350] R13: 89fa43d89230 R14: 85ed R15: 
b706dbaf7d50
  [18558.938616] FS:  7fe41f039040() GS:89fc61a8() 
knlGS:
  [18558.946928] CS:  0010 DS:  ES:  CR0: 80050033
  [18558.952826] CR2: 5614215be0a8 CR3: 0007594fc002 CR4: 
001606e0
  [18558.960078] DR0:  DR1:  DR2: 

  [18558.967395] DR3:  DR6: fffe0ff0 DR7: 
0400
  [18558.975018] Call Trace:
  [18558.977810]  ? setattr_prepare+0x178/0x200
  [18558.982160]  shiftfs_setattr+0xec/0x140
  [18558.986149]  notify_change+0x2d9/0x460
  [18558.990014]  chown_common+0x1c8/0x1e0
  [18558.993917]  do_fchownat+0x93/0xf0
  [18558.997551]  __x64_sys_chown+0x22/0x30
  [18559.001522]  do_syscall_64+0x5a/0x110
  [18559.005481]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [18559.010652] RIP: 0033:0x7fe41e9193e7
  [18559.014343] Code: 39 84 24 98 00 00 00 75 a1 48 89 df e8 d2 c5 f8 ff eb a0 
e8 ab 38 02 00 66 2e 0f 1f 84 00 00 00 00 00 90 b8 5c 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 71 9a 2d 00 f7 d8 64 89 01 48
  [18559.033294] RSP: 002b:7fff73c89d48 EFLAGS: 0297 ORIG_RAX: 
005c
  [18559.041365] RAX: ffda RBX: 5614237e0190 RCX: 
7fe41e9193e7
  [18559.048820] RDX: 0008 RSI:  RDI: 
5614237e0190
  [18559.056290] RBP: 5614237df110 R08: 001b R09: 
002e
  [18559.063681] R10: f32f R11: 0297 R12: 
7fff73c8a210
  [18559.071386] R13: 561424166360 R14: 5614237e0190 R15: 

  [18559.078773] Modules linked in: binfmt_misc veth ebtable_filter ebtables

[Kernel-packages] [Bug 1824378] Re: linux-kvm: 5.0.0-1003.3 -proposed tracker

2019-04-13 Thread Seth Forshee
** Tags added: regression-testing-passed

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

Title:
  linux-kvm: 5.0.0-1003.3 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1824383
  phase: Ready for Release
  phase-changed: Saturday, 13. April 2019 12:43 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-release: Pending -- ready to copy

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

2019-04-12 Thread Seth Forshee
** Tags added: regression-testing-passed

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

Title:
  linux-aws: 5.0.0-1003.3 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1824383
  phase: Ready for Release
  phase-changed: Saturday, 13. April 2019 03:23 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-release: Pending -- ready to copy

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

2019-04-12 Thread Seth Forshee
** Tags added: regression-testing-passed

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

Title:
  linux-azure: 5.0.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1824383
  phase: Ready for Signoff
  phase-changed: Saturday, 13. April 2019 01:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-release: Holding -- master bug not ready for release
stakeholder-signoff: Pending -- waiting for signoff

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

2019-04-12 Thread Seth Forshee
** Tags added: regression-testing-passed

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

Title:
  linux-gcp: 5.0.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
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:
  Fix Released
Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1824383
  phase: Packaging
  phase-changed: Thursday, 11. April 2019 18:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
prepare-package-meta: Pending -- package tag not yet published
promote-to-release: Holding -- master bug not ready for release

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

2019-04-12 Thread Seth Forshee
** Tags added: regression-testing-passed

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

Title:
  linux: 5.0.0-11.12 -proposed tracker

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

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

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

  backports: bug 1824381 (bionic/linux-hwe-edge), bug 1824382 
(bionic/linux-oem-osp1)
  derivatives: bug 1824374 (linux-raspi2), bug 1824375 (linux-aws), bug 1824376 
(linux-azure), bug 1824377 (linux-gcp), bug 1824378 (linux-kvm), bug 1824380 
(linux-snapdragon)

  -- swm properties --
  phase: Packaging
  phase-changed: Thursday, 11. April 2019 15:43 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
prepare-package-meta: Pending -- package tag not yet published
prepare-package-signed: Pending -- package tag not yet published
promote-to-release: Pending -- ready to copy

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824383/+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 1794055] Re: [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with nouveau errors; OS booted successfully

2019-04-12 Thread Seth Forshee
Thanks for verifying on cosmic! Looks like verification for bionic is
still missing however.

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

Title:
  [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown
  with nouveau errors; OS booted successfully

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Won't Fix
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-firmware source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Missing firmware for nouveau is causing errors to appear in
  dmesg.

  Fix: Add missing firmware files from upstream linux-firmware.

  Test Case: Confirm that errors in dmesg are gone once new firmware
  files are present.

  Regression Potential: New and updated firmware always has potential to
  cause regressions, however this firmware has been in disco for several
  months with no reported issues.

  ---

  == Comment: #0 - Kalpana Shetty  - 2018-09-15 23:55:13 ==
  ---Problem Description---
  [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with 
nouveau errors

  Contact Information = kalsh...@in.ibm.com, preeti.tha...@in.ibm.com

  ---uname output---
  root@ltc-wcwsp3:~# uname -a Linux ltc-wcwsp3 4.18.0-7-generic #8-Ubuntu SMP 
Tue Aug 28 18:20:56 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = Witherspoon DD2.2 LC

  Steps:
  1. Netinstall Ubu 18.10 on Witherspoon-LC-DD2.2 6GPU system --> PASS
  2. Boot the OS ---> PASS but error thrown on the console related open source 
NVIDIA driver.

    [Disk: sdb2 / c0302064-c5a3-49a7-8bd4-402283e6fcbe]
  Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
  Ubuntu, with Linux 4.18.0-7-generic
  Ubuntu
    [Disk: nvme0n1p2 / c5d042f1-812e-49e0-94b2-ade477084061]
  Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
   *  Ubuntu, with Linux 4.18.0-7-generic
  Ubuntu

    System information
    System configuration
    System status log
    Language
    Rescan devices
    Retrieve config from URL
    Plugins (0)
    Exit to shell
   
??
   Enter=accept, e=edit, n=new, x=exit, l=language, g=log, h=help
  The system is going down NOW!
  Sent SIGTERM to all processes
  Sent SIGKILL to all processes
  [   57.513329] kexec_core: Starting new kernel
  [  149.358703978,5] OPAL: Switch to big-endian OS
  [  153.355498935,5] OPAL: Switch to little-endian OS
  [2.943735] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
  [2.943738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
  [3.132733] vio vio: uevent: failed to send synthetic uevent
  [4.058698] nouveau 0004:04:00.0: gr: failed to load gr/sw_nonctx
  [4.129215] nouveau 0004:04:00.0: DRM: failed to create kernel channel, -22
  [   19.126509] nouveau 0004:04:00.0: DRM: failed to idle channel 0 [DRM]
  [   19.281450] nouveau 0004:05:00.0: gr: failed to load gr/sw_nonctx
  [   19.351322] nouveau 0004:05:00.0: DRM: failed to create kernel channel, -22
  [   34.350509] nouveau 0004:05:00.0: DRM: failed to idle channel 0 [DRM]
  [   34.502063] nouveau 0004:06:00.0: gr: failed to load gr/sw_nonctx
  [   34.572144] nouveau 0004:06:00.0: DRM: failed to create kernel channel, -22
  [   49.570509] nouveau 0004:06:00.0: DRM: failed to idle channel 0 [DRM]
  [   49.734754] nouveau 0035:03:00.0: gr: failed to load gr/sw_nonctx
  [   49.805057] nouveau 0035:03:00.0: DRM: failed to create kernel channel, -22
  [   64.802510] nouveau 0035:03:00.0: DRM: failed to idle channel 0 [DRM]
  [   64.955442] nouveau 0035:04:00.0: gr: failed to load gr/sw_nonctx
  [   65.025537] nouveau 0035:04:00.0: DRM: failed to create kernel channel, -22

  [   80.022509] nouveau 0035:04:00.0: DRM: failed to idle channel 0 [DRM]
  [   80.181169] nouveau 0035:05:00.0: gr: failed to load gr/sw_nonctx
  [   80.251481] nouveau 0035:05:00.0: DRM: failed to create kernel channel, -22
  [   95.250509] nouveau 0035:05:00.0: DRM: failed to idle channel 0 [DRM]
  /dev/nvme0n1p2: recovering journal
  /dev/nvme0n1p2: clean, 72569/97681408 files, 7384418/390701312 blocks
  -.mount
  kmod-static-nodes.service
  dev-hugepages.mount
  dev-mqueue.mount
  sys-kernel-debug.mount
  ufw.service
  lvm2-lvmetad.service
  systemd-remount-fs.service
  systemd-random-seed.service
  systemd-sysusers.service
  keyboard-setup.service
  systemd-tmpfiles-setup-dev.service
  lvm2-monitor.service
  finalrd.service
  console-setup.service
  swapfile.swap
  ebtables.service
  systemd-udevd.service
  systemd-journald.service
  systemd-journal-flush.service
  

[Kernel-packages] [Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6

2019-04-12 Thread Seth Forshee
Added verifiction-done tags for bionic and cosmic based on comments #17
and #18.

** Tags added: verification-done-bionic verification-done-cosmic

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

Title:
  iwlwifi  Intel 8265 firmware crashing on lenovo x1 Gen 6

Status in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in The Bionic Beaver:
  Confirmed
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in The Cosmic Cuttlefish:
  Confirmed
Status in linux-firmware source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification:
  ===
  [Impact]
  repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6.

  [Fix]
  New iwlwifi firmware fix it.

  [Test]
  Bug reporter verified with positive result.

  [Regression Potential]
  Upstream fix, low risk.
  Bug reporter confirms fix.

  
  Original bug report:
  =

  Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1
  Gen6.

  Firmware: 36.7596afd4.0

  Dec 13 11:53:36 james-x1 kernel: [  856.840159] wlp2s0: send auth to 
60:38:e0:70:a2:11 (try 1/3)
  Dec 13 11:53:36 james-x1 kernel: [  856.844875] iwlwifi :02:00.0: 
Microcode SW error detected.  Restarting 0x200.
  Dec 13 11:53:36 james-x1 kernel: [  856.845015] iwlwifi :02:00.0: Start 
IWL Error Log Dump:
  Dec 13 11:53:36 james-x1 kernel: [  856.845018] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  Dec 13 11:53:36 james-x1 kernel: [  856.845021] iwlwifi :02:00.0: Loaded 
firmware version: 36.7596afd4.0
  Dec 13 11:53:36 james-x1 kernel: [  856.845024] iwlwifi :02:00.0: 
0x1006 | ADVANCED_SYSASSERT
  Dec 13 11:53:36 james-x1 kernel: [  856.845026] iwlwifi :02:00.0: 
0x02F0 | trm_hw_status0
  Dec 13 11:53:36 james-x1 kernel: [  856.845029] iwlwifi :02:00.0: 
0x | trm_hw_status1
  Dec 13 11:53:36 james-x1 kernel: [  856.845031] iwlwifi :02:00.0: 
0x000248DC | branchlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845034] iwlwifi :02:00.0: 
0x0003A7DA | interruptlink1
  Dec 13 11:53:36 james-x1 kernel: [  856.845036] iwlwifi :02:00.0: 
0x | interruptlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845039] iwlwifi :02:00.0: 
0xFEDA | data1
  Dec 13 11:53:36 james-x1 kernel: [  856.845041] iwlwifi :02:00.0: 
0xDEADBEEF | data2
  Dec 13 11:53:36 james-x1 kernel: [  856.845044] iwlwifi :02:00.0: 
0xDEADBEEF | data3
  Dec 13 11:53:36 james-x1 kernel: [  856.845046] iwlwifi :02:00.0: 
0x0007E1DC | beacon time
  Dec 13 11:53:36 james-x1 kernel: [  856.845048] iwlwifi :02:00.0: 
0x003B0850 | tsf low
  Dec 13 11:53:36 james-x1 kernel: [  856.845051] iwlwifi :02:00.0: 
0x | tsf hi
  Dec 13 11:53:36 james-x1 kernel: [  856.845053] iwlwifi :02:00.0: 
0x | time gp1
  Dec 13 11:53:36 james-x1 kernel: [  856.845055] iwlwifi :02:00.0: 
0x003B0852 | time gp2
  Dec 13 11:53:36 james-x1 kernel: [  856.845058] iwlwifi :02:00.0: 
0x0001 | uCode revision type
  Dec 13 11:53:36 james-x1 kernel: [  856.845060] iwlwifi :02:00.0: 
0x0024 | uCode version major
  Dec 13 11:53:36 james-x1 kernel: [  856.845063] iwlwifi :02:00.0: 
0x7596AFD4 | uCode version minor
  Dec 13 11:53:36 james-x1 kernel: [  856.845065] iwlwifi :02:00.0: 
0x0230 | hw version
  Dec 13 11:53:36 james-x1 kernel: [  856.845068] iwlwifi :02:00.0: 
0x18489000 | board version
  Dec 13 11:53:36 james-x1 kernel: [  856.845070] iwlwifi :02:00.0: 
0x0501001C | hcmd
  Dec 13 11:53:36 james-x1 kernel: [  856.845072] iwlwifi :02:00.0: 
0x00023008 | isr0
  Dec 13 11:53:36 james-x1 kernel: [  856.845075] iwlwifi :02:00.0: 
0x000D | isr1
  Dec 13 11:53:36 james-x1 kernel: [  856.845077] iwlwifi :02:00.0: 
0x08001802 | isr2
  Dec 13 11:53:36 james-x1 kernel: [  856.845080] iwlwifi :02:00.0: 
0x0041FDC0 | isr3
  Dec 13 11:53:36 james-x1 kernel: [  856.845082] iwlwifi :02:00.0: 
0x | isr4
  Dec 13 11:53:36 james-x1 kernel: [  856.845084] iwlwifi :02:00.0: 
0x00580118 | last cmd Id
  Dec 13 11:53:36 james-x1 kernel: [  856.845087] iwlwifi :02:00.0: 
0x | wait_event
  Dec 13 11:53:36 james-x1 kernel: [  856.845089] iwlwifi :02:00.0: 
0x76DD | l2p_control
  Dec 13 11:53:36 james-x1 kernel: [  856.845091] iwlwifi :02:00.0: 
0x0020 | l2p_duration
  Dec 13 11:53:36 james-x1 kernel: [  856.845094] iwlwifi :02:00.0: 
0x | l2p_mhvalid
  Dec 13 11:53:36 james-x1 kernel: [  856.845096] iwlwifi :02:00.0: 
0x00A0 | l2p_addr_match
  Dec 13 11:53:36 james-x1 kernel: [  856.845099] iwlwifi :02:00.0: 
0x000D | lmpm_pmg_sel
  Dec 13 11:53:36 james-x1 kernel: [  856.845101] iwlwifi :02:00.0: 
0x22040707 | timestamp
  Dec 13 11:53:36 james-x1 kernel: [  856.845103] iwlwifi :02:00.0: 

[Kernel-packages] [Bug 1824377] Re: linux-gcp: 5.0.0-1003.3 -proposed tracker

2019-04-11 Thread Seth Forshee
** Summary changed:

- linux-gcp:  -proposed tracker
+ linux-gcp: 5.0.0-1003.3 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

** 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) => Seth Forshee 
(sforshee)

** 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) => Seth Forshee 
(sforshee)

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

Title:
  linux-gcp: 5.0.0-1003.3 -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-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1824383
  phase: Packaging
  phase-changed: Thursday, 11. April 2019 18:10 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

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

2019-04-11 Thread Seth Forshee
** Summary changed:

- linux-azure:  -proposed tracker
+ linux-azure: 5.0.0-1003.3 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

** 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) => Seth Forshee 
(sforshee)

** 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) => Seth Forshee 
(sforshee)

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

Title:
  linux-azure: 5.0.0-1003.3 -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 Kernel SRU Workflow stakeholder-signoff series:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1824383
  phase: Holding before Packaging
  phase-changed: Thursday, 11. April 2019 15:42 UTC
  reason:
prepare-package: Stalled -- waiting for master bug

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

2019-04-11 Thread Seth Forshee
*** This bug is a duplicate of bug 1824376 ***
https://bugs.launchpad.net/bugs/1824376

** This bug has been marked a duplicate of bug 1824376
   linux-azure:  -proposed tracker

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

Title:
  linux-azure: 5.0.0-1001.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 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:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released

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-master-bug: 1819759
  phase: Ready for Signoff
  phase-changed: Monday, 01. April 2019 11:08 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
stakeholder-signoff: Pending -- waiting for signoff

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

2019-04-11 Thread Seth Forshee
** Summary changed:

- linux-aws:  -proposed tracker
+ linux-aws: 5.0.0-1003.3 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

** 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) => Seth Forshee 
(sforshee)

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

Title:
  linux-aws: 5.0.0-1003.3 -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 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-aws package in Ubuntu:
  New
Status in linux-aws source package in Disco:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1824383
  phase: Packaging
  phase-changed: Thursday, 11. April 2019 15:42 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824375/+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


  1   2   3   4   5   6   7   8   9   10   >