[Kernel-packages] [Bug 1836467] Update Released

[Adam Conrad]

The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Bluetooth fails with "Bluetooth: hci0: request failed to create LE
  connection: status 0x0c" message with Kernel 4.20 and up [9df0:0034]

Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-firmware source package in Cosmic:
  Won't Fix
Status in linux-firmware source package in Disco:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]
  Bluetooth for Intel Wireless-AC 9560 variant 9df0:0034 still fails to
  pair BT LE HID devices on recent (>= 4.19) kernel.

  [Fix]
  Bluetooth firmware REL0450 or newer is required to fix this issue.

  [Test Case]
  Install new firmware blob to /lib/firmware/intel, shutdown the machine
  completely and wait for a couple minutes to trigger firmware reloading
  at the next boot. Then perform Bluetooth LE HID devices pairing to
  verify if the proposed fw fixes this issue.

  [Regression Risk]
  Low. This affects only sub models of Intel JeffersonPeak Bluetooth chip
  series using these firmware blobs.

  == Original Bug Description ==

  This is similar to https://bugs.launchpad.net/bugs/1829737 - however
  the issue was not fixed by linux-firmware 1.173.8 so I was advised to
  log a new bug.

  I have an ASUS ZenBook 14 - UX433FA - which based on this - 
https://www.notebookcheck.net/ASUS-ZenBook-14-UX433FA-Core-i5-8265U-SSD-FHD-Laptop-Review.403541.0.html
 - I believe has an Intel 9560 chipset (I am not sure how to independently 
verify this).
  With kernels older than 4.20 I can successfully pair my bluetooth mouse 
(Logitech MX Master) - but with newer kernels I get "Bluetooth: hci0: request 
failed to create LE connection: status 0x0c" messages.

  I'm running Linux Mint 19.1

  I tried installing linux-firmware 1.173.8, and it didn't seem to help
  - I also downloaded 1.173.9 proposed from here:
  https://launchpad.net/ubuntu/bionic/amd64/linux-firmware/1.173.9 and
  that also didn't seem to help.

  Both after a cold reboot and a warm reboot I see
  [ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017

  in my dmesg output.

  Bluetooth works just fine with earlier kernels (however other aspects
  of the laptop like suspend don't work as well, which is why I'm trying
  the newer kernel.

  Linux warren-ZenBook 5.1.16-050116-generic #201907031232 SMP Wed Jul 3
  12:35:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  dmesg | egrep -i 'blue|firm'
  [
  [0.180273] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.004526] [Firmware Bug]: TSC ADJUST differs within socket(s), fixing 
all errors
  [1.417663] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin 
(v1.4)
  [   14.641146] iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-9000-pu-b0-jf-b0-46.ucode failed with error -2
  [   14.642377] iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-9000-pu-b0-jf-b0-45.ucode failed with error -2
  [   14.642392] iwlwifi :00:14.3: Direct firmware load for 
iwlwifi-9000-pu-b0-jf-b0-44.ucode failed with error -2
  [   14.652301] iwlwifi :00:14.3: loaded firmware version 43.95eb4e97.0 
op_mode iwlmvm
  [   14.675356] Bluetooth: Core ver 2.22
  [   14.675374] Bluetooth: HCI device and connection manager initialized
  [   14.675377] Bluetooth: HCI socket layer initialized
  [   14.675379] Bluetooth: L2CAP socket layer initialized
  [   14.675382] Bluetooth: SCO socket layer initialized
  [   14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017
  [   15.207800] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   15.207801] Bluetooth: BNEP filters: protocol multicast
  [   15.207804] Bluetooth: BNEP socket layer initialized
  [   22.040223] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
  [   22.040232] Bluetooth: HIDP socket layer initialized
  [   22.042238] input: Logitech K810 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input27
  [   22.042996] input: Logitech K810 Consumer Control as 
/devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input28
  [   22.043235] input: Logitech K810 System Control as 

[Kernel-packages] [Bug 1847250] Update Released

[Adam Conrad]

The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  update firmware for sound sof driver to fix the hang issue on several
  Dell machines

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-firmware source package in Disco:
  Fix Released
Status in linux-firmware source package in Eoan:
  Fix Released

Bug description:
  We expect this firmware update could be released with 19.10

  [Impact]
  We have a couple of Dell machines, after installing the system, it
  will hang randomly, and this issue was reported by factory, they met
  this issue a couple of times. Then we tried to reproduce this issue,
  finally reproduced it.

  [Fix]
  Intel debugged this issue as well, and they provided 4 kernel patches
  and a new firmware, we tested them, they really can fix the issue.
  And the patches were sent the SRU already, now it is time to update
  firmware.

  [Test Case]
  Install the system repeatedly and there is no hang issue anymore.

  [Regression Risk]
  Low, Intel told us there is no ABI change for the firmware, so
  it is safe to run this firmware both with the old driver (not applied
  those 4 patches) and the new driver (applied those 4 patches).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1847250/+subscriptions

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

[Kernel-packages] [Bug 1842893] Update Released

[Adam Conrad]

The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Intel Bluetooth AX201, aka HarrisonPeak (HrP), not supported

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

Bug description:
  [5.950346] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 11 2017
  [5.951318] Bluetooth: hci0: Device revision is 2
  [5.951319] Bluetooth: hci0: Secure boot is enabled
  [5.951320] Bluetooth: hci0: OTP lock is enabled
  [5.951320] Bluetooth: hci0: API lock is enabled
  [5.951321] Bluetooth: hci0: Debug lock is disabled
  [5.951322] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [5.952242] bluetooth hci0: Direct firmware load for intel/ibt-19-32-4.sfi 
failed with error -2
  [5.952244] Bluetooth: hci0: Failed to load Intel firmware file (-2)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-melisa+X16
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-08-13 (23 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 5.3.0-050300rc4-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1842893/+subscriptions

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

[Kernel-packages] [Bug 1836983] Update Released

[Adam Conrad]

The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [Intel CyclonePeak] Pairing new BT mouse fails sometimes

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

Bug description:
  [Impact]
  After update the BT firmware, it requires to pair twice to pair a new device.
  There should be a "SMP: Pairing Request" send from hci0, but it doesn't be 
submitted in the first time.

  [Fix]
  The new firmware fix this issue.

  [Test]
  Verified on Dell platforms with BT Designer Mouse(DF:29:ED:BD:82:95)

  [Regression Potential]
  Low, the firmware is newly added for new Cyclone Peak wifi/bt, and it won't 
affect the devices on the market currently.

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

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

[Kernel-packages] [Bug 1835879] Update Released

[Adam Conrad]

The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Intel Wireless-AC 9462/9560 not supported on ICL

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Won't Fix
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-firmware 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:
  Won't Fix
Status in linux-firmware source package in Disco:
  Fix Released
Status in linux-oem-osp1 source package in Disco:
  Fix Released

Bug description:
  [Impact]
  Intel Wireless-AC 9560/9462 is not correctly enabled on IceLake
  platforms.

  [Fix]
  Two changes from Intel maintained backport-iwlwifi repository are
  necessary to add device ID/configs to iwlwifi driver.

  [Test]
  Verified on hardware 9462/9560 on IceLake/CometLake platforms.

  [Regression Potential]
  Low. These changes are part of the series to enable 9462/9560 on
  CometLake/IceLake platforms that don't have the support originally.

  = Original Bug Description =

  Intel Wireless-AC 9462/9560 on CML was previously enabled via bug
  1833065, bug 1834415 and bug 1834464. However on ICL, it fails to
  startup with following error messages with kernel v5.2-rc7:

    iwlwifi :00:14.3: loaded firmware version 48.13675109.0 op_mode iwlmvm
    iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560, REV=0x338
    iwlwifi :00:14.3: Loaded firmware version: 48.13675109.0
    iwlwifi :00:14.3: SecBoot CPU1 Status: 0x5c97, CPU2 Status: 0x3
    iwlwifi :00:14.3: Failed to start RT ucode: -5
    iwlwifi :00:14.3: Collecting data: trigger 16 fired.
    iwlwifi :00:14.3: Firmware not running - cannot dump error
    iwlwifi :00:14.3: Failed to run INIT ucode: -5

  Also tried backport-iwlwifi out-of-tree driver revision 7858 (HEAD at
  the moment) with no luck.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1835879/+subscriptions

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

[Kernel-packages] [Bug 1780590] Update Released

[Adam Conrad]

The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Add support for Realtek 8723DE wireless adapter

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Won't Fix
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Disco:
  Won't Fix
Status in linux-firmware source package in Disco:
  Fix Released
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Won't Fix
Status in linux-firmware source package in Eoan:
  Fix Released
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Confirmed
Status in linux-firmware source package in Focal:
  New
Status in linux-oem-osp1 source package in Focal:
  Won't Fix

Bug description:
  === SRU Justification ===
  [Impact]
  There's no in-kernel support for Realtek 8723DE, so users need to use
  out-of-tree DKMS which is not from Ubuntu archive. This has security
  implication and should be avoided. Also this provides pretty bad user
  experience.

  [Fix]
  Add support to Realtek 8723DE.
  All commits are cherry-picked from Realtek maintained repo:
  https://github.com/rtlwifi-linux/rtw88_8723de

  [Test]
  With the patch series applied, 8723DE can scan and connect to APs
  succesfully. Also did some S3 smoke test, it continues to work.

  [Regression Potential]
  Low. The device in question was never supported, and if there's any
  regression, we can count on Realtek Wireless team, thy are now pretty
  responsive on upstream mailing list.

  === Original Bug Report ===
  recently I just installed ubuntu 18.04 lts in dual bot next to windows 10. 
Everything in the installation was fine until the moment to start session. The 
problem is that the wireless network card does not detect me and when entering 
the configuration I simply get an error message saying that no wireless adapter 
was found. I have already followed all the tutorials I found on the web. and 
update the driver of a github repository, and install how much program they 
told me to install and I still can not connect via wifi.

  I just do not know what to do. I have a laptop hp 14-bs004 came with
  windows 10 installed. The information on the network card is as
  follows:

   Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec: 
d723]
  Subsystem: Hewlett-Packard Company Device [103c: 8319]
  Control: I / O + Mem + BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
  Status: Cap + 66MHz- UDF- FastB2B- ParErr- DEVSEL = fast> TAbort-  SERR- 
  Kernel modules: wl

  already install the most recent kernel, already intale driver driver
  realtek rtl8723be according to the instructions of the git repository.
  and nothing has worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  7 22:57:40 2018
  InstallationDate: Installed on 2018-07-08 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_MX.UTF-8
   SHELL=/bin/bash
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1849779] Update Released

[Adam Conrad]

The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  System will auto resume from sleep on receiving LE ADV after paired
  with BT LE devices

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

Bug description:
  System, with Intel 9260 Bluetooth fw ver < REL0472, deep suspend will
  be interrupted and resume automatically once it has been paired with a
  BLE device. The device doesn't have to remain connected, as long as
  there are BLE devices near by broadcasting LE ADV. Known affected fw
  versions are:

  |commit|fw rev/kernel|4.15.0-66-generic|series|
  |-|-|-|-|
  |c2d8f1b7f820|0329|waked up|bionic|
  |ae90c3bce108|0386|waked up| |
  |046d1085b19e|0420|waked up|disco|
  |1e8253bbaafb|0450|waked up| |
  |7444ca40083a|0472|ok| |
  |fe48882708de|0482|ok|eoan| 

  This doesn't seem to apply to all platform with 9260, as there are
  some platforms with identical chip and fw version but are immune from
  this issue.

  Steps to reproduce:
  1. pair with BLE device and turn off the device. It should be listed as 
Disconnected in System Bluetooth settings. Close the settings app as well.
  2. run `sudo btmon -t` in the background, make sure LE ADV packets pop up.
  3. run `sudo btmon -t` on another host to make sure there are LE ADV packets 
during the suspend period.
  3. trigger system deep suspend (S3) on DUT.
  4. wait for around 1 minutes (depending on the surrounding environment) and 
see if the DUT is resumed unsolicitedly.

  Expects:
  DUT only resumes when power button pressed or on other explicit requests.

  Actual:
  DUT resumes unsolicitedly within 1 minutes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.9
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 25 06:50:31 2019
  Dependencies:
   
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1849779/+subscriptions

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

[Kernel-packages] [Bug 1850654] Update Released

[Adam Conrad]

The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  update-initramfs complains of missing amdgpu firmware files

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in linux-firmware source package in Eoan:
  Fix Released

Bug description:
  SRU Justification

  Impact: With 5.3 update-initramfs reports several missing amdgpu
  firmware files:

  update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic
  W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module 
amdgpu

  Of these, only raven_kicker_rlc.bin has been added to upstream linux-
  firmware.

  Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other
  files from modinfo for amdgpu.

  Test Case: Once fixed, the warnings from update-initramfs should be
  gone.

  Regression Potential: Adding a missing firmware is unlikely to break
  any working hardware. Removing the other missing files from modinfo
  will not cause regressions either, however if the firmware is added
  later update-initramfs will not add the files to the initramfs until
  the firmware is added back to modinfo.

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

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

[Kernel-packages] [Bug 1849598] Update Released

[Adam Conrad]

The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU][B/OEM-B/OEM-OSP1/D/E] Add RTL8822cu bluetooth support

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

Bug description:
  SRU justification:

  [Impact]
  Current kernel and firmware lack support of rtl8822cu Bluetooth.

  [Fix]
  Add and update the Bluetooth driver and firmware of rtl8822cu.

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

  [Regression Potential]
  Low.
  Add new bt chip ID;
  Add the new firmware and config to enable new bt chip.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1849598/+subscriptions

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

[Kernel-packages] [Bug 1850739] Update Released

[Adam Conrad]

The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Revert the firmware update for sound/sof

Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-firmware source package in Disco:
  Fix Released
Status in linux-firmware source package in Eoan:
  Fix Released

Bug description:
  SRU Justification

  Impact: An update to the sound sof firmware does not set the PV bit
  for cometlake, and thus will not load. This is a regression on
  cometlake platforms.

  Fix: Revert the update.

  Test Case: Check that the firmware will load on affected platforms.

  Regression Potential: This fixes a regression on cometlake paltforms,
  but will regress the platforms fixed by the patch being reverted.

  ---

  I submitted a firmware update for sound/sof, the tracking bug number
  is: https://bugs.launchpad.net/bugs/1847250

  Recently we found this update introduced one problem for cometlake
  platforms, cometlake need to check PV bit when loading the firmware,
  but this update doesn't set the PV bit for cometlake, as a result, on
  cometlake platforms, it always fails to load the firmware.

  So we should revert this update

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

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

[Kernel-packages] [Bug 1850738] Update Released

[Adam Conrad]

The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Intel Bluetooth AX201 HarrisonPeak (HrP) firmware causes system hang
  in deep suspend

Status in OEM Priority Project:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-firmware source package in Disco:
  Fix Released

Bug description:
  When system has been paired with BLE devices, bluetooth firmware may
  fail to suspend, or even hangs the whole system that it can only be
  rebooted with SysRq keys.

  [Reproduce steps]:

  1. pair with BLE devices. They doesn't have to stay connected/powered
  on during the test.

  2. make sure Bluetooth is now receiving LE ADV broadcats, which should
  leave messages in dmesg like:

   Bluetooth: hci0: advertising data len corrected

  3. suspend the system a few times. With 5.0.0-1025-oem-osp1 kernel,
  symptoms would usually appear in <= 5 times.

  [Results]

  1. one may observed following errors in between the suspend messages:

   PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
   PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -16
   PM: Device :00:14.0 failed to suspend async: error -16
   PM: Some devices failed to suspend, or early wake event detected

 where :00:14.0 is the xHCI Usb hub.

  2. with or without above error messages appear first, system may hang
  and leave only "PM: suspend entry (deep)" in the syslog.

  [Notes]

  * kernels newer than v5.2.1, inclusive of latest v5.4-rc5, still have
  those PM suspend errors, but they doesn't seem to cause system block.
  Instead, they may resume immediately.

  * this was found on one platform with Intel Dual Band Wireless AC 9462
  [8086:02f0] subsystem id [8086:42a4], linux-firmware 1.173.11 with
  intel/ibt-19-0-0.sfi REL0282. However, it's not reproducible on
  another platform with same hw/fw/kernel configuration.

  kernel: [   78.136285] PM: suspend entry (deep)
  kernel: [   78.139836] Filesystems sync: 0.003 seconds
  kernel: [   78.140461] Freezing user space processes ... (elapsed 0.002 
seconds) done.
  kernel: [   78.142669] OOM killer disabled.
  kernel: [   78.142669] Freezing remaining freezable tasks ... (elapsed 0.001 
seconds) done.
  kernel: [   78.143875] printk: Suspending console(s) (use no_console_suspend 
to debug)
  kernel: [   78.335256] sof-audio-pci :00:1f.3: error: no reply expected, 
received 0x0
  kernel: [   78.457675] sof-audio-pci :00:1f.3: firmware boot complete
  kernel: [   78.460486] PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns 
-16
  kernel: [   78.460494] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 
returns -16
  kernel: [   78.460497] PM: Device :00:14.0 failed to suspend async: error 
-16
  kernel: [   78.567263] PM: Some devices failed to suspend, or early wake 
event detected
  kernel: [   78.580871] sof-audio-pci :00:1f.3: error: no reply expected, 
received 0x0
  kernel: [   78.713018] sof-audio-pci :00:1f.3: firmware boot complete
  kernel: [   78.733982] Bluetooth: hci0: advertising data len corrected
  kernel: [   78.792707] nvme nvme0: Shutdown timeout set to 8 seconds
  kernel: [   78.841602] nvme nvme0: 8/0/0 default/read/poll queues
  kernel: [   78.859328] usb 1-4: reset high-speed USB device number 12 using 
xhci_hcd
  kernel: [   79.113113] Bluetooth: hci0: advertising data len corrected
  kernel: [   79.331948] usb 1-4.4: reset high-speed USB device number 14 using 
xhci_hcd
  kernel: [   79.432122] Bluetooth: hci0: advertising data len corrected
  kernel: [   79.559747] usb 1-4.1: reset full-speed USB device number 13 using 
xhci_hcd
  kernel: [   79.887006] acpi LNXPOWER:05: Turning OFF
  kernel: [   79.887265] OOM killer enabled.
  kernel: [   79.887266] Restarting tasks ... done.
  kernel: [   79.926848] PM: suspend exit

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.11 [modified: lib/firmware/intel/ibt-19-0-0.sfi 
lib/firmware/intel/sof/sof-cnl.ri]
  ProcVersionSignature: Ubuntu 5.0.0-1025.28-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1025-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  2037 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 30 22:11:48 2019
  

[Kernel-packages] [Bug 1845317] Re: Add new pci-id's for CML-S, ICL

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted libdrm into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libdrm/2.4.99-1ubuntu1~18.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: libdrm (Ubuntu Bionic)
   Status: New => Fix Committed

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

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

Title:
  Add new pci-id's for CML-S, ICL

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Comet Lake (CML) is basically same gen9 GPU as Sky Lake (SKL) (as is KBL, 
CFL, WHL). There are new CML-S desktop cpu's on the way, and they add three new 
pci-id's that need to be added across the stack in order to use the GPU 
properly.

  There's also one ICL pci-id which was added recently (not in 5.3).

  [Test case]
  The proper way to test is to have an actual machine and boot it up with the 
updated stack, but since these are just pci-id's with no regression potential 
on older hw, it should be fine to just accept them.

  [Regression potential]
  None, just adds new pci-id's to allow the new GPUs to load the proper drivers.

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

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

[Kernel-packages] [Bug 1844155] Re: arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes

[Adam Conrad]

With previous xenial kernels:

XFAIL: nptl/tst-signal6
XFAIL: nptl/tst-thread-exit-clobber
XFAIL: signal/tst-minsigstksz-1
XFAIL: signal/tst-minsigstksz-2
XFAIL: signal/tst-minsigstksz-3
XFAIL: signal/tst-minsigstksz-3a
XFAIL: signal/tst-minsigstksz-4
XFAIL: support/tst-xsigstack

With the kernel in xenial-proposed:

XPASS: nptl/tst-signal6
XPASS: nptl/tst-thread-exit-clobber
XPASS: signal/tst-minsigstksz-1
XPASS: signal/tst-minsigstksz-2
XPASS: signal/tst-minsigstksz-3
XPASS: signal/tst-minsigstksz-3a
XPASS: signal/tst-minsigstksz-4
XPASS: support/tst-xsigstack

I declare this a resounding success and will adjust the tags
accordingly.

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

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

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

Title:
  arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux package in Debian:
  Fix Released

Bug description:
  [Impact]

  The arm64 kernel allows one to run aarch32 processes on an aarch64
  processor, using the standard 32/64-bit syscall compatibility. However
  this compat layer does not correctly validate the arguments of the
  sigaltstack syscall which can result in process failures.

  [Test Case]

  The simple reproducer from https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=904385 triggers a memory allocation error with
  the current Xenial 4.4 kernel.

  [Fix]

  Backport the following two upstream commits:
  24951465cbd2 arm64: compat: Provide definition for COMPAT_SIGMINSTKSZ
  22839869f21a signal: Introduce COMPAT_SIGMINSTKSZ for use in 
compat_sys_sigaltstack

  With these two commits, the reproducer no longer fails.

  [Regression Potential]

  Low. the modifications are trivial and the two patches have been in
  upstream for quite a while.

  [Original Description]

  This seems to have been fixed in 4.15 (finally), but is still an issue
  in the 4.4 kernel used on our builders, and possibly others as well
  (needs investigation).

  The original Debian bug report linked has more info, as well as the
  patchset on lkml at https://lkml.org/lkml/2018/7/25/409

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

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

[Kernel-packages] [Bug 1850654] Re: update-initramfs complains of missing amdgpu firmware files

[Adam Conrad]

Hello Seth, or anyone else affected,

Accepted linux-firmware into eoan-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.183.2 in a few hours, and then in the -proposed repository.

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

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

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

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

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

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

Title:
  update-initramfs complains of missing amdgpu firmware files

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-firmware source package in Bionic:
  New
Status in linux source package in Eoan:
  Confirmed
Status in linux-firmware source package in Eoan:
  Fix Committed

Bug description:
  SRU Justification

  Impact: With 5.3 update-initramfs reports several missing amdgpu
  firmware files:

  update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic
  W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module 
amdgpu

  Of these, only raven_kicker_rlc.bin has been added to upstream linux-
  firmware.

  Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other
  files from modinfo for amdgpu.

  Test Case: Once fixed, the warnings from update-initramfs should be
  gone.

  Regression Potential: Adding a missing firmware is unlikely to break
  any working hardware. Removing the other missing files from modinfo
  will not cause regressions either, however if the firmware is added
  later update-initramfs will not add the files to the initramfs until
  the firmware is added back to modinfo.

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

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

[Kernel-packages] [Bug 1849598] Re: [SRU][B/OEM-B/OEM-OSP1/D/E] Add RTL8822cu bluetooth support

[Adam Conrad]

Hello AaronMa, or anyone else affected,

Accepted linux-firmware into eoan-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.183.2 in a few hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  [SRU][B/OEM-B/OEM-OSP1/D/E] Add RTL8822cu bluetooth support

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

Bug description:
  SRU justification:

  [Impact]
  Current kernel and firmware lack support of rtl8822cu Bluetooth.

  [Fix]
  Add and update the Bluetooth driver and firmware of rtl8822cu.

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

  [Regression Potential]
  Low.
  Add new bt chip ID;
  Add the new firmware and config to enable new bt chip.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1849598/+subscriptions

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

[Kernel-packages] [Bug 1780590] Re: Add support for Realtek 8723DE wireless adapter

[Adam Conrad]

Hello manuel, or anyone else affected,

Accepted linux-firmware into eoan-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.183.2 in a few hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  Add support for Realtek 8723DE wireless adapter

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Won't Fix
Status in linux-firmware source package in Bionic:
  New
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Disco:
  Won't Fix
Status in linux-firmware source package in Disco:
  New
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Won't Fix
Status in linux-firmware source package in Eoan:
  Fix Committed
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Confirmed
Status in linux-firmware source package in Focal:
  New
Status in linux-oem-osp1 source package in Focal:
  Won't Fix

Bug description:
  === SRU Justification ===
  [Impact]
  There's no in-kernel support for Realtek 8723DE, so users need to use
  out-of-tree DKMS which is not from Ubuntu archive. This has security
  implication and should be avoided. Also this provides pretty bad user
  experience.

  [Fix]
  Add support to Realtek 8723DE.
  All commits are cherry-picked from Realtek maintained repo:
  https://github.com/rtlwifi-linux/rtw88_8723de

  [Test]
  With the patch series applied, 8723DE can scan and connect to APs
  succesfully. Also did some S3 smoke test, it continues to work.

  [Regression Potential]
  Low. The device in question was never supported, and if there's any
  regression, we can count on Realtek Wireless team, thy are now pretty
  responsive on upstream mailing list.

  === Original Bug Report ===
  recently I just installed ubuntu 18.04 lts in dual bot next to windows 10. 
Everything in the installation was fine until the moment to start session. The 
problem is that the wireless network card does not detect me and when entering 
the configuration I simply get an error message saying that no wireless adapter 
was found. I have already followed all the tutorials I found on the web. and 
update the driver of a github repository, and install how much program they 
told me to install and I still can not connect via wifi.

  I just do not know what to do. I have a laptop hp 14-bs004 came with
  windows 10 installed. The information on the network card is as
  follows:

   Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec: 
d723]
  Subsystem: Hewlett-Packard Company Device [103c: 8319]
  Control: I / O + Mem + BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
  Status: Cap + 66MHz- UDF- FastB2B- ParErr- DEVSEL = fast> TAbort-  SERR- 
  Kernel modules: wl

  already install the most recent kernel, already intale driver driver
  realtek rtl8723be according to the instructions of the git repository.
  and nothing has worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  7 22:57:40 2018
  InstallationDate: Installed on 2018-07-08 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_MX.UTF-8
   SHELL=/bin/bash
  

[Kernel-packages] [Bug 1850739] Re: Revert the firmware update for sound/sof

[Adam Conrad]

Hello Hui, or anyone else affected,

Accepted linux-firmware into eoan-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.183.2 in a few hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  Revert the firmware update for sound/sof

Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-firmware source package in Bionic:
  New
Status in linux-firmware source package in Disco:
  New
Status in linux-firmware source package in Eoan:
  Fix Committed

Bug description:
  SRU Justification

  Impact: An update to the sound sof firmware does not set the PV bit
  for cometlake, and thus will not load. This is a regression on
  cometlake platforms.

  Fix: Revert the update.

  Test Case: Check that the firmware will load on affected platforms.

  Regression Potential: This fixes a regression on cometlake paltforms,
  but will regress the platforms fixed by the patch being reverted.

  ---

  I submitted a firmware update for sound/sof, the tracking bug number
  is: https://bugs.launchpad.net/bugs/1847250

  Recently we found this update introduced one problem for cometlake
  platforms, cometlake need to check PV bit when loading the firmware,
  but this update doesn't set the PV bit for cometlake, as a result, on
  cometlake platforms, it always fails to load the firmware.

  So we should revert this update

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

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

[Kernel-packages] [Bug 1824407] Re: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files

[Adam Conrad]

I didn't mean actually random, and I think clock-based would be entirely
fine, but my paranoia about stacking two things with identical
superblocks might be just paranoia too.  I dunno.

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

Title:
  remount of multilower moved pivoted-root overlayfs root, results in
  I/O errors on some modified files

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe source package in Bionic:
  Confirmed

Bug description:
  1) Download focal subiquity pending image, or eoan release image
  2) boot, and press ESC and edit boot command line (F6 in bios, e in UEFI)
  3) After --- insert the following options

     break=top debug init=/bin/bash

  4) Continue boot (Enter in BIOS, ctrl+x in UEFI)
  5) in the initramfs execute:

  rm /scripts/casper-bottom/25adduser
  exit

  6) you will be dropped into pivoted root filesystem, before systemd is execed 
as pid one
  7) /run/initramfs/ will contain a debug log, showing how everything was 
mounted. Ie. cdrom mounted, squashfs losetup from there, then multilower 
overlay setup from them, moved to /root, and then pivot-root to /root done to 
finally end up as /. Underlying layers are moved into /cow for your convenience.

  8) At this point modifying zero-byte length files, that exist in the
  lowest layer, but not the middle one, in certain ways, will results in
  them to be corrupted, after / is remounted.

  9) Corruption examples

  (On both focal & eoan)

  cat /etc/.pwd.lock
  systemd-sysusers
  cat /etc/.pwd.lock
  mount -o remount /
  cat /etc/.pwd.lock
  overlayfs: invalid origin (etc/.pwd.lock, ftype=8000, origin ftype=4000)
  cat: /etc/.pwd.lock: Input/output error

  (Only on eoan)

  cat /etc/machine-id
  systemd-machine-id-setup
  cat /etc/machine-id
  mount -o remount /
  cat /etc/machine-id
  overlayfs: invalid origin (etc/machine-id, ftype=8000, origin ftype=4000)
  cat: /etc/machine-id: Input/output error

  Lots of things break once machine-id and .pwd.lock are corrupted. I.e.
  unable to dhcp, connect to dbus, add/remove/change users or groups,
  etc.

  We were unable to recreate the issue outside of booting things with
  casper. Ie. statically on a regular host machine without pivot-root.
  But hopefully booting to a quite state with nothing running is
  sufficient to reproduce this.

  Instead of booting with `bebroken init=/bin/bash` you can boot with
  `bebroken systemd.mask=systemd-remount-fs.service` this will complete
  the boot, with /etc/machine-id & .pwd.lock modified, meaning that
  remount of / will cause IO errors on those files.

  Currently, we are shipping two hacks in casper's 25adduser script to
  "rm" the offending files, and create them again on the upper rw layer.
  They then survive remount without i/o errors. However, we'd rather not
  ship those hacks, and have kernel overlay fixed to work correctly with
  multi-lower-dir and not corrupt files upon remounting /.

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

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

[Kernel-packages] [Bug 1824407] Re: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files

[Adam Conrad]

While there may be arguments for synthesizing UUIDs in various fs
drivers, or creating them in the first place in fs-creation tools, I
agree that if overlayfs has a hard dependency on UUIDs for uniquely
identifying layers, it needs to fill in the gaps where the previous
tools/drivers failed to provide.

So, yeah, I think Colin's on the right track here with making overlayfs
itself fix its own use-case, which will cover any future filesystem/tool
that otherwise fails to UUID itself.

My only review of the above is that you might want to mix a monotonic or
random seed in with your superblock when generating your fake UUIDs, in
case someone does something like stacking multiple empties on top of
each other, or some other madness where you effectively have the same
superblock more than once at the RO level, but need to identify them as
different.

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

Title:
  remount of multilower moved pivoted-root overlayfs root, results in
  I/O errors on some modified files

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe source package in Bionic:
  Confirmed

Bug description:
  1) Download focal subiquity pending image, or eoan release image
  2) boot, and press ESC and edit boot command line (F6 in bios, e in UEFI)
  3) After --- insert the following options

     break=top debug init=/bin/bash

  4) Continue boot (Enter in BIOS, ctrl+x in UEFI)
  5) in the initramfs execute:

  rm /scripts/casper-bottom/25adduser
  exit

  6) you will be dropped into pivoted root filesystem, before systemd is execed 
as pid one
  7) /run/initramfs/ will contain a debug log, showing how everything was 
mounted. Ie. cdrom mounted, squashfs losetup from there, then multilower 
overlay setup from them, moved to /root, and then pivot-root to /root done to 
finally end up as /. Underlying layers are moved into /cow for your convenience.

  8) At this point modifying zero-byte length files, that exist in the
  lowest layer, but not the middle one, in certain ways, will results in
  them to be corrupted, after / is remounted.

  9) Corruption examples

  (On both focal & eoan)

  cat /etc/.pwd.lock
  systemd-sysusers
  cat /etc/.pwd.lock
  mount -o remount /
  cat /etc/.pwd.lock
  overlayfs: invalid origin (etc/.pwd.lock, ftype=8000, origin ftype=4000)
  cat: /etc/.pwd.lock: Input/output error

  (Only on eoan)

  cat /etc/machine-id
  systemd-machine-id-setup
  cat /etc/machine-id
  mount -o remount /
  cat /etc/machine-id
  overlayfs: invalid origin (etc/machine-id, ftype=8000, origin ftype=4000)
  cat: /etc/machine-id: Input/output error

  Lots of things break once machine-id and .pwd.lock are corrupted. I.e.
  unable to dhcp, connect to dbus, add/remove/change users or groups,
  etc.

  We were unable to recreate the issue outside of booting things with
  casper. Ie. statically on a regular host machine without pivot-root.
  But hopefully booting to a quite state with nothing running is
  sufficient to reproduce this.

  Instead of booting with `bebroken init=/bin/bash` you can boot with
  `bebroken systemd.mask=systemd-remount-fs.service` this will complete
  the boot, with /etc/machine-id & .pwd.lock modified, meaning that
  remount of / will cause IO errors on those files.

  Currently, we are shipping two hacks in casper's 25adduser script to
  "rm" the offending files, and create them again on the upper rw layer.
  They then survive remount without i/o errors. However, we'd rather not
  ship those hacks, and have kernel overlay fixed to work correctly with
  multi-lower-dir and not corrupt files upon remounting /.

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

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

[Kernel-packages] [Bug 1844155] Re: arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes

[Adam Conrad]

I completely missed the verification ping here in the sea of other
kernel bug mail that I get.  Will work with the LP team to get this
verified as quickly as I can, but if you need to make a revert/ship call
before I can, the patches should be pretty harmless even if they don't
fix the bug, so I'd vote for keep and ship and we can fix later if we
missed a bit.

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

Title:
  arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in linux package in Debian:
  Fix Released

Bug description:
  [Impact]

  The arm64 kernel allows one to run aarch32 processes on an aarch64
  processor, using the standard 32/64-bit syscall compatibility. However
  this compat layer does not correctly validate the arguments of the
  sigaltstack syscall which can result in process failures.

  [Test Case]

  The simple reproducer from https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=904385 triggers a memory allocation error with
  the current Xenial 4.4 kernel.

  [Fix]

  Backport the following two upstream commits:
  24951465cbd2 arm64: compat: Provide definition for COMPAT_SIGMINSTKSZ
  22839869f21a signal: Introduce COMPAT_SIGMINSTKSZ for use in 
compat_sys_sigaltstack

  With these two commits, the reproducer no longer fails.

  [Regression Potential]

  Low. the modifications are trivial and the two patches have been in
  upstream for quite a while.

  [Original Description]

  This seems to have been fixed in 4.15 (finally), but is still an issue
  in the 4.4 kernel used on our builders, and possibly others as well
  (needs investigation).

  The original Debian bug report linked has more info, as well as the
  patchset on lkml at https://lkml.org/lkml/2018/7/25/409

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

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

[Kernel-packages] [Bug 1849665] Re: zfs diff: Unable to determine path or stats for object

[Adam Conrad]

Hello Andreas, or anyone else affected,

Accepted zfs-linux into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/zfs-
linux/0.8.1-1ubuntu14.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

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

Title:
  zfs diff: Unable to determine path or stats for object

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Eoan:
  Fix Committed

Bug description:
  == SRU Justification, Eoan ==

  Using zfs diff on an encrypted dataset with large objects one can hit
  an error such as follows:

  # zfs diff nsnx/trusty-2a@snap1 nsnx/trusty-2a
  + /nsnx/trusty-2a/bin
  Unable to determine path or stats for object 5 in 
nsnx/trusty-2a@zfs-diff-32359-00010001f165: File exists

  == Fix ==

  Upstream commit d359e99c38f667 ("diff_cb() does not handle large
  dnodes") as addressed in ZFS bug fix:
  https://github.com/zfsonlinux/zfs/pull/9343

  == Testcase ==

  # mkdir /zfs-test
  # cd /zfs-test
  # truncate -s 10G file.img
  # zpool create -o ashift=12 -O acltype=posixacl -O compression=lz4 -O 
xattr=sa -O normalization=formD -O dnodesize=auto tank $(pwd)/file.img
  # zfs create tank/d1 -o encryption=on -o keyformat=passphrase
  Enter passphrase:
  Re-enter passphrase:
  # dd if=/dev/urandom bs=4k of=/tank/d1/somedata.bin count=10240
  10240+0 records in
  10240+0 records out
  41943040 bytes (42 MB, 40 MiB) copied, 0,304365 s, 138 MB/s
  # zfs snapshot tank/d1@s1
  # dd if=/dev/urandom bs=4k of=/tank/d1/somedata2.bin count=10240
  10240+0 records in
  10240+0 records out
  41943040 bytes (42 MB, 40 MiB) copied, 0,305324 s, 137 MB/s

  Without the fix, one hits an error such as:

  # zfs diff tank/d1@s1 tank/d1
  Unable to determine path or stats for object 3 in tank/d1@s1: File exists

  With the fix, we get:
  + /tank/d1/somedata2.bin
  M /tank/d1/

  == Regression Potential ==

  This is a minor change in module/zfs/dmu_diff.c and it only affects
  the zfs diff component, so this should not affect ZFS in terms of file
  system corruption/data loss.  This has also been upstream regression
  tested and passes the Ubuntu ZFS regressions tests too.  So the risk
  is limited.

  
  -

  Eoan 19.10
  zfsutils-linux 0.8.1-1ubuntu14
  kernel 5.3.0-19-generic #20-Ubuntu

  When using zfs diff on an encrypted dataset, I frequently encounter
  this error:

  # zfs diff nsnx/trusty-2a@snap1 nsnx/trusty-2a
  + /nsnx/trusty-2a/bin
  Unable to determine path or stats for object 5 in 
nsnx/trusty-2a@zfs-diff-32359-00010001f165: File exists

  I believe this to be upstream bug
  https://github.com/zfsonlinux/zfs/issues/7678, fixed with
  https://github.com/zfsonlinux/zfs/pull/9343

  Here is one way to reproduce it:

  # mkdir /zfs-test
  # cd /zfs-test
  # truncate -s 10G file.img
  # zpool create -o ashift=12 -O acltype=posixacl -O compression=lz4 -O 
xattr=sa -O normalization=formD -O dnodesize=auto tank $(pwd)/file.img
  # zfs create tank/d1 -o encryption=on -o keyformat=passphrase
  Enter passphrase:
  Re-enter passphrase:
  # dd if=/dev/urandom bs=4k of=/tank/d1/somedata.bin count=10240
  10240+0 records in
  10240+0 records out
  41943040 bytes (42 MB, 40 MiB) copied, 0,304365 s, 138 MB/s
  # zfs snapshot tank/d1@s1
  # dd if=/dev/urandom bs=4k of=/tank/d1/somedata2.bin count=10240
  10240+0 records in
  10240+0 records out
  41943040 bytes (42 MB, 40 MiB) copied, 0,305324 s, 137 MB/s
  # zfs diff tank/d1@s1 tank/d1
  Unable to determine path or stats for object 3 in tank/d1@s1: File exists

  There may be a simpler way to test this, but this should be enough to
  start with.

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

-- 
Mailing 

[Kernel-packages] [Bug 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2

[Adam Conrad]

Ah-ha.  If loop0 is in use, then the test-case appropriately fails in
both unstable and eoan, which is comforting, as I didn't look forward to
figuring out why this works in Debian (it doesn't).

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

Title:
  losetup -f broken in 2.0.6-1ubuntu2

Status in gcc-9 package in Ubuntu:
  New
Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in gcc-9 source package in Eoan:
  New
Status in klibc source package in Eoan:
  New
Status in linux source package in Eoan:
  Incomplete
Status in gcc-9 source package in Focal:
  New
Status in klibc source package in Focal:
  New
Status in linux source package in Focal:
  Incomplete

Bug description:
  [Impact]

   * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt,
  as main(argc) is reset to zero, after ioctl() operations in a function
  call, quite unexpectadly.

  [Test Case]

   * $ sudo /usr/lib/klibc/bin/losetup -vf
  Loop device is /dev/loop20
  loop: can't get info on device /dev/loop20: No such device or address

  is bad.

  Note that ioctl() must succeed, thus loop0 device must be configured
  to trigger the bug.

  
  [Regression Potential]

   * klibc is quite special, as it uses linux kernel headers/assembly.
  It seems like there is incompatibility between klibc sources, and
  gcc-9 with linux-5.3 when used to build userspace programmes.

   * disabling cf-protection and stack-clash-protection did not help.

   * building with gcc-8 does not exhibit the problem.

   * the workaround is quite simple in the code, keep a copy of argc to
  compare to it later in the code.

  [Other Info]

   * Original bug report

  http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz

  ...
  [   11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 
subsystem
  [   11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: 
(null)
  loop: can't get info on device /dev/loop1: No such device or address

  BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs) + mkdir result
  + set -x
  + read LINE
  + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt
  ++ grep -q /rofs result/lsblk.txt
  grep: result/lsblk.txt: No such file or directory
  autopkgtest [21:45:45]: test boot: ---]
  autopkgtest [21:45:45]: test boot:  - - - - - - - - - - results - - - - - - - 
- - -
  boot FAIL non-zero exit status 2
  autopkgtest [21:45:45]:  summary
  boot FAIL non-zero exit status 2
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1850184/+subscriptions

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

[Kernel-packages] [Bug 1850184] Re: losetup -f broken in 2.0.6-1ubuntu2

[Adam Conrad]

The testcase here doesn't seem to be working (or, rather, failing) for
me, which makes it harder to investigate this.  It passes on both sid
and eoan for me:

(sid-amd64)root@nosferatu:~# dpkg -l \*klibc\*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---===
ii  klibc-utils2.0.7-1  amd64small utilities built with klibc 
for early boot
ii  libklibc:amd64 2.0.7-1  amd64minimal libc subset for use with 
initramfs
(sid-amd64)root@nosferatu:~# /usr/lib/klibc/bin/losetup -vf
Loop device is /dev/loop0
/dev/loop0
(sid-amd64)root@nosferatu:~# 

(eoan-amd64)root@nosferatu:~# dpkg -l \*klibc\*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   VersionArchitecture Description
+++-==-==--===
ii  klibc-utils2.0.6-1ubuntu2 amd64small utilities built with klibc 
for early boot
ii  libklibc:amd64 2.0.6-1ubuntu2 amd64minimal libc subset for use with 
initramfs
(eoan-amd64)root@nosferatu:~# /usr/lib/klibc/bin/losetup -vf
Loop device is /dev/loop0
/dev/loop0
(eoan-amd64)root@nosferatu:~#

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

Title:
  losetup -f broken in 2.0.6-1ubuntu2

Status in gcc-9 package in Ubuntu:
  New
Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in gcc-9 source package in Eoan:
  New
Status in klibc source package in Eoan:
  New
Status in linux source package in Eoan:
  Incomplete
Status in gcc-9 source package in Focal:
  New
Status in klibc source package in Focal:
  New
Status in linux source package in Focal:
  Incomplete

Bug description:
  [Impact]

   * sudo /usr/lib/klibc/bin/losetup -vf, which appears to be missbuilt,
  as main(argc) is reset to zero, after ioctl() operations in a function
  call, quite unexpectadly.

  [Test Case]

   * $ sudo /usr/lib/klibc/bin/losetup -vf
  Loop device is /dev/loop20
  loop: can't get info on device /dev/loop20: No such device or address

  is bad.

  Note that ioctl() must succeed, thus loop0 device must be configured
  to trigger the bug.

  
  [Regression Potential]

   * klibc is quite special, as it uses linux kernel headers/assembly.
  It seems like there is incompatibility between klibc sources, and
  gcc-9 with linux-5.3 when used to build userspace programmes.

   * disabling cf-protection and stack-clash-protection did not help.

   * building with gcc-8 does not exhibit the problem.

   * the workaround is quite simple in the code, keep a copy of argc to
  compare to it later in the code.

  [Other Info]

   * Original bug report

  http://autopkgtest.ubuntu.com/packages/c/casper/focal/amd64

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/amd64/c/casper/20191025_214555_df8b8@/log.gz

  ...
  [   11.751912] EXT4-fs (sda1): mounting ext2 file system using the ext4 
subsystem
  [   11.761441] EXT4-fs (sda1): mounted filesystem without journal. Opts: 
(null)
  loop: can't get info on device /dev/loop1: No such device or address

  BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs) + mkdir result
  + set -x
  + read LINE
  + grep -e '^--OUT .* BEGIN-- .* --END--$' qemu-output.txt
  ++ grep -q /rofs result/lsblk.txt
  grep: result/lsblk.txt: No such file or directory
  autopkgtest [21:45:45]: test boot: ---]
  autopkgtest [21:45:45]: test boot:  - - - - - - - - - - results - - - - - - - 
- - -
  boot FAIL non-zero exit status 2
  autopkgtest [21:45:45]:  summary
  boot FAIL non-zero exit status 2
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1850184/+subscriptions

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

[Kernel-packages] [Bug 1848848] Update Released

[Adam Conrad]

The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Firmware for Radeon RX5700 (navi10) missing / boot failure

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

Bug description:
  As an owner of a Radeon RX5700 GPU, I was really looking forward to
  the Eoan release which includes the Linux Kernel 5.3 and Mesa 19.2 -
  both with finally Radeon RX5700 (navi10) support. However, upgrading
  my system from Kubuntu 18.10 (working) via 19.04 (does not boot) to
  19.10 resulted in a boot failure. Last message shown on the screen is:

  fb0: switching to amdgpudrmfb from EFI VGA

  After some research I found that the package linux-firmware does not
  include the necessary files /lib/firmware/amdgpu/navi10_*. After I
  manually copied the missing files from the repository
  git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git, I was able to boot normally.

  Please update the package linux-firmware and add the needed firmware.

  
  $ lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10
  $ apt-cache policy linux-firmware
  linux-firmware:
Installiert:   1.183
Installationskandidat: 1.183
Versionstabelle:
   *** 1.183 500
  500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu eoan/main i386 Packages
  100 /var/lib/dpkg/status

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

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

[Kernel-packages] [Bug 1848848] Re: Firmware for Radeon RX5700 (navi10) missing / boot failure

[Adam Conrad]

@sforshee: Given the severity of this issue, and that it's only adding
new files, I'm inclined to say we fasttrack the release, but I'd also
like to see a follow-up upload that includes the missing files the
drivers reference (if they exist), or patch the drivers to stop
referencing them (if they don't, and won't).

Any opinions on both those things?

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

Title:
  Firmware for Radeon RX5700 (navi10) missing / boot failure

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

Bug description:
  As an owner of a Radeon RX5700 GPU, I was really looking forward to
  the Eoan release which includes the Linux Kernel 5.3 and Mesa 19.2 -
  both with finally Radeon RX5700 (navi10) support. However, upgrading
  my system from Kubuntu 18.10 (working) via 19.04 (does not boot) to
  19.10 resulted in a boot failure. Last message shown on the screen is:

  fb0: switching to amdgpudrmfb from EFI VGA

  After some research I found that the package linux-firmware does not
  include the necessary files /lib/firmware/amdgpu/navi10_*. After I
  manually copied the missing files from the repository
  git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git, I was able to boot normally.

  Please update the package linux-firmware and add the needed firmware.

  
  $ lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10
  $ apt-cache policy linux-firmware
  linux-firmware:
Installiert:   1.183
Installationskandidat: 1.183
Versionstabelle:
   *** 1.183 500
  500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu eoan/main i386 Packages
  100 /var/lib/dpkg/status

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

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

[Kernel-packages] [Bug 1848848] Re: Firmware for Radeon RX5700 (navi10) missing / boot failure

[Adam Conrad]

** Tags added: verification-needed-eoan

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

Title:
  Firmware for Radeon RX5700 (navi10) missing / boot failure

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

Bug description:
  As an owner of a Radeon RX5700 GPU, I was really looking forward to
  the Eoan release which includes the Linux Kernel 5.3 and Mesa 19.2 -
  both with finally Radeon RX5700 (navi10) support. However, upgrading
  my system from Kubuntu 18.10 (working) via 19.04 (does not boot) to
  19.10 resulted in a boot failure. Last message shown on the screen is:

  fb0: switching to amdgpudrmfb from EFI VGA

  After some research I found that the package linux-firmware does not
  include the necessary files /lib/firmware/amdgpu/navi10_*. After I
  manually copied the missing files from the repository
  git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git, I was able to boot normally.

  Please update the package linux-firmware and add the needed firmware.

  
  $ lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10
  $ apt-cache policy linux-firmware
  linux-firmware:
Installiert:   1.183
Installationskandidat: 1.183
Versionstabelle:
   *** 1.183 500
  500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu eoan/main i386 Packages
  100 /var/lib/dpkg/status

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

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

[Kernel-packages] [Bug 1848848] Please test proposed package

[Adam Conrad]

Hello Christian, or anyone else affected,

Accepted linux-firmware into eoan-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.183.1 in a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: linux-firmware (Ubuntu Bionic)
   Status: Fix Committed => 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/1848848

Title:
  Firmware for Radeon RX5700 (navi10) missing / boot failure

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

Bug description:
  As an owner of a Radeon RX5700 GPU, I was really looking forward to
  the Eoan release which includes the Linux Kernel 5.3 and Mesa 19.2 -
  both with finally Radeon RX5700 (navi10) support. However, upgrading
  my system from Kubuntu 18.10 (working) via 19.04 (does not boot) to
  19.10 resulted in a boot failure. Last message shown on the screen is:

  fb0: switching to amdgpudrmfb from EFI VGA

  After some research I found that the package linux-firmware does not
  include the necessary files /lib/firmware/amdgpu/navi10_*. After I
  manually copied the missing files from the repository
  git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git, I was able to boot normally.

  Please update the package linux-firmware and add the needed firmware.

  
  $ lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10
  $ apt-cache policy linux-firmware
  linux-firmware:
Installiert:   1.183
Installationskandidat: 1.183
Versionstabelle:
   *** 1.183 500
  500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu eoan/main i386 Packages
  100 /var/lib/dpkg/status

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

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

[Kernel-packages] [Bug 1847927] Re: Upgrading of 20191010 installed on ZFS will lead to "device-mapper: reload ioctl on osprober-linux-sda6 failed: Device or resource busy" and then to auto-removal of

[Adam Conrad]

20191012 is the only one where this is expected to work, however for
other hilarious reasons, you need to boot in the live session, upgrade
to ubiquity from eoan-proposed (19.10.20), then run the installer.

This should all be in better shape with tonight's images when we spin
them (expected serial of 20191014)

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

Title:
  Upgrading of 20191010 installed on ZFS will lead to "device-mapper:
  reload ioctl on osprober-linux-sda6  failed: Device or resource busy"
  and then to auto-removal of all zfs packages

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 19.10 from 20191010 ISO
  2. Run `sudo apt-get update` and `sudo apt-get upgrade`
  3. Note the following lines in the APT output:

  ...
  Warning: Couldn't find any valid initrd for dataset rpool/ROOT/ubuntu_69xc2t.
  Found memtest86+ image: /BOOT/ubuntu_69xc2t@/memtest86+.elf
  Found memtest86+ image: /BOOT/ubuntu_69xc2t@/memtest86+.bin
  device-mapper: reload ioctl on osprober-linux-sda6  failed: Device or 
resource busy
  Command failed.
  done
  ...
  device-mapper: reload ioctl on osprober-linux-sda6  failed: Device or 
resource busy
  Command failed.
  done

  4. Run `sudo apt-get autoremove --purge`

  $ sudo apt-get autoremove --purge
  [sudo] password for zfs: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
libnvpair1linux* libuutil1linux* libzfs2linux* libzpool2linux* 
zfs-initramfs* zfs-zed* zfsutils-linux*
  0 upgraded, 0 newly installed, 7 to remove and 0 not upgraded.
  After this operation, 5 243 kB disk space will be freed.
  Do you want to continue? [Y/n] n
  Abort.

  
  Expected results:
  * upgrading of packages run without errors

  Actual results:
  * system will not boot if user will proceed with package autoremoval

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libzfs2linux 0.8.1-1ubuntu14
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 13 22:51:39 2019
  InstallationDate: Installed on 2019-10-13 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191010)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1847927] Re: Upgrading of 20191010 installed on ZFS will lead to "device-mapper: reload ioctl on osprober-linux-sda6 failed: Device or resource busy" and then to auto-removal of

[Adam Conrad]

The autoremoval part should be fixed if you install from a more recent
image.

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

Title:
  Upgrading of 20191010 installed on ZFS will lead to "device-mapper:
  reload ioctl on osprober-linux-sda6  failed: Device or resource busy"
  and then to auto-removal of all zfs packages

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 19.10 from 20191010 ISO
  2. Run `sudo apt-get update` and `sudo apt-get upgrade`
  3. Note the following lines in the APT output:

  ...
  Warning: Couldn't find any valid initrd for dataset rpool/ROOT/ubuntu_69xc2t.
  Found memtest86+ image: /BOOT/ubuntu_69xc2t@/memtest86+.elf
  Found memtest86+ image: /BOOT/ubuntu_69xc2t@/memtest86+.bin
  device-mapper: reload ioctl on osprober-linux-sda6  failed: Device or 
resource busy
  Command failed.
  done
  ...
  device-mapper: reload ioctl on osprober-linux-sda6  failed: Device or 
resource busy
  Command failed.
  done

  4. Run `sudo apt-get autoremove --purge`

  $ sudo apt-get autoremove --purge
  [sudo] password for zfs: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
libnvpair1linux* libuutil1linux* libzfs2linux* libzpool2linux* 
zfs-initramfs* zfs-zed* zfsutils-linux*
  0 upgraded, 0 newly installed, 7 to remove and 0 not upgraded.
  After this operation, 5 243 kB disk space will be freed.
  Do you want to continue? [Y/n] n
  Abort.

  
  Expected results:
  * upgrading of packages run without errors

  Actual results:
  * system will not boot if user will proceed with package autoremoval

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libzfs2linux 0.8.1-1ubuntu14
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 13 22:51:39 2019
  InstallationDate: Installed on 2019-10-13 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191010)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1836635] Re: Bionic: support for Solarflare X2542 network adapter (sfc driver)

[Adam Conrad]

Hello Mauricio, or anyone else affected,

Accepted debian-installer into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/debian-
installer/20101020ubuntu543.11 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

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

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

Title:
  Bionic: support for Solarflare X2542 network adapter (sfc driver)

Status in debian-installer package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in debian-installer source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in debian-installer source package in Cosmic:
  Invalid
Status in linux source package in Cosmic:
  Invalid
Status in debian-installer source package in Disco:
  Invalid
Status in linux source package in Disco:
  Invalid
Status in debian-installer source package in Eoan:
  Invalid
Status in linux source package in Eoan:
  Invalid

Bug description:
  [Impact]

   * Support for Solarflare X2542 network adapter
     (Medford2 / SFC9250) in the Bionic sfc driver.

   * This network adapter is present on recent hardware,
     at least HP 2019 and Dell PowerEdge R740xd systems.

   * On recent-hardware deployments that would rather use
     the Bionic LTS / GA supported kernel and cannot move
     to HWE kernels this adapter is non functional at all.

  [Test Case]

   * The X2542 adapter has been exercised with iperf3 and nc
     across 2 hosts on 25G link speed w/ MTUs 1400/1500/9000
     on both directions, for 1 week.

     Its performance is on par with the Cosmic 4.18 kernel
     (which contains all these patches) and the out-of-tree
     driver from the vendor.

   * The 7000 series adapter (for regression testing an old model,
     supported previously) has been exercised with iperf and netperf
     (TCP_STREAM, UDP_STREAM, TCP_RR, UDP_RR, and TCP_CRR) in one
     host (client/server in different adapter ports isolated with
     network namespaces, so traffic goes through the network switch),
     on 10G link speed on MTUs 1500/9000, for 1 weekend.

     No regressions observed between the original and test kernels.

  [Regression Potential]

   * The patchset touches a lot of the sfc driver, so the potential
     for regression definitely exists. Thus, a lot of consideration
     and testing happened:

   * It has been tested on other adapter which uses the old code,
     and no regressions were found so far (see 7000 series above).

   * The patchset is exclusively cherry-picks, no single backport.

   * The patchset essentially moves the Bionic driver up in the
     upstream 'git log --oneline -- drivers/net/ethernet/sfc/':

     - since commit d4a7a8893d4c ("sfc: pass valid pointers from 
efx_enqueue_unwind")
     - until commit 7f61e6c6279b ("sfc: support FEC configuration through 
ethtool")
     - except for 2 commits (not needed / unrelated)
   - commit 42356d9a137b ("sfc: support RSS spreading of ethtool ntuple 
filters")
   - commit 9baeb5eb1f83 ("sfc: falcon: remove duplicated bit-wise or of 
LOOPBACK_SGMII")
     - plus 2 more recent commits (fixes)
   - commit 458bd99e4974 ("sfc: remove ctpio_dmabuf_start from stats")
   - commit 0c235113b3c4 ("sfc: stop the TX queue before pushing new 
buffers")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1836635/+subscriptions

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

[Kernel-packages] [Bug 1844155] Re: arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes

[Adam Conrad]

Confirmed that this is fixed in 4.15 as of (at least) 4.15.0-62-generic.

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

Title:
  arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes

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

Bug description:
  This seems to have been fixed in 4.15 (finally), but is still an issue
  in the 4.4 kernel used on our builders, and possibly others as well
  (needs investigation).

  The original Debian bug report linked has more info, as well as the
  patchset on lkml at https://lkml.org/lkml/2018/7/25/409

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

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

[Kernel-packages] [Bug 1844155] [NEW] arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes

[Adam Conrad]

Public bug reported:

This seems to have been fixed in 4.15 (finally), but is still an issue
in the 4.4 kernel used on our builders, and possibly others as well
(needs investigation).

The original Debian bug report linked has more info, as well as the
patchset on lkml at https://lkml.org/lkml/2018/7/25/409

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

** Affects: linux (Debian)
 Importance: Unknown
 Status: Unknown

** Bug watch added: Debian Bug tracker #904385
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904385

** Also affects: linux (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904385
   Importance: Unknown
   Status: Unknown

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

Title:
  arm64: sigaltstack fails with MINSIGSTKSZ for 32-bit processes

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

Bug description:
  This seems to have been fixed in 4.15 (finally), but is still an issue
  in the 4.4 kernel used on our builders, and possibly others as well
  (needs investigation).

  The original Debian bug report linked has more info, as well as the
  patchset on lkml at https://lkml.org/lkml/2018/7/25/409

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

-- 
Mailing list: https://launchpad.net/~kernel-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: glibc needs an update for linux-5.2 kernel headers (alpha)

[Adam Conrad]

** Changed in: glibc (Ubuntu Eoan)
   Status: Triaged => Fix Released

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

Title:
  glibc needs an update for linux-5.2 kernel headers (alpha)

Status in glibc package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in glibc source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Fix Released

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 1838045] Update Released

[Adam Conrad]

The verification of the Stable Release Update for dkms has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Header check ignore --kernelsourcedir

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Xenial:
  Fix Released

Bug description:
  In Ubuntu 16.04/Xenial the dkms command (2.2.0.3-2ubuntu11.7) ignores
  the provided kernel source directory and then fails by not finding the
  headers.

  This was fixed upstream in 2.2.0.3-5 and landed in 18.04/Bionic.
  Proposing to backport the additional line of code into Xenial.

  +[ ! -z "$ksourcedir_fromcli" ] && DIR=$kernel_source_dir

  Testcase:
  Trying to compile any DKMS module with kernel source (headers) in a 
non-standard location (/usr/src) will fail with an error reporting missing 
headers without the change, even using --kernelsourcedir. With the patch 
applied, this works.

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

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

[Kernel-packages] [Bug 1834451] Re: glibc 2.23-0ubuntu11 ADT test failure with linux 4.4.0-154.181

[Adam Conrad]

Historically, this test had a timeout of 5s.  In more modern glibcs, it
uses the default of 20s.  It's probably reasonable when SRUing or doing
security updates to bump up that timeout.

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

Title:
  glibc 2.23-0ubuntu11 ADT test failure with linux 4.4.0-154.181

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

Bug description:
  Testing failed on:
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/g/glibc/20190625_182524_dae44@/log.gz

  Testcase nptl/tst-cond25 has been flaky on arm64.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Adam Conrad]

Confirmed in production as well, eoan's glibc now builds again on x86.

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

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 1829737] Update Released

[Adam Conrad]

The verification of the Stable Release Update for linux-firmware has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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 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 1831833] Update Released

[Adam Conrad]

The verification of the Stable Release Update for linux-firmware has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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 Released
Status in linux-firmware source package in Cosmic:
  Fix Released

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 1828133] Update Released

[Adam Conrad]

The verification of the Stable Release Update for linux-firmware has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Intel CyclonePeak wifi firmware

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

Bug description:
  [Impact]
  New Intel CyclonePeak Wifi cards require new firmware to enable.

  [Fix]
  To update the firmware we want only, backport the following 2 commits from 
iwlwifi tree for-upstream branch[1], and remove all 9000 series related 
firmwares.
     95a93535 iwlwifi: update -46 firmwares for 22260 and 9000 series
     68040ceb iwlwifi: add firmware for 22260 and update 9000 series -46 
firmwares

  1. git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-
  firmware.git

  [Test Case]
  Verified on AX200NGW & 22560NGW chips & Killer 1653 card, wifi works well.

  [Regression Risk]
  Low. This firmware is for new cards and new ABI, it won't affect current 
Intel wifi cards, and won't take effect on Bionic(4.15) kernel. Only iwlwifi 
DKMS driver or oem-osp1 kernel loads this firmware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1828133/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-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] Update Released

[Adam Conrad]

The verification of the Stable Release Update for linux-firmware has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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:
  Fix Committed
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux-firmware source package in Cosmic:
  Fix Released
Status in linux-oem-osp1 source package in Cosmic:
  Fix Committed
Status in linux-firmware source package in Disco:
  Fix Committed
Status in linux-oem-osp1 source package in Disco:
  Fix Committed
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] Update Released

[Adam Conrad]

The verification of the Stable Release Update for linux-firmware has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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 Released
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-firmware source package in Cosmic:
  Fix Released
Status in linux-firmware source package in Disco:
  Fix Committed
Status in linux-firmware source package in Eoan:
  Fix Released

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 1830890] Re: glibc 2.23-0ubuntu11 ADT test failure with linux 4.4.0-149.175

[Adam Conrad]

glibc in eoan building against the supposedly-fixed kernel is hitting
these issues again on i386 testsuites.  Did we break it again?

https://launchpad.net/ubuntu/+source/glibc/2.29-0ubuntu3

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

Title:
  glibc 2.23-0ubuntu11 ADT test failure with linux 4.4.0-149.175

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in glibc source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Some glibc testcases are regressing on i386 after the following commit was 
applied to xenial/linux as part of upstream stable update 4.4.179:

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

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

  which accidentally broke unwinding from userspace, because ld would
  strip the .eh_frame sections when linking.

  Test logs:
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/g/glibc/20190528_085308_d03ca@/log.gz

  [Fix]
  The following commit fixes the issue:

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

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

  It was applied to 4.4.180, but we need to apply it before otherwise
  xenial/linux will be released with a regression.

  [Test]
  ADT tests for glibc.

  [Regression Potential]
  Low. One line patch to Makefile which fixes a known regression.

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

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

[Kernel-packages] [Bug 1817518] Please test proposed package

[Adam Conrad]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into disco-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.178.1 in a few hours, and then in the -proposed repository.

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

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

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

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

-- 
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 OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
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

[Kernel-packages] [Bug 1817518] Please test proposed package

[Adam Conrad]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.175.4 in a few hours, and then in the -proposed repository.

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

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

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

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

-- 
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 OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
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

[Kernel-packages] [Bug 1817518] Please test proposed package

[Adam Conrad]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.173.6 in a few hours, and then in the -proposed repository.

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

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

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

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

-- 
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 OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
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

[Kernel-packages] [Bug 1824819] Re: linux: 5.0.0-13.14 -proposed tracker

[Adam Conrad]

** Tags removed: block-proposed block-proposed-disco

-- 
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:
  Incomplete
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  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 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: Promote to Proposed
  phase-changed: Monday, 15. April 2019 23:33 UTC
  reason:
automated-testing: Stalled -- testing FAILED
promote-to-proposed: Stalled -- packages are in the wrong component
regression-testing: Ongoing -- testing in progress

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 1824546] Re: Intel N3060 booting into black screen with 5.0 kernel

[Adam Conrad]

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

** This bug has been marked a duplicate of bug 1821820
   Cannot boot or install - have to use nomodeset

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

Title:
  Intel N3060 booting into black screen with 5.0 kernel

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  I updated xubuntu 19.04 to the new 5.0 kernel and it no longer boots,
  staying on a black screen with stable cursor.  I can however select
  4.18 kernel from grub and it boots perfectly.

  I am using Intel Celeron N3060 CPU.

  Please find attached the dmesg output.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1085 F pulseaudio
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=6dc53e52-37f1-4a3c-aef7-5dedb4684c69
  InstallationDate: Installed on 2016-08-27 (957 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160824)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 064e:9404 Suyin Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire one 1-431
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=25f4f2d4-2c0a-4661-bfde-bee6253caff5 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.178
  Tags:  disco
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-03-16 (27 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/28/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Oxford
  dmi.board.vendor: Acer
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd12/28/2015:svnAcer:pnAspireone1-431:pvrV1.10:rvnAcer:rnOxford:rvrV1.10:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: BSW
  dmi.product.name: Aspire one 1-431
  dmi.product.sku: AO1-431_106D_1.10
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1795857] Re: enable CONFIG_DRM_BOCHS

[Adam Conrad]

What was the host system (ie: what version of qemu)?  I want to be sure
this works going back as far as we support (so, trusty hosts).

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

Title:
  enable CONFIG_DRM_BOCHS

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

Bug description:
  CONFIG_DRM_BOCHS got disabled for
  https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648

  but doing so regressed running qemu with the 'std' VGA driver, where
  it'd fail to start X after install, as mentioned on bug 1794280

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

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

[Kernel-packages] [Bug 1795857] Re: enable CONFIG_DRM_BOCHS

[Adam Conrad]

I'm rejecting the kmod upload in the disco queue until the above comment
is addressed, so we don't get into a revert war.

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

Title:
  enable CONFIG_DRM_BOCHS

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

Bug description:
  CONFIG_DRM_BOCHS got disabled for
  https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648

  but doing so regressed running qemu with the 'std' VGA driver, where
  it'd fail to start X after install, as mentioned on bug 1794280

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

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

[Kernel-packages] [Bug 1795857] Re: enable CONFIG_DRM_BOCHS

[Adam Conrad]

The original bug report was on PowerKVM (ppc64el qemu).  In testing that
it was okay to revert this wholesale in both kmod and kernel, did anyone
test POWER?

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

Title:
  enable CONFIG_DRM_BOCHS

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

Bug description:
  CONFIG_DRM_BOCHS got disabled for
  https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648

  but doing so regressed running qemu with the 'std' VGA driver, where
  it'd fail to start X after install, as mentioned on bug 1794280

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

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

[Kernel-packages] [Bug 1802689] Update Released

[Adam Conrad]

The verification of the Stable Release Update for kmod has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on
  boot

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in kmod source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Incomplete
Status in kmod source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Incomplete
Status in kmod source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Incomplete

Bug description:
  After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it
  hangs on boot.

  After blacklisting i2c_i801 everything works great again.

  I realize that this was a fix for bug 1786574, and that helps some
  other folks out.  I'm not sure what the right fix is but there's got
  to be something that works for everyone.

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

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

[Kernel-packages] [Bug 1648873] Re: Ubuntu 16.10 netboot install fails with "Oops: Exception in kernel mode, sig: 5 [#1] " (lpfc)

[Adam Conrad]

** Changed in: debian-installer (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: debian-installer (Ubuntu Yakkety)
   Status: New => Fix Released

** Changed in: debian-installer (Ubuntu)
   Status: New => Fix Released

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

Title:
  Ubuntu 16.10 netboot install fails with "Oops: Exception in kernel
  mode, sig: 5 [#1] " (lpfc)

Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in debian-installer source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  == Comment: #33 - Mauricio Faria De Oliveira - 2016-12-09 06:49:57 ==

  Hi Canonical,

  Can you please apply this patch [1] to 16.10 and 16.04.x HWE (4.8) ?
  It's fixes a regression introduced in 4.8.

  As you can see, it's in the SCSI maintainer (James Bottomley)'s
  'fixes' branch, but didn't make 4.9-rc8 (maybe he considered it late
  for this one).

  We have installer, boot, and post-boot problems due to this one.
  It'd be good if the netboot images for 16.04.x HWE kernel can get it too.

  Thank you,

  [1] scsi: lpfc: fix oops/BUG in lpfc_sli_ringtxcmpl_put() 
  
http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=fixes=2319f847a8910cff1d46c9b66aa1dd7cc3e836a9

  Historical context:

  == Comment: #0 - HARSHA THYAGARAJA - 2016-11-21 02:39:35 ==
  ---Problem Description---
  Ubuntu 16.10 netboot install fails with "Oops: Exception in kernel mode. " 
(kernel: 4.8.0-27)
   
  Machine Type = Power8 baremetal  
   
  ---boot type---
  QEMU direct boot kernel/initrd
   
  ---Kernel cmdline used to launch install---
  On a Power8 server,  Using kernel and initrd images, 

  netcfg/disable_dhcp=true netcfg/confirm_static=true 
netcfg/choose_interface=98:BE:94:00:4C:68 netcfg/get_ipaddress=9.47.67.159/20 
netcfg/get_gateway=9.47.79.254 netcfg/get_nameservers=
   
  ---Install repository type---
  Internet repository
   
  ---Install repository Location---
  
http://ports.ubuntu.com/ubuntu-ports/dists/yakkety/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/
   
  ---Point of failure---
  Other failure during installation (stage 1)

  == Comment: #1 - HARSHA THYAGARAJA - 2016-11-21 02:41:54 ==
  The netboot install fails and Call traces are seen at the Disk detection step.

  == Comment: #8 - Mauricio Faria De Oliveira - 2016-11-21 15:58:25 ==
  Finally got it.

  The assembly offset/code + the trap signal is due to this BUG_ON(),
  and the second condition triggered the trap.

  Checking why piocb is not NULL but piocb->vport is NULL.
  This might have happened in the lpfc_linkdown_port() path, in the stack trace.

  Would need a more readable console log (ie, dmesg, as requested in
  comments 5, 3) to help understanding it.

  --

  static int
  lpfc_sli_ringtxcmpl_put(struct lpfc_hba *phba, struct lpfc_sli_ring *pring,
  struct lpfc_iocbq *piocb)
  {
  lockdep_assert_held(>hbalock);

  BUG_ON(!piocb || !piocb->vport);
  <...>
  }

  [  226.147886] NIP [db7324c0]
  lpfc_sli_ringtxcmpl_put+0x48/0x120 [lpfc]

  0x2478 + 0x48 = 0x24c0 (tdnei; trap doubleword not equal immediate)

  2478 :
  <...>
  2498:   78 2b bf 7c mr  r31,r5 // r31 is *piocb (r5 is the 
3rd function parameter)
  249c:   78 1b 7d 7c mr  r29,r3
  24a0:   78 23 9e 7c mr  r30,r4
  24a4:   01 00 00 48 bl  24a4  
// probably converted at module load time to the call lockdep_assert_held()
  24a8:   00 00 00 60 nop
  24ac:   00 00 bf 2f cmpdi   cr7,r31,0 // compare piocb with 0. 
checking for NULL.
  24b0:   70 00 9e 41 beq cr7,2520 
 // if equal to zero, branch out. done w/ the  
former part of the OR check.
  24b4:   e8 00 3f e9 ld  r9,232(r31) // an offset of piocb. 
probably piocb->vport in the bug_on
  24b8:   74 00 29 7d cntlzd  r9,r9 // count leading zeroes. if r59 
is null (0), leading zeroes is 64 (binary: 0100_, bit 6 is 1, and 6 LSbs 
[bits 5-0] are 0)
  24bc:   82 d1 29 79 rldicl  r9,r9,58,6 // rotate left 58 (ie, 
those 6 LSbs are now MSbs, and that bit 6 from 64 was rotated in the register 
and is now bit 0, the LSb), now AND the 6 MSbs w/ 0-bits, and the all lower 
bits with 1-bits (ie, save the LSb). 
  24c0:   00 00 09 0b tdnei   r9,0 // trap if not equal to zero. 
(ie, the whole r9 was zero, with 64 leading/consecutive zeroes, then bit 6 is 
1, it becomes bit 0.. and since bit 0 is now 1, r9 is thus non-zero, and the 
trap triggers.)this checked the latter part of the OR.

To manage 

[Kernel-packages] [Bug 1815579] Update Released

[Adam Conrad]

The verification of the Stable Release Update for nvidia-graphics-
drivers-340 has completed successfully and the package has now been
released to -updates.  Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report.  In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update so we can easily find any regressions.

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

Title:
  Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04
  in bionic

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released

Bug description:
  I am trying to test new HWE stack from 18.10 in my destkop Ubuntu
  18.04.1 (expected release 18.04.2 this week) and I have broken
  dependencies when installing `xserver-xorg-hwe-18.04` package with
  NVidia drivers:

  me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 
xserver-xorg-video-nvidia-390 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  xserver-xorg-video-nvidia-390 is already the newest version 
(390.77-0ubuntu0.18.04.1).
  xserver-xorg-video-nvidia-390 set to manually installed.
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   xserver-xorg-hwe-18.04 : Depends: xserver-xorg-core-hwe-18.04 (>= 
2:1.17.2-2) but it is not going to be installed
Conflicts: xserver-xorg-core (>= 0~)
Recommends: xserver-xorg-video-all-hwe-18.04 but it 
is not going to be installed
  E: Unable to correct problems, you have held broken packages.

  
  Otherwise, if I try to install it without `xserver-xorg-video-nvidia-390` 
this happens:

  me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 
libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 
libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386
libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 
libllvm7:i386 libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 
libnvidia-compute-390:i386 libnvidia-decode-390
libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 
libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 
libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386
libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libvdpau1 
libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 
libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386
libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 
libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 
libxshmfence1:i386 libxxf86vm1:i386 mesa-vdpau-drivers
nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-common-390 
nvidia-kernel-source-390 nvidia-prime nvidia-settings nvidia-utils-390 
pkg-config screen-resolution-extra vdpau-driver-all
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
xserver-xorg-core-hwe-18.04 xserver-xorg-input-all-hwe-18.04 
xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 
xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04
xserver-xorg-video-fbdev-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 
xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-qxl-hwe-18.04 
xserver-xorg-video-radeon-hwe-18.04
xserver-xorg-video-vesa-hwe-18.04 xserver-xorg-video-vmware-hwe-18.04
  Suggested packages:
xfonts-100dpi | xfonts-75dpi firmware-amd-graphics xserver-xorg-video-r128 
xserver-xorg-video-mach64 firmware-misc-nonfree
  Recommended packages:
xserver-xorg-input-wacom-hwe-18.04
  The following packages will be REMOVED:
nvidia-driver-390 xserver-xorg xserver-xorg-core xserver-xorg-input-all 
xserver-xorg-input-libinput xserver-xorg-video-nvidia-390
  The following NEW packages will be installed:
xserver-xorg-core-hwe-18.04 xserver-xorg-hwe-18.04 
xserver-xorg-input-all-hwe-18.04 

[Kernel-packages] [Bug 1789924] Please test proposed package

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/18.2.8-0ubuntu0~18.04.2 in a
few hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server source package in Bionic:
  Fix Released
Status in libdrm source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in mesa source package in Cosmic:
  Fix Committed
Status in xorg-server source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems.

  [Regression potential]
  none, these just add pci-id's and platform definitions

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

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

[Kernel-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

[Adam Conrad]

Hello Alkis, or anyone else affected,

Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/18.2.8-0ubuntu0~18.04.2 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: mesa (Ubuntu Bionic)
   Status: Fix Released => Fix Committed

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

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions

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

[Kernel-packages] [Bug 1815172] Update Released

[Adam Conrad]

The verification of the Stable Release Update for mesa has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions

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

[Kernel-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted mesa into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/18.2.8-0ubuntu0~18.10.2 in a
few hours, and then in the -proposed repository.

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

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

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

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

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

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

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server source package in Bionic:
  Fix Released
Status in libdrm source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in mesa source package in Cosmic:
  Fix Committed
Status in xorg-server source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems.

  [Regression potential]
  none, these just add pci-id's and platform definitions

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

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

[Kernel-packages] [Bug 1815172] Please test proposed package

[Adam Conrad]

Hello Alkis, or anyone else affected,

Accepted mesa into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/18.2.8-0ubuntu0~18.10.2 in a
few hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions

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

[Kernel-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

[Adam Conrad]

Hello Alkis, or anyone else affected,

Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/18.2.2-0ubuntu1~18.04.2 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: mesa (Ubuntu Bionic)
   Status: New => Fix Committed

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

** Changed in: mesa (Ubuntu Cosmic)
   Status: New => Fix Committed

** Tags added: verification-needed-cosmic

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions

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

[Kernel-packages] [Bug 1802135] Update Released

[Adam Conrad]

The verification of the Stable Release Update for kmod has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  broken touchpad after i2c-i801 blacklist change

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in kmod source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Invalid
Status in kmod source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in kmod source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  SRU:
  

  [Impact]
  ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801.
  PNP LEN0049 will use smbus by default in kernel, but i2c bus is in
  runtime suspend mode in old touchpad fw.
  Then touchpad will not work.
  LEN2040 on 11e 3rd can reproduce this issue by passing
  psmouse.synaptics_intertouch=1

  These 2 pnp device should be the same one Synaptics s3203_ver5.

  [Fix]
  i2c-i801 should auto suspend when not used, no need runtime pm.

  [Test Case]
  Tested on Thinkpad 11e 3rd.
  Touchpad works fine.

  [Regression Potential]
  Low, upstream fix cherry-picked.

  4.18 kernel patch, no need for cosmic.

  
  Original bug report:
  =
  After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 
11e 2nd gen machines.

  We have a fleet of approximetly 1000 of them in production running
  ubuntu 18.04. Prior to this update the trackpads worked out of box in
  18.04.

  We are currently working around the issue by deploying our own
  blacklist files.

  Here is a link to the SRU justification: https://bugs.launchpad.net
  /hwe-next/+bug/1786574

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

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

[Kernel-packages] [Bug 1803360] Update Released

[Adam Conrad]

The verification of the Stable Release Update for thermald has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Xenial:
  Won't Fix
Status in thermald source package in Bionic:
  Fix Released
Status in thermald source package in Cosmic:
  Fix Committed
Status in thermald source package in Disco:
  Fix Released

Bug description:
  == SRU Justification, Cosmic, Bionic, Xenial ==

  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

  == Fix ==
   
  Upstream fix 
https://github.com/intel/thermal_daemon/commit/97976782dd26b4d592ccb97eb89c2a3a871a22a9

  == Testing ==

  Exercise CPUs on a fanless INT340X device with _CRT ACPI objects and
  try and reach the trip point. Without the fix thermal overrun occurs
  and this trips CPU shutdown. With the fix, thermald will start to
  throttle the system and get it out of the thermal overrun zone.

  == Regression Potential ==

  This modifies the behavior for just INT340X devices with ACPI _CRT
  objects, specifically, now to honor this setting.  This is a small
  subset of devices with these objects and the change will in face make
  thermald catch systems before they hit thermal overrun, so the risk of
  regression is small. This fix also has been reviewed by the thermal
  experts at Intel, so it seems like a very reasonable workaround for
  these specific use cases.

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

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

[Kernel-packages] [Bug 1771823] Re: Please include ax88179_178a and r8152 modules in d-i udeb

[Adam Conrad]

** Changed in: debian-installer (Ubuntu)
   Status: New => Fix Released

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

Title:
  Please include ax88179_178a and r8152 modules in d-i udeb

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

Bug description:
  
  == SRU Justification ==
  The r8152 module is used in a thunderbolt-connected docking station and
  ax88179_178a by an external USB dongle.

  Despite having two nics connected the bug reporter can't install
  Bionic.

  This SRU request is to add the modules to the debian installer.

  == Fix ==
  UBUNTU: [Config:] d-i: Add ax88179_178a and r8152 to nic-modules

  == Regression Potential ==
  Low.  This is adding a module to the installer.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.





  r8152 is used in a thunderbolt-connected docking station and
  ax88179_178a by an external USB dongle.

  Despite having two nics connected i can't install Bionic. :-)

  This is probably a subset of the modules to be included when fixing
  LP: #1503218.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1771823/+subscriptions

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

[Kernel-packages] [Bug 1808528] Re: Update linux-firmware in bionic for 18.10 hwe kernel

[Adam Conrad]

Hello Seth, or anyone else affected,

Accepted linux-firmware into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.173.3 in a few hours, and then in the -proposed repository.

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

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

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

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

** Description changed:

  SRU Justification
  
  Impact: A 4.18-based hwe kernel has been introduced into bionic. However
  some of the firmware files it requires are missing from bionic's linux-
  firmware, rendering the relevant hardware inoperable.
  
  Fix: Add the missing firmware files.
  
  Regression Potential: Most of these files will not be used by the
- existing kernels in xenial. A few may be, and while regressions are not
+ existing kernels in bionic. A few may be, and while regressions are not
  expected it's possible that new firmware versions might introduce
  regressions.

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

Title:
  Update linux-firmware in bionic for 18.10 hwe kernel

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

Bug description:
  SRU Justification

  Impact: A 4.18-based hwe kernel has been introduced into bionic.
  However some of the firmware files it requires are missing from
  bionic's linux-firmware, rendering the relevant hardware inoperable.

  Fix: Add the missing firmware files.

  Regression Potential: Most of these files will not be used by the
  existing kernels in bionic. A few may be, and while regressions are
  not expected it's possible that new firmware versions might introduce
  regressions.

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

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

[Kernel-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/18.2.2-0ubuntu1~18.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: mesa (Ubuntu Bionic)
   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/1789924

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server source package in Bionic:
  Fix Released
Status in libdrm source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in mesa source package in Cosmic:
  New
Status in xorg-server source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems.

  [Regression potential]
  none, these just add pci-id's and platform definitions

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

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

[Kernel-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted libdrm into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libdrm/2.4.95-1~18.04.1 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems.

  [Regression potential]
  none, these just add pci-id's and platform definitions

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

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

[Kernel-packages] [Bug 1792189] Re: linux-firmware does not depend on initramfs-tools

[Adam Conrad]

This isn't a bug in linux-firmware, it shouldn't depend on initramfs-
tools, but initrafms-tools shouldn't fail miserably when called in this
fashion either.

** Package changed: linux-firmware (Ubuntu) => initramfs-tools (Ubuntu)

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

Title:
  linux-firmware does not depend on initramfs-tools

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  In bug #1646197 the linux-firmware.postinst was added to call update-
  initramfs (provided by initramfs-tools.  If the initramfs-tools
  package is not installed the installation of linux-firmware will fail.

  Recreate:
  sudo apt-get purge --assume-yes '^linux-.*' 'linux-base+' initramfs*
  sudo apt-get install --assume-yes linux-generic

  Result:
  Setting up linux-modules-4.15.0-34-generic (4.15.0-34.37) ...
  Setting up linux-headers-4.15.0-34 (4.15.0-34.37) ...
  Setting up linux-headers-4.15.0-34-generic (4.15.0-34.37) ...
  Setting up initramfs-tools-bin (0.130ubuntu3.3) ...
  Setting up linux-firmware (1.173.1) ...
  update-initramfs: Generating /boot/initrd.img-4.15.0-1021-kvm
  /usr/sbin/mkinitramfs: 66: .: Can't open /etc/initramfs-tools/initramfs.conf
  update-initramfs: failed for /boot/initrd.img-4.15.0-1021-kvm with 2.
  dpkg: error processing package linux-firmware (--configure):
   installed linux-firmware package post-installation script subprocess 
returned error exit status 2
  ...
  Errors were encountered while processing:
   linux-firmware
   linux-image-generic
   linux-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Impact:
  Builds of minimized images start with an image that has the linux-kvm kernel 
but lack initramfs-tools.  Derivative builds that require a different kernel, 
linux-generic for example, will purge the existing kernel and install the 
correct kernel which could pull in linux-firmware and initramfs-tools.  In that 
case the builds fail unless initramfs-tools is installed prior to kernel 
installation as a workaround for this missing package dependency.

  This has been recreated on cosmic and bionic, a fix is desired on
  each.  (I was unable to recreate on Xenial but that package lacks the
  dependency as well).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1792189/+subscriptions

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

[Kernel-packages] [Bug 1772024] Update Released

[Adam Conrad]

The verification of the Stable Release Update for nbd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  linux 4.13.0-42.47 ADT test failure with linux 4.13.0-42.47 (nbd-
  smoke-test)

Status in linux package in Ubuntu:
  In Progress
Status in nbd package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  New
Status in nbd source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  New
Status in nbd source package in Xenial:
  Invalid
Status in linux source package in Artful:
  New
Status in nbd source package in Artful:
  Incomplete
Status in linux source package in Bionic:
  New
Status in nbd source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  In Progress
Status in nbd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  nbd-server will crash when a client connects to it, if it was started without 
a server name. It may also leak fds if fork fails.

  [Test Case]
  Running the server with an empty config file and an image on the command 
line, and then starting a local client will crash the server. After the fix, it 
doesn't crash anymore, and a filesystem may be created and used after that.

  [Regression Potential]
  The fix also implies a small package change, to use quilt. It has built just 
fine and many tests have been run on top of those packages and no failure 
seemed to be the result of those userspace changes, but known failures in the 
kernel driver.

  
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/l/linux/20180518_040741_b3b54@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/i386/l/linux/20180518_050911_b3b54@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/l/linux/20180518_040734_b3b54@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/s390x/l/linux/20180518_035527_b3b54@/log.gz

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

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

[Kernel-packages] [Bug 1781001] Update Released

[Adam Conrad]

The verification of the Stable Release Update for dkms has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  DKMS seems to hang after installing a module.

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  All users of third-party modules on Ubuntu when running under SecureBoot 
experience a package manager hang trying to initially configure the dkms 
package from the commandline.

  [Test cases]
  1) Install Ubuntu on an UEFI system
  2) Clear any files in /var/lib/shim-signed/mok: "sudo rm -rf 
/var/lib/shim-signed/mok/*"
  3) Install virtualbox-dkms: "sudo apt install virtualbox-dkms"
  4) Verify that you are prompted for a password to enroll a new MOK, and that 
you are asked that password at reboot.

  Without the patch, no prompt will appear at install of virtualbox-
  dkms.

  [Regression Potential]
  Shuffling of file descriptors as required by this change may impact dkms 
builds if these builds do special steps requiring different file descriptors. 
Any failure to install a -dkms package should be investigated as a potential 
regression coming from this SRU.

  

  (while gathering info for this bugreport, my knowledge about this
  issue has been growing. So the top part was written with not
  everything known yet)

  In my case I installed tp_smapi, but on the internet I've found others
  that have installed other modules.

  When configuring the tp-smapi-dkms package it says it will uninstall
  the module first and the it reports: Building initial module for
  4.15.0-23-generic

  After that it hangs, or so it seems. It turns out that somewhere in
  there a script is being called with output redirected to /dev/null.
  But under certain circumstances, in my case "the computer is
  configured for secure boot", whiptail is being called asking for a
  password.

  Whiptail outputs curses codes to write stuff to the screen but that is
  redirected to /dev/null. It then waits for input from the user. I've
  debugged this to the point that it is saying this:

   whiptail --backtitle Package configuration --title Configuring Secure
  Boot --output-fd 12 --nocancel --msgbox Your system has UEFI Secure
  Boot enabled.  UEFI Secure Boot requires additional configuration to
  work with  third-party drivers.  The system will assist you in
  configuring UEFI Secure Boot. To permit  the use of third-party
  drivers, a new Machine-Owner Key (MOK) has been  generated. This key
  now needs to be enrolled in your system's firmware.  To ensure that
  this change is being made by you as an authorized user,  and not by an
  attacker, you must choose a password now and then confirm  the change
  after reboot using the same password, in both the "Enroll  MOK" and
  "Change Secure Boot state" menus that will be presented to you  when
  this system reboots.  If you proceed but do not confirm the password
  upon reboot, Ubuntu will  still be able to boot on your system but any
  hardware that requires  third-party drivers to work correctly may not
  be usable. --scrolltext 20 77

  but, as I said the output is redirected to /dev/null.

  The call-tree is as follows:
  
-dpkg(18879)---tp-smapi-dkms.p(18880)---common.postinst(18881)---dkms(19146)---dkms(19161)---frontend(20224)-+-update-securebo(20238)
     |   |  

 `-whiptail(20253)

  (with the update-secureboot and whiptail both being children from "frontend". 
).
  The tp-smapi-dkms.postinst  program is still being called with stdout 
connected to my controlling terminal. The common.postinst has stdout connected 
ot /dev/null, so I'd first look in /var/lib/dpkg/info/tp-smapi-dkms.postinst
  I have looked there, and I don't see a reason why it would redirect the 
output of a subprocess to /dev/null. (the word does not occur in the short 
script.)
  Alternatively I'd think that maybe the subprocess 
/usr/lib/dkms/common.postinst would redirect its own stdout to /dev/null.

  On the other hand I found
    dkms build -m $NAME -v $VERSION -k $KERNEL $ARCH > /dev/null

  which explains the dkms subprocess running with output redirected to
  devnull, but not why the common.postinst runs with output redirected
  to devnull.

  Anyway. DKMS kernel module install postponed, apt  

[Kernel-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device

[Adam Conrad]

Hello bugproxy, or anyone else affected,

Accepted debian-installer into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/debian-
installer/20101020ubuntu543.1 in a few hours, and then in the -proposed
repository.

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

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

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

** Changed in: debian-installer (Ubuntu Bionic)
   Status: New => Fix Committed

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

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

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

Status in The Ubuntu-power-systems project:
  Triaged
Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Xenial:
  New
Status in linux source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  New
Status in debian-installer source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  == Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / 
MD RAID devices 

  Used 20101020ubuntu543 version to install
  
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdha...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  ===console error log===

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? /dev/nvme0n1 - 491.5 GB NVMe Device ?
? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  To make sure it detects the disks I had to 
  
  
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?  /dev/nvme0n1 - 491.5 GB NVMe Device?
?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
?  SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ  ?
?  

[Kernel-packages] [Bug 1782835] Re: d-i step "Configure the keyboard" fails

[Adam Conrad]

** Package changed: linux (Ubuntu) => console-setup (Ubuntu)

** Changed in: console-setup (Ubuntu)
   Importance: Critical => Undecided

** Changed in: console-setup (Ubuntu)
   Status: Incomplete => New

** Changed in: console-setup (Ubuntu)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: console-setup (Ubuntu)
   Status: New => Fix Committed

** Changed in: console-setup (Ubuntu Bionic)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: console-setup (Ubuntu Bionic)
   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/1782835

Title:
  d-i step "Configure the keyboard" fails

Status in console-setup package in Ubuntu:
  Fix Committed
Status in console-setup source package in Bionic:
  Fix Committed

Bug description:
  Testing a bionic build of d-i w/ proposed results in a failure.

  From d-i's /var/log/syslog:

  Jul 20 20:01:04 main-menu[897]: INFO: Menu item 'di-utils-shell' selected
  Jul 20 20:03:23 main-menu[897]: INFO: Menu item 'console-setup-udeb' selected
  Jul 20 20:03:25 main-menu[897]: (process:1567): 
/var/lib/dpkg/info/console-setup-udeb.postinst: line 52: dpkg-query: not found
  Jul 20 20:03:25 main-menu[897]: WARNING **: Configuring 'console-setup-udeb' 
failed with error code 127
  Jul 20 20:03:25 main-menu[897]: WARNING **: Menu item 'console-setup-udeb' 
failed.
  Jul 20 20:03:41 main-menu[897]: INFO: Menu item 'di-utils-shell' selected
  Jul 20 20:03:46 kernel: [  224.155631] random: crng init done

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1782835/+subscriptions

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

[Kernel-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device

[Adam Conrad]

** Changed in: systemd (Ubuntu)
   Status: New => Fix Committed

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

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

Status in The Ubuntu-power-systems project:
  Triaged
Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Xenial:
  New
Status in linux source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  New
Status in debian-installer source package in Bionic:
  New
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  == Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / 
MD RAID devices 

  Used 20101020ubuntu543 version to install
  
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdha...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  ===console error log===

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? /dev/nvme0n1 - 491.5 GB NVMe Device ?
? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  To make sure it detects the disks I had to 
  
  
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?  /dev/nvme0n1 - 491.5 GB NVMe Device?
?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
?  SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ  ?
? ?
??
? ?
???

  IPR had similar issue reported  #164932 and fixed with 4.15.0-20,
  looks installer need a fix for LSI (mpt3sas) devices too

  == Comment: #2 - SEETEENA THOUFEEK  - 2018-07-03 
02:01:47 ==
  164932 - refers LP1751813

  == Comment: #3 - SEETEENA THOUFEEK  - 2018-07-03 
02:02:51 ==
  Jul  2 08:49:52 anna-install: Installing mdadm-udeb
  Jul  2 08:49:52 disk-detect: No Intel/DDF RAID disks detected.
  Jul  2 08:49:52 anna-install: Installing dmraid-udeb
  Jul  2 08:49:52 disk-detect: No Serial ATA RAID disks detected
  Jul  2 08:49:53 check-missing-firmware: looking at dmesg again, restarting 
from \[  330.659712\]
  Jul  2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg 
accordingly
  Jul  2 08:49:53 check-missing-firmware: saving timestamp for a later use: 
  Jul  2 08:49:53 check-missing-firmware: /dev/.udev/firmware-missing does not 
exist, skipping
  Jul  2 08:49:53 

[Kernel-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device

[Adam Conrad]

I've uploaded a fixed systemd to cosmic and bionic for this (xenial will
follow when I sort out the best way to backport the fix).  dannf should
be in a position to test this once a new d-i is built using the new
udev-udeb.

** Also affects: debian-installer (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Also affects: debian-installer (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

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

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Adam Conrad (adconrad)

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Adam Conrad (adconrad)

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

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

Status in The Ubuntu-power-systems project:
  Triaged
Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New
Status in debian-installer source package in Xenial:
  New
Status in linux source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  New
Status in debian-installer source package in Bionic:
  New
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  New

Bug description:
  == Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / 
MD RAID devices 

  Used 20101020ubuntu543 version to install
  
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdha...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  ===console error log===

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? /dev/nvme0n1 - 491.5 GB NVMe Device ?
? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  To make sure it detects the disks I had to 
  
  
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?  /dev/nvme0n1 - 491.5 GB NVMe Device?
?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
?  SCSI3 (0,2,0) (sdc) - 2.0 TB

[Kernel-packages] [Bug 1778529] Re: linux-firmware: restore firmware files previously shipped with the kernel

[Adam Conrad]

root@stilson:~# dpkg -l linux-firmware | grep ^i
ii  linux-firmware  1.157.19   allFirmware for Linux kernel 
drivers
root@stilson:~# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic
W: Possible missing firmware /lib/firmware/tigon/tg3_tso5.bin for module tg3
W: Possible missing firmware /lib/firmware/tigon/tg3_tso.bin for module tg3
W: Possible missing firmware /lib/firmware/tigon/tg3.bin for module tg3
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
root@stilson:~# apt-get install linux-firmware
[...]
Unpacking linux-firmware (1.157.20) over (1.157.19) ...
Setting up linux-firmware (1.157.20) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
update-initramfs: Generating /boot/initrd.img-4.13.0-45-generic
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
root@stilson:~# 


** Tags added: verification-done-xenial

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

Title:
  linux-firmware: restore firmware files previously shipped with the
  kernel

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Committed

Bug description:
  == SRU Justification ==

  Impact: Prior to Linux 4.14 a number of firmware files were being
  shipped with the kernel source. The duplicate files in linux-firmware
  had been removed, but now they need to be restored for the 4.15 hwe
  kernel.

  Fix: Restore the missing firmware files.

  Test Case: Install the updated linux-firmware package and confirm the
  presence of the restored files.

  Regression Potential: This only adds new firmware files and thus is
  not likely to cause regressions with already working hardware.

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

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

[Kernel-packages] [Bug 1778529] Re: linux-firmware: restore firmware files previously shipped with the kernel

[Adam Conrad]

Hello Seth, or anyone else affected,

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

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

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

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

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

Title:
  linux-firmware: restore firmware files previously shipped with the
  kernel

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Committed

Bug description:
  == SRU Justification ==

  Impact: Prior to Linux 4.14 a number of firmware files were being
  shipped with the kernel source. The duplicate files in linux-firmware
  had been removed, but now they need to be restored for the 4.15 hwe
  kernel.

  Fix: Restore the missing firmware files.

  Test Case: Install the updated linux-firmware package and confirm the
  presence of the restored files.

  Regression Potential: This only adds new firmware files and thus is
  not likely to cause regressions with already working hardware.

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

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

[Kernel-packages] [Bug 1772787] Re: lspci command cannot work normally in ubuntu16.04.4 with 4.10.0-40 kernel

[Adam Conrad]

Linux 4.10.0-40 is wildly out of date.  The current HWE kernel on 16.04
is 4.13.0-43.  Do you still see issues if you upgrade?

** Package changed: debian-installer (Ubuntu) => linux (Ubuntu)

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

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

Title:
  lspci command cannot work normally in ubuntu16.04.4 with 4.10.0-40
  kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Execute lspci command in ubuntu 16.04.4 with kernel update
  (kernel:4.10.0-40-generic), but always prompt error that cannot open
  /sys/bus/pci/devices/0001:00:02.0/resource: no such file or directory.

  Execute lspci command in ubuntu 16.04.4 without kernel update
  (kernel:4.4.0-116-generic), issue not exist.

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

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

[Kernel-packages] [Bug 1766727] Re: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04

[Adam Conrad]

** Changed in: initramfs-tools (Ubuntu Xenial)
   Status: New => Invalid

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

Title:
  initramfs-tools exception during pm.DoInstall with  do-release-upgrade
  from 16.04 to 18.04

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Committed
Status in s390-tools package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  New
Status in s390-tools source package in Xenial:
  Fix Released
Status in ubuntu-release-upgrader source package in Xenial:
  Invalid
Status in initramfs-tools source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in s390-tools source package in Bionic:
  Fix Released
Status in ubuntu-release-upgrader source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Upgrades of linux-image-generic-hwe-16.04-edge will fail to configure because 
the post-update script for zipl will fail.

  [Test Case]
  Upgrade linux-image-generic-hwe-16.04-edge from xenial to xenial-proposed on 
s390x.

  [Regression]
  zipl update on s390x might fail, causing the system to be unbootable.

  
  

  Upgrading from 16.04 to 18.04 using 'do-release-upgrade -d' results
  in:

  Errors were encountered while processing:
   initramfs-tools
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  Could not install the upgrades

  The upgrade has aborted. Your system could be in an unusable state. A
  recovery will run now (dpkg --configure -a).

  ---

  Processing triggers for systemd (237-3ubuntu10) ...
  Processing triggers for initramfs-tools (0.130ubuntu3) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-121-generic
  Using config file '/etc/zipl.conf'
  Error: Ramdisk file '/boot/initrd.img' in section 'ubuntu': No such file or 
directory
  run-parts: /etc/initramfs/post-update.d//zz-zipl exited with return code 1
  dpkg: error processing package initramfs-tools (--configure):
   installed initramfs-tools package post-installation script subprocess 
returned error exit status 1
  Processing triggers for ca-certificates (20180409) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  done.
  Processing triggers for dictionaries-common (1.27.2) ...
  Processing triggers for linux-image-4.15.0-19-generic (4.15.0-19.20) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-4.15.0-19-generic
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasdb (0104).
  Done.
  /etc/kernel/postinst.d/zz-zipl:
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasdb (0104).
  Done.
  Processing triggers for sgml-base (1.29) ...
  Processing triggers for resolvconf (1.79ubuntu10) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Errors were encountered while processing:
   initramfs-tools
  Log ended: 2018-04-24  13:12:40
  ---
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: s390x
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-19-generic s390x
  UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago)
  UserGroups: adm cdrom cpacfstats dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1766727/+subscriptions

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

[Kernel-packages] [Bug 1766727] Update Released

[Adam Conrad]

The verification of the Stable Release Update for s390-tools has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  initramfs-tools exception during pm.DoInstall with  do-release-upgrade
  from 16.04 to 18.04

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Committed
Status in s390-tools package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  New
Status in s390-tools source package in Xenial:
  Fix Released
Status in ubuntu-release-upgrader source package in Xenial:
  Invalid
Status in initramfs-tools source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in s390-tools source package in Bionic:
  Fix Released
Status in ubuntu-release-upgrader source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Upgrades of linux-image-generic-hwe-16.04-edge will fail to configure because 
the post-update script for zipl will fail.

  [Test Case]
  Upgrade linux-image-generic-hwe-16.04-edge from xenial to xenial-proposed on 
s390x.

  [Regression]
  zipl update on s390x might fail, causing the system to be unbootable.

  
  

  Upgrading from 16.04 to 18.04 using 'do-release-upgrade -d' results
  in:

  Errors were encountered while processing:
   initramfs-tools
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  Could not install the upgrades

  The upgrade has aborted. Your system could be in an unusable state. A
  recovery will run now (dpkg --configure -a).

  ---

  Processing triggers for systemd (237-3ubuntu10) ...
  Processing triggers for initramfs-tools (0.130ubuntu3) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-121-generic
  Using config file '/etc/zipl.conf'
  Error: Ramdisk file '/boot/initrd.img' in section 'ubuntu': No such file or 
directory
  run-parts: /etc/initramfs/post-update.d//zz-zipl exited with return code 1
  dpkg: error processing package initramfs-tools (--configure):
   installed initramfs-tools package post-installation script subprocess 
returned error exit status 1
  Processing triggers for ca-certificates (20180409) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  done.
  Processing triggers for dictionaries-common (1.27.2) ...
  Processing triggers for linux-image-4.15.0-19-generic (4.15.0-19.20) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-4.15.0-19-generic
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasdb (0104).
  Done.
  /etc/kernel/postinst.d/zz-zipl:
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasdb (0104).
  Done.
  Processing triggers for sgml-base (1.29) ...
  Processing triggers for resolvconf (1.79ubuntu10) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Errors were encountered while processing:
   initramfs-tools
  Log ended: 2018-04-24  13:12:40
  ---
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: s390x
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-19-generic s390x
  UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago)
  UserGroups: adm cdrom cpacfstats dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1766727/+subscriptions

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

[Kernel-packages] [Bug 1707875] Re: [18.04] include support for Python bindings in "perf"

[Adam Conrad]

Python2 will not be maintained upstream past 2020, so a lack of python3
bindings certainly feels like a non-starter.  As for why the kernel team
decided to drop the python build-dep in 13.04, I'm not sure, and it's a
conversation worth having.

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

Title:
  [18.04] include support for Python bindings in "perf"

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == Comment: #0 - Paul A. Clarke  - 2017-07-26 09:59:57 ==
  ---Problem Description---
  Request to build python bindings support with perf.

  ---Steps to Reproduce---
   Ubuntu-17.04# perf script -g python
  Python scripting not supported.  Install libpython and rebuild perf to enable 
it.
  For example:
# apt-get install python-dev (ubuntu)
# yum install python-devel (Fedora)
etc.
   
  Userspace tool common name: perf 
   
  Userspace rpm: linux-tools-common 

  Userspace tool obtained from project website:  na

  == Comment: #2 - MAMATHA INAMDAR  - 2017-08-01 05:02:34 
==
  After installing libpython, downloaded ubuntu 17.04 linux source code and 
compiled perf tool then it works fine.

  # ./perf script  -g python 
  generated Python script: perf-script.py

  but when I run perf tool without rebuilding after installing libpython
  it shows an error

  # perf script  -g python 
  Python scripting not supported.  Install libpython and rebuild perf to enable 
it.
  For example:
# apt-get install python-dev (ubuntu)
# yum install python-devel (Fedora)
etc.
  root@p8wookie:/home/Mamatha/ubuntu/ubuntu-zesty/tools/perf# perf --version
  perf version 4.10.17

  == Comment: #3 - MAMATHA INAMDAR  - 2017-08-01 05:03:44 
==
  Request to build python bindings support with perf.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1707875/+subscriptions

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

[Kernel-packages] [Bug 1766727] Re: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04

[Adam Conrad]

** Also affects: s390-tools (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

Title:
  initramfs-tools exception during pm.DoInstall with  do-release-upgrade
  from 16.04 to 18.04

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in s390-tools package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid

Bug description:
  Upgrading from 16.04 to 18.04 using 'do-release-upgrade -d' results
  in:

  Errors were encountered while processing:
   initramfs-tools
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  Could not install the upgrades

  The upgrade has aborted. Your system could be in an unusable state. A
  recovery will run now (dpkg --configure -a).

  ---

  Processing triggers for systemd (237-3ubuntu10) ...
  Processing triggers for initramfs-tools (0.130ubuntu3) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-121-generic
  Using config file '/etc/zipl.conf'
  Error: Ramdisk file '/boot/initrd.img' in section 'ubuntu': No such file or 
directory
  run-parts: /etc/initramfs/post-update.d//zz-zipl exited with return code 1
  dpkg: error processing package initramfs-tools (--configure):
   installed initramfs-tools package post-installation script subprocess 
returned error exit status 1
  Processing triggers for ca-certificates (20180409) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  done.
  Processing triggers for dictionaries-common (1.27.2) ...
  Processing triggers for linux-image-4.15.0-19-generic (4.15.0-19.20) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-4.15.0-19-generic
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasdb (0104).
  Done.
  /etc/kernel/postinst.d/zz-zipl:
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasdb (0104).
  Done.
  Processing triggers for sgml-base (1.29) ...
  Processing triggers for resolvconf (1.79ubuntu10) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Errors were encountered while processing:
   initramfs-tools
  Log ended: 2018-04-24  13:12:40
  --- 
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: s390x
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-19-generic s390x
  UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago)
  UserGroups: adm cdrom cpacfstats dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1766727/+subscriptions

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

[Kernel-packages] [Bug 1766629] [NEW] linux-image packages need to Break flash-kernel << 3.90ubuntu2

[Adam Conrad]

Public bug reported:

Due to the fact that we are no longer guaranteed to produce an initrd
from our postinst, flash-kernel can fail on upgrade when it attempts to
operate (incorrectly, because it's not smart) on the wrong kernel, and
fails to find the initrd we've not yet made.

This is worked around in flash-kernel 3.90ubuntu2, but all linux-image
packages need to Breaks on << that version to ensure upgrade ordering.

This should only apply to kernels which build on arm64 or armhf.

** Affects: linux (Ubuntu)
 Importance: Critical
 Status: 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/1766629

Title:
  linux-image packages need to Break flash-kernel << 3.90ubuntu2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Due to the fact that we are no longer guaranteed to produce an initrd
  from our postinst, flash-kernel can fail on upgrade when it attempts
  to operate (incorrectly, because it's not smart) on the wrong kernel,
  and fails to find the initrd we've not yet made.

  This is worked around in flash-kernel 3.90ubuntu2, but all linux-image
  packages need to Breaks on << that version to ensure upgrade ordering.

  This should only apply to kernels which build on arm64 or armhf.

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

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

[Kernel-packages] [Bug 1765083] [NEW] Please cherrypick s390 unwind fix

[Adam Conrad]

Public bug reported:

SRU Justification

Impact: On s390, an incorrect pointer being copied from the kernel to
userspace breaks stack unwinding.

Fix: One-line change from upstream. Only needed for 4.15+.

Test Case: The glibc testsuite contains test cases, which currently fail
with 4.15.

Regression Potential: Minimal as this is a small, obvious bug fix for a
single architecture.

---

As pointed out in the glibc bug[1], there's a kernel bug preventing
unwinding due to an incorrect pointer being copied to userspace.  A
1-line patch[2] has been committed to Linus's tree to fix this.

I investigated, and this only affects 4.15, so we only need this applied
to bionic.

[1] https://sourceware.org/bugzilla/show_bug.cgi?id=22916
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8b09ca746a643ca452cd41a522046a96ee5a55fd

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

Title:
  Please cherrypick s390 unwind fix

Status in linux package in Ubuntu:
  In Progress

Bug description:
  SRU Justification

  Impact: On s390, an incorrect pointer being copied from the kernel to
  userspace breaks stack unwinding.

  Fix: One-line change from upstream. Only needed for 4.15+.

  Test Case: The glibc testsuite contains test cases, which currently
  fail with 4.15.

  Regression Potential: Minimal as this is a small, obvious bug fix for
  a single architecture.

  ---

  As pointed out in the glibc bug[1], there's a kernel bug preventing
  unwinding due to an incorrect pointer being copied to userspace.  A
  1-line patch[2] has been committed to Linus's tree to fix this.

  I investigated, and this only affects 4.15, so we only need this
  applied to bionic.

  [1] https://sourceware.org/bugzilla/show_bug.cgi?id=22916
  [2] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8b09ca746a643ca452cd41a522046a96ee5a55fd

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

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

[Kernel-packages] [Bug 1761593] Re: Uninstall left nouveau blacklisted

[Adam Conrad]

This is very much a bug in nvidia-graphics-drivers-340.  One can debate
if software-properties should or shouldn't purge (though traditionally,
the argument was that silent frontends shouldn't purge because the user
hasn't explicitly asked for that), but if a removed package's unpurged
conffiles cause the system to misbehave, that package needs to be
rethought to avoid that situation.

** Package changed: nvidia-settings (Ubuntu) => nvidia-graphics-
drivers-340 (Ubuntu)

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Uninstall left nouveau blacklisted

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Following a successful install and subsequent use of nvidia-340 -
  uninstallation of nvidia via Additional Drivers led to a reboot to a
  desktop at 640x480 px.

  Investigation found an nvidia created file left on the system
  blacklisting nouveau, deleted file and rebooted to normal desktop.

  Didn't think about ubuntu-reporting this - can try and replicate and
  apport-collect if it's of any use.

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

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

[Kernel-packages] [Bug 1742998] Re: linux-aws: 4.4.0-1011.11 -proposed tracker

[Adam Conrad]

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad 
(adconrad)

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

Title:
  linux-aws: 4.4.0-1011.11 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1742995
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1742998/+subscriptions

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

[Kernel-packages] [Bug 1743001] Re: linux-aws: 4.4.0-1049.58 -proposed tracker

[Adam Conrad]

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad 
(adconrad)

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

Title:
  linux-aws: 4.4.0-1049.58 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1742995
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1743001/+subscriptions

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

[Kernel-packages] [Bug 1742995] Re: linux: 4.4.0-110.133 -proposed tracker

[Adam Conrad]

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad 
(adconrad)

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

Title:
  linux: 4.4.0-110.133 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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

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

  backports: 1742996,1742998
  derivatives: 1742999,1743000,1743001,1743002,1743004,1743006
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Saturday, 13. January 2018 02:21 UTC

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1742995/+subscriptions

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

[Kernel-packages] [Bug 1741920] Re: linux: 4.14.0-16.19 -proposed tracker

[Adam Conrad]

** Tags removed: block-proposed block-proposed-bionic

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

Title:
  linux: 4.14.0-16.19 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.14.0-16.19 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 --
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1741920/+subscriptions

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

[Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"

[Adam Conrad]

Note that if it *is* the same bug as #1713751, that reporter already
mentioned that using mainline kernels (and he was hitting this on 4.10)
fixed it for him, so it seems more plausible not that 4.14 has a fix,
but that Ubuntu's sauce has the breakage.  Of course, they may well not
be the same bug, cause the symptom itself is pretty generic.

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

Title:
  Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck
  for 22s! [systemd:1]"

Status in linux package in Ubuntu:
  Triaged
Status in qemu-kvm package in Ubuntu:
  New
Status in linux source package in Artful:
  Triaged
Status in qemu-kvm source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in qemu-kvm source package in Bionic:
  New

Bug description:
  This is impacting us for ubuntu autopkgtests. Eventually the whole
  region ends up dying because each worker is hit by this bug in turn
  and backs off until the next reset (6 hourly).

  17.10 (and bionic) guests are sometimes failing to reboot. When this
  happens, you see the following in the console

    [[0;32m  OK  [0m] Reached target Shutdown.
    [  191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
    [  219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
    [  226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
    [  226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
    [  226.706093] All QSes seen, last rcu_sched kthread activity 15002 
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
    [  226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346 
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0

  One host that exhibits this behaviour was:

    Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

  guest running:

    Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
  (Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
  (Ubuntu 4.13.0-16.19-generic 4.13.4)

  The affected cloud region is running the xenial/Ocata cloud archive,
  so the version of qemu-kvm in there may also be relevant.

  Here's how I reproduced it in lcy01:

    $ for n in {1..30}; do nova boot --flavor m1.small --image 
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name 
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n}; 
done
    $  sudo reboot
    # wait a minute or so for the instances to all reboot
    $ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n} 
| tail; done

  On bad instances you'll see the "soft lockup" message - on good it'll
  reboot as normal.

  We've seen good and bad instances on multiple compute hosts - it
  doesn't feel to me like a host problem but rather a race condition
  somewhere that's somehow either triggered or triggered much more often
  by what lcy01 is running. I always saw this on the first reboot -
  never on first boot, and never on n>1th boot. (But if it's a race then
  that might not mean much.)

  I'll attach a bad and a good console-log for reference.

  If you're at Canonical then see internal rt #107135 for some other
  details.

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

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

[Kernel-packages] [Bug 1694791] Re: Please remove libmpc from the sync blacklist

[Adam Conrad]

Unblacklisted and synced back to a current version.

** Changed in: libmpc (Ubuntu)
   Status: New => Fix Released

** Changed in: libmpc (Ubuntu)
 Assignee: (unassigned) => Adam Conrad (adconrad)

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

Title:
  Please remove libmpc from the sync blacklist

Status in libmpc package in Ubuntu:
  Fix Released

Bug description:
  
  I came across this package, wondering why Debian has a newer version which 
didn't seem to automatically sync in Artful. After some digging, I discovered 
that the package had been blacklisted [1] and thus prevented from syncing. 
Originally done because the binary packages provided were also offered by a 
different package libmpcdec (bug 540019). 

  However, I did some more digging and found that libmpcdec had been
  removed shortly after [2]. With this other package gone, I wonder if
  there is still reasons to keep libmpc in the blacklist or whether it
  could be synced to the latest version available in Debian?

  [1] http://people.canonical.com/~ubuntu-archive/sync-blacklist.txt
  [2] https://launchpad.net/ubuntu/+source/libmpcdec/+publishinghistory




  Please sync libmpc 2:0.1~r495-1 (universe) from Debian unstable (main)

  Changelog entries since current artful version 2:0.1~r459-4.1build1:

  libmpc (2:0.1~r495-1) unstable; urgency=medium

    * Team upload.
    * New upstream release. (Closes: #837096)
    * debian/rules: Add get-orig-source target to fetch newer upstream
  snapshots.
    * debian/patches:
  - 02_link-libm.patch, 1001_missing_extern_kw.patch: Removed, included
    upstream.
  - 03_mpcchap.patch: Refreshed and fixed use of cue_parse_file.

   -- Sebastian Ramacher <sramac...@debian.org>  Mon, 12 Sep 2016
  20:34:33 +0200

  libmpc (2:0.1~r475-2) unstable; urgency=medium

    * Team upload.
    * Drop all DEB_AUTO_UPDATE_* stuff and use dh-autoreconf exclusively to fix
  FTBFS. (Closes: #816529)
    * Update Vcs fields.
    * Bump standards to 3.9.8.

   -- James Cowgill <jcowg...@debian.org>  Wed, 31 Aug 2016 21:16:41
  +0100

  libmpc (2:0.1~r475-1) unstable; urgency=medium

    * New upstream release:
  - Contains a minor API change of removing some enum values that
    are not used anywhere in Debian.
    * debian/patches/05_visibility.patch:
  - Minor build system fix to declare HAVE_VISIBILITY.

   -- Sebastian Dröge <sl...@debian.org>  Sat, 19 Sep 2015 20:59:38
  +0200

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

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

[Kernel-packages] [Bug 1625233] Re: linux: 4.8.0-12.13 -proposed tracker

[Adam Conrad]

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

** This bug is no longer a duplicate of bug 1625240
   linux: 4.8.0-11.12 -proposed tracker
** This bug has been marked a duplicate of bug 1630279
   linux: 4.8.0-21.23 -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/1625233

Title:
  linux: 4.8.0-12.13 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.8.0-12.13 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 --
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1625233/+subscriptions

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

[Kernel-packages] [Bug 1624460] Re: linux: 4.6.0-13.15 -proposed tracker

[Adam Conrad]

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

** This bug has been marked a duplicate of bug 1630279
   linux: 4.8.0-21.23 -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/1624460

Title:
  linux: 4.6.0-13.15 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  New
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Invalid

Bug description:
  This bug is for tracking the 4.6.0-13.15 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1624460/+subscriptions

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

[Kernel-packages] [Bug 1624195] Re: linux: 4.6.0-13.15 -proposed tracker

[Adam Conrad]

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

** This bug is no longer a duplicate of bug 1624198
   linux: 4.6.0-13.15 -proposed tracker
** This bug has been marked a duplicate of bug 1630279
   linux: 4.8.0-21.23 -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/1624195

Title:
  linux: 4.6.0-13.15 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.6.0-13.15 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

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

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

[Kernel-packages] [Bug 1624198] Re: linux: 4.6.0-13.15 -proposed tracker

[Adam Conrad]

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

** This bug has been marked a duplicate of bug 1630279
   linux: 4.8.0-21.23 -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/1624198

Title:
  linux: 4.6.0-13.15 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Invalid

Bug description:
  This bug is for tracking the 4.6.0-13.15 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

  kernel-phase-changed:Friday, 16. September 2016 04:30 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1624198/+subscriptions

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

[Kernel-packages] [Bug 1624196] Re: linux: 4.6.0-13.15 -proposed tracker

[Adam Conrad]

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

** This bug is no longer a duplicate of bug 1624198
   linux: 4.6.0-13.15 -proposed tracker
** This bug has been marked a duplicate of bug 1630279
   linux: 4.8.0-21.23 -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/1624196

Title:
  linux: 4.6.0-13.15 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.6.0-13.15 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

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

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

[Kernel-packages] [Bug 1624454] Re: linux: 4.6.0-13.15 -proposed tracker

[Adam Conrad]

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

** This bug is no longer a duplicate of bug 1625240
   linux: 4.8.0-11.12 -proposed tracker
** This bug has been marked a duplicate of bug 1630279
   linux: 4.8.0-21.23 -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/1624454

Title:
  linux: 4.6.0-13.15 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.6.0-13.15 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

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

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

[Kernel-packages] [Bug 1626239] Re: linux: 4.8.0-15.16 -proposed tracker

[Adam Conrad]

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

** This bug has been marked a duplicate of bug 1630279
   linux: 4.8.0-21.23 -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/1626239

Title:
  linux: 4.8.0-15.16 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Confirmed
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  This bug is for tracking the 4.8.0-15.16 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 --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1626239/+subscriptions

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

[Kernel-packages] [Bug 1626768] Re: linux: 4.8.0-16.17 -proposed tracker

[Adam Conrad]

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

** This bug has been marked a duplicate of bug 1630279
   linux: 4.8.0-21.23 -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/1626768

Title:
  linux: 4.8.0-16.17 -proposed tracker

Status in Kernel Development Workflow:
  Fix Released
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  This bug is for tracking the 4.8.0-16.17 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 --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1626768/+subscriptions

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

[Kernel-packages] [Bug 1625733] Re: linux: 4.8.0-13.14 -proposed tracker

[Adam Conrad]

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

** This bug is no longer a duplicate of bug 1625240
   linux: 4.8.0-11.12 -proposed tracker
** This bug has been marked a duplicate of bug 1630279
   linux: 4.8.0-21.23 -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/1625733

Title:
  linux: 4.8.0-13.14 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.8.0-13.14 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

  kernel-phase:Packaging
  kernel-phase-changed:Tuesday, 20. September 2016 17:16 UTC

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1625733/+subscriptions

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

[Kernel-packages] [Bug 1626062] Re: linux: 4.8.0-14.15 -proposed tracker

[Adam Conrad]

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

** This bug has been marked a duplicate of bug 1630279
   linux: 4.8.0-21.23 -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/1626062

Title:
  linux: 4.8.0-14.15 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Won't Fix

Bug description:
  This bug is for tracking the 4.8.0-14.15 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 --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1626062/+subscriptions

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

[Kernel-packages] [Bug 1625240] Re: linux: 4.8.0-11.12 -proposed tracker

[Adam Conrad]

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

** This bug has been marked a duplicate of bug 1630279
   linux: 4.8.0-21.23 -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/1625240

Title:
  linux: 4.8.0-11.12 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Invalid

Bug description:
  This bug is for tracking the 4.8.0-11.12 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 --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1625240/+subscriptions

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

[Kernel-packages] [Bug 1627387] Re: linux: 4.8.0-17.19 -proposed tracker

[Adam Conrad]

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

** This bug has been marked a duplicate of bug 1630279
   linux: 4.8.0-21.23 -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/1627387

Title:
  linux: 4.8.0-17.19 -proposed tracker

Status in Kernel Development Workflow:
  Invalid
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Confirmed
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1627387/+subscriptions

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