[Kernel-packages] [Bug 1929166] [NEW] TGL-H system NV GPU fallen off the bus after resumes from s2idle with the external display connected via docking station

[Chris Chiu]

Public bug reported:

[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 IPSC to 
power on 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.

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

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

** Affects: linux (Ubuntu Focal)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem-5.10 (Ubuntu Focal)
 Importance: Undecided
 Assignee: Chris Chiu (mschiu77)
 Status: In Progress

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

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

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

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

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

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

** Changed in: linux-oem-5.10 (Ubuntu Focal)
 Assignee: (unassigned) => Chris Chiu (mschiu77)

-- 
You 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 resumes from s2idle with
  the external display connected via docking station

Status in linux package in Ubuntu:
  New
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:
  In Progress

Bug description:
  [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 IPSC to 
power on 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/ubuntu/+source/linux/+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 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

[Timo Aaltonen]

** Changed in: linux-oem-5.10 (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting
  s2idle

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

Bug description:
  [SRU Justification]

  [Impact]
  All of 3 different WD19(TB/SC/DC) docks have 3 Type-A ports and 2 Type-C 
ports, and there're highspeed Hubs(0bda:5487 and its substream hub 0bda:5413) 
and Superspeed Hubs (0bda:0487 and its downstream hub 0bda:0413). In the bug 
description below, we will refer the 2 highspeed hubs as Hub A and Hub A.3, and 
the 2 superspeed hubs as Hub B and Hub B.3. All devices connected via either 
Type-A or Type-C ports will connect to either Hub A.3 or Hub B.3. If we connect 
a wakup enabled device (keyboard) to a Type-A port, the Hub A.3 will fail to 
activate after exiting s2idle and all downstream devices will not be detected. 
If we have a superspeed device connected to other Type-A port in addition to 
the keyboard, this superspeed device actually connects to Hub B.3, and the Hub 
B.3 will also fails to work after exiting s2idle. If the wakeup enabled device 
connects via Type-C port, there's no such problem.

  As a summary, a wakeup enabled device connect to Type-A port will
  cause the failure of Hub A.3 and Hub B.3. Hub B.3 only fails when a
  wakeup enabled device and a superspeed device both connect via Type-A
  port.

  [Fix]
  Before the resume failure, the upstream hub(Hub A or B) will hit the timeout 
problem while doing SetPortFeature(PORT_SUSPEND) to the port of the downstream 
hub (Hub A.3 or Hub B.3). However, the PORT_SUSPEND bit of the wPortStatus is 
actually turned on for the Hub A.3, we simply need to make the kernel believe 
it's already suspended. Then the ClearPortFeature will be done during resume 
and the problem will go away.

  The Hub B.3 will be tricky. The PORT_SUSPEND bit is not on after the
  suspend timeout, but it needs the ClearPortFeature(PORT_SUSPEND) for
  Hub B.3 to avoid resume failure. It doesn't comply with the USB spec
  so it's hard to create a generic fix for it. Because it only happens
  when timeout happens on suspending Hub A.3 and there's a superspeed
  device connecting to Type-A port, we choose to leave it as-is and try
  to address it in the future.

  [Test Case]
  1. Make sure that the WD19 connects to the laptop
  2. Connect USB keyboard/mouse to USB Type-A ports.
  3. Suspend the system
  4. Press the Enter key or power button to wake up the system
  5. Check if the USB keyboard/mouse are still working
  Repeat 4 and 5 for > 10 times w/o losing any USB devices.

  
  [Where problems could occur]
  A wakeup enabled device (keyboard) connect to Type-A port will cause the 
failure of Hub A.3 and Hub B.3 during resume. Hub B.3 only fails when a wakeup 
enabled device and a superspeed device both connect via Type-A port. All 
devices connects to Hub A.3 (and B.3 if superspeed device connect via Type-A 
port) will be lost after resume.

  [Regression Potential]
  Minimum. The fix is only triggered when timeout happens during USB port 
suspend and it follows the standard USB protocol to do either resume or 
reset_resume.

  == Original Bug Description ==

  ● Summary
  Plug in USB mouse and USB keyboard to WD19/WD19DC USB ports near LAN port. 
Plug dock into SUT and check USB keyboard and mouse work. SUT enter suspend. 
After 1 min resume SUT, check USB keyboard/mouse function. Sometimes USB 
keyboard/mouse no function.

  Isolation:
  1. VP on UMA and Discrete
  2. When issue occur, both front and back port on WD19 can't work using USB 
keyboard/mouse but USB Key.

  ● Reproduce Steps
  1.Plug in USB mouse and USB keyboard to WD19/WD19DC USB ports near LAN port.
  2.Plug dock into SUT and check USB keyboard and mouse work.
  3. SUT enter suspend.
  4.After 1 min, resume SUT and check USB keyboard/mouse function.
  5.Sometimes USB keyboard/mouse no function.

  ● Results
  ○ Expected Result
  USB mouse or keyboard on dock can use after suspend

  ○ Actual Result
  USB mouse or keyboard on dock sometimes no function after suspend

  ● Additional Information
  ○ Test Vault ID：60943.011
  ○ SKU：Broadmoor Latitude5421
  ○ BIOS Version：0.3.21
  ○ Image/Manifest：
  dell-bto-focal-f

[Kernel-packages] [Bug 1928750] Re: Support mic-mute on Dell's platform

[Timo Aaltonen]

** Changed in: linux-oem-5.10 (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Support mic-mute on Dell's platform

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

Bug description:
  [Impact]
  On Dell's platform, the MIC-Mute can't work.

  [Fix]
  Here's v8 patch, support MIC-Mute of dell e-privacy feature.
  Link: https://patchwork.kernel.org/project/alsa-devel/list/?series=477845
  The set of patches has been verified and works well on dell's machine.
  In the upstream, Hans De Goede ask dell's developer to follow ucm2 and Dell 
will upstream v9.
  For the schedule, can't wait v9 and sru v8 first.
  In the feature, will sru the final solution.

  [Test Case]
  1. fire "arecord record_file"
  2. press mic-mute hot-key and wait 20s.
  3. check the record file and can't hear voice.

  [Where problems could occur]
  Because the rt715 patch doesn't follow the ucm2, dell will upstream v9.
  In the future, will sru the final solution again.

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

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

[Kernel-packages] [Bug 1909814] Re: Keyboard not working

[Philippe Schottey]

Latest kernel not working for me.

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

Title:
  Keyboard not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  Brand new laptop (Medion), keyboard is only working with the grub menu.
  Mouse is now working since 20.10 have been installed.
  Only the luminosity key are working on the keyboard.
  External usb keyboard works fine.
  I tried to install with usb keyboard disconnected but doesn't change anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  did4364 F pulseaudio
   /dev/snd/pcmC0D0p:   did4364 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  1 16:24:12 2021
  InstallationDate: Installed on 2021-01-01 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: MEDION S15450
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2020
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 209
  dmi.board.asset.tag: Default string
  dmi.board.name: M15T
  dmi.board.vendor: MEDION
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: MEDION
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring:
  dmi.product.family: Akoya
  dmi.product.name: S15450
  dmi.product.sku: ML-230008 30030452
  dmi.product.version: Default string
  dmi.sys.vendor: MEDION

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

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

[Kernel-packages] [Bug 1925981] Re: 20.04.02 introduces noise into the audio channel when using YouTube

[Kai-Heng Feng]

Is it a kernel regression? Can you please try 20.04 with kernel 4.15?

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

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

Title:
  20.04.02 introduces noise into the audio channel when using YouTube

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My hardware:
  HDMI output to TV/Monitor. Optical cable to Phonak TVLink. Bluetooth to 
compilot. ComPilot to hearing aids.
  Browsing YouTube with Google Chrome.
  Works fine with 18.04.
  Tried Ubuntu MATE 20.04.02.
  High level of noise with 20.04. When reboot to 18.04 noise goes away.

  Not Hardware. Just bad code in 20.04.02 audio.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-142-generic 4.15.0-142.146
  ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18
  Uname: Linux 4.15.0-142-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 6819 F pulseaudio
   /dev/snd/controlC0:  robert 6819 F pulseaudio
  CurrentDesktop: MATE
  Date: Fri Apr 23 19:30:35 2021
  InstallationDate: Installed on 2019-12-22 (488 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic 
root=UUID=ae6f5cdd-0c3b-48a9-8449-da1027511bec ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-142-generic N/A
   linux-backports-modules-4.15.0-142-generic  N/A
   linux-firmware  1.173.20
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  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.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1924685] Re: No sound output/input available after installing 21.04

[Anthony Wong]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

Title:
  No sound output/input available after installing 21.04

Status in OEM Priority Project:
  Won't Fix
Status in Release Notes for Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Image: Hirsute 21.04 (20210415 daily build)

  Device: Dell Precision 5750

  After installing 21.04, the sound card is unavailable. In Sound
  Settings, there is only one choice: "Dummy Output" .

  The only way to hear sound is to connect a Bluetooth speaker.

  Note: this device was enabled with 20.04 and 5.6.0-1035-oem kernel:

  https://certification.ubuntu.com/hardware/202002-27726

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-14-generic 5.11.0-14.15
  ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
  Uname: Linux 5.11.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1561 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 16 15:10:05 2021
  InstallationDate: Installed on 2021-04-16 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  MachineType: Dell Inc. Precision 5750
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic 
root=UUID=2562d52a-de88-45e9-9d0a-3a79e48b1638 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-14-generic N/A
   linux-backports-modules-5.11.0-14-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2020
  dmi.bios.release: 1.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:br1.6:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5750
  dmi.product.sku: 0990
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1912673] Re: sounds not working on Dell XPS 17 (9700)

[Anthony Wong]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

Title:
  sounds not working on Dell XPS 17 (9700)

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Debian:
  Fix Released

Bug description:
  My investigation process:

  Dell XPS 17 (9700) comes with Windows 10 preinstalled, where sounds
  worked.

  I installed Ubuntu 20.04 LTS fresh, sounds did not work on speakers or 3.5mm 
headphones,
  using linux-image-5.4.0-42-generic, I did not try blutooth.

  I sudo apt upgrade, dist-upgrade to get kernels

  linux-image-5.8.0-38-generic
  linux-image-5.8.0-40-generic

  Sounds did not work.
  I download linux-image-unsigned-5.10.9-051009-generic.
  Sounds did not work.

  I upgrade Dell XPS 9700 firmware from 1.3 to 1.63.
  Sounds did not work.

  After googling I found this solution in the comments:
  https://askubuntu.com/questions/1270442/no-sound-on-xps-17-9700

  """

  Download and install dkms module:

  https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/pc-oem-
  dkms/+packages

  Alternatively, you can install linux-oem-20.04, it will install
  the 5.6 kernel with the above driver. Your system may be more stable
  with 5.4 kernel since it is in wide use.

  Manually install sof-firmware from Arch Linux:

  https://archlinux.pkgs.org/rolling/archlinux-extra-x86_64/sof-
  firmware-1.5.1-1-any.pkg.tar.zst.html

  You will need to delete the existing "sof" and "sof-tplg" files
  from the Ubuntu linux-firmware package first. Note if this package
  gets updated from Canoncial and they don't update these, you will have
  to delete and then reextract. Files go into the
  /usr/lib/firmware/intel/sof and /usr/lib/firmware/intel/sof-tplg
  folders.

  Manually install the ucm2 files:

  http://xps17.ddns.net/sof-soundwire.zip

  These go into /usr/share/alsa/ucm2/sof-soundwire. Delete the
  contents of the existing sof-soundwire folder (if you have it) and
  replace them with the ones from the archive.

  Reboot. You should now have all your audio devices available. If speakers 
do not play, you may need to run alsamixer (non-root) from a terminal and 
unmute and set the mixer levels all the way up.
  """


  This solution worked for me on linux-image-5.6.0-1042-oem AFTER
  manually opening alsa-mixer and changing soundcard to sof. The sound
  would otherwise just show 'dummy'.

  My sounds still do not work on 5.8 or 5.10, full name listed above. I
  did not get to test this temporary fix with 5.4.

  my full alsa-info:
  http://alsa-project.org/db/?f=6a638be0cfbe8ed08a010eb26a7702e324dce5ff

  based on some google research, this seems to be a common problem:
  
https://www.reddit.com/r/Dell/comments/hj8oxw/xps_17_9700_no_audio_on_linux_also_hardware_is/
  
https://www.reddit.com/r/Dell/comments/hge2yo/no_audio_on_linux_ubuntu_2004_xps_17_9700_realtek/
  
https://www.reddit.com/r/Dell/comments/j2kdjw/xps_17_9700_on_linux_audio_issue/
  etc...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.10
  ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
  Uname: Linux 5.6.0-1042-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neoh   1786 F pulseaudio
   /dev/snd/pcmC1D0p:   neoh   1786 F...m pulseaudio
   /dev/snd/controlC0:  neoh   1786 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 21 12:08:45 2021
  InstallationDate: Installed on 2021-01-20 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.3
  dmi.board.name: 0CXCCY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0CXCCY:rvrA03:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 17 9700
  dmi.product.sku: 098F
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Dependencies:
   
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-20 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitec

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

[Kai-Heng Feng]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13-rc2/amd64/

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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: 
dmi:bvnAmericanMegatrendsInc.:bvrF.23:bd10/30/2020:br15.23:efr40.28:svnHP:pnOMENbyHPLaptop15-ce0xx:pvr:rvnHP:rn838F:rvr40.28:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-ce0xx
  dmi.product.sku: 1KV78UA#ABA
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1925964] Re: HP NC364T NIC with 20.04.2 LTS Issues

[Kai-Heng Feng]

It doesn't need to be a coder to rollback to an older kernel.

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

Title:
  HP NC364T NIC with 20.04.2 LTS Issues

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This NIC is a 4 Port Copper 1GB Intel 82571B/82571GB Gigabit Ethernet
  Controller with a Dual Chipset where each Chipset controls 2 ports
  each (ie (1 Chipset - 2 Ports) * 2).  In the latest 20.04.2 LTS, the
  OS is mapping the ports incorrectly, causing only 2 of the 4 total
  ports to be allocated via DMESG:

  thannock@nwtools04-usdc7:~$ lspci 
  00:00.0 Host bridge: Intel Corporation 5000P Chipset Memory Controller Hub 
(rev b1)
  00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 
2 (rev b1)
  00:03.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 
3 (rev b1)
  00:04.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 
4-5 (rev b1)
  00:05.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 
5 (rev b1)
  00:06.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 
6 (rev b1)
  00:07.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 
7 (rev b1)
  00:10.0 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev 
b1)
  00:10.1 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev 
b1)
  00:10.2 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev 
b1)
  00:11.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers 
(rev b1)
  00:13.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers 
(rev b1)
  00:15.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 
b1)
  00:16.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 
b1)
  00:1d.0 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI 
USB Controller #1 (rev 09)
  00:1d.1 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI 
USB Controller #2 (rev 09)
  00:1d.2 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI 
USB Controller #3 (rev 09)
  00:1d.3 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI 
USB Controller #4 (rev 09)
  00:1d.7 USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI 
USB2 Controller (rev 09)
  00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9)
  00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC 
Interface Controller (rev 09)
  00:1f.1 IDE interface: Intel Corporation 631xESB/632xESB IDE Controller (rev 
09)
  01:03.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
ES1000 (rev 02)
  01:04.0 System peripheral: Compaq Computer Corporation Integrated Lights Out 
Controller (rev 03)
  01:04.2 System peripheral: Compaq Computer Corporation Integrated Lights Out  
Processor (rev 03)
  01:04.4 USB controller: Hewlett-Packard Company Integrated Lights-Out 
Standard Virtual USB Controller
  01:04.6 IPMI Interface: Hewlett-Packard Company Integrated Lights-Out 
Standard KCS Interface
  02:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev c3)
  03:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme II 
BCM5708 Gigabit Ethernet (rev 12)
  04:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev c3)
  05:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme II 
BCM5708 Gigabit Ethernet (rev 12)
  06:00.0 PCI bridge: Broadcom EPB PCI-Express to PCI-X Bridge (rev b4)
  07:04.0 PCI bridge: Broadcom BCM5785 [HT1000] PCI/PCI-X Bridge (rev b2)
  07:08.0 RAID bus controller: Hewlett-Packard Company Smart Array E200i (SAS 
Controller)
  09:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream 
Port (rev 01)
  09:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X 
Bridge (rev 01)
  0a:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream 
Port E1 (rev 01)
  0a:01.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream 
Port E2 (rev 01)
  0a:02.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream 
Port E3 (rev 01)
  0b:00.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane 3-Port PCI Express 
Switch (rev 0e)
  0c:02.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane 3-Port PCI Express 
Switch (rev 0e)
  0c:04.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane 3-Port PCI Express 
Switch (rev 0e)
  0d:00.0 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit 
Ethernet Controller (Copper) (rev 06)
  0d:00.1 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit 
Ethernet Controller (Copper) (rev 06)
  0e:00.0 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit 
Ethernet Controller (Copper) (rev 06)
  0e:00.1 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit 
Et

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

[Kai-Heng Feng]

Blacklist amdgpu via kernel parameter "blacklist=amdgpu
modprobe.blacklist=amdgpu", SSH to the system, then run "modprobe
amdgpu" to see what happened.

-- 
You 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 1925415] Re: Enable mute/micmute LEDs and limit mic boost on EliteBook 845 G8

[Kai-Heng Feng]

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

Title:
  Enable mute/micmute LEDs and limit mic boost on EliteBook 845 G8

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-oem-5.10 source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  Mute/micmute LEDs don't work.
  In addition, the internal mic can only capture lots of noises.

  [Fix]
  Use Realtek specific coef to enable LEDs and limit mic boost on the
  platform.

  [Test]
  With the patch applied, the both LEDs start to work, and audio recording
  becomes crystal clear.

  [Where problems could occur]
  It's a trivial change to a brand new device, so no existing device is
  affected.

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

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

[Kernel-packages] [Bug 1925675] Re: hirsuit kernel fails to detect monitor plugged into USBC thunderbolt socket

[Kai-Heng Feng]

Please test latest drm-tip kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/

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

Title:
  hirsuit kernel fails to detect monitor plugged into USBC thunderbolt
  socket

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On upgrade to hirsuit hippo, my Dell 9360 no longer detects a monitor
  plugged into the thunderbolt usbc socket. If I reboot with the latest
  kernel from Ubuntu 20.10 (version 5.8.0-50) it works perfectly,
  detecting the monitor from kernel boot.

  I have tried both a thunderbolt cable, where usb devices plugged into
  the monitor are detected, but the monitor itself is not, and a
  usbc<->displayport adaptor that puts the socket straight into DP
  alternate mode. Neither work in 21.04.

  Happy to try and debug this, but not sure where to start!

  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:  phil   3089 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Thu Apr 22 20:11:35 2021
  HibernationDevice: RESUME=UUID=8b5c4d3a-8f9a-420d-a564-3d58a0c0502b
  InstallationDate: Installed on 2018-07-19 (1008 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia Integrated Webcam HD
   Bus 001 Device 002: ID 0cf3:e300 Qualcomm Atheros Communications QCA61x4 
Bluetooth 4.0
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (0 days ago)
  dmi.bios.date: 03/09/2021
  dmi.bios.release: 2.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.15.1
  dmi.board.name: 0PVG6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.15.1:bd03/09/2021:br2.15:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PVG6D:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.product.sku: 082A
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-04-29T12:11:49.292007

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Kai-Heng Feng]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13-rc2/amd64/

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1916945] Re: unable to Poweroff, it causes a restart instead

[Kai-Heng Feng]

Would it be possible for you to do a kernel bisection?

First, find the last -rc kernel works and the first -rc kernel doesn’t
work from http://kernel.ubuntu.com/~kernel-ppa/mainline/

Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good $(the working version you found)
$ git bisect bad $(the non-working version found)
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If it still have the same issue,
$ git bisect bad
Otherwise,
$ git bisect good
Repeat to "make -j`nproc` deb-pkg" until you find the offending commit.

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

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

Title:
  unable to Poweroff, it causes a restart instead

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 20.04 after jan/2021 update I am unable to poweroff (or
  shutdown) the laptop.

  it works fine if I poweroff in windows or when boot test 20.04 iso OS
  and power off

  HP probook 650

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-66-generic 5.4.0-66.74
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Uname: Linux 5.4.0-66-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cvancrae   2080 F pulseaudio
   /dev/snd/controlC1:  cvancrae   2080 F pulseaudio
   /dev/snd/pcmC1D0c:   cvancrae   2080 F...m pulseaudio
   /dev/snd/pcmC1D0p:   cvancrae   2080 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 25 20:15:49 2021
  InstallationDate: Installed on 2018-07-30 (940 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Hewlett-Packard HP ProBook 650 G1
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=ef9f1472-488d-4d4d-94ae-545d7b6bf18e ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2017
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.40
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.asset.tag: 5CG4380HYL
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.40:bd07/13/2017:svnHewlett-Packard:pnHPProBook650G1:pvrA3009DD10203:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP ProBook 650 G1
  dmi.product.sku: D9S35AV
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1909814] Re: Keyboard not working

[Kai-Heng Feng]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13-rc2/amd64/

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

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

Title:
  Keyboard not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  Brand new laptop (Medion), keyboard is only working with the grub menu.
  Mouse is now working since 20.10 have been installed.
  Only the luminosity key are working on the keyboard.
  External usb keyboard works fine.
  I tried to install with usb keyboard disconnected but doesn't change anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  did4364 F pulseaudio
   /dev/snd/pcmC0D0p:   did4364 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  1 16:24:12 2021
  InstallationDate: Installed on 2021-01-01 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: MEDION S15450
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2020
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 209
  dmi.board.asset.tag: Default string
  dmi.board.name: M15T
  dmi.board.vendor: MEDION
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: MEDION
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring:
  dmi.product.family: Akoya
  dmi.product.name: S15450
  dmi.product.sku: ML-230008 30030452
  dmi.product.version: Default string
  dmi.sys.vendor: MEDION

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

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

[Kernel-packages] [Bug 1928183] Re: turbostat doesn't work with AMD Cezanne APUs

[Po-Hsu Lin]

Hi David,

I found a laptop with AMD Ryzen 5 APU and gave it a try, before this
patch turbostat will terminate with return code 243:

Welcome to Ubuntu Impish Indri (development branch) (GNU/Linux 
5.11.0-16-generic x86_64)
$ sudo turbostat 
turbostat version 20.09.30 - Len Brown 
CPUID(0): AuthenticAMD 0x10 CPUID levels; 0x8020 xlevels; 
family:model:stepping 0x17:60:1 (23:96:1)
CPUID(1): SSE3 MONITOR - - - TSC MSR - HT -
CPUID(6): APERF, No-TURBO, No-DTS, No-PTM, No-HWP, No-HWPnotify, No-HWPwindow, 
No-HWPepp, No-HWPpkg, No-EPB
CPUID(7): No-SGX
RAPL: 234 sec. Joule Counter Range, at 280 Watts
/dev/cpu_dma_latency: 20 usec (default)
current_driver: acpi_idle
current_governor: menu
current_governor_ro: menu
cpu4: POLL: CPUIDLE CORE POLL IDLE
cpu4: C1: ACPI FFH MWAIT 0x0
cpu4: C2: ACPI IOPORT 0x414
cpu4: C3: ACPI IOPORT 0x415
cpu4: cpufreq driver: acpi-cpufreq
cpu4: cpufreq governor: schedutil
cpufreq boost: 1
cpu0: MSR_RAPL_PWR_UNIT: 0x000a1003 (0.125000 Watts, 0.15 Joules, 0.000977 
sec.)
$ echo $?
243

After installing debs from 
https://people.canonical.com/~phlin/kernel/lp-1928183-turbostat-cezanne/ and 
reboot to 5.11.0-18, the turbostat command seems to be working (not terminate 
early with 243):
$ sudo turbostat 
turbostat version 20.09.30 - Len Brown 
CPUID(0): AuthenticAMD 0x10 CPUID levels; 0x8020 xlevels; 
family:model:stepping 0x17:60:1 (23:96:1)
CPUID(1): SSE3 MONITOR - - - TSC MSR - HT -
CPUID(6): APERF, No-TURBO, No-DTS, No-PTM, No-HWP, No-HWPnotify, No-HWPwindow, 
No-HWPepp, No-HWPpkg, No-EPB
CPUID(7): No-SGX
RAPL: 234 sec. Joule Counter Range, at 280 Watts
/dev/cpu_dma_latency: 20 usec (default)
current_driver: acpi_idle
current_governor: menu
current_governor_ro: menu
cpu4: POLL: CPUIDLE CORE POLL IDLE
cpu4: C1: ACPI FFH MWAIT 0x0
cpu4: C2: ACPI IOPORT 0x414
cpu4: C3: ACPI IOPORT 0x415
cpu4: cpufreq driver: acpi-cpufreq
cpu4: cpufreq governor: schedutil
cpufreq boost: 1
cpu0: MSR_RAPL_PWR_UNIT: 0x000a1003 (0.125000 Watts, 0.15 Joules, 0.000977 
sec.)
CoreCPU Avg_MHz Busy%   Bzy_MHz TSC_MHz IRQ POLLC1  C2  
C3  POLL%   C1% C2% C3% CorWatt PkgWatt
-   -   2   0.0819203716542 22  67  0   
457 0.000.060.0099.81   0.013.66
0   0   2   0.101873371750  0   3   0   
48  0.000.040.0099.84   0.003.66
0   1   0   0.031860371715  0   0   0   
15  0.000.000.0099.93
1   2   1   0.042759371728  0   2   0   
26  0.000.010.0099.91   0.00
1   3   0   0.022636371712  1   1   0   
10  0.000.010.0099.93
2   4   1   0.023079371722  1   6   0   
15  0.000.010.0099.92   0.00
2   5   1   0.042790371730  0   13  0   
20  0.000.370.0099.55
4   6   2   0.141738371774  4   12  0   
60  0.000.070.0099.79   0.00
4   7   2   0.101747371748  4   9   0   
35  0.020.050.0099.82
5   8   1   0.042305371719  0   0   0   
19  0.000.000.0099.93   0.00
5   9   2   0.091876371746  3   5   0   
38  0.000.040.0099.84
6   10  2   0.092114371750  4   7   0   
39  0.020.070.0099.81   0.00
6   11  5   0.3116573717148 5   9   0   
132 0.010.080.0099.65

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

Title:
  turbostat doesn't work with AMD Cezanne APUs

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Hirsute:
  Incomplete

Bug description:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985681 describes the
  issue and necessary cherry-pick
  (https://git.kernel.org/linus/301b1d3a9104f4f3a8ab4171cf88d0f55d632b41).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-tools-common 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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bartle 2287 F pulseaudio
   /dev/snd/controlC0:  bartle 2287 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed May 12 01:04:15 2021
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  PackageArchitecture: all
  ProcFB: 0 amdgp

[Kernel-packages] [Bug 1929144] Re: linux ADT test failure with linux/4.15.0-144.148 i386 (stress-misaligned.0 failed)

[Kelsey Skunberg]

** Summary changed:

- linux ADT test failure with linux/4.15.0-144.148 s390x (stress-misaligned.0 
failed)
+ linux ADT test failure with linux/4.15.0-144.148 i386 (stress-misaligned.0 
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/1929144

Title:
  linux ADT test failure with linux/4.15.0-144.148 i386 (stress-
  misaligned.0 failed)

Status in linux package in Ubuntu:
  Incomplete

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

  Testing failed on:
  i386: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210520_041720_4a574@/log.gz

  
  Only found on i386. Failing tests with the same output:
  ubuntu_stress_smoke_test.setup
  ubuntu_stress_smoke_test.stress-smoke-test
  ubuntu_ramfs_stress.setup
  ubuntu_ramfs_stress.ramfs-stress
  ubuntu_vfat_stress.setup
  ubuntu_vfat_stress.vfat-stress


Makefile:385: recipe for target 'stress-misaligned.o' failed
make[1]: Leaving directory 
'/tmp/autopkgtest.Y8PkHb/build.Fp9/src/autotest/client/tmp/ubuntu_ramfs_stress/src/stress-ng'
Makefile:370: recipe for target 'all' failed
stderr:
stress-aio-linux.c: In function ‘stress_aiol’:
stress-aio-linux.c:513:23: warning: large integer implicitly truncated to 
unsigned type [-Woverflow]
cb[i].u.c.nbytes = ~0ULL; /* invalid */
   ^
stress-misaligned.c:419:18: error: ‘stress_misaligned_int128atomic’ 
undeclared here (not in a function); did you mean 
‘stress_misaligned_int32atomic’?
  { "int128tomic",stress_misaligned_int128atomic, false, false },
  ^~
  stress_misaligned_int32atomic
make[1]: *** [stress-misaligned.o] Error 1
make[1]: *** Waiting for unfinished jobs
make: *** [all] Error 2

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

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

[Kernel-packages] [Bug 1829989] Re: memcg_use_hierarchy from controllers test suite in LTP failed

[Kelsey Skunberg]

** Tags added: 5.11 hirsute sru-20210510

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

Title:
  memcg_use_hierarchy from controllers test suite in LTP failed

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Confirmed
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Cosmic:
  Confirmed
Status in linux-aws source package in Cosmic:
  New

Bug description:
  startup='Wed May 22 05:59:07 2019'
  memcg_use_hierarchy_test 1 TINFO: Starting test 1
  sh: echo: I/O error
  memcg_use_hierarchy_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
  memcg_use_hierarchy_test 1 TPASS: process 31577 is killed
  memcg_use_hierarchy_test 2 TINFO: Starting test 2
  sh: echo: I/O error
  memcg_use_hierarchy_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
  memcg_use_hierarchy_test 2 TFAIL: echo 1 > memory.use_hierarchy passed 
unexpectedly
  memcg_use_hierarchy_test 3 TINFO: Starting test 3
  sh: echo: I/O error
  memcg_use_hierarchy_test 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
  memcg_use_hierarchy_test 3 TPASS: echo 0 > subgroup/memory.use_hierarchy 
failed as expected
  tag=memcg_use_hierarchy stime=1558504747 dur=1 exit=exited stat=1 core=no 
cu=5 cs=5

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [14538.862950] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed May 22 07:33:33 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1891003] Re: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed with script is not executable

[Kelsey Skunberg]

** Tags added: 5.11 hirsute sru-20210510

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

Title:
  mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests
  failed with script is not executable

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

Bug description:
  Issue found on Bionic 5.3.0-1033.35-aws

  TAP version 13
   1..1
   # selftests: memory-hotplug: mem-on-off-test.sh
   # Warning: file mem-on-off-test.sh is not executable, correct this.
   not ok 1 selftests: memory-hotplug: mem-on-off-test.sh
   make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memory-hotplug'
   make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  ubuntu_ker:0242| == Summary ===
  ubuntu_ker:0076| Sub test case: mem-on-off-test.sh failed.

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

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

[Kernel-packages] [Bug 1834006] Re: cpuset_hotplug from controllers in ubuntu_ltp failed

[Kelsey Skunberg]

** Tags added: 5.11 hirsute sru-20210510

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

Title:
  cpuset_hotplug from controllers in ubuntu_ltp failed

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-aws source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux source package in Focal:
  New
Status in linux-aws source package in Focal:
  New
Status in linux-azure source package in Focal:
  New

Bug description:
  Issue found on node amaura:
  <<>>
  tag=cpuset_hotplug stime=1561372131
  cmdline="cpuset_hotplug_test.sh"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  cpuset_hotplug 1 TFAIL: task's allowed list isn't expected.(Result: 0-15, 
Expect: 0-7)
  cpuset_hotplug 3 TFAIL: task's allowed list isn't expected.(Result: 0-15, 
Expect: 0-7)
  cpuset_hotplug 5 TPASS: Cpuset vs CPU hotplug test succeeded.
  cpuset_hotplug 7 TFAIL: task's cpu allowed list isn't expected(Result: 0-15, 
Expect: 0-7).
  cpuset_hotplug 9 TPASS: Cpuset vs CPU hotplug test succeeded.
  cpuset_hotplug 11 TPASS: Cpuset vs CPU hotplug test succeeded.
  <<>>
  initiation_status="ok"
  duration=1 termination_type=exited termination_id=1 corefile=no
  cutime=19 cstime=81
  <<>>

  Test script:
  
https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/controllers/cpuset/cpuset_hotplug_test/cpuset_hotplug_test.sh

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-22-generic 4.18.0-22.23
  ProcVersionSignature: User Name 4.18.0-22.23-generic 4.18.20
  Uname: Linux 4.18.0-22-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 24 10:25 seq
   crw-rw 1 root audio 116, 33 Jun 24 10:25 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon Jun 24 10:30:59 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Intel Corporation S1200RP
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic 
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-22-generic N/A
   linux-backports-modules-4.18.0-22-generic  N/A
   linux-firmware 1.175.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
  dmi.board.asset.tag: 
  dmi.board.name: S1200RP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G62254-407
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: S1200RP
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

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

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

[Kernel-packages] [Bug 1847982] Re: memcg_subgroup_charge from controllers in ubuntu_ltp failed on D/E/F/G

[Kelsey Skunberg]

** Tags added: 5.11 hirsute sru-20210510

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

Title:
  memcg_subgroup_charge from controllers in ubuntu_ltp failed on D/E/F/G

Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New
Status in linux-azure source package in Disco:
  Won't Fix
Status in linux-kvm source package in Disco:
  Won't Fix
Status in linux-oracle source package in Disco:
  Won't Fix

Bug description:
  Issue found on Azure Disco kernel 5.0.0-1023.24

  Failed on instance:
* Standard_GS2
* Standard_D16s_v3

  Passed on instance:
* Standard_F32s_v2
* Standard_L8s_v2
* Standard_L4s
* Standard_L8s_v2

  (Although it has passed on these instances, but they all have the same
  test output, just the pids are different)

  
  Test failed with:
    /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error

   tag=memcg_subgroup_charge stime=1570239843 dur=3 exit=exited stat=1 core=no 
cu=7 cs=11
   startup='Sat Oct 5 01:44:03 2019'
   memcg_subgroup_charge 1 TINFO: Starting test 1
   /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error
   memcg_subgroup_charge 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_subgroup_charge 1 TINFO: Running memcg_process --mmap-anon -s 135168
   memcg_subgroup_charge 1 TINFO: Warming up pid: 119041
   memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 119041
   memcg_subgroup_charge 1 TPASS: rss is 135168 as expected
   memcg_subgroup_charge 2 TPASS: rss is 0 as expected
   memcg_subgroup_charge 3 TINFO: Starting test 2
   /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error
   memcg_subgroup_charge 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_subgroup_charge 3 TINFO: Running memcg_process --mmap-anon -s 135168
   memcg_subgroup_charge 3 TINFO: Warming up pid: 119071
   memcg_subgroup_charge 3 TINFO: Process is still here after warm up: 119071
   memcg_subgroup_charge 3 TFAIL: rss is 0, 135168 expected
   memcg_subgroup_charge 4 TPASS: rss is 0 as expected
   memcg_subgroup_charge 5 TINFO: Starting test 3
   /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error
   memcg_subgroup_charge 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_subgroup_charge 5 TINFO: Running memcg_process --mmap-anon -s 135168
   memcg_subgroup_charge 5 TINFO: Warming up pid: 119094
   memcg_subgroup_charge 5 TINFO: Process is still here after warm up: 119094
   memcg_subgroup_charge 5 TPASS: rss is 135168 as expected
   memcg_subgroup_charge 6 TPASS: rss is 0 as expected

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

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

[Kernel-packages] [Bug 1829984] Re: memcg_usage_in_bytes from controllers test suite in LTP failed

[Kelsey Skunberg]

** Tags added: 5.11 hirsute sru-20210510

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

Title:
  memcg_usage_in_bytes from controllers test suite in LTP failed

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux source package in Bionic:
  Confirmed
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Cosmic:
  Confirmed
Status in linux-aws source package in Cosmic:
  New

Bug description:
   startup='Wed May 22 05:59:09 2019'
   memcg_usage_in_bytes_test 1 TINFO: Starting test 1
   sh: echo: I/O error
   memcg_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 
4194304
   memcg_usage_in_bytes_test 1 TINFO: Warming up pid: 31689
   memcg_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 31689
   memcg_usage_in_bytes_test 1 TFAIL: memory.usage_in_bytes is 4202496, 4194304 
expected
   memcg_usage_in_bytes_test 2 TINFO: Starting test 2
   sh: echo: I/O error
   memcg_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_usage_in_bytes_test 2 TCONF: mem+swap is not enabled
   tag=memcg_usage_in_bytes stime=1558504749 dur=1 exit=exited stat=33 core=no 
cu=5 cs=3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [14538.862950] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed May 22 07:17:43 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle

[Chris Chiu]

** Description changed:

  [SRU Justification]
  
  [Impact]
  All of 3 different WD19(TB/SC/DC) docks have 3 Type-A ports and 2 Type-C 
ports, and there're highspeed Hubs(0bda:5487 and its substream hub 0bda:5413) 
and Superspeed Hubs (0bda:0487 and its downstream hub 0bda:0413). In the bug 
description below, we will refer the 2 highspeed hubs as Hub A and Hub A.3, and 
the 2 superspeed hubs as Hub B and Hub B.3. All devices connected via either 
Type-A or Type-C ports will connect to either Hub A.3 or Hub B.3. If we connect 
a wakup enabled device (keyboard) to a Type-A port, the Hub A.3 will fail to 
activate after exiting s2idle and all downstream devices will not be detected. 
If we have a superspeed device connected to other Type-A port in addition to 
the keyboard, this superspeed device actually connects to Hub B.3, and the Hub 
B.3 will also fails to work after exiting s2idle. If the wakeup enabled device 
connects via Type-C port, there's no such problem.
  
  As a summary, a wakeup enabled device connect to Type-A port will cause
  the failure of Hub A.3 and Hub B.3. Hub B.3 only fails when a wakeup
  enabled device and a superspeed device both connect via Type-A port.
  
  [Fix]
  Before the resume failure, the upstream hub(Hub A or B) will hit the timeout 
problem while doing SetPortFeature(PORT_SUSPEND) to the port of the downstream 
hub (Hub A.3 or Hub B.3). However, the PORT_SUSPEND bit of the wPortStatus is 
actually turned on for the Hub A.3, we simply need to make the kernel believe 
it's already suspended. Then the ClearPortFeature will be done during resume 
and the problem will go away.
  
  The Hub B.3 will be tricky. The PORT_SUSPEND bit is not on after the
- suspend timeout, but we need to reset_resume the Hub B.3 to avoid resume
- failure. It's hard to create a generic fix for it. Because it only
- happens when timeout happens on suspending Hub A.3 and there's a
- superspeed device connecting to Type-A port. I can only reset_resume the
- problematic hub if the timeout happens during suspend and it happens to
- be a Realtek hub.
+ suspend timeout, but it needs the ClearPortFeature(PORT_SUSPEND) for Hub
+ B.3 to avoid resume failure. It doesn't comply with the USB spec so it's
+ hard to create a generic fix for it. Because it only happens when
+ timeout happens on suspending Hub A.3 and there's a superspeed device
+ connecting to Type-A port, we choose to leave it as-is and try to
+ address it in the future.
  
- [Test]
+ [Test Case]
  1. Make sure that the WD19 connects to the laptop
- 2. Connect a USB keyboard and a superspeed USB stick to USB Type-A ports.
+ 2. Connect USB keyboard/mouse to USB Type-A ports.
  3. Suspend the system
  4. Press the Enter key or power button to wake up the system
- 5. Check if the keyboard and USB stick are still working
+ 5. Check if the USB keyboard/mouse are still working
  Repeat 4 and 5 for > 10 times w/o losing any USB devices.
+ 
  
  [Where problems could occur]
  A wakeup enabled device (keyboard) connect to Type-A port will cause the 
failure of Hub A.3 and Hub B.3 during resume. Hub B.3 only fails when a wakeup 
enabled device and a superspeed device both connect via Type-A port. All 
devices connects to Hub A.3 (and B.3 if superspeed device connect via Type-A 
port) will be lost after resume.
  
  [Regression Potential]
  Minimum. The fix is only triggered when timeout happens during USB port 
suspend and it follows the standard USB protocol to do either resume or 
reset_resume.
  
  == Original Bug Description ==
  
  ● Summary
  Plug in USB mouse and USB keyboard to WD19/WD19DC USB ports near LAN port. 
Plug dock into SUT and check USB keyboard and mouse work. SUT enter suspend. 
After 1 min resume SUT, check USB keyboard/mouse function. Sometimes USB 
keyboard/mouse no function.
  
  Isolation:
  1. VP on UMA and Discrete
  2. When issue occur, both front and back port on WD19 can't work using USB 
keyboard/mouse but USB Key.
  
  ● Reproduce Steps
  1.Plug in USB mouse and USB keyboard to WD19/WD19DC USB ports near LAN port.
  2.Plug dock into SUT and check USB keyboard and mouse work.
  3. SUT enter suspend.
  4.After 1 min, resume SUT and check USB keyboard/mouse function.
  5.Sometimes USB keyboard/mouse no function.
  
  ● Results
  ○ Expected Result
  USB mouse or keyboard on dock can use after suspend
  
  ○ Actual Result
  USB mouse or keyboard on dock sometimes no function after suspend
  
  ● Additional Information
  ○ Test Vault ID：60943.011
  ○ SKU：Broadmoor Latitude5421
  ○ BIOS Version：0.3.21
  ○ Image/Manifest：
  dell-bto-focal-fossa-pidgeot-14-X79-20210106-3.iso
  dell-bto-focal-fossa-pidgeot-14-X81-20210121-6.iso
  ○ CPU：TGL ES
  ○ GPU：Intel pGFX 2020
  ○ Failure rate：F/R: 2/2 units, 1/10 times
  ○ WD19 dock, Dock DFU: 1.0.15
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  263

[Kernel-packages] [Bug 1880645] Re: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / G / H

[Kelsey Skunberg]

** Tags added: 5.11 sru-20210510

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

Title:
  icmp_redirect.sh in net from ubuntu_kernel_selftests failed on
  F-OEM-5.6 / G / H

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed-oem-5.6 package in Ubuntu:
  New
Status in linux source package in Focal:
  Invalid
Status in linux-signed-oem-5.6 source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Confirmed
Status in linux-signed-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  Issue found on Focal 5.6.0-1011.11-oem


  
ubuntu@rizzo:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$
  sudo ./icmp_redirect.sh

  ###
  Legacy routing
  ###

  TEST: IPv4: redirect exception  [ OK ]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [ OK ]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [ OK ]
  TEST: IPv6: mtu exception plus redirect [FAIL]

  ###
  Legacy routing with VRF
  ###

  TEST: IPv4: redirect exception  [ OK ]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [ OK ]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [ OK ]
  TEST: IPv6: mtu exception plus redirect [FAIL]

  ###
  Routing with nexthop objects
  ###

  TEST: IPv4: redirect exception  [ OK ]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [ OK ]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [ OK ]
  TEST: IPv6: mtu exception plus redirect [FAIL]

  ###
  Routing with nexthop objects and VRF
  ###

  TEST: IPv4: redirect exception  [ OK ]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [ OK ]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [ OK ]
  TEST: IPv6: mtu exception plus redirect [FAIL]

  Tests passed:  36
  Tests failed:   4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.6.0-1011-oem 5.6.0-1011.11
  ProcVersionSignature: User Name 5.6.0-1011.11-oem 5.6.14
  Uname: Linux 5.6.0-1011-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  

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

[chang long]

@tuxinvader is there a tutorial somewhere on how to manually replicate
your build (specifically on building dependencies)? most tuts are wildly
out of date and are not working. i'd like to install the ppa but also
learn how you did it.

-- 
You 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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed

[Trent Lloyd]

Are you confident that the issue is a new issue? Unfortunately as best I
can tell, the corruption can occur and then will still appear on a fixed
system if it's reading corruption created in the past that unfortunately
scrub doesn't seem to detect.

I've still had no re-occurance here after a few weeks on hirsute with
2.0.2-1ubuntu5 (which includes the
https://github.com/openzfs/zfs/issues/11474 fix) - but from a fresh
install.

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  &zp->z_sa_hdl)) failed

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

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

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

[Kernel-packages] [Bug 1854722] Re: mtest06 from mm in ubuntu_ltp failed on B-AWS-5.0 B-AWS-4.15

[Po-Hsu Lin]

That's awesome Thadeu,
thanks for the patch, I noticed that this has been applied upstream.
I will give this a retry on Bionic 4.15 / 4.15 FIPS AWS t2.small

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

Title:
  mtest06 from mm in ubuntu_ltp failed on B-AWS-5.0 B-AWS-4.15

Status in ubuntu-kernel-tests:
  In Progress
Status in linux-aws package in Ubuntu:
  Invalid

Bug description:
  Kernel: 5.0.0-1022.25~18.04.1

  Issue found on instance t2.small
  The test failed with ENOMEM

  
   startup='Wed Nov 20 10:40:07 2019'
   tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
   mmap1.c:205: BROK: mmap((nil),2147483648,3,34,-1,0) failed: ENOMEM (12)

   Summary:
   passed 0
   failed 0
   skipped 0
   warnings 0
   tag=mtest06 stime=1574246407 dur=0 exit=exited stat=2 core=no cu=0 cs=0

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

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

[Kernel-packages] [Bug 1591669] Re: duplicate touchpad reported and syndaemon/synclient does not work

[Joel Östblom]

This has been marked as "wontfix" upstreams
https://gitlab.freedesktop.org/xorg/driver/xf86-input-
synaptics/-/issues/5, but a workaround is mentioned to exist in that
thread.

** Bug watch added: 
gitlab.freedesktop.org/xorg/driver/xf86-input-synaptics/-/issues #5
   https://gitlab.freedesktop.org/xorg/driver/xf86-input-synaptics/-/issues/5

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

Title:
  duplicate touchpad reported and syndaemon/synclient does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is on a Dell XPS 13 9350 DE running ubuntu 16.04.
  This laptop has a touchpad and a touchscreen.
  I'm reporting here about the touchpad.

  One can see from Xorg.0.log and "xinput list" that *two* touchpads are
  registered by the system

  one is called "DLL0704:01 06CB:76AE Touchpad"
  and the other "SynPS/2 Synaptics TouchPad"

  As a result, syndaemon is not working.
  To check this, open two terminals, press and hold some key, like "e" in one 
of them. It starts filling with "eee". Now while holding the key, use the 
touchpad to tap on the other terminal. Then "" fills the new terminal.
  Expected behaviour:
  tapping on the other terminal should have no effet, the "e"'s should continue 
to fill the first terminal.

  Moreover, configuring the touchpad with synclient is not working
  either.

  FIX:

  Since invoking
  xinput disable "SynPS/2 Synaptics TouchPad"
  has no effect, it is clear that this one is a "false" touchpad.

  Hence this fix is:
  Add an "ignore" section in /usr/share/X11/xorg.conf.d/50-synaptics.conf

  I added, line 29:

  Section "InputClass"
  Identifier "touchpad ignore SynPS/2 Synaptics duplicate"
  MatchProduct "SynPS/2 Synaptics TouchPad"
  Option "Ignore" "on"
  EndSection

  Now it works. The touchpad is correctly disabled when using the
  keyboard, and moreover I can configure it using synclient, or adding a
  file to /etc/X11/xorg.conf.d/

  Of course this fix is not universal because I had to use the precise
  name of the "false touchpad" as reported by xinput.

  
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  san1697 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0dbbd1c1-bb58-45af-8c68-716d7ae636e7
  InstallationDate: Installed on 2016-06-03 (9 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia
   Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp.
   Bus 001 Device 002: ID 8087:0a2b Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed 
root=UUID=75dd5fb6-2ff1-4f2b-859d-4c3942a5c45b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-24-generic N/A
   linux-backports-modules-4.4.0-24-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.name: 09JHRY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1929114] Re: Resolução da minha tela.

[Daniel van Vugt]

Thanks for the bug report. It appears the answer is in your kernel log:

[   25.771227] NVRM: The NVIDIA NVS 3100M GPU installed in this system is
   NVRM:  supported through the NVIDIA 340.xx Legacy drivers. Please
   NVRM:  visit http://www.nvidia.com/object/unix.html for more
   NVRM:  information.  The 460.80 NVIDIA driver will ignore
   NVRM:  this GPU.  Continuing probe...

You have installed the wrong driver. Your system needs the version 340
Nvidia driver.

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

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

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

Title:
  Resolução da minha tela.

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

Bug description:
  Minha tela não volta para a rsolução nativa só da pra usar no 480 X
  620, o que é horrível.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-73.82~18.04.1-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 20 13:55:23 2021
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 460.80, 5.4.0-73-generic, x86_64: installed
   virtualbox, 5.2.42, 5.4.0-72-generic, x86_64: installed
   virtualbox, 5.2.42, 5.4.0-73-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo ThinkPad T410 [17aa:2142]
  InstallationDate: Installed on 2020-05-06 (379 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip 
Fingerprint Sensor
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 2537GC0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic 
root=UUID=4e34df45-65c4-4324-b2d9-8e3eb8d18fff ro quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 10/25/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET74WW (1.34 )
  dmi.board.name: 2537GC0
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET74WW(1.34):bd10/25/2010:svnLENOVO:pn2537GC0:pvrThinkPadT410:rvnLENOVO:rn2537GC0:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T410
  dmi.product.name: 2537GC0
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Kernel-packages] [Bug 1929114] [NEW] Resolução da minha tela.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Minha tela não volta para a rsolução nativa só da pra usar no 480 X 620,
o que é horrível.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xserver-xorg (not installed)
ProcVersionSignature: Ubuntu 5.4.0-73.82~18.04.1-generic 5.4.106
Uname: Linux 5.4.0-73-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu May 20 13:55:23 2021
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 460.80, 5.4.0-73-generic, x86_64: installed
 virtualbox, 5.2.42, 5.4.0-72-generic, x86_64: installed
 virtualbox, 5.2.42, 5.4.0-73-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo ThinkPad T410 [17aa:2142]
InstallationDate: Installed on 2020-05-06 (379 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
Lsusb:
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip 
Fingerprint Sensor
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 2537GC0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic 
root=UUID=4e34df45-65c4-4324-b2d9-8e3eb8d18fff ro quiet
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLogOld:
 
dmi.bios.date: 10/25/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6IET74WW (1.34 )
dmi.board.name: 2537GC0
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr6IET74WW(1.34):bd10/25/2010:svnLENOVO:pn2537GC0:pvrThinkPadT410:rvnLENOVO:rn2537GC0:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T410
dmi.product.name: 2537GC0
dmi.product.version: ThinkPad T410
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic ubuntu
-- 
Resolução da minha tela.
https://bugs.launchpad.net/bugs/1929114
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 1929147] Re: fix system hang with 5.10 kernel + RX540 on RKL platform

[koba]

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

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

** Changed in: linux-firmware (Ubuntu Hirsute)
 Assignee: (unassigned) => koba (kobako)

** Tags added: oem-priority originate-from-1908483 somerville

-- 
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:
  New
Status in linux-firmware source package in Focal:
  In Progress
Status in linux-firmware source package in Hirsute:
  In Progress

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 1929147] [NEW] fix system hang with 5.10 kernel + RX540 on RKL platform

[koba]

Public bug reported:

[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.

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

** Affects: linux-firmware (Ubuntu Focal)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress

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

** Changed in: linux-oem-5.10 (Ubuntu Focal)
 Assignee: (unassigned) => koba (kobako)

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

** No longer affects: linux-oem-5.10 (Ubuntu)

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

** Changed in: linux-firmware (Ubuntu Focal)
 Assignee: (unassigned) => koba (kobako)

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

** No longer affects: linux-oem-5.10 (Ubuntu 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/1929147

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

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Focal:
  In Progress

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/ubuntu/+source/linux-firmware/+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 1926030] Re: IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49

[Kelsey Skunberg]

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

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

Title:
  IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49

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

Bug description:
  [Impact]
  Patch:
* media: rc: fix timeout handling after switch to microsecond durations
* media: rc: ite-cir: fix min_timeout calculation

  Were applied to Groovy with our stable update process (bug 1918516)

  User reported that IR Remote key press will be repeated for multiple times
  with these patches applied.

  Commit 528222d853f92 ("media: rc: harmonize infrared durations to
  microseconds") that needs to be fixed by these two does not exist in
  5.8 kernel. The patch author Matthias Reichl also state these are for
  5.10 and onward.

  [Fix]
  Revert these two patches for groovy.

  [Test]
  Test kernels for G-5.8 / F-5.8 can be found here:
  https://people.canonical.com/~phlin/kernel/lp-1926030-revert-for-ir/

  User Ted L confirmed that F-5.8 test kernel can fix the problem.

  [Where problems could occur]
  The chance to cause regression can be considered as low since the original 
patch that need to be fix by these two patches does not exist in 5.8 at all. 

  
  [Original Bug Report]
  I use an IR remote with the ir-keytable package.  Everything was working fine 
until kernel 5.8.0-49 was automatically installed by Software Updater on Ubuntu 
20.04.2.  When any key is pressed on the remote, the key is repeated about 500 
times.  The kernel is now 5.8.0-50, and the problem persists.

  Other users on the MythTV mailing list are reporting the issue, and it
  appears that the problem is related to changes in the following files:

  drivers/media/rc/ir-mce_kbd-decoder.c
  drivers/media/rc/rc-main.c b/drivers/media/rc/rc-main.c
  drivers/media/rc/serial_ir.c

  It has been reported that reverting the ir-mce_kbd-decoder.c and rc-
  main.c files to the older versions fixes the problem.

  /proc/version_signature > version.log:
  Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18

  lspci -vnvn:
  00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:590f] (rev 06)
   Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host 
Bridge/DRAM Registers [1043:8694]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: skl_uncore

  ir-keytable -V:
  IR keytable control version 1.18.0

  lsb_release -rd:
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ted1020 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-09-19 (217 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   lono wireless extensions.

   enp3s0no wireless extensions.

   enp0s31f6  no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic 
root=UUID=529cae8e-19cd-4732-80d5-b3dca123afc6 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-50-generic N/A
   linux-backports-modules-5.8.0-50-generic  N/A
   linux-firmware1.187.11
  RfKill:

  Tags:  focal
  Uname: Linux 5.8.0-50-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd mythtv plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3405
  dmi.board.asset.tag: Default string
  dmi.board.name: H110T
  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: 
dmi:bvnAmericanMegatrendsInc.:bvr3405:bd07/05/2017:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110T:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.pr

[Kernel-packages] [Bug 1929132] Re: Groovy update: upstream stable patchset 2021-05-20

[Kelsey Skunberg]

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

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

Title:
  Groovy update: upstream stable patchset 2021-05-20

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Groovy:
  Fix Committed

Bug description:
  SRU Justification

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

     upstream stable patchset 2021-05-20

  Ported from the following upstream stable releases:
  v5.4.114, v5.10.32
  v5.4.115, v5.10.33
  v5.4.116, v5.10.34
  v5.4.117, v5.10.35

     from git://git.kernel.org/

  Input: nspire-keypad - enable interrupts only when opened
  gpio: sysfs: Obey valid_mask
  dmaengine: idxd: Fix clobbering of SWERR overflow bit on writeback
  dmaengine: idxd: fix delta_rec and crc size field for completion record
  dmaengine: idxd: fix opcap sysfs attribute output
  dmaengine: idxd: fix wq size store permission state
  dmaengine: dw: Make it dependent to HAS_IOMEM
  dmaengine: Fix a double free in dma_async_device_register
  dmaengine: plx_dma: add a missing put_device() on error path
  ACPI: x86: Call acpi_boot_table_init() after acpi_table_upgrade()
  ARM: dts: Drop duplicate sha2md5_fck to fix clk_disable race
  ARM: dts: Fix moving mmc devices with aliases for omap4 & 5
  lockdep: Add a missing initialization hint to the "INFO: Trying to register 
non-static key" message
  arc: kernel: Return -EFAULT if copy_to_user() fails
  iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_enqueue_hcmd()
  xfrm: BEET mode doesn't support fragments for inner packets
  ASoC: max98373: Added 30ms turn on/off time delay
  gpu/xen: Fix a use after free in xen_drm_drv_init
  neighbour: Disregard DEAD dst in neigh_update
  ARM: keystone: fix integer overflow warning
  ARM: omap1: fix building with clang IAS
  drm/msm: Fix a5xx/a6xx timestamps
  ASoC: fsl_esai: Fix TDM slot setup for I2S mode
  scsi: scsi_transport_srp: Don't block target in SRP_PORT_LOST state
  iwlwifi: add support for Qu with AX201 device
  net: ieee802154: stop dump llsec keys for monitors
  net: ieee802154: forbid monitor for add llsec key
  net: ieee802154: forbid monitor for del llsec key
  net: ieee802154: stop dump llsec devs for monitors
  net: ieee802154: forbid monitor for add llsec dev
  net: ieee802154: forbid monitor for del llsec dev
  net: ieee802154: stop dump llsec devkeys for monitors
  net: ieee802154: forbid monitor for add llsec devkey
  net: ieee802154: forbid monitor for del llsec devkey
  net: ieee802154: stop dump llsec seclevels for monitors
  net: ieee802154: forbid monitor for add llsec seclevel
  pcnet32: Use pci_resource_len to validate PCI resource
  mac80211: clear sta->fast_rx when STA removed from 4-addr VLAN
  virt_wifi: Return micros for BSS TSF values
  lib: fix kconfig dependency on ARCH_WANT_FRAME_POINTERS
  Input: s6sy761 - fix coordinate read bit shift
  Input: i8042 - fix Pegatron C15B ID entry
  HID: wacom: set EV_KEY and EV_ABS only for non-HID_GENERIC type of devices
  dm verity fec: fix misaligned RS roots IO
  readdir: make sure to verify directory entry for legacy interfaces too
  arm64: fix inline asm in load_unaligned_zeropad()
  arm64: alternatives: Move length validation in alternative_{insn, endif}
  vfio/pci: Add missing range check in vfio_pci_mmap
  riscv: Fix spelling mistake "SPARSEMEM" to "SPARSMEM"
  scsi: libsas: Reset num_scatter if libata marks qc as NODATA
  netfilter: flowtable: fix NAT IPv6 offload mangling
  netfilter: conntrack: do not print icmpv6 as unknown via /proc
  ice: Fix potential infinite loop when using u8 loop counter
  libnvdimm/region: Fix nvdimm_has_flush() to handle ND_REGION_ASYNC
  netfilter: bridge: add pre_exit hooks for ebtable unregistration
  netfilter: arp_tables: add pre_exit hook for table unregister
  net: macb: fix the restore of cmp registers
  net/mlx5e: fix ingress_ifindex check in mlx5e_flower_parse_meta
  netfilter: nft_limit: avoid possible divide error in nft_limit_init
  net/mlx5e: Fix setting of RS FEC mode
  net: davicom: Fix regulator not turned off on failed probe
  net: sit: Unregister catch-all devices
  net: ip6_tunnel: Unregister catch-all devices
  mm: ptdump: fix build failure
  net: Make tcp_allowed_congestion_control readonly in non-init netns
  i40e: fix the panic when running bpf in xdpdrv mode
  ia64: remove duplica

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

[Ubuntu Kernel Bot]

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

apport-collect 1929144

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

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

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

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

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

Title:
  linux ADT test failure with linux/4.15.0-144.148 s390x (stress-
  misaligned.0 failed)

Status in linux package in Ubuntu:
  Incomplete

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

  Testing failed on:
  i386: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210520_041720_4a574@/log.gz

  
  Only found on i386. Failing tests with the same output:
  ubuntu_stress_smoke_test.setup
  ubuntu_stress_smoke_test.stress-smoke-test
  ubuntu_ramfs_stress.setup
  ubuntu_ramfs_stress.ramfs-stress
  ubuntu_vfat_stress.setup
  ubuntu_vfat_stress.vfat-stress


Makefile:385: recipe for target 'stress-misaligned.o' failed
make[1]: Leaving directory 
'/tmp/autopkgtest.Y8PkHb/build.Fp9/src/autotest/client/tmp/ubuntu_ramfs_stress/src/stress-ng'
Makefile:370: recipe for target 'all' failed
stderr:
stress-aio-linux.c: In function ‘stress_aiol’:
stress-aio-linux.c:513:23: warning: large integer implicitly truncated to 
unsigned type [-Woverflow]
cb[i].u.c.nbytes = ~0ULL; /* invalid */
   ^
stress-misaligned.c:419:18: error: ‘stress_misaligned_int128atomic’ 
undeclared here (not in a function); did you mean 
‘stress_misaligned_int32atomic’?
  { "int128tomic",stress_misaligned_int128atomic, false, false },
  ^~
  stress_misaligned_int32atomic
make[1]: *** [stress-misaligned.o] Error 1
make[1]: *** Waiting for unfinished jobs
make: *** [all] Error 2

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

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

[Kernel-packages] [Bug 1929144] [NEW] linux ADT test failure with linux/4.15.0-144.148 s390x (stress-misaligned.0 failed)

[Kelsey Skunberg]

Public bug reported:

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

Testing failed on:
i386: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210520_041720_4a574@/log.gz


Only found on i386. Failing tests with the same output:
ubuntu_stress_smoke_test.setup
ubuntu_stress_smoke_test.stress-smoke-test
ubuntu_ramfs_stress.setup
ubuntu_ramfs_stress.ramfs-stress
ubuntu_vfat_stress.setup
ubuntu_vfat_stress.vfat-stress


  Makefile:385: recipe for target 'stress-misaligned.o' failed
  make[1]: Leaving directory 
'/tmp/autopkgtest.Y8PkHb/build.Fp9/src/autotest/client/tmp/ubuntu_ramfs_stress/src/stress-ng'
  Makefile:370: recipe for target 'all' failed
  stderr:
  stress-aio-linux.c: In function ‘stress_aiol’:
  stress-aio-linux.c:513:23: warning: large integer implicitly truncated to 
unsigned type [-Woverflow]
  cb[i].u.c.nbytes = ~0ULL; /* invalid */
 ^
  stress-misaligned.c:419:18: error: ‘stress_misaligned_int128atomic’ 
undeclared here (not in a function); did you mean 
‘stress_misaligned_int32atomic’?
{ "int128tomic",stress_misaligned_int128atomic, false, false },
^~
stress_misaligned_int32atomic
  make[1]: *** [stress-misaligned.o] Error 1
  make[1]: *** Waiting for unfinished jobs
  make: *** [all] Error 2

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


** Tags: bionic kernel-adt-failure

** Tags added: kernel-adt-failure

** Summary changed:

- linux ADT test failure with linux/4.15.0-144.148
+ linux ADT test failure with linux/4.15.0-144.148 s390x (stress-misaligned.0 
failed)

** Tags added: bionic

** Description changed:

  This is a scripted bug report about ADT failures while running linux
  tests for linux/4.15.0-144.148 on bionic. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be determined.
  
  Testing failed on:
- arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/l/linux/20210520_203109_c64e0@/log.gz
- i386: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210520_041720_4a574@/log.gz
+ i386: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210520_041720_4a574@/log.gz
+ 
+ 
+ Only found on i386. Failing tests with the same output:
+ ubuntu_stress_smoke_test.setup
+ ubuntu_stress_smoke_test.stress-smoke-test
+ ubuntu_ramfs_stress.setup
+ ubuntu_ramfs_stress.ramfs-stress
+ ubuntu_vfat_stress.setup
+ ubuntu_vfat_stress.vfat-stress
+ 
+ 
+   Makefile:385: recipe for target 'stress-misaligned.o' failed
+   make[1]: Leaving directory 
'/tmp/autopkgtest.Y8PkHb/build.Fp9/src/autotest/client/tmp/ubuntu_ramfs_stress/src/stress-ng'
+   Makefile:370: recipe for target 'all' failed
+   stderr:
+   stress-aio-linux.c: In function ‘stress_aiol’:
+   stress-aio-linux.c:513:23: warning: large integer implicitly truncated to 
unsigned type [-Woverflow]
+   cb[i].u.c.nbytes = ~0ULL; /* invalid */
+  ^
+   stress-misaligned.c:419:18: error: ‘stress_misaligned_int128atomic’ 
undeclared here (not in a function); did you mean 
‘stress_misaligned_int32atomic’?
+ { "int128tomic",stress_misaligned_int128atomic, false, false },
+ ^~
+ stress_misaligned_int32atomic
+   make[1]: *** [stress-misaligned.o] Error 1
+   make[1]: *** Waiting for unfinished jobs
+   make: *** [all] Error 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/1929144

Title:
  linux ADT test failure with linux/4.15.0-144.148 s390x (stress-
  misaligned.0 failed)

Status in linux package in Ubuntu:
  Incomplete

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

  Testing failed on:
  i386: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210520_041720_4a574@/log.gz

  
  Only found on i386. Failing tests with the same output:
  ubuntu_stress_smoke_test.setup
  ubuntu_stress_smoke_test.stress-smoke-test
  ubuntu_ramfs_stress.setup
  ubuntu_ramfs_stress.ramfs-stress
  ubuntu_vfat_stress.setup
  ubuntu_vfat_stress.vfat-stress


Makefile:385: recipe for target 'stress-misaligned.o' failed
make[1]: Leaving directory 
'/tmp/autopkgtest.Y8PkHb/build.Fp9/src/autotest/client/tmp/ubuntu_ramfs_stress/src/stress-ng'
Makefile:370: recipe for target 'all' failed
stderr:
stress-aio-linux.c: In function ‘stress_aiol’:
stress-aio-lin

[Kernel-packages] [Bug 1925522] Please test proposed package

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted libnvidia-nscq-460 into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/libnvidia-
nscq-460/460.73.01-0ubuntu0.20.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Also affects: libnvidia-nscq-460 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libnvidia-nscq-450 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libnvidia-nscq-450 (Ubuntu Focal)
   Status: New => Fix Committed

-- 
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-driver

[Kernel-packages] [Bug 1925522] Please test proposed package

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted libnvidia-nscq-450 into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/libnvidia-
nscq-450/450.119.04-0ubuntu0.20.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: fabric-manager-460 (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: fabric-manager-450 (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: libnvidia-nscq-450 (Ubuntu)
   Status: New => Fix Released

** Changed in: libnvidia-nscq-460 (Ubuntu)
   Status: New => Fix Released

** Changed in: libnvidia-nscq-450 (Ubuntu Groovy)
   Status: New => Fix Committed

** Changed in: libnvidia-nscq-450 (Ubuntu Hirsute)
   Status: New => Fix Committed

** Changed in: libnvidia-nscq-460 (Ubuntu Hirsute)
   Status: New => Fix Committed

** Changed in: libnvidia-nscq-460 (Ubuntu Groovy)
   Status: New => Fix Committed

** Changed in: libnvidia-nscq-460 (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: libnvidia-nscq-460 (Ubuntu Bionic)
   Status: New => Fix Committed

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

[Kernel-packages] [Bug 1925522] Please test proposed package

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted libnvidia-nscq-460 into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/libnvidia-
nscq-460/460.73.01-0ubuntu0.18.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: libnvidia-nscq-450 (Ubuntu Bionic)
   Status: New => Fix Committed

-- 
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 s

[Kernel-packages] [Bug 1925522] Please test proposed package

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted libnvidia-nscq-450 into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/libnvidia-
nscq-450/450.119.04-0ubuntu0.18.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

[Kernel-packages] [Bug 1925522] Please test proposed package

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted libnvidia-nscq-460 into groovy-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/libnvidia-
nscq-460/460.73.01-0ubuntu0.20.10.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

[Kernel-packages] [Bug 1925522] Please test proposed package

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted libnvidia-nscq-450 into groovy-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/libnvidia-
nscq-450/450.119.04-0ubuntu0.20.10.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

[Kernel-packages] [Bug 1925522] Please test proposed package

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted libnvidia-nscq-450 into hirsute-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/libnvidia-nscq-450/450.119.04-0ubuntu0.21.04.1 in a few hours, and then
in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

[Kernel-packages] [Bug 1925522] Please test proposed package

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted libnvidia-nscq-460 into hirsute-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/libnvidia-nscq-460/460.73.01-0ubuntu0.21.04.1 in a few hours, and then
in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
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 Committed
Status in fabric-manager-460 package in Ubuntu:
  Fix Committed
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 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 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 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 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’ unti

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

[Jim Cline]

Hi Alex,
unfortunately that bug has come back.  It just took longer to manifest 
itself after booting.  It also affects recognition of the power state and 
the brightness buttons, which I hadn't noticed before.  --Jim

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

Title:
  acpi event detection crashes

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

Bug description:
  = SRU Justification =

  [Impact]

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

  [Fix]

  Upstream commit 03e9a0e05739cf reworks ec_install_handlers to avoid
  initialisation failures.

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

  [Test]

  Tested with Lenovo ThinkPad X1 Carbon Gen 8

  [Regression Potential]

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

  = Original Bug Report =

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

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

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

[Gerald Gilbert-Thorple]

damn, wrong again, the patched kernel has just displayed the bug.
no fixed!

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

Title:
  acpi event detection crashes

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

Bug description:
  = SRU Justification =

  [Impact]

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

  [Fix]

  Upstream commit 03e9a0e05739cf reworks ec_install_handlers to avoid
  initialisation failures.

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

  [Test]

  Tested with Lenovo ThinkPad X1 Carbon Gen 8

  [Regression Potential]

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

  = Original Bug Report =

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

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

[Kernel-packages] [Bug 1929132] [NEW] Groovy update: upstream stable patchset 2021-05-20

[Kamal Mostafa]

Public bug reported:

SRU Justification

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

   upstream stable patchset 2021-05-20

Ported from the following upstream stable releases:
v5.4.114, v5.10.32
v5.4.115, v5.10.33
v5.4.116, v5.10.34
v5.4.117, v5.10.35

   from git://git.kernel.org/

Input: nspire-keypad - enable interrupts only when opened
gpio: sysfs: Obey valid_mask
dmaengine: idxd: Fix clobbering of SWERR overflow bit on writeback
dmaengine: idxd: fix delta_rec and crc size field for completion record
dmaengine: idxd: fix opcap sysfs attribute output
dmaengine: idxd: fix wq size store permission state
dmaengine: dw: Make it dependent to HAS_IOMEM
dmaengine: Fix a double free in dma_async_device_register
dmaengine: plx_dma: add a missing put_device() on error path
ACPI: x86: Call acpi_boot_table_init() after acpi_table_upgrade()
ARM: dts: Drop duplicate sha2md5_fck to fix clk_disable race
ARM: dts: Fix moving mmc devices with aliases for omap4 & 5
lockdep: Add a missing initialization hint to the "INFO: Trying to register 
non-static key" message
arc: kernel: Return -EFAULT if copy_to_user() fails
iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_enqueue_hcmd()
xfrm: BEET mode doesn't support fragments for inner packets
ASoC: max98373: Added 30ms turn on/off time delay
gpu/xen: Fix a use after free in xen_drm_drv_init
neighbour: Disregard DEAD dst in neigh_update
ARM: keystone: fix integer overflow warning
ARM: omap1: fix building with clang IAS
drm/msm: Fix a5xx/a6xx timestamps
ASoC: fsl_esai: Fix TDM slot setup for I2S mode
scsi: scsi_transport_srp: Don't block target in SRP_PORT_LOST state
iwlwifi: add support for Qu with AX201 device
net: ieee802154: stop dump llsec keys for monitors
net: ieee802154: forbid monitor for add llsec key
net: ieee802154: forbid monitor for del llsec key
net: ieee802154: stop dump llsec devs for monitors
net: ieee802154: forbid monitor for add llsec dev
net: ieee802154: forbid monitor for del llsec dev
net: ieee802154: stop dump llsec devkeys for monitors
net: ieee802154: forbid monitor for add llsec devkey
net: ieee802154: forbid monitor for del llsec devkey
net: ieee802154: stop dump llsec seclevels for monitors
net: ieee802154: forbid monitor for add llsec seclevel
pcnet32: Use pci_resource_len to validate PCI resource
mac80211: clear sta->fast_rx when STA removed from 4-addr VLAN
virt_wifi: Return micros for BSS TSF values
lib: fix kconfig dependency on ARCH_WANT_FRAME_POINTERS
Input: s6sy761 - fix coordinate read bit shift
Input: i8042 - fix Pegatron C15B ID entry
HID: wacom: set EV_KEY and EV_ABS only for non-HID_GENERIC type of devices
dm verity fec: fix misaligned RS roots IO
readdir: make sure to verify directory entry for legacy interfaces too
arm64: fix inline asm in load_unaligned_zeropad()
arm64: alternatives: Move length validation in alternative_{insn, endif}
vfio/pci: Add missing range check in vfio_pci_mmap
riscv: Fix spelling mistake "SPARSEMEM" to "SPARSMEM"
scsi: libsas: Reset num_scatter if libata marks qc as NODATA
netfilter: flowtable: fix NAT IPv6 offload mangling
netfilter: conntrack: do not print icmpv6 as unknown via /proc
ice: Fix potential infinite loop when using u8 loop counter
libnvdimm/region: Fix nvdimm_has_flush() to handle ND_REGION_ASYNC
netfilter: bridge: add pre_exit hooks for ebtable unregistration
netfilter: arp_tables: add pre_exit hook for table unregister
net: macb: fix the restore of cmp registers
net/mlx5e: fix ingress_ifindex check in mlx5e_flower_parse_meta
netfilter: nft_limit: avoid possible divide error in nft_limit_init
net/mlx5e: Fix setting of RS FEC mode
net: davicom: Fix regulator not turned off on failed probe
net: sit: Unregister catch-all devices
net: ip6_tunnel: Unregister catch-all devices
mm: ptdump: fix build failure
net: Make tcp_allowed_congestion_control readonly in non-init netns
i40e: fix the panic when running bpf in xdpdrv mode
ia64: remove duplicate entries in generic_defconfig
ia64: tools: remove inclusion of ia64-specific version of errno.h header
ibmvnic: avoid calling napi_disable() twice
ibmvnic: remove duplicate napi_schedule call in do_reset function
ibmvnic: remove duplicate napi_schedule call in open function
gro: ensure frag0 meets IP header alignment
ARM: OMAP2+: Fix warning for omap_init_time_of()
ARM: footbridge: fix PCI interrupt mapping
ARM: OMAP2+: Fix uninitialized sr_inst
arm64: dts: allwinner: Fix SD card CD GPIO for SOPine systems
arm64: dts: allwinner: h6: beelink-gs1: Remove ext. 32 kH

[Kernel-packages] [Bug 1875577] Re: Encrypted swap won't load on 20.04 with zfs root

[Dan Streetman]

@halves could you take a look at this?

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

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

Title:
  Encrypted swap won't load on 20.04 with zfs root

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Focal:
  New

Bug description:
  root@eu1:/var/log# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  Codename: focal

  root@eu1:/var/log# apt-cache policy cryptsetup
  cryptsetup:
Installed: (none)
Candidate: 2:2.2.2-3ubuntu2
Version table:
   2:2.2.2-3ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  OTHER BACKGROUND INFO:
  ==

  1. machine has 2 drives. each drive is partitioned into 2 partitions,
  zfs and swap

  
  2. Ubuntu 20.04 installed on ZFS root using debootstrap 
(debootstrap_1.0.118ubuntu1_all)

  
  3. The ZFS root pool is a 2 partition mirror (the first partition of each 
disk)

  
  4. /etc/crypttab is set up as follows:

  swap  
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2
/dev/urandom   swap,cipher=aes-xts-plain64,size=256
  swap  
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802933-part2
/dev/urandom   swap,cipher=aes-xts-plain64,size=256


  
  WHAT I EXPECTED
  ===

  I expected machine would reboot and have encrypted swap that used two
  devices under /dev/mapper


  WHAT HAPPENED INSTEAD
  =

  
  On reboot, swap setup fails with the following messages in /var/log/syslog:

  Apr 28 17:13:01 eu1 kernel: [5.360793] systemd[1]: cryptsetup.target: 
Found ordering cycle on systemd-cryptsetup@swap.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360795] systemd[1]: cryptsetup.target: 
Found dependency on systemd-random-seed.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360796] systemd[1]: cryptsetup.target: 
Found dependency on zfs-mount.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360797] systemd[1]: cryptsetup.target: 
Found dependency on zfs-load-module.service/start
  Apr 28 17:13:01 eu1 kernel: [5.360798] systemd[1]: cryptsetup.target: 
Found dependency on cryptsetup.target/start
  Apr 28 17:13:01 eu1 kernel: [5.360799] systemd[1]: cryptsetup.target: Job 
systemd-cryptsetup@swap.service/start deleted to break ordering cycle starting 
with cryptsetup.target/start
  . . . . . .
  Apr 28 17:13:01 eu1 kernel: [5.361082] systemd[1]: Unnecessary job for 
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2 was removed

  
  Also, /dev/mapper does not contain any swap devices:

  root@eu1:/var/log# ls -l /dev/mapper
  total 0
  crw--- 1 root root 10, 236 Apr 28 17:13 control
  root@eu1:/var/log#

  
  And top shows no swap:

  MiB Swap:  0.0 total,  0.0 free,  0.0 used.  63153.6 avail
  Mem

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Jorge Gustavo]

I was able to install 5.12.4 using @tuxinvader ppa on 20.04 with current
libc6 2.31. Great work @tuxinvader!

I have used:

sudo add-apt-repository ppa:tuxinvader/lts-mainline
sudo apt install linux-image-unsigned-5.12.4-051204-generic 
linux-modules-5.12.4-051204-generic linux-headers-5.12.4-051204-generic

-- 
You 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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Birender Singh]

Sorry @~gavin.lin, by mistake marked released.
Please fix it at youe end.

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

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

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

[Gerald Gilbert-Thorple]

sorry, I retract that.  The problem is that ubuntu updated my kernel without my 
knowledge,
replacing the correctly patched kernel with the broken one (that both have the 
same numbers!)
It would be nice if the patch got incorporated into the distro to save me and 
others from this headache!  

I have since noticed that no only is hibernation screwed up by this bug, but 
also detection of 
the power supply and the brightness buttons.

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

Title:
  acpi event detection crashes

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

Bug description:
  = SRU Justification =

  [Impact]

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

  [Fix]

  Upstream commit 03e9a0e05739cf reworks ec_install_handlers to avoid
  initialisation failures.

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

  [Test]

  Tested with Lenovo ThinkPad X1 Carbon Gen 8

  [Regression Potential]

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

  = Original Bug Report =

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

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

[Kernel-packages] [Bug 1913933] Re: System freeze while dbus-daemon execution

[ch shr]

Hey, I just wanted to say the issue reappears again. Not on a regular
basis, quite random. I am trying to figure out, when it occurs and if
it's a hardware issue.

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

Title:
  System freeze while dbus-daemon execution

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I regularly get my system frozen while using. It does not occur on any
  user interaction I do periodically, so I checked the log files last
  time it happened:

  These are the last 3 kernel log entries before the freeze:

  Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
  Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  So I think this is related to the dbus-daemon.

  If you need any more information, please let me know so I can provide
  them.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: dbus 1.12.20-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Jan 31 09:22:49 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chshr  2241 F pulseaudio
   /dev/snd/controlC0:  chshr  2241 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52
  MachineType: Micro-Star International Co., Ltd MS-7A34
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: yes
    Hard bloc

[Kernel-packages] [Bug 1910965] Re: riscv: backport support for SiFive Unmatched

[William Wilson]

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => William Wilson (jawn-smith)

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

Title:
  riscv: backport support for SiFive Unmatched

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

Bug description:
  == SRU Justifcation Groovy/RISCV ==

  The SiFive HiFive Unmatched board should be supported as well as the current 
Unleashed. There are various upstream commits for this support and some misc 
fixes for the Unleashed and Unmatched that are required for this
  board support.

  == The fix(es) ==

  The following changes since commit
  7295e646e91b648b7f45b4f36eba14bfe59dd3f6:

UBUNTU: Ubuntu-riscv-5.8.0-13.15 (2020-12-15 10:33:23 +0100)

  are available in the Git repository at:

https://git.launchpad.net/~colin-king/+git/ubuntu-riscv-groovy

  for you to fetch changes up to
  86de0730500269fee8b71fcb1be29193455c3be7:

UBUNTU: [Config] Align configs with Unleashed defconfigs (2021-01-11
  09:37:13 +)

  
  Colin Ian King (1):
UBUNTU: [Config] Align configs with Unleashed defconfigs

  David Abdurachmanov (5):
PCI: microsemi: Add host driver for Microsemi PCIe controller
Microsemi PCIe expansion board DT entry.
HACK: Revert "of/device: Really only set bus DMA mask when appropriate"
SiFive Unleashed CPUFreq
SiFive HiFive Unleashed: Add PWM LEDs (D1, D2, D3, D4)

  Greentime Hu (2):
irqchip/sifive-plic: Fix broken irq_set_affinity() callback
irqchip/sifive-plic: Fix getting wrong chip_data when interrupt is 
hierarchy

  Pragnesh Patel (1):
clk: sifive: Add clock enable and disable ops

  Rob Herring (2):
dt-bindings: More whitespace clean-ups in schema files
dt-bindings: Explicitly allow additional properties in board/SoC schemas

  Sagar Kadam (2):
dt-bindings: riscv: sifive-l2-cache: convert bindings to json-schema
dt-bindings: riscv: convert pwm bindings to json-schema

  Sagar Shrikant Kadam (1):
i2c: ocores: fix polling mode workaround on FU540-C000 SoC

  Yash Shah (6):
RISC-V: Update l2 cache DT documentation to add support for SiFive FU740
RISC-V: sifive_l2_cache: Update L2 cache driver to support SiFive FU740
dt-bindings: riscv: Update DT binding docs to support SiFive FU740 SoC
riscv: dts: add initial support for the SiFive FU740-C000 SoC
dt-bindings: riscv: Update YAML doc to support SiFive HiFive Unmatched 
board
riscv: dts: add initial board data for the SiFive HiFive Unmatched

  Zong Li (5):
clk: sifive: Extract prci core to common base
clk: sifive: Use common name for prci configuration
clk: sifive: Add a driver for the SiFive FU740 PRCI IP block
clk: sifive: Fix the wrong bit field shift
dt-bindings: fu740: prci: add YAML documentation for the FU740 PRCI

   Documentation/devicetree/bindings/clock/sifive/fu740-prci.yaml |  60 
   Documentation/devicetree/bindings/gpio/sifive,gpio.yaml|   4 +-
   Documentation/devicetree/bindings/i2c/i2c-ocores.txt   |   6 +-
   Documentation/devicetree/bindings/pwm/pwm-sifive.txt   |  33 ---
   Documentation/devicetree/bindings/pwm/pwm-sifive.yaml  |  72 +
   Documentation/devicetree/bindings/riscv/cpus.yaml  |   6 +
   Documentation/devicetree/bindings/riscv/sifive-l2-cache.txt|  51 
   Documentation/devicetree/bindings/riscv/sifive-l2-cache.yaml   | 127 
+
   Documentation/devicetree/bindings/riscv/sifive.yaml|  20 +-
   Documentation/devicetree/bindings/serial/sifive-serial.yaml|   4 +-
   Documentation/devicetree/bindings/spi/spi-sifive.yaml  |  10 +-
   arch/riscv/Kconfig |   8 +
   arch/riscv/Kconfig.socs|   2 +-
   arch/riscv/boot/dts/sifive/Makefile|   3 +-
   arch/riscv/boot/dts/sifive/fu540-c000.dtsi |   5 +
   arch/riscv/boot/dts/sifive/fu740-c000.dtsi | 293 
+++
   arch/riscv/boot/dts/sifive/hifive-unleashed-a00-microsemi.dts  |  28 ++
   arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dts|  66 +
   arch/riscv/boot/dts/sifive/hifive-unmatched-a00.dts| 253 
+
   arch/riscv/configs/defconfig   |   5 +
   debian.riscv/config/annotations|  17 +-
   debian.riscv/config/config.common.ubuntu   |  47 +--
   drivers/clk/sifive/Kconfig   

[Kernel-packages] [Bug 1925522] Please test proposed package

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted fabric-manager-450 into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/fabric-
manager-450/450.119.04-0ubuntu0.18.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
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 Committed
Status in fabric-manager-460 package in Ubuntu:
  Fix Committed
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 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 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 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 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 

[Kernel-packages] [Bug 1925522] Please test proposed package

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted fabric-manager-460 into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/fabric-
manager-460/460.73.01-0ubuntu0.20.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: fabric-manager-460 (Ubuntu Bionic)
   Status: New => Fix Committed

-- 
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 Committed
Status in fabric-manager-460 package in Ubuntu:
  Fix Committed
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 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 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 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 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 t

[Kernel-packages] [Bug 1925522] Please test proposed package

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted fabric-manager-460 into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/fabric-
manager-460/460.73.01-0ubuntu0.18.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: fabric-manager-450 (Ubuntu Bionic)
   Status: New => Fix Committed

-- 
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 Committed
Status in fabric-manager-460 package in Ubuntu:
  Fix Committed
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 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 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 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 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 

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

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted fabric-manager-450 into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/fabric-
manager-450/450.119.04-0ubuntu0.20.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: fabric-manager-450 (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: fabric-manager-460 (Ubuntu Focal)
   Status: New => Fix Committed

-- 
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 Committed
Status in fabric-manager-460 package in Ubuntu:
  Fix Committed
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 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 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 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 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 t

[Kernel-packages] [Bug 1925344] Re: [nvidia] Session not started after reboot (black screen) - requires switching tty back and forth

[Launchpad Bug Tracker]

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

** Changed in: xorg-server (Ubuntu)
   Status: New => Confirmed

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

Title:
  [nvidia] Session not started after reboot (black screen) - requires
  switching tty back and forth

Status in gdm3 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  After installation, the first boot works as expected - the system
  boots into a graphical shell login screen. However all subsequent
  reboots end up with a black screen with a blinking cursor in the top-
  left corner of the screen. To get to the login screen, one has to
  switch to a different tty (like tty2 with ctrl+alt+f2) and then to
  tty1.

  Running `prime-select query` shows `nvidia`.

  Interesting enough, when I change the nvidia-prime settings at least
  once, like to on-demand via `prime-select on-demand` - then everything
  starts working as expected. Even when I switch back to `nvidia`.

  Not sure which package I should fill this under.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xserver-xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.67  Thu Mar 11 00:11:45 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 21 15:20:15 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Dell UHD Graphics [1028:09e1]
   NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TU116M [GeForce GTX 1660 Ti Mobile] [1028:09e1]
  InstallationDate: Installed on 2021-04-21 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. G3 3500
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=5b38428b-60e8-4741-8b7f-0e60094a80f7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2020
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 06ND9G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd12/04/2020:br1.7:svnDellInc.:pnG33500:pvr:rvnDellInc.:rn06ND9G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G3 3500
  dmi.product.sku: 09E1
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  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.11-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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

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

[Kernel-packages] [Bug 1925344] Re: [nvidia] Session not started after reboot (black screen) - requires switching tty back and forth

[Launchpad Bug Tracker]

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

** Changed in: nvidia-prime (Ubuntu)
   Status: New => Confirmed

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

Title:
  [nvidia] Session not started after reboot (black screen) - requires
  switching tty back and forth

Status in gdm3 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  After installation, the first boot works as expected - the system
  boots into a graphical shell login screen. However all subsequent
  reboots end up with a black screen with a blinking cursor in the top-
  left corner of the screen. To get to the login screen, one has to
  switch to a different tty (like tty2 with ctrl+alt+f2) and then to
  tty1.

  Running `prime-select query` shows `nvidia`.

  Interesting enough, when I change the nvidia-prime settings at least
  once, like to on-demand via `prime-select on-demand` - then everything
  starts working as expected. Even when I switch back to `nvidia`.

  Not sure which package I should fill this under.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xserver-xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.67  Thu Mar 11 00:11:45 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 21 15:20:15 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Dell UHD Graphics [1028:09e1]
   NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TU116M [GeForce GTX 1660 Ti Mobile] [1028:09e1]
  InstallationDate: Installed on 2021-04-21 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. G3 3500
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=5b38428b-60e8-4741-8b7f-0e60094a80f7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2020
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 06ND9G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd12/04/2020:br1.7:svnDellInc.:pnG33500:pvr:rvnDellInc.:rn06ND9G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G3 3500
  dmi.product.sku: 09E1
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  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.11-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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

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

[Kernel-packages] [Bug 1925344] Re: [nvidia] Session not started after reboot (black screen) - requires switching tty back and forth

[Launchpad Bug Tracker]

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

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

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

Title:
  [nvidia] Session not started after reboot (black screen) - requires
  switching tty back and forth

Status in gdm3 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  After installation, the first boot works as expected - the system
  boots into a graphical shell login screen. However all subsequent
  reboots end up with a black screen with a blinking cursor in the top-
  left corner of the screen. To get to the login screen, one has to
  switch to a different tty (like tty2 with ctrl+alt+f2) and then to
  tty1.

  Running `prime-select query` shows `nvidia`.

  Interesting enough, when I change the nvidia-prime settings at least
  once, like to on-demand via `prime-select on-demand` - then everything
  starts working as expected. Even when I switch back to `nvidia`.

  Not sure which package I should fill this under.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xserver-xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.67  Thu Mar 11 00:11:45 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 21 15:20:15 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Dell UHD Graphics [1028:09e1]
   NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TU116M [GeForce GTX 1660 Ti Mobile] [1028:09e1]
  InstallationDate: Installed on 2021-04-21 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. G3 3500
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=5b38428b-60e8-4741-8b7f-0e60094a80f7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2020
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 06ND9G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd12/04/2020:br1.7:svnDellInc.:pnG33500:pvr:rvnDellInc.:rn06ND9G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G3 3500
  dmi.product.sku: 09E1
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  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.11-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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

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

[Kernel-packages] [Bug 1925344] Re: [nvidia] Session not started after reboot (black screen) - requires switching tty back and forth

[Launchpad Bug Tracker]

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

** Changed in: nvidia-graphics-drivers-460 (Ubuntu)
   Status: New => Confirmed

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

Title:
  [nvidia] Session not started after reboot (black screen) - requires
  switching tty back and forth

Status in gdm3 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  After installation, the first boot works as expected - the system
  boots into a graphical shell login screen. However all subsequent
  reboots end up with a black screen with a blinking cursor in the top-
  left corner of the screen. To get to the login screen, one has to
  switch to a different tty (like tty2 with ctrl+alt+f2) and then to
  tty1.

  Running `prime-select query` shows `nvidia`.

  Interesting enough, when I change the nvidia-prime settings at least
  once, like to on-demand via `prime-select on-demand` - then everything
  starts working as expected. Even when I switch back to `nvidia`.

  Not sure which package I should fill this under.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xserver-xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.67  Thu Mar 11 00:11:45 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 21 15:20:15 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Dell UHD Graphics [1028:09e1]
   NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TU116M [GeForce GTX 1660 Ti Mobile] [1028:09e1]
  InstallationDate: Installed on 2021-04-21 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. G3 3500
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=5b38428b-60e8-4741-8b7f-0e60094a80f7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2020
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 06ND9G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd12/04/2020:br1.7:svnDellInc.:pnG33500:pvr:rvnDellInc.:rn06ND9G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G3 3500
  dmi.product.sku: 09E1
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  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.11-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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

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

[Kernel-packages] [Bug 1929106] Re: runc -v empty output

[Kir Kolyshkin]

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

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

Title:
  runc -v empty output

Status in runc package in Ubuntu:
  New

Bug description:
  Apparently runc is built in some non-standard way, so it does not show
  its version:

  kir@ubu2004:~$ runc -v
  runc version spec: 1.0.2-dev
  go: go1.13.8
  libseccomp: 2.5.1

  In the output above, version string is empty and there is no newline
  added, so we have a version of the spec in the same line. Thus, docker
  has the same problem reporting runc version:

  kir@ubu2004:~$ docker version | grep -A2 runc
   runc:
Version:  spec: 1.0.2-dev
GitCommit:  

  For comparison, here is the correct/expected output:

  [kir@kir-rhat runc]$ runc -v
  runc version 1.0.0-rc93+dev
  commit: ba257d2de86e7e530eeb28fe697e206630ef45f8
  spec: 1.0.2-dev
  go: go1.15.8
  libseccomp: 2.5.0

  Package information:

  kir@ubu2004:~$ dpkg -l runc
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version Architecture Description
  
+++-==-===--=
  ii  runc   1.0.0~rc93-0ubuntu1~20.04.2 amd64Open Container 
Project - runtime
  kir@ubu2004:~$ runc -v
  runc version spec: 1.0.2-dev
  go: go1.13.8
  libseccomp: 2.5.1

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

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

[Kernel-packages] [Bug 1925344] Re: [nvidia] Session not started after reboot (black screen) - requires switching tty back and forth

[Tim Crawford]

I believe I am experiencing this on 20.04

> (EE) open /dev/dri/card0: No such file or directory

The problem seems to be that gdm-wait-for-drm doesn't work for (muxless)
dual GPU laptops when using the dGPU.

GDM will start when only card1 is available, *both* card0 and card1 need
to be available before starting X.

(As a quick hack, I am using `ExecStartPre=/bin/sleep 1` to give drm
enough time before starting GDM.)

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

Title:
  [nvidia] Session not started after reboot (black screen) - requires
  switching tty back and forth

Status in gdm3 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  After installation, the first boot works as expected - the system
  boots into a graphical shell login screen. However all subsequent
  reboots end up with a black screen with a blinking cursor in the top-
  left corner of the screen. To get to the login screen, one has to
  switch to a different tty (like tty2 with ctrl+alt+f2) and then to
  tty1.

  Running `prime-select query` shows `nvidia`.

  Interesting enough, when I change the nvidia-prime settings at least
  once, like to on-demand via `prime-select on-demand` - then everything
  starts working as expected. Even when I switch back to `nvidia`.

  Not sure which package I should fill this under.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xserver-xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.67  Thu Mar 11 00:11:45 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 21 15:20:15 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Dell UHD Graphics [1028:09e1]
   NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TU116M [GeForce GTX 1660 Ti Mobile] [1028:09e1]
  InstallationDate: Installed on 2021-04-21 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. G3 3500
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=5b38428b-60e8-4741-8b7f-0e60094a80f7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2020
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 06ND9G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd12/04/2020:br1.7:svnDellInc.:pnG33500:pvr:rvnDellInc.:rn06ND9G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G3 3500
  dmi.product.sku: 09E1
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  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.11-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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

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

[Kernel-packages] [Bug 1925522] Please test proposed package

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted fabric-manager-450 into groovy-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/fabric-
manager-450/450.119.04-0ubuntu0.20.10.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
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 Committed
Status in fabric-manager-460 package in Ubuntu:
  Fix Committed
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:
  New
Status in fabric-manager-460 source package in Bionic:
  New
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:
  New
Status in fabric-manager-460 source package in Focal:
  New
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 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 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 Pote

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

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted fabric-manager-460 into groovy-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/fabric-
manager-460/460.73.01-0ubuntu0.20.10.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: fabric-manager-460 (Ubuntu Groovy)
   Status: New => Fix Committed

** Changed in: fabric-manager-450 (Ubuntu Groovy)
   Status: New => Fix Committed

-- 
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 Committed
Status in fabric-manager-460 package in Ubuntu:
  Fix Committed
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:
  New
Status in fabric-manager-460 source package in Bionic:
  New
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:
  New
Status in fabric-manager-460 source package in Focal:
  New
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 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 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

[Kernel-packages] [Bug 1856372] Re: Wifi drops, particularly under load

[Lee Blackwell]

I'm seeing similar behaviour; the NIC  appears to be 'connected' to the
AP but no packets appear to move.

root@vs85483:~# lspci | egrep Ath
3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network 
Adapter (rev 32)
root@vs85483:~# 

root@vs85483:~# dmesg | grep ath10k
[4.379983] ath10k_pci :3b:00.0: enabling device ( -> 0002)
[4.384471] ath10k_pci :3b:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 
reset_mode 0
[4.670211] ath10k_pci :3b:00.0: qca6174 hw3.2 target 0x0503 chip_id 
0x00340aff sub 1a56:1535
[4.670213] ath10k_pci :3b:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 
0 testmode 0
[4.670611] ath10k_pci :3b:00.0: firmware ver 
WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 
29eb8ca1
[4.735670] ath10k_pci :3b:00.0: board_file api 2 bmi_id N/A crc32 
4ac0889b
[4.826897] ath10k_pci :3b:00.0: unsupported HTC service id: 1536
[4.846191] ath10k_pci :3b:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp 
max-sta 32 raw 0 hwcrypto 1
[4.952299] ath10k_pci :3b:00.0 wlp59s0: renamed from wlan0
[9.360405] ath10k_pci :3b:00.0: unsupported HTC service id: 1536

root@vs85483:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename:   focal
root@vs85483:~# 

root@vs85483:~# apt list --installed | egrep "^linux-firmware"
[snip]
linux-firmware/focal-updates,focal-updates,now 1.187.12 all 
[installed,automatic]
root@vs85483:~# 

Plucked from lshw:
product: XPS 15 9570 (087C)

System firmware and apt managed packages all up to date as of today
(2021/05/20).

I'm happy to assist with further information/tests if that is helpful.

-Lee

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

Title:
  Wifi drops, particularly under load

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 18.04.3 LTS with Qualcomm Atheros QCA6174 wireless card,
  internet drops out, particularly when downloading at speeds ~1MB/s say
  via P2P torrent or ooka speedtest. The wifi connection (at least
  reported by wicd) remains active, but I cannot ping the router or
  access the internet. No error message is logged in journalctl after
  the internet drops. Details on my card, firmware and dmesg given below
  I'm not the only one with this issue:
  https://askubuntu.com/questions/1171813/wifi-randomly-or-under-load-
  disconnects-on-ubuntu-18-04-with-qualcomm-atheros

  The issue DOES NOT occur with wired connection (ethernet).
  
-
    *-network
     description: Wireless interface
     product: QCA6174 802.11ac Wireless Network Adapter
     vendor: Qualcomm Atheros
     physical id: 0
     bus info: pci@:3a:00.0
     logical name: wlp58s0
     version: 32
     serial: 9c:b6:d0:d4:9b:33
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=ath10k_pci 
driverversion=5.4.0-050400rc8-generic firmware=WLAN.RM.4.4.1-00140-QCARMSWPZ-1 
latency=0 link=no multicast=yes wireless=IEEE 802.11

     resources: irq:135 memory:dc00-dc1f
  
-
  $ dmesg | grep ath10k

  [2.662000] ath10k_pci :3a:00.0: enabling device ( -> 0002)
  [2.665299] ath10k_pci :3a:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [2.950979] ath10k_pci :3a:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 1a56:1535
  [2.950982] ath10k_pci :3a:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [2.951390] ath10k_pci :3a:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  [3.029754] ath10k_pci :3a:00.0: board_file api 2 bmi_id N/A crc32 
4ed3569e
  [3.108957] ath10k_pci :3a:00.0: unsupported HTC service id: 1536
  [3.128068] ath10k_pci :3a:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal 
otp max-sta 32 raw 0 hwcrypto 1
  [3.216750] ath10k_pci :3a:00.0 wlp58s0: renamed from wlan0
  [3.828149] ath10k_pci :3a:00.0: unsupported HTC service id: 1536
  [   14.519059] ath10k_pci :3a:00.0: unsupported HTC service id: 1536
  [   15.014705] ath10k_pci :3a:00.0: unsupported HTC service id: 1536
  [ 1054.860682] ath10k_pci :3a:00.0: unsupported HTC service id: 1536
  [ 1055.385335] ath10k_pci :3a:00.0: unsupported HTC service id: 1536

  
-
  $ dmesg | grep pcieport

  [0.959817] pcieport :00:1c.0: AER:

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

[Ubuntu Kernel Bot]

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

apport-collect 1929106

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

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

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

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

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

Title:
  runc -v empty output

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Apparently runc is built in some non-standard way, so it does not show
  its version:

  kir@ubu2004:~$ runc -v
  runc version spec: 1.0.2-dev
  go: go1.13.8
  libseccomp: 2.5.1

  In the output above, version string is empty and there is no newline
  added, so we have a version of the spec in the same line. Thus, docker
  has the same problem reporting runc version:

  kir@ubu2004:~$ docker version | grep -A2 runc
   runc:
Version:  spec: 1.0.2-dev
GitCommit:  

  For comparison, here is the correct/expected output:

  [kir@kir-rhat runc]$ runc -v
  runc version 1.0.0-rc93+dev
  commit: ba257d2de86e7e530eeb28fe697e206630ef45f8
  spec: 1.0.2-dev
  go: go1.15.8
  libseccomp: 2.5.0

  Package information:

  kir@ubu2004:~$ dpkg -l runc
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version Architecture Description
  
+++-==-===--=
  ii  runc   1.0.0~rc93-0ubuntu1~20.04.2 amd64Open Container 
Project - runtime
  kir@ubu2004:~$ runc -v
  runc version spec: 1.0.2-dev
  go: go1.13.8
  libseccomp: 2.5.1

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

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

[Kernel-packages] [Bug 1929106] [NEW] runc -v empty output

[Kir Kolyshkin]

Public bug reported:

Apparently runc is built in some non-standard way, so it does not show
its version:

kir@ubu2004:~$ runc -v
runc version spec: 1.0.2-dev
go: go1.13.8
libseccomp: 2.5.1

In the output above, version string is empty and there is no newline
added, so we have a version of the spec in the same line. Thus, docker
has the same problem reporting runc version:

kir@ubu2004:~$ docker version | grep -A2 runc
 runc:
  Version:  spec: 1.0.2-dev
  GitCommit:  

For comparison, here is the correct/expected output:

[kir@kir-rhat runc]$ runc -v
runc version 1.0.0-rc93+dev
commit: ba257d2de86e7e530eeb28fe697e206630ef45f8
spec: 1.0.2-dev
go: go1.15.8
libseccomp: 2.5.0

Package information:

kir@ubu2004:~$ dpkg -l runc
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version Architecture Description
+++-==-===--=
ii  runc   1.0.0~rc93-0ubuntu1~20.04.2 amd64Open Container 
Project - runtime
kir@ubu2004:~$ runc -v
runc version spec: 1.0.2-dev
go: go1.13.8
libseccomp: 2.5.1

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

Title:
  runc -v empty output

Status in linux package in Ubuntu:
  New

Bug description:
  Apparently runc is built in some non-standard way, so it does not show
  its version:

  kir@ubu2004:~$ runc -v
  runc version spec: 1.0.2-dev
  go: go1.13.8
  libseccomp: 2.5.1

  In the output above, version string is empty and there is no newline
  added, so we have a version of the spec in the same line. Thus, docker
  has the same problem reporting runc version:

  kir@ubu2004:~$ docker version | grep -A2 runc
   runc:
Version:  spec: 1.0.2-dev
GitCommit:  

  For comparison, here is the correct/expected output:

  [kir@kir-rhat runc]$ runc -v
  runc version 1.0.0-rc93+dev
  commit: ba257d2de86e7e530eeb28fe697e206630ef45f8
  spec: 1.0.2-dev
  go: go1.15.8
  libseccomp: 2.5.0

  Package information:

  kir@ubu2004:~$ dpkg -l runc
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version Architecture Description
  
+++-==-===--=
  ii  runc   1.0.0~rc93-0ubuntu1~20.04.2 amd64Open Container 
Project - runtime
  kir@ubu2004:~$ runc -v
  runc version spec: 1.0.2-dev
  go: go1.13.8
  libseccomp: 2.5.1

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

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

[Kernel-packages] [Bug 1928183] Re: turbostat doesn't work with AMD Cezanne APUs

[David Bartley]

Nope, still didn't work :(. I wonder if there was some subsequent patch
as well?  The version I have working is built off of master.

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

Title:
  turbostat doesn't work with AMD Cezanne APUs

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Hirsute:
  Incomplete

Bug description:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985681 describes the
  issue and necessary cherry-pick
  (https://git.kernel.org/linus/301b1d3a9104f4f3a8ab4171cf88d0f55d632b41).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-tools-common 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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bartle 2287 F pulseaudio
   /dev/snd/controlC0:  bartle 2287 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed May 12 01:04:15 2021
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  PackageArchitecture: all
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=27b86d91-8e89-49da-ad17-45901581ce2f ro
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (19 days ago)
  dmi.bios.date: 04/23/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P2.10
  dmi.board.name: B550 Phantom Gaming-ITX/ax
  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:bvnAmericanMegatrendsInternational,LLC.:bvrP2.10:bd04/23/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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/1928183/+subscriptions

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

[Kernel-packages] [Bug 1927518] Re: Fix kdump failures

[Tim Gardner]

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

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

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

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

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

Title:
  Fix kdump failures

Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure-4.15 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-azure source package in Bionic:
  Invalid
Status in linux-azure-4.15 source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux-azure source package in Focal:
  Fix Committed
Status in linux-azure-4.15 source package in Focal:
  Invalid
Status in linux source package in Groovy:
  Fix Committed
Status in linux-azure source package in Groovy:
  Fix Committed
Status in linux-azure-4.15 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-azure source package in Hirsute:
  Fix Committed
Status in linux-azure-4.15 source package in Hirsute:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  Microsoft relayed a customer report of failures when trying to take a
  kdump.

  These 3 patches fix the issue:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/video/fbdev/hyperv_fb.c?id=aa5b7d11c7cb87c266d705b237368985e7171958
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/channel_mgmt.c?id=77db0ec8b7764cb9b09b78066ebfd47b2c0c1909
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/channel_mgmt.c?id=8c2d5e0640e53c14b6240e9bf1e32a2226e6e6ca

  Patch #1 solves a problem where the “Unable to send packet via vmbus”
  message is output continuously. But with that problem fixed, the
  second problem can occur where the kdump kernel panics due to
  receiving an unexpected VMbus UNLOAD complete message.

  Patch #2 prevents the UNLOAD complete message from ever occurring in
  the kdump kernel. But if the UNLOAD complete message does occur at
  some unexpected time, Patch #3 prevents it from causing a panic.

  These patches seem worthy of application to all affected master
  kernels.

  [Test Plan]

  Cause a guest kernel to crash and successfully acquire a kdump.

  [Where problems could occur]

  The extended Hyper-V wait while flushing could cause side effects.

  [Other Info]
  SF: #00310145
  https://canonical.lightning.force.com/lightning/r/Case/5004K05pZNNQA2

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

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

[Kernel-packages] [Bug 1920944] Re: kvm: properly tear down PV features on hibernate

[Kleber Sacilotto de Souza]

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

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

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

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

Title:
  kvm: properly tear down PV features on hibernate

Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Focal:
  In Progress
Status in linux-aws source package in Focal:
  New
Status in linux source package in Groovy:
  In Progress
Status in linux-aws source package in Groovy:
  New
Status in linux source package in Hirsute:
  In Progress
Status in linux-aws source package in Hirsute:
  New

Bug description:
  [Impact]

  In LP: #1918694 we applied a fix and a workaround to solve the
  hibernation issues on c5.18xlarge. The workaround was in the form of a
  SAUCE patch:

    "UBUNTU: SAUCE: aws: kvm: double the size of hv_clock_boot"

  It looks like we can replace this workaround with a proper fix, by
  applying this patch:

  http://next.patchew.org/Linux/20210414123544.1060604-1-vkuzn...@redhat.com/

  This is required because various PV features (Async PF, PV EOI, steal
  time) work through memory shared with hypervisor and when we restore
  from hibernation we must properly tear down all these features to make
  sure hypervisor doesn't write to stale locations after we jump to the
  previously hibernated kernel.

  For this reason it is safe to apply this patch set also to all the
  generic kernels and not just AWS.

  [Test plan]

  This can be easily tested on AWS (but it should be reproduced by
  hibernating any kvm instance with multiple CPUs). Create a c5.18xlarge
  instance, run the memory stress test script (the same test script that
  we are using to stress test hibernation), trigger the hibernate event,
  trigger the resume event. Repeat a couple of times and the problem is
  very likely to happen.

  [Fix]

  On the AWS kernel replace "UBUNTU: SAUCE: aws: kvm: double the size of
  hv_clock_boot" with:

  http://next.patchew.org/Linux/20210414123544.1060604-1-vkuzn...@redhat.com/

  For the other kernels, simply apply this patch set.

  The fix has been tested extensively in the AWS infrastructure with
  positive results.

  [Regression potential]

  This new code introduced by the fix can be executed also when a CPU is
  put offline, so we may see potential regressions in the KVM CPU hot-
  plugging.

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

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

[Kernel-packages] [Bug 1928183] Re: turbostat doesn't work with AMD Cezanne APUs

[Po-Hsu Lin]

Hum...
yes this kernel contains 5.11.0-18 from the master-next branch + the commit 
mentioned in your bug description:

ubuntu-hirsute [master-next]$ git log --oneline 
d96cbcb tools/power/turbostat: Fix turbostat for AMD Zen CPUs
8c01482 UBUNTU: Ubuntu-5.11.0-18.19

commit d96cbcb71e2a47f240dcadfc498db278fb2a0b56
Author: Bas Nieuwenhuizen 
Date:   Wed Apr 28 17:09:03 2021 +0800

tools/power/turbostat: Fix turbostat for AMD Zen CPUs

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

It was reported that on Zen+ system turbostat started exiting,
which was tracked down to the MSR_PKG_ENERGY_STAT read failing because
offset_to_idx wasn't returning a non-negative index.

This patch combined the modification from Bingsong Si and
Bas Nieuwenhuizen and addd the MSR to the index system as alternative for
MSR_PKG_ENERGY_STATUS.

Fixes: 9972d5d84d76 ("tools/power turbostat: Enable accumulate RAPL 
display")
Reported-by: youling257 
Tested-by: youling257 
Tested-by: Kurt Garloff 
Tested-by: Bingsong Si 
Tested-by: Artem S. Tashkinov 
Co-developed-by: Bingsong Si 
Co-developed-by: Terry Bowman 
Signed-off-by: Bas Nieuwenhuizen 
Reviewed-by: Chen Yu 
Signed-off-by: Len Brown 
(cherry picked from commit 301b1d3a9104f4f3a8ab4171cf88d0f55d632b41)
Signed-off-by: Po-Hsu Lin 

BTW it looks like you will need to install more than just linux-tools-common 
deb. On a 21.04 clean install, if I just install linux-tools-common the 
turbostat command will complain about:
$ turbostat
WARNING: turbostat not found for kernel 5.11.0-17

  You may need to install the following packages for this specific kernel:
linux-tools-5.11.0-17-generic
linux-cloud-tools-5.11.0-17-generic

I will have to install 5.11.0-18 kernel/header/module/module-extras debs and 
other two tools-5.11 deb files to make it work on 5.11.0-18
Can you give it a try?
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/1928183

Title:
  turbostat doesn't work with AMD Cezanne APUs

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Hirsute:
  Incomplete

Bug description:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985681 describes the
  issue and necessary cherry-pick
  (https://git.kernel.org/linus/301b1d3a9104f4f3a8ab4171cf88d0f55d632b41).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-tools-common 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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bartle 2287 F pulseaudio
   /dev/snd/controlC0:  bartle 2287 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Wed May 12 01:04:15 2021
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  PackageArchitecture: all
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=27b86d91-8e89-49da-ad17-45901581ce2f ro
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-17-generic N/A
   linux-backports-modules-5.11.0-17-generic  N/A
   linux-firmware 1.197
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (19 days ago)
  dmi.bios.date: 04/23/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P2.10
  dmi.board.name: B550 Phantom Gaming-ITX/ax
  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:bvnAmericanMegatrendsInternational,LLC.:bvrP2.10:bd04/23/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax: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/1928183/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-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] Please test proposed package

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted fabric-manager-450 into hirsute-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/fabric-manager-450/450.119.04-0ubuntu0.21.04.2 in a few hours, and then
in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
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 Committed
Status in fabric-manager-460 package in Ubuntu:
  Fix Committed
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:
  New
Status in fabric-manager-460 source package in Bionic:
  New
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:
  New
Status in fabric-manager-460 source package in Focal:
  New
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:
  New
Status in fabric-manager-460 source package in Groovy:
  New
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 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

[Kernel-packages] [Bug 1925522] Please test proposed package

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted fabric-manager-460 into hirsute-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/fabric-manager-460/460.73.01-0ubuntu0.21.04.2 in a few hours, and then
in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
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 Committed
Status in fabric-manager-460 package in Ubuntu:
  Fix Committed
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:
  New
Status in fabric-manager-460 source package in Bionic:
  New
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:
  New
Status in fabric-manager-460 source package in Focal:
  New
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:
  New
Status in fabric-manager-460 source package in Groovy:
  New
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 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 

[Kernel-packages] [Bug 1919177] Re: Azure: issues with accelerated networking on Hirsute

[Gauthier Jolly]

@rbalint, I just tested Impish and I cannot reproduce the issue. It
doesn't prove it's not there but it's a very good sign!

I can see that our automated testing failed because of this issue on the
2021-05-10 but not after. If I'm not wrong, systemd 248 was pushed on
the 14th, this would make a nice correlation.

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

Title:
  Azure: issues with accelerated networking on Hirsute

Status in cloud-init:
  Incomplete
Status in cloud-init package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  [General]

  On Azure, when provisioning a Hirsute VM with Accelerated Networking
  enabled, sometimes part of the cloud-init configuration is not
  applied.

  Especially, in those cases, the public SSH key is not setup properly.

  [how to reproduce]

  Start a VM with AN enabled:

  ```
  az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South" 
 --image 
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size 
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY" 
--accelerated-networking
  ```

  After a moment, try to SSH: if you succeed, delete and recreate a new
  VM.

  [troubleshooting]

  To be able to connect into the VM, run:

  az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id 
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
  ```

  In "/run/cloud-init/instance-data.json", I can see:
  ```
   "publicKeys": [
    {
     "keyData": "",
     "path": "/home/ubuntu/.ssh/authorized_keys"
    }
   ],
  ```

  as expected.

  [workaround]

  As mentioned, Azure allows the user to run command into the VM without
  SSH connection. To do so, one can use the Azure CLI:

  az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
  RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"

  This example uses "ssh-import-id" but it's also possible to just echo
  a given public key into /home/ubuntu/.ssh/authorized_keys

  NOTE: this will only solves the SSH issue, I do not know if this bug
  affects other things. If so the user would have to apply those things
  manually.

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

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

[Kernel-packages] [Bug 1922494] Re: Ubuntu 20.04 - 'Support flow counters offset for bulk counters'

[Tim Gardner]

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

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

Title:
  Ubuntu 20.04 - 'Support flow counters offset for bulk counters'

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

Bug description:
  [impact]
  Add Support for flow counters offset for bulk counters on kernel side.
  Currently Ubuntu 20.04 supports 'flow counters offset for bulk counters' on 
user space side only with these 3 rdma-core patches from v27.0
  3956cf74 mlx5: Add support for bulk flow counters steering actions
  65ed59c6 Update kernel headers
  b32eee70 mlx5: Fix typos

  [test case]
  /*  download and install dpdk from github (issue do not reproduce with inbox 
dpdk) */
  $ git clone https://github.com/mellanox/dpdk.org
  $ cd dpdk.org/

  /* install dependencies if needed */
  $ apt-get install -y python3-pyelftools python-pyelftools
  $ apt install meson

  $ meson build-meson
  $ ninja -C build-meson/

  /* run dpdk-testpmd with mellanox HCA (I used CX5) :05:00.0,
  :05:00.1 are pci id for the cx5 devices */

  //dpdk.org/build-meson/app/dpdk-testpmd -v  -n 4
  -w :05:00.0,txq_inline=147,rx_vec_en=1  -w
  :05:00.1,txq_inline=147,rx_vec_en=1 -- --mbcache=512 -i  --nb-
  cores=7  --txd=8192 --rxd=8192  --burst=64

  EAL: Detected 12 lcore(s)
  EAL: Detected 2 NUMA nodes
  EAL: RTE Version: 'DPDK 21.05.0-rc0'
  Option -w, --pci-whitelist is deprecated, use -a, --allow option instead
  Option -w, --pci-whitelist is deprecated, use -a, --allow option instead
  EAL: Detected static linkage of DPDK
  EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
  EAL: Selected IOVA mode 'VA'
  EAL: Probing VFIO support...
  EAL: VFIO support initialized
  EAL: Probe PCI driver: mlx5_pci (15b3:101d) device: :05:00.0 (socket 0)
  mlx5_pci: txq_inline: deprecated parameter, converted to txq_inline_max
  mlx5_pci: txq_inline: deprecated parameter, converted to txq_inline_max
  mlx5_pci: Default miss action is not supported.
  mlx5_pci: Unexpected error in counter offset support detection /* 
LINE INDICATING ERROR*/
  EAL: Probe PCI driver: mlx5_pci (15b3:101d) device: :05:00.1 (socket 0)
  mlx5_pci: txq_inline: deprecated parameter, converted to txq_inline_max
  mlx5_pci: txq_inline: deprecated parameter, converted to txq_inline_max
  mlx5_pci: Default miss action is not supported.
  mlx5_pci: Unexpected error in counter offset support detection   /* 
LINE INDICATING ERROR*/
  Interactive-mode selected
  testpmd: create a new mbuf pool : n=327680, size=2176, socket=0
  testpmd: preferred mempool ops selected: ring_mp_mc
  testpmd: create a new mbuf pool : n=327680, size=2176, socket=1
  testpmd: preferred mempool ops selected: ring_mp_mc
  Configuring Port 0 (socket 0)
  Port 0: 0C:42:A1:D1:D0:64
  Configuring Port 1 (socket 0)
  Port 1: 0C:42:A1:D1:D0:65
  Checking link statuses...
  Done
  testpmd>

  two lines indicates errors in counter offset supports detection.

  [Fix]

  the issue is fixed with the following upstream commit from v5.5-rc1 which 
cleanly applied above focal.
  208d70f562e5 IB/mlx5: Support flow counters offset for bulk counters
  Our QA-dpdk team tested the focal kernel with this patch and found no issues.

  [regression potential]
  function mlx5_ib devx _is_flow_counter (from the devx interface) signature 
has changed so anything that uses it like rdma-core might be impacted.

  Thanks,
  Amir

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

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

[Kernel-packages] [Bug 1927518] Re: Fix kdump failures

[Ubuntu Kernel Bot]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
hirsute' to 'verification-done-hirsute'. If the problem still exists,
change the tag 'verification-needed-hirsute' to 'verification-failed-
hirsute'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-hirsute

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

Title:
  Fix kdump failures

Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure-4.15 package in Ubuntu:
  New
Status in linux source package in Bionic:
  In Progress
Status in linux-azure source package in Bionic:
  Invalid
Status in linux-azure-4.15 source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  In Progress
Status in linux-azure source package in Focal:
  Fix Committed
Status in linux-azure-4.15 source package in Focal:
  Invalid
Status in linux source package in Groovy:
  In Progress
Status in linux-azure source package in Groovy:
  Fix Committed
Status in linux-azure-4.15 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  In Progress
Status in linux-azure source package in Hirsute:
  Fix Committed
Status in linux-azure-4.15 source package in Hirsute:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  Microsoft relayed a customer report of failures when trying to take a
  kdump.

  These 3 patches fix the issue:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/video/fbdev/hyperv_fb.c?id=aa5b7d11c7cb87c266d705b237368985e7171958
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/channel_mgmt.c?id=77db0ec8b7764cb9b09b78066ebfd47b2c0c1909
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/channel_mgmt.c?id=8c2d5e0640e53c14b6240e9bf1e32a2226e6e6ca

  Patch #1 solves a problem where the “Unable to send packet via vmbus”
  message is output continuously. But with that problem fixed, the
  second problem can occur where the kdump kernel panics due to
  receiving an unexpected VMbus UNLOAD complete message.

  Patch #2 prevents the UNLOAD complete message from ever occurring in
  the kdump kernel. But if the UNLOAD complete message does occur at
  some unexpected time, Patch #3 prevents it from causing a panic.

  These patches seem worthy of application to all affected master
  kernels.

  [Test Plan]

  Cause a guest kernel to crash and successfully acquire a kdump.

  [Where problems could occur]

  The extended Hyper-V wait while flushing could cause side effects.

  [Other Info]
  SF: #00310145
  https://canonical.lightning.force.com/lightning/r/Case/5004K05pZNNQA2

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

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

[Kernel-packages] [Bug 1920944] Re: kvm: properly tear down PV features on hibernate

[Andrea Righi]

** Summary changed:

- properly tear down KVM PV features on hibernate
+ kvm: properly tear down PV features on hibernate

** Description changed:

  [Impact]
  
  In LP: #1918694 we applied a fix and a workaround to solve the
  hibernation issues on c5.18xlarge. The workaround was in the form of a
  SAUCE patch:
  
    "UBUNTU: SAUCE: aws: kvm: double the size of hv_clock_boot"
  
  It looks like we can replace this workaround with a proper fix, by
  applying this patch:
  
  http://next.patchew.org/Linux/20210414123544.1060604-1-vkuzn...@redhat.com/
  
  This is required because various PV features (Async PF, PV EOI, steal
  time) work through memory shared with hypervisor and when we restore
  from hibernation we must properly tear down all these features to make
  sure hypervisor doesn't write to stale locations after we jump to the
  previously hibernated kernel.
  
- For this reason it is safe to apply this patch set also to the other
+ For this reason it is safe to apply this patch set also to all the
  generic kernels and not just AWS.
  
  [Test plan]
  
  This can be easily tested on AWS (but it should be reproduced by
  hibernating any kvm instance with multiple CPUs). Create a c5.18xlarge
  instance, run the memory stress test script (the same test script that
  we are using to stress test hibernation), trigger the hibernate event,
  trigger the resume event. Repeat a couple of times and the problem is
  very likely to happen.
  
  [Fix]
  
  On the AWS kernel replace "UBUNTU: SAUCE: aws: kvm: double the size of
  hv_clock_boot" with:
  
  http://next.patchew.org/Linux/20210414123544.1060604-1-vkuzn...@redhat.com/
  
  For the other kernels, simply apply this patch set.
  
  The fix has been tested extensively in the AWS infrastructure with
  positive results.
  
  [Regression potential]
  
  This new code introduced by the fix can be executed also when a CPU is
- put offline, so we may see potential regressions in the KVM CPU
- hotplugging.
+ put offline, so we may see potential regressions in the KVM CPU hot-
+ plugging.

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

Title:
  kvm: properly tear down PV features on hibernate

Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Focal:
  Incomplete
Status in linux-aws source package in Focal:
  New
Status in linux source package in Groovy:
  Incomplete
Status in linux-aws source package in Groovy:
  New
Status in linux source package in Hirsute:
  Incomplete
Status in linux-aws source package in Hirsute:
  New

Bug description:
  [Impact]

  In LP: #1918694 we applied a fix and a workaround to solve the
  hibernation issues on c5.18xlarge. The workaround was in the form of a
  SAUCE patch:

    "UBUNTU: SAUCE: aws: kvm: double the size of hv_clock_boot"

  It looks like we can replace this workaround with a proper fix, by
  applying this patch:

  http://next.patchew.org/Linux/20210414123544.1060604-1-vkuzn...@redhat.com/

  This is required because various PV features (Async PF, PV EOI, steal
  time) work through memory shared with hypervisor and when we restore
  from hibernation we must properly tear down all these features to make
  sure hypervisor doesn't write to stale locations after we jump to the
  previously hibernated kernel.

  For this reason it is safe to apply this patch set also to all the
  generic kernels and not just AWS.

  [Test plan]

  This can be easily tested on AWS (but it should be reproduced by
  hibernating any kvm instance with multiple CPUs). Create a c5.18xlarge
  instance, run the memory stress test script (the same test script that
  we are using to stress test hibernation), trigger the hibernate event,
  trigger the resume event. Repeat a couple of times and the problem is
  very likely to happen.

  [Fix]

  On the AWS kernel replace "UBUNTU: SAUCE: aws: kvm: double the size of
  hv_clock_boot" with:

  http://next.patchew.org/Linux/20210414123544.1060604-1-vkuzn...@redhat.com/

  For the other kernels, simply apply this patch set.

  The fix has been tested extensively in the AWS infrastructure with
  positive results.

  [Regression potential]

  This new code introduced by the fix can be executed also when a CPU is
  put offline, so we may see potential regressions in the KVM CPU hot-
  plugging.

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1920944

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

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

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

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

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

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

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

Title:
  kvm: properly tear down PV features on hibernate

Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Focal:
  Incomplete
Status in linux-aws source package in Focal:
  New
Status in linux source package in Groovy:
  Incomplete
Status in linux-aws source package in Groovy:
  New
Status in linux source package in Hirsute:
  Incomplete
Status in linux-aws source package in Hirsute:
  New

Bug description:
  [Impact]

  In LP: #1918694 we applied a fix and a workaround to solve the
  hibernation issues on c5.18xlarge. The workaround was in the form of a
  SAUCE patch:

    "UBUNTU: SAUCE: aws: kvm: double the size of hv_clock_boot"

  It looks like we can replace this workaround with a proper fix, by
  applying this patch:

  http://next.patchew.org/Linux/20210414123544.1060604-1-vkuzn...@redhat.com/

  This is required because various PV features (Async PF, PV EOI, steal
  time) work through memory shared with hypervisor and when we restore
  from hibernation we must properly tear down all these features to make
  sure hypervisor doesn't write to stale locations after we jump to the
  previously hibernated kernel.

  For this reason it is safe to apply this patch set also to the other
  generic kernels and not just AWS.

  [Test plan]

  This can be easily tested on AWS (but it should be reproduced by
  hibernating any kvm instance with multiple CPUs). Create a c5.18xlarge
  instance, run the memory stress test script (the same test script that
  we are using to stress test hibernation), trigger the hibernate event,
  trigger the resume event. Repeat a couple of times and the problem is
  very likely to happen.

  [Fix]

  On the AWS kernel replace "UBUNTU: SAUCE: aws: kvm: double the size of
  hv_clock_boot" with:

  http://next.patchew.org/Linux/20210414123544.1060604-1-vkuzn...@redhat.com/

  For the other kernels, simply apply this patch set.

  The fix has been tested extensively in the AWS infrastructure with
  positive results.

  [Regression potential]

  This new code introduced by the fix can be executed also when a CPU is
  put offline, so we may see potential regressions in the KVM CPU
  hotplugging.

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

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

[Kernel-packages] [Bug 1920944] Re: aws: proper fix for c5.18xlarge hibernation issues

[Andrea Righi]

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

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

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

** Description changed:

  [Impact]
  
  In LP: #1918694 we applied a fix and a workaround to solve the
  hibernation issues on c5.18xlarge. The workaround was in the form of a
  SAUCE patch:
  
    "UBUNTU: SAUCE: aws: kvm: double the size of hv_clock_boot"
  
  It looks like we can replace this workaround with a proper fix, by
  applying this patch:
  
  http://next.patchew.org/Linux/20210414123544.1060604-1-vkuzn...@redhat.com/
  
+ This is required because various PV features (Async PF, PV EOI, steal
+ time) work through memory shared with hypervisor and when we restore
+ from hibernation we must properly tear down all these features to make
+ sure hypervisor doesn't write to stale locations after we jump to the
+ previously hibernated kernel.
+ 
+ For this reason it is safe to apply this patch set also to the other
+ generic kernels and not just AWS.
+ 
  [Test plan]
  
- Create a c5.18xlarge instance, run the memory stress test script (the
- same test script that we are using to stress test hibernation), trigger
- the hibernate event, trigger the resume event. Repeat a couple of times
- and the problem is very likely to happen.
+ This can be easily tested on AWS (but it should be reproduced by
+ hibernating any kvm instance with multiple CPUs). Create a c5.18xlarge
+ instance, run the memory stress test script (the same test script that
+ we are using to stress test hibernation), trigger the hibernate event,
+ trigger the resume event. Repeat a couple of times and the problem is
+ very likely to happen.
  
  [Fix]
  
- Replace "UBUNTU: SAUCE: aws: kvm: double the size of hv_clock_boot"
- with:
+ On the AWS kernel replace "UBUNTU: SAUCE: aws: kvm: double the size of
+ hv_clock_boot" with:
  
  http://next.patchew.org/Linux/20210414123544.1060604-1-vkuzn...@redhat.com/
+ 
+ For the other kernels, simply apply this patch set.
  
  The fix has been tested extensively in the AWS infrastructure with
  positive results.
  
  [Regression potential]
  
  This new code introduced by the fix can be executed also when a CPU is
  put offline, so we may see potential regressions in the KVM CPU
  hotplugging.

** Summary changed:

- aws: proper fix for c5.18xlarge hibernation issues
+ properly tear down KVM PV features on hibernate

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

Title:
  kvm: properly tear down PV features on hibernate

Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Focal:
  Incomplete
Status in linux-aws source package in Focal:
  New
Status in linux source package in Groovy:
  Incomplete
Status in linux-aws source package in Groovy:
  New
Status in linux source package in Hirsute:
  Incomplete
Status in linux-aws source package in Hirsute:
  New

Bug description:
  [Impact]

  In LP: #1918694 we applied a fix and a workaround to solve the
  hibernation issues on c5.18xlarge. The workaround was in the form of a
  SAUCE patch:

    "UBUNTU: SAUCE: aws: kvm: double the size of hv_clock_boot"

  It looks like we can replace this workaround with a proper fix, by
  applying this patch:

  http://next.patchew.org/Linux/20210414123544.1060604-1-vkuzn...@redhat.com/

  This is required because various PV features (Async PF, PV EOI, steal
  time) work through memory shared with hypervisor and when we restore
  from hibernation we must properly tear down all these features to make
  sure hypervisor doesn't write to stale locations after we jump to the
  previously hibernated kernel.

  For this reason it is safe to apply this patch set also to the other
  generic kernels and not just AWS.

  [Test plan]

  This can be easily tested on AWS (but it should be reproduced by
  hibernating any kvm instance with multiple CPUs). Create a c5.18xlarge
  instance, run the memory stress test script (the same test script that
  we are using to stress test hibernation), trigger the hibernate event,
  trigger the resume event. Repeat a couple of times and the problem is
  very likely to happen.

  [Fix]

  On the AWS kernel replace "UBUNTU: SAUCE: aws: kvm: double the size of
  hv_clock_boot" with:

  http://next.patchew.org/Linux/20210414123544.1060604-1-vkuzn...@redhat.com/

  For the other kernels, simply apply this patch set.

  The fix has been tested extensively in the AWS infrastructure with
  positive results.

  [Regression potential]

  This new code introduced by the fix can be executed also when a CPU is
  put offline, so we may see potential regressions in the KVM CPU
  hotplugging.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu

[Kernel-packages] [Bug 1925522] Please test proposed package

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted fabric-manager-450 into hirsute-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/fabric-manager-450/450.119.04-0ubuntu0.21.04.1 in a few hours, and then
in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: fabric-manager-460 (Ubuntu Hirsute)
   Status: New => Fix Committed

-- 
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 Committed
Status in fabric-manager-460 package in Ubuntu:
  Fix Committed
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:
  New
Status in fabric-manager-460 source package in Bionic:
  New
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:
  New
Status in fabric-manager-460 source package in Focal:
  New
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:
  New
Status in fabric-manager-460 source package in Groovy:
  New
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 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 

[Kernel-packages] [Bug 1925522] Please test proposed package

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted fabric-manager-460 into hirsute-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/fabric-manager-460/460.73.01-0ubuntu0.21.04.1 in a few hours, and then
in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
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 Committed
Status in fabric-manager-460 package in Ubuntu:
  Fix Committed
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:
  New
Status in fabric-manager-460 source package in Bionic:
  New
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:
  New
Status in fabric-manager-460 source package in Focal:
  New
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:
  New
Status in fabric-manager-460 source package in Groovy:
  New
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 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 

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

[Łukasz Zemczak]

** Changed in: fabric-manager-450 (Ubuntu Hirsute)
   Status: New => Fix Committed

-- 
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 Committed
Status in fabric-manager-460 package in Ubuntu:
  Fix Committed
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:
  New
Status in fabric-manager-460 source package in Bionic:
  New
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:
  New
Status in fabric-manager-460 source package in Focal:
  New
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:
  New
Status in fabric-manager-460 source package in Groovy:
  New
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:
  New
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 library that caused clients such as
DCGM to fail to load the library. Since the NSCQ library version
needs to match the driver version, the user would encounter a
version mismatch issue when using DCGM.
  - Fixed an ECC policy that caused a CUDA malloc failure after
encountering a single uncorrectable error.

  == 460 ==

* debian/templates/control.in:
  - Make nvidia-dkms depend on its versioned nvidia-kernel-source
(LP: #1925386).
  - Add transitional packages for the 450 series (LP: #1925522).

  == 465 ==

* Initial release (LP: #1925522).

  == nvidia-settings ==

* New upstream release (LP: #1925522). [all releases]
* debian/patches/08_add_prime_support.patch: [all releases except for 
impish and hirsute]
  - Stop the timeout after the child is done. This fixes an error
that g_type_check_instance_is_a() was throwing.

  == fabric-manager-450 and fabric-manager-4

[Kernel-packages] [Bug 1854722] Re: mtest06 from mm in ubuntu_ltp failed on B-AWS-5.0 B-AWS-4.15

[Thadeu Lima de Souza Cascardo]

Marking the linux-aws task as invalid because this is not a bug in the
kernel, but the test. Though we could consider backporting the
overcommit change, that should be on a different bug.

Cascardo.

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

** Changed in: ubuntu-kernel-tests
   Status: Triaged => In Progress

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

Title:
  mtest06 from mm in ubuntu_ltp failed on B-AWS-5.0 B-AWS-4.15

Status in ubuntu-kernel-tests:
  In Progress
Status in linux-aws package in Ubuntu:
  Invalid

Bug description:
  Kernel: 5.0.0-1022.25~18.04.1

  Issue found on instance t2.small
  The test failed with ENOMEM

  
   startup='Wed Nov 20 10:40:07 2019'
   tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
   mmap1.c:205: BROK: mmap((nil),2147483648,3,34,-1,0) failed: ENOMEM (12)

   Summary:
   passed 0
   failed 0
   skipped 0
   warnings 0
   tag=mtest06 stime=1574246407 dur=0 exit=exited stat=2 core=no cu=0 cs=0

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

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

[Kernel-packages] [Bug 1929027] Re: drm/i915: Drop force_probe requirement for ADL-S

[You-Sheng Yang]

** Description changed:

+ [SRU Justification]
+ 
+ [Impact]
+ 
+ ADL-S i915 PCI ID has been in v5.13-rc1 in commit 0883d63b19bbd
+ ("drm/i915/adl_s: Add ADL-S platform info and PCI ids"), but it is
+ marked require_force_probe currently, therefore early phase development
+ takes an extra i915.force_probe=4680 boot parameter to enable i915.
+ 
+ [Fix]
+ 
+ Intel should remove this flag sometime later when ADL-S drm is stable
+ enough. But before that, we can simply remove that flag from adl_s_info in
+ drivers/gpu/drm/i915/i915_pci.c.
+ 
+ [Test Case]
+ 
+ i915 should be loaded automatically with patched kernel, so do:
+ 
+   $ lsmod|grep i915
+   i915
+ 
+ [Where problems could occur]
+ 
+ While this is still an alpha platform in development in OEM projects,
+ this should not introduce trouble for others. As for ADL, troubles are
+ expected and to be resolved.
+ 
+ == original bug description ==
+ 
  ADL i915 PCI IDs have been in v5.13-rc1 in commit 0883d63b19bbd 
("drm/i915/adl_s: Add ADL-S platform info and PCI ids"), but it is marked 
require_force_probe. We need drop this requirement from this kernel so that 
machines being tested don't need to work around it locally.
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  u  1601 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  u  1601 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-01 (413 days ago)
  InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
  IwConfig:
-  lono wireless extensions.
-  
-  enp0s31f6  no wireless extensions.
+  lono wireless extensions.
+ 
+  enp0s31f6  no wireless extensions.
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
-  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 2M
-  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
-  |__ Port 13: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
12M
-  |__ Port 13: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 
12M
+  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 2M
+  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
+  |__ Port 13: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
12M
+  |__ Port 13: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 
12M
  MachineType: Intel Corporation Alder Lake Client Platform
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-2002-oem 
root=UUID=19a0773e-f33a-413d-bb6a-f1e1cc674a3a ro quiet splash vt.handoff=7 
i915.force_probe=4680
  ProcVersionSignature: Ubuntu 5.13.0-2002.2+lp1922856.1.i915.mm.bug-oem 
5.13.0-rc2
  RelatedPackageVersions:
-  linux-restricted-modules-5.13.0-2002-oem N/A
-  linux-backports-modules-5.13.0-2002-oem  N/A
-  linux-firmware   1.187.12
+  linux-restricted-modules-5.13.0-2002-oem N/A
+  linux-backports-modules-5.13.0-2002-oem  N/A
+  linux-firmware   1.187.12
  RfKill:
-  
+ 
  Tags:  focal
  Uname: Linux 5.13.0-2002-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/25/2021
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: ADLSFWI1.R00.2081.A02.2102250858
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: AlderLake-S ADP-S DDR5 UDIMM CRB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: 2
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrADLSFWI1.R00.2081.A02.2102250858:bd02/25/2021:efr1.25:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku1001002B0100:rvnIntelCorporation:rnAlderLake-SADP-SDDR5UDIMMCRB:rvr2:cvnIntelCorporation:ct3:cvr0.1:
  dmi.product.family: Alder Lake Client System
  dmi.product.name: Alder Lake Client Platform
  dmi.product.sku: 1001002B0100
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

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

Title:
  drm/i915: Drop force_probe requirement for ADL-S

Status in HWE Next:
  New
Status in linux

[Kernel-packages] [Bug 1928889] Re: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range)

[Po-Hsu Lin]

Patch submitted upstream
https://lore.kernel.org/netdev/20210520104954.25007-1-po-
hsu@canonical.com/T/#u

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

Title:
  devlink_port_split in net from ubuntu_kernel_selftests linux ADT test
  failure with linux/5.11.0-18.19 ( list index out of range)

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

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

  Not a regression. Found to occur previously on hirsute/linux
  5.11.0-14.15

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz


  17:39:37 DEBUG| [stdout] # selftests: net: devlink_port_split.py
  17:39:37 DEBUG| [stdout] # Traceback (most recent call last):
  17:39:37 DEBUG| [stdout] #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 277, in 
  17:39:37 DEBUG| [stdout] # main()
  17:39:37 DEBUG| [stdout] #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 242, in main
  17:39:37 DEBUG| [stdout] # dev = list(devs.keys())[0]
  17:39:37 DEBUG| [stdout] # IndexError: list index out of range
  17:39:37 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # 
exit=1

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

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

[Kernel-packages] [Bug 1929048] [NEW] Speed up resume time on HP laptops

[Kai-Heng Feng]

Public bug reported:

[Impact]
Some HP laptops can take very long time to resume from sleep.

[Fix]
Avoid evaluating _INI on resume. It's only needed to run once at boot.

[Test]
Suspend and resume the system.
With the patch applied, the system resumes in a blink.

[Where problems could occur]
Maybe there are some platforms require the old behavior, so hp-accel can
break after system resume.

** Affects: hwe-next
 Importance: Undecided
 Status: New

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

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

** Affects: linux (Ubuntu Focal)
 Importance: Undecided
 Status: Won't Fix

** Affects: linux-oem-5.10 (Ubuntu Focal)
 Importance: Low
 Status: Confirmed

** Affects: linux (Ubuntu Hirsute)
 Importance: Low
 Status: Confirmed

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


** Tags: oem-priority originate-from-1925718 stella

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Tags added: oem-priority originate-from-1925718 stella

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

Title:
  Speed up resume time on HP laptops

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.10 source package in Focal:
  Confirmed
Status in linux source package in Hirsute:
  Confirmed
Status in linux-oem-5.10 source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  Some HP laptops can take very long time to resume from sleep.

  [Fix]
  Avoid evaluating _INI on resume. It's only needed to run once at boot.

  [Test]
  Suspend and resume the system.
  With the patch applied, the system resumes in a blink.

  [Where problems could occur]
  Maybe there are some platforms require the old behavior, so hp-accel can
  break after system resume.

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

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

[Kernel-packages] [Bug 1928889] Re: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range)

[Po-Hsu Lin]

This is a test case issue when there is no devlink device available.

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

Title:
  devlink_port_split in net from ubuntu_kernel_selftests linux ADT test
  failure with linux/5.11.0-18.19 ( list index out of range)

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

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

  Not a regression. Found to occur previously on hirsute/linux
  5.11.0-14.15

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz


  17:39:37 DEBUG| [stdout] # selftests: net: devlink_port_split.py
  17:39:37 DEBUG| [stdout] # Traceback (most recent call last):
  17:39:37 DEBUG| [stdout] #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 277, in 
  17:39:37 DEBUG| [stdout] # main()
  17:39:37 DEBUG| [stdout] #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 242, in main
  17:39:37 DEBUG| [stdout] # dev = list(devs.keys())[0]
  17:39:37 DEBUG| [stdout] # IndexError: list index out of range
  17:39:37 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # 
exit=1

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

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

[Kernel-packages] [Bug 1919177] Re: Azure: issues with accelerated networking on Hirsute

[Gauthier Jolly]

@rbalint I was able to reproduce the issue with an image that was
running the following:

ii  cloud-init20.4.1-79-g71564dce-0ubuntu1 all  initialization 
and customization tool for cloud instances
ii  linux-image-azure 5.8.0.1017.19+21.04.14   amd64Linux kernel 
image for Azure systems.
ii  systemd   247.3-3ubuntu3   amd64system and 
service manager

For reference, I took 20210219 and only upgraded systemd.

I will also try to reproduce with Impish to confirm whether or not
systemd 248 solves the issue.

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

Title:
  Azure: issues with accelerated networking on Hirsute

Status in cloud-init:
  Incomplete
Status in cloud-init package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  [General]

  On Azure, when provisioning a Hirsute VM with Accelerated Networking
  enabled, sometimes part of the cloud-init configuration is not
  applied.

  Especially, in those cases, the public SSH key is not setup properly.

  [how to reproduce]

  Start a VM with AN enabled:

  ```
  az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South" 
 --image 
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size 
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY" 
--accelerated-networking
  ```

  After a moment, try to SSH: if you succeed, delete and recreate a new
  VM.

  [troubleshooting]

  To be able to connect into the VM, run:

  az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id 
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
  ```

  In "/run/cloud-init/instance-data.json", I can see:
  ```
   "publicKeys": [
    {
     "keyData": "",
     "path": "/home/ubuntu/.ssh/authorized_keys"
    }
   ],
  ```

  as expected.

  [workaround]

  As mentioned, Azure allows the user to run command into the VM without
  SSH connection. To do so, one can use the Azure CLI:

  az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
  RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"

  This example uses "ssh-import-id" but it's also possible to just echo
  a given public key into /home/ubuntu/.ssh/authorized_keys

  NOTE: this will only solves the SSH issue, I do not know if this bug
  affects other things. If so the user would have to apply those things
  manually.

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

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

[Kernel-packages] [Bug 1922494] Re: Ubuntu 20.04 - 'Support flow counters offset for bulk counters'

[Amir Tzin]

** Description changed:

  [impact]
  Add Support for flow counters offset for bulk counters on kernel side.
  Currently Ubuntu 20.04 supports 'flow counters offset for bulk counters' on 
user space side only with these 3 rdma-core patches from v27.0
  3956cf74 mlx5: Add support for bulk flow counters steering actions
  65ed59c6 Update kernel headers
  b32eee70 mlx5: Fix typos
  
  [test case]
  /*  download and install dpdk from github (issue do not reproduce with inbox 
dpdk) */
  $ git clone https://github.com/mellanox/dpdk.org
  $ cd dpdk.org/
  
  /* install dependencies if needed */
  $ apt-get install -y python3-pyelftools python-pyelftools
  $ apt install meson
  
  $ meson build-meson
  $ ninja -C build-meson/
  
  /* run dpdk-testpmd with mellanox HCA (I used CX5) :05:00.0,
  :05:00.1 are pci id for the cx5 devices */
  
  //dpdk.org/build-meson/app/dpdk-testpmd -v  -n 4
  -w :05:00.0,txq_inline=147,rx_vec_en=1  -w
  :05:00.1,txq_inline=147,rx_vec_en=1 -- --mbcache=512 -i  --nb-
  cores=7  --txd=8192 --rxd=8192  --burst=64
  
  EAL: Detected 12 lcore(s)
  EAL: Detected 2 NUMA nodes
  EAL: RTE Version: 'DPDK 21.05.0-rc0'
  Option -w, --pci-whitelist is deprecated, use -a, --allow option instead
  Option -w, --pci-whitelist is deprecated, use -a, --allow option instead
  EAL: Detected static linkage of DPDK
  EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
  EAL: Selected IOVA mode 'VA'
  EAL: Probing VFIO support...
  EAL: VFIO support initialized
  EAL: Probe PCI driver: mlx5_pci (15b3:101d) device: :05:00.0 (socket 0)
  mlx5_pci: txq_inline: deprecated parameter, converted to txq_inline_max
  mlx5_pci: txq_inline: deprecated parameter, converted to txq_inline_max
  mlx5_pci: Default miss action is not supported.
  mlx5_pci: Unexpected error in counter offset support detection /* 
LINE INDICATING ERROR*/
  EAL: Probe PCI driver: mlx5_pci (15b3:101d) device: :05:00.1 (socket 0)
  mlx5_pci: txq_inline: deprecated parameter, converted to txq_inline_max
  mlx5_pci: txq_inline: deprecated parameter, converted to txq_inline_max
  mlx5_pci: Default miss action is not supported.
  mlx5_pci: Unexpected error in counter offset support detection   /* 
LINE INDICATING ERROR*/
  Interactive-mode selected
  testpmd: create a new mbuf pool : n=327680, size=2176, socket=0
  testpmd: preferred mempool ops selected: ring_mp_mc
  testpmd: create a new mbuf pool : n=327680, size=2176, socket=1
  testpmd: preferred mempool ops selected: ring_mp_mc
  Configuring Port 0 (socket 0)
  Port 0: 0C:42:A1:D1:D0:64
  Configuring Port 1 (socket 0)
  Port 1: 0C:42:A1:D1:D0:65
  Checking link statuses...
  Done
  testpmd>
  
  two lines indicates errors in counter offset supports detection.
  
  [Fix]
  
  the issue is fixed with the following upstream commit from v5.5-rc1 which 
cleanly applied above focal.
  208d70f562e5 IB/mlx5: Support flow counters offset for bulk counters
  Our QA-dpdk team tested the focal kernel with this patch and found no issues.
  
+ [regression potential]
+ function mlx5_ib devx _is_flow_counter (from the devx interface) signature 
has changed so anything that uses it like rdma-core might be impacted.
+ 
  Thanks,
  Amir

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

Title:
  Ubuntu 20.04 - 'Support flow counters offset for bulk counters'

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

Bug description:
  [impact]
  Add Support for flow counters offset for bulk counters on kernel side.
  Currently Ubuntu 20.04 supports 'flow counters offset for bulk counters' on 
user space side only with these 3 rdma-core patches from v27.0
  3956cf74 mlx5: Add support for bulk flow counters steering actions
  65ed59c6 Update kernel headers
  b32eee70 mlx5: Fix typos

  [test case]
  /*  download and install dpdk from github (issue do not reproduce with inbox 
dpdk) */
  $ git clone https://github.com/mellanox/dpdk.org
  $ cd dpdk.org/

  /* install dependencies if needed */
  $ apt-get install -y python3-pyelftools python-pyelftools
  $ apt install meson

  $ meson build-meson
  $ ninja -C build-meson/

  /* run dpdk-testpmd with mellanox HCA (I used CX5) :05:00.0,
  :05:00.1 are pci id for the cx5 devices */

  //dpdk.org/build-meson/app/dpdk-testpmd -v  -n 4
  -w :05:00.0,txq_inline=147,rx_vec_en=1  -w
  :05:00.1,txq_inline=147,rx_vec_en=1 -- --mbcache=512 -i  --nb-
  cores=7  --txd=8192 --rxd=8192  --burst=64

  EAL: Detected 12 lcore(s)
  EAL: Detected 2 NUMA nodes
  EAL: RTE Version: 'DPDK 21.05.0-rc0'
  Option -w, --pci-whitelist is deprecated, use -a, --allow option instead
  Option -w, --pci-whitelist is deprecated, use -a, --allow option instead
  EAL: Detected static linkage of DPDK
  EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
  EAL: Selected IOVA mode 'VA'

[Kernel-packages] [Bug 1927858] Re: package libnvidia-compute-460-server 460.73.01-0ubuntu0.20.04.1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is

[Launchpad Bug Tracker]

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

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

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

Title:
  package libnvidia-compute-460-server 460.73.01-0ubuntu0.20.04.1 failed
  to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu
  /libnvidia-ml.so', which is also in package nvidia-340
  340.108-0ubuntu5.20.04.1

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

Bug description:
  This package tries to manage a file that is also managed by another
  nvidia package.

  Sorry, I can't remember which other nvidia package caused the problem
  now but it was related to nvidia-cuda-toolkit.

  I had to resolve it like this:

  sudo dpkg -i --force-overwrite libnvidia-
  compute-460-server_460.73.01-0ubuntu0.20.04.1_amd64.deb

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libnvidia-compute-460-server 460.73.01-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun May  9 14:06:50 2021
  DuplicateSignature:
   package:libnvidia-compute-460-server:460.73.01-0ubuntu0.20.04.1
   Unpacking libnvidia-compute-460-server:amd64 (460.73.01-0ubuntu0.20.04.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-lvdbkX/20-libnvidia-compute-460-server_460.73.01-0ubuntu0.20.04.1_amd64.deb
 (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is 
also in package nvidia-340 340.108-0ubuntu5.20.04.1
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package 
nvidia-340 340.108-0ubuntu5.20.04.1
  InstallationDate: Installed on 2021-05-08 (0 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-460-server
  Title: package libnvidia-compute-460-server 460.73.01-0ubuntu0.20.04.1 failed 
to install/upgrade: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package 
nvidia-340 340.108-0ubuntu5.20.04.1
  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-server/+bug/1927858/+subscriptions

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

[Kernel-packages] [Bug 1929030] ProcCpuinfoMinimal.txt

[corrado venturini]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1929030/+attachment/5498932/+files/ProcCpuinfoMinimal.txt

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

Title:
  cheese image flickers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Start cheese, the image on the screen flickers and I have a lot of messages:
  (cheese:5350): cheese-WARNING **: 10:03:34.226: Internal GStreamer error: 
code not implemented.  Please file a bug at 
https://gitlab.freedesktop.org/gstreamer/gstreamer/issues/new.: 
../gst-libs/gst/video/gstvideofilter.c(296): gst_video_filter_transform (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/GstVideoConvert:vfbin-csp:
  invalid video buffer received

  I don't know if the problem is due to cheese, starting cheese and
  doing 'ubuntu-bug cheese' the bug seems opened against linux package.

  note: 
  problem occurs in both sessions Xorg and Wayland
  starting cheese as superuser the problem does not occurs

  the problem is described also in
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/696
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/689

  corrado@corrado-n3-ii-0501:~$ apt policy cheese
  cheese:
Installed: 3.38.0-3
Candidate: 3.38.0-3
Version table:
   *** 3.38.0-3 500
  500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-n3-ii-0501:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: cheese 3.38.0-3
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu66
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 20 09:56:12 2021
  InstallationDate: Installed on 2021-05-01 (18 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501)
  MachineType: Dell Inc. Inspiron 3793
  RelatedPackageVersions:
   cheese3.38.0-3
   cheese-common 3.38.0-3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0C1PF2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3793
  dmi.product.sku: 097A
  dmi.sys.vendor: Dell Inc.
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu66
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  corrado1517 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-05-01 (18 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3793
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=90e968ca-6cd0-46ed-b382-cab86d63f80c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  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:  wayland-session impish
  Uname: Linux 5.11.0-16-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: 12/17/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0C1PF2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspi

[Kernel-packages] [Bug 1929030] ProcModules.txt

[corrado venturini]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1929030/+attachment/5498935/+files/ProcModules.txt

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

Title:
  cheese image flickers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Start cheese, the image on the screen flickers and I have a lot of messages:
  (cheese:5350): cheese-WARNING **: 10:03:34.226: Internal GStreamer error: 
code not implemented.  Please file a bug at 
https://gitlab.freedesktop.org/gstreamer/gstreamer/issues/new.: 
../gst-libs/gst/video/gstvideofilter.c(296): gst_video_filter_transform (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/GstVideoConvert:vfbin-csp:
  invalid video buffer received

  I don't know if the problem is due to cheese, starting cheese and
  doing 'ubuntu-bug cheese' the bug seems opened against linux package.

  note: 
  problem occurs in both sessions Xorg and Wayland
  starting cheese as superuser the problem does not occurs

  the problem is described also in
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/696
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/689

  corrado@corrado-n3-ii-0501:~$ apt policy cheese
  cheese:
Installed: 3.38.0-3
Candidate: 3.38.0-3
Version table:
   *** 3.38.0-3 500
  500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-n3-ii-0501:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: cheese 3.38.0-3
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu66
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 20 09:56:12 2021
  InstallationDate: Installed on 2021-05-01 (18 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501)
  MachineType: Dell Inc. Inspiron 3793
  RelatedPackageVersions:
   cheese3.38.0-3
   cheese-common 3.38.0-3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0C1PF2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3793
  dmi.product.sku: 097A
  dmi.sys.vendor: Dell Inc.
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu66
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  corrado1517 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-05-01 (18 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3793
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=90e968ca-6cd0-46ed-b382-cab86d63f80c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  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:  wayland-session impish
  Uname: Linux 5.11.0-16-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: 12/17/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0C1PF2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.prod

[Kernel-packages] [Bug 1929030] PulseList.txt

[corrado venturini]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1929030/+attachment/5498936/+files/PulseList.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/1929030

Title:
  cheese image flickers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Start cheese, the image on the screen flickers and I have a lot of messages:
  (cheese:5350): cheese-WARNING **: 10:03:34.226: Internal GStreamer error: 
code not implemented.  Please file a bug at 
https://gitlab.freedesktop.org/gstreamer/gstreamer/issues/new.: 
../gst-libs/gst/video/gstvideofilter.c(296): gst_video_filter_transform (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/GstVideoConvert:vfbin-csp:
  invalid video buffer received

  I don't know if the problem is due to cheese, starting cheese and
  doing 'ubuntu-bug cheese' the bug seems opened against linux package.

  note: 
  problem occurs in both sessions Xorg and Wayland
  starting cheese as superuser the problem does not occurs

  the problem is described also in
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/696
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/689

  corrado@corrado-n3-ii-0501:~$ apt policy cheese
  cheese:
Installed: 3.38.0-3
Candidate: 3.38.0-3
Version table:
   *** 3.38.0-3 500
  500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-n3-ii-0501:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: cheese 3.38.0-3
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu66
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 20 09:56:12 2021
  InstallationDate: Installed on 2021-05-01 (18 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501)
  MachineType: Dell Inc. Inspiron 3793
  RelatedPackageVersions:
   cheese3.38.0-3
   cheese-common 3.38.0-3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0C1PF2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3793
  dmi.product.sku: 097A
  dmi.sys.vendor: Dell Inc.
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu66
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  corrado1517 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-05-01 (18 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3793
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=90e968ca-6cd0-46ed-b382-cab86d63f80c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  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:  wayland-session impish
  Uname: Linux 5.11.0-16-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: 12/17/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0C1PF2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.

[Kernel-packages] [Bug 1929030] Lsusb-v.txt

[corrado venturini]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1929030/+attachment/5498929/+files/Lsusb-v.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/1929030

Title:
  cheese image flickers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Start cheese, the image on the screen flickers and I have a lot of messages:
  (cheese:5350): cheese-WARNING **: 10:03:34.226: Internal GStreamer error: 
code not implemented.  Please file a bug at 
https://gitlab.freedesktop.org/gstreamer/gstreamer/issues/new.: 
../gst-libs/gst/video/gstvideofilter.c(296): gst_video_filter_transform (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/GstVideoConvert:vfbin-csp:
  invalid video buffer received

  I don't know if the problem is due to cheese, starting cheese and
  doing 'ubuntu-bug cheese' the bug seems opened against linux package.

  note: 
  problem occurs in both sessions Xorg and Wayland
  starting cheese as superuser the problem does not occurs

  the problem is described also in
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/696
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/689

  corrado@corrado-n3-ii-0501:~$ apt policy cheese
  cheese:
Installed: 3.38.0-3
Candidate: 3.38.0-3
Version table:
   *** 3.38.0-3 500
  500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-n3-ii-0501:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: cheese 3.38.0-3
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu66
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 20 09:56:12 2021
  InstallationDate: Installed on 2021-05-01 (18 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501)
  MachineType: Dell Inc. Inspiron 3793
  RelatedPackageVersions:
   cheese3.38.0-3
   cheese-common 3.38.0-3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0C1PF2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3793
  dmi.product.sku: 097A
  dmi.sys.vendor: Dell Inc.
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu66
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  corrado1517 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-05-01 (18 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3793
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=90e968ca-6cd0-46ed-b382-cab86d63f80c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  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:  wayland-session impish
  Uname: Linux 5.11.0-16-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: 12/17/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0C1PF2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name

[Kernel-packages] [Bug 1929030] RfKill.txt

[corrado venturini]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1929030/+attachment/5498937/+files/RfKill.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/1929030

Title:
  cheese image flickers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Start cheese, the image on the screen flickers and I have a lot of messages:
  (cheese:5350): cheese-WARNING **: 10:03:34.226: Internal GStreamer error: 
code not implemented.  Please file a bug at 
https://gitlab.freedesktop.org/gstreamer/gstreamer/issues/new.: 
../gst-libs/gst/video/gstvideofilter.c(296): gst_video_filter_transform (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/GstVideoConvert:vfbin-csp:
  invalid video buffer received

  I don't know if the problem is due to cheese, starting cheese and
  doing 'ubuntu-bug cheese' the bug seems opened against linux package.

  note: 
  problem occurs in both sessions Xorg and Wayland
  starting cheese as superuser the problem does not occurs

  the problem is described also in
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/696
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/689

  corrado@corrado-n3-ii-0501:~$ apt policy cheese
  cheese:
Installed: 3.38.0-3
Candidate: 3.38.0-3
Version table:
   *** 3.38.0-3 500
  500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-n3-ii-0501:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: cheese 3.38.0-3
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu66
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 20 09:56:12 2021
  InstallationDate: Installed on 2021-05-01 (18 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501)
  MachineType: Dell Inc. Inspiron 3793
  RelatedPackageVersions:
   cheese3.38.0-3
   cheese-common 3.38.0-3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0C1PF2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3793
  dmi.product.sku: 097A
  dmi.sys.vendor: Dell Inc.
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu66
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  corrado1517 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-05-01 (18 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3793
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=90e968ca-6cd0-46ed-b382-cab86d63f80c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  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:  wayland-session impish
  Uname: Linux 5.11.0-16-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: 12/17/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0C1PF2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: I

[Kernel-packages] [Bug 1929030] IwConfig.txt

[corrado venturini]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1929030/+attachment/5498925/+files/IwConfig.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/1929030

Title:
  cheese image flickers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Start cheese, the image on the screen flickers and I have a lot of messages:
  (cheese:5350): cheese-WARNING **: 10:03:34.226: Internal GStreamer error: 
code not implemented.  Please file a bug at 
https://gitlab.freedesktop.org/gstreamer/gstreamer/issues/new.: 
../gst-libs/gst/video/gstvideofilter.c(296): gst_video_filter_transform (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/GstVideoConvert:vfbin-csp:
  invalid video buffer received

  I don't know if the problem is due to cheese, starting cheese and
  doing 'ubuntu-bug cheese' the bug seems opened against linux package.

  note: 
  problem occurs in both sessions Xorg and Wayland
  starting cheese as superuser the problem does not occurs

  the problem is described also in
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/696
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/689

  corrado@corrado-n3-ii-0501:~$ apt policy cheese
  cheese:
Installed: 3.38.0-3
Candidate: 3.38.0-3
Version table:
   *** 3.38.0-3 500
  500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-n3-ii-0501:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: cheese 3.38.0-3
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu66
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 20 09:56:12 2021
  InstallationDate: Installed on 2021-05-01 (18 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501)
  MachineType: Dell Inc. Inspiron 3793
  RelatedPackageVersions:
   cheese3.38.0-3
   cheese-common 3.38.0-3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0C1PF2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3793
  dmi.product.sku: 097A
  dmi.sys.vendor: Dell Inc.
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu66
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  corrado1517 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-05-01 (18 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3793
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=90e968ca-6cd0-46ed-b382-cab86d63f80c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  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:  wayland-session impish
  Uname: Linux 5.11.0-16-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: 12/17/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0C1PF2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.na

[Kernel-packages] [Bug 1929030] Lspci-vt.txt

[corrado venturini]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1929030/+attachment/5498927/+files/Lspci-vt.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/1929030

Title:
  cheese image flickers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Start cheese, the image on the screen flickers and I have a lot of messages:
  (cheese:5350): cheese-WARNING **: 10:03:34.226: Internal GStreamer error: 
code not implemented.  Please file a bug at 
https://gitlab.freedesktop.org/gstreamer/gstreamer/issues/new.: 
../gst-libs/gst/video/gstvideofilter.c(296): gst_video_filter_transform (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/GstVideoConvert:vfbin-csp:
  invalid video buffer received

  I don't know if the problem is due to cheese, starting cheese and
  doing 'ubuntu-bug cheese' the bug seems opened against linux package.

  note: 
  problem occurs in both sessions Xorg and Wayland
  starting cheese as superuser the problem does not occurs

  the problem is described also in
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/696
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/689

  corrado@corrado-n3-ii-0501:~$ apt policy cheese
  cheese:
Installed: 3.38.0-3
Candidate: 3.38.0-3
Version table:
   *** 3.38.0-3 500
  500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-n3-ii-0501:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: cheese 3.38.0-3
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu66
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 20 09:56:12 2021
  InstallationDate: Installed on 2021-05-01 (18 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501)
  MachineType: Dell Inc. Inspiron 3793
  RelatedPackageVersions:
   cheese3.38.0-3
   cheese-common 3.38.0-3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0C1PF2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3793
  dmi.product.sku: 097A
  dmi.sys.vendor: Dell Inc.
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu66
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  corrado1517 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-05-01 (18 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3793
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=90e968ca-6cd0-46ed-b382-cab86d63f80c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  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:  wayland-session impish
  Uname: Linux 5.11.0-16-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: 12/17/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0C1PF2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.na

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

[corrado venturini]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1929030/+attachment/5498939/+files/WifiSyslog.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/1929030

Title:
  cheese image flickers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Start cheese, the image on the screen flickers and I have a lot of messages:
  (cheese:5350): cheese-WARNING **: 10:03:34.226: Internal GStreamer error: 
code not implemented.  Please file a bug at 
https://gitlab.freedesktop.org/gstreamer/gstreamer/issues/new.: 
../gst-libs/gst/video/gstvideofilter.c(296): gst_video_filter_transform (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/GstVideoConvert:vfbin-csp:
  invalid video buffer received

  I don't know if the problem is due to cheese, starting cheese and
  doing 'ubuntu-bug cheese' the bug seems opened against linux package.

  note: 
  problem occurs in both sessions Xorg and Wayland
  starting cheese as superuser the problem does not occurs

  the problem is described also in
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/696
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/689

  corrado@corrado-n3-ii-0501:~$ apt policy cheese
  cheese:
Installed: 3.38.0-3
Candidate: 3.38.0-3
Version table:
   *** 3.38.0-3 500
  500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-n3-ii-0501:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: cheese 3.38.0-3
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu66
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 20 09:56:12 2021
  InstallationDate: Installed on 2021-05-01 (18 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501)
  MachineType: Dell Inc. Inspiron 3793
  RelatedPackageVersions:
   cheese3.38.0-3
   cheese-common 3.38.0-3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0C1PF2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3793
  dmi.product.sku: 097A
  dmi.sys.vendor: Dell Inc.
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu66
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  corrado1517 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-05-01 (18 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3793
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=90e968ca-6cd0-46ed-b382-cab86d63f80c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  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:  wayland-session impish
  Uname: Linux 5.11.0-16-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: 12/17/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0C1PF2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.produc

[Kernel-packages] [Bug 1929030] acpidump.txt

[corrado venturini]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1929030/+attachment/5498940/+files/acpidump.txt

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

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

Title:
  cheese image flickers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Start cheese, the image on the screen flickers and I have a lot of messages:
  (cheese:5350): cheese-WARNING **: 10:03:34.226: Internal GStreamer error: 
code not implemented.  Please file a bug at 
https://gitlab.freedesktop.org/gstreamer/gstreamer/issues/new.: 
../gst-libs/gst/video/gstvideofilter.c(296): gst_video_filter_transform (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/GstVideoConvert:vfbin-csp:
  invalid video buffer received

  I don't know if the problem is due to cheese, starting cheese and
  doing 'ubuntu-bug cheese' the bug seems opened against linux package.

  note: 
  problem occurs in both sessions Xorg and Wayland
  starting cheese as superuser the problem does not occurs

  the problem is described also in
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/696
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/689

  corrado@corrado-n3-ii-0501:~$ apt policy cheese
  cheese:
Installed: 3.38.0-3
Candidate: 3.38.0-3
Version table:
   *** 3.38.0-3 500
  500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-n3-ii-0501:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: cheese 3.38.0-3
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu66
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 20 09:56:12 2021
  InstallationDate: Installed on 2021-05-01 (18 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501)
  MachineType: Dell Inc. Inspiron 3793
  RelatedPackageVersions:
   cheese3.38.0-3
   cheese-common 3.38.0-3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0C1PF2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3793
  dmi.product.sku: 097A
  dmi.sys.vendor: Dell Inc.
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu66
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  corrado1517 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-05-01 (18 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3793
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=90e968ca-6cd0-46ed-b382-cab86d63f80c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  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:  wayland-session impish
  Uname: Linux 5.11.0-16-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: 12/17/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0C1PF2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00