date:20240123

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

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

** Changed in: linux (Ubuntu Lunar)
   Importance: Undecided => Medium

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

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

** Changed in: linux (Ubuntu Mantic)
   Importance: Undecided => Medium

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

** Changed in: linux (Ubuntu Noble)
   Importance: Undecided => Medium

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

Title:
  Audio balancing setting doesn't work with the cirrus codec

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-6.1 source package in Jammy:
  In Progress
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in linux source package in Lunar:
  In Progress
Status in linux source package in Mantic:
  In Progress
Status in linux source package in Noble:
  Fix Committed

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

  Currently this patch is in the linux-next, and will be in the
  mainline kernel v6.8-rc2, there is no need to SRU this patch to Noble
  kernel, Noble kernel will have this patch automatically.

  [Impact]
  In the gnome audio setting, if we adjust balancing setting, it doesn't
  work at all on a Dell machine with cirrus codec, that is because with
  the current driver, the exported amixer controls can't be handled by
  pulseaudio.

  [Fix]
  Cherry-pick a mainline kernel patch, this could fix this issue.

  [Test]
  Booted with the patched kernel, move the bar to the left or right to
  adjust the balance, we could hear the sound from left channel or right
  channel accordingly.

  [Where problems could occur]
  This change will not create "Master Volume" amixer controls, probably
  will make the audio control malfunction, that is we couldn't control
  playback or capture volume correctly, but this regression possibility
  is very low, we already tested the patch on the machines with cirrus
  codec, they all worked well as before.

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


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

[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

Added "Signed-off-by:"

** Patch added: "0001-fbcon-Defer-AND-delay-console-takeover.patch"
   
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1970069/+attachment/5741877/+files/0001-fbcon-Defer-AND-delay-console-takeover.patch

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid

Bug description:
  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

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


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

[Kernel-packages] [Bug 1939035] Re: memory.usage_in_bytes from ubuntu_ltp.controllers.memcg_subgroup_charge times out in Hirsute 5.11

2024-01-23 Thread Po-Hsu Lin

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

** This bug has been marked a duplicate of bug 1942426
   memcg_subgroup_charge from controllers in ubuntu_ltp fails with "timed out 
on memory.usage_in_byte"

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

Title:
  memory.usage_in_bytes from
  ubuntu_ltp.controllers.memcg_subgroup_charge times out in Hirsute 5.11

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Hirsute:
  Won't Fix

Bug description:
  memory.usage_in_bytes from
  ubuntu_ltp.controllers.memcg_subgroup_charge times out when running
  with hirsute/linux 5.11.

  startup='Mon Jul 19 15:17:41 2021'
  memcg_subgroup_charge 1 TINFO: timeout per run is 0h 5m 0s
  memcg_subgroup_charge 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_subgroup_charge 1 TINFO: Test that group and subgroup have no 
relationship
  memcg_subgroup_charge 1 TINFO: Running memcg_process --mmap-anon -s 270336
  memcg_subgroup_charge 1 TINFO: Warming up pid: 443417
  memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 443417
  memcg_subgroup_charge 1 TBROK: timed out on memory.usage_in_bytes
  memcg_subgroup_charge 1 TINFO: AppArmor enabled, this may affect test results
  memcg_subgroup_charge 1 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 
(requires super/root)
  memcg_subgroup_charge 1 TINFO: loaded AppArmor profiles: none
   
  Summary:
  passed   0
  failed   0
  broken   1
  skipped  0
  warnings 0
  tag=memcg_subgroup_charge stime=1626707861 dur=11 exit=exited stat=2 core=no 
cu=19 cs=12

  
  This is not a regression as it already failed on previous releases.

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


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

[Kernel-packages] [Bug 2049635] Re: Roll UDA & ERD drivers from 525 to 535

This bug was fixed in the package nvidia-graphics-drivers-525 -
525.147.05-0ubuntu2

---
nvidia-graphics-drivers-525 (525.147.05-0ubuntu2) noble; urgency=medium

  * End of support for 525 series, transition to 535. LP: #2049635

 -- Dimitri John Ledkov   Mon, 22 Jan 2024
22:40:54 +

** Changed in: nvidia-graphics-drivers-525 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Roll UDA & ERD drivers from 525 to 535

Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

   * 525 series of drivers is now end of life, roll these to 535 via
  transitional packages

   * 535 is a longterm branch

  [ Test Plan ]

   * Install 525, 525-open, 525-server drivers with LRM using ubuntu-drivers
   * Enable proposed
   * apt full-upgrade should upgrade both userspace drivers and LRM to 
respective 535, 535-open, 535-server drivers

  [ Where problems could occur ]

   * Virtual provides in the past have caused kernel flavour switch during such 
rolls before, this remains unresolved.
   * All cards supported by 525 series of the driver are supported by the 535 
driver, thus there is no loss of functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-525/+bug/2049635/+subscriptions


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

[Kernel-packages] [Bug 2049184] Re: iwlwifi leads to system randomly hangs after suspend

2024-01-23 Thread Andy Chi

** Tags added: originate-from-2049475

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

Title:
  iwlwifi leads to system randomly hangs after suspend

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  The system randomly hangs while doing s2idle test.

  [Fix]
  Intel found the issue and provided a fix.
  
https://patchwork.kernel.org/project/linux-wireless/patch/2024045954.2d2b8b870194.I14ed76505a5cf87304e0c9cc05cc0ae85ed3bf91@changeid/

  [Test case]
  Boot up the system and run the s2idle test around 1000 times
  sudo fwts s3 --s3-multiple=1000

  [Where problems could occur]
  The fix is trivial and should no introduce any issue.

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


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

[Kernel-packages] [Bug 2038777] Re: UBSAN: array-index-out-of-bounds (drivers/net/hyperv/netvsc.c)

2024-01-23 Thread Mike Ferreira

I have a user that is affected by this bug. I am asking him to post here
with his info. I ask that you reopen this... For him = His is a VM in
Hyper-V.

RE: https://ubuntuforums.org/showthread.php?t=2494675

>From what I can see, there was a Kernel Bug that was patched for this
error upstream: https://lore.kernel.org/lkml/1691401853-26974-1-git-
send-email-ssen...@linux.microsoft.com/T/

I'm wondering if that patch applied to kernel 6.5.0-14? (Ubuntu 22.04.3)

If so or not, he is still getting this error. Maybe we could get this
kick-started back to life, to get this investigated and resolved(?)

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

Title:
  UBSAN: array-index-out-of-bounds (drivers/net/hyperv/netvsc.c)

Status in linux package in Ubuntu:
  Expired

Bug description:
  HiperV VM network problems

  [   19.259297] 

  [   19.259536] UBSAN: array-index-out-of-bounds in 
/build/linux-7dWMY3/linux-6.5.0/drivers/net/hyperv/netvsc.c:1445:41
  [   19.259715] index 1 is out of range for type 'vmtransfer_page_range [1]'
  [   19.259896] CPU: 1 PID: 1306 Comm: (udev-worker) Not tainted 
6.5.0-7-generic #7-Ubuntu
  [   19.259898] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [   19.259899] Call Trace:
  [   19.259901]  
  [   19.259902]  dump_stack_lvl+0x48/0x70
  [   19.259908]  dump_stack+0x10/0x20
  [   19.259909]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [   19.259912]  netvsc_receive+0x437/0x490 [hv_netvsc]
  [   19.259917]  netvsc_poll+0x176/0x4b0 [hv_netvsc]
  [   19.259921]  __napi_poll+0x30/0x1f0
  [   19.259924]  net_rx_action+0x181/0x2e0
  [   19.259925]  __do_softirq+0xd6/0x346
  [   19.259927]  ? _raw_spin_unlock+0xe/0x40
  [   19.259929]  __irq_exit_rcu+0x75/0xa0
  [   19.259932]  irq_exit_rcu+0xe/0x20
  [   19.259933]  sysvec_hyperv_callback+0x92/0xd0
  [   19.259935]  
  [   19.259935]  

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.8
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CrashDB: ubuntu
  Date: Sun Oct  8 23:09:45 2023
  InstallationDate: Installed on 2021-03-07 (945 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  PackageArchitecture: all
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 oct  9 20:46 seq
   crw-rw 1 root audio 116, 33 oct  9 20:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2021-03-07 (948 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  ProcFB: 0 hyperv_drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off iommu=pt
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:

Re: [Kernel-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable

2024-01-23 Thread dann frazier

On Tue, Jan 23, 2024 at 8:55 PM Michael Hudson-Doyle
<2045...@bugs.launchpad.net> wrote:
>
> Amazing debugging Dann. Until we can get a kernel fix, what's the way
> forward here? Run losetup without -P, run udevadm settle, run partprobe
> on the device (then maybe run udevadm settle again??)

That seems logical. I don't see the need for the 2nd udevadm settle -
but I also don't see the harm.

I've a test fix kernel building in a PPA. I think Łukasz mentioned
that there's a way to have an autopkgtest run on a specific kernel?
Can someone give me those steps?

  -dann

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

Title:
  livecd-rootfs uses losetup -P for theoretically reliable/synchronous
  partition setup but it's not reliable

Status in linux package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  In mantic, we migrated livecd-rootfs to use losetup -P instead of
  kpartx, with the expectation that this would give us a reliable, race-
  free way of loop-mounting partitions from a disk image during image
  build.

  In noble, we are finding that it is no longer reliable, and in fact
  fails rather often.

  It is most noticeable with riscv64 builds, which is the architecture
  where we most frequently ran into problems before with kpartx.  The
  first riscv64+generic build in noble where the expected loop partition
  device is not available is

https://launchpad.net/~ubuntu-
  cdimage/+livefs/ubuntu/noble/cpc/+build/531790

  The failure is however not unique to riscv64, and the autopkgtest for
  the latest version of livecd-rootfs (24.04.7) - an update that
  specifically tries to add more debugging code for this scenario - has
  also failed on ppc64el.

https://autopkgtest.ubuntu.com/packages/l/livecd-
  rootfs/noble/ppc64el

  The first failure happened on November 16.  While there has been an
  update to the util-linux package in noble, this did not land until
  November 23.

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

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

[Kernel-packages] [Bug 2051064] [NEW] package linux-modules-nvidia-525-6.5.0-14-generic 6.5.0-14.14~22.04.1+5 failed to install/upgrade: installed linux-modules-nvidia-525-6.5.0-14-generic package pos

2024-01-23 Thread Bipin Pandey

Public bug reported:

Graphical interface lagging due to this pack

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-modules-nvidia-525-6.5.0-14-generic 6.5.0-14.14~22.04.1+5
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Jan 24 10:06:24 2024
ErrorMessage: installed linux-modules-nvidia-525-6.5.0-14-generic package 
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2023-12-28 (26 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.21ubuntu1
 apt  2.6.0
SourcePackage: linux-restricted-modules-hwe-6.5
Title: package linux-modules-nvidia-525-6.5.0-14-generic 6.5.0-14.14~22.04.1+5 
failed to install/upgrade: installed linux-modules-nvidia-525-6.5.0-14-generic 
package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

** Affects: linux-restricted-modules-hwe-6.5 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package lunar

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

Title:
  package linux-modules-nvidia-525-6.5.0-14-generic
  6.5.0-14.14~22.04.1+5 failed to install/upgrade: installed linux-
  modules-nvidia-525-6.5.0-14-generic package post-installation script
  subprocess returned error exit status 1

Status in linux-restricted-modules-hwe-6.5 package in Ubuntu:
  New

Bug description:
  Graphical interface lagging due to this pack

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-modules-nvidia-525-6.5.0-14-generic 6.5.0-14.14~22.04.1+5
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Jan 24 10:06:24 2024
  ErrorMessage: installed linux-modules-nvidia-525-6.5.0-14-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-12-28 (26 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0
  SourcePackage: linux-restricted-modules-hwe-6.5
  Title: package linux-modules-nvidia-525-6.5.0-14-generic 
6.5.0-14.14~22.04.1+5 failed to install/upgrade: installed 
linux-modules-nvidia-525-6.5.0-14-generic package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-6.5/+bug/2051064/+subscriptions


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

[Kernel-packages] [Bug 2049976] Re: Analog VGA goes black on resume

It might be a subtle regression in the kernel then, in how it handles
VGA negotiation. But if you have the option of DisplayPort/HDMI then I
wouldn't spend time trying to figure out what might have regressed in
the kernel for VGA.

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

Title:
  Analog VGA goes black on resume

Status in linux package in Ubuntu:
  New

Bug description:
  Starting a few weeks ago after applying regular maintenance to 22.04.3
  LTS one of my two displays, an LG 22MP47HQ-P connected to my tower by
  a D-Sub cable, blinked multiple times immediately on resume from
  suspend.  My second display which is connected using HDMI works
  normally. This, of course, was merely a mild annoyance because after a
  few seconds it stopped. However in the past week that same display
  flashes on, and then goes black. I power the display off and back on
  and again it flashes on for a fraction of a second and then goes
  black. After several power cycles of the display it stays on, so again
  this is only a mild annoyance. Is this a known issue with a recent
  update?

  Specifically this is after a deep suspend, one where on unlock you
  need to press a key to get the login prompt.

  I tried updating to 23.10 but the problem is there as well.

  This bug tool does not permit reporting a problem against Wayland.

  lshw -C video
  *-display
  description: VGA compatible controller
  product: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
  vendor: Intel Corporation
  physical id: 2
  bus info: pci@:00:02.0
  logical name: /dev/fb0
  version: 06
  width: 64 bits
  clock: 33MHz
  capabilities: msi pm vga_controller bus_master cap_list rom fb
  configuration: depth=32 driver=i915 latency=0 resolution=1920,1080
  resources: irq:31 memory:f780-f7bf memory:e000-efff 
ioport:f000(size=64) memory:c-d

  /var/log/apt/history.log taken immediately after encountering the
  issue on 22.04

  Start-Date: 2024-01-02 16:01:30
  Commandline: aptdaemon role='role-commit-packages' sender=':1.7295'
  Upgrade: thunderbird:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 
1:115.6.0+build2-0ubuntu0.22.04.1), thunderbird-locale-en:amd64 
(1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1), 
thunderbird-locale-en-gb:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 
1:115.6.0+build2-0ubuntu0.22.04.1), thunderbird-locale-en-us:amd64 
(1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1), 
thunderbird-gnome-support:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 
1:115.6.0+build2-0ubuntu0.22.04.1)
  End-Date: 2024-01-02 16:01:33

  Start-Date: 2024-01-03 16:57:04
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libsqlite3-dev:amd64 (3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3), 
libsqlite3-0:amd64 (3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3), sqlite3:amd64 
(3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3)
  End-Date: 2024-01-03 16:57:05

  Start-Date: 2024-01-03 16:57:08
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: openssh-client:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6), 
openssh-server:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6), 
openssh-sftp-server:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6)
  End-Date: 2024-01-03 16:57:10

  Start-Date: 2024-01-03 16:57:13
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libnode72:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3), 
nodejs:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3), 
libnode-dev:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3)
  End-Date: 2024-01-03 16:57:14

  Start-Date: 2024-01-03 16:57:16
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: nodejs-doc:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3)
  End-Date: 2024-01-03 16:57:17

  Start-Date: 2024-01-09 20:43:19
  Commandline: aptdaemon role='role-commit-packages' sender=':1.9514'
  Install: php8.3-xml:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), 
php8.3-mbstring:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), 
php8.3-common:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), 
php8.3-intl:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic)
  Upgrade: php-common:amd64 (2:93+ubuntu22.04.1+deb.sury.org+3, 
2:94+ubuntu22.04.1+deb.sury.org+1), software-properties-common:amd64 
(0.99.22.8, 0.99.22.9), python3-software-properties:amd64 (0.99.22.8, 
0.99.22.9), php-intl:amd64 (2:8.2+93+ubuntu22.04.1+deb.sury.org+3, 
2:8.3+94+ubuntu22.04.1+deb.sury.org+1), php-mbstring:amd64 
(2:8.2+93+ubuntu22.04.1+deb.sury.org+3, 2:8.3+94+ubuntu22.04.1+deb.sury.org+1), 
software-properties-gtk:amd64 (0.99.22.8, 0.99.22.9), python3-distro-info:amd64 
(1.1ubuntu0.1, 1.1ubuntu0.2), distro-info-data:amd64 (0.52ubuntu0.5, 
0.52ubuntu0.6), linux-firmware:amd64 (20220329.git681281e4-0ubuntu3.23, 
20220329.git681281e4-0ubuntu3.24), php-xml:amd64 
(2:8.2+93+ubuntu22.04.1+deb.sury.org+3,

[Kernel-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable

2024-01-23 Thread Michael Hudson-Doyle

Amazing debugging Dann. Until we can get a kernel fix, what's the way
forward here? Run losetup without -P, run udevadm settle, run partprobe
on the device (then maybe run udevadm settle again??)

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

Title:
  livecd-rootfs uses losetup -P for theoretically reliable/synchronous
  partition setup but it's not reliable

Status in linux package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  In mantic, we migrated livecd-rootfs to use losetup -P instead of
  kpartx, with the expectation that this would give us a reliable, race-
  free way of loop-mounting partitions from a disk image during image
  build.

  In noble, we are finding that it is no longer reliable, and in fact
  fails rather often.

  It is most noticeable with riscv64 builds, which is the architecture
  where we most frequently ran into problems before with kpartx.  The
  first riscv64+generic build in noble where the expected loop partition
  device is not available is

https://launchpad.net/~ubuntu-
  cdimage/+livefs/ubuntu/noble/cpc/+build/531790

  The failure is however not unique to riscv64, and the autopkgtest for
  the latest version of livecd-rootfs (24.04.7) - an update that
  specifically tries to add more debugging code for this scenario - has
  also failed on ppc64el.

https://autopkgtest.ubuntu.com/packages/l/livecd-
  rootfs/noble/ppc64el

  The first failure happened on November 16.  While there has been an
  update to the util-linux package in noble, this did not land until
  November 23.

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


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

[Kernel-packages] [Bug 2049976] Re: Analog VGA goes black on resume

2024-01-23 Thread James Cobban

Thank you for responding.  Please bear in mind that I have been using
this same computer and this same monitor configuration for over five
years, and only in the past three weeks since I originally reported this
problem have I had this issue.  I did not change the hardware before the
problem arose.  However since my computer has two DisplayPort 1.2
outputs I will try connecting the failing display using a DisplayPort to
HDMI cable, the same way the working display is connected.

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

Title:
  Analog VGA goes black on resume

Status in linux package in Ubuntu:
  New

Bug description:
  Starting a few weeks ago after applying regular maintenance to 22.04.3
  LTS one of my two displays, an LG 22MP47HQ-P connected to my tower by
  a D-Sub cable, blinked multiple times immediately on resume from
  suspend.  My second display which is connected using HDMI works
  normally. This, of course, was merely a mild annoyance because after a
  few seconds it stopped. However in the past week that same display
  flashes on, and then goes black. I power the display off and back on
  and again it flashes on for a fraction of a second and then goes
  black. After several power cycles of the display it stays on, so again
  this is only a mild annoyance. Is this a known issue with a recent
  update?

  Specifically this is after a deep suspend, one where on unlock you
  need to press a key to get the login prompt.

  I tried updating to 23.10 but the problem is there as well.

  This bug tool does not permit reporting a problem against Wayland.

  lshw -C video
  *-display
  description: VGA compatible controller
  product: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
  vendor: Intel Corporation
  physical id: 2
  bus info: pci@:00:02.0
  logical name: /dev/fb0
  version: 06
  width: 64 bits
  clock: 33MHz
  capabilities: msi pm vga_controller bus_master cap_list rom fb
  configuration: depth=32 driver=i915 latency=0 resolution=1920,1080
  resources: irq:31 memory:f780-f7bf memory:e000-efff 
ioport:f000(size=64) memory:c-d

  /var/log/apt/history.log taken immediately after encountering the
  issue on 22.04

  Start-Date: 2024-01-02 16:01:30
  Commandline: aptdaemon role='role-commit-packages' sender=':1.7295'
  Upgrade: thunderbird:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 
1:115.6.0+build2-0ubuntu0.22.04.1), thunderbird-locale-en:amd64 
(1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1), 
thunderbird-locale-en-gb:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 
1:115.6.0+build2-0ubuntu0.22.04.1), thunderbird-locale-en-us:amd64 
(1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1), 
thunderbird-gnome-support:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 
1:115.6.0+build2-0ubuntu0.22.04.1)
  End-Date: 2024-01-02 16:01:33

  Start-Date: 2024-01-03 16:57:04
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libsqlite3-dev:amd64 (3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3), 
libsqlite3-0:amd64 (3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3), sqlite3:amd64 
(3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3)
  End-Date: 2024-01-03 16:57:05

  Start-Date: 2024-01-03 16:57:08
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: openssh-client:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6), 
openssh-server:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6), 
openssh-sftp-server:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6)
  End-Date: 2024-01-03 16:57:10

  Start-Date: 2024-01-03 16:57:13
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libnode72:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3), 
nodejs:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3), 
libnode-dev:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3)
  End-Date: 2024-01-03 16:57:14

  Start-Date: 2024-01-03 16:57:16
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: nodejs-doc:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3)
  End-Date: 2024-01-03 16:57:17

  Start-Date: 2024-01-09 20:43:19
  Commandline: aptdaemon role='role-commit-packages' sender=':1.9514'
  Install: php8.3-xml:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), 
php8.3-mbstring:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), 
php8.3-common:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), 
php8.3-intl:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic)
  Upgrade: php-common:amd64 (2:93+ubuntu22.04.1+deb.sury.org+3, 
2:94+ubuntu22.04.1+deb.sury.org+1), software-properties-common:amd64 
(0.99.22.8, 0.99.22.9), python3-software-properties:amd64 (0.99.22.8, 
0.99.22.9), php-intl:amd64 (2:8.2+93+ubuntu22.04.1+deb.sury.org+3, 
2:8.3+94+ubuntu22.04.1+deb.sury.org+1), php-mbstring:amd64 
(2:8.2+93+ubuntu22.04.1+deb.sury.org+3, 2:8.3+94+ubuntu22.04.1+deb.sury.org+1), 
software-properties-gtk:amd64 (0.99.22.8, 0.99.22.9),

[Kernel-packages] [Bug 2050955] Re: consistently fails to resume from suspend

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2050954, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)

** This bug has been marked a duplicate of bug 2050954
   consistently fails to resume from suspend

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

Title:
  consistently fails to resume from suspend

Status in linux-hwe-6.5 package in Ubuntu:
  New

Bug description:
  using integrated intel gpu no nvidia

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 08:39:14 2024
  DistUpgraded: 2022-08-02 07:50:46,100 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation RocketLake-S GT1 [UHD Graphics 750] [8086:4c8a] (rev 04) 
(prog-if 00 [VGA controller])
 Subsystem: Dell RocketLake-S GT1 [UHD Graphics 750] [1028:09c5]
  InstallationDate: Installed on 2022-04-28 (634 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: Dell Inc. XPS 8940
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=cce872cb-0478-4e9a-b49b-c63cabcbe4f6 ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to jammy on 2022-08-02 (539 days ago)
  dmi.bios.date: 09/14/2022
  dmi.bios.release: 2.10
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.10.0
  dmi.board.name: 0427JK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.10.0:bd09/14/2022:br2.10:svnDellInc.:pnXPS8940:pvr:rvnDellInc.:rn0427JK:rvrA00:cvnDellInc.:ct3:cvr:sku09C5:
  dmi.product.family: XPS
  dmi.product.name: XPS 8940
  dmi.product.sku: 09C5
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2050954] Re: Xorg freeze

Thanks for the bug report. Next time the problem happens please:

1. Reboot.

2. Run:

   journalctl -b-1 > prevboot.txt

3. Attach the resulting text file here.


** Summary changed:

- Xorg freeze
+ consistently fails to resume from suspend

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

** Changed in: ubuntu
   Status: New => Incomplete

** Package changed: ubuntu => linux-hwe-6.5 (Ubuntu)

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

Title:
  consistently fails to resume from suspend

Status in linux-hwe-6.5 package in Ubuntu:
  Incomplete

Bug description:
  consistently fails to resume from suspend

  using integrated intel gpu no nvidia

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 08:34:38 2024
  DistUpgraded: 2022-08-02 07:50:46,100 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   Intel Corporation RocketLake-S GT1 [UHD Graphics 750] [8086:4c8a] (rev 04) 
(prog-if 00 [VGA controller])
 Subsystem: Dell RocketLake-S GT1 [UHD Graphics 750] [1028:09c5]
  InstallationDate: Installed on 2022-04-28 (634 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: Dell Inc. XPS 8940
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=cce872cb-0478-4e9a-b49b-c63cabcbe4f6 ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to jammy on 2022-08-02 (539 days ago)
  dmi.bios.date: 09/14/2022
  dmi.bios.release: 2.10
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.10.0
  dmi.board.name: 0427JK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.10.0:bd09/14/2022:br2.10:svnDellInc.:pnXPS8940:pvr:rvnDellInc.:rn0427JK:rvrA00:cvnDellInc.:ct3:cvr:sku09C5:
  dmi.product.family: XPS
  dmi.product.name: XPS 8940
  dmi.product.sku: 09C5
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2051050] Re: Audio balancing setting doesn't work with the cirrus codec

** Description changed:

- This bug is for tracking purpose.
+ BugLink: https://bugs.launchpad.net/bugs/2051050
+ 
+ Currently this patch is in the linux-next, and will be in the
+ mainline kernel v6.8-rc2, there is no need to SRU this patch to Noble
+ kernel, Noble kernel will have this patch automatically.
+ 
+ [Impact]
+ In the gnome audio setting, if we adjust balancing setting, it doesn't
+ work at all on a Dell machine with cirrus codec, that is because with
+ the current driver, the exported amixer controls can't be handled by
+ pulseaudio.
+ 
+ [Fix]
+ Cherry-pick a mainline kernel patch, this could fix this issue.
+ 
+ [Test]
+ Booted with the patched kernel, move the bar to the left or right to
+ adjust the balance, we could hear the sound from left channel or right
+ channel accordingly.
+ 
+ [Where problems could occur]
+ This change will not create "Master Volume" amixer controls, probably
+ will make the audio control malfunction, that is we couldn't control
+ playback or capture volume correctly, but this regression possibility
+ is very low, we already tested the patch on the machines with cirrus
+ codec, they all worked well as before.

** Changed in: linux-oem-6.1 (Ubuntu Jammy)
   Importance: Undecided => Critical

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

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

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

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Importance: Undecided => Critical

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

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

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

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

Title:
  Audio balancing setting doesn't work with the cirrus codec

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  New
Status in linux-oem-6.1 source package in Jammy:
  In Progress
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in linux source package in Lunar:
  New
Status in linux source package in Mantic:
  New
Status in linux source package in Noble:
  Fix Committed

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

  Currently this patch is in the linux-next, and will be in the
  mainline kernel v6.8-rc2, there is no need to SRU this patch to Noble
  kernel, Noble kernel will have this patch automatically.

  [Impact]
  In the gnome audio setting, if we adjust balancing setting, it doesn't
  work at all on a Dell machine with cirrus codec, that is because with
  the current driver, the exported amixer controls can't be handled by
  pulseaudio.

  [Fix]
  Cherry-pick a mainline kernel patch, this could fix this issue.

  [Test]
  Booted with the patched kernel, move the bar to the left or right to
  adjust the balance, we could hear the sound from left channel or right
  channel accordingly.

  [Where problems could occur]
  This change will not create "Master Volume" amixer controls, probably
  will make the audio control malfunction, that is we couldn't control
  playback or capture volume correctly, but this regression possibility
  is very low, we already tested the patch on the machines with cirrus
  codec, they all worked well as before.

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


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

[Kernel-packages] [Bug 2050955] [NEW] consistently fails to resume from suspend

You have been subscribed to a public bug:

using integrated intel gpu no nvidia

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 23 08:39:14 2024
DistUpgraded: 2022-08-02 07:50:46,100 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation RocketLake-S GT1 [UHD Graphics 750] [8086:4c8a] (rev 04) 
(prog-if 00 [VGA controller])
   Subsystem: Dell RocketLake-S GT1 [UHD Graphics 750] [1028:09c5]
InstallationDate: Installed on 2022-04-28 (634 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: Dell Inc. XPS 8940
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=cce872cb-0478-4e9a-b49b-c63cabcbe4f6 ro
SourcePackage: xorg
UpgradeStatus: Upgraded to jammy on 2022-08-02 (539 days ago)
dmi.bios.date: 09/14/2022
dmi.bios.release: 2.10
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.10.0
dmi.board.name: 0427JK
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.10.0:bd09/14/2022:br2.10:svnDellInc.:pnXPS8940:pvr:rvnDellInc.:rn0427JK:rvrA00:cvnDellInc.:ct3:cvr:sku09C5:
dmi.product.family: XPS
dmi.product.name: XPS 8940
dmi.product.sku: 09C5
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy third-party-packages ubuntu uec-images
-- 
consistently fails to resume from suspend
https://bugs.launchpad.net/bugs/2050955
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-hwe-6.5 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 2050954] [NEW] consistently fails to resume from suspend

You have been subscribed to a public bug:

consistently fails to resume from suspend

using integrated intel gpu no nvidia

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 23 08:34:38 2024
DistUpgraded: 2022-08-02 07:50:46,100 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: Several times a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Since before I upgraded
GraphicsCard:
 Intel Corporation RocketLake-S GT1 [UHD Graphics 750] [8086:4c8a] (rev 04) 
(prog-if 00 [VGA controller])
   Subsystem: Dell RocketLake-S GT1 [UHD Graphics 750] [1028:09c5]
InstallationDate: Installed on 2022-04-28 (634 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: Dell Inc. XPS 8940
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=cce872cb-0478-4e9a-b49b-c63cabcbe4f6 ro
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to jammy on 2022-08-02 (539 days ago)
dmi.bios.date: 09/14/2022
dmi.bios.release: 2.10
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.10.0
dmi.board.name: 0427JK
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.10.0:bd09/14/2022:br2.10:svnDellInc.:pnXPS8940:pvr:rvnDellInc.:rn0427JK:rvrA00:cvnDellInc.:ct3:cvr:sku09C5:
dmi.product.family: XPS
dmi.product.name: XPS 8940
dmi.product.sku: 09C5
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: linux-hwe-6.5 (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug freeze jammy third-party-packages ubuntu uec-images
-- 
consistently fails to resume from suspend
https://bugs.launchpad.net/bugs/2050954
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-hwe-6.5 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 2051050] Re: Audio balancing setting doesn't work with the cirrus codec

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

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

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

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

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

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

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

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

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

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

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

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

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

** No longer affects: linux-oem-6.1 (Ubuntu Mantic)

** No longer affects: linux-oem-6.1 (Ubuntu Lunar)

** No longer affects: linux-oem-6.1 (Ubuntu Noble)

** No longer affects: linux-oem-6.5 (Ubuntu Lunar)

** No longer affects: linux-oem-6.5 (Ubuntu Mantic)

** No longer affects: linux-oem-6.5 (Ubuntu Noble)

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

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

Title:
  Audio balancing setting doesn't work with the cirrus codec

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.1 package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-oem-6.1 source package in Jammy:
  New
Status in linux-oem-6.5 source package in Jammy:
  New
Status in linux source package in Lunar:
  New
Status in linux source package in Mantic:
  New
Status in linux source package in Noble:
  Fix Committed

Bug description:
  This bug is for tracking purpose.

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


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

[Kernel-packages] [Bug 2051050] [NEW] Audio balancing setting doesn't work with the cirrus codec

Public bug reported:

This bug is for tracking purpose.

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Fix Committed

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

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

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

** Affects: linux-oem-6.1 (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: linux-oem-6.5 (Ubuntu Jammy)
 Importance: Undecided
 Status: New

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

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

** Affects: linux (Ubuntu Noble)
 Importance: Undecided
 Status: Fix Committed


** Tags: oem-priority originate-from-2047895 somerville

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

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

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

Title:
  Audio balancing setting doesn't work with the cirrus codec

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.1 package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-oem-6.1 source package in Jammy:
  New
Status in linux-oem-6.5 source package in Jammy:
  New
Status in linux source package in Lunar:
  New
Status in linux source package in Mantic:
  New
Status in linux source package in Noble:
  Fix Committed

Bug description:
  This bug is for tracking purpose.

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


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

[Kernel-packages] [Bug 2042426] Re: Introduce the new NVIDIA 545 driver series (promote to restricted)

This bug was fixed in the package nvidia-graphics-drivers-545 -
545.29.06-0ubuntu0.22.04.2

---
nvidia-graphics-drivers-545 (545.29.06-0ubuntu0.22.04.2) jammy; urgency=medium

  [ Alberto Milone ]
  * debian/templates/control.in:
- Set XB-Support to NFB for 545.

  [ Dimitri John Ledkov ]
  * Start to modernise packaging with debhelper compat 13.

nvidia-graphics-drivers-545 (545.29.06-0ubuntu0.22.04.1) jammy;
urgency=medium

  * New upstream release (LP: #2042426):
- Fixed a regression that prevented setting backlight brightness
  levels.
- Fixed a bug that could lead to UI corruption in nvidia-
  installer on systems with more than one initramfs file per
  kernel.
- Fixed a bug that caused games built on the Source 2 engine to
  hang when running under Xwayland.

nvidia-graphics-drivers-545 (545.29.02-0ubuntu0.22.04.1) jammy;
urgency=medium

  * New upstream release (LP: #2042426).

 -- Dimitri John Ledkov   Mon, 08 Jan 2024
15:06:24 +

** Changed in: nvidia-graphics-drivers-545 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

** Changed in: nvidia-graphics-drivers-545 (Ubuntu Mantic)
   Status: Fix Committed => Fix Released

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

Title:
  Introduce the new NVIDIA 545 driver series (promote to restricted)

Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-545 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-545 source package in Lunar:
  Won't Fix
Status in nvidia-graphics-drivers-545 source package in Mantic:
  Fix Released

Bug description:
  Introduce the new NVIDIA 545 driver series.

  TODO:
  Archive Admins please promote to restricted in jammy & mantic

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-lowlatency/6.5.0-17.17.1+1)

All autopkgtests for the newly accepted linux-restricted-modules-lowlatency 
(6.5.0-17.17.1+1) for mantic have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-525/525.147.05-0ubuntu0.23.10.1 (arm64)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/mantic/update_excuses.html#linux-restricted-modules-lowlatency

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2033418] Re: Ubuntu desktop does not appear on DGX Station A100 discrete GPU by default

I think comment #17 was on the right track. fbcon=map:1 should work in
theory if the Nvidia kernel driver has framebuffer support. Make sure
you're not using nofb or nomodeset which would break it.

https://www.kernel.org/doc/html/latest/fb/fbcon.html

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

Title:
  Ubuntu desktop does not appear on DGX Station A100 discrete GPU by
  default

Status in linux-nvidia package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Incomplete

Bug description:
  The DGX Station A10 has various display options. The BMC provides an
  emulated device (Aspeed controller), a physical BMC controller (NVIDIA
  Quadro T1000 Mobile), and a discrete GPU card with 4 DisplayPort
  outputs (A100 SXM4 80GB). See the user guide[*] for a diagram.

  In a default Ubuntu Desktop 22.04 ('jammy') install, nothing appears
  on the A100 DisplayPort output.

  NVIDIA DGX OS - a derivative of Ubuntu - works around this by
  installing a service that generates an xorg config file dynamically
  based on the "OnBrd/Ext VGA Select" setting (aka "dmidecode -t 11").
  I'll attach samples of those files here. Replacing the default Ubuntu
  xorg.conf file with the sample xorg-nvidia.conf file on a default
  Ubuntu Desktop install is confirmed to enable output.

  [*] https://docs.nvidia.com/dgx/dgx-station-a100-user-guide/getting-
  started-station-a100.html

  (Note: split from bug 2031367)

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules/5.15.0-94.104+1)

All autopkgtests for the newly accepted linux-restricted-modules 
(5.15.0-94.104+1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (armhf)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-gcp/5.15.0-1050.58+1)

All autopkgtests for the newly accepted linux-restricted-modules-gcp 
(5.15.0-1050.58+1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (armhf)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-gcp

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2050098] Re: cgroup2 broken since 5.15.0-90-generic?

@hedrick: Regarding that workaround you mentioned above, I would guess
it only suppresses the error message but doesn't fix the problem with
broken cgroup confinement. Is that correct?

I've done more testing and have identified the following commit:
 
https://github.com/torvalds/linux/commit/2516deeb872ab9dda3bf4c66cf24b1ee900f25bf

Reverting that one (and the follow-up
683d2969a0820072ddc05dbcc667664f7a34ac90) makes things work again as far
as I can tell. I haven't tested that on the Ubuntu source yet, so far
only on upstream 5.15.127.

The only thing I can imagine regarding why this works with newer kernels
is that this is an incomplete backport.

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

Title:
  cgroup2 broken since 5.15.0-90-generic?

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  We're using Slurm workload manager in a cluster with Ubuntu 22.04 and
  the linux-generic kernel (amd64). We  use cgroups (cgroup2) for
  resource allocation with Slurm. With kernel version

  linux-image-5.15.0-91-generic 5.15.0-91.101
  amd64

  I'm seeing a new issue. This must have been introduced recently, I can
  confirm that with kernel 5.15.0-88-generic the issue does not exist.
  When I request a single GPU on a node with kernel 5.15.0-88-generic
  all is well:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  GPU 0: NVIDIA [...]

  Instead with kernel 5.15.0-91-generic:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  slurmstepd: error: load_ebpf_prog: BPF load error (No space left on device). 
Please check your system limits (MEMLOCK).
  GPU 0: NVIDIA [...]
  GPU 1: NVIDIA [...]
  GPU 2: NVIDIA [...]
  GPU 3: NVIDIA [...]
  GPU 4: NVIDIA [...]
  GPU 5: NVIDIA [...]
  GPU 6: NVIDIA [...]
  GPU 7: NVIDIA [...]

  So I get this error regarding MEMLOCK limit and see all GPUs in the
  system instead of only the one requested. Hence I assume the problem
  is related to cgroups.

  $ cat /proc/version_signature
  Ubuntu 5.15.0-91.101-generic 5.15.131

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


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

[Kernel-packages] [Bug 2051044] [NEW] missing depends on libnvidia-fbc1-545

Public bug reported:

[ Impact ]

 * missing libnvidia-fbc1-545 library

[ Test Plan ]

 * install 545 drivers, and observe that libnvidia-fbc1-545 is installed

[ Where problems could occur ]

 * this fixes regression versus all other driver series

[ Other Info ]
 
Removal of ppc64le packaging incorrectly dropped

> Depends: libnvidia-fbc1-545 (= ${binary:Version}) [!ppc64el],

when clearly only the `[!ppc64el]` tag should have been dropped, as this
library does exist on all supported architectures.

reported via irc

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

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

** Also affects: nvidia-graphics-drivers-545 (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-545 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-545 (Ubuntu Noble)
   Importance: Undecided
   Status: New

** No longer affects: nvidia-graphics-drivers-545 (Ubuntu Jammy)

** No longer affects: nvidia-graphics-drivers-545 (Ubuntu Mantic)

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

Title:
  missing depends on libnvidia-fbc1-545

Status in nvidia-graphics-drivers-545 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-545 source package in Noble:
  New

Bug description:
  [ Impact ]

   * missing libnvidia-fbc1-545 library

  [ Test Plan ]

   * install 545 drivers, and observe that libnvidia-fbc1-545 is
  installed

  [ Where problems could occur ]

   * this fixes regression versus all other driver series

  [ Other Info ]
   
  Removal of ppc64le packaging incorrectly dropped

  > Depends: libnvidia-fbc1-545 (= ${binary:Version}) [!ppc64el],

  when clearly only the `[!ppc64el]` tag should have been dropped, as
  this library does exist on all supported architectures.

  reported via irc

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


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

[Kernel-packages] [Bug 2049688] Re: nvidia stoped working, , package nvidia-dkms-390 390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subp

2024-01-23 Thread John Dyer

copy of log file

** Attachment added: "gpu-manager-switch.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049688/+attachment/5741801/+files/gpu-manager-switch.log

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

Title:
  nvidia stoped working,, package nvidia-dkms-390
  390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed nvidia-
  dkms-390 package post-installation script subprocess returned error
  exit status 10

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

Bug description:
  after latest update on 22.04 nvidia driver stoped working, gpu not
  found, cannot reinstall, even after upgrade I get : package nvidia-
  dkms-390 390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed
  nvidia-dkms-390 package post-installation script subprocess returned
  error exit status 10.

  I also had errors with dependencies, when trying to reinstall and with
  kernel headers.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: nvidia-dkms-390 390.157-0ubuntu5.23.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Jan 17 22:54:39 2024
  ErrorMessage: installed nvidia-dkms-390 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2023-11-28 (50 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-390
  Title: package nvidia-dkms-390 390.157-0ubuntu5.23.04.1 failed to 
install/upgrade: installed nvidia-dkms-390 package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: Upgraded to lunar on 2024-01-17 (0 days ago)

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws/5.15.0.1053.52)

All autopkgtests for the newly accepted linux-meta-aws (5.15.0.1053.52) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

dm-writeboost/2.2.13-1ubuntu3 (amd64, arm64)
dpdk-kmods/0~20220111+git-1ubuntu1~22.04.1 (amd64, arm64)
systemd/249.11-0ubuntu3.12 (amd64, arm64)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-aws

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2049537] Re: Pull request for: peer-memory, ACPI thermal issues and coresight etm4x issues

2024-01-23 Thread Ubuntu Kernel Bot

This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1011.11 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-jammy-linux-nvidia-6.5' to
'verification-done-jammy-linux-nvidia-6.5'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-nvidia-6.5' to
'verification-failed-jammy-linux-nvidia-6.5'.


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: kernel-spammed-jammy-linux-nvidia-6.5-v2 
verification-needed-jammy-linux-nvidia-6.5

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

Title:
  Pull request for: peer-memory, ACPI thermal issues and coresight
  etm4x issues

Status in linux-nvidia-6.5 package in Ubuntu:
  Fix Committed

Bug description:
  * Add support of "Thermal fast Sampling Period (_TFP)" for passive cooling.
  * Finer grained CPU throttling
  * The peer_memory_client scheme allows a driver to register with the ib_umem
  system that it has the ability to understand user virtual address ranges that 
are not compatible with get_user_pages(). For instance VMAs created with 
io_remap_pfn_range(), or other driver special VMA.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules/5.15.0-94.104)

All autopkgtests for the newly accepted linux-restricted-modules 
(5.15.0-94.104) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (armhf)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-nvidia/5.15.0-1044.44)

All autopkgtests for the newly accepted linux-restricted-modules-nvidia 
(5.15.0-1044.44) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (armhf)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-nvidia

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules/6.2.0-41.42)

All autopkgtests for the newly accepted linux-restricted-modules (6.2.0-41.42) 
for lunar have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-525/525.147.05-0ubuntu0.23.04.1 (arm64)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/lunar/update_excuses.html#linux-restricted-modules

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2033418] Re: Ubuntu desktop does not appear on DGX Station A100 discrete GPU by default

2024-01-23 Thread dann frazier

We're checking to see if the system behaves the same with NVIDIA's
BaseOS. If it is, we'll probably move on and this can move to Won't Fix.

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

Title:
  Ubuntu desktop does not appear on DGX Station A100 discrete GPU by
  default

Status in linux-nvidia package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Incomplete

Bug description:
  The DGX Station A10 has various display options. The BMC provides an
  emulated device (Aspeed controller), a physical BMC controller (NVIDIA
  Quadro T1000 Mobile), and a discrete GPU card with 4 DisplayPort
  outputs (A100 SXM4 80GB). See the user guide[*] for a diagram.

  In a default Ubuntu Desktop 22.04 ('jammy') install, nothing appears
  on the A100 DisplayPort output.

  NVIDIA DGX OS - a derivative of Ubuntu - works around this by
  installing a service that generates an xorg config file dynamically
  based on the "OnBrd/Ext VGA Select" setting (aka "dmidecode -t 11").
  I'll attach samples of those files here. Replacing the default Ubuntu
  xorg.conf file with the sample xorg-nvidia.conf file on a default
  Ubuntu Desktop install is confirmed to enable output.

  [*] https://docs.nvidia.com/dgx/dgx-station-a100-user-guide/getting-
  started-station-a100.html

  (Note: split from bug 2031367)

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


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

[Kernel-packages] [Bug 2051036] [NEW] Touchpad doesn't work

2024-01-23 Thread Carles

Public bug reported:

Touchpad is not working with ubuntu 22.04

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-91-generic 5.15.0-91.101
ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131
Uname: Linux 5.15.0-91-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  carles 1279 F pulseaudio
 /dev/snd/controlC1:  carles 1279 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 23 22:49:24 2024
InstallationDate: Installed on 2023-08-04 (172 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: TOSHIBA SATELLITE L855
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-91-generic 
root=UUID=e71a1c26-d243-481c-9fe3-e858ef16f63d ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-91-generic N/A
 linux-backports-modules-5.15.0-91-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.24
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2023-08-04 (172 days ago)
dmi.bios.date: 04/22/2013
dmi.bios.release: 6.70
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.70
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: MP
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.ec.firmware.release: 1.70
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.70:bd04/22/2013:br6.70:efr1.70:svnTOSHIBA:pnSATELLITEL855:pvrPSKACE-015007CE:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKACE-015007CE:
dmi.product.family: Dakar 10F/FG
dmi.product.name: SATELLITE L855
dmi.product.sku: PSKACE-015007CE
dmi.product.version: PSKACE-015007CE
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-bug jammy

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

Title:
  Touchpad doesn't work

Status in linux package in Ubuntu:
  New

Bug description:
  Touchpad is not working with ubuntu 22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-91-generic 5.15.0-91.101
  ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131
  Uname: Linux 5.15.0-91-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  carles 1279 F pulseaudio
   /dev/snd/controlC1:  carles 1279 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 22:49:24 2024
  InstallationDate: Installed on 2023-08-04 (172 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: TOSHIBA SATELLITE L855
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-91-generic 
root=UUID=e71a1c26-d243-481c-9fe3-e858ef16f63d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-91-generic N/A
   linux-backports-modules-5.15.0-91-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.24
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2023-08-04 (172 days ago)
  dmi.bios.date: 04/22/2013
  dmi.bios.release: 6.70
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.70
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.ec.firmware.release: 1.70
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.70:bd04/22/2013:br6.70:efr1.70:svnTOSHIBA:pnSATELLITEL855:pvrPSKACE-015007CE:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKACE-015007CE:
  dmi.product.family: Dakar 10F/FG
  dmi.product.name: SATELLITE L855
  dmi.product.sku: PSKACE-015007CE
  dmi.product.version: PSKACE-015007CE
  dmi.sys.vendor: TOSHIBA

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


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

[Kernel-packages] [Bug 2049635] Re: Roll UDA & ERD drivers from 525 to 535

This bug was fixed in the package libnvidia-nscq-525 -
525.147.05-0ubuntu2

---
libnvidia-nscq-525 (525.147.05-0ubuntu2) noble; urgency=medium

  * End of support for 525 series, transition to 535. LP: #2049635

 -- Dimitri John Ledkov   Tue, 23 Jan 2024
19:27:17 +

** Changed in: libnvidia-nscq-525 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Roll UDA & ERD drivers from 525 to 535

Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

   * 525 series of drivers is now end of life, roll these to 535 via
  transitional packages

   * 535 is a longterm branch

  [ Test Plan ]

   * Install 525, 525-open, 525-server drivers with LRM using ubuntu-drivers
   * Enable proposed
   * apt full-upgrade should upgrade both userspace drivers and LRM to 
respective 535, 535-open, 535-server drivers

  [ Where problems could occur ]

   * Virtual provides in the past have caused kernel flavour switch during such 
rolls before, this remains unresolved.
   * All cards supported by 525 series of the driver are supported by the 535 
driver, thus there is no loss of functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-525/+bug/2049635/+subscriptions


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-nvidia-6.5/6.5.0.1010.11)

All autopkgtests for the newly accepted linux-meta-nvidia-6.5 (6.5.0.1010.11) 
for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

linux-nvidia-6.5/6.5.0-1010.10 (arm64)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-nvidia-6.5

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2050098] Re: cgroup2 broken since 5.15.0-90-generic?

Furthermore, slurm doesn't actually use the log data that the kernel
would pass back. So my code is better even with kernels that work. Why
pass a log buffer that you aren't going to use?

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

Title:
  cgroup2 broken since 5.15.0-90-generic?

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  We're using Slurm workload manager in a cluster with Ubuntu 22.04 and
  the linux-generic kernel (amd64). We  use cgroups (cgroup2) for
  resource allocation with Slurm. With kernel version

  linux-image-5.15.0-91-generic 5.15.0-91.101
  amd64

  I'm seeing a new issue. This must have been introduced recently, I can
  confirm that with kernel 5.15.0-88-generic the issue does not exist.
  When I request a single GPU on a node with kernel 5.15.0-88-generic
  all is well:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  GPU 0: NVIDIA [...]

  Instead with kernel 5.15.0-91-generic:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  slurmstepd: error: load_ebpf_prog: BPF load error (No space left on device). 
Please check your system limits (MEMLOCK).
  GPU 0: NVIDIA [...]
  GPU 1: NVIDIA [...]
  GPU 2: NVIDIA [...]
  GPU 3: NVIDIA [...]
  GPU 4: NVIDIA [...]
  GPU 5: NVIDIA [...]
  GPU 6: NVIDIA [...]
  GPU 7: NVIDIA [...]

  So I get this error regarding MEMLOCK limit and see all GPUs in the
  system instead of only the one requested. Hence I assume the problem
  is related to cgroups.

  $ cat /proc/version_signature
  Ubuntu 5.15.0-91.101-generic 5.15.131

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


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

[Kernel-packages] [Bug 2028985] Re: package libnvidia-compute-535-server (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/aarch64-linux-gnu/libcuda.so', which is also in packag

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

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

Title:
  package libnvidia-compute-535-server (not installed) failed to
  install/upgrade: trying to overwrite '/usr/lib/aarch64-linux-
  gnu/libcuda.so', which is also in package nvidia-l4t-cuda
  35.3.1-20230319081403

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

Bug description:
  in an attempt to activate pytorch within current enviroment. after a
  failure to install nvidia-smi

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libnvidia-compute-535-server (not installed)
  Uname: Linux 5.10.104-tegra aarch64
  ApportVersion: 2.20.11-0ubuntu27.27
  AptOrdering:
   libnvidia-compute-535-server:arm64: Install
   nvidia-utils-535-server:arm64: Install
   NULL: ConfigurePending
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Fri Jul 28 14:54:25 2023
  DpkgTerminalLog:
   Preparing to unpack 
.../libnvidia-compute-535-server_535.54.03-0ubuntu0.20.04.1_arm64.deb ...
   Unpacking libnvidia-compute-535-server:arm64 (535.54.03-0ubuntu0.20.04.1) ...
   [1mdpkg:[0m error processing archive 
/var/cache/apt/archives/libnvidia-compute-535-server_535.54.03-0ubuntu0.20.04.1_arm64.deb
 (--unpack):
trying to overwrite '/usr/lib/aarch64-linux-gnu/libcuda.so', which is also 
in package nvidia-l4t-cuda 35.3.1-20230319081403
  ErrorMessage: trying to overwrite '/usr/lib/aarch64-linux-gnu/libcuda.so', 
which is also in package nvidia-l4t-cuda 35.3.1-20230319081403
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: nvidia-graphics-drivers-535-server
  Title: package libnvidia-compute-535-server (not installed) failed to 
install/upgrade: trying to overwrite '/usr/lib/aarch64-linux-gnu/libcuda.so', 
which is also in package nvidia-l4t-cuda 35.3.1-20230319081403
  UpgradeStatus: Upgraded to focal on 2023-07-24 (4 days ago)

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


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

[Kernel-packages] [Bug 2033418] Re: Ubuntu desktop does not appear on DGX Station A100 discrete GPU by default

Newer drivers are available now, and i'm not sure what is expected here.

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

Title:
  Ubuntu desktop does not appear on DGX Station A100 discrete GPU by
  default

Status in linux-nvidia package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Incomplete

Bug description:
  The DGX Station A10 has various display options. The BMC provides an
  emulated device (Aspeed controller), a physical BMC controller (NVIDIA
  Quadro T1000 Mobile), and a discrete GPU card with 4 DisplayPort
  outputs (A100 SXM4 80GB). See the user guide[*] for a diagram.

  In a default Ubuntu Desktop 22.04 ('jammy') install, nothing appears
  on the A100 DisplayPort output.

  NVIDIA DGX OS - a derivative of Ubuntu - works around this by
  installing a service that generates an xorg config file dynamically
  based on the "OnBrd/Ext VGA Select" setting (aka "dmidecode -t 11").
  I'll attach samples of those files here. Replacing the default Ubuntu
  xorg.conf file with the sample xorg-nvidia.conf file on a default
  Ubuntu Desktop install is confirmed to enable output.

  [*] https://docs.nvidia.com/dgx/dgx-station-a100-user-guide/getting-
  started-station-a100.html

  (Note: split from bug 2031367)

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


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

[Kernel-packages] [Bug 2049635] Re: Roll UDA & ERD drivers from 525 to 535

** Package changed: fabric-manager-535 (Ubuntu) => fabric-manager-525
(Ubuntu)

** Package changed: libnvidia-nscq-535 (Ubuntu) => libnvidia-nscq-525
(Ubuntu)

** Package changed: nvidia-graphics-drivers-535-server (Ubuntu) =>
nvidia-graphics-drivers-525-server (Ubuntu)

** No longer affects: nvidia-graphics-drivers-535 (Ubuntu)

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

Title:
  Roll UDA & ERD drivers from 525 to 535

Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-525 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  New

Bug description:
  [ Impact ]

   * 525 series of drivers is now end of life, roll these to 535 via
  transitional packages

   * 535 is a longterm branch

  [ Test Plan ]

   * Install 525, 525-open, 525-server drivers with LRM using ubuntu-drivers
   * Enable proposed
   * apt full-upgrade should upgrade both userspace drivers and LRM to 
respective 535, 535-open, 535-server drivers

  [ Where problems could occur ]

   * Virtual provides in the past have caused kernel flavour switch during such 
rolls before, this remains unresolved.
   * All cards supported by 525 series of the driver are supported by the 535 
driver, thus there is no loss of functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-525/+bug/2049635/+subscriptions


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

[Kernel-packages] [Bug 2050098] Re: cgroup2 broken since 5.15.0-90-generic?

However the same patch is in 6.5. I give up. At least I have a
workaround.

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

Title:
  cgroup2 broken since 5.15.0-90-generic?

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  We're using Slurm workload manager in a cluster with Ubuntu 22.04 and
  the linux-generic kernel (amd64). We  use cgroups (cgroup2) for
  resource allocation with Slurm. With kernel version

  linux-image-5.15.0-91-generic 5.15.0-91.101
  amd64

  I'm seeing a new issue. This must have been introduced recently, I can
  confirm that with kernel 5.15.0-88-generic the issue does not exist.
  When I request a single GPU on a node with kernel 5.15.0-88-generic
  all is well:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  GPU 0: NVIDIA [...]

  Instead with kernel 5.15.0-91-generic:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  slurmstepd: error: load_ebpf_prog: BPF load error (No space left on device). 
Please check your system limits (MEMLOCK).
  GPU 0: NVIDIA [...]
  GPU 1: NVIDIA [...]
  GPU 2: NVIDIA [...]
  GPU 3: NVIDIA [...]
  GPU 4: NVIDIA [...]
  GPU 5: NVIDIA [...]
  GPU 6: NVIDIA [...]
  GPU 7: NVIDIA [...]

  So I get this error regarding MEMLOCK limit and see all GPUs in the
  system instead of only the one requested. Hence I assume the problem
  is related to cgroups.

  $ cat /proc/version_signature
  Ubuntu 5.15.0-91.101-generic 5.15.131

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


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

[Kernel-packages] [Bug 2033418] Re: Ubuntu desktop does not appear on DGX Station A100 discrete GPU by default

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

** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
   Status: New => Incomplete

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

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

Title:
  Ubuntu desktop does not appear on DGX Station A100 discrete GPU by
  default

Status in linux-nvidia package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Incomplete

Bug description:
  The DGX Station A10 has various display options. The BMC provides an
  emulated device (Aspeed controller), a physical BMC controller (NVIDIA
  Quadro T1000 Mobile), and a discrete GPU card with 4 DisplayPort
  outputs (A100 SXM4 80GB). See the user guide[*] for a diagram.

  In a default Ubuntu Desktop 22.04 ('jammy') install, nothing appears
  on the A100 DisplayPort output.

  NVIDIA DGX OS - a derivative of Ubuntu - works around this by
  installing a service that generates an xorg config file dynamically
  based on the "OnBrd/Ext VGA Select" setting (aka "dmidecode -t 11").
  I'll attach samples of those files here. Replacing the default Ubuntu
  xorg.conf file with the sample xorg-nvidia.conf file on a default
  Ubuntu Desktop install is confirmed to enable output.

  [*] https://docs.nvidia.com/dgx/dgx-station-a100-user-guide/getting-
  started-station-a100.html

  (Note: split from bug 2031367)

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


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

[Kernel-packages] [Bug 2050098] Re: cgroup2 broken since 5.15.0-90-generic?

>From timing I suspect kernel.org
2dcb31e65d26a29a6842500e904907180e80a091, but I don't understand the
code so I can't tell whether there's actually a problem there.

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

Title:
  cgroup2 broken since 5.15.0-90-generic?

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  We're using Slurm workload manager in a cluster with Ubuntu 22.04 and
  the linux-generic kernel (amd64). We  use cgroups (cgroup2) for
  resource allocation with Slurm. With kernel version

  linux-image-5.15.0-91-generic 5.15.0-91.101
  amd64

  I'm seeing a new issue. This must have been introduced recently, I can
  confirm that with kernel 5.15.0-88-generic the issue does not exist.
  When I request a single GPU on a node with kernel 5.15.0-88-generic
  all is well:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  GPU 0: NVIDIA [...]

  Instead with kernel 5.15.0-91-generic:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  slurmstepd: error: load_ebpf_prog: BPF load error (No space left on device). 
Please check your system limits (MEMLOCK).
  GPU 0: NVIDIA [...]
  GPU 1: NVIDIA [...]
  GPU 2: NVIDIA [...]
  GPU 3: NVIDIA [...]
  GPU 4: NVIDIA [...]
  GPU 5: NVIDIA [...]
  GPU 6: NVIDIA [...]
  GPU 7: NVIDIA [...]

  So I get this error regarding MEMLOCK limit and see all GPUs in the
  system instead of only the one requested. Hence I assume the problem
  is related to cgroups.

  $ cat /proc/version_signature
  Ubuntu 5.15.0-91.101-generic 5.15.131

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


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

[Kernel-packages] [Bug 2050098] Re: cgroup2 broken since 5.15.0-90-generic?

In src/plugins/cgroup/v2/ebpf.c, comment out logging. I.e. change

attr.log_level = 1; 
attr.log_buf = (size_t) log;
attr.log_size = sizeof(log);

to

attr.log_level = 0;
attr.log_buf = NULL;
attr.log_size = 0;

I think you'll find that this fixes it.

I have no idea why this is a problem in this specific kernel release

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

Title:
  cgroup2 broken since 5.15.0-90-generic?

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  We're using Slurm workload manager in a cluster with Ubuntu 22.04 and
  the linux-generic kernel (amd64). We  use cgroups (cgroup2) for
  resource allocation with Slurm. With kernel version

  linux-image-5.15.0-91-generic 5.15.0-91.101
  amd64

  I'm seeing a new issue. This must have been introduced recently, I can
  confirm that with kernel 5.15.0-88-generic the issue does not exist.
  When I request a single GPU on a node with kernel 5.15.0-88-generic
  all is well:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  GPU 0: NVIDIA [...]

  Instead with kernel 5.15.0-91-generic:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  slurmstepd: error: load_ebpf_prog: BPF load error (No space left on device). 
Please check your system limits (MEMLOCK).
  GPU 0: NVIDIA [...]
  GPU 1: NVIDIA [...]
  GPU 2: NVIDIA [...]
  GPU 3: NVIDIA [...]
  GPU 4: NVIDIA [...]
  GPU 5: NVIDIA [...]
  GPU 6: NVIDIA [...]
  GPU 7: NVIDIA [...]

  So I get this error regarding MEMLOCK limit and see all GPUs in the
  system instead of only the one requested. Hence I assume the problem
  is related to cgroups.

  $ cat /proc/version_signature
  Ubuntu 5.15.0-91.101-generic 5.15.131

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


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

[Kernel-packages] [Bug 2049603] Re: nvidia-dkms-535 FTBS on noble with the latest 6.7 kernel on arm64

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Noble)
   Status: New => Fix Released

** Also affects: nvidia-graphics-drivers-535-server (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Noble)
   Status: New => Fix Released

** Changed in: nvidia-graphics-drivers-545 (Ubuntu Noble)
   Status: New => Triaged

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

Title:
  nvidia-dkms-535 FTBS on noble with the latest 6.7 kernel on arm64

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-535 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-545 source package in Noble:
  Triaged

Bug description:
  [Impact]

  It looks like nvidia-dkms-535 is using a symbol that became GPL-only
  in the latest 6.7 kernel, causing the following build error:

  # MODPOST <>/build/nvidia/535.146.02/build/Module.symvers
 scripts/mod/modpost -M -m -a  -o 
<>/build/nvidia/535.146.02/build/Module.symvers -T 
<>/build/nvidia/535.146.02/build/modules.order -i Module.symvers -e 
  ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 
'screen_info'

  This change was introduced by: b8466fe82b79 ("efi: move screen_info
  into efi init code")

  This happens only on arm64, where the symbol is defined.

  [Fix]

  Avoid using screen_info in the nvidia-dkms-535 driver.

  [Regression potential]

  We may disable certain features in the 535 driver, or even have an
  unusable driver, unless a proper workaround/solution is provided.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/5.4.0.1106.102)

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

dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64)
evdi/1.9.1-1ubuntu4~20.04.2 (amd64)
lttng-modules/2.12.5-1ubuntu2~20.04.5 (amd64)
oss4/4.2-build2010-5ubuntu6~20.04.3 (amd64)
rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.4 (amd64)
rtl8821ce/5.5.2.1-0ubuntu4~20.04.5 (amd64)
sl-modem/2.9.11~20110321-16ubuntu1 (amd64)
v4l2loopback/0.12.3-1ubuntu0.4 (amd64)
virtualbox/6.1.48-dfsg-1~ubuntu1.20.04.1 (amd64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2028770] Re: package nvidia-dkms-525-server (not installed) failed to install/upgrade: подпроцесс из пакета nvidia-dkms-525-server установлен сценарий post-installation возврати

no support is provided for non-ubuntu-archive kernels.

please use precompiled nvidia drivers for Ubuntu Archive kernel via
`ubuntu-drivers`

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

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

Title:
  package nvidia-dkms-525-server (not installed) failed to
  install/upgrade: подпроцесс из пакета nvidia-dkms-525-server
  установлен сценарий post-installation возвратил код ошибки 10

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

Bug description:
  1

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: nvidia-dkms-525-server (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17
  Uname: Linux 5.19.0-50-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Jul 26 11:57:56 2023
  ErrorMessage: подпроцесс из пакета nvidia-dkms-525-server установлен сценарий 
post-installation возвратил код ошибки 10
  InstallationDate: Installed on 2023-04-13 (104 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.9
  SourcePackage: nvidia-graphics-drivers-525-server
  Title: package nvidia-dkms-525-server (not installed) failed to 
install/upgrade: подпроцесс из пакета nvidia-dkms-525-server установлен 
сценарий post-installation возвратил код ошибки 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2029934] Re: arm64 AWS host hangs during modprobe nvidia on lunar and mantic

since then, we had multiple glibc srus; kernel sru's and most recently
new release of 535-server.

can i request for this to be retested again?

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

Title:
  arm64 AWS host hangs during modprobe nvidia on lunar and mantic

Status in linux-aws package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  New

Bug description:
  Loading the nvidia driver dkms modules with "modprove nvidia" will
  result in the host hanging and being completely unusable. This was
  reproduced using both the linux generic and linux-aws kernels on lunar
  and mantic using an AWS g5g.xlarge instance.

  To reproduce using the generic kernel:
  # Deploy a arm64 host with an nvidia gpu, such as an AWS g5g.xlarge.

  # Install the linux generic kernel from lunar-updates:
  $ sudo DEBIAN_FRONTEND=noninteractive apt-get install -y -o 
DPkg::Options::=--force-confold linux-generic

  # Boot to the linux-generic kernel (this can be accomplished by removing the 
existing kernel, in this case it was the linux-aws 6.2.0-1008-aws kernel)
  $ sudo DEBIAN_FRONTEND=noninteractive apt-get purge -y -o 
DPkg::Options::=--force-confold linux-aws linux-aws-headers-6.2.0-1008 
linux-headers-6.2.0-1008-aws linux-headers-aws linux-image-6.2.0-1008-aws 
linux-image-aws linux-modules-6.2.0-1008-aws  linux-headers-6.2.0-1008-aws 
linux-image-6.2.0-1008-aws linux-modules-6.2.0-1008-aws
  $ reboot

  # Install the Nvidia 535-server driver DKMS package:
  $ sudo DEBIAN_FRONTEND=noninteractive apt-get install -y 
nvidia-driver-535-server

  # Enable the driver
  $ sudo modprobe nvidia

  # At this point the system will hang and never return.
  # A reboot instead of a modprobe will result in a system that never boots up 
all the way. I was able to recover the console logs from such a system and 
found (the full captured log is attached):

  [1.964942] nvidia: loading out-of-tree module taints kernel.
  [1.965475] nvidia: module license 'NVIDIA' taints kernel.
  [1.965905] Disabling lock debugging due to kernel taint
  [1.980905] nvidia: module verification failed: signature and/or required 
key missing - tainting kernel
  [2.012067] nvidia-nvlink: Nvlink Core is being initialized, major device 
number 510
  [2.012715] 
  [   62.025143] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
  [   62.025807] rcu:   3-...0: (14 ticks this GP) 
idle=c04c/1/0x4000 softirq=653/654 fqs=3301
  [   62.026516](detected by 0, t=15003 jiffies, g=-699, q=216 ncpus=4)
  [   62.027018] Task dump for CPU 3:
  [   62.027290] task:systemd-udevd   state:R  running task stack:0 
pid:164   ppid:144flags:0x000e
  [   62.028066] Call trace:
  [   62.028273]  __switch_to+0xbc/0x100
  [   62.028567]  0x228
  Timed out for waiting the udev queue being empty.
  Timed out for waiting the udev queue being empty.
  [  242.045143] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
  [  242.045655] rcu:   3-...0: (14 ticks this GP) 
idle=c04c/1/0x4000 softirq=653/654 fqs=12303
  [  242.046373](detected by 1, t=60008 jiffies, g=-699, q=937 ncpus=4)
  [  242.046874] Task dump for CPU 3:
  [  242.047146] task:systemd-udevd   state:R  running task stack:0 
pid:164   ppid:144flags:0x000f
  [  242.047922] Call trace:
  [  242.048128]  __switch_to+0xbc/0x100
  [  242.048417]  0x228
  Timed out for waiting the udev queue being empty.
  Begin: Loading essential drivers ... [  384.001142] watchdog: BUG: soft 
lockup - CPU#2 stuck for 22s! [modprobe:215]
  [  384.001738] Modules linked in: nvidia(POE+) crct10dif_ce video polyval_ce 
polyval_generic drm_kms_helper ghash_ce syscopyarea sm4 sysfillrect sha2_ce 
sysimgblt sha256_arm64 sha1_ce drm nvme nvme_core ena nvme_common aes_neon_bs 
aes_neon_blk aes_ce_blk aes_ce_cipher
  [  384.003513] CPU: 2 PID: 215 Comm: modprobe Tainted: P   OE  
6.2.0-26-generic #26-Ubuntu
  [  384.004210] Hardware name: Amazon EC2 g5g.xlarge/, BIOS 1.0 11/1/2018
  [  384.004715] pstate: 8045 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
  [  384.005259] pc : smp_call_function_many_cond+0x1b4/0x4b4
  [  384.005683] lr : smp_call_function_many_cond+0x1d0/0x4b4
  [  384.006108] sp : 889a3a70
  [  384.006381] x29: 889a3a70 x28: 0003 x27: 
00056d1fafa0
  [  384.006954] x26: 00056d1d76c8 x25: c87cf18bdd10 x24: 
0003
  [  384.007527] x23: 0001 x22: 00056d1d76c8 x21: 
c87cf18c2690
  [  384.008086] x20: 00056d1fafa0 x19: 00056d1d76c0 x18: 
8896d058
  [  384.008645] x17:  x16:

[Kernel-packages] [Bug 2016329] Re: package nvidia-dkms-525-server 525.105.17-0ubuntu0.22.10.1 failed to install/upgrade: nvidia-dkms-525-server paketi post-installation betiği kuruldu alt süreci 10 h

please reboot, and upgrade your kernel.

please use precompiled nvidia drivers for Ubuntu Archive kernels via
`ubuntu-drivers` or "Additional Drivers" GUI.

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

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

Title:
  package nvidia-dkms-525-server 525.105.17-0ubuntu0.22.10.1 failed to
  install/upgrade: nvidia-dkms-525-server paketi post-installation
  betiği kuruldu alt süreci 10 hatalı çıkış kodu ile sona erdi

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

Bug description:
  ı dont understand much

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: nvidia-dkms-525-server 525.105.17-0ubuntu0.22.10.1
  ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87
  Uname: Linux 5.15.0-69-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3.2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Apr 14 21:50:14 2023
  ErrorMessage: nvidia-dkms-525-server paketi post-installation betiği kuruldu 
alt süreci 10 hatalı çıkış kodu ile sona erdi
  InstallationDate: Installed on 2023-04-13 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: nvidia-graphics-drivers-525-server
  Title: package nvidia-dkms-525-server 525.105.17-0ubuntu0.22.10.1 failed to 
install/upgrade: nvidia-dkms-525-server paketi post-installation betiği kuruldu 
alt süreci 10 hatalı çıkış kodu ile sona erdi
  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-525-server/+bug/2016329/+subscriptions


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

[Kernel-packages] [Bug 2039470] Re: package nvidia-dkms-525-server 525.125.06-0ubuntu0.22.04.1 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-525-server script post-installatio

ERROR (dkms apport): kernel package linux-headers-6.4.9-060409-generic
is not supported

no support is provided for non-ubuntu-archive kernels.

please use precompiled nvidia drivers for Ubuntu Archive kernel via
`ubuntu-drivers`

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

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

Title:
  package nvidia-dkms-525-server 525.125.06-0ubuntu0.22.04.1 failed to
  install/upgrade: el subproceso instalado paquete nvidia-
  dkms-525-server script post-installation devolvió el código de salida
  de error 10

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

Bug description:
  I tried to install the driver for my GTM-1650 video card and received
  the following error: pk-client-error-quark

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: nvidia-dkms-525-server 525.125.06-0ubuntu0.22.04.1
  Uname: Linux 6.4.9-060409-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Oct 16 09:58:54 2023
  ErrorMessage: el subproceso instalado paquete nvidia-dkms-525-server script 
post-installation devolvió el código de salida de error 10
  InstallationDate: Installed on 2023-01-04 (284 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.10
  SourcePackage: nvidia-graphics-drivers-525-server
  Title: package nvidia-dkms-525-server 525.125.06-0ubuntu0.22.04.1 failed to 
install/upgrade: el subproceso instalado paquete nvidia-dkms-525-server script 
post-installation devolvió el código de salida de error 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2025243] Re: Introduce the NVIDIA 535-server ERD driver series, and enable arm64 for 535, 525, 525-server in Focal

** Changed in: fabric-manager-525 (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: libnvidia-nscq-525 (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: nvidia-graphics-drivers-525 (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: nvidia-graphics-drivers-525 (Ubuntu Bionic)
   Status: Confirmed => Fix Released

** Changed in: nvidia-graphics-drivers-525 (Ubuntu Jammy)
   Status: Confirmed => Fix Released

** Changed in: nvidia-graphics-drivers-525 (Ubuntu Kinetic)
   Status: Confirmed => Fix Released

** Changed in: nvidia-graphics-drivers-525 (Ubuntu Lunar)
   Status: Confirmed => Fix Released

** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Bionic)
   Status: Confirmed => Fix Released

** Changed in: nvidia-graphics-drivers-525-server (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Jammy)
   Status: In Progress => Fix Released

** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Lunar)
   Status: In Progress => Fix Released

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

Title:
  Introduce the NVIDIA 535-server ERD driver series, and enable arm64
  for 535, 525, 525-server in Focal

Status in fabric-manager-525 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Kinetic:
  Won't Fix
Status in nvidia-graphics-drivers-525 source package in Lunar:
  Fix Released
Status in nvidia-graphics-drivers-525-server source package in Lunar:
  Fix Released

Bug description:
  Introduce the NVIDIA 535-server ERD driver series, enabling the -open
  kernel module.

  Release notes:
  
https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-535-54-03/index.html

  
  Changelogs for the drivers in focal:

  
  nvidia-graphics-drivers-525 (525.125.06-0ubuntu0.20.04.3) focal; 
urgency=medium

[ Dimitri John Ledkov ]
* debian:
  - Enable arm64 builds (LP: #2025243).
* debian/templates:
  - Encode amd64-only libraries and binaries.

  
  nvidia-graphics-drivers-535 (535.54.03-0ubuntu0.20.04.4) focal; urgency=medium

[ Dimitri John Ledkov ]
* templates: encode amd64-only libraries and binaries
* debian: Enable arm64 builds (LP: #2025243).

   -- Alberto Milone   Mon, 03 Jul 2023
  13:34:05 +

  
  nvidia-graphics-drivers-525-server (525.125.06-0ubuntu0.20.04.2) focal; 
urgency=medium

[ Alberto Milone ]
* debian/rules:
  - Drop the unused generate-nvidia-icd-json target;

[ Dimitri John Ledkov ]
* debian:
  - Enable arm64 builds (LP: #2025243).
* debian/templates:
  - Encode amd64-only libraries and binaries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-525/+bug/2025243/+subscriptions


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

[Kernel-packages] [Bug 1954904] Re: bpf pointer tainted kaslr leak

2024-01-23 Thread Thadeu Lima de Souza Cascardo

CVE-2021-4159 was fixed by this same commit.

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

** Information type changed from Private Security to Public Security

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

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

Title:
  bpf pointer tainted kaslr leak

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  adjust_ptr_min_max_vals will allow a pointer arithmetic with any value, but 
set the register to a SCALAR, preventing further pointer operations, leading to 
a pointer leak, aka, KASLR leak.

  [Potential regression]
  Any potential fixes will change the verifier, which means that some BPF code 
that was previously allowed may be prevented to load. It may also lead to other 
code being allowed that leads to other vulnerabilities.

  [Test case]
  Use a privately shared code to test it.

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


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

[Kernel-packages] [Bug 1989435] Re: race condition in io_uring lead to Local Privilege Escalation

2024-01-23 Thread Thadeu Lima de Souza Cascardo

Thanks, neoni. We appreciate the report. Sorry it took this long to get
a response.

Those fixes are already applied in our 5.15 kernels and we don't support
5.19 and 6.0 anymore. Since these have been fixed in 6.1 and later
kernels and 5.4 do not carry those features, we consider this issue
fixed in all the supported kernels we currently ship.

Thanks again.
Cascardo.

** Information type changed from Private Security to Public Security

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

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

Title:
race condition in io_uring lead to Local Privilege Escalation

Status in linux-hwe package in Ubuntu:
Fix Released

Bug description:
Hello. I'm neoni. I would like to report a vulnerability that lead to
Use After Free.

An unprivileged attacker may use this vulnerability to root to achieve
local privilege escalation.

Here is the detail:
When io_uring does io_sqe_buffers_unregister/io_sqe_files_unregister
operation, it will unlock ctx->uring_lock in io_rsrc_ref_quiesce process and
later release files/buffers. So an attacker could submit a file/buffer
read/write related operation by racing io_rsrc_ref_quiesce process. When
files/buffers are released and ctx starts to deal with new sqe, an
Use-After-Free will be triggered.

The vulnerability was already patched as a bug in Linux mainstream
5.19 and

6.0(https://github.com/torvalds/linux/commit/d11d31fc5d8a96f707facee0babdcffaafa38de2)(https://github.com/torvalds/linux/commit/b0380bf6dad4601d92025841e2b7a135d566c6e3).

a PoC crashes kernel is attached. It affects most recent ubuntu kernel images
as well as some hwe/oem kernel like hwe-5.17.

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

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

[Kernel-packages] [Bug 2048945] Dependencies.txt

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/2048945/+attachment/5741724/+files/Dependencies.txt

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

Title:
  scsi_eh_* process using idle CPU after upgrade to kernel 6.5

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux-aws-6.5 package in Ubuntu:
  New
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-meta-hwe-6.5 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  Possibly related to https://lkml.kernel.org/linux-
  scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/

  Getting alerts from monitoring tools about high average CPU usage.
  Machine reporting the following:

  root@server:~# uptime
   17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94

  root@server:~# top -d 1

  top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
  Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
  MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   88 root  20   0   0  0  0 D  55.4   0.0  11275:46 
scsi_eh_1

  root@server:~# lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
  linux-image-virtual-hwe-22.04-edge:
Installed: 6.5.0.14.14~22.04.6
Candidate: 6.5.0.14.14~22.04.7
Version table:
   6.5.0.14.14~22.04.7 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   *** 6.5.0.14.14~22.04.6 100
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jan 10 17:02:50 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Tags: jammy third-party-packages
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 10:31 seq
   crw-rw 1 root audio 116, 33 Dec 27 10:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vmwgfxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.23
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to

[Kernel-packages] [Bug 2048945] Re: scsi_eh_* process using idle CPU after upgrade to kernel 6.5

Updated to 6.5.0-17 and the issue still persists.

user@host:~$ uptime
 11:26:35 up  1:15,  1 user,  load average: 13.68, 13.67, 13.64


** Description changed:

  Possibly related to https://lkml.kernel.org/linux-
  scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/
  
  Getting alerts from monitoring tools about high average CPU usage.
  Machine reporting the following:
  
  root@server:~# uptime
   17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94
  
  root@server:~# top -d 1
  
  top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
  Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
  MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem
  
  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   88 root  20   0   0  0  0 D  55.4   0.0  11275:46 
scsi_eh_1
  
  root@server:~# lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04
  
  root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
  linux-image-virtual-hwe-22.04-edge:
Installed: 6.5.0.14.14~22.04.6
Candidate: 6.5.0.14.14~22.04.7
Version table:
   6.5.0.14.14~22.04.7 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   *** 6.5.0.14.14~22.04.6 100
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jan 10 17:02:50 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Tags: jammy third-party-packages
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 10:31 seq
   crw-rw 1 root audio 116, 33 Dec 27 10:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vmwgfxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.23
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias:

[Kernel-packages] [Bug 2048945] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2048945/+attachment/5741725/+files/ProcCpuinfoMinimal.txt

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

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

Title:
  scsi_eh_* process using idle CPU after upgrade to kernel 6.5

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux-aws-6.5 package in Ubuntu:
  New
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-meta-hwe-6.5 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  Possibly related to https://lkml.kernel.org/linux-
  scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/

  Getting alerts from monitoring tools about high average CPU usage.
  Machine reporting the following:

  root@server:~# uptime
   17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94

  root@server:~# top -d 1

  top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
  Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
  MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   88 root  20   0   0  0  0 D  55.4   0.0  11275:46 
scsi_eh_1

  root@server:~# lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
  linux-image-virtual-hwe-22.04-edge:
Installed: 6.5.0.14.14~22.04.6
Candidate: 6.5.0.14.14~22.04.7
Version table:
   6.5.0.14.14~22.04.7 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   *** 6.5.0.14.14~22.04.6 100
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jan 10 17:02:50 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Tags: jammy third-party-packages
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 10:31 seq
   crw-rw 1 root audio 116, 33 Dec 27 10:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vmwgfxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.23
  RfKill: Error: [Errno 2] No such file or directory:

[Kernel-packages] [Bug 2048945] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2048945/+attachment/5741723/+files/ProcCpuinfoMinimal.txt

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

Title:
  scsi_eh_* process using idle CPU after upgrade to kernel 6.5

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux-aws-6.5 package in Ubuntu:
  New
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-meta-hwe-6.5 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  Possibly related to https://lkml.kernel.org/linux-
  scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/

  Getting alerts from monitoring tools about high average CPU usage.
  Machine reporting the following:

  root@server:~# uptime
   17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94

  root@server:~# top -d 1

  top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
  Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
  MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   88 root  20   0   0  0  0 D  55.4   0.0  11275:46 
scsi_eh_1

  root@server:~# lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
  linux-image-virtual-hwe-22.04-edge:
Installed: 6.5.0.14.14~22.04.6
Candidate: 6.5.0.14.14~22.04.7
Version table:
   6.5.0.14.14~22.04.7 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   *** 6.5.0.14.14~22.04.6 100
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jan 10 17:02:50 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Tags: jammy third-party-packages
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 10:31 seq
   crw-rw 1 root audio 116, 33 Dec 27 10:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vmwgfxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.23
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus:

[Kernel-packages] [Bug 2048945] Re: scsi_eh_* process using idle CPU after upgrade to kernel 6.5

apport information

** Description changed:

  Possibly related to https://lkml.kernel.org/linux-
  scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/
  
  Getting alerts from monitoring tools about high average CPU usage.
  Machine reporting the following:
  
  root@server:~# uptime
   17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94
  
  root@server:~# top -d 1
  
  top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
  Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
  MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem
  
  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   88 root  20   0   0  0  0 D  55.4   0.0  11275:46 
scsi_eh_1
  
  root@server:~# lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04
  
  root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
  linux-image-virtual-hwe-22.04-edge:
Installed: 6.5.0.14.14~22.04.6
Candidate: 6.5.0.14.14~22.04.7
Version table:
   6.5.0.14.14~22.04.7 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   *** 6.5.0.14.14~22.04.6 100
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jan 10 17:02:50 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Tags: jammy third-party-packages
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 10:31 seq
   crw-rw 1 root audio 116, 33 Dec 27 10:31 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vmwgfxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.23
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias:

[Kernel-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable

2024-01-23 Thread dann frazier

** Summary changed:

- livecd-rootfs uses losetup -P for theoretically reliable/synchronous 
partition setup but it's not reliable in noble
+ livecd-rootfs uses losetup -P for theoretically reliable/synchronous 
partition setup but it's not reliable

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

Title:
  livecd-rootfs uses losetup -P for theoretically reliable/synchronous
  partition setup but it's not reliable

Status in linux package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  In mantic, we migrated livecd-rootfs to use losetup -P instead of
  kpartx, with the expectation that this would give us a reliable, race-
  free way of loop-mounting partitions from a disk image during image
  build.

  In noble, we are finding that it is no longer reliable, and in fact
  fails rather often.

  It is most noticeable with riscv64 builds, which is the architecture
  where we most frequently ran into problems before with kpartx.  The
  first riscv64+generic build in noble where the expected loop partition
  device is not available is

https://launchpad.net/~ubuntu-
  cdimage/+livefs/ubuntu/noble/cpc/+build/531790

  The failure is however not unique to riscv64, and the autopkgtest for
  the latest version of livecd-rootfs (24.04.7) - an update that
  specifically tries to add more debugging code for this scenario - has
  also failed on ppc64el.

https://autopkgtest.ubuntu.com/packages/l/livecd-
  rootfs/noble/ppc64el

  The first failure happened on November 16.  While there has been an
  update to the util-linux package in noble, this did not land until
  November 23.

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


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

[Kernel-packages] [Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

2024-01-23 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

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


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

[Kernel-packages] [Bug 2007055] Re: cifs/samba mount not preserving file timestamps

2024-01-23 Thread Mint Platz

@Nicholas Neumann: Interesting! So the only difference is, that Windows
clients do not specify the "Last Access" attribute. So in case of a
Windows client, you expect and see a modification date of Nov 22, 2023
13:15:09 on the NAS, for the Linux client (which transmits the "Last
Access" attribute), you expect Nov 22, 2023 13:15:09 but get Jan 22,
2024 13:15:35?

I'm a bit helpless in understanding how one would _change_ a file on Jan
22, 2024 13:23:52 without actually _writing_ to it (which happened on
Nov 22, 2023 13:15:09) and why the time stamps for "Last Access" and
"Last Change" are not identical, but that's probably just one more
particularity of the Linux file system.

Whatever may be the case, I do not think it is correct when the Synology
NAS' SMB server module confuses the presence of "Last Access" (which
could have been either read or write) with "Last Change", effectively
overwriting the modification date of the file (which seems to be defined
by "Last Write").

SMB: the final frontier. These are the voyages of numerous Linux
enthusiasts. Their perpetual mission: to explore strange new worlds; to
seek out new software and new functionality; to boldly go where no man
has gone before!

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

Title:
  cifs/samba mount not preserving file timestamps

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Incomplete

Bug description:
  I think I've found a bug or regression in something when trying to
  mount a remote samba share. Modified/Created times are not properly
  preserved in newer versions of Ubuntu. Because of this, rsync thinks
  files are different based on their modified times and keeps re-syncing
  them.

  I have a NAS on my network, running samba.

  I have two devices, a desktop and laptop. Both are running Ubuntu, and
  set up the exact same way. The desktop is running ubuntu 20.04, the
  laptop 22.04.

  I have mounted the NAS on both devices the exact same way. I attempt
  to copy a file (rsync) the exact same way. On the 20.04 desktop, this
  works perfectly fine. On the 22.04 laptop, the modified times are not
  preserved and set to the current time, preventing things like rsync -t
  from working.

  The only difference i can find is that between the two systems, the newer 
laptop 22.04 mount adds a few more options than the older system to the cifs 
mount options. These are added automatically without being specified explicitly 
(see the mount -v output below): 
  * 'forceuid'/'forcegid' are changed to 'noforceuid'/'noforcegid
  *  iocharset=utf8 added
  *  serverino added

  desktop:

  $ lsb_release -rd
  Description:Ubuntu 20.04.5 LTS
  Release:20.04
  $ apt-cache policy cifs-utils
  cifs-utils:
Installed: 2:6.9-1ubuntu0.2
Candidate: 2:6.9-1ubuntu0.2
Version table:
   *** 2:6.9-1ubuntu0.2 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2:6.9-1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  $ uname -a
  Linux desktop 5.4.0-132-generic #148-Ubuntu SMP Mon Oct 17 16:02:06 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux
  $ mount -v 
  //nas/backup on /media/scratch type cifs 
(rw,relatime,vers=3.0,cache=strict,username=nas_rw,uid=1000,forceuid,gid=1000,forcegid,addr=192.168.1.10,file_mode=0664,dir_mode=0775,soft,nounix,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1)

  
  laptop:

  $ lsb_release -rd
  Description:KDE neon 5.26
  Release:22.04
  $ apt-cache policy cifs-utils
  cifs-utils:
Installed: 2:6.14-1ubuntu0.1
Candidate: 2:6.14-1ubuntu0.1
Version table:
   *** 2:6.14-1ubuntu0.1 500
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   2:6.14-1build1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  $ uname -a
  Linux laptop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 
x86_64 x86_64 x86_64 GNU/Linux
  $ mount -v
  //nas/backup on /media/scratch type cifs 
(rw,relatime,vers=3.0,cache=strict,username=nas_rw,uid=1000,noforceuid,gid=1000,noforcegid,addr=192.168.1.10,file_mode=0664,dir_mode=0775,iocharset=utf8,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1)

  the remote NAS is a synology appliance, running Samba version 4.10.18.
  SMB version 3

  Steps to reproduce:
  1. Similar setup, 1 device running 20.04, another running 22.04, otherwise up 
to date.

  2. mount the NAS on both devices the exact same way
  $ sudo mount -t cifs -o

[Kernel-packages] [Bug 2050098] Re: cgroup2 broken since 5.15.0-90-generic?

I'm concerned with the security implications of being frozen on a kernel
we can't update. I suspect we should start testing an HWE kernel. That
raises other issues, since there are lots of other features we also need
to work, so it's going to require a fair amount of testing. I'd
accelerate our move to 24.04, except there is too much question about
update of user packages, which often lag new system versions.

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

Title:
  cgroup2 broken since 5.15.0-90-generic?

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  We're using Slurm workload manager in a cluster with Ubuntu 22.04 and
  the linux-generic kernel (amd64). We  use cgroups (cgroup2) for
  resource allocation with Slurm. With kernel version

  linux-image-5.15.0-91-generic 5.15.0-91.101
  amd64

  I'm seeing a new issue. This must have been introduced recently, I can
  confirm that with kernel 5.15.0-88-generic the issue does not exist.
  When I request a single GPU on a node with kernel 5.15.0-88-generic
  all is well:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  GPU 0: NVIDIA [...]

  Instead with kernel 5.15.0-91-generic:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  slurmstepd: error: load_ebpf_prog: BPF load error (No space left on device). 
Please check your system limits (MEMLOCK).
  GPU 0: NVIDIA [...]
  GPU 1: NVIDIA [...]
  GPU 2: NVIDIA [...]
  GPU 3: NVIDIA [...]
  GPU 4: NVIDIA [...]
  GPU 5: NVIDIA [...]
  GPU 6: NVIDIA [...]
  GPU 7: NVIDIA [...]

  So I get this error regarding MEMLOCK limit and see all GPUs in the
  system instead of only the one requested. Hence I assume the problem
  is related to cgroups.

  $ cat /proc/version_signature
  Ubuntu 5.15.0-91.101-generic 5.15.131

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


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

[Kernel-packages] [Bug 2029001] Re: igc ethernet driver: unplugging thunderbolt dock causes kernel OOPs

2024-01-23 Thread Lassi Väätämöinen

I could not pin-point a specific upgrade that could cause this. The previous 
batch of updates contained pretty much just
- KDE and Qt updates
- fwupd libflashrom1


Last time I saw this, I was using 5.19 kernel, and it was said that a fix was 
in 6.0. or newer.
Now I have run 6.2.0-33 for 3 months without issues, until today, as this 
happens continuously right upon connecting the TB4 dock.

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

Title:
  igc ethernet driver: unplugging thunderbolt dock causes kernel OOPs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a ThinkPad Thunderbolt 4 dock.

  When I unplug it from the laptop, I see this traceback in kernel logs:

  [407643.532144] igc :79:00.0 enp121s0: PCIe link lost, device now detached
  [407643.532174] [ cut here ]
  [407643.532179] igc: Failed to read reg 0x5b50!
  [407643.532367] WARNING: CPU: 4 PID: 598295 at 
drivers/net/ethernet/intel/igc/igc_main.c:6412 igc_rd32+0xa4/0xc0 [igc]
  [407643.532430] Modules linked in: tcp_diag inet_diag xt_nat 
nf_conntrack_netlink 8021q garp mrp veth nft_masq zfs(PO) zunicode(PO) zzstd(O) 
zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) vhost_vsock 
vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xfrm_user xfrm_algo 
xt_addrtype ccm rfcomm snd_seq_dummy snd_hrtimer xt_CHECKSUM xt_MASQUERADE 
xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat 
nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink cmac 
algif_hash algif_skcipher af_alg bnep binfmt_misc nls_iso8859_1 snd_ctl_led 
snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi 
snd_sof_probes snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic 
snd_soc_dmic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel 
soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acp
 i
  [407643.532614]  soundwire_bus snd_soc_core snd_compress ac97_bus 
snd_pcm_dmaengine intel_tcc_cooling iwlmvm x86_pkg_temp_thermal 
intel_powerclamp snd_hda_intel coretemp snd_intel_dspcfg mac80211 kvm_intel 
snd_intel_sdw_acpi btusb pmt_telemetry mei_pxp mei_hdcp btrtl intel_rapl_msr 
pmt_class libarc4 snd_hda_codec kvm snd_usb_audio uvcvideo snd_seq_midi btbcm 
snd_seq_midi_event snd_usbmidi_lib videobuf2_vmalloc snd_hda_core btintel 
videobuf2_memops snd_hwdep btmtk snd_rawmidi videobuf2_v4l2 irqbypass snd_seq 
iwlwifi bluetooth processor_thermal_device_pci videodev 
processor_thermal_device snd_pcm mei_me processor_thermal_rfim rapl 
snd_seq_device videobuf2_common think_lmi processor_thermal_mbox spi_nor 
thinkpad_acpi processor_thermal_rapl ucsi_acpi intel_cstate ecdh_generic 
firmware_attributes_class wmi_bmof typec_ucsi nvram cfg80211 mtd snd_timer mei 
ecc mc joydev intel_vsec intel_rapl_common igen6_edac typec snd soundcore 
nxp_nci_i2c ledtrig_audio int3403_thermal platform_profile n
 xp_nci
  [407643.532800]  int340x_thermal_zone nci nfc int3400_thermal intel_hid 
acpi_thermal_rel acpi_tad sparse_keymap acpi_pad input_leds hid_multitouch 
serio_raw mac_hid overlay iptable_filter ip6table_filter ip6_tables 
br_netfilter bridge stp llc arp_tables msr parport_pc ppdev lp parport 
efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic xor 
raid6_pq libcrc32c dm_crypt hid_lenovo usbhid i915 drm_buddy i2c_algo_bit ttm 
drm_display_helper cec rc_core drm_kms_helper syscopyarea hid_generic 
sysfillrect crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic 
ghash_clmulni_intel sha512_ssse3 aesni_intel nvme crypto_simd sysimgblt 
nvme_core psmouse cryptd drm e1000e igc thunderbolt spi_intel_pci 
intel_lpss_pci i2c_i801 spi_intel xhci_pci intel_lpss i2c_smbus idma64 
xhci_pci_renesas nvme_common i2c_hid_acpi i2c_hid video hid wmi 
pinctrl_tigerlake
  [407643.532992] CPU: 4 PID: 598295 Comm: kworker/4:7 Tainted: P   O   
6.2.0-26-generic #26-Ubuntu
  [407643.533005] Hardware name: LENOVO 21AHCTO1WW/21AHCTO1WW, BIOS N3MET15W 
(1.14 ) 04/27/2023
  [407643.533012] Workqueue: events igc_watchdog_task [igc]
  [407643.533062] RIP: 0010:igc_rd32+0xa4/0xc0 [igc]
  [407643.533103] Code: c7 c6 d8 55 4c c0 e8 cb b9 71 e9 48 8b bb 28 ff ff ff 
e8 df 1b 23 e9 84 c0 74 b4 44 89 e6 48 c7 c7 00 56 4c c0 e8 6c 9a a3 e8 <0f> 0b 
eb a1 b8 ff ff ff ff 31 d2 31 f6 31 ff c3 cc cc cc cc 0f 1f
  [407643.533113] RSP: 0018:a8da031d7c90 EFLAGS: 00010246
  [407643.533122] RAX:  RBX: 9d99501b8c60 RCX: 

  [407643.533129] RDX:  RSI:  RDI: 

  [407643.533133] RBP: a8da031d7ca8 R08:  R09: 

  [407643.533138] R10:  R11:  R12: 
5b50

[Kernel-packages] [Bug 2050098] Re: cgroup2 broken since 5.15.0-90-generic?

We are also seeing this. We're now stuck on old kernels until this is
fixed.

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

Title:
  cgroup2 broken since 5.15.0-90-generic?

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  We're using Slurm workload manager in a cluster with Ubuntu 22.04 and
  the linux-generic kernel (amd64). We  use cgroups (cgroup2) for
  resource allocation with Slurm. With kernel version

  linux-image-5.15.0-91-generic 5.15.0-91.101
  amd64

  I'm seeing a new issue. This must have been introduced recently, I can
  confirm that with kernel 5.15.0-88-generic the issue does not exist.
  When I request a single GPU on a node with kernel 5.15.0-88-generic
  all is well:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  GPU 0: NVIDIA [...]

  Instead with kernel 5.15.0-91-generic:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  slurmstepd: error: load_ebpf_prog: BPF load error (No space left on device). 
Please check your system limits (MEMLOCK).
  GPU 0: NVIDIA [...]
  GPU 1: NVIDIA [...]
  GPU 2: NVIDIA [...]
  GPU 3: NVIDIA [...]
  GPU 4: NVIDIA [...]
  GPU 5: NVIDIA [...]
  GPU 6: NVIDIA [...]
  GPU 7: NVIDIA [...]

  So I get this error regarding MEMLOCK limit and see all GPUs in the
  system instead of only the one requested. Hence I assume the problem
  is related to cgroups.

  $ cat /proc/version_signature
  Ubuntu 5.15.0-91.101-generic 5.15.131

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


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

[Kernel-packages] [Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

2024-01-23 Thread Nick Rosbrook

** Tags added: systemd-sru-next

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

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


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

[Kernel-packages] [Bug 2050098] Re: cgroup2 broken since 5.15.0-90-generic?

** Summary changed:

- cgroup2 appears to be broken
+ cgroup2 broken since 5.15.0-90-generic?

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

Title:
  cgroup2 broken since 5.15.0-90-generic?

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  We're using Slurm workload manager in a cluster with Ubuntu 22.04 and
  the linux-generic kernel (amd64). We  use cgroups (cgroup2) for
  resource allocation with Slurm. With kernel version

  linux-image-5.15.0-91-generic 5.15.0-91.101
  amd64

  I'm seeing a new issue. This must have been introduced recently, I can
  confirm that with kernel 5.15.0-88-generic the issue does not exist.
  When I request a single GPU on a node with kernel 5.15.0-88-generic
  all is well:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  GPU 0: NVIDIA [...]

  Instead with kernel 5.15.0-91-generic:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  slurmstepd: error: load_ebpf_prog: BPF load error (No space left on device). 
Please check your system limits (MEMLOCK).
  GPU 0: NVIDIA [...]
  GPU 1: NVIDIA [...]
  GPU 2: NVIDIA [...]
  GPU 3: NVIDIA [...]
  GPU 4: NVIDIA [...]
  GPU 5: NVIDIA [...]
  GPU 6: NVIDIA [...]
  GPU 7: NVIDIA [...]

  So I get this error regarding MEMLOCK limit and see all GPUs in the
  system instead of only the one requested. Hence I assume the problem
  is related to cgroups.

  $ cat /proc/version_signature
  Ubuntu 5.15.0-91.101-generic 5.15.131

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


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

[Kernel-packages] [Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

2024-01-23 Thread Lukas Märdian

Actually, we can further reduce the patch to the removal of
`.generate_mac = true`. This already fixes the issue we observe here.

** Patch added: "lp2037667.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+attachment/5741632/+files/lp2037667.patch

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

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


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

[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

2024-01-23 Thread Mario Limonciello

If it's a SAUCE only patch, I think it should be proposed here:
https://lists.ubuntu.com/mailman/listinfo/kernel-team

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid

Bug description:
  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

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


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

[Kernel-packages] [Bug 2050098] Re: cgroup2 appears to be broken

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

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

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

Title:
  cgroup2 appears to be broken

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  We're using Slurm workload manager in a cluster with Ubuntu 22.04 and
  the linux-generic kernel (amd64). We  use cgroups (cgroup2) for
  resource allocation with Slurm. With kernel version

  linux-image-5.15.0-91-generic 5.15.0-91.101
  amd64

  I'm seeing a new issue. This must have been introduced recently, I can
  confirm that with kernel 5.15.0-88-generic the issue does not exist.
  When I request a single GPU on a node with kernel 5.15.0-88-generic
  all is well:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  GPU 0: NVIDIA [...]

  Instead with kernel 5.15.0-91-generic:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  slurmstepd: error: load_ebpf_prog: BPF load error (No space left on device). 
Please check your system limits (MEMLOCK).
  GPU 0: NVIDIA [...]
  GPU 1: NVIDIA [...]
  GPU 2: NVIDIA [...]
  GPU 3: NVIDIA [...]
  GPU 4: NVIDIA [...]
  GPU 5: NVIDIA [...]
  GPU 6: NVIDIA [...]
  GPU 7: NVIDIA [...]

  So I get this error regarding MEMLOCK limit and see all GPUs in the
  system instead of only the one requested. Hence I assume the problem
  is related to cgroups.

  $ cat /proc/version_signature
  Ubuntu 5.15.0-91.101-generic 5.15.131

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


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

[Kernel-packages] [Bug 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module

2024-01-23 Thread Bartlomiej Zolnierkiewicz

$ dpkg -X linux-buildinfo-5.15.0-1033-bluefield_5.15.0-1033.35_arm64.deb unpack
$ grep ^wwan unpack/usr/lib/linux/5.15.0-1033-bluefield/modules
wwan
wwan_hwsim


** Tags removed: verification-needed-jammy-linux-bluefield
** Tags added: verification-done-jammy-linux-bluefield

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

Title:
  [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  == SRU Justification ==
  The CONFIG_WWAN config is set to 'Y' for the generic and most derivative 
kernels.  This is affecting custom driver development for some partners.

  Change this config to be a loadable module and include it in linux-
  modules-*.

  Make this change to -generic kernels, so all derivatives will inherit
  it.

  
  == Fix ==
  UBUNTU: [Packaging] Make WWAN driver loadable modules

  
  == Regression Potential ==
  Medium.  This change is only to WWAN, and is changing it to a loadable module 
and not removing it.

  == Test Case ==
  A test kernel was built with this patch and tested by a partner.  It was also 
compile and boot tested internally.  Testing will also be performed on a WWAN 
device.

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


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

[Kernel-packages] [Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

2024-01-23 Thread Lukas Märdian

This seems to do the trick using the following Netplan config as a
testcase.

All 3 interfaces (tun[0-2]) are correctly created with their local &
remote properties set:

root@jj-abi:~/systemd# ip link show dev tun0
19: tun0@NONE:  mtu 1448 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
link/gre6 fe80::1 brd 2001:dead:beef::2 permaddr e262:75ae:2aa0::
root@jj-abi:~/systemd# ip link show dev tun1
20: tun1@NONE:  mtu 1332 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
link/tunnel6 fe80::2 brd 2001:dead:beef::3 permaddr c2aa:7446:cc29::
root@jj-abi:~/systemd# ip link show dev tun2
21: tun2@NONE:  mtu 1444 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
link/gre6 fe80::3 brd 2001:dead:beef::4 permaddr 3ef2:274c:a921::


Netplan test config:
```
network:
  version: 2
  tunnels:
tun0:
  mode: ip6gre
  local: fe80::1
  remote: 2001:dead:beef::2
tun1:
  mode: vti6
  local: fe80::2
  remote: 2001:dead:beef::3
tun2:
  mode: ip6gre
  key: 1234
  local: fe80::3
  remote: 2001:dead:beef::4
```

** Patch added: "network-netdev-introduce-.iftype-to-netdev-vtable.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+attachment/5741625/+files/network-netdev-introduce-.iftype-to-netdev-vtable.patch

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1

[Kernel-packages] [Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

2024-01-23 Thread Lukas Märdian

So after bisecting systemd (v249..v251) on Jammy, this seems to be the
commit that changed behavior for the better:

https://github.com/systemd/systemd/commit/9f0cf80dd007491698978dbfe38158d74c1c9526

It probably needs some backporting for v249.11.

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

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


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

[Kernel-packages] [Bug 2050103] Re: Integrated Laptop screen not detected on 6.5 hwe - Intel UHD 630 Coffee Lake

** Attachment added: "Output from journalctl for boot to shutdown from kernel 
6.5.0-14"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2050103/+attachment/5741576/+files/journalctl_6.5

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

Title:
  Integrated Laptop screen not detected on 6.5 hwe - Intel UHD 630
  Coffee Lake

Status in linux-hwe-6.5 package in Ubuntu:
  New

Bug description:
  lsb_release
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04
  Codename: jammy

  Laptop: Rebadged Clevo
  Graphics: on-board Intel UHD 630 

  Updated from kernel 6.2.0-39-generic to 6.5.0-14-generic

  Problem:- LCD laptop screen not detected on kernel 6.5.0-14

  The laptop LCD screen is black but the external RGB monitor works
  fine. Using kernel 6.2.0-39, both the LCD and external monitor work.

  inxi -Gxx  on 6.2 kernel shows 2 Monitors - DP-1 is the external and eDP-1 is 
the LCD
  Graphics:
Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: CLEVO/KAPOK
  driver: i915 v: kernel ports: active: DP-1,eDP-1 empty: HDMI-A-1,HDMI-A-2
  bus-ID: 00:02.0 chip-ID: 8086:3e9b
Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 1-8:4
  chip-ID: 5986:2110
Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.1
  compositor: gnome-shell v: 42.9 driver: X: loaded: vesa
  unloaded: fbdev,modesetting gpu: i915 display-ID: 0
Monitor-1: DP-1 model: Vw19B2 res: 1440x900 dpi: 89 diag: 483mm (19")
Monitor-2: eDP-1 model: LG res: 1920x1080 dpi: 128 diag: 438mm (17.3")
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
  v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes

  inxi -Gxx  on 6.5 kernel shows 1 Monitor - DP-1 is the external
  Graphics:
Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: CLEVO/KAPOK
  driver: i915 v: kernel ports: active: DP-1 empty: HDMI-A-1,HDMI-A-2
  bus-ID: 00:02.0 chip-ID: 8086:3e9b
Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 1-8:4
  chip-ID: 5986:2110
Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.1
  compositor: gnome-shell v: 42.9 driver: X: loaded: vesa
  unloaded: fbdev,modesetting gpu: i915 display-ID: 0
Monitor-1: DP-1 model: Vw19B2 res: 1440x900 dpi: 89 diag: 483mm (19")
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
  v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes

  This line using journalctl is in the boot log of kernel 6.2 but not in the 
boot log of 6.5(probably not relevant)
  Jan 14 15:27:20 hybris kernel: i915 :00:02.0: [drm] Skipping 
intel_backlight registration

  Have noticed Bug:- https://answers.launchpad.net/bugs/2049245 which is
  against nvidia graphics but will try 1024x768 resolution.

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


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

[Kernel-packages] [Bug 2050103] Re: Integrated Laptop screen not detected on 6.5 hwe - Intel UHD 630 Coffee Lake

There is this gem in the journalctl from 6.5.0-14:-
journalctl_6.5:Jan 23 12:18:00 hybris kernel: i915 :00:02.0: [drm] 
[ENCODER:94:DDI A/PHY A] HPD is down, disabling eDP

May explain why eDP is not enabled.

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

Title:
  Integrated Laptop screen not detected on 6.5 hwe - Intel UHD 630
  Coffee Lake

Status in linux-hwe-6.5 package in Ubuntu:
  New

Bug description:
  lsb_release
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04
  Codename: jammy

  Laptop: Rebadged Clevo
  Graphics: on-board Intel UHD 630 

  Updated from kernel 6.2.0-39-generic to 6.5.0-14-generic

  Problem:- LCD laptop screen not detected on kernel 6.5.0-14

  The laptop LCD screen is black but the external RGB monitor works
  fine. Using kernel 6.2.0-39, both the LCD and external monitor work.

  inxi -Gxx  on 6.2 kernel shows 2 Monitors - DP-1 is the external and eDP-1 is 
the LCD
  Graphics:
Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: CLEVO/KAPOK
  driver: i915 v: kernel ports: active: DP-1,eDP-1 empty: HDMI-A-1,HDMI-A-2
  bus-ID: 00:02.0 chip-ID: 8086:3e9b
Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 1-8:4
  chip-ID: 5986:2110
Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.1
  compositor: gnome-shell v: 42.9 driver: X: loaded: vesa
  unloaded: fbdev,modesetting gpu: i915 display-ID: 0
Monitor-1: DP-1 model: Vw19B2 res: 1440x900 dpi: 89 diag: 483mm (19")
Monitor-2: eDP-1 model: LG res: 1920x1080 dpi: 128 diag: 438mm (17.3")
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
  v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes

  inxi -Gxx  on 6.5 kernel shows 1 Monitor - DP-1 is the external
  Graphics:
Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: CLEVO/KAPOK
  driver: i915 v: kernel ports: active: DP-1 empty: HDMI-A-1,HDMI-A-2
  bus-ID: 00:02.0 chip-ID: 8086:3e9b
Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 1-8:4
  chip-ID: 5986:2110
Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.1
  compositor: gnome-shell v: 42.9 driver: X: loaded: vesa
  unloaded: fbdev,modesetting gpu: i915 display-ID: 0
Monitor-1: DP-1 model: Vw19B2 res: 1440x900 dpi: 89 diag: 483mm (19")
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
  v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes

  This line using journalctl is in the boot log of kernel 6.2 but not in the 
boot log of 6.5(probably not relevant)
  Jan 14 15:27:20 hybris kernel: i915 :00:02.0: [drm] Skipping 
intel_backlight registration

  Have noticed Bug:- https://answers.launchpad.net/bugs/2049245 which is
  against nvidia graphics but will try 1024x768 resolution.

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


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

[Kernel-packages] [Bug 2050103] Re: Integrated Laptop screen not detected on 6.5 hwe - Intel UHD 630 Coffee Lake

** Attachment added: "Output from journalctl for boot to shutdown from kernel 
6.5.0-14"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2050103/+attachment/5741577/+files/journalctl_6.5

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

Title:
  Integrated Laptop screen not detected on 6.5 hwe - Intel UHD 630
  Coffee Lake

Status in linux-hwe-6.5 package in Ubuntu:
  New

Bug description:
  lsb_release
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04
  Codename: jammy

  Laptop: Rebadged Clevo
  Graphics: on-board Intel UHD 630 

  Updated from kernel 6.2.0-39-generic to 6.5.0-14-generic

  Problem:- LCD laptop screen not detected on kernel 6.5.0-14

  The laptop LCD screen is black but the external RGB monitor works
  fine. Using kernel 6.2.0-39, both the LCD and external monitor work.

  inxi -Gxx  on 6.2 kernel shows 2 Monitors - DP-1 is the external and eDP-1 is 
the LCD
  Graphics:
Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: CLEVO/KAPOK
  driver: i915 v: kernel ports: active: DP-1,eDP-1 empty: HDMI-A-1,HDMI-A-2
  bus-ID: 00:02.0 chip-ID: 8086:3e9b
Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 1-8:4
  chip-ID: 5986:2110
Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.1
  compositor: gnome-shell v: 42.9 driver: X: loaded: vesa
  unloaded: fbdev,modesetting gpu: i915 display-ID: 0
Monitor-1: DP-1 model: Vw19B2 res: 1440x900 dpi: 89 diag: 483mm (19")
Monitor-2: eDP-1 model: LG res: 1920x1080 dpi: 128 diag: 438mm (17.3")
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
  v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes

  inxi -Gxx  on 6.5 kernel shows 1 Monitor - DP-1 is the external
  Graphics:
Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: CLEVO/KAPOK
  driver: i915 v: kernel ports: active: DP-1 empty: HDMI-A-1,HDMI-A-2
  bus-ID: 00:02.0 chip-ID: 8086:3e9b
Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 1-8:4
  chip-ID: 5986:2110
Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.1
  compositor: gnome-shell v: 42.9 driver: X: loaded: vesa
  unloaded: fbdev,modesetting gpu: i915 display-ID: 0
Monitor-1: DP-1 model: Vw19B2 res: 1440x900 dpi: 89 diag: 483mm (19")
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
  v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes

  This line using journalctl is in the boot log of kernel 6.2 but not in the 
boot log of 6.5(probably not relevant)
  Jan 14 15:27:20 hybris kernel: i915 :00:02.0: [drm] Skipping 
intel_backlight registration

  Have noticed Bug:- https://answers.launchpad.net/bugs/2049245 which is
  against nvidia graphics but will try 1024x768 resolution.

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


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

[Kernel-packages] [Bug 2050103] Re: Integrated Laptop screen not detected on 6.5 hwe - Intel UHD 630 Coffee Lake

** Attachment added: "Output from journalctl from boot to shutdown from kernel 
6.2.0-39"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2050103/+attachment/5741578/+files/journalctl_6.2

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

Title:
  Integrated Laptop screen not detected on 6.5 hwe - Intel UHD 630
  Coffee Lake

Status in linux-hwe-6.5 package in Ubuntu:
  New

Bug description:
  lsb_release
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04
  Codename: jammy

  Laptop: Rebadged Clevo
  Graphics: on-board Intel UHD 630 

  Updated from kernel 6.2.0-39-generic to 6.5.0-14-generic

  Problem:- LCD laptop screen not detected on kernel 6.5.0-14

  The laptop LCD screen is black but the external RGB monitor works
  fine. Using kernel 6.2.0-39, both the LCD and external monitor work.

  inxi -Gxx  on 6.2 kernel shows 2 Monitors - DP-1 is the external and eDP-1 is 
the LCD
  Graphics:
Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: CLEVO/KAPOK
  driver: i915 v: kernel ports: active: DP-1,eDP-1 empty: HDMI-A-1,HDMI-A-2
  bus-ID: 00:02.0 chip-ID: 8086:3e9b
Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 1-8:4
  chip-ID: 5986:2110
Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.1
  compositor: gnome-shell v: 42.9 driver: X: loaded: vesa
  unloaded: fbdev,modesetting gpu: i915 display-ID: 0
Monitor-1: DP-1 model: Vw19B2 res: 1440x900 dpi: 89 diag: 483mm (19")
Monitor-2: eDP-1 model: LG res: 1920x1080 dpi: 128 diag: 438mm (17.3")
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
  v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes

  inxi -Gxx  on 6.5 kernel shows 1 Monitor - DP-1 is the external
  Graphics:
Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: CLEVO/KAPOK
  driver: i915 v: kernel ports: active: DP-1 empty: HDMI-A-1,HDMI-A-2
  bus-ID: 00:02.0 chip-ID: 8086:3e9b
Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 1-8:4
  chip-ID: 5986:2110
Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.1
  compositor: gnome-shell v: 42.9 driver: X: loaded: vesa
  unloaded: fbdev,modesetting gpu: i915 display-ID: 0
Monitor-1: DP-1 model: Vw19B2 res: 1440x900 dpi: 89 diag: 483mm (19")
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
  v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes

  This line using journalctl is in the boot log of kernel 6.2 but not in the 
boot log of 6.5(probably not relevant)
  Jan 14 15:27:20 hybris kernel: i915 :00:02.0: [drm] Skipping 
intel_backlight registration

  Have noticed Bug:- https://answers.launchpad.net/bugs/2049245 which is
  against nvidia graphics but will try 1024x768 resolution.

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


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

[Kernel-packages] [Bug 2049930] Re: mlxbf_gige: disable RX_DMA during NAPI poll

2024-01-23 Thread Bartlomiej Zolnierkiewicz

** Changed in: linux-bluefield (Ubuntu Jammy)
   Status: New => Fix Committed

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

Title:
  mlxbf_gige: disable RX_DMA during NAPI poll

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  A regression has been introduced in the latest 22.04 kernel by including
  the following two commits:
 revert "UBUNTU: SAUCE: Fix OOB handling RX packets in heavy traffic"
 addition of upstream "mlxbf_gige: fix receive packet race condition"
  The regression will manifest as connectivity problems on "oob_net0" interface

  [Fix]

  Modify the GIGE driver to include the RX_DMA disable logic in its NAPI poll 
routine
  This logic was part of "UBUNTU: SAUCE: Fix OOB handling RX packets in heavy 
traffic"
  but not part of upstream "mlxbf_gige: fix receive packet race condition"

  [Test Case]

  Boot BF3 platform and ensure oob_net0 interface is up and has IP address
  Bring up many IP interfaces, including oob_net0, and make sure OOB interface
  is continually accessible (e.g. via ping)

  [Regression Potential]

  Low risk change, adding back in prior logic.

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


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

[Kernel-packages] [Bug 2029001] Re: igc ethernet driver: unplugging thunderbolt dock causes kernel OOPs

2024-01-23 Thread Lassi Väätämöinen

Occurred today on KDE Neon, while plugging the TB4 dock. This started
happening after the recent updates, so was working fine reboot today.

[ 7556.301991] usb 3-5.1: Product: ThinkPad Thunderbolt 4 Dock MCU Contoller
[ 7556.301992] usb 3-5.1: Manufacturer: Lenovo
[ 7556.301993] usb 3-5.1: SerialNumber: 0123456789ABCDEF
[ 7556.309244] hid-generic 0003:17EF:30B4.0010: hiddev2,hidraw7: USB HID v1.11 
Device [Lenovo ThinkPad Thunderbolt 4 Dock MCU Contoller] on 
usb-:00:14.0-5.1/input0
[ 7556.981411] igc :49:00.0 enp73s0: NIC Link is Up 1000 Mbps Full Duplex, 
Flow Control: RX/TX
[ 7556.981648] IPv6: ADDRCONF(NETDEV_CHANGE): enp73s0: link becomes ready
[ 7557.130669] igc :49:00.0 enp73s0: PCIe link lost, device now detached
[ 7557.130677] [ cut here ]
[ 7557.130678] igc: Failed to read reg 0xc030!
[ 7557.130690] WARNING: CPU: 13 PID: 1735 at 
drivers/net/ethernet/intel/igc/igc_main.c:6412 igc_rd32+0xaf/0xc0 [igc]
[ 7557.130701] Modules linked in: igc ccm rfcomm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype br_netfilter bridge stp llc 
vboxnetadp(O) vboxnetflt(O) vboxdrv(O) xt_comment nft_compat nf_tables 
nfnetlink cmac algif_hash algif_skcipher af_alg overlay bnep binfmt_misc 
dm_crypt nvidia_uvm(PO) nvidia_drm(PO) nvidia_modeset(PO) intel_tcc_cooling 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_ctl_led snd_soc_skl_hda_dsp 
kvm_intel snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi snd_sof_probes kvm 
nvidia(PO) irqbypass snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic 
snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel 
soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_compress 
ac97_bus nls_iso8859_1
[ 7557.130735]  snd_hda_codec_hdmi snd_pcm_dmaengine rapl iwlmvm btusb 
snd_hda_intel btrtl snd_intel_dspcfg btbcm snd_usb_audio mac80211 
snd_intel_sdw_acpi btintel uvcvideo snd_usbmidi_lib snd_hda_codec btmtk 
videobuf2_vmalloc snd_seq_midi libarc4 mei_hdcp 
processor_thermal_device_pci_legacy mei_pxp snd_seq_midi_event videobuf2_memops 
cmdlinepart snd_hda_core bluetooth intel_rapl_msr processor_thermal_device 
snd_rawmidi snd_seq iwlwifi videobuf2_v4l2 spi_nor snd_hwdep think_lmi 
processor_thermal_rfim thinkpad_acpi ecdh_generic snd_seq_device intel_cstate 
serio_raw videodev snd_pcm joydev mtd firmware_attributes_class input_leds 
videobuf2_common cfg80211 processor_thermal_mbox wmi_bmof ee1004 nvram mc ecc 
snd_timer mei_me processor_thermal_rapl mei snd intel_rapl_common ledtrig_audio 
soundcore intel_soc_dts_iosf int3403_thermal int3400_thermal platform_profile 
intel_hid int340x_thermal_zone acpi_thermal_rel mac_hid acpi_pad acpi_tad 
sparse_keymap sch_fq_codel vcan can_dev msr parport_
 pc
[ 7557.130769]  ppdev lp parport efi_pstore ip_tables x_tables autofs4 btrfs 
blake2b_generic xor raid6_pq libcrc32c hid_logitech_hidpp hid_logitech_dj 
hid_generic usbhid hid i915 drm_buddy i2c_algo_bit ttm drm_display_helper cec 
rc_core crct10dif_pclmul crc32_pclmul drm_kms_helper polyval_clmulni 
syscopyarea polyval_generic sysfillrect ghash_clmulni_intel sha512_ssse3 
aesni_intel sysimgblt nvme crypto_simd ucsi_acpi rtsx_pci_sdmmc i2c_i801 drm 
xhci_pci nvme_core cryptd psmouse spi_intel_pci typec_ucsi spi_intel 
thunderbolt i2c_smbus rtsx_pci xhci_pci_renesas nvme_common video typec wmi 
pinctrl_tigerlake [last unloaded: igc]
[ 7557.130793] CPU: 13 PID: 1735 Comm: pulsesecure Tainted: PW  O   
6.2.0-33-generic #33~22.04.1-Ubuntu
[ 7557.130795] Hardware name: LENOVO 20YRS21300/20YRS21300, BIOS N37ET46W (1.27 
) 07/12/2023
[ 7557.130795] RIP: 0010:igc_rd32+0xaf/0xc0 [igc]
[ 7557.130801] Code: bc ff ff ff ff 5b 44 89 e0 41 5c 41 5d 41 5e 5d 31 d2 31 
f6 31 ff c3 cc cc cc cc 44 89 ee 48 c7 c7 f8 85 38 c0 e8 01 56 57 e3 <0f> 0b e9 
74 ff ff ff 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90
[ 7557.130803] RSP: 0018:9f5982d035b0 EFLAGS: 00010246
[ 7557.130804] RAX:  RBX: 90add0bf8c60 RCX: 
[ 7557.130806] RDX:  RSI:  RDI: 
[ 7557.130806] RBP: 9f5982d035d0 R08:  R09: 
[ 7557.130807] R10:  R11:  R12: 
[ 7557.130808] R13: c030 R14: 90add0bf8000 R15: 90ac4313cd80
[ 7557.130809] FS:  7f2b2a3ff640() GS:90b76f74() 
knlGS:
[ 7557.130810] CS:  0010 DS:  ES:  CR0: 80050033
[ 7557.130811] CR2: 29bc0067b0a0 CR3: 00010e072001 CR4: 00770ee0
[ 7557.130812] PKRU: 5554
[ 7557.130812] Call Trace:
[ 7557.130813]  
[ 7557.130815]  ? show_regs+0x72/0x90
[ 7557.130818]  ? igc_rd32+0xaf/0xc0 [igc]
[ 7557.130823]  ? __warn+0x8d/0x160
[

[Kernel-packages] [Bug 2049327] Re: `alsactl init` unable to initialze audio device on G700

2024-01-23 Thread ethan.hsieh

Verified packages on jammy- and mantic-proposed. Here is the test
result:

$ alsactl init
alsa-lib main.c:761:(execute_sequence) unable to execute cset 
'name='DP_OUT_MUX' Disconnect'
alsa-lib main.c:2373:(set_boot_user) Unable to execute boot sequence
Found hardware: "mt8390-evk" "" "" "" ""
Hardware is initialized using a generic method

# Install the package on jammy-proposed
$ alsactl init
# no error message
$ apt-cache policy alsa-ucm-conf | grep Installed
  Installed: 1.2.6.3-1ubuntu1.10

# Install the package on mantic-proposed
$ alsactl init
# no error message
$ apt-cache policy alsa-ucm-conf | grep Installed
  Installed: 1.2.9-1ubuntu3.2


** Tags removed: verification-needed-jammy verification-needed-mantic
** Tags added: verification-done-jammy verification-done-mantic

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

Title:
  `alsactl init` unable to initialze audio device on G700

Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed
Status in alsa-ucm-conf source package in Mantic:
  Fix Committed

Bug description:
  [Impact]
  This bug cause "alsactl init" command unable to initialize mt8390-evk 
correctly and print these error message:

  ```
  ceqa@ubuntu:/home/ceqa$ alsactl init
  alsa-lib main.c:761:(execute_sequence) unable to execute cset 
'name='DP_OUT_MUX' Disconnect'
  alsa-lib main.c:2373:(set_boot_user) Unable to execute boot sequence
  Found hardware: "mt8390-evk" "" "" "" ""
  Hardware is initialized using a generic method
  ```

  Thus, the audio devices on MediaTek G700 do not work.

  This patch fix this bug by correcting 'DP_OUT_MUX' to 'DPTX_OUT_MUX'.

  [ Test Plan ]
  Reproduce:
  1. Install Ubuntu 22.04 (jammy) on a MediaTek G700 device
  2. Run `alsactl init` on MediaTek G700 device
  3. alsactl print error message "unable to execute cset 'name='DP_OUT_MUX' 
Disconnect'" and audio devices do not work.

  Verify:
  By applying this patch, alsactl does not print this error message and audio 
devices work.

  
  [Where problems could occur]
  This patch fix the typo in ucm files, and it affects the device init process 
on Mediatek Genio boards.

  
  [ Other Info ]
  There is a typo in 
'd/p/0001-Add-initial-support-for-MediaTek-Genio-boards.patch'.

  The name of the flag that controls the audio output of the DP port is
  not 'DP_OUT_MUX'. It is 'DPTX_OUT_MUX'.

  MediaTek fix this issue in the PR in upstream:
  
https://github.com/alsa-project/alsa-ucm-conf/compare/243f2d60740e41a0cfb7779388c17e4a00e1bfe9..a55f840ab2b13f32cb55cd1730933ef0f5a96079

  
  mt8390-evk (G700) Pull Request: (Still under review)
  https://github.com/alsa-project/alsa-ucm-conf/pull/321

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


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

[Kernel-packages] [Bug 2050098] Re: cgroup2 appears to be broken

** Package changed: linux (Ubuntu) => linux-signed (Ubuntu)

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

Title:
  cgroup2 appears to be broken

Status in linux-signed package in Ubuntu:
  New

Bug description:
  We're using Slurm workload manager in a cluster with Ubuntu 22.04 and
  the linux-generic kernel (amd64). We  use cgroups (cgroup2) for
  resource allocation with Slurm. With kernel version

  linux-image-5.15.0-91-generic 5.15.0-91.101
  amd64

  I'm seeing a new issue. This must have been introduced recently, I can
  confirm that with kernel 5.15.0-88-generic the issue does not exist.
  When I request a single GPU on a node with kernel 5.15.0-88-generic
  all is well:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  GPU 0: NVIDIA [...]

  Instead with kernel 5.15.0-91-generic:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  slurmstepd: error: load_ebpf_prog: BPF load error (No space left on device). 
Please check your system limits (MEMLOCK).
  GPU 0: NVIDIA [...]
  GPU 1: NVIDIA [...]
  GPU 2: NVIDIA [...]
  GPU 3: NVIDIA [...]
  GPU 4: NVIDIA [...]
  GPU 5: NVIDIA [...]
  GPU 6: NVIDIA [...]
  GPU 7: NVIDIA [...]

  So I get this error regarding MEMLOCK limit and see all GPUs in the
  system instead of only the one requested. Hence I assume the problem
  is related to cgroups.

  $ cat /proc/version_signature
  Ubuntu 5.15.0-91.101-generic 5.15.131

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


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

[Kernel-packages] [Bug 2050885] [NEW] hd will not mount

2024-01-23 Thread tim riggs

Public bug reported:

I now have two hd that will not work on linux but work on window 11 .

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-14-generic 6.5.0-14.14
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tlr2004 F wireplumber
 /dev/snd/seq:tlr1987 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 23 06:03:16 2024
HotplugNewDevices:
 
HotplugNewMounts:
 
InstallationDate: Installed on 2023-11-13 (71 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=88481562-dc81-4d92-bc63-a1c80eeb6605 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-6.5.0-14-generic N/A
 linux-backports-modules-6.5.0-14-generic  N/A
 linux-firmware20230919.git3672ccab-0ubuntu2.5
SourcePackage: linux
Symptom: storage
UdisksMonitorLog:
 Monitoring the udisks daemon. Press Ctrl+C to exit.
 06:03:39.779: The udisks-daemon is running (name-owner :1.8).
UpgradeStatus: Upgraded to mantic on 2024-01-22 (1 days ago)
dmi.bios.date: 07/03/2023
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: JB20B001
dmi.board.asset.tag: Default string
dmi.board.name: JB20B
dmi.board.vendor: Default string
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.ec.firmware.release: 1.2
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrJB20B001:bd07/03/2023:br5.19:efr1.2:svnDefaultstring:pnJB20B:pvrDefaultstring:rvnDefaultstring:rnJB20B:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU1:
dmi.product.family: MiniPC
dmi.product.name: JB20B
dmi.product.sku: SKU1
dmi.product.version: Default string
dmi.sys.vendor: Default string

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


** Tags: amd64 apport-bug mantic wayland-session

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

Title:
  hd will not mount

Status in linux package in Ubuntu:
  New

Bug description:
  I now have two hd that will not work on linux but work on window 11 .

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tlr2004 F wireplumber
   /dev/snd/seq:tlr1987 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 06:03:16 2024
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2023-11-13 (71 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=88481562-dc81-4d92-bc63-a1c80eeb6605 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.5
  SourcePackage: linux
  Symptom: storage
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   06:03:39.779: The udisks-daemon is running (name-owner :1.8).
  UpgradeStatus: Upgraded to mantic on 2024-01-22 (1 days ago)
  dmi.bios.date: 07/03/2023
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: JB20B001
  dmi.board.asset.tag: Default string
  dmi.board.name: JB20B
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrJB20B001:bd07/03/2023:br5.19:efr1.2:svnDefaultstring:pnJB20B:pvrDefaultstring:rvnDefaultstring:rnJB20B:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU1:
  dmi.product.family: MiniPC
  dmi.product.name: JB20B
  dmi.product.sku: SKU1

[Kernel-packages] [Bug 2049924] Re: WireGuard broken on Noble ppc64el

2024-01-23 Thread Frank Heimes

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => bugproxy (bugproxy)

** Tags added: noble ppc64el reverse-proxy-bugzilla

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

Title:
  WireGuard broken on Noble ppc64el

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New
Status in linux source package in Noble:
  New
Status in netplan.io source package in Noble:
  New

Bug description:
  Netplan autopkgtests related to Wireguard are currently failing (see
  below) on Noble ppc64el. Trying it manually on a ppc64el system, I
  can't load the kernel module:

  ~# modprobe wireguard
  modprobe: ERROR: could not insert 'wireguard': No such device

  
  And because of that the interface can't be created:

  Jan 19 15:47:59 mantic-bos01-ppc64el NetworkManager[2414]:   
[1705679279.5797] platform-linux: do-add-link[wg0/wireguard]: failure 95 
(Operation not supported - Unknown device type)
  Jan 19 15:47:59 mantic-bos01-ppc64el NetworkManager[2414]:  
[1705679279.5797] manager: (netplan-wg0) couldn't create the device: Failed to 
create WireGuard interface 'wg0' for 'netplan-wg0': Operation not supported

  
  Jan 19 15:45:08 mantic-bos01-ppc64el systemd-networkd[731]: 
/run/systemd/network/10-netplan-wg0.netdev has 0644 mode that is too 
permissive, please adjust the ownership and access mode.
  Jan 19 15:45:08 mantic-bos01-ppc64el systemd-networkd[731]: wg0: netdev could 
not be created: Operation not supported

  
  Autopkgtest error:

  2690s .Interface "wg0" not found.
  2691s .Interface "wg0" not found.
  2692s .Interface "wg0" not found.
  2693s ..Interface "wg0" not found.
  2694s Interface "wg0" not found.
  2695s .Interface "wg0" not found.
  2696s .Interface "wg0" not found.
  2697s .Interface "wg0" not found.
  2697s FAIL
  2697s 
  2697s ==
  2697s FAIL: test_tunnel_wireguard 
(__main__.TestNetworkManager.test_tunnel_wireguard)
  2697s --
  2697s Traceback (most recent call last):
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/tunnels.py", line 126, 
in test_tunnel_wireguard
  2697s self.generate_and_settle(['wg0', 'wg1'])
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 363, in 
generate_and_settle
  2697s self.nm_wait_connected(iface, 60)
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 419, in 
nm_wait_connected
  2697s self.wait_output(['nmcli', 'dev', 'show', iface], '(connected', 
timeout)
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 416, in 
wait_output
  2697s self.fail('timed out waiting for "{}" to appear in 
{}'.format(expected_output, cmd))
  2697s AssertionError: timed out waiting for "(connected" to appear in 
['nmcli', 'dev', 'show', 'wg0']
  2697s 
  2697s ==
  2697s FAIL: test_tunnel_wireguard 
(__main__.TestNetworkd.test_tunnel_wireguard)
  2697s --
  2697s Traceback (most recent call last):
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/tunnels.py", line 126, 
in test_tunnel_wireguard
  2697s self.generate_and_settle(['wg0', 'wg1'])
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 365, in 
generate_and_settle
  2697s self.networkd_wait_connected(iface, 60)
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 423, in 
networkd_wait_connected
  2697s self.wait_output(['networkctl', 'status', iface], '(configured', 
timeout)
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 416, in 
wait_output
  2697s self.fail('timed out waiting for "{}" to appear in 
{}'.format(expected_output, cmd))
  2697s AssertionError: timed out waiting for "(configured" to appear in 
['networkctl', 'status', 'wg0']
  2697s 
  2697s --
  2697s Ran 26 tests in 294.247s

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


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

[Kernel-packages] [Bug 2050098] Re: cgroup2 appears to be broken

** Description changed:

  We're using Slurm workload manager in a cluster with Ubuntu 22.04 and
  the linux-generic kernel (amd64). We  use cgroups (cgroup2) for resource
  allocation with Slurm. With kernel version
  
  linux-image-5.15.0-91-generic 5.15.0-91.101
  amd64
  
- I'm seeing a new issue. This must have been introduces recently, I can
+ I'm seeing a new issue. This must have been introduced recently, I can
  confirm that with kernel 5.15.0-88-generic the issue does not exist.
  When I request a single GPU on a node with kernel 5.15.0-88-generic all
  is well:
  
  $ srun -G 1 -w gpu59 nvidia-smi -L
  GPU 0: NVIDIA [...]
- 
  
  Instead with kernel 5.15.0-91-generic:
  
  $ srun -G 1 -w gpu59 nvidia-smi -L
  slurmstepd: error: load_ebpf_prog: BPF load error (No space left on device). 
Please check your system limits (MEMLOCK).
  GPU 0: NVIDIA [...]
  GPU 1: NVIDIA [...]
  GPU 2: NVIDIA [...]
  GPU 3: NVIDIA [...]
  GPU 4: NVIDIA [...]
  GPU 5: NVIDIA [...]
  GPU 6: NVIDIA [...]
  GPU 7: NVIDIA [...]
  
  So I get this error regarding MEMLOCK limit and see all GPUs in the
  system instead of only the one requested. Hence I assume the problem is
  related to cgroups.
  
- $ cat /proc/version_signature 
+ $ cat /proc/version_signature
  Ubuntu 5.15.0-91.101-generic 5.15.131

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

Title:
  cgroup2 appears to be broken

Status in linux package in Ubuntu:
  New

Bug description:
  We're using Slurm workload manager in a cluster with Ubuntu 22.04 and
  the linux-generic kernel (amd64). We  use cgroups (cgroup2) for
  resource allocation with Slurm. With kernel version

  linux-image-5.15.0-91-generic 5.15.0-91.101
  amd64

  I'm seeing a new issue. This must have been introduced recently, I can
  confirm that with kernel 5.15.0-88-generic the issue does not exist.
  When I request a single GPU on a node with kernel 5.15.0-88-generic
  all is well:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  GPU 0: NVIDIA [...]

  Instead with kernel 5.15.0-91-generic:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  slurmstepd: error: load_ebpf_prog: BPF load error (No space left on device). 
Please check your system limits (MEMLOCK).
  GPU 0: NVIDIA [...]
  GPU 1: NVIDIA [...]
  GPU 2: NVIDIA [...]
  GPU 3: NVIDIA [...]
  GPU 4: NVIDIA [...]
  GPU 5: NVIDIA [...]
  GPU 6: NVIDIA [...]
  GPU 7: NVIDIA [...]

  So I get this error regarding MEMLOCK limit and see all GPUs in the
  system instead of only the one requested. Hence I assume the problem
  is related to cgroups.

  $ cat /proc/version_signature
  Ubuntu 5.15.0-91.101-generic 5.15.131

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


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

[Kernel-packages] [Bug 2045969] Re: package linux-image-6.2.0-39-generic 6.2.0-39.40 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11

2024-01-23 Thread FACELLO

Thanks for your answer, but now it's work with new generix package !

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

Title:
  package linux-image-6.2.0-39-generic 6.2.0-39.40 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with
  return code 11

Status in linux-signed package in Ubuntu:
  New

Bug description:
  I don't kno why my computer is blocked just 15 s afeter start up

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-39-generic 6.2.0-39.40
  ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2.1
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Fri Dec  8 12:03:31 2023
  DpkgHistoryLog:
   Start-Date: 2023-12-08  12:03:21
   Commandline: /usr/bin/unattended-upgrade
   Install: linux-signatures-nvidia-6.2.0-39-generic:amd64 (6.2.0-39.40, 
automatic), linux-modules-6.2.0-39-generic:amd64 (6.2.0-39.40, automatic), 
linux-modules-nvidia-525-6.2.0-39-generic:amd64 (6.2.0-39.40, automatic), 
linux-image-6.2.0-39-generic:amd64 (6.2.0-39.40, automatic), 
linux-objects-nvidia-525-6.2.0-39-generic:amd64 (6.2.0-39.40, automatic)
   Upgrade: linux-modules-nvidia-525-generic-hwe-22.04:amd64 (6.2.0-37.38+1, 
6.2.0-39.40), linux-modules-nvidia-510-generic-hwe-22.04:amd64 (6.2.0-37.38+1, 
6.2.0-39.40), linux-libc-dev:amd64 (6.2.0-37.38, 6.2.0-39.40)
  ErrorMessage: installed linux-image-6.2.0-39-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2022-10-31 (403 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming A17 FA706ICB_TUF706ICB
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic 
root=UUID=8e316101-89cb-4820-a4b4-a076b22a5c2c ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux-signed
  Title: package linux-image-6.2.0-39-generic 6.2.0-39.40 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2022
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA706ICB.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FA706ICB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFA706ICB.304:bd04/11/2022:br5.16:efr3.2:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingA17FA706ICB_TUF706ICB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA706ICB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUS TUF Gaming A17
  dmi.product.name: ASUS TUF Gaming A17 FA706ICB_TUF706ICB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1972728] Re: Night light not working on Nvidia Wayland

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

** Changed in: nvidia-graphics-drivers-545 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Night light not working on Nvidia Wayland

Status in Mutter:
  New
Status in nvidia-graphics-drivers-545 package in Ubuntu:
  Fix Released

Bug description:
  On the Wayland session using an Nvidia GPU, enabling the Night Light
  setting in the Settings app doesn't change the screen colour
  temperature to a warmer hue regardless of "Sunset to Sunrise" or
  "Manual Schedule" being selected. Switching to the X11 session results
  in Night Light working as expecting.

  I'm currently using the Nvidia 510.60.02 driver (RTX 2080Ti).

  $ lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 42.0-2ubuntu1
Candidate: 42.0-2ubuntu1
Version table:
   *** 42.0-2ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  9 22:01:57 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-04-29 (10 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1972728] [NEW] Night light not working on Nvidia Wayland

You have been subscribed to a public bug:

On the Wayland session using an Nvidia GPU, enabling the Night Light
setting in the Settings app doesn't change the screen colour temperature
to a warmer hue regardless of "Sunset to Sunrise" or "Manual Schedule"
being selected. Switching to the X11 session results in Night Light
working as expecting.

I'm currently using the Nvidia 510.60.02 driver (RTX 2080Ti).

$ lsb_release -rd
Description:Ubuntu 22.04 LTS
Release:22.04

$ apt-cache policy gnome-shell
gnome-shell:
  Installed: 42.0-2ubuntu1
  Candidate: 42.0-2ubuntu1
  Version table:
 *** 42.0-2ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.0-2ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon May  9 22:01:57 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-04-29 (10 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
RelatedPackageVersions: mutter-common 42.0-3ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mutter
 Importance: Unknown
 Status: New

** Affects: nvidia-graphics-drivers-545 (Ubuntu)
 Importance: Medium
 Status: Fix Released


** Tags: amd64 apport-bug jammy nvidia nvidia-wayland wayland-session
-- 
Night light not working on Nvidia Wayland
https://bugs.launchpad.net/bugs/1972728
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to nvidia-graphics-drivers-545 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 2050103] Re: Integrated Laptop screen not detected on 6.5 hwe - Intel UHD 630 Coffee Lake

2024-01-23 Thread Roxana Nicolescu

Can you also attach the boot logs for both versions? Thanks

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

Title:
  Integrated Laptop screen not detected on 6.5 hwe - Intel UHD 630
  Coffee Lake

Status in linux-hwe-6.5 package in Ubuntu:
  New

Bug description:
  lsb_release
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04
  Codename: jammy

  Laptop: Rebadged Clevo
  Graphics: on-board Intel UHD 630 

  Updated from kernel 6.2.0-39-generic to 6.5.0-14-generic

  Problem:- LCD laptop screen not detected on kernel 6.5.0-14

  The laptop LCD screen is black but the external RGB monitor works
  fine. Using kernel 6.2.0-39, both the LCD and external monitor work.

  inxi -Gxx  on 6.2 kernel shows 2 Monitors - DP-1 is the external and eDP-1 is 
the LCD
  Graphics:
Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: CLEVO/KAPOK
  driver: i915 v: kernel ports: active: DP-1,eDP-1 empty: HDMI-A-1,HDMI-A-2
  bus-ID: 00:02.0 chip-ID: 8086:3e9b
Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 1-8:4
  chip-ID: 5986:2110
Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.1
  compositor: gnome-shell v: 42.9 driver: X: loaded: vesa
  unloaded: fbdev,modesetting gpu: i915 display-ID: 0
Monitor-1: DP-1 model: Vw19B2 res: 1440x900 dpi: 89 diag: 483mm (19")
Monitor-2: eDP-1 model: LG res: 1920x1080 dpi: 128 diag: 438mm (17.3")
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
  v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes

  inxi -Gxx  on 6.5 kernel shows 1 Monitor - DP-1 is the external
  Graphics:
Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: CLEVO/KAPOK
  driver: i915 v: kernel ports: active: DP-1 empty: HDMI-A-1,HDMI-A-2
  bus-ID: 00:02.0 chip-ID: 8086:3e9b
Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 1-8:4
  chip-ID: 5986:2110
Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.1
  compositor: gnome-shell v: 42.9 driver: X: loaded: vesa
  unloaded: fbdev,modesetting gpu: i915 display-ID: 0
Monitor-1: DP-1 model: Vw19B2 res: 1440x900 dpi: 89 diag: 483mm (19")
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
  v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes

  This line using journalctl is in the boot log of kernel 6.2 but not in the 
boot log of 6.5(probably not relevant)
  Jan 14 15:27:20 hybris kernel: i915 :00:02.0: [drm] Skipping 
intel_backlight registration

  Have noticed Bug:- https://answers.launchpad.net/bugs/2049245 which is
  against nvidia graphics but will try 1024x768 resolution.

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


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

[Kernel-packages] [Bug 2048988] Re: 1 time ib_umda loading fail during 105 power cycle

2024-01-23 Thread Zhanglei Mao

** Summary changed:

- 1 time ib_umda lloading fail during 105 power cycle 
+ 1 time ib_umda loading fail during 105 power cycle

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

Title:
  1 time ib_umda loading fail during 105 power cycle

Status in linux-hwe-5.15 package in Ubuntu:
  New

Bug description:
  found error log like below in 105 power cycles.

  Dec 23 02:09:27 192-168-111-160 root[5747]: openibd: ERROR: Failed
  loading kernel module ib_umad.

  Dec 23 02:09:27 192-168-111-160 root[5750]: openibd: ERROR: Failed
  loading kernel module ib_ipoib.

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


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

[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen