[Kernel-packages] [Bug 1870447] Re: Possible Missing Firmware vega20_ta.bin and navi10_mes.bin for amdgpu RX480

[Michael Haworth]

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

** This bug has been marked a duplicate of bug 1850654
   update-initramfs complains of missing amdgpu firmware files

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

Title:
  Possible Missing Firmware vega20_ta.bin and navi10_mes.bin for amdgpu
  RX480

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  When running apt update && apt dist-upgrade I am receiving the
  following possible missing firmware message:

  Processing triggers for linux-image-5.3.0-45-generic (5.3.0-45.37) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.3.0-45-generic
  W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module 
amdgpu
  I: The initramfs will attempt to resume from /dev/sda1
  I: (UUID=f77cf124-fcd0-4de3-a528-466aff1270ba)
  I: Set the RESUME variable to override this.
  /etc/kernel/postinst.d/zz-update-grub:
  Sourcing file `/etc/default/grub'
  Sourcing file `/etc/default/grub.d/init-select.cfg'
  Generating grub configuration file ...
  Found linux image: /boot/vmlinuz-5.3.0-45-generic
  Found initrd image: /boot/initrd.img-5.3.0-45-generic
  Found linux image: /boot/vmlinuz-5.3.0-42-generic
  Found initrd image: /boot/initrd.img-5.3.0-42-generic
  Found linux image: /boot/vmlinuz-5.3.0-40-generic
  Found initrd image: /boot/initrd.img-5.3.0-40-generic
  Found memtest86+ image: /boot/memtest86+.elf
  Found memtest86+ image: /boot/memtest86+.bin
  Found Windows 10 on /dev/nvme0n1p1
  done

  My desktop system has a AMD Radeon RX 480 graphics card.

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

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

[Kernel-packages] [Bug 1864005] Re: Fix AMD Stoney Ridge screen flickering under 4K resolution

[Khaled El Mously]

This is fixed in Disco as well via linux-stable

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

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

Title:
  Fix AMD Stoney Ridge screen flickering under 4K resolution

Status in HWE Next:
  New
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 Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Screen flickering/tearing when AMD Stoney Ridge outputs to 4K display.

  [Fix]
  Disable IOMMU on Stoney Ridge.

  [Test]
  Connect to 4K screen through DP or HDMI. Heavy flickering/tearing can be
  observed.
  The flickering/tearing is gone once the patch is applied.

  [Regression Potential]
  Low. This fix limits to one specific SoC.
  According to AMD, IOMMU isn't enabled for this SoC under Windows.
  So it's expected behavior.

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

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

[Kernel-packages] [Bug 1852383] Re: system hangs on shutdown

[Launchpad Bug Tracker]

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

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

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

Title:
  system hangs on shutdown

Status in linux package in Ubuntu:
  Expired

Bug description:
  On a Lenovo Yoga S940, the system always hangs on shutdown.
  The screen turns black and nothing happens anymore. 
  I have to keep pressed for several seconds the shutdown hardware button in 
order to actually turn it off.

  I attach the journalctl output from the shutdown which present very
  similar 'errors' from session to session.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7
  Uname: Linux 5.3.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 13 07:03:38 2019
  InstallationDate: Installed on 2019-10-09 (34 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190916)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1861700] Re: kernel 4.15.0-72 wifi and lan network not found

[Launchpad Bug Tracker]

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

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

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

Title:
  kernel 4.15.0-72 wifi and lan network not found

Status in linux package in Ubuntu:
  Expired

Bug description:
  i have dell inspiron 3467
  OS : Ubuntu 18.04.3
  when updated initially touchpad stopped working and then wifi and network 
stopped working
  right now touch pad is working. 
  I have edited the grub file and default kernel is made to 4.15.0.66
  In this kernel 4.15.0.66 everything works perfectly alright. 

  version : Ubuntu 4.15.0-66.75-generic 4.15.18

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

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

[Kernel-packages] [Bug 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]

[Phuc Minh Cai]

Hi Hai Heng Feng,

How are you? Hope you're fine.

I saw it's already release kernel v5.6

Should I try with this kernel?

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

Title:
  ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to
  submit batchbuffer: Input/output error]

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't 
recognize graphic driver.
  - run udo apt-get install xserver-xorg-video-intel
  0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 14:29:01 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd]
  InstallationDate: Installed on 2020-01-24 (0 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 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub
   Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. T100HAN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T100HAN.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: T100HAN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: T
  dmi.product.name: T100HAN
  dmi.product.sku: ASUS-TabletSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1870265] Re: Intel GPU causes BUG: kernel NULL pointer dereference, address: 0000000000000040

[Leonardo Müller]

I just tested the Xubuntu Beta ISO and, from it, I was able to reproduce
the system crash.

Unfortunately I was unable to obtain any logs, as sshd was no longer
responsive and it was a live system.

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

Title:
  Intel GPU causes BUG: kernel NULL pointer dereference, address:
  0040

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After playing Gurumin: A Monstrous Adventure for some time, the system
  crashed in an unrecoverable way. REISUB was required to get some logs.

  This crash happened with default Ubuntu's kernel, default Mesa and
  default Xorg session. I never observed a crash this serious using the
  intel Xorg driver. However, using the default (modesetting), the
  following unrecoverable crash happened after two hours:

  The syslog contains the following:

  Apr  2 00:39:02 Lenovo-ideapad-310-14ISK systemd[1]: Starting Clean php 
session files...
  Apr  2 00:39:03 Lenovo-ideapad-310-14ISK systemd[1]: phpsessionclean.service: 
Succeeded.
  Apr  2 00:39:03 Lenovo-ideapad-310-14ISK systemd[1]: Finished Clean php 
session files.
  Apr  2 00:56:59 Lenovo-ideapad-310-14ISK wpa_supplicant[1083]: wlp2s0: WPA: 
Group rekeying completed with 18:d6:c7:ee:b0:90 [GTK=CCMP]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284307] BUG: kernel 
NULL pointer dereference, address: 0040
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284314] #PF: 
supervisor read access in kernel mode
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284316] #PF: 
error_code(0x) - not-present page
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284321] PGD 0 P4D 0 
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284325] Oops:  
[#1] SMP PTI
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284330] CPU: 1 PID: 
200385 Comm: xfwm4 Tainted: P   O  5.4.0-21-generic #25-Ubuntu
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284331] Hardware 
name: LENOVO 80UG/Toronto 4A2, BIOS 0XCN45WW 08/09/2018
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284399] RIP: 
0010:i915_active_acquire+0xe/0x80 [i915]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284403] Code: 00 48 
c7 c6 a5 4e 6f c0 e8 af 07 93 e5 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 
0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 
01 f0 0f b1 53 38 75 f2 45 31
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284405] RSP: 
0018:bd8446f979c8 EFLAGS: 00010286
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284408] RAX: 
 RBX: 9c477afaca80 RCX: 
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284409] RDX: 
9c4633bfc500 RSI: 9c477afaca80 RDI: 0008
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284411] RBP: 
bd8446f979e0 R08: 9c47d6f4dc28 R09: 9c47d6f4dc20
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284413] R10: 
00014000 R11: 9c47d1918b00 R12: 9c4633bfc500
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284414] R13: 
0008 R14: 9c4633bfc500 R15: 9c47d6f4db00
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284417] FS:  
7f99a3564a80() GS:9c47de28() knlGS:
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284419] CS:  0010 DS: 
 ES:  CR0: 80050033
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284420] CR2: 
0040 CR3: 000556ca0001 CR4: 003606e0
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284421] DR0: 
 DR1:  DR2: 
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284422] DR3: 
 DR6: fffe0ff0 DR7: 0400
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284423] Call Trace:
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284477]  
i915_active_ref+0x24/0x200 [i915]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284521]  
i915_vma_move_to_active+0x74/0xf0 [i915]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284564]  
eb_submit+0xff/0x440 [i915]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284608]  
i915_gem_do_execbuffer+0x88e/0xc20 [i915]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284615]  ? 
sock_def_readable+0x40/0x70
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284618]  ? 
__kmalloc_node+0x205/0x320
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284668]  
i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284717]  ? 
i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
  Apr  2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284742]  

[Kernel-packages] [Bug 1831940] Re: hibernation support for linux-aws

[Launchpad Bug Tracker]

This bug was fixed in the package linux-aws - 5.4.0-1007.7

---
linux-aws (5.4.0-1007.7) focal; urgency=medium

  [ Ubuntu: 5.4.0-21.25 ]

  * CVE-2020-8835
- SAUCE: bpf: undo incorrect __reg_bound_offset32 handling

 -- Thadeu Lima de Souza Cascardo   Fri, 27 Mar
2020 17:06:08 -0300

** Changed in: linux-aws (Ubuntu Focal)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8835

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

Title:
  hibernation support for linux-aws

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

Bug description:
  Additional AWS-specific and mainline patches are required to support
  hibernation across the various types of AWS instances.

  The following patch sets for linux-aws-xenial and linux-aws-bionic
  provide the necessary functionality, and should only impact the
  hibernation and resume paths.

  [linux-aws-xenial]

  UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore
  UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake
  UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation.
  UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in 
xen_restore_pirqs.
  radix-tree: delete radix_tree_locate_item()
  mm: rid swapoff of quadratic complexity
  sched/wait: Fix abort_exclusive_wait(), it should pass TASK_NORMAL to 
wake_up()
  sched/wait: Avoid abort_exclusive_wait() in ___wait_event()
  sched/wait: Avoid abort_exclusive_wait() in __wait_on_bit_lock()
  sched/wait: Introduce init_wait_entry()
  sched/wait: Standardize wait_bit_queue naming
  sched/wait: Introduce wait_var_event()
  mm: swapoff: shmem_unuse() stop eviction without igrab()
  UBUNTU SAUCE [aws]: mm: aggressive swapoff
  UBUNTU SAUCE [aws]: PM / hibernate: make sure pm_async is always disabled
  NVMe: Allow request merges
  PM / hibernate: Do not free preallocated safe pages during image restore
  PM / hibernate: Recycle safe pages after image restoration
  PM / hibernate: Simplify mark_unsafe_pages()
  UBUNTU: [Config] aws: disable CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS
  UBUNTU SAUCE [aws] PM / hibernate: set image_size to total RAM size by default
  UBUNTU SAUCE [aws] PM / hibernate: reduce memory pressure during image writing
  UBUNTU SAUCE [aws] mm, page_alloc: disable fair zone allocation policy on 
hibernate

  [linux-aws-bionic]

  UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore
  UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake
  UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation.
  UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in 
xen_restore_pirqs.
  mm: rid swapoff of quadratic complexity
  sched/wait: Introduce wait_var_event()
  mm: swapoff: shmem_unuse() stop eviction without igrab()
  UBUNTU SAUCE [aws]: mm: aggressive swapoff
  netlink: Don't shift on 64 for ngroups

  [linux-aws-edge-bionic]

  UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in 
xen_restore_pirqs.
  UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation.
  UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore
  UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake
  UBUNTU SAUCE [aws]: PM / hibernate: set image_size to 0 by default
  UBUNTU SAUCE [aws]: PM / hibernate: make sure pm_async is always disabled
  UBUNTU SAUCE [aws]: mm: swap: improve swap readahead heuristic
  UBUNTU SAUCE [aws] PM / hibernate: reduce memory pressure during image writing
  PM / hibernate: memory_bm_find_bit(): Tighten node optimisation
  mm: rid swapoff of quadratic complexity
  mm: refactor swap-in logic out of shmem_getpage_gfp

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

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

[Kernel-packages] [Bug 1858618] Re: linux-aws: swapoff optimization

[Launchpad Bug Tracker]

This bug was fixed in the package linux-aws - 5.4.0-1007.7

---
linux-aws (5.4.0-1007.7) focal; urgency=medium

  [ Ubuntu: 5.4.0-21.25 ]

  * CVE-2020-8835
- SAUCE: bpf: undo incorrect __reg_bound_offset32 handling

 -- Thadeu Lima de Souza Cascardo   Fri, 27 Mar
2020 17:06:08 -0300

** Changed in: linux-aws (Ubuntu Focal)
   Status: New => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8835

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

Title:
  linux-aws: swapoff optimization

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws-5.0 package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  Fix Released
Status in linux-aws-5.0 source package in Bionic:
  Fix Released
Status in linux-aws source package in Disco:
  Fix Committed
Status in linux-aws-5.0 source package in Disco:
  Invalid
Status in linux-aws source package in Eoan:
  Fix Committed
Status in linux-aws-5.0 source package in Eoan:
  New
Status in linux-aws source package in Focal:
  Fix Released
Status in linux-aws-5.0 source package in Focal:
  Invalid

Bug description:
  [Impact]

  When an instance in the AWS EC2 infrastructure is successfully
  hibernated and resumed we want to deactivate the swap file as fast as
  possible in order to make the instance available again for the user.
  By default the kernel doesn't really optimize swapoff performance, it
  tries to keep the whole system still usable and responsive while
  swapoff is running.

  However, in our specific use case, swapoff needs to complete as fast
  as possible, so we may want to give swapoff I/O a higher priority and
  use different heuristics in order to optimize the I/O and page
  readahead generated by swapoff.

  [Test Case]

  Run the hibernation test on the AWS EC2 instances.

  [Fix]

  Apply a more aggressive swapin readahead policy that allows to improve
  swapoff performance.

  [Regression Potential]

  Minimal, this change is only affecting the swapoff-related code and it
  has been tested extensively with positive test results. The only
  downside is that this different heuristic makes the system more
  unresponsive during swapoff, but this is not a problem in the AWS
  scenario, because (by explicit requirement) the user shouldn't be able
  to use the instance during this swapoff phase.

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

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

[Kernel-packages] [Bug 1863951] Re: [linux-azure] Missing user mode io driver - uio_pci_generic

[Launchpad Bug Tracker]

This bug was fixed in the package linux-azure - 5.4.0-1008.8

---
linux-azure (5.4.0-1008.8) focal; urgency=medium

  [ Ubuntu: 5.4.0-21.25 ]

  * CVE-2020-8835
- SAUCE: bpf: undo incorrect __reg_bound_offset32 handling

 -- Thadeu Lima de Souza Cascardo   Fri, 27 Mar
2020 17:57:04 -0300

** Changed in: linux-azure (Ubuntu Focal)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8835

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

Title:
  [linux-azure] Missing user mode io driver - uio_pci_generic

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux-azure source package in Bionic:
  Fix Committed
Status in linux-azure source package in Eoan:
  Fix Committed
Status in linux-azure source package in Focal:
  Fix Released

Bug description:
  After creating a Lv2 VM (OS - ubuntu 18.04) it was found that
  uio_pci_generic is missing.  It is needed to attach SPDK to nvme disk.

  The kernel build config file that Canonical provides in Ubuntu 18.04
  images shows CONFIG_UIO_PCI_GENERIC=m, indicating that the module was
  built.  However, the module is not included in the image.

  Is there a reason why the uio_pci_generic module is not included in
  the Azure Marketplace image?  If not, can we get it added back in?

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

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

[Kernel-packages] [Bug 1867002] Re: Add XHCI/USB support to linux-azure

[Launchpad Bug Tracker]

This bug was fixed in the package linux-azure - 5.4.0-1008.8

---
linux-azure (5.4.0-1008.8) focal; urgency=medium

  [ Ubuntu: 5.4.0-21.25 ]

  * CVE-2020-8835
- SAUCE: bpf: undo incorrect __reg_bound_offset32 handling

 -- Thadeu Lima de Souza Cascardo   Fri, 27 Mar
2020 17:57:04 -0300

** Changed in: linux-azure (Ubuntu Focal)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8835

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

Title:
  Add XHCI/USB support to linux-azure

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

Bug description:
  Enable xHCI for PCI passthrough for USB support.

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

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

[Kernel-packages] [Bug 1867820] Re: linux-azure: Update SGX version and udev rules

[Launchpad Bug Tracker]

This bug was fixed in the package linux-azure - 5.4.0-1008.8

---
linux-azure (5.4.0-1008.8) focal; urgency=medium

  [ Ubuntu: 5.4.0-21.25 ]

  * CVE-2020-8835
- SAUCE: bpf: undo incorrect __reg_bound_offset32 handling

 -- Thadeu Lima de Souza Cascardo   Fri, 27 Mar
2020 17:57:04 -0300

** Changed in: linux-azure (Ubuntu Focal)
   Status: New => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8835

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

Title:
  linux-azure: Update SGX version and udev rules

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-base package in Ubuntu:
  Fix Released
Status in linux-azure source package in Trusty:
  Invalid
Status in linux-base source package in Trusty:
  Invalid
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-base source package in Xenial:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-base source package in Bionic:
  Fix Released
Status in linux-azure source package in Eoan:
  Fix Released
Status in linux-base source package in Eoan:
  Fix Released
Status in linux-azure source package in Focal:
  Fix Released
Status in linux-base source package in Focal:
  Fix Released

Bug description:
  [Impact]

  We will use the official Intel's DCAP git repository to keep SGX up-
  to-date. We need to update the driver included to the linux-azure
  kernels to the version located at:

  
https://github.com/intel/SGXDataCenterAttestationPrimitives/tree/LD_1.22/driver/linux

  Including the provided udev rules.

  [Test Case]

  The driver should continue to work normally. The main difference
  should be the permissions and groups for the /dev/sgx (0666) and
  /dev/sgx_prv (0660 with sgx_prc group).

  
  [Regression Potential] 

  The regression potential is low since the functional changes are not
  meaningful and the permissions are less restrictive.

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

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

[Kernel-packages] [Bug 1866734] Re: All PS/2 ports on PS/2 Serial add-in bracket are not working after S3

[Khaled El Mously]

Applied to Eoan.

@You-Sheng: Note that this was NOT applied to Bionic. It's not clear if
it should be applied to Bionic or not (see the responses on the email
thread)

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

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

Title:
  All PS/2 ports on PS/2 Serial add-in bracket are not working after S3

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

Bug description:
  [Impact]
  PS/2 ports on PS/2 Serial add-in card do not work after S3.

  [Fix]
  The i8042 controller selftest fails while resuming, adding retry fix this 
issue.

  [Test]
  Verified on the target machine, the ps/2 keyboard keeps working after S3 test 
30 times.

  [Regression Potential]
  Low, there is a retry logic in controller selftest, but it returns directly 
if it fails to communicate with the controller. This commit make it retry 5 
times before return fails.

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

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

[Kernel-packages] [Bug 1870604] Re: Bionic update: upstream stable patchset 2020-04-03

[Khaled El Mously]

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

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

Title:
  Bionic update: upstream stable patchset 2020-04-03

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2020-04-03

  Ported from the following upstream stable releases:
  v4.14.175, v4.19.113,
 v4.19.114

     from git://git.kernel.org/

  spi: qup: call spi_qup_pm_resume_runtime before suspending
  powerpc: Include .BTF section
  ARM: dts: dra7: Add "dma-ranges" property to PCIe RC DT nodes
  spi: pxa2xx: Add CS control clock quirk
  spi/zynqmp: remove entry that causes a cs glitch
  drm/exynos: dsi: propagate error value and silence meaningless warning
  drm/exynos: dsi: fix workaround for the legacy clock name
  drivers/perf: arm_pmu_acpi: Fix incorrect checking of gicc pointer
  altera-stapl: altera_get_note: prevent write beyond end of 'key'
  dm bio record: save/restore bi_end_io and bi_integrity
  xenbus: req->body should be updated before req->state
  xenbus: req->err should be updated before req->state
  block, bfq: fix overwrite of bfq_group pointer in bfq_find_set_group()
  parse-maintainers: Mark as executable
  USB: Disable LPM on WD19's Realtek Hub
  usb: quirks: add NO_LPM quirk for RTL8153 based ethernet adapters
  USB: serial: option: add ME910G1 ECM composition 0x110b
  usb: host: xhci-plat: add a shutdown
  USB: serial: pl2303: add device-id for HP LD381
  usb: xhci: apply XHCI_SUSPEND_DELAY to AMD XHCI controller 1022:145c
  ALSA: line6: Fix endless MIDI read loop
  ALSA: seq: virmidi: Fix running status after receiving sysex
  ALSA: seq: oss: Fix running status after receiving sysex
  ALSA: pcm: oss: Avoid plugin buffer overflow
  ALSA: pcm: oss: Remove WARNING from snd_pcm_plug_alloc() checks
  iio: trigger: stm32-timer: disable master mode when stopping
  iio: magnetometer: ak8974: Fix negative raw values in sysfs
  mmc: sdhci-of-at91: fix cd-gpios for SAMA5D2
  staging: rtl8188eu: Add device id for MERCUSYS MW150US v2
  staging/speakup: fix get_word non-space look-ahead
  intel_th: Fix user-visible error codes
  intel_th: pci: Add Elkhart Lake CPU support
  rtc: max8907: add missing select REGMAP_IRQ
  xhci: Do not open code __print_symbolic() in xhci trace events
  memcg: fix NULL pointer dereference in __mem_cgroup_usage_unregister_event
  mm: slub: be more careful about the double cmpxchg of freelist
  mm, slub: prevent kmalloc_node crashes and memory leaks
  page-flags: fix a crash at SetPageError(THP_SWAP)
  x86/mm: split vmalloc_sync_all()
  USB: cdc-acm: fix close_delay and closing_wait units in TIOCSSERIAL
  USB: cdc-acm: fix rounding error in TIOCSSERIAL
  iio: adc: at91-sama5d2_adc: fix channel configuration for differential 
channels
  iio: adc: at91-sama5d2_adc: fix differential channels in triggered mode
  kbuild: Disable -Wpointer-to-enum-cast
  futex: Fix inode life-time issue
  futex: Unbreak futex hashing
  Revert "vrf: mark skb for multicast or link-local as enslaved to VRF"
  Revert "ipv6: Fix handling of LLA with VRF and sockets bound to VRF"
  ALSA: hda/realtek: Fix pop noise on ALC225
  arm64: smp: fix smp_send_stop() behaviour
  arm64: smp: fix crash_smp_send_stop() behaviour
  drm/bridge: dw-hdmi: fix AVI frame colorimetry
  staging: greybus: loopback_test: fix potential path truncation
  staging: greybus: loopback_test: fix potential path truncations
  Revert "drm/dp_mst: Skip validating ports during destruction, just ref"
  hsr: fix general protection fault in hsr_addr_is_self()
  macsec: restrict to ethernet devices
  net: dsa: Fix duplicate frames flooded by learning
  net: mvneta: Fix the case where the last poll did not process all rx
  net/packet: tpacket_rcv: avoid a producer race condition
  net: qmi_wwan: add support for ASKEY WWHC050
  net_sched: cls_route: remove the right filter from hashtable
  net_sched: keep alloc_hash updated after hash allocation
  net: stmmac: dwmac-rk: fix error path in rk_gmac_probe
  NFC: fdp: Fix a signedness bug in fdp_nci_send_patch()
  slcan: not call free_netdev before rtnl_unlock in slcan_open
  bnxt_en: fix memory leaks in bnxt_dcbnl_ieee_getets()
  net: dsa: mt7530: Change the LINK bit to reflect the link status
  vxlan: 

[Kernel-packages] [Bug 1855668] Re: lockdown on power

[Seth Forshee]

New test build with the updated patch in the same ppa.

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

Title:
  lockdown on power

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  == Comment: #0 - Michael Ranweiler  - 2019-11-11 
08:50:51 ==
  For 20.04 testing/inclusion.  The ubuntu kernel team has a ppa here for 
testing:
  https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable

  Test results will follow...

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

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

[Kernel-packages] [Bug 1866909] Re: Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

[Seth Forshee]

Test build is done now, in the same location. It has the above patch and
also the updated patch from bug 1855668.

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

Title:
  Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - George C. Wilson  - 2020-02-25 18:40:44 
==
  - sysfs enablement: TBD
  - ima: arch specific policy support 6191706246de
  - platform keyring changes for powerpc: TBD
  - Appended signatures support for IMA appraisal 
39b07096364a42c516415d5f841069e885234e61
  - integrity: Define a trusted platform keyring: 9dc92c45177a
  - ima: Support platform keyring for kernel appraisal: d7cecb676dd3
  - TPM 2.0 Multibank extend support: c1f92b4b04ad
  - TPM 2.0 Eventlog support: 4d23cc323cdb
  - ima: carry the measurement list across kexec: d68a6fe9fccf
  - kexec_file_load system call support: 500c7ab1a9db

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

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

[Kernel-packages] [Bug 1869694] Re: Support SMO8840 as LIS2DH12

[Kelsey Margarete Skunberg]

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

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

Title:
  Support SMO8840 as LIS2DH12

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  In Progress

Bug description:
  === Impact ===
  According to ST, HID SMO8840 is for LIS2DH12. In Ubuntu kernel, support for 
this ID is missing in Bionic, and it's mapped to LNG2DM in D/E/F.

  === Fix ===
  * e43d110cdc20 - iio: st_sensors: remap SMO8840 to LIS2DH12
  This is in mainline kernel 5.6, and also 4.19, 5.4, and 5.5 stable trees.

  === Risk of Regression ===
  Low.
  Hans de Goede@redhat, who originally mapped SMO8840 to LNG2DM, confirmed the 
patch works for his Lenovo Ideapad Miix 320: 
  
https://lore.kernel.org/linux-iio/20200224095426.25681-1-jesse.s...@canonical.com/T/#u

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

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

[Kernel-packages] [Bug 1869694] Re: Support SMO8840 as LIS2DH12

[Kelsey Margarete Skunberg]

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

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

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

Title:
  Support SMO8840 as LIS2DH12

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  In Progress
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  In Progress

Bug description:
  === Impact ===
  According to ST, HID SMO8840 is for LIS2DH12. In Ubuntu kernel, support for 
this ID is missing in Bionic, and it's mapped to LNG2DM in D/E/F.

  === Fix ===
  * e43d110cdc20 - iio: st_sensors: remap SMO8840 to LIS2DH12
  This is in mainline kernel 5.6, and also 4.19, 5.4, and 5.5 stable trees.

  === Risk of Regression ===
  Low.
  Hans de Goede@redhat, who originally mapped SMO8840 to LNG2DM, confirmed the 
patch works for his Lenovo Ideapad Miix 320: 
  
https://lore.kernel.org/linux-iio/20200224095426.25681-1-jesse.s...@canonical.com/T/#u

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

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

[Kernel-packages] [Bug 1869642] Re: No audio output from Dell WD19 HDMI/DP after resumed from S3 or s2idle

[Kelsey Margarete Skunberg]

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

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

Title:
  No audio output from Dell WD19 HDMI/DP after resumed from S3 or s2idle

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  In Progress

Bug description:
  [Impact]
  Plug-in HDMI/DP cable onto docking station after system resumed from 
S3/s2idle, there is no audio output from HDMI/DP even if you select the HDMI/DP 
audio output manually from sound settings.
  It shows this in dmesg when try testing speakers from sound settings
  [ 2052.030247] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 
0x2f0d00. -5

  [Fix]
  This issue has been fixed in 4.16-rc1 by below commit
  4918e1f87c5f PM / runtime: Rework pm_runtime_force_suspend/resume()

  [Test]
  Verified on Dell Latitude 3310 + Dell WD19 docking station

  [Regression Potential]
  Low, it fixes the device usage counter, and should also fix some other runpm 
issues.

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

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

[Kernel-packages] [Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller

[Aki Nyrhinen]

Beyond all of that, does anyone happen to know of a USB3 card that does work 
(on Linux)?

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

Title:
  xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1
  Controller

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress
Status in linux package in Debian:
  Confirmed

Bug description:
  It was observed that while trying to use a 4K USB webcam connected to
  USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam
  does not work and kernel log shows the following messages:

  [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13

  A similar issue was already reported on Launchpad:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750

  The fix to this issue seems to be the following patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109

  Tests in our scenario with this patch proved still broken. Our next
  approach is to modify the patch a bit and re-test.

  This LP will be used to document our progress in the investigation.

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

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

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

[Kelsey Margarete Skunberg]

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

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

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

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

Bug description:
  === SRU Justification ===
  [Impact]
  Some systems have a "phantom" Nvidia UCSI, which prevent systems from
  suspending. 

  [Fix]
  ucsi_ccg is stuck in its probe routine because of the i2c bus never
  timeouts. Let it timeouts and probe can fail since it's just a phantom
  device.

  [Test]
  After applying this patch system can suspend/resume succesfully.

  [Regression Potential]
  Low. It's a trivial change to correctly handle timeout.

  === Original Bug Report ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  System info
  ===

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

  # lspci -tv
  -[:00]-+-00.0  Intel Corporation 8th 

[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Rick]

20.04 beta still has this issue for me

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller

[Aki Nyrhinen]

I'm also getting the above errors when trying to read from a 1080p60
USB3 webcam. It seems I have some information not mentioned above.

[8.822044] usb 4-2: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[8.851879] usb 4-2: New USB device found, idVendor=15aa, idProduct=1555, 
bcdDevice=10.02
[8.851883] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[8.851886] usb 4-2: Product: 3.0 USB Camera

When opening /dev/video0 with an application, I immediatelly get the
following error repeatedly (but event-dma increments by 0x10 each line),
as seems to be the case for everyone.

[   54.007465] xhci_hcd :01:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
[   54.010154] xhci_hcd :01:00.0: Looking for event-dma 000849690010 
trb-start 00084969 trb-end 00084969 seg-start 00084969 
seg-end 000849690ff0

I added some previously posted diagnostic code from Mathias Nyman to
drivers/usb/host/xhci-ring.c, and got the following, which is similar to
previously reported bug with some ASMedia chip, but seems to be missing
transfer events much more frequently. It seems to be missing a "Transfer
Event" after each "Normal" packet. It's not about the LINK TRB because
it doesn't work for long enough to get to it (there's plenty of zeroed
out descriptors at the end of both rings, which I've omitted).

This is likely an ASMedia firmware/hardware issue, though this card (&
camera) works fine on the same machine when running Windows. I saw
mentions that ASMedia would be releasing a firmware fix, but I've
updated to what I believe to be the latest and it didn't help at all.
Has anyone found a firmware that works?

Attached dmesg also contains the event & endpoint ring dumps


** Attachment added: "asm1142-trace.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749961/+attachment/5345871/+files/asm1142-trace.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/1749961

Title:
  xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1
  Controller

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress
Status in linux package in Debian:
  Confirmed

Bug description:
  It was observed that while trying to use a 4K USB webcam connected to
  USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam
  does not work and kernel log shows the following messages:

  [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13
  [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 
trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 
seg-end 003f3330eff0
  [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 13

  A similar issue was already reported on Launchpad:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750

  The fix to this issue seems to be the following patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109

  Tests in our scenario with this patch proved still broken. Our next
  approach is to modify the patch a bit and re-test.

  This LP will be used to document our progress in the investigation.

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

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

[Kernel-packages] [Bug 1768452] Re: Insert test_bpf module will report 4 failures for ubuntu_bpf_jit on X s390x

[Kelsey Margarete Skunberg]

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

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

Title:
  Insert test_bpf module will report 4 failures for ubuntu_bpf_jit on X
  s390x

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

Bug description:
  == SRU Justification ==
  In the ubuntu_bpf_jit test, it will insert the test_bpf module to perform the 
test. There will be 4 failures reported on s390x instances by the test, 3 of 
them were simply because they cannot be jited on s390x:
    * test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations FAIL to 
prog_create err=-524 len=4096
    * test_bpf: #244 BPF_MAXINSNS: Call heavy transformations FAIL to 
prog_create err=-524 len=4096
    * test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create 
err=-524 len=4096

  (For another failure "ld_abs+vlan_push/pop" please check bug 1868243)

  == Fix ==
  * 3203c901 (test_bpf: flag tests that cannot be jited on s390)
  Only Xenial needs this patch, and it needs to be backported to Xenial
  as some test case does not exist.

  == Test ==
  Test kernel could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1768452-bpf-jit/

  The test will be marked as pass with the patched kernel:
  test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations PASS
  test_bpf: #244 BPF_MAXINSNS: Call heavy transformations PASS
  test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id PASS

  == Regression Potential ==
  Low, change limited to the test_bpf module itself and specific to s390x, no 
impact to real functions.

  == Original Bug Report ==
  After the test_bpf insert issue for Xenial was fixed in bug 1765698

  But it looks like the s390x needs some extra work.
  $ sudo modprobe test_bpf
  modprobe: ERROR: could not insert 'test_bpf': Invalid argument

  4 tests failed here:
    test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create 
err=-524 len=4096
    test_bpf: #244 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create 
err=-524 len=4096
    test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create 
err=-524 len=4096
    test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime 
err=-524

  Complete test result:
  https://pastebin.ubuntu.com/p/zMDwVjwF7X/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-123-generic 4.4.0-123.147
  ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128
  Uname: Linux 4.4.0-123-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Wed May  2 03:45:22 2018
  HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-123-generic N/A
   linux-backports-modules-4.4.0-123-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1859380] Re: Sleep doesn't work on my ThinkPad X1 Yoga with Kubuntu 20.04

[Jonas Gamao]

Sorry for the late response

Do you want me to run that command when the lid is close?

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

Title:
  Sleep doesn't work on my ThinkPad X1 Yoga with Kubuntu 20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sleep button doesn't work at all, and when I close the lid, the screen
  goes black, but there's a cursor, and it doesn't respond.  Had to
  force shut down.

  Operating System: Kubuntu 20.04
  KDE Plasma Version: 5.17.5
  KDE Frameworks Version: 5.66.0
  Qt Version: 5.12.5
  Kernel Version: 5.4.0-9-generic
  OS Type: 64-bit
  Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
  Memory: 15.3 GiB of RAM

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: kubuntu-desktop 1.392
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Jan 12 19:24:55 2020
  InstallationDate: Installed on 2020-01-03 (9 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: kubuntu-meta
  UpgradeStatus: Upgraded to focal on 2020-01-12 (0 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-25 (9 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200120)
  IwConfig:
   wlp0s20f3  no wireless extensions.
   
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
  MachineType: LENOVO 20SA0002US
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=d3ea3aaf-4630-491b-8315-c7efa5381fdf ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  Tags:  focal
  Uname: Linux 5.4.0-12-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: 01/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2QET19W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SA0002US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20SA0002US
  dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1868217] Re: Make Dell WD19 dock more reliable after suspend

[Kelsey Margarete Skunberg]

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

Title:
   Make Dell WD19 dock more reliable after suspend

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

Bug description:
  [Impact]
  When Dell WD19 dock connects multiple USB3 storage devices, the USB Hub
  used internally may stop working after suspend.

  [Fix]
  Disable LPM on the Realtek USB Hub, and let xHCI controller make sure
  the link state transition is completed.

  [Test]
  After applying the patches, the Dell WD19 works reliably after thousand
  times for suspend/resume cycle.

  [Regression Potential]
  Low. This replaces the currently "msleep" way with more robust
  mechanism. I also test other systems and nothing breaks.

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

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

[Kernel-packages] [Bug 1866772] Re: Sys oopsed with sysfs test in ubuntu_stress_smoke_test on X-hwe ARM64

[Kelsey Margarete Skunberg]

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

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

Title:
  Sys oopsed with sysfs test in ubuntu_stress_smoke_test on X-hwe ARM64

Status in Stress-ng:
  New
Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Released

Bug description:
  == SRU Request [ BIONIC, EOAN, FOCAL ] ==

  Reading /sys/firmware/acpi/tables/data/BERT as root at at odd byte
  offset will cause an oops.  This is because the source address is I/O
  mapped and this needs to be read with an I/O memcpy rather than an
  memcpy.

  == Fix ==

  The fix is upstream (linux-next) commit that will land in 5.7, the
  backport to bionic, eoan and focal is just a minor context wiggle.

  commit 08c07cefb3042a55bc9f8243814b504d5eff93f3
  Author: Colin Ian King 
  Date:   Thu Mar 12 11:13:45 2020 +

  ACPI: sysfs: copy ACPI data using io memory copying

  == Test ==

  Running on hotdog with the reproducer below (run as root):

  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(void)
  {
  int fd;
  char buffer[3];
  ssize_t n;

  fd = open("/sys/firmware/acpi/tables/data/BERT", O_RDONLY);
  if (fd < 0) {
  fprintf(stderr, "open failed: %d (%s)\n", errno, 
strerror(errno));
  return -1;
  }
  do {
  n = read(fd, buffer, sizeof(buffer));
  } while (n > 0);

  return 0;
  }

  Without the fix it will oops. With the fix it works OK.

  == Regession Potential ==

  This only affects the reading of the ACPI BERT table from /sys as root
  so it is limited in scope to just a very narrow use case. Normally the
  BERT table is just handled by the kernel, so access to this table is
  just for debugging purposes.

  ---

  Issue found on new ARM64 node "hotdog" 4.15.0-91.92~16.04.1
  Failed 2 of 2 attempts.

  Test suite HEAD SHA1: 3f43e81

   sysfs STARTING
   sysfs RETURNED 0
   sysfs FAILED (kernel oopsed)
   [ 1075.760640] Unable to handle kernel paging request at virtual address 
4a70072a
   [ 1075.763319] Unable to handle kernel paging request at virtual address 
4a70e4ba
   [ 1075.768563] Mem abort info:
   [ 1075.768566]   ESR = 0x9621
   [ 1075.768568]   Exception class = DABT (current EL), IL = 32 bits
   [ 1075.768569]   SET = 0, FnV = 0
   [ 1075.768570]   EA = 0, S1PTW = 0
   [ 1075.768571] Data abort info:
   [ 1075.768577]   ISV = 0, ISS = 0x0021
   [ 1075.776489] Mem abort info:
   [ 1075.776491]   ESR = 0x9621
   [ 1075.776493]   Exception class = DABT (current EL), IL = 32 bits
   [ 1075.776494]   SET = 0, FnV = 0
   [ 1075.776495]   EA = 0, S1PTW = 0
   [ 1075.776496] Data abort info:
   [ 1075.776500]   ISV = 0, ISS = 0x0021
   [ 1075.779284]   CM = 0, WnR = 0
   [ 1075.779288] swapper pgtable: 4k pages, 48-bit VAs, pgd = facfed4f
   [ 1075.779290] [4a70072a] *pgd=00bffcffe003, 
*pud=009f6122c003, *pmd=00bf5adf4003, *pte=006880280703
   [ 1075.782342]   CM = 0, WnR = 0
   [ 1075.782346] swapper pgtable: 4k pages, 48-bit VAs, pgd = facfed4f
   [ 1075.782352] [4a70e4ba] *pgd=00bffcffe003, 
*pud=009f6122c003, *pmd=00bf5adf4003, *pte=00688028e703
   [ 1075.788262] Internal error: Oops: 9621 [#2] SMP
   [ 1075.788269] Modules linked in: unix_diag binfmt_misc snd_seq 
snd_seq_device snd_timer snd soundcore userio vfio_iommu_type1 vfio hci_vhci 
bluetooth ecdh_generic uhid cuse vhost_vsock vmw_vsock_virtio_transport_common 
vhost_net vhost vsock tap dccp_ipv4 dccp ipx p8023 atm psnap p8022 llc 
algif_rng algif_aead anubis fcrypt khazad seed tea md4 michael_mic 
poly1305_generic rmd128 rmd160 rmd256 rmd320 sha3_generic sm3_generic tgr192 
wp512 algif_hash chacha20_neon chacha20_generic blowfish_generic 
blowfish_common cast5_generic des_generic salsa20_generic camellia_generic 
cast6_generic cast_common serpent_generic twofish_generic twofish_common 
algif_skcipher af_alg nls_iso8859_1 ipmi_ssif ipmi_devintf joydev input_leds 
ipmi_msghandler shpchp i2c_xlp9xx(+) thunderx2_pmu ib_iser rdma_cm iw_cm ib_cm 
ib_core
   [ 1075.942470]  iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 
btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
hid_generic usbhid hid uas usb_storage aes_ce_blk aes_ce_cipher crc32_ce qede 
ast i2c_algo_bit crct10dif_ce ptp ghash_ce ttm drm_kms_helper sha2_ce 

[Kernel-packages] [Bug 1867790] Re: update-version-dkms doesn't add a BugLink

[Kelsey Margarete Skunberg]

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

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

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

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

Title:
  update-version-dkms doesn't add a BugLink

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

Bug description:
  == Impact ==
  When there are updates on the dkms versions used for a linux build, 
'update-version-dkms' saves the new version(s) in 'debian/dkms-versions' and 
commits it. The commit doesn't have any BugLink, so it gets added to the debian 
changelog under "* Miscellaneous Ubuntu changes".

  == Fix ==
  Change 'update-version-dkms' to add a BugLink to 
https://bugs.launchpad.net/bugs/1786013 ("Packaging resync"), which is the bug 
report being used for all the other automated commits.

  == Test Case ==
  In one of the main kernels, run 'update-version-dkms' and make sure it adds a 
valid BugLink.

  == Regression Potential ==
  Low. This only changes how the automated commits are generated and later 
added to the changelog.

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

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

[Kernel-packages] [Bug 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series

[Kelsey Margarete Skunberg]

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

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

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

Title:
  Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility
  to the 340 and 390 series

Status in linux package in Ubuntu:
  Triaged
Status in linux-restricted-modules package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux-restricted-modules source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-440 source package in Bionic:
  Fix Committed
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux-restricted-modules source package in Eoan:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Eoan:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Eoan:
  Fix Committed
Status in nvidia-graphics-drivers-440 source package in Eoan:
  Fix Committed
Status in nvidia-settings source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  440.40:
    * New upstream release:
  - Added support for the following GPU:
  Quadro T2000 with Max-Q Design
  - Added support for the __GL_SYNC_DISPLAY_DEVICE environment
    variable for Vulkan applications.
  - Fixed a bug that caused applications running directly on a
    display (such as VR HMDs) to tear when a G-SYNC or G-SYNC
    Compatible monitor is plugged in the system.
  - Fixed a bug in an error handling path that could cause a kernel
    crash while loading nvidia.ko.
  - Fixed driver installation failure on Oracle Linux 7.7 systems,
    where the NVIDIA kernel module failed to build with error
    "unknown type name 'vm_fault_t'".
    * Changes from the 440.36 series:
  - Added support for the following GPUs:
    o GeForce GTX 1650 SUPER
    o GeForce GTX 1660 SUPER
  - Fixed graphical corruption that can occur when using glslang
    SPIR-V Generator Version <= 2.
  - Fixed a bug that could cause the X server to crash when running
    applications using GLX indirect rendering.
  - Updated the Module.symvers sanity check, which is part of the
    NVIDIA kernel module build process, to accommodate the recent
    addition of a new field in the Module.symvers file format.
    This fixes the error "The Module.symvers file is missing [...]"
    seen during driver installation or DKMS rebuilds with Linux 5.4 RC
    kernels.
  - Fixed kernel module build problems with Linux kernel 5.4.0 release
    candidates.
  - Updated nvidia-bug-report.sh to collect information about X server
    crashes from coredumpctl, when available.
  - Updated the nvidia-drm kernel module for compatibility with the
    removal of the DRIVER_PRIME flag in recent Linux kernel versions.
  - Enabled parallel GLSL shader linking by default; i.e., allow
    GL_ARB_parallel_shader_compile to work without first calling
    glMaxShaderCompilerThreadsARB().
  - Added support for HDMI 2.1 variable refresh rate (VRR) G-SYNC
    Compatible monitors on supported GPUs.For more details, see
    "Configuring Multiple Display Devices on One X Screen" in the README.
    Added support for the GLX_NV_multigpu_context and GL_NV_gpu_multicast
    extensions.For more details, see the "Configuring SLI and Multi-GPU
   

[Kernel-packages] [Bug 1812638] Re: reuseport_bpf_numa in net from ubuntu_kernel_selftests failed on i386

[Kelsey Margarete Skunberg]

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

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

Title:
  reuseport_bpf_numa in net from ubuntu_kernel_selftests failed on i386

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  The reuseport_bpf_numa test in net category from ubuntu_kernel_selftests
  will fail on i386 systems with:
selftests: reuseport_bpf_numa

not ok 1..3 selftests: reuseport_bpf_numa [FAIL]

  If you run it directly, you will see the test is simply not supported.
$ sudo ./reuseport_bpf_numa
./reuseport_bpf_numa: no numa api support: Function not implemented

  == Fix ==
  * 1a2b80ec (selftests: net: reuseport_bpf_numa: don't fail if no numa
   support)

  We have this patch in newer kernel from D, and we don't run this test
  on Xenial so only Bionic needs this patch.

  == Test ==
  Tested on a Bionic i386 node and it works as expected.
selftests: reuseport_bpf_numa

1..0 # Skipped: no numa api support
ok 1..3 selftests: reuseport_bpf_numa [PASS]

  == Regression Potential ==
  Low, trival change to testing tool itself.

  
  == Original Bug Report ==
  Test failed with:
  $ sudo ./reuseport_bpf_numa
  ./reuseport_bpf_numa: no numa api support: Function not implemented

  Maybe this one should be skipped.

  selftests: reuseport_bpf_numa
   
   not ok 1..3 selftests: reuseport_bpf_numa [FAIL]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic i686
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 21 10:52 seq
   crw-rw 1 root audio 116, 33 Jan 21 10:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon Jan 21 11:06:26 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R310
  PciMultimedia:

  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=6aaa11f6-d386-4c0c-b4b8-38e6c408980a ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 05XKKK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd09/18/2012:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R310
  dmi.sys.vendor: Dell Inc.

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

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

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

[bugproxy]

--- Comment From mranw...@us.ibm.com 2020-04-03 16:36 EDT---
We did some testing with that patch (previous comment) on top of the 
5.4.0-21.25+lp1866909v202004020814 source/config file.  We signed the 
kernel/modules and securely booted it.  That fixed the module loading issue we 
were having when trying 5.4.0-21.25+lp1866909v202004020814 and seemed to be 
generally successful.

We'll try the PPA once that's done building.  Thank you, again.

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

Title:
  Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - George C. Wilson  - 2020-02-25 18:40:44 
==
  - sysfs enablement: TBD
  - ima: arch specific policy support 6191706246de
  - platform keyring changes for powerpc: TBD
  - Appended signatures support for IMA appraisal 
39b07096364a42c516415d5f841069e885234e61
  - integrity: Define a trusted platform keyring: 9dc92c45177a
  - ima: Support platform keyring for kernel appraisal: d7cecb676dd3
  - TPM 2.0 Multibank extend support: c1f92b4b04ad
  - TPM 2.0 Eventlog support: 4d23cc323cdb
  - ima: carry the measurement list across kexec: d68a6fe9fccf
  - kexec_file_load system call support: 500c7ab1a9db

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

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

[Kernel-packages] [Bug 1862760] Re: Unreliable 802.11ac connection on our raspi images

[Brian Murray]

I went ahead and ran through the Raspbian setup again and this time I
said I was in the UK. After that and rebooting I ran 'iw reg get' and
the results showed "country GB: DFS-ETSI".

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

Title:
  Unreliable 802.11ac connection on our raspi images

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware-raspi2 package in Ubuntu:
  Triaged
Status in linux-raspi2-5.3 package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  New
Status in linux-firmware-raspi2 source package in Bionic:
  New
Status in linux-raspi2-5.3 source package in Bionic:
  New
Status in linux-firmware source package in Eoan:
  New
Status in linux-firmware-raspi2 source package in Eoan:
  New
Status in linux-raspi2-5.3 source package in Eoan:
  New
Status in linux-firmware source package in Focal:
  New
Status in linux-firmware-raspi2 source package in Focal:
  Triaged
Status in linux-raspi2-5.3 source package in Focal:
  New

Bug description:
  We were not able to completely pin-point the issue yet, so this is
  more of a blanket bug for the current issues we are seeing. We don't
  know where exactly the issue can be located.

  While preparing and testing 18.04.4, certification reported issues
  with our uc18 images on the pi4 with wifi ac tests. One of our
  engineers (Brian) confirmed it locally with a wifi access point
  restricted only to 802.11ac. After some additional testing, he noticed
  that he had the same unreliable symptoms for both the classic and core
  images, as well as the 19.10.1 classic images. The symptoms seem to
  vary, from inability to detect 802.11ac APs, inability to connect
  and/or receive an IP address and no traffic getting through.

  We will provide all the information that we have. Raspbian works
  better in this regard. We have pulled in the wifi firmware bits from
  Raspbian and using those, and that seems to resolve all flakiness.

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

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

[Kernel-packages] [Bug 1869672] Re: kdump kernel can't be loaded using kernel 4.15.0-76

[Guilherme G. Piccoli]

Hi yamato, thank you for the report and prompt test!

So, I need to setup a guest with secureboot, I don't have it at hand. 
Meanwhile, can you test the in-between kernel versions, so we can narrow down 
when the problem was introduced?
The versions we had released in Bionic between -64 and -76 are: 
4.15.0-65-generic, 4.15.0-66-generic, 4.15.0-69-generic, 4.15.0-70-generic and 
4.15.0-72-generic.

If you could test with them all, certainly that would speed-up the resolution, 
while I work a VM with secureboot support.
Thanks again,


Guilherme

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

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

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

Title:
  kdump kernel can't be loaded using kernel 4.15.0-76

Status in makedumpfile package in Ubuntu:
  New

Bug description:
  Thank you for reading this report.
  This may caused by bugs in kernel, not in kdump. If so, I will report this to 
kernel team.
  I need your comment to solve this.

  [Impact]
  * Kdump kernel can't be loaded using linux kernel 4.15.0-76.

  [Environment]
  Description:Ubuntu 18.04.4 LTS
  Release:18.04

  uname:
  Linux ubuntu 4.15.0-76-generic #86-Ubuntu SMP Fri Jan 17 17:24:28 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  Secure boot is enabled.

  Versions:
  * kexec-tools/bionic-updates,now 1:2.0.16-1ubuntu1.1
  * kdump-tools/bionic-updates,now 1:1.6.5-1ubuntu1~18.04.4

  [Test case]
  1)After OS booted, run systemctl status kdump-tools shows these messages 
below:

  
  ● kdump-tools.service - Kernel crash dump capture service
     Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
preset: enabled)
     Active: active (exited) since Fri 2020-03-27 16:40:31 JST; 5min ago
    Process: 895 ExecStart=/etc/init.d/kdump-tools start (code=exited, 
status=0/SUCCESS)
   Main PID: 895 (code=exited, status=0/SUCCESS)

  Mar 27 16:40:31 ubuntu systemd[1]: Starting Kernel crash dump capture 
service...
  Mar 27 16:40:31 ubuntu kdump-tools[895]: Starting kdump-tools:  * Creating 
symlink /var/lib/kdump/vmlinuz
  Mar 27 16:40:31 ubuntu kdump-tools[895]:  * Creating symlink 
/var/lib/kdump/initrd.img
  Mar 27 16:40:31 ubuntu kdump-tools[895]: kexec_file_load failed: Exec format 
error
  Mar 27 16:40:31 ubuntu kdump-tools[895]:  * failed to load kdump kernel
  Mar 27 16:40:31 ubuntu systemd[1]: Started Kernel crash dump capture service.
  

  2)Run kexec directly:
  $ sudo /sbin/kexec -p --command-line="/boot/vmlinuz-4.15.0-76-generic 
root=UUID=29a89ad8-8923-435e-a88c-aaf5cb379568 ro mce=ignore_ce reset_devices 
systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb 
ata_piix.prefer_ms_hyperv=0" --initrd=/boot/initrd.img-4.15.0-76-generic 
/boot/vmlinuz-4.15.0-64-generic

  Then,these messages are shown:
  Cannot open /proc/kcore: Operation not permitted
  Cannot read /proc/kcore: Operation not permitted
  Cannot load /boot/vmlinuz-4.15.0-76-generic

  On dmesg, these messages are shown:
  
  [  538.524718] Lockdown: /proc/kcore is restricted; see man kernel_lockdown.7
  

  3) Changing OS kernel to older one(I used 4.15.0-64), kdump kernel can
  be loaded.

  $ sudo systemctl status kdump-tools
  ● kdump-tools.service - Kernel crash dump capture service
     Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
preset: enabled)
     Active: active (exited) since Wed 2020-03-25 13:39:03 JST; 5 days ago
   Main PID: 832 (code=exited, status=0/SUCCESS)
  Tasks: 0 (limit: 4915)
     CGroup: /system.slice/kdump-tools.service

  Mar 25 13:39:02 ubuntu systemd[1]: Starting Kernel crash dump capture 
service...
  Mar 25 13:39:02 ubuntu kdump-tools[832]: Starting kdump-tools:  * Creating 
symlink /var/lib/kdump/vmlinuz
  Mar 25 13:39:02 ubuntu kdump-tools[832]:  * Creating symlink 
/var/lib/kdump/initrd.img
  Mar 25 13:39:03 ubuntu kdump-tools[832]:  * loaded kdump kernel
  Mar 25 13:39:03 ubuntu kdump-tools[938]: loaded kdump kernel
  Mar 25 13:39:03 ubuntu systemd[1]: Started Kernel crash dump capture service.

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  [MEDION E122X] hibernate/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Had terminal and firefox open.

  Then atemmepted to see if i could hibernate with

  pm-hibernate

  just to see if it worked

  ProblemType: KernelOops
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darkyere   1121 F pulseaudio
  Date: Fri Apr  3 21:57:45 2020
  DuplicateSignature: hibernate/resume:MEDION E122X:Medion-E122X_0107
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  InstallationDate: Installed on 2020-04-02 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  InterpreterPath: /usr/bin/python3.8
  MachineType: MEDION E122X
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/LubuntuRootLVM-Root 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.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  Title: [MEDION E122X] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/11/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Medion-E122X_0107
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: E122X
  dmi.board.vendor: MEDION
  dmi.board.version: Rev 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: MEDION
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMedion-E122X_0107:bd05/11/2010:svnMEDION:pnE122X:pvrVer01.07:rvnMEDION:rnE122X:rvrRev1.0:cvnMEDION:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: E122X
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: Ver: 01.07
  dmi.sys.vendor: MEDION

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

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

[Kernel-packages] [Bug 1806242] Re: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A/B/C

[Carcalac]

i have the same issue on ubuntu 19.10

Apr  3 22:43:21 HP-15-cs3xxx kernel: [ 8867.271966]
[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe
A (start=532823 end=532824) time 143 us, min 1073, max 1079, scanline
start 1072, end 1081

cat /etc/modprobe.d/i915.conf

options i915 enable_psr=0
options i915 enable_guc=2

5.3.0-45-generic

followed by one of the eight cores going crazy ~100% usage and i have to
reboot because the system becomes slow..

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

Title:
  kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
  failure on pipe A/B/C

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I have this error and arbitrary freezes on the system

  My System:

  Hardware:
  Processor: Intel Core i7-8750H @ 4.10GHz (12 Cores), Motherboard: Dell 
0M2MWX, Chipset: Intel Device a36f, Memory: 16384MB, Disk: 1000GB Seagate 
ST1000LM035-1RK1 + 256GB TOSHIBA KSG60ZMV, Graphics: Intel Device 3e9b, Audio: 
Realtek ALC3246, Monitor: DELL P2016, Network: Qualcomm Atheros Killer E2400 
Gigabit + Intel Device a370

  Software:
  OS: Ubuntu 18.04, Kernel: 4.15.0-39-generic (x86_64), Desktop: Xfce 4.12, 
Display Driver: modesetting 1.19.6, OpenGL: 4.5 Mesa 18.0.5, File-System: ext4, 
Screen Resolution: 1920x1980

  dmesg output:

  Dec  2 16:00:22 G5 kernel: [ 2027.018608] [drm:intel_pipe_update_end [i915]] 
*ERROR* Atomic update failure on pipe B (start=15726 end=15727) time 1024 us, 
min 894, max 899, scanline start 845, end 903
  Dec  2 16:08:50 G5 kernel: [ 2534.448063] ACPI Error: [LCD_] Namespace lookup 
failure, AE_NOT_FOUND (20170831/psargs-364)
  Dec  2 16:08:50 G5 kernel: [ 2534.448071] No Local Variables are initialized 
for Method [BRT6]
  Dec  2 16:08:50 G5 kernel: [ 2534.448072] Initialized Arguments for Method 
[BRT6]:  (2 arguments defined for method invocation)
  Dec  2 16:08:50 G5 kernel: [ 2534.448073]   Arg0:   a83faa08 
   Integer 0001
  Dec  2 16:08:50 G5 kernel: [ 2534.448076]   Arg1:   35246c42 
   Integer 
  Dec  2 16:08:50 G5 kernel: [ 2534.448079] ACPI Error: Method parse/execution 
failed \_SB.PCI0.PEG0.PEGP.BRT6, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448145] ACPI Error: Method parse/execution 
failed \EV5, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448206] ACPI Error: Method parse/execution 
failed \SMEE, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448268] ACPI Error: Method parse/execution 
failed \SMIE, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448332] ACPI Error: Method parse/execution 
failed \NEVT, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:08:50 G5 kernel: [ 2534.448394] ACPI Error: Method parse/execution 
failed \_SB.PCI0.LPCB.ECDV._Q66, AE_NOT_FOUND (20170831/psparse-550)
  Dec  2 16:14:41 G5 kernel: [ 2885.660715] acpi INT3400:00: Unsupported event 
[0x86]
  Dec  2 16:14:45 G5 kernel: [ 2889.787584] acpi INT3400:00: Unsupported event 
[0x86]
  Dec  2 16:20:32 G5 kernel: [ 3237.026638] [drm:intel_pipe_update_end [i915]] 
*ERROR* Atomic update failure on pipe B (start=88190 end=88191) time 1687 us, 
min 894, max 899, scanline start 864, end 14
  Dec  2 16:22:20 G5 kernel: [ 3344.842212] wlp0s20f3: AP 90:ef:68:2c:31:9b 
changed bandwidth, new config is 2432 MHz, width 2 (2422/0 MHz)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  instantcrush   1622 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-11-28 (4 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. G5 5587
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=0017db25-edad-4311-bca6-171f2624432e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.2
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/01/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.1
  dmi.board.name: 0M2MWX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Kernel-packages] [Bug 1813423] Re: System freezing or flickering with i915 error [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A

[Carcalac]

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

i have the same issue on ubuntu 19.10

cat /etc/modprobe.d/i915.conf

options i915 enable_psr=0
options i915 enable_guc=2


5.3.0-45-generic

followed by one of the eight cores going crazy ~100% usage and i have to
reboot because the system becomes slow..

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

Title:
  System freezing or flickering with i915 error
  [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on
  pipe A

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  My system keeps freezing on a brand new install of Kubuntu 18.10,
  always with the kern.log error "[drm:intel_pipe_update_end [i915]]
  *ERROR* Atomic update failure on pipe A (start=4120234 end=4120235)
  time 486 us, min 763, max 767, scanline start 760, end 783"

  I think it's probably a duplicate of these bugs which were closed unresolved:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619 (closed as it was 
on an older version of Ubuntu)
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1671975 (closed because 
it was a duplicate of the first bug)

  It happens far more frequently if I have desktop effects turned on,
  and far less frequently when using a live USB key (at always happens
  eventually though. Usually once every few hours.)

  Please advise how I can help triage / test. My system is a new install
  now, so I'm perfectly willing to modify / reinstall to help testing
  (I've reinstalled 5 times to test things, but never managed to find a
  solution)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Jan 26 14:19:52 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:227a]
  InstallationDate: Installed on 2019-01-18 (8 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=2c4bf3d1-1ff2-4345-95c0-c68d0e073df9 ro nogpumanager 
modprobe.blacklist=nouveau,nvidiafb,nvidia-modeset,nvidia-uvm,nvidia 
intel_iommu=igfx_off i915.semaphores=1 i915.enable_fbc=0 i915.modeset=1 
i915.enable_rc=7 i915.enable_dc=2 i915.enable_ppgtt=3 i915.enable_guc_loading=1 
i915.lvds_channel_mode=2 i915.lvds_use_ssc=1 quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.42
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 227A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 76.35
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.42:bd03/18/2015:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr096C110800405F1620180:rvnHewlett-Packard:rn227A:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 14 Notebook PC
  dmi.product.sku: J9L01UA#ABL
  dmi.product.version: 096C110800405F1620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Kernel-packages] [Bug 1870616] Re: [MEDION E122X] hibernate/resume failure

[Apport retracing service]

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

** Tags removed: need-duplicate-check

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

Title:
  [MEDION E122X] hibernate/resume failure

Status in linux package in Ubuntu:
  New

Bug description:
  Had terminal and firefox open.

  Then atemmepted to see if i could hibernate with

  pm-hibernate

  just to see if it worked

  ProblemType: KernelOops
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darkyere   1121 F pulseaudio
  Date: Fri Apr  3 21:57:45 2020
  DuplicateSignature: hibernate/resume:MEDION E122X:Medion-E122X_0107
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  InstallationDate: Installed on 2020-04-02 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  InterpreterPath: /usr/bin/python3.8
  MachineType: MEDION E122X
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/LubuntuRootLVM-Root 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.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  Title: [MEDION E122X] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/11/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Medion-E122X_0107
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: E122X
  dmi.board.vendor: MEDION
  dmi.board.version: Rev 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: MEDION
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMedion-E122X_0107:bd05/11/2010:svnMEDION:pnE122X:pvrVer01.07:rvnMEDION:rnE122X:rvrRev1.0:cvnMEDION:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: E122X
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: Ver: 01.07
  dmi.sys.vendor: MEDION

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

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

[Kernel-packages] [Bug 1870616] [NEW] [MEDION E122X] hibernate/resume failure

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Had terminal and firefox open.

Then atemmepted to see if i could hibernate with

pm-hibernate

just to see if it worked

ProblemType: KernelOops
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-21-generic 5.4.0-21.25
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  darkyere   1121 F pulseaudio
Date: Fri Apr  3 21:57:45 2020
DuplicateSignature: hibernate/resume:MEDION E122X:Medion-E122X_0107
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: hibernate/resume
InstallationDate: Installed on 2020-04-02 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
InterpreterPath: /usr/bin/python3.8
MachineType: MEDION E122X
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/LubuntuRootLVM-Root 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.
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-21-generic N/A
 linux-backports-modules-5.4.0-21-generic  N/A
 linux-firmware1.187
SourcePackage: linux
Title: [MEDION E122X] hibernate/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 05/11/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: Medion-E122X_0107
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: E122X
dmi.board.vendor: MEDION
dmi.board.version: Rev 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: MEDION
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMedion-E122X_0107:bd05/11/2010:svnMEDION:pnE122X:pvrVer01.07:rvnMEDION:rnE122X:rvrRev1.0:cvnMEDION:ct10:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: E122X
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: Ver: 01.07
dmi.sys.vendor: MEDION

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


** Tags: amd64 apport-kerneloops focal hibernate need-duplicate-check resume
-- 
[MEDION E122X] hibernate/resume failure
https://bugs.launchpad.net/bugs/1870616
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1870604] [NEW] Bionic update: upstream stable patchset 2020-04-03

[Kamal Mostafa]

Public bug reported:

SRU Justification

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

   upstream stable patchset 2020-04-03

Ported from the following upstream stable releases:
v4.14.175, v4.19.113,
   v4.19.114

   from git://git.kernel.org/

spi: qup: call spi_qup_pm_resume_runtime before suspending
powerpc: Include .BTF section
ARM: dts: dra7: Add "dma-ranges" property to PCIe RC DT nodes
spi: pxa2xx: Add CS control clock quirk
spi/zynqmp: remove entry that causes a cs glitch
drm/exynos: dsi: propagate error value and silence meaningless warning
drm/exynos: dsi: fix workaround for the legacy clock name
drivers/perf: arm_pmu_acpi: Fix incorrect checking of gicc pointer
altera-stapl: altera_get_note: prevent write beyond end of 'key'
dm bio record: save/restore bi_end_io and bi_integrity
xenbus: req->body should be updated before req->state
xenbus: req->err should be updated before req->state
block, bfq: fix overwrite of bfq_group pointer in bfq_find_set_group()
parse-maintainers: Mark as executable
USB: Disable LPM on WD19's Realtek Hub
usb: quirks: add NO_LPM quirk for RTL8153 based ethernet adapters
USB: serial: option: add ME910G1 ECM composition 0x110b
usb: host: xhci-plat: add a shutdown
USB: serial: pl2303: add device-id for HP LD381
usb: xhci: apply XHCI_SUSPEND_DELAY to AMD XHCI controller 1022:145c
ALSA: line6: Fix endless MIDI read loop
ALSA: seq: virmidi: Fix running status after receiving sysex
ALSA: seq: oss: Fix running status after receiving sysex
ALSA: pcm: oss: Avoid plugin buffer overflow
ALSA: pcm: oss: Remove WARNING from snd_pcm_plug_alloc() checks
iio: trigger: stm32-timer: disable master mode when stopping
iio: magnetometer: ak8974: Fix negative raw values in sysfs
mmc: sdhci-of-at91: fix cd-gpios for SAMA5D2
staging: rtl8188eu: Add device id for MERCUSYS MW150US v2
staging/speakup: fix get_word non-space look-ahead
intel_th: Fix user-visible error codes
intel_th: pci: Add Elkhart Lake CPU support
rtc: max8907: add missing select REGMAP_IRQ
xhci: Do not open code __print_symbolic() in xhci trace events
memcg: fix NULL pointer dereference in __mem_cgroup_usage_unregister_event
mm: slub: be more careful about the double cmpxchg of freelist
mm, slub: prevent kmalloc_node crashes and memory leaks
page-flags: fix a crash at SetPageError(THP_SWAP)
x86/mm: split vmalloc_sync_all()
USB: cdc-acm: fix close_delay and closing_wait units in TIOCSSERIAL
USB: cdc-acm: fix rounding error in TIOCSSERIAL
iio: adc: at91-sama5d2_adc: fix channel configuration for differential channels
iio: adc: at91-sama5d2_adc: fix differential channels in triggered mode
kbuild: Disable -Wpointer-to-enum-cast
futex: Fix inode life-time issue
futex: Unbreak futex hashing
Revert "vrf: mark skb for multicast or link-local as enslaved to VRF"
Revert "ipv6: Fix handling of LLA with VRF and sockets bound to VRF"
ALSA: hda/realtek: Fix pop noise on ALC225
arm64: smp: fix smp_send_stop() behaviour
arm64: smp: fix crash_smp_send_stop() behaviour
drm/bridge: dw-hdmi: fix AVI frame colorimetry
staging: greybus: loopback_test: fix potential path truncation
staging: greybus: loopback_test: fix potential path truncations
Revert "drm/dp_mst: Skip validating ports during destruction, just ref"
hsr: fix general protection fault in hsr_addr_is_self()
macsec: restrict to ethernet devices
net: dsa: Fix duplicate frames flooded by learning
net: mvneta: Fix the case where the last poll did not process all rx
net/packet: tpacket_rcv: avoid a producer race condition
net: qmi_wwan: add support for ASKEY WWHC050
net_sched: cls_route: remove the right filter from hashtable
net_sched: keep alloc_hash updated after hash allocation
net: stmmac: dwmac-rk: fix error path in rk_gmac_probe
NFC: fdp: Fix a signedness bug in fdp_nci_send_patch()
slcan: not call free_netdev before rtnl_unlock in slcan_open
bnxt_en: fix memory leaks in bnxt_dcbnl_ieee_getets()
net: dsa: mt7530: Change the LINK bit to reflect the link status
vxlan: check return value of gro_cells_init()
hsr: use rcu_read_lock() in hsr_get_node_{list/status}()
hsr: add restart routine into hsr_get_node_list()
hsr: set .netnsok flag
cgroup-v1: cgroup_pidlist_next should update position index
cpupower: avoid multiple definition with gcc -fno-common
drivers/of/of_mdio.c:fix of_mdiobus_register()
cgroup1: don't call release_agent when it is ""
UBUNTU: updateconfigs for DPAA_ERRATUM_A050385
dt-bindings: net: FMan erratum A050385
arm64: dts: ls1043a: FMan erratum A050385
fsl/fman: detect FMan erratum A050385
scsi: ipr: Fix softlockup when 

[Kernel-packages] [Bug 1845678] Re: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work

[Jean-]

under the following configuration the sound and microphone work as
described in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845678/comments/28

ii  libasound2:amd64   1.1.9-0ubuntu1.3 
  amd64shared library for ALSA applications
ii  libasound2-data1.1.9-0ubuntu1.3 
  all  Configuration files and profiles for ALSA drivers
ii  libasound2-plugins:amd64   1.1.9-0ubuntu1   
  amd64ALSA library additional plugins
ii  linux-firmware 1.183.5  
  all  Firmware for Linux kernel drivers
ii  linux-image-5.3.0-46-generic   5.3.0-46.38  
  amd64Signed kernel image generic
ii  linux-image-generic5.3.0.45.38  
  amd64Generic Linux kernel image
ii  linux-modules-5.3.0-46-generic 5.3.0-46.38  
  amd64Linux kernel extra modules for version 5.3.0 on 64 bit x86 
SMP
ii  linux-modules-extra-5.3.0-46-generic   5.3.0-46.38  
  amd64Linux kernel extra modules for version 5.3.0 on 64 bit x86 
SMP

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

Title:
  Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't
  work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The built-in microphone in my Lenovo ThinkPad X1 Carbon 7th Generation
  doesn't work.

  A microphone on a headset plugged into the 3.5mm jack works fine.

  This is probably relevant:
  https://bugzilla.kernel.org/show_bug.cgi?id=201251

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-12-generic 5.3.0-12.13
  ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
  Uname: Linux 5.3.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jik3746 F pulseaudio
   /dev/snd/pcmC0D0p:   jik3746 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 11:13:25 2019
  InstallationDate: Installed on 2019-09-12 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-12-generic N/A
   linux-backports-modules-5.3.0-12-generic  N/A
   linux-firmware1.182
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  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/1845678/+subscriptions

-- 
Mailing list: https://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 1855303] Re: Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5

[Jeff Lane]

Oh thanks!

I got some guidance from the kernel team that everything was mostly
ok, but I needed to update the commits so the cherry pick showed the
source it came from since it was not mainline.  I had started working
on updating all the commits, but, let me check what you've just
provided and I may not need to update anything (or update far less).
They did say that it shouldnt' be an issue getting these all in.  So
I'll try to get that pushed again this afternoon or tomorrow.

On Fri, Apr 3, 2020 at 1:36 PM Vignesh Gunasekaran
<1855...@bugs.launchpad.net> wrote:
>
> Hi Jeff,
>
> I went back to check if those patches in comment #5 are pulled from the
> MKP tree into the Mainline tree and I noticed that those are landed now.
>
> The SHA IDs of those commits in the Mainline kernel are as follows,
>
> df3fe76658ed scsi: lpfc: add RDF registration and Link Integrity FPIN logging
> 73ec6d2748dc scsi: fc: Update Descriptor definition and add RDF and Link 
> Integrity FPINs
> 145e5a8a5cbd scsi: lpfc: Copyright updates for 12.6.0.4 patches
> ad6203f97526 scsi: lpfc: Update lpfc version to 12.6.0.4
> f6770e7d2329 scsi: lpfc: Clean up hba max_lun_queue_depth checks
> 6cde2e3e2813 scsi: lpfc: Remove handler for obsolete ELS - Read Port Status 
> (RPS)
> 4cb9e1ddaa14 scsi: lpfc: Fix coverity errors in fmdi attribute handling
> a99c80742af4 scsi: lpfc: Fix compiler warning on frame size
> 821bc882acca scsi: lpfc: Fix release of hwq to clear the eq relationship
> 792f3b90be2a scsi: lpfc: Fix registration of ELS type support in fdmi
> 835214f5d5f5 scsi: lpfc: Fix broken Credit Recovery after driver load
> 0ab384a49c54 scsi: lpfc: Fix lpfc_io_buf resource leak in 
> lpfc_get_scsi_buf_s4 error path
>
> Could you pass on this info to your kernel team? So that all lpfc
> patches can be accepted.
>
> Thanks
> Vignesh
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1855303
>
> Title:
>   Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5
>
> Status in linux package in Ubuntu:
>   In Progress
> Status in linux source package in Focal:
>   In Progress
>
> Bug description:
>   [IMPACT]
>
>   This is related to bug
>   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856340
>
>   This is a significant number of updates by Broadcom to the lpfc driver
>   that didn't make 5.4 in time.  As 20.04 is an LTS release with
>   expected hardware support for 5 years, we need to ensure as much
>   hardware support lands as possible to support server vendors over the
>   next couple years.
>
>   Broadcom has updated the lpfc driver to version 12.6.0.4 in 5.5.  The
>   version in focal is 12.2.0.3 and missing several bug fixes and
>   hardware support additions.
>
>   Please update the driver in focal appropriately.
>
>   [FIXES]
>   eede4970fb6c29f2056d7d016a3764c90e9d8a65 scsi: lpfc: size cpu map by
>   last cpu id set
>   4583a4f66b323c6e4d774be2649e83a4e7c7b78c scsi: lpfc: use hdwq assigned
>   cpu for allocation
>   3b294c0fb910dc91250abab574e85c9c1957c795 scsi: lpfc: Update lpfc version
>   to 12.6.0.2
>   542ddc9b346984cb5bbc2a923d3f3f27ae961ffa scsi: lpfc: revise nvme max
>   queues to be hdwq count
>   bc227dde0d8b687aa525d01b0df5556d4d37eca3 scsi: lpfc: Initialize cpu_map
>   for not present cpus
>   d480e57809a04a3b9e755c0bdd43e10a9f12 scsi: lpfc: fix inlining of
>   lpfc_sli4_cleanup_poll_list()
>   6c6d59e0fe5b86cf273d6d744a6a9768c4ecc756 scsi: lpfc: fix: Coverity:
>   lpfc_cmpl_els_rsp(): Null pointer dereferences
>   6f23f8c5c9f1be4eb17c035129c80e49000c18a7 scsi: lpfc: fix: Coverity:
>   lpfc_get_scsi_buf_s3(): Null pointer dereferences
>   61951a6d3153b4482404b739be921a7459f8dc12 scsi: lpfc: Fix
>   lpfc_cpumask_of_node_init()
>   eea2d396aa57acb3607f79ef04c08c2c5166f3fa scsi: lpfc: Fix a kernel
>   warning triggered by lpfc_sli4_enable_intr()
>   765ab6cdac3b681952da0e22184bf6cf1ae41cf8 scsi: lpfc: Fix a kernel
>   warning triggered by lpfc_get_sgl_per_hdwq()
>   aff6ab9e7221c1b5d15418419b9797e5badd4aec scsi: lpfc: Update lpfc version
>   to 12.6.0.1
>   171f6c41949f6e9d5e09dcac842a10bf8dda8dcc scsi: lpfc: Add enablement of
>   multiple adapter dumps
>   dcaa213679387e95a315dca05c57dbb15273703c scsi: lpfc: Change default IRQ
>   model on AMD architectures
>   93a4d6f40198dffcca35d9a928c409f9290f1fe0 scsi: lpfc: Add registration
>   for CPU Offline/Online events
>   b9da814cd5f5bb93041a6e4dbc9c5149713186ff scsi: lpfc: Clarify FAWNN error
>   message
>   69641627c653464db46f3e3d8c438349be055670 scsi: lpfc: Sync with FC-NVMe-2
>   SLER change to require Conf with SLER
>   dda5bdf074da3782ff9e785ee50cd2a3f214d498 scsi: lpfc: Fix dynamic fw log
>   enablement check
>   2332e6e475b016e2026763f51333f84e2e6c57a3 scsi: lpfc: Fix unexpected
>   error messages during RSCN handling
>   6c1e803eac846f886cd35131e6516fc51a8414b9 scsi: lpfc: Fix kernel crash at
>   lpfc_nvme_info_show during remote port bounce
>   

[Kernel-packages] [Bug 1862760] Re: Unreliable 802.11ac connection on our raspi images

[Seth Forshee]

Based on some quick googling, I think there's some localization set up
on raspbian that must also cause it to set the regulatory domain.

https://www.raspberrypi.org/documentation/configuration/wireless/desktop.md

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

Title:
  Unreliable 802.11ac connection on our raspi images

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware-raspi2 package in Ubuntu:
  Triaged
Status in linux-raspi2-5.3 package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  New
Status in linux-firmware-raspi2 source package in Bionic:
  New
Status in linux-raspi2-5.3 source package in Bionic:
  New
Status in linux-firmware source package in Eoan:
  New
Status in linux-firmware-raspi2 source package in Eoan:
  New
Status in linux-raspi2-5.3 source package in Eoan:
  New
Status in linux-firmware source package in Focal:
  New
Status in linux-firmware-raspi2 source package in Focal:
  Triaged
Status in linux-raspi2-5.3 source package in Focal:
  New

Bug description:
  We were not able to completely pin-point the issue yet, so this is
  more of a blanket bug for the current issues we are seeing. We don't
  know where exactly the issue can be located.

  While preparing and testing 18.04.4, certification reported issues
  with our uc18 images on the pi4 with wifi ac tests. One of our
  engineers (Brian) confirmed it locally with a wifi access point
  restricted only to 802.11ac. After some additional testing, he noticed
  that he had the same unreliable symptoms for both the classic and core
  images, as well as the 19.10.1 classic images. The symptoms seem to
  vary, from inability to detect 802.11ac APs, inability to connect
  and/or receive an IP address and no traffic getting through.

  We will provide all the information that we have. Raspbian works
  better in this regard. We have pulled in the wifi firmware bits from
  Raspbian and using those, and that seems to resolve all flakiness.

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

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

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

[Reshad Dernjani]

Is https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1869481
possibly connected to this too?

-- 
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:
  [SRU] add ucm to make alsa/sof driver work under PA (variants of
  Lenovo X1 Carbon 7th, Dell cnl and cml machines)

Status in HWE Next:
  Fix Released
Status in alsa-lib package in Ubuntu:
  Invalid
Status in alsa-lib source package in Bionic:
  Fix Released
Status in alsa-lib source package in Eoan:
  Fix Released

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/hwe-next/+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 1862760] Re: Unreliable 802.11ac connection on our raspi images

[Brian Murray]

Just to be clear this is what iw reg get shows on Rasbian:

pi@raspberrypi:~$ iw reg get
global
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)

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

Title:
  Unreliable 802.11ac connection on our raspi images

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware-raspi2 package in Ubuntu:
  Triaged
Status in linux-raspi2-5.3 package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  New
Status in linux-firmware-raspi2 source package in Bionic:
  New
Status in linux-raspi2-5.3 source package in Bionic:
  New
Status in linux-firmware source package in Eoan:
  New
Status in linux-firmware-raspi2 source package in Eoan:
  New
Status in linux-raspi2-5.3 source package in Eoan:
  New
Status in linux-firmware source package in Focal:
  New
Status in linux-firmware-raspi2 source package in Focal:
  Triaged
Status in linux-raspi2-5.3 source package in Focal:
  New

Bug description:
  We were not able to completely pin-point the issue yet, so this is
  more of a blanket bug for the current issues we are seeing. We don't
  know where exactly the issue can be located.

  While preparing and testing 18.04.4, certification reported issues
  with our uc18 images on the pi4 with wifi ac tests. One of our
  engineers (Brian) confirmed it locally with a wifi access point
  restricted only to 802.11ac. After some additional testing, he noticed
  that he had the same unreliable symptoms for both the classic and core
  images, as well as the 19.10.1 classic images. The symptoms seem to
  vary, from inability to detect 802.11ac APs, inability to connect
  and/or receive an IP address and no traffic getting through.

  We will provide all the information that we have. Raspbian works
  better in this regard. We have pulled in the wifi firmware bits from
  Raspbian and using those, and that seems to resolve all flakiness.

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

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

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

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

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

Bug description:
  === SRU Justification ===
  [Impact]
  Some systems have a "phantom" Nvidia UCSI, which prevent systems from
  suspending. 

  [Fix]
  ucsi_ccg is stuck in its probe routine because of the i2c bus never
  timeouts. Let it timeouts and probe can fail since it's just a phantom
  device.

  [Test]
  After applying this patch system can suspend/resume succesfully.

  [Regression Potential]
  Low. It's a trivial change to correctly handle timeout.

  === Original Bug Report ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  System info
  ===

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

  

[Kernel-packages] [Bug 1862708] Re: tracing doesn't work on focal

[Seth Arnold]

Just to be clear, not *all* tracing tools work, but this is much better:

sarnold@millbarge:/tmp$ uname -a
Linux millbarge 5.4.0-21-generic #25-Ubuntu SMP Sat Mar 28 13:10:28 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
sarnold@millbarge:/tmp$ sudo zfsslower-bpfcc 
Traceback (most recent call last):
  File "/usr/sbin/zfsslower-bpfcc", line 265, in 
if BPF.get_kprobe_functions(b'zpl_iter'):
  File "/usr/lib/python3/dist-packages/bcc/__init__.py", line 539, in 
get_kprobe_functions
with open("%s/../kprobes/blacklist" % TRACEFS, "rb") as blacklist_f:
PermissionError: [Errno 1] Operation not permitted: 
'/sys/kernel/debug/tracing/../kprobes/blacklist'

Thanks

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

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Fix Released
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of 

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

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

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

Bug description:
  === SRU Justification ===
  [Impact]
  Some systems have a "phantom" Nvidia UCSI, which prevent systems from
  suspending. 

  [Fix]
  ucsi_ccg is stuck in its probe routine because of the i2c bus never
  timeouts. Let it timeouts and probe can fail since it's just a phantom
  device.

  [Test]
  After applying this patch system can suspend/resume succesfully.

  [Regression Potential]
  Low. It's a trivial change to correctly handle timeout.

  === Original Bug Report ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  System info
  ===

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

[Kernel-packages] [Bug 1867586] Re: [hns3-0316]sync mainline kernel 5.6rc4 hns3 patchset into ubuntu HWE kernel branch

[Andrew Cloke]

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

** Changed in: kunpeng920/ubuntu-18.04-hwe
Milestone: None => ubuntu-18.04.5

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

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

** Changed in: kunpeng920
   Status: New => Fix Committed

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

Title:
  [hns3-0316]sync mainline kernel 5.6rc4  hns3 patchset into ubuntu HWE
  kernel branch

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.6rc1 kernel.

  [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: clear port base VLAN when unload PF
  net: hns3: fix RMW issue for VLAN filter switch
  net: hns3: fix VF VLAN table entries inconsistent issue
  net: hns3: fix "tc qdisc del" failed issue
  net: hns3: reject unsupported coalescing params
  net: hns3: delete unnecessary logs after kzalloc fails
  net: hns3: synchronize some print relating to reset issue
  net: hns3: print out command code when dump fails in debugfs
  net: hns3: print out status register when VF receives unknown source interrupt
  net: hns3: add a check before PF inform VF to reset
  net: hns3: delete some reduandant code
  net: hns3: remove an unnecessary resetting check in 
hclge_handle_hw_ras_error()
  net: hns3: rename macro HCLGE_MAX_NCL_CONFIG_LENGTH
  net: hns3: fix some mixed type assignment
  net: hns3: fix a not link up issue when fibre port supports autoneg
  net: hns3: add missing help info for QS shaper in debugfs
  net: hns3: add support for dump MAC ID and loopback status in debugfs
  net: hns3: add enabled TC numbers and DWRR weight info in debugfs
  net: hns3: modify an unsuitable print when setting unknown duplex to fibre

  [Status]
  (In progress) net: hns3: clear port base VLAN when unload PF
  (In progress) net: hns3: fix RMW issue for VLAN filter switch
  (In progress) net: hns3: fix VF VLAN table entries inconsistent issue
  (In progress) net: hns3: fix "tc qdisc del" failed issue
  (Fix committed) net: hns3: fix a not link up issue when fibre port supports 
autoneg

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

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

[Kernel-packages] [Bug 1855303] Re: Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5

[Vignesh Gunasekaran]

Hi Jeff,

I went back to check if those patches in comment #5 are pulled from the
MKP tree into the Mainline tree and I noticed that those are landed now.

The SHA IDs of those commits in the Mainline kernel are as follows,

df3fe76658ed scsi: lpfc: add RDF registration and Link Integrity FPIN logging
73ec6d2748dc scsi: fc: Update Descriptor definition and add RDF and Link 
Integrity FPINs
145e5a8a5cbd scsi: lpfc: Copyright updates for 12.6.0.4 patches
ad6203f97526 scsi: lpfc: Update lpfc version to 12.6.0.4
f6770e7d2329 scsi: lpfc: Clean up hba max_lun_queue_depth checks
6cde2e3e2813 scsi: lpfc: Remove handler for obsolete ELS - Read Port Status 
(RPS)
4cb9e1ddaa14 scsi: lpfc: Fix coverity errors in fmdi attribute handling
a99c80742af4 scsi: lpfc: Fix compiler warning on frame size
821bc882acca scsi: lpfc: Fix release of hwq to clear the eq relationship
792f3b90be2a scsi: lpfc: Fix registration of ELS type support in fdmi
835214f5d5f5 scsi: lpfc: Fix broken Credit Recovery after driver load
0ab384a49c54 scsi: lpfc: Fix lpfc_io_buf resource leak in lpfc_get_scsi_buf_s4 
error path

Could you pass on this info to your kernel team? So that all lpfc
patches can be accepted.

Thanks
Vignesh

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

Title:
  Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5

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

Bug description:
  [IMPACT]

  This is related to bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856340

  This is a significant number of updates by Broadcom to the lpfc driver
  that didn't make 5.4 in time.  As 20.04 is an LTS release with
  expected hardware support for 5 years, we need to ensure as much
  hardware support lands as possible to support server vendors over the
  next couple years.

  Broadcom has updated the lpfc driver to version 12.6.0.4 in 5.5.  The
  version in focal is 12.2.0.3 and missing several bug fixes and
  hardware support additions.

  Please update the driver in focal appropriately.

  [FIXES]
  eede4970fb6c29f2056d7d016a3764c90e9d8a65 scsi: lpfc: size cpu map by
  last cpu id set
  4583a4f66b323c6e4d774be2649e83a4e7c7b78c scsi: lpfc: use hdwq assigned
  cpu for allocation
  3b294c0fb910dc91250abab574e85c9c1957c795 scsi: lpfc: Update lpfc version
  to 12.6.0.2
  542ddc9b346984cb5bbc2a923d3f3f27ae961ffa scsi: lpfc: revise nvme max
  queues to be hdwq count
  bc227dde0d8b687aa525d01b0df5556d4d37eca3 scsi: lpfc: Initialize cpu_map
  for not present cpus
  d480e57809a04a3b9e755c0bdd43e10a9f12 scsi: lpfc: fix inlining of
  lpfc_sli4_cleanup_poll_list()
  6c6d59e0fe5b86cf273d6d744a6a9768c4ecc756 scsi: lpfc: fix: Coverity:
  lpfc_cmpl_els_rsp(): Null pointer dereferences
  6f23f8c5c9f1be4eb17c035129c80e49000c18a7 scsi: lpfc: fix: Coverity:
  lpfc_get_scsi_buf_s3(): Null pointer dereferences
  61951a6d3153b4482404b739be921a7459f8dc12 scsi: lpfc: Fix
  lpfc_cpumask_of_node_init()
  eea2d396aa57acb3607f79ef04c08c2c5166f3fa scsi: lpfc: Fix a kernel
  warning triggered by lpfc_sli4_enable_intr()
  765ab6cdac3b681952da0e22184bf6cf1ae41cf8 scsi: lpfc: Fix a kernel
  warning triggered by lpfc_get_sgl_per_hdwq()
  aff6ab9e7221c1b5d15418419b9797e5badd4aec scsi: lpfc: Update lpfc version
  to 12.6.0.1
  171f6c41949f6e9d5e09dcac842a10bf8dda8dcc scsi: lpfc: Add enablement of
  multiple adapter dumps
  dcaa213679387e95a315dca05c57dbb15273703c scsi: lpfc: Change default IRQ
  model on AMD architectures
  93a4d6f40198dffcca35d9a928c409f9290f1fe0 scsi: lpfc: Add registration
  for CPU Offline/Online events
  b9da814cd5f5bb93041a6e4dbc9c5149713186ff scsi: lpfc: Clarify FAWNN error
  message
  69641627c653464db46f3e3d8c438349be055670 scsi: lpfc: Sync with FC-NVMe-2
  SLER change to require Conf with SLER
  dda5bdf074da3782ff9e785ee50cd2a3f214d498 scsi: lpfc: Fix dynamic fw log
  enablement check
  2332e6e475b016e2026763f51333f84e2e6c57a3 scsi: lpfc: Fix unexpected
  error messages during RSCN handling
  6c1e803eac846f886cd35131e6516fc51a8414b9 scsi: lpfc: Fix kernel crash at
  lpfc_nvme_info_show during remote port bounce
  6bfb1620829825c01e1dcdd63b6a7700352babd9 scsi: lpfc: Fix configuration
  of BB credit recovery in service parameters
  7cfd5639d99bec0d27af089d0c8c114330e43a72 scsi: lpfc: Fix duplicate
  unreg_rpi error in port offline flow
  7b10db555257d1248398643a23e10cf36b50d516 scsi: lpfc: Make
  lpfc_debugfs_ras_log_data static
  c3e5aac3e2f501ad4fcb03fed0e32a6f009faea2 scsi: lpfc: Fix NULL check
  before mempool_destroy is not needed
  5792a0e81678da41f05bb724ebd20f134604fa15 scsi: lpfc: fix spelling error
  in MAGIC_NUMER_xxx
  9e2edb41c3d4cab6da0eedcc07ae04758af62ab8 scsi: lpfc: fix build error of
  lpfc_debugfs.c for vfree/vmalloc
  5314995e370e46ac12d12378544ad4575b6f6672 scsi: lpfc: lpfc_nvmet: Fix Use
  plain integer as NULL pointer
  

[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

[Seth Arnold]

Stefan, while recent kernels seem happier than previous kernels (I think
-14 era was terrible), I don't think this problem is fixed yet:

sarnold@millbarge:/tmp$ uname -a
Linux millbarge 5.4.0-21-generic #25-Ubuntu SMP Sat Mar 28 13:10:28 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
sarnold@millbarge:/tmp$ uptime
 17:18:02 up 14:59,  8 users,  load average: 0.36, 0.27, 0.16
sarnold@millbarge:/tmp$ time journalctl > foo

real0m47.135s
user0m36.886s
sys 0m10.180s
sarnold@millbarge:/tmp$ ls -lh /tmp/foo
-rw-rw-r-- 1 sarnold sarnold 841M Apr  3 17:15 /tmp/foo
sarnold@millbarge:/tmp$ wc -l /tmp/foo
4045530 /tmp/foo


During that journalctl run, my mouse could not move for twenty seconds. I left 
an iovisor tool running to log high-latency __alloc_pages_nodemask() calls 
(identified by Sultan as a likely cause):

# funcslower-bpfcc __alloc_pages_nodemask
Tracing function calls slower than 1 ms... Ctrl+C to quit.
COMM   PIDLAT(ms) RVAL FUNC
dp_sync_taskq  716   7.72 f2d109115040 __alloc_pages_nodemask 
systemd-udevd  44671 1.59 f2d10575b800 __alloc_pages_nodemask 
git46218 4.27 f2d10500edc0 __alloc_pages_nodemask 
z_wr_iss   683   4.90 f2d101b4cf40 __alloc_pages_nodemask 
systemd-udevd  51359 4.27 f2d10ec12800 __alloc_pages_nodemask 
systemd-udevd  56585 2.48 f2d10d3b0500 __alloc_pages_nodemask 
systemd-udevd  56577 2.55 f2d106f73380 __alloc_pages_nodemask 
systemd-udevd  72552 2.09 f2d105249680 __alloc_pages_nodemask 
systemd-udevd  76964 1.53 f2d1017fd440 __alloc_pages_nodemask 
systemd-udevd  80900 3.94 f2d102675200 __alloc_pages_nodemask 
systemd-udevd  88669 2.09 f2d1015fb5c0 __alloc_pages_nodemask 
kthreadd   2 4.41 f2d10d6f96c0 __alloc_pages_nodemask 
kthreadd   2 4.65 f2d10d38c3c0 __alloc_pages_nodemask 
kthreadd   2 3.97 f2d10d3cc780 __alloc_pages_nodemask 
updatedb.mloca 1061942.44 f2d10e1c2680 __alloc_pages_nodemask 
kthreadd   2 1.20 f2d10d36ff40 __alloc_pages_nodemask 
kthreadd   2 4.13 f2d10d495940 __alloc_pages_nodemask 
kthreadd   2 6.34 f2d10d317180 __alloc_pages_nodemask 
kthreadd   2 4.76 f2d110e85000 __alloc_pages_nodemask 
systemd-udevd  1138221.51 f2d10f5c8e00 __alloc_pages_nodemask 
systemd-udevd  1138201.91 f2d10e611800 __alloc_pages_nodemask 
systemd-udevd  1220173.13 f2d10e539700 __alloc_pages_nodemask 
systemd-udevd  1411022.43 f2d104487200 __alloc_pages_nodemask 
systemd-udevd  1445654.82 f2d106b84040 __alloc_pages_nodemask 
systemd-udevd  1156  1.28 f2d102325c00 __alloc_pages_nodemask 
systemd-udevd  1524863.07 f2d101516500 __alloc_pages_nodemask 
systemd-udevd  1524854.94 f2d1015cbbc0 __alloc_pages_nodemask 
systemd-udevd  1728071.33 f2d1015f4700 __alloc_pages_nodemask 
systemd-udevd  1855034.46 f2d10d321240 __alloc_pages_nodemask 
systemd-udevd  1892445.12 f2d10e7f0b00 __alloc_pages_nodemask 
systemd-udevd  2059735.36 f2d10d4171c0 __alloc_pages_nodemask 
systemd-udevd  2101335.19 f2d10ffac340 __alloc_pages_nodemask 
systemd-udevd  2096212.95 f2d10d377fc0 __alloc_pages_nodemask 
systemd-udevd  2187682.24 f2d10526e500 __alloc_pages_nodemask 
systemd-udevd  2342611.42 f2d101814680 __alloc_pages_nodemask 
systemd-udevd  2354683.82 f2d10d2afa40 __alloc_pages_nodemask 
systemd-udevd  2368264.94 f2d10d0f8440 __alloc_pages_nodemask 
systemd-udevd  2471151.13 f2d1023ee180 __alloc_pages_nodemask 
systemd-udevd  2475731.46 f2d1015a4040 __alloc_pages_nodemask 
systemd-udevd  2712885.38 f2d10d1b3800 __alloc_pages_nodemask 
dav1d-tile 2834602.05 f2d10cdb0b80 __alloc_pages_nodemask 
dav1d-tile 2834602.80 f2d10cdb8840 __alloc_pages_nodemask 
dav1d-tile 2834602.83 f2d10cdb9200 __alloc_pages_nodemask 
RemVidParent   2834602.82 f2d10cdba200 __alloc_pages_nodemask 
dav1d-tile 2834604.11 f2d10cdbcf00 __alloc_pages_nodemask 
journalctl 2862701.71 f2d10e2668c0 __alloc_pages_nodemask 
journalctl 2862701.09 f2d10ccfac00 __alloc_pages_nodemask 
journalctl 2862701.11 f2d10cce3200 __alloc_pages_nodemask 
journalctl 2862702.96 f2d10cce7380 __alloc_pages_nodemask 
x-terminal-emu 24851 1.14 f2d1086a2a00 __alloc_pages_nodemask 
journalctl 2862701.44 f2d10ccc41c0 __alloc_pages_nodemask 
kthreadd   2 1.25 f2d110c71000 __alloc_pages_nodemask 
journalctl 2862701.05 f2d10ccb1200 __alloc_pages_nodemask 
journalctl 2862701.65 f2d10ccbd700 __alloc_pages_nodemask 
journalctl 2862703.08 f2d102229000 __alloc_pages_nodemask 
journalctl 2862701.88 f2d10cbfd0c0 __alloc_pages_nodemask 
journalctl 2862701.54 

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

[Ayyappan]

Follow-up on my previous post - Unpacking failed, Decoding failed is
back on second boot. Please do not waste your time trying the above.
Sorry.

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

Title:
  initramfs unpacking failed

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

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

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

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

[Ayyappan]

Edit initramfs.conf as su.

Rem out COMPRESS-lz4 line

Run update-initramfs -u - System will return with "COMPRESS parameter
not set".

Now edit initramfs.conf again. Remove the # on COMPRESS=lz4, run again
update-initramfs -u.

It will close without any error. Reboot.

I just did and no more failed message.


** Attachment added: "initramfs-unpacking-decoding-failed.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835660/+attachment/5345715/+files/initramfs-unpacking-decoding-failed.png

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

Title:
  initramfs unpacking failed

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

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

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

[Kernel-packages] [Bug 1862760] Re: Unreliable 802.11ac connection on our raspi images

[Seth Forshee]

Generally speaking we don't know what country a device is operating in,
so we default to the world domain which should be safe throughout the
world. The AP may send a hint to the client as to what regulatory domain
to use, but many APs do not do this.

Also note that on many desktop systems now the regulatory domain is
managed by the wireless card firmware, which is why you may see the
domain set there even if the AP does not send a hint.

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

Title:
  Unreliable 802.11ac connection on our raspi images

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware-raspi2 package in Ubuntu:
  Triaged
Status in linux-raspi2-5.3 package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  New
Status in linux-firmware-raspi2 source package in Bionic:
  New
Status in linux-raspi2-5.3 source package in Bionic:
  New
Status in linux-firmware source package in Eoan:
  New
Status in linux-firmware-raspi2 source package in Eoan:
  New
Status in linux-raspi2-5.3 source package in Eoan:
  New
Status in linux-firmware source package in Focal:
  New
Status in linux-firmware-raspi2 source package in Focal:
  Triaged
Status in linux-raspi2-5.3 source package in Focal:
  New

Bug description:
  We were not able to completely pin-point the issue yet, so this is
  more of a blanket bug for the current issues we are seeing. We don't
  know where exactly the issue can be located.

  While preparing and testing 18.04.4, certification reported issues
  with our uc18 images on the pi4 with wifi ac tests. One of our
  engineers (Brian) confirmed it locally with a wifi access point
  restricted only to 802.11ac. After some additional testing, he noticed
  that he had the same unreliable symptoms for both the classic and core
  images, as well as the 19.10.1 classic images. The symptoms seem to
  vary, from inability to detect 802.11ac APs, inability to connect
  and/or receive an IP address and no traffic getting through.

  We will provide all the information that we have. Raspbian works
  better in this regard. We have pulled in the wifi firmware bits from
  Raspbian and using those, and that seems to resolve all flakiness.

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

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

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

[bugproxy]

--- Comment From mranw...@us.ibm.com 2020-04-03 12:45 EDT---
We've been working with Mimi and I think that what we need now aren't config 
option changes, but this patch:

diff --git a/arch/powerpc/kernel/ima_arch.c b/arch/powerpc/kernel/ima_arch.c
index e341162..c1ea55d 100644
--- a/arch/powerpc/kernel/ima_arch.c
+++ b/arch/powerpc/kernel/ima_arch.c
@@ -50,7 +50,7 @@ bool arch_ima_get_secureboot(void)
"measure func=KEXEC_KERNEL_CHECK template=ima-modsig",
"measure func=MODULE_CHECK template=ima-modsig",
"appraise func=KEXEC_KERNEL_CHECK appraise_flag=check_blacklist 
appraise_type=imasig|modsig",
-#ifndef CONFIG_MODULE_SIG_FORCE
+#ifndef CONFIG_MODULE_SIG
"appraise func=MODULE_CHECK appraise_flag=check_blacklist 
appraise_type=imasig|modsig",
#endif
NULL

We're going to test that, but it's similar to commit 8db5da0b8618 on the
x86 side.

It looks like the MODULE_SIG_FORCE/IMA_ARCH_POLICY change is the wrong
path right now.  But testing that, too. ;)

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

Title:
  Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - George C. Wilson  - 2020-02-25 18:40:44 
==
  - sysfs enablement: TBD
  - ima: arch specific policy support 6191706246de
  - platform keyring changes for powerpc: TBD
  - Appended signatures support for IMA appraisal 
39b07096364a42c516415d5f841069e885234e61
  - integrity: Define a trusted platform keyring: 9dc92c45177a
  - ima: Support platform keyring for kernel appraisal: d7cecb676dd3
  - TPM 2.0 Multibank extend support: c1f92b4b04ad
  - TPM 2.0 Eventlog support: 4d23cc323cdb
  - ima: carry the measurement list across kexec: d68a6fe9fccf
  - kexec_file_load system call support: 500c7ab1a9db

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

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

[Kernel-packages] [Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache

[Mauricio Faria de Oliveira]

Hi Sebastian,

Sure, that's certainly understandable.
For starters, the topology of the block/bcache devices would do it:

(set -x; lsblk; sudo dmsetup table; grep -r ^ /sys/block/bcache*/bcache)
> lp1867916.1.out 2>&1

Then please upload the output file (or copy/paste, if file access is
though.)

Thanks,
Mauricio

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

Title:
  Regression in kernel 4.15.0-91 causes kernel panic with Bcache

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems
  does not boot any longer. It always crashes during boot with a kernel
  panic.

  I suspect that this crash might be related to Bcache because this is
  the only one of our systems where we use Bcache and the kernel panic
  appears right after Bcache initialization.

  I already checked that this bug still exists in the 4.15.0-92.93
  kernel from proposed.

  Unfortunately, I cannot do a bisect because this is a critical
  production system and we do not have any other system with a similar
  configuration.

  I attached a screenshot with the trace of the kernel panic.

  The last message that appears before the kernel panic (or rather the
  last one that I can see - there is a rather long pause between that
  message and the panic and I cannot scroll up far enough to ensure that
  there are no other messages in between) is:

  bcache: register_bcache() error /dev/dm-0: device already registered

  When booting with kernel 4.15.0-88 that does not have this problem,
  the next message is

  bcache: register_bcache() error /dev/dm-12: device already registered
  (emitting change event)

  After that the next message is:

  Begin: Loading essential drivers ... done

  This message also appears after the kernel panic, but the boot process
  stalls and the system can only be recovered by doing a hardware reset.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-88-generic 4.15.0-88.88
  ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
  Uname: Linux 4.15.0-88-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 17 21:08 seq
   crw-rw 1 root audio 116, 33 Mar 17 21:08 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Mar 18 12:55:18 2020
  HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a
  InstallationDate: Installed on 2013-07-02 (2450 days ago)
  InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release 
amd64 (20130214)
  MachineType: HP ProLiant DL160 G6
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic 
root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-88-generic N/A
   linux-backports-modules-4.15.0-88-generic  N/A
   linux-firmware 1.173.16
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago)
  dmi.bios.date: 11/06/2009
  dmi.bios.vendor: HP
  dmi.bios.version: O33
  dmi.chassis.asset.tag: 0191525
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL160 G6
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1870571] Re: Focal update: v5.4.30 upstream stable release

[Kamal Mostafa]

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

Title:
  Focal update: v5.4.30 upstream stable release

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

Bug description:
  SRU Justification

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

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

  mac80211: Check port authorization in the ieee80211_tx_dequeue() case
  mac80211: fix authentication with iwlwifi/mvm
  serial: sprd: Fix a dereference warning
  vt: selection, introduce vc_is_sel
  vt: ioctl, switch VT_IS_IN_USE and VT_BUSY to inlines
  vt: switch vt_dont_switch to bool
  vt: vt_ioctl: remove unnecessary console allocation checks
  vt: vt_ioctl: fix VT_DISALLOCATE freeing in-use virtual console
  vt: vt_ioctl: fix use-after-free in vt_in_use()
  platform/x86: pmc_atom: Add Lex 2I385SW to critclk_systems DMI table
  bpf: Explicitly memset the bpf_attr structure
  bpf: Explicitly memset some bpf info structures declared on the stack
  gpiolib: acpi: Add quirk to ignore EC wakeups on HP x2 10 CHT + AXP288 model
  net: ks8851-ml: Fix IO operations, again
  clk: imx: Align imx sc clock msg structs to 4
  clk: imx: Align imx sc clock parent msg structs to 4
  clk: ti: am43xx: Fix clock parent for RTC clock
  libceph: fix alloc_msg_with_page_vector() memory leaks
  arm64: alternative: fix build with clang integrated assembler
  perf map: Fix off by one in strncpy() size argument
  ARM: dts: oxnas: Fix clear-mask property
  ARM: bcm2835-rpi-zero-w: Add missing pinctrl name
  ARM: dts: imx6: phycore-som: fix arm and soc minimum voltage
  ARM: dts: N900: fix onenand timings
  ARM: dts: sun8i: r40: Move AHCI device node based on address order
  arm64: dts: ls1043a-rdb: correct RGMII delay mode to rgmii-id
  arm64: dts: ls1046ardb: set RGMII interfaces to RGMII_ID mode
  Linux 5.4.30
  UBUNTU: upstream stable to v5.4.30

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

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

[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

[Bug Watch Updater]

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

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1690085]

[dl9px]

I as the thread starter fully agree with Borislav and set this bug
report to status resolved. Thank you all very much for the interesting
discussion!

Having started with massive stability problems on my new Ryzen build, I
reported this issue to address a potential problem in the Linux kernel.
In the hundreds of comments, which surely could be very interesting for
everybody affected, I found a workaround - disabling C6 states with the
python script attached to a comment above. Since then the system was
perfectly stable. Test with the "kill Ryzen" script also showed me, the
CPU was not affected by the other huge problem early adopters had.

A few days ago I finally found the time to update the AB350 BIOS to the
latest version and set the "typical idle current" in the options. I had
only 2 issues since then: The bootloader entry for my OS was broken
after the update and network manager did not bring up the LAN interface
anymore. But after resolving these issues: No more stability problems.
Of course I deactivated my systemd service for c6 states. I am still on
the stable branch of Manjaro and use the latest 5.5 series kernel.

See you!

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related 

[Kernel-packages] [Bug 1870395] Re: Ubuntu Studio 20.04 ZFS Option Fails to Boot

[David R. Bergstein]

I tried the current Ubuntu Studio ISO, dated 4/3/2020, and this ZFS boot
issue is still there.  Are there any post-install commands that can be
run to fix it or do I need to wait for a subsequent spin of the ISO
file?

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

Title:
  Ubuntu Studio 20.04 ZFS Option Fails to Boot

Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  As part of installation, I selected the experimental ZFS option.
  Ubuntu Studio then installed without errors, however upon booting the
  new system there was a zpool import failure and I was prompted at the
  initrd to manually import the zfs datasets.

  The workaround at initrd was to enter the following commands:

  zpool import -R /root -N rpool
  zpool import -R /root -N bpool
  zfs mount -a
  exit

  The system then booted up normally, however the workaround above has
  to be used for each subsequent boot.

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

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

[Kernel-packages] [Bug 1866909] Re: Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

[Seth Forshee]

Oh but PPC_SECURE_BOOT depends on IMA_ARCH_POLICY. For now I'm going to
make it depend on that or LOCK_DOWN_IN_SECURE_BOOT to get the test build
going. I think this makes sense because lockdown enforces signatures for
module loading and kexec (plus a number of other restrictions), which I
think is all the IMA arch policy is enforcing.

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

Title:
  Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - George C. Wilson  - 2020-02-25 18:40:44 
==
  - sysfs enablement: TBD
  - ima: arch specific policy support 6191706246de
  - platform keyring changes for powerpc: TBD
  - Appended signatures support for IMA appraisal 
39b07096364a42c516415d5f841069e885234e61
  - integrity: Define a trusted platform keyring: 9dc92c45177a
  - ima: Support platform keyring for kernel appraisal: d7cecb676dd3
  - TPM 2.0 Multibank extend support: c1f92b4b04ad
  - TPM 2.0 Eventlog support: 4d23cc323cdb
  - ima: carry the measurement list across kexec: d68a6fe9fccf
  - kexec_file_load system call support: 500c7ab1a9db

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

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

[Kernel-packages] [Bug 1870571] [NEW] Focal update: v5.4.30 upstream stable release

[Kamal Mostafa]

Public bug reported:

SRU Justification

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

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

mac80211: Check port authorization in the ieee80211_tx_dequeue() case
mac80211: fix authentication with iwlwifi/mvm
serial: sprd: Fix a dereference warning
vt: selection, introduce vc_is_sel
vt: ioctl, switch VT_IS_IN_USE and VT_BUSY to inlines
vt: switch vt_dont_switch to bool
vt: vt_ioctl: remove unnecessary console allocation checks
vt: vt_ioctl: fix VT_DISALLOCATE freeing in-use virtual console
vt: vt_ioctl: fix use-after-free in vt_in_use()
platform/x86: pmc_atom: Add Lex 2I385SW to critclk_systems DMI table
bpf: Explicitly memset the bpf_attr structure
bpf: Explicitly memset some bpf info structures declared on the stack
gpiolib: acpi: Add quirk to ignore EC wakeups on HP x2 10 CHT + AXP288 model
net: ks8851-ml: Fix IO operations, again
clk: imx: Align imx sc clock msg structs to 4
clk: imx: Align imx sc clock parent msg structs to 4
clk: ti: am43xx: Fix clock parent for RTC clock
libceph: fix alloc_msg_with_page_vector() memory leaks
arm64: alternative: fix build with clang integrated assembler
perf map: Fix off by one in strncpy() size argument
ARM: dts: oxnas: Fix clear-mask property
ARM: bcm2835-rpi-zero-w: Add missing pinctrl name
ARM: dts: imx6: phycore-som: fix arm and soc minimum voltage
ARM: dts: N900: fix onenand timings
ARM: dts: sun8i: r40: Move AHCI device node based on address order
arm64: dts: ls1043a-rdb: correct RGMII delay mode to rgmii-id
arm64: dts: ls1046ardb: set RGMII interfaces to RGMII_ID mode
Linux 5.4.30
UBUNTU: upstream stable to v5.4.30

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress

** Affects: linux (Ubuntu Focal)
 Importance: Undecided
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

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

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

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

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

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.4.30 upstream stable release
+    from git://git.kernel.org/
  
-v5.4.30 upstream stable release
-from git://git.kernel.org/
+ mac80211: Check port authorization in the ieee80211_tx_dequeue() case
+ mac80211: fix authentication with iwlwifi/mvm
+ serial: sprd: Fix a dereference warning
+ vt: selection, introduce vc_is_sel
+ vt: ioctl, switch VT_IS_IN_USE and VT_BUSY to inlines
+ vt: switch vt_dont_switch to bool
+ vt: vt_ioctl: remove unnecessary console allocation checks
+ vt: vt_ioctl: fix VT_DISALLOCATE freeing in-use virtual console
+ vt: vt_ioctl: fix use-after-free in vt_in_use()
+ platform/x86: pmc_atom: Add Lex 2I385SW to critclk_systems DMI table
+ bpf: Explicitly memset the bpf_attr structure
+ bpf: Explicitly memset some bpf info structures declared on the stack
+ gpiolib: acpi: Add quirk to ignore EC wakeups on HP x2 10 CHT + AXP288 model
+ net: ks8851-ml: Fix IO operations, again
+ clk: imx: Align imx sc clock msg structs to 4
+ clk: imx: Align imx sc clock parent msg structs to 4
+ clk: ti: am43xx: Fix clock parent for RTC clock
+ libceph: fix alloc_msg_with_page_vector() memory leaks
+ arm64: alternative: fix build with clang integrated assembler
+ perf map: Fix off by one in strncpy() size argument
+ ARM: dts: oxnas: Fix clear-mask property
+ ARM: 

[Kernel-packages] [Bug 1866909] Re: Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

[Seth Forshee]

Um, off rather.

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

Title:
  Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - George C. Wilson  - 2020-02-25 18:40:44 
==
  - sysfs enablement: TBD
  - ima: arch specific policy support 6191706246de
  - platform keyring changes for powerpc: TBD
  - Appended signatures support for IMA appraisal 
39b07096364a42c516415d5f841069e885234e61
  - integrity: Define a trusted platform keyring: 9dc92c45177a
  - ima: Support platform keyring for kernel appraisal: d7cecb676dd3
  - TPM 2.0 Multibank extend support: c1f92b4b04ad
  - TPM 2.0 Eventlog support: 4d23cc323cdb
  - ima: carry the measurement list across kexec: d68a6fe9fccf
  - kexec_file_load system call support: 500c7ab1a9db

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

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

[Kernel-packages] [Bug 1866909] Re: Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

[Seth Forshee]

I'll get a test kernel uploaded with IMA_ARCH_POLICY up, will let you
know when it's ready for testing.

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

Title:
  Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - George C. Wilson  - 2020-02-25 18:40:44 
==
  - sysfs enablement: TBD
  - ima: arch specific policy support 6191706246de
  - platform keyring changes for powerpc: TBD
  - Appended signatures support for IMA appraisal 
39b07096364a42c516415d5f841069e885234e61
  - integrity: Define a trusted platform keyring: 9dc92c45177a
  - ima: Support platform keyring for kernel appraisal: d7cecb676dd3
  - TPM 2.0 Multibank extend support: c1f92b4b04ad
  - TPM 2.0 Eventlog support: 4d23cc323cdb
  - ima: carry the measurement list across kexec: d68a6fe9fccf
  - kexec_file_load system call support: 500c7ab1a9db

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

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

[Kernel-packages] [Bug 1866882] Re: segfault in libllvm-10 when building kernel bpf selftests on s390

[Matthias Klose]

sorry, this needs testing

** Changed in: llvm-toolchain-10 (Ubuntu)
   Status: Fix Released => 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/1866882

Title:
  segfault in libllvm-10 when building kernel bpf selftests on s390

Status in linux package in Ubuntu:
  Incomplete
Status in llvm-toolchain-10 package in Ubuntu:
  Incomplete

Bug description:
  Seeing this in autopkgtest for the 5.4.0-18 kernel. Only happens on
  s390, other architectures are fine.

    Stack dump:
    0.  Program arguments: llc -march=bpf -mcpu=probe -filetype=obj -o 
/tmp/autopkgtest.92AlD3/build.vya/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/btf__core_reloc_nesting___err_array_container.o
    #0 0x03ff830ab14a (/lib/s390x-linux-gnu/libLLVM-10.so.1+0x9ab14a)
    Segmentation fault (core dumped)

  Full log:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/s390x/l/linux/20200310_180956_146bd@/log.gz

  This did not happen for the 5.4.0-17 upload with llvm-9, with no
  changes to the bpf program being compiled when the segfault happens
  between the -17 and -18 uploads.

  To reproduce, clone the focal kernel tree and build the bpf selftests.

  $ git clone --single-branch --depth=1 -b master-next 
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal
  $ make -C focal/tools/testing/selftests TARGETS=bpf

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

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

[Kernel-packages] [Bug 1868165] Re: [X1 Carbon 7th ed] 5.3.0-42 loses internal audio; regression from 5.3.0-40

[Pete Gamache]

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

This issue is still broken with -43 and -45 kernels.

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

Title:
  [X1 Carbon 7th ed] 5.3.0-42 loses internal audio; regression from
  5.3.0-40

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo ThinkPad X1 Carbon 7th edition laptop running Ubuntu
  19.10 desktop. I recently applied a software update that contained a
  new kernel, 5.3.0-42, and upon restarting, the internal audio
  interface was not found; internal speakers and the headphone output
  were unusable.

  Upon rebooting with the previous kernel, 5.3.0-40, the problem went
  away again. Subsequent testing confirms this is repeatable.

  Some relevant lines from `dmesg` follow.

  On kernel 5.3.0-40 (working):

  [4.386007] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.391825] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
  [4.392016] thermal thermal_zone5: failed to read out thermal zone (-61)
  [4.430083] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC285: 
line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker
  [4.430085] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [4.430087] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [4.430087] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [4.430088] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [4.430089] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x19

  
  On kernel 5.3.0-42 (broken):

  [3.076809] i915 :00:02.0: fb0: i915drmfb frame buffer device
  [3.088029] snd_soc_skl :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.173463] snd_soc_skl :00:1f.3: Direct firmware load for 
9dc8-LENOVO-TP-N2H-4752-tplg.bin failed with error -2
  [3.173465] snd_soc_skl :00:1f.3: tplg fw 
9dc8-LENOVO-TP-N2H-4752-tplg.bin load failed with -2, falling back to 
dfw_sst.bin
  [3.173480] snd_soc_skl :00:1f.3: Direct firmware load for dfw_sst.bin 
failed with error -2
  [3.173481] snd_soc_skl :00:1f.3: Fallback tplg fw dfw_sst.bin load 
failed with -2
  [3.173484] snd_soc_skl :00:1f.3: Failed to init topology!
  [3.173486] snd_soc_skl :00:1f.3: ASoC: failed to probe component -2
  [3.173496] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: failed to 
instantiate card -2
  [3.173508] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with 
error -2

  
  I've attached `lspci -vnvn` and `dmesg` output for both the -40 and -42 
kernels.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-40-generic 5.3.0-40.32
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gamache1768 F pulseaudio
   /dev/snd/controlC1:  gamache1768 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 19 15:08:14 2020
  InstallationDate: Installed on 2019-11-21 (119 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QD0007US
  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-40-generic 
root=UUID=90290cff-6557-4384-b8a9-1b83f860ea01 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.183.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET46W (1.29 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD0007US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET46W(1.29):bd02/21/2020:svnLENOVO:pn20QD0007US:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD0007US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD0007US
  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/1868165/+subscriptions

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

[Kernel-packages] [Bug 1845678] Re: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work

[Jean-]

Damn sorry about that, I didn't notice the kernel moved from .43 to .45.
I'll try with 46

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

Title:
  Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't
  work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The built-in microphone in my Lenovo ThinkPad X1 Carbon 7th Generation
  doesn't work.

  A microphone on a headset plugged into the 3.5mm jack works fine.

  This is probably relevant:
  https://bugzilla.kernel.org/show_bug.cgi?id=201251

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-12-generic 5.3.0-12.13
  ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
  Uname: Linux 5.3.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jik3746 F pulseaudio
   /dev/snd/pcmC0D0p:   jik3746 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 11:13:25 2019
  InstallationDate: Installed on 2019-09-12 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QD001VUS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-12-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-12-generic N/A
   linux-backports-modules-5.3.0-12-generic  N/A
   linux-firmware1.182
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (7 days ago)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QD001VUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QD001VUS
  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/1845678/+subscriptions

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Kernel NULL pointer dereference while receiving zfs snapshots

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I was transferring my zfs snapshots to the backup server, when
  suddenly it stalled. I checked dmesg on the server and found a "kernel
  bug" entry.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-21-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Fri Apr  3 14:48:19 2020
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=7934268a-8e6f-11e8-828e-00133b1029de ro mitigations=off maybe-ubiquity
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-01-19 (75 days ago)
  dmi.bios.date: 12/23/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0214
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5LD2-X/1333
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: Rev 1.xx
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0214:bd12/23/2008:svnSystemmanufacturer:pnSystemProductName:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5LD2-X/1333:rvrRevx.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: Rev 1.xx
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1870559] [NEW] Kernel NULL pointer dereference while receiving zfs snapshots

[Andreas Hasenack]

Public bug reported:

I was transferring my zfs snapshots to the backup server, when suddenly
it stalled. I checked dmesg on the server and found a "kernel bug"
entry.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-21-generic 5.4.0-21.25
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-21-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Date: Fri Apr  3 14:48:19 2020
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: System manufacturer System Product Name
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=7934268a-8e6f-11e8-828e-00133b1029de ro mitigations=off maybe-ubiquity
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-21-generic N/A
 linux-backports-modules-5.4.0-21-generic  N/A
 linux-firmware1.187
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-01-19 (75 days ago)
dmi.bios.date: 12/23/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0214
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5LD2-X/1333
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev x.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: Rev 1.xx
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0214:bd12/23/2008:svnSystemmanufacturer:pnSystemProductName:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5LD2-X/1333:rvrRevx.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: Rev 1.xx
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug champagne focal

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

Title:
  Kernel NULL pointer dereference while receiving zfs snapshots

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I was transferring my zfs snapshots to the backup server, when
  suddenly it stalled. I checked dmesg on the server and found a "kernel
  bug" entry.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-21-generic 5.4.0-21.25
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-21-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Fri Apr  3 14:48:19 2020
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=7934268a-8e6f-11e8-828e-00133b1029de ro mitigations=off maybe-ubiquity
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-01-19 (75 days ago)
  dmi.bios.date: 12/23/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0214
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5LD2-X/1333
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  

[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Rajat Pandita]

Fresh install with proprietary driver’s installation check box ticked
worked fine till I rebooted again and then I could not get into the
desktop. All drivers installed fine but one reboot later things were
back to being unable to login. So I did a chroot and removed splash from
grub command line followed by update grub and I Am back in business

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:

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

[bugproxy]

--- Comment From mranw...@us.ibm.com 2020-04-03 10:30 EDT---
Sorry, we don't know if we want CONFIG_MODULE_SIG_FORCE set.  The modules 
aren't loading, and we weren't sure what needed to change.  We're happy to try 
a kernel with IMA_ARCH_POLICY if that fixed it on x86.

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

Title:
  Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - George C. Wilson  - 2020-02-25 18:40:44 
==
  - sysfs enablement: TBD
  - ima: arch specific policy support 6191706246de
  - platform keyring changes for powerpc: TBD
  - Appended signatures support for IMA appraisal 
39b07096364a42c516415d5f841069e885234e61
  - integrity: Define a trusted platform keyring: 9dc92c45177a
  - ima: Support platform keyring for kernel appraisal: d7cecb676dd3
  - TPM 2.0 Multibank extend support: c1f92b4b04ad
  - TPM 2.0 Eventlog support: 4d23cc323cdb
  - ima: carry the measurement list across kexec: d68a6fe9fccf
  - kexec_file_load system call support: 500c7ab1a9db

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

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

[Kernel-packages] [Bug 1867803] Re: ALSA: No soundcards found after updating kernel to 5.3.0.42.36

[Bartosz Nowotny]

Hi!

Sound still not working on -45, confirmed working on -40. Running Ubuntu
18.04.4 on Lenovo X1C 7th gen (just like
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868165).

cheers

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

Title:
  ALSA: No soundcards found after updating kernel to 5.3.0.42.36

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  There seems to be some changes in ALSA in 5.3.0.41 and it seems to
  have caused some regression on my HP Spectrre (details attached).

  ~$ alsactl init
  alsactl: init:1759: No soundcards found...

  I verified that 5.3.0.40 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-42-generic 5.3.0-42.34
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 18 01:11:42 2020
  InstallationDate: Installed on 2019-07-11 (249 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: HP HP Spectre x360 Convertible 13-ap0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=57fb6fa4-a696-476b-813a-635b91fbc299 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-42-generic N/A
   linux-backports-modules-5.3.0-42-generic  N/A
   linux-firmware1.183.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.28
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8514
  dmi.board.vendor: HP
  dmi.board.version: 09.48
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.28:bd04/22/2019:svnHP:pnHPSpectrex360Convertible13-ap0xxx:pvr:rvnHP:rn8514:rvr09.48:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ap0xxx
  dmi.product.sku: 5KX23PA#ABJ
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1870554] Re: ip-netns(8) unmounts /sys filesystem hierarchy within namespace

[Lucio Andrés Illanes Albornoz]

** Patch added: "iproute2-4.3.0+no-remount-sysfs.patch"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1870554/+attachment/5345648/+files/iproute2-4.3.0+no-remount-sysfs.patch

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

Title:
  ip-netns(8) unmounts /sys filesystem hierarchy within namespace

Status in iproute2 package in Ubuntu:
  New

Bug description:
  Filesystems ordinarily mounted beneath /sys, particularly /sys/fs/cgroup, are 
not mounted within network namespaces created by ip-netns(8), as 
lib/namespace.c:netns_switch() explicitly remounts /sys.
  The patch enclosed removes the offending calls to umount2(2) and mount(2), 
leaving the /sys hierarchy intact within network namespaces.

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

  $ apt-cache policy iproute2
  iproute2:
Installed: 4.15.0-2ubuntu1
Candidate: 4.15.0-2ubuntu1
Version table:
   *** 4.15.0-2ubuntu1 500
  500 http://fr2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Nota bene: this bug was reported in [1] (unresolved) and, on Arch
  Linux, [2].

  References:
  [1] https://answers.launchpad.net/ubuntu/+source/iproute2/+question/659146
  [2] https://bugs.archlinux.org/task/33328

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

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

[Kernel-packages] [Bug 1870554] [NEW] ip-netns(8) unmounts /sys filesystem hierarchy within namespace

[Lucio Andrés Illanes Albornoz]

Public bug reported:

Filesystems ordinarily mounted beneath /sys, particularly /sys/fs/cgroup, are 
not mounted within network namespaces created by ip-netns(8), as 
lib/namespace.c:netns_switch() explicitly remounts /sys.
The patch enclosed removes the offending calls to umount2(2) and mount(2), 
leaving the /sys hierarchy intact within network namespaces.

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

$ apt-cache policy iproute2
iproute2:
  Installed: 4.15.0-2ubuntu1
  Candidate: 4.15.0-2ubuntu1
  Version table:
 *** 4.15.0-2ubuntu1 500
500 http://fr2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

Nota bene: this bug was reported in [1] (unresolved) and, on Arch Linux,
[2].

References:
[1] https://answers.launchpad.net/ubuntu/+source/iproute2/+question/659146
[2] https://bugs.archlinux.org/task/33328

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

** Patch added: "iproute2-4.3.0+no-remount-sysfs.patch"
   
https://bugs.launchpad.net/bugs/1870554/+attachment/5345647/+files/iproute2-4.3.0+no-remount-sysfs.patch

** Patch removed: "iproute2-4.3.0+no-remount-sysfs.patch"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1870554/+attachment/5345647/+files/iproute2-4.3.0+no-remount-sysfs.patch

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

Title:
  ip-netns(8) unmounts /sys filesystem hierarchy within namespace

Status in iproute2 package in Ubuntu:
  New

Bug description:
  Filesystems ordinarily mounted beneath /sys, particularly /sys/fs/cgroup, are 
not mounted within network namespaces created by ip-netns(8), as 
lib/namespace.c:netns_switch() explicitly remounts /sys.
  The patch enclosed removes the offending calls to umount2(2) and mount(2), 
leaving the /sys hierarchy intact within network namespaces.

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

  $ apt-cache policy iproute2
  iproute2:
Installed: 4.15.0-2ubuntu1
Candidate: 4.15.0-2ubuntu1
Version table:
   *** 4.15.0-2ubuntu1 500
  500 http://fr2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Nota bene: this bug was reported in [1] (unresolved) and, on Arch
  Linux, [2].

  References:
  [1] https://answers.launchpad.net/ubuntu/+source/iproute2/+question/659146
  [2] https://bugs.archlinux.org/task/33328

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

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

[Kernel-packages] [Bug 1868388] Re: watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0]

[Mauricio Faria de Oliveira]

FWIW, bug 1870553 reported for apport, about the lack of the kernel
stack traces.

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

Title:
  watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0]

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Got this after resuming from suspend for a few hours. Also noticed
  that it was not possible to re-establish wifi connectivity. Had to
  reboot the machine to get back to a proper working state.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-18-generic 5.4.0-18.22
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1443 F pulseaudio
marcus 1889 F pulseaudio
  Date: Sat Mar 21 11:43:52 2020
  Failure: oops
  InstallationDate: Installed on 2020-03-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
   Bus 001 Device 002: ID 0cf3:e300 Qualcomm Atheros Communications 
   Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=8c0be221-e900-480f-b359-5cbd3f16ebd4 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: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1862749] Re: [UBUNTU 20.04] Fix a potential data corruption issue for thin provisioned devices

[Frank Heimes]

Landed in focal master:
96225dde40a6 s390/dasd: fix data corruption for thin provisioned devices
and also in the current kernel.
Hence updating ticket to Fix Released.

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

** Changed in: ubuntu-z-systems
   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/1862749

Title:
  [UBUNTU 20.04] Fix a potential data corruption issue for thin
  provisioned devices

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

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 1861359] Re: swap storms kills interactive use

[Mason Loring Bliss]

Reporter hasn't confirmed that it's corrected yet... "Fix committed"
seems premature.

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

Title:
  swap storms kills interactive use

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

Bug description:
  [Impact]

  High watermark boosting can cause large swap activity under certain
  memory intensive workloads, making the system very unresponsive
  (screen does not refresh, keyboard not responding, etc.).

  This large swap activity seems to be prevented disabling high
  watermark boosting.

  [Test case]

  Opening this web page in chrome seems to be a good reproducer of the
  problem:

  
https://platform.leolabs.space/visualizations/conjunction?type=conjunction=2004981040

  When this page is opened we can clearly see from 'top' (for example)
  that the used swap is going up very quickly.

  With the fix applied swap is not used at all and the system is always
  responsive.

  [Fix]

  Set vm.watermark_boost_factor to 0, disabling watermark boosting by
  default.

  [Regression potential]

  Regression potential is minimal, setting vm.watermark_boost_factor to
  0 by default restores the old kernel behavior before watermark
  boosting was introduced. In case of unexpected regressions we can
  always fix this in user-space via sysctl.

  [Original report]

  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
     Mixer name : 'Realtek ALC285'
     Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
     Controls  : 53
     Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
     Mixer name : 'USB Mixer'
     Components : 'USB17ef:306f'
     Controls  : 9
     Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  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: 

[Kernel-packages] [Bug 1868388] Re: watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0]

[Mauricio Faria de Oliveira]

Hi Marcus,

Since 20.04 is not yet released, and the logs attached do not show the stack 
trace
(it seems like an apport behavior, in OopsText.txt, not your/human's fault 
AFAIK)
it seems there's little investigation that can be done in this error.

I'd suggest that if you can reproduce this problem again, please re-open this 
bug,
and provide the output of 'dmesg' after the error happens/before rebooting 
system.

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

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

Title:
  watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0]

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Got this after resuming from suspend for a few hours. Also noticed
  that it was not possible to re-establish wifi connectivity. Had to
  reboot the machine to get back to a proper working state.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-18-generic 5.4.0-18.22
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1443 F pulseaudio
marcus 1889 F pulseaudio
  Date: Sat Mar 21 11:43:52 2020
  Failure: oops
  InstallationDate: Installed on 2020-03-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
   Bus 001 Device 002: ID 0cf3:e300 Qualcomm Atheros Communications 
   Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=8c0be221-e900-480f-b359-5cbd3f16ebd4 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: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1863574] Re: Update mpt3sas Driver to 33.100.00.00 for Ubuntu 20.04

[Stefan Bader]

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

Title:
  Update mpt3sas Driver to 33.100.00.00 for Ubuntu 20.04

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

Bug description:
  [IMPACT]
  This is a feature request to update the mpt3sas driver in focal to latest 
version 33.100.00.00 in Ubuntu 20.04.  This will allow users to use
  fixes and enhancements that landed upstream in 5.6.  For this reason,
  Broadcom and Dell have requested that we pull these patches to update the 
  mpt3sas driver to the current upstream version.  

  [FIXES]
  The following commit ID's from Broadcom that whould be cherry-picked form 
mainline

  commit c53cf10ef6d9faeee9baa1fab824139c6f10a134
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=c53cf10ef6d9faeee9baa1fab824139c6f10a134
  commit c50ed99cd56ee725d9e14dffec8e8f1641b8ca30
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=c50ed99cd56ee725d9e14dffec8e8f1641b8ca30
  commit c6bdb6a10892d1130638a5e28d1523a813e45d5e
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=c6bdb6a10892d1130638a5e28d1523a813e45d5e
  commit 5b061980e362820894d7d884370b37005bed23ec
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=5b061980e362820894d7d884370b37005bed23ec
  commit c59777189433621392f6f5c82ecfc62f00a1232d
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=c59777189433621392f6f5c82ecfc62f00a1232d
  commit fce0aa08792b3ae725395fa25d44507dee0b603b
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=fce0aa08792b3ae725395fa25d44507dee0b603b
  commit e8c2307e6a690db9aaff84153b2857c5c4dfd969
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=e8c2307e6a690db9aaff84153b2857c5c4dfd969
  commit 36c6c7f75b0998f5a4b5c79cbb94ee1ab4ee35c0
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=36c6c7f75b0998f5a4b5c79cbb94ee1ab4ee35c0
  commit d3f623ae8e0323ca434ee9029100312a8be37773
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=d3f623ae8e0323ca434ee9029100312a8be37773
  commit 1ade26b616cc2da0b7277a97e3799c99bae0655b
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=1ade26b616cc2da0b7277a97e3799c99bae0655b
  commit ee560e7bbab0c10cf3f0e71997fbc354ab2ee5cb
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=ee560e7bbab0c10cf3f0e71997fbc354ab2ee5cb
  commit 5bb2f743cdaa6da618e77a6aab5c38b46072365b
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=5bb2f743cdaa6da618e77a6aab5c38b46072365b
  commit 3524a38e594dd5f090cbc3226e5f47cb4067fac7
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=3524a38e594dd5f090cbc3226e5f47cb4067fac7
  commit d8b2625f4699a36b1753d87e96b0c50a4531c065
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=d8b2625f4699a36b1753d87e96b0c50a4531c065
  commit 9e64fd1e65f72d229f96fcf390576e772770a01c
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=9e64fd1e65f72d229f96fcf390576e772770a01c
  commit 77fd4f2c88bf83205a21f9ca49fdcc0c7868dba9
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=77fd4f2c88bf83205a21f9ca49fdcc0c7868dba9
  commit b06ff10249036eec74fa8565503ac40d0ee92213
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=b06ff10249036eec74fa8565503ac40d0ee92213
  commit 29f571f8b4cc652cae9244630f714a610549d301
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=29f571f8b4cc652cae9244630f714a610549d301
  commit a8a6cbcd038de4ee3722c17edd7a4d84ce423f7d
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=a8a6cbcd038de4ee3722c17edd7a4d84ce423f7d
  commit a066f4c31359d07b1a2c5144b4b9a29901365fd0
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=a066f4c31359d07b1a2c5144b4b9a29901365fd0
  commit dd180e4eedfd85b80020a6fd566601f4765a9d69
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=dd180e4eedfd85b80020a6fd566601f4765a9d69
  commit 08e7378ee331a803cfdd91c512a3dea040f1da79
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=5.6/scsi-queue=08e7378ee331a803cfdd91c512a3dea040f1da79
  commit 764f472ba4a7a0c18107ebfbe1a9f1f5f5a1e411
  

[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use

[Stefan Bader]

** Also affects: linux (Ubuntu Focal)
   Importance: High
 Assignee: Andrea Righi (arighi)
   Status: Confirmed

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

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

Title:
  swap storms kills interactive use

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

Bug description:
  [Impact]

  High watermark boosting can cause large swap activity under certain
  memory intensive workloads, making the system very unresponsive
  (screen does not refresh, keyboard not responding, etc.).

  This large swap activity seems to be prevented disabling high
  watermark boosting.

  [Test case]

  Opening this web page in chrome seems to be a good reproducer of the
  problem:

  
https://platform.leolabs.space/visualizations/conjunction?type=conjunction=2004981040

  When this page is opened we can clearly see from 'top' (for example)
  that the used swap is going up very quickly.

  With the fix applied swap is not used at all and the system is always
  responsive.

  [Fix]

  Set vm.watermark_boost_factor to 0, disabling watermark boosting by
  default.

  [Regression potential]

  Regression potential is minimal, setting vm.watermark_boost_factor to
  0 by default restores the old kernel behavior before watermark
  boosting was introduced. In case of unexpected regressions we can
  always fix this in user-space via sysctl.

  [Original report]

  Hello, several times since upgrading to focal from 19.04 I've found my
  computer entirely unresponsive for periods of twenty or thirty
  seconds. No mouse movement, no keyboard input, the screen output does
  not change.

  My computer was using swap space and despite very slow writeout speeds
  well below what the NVME drive can handle, the computer was unusable.

  I've captured some vmstat 1 output and top output that I started
  collecting during the event. (Normally one very long painful period is
  followed by several shorter periods of uselessness.)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Wed Jan 29 23:44:05 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-12-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarnold2734 F pulseaudio
   /dev/snd/controlC1:  sarnold2734 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145'
     Mixer name : 'Realtek ALC285'
     Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
     Controls  : 53
     Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
     Mixer name : 'USB Mixer'
     Components : 'USB17ef:306f'
     Controls  : 9
     Simple ctrls  : 4
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=none
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO 20KHCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic 
root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash 
acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)
  UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  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: 

[Kernel-packages] [Bug 1866909] Re: Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

[Seth Forshee]

Afaict the ppc ima arch policy is about ensuring that signature
verification is done for module loading and kexec, which in our kernel
will be enforced by automatically turning on lockdown integrity mode
under secure boot. So my conclusion is that CONFIG_MODULE_SIG_FORCE
should stay off and CONFIG_IMA_ARCH_POLICY should be disabled.

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

Title:
  Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - George C. Wilson  - 2020-02-25 18:40:44 
==
  - sysfs enablement: TBD
  - ima: arch specific policy support 6191706246de
  - platform keyring changes for powerpc: TBD
  - Appended signatures support for IMA appraisal 
39b07096364a42c516415d5f841069e885234e61
  - integrity: Define a trusted platform keyring: 9dc92c45177a
  - ima: Support platform keyring for kernel appraisal: d7cecb676dd3
  - TPM 2.0 Multibank extend support: c1f92b4b04ad
  - TPM 2.0 Eventlog support: 4d23cc323cdb
  - ima: carry the measurement list across kexec: d68a6fe9fccf
  - kexec_file_load system call support: 500c7ab1a9db

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

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

[Kernel-packages] [Bug 1862888] Re: Boot hang on ASUS WS X299 SAGE

[Steven Clarkson]

Handled by #1867677

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

Title:
  Boot hang on ASUS WS X299 SAGE

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  Upstream kernels since 5.3 fail to boot on the ASUS WS X299 SAGE
  motherboard with firmware version 1201. This is the result of an
  infinite loop while trying to parse a malformed ACPI table. It is
  suspected to affect other ASUS motherboards, but I have no first
  hand proof of that.

  This is particularly troublesome for bionic HWE installs, which
  will then fail to boot after upgrading to the 5.3 series eoan
  kernel.

  [Test Case]

  Try to boot an ASUS WS X299 SAGE computer with firmware version 1201.

  Eoan and Focal kernels will fail to boot.

  Upstream kernel 5.6-rc1 will boot succressfully.

  
  [Fix]

  Cherry pick upstream  2b73ea379624 ("x86/boot: Handle malformed SRAT
  tables during early ACPI parsing")

  [Regression Potential]

  Low. Any system affected by this patch is already failing to boot.

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

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

[Kernel-packages] [Bug 1863581] Re: Ubuntu 20.04: megaraid_sas driver update to version 07.713.01.00-rc1

[Stefan Bader]

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

Title:
  Ubuntu 20.04: megaraid_sas driver update to version 07.713.01.00-rc1

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

Bug description:
  [IMPACT]
  This is a feature request to update megaraid_sas driver in Ubuntu 20.04 
release to latest Linux upstream tip.
  The current latest upstream megaraid_sas driver version is- 07.713.01.00-rc1.
  The current latest Ubuntu 20.04 Pre GA kernel has megaraid_sas driver 
version- 07.710.50.00-rc1. This will allow users to utilize features of
  the PERC 11 device. For this reason, Broadcom and Dell have requested that we 
pull these patches to update the megaraid_sas driver to the current upstream 
version.

  [FIXES]
  Below set of upstream commit ids will lift driver version to 07.713.01.00-rc1 
from 07.710.50.00-rc1:

  92b4f9d15059 scsi: megaraid_sas: fixup MSIx interrupt setup during resume
  824b72db5086 scsi: megaraid_sas: Update driver version to 07.713.01.00-rc1
  4d1634b8d12e scsi: megaraid_sas: Use Block layer API to check SCSI device 
in-flight IO requests
  56ee0c585602 scsi: megaraid_sas: Limit the number of retries for the IOCTLs 
causing firmware fault
  6d7537270e32 scsi: megaraid_sas: Do not initiate OCR if controller is not in 
ready state
  201a810cc188 scsi: megaraid_sas: Re-Define enum DCMD_RETURN_STATUS
  eeb63c23ffe1 scsi: megaraid_sas: Do not set HBA Operational if FW is not in 
operational state
  9330a0fd827a scsi: megaraid_sas: Do not kill HBA if JBOD Seqence map or RAID 
map is disabled
  eb974f34bb9d scsi: megaraid_sas: Do not kill host bus adapter, if adapter is 
already dead
  6e73550670ed scsi: megaraid_sas: Update optimal queue depth for SAS and NVMe 
devices
  a7faf81d7858 scsi: megaraid_sas: Set no_write_same only for Virtual Disk
  499e7246d6da scsi: megaraid_sas: Reset adapter if FW is not in READY state 
after device resume
  73374b39b01e scsi: megaraid_sas: Make poll_aen_lock static
  01b8bca81e18 compat_ioctl: use correct compat_ptr() translation in drivers
  8cfb8e40d686 scsi: megaraid_sas: remove unused variables 'debugBlk','fusion'
  ff7ca7fd03ce scsi: megaraid_sas: Unique names for MSI-X vectors
  9ab089d30bcf scsi: megaraid_sas: Introduce module parameter for default queue 
depth
  e5460f084b84 scsi: megaraid_sas: Fix a compilation warning
  88d5c343949e scsi: megaraid_sas: Make a bunch of functions static
  e45ab43b1d40 scsi: megaraid_sas: Make some functions static
  3b5f307ef3cb scsi: megaraid_sas: fix panic on loading firmware crashdump
  359603a3847e scsi: megaraid_sas: fix spelling mistake "megarid_sas" -> 
"megaraid_sas"
  07d9aa143464 scsi: megaraid_sas: set an unlimited max_segment_size

  Here is the link to latest Linux upstream megaraid_sas driver source:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/scsi/megaraid

  Please let me know if any further information is required.

  Thanks,
  Sumit

  All are clean cherry picks into the 5.4 branch and can be pulled from the
  following branch:

  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/lp1863581_megaraid_sas

  [TESTING]
  Modinfo should show that the megaraid_sas driver has been updated to 
07.713.01.00

  [REGRESSION RISK]
  Low - Focal is not yet released, this is not being backported to current 
releases.

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

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

[Kernel-packages] [Bug 1867586] Re: [hns3-0316]sync mainline kernel 5.6rc4 hns3 patchset into ubuntu HWE kernel branch

[Stefan Bader]

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

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

Title:
  [hns3-0316]sync mainline kernel 5.6rc4  hns3 patchset into ubuntu HWE
  kernel branch

Status in kunpeng920:
  New
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:
  New
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  [Bug Description]
   hns3 patchset have merged into mainline 5.6rc1 kernel.

  [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: clear port base VLAN when unload PF
  net: hns3: fix RMW issue for VLAN filter switch
  net: hns3: fix VF VLAN table entries inconsistent issue
  net: hns3: fix "tc qdisc del" failed issue
  net: hns3: reject unsupported coalescing params
  net: hns3: delete unnecessary logs after kzalloc fails
  net: hns3: synchronize some print relating to reset issue
  net: hns3: print out command code when dump fails in debugfs
  net: hns3: print out status register when VF receives unknown source interrupt
  net: hns3: add a check before PF inform VF to reset
  net: hns3: delete some reduandant code
  net: hns3: remove an unnecessary resetting check in 
hclge_handle_hw_ras_error()
  net: hns3: rename macro HCLGE_MAX_NCL_CONFIG_LENGTH
  net: hns3: fix some mixed type assignment
  net: hns3: fix a not link up issue when fibre port supports autoneg
  net: hns3: add missing help info for QS shaper in debugfs
  net: hns3: add support for dump MAC ID and loopback status in debugfs
  net: hns3: add enabled TC numbers and DWRR weight info in debugfs
  net: hns3: modify an unsuitable print when setting unknown duplex to fibre

  [Status]
  (In progress) net: hns3: clear port base VLAN when unload PF
  (In progress) net: hns3: fix RMW issue for VLAN filter switch
  (In progress) net: hns3: fix VF VLAN table entries inconsistent issue
  (In progress) net: hns3: fix "tc qdisc del" failed issue
  (Fix committed) net: hns3: fix a not link up issue when fibre port supports 
autoneg

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

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

[Kernel-packages] [Bug 1866357] Re: Pop sound from build-in speaker during cold boot and resume from S3

[Stefan Bader]

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

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

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

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

Title:
  Pop sound from build-in speaker during cold boot and resume from S3

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

Bug description:
  [Description]
  On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot 
and resume from S3, internal speaker will have a noticeable short pop noise.  

  [More detail]
  There are similar bugs reported indicating it's related to codec powersaving 
[1].  On some devices, disable powersaving can workaround it, but the same 
workaround does not work on this device.
  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663

  [Experiment]
  With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise
  With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise
  With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise
  So I started testing kernels between 4.13 and 4.15, found the issue does not 
present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that 
started to have the pop noise.

  [HW info]
  Codec: Realtek ALC3253
  00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03)


  Device is not with me at this moment, I will provide more info if required.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1901 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osp1-sanbernardino+X100
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-03-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Wyse 5070 Thin Client
  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-40-generic 
root=UUID=22fa172b-895b-4061-834e-d616380befc5 ro mem_sleep_default=deep quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.9
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd01/08/2020:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr:
  dmi.product.family: Wyse Thin Client 5000 Series
  dmi.product.name: Wyse 5070 Thin Client
  dmi.product.sku: 080C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1866909] Re: Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

[Seth Forshee]

I'm suddenly having a major sense of deja vu about this. I think we hit
very similar issues on x86, and after discussions with Mimi we decided
that CONFIG_IMA_ARCH_POLICY should be disabled for us. I think this may
be the right solution here too.

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

Title:
  Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - George C. Wilson  - 2020-02-25 18:40:44 
==
  - sysfs enablement: TBD
  - ima: arch specific policy support 6191706246de
  - platform keyring changes for powerpc: TBD
  - Appended signatures support for IMA appraisal 
39b07096364a42c516415d5f841069e885234e61
  - integrity: Define a trusted platform keyring: 9dc92c45177a
  - ima: Support platform keyring for kernel appraisal: d7cecb676dd3
  - TPM 2.0 Multibank extend support: c1f92b4b04ad
  - TPM 2.0 Eventlog support: 4d23cc323cdb
  - ima: carry the measurement list across kexec: d68a6fe9fccf
  - kexec_file_load system call support: 500c7ab1a9db

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

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

[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround

[bmaupin]

I'm still seeing this same behaviour for the 5.3 kernel.

I'm just now getting back to this, and I think I'm going to need some
hand holding...

> Try changing IRQ configs (CONFIG_GENERIC_IRQ_MIGRATION=y to =n) and
i2c-designware's (CONFIG_I2C_DESIGNWARE_CORE=y to =m).

I copied the 4.13.0 configuration from here to .config and modified
those two options:

curl https://launchpadlibrarian.net/414616578/config-4.13.0-041300rc1-generic > 
.config
cp .config .config.bak
sed -i 's/CONFIG_GENERIC_IRQ_MIGRATION=.*/CONFIG_GENERIC_IRQ_MIGRATION=n/' 
.config
sed -i 's/CONFIG_I2C_DESIGNWARE_CORE=.*/CONFIG_I2C_DESIGNWARE_CORE=m/' .config

Now I can confirm the changes:

$ diff .config.bak .config
92c92
< CONFIG_GENERIC_IRQ_MIGRATION=y
---
> CONFIG_GENERIC_IRQ_MIGRATION=n
4073c4073
< CONFIG_I2C_DESIGNWARE_CORE=y
---
> CONFIG_I2C_DESIGNWARE_CORE=m

However, when I build the kernel and look at the .config file, both of
them seem to be reverted.

The same thing happens if I run make oldconfig; the changes aren't
preserved.

I can't find them either using make menuconfig. I just see this:

│ Symbol: GENERIC_IRQ_MIGRATION [=y]
  │  
  │ Type  : boolean 
│  
  │   Defined at kernel/irq/Kconfig:38  
│  
  │   Selected by: X86 [=y] && SMP [=y]


  │ Symbol: I2C_DESIGNWARE_CORE [=y]
│  
  │ Type  : tristate
│  
  │   Defined at drivers/i2c/busses/Kconfig:480 
│  
  │   Depends on: I2C [=y] && HAS_IOMEM [=y]
│  
  │   Selected by: I2C_DESIGNWARE_PLATFORM [=y] && I2C [=y] && HAS_IOMEM [=y] 
&& (ACPI [=y] && COMMON_CLK [=y] || !ACPI [=y]) || I2C_DESIGNWARE


How can I override these two values?

Thanks!

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

Title:
  Thinkpad T430u won't boot without noapic workaround

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

Bug description:
  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot,
  hanging at various screens:

  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked

  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38
  - 4.15.0-42
  - 4.20.0-rc7

  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.

  This bug seems very similar to what's described here for the Thinkpad
  E485/E585: https://evilazrael.de/node/401

  I'll attach screenshots of various times I've encountered this bug
  over the last year.

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

  $ apt-cache policy linux-image-4.15.0-42-generic
  linux-image-4.15.0-42-generic:
    Installed: 4.15.0-42.45
    Candidate: 4.15.0-42.45
    Version table:
   *** 4.15.0-42.45 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bryan  2349 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec 13 15:31:15 2018
  HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac
  InstallationDate: Installed on 2014-05-08 (1680 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 

[Kernel-packages] [Bug 1870543] [NEW] [Selftests] Apply various fixes and improvements

[Stefan Bader]

Public bug reported:

This is a generic (catch-all) bug for tracking various changes to
improve the built-in kernel selftests.

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


** Tags: focal

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

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

Title:
  [Selftests] Apply various fixes and improvements

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  This is a generic (catch-all) bug for tracking various changes to
  improve the built-in kernel selftests.

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  ryzen 5 3600x hard lockup

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System randomly freezes and requires a hard reset. Very frequently it
  happens when trying to wake it up from a period of inactivity. (after
  the screen has turned off). Almost daily occurrence.

  
  Description:  Ubuntu 19.10
  Release:  19.10
  Codename: eoan

  
  Linux MartoBeast 5.3.0-45-generic #37-Ubuntu SMP Thu Mar 26 20:41:27 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-45-generic 5.3.0-45.37
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  martin 2642 F pulseaudio
   /dev/snd/controlC0:  martin 2642 F pulseaudio
   /dev/snd/controlC2:  martin 2642 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 08:46:11 2020
  InstallationDate: Installed on 2019-12-08 (117 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic 
root=UUID=05d2cb45-6b9c-47b3-8102-e6c6a13de26b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-45-generic N/A
   linux-backports-modules-5.3.0-45-generic  N/A
   linux-firmware1.183.4
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1870538] [NEW] ryzen 5 3600x hard lockup

[Martin Gerdzhev]

Public bug reported:

System randomly freezes and requires a hard reset. Very frequently it
happens when trying to wake it up from a period of inactivity. (after
the screen has turned off). Almost daily occurrence.


Description:Ubuntu 19.10
Release:19.10
Codename:   eoan


Linux MartoBeast 5.3.0-45-generic #37-Ubuntu SMP Thu Mar 26 20:41:27 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-45-generic 5.3.0-45.37
ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
Uname: Linux 5.3.0-45-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  martin 2642 F pulseaudio
 /dev/snd/controlC0:  martin 2642 F pulseaudio
 /dev/snd/controlC2:  martin 2642 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  3 08:46:11 2020
InstallationDate: Installed on 2019-12-08 (117 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
IwConfig:
 lono wireless extensions.
 
 enp4s0no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic 
root=UUID=05d2cb45-6b9c-47b3-8102-e6c6a13de26b ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-45-generic N/A
 linux-backports-modules-5.3.0-45-generic  N/A
 linux-firmware1.183.4
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/06/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F11
dmi.board.asset.tag: Default string
dmi.board.name: X570 AORUS ELITE
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: X570 AORUS ELITE
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug eoan

** Attachment added: "journal_log_03042020.txt"
   
https://bugs.launchpad.net/bugs/1870538/+attachment/5345574/+files/journal_log_03042020.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/1870538

Title:
  ryzen 5 3600x hard lockup

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System randomly freezes and requires a hard reset. Very frequently it
  happens when trying to wake it up from a period of inactivity. (after
  the screen has turned off). Almost daily occurrence.

  
  Description:  Ubuntu 19.10
  Release:  19.10
  Codename: eoan

  
  Linux MartoBeast 5.3.0-45-generic #37-Ubuntu SMP Thu Mar 26 20:41:27 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-45-generic 5.3.0-45.37
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  martin 2642 F pulseaudio
   /dev/snd/controlC0:  martin 2642 F pulseaudio
   /dev/snd/controlC2:  martin 2642 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 08:46:11 2020
  InstallationDate: Installed on 2019-12-08 (117 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic 
root=UUID=05d2cb45-6b9c-47b3-8102-e6c6a13de26b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-45-generic N/A
   linux-backports-modules-5.3.0-45-generic  N/A
   linux-firmware1.183.4
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  

[Kernel-packages] [Bug 1866909] Re: Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

[Seth Forshee]

Our policy is to require module signatures only under lockdown.
CONFIG_MODULE_SIG_FORCE requires modules to be signed unconditionally,
which makes dkms impossible on systems which have no mechanism for
importing keys from firmware.

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

Title:
  Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - George C. Wilson  - 2020-02-25 18:40:44 
==
  - sysfs enablement: TBD
  - ima: arch specific policy support 6191706246de
  - platform keyring changes for powerpc: TBD
  - Appended signatures support for IMA appraisal 
39b07096364a42c516415d5f841069e885234e61
  - integrity: Define a trusted platform keyring: 9dc92c45177a
  - ima: Support platform keyring for kernel appraisal: d7cecb676dd3
  - TPM 2.0 Multibank extend support: c1f92b4b04ad
  - TPM 2.0 Eventlog support: 4d23cc323cdb
  - ima: carry the measurement list across kexec: d68a6fe9fccf
  - kexec_file_load system call support: 500c7ab1a9db

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

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

[Kernel-packages] [Bug 1869799] Re: no sound driver since 5.3.0.42 kernel

[Hui Wang]

@schmit,

Could you please test this kernel
https://people.canonical.com/~hwang4/testdsp/, remove the dmic_detect=0
workaround, and download all deb and sudo apt install *.deb;reboot

thx.

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

Title:
  no sound driver since 5.3.0.42 kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  no sound driver since 5.3.0.42 kernel, 5.3.0.45 kernel doesn't solve the 
problem. i have only a dummy soundcard. no sound. 
  5.3.0.42 kernel works fine.
  my sound card is intel 100 / c230 hd audio

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

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

[Kernel-packages] [Bug 1870265] Re: Intel GPU causes BUG: kernel NULL pointer dereference, address: 0000000000000040

[Leonardo Müller]

This crash seems to be easy to reproduce. I made an Apitrace of the part
of Gurumin with the scene that caused the first crash and let it
replaying endlessly. After 1h30min, the system crashed again.

The apitrace can be obtained from:
https://mega.nz/file/8thHlYpa#_HBCUsIifUnD8R3K2U6v--
BWg8noez_Fn7KazWrrGRg

A warning to those that want to play Gurumin: what was traced here can
be considered mild spoilers.

Log of the last crash:

Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741100] BUG: kernel 
NULL pointer dereference, address: 0040
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741109] #PF: supervisor 
read access in kernel mode
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.74] #PF: 
error_code(0x) - not-present page
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741113] PGD 0 P4D 0 
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741117] Oops:  [#1] 
SMP PTI
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741123] CPU: 1 PID: 
201976 Comm: xfwm4 Tainted: P   O  5.4.0-21-generic #25-Ubuntu
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741125] Hardware name: 
LENOVO 80UG/Toronto 4A2, BIOS 0XCN45WW 08/09/2018
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741208] RIP: 
0010:i915_active_acquire+0xe/0x80 [i915]
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741213] Code: 00 48 c7 
c6 a5 8e 5f c0 e8 af c7 82 f7 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 
1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 01 
f0 0f b1 53 38 75 f2 45 31
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741214] RSP: 
0018:b4fa4775f9c8 EFLAGS: 00010286
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741216] RAX: 
 RBX: 93a6aeba7e40 RCX: 
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741218] RDX: 
93a4b6d2d900 RSI: 93a6aeba7e40 RDI: 0008
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741219] RBP: 
b4fa4775f9e0 R08: 93a72e958368 R09: 93a72e958360
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741220] R10: 
93a4e7248280 R11: 0001 R12: 93a4b6d2d900
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741221] R13: 
0008 R14: 93a4b6d2d900 R15: 93a72e958240
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741222] FS:  
7f151279ba80() GS:93a7de28() knlGS:
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741224] CS:  0010 DS: 
 ES:  CR0: 80050033
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741225] CR2: 
0040 CR3: 00027c8cc006 CR4: 003606e0
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741226] DR0: 
 DR1:  DR2: 
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741227] DR3: 
 DR6: fffe0ff0 DR7: 0400
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741229] Call Trace:
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741289]  
i915_active_ref+0x24/0x200 [i915]
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741338]  
i915_vma_move_to_active+0x74/0xf0 [i915]
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741367]  
eb_submit+0xff/0x440 [i915]
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741393]  
i915_gem_do_execbuffer+0x88e/0xc20 [i915]
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741399]  ? 
sock_def_readable+0x40/0x70
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741401]  ? 
__kmalloc_node+0x205/0x320
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741428]  
i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915]
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741453]  ? 
i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741466]  
drm_ioctl_kernel+0xae/0xf0 [drm]
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741476]  
drm_ioctl+0x234/0x3d0 [drm]
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741501]  ? 
i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741505]  ? 
__switch_to_asm+0x40/0x70
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741506]  ? 
__switch_to_asm+0x34/0x70
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741508]  ? 
__switch_to_asm+0x40/0x70
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741509]  ? 
__switch_to_asm+0x34/0x70
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741511]  ? 
__switch_to_asm+0x40/0x70
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741512]  ? 
__switch_to_asm+0x34/0x70
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741514]  ? 
__switch_to_asm+0x40/0x70
Apr  3 01:24:37 Lenovo-ideapad-310-14ISK kernel: [87485.741516]  ? 
__switch_to+0x110/0x470
Apr  3 01:24:37 

[Kernel-packages] [Bug 1869180] Re: focal/linux-raspi2: Upstream raspberrypi patchset 2020-03-27

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-focal

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

Title:
  focal/linux-raspi2: Upstream raspberrypi patchset 2020-03-27

Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-raspi2 source package in Focal:
  Fix Committed

Bug description:
  Upstream raspberrypi patchset 2020-03-27

    Ported from the following raspberrypi branch:
  rpi-5.4.y
    from https://github.com/raspberrypi/linux.git

  drm/modes: parse_cmdline: Explicitly memset the passed in drm_cmdline_mode 
struct
  drm/modes: parse_cmdline: Remove some unnecessary code (v2)
  drm/modes: parse_cmdline: Add support for specifying panel_orientation (v2)
  drm/modes: parse_cmdline: Allow specifying stand-alone options
  drm/modes: parse_cmdline: Set bpp/refresh_specified after successful parsing
  drm/modes: parse_cmdline: Add freestanding argument to 
drm_mode_parse_cmdline_options()
  drm/modes: parse_cmdline: Rework drm_mode_parse_cmdline_options()
  drm/modes: parse_cmdline: Accept extras directly after mode combined with 
options
  drm/modes: parse_cmdline: Stop parsing extras after bpp / refresh at ', '
  drm/modes: parse_cmdline: Make various char pointers const
  drm/modes: parse_cmdline: Fix possible reference past end of string
  net: bcmgenet: Clear ID_MODE_DIS in EXT_RGMII_OOB_CTRL when not needed
  ARM: dts: bcm271x: Use a53 pmu, drop RPI364
  ARM: dts: bcm2711: Add 32-bit PMU compatibility
  Add support for merus-amp soundcard and ma120x0p codec
  gpio-ir-overlay: add parameter to configure signal polarity (#3490)
  drm/vc4: Add DRM_FORMAT_P030 support to firmware-kms
  drm/fourcc: Add packed 10bit YUV 4:2:0 format
  drm/vc4: fkms: Change crtc_state structure name to avoid conflict
  media: ov5647: change defaults to better match raw camera applications.
  media: ov5647: Add extra 10-bit sensor modes.
  media: ov5647: Add V4L2 controls for analogue gain, exposure and AWB
  media: ov5647: Add basic support for multiple sensor modes.
  media: ov5647: Fix return codes from ov5647_write/ov5647_read functions.
  Kbuild: Allow .dtbo overlays to be built, adjust.
  overlays: imx219: Correct link frequency to match the upstream driver
  media: i2c: Add driver for Sony IMX219 sensor
  media: dt-bindings: media: i2c: Add IMX219 CMOS sensor binding
  Revert "media: dt-bindings: Add binding for the Sony IMX219 sensor"
  Revert "media: i2c: Add driver for Sony IMX219 sensor"
  bcm2711-rpi.dtsi: Use upstream pcie node
  PCI: brcmstb: Fix build on 32bit ARM platforms with older compilers
  PCI: brcmstb: Add MSI support
  PCI: brcmstb: Add Broadcom STB PCIe host controller driver
  ARM: dts: bcm2711: Enable PCIe controller
  dma-mapping: treat dev->bus_dma_mask as a DMA limit
  dma-direct: exclude dma_direct_map_resource from the min_low_pfn check
  dma-direct: avoid a forward declaration for phys_to_dma
  dma-direct: unify the dma_capable definitions
  PCI: of: Add inbound resource parsing to helpers
  x86/PCI: sta2x11: use default DMA address translation
  dma-direct: check for overflows on 32 bit DMA addresses
  dma/direct: turn ARCH_ZONE_DMA_BITS into a variable
  resource: Add a resource_list_first_type helper
  mm: refresh ZONE_DMA and ZONE_DMA32 comments in 'enum zone_type'
  arm64: use both ZONE_DMA and ZONE_DMA32
  arm64: rename variables used to calculate ZONE_DMA32's size
  arm64: mm: use arm64_dma_phys_limit instead of calling max_zone_dma_phys()
  of: Make of_dma_get_range() work on bus nodes
  of/address: Translate 'dma-ranges' for parent nodes missing 'dma-ranges'
  of: Factor out #{addr,size}-cells parsing
  of: address: Follow DMA parent for "dma-coherent"
  of/address: Introduce of_get_next_dma_parent() helper
  Revert "dma-direct: check for overflows on 32 bit DMA addresses"
  Revert "arm64/mm: Limit the DMA zone for arm64"
  Revert "PCI: brcmstb: Add Broadcom STB PCIe host controller driver"
  Revert "PCI: brcmstb: Add dma-range mapping for inbound traffic"
  Revert "PCI: brcmstb: Add MSI capability"
  Revert "pcie-brcmstb: Changes for BCM2711"
  Revert "bcm2835-dma: Add proper 40-bit DMA support"
  Revert "bcm2835-dma: Correct SoC name"
  Revert "pcie-brcmstb: Don't set DMA ops for root complex"
  Revert "Ported pcie-brcmstb bounce buffer implementation 

[Kernel-packages] [Bug 1862708] Re: tracing doesn't work on focal

[Francis Ginther]

Marking 'Fix Released' after the lockdown changes.

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

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

Title:
  tracing doesn't work on focal

Status in linux package in Ubuntu:
  Fix Released
Status in perf-tools-unstable package in Ubuntu:
  New

Bug description:
  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:

  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options

  
  I'm guessing this is due to lockdown:

  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534786] Could not create tracefs 'timestamp_mode' entry
  [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534788] Could not create tracefs 'buffer_percent' entry
  [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534817] Could 

[Kernel-packages] [Bug 1866909] Re: Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

[Frank Heimes]

If we understood you correctly you want to have CONFIG_MODULE_SIG_FORCE
set (for Power only) - so we are considering that ...

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

Title:
  Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - George C. Wilson  - 2020-02-25 18:40:44 
==
  - sysfs enablement: TBD
  - ima: arch specific policy support 6191706246de
  - platform keyring changes for powerpc: TBD
  - Appended signatures support for IMA appraisal 
39b07096364a42c516415d5f841069e885234e61
  - integrity: Define a trusted platform keyring: 9dc92c45177a
  - ima: Support platform keyring for kernel appraisal: d7cecb676dd3
  - TPM 2.0 Multibank extend support: c1f92b4b04ad
  - TPM 2.0 Eventlog support: 4d23cc323cdb
  - ima: carry the measurement list across kexec: d68a6fe9fccf
  - kexec_file_load system call support: 500c7ab1a9db

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

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

[Kernel-packages] [Bug 1855668] Re: lockdown on power

[Frank Heimes]

The revised patch looks indeed less strict - we are considering that one
...

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

Title:
  lockdown on power

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  == Comment: #0 - Michael Ranweiler  - 2019-11-11 
08:50:51 ==
  For 20.04 testing/inclusion.  The ubuntu kernel team has a ppa here for 
testing:
  https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable

  Test results will follow...

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

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

[Kernel-packages] [Bug 1866882] Re: segfault in libllvm-10 when building kernel bpf selftests on s390

[Matthias Klose]

not seen anymore with 1:10.0.0-1ubuntu2

** Changed in: llvm-toolchain-10 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  segfault in libllvm-10 when building kernel bpf selftests on s390

Status in linux package in Ubuntu:
  Incomplete
Status in llvm-toolchain-10 package in Ubuntu:
  Fix Released

Bug description:
  Seeing this in autopkgtest for the 5.4.0-18 kernel. Only happens on
  s390, other architectures are fine.

    Stack dump:
    0.  Program arguments: llc -march=bpf -mcpu=probe -filetype=obj -o 
/tmp/autopkgtest.92AlD3/build.vya/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/btf__core_reloc_nesting___err_array_container.o
    #0 0x03ff830ab14a (/lib/s390x-linux-gnu/libLLVM-10.so.1+0x9ab14a)
    Segmentation fault (core dumped)

  Full log:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/s390x/l/linux/20200310_180956_146bd@/log.gz

  This did not happen for the 5.4.0-17 upload with llvm-9, with no
  changes to the bpf program being compiled when the segfault happens
  between the -17 and -18 uploads.

  To reproduce, clone the focal kernel tree and build the bpf selftests.

  $ git clone --single-branch --depth=1 -b master-next 
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal
  $ make -C focal/tools/testing/selftests TARGETS=bpf

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

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

[Kernel-packages] [Bug 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache

[Sebastian Marsching]

Hi Mauricio,

there is the problem that this tarball contains an awful lot of
sensitive data, some of that personal data that is protected under the
GDPR.

Maybe you could tell me which specific parts / sections you are
interested in, so that I can anonymize and upload them.

Thanks,
Sebastian

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

Title:
  Regression in kernel 4.15.0-91 causes kernel panic with Bcache

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems
  does not boot any longer. It always crashes during boot with a kernel
  panic.

  I suspect that this crash might be related to Bcache because this is
  the only one of our systems where we use Bcache and the kernel panic
  appears right after Bcache initialization.

  I already checked that this bug still exists in the 4.15.0-92.93
  kernel from proposed.

  Unfortunately, I cannot do a bisect because this is a critical
  production system and we do not have any other system with a similar
  configuration.

  I attached a screenshot with the trace of the kernel panic.

  The last message that appears before the kernel panic (or rather the
  last one that I can see - there is a rather long pause between that
  message and the panic and I cannot scroll up far enough to ensure that
  there are no other messages in between) is:

  bcache: register_bcache() error /dev/dm-0: device already registered

  When booting with kernel 4.15.0-88 that does not have this problem,
  the next message is

  bcache: register_bcache() error /dev/dm-12: device already registered
  (emitting change event)

  After that the next message is:

  Begin: Loading essential drivers ... done

  This message also appears after the kernel panic, but the boot process
  stalls and the system can only be recovered by doing a hardware reset.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-88-generic 4.15.0-88.88
  ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
  Uname: Linux 4.15.0-88-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 17 21:08 seq
   crw-rw 1 root audio 116, 33 Mar 17 21:08 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Mar 18 12:55:18 2020
  HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a
  InstallationDate: Installed on 2013-07-02 (2450 days ago)
  InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release 
amd64 (20130214)
  MachineType: HP ProLiant DL160 G6
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic 
root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-88-generic N/A
   linux-backports-modules-4.15.0-88-generic  N/A
   linux-firmware 1.173.16
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago)
  dmi.bios.date: 11/06/2009
  dmi.bios.vendor: HP
  dmi.bios.version: O33
  dmi.chassis.asset.tag: 0191525
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL160 G6
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1855668] patch 1/2

[bugproxy]

--- Comment on attachment From daniel.axte...@ibm.com 2020-04-03 03:05 
EDT---


Hi Seth,

Thanks, that was extremely helpful.

Nayna noticed that I was overly keen to lock things down - I should only
lock down in Secure mode: if a system is in Trusted mode only I
shouldn't lock it down. This now matches the UEFI behaviour: (AFAICT)
measurements are made unconditionally but lockdown only occurs in Secure
Boot mode.

I have updated patch 1/2.

Kind regards,
Daniel

** Attachment added: "patch 1/2"
   
https://bugs.launchpad.net/bugs/1855668/+attachment/5345455/+files/0001-UBUNTU-SAUCE-lockdown-powerpc-lock-down-kernel-in-se.patch

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

Title:
  lockdown on power

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  == Comment: #0 - Michael Ranweiler  - 2019-11-11 
08:50:51 ==
  For 20.04 testing/inclusion.  The ubuntu kernel team has a ppa here for 
testing:
  https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable

  Test results will follow...

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

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

[Kernel-packages] [Bug 1867587] Re: [sas-0316]sync mainline kernel 5.6rc1 roce patchset into ubuntu HWE kernel branch

[Andrew Cloke]

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

** Changed in: kunpeng920/ubuntu-18.04-hwe
   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/1867587

Title:
  [sas-0316]sync mainline kernel 5.6rc1 roce patchset into ubuntu HWE
  kernel branch

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 Released
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  [Bug Description]
  SAS patchset have merged into mainline 5.6rc1 kernel.

  [Steps to Reproduce]
1)
2)
3)

  [Actual Results]

  [Expected Results]

  [Reproducibility]

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

  [Resolution]
  scsi: hisi_sas: Rename hisi_sas_cq.pci_irq_mask
  scsi: hisi_sas: Add prints for v3 hw interrupt converge and automatic affinity
  scsi: hisi_sas: Modify the file permissions of trigger_dump to write only
  scsi: hisi_sas: Replace magic number when handle channel interrupt
  scsi: hisi_sas: replace spin_lock_irqsave/spin_unlock_restore with 
spin_lock/spin_unlock
  scsi: hisi_sas: use threaded irq to process CQ interrupts

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

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

[Kernel-packages] [Bug 1867588] Re: [SFC-0316]sync mainline kernel 5.7rc1 SFC patchset into ubuntu HWE kernel branch

[Andrew Cloke]

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

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

** Changed in: kunpeng920/ubuntu-18.04-hwe
Milestone: None => ubuntu-18.04.5

** Changed in: kunpeng920
   Status: New => Fix Committed

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

Title:
  [SFC-0316]sync mainline kernel 5.7rc1 SFC patchset into ubuntu HWE
  kernel branch

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]
  SFC patchset have merged into mainline 5.7RC1rc2 kernel.

  [Steps to Reproduce]
1)
2)
3)

  [Actual Results]

  [Expected Results]

  [Reproducibility]

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

  [Resolution]

  spi: HiSilicon v3xx: Use DMI quirk to set controller buswidth override bits
  spi: HiSilicon v3xx: Properly set CMD_CONFIG for Dual/Quad modes
  spi: Allow SPI controller override device buswidth

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

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