date:20200107

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

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

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

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

Title:
  [sas-1126]scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset()

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04 series:
  In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
  In Progress
Status in kunpeng920 ubuntu-19.04 series:
  In Progress
Status in kunpeng920 ubuntu-19.10 series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Potential NULL-pointer dereference.

  [Test Case]
  No known test case, but the issue is clear from code reading.

  [Fix]
  445ee2de112a scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset()

  [Regression Risk]
  Patch restricted to hisi_sas driver.


  [Bug Description]
  sas kasan test will produce this out bounds in sas module

  [Steps to Reproduce]
  1) enbale this kasn
  2)
  3)

  [Actual Results]
  30293.504016] sas: ata464: end_device-2:2:6: dev error handler
  [30293.504041] sas: ata465: end_device-2:2:7: dev error handler
  [30293.504059] sas: ata466: end_device-2:2:8: dev error handler
  [30293.538746] 
==
  [30293.550672] BUG: KASAN: slab-out-of-bounds in 
hisi_sas_debug_I_T_nexus_reset+0xcc/0x250
  [30293.558642] Read of size 8 at addr b72e47233540 by task 
kworker/u193:3/79165
  [30293.566004]
  [30293.567498] CPU: 14 PID: 79165 Comm: kworker/u193:3 Tainted: GB  O 
 5.1.0-rc1-g7a3fab8-dirty #1
  [30293.577196] Hardware name: Huawei TaiShan 2280 V2/BC82AMDC, BIOS 2280-V2 
CS V3.B010.01 06/21/2019
  [30293.586037] Workqueue: events_unbound async_run_entry_fn
  [30293.591331] Call trace:
  [30293.593770]  dump_backtrace+0x0/0x1f8
  [30293.597419]  show_stack+0x14/0x20
  [30293.600726]  dump_stack+0xc4/0xfc
  [30293.604032]  print_address_description+0x60/0x258
  [30293.608716]  kasan_report+0x164/0x1b8
  [30293.612366]  __asan_load8+0x84/0xa8
  [30293.615842]  hisi_sas_debug_I_T_nexus_reset+0xcc/0x250
  [30293.620961]  hisi_sas_I_T_nexus_reset+0xc4/0x170
  [30293.625562]  sas_ata_hard_reset+0x88/0x178
  [30293.629646]  ata_do_reset.constprop.6+0x80/0x90
  [30293.634160]  ata_eh_reset+0x71c/0x10e8
  [30293.637897]  ata_eh_recover+0x3d0/0x1a80
  [30293.641804]  ata_do_eh+0x50/0xd0
  [30293.645020]  ata_std_error_handler+0x78/0xa8
  [30293.649273]  ata_scsi_port_error_handler+0x288/0x930
  [30293.654216]  async_sas_ata_eh+0x68/0x90
  [30293.658040]  async_run_entry_fn+0x7c/0x1c0
  [30293.662121]  process_one_work+0x3c0/0x878
  [30293.666115]  worker_thread+0x70/0x670
  [30293.669762]  kthread+0x1b0/0x1b8
  [30293.672978]  ret_from_fork+0x10/0x18
  [30293.676541]
  [30293.678027] Allocated by task 16690:
  [30293.681593]  __kasan_kmalloc.isra.0+0xd4/0x188
  [30293.686018]  kasan_kmalloc+0xc/0x18
  [30293.689496]  __kmalloc_node_track_caller+0x5c/0x98
  [30293.694270]  devm_kmalloc+0x44/0xb8
  [30293.697746]  hisi_sas_v3_probe+0x2ec/0x698
  [30293.701828]  local_pci_probe+0x74/0xf0
  [30293.705562]  work_for_cpu_fn+0x2c/0x48
  [30293.709300]  process_one_work+0x3c0/0x878
  [30293.713294]  worker_thread+0x400/0x670
  [30293.717027]  kthread+0x1b0/0x1b8
  [30293.720241]  ret_from_fork+0x10/0x18
  [30293.723801]
  [30293.725287] Freed by task 16227:
  [30293.728503]  __kasan_slab_free+0x108/0x210
  [30293.732583]  kasan_slab_free+0x10/0x18
  [30293.736318]  kfree+0x74/0x150
  [30293.739276]  devres_free+0x34/0x48
  [30293.742665]  devres_release+0x38/0x60
  [30293.746313]  devm_pinctrl_put+0x34/0x58
  [30293.750136]  pinctrl_bind_pins+0x164/0x248
  [30293.754214]  really_probe+0xc0/0x3b0
  [30293.75]  driver_probe_device+0x70/0x138
  [30293.761944]  __device_attach_driver+0xc0/0xe0
  [30293.766285]  bus_for_each_drv+0xcc/0x150
  [30293.770194]  __device_attach+0x154/0x1c0
  [30293.774101]  device_initial_probe+0x10/0x18
  [30293.778270]  bus_probe_device+0xec/0x100
  [30293.782178]  device_add+0x5f8/0x9b8
  [30293.785658]  scsi_sysfs_add_sdev+0xa4/0x310
  [30293.789825]  scsi_probe_and_add_lun+0xe60/0x1240
  [30293.794425]  __scsi_scan_target+0x1ac/0x780
  [30293.798591]  scsi_scan_target+0x134/0x140
  [30293.802586]  sas_rphy_add+0x1fc/0x2c8
  [30293.806234]  sas_probe_devices+0x10c/0x1e8
  [30293.810313]  sas_discover_domain+0x754/0x998
  [30293.814567]

[Kernel-packages] [Bug 1849269] Re: The system cannot resume from S3 if user unplugs the TB16 during suspend state

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

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

Title:
  The system cannot resume from S3 if user unplugs the TB16 during
  suspend state

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Unplug TBT dock during S3 and then wakes up the system leads to system hangs.
  This not only happens on Dell TB16, but also Dell WD19TB. It's more like a 
BIOS or TBT firmware issue that TBT firmware doesn't re-create the PCIe tunnels.

  [Fix]
  Mika provides 4 patches to fix this issue, but only 2 are accepted and are 
included in linus' tree. We need especially the 4th commit to fix the issue, so 
we keep the 3rd and 4th commits as sauce patches.

  [Test]
  Verified on Dell Precision 5530 + WD19TB

  [Regression Potential]
  Low, those patches doesn't change the code path much. The 4th commit adds 
some checks to return failure state, and it should be safe for those machines 
which is working well.

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

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

[Kernel-packages] [Bug 1858650] Re: package zfsutils-linux 0.8.1-1ubuntu14.2 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status

2020-01-07 Thread Colin Ian King

ZFS kernel modules are not supported for small memory ARM platforms such
as raspberry pi as it requires at least 4GB of memory to perform without
causing memory pressure issues.

** Changed in: zfs-linux (Ubuntu)
   Status: New => Won't Fix

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

Title:
  package zfsutils-linux 0.8.1-1ubuntu14.2 failed to install/upgrade:
  installed zfsutils-linux package post-installation script subprocess
  returned error exit status 1

Status in zfs-linux package in Ubuntu:
  Won't Fix

Bug description:
  cant install zfsutils-linux on headless nor desktop

  Jan 07 15:06:06 ubuntu zfs[3775]: The ZFS modules are not loaded.
  Jan 07 15:06:06 ubuntu zfs[3775]: Try running '/sbin/modprobe zfs' as root to 
lo
  ad them.
  Jan 07 15:06:06 ubuntu systemd[1]: zfs-mount.service: Main process exited, 
code=
  exited, status=1/FAILURE
  Jan 07 15:06:06 ubuntu systemd[1]: zfs-mount.service: Failed with result 
'exit-c
  ode'.
  Jan 07 15:06:06 ubuntu systemd[1]: Failed to start Mount ZFS filesystems.

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: zfsutils-linux 0.8.1-1ubuntu14.2
  ProcVersionSignature: Ubuntu 5.3.0-1015.17-raspi2 5.3.13
  Uname: Linux 5.3.0-1015-raspi2 aarch64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: arm64
  Date: Tue Jan  7 15:06:06 2020
  ErrorMessage: installed zfsutils-linux package post-installation script 
subprocess returned error exit status 1
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: zfs-linux
  Title: package zfsutils-linux 0.8.1-1ubuntu14.2 failed to install/upgrade: 
installed zfsutils-linux package post-installation script subprocess returned 
error exit status 1
  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/1858650/+subscriptions

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

[Kernel-packages] [Bug 1858650] [NEW] package zfsutils-linux 0.8.1-1ubuntu14.2 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit statu

2020-01-07 Thread Ben Houghton

Public bug reported:

cant install zfsutils-linux on headless nor desktop

Jan 07 15:06:06 ubuntu zfs[3775]: The ZFS modules are not loaded.
Jan 07 15:06:06 ubuntu zfs[3775]: Try running '/sbin/modprobe zfs' as root to lo
ad them.
Jan 07 15:06:06 ubuntu systemd[1]: zfs-mount.service: Main process exited, code=
exited, status=1/FAILURE
Jan 07 15:06:06 ubuntu systemd[1]: zfs-mount.service: Failed with result 'exit-c
ode'.
Jan 07 15:06:06 ubuntu systemd[1]: Failed to start Mount ZFS filesystems.

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: zfsutils-linux 0.8.1-1ubuntu14.2
ProcVersionSignature: Ubuntu 5.3.0-1015.17-raspi2 5.3.13
Uname: Linux 5.3.0-1015-raspi2 aarch64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: arm64
Date: Tue Jan  7 15:06:06 2020
ErrorMessage: installed zfsutils-linux package post-installation script 
subprocess returned error exit status 1
Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4
SourcePackage: zfs-linux
Title: package zfsutils-linux 0.8.1-1ubuntu14.2 failed to install/upgrade: 
installed zfsutils-linux package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package arm64 eoan uec-images

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

Title:
  package zfsutils-linux 0.8.1-1ubuntu14.2 failed to install/upgrade:
  installed zfsutils-linux package post-installation script subprocess
  returned error exit status 1

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  cant install zfsutils-linux on headless nor desktop

  Jan 07 15:06:06 ubuntu zfs[3775]: The ZFS modules are not loaded.
  Jan 07 15:06:06 ubuntu zfs[3775]: Try running '/sbin/modprobe zfs' as root to 
lo
  ad them.
  Jan 07 15:06:06 ubuntu systemd[1]: zfs-mount.service: Main process exited, 
code=
  exited, status=1/FAILURE
  Jan 07 15:06:06 ubuntu systemd[1]: zfs-mount.service: Failed with result 
'exit-c
  ode'.
  Jan 07 15:06:06 ubuntu systemd[1]: Failed to start Mount ZFS filesystems.

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: zfsutils-linux 0.8.1-1ubuntu14.2
  ProcVersionSignature: Ubuntu 5.3.0-1015.17-raspi2 5.3.13
  Uname: Linux 5.3.0-1015-raspi2 aarch64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: arm64
  Date: Tue Jan  7 15:06:06 2020
  ErrorMessage: installed zfsutils-linux package post-installation script 
subprocess returned error exit status 1
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: zfs-linux
  Title: package zfsutils-linux 0.8.1-1ubuntu14.2 failed to install/upgrade: 
installed zfsutils-linux package post-installation script subprocess returned 
error exit status 1
  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/1858650/+subscriptions

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

[Kernel-packages] [Bug 1848445] Re: [HP Pavilion 360 - 13-a200nt (ENERGY STAR)] Kernel parameter acpi_osi= required to boot

2020-01-07 Thread Bug Watch Updater

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

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

Title:
  [HP Pavilion 360 - 13-a200nt (ENERGY STAR)] Kernel parameter acpi_osi=
  required to boot

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  When booting my HP Pavilion 360 - 13-a200nt (ENERGY STAR), it stops
  with just a non-blinking white cursor on screen in the top left, and
  the Caps Lock doesn't respond when pressed.

  Previously on 4.x kernels, system would boot using acpi=off argument
  creating more problems.

  WORKAROUND: Boot with kernel parameter:
  acpi_osi=

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
   /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
   /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 10:02:44 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2341
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 13 x360 PC
  dmi.product.sku: L0B89EA#AB8
  dmi.product.version: 097712405F0410180
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1844245] Re: Integrate Intel SGX driver into linux-azure

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

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

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

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

Title:
   Integrate Intel SGX driver into linux-azure

Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux-azure source package in Bionic:
  Invalid
Status in linux source package in Disco:
  Fix Committed
Status in linux-azure source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux-azure source package in Eoan:
  Fix Committed

Bug description:
  Intel is still trying to upstream the SGX driver, but in the meantime
  it would be desirable to have it available on the linux-azure kernel.

  The following version relies only on Kbuild:

  https://github.com/haimc-intel/SGXDataCenterAttestationPrimitives
  inker-ph1

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

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

[Kernel-packages] [Bug 1846539]

The issue seems to be resolved in the current kernel supplied with Arch
Linux. I attached updated files to the report.

> uname -a
Linux pixie 5.4.7-arch1-1 #1 SMP PREEMPT Tue, 31 Dec 2019 17:20:16 + x86_64 
GNU/Linux

> cat /proc/version
Linux version 5.4.7-arch1-1 (linux@archlinux) (gcc version 9.2.0 (GCC)) #1 SMP 
PREEMPT Tue, 31 Dec 2019 17:20:16 +

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

Title:
  [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no
  longer works on Dell Venue 11 Pro 7140

Status in HWE Next:
  Confirmed
Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux-oem-osp1 source package in Eoan:
  Confirmed

Bug description:
  [Impact]
  With the current default kernel config, the SND_SOC_SOF_BROADWELL_SUPPORT
  is set to Y, then it will make the legacy intel soc driver fail, and
  moreover the current sof driver can't support broadwell well, as a
  result, many broadwell computers with I2S codec can't support sound anymore.

  [Fix]
  Intel submitted a patch, it will make those two kconfig options exclusive,
  and the legacy soc's option has higher priority, if both of them are
  enabled, sof's option will be disabled.

  [Test Case]
  Build the kernel and check the debian/build/$buidling_dir/.config,  the
  SND_SOC_SOF_BROADWELL_SUPPORT is disabled.

  [Regression Risk]
  Low, so far, the sof driver can't support broadwell machine well, so
  there is no machine use this driver yet.


  Hello!

  I noticed that since Linux 5.2rc2 audio playback no longer works on
  Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that
  happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel
  binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel-
  ppa/mainline/v5.2-rc2/

  To verify this assumption I tested two builds of Linux 5.3.1.
  1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/

  Audio playback doesn't work, dmesg:
  [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
  [4.480344] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14
  [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 
header 0x8700
  [   13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 
still running
  [   13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 
still running
  [   19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- 
ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff
  [   19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 
faile

  2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT.

  Audio playback works, dmesg:
  [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77,

[Kernel-packages] [Bug 1846539]

2020-01-07 Thread pierre-louis.bossart

FWIW there are still issues with the latest ALSA/ASoC code when using
bdw-rt5677 with the legacy BIOS, see
https://github.com/thesofproject/linux/pull/1659

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

Title:
  [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no
  longer works on Dell Venue 11 Pro 7140

Status in HWE Next:
  Confirmed
Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux-oem-osp1 source package in Eoan:
  Confirmed

Bug description:
  [Impact]
  With the current default kernel config, the SND_SOC_SOF_BROADWELL_SUPPORT
  is set to Y, then it will make the legacy intel soc driver fail, and
  moreover the current sof driver can't support broadwell well, as a
  result, many broadwell computers with I2S codec can't support sound anymore.

  [Fix]
  Intel submitted a patch, it will make those two kconfig options exclusive,
  and the legacy soc's option has higher priority, if both of them are
  enabled, sof's option will be disabled.

  [Test Case]
  Build the kernel and check the debian/build/$buidling_dir/.config,  the
  SND_SOC_SOF_BROADWELL_SUPPORT is disabled.

  [Regression Risk]
  Low, so far, the sof driver can't support broadwell machine well, so
  there is no machine use this driver yet.


  Hello!

  I noticed that since Linux 5.2rc2 audio playback no longer works on
  Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that
  happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel
  binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel-
  ppa/mainline/v5.2-rc2/

  To verify this assumption I tested two builds of Linux 5.3.1.
  1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/

  Audio playback doesn't work, dmesg:
  [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
  [4.480344] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14
  [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 
header 0x8700
  [   13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 
still running
  [   13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 
still running
  [   19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- 
ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff
  [   19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 
faile

  2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT.

  Audio playback works, dmesg:
  [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.907386] broadwell-audio

[Kernel-packages] [Bug 1846539]

Created attachment 286591
lspci -vvv (5.4.7-arch1-1)

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

Title:
  [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no
  longer works on Dell Venue 11 Pro 7140

Status in HWE Next:
  Confirmed
Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux-oem-osp1 source package in Eoan:
  Confirmed

Bug description:
  [Impact]
  With the current default kernel config, the SND_SOC_SOF_BROADWELL_SUPPORT
  is set to Y, then it will make the legacy intel soc driver fail, and
  moreover the current sof driver can't support broadwell well, as a
  result, many broadwell computers with I2S codec can't support sound anymore.

  [Fix]
  Intel submitted a patch, it will make those two kconfig options exclusive,
  and the legacy soc's option has higher priority, if both of them are
  enabled, sof's option will be disabled.

  [Test Case]
  Build the kernel and check the debian/build/$buidling_dir/.config,  the
  SND_SOC_SOF_BROADWELL_SUPPORT is disabled.

  [Regression Risk]
  Low, so far, the sof driver can't support broadwell machine well, so
  there is no machine use this driver yet.


  Hello!

  I noticed that since Linux 5.2rc2 audio playback no longer works on
  Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that
  happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel
  binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel-
  ppa/mainline/v5.2-rc2/

  To verify this assumption I tested two builds of Linux 5.3.1.
  1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/

  Audio playback doesn't work, dmesg:
  [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
  [4.480344] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14
  [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 
header 0x8700
  [   13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 
still running
  [   13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 
still running
  [   19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- 
ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff
  [   19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 
faile

  2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT.

  Audio playback works, dmesg:
  [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.907475] broadwell-audio broadwell-audio:

[Kernel-packages] [Bug 1846539]

Created attachment 286589
/proc/iomem (5.4.7-arch1-1)

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

Title:
  [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no
  longer works on Dell Venue 11 Pro 7140

Status in HWE Next:
  Confirmed
Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux-oem-osp1 source package in Eoan:
  Confirmed

Bug description:
  [Impact]
  With the current default kernel config, the SND_SOC_SOF_BROADWELL_SUPPORT
  is set to Y, then it will make the legacy intel soc driver fail, and
  moreover the current sof driver can't support broadwell well, as a
  result, many broadwell computers with I2S codec can't support sound anymore.

  [Fix]
  Intel submitted a patch, it will make those two kconfig options exclusive,
  and the legacy soc's option has higher priority, if both of them are
  enabled, sof's option will be disabled.

  [Test Case]
  Build the kernel and check the debian/build/$buidling_dir/.config,  the
  SND_SOC_SOF_BROADWELL_SUPPORT is disabled.

  [Regression Risk]
  Low, so far, the sof driver can't support broadwell machine well, so
  there is no machine use this driver yet.


  Hello!

  I noticed that since Linux 5.2rc2 audio playback no longer works on
  Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that
  happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel
  binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel-
  ppa/mainline/v5.2-rc2/

  To verify this assumption I tested two builds of Linux 5.3.1.
  1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/

  Audio playback doesn't work, dmesg:
  [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
  [4.480344] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14
  [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 
header 0x8700
  [   13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 
still running
  [   13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 
still running
  [   19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- 
ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff
  [   19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 
faile

  2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT.

  Audio playback works, dmesg:
  [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.907475] broadwell-audio

[Kernel-packages] [Bug 1846539]

Created attachment 286593
lsmod (5.4.7-arch1-1)

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

Title:
  [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no
  longer works on Dell Venue 11 Pro 7140

Status in HWE Next:
  Confirmed
Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux-oem-osp1 source package in Eoan:
  Confirmed

Bug description:
  [Impact]
  With the current default kernel config, the SND_SOC_SOF_BROADWELL_SUPPORT
  is set to Y, then it will make the legacy intel soc driver fail, and
  moreover the current sof driver can't support broadwell well, as a
  result, many broadwell computers with I2S codec can't support sound anymore.

  [Fix]
  Intel submitted a patch, it will make those two kconfig options exclusive,
  and the legacy soc's option has higher priority, if both of them are
  enabled, sof's option will be disabled.

  [Test Case]
  Build the kernel and check the debian/build/$buidling_dir/.config,  the
  SND_SOC_SOF_BROADWELL_SUPPORT is disabled.

  [Regression Risk]
  Low, so far, the sof driver can't support broadwell machine well, so
  there is no machine use this driver yet.


  Hello!

  I noticed that since Linux 5.2rc2 audio playback no longer works on
  Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that
  happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel
  binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel-
  ppa/mainline/v5.2-rc2/

  To verify this assumption I tested two builds of Linux 5.3.1.
  1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/

  Audio playback doesn't work, dmesg:
  [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
  [4.480344] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14
  [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 
header 0x8700
  [   13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 
still running
  [   13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 
still running
  [   19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- 
ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff
  [   19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 
faile

  2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT.

  Audio playback works, dmesg:
  [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.907475] broadwell-audio broadwell-audio:

[Kernel-packages] [Bug 1846539]

Created attachment 286587
/proc/modules (5.4.7-arch1-1)

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

Title:
  [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no
  longer works on Dell Venue 11 Pro 7140

Status in HWE Next:
  Confirmed
Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux-oem-osp1 source package in Eoan:
  Confirmed

Bug description:
  [Impact]
  With the current default kernel config, the SND_SOC_SOF_BROADWELL_SUPPORT
  is set to Y, then it will make the legacy intel soc driver fail, and
  moreover the current sof driver can't support broadwell well, as a
  result, many broadwell computers with I2S codec can't support sound anymore.

  [Fix]
  Intel submitted a patch, it will make those two kconfig options exclusive,
  and the legacy soc's option has higher priority, if both of them are
  enabled, sof's option will be disabled.

  [Test Case]
  Build the kernel and check the debian/build/$buidling_dir/.config,  the
  SND_SOC_SOF_BROADWELL_SUPPORT is disabled.

  [Regression Risk]
  Low, so far, the sof driver can't support broadwell machine well, so
  there is no machine use this driver yet.


  Hello!

  I noticed that since Linux 5.2rc2 audio playback no longer works on
  Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that
  happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel
  binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel-
  ppa/mainline/v5.2-rc2/

  To verify this assumption I tested two builds of Linux 5.3.1.
  1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/

  Audio playback doesn't work, dmesg:
  [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
  [4.480344] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14
  [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 
header 0x8700
  [   13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 
still running
  [   13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 
still running
  [   19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- 
ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff
  [   19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 
faile

  2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT.

  Audio playback works, dmesg:
  [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.907475] broadwell-audio

[Kernel-packages] [Bug 1858200] Re: Kernel 5.4.5-050405-generic produces garbage on HDMI audio after 19.10

2020-01-07 Thread Raul Dias

I think it is invalid as the solution already exists in the updated
kernel.

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

Title:
  Kernel 5.4.5-050405-generic produces garbage on HDMI audio after 19.10

Status in linux package in Ubuntu:
  Invalid

Bug description:
  After upgrading from 19.04 to 19.10, the sound output to HDMI is
  garbage.

  The sound is great on local output, on bluetooth headphones, etc.  But
  when outputting to a HDMI TV it is garbage.

  I tried different users with the same problem.

  If I boot on Windows, the output is fine, which discards any physical
  problem, cables and TV as the source of the problem.

  I did delete any user pulseaudio configuration (and tried as a
  different one).

  I purged all system wide configuration and reinstalled the default
  pulseaudio configs with:

  apt-get -o DPkg::options::=--force-confmiss --reinstall install
  pulseaudio

  On 19.04 and before this problem did not happen at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  Uname: Linux 5.4.5-050405-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  raul   4850 F pulseaudio
   /dev/snd/controlC0:  raul   4850 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jan  3 09:33:11 2020
  InstallationDate: Installed on 2014-05-12 (2062 days ago)
  InstallationMedia: Error: [Errno 13] Permission denied: 
'/var/log/installer/media-info'
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to eoan on 2019-11-17 (46 days ago)
  dmi.bios.date: 02/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P870KM_KM1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/22/2017:svnNotebook:pnP870KM_KM1:pvrNotApplicable:rvnNotebook:rnP870KM_KM1:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P870KM_KM1
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  modified.conffile..etc.pulse.default.pa: [modified]
  modified.conffile..etc.pulse.system.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2019-12-22T00:17:51.785216
  mtime.conffile..etc.pulse.system.pa: 2019-12-22T00:16:08.693216

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

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

[Kernel-packages] [Bug 1846539]

Created attachment 286585
dmesg output (5.4.7-arch1-1)

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

Title:
  [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no
  longer works on Dell Venue 11 Pro 7140

Status in HWE Next:
  Confirmed
Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux-oem-osp1 source package in Eoan:
  Confirmed

Bug description:
  [Impact]
  With the current default kernel config, the SND_SOC_SOF_BROADWELL_SUPPORT
  is set to Y, then it will make the legacy intel soc driver fail, and
  moreover the current sof driver can't support broadwell well, as a
  result, many broadwell computers with I2S codec can't support sound anymore.

  [Fix]
  Intel submitted a patch, it will make those two kconfig options exclusive,
  and the legacy soc's option has higher priority, if both of them are
  enabled, sof's option will be disabled.

  [Test Case]
  Build the kernel and check the debian/build/$buidling_dir/.config,  the
  SND_SOC_SOF_BROADWELL_SUPPORT is disabled.

  [Regression Risk]
  Low, so far, the sof driver can't support broadwell machine well, so
  there is no machine use this driver yet.


  Hello!

  I noticed that since Linux 5.2rc2 audio playback no longer works on
  Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that
  happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel
  binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel-
  ppa/mainline/v5.2-rc2/

  To verify this assumption I tested two builds of Linux 5.3.1.
  1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/

  Audio playback doesn't work, dmesg:
  [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
  [4.480344] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14
  [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 
header 0x8700
  [   13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 
still running
  [   13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 
still running
  [   19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- 
ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff
  [   19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 
faile

  2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT.

  Audio playback works, dmesg:
  [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.907475] broadwell-audio

[Kernel-packages] [Bug 1848445]

2020-01-07 Thread rui.zhang

it is really rare to see a system running with acpi=off.
May I know why acpi=off is used in the first place?

for this particular issue, please confirm if problem still exists with
acpi_osi=!.

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

Title:
  [HP Pavilion 360 - 13-a200nt (ENERGY STAR)] Kernel parameter acpi_osi=
  required to boot

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  When booting my HP Pavilion 360 - 13-a200nt (ENERGY STAR), it stops
  with just a non-blinking white cursor on screen in the top left, and
  the Caps Lock doesn't respond when pressed.

  Previously on 4.x kernels, system would boot using acpi=off argument
  creating more problems.

  WORKAROUND: Boot with kernel parameter:
  acpi_osi=

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
   /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
   /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 10:02:44 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2341
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 13 x360 PC
  dmi.product.sku: L0B89EA#AB8
  dmi.product.version: 097712405F0410180
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1850238] Re: ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent kernels

2020-01-07 Thread Nahuel Pastorale

** Also affects: linux (Arch Linux)
   Importance: Undecided
   Status: New

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

Title:
  ucsi_ccg 50 second hang while resuming from s2ram with nvidia, recent
  kernels

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

Bug description:
  Short version
  =
  I'm experiencing a 50-second hang each time I resume from a "deep" 
(suspend-to-RAM) sleep.

  It happens with the newer kernel (5.3 series; I'm currently running
  the version from eoan-proposed), but not with the version from the
  Ubuntu 18.04.3 LTS (uname says "5.0.0-31-generic #33~18.04.1-Ubuntu
  SMP").

  [I haven't yet tried to test the mainline builds, nor to find/confirm
  the regression range, as this seems like something that will take me
  another week, and I'm not sure if it would be helpful.]

  I narrowed the problem down to what I believe is a broken USB Type-C
  controller on the NVIDIA GPU: the ucsi_ccg driver for
  /sys/devices/pci:00/:00:01.0/:01:00.3/i2c-0/0-0008 reports
  a timeout for both the initial PPM_RESET command (on system startup)
  and for the SET_NOTIFICATION_ENABLE command the driver runs on resume.

  I guess the hang is the driver waiting for a response to
  SET_NOTIFICATION_ENABLE; it appears to have been added recently in
  
https://github.com/torvalds/linux/commit/a94ecde41f7e51e2742e53b5f151aee662c54d39,
  which could explain why I don't see the hang with 5.0.x.

  Creating /etc/modprobe.d/dell.conf with a `blacklist ucsi_ccg` line
  (and rebooting) makes the hang go away.


  Steps to reproduce
  ==
  (these are not the actual steps one can take to reproduce, starting from a 
new install; let me know if those will be useful)

  1. Boot Ubuntu 19.10 with NVIDIA GPU drivers uninstalled and the following 
kernel parameters 
:
nouveau.modeset=0 nouveau.runpm=0   # force using integrated graphics
  # (the problem can be reproduced 
using NVIDIA's proprietary driver too, but I
  # guessed it's better to avoid 
it, and nouveau prints lots of errors with this GPU)
mem_sleep_default=deep  # suspend to RAM; suspend-to-idle 
has its own problems on this system

  2. Run `dmesg -w` and wait a minute or two until a message like the
  following is printed:

[  175.611346] ucsi_ccg 0-0008: failed to reset PPM!
[  175.611355] ucsi_ccg 0-0008: PPM init failed (-110)

  (attempting to suspend before the PPM init timeout will fail to enter sleep 
at all.)
  (if your system doesn't report PPM init timeout, you probably won't see the 
hang on resume either)

  3. Run `sudo pm-suspend` (using the power button to suspend causes
  other problems)

  ...wait for the laptop to go to sleep and the fans to turn off.

  4. Press Enter on the built-in keyboard to resume. (Although the way
  we wake up the system doesn't seem to matter.)

  5. Observe a hang lasting for almost a minute before the system is
  operational, with dmesg reporting:

[  299.331393] ata1.00: configured for UDMA/100


[  346.133024] ucsi_ccg 0-0008: PPM NOT RESPONDING
[  346.133039] PM: dpm_run_callback(): ucsi_ccg_resume+0x0/0x20 
[ucsi_ccg] returns -110
[  346.133042] PM: Device 0-0008 failed to resume: error -110
...
[  346.141504] Restarting tasks ... done.
[  346.340221] PM: suspend exit

  
  System info
  ===

  My Dell G3 3590 laptop has an NVIDIA "GeForce GTX 1660 Ti with Max-Q Design" 
GPU.
  NVIDIA's "Turing" chips include USB Type-C controller on the GPU (I read 
future VR headsets are supposed to use it 
),
 and indeed I'm seeing:

  # lspci -tv
  -[:00]-+-00.0  Intel Corporation 8th Gen Core Processor Host Bridge/DRAM 
Registers
 +-01.0-[01]--+-00.0  NVIDIA Corporation TU116M [GeForce GTX 1660 
Ti Mobile]
 |+-00.1  NVIDIA Corporation Device 1aeb
 |+-00.2  NVIDIA Corporation Device 1aec
 |\-00.3  NVIDIA Corporation Device 1aed
  ...

  Where the '1aed' device is detected as "NVIDIA USB Type-C Port Policy
  Controller" in Windows.

  I'm not sure if it's serving any useful purpose on this laptop, and it
  certainly doesn't seem to function properly:

  If I enable UCSI logging on startup (root's crontab):

  @reboot bash -c 'echo 1 >
  /sys/kernel/debug/tracing/events/ucsi/enable'

  ..the steps to reproduce above result in the following 
/sys/kernel/debug/tracing/trace:
  # tracer: nop
  #
  #

[Kernel-packages] [Bug 1844245] Re: Integrate Intel SGX driver into linux-azure

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

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

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

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

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

Title:
   Integrate Intel SGX driver into linux-azure

Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux-azure source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux-azure source package in Bionic:
  Invalid
Status in linux source package in Disco:
  Fix Committed
Status in linux-azure source package in Disco:
  In Progress
Status in linux source package in Eoan:
  Fix Committed
Status in linux-azure source package in Eoan:
  In Progress

Bug description:
  Intel is still trying to upstream the SGX driver, but in the meantime
  it would be desirable to have it available on the linux-azure kernel.

  The following version relies only on Kbuild:

  https://github.com/haimc-intel/SGXDataCenterAttestationPrimitives
  inker-ph1

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

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

[Kernel-packages] [Bug 1855312] Re: Fix unusable USB hub on Dell TB16 after S3

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

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

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

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

Title:
  Fix unusable USB hub on Dell TB16 after S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  In Progress
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  In Progress
Status in linux-oem source package in Disco:
  Won't Fix
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  In Progress
Status in linux-oem source package in Eoan:
  Won't Fix
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix

Bug description:
  [Impact]
  Sometimes USB hub on Dell TB16 stop working after S3.

  [Fix]
  Attempt to power cycle USB device when a it's stuck at eSS.Disabled
  state, it's basically not recoverable.

  [Test]
  After applying the patch, USB ports and USB ethernet are still working
  after 100 times S3 stress test.

  Tested on other platforms and didn't observe any regression.
  However, I have never seen any other USB device stuck in eSS.Disabled state,
  so the code path wasn't executed at all.

  [Regression Potential]
  Low. This is a last resort attempt, in most cases this code path won't
  be reached.

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

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

[Kernel-packages] [Bug 1825736] Re: Mouse scroll wheel barely works after suspend

2020-01-07 Thread Paul Tansom

Updating to 19.10 hasn't fixed the problem, but I have just replaced my
mouse and found the issue is no longer there with the new one. The
original was a Microsoft Wireless Mobile Mouse 1000 (045e:0745 Microsoft
Corp. Nano Transceiver v1.0 for Bluetooth) and the new one is a Logitech
M220 (046d:c534 Logitech, Inc. Unifying Receiver).

Not a fix, but a work around perhaps and extra info for any debugging. I
still have the Microsoft one to test any fixes posted here.

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

Title:
  Mouse scroll wheel barely works after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After a resuming from a suspend the mouse scroll wheel is almost, but
  not quite, non functional. If you scroll quickly for a while you do
  get a slight movement of the scroll bar to show that there is some
  level of communication, but nothing remotely usable.

  The fix is to use the following commands to remove the hid_generic
  module and reinstate it:

  sudo rmmod hid_generic
  sudo modprobe hid_generic

  Following this all works as expected until the next suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-modules-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paul   1905 F pulseaudio
   /dev/snd/controlC1:  paul   1905 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 21 19:02:00 2019
  Dependencies:
   
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8032c5f7-74fd-4a23-92cb-5ad7d0642a9f
  InstallationDate: Installed on 2017-12-15 (491 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20238
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=63abd1a6-61ac-485b-9448-47d635ee8808 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-20 (1 days ago)
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79CN50WW(V3.09)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058Std
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G510
  dmi.modalias: 
dmi:bvnLENOVO:bvr79CN50WW(V3.09):bd10/20/2014:svnLENOVO:pn20238:pvrLenovoG510:rvnLENOVO:rnINVALID:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoG510:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20238
  dmi.product.sku: LENOVO_MT_20238
  dmi.product.version: Lenovo G510
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1849269] Re: The system cannot resume from S3 if user unplugs the TB16 during suspend state

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

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

Title:
  The system cannot resume from S3 if user unplugs the TB16 during
  suspend state

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Unplug TBT dock during S3 and then wakes up the system leads to system hangs.
  This not only happens on Dell TB16, but also Dell WD19TB. It's more like a 
BIOS or TBT firmware issue that TBT firmware doesn't re-create the PCIe tunnels.

  [Fix]
  Mika provides 4 patches to fix this issue, but only 2 are accepted and are 
included in linus' tree. We need especially the 4th commit to fix the issue, so 
we keep the 3rd and 4th commits as sauce patches.

  [Test]
  Verified on Dell Precision 5530 + WD19TB

  [Regression Potential]
  Low, those patches doesn't change the code path much. The 4th commit adds 
some checks to return failure state, and it should be safe for those machines 
which is working well.

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

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

[Kernel-packages] [Bug 1856588] Re: WARNING: CPU: 0 PID: 1 at /build/linux-raspi2-DI3Sqp/linux-raspi2-4.15.0/arch/arm64/kernel/cpufeature.c:823 has_cpuid_feature+0x90/0x340

2020-01-07 Thread Juerg Haefliger

4.15.0-1050-raspi2 seems ok.

** Description changed:

- After upgrading Bionic on a Raspberry Pi 3B+ and rebooting:
+ After upgrading Bionic on a Raspberry Pi 3B+ from 
+ 4.15.0-1041-raspi2 to 4.15.0-1052-raspi2 and rebooting:
  
  [0.088772] CPU features: detected: 32-bit EL0 Support
  [0.106266] [ cut here ]
  [0.106325] WARNING: CPU: 0 PID: 1 at 
/build/linux-raspi2-DI3Sqp/linux-raspi2-4.15.0/arch/arm64/kernel/cpufeature.c:823
 has_cpuid_feature+0x90/0x340
  [0.106366] Modules linked in:
  [0.106397] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-1052-raspi2 
#56-Ubuntu
  [0.106426] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT)
  [0.106455] pstate: 4045 (nZcv daif +PAN -UAO)
  [0.106480] pc : has_cpuid_feature+0x90/0x340
  [0.106504] lr : has_cpuid_feature+0x90/0x340
  [0.106524] sp : 08023d60
- [0.106542] x29: 08023d60 x28:  
- [0.106572] x27:  x26: 28740962ff98 
- [0.106603] x25: 0040 x24: 287409609c40 
- [0.106633] x23: 287409609000 x22: 28740962f000 
- [0.106664] x21: 287408e29740 x20: 0001 
- [0.106693] x19: 287408c03e78 x18:  
- [0.106723] x17: 01b5644e x16: 0068011fff13 
- [0.106753] x15: 287409609c08 x14: 0720072007200720 
- [0.106783] x13: 0720072007200720 x12: 0720072007200720 
- [0.106814] x11: 0720072007200720 x10: 0720072007200720 
- [0.106845] x9 : 0720072007200720 x8 : 0720072007200720 
- [0.106875] x7 : 0720072d072d072d x6 : 0044 
- [0.106904] x5 :  x4 :  
- [0.106934] x3 :  x2 : f9b69bb55a180d00 
- [0.106964] x1 :  x0 : 0024 
+ [0.106542] x29: 08023d60 x28: 
+ [0.106572] x27:  x26: 28740962ff98
+ [0.106603] x25: 0040 x24: 287409609c40
+ [0.106633] x23: 287409609000 x22: 28740962f000
+ [0.106664] x21: 287408e29740 x20: 0001
+ [0.106693] x19: 287408c03e78 x18: 
+ [0.106723] x17: 01b5644e x16: 0068011fff13
+ [0.106753] x15: 287409609c08 x14: 0720072007200720
+ [0.106783] x13: 0720072007200720 x12: 0720072007200720
+ [0.106814] x11: 0720072007200720 x10: 0720072007200720
+ [0.106845] x9 : 0720072007200720 x8 : 0720072007200720
+ [0.106875] x7 : 0720072d072d072d x6 : 0044
+ [0.106904] x5 :  x4 : 
+ [0.106934] x3 :  x2 : f9b69bb55a180d00
+ [0.106964] x1 :  x0 : 0024
  [0.106994] Call trace:
  [0.107017]  has_cpuid_feature+0x90/0x340
  [0.107044]  setup_elf_hwcaps+0x50/0xd4
  [0.107068]  setup_cpu_features+0x5c/0x100
  [0.107092]  smp_cpus_done+0x34/0xa8
  [0.107116]  smp_init+0xf0/0x108
  [0.107139]  kernel_init_freeable+0xec/0x24c
  [0.107166]  kernel_init+0x18/0x110
  [0.107189]  ret_from_fork+0x10/0x1c
  [0.107214] ---[ end trace 870841374e14badc ]---
  [0.107238] CPU: All CPU(s) started at EL2

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

Title:
  WARNING: CPU: 0 PID: 1 at /build/linux-raspi2-DI3Sqp/linux-
  raspi2-4.15.0/arch/arm64/kernel/cpufeature.c:823
  has_cpuid_feature+0x90/0x340

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

Bug description:
  After upgrading Bionic on a Raspberry Pi 3B+ from 
  4.15.0-1041-raspi2 to 4.15.0-1052-raspi2 and rebooting:

  [0.088772] CPU features: detected: 32-bit EL0 Support
  [0.106266] [ cut here ]
  [0.106325] WARNING: CPU: 0 PID: 1 at 
/build/linux-raspi2-DI3Sqp/linux-raspi2-4.15.0/arch/arm64/kernel/cpufeature.c:823
 has_cpuid_feature+0x90/0x340
  [0.106366] Modules linked in:
  [0.106397] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-1052-raspi2 
#56-Ubuntu
  [0.106426] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT)
  [0.106455] pstate: 4045 (nZcv daif +PAN -UAO)
  [0.106480] pc : has_cpuid_feature+0x90/0x340
  [0.106504] lr : has_cpuid_feature+0x90/0x340
  [0.106524] sp : 08023d60
  [0.106542] x29: 08023d60 x28: 
  [0.106572] x27:  x26: 28740962ff98
  [0.106603] x25: 0040 x24: 287409609c40
  [0.106633] x23: 287409609000 x22: 28740962f000
  [0.106664] x21: 287408e29740 x20: 0001
  [0.106693] x19: 287408c03e78 x18: 
  [0.106723] x17: 01b5644e x16: 0068011fff13
  [0.106753] x15: 287409609c08 x14: 0720072007200720
  [0.106783] x13: 0720072007200720 x12: 0720072007200720

[Kernel-packages] [Bug 1854887] Re: cifs: DFS Caching feature causing problems traversing multi-tier DFS setups

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

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

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

Title:
  cifs: DFS Caching feature causing problems traversing multi-tier DFS
  setups

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1854887

  [Impact]

  There is a problem where kernels 5.0-rc1 and onwards cannot mount a
  multi tier cifs DFS setup, while kernels 4.20 and below can mount the
  share fine.

  The DFS tiering structure looks like this:

  Domain virtual DFS (i.e. \\company.com\folders\share)
  |-- Domain controller DFS (i.e. \\regional-dc.company.com\folders\share)
  |-- Regional DFS Server (i.e. \\regional-dfs.company.com\folders\share)
  |-- Actual file server (i.e. \\regional-svr.company.com\share)

  On the 5.x series kernels, after getting the DFS referrals list
  through to the Regional DFS Server, which responds with the correct
  server/share, instead of going to the Actual file server, the kernel
  backtracks from the Regional DFS Server back to the Domain controller
  and requests the share there. Of course, this share does not exist on
  the Domain controller, as it only exists on the Actual file server,
  and the connection dies.

  We have collected a packet capture, and the flow looks like this:

  Legend:
  --
  DC = Domain Controller / Domain DFS Root
  RDC = Regional Domain Controller / Domain DFS Root
  RDS = Regional DFS Server
  AFS = Actual File Server

  4.18.0-21-generic Ubuntu kernel - Good

  Host:   request/response
  
  DC: company.com\folders
  DC: Referral List
  RDC:start convo
  RDC:\Folders\Country\ referral
  RDC:\Folders\Country\ referral
  RDS:start convo
  RDS:\Root\Country\
  RDS:STATUS_PATH_NOT_COVERED
  RDS:request referrals
  RDS:Referral List
  AFS:convo started
  AFS:\
  AFS:Good response

  5.0.0-26-generic Ubuntu kernel - Bad

  Host:   request/response
  
  DC: company.com\folders
  RDC:start convo
  RDC:\Folders\Country\
  RDC:STATUS_PATH_NOT_COVERED
  RDS:start convo
  RDS:\Root\Country\
  RDS:STATUS_PATH_NOT_COVERED
  RDC:\Root\Country\
  RDC:STATUS_PATH_NOT_COVERED

  From there the debugging output was more or less the same between the
  two kernel versions, until the problematic area:

  Linux 4.18:

  Full log: https://paste.ubuntu.com/p/D9XwBbvTXc/

  Status code returned 0xc257 STATUS_PATH_NOT_COVERED
  fs/cifs/smb2maperror.c: Mapping SMB2 status code 0xc257 to POSIX err -66
  fs/cifs/connect.c: build_unc_path_to_root: full_path=\\\Root\Country\
  fs/cifs/smb2ops.c: smb2_get_dfs_refer path <\\Root\Country\>
  fs/cifs/misc.c: num_referrals: 1 dfs flags: 0x2 ...
  fs/cifs/dns_resolve.c: dns_resolve_server_name_to_ip: resolved:  to 
  fs/cifs/connect.c: Username: XXX
  // mounts the share successfully

  Linux 5.0:

  Full log: https://paste.ubuntu.com/p/9sXPj7WMQv/

  Status code returned 0xc257 STATUS_PATH_NOT_COVERED
  fs/cifs/smb2maperror.c: Mapping SMB2 status code 0xc257 to POSIX err -66
  fs/cifs/connect.c: build_unc_path_to_root: full_path=\\\Root\Country\
  fs/cifs/connect.c: build_unc_path_to_root: full_path=\\\Root\Country\
  fs/cifs/dfs_cache.c: do_dfs_cache_find: search path: \\Root\Country\
  fs/cifs/dfs_cache.c: do_dfs_cache_find: cache miss
  fs/cifs/dfs_cache.c: do_dfs_cache_find: DFS referral request for \\Root\Country\
  fs/cifs/smb2ops.c: smb2_get_dfs_refer path <\\Root\Country\>
  fs/cifs/smb2pdu.c: SMB2 IOCTL
  Status code returned 0xc225 STATUS_NOT_FOUND
  fs/cifs/smb2maperror.c: Mapping SMB2 status code 0xc225 to POSIX err -2
  // mounting the share fails shortly after

  This has quite a big impact to customers who need to mount their
  multi-tier DFS mounts, as they have to remain on the 4.15 bionic
  kernel and cannot use the HWE kernel for their machines.

  [Fix]

  After some debugging, I narrowed the cause down to a new DFS caching
  feature introduced in 5.0-rc1. I started a discussion with the
  upstream maintainer of cifs, which you can read here:

  https://lore.kernel.org/linux-cifs/05aa2995-e85e-
  0ff4-d003-5bb08bd17...@canonical.com/T/#u

  This discussion resulted in the below upstream commit, which was
  merged in the 5.5 development window:

  commit 5bb30a4dd60e2a10a4de9932daff23e503f1dd2b
  Author: Paulo Alcantara (SUSE) 
  Date:   Fri Nov 22

[Kernel-packages] [Bug 1857541] Re: [SRU][B/OEM-B/OEM-OSP1/D/E/F] Add LG I2C touchscreen multitouch support

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

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

** Changed in: linux (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/1857541

Title:
  [SRU][B/OEM-B/OEM-OSP1/D/E/F] Add LG I2C touchscreen multitouch
  support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Triaged

Bug description:
  SRU justification:

  [Impact]
  The current kernel didn't support multitouch for LG I2C touchscreen.

  [Fix]
  Add LG I2C id to hid-multitouch to support it.

  [Test]
  Verified on hardware with a positive result.

  [Regression Potential]
  Low.
  Add new I2C id with positive verification.

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

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

[Kernel-packages] [Bug 1848739] Re: [linux] Patch to prevent possible data corruption

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

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

Title:
  [linux] Patch to prevent possible data corruption

Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Invalid
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux-azure source package in Bionic:
  Invalid

Bug description:
  There are three patches that prevent possible data corruption.  The
  three commits are:

  aef1897cd36d ("blk-mq: insert rq with DONTPREP to hctx dispatch list when 
requeue")
  c616cbee97ae ("blk-mq: punt failed direct issue to dispatch list")
  923218f6166a ("blk-mq: don't allocate driver tag upfront for flush rq")

  18.04 has all three of these patches.  16.04 has two out of the three,
  but it is missing commit c616cbee97ae.

  We would like to request commit c616cbee97ae be included in the 16.04 kernel:
  c616cbee97ae ("blk-mq: punt failed direct issue to dispatch list")

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

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

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

2020-01-07 Thread bugproxy

--- Comment From heinz-werner_se...@de.ibm.com 2020-01-07 08:58 EDT---
IBM bugzilla status-> closed, fix Released with requested distros

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

Title:
  Change Config Option CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE for s390x
  from yes to no

Status in Ubuntu on IBM z Systems:
  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 Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

  * By default all standby memory that is configured to an LPAR is used
  at boot (IPL) time.

  * But the standby memory is meant to be added and used on demand later
  (after IPL).

  [Fix]

  * 0001-Ubuntu-Config-Disabled-CONFIG_MEMORY_HOTPLUG_DEFAULT.patch

  [Test Case]

  * Configure an LPAR in it's Activation Profile with a certain amount
  of 'Initial' memory and some 'Reserved' memory on top.

  * Re-activate the LPAR to make the changes take effect and boot (IPL)
  Ubuntu.

  * Check with the help of free whether the reported memory is only the
  initial memory (actual) or initial+reserved (desired).

  [Regression Potential]

  * There is a certain regression potential, since some systems may have
  Initial and Reserved memory already defined today and have it already
  all in use under Linux (today obviously w/o having it dynamically
  added).

  * If such a system got re-activated and rebooted, the memory size will
  then be what's defined as Initial memory and no longer
  Initial+Reserved.

  * To be able to use the same size of the memory than before, the
  Reserved memory need to be either dynamically be added or the Initial
  memory re-configured to the sum of former Initial+Reserved.

  * The latter case requires a re-activation of the LPAR, but since this
  corner case only happens after a reboot, a downtime is already in
  place for the re-activation.

  * But overall the regression potential is low since it's for s390x
  only and the 'Reserved' memory option in the Activation Profile is
  rarely used.

  [Other Info]

  * In the past this config option was diabled for ppc64el, too.
  __

  The Ubuntu kernel configuration contains 
CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE=y for s390.
  This causes all standby memory configured for an LPAR to be used at IPL time.

  Note that this is definetaly not what a user wants on s390.
  The normal process is: define a certain amount of "base" memory which the 
system should use when IPL'ed, and define also a certain amount of "standby" 
memory which can be (also only partially) be additionaly used when necessary.
  Also note that it is *not* possible to add additional memory to a runnung 
system, besides the amount of memory specified as "standby".

  Therefore please change the kernel config option
  CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE to "n" for s390.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1848492/+subscriptions

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

[Kernel-packages] [Bug 1856983] Re: bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker

2020-01-07 Thread Sean Feole

Verified gve driver in all gcp kernels for Bionic 2019.12.02

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

Title:
  bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1856985
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Monday, 06. January 2020 15:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1856982
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856983/+subscriptions

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

[Kernel-packages] [Bug 1856983] Re: bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1856985
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Monday, 06. January 2020 15:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
-   regression-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1856982
  variant: debs

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

Title:
  bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1856985
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Monday, 06. January 2020 15:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1856982
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856983/+subscriptions

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

[Kernel-packages] [Bug 1856983] Re: bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker

2020-01-07 Thread Sean Feole

** Tags added: regression-testing-passed

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

Title:
  bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1856985
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Monday, 06. January 2020 15:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1856982
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856983/+subscriptions

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

[Kernel-packages] [Bug 1856983] Re: bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker

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

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

Title:
  bionic/linux-gcp: 5.0.0-1028.29~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1856985
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Monday, 06. January 2020 15:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1856982
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856983/+subscriptions

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

[Kernel-packages] [Bug 1239459]

2020-01-07 Thread mehndidesignid

http://www.mehndidesign.info/;>Simple Mehndi DesignIf you
are looking for Beautifull Simple Mehndi Design. This is the Right Place
for you, Here is the 2000+ huge collection of Latest Simple Mehndi
Design 2020.

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

Title:
  1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few
  seconds

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

Bug description:
  With the new 3.11.0-12-generic kernel, wifi has problems to connect with many 
errors like these:
  Oct 13 23:50:03 ubuntotto kernel: [ 1186.580726] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:50:03 ubuntotto kernel: [ 1186.740659] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:50:04 ubuntotto kernel: [ 1186.900544] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:50:04 ubuntotto kernel: [ 1187.060571] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:50:04 ubuntotto kernel: [ 1187.096576] ieee80211 phy0: 
rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0
  Oct 13 23:50:05 ubuntotto kernel: [ 1188.280106] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:50:05 ubuntotto kernel: [ 1188.440128] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:51:06 ubuntotto kernel: [ 1249.560697] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:51:06 ubuntotto kernel: [ 1249.720644] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:51:07 ubuntotto kernel: [ 1249.880590] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:51:07 ubuntotto kernel: [ 1250.040543] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-12-generic 3.11.0-12.19
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrea 1791 F pulseaudio
  Date: Sun Oct 13 23:45:04 2013
  HibernationDevice: RESUME=UUID=297ef090-5420-41f6-8439-f1254f3e9e15
  InstallationDate: Installed on 2013-10-12 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: ASUSTeK COMPUTER INC. X200CA
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=088f2a7d-b78f-4bdd-a184-754b70a3184a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-12-generic N/A
   linux-backports-modules-3.11.0-12-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-10-13 (0 days ago)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200CA.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX200CA.208:bd09/18/2013:svnASUSTeKCOMPUTERINC.:pnX200CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 88746]

2020-01-07 Thread clarkembers

I am from Alberta, Canada. I am really happy to be a member of this
forum. thanks.

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

Title:
  ehci_hcd module causes I/O errors in USB 2.0 devices

Status in Linux:
  Invalid
Status in linux package in Ubuntu:
  Won't Fix
Status in linux-source-2.6.20 package in Ubuntu:
  Won't Fix
Status in linux-source-2.6.22 package in Ubuntu:
  Won't Fix
Status in linux source package in Hardy:
  Won't Fix
Status in linux-source-2.6.20 source package in Hardy:
  Won't Fix
Status in linux-source-2.6.22 source package in Hardy:
  Won't Fix
Status in linux source package in Intrepid:
  Won't Fix
Status in linux-source-2.6.20 source package in Intrepid:
  Won't Fix
Status in linux-source-2.6.22 source package in Intrepid:
  Won't Fix
Status in linux source package in Jaunty:
  Won't Fix
Status in linux-source-2.6.20 source package in Jaunty:
  Won't Fix
Status in linux-source-2.6.22 source package in Jaunty:
  Won't Fix
Status in linux-source-2.6.22 package in Baltix:
  Invalid
Status in linux package in Fedora:
  Invalid

Bug description:
  Certain USB devices do not work properly, or do not work at all, while
  the ehci_hcd module is loaded.

  A solution is to unload the ehci_hcd module, which is loaded every time the 
computer starts, using the command 'sudo modprobe -r ehci_hcd'. This works fine 
but unfortunatly ehci-hcd is necessary for using USB 2.0, so you lose USB 2.0 
features.
  Another solution is to disable USB 2.0 through the BIOS setup.

  With some devices it is possible to read files normally (ie. copy
  files from an USB pendrive to the computer), but the device
  disconnects abrubtly when you start writing data on the device. In
  some devices it fails after writing a certain amount of data, probably
  the size of the write cache.

  Steps to reproduce:
  1. Insert your USB 2.0 device (like a flash drive)
  2. If the device is recognised and mounted properly try copying a file to it.
  3. Comfirm with the 'dmesg' command that it isn't functioning properly. (I/O 
errors etc)
  4. Remove the USB device
  5. Unload ehci_hcd with  'sudo modprobe -r ehci_hcd'
  6. Insert your USB device again.
  7. Check that everything works. (copy some files, etc.)

  A disproportionate number of individuals report Alcor chipsets in the 
problematic behavior.  See:
  
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746/comments/62
  
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746/comments/119
  
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746/comments/299
  
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746/comments/397
  http://bugzilla.kernel.org/show_bug.cgi?id=ehci_hcd

  Noted Workarounds:
  
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746/comments/372

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

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

[Kernel-packages] [Bug 1443924]

2020-01-07 Thread mehndidesignid

http://www.mehndidesign.info/;>Simple Mehndi DesignIf you
are looking for Beautifull Simple Mehndi Design. This is the Right Place
for you, Here is the 2000+ huge collection of Latest Simple Mehndi
Design 2020.

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

Title:
  1814:0201 ieee80211 phy0: rt2x00queue_flush_queue:Warning - Queue 0
  failed to flush

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

Bug description:
  Philips i386 PC with rt2x00 pci is suffering loss of WiFi connectivity
  after installing 15.04 Beta.

  The system did work correctly with older Ubuntu versions (like 12.04)
  and had this problem show up after upgrading to Trusty (as I already
  reported in bug #1318837). Using Trusty the problem went away when
  switching from the stock 3.13.0-XX-generic kernel to builds of newer
  kernels (like 3.14.1-031401).

  Now the same problem shows up again after installing Vivid Beta. It seems to 
be the same problem reported for other Ubuntu releases (see bugs #1318837 and 
#1383555) and also the same problem of this upstream kernel bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=61621

  Someone on kernel's bug mentions turning off MSI interrupts and I can confirm 
it did change the situation:
  - normally the system looses WiFi connectivity mere seconds after boot (eg. 
can't ping anything after boot)
  - if I boot with "pci=nomsi" the system will remain connected to the WiFi for 
a much longer period (eg. I am able to apt-get install something after boot)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-extra-3.19.0-13-generic 3.19.0-13.13
  ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3
  Uname: Linux 3.19.0-13-generic i686
  ApportVersion: 2.17-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luca   1997 F pulseaudio
  CurrentDesktop: LXDE
  Date: Tue Apr 14 14:19:19 2015
  HibernationDevice: RESUME=UUID=cbd1e136-ffc4-48b9-b2aa-c15264b9b132
  MachineType: Freeline Freeline Series
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-13-generic 
root=UUID=6110f881-b32b-426d-910a-c63b355c179c ro quiet splash vt.handoff=7 
pci=nomsi
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-13-generic N/A
   linux-backports-modules-3.19.0-13-generic  N/A
   linux-firmware 1.143
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2004
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: Freeline Series
  dmi.board.vendor: Freeline
  dmi.board.version: Ver1.0
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/29/2004:svnFreeline:pnFreelineSeries:pvrVer1.0:rvnFreeline:rnFreelineSeries:rvrVer1.0:cvn:ct3:cvr:
  dmi.product.name: Freeline Series
  dmi.product.version: Ver1.0
  dmi.sys.vendor: Freeline

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

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

[Kernel-packages] [Bug 1833281]

2020-01-07 Thread m.novosyolov

(In reply to ValdikSS from comment #60)
> I'm not sure, but people on Rosa forum blamed BTRFS for this bug. I'm pretty
> sure it's not directly tight with BTRFS, but write and read amplification
> may explain why lags are more severe with this FS.

People here and on ROSA forum blamed BTRFS for the problem that swap is
being not used, but not for microfreezes...

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

Title:
  System freeze when memory is put on SWAP in Linux >4.10.x

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

Bug description:
  I'm reporting this since it's reproduceable the 70% of the time.
  Summary:

  In different circumstances, when the systems starts to swap out RAM
  memory, even small amounts, the system becomes completely unusuable
  and the screen freezes up, no mouse movement, no TTY access or SSH
  access can be made, only SYSRQ keys seem to do something (only reboot,
  so REISUB worked so far though, OOM is useless since the memory/swap
  is not even full)

  The I/O Disk led is stuck to 100% in ALL the following cases when this
  happens.

  So far:
  - This happens even when only ZRAM is enabled, and no swap partition is used.
  - Happens when ZSWAP is used with a swap partition
  - Happens also when a partition without zram or zswap is used
  - Maybe it's AMD specific? 

  However, I'm not experiencing this on my laptop using the same tests.

  My laptop is an Intel one, while my desktop is an AMD Ryzen platform.

  Here are the specs:
  CPU: AMD Ryzen 5 1600 no OC
  GPU: AMD RX 580 8GB
  SSD: Crucial MX500 500GB
  MOBO: MSI B350M Grenade
  RAM: 8GB HyperX Kingston 2667Mhz

  Ubuntu version: 18.04 LTS, backports repo enabled
  Kernel version: 4.18.0-18, official ubuntu repo
  Bios settings: Default

  Additional info: Maybe I'm not 100% sure, but I noticed when using the
  5.0.0-17 generic kernel, the lockups seem to still happen, but they
  recover eventually. Happened only a few times though...

  But will always be frozen for at least 30 seconds, differently from my
  intel laptop where those do occur.

  The SSD make is the same. I bought two of these, they got also the
  same amount of RAM.

  In my laptop those do not occur at all. Swapping memory even huge
  quantities like 1GB or more, do not produce any issues.

  Tests made:
  For testing this behaviour I tried:

  - Compiling the chromium-browser source code (takes up a lot of system
  RAM)

  - Used the "stress" command, using a specific amount of memory to
  decide how many it will be swapped, and here I noticed that even small
  quantities like a couple of megabytes will cause the system to freeze
  the 70% of the times

  Example: "stress --vm 1 --vm-bytes=7G"

  What should happen:
  I expect system slowdowns when swapping out memory since I do not have enough 
RAM, but unlikely when using Windows or my laptop with the same Linux version, 
not a completely unusuable environment. The swap partition is in both cases on 
an SSD.

  Reproduceability: 70% of the times

  Additional info again:
  I'm not sure this is due to any hardware failure, my SSD health is fine, as 
my CPU and RAM. As I said swapping in Windows works fine...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  haru   2076 F pulseaudio
   /dev/snd/controlC2:  haru   2076 F pulseaudio
   /dev/snd/controlC0:  haru   2076 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IwConfig:
   enp24s0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7A37
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic 
root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-17-generic N/A
   linux-backports-modules-5.0.0-17-generic  N/A
   linux-firmware1.173.6
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 5.0.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo video
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 01/22/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.K0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350M MORTAR (MS-7A37)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 4
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version:

[Kernel-packages] [Bug 1803179]

2020-01-07 Thread mfulz

ok I've found out that this difference seems to be gone when using tlp
instead of laptop-mode-tools.

Kernel 5.5-rc3 (including these patches) + Bumblebee and tlp provides me
the full optimus usage + 8/9W power consumption on intel GPU.

For me everything is working absolutely perfect now !!! :)

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

Title:
  System does not reliably come out of suspend

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-410 package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 15 (9750); it might eventually manage to suspend when the lid
  is closed, but more often than not will not wake up again when the lid
  is opened. Waking up using the power button often results in a system
  that is apparently frozen (graphics displayed are the last on screen
  before suspend, clock seconds do not change)

  System is unresponsive to the keyboard at that time (can't switch to a
  VT or otherwise interact with the system other than holding the power
  button for a few seconds to shut it down).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mtrudel2516 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 13 10:42:08 2018
  InstallationDate: Installed on 2018-11-02 (10 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=UUID=14900847-323c-4427-b59e-89210ec1c8ec ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1833281]

2020-01-07 Thread cfeck

I don't use btrfs, but only ext4 on an SSD. Since updating my system
from kernel 5.1.7 to kernel 5.3.12 in Tumbleweed, I get regular ~1-2
second freezes (e.g. mouse pointer hangs in X11, or characters don't
appear while typing in Konsole) while Blender renders and swaps out
finished tiles. This didn't happen with the previous kernel.

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

Title:
  System freeze when memory is put on SWAP in Linux >4.10.x

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

Bug description:
  I'm reporting this since it's reproduceable the 70% of the time.
  Summary:

  In different circumstances, when the systems starts to swap out RAM
  memory, even small amounts, the system becomes completely unusuable
  and the screen freezes up, no mouse movement, no TTY access or SSH
  access can be made, only SYSRQ keys seem to do something (only reboot,
  so REISUB worked so far though, OOM is useless since the memory/swap
  is not even full)

  The I/O Disk led is stuck to 100% in ALL the following cases when this
  happens.

  So far:
  - This happens even when only ZRAM is enabled, and no swap partition is used.
  - Happens when ZSWAP is used with a swap partition
  - Happens also when a partition without zram or zswap is used
  - Maybe it's AMD specific? 

  However, I'm not experiencing this on my laptop using the same tests.

  My laptop is an Intel one, while my desktop is an AMD Ryzen platform.

  Here are the specs:
  CPU: AMD Ryzen 5 1600 no OC
  GPU: AMD RX 580 8GB
  SSD: Crucial MX500 500GB
  MOBO: MSI B350M Grenade
  RAM: 8GB HyperX Kingston 2667Mhz

  Ubuntu version: 18.04 LTS, backports repo enabled
  Kernel version: 4.18.0-18, official ubuntu repo
  Bios settings: Default

  Additional info: Maybe I'm not 100% sure, but I noticed when using the
  5.0.0-17 generic kernel, the lockups seem to still happen, but they
  recover eventually. Happened only a few times though...

  But will always be frozen for at least 30 seconds, differently from my
  intel laptop where those do occur.

  The SSD make is the same. I bought two of these, they got also the
  same amount of RAM.

  In my laptop those do not occur at all. Swapping memory even huge
  quantities like 1GB or more, do not produce any issues.

  Tests made:
  For testing this behaviour I tried:

  - Compiling the chromium-browser source code (takes up a lot of system
  RAM)

  - Used the "stress" command, using a specific amount of memory to
  decide how many it will be swapped, and here I noticed that even small
  quantities like a couple of megabytes will cause the system to freeze
  the 70% of the times

  Example: "stress --vm 1 --vm-bytes=7G"

  What should happen:
  I expect system slowdowns when swapping out memory since I do not have enough 
RAM, but unlikely when using Windows or my laptop with the same Linux version, 
not a completely unusuable environment. The swap partition is in both cases on 
an SSD.

  Reproduceability: 70% of the times

  Additional info again:
  I'm not sure this is due to any hardware failure, my SSD health is fine, as 
my CPU and RAM. As I said swapping in Windows works fine...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  haru   2076 F pulseaudio
   /dev/snd/controlC2:  haru   2076 F pulseaudio
   /dev/snd/controlC0:  haru   2076 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IwConfig:
   enp24s0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7A37
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-17-generic 
root=UUID=75d45574-7169-4653-aea3-9f95087f0806 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-17-generic N/A
   linux-backports-modules-5.0.0-17-generic  N/A
   linux-firmware1.173.6
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 5.0.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo video
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 01/22/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.K0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350M MORTAR (MS-7A37)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 4
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias:

[Kernel-packages] [Bug 1857409] Re: alsa/sof: load different firmware on different platforms

2020-01-07 Thread Timo Aaltonen

** Changed in: linux-oem-osp1 (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/1857409

Title:
  alsa/sof: load different firmware on different platforms

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Confirmed

Bug description:
  [Impact]
  In our ubuntu kernel, the sof driver will load the sof-cnl.ri (firmware)
  on all platforms, but mainline kernel already supported the multi
  firmwares on differnt platforms, and OEM project needs us to
  support the mutli-firmware names in the ubuntu kernel

  [Fix]
  cherry-pick 3 upstream patches, then on cnl platforms, it will
  load sof-cnl.ri, on cml platfomrs, it will load sof-cml.ri, on cfl
  platforms, it will load sof-cfl.ri

  
  [Test Case]
  Prepare the firmware from https://github.com/thesofproject/linux-firmware
  master branch, then boot the kernel with these patches.

  [Regression Risk]
  Low, just let different platforms load differnt firmware, and these
  patches are in the upstream kernel.

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

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

[Kernel-packages] [Bug 1854808] Re: bionic/linux-oracle: 4.15.0-1031.34 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


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

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

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

Title:
  bionic/linux-oracle: 4.15.0-1031.34 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-oracle source package in Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: '1856749'
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 12:27 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
unknown/unknown: bug 1854807
xenial/linux-oracle: bug 1854807
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854808/+subscriptions

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

[Kernel-packages] [Bug 1856749] Re: bionic/linux: 4.15.0-74.84 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


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

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

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

Title:
  bionic/linux: 4.15.0-74.84 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 12:27 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
bionic/linux-aws: bug 1854802
bionic/linux-fips: bug 1854809
bionic/linux-gke-4.15: bug 1854804
bionic/linux-ibm-gt: bug 1854806
bionic/linux-kvm: bug 1854805
bionic/linux-oem: bug 1854797
bionic/linux-oracle: bug 1854808
bionic/linux-raspi2: bug 1854793
bionic/linux-snapdragon: bug 1854796
bionic/linux/pc-kernel: bug 1856747
bionic/linux/pc-lowlatency-kernel: bug 1856748
xenial/linux-azure: bug 1856203
xenial/linux-gcp: bug 1856976
xenial/linux-hwe: bug 1856804
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856749/+subscriptions

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

[Kernel-packages] [Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic

2020-01-07 Thread Albert Pool

Yes, works fine.

I'll change the status to fix released.

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

Title:
  Synaptics s3203 touchpad not working after update to kernel
  4.15.0-72-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  SRU justification
  =
  [Impact]
  Synaptics s3203 touchpad not working after update to kernel
  4.15.0-72-generic

  [Fix]
  After applied commit "Input: synaptics-rmi4 - avoid processing unknown
  IRQs",
  no irq response from touchpad.
  This commit is depended on commit:
  "Input: synaptics-rmi4 - convert irq distribution to irq_domain"

  [Test]
  Verified on hardware, tests results are good.

  [Regression Potential]
  Low.
  Fix bug that introduced by stable release update.

  2nd and 3rd patches are fixes for the 1st patch.
  These commits are already included by eoan kernel, so bionic 4.15 only.

  Original reports
  ===

  environment:
  Dell Laptop XPS-9333
  Device:
  # xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SYNAPTICS Synaptics Large Touch Screen  id=9[slave  pointer 
 (2)]
  ⎜   ↳ Synaptics s3203 id=12   [slave  pointer 
 (2)]
  ⎜   ↳ Ultrathin Touch Mouse   id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=13   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=14   [slave  
keyboard (3)]
  ↳ Integrated_Webcam_HD: Integrate id=10   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]

  # xinput --list-props 12
  Device 'Synaptics s3203':
   Device Enabled (142):1
   Coordinate Transformation Matrix (144):  1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
   Device Accel Profile (270):  1
   Device Accel Constant Deceleration (271):2.50
   Device Accel Adaptive Deceleration (272):1.00
   Device Accel Velocity Scaling (273): 9.712231
   Synaptics Edges (304):   162, 3908, 133, 2339
   Synaptics Finger (305):  25, 30, 0
   Synaptics Tap Time (306):180
   Synaptics Tap Move (307):209
   Synaptics Tap Durations (308):   180, 180, 100
   Synaptics ClickPad (309):1
   Synaptics Middle Button Timeout (310):   0
   Synaptics Two-Finger Pressure (311): 282
   Synaptics Two-Finger Width (312):7
   Synaptics Scrolling Distance (313):  -95, 95
   Synaptics Edge Scrolling (314):  0, 0, 0
   Synaptics Two-Finger Scrolling (315):1, 1
   Synaptics Move Speed (316):  1.00, 1.75, 0.042008, 0.00
   Synaptics Off (317): 0
   Synaptics Locked Drags (318):0
   Synaptics Locked Drags Timeout (319):5000
   Synaptics Tap Action (320):  0, 0, 0, 0, 1, 3, 2
   Synaptics Click Action (321):1, 3, 2
   Synaptics Circular Scrolling (322):  0
   Synaptics Circular Scrolling Distance (323): 0.10
   Synaptics Circular Scrolling Trigger (324):  0
   Synaptics Circular Pad (325):0
   Synaptics Palm Detection (326):  1
   Synaptics Palm Dimensions (327): 10, 200
   Synaptics Coasting Speed (328):  20.00, 50.00
   Synaptics Pressure Motion (329): 30, 160
   Synaptics Pressure Motion Factor (330):  1.00, 1.00
   Synaptics Resolution Detect (331):   1
   Synaptics Grab Event Device (332):   0
   Synaptics Gestures (333):1
   Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0
   Synaptics Pad Resolution (335):  42, 42
   Synaptics Area (336):0, 0, 0, 0
   Synaptics Soft Button Areas (337):   0, 0, 0, 0, 0, 0, 0, 0
   Synaptics Noise Cancellation (338):  23, 23
   Device Product ID (262): 1739, 10036
   Device Node (263):   "/dev/input/event5"

  # lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 09)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
09)
  00:14.0 USB controller: Intel Corporation 8

[Kernel-packages] [Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic

2020-01-07 Thread Albert Pool

@Cliff Wong, your problem should be fixed as well. Please try the
4.15.0-74 kernel without any i8042 boot parameters to see whether you
can use both your touchpad and touchscreen again.

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

Title:
  Synaptics s3203 touchpad not working after update to kernel
  4.15.0-72-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  SRU justification
  =
  [Impact]
  Synaptics s3203 touchpad not working after update to kernel
  4.15.0-72-generic

  [Fix]
  After applied commit "Input: synaptics-rmi4 - avoid processing unknown
  IRQs",
  no irq response from touchpad.
  This commit is depended on commit:
  "Input: synaptics-rmi4 - convert irq distribution to irq_domain"

  [Test]
  Verified on hardware, tests results are good.

  [Regression Potential]
  Low.
  Fix bug that introduced by stable release update.

  2nd and 3rd patches are fixes for the 1st patch.
  These commits are already included by eoan kernel, so bionic 4.15 only.

  Original reports
  ===

  environment:
  Dell Laptop XPS-9333
  Device:
  # xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SYNAPTICS Synaptics Large Touch Screen  id=9[slave  pointer 
 (2)]
  ⎜   ↳ Synaptics s3203 id=12   [slave  pointer 
 (2)]
  ⎜   ↳ Ultrathin Touch Mouse   id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=13   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=14   [slave  
keyboard (3)]
  ↳ Integrated_Webcam_HD: Integrate id=10   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]

  # xinput --list-props 12
  Device 'Synaptics s3203':
   Device Enabled (142):1
   Coordinate Transformation Matrix (144):  1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
   Device Accel Profile (270):  1
   Device Accel Constant Deceleration (271):2.50
   Device Accel Adaptive Deceleration (272):1.00
   Device Accel Velocity Scaling (273): 9.712231
   Synaptics Edges (304):   162, 3908, 133, 2339
   Synaptics Finger (305):  25, 30, 0
   Synaptics Tap Time (306):180
   Synaptics Tap Move (307):209
   Synaptics Tap Durations (308):   180, 180, 100
   Synaptics ClickPad (309):1
   Synaptics Middle Button Timeout (310):   0
   Synaptics Two-Finger Pressure (311): 282
   Synaptics Two-Finger Width (312):7
   Synaptics Scrolling Distance (313):  -95, 95
   Synaptics Edge Scrolling (314):  0, 0, 0
   Synaptics Two-Finger Scrolling (315):1, 1
   Synaptics Move Speed (316):  1.00, 1.75, 0.042008, 0.00
   Synaptics Off (317): 0
   Synaptics Locked Drags (318):0
   Synaptics Locked Drags Timeout (319):5000
   Synaptics Tap Action (320):  0, 0, 0, 0, 1, 3, 2
   Synaptics Click Action (321):1, 3, 2
   Synaptics Circular Scrolling (322):  0
   Synaptics Circular Scrolling Distance (323): 0.10
   Synaptics Circular Scrolling Trigger (324):  0
   Synaptics Circular Pad (325):0
   Synaptics Palm Detection (326):  1
   Synaptics Palm Dimensions (327): 10, 200
   Synaptics Coasting Speed (328):  20.00, 50.00
   Synaptics Pressure Motion (329): 30, 160
   Synaptics Pressure Motion Factor (330):  1.00, 1.00
   Synaptics Resolution Detect (331):   1
   Synaptics Grab Event Device (332):   0
   Synaptics Gestures (333):1
   Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0
   Synaptics Pad Resolution (335):  42, 42
   Synaptics Area (336):0, 0, 0, 0
   Synaptics Soft Button Areas (337):   0, 0, 0, 0, 0, 0, 0, 0
   Synaptics Noise Cancellation (338):  23, 23
   Device Product ID (262): 1739, 10036
   Device Node (263):   "/dev/input/event5"

  # lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 09)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev

[Kernel-packages] [Bug 1856079] Re: Fix Realtek Bluetooth firmware download

** Changed in: linux (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/1856079

Title:
  Fix Realtek Bluetooth firmware download

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix

Bug description:
  [Impact]
  Realtek Bluetooth controller failed to download firmware larger than 32K.

  [Fix]
  Update btrtl firmware downloading logic to match the hardware behavior.

  [Test]
  Several cold boots to force load firmware, and it never fails after the fix.

  [Regression Potential]
  Low. It's a trivial fix and we've verified it.

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

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

[Kernel-packages] [Bug 1857409] Re: alsa/sof: load different firmware on different platforms

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

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

Title:
  alsa/sof: load different firmware on different platforms

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Confirmed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Confirmed

Bug description:
  [Impact]
  In our ubuntu kernel, the sof driver will load the sof-cnl.ri (firmware)
  on all platforms, but mainline kernel already supported the multi
  firmwares on differnt platforms, and OEM project needs us to
  support the mutli-firmware names in the ubuntu kernel

  [Fix]
  cherry-pick 3 upstream patches, then on cnl platforms, it will
  load sof-cnl.ri, on cml platfomrs, it will load sof-cml.ri, on cfl
  platforms, it will load sof-cfl.ri

  
  [Test Case]
  Prepare the firmware from https://github.com/thesofproject/linux-firmware
  master branch, then boot the kernel with these patches.

  [Regression Risk]
  Low, just let different platforms load differnt firmware, and these
  patches are in the upstream kernel.

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

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

[Kernel-packages] [Bug 1857496] Re: usb-audio: the mic can't record any sound after resume on Dell Dock WD19

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

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

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

Title:
  usb-audio: the mic can't record any sound after resume on Dell Dock
  WD19

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  There is a heaset jack on the dock, after resume, the mic on that jack
  can't record sound anymore, need to close the recording app then reopen
  that app to workaround this issue.

  [Fix]
  set the interface and EP, then the mic can record sound again.

  
  [Test Case]
  test the kernel with this patch, the mic can record sound after resume.

  [Regression Risk]
  Low, this quirk is specific to WD19 (usb vednor and device id).

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

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

[Kernel-packages] [Bug 1850540] Re: multi-zone raid0 corruption

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

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

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

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

Title:
  multi-zone raid0 corruption

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mdadm package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  New
Status in mdadm source package in Precise:
  New
Status in linux source package in Trusty:
  Confirmed
Status in mdadm source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in mdadm source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in mdadm source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in mdadm source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in mdadm source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Confirmed
Status in mdadm source package in Focal:
  Fix Released
Status in mdadm package in Debian:
  Fix Released

Bug description:
  Bug 1849682 tracks the temporarily revert of the fix for this issue,
  while this bug tracks the re-application of that fix once we have a
  full solution.

  [Impact]
  (cut & paste from https://marc.info/?l=linux-raid=157360088014027=2)
  An unintentional RAID0 layout change was introduced in the v3.14 kernel. This 
effectively means there are 2 different layouts Linux will use to write data to 
RAID0 arrays in the wild - the “pre-3.14” way and the “3.14 and later” way. 
Mixing these layouts by writing to an array while booted on these different 
kernel versions can lead to corruption.

  Note that this only impacts RAID0 arrays that include devices of
  different sizes. If your devices are all the same size, both layouts
  are equivalent, and your array is not at risk of corruption due to
  this issue.

  Unfortunately, the kernel cannot detect which layout was used for
  writes to pre-existing arrays, and therefore requires input from the
  administrator. This input can be provided via the kernel command line
  with the raid0.default_layout= parameter, or by setting the
  default_layout module parameter when loading the raid0 module. With a
  new enough version of mdadm (>= 4.2, or equivalent distro backports),
  you can set the layout version when assembling a stopped array. For
  example:

  mdadm --stop /dev/md0
  mdadm --assemble -U layout-alternate /dev/md0 /dev/sda1 /dev/sda2
  See the mdadm manpage for more details. Once set in this manner, the layout 
will be recorded in the array and will not need to be explicitly specified in 
the future.

  (The mdadm part of this SRU is for the above support ^)

  [Test Case]
  = mdadm =
  Confirm that a multi-zone raid0 created w/ older mdadm is able to be started 
on a fixed kernel by setting a layout.
  1) Ex: w/ old kernel/mdadm:
    mdadm --create /dev/md0 --run --metadata=default \
  --level=0 --raid-devices=2 /dev/vdb1 /dev/vdc1
  2) Reboot onto fixed kernel & update mdadm
  3) sudo mdadm --stop /dev/md0 &&
     sudo mdadm --assemble -U layout-alternate \
   /dev/md0 /dev/vdb1 /dev/vdc1
  4) Confirm that the array autostarts on reboot
  5) Confirm that w/ new kernel & new mdadm, a user can create and start an 
array in a backwards-compatible fashion (i.e. w/o an explicit layout).
  6) Verify that 'mdadm --detail /dev/md0' displays the layout

  = linux =
  Similar to above, but using kernel command line options.

  [Regression Risk]
  The kernel side of things will break starting pre-existing arrays. That's 
intentional.

  The mdadm side will cause a regression in functionality where a user
  can no longer create multi-zone raid0s on kernels that do not yet have
  the raid0 layout patches. This is intentional, as such RAID arrays
  present a corruption risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1850540/+subscriptions

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

[Kernel-packages] [Bug 1854831] Re: xenial/linux-snapdragon: 4.4.0-1131.139 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


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

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

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

Title:
  xenial/linux-snapdragon: 4.4.0-1131.139 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 12:08 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1854830
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854831/+subscriptions

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

[Kernel-packages] [Bug 1856203] Re: xenial/linux-azure: 4.15.0-1066.71 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


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

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

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

Title:
  xenial/linux-azure: 4.15.0-1066.71 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: '1856749'
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 12:08 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
trusty/linux-azure: bug 1856202
xenial/linux-azure/azure-kernel: bug 1856199
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856203/+subscriptions

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

[Kernel-packages] [Bug 1856976] Re: xenial/linux-gcp: 4.15.0-1052.56 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


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

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

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

Title:
  xenial/linux-gcp: 4.15.0-1052.56 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  kernel-stable-master-bug: 1856749
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 12:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
xenial/linux-gcp/gcp-kernel: bug 1856973
xenial/linux-gcp/gke-kernel: bug 1856974
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856976/+subscriptions

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

[Kernel-packages] [Bug 1854807] Re: xenial/linux-oracle: 4.15.0-1031.34~16.04.1 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


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

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

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

Title:
  xenial/linux-oracle: 4.15.0-1031.34~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854808
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 11:59 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854807/+subscriptions

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

[Kernel-packages] [Bug 1857409] Re: alsa/sof: load different firmware on different platforms

** Changed in: linux-oem-osp1 (Ubuntu Bionic)
   Importance: Undecided => Critical

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

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

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

Title:
  alsa/sof: load different firmware on different platforms

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Confirmed
Status in linux source package in Eoan:
  Confirmed
Status in linux source package in Focal:
  Confirmed

Bug description:
  [Impact]
  In our ubuntu kernel, the sof driver will load the sof-cnl.ri (firmware)
  on all platforms, but mainline kernel already supported the multi
  firmwares on differnt platforms, and OEM project needs us to
  support the mutli-firmware names in the ubuntu kernel

  [Fix]
  cherry-pick 3 upstream patches, then on cnl platforms, it will
  load sof-cnl.ri, on cml platfomrs, it will load sof-cml.ri, on cfl
  platforms, it will load sof-cfl.ri

  
  [Test Case]
  Prepare the firmware from https://github.com/thesofproject/linux-firmware
  master branch, then boot the kernel with these patches.

  [Regression Risk]
  Low, just let different platforms load differnt firmware, and these
  patches are in the upstream kernel.

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

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

[Kernel-packages] [Bug 1855409] Re: qede driver causes 100% CPU load

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

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

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

Title:
  qede driver causes 100% CPU load

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]

  * The PTP feature in qede driver is implemented in a way that if the
  NIC firmware takes some time to perform the timestamping then the PTP
  worker function will reschedule itself indefinitely until the value
  read from a device register is meaningful. With that behavior, if an
  userspace tool requests a bad configured TX/RX filter (or if NIC
  firmware has any other issue in timestamping), the function
  qede_ptp_task() will reschedule itself forever and cause an unbound
  resource consumption. This manifests as a kworker thread consuming
  100% of CPU.

  * The dmesg log will show a message like this:
  "qede_ptp_tx_ts:533(eno3)]Timestamping in progress"

  Also, by using perf user can observe a stack like the following:
  - 44.76% 0.00% kworker/16:5 [kernel.kallsyms]
   ret_from_fork
 - kthread
- 44.74% worker_thread
   - 44.57% process_one_work
  - 42.67% qede_ptp_task
 - 38.86% qed_ptp_hw_read_tx_ts
  qed_rd
 - 3.03% queue_work_on
- 2.06% __queue_work
   - 0.68% get_work_pool
  - 0.61% radix_tree_lookup
   __radix_tree_lookup
0.50% set_work_pool_and_clear_pending

  * The patch proposed in this SRU request refactors the PTP worked in
  qede by adding a time limit, after which the task doesn't reschedule
  itself anymore, failing the timestamp procedure: 9adebac37e7d ("qede:
  Handle infinite driver spinning for Tx timestamp.")
  http://git.kernel.org/linus/9adebac37e7d

  Besides fixing the issue, it also adds an ethtool statistics for
  accounting the PTP errors.

  [Test case]

  By using chrony in Bionic, the following steps will reproduce the
  issue:

  a) Install chrony on Bionic in a system with working NIC managed by qede;
  b) Edit chrony configuration and add: "hwtimestamp *" to the top of its conf 
file;
  c) Restart chrony service

  Check dmesg for the "[...]Timestamping in progress" message and the
  overall CPU workload using a tool like "top" to observe a kthread
  consuming 100% of CPU.

  [Regression potential]

  The patch scope is restricted to qede PTP handler, and is upstream for
  more than 7 months. If there's any possibility of regressions, the
  worst would be an issue affecting the packet timestamping, not messing
  with the regular xmit path of the driver.

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

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

[Kernel-packages] [Bug 1854824] Re: xenial/linux-aws: 4.4.0-1100.111 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


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

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

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

Title:
  xenial/linux-aws: 4.4.0-1100.111 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 11:53 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
xenial/linux-aws/aws-kernel: bug 1854823
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854824/+subscriptions

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

[Kernel-packages] [Bug 1855409] Re: qede driver causes 100% CPU load

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

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

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

Title:
  qede driver causes 100% CPU load

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]

  * The PTP feature in qede driver is implemented in a way that if the
  NIC firmware takes some time to perform the timestamping then the PTP
  worker function will reschedule itself indefinitely until the value
  read from a device register is meaningful. With that behavior, if an
  userspace tool requests a bad configured TX/RX filter (or if NIC
  firmware has any other issue in timestamping), the function
  qede_ptp_task() will reschedule itself forever and cause an unbound
  resource consumption. This manifests as a kworker thread consuming
  100% of CPU.

  * The dmesg log will show a message like this:
  "qede_ptp_tx_ts:533(eno3)]Timestamping in progress"

  Also, by using perf user can observe a stack like the following:
  - 44.76% 0.00% kworker/16:5 [kernel.kallsyms]
   ret_from_fork
 - kthread
- 44.74% worker_thread
   - 44.57% process_one_work
  - 42.67% qede_ptp_task
 - 38.86% qed_ptp_hw_read_tx_ts
  qed_rd
 - 3.03% queue_work_on
- 2.06% __queue_work
   - 0.68% get_work_pool
  - 0.61% radix_tree_lookup
   __radix_tree_lookup
0.50% set_work_pool_and_clear_pending

  * The patch proposed in this SRU request refactors the PTP worked in
  qede by adding a time limit, after which the task doesn't reschedule
  itself anymore, failing the timestamp procedure: 9adebac37e7d ("qede:
  Handle infinite driver spinning for Tx timestamp.")
  http://git.kernel.org/linus/9adebac37e7d

  Besides fixing the issue, it also adds an ethtool statistics for
  accounting the PTP errors.

  [Test case]

  By using chrony in Bionic, the following steps will reproduce the
  issue:

  a) Install chrony on Bionic in a system with working NIC managed by qede;
  b) Edit chrony configuration and add: "hwtimestamp *" to the top of its conf 
file;
  c) Restart chrony service

  Check dmesg for the "[...]Timestamping in progress" message and the
  overall CPU workload using a tool like "top" to observe a kthread
  consuming 100% of CPU.

  [Regression potential]

  The patch scope is restricted to qede PTP handler, and is upstream for
  more than 7 months. If there's any possibility of regressions, the
  worst would be an issue affecting the packet timestamping, not messing
  with the regular xmit path of the driver.

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

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

[Kernel-packages] [Bug 1855990] Re: linux-raspi2: dmesg prints calltrace when continuous memory allocation fails

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

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

Title:
  linux-raspi2: dmesg prints calltrace when continuous memory allocation
  fails

Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  When booting our raspi2 eoan kernel on rpi2/3/4, the dmesg sometimes
  prints calltrace, that is because the fb driver fails to allocate memory
  from cma, this is not critical since the fb driver could handle the
  failure of allocation.

  [Fix]
  Disable the warning, then the calltrace will not be printed out.

  [Test Case]
  Booting the kernel with high resolution moinitor, the fb drver print the
  log about failure of allocation, but there is no calltrace anymore.

  [Regression Risk]
  Low, just disable a warning.

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

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

[Kernel-packages] [Bug 1854826] Re: xenial/linux-kvm: 4.4.0-1064.71 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


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

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

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

Title:
  xenial/linux-kvm: 4.4.0-1064.71 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 11:54 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854826/+subscriptions

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

[Kernel-packages] [Bug 1855990] Re: linux-raspi2: dmesg prints calltrace when continuous memory allocation fails

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

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

Title:
  linux-raspi2: dmesg prints calltrace when continuous memory allocation
  fails

Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  When booting our raspi2 eoan kernel on rpi2/3/4, the dmesg sometimes
  prints calltrace, that is because the fb driver fails to allocate memory
  from cma, this is not critical since the fb driver could handle the
  failure of allocation.

  [Fix]
  Disable the warning, then the calltrace will not be printed out.

  [Test Case]
  Booting the kernel with high resolution moinitor, the fb drver print the
  log about failure of allocation, but there is no calltrace anymore.

  [Regression Risk]
  Low, just disable a warning.

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

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

[Kernel-packages] [Bug 1854829] Re: xenial/linux-raspi2: 4.4.0-1127.136 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


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

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

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

Title:
  xenial/linux-raspi2: 4.4.0-1127.136 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 11:54 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1854828
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854829/+subscriptions

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

[Kernel-packages] [Bug 1856079] Re: Fix Realtek Bluetooth firmware download

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

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

Title:
  Fix Realtek Bluetooth firmware download

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  New
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix

Bug description:
  [Impact]
  Realtek Bluetooth controller failed to download firmware larger than 32K.

  [Fix]
  Update btrtl firmware downloading logic to match the hardware behavior.

  [Test]
  Several cold boots to force load firmware, and it never fails after the fix.

  [Regression Potential]
  Low. It's a trivial fix and we've verified it.

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

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

[Kernel-packages] [Bug 1855990] Re: linux-raspi2: dmesg prints calltrace when continuous memory allocation fails

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

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

Title:
  linux-raspi2: dmesg prints calltrace when continuous memory allocation
  fails

Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  When booting our raspi2 eoan kernel on rpi2/3/4, the dmesg sometimes
  prints calltrace, that is because the fb driver fails to allocate memory
  from cma, this is not critical since the fb driver could handle the
  failure of allocation.

  [Fix]
  Disable the warning, then the calltrace will not be printed out.

  [Test Case]
  Booting the kernel with high resolution moinitor, the fb drver print the
  log about failure of allocation, but there is no calltrace anymore.

  [Regression Risk]
  Low, just disable a warning.

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

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

[Kernel-packages] [Bug 1854835] Re: xenial/linux: 4.4.0-171.200 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


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

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

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

Title:
  xenial/linux: 4.4.0-171.200 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 11:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
trusty/linux-aws: bug 1854833
trusty/linux-lts-xenial: bug 1854834
unknown/unknown: bug 1854820
xenial/linux-aws: bug 1854824
xenial/linux-cascade: bug 1854825
xenial/linux-fips: bug 1854832
xenial/linux-kvm: bug 1854826
xenial/linux-raspi2: bug 1854829
xenial/linux-snapdragon: bug 1854831
xenial/linux/caracalla-kernel: bug 1854820
xenial/linux/pc-kernel: bug 1854821
xenial/linux/stlouis-kernel: bug 1854822
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854835/+subscriptions

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

[Kernel-packages] [Bug 1857496] Re: usb-audio: the mic can't record any sound after resume on Dell Dock WD19

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

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

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

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

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

Title:
  usb-audio: the mic can't record any sound after resume on Dell Dock
  WD19

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  In Progress

Bug description:
  [Impact]
  There is a heaset jack on the dock, after resume, the mic on that jack
  can't record sound anymore, need to close the recording app then reopen
  that app to workaround this issue.

  [Fix]
  set the interface and EP, then the mic can record sound again.

  
  [Test Case]
  test the kernel with this patch, the mic can record sound after resume.

  [Regression Risk]
  Low, this quirk is specific to WD19 (usb vednor and device id).

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

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

[Kernel-packages] [Bug 1851340] Re: [mgag200] Ubuntu 19.10 upgrade results in invisible mouse cursor on Matrox G200eR2

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

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

Title:
  [mgag200] Ubuntu 19.10 upgrade results in invisible mouse cursor on
  Matrox G200eR2

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

Bug description:
  == SRU Justification ==
  The cursor on Matrox G200eR2 will disappear after upgrading kernel from
  Disco to Eoan, this is caused by this commit that got applied in Eoan:
  4dc57b10 (drm/mgag200: Rewrite cursor handling)

  == Fix ==
  * a9c342ab (drm/mgag200: Don't unpin the current cursor image's buffer.)
  * cf578c8c (drm/mgag200: Set cursor scanout address to correct BO)
  * e61576c4 (drm/mgag200: add in missing { } around if block)
  * a0fd72d2 (drm/mgag200: Pin displayed cursor BO to video memory)

  Focal got these patches already and it does not have this issue.

  == Test ==
  Test kernel could be found here:
    https://people.canonical.com/~phlin/kernel/lp-1851340-mgag200-cursor/

  Verified by the bug reporter, John Hartley, the patched kernel can fix
  this issue.

  == Regression Potential ==
  Low, change limited to mgag200 cursor itself, and it's already been
  applied on newer releases.


  == Original Bug Report ==
  Following in place upgrade of Ubuntu 19.04 -> 19.10 I no longer have visible 
cursor with my Gnone desktop.

  I have found the same problem when upgrading 2 machines from Ubuntu
  19.04 -> 19.10.

  Reproducing problem is easy:

  1. Open Ubuntu Update Window
  2. Select "Upgrade"
  3. On completion of update (after reboot) cursor is no longer visible.
  4. This applies to display connected to VGA port on host with USB Keyboard + 
Mouse

  While the connected display has no visible cursor and so is usable, I
  have always used X11VNC Server to provide network GUI access. On the
  remote X11VNC display I see and can use the cursor.

  This bug report is being sent via Remote X11VNC window, as I cannot
  use the main VGA display window (due to lack of visible cursor)

  I have done search online and thought that maybe issue was with my USB
  Mighty Mouse, so I also tried with Logitech M100R USB Mouse. Same
  result, no visible mouse cursor.

  I have done: "grep usb /var/log/syslog" and can see many USB events,
  including both Apple and Logitech mouse detection events.

  NOTE:

  Due to compatibility issue with X11VNC, I have disable Wayland on both
  machines by adding the following option to: /etc/gdm3/custom.conf

  WaylandEnable=false

  Regards,

  John Hartley.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 18:25:23 2019
  DistUpgraded: 2019-11-05 15:20:04,402 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   Matrox Electronics Systems Ltd. G200eR2 [102b:0534] (rev 01) (prog-if 00 
[VGA controller])
     Subsystem: Lenovo G200eR2 [1d49:0a01]
  InstallationDate: Installed on 2018-12-17 (322 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO System x3650 M5: -[8871AC1]-
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=3b8f415b-7e78-461c-83df-64f1f1a7826a ro ipv6.disable=1 quiet splash 
iommu=1 intel_iommu=on ipv6.disable=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago)
  dmi.bios.date: 06/03/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: -[TCE140H-2.91]-
  dmi.board.asset.tag: (none)
  dmi.board.name: 01KN179
  dmi.board.vendor: LENOVO
  dmi.board.version: NULL
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: none
  dmi.modalias: 
dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone:
  dmi.product.family: System X
  dmi.product.name: System x3650 M5: -[8871AC1]-
  dmi.product.sku: (none)
  dmi.product.version: 13
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati:

[Kernel-packages] [Bug 1857541] Re: [SRU][B/OEM-B/OEM-OSP1/D/E/F] Add LG I2C touchscreen multitouch support

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
 Assignee: AaronMa (mapengyu)
   Status: Triaged

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

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

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

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

Title:
  [SRU][B/OEM-B/OEM-OSP1/D/E/F] Add LG I2C touchscreen multitouch
  support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in linux source package in Eoan:
  New
Status in linux source package in Focal:
  Triaged

Bug description:
  SRU justification:

  [Impact]
  The current kernel didn't support multitouch for LG I2C touchscreen.

  [Fix]
  Add LG I2C id to hid-multitouch to support it.

  [Test]
  Verified on hardware with a positive result.

  [Regression Potential]
  Low.
  Add new I2C id with positive verification.

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

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

[Kernel-packages] [Bug 1856749] Re: bionic/linux: 4.15.0-74.84 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
- phase: Promote to Security
- phase-changed: Tuesday, 07. January 2020 10:36 UTC
+ phase: Complete
+ phase-changed: Tuesday, 07. January 2020 12:27 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-security: Ongoing -- packages not yet published
  trackers:
bionic/linux-aws: bug 1854802
bionic/linux-fips: bug 1854809
bionic/linux-gke-4.15: bug 1854804
bionic/linux-ibm-gt: bug 1854806
bionic/linux-kvm: bug 1854805
bionic/linux-oem: bug 1854797
bionic/linux-oracle: bug 1854808
bionic/linux-raspi2: bug 1854793
bionic/linux-snapdragon: bug 1854796
bionic/linux/pc-kernel: bug 1856747
bionic/linux/pc-lowlatency-kernel: bug 1856748
xenial/linux-azure: bug 1856203
xenial/linux-gcp: bug 1856976
xenial/linux-hwe: bug 1856804
  variant: debs

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

Title:
  bionic/linux: 4.15.0-74.84 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 12:27 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
bionic/linux-aws: bug 1854802
bionic/linux-fips: bug 1854809
bionic/linux-gke-4.15: bug 1854804
bionic/linux-ibm-gt: bug 1854806
bionic/linux-kvm: bug 1854805
bionic/linux-oem: bug 1854797
bionic/linux-oracle: bug 1854808
bionic/linux-raspi2: bug 1854793
bionic/linux-snapdragon: bug 1854796
bionic/linux/pc-kernel: bug 1856747
bionic/linux/pc-lowlatency-kernel: bug 1856748
xenial/linux-azure: bug 1856203
xenial/linux-gcp: bug 1856976
xenial/linux-hwe: bug 1856804
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856749/+subscriptions

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

[Kernel-packages] [Bug 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container

2020-01-07 Thread Adrian

Replying to Andrew Vagin's comment: This patch references the bug you
mentioned:

https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/bionic/commit/?h=hwe=5613773b6f576de155c39a7b7a04e45f9f6eaf46

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

Title:
linux-image-5.0.0-35-generic breaks checkpointing of container

Status in linux package in Ubuntu:
Confirmed

Bug description:
Trying to checkpoint a container (docker/podman) on 18.04 fails
starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see
this in Travis starting a few weeks ago. Manually testing it locally
shows that linux-image-5.0.0-32-generic still works and linux-
image-5.0.0-35-generic does not longer work. It seems to be overlayfs
related, at least that is what we believe. The CRIU error message we
see is:

(00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3
path=/bin/busybox
(00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed
with -1

We have not seen this only in Travis, but also multiple CRIU users reported
that bug already. Currently we have to tell them to downgrade the kernel.

I also able to reproduce it with linux-image-5.3.0-24-generic. Staying
on the 4.18.0 kernel series does not show this error.
4.18.0-25-generic works without problems.

See also https://github.com/checkpoint-restore/criu/issues/860

One of the possible explanations from our side include:

"Looks like we have the same as for st_dev now with mnt_id, that is
bad, because we can't find on which mount to open the file if kernel
hides these information from us."

Running on the upstream 5.5.0-rc1 kernel does not show this error.

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

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

[Kernel-packages] [Bug 1854808] Re: bionic/linux-oracle: 4.15.0-1031.34 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: '1856749'
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
- phase: Promote to Security
- phase-changed: Tuesday, 07. January 2020 12:17 UTC
+ phase: Complete
+ phase-changed: Tuesday, 07. January 2020 12:27 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-security: Ongoing -- packages not yet published
  trackers:
unknown/unknown: bug 1854807
xenial/linux-oracle: bug 1854807
  variant: debs

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

Title:
  bionic/linux-oracle: 4.15.0-1031.34 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-oracle source package in Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: '1856749'
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 12:27 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
unknown/unknown: bug 1854807
xenial/linux-oracle: bug 1854807
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854808/+subscriptions

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

[Kernel-packages] [Bug 1854808] Re: bionic/linux-oracle: 4.15.0-1031.34 -proposed tracker

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: '1856749'
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
- phase: Ready for Promote to Security
- phase-changed: Tuesday, 07. January 2020 01:52 UTC
+ phase: Promote to Security
+ phase-changed: Tuesday, 07. January 2020 12:17 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Pending -- ready to copy
+   promote-to-security: Ongoing -- packages not yet published
  trackers:
unknown/unknown: bug 1854807
xenial/linux-oracle: bug 1854807
  variant: debs

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

Title:
  bionic/linux-oracle: 4.15.0-1031.34 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  In Progress
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-oracle source package in Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: '1856749'
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Promote to Security
  phase-changed: Tuesday, 07. January 2020 12:17 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Ongoing -- packages not yet published
  trackers:
unknown/unknown: bug 1854807
xenial/linux-oracle: bug 1854807
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854808/+subscriptions

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

[Kernel-packages] [Bug 1854808] Re: bionic/linux-oracle: 4.15.0-1031.34 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  bionic/linux-oracle: 4.15.0-1031.34 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  In Progress
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-oracle source package in Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: '1856749'
  packages:
lrm: linux-restricted-modules-oracle
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Promote to Security
  phase-changed: Tuesday, 07. January 2020 12:17 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Ongoing -- packages not yet published
  trackers:
unknown/unknown: bug 1854807
xenial/linux-oracle: bug 1854807
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854808/+subscriptions

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

[Kernel-packages] [Bug 1798400]

2020-01-07 Thread Kilasa4010

Can confirm that my samsung galaxy running Android 9 and linux mint 19.3
are still not working appropriately with the impress remote. It refuses
to connect via bluetooth no matter what I do.

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

Title:
  [upstream] Regression: cannot use impress remote over bluetooth with
  ubuntu bionic

Status in LibreOffice:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in libreoffice package in Fedora:
  Unknown

Bug description:
  Trying to use the impress remote
  (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth
  with libreoffice over ubuntu bionic fails.

  The handset errors out that it cannot connect with Libreoffice on the
  computer even if the bluetooth adapter on the handset and on the
  computer are correctly paired.

  This does not seem to be an issue in the Libreoffice or in the impress
  remote code:

  - I have tested also past LibO versions
  - The Impress remote codebase has not changed recently

  This used to work on the same hardware (headset and laptop) with
  ubuntu 16.04.

  Hence the issue seems to be in a regression in the ubuntu bluetooth
  stack.

  To replicate:

  1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo
  or with the deb packages from the document fundation)

  2) Assure that your computer has bluetooth

  3) Install impress remote on an android handset (either from the play
  store of via fdroid)

  4) Assure that "remote control" is enabled in impress
  Tools>Options>Impress>General

  5) Pair the bluetooth adapters in the laptop and in the computer

  6) Open a presentation on the laptop

  7) Open the remote on the handset, got to the bluetooth pane see the
  computer there, touch it

  8) See the impress remote erroring out

  Most likely you will also get a bluetooth error on dmesg

  RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind:
  Address already in use (98)

  Same issue was reported for fedora

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct 17 16:57:29 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1769 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Notebook W740SU
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W740SU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:C2:C6:1A:28:71  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN 
RX bytes:245088 acl:15156 sco:0 events:1266 errors:0
TX bytes:15571 acl:402 sco:1 commands:131 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions

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

[Kernel-packages] [Bug 1854831] Re: xenial/linux-snapdragon: 4.4.0-1131.139 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
- phase: Ready for Promote to Security
- phase-changed: Tuesday, 07. January 2020 02:42 UTC
+ phase: Complete
+ phase-changed: Tuesday, 07. January 2020 12:08 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-security: Pending -- ready to copy
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1854830
  variant: debs

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

Title:
  xenial/linux-snapdragon: 4.4.0-1131.139 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 12:08 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1854830
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854831/+subscriptions

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

[Kernel-packages] [Bug 1856976] Re: xenial/linux-gcp: 4.15.0-1052.56 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1856749
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Ready for Promote to Security
- phase-changed: Tuesday, 07. January 2020 03:01 UTC
+ phase: Complete
+ phase-changed: Tuesday, 07. January 2020 12:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-security: Pending -- ready to copy
  trackers:
xenial/linux-gcp/gcp-kernel: bug 1856973
xenial/linux-gcp/gke-kernel: bug 1856974
  variant: debs

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

Title:
  xenial/linux-gcp: 4.15.0-1052.56 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  kernel-stable-master-bug: 1856749
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 12:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
xenial/linux-gcp/gcp-kernel: bug 1856973
xenial/linux-gcp/gke-kernel: bug 1856974
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856976/+subscriptions

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

[Kernel-packages] [Bug 1854770] Re: bionic/linux-azure: 5.0.0-1028.30~18.04.1 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


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

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

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

Title:
  bionic/linux-azure: 5.0.0-1028.30~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854771
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 10:59 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
bionic/linux-azure/azure-kernel: bug 1854769
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854770/+subscriptions

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

[Kernel-packages] [Bug 1856203] Re: xenial/linux-azure: 4.15.0-1066.71 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: '1856749'
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Ready for Promote to Security
- phase-changed: Tuesday, 07. January 2020 02:51 UTC
+ phase: Complete
+ phase-changed: Tuesday, 07. January 2020 12:08 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-security: Pending -- ready to copy
  trackers:
trusty/linux-azure: bug 1856202
xenial/linux-azure/azure-kernel: bug 1856199
  variant: debs

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

Title:
  xenial/linux-azure: 4.15.0-1066.71 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: '1856749'
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 12:08 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
trusty/linux-azure: bug 1856202
xenial/linux-azure/azure-kernel: bug 1856199
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856203/+subscriptions

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

[Kernel-packages] [Bug 1854807] Re: xenial/linux-oracle: 4.15.0-1031.34~16.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854808
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
- phase: Ready for Promote to Security
- phase-changed: Tuesday, 07. January 2020 02:42 UTC
+ phase: Complete
+ phase-changed: Tuesday, 07. January 2020 11:59 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-security: Pending -- ready to copy
  variant: debs

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

Title:
  xenial/linux-oracle: 4.15.0-1031.34~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854808
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 11:59 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854807/+subscriptions

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

[Kernel-packages] [Bug 1854824] Re: xenial/linux-aws: 4.4.0-1100.111 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-aws
meta: linux-meta-aws
- phase: Promote to Security
- phase-changed: Tuesday, 07. January 2020 11:44 UTC
+ phase: Complete
+ phase-changed: Tuesday, 07. January 2020 11:53 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-security: Ongoing -- packages not yet published
  trackers:
xenial/linux-aws/aws-kernel: bug 1854823
  variant: debs

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

Title:
  xenial/linux-aws: 4.4.0-1100.111 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 11:53 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
xenial/linux-aws/aws-kernel: bug 1854823
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854824/+subscriptions

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

[Kernel-packages] [Bug 1854805] Re: bionic/linux-kvm: 4.15.0-1052.52 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


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

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

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

Title:
  bionic/linux-kvm: 4.15.0-1052.52 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: '1856749'
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 10:48 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854805/+subscriptions

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

[Kernel-packages] [Bug 1854797] Re: bionic/linux-oem: 4.15.0-1066.76 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


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

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

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

Title:
  bionic/linux-oem: 4.15.0-1066.76 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: '1856749'
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 10:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854797/+subscriptions

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

[Kernel-packages] [Bug 1854796] Re: bionic/linux-snapdragon: 4.15.0-1070.77 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


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

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

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

Title:
  bionic/linux-snapdragon: 4.15.0-1070.77 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: '1856749'
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 10:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1854795
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854796/+subscriptions

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

[Kernel-packages] [Bug 1854793] Re: bionic/linux-raspi2: 4.15.0-1053.57 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


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

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

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

Title:
  bionic/linux-raspi2: 4.15.0-1053.57 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: '1856749'
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 10:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
bionic/linux-raspi2/pi-kernel: bug 1854792
unknown/unknown: bug 1854792
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854793/+subscriptions

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

[Kernel-packages] [Bug 1854802] Re: bionic/linux-aws: 4.15.0-1057.59 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


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

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

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

Title:
  bionic/linux-aws: 4.15.0-1057.59 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: '1856749'
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 10:46 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
bionic/linux-aws-fips: bug 1854800
bionic/linux-aws/aws-kernel: bug 1854799
xenial/linux-aws-hwe: bug 1854801
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854802/+subscriptions

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

[Kernel-packages] [Bug 1854826] Re: xenial/linux-kvm: 4.4.0-1064.71 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-kvm
meta: linux-meta-kvm
- phase: Ready for Promote to Security
- phase-changed: Tuesday, 07. January 2020 02:41 UTC
+ phase: Complete
+ phase-changed: Tuesday, 07. January 2020 11:54 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-security: Pending -- ready to copy
  variant: debs

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

Title:
  xenial/linux-kvm: 4.4.0-1064.71 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 11:54 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854826/+subscriptions

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

[Kernel-packages] [Bug 1856976] Re: xenial/linux-gcp: 4.15.0-1052.56 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  xenial/linux-gcp: 4.15.0-1052.56 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  In Progress
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  kernel-stable-master-bug: 1856749
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Ready for Promote to Security
  phase-changed: Tuesday, 07. January 2020 03:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Pending -- ready to copy
  trackers:
xenial/linux-gcp/gcp-kernel: bug 1856973
xenial/linux-gcp/gke-kernel: bug 1856974
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856976/+subscriptions

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

[Kernel-packages] [Bug 1854829] Re: xenial/linux-raspi2: 4.4.0-1127.136 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
- phase: Ready for Promote to Security
- phase-changed: Tuesday, 07. January 2020 02:41 UTC
+ phase: Complete
+ phase-changed: Tuesday, 07. January 2020 11:54 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-security: Pending -- ready to copy
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1854828
  variant: debs

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

Title:
  xenial/linux-raspi2: 4.4.0-1127.136 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 11:54 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1854828
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854829/+subscriptions

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

[Kernel-packages] [Bug 1856203] Re: xenial/linux-azure: 4.15.0-1066.71 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  xenial/linux-azure: 4.15.0-1066.71 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  In Progress
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: '1856749'
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Promote to Security
  phase-changed: Tuesday, 07. January 2020 02:51 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Pending -- ready to copy
  trackers:
trusty/linux-azure: bug 1856202
xenial/linux-azure/azure-kernel: bug 1856199
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856203/+subscriptions

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

[Kernel-packages] [Bug 1854831] Re: xenial/linux-snapdragon: 4.4.0-1131.139 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  xenial/linux-snapdragon: 4.4.0-1131.139 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  In Progress
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Ready for Promote to Security
  phase-changed: Tuesday, 07. January 2020 02:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Pending -- ready to copy
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1854830
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854831/+subscriptions

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

[Kernel-packages] [Bug 1858634] Re: focal/linux-5.4: -proposed tracker

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
-   https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+   https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  packages:
-   lrm: linux-restricted-modules-5.4
-   main: linux-5.4
-   meta: linux-meta-5.4
-   signed: linux-signed-5.4
+   lrm: linux-restricted-modules-5.4
+   main: linux-5.4
+   meta: linux-meta-5.4
+   signed: linux-signed-5.4
  phase: Ready for Packaging
  phase-changed: Tuesday, 07. January 2020 11:36 UTC
  reason:
-   prepare-package: Pending -- version not specified
- trackers:
-   focal/linux-oem-5.4: bug 1858633
+   prepare-package: Pending -- version not specified
  variant: debs

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

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

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Invalid

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

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

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

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

** Changed in: kernel-sru-workflow/promote-to-release
   Status: New => Invalid

** Changed in: kernel-sru-workflow/regression-testing
   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/1858634

Title:
  focal/linux-5.4:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-release series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid

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

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

  -- swm properties --
  packages:
    lrm: linux-restricted-modules-5.4
    main: linux-5.4
    meta: linux-meta-5.4
    signed: linux-signed-5.4
  phase: Ready for Packaging
  phase-changed: Tuesday, 07. January 2020 11:36 UTC
  reason:
    prepare-package: Pending -- version not specified
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858634/+subscriptions

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

[Kernel-packages] [Bug 1853989] Re: [roce-1126]RDMA/hns: bugfix for slab-out-of-bounds when loading hip08 driver

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

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

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

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

Title:
  [roce-1126]RDMA/hns: bugfix for slab-out-of-bounds when loading hip08
  driver

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04 series:
  In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Committed
Status in kunpeng920 ubuntu-19.04 series:
  In Progress
Status in kunpeng920 ubuntu-19.10 series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
KASAN reports slab-out-of-bounds in RDMA/hns driver

  [Testcase]
Enable KASAN and modprobe RDMA/hns driver

  [Regression Risk]
Only RDMA/hns driver modified. lowest risk to other drivers/platforms

  [Bug Description]
  KASAN: slab-out-of-bounds in hns_roce_table_mhop_put+0x584/0x828
  [hns_roce]
  Read of size 8 at addr 802185e08300 by task rmmod/270

  Call trace:
  dump_backtrace+0x0/0x1e8
  show_stack+0x14/0x20
  dump_stack+0xc4/0xfc
  print_address_description+0x60/0x270
  __kasan_report+0x164/0x1b8
  kasan_report+0xc/0x18
  __asan_load8+0x84/0xa8
  hns_roce_table_mhop_put+0x584/0x828 [hns_roce]
  hns_roce_table_put+0x174/0x1a0 [hns_roce]
  hns_roce_mr_free+0x124/0x210 [hns_roce]
  hns_roce_dereg_mr+0x90/0xb8 [hns_roce]
  ib_dealloc_pd_user+0x60/0xf0
  ib_mad_port_close+0x128/0x1d8
  ib_mad_remove_device+0x94/0x118
  remove_client_context+0xa0/0xe0
  disable_device+0xfc/0x1c0
  __ib_unregister_device+0x60/0xe0
  ib_unregister_device+0x24/0x38
  hns_roce_exit+0x3c/0x138 [hns_roce]
  __hns_roce_hw_v2_uninit_instance.isra.30+0x28/0x50 [hns_roce_hw_v2]
  hns_roce_hw_v2_uninit_instance+0x44/0x60 [hns_roce_hw_v2]
  hclge_uninit_client_instance+0x15c/0x238 [hclge]
  hnae3_uninit_client_instance+0x84/0xa8 [hnae3]
  hnae3_unregister_client+0x84/0x158 [hnae3]
  hns_roce_hw_v2_exit+0x14/0x20 [hns_roce_hw_v2]
  __arm64_sys_delete_module+0x20c/0x308
  el0_svc_handler+0xbc/0x210
  el0_svc+0x8/0xc

  Allocated by task 255:
  __kasan_kmalloc.isra.0+0xd0/0x180
  kasan_kmalloc+0xc/0x18
  __kmalloc+0x16c/0x328
  hns_roce_init_hem_table+0x20c/0x428 [hns_roce]
  hns_roce_init+0x214/0xfe0 [hns_roce]
  __hns_roce_hw_v2_init_instance+0x284/0x330 [hns_roce_hw_v2]
  hns_roce_hw_v2_init_instance+0xd0/0x1b8 [hns_roce_hw_v2]
  hclge_init_roce_client_instance+0x180/0x310 [hclge]
  hclge_init_client_instance+0xcc/0x508 [hclge]
  hnae3_init_client_instance.part.3+0x3c/0x80 [hnae3]
  hnae3_register_client+0x134/0x1a8 [hnae3]
  0x29c00014
  do_one_initcall+0x9c/0x3e0
  do_init_module+0xd4/0x2d8
  load_module+0x3284/0x3690
  __se_sys_init_module+0x274/0x308
  __arm64_sys_init_module+0x40/0x50
  el0_svc_handler+0xbc/0x210
  el0_svc+0x8/0xc

  Freed by task 0:
  (stack is not available)

  The buggy address belongs to the object at 802185e06300
  which belongs to the cache kmalloc-8k of size 8192
  The buggy address is located 0 bytes to the right of
  8192-byte region [802185e06300, 802185e08300)
  The buggy address belongs to the page:
  page:7fe008617800 refcount:1 mapcount:0 mapping:802340020e00 
index:0x0
  compound_mapcount: 0
  flags: 0x5fffe0010200(slab|head)
  raw: 5fffe0010200 dead0100 dead0200 802340020e00
  raw:  803e003e 0001 
  page dumped because: kasan: bad access detected
   Memory state around the buggy address:
  802185e08200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  802185e08280: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  >802185e08300: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
  ^
  802185e08380: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
  802185e08400: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  ==
  Disabling lock debugging due to kernel taint

  [Steps to Reproduce]
  Enable KASAN and configure PAGE_SIZE to 64K, insmod hns roce driver and then 
rmmod it.

  [Actual Results]
  Call trace because of slab-out-of-bound.

  [Expected Results]
  Success

  [Reproducibility]
  Inevitably

[Kernel-packages] [Bug 1854807] Re: xenial/linux-oracle: 4.15.0-1031.34~16.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  xenial/linux-oracle: 4.15.0-1031.34~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  In Progress
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854808
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Ready for Promote to Security
  phase-changed: Tuesday, 07. January 2020 02:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Pending -- ready to copy
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854807/+subscriptions

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

[Kernel-packages] [Bug 1854826] Re: xenial/linux-kvm: 4.4.0-1064.71 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  xenial/linux-kvm: 4.4.0-1064.71 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 11:54 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854826/+subscriptions

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

[Kernel-packages] [Bug 1853990] Re: [roce-1126]RDMA/hns: Fixs hw access invalid dma memory error

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

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

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

Title:
  [roce-1126]RDMA/hns: Fixs hw access invalid dma memory error

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04 series:
  In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Committed
Status in kunpeng920 ubuntu-19.04 series:
  In Progress
Status in kunpeng920 ubuntu-19.10 series:
  Fix Released
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [Impact]
With SMMU enabled, kill RDMA process will cause unexpected SMMU event

  [Testcase]
Kill RMDA process several times and check console output

  [Regression Risk]
Only RDMA/hns driver modified. lowest risk to other drivers/platforms


  [Bug Description]
  When smmu is enable, if execute the perftest command and then use 'kill
  -9' to exit, follow this operation repeatedly, the kernel will have a high
  probability to print the following smmu event:

    arm-smmu-v3 arm-smmu-v3.1.auto: event 0x10 received:
    arm-smmu-v3 arm-smmu-v3.1.auto:  0x7d10
    arm-smmu-v3 arm-smmu-v3.1.auto:  0x02090080
    arm-smmu-v3 arm-smmu-v3.1.auto:  0xf47cf000
    arm-smmu-v3 arm-smmu-v3.1.auto:  0xf47cf000

  This is because the hw will periodically refresh the qpc cache until the
  next reset.

  This patch fixed it by removing the action that release qpc memory in the
  'hns_roce_qp_free' function.

  [Steps to Reproduce]
  1. load hns-roce-hw-v2.ko and open smmu
  2. run rdma app
  3. kill RoCE process

  [Actual Results]
  fail

  [Expected Results]
  success

  [Reproducibility]
  Inevitably

  [Additional information]
  Hardware: D06
  Firmware: NA
  Kernel: NA

  [Resolution]
  RDMA/hns: Fixs hw access invalid dma memory error

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

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

[Kernel-packages] [Bug 1854824] Re: xenial/linux-aws: 4.4.0-1100.111 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  xenial/linux-aws: 4.4.0-1100.111 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 11:53 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
xenial/linux-aws/aws-kernel: bug 1854823
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854824/+subscriptions

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

[Kernel-packages] [Bug 1854829] Re: xenial/linux-raspi2: 4.4.0-1127.136 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  xenial/linux-raspi2: 4.4.0-1127.136 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 11:54 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1854828
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854829/+subscriptions

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

[Kernel-packages] [Bug 1854835] Re: xenial/linux: 4.4.0-171.200 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
- phase: Ready for Promote to Security
- phase-changed: Tuesday, 07. January 2020 02:32 UTC
+ phase: Complete
+ phase-changed: Tuesday, 07. January 2020 11:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
- reason:
-   promote-to-security: Pending -- ready to copy
  trackers:
trusty/linux-aws: bug 1854833
trusty/linux-lts-xenial: bug 1854834
unknown/unknown: bug 1854820
xenial/linux-aws: bug 1854824
xenial/linux-cascade: bug 1854825
xenial/linux-fips: bug 1854832
xenial/linux-kvm: bug 1854826
xenial/linux-raspi2: bug 1854829
xenial/linux-snapdragon: bug 1854831
xenial/linux/caracalla-kernel: bug 1854820
xenial/linux/pc-kernel: bug 1854821
xenial/linux/stlouis-kernel: bug 1854822
  variant: debs

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

Title:
  xenial/linux: 4.4.0-171.200 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 11:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
trusty/linux-aws: bug 1854833
trusty/linux-lts-xenial: bug 1854834
unknown/unknown: bug 1854820
xenial/linux-aws: bug 1854824
xenial/linux-cascade: bug 1854825
xenial/linux-fips: bug 1854832
xenial/linux-kvm: bug 1854826
xenial/linux-raspi2: bug 1854829
xenial/linux-snapdragon: bug 1854831
xenial/linux/caracalla-kernel: bug 1854820
xenial/linux/pc-kernel: bug 1854821
xenial/linux/stlouis-kernel: bug 1854822
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854835/+subscriptions

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

[Kernel-packages] [Bug 1854824] Re: xenial/linux-aws: 4.4.0-1100.111 -proposed tracker

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-aws
meta: linux-meta-aws
- phase: Ready for Promote to Security
- phase-changed: Tuesday, 07. January 2020 02:41 UTC
+ phase: Promote to Security
+ phase-changed: Tuesday, 07. January 2020 11:44 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Pending -- ready to copy
+   promote-to-security: Ongoing -- packages not yet published
  trackers:
xenial/linux-aws/aws-kernel: bug 1854823
  variant: debs

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

Title:
  xenial/linux-aws: 4.4.0-1100.111 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854835
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 11:53 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
xenial/linux-aws/aws-kernel: bug 1854823
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854824/+subscriptions

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

[Kernel-packages] [Bug 1853984] Re: [hns-1126]net: hns3: fix port setting handle for fibre port

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

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

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

Title:
  [hns-1126]net: hns3: fix port setting handle for fibre port

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04 series:
  Invalid
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Committed
Status in kunpeng920 ubuntu-19.04 series:
  In Progress
Status in kunpeng920 ubuntu-19.10 series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  For hardware doesn't support use specified speed and duplex
  to negotiate, it's unnecessary to check and modify the port
  speed and duplex for fibre port when autoneg is on.

  [Test Case]
  `sudo ethtool -s eno1 autoneg off speed 10 duplex full`
  `sudo ethtool -s eno1 autoneg on`
  commands shall return 0

  [Fix]
  24283ece5a0f net: hns3: fix port setting handle for fibre port

  [Regression Risk]
  Patch restricted to hns3 driver.

  "[Bug Description]
  For hardware doesn't support use specified speed and duplex
  to negotiate, it's unnecessary to check and modify the port
  speed and duplex for fibre port when autoneg is on.

  [Steps to Reproduce]
  1.ethtool -s eth* autoneg off speed 10 duplex full
  2.ethtool -s eth* autoneg on

  [Actual Results]
  set autoneg on fail

  [Expected Results]
  set autoneg on ok

  [Reproducibility]
  Inevitably

  [Additional information]
  Hardware: D06
  Firmware: NA
  Kernel: NA

  [Resolution]
  Not check and modify the port speed and duplex for fibre port when autoneg 
on."

  net: hns3: fix port setting handle for fibre port

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

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

[Kernel-packages] [Bug 1853983] Re: [hns-1126]net: hns3: revert to old channel when setting new channel num fail

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

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

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

Title:
  [hns-1126]net: hns3: revert to old channel when setting new channel
  num fail

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04 series:
  Won't Fix
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Committed
Status in kunpeng920 ubuntu-19.04 series:
  In Progress
Status in kunpeng920 ubuntu-19.10 series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  With specific ethtool commands, ethernet does not work

  [Test Case]
  run VF on VM with 3G memory and load VF driver
  ethtool -G eth0 tx 3 rx 3
  ethtool -G eth0 tx 24 rx 24；ethtool -L eth0 combined 1
  ethtool -G eth0 tx 32760 rx 32760
  ethtool -L eth0 combined 32
  ethernet shall still be functional after these commands

  [Fix]
  3a5a5f06d4d2 net: hns3: revert to old channel when setting new channel num 
fail

  [Regression Risk]
  Patch restricted to hns3 driver.

  "[Bug Description]
  After setting new channel num, it needs free old ring memory and
  allocate new ring memory. If there is no enough memory and allocate
  new ring memory fail, the ring may initialize fail. To make sure
  the network interface can work normally, driver should revert the
  channel to the old configuration.

  [Steps to Reproduce]
  1.run VF on VM with 3G memory
  2.load VF driver
  3.ethtool -G eth0 tx 3 rx 3
  4.ethtool -G eth0 tx 24 rx 24；ethtool -L eth0 combined 1
  5.ethtool -G eth0 tx 32760 rx 32760
  6.ethtool -L eth0 combined 32
  7.ping

  [Actual Results]
  netdevice can not work

  [Expected Results]
  ping ok

  [Reproducibility]
  Inevitably

  [Additional information]
  Hardware: D06
  Firmware: NA
  Kernel: NA

  [Resolution]
  Revert the channel to the old configuration when allocate new ring memory 
fail."

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

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

[Kernel-packages] [Bug 1858634] Re: focal/linux-5.4: -proposed tracker

** Summary changed:

- linux-5.4:  -proposed tracker
+ focal/linux-5.4:  -proposed tracker

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

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ packages:
+   lrm: linux-restricted-modules-5.4
+   main: linux-5.4
+   meta: linux-meta-5.4
+   signed: linux-signed-5.4
+ phase: Ready for Packaging
+ phase-changed: Tuesday, 07. January 2020 11:36 UTC
+ reason:
+   prepare-package: Pending -- version not specified
+ trackers:
+   focal/linux-oem-5.4: bug 1858633
  variant: debs

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

Title:
  focal/linux-5.4:  -proposed tracker

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

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

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

  -- swm properties --
  packages:
lrm: linux-restricted-modules-5.4
main: linux-5.4
meta: linux-meta-5.4
signed: linux-signed-5.4
  phase: Ready for Packaging
  phase-changed: Tuesday, 07. January 2020 11:36 UTC
  reason:
prepare-package: Pending -- version not specified
  trackers:
focal/linux-oem-5.4: bug 1858633
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858634/+subscriptions

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

[Kernel-packages] [Bug 1854835] Re: xenial/linux: 4.4.0-171.200 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-security
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  xenial/linux: 4.4.0-171.200 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Complete
  phase-changed: Tuesday, 07. January 2020 11:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  trackers:
trusty/linux-aws: bug 1854833
trusty/linux-lts-xenial: bug 1854834
unknown/unknown: bug 1854820
xenial/linux-aws: bug 1854824
xenial/linux-cascade: bug 1854825
xenial/linux-fips: bug 1854832
xenial/linux-kvm: bug 1854826
xenial/linux-raspi2: bug 1854829
xenial/linux-snapdragon: bug 1854831
xenial/linux/caracalla-kernel: bug 1854820
xenial/linux/pc-kernel: bug 1854821
xenial/linux/stlouis-kernel: bug 1854822
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854835/+subscriptions

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

[Kernel-packages] [Bug 1858634] [NEW] focal/linux-5.4: -proposed tracker