date:20210517

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

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

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

Title:
  ubuntu 20.04 nfs page fault since Kernel 5.3 (?)

Status in linux-oem-5.6 package in Ubuntu:
  Expired

Bug description:
  Kind of a follow up/extension to
  https://bugs.launchpad.net/ubuntu/disco/+source/linux/+bug/1858832

  == Original Bug Report (for the most part, still holds true) ==

  RELEASE=19.3
  CODENAME=tricia
  EDITION="Cinnamon"
  DESCRIPTION="Linux Mint 19.3 Tricia"
  DESKTOP=Gnome
  TOOLKIT=GTK
  NEW_FEATURES_URL=https://www.linuxmint.com/rel_tricia_cinnamon_whatsnew.php
  RELEASE_NOTES_URL=https://www.linuxmint.com/rel_tricia_cinnamon.php
  USER_GUIDE_URL=https://www.linuxmint.com/documentation.php
  GRUB_TITLE=Linux Mint 19.3 Cinnamon

  My home dir is mounted through nfs on a local server via nfs4 and krb5i.
  When stressing the mounted directory or its sub-directories (sometimes 
starting firefox, sometimes starting thunderbird, nearly guaranteed when 
compiling, sometimes the login itself), it will eventually lead to the 
following stack-trace. The corresponding process is then stuck and
  accessing the mounted directory (like calling ls) easily yields further and 
similar stack trace and causing the process to also stuck.

  Currently I am running an AMD 3950x on a ASUS Crosshair VII Hero Wifi
  (chipset x470).

  I installed Ubuntu 20.04 LTS Desktop to check if the newer kernels
  (5.4 + 5.6) work without issues, but sadly, they **do not**.

  With a little compile-stress-test, I have tested the following kernels which 
seem to run fine:
   * 4.15.0-69
   * 4.15.0-70
   * 4.15.0-72
   * 5.0.0-32
   * 5.0.0-47 (current daily driver, runs without a hassle, max test length >7d 
- I am writing this bug report on it)
   * 5.4.0-32-generic #36-Ubuntu from the proposal 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/19306320
   * 5.6.0-1010-oem #10-Ubuntu SMP
   * 5.7.0-050700rc6-generic #202005172030

  But the following kernels do not run stable:
   * 5.3.0-51 (Linux Mint 19.3 HWE)
   * 5.4.0-28 (Ubuntu 20.04)
   * 5.4.0-31-generic #35-Ubuntu
   * 5.6.0-1008 (Ubuntu 20.04 OEM)

  $ lspci | grep -i ether
  06:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network 
Connection (rev 03

  $ mount | grep filer
  filer:/ on /share type nfs4 
(rw,noatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=krb5i,clientaddr=192.168.3.55,local_lock=none,addr=192.168.2.33)
  filer:/home/michael on /share/home/michael type nfs4 
(rw,noatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=krb5i,clientaddr=192.168.3.55,local_lock=none,addr=192.168.2.33)

  $ cat /etc/fstab | grep -i filer
  filer:/ /share/ nfs4 
nfsvers=4,sec=krb5i,rw,x-systemd.automount,soft,intr,tcp,noatime 0 0
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rootmw 2299 F pulseaudio
   /dev/snd/controlC2:  rootmw 2299 F pulseaudio
   /dev/snd/controlC1:  rootmw 2299 F pulseaudio
   /dev/snd/controlC3:  rootmw 2299 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-02 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   lono wireless extensions.

   enp6s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1008-oem 
root=/dev/mapper/vgnvme-ubuntu2004 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1008.8-oem 5.6.4
  RelatedPackageVersions:
   linux-restricted-modules-5.6.0-1008-oem N/A
   linux-backports-modules-5.6.0-1008-oem  N/A
   linux-firmware  1.187
  RfKill:

  Tags:  focal
  Uname: Linux 5.6.0-1008-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3004
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG CROSSHAIR VII HERO (WI-FI)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default

[Kernel-packages] [Bug 1908286] Re: Asus G732LWS | ALC294 | Speakers don't work on 20.04 or 20.10

[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/1908286

Title:
  Asus G732LWS | ALC294 | Speakers don't work on 20.04 or 20.10

Status in linux package in Ubuntu:
  Expired

Bug description:
  Asus G732LWS-DS76
  Realtek ALC294 (Intel HDA Audio)
  Xubuntu 20.04 with kernel 5.4.0-58-generic

  No sound from speakers even though it shows in pavucontrol.
  For some reason the sound gets redirected to the internal mic (when I play 
music there is no sound from speakers, but when I open Audacity and start 
recording it records a song playing).

  I tried:
  alc294-sound-patch.fw from https://bugzilla.kernel.org/show_bug.cgi?id=206589
No effect
  "options snd-hda-intel model=asus-zenbook" in /etc/modprobe.d/alsa-base.conf
Speakers start working, but it is impossible to control the volume, they're 
eithher ON (100%) or OFF (Muted)

  I tried different kernels and sidtributions to localize the problem:
  Doesn't work
Xubuntu 20.04 | 5.4.0-58-generic
Xubuntu 20.04 | 5.4.0-54-generic
Xubuntu 20.04 | 5.4.0-48-generic
Xubuntu 20.10 | 5.8.0-25-generic
Fedora 33 | 5.8.15-301.fc33.x86_64
Manjaro 20.2  | 5.9.11-3-MANJARO
  WORKS
Xubuntu 20.04 | 5.4.0-42-generic

  It appears that it is a kernel problem and something broke between
  5.4.0-42-generic and 5.4.0-48-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kotek  5812 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Dec 15 09:25:13 2020
  InstallationDate: Installed on 2020-10-01 (75 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b05:1866 ASUSTek Computer, Inc. N-KEY Device
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ROG Strix G732LWS_G732LWS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=8d8cfa7f-5e24-4952-b6ae-4ae35ca9563d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G732LWS.310
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G732LWS
  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.:bvrG732LWS.310:bd07/14/2020:svnASUSTeKCOMPUTERINC.:pnROGStrixG732LWS_G732LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG732LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G732LWS_G732LWS
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1901363] Re: Updating to 1.2.4-1 breaks pulseaudio on AMD Renoir devices

[Expired for alsa-ucm-conf (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: alsa-ucm-conf (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Updating to 1.2.4-1 breaks pulseaudio on AMD Renoir devices

Status in alsa-ucm-conf package in Ubuntu:
  Expired

Bug description:
  same issue on groovy on my Lenovo T14 AMD.
  https://bugs.archlinux.org/task/68313
  already fixed upstream
  https://github.com/alsa-project/alsa-ucm-conf/issues/55

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

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

[Kernel-packages] [Bug 1910976] Re: Cherry-pick dm-crypt performance improvement patch from Linux 5.9

2021-05-17 Thread gerald.yang

** Description changed:

  === SRU Justification ===
  [Impact]
- To get better performance for dm-crypt in some cases, bypass kcryptd 
workqueue can reduce the overhead in context switch between workers, 
cherry-pick commit 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 from mainline 
kernel, and this is not enabled by default
+ To get better performance for dm-crypt in some cases, bypass kcryptd 
workqueue can reduce the overhead in context switch between workers, 
cherry-pick commit 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 from mainline 
kernel, and bypass kcryptd workqueue is not enabled by default
  
  [Fix]
  Add flags to bypass kcryptd workqueue
  
  [Test]
  create dm-crypt and setup DM_CRYPT_NO_READ_WORKQUEUE and 
DM_CRYPT_NO_WRITE_WORKQUEUE, read/write data and run perf record to see if 
read/write to the encrypted device will bypass kcryptd workqueue
  
  [Regression Potential]
  Low, this feature is disabled by default, need to enable manually
  
  = original bug description =
  Hi,
  
  I'm asking if it would be possible to cherry-pick patch "dm crypt: add
  flags to optionally bypass kcryptd workqueues" into the 5.4 Ubuntu
  kernel. This patch has been merged in mainline kernel 5.9
  
https://github.com/torvalds/linux/commit/39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877
  but was not tagged for the stable tree.
  
  This patch provides important performance gains for some workloads using
  dm-crypt / LUKS and cherry-picking it would be very beneficial for dm-
  crypt users. You can find details on the expected gain in the following
  links:
  
  * https://www.redhat.com/archives/dm-devel/2020-July/msg00138.html
  * https://blog.cloudflare.com/speeding-up-linux-disk-encryption/
  
  The patch mostly applies cleanly on the Ubuntu 5.4 kernel, the only
  merge conflict is due to the module version at the end of the patch. I
  can provide a backport patch if needed.
  
  Thanks,

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

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

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

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

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => gerald.yang (gerald-yang-tw)

** Changed in: linux (Ubuntu Groovy)
 Assignee: (unassigned) => gerald.yang (gerald-yang-tw)

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => gerald.yang (gerald-yang-tw)

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

Title:
  Cherry-pick dm-crypt performance improvement patch from Linux 5.9

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

Bug description:
  === SRU Justification ===
  [Impact]
  To get better performance for dm-crypt in some cases, bypass kcryptd 
workqueue can reduce the overhead in context switch between workers, 
cherry-pick commit 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 from mainline 
kernel, and bypass kcryptd workqueue is not enabled by default

  [Fix]
  Add flags to bypass kcryptd workqueue

  [Test]
  create dm-crypt and setup DM_CRYPT_NO_READ_WORKQUEUE and 
DM_CRYPT_NO_WRITE_WORKQUEUE, read/write data and run perf record to see if 
read/write to the encrypted device will bypass kcryptd workqueue

  [Regression Potential]
  Low, this feature is disabled by default, need to enable manually

  = original bug description =
  Hi,

  I'm asking if it would be possible to cherry-pick patch "dm crypt: add
  flags to optionally bypass kcryptd workqueues" into the 5.4 Ubuntu
  kernel. This patch has been merged in mainline kernel 5.9
  
https://github.com/torvalds/linux/commit/39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877
  but was not tagged for the stable tree.

  This patch provides important performance gains for some workloads
  using dm-crypt / LUKS and cherry-picking it would be very beneficial
  for dm-crypt users. You can find details on the expected gain in the
  following links:

  * https://www.redhat.com/archives/dm-devel/2020-July/msg00138.html
  * https://blog.cloudflare.com/speeding-up-linux-disk-encryption/

  The patch mostly applies cleanly on the Ubuntu 5.4 kernel, the only
  merge conflict is due to the module version at the end of the patch. I
  can provide a backport patch if needed.

  Thanks,

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

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

Re: [Kernel-packages] [Bug 1920180] Re: Can't detect intel wifi 6235

2021-05-17 Thread sugianto

Dear Mr. Alex,

Thank you so much for your help and great information. I'm very excited
while wait for it to work.


On Tue, May 11, 2021, 3:05 AM Alex Hung <1920...@bugs.launchpad.net> wrote:

> Updates: the patch was not included in kernel 5.13-rc1 yet but I sent a
> follow-up email and let's see how this goes.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1920180
>
> Title:
>   Can't detect intel wifi 6235
>
> Status in linux package in Ubuntu:
>   In Progress
>
> Bug description:
>   Can't detect Wireless intel advance 6235
>
>   03:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N
> 6235 [8086:088f] (rev 24)
> Subsystem: Intel Corporation Centrino Advanced-N 6235 [8086:526a]
> Flags: fast devsel, IRQ 255
> Memory at e040 (64-bit, non-prefetchable) [size=8K]
> Capabilities: 
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.11-0ubuntu27.16
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  sgo1245 F pulseaudio
>/dev/snd/controlC0:  sgo1245 F pulseaudio
>   CasperMD5CheckResult: skip
>   CurrentDesktop: X-Cinnamon
>   DistroRelease: Linux Mint 20.1
>   InstallationDate: Installed on 2021-03-15 (4 days ago)
>   InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
>   IwConfig:
>enp0s25   no wireless extensions.
>
>lono wireless extensions.
>   MachineType: LENOVO 20AWS0DS0T
>   Package: linux (not installed)
>   ProcFB: 0 i915drmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic
> root=UUID=7bbc36d4-b65d-4291-a3b9-dc840a88f20a ro quiet splash
>   ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94
>   RelatedPackageVersions:
>linux-restricted-modules-5.4.0-67-generic N/A
>linux-backports-modules-5.4.0-67-generic  N/A
>linux-firmware1.187.10
>   RfKill:
>0: tpacpi_bluetooth_sw: Bluetooth
> Soft blocked: yes
> Hard blocked: no
>   Tags:  ulyssa
>   Uname: Linux 5.4.0-67-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 04/20/2020
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: GLETA1WW (2.55 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 20AWS0DS0T
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Defined
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Not Available
>   dmi.modalias:
> dmi:bvnLENOVO:bvrGLETA1WW(2.55):bd04/20/2020:svnLENOVO:pn20AWS0DS0T:pvrThinkPadT440p:rvnLENOVO:rn20AWS0DS0T:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
>   dmi.product.family: ThinkPad T440p
>   dmi.product.name: 20AWS0DS0T
>   dmi.product.sku: LENOVO_MT_20AW_BU_Think_FM_ThinkPad T440p
>   dmi.product.version: ThinkPad T440p
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920180/+subscriptions
>

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

Title:
  Can't detect intel wifi 6235

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Can't detect Wireless intel advance 6235

  03:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6235 
[8086:088f] (rev 24)
Subsystem: Intel Corporation Centrino Advanced-N 6235 [8086:526a]
Flags: fast devsel, IRQ 255
Memory at e040 (64-bit, non-prefetchable) [size=8K]
Capabilities: 
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sgo1245 F pulseaudio
   /dev/snd/controlC0:  sgo1245 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.1
  InstallationDate: Installed on 2021-03-15 (4 days ago)
  InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
  IwConfig:
   enp0s25   no wireless extensions.
   
   lono wireless extensions.
  MachineType: LENOVO 20AWS0DS0T
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic 
root=UUID=7bbc36d4-b65d-4291-a3b9-dc840a88f20a ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-67-generic N/A
   linux-backports-modules-5.4.0-67-generic  N/A
   linux-firmware1.187.10
  RfKill:
   0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: yes
Hard blocked: no
  Tags:  ulyssa
  Uname: Linux 5.4.0-67-generic x86_64
  UpgradeStatus: No upgrade

[Kernel-packages] [Bug 1928600] Re: [amdgpu] Gnome locks up with artifacts on screen

Thanks for that. Next time you experience a lockup, please:

1. Wait 10 seconds.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)

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

-- 
Mailing list: https://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 1928593] Re: Dell Precision 3560: system hang upon resume from s2idle suspend

2021-05-17 Thread koba

@Brian,
would you mind helping me try this cmd? then please s2idle
*echo 0|sudo tee /sys/bus/pci/devices/*/d3cold_allowed

please also provide dmesg. 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/1928593

Title:
  Dell Precision 3560: system hang upon resume from s2idle suspend

Status in linux package in Ubuntu:
  In Progress

Bug description:
  On a Dell Precision 3560 with all-Intel graphics (no Nvidia).  The
  machine will successfully go into s2idle suspend (sleep) but upon
  waking, the system will immediately freeze hard. In its frozen state,
  the mouse pointer will be visible against a black screen.  Here are
  the troubleshooting steps I have taken so far:

  - Can successfully reproduce under Ubuntu 20.04.2 (gdm3), Kubuntu
  20.04.2 (sddm).  For what it's worth, I can also reproduce this under
  Manjaro (stable), so it's conceivable this is a kernel bug.

  - There's some evidence online that this issue, or something similar,
  was introduced in/around kernel 5.6.19 -- I have not been able to get
  Ubuntu to boot under a kernel earlier than 5.8 so I cannot confirm
  this.

  - Updated BIOS to latest (1.6).  'Block sleep' is off. System > SATA
  is 'AHCI'.  Post Behavior > Fastboot is 'Thorough'.  Secure Boot is
  disabled.

  - Determined that this BIOS does not appear to support 'deep' sleep,
  only s2idle.

  - The problem does NOT occur if I boot to an Ubuntu 20.04.2 live USB
  disk.  I compared the drivers that are loaded in that environment vs.
  those that are loaded under the installed OS and did not notice
  anything suspicious.

  
  I am happy to supply any diagnostics or logs that are requested.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brian   916 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-05-16 (0 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Precision 3560
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic 
root=UUID=03c4b3bd-b521-45b0-b01d-cd092ba108bc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-53-generic N/A
   linux-backports-modules-5.8.0-53-generic  N/A
   linux-firmware1.187.12
  Tags:  focal
  Uname: Linux 5.8.0-53-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/19/2021
  dmi.bios.release: 1.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 063MV5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd04/19/2021:br1.6:svnDellInc.:pnPrecision3560:pvr:rvnDellInc.:rn063MV5:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3560
  dmi.product.sku: 0A22
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1912905] Re: Can't find WLAN device on RPI-CM4L with 20.10 armhf preinstall server image

This bug was fixed in the package linux-firmware-raspi2 -
4-0ubuntu0~20.04.1

---
linux-firmware-raspi2 (4-0ubuntu0~20.04.1) focal; urgency=medium

  * Backport to focal (LP: #1925971)
- Add aliases and diversions for brcmfmac43455 configuration on the
  Raspberry Pi Compute Module 4, and 400 (LP: #1912905)

- Added diversions for all wifi firmware blobs (LP: #1918013)
- New upstream boot firmware release, 1.20210303
- New upstream bluetooth firmware release, 1.2-4+rpt8

  [ Phil Elwell ]
  - Second Spectra fix for CYW43455 (CVE-2020-10370)
- Original firmware name: BCM4345C0_003.001.025.0174.0342.hcd

- New upstream wifi firmware release, 1:20190114-1+rpt11

  [ Serge Schneider ]
  - Update CYW43455 firmware
- brcm/brcmfmac43455-sdio.bin 7.45.229
- See: https://github.com/raspberrypi/linux/issues/3849

 -- William 'jawn-smith' Wilson   Fri, 23
Apr 2021 16:05:55 -0500

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

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

Title:
  Can't find WLAN device on RPI-CM4L with 20.10 armhf preinstall server
  image

Status in linux-firmware-raspi2 package in Ubuntu:
  Fix Released
Status in linux-raspi package in Ubuntu:
  Invalid
Status in linux-firmware-raspi2 source package in Focal:
  Fix Released
Status in linux-raspi source package in Focal:
  Invalid
Status in linux-firmware-raspi2 source package in Groovy:
  Fix Released
Status in linux-raspi source package in Groovy:
  Invalid
Status in linux-firmware-raspi2 source package in Hirsute:
  Fix Released
Status in linux-raspi source package in Hirsute:
  Invalid

Bug description:
  [Description]
  Can't find WLAN device on Raspberry Pi CM4L with 20.10 armhf preinstall 
server image.
  This only happens on armhf image.

  [Steps to reproduce]
  1. Flash image 
http://cdimage.ubuntu.com/ubuntu/releases/groovy/release/ubuntu-20.10-preinstalled-server-armhf+raspi.img.xz
  2. Boot into system
  5. Check wireless device using "ip a"

  [Expected result]
  Can't find WLAN device

  [Actual result]
  WLAN device works fine

  [Additional information]
  Hardware: RPI-CM4L
  Kernel Version: 5.8.0-1006-raspi, 5.8.0-1012-raspi, 5.8.0-1013-raspi

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

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

[Kernel-packages] [Bug 1918013] Update Released

2021-05-17 Thread Brian Murray

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

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

Title:
  package linux-firmware 1.194 [modified:
  lib/firmware/brcm/brcmfmac43430-sdio.bin
  lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt
  lib/firmware/brcm/brcmfmac43455-sdio.bin
  lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt
  lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] failed
  to install/upgrade: trying to overwrite
  '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in
  package linux-firmware-raspi2 3-0ubuntu2

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware-raspi2 package in Ubuntu:
  Fix Released
Status in linux-firmware-raspi2 source package in Focal:
  Fix Released
Status in linux-firmware-raspi2 source package in Groovy:
  Fix Released
Status in linux-firmware source package in Hirsute:
  Invalid
Status in linux-firmware-raspi2 source package in Hirsute:
  Fix Released

Bug description:
  [SRU Information]

  [Impact]

  The same file was provided by two packages, causing errors when
  upgrading.

  [Test Case]

  * Boot an ubuntu image on a Raspberry Pi.
  * "sudo apt update"
  * "sudo apt upgrade"
  * Install linux-firmware-raspi2 from -proposed. No errors should occur.

  [Regression Potential]
  If any files are added or removed from either linux-firmware or 
linux-firmware-raspi2 we could see degraded functionality or another error like 
what is reported in this bug.

  [Original Description]

  Upgrade error

  Unpacking linux-firmware (1.195) over (1.194) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-N6i2Cp/86-linux-firmware_1.
  195_all.deb (--unpack):
   trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which 
is
  also in package linux-firmware-raspi2 3-0ubuntu2
  update-initramfs: Generating /boot/initrd.img-5.8.0-1017-raspi

  ProblemType: Package
  DistroRelease: Ubuntu 21.04
  Package: linux-firmware 1.194 [modified: 
lib/firmware/brcm/brcmfmac43430-sdio.bin 
lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt 
lib/firmware/brcm/brcmfmac43455-sdio.bin 
lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt 
lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt]
  ProcVersionSignature: Ubuntu 5.8.0-1017.20+21.04.1-raspi 5.8.18
  Uname: Linux 5.8.0-1017-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dad1239 F pulseaudio
   /dev/snd/pcmC1D0p:   dad1239 F...m pulseaudio
   /dev/snd/controlC0:  dad1239 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat Mar  6 14:59:23 2021
  Dependencies:

  ErrorMessage: trying to overwrite 
'/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package 
linux-firmware-raspi2 3-0ubuntu2
  ImageMediaBuild: 20210302
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  PackageArchitecture: all
  ProcFB: 0 vc4drmfb
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1280x1024M@60 
smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 console=tty1 
root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet 
splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.9, Python 3.9.2, python3-minimal, 3.9.1-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux-firmware
  StagingDrivers: bcm2835_v4l2 bcm2835_isp bcm2835_codec bcm2835_mmal_vchiq 
snd_bcm2835 vc_sm_cma
  Title: package linux-firmware 1.194 [modified: 
lib/firmware/brcm/brcmfmac43430-sdio.bin 
lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt 
lib/firmware/brcm/brcmfmac43455-sdio.bin 
lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt 
lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] failed to 
install/upgrade: trying to overwrite 
'/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package 
linux-firmware-raspi2 3-0ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:

[Kernel-packages] [Bug 1918013] Re: package linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi, 3-model-b.txt lib/firmware/brcm/b

This bug was fixed in the package linux-firmware-raspi2 -
4-0ubuntu0~20.04.1

---
linux-firmware-raspi2 (4-0ubuntu0~20.04.1) focal; urgency=medium

  * Backport to focal (LP: #1925971)
- Add aliases and diversions for brcmfmac43455 configuration on the
  Raspberry Pi Compute Module 4, and 400 (LP: #1912905)

- Added diversions for all wifi firmware blobs (LP: #1918013)
- New upstream boot firmware release, 1.20210303
- New upstream bluetooth firmware release, 1.2-4+rpt8

  [ Phil Elwell ]
  - Second Spectra fix for CYW43455 (CVE-2020-10370)
- Original firmware name: BCM4345C0_003.001.025.0174.0342.hcd

- New upstream wifi firmware release, 1:20190114-1+rpt11

  [ Serge Schneider ]
  - Update CYW43455 firmware
- brcm/brcmfmac43455-sdio.bin 7.45.229
- See: https://github.com/raspberrypi/linux/issues/3849

 -- William 'jawn-smith' Wilson   Fri, 23
Apr 2021 16:05:55 -0500

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

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

Title:
  package linux-firmware 1.194 [modified:
  lib/firmware/brcm/brcmfmac43430-sdio.bin
  lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt
  lib/firmware/brcm/brcmfmac43455-sdio.bin
  lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt
  lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] failed
  to install/upgrade: trying to overwrite
  '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in
  package linux-firmware-raspi2 3-0ubuntu2

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware-raspi2 package in Ubuntu:
  Fix Released
Status in linux-firmware-raspi2 source package in Focal:
  Fix Released
Status in linux-firmware-raspi2 source package in Groovy:
  Fix Released
Status in linux-firmware source package in Hirsute:
  Invalid
Status in linux-firmware-raspi2 source package in Hirsute:
  Fix Released

Bug description:
  [SRU Information]

  [Impact]

  The same file was provided by two packages, causing errors when
  upgrading.

  [Test Case]

  * Boot an ubuntu image on a Raspberry Pi.
  * "sudo apt update"
  * "sudo apt upgrade"
  * Install linux-firmware-raspi2 from -proposed. No errors should occur.

  [Regression Potential]
  If any files are added or removed from either linux-firmware or 
linux-firmware-raspi2 we could see degraded functionality or another error like 
what is reported in this bug.

  [Original Description]

  Upgrade error

  Unpacking linux-firmware (1.195) over (1.194) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-N6i2Cp/86-linux-firmware_1.
  195_all.deb (--unpack):
   trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which 
is
  also in package linux-firmware-raspi2 3-0ubuntu2
  update-initramfs: Generating /boot/initrd.img-5.8.0-1017-raspi

  ProblemType: Package
  DistroRelease: Ubuntu 21.04
  Package: linux-firmware 1.194 [modified: 
lib/firmware/brcm/brcmfmac43430-sdio.bin 
lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt 
lib/firmware/brcm/brcmfmac43455-sdio.bin 
lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt 
lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt]
  ProcVersionSignature: Ubuntu 5.8.0-1017.20+21.04.1-raspi 5.8.18
  Uname: Linux 5.8.0-1017-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dad1239 F pulseaudio
   /dev/snd/pcmC1D0p:   dad1239 F...m pulseaudio
   /dev/snd/controlC0:  dad1239 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat Mar  6 14:59:23 2021
  Dependencies:

  ErrorMessage: trying to overwrite 
'/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package 
linux-firmware-raspi2 3-0ubuntu2
  ImageMediaBuild: 20210302
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  PackageArchitecture: all
  ProcFB: 0 vc4drmfb
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1280x1024M@60 
smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 console=tty1 
root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet 
splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.9, Python 3.9.2, python3-minimal, 3.9.1-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux-firmware
  StagingDrivers: bcm2835_v4l2 bcm2835_isp bcm2835_codec bcm2835_mmal_vchiq 
snd_bcm2835

[Kernel-packages] [Bug 1912905] Re: Can't find WLAN device on RPI-CM4L with 20.10 armhf preinstall server image

This bug was fixed in the package linux-firmware-raspi2 -
4-0ubuntu0~20.10.1

---
linux-firmware-raspi2 (4-0ubuntu0~20.10.1) groovy; urgency=medium

  * Pull in latest from hirsute (LP: #1925971)
- Add aliases and diversions for brcmfmac43455 configuration on the
  Raspberry Pi Compute Module 4, and 400 (LP: #1912905)

- Added diversions for all wifi firmware blobs (LP: #1918013)
- New upstream boot firmware release, 1.20210303
- New upstream bluetooth firmware release, 1.2-4+rpt8

  [ Phil Elwell ]
  - Second Spectra fix for CYW43455 (CVE-2020-10370)
- Original firmware name: BCM4345C0_003.001.025.0174.0342.hcd

- New upstream wifi firmware release, 1:20190114-1+rpt11

  [ Serge Schneider ]
  - Update CYW43455 firmware
- brcm/brcmfmac43455-sdio.bin 7.45.229
- See: https://github.com/raspberrypi/linux/issues/3849

 -- William 'jawn-smith' Wilson   Fri, 23
Apr 2021 16:05:55 -0500

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

** Bug watch added: github.com/raspberrypi/linux/issues #3849
   https://github.com/raspberrypi/linux/issues/3849

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

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

Title:
  Can't find WLAN device on RPI-CM4L with 20.10 armhf preinstall server
  image

Status in linux-firmware-raspi2 package in Ubuntu:
  Fix Released
Status in linux-raspi package in Ubuntu:
  Invalid
Status in linux-firmware-raspi2 source package in Focal:
  Fix Released
Status in linux-raspi source package in Focal:
  Invalid
Status in linux-firmware-raspi2 source package in Groovy:
  Fix Released
Status in linux-raspi source package in Groovy:
  Invalid
Status in linux-firmware-raspi2 source package in Hirsute:
  Fix Released
Status in linux-raspi source package in Hirsute:
  Invalid

Bug description:
  [Description]
  Can't find WLAN device on Raspberry Pi CM4L with 20.10 armhf preinstall 
server image.
  This only happens on armhf image.

  [Steps to reproduce]
  1. Flash image 
http://cdimage.ubuntu.com/ubuntu/releases/groovy/release/ubuntu-20.10-preinstalled-server-armhf+raspi.img.xz
  2. Boot into system
  5. Check wireless device using "ip a"

  [Expected result]
  Can't find WLAN device

  [Actual result]
  WLAN device works fine

  [Additional information]
  Hardware: RPI-CM4L
  Kernel Version: 5.8.0-1006-raspi, 5.8.0-1012-raspi, 5.8.0-1013-raspi

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

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

[Kernel-packages] [Bug 1918013] Re: package linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi, 3-model-b.txt lib/firmware/brcm/b

This bug was fixed in the package linux-firmware-raspi2 -
4-0ubuntu0~20.10.1

---
linux-firmware-raspi2 (4-0ubuntu0~20.10.1) groovy; urgency=medium

  * Pull in latest from hirsute (LP: #1925971)
- Add aliases and diversions for brcmfmac43455 configuration on the
  Raspberry Pi Compute Module 4, and 400 (LP: #1912905)

- Added diversions for all wifi firmware blobs (LP: #1918013)
- New upstream boot firmware release, 1.20210303
- New upstream bluetooth firmware release, 1.2-4+rpt8

  [ Phil Elwell ]
  - Second Spectra fix for CYW43455 (CVE-2020-10370)
- Original firmware name: BCM4345C0_003.001.025.0174.0342.hcd

- New upstream wifi firmware release, 1:20190114-1+rpt11

  [ Serge Schneider ]
  - Update CYW43455 firmware
- brcm/brcmfmac43455-sdio.bin 7.45.229
- See: https://github.com/raspberrypi/linux/issues/3849

 -- William 'jawn-smith' Wilson   Fri, 23
Apr 2021 16:05:55 -0500

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

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

Title:
  package linux-firmware 1.194 [modified:
  lib/firmware/brcm/brcmfmac43430-sdio.bin
  lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt
  lib/firmware/brcm/brcmfmac43455-sdio.bin
  lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt
  lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] failed
  to install/upgrade: trying to overwrite
  '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in
  package linux-firmware-raspi2 3-0ubuntu2

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware-raspi2 package in Ubuntu:
  Fix Released
Status in linux-firmware-raspi2 source package in Focal:
  Fix Released
Status in linux-firmware-raspi2 source package in Groovy:
  Fix Released
Status in linux-firmware source package in Hirsute:
  Invalid
Status in linux-firmware-raspi2 source package in Hirsute:
  Fix Released

Bug description:
  [SRU Information]

  [Impact]

  The same file was provided by two packages, causing errors when
  upgrading.

  [Test Case]

  * Boot an ubuntu image on a Raspberry Pi.
  * "sudo apt update"
  * "sudo apt upgrade"
  * Install linux-firmware-raspi2 from -proposed. No errors should occur.

  [Regression Potential]
  If any files are added or removed from either linux-firmware or 
linux-firmware-raspi2 we could see degraded functionality or another error like 
what is reported in this bug.

  [Original Description]

  Upgrade error

  Unpacking linux-firmware (1.195) over (1.194) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-N6i2Cp/86-linux-firmware_1.
  195_all.deb (--unpack):
   trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which 
is
  also in package linux-firmware-raspi2 3-0ubuntu2
  update-initramfs: Generating /boot/initrd.img-5.8.0-1017-raspi

  ProblemType: Package
  DistroRelease: Ubuntu 21.04
  Package: linux-firmware 1.194 [modified: 
lib/firmware/brcm/brcmfmac43430-sdio.bin 
lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt 
lib/firmware/brcm/brcmfmac43455-sdio.bin 
lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt 
lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt]
  ProcVersionSignature: Ubuntu 5.8.0-1017.20+21.04.1-raspi 5.8.18
  Uname: Linux 5.8.0-1017-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dad1239 F pulseaudio
   /dev/snd/pcmC1D0p:   dad1239 F...m pulseaudio
   /dev/snd/controlC0:  dad1239 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat Mar  6 14:59:23 2021
  Dependencies:

  ErrorMessage: trying to overwrite 
'/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package 
linux-firmware-raspi2 3-0ubuntu2
  ImageMediaBuild: 20210302
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  PackageArchitecture: all
  ProcFB: 0 vc4drmfb
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1280x1024M@60 
smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 console=tty1 
root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet 
splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.9, Python 3.9.2, python3-minimal, 3.9.1-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux-firmware
  StagingDrivers: bcm2835_v4l2 bcm2835_isp bcm2835_codec bcm2835_mmal_vchiq

[Kernel-packages] [Bug 1928601] Re: Ubuntu fails to start by default after upgrade 18.04 to 20.04 in virtual machine

2021-05-17 Thread Reijo Korhonen

I can run 'apport-collect 1928601' in the virtual machine, if I boot
using series-4 kernel, but does it give any information why series-5
kernel panics? Please tell if helps, if I run apport-collect 1928601' in
series-4 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/1928601

Title:
  Ubuntu fails to start by default after upgrade 18.04 to 20.04 in
  virtual machine

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading virtual machine from Ubuntu 18.04 to 20.04 it fails to
  boot with kernel panic to run 5-series kernel, which is default in
  20.04, but can run 4-series kernel, which comes with Ubuntu 18.04.
  Tested with Microsoft's Hyper-V and Ubuntu's libvirt qemu. Results are
  identical.

  More information https://askubuntu.com/questions/1338236/ubuntu-fails-
  to-start-by-default-after-upgrade-18-04-to-20-04/1338722#1338722

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

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

[Kernel-packages] [Bug 1928601] Re: Ubuntu fails to start by default after upgrade 18.04 to 20.04 in virtual machine

2021-05-17 Thread Reijo Korhonen

When virtual machine's kernel panics in the boot, it not possiblr run
apport-collect 1928601 any more, I'm afraid.

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

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

Title:
  Ubuntu fails to start by default after upgrade 18.04 to 20.04 in
  virtual machine

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading virtual machine from Ubuntu 18.04 to 20.04 it fails to
  boot with kernel panic to run 5-series kernel, which is default in
  20.04, but can run 4-series kernel, which comes with Ubuntu 18.04.
  Tested with Microsoft's Hyper-V and Ubuntu's libvirt qemu. Results are
  identical.

  More information https://askubuntu.com/questions/1338236/ubuntu-fails-
  to-start-by-default-after-upgrade-18-04-to-20-04/1338722#1338722

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

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

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

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

apport-collect 1928601

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

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

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

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

** Tags added: bionic

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

Title:
  Ubuntu fails to start by default after upgrade 18.04 to 20.04 in
  virtual machine

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When upgrading virtual machine from Ubuntu 18.04 to 20.04 it fails to
  boot with kernel panic to run 5-series kernel, which is default in
  20.04, but can run 4-series kernel, which comes with Ubuntu 18.04.
  Tested with Microsoft's Hyper-V and Ubuntu's libvirt qemu. Results are
  identical.

  More information https://askubuntu.com/questions/1338236/ubuntu-fails-
  to-start-by-default-after-upgrade-18-04-to-20-04/1338722#1338722

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

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

[Kernel-packages] [Bug 1928601] Re: Ubuntu fails to start by default after upgrade 18.04 to 20.04 in virtual machine

2021-05-17 Thread Brian Murray

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

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

Title:
  Ubuntu fails to start by default after upgrade 18.04 to 20.04 in
  virtual machine

Status in linux package in Ubuntu:
  New

Bug description:
  When upgrading virtual machine from Ubuntu 18.04 to 20.04 it fails to
  boot with kernel panic to run 5-series kernel, which is default in
  20.04, but can run 4-series kernel, which comes with Ubuntu 18.04.
  Tested with Microsoft's Hyper-V and Ubuntu's libvirt qemu. Results are
  identical.

  More information https://askubuntu.com/questions/1338236/ubuntu-fails-
  to-start-by-default-after-upgrade-18-04-to-20-04/1338722#1338722

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

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

[Kernel-packages] [Bug 1928601] [NEW] Ubuntu fails to start by default after upgrade 18.04 to 20.04 in virtual machine

You have been subscribed to a public bug:

When upgrading virtual machine from Ubuntu 18.04 to 20.04 it fails to
boot with kernel panic to run 5-series kernel, which is default in
20.04, but can run 4-series kernel, which comes with Ubuntu 18.04.
Tested with Microsoft's Hyper-V and Ubuntu's libvirt qemu. Results are
identical.

More information https://askubuntu.com/questions/1338236/ubuntu-fails-
to-start-by-default-after-upgrade-18-04-to-20-04/1338722#1338722

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


** Tags: bot-comment hyper-v libvirt qemu
-- 
Ubuntu fails to start by default after upgrade 18.04 to 20.04 in virtual machine
https://bugs.launchpad.net/bugs/1928601
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 1928715] Re: Debugging symbols (dbgsym) packages are missing GDB kernel scripts

2021-05-17 Thread Krzysztof Kozlowski

** Description changed:

  [Impact]
  
-  * Linux kernel comes with useful GDB scripts under scripts/gdb.
-  * These bring new commands helping in debugging like lx-clk-summary, 
lx-cpus, lx-device-list-tree, lx-genpd-summary, lx-symbols, lx-timerlist and 
more
-  * It would be useful to have them installed in dbgsym package.
+  * Linux kernel comes with useful GDB scripts under scripts/gdb.
+  * These bring new commands helping in debugging like lx-clk-summary, 
lx-cpus, lx-device-list-tree, lx-genpd-summary, lx-symbols, lx-timerlist and 
more
+  * It would be useful to have them installed in dbgsym package.
  
  [Test Plan]
  
-  * Build package with and without skipdbg.
-  * Check if GDB scripts are installed in /usr/lib/debug/share
+  * Build package with and without skipdbg.
+  * Check if GDB scripts are installed in /usr/lib/debug/share
  
  [Where problems could occur]
  
- * This is packaging and Makefile change, so no particular runtime issues
- expected.
+  * This is packaging and Makefile change, so no particular runtime issues 
expected. Most likely any problem will be build time.
+  * Wrong packaging could lead to missing files in dbgsym package.

** Also affects: linux (Ubuntu Impish)
   Importance: Undecided
 Assignee: Krzysztof Kozlowski (krzk)
   Status: Incomplete

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

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

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

** Changed in: linux (Ubuntu Hirsute)
 Assignee: (unassigned) => Krzysztof Kozlowski (krzk)

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Krzysztof Kozlowski (krzk)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Krzysztof Kozlowski (krzk)

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

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

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

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

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

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

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

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

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

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

Title:
  Debugging symbols (dbgsym) packages are missing GDB kernel scripts

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux source package in Impish:
  In Progress

Bug description:
  [Impact]

   * Linux kernel comes with useful GDB scripts under scripts/gdb.
   * These bring new commands helping in debugging like lx-clk-summary, 
lx-cpus, lx-device-list-tree, lx-genpd-summary, lx-symbols, lx-timerlist and 
more
   * It would be useful to have them installed in dbgsym package.

  [Test Plan]

   * Build package with and without skipdbg.
   * Check if GDB scripts are installed in /usr/lib/debug/share

  [Where problems could occur]

   * This is packaging and Makefile change, so no particular runtime issues 
expected. Most likely any problem will be build time.
   * Wrong packaging could lead to missing files in dbgsym package.

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

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

[Kernel-packages] [Bug 1928522] Re: seccomp_bpf from ubuntu_kernel_selftests.seccomp in linux ADT test failure with linux/4.15.0-144.148

2021-05-17 Thread Thadeu Lima de Souza Cascardo

01:54:40 ERROR| [stderr] 
seccomp_bpf.c:1902:TRACE_syscall.syscall_faked:Expected 45000 (45000) == 
syscall(236) (18446744073709551615)
01:54:40 ERROR| [stderr] TRACE_syscall.syscall_faked: Test failed at step #11

This fails after the fix for LP: #1895132. However, this is not a
regression. s390x ptrace does not support changing the syscall return
code and the other way was not expected by strace (so tests for that one
were failing).

We have not been running this test on s390x since after 4.18. After an
effort to get that fixed on ppc64el (because it also has some different
behaviors, like only able to set syscall return code at exit time),
there was some restructure of the test.

Applying that patchset would allow us to get s390x test back to work on
4.15 kernels, and also start running it on 5.4 and later kernels.

Cascardo.

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

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

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

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

** Also affects: linux (Ubuntu Impish)
   Importance: Undecided
   Status: Incomplete

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

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

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

Title:
  seccomp_bpf from ubuntu_kernel_selftests.seccomp in linux ADT test
  failure with linux/4.15.0-144.148

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  New
Status in linux source package in Focal:
  New
Status in linux source package in Groovy:
  New
Status in linux source package in Hirsute:
  Fix Released
Status in linux source package in Impish:
  Fix Released

Bug description:
  This is a scripted bug report about ADT failures while running linux
  tests for linux/4.15.0-144.148 on bionic. Whether this is caused by
  the dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/l/linux/20210514_022345_e6f3c@/log.gz

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

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

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

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

apport-collect 1928715

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

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

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

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

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

Title:
  Debugging symbols (dbgsym) packages are missing GDB kernel scripts

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

   * Linux kernel comes with useful GDB scripts under scripts/gdb.
   * These bring new commands helping in debugging like lx-clk-summary, 
lx-cpus, lx-device-list-tree, lx-genpd-summary, lx-symbols, lx-timerlist and 
more
   * It would be useful to have them installed in dbgsym package.

  [Test Plan]

   * Build package with and without skipdbg.
   * Check if GDB scripts are installed in /usr/lib/debug/share

  [Where problems could occur]

  * This is packaging and Makefile change, so no particular runtime
  issues expected.

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

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

[Kernel-packages] [Bug 1928715] [NEW] Debugging symbols (dbgsym) packages are missing GDB kernel scripts

2021-05-17 Thread Krzysztof Kozlowski

Public bug reported:

[Impact]

 * Linux kernel comes with useful GDB scripts under scripts/gdb.
 * These bring new commands helping in debugging like lx-clk-summary, lx-cpus, 
lx-device-list-tree, lx-genpd-summary, lx-symbols, lx-timerlist and more
 * It would be useful to have them installed in dbgsym package.

[Test Plan]

 * Build package with and without skipdbg.
 * Check if GDB scripts are installed in /usr/lib/debug/share

[Where problems could occur]

* This is packaging and Makefile change, so no particular runtime issues
expected.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Krzysztof Kozlowski (krzk)
 Status: New

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Krzysztof Kozlowski (krzk)

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

Title:
  Debugging symbols (dbgsym) packages are missing GDB kernel scripts

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]

   * Linux kernel comes with useful GDB scripts under scripts/gdb.
   * These bring new commands helping in debugging like lx-clk-summary, 
lx-cpus, lx-device-list-tree, lx-genpd-summary, lx-symbols, lx-timerlist and 
more
   * It would be useful to have them installed in dbgsym package.

  [Test Plan]

   * Build package with and without skipdbg.
   * Check if GDB scripts are installed in /usr/lib/debug/share

  [Where problems could occur]

  * This is packaging and Makefile change, so no particular runtime
  issues expected.

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

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

[Kernel-packages] [Bug 1896482] Re: acpi event detection crashes

2021-05-17 Thread Gerald Gilbert-Thorple

Unfortunately it looks like the bug did not disappear.  I have it
starting around 45 minutes after booting in the kernel we thought was
good, 5.4.0-52-generic_5.4.0-52.57.  Unless I somehow screwed up and
reinstalled a broken 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/1896482

Title:
  acpi event detection crashes

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

Bug description:
  = SRU Justification =

  [Impact]

  The bug causes the EC driver to fail and ACPI events are no longer
  handled by Linux kernel, i.e lid close no longer triggers suspends.

  [Fix]

  Upstream commit 03e9a0e05739cf reworks ec_install_handlers to avoid
  initialisation failures.

  The other three patches are prerequisite to apply 03e9a0e05739cf on
  focal kernel.

  [Test]

  Tested with Lenovo ThinkPad X1 Carbon Gen 8

  [Regression Potential]

  Low. The patches were cherry-picked from mainline kernel (two since 5.5
  and two since 5.7)

  = Original Bug Report =

  Right after booting, acpi lid open/close is detected as it should be
  by the kernel, but some time later it crashes, so I have to manually
  suspend the system.  The traceback is here:

  Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here 
]
  Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at 
kernel/workqueue.c:1416 __queue_work+0x337/0x3f0
  Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm 
cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp 
snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic 
snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal 
intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common 
snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt 
snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus 
snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel 
aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec 
glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep 
snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm 
videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw 
btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwifi 
processor_thermal_device bluetooth videodev
  Sep 20 11:35:33 laxmi kernel: [232492.303600]  drm_kms_helper mc wmi_bmof 
i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt 
ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch 
snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf typec 
snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad intel_hid 
int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel parport_pc 
ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul nvme 
psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci intel_lpss nvme_core idma64 
virt_dma i2c_hid hid wmi video pinctrl_cannonlake pinctrl_intel
  Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: 
kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu
  Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO 
20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020
  Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query 
acpi_ec_event_processor
  Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: 
0010:__queue_work+0x337/0x3f0
  Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 
e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b 
01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 
0b e9 fd fd
  Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 
EFLAGS: 00010087
  Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: 
0002 RCX: 0004
  Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: 
9a2475b03200 RDI: 9a2430215f00
  Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: 
 R09: 0007
  Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: 
 R12: 9a2475af4a00
  Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: 
2000 R15: 9a2475af4a90
  Sep 20 11:35:33 laxmi kernel: [232492.303645] FS:  () 
GS:9a247740() knlGS:
  Sep 20 11:35:33 laxmi kernel: [232492.303646] CS:  0010 DS:  ES:  
CR0: 80050033
  Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: 
00018520a003 CR4: 003606f0
  Sep 20 11:35:33 laxmi kernel:

[Kernel-packages] [Bug 1928594] Re: Setting up encrypted swap causes ordering cycle

2021-05-17 Thread Vasya Pupkin

While zfs-linux indeed triggers the issue, the root cause, I believe, is
that automatically generated service systemd-cryptsetup@cswap wants to
start after systemd-random-seed, even though it uses /dev/urandom which
shouldn't require random seed data initialized. Also please note that in
this particular case zfs partition is not root.

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

Title:
  Setting up encrypted swap causes ordering cycle

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  root@home:~# cat /etc/crypttab
  # 
  cswap /dev/disk/by-partuuid/95605326-e210-4e13-9f93-50cc3d556aca /dev/urandom 
cipher=aes-xts-plain64,size=256,hash=sha1,swap

  root@home:~# update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-73-generic
  cryptsetup: WARNING: Resume target cswap uses a key file

  After reboot:

  root@home:~# systemctl status systemd-random-seed.service
  ● systemd-random-seed.service - Load/Save Random Seed
   Loaded: loaded (/lib/systemd/system/systemd-random-seed.service; static; 
vendor preset: enabled)
   Active: inactive (dead)
 Docs: man:systemd-random-seed.service(8)
   man:random(4)

  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on cryptsetup.target/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on systemd-cryptsetup@cswap.service/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Job 
systemd-random-seed.service/start deleted to break ordering cycle starting with 
systemd-cryptsetup@cswap.service/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
ordering cycle on systemd-random-seed.service/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on zfs-mount.service/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on zfs-import.target/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on zfs-import-cache.service/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on cryptsetup.target/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on systemd-cryptsetup@cswap.service/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Job 
systemd-random-seed.service/start deleted to break ordering cycle starting with 
systemd-cryptsetup@cswap.service/start

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/efi.img
  CasperMD5CheckResult: fail
  Date: Sun May 16 18:40:45 2021
  InstallationDate: Installed on 2021-01-21 (115 days ago)
  InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
   |__ Port 6: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   SHELL=/bin/bash
   LANG=C.UTF-8
   TERM=screen.xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic 
root=UUID=7c964d4b-ef4d-40df-b297-631e4233f297 ro bootdegraded=true 
transparent_hugepage=never
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3801
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-E:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be

[Kernel-packages] [Bug 1928710] [NEW] ubuntu server 20.04 LTS for ARM64 on Raspberry Pi4 could not handle more than 32 USB3 devices

2021-05-17 Thread Ye He

Public bug reported:

When I connect a 16 port USB3 hub to one of the USB3 ports on the Pi4
(4GB or 8GB ram model), and then plug in external powered hard drives
into the hub, when I reach the sixth or seventh or maximum 8th drive, OS
complains xHCI max limit of 32 has been reached.   I have a keyboard, no
mouse, I'm not sure why it's already 32 USB devices.

I was hoping I could connect 2 such 16port usb hubs to the 2 usb3 ports
on the Pi4, and connect 32 externally powered hard drives to the Pi4.

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

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

Title:
  ubuntu server 20.04 LTS for ARM64 on Raspberry Pi4 could not handle
  more than 32 USB3 devices

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  When I connect a 16 port USB3 hub to one of the USB3 ports on the Pi4
  (4GB or 8GB ram model), and then plug in external powered hard drives
  into the hub, when I reach the sixth or seventh or maximum 8th drive,
  OS complains xHCI max limit of 32 has been reached.   I have a
  keyboard, no mouse, I'm not sure why it's already 32 USB devices.

  I was hoping I could connect 2 such 16port usb hubs to the 2 usb3
  ports on the Pi4, and connect 32 externally powered hard drives to the
  Pi4.

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

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

[Kernel-packages] [Bug 1928700] Re: new postinst hook requires initramfs-tools

2021-05-17 Thread Stefan Bader

** Description changed:

- The new postinst hook from bug 1877088 currently requires initramfs-
- tools installed, or installing a kernel would fail. This happens for me
- on a builder chroot trying to build linux-meta of a derivative kernel.
+ [SRU Justification]
  
- The fix would be to skip running the script if update-initramfs is not
- available.
+ == Impact ==
+ The new postinst hook from bug 1877088 currently requires initramfs-tools 
installed, or installing a kernel would fail. This happens for me on a builder 
chroot trying to build linux-meta of a derivative kernel.
+ 
+ == Fix ==
+ The fix would be to skip running the script if update-initramfs is not 
available. The check was taken from the /etc/kernel/postinst.d/initramfs-tools 
script which has exactly that check at the beginning.
+ 
+ == Testcase ==
+ Building linux-meta in a sbuild chroot which should again work without the 
messages about verifying links. Reinstalling a kernel on a system with 
update-initramfs existing should still print the messages.
+ 
+ == Regression Potential ==
+ Systems with update-initramfs installed and initrd files might for some 
reason again fail to fix missing links.

** Changed in: linux-base (Ubuntu Bionic)
 Assignee: (unassigned) => Stefan Bader (smb)

** Changed in: linux-base (Ubuntu Focal)
 Assignee: (unassigned) => Stefan Bader (smb)

** Changed in: linux-base (Ubuntu Hirsute)
 Assignee: (unassigned) => Stefan Bader (smb)

** Changed in: linux-base (Ubuntu Impish)
 Assignee: (unassigned) => Stefan Bader (smb)

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

Title:
  new postinst hook requires initramfs-tools

Status in linux-base package in Ubuntu:
  Triaged
Status in linux-base source package in Bionic:
  Triaged
Status in linux-base source package in Focal:
  Triaged
Status in linux-base source package in Hirsute:
  Triaged
Status in linux-base source package in Impish:
  Triaged

Bug description:
  [SRU Justification]

  == Impact ==
  The new postinst hook from bug 1877088 currently requires initramfs-tools 
installed, or installing a kernel would fail. This happens for me on a builder 
chroot trying to build linux-meta of a derivative kernel.

  == Fix ==
  The fix would be to skip running the script if update-initramfs is not 
available. The check was taken from the /etc/kernel/postinst.d/initramfs-tools 
script which has exactly that check at the beginning.

  == Testcase ==
  Building linux-meta in a sbuild chroot which should again work without the 
messages about verifying links. Reinstalling a kernel on a system with 
update-initramfs existing should still print the messages.

  == Regression Potential ==
  Systems with update-initramfs installed and initrd files might for some 
reason again fail to fix missing links.

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

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

[Kernel-packages] [Bug 1928595] Re: cheese camera app not display anything

2021-05-17 Thread andrew g

here is the info: HP Truevision HD: HP Truevision (usb-:00:1d.0-1.5):
/dev/video0
/dev/video1

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

Title:
  cheese camera app not display anything

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  when opening the cheese camera app nothing is displayed it shows
  nothing just a black screen on my end tested on Ubuntu 21.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: cheese 3.38.0-3
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 11:46:58 2021
  InstallationDate: Installed on 2021-05-14 (2 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Hewlett-Packard HP 15 TS Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   cheese3.38.0-3
   cheese-common 3.38.0-3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/24/2014
  dmi.bios.release: 15.22
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2211
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.26
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 86.26
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 TS Notebook PC
  dmi.product.sku: G9D75UA#ABA
  dmi.product.version: 097412405F0620180
  dmi.sys.vendor: Hewlett-Packard
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  familypc   1357 F pulseaudio
   /dev/snd/controlC0:  familypc   1357 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-05-14 (2 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Hewlett-Packard HP 15 TS Notebook PC
  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.11.0-17-generic 
root=UUID=c4c005df-0176-4582-a70b-d2a43dc51b21 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  hirsute wayland-session
  Uname: Linux 5.11.0-17-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: 04/24/2014
  dmi.bios.release: 15.22
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2211
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.26
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 86.26
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP 15 TS Notebook PC
  dmi.product.sku: G9D75UA#ABA
  dmi.product.version: 097412405F0620180
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1925685] Re: [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer

2021-05-17 Thread Erich Eickmeyer 

Installed and ran on systems containing issue. Kernel seemed to work
flawlessly. We are going to roll with this kernel and resume sales of
our systems.

** Tags removed: verification-needed-focal
** Tags added: verification-done-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/1925685

Title:
  [SRU] Patch for flicker and glitching on common LCD display panels,
  intel framebuffer

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Won't Fix
Status in linux-hwe-5.8 source package in Bionic:
  Confirmed
Status in linux-oem-5.10 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-hwe-5.8 source package in Focal:
  Confirmed
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Confirmed
Status in linux-hwe-5.8 source package in Groovy:
  Confirmed
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  Confirmed
Status in linux-hwe-5.8 source package in Hirsute:
  Confirmed
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Confirmed
Status in linux-hwe-5.8 source package in Impish:
  Confirmed
Status in linux-oem-5.10 source package in Impish:
  Invalid

Bug description:
  Filing this with my Kubuntu Focus (kfocus.org) OEM hat on:

  [Impact]

  We are having screen flickering and glitching issues with some of our
  hardware upon wake from suspend. We have worked with our ODM to figure
  out a fix for this. They had reported there were no issues when
  running Windows on the same hardware. As such, we tested, and found
  that this issue first began as a regression in kernel 5.0 (did not
  exist in kernel 4.18 per our tests).

  We identified a patch via
  https://gitlab.freedesktop.org/drm/intel/-/issues/272 in which this
  has been solved. Per our testing by recompiling the kernel, this
  completely fixes our hardware issue. As of 4-21, this fix has been
  merged into the Linux kernel per Timo Aaltonen, and will be included
  in the kernel in the 5.13 release.

  Our hardware ships with Kubuntu 20.04 LTS, which means the 5.13 kernel
  will not see these machines, at least in the forseeable future. As
  such, we request that this patch be added to the kernel. Per our
  testing, this patch is straightforward to add and works flawlessly.

  The patch that works best was created in collaboration with Kai-Heng
  Feng, is attached to this bug report, and can be found here:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+attachment/5491421/+files
  /drm-intel-both.patch

  Until this is fixed, we have a whole batch of hardware we cannot sell,
  so, as an OEM, this is a high priority.

  [Test Plan]

   * Install Kubuntu on an affected Kubuntu Focus M2 computer (not in
  the hands of customers at this time)

   * Notice screen glitching/flickering after wake-from-suspend.

   * Install kernel compiled with the attached patch. Boot from patched
  kernel.

   * Suspend laptop, resume. No glitches.

  [Where problems could occur]

   * Although this solves the problem for us and has been confirmed to
  work with the Intel developers that developed this patch, it could
  cause another display type to have problems. This is unlikely as it
  has been vetted by Intel and by the mainline Linux kernel developers.

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

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

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

This change was made by a bot.

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

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

Title:
  21.04 - Bay Trail - Annoying Graphic Artifacts

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I used Kubuntu 20.10, then migrated to 21.04. [This
  bug](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624)
  appeared in kernel version 5.8.0-49. When upgrading to 21.04, it
  remained in version 5.11.0-17-generic. Today's fix did not help.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-17-generic 5.11.0-17.18
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  danil   772 F pulseaudio
   /dev/snd/pcmC0D0c:   danil   772 F...m pulseaudio
   /dev/snd/pcmC0D0p:   danil   772 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Mon May 17 19:14:10 2021
  InstallationDate: Installed on 2021-05-09 (8 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Notebook W54_W94_W955TU,-T,-C
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=e9593473-516a-4042-9484-7d37f7ba6129 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  StagingDrivers: atomisp_gmin_platform atomisp_lm3554
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/13/2015
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W54_W94_W955TU,-T,-C
  dmi.board.vendor: Notebook
  dmi.board.version: V1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd03/13/2015:br5.6:svnNotebook:pnW54_W94_W955TU,-T,-C:pvrNotApplicable:rvnNotebook:rnW54_W94_W955TU,-T,-C:rvrV1.0:cvnNotebook:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W54_W94_W955TU,-T,-C
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Kernel-packages] [Bug 1928702] Re: 21.04 - Bay Trail - Annoying Graphic Artifacts

2021-05-17 Thread Danil Alexeev

** Attachment added: "bug.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928702/+attachment/5498297/+files/bug.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/1928702

Title:
  21.04 - Bay Trail - Annoying Graphic Artifacts

Status in linux package in Ubuntu:
  New

Bug description:
  I used Kubuntu 20.10, then migrated to 21.04. [This
  bug](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624)
  appeared in kernel version 5.8.0-49. When upgrading to 21.04, it
  remained in version 5.11.0-17-generic. Today's fix did not help.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-17-generic 5.11.0-17.18
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  danil   772 F pulseaudio
   /dev/snd/pcmC0D0c:   danil   772 F...m pulseaudio
   /dev/snd/pcmC0D0p:   danil   772 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Mon May 17 19:14:10 2021
  InstallationDate: Installed on 2021-05-09 (8 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Notebook W54_W94_W955TU,-T,-C
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=e9593473-516a-4042-9484-7d37f7ba6129 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  StagingDrivers: atomisp_gmin_platform atomisp_lm3554
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/13/2015
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W54_W94_W955TU,-T,-C
  dmi.board.vendor: Notebook
  dmi.board.version: V1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd03/13/2015:br5.6:svnNotebook:pnW54_W94_W955TU,-T,-C:pvrNotApplicable:rvnNotebook:rnW54_W94_W955TU,-T,-C:rvrV1.0:cvnNotebook:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W54_W94_W955TU,-T,-C
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Kernel-packages] [Bug 1928702] [NEW] 21.04 - Bay Trail - Annoying Graphic Artifacts

2021-05-17 Thread Danil Alexeev

Public bug reported:

I used Kubuntu 20.10, then migrated to 21.04. [This
bug](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624)
appeared in kernel version 5.8.0-49. When upgrading to 21.04, it
remained in version 5.11.0-17-generic. Today's fix did not help.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-17-generic 5.11.0-17.18
ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
Uname: Linux 5.11.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  danil   772 F pulseaudio
 /dev/snd/pcmC0D0c:   danil   772 F...m pulseaudio
 /dev/snd/pcmC0D0p:   danil   772 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Mon May 17 19:14:10 2021
InstallationDate: Installed on 2021-05-09 (8 days ago)
InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: Notebook W54_W94_W955TU,-T,-C
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=e9593473-516a-4042-9484-7d37f7ba6129 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-17-generic N/A
 linux-backports-modules-5.11.0-17-generic  N/A
 linux-firmware 1.197
SourcePackage: linux
StagingDrivers: atomisp_gmin_platform atomisp_lm3554
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/13/2015
dmi.bios.release: 5.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W54_W94_W955TU,-T,-C
dmi.board.vendor: Notebook
dmi.board.version: V1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd03/13/2015:br5.6:svnNotebook:pnW54_W94_W955TU,-T,-C:pvrNotApplicable:rvnNotebook:rnW54_W94_W955TU,-T,-C:rvrV1.0:cvnNotebook:ct10:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: W54_W94_W955TU,-T,-C
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook

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


** Tags: amd64 apport-bug hirsute staging

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

Title:
  21.04 - Bay Trail - Annoying Graphic Artifacts

Status in linux package in Ubuntu:
  New

Bug description:
  I used Kubuntu 20.10, then migrated to 21.04. [This
  bug](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624)
  appeared in kernel version 5.8.0-49. When upgrading to 21.04, it
  remained in version 5.11.0-17-generic. Today's fix did not help.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-17-generic 5.11.0-17.18
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  danil   772 F pulseaudio
   /dev/snd/pcmC0D0c:   danil   772 F...m pulseaudio
   /dev/snd/pcmC0D0p:   danil   772 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Mon May 17 19:14:10 2021
  InstallationDate: Installed on 2021-05-09 (8 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Notebook W54_W94_W955TU,-T,-C
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=e9593473-516a-4042-9484-7d37f7ba6129 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  StagingDrivers: atomisp_gmin_platform atomisp_lm3554
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/13/2015
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W54_W94_W955TU,-T,-C
  dmi.board.vendor: Notebook
  dmi.board.version: V1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd03/13/2015:br5.6:svnNotebook:pnW54_W94_W955TU,-T,-C:pvrNotApplicable:rvnNotebook:rnW54_W94_W955TU,-T,-C:rvrV1.0:cvnNotebook:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W54_W94_W955TU,-T,-C
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this

[Kernel-packages] [Bug 1922754] Re: Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output

2021-05-17 Thread Werner Sembach

Testing done:
The proposed kernels are fixing the bug.

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

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

Title:
  Make AMD gpus choose YCbCr420 encoding automatically when required for
  4k 60Hz output

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  SRU Justification:

  Impact:
  On some setups, while the monitor and the gpu support display modes with 
pixel clocks of up to 600MHz, the link encoder might not. This prevents 
YCbCr444 and RGB encoding for 4k60Hz, but YCbCr420 encoding might still be 
possible. However, which color mode is used is decided before the link encoder 
capabilities are checked, causing the check to fail and discarding 4k60Hz from 
the list of possible display modes.

  Fix:
  This patch fixes the problem by retrying to find a display mode with YCbCr420 
enforced and using it, if it is valid.

  Testcase:
  Tested on an Clevo NL50RU. General: Find a PC with a current AMD Radeon GPU, 
but only a hdmi 1.4 output (e.g. current Clevo laptops with AMD APU's). Connect 
a 4k@60Hz display supporting YCbCr420 encoding to the hdmi port. Without the 
patch the maximum that can be set via xrandr is 3840 × 2160 30Hz. With the 
Patch 3840 × 2160 60Hz can be selected which will use YCbCr420 automatically.

  Patch already got accepted upstream for linux-next:
  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=14e4a095b29fd290a9b80f6e553adcfcf01672d1 and
  applies without modifications to ubuntu-focal/hwe-5.8

  Commit-hash: 14e4a095b29fd290a9b80f6e553adcfcf01672d1
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  test   2903 F pulseaudio
   /dev/snd/controlC0:  test   2903 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 20.04
  MachineType: TUXEDO TUXEDO Aura 15 Gen1
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=59a028a1-0764-418a-951d-515f1839bd7f ro ignore_loglevel quiet splash 
i8042.reset i8042.nomux i8042.nopnp i8042.noloop xhci_hcd.quirks=1073741824 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.187.9
  Tags:  focal
  Uname: Linux 5.8.0-48-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/13/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03RTR2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: AURA1501
  dmi.board.vendor: TUXEDO Computers
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03RTR2:bd11/13/2020:br7.3:svnTUXEDO:pnTUXEDOAura15Gen1:pvrNotApplicable:rvnTUXEDOComputers:rnAURA1501:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO Aura 15 Gen1
  dmi.product.sku: AURA1501
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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

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

[Kernel-packages] [Bug 1928700] Re: new postinst hook requires initramfs-tools

2021-05-17 Thread Stefan Bader

** Also affects: linux-base (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: linux-base (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux-base (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

** Changed in: linux-base (Ubuntu Impish)
   Status: New => Triaged

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

** Changed in: linux-base (Ubuntu Hirsute)
   Status: New => Triaged

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

** Changed in: linux-base (Ubuntu Focal)
   Status: New => Triaged

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

** Changed in: linux-base (Ubuntu Bionic)
   Status: New => Triaged

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

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

Title:
  new postinst hook requires initramfs-tools

Status in linux-base package in Ubuntu:
  Triaged
Status in linux-base source package in Bionic:
  Triaged
Status in linux-base source package in Focal:
  Triaged
Status in linux-base source package in Hirsute:
  Triaged
Status in linux-base source package in Impish:
  Triaged

Bug description:
  The new postinst hook from bug 1877088 currently requires initramfs-
  tools installed, or installing a kernel would fail. This happens for
  me on a builder chroot trying to build linux-meta of a derivative
  kernel.

  The fix would be to skip running the script if update-initramfs is not
  available.

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

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

[Kernel-packages] [Bug 1928700] [NEW] new postinst hook requires initramfs-tools

2021-05-17 Thread Timo Aaltonen

Public bug reported:

The new postinst hook from bug 1877088 currently requires initramfs-
tools installed, or installing a kernel would fail. This happens for me
on a builder chroot trying to build linux-meta of a derivative kernel.

The fix would be to skip running the script if update-initramfs is not
available.

** Affects: linux-base (Ubuntu)
 Importance: Medium
 Status: Triaged

** Affects: linux-base (Ubuntu Bionic)
 Importance: Medium
 Status: Triaged

** Affects: linux-base (Ubuntu Focal)
 Importance: Medium
 Status: Triaged

** Affects: linux-base (Ubuntu Hirsute)
 Importance: Medium
 Status: Triaged

** Affects: linux-base (Ubuntu Impish)
 Importance: Medium
 Status: Triaged

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

Title:
  new postinst hook requires initramfs-tools

Status in linux-base package in Ubuntu:
  Triaged
Status in linux-base source package in Bionic:
  Triaged
Status in linux-base source package in Focal:
  Triaged
Status in linux-base source package in Hirsute:
  Triaged
Status in linux-base source package in Impish:
  Triaged

Bug description:
  The new postinst hook from bug 1877088 currently requires initramfs-
  tools installed, or installing a kernel would fail. This happens for
  me on a builder chroot trying to build linux-meta of a derivative
  kernel.

  The fix would be to skip running the script if update-initramfs is not
  available.

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

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

[Kernel-packages] [Bug 1922754] Re: Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output

2021-05-17 Thread Werner Sembach

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

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

Title:
  Make AMD gpus choose YCbCr420 encoding automatically when required for
  4k 60Hz output

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  SRU Justification:

  Impact:
  On some setups, while the monitor and the gpu support display modes with 
pixel clocks of up to 600MHz, the link encoder might not. This prevents 
YCbCr444 and RGB encoding for 4k60Hz, but YCbCr420 encoding might still be 
possible. However, which color mode is used is decided before the link encoder 
capabilities are checked, causing the check to fail and discarding 4k60Hz from 
the list of possible display modes.

  Fix:
  This patch fixes the problem by retrying to find a display mode with YCbCr420 
enforced and using it, if it is valid.

  Testcase:
  Tested on an Clevo NL50RU. General: Find a PC with a current AMD Radeon GPU, 
but only a hdmi 1.4 output (e.g. current Clevo laptops with AMD APU's). Connect 
a 4k@60Hz display supporting YCbCr420 encoding to the hdmi port. Without the 
patch the maximum that can be set via xrandr is 3840 × 2160 30Hz. With the 
Patch 3840 × 2160 60Hz can be selected which will use YCbCr420 automatically.

  Patch already got accepted upstream for linux-next:
  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=14e4a095b29fd290a9b80f6e553adcfcf01672d1 and
  applies without modifications to ubuntu-focal/hwe-5.8

  Commit-hash: 14e4a095b29fd290a9b80f6e553adcfcf01672d1
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  test   2903 F pulseaudio
   /dev/snd/controlC0:  test   2903 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 20.04
  MachineType: TUXEDO TUXEDO Aura 15 Gen1
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic 
root=UUID=59a028a1-0764-418a-951d-515f1839bd7f ro ignore_loglevel quiet splash 
i8042.reset i8042.nomux i8042.nopnp i8042.noloop xhci_hcd.quirks=1073741824 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.187.9
  Tags:  focal
  Uname: Linux 5.8.0-48-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/13/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03RTR2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: AURA1501
  dmi.board.vendor: TUXEDO Computers
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03RTR2:bd11/13/2020:br7.3:svnTUXEDO:pnTUXEDOAura15Gen1:pvrNotApplicable:rvnTUXEDOComputers:rnAURA1501:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO Aura 15 Gen1
  dmi.product.sku: AURA1501
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

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

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

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

2021-05-17 Thread bugproxy

--- Comment From niklas.schne...@ibm.com 2021-05-17 10:50 EDT---
I just did an "apt update && apt upgrade" on a KVM guest with Ubuntu 20.04 that 
I had previously used installkernel on with an early version of your updated 
script:

Setting up linux-image-5.4.0-73-generic (5.4.0-73.82) ...
I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.12.0-rc8-07595-g446009324fa8
I: /boot/initrd.img.old is now a symlink to 
initrd.img-5.12.0-rc8-07595-g446009324fa8
I: /boot/vmlinuz is now a symlink to vmlinuz-5.4.0-73-generic
I: /boot/initrd.img is now a symlink to initrd.img-5.4.0-73-generic
Setting up alsa-utils (1.2.2-1ubuntu2.1) ...
alsa-restore.service is a disabled or a static unit not running, not starting 
it.
alsa-state.service is a disabled or a static unit not running, not starting it.
Setting up procps (2:3.3.16-1ubuntu2.1) ...
Setting up bind9-dnsutils (1:9.16.1-0ubuntu2.8) ...
Setting up cloud-init (21.1-19-gbad84ad4-0ubuntu1~20.04.2) ...
Setting up linux-modules-extra-5.4.0-73-generic (5.4.0-73.82) ...
Setting up linux-image-generic (5.4.0.73.76) ...
Setting up linux-generic (5.4.0.73.76) ...
Setting up python3-distupgrade (1:20.04.32) ...
Setting up ubuntu-release-upgrader-core (1:20.04.32) ...
Setting up python3-update-manager (1:20.04.10.7) ...
Setting up update-manager-core (1:20.04.10.7) ...
Setting up update-notifier-common (3.192.30.7) ...
Processing triggers for libc-bin (2.31-0ubuntu9.2) ...
Processing triggers for rsyslog (8.2001.0-1ubuntu1.1) ...
Processing triggers for systemd (245.4-4ubuntu3.6) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for dbus (1.12.16-2ubuntu2.1) ...
Processing triggers for initramfs-tools (0.136ubuntu6.4) ...
update-initramfs: Generating /boot/initrd.img-5.12.0-rc8-07595-g446009324fa8 
<--- this is the currently running kernel installed with installkernel
Not invoking zipl: initrd doesn't exist yet
Processing triggers for linux-image-5.4.0-73-generic (5.4.0-73.82) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.0-73-generic
Not invoking zipl: initrd doesn't exist yet
/etc/kernel/postinst.d/zz-zipl:
Not invoking zipl: initrd doesn't exist yet <--- but above it said it generated 
?it!?

So usually I would expect that upgrading the kernel after having used
installkernel will afterwards use the new distro kernel. Am I correct in
that assumption? It might also be that this system is somehow in a weird
state but would like confirmation either way.

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

Title:
  [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img
  which is required with the default zipl.conf

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux-base package in Ubuntu:
  Fix Released
Status in linux-base source package in Bionic:
  Fix Committed
Status in linux-base source package in Focal:
  Fix Committed
Status in linux-base source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  * initrd link is not updated when using installkernel or "make
  install" from kernel sources. This leads to boot failure after
  installing a new kernel with mentioned methods because the kernel does
  not match initrd.

  * It's a regression because for Focal it was working before.

  * Issue was reproduced also on Bionic.

  * The proposed fixed by Stefan Bader adds a hook in
  /etc/kernel/postinst.d/ so installkernel will relink the initrd. The
  kernel DEB packages should not be affected.

  * The solution from Stefan (first patch) was tested by the bug
  reporter (niklas.schne...@ibm.com).

  [Test Plan]

  * Build a kernel
  * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot
  * Check if /boot/initrd or /initrd symlink to the new initrd

  [Where problems could occur]

  * Installing kernel via: installkernel or "make install", so mostly
  kernel developer environments

  [Other info from developer]

  When testing development kernels I usually rely on the installkernel
  script either through the "make install" target of the Kernel source
  or manually. This used to work great on Ubuntu on Z.

  On Ubuntu 20.04 (freshly installed up to date) this fails however because
  /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the
  wrong kernel/initrd combination rendering the system unbootable.

  (with the correct modules already copied to 
/usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/)
  # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 
5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd
  update-initramfs: Generating

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

This change was made by a bot.

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

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

Title:
  package linux-headers-5.8.0-53 5.8.0-53.60 failed to install/upgrade:
  não pode copiar dados extráidos para './usr/src/linux-
  headers-5.8.0-53/drivers/net/ethernet/mellanox/mlx5/core/steering/Makefile'
  para '/usr/src/linux-
  headers-5.8.0-53/drivers/net/ethernet/mellanox/mlx5/core/steering/Makefile
  .dpkg-new': falhou a escrita (Sem espaço livre no dispositivo)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Getting error message after log in or after any package update.

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: linux-headers-5.8.0-53 5.8.0-53.60
  ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun May 16 21:07:11 2021
  ErrorMessage: não pode copiar dados extráidos para 
'./usr/src/linux-headers-5.8.0-53/drivers/net/ethernet/mellanox/mlx5/core/steering/Makefile'
 para 
'/usr/src/linux-headers-5.8.0-53/drivers/net/ethernet/mellanox/mlx5/core/steering/Makefile.dpkg-new':
 falhou a escrita (Sem espaço livre no dispositivo)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  PackageArchitecture: all
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic 
root=UUID=63c32f9f-5681-43ab-a344-9453024dffd5 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.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: linux
  Title: package linux-headers-5.8.0-53 5.8.0-53.60 failed to install/upgrade: 
não pode copiar dados extráidos para 
'./usr/src/linux-headers-5.8.0-53/drivers/net/ethernet/mellanox/mlx5/core/steering/Makefile'
 para 
'/usr/src/linux-headers-5.8.0-53/drivers/net/ethernet/mellanox/mlx5/core/steering/Makefile.dpkg-new':
 falhou a escrita (Sem espaço livre no dispositivo)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/01/2019
  dmi.bios.release: 4.0
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 7152-2433-7923-1971-9356-1586-36
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1928691] [NEW] package linux-headers-5.8.0-53 5.8.0-53.60 failed to install/upgrade: não pode copiar dados extráidos para './usr/src/linux-headers-5.8.0-53/drivers/net/ethernet/

2021-05-17 Thread Sandro Roberto Costa da Silva

Public bug reported:

Getting error message after log in or after any package update.

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: linux-headers-5.8.0-53 5.8.0-53.60
ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.6
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: skip
Date: Sun May 16 21:07:11 2021
ErrorMessage: não pode copiar dados extráidos para 
'./usr/src/linux-headers-5.8.0-53/drivers/net/ethernet/mellanox/mlx5/core/steering/Makefile'
 para 
'/usr/src/linux-headers-5.8.0-53/drivers/net/ethernet/mellanox/mlx5/core/steering/Makefile.dpkg-new':
 falhou a escrita (Sem espaço livre no dispositivo)
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
Lspci:
 
Lspci-vt: -[:00]-
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
 
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: Microsoft Corporation Virtual Machine
PackageArchitecture: all
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic 
root=UUID=63c32f9f-5681-43ab-a344-9453024dffd5 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.6, python3-minimal, 
3.8.6-0ubuntu1
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
RfKill:
 
SourcePackage: linux
Title: package linux-headers-5.8.0-53 5.8.0-53.60 failed to install/upgrade: 
não pode copiar dados extráidos para 
'./usr/src/linux-headers-5.8.0-53/drivers/net/ethernet/mellanox/mlx5/core/steering/Makefile'
 para 
'/usr/src/linux-headers-5.8.0-53/drivers/net/ethernet/mellanox/mlx5/core/steering/Makefile.dpkg-new':
 falhou a escrita (Sem espaço livre no dispositivo)
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/01/2019
dmi.bios.release: 4.0
dmi.bios.vendor: Microsoft Corporation
dmi.bios.version: Hyper-V UEFI Release v4.0
dmi.board.asset.tag: None
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: Hyper-V UEFI Release v4.0
dmi.chassis.asset.tag: 7152-2433-7923-1971-9356-1586-36
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: Hyper-V UEFI Release v4.0
dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
dmi.product.family: Virtual Machine
dmi.product.name: Virtual Machine
dmi.product.sku: None
dmi.product.version: Hyper-V UEFI Release v4.0
dmi.sys.vendor: Microsoft Corporation

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


** Tags: amd64 apport-package groovy

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

Title:
  package linux-headers-5.8.0-53 5.8.0-53.60 failed to install/upgrade:
  não pode copiar dados extráidos para './usr/src/linux-
  headers-5.8.0-53/drivers/net/ethernet/mellanox/mlx5/core/steering/Makefile'
  para '/usr/src/linux-
  headers-5.8.0-53/drivers/net/ethernet/mellanox/mlx5/core/steering/Makefile
  .dpkg-new': falhou a escrita (Sem espaço livre no dispositivo)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Getting error message after log in or after any package update.

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: linux-headers-5.8.0-53 5.8.0-53.60
  ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun May 16 21:07:11 2021
  ErrorMessage: não pode copiar dados extráidos para 
'./usr/src/linux-headers-5.8.0-53/drivers/net/ethernet/mellanox/mlx5/core/steering/Makefile'
 para 
'/usr/src/linux-headers-5.8.0-53/drivers/net/ethernet/mellanox/mlx5/core/steering/Makefile.dpkg-new':
 falhou a escrita (Sem espaço livre no dispositivo)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  PackageArchitecture: all
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic 
root=UUID=63c32f9f-5681-43ab-a344-9453024dffd5 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd',

[Kernel-packages] [Bug 1928594] Re: Setting up encrypted swap causes ordering cycle

2021-05-17 Thread Dan Streetman

This looks an awful lot like bug 1875577 and from reading the latest
comments it seems like that was never fixed in focal.

Colin did you ever get focal updated with the fix for bug 1875577?

** Package changed: systemd (Ubuntu) => zfs-linux (Ubuntu)

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

Title:
  Setting up encrypted swap causes ordering cycle

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  root@home:~# cat /etc/crypttab
  # 
  cswap /dev/disk/by-partuuid/95605326-e210-4e13-9f93-50cc3d556aca /dev/urandom 
cipher=aes-xts-plain64,size=256,hash=sha1,swap

  root@home:~# update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-73-generic
  cryptsetup: WARNING: Resume target cswap uses a key file

  After reboot:

  root@home:~# systemctl status systemd-random-seed.service
  ● systemd-random-seed.service - Load/Save Random Seed
   Loaded: loaded (/lib/systemd/system/systemd-random-seed.service; static; 
vendor preset: enabled)
   Active: inactive (dead)
 Docs: man:systemd-random-seed.service(8)
   man:random(4)

  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on cryptsetup.target/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on systemd-cryptsetup@cswap.service/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Job 
systemd-random-seed.service/start deleted to break ordering cycle starting with 
systemd-cryptsetup@cswap.service/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
ordering cycle on systemd-random-seed.service/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on zfs-mount.service/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on zfs-import.target/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on zfs-import-cache.service/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on cryptsetup.target/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on systemd-cryptsetup@cswap.service/start
  May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Job 
systemd-random-seed.service/start deleted to break ordering cycle starting with 
systemd-cryptsetup@cswap.service/start

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/efi.img
  CasperMD5CheckResult: fail
  Date: Sun May 16 18:40:45 2021
  InstallationDate: Installed on 2021-01-21 (115 days ago)
  InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
   |__ Port 6: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   SHELL=/bin/bash
   LANG=C.UTF-8
   TERM=screen.xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic 
root=UUID=7c964d4b-ef4d-40df-b297-631e4233f297 ro bootdegraded=true 
transparent_hugepage=never
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3801
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-E:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU

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

2021-05-17 Thread bugproxy

--- Comment From alexs...@de.ibm.com 2021-05-17 10:30 EDT---
Verified successfully on 5.4.0-74, with adapter in eswitch mode and adapter 
firmware 16.27.2008. Thank you!

alexschm@pok1-qz1-sr1-rk011-s21:~$ uname -a
Linux pok1-qz1-sr1-rk011-s21 5.4.0-74-generic #83 SMP Mon May 17 09:04:32 EDT 
2021 s390x s390x s390x GNU/Linux
alexschm@pok1-qz1-sr1-rk011-s21:~$ ping 172.31.22.170
PING 172.31.22.170 (172.31.22.170) 56(84) bytes of data.
64 bytes from 172.31.22.170: icmp_seq=1 ttl=0 time=0.217 ms
64 bytes from 172.31.22.170: icmp_seq=2 ttl=0 time=0.162 ms
64 bytes from 172.31.22.170: icmp_seq=3 ttl=0 time=0.191 ms
^C
--- 172.31.22.170 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2052ms
rtt min/avg/max/mdev = 0.162/0.190/0.217/0.022 ms

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

Title:
  [Ubuntu 21.04] net/mlx5: Fix HW spec violation configuring uplink

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  SRU Justification:
  ==

  [Impact]

  * In addition to 9c9be85f6b59 "net/mlx5e: Add missing capability check
  for uplink follow" (handled in LP#1921104) another fix 1a73704c82ed
  "Fix HW spec violation configuring uplink" (handled in this bug,
  LP#1925452) is needed to fix issues that were introduced with commit
  7d0314b11cdd "net/mlx5e: Modify uplink state on interface up/down".

  * Commit 1a73704c82ed "Fix HW spec violation configuring uplink" fixes
  a regression for mlx5 adapters required to operate in switchdev mode.

  * This fix makes sure that the uplink port is modified to follow only
  if the uplink_follow capability if it's set as required by the hw
  specification.

  * Failure cause traffic to the uplink representer net device to cease
  after switching to switchdev mode.

  [Fix]

  * upstream fix (upstream with v5.12-rc7)
  1a73704c82ed4ee95532ac04645d02075bd1ce3d 1a73704c82ed "Fix HW spec violation 
configuring uplink"

  * can be cleanly cherry picked from hirsute master-next.

  * a backport for groovy:
  
https://launchpadlibrarian.net/534888680/groovy-0001-net-mlx5-Fix-HW-spec-violation-configuring-uplink.patch

  * a backport for focal:
  
https://launchpadlibrarian.net/534847308/focal-0001-net-mlx5-Fix-HW-spec-violation-configuring-uplink.patch

  [Test Case]

  * Two servers, installed with Ubuntu Server 20.04 or 20.10 are needed.

  * Each server needs to have a Mellanox ConnectX4/5 adapter, attached
  to the same switch

  * Adapters must be running adapter firmware level 16.29.1006 or
  earlier.

  * enable SRIOV and switchdev mode on one adapter:
    echo 0 > /sys/bus/pci/devices/0100\:00\:00.0/sriov_drivers_autoprobe
    echo 0 > /sys/bus/pci/devices/0100\:00\:00.1/sriov_drivers_autoprobe
    echo 64 > /sys/bus/pci/devices/0100\:00\:00.0/sriov_numvfs
    echo 64 > /sys/bus/pci/devices/0100\:00\:00.1/sriov_numvfs
    devlink dev eswitch set pci/0100:00:00.0 mode switchdev
    devlink dev eswitch set pci/0100:00:00.1 mode switchdev

  * Assign an IP address to the physical function device of the adapters
  on both systems

  * IP communication will fail

  * With the fix, IP communication can be established.

  [Regression Potential]

  * There is always at least some potential for regression. In this case
  the new code can go wrong (or might become worse than before) in case
  the new if statement is wrong.

  * It checks for the condition of "MLX5_CAP_GEN(mdev, uplink_follow)"
  and in case MLX5_CAP_GEN is calculated erroneous or mdev is other than
  expected, the mlx5_modify_vport_admin_state call might go wrong, too.

  * But since only the If clause was added, the changes are pretty
  minimal and therefore well traceable.

  [Other]

  * Since the patch/commit is upstream with 5.12-rc7, it will be in Impish.
  __

  With the 5.4.0-48 update for Ubuntu 20.04, the commit

  "net/mlx5e: Modify uplink state on interface up/down"

  was integrated which contains a regression for mlx5 adapters with
  older adapter firmware.

  This is the second bugfix to repair the regression, required to operate the 
adapter in switchdev mode.
  The first part was integrated via Bug 192185 - LP1921104.

  This is the upstream fix required to be backported to Ubuntu 20.04:
  
https://github.com/torvalds/linux/commit/1a73704c82ed4ee95532ac04645d02075bd1ce3d

  ---Additional Hardware Info---
  Mellanox ConnectX network adapter

  ---uname output---
  5.4.0-73-generic

  ---Steps to Reproduce---
   enable switchdev mode
  try to ping external host

  Backports need to be provide for 21.04, 20.10 and 20.04 (if not
  cleanly applyable)!

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1928594] [NEW] Setting up encrypted swap causes ordering cycle

You have been subscribed to a public bug:

root@home:~# cat /etc/crypttab
# 
cswap /dev/disk/by-partuuid/95605326-e210-4e13-9f93-50cc3d556aca /dev/urandom 
cipher=aes-xts-plain64,size=256,hash=sha1,swap

root@home:~# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.4.0-73-generic
cryptsetup: WARNING: Resume target cswap uses a key file

After reboot:

root@home:~# systemctl status systemd-random-seed.service
● systemd-random-seed.service - Load/Save Random Seed
 Loaded: loaded (/lib/systemd/system/systemd-random-seed.service; static; 
vendor preset: enabled)
 Active: inactive (dead)
   Docs: man:systemd-random-seed.service(8)
 man:random(4)

May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on cryptsetup.target/start
May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on systemd-cryptsetup@cswap.service/start
May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Job 
systemd-random-seed.service/start deleted to break ordering cycle starting with 
systemd-cryptsetup@cswap.service/start
May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
ordering cycle on systemd-random-seed.service/start
May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on zfs-mount.service/start
May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on zfs-import.target/start
May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on zfs-import-cache.service/start
May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on cryptsetup.target/start
May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Found 
dependency on systemd-cryptsetup@cswap.service/start
May 16 18:29:16 home systemd[1]: systemd-cryptsetup@cswap.service: Job 
systemd-random-seed.service/start deleted to break ordering cycle starting with 
systemd-cryptsetup@cswap.service/start

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.6
ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
Uname: Linux 5.4.0-73-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/efi.img
CasperMD5CheckResult: fail
Date: Sun May 16 18:40:45 2021
InstallationDate: Installed on 2021-01-21 (115 days ago)
InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
Lsusb:
 Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M
 /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
 |__ Port 6: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
MachineType: System manufacturer System Product Name
ProcEnviron:
 SHELL=/bin/bash
 LANG=C.UTF-8
 TERM=screen.xterm-256color
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic 
root=UUID=7c964d4b-ef4d-40df-b297-631e4233f297 ro bootdegraded=true 
transparent_hugepage=never
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/14/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3801
dmi.board.asset.tag: Default string
dmi.board.name: Z170-E
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-E:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug focal third-party-packages
-- 
Setting up encrypted swap causes ordering cycle
https://bugs.launchpad.net/bugs/1928594
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to zfs-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 1928600] Re: [amdgpu] Gnome locks up with artifacts on screen

2021-05-17 Thread Paul Tansom

Tried the 5.12.4-051204 image from the reference link and still get the
lock up - 3 since installing about 4 hours ago (first from suspend and
then twice in attempts to reboot and get working again - in each case
moments after logging in).

Currently running the 5.8.0-53 kernel from the 21.04 repositories as a
comparison. 5.8 was less unstable under 20.04 than 5.11 has been under
21.04 so far.

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)

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

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

[Kernel-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules

2021-05-17 Thread Dimitri John Ledkov

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

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

Title:
  linux from security may force reboots without complete dkms modules

Status in acpi-call package in Ubuntu:
  Fix Released
Status in apt package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in bcmwl package in Ubuntu:
  Fix Released
Status in dahdi-linux package in Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dm-writeboost package in Ubuntu:
  Fix Released
Status in evdi package in Ubuntu:
  Fix Released
Status in gost-crypto package in Ubuntu:
  Fix Released
Status in iptables-netflow package in Ubuntu:
  Fix Released
Status in liblzf package in Ubuntu:
  Fix Released
Status in lime-forensics package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-meta package in Ubuntu:
  Triaged
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in openafs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  Fix Released
Status in r8168 package in Ubuntu:
  Fix Released
Status in rtl8812au package in Ubuntu:
  Fix Released
Status in sysdig package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-hwe package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in acpi-call source package in Focal:
  Fix Committed
Status in backport-iwlwifi-dkms source package in Focal:
  Fix Committed
Status in bcmwl source package in Focal:
  Fix Committed
Status in dahdi-linux source package in Focal:
  Fix Committed
Status in dm-writeboost source package in Focal:
  Fix Committed
Status in evdi source package in Focal:
  Fix Committed
Status in gost-crypto source package in Focal:
  Fix Committed
Status in iptables-netflow source package in Focal:
  Fix Committed
Status in liblzf source package in Focal:
  Fix Committed
Status in lime-forensics source package in Focal:
  Fix Committed
Status in lttng-modules source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Focal:
  Fix Committed
Status in oss4 source package in Focal:
  Fix Committed
Status in r8168 source package in Focal:
  Fix Committed
Status in rtl8812au source package in Focal:
  Fix Committed
Status in sysdig source package in Focal:
  Fix Committed
Status in v4l2loopback source package in Focal:
  Fix Committed
Status in virtualbox source package in Focal:
  Fix Committed
Status in virtualbox-hwe source package in Focal:
  Fix Committed
Status in zfs-linux source package in Focal:
  Fix Committed

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions

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

[Kernel-packages] [Bug 1928686] [NEW] Oracle kernel has Android related config options disabled

2021-05-17 Thread Simon Fels

Public bug reported:

For Anbox Cloud we require certain CONFIG_ANDROID_* options to be
enabled in the kernel. We do this already for most of our cloud kernels
(GCE, AWS, Azure) and the generic kernel and should do so for the oracle
(and possible others too). We have customers looking at running Anbox
Cloud on OCI instances and having the ashmem and binder kernel modules
available is a precondition for this to work.


The following options are what we need

CONFIG_ANDROID=y
CONFIG_ANDROID_BINDER_IPC=m
CONFIG_ANDROID_BINDERFS=m
CONFIG_ANDROID_BINDER_DEVICES=""
# CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set
CONFIG_ASHMEM=m

These should be the same across all our kernels where we're going to
support Anbox Cloud.

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

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

Title:
  Oracle kernel has Android related config options disabled

Status in linux-oracle package in Ubuntu:
  New

Bug description:
  For Anbox Cloud we require certain CONFIG_ANDROID_* options to be
  enabled in the kernel. We do this already for most of our cloud
  kernels (GCE, AWS, Azure) and the generic kernel and should do so for
  the oracle (and possible others too). We have customers looking at
  running Anbox Cloud on OCI instances and having the ashmem and binder
  kernel modules available is a precondition for this to work.

  
  The following options are what we need

  CONFIG_ANDROID=y
  CONFIG_ANDROID_BINDER_IPC=m
  CONFIG_ANDROID_BINDERFS=m
  CONFIG_ANDROID_BINDER_DEVICES=""
  # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set
  CONFIG_ASHMEM=m

  These should be the same across all our kernels where we're going to
  support Anbox Cloud.

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

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

[Kernel-packages] [Bug 1928679] [NEW] Support importing mokx keys into revocation list from the mok table

2021-05-17 Thread Dimitri John Ledkov

*** This bug is a security vulnerability ***

Public security bug reported:

[Impact]

 * Ubuntu's 15.4 based shim ships a very large vendor-dbx (aka mokx)
which revokes many Ubuntu kernel hashes and 2012 signing key.

 * Kernel should import those into it's %:.blacklist keyring such that
it prohibits signed kexec of the revoked kernels.

 * v5.13-rc1 kernel has learned how to import mokx and how to import
full certs into the %:.blacklist keyring.

 * However, it only does so by reading MokListXRT efi variable.

 * Due to the large size of Ubuntu's vendor-dbx, shim does not create
MokListXRT efi variable, but instead creates MokListXRT1 MokListXRT2
MokListXRT3 which currently v5.13-rc1 kernel cannot read. Shim also
exposes MokListXRT via mokvar table, which is easier to parse and
contains all the revocations in full. Kernel needs a patch to read
MokListXRT via mokvar table.

 * We have two options on how to proceed from here, either we include
the same hashes and certs as our vendordbx in in the kernel as
revocation list, or we fix kernel to read MokListXRT via mokvar table

 * The above is known as CVE-2020-26541

 * Separately it would be nice to add informational dmesg messages when
revoking signing certificates, as a good indication that signing key
rotation events have happened and have been applied correctly.

[Test Plan]

 * Boot kernel with 15.4 based Ubuntu shim

 * Install keyutils package

 * Execute $ sudo keyctl list %:.blacklist it should list in exccess of
300+ hash entries. It also must list assymetric Canonical signing key
from 2012.

 * Separately check dmesg to observe that asymmetric canonical signing
key from 2012 is revoked.

[Where problems could occur]

 * EFI variable storage can be full thus preventing shim to mirror
efivars and the moktable. On decent hardware this should not happen, but
has been observed to be corrupted on some older EDKII based OVMF
instances with small EFI variable storage space (pre-4MB).

[Other Info]
 
 * The patches to fix the above have been submitted upstream

https://lore.kernel.org/keyrings/20210512153100.285169-1-dimitri.led...@canonical.com/

https://lore.kernel.org/keyrings/20210512110302.262104-1-dimitri.led...@canonical.com/

This will now be submitted as SAUCE patches for the Ubuntu UNSTABLE
kernel, until accepted upstream.

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

** Summary changed:

- Supporting importing dbx keys into revocation list from mok table
+ Support importing mokx keys into revocation list from the mok table

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

** Information type changed from Public to Public Security

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

Title:
  Support importing mokx keys into revocation list from the mok table

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * Ubuntu's 15.4 based shim ships a very large vendor-dbx (aka mokx)
  which revokes many Ubuntu kernel hashes and 2012 signing key.

   * Kernel should import those into it's %:.blacklist keyring such that
  it prohibits signed kexec of the revoked kernels.

   * v5.13-rc1 kernel has learned how to import mokx and how to import
  full certs into the %:.blacklist keyring.

   * However, it only does so by reading MokListXRT efi variable.

   * Due to the large size of Ubuntu's vendor-dbx, shim does not create
  MokListXRT efi variable, but instead creates MokListXRT1 MokListXRT2
  MokListXRT3 which currently v5.13-rc1 kernel cannot read. Shim also
  exposes MokListXRT via mokvar table, which is easier to parse and
  contains all the revocations in full. Kernel needs a patch to read
  MokListXRT via mokvar table.

   * We have two options on how to proceed from here, either we include
  the same hashes and certs as our vendordbx in in the kernel as
  revocation list, or we fix kernel to read MokListXRT via mokvar table

   * The above is known as CVE-2020-26541

   * Separately it would be nice to add informational dmesg messages
  when revoking signing certificates, as a good indication that signing
  key rotation events have happened and have been applied correctly.

  [Test Plan]

   * Boot kernel with 15.4 based Ubuntu shim

   * Install keyutils package

   * Execute $ sudo keyctl list %:.blacklist it should list in exccess
  of 300+ hash entries. It also must list assymetric Canonical signing
  key from 2012.

   * Separately check dmesg to observe that asymmetric canonical signing
  key from 2012 is revoked.

  [Where problems could occur]

   * EFI variable storage can be full thus preventing shim to mirror
  efivars and the moktable. On decent hardware this should not happen,
  but has been observed to be corrupted on some older EDKII based OVMF
  instances with small EFI

[Kernel-packages] [Bug 1928593] Re: Dell Precision 3560: system hang upon resume from s2idle suspend

2021-05-17 Thread Brian J. Cohen

** Attachment added: "journalctl.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928593/+attachment/5498228/+files/journalctl.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/1928593

Title:
  Dell Precision 3560: system hang upon resume from s2idle suspend

Status in linux package in Ubuntu:
  In Progress

Bug description:
  On a Dell Precision 3560 with all-Intel graphics (no Nvidia).  The
  machine will successfully go into s2idle suspend (sleep) but upon
  waking, the system will immediately freeze hard. In its frozen state,
  the mouse pointer will be visible against a black screen.  Here are
  the troubleshooting steps I have taken so far:

  - Can successfully reproduce under Ubuntu 20.04.2 (gdm3), Kubuntu
  20.04.2 (sddm).  For what it's worth, I can also reproduce this under
  Manjaro (stable), so it's conceivable this is a kernel bug.

  - There's some evidence online that this issue, or something similar,
  was introduced in/around kernel 5.6.19 -- I have not been able to get
  Ubuntu to boot under a kernel earlier than 5.8 so I cannot confirm
  this.

  - Updated BIOS to latest (1.6).  'Block sleep' is off. System > SATA
  is 'AHCI'.  Post Behavior > Fastboot is 'Thorough'.  Secure Boot is
  disabled.

  - Determined that this BIOS does not appear to support 'deep' sleep,
  only s2idle.

  - The problem does NOT occur if I boot to an Ubuntu 20.04.2 live USB
  disk.  I compared the drivers that are loaded in that environment vs.
  those that are loaded under the installed OS and did not notice
  anything suspicious.

  
  I am happy to supply any diagnostics or logs that are requested.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brian   916 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-05-16 (0 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Dell Inc. Precision 3560
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic 
root=UUID=03c4b3bd-b521-45b0-b01d-cd092ba108bc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-53-generic N/A
   linux-backports-modules-5.8.0-53-generic  N/A
   linux-firmware1.187.12
  Tags:  focal
  Uname: Linux 5.8.0-53-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/19/2021
  dmi.bios.release: 1.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 063MV5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd04/19/2021:br1.6:svnDellInc.:pnPrecision3560:pvr:rvnDellInc.:rn063MV5:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3560
  dmi.product.sku: 0A22
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1928593] Re: Dell Precision 3560: system hang upon resume from s2idle suspend

2021-05-17 Thread Brian J. Cohen

@koba,

Funny you should mention that. I actually did yesterday try the 5.6.0-1032-oem
kernel because that is the one that this machine was apparently certified under
as documented here:
https://certification.ubuntu.com/hardware/202010-28315

And, sure enough, suspend mostly works under this kernel. Or, at least,
it properly wakes from suspend.

I was not able to install linux-image-unsigned-5.10.0-1027-oem because
it is not yet available in the respositories (even after 'apt update')
but I installed linux-image-unsigned-5.10.0-1026-oem and I *am* able to
reproduce the problem under this kernel. When I tried to resume from
suspend, the mouse cursor was visible against a black screen and the
machine was frozen. I restarted by holding down the power button and
booted back into 5.6.0-1032-oem and ran journalctl -k -b -1, which I've
attached.

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

Title:
Dell Precision 3560: system hang upon resume from s2idle suspend

Status in linux package in Ubuntu:
In Progress

Bug description:
On a Dell Precision 3560 with all-Intel graphics (no Nvidia). The
machine will successfully go into s2idle suspend (sleep) but upon
waking, the system will immediately freeze hard. In its frozen state,
the mouse pointer will be visible against a black screen. Here are
the troubleshooting steps I have taken so far:

- Can successfully reproduce under Ubuntu 20.04.2 (gdm3), Kubuntu
20.04.2 (sddm). For what it's worth, I can also reproduce this under
Manjaro (stable), so it's conceivable this is a kernel bug.

- There's some evidence online that this issue, or something similar,
was introduced in/around kernel 5.6.19 -- I have not been able to get
Ubuntu to boot under a kernel earlier than 5.8 so I cannot confirm
this.

- Updated BIOS to latest (1.6). 'Block sleep' is off. System > SATA
is 'AHCI'. Post Behavior > Fastboot is 'Thorough'. Secure Boot is
disabled.

- Determined that this BIOS does not appear to support 'deep' sleep,
only s2idle.

- The problem does NOT occur if I boot to an Ubuntu 20.04.2 live USB
disk. I compared the drivers that are loaded in that environment vs.
those that are loaded under the installed OS and did not notice
anything suspicious.

I am happy to supply any diagnostics or logs that are requested.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: brian 916 F pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-05-16 (0 days ago)
InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
MachineType: Dell Inc. Precision 3560
Package: linux (not installed)
ProcEnviron:
LANGUAGE=
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic
root=UUID=03c4b3bd-b521-45b0-b01d-cd092ba108bc ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.8.0-53-generic N/A
linux-backports-modules-5.8.0-53-generic N/A
linux-firmware1.187.12
Tags: focal
Uname: Linux 5.8.0-53-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 04/19/2021
dmi.bios.release: 1.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.0
dmi.board.name: 063MV5
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.6.0:bd04/19/2021:br1.6:svnDellInc.:pnPrecision3560:pvr:rvnDellInc.:rn063MV5:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 3560
dmi.product.sku: 0A22
dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1922651] Re: r8152 tx status -71

2021-05-17 Thread Martin Vysny

I've successfully upgraded to 5.11.0-18-generic and removed all
usbcore.quirks kernel parameters; so far everything is working. I'll
test more and I'll update the tags tomorrow appropriately.

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

Title:
  r8152 tx status -71

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've bought ThinkPad T14s with a USB-based docking station. Everything
  is working marvelously, but from time to time the ethernet port on the
  docking station won't connect. I've discovered the following messages
  in my dmesg:

  [  400.597506] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  401.164370] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  463.168412] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  465.314415] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  529.409871] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  533.718163] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  591.168537] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
  [  594.335383] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71

  Rebooting the machine doesn't seem to work, turning the ethernet
  connection off and on doesn't seem to work. I have a dualboot
  Linux+Windows (one wants to play games from time to time :-p ) and it
  could be that rebooting from Win to Lin causes this issue, but this
  needs to be confirmed yet. I will try to power off the computer and/or
  the docking station, to see whether that would help.

  I've found numerous bug reports, but they are rather old or may not
  apply to this situation, therefore I figured it's best to open a new
  bug report.

  Thank you so much for your hard work!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-48-generic 5.8.0-48.54
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  6 10:00:29 2021
  InstallationDate: Installed on 2021-03-24 (12 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20UH001QMX
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-48-generic 
root=UUID=14a0-0947-4e58-ade1-ad9963053d85 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-48-generic N/A
   linux-backports-modules-5.8.0-48-generic  N/A
   linux-firmware1.190.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2020
  dmi.bios.release: 1.30
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1CET61W(1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UH001QMX
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.30
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1CET61W(1.30):bd12/21/2020:br1.30:efr1.30:svnLENOVO:pn20UH001QMX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UH001QMX:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14s Gen 1
  dmi.product.name: 20UH001QMX
  dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1
  dmi.product.version: ThinkPad T14s Gen 1
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1927064] Re: Bluetooth toggle not working in Ubuntu 21.04

2021-05-17 Thread andrew robinson

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

** This bug has been marked a duplicate of bug 1926062
   [hirsute] Can't turn bluetooth on again after turning it off

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

Title:
  Bluetooth toggle not working in Ubuntu 21.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating my OS from 20.10 to 21.04 the Bluetooth service remains
  turned off even when I turn the toggle switch on.

  The toggle is not working, neither from the top bar dropdown menu nor
  from the settings window. Switching on the toggle did not have any
  effect.

  I have tried using these commands in the terminal:

  sudo modprobe -r btusb
  sudo modprobe btusb

  They worked once, then when I toggle off and toggle on bluetooth it
  remains turned off. I have restart the system for the commands to work
  again

  I also tried from the terminal:

  sudo systemctl restart Bluetooth

  Again it did restart the bluetooth service but if I toggle off and
  then on again bluetooth service remains off. As before I have to
  restart the system for the command to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-16-generic 5.11.0-16.17
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andrew 1376 F pulseaudio
   /dev/snd/controlC0:  andrew 1376 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  4 09:37:29 2021
  InstallationDate: Installed on 2021-04-15 (18 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Acer Aspire E5-572G
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=6b9d5149-b57c-405b-802b-9e82a0fe23e3 ro quiet splash 
resume=UUID=69d3cfd8-3a1a-4a9e-b158-4c66cfe64a1a vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (11 days ago)
  dmi.bios.date: 12/17/2014
  dmi.bios.release: 1.3
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.03
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA50_HWS
  dmi.board.vendor: Acer
  dmi.board.version: V1.03
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.03:bd12/17/2014:br1.3:efr1.3:svnAcer:pnAspireE5-572G:pvrV1.03:rvnAcer:rnEA50_HWS:rvrV1.03:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: SharkBay System
  dmi.product.name: Aspire E5-572G
  dmi.product.sku: Aspire E5-572G_0922_V1.03
  dmi.product.version: V1.03
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1928600] Re: [amdgpu] Gnome locks up with artifacts on screen

2021-05-17 Thread Paul Tansom

lspci output attached. Kernel wise, I'll take a look, but will note that
this has followed me through kernel updates at least with 5.4.x 5.8.x
and 5.11.x kernels from the stock Ubuntu repositories in case that is of
any help. If it is kernel related 5.11.x is significantly worse than the
5.4.x and 5.8.x ones.

** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928600/+attachment/5498200/+files/lspci.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/1928600

Title:
  [amdgpu] Gnome locks up with artifacts on screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With this hardware configuration this issue has been a problem only
  when suspending or resuming from suspend under 20.04. Having decided
  to upgrade through 20.10 to 21.04 to see if things improve enough to
  help me identify which package to report a bug against things have
  become significantly worse.

  With 20.04 it was an occasional occurrence found when returning to the
  computer. Either it was stuck in the suspend process with a blank
  screen or one with artefacts on, or it would start the resume and then
  lock.

  On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough
  time to tidy up and upgrade again), the system seemed improved
  initially - including notably improved boot times (no idea if that is
  related). After a bit of checking things out I went to enable the PPAs
  that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome -
  all of which have been installed after the problems were initially
  noted). When the window to authenticate popped up the screen filled
  with artefacts and I had to reset. After several attempts to reboot
  into a working desktop variously booting to artefacts, or getting
  artefacts immediately after logging in (usually when opening and
  maximising a terminal to capture the logs for later) I managed to
  change from Wayland to X.Org and logged in successfully with no
  problems for the rest of the day (including a Jitsi meeting lasting
  about 4 hours or more). The next day (today) suspend and resume is
  causing problems as before, boot has slowed down again (again, no idea
  if this is related).

  Compared to 20.04 there are more frequent locks (it had reached one
  every other day, but now it is more frequent - 4 today so far).

  Key things I have noted:

  - it is significantly worse under Wayland (to the point of being unusable)
  - it usually happens during the suspend / resume, but not always
  - when using the desktop it will always related to moving or resizing a window
  - leaving the PC powered off for a few minutes helps to get a reliable reboot 
(as in, if you reboot too quickly you get artefacts immediately after logging 
in)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 16 19:23:00 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-10-16 (212 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago)

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

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

[Kernel-packages] [Bug 1770845] Re: Make vfio-pci built-in or xhci_hcd optional

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-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1770845

Title:
  Make vfio-pci built-in or xhci_hcd optional

Status in linux package in Ubuntu:
  Fix Released
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Cosmic:
  Invalid
Status in linux-kvm source package in Cosmic:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-kvm source package in Focal:
  Invalid

Bug description:
  [Impact]
  This allows vfio-pci to be bound to certain devices during boot, preventing 
other drivers from binding them.

  In particular, USB host drivers, like xhci_hcd, are hard to unbind, as
  USB devices may end up being used by applications.

  [Test case]
  Boot the system with vfio-pci.ids=8086:1e31 or other device ID.

  [Regression potential]
  Check that VFIO does not bind to any other device.

  --

  
  Because of
  nazar-pc@nazar-pc ~> cat '/boot/config-4.15.0-21-generic' | grep 
CONFIG_USB_XHCI_HCD
  CONFIG_USB_XHCI_HCD=y

  Following doesn't work:
  nazar-pc@nazar-pc ~> cat /etc/modprobe.d/gpu-passthrough.conf
  options vfio-pci ids=10de:1b06,10de:10ef,1b21:2142
  softdep nouveau pre: vfio-pci
  softdep xhci_hcd pre: vfio-pci

  GPU is fine (first 2 IDs), but USB controller is always occupied by
  xhci_hcd and I can't change that while xhci_hcd is built-in.

  I'd like you to resolve this issue by either embedding vfio-pci module
  too (prefered solution) or making xhci_hcd optional.

  There are some discussions withot clean solution online like this:
  
https://www.reddit.com/r/VFIO/comments/4o6wla/cant_get_vfiopci_to_bind_to_usb_30_card_at_boot/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.15.0-21-generic 4.15.0-21.22
  ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
  Uname: Linux 4.15.0-21-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-21-generic.
  ApportVersion: 2.20.10-0ubuntu2
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: S51 [SB Omni Surround 5.1], device 0: USB Audio [USB Audio]
     Subdevices: 0/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   nazar-pc   2226 F...m pulseaudio
   /dev/snd/pcmC1D0p:   nazar-pc   2226 F...m pulseaudio
   /dev/snd/controlC1:  nazar-pc   2226 F pulseaudio
    nazar-pc   2267 F volumeicon
  Card1.Amixer.info:
   Card hw:1 'S51'/'Creative Technology Ltd SB Omni Surround 5.1 at 
usb-:00:14.0-9.2, full spee'
     Mixer name : 'USB Mixer'
     Components : 'USB041e:322c'
     Controls  : 12
     Simple ctrls  : 5
  CurrentDesktop: Custom
  Date: Sat May 12 16:44:11 2018
  IwConfig: Error: [Errno 2] Немає такого файла або каталогу: 'iwconfig': 
'iwconfig'
  MachineType: Micro-Star International Co., Ltd. MS-7B45
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/root/boot/vmlinuz-4.15.0-21-generic 
root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root 
nosplash intel_pstate=disable scsi_mod.use_blk_mq=1 intel_iommu=on
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-21-generic N/A
   linux-backports-modules-4.15.0-21-generic  N/A
   linux-firmware 1.173
  RfKill: Error: [Errno 2] Немає такого файла або каталогу: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.51
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.51:bd03/29/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7B45
  dmi.product.version: 2.0

[Kernel-packages] [Bug 1925008] Re: no memory hot-plugging in cloud-images

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-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1925008

Title:
  no memory hot-plugging in cloud-images

Status in cloud-images:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Released
Status in linux-kvm source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Released
Status in linux-kvm source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Released
Status in linux-kvm source package in Hirsute:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  Memory hot-plugging is not working with public cloud-images. Error with dmesg 
shows:
  [  184.544535] acpi PNP0C80:00: Enumeration failure

  checking kernel configuration:
  root@ubuntu:/boot# uname -r
  5.4.0-1038-kvm
  root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm
  # CONFIG_ACPI_HOTPLUG_MEMORY is not set

  Obviously the necessary kernel configuration for ACPI memory hotplug
  is missing.

  root@ubuntu:~# cat  /etc/cloud/build.info
  build_name: server
  serial: 20210415
  ---
  ProblemType: Bug
  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.11-0ubuntu27.16
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: N/A
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: 
/sys/bus/usb/devices: No such file or directory
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm 
root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 
console=ttyS0 panic=-1
  ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-1038-kvm N/A
   linux-backports-modules-5.4.0-1038-kvm  N/A
   linux-firmware  N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-1038-kvm x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: False
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.12.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.7
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.7
  dmi.sys.vendor: QEMU

  [Test Plan]

  Boot a kernel with CONFIG_ACPI_HOTPLUG_MEMORY enabled. Check that
  requested memory has been added.

  [Where problems could occur]

  Adding memory could fail, or cause other configurations issues.
  Regressions seem unlikely since this config option is enabled in all
  cloud kernels except linux-azure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions

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

[Kernel-packages] [Bug 1924624] Re: After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge/Bay Trail) graphics a lot of glitches render screen unusable

2021-05-17 Thread Mahmoud Elbarbari

I have opened a new bug: https://bugs.launchpad.net/ubuntu/+source
/linux-signed-hwe-5.8/+bug/1928656

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

Title:
  After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy
  Bridge/Bay Trail) graphics a lot of glitches render screen unusable

Status in linux package in Ubuntu:
  Fix Released
Status in linux-meta-hwe-5.8 package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to 5.8.0-49, on a laprtop with intel graphics, graphics was 
suddenly extremely glitchy.
  Icons from the desktop flash through the browser, windows top bar gets 
distorted, all sort of glitches appear, parts of characters are missing in 
terminal, scrolling is inconsistent and the whole desktop becomes unusable.
  Under wayland the graphics are a bit more stable, but lots of glitches appear 
anyway, video reproduction in browser is stuttering and wobbly.
  Booting with previous kernel 5.8.0-48 seems to fix the issues.
  5.8.0-50 is broken as well.

  this is the result of 'sudo lshw -c video' on my hp Elitebook 8470:

  *-display 
 description: VGA compatible controller
 product: 3rd Gen Core processor Graphics Controller
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:33 memory:d400-d43f memory:c000-cfff 
ioport:4000(size=64) memory:c-d

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

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

[Kernel-packages] [Bug 1924624] Re: After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge/Bay Trail) graphics a lot of glitches render screen unusable

2021-05-17 Thread Rudi van Vuuren

System updated, been using it for a few hours now and all seems well. 
I am so thankful for whoever fixed this.

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

Title:
  After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy
  Bridge/Bay Trail) graphics a lot of glitches render screen unusable

Status in linux package in Ubuntu:
  Fix Released
Status in linux-meta-hwe-5.8 package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to 5.8.0-49, on a laprtop with intel graphics, graphics was 
suddenly extremely glitchy.
  Icons from the desktop flash through the browser, windows top bar gets 
distorted, all sort of glitches appear, parts of characters are missing in 
terminal, scrolling is inconsistent and the whole desktop becomes unusable.
  Under wayland the graphics are a bit more stable, but lots of glitches appear 
anyway, video reproduction in browser is stuttering and wobbly.
  Booting with previous kernel 5.8.0-48 seems to fix the issues.
  5.8.0-50 is broken as well.

  this is the result of 'sudo lshw -c video' on my hp Elitebook 8470:

  *-display 
 description: VGA compatible controller
 product: 3rd Gen Core processor Graphics Controller
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:33 memory:d400-d43f memory:c000-cfff 
ioport:4000(size=64) memory:c-d

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

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

[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14

2021-05-17 Thread Badaoui Mohamed

Hi @Logix,

Thanks you very much for this contribution! :)

I updated the README with your recommendations:
https://github.com/mohamed-badaoui/asus-touchpad-numpad-driver

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

Title:
  numpad on touchpad doesn't work in ASUS Zenbook 14

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

Bug description:
  I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside 
windows 10. 
  The numeric keypads are within the touchpad and are supposed to be turned on 
by a button on the touchpad. This works well in Windows but doesn't work in 
Ubuntu. 
  I have tried to search for any related problems/solutions online but I 
haven't been able to.
  I will appreciate any suggestion or help.
  Thanks,
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.19.11-041911-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.18.10-041810-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1924624] Re: After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge/Bay Trail) graphics a lot of glitches render screen unusable

Also the link in comment #30 is NOT related to this bug. It's the wrong
hardware generation. You need to open a new bug.

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

Title:
  After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy
  Bridge/Bay Trail) graphics a lot of glitches render screen unusable

Status in linux package in Ubuntu:
  Fix Released
Status in linux-meta-hwe-5.8 package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to 5.8.0-49, on a laprtop with intel graphics, graphics was 
suddenly extremely glitchy.
  Icons from the desktop flash through the browser, windows top bar gets 
distorted, all sort of glitches appear, parts of characters are missing in 
terminal, scrolling is inconsistent and the whole desktop becomes unusable.
  Under wayland the graphics are a bit more stable, but lots of glitches appear 
anyway, video reproduction in browser is stuttering and wobbly.
  Booting with previous kernel 5.8.0-48 seems to fix the issues.
  5.8.0-50 is broken as well.

  this is the result of 'sudo lshw -c video' on my hp Elitebook 8470:

  *-display 
 description: VGA compatible controller
 product: 3rd Gen Core processor Graphics Controller
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:33 memory:d400-d43f memory:c000-cfff 
ioport:4000(size=64) memory:c-d

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

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

[Kernel-packages] [Bug 1924624] Re: After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge/Bay Trail) graphics a lot of glitches render screen unusable

If you still experience a problem in kernel 5.8.0-52 or later then
please open a new bug by running:

  ubuntu-bug 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/1924624

Title:
  After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy
  Bridge/Bay Trail) graphics a lot of glitches render screen unusable

Status in linux package in Ubuntu:
  Fix Released
Status in linux-meta-hwe-5.8 package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to 5.8.0-49, on a laprtop with intel graphics, graphics was 
suddenly extremely glitchy.
  Icons from the desktop flash through the browser, windows top bar gets 
distorted, all sort of glitches appear, parts of characters are missing in 
terminal, scrolling is inconsistent and the whole desktop becomes unusable.
  Under wayland the graphics are a bit more stable, but lots of glitches appear 
anyway, video reproduction in browser is stuttering and wobbly.
  Booting with previous kernel 5.8.0-48 seems to fix the issues.
  5.8.0-50 is broken as well.

  this is the result of 'sudo lshw -c video' on my hp Elitebook 8470:

  *-display 
 description: VGA compatible controller
 product: 3rd Gen Core processor Graphics Controller
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:33 memory:d400-d43f memory:c000-cfff 
ioport:4000(size=64) memory:c-d

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

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

[Kernel-packages] [Bug 1924624] Re: After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge/Bay Trail) graphics a lot of glitches render screen unusable

2021-05-17 Thread Mahmoud Elbarbari

My problem still persists after upgrading

https://answers.launchpad.net/ubuntu/+question/696971

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

Title:
  After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy
  Bridge/Bay Trail) graphics a lot of glitches render screen unusable

Status in linux package in Ubuntu:
  Fix Released
Status in linux-meta-hwe-5.8 package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to 5.8.0-49, on a laprtop with intel graphics, graphics was 
suddenly extremely glitchy.
  Icons from the desktop flash through the browser, windows top bar gets 
distorted, all sort of glitches appear, parts of characters are missing in 
terminal, scrolling is inconsistent and the whole desktop becomes unusable.
  Under wayland the graphics are a bit more stable, but lots of glitches appear 
anyway, video reproduction in browser is stuttering and wobbly.
  Booting with previous kernel 5.8.0-48 seems to fix the issues.
  5.8.0-50 is broken as well.

  this is the result of 'sudo lshw -c video' on my hp Elitebook 8470:

  *-display 
 description: VGA compatible controller
 product: 3rd Gen Core processor Graphics Controller
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:33 memory:d400-d43f memory:c000-cfff 
ioport:4000(size=64) memory:c-d

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

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

[Kernel-packages] [Bug 1928028] Re: io_uring02 from ubuntu_ltp_syscalls fails on F/oem-5.6 (timeouted / SIGKILL)

2021-05-17 Thread Stefan Bader

** Changed in: linux-oem-5.6 (Ubuntu)
   Status: New => Invalid

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

Title:
  io_uring02 from ubuntu_ltp_syscalls fails on F/oem-5.6 (timeouted /
  SIGKILL)

Status in ubuntu-kernel-tests:
  New
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 source package in Focal:
  In Progress

Bug description:
  [Impact]
  When using async io_uring OP_SENDMSG, a copy to kernel address 0 might be 
attempted, leading to a kernel WARN/BUG and an uninterruptible process.

  [Fix]
  Partial backport of dd821e0c95a64b5923a0c57f07d3f7563553e756 ("io_uring: fix 
missing msg_name assignment"). The recvmsg side does not seed to set msg_name, 
as it copies from a local/stack kernel address (at sys_recvmsg) to a uaddr 
parameter, which is given when doing the copy_msghdr operation.

  [Test case]
  LTP io_uring02 was run, and an equivalent recvmsg test was done too. A 
successfull sendmsg test (without the chroot at io_uring02 test) was also 
tested.

  [Potential regressions]
  io_uring sendmsg/recvmsg paths could fail, potentially leading to a system 
crash or even a security vulnerability.

  
  ---

  
  io_uring02 from ubuntu_ltp_syscalls fails on F/oem-5.6 5.6.0-1056.60 on host 
spitfire

  This test isn't found to be ran on previous versions on F/oem-5.6, so
  would not consider this to be a regression.

  26934.05/07 14:42:48 DEBUG| utils:0153| [stdout] tag=io_uring01 
stime=1620398217 dur=0 exit=exited stat=0 core=no cu=0 cs=0
  26935.05/07 14:42:48 DEBUG| utils:0153| [stdout] startup='Fri May 7 
14:36:57 2021'
  26936.05/07 14:42:48 DEBUG| utils:0153| [stdout] tst_test.c:1311: 
TINFO: Timeout per run is 0h 05m 00s
  26937.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted, 
sending SIGKILL!
  26938.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted, 
sending SIGKILL!
  26939.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted, 
sending SIGKILL!
  26940.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted, 
sending SIGKILL!
  26941.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted, 
sending SIGKILL!
  26942.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted, 
sending SIGKILL!
  26943.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted, 
sending SIGKILL!
  26944.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted, 
sending SIGKILL!
  26945.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted, 
sending SIGKILL!
  26946.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted, 
sending SIGKILL!
  26947.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted, 
sending SIGKILL!
  26948.05/07 14:42:48 DEBUG| utils:0153| [stdout] Cannot kill test 
processes!
  26949.05/07 14:42:48 DEBUG| utils:0153| [stdout] Congratulation, 
likely test hit a kernel bug.
  26950.05/07 14:42:48 DEBUG| utils:0153| [stdout] Exitting uncleanly...
  26951.05/07 14:42:48 DEBUG| utils:0153| [stdout] tag=io_uring02 
stime=1620398217 dur=350 exit=exited stat=1 core=no cu=0 cs=0

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

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

[Kernel-packages] [Bug 1923557] Re: CirrusLogic: The default input volume is "0%"

2021-05-17 Thread You-Sheng Yang

verify version 5.10.0-1027.28 from focal-proposed.

** Tags removed: verification-needed-focal
** Tags added: verification-done-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/1923557

Title:
  CirrusLogic: The default input volume is "0%"

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

Bug description:
  [SRU Justification]

  [Impact]

  On some platforms with Cirrus CS8409 audio codec, DMIC volume default
  value in kernel driver is 0, which follows no audio sound will be played
  during installation and OOBE until being explicitly configured again via
  GNOME Settings GUI or other methods.

  [Fix]

  Commit 0e853a9c3937 ("ALSA: hda/cirrus: Set Initial DMIC volume for
  Bullseye to -26 dB") currently landed in upstream tiwai/sound.git is
  required this address this issue. It's also being proposed to v5.13
  merge window.

  [Test Case]

  Try to remove all the user space settings caches and reboot. The
  detailed steps are:

$ sudo systemctl disable alsa-restore.service
$ sudo rm /var/lib/alsa/asound.state
$ sudo reboot
$ amixer sget 'Internal Mic',0
Simple mixer control 'Internal Mic',0
  Capabilities: cvolume cswitch
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 63
  Front Left: Capture 0 [0%] [-51.00dB] [off]
  Front Right: Capture 0 [0%] [-51.00dB] [off]

  Expect 40% in the front left/right capture volumes.

  [Where problems could occur]

  This gives the default value of Cirrus CS8409 audio codec capture volume
  on Bullseye only. Cannot come out with any side effect it may produce so
  far.

  [Other Info]

  By SRU we skipped a couple of refactoring changes in asound upstream
  tree, so additional changes to the original patch are required to
  backport.

  == original bug description ==

  The initial default input volume right after Ubuntu installation is
  set to 0% while 16% is expected.

  $ amixer
  ...
  Simple mixer control 'Internal Mic',0
    Capabilities: cvolume cswitch
    Capture channels: Front Left - Front Right
    Limits: Capture 0 - 63
    Front Left: Capture 0 [0%] [-51.00dB] [off]
    Front Right: Capture 0 [0%] [-51.00dB] [off]
  Simple mixer control 'Internal Mic Boost',0
    Capabilities: volume
    Playback channels: Front Left - Front Right
    Capture channels: Front Left - Front Right
    Limits: 0 - 2
    Front Left: 0 [0%] [0.00dB]
    Front Right: 0 [0%] [0.00dB]

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1523 F pulseaudio
  CasperMD5CheckResult: skip
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-proposed-release+X90
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-04-13 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. 
FingerPrint
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Vostro 3500
  Package: linux-oem-5.10
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem 
root=UUID=c666f936-5b87-4cbd-bde6-21fa93b89036 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1020-oem N/A
   linux-backports-modules-5.10.0-1020-oem  N/A
   linux-firmware   1.187.10
  Tags:  focal
  Uname: Linux 5.10.0-1020-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/02/2021
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.2
  dmi.board.name: 09YKK0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias:

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

This change was made by a bot.

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

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

Title:
  Can not wake up after sleep using 5.4.0-73-generic, but
  5.4.0-65-generic works fine

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm having trouble waking up my computer which was previously in sleep mode.
  I'm using a Dell Optiplex 5040 computer, an Intel Core i5 6400 with Kubuntu 
20.04, and the linux kernel version-image-5.4.0-73-generic,
  then I tried to switch to kernel version linux-image-5.4.0-65-generic and the 
problem was resolved.
  I hope this problem can be resolved in the next kernel update.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon May 17 05:37:17 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:06ba]
  InstallationDate: Installed on 2021-01-26 (110 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1a2c:45e8 China Resource Semico Co., Ltd USB Keyboard
   Bus 001 Device 002: ID 04d9:a09f Holtek Semiconductor, Inc. E-Signal LUOM 
G10 Mechanical Gaming Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. OptiPlex 5040
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic 
root=UUID=eb4d1ced-011f-46f8-8f11-bffe7b376911 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.17.1
  dmi.board.name: 0T7D40
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: RCPU006375
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.17.1:bd12/23/2020:svnDellInc.:pnOptiPlex5040:pvr:rvnDellInc.:rn0T7D40:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: OptiPlex
  dmi.product.name: OptiPlex 5040
  dmi.product.sku: 06BA
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-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/1928607/+subscriptions

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

[Kernel-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x

Testing former status with 5.11.0-17-generic

Journal:
Add:
May 17 05:56:26 h kernel: crw_info : CRW reports slct=0, oflw=0, chn=1, rsc=3, 
anc=0, erc=4, rsid=5
May 17 05:56:26 h kernel: crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3, 
anc=0, erc=4, rsid=0
May 17 05:56:26 h kernel: virtio_blk virtio5: [vdc] 385 512-byte logical blocks 
(197 kB/193 KiB)
Remove:
May 17 05:56:35 h kernel: crw_info : CRW reports slct=0, oflw=0, chn=1, rsc=3, 
anc=0, erc=4, rsid=5
May 17 05:56:35 h kernel: crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3, 
anc=0, erc=4, rsid=0

ubuntu@s1lp5:~$ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc
Disk attached successfully

ubuntu@s1lp5:~$ virsh detach-disk h vdc
Disk detached successfully

ubuntu@s1lp5:~$ virsh domblklist h
 Target   Source

 vda  /var/lib/uvtool/libvirt/images/h.qcow
 vdb  /var/lib/uvtool/libvirt/images/h-ds.qcow

ubuntu@s1lp5:~$ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk
uvt-kvm: error: libvirt: Domain not found: no domain with matching name 
'hirsute-2nd-zfs'
ubuntu@s1lp5:~$ uvt-kvm ssh --insecure h lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop07:00  47.9M  1 loop /snap/core18/1998
loop17:10  29.9M  1 loop /snap/snapd/11838
loop27:20  63.1M  1 loop /snap/lxd/20396
vda252:00 8G  0 disk 
└─vda1 252:10 8G  0 part /
vdb252:16   0   372K  0 disk 
vdc252:32   0 192.5K  0 disk 


The disk is still present despite not really being in the guest anymore.

Now testing the proposed kernel 5.11.0-18-generic

Upgrades fine, well triggering an unrelated bug 1928625 but fine in
regard to the issue here.

Then journal (as expected) looks the same:
# Attach
May 17 06:09:22 h kernel: crw_info : CRW reports slct=0, oflw=0, chn=1, rsc=3, 
anc=0, erc=4, rsid=5
May 17 06:09:22 h kernel: crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3, 
anc=0, erc=4, rsid=0
May 17 06:09:22 h kernel: virtio_blk virtio5: [vdc] 385 512-byte logical blocks 
(197 kB/193 KiB)
# Detach
May 17 06:09:29 h kernel: crw_info : CRW reports slct=0, oflw=0, chn=1, rsc=3, 
anc=0, erc=4, rsid=5
May 17 06:09:29 h kernel: crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3, 
anc=0, erc=4, rsid=0


But lsblk confirms that the new kernel now works:
ubuntu@s1lp5:~$ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc
Disk attached successfully

ubuntu@s1lp5:~$ virsh detach-disk h vdc
Disk detached successfully

ubuntu@s1lp5:~$ virsh domblklist h
 Target   Source

 vda  /var/lib/uvtool/libvirt/images/h.qcow
 vdb  /var/lib/uvtool/libvirt/images/h-ds.qcow

ubuntu@s1lp5:~$ uvt-kvm ssh --insecure h lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
loop07:00 63.1M  1 loop /snap/lxd/20396
loop17:10 29.9M  1 loop /snap/snapd/11838
loop27:20 47.9M  1 loop /snap/core18/1998
vda252:008G  0 disk 
└─vda1 252:108G  0 part /
vdb252:16   0  372K  0 disk 


^^ no more vdc after the detach.
Setting verified

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

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

Title:
  Hot-unplug of disks leaves broken block devices around in Hirsute on
  s390x

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Invalid
Status in udev package in Ubuntu:
  Invalid
Status in linux source package in Hirsute:
  Fix Committed
Status in systemd source package in Hirsute:
  Invalid
Status in udev source package in Hirsute:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  Hot removal of disks under kvm on s390 does not result in the kernel
  removing the block device, which can lead to hung tasks and other
  issues.

  [Test Plan]

  See steps to reproduce the bug in the original description below. To
  test, execute these steps and confirm that the block device gets
  removed as expected.

  [Where problems could occur]

  The fix is a revert of the changes which introduced this regression.
  The original commit was a removal of supposedly unused code, but it
  seems a mistake was made in the logic around unregistering of disks.
  Reverting the changes could have potential to introduce bugs related
  to other virt devices, especially if it interacts badly with
  subsequent driver changes. However, the patch reverted cleanly, and
  reverting restores the code to the state which has been working well
  in previous kernels and seems like the lowest risk option until a
  proper fix is available upstream.

  ---

  Repro:
  #1 Get a guest
  $ uvt-kvm create --disk 5  --password=ubuntu h release=hirsute arch=s390x 
label=daily
  $ uvt-kvm wait h release=hirsute arch=s390x label=daily

  #2 Attach and Detach disk
  $

[Kernel-packages] [Bug 1928625] UdevDb.txt

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

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1928625/+attachment/5498152/+files/UdevDb.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/1928625

Title:
  hirsute s390x kernel upgrade reports placeholder

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

Bug description:
  I was upgrading Hirsute to hirsute-proposed and got this text:

  "
  Pending kernel upgrade
  Newer kernel available
 
  The currently running kernel version is 5.11.0-17-generic which is not the 
expected kernel version %s.
  Restarting the system to load the new kernel will not be handled 
automatically, so you should consider rebooting.
  "

  One would expect the %s to be replaced, but it isn't

  The new kernel was:
  Processing triggers for linux-image-5.11.0-18-generic (5.11.0-18.19) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.11.0-18-generic

  I don't know if this is a s390x-kernel (not having the right data set)
  or a needrestart (fail to probe version on s390x) issue so I'm filing
  it against both.

  Repro:
  1. get a s390x system (KVM guest is fine, no need for an LPAR)
  2. install hirsute
  3. upgrade the kernel
  --- 
  ProblemType: Bug
  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.11-0ubuntu65
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 21.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: 
/sys/bus/usb/devices: No such file or directory
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  Package: needrestart 3.5-2ubuntu2
  PackageArchitecture: all
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: root=LABEL=cloudimg-rootfs
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-18-generic N/A
   linux-backports-modules-5.11.0-18-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  hirsute uec-images
  Uname: Linux 5.11.0-18-generic s390x
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:

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

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

[Kernel-packages] [Bug 1928625] WifiSyslog.txt

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

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1928625/+attachment/5498153/+files/WifiSyslog.txt

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

Title:
  hirsute s390x kernel upgrade reports placeholder

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

Bug description:
  I was upgrading Hirsute to hirsute-proposed and got this text:

  "
  Pending kernel upgrade
  Newer kernel available
 
  The currently running kernel version is 5.11.0-17-generic which is not the 
expected kernel version %s.
  Restarting the system to load the new kernel will not be handled 
automatically, so you should consider rebooting.
  "

  One would expect the %s to be replaced, but it isn't

  The new kernel was:
  Processing triggers for linux-image-5.11.0-18-generic (5.11.0-18.19) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.11.0-18-generic

  I don't know if this is a s390x-kernel (not having the right data set)
  or a needrestart (fail to probe version on s390x) issue so I'm filing
  it against both.

  Repro:
  1. get a s390x system (KVM guest is fine, no need for an LPAR)
  2. install hirsute
  3. upgrade the kernel
  --- 
  ProblemType: Bug
  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.11-0ubuntu65
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 21.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: 
/sys/bus/usb/devices: No such file or directory
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  Package: needrestart 3.5-2ubuntu2
  PackageArchitecture: all
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: root=LABEL=cloudimg-rootfs
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-18-generic N/A
   linux-backports-modules-5.11.0-18-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  hirsute uec-images
  Uname: Linux 5.11.0-18-generic s390x
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:

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

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

[Kernel-packages] [Bug 1928625] Re: hirsute s390x kernel upgrade reports placeholder

2021-05-17 Thread Frank Heimes

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

** This bug has been marked a duplicate of bug 1925488
   needrestart msg "The currently running kernel version is 5.11.0-16-generic 
which is not the expected kernel version %s"

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

Title:
  hirsute s390x kernel upgrade reports placeholder

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

Bug description:
  I was upgrading Hirsute to hirsute-proposed and got this text:

  "
  Pending kernel upgrade
  Newer kernel available
 
  The currently running kernel version is 5.11.0-17-generic which is not the 
expected kernel version %s.
  Restarting the system to load the new kernel will not be handled 
automatically, so you should consider rebooting.
  "

  One would expect the %s to be replaced, but it isn't

  The new kernel was:
  Processing triggers for linux-image-5.11.0-18-generic (5.11.0-18.19) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.11.0-18-generic

  I don't know if this is a s390x-kernel (not having the right data set)
  or a needrestart (fail to probe version on s390x) issue so I'm filing
  it against both.

  Repro:
  1. get a s390x system (KVM guest is fine, no need for an LPAR)
  2. install hirsute
  3. upgrade the kernel
  --- 
  ProblemType: Bug
  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.11-0ubuntu65
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 21.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: 
/sys/bus/usb/devices: No such file or directory
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  Package: needrestart 3.5-2ubuntu2
  PackageArchitecture: all
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: root=LABEL=cloudimg-rootfs
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-18-generic N/A
   linux-backports-modules-5.11.0-18-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  hirsute uec-images
  Uname: Linux 5.11.0-18-generic s390x
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:

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

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

[Kernel-packages] [Bug 1910976] Re: Cherry-pick dm-crypt performance improvement patch from Linux 5.9

2021-05-17 Thread gerald.yang

** Description changed:

+ === SRU Justification ===
+ [Impact]
+ To get better performance for dm-crypt in some cases, bypass kcryptd 
workqueue can reduce the overhead in context switch between workers, 
cherry-pick commit 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 from mainline 
kernel, and this is not enabled by default
+ 
+ [Fix]
+ Add flags to bypass kcryptd workqueue
+ 
+ [Test]
+ create dm-crypt and setup DM_CRYPT_NO_READ_WORKQUEUE and 
DM_CRYPT_NO_WRITE_WORKQUEUE, read/write data and run perf record to see if 
read/write to the encrypted device will bypass kcryptd workqueue
+ 
+ [Regression Potential]
+ Low, this feature is disabled by default, need to enable manually
+ 
+ = original bug description =
  Hi,
  
  I'm asking if it would be possible to cherry-pick patch "dm crypt: add
  flags to optionally bypass kcryptd workqueues" into the 5.4 Ubuntu
  kernel. This patch has been merged in mainline kernel 5.9
  
https://github.com/torvalds/linux/commit/39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877
  but was not tagged for the stable tree.
  
  This patch provides important performance gains for some workloads using
  dm-crypt / LUKS and cherry-picking it would be very beneficial for dm-
  crypt users. You can find details on the expected gain in the following
  links:
  
  * https://www.redhat.com/archives/dm-devel/2020-July/msg00138.html
  * https://blog.cloudflare.com/speeding-up-linux-disk-encryption/
  
  The patch mostly applies cleanly on the Ubuntu 5.4 kernel, the only
  merge conflict is due to the module version at the end of the patch. I
  can provide a backport patch if needed.
  
  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/1910976

Title:
  Cherry-pick dm-crypt performance improvement patch from Linux 5.9

Status in linux package in Ubuntu:
  In Progress

Bug description:
  === SRU Justification ===
  [Impact]
  To get better performance for dm-crypt in some cases, bypass kcryptd 
workqueue can reduce the overhead in context switch between workers, 
cherry-pick commit 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 from mainline 
kernel, and this is not enabled by default

  [Fix]
  Add flags to bypass kcryptd workqueue

  [Test]
  create dm-crypt and setup DM_CRYPT_NO_READ_WORKQUEUE and 
DM_CRYPT_NO_WRITE_WORKQUEUE, read/write data and run perf record to see if 
read/write to the encrypted device will bypass kcryptd workqueue

  [Regression Potential]
  Low, this feature is disabled by default, need to enable manually

  = original bug description =
  Hi,

  I'm asking if it would be possible to cherry-pick patch "dm crypt: add
  flags to optionally bypass kcryptd workqueues" into the 5.4 Ubuntu
  kernel. This patch has been merged in mainline kernel 5.9
  
https://github.com/torvalds/linux/commit/39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877
  but was not tagged for the stable tree.

  This patch provides important performance gains for some workloads
  using dm-crypt / LUKS and cherry-picking it would be very beneficial
  for dm-crypt users. You can find details on the expected gain in the
  following links:

  * https://www.redhat.com/archives/dm-devel/2020-July/msg00138.html
  * https://blog.cloudflare.com/speeding-up-linux-disk-encryption/

  The patch mostly applies cleanly on the Ubuntu 5.4 kernel, the only
  merge conflict is due to the module version at the end of the patch. I
  can provide a backport patch if needed.

  Thanks,

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

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

[Kernel-packages] [Bug 1928625] ProcModules.txt

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

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1928625/+attachment/5498151/+files/ProcModules.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/1928625

Title:
  hirsute s390x kernel upgrade reports placeholder

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

Bug description:
  I was upgrading Hirsute to hirsute-proposed and got this text:

  "
  Pending kernel upgrade
  Newer kernel available
 
  The currently running kernel version is 5.11.0-17-generic which is not the 
expected kernel version %s.
  Restarting the system to load the new kernel will not be handled 
automatically, so you should consider rebooting.
  "

  One would expect the %s to be replaced, but it isn't

  The new kernel was:
  Processing triggers for linux-image-5.11.0-18-generic (5.11.0-18.19) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.11.0-18-generic

  I don't know if this is a s390x-kernel (not having the right data set)
  or a needrestart (fail to probe version on s390x) issue so I'm filing
  it against both.

  Repro:
  1. get a s390x system (KVM guest is fine, no need for an LPAR)
  2. install hirsute
  3. upgrade the kernel
  --- 
  ProblemType: Bug
  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.11-0ubuntu65
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 21.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: 
/sys/bus/usb/devices: No such file or directory
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  Package: needrestart 3.5-2ubuntu2
  PackageArchitecture: all
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: root=LABEL=cloudimg-rootfs
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-18-generic N/A
   linux-backports-modules-5.11.0-18-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  hirsute uec-images
  Uname: Linux 5.11.0-18-generic s390x
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:

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

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

[Kernel-packages] [Bug 1928625] ProcInterrupts.txt

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

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1928625/+attachment/5498150/+files/ProcInterrupts.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/1928625

Title:
  hirsute s390x kernel upgrade reports placeholder

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

Bug description:
  I was upgrading Hirsute to hirsute-proposed and got this text:

  "
  Pending kernel upgrade
  Newer kernel available
 
  The currently running kernel version is 5.11.0-17-generic which is not the 
expected kernel version %s.
  Restarting the system to load the new kernel will not be handled 
automatically, so you should consider rebooting.
  "

  One would expect the %s to be replaced, but it isn't

  The new kernel was:
  Processing triggers for linux-image-5.11.0-18-generic (5.11.0-18.19) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.11.0-18-generic

  I don't know if this is a s390x-kernel (not having the right data set)
  or a needrestart (fail to probe version on s390x) issue so I'm filing
  it against both.

  Repro:
  1. get a s390x system (KVM guest is fine, no need for an LPAR)
  2. install hirsute
  3. upgrade the kernel
  --- 
  ProblemType: Bug
  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.11-0ubuntu65
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 21.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: 
/sys/bus/usb/devices: No such file or directory
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  Package: needrestart 3.5-2ubuntu2
  PackageArchitecture: all
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: root=LABEL=cloudimg-rootfs
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-18-generic N/A
   linux-backports-modules-5.11.0-18-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  hirsute uec-images
  Uname: Linux 5.11.0-18-generic s390x
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:

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

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

[Kernel-packages] [Bug 1928625] AudioDevicesInUse.txt

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

apport information

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/1928625/+attachment/5498145/+files/AudioDevicesInUse.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/1928625

Title:
  hirsute s390x kernel upgrade reports placeholder

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

Bug description:
  I was upgrading Hirsute to hirsute-proposed and got this text:

  "
  Pending kernel upgrade
  Newer kernel available
 
  The currently running kernel version is 5.11.0-17-generic which is not the 
expected kernel version %s.
  Restarting the system to load the new kernel will not be handled 
automatically, so you should consider rebooting.
  "

  One would expect the %s to be replaced, but it isn't

  The new kernel was:
  Processing triggers for linux-image-5.11.0-18-generic (5.11.0-18.19) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.11.0-18-generic

  I don't know if this is a s390x-kernel (not having the right data set)
  or a needrestart (fail to probe version on s390x) issue so I'm filing
  it against both.

  Repro:
  1. get a s390x system (KVM guest is fine, no need for an LPAR)
  2. install hirsute
  3. upgrade the kernel
  --- 
  ProblemType: Bug
  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.11-0ubuntu65
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 21.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: 
/sys/bus/usb/devices: No such file or directory
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  Package: needrestart 3.5-2ubuntu2
  PackageArchitecture: all
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: root=LABEL=cloudimg-rootfs
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-18-generic N/A
   linux-backports-modules-5.11.0-18-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  hirsute uec-images
  Uname: Linux 5.11.0-18-generic s390x
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:

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

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

[Kernel-packages] [Bug 1928625] ProcEnviron.txt

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

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1928625/+attachment/5498149/+files/ProcEnviron.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/1928625

Title:
  hirsute s390x kernel upgrade reports placeholder

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

Bug description:
  I was upgrading Hirsute to hirsute-proposed and got this text:

  "
  Pending kernel upgrade
  Newer kernel available
 
  The currently running kernel version is 5.11.0-17-generic which is not the 
expected kernel version %s.
  Restarting the system to load the new kernel will not be handled 
automatically, so you should consider rebooting.
  "

  One would expect the %s to be replaced, but it isn't

  The new kernel was:
  Processing triggers for linux-image-5.11.0-18-generic (5.11.0-18.19) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.11.0-18-generic

  I don't know if this is a s390x-kernel (not having the right data set)
  or a needrestart (fail to probe version on s390x) issue so I'm filing
  it against both.

  Repro:
  1. get a s390x system (KVM guest is fine, no need for an LPAR)
  2. install hirsute
  3. upgrade the kernel
  --- 
  ProblemType: Bug
  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.11-0ubuntu65
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 21.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: 
/sys/bus/usb/devices: No such file or directory
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  Package: needrestart 3.5-2ubuntu2
  PackageArchitecture: all
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: root=LABEL=cloudimg-rootfs
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-18-generic N/A
   linux-backports-modules-5.11.0-18-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  hirsute uec-images
  Uname: Linux 5.11.0-18-generic s390x
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:

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

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

[Kernel-packages] [Bug 1928625] ProcCpuinfoMinimal.txt

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

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1928625/+attachment/5498148/+files/ProcCpuinfoMinimal.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/1928625

Title:
  hirsute s390x kernel upgrade reports placeholder

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

Bug description:
  I was upgrading Hirsute to hirsute-proposed and got this text:

  "
  Pending kernel upgrade
  Newer kernel available
 
  The currently running kernel version is 5.11.0-17-generic which is not the 
expected kernel version %s.
  Restarting the system to load the new kernel will not be handled 
automatically, so you should consider rebooting.
  "

  One would expect the %s to be replaced, but it isn't

  The new kernel was:
  Processing triggers for linux-image-5.11.0-18-generic (5.11.0-18.19) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.11.0-18-generic

  I don't know if this is a s390x-kernel (not having the right data set)
  or a needrestart (fail to probe version on s390x) issue so I'm filing
  it against both.

  Repro:
  1. get a s390x system (KVM guest is fine, no need for an LPAR)
  2. install hirsute
  3. upgrade the kernel
  --- 
  ProblemType: Bug
  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.11-0ubuntu65
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 21.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: 
/sys/bus/usb/devices: No such file or directory
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  Package: needrestart 3.5-2ubuntu2
  PackageArchitecture: all
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: root=LABEL=cloudimg-rootfs
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-18-generic N/A
   linux-backports-modules-5.11.0-18-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  hirsute uec-images
  Uname: Linux 5.11.0-18-generic s390x
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:

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

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

[Kernel-packages] [Bug 1928625] [NEW] hirsute s390x kernel upgrade reports placeholder

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

Public bug reported:

I was upgrading Hirsute to hirsute-proposed and got this text:

"
Pending kernel upgrade
Newer kernel available  
   
The currently running kernel version is 5.11.0-17-generic which is not the 
expected kernel version %s.
Restarting the system to load the new kernel will not be handled automatically, 
so you should consider rebooting.
"

One would expect the %s to be replaced, but it isn't

The new kernel was:
Processing triggers for linux-image-5.11.0-18-generic (5.11.0-18.19) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.11.0-18-generic

I don't know if this is a s390x-kernel (not having the right data set)
or a needrestart (fail to probe version on s390x) issue so I'm filing it
against both.

Repro:
1. get a s390x system (KVM guest is fine, no need for an LPAR)
2. install hirsute
3. upgrade the kernel
--- 
ProblemType: Bug
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.11-0ubuntu65
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: N/A
CasperMD5CheckResult: unknown
DistroRelease: Ubuntu 21.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci:
 
Lspci-vt: -[:00]-
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: 
/sys/bus/usb/devices: No such file or directory
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
Package: needrestart 3.5-2ubuntu2
PackageArchitecture: all
PciMultimedia:
 
ProcFB:
 
ProcKernelCmdLine: root=LABEL=cloudimg-rootfs
ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-18-generic N/A
 linux-backports-modules-5.11.0-18-generic  N/A
 linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
Tags:  hirsute uec-images
Uname: Linux 5.11.0-18-generic s390x
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
acpidump:

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

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


** Tags: apport-collected hirsute uec-images

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

** Tags added: apport-collected hirsute uec-images

** Description changed:

  I was upgrading Hirsute to hirsute-proposed and got this text:
  
  "
  Pending kernel upgrade
  Newer kernel available
 
  The currently running kernel version is 5.11.0-17-generic which is not the 
expected kernel version %s.
  Restarting the system to load the new kernel will not be handled 
automatically, so you should consider rebooting.
  "
  
  One would expect the %s to be replaced, but it isn't
  
  The new kernel was:
  Processing triggers for linux-image-5.11.0-18-generic (5.11.0-18.19) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.11.0-18-generic
  
  I don't know if this is a s390x-kernel (not having the right data set)
  or a needrestart (fail to probe version on s390x) issue so I'm filing it
  against both.
  
  Repro:
  1. get a s390x system (KVM guest is fine, no need for an LPAR)
  2. install hirsute
  3. upgrade the kernel
+ --- 
+ ProblemType: Bug
+ 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.11-0ubuntu65
+ Architecture: s390x
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
+ CRDA: N/A
+ CasperMD5CheckResult: unknown
+ DistroRelease: Ubuntu 21.04
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
+ Lspci:
+  
+ Lspci-vt: -[:00]-
+ Lsusb: Error: command ['lsusb'] failed with exit code 1:
+ Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: 
/sys/bus/usb/devices: No such file or directory
+ Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
+ Package: needrestart 3.5-2ubuntu2
+ PackageArchitecture: all
+ PciMultimedia:
+  
+ ProcFB:
+  
+ ProcKernelCmdLine: root=LABEL=cloudimg-rootfs
+ ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
+ RelatedPackageVersions:
+  linux-restricted-modules-5.11.0-18-generic N/A
+  linux-backports-modules-5.11.0-18-generic  N/A
+  linux-firmware N/A
+ RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
+

[Kernel-packages] [Bug 1928625] CurrentDmesg.txt

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

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1928625/+attachment/5498146/+files/CurrentDmesg.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/1928625

Title:
  hirsute s390x kernel upgrade reports placeholder

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

Bug description:
  I was upgrading Hirsute to hirsute-proposed and got this text:

  "
  Pending kernel upgrade
  Newer kernel available
 
  The currently running kernel version is 5.11.0-17-generic which is not the 
expected kernel version %s.
  Restarting the system to load the new kernel will not be handled 
automatically, so you should consider rebooting.
  "

  One would expect the %s to be replaced, but it isn't

  The new kernel was:
  Processing triggers for linux-image-5.11.0-18-generic (5.11.0-18.19) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.11.0-18-generic

  I don't know if this is a s390x-kernel (not having the right data set)
  or a needrestart (fail to probe version on s390x) issue so I'm filing
  it against both.

  Repro:
  1. get a s390x system (KVM guest is fine, no need for an LPAR)
  2. install hirsute
  3. upgrade the kernel
  --- 
  ProblemType: Bug
  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.11-0ubuntu65
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 21.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: 
/sys/bus/usb/devices: No such file or directory
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  Package: needrestart 3.5-2ubuntu2
  PackageArchitecture: all
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: root=LABEL=cloudimg-rootfs
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-18-generic N/A
   linux-backports-modules-5.11.0-18-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  hirsute uec-images
  Uname: Linux 5.11.0-18-generic s390x
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:

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

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

[Kernel-packages] [Bug 1928625] Dependencies.txt

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

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1928625/+attachment/5498147/+files/Dependencies.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/1928625

Title:
  hirsute s390x kernel upgrade reports placeholder

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

Bug description:
  I was upgrading Hirsute to hirsute-proposed and got this text:

  "
  Pending kernel upgrade
  Newer kernel available
 
  The currently running kernel version is 5.11.0-17-generic which is not the 
expected kernel version %s.
  Restarting the system to load the new kernel will not be handled 
automatically, so you should consider rebooting.
  "

  One would expect the %s to be replaced, but it isn't

  The new kernel was:
  Processing triggers for linux-image-5.11.0-18-generic (5.11.0-18.19) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.11.0-18-generic

  I don't know if this is a s390x-kernel (not having the right data set)
  or a needrestart (fail to probe version on s390x) issue so I'm filing
  it against both.

  Repro:
  1. get a s390x system (KVM guest is fine, no need for an LPAR)
  2. install hirsute
  3. upgrade the kernel
  --- 
  ProblemType: Bug
  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.11-0ubuntu65
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 21.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: 
/sys/bus/usb/devices: No such file or directory
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  Package: needrestart 3.5-2ubuntu2
  PackageArchitecture: all
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: root=LABEL=cloudimg-rootfs
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-18-generic N/A
   linux-backports-modules-5.11.0-18-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  hirsute uec-images
  Uname: Linux 5.11.0-18-generic s390x
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:

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

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

[Kernel-packages] [Bug 1837810] Re: KVM: Fix zero_page reference counter overflow when using KSM on KVM compute host

2021-05-17 Thread Matthew Ruffell

Hi Jiatong,

Thanks for emailing me, happy to answer questions anytime.

> 1. why linux-hwe-4.15.0 source code is used?

If you look closely at the oops in the description, the customer I was
working with was running:

4.15.0-106-generic #107~16.04.1-Ubuntu
 
This is the Xenial (16.04) HWE kernel. I was using the linux-hwe-4.15.0 source 
code to make sure the debug symbols used for the debug symbol package matched 
exactly.

In your case:

4.15.0-72-generic #81-Ubuntu

you are running the 4.15 kernel on normal Bionic (18.04), so we can use
the normal linux-4.15.0 source code.

> 2. we are using linux-4.15.0-unsigned and by skimming through the
source code, looks like try_get_page is not defined at that time?

Yes! You are correct, the original mainline 4.15 kernel did not have
try_get_page() defined at:

https://elixir.bootlin.com/linux/v4.15/source/mm/gup.c#L156

But if you look closely at the actual kernel sources for
4.15.0-72-generic:

https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/bionic/tree/mm/gup.c?h=Ubuntu-4.15.0-72.81#n156

We see that try_get_page() is there. That is because we backported:

commit 8fde12ca79aff9b5ba951fce1a2641901b8d8e64
Author: Linus Torvalds 
Date:   Thu Apr 11 10:49:19 2019 -0700
Subject: mm: prevent get_user_pages() from overflowing page refcount
Link:https://github.com/torvalds/linux/commit/8fde12ca79aff9b5ba951fce1a2641901b8d8e64

Ubuntu 4.15 backport link: https://paste.ubuntu.com/p/2bF5WWQy2r/

That commit first turned up in 4.15.0-59-generic, via upstream-stable.

Anyway, let's have a look at your stack trace:

4.15.0-72-generic #81-Ubuntu
RIP: 0010:follow_page_pte+0x663/0x6d0

I downloaded the debug symbols:

http://ddebs.ubuntu.com/ubuntu/pool/main/l/linux/linux-image-
unsigned-4.15.0-72-generic-dbgsym_4.15.0-72.81_amd64.ddeb

Extracted them:

dpkg -x linux-image-unsigned-4.15.0-72-generic-
dbgsym_4.15.0-72.81_amd64.ddeb debug

and looked up:

$ eu-addr2line -e ./vmlinux-4.15.0-72-generic -f follow_page_pte+0x663
try_get_page inlined at /build/linux-E6MDAa/linux-4.15.0/mm/gup.c:156 in 
follow_page_pte
/build/linux-E6MDAa/linux-4.15.0/mm/gup.c:138

We see that you hit try_get_page() in mm/gup.c:156

 155 if (flags & FOLL_GET) {
 156 if (unlikely(!try_get_page(page))) {
 157 page = ERR_PTR(-ENOMEM);
 158 goto out;
 159 }
 
Looking at try_get_page() in include/linux/mm.h:

 854 static inline __must_check bool try_get_page(struct page *page)
 855 {
 856 page = compound_head(page);
 857 if (WARN_ON_ONCE(page_ref_count(page) <= 0))
 858 return false;
 859 page_ref_inc(page);
 860 return true;
 861 }
 
We see that you hit the exact same WARN_ON_ONCE for the page_ref_count(page) <= 
0).

So, whatever page you are trying to access, has its reference counter in
the negatives, which suggests that has either wrapped around, or has
been decremented too many times.

Looking at your error log, I can't tell for sure if it is the zero_page,
but its quite likely going to be. The zero_page is a frequently used
page in the system, and it is used outside of ksm, it's just that ksm is
a heavy user of the zero_page. If you are constantly allocating large
amounts of new memory, you will be be using the zero_page similar to
ksm, and the reference counter will eventually overflow.

I think there is a good chance that the fix I submitted in
4.15.0-118-generic will solve your problems. Please do a "apt update"
and "apt upgrade" and upgrade to a newer kernel, the newer the better,
and it will most likely fix the problem.

Let me know if you have any more questions.

Thanks,
Matthew

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

Title:
  KVM: Fix zero_page reference counter overflow when using KSM on KVM
  compute host

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

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

  [Impact]

  We are seeing a problem on OpenStack compute nodes, and KVM hosts,
  where a kernel oops is generated, and all running KVM machines are
  placed into the pause state.

  This is caused by the kernel's reserved zero_page reference counter
  overflowing from a positive number to a negative number, and hitting a
  (WARN_ON_ONCE(page_ref_count(page) <= 0)) condition in try_get_page().

  This only happens if the machine has Kernel Samepage Mapping (KSM)
  enabled, with "use_zero_pages" turned on. Each time a new VM starts
  and the kernel does a KSM merge run during a EPT violation, the
  reference counter for the zero_page is incremented in try_async_pf()
  and never decremented. Eventually, the reference counter will
  overflow, causing the KVM subsystem to fail.

  Syslog:
  error : qemuMonitorJSONCheckError:392 : internal error:

[Kernel-packages] [Bug 1928607] Re: Can not wake up after sleep using 5.4.0-73-generic, but 5.4.0-65-generic works fine

** Summary changed:

- Can not wake up after sleep.
+ Can not wake up after sleep using 5.4.0-73-generic, but 5.4.0-65-generic 
works fine

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

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

Title:
  Can not wake up after sleep using 5.4.0-73-generic, but
  5.4.0-65-generic works fine

Status in linux package in Ubuntu:
  New

Bug description:
  I'm having trouble waking up my computer which was previously in sleep mode.
  I'm using a Dell Optiplex 5040 computer, an Intel Core i5 6400 with Kubuntu 
20.04, and the linux kernel version-image-5.4.0-73-generic,
  then I tried to switch to kernel version linux-image-5.4.0-65-generic and the 
problem was resolved.
  I hope this problem can be resolved in the next kernel update.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon May 17 05:37:17 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:06ba]
  InstallationDate: Installed on 2021-01-26 (110 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1a2c:45e8 China Resource Semico Co., Ltd USB Keyboard
   Bus 001 Device 002: ID 04d9:a09f Holtek Semiconductor, Inc. E-Signal LUOM 
G10 Mechanical Gaming Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. OptiPlex 5040
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic 
root=UUID=eb4d1ced-011f-46f8-8f11-bffe7b376911 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.17.1
  dmi.board.name: 0T7D40
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: RCPU006375
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.17.1:bd12/23/2020:svnDellInc.:pnOptiPlex5040:pvr:rvnDellInc.:rn0T7D40:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: OptiPlex
  dmi.product.name: OptiPlex 5040
  dmi.product.sku: 06BA
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-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/1928607/+subscriptions

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

[Kernel-packages] [Bug 1928607] [NEW] Can not wake up after sleep using 5.4.0-73-generic, but 5.4.0-65-generic works fine