date:20200213

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

** This bug has been marked a duplicate of bug 1856539
   wireguard package doesn't work on ubuntu eon

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

Title:
  Wireguard install fails on 19.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  # apt install wireguard-tools
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
wireguard-dkms
  The following NEW packages will be installed:
wireguard-dkms wireguard-tools
  0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/330 kB of archives.
  After this operation, 2,126 kB of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  Selecting previously unselected package wireguard-dkms.
  (Reading database ... 298438 files and directories currently installed.)
  Preparing to unpack .../wireguard-dkms_0.0.20190913-1ubuntu1_all.deb ...
  Unpacking wireguard-dkms (0.0.20190913-1ubuntu1) ...
  Selecting previously unselected package wireguard-tools.
  Preparing to unpack .../wireguard-tools_0.0.20190913-1ubuntu1_amd64.deb ...
  Unpacking wireguard-tools (0.0.20190913-1ubuntu1) ...
  Setting up wireguard-dkms (0.0.20190913-1ubuntu1) ...
  Loading new wireguard-0.0.20190913 DKMS files...
  Building for 5.5.0-050500rc5-generic
  Building initial module for 5.5.0-050500rc5-generic
  ERROR (dkms apport): kernel package linux-headers-5.5.0-050500rc5-generic is 
not supported
  Error! Bad return status for module build on kernel: 5.5.0-050500rc5-generic 
(x86_64)
  Consult /var/lib/dkms/wireguard/0.0.20190913/build/make.log for more 
information.
  dpkg: error processing package wireguard-dkms (--configure):
   installed wireguard-dkms package post-installation script subprocess 
returned error exit status 10
  Setting up wireguard-tools (0.0.20190913-1ubuntu1) ...
  Processing triggers for man-db (2.8.7-3) ...
  Errors were encountered while processing:
   wireguard-dkms
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  

  make.log:
  -
  KMS make.log for wireguard-0.0.20190913 for kernel 5.5.0-050500rc5-generic 
(x86_64)
  Wed 08 Jan 2020 03:43:59 PM CET
  make: Entering directory '/usr/src/linux-headers-5.5.0-050500rc5-generic'
AR  /var/lib/dkms/wireguard/0.0.20190913/build/built-in.a
CC [M]  /var/lib/dkms/wireguard/0.0.20190913/build/main.o
CC [M]  /var/lib/dkms/wireguard/0.0.20190913/build/noise.o
CC [M]  /var/lib/dkms/wireguard/0.0.20190913/build/device.o
CC [M]  /var/lib/dkms/wireguard/0.0.20190913/build/peer.o
CC [M]  /var/lib/dkms/wireguard/0.0.20190913/build/timers.o
CC [M]  /var/lib/dkms/wireguard/0.0.20190913/build/queueing.o
CC [M]  /var/lib/dkms/wireguard/0.0.20190913/build/send.o
CC [M]  /var/lib/dkms/wireguard/0.0.20190913/build/receive.o
CC [M]  /var/lib/dkms/wireguard/0.0.20190913/build/socket.o
CC [M]  /var/lib/dkms/wireguard/0.0.20190913/build/peerlookup.o
CC [M]  /var/lib/dkms/wireguard/0.0.20190913/build/allowedips.o
CC [M]  /var/lib/dkms/wireguard/0.0.20190913/build/ratelimiter.o
CC [M]  /var/lib/dkms/wireguard/0.0.20190913/build/cookie.o
CC [M]  /var/lib/dkms/wireguard/0.0.20190913/build/netlink.o
CC [M]  
/var/lib/dkms/wireguard/0.0.20190913/build/crypto/zinc/chacha20/chacha20.o
PERLASM 
/var/lib/dkms/wireguard/0.0.20190913/build/crypto/zinc/chacha20/chacha20-x86_64.S
CC [M]  
/var/lib/dkms/wireguard/0.0.20190913/build/crypto/zinc/poly1305/poly1305.o
  /var/lib/dkms/wireguard/0.0.20190913/build/socket.c: In function ‘send6’:
  /var/lib/dkms/wireguard/0.0.20190913/build/socket.c:145:20: error: ‘const 
struct ipv6_stub’ has no member named ‘ipv6_dst_lookup’; did you mean 
‘ipv6_dst_lookup_flow’?
145 |   ret = ipv6_stub->ipv6_dst_lookup(sock_net(sock), sock, &dst,
|^~~
|ipv6_dst_lookup_flow
  make[1]: *** [scripts/Makefile.build:266: 
/var/lib/dkms/wireguard/0.0.20190913/build/socket.o] Error 1
  make[1]: *** Waiting for unfinished jobs
  /var/lib/dkms/wireguard/0.0.20190913/build/netlink.c: In function 
‘wg_get_device_start’:
  /var/lib/dkms/wireguard/0.0.20190913/build/netlink.c:199:26: error: implicit 
declaration of function ‘genl_family_attrbuf’ 
[-Werror=implicit-function-declaration]
199 |  struct nlattr **attrs = genl_family_attrbuf(&genl_family);
|  ^~~
  /var/lib/dkms/wireguard/0.0.20190913/build/netlink.c:199:26: warning: 
initialization of ‘struct nlattr **’ from ‘int’ makes pointer from integer 
without a cast [-Wint-conversion]
  cc1:

[Kernel-packages] [Bug 1851068] Re: laptop does not wakeup after suspend (when lid off). Need to had reset

What about using `systemctl suspend`?

Also I can't find any trace of Nvidia in the log.

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

Title:
  laptop does not wakeup after suspend (when lid off). Need to had reset

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When lid off. The laptop goes to unusual suspend mode. When raising
  the lid. Cannot turn laptop on. Cannot even log remotely using ssh.

  My laptop is hp spectre-15, i7-9750h with nvidia gtx 1650

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pm-utils 1.4.1-18
  Uname: Linux 5.4.0-050400rc5-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  2 16:14:29 2019
  InstallationDate: Installed on 2019-10-31 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dror   1529 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-31 (11 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP HP Spectre x360 Convertible 15t-df100
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-21-generic 
root=UUID=ad8d697c-17a2-4ab1-97ac-a1f665546354 ro acpi_osi=! "acpi_osi=Windows 
2015" nouveau.modeset=0
  ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-21-generic N/A
   linux-backports-modules-5.3.0-21-generic  N/A
   linux-firmware1.183.1
  Tags:  wayland-session eoan
  Uname: Linux 5.3.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/14/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 863E
  dmi.board.vendor: HP
  dmi.board.version: 53.23
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.11:bd10/14/2019:svnHP:pnHPSpectrex360Convertible15t-df100:pvr:rvnHP:rn863E:rvr53.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15t-df100
  dmi.product.sku: 5ZV29AV
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1856539] Re: wireguard package doesn't work on ubuntu eon

What's the output of `dkms status`?

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

Title:
  wireguard package doesn't work on ubuntu eon

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to ubuntu eon, i've tried to install wireguard.
  Install went well but wireguard module can't be loaded and so wireguard can't 
be used.

  Ubuntu version: 19.10
  Wireguard version: 0.0.20190913-1ubuntu1

  When trying to use wireguard:
  > sudo systemctl start wg-quick@wg0.service
  Job for wg-quick@wg0.service failed because the control process exited with 
error code.
  See "systemctl status wg-quick@wg0.service" and "journalctl -xe" for details.
  10:19:32 ~/ (feat/start-vm-choose-power-state u=)
  > systemctl status wg-quick@wg0.service
  ● wg-quick@wg0.service - WireGuard via wg-quick(8) for wg0
 Loaded: loaded (/lib/systemd/system/wg-quick@.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Mon 2019-12-16 10:19:32 CET; 5s 
ago
   Docs: man:wg-quick(8)
 man:wg(8)
 https://www.wireguard.com/
 https://www.wireguard.com/quickstart/
 https://git.zx2c4.com/WireGuard/about/src/tools/man/wg-quick.8
 https://git.zx2c4.com/WireGuard/about/src/tools/man/wg.8
Process: 31063 ExecStart=/usr/bin/wg-quick up wg0 (code=exited, 
status=1/FAILURE)
   Main PID: 31063 (code=exited, status=1/FAILURE)

  déc. 16 10:19:32 benjamin-XPS-13-9370 systemd[1]: Starting WireGuard via 
wg-quick(8) for wg0...
  déc. 16 10:19:32 benjamin-XPS-13-9370 wg-quick[31063]: Warning: 
`/etc/wireguard/wg0.conf' is world accessible
  déc. 16 10:19:32 benjamin-XPS-13-9370 wg-quick[31063]: [#] ip link add wg0 
type wireguard
  déc. 16 10:19:32 benjamin-XPS-13-9370 wg-quick[31063]: RTNETLINK answers: 
Operation not supported
  déc. 16 10:19:32 benjamin-XPS-13-9370 wg-quick[31063]: Unable to access 
interface: Protocol not supported
  déc. 16 10:19:32 benjamin-XPS-13-9370 wg-quick[31063]: [#] ip link delete dev 
wg0
  déc. 16 10:19:32 benjamin-XPS-13-9370 wg-quick[31063]: Cannot find device 
"wg0"
  déc. 16 10:19:32 benjamin-XPS-13-9370 systemd[1]: wg-quick@wg0.service: Main 
process exited, code=exited, status=1/FAILURE
  déc. 16 10:19:32 benjamin-XPS-13-9370 systemd[1]: wg-quick@wg0.service: 
Failed with result 'exit-code'.
  déc. 16 10:19:32 benjamin-XPS-13-9370 systemd[1]: Failed to start WireGuard 
via wg-quick(8) for wg0.

  
  When trying to load wireguard module:
  > sudo modprobe wireguard
  modprobe: ERROR: could not insert 'wireguard': Exec format error

  I'm happy to provide more info if needed.
  Any help would be greatly appreciated!

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

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

[Kernel-packages] [Bug 1851295] Re: dkms error with wireguard on upgrafe to 19.10

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

** This bug has been marked a duplicate of bug 1856539
   wireguard package doesn't work on ubuntu eon

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

Title:
  dkms error with wireguard on upgrafe to 19.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Loading new wireguard-0.0.20190913 DKMS files...
  Building for 5.0.0-27-generic 5.3.0-19-generic
  Building initial module for 5.0.0-27-generic
  ERROR (dkms apport): kernel package linux-headers-5.0.0-27-generic is not 
supported
  Error! Bad return status for module build on kernel: 5.0.0-27-generic (x86_64)
  Consult /var/lib/dkms/wireguard/0.0.20190913/build/make.log for more 
information.
  dpkg: error processing package wireguard-dkms (--configure):
   installed wireguard-dkms package post-installation script subprocess 
returned error exit status 10
  dpkg: dependency problems prevent configuration of wireguard:
   wireguard depends on wireguard-dkms (= 0.0.20190913-1ubuntu1) | 
wireguard-modules (= 0.0.20190913); however:
Package wireguard-dkms is not configured yet.
Package wireguard-modules is not installed.

  dpkg: error processing package wireguard (--configure):
   dependency problems - leaving unconfigured
  Errors were encountered while processing:
   wireguard-dkms
   wireguard

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: wireguard-dkms 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  NonfreeKernelModules: wireguard
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  Date: Mon Nov  4 23:58:10 2019
  ErrorMessage: installed wireguard-dkms package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2018-10-12 (388 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: wireguard
  Title: package wireguard-dkms 0.0.20190913-1ubuntu1 failed to 
install/upgrade: installed wireguard-dkms package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: Upgraded to eoan on 2019-11-04 (0 days ago)

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

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

[Kernel-packages] [Bug 1861925] Re: BrightnessOutofRange: Actual brightness for amdgpu_bl0 not in range 0..255

** Package changed: xserver-xorg-video-amdgpu (Ubuntu) => linux (Ubuntu)

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

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

Title:
  BrightnessOutofRange: Actual brightness for amdgpu_bl0 not in range
  0..255

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I have a acer aspire a315-41 laptop, it has BIOS 1.15, Ubuntu 19.10,
  Kernel stock 5.3, and 5.5.0. I have a problem with the Backlight. I
  can not control.

  According to: https://wiki.ubuntu.com/Kernel/Debugging/Backlight

  It is : Backlight control does not work, but there are entries in
  /sys/class/backlight.

  The problem is as far I could find:

  sanya@Aspire-A315-41:/sys/class/backlight/amdgpu_bl0$ cat brightness
  135
  sanya@Aspire-A315-41:/sys/class/backlight/amdgpu_bl0$ cat actual_brightness
  43500
  sanya@Aspire-A315-41:/sys/class/backlight/amdgpu_bl0$ cat max_brightness
  255

  The brightness read from the HW is not in the range, and when I change
  the brightness by the keys the value in the brightness file changes
  too, but the actual_brightness is stuck at the value 43500...

  I have tried all the steps mentioned in
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight

  Actually I have tried all these kernel startup parameter variants
  without luck:

  GRUB_CMDLINE_LINUX_DEFAULT=""
  #GRUB_CMDLINE_LINUX_DEFAULT="video.use_native_backlight=1"
  #GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi="
  #GRUB_CMDLINE_LINUX_DEFAULT="video.use_bios_initial_backlight=0"
  #GRUB_CMDLINE_LINUX_DEFAULT="amdgpu.dcfeaturemask=0x4 amdgpu.abmlevel=2"
  #GRUB_CMDLINE_LINUX_DEFAULT="acpi_backlight=video amdgpu.abmlevel=1"
  #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=Linux acpi_backlight=vendor"
  #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" 
acpi_backlight=vendor"
  #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" 
acpi_backlight=video"
  #GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=! acpi_osi=\"Windows 2009\" 
acpi_backlight=vendor"
  #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" 
acpi_backlight=vendor"
  #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" 
acpi_backlight=vendor"

  I guess the fwts has found also this as an error:

  autobrightness: Automated LCD brightness test.
  

  Test 1 of 2: Test for maximum and actual brightness.
  PASSED: Test 1, Maximum brightness for amdgpu_bl0 is 255 which is sane.
  FAILED [HIGH] BrightnessOutofRange: Test 1, Actual brightness for amdgpu_bl0 
not
  in range 0..255.

  Test 2 of 2: Change actual brightness.
  FAILED [MEDIUM] BrightnessMismatch: Test 2, 256 brightness levels did not 
match
  the brightnesss level just set for backlight amdgpu_bl0.
  The failed brightness levels were: 0-255.

  It would be great if someone could help set the HW brightness back to
  the normal range.

  If you need any more debug files please let me know!

  Thanks,
  Regards,
  Sandor

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

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

[Kernel-packages] [Bug 1861300] Re: Data Corruption with Sil 3114 and 3124 controlleurs

2020-02-13 Thread xenoxis

I can't, cause I get the error "No REFERER Header", i'm using Lynx cause
i'm running SSH console on the server, so there's no X11 server to run a
better web browser.

How could I get logs ? Even if there's no error about data corruption in
linux logs ? Cause Linux can't notice that data being corrupted by a
driver

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

Title:
  Data Corruption with Sil 3114 and 3124 controlleurs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Silicon Image 3114 and 3124 seem to have data corruption at writing data 
(particularly with big files or when the writing concern lot of files).
  I used a PCI card with the Sil 3114 chip; when copying files and directories 
from a HDD to an other, data corruption appears and seems to be random in files.
  But every checks about the computer (RAM, HDD ...) have gone right.
  Don't know what happening really, but I supposed that the module which 
control the Sil 3114 (and so the Sil 3124, cause this module was written from 
the 3114's module) contain a bug.
  I've tried to enable the Sil 3114 module's option called "slow_down" which 
should solve some "problems", no difference with and without this option 
activated. The Sil 3124 module's doesn't have this option.

  Drives connected to Sil3124 controller seems to be affected by data
  corruption when at least 2 process attempts to writing at the same
  drive (obviously not in the same directory nor the same file), against
  Sil3114 which the bug seems to appears anytime.

  I have already posted a question :
  https://unix.stackexchange.com/questions/564067/file-corruption-
  between-2-hdd with more precisions about what have done until now.

  Now i use a PCI card based on the Sil 3124 controller, seems to have
  the same data corruption issue as the Sil 3114, but less pronounced
  (less often).

  Running Ubuntu 16.04 server i386 with Linux Kernel 4.4.211.

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

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

[Kernel-packages] [Bug 1859261] Re: [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch Edit

2020-02-13 Thread Ike Panhc

** Changed in: kunpeng920/upstream-kernel
   Status: Triaged => Fix Committed

** Changed in: kunpeng920/upstream-kernel
Milestone: None => linux-v5.6

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

Title:
  [hns3-0111]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE
  kernel branch Edit

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Committed
Status in kunpeng920 ubuntu-20.04 series:
  Fix Committed
Status in kunpeng920 upstream-kernel series:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  [Bug Description]
   hns3 patchset have merged into mainline 5.4rc5 kernel. Pls backport ubuntu 
18.04.5 kernel version
  [Steps to Reproduce]
    1)
    2)
    3)

  [Actual Results]

  [Expected Results]

  [Reproducibility]

  [Additional information]
    (Firmware version, kernel version, affected hardware, etc. if required):

  [Resolution]
  net: hns3: support tx-scatter-gather-fraglist feature
  net: hns3: add support for configuring VF MAC from the host
  net: hns3: add support for configuring bandwidth of VF on the host
  net: hns3: add support for setting VF trust
  net: hns3: add support for spoof check setting
  net: hns3: add support for setting VF link status on the host
  net: hns3: make array tick_array static, makes object smaller

  net: hns3: fix a wrong reset interrupt status mask
  net: hns3: cleanup of stray struct hns3_link_mode_mapping
  net: hns3: fix ETS bandwidth validation bug
  net: hns3: reallocate SSU' buffer size when pfc_en changes
  net: hns3: add compatible handling for MAC VLAN switch parameter configuration
  net: hns3: add compatible handling for command HCLGE_OPC_PF_RST_DONE
  net: hns3: remove unused macros
  net: hns3: Use the correct style for SPDX License Identifier
  net: hns3: cleanup byte order issues when printed
  net: hns3: cleanup some print format warning
  net: hns3: add or modify some comments
  net: hns3: optimize local variable initialization
  net: hns3: cleanup a format-truncation warning
  net: hns3: cleanup some coding style issues
  net: hns3: cleanup some magic numbers
  net: hns3: add struct netdev_queue debug info for TX timeout
  net: hns3: dump some debug information when reset fail
  treewide: Use sizeof_member() macro
  net: hns3: log and clear hardware error after reset complete
  net: hns3: do not allocate linear data for fraglist skb
  net: hns3: minor cleanup for hns3_handle_rx_bd()
  net: hns3: make struct hns3_enet_ring cacheline aligned
  net: hns3: introduce ring_to_netdev() in enet module
  net: hns3: minor optimization for barrier in IO path
  net: hns3: optimized MAC address in management table.
  net: hns3: remove struct hns3_nic_ring_data in hns3_enet module
  net: hns3: fix mis-counting IRQ vector numbers issue
    net: hns3: fix VF ID issue for setting VF VLAN
  net: hns3: fix a use after free problem in hns3_nic_maybe_stop_tx()
  net: hns3: fix for TX queue not restarted problem
   net: hns3: only print misc interrupt status when handling fails
  net: hns3: add a log for getting chain failure in 
hns3_nic_uninit_vector_data()
  net: hns3: add some VF VLAN information for command "ip link show"
  net: hns3: implement ndo_features_check ops for hns3 driver
  net: hns3: get FD rules location before dump in debugfs
  net: hns3: optimization for CMDQ uninitialization
  net: hns3: remove useless mutex vport_cfg_mutex in the struct hclge_dev
  net: hns3: check FE bit before calling hns3_add_frag()
  net: hns3: do not schedule the periodic task when reset fail
  net: hns3: allocate WQ with WQ_MEM_RECLAIM flag
  net: hns3: remove unnecessary work in hclgevf_main
  net: hns3: remove mailbox and reset work in hclge_main
  net: hns3: schedule hclgevf_service by using delayed workqueue
  net: hns3: refactor the notification scheme of PF reset
  net: hns3: refactor the procedure of VF FLR
  net: hns3: modify hclge_func_reset_sync_vf()'s return type to void
  net: hns3: enlarge HCLGE_RESET_WAIT_CNT
  net: hns3: refactor the precedure of PF FLR
  net: hns3: split hclgevf_reset() into preparing and rebuilding part
  net: hns3: split hclge_reset() into preparing and rebuilding part
  net: hns3: modify an unsuitable reset level for hardware error
  net: hns3: replace an unsuitable variable type in 
hclge_inform_reset_assert_to_vf()
  net: hns3: add protection when get SFP speed as 0
  net: hns3: modify the IRQ name of misc vectors
  net: hns3: modify an unsuitable log in hclge_map_ring_to_vector()
  net: hns3: modify the IRQ name of TQP vector
  net: hns3: re-organize vector handle
  net: hns3: add trace event support for HNS3 driver

  update 0120
  net: hns3: pad the short frame before sending to the hardware

  [Status]
  (Fix committed): net: hns3: support tx-scatter-gather-fraglist feature
  (Fix committed): net: hns3: add support for co

[Kernel-packages] [Bug 1862712] Re: change the ASoC card name and card longname to meet the requirement of alsa-lib-1.2.1 (Focal)

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

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

Title:
  change the ASoC card name and card longname to meet the requirement of
  alsa-lib-1.2.1 (Focal)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In the ubuntu-20.04, we integrate the alsa-lib-1.2.1.2, and from the
  alsa-lib-1.2.1, the ucm is put into a standalone package alsa-ucm-conf,
  and from the 1.2.1, the alsa-lib supports the ucm2.

  In the alsa-ucm-conf-1.2.1.2, the ucm2 folders are named by new
  card name or longname, kernel-v5.5-rc1 has patches to change those
  names to new names. now we backport them to focal kernel.

  [Impact]
  booting with the focal kernel, the audio driver can't find the ucm2
  confs, that is becuase alsa-lib-1.2.1 requires new cardname and long
  name, but focal kernel provides the old card names.

  [Fix]
  backport 3 patches from v5.5-rc1.

  
  [Test Case]
  install the 20.04 daily build image, install the linux-firmware and
  alsa-ucm-conf, booting with the kernel which have those 3 patches,
  the alsa-lib could find the correct ucm2 confs.

  [Regression Risk]
  It is low risk to focal.
  If users install focal kernel to bionic or disco, it will break
  the audio since the ucm in the bionic and disco still follow the old
  card name and longname, we need to link a new copy ucm named by new
  cardname or longname in the bionic and disco.

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

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

[Kernel-packages] [Bug 1861192] Re: disco/linux: 5.0.0-41.45 -proposed tracker

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => 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/1861192

Title:
  disco/linux: 5.0.0-41.45 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 30. January 2020 14:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-5.0: bug 1861179
bionic/linux-azure: bug 1862405
bionic/linux-bluefield: bug 1861188
bionic/linux-gcp: bug 1862213
bionic/linux-gke-5.0: bug 1861187
bionic/linux-oem-osp1: bug 1861178
bionic/linux-oracle-5.0: bug 1861190
  variant: debs

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

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

[Kernel-packages] [Bug 1862736] Re: sof driver fails and print lots of errors in the dmesg (focal)

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

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

Title:
  sof driver fails and print lots of errors in  the dmesg (focal)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In the focal kernel, we backported a commit from the stable patches,
  that commit make the sof driver fail to work, and even make the system
  hang randomly.

  The commit we introduced is:
  Author: Ranjani Sridharan 
  Date: Mon Nov 4 14:48:12 2019 -0800

  ASoC: SOF: topology: set trigger order for FE DAI link

  BugLink: https://bugs.launchpad.net/bugs/1858428

  [ Upstream commit 5eee2b3f60065a2530d13f28e771be48b989eb4c ]

  Set trigger order for FE DAI links to SND_SOC_DPCM_TRIGGER_POST
  to trigger the BE DAI's before the FE DAI's. This prevents the
  xruns seen on playback pipelines using the link DMA.

  Signed-off-by: Ranjani Sridharan 
  Signed-off-by: Pierre-Louis Bossart 
  Link: 
https://lore.kernel.org/r/20191104224812.3393-3-ranjani.sridha...@linux.intel.com
  Signed-off-by: Mark Brown 
  Signed-off-by: Sasha Levin 
  Signed-off-by: Seth Forshee 

  
  [Impact]
  Booting the focal kernel on the LENOVO X1 corbon 7th and a Dell
  machine which has dmic on it, the sof driver print lots of errors
  even it loaded the firmware and topology conf file correctly, and
  the sof driver fails to initializaton, after booting up, we run:
  aplay -l, it print out that there is no soundcard. And the system
  randomly hang.

  [Fix]
  We backported a patch from stable kernel, that is not enough, the
  submitter of that patch sent 2 patches out, the stable kernel only
  integrated the 2nd one, to fix this problem, let's integrate the
  1st one as well.

  
  [Test Case]
  After applied all patches, the sof driver worked well, all audio
  functions worked well, and the system didn't hang randomly anymore.

  [Regression Risk]
  Low, these two patches fix FB/BE order issue, we should backport them
  together. And I have tested the patches on a LENOVO and a Dell machine,
  all worked well.

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

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

[Kernel-packages] [Bug 1862824] Re: bionic/linux: 4.15.0-88.88 -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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Wednesday, 12. February 2020 12:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1862808
bionic/linux-fips: bug 1861152
bionic/linux-gke-4.15: bug 1862810
bionic/linux-ibm-gt: bug 1862812
bionic/linux-kvm: bug 1862811
bionic/linux-oem: bug 1862013
bionic/linux-oracle: bug 1862814
bionic/linux-raspi2: bug 1861134
bionic/linux/pc-kernel: bug 1862803
bionic/linux/pc-lowlatency-kernel: bug 1862804
xenial/linux-azure: bug 1862818
xenial/linux-gcp: bug 1862821
xenial/linux-hwe: bug 1862823
  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/1862824

Title:
  bionic/linux: 4.15.0-88.88 -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:
  Confirmed
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux 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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Wednesday, 12. February 2020 12:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1862808
bionic/linux-fips: bug 1861152
bionic/linux-gke-4.15: bug 1862810
bionic/linux-ibm-gt: bug 1862812
bionic/linux-kvm: bug 1862811
bionic/linux-oem: bug 1862013
bionic/linux-oracle: bug 1862814
bionic/linux-raspi2: bug 1861134
bionic/linux/pc-kernel: bug 1862803
bionic/linux/pc-lowlatency-kernel: bug 1862804
xenial/linux-azure: bug 1862818
xenial/linux-gcp: bug 1862821
xenial/linux-hwe: bug 1862823
  variant: debs

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

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

[Kernel-packages] [Bug 1861110] Re: xenial/linux-kvm: 4.4.0-1066.73 -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: 1861122
  packages:
main: linux-kvm
meta: linux-meta-kvm
- phase: Testing
- phase-changed: Thursday, 30. January 2020 13:18 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Thursday, 13. February 2020 08:38 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- cycle not ready to release
  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/1861110

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  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:
  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: 1861122
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Holding before Promote to Updates
  phase-changed: Thursday, 13. February 2020 08:38 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- cycle not ready to release
  variant: debs

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

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

[Kernel-packages] [Bug 1861115] Re: xenial/linux-snapdragon: 4.4.0-1133.141 -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: 1861122
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
- phase: Ready for Testing
- phase-changed: Wednesday, 12. February 2020 22:11 UTC
+ phase: Testing
+ phase-changed: Thursday, 13. February 2020 08:38 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1861114
  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/1861115

Title:
  xenial/linux-snapdragon: 4.4.0-1133.141 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  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:
  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: 1861122
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Thursday, 13. February 2020 08:38 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1861114
  variant: debs

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

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

[Kernel-packages] [Bug 1861136] Re: bionic/linux-snapdragon: 4.15.0-1072.79 -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: 1861165
+ kernel-stable-master-bug: '1862824'
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Tuesday, 11. February 2020 13:26 UTC
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1861135
  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/1861136

Title:
  bionic/linux-snapdragon: 4.15.0-1072.79 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon 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: '1862824'
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Tuesday, 11. February 2020 13:26 UTC
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1861135
  variant: debs

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

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

[Kernel-packages] [Bug 1852071] Re: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys

Can you please try BIOS 01.10.00 Rev.A?

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

Title:
  [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys
  works as microphone mute function keys

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1. Press fn+F3.
  Ubuntu shows "Internal microphone" turned off OSD pop-up.
  Should turn the brightness down.
  2. Press fn+F3 again.
  Ubuntu shows "Internal microphone" turned on OSD pop-up.
  Should turn the brightness down.

  1. Press fn+F4.
  Ubuntu shows "Internal microphone" turned off OSD pop-up.
  Should turn the brightness up.
  2. Press fn+F4 again.
  Ubuntu shows "Internal microphone" turned on OSD pop-up.
  Should turn the brightness up.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 13:23:56 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:8428]
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc.
   Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd 
(Foxlink)
   Bus 001 Device 004: ID 8087:0aaa Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook Studio G5
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic 
root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Kernel-packages] [Bug 1861300] Re: Data Corruption with Sil 3114 and 3124 controlleurs

Ok, please try disabling via kernel parameter "libata.force=noncq".

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

Title:
  Data Corruption with Sil 3114 and 3124 controlleurs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Silicon Image 3114 and 3124 seem to have data corruption at writing data 
(particularly with big files or when the writing concern lot of files).
  I used a PCI card with the Sil 3114 chip; when copying files and directories 
from a HDD to an other, data corruption appears and seems to be random in files.
  But every checks about the computer (RAM, HDD ...) have gone right.
  Don't know what happening really, but I supposed that the module which 
control the Sil 3114 (and so the Sil 3124, cause this module was written from 
the 3114's module) contain a bug.
  I've tried to enable the Sil 3114 module's option called "slow_down" which 
should solve some "problems", no difference with and without this option 
activated. The Sil 3124 module's doesn't have this option.

  Drives connected to Sil3124 controller seems to be affected by data
  corruption when at least 2 process attempts to writing at the same
  drive (obviously not in the same directory nor the same file), against
  Sil3114 which the bug seems to appears anytime.

  I have already posted a question :
  https://unix.stackexchange.com/questions/564067/file-corruption-
  between-2-hdd with more precisions about what have done until now.

  Now i use a PCI card based on the Sil 3124 controller, seems to have
  the same data corruption issue as the Sil 3114, but less pronounced
  (less often).

  Running Ubuntu 16.04 server i386 with Linux Kernel 4.4.211.

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

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

[Kernel-packages] [Bug 1861116] Re: xenial/linux-fips: 4.4.0-1029.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: 1861122
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
- phase: Testing
- phase-changed: Friday, 31. January 2020 17:22 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Thursday, 13. February 2020 08:38 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Ongoing -- testing in progress
+   promote-to-updates: Holding -- cycle not ready to release
  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/1861116

Title:
  xenial/linux-fips: 4.4.0-1029.34 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
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-signing-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1861122
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Holding before Promote to Updates
  phase-changed: Thursday, 13. February 2020 08:38 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Holding -- cycle not ready to release
  variant: debs

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

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

[Kernel-packages] [Bug 1862818] Re: xenial/linux-azure: 4.15.0-1071.76 -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: 1862824
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Wednesday, 12. February 2020 15:58 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   stakeholder-signoff: Pending -- waiting for signoff
+   stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-azure: bug 1862816
xenial/linux-azure/azure-kernel: bug 1862815
  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/1862818

Title:
  xenial/linux-azure: 4.15.0-1071.76 -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-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:
  In Progress
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  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: 1862824
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Wednesday, 12. February 2020 15:58 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-azure: bug 1862816
xenial/linux-azure/azure-kernel: bug 1862815
  variant: debs

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

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

[Kernel-packages] [Bug 1862808] Re: bionic/linux-aws: 4.15.0-1060.62 -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: 1862824
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Wednesday, 12. February 2020 11:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-fips: bug 1862806
bionic/linux-aws/aws-kernel: bug 1862805
xenial/linux-aws-hwe: bug 1862807
  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/1862808

Title:
  bionic/linux-aws: 4.15.0-1060.62 -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 promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws 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: 1862824
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Wednesday, 12. February 2020 11:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-fips: bug 1862806
bionic/linux-aws/aws-kernel: bug 1862805
xenial/linux-aws-hwe: bug 1862807
  variant: debs

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

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

[Kernel-packages] [Bug 1861595] Re: Laptop does not resume after suspend. OK plugged-in, fails with battery

Please attach `journalctl -b -1 -k` on the next boot after failed
resume.

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

Title:
  Laptop does not resume after suspend. OK plugged-in, fails with
  battery

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This replicated in 18.10, 19.04 and 19.10.

  If I suspend the laptop by turning the lid of, or by

  #echo mem > /sys/power/state

  The nvme disk I have:
  # nvme list
  Node SN   Model   
 Namespace Usage  Format   FW Rev
    
 - -- 
 
  /dev/nvme0n1 03F107951E4452173098 Sabrent 
 1   1.02  TB /   1.02  TB512   B +  0 B   ECFM12.2

  Make it to fail the resume process.

  Everything works fine while plugged in.
  If power by battery it fails to resume (attached dmesg file). It gets stuck 
into the desktop but it's dysfunctional without disk operation.

  If I suspend in battery mode and then resume (that fails to resume
  properly) and then plug in the power supply the disk resumes perfectly
  and everything comes back to normal.

  It doesn't always replicate, but I would say 80% of the time.

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

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

[Kernel-packages] [Bug 1862250] Re: focal/linux-azure-5.4: 5.4.0-1002.2 -proposed tracker

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

** Tags added: block-proposed-focal

** Tags added: block-proposed

** 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: 1862255
  packages:
lrm: linux-restricted-modules-azure-5.4
main: linux-azure-5.4
meta: linux-meta-azure-5.4
signed: linux-signed-azure-5.4
- phase: Holding before Promote to Proposed
- phase-changed: Wednesday, 12. February 2020 23:01 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Thursday, 13. February 2020 08:48 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,meta:depwait,signed:depwait
+   promote-to-proposed: Pending -- ready for review
  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/1862250

Title:
  focal/linux-azure-5.4: 5.4.0-1002.2 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow stakeholder-signoff 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1862255
  packages:
lrm: linux-restricted-modules-azure-5.4
main: linux-azure-5.4
meta: linux-meta-azure-5.4
signed: linux-signed-azure-5.4
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 13. February 2020 08:48 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  variant: debs

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

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

[Kernel-packages] [Bug 1861197] Re: eoan/linux-raspi2: 5.3.0-1018.20 -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: 1861214
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Tuesday, 04. February 2020 14:47 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-raspi2-5.3: bug 1861196
eoan/linux-raspi2/pi-kernel: bug 1861194
  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/1861197

Title:
  eoan/linux-raspi2: 5.3.0-1018.20 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Eoan:
  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: 1861214
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Tuesday, 04. February 2020 14:47 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-raspi2-5.3: bug 1861196
eoan/linux-raspi2/pi-kernel: bug 1861194
  variant: debs

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

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

[Kernel-packages] [Bug 1859979] Re: nilfs2 segctord kthread dies after which write to nilfs2 fs freezes the process writing

If it's a regression, please consider running a kernel bisection.

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

Title:
  nilfs2 segctord kthread dies after which write to nilfs2 fs freezes
  the process writing

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With linux-image-5.3.0-26-lowlatency, segctord kthread encounters a
  "BUG: kernel NULL pointer dereference, address: 00a8" some
  half a minute from boot. Before that, one can log in to the system
  (/home is on a nilfs2 filesystem), but after the kernel BUG report,
  any write to a nilfs2 filesystem freezes the process trying to write,
  or any new login attempt freezes. This bug can be reproduced with
  every boot.

  With linux-image-5.3.0-24-lowlatency and earlier, this doesn't happen.

  Relevant excerpt from syslog:

  ...
  Jan 16 10:56:59 lillukka kernel: [0.00] Linux version 
5.3.0-26-lowlatency (buildd@lgw01-amd64-013) (gcc version 9.2.1 20191008 
(Ubuntu 9.2.1-9ubuntu2)) #28-Ubuntu SMP
   PREEMPT Wed Dec 18 06:21:38 UTC 2019 (Ubuntu 5.3.0-26.28-lowlatency 5.3.13)
  ...
  Jan 16 10:57:13 lillukka kernel: [   28.727753] BUG: kernel NULL pointer 
dereference, address: 00a8
  Jan 16 10:57:13 lillukka kernel: [   28.727852] #PF: supervisor read access 
in kernel mode
  Jan 16 10:57:13 lillukka kernel: [   28.727914] #PF: error_code(0x) - 
not-present page
  Jan 16 10:57:13 lillukka kernel: [   28.727974] PGD 0 P4D 0 
  Jan 16 10:57:13 lillukka kernel: [   28.728012] Oops:  [#1] PREEMPT SMP 
PTI
  Jan 16 10:57:13 lillukka kernel: [   28.728067] CPU: 3 PID: 838 Comm: 
segctord Not tainted 5.3.0-26-lowlatency #28-Ubuntu
  Jan 16 10:57:13 lillukka kernel: [   28.728156] Hardware name: Sony 
Corporation SVP1321C5E/VAIO, BIOS R0280V7 07/11/2013
  Jan 16 10:57:13 lillukka kernel: [   28.728257] RIP: 
0010:percpu_counter_add_batch+0x13/0x80
  Jan 16 10:57:13 lillukka kernel: [   28.728334] Code: e0 41 5c 41 5d 41 5e 5d 
c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 55 48 89 e5 41 55 41 54 49 89 fc 
53 65 ff 05 b5 5c 
  ed 72 <48> 8b 47 20 48 63 ca 65 44 8b 28 49 63 dd 48 01 f3 48 39 d9 7e 0a
  Jan 16 10:57:13 lillukka kernel: [   28.728536] RSP: 0018:b582c02afcb0 
EFLAGS: 00010082
  Jan 16 10:57:13 lillukka kernel: [   28.728598] RAX: 0002 RBX: 
 RCX: 0001
  Jan 16 10:57:13 lillukka kernel: [   28.728679] RDX: 0018 RSI: 
0001 RDI: 0088
  Jan 16 10:57:13 lillukka kernel: [   28.728760] RBP: b582c02afcc8 R08: 
8f519357ab40 R09: 0018
  Jan 16 10:57:13 lillukka kernel: [   28.728841] R10: 00030140 R11: 
8f5193609eea R12: 0088
  Jan 16 10:57:13 lillukka kernel: [   28.728920] R13: 8f518a3ee498 R14: 
8f518a3ee608 R15: e52b07e5a200
  Jan 16 10:57:13 lillukka kernel: [   28.729001] FS:  () 
GS:8f519798() knlGS:
  Jan 16 10:57:13 lillukka kernel: [   28.729091] CS:  0010 DS:  ES:  
CR0: 80050033
  Jan 16 10:57:13 lillukka kernel: [   28.729157] CR2: 00a8 CR3: 
8d60a002 CR4: 001606e0
  Jan 16 10:57:13 lillukka kernel: [   28.729237] Call Trace:
  Jan 16 10:57:13 lillukka kernel: [   28.729280]  
__test_set_page_writeback+0x2f1/0x310
  Jan 16 10:57:13 lillukka kernel: [   28.729362]  
nilfs_segctor_do_construct+0xd13/0x1260 [nilfs2]
  Jan 16 10:57:13 lillukka kernel: [   28.729432]  ? __switch_to_asm+0x40/0x70
  Jan 16 10:57:13 lillukka kernel: [   28.729496]  
nilfs_segctor_construct+0x1ff/0x2f0 [nilfs2]
  Jan 16 10:57:13 lillukka kernel: [   28.729572]  
nilfs_segctor_thread+0x136/0x3a0 [nilfs2]
  Jan 16 10:57:13 lillukka kernel: [   28.729640]  kthread+0x104/0x140
  Jan 16 10:57:13 lillukka kernel: [   28.729690]  ? 
nilfs_segctor_construct+0x2f0/0x2f0 [nilfs2]
  Jan 16 10:57:13 lillukka kernel: [   28.729760]  ? kthread_park+0x80/0x80
  Jan 16 10:57:13 lillukka kernel: [   28.729807]  ret_from_fork+0x35/0x40
  Jan 16 10:57:13 lillukka kernel: [   28.729854] Modules linked in: ccm rfcomm 
aufs overlay cmac bnep nilfs2 snd_hda_codec_realtek snd_hda_codec_generic 
ledtrig_audio snd_hda_codec_hdmi snd_hda_intel pn544_mei mei_phy pn544 
snd_hda_codec hci snd_hda_core snd_hwdep intel_rapl_msr mei_hdcp nfc snd_pcm 
snd_seq_midi snd_seq_midi_event intel_rapl_common x86_pkg_temp_thermal 
intel_powerclamp snd_rawmidi coretemp iwlmvm mac80211 snd_seq btusb btrtl 
libarc4 btbcm uvcvideo btintel kvm videobuf2_vmalloc iwlwifi videobuf2_memops 
bluetooth snd_seq_device videobuf2_v4l2 videobuf2_common irqbypass joydev 
input_leds intel_cstate videodev ecdh_generic snd_timer intel_rapl_perf ecc 
serio_raw mc mei_me cfg80211 mei snd soundcore sony_laptop mac_hid 
intel_smartconnect sch_fq_codel cuse parport_pc ppdev lp parport ip_tables 
x_tables autofs4 btrfs xor zstd_compress

[Kernel-packages] [Bug 1860166] Re: Touchpad not supported

Please remove i2c_i801 in /etc/modprobe.d/blacklist.conf.

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

Title:
  Touchpad not supported

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My touchpad is not supported by kernal of Ubuntu 18.04.
  It is a lenovo G50-80 laptop.

  The below is the response of xinput.
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ETPS/2 Elantech Touchpadid=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Lenovo EasyCamera: Lenovo EasyC id=10   [slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=11   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]


  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.36
  Uname: Linux 5.0.0-05-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 18 00:10:51 2020
  InstallationDate: Installed on 2020-01-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sridhar1704 F pulseaudio
   /dev/snd/controlC0:  sridhar1704 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-18 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 80E5
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=b6cf46e6-9187-4b99-9327-6126097a94aa ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-74-generic N/A
   linux-backports-modules-4.15.0-74-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-74-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0CN96WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo G50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0CN96WW:bd09/22/2015:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoG50-80:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80E5
  dmi.product.version: Lenovo G50-80
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1853937] Re: [hns-1126] net: hns: add support for vlan TSO

18.04.4 has now been released.

** Changed in: kunpeng920/ubuntu-18.04-hwe
   Status: Fix Committed => 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/1853937

Title:
  [hns-1126] net: hns: add support for vlan TSO

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-18.04 series:
  Fix Committed
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Released
Status in kunpeng920 ubuntu-19.04 series:
  Fix Released
Status in kunpeng920 ubuntu-19.10 series:
  Fix Released
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 Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  hns hardware supports vlan TSO but driver does not set the flag.

  [Test Case]
  Performance run through vlan TSO shall reach limitation.

  [Fix]
  0d581ba311a2 net: hns: add support for vlan TSO

  [Regression Risk]
  Patch restricted to hns3 driver.

  """[Bug Description]
  When add vlan to the net ports, the performance is almost 50% lower than no 
vlan.

  [Steps to Reproduce]
  1.add vlan to net port(10G fibre);
  2.add ip to this vlan;
  3.run iperf to test the performance;

  [Actual Results]
  iperf result is about 5~6Gbp/s

  [Expected Results]
  iperf result is about 9.4Gbp/s

  [Reproducibility]
  Conditionally Recur

  [Additional information]
  Hardware: D05
  Firmware: NA
  Kernel: NA

  [Resolution]
  The hip07 chip support vlan TSO, adds NETIF_F_TSO and NETIF_F_TSO6 flags to 
vlan_features."""

  net: hns: add support for vlan TSO

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

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

[Kernel-packages] [Bug 1853937] Re: [hns-1126] net: hns: add support for vlan TSO

Apologies, this patch is still in the proposed pocket. Correcting 18.04
series status to "Fix Committed".

** Changed in: kunpeng920/ubuntu-18.04
   Status: Fix Released => Fix Committed

** Changed in: kunpeng920/ubuntu-18.04
Milestone: ubuntu-18.04.3-sru-6 => ubuntu-18.04.4-sru-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/1853937

Title:
  [hns-1126] net: hns: add support for vlan TSO

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-18.04 series:
  Fix Committed
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Released
Status in kunpeng920 ubuntu-19.04 series:
  Fix Released
Status in kunpeng920 ubuntu-19.10 series:
  Fix Released
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 Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  hns hardware supports vlan TSO but driver does not set the flag.

  [Test Case]
  Performance run through vlan TSO shall reach limitation.

  [Fix]
  0d581ba311a2 net: hns: add support for vlan TSO

  [Regression Risk]
  Patch restricted to hns3 driver.

  """[Bug Description]
  When add vlan to the net ports, the performance is almost 50% lower than no 
vlan.

  [Steps to Reproduce]
  1.add vlan to net port(10G fibre);
  2.add ip to this vlan;
  3.run iperf to test the performance;

  [Actual Results]
  iperf result is about 5~6Gbp/s

  [Expected Results]
  iperf result is about 9.4Gbp/s

  [Reproducibility]
  Conditionally Recur

  [Additional information]
  Hardware: D05
  Firmware: NA
  Kernel: NA

  [Resolution]
  The hip07 chip support vlan TSO, adds NETIF_F_TSO and NETIF_F_TSO6 flags to 
vlan_features."""

  net: hns: add support for vlan TSO

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

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

[Kernel-packages] [Bug 1853937] Re: [hns-1126] net: hns: add support for vlan TSO

Was released in 4.15 in Dec 2019.

** Changed in: kunpeng920/ubuntu-18.04
   Status: Fix Committed => Fix Released

** Changed in: kunpeng920/ubuntu-18.04
Milestone: None => ubuntu-18.04.3-sru-6

** Changed in: kunpeng920/ubuntu-19.04
   Status: Fix Committed => Fix Released

** Changed in: kunpeng920/ubuntu-19.04
Milestone: None => ubuntu-19.04-sru-10

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

Title:
  [hns-1126] net: hns: add support for vlan TSO

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-18.04 series:
  Fix Committed
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Released
Status in kunpeng920 ubuntu-19.04 series:
  Fix Released
Status in kunpeng920 ubuntu-19.10 series:
  Fix Released
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 Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  hns hardware supports vlan TSO but driver does not set the flag.

  [Test Case]
  Performance run through vlan TSO shall reach limitation.

  [Fix]
  0d581ba311a2 net: hns: add support for vlan TSO

  [Regression Risk]
  Patch restricted to hns3 driver.

  """[Bug Description]
  When add vlan to the net ports, the performance is almost 50% lower than no 
vlan.

  [Steps to Reproduce]
  1.add vlan to net port(10G fibre);
  2.add ip to this vlan;
  3.run iperf to test the performance;

  [Actual Results]
  iperf result is about 5~6Gbp/s

  [Expected Results]
  iperf result is about 9.4Gbp/s

  [Reproducibility]
  Conditionally Recur

  [Additional information]
  Hardware: D05
  Firmware: NA
  Kernel: NA

  [Resolution]
  The hip07 chip support vlan TSO, adds NETIF_F_TSO and NETIF_F_TSO6 flags to 
vlan_features."""

  net: hns: add support for vlan TSO

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

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

[Kernel-packages] [Bug 1863064] [NEW] package kexec-tools 1:2.0.18-1ubuntu1 failed to install/upgrade: installed kexec-tools package post-installation script subprocess returned error exit status 1

2020-02-13 Thread Max Lund

Public bug reported:

Hang on install package

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: kexec-tools 1:2.0.18-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
Uname: Linux 5.3.0-29-generic x86_64
NonfreeKernelModules: wl nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
Date: Thu Feb 13 09:54:03 2020
ErrorMessage: installed kexec-tools package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2019-12-11 (63 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4
SourcePackage: kexec-tools
Title: package kexec-tools 1:2.0.18-1ubuntu1 failed to install/upgrade: 
installed kexec-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: kexec-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package eoan

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

Title:
  package kexec-tools 1:2.0.18-1ubuntu1 failed to install/upgrade:
  installed kexec-tools package post-installation script subprocess
  returned error exit status 1

Status in kexec-tools package in Ubuntu:
  New

Bug description:
  Hang on install package

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: kexec-tools 1:2.0.18-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Thu Feb 13 09:54:03 2020
  ErrorMessage: installed kexec-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2019-12-11 (63 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: kexec-tools
  Title: package kexec-tools 1:2.0.18-1ubuntu1 failed to install/upgrade: 
installed kexec-tools 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/kexec-tools/+bug/1863064/+subscriptions

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

[Kernel-packages] [Bug 1861197] Re: eoan/linux-raspi2: 5.3.0-1018.20 -proposed tracker

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

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

Title:
  eoan/linux-raspi2: 5.3.0-1018.20 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Eoan:
  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: 1861214
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Tuesday, 04. February 2020 14:47 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-raspi2-5.3: bug 1861196
eoan/linux-raspi2/pi-kernel: bug 1861194
  variant: debs

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

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

[Kernel-packages] [Bug 1853948] Re: [hns-1126]net: hns3: fix flow control configure issue for fibre port

18.04.4 has now been released.

** Changed in: kunpeng920/ubuntu-19.04
   Status: Fix Committed => Fix Released

** Changed in: kunpeng920/ubuntu-19.04
Milestone: None => ubuntu-19.04-sru-12

** Changed in: kunpeng920/ubuntu-18.04-hwe
   Status: Fix Committed => 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/1853948

Title:
  [hns-1126]net: hns3: fix flow control configure issue for fibre port

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

Bug description:
  [Impact]
  Flow control parameters of fibre port can not be set after enable flow 
control autoneg, as flow control autoneg is unsupported for fibre port

  [Test Case]
  Turning on/off tx pause and ethtool shall report status accordingly.

  [Fix]
  fb89629f2ecf net: hns3: fix flow control configure issue for fibre port

  [Regression Risk]
  Patch restricted to hns3 driver.

  "[Bug Description]
  Flow control parameters of fibre port can not be set after enable flow 
control autoneg, as flow control autoneg is unsupported for fibre port.

  [Steps to Reproduce]
  1.link up fibre port and enable flow control autoneg
  2.check status of tx pause and rx pause
  3.turn off tx pause
  4.checkout status of tx pause

  [Actual Results]
  tx pause is on

  [Expected Results]
  tx pause is off

  [Reproducibility]
  Inevitably

  [Additional information]
  Hardware: D06
  Firmware: NA
  Kernel: NA

  [Resolution]
  This patch return -EOPNOTSUPP when user tries to enable flow control autoneg."

  net: hns3: fix flow control configure issue for fibre port

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

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

[Kernel-packages] [Bug 1863064] Re: package kexec-tools 1:2.0.18-1ubuntu1 failed to install/upgrade: installed kexec-tools package post-installation script subprocess returned error exit status 1

2020-02-13 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package kexec-tools 1:2.0.18-1ubuntu1 failed to install/upgrade:
  installed kexec-tools package post-installation script subprocess
  returned error exit status 1

Status in kexec-tools package in Ubuntu:
  New

Bug description:
  Hang on install package

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: kexec-tools 1:2.0.18-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Thu Feb 13 09:54:03 2020
  ErrorMessage: installed kexec-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2019-12-11 (63 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: kexec-tools
  Title: package kexec-tools 1:2.0.18-1ubuntu1 failed to install/upgrade: 
installed kexec-tools 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/kexec-tools/+bug/1863064/+subscriptions

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

[Kernel-packages] [Bug 1861134] Re: bionic/linux-raspi2: 4.15.0-1055.59 -proposed tracker

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

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

Title:
  bionic/linux-raspi2: 4.15.0-1055.59 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 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: '1862824'
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Tuesday, 04. February 2020 22:43 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-raspi2/pi-kernel: bug 1861133
  variant: debs

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

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

[Kernel-packages] [Bug 1861162] Re: xenial/linux-deeplens: 4.15.0-1016.16 -proposed tracker

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => 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/1861162

Title:
  xenial/linux-deeplens: 4.15.0-1016.16 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: '1862823'
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
  phase: Testing
  phase-changed: Wednesday, 05. February 2020 16:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1861113] Re: xenial/linux-raspi2: 4.4.0-1129.138 -proposed tracker

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

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

Title:
  xenial/linux-raspi2: 4.4.0-1129.138 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
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:
  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: 1861122
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Thursday, 13. February 2020 09:20 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 186
  variant: debs

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

-- 
Mailing list: https://launchpad.net/~kernel-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: kunpeng920/ubuntu-18.04
   Status: In Progress => Fix Committed

** Changed in: kunpeng920
   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:
  Fix Committed
Status in kunpeng920 ubuntu-18.04 series:
  Fix Committed
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Released
Status in kunpeng920 ubuntu-19.04 series:
  Fix Released
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 Released

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 1853992] Re: [sas-1126]scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset()

** Changed in: kunpeng920
   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:
  Fix Committed
Status in kunpeng920 ubuntu-18.04 series:
  Fix Committed
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Released
Status in kunpeng920 ubuntu-19.04 series:
  Fix Released
Status in kunpeng920 ubuntu-19.10 series:
  Fix Committed
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 Released
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]  process_one_work+0x3c0/0x878
  [30293.818560]  worker_thread+0x70/0x670
  [30293.822207]  kthread+0x1b0/0x1b8
  [30293.825423]  ret_from_fork+0x10/0x18
  [30293.828

[Kernel-packages] [Bug 1853989] Re: [roce-1126]RDMA/hns: bugfix for slab-out-of-bounds when loading hip08 driver

** Changed in: kunpeng920/ubuntu-19.10
   Status: In Progress => Fix Committed

** Changed in: kunpeng920/ubuntu-18.04
   Status: In Progress => Fix Committed

** Changed in: kunpeng920
   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:
  Fix Committed
Status in kunpeng920 ubuntu-18.04 series:
  Fix Committed
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Released
Status in kunpeng920 ubuntu-19.04 series:
  Fix Released
Status in kunpeng920 ubuntu-19.10 series:
  Fix Committed
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 Released
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 1862824] Re: bionic/linux: 4.15.0-88.88 -proposed tracker

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => 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/1862824

Title:
  bionic/linux: 4.15.0-88.88 -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:
  In Progress
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux 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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Wednesday, 12. February 2020 12:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1862808
bionic/linux-fips: bug 1861152
bionic/linux-gke-4.15: bug 1862810
bionic/linux-ibm-gt: bug 1862812
bionic/linux-kvm: bug 1862811
bionic/linux-oem: bug 1862013
bionic/linux-oracle: bug 1862814
bionic/linux-raspi2: bug 1861134
bionic/linux-snapdragon: bug 1861136
bionic/linux/pc-kernel: bug 1862803
bionic/linux/pc-lowlatency-kernel: bug 1862804
xenial/linux-azure: bug 1862818
xenial/linux-gcp: bug 1862821
xenial/linux-hwe: bug 1862823
  variant: debs

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

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

[Kernel-packages] [Bug 1862824] Re: bionic/linux: 4.15.0-88.88 -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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Wednesday, 12. February 2020 12:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1862808
bionic/linux-fips: bug 1861152
bionic/linux-gke-4.15: bug 1862810
bionic/linux-ibm-gt: bug 1862812
bionic/linux-kvm: bug 1862811
bionic/linux-oem: bug 1862013
bionic/linux-oracle: bug 1862814
bionic/linux-raspi2: bug 1861134
+   bionic/linux-snapdragon: bug 1861136
bionic/linux/pc-kernel: bug 1862803
bionic/linux/pc-lowlatency-kernel: bug 1862804
xenial/linux-azure: bug 1862818
xenial/linux-gcp: bug 1862821
xenial/linux-hwe: bug 1862823
  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/1862824

Title:
  bionic/linux: 4.15.0-88.88 -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:
  In Progress
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux 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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Wednesday, 12. February 2020 12:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1862808
bionic/linux-fips: bug 1861152
bionic/linux-gke-4.15: bug 1862810
bionic/linux-ibm-gt: bug 1862812
bionic/linux-kvm: bug 1862811
bionic/linux-oem: bug 1862013
bionic/linux-oracle: bug 1862814
bionic/linux-raspi2: bug 1861134
bionic/linux-snapdragon: bug 1861136
bionic/linux/pc-kernel: bug 1862803
bionic/linux/pc-lowlatency-kernel: bug 1862804
xenial/linux-azure: bug 1862818
xenial/linux-gcp: bug 1862821
xenial/linux-hwe: bug 1862823
  variant: debs

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

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

[Kernel-packages] [Bug 1861162] Re: xenial/linux-deeplens: 4.15.0-1016.16 -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: 1861164
+ kernel-stable-master-bug: '1862823'
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
  phase: Testing
  phase-changed: Wednesday, 05. February 2020 16:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  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/1861162

Title:
  xenial/linux-deeplens: 4.15.0-1016.16 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1862823
  packages:
    main: linux-deeplens
    meta: linux-meta-deeplens
  phase: Testing
  phase-changed: Wednesday, 05. February 2020 16:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
    certification-testing: Ongoing -- testing in progress
    verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1854547] Re: 【sas-1130】scsi: sd: define variable dif as unsigned int instead of bool

18.04.4 is now released.

** Changed in: kunpeng920/ubuntu-18.04-hwe
   Status: Fix Committed => Fix Released

** Changed in: kunpeng920/ubuntu-19.10
   Status: Fix Committed => Fix Released

** Changed in: kunpeng920/ubuntu-19.10
Milestone: None => ubuntu-19.10-sru-4

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

Title:
  【sas-1130】scsi: sd: define variable dif as unsigned int instead of
  bool

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

Bug description:
  [Bug Description]
  DIF3 WILL not work when run fio test

  【Steps to Reproduce]
  1. Enable DIF/DIX for DIF3 disk
  2. fio test

  [Actual Results]
  IO error when running IO;
  [  781.032816] sd 5:0:0:0: [sdd] Disabling DIF Type 3 protection
  [  781.112250] sd 5:0:0:0: [sdd] tag#72 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [  781.112287] sd 5:0:0:0: [sdd] tag#72 CDB: Read(10) 28 00 00 00 00 00 00 00 
08 00
  [  781.112305] print_req_error: I/O error, dev sdd, sector 0 flags 0
  [  781.118429] Buffer I/O error on dev sdd, logical block 0, async page read
  [  781.204243] sd 5:0:0:0: [sdd] tag#77 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [  781.204252] sd 5:0:0:0: [sdd] tag#77 CDB: Read(10) 28 00 00 00 00 00 00 00 
08 00
  [  781.204257] print_req_error: I/O error, dev sdd, sector 0 flags 0
  [  781.210365] Buffer I/O error on dev sdd, logical block 0, async page read
  [  781.296238] sd 5:0:0:0: [sdd] tag#82 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [  781.296266] sd 5:0:0:0: [sdd] tag#82 CDB: Read(10) 28 00 00 00 00 00 00 00 
08 00
  [  781.296276] print_req_error: I/O error, dev sdd, sector 0 flags 0
  [  781.302384] Buffer I/O error on dev sdd, logical block 0, async page read
  [  781.309207] ldm_validate_partition_table(): Disk read failed.
  [  781.392239] sd 5:0:0:0: [sdd] tag#87 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [  781.392267] sd 5:0:0:0: [sdd] tag#87 CDB: Read(10) 28 00 00 00 00 00 00 00 
08 00
  [  781.392278] print_req_error: I/O error, dev sdd, sector 0 flags 0
  [  781.398386] Buffer I/O error on dev sdd, logical block 0, async page read
  [  781.484250] sd 5:0:0:0: [sdd] tag#92 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [  781.484260] sd 5:0:0:0: [sdd] tag#92 CDB: Read(10) 28 00 00 00 00 00 00 00 
08 00
  [  781.484264] print_req_error: I/O error, dev sdd, sector 0 flags 0
  [  781.490371] Buffer I/O error on dev sdd, logical block 0, async page read
  [  781.576249] sd 5:0:0:0: [sdd] tag#97 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [  781.576278] sd 5:0:0:0: [sdd] tag#97 CDB: Read(10) 28 00 00 00 00 00 00 00 
08 00
  [  781.576293] print_req_error: I/O error, dev sdd, sector 0 flags 0
  [  781.582399] Buffer I/O error on dev sdd, logical block 0, async page read
  [  781.668236] sd 5:0:0:0: [sdd] tag#102 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [  781.668245] sd 5:0:0:0: [sdd] tag#102 CDB: Read(10) 28 00 00 00 00 00 00 
00 08 00
  [  781.668249] print_req_error: I/O error, dev sdd, sector 0 flags 0
  [  781.674354] Buffer I/O error on dev sdd, logical block 0, async page read
  [  781.681184] Dev sdd: unable to read RDB block 0
  [  781.764241] sd 5:0:0:0: [sdd] tag#121 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [  781.764267] sd 5:0:0:0: [sdd] tag#121 CDB: Read(10) 28 00 00 00 00 00 00 
00 08 00
  [  781.764278] print_req_error: I/O error, dev sdd, sector 0 flags 0
  [  781.770386] Buffer I/O error on dev sdd, logical block 0, async page read
  [  781.856240] sd 5:0:0:0: [sdd] tag#126 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [  781.856248] sd 5:0:0:0: [sdd] tag#126 CDB: Read(10) 28 00 00 00 00 00 00 
00 08 00
  [  781.856253] print_req_error: I/O error, dev sdd, sector 0 flags 0
  [  781.862362] Buffer I/O error on dev sdd, logical block 0, async page read
  [  781.948238] sd 5:0:0:0: [sdd] tag#131 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [  781.948264] sd 5:0:0:0: [sdd] tag#131 CDB: Read(10) 28 00 00 00 00 18 00 
00 08 00
  [  781.948272] print_req_error: I/O error, dev sdd, sector 24 flags 0
  [  781.954467] Buffer I/O error on dev sdd, logical block 3, async page read
  [  782.120252]  sdd: unable to read partition table

  [Expected Results]
  IO running normally

  [Reproducibility]
  occasionally

  [Additional information]
  Hardware: D06 CS

[Kernel-packages] [Bug 1855952] Re: scsi: hisi_sas: Check sas_port before using it

** Changed in: kunpeng920/ubuntu-19.04
   Status: Fix Committed => 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/1855952

Title:
  scsi: hisi_sas: Check sas_port before using it

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-18.04 series:
  Fix Committed
Status in kunpeng920 ubuntu-18.04-hwe series:
  Fix Committed
Status in kunpeng920 ubuntu-19.04 series:
  Fix Released
Status in kunpeng920 ubuntu-19.10 series:
  Fix Committed
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 Released
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]
  8c39673d5474b scsi: hisi_sas: Check sas_port before using it

  [Regression Risk]
  Patch restricted to hisi_sas driver.

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

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

[Kernel-packages] [Bug 1861113] Re: xenial/linux-raspi2: 4.4.0-1129.138 -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: 1861122
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
- phase: Signoff
- phase-changed: Wednesday, 12. February 2020 08:16 UTC
+ phase: Testing
+ phase-changed: Thursday, 13. February 2020 09:20 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 186
  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/1861113

Title:
  xenial/linux-raspi2: 4.4.0-1129.138 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
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:
  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: 1861122
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Testing
  phase-changed: Thursday, 13. February 2020 09:20 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 186
  variant: debs

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

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

[Kernel-packages] [Bug 1854842] Re: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs

2020-02-13 Thread Mohammad Heib

Hi Matthew,
first of all, I would like to apologize for the late reply
i was OOO for a while, sorry :P).

I re-tested the 4.15.0-88-generic and it seems that the issue resolved
So it's verified by Mellanox.

Thank you very much guys for your efforts.

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

Title:
mlx5_core reports hardware checksum error for padded packets on
Mellanox NICs

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

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

[Impact]

On machines equipped with Mellanox NIC's, in this particular case,
Mellanox 5 series NICs using the mlx5_core driver, there is a kernel
splat when sending large IP packets which have padding at the end.

enp6s0f0: hw csum failure
CPU: 19 PID: 0 Comm: swapper/19 Not tainted 4.15.0-72-generic
Call Trace:

dump_stack+0x63/0x8e
netdev_rx_csum_fault+0x38/0x40
__skb_checksum_complete+0xbc/0xd0
nf_ip_checksum+0xc3/0xf0
icmp_error+0x27d/0x310 [nf_conntrack_ipv4]
nf_conntrack_in+0x15a/0x510 [nf_conntrack]
? __skb_checksum+0x68/0x330
ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4]
nf_hook_slow+0x48/0xc0
? skb_send_sock+0x50/0x50
ip_rcv+0x301/0x360
? inet_del_offload+0x40/0x40
__netif_receive_skb_core+0x432/0xb80
__netif_receive_skb+0x18/0x60
? __netif_receive_skb+0x18/0x60
netif_receive_skb_internal+0x45/0xe0
napi_gro_receive+0xc5/0xf0
mlx5e_handle_rx_cqe+0x48d/0x5e0 [mlx5_core]
? enqueue_task_rt+0x1b4/0x2e0
mlx5e_poll_rx_cq+0xd1/0x8c0 [mlx5_core]
mlx5e_napi_poll+0x9d/0x290 [mlx5_core]
net_rx_action+0x140/0x3a0
__do_softirq+0xe4/0x2d4
irq_exit+0xc5/0xd0
do_IRQ+0x86/0xe0
common_interrupt+0x8c/0x8c

This bug is a further attempt to fix these splats, as there has been
previous fixes in LP #1840854 and a series of commits which landed in
4.15.0-67 (LP #1847155) as a part of upstream -stable patches.

This bug will also fix the same problems on the new Mellanox CX6 and
Bluefield hardware, which has been enabled already via previous
upstream -stable patches which landed in LP #1847155.

[Fix]

This particular issue was fixed for Mellanox series 5 drivers in the
following commits:

commit 0aa1d18615c163f92935b806dcaff9157645233a
Author: Saeed Mahameed
Date: Tue Mar 12 00:24:52 2019 -0700
Subject: net/mlx5e: Rx, Fixup skb checksum for packets with tail padding

This commit required a minor backport.

This commit was selected for upstream -stable in 4.19.76 and 5.0.10.
This commit appears to be omitted from "Bionic update: upstream stable
patchset 2019-10-07", which is LP #1847155, probably due to requiring a
backport.

commit db849faa9bef993a1379dc510623f750a72fa7ce
Author: Saeed Mahameed
Date: Fri May 3 13:14:59 2019 -0700
Subject: net/mlx5e: Rx, Fix checksum calculation for new hardware

This commit required a minor backport.

This commit was selected for upstream -stable in 5.1.21 and 5.2.4.
This commit has already been applied to the disco kernel, as part of stable
updates.

[Testcase]

The following scapy script will reproduce this issue. Run from the
machine with the Mellanox series 5 NIC:

a=Ether(dst='ff:ff:ff:ff:ff:ff')/IP(dst='127.0.0.1')/ICMP()/Padding(load='\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe\xfe')

2) sendp(a, iface='enp6s0f0')

3) Check dmesg on the reciever side. The example uses localhost, so
check dmesg.

I have built some test kernels, which are available here:

https://launchpad.net/~mruffell/+archive/ubuntu/lp1854842-test
This kernel contains 0aa1d18615c163f92935b806dcaff9157645233a.

and

https://launchpad.net/~mruffell/+archive/ubuntu/lp1854842-test-2
This kernel contains db849faa9bef993a1379dc510623f750a72fa7ce.

If you install the test kernels the issue is resolved.

[Regression Potential]

The changes are limited to the mlx5_core driver, and only modify how
packet checksums are calculated when padding is involved.

Both patches have been accepted and published by upstream -stable, and
are widely accepted by the community.

Because of this, I believe the risk of regression is low.

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

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

[Kernel-packages] [Bug 1861136] Re: bionic/linux-snapdragon: 4.15.0-1072.79 -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: 1862824
  packages:
-   main: linux-snapdragon
-   meta: linux-meta-snapdragon
+   main: linux-snapdragon
+   meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Tuesday, 11. February 2020 13:26 UTC
  reason:
-   certification-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
-   verification-testing: Ongoing -- testing in progress
+   certification-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  trackers:
-   bionic/linux-snapdragon/dragonboard-kernel: bug 1861135
+   bionic/linux-snapdragon/dragonboard-kernel: bug 1861135
  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/1861136

Title:
  bionic/linux-snapdragon: 4.15.0-1072.79 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon 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: 1862824
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Tuesday, 11. February 2020 13:26 UTC
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1861135
  variant: debs

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

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

[Kernel-packages] [Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"

2020-02-13 Thread Rex Tsai

** Tags added: skylake

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

Title:
  [19.10] Boot hangs at "loading initial ramdisk"

Status in grub2 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [19.10] Boot hangs at "loading initial ramdisk"

  So after completing the upgrade from 19.04 to 19.10, my computer got
  stuck on the solid purple Grub screen upon reboot. After getting into
  the grub menu on next boot and booting from advanced options, I see
  that it gets to "loading initial ramdisk" and then just hangs forever.
  I am able to boot without issues on the old kernel (5.0.0-32-generic),
  but not the one that got installed with the upgrade
  (5.3.0-18-generic).

  Things I've tried based on what worked for other people who got this
  problem (though I haven't found anyone who has it specifically with
  19.10):

  acpi=off

  dis_ucode_ldr

  disabling secure boot

  recovery mode

  making sure all packages are up to date

  I'm kind of at a loss of what to do, other than just keep using the
  old kernel. (which presumably might cause problems at some point?)

  I'm posting this from Ubuntu 19.04, since upgrade from 19.04 to 19.10
  resulted in unable to boot system.

  Hardware Dell XPS 9550

  # dmidecode 3.2
  Getting SMBIOS data from sysfs.
  SMBIOS 2.8 present.
  91 structures occupying 5683 bytes.
  Table at 0x000E.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
Vendor: Dell Inc.
Version: 1.11.2
Release Date: 07/30/2019
Address: 0xF
Runtime Size: 64 kB
ROM Size: 16 MB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
Smart battery is supported
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 1.11

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
Manufacturer: Dell Inc.
Product Name: XPS 15 9550
Version: Not Specified
Serial Number: 5QRHRF2
UUID: 4c4c4544-0051-5210-8048-b5c04f524632
Wake-up Type: Power Switch
SKU Number: 06E4
Family: XPS

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
Manufacturer: Dell Inc.
Product Name: 0N7TVV
Version: A01
Serial Number: /5QRHRF2/CN129636CS0026/
Asset Tag: Not Specified
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: Not Specified
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0

  Handle 0x0003, DMI type 3, 22 bytes
  Chassis Information
Manufacturer: Dell Inc.
Type: Laptop
Lock: Not Present
Version: Not Specified
Serial Number: 5QRHRF2
Asset Tag: Not Specified
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
OEM Information: 0x
Height: Unspecified
Number Of Power Cords: 1
Contained Elements: 0
SKU Number: Laptop

  Handle 0x0004, DMI type 8, 9 bytes
  Port Connector Information
Internal Reference Designator: JUSB1
Internal Connector Type: None
External Reference Designator: USB1
External Connector Type: Access Bus (USB)
Port Type: USB

  Handle 0x0005, DMI type 8, 9 bytes
  Port Connector Information
Internal Reference Designator: JUSB2
Internal Connector Type: None
External Reference Designator: USB2
External Connector Type: Access Bus (USB)
Port Type: USB

  Handle 0x0006, DMI type 8, 9 bytes
  Port Connector Information
Internal Reference Designator: JUSBC1
Internal Connector Type: None
External Reference Designator: USB TYPEC
External Connector Type: Access Bus (USB)
Port Type: USB

  Handle 0x0007, DMI type 8, 9 bytes
  Port Connector Infor

[Kernel-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

2020-02-13 Thread Paolo Mainardi

Thanks for your reply @hui.wang

So, i've tried to change "name='Mic Boost Volume' 2"" all the LENOVO
files but nothing changed.

Your assumption about the cardlongname was right, because it seems that
is different from the versioned ones, mine is "LENOVO-20QD00LKIX-
ThinkPadX1Carbon7th-20QD00LKIX".

  pactl list cards
Card #0
Name: alsa_card.pci-_00_1f.3-platform-skl_hda_dsp_generic
Driver: module-alsa-card.c
Owner Module: 7
Properties:
alsa.card = "0"
alsa.card_name = "sof-skl_hda_card"
alsa.long_card_name = 
"LENOVO-20QD00LKIX-ThinkPadX1Carbon7th-20QD00LKIX"
alsa.driver_name = "snd_soc_skl_hda_dsp"
device.bus_path = 
"pci-:00:1f.3-platform-skl_hda_dsp_generic"
sysfs.path = 
"/devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "9dc8"
device.string = "0"
device.description = "sof-skl_hda_card"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
Profiles:
input:stereo-fallback: Stereo Input (sinks: 0, sources: 1, 
priority: 51, available: no)
input:multichannel-input: Multichannel Input (sinks: 0, 
sources: 1, priority: 1, available: yes)
output:stereo-fallback: Stereo Output (sinks: 1, sources: 0, 
priority: 5100, available: yes)
output:stereo-fallback+input:stereo-fallback: Stereo Output + 
Stereo Input (sinks: 1, sources: 1, priority: 5151, available: yes)
output:stereo-fallback+input:multichannel-input: Stereo Output 
+ Multichannel Input (sinks: 1, sources: 1, priority: 5101, available: yes)
output:multichannel-output: Multichannel Output (sinks: 1, 
sources: 0, priority: 100, available: yes)
output:multichannel-output+input:stereo-fallback: Multichannel 
Output + Stereo Input (sinks: 1, sources: 1, priority: 151, available: yes)
output:multichannel-output+input:multichannel-input: 
Multichannel Duplex (sinks: 1, sources: 1, priority: 101, available: yes)
off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
Active Profile: output:stereo-fallback+input:multichannel-input
Ports:
analog-input-mic: Microphone (priority: 8700, latency offset: 0 
usec, not available)
Properties:
device.icon_name = "audio-input-microphone"
Part of profile(s): input:stereo-fallback, 
output:stereo-fallback+input:stereo-fallback, 
output:multichannel-output+input:stereo-fallback
multichannel-input: Multichannel Input (priority: 0, latency 
offset: 0 usec)
Part of profile(s): input:multichannel-input, 
output:stereo-fallback+input:multichannel-input, 
output:multichannel-output+input:multichannel-input
analog-output-speaker: Speakers (priority: 1, latency 
offset: 0 usec)
Properties:
device.icon_name = "audio-speakers"
Part of profile(s): output:stereo-fallback, 
output:stereo-fallback+input:stereo-fallback, 
output:stereo-fallback+input:multichannel-input
analog-output-headphones: Headphones (priority: 9000, latency 
offset: 0 usec, not available)
Properties:
device.icon_name = "audio-headphones"
Part of profile(s): output:stereo-fallback, 
output:stereo-fallback+input:stereo-fallback, 
output:stereo-fallback+input:multichannel-input
multichannel-output: Multichannel Output (priority: 0, latency 
offset: 0 usec)
Part of profile(s): output:multichannel-output, 
output:multichannel-output+input:stereo-fallback, 
output:multichannel-output+input:multichannel-input

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

Title:
  add ucm to make alsa/sof driver work under PA (variants of Lenovo X1
  Carbon 7th, Dell cnl and cml machines)

Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Eoan:
  Fix Committed

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic

[Kernel-packages] [Bug 1861136] Re: bionic/linux-snapdragon: 4.15.0-1072.79 -proposed tracker

2020-02-13 Thread Andy Whitcroft

** 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 --
  boot-testing-requested: true
- kernel-stable-master-bug: '1862824'
+ kernel-stable-master-bug: 1862824
  packages:
-   main: linux-snapdragon
-   meta: linux-meta-snapdragon
+   main: linux-snapdragon
+   meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Tuesday, 11. February 2020 13:26 UTC
  reason:
-   certification-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
-   verification-testing: Ongoing -- testing in progress
+   certification-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  trackers:
-   bionic/linux-snapdragon/dragonboard-kernel: bug 1861135
+   bionic/linux-snapdragon/dragonboard-kernel: bug 1861135
  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/1861136

Title:
  bionic/linux-snapdragon: 4.15.0-1072.79 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon 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: 1862824
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Tuesday, 11. February 2020 13:26 UTC
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1861135
  variant: debs

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

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

[Kernel-packages] [Bug 1861162] Re: xenial/linux-deeplens: 4.15.0-1016.16 -proposed tracker

2020-02-13 Thread Andy Whitcroft

** 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 --
  boot-testing-requested: true
- kernel-stable-master-bug: '1862823'
+ kernel-stable-master-bug: 1862823
  packages:
-   main: linux-deeplens
-   meta: linux-meta-deeplens
+   main: linux-deeplens
+   meta: linux-meta-deeplens
  phase: Testing
  phase-changed: Wednesday, 05. February 2020 16:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Ongoing -- testing in progress
-   verification-testing: Ongoing -- testing in progress
+   certification-testing: Ongoing -- testing in progress
+   verification-testing: Ongoing -- testing in progress
  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/1861162

Title:
  xenial/linux-deeplens: 4.15.0-1016.16 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1862823
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
  phase: Testing
  phase-changed: Wednesday, 05. February 2020 16:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1861162] Re: xenial/linux-deeplens: 4.15.0-1016.16 -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: 1862823
  packages:
-   main: linux-deeplens
-   meta: linux-meta-deeplens
+   main: linux-deeplens
+   meta: linux-meta-deeplens
  phase: Testing
  phase-changed: Wednesday, 05. February 2020 16:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Ongoing -- testing in progress
-   verification-testing: Ongoing -- testing in progress
+   certification-testing: Ongoing -- testing in progress
+   verification-testing: Ongoing -- testing in progress
  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/1861162

Title:
  xenial/linux-deeplens: 4.15.0-1016.16 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1862823
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
  phase: Testing
  phase-changed: Wednesday, 05. February 2020 16:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1862980] Re: i2c-HTIX5288:00: i2c_hid_get_input: incomplete report

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6-rc1/

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

Title:
  i2c-HTIX5288:00: i2c_hid_get_input: incomplete report

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touchpad is spamming "i2c_hid_get_input: incomplete report" messages to 
dmesg and not working properly. Sometimes the left button acts like the right 
button. Sometimes it freezes completely. Also the keys to enable/disable 
touchpad (fn + f2) doesn't work.
  Also 'libinput list-devices' shows the following message: "event4  - 
HTIX5288:00 0911:5288 Touchpad: kernel bug: clickpad advertising right button"

  What's expected to happen?
   - The touchpad working properly.
  What's actually happening?
   - The touchpad not working properly.
  How to reproduce?
   - Start the computer and wait a few minutes.
  How to make the touchpad work normally for a few minutes (or seconds):
   - sudo rmmod i2c_hid && sudo modprobe i2c_hid

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-29-generic 5.3.0-29.31
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  username 1382 F pulseaudio
  Date: Wed Feb 12 13:11:15 2020
  InstallationDate: Installed on 2020-02-02 (10 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
   Bus 001 Device 004: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Positivo Tecnologia SA N1240
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=2656c128-b4f1-48e5-b1ef-79eea7a3280d ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: Desenvolvido por Positivo Tecnologia SA
  dmi.bios.version: V1.09.X
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: N14DP6
  dmi.board.vendor: Positivo Tecnologia SA
  dmi.board.version: 11139547
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Positivo Tecnologia SA
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnDesenvolvidoporPositivoTecnologiaSA:bvrV1.09.X:bd07/15/2019:svnPositivoTecnologiaSA:pnN1240:pvrTobefilledbyO.E.M.:rvnPositivoTecnologiaSA:rnN14DP6:rvr11139547:cvnPositivoTecnologiaSA:ct10:cvrTobefilledbyO.E.M.:
  dmi.product.family: MASTER
  dmi.product.name: N1240
  dmi.product.sku: 3052532
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Positivo Tecnologia SA

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

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

[Kernel-packages] [Bug 1862013] Re: bionic/linux-oem: 4.15.0-1071.81 -proposed tracker

2020-02-13 Thread AceLan Kao

** Summary changed:

- bionic/linux-oem: 4.15.0-1072.82 -proposed tracker
+ bionic/linux-oem: 4.15.0-1071.81 -proposed tracker

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

Title:
  bionic/linux-oem: 4.15.0-1071.81 -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:
  In Progress
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem 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: '1862824'
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Testing
  phase-changed: Tuesday, 11. February 2020 10:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  replaces: bug 1861137
  variant: debs

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

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

[Kernel-packages] [Bug 1861554] Re: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54

Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/Radeon

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

Title:
  Radeon mobility HD3450 (RV620) heavy screen flickering after trying to
  upgrade kernel 4.15.0-54

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450.
  Distro: Linux Mint 19.2 Tina base: Ubuntu 18.04 bionic.
  This happen trying any distro. I tried Ubuntu, Manjaro, Debian, Deepin, MX 
and so on.
  I'm stuck with Kernel 4.15.0-54 and 5.0.0-20 (and the contemporary 5.3 
kernel). I cannot upgrade to newer kernels.
  Seems that the fixes for bug #1791312 broke my kind of card.

  here is a video:
  https://youtu.be/9Rez7s0V6iA

  here is another user with same problem:
  https://forums.linuxmint.com/viewtopic.php?p=1702005#p1702005

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

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

[Kernel-packages] [Bug 1862013] Re: bionic/linux-oem: 4.15.0-1071.81 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => 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: '1862824'
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Testing
  phase-changed: Tuesday, 11. February 2020 10:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  replaces: bug 1861137
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1071.81 -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:
  In Progress
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem 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: '1862824'
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Testing
  phase-changed: Tuesday, 11. February 2020 10:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  replaces: bug 1861137
  variant: debs

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

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

[Kernel-packages] [Bug 1863072] [NEW] bionic/linux-oem: 4.15.0-1072.82 -proposed tracker

2020-02-13 Thread AceLan Kao

Public bug reported:

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

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

-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1862824
packages:
  lrm: linux-restricted-modules-oem
  main: linux-oem
  meta: linux-meta-oem
  signed: linux-signed-oem
phase: Ready for Promote to Proposed
phase-changed: Thursday, 13. February 2020 09:58 UTC
reason:
  promote-to-proposed: Pending -- ready for review
variant: debs

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

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

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: AceLan Kao (acelankao)
 Status: Fix Released

** Affects: kernel-sru-workflow/prepare-package-lrm
 Importance: Medium
 Assignee: AceLan Kao (acelankao)
 Status: Fix Released

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: AceLan Kao (acelankao)
 Status: Fix Released

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: AceLan Kao (acelankao)
 Status: Fix Released

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: Confirmed

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

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

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

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

** Affects: linux-oem (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic block-proposed block-proposed-bionic 
kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2020.01.27-5 kernel-sru-derivative-of-1862824

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

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

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

[Kernel-packages] [Bug 1862013] Re: bionic/linux-oem: 4.15.0-1071.81 -proposed tracker

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

** This bug has been marked a duplicate of bug 1863072
   bionic/linux-oem: 4.15.0-1072.82 -proposed tracker

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

Title:
  bionic/linux-oem: 4.15.0-1071.81 -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:
  In Progress
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem 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: '1862824'
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Testing
  phase-changed: Tuesday, 11. February 2020 10:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  replaces: bug 1861137
  variant: debs

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

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

[Kernel-packages] [Bug 1863072] Re: bionic/linux-oem: 4.15.0-1072.82 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package-lrm
   Status: New => Confirmed

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

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

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: Fix Committed => 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: 1862824
- replaces: bug 1862013
+ packages:
+   lrm: linux-restricted-modules-oem
+   main: linux-oem
+   meta: linux-meta-oem
+   signed: linux-signed-oem
+ phase: Ready for Promote to Proposed
+ phase-changed: Thursday, 13. February 2020 09:58 UTC
+ reason:
+   promote-to-proposed: Pending -- ready for review
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1072.82 -proposed tracker

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

Bug description:
  This bug 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: 1862824
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 13. February 2020 09:58 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  variant: debs

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

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

[Kernel-packages] [Bug 1861972] Re: [hns3-0205]sync mainline kernel 5.5rc7 hns3 patchset into ubuntu HWE kernel branch

** Changed in: kunpeng920/upstream-kernel
   Status: Fix Released => 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/1861972

Title:
  [hns3-0205]sync mainline kernel 5.5rc7 hns3 patchset into ubuntu HWE
  kernel branch

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  In Progress
Status in kunpeng920 upstream-kernel series:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Bug Description]
   hns3 patchset have merged into mainline 5.4rc7 kernel.
  [Steps to Reproduce]
    1)
    2)
    3)

  [Actual Results]

  [Expected Results]

  [Reproducibility]

  [Additional information]
    (Firmware version, kernel version, affected hardware, etc. if required):

  [Resolution]
  (Fix committed) net: hns3: cleanup some coding style issue
  (In progress) net: hns3: remove redundant print on ENOMEM
  (In progress) net: hns3: delete unnecessary blank line and space for cleanup
  (In progress) net: hns3: rewrite a log in hclge_put_vector()
  (In progress) net: hns3: refine the input parameter 'size' for snprintf()
  (In progress) net: hns3: move duplicated macro definition into header
  (In progress) net: hns3: set VF's default reset_type to HNAE3_NONE_RESET
  (In progress) net: hns3: do not reuse pfmemalloc pages
  (In progress) net: hns3: limit the error logging in the hns3_clean_tx_ring()
  (In progress) net: hns3: replace snprintf with scnprintf in 
hns3_update_strings
  (In progress) net: hns3: replace snprintf with scnprintf in hns3_dbg_cmd_read
  (Fix committed) net: hns3: pad the short frame before sending to the hardware

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

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

[Kernel-packages] [Bug 1854842] Re: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs

2020-02-13 Thread Mohammad Heib

** Tags removed: bot-comment seg verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
mlx5_core reports hardware checksum error for padded packets on
Mellanox NICs

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

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

[Impact]

enp6s0f0: hw csum failure
CPU: 19 PID: 0 Comm: swapper/19 Not tainted 4.15.0-72-generic
Call Trace:

This bug will also fix the same problems on the new Mellanox CX6 and
Bluefield hardware, which has been enabled already via previous
upstream -stable patches which landed in LP #1847155.

[Fix]

This particular issue was fixed for Mellanox series 5 drivers in the
following commits:

commit 0aa1d18615c163f92935b806dcaff9157645233a
Author: Saeed Mahameed
Date: Tue Mar 12 00:24:52 2019 -0700
Subject: net/mlx5e: Rx, Fixup skb checksum for packets with tail padding

This commit required a minor backport.

commit db849faa9bef993a1379dc510623f750a72fa7ce
Author: Saeed Mahameed
Date: Fri May 3 13:14:59 2019 -0700
Subject: net/mlx5e: Rx, Fix checksum calculation for new hardware

This commit required a minor backport.

This commit was selected for upstream -stable in 5.1.21 and 5.2.4.
This commit has already been applied to the disco kernel, as part of stable
updates.

[Testcase]

The following scapy script will reproduce this issue. Run from the
machine with the Mellanox series 5 NIC:

2) sendp(a, iface='enp6s0f0')

3) Check dmesg on the reciever side. The example uses localhost, so
check dmesg.

I have built some test kernels, which are available here:

https://launchpad.net/~mruffell/+archive/ubuntu/lp1854842-test
This kernel contains 0aa1d18615c163f92935b806dcaff9157645233a.

and

https://launchpad.net/~mruffell/+archive/ubuntu/lp1854842-test-2
This kernel contains db849faa9bef993a1379dc510623f750a72fa7ce.

If you install the test kernels the issue is resolved.

[Regression Potential]

The changes are limited to the mlx5_core driver, and only modify how
packet checksums are calculated when padding is involved.

Both patches have been accepted and published by upstream -stable, and
are widely accepted by the community.

Because of this, I believe the risk of regression is low.

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

[Kernel-packages] [Bug 1861976] Re: [acc-0205]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE kernel branch

** Changed in: kunpeng920/upstream-kernel
   Status: Fix Released => 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/1861976

Title:
  [acc-0205]sync mainline kernel 5.5rc6 hns3 patchset into ubuntu HWE
  kernel branch

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  In Progress
Status in kunpeng920 upstream-kernel series:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Bug Description]
  acc patchset have merged into mainline 5.5rc6 kernel. 
  [Steps to Reproduce]
1)
2)
3)

  [Actual Results]

  [Expected Results]

  [Reproducibility]

  [Additional information]
(Firmware version, kernel version, affected hardware, etc. if required):

  [Resolution]
  crypto: hisilicon - fix spelling mistake "disgest" -> "digest"
  crypto: hisilicon - add branch prediction macro
  crypto: hisilicon - adjust hpre_crt_para_get
  crypto: hisilicon - Fixed some tiny bugs of HPRE
  crypto: hisilicon - Bugfixed tfm leak
  crypto: hisilicon - Add aead support on SEC2
  crypto: hisilicon - redefine skcipher initiation
  crypto: hisilicon - Add branch prediction macro
  crypto: hisilicon - Add callback error check
  crypto: hisilicon - Adjust some inner logic
  crypto: hisilicon - Update QP resources of SEC V2
  crypto: hisilicon - Update some names on SEC V2
  crypto: hisilicon - fix print/comment of SEC V2
  crypto: hisilicon - Update debugfs usage of SEC V2

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

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

[Kernel-packages] [Bug 1862824] Re: bionic/linux: 4.15.0-88.88 -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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Wednesday, 12. February 2020 12:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1862808
bionic/linux-fips: bug 1861152
bionic/linux-gke-4.15: bug 1862810
bionic/linux-ibm-gt: bug 1862812
bionic/linux-kvm: bug 1862811
-   bionic/linux-oem: bug 1862013
+   bionic/linux-oem: bug 1863072, bug 1862013
bionic/linux-oracle: bug 1862814
bionic/linux-raspi2: bug 1861134
bionic/linux-snapdragon: bug 1861136
bionic/linux/pc-kernel: bug 1862803
bionic/linux/pc-lowlatency-kernel: bug 1862804
xenial/linux-azure: bug 1862818
xenial/linux-gcp: bug 1862821
xenial/linux-hwe: bug 1862823
  variant: debs

** 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: Testing
  phase-changed: Wednesday, 12. February 2020 12:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1862808
bionic/linux-fips: bug 1861152
bionic/linux-gke-4.15: bug 1862810
bionic/linux-ibm-gt: bug 1862812
bionic/linux-kvm: bug 1862811
-   bionic/linux-oem: bug 1863072, bug 1862013
+   bionic/linux-oem: bug 1863072
bionic/linux-oracle: bug 1862814
bionic/linux-raspi2: bug 1861134
bionic/linux-snapdragon: bug 1861136
bionic/linux/pc-kernel: bug 1862803
bionic/linux/pc-lowlatency-kernel: bug 1862804
xenial/linux-azure: bug 1862818
xenial/linux-gcp: bug 1862821
xenial/linux-hwe: bug 1862823
  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/1862824

Title:
  bionic/linux: 4.15.0-88.88 -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:
  In Progress
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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux 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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Wednesday, 12. February 2020 12:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1862808
bionic/linux-fips: bug 1861152
bionic/linux-gke-4.15: bug 1862810
bioni

[Kernel-packages] [Bug 1862749] Re: [UBUNTU 20.04] Thin Provisioning support (disablement or final solution)

2020-02-13 Thread bugproxy

** Tags removed: severity-high
** Tags added: severity-critical

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

Title:
  [UBUNTU 20.04] Thin Provisioning support (disablement or final
  solution)

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This pro-active fix is requested to provide the code for disablement
  of Thin Provisioning within Ubuntu 20.04, like within Ubuntu 19.10 or
  providing the final solution from upstream.

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

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

[Kernel-packages] [Bug 1863072] Re: bionic/linux-oem: 4.15.0-1072.82 -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: 1862824
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
- phase: Ready for Promote to Proposed
- phase-changed: Thursday, 13. February 2020 09:58 UTC
+ phase: Promote to Proposed
+ phase-changed: Thursday, 13. February 2020 10:16 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1072.82 -proposed tracker

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

Bug description:
  This bug 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: 1862824
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Thursday, 13. February 2020 10:16 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1863072] Re: bionic/linux-oem: 4.15.0-1072.82 -proposed tracker

2020-02-13 Thread Andy Whitcroft

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  bionic/linux-oem: 4.15.0-1072.82 -proposed tracker

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

Bug description:
  This bug 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: 1862824
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Thursday, 13. February 2020 10:16 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress
  variant: debs

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

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

[Kernel-packages] [Bug 1861192] Re: disco/linux: 5.0.0-41.45 -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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 30. January 2020 14:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-5.0: bug 1861179
bionic/linux-azure: bug 1862405
bionic/linux-bluefield: bug 1861188
bionic/linux-gcp: bug 1862213
bionic/linux-gke-5.0: bug 1861187
-   bionic/linux-oem-osp1: bug 1861178
+   bionic/linux-oem-osp1: bug 1861178, bug 1863082
bionic/linux-oracle-5.0: bug 1861190
  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/1861192

Title:
  disco/linux: 5.0.0-41.45 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 30. January 2020 14:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-5.0: bug 1861179
bionic/linux-azure: bug 1862405
bionic/linux-bluefield: bug 1861188
bionic/linux-gcp: bug 1862213
bionic/linux-gke-5.0: bug 1861187
bionic/linux-oem-osp1: bug 1861178, bug 1863082
bionic/linux-oracle-5.0: bug 1861190
  variant: debs

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

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

[Kernel-packages] [Bug 1825778] Re: False positive test result in run_afpackettests from net in ubuntu_kernel_selftest

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

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

Title:
  False positive test result in run_afpackettests from net in
  ubuntu_kernel_selftest

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Released

Bug description:
  == Justification ==
  The run_afpackettests will be marked as passed regardless the return
  value of those sub-tests in the script:
  
  running psock_tpacket test
  
  [FAIL]
  selftests: run_afpackettests [PASS]

  Fix this by changing the return value for each tests.

  == Fix ==
  * 8c03557 (selftests/net: correct the return value for run_afpackettests)

  This patch has alreay landed on newer releases and D with stable
  updates.
  For X and B this can be backported with the same logic.

  == Test ==
  Tested on a Xenial KVM with this patch applied on these two trees, when
  the test failed the return value will be 1 instead of 0 as expected.

  == Regression Potential ==
  * Low, it's just reflecting the real test return value. We may see this
  test failing on some kernels but it's good as it's reporting a real bug.

  
  == Original Bug Report ==
  The run_afpackettests will be marked as passed regardless the return
  value of those sub-tests in the script:
  
  running psock_tpacket test
  
  [FAIL]
  selftests: run_afpackettests [PASS]

  Fix this by changing the return value for each tests.

  Patch sent to upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1825778/+subscriptions

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

[Kernel-packages] [Bug 1850105] Re: ubuntu_k8s_unit_tests failed to build with cannot find package "context"

** Tags added: sru-20200127

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

Title:
  ubuntu_k8s_unit_tests failed to build with cannot find package
  "context"

Status in ubuntu-kernel-tests:
  New
Status in linux-signed-gcp package in Ubuntu:
  New

Bug description:
  Issue found on Xenial GCP testing.

  Test failed with:
vendor/k8s.io/client-go/rest/request.go:21:2: cannot find package "context" 
in any of:

/tmp/kubernetes.git/_output/local/go/src/k8s.io/kubernetes/vendor/context 
(vendor tree)
/usr/lib/go-1.6/src/context (from $GOROOT)
/tmp/kubernetes.git/_output/local/go/src/context (from $GOPATH)

  Complete test log:
   Running 'make test'
+++ [1023 18:04:28] Building the toolchain targets:
k8s.io/kubernetes/hack/cmd/teststale
k8s.io/kubernetes/vendor/github.com/jteeuwen/go-bindata/go-bindata
+++ [1023 18:04:30] Generating bindata:
test/e2e/generated/gobindata_util.go
/tmp/kubernetes.git /tmp/kubernetes.git/test/e2e/generated
/tmp/kubernetes.git/test/e2e/generated
+++ [1023 18:04:31] Building go targets for linux/amd64:
cmd/libs/go2idl/deepcopy-gen
+++ [1023 18:04:41] Building the toolchain targets:
k8s.io/kubernetes/hack/cmd/teststale
k8s.io/kubernetes/vendor/github.com/jteeuwen/go-bindata/go-bindata
+++ [1023 18:04:41] Generating bindata:
test/e2e/generated/gobindata_util.go
/tmp/kubernetes.git /tmp/kubernetes.git/test/e2e/generated
/tmp/kubernetes.git/test/e2e/generated
+++ [1023 18:04:41] Building go targets for linux/amd64:
cmd/libs/go2idl/defaulter-gen
+++ [1023 18:04:49] Building the toolchain targets:
k8s.io/kubernetes/hack/cmd/teststale
k8s.io/kubernetes/vendor/github.com/jteeuwen/go-bindata/go-bindata
+++ [1023 18:04:49] Generating bindata:
test/e2e/generated/gobindata_util.go
/tmp/kubernetes.git /tmp/kubernetes.git/test/e2e/generated
/tmp/kubernetes.git/test/e2e/generated
+++ [1023 18:04:50] Building go targets for linux/amd64:
cmd/libs/go2idl/conversion-gen
+++ [1023 18:04:59] Building the toolchain targets:
k8s.io/kubernetes/hack/cmd/teststale
k8s.io/kubernetes/vendor/github.com/jteeuwen/go-bindata/go-bindata
+++ [1023 18:04:59] Generating bindata:
test/e2e/generated/gobindata_util.go
/tmp/kubernetes.git /tmp/kubernetes.git/test/e2e/generated
/tmp/kubernetes.git/test/e2e/generated
+++ [1023 18:04:59] Building go targets for linux/amd64:
cmd/libs/go2idl/openapi-gen
Running tests for APIVersion: 
v1,apps/v1beta1,authentication.k8s.io/v1,authentication.k8s.io/v1beta1,authorization.k8s.io/v1,authorization.k8s.io/v1beta1,autoscaling/v1,autoscaling/v2alpha1,batch/v1,batch/v2alpha1,certificates.k8s.io/v1beta1,extensions/v1beta1,imagepolicy.k8s.io/v1alpha1,policy/v1beta1,rbac.authorization.k8s.io/v1beta1,rbac.authorization.k8s.io/v1alpha1,settings.k8s.io/v1alpha1,storage.k8s.io/v1beta1,storage.k8s.io/v1,federation/v1beta1
+++ [1023 18:05:14] Running tests without code coverage
vendor/k8s.io/client-go/rest/request.go:21:2: cannot find package "context" 
in any of:
/tmp/kubernetes.git/_output/local/go/src/k8s.io/kubernetes/vendor/context 
(vendor tree)
/usr/lib/go-1.6/src/context (from $GOROOT)
/tmp/kubernetes.git/_output/local/go/src/context (from $GOPATH)
!!! [1023 18:05:16] Call tree:
Makefile:164: recipe for target 'test' failed
!!! [1023 18:05:16] 1: hack/make-rules/test.sh:343 runTests(...)
make: *** [test] Error 1

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.15.0-1047-gcp 4.15.0-1047.50
  ProcVersionSignature: Ubuntu 4.15.0-1047.50-gcp 4.15.18
  Uname: Linux 4.15.0-1047-gcp x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Mon Oct 28 04:54:34 2019
  SourcePackage: linux-signed-gcp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1850105/+subscriptions

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

[Kernel-packages] [Bug 1862821] Re: xenial/linux-gcp: 4.15.0-1055.59 -proposed tracker

4.15.0-1055.59 - gcp
Regression test CMPL, RTB.

Issue to note in gcp:
  ubuntu_k8s_unit_tests - test failed with context package not found in go (bug 
1850105)
  ubuntu_ltp_syscalls - quotactl04 (bug 1854153) statx05 (bug 1798524)

Skipped / blacklisted:
 * ubuntu_ltp

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

Title:
  xenial/linux-gcp: 4.15.0-1055.59 -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-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  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: 1862824
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Wednesday, 12. February 2020 15:58 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-gcp/gcp-kernel: bug 1862819
xenial/linux-gcp/gke-kernel: bug 1862820
  variant: debs

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

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

[Kernel-packages] [Bug 1862821] Re: xenial/linux-gcp: 4.15.0-1055.59 -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: 1862824
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Wednesday, 12. February 2020 15:58 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-gcp/gcp-kernel: bug 1862819
xenial/linux-gcp/gke-kernel: bug 1862820
  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/1862821

Title:
  xenial/linux-gcp: 4.15.0-1055.59 -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-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  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: 1862824
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Wednesday, 12. February 2020 15:58 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-gcp/gcp-kernel: bug 1862819
xenial/linux-gcp/gke-kernel: bug 1862820
  variant: debs

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

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

Re: [Kernel-packages] [Bug 1861554] Re: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54

2020-02-13 Thread Diego Maniacco

hoi: got "freedesktop.org Bugzilla is no longer in use".

---
Diego Maniacco, Bolzano (Italy)
diego.mania...@gmail.com
---

[image: Not f'd — you won't find me on Facebook] 
Not f'd — you won't find me on Facebook


On Thu, 13 Feb 2020 at 10:56, Kai-Heng Feng 
wrote:

> Please file an upstream bug at https://bugs.freedesktop.org/
> Product: DRI
> Component: DRM/Radeon
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1861554
>
> Title:
>   Radeon mobility HD3450 (RV620) heavy screen flickering after trying to
>   upgrade kernel 4.15.0-54
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450.
>   Distro: Linux Mint 19.2 Tina base: Ubuntu 18.04 bionic.
>   This happen trying any distro. I tried Ubuntu, Manjaro, Debian, Deepin,
> MX and so on.
>   I'm stuck with Kernel 4.15.0-54 and 5.0.0-20 (and the contemporary 5.3
> kernel). I cannot upgrade to newer kernels.
>   Seems that the fixes for bug #1791312 broke my kind of card.
>
>   here is a video:
>   https://youtu.be/9Rez7s0V6iA
>
>   here is another user with same problem:
>   https://forums.linuxmint.com/viewtopic.php?p=1702005#p1702005
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861554/+subscriptions
>

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

Title:
  Radeon mobility HD3450 (RV620) heavy screen flickering after trying to
  upgrade kernel 4.15.0-54

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450.
  Distro: Linux Mint 19.2 Tina base: Ubuntu 18.04 bionic.
  This happen trying any distro. I tried Ubuntu, Manjaro, Debian, Deepin, MX 
and so on.
  I'm stuck with Kernel 4.15.0-54 and 5.0.0-20 (and the contemporary 5.3 
kernel). I cannot upgrade to newer kernels.
  Seems that the fixes for bug #1791312 broke my kind of card.

  here is a video:
  https://youtu.be/9Rez7s0V6iA

  here is another user with same problem:
  https://forums.linuxmint.com/viewtopic.php?p=1702005#p1702005

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

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

[Kernel-packages] [Bug 1862821] Re: xenial/linux-gcp: 4.15.0-1055.59 -proposed tracker

4.15.0-1055.59 - gcp
Regression test CMPL, RTB.

Issue to note in gcp:
  ubuntu_k8s_unit_tests - test failed with context package not found in go (bug 
1850105)
  ubuntu_ltp_syscalls - quotactl04 (bug 1854153) statx05 (bug 1798524)

Skipped / blacklisted:
 * ubuntu_ltp

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

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

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

Title:
  xenial/linux-gcp: 4.15.0-1055.59 -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-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  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: 1862824
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Wednesday, 12. February 2020 15:58 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-gcp/gcp-kernel: bug 1862819
xenial/linux-gcp/gke-kernel: bug 1862820
  variant: debs

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

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

[Kernel-packages] [Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"

2020-02-13 Thread You-Sheng Yang

For XPS 15 9550:

$ dmesg |grep microcode
[0.00] microcode: microcode updated early to revision 0xd6, date = 
2019-10-03
[1.948537] microcode: sig=0x506e3, pf=0x20, revision=0xd6
[1.950991] microcode: Microcode Update Driver: v2.2.

$ dpkg -l|grep micro
ii  amd64-microcode
3.20191021.1+really3.20181128.1ubuntu1.1 amd64Processor microcode 
firmware for AMD CPUs
ii  intel-microcode3.20191115.1ubuntu0.19.04.2  
amd64Processor microcode firmware for Intel CPUs

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

Title:
  [19.10] Boot hangs at "loading initial ramdisk"

Status in intel-microcode package in Ubuntu:
  In Progress

Bug description:
  [19.10] Boot hangs at "loading initial ramdisk"

  So after completing the upgrade from 19.04 to 19.10, my computer got
  stuck on the solid purple Grub screen upon reboot. After getting into
  the grub menu on next boot and booting from advanced options, I see
  that it gets to "loading initial ramdisk" and then just hangs forever.
  I am able to boot without issues on the old kernel (5.0.0-32-generic),
  but not the one that got installed with the upgrade
  (5.3.0-18-generic).

  Things I've tried based on what worked for other people who got this
  problem (though I haven't found anyone who has it specifically with
  19.10):

  acpi=off

  dis_ucode_ldr

  disabling secure boot

  recovery mode

  making sure all packages are up to date

  I'm kind of at a loss of what to do, other than just keep using the
  old kernel. (which presumably might cause problems at some point?)

  I'm posting this from Ubuntu 19.04, since upgrade from 19.04 to 19.10
  resulted in unable to boot system.

  Hardware Dell XPS 9550

  # dmidecode 3.2
  Getting SMBIOS data from sysfs.
  SMBIOS 2.8 present.
  91 structures occupying 5683 bytes.
  Table at 0x000E.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
Vendor: Dell Inc.
Version: 1.11.2
Release Date: 07/30/2019
Address: 0xF
Runtime Size: 64 kB
ROM Size: 16 MB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
Smart battery is supported
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 1.11

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
Manufacturer: Dell Inc.
Product Name: XPS 15 9550
Version: Not Specified
Serial Number: 5QRHRF2
UUID: 4c4c4544-0051-5210-8048-b5c04f524632
Wake-up Type: Power Switch
SKU Number: 06E4
Family: XPS

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
Manufacturer: Dell Inc.
Product Name: 0N7TVV
Version: A01
Serial Number: /5QRHRF2/CN129636CS0026/
Asset Tag: Not Specified
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: Not Specified
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0

  Handle 0x0003, DMI type 3, 22 bytes
  Chassis Information
Manufacturer: Dell Inc.
Type: Laptop
Lock: Not Present
Version: Not Specified
Serial Number: 5QRHRF2
Asset Tag: Not Specified
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
OEM Information: 0x
Height: Unspecified
Number Of Power Cords: 1
Contained Elements: 0
SKU Number: Laptop

  Handle 0x0004, DMI type 8, 9 bytes
  Port Connector Information
Internal Reference Designator: JUSB1
Internal Connector Type: None
External Reference Designator: USB1
External Connector Type: Access Bus (USB)
Port Type: USB

  Handle 0x0005, DMI type 8, 9 bytes
  Port Connector Information
Internal Reference Des

[Kernel-packages] [Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"

2020-02-13 Thread You-Sheng Yang

To be fixed in bug 1862751 together.

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Also affects: intel-microcode (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: linux (Ubuntu)

** No longer affects: grub2 (Ubuntu)

** Changed in: intel-microcode (Ubuntu)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: intel-microcode (Ubuntu)
   Status: New => In Progress

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

Title:
  [19.10] Boot hangs at "loading initial ramdisk"

Status in intel-microcode package in Ubuntu:
  In Progress

Bug description:
  [19.10] Boot hangs at "loading initial ramdisk"

  So after completing the upgrade from 19.04 to 19.10, my computer got
  stuck on the solid purple Grub screen upon reboot. After getting into
  the grub menu on next boot and booting from advanced options, I see
  that it gets to "loading initial ramdisk" and then just hangs forever.
  I am able to boot without issues on the old kernel (5.0.0-32-generic),
  but not the one that got installed with the upgrade
  (5.3.0-18-generic).

  Things I've tried based on what worked for other people who got this
  problem (though I haven't found anyone who has it specifically with
  19.10):

  acpi=off

  dis_ucode_ldr

  disabling secure boot

  recovery mode

  making sure all packages are up to date

  I'm kind of at a loss of what to do, other than just keep using the
  old kernel. (which presumably might cause problems at some point?)

  I'm posting this from Ubuntu 19.04, since upgrade from 19.04 to 19.10
  resulted in unable to boot system.

  Hardware Dell XPS 9550

  # dmidecode 3.2
  Getting SMBIOS data from sysfs.
  SMBIOS 2.8 present.
  91 structures occupying 5683 bytes.
  Table at 0x000E.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
Vendor: Dell Inc.
Version: 1.11.2
Release Date: 07/30/2019
Address: 0xF
Runtime Size: 64 kB
ROM Size: 16 MB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
Smart battery is supported
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 1.11

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
Manufacturer: Dell Inc.
Product Name: XPS 15 9550
Version: Not Specified
Serial Number: 5QRHRF2
UUID: 4c4c4544-0051-5210-8048-b5c04f524632
Wake-up Type: Power Switch
SKU Number: 06E4
Family: XPS

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
Manufacturer: Dell Inc.
Product Name: 0N7TVV
Version: A01
Serial Number: /5QRHRF2/CN129636CS0026/
Asset Tag: Not Specified
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: Not Specified
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0

  Handle 0x0003, DMI type 3, 22 bytes
  Chassis Information
Manufacturer: Dell Inc.
Type: Laptop
Lock: Not Present
Version: Not Specified
Serial Number: 5QRHRF2
Asset Tag: Not Specified
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
OEM Information: 0x
Height: Unspecified
Number Of Power Cords: 1
Contained Elements: 0
SKU Number: Laptop

  Handle 0x0004, DMI type 8, 9 bytes
  Port Connector Information
Internal Reference Designator: JUSB1
Internal Connector Type: None
External Reference Designator: USB1
External Connector Type: Access Bus (USB)
Port Type: USB

  Handle 0x0005, DMI type 8, 9 bytes
  Port Connector Information
Internal Reference Designator: JUSB2
Internal Connector Type: None
External Reference Designator: USB2

[Kernel-packages] [Bug 1863072] Re: bionic/linux-oem: 4.15.0-1072.82 -proposed tracker

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

** 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: 1862824
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Thursday, 13. February 2020 10:16 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  variant: debs

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

Title:
  bionic/linux-oem: 4.15.0-1072.82 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-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 Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

Bug description:
  This bug 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: 1862824
  packages:
lrm: linux-restricted-modules-oem
main: linux-oem
meta: linux-meta-oem
signed: linux-signed-oem
  phase: Promote to Proposed
  phase-changed: Thursday, 13. February 2020 10:16 UTC
  reason:
promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait
  variant: debs

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

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

[Kernel-packages] [Bug 1863086] [NEW] unkillable process (kernel NULL pointer dereference)

2020-02-13 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

If process that listens socket on any port crashes (segmentation fault) it 
becomes unkillable.
Kill command does not kill this process.
Port that listen crashed process never be freed.

journalctl shows error:

Feb 13 13:28:09 vbun04 kernel: socktest[1359]: segfault at 21 ip 
55ec3a6bf11e sp 7ffd88899fb0 error 6 in socktest[55ec3a6bf000+1000]
Feb 13 13:28:09 vbun04 kernel: Code: 04 24 02 00 17 70 89 c5 48 b8 30 30 30 30 
30 30 30 30 89 ef 48 89 44 24 08 e8 8e ff ff ff be 0a 00 00 00 89 ef e8 72 ff 
ff ff  04 25 21 00 00 00 21 00 00 00 48 8b 44 24 18
Feb 13 13:28:09 vbun04 kernel: BUG: kernel NULL pointer dereference, address: 
0020
Feb 13 13:28:09 vbun04 kernel: #PF: supervisor read access in kernel mode
Feb 13 13:28:09 vbun04 kernel: #PF: error_code(0x) - not-present page
Feb 13 13:28:09 vbun04 kernel: PGD 0 P4D 0
Feb 13 13:28:09 vbun04 kernel: Oops:  [#1] SMP NOPTI
Feb 13 13:28:09 vbun04 kernel: CPU: 1 PID: 1359 Comm: socktest Tainted: G   
OE 5.3.0-29-generic #31-Ubuntu
Feb 13 13:28:09 vbun04 kernel: Hardware name: innotek GmbH 
VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
Feb 13 13:28:09 vbun04 kernel: RIP: 0010:do_coredump+0x536/0xb30
Feb 13 13:28:09 vbun04 kernel: Code: 00 48 8b bd 18 ff ff ff 48 85 ff 74 05 e8 
c2 47 fa ff 65 48 8b 04 25 c0 6b 01 00 48 8b 00 48 8b 7d a0 a8 04 0f 85 65 05 
00 00 <48> 8b 57 20 0f b7 02 66 25 00 f0 66 3d 00 80 0f
Feb 13 13:28:09 vbun04 kernel: RSP: :b464c2c5fca8 EFLAGS: 00010246
Feb 13 13:28:09 vbun04 kernel: RAX:  RBX: 9d4b76995100 RCX: 
1afc
Feb 13 13:28:09 vbun04 kernel: RDX:  RSI: b464c2c5fc68 RDI: 

Feb 13 13:28:09 vbun04 kernel: RBP: b464c2c5fdd8 R08: 0400 R09: 
b464c2c5fbe0
Feb 13 13:28:09 vbun04 kernel: R10: 9d4b75d01170 R11:  R12: 
9d4b7b3df540
Feb 13 13:28:09 vbun04 kernel: R13: 0001 R14:  R15: 
b9f15920
Feb 13 13:28:09 vbun04 kernel: FS:  7f6c91911540() 
GS:9d4b7db0() knlGS:
Feb 13 13:28:09 vbun04 kernel: CS:  0010 DS:  ES:  CR0: 80050033
Feb 13 13:28:09 vbun04 kernel: CR2: 0020 CR3: 723ac003 CR4: 
000606e0
Feb 13 13:28:09 vbun04 kernel: Call Trace:
Feb 13 13:28:09 vbun04 kernel:  ? wake_up_state+0x10/0x20
Feb 13 13:28:09 vbun04 kernel:  ? __send_signal+0x1eb/0x3f0
Feb 13 13:28:09 vbun04 kernel:  get_signal+0x159/0x880
Feb 13 13:28:09 vbun04 kernel:  do_signal+0x34/0x280
Feb 13 13:28:09 vbun04 kernel:  ? bad_area+0x47/0x50
Feb 13 13:28:09 vbun04 kernel:  exit_to_usermode_loop+0xbf/0x160
Feb 13 13:28:09 vbun04 kernel:  prepare_exit_to_usermode+0x77/0xa0
Feb 13 13:28:09 vbun04 kernel:  retint_user+0x8/0x8
Feb 13 13:28:09 vbun04 kernel: RIP: 0033:0x55ec3a6bf11e
Feb 13 13:28:09 vbun04 kernel: Code: 04 24 02 00 17 70 89 c5 48 b8 30 30 30 30 
30 30 30 30 89 ef 48 89 44 24 08 e8 8e ff ff ff be 0a 00 00 00 89 ef e8 72 ff 
ff ff  04 25 21 00 00 00 21 00 00 00 48 8b 44 24 18
Feb 13 13:28:09 vbun04 kernel: RSP: 002b:7ffd88899fb0 EFLAGS: 00010217
Feb 13 13:28:09 vbun04 kernel: RAX:  RBX:  RCX: 
7f6c918424eb
Feb 13 13:28:09 vbun04 kernel: RDX: 0010 RSI: 000a RDI: 
0003
Feb 13 13:28:09 vbun04 kernel: RBP: 0003 R08:  R09: 
7f6c919331f0
Feb 13 13:28:09 vbun04 kernel: R10:  R11: 0217 R12: 
55ec3a6bf150
Feb 13 13:28:09 vbun04 kernel: R13: 7ffd8889a0b0 R14:  R15: 

Feb 13 13:28:09 vbun04 kernel: Modules linked in: vboxsf(OE) nls_utf8 isofs 
vboxvideo(OE) intel_rapl_msr intel_rapl_common crct10dif_pclmul vmwgfx 
crc32_pclmul ghash_clmulni_intel aesni_intel ttm drm_kms_helper a
Feb 13 13:28:09 vbun04 kernel: CR2: 0020
Feb 13 13:28:09 vbun04 kernel: ---[ end trace 278d665c8727286a ]---
Feb 13 13:28:09 vbun04 kernel: RIP: 0010:do_coredump+0x536/0xb30
Feb 13 13:28:09 vbun04 kernel: Code: 00 48 8b bd 18 ff ff ff 48 85 ff 74 05 e8 
c2 47 fa ff 65 48 8b 04 25 c0 6b 01 00 48 8b 00 48 8b 7d a0 a8 04 0f 85 65 05 
00 00 <48> 8b 57 20 0f b7 02 66 25 00 f0 66 3d 00 80 0f
Feb 13 13:28:09 vbun04 kernel: RSP: :b464c2c5fca8 EFLAGS: 00010246
Feb 13 13:28:09 vbun04 kernel: RAX:  RBX: 9d4b76995100 RCX: 
1afc
Feb 13 13:28:09 vbun04 kernel: RDX:  RSI: b464c2c5fc68 RDI: 

Feb 13 13:28:09 vbun04 kernel: RBP: b464c2c5fdd8 R08: 0400 R09: 
b464c2c5fbe0
Feb 13 13:28:09 vbun04 kernel: R10: 9d4b75d01170 R11:  R12: 
9d4b7b3df540
Feb 13 13:28:09 vbun04 kernel: R13: 0001 R14:  R15: 
b9f15920
Feb 13 13:28:09 vbun04 kernel: FS:  7f6c91911540() 
GS:9d4b7db0() knlGS:
Feb 13 13:28:09 vbun04 kernel: CS:  0010 DS:  ES: 00

[Kernel-packages] [Bug 1863092] [NEW] Testing node with B-FIPS will complain "Unknown error executing apt-key"

Public bug reported:

B-FIPS testing node will complain about "Unknown error executing apt-
key" when running the apt update command.

This issue does not exist in X-FIPS.
Not sure what's the cause.

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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


** Tags: 4.15 bionic fips

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Tags added: bionic fips

** Tags added: 4.15

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

Title:
  Testing node with B-FIPS will complain "Unknown error executing apt-
  key"

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  B-FIPS testing node will complain about "Unknown error executing apt-
  key" when running the apt update command.

  This issue does not exist in X-FIPS.
  Not sure what's the cause.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1863092/+subscriptions

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

[Kernel-packages] [Bug 1863086] Re: unkillable process (kernel NULL pointer dereference)

2020-02-13 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  unkillable process (kernel NULL pointer dereference)

Status in linux package in Ubuntu:
  New

Bug description:
  If process that listens socket on any port crashes (segmentation fault) it 
becomes unkillable.
  Kill command does not kill this process.
  Port that listen crashed process never be freed.

  journalctl shows error:

  Feb 13 13:28:09 vbun04 kernel: socktest[1359]: segfault at 21 ip 
55ec3a6bf11e sp 7ffd88899fb0 error 6 in socktest[55ec3a6bf000+1000]
  Feb 13 13:28:09 vbun04 kernel: Code: 04 24 02 00 17 70 89 c5 48 b8 30 30 30 
30 30 30 30 30 89 ef 48 89 44 24 08 e8 8e ff ff ff be 0a 00 00 00 89 ef e8 72 
ff ff ff  04 25 21 00 00 00 21 00 00 00 48 8b 44 24 18
  Feb 13 13:28:09 vbun04 kernel: BUG: kernel NULL pointer dereference, address: 
0020
  Feb 13 13:28:09 vbun04 kernel: #PF: supervisor read access in kernel mode
  Feb 13 13:28:09 vbun04 kernel: #PF: error_code(0x) - not-present page
  Feb 13 13:28:09 vbun04 kernel: PGD 0 P4D 0
  Feb 13 13:28:09 vbun04 kernel: Oops:  [#1] SMP NOPTI
  Feb 13 13:28:09 vbun04 kernel: CPU: 1 PID: 1359 Comm: socktest Tainted: G 
  OE 5.3.0-29-generic #31-Ubuntu
  Feb 13 13:28:09 vbun04 kernel: Hardware name: innotek GmbH 
VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
  Feb 13 13:28:09 vbun04 kernel: RIP: 0010:do_coredump+0x536/0xb30
  Feb 13 13:28:09 vbun04 kernel: Code: 00 48 8b bd 18 ff ff ff 48 85 ff 74 05 
e8 c2 47 fa ff 65 48 8b 04 25 c0 6b 01 00 48 8b 00 48 8b 7d a0 a8 04 0f 85 65 
05 00 00 <48> 8b 57 20 0f b7 02 66 25 00 f0 66 3d 00 80 0f
  Feb 13 13:28:09 vbun04 kernel: RSP: :b464c2c5fca8 EFLAGS: 00010246
  Feb 13 13:28:09 vbun04 kernel: RAX:  RBX: 9d4b76995100 
RCX: 1afc
  Feb 13 13:28:09 vbun04 kernel: RDX:  RSI: b464c2c5fc68 
RDI: 
  Feb 13 13:28:09 vbun04 kernel: RBP: b464c2c5fdd8 R08: 0400 
R09: b464c2c5fbe0
  Feb 13 13:28:09 vbun04 kernel: R10: 9d4b75d01170 R11:  
R12: 9d4b7b3df540
  Feb 13 13:28:09 vbun04 kernel: R13: 0001 R14:  
R15: b9f15920
  Feb 13 13:28:09 vbun04 kernel: FS:  7f6c91911540() 
GS:9d4b7db0() knlGS:
  Feb 13 13:28:09 vbun04 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Feb 13 13:28:09 vbun04 kernel: CR2: 0020 CR3: 723ac003 
CR4: 000606e0
  Feb 13 13:28:09 vbun04 kernel: Call Trace:
  Feb 13 13:28:09 vbun04 kernel:  ? wake_up_state+0x10/0x20
  Feb 13 13:28:09 vbun04 kernel:  ? __send_signal+0x1eb/0x3f0
  Feb 13 13:28:09 vbun04 kernel:  get_signal+0x159/0x880
  Feb 13 13:28:09 vbun04 kernel:  do_signal+0x34/0x280
  Feb 13 13:28:09 vbun04 kernel:  ? bad_area+0x47/0x50
  Feb 13 13:28:09 vbun04 kernel:  exit_to_usermode_loop+0xbf/0x160
  Feb 13 13:28:09 vbun04 kernel:  prepare_exit_to_usermode+0x77/0xa0
  Feb 13 13:28:09 vbun04 kernel:  retint_user+0x8/0x8
  Feb 13 13:28:09 vbun04 kernel: RIP: 0033:0x55ec3a6bf11e
  Feb 13 13:28:09 vbun04 kernel: Code: 04 24 02 00 17 70 89 c5 48 b8 30 30 30 
30 30 30 30 30 89 ef 48 89 44 24 08 e8 8e ff ff ff be 0a 00 00 00 89 ef e8 72 
ff ff ff  04 25 21 00 00 00 21 00 00 00 48 8b 44 24 18
  Feb 13 13:28:09 vbun04 kernel: RSP: 002b:7ffd88899fb0 EFLAGS: 00010217
  Feb 13 13:28:09 vbun04 kernel: RAX:  RBX:  
RCX: 7f6c918424eb
  Feb 13 13:28:09 vbun04 kernel: RDX: 0010 RSI: 000a 
RDI: 0003
  Feb 13 13:28:09 vbun04 kernel: RBP: 0003 R08:  
R09: 7f6c919331f0
  Feb 13 13:28:09 vbun04 kernel: R10:  R11: 0217 
R12: 55ec3a6bf150
  Feb 13 13:28:09 vbun04 kernel: R13: 7ffd8889a0b0 R14:  
R15: 
  Feb 13 13:28:09 vbun04 kernel: Modules linked in: vboxsf(OE) nls_utf8 isofs 
vboxvideo(OE) intel_rapl_msr intel_rapl_common crct10dif_pclmul vmwgfx 
crc32_pclmul ghash_clmulni_intel aesni_intel ttm drm_kms_helper a
  Feb 13 13:28:09 vbun04 kernel: CR2: 0020
  Feb 13 13:28:09 vbun04 kernel: ---[ end trace 278d665c8727286a ]---
  Feb 13 13:28:09 vbun04 kernel: RIP: 0010:do_coredump+0x536/0xb30
  Feb 13 13:28:09 vbun04 kernel: Code: 00 48 8b bd 18 ff ff ff 48 85 ff 74 05 
e8 c2 47 fa ff 65 48 8b 04 25 c0 6b 01 00 48 8b 00 48 8b 7d a0 a8 04 0f 85 65 
05 00 00 <48> 8b 57 20 0f b7 02 66 25 00 f0 66 3d 00 80 0f
  Feb 13 13:28:09 vbun04 kernel: RSP: :b464c2c5fca8 EFLAGS: 00010246
  Feb 13 13:28:09 vbun04 kernel: RAX:  RBX: 9d4b76995100 
RCX: 1afc
  Feb 13 13:28:09 vbun04 kernel: RDX:  RSI: b464c2c5fc68 
RDI: 
  Feb 13 13:28:09 vbun04 kernel: RBP: b464c2c5fdd8 R08: 00

[Kernel-packages] [Bug 1862806] Re: bionic/linux-aws-fips: 4.15.0-2009.9 -proposed tracker

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => 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: 1862808
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
- phase: Promote to Proposed
- phase-changed: Thursday, 13. February 2020 00:17 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Thursday, 13. February 2020 12:16 UTC
  reason:
-   promote-to-proposed: Pending -- package copied to Signing 
signed:retry-needed
+   promote-signing-to-proposed: Pending -- ready for review
  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/1862806

Title:
  bionic/linux-aws-fips: 4.15.0-2009.9 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
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-signing-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1862808
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 13. February 2020 12:16 UTC
  reason:
promote-signing-to-proposed: Pending -- ready for review
  variant: debs

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

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

[Kernel-packages] [Bug 1863092] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1863092

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Testing node with B-FIPS will complain "Unknown error executing apt-
  key"

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  B-FIPS testing node will complain about "Unknown error executing apt-
  key" when running the apt update command.

  This issue does not exist in X-FIPS.
  Not sure what's the cause.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1863092/+subscriptions

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

[Kernel-packages] [Bug 1863086] Status changed to Confirmed

This change was made by a bot.

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

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

Title:
  unkillable process (kernel NULL pointer dereference)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  If process that listens socket on any port crashes (segmentation fault) it 
becomes unkillable.
  Kill command does not kill this process.
  Port that listen crashed process never be freed.

  journalctl shows error:

  Feb 13 13:28:09 vbun04 kernel: socktest[1359]: segfault at 21 ip 
55ec3a6bf11e sp 7ffd88899fb0 error 6 in socktest[55ec3a6bf000+1000]
  Feb 13 13:28:09 vbun04 kernel: Code: 04 24 02 00 17 70 89 c5 48 b8 30 30 30 
30 30 30 30 30 89 ef 48 89 44 24 08 e8 8e ff ff ff be 0a 00 00 00 89 ef e8 72 
ff ff ff  04 25 21 00 00 00 21 00 00 00 48 8b 44 24 18
  Feb 13 13:28:09 vbun04 kernel: BUG: kernel NULL pointer dereference, address: 
0020
  Feb 13 13:28:09 vbun04 kernel: #PF: supervisor read access in kernel mode
  Feb 13 13:28:09 vbun04 kernel: #PF: error_code(0x) - not-present page
  Feb 13 13:28:09 vbun04 kernel: PGD 0 P4D 0
  Feb 13 13:28:09 vbun04 kernel: Oops:  [#1] SMP NOPTI
  Feb 13 13:28:09 vbun04 kernel: CPU: 1 PID: 1359 Comm: socktest Tainted: G 
  OE 5.3.0-29-generic #31-Ubuntu
  Feb 13 13:28:09 vbun04 kernel: Hardware name: innotek GmbH 
VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
  Feb 13 13:28:09 vbun04 kernel: RIP: 0010:do_coredump+0x536/0xb30
  Feb 13 13:28:09 vbun04 kernel: Code: 00 48 8b bd 18 ff ff ff 48 85 ff 74 05 
e8 c2 47 fa ff 65 48 8b 04 25 c0 6b 01 00 48 8b 00 48 8b 7d a0 a8 04 0f 85 65 
05 00 00 <48> 8b 57 20 0f b7 02 66 25 00 f0 66 3d 00 80 0f
  Feb 13 13:28:09 vbun04 kernel: RSP: :b464c2c5fca8 EFLAGS: 00010246
  Feb 13 13:28:09 vbun04 kernel: RAX:  RBX: 9d4b76995100 
RCX: 1afc
  Feb 13 13:28:09 vbun04 kernel: RDX:  RSI: b464c2c5fc68 
RDI: 
  Feb 13 13:28:09 vbun04 kernel: RBP: b464c2c5fdd8 R08: 0400 
R09: b464c2c5fbe0
  Feb 13 13:28:09 vbun04 kernel: R10: 9d4b75d01170 R11:  
R12: 9d4b7b3df540
  Feb 13 13:28:09 vbun04 kernel: R13: 0001 R14:  
R15: b9f15920
  Feb 13 13:28:09 vbun04 kernel: FS:  7f6c91911540() 
GS:9d4b7db0() knlGS:
  Feb 13 13:28:09 vbun04 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Feb 13 13:28:09 vbun04 kernel: CR2: 0020 CR3: 723ac003 
CR4: 000606e0
  Feb 13 13:28:09 vbun04 kernel: Call Trace:
  Feb 13 13:28:09 vbun04 kernel:  ? wake_up_state+0x10/0x20
  Feb 13 13:28:09 vbun04 kernel:  ? __send_signal+0x1eb/0x3f0
  Feb 13 13:28:09 vbun04 kernel:  get_signal+0x159/0x880
  Feb 13 13:28:09 vbun04 kernel:  do_signal+0x34/0x280
  Feb 13 13:28:09 vbun04 kernel:  ? bad_area+0x47/0x50
  Feb 13 13:28:09 vbun04 kernel:  exit_to_usermode_loop+0xbf/0x160
  Feb 13 13:28:09 vbun04 kernel:  prepare_exit_to_usermode+0x77/0xa0
  Feb 13 13:28:09 vbun04 kernel:  retint_user+0x8/0x8
  Feb 13 13:28:09 vbun04 kernel: RIP: 0033:0x55ec3a6bf11e
  Feb 13 13:28:09 vbun04 kernel: Code: 04 24 02 00 17 70 89 c5 48 b8 30 30 30 
30 30 30 30 30 89 ef 48 89 44 24 08 e8 8e ff ff ff be 0a 00 00 00 89 ef e8 72 
ff ff ff  04 25 21 00 00 00 21 00 00 00 48 8b 44 24 18
  Feb 13 13:28:09 vbun04 kernel: RSP: 002b:7ffd88899fb0 EFLAGS: 00010217
  Feb 13 13:28:09 vbun04 kernel: RAX:  RBX:  
RCX: 7f6c918424eb
  Feb 13 13:28:09 vbun04 kernel: RDX: 0010 RSI: 000a 
RDI: 0003
  Feb 13 13:28:09 vbun04 kernel: RBP: 0003 R08:  
R09: 7f6c919331f0
  Feb 13 13:28:09 vbun04 kernel: R10:  R11: 0217 
R12: 55ec3a6bf150
  Feb 13 13:28:09 vbun04 kernel: R13: 7ffd8889a0b0 R14:  
R15: 
  Feb 13 13:28:09 vbun04 kernel: Modules linked in: vboxsf(OE) nls_utf8 isofs 
vboxvideo(OE) intel_rapl_msr intel_rapl_common crct10dif_pclmul vmwgfx 
crc32_pclmul ghash_clmulni_intel aesni_intel ttm drm_kms_helper a
  Feb 13 13:28:09 vbun04 kernel: CR2: 0020
  Feb 13 13:28:09 vbun04 kernel: ---[ end trace 278d665c8727286a ]---
  Feb 13 13:28:09 vbun04 kernel: RIP: 0010:do_coredump+0x536/0xb30
  Feb 13 13:28:09 vbun04 kernel: Code: 00 48 8b bd 18 ff ff ff 48 85 ff 74 05 
e8 c2 47 fa ff 65 48 8b 04 25 c0 6b 01 00 48 8b 00 48 8b 7d a0 a8 04 0f 85 65 
05 00 00 <48> 8b 57 20 0f b7 02 66 25 00 f0 66 3d 00 80 0f
  Feb 13 13:28:09 vbun04 kernel: RSP: :b464c2c5fca8 EFLAGS: 00010246
  Feb 13 13:28:09 vbun04 kernel: RAX:  RBX: 9d4b76995100 
RCX: 1afc
  Feb 13 13:28:09 vbun04 kernel: RDX:  RSI: b464c2c5fc68 
RDI: 
  Feb 13 13:28:

[Kernel-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

2020-02-13 Thread Hui Wang

@Paolo,

That is easy to fix.

change cset "name='Headset Mic Boost Volume' 1" to cset "name='Mic Boost
Volume' 2" in the all LENOVO_*/LENOVO_*.conf

sudo cp -rf /usr/share/alsa/ucm/LENOVO-MFG_IN_GO-ThinkPad-MFG_IN_GO/
/usr/share/alsa/ucm/LENOVO-20QD00LKIX-ThinkPadX1Carbon7th-20QD00LKIX/

sudo mv /usr/share/alsa/ucm/LENOVO-20QD00LKIX-ThinkPadX1Carbon7th-
20QD00LKIX/LENOVO-MFG_IN_GO-ThinkPad-MFG_IN_GO.conf /usr/share/alsa/ucm
/LENOVO-20QD00LKIX-ThinkPadX1Carbon7th-20QD00LKIX/LENOVO-20QD00LKIX-
ThinkPadX1Carbon7th-20QD00LKIX.conf

reboot

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

Title:
  add ucm to make alsa/sof driver work under PA (variants of Lenovo X1
  Carbon 7th, Dell cnl and cml machines)

Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Eoan:
  Fix Committed

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+subscriptions

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

[Kernel-packages] [Bug 1863099] [NEW] SOF firmwares missing

Public bug reported:

Files intel/sof/*.ri, intel/sof/*.ldc and intel/sof-tplg/*.tplg are
missing in the binary package.

** Affects: linux-firmware (Ubuntu)
 Importance: High
 Assignee: Anthony Wong (anthonywong)
 Status: Confirmed

** Affects: linux-firmware (Ubuntu Focal)
 Importance: High
 Assignee: Anthony Wong (anthonywong)
 Status: Confirmed

** Also affects: linux-firmware (Ubuntu Focal)
   Importance: High
   Status: Confirmed

** Changed in: linux-firmware (Ubuntu Focal)
 Assignee: (unassigned) => Anthony Wong (anthonywong)

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

Title:
  SOF firmwares missing

Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-firmware source package in Focal:
  Confirmed

Bug description:
  Files intel/sof/*.ri, intel/sof/*.ldc and intel/sof-tplg/*.tplg are
  missing in the binary package.

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

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

[Kernel-packages] [Bug 1863099] Re: SOF firmwares missing

** Patch added: "linux-firmware.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1863099/+attachment/5327963/+files/linux-firmware.patch

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

Title:
  SOF firmwares missing

Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-firmware source package in Focal:
  Confirmed

Bug description:
  Files intel/sof/*.ri, intel/sof/*.ldc and intel/sof-tplg/*.tplg are
  missing in the binary package.

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

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

[Kernel-packages] [Bug 1861554] Re: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54

You are right, please file an upstream bug at
https://gitlab.freedesktop.org/drm/amd/issues

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

Title:
  Radeon mobility HD3450 (RV620) heavy screen flickering after trying to
  upgrade kernel 4.15.0-54

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450.
  Distro: Linux Mint 19.2 Tina base: Ubuntu 18.04 bionic.
  This happen trying any distro. I tried Ubuntu, Manjaro, Debian, Deepin, MX 
and so on.
  I'm stuck with Kernel 4.15.0-54 and 5.0.0-20 (and the contemporary 5.3 
kernel). I cannot upgrade to newer kernels.
  Seems that the fixes for bug #1791312 broke my kind of card.

  here is a video:
  https://youtu.be/9Rez7s0V6iA

  here is another user with same problem:
  https://forums.linuxmint.com/viewtopic.php?p=1702005#p1702005

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

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

[Kernel-packages] [Bug 1862980] Re: i2c-HTIX5288:00: i2c_hid_get_input: incomplete report

I tested the kernel. There are still some error messages in dmesg, but
the buttons are working normally. Also the touchpad is now recognized as
a touchpad and as a mouse.

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862980/+attachment/5327964/+files/dmesg.txt

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

Title:
  i2c-HTIX5288:00: i2c_hid_get_input: incomplete report

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touchpad is spamming "i2c_hid_get_input: incomplete report" messages to 
dmesg and not working properly. Sometimes the left button acts like the right 
button. Sometimes it freezes completely. Also the keys to enable/disable 
touchpad (fn + f2) doesn't work.
  Also 'libinput list-devices' shows the following message: "event4  - 
HTIX5288:00 0911:5288 Touchpad: kernel bug: clickpad advertising right button"

  What's expected to happen?
   - The touchpad working properly.
  What's actually happening?
   - The touchpad not working properly.
  How to reproduce?
   - Start the computer and wait a few minutes.
  How to make the touchpad work normally for a few minutes (or seconds):
   - sudo rmmod i2c_hid && sudo modprobe i2c_hid

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-29-generic 5.3.0-29.31
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  username 1382 F pulseaudio
  Date: Wed Feb 12 13:11:15 2020
  InstallationDate: Installed on 2020-02-02 (10 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
   Bus 001 Device 004: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Positivo Tecnologia SA N1240
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=2656c128-b4f1-48e5-b1ef-79eea7a3280d ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: Desenvolvido por Positivo Tecnologia SA
  dmi.bios.version: V1.09.X
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: N14DP6
  dmi.board.vendor: Positivo Tecnologia SA
  dmi.board.version: 11139547
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Positivo Tecnologia SA
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnDesenvolvidoporPositivoTecnologiaSA:bvrV1.09.X:bd07/15/2019:svnPositivoTecnologiaSA:pnN1240:pvrTobefilledbyO.E.M.:rvnPositivoTecnologiaSA:rnN14DP6:rvr11139547:cvnPositivoTecnologiaSA:ct10:cvrTobefilledbyO.E.M.:
  dmi.product.family: MASTER
  dmi.product.name: N1240
  dmi.product.sku: 3052532
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Positivo Tecnologia SA

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

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

[Kernel-packages] [Bug 1862980] Re: i2c-HTIX5288:00: i2c_hid_get_input: incomplete report

** Attachment added: "xinput.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862980/+attachment/5327966/+files/xinput.txt

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

Title:
  i2c-HTIX5288:00: i2c_hid_get_input: incomplete report

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touchpad is spamming "i2c_hid_get_input: incomplete report" messages to 
dmesg and not working properly. Sometimes the left button acts like the right 
button. Sometimes it freezes completely. Also the keys to enable/disable 
touchpad (fn + f2) doesn't work.
  Also 'libinput list-devices' shows the following message: "event4  - 
HTIX5288:00 0911:5288 Touchpad: kernel bug: clickpad advertising right button"

  What's expected to happen?
   - The touchpad working properly.
  What's actually happening?
   - The touchpad not working properly.
  How to reproduce?
   - Start the computer and wait a few minutes.
  How to make the touchpad work normally for a few minutes (or seconds):
   - sudo rmmod i2c_hid && sudo modprobe i2c_hid

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-29-generic 5.3.0-29.31
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  username 1382 F pulseaudio
  Date: Wed Feb 12 13:11:15 2020
  InstallationDate: Installed on 2020-02-02 (10 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
   Bus 001 Device 004: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Positivo Tecnologia SA N1240
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=2656c128-b4f1-48e5-b1ef-79eea7a3280d ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: Desenvolvido por Positivo Tecnologia SA
  dmi.bios.version: V1.09.X
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: N14DP6
  dmi.board.vendor: Positivo Tecnologia SA
  dmi.board.version: 11139547
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Positivo Tecnologia SA
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnDesenvolvidoporPositivoTecnologiaSA:bvrV1.09.X:bd07/15/2019:svnPositivoTecnologiaSA:pnN1240:pvrTobefilledbyO.E.M.:rvnPositivoTecnologiaSA:rnN14DP6:rvr11139547:cvnPositivoTecnologiaSA:ct10:cvrTobefilledbyO.E.M.:
  dmi.product.family: MASTER
  dmi.product.name: N1240
  dmi.product.sku: 3052532
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Positivo Tecnologia SA

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

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

[Kernel-packages] [Bug 1863092] Re: Testing node with B-FIPS will complain "Unknown error executing apt-key"

Compared with the old test result, I didn't see this message with the same test 
case.
ubuntu_qrt_apparmor test on node onibi 
4.15.0-1022.25

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

Title:
  Testing node with B-FIPS will complain "Unknown error executing apt-
  key"

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  B-FIPS testing node will complain about "Unknown error executing apt-
  key" when running the apt update command.

  This issue does not exist in X-FIPS.
  Not sure what's the cause.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1863092/+subscriptions

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

[Kernel-packages] [Bug 1862980] Re: i2c-HTIX5288:00: i2c_hid_get_input: incomplete report

The problem with the left button happened again, this time it only took
a little longer to happen.

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

Title:
  i2c-HTIX5288:00: i2c_hid_get_input: incomplete report

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touchpad is spamming "i2c_hid_get_input: incomplete report" messages to 
dmesg and not working properly. Sometimes the left button acts like the right 
button. Sometimes it freezes completely. Also the keys to enable/disable 
touchpad (fn + f2) doesn't work.
  Also 'libinput list-devices' shows the following message: "event4  - 
HTIX5288:00 0911:5288 Touchpad: kernel bug: clickpad advertising right button"

  What's expected to happen?
   - The touchpad working properly.
  What's actually happening?
   - The touchpad not working properly.
  How to reproduce?
   - Start the computer and wait a few minutes.
  How to make the touchpad work normally for a few minutes (or seconds):
   - sudo rmmod i2c_hid && sudo modprobe i2c_hid

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-29-generic 5.3.0-29.31
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  username 1382 F pulseaudio
  Date: Wed Feb 12 13:11:15 2020
  InstallationDate: Installed on 2020-02-02 (10 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
   Bus 001 Device 004: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Positivo Tecnologia SA N1240
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=2656c128-b4f1-48e5-b1ef-79eea7a3280d ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: Desenvolvido por Positivo Tecnologia SA
  dmi.bios.version: V1.09.X
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: N14DP6
  dmi.board.vendor: Positivo Tecnologia SA
  dmi.board.version: 11139547
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Positivo Tecnologia SA
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnDesenvolvidoporPositivoTecnologiaSA:bvrV1.09.X:bd07/15/2019:svnPositivoTecnologiaSA:pnN1240:pvrTobefilledbyO.E.M.:rvnPositivoTecnologiaSA:rnN14DP6:rvr11139547:cvnPositivoTecnologiaSA:ct10:cvrTobefilledbyO.E.M.:
  dmi.product.family: MASTER
  dmi.product.name: N1240
  dmi.product.sku: 3052532
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Positivo Tecnologia SA

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

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

[Kernel-packages] [Bug 1861136] Re: bionic/linux-snapdragon: 4.15.0-1072.79 -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: 1862824
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Tuesday, 11. February 2020 13:26 UTC
  reason:
certification-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
+   security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1861135
  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/1861136

Title:
  bionic/linux-snapdragon: 4.15.0-1072.79 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon 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: 1862824
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Tuesday, 11. February 2020 13:26 UTC
  reason:
certification-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1861135
  variant: debs

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

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

[Kernel-packages] [Bug 1861249] Re: clashing with i915 video driver

Please refer to https://wiki.ubuntu.com/Kernel/MainlineBuilds

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

Title:
  clashing with i915 video driver

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed the new kernel 5.3 but found a black screen at startup.
  Had to remove it and go back to the 5.0 kernel.

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

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

[Kernel-packages] [Bug 1860697] Re: Sound doesn't work on Lenovo X1 Carbon 7th with 20.04

Copying Hui Wang's comment from https://lore.kernel.org/alsa-
devel/f8c8aa01-082a-8b00-cd6a-7d12af810...@canonical.com/:

After cherry-pick this commit (acbf27746ecfa96b290b54cc7f05273482ea128a 
ASoC: pcm: update FE/BE trigger order based on the command) to 5.4 
stable kernel, the sof driver works.

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

Title:
  Sound doesn't work on Lenovo X1 Carbon 7th with 20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently upgraded from 18.04+HWE kernel to 20.04 and now sound, both
  output and input, does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-9-generic 5.4.0-9.12
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 23 12:00:01 2020
  InstallationDate: Installed on 2019-09-06 (139 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 20QDCTO1WW
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-01-22 (1 days ago)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET43W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET43W(1.26):bd12/09/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1862980] Re: i2c-HTIX5288:00: i2c_hid_get_input: incomplete report

Only after suspend/resume cycle?

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

Title:
  i2c-HTIX5288:00: i2c_hid_get_input: incomplete report

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touchpad is spamming "i2c_hid_get_input: incomplete report" messages to 
dmesg and not working properly. Sometimes the left button acts like the right 
button. Sometimes it freezes completely. Also the keys to enable/disable 
touchpad (fn + f2) doesn't work.
  Also 'libinput list-devices' shows the following message: "event4  - 
HTIX5288:00 0911:5288 Touchpad: kernel bug: clickpad advertising right button"

  What's expected to happen?
   - The touchpad working properly.
  What's actually happening?
   - The touchpad not working properly.
  How to reproduce?
   - Start the computer and wait a few minutes.
  How to make the touchpad work normally for a few minutes (or seconds):
   - sudo rmmod i2c_hid && sudo modprobe i2c_hid

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-29-generic 5.3.0-29.31
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  username 1382 F pulseaudio
  Date: Wed Feb 12 13:11:15 2020
  InstallationDate: Installed on 2020-02-02 (10 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
   Bus 001 Device 004: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Positivo Tecnologia SA N1240
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=2656c128-b4f1-48e5-b1ef-79eea7a3280d ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: Desenvolvido por Positivo Tecnologia SA
  dmi.bios.version: V1.09.X
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: N14DP6
  dmi.board.vendor: Positivo Tecnologia SA
  dmi.board.version: 11139547
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Positivo Tecnologia SA
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnDesenvolvidoporPositivoTecnologiaSA:bvrV1.09.X:bd07/15/2019:svnPositivoTecnologiaSA:pnN1240:pvrTobefilledbyO.E.M.:rvnPositivoTecnologiaSA:rnN14DP6:rvr11139547:cvnPositivoTecnologiaSA:ct10:cvrTobefilledbyO.E.M.:
  dmi.product.family: MASTER
  dmi.product.name: N1240
  dmi.product.sku: 3052532
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Positivo Tecnologia SA

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

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

[Kernel-packages] [Bug 1862980] Re: i2c-HTIX5288:00: i2c_hid_get_input: incomplete report

No.

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

Title:
  i2c-HTIX5288:00: i2c_hid_get_input: incomplete report

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touchpad is spamming "i2c_hid_get_input: incomplete report" messages to 
dmesg and not working properly. Sometimes the left button acts like the right 
button. Sometimes it freezes completely. Also the keys to enable/disable 
touchpad (fn + f2) doesn't work.
  Also 'libinput list-devices' shows the following message: "event4  - 
HTIX5288:00 0911:5288 Touchpad: kernel bug: clickpad advertising right button"

  What's expected to happen?
   - The touchpad working properly.
  What's actually happening?
   - The touchpad not working properly.
  How to reproduce?
   - Start the computer and wait a few minutes.
  How to make the touchpad work normally for a few minutes (or seconds):
   - sudo rmmod i2c_hid && sudo modprobe i2c_hid

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-29-generic 5.3.0-29.31
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  username 1382 F pulseaudio
  Date: Wed Feb 12 13:11:15 2020
  InstallationDate: Installed on 2020-02-02 (10 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
   Bus 001 Device 004: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Positivo Tecnologia SA N1240
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=2656c128-b4f1-48e5-b1ef-79eea7a3280d ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: Desenvolvido por Positivo Tecnologia SA
  dmi.bios.version: V1.09.X
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: N14DP6
  dmi.board.vendor: Positivo Tecnologia SA
  dmi.board.version: 11139547
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Positivo Tecnologia SA
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnDesenvolvidoporPositivoTecnologiaSA:bvrV1.09.X:bd07/15/2019:svnPositivoTecnologiaSA:pnN1240:pvrTobefilledbyO.E.M.:rvnPositivoTecnologiaSA:rnN14DP6:rvr11139547:cvnPositivoTecnologiaSA:ct10:cvrTobefilledbyO.E.M.:
  dmi.product.family: MASTER
  dmi.product.name: N1240
  dmi.product.sku: 3052532
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Positivo Tecnologia SA

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

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

[Kernel-packages] [Bug 1860401] Re: [sfc-0121]enable the HiSilicon v3xx SFC driver

2020-02-13 Thread Ike Panhc

Test build failed after 3 patches cherry-pick from mainline.

/home/ubuntu/ubuntu-focal/drivers/mtd/spi-nor/spi-nor.c: In function 
‘st_micron_set_default_init’:
/home/ubuntu/ubuntu-focal/drivers/mtd/spi-nor/spi-nor.c:4393:17: error: 
‘SNOR_F_HAS_16BIT_SR’ undeclared (first use in this function); did you mean 
‘SNOR_F_HAS_4BAIT’?
  nor->flags &= ~SNOR_F_HAS_16BIT_SR;
 ^~~
 SNOR_F_HAS_4BAIT
/home/ubuntu/ubuntu-focal/drivers/mtd/spi-nor/spi-nor.c:4393:17: note: each 
undeclared identifier is reported only once for each function it appears in

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

Title:
  [sfc-0121]enable the HiSilicon v3xx SFC driver

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  In Progress
Status in kunpeng920 upstream-kernel series:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Bug Description]
  enable the HiSilicon v3xx SFC driver 

  [Steps to Reproduce]
  1)
  2)
  3)

  [Actual Results]

  [Expected Results]

  [Reproducibility]

  [Additional information]
  (Firmware version, kernel version, affected hardware, etc. if required):

  [Resolution]

  MAINTAINERS: Add a maintainer for the HiSilicon v3xx SFC driver
  spi: Add HiSilicon v3xx SPI NOR flash controller driver
  mtd: spi-nor: Fix the writing of the Status Register on micron flashes

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

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

[Kernel-packages] [Bug 1862253] Re: focal/linux-kvm-5.4: 5.4.0-1001.1 -proposed tracker

2020-02-13 Thread Paolo Pisati

** Summary changed:

- focal/linux-kvm-5.4:  -proposed tracker
+ focal/linux-kvm-5.4: 5.4.0-1001.1 -proposed tracker

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

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

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

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

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

Title:
  focal/linux-kvm-5.4: 5.4.0-1001.1 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1862255
  packages:
main: linux-kvm-5.4
meta: linux-meta-kvm-5.4
  phase: Ready for Promote to Proposed
  phase-changed: Thursday, 13. February 2020 14:16 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  variant: debs

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

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

2020-02-13 Thread Guilherme G. Piccoli

Thank you Khaled! I've just checked the source from bionic-proposed
(4.15.0-88) and the patch is there, as expected - I've verified that
comparing with the upstream patch, it's all correct.

Given we don't have the HW and the bug reporter seems to be unable to
verify it (and the patch is self-contained/straightforward), we can
consider it ready to go!

Cheers,


Guilherme

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 Released
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 1861554] Re: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54

2020-02-13 Thread dueller

Done
Issue is here:
https://gitlab.freedesktop.org/drm/amd/issues/1045

** Bug watch added: gitlab.freedesktop.org/drm/amd/issues #1045
   https://gitlab.freedesktop.org/drm/amd/issues/1045

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

Title:
  Radeon mobility HD3450 (RV620) heavy screen flickering after trying to
  upgrade kernel 4.15.0-54

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450.
  Distro: Linux Mint 19.2 Tina base: Ubuntu 18.04 bionic.
  This happen trying any distro. I tried Ubuntu, Manjaro, Debian, Deepin, MX 
and so on.
  I'm stuck with Kernel 4.15.0-54 and 5.0.0-20 (and the contemporary 5.3 
kernel). I cannot upgrade to newer kernels.
  Seems that the fixes for bug #1791312 broke my kind of card.

  here is a video:
  https://youtu.be/9Rez7s0V6iA

  here is another user with same problem:
  https://forums.linuxmint.com/viewtopic.php?p=1702005#p1702005

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

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

[Kernel-packages] [Bug 1853665] Re: Bluetooth not working with Realtek RTL8821CE

2020-02-13 Thread ofek luis lewinsohn

Same problem on Asus UX410UA reverting to kernel 5.3.0-26 seems to solve
it though so I assume the problem lies on the new kernel.

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

Title:
  Bluetooth not working with Realtek RTL8821CE

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in rtl8821ce package in Ubuntu:
  Confirmed

Bug description:
  The driver installed just fine and wifi is working but bluetooth does
  not.

  I will gladly provide further debugging information.

  Ubuntu 19.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steven 2090 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-17 (75 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0408:5321 Quanta Computer, Inc. HP Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP 250 G7 Notebook PC
  Package: rtl8821ce
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=a0cdf605-0b72-4674-a76e-ad1dbae26043 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/05/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8532
  dmi.board.vendor: HP
  dmi.board.version: 70.22
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd12/05/2018:svnHP:pnHP250G7NotebookPC:pvrType1ProductConfigId:rvnHP:rn8532:rvr70.22:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN HP 200
  dmi.product.name: HP 250 G7 Notebook PC
  dmi.product.sku: 6MQ54EA#ABD
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1862253] Re: focal/linux-kvm-5.4: 5.4.0-1001.1 -proposed tracker