[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues

[Bijay Shah]

** Attachment added: "Pulse Audio Output Devices.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+attachment/5501573/+files/Pulse%20Audio%20Output%20Devices.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/1930188

Title:
  Acer Aspire 5 sound driver issues

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  There seems to be lots of issues in sound driver for Acer Aspire
  A515-56-57XR with ALC255. I will list all of them below and what I
  have tried so far.

  1. Headphones appears always plugged in even if they are physically not
  2. When actually plugging in headset/earphones it does not auto switch from 
speakers/internal mic to headphones/headset microphone automatically and vice 
versa, have to manually switch everytime.
  3. External headset/earphones microphone won't work at all

  After, logs of trial and error I have found a temporary fix. This
  seems to use legacy intel drivers which solves all 3 issues mentioned
  above but the internal/dmic mic is completely gone (which seems
  intentional when using this). Both depreciated dmic_detect and
  dsp_driver works, I have been using dsp_driver for now as I need
  external microphone at any cost.

  End of /etc/modprobe.d/alsa-base.conf
  # Headset mic fix
  options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1
  options snd-hda-intel model=alc255-acer

  In another thread similar to this I got some support and at least
  fixed the external microphone without using the alsa-base.conf change
  in custom modified kernel. I will attach it here. Now, hoping to fix
  other issues as well slowly like making headphones unplugged when
  physically removing as well as auto switching like the legacy driver
  one.

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

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

[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues

[Bijay Shah]

I tested this kernel here are my findings.

1. Headphones input/output are unplugged by default now

2. When I physically plug it in and select headphones input/output as
default, from next plug in it auto switches to headphones input/output
from internal input/output and vice versa.

2. Headphones microphone is working fine now, had to set mic boost(seems
to be tied to microphone sensitivity) in alsamixer to max to get good
sensitivity was set to 0 at first.


So, all issues I mentioned above seems to be solved but I have few extra small 
issues and want to get some insights into it before fully marking this thread 
as solved.

1. When internal microphone switches to external headphone microphone,
internal microphone is still on and keeps picking up compared to
internal speakers/headphones output where one or the other is muted
automatically.

2. In the legacy driver when earphones/headphones is plugged in internal
input/output devices shows as unavailable in pulse audio control and
can't be selected in gnome sound settings, in current driver seems like
all devices are active and can be switched without unplugging
headphones/earphones. I am not sure if this is something that needs to
be fixed.

3. I also notice few unplugged hdmi devices in pulse audio control which
are not shown when switching to legacy driver. Like HDMI1/DP1 Output,
HDMI2/DP2 Output, HDMI3/DP3 Output all of them are shown as unplugged.
Also, not sure if this is something that needs to be fixed.

If you could provide some insights on these 3 extra issues would really
appreciate it. Thanks again.

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

Title:
  Acer Aspire 5 sound driver issues

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  There seems to be lots of issues in sound driver for Acer Aspire
  A515-56-57XR with ALC255. I will list all of them below and what I
  have tried so far.

  1. Headphones appears always plugged in even if they are physically not
  2. When actually plugging in headset/earphones it does not auto switch from 
speakers/internal mic to headphones/headset microphone automatically and vice 
versa, have to manually switch everytime.
  3. External headset/earphones microphone won't work at all

  After, logs of trial and error I have found a temporary fix. This
  seems to use legacy intel drivers which solves all 3 issues mentioned
  above but the internal/dmic mic is completely gone (which seems
  intentional when using this). Both depreciated dmic_detect and
  dsp_driver works, I have been using dsp_driver for now as I need
  external microphone at any cost.

  End of /etc/modprobe.d/alsa-base.conf
  # Headset mic fix
  options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1
  options snd-hda-intel model=alc255-acer

  In another thread similar to this I got some support and at least
  fixed the external microphone without using the alsa-base.conf change
  in custom modified kernel. I will attach it here. Now, hoping to fix
  other issues as well slowly like making headphones unplugged when
  physically removing as well as auto switching like the legacy driver
  one.

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

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

[Kernel-packages] [Bug 1929444] Re: SD card initialization on insertion fails

[Chris Chiu]

Thanks. Please try https://people.canonical.com/~mschiu77/lp1929444/v3/
and I can confirm which commits really cause the problem.

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

Title:
  SD card initialization on insertion fails

Status in linux package in Ubuntu:
  New

Bug description:
  If I boot my laptop with an SD card (actually SDXC) in the MMC slot
  the system sees it and I can mount and use it.

  If I then unmount it, remove it then re-insert it I get this in the
  system ,og:

  [  194.673108] mmc0: card e624 removed
  [  205.462065] mmc0: cannot verify signal voltage switch
  [  205.567479] mmc0: error -84 whilst initialising SD card

  and the card cannot then be used.

  It was OK in groovy. It's failing in hirsute.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-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:  gml44104153 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Mon May 24 17:36:49 2021
  HibernationDevice: RESUME=UUID=03dec042-8ba2-48a8-8d19-373ca2e0829c
  InstallationDate: Installed on 2020-08-13 (284 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: PC Specialist LTD N150CU
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=b21720c3-60bf-4298-9d73-743672f89216 ro quiet splash 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
  UpgradeStatus: Upgraded to hirsute on 2021-05-13 (11 days ago)
  dmi.bios.date: 11/15/2019
  dmi.bios.release: 7.7
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.07TPCS2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N151CU
  dmi.board.vendor: CLEVO
  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.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N150CU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist LTD

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

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

[Kernel-packages] [Bug 1930354] [NEW] package nvidia-dkms-460 460.73.01-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-460 package post-installation script subprocess returned error

[Kevin Remisoski]

Public bug reported:

Pretty sure this bug is more related to my kernel version, but there
doesn't seem to be any information about what the latest supported
kernel is.

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: nvidia-dkms-460 460.73.01-0ubuntu0.20.10.1
Uname: Linux 5.12.8-051208-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.7
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Jun  1 00:17:36 2021
ErrorMessage: installed nvidia-dkms-460 package post-installation script 
subprocess returned error exit status 10
InstallationDate: Installed on 2021-06-01 (0 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.20.5ubuntu2
 apt  2.1.10ubuntu0.3
SourcePackage: nvidia-graphics-drivers-460
Title: package nvidia-dkms-460 460.73.01-0ubuntu0.20.10.1 failed to 
install/upgrade: installed nvidia-dkms-460 package post-installation script 
subprocess returned error exit status 10
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-460 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package groovy

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

Title:
  package nvidia-dkms-460 460.73.01-0ubuntu0.20.10.1 failed to
  install/upgrade: installed nvidia-dkms-460 package post-installation
  script subprocess returned error exit status 10

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  New

Bug description:
  Pretty sure this bug is more related to my kernel version, but there
  doesn't seem to be any information about what the latest supported
  kernel is.

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: nvidia-dkms-460 460.73.01-0ubuntu0.20.10.1
  Uname: Linux 5.12.8-051208-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.7
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jun  1 00:17:36 2021
  ErrorMessage: installed nvidia-dkms-460 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2021-06-01 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10ubuntu0.3
  SourcePackage: nvidia-graphics-drivers-460
  Title: package nvidia-dkms-460 460.73.01-0ubuntu0.20.10.1 failed to 
install/upgrade: installed nvidia-dkms-460 package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1930354/+subscriptions

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

[Kernel-packages] [Bug 1927866] Re: Root filesystem becomes readonly frequenty freezing system

[anoopjohn]

I finally gave up on the laptop. I am going to return this and get
another model. The crashes were making it unusable for my work. I tried.
I wiped clean the system. However I still have the device. I booted from
live usb and got the details. Please find below the details.

Thanks for everybody who tried to help on this thread. I am sorry I had
to give up as it was making it difficult for me to work with this. I
hope the thread will help somebody else to move forward the research on
this bug forward.

If there is something else that need to be pulled up before I return
this, please let me know and I will be happy to do that.

sudo nvme get-feature -f 0x0c -H /dev/nvme0n1
get-feature:0xc (Autonomous Power State Transition), Current value:0x01
Autonomous Power State Transition Enable (APSTE): Enabled
Auto PST Entries.
Entry[ 0]   
.
Idle Time Prior to Transition (ITPT): 745 ms
Idle Transition Power State   (ITPS): 3
.
Entry[ 1]   
.
Idle Time Prior to Transition (ITPT): 745 ms
Idle Transition Power State   (ITPS): 3
.
Entry[ 2]   
.
Idle Time Prior to Transition (ITPT): 745 ms
Idle Transition Power State   (ITPS): 3
.
Entry[ 3]   
.
Idle Time Prior to Transition (ITPT): 2200 ms
Idle Transition Power State   (ITPS): 4
.

All subsequent entries all the way to 31 are 0ms and 0s.

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

Title:
  Root filesystem becomes readonly frequenty freezing system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a brand new Lenovo Ideapad Flex 5.14 which came with Windows 10
  and I have installed Ubuntu 21.04 with dual boot.

  I am running into this problem where the root filesystem becomes
  readonly and the system freezes with a screen full of errors shown
  about unable to write to filesystem.

  I booted into a live boot usb and did fsck and e2fsck but did not see
  any errors there. I read online that this could be because of io
  errors but smartctl and fsck does not show any errors

  So I was wondering if this could be a bug vs a hardward issue. Please
  let me know if you need any further information from the system.

  =
  =

  fdisk -l /dev/nvme0n1
  Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
  Disk model: WDC PC SN530 SDBPMPZ-512G-1101
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: gpt
  Disk identifier: E8803E28-C4F7-4FA5-9B6D-0F3CAB7027A5

  Device StartEnd   Sectors   Size Type
  /dev/nvme0n1p1  2048 534527532480   260M EFI System
  /dev/nvme0n1p2534528 567295 3276816M Microsoft reserved
  /dev/nvme0n1p3567296  199446527 198879232  94.8G Microsoft basic data
  /dev/nvme0n1p4 998166528 1000214527   2048000  1000M Windows recovery 
environmen
  /dev/nvme0n1p5 199446528  203352063   3905536   1.9G Linux filesystem
  /dev/nvme0n1p6 203352064  219353087  16001024   7.6G Linux swap
  /dev/nvme0n1p7 219353088  414664703 195311616  93.1G Linux filesystem
  /dev/nvme0n1p8 414664704  998166527 583501824 278.2G Microsoft basic data

  =
  =

  smartctl -a /dev/nvme0
  smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.11.0-16-generic] (local build)
  Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF INFORMATION SECTION ===
  Model Number:   WDC PC SN530 SDBPMPZ-512G-1101
  Serial Number:  205135806243
  Firmware Version:   21160001
  PCI Vendor/Subsystem ID:0x15b7
  IEEE OUI Identifier:0x001b44
  Total NVM Capacity: 512,110,190,592 [512 GB]
  Unallocated NVM Capacity:   0
  Controller ID:  1
  NVMe Version:   1.4
  Number of Namespaces:   1
  Namespace 1 Size/Capacity:  512,110,190,592 [512 GB]
  Namespace 1 Formatted LBA Size: 512
  Namespace 1 IEEE EUI-64:001b44 8b484daff7
  Local Time is:  Sun May  9 12:45:05 2021 EDT
  Firmware Updates (0x14):2 Slots, no Reset required
  Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
  Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat 
Timestmp

[Kernel-packages] [Bug 1925290] Re: hangup01 from pty in ubuntu_ltp_stable failed on G-5.8

[Po-Hsu Lin]

** Changed in: ubuntu-kernel-tests
   Status: New => Fix Released

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

Title:
  hangup01 from pty in ubuntu_ltp_stable failed on G-5.8

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  Testcase hangup01 from ubuntu_ltp_stable.pty is failing on Groovy 5.8.0-51.57.

  Test case failed with:
   hangup011  TFAIL  :  hangup01.c:132: unexpected message 3
   tag=hangup01 stime=1618856629 dur=1 exit=exited stat=1

  It was found that the regression was introduced by the following
  commits applied via stable uddates:

  dd78b0c483e3 tty: implement read_iter
  3b830a9c34d5 tty: convert tty_ldisc_ops 'read()' function to take a kernel 
pointer

  These patches were applied via bug 1921960 ("Groovy update: upstream
  stable patchset 2021-03-30").

  [Fix]
  Revert the patches mentioned above until a fix can be found.

  [Test case]
  Run the pty testsuite from ubuntu_ltp_stable.

  [Where problems could occur]
  If reverting these two patches is not enough to bring the code to the 
behavior of the tty driver before 5.8.0-51.57 then remaining issues could still 
be present on the tty code. Those issues should be caught by the ltp testcases 
though.

  [Original Description]
  Issue found on Groovy 5.8.0-51.57 with P8 node "dryden" and ARM64 node 
"helo-kernel" and AMD64 node "onibi"

  Test case failed with:
   hangup011  TFAIL  :  hangup01.c:132: unexpected message 3
   tag=hangup01 stime=1618856629 dur=1 exit=exited stat=1

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

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

[Kernel-packages] [Bug 1910323] Re: Fix implicit declaration warnings for kselftests/memfd test on newer releases

[Po-Hsu Lin]

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

Title:
  Fix implicit declaration warnings for kselftests/memfd test on newer
  releases

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-5.6 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in linux source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  While debugging bug 1910277, I found that the test compilation will
  print some warnings:
memfd_test.c:64:7: warning: implicit declaration of function ‘open’;
memfd_test.c:90:6: warning: implicit declaration of function ‘fcntl’
memfd_test.c:397:6: warning: implicit declaration of function ‘fallocate’;
fuse_test.c:67:6: warning: implicit declaration of function ‘fcntl’
fuse_test.c:261:7: warning: implicit declaration of function ‘open’;

  It's harmless but fixing this we can make the test report easier to
  read.

  [Fix]
  * 1c49e3783f8899 ("selftests/memfd: Fix implicit declaration warnings")

  This fix can be cherry-picked into F/F-oem-5.6/G and compiled without
  any problem. Older kernel does not have this issue since they're
  missing some other commits.

  [Test Case]
  Build the memfd test in tools/testing/selftests/ with:
sudo make TARGETS=memfd

  With this fix, these warnings will be gone.

  [Where problems could occur]
  This fix is just for fixing the test case compilation, so it's not
  affecting real kernel functionality.

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

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

[Kernel-packages] [Bug 1909428] Re: eeh-basic.sh from powerpc in ubuntu_kernel_selftests failed with unexpected operator on F-5.8

[Po-Hsu Lin]

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

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

** Changed in: ubuntu-kernel-tests
   Status: In Progress => 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/1909428

Title:
  eeh-basic.sh from powerpc in ubuntu_kernel_selftests failed with
  unexpected operator on F-5.8

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in linux source package in Hirsute:
  Fix Released

Bug description:
  [Impact] 
  The fail check in the end of powerpc/eeh/eeh-basic.sh script will complain 
about "unexpected operator"

  This is caused by the following line in the script:
$ test "$failed" == 0
/bin/sh: 4: test: 0: unexpected operator

  [Fix]
  * 3db380570af705 ("selftests/powerpc: Make the test check in eeh-basic.sh 
posix compliant")

  This is affecting F/G/H and can be cherry-picked for all of them.

  [Test case]
  Run the eeh-basic.sh script in tools/testing/selftests/powerpc/eeh/
  This error message should be gone.

  [Where problems could occur]
  This fix is limited to PowerPC testing tool, it's unlike to cause any issue.

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

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

[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS

[MikeMecanic]

This bug and there is no bug started in Mint 20.1 with Kernel 5.12-rc7
alongside the shim 1.46 multiple issues. Since then it works here secure
boot enabled or not.

The bug comes with a broken header and it kills update manager.

All we do here to make it work is to delete the broken header in
Synaptic, After, update manager runs normally.  Same for the Kernel with
3 deb packages only. Give it a try, there is no side effect.

If you don't want me to test mainline Kernel in Mint (noise free), then
you have to remove the second header.

We never give up no matter what the problem is, even with 3 legs.

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

Title:
  Recent mainline packages are built with Hirsuite 21.04, not Focal
  20.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  The Mainline wiki states that the mainline kernels are built with the
  previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are
  being built with Hirsuite 21.04, and before that Groovy? If this is
  intentional, then the wiki should be updated to reflect the change in
  policy.

  From https://wiki.ubuntu.com/Kernel/MainlineBuilds

Mainline kernel build toolchain
These kernels are built with the toolchain (gcc, g++, etc.) from the 
previous Ubuntu LTS release. 
(e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic 
Beaver", etc.) Therefore, 
out-of-tree kernel modules you already have built and installed for use 
with your release kernels 
are not likely to work with the mainline builds.

  The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On
  my Focal LTS system I have GCC 9.3.0.

  The Mainline kernel build toolchain
  These kernels are built with the toolchain (gcc, g++, etc.) from the previous 
Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 
18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already 
have built and installed for use with your release kernels are not likely to 
work with the mainline builds.

  The *linux-headers-generic* packages have unmet dependencies on 20.04
  LTS.

  I could install Groovy built kernels fine, but the Hirsuite ones built
  with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels
  can't be installed on Focal (libc 2.31).

  Thanks,
  Mark

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

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

[Kernel-packages] [Bug 1929147] Re: fix system hang with 5.10 kernel + RX540 on RKL platform

[koba]

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

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

Title:
  fix system hang with 5.10 kernel + RX540 on RKL platform

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-firmware source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]
  On RKL platform with AMD RX540, system would hang during boot-up.

  [Fix]
  AMD introduce a brand new firmware, polaris 12 MC firmware.
  This fix the issue and the system wouldn't hang during boot-up with AMD RX540.

  [Test]
  Verified on RKL platform and AMD RX540
  System would boot-up and login to desktop successfully.

  [Where problems could occur]
  This's a brand new firmware to support Polaris-series,
  it may introduce new issues.

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

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

[Kernel-packages] [Bug 1927866] Re: Root filesystem becomes readonly frequenty freezing system

[Kai-Heng Feng]

Can you please attach the out put of `sudo nvme get-feature -f 0x0c -H
/dev/nvme0n1` when there's no kernel parameter?

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

Title:
  Root filesystem becomes readonly frequenty freezing system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a brand new Lenovo Ideapad Flex 5.14 which came with Windows 10
  and I have installed Ubuntu 21.04 with dual boot.

  I am running into this problem where the root filesystem becomes
  readonly and the system freezes with a screen full of errors shown
  about unable to write to filesystem.

  I booted into a live boot usb and did fsck and e2fsck but did not see
  any errors there. I read online that this could be because of io
  errors but smartctl and fsck does not show any errors

  So I was wondering if this could be a bug vs a hardward issue. Please
  let me know if you need any further information from the system.

  =
  =

  fdisk -l /dev/nvme0n1
  Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
  Disk model: WDC PC SN530 SDBPMPZ-512G-1101
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: gpt
  Disk identifier: E8803E28-C4F7-4FA5-9B6D-0F3CAB7027A5

  Device StartEnd   Sectors   Size Type
  /dev/nvme0n1p1  2048 534527532480   260M EFI System
  /dev/nvme0n1p2534528 567295 3276816M Microsoft reserved
  /dev/nvme0n1p3567296  199446527 198879232  94.8G Microsoft basic data
  /dev/nvme0n1p4 998166528 1000214527   2048000  1000M Windows recovery 
environmen
  /dev/nvme0n1p5 199446528  203352063   3905536   1.9G Linux filesystem
  /dev/nvme0n1p6 203352064  219353087  16001024   7.6G Linux swap
  /dev/nvme0n1p7 219353088  414664703 195311616  93.1G Linux filesystem
  /dev/nvme0n1p8 414664704  998166527 583501824 278.2G Microsoft basic data

  =
  =

  smartctl -a /dev/nvme0
  smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.11.0-16-generic] (local build)
  Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF INFORMATION SECTION ===
  Model Number:   WDC PC SN530 SDBPMPZ-512G-1101
  Serial Number:  205135806243
  Firmware Version:   21160001
  PCI Vendor/Subsystem ID:0x15b7
  IEEE OUI Identifier:0x001b44
  Total NVM Capacity: 512,110,190,592 [512 GB]
  Unallocated NVM Capacity:   0
  Controller ID:  1
  NVMe Version:   1.4
  Number of Namespaces:   1
  Namespace 1 Size/Capacity:  512,110,190,592 [512 GB]
  Namespace 1 Formatted LBA Size: 512
  Namespace 1 IEEE EUI-64:001b44 8b484daff7
  Local Time is:  Sun May  9 12:45:05 2021 EDT
  Firmware Updates (0x14):2 Slots, no Reset required
  Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
  Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat 
Timestmp
  Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg 
Pers_Ev_Lg
  Maximum Data Transfer Size: 128 Pages
  Warning  Comp. Temp. Threshold: 80 Celsius
  Critical Comp. Temp. Threshold: 85 Celsius
  Namespace 1 Features (0x02):NA_Fields

  Supported Power States
  St Op Max   Active Idle   RL RT WL WT  Ent_Lat  Ex_Lat
   0 + 3.50W2.10W   -0  0  0  00   0
   1 + 2.40W1.60W   -0  0  0  00   0
   2 + 1.90W1.50W   -0  0  0  00   0
   3 -   0.0250W   --3  3  3  3 3900   11000
   4 -   0.0050W   --4  4  4  4 5000   39000

  Supported LBA Sizes (NSID 0x1)
  Id Fmt  Data  Metadt  Rel_Perf
   0 + 512   0 2
   1 -4096   0 1

  === START OF SMART DATA SECTION ===
  SMART overall-health self-assessment test result: PASSED

  SMART/Health Information (NVMe Log 0x02)
  Critical Warning:   0x00
  Temperature:35 Celsius
  Available Spare:100%
  Available Spare Threshold:  10%
  Percentage Used:0%
  Data Units Read:624,535 [319 GB]
  Data Units Written: 526,042 [269 GB]
  Host Read Commands: 4,462,163
  Host Write Commands:4,686,788
  Controller Busy Time:   25
  Power Cycles:   20
  Power On Hours: 

[Kernel-packages] [Bug 1929925] Re: [Potential Regression] Unable to create KVM with uvtool on Groovy ARM64

[Po-Hsu Lin]

Hi Marcelo,
this kernel work well with the KVM smoke test.

 Running 'sudo -u ubuntu 
/home/ubuntu/autotest/client/tests/ubuntu_kvm_smoke_test/the-test arm64'
 [stderr] + SUT=bjf-test
 [stderr] + SSH_KEY=/home/ubuntu/.ssh/id_rsa
 [stderr] + SSH_OPTIONS='-o StrictHostKeyChecking=no -o 
UserKnownHostsFile=/dev/null -o LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa'
 [stderr] ++ lsb_release -c 
 [stderr] ++ awk '{print$2}'
 [stderr] + DISTRO=groovy
 [stderr] + ARCHITECTURE=arm64
 [stderr] + trap cleanup EXIT
 [stderr] + '[' -z arm64 ']'
 [stderr] + kvm-ok
 [stdout] INFO: /dev/kvm exists
 [stdout] KVM acceleration can be used
 [stderr] + '[' 0 '!=' 0 ']'
 [stderr] + '[' '!' -f /home/ubuntu/.ssh/id_rsa ']'
 [stderr] + '[' arm64 = ppc64el ']'
 [stderr] ++ uvt-simplestreams-libvirt query
 [stderr] ++ grep -P 'groovy.*arm64'
 [stderr] + image='release=groovy arch=arm64 label=daily (20210527)'
 [stderr] + '[' -z 'release=groovy arch=arm64 label=daily (20210527)' ']'
 [stderr] + uvt-kvm create bjf-test release=groovy arch=arm64
 [stderr] + uvt-kvm wait bjf-test --insecure --ssh-private-key-file 
/home/ubuntu/.ssh/id_rsa
 [stderr] ++ uvt-kvm ip bjf-test
 [stderr] + ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o 
LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa ubuntu@192.168.122.110 uname -a
 [stdout] Linux bjf-test 5.8.0-53-generic #60-Ubuntu SMP Thu May 6 07:47:26 UTC 
2021 aarch64 aarch64 aarch64 GNU/Linux
 [stderr] ++ cut '-d' -f 2 
 [stderr] +++ uvt-kvm ip bjf-test
 [stderr] ++ ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o 
LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa ubuntu@192.168.122.110 lsb_release -c
 [stderr] + RESULT=groovy
 [stderr] + '[' groovy '!=' groovy ']'
 [stderr] + cleanup
 [stderr] + uvt-kvm destroy bjf-test
 [stderr] + '[' arm64 = ppc64el ']'
GOODubuntu_kvm_smoke_test.kvm_smoke_test
ubuntu_kvm_smoke_test.kvm_smoke_testtimestamp=1622514210localtime=Jun 
01 02:23:30   completed successfully
END GOODubuntu_kvm_smoke_test.kvm_smoke_test
ubuntu_kvm_smoke_test.kvm_smoke_testtimestamp=1622514210localtime=Jun 
01 02:23:30   
 Persistent state client._record_indent now set to 1
 Persistent state client.unexpected_reboot deleted
 END GOOD   timestamp=1622514210localtime=Jun 01 02:23:30   

$ uname -a
Linux wright-kernel 5.8.0-54-generic #61+lp1929925.1 SMP Mon May 31 16:19:25 
UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

Thank you.

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

Title:
  [Potential Regression] Unable to create KVM with uvtool on Groovy
  ARM64

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

Bug description:
  Issue found on 5.8.0-54-generic proposed ARM64 kernel with node
  "helo", "wright"

  This issue does not exist in 5.8.0-53.60 so this might be a
  regression.

  Test case:
    1. Deploy Groovy on an ARM64 node
    2. Create a KVM with the following command:
   uvt-kvm create bjf-test release=groovy arch=arm64
       Or you can run the ubuntu_kvm_smoke_test with autotest:
   git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests 
-b master-next
   git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
   rm -fr autotest/client/tests
   ln -sf ~/autotest-client-tests autotest/client/tests
   sudo apt-get install git python-minimal -y || sudo apt install python2 -y
   AUTOTEST_PATH=/home/ubuntu/autotest sudo -E 
autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_kvm_smoke_test/control
    3. Install just the proposed kernel and reboot
    4. Repeat step 2

  This is 100% reproducible on ARM64, 4 out of 4 attempts (twice on each
  nodes).

  Test log:
    + SUT=bjf-test
    + SSH_KEY=/home/ubuntu/.ssh/id_rsa
    + SSH_OPTIONS='-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null 
-o LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa'
    ++ lsb_release -c
    ++ awk '{print$2}'
    + DISTRO=groovy
    + ARCHITECTURE=arm64
    + trap cleanup EXIT
    + '[' -z arm64 ']'
    + kvm-ok
    + '[' 0 '!=' 0 ']'
    + '[' '!' -f /home/ubuntu/.ssh/id_rsa ']'
    + '[' arm64 = ppc64el ']'
    ++ uvt-simplestreams-libvirt query
    ++ grep -P 'groovy.*arm64'
    + image='release=groovy arch=arm64 label=daily (20210527)'
    + '[' -z 'release=groovy arch=arm64 label=daily (20210527)' ']'
    + uvt-kvm create bjf-test release=groovy arch=arm64
    uvt-kvm: error: libvirt: unsupported configuration: Emulator 
'/usr/bin/qemu-system-aarch64' does not support virt type 'kvm'

  syslog:
  May 28 08:01:07 helo-kernel kernel: [ 1030.945560] mpt3sas :8d:00.0: 
invalid short VPD tag 00 at offset 1
  May 28 08:01:08 helo-kernel kernel: [ 1031.238058] sr 3:0:0:0: [sr0] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 

[Kernel-packages] [Bug 1930275] Re: [nvidia] System does not wake up after suspend

[Daniel van Vugt]

Thanks for the bug report. Next time the problem happens and you have to
"hard reboot", please then run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.


** Summary changed:

- Xorg freeze
+ [nvidia] System does not wake up after suspend

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-460
(Ubuntu)

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

** Tags added: nvidia

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

Title:
  [nvidia] System does not wake up after suspend

Status in linux package in Ubuntu:
  New
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  New

Bug description:
  Ubuntu 20.10 suspend is not working. After suspend it does not wake
  up. And I have to hard reboot machine. It is happening since last few
  days.

  Here is error message I see from logs:

  "Failed to start Application launched by gnome-session-binary.

  A start job for unit UNIT has finished with a failure.
  The job identifier is 368 and the job result is failed.

  Failed to start LSB: OpenIPMI Driver init script.
  A start job for unit openipmi.service has finished with a failure.
  The job identifier is 151 and the job result is failed.
  "

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.73.01  Thu Apr  1 
21:40:36 UTC 2021
   GCC version:  gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1)
  ApportVersion: 2.20.11-0ubuntu50.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 31 09:04:06 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 460.73.01, 5.8.0-50-generic, x86_64: installed
   nvidia, 460.73.01, 5.8.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last few days
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:1f06] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. TU106 [GeForce RTX 2060 SUPER] [3842:3061]
  InstallationDate: Installed on 2020-02-15 (471 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic 
root=UUID=ae47d531-67a5-47ff-ba8c-fd3928cd4cad ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7b
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7b:bd09/17/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

[Kernel-packages] [Bug 1930279] Re: [Ivy Bridge] winking triangles on screen

[Daniel van Vugt]

** Summary changed:

- winking triangles on screen
+ [Ivy Bridge] winking triangles on screen

** Package changed: xorg (Ubuntu) => mesa (Ubuntu)

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

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

Title:
  [Ivy Bridge] winking triangles on screen

Status in linux package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  when i did upgrade my ubuntu from 20.04 to 20.10 i have small winking
  triangles on my screen, they sometimes will appear when i watching a
  youtube video they will appear on the video's seek bar or when i
  typing they will appear on selected texts,but the main and most
  annoying state of it happens when I am playing minecraft,my entire
  game screen has these little triangles

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  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.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 31 18:05:33 2021
  DistUpgraded: 2021-05-27 14:18:07,483 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed
   virtualbox, 6.1.16, 5.8.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller [1043:844d]
  InstallationDate: Installed on 2020-01-10 (507 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic 
root=UUID=a5a5279f-cdf5-4129-94fa-8f17f7401833 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2021-05-27 (4 days ago)
  dmi.bios.date: 03/19/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1204
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1204:bd03/19/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXR2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  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
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/1930279/+subscriptions

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

[Kernel-packages] [Bug 1930275] [NEW] [nvidia] System does not wake up after suspend

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Ubuntu 20.10 suspend is not working. After suspend it does not wake up.
And I have to hard reboot machine. It is happening since last few days.

Here is error message I see from logs:

"Failed to start Application launched by gnome-session-binary.

A start job for unit UNIT has finished with a failure.
The job identifier is 368 and the job result is failed.

Failed to start LSB: OpenIPMI Driver init script.
A start job for unit openipmi.service has finished with a failure.
The job identifier is 151 and the job result is failed.
"

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.73.01  Thu Apr  1 21:40:36 
UTC 2021
 GCC version:  gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1)
ApportVersion: 2.20.11-0ubuntu50.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon May 31 09:04:06 2021
DistUpgraded: Fresh install
DistroCodename: groovy
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 460.73.01, 5.8.0-50-generic, x86_64: installed
 nvidia, 460.73.01, 5.8.0-53-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Within the last few days
GraphicsCard:
 NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:1f06] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: eVga.com. Corp. TU106 [GeForce RTX 2060 SUPER] [3842:3061]
InstallationDate: Installed on 2020-02-15 (471 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic 
root=UUID=ae47d531-67a5-47ff-ba8c-fd3928cd4cad ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/17/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F7b
dmi.board.asset.tag: Default string
dmi.board.name: X570 AORUS MASTER
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7b:bd09/17/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: X570 AORUS MASTER
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: nvidia-graphics-drivers-460 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug freeze groovy ubuntu
-- 
[nvidia] System does not wake up after suspend
https://bugs.launchpad.net/bugs/1930275
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to nvidia-graphics-drivers-460 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 1930188] Re: Acer Aspire 5 sound driver issues

[Hui Wang]

Please test this kernel:
https://people.canonical.com/~hwang4/lp1930188/v2/

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

Title:
  Acer Aspire 5 sound driver issues

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  There seems to be lots of issues in sound driver for Acer Aspire
  A515-56-57XR with ALC255. I will list all of them below and what I
  have tried so far.

  1. Headphones appears always plugged in even if they are physically not
  2. When actually plugging in headset/earphones it does not auto switch from 
speakers/internal mic to headphones/headset microphone automatically and vice 
versa, have to manually switch everytime.
  3. External headset/earphones microphone won't work at all

  After, logs of trial and error I have found a temporary fix. This
  seems to use legacy intel drivers which solves all 3 issues mentioned
  above but the internal/dmic mic is completely gone (which seems
  intentional when using this). Both depreciated dmic_detect and
  dsp_driver works, I have been using dsp_driver for now as I need
  external microphone at any cost.

  End of /etc/modprobe.d/alsa-base.conf
  # Headset mic fix
  options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1
  options snd-hda-intel model=alc255-acer

  In another thread similar to this I got some support and at least
  fixed the external microphone without using the alsa-base.conf change
  in custom modified kernel. I will attach it here. Now, hoping to fix
  other issues as well slowly like making headphones unplugged when
  physically removing as well as auto switching like the legacy driver
  one.

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

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

[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze

[Paul Szabo]

Just wondering (maybe I am way off ...).
In kernel code I often see segments like
  lock(thing)
  do stuff
  unlock(thing)
but in drivers/net/wireless/realtek/rtw88/main.c there is:

void rtw_core_stop(struct rtw_dev *rtwdev)
{
...
mutex_unlock(>mutex);
...
mutex_lock(>mutex);
...
}

and that seems back-to-front. Is that as should be?

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

Title:
  rtw88_8821ce causes freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card.
  Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic 
kernel,and it works "well" for both WiFi and Bluetooth.
  However, this module (driver) causes frequent freezes, randomly but usually 
within a few minutes of running (thus very soon after boot): screen display 
remains frozen, no response to either keyboard or mouse input. All I can do is 
to hold the power button to power off, then reboot.

  After reboot, I do not see any crash reports, nor logs about the freeze.
  Please let me know if I should try to collect some info, and how.

  For now I use the DKMS module/driver from
    https://github.com/tomaspinho/rtl8821ce
  (having blacklisted rtw88_8821ce), and it seems to work perfectly.

  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
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  psz1189 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  8 16:58:19 2021
  InstallationDate: Installed on 2021-04-23 (14 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera
   Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Protempo Ltd L116HTN6SPW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer 
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: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2020
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Notebook
  dmi.product.name: L116HTN6SPW
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Protempo Ltd

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

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

[Kernel-packages] [Bug 1925843] Re: Linux 5.8.0-49+ fails to resume from suspend

[Steven]

I am not terribly familiar with the git and make commands so I want to
give a full account of my process in case I did something wrong.

First, I can confirm that 5.12-rc8 is the last kernel that doesn't work
for me and 5.13-rc2 is the first one that does.

I am skipping over 5.13-rc1 because I don't believe I can install it on my 
machine. It doesn't seem to be compatible with my Nvidia drivers as per this 
error: 
ERROR (dkms apport): kernel package linux-headers-5.13.0-051300rc1-generic is 
not supported
Error! Bad return status for module build on kernel: 5.13.0-051300rc1-generic 
(x86_64)
Consult /var/lib/dkms/nvidia/460.73.01/build/make.log for more information.

Maybe I am just unwilling to mess with drivers enough to make it work,
though.

As for the bisect, I ran 'apt build-dep linux' (after checking 'Source
Code' in Software and Updates so I could actually find the right
packages) and cloned the git repository.

Using 5.12-rc8 as the last non-working kernel and 5.13-rc2 as the first working 
kernel, I ran:
cd linux
git bisect start
git bisect good v5.13-rc2
git bisect bad v5.12-rc8

This simply returned:
Bisecting: a merge base must be tested
[bf05bf16c76bb44ab5156223e1e58e26dfe30a88] Linux 5.12-rc8

which I didn't find particularly helpful. I had to use 'good' and 'bad'
instead of 'new' and 'old' because the latter returned '[a string of
numbers] is both old and new', which seemed wrong.

To build the new kernel, I ran:
make olddefconfig
make localmodconfig 
make -j`nproc` deb-pkg

This gave several warnings, but seemed to run OK. I can attached a file
with the outputs if you want.

It looks like it just built 5.12-rc8, although maybe the file name is
misleading.

I assume to install this kernel I should install the four .deb that make made:
linux-headers-5.12.0-rc8_5.12.0-rc8-1_amd64.deb
linux-image-5.12.0-rc8_5.12.0-rc8-1_amd64.deb
linux-image-5.12.0-rc8-dbg_5.12.0-rc8-1_amd64.deb
linux-libc-dev_5.12.0-rc8-1_amd64.deb

I will do that when I have some time to test the new kernel unless I
hear from you first. Hopefully, I did everything right.

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

Title:
  Linux 5.8.0-49+ fails to resume from suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Expected Result: System resumes from suspend and displays the log in
  screen to unlock the computer.

  Actual Result: System displays a black screen with a flashing cursor
  in the upper left and cannot be interacted with. Hard reboot is
  required to get back to a working system.

  Additional information:

  When I boot my computer with 5.8.0-48, the system resumes from suspend
  as expected. Both 5.8.0-49 and 5.8.0-50 fail to resume from suspend.

  This problem began after I updated from 20.04 to 20.10 using the
  Software Updater on 4-19-21. I was using the latest kernel available
  for 20.04 at that time (5.8.0-48, I think) before updating.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-50-generic 5.8.0-50.56
  ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steven 1268 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 23 12:54:52 2021
  InstallationDate: Installed on 2020-09-01 (234 days ago)
  InstallationMedia: Ubuntu 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 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 0bda:58eb Realtek Semiconductor Corp. HP Wide Vision 
HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP OMEN by HP Laptop 15-ce0xx
  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.8.0-50-generic 
root=UUID=208c1c0d-3e9e-43da-ba24-0d1cd92b5ad0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-50-generic N/A
   linux-backports-modules-5.8.0-50-generic  N/A
   linux-firmware1.190.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2020
  dmi.bios.release: 15.23
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.23
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 838F
  dmi.board.vendor: HP
  dmi.board.version: 40.28
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 40.28
  dmi.modalias: 

[Kernel-packages] [Bug 1929925] Re: [Potential Regression] Unable to create KVM with uvtool on Groovy ARM64

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  [Potential Regression] Unable to create KVM with uvtool on Groovy
  ARM64

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

Bug description:
  Issue found on 5.8.0-54-generic proposed ARM64 kernel with node
  "helo", "wright"

  This issue does not exist in 5.8.0-53.60 so this might be a
  regression.

  Test case:
    1. Deploy Groovy on an ARM64 node
    2. Create a KVM with the following command:
   uvt-kvm create bjf-test release=groovy arch=arm64
       Or you can run the ubuntu_kvm_smoke_test with autotest:
   git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests 
-b master-next
   git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
   rm -fr autotest/client/tests
   ln -sf ~/autotest-client-tests autotest/client/tests
   sudo apt-get install git python-minimal -y || sudo apt install python2 -y
   AUTOTEST_PATH=/home/ubuntu/autotest sudo -E 
autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_kvm_smoke_test/control
    3. Install just the proposed kernel and reboot
    4. Repeat step 2

  This is 100% reproducible on ARM64, 4 out of 4 attempts (twice on each
  nodes).

  Test log:
    + SUT=bjf-test
    + SSH_KEY=/home/ubuntu/.ssh/id_rsa
    + SSH_OPTIONS='-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null 
-o LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa'
    ++ lsb_release -c
    ++ awk '{print$2}'
    + DISTRO=groovy
    + ARCHITECTURE=arm64
    + trap cleanup EXIT
    + '[' -z arm64 ']'
    + kvm-ok
    + '[' 0 '!=' 0 ']'
    + '[' '!' -f /home/ubuntu/.ssh/id_rsa ']'
    + '[' arm64 = ppc64el ']'
    ++ uvt-simplestreams-libvirt query
    ++ grep -P 'groovy.*arm64'
    + image='release=groovy arch=arm64 label=daily (20210527)'
    + '[' -z 'release=groovy arch=arm64 label=daily (20210527)' ']'
    + uvt-kvm create bjf-test release=groovy arch=arm64
    uvt-kvm: error: libvirt: unsupported configuration: Emulator 
'/usr/bin/qemu-system-aarch64' does not support virt type 'kvm'

  syslog:
  May 28 08:01:07 helo-kernel kernel: [ 1030.945560] mpt3sas :8d:00.0: 
invalid short VPD tag 00 at offset 1
  May 28 08:01:08 helo-kernel kernel: [ 1031.238058] sr 3:0:0:0: [sr0] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.242304] sr 3:0:0:0: [sr0] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.245430] sr 3:0:0:1: [sr1] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.248810] sr 3:0:0:1: [sr1] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.252678] sr 3:0:0:2: [sr2] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.255678] sr 3:0:0:2: [sr2] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.258811] sr 3:0:0:3: [sr3] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.272678] sr 3:0:0:3: [sr3] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:13 helo-kernel systemd[1]: Started Daemon for generating UUIDs.
  May 28 08:01:13 helo-kernel kernel: [ 1036.620470] qemu-system-aar using 
unsupported default IPA limit, upgrade your VMM
  May 28 08:01:14 helo-kernel libvirtd[3767]: libvirt version: 6.6.0, package: 
1ubuntu3.5 (Christian Ehrhardt  Wed, 07 Apr 
2021 13:33:46 +0200)
  May 28 08:01:14 helo-kernel libvirtd[3767]: hostname: helo-kernel
  May 28 08:01:14 helo-kernel libvirtd[3767]: unsupported configuration: 
Emulator '/usr/bin/qemu-system-aarch64' does not support virt type 'kvm'

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-54-generic 5.8.0-54.61
  ProcVersionSignature: Ubuntu 5.8.0-54.61-generic 5.8.18
  Uname: Linux 5.8.0-54-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 28 07:04 seq
   crw-rw 1 root audio 116, 33 May 28 07:04 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDmesg:

  Date: Fri May 28 07:10:15 2021
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: To be filled by O.E.M. Saber
  PciMultimedia:

  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-54-generic 
root=UUID=6660a008-6d09-4dba-a6f8-0fb57ee2582f ro 

[Kernel-packages] [Bug 1930303] Re: package libnvidia-cfg1-450-server 450.102.04-0ubuntu0.20.04.1 failed to install/upgrade: read error in '/var/lib/dpkg/info/libnvidia-cfg1-450-server:amd64.triggers'

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: nvidia-graphics-drivers-450-server (Ubuntu)
   Importance: Undecided => Low

** Changed in: nvidia-graphics-drivers-450-server (Ubuntu)
   Status: New => Invalid

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

Title:
  package libnvidia-cfg1-450-server 450.102.04-0ubuntu0.20.04.1 failed
  to install/upgrade: read error in '/var/lib/dpkg/info/libnvidia-
  cfg1-450-server:amd64.triggers': Input/output error

Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Invalid

Bug description:
  This came while updating the system

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libnvidia-cfg1-450-server 450.102.04-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon May 31 22:47:12 2021
  DuplicateSignature:
   package:libnvidia-cfg1-450-server:450.102.04-0ubuntu0.20.04.1
   Preparing to unpack 
.../071-libnvidia-cfg1-450-server_450.119.03-0ubuntu0.20.04.1_amd64.deb ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-kJRTFO/071-libnvidia-cfg1-450-server_450.119.03-0ubuntu0.20.04.1_amd64.deb
 (--unpack):
read error in 
'/var/lib/dpkg/info/libnvidia-cfg1-450-server:amd64.triggers': Input/output 
error
  ErrorMessage: read error in 
'/var/lib/dpkg/info/libnvidia-cfg1-450-server:amd64.triggers': Input/output 
error
  InstallationDate: Installed on 2021-01-06 (144 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.5
  SourcePackage: nvidia-graphics-drivers-450-server
  Title: package libnvidia-cfg1-450-server 450.102.04-0ubuntu0.20.04.1 failed 
to install/upgrade: read error in 
'/var/lib/dpkg/info/libnvidia-cfg1-450-server:amd64.triggers': Input/output 
error
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450-server/+bug/1930303/+subscriptions

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

[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS

[Martin Pecka]

Ok, this gets emotional, so let's concentrate on what's important.

Is there anyone speaking for the official mainline builds? What problems
would it bring to change the policy and build the mainline kernels with
latest (or even oldest!) LTS tooling?

It is apparent that the community would benefit from it. It is
understandable that Ubuntu doesn't want to "officially support" mainline
kernels (just because they're a kind of testing stuff), but apparently
there are people (disclosure: including myself) who need to run mainline
kernels on older distros (Bionic in my case). It is completely fine to
run into problems with a mainline kernel, but why add hurdles to those
who want or need to try?

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

Title:
  Recent mainline packages are built with Hirsuite 21.04, not Focal
  20.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  The Mainline wiki states that the mainline kernels are built with the
  previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are
  being built with Hirsuite 21.04, and before that Groovy? If this is
  intentional, then the wiki should be updated to reflect the change in
  policy.

  From https://wiki.ubuntu.com/Kernel/MainlineBuilds

Mainline kernel build toolchain
These kernels are built with the toolchain (gcc, g++, etc.) from the 
previous Ubuntu LTS release. 
(e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic 
Beaver", etc.) Therefore, 
out-of-tree kernel modules you already have built and installed for use 
with your release kernels 
are not likely to work with the mainline builds.

  The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On
  my Focal LTS system I have GCC 9.3.0.

  The Mainline kernel build toolchain
  These kernels are built with the toolchain (gcc, g++, etc.) from the previous 
Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 
18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already 
have built and installed for use with your release kernels are not likely to 
work with the mainline builds.

  The *linux-headers-generic* packages have unmet dependencies on 20.04
  LTS.

  I could install Groovy built kernels fine, but the Hirsuite ones built
  with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels
  can't be installed on Focal (libc 2.31).

  Thanks,
  Mark

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

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

[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS

[DanglingPointer]

What a joke!  So how is the community going to contribute, help, and
support the mainline kernels for "debug purposes" now?

Everyone on LTS that wants mainline will now be forced to compile their
own kernels or arbitrarily trust PPAs of unofficial 3rd parties if
choosing to stay with Ubuntu.

@David R Bergstein,
Your other alternative to 3rd party unofficial PPA's or compiling your own is 
ditching Ubuntu altogether and switching to rolling release distros like 
OpenSUSE Tumbleweed or Fedora.

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

Title:
  Recent mainline packages are built with Hirsuite 21.04, not Focal
  20.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  The Mainline wiki states that the mainline kernels are built with the
  previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are
  being built with Hirsuite 21.04, and before that Groovy? If this is
  intentional, then the wiki should be updated to reflect the change in
  policy.

  From https://wiki.ubuntu.com/Kernel/MainlineBuilds

Mainline kernel build toolchain
These kernels are built with the toolchain (gcc, g++, etc.) from the 
previous Ubuntu LTS release. 
(e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic 
Beaver", etc.) Therefore, 
out-of-tree kernel modules you already have built and installed for use 
with your release kernels 
are not likely to work with the mainline builds.

  The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On
  my Focal LTS system I have GCC 9.3.0.

  The Mainline kernel build toolchain
  These kernels are built with the toolchain (gcc, g++, etc.) from the previous 
Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 
18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already 
have built and installed for use with your release kernels are not likely to 
work with the mainline builds.

  The *linux-headers-generic* packages have unmet dependencies on 20.04
  LTS.

  I could install Groovy built kernels fine, but the Hirsuite ones built
  with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels
  can't be installed on Focal (libc 2.31).

  Thanks,
  Mark

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

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

[Kernel-packages] [Bug 1794293] Re: Please include hid-bigbenff.c driver for 18.04 and later kernels

[Hanno]

This report may be closed now. Thank you.

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

Title:
  Please include hid-bigbenff.c driver for 18.04 and later kernels

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged

Bug description:
  Hi there,

  my driver submission has just been accepted for the upcoming 4.20
  mainline kernel by the input maintainers:

  
https://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git/commit/?h=for-4.20/bigbenff=256a90ed9e46b270bbc4e15ef05216ff049c3721

  The BigBen Interactive PS3OFMINIPAD kids' gamepad is a Playstation3
  accessory and was designed for smaller hands. The Linux kernel didn't
  support its rumble effects, so the device's HID protocol needed to be
  reverse-engineered to write this driver.

  I originally wrote this driver for the Raspberry Pi and the Retropie
  software used by my kids. But now that Steam and Proton are here, we
  are using our Ubuntu boxes more and more often for gaming, so
  including this driver in the default kernel would be nice.

  The patch applies cleanly on the kernels of 18.04 and 18.10 with no
  changes, so there's no backporting to do.

  Thank you.

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

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

[Kernel-packages] [Bug 1927866] Re: Root filesystem becomes readonly frequenty freezing system

[anoopjohn]

Crashed multiple times. That shows that the symptom is happening
frequently. Now trying to use the system for a while in Windows to see
if it crashes at all. Have not had a crash on windows but I have not
used in windows much. Will try to use in windows for a while to see if
any crash happens in windows at all.

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

Title:
  Root filesystem becomes readonly frequenty freezing system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a brand new Lenovo Ideapad Flex 5.14 which came with Windows 10
  and I have installed Ubuntu 21.04 with dual boot.

  I am running into this problem where the root filesystem becomes
  readonly and the system freezes with a screen full of errors shown
  about unable to write to filesystem.

  I booted into a live boot usb and did fsck and e2fsck but did not see
  any errors there. I read online that this could be because of io
  errors but smartctl and fsck does not show any errors

  So I was wondering if this could be a bug vs a hardward issue. Please
  let me know if you need any further information from the system.

  =
  =

  fdisk -l /dev/nvme0n1
  Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
  Disk model: WDC PC SN530 SDBPMPZ-512G-1101
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: gpt
  Disk identifier: E8803E28-C4F7-4FA5-9B6D-0F3CAB7027A5

  Device StartEnd   Sectors   Size Type
  /dev/nvme0n1p1  2048 534527532480   260M EFI System
  /dev/nvme0n1p2534528 567295 3276816M Microsoft reserved
  /dev/nvme0n1p3567296  199446527 198879232  94.8G Microsoft basic data
  /dev/nvme0n1p4 998166528 1000214527   2048000  1000M Windows recovery 
environmen
  /dev/nvme0n1p5 199446528  203352063   3905536   1.9G Linux filesystem
  /dev/nvme0n1p6 203352064  219353087  16001024   7.6G Linux swap
  /dev/nvme0n1p7 219353088  414664703 195311616  93.1G Linux filesystem
  /dev/nvme0n1p8 414664704  998166527 583501824 278.2G Microsoft basic data

  =
  =

  smartctl -a /dev/nvme0
  smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.11.0-16-generic] (local build)
  Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF INFORMATION SECTION ===
  Model Number:   WDC PC SN530 SDBPMPZ-512G-1101
  Serial Number:  205135806243
  Firmware Version:   21160001
  PCI Vendor/Subsystem ID:0x15b7
  IEEE OUI Identifier:0x001b44
  Total NVM Capacity: 512,110,190,592 [512 GB]
  Unallocated NVM Capacity:   0
  Controller ID:  1
  NVMe Version:   1.4
  Number of Namespaces:   1
  Namespace 1 Size/Capacity:  512,110,190,592 [512 GB]
  Namespace 1 Formatted LBA Size: 512
  Namespace 1 IEEE EUI-64:001b44 8b484daff7
  Local Time is:  Sun May  9 12:45:05 2021 EDT
  Firmware Updates (0x14):2 Slots, no Reset required
  Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
  Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat 
Timestmp
  Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg 
Pers_Ev_Lg
  Maximum Data Transfer Size: 128 Pages
  Warning  Comp. Temp. Threshold: 80 Celsius
  Critical Comp. Temp. Threshold: 85 Celsius
  Namespace 1 Features (0x02):NA_Fields

  Supported Power States
  St Op Max   Active Idle   RL RT WL WT  Ent_Lat  Ex_Lat
   0 + 3.50W2.10W   -0  0  0  00   0
   1 + 2.40W1.60W   -0  0  0  00   0
   2 + 1.90W1.50W   -0  0  0  00   0
   3 -   0.0250W   --3  3  3  3 3900   11000
   4 -   0.0050W   --4  4  4  4 5000   39000

  Supported LBA Sizes (NSID 0x1)
  Id Fmt  Data  Metadt  Rel_Perf
   0 + 512   0 2
   1 -4096   0 1

  === START OF SMART DATA SECTION ===
  SMART overall-health self-assessment test result: PASSED

  SMART/Health Information (NVMe Log 0x02)
  Critical Warning:   0x00
  Temperature:35 Celsius
  Available Spare:100%
  Available Spare Threshold:  10%
  Percentage Used:0%
  Data Units Read:624,535 [319 GB]
  Data Units Written: 526,042 [269 GB]
  Host Read 

[Kernel-packages] [Bug 1927866] Re: Root filesystem becomes readonly frequenty freezing system

[anoopjohn]

I changed to pcie_aspm=force

Rebooted and logged in and the system crashed again.

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

Title:
  Root filesystem becomes readonly frequenty freezing system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a brand new Lenovo Ideapad Flex 5.14 which came with Windows 10
  and I have installed Ubuntu 21.04 with dual boot.

  I am running into this problem where the root filesystem becomes
  readonly and the system freezes with a screen full of errors shown
  about unable to write to filesystem.

  I booted into a live boot usb and did fsck and e2fsck but did not see
  any errors there. I read online that this could be because of io
  errors but smartctl and fsck does not show any errors

  So I was wondering if this could be a bug vs a hardward issue. Please
  let me know if you need any further information from the system.

  =
  =

  fdisk -l /dev/nvme0n1
  Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
  Disk model: WDC PC SN530 SDBPMPZ-512G-1101
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: gpt
  Disk identifier: E8803E28-C4F7-4FA5-9B6D-0F3CAB7027A5

  Device StartEnd   Sectors   Size Type
  /dev/nvme0n1p1  2048 534527532480   260M EFI System
  /dev/nvme0n1p2534528 567295 3276816M Microsoft reserved
  /dev/nvme0n1p3567296  199446527 198879232  94.8G Microsoft basic data
  /dev/nvme0n1p4 998166528 1000214527   2048000  1000M Windows recovery 
environmen
  /dev/nvme0n1p5 199446528  203352063   3905536   1.9G Linux filesystem
  /dev/nvme0n1p6 203352064  219353087  16001024   7.6G Linux swap
  /dev/nvme0n1p7 219353088  414664703 195311616  93.1G Linux filesystem
  /dev/nvme0n1p8 414664704  998166527 583501824 278.2G Microsoft basic data

  =
  =

  smartctl -a /dev/nvme0
  smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.11.0-16-generic] (local build)
  Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF INFORMATION SECTION ===
  Model Number:   WDC PC SN530 SDBPMPZ-512G-1101
  Serial Number:  205135806243
  Firmware Version:   21160001
  PCI Vendor/Subsystem ID:0x15b7
  IEEE OUI Identifier:0x001b44
  Total NVM Capacity: 512,110,190,592 [512 GB]
  Unallocated NVM Capacity:   0
  Controller ID:  1
  NVMe Version:   1.4
  Number of Namespaces:   1
  Namespace 1 Size/Capacity:  512,110,190,592 [512 GB]
  Namespace 1 Formatted LBA Size: 512
  Namespace 1 IEEE EUI-64:001b44 8b484daff7
  Local Time is:  Sun May  9 12:45:05 2021 EDT
  Firmware Updates (0x14):2 Slots, no Reset required
  Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
  Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat 
Timestmp
  Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg 
Pers_Ev_Lg
  Maximum Data Transfer Size: 128 Pages
  Warning  Comp. Temp. Threshold: 80 Celsius
  Critical Comp. Temp. Threshold: 85 Celsius
  Namespace 1 Features (0x02):NA_Fields

  Supported Power States
  St Op Max   Active Idle   RL RT WL WT  Ent_Lat  Ex_Lat
   0 + 3.50W2.10W   -0  0  0  00   0
   1 + 2.40W1.60W   -0  0  0  00   0
   2 + 1.90W1.50W   -0  0  0  00   0
   3 -   0.0250W   --3  3  3  3 3900   11000
   4 -   0.0050W   --4  4  4  4 5000   39000

  Supported LBA Sizes (NSID 0x1)
  Id Fmt  Data  Metadt  Rel_Perf
   0 + 512   0 2
   1 -4096   0 1

  === START OF SMART DATA SECTION ===
  SMART overall-health self-assessment test result: PASSED

  SMART/Health Information (NVMe Log 0x02)
  Critical Warning:   0x00
  Temperature:35 Celsius
  Available Spare:100%
  Available Spare Threshold:  10%
  Percentage Used:0%
  Data Units Read:624,535 [319 GB]
  Data Units Written: 526,042 [269 GB]
  Host Read Commands: 4,462,163
  Host Write Commands:4,686,788
  Controller Busy Time:   25
  Power Cycles:   20
  Power On Hours: 76
  Unsafe Shutdowns:  

[Kernel-packages] [Bug 1930303] [NEW] package libnvidia-cfg1-450-server 450.102.04-0ubuntu0.20.04.1 failed to install/upgrade: read error in '/var/lib/dpkg/info/libnvidia-cfg1-450-server:amd64.trigger

[Bharatbhushan]

Public bug reported:

This came while updating the system

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libnvidia-cfg1-450-server 450.102.04-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon May 31 22:47:12 2021
DuplicateSignature:
 package:libnvidia-cfg1-450-server:450.102.04-0ubuntu0.20.04.1
 Preparing to unpack 
.../071-libnvidia-cfg1-450-server_450.119.03-0ubuntu0.20.04.1_amd64.deb ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-kJRTFO/071-libnvidia-cfg1-450-server_450.119.03-0ubuntu0.20.04.1_amd64.deb
 (--unpack):
  read error in '/var/lib/dpkg/info/libnvidia-cfg1-450-server:amd64.triggers': 
Input/output error
ErrorMessage: read error in 
'/var/lib/dpkg/info/libnvidia-cfg1-450-server:amd64.triggers': Input/output 
error
InstallationDate: Installed on 2021-01-06 (144 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.5
SourcePackage: nvidia-graphics-drivers-450-server
Title: package libnvidia-cfg1-450-server 450.102.04-0ubuntu0.20.04.1 failed to 
install/upgrade: read error in 
'/var/lib/dpkg/info/libnvidia-cfg1-450-server:amd64.triggers': Input/output 
error
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-450-server (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package libnvidia-cfg1-450-server 450.102.04-0ubuntu0.20.04.1 failed
  to install/upgrade: read error in '/var/lib/dpkg/info/libnvidia-
  cfg1-450-server:amd64.triggers': Input/output error

Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New

Bug description:
  This came while updating the system

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libnvidia-cfg1-450-server 450.102.04-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon May 31 22:47:12 2021
  DuplicateSignature:
   package:libnvidia-cfg1-450-server:450.102.04-0ubuntu0.20.04.1
   Preparing to unpack 
.../071-libnvidia-cfg1-450-server_450.119.03-0ubuntu0.20.04.1_amd64.deb ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-kJRTFO/071-libnvidia-cfg1-450-server_450.119.03-0ubuntu0.20.04.1_amd64.deb
 (--unpack):
read error in 
'/var/lib/dpkg/info/libnvidia-cfg1-450-server:amd64.triggers': Input/output 
error
  ErrorMessage: read error in 
'/var/lib/dpkg/info/libnvidia-cfg1-450-server:amd64.triggers': Input/output 
error
  InstallationDate: Installed on 2021-01-06 (144 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.5
  SourcePackage: nvidia-graphics-drivers-450-server
  Title: package libnvidia-cfg1-450-server 450.102.04-0ubuntu0.20.04.1 failed 
to install/upgrade: read error in 
'/var/lib/dpkg/info/libnvidia-cfg1-450-server:amd64.triggers': Input/output 
error
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450-server/+bug/1930303/+subscriptions

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

[Kernel-packages] [Bug 1909005] Re: Ubuntu does not resume (wake up) from suspend

[David Esteves]

Same problem on Dell Inspiron 5502
- bios 1.4.1
- Linux ubuntu 5.8.0-53-generic #60~20.04.1-Ubuntu SMP Thu May 6 09:52:46 UTC 
2021 x86_64 x86_64 x86_64 GNU/Linux

Sometimes it works, sometimes not. I couldn't find a way to reproduce
yet.

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

Title:
  Ubuntu does not resume (wake up) from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Whenever Ubuntu gets into suspend state, I cannot wake it up. 
  -Keystrokes start the fans but screen does not turn on and Ubuntu still seems 
to be suspended because in my teamviewer account the computer is still offline.
  -Power button clicks do not help
  -I always have to turn off computer by holding power button and then turn it 
on again.

  The only kernel that works is the following: "linux-image-5.0.0-1070
  -oem-osp1". But with this old kernel I run into different problems.

  I have the latest BIOS version from Dell (released 2020-11-27) and the
  latest updates in Ubuntu 20.04.

  I will post logs during suspend and important logs (found in Logs gui
  tool)

  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
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philip 2340 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 22 13:59:14 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18
  InstallationDate: Installed on 2019-12-04 (383 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3593
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep 
tsc=reliable 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: Upgraded to focal on 2020-11-04 (47 days ago)
  dmi.bios.date: 11/13/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 04N9HV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3593
  dmi.product.sku: 0979
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1929925] Re: [Potential Regression] Unable to create KVM with uvtool on Groovy ARM64

[Marcelo Cerri]

Attaching a patch with the fix to be tested.

I built a test kernel with the patch and the debian packages are
available at:

https://kernel.ubuntu.com/~mhcerri/lp1929925.1/

** Patch added: "0001-UBUNTU-SAUCE-KVM-arm64-Assign-kvm_ipa_limit.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929925/+attachment/5501464/+files/0001-UBUNTU-SAUCE-KVM-arm64-Assign-kvm_ipa_limit.patch

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

Title:
  [Potential Regression] Unable to create KVM with uvtool on Groovy
  ARM64

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

Bug description:
  Issue found on 5.8.0-54-generic proposed ARM64 kernel with node
  "helo", "wright"

  This issue does not exist in 5.8.0-53.60 so this might be a
  regression.

  Test case:
    1. Deploy Groovy on an ARM64 node
    2. Create a KVM with the following command:
   uvt-kvm create bjf-test release=groovy arch=arm64
       Or you can run the ubuntu_kvm_smoke_test with autotest:
   git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests 
-b master-next
   git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
   rm -fr autotest/client/tests
   ln -sf ~/autotest-client-tests autotest/client/tests
   sudo apt-get install git python-minimal -y || sudo apt install python2 -y
   AUTOTEST_PATH=/home/ubuntu/autotest sudo -E 
autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_kvm_smoke_test/control
    3. Install just the proposed kernel and reboot
    4. Repeat step 2

  This is 100% reproducible on ARM64, 4 out of 4 attempts (twice on each
  nodes).

  Test log:
    + SUT=bjf-test
    + SSH_KEY=/home/ubuntu/.ssh/id_rsa
    + SSH_OPTIONS='-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null 
-o LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa'
    ++ lsb_release -c
    ++ awk '{print$2}'
    + DISTRO=groovy
    + ARCHITECTURE=arm64
    + trap cleanup EXIT
    + '[' -z arm64 ']'
    + kvm-ok
    + '[' 0 '!=' 0 ']'
    + '[' '!' -f /home/ubuntu/.ssh/id_rsa ']'
    + '[' arm64 = ppc64el ']'
    ++ uvt-simplestreams-libvirt query
    ++ grep -P 'groovy.*arm64'
    + image='release=groovy arch=arm64 label=daily (20210527)'
    + '[' -z 'release=groovy arch=arm64 label=daily (20210527)' ']'
    + uvt-kvm create bjf-test release=groovy arch=arm64
    uvt-kvm: error: libvirt: unsupported configuration: Emulator 
'/usr/bin/qemu-system-aarch64' does not support virt type 'kvm'

  syslog:
  May 28 08:01:07 helo-kernel kernel: [ 1030.945560] mpt3sas :8d:00.0: 
invalid short VPD tag 00 at offset 1
  May 28 08:01:08 helo-kernel kernel: [ 1031.238058] sr 3:0:0:0: [sr0] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.242304] sr 3:0:0:0: [sr0] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.245430] sr 3:0:0:1: [sr1] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.248810] sr 3:0:0:1: [sr1] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.252678] sr 3:0:0:2: [sr2] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.255678] sr 3:0:0:2: [sr2] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.258811] sr 3:0:0:3: [sr3] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.272678] sr 3:0:0:3: [sr3] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:13 helo-kernel systemd[1]: Started Daemon for generating UUIDs.
  May 28 08:01:13 helo-kernel kernel: [ 1036.620470] qemu-system-aar using 
unsupported default IPA limit, upgrade your VMM
  May 28 08:01:14 helo-kernel libvirtd[3767]: libvirt version: 6.6.0, package: 
1ubuntu3.5 (Christian Ehrhardt  Wed, 07 Apr 
2021 13:33:46 +0200)
  May 28 08:01:14 helo-kernel libvirtd[3767]: hostname: helo-kernel
  May 28 08:01:14 helo-kernel libvirtd[3767]: unsupported configuration: 
Emulator '/usr/bin/qemu-system-aarch64' does not support virt type 'kvm'

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-54-generic 5.8.0-54.61
  ProcVersionSignature: Ubuntu 5.8.0-54.61-generic 5.8.18
  Uname: Linux 5.8.0-54-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 28 07:04 seq
   crw-rw 1 root audio 116, 33 May 28 07:04 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] 

[Kernel-packages] [Bug 1929925] Re: [Potential Regression] Unable to create KVM with uvtool on Groovy ARM64

[Marcelo Cerri]

As pointed out by Krzysztof the backport is dropping the line
`kvm_ipa_limit = ipa_max;`.

I will prepare a test kernel re-introducing this line.

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

Title:
  [Potential Regression] Unable to create KVM with uvtool on Groovy
  ARM64

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

Bug description:
  Issue found on 5.8.0-54-generic proposed ARM64 kernel with node
  "helo", "wright"

  This issue does not exist in 5.8.0-53.60 so this might be a
  regression.

  Test case:
    1. Deploy Groovy on an ARM64 node
    2. Create a KVM with the following command:
   uvt-kvm create bjf-test release=groovy arch=arm64
       Or you can run the ubuntu_kvm_smoke_test with autotest:
   git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests 
-b master-next
   git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
   rm -fr autotest/client/tests
   ln -sf ~/autotest-client-tests autotest/client/tests
   sudo apt-get install git python-minimal -y || sudo apt install python2 -y
   AUTOTEST_PATH=/home/ubuntu/autotest sudo -E 
autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_kvm_smoke_test/control
    3. Install just the proposed kernel and reboot
    4. Repeat step 2

  This is 100% reproducible on ARM64, 4 out of 4 attempts (twice on each
  nodes).

  Test log:
    + SUT=bjf-test
    + SSH_KEY=/home/ubuntu/.ssh/id_rsa
    + SSH_OPTIONS='-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null 
-o LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa'
    ++ lsb_release -c
    ++ awk '{print$2}'
    + DISTRO=groovy
    + ARCHITECTURE=arm64
    + trap cleanup EXIT
    + '[' -z arm64 ']'
    + kvm-ok
    + '[' 0 '!=' 0 ']'
    + '[' '!' -f /home/ubuntu/.ssh/id_rsa ']'
    + '[' arm64 = ppc64el ']'
    ++ uvt-simplestreams-libvirt query
    ++ grep -P 'groovy.*arm64'
    + image='release=groovy arch=arm64 label=daily (20210527)'
    + '[' -z 'release=groovy arch=arm64 label=daily (20210527)' ']'
    + uvt-kvm create bjf-test release=groovy arch=arm64
    uvt-kvm: error: libvirt: unsupported configuration: Emulator 
'/usr/bin/qemu-system-aarch64' does not support virt type 'kvm'

  syslog:
  May 28 08:01:07 helo-kernel kernel: [ 1030.945560] mpt3sas :8d:00.0: 
invalid short VPD tag 00 at offset 1
  May 28 08:01:08 helo-kernel kernel: [ 1031.238058] sr 3:0:0:0: [sr0] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.242304] sr 3:0:0:0: [sr0] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.245430] sr 3:0:0:1: [sr1] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.248810] sr 3:0:0:1: [sr1] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.252678] sr 3:0:0:2: [sr2] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.255678] sr 3:0:0:2: [sr2] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.258811] sr 3:0:0:3: [sr3] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.272678] sr 3:0:0:3: [sr3] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:13 helo-kernel systemd[1]: Started Daemon for generating UUIDs.
  May 28 08:01:13 helo-kernel kernel: [ 1036.620470] qemu-system-aar using 
unsupported default IPA limit, upgrade your VMM
  May 28 08:01:14 helo-kernel libvirtd[3767]: libvirt version: 6.6.0, package: 
1ubuntu3.5 (Christian Ehrhardt  Wed, 07 Apr 
2021 13:33:46 +0200)
  May 28 08:01:14 helo-kernel libvirtd[3767]: hostname: helo-kernel
  May 28 08:01:14 helo-kernel libvirtd[3767]: unsupported configuration: 
Emulator '/usr/bin/qemu-system-aarch64' does not support virt type 'kvm'

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-54-generic 5.8.0-54.61
  ProcVersionSignature: Ubuntu 5.8.0-54.61-generic 5.8.18
  Uname: Linux 5.8.0-54-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 28 07:04 seq
   crw-rw 1 root audio 116, 33 May 28 07:04 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDmesg:

  Date: Fri May 28 07:10:15 2021
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: To be filled by O.E.M. Saber
  PciMultimedia:

  ProcFB: 0 astdrmfb
 

[Kernel-packages] [Bug 1921870] Re: [UBUNTU 21.04] tools/kvm_stat: Add restart delay

[Frank Heimes]

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

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

Title:
  [UBUNTU 21.04] tools/kvm_stat: Add restart delay

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Hirsute:
  New
Status in linux source package in Impish:
  In Progress

Bug description:
  Description:   tools/kvm_stat: Add restart delay
  Symptom:   If the kvm service is enabled and the system rebooted,
 Systemd's initial attempt to start the kvm unit file may
 fail in case the kvm module is not loaded. However, once the
 kvm module is loaded, the service is _not_ started.
  Problem:   Since the unit file does not specify a delay for the retries,
 Systemd restarts with a minimum delay a number of times
 before giving up and disabling the service. Which means a
 subsequent kvm module load will have kvm running without
 monitoring.
  Solution:  Add an appropriate delay in the unit file.
  Reproduction:  (1) Enable the kvm service via systemctl
 (2) Reboot
 (3) Verify that the kvm module is not loaded & kvm service
 not running
 (4) Load the kvm module via 'modprobe kvm'
 (5) Verify that the kvm service came up within the next
 minute.
  Preventive:yes

  Just use the attached patch and you're good!

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

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

[Kernel-packages] [Bug 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)

[Rex Tsai]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
 Assignee: (unassigned) => Bin Li (binli)

** Changed in: oem-priority
 Assignee: Bin Li (binli) => Shengyao Xue (xueshengyao)

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

Title:
  Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently got a Thinkpad T14 Gen2 with a I219-V network adapter
  (8086:15fc). I get very slow connection speeds and even total loss of
  connectivity without seeing much in the logs (like dmesg etc.).
  ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel
  5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried
  the e1000e driver directly from upstream (3.8.7) with no success.

  A strange behaviour I observed: if connectivity is lost (notebook is
  not reachable via ping from another host), if I do something like
  "ping 8.8.8.8" on the notebook itself, it becomes reachable from the
  other host again.

  Downloads in general are very slow if they work at all.

  WLAN (AX210) seems to work fine, wired network using a USB-network adapter 
works fine, too.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ros3285 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 21.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-05-07 (2 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20W0004MGE
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  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.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  Tags:  hirsute
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/10/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N34ET21W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20W0004MGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 2i
  dmi.product.name: 20W0004MGE
  dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
  dmi.product.version: ThinkPad T14 Gen 2i
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1927925/+subscriptions

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

[Kernel-packages] [Bug 1929925] Re: [Potential Regression] Unable to create KVM with uvtool on Groovy ARM64

[Stefan Bader]

Maybe missing the following though nothing refers to it:

commit c9b69a0cf0b4336fe7d2e35c46273debc68910fd
Author: Will Deacon 
Date:   Fri Sep 11 14:25:29 2020 +0100

KVM: arm64: Don't constrain maximum IPA size based on host
configuration

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

Title:
  [Potential Regression] Unable to create KVM with uvtool on Groovy
  ARM64

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

Bug description:
  Issue found on 5.8.0-54-generic proposed ARM64 kernel with node
  "helo", "wright"

  This issue does not exist in 5.8.0-53.60 so this might be a
  regression.

  Test case:
    1. Deploy Groovy on an ARM64 node
    2. Create a KVM with the following command:
   uvt-kvm create bjf-test release=groovy arch=arm64
       Or you can run the ubuntu_kvm_smoke_test with autotest:
   git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests 
-b master-next
   git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
   rm -fr autotest/client/tests
   ln -sf ~/autotest-client-tests autotest/client/tests
   sudo apt-get install git python-minimal -y || sudo apt install python2 -y
   AUTOTEST_PATH=/home/ubuntu/autotest sudo -E 
autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_kvm_smoke_test/control
    3. Install just the proposed kernel and reboot
    4. Repeat step 2

  This is 100% reproducible on ARM64, 4 out of 4 attempts (twice on each
  nodes).

  Test log:
    + SUT=bjf-test
    + SSH_KEY=/home/ubuntu/.ssh/id_rsa
    + SSH_OPTIONS='-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null 
-o LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa'
    ++ lsb_release -c
    ++ awk '{print$2}'
    + DISTRO=groovy
    + ARCHITECTURE=arm64
    + trap cleanup EXIT
    + '[' -z arm64 ']'
    + kvm-ok
    + '[' 0 '!=' 0 ']'
    + '[' '!' -f /home/ubuntu/.ssh/id_rsa ']'
    + '[' arm64 = ppc64el ']'
    ++ uvt-simplestreams-libvirt query
    ++ grep -P 'groovy.*arm64'
    + image='release=groovy arch=arm64 label=daily (20210527)'
    + '[' -z 'release=groovy arch=arm64 label=daily (20210527)' ']'
    + uvt-kvm create bjf-test release=groovy arch=arm64
    uvt-kvm: error: libvirt: unsupported configuration: Emulator 
'/usr/bin/qemu-system-aarch64' does not support virt type 'kvm'

  syslog:
  May 28 08:01:07 helo-kernel kernel: [ 1030.945560] mpt3sas :8d:00.0: 
invalid short VPD tag 00 at offset 1
  May 28 08:01:08 helo-kernel kernel: [ 1031.238058] sr 3:0:0:0: [sr0] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.242304] sr 3:0:0:0: [sr0] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.245430] sr 3:0:0:1: [sr1] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.248810] sr 3:0:0:1: [sr1] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.252678] sr 3:0:0:2: [sr2] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.255678] sr 3:0:0:2: [sr2] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.258811] sr 3:0:0:3: [sr3] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.272678] sr 3:0:0:3: [sr3] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:13 helo-kernel systemd[1]: Started Daemon for generating UUIDs.
  May 28 08:01:13 helo-kernel kernel: [ 1036.620470] qemu-system-aar using 
unsupported default IPA limit, upgrade your VMM
  May 28 08:01:14 helo-kernel libvirtd[3767]: libvirt version: 6.6.0, package: 
1ubuntu3.5 (Christian Ehrhardt  Wed, 07 Apr 
2021 13:33:46 +0200)
  May 28 08:01:14 helo-kernel libvirtd[3767]: hostname: helo-kernel
  May 28 08:01:14 helo-kernel libvirtd[3767]: unsupported configuration: 
Emulator '/usr/bin/qemu-system-aarch64' does not support virt type 'kvm'

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-54-generic 5.8.0-54.61
  ProcVersionSignature: Ubuntu 5.8.0-54.61-generic 5.8.18
  Uname: Linux 5.8.0-54-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 28 07:04 seq
   crw-rw 1 root audio 116, 33 May 28 07:04 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu50.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDmesg:

  Date: Fri May 28 07:10:15 2021
  IwConfig: Error: [Errno 2] No such file or 

[Kernel-packages] [Bug 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)

[Roland Sommer]

I still encounter very bad network connectivity using the
5.10.0-1026-oem kernel while running Ubuntu 20.04.

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

Title:
  Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently got a Thinkpad T14 Gen2 with a I219-V network adapter
  (8086:15fc). I get very slow connection speeds and even total loss of
  connectivity without seeing much in the logs (like dmesg etc.).
  ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel
  5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried
  the e1000e driver directly from upstream (3.8.7) with no success.

  A strange behaviour I observed: if connectivity is lost (notebook is
  not reachable via ping from another host), if I do something like
  "ping 8.8.8.8" on the notebook itself, it becomes reachable from the
  other host again.

  Downloads in general are very slow if they work at all.

  WLAN (AX210) seems to work fine, wired network using a USB-network adapter 
works fine, too.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ros3285 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 21.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-05-07 (2 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20W0004MGE
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  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.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  Tags:  hirsute
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/10/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N34ET21W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20W0004MGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 2i
  dmi.product.name: 20W0004MGE
  dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
  dmi.product.version: ThinkPad T14 Gen 2i
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1921870] Re: [UBUNTU 21.04] tools/kvm_stat: Add restart delay

[Krzysztof Kozlowski]

Patch submitted for review:
https://lists.ubuntu.com/archives/kernel-team/2021-May/120907.html

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

Title:
  [UBUNTU 21.04] tools/kvm_stat: Add restart delay

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  New
Status in linux source package in Hirsute:
  New
Status in linux source package in Impish:
  New

Bug description:
  Description:   tools/kvm_stat: Add restart delay
  Symptom:   If the kvm service is enabled and the system rebooted,
 Systemd's initial attempt to start the kvm unit file may
 fail in case the kvm module is not loaded. However, once the
 kvm module is loaded, the service is _not_ started.
  Problem:   Since the unit file does not specify a delay for the retries,
 Systemd restarts with a minimum delay a number of times
 before giving up and disabling the service. Which means a
 subsequent kvm module load will have kvm running without
 monitoring.
  Solution:  Add an appropriate delay in the unit file.
  Reproduction:  (1) Enable the kvm service via systemctl
 (2) Reboot
 (3) Verify that the kvm module is not loaded & kvm service
 not running
 (4) Load the kvm module via 'modprobe kvm'
 (5) Verify that the kvm service came up within the next
 minute.
  Preventive:yes

  Just use the attached patch and you're good!

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

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

[Kernel-packages] [Bug 1921870] Re: [UBUNTU 21.04] tools/kvm_stat: Add restart delay

[Krzysztof Kozlowski]

** Changed in: ubuntu-z-systems
   Status: Triaged => In Progress

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

Title:
  [UBUNTU 21.04] tools/kvm_stat: Add restart delay

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  New
Status in linux source package in Hirsute:
  New
Status in linux source package in Impish:
  New

Bug description:
  Description:   tools/kvm_stat: Add restart delay
  Symptom:   If the kvm service is enabled and the system rebooted,
 Systemd's initial attempt to start the kvm unit file may
 fail in case the kvm module is not loaded. However, once the
 kvm module is loaded, the service is _not_ started.
  Problem:   Since the unit file does not specify a delay for the retries,
 Systemd restarts with a minimum delay a number of times
 before giving up and disabling the service. Which means a
 subsequent kvm module load will have kvm running without
 monitoring.
  Solution:  Add an appropriate delay in the unit file.
  Reproduction:  (1) Enable the kvm service via systemctl
 (2) Reboot
 (3) Verify that the kvm module is not loaded & kvm service
 not running
 (4) Load the kvm module via 'modprobe kvm'
 (5) Verify that the kvm service came up within the next
 minute.
  Preventive:yes

  Just use the attached patch and you're good!

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

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

[Kernel-packages] [Bug 1926809] Re: WD19 dock stops working in Ubuntu 21.04

[Harald]

I think here are more information:
https://gitlab.freedesktop.org/drm/intel/-/issues/2579

** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #2579
   https://gitlab.freedesktop.org/drm/intel/-/issues/2579

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

Title:
  WD19 dock stops working in Ubuntu 21.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This morning I upgraded to Kubuntu 21.04.

  I use two external monitors connected to my Dell XPS laptop via a Dell
  WD19 dock.

  Post-upgrade the monitors and also network functionality through the
  dock appear to have completely stopped functioning.

  When the dock is plugged in and the computer is booted the monitors do not 
enable.
  When the dock is not plugged in the computer boots normally.

  When I look at the dmesg output there appears to be some notable
  errors when I plug the dock in:

  [  516.173451] xhci_hcd :39:00.0: xHCI host controller not responding, 
assume dead
  [  516.207480] xhci_hcd :39:00.0: HC died; cleaning up
  [  521.313422] pcieport :02:00.0: can't change power state from D3cold to 
D0 (config space inaccessible)
  [  555.140320] xhci_hcd :39:00.0: xHCI host controller not responding, 
assume dead
  [  555.140343] xhci_hcd :39:00.0: HC died; cleaning up
  [  560.291086] pcieport :02:00.0: can't change power state from D3cold to 
D0 (config space inaccessible)
  [  850.385934] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 
eaa106e4 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed
  [  850.499763] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 
eaa106e4 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed
  [  851.717630] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  [  851.815190] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  [  856.231021] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 
eaa106e4 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed
  [  856.301269] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 
eaa106e4 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed
  [  856.320487] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  [  856.343208] i915 :00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun
  [  856.382831] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  [  860.704920] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  [  860.765138] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  [  860.894454] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  [  860.965337] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  [  861.115198] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  [  861.182111] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  [  866.232326] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 
eaa106e4 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed
  [  866.351715] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  [  866.454536] [drm:drm_dp_send_dpcd_read [drm_kms_helper]] *ERROR* mstb 
eaa106e4 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed
  [  866.473097] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
  [  866.534697] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful

  With the dock plugged in:

  * neither monitor displays although they are present under display 
configuration
  * since my laptop screen is not usually on if both monitors are present on 
the dock the immediate result was no display at all under the dock was detached
  * network connectivity is not established although the network device appears 
under networks

  Unfortunately I lack the skills to diagnose this further without
  assistance or to install a more recent kernel to see if it is resolved
  there.

  It appears that communications between the laptop and the Dock are not
  going well to my eyes (is this what link training is on Thunderbolt)

  I'm happy to provide further information... although in a few days the
  lack of Dock and monitors will be a bit of an issue and I may have to
  roll something back.

  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
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mulhollandd   1940 F pulseaudio
   /dev/snd/controlC1:  mulhollandd   1940 F pulseaudio
   /dev/snd/controlC0:  mulhollandd   1940 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sat May  1 08:57:26 2021
  InstallationDate: Installed on 2020-06-13 (321 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - 

[Kernel-packages] [Bug 1930288] Re: Picure breaks up when using TV tuner

[Dennisnail]

I also tried the kernel from Groovy Gorilla 5.8.0-36 and from Hirsute Hippo 
5.11.0-16
Both failed.

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

Title:
  Picure breaks up when using TV tuner

Status in linux package in Ubuntu:
  New

Bug description:
  I am using a Hauppauge HVR-1950 TV tuner with my Dell Inspiron 5567 laptop. 
When using the tuner the picture and audio break up as if the signal is weak. 
All of the kernels since upgrading to 20.04 have failed, most recently 5.4.0-73
  It worked fine when I was using 18.04 Bionic Beaver and it works with the 
current bionic kernel, 4.15.0-143
  It also works with the mainline kernel, most recently 5.4.111

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-73-generic 5.4.0-73.82
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1042 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 31 10:25:28 2021
  InstallationDate: Installed on 2019-10-01 (608 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 5567
  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.4.0-73-generic 
root=UUID=35b8961f-2fe6-4648-a54e-583d411153fd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-73-generic N/A
   linux-backports-modules-5.4.0-73-generic  N/A
   linux-firmware1.187.12
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-10-02 (241 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.6
  dmi.board.name: 04M49V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.6:bd07/09/2018:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn04M49V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5567
  dmi.product.sku: 0767
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1930288] [NEW] Picure breaks up when using TV tuner

[Dennisnail]

Public bug reported:

I am using a Hauppauge HVR-1950 TV tuner with my Dell Inspiron 5567 laptop. 
When using the tuner the picture and audio break up as if the signal is weak. 
All of the kernels since upgrading to 20.04 have failed, most recently 5.4.0-73
It worked fine when I was using 18.04 Bionic Beaver and it works with the 
current bionic kernel, 4.15.0-143
It also works with the mainline kernel, most recently 5.4.111

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-73-generic 5.4.0-73.82
ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
Uname: Linux 5.4.0-73-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dennis 1042 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 31 10:25:28 2021
InstallationDate: Installed on 2019-10-01 (608 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. Inspiron 5567
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.4.0-73-generic 
root=UUID=35b8961f-2fe6-4648-a54e-583d411153fd ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-73-generic N/A
 linux-backports-modules-5.4.0-73-generic  N/A
 linux-firmware1.187.12
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-10-02 (241 days ago)
dmi.bios.date: 07/09/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.6
dmi.board.name: 04M49V
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.6:bd07/09/2018:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn04M49V:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5567
dmi.product.sku: 0767
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal third-party-packages

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

Title:
  Picure breaks up when using TV tuner

Status in linux package in Ubuntu:
  New

Bug description:
  I am using a Hauppauge HVR-1950 TV tuner with my Dell Inspiron 5567 laptop. 
When using the tuner the picture and audio break up as if the signal is weak. 
All of the kernels since upgrading to 20.04 have failed, most recently 5.4.0-73
  It worked fine when I was using 18.04 Bionic Beaver and it works with the 
current bionic kernel, 4.15.0-143
  It also works with the mainline kernel, most recently 5.4.111

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-73-generic 5.4.0-73.82
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1042 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 31 10:25:28 2021
  InstallationDate: Installed on 2019-10-01 (608 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 5567
  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.4.0-73-generic 
root=UUID=35b8961f-2fe6-4648-a54e-583d411153fd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-73-generic N/A
   linux-backports-modules-5.4.0-73-generic  N/A
   linux-firmware1.187.12
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-10-02 (241 days ago)
  dmi.bios.date: 07/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.6
  dmi.board.name: 04M49V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.6:bd07/09/2018:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn04M49V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5567
  dmi.product.sku: 0767
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)

[Roland Sommer]

This laptop has been certified for 20.04 using the latest OEM kernel:

https://certification.ubuntu.com/hardware/202104-28912

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

Title:
  Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently got a Thinkpad T14 Gen2 with a I219-V network adapter
  (8086:15fc). I get very slow connection speeds and even total loss of
  connectivity without seeing much in the logs (like dmesg etc.).
  ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel
  5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried
  the e1000e driver directly from upstream (3.8.7) with no success.

  A strange behaviour I observed: if connectivity is lost (notebook is
  not reachable via ping from another host), if I do something like
  "ping 8.8.8.8" on the notebook itself, it becomes reachable from the
  other host again.

  Downloads in general are very slow if they work at all.

  WLAN (AX210) seems to work fine, wired network using a USB-network adapter 
works fine, too.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ros3285 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 21.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2021-05-07 (2 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20W0004MGE
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic 
root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  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.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  Tags:  hirsute
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/10/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N34ET21W (1.10 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20W0004MGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 2i
  dmi.product.name: 20W0004MGE
  dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
  dmi.product.version: ThinkPad T14 Gen 2i
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues

[Bijay Shah]

Hello I can't seem to boot with with kernel, something related to
unpacking initparms error. The size of this kernel image seems off as
well only 12mb, I am sure kernel image was around 65+ mb. Please check
once 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/1930188

Title:
  Acer Aspire 5 sound driver issues

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  There seems to be lots of issues in sound driver for Acer Aspire
  A515-56-57XR with ALC255. I will list all of them below and what I
  have tried so far.

  1. Headphones appears always plugged in even if they are physically not
  2. When actually plugging in headset/earphones it does not auto switch from 
speakers/internal mic to headphones/headset microphone automatically and vice 
versa, have to manually switch everytime.
  3. External headset/earphones microphone won't work at all

  After, logs of trial and error I have found a temporary fix. This
  seems to use legacy intel drivers which solves all 3 issues mentioned
  above but the internal/dmic mic is completely gone (which seems
  intentional when using this). Both depreciated dmic_detect and
  dsp_driver works, I have been using dsp_driver for now as I need
  external microphone at any cost.

  End of /etc/modprobe.d/alsa-base.conf
  # Headset mic fix
  options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1
  options snd-hda-intel model=alc255-acer

  In another thread similar to this I got some support and at least
  fixed the external microphone without using the alsa-base.conf change
  in custom modified kernel. I will attach it here. Now, hoping to fix
  other issues as well slowly like making headphones unplugged when
  physically removing as well as auto switching like the legacy driver
  one.

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

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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oracle-5.4/5.4.0.1046.50~18.04.28)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-oracle-5.4 
(5.4.0.1046.50~18.04.28) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/0.7.5-1ubuntu16.11 (amd64)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
virtualbox/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64)
virtualbox-hwe/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64)
kpatch/0.5.0-0ubuntu1.1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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

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

[Kernel-packages] [Bug 1927704] Autopkgtest regression report (linux-meta-oracle-5.4/5.4.0.1046.50~18.04.28)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-oracle-5.4 
(5.4.0.1046.50~18.04.28) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/0.7.5-1ubuntu16.11 (amd64)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
virtualbox/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64)
virtualbox-hwe/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64)
kpatch/0.5.0-0ubuntu1.1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Incorrect meta provides and dependencies

Status in linux-meta-oracle package in Ubuntu:
  Invalid
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-meta-oracle source package in Focal:
  Fix Released
Status in linux-oracle source package in Focal:
  Invalid

Bug description:
  [Impact]

  linux-image-oracle for arm64 incorrectly:
  1) provides virtualbox-guest-modules.
  2) doesn't depend on linux-modules-extra--oracle.

  [Test Case]

  $ dpkg-deb -I linux-image-oracle_5.4.0.1045.43_arm64.deb  | grep -P 
'Depends|Provides'
   Depends: linux-image-5.4.0-1045-oracle
   Provides: virtualbox-guest-modules (= 6.1.16-dfsg-6~ubuntu1.20.04.1), 
wireguard-modules (= 1.0.20201112-1~20.04.1), zfs-modules (= 0.8.3-1ubuntu12.7)

  [Where Problems Could Occur]

  Package upgrades?

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

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

[Kernel-packages] [Bug 1929925] Re: [Potential Regression] Unable to create KVM with uvtool on Groovy ARM64

[Stefan Bader]

This seems to be a deliberate action caused by:

commit c526c11a462c4f1c0a88735b6e2d1083a9655d0b
Author: Marc Zyngier 
Date:   Thu Mar 11 10:00:15 2021 +

KVM: arm64: Reject VM creation when the default IPA size is unsupported

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

commit 7d717558dd5ef10d28866750d5c24ff892ea3778 upstream.

KVM/arm64 has forever used a 40bit default IPA space, partially
due to its 32bit heritage (where the only choice is 40bit).
...

This adds an -EINVAL exit with the following message logged (visible in the 
rport):
May 28 08:01:13 helo-kernel kernel: [ 1036.620470] qemu-system-aar using 
unsupported default IPA limit, upgrade your VMM

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

Title:
  [Potential Regression] Unable to create KVM with uvtool on Groovy
  ARM64

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

Bug description:
  Issue found on 5.8.0-54-generic proposed ARM64 kernel with node
  "helo", "wright"

  This issue does not exist in 5.8.0-53.60 so this might be a
  regression.

  Test case:
    1. Deploy Groovy on an ARM64 node
    2. Create a KVM with the following command:
   uvt-kvm create bjf-test release=groovy arch=arm64
       Or you can run the ubuntu_kvm_smoke_test with autotest:
   git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests 
-b master-next
   git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
   rm -fr autotest/client/tests
   ln -sf ~/autotest-client-tests autotest/client/tests
   sudo apt-get install git python-minimal -y || sudo apt install python2 -y
   AUTOTEST_PATH=/home/ubuntu/autotest sudo -E 
autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_kvm_smoke_test/control
    3. Install just the proposed kernel and reboot
    4. Repeat step 2

  This is 100% reproducible on ARM64, 4 out of 4 attempts (twice on each
  nodes).

  Test log:
    + SUT=bjf-test
    + SSH_KEY=/home/ubuntu/.ssh/id_rsa
    + SSH_OPTIONS='-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null 
-o LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa'
    ++ lsb_release -c
    ++ awk '{print$2}'
    + DISTRO=groovy
    + ARCHITECTURE=arm64
    + trap cleanup EXIT
    + '[' -z arm64 ']'
    + kvm-ok
    + '[' 0 '!=' 0 ']'
    + '[' '!' -f /home/ubuntu/.ssh/id_rsa ']'
    + '[' arm64 = ppc64el ']'
    ++ uvt-simplestreams-libvirt query
    ++ grep -P 'groovy.*arm64'
    + image='release=groovy arch=arm64 label=daily (20210527)'
    + '[' -z 'release=groovy arch=arm64 label=daily (20210527)' ']'
    + uvt-kvm create bjf-test release=groovy arch=arm64
    uvt-kvm: error: libvirt: unsupported configuration: Emulator 
'/usr/bin/qemu-system-aarch64' does not support virt type 'kvm'

  syslog:
  May 28 08:01:07 helo-kernel kernel: [ 1030.945560] mpt3sas :8d:00.0: 
invalid short VPD tag 00 at offset 1
  May 28 08:01:08 helo-kernel kernel: [ 1031.238058] sr 3:0:0:0: [sr0] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.242304] sr 3:0:0:0: [sr0] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.245430] sr 3:0:0:1: [sr1] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.248810] sr 3:0:0:1: [sr1] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.252678] sr 3:0:0:2: [sr2] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.255678] sr 3:0:0:2: [sr2] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.258811] sr 3:0:0:3: [sr3] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:08 helo-kernel kernel: [ 1031.272678] sr 3:0:0:3: [sr3] CDROM 
not ready.  Make sure there is a disc in the drive.
  May 28 08:01:13 helo-kernel systemd[1]: Started Daemon for generating UUIDs.
  May 28 08:01:13 helo-kernel kernel: [ 1036.620470] qemu-system-aar using 
unsupported default IPA limit, upgrade your VMM
  May 28 08:01:14 helo-kernel libvirtd[3767]: libvirt version: 6.6.0, package: 
1ubuntu3.5 (Christian Ehrhardt  Wed, 07 Apr 
2021 13:33:46 +0200)
  May 28 08:01:14 helo-kernel libvirtd[3767]: hostname: helo-kernel
  May 28 08:01:14 helo-kernel libvirtd[3767]: unsupported configuration: 
Emulator '/usr/bin/qemu-system-aarch64' does not support virt type 'kvm'

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-54-generic 5.8.0-54.61
  ProcVersionSignature: Ubuntu 5.8.0-54.61-generic 5.8.18
  Uname: Linux 5.8.0-54-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 28 07:04 seq
   crw-rw 1 root audio 

[Kernel-packages] [Bug 1930179] Re: Advantech CAN driver not recognized in Ubuntu Core 20

[Maciej Borzecki]

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

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

Title:
  Advantech CAN driver not recognized in Ubuntu Core 20

Status in linux package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Incomplete

Bug description:
  CAN module is not built into the kernel source for Ubuntu Core 20,
  hence, the CAN interface did not show up. Purpose to include
  Advantech's CAN driver for board MIO5373.

  Please kindly consider and refer to the attachment for the CAN driver
  source code and instructions. I hope the driver can be included as
  part of the official kernel.

   
  Thank you.

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

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

[Kernel-packages] [Bug 1920674] Re: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation

[RBX2]

Can you please be more specific about what I'm supposed to do? I suspect
building kernel from source is involved ... I did not do that for at
least 15 years.

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

Title:
  AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dear developers, please let me thank you for all your hard work first
  of all, I'm a big fan of yours!

  On my desktop PC with AMD A8-7680 APU, I'm facing 2 problems which
  seem to be connected to the amdgpu kernel module:

  1. Amdgpu kernel module loads correctly during boot, but VESA Xorg
  module is loaded instead of AMDGPU Xorg module during X startup. This
  results in non-accelerated X and high CPU load.

  - This situation is always reproducible.

  - I'm experiencing it with all kernel versions in between
  5.4.0-47-generic and 5.4.0-67-generic inclusive.

  - The situation escalates more with newer kernel version. For
  5.8.0-45-generic and 5.11.8-051108-generic, X even does not start and
  I just get black screen.

  - I have found a workaround after many days of googling and testing. AMDGPU 
Xorg module is loaded correctly if and only if I disable AMD ACP by means of 
the following kernel boot parameter:
  amdgpu.ip_block_mask=0xfdff

  - Acceleration is ok with kernels where AMD ACP is disabled by default
  (linux-image-linuxlite-5.6.0 for example)

  
  2. The 2nd problem I'm facing is with non functioning hibernation after I 
"fixed" the X acceleration. Hibernation image does not seem to get created, 
screen goes black, PC freezes but never turns off whenever AMDGPU Xorg module 
is loaded. Hibernation and subsequent resume is all ok if I disable AMDGPU by 
means of "nomodeset" and go just with VESA module.

  - always reproducible but tested only with 5.4.0-67-generic

  
  Thank you and best regards,
  Radek

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-67-generic 5.4.0-67.75
  ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94
  Uname: Linux 5.4.0-67-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  radek  1513 F pulseaudio
   /dev/snd/controlC0:  radek  1513 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Mar 21 15:22:29 2021
  HibernationDevice: RESUME=/dev/disk/by-label/SSD_LinuxSwap
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic 
root=UUID=1cc747ae-f2db-4733-aa04-be8d4bde050a ro ipv6.disable=1 net.ifnames=0 
nmi_watchdog=0 resume=LABEL=SSD_LinuxSwap amdgpu.ip_block_mask=0xfdff 
no_console_suspend
  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:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.20
  dmi.board.name: FM2A68M-HD+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.20:bd02/13/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+:rvr:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1918253] Re: WWAN I XMM 7360 LTE-Advanced (Cat 9) doesn't work [8086:7360]

[jeremyszu]

** Tags added: originate-from-1930268

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

Title:
  WWAN I XMM 7360 LTE-Advanced (Cat 9) doesn't work [8086:7360]

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  There is no driver for it [8086:7360] when using 5.10 kernel.

  $ lspci -nnv -s 55:00.0
  55:00.0 Wireless controller [0d40]: Intel Corporation XMM7360 LTE Advanced 
Modem [8086:7360] (rev 01)
Subsystem: Hewlett-Packard Company XMM7360 LTE Advanced Modem 
[103c:8337]
Flags: fast devsel, IRQ 255
Memory at 6e40 (64-bit, non-prefetchable) [disabled] [size=4K]
Memory at 6e401000 (64-bit, non-prefetchable) [disabled] [size=1K]
Capabilities: 

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918253/+subscriptions

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

[Kernel-packages] [Bug 1911055] Re: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed

[Hugo Ferreira]

I had the same issue in a ZBook G5 but interestingly enough I got this
working.

Some background: I had used the Nvidia drive 460 with success. However
due to a small mishap, I had to reinstall Ubuntu. Second time around,
though I go the error reported here. I tried installing the drives
directly via the "Software & Updates -> Additional Driver" application
and via the packages (never NVIDIAs scripts). But these did not work.
But the following 2 steps seemed to get this doing:

1. Configure the use of the suspend and resume scripts shown here: 
https://download.nvidia.com/XFree86/Linux-x86_64/460.39/README/powermanagement.html

2. Use the "Software & Updates -> Additional Driver" application but use
the "NVIDIA Server Driver metapackage  ... (proprietery)" and *not* the
"NVIDIA driver metapackage ... (proprietary, tested)"

Tests show both NVIDia profiles work now on resume.

It would be interresting to get feedback from others. If this in fact
does work, then one needs to know what is the diffference between the
above two options.

HTHs

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

Title:
  [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine
  push buffer channel allocation failed

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed

Bug description:
  After a recent update to nvidia-460, suspend then resume results in a
  black screen, then a hang for around 120 seconds, and then the text:

  nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation 
failed: 0x65 (Call timed out [NV_ERR_TIMEOUT])
  nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push 
buffer
  nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation 
failed: 0x65 (Call timed out [NV_ERR_TIMEOUT])
  nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push 
buffer

  dmesg shows:

  [  188.352670] ACPI: Waking up from system sleep state S3
  ...
  [  309.142164] nvidia-modeset: ERROR: GPU:0: Display engine push buffer 
channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT])
  [  309.142319] nvidia-modeset: ERROR: GPU:0: Failed to allocate display 
engine core DMA push buffer
  [  313.142165] nvidia-modeset: ERROR: GPU:0: Display engine push buffer 
channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT])
  [  313.142348] nvidia-modeset: ERROR: GPU:0: Failed to allocate display 
engine core DMA push buffer
  [  313.151885] acpi LNXPOWER:08: Turning OFF
  [  313.151898] acpi LNXPOWER:04: Turning OFF
  [  313.152351] acpi LNXPOWER:03: Turning OFF
  [  313.153064] acpi LNXPOWER:02: Turning OFF
  ...
  [  325.010192] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for 
display device DELL 2209WA (HDMI-0)
  [  325.010577] BUG: kernel NULL pointer dereference, address: 0050
  [  325.010579] #PF: supervisor read access in kernel mode
  [  325.010580] #PF: error_code(0x) - not-present page
  [  325.010580] PGD 0 P4D 0
  [  325.010582] Oops:  [#1] SMP PTI
  [  325.010583] CPU: 9 PID: 2247 Comm: Xorg Tainted: P   O  
5.4.0-60-generic #67-Ubuntu
  [  325.010584] Hardware name: Razer Blade/DANA_MB, BIOS 01.01 08/31/2018
  [  325.010595] RIP: 0010:_nv000112kms+0xd/0x30 [nvidia_modeset]
  [  325.010596] Code: 16 00 74 06 83 7e 0c 02 77 03 31 c0 c3 c7 46 0c 01 00 00 
00 b8 01 00 00 00 c3 0f 1f 00 0f b7 46 04 0f b7 56 08 39 d0 0f 47 c2 <3b> 47 18 
77 06 83 7e 10 02 77 08 31 c0 c3 0f 1f 44 00 00 c7 46 10
  [  325.010597] RSP: 0018:b89542e5b8a8 EFLAGS: 00010246
  [  325.010598] RAX: 0280 RBX: 0038 RCX: 
03ff
  [  325.010598] RDX: 0280 RSI: b89542e5bba0 RDI: 
0038
  [  325.010599] RBP: b89542e5b9c8 R08:  R09: 
c379e440
  [  325.010600] R10:  R11:  R12: 
b89542e5b948
  [  325.010600] R13: b89542e5b948 R14: b89542e5b930 R15: 
c3a50e60
  [  325.010601] FS:  7feb4c09ea80() GS:8e46ada4() 
knlGS:
  [  325.010602] CS:  0010 DS:  ES:  CR0: 80050033
  [  325.010602] CR2: 0050 CR3: 0004772e2006 CR4: 
003606e0
  [  325.010603] Call Trace:
  [  325.010610]  ? _nv002768kms+0x96/0xd0 [nvidia_modeset]
  [  325.010616]  ? _nv002328kms+0xb5/0x110 [nvidia_modeset]
  [  325.010624]  ? _nv000742kms+0x168/0x370 [nvidia_modeset]
  [  325.010823]  ? _nv036002rm+0x62/0x70 [nvidia]
  [  325.010910]  ? os_get_current_tick+0x2c/0x50 [nvidia]
  [  325.010921]  ? _nv002771kms+0x433/0x600 [nvidia_modeset]
  [  325.010928]  ? _nv002771kms+0x3fc/0x600 [nvidia_modeset]
  [  325.010930]  ? __schedule+0x2eb/0x740
  [  325.010935]  ? _nv000742kms+0x40/0x40 [nvidia_modeset]
  [  325.010939]  ? nvkms_alloc+0x6a/0xa0 [nvidia_modeset]
  [  325.010944]  ? 

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oem-5.10/5.10.0.1029.30)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-oem-5.10 (5.10.0.1029.30) 
for focal have finished running.
The following regressions have been reported in tests triggered by the package:

dm-writeboost/2.2.9-1ubuntu1.2 (amd64)
systemd/245.4-4ubuntu3.6 (amd64)
virtualbox/6.1.16-dfsg-6~ubuntu1.20.04.2 (amd64)
nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 (amd64)
dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 (amd64)
rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2 (amd64)
xtables-addons/3.9-1ubuntu0.2~20.04.1 (amd64)
broadcom-sta/6.30.223.271-12 (amd64)
evdi/1.7.0+dfsg-1ubuntu1~20.04.3 (amd64)
lttng-modules/2.12.2-1ubuntu1~20.04.2 (amd64)
virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (amd64)
backport-iwlwifi-dkms/8324-0ubuntu3~20.04.3 (amd64)
bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 (amd64)
lime-forensics/1.9-1ubuntu0.2 (amd64)
openafs/1.8.4~pre1-1ubuntu2.1 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-oem-5.10

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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

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

[Kernel-packages] [Bug 1927692] Re: AWS: out of entropy on Graviton 2 instances types (mg6.*)

[Andrea Righi]

** 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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1927692

Title:
  AWS: out of entropy on Graviton 2 instances types (mg6.*)

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  AWS Graviton 2 instances do not have enough entropy available at boot,
  so any task that require entropy (even reading few bytes from
  /dev/random) will be stuck forever.

  [Fix]

  The proper fix for this problem is to correctly refill the entropy
  pool with some real random data using some hardware-generated
  randomness.

  In the meantime a reasonable workaround can be to apply the following
  upstream commits:

   30c08efec888 random: make /dev/random be almost like /dev/urandom
   48446f198f9a random: ignore GRND_RANDOM in getentropy(2)
   75551dbf112c random: add GRND_INSECURE to return best-effort 
non-cryptographic bytes
   c6f1deb15878 random: Add a urandom_read_nowait() for random APIs that don't 
warn
   4c8d062186d9 random: Don't wake crng_init_wait when crng_init == 1

  In this way the system will not run out of entropy and will be able to
  provide best-effort randomness in any case, preventing the out of
  entropy issue on the AWS Gravion 2 instances.

  [Test plan]

  Execute the following command on any m6g instance:

    dd bs=32 count=1 if=/dev/random of=/dev/null

  This should return quickly, if not it means that the system does not
  have enough entropy available. When the problem happens this command
  hangs forever.

  [Where problems could occur]

  This changes affect the read semantics of /dev/random to be the same
  as /dev/urandom except that reads will block until the CRNG is ready.
  This should not materially break any API. Any code that worked without
  these changes should work at least as well as before. However,
  applications that have strict randomness requirements might be
  affected by the provided best-effort randomness, so we may need to
  apply more commits/changes to introduce a proper hardware entropy
  support on Graviton 2 instances to provide a better quality of
  randomness. In the meantime these upstream changes consist a
  reasonable workaround to prevent applications from hanging forever on
  the mg6.* instances.

  [Other Info]
  SF: #00310204

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

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

[Kernel-packages] [Bug 1929444] Re: SD card initialization on insertion fails

[Gordon Lack]

I don't have Secure Boot enabled anyway, so that bit's easy.

As for the v2 kernel - it FAILS (with the -84 error).

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

Title:
  SD card initialization on insertion fails

Status in linux package in Ubuntu:
  New

Bug description:
  If I boot my laptop with an SD card (actually SDXC) in the MMC slot
  the system sees it and I can mount and use it.

  If I then unmount it, remove it then re-insert it I get this in the
  system ,og:

  [  194.673108] mmc0: card e624 removed
  [  205.462065] mmc0: cannot verify signal voltage switch
  [  205.567479] mmc0: error -84 whilst initialising SD card

  and the card cannot then be used.

  It was OK in groovy. It's failing in hirsute.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-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:  gml44104153 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Mon May 24 17:36:49 2021
  HibernationDevice: RESUME=UUID=03dec042-8ba2-48a8-8d19-373ca2e0829c
  InstallationDate: Installed on 2020-08-13 (284 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: PC Specialist LTD N150CU
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=b21720c3-60bf-4298-9d73-743672f89216 ro quiet splash 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
  UpgradeStatus: Upgraded to hirsute on 2021-05-13 (11 days ago)
  dmi.bios.date: 11/15/2019
  dmi.bios.release: 7.7
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.07TPCS2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N151CU
  dmi.board.vendor: CLEVO
  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.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N150CU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist LTD

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

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

[Kernel-packages] [Bug 1930086] Re: [22.04 FEAT] gcc tunings for power9

[Frank Heimes]

** Also affects: gcc-defaults (Ubuntu)
   Importance: Undecided
   Status: New

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

** Tags added: ppc64el

** Tags added: targetmilestone-inin2204

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

Title:
  [22.04 FEAT] gcc tunings for power9

Status in The Ubuntu-power-systems project:
  New
Status in gcc-defaults package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  This is an Ubuntu-power-systems 22.04 LTS feature bug to track
  changing the gcc configure options from --with-cpu=power8 to --with-
  cpu=power9.

  Prerequisites for this bug include power9 builder hardware in
  Canonical datacenter.

  I'm still learning my way around Debian/Ubuntu source so go easy on me
  if this isn't the correct branch:

  https://salsa.debian.org/toolchain-
  team/gcc/-/blob/gcc-10-debian/debian/rules2#L394

  But we'll want to add some logic around line 394 to add --with-
  cpu=power9 for 22.04 and possibly --with-tune=? but I'll reverse
  mirror this bug and verify with our IBM Power toolchain architect.

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

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

[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues

[Hui Wang]

Please test this kernel, no need to add any temp fix.

https://people.canonical.com/~hwang4/lp1930188/

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

Title:
  Acer Aspire 5 sound driver issues

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  There seems to be lots of issues in sound driver for Acer Aspire
  A515-56-57XR with ALC255. I will list all of them below and what I
  have tried so far.

  1. Headphones appears always plugged in even if they are physically not
  2. When actually plugging in headset/earphones it does not auto switch from 
speakers/internal mic to headphones/headset microphone automatically and vice 
versa, have to manually switch everytime.
  3. External headset/earphones microphone won't work at all

  After, logs of trial and error I have found a temporary fix. This
  seems to use legacy intel drivers which solves all 3 issues mentioned
  above but the internal/dmic mic is completely gone (which seems
  intentional when using this). Both depreciated dmic_detect and
  dsp_driver works, I have been using dsp_driver for now as I need
  external microphone at any cost.

  End of /etc/modprobe.d/alsa-base.conf
  # Headset mic fix
  options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1
  options snd-hda-intel model=alc255-acer

  In another thread similar to this I got some support and at least
  fixed the external microphone without using the alsa-base.conf change
  in custom modified kernel. I will attach it here. Now, hoping to fix
  other issues as well slowly like making headphones unplugged when
  physically removing as well as auto switching like the legacy driver
  one.

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

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

[Kernel-packages] [Bug 1929921] Re: Ubuntu 20.04.2 - OPENSSL_cleanse() fails with segmentation fault in eddsa_test

[Frank Heimes]

** Package changed: linux (Ubuntu) => openssl (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/1929921

Title:
  Ubuntu 20.04.2 - OPENSSL_cleanse() fails with segmentation fault in
  eddsa_test

Status in Ubuntu on IBM z Systems:
  Invalid
Status in openssl package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  ===
  IBM z15 with D41C Bundle S39a and z/VM 7.2.0 guest with crypto cards attached 
  OS: Ubuntu 20.04.2 (focal fossa) with 5.4.0-73-generic and libica 3.6.1 
installed
  Core dump when running the eddsa_test from libica

  Details
  ===
  The available openSSL version is: OpenSSL 1.1.1f  31 Mar 2020
  The ibmca engine was installed, but not defined into the openssl.cnf file,
  openssl engine displayed the default line:
 (dynamic) Dynamic engine loading support

  The segmentation fault was generated by `./eddsa_test'.
  Program terminated with signal SIGSEGV, Segmentation fault in openSSL 
  (gdb) bt
  #0  0x03ff896e50be in OPENSSL_cleanse () from 
/lib/s390x-linux-gnu/libcrypto.so.1.1
  #1  0x03ff898a26fa in ica_ed25519_ctx_del (ctx=0x3fff9b7e010) at 
ica_api.c:1897
  #2  0x02aa28986f14 in ed25519_stress () at eddsa_test.c:441
  #3  0x02aa289831bc in main (argc=0x1, argv=0x3fff9b7eaf8) at 
eddsa_test.c:66

  See https://wiki.ubuntu.com/Debug%20Symbol%20Packages about how to
  define debug repositories

  apt install libica3-dbgsym

  #0  0x03ff896e50be in OPENSSL_cleanse () from 
/lib/s390x-linux-gnu/libcrypto.so.1.1
  (gdb) bt
  # coredumpctl dump 158582 > eddsa.core
 PID: 158582 (eddsa_test)
 UID: 0 (root)
 GID: 0 (root)
  Signal: 11 (SEGV)
   Timestamp: Wed 2021-05-26 19:52:28 CEST (15h ago)
Command Line: ./eddsa_test
  Executable: /root/crypto/libica-3.6.1/test/eddsa_test
   Control Group: /user.slice/user-0.slice/session-9.scope
Unit: session-9.scope
   Slice: user-0.slice
 Session: 9
   Owner UID: 0 (root)
 Boot ID: 6a7a23240f464a0d9f2d3fa3e82be73e
  Machine ID: c933ae494f9a4c6e8d82625c952945d5
Hostname: t3514002.lnxne.boe
 Storage: 
/var/lib/systemd/coredump/core.eddsa_test.0.6a7a23240f464a0d9f2d3fa3e82be73e.158582.1622051548.lz4
 Message: Process 158582 (eddsa_test) of user 0 dumped core.

  Stack trace of thread 158582:
  #0  0x03ff896e50be OPENSSL_cleanse (libcrypto.so.1.1 + 
0x1650be)

  ---uname output---
  Linux system 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 
s390x s390x s390x GNU/Linux
   
  Machine Type = Manufacturer:  IBM Type:   8561 Model:703 T01 
   ---Debugger---
  A debugger was configured, however the system did not enter into the debugger
   
  ---Steps to Reproduce---
  1.) install the github libica 3.6.1 package
  and build the test cases
  2.) cd .../libica-3.6.1
  3.) ./bootstrap.sh; configure --enable-coverage
  4.) make coverage
  Watch the segmentation fault to happen
   
  Userspace tool common name: eddsa_test 
   
  The userspace tool has the following bit modes: 64bit 

  Userspace rpm: libica3

  Userspace tool obtained from project website:  na

  
  The problem could be reproduced with libica 3.6.1, however, it does not show 
up with libica 3.8.0. Looks like the problem was fixed by commit 

  
https://github.com/opencryptoki/libica/commit/b40d0d2ad4a2aac088cf47befbddd8b3b9fca1c5

  After applying this fix on top of 3.6.1, the segfault does not occur
  anymore. It's sufficient to apply the 4 changes in eddsa_test.c.

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

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

[Kernel-packages] [Bug 1925522] Re: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq

[Alberto Milone]

** Tags removed: verification-needed verification-needed-bionic 
verification-needed-focal verification-needed-groovy verification-needed-hirsute
** Tags added: verification-done verification-done-bionic 
verification-done-focal verification-done-groovy verification-done-hirsute

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

Title:
  Introduce the 465 driver series, fabric-manager, and libnvidia-nscq

Status in fabric-manager-450 package in Ubuntu:
  Fix Released
Status in fabric-manager-460 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-460 package in Ubuntu:
  Fix Released
Status in linux-restricted-modules package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  In Progress
Status in fabric-manager-450 source package in Bionic:
  Fix Committed
Status in fabric-manager-460 source package in Bionic:
  Fix Committed
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Committed
Status in libnvidia-nscq-460 source package in Bionic:
  Fix Committed
Status in linux-restricted-modules source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-465 source package in Bionic:
  Fix Committed
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in fabric-manager-450 source package in Focal:
  Fix Committed
Status in fabric-manager-460 source package in Focal:
  Fix Committed
Status in libnvidia-nscq-450 source package in Focal:
  Fix Committed
Status in libnvidia-nscq-460 source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-465 source package in Focal:
  Fix Committed
Status in nvidia-settings source package in Focal:
  Fix Committed
Status in fabric-manager-450 source package in Groovy:
  Fix Committed
Status in fabric-manager-460 source package in Groovy:
  Fix Committed
Status in libnvidia-nscq-450 source package in Groovy:
  Fix Committed
Status in libnvidia-nscq-460 source package in Groovy:
  Fix Committed
Status in linux-restricted-modules source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-465 source package in Groovy:
  Fix Committed
Status in nvidia-settings source package in Groovy:
  Fix Committed
Status in fabric-manager-450 source package in Hirsute:
  Fix Committed
Status in fabric-manager-460 source package in Hirsute:
  Fix Committed
Status in libnvidia-nscq-450 source package in Hirsute:
  Fix Committed
Status in libnvidia-nscq-460 source package in Hirsute:
  Fix Committed
Status in linux-restricted-modules source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-465 source package in Hirsute:
  Fix Committed
Status in nvidia-settings source package in Hirsute:
  Fix Committed

Bug description:
  Introduce the new NVIDIA 465 driver series, fabric-manager and
  libnvidia-nscq. Also migrate the UDA 450 series to the 460 series.

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

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

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

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

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

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

  [Discussion]

  [Changelog]

  == 450-server ==

    * New upstream release (LP: #1925522).
  - Fixed an issue with the NSCQ 

[Kernel-packages] [Bug 1929825] Re: [Ubuntu 21.04] OSA Device doesn't get enabled if a vlan is specified on the kernel cmdline for the installer

[Frank Heimes]

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

This is an issue that got already identified and reported (late in the cycle) 
during 21.04 testing and is described at LP#1924794 in more detail.
It was unfortunately too late to get it fixed in time for 21.04 GA,
but you will find a fixed initramfs file in LP#1924794 comment #10 that needs 
to be used as a replacement for the initfamfs file that is shipped by the ISO 
in /boot.
The fix is already included in Impish, too.

Hence I'm marking this LP bug as a duplicate of LP#1924794.

** Changed in: linux (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned)

** Changed in: ubuntu-z-systems
   Status: New => Fix Released

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Fix Released

** This bug has been marked a duplicate of bug 1924794
   Getting error "ipconfig: no devices to configure" while trying to 
autoinstall in a VLAN env on s390x

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

Title:
  [Ubuntu 21.04] OSA Device doesn't get enabled if a vlan is specified
  on the kernel cmdline for the installer

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  The OSA Device doesn't get enabled if a vlan is specified on the
  kernel cmdline for the installer.

  with the cmdline
  `ip=10.1.8.74::10.1.10.1:255.255.252.0::enc800.300:none nameserver=10.1.9.101 
vlan=enc800.300:enc800 
url=http://10.1.9.101:1002/iso/ubuntu-21.04-live-server-s390x.iso quiet ---`

  the boot fails with this message and drops to a shell:
  ```
  BusyBox v1.30.1 (Ubuntu 1:1.30.1-6ubuntu2) built-in shell (ash)
  Enter 'help' for a list of built-in commands.
   
  (initramfs) [6n
  ip: SIOCGIFFLAGS: No such device
  ip: can't find device 'enc800'
  ipconfig: enc800.300: SIOCGIFINDEX: No such device
  ipconfig: no devices to configure
  ipconfig: enc800.300: SIOCGIFINDEX: No such device
  ipconfig: no devices to configure
  ipconfig: enc800.300: SIOCGIFINDEX: No such device
  ipconfig: no devices to configure
  ipconfig: enc800.300: SIOCGIFINDEX: No such device
  ipconfig: no devices to configure
  ipconfig: enc800.300: SIOCGIFINDEX: No such device
  ipconfig: no devices to configure
  ipconfig: enc800.300: SIOCGIFINDEX: No such device
  ipconfig: no devices to configure
  ipconfig: enc800.300: SIOCGIFINDEX: No such device
  ipconfig: no devices to configure
  ipconfig: enc800.300: SIOCGIFINDEX: No such device
  ipconfig: no devices to configure
  ipconfig: enc800.300: SIOCGIFINDEX: No such device
  ipconfig: no devices to configure
  ipconfig: enc800.300: SIOCGIFINDEX: No such device
  ipconfig: no devices to configure
  no search or nameservers found in /run/net-enc800.300.conf /run/net-*.conf 
/run/
  net6-*.conf
  Connecting to 10.1.9.101:1002 (10.1.9.101:1002)
  wget: can't connect to remote host (10.1.9.101): Network is unreachable
  Unable to find a live file system on the network
  ```

  It the zdev 800 doesn't get enabled.
  ``` 
  ip addr
  1: lo:  mtu 65536 qdisc noop qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  (initramfs) [6n
  lszdev | grep 0.0.0800
  qeth 0.0.0800:0.0.0801:0.0.0802  no  no
  ```

  But I can enable it manually:
  ```
  chzdev -e 800
  QETH device 0.0.0800:0.0.0801:0.0.0802 configured
  Note: The initial RAM-disk must be updated for these changes to take effect:
 - QETH device 0.0.0800:0.0.0801:0.0.0802
  A manual update of the initial RAM-disk is required.
  (initramfs) [6n
  ip addr
  1: lo:  mtu 65536 qdisc noop qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: enc800:  mtu 1500 qdisc noop qlen 1000
  link/ether f2:ae:7d:de:88:a0 brd ff:ff:ff:ff:ff:ff
  ```

  The same cmdline (adjusted for the iso url) works on 20.04.
  Between 20.04 and 21.04 the line 318 `echo "${VLAN}" | grep -q "${dev}" && 
continue` was added to /scripts/functions in the initrd.ubuntu. If I remove 
this line and repack the ramdisk the network boot works as expected like on 
ubuntu 20.04

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

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

[Kernel-packages] [Bug 1925522] Re: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq

[Lukas Waymann]

We've tested driver versions 460.80 and 465.27 on Bionic, Focal, Groovy,
and Hirsute. The full results are available at
 and
,
respectively.

We found one potential issue.  During some boots, the nvidia-settings
GUI only has the "PRIME Profiles" tab with all other options missing.
This only occurred on Hirsute, primarily on one out of three tested
laptops, and primarily with the 460.80 driver.  I could also reproduce
the same issue with the previous driver version (460.73.01).  All other
tests were successful.

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

Title:
  Introduce the 465 driver series, fabric-manager, and libnvidia-nscq

Status in fabric-manager-450 package in Ubuntu:
  Fix Released
Status in fabric-manager-460 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-460 package in Ubuntu:
  Fix Released
Status in linux-restricted-modules package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  In Progress
Status in fabric-manager-450 source package in Bionic:
  Fix Committed
Status in fabric-manager-460 source package in Bionic:
  Fix Committed
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Committed
Status in libnvidia-nscq-460 source package in Bionic:
  Fix Committed
Status in linux-restricted-modules source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-465 source package in Bionic:
  Fix Committed
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in fabric-manager-450 source package in Focal:
  Fix Committed
Status in fabric-manager-460 source package in Focal:
  Fix Committed
Status in libnvidia-nscq-450 source package in Focal:
  Fix Committed
Status in libnvidia-nscq-460 source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-465 source package in Focal:
  Fix Committed
Status in nvidia-settings source package in Focal:
  Fix Committed
Status in fabric-manager-450 source package in Groovy:
  Fix Committed
Status in fabric-manager-460 source package in Groovy:
  Fix Committed
Status in libnvidia-nscq-450 source package in Groovy:
  Fix Committed
Status in libnvidia-nscq-460 source package in Groovy:
  Fix Committed
Status in linux-restricted-modules source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-465 source package in Groovy:
  Fix Committed
Status in nvidia-settings source package in Groovy:
  Fix Committed
Status in fabric-manager-450 source package in Hirsute:
  Fix Committed
Status in fabric-manager-460 source package in Hirsute:
  Fix Committed
Status in libnvidia-nscq-450 source package in Hirsute:
  Fix Committed
Status in libnvidia-nscq-460 source package in Hirsute:
  Fix Committed
Status in linux-restricted-modules source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-465 source package in Hirsute:
  Fix Committed
Status in nvidia-settings source package in Hirsute:
  Fix Committed

Bug description:
  Introduce the new NVIDIA 465 driver series, fabric-manager and
  libnvidia-nscq. Also migrate the UDA 450 series to the 460 series.

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

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

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

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

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to 

[Kernel-packages] [Bug 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)

[Frank Heimes]

I forgot to ask you to please provide the the journal logs, too.

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

Title:
  [Ubuntu 20.4.2]  vLan not getting static IP assigned (on s390x)

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Doing vLAN configuration one of the vLANs is not getting static IP assigned 
when the rest are workin without problems
   
  Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com 
   
  ---uname output---
  Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 
17:29:32 UTC 2021 s390x s390x s390x GNU/Linux
   
  Machine Type = z15 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1)Configure the netplan file as follow:
  root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml

  # This is the network config written by 'subiquity'

  network:

ethernets:

  encdb0:

addresses:

- 11.111.114.213/22

macaddress: 02:76:54:00:00:03

  encdc0:

addresses:

- 11.111.112.213/22

macaddress: 02:76:54:00:00:04

  enP50s3832 :

addresses:

- 11.111.112.214/22

  enP53p0s0:

addresses:

- 11.111.112.215/22

vlans:

  encdb0.160:

id: 160

link: encdb0

mtu: 9000

addresses:

- 192.168.160.53/24

  encdc0.150:

id: 150

link: encdc0

mtu: 9000

addresses:

- 192.168.150.53/24

  enP50s3832.170:

id: 170

link: enP50s3832

mtu: 9000

addresses:

- 192.168.170.53/24

  enP53p0s0.171:

id: 171

link: enP53p0s0

mtu: 9000

addresses:

- 192.168.171.53/24

version: 2

  2)run net plan apply:
  root@ilabg13:~# netplan --debug apply

  ** (generate:59965): DEBUG: 14:55:15.046: Processing input file
  /etc/netplan/00-installer-config.yaml..

  ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass

  ** (generate:59965): DEBUG: 14:55:15.046: Processing input file
  /etc/netplan/01-iscsi-config.yaml..

  ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass

  ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass
  them through a final round of validation

  ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting
  default backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting
  default backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.047: Generating output files..

  ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition
  ence0f is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition
  ence0f is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition
  encdb0 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition
  encdb0 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition
  encdc0 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition
  encdc0 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition
  enP50s3832 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition
  enP50s3832 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition
  enP53p0s0 is not for us (backend 1)

  ** 

[Kernel-packages] [Bug 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)

[Frank Heimes]

Reading through the info provided I found it surprising that the IP
address could not be attached to only one of the vlan devices
(enP53p0s0.171@enP53p0s0).

Can you share how the devices were activated and how they are based
upon? (OSA/qeth, hipersockets/qeth or RoCE/SMC)

I assume that all interfaces that start with "enP*" are based on
RoCE/SMC devices, right?

If this is the case I find the naming very strange:
This name seems to be fine: enP53p0s0
But this looks odd to me: enP50s3832 - especially the ending: 3832

On my test system (that unfortunately only has older X-3 Pro based RoCE 
adapters) the naming is like this (and with that pretty structured and 
straight-forward):
   enP1p0s0
   enP1p0s0d1  
   enP2p0s0 
   enP2p0s0d1
So is enP50s3832 really a RoCE interface?

And are there any udev rules that were written or modified to modify the
name of this adapter? Or is it otherwise traceable where this name is
coming from (even knowing that this is the interface that got the ip
address assigned).

Could you also please share the output of 'sudo lshw'?

** Changed in: ubuntu-z-systems
   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/1929657

Title:
  [Ubuntu 20.4.2]  vLan not getting static IP assigned (on s390x)

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Doing vLAN configuration one of the vLANs is not getting static IP assigned 
when the rest are workin without problems
   
  Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com 
   
  ---uname output---
  Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 
17:29:32 UTC 2021 s390x s390x s390x GNU/Linux
   
  Machine Type = z15 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1)Configure the netplan file as follow:
  root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml

  # This is the network config written by 'subiquity'

  network:

ethernets:

  encdb0:

addresses:

- 11.111.114.213/22

macaddress: 02:76:54:00:00:03

  encdc0:

addresses:

- 11.111.112.213/22

macaddress: 02:76:54:00:00:04

  enP50s3832 :

addresses:

- 11.111.112.214/22

  enP53p0s0:

addresses:

- 11.111.112.215/22

vlans:

  encdb0.160:

id: 160

link: encdb0

mtu: 9000

addresses:

- 192.168.160.53/24

  encdc0.150:

id: 150

link: encdc0

mtu: 9000

addresses:

- 192.168.150.53/24

  enP50s3832.170:

id: 170

link: enP50s3832

mtu: 9000

addresses:

- 192.168.170.53/24

  enP53p0s0.171:

id: 171

link: enP53p0s0

mtu: 9000

addresses:

- 192.168.171.53/24

version: 2

  2)run net plan apply:
  root@ilabg13:~# netplan --debug apply

  ** (generate:59965): DEBUG: 14:55:15.046: Processing input file
  /etc/netplan/00-installer-config.yaml..

  ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass

  ** (generate:59965): DEBUG: 14:55:15.046: Processing input file
  /etc/netplan/01-iscsi-config.yaml..

  ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass

  ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass
  them through a final round of validation

  ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting
  default backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting
  default backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default
  backend to 1

  ** (generate:59965): DEBUG: 

[Kernel-packages] [Bug 1912371] Re: [MIR] flashrom + libftdi

[Alex Murray]

** Package changed: libftdi (Ubuntu) => libftdi1 (Ubuntu)

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

Title:
  [MIR] flashrom + libftdi

Status in flashrom package in Ubuntu:
  New
Status in libftdi1 package in Ubuntu:
  New

Bug description:
  [Summary]
  Further review will be needed. The Package does not have a test suite that 
runs as autopkgtest.

  [Availability]
  Currently in universe.

  [Duplication]
  There is no other package in main providing the same functionality.

  [Rationale]
  fwupd depends on libflashrom1 for its flashrom plugin, something that's 
required to update Coreboot firmware.

  [Security]
  No CVE's, but due to the nature of the package security should review.

  [Quality Assurance]
  Package builds and runs easily

  [Dependencies]
  N/A

  [Standards Compliance]
  Complies with FHS, though the organization of files in the source package 
could be organized better.

  [Common blockers]
  flashrom does NOT have a test suite that runs at build time.
  flashrom does NOT have a test suite that runs as autopkgtest.

  [Maintenance]
  Actively maintained - https://github.com/flashrom/flashrom
  Packaging - https://salsa.debian.org/myczko-guest/flashrom.git

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

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

[Kernel-packages] [Bug 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)

[Frank Heimes]

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned)

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

Title:
  [Ubuntu 20.4.2]  vLan not getting static IP assigned (on s390x)

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Doing vLAN configuration one of the vLANs is not getting static IP assigned 
when the rest are workin without problems
   
  Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com 
   
  ---uname output---
  Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 
17:29:32 UTC 2021 s390x s390x s390x GNU/Linux
   
  Machine Type = z15 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1)Configure the netplan file as follow:
  root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml

  # This is the network config written by 'subiquity'

  network:

ethernets:

  encdb0:

addresses:

- 11.111.114.213/22

macaddress: 02:76:54:00:00:03

  encdc0:

addresses:

- 11.111.112.213/22

macaddress: 02:76:54:00:00:04

  enP50s3832 :

addresses:

- 11.111.112.214/22

  enP53p0s0:

addresses:

- 11.111.112.215/22

vlans:

  encdb0.160:

id: 160

link: encdb0

mtu: 9000

addresses:

- 192.168.160.53/24

  encdc0.150:

id: 150

link: encdc0

mtu: 9000

addresses:

- 192.168.150.53/24

  enP50s3832.170:

id: 170

link: enP50s3832

mtu: 9000

addresses:

- 192.168.170.53/24

  enP53p0s0.171:

id: 171

link: enP53p0s0

mtu: 9000

addresses:

- 192.168.171.53/24

version: 2

  2)run net plan apply:
  root@ilabg13:~# netplan --debug apply

  ** (generate:59965): DEBUG: 14:55:15.046: Processing input file
  /etc/netplan/00-installer-config.yaml..

  ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass

  ** (generate:59965): DEBUG: 14:55:15.046: Processing input file
  /etc/netplan/01-iscsi-config.yaml..

  ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass

  ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass
  them through a final round of validation

  ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting
  default backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting
  default backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.047: Generating output files..

  ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition
  ence0f is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition
  ence0f is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition
  encdb0 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition
  encdb0 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition
  encdc0 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition
  encdc0 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition
  enP50s3832 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition
  enP50s3832 is not for us (backend 1)

  ** 

[Kernel-packages] [Bug 1920777] Re: [SRU][G][HWE-5.8] Fix compatibility issue on some external monitors

[Launchpad Bug Tracker]

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

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

Title:
  [SRU][G][HWE-5.8] Fix compatibility issue on some external monitors

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-5.8 package in Ubuntu:
  Confirmed
Status in linux-hwe-5.8 source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Confirmed

Bug description:
  [Impact]
  Some external monitors got black screen via HDMI on laptops with Intel GPU.

  [Fix]
  Reading more of the port caps and dealing with various clock/bpc limitations.
  Patchset:
  https://patchwork.freedesktop.org/series/72928/

  [Test Case]
  Verified on the target platform and other 2 laptops include workstation,
  Tested on LG/ThinkVision 4k monitors and Dell 1080p monitor, include dock 
station.
  All good.

  [Where problems could occur]
  Intel GPU may lose or mess the output.

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

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

[Kernel-packages] [Bug 1920777] Re: [SRU][G][HWE-5.8] Fix compatibility issue on some external monitors

[Launchpad Bug Tracker]

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

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

Title:
  [SRU][G][HWE-5.8] Fix compatibility issue on some external monitors

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-5.8 package in Ubuntu:
  Confirmed
Status in linux-hwe-5.8 source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Confirmed

Bug description:
  [Impact]
  Some external monitors got black screen via HDMI on laptops with Intel GPU.

  [Fix]
  Reading more of the port caps and dealing with various clock/bpc limitations.
  Patchset:
  https://patchwork.freedesktop.org/series/72928/

  [Test Case]
  Verified on the target platform and other 2 laptops include workstation,
  Tested on LG/ThinkVision 4k monitors and Dell 1080p monitor, include dock 
station.
  All good.

  [Where problems could occur]
  Intel GPU may lose or mess the output.

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

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

[Kernel-packages] [Bug 1920777] Re: [SRU][G][HWE-5.8] Fix compatibility issue on some external monitors

[Launchpad Bug Tracker]

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

** Changed in: linux-hwe-5.8 (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/1920777

Title:
  [SRU][G][HWE-5.8] Fix compatibility issue on some external monitors

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-5.8 package in Ubuntu:
  Confirmed
Status in linux-hwe-5.8 source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Confirmed

Bug description:
  [Impact]
  Some external monitors got black screen via HDMI on laptops with Intel GPU.

  [Fix]
  Reading more of the port caps and dealing with various clock/bpc limitations.
  Patchset:
  https://patchwork.freedesktop.org/series/72928/

  [Test Case]
  Verified on the target platform and other 2 laptops include workstation,
  Tested on LG/ThinkVision 4k monitors and Dell 1080p monitor, include dock 
station.
  All good.

  [Where problems could occur]
  Intel GPU may lose or mess the output.

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

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

[Kernel-packages] [Bug 1929923] Re: [UBUNTU 20.04] LPAR becomes unresponsive after the Kernel panic - rq_qos_wake_function

[Frank Heimes]

Well, as already mentioned in the two comments before more details are
needed:

If a system is not on the latest kernel level, but shows kernel issues, it is 
first of all needed to update the system to the latest kernel level and try to 
recreate the issue there.
So I agree with Pedro that this needs to be verified on (currently) latest 
5.4.0.73, since especially 5.4.0.73 includes hundreds of upstream stable 
patches because it includes the range from v5.4.102 to .106.

Testing on 5.4.0-74 (currently in proposed) would be the next crucial
step, since it incl. even more upstream stable patches ranging from
v5.4.107 to .114 - again hundreds of patches.

This is needed to be sure that we don't hunt a bug that may already have
been fixed.

If the issue is re-produceable on these kernel levels, wee need more details on 
the environment:
- which IBM Z or LinuxONE system is in use
- which storage backend is attached and used?
- is zFCP/SCSI used or DASDs?
- and what is the dump device and how did it got configured?
(again detailed steps to re-produce, like Andrew asked for)

** Changed in: ubuntu-z-systems
   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/1929923

Title:
  [UBUNTU 20.04] LPAR becomes unresponsive after the Kernel panic -
  rq_qos_wake_function

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

Bug description:
  ---Problem Description---
  kernel panic rq_qos_wake_function
   
  ---uname output---
  Linux version 5.4.0-71-generic
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  Stack trace output:
   May 15 20:21:04 data1 kernel: Call Trace:
  May 15 20:21:04 data1 kernel: ([<00234091e670>] 0x234091e670)
  May 15 20:21:04 data1 kernel:  [<003e10047e3a>] 
rq_qos_wake_function+0x8a/0xa0 
  May 15 20:21:04 data1 kernel:  [<003e0fbec482>] 
__wake_up_common+0xa2/0x1b0 
  May 15 20:21:04 data1 kernel:  [<003e0fbec984>] 
__wake_up_common_lock+0x94/0xe0 
  May 15 20:21:04 data1 kernel:  [<003e0fbec9fa>] __wake_up+0x2a/0x40 
  May 15 20:21:04 data1 kernel:  [<003e1005ee70>] wbt_done+0x90/0xe0 
  May 15 20:21:04 data1 kernel:  [<003e10047f42>] __rq_qos_done+0x42/0x60 
  May 15 20:21:04 data1 kernel:  [<003e10033cb0>] 
blk_mq_free_request+0xe0/0x140 
  May 15 20:21:04 data1 kernel:  [<003e101d46f0>] 
dm_softirq_done+0x140/0x230 
  May 15 20:21:04 data1 kernel:  [<003e100326c0>] 
blk_done_softirq+0xc0/0xe0 
  May 15 20:21:04 data1 kernel:  [<003e103fc084>] __do_softirq+0x104/0x360 
  May 15 20:21:04 data1 kernel:  [<003e0fb9da1e>] irq_exit+0x9e/0xc0 
  May 15 20:21:04 data1 kernel:  [<003e0fb28ae8>] do_IRQ+0x78/0xb0 
  May 15 20:21:04 data1 kernel:  [<003e103fb588>] 
ext_int_handler+0x130/0x134 
  May 15 20:21:04 data1 kernel:  [<003e101d4416>] dm_mq_queue_rq+0x36/0x1d0 
  May 15 20:21:04 data1 kernel: Last Breaking-Event-Address:
  May 15 20:21:04 data1 kernel:  [<003e0fbce75e>] wake_up_process+0xe/0x20
  May 15 20:21:04 data1 kernel: Kernel panic - not syncing: Fatal exception in 
interrupt
   
  Oops output:
   no
   
  System Dump Info:
The system was configured to capture a dump, however a dump was not 
produced.

  -Attach sysctl -a output output to the bug.

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

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

[Kernel-packages] [Bug 1909499] Re: iwlwifi 0000:03:00.0: No beacon heard and the time event is over already...

[Lyubomir]

Since then i've clean reinstalled and i think i don't see this error in my 
logs. Also don't experience network disruptions.
My curret kernel is 5.11.0-17-lowlatency
Don't know what kernel @uberschizo uses.

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

Title:
  iwlwifi :03:00.0: No beacon heard and the time event is over
  already...

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I see this error frequently inside logs: iwlwifi :03:00.0: No
  beacon heard and the time event is over already...

  Also, the internet doesn't seem stable, from time to time it
  disconnects and reconnects on its own, and other times it disconnects
  and wants me to enter the key again to connect. However, if i hit the
  X button to close the password modal and try to connect again from the
  networks list, it does connect without the need to enter the password.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.6
  ProcVersionSignature: Ubuntu 5.4.0-58.64-lowlatency 5.4.73
  Uname: Linux 5.4.0-58-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lyubo 14448 F pulseaudio
   /dev/snd/pcmC0D0p:   lyubo 14448 F...m pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Dec 28 21:50:51 2020
  Dependencies:
   
  InstallationDate: Installed on 2020-12-27 (0 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 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 275d:0ba6  USB OPTICAL MOUSE 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A515-51G
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-58-lowlatency 
root=/dev/mapper/vgkubuntu-root ro quiet splash lockdown=confidentiality 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-lowlatency N/A
   linux-backports-modules-5.4.0-58-lowlatency  N/A
   linux-firmware   1.187.6
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/03/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.02
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Charmander_KL
  dmi.board.vendor: KBL
  dmi.board.version: V2.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-51G
  dmi.product.sku: 
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues

[Bijay Shah]

Also alsa info without temp fix and headset/earphones plugged in and
input/output manually switched to if it helps.

** Attachment added: 
"alsa-info-with-coef-without-temp-fix-audio-jack-plugged.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+attachment/5501270/+files/alsa-info-with-coef-without-temp-fix-audio-jack-plugged.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/1930188

Title:
  Acer Aspire 5 sound driver issues

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  There seems to be lots of issues in sound driver for Acer Aspire
  A515-56-57XR with ALC255. I will list all of them below and what I
  have tried so far.

  1. Headphones appears always plugged in even if they are physically not
  2. When actually plugging in headset/earphones it does not auto switch from 
speakers/internal mic to headphones/headset microphone automatically and vice 
versa, have to manually switch everytime.
  3. External headset/earphones microphone won't work at all

  After, logs of trial and error I have found a temporary fix. This
  seems to use legacy intel drivers which solves all 3 issues mentioned
  above but the internal/dmic mic is completely gone (which seems
  intentional when using this). Both depreciated dmic_detect and
  dsp_driver works, I have been using dsp_driver for now as I need
  external microphone at any cost.

  End of /etc/modprobe.d/alsa-base.conf
  # Headset mic fix
  options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1
  options snd-hda-intel model=alc255-acer

  In another thread similar to this I got some support and at least
  fixed the external microphone without using the alsa-base.conf change
  in custom modified kernel. I will attach it here. Now, hoping to fix
  other issues as well slowly like making headphones unplugged when
  physically removing as well as auto switching like the legacy driver
  one.

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

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

[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues

[Bijay Shah]

Here is alsa info without temp fix applied and nothing plugged into
audio jack.

** Attachment added: 
"alsa-info-with-coef-without-temp-fix-audio-jack-unplugged.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+attachment/5501269/+files/alsa-info-with-coef-without-temp-fix-audio-jack-unplugged.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/1930188

Title:
  Acer Aspire 5 sound driver issues

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  There seems to be lots of issues in sound driver for Acer Aspire
  A515-56-57XR with ALC255. I will list all of them below and what I
  have tried so far.

  1. Headphones appears always plugged in even if they are physically not
  2. When actually plugging in headset/earphones it does not auto switch from 
speakers/internal mic to headphones/headset microphone automatically and vice 
versa, have to manually switch everytime.
  3. External headset/earphones microphone won't work at all

  After, logs of trial and error I have found a temporary fix. This
  seems to use legacy intel drivers which solves all 3 issues mentioned
  above but the internal/dmic mic is completely gone (which seems
  intentional when using this). Both depreciated dmic_detect and
  dsp_driver works, I have been using dsp_driver for now as I need
  external microphone at any cost.

  End of /etc/modprobe.d/alsa-base.conf
  # Headset mic fix
  options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1
  options snd-hda-intel model=alc255-acer

  In another thread similar to this I got some support and at least
  fixed the external microphone without using the alsa-base.conf change
  in custom modified kernel. I will attach it here. Now, hoping to fix
  other issues as well slowly like making headphones unplugged when
  physically removing as well as auto switching like the legacy driver
  one.

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

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

[Kernel-packages] [Bug 1912371] security audit

[Alex Murray]

I reviewed flashrom 1.2-5ubuntu1 as per the debdiff attached to this bug as
applied to 1.2-5 in impish.  This shouldn't be considered a full audit but
rather a quick gauge of maintainability.

flashrom is a tool used for reading and flashing BIOS/ROM/firmware onto the
various flash chips within a machine - this can include the UEFI BIOS or
optionROMs plus other devices like NICs etc.

- No CVE History
- Relevant Build-Depends:
  - libpci-dev, libusb-1.0-0-dev, libftdi1-dev
- No pre/post inst/rm scripts
- No init scripts
- No systemd units
- No dbus services
- No setuid binaries
- 1 binary in PATH
  - /usr/sbin/flashrom
- No sudo fragments
- No polkit files
- 1 udev rules
  - Grants read/write access to the various specific USB devices for users
in the plugdev group
- Includes unit tests run during build and autopkgtests to do more
  system-level testing via dummy devices
- No cron jobs
- Build logs:
  - No significant warnings during the build other than the following
lintian issues:
E: libflashrom1: symbols-file-contains-current-version-with-debian-revision on 
symbol LIBFLASHROM_1.0@LIBFLASHROM_1.0 and 23 others
W: flashrom: appstream-metadata-missing-modalias-provide 
lib/udev/rules.d/60-flashrom.rules
W: flashrom source: illegal-runtime-test-name emulated_programmer.sh in line 1

- Processes spawned
  - Uses popen() to call dmidecode() to read various hard-coded
identifiers - as these are hard-coded there is no chance for these to
be used for command injection so whilst this is a bit ugly it is safe.
- Memory management
  - Being written in C there is a lot of dynamic memory management via
malloc, realloc and free etc - but in general these seem quite
defensive, with return values being checked and no instances that I
could see with obvious chance for integer overflow when calculating
sizes to allocate etc.
- File IO
  - Opens and reads from a number of hard-coded paths or from paths as
specified via command-line arguments
  - Can dump out to a user-specified path as well
- Logging
  - Lots of printf() style logging but again this looks pretty defensive
- No environment variable usage
- Uses various privileged ioctl() calls so likely would need to be run as
  root in these cases but again I don't see any obvious chance to abuse
  this
- No use of cryptography / random number sources
- No use of temp files
- Use of networking
  - Supports connecting to a remote serial programmer over TCP/IP - this is
treated as trusted like a real device
- No use of WebKit
- No use of PolicyKit

- No significant cppcheck/coverity results

flashrom appears to be reasonably defensively written and does not have a
history of security issues, whilst the upstream project seems relatively
healthy so should likely be responsive and supporting for any potential
future security issues.

Security team ACK for promoting flashrom to main assuming this includes the
changes from comment:14 above - can the lintian issues highlighted earlier
please be investigated?


** Tags added: security-review-done

** Changed in: flashrom (Ubuntu)
 Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)

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

Title:
  [MIR] flashrom + libftdi

Status in flashrom package in Ubuntu:
  New
Status in libftdi package in Ubuntu:
  New

Bug description:
  [Summary]
  Further review will be needed. The Package does not have a test suite that 
runs as autopkgtest.

  [Availability]
  Currently in universe.

  [Duplication]
  There is no other package in main providing the same functionality.

  [Rationale]
  fwupd depends on libflashrom1 for its flashrom plugin, something that's 
required to update Coreboot firmware.

  [Security]
  No CVE's, but due to the nature of the package security should review.

  [Quality Assurance]
  Package builds and runs easily

  [Dependencies]
  N/A

  [Standards Compliance]
  Complies with FHS, though the organization of files in the source package 
could be organized better.

  [Common blockers]
  flashrom does NOT have a test suite that runs at build time.
  flashrom does NOT have a test suite that runs as autopkgtest.

  [Maintenance]
  Actively maintained - https://github.com/flashrom/flashrom
  Packaging - https://salsa.debian.org/myczko-guest/flashrom.git

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

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

[Kernel-packages] [Bug 1929870] Re: AMD desktop often fails to resume from deep suspend

[Kai-Heng Feng]

Please attach `journalctl -b -1 -k` after the suspend failed.

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

Title:
  AMD desktop often fails to resume from deep suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Machine setup:

  Desktop PC
  Ubuntu 21.04
  Linux version 5.11.0-17-generic
  AMD Ryzen 3900X
  Asus X590 PRIME PRO motherboard
  NVIDIA P400 GPU

  Approximately one in every 4 attempts to resume from a deep suspend
  fails. When the issue occurs the fans spin up but the monitor displays
  no output and input devices do not function, the system appears frozen
  and must be restarted using power or reset buttons.

  I have tried using different dNVIDIA isplay drivers (proprietary as
  well as open source) as well as trying an AMD Radeon HD 6450 GPU
  instead of the NVIDIA GPU.

  I have tried the following kernel parameters: processor.max_cstate=1
  rcu_nocbs=0-23

  I have updated the BIOS several times.

  I had similar problems with Ubuntu 20.10.

  I have enabled some additional kernel logging with initcall_debug.

  Fairly consistently the last message printed in the kernel log is from
  the ethernet driver:

  May 27 09:19:43 jacob-tm kernel: [  230.878348] OOM killer enabled.
  May 27 09:19:43 jacob-tm kernel: [  230.878349] Restarting tasks ... 
  May 27 09:19:43 jacob-tm kernel: [  230.879023] usb 5-2.3: USB disconnect, 
device number 4
  May 27 09:19:43 jacob-tm kernel: [  230.879026] usb 5-2.3.1: USB disconnect, 
device number 5
  May 27 09:19:43 jacob-tm kernel: [  230.879285] done.
  May 27 09:19:43 jacob-tm kernel: [  230.879318] PM: suspend exit
  May 27 09:19:43 jacob-tm kernel: [  230.880916] rfkill: input handler enabled
  May 27 09:19:43 jacob-tm kernel: [  230.955727] kauditd_printk_skb: 1 
callbacks suppressed
  May 27 09:19:43 jacob-tm kernel: [  230.955731] audit: type=1400 
audit(1622132383.424:64): apparmor="DENIED" operation="capab
  le" profile="/usr/sbin/cupsd" pid=4418 comm="cupsd" capability=12  
capname="net_admin"
  May 27 09:19:43 jacob-tm kernel: [  230.966192] audit: type=1400 
audit(1622132383.432:65): apparmor="DENIED" operation="capab
  le" profile="/usr/sbin/cups-browsed" pid=4429 comm="cups-browsed" 
capability=23  capname="sys_nice"
  May 27 09:19:43 jacob-tm kernel: [  231.120385] rfkill: input handler disabled
  May 27 09:19:43 jacob-tm kernel: [  231.225924] usb 5-2.3.2: USB disconnect, 
device number 6
  May 27 09:19:43 jacob-tm kernel: [  231.481893] usb 5-2.3.5: USB disconnect, 
device number 7
  May 27 09:19:47 jacob-tm kernel: [  235.009576] igb :05:00.0 enp5s0: igb: 
enp5s0 NIC Link is Up 1000 Mbps Full Duplex, Fl
  ow Control: RX/TX
  May 27 09:19:47 jacob-tm kernel: [  235.009913] IPv6: 
ADDRCONF(NETDEV_CHANGE): enp5s0: link becomes ready

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jacob  2024 F pulseaudio
   /dev/snd/controlC0:  jacob  2024 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 27 14:12:33 2021
  InstallationDate: Installed on 2020-10-28 (211 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=f721d5df-ceec-434a-919a-0680ee380996 ro quiet splash initcall_debug 
processor.max_cstate=1 rcu_nocbs=0-23 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
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-05-14 (13 days ago)
  dmi.bios.date: 05/08/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3604
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X570-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 

[Kernel-packages] [Bug 1929923] Re: [UBUNTU 20.04] LPAR becomes unresponsive after the Kernel panic - rq_qos_wake_function

[Frank Heimes]

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

Title:
  [UBUNTU 20.04] LPAR becomes unresponsive after the Kernel panic -
  rq_qos_wake_function

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

Bug description:
  ---Problem Description---
  kernel panic rq_qos_wake_function
   
  ---uname output---
  Linux version 5.4.0-71-generic
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  Stack trace output:
   May 15 20:21:04 data1 kernel: Call Trace:
  May 15 20:21:04 data1 kernel: ([<00234091e670>] 0x234091e670)
  May 15 20:21:04 data1 kernel:  [<003e10047e3a>] 
rq_qos_wake_function+0x8a/0xa0 
  May 15 20:21:04 data1 kernel:  [<003e0fbec482>] 
__wake_up_common+0xa2/0x1b0 
  May 15 20:21:04 data1 kernel:  [<003e0fbec984>] 
__wake_up_common_lock+0x94/0xe0 
  May 15 20:21:04 data1 kernel:  [<003e0fbec9fa>] __wake_up+0x2a/0x40 
  May 15 20:21:04 data1 kernel:  [<003e1005ee70>] wbt_done+0x90/0xe0 
  May 15 20:21:04 data1 kernel:  [<003e10047f42>] __rq_qos_done+0x42/0x60 
  May 15 20:21:04 data1 kernel:  [<003e10033cb0>] 
blk_mq_free_request+0xe0/0x140 
  May 15 20:21:04 data1 kernel:  [<003e101d46f0>] 
dm_softirq_done+0x140/0x230 
  May 15 20:21:04 data1 kernel:  [<003e100326c0>] 
blk_done_softirq+0xc0/0xe0 
  May 15 20:21:04 data1 kernel:  [<003e103fc084>] __do_softirq+0x104/0x360 
  May 15 20:21:04 data1 kernel:  [<003e0fb9da1e>] irq_exit+0x9e/0xc0 
  May 15 20:21:04 data1 kernel:  [<003e0fb28ae8>] do_IRQ+0x78/0xb0 
  May 15 20:21:04 data1 kernel:  [<003e103fb588>] 
ext_int_handler+0x130/0x134 
  May 15 20:21:04 data1 kernel:  [<003e101d4416>] dm_mq_queue_rq+0x36/0x1d0 
  May 15 20:21:04 data1 kernel: Last Breaking-Event-Address:
  May 15 20:21:04 data1 kernel:  [<003e0fbce75e>] wake_up_process+0xe/0x20
  May 15 20:21:04 data1 kernel: Kernel panic - not syncing: Fatal exception in 
interrupt
   
  Oops output:
   no
   
  System Dump Info:
The system was configured to capture a dump, however a dump was not 
produced.

  -Attach sysctl -a output output to the bug.

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

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

[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues

[Hui Wang]

Yes, please also upload a alsa-info-with-coef without temp fix and
without plugging anything into the audio jack.

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

Title:
  Acer Aspire 5 sound driver issues

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  There seems to be lots of issues in sound driver for Acer Aspire
  A515-56-57XR with ALC255. I will list all of them below and what I
  have tried so far.

  1. Headphones appears always plugged in even if they are physically not
  2. When actually plugging in headset/earphones it does not auto switch from 
speakers/internal mic to headphones/headset microphone automatically and vice 
versa, have to manually switch everytime.
  3. External headset/earphones microphone won't work at all

  After, logs of trial and error I have found a temporary fix. This
  seems to use legacy intel drivers which solves all 3 issues mentioned
  above but the internal/dmic mic is completely gone (which seems
  intentional when using this). Both depreciated dmic_detect and
  dsp_driver works, I have been using dsp_driver for now as I need
  external microphone at any cost.

  End of /etc/modprobe.d/alsa-base.conf
  # Headset mic fix
  options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1
  options snd-hda-intel model=alc255-acer

  In another thread similar to this I got some support and at least
  fixed the external microphone without using the alsa-base.conf change
  in custom modified kernel. I will attach it here. Now, hoping to fix
  other issues as well slowly like making headphones unplugged when
  physically removing as well as auto switching like the legacy driver
  one.

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

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

[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues

[Bijay Shah]

Here is alsa-info with coef enabled. This info is as of applying temp
fix if it makes any difference. If alsa-info is needed with the temp fix
non applied then I can attach another one later.

** Attachment added: "alsa-info-with-coef.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+attachment/5501266/+files/alsa-info-with-coef.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/1930188

Title:
  Acer Aspire 5 sound driver issues

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  There seems to be lots of issues in sound driver for Acer Aspire
  A515-56-57XR with ALC255. I will list all of them below and what I
  have tried so far.

  1. Headphones appears always plugged in even if they are physically not
  2. When actually plugging in headset/earphones it does not auto switch from 
speakers/internal mic to headphones/headset microphone automatically and vice 
versa, have to manually switch everytime.
  3. External headset/earphones microphone won't work at all

  After, logs of trial and error I have found a temporary fix. This
  seems to use legacy intel drivers which solves all 3 issues mentioned
  above but the internal/dmic mic is completely gone (which seems
  intentional when using this). Both depreciated dmic_detect and
  dsp_driver works, I have been using dsp_driver for now as I need
  external microphone at any cost.

  End of /etc/modprobe.d/alsa-base.conf
  # Headset mic fix
  options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1
  options snd-hda-intel model=alc255-acer

  In another thread similar to this I got some support and at least
  fixed the external microphone without using the alsa-base.conf change
  in custom modified kernel. I will attach it here. Now, hoping to fix
  other issues as well slowly like making headphones unplugged when
  physically removing as well as auto switching like the legacy driver
  one.

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

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

[Kernel-packages] [Bug 1920674] Re: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation

[Kai-Heng Feng]

Can you please see if reverting commit
2d95ceb45459357288058c646022019d257ae04b "drm/amd/amdgpu: creating two
I2S instances for stoney/cz (v2)" helps?

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

Title:
  AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dear developers, please let me thank you for all your hard work first
  of all, I'm a big fan of yours!

  On my desktop PC with AMD A8-7680 APU, I'm facing 2 problems which
  seem to be connected to the amdgpu kernel module:

  1. Amdgpu kernel module loads correctly during boot, but VESA Xorg
  module is loaded instead of AMDGPU Xorg module during X startup. This
  results in non-accelerated X and high CPU load.

  - This situation is always reproducible.

  - I'm experiencing it with all kernel versions in between
  5.4.0-47-generic and 5.4.0-67-generic inclusive.

  - The situation escalates more with newer kernel version. For
  5.8.0-45-generic and 5.11.8-051108-generic, X even does not start and
  I just get black screen.

  - I have found a workaround after many days of googling and testing. AMDGPU 
Xorg module is loaded correctly if and only if I disable AMD ACP by means of 
the following kernel boot parameter:
  amdgpu.ip_block_mask=0xfdff

  - Acceleration is ok with kernels where AMD ACP is disabled by default
  (linux-image-linuxlite-5.6.0 for example)

  
  2. The 2nd problem I'm facing is with non functioning hibernation after I 
"fixed" the X acceleration. Hibernation image does not seem to get created, 
screen goes black, PC freezes but never turns off whenever AMDGPU Xorg module 
is loaded. Hibernation and subsequent resume is all ok if I disable AMDGPU by 
means of "nomodeset" and go just with VESA module.

  - always reproducible but tested only with 5.4.0-67-generic

  
  Thank you and best regards,
  Radek

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-67-generic 5.4.0-67.75
  ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94
  Uname: Linux 5.4.0-67-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  radek  1513 F pulseaudio
   /dev/snd/controlC0:  radek  1513 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Mar 21 15:22:29 2021
  HibernationDevice: RESUME=/dev/disk/by-label/SSD_LinuxSwap
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic 
root=UUID=1cc747ae-f2db-4733-aa04-be8d4bde050a ro ipv6.disable=1 net.ifnames=0 
nmi_watchdog=0 resume=LABEL=SSD_LinuxSwap amdgpu.ip_block_mask=0xfdff 
no_console_suspend
  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:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.20
  dmi.board.name: FM2A68M-HD+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.20:bd02/13/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+:rvr:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1909499] Re: iwlwifi 0000:03:00.0: No beacon heard and the time event is over already...

[Kai-Heng Feng]

Can you please try the -generic kernel instead of -lowlatency?

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

Title:
  iwlwifi :03:00.0: No beacon heard and the time event is over
  already...

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I see this error frequently inside logs: iwlwifi :03:00.0: No
  beacon heard and the time event is over already...

  Also, the internet doesn't seem stable, from time to time it
  disconnects and reconnects on its own, and other times it disconnects
  and wants me to enter the key again to connect. However, if i hit the
  X button to close the password modal and try to connect again from the
  networks list, it does connect without the need to enter the password.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.6
  ProcVersionSignature: Ubuntu 5.4.0-58.64-lowlatency 5.4.73
  Uname: Linux 5.4.0-58-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lyubo 14448 F pulseaudio
   /dev/snd/pcmC0D0p:   lyubo 14448 F...m pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Dec 28 21:50:51 2020
  Dependencies:
   
  InstallationDate: Installed on 2020-12-27 (0 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 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 275d:0ba6  USB OPTICAL MOUSE 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A515-51G
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-58-lowlatency 
root=/dev/mapper/vgkubuntu-root ro quiet splash lockdown=confidentiality 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-lowlatency N/A
   linux-backports-modules-5.4.0-58-lowlatency  N/A
   linux-firmware   1.187.6
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/03/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.02
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Charmander_KL
  dmi.board.vendor: KBL
  dmi.board.version: V2.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-51G
  dmi.product.sku: 
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1929870] Re: AMD desktop often fails to resume from deep suspend

[Kai-Heng Feng]

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

Title:
  AMD desktop often fails to resume from deep suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Machine setup:

  Desktop PC
  Ubuntu 21.04
  Linux version 5.11.0-17-generic
  AMD Ryzen 3900X
  Asus X590 PRIME PRO motherboard
  NVIDIA P400 GPU

  Approximately one in every 4 attempts to resume from a deep suspend
  fails. When the issue occurs the fans spin up but the monitor displays
  no output and input devices do not function, the system appears frozen
  and must be restarted using power or reset buttons.

  I have tried using different dNVIDIA isplay drivers (proprietary as
  well as open source) as well as trying an AMD Radeon HD 6450 GPU
  instead of the NVIDIA GPU.

  I have tried the following kernel parameters: processor.max_cstate=1
  rcu_nocbs=0-23

  I have updated the BIOS several times.

  I had similar problems with Ubuntu 20.10.

  I have enabled some additional kernel logging with initcall_debug.

  Fairly consistently the last message printed in the kernel log is from
  the ethernet driver:

  May 27 09:19:43 jacob-tm kernel: [  230.878348] OOM killer enabled.
  May 27 09:19:43 jacob-tm kernel: [  230.878349] Restarting tasks ... 
  May 27 09:19:43 jacob-tm kernel: [  230.879023] usb 5-2.3: USB disconnect, 
device number 4
  May 27 09:19:43 jacob-tm kernel: [  230.879026] usb 5-2.3.1: USB disconnect, 
device number 5
  May 27 09:19:43 jacob-tm kernel: [  230.879285] done.
  May 27 09:19:43 jacob-tm kernel: [  230.879318] PM: suspend exit
  May 27 09:19:43 jacob-tm kernel: [  230.880916] rfkill: input handler enabled
  May 27 09:19:43 jacob-tm kernel: [  230.955727] kauditd_printk_skb: 1 
callbacks suppressed
  May 27 09:19:43 jacob-tm kernel: [  230.955731] audit: type=1400 
audit(1622132383.424:64): apparmor="DENIED" operation="capab
  le" profile="/usr/sbin/cupsd" pid=4418 comm="cupsd" capability=12  
capname="net_admin"
  May 27 09:19:43 jacob-tm kernel: [  230.966192] audit: type=1400 
audit(1622132383.432:65): apparmor="DENIED" operation="capab
  le" profile="/usr/sbin/cups-browsed" pid=4429 comm="cups-browsed" 
capability=23  capname="sys_nice"
  May 27 09:19:43 jacob-tm kernel: [  231.120385] rfkill: input handler disabled
  May 27 09:19:43 jacob-tm kernel: [  231.225924] usb 5-2.3.2: USB disconnect, 
device number 6
  May 27 09:19:43 jacob-tm kernel: [  231.481893] usb 5-2.3.5: USB disconnect, 
device number 7
  May 27 09:19:47 jacob-tm kernel: [  235.009576] igb :05:00.0 enp5s0: igb: 
enp5s0 NIC Link is Up 1000 Mbps Full Duplex, Fl
  ow Control: RX/TX
  May 27 09:19:47 jacob-tm kernel: [  235.009913] IPv6: 
ADDRCONF(NETDEV_CHANGE): enp5s0: link becomes ready

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jacob  2024 F pulseaudio
   /dev/snd/controlC0:  jacob  2024 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 27 14:12:33 2021
  InstallationDate: Installed on 2020-10-28 (211 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=f721d5df-ceec-434a-919a-0680ee380996 ro quiet splash initcall_debug 
processor.max_cstate=1 rcu_nocbs=0-23 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
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-05-14 (13 days ago)
  dmi.bios.date: 05/08/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3604
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X570-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 

[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze

[Paul Szabo]

I have now tried the RC4 kernel from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13-rc4/amd64/
and sorry, but the freeze is still there.

Only now I notice that, curiously, the freeze may (is more likely to?)
occur while the network is essentially idle.

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

Title:
  rtw88_8821ce causes freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card.
  Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic 
kernel,and it works "well" for both WiFi and Bluetooth.
  However, this module (driver) causes frequent freezes, randomly but usually 
within a few minutes of running (thus very soon after boot): screen display 
remains frozen, no response to either keyboard or mouse input. All I can do is 
to hold the power button to power off, then reboot.

  After reboot, I do not see any crash reports, nor logs about the freeze.
  Please let me know if I should try to collect some info, and how.

  For now I use the DKMS module/driver from
    https://github.com/tomaspinho/rtl8821ce
  (having blacklisted rtw88_8821ce), and it seems to work perfectly.

  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
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  psz1189 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  8 16:58:19 2021
  InstallationDate: Installed on 2021-04-23 (14 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera
   Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Protempo Ltd L116HTN6SPW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer 
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: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2020
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Notebook
  dmi.product.name: L116HTN6SPW
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Protempo Ltd

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

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

[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues

[Hui Wang]

Please collect a log:

sudo sh -c 'echo 1 > /sys/module/snd_hda_codec/parameters/dump_coef'

Then collect an alsa-info.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/1930188

Title:
  Acer Aspire 5 sound driver issues

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  There seems to be lots of issues in sound driver for Acer Aspire
  A515-56-57XR with ALC255. I will list all of them below and what I
  have tried so far.

  1. Headphones appears always plugged in even if they are physically not
  2. When actually plugging in headset/earphones it does not auto switch from 
speakers/internal mic to headphones/headset microphone automatically and vice 
versa, have to manually switch everytime.
  3. External headset/earphones microphone won't work at all

  After, logs of trial and error I have found a temporary fix. This
  seems to use legacy intel drivers which solves all 3 issues mentioned
  above but the internal/dmic mic is completely gone (which seems
  intentional when using this). Both depreciated dmic_detect and
  dsp_driver works, I have been using dsp_driver for now as I need
  external microphone at any cost.

  End of /etc/modprobe.d/alsa-base.conf
  # Headset mic fix
  options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1
  options snd-hda-intel model=alc255-acer

  In another thread similar to this I got some support and at least
  fixed the external microphone without using the alsa-base.conf change
  in custom modified kernel. I will attach it here. Now, hoping to fix
  other issues as well slowly like making headphones unplugged when
  physically removing as well as auto switching like the legacy driver
  one.

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

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

[Kernel-packages] [Bug 1929166] Re: TGL-H system NV GPU fallen off the bus after resuming from s2idle with the external display connected via docking station

[Timo Aaltonen]

can't wait for the bios, kernel needs to release

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

Title:
  TGL-H system NV GPU  fallen off the bus after resuming from s2idle
  with the external display connected via docking station

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
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

Bug description:
  [SRU Justification]

  [Impact]
  The NVIDIA GPU will fall off the bus after exiting s2idle in TGL-H systems if 
the docking station with external display connected is unplugged when the 
system is still in s2idle. The system will be hold by the infinite loop in ACPI 
method IPCS and then the PCIe root port of NVIDIA gpu fails the power 
transition from D3cold to D0. Then display managed by the NVDIA GPU shows 
nothing until system reboot. Note that it only happens when NVIDIA GPU in 
either Performance mode or On-Demand mode.

  [Fix]
  A BIOS workaround is used to skip the ACPI method PGSC which invokes IPCS to 
do source clock control of the PCIe root port with an _OSI string 
"Linux-Dell-USB4-NVWakeup". Should be removed until we get a generic fix for it.

  [Test Case]
  1. On all TigerLake-H and later platforms with NVIDIA GPU, make sure the 
NVIDIA GPU is running in either On-Demand mode or Performance mode.
  2. Connect the docking station with the external display connected.
  3. Suspend the system.
  4. Remove the docking station when the system is suspended.
  5. Press power button to wake up the system and wait > 1 minutes to make sure 
if the display comes back.

  [Regression Potential]
  Low. This only works on platforms supporting "Linux-Dell-USB4-NVWakeup".
  No other platforms will be affected.

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

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

[Kernel-packages] [Bug 1929790] Re: Request to backport fix for endianness issue in TigerVNC vncviewer

[Frank Heimes]

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Package changed: linux (Ubuntu) => tigervnc (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/1929790

Title:
  Request to backport fix for endianness issue in TigerVNC vncviewer

Status in Ubuntu on IBM z Systems:
  New
Status in tigervnc package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  TigerVNC 1.11.0 contains a regression that causes vncviewer to display
  incorrect colors when vncviewer and X11 server use different endianness (e.g.,
  when using X11 forwarding via SSH between an x86-64 desktop and a Linux system
  on s390x). The regression was originally reported in github issue
  https://github.com/TigerVNC/tigervnc/issues/1073 and fixed in github pull
  request https://github.com/TigerVNC/tigervnc/pull/1084

  The regression caused vncviewer to always use the system byte order for pixel
  values instead of the byte order required by the X11 display. With the fix,
  vncviewer queries the X11 display for the required byte order.

  As of now, the fix has not made it into a release yet. Please consider
  backporting the fix (upstream commit 7ab92639848). I confirmed that this 
commit
  cleanly applies on top of release 1.11.0 and fixes the regression.

  ---uname output---
  Linux s390x
   
  Machine Type = x15 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   See also https://github.com/TigerVNC/tigervnc/issues/1252

  
  - From a Linux x86 system, connect to a Linux system on s390x via SSH with X 
forwarding
  - Start a Xvnc session on that Linux system

  tigervncserver :0 -geometry 800x600 -depth 32

  - Start vncviewer on the same Linux system

  xtigervncviewer :0

  - On vncviewer's window on your origin X session, observe incorrect colors.
  - Optionally, start X11 programs such as xlogo, xclock, or xeyes to make the 
problem obvious
  - Optionally, connect to the vnc session directly (i.e., with a vnc client on 
the origin system) to compare

   
  Userspace tool common name: vncviewer 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: tigervnc-viewer

  Userspace tool obtained from project website:  na

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

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

[Kernel-packages] [Bug 1918142] Re: Headphone microphone doesn't work - ALC255

[Bijay Shah]

Hello, I have filed a new bug with relevant details and added you to
notification. Thanks you once again for support, hope discussion above
helps OP as well.

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

Title:
  Headphone microphone doesn't work - ALC255

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  The headphone microphone is not working : I cannot register any sound from it.
  Driver is alc255 and the laptop is an Acer SF314-42.
  I am not sure what else I should post :S
  Best
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2021-03-08 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Acer Swift SF314-42
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic 
root=UUID=cffa8cec-df4e-4dca-94ba-c08d71257664 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-44-generic N/A
   linux-backports-modules-5.8.0-44-generic  N/A
   linux-firmware1.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-44-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: 08/26/2020
  dmi.bios.release: 1.7
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Kona_RN
  dmi.board.vendor: RO
  dmi.board.version: V1.07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.07
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.07:bd08/26/2020:br1.7:efr1.5:svnAcer:pnSwiftSF314-42:pvrV1.07:rvnRO:rnKona_RN:rvrV1.07:cvnAcer:ct10:cvrV1.07:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-42
  dmi.product.sku: 
  dmi.product.version: V1.07
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues

[Bijay Shah]

Link to custom modified kernel by kaihengfeng from another thread with
headset/earphones microphone fixed but other issues still remaining.

https://people.canonical.com/~khfeng/lp1918142-2/

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

Title:
  Acer Aspire 5 sound driver issues

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  There seems to be lots of issues in sound driver for Acer Aspire
  A515-56-57XR with ALC255. I will list all of them below and what I
  have tried so far.

  1. Headphones appears always plugged in even if they are physically not
  2. When actually plugging in headset/earphones it does not auto switch from 
speakers/internal mic to headphones/headset microphone automatically and vice 
versa, have to manually switch everytime.
  3. External headset/earphones microphone won't work at all

  After, logs of trial and error I have found a temporary fix. This
  seems to use legacy intel drivers which solves all 3 issues mentioned
  above but the internal/dmic mic is completely gone (which seems
  intentional when using this). Both depreciated dmic_detect and
  dsp_driver works, I have been using dsp_driver for now as I need
  external microphone at any cost.

  End of /etc/modprobe.d/alsa-base.conf
  # Headset mic fix
  options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1
  options snd-hda-intel model=alc255-acer

  In another thread similar to this I got some support and at least
  fixed the external microphone without using the alsa-base.conf change
  in custom modified kernel. I will attach it here. Now, hoping to fix
  other issues as well slowly like making headphones unplugged when
  physically removing as well as auto switching like the legacy driver
  one.

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

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

[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues

[Bijay Shah]

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+attachment/5501245/+files/lspci-vnvn.log

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

Title:
  Acer Aspire 5 sound driver issues

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  There seems to be lots of issues in sound driver for Acer Aspire
  A515-56-57XR with ALC255. I will list all of them below and what I
  have tried so far.

  1. Headphones appears always plugged in even if they are physically not
  2. When actually plugging in headset/earphones it does not auto switch from 
speakers/internal mic to headphones/headset microphone automatically and vice 
versa, have to manually switch everytime.
  3. External headset/earphones microphone won't work at all

  After, logs of trial and error I have found a temporary fix. This
  seems to use legacy intel drivers which solves all 3 issues mentioned
  above but the internal/dmic mic is completely gone (which seems
  intentional when using this). Both depreciated dmic_detect and
  dsp_driver works, I have been using dsp_driver for now as I need
  external microphone at any cost.

  End of /etc/modprobe.d/alsa-base.conf
  # Headset mic fix
  options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1
  options snd-hda-intel model=alc255-acer

  In another thread similar to this I got some support and at least
  fixed the external microphone without using the alsa-base.conf change
  in custom modified kernel. I will attach it here. Now, hoping to fix
  other issues as well slowly like making headphones unplugged when
  physically removing as well as auto switching like the legacy driver
  one.

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

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

[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues

[Bijay Shah]

** Attachment added: "alsa-info.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+attachment/5501246/+files/alsa-info.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/1930188

Title:
  Acer Aspire 5 sound driver issues

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  There seems to be lots of issues in sound driver for Acer Aspire
  A515-56-57XR with ALC255. I will list all of them below and what I
  have tried so far.

  1. Headphones appears always plugged in even if they are physically not
  2. When actually plugging in headset/earphones it does not auto switch from 
speakers/internal mic to headphones/headset microphone automatically and vice 
versa, have to manually switch everytime.
  3. External headset/earphones microphone won't work at all

  After, logs of trial and error I have found a temporary fix. This
  seems to use legacy intel drivers which solves all 3 issues mentioned
  above but the internal/dmic mic is completely gone (which seems
  intentional when using this). Both depreciated dmic_detect and
  dsp_driver works, I have been using dsp_driver for now as I need
  external microphone at any cost.

  End of /etc/modprobe.d/alsa-base.conf
  # Headset mic fix
  options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1
  options snd-hda-intel model=alc255-acer

  In another thread similar to this I got some support and at least
  fixed the external microphone without using the alsa-base.conf change
  in custom modified kernel. I will attach it here. Now, hoping to fix
  other issues as well slowly like making headphones unplugged when
  physically removing as well as auto switching like the legacy driver
  one.

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

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

[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues

[Bijay Shah]

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+attachment/5501244/+files/version.log

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

Title:
  Acer Aspire 5 sound driver issues

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  There seems to be lots of issues in sound driver for Acer Aspire
  A515-56-57XR with ALC255. I will list all of them below and what I
  have tried so far.

  1. Headphones appears always plugged in even if they are physically not
  2. When actually plugging in headset/earphones it does not auto switch from 
speakers/internal mic to headphones/headset microphone automatically and vice 
versa, have to manually switch everytime.
  3. External headset/earphones microphone won't work at all

  After, logs of trial and error I have found a temporary fix. This
  seems to use legacy intel drivers which solves all 3 issues mentioned
  above but the internal/dmic mic is completely gone (which seems
  intentional when using this). Both depreciated dmic_detect and
  dsp_driver works, I have been using dsp_driver for now as I need
  external microphone at any cost.

  End of /etc/modprobe.d/alsa-base.conf
  # Headset mic fix
  options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1
  options snd-hda-intel model=alc255-acer

  In another thread similar to this I got some support and at least
  fixed the external microphone without using the alsa-base.conf change
  in custom modified kernel. I will attach it here. Now, hoping to fix
  other issues as well slowly like making headphones unplugged when
  physically removing as well as auto switching like the legacy driver
  one.

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

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

[Kernel-packages] [Bug 1930188] [NEW] Acer Aspire 5 sound driver issues

[Bijay Shah]

Public bug reported:

Hello,

There seems to be lots of issues in sound driver for Acer Aspire
A515-56-57XR with ALC255. I will list all of them below and what I have
tried so far.

1. Headphones appears always plugged in even if they are physically not
2. When actually plugging in headset/earphones it does not auto switch from 
speakers/internal mic to headphones/headset microphone automatically and vice 
versa, have to manually switch everytime.
3. External headset/earphones microphone won't work at all

After, logs of trial and error I have found a temporary fix. This seems
to use legacy intel drivers which solves all 3 issues mentioned above
but the internal/dmic mic is completely gone (which seems intentional
when using this). Both depreciated dmic_detect and dsp_driver works, I
have been using dsp_driver for now as I need external microphone at any
cost.

End of /etc/modprobe.d/alsa-base.conf
# Headset mic fix
options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1
options snd-hda-intel model=alc255-acer

In another thread similar to this I got some support and at least fixed
the external microphone without using the alsa-base.conf change in
custom modified kernel. I will attach it here. Now, hoping to fix other
issues as well slowly like making headphones unplugged when physically
removing as well as auto switching like the legacy driver one.

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

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

Title:
  Acer Aspire 5 sound driver issues

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  There seems to be lots of issues in sound driver for Acer Aspire
  A515-56-57XR with ALC255. I will list all of them below and what I
  have tried so far.

  1. Headphones appears always plugged in even if they are physically not
  2. When actually plugging in headset/earphones it does not auto switch from 
speakers/internal mic to headphones/headset microphone automatically and vice 
versa, have to manually switch everytime.
  3. External headset/earphones microphone won't work at all

  After, logs of trial and error I have found a temporary fix. This
  seems to use legacy intel drivers which solves all 3 issues mentioned
  above but the internal/dmic mic is completely gone (which seems
  intentional when using this). Both depreciated dmic_detect and
  dsp_driver works, I have been using dsp_driver for now as I need
  external microphone at any cost.

  End of /etc/modprobe.d/alsa-base.conf
  # Headset mic fix
  options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1
  options snd-hda-intel model=alc255-acer

  In another thread similar to this I got some support and at least
  fixed the external microphone without using the alsa-base.conf change
  in custom modified kernel. I will attach it here. Now, hoping to fix
  other issues as well slowly like making headphones unplugged when
  physically removing as well as auto switching like the legacy driver
  one.

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

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

[Kernel-packages] [Bug 1926236] Re: Fix The sound has noise while audio volume is maximum

[Timo Aaltonen]

is in focal-proposed now, please test

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

** Tags added: verification-needed-focal

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

Title:
  Fix The sound has noise while audio volume is maximum

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  The sound has noise while turning the audio volume to maximum

  [Fix]
  For VEGA & Polaris, need two patches(landed on mainline kernel) to fix and a 
modprobe
  1.(50ceb1fe7a) drm/amd/pm: bug fix for pcie dpm, has landed on oem kernel.
  2.(9d03730ecb) drm/amd/pm: workaround for audio noise issue, has landed on 
oem kernel
  3. #modprobe amdgpu ppfeaturemask=0xfff7bffb.
  For Navi_1x, need smc firmware to fix.
  1. (4fe6e53b96 linux-firmware) amdgpu: update navi10 SMC firmware
  1. (8ab7abaf63 linux-firmware) amdgpu: update navi14 SMC firmware

  [Test]
  Verified on RKL platform 
  A. with wx3200(Polaris series) and the following configuration

  1. With these two patch,  

  1.1. (50ceb1fe7a) drm/amd/pm: bug fix for pcie dpm, has landed on oem kernel. 
  
  1.2. (9d03730ecb) drm/amd/pm: workaround for audio noise issue, has landed on 
oem kernel

   
  2. doesn't append ppfeaturemask=0xfff7bffb
   

   
  Can't observe issue.  
   

   
  B. With wx5500(Navi series) and update the related firmware,  
  
  Can't observe issue

  [Where problems could occur]
  Because disabling DPM, the power consumption would be slightly higher.

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

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

[Kernel-packages] [Bug 1929147] Re: fix system hang with 5.10 kernel + RX540 on RKL platform

[Timo Aaltonen]

is also in focal-proposed, please test

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

** Tags added: verification-needed-focal verification-needed-hirsute

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

Title:
  fix system hang with 5.10 kernel + RX540 on RKL platform

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-firmware source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]
  On RKL platform with AMD RX540, system would hang during boot-up.

  [Fix]
  AMD introduce a brand new firmware, polaris 12 MC firmware.
  This fix the issue and the system wouldn't hang during boot-up with AMD RX540.

  [Test]
  Verified on RKL platform and AMD RX540
  System would boot-up and login to desktop successfully.

  [Where problems could occur]
  This's a brand new firmware to support Polaris-series,
  it may introduce new issues.

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

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

[Kernel-packages] [Bug 1895276] Re: shmctl04 from ubuntu_ltp_syscalls failed with X-aws / 4.15

[Po-Hsu Lin]

Didn't see this on X-aws-4.15
4.15.0-1103.110~16.04.1
Test skipped:
shmctl04.c:167: TCONF: kernel doesn't support SHM_STAT_ANY

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

Title:
  shmctl04 from ubuntu_ltp_syscalls failed with X-aws / 4.15

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

Bug description:
  Issue spotted with 4.15.0-1054.58~16.04.1-oracle

  The test case got re-wrote in the upstream
  
https://github.com/linux-test-project/ltp/commit/234b8f200cd80556a4784a3a6b4b073061128c16#diff-c2b2d6e89ea2cd9831c395fbe1bef9f3

  Test failed with:
   startup='Fri Sep 11 07:28:24 2020'
   tst_test.c:1250: INFO: Timeout per run is 0h 05m 00s
   shmctl04.c:115: FAIL: SHM_INFO haven't returned a valid index: SUCCESS (0)
   shmctl04.c:131: FAIL: Counted used = 0, used_ids = 4
   shmctl04.c:72: PASS: used_ids = 4
   shmctl04.c:79: PASS: shm_rss = 6
   shmctl04.c:86: PASS: shm_swp = 0
   shmctl04.c:93: PASS: shm_tot = 7
   
   Summary:
   passed   4
   failed   2
   skipped  0
   warnings 0
   tag=shmctl04 stime=1599809304 dur=0 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/1895276/+subscriptions

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

[Kernel-packages] [Bug 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)

[Frank Heimes]

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

Title:
  [Ubuntu 20.4.2]  vLan not getting static IP assigned (on s390x)

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

Bug description:
  ---Problem Description---
  Doing vLAN configuration one of the vLANs is not getting static IP assigned 
when the rest are workin without problems
   
  Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com 
   
  ---uname output---
  Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 
17:29:32 UTC 2021 s390x s390x s390x GNU/Linux
   
  Machine Type = z15 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1)Configure the netplan file as follow:
  root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml

  # This is the network config written by 'subiquity'

  network:

ethernets:

  encdb0:

addresses:

- 11.111.114.213/22

macaddress: 02:76:54:00:00:03

  encdc0:

addresses:

- 11.111.112.213/22

macaddress: 02:76:54:00:00:04

  enP50s3832 :

addresses:

- 11.111.112.214/22

  enP53p0s0:

addresses:

- 11.111.112.215/22

vlans:

  encdb0.160:

id: 160

link: encdb0

mtu: 9000

addresses:

- 192.168.160.53/24

  encdc0.150:

id: 150

link: encdc0

mtu: 9000

addresses:

- 192.168.150.53/24

  enP50s3832.170:

id: 170

link: enP50s3832

mtu: 9000

addresses:

- 192.168.170.53/24

  enP53p0s0.171:

id: 171

link: enP53p0s0

mtu: 9000

addresses:

- 192.168.171.53/24

version: 2

  2)run net plan apply:
  root@ilabg13:~# netplan --debug apply

  ** (generate:59965): DEBUG: 14:55:15.046: Processing input file
  /etc/netplan/00-installer-config.yaml..

  ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass

  ** (generate:59965): DEBUG: 14:55:15.046: Processing input file
  /etc/netplan/01-iscsi-config.yaml..

  ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass

  ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass
  them through a final round of validation

  ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting
  default backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting
  default backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.047: Generating output files..

  ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition
  ence0f is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition
  ence0f is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition
  encdb0 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition
  encdb0 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition
  encdc0 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition
  encdc0 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition
  enP50s3832 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition
  enP50s3832 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition
  enP53p0s0 is not for us (backend 1)

  ** (generate:59965): 

[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS

[Doug Smythies]

Within the context of this bug report it is valid, as it is specifically
about the mainline PPA.

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

Title:
  Recent mainline packages are built with Hirsuite 21.04, not Focal
  20.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  The Mainline wiki states that the mainline kernels are built with the
  previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are
  being built with Hirsuite 21.04, and before that Groovy? If this is
  intentional, then the wiki should be updated to reflect the change in
  policy.

  From https://wiki.ubuntu.com/Kernel/MainlineBuilds

Mainline kernel build toolchain
These kernels are built with the toolchain (gcc, g++, etc.) from the 
previous Ubuntu LTS release. 
(e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic 
Beaver", etc.) Therefore, 
out-of-tree kernel modules you already have built and installed for use 
with your release kernels 
are not likely to work with the mainline builds.

  The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On
  my Focal LTS system I have GCC 9.3.0.

  The Mainline kernel build toolchain
  These kernels are built with the toolchain (gcc, g++, etc.) from the previous 
Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 
18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already 
have built and installed for use with your release kernels are not likely to 
work with the mainline builds.

  The *linux-headers-generic* packages have unmet dependencies on 20.04
  LTS.

  I could install Groovy built kernels fine, but the Hirsuite ones built
  with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels
  can't be installed on Focal (libc 2.31).

  Thanks,
  Mark

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

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

[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS

[David R. Bergstein]

Like many of you out there I totally disagree with the decision to mark
this bug as invalid.  I myself am running newer hardware that requires
support from kernel 12.x and can now only use compatible kernels like
the ones produced by tux-invader, not the ones on the mainline ppa.

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

Title:
  Recent mainline packages are built with Hirsuite 21.04, not Focal
  20.04 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  The Mainline wiki states that the mainline kernels are built with the
  previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are
  being built with Hirsuite 21.04, and before that Groovy? If this is
  intentional, then the wiki should be updated to reflect the change in
  policy.

  From https://wiki.ubuntu.com/Kernel/MainlineBuilds

Mainline kernel build toolchain
These kernels are built with the toolchain (gcc, g++, etc.) from the 
previous Ubuntu LTS release. 
(e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic 
Beaver", etc.) Therefore, 
out-of-tree kernel modules you already have built and installed for use 
with your release kernels 
are not likely to work with the mainline builds.

  The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On
  my Focal LTS system I have GCC 9.3.0.

  The Mainline kernel build toolchain
  These kernels are built with the toolchain (gcc, g++, etc.) from the previous 
Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 
18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already 
have built and installed for use with your release kernels are not likely to 
work with the mainline builds.

  The *linux-headers-generic* packages have unmet dependencies on 20.04
  LTS.

  I could install Groovy built kernels fine, but the Hirsuite ones built
  with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels
  can't be installed on Focal (libc 2.31).

  Thanks,
  Mark

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

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