date:20230525

** Also affects: nvidia-graphics-drivers-390 (Ubuntu Lunar)
   Importance: Undecided
   Status: New

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

** Also affects: nvidia-graphics-drivers-470 (Ubuntu Lunar)
   Importance: Undecided
   Status: New

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

** Also affects: nvidia-graphics-drivers-510 (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-515 (Ubuntu Lunar)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

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

** No longer affects: nvidia-graphics-drivers-450-server (Ubuntu Lunar)

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

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

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

** No longer affects: nvidia-graphics-drivers-470-server (Ubuntu Lunar)

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

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

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

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

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

** No longer affects: nvidia-graphics-drivers-515-server (Ubuntu Lunar)

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

Title:
  nvidia-dkms-* FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Mantic:
  New
Status in nvidia-graphics-drivers-470 source package in Mantic:
  New
Status in nvidia-graphics-drivers-470-server source package in Mantic:
  New
Status in nvidia-graphics-drivers-510 source package in Mantic:
  New
Status in nvidia-graphics-drivers-515 source package in Mantic:
  New
Status in nvidia-graphics-drivers-515-server source package in Mantic:
  New

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA it

[Kernel-packages] [Bug 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)

2023-05-25 Thread Alberto Donato

** Changed in: maas
Milestone: 3.4.0 => 3.4.0-beta2

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

Title:
  udev fails to make prctl() syscall with apparmor=0 (as used by maas by
  default)

Status in AppArmor:
  New
Status in MAAS:
  Fix Committed
Status in maas-images:
  Invalid
Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Invalid
Status in apparmor source package in Lunar:
  New
Status in linux source package in Lunar:
  Fix Committed
Status in systemd source package in Lunar:
  New

Bug description:
  I'm assuming the image being used for these deploys is 20230417 or
  20230417.1 based on the fact that I saw a 6.2 kernel being used which
  I don't believe was part of the 20230319 serial. I don't have access
  to the maas server, so I can't directly check any log files.

  MAAS Version: 3.3.2

  Here's where the serial log indicates it can't download the squashfs. The 
full log is attached as scobee-lunar-no-squashfs.log (there are some other 
console message intermixed):
  no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf 
/run/net6
  -*.conf
  :: 
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
  date/squa[  206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes, 
fsverity
  =yes
  shfs
  :: mount_squash downloading 
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
  4/lunar/candidate/squashfs to /root.tmp.img
  Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
  wget: can't connect to remote host (10.229.32.21): Network is unreachable
  :: mount -t squashfs -o loop  '/root.tmp.img' '/root.tmp'
  mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
  done.

  Still gathering logs and info and will update as I go.

  
  Kernel Bug / Apparmor
  reproducer

  $ wget 
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
  $ wget 
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
  $ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd 
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'

  #start the VM
  
  Starting systemd-udevd version 252.5-2ubuntu3
  Spawning shell within the initramfs

  BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs) udevadm info --export-db
  Failed to set death signal: Invalid argument

  Observe that udevadm fails to setup death signal, with in systemd code
  is this

  
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
  util.c#L1252

  if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
  if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ? 
SIGINT : SIGTERM) < 0) {
  log_full_errno(prio, errno, "Failed to set death 
signal: %m");
  _exit(EXIT_FAILURE);
  }

  
  workaround set kernel commandline to `apparmor=1`
  

  MAAS bug
  Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor. 
Even for deployment and commisioning.

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


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

[Kernel-packages] [Bug 2019869] Re: nvidia-dkms-390: better support for kernel 6.2

Attached debdiff contains the SRU patch to fix the same nvidia-dkms-390
build error with kernel 6.2 for lunar.

** Patch added: "nvidia-dkms-390-lunar-better-support-for-linux-6.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019869/+attachment/5675576/+files/nvidia-dkms-390-lunar-better-support-for-linux-6.2.debdiff

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

Title:
  nvidia-dkms-390: better support for kernel 6.2

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-390 source package in Lunar:
  Confirmed
Status in nvidia-graphics-drivers-390 source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  Instead of disabling acpi support completely with nvidia-dkms-390, we
  should try instead to see if it's possible to support it somehow.

  [Fix]

  This patch looks promising (even if it says huge hack in the comments...):
  
https://gitlab.com/herecura/packages/nvidia-390xx-dkms/-/blob/780a3c8b159f24c14e6c1cb35fd747338aefea39/kernel-6.2.patch

  Apply this patch and drop any 6.0 and 6.2 related patches.

  [Regression potential]

  With this patch nvidia-dkms-390 should build against 6.2 kernels
  without disabling any feature, but users of this driver may experience
  kernel bugs / crashes. However, the nvidia 390 driver is unmaintained
  so we should start to consider phasing it out.

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


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

[Kernel-packages] [Bug 2020647] Re: Upgrade from 22.04 to 22.10 won't boot

2023-05-25 Thread Jan Pfeifer

A few updates: I downloaded a Ubuntu 23.04 in a USB stick and I can
consistently boot from it, it uses kernel 6.2.0.

But when I try to boot it the same kernel from my hard drive
(/dev/nvme0n1p1) it freezes just after grub initializes initrd --
nothing is printed, even though I passed "loglevel=7" parameter to the
kernel.

I'm still able to boot on a 5.17 (Linux galactica 5.17.5-051705-generic)
kernel on the new system.

So I tried to eliminate differences, and copied over the directories
`/etc/modprobe.d` and `/etc/modules-load.d` and the `/etc/modules` file
from my usb stick to my system. That didn't solve it though. But I did a
diff of which kernel modules are installed in my system by default
(kernel 5.17.5) that are not in the usb stick 23.04 (kernel 6.2.0).
These are:

> bridge
> br_netfilter
> dm_crypt
> fb_sys_fops
> hwmon_vid
> intel_tcc_cooling
> llc
> nf_conntrack
> nf_conntrack_netlink
> nf_defrag_ipv4
> nf_defrag_ipv6
> nf_log_syslog
> nf_nat
> nfnetlink
> nf_tables
> nft_chain_nat
> nft_compat
> nft_limit
> stp
> xfrm_algo
> xfrm_user
> xt_addrtype
> xt_conntrack
> xt_limit
> xt_LOG
> xt_MASQUERADE
> xt_state
> xt_tcpudp

I suppose something changed after kernel 5.17 (kernel 5.19 also doesn't
boot) and is incompatible with something. Not sure what.

Anything I can do to make the kernel (or maybe it's even grub ?) print
out whatever it's doing before crashing ?

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

Title:
  Upgrade from 22.04 to 22.10 won't boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I was actually meaning to upgrade to 23.04, but the updater offered to
  upgrade to 22.10 first, so I supposed this was needed.

  After a standard upgrade with the UI, even the recovery boot never
  passes the "Loading initial ramdisk ..." line -- it silently freezes.

  I have removed the "quiet splash" options in grub by "dis_ucode_ldr",
  following some random article. Anyway, nothing is displayed after
  "Loading initial ramdisk ..." line.

  I have the following kernel installed:

  5.19.0-42-generic
  5.17.5-051705-generic
  5.15.36-051536-generic
  5.15.0-27-generic (*)
  5.13.0-19-generic
  Plus a dual-boot windows.

  Just the 5.15.0-27-generic boots, but it doesn't mount ethernet for
  some reason. My motherboard uses Realtek 8125, and it used to work
  just fine 10 minutes ago (in 22.04), but now I'm not able to install
  `r8125-dkms` module, because I dont' have the linux-headers version
  installed for that kernel ... I'm also not able to find it to
  download.

  I also have an old 2080ti NVidia card, in case that has any effect on
  this.

  Any suggestions ?

  Thanks

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


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

[Kernel-packages] [Bug 2020757] Re: Kernel BUG (null ptr dereference) with linux-image-5.19.0-42-generic (HWE kernel on 22.04)

2023-05-25 Thread Arvid Norlander

Attached refcount / OOM log

** Attachment added: "refcount error log"

https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2020757/+attachment/5675585/+files/oom.log

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

Title:
Kernel BUG (null ptr dereference) with linux-image-5.19.0-42-generic
(HWE kernel on 22.04)

Status in linux-signed-hwe-5.19 package in Ubuntu:
New

Bug description:
I use Ubuntu 22.04 in VMWare Player 17.0.2 (Windows host, due to
corporate IT...). I installed the HWE kernel since I have an Intel CPU
with P/E-cores. 3D acceleration is enabled in VMWare.

With linux-image-5.19.0-41-generic it is rock solid. With linux-
image-5.19.0-42-generic it invariably crashes after anything between a
minute and an hour.

In the journalctl after rebooting it showed that X.Org had crashed
followed by a Kernel BUG/Oops due to NULL pointer dereference in
drm_gem_object_release_handle. A journalctl log from the Xorg crash up
until the kernel OOPS has been attached to this case.

This issue happened twice with this kernel. In addition, after trying
to reproduce it with kdump tools installed, I got a different issue:
refcount_t: saturated; leaking memory. in the log, leading to the OOM
killing everything on the system, including (based on what was printed
on the terminal), systemd-udevd and journald. That OOM killing never
made it into the journal however, as can be expected. I have attached
what I could get from the journal for this case as well.

One thing that helped trigger this bug (but not every time) was
launching Firefox, but once it didn't crash from that and only crashed
much much later.

Unfortunately I could not get ubuntu-bug to work for this case. I
tried "ubuntu-bug --package linux-image-5.19.0-42-generic" but it did
absolutely nothing. I'm happy to provide any additional information
you require however.

$ lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04
$ apt-cache policy linux-generic-hwe-20.04
linux-generic-hwe-20.04:
Installed: (none)
Candidate: 5.15.0.72.70
Version table:
5.15.0.72.70 500
500 http://se.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64
Packages
5.15.0.25.27 500
500 http://se.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
$ apt-cache policy linux-image-5.19.0-42-generic
linux-image-5.19.0-42-generic:
Installed: 5.19.0-42.43~22.04.1
Candidate: 5.19.0-42.43~22.04.1
Version table:
*** 5.19.0-42.43~22.04.1 500
500 http://se.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64
Packages
100 /var/lib/dpkg/status

What I expected to happen: No crash.
What happened instead: The crash in the attached log.

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

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

[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM

2023-05-25 Thread Samer Attrah

@Giuliano
Hello,

Thanks for your reply, I have compiled the uvc_video.c file today and
the camera is still not working,

I will be looking forward to other instructions from you and others, I
hope for the camera to start

functioning earliest possible.


Kind regards
Samer Attrah

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

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing',
  USB 0408:4035.

  The camera is reported to have problems by many users:  
  https://linux-hardware.org/?id=usb:0408-4035
  The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera 
is “recongized” but fails installation.

  My console commands report similar info to other users: 
  
https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58

  
  PROPOSED SOLUTION 
  I got in contact with laurent.pinch...@ideasonboard.com   and with 
riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And  
me...@vger.kernel.org mailinglist.

  Laurent proposed me a fix and I modified the 5,15 uvc_driver.c
  version, and loaded it on github

  https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-
  Facing-0x0408-0x4035-/blob/main/uvc_driver.c

  I offered to test the fix, so I tried to compile the module with the
  new source.

  COMPILING PROBLEMS
  I’m running **Ubuntu 22.04.1 LTS, with kernel 
  giuliano@Astra2A:/usr/src$ cat /proc/version_signature
  Ubuntu 5.15.0-56.62-generic 5.15.64

  BUT  the linux-source that I found installed seems to be different
  tgiuliano@Astra2A:/usr/src$ ls -al linux-so*
  lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> 
linux-source-5.15.0/linux-source-5.15.0.tar.bz2

  I expanded  the tar file, configured the IDE and compiled without error  any 
errors… 
  I manually copied the uvcvideo.ko in 
  /lib/modules/5.15.0-56-
  sudo cp…...

  then tryed to intall the new uvcvideo.ko module
  sudo rmmod uvcvideo && sudo modprobe uvcvideo

  BUT… IT FAILS
  giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo
  modprobe: ERROR: could not insert 'uvcvideo': Exec format error

  and dmesg shows
  [25961.151982] usbcore: registered new interface driver uvcvideo
  [26323.125534] usbcore: deregistering interface driver uvcvideo
  [26323.189294] uvcvideo: disagrees about version of symbol module_layout


  These are the TWO modinfo from the old and new uvcvideo modules
  https://pastebin.com/tSj8Exm6
  Basically
  OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions 
  NEW module: vermagic: 5.15.64 SMP mod_unload modversions


  -kindly ASK

  HOW can FORCE the uvcdriver.c to match mi kernel version ?
  Have I got OTHER ways to make the kernel module I’m compiling, match my 
running system ?

  I would like to test the module so to confirm the patch and let it
  enter the kernel main stream...

  
  BR
  Giuliano

  PS
  btw…. to allow Eclipse to compile the kernel, I had to pass this commands
  scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_TRUSTED_KEYS

  hope that this does not affect the module layout & checking
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giuliano   2142 F pulseaudio
   /dev/snd/pcmC1D0p:   giuliano   2142 F...m pulseaudio
   /dev/snd/controlC0:  giuliano   2142 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-03 (66 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Nitro AN517-55
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-57-generic N/A
   linux-backports-modules-5.15.0-57-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  Tags:  jammy
  Uname: Linux 5.15.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/20/2022
  dmi.bios.release: 1.6
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V

[Kernel-packages] [Bug 2020757] [NEW] Kernel BUG (null ptr dereference) with linux-image-5.19.0-42-generic (HWE kernel on 22.04)

2023-05-25 Thread Arvid Norlander

Public bug reported:

I use Ubuntu 22.04 in VMWare Player 17.0.2 (Windows host, due to
corporate IT...). I installed the HWE kernel since I have an Intel CPU
with P/E-cores. 3D acceleration is enabled in VMWare.

With linux-image-5.19.0-41-generic it is rock solid. With linux-
image-5.19.0-42-generic it invariably crashes after anything between a
minute and an hour.

In the journalctl after rebooting it showed that X.Org had crashed
followed by a Kernel BUG/Oops due to NULL pointer dereference in
drm_gem_object_release_handle. A journalctl log from the Xorg crash up
until the kernel OOPS has been attached to this case.

This issue happened twice with this kernel. In addition, after trying to
reproduce it with kdump tools installed, I got a different issue:
refcount_t: saturated; leaking memory. in the log, leading to the OOM
killing everything on the system, including (based on what was printed
on the terminal), systemd-udevd and journald. That OOM killing never
made it into the journal however, as can be expected. I have attached
what I could get from the journal for this case as well.

One thing that helped trigger this bug (but not every time) was
launching Firefox, but once it didn't crash from that and only crashed
much much later.

Unfortunately I could not get ubuntu-bug to work for this case. I tried
"ubuntu-bug --package linux-image-5.19.0-42-generic" but it did
absolutely nothing. I'm happy to provide any additional information you
require however.


$ lsb_release -rd
Description:Ubuntu 22.04.2 LTS
Release:22.04
$ apt-cache policy linux-generic-hwe-20.04 
linux-generic-hwe-20.04:
  Installed: (none)
  Candidate: 5.15.0.72.70
  Version table:
 5.15.0.72.70 500
500 http://se.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
 5.15.0.25.27 500
500 http://se.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
$ apt-cache policy linux-image-5.19.0-42-generic 
linux-image-5.19.0-42-generic:
  Installed: 5.19.0-42.43~22.04.1
  Candidate: 5.19.0-42.43~22.04.1
  Version table:
 *** 5.19.0-42.43~22.04.1 500
500 http://se.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
100 /var/lib/dpkg/status

What I expected to happen: No crash.
What happened instead: The crash in the attached log.

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

** Attachment added: "Crash log"
   https://bugs.launchpad.net/bugs/2020757/+attachment/5675584/+files/crash.log

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

Title:
  Kernel BUG (null ptr dereference) with linux-image-5.19.0-42-generic
  (HWE kernel on 22.04)

Status in linux-signed-hwe-5.19 package in Ubuntu:
  New

Bug description:
  I use Ubuntu 22.04 in VMWare Player 17.0.2 (Windows host, due to
  corporate IT...). I installed the HWE kernel since I have an Intel CPU
  with P/E-cores. 3D acceleration is enabled in VMWare.

  With linux-image-5.19.0-41-generic it is rock solid. With linux-
  image-5.19.0-42-generic it invariably crashes after anything between a
  minute and an hour.

  In the journalctl after rebooting it showed that X.Org had crashed
  followed by a Kernel BUG/Oops due to NULL pointer dereference in
  drm_gem_object_release_handle. A journalctl log from the Xorg crash up
  until the kernel OOPS has been attached to this case.

  This issue happened twice with this kernel. In addition, after trying
  to reproduce it with kdump tools installed, I got a different issue:
  refcount_t: saturated; leaking memory. in the log, leading to the OOM
  killing everything on the system, including (based on what was printed
  on the terminal), systemd-udevd and journald. That OOM killing never
  made it into the journal however, as can be expected. I have attached
  what I could get from the journal for this case as well.

  One thing that helped trigger this bug (but not every time) was
  launching Firefox, but once it didn't crash from that and only crashed
  much much later.

  Unfortunately I could not get ubuntu-bug to work for this case. I
  tried "ubuntu-bug --package linux-image-5.19.0-42-generic" but it did
  absolutely nothing. I'm happy to provide any additional information
  you require however.

  
  $ lsb_release -rd
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04
  $ apt-cache policy linux-generic-hwe-20.04 
  linux-generic-hwe-20.04:
Installed: (none)
Candidate: 5.15.0.72.70
Version table:
   5.15.0.72.70 500
  500 http://se.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   5.15.0.25.27 500
  500 http://se.a

[Kernel-packages] [Bug 2020656] Re: system freeze (cpu fan goes high)

2023-05-25 Thread __JEAN_FRANCOIS__

Digging the Internet I reached some posts/bugs that talked about a
problem with some amd cpu that hard time getting out of C6 power state.

So I applied one of the suggested workaround that is: prevent cpu to
enter C6 state so it won't have problem to exit ^^

For this purpose is used cpupower, more precisely I used this command:
cpupower idle-set --disable-by-latency 350

before I ran this command, cpupower moniter résulted in:
| Mperf  || Idle_Stats
 CPU| C0   | Cx   | Freq  || POLL | C1   | C2   | C3
   0|  0,07| 99,93|  1429||  0,00|  0,00| 0,00|  99,86
nearly the same for other cores

I guess it means that all cores can sleep down as much as possible…

after the command, cpupower moniter résulted in:
| Mperf  || Idle_Stats
 CPU| C0   | Cx   | Freq  || POLL | C1   | C2   | C3
   0|  0,07| 99,93|  1429||  0,00|  0,00| 99,91|  0,00
nearly the same for other cores

It seems cores can't sleep as much as before.

I've not really understood what the C6 state is and what the mapping with those 
Cx shown by cpupower is (max for cpupower is C4). 
So far, cpupower idle-set --disable-by-latency 350 seems to do a good job 
preventing the cpu to go to far in sleeping state.

Nearly one full day without a freeze makes my computer usable.

Some questions please:
- any help to understand the C6/Cx mapping?
- is it a software problem (bug in the kernel like I'm guessing and I can hope 
for a fix) or a hardware problem and I should send the computer back to the 
manufacturer?
- I'm on laptop, how to evaluate the impact on the battery usage?

Many thanks

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

Title:
  system freeze (cpu fan goes high)

Status in linux-signed-hwe-5.19 package in Ubuntu:
  New

Bug description:
  More than once a day the system totally freeze.

  CPU fan then goes higher and higher.

  Does not seem to be related to system load as yesterday it happend
  during lunch break.

  Today's journalctl -b -1 last message is 
  mai 24 11:50:06 ThinkPad-P14s kernel: watchdog: BUG: soft lockup - CPU#9 
stuck for 167s! [opt ax7ixzwwoey:158586]

  There are many more of the same kind just before

  
  $ lsb_release -rd
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04

  $ apt-cache policy linux-image-5.19.0-42-generic
  linux-image-5.19.0-42-generic:
Installé : 5.19.0-42.43~22.04.1
Candidat : 5.19.0-42.43~22.04.1
   Table de version :
   *** 5.19.0-42.43~22.04.1 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  Note this problem was present before last kernel updates

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-42-generic 5.19.0-42.43~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 24 12:00:08 2023
  InstallationDate: Installed on 2023-03-25 (59 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   TERM=alacritty
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.19
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2008157] Re: [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace multiple times on Ubuntu 22.04.1 OS during boot

2023-05-25 Thread Jian Hui Lee

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

Title:
  [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace
  multiple times on Ubuntu 22.04.1 OS during boot

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  In Progress

Bug description:
  SRU Justification:

  [Impact]

  When booted into Ubuntu 22.04.1 OS after installation, observed "Array
  Index out of bounds" Call Trace multiple times in dmesg.

  Call Trace is as follow:
  [ 6.125704] UBSAN: array-index-out-of-bounds in 
/build/linux-JjvoxS/linux-5.15.0/drivers/scsi/megaraid/megaraid_sas_fp.c:103:32
  [ 6.125705] index 1 is out of range for type 'MR_LD_SPAN_MAP [1]'
  [ 6.125707] CPU: 0 PID: 18 Comm: kworker/0:1 Not tainted 5.15.0-53-generic 
#59-Ubuntu
  [ 6.125709] Hardware name: Dell Inc. , BIOS 11/08/2022
  [ 6.125710] Workqueue: events work_for_cpu_fn
  [ 6.125716] Call Trace:
  [ 6.125718] 
  [ 6.125720] show_stack+0x52/0x5c
  [ 6.125725] dump_stack_lvl+0x4a/0x63
  [ 6.125731] dump_stack+0x10/0x16
  [ 6.125732] ubsan_epilogue+0x9/0x49
  [ 6.125734] __ubsan_handle_out_of_bounds.cold+0x44/0x49
  [ 6.125736] ? MR_PopulateDrvRaidMap+0x194/0x580 [megaraid_sas]
  [ 6.125747] mr_update_load_balance_params+0xb9/0xc0 [megaraid_sas]
  [ 6.125753] MR_ValidateMapInfo+0x8d/0x290 [megaraid_sas]
  [ 6.125757] megasas_init_adapter_fusion+0x3ce/0x420 [megaraid_sas]
  [ 6.125762] ? megasas_setup_reply_map+0x49/0xac [megaraid_sas]
  [ 6.125768] megasas_init_fw.cold+0x87c/0x10c8 [megaraid_sas]
  [ 6.125774] megasas_probe_one+0x15c/0x4e0 [megaraid_sas]
  [ 6.125779] local_pci_probe+0x48/0x90
  [ 6.125783] work_for_cpu_fn+0x17/0x30
  [ 6.125785] process_one_work+0x228/0x3d0
  [ 6.125786] worker_thread+0x223/0x420
  [ 6.125787] ? process_one_work+0x3d0/0x3d0
  [ 6.125788] kthread+0x127/0x150
  [ 6.125790] ? set_kthread_struct+0x50/0x50
  [ 6.125791] ret_from_fork+0x1f/0x30
  [ 6.125796] 
  [ 6.125796] 


  Steps to reproduce:
  1. Connect PERC H355 controller to the system
  2. Create RAID1 using drives connected to PERC Controller
  3. Install Ubuntu 22.04.1 on VD
  4. Boot into OS after installation
  5. Multiple Call Traces of "array-index-out-of-bounds" are seen

  Expected Behavior:
  OS should boot without this Call Trace

  [Fix]

  [PATCH v3 0/6] Replace one-element arrays with flexible-array members
  
https://lore.kernel.org/linux-hardening/cover.1660592640.git.gustavo...@kernel.org/

  48658213 scsi: megaraid_sas: Use struct_size() in code related to
  struct MR_PD_CFG_SEQ_NUM_SYNC

  41e83026 scsi: megaraid_sas: Use struct_size() in code related to
  struct MR_FW_RAID_MAP

  ee92366a scsi: megaraid_sas: Replace one-element array with flexible-
  array member in MR_PD_CFG_SEQ_NUM_SYNC

  eeb3bab7 scsi: megaraid_sas: Replace one-element array with flexible-
  array member in MR_DRV_RAID_MAP

  204a29a1 scsi: megaraid_sas: Replace one-element array with flexible-
  array member in MR_FW_RAID_MAP_DYNAMIC

  ac23b92b scsi: megaraid_sas: Replace one-element array with flexible-
  array member in MR_FW_RAID_MAP

  [Test Plan]

  1. Connect PERC H355 controller to the system
  2. Create RAID1 using drives connected to PERC Controller
  3. Install Ubuntu 22.04.1 on VD
  4. Boot into OS after installation
  OS should boot without the Call Trace listed in the Impact field

  [Where problems could occur]

  [Other Info]
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/array_bounds_lp_2008157

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


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

[Kernel-packages] [Bug 2020656] Re: system freeze (cpu fan goes high)

2023-05-25 Thread __JEAN_FRANCOIS__

Sadly I managed to freeze it again.
I was testing some ssh parameters,
just did ssh -C -X onto the machine then launched a vscode and moved the mouse 
quickly over the folder list.
No "watchdog: BUG: soft lockup" seen in journalctl

A reddit post mentions that with a lenove T14s (very similar to my P14s) 
disabling Wayland did the trick.
I'm gonna try this.

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

Title:
  system freeze (cpu fan goes high)

Status in linux-signed-hwe-5.19 package in Ubuntu:
  New

Bug description:
  More than once a day the system totally freeze.

  CPU fan then goes higher and higher.

  Does not seem to be related to system load as yesterday it happend
  during lunch break.

  Today's journalctl -b -1 last message is 
  mai 24 11:50:06 ThinkPad-P14s kernel: watchdog: BUG: soft lockup - CPU#9 
stuck for 167s! [opt ax7ixzwwoey:158586]

  There are many more of the same kind just before

  
  $ lsb_release -rd
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04

  $ apt-cache policy linux-image-5.19.0-42-generic
  linux-image-5.19.0-42-generic:
Installé : 5.19.0-42.43~22.04.1
Candidat : 5.19.0-42.43~22.04.1
   Table de version :
   *** 5.19.0-42.43~22.04.1 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  Note this problem was present before last kernel updates

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-42-generic 5.19.0-42.43~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 24 12:00:08 2023
  InstallationDate: Installed on 2023-03-25 (59 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   TERM=alacritty
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.19
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2020757] Re: Kernel BUG (null ptr dereference) with linux-image-5.19.0-42-generic (HWE kernel on 22.04)

2023-05-25 Thread Arvid Norlander

** Description changed:

  I use Ubuntu 22.04 in VMWare Player 17.0.2 (Windows host, due to
  corporate IT...). I installed the HWE kernel since I have an Intel CPU
  with P/E-cores. 3D acceleration is enabled in VMWare.
  
  With linux-image-5.19.0-41-generic it is rock solid. With linux-
  image-5.19.0-42-generic it invariably crashes after anything between a
  minute and an hour.
  
  In the journalctl after rebooting it showed that X.Org had crashed
  followed by a Kernel BUG/Oops due to NULL pointer dereference in
  drm_gem_object_release_handle. A journalctl log from the Xorg crash up
  until the kernel OOPS has been attached to this case.
  
  This issue happened twice with this kernel. In addition, after trying to
  reproduce it with kdump tools installed, I got a different issue:
  refcount_t: saturated; leaking memory. in the log, leading to the OOM
  killing everything on the system, including (based on what was printed
  on the terminal), systemd-udevd and journald. That OOM killing never
  made it into the journal however, as can be expected. I have attached
  what I could get from the journal for this case as well.
  
  One thing that helped trigger this bug (but not every time) was
  launching Firefox, but once it didn't crash from that and only crashed
  much much later.
  
  Unfortunately I could not get ubuntu-bug to work for this case. I tried
  "ubuntu-bug --package linux-image-5.19.0-42-generic" but it did
  absolutely nothing. I'm happy to provide any additional information you
  require however.
  
- 
  $ lsb_release -rd
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04
- $ apt-cache policy linux-generic-hwe-20.04 
- linux-generic-hwe-20.04:
-   Installed: (none)
-   Candidate: 5.15.0.72.70
+ $ apt-cache policy linux-generic-hwe-22.04   
+ linux-generic-hwe-22.04:
+   Installed: 5.19.0.42.43~22.04.15
+   Candidate: 5.19.0.42.43~22.04.15
Version table:
-  5.15.0.72.70 500
- 500 http://se.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
- 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
-  5.15.0.25.27 500
- 500 http://se.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
- $ apt-cache policy linux-image-5.19.0-42-generic 
- linux-image-5.19.0-42-generic:
-   Installed: 5.19.0-42.43~22.04.1
-   Candidate: 5.19.0-42.43~22.04.1
-   Version table:
-  *** 5.19.0-42.43~22.04.1 500
+  *** 5.19.0.42.43~22.04.15 500
  500 http://se.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
+  5.15.0.25.27 500
+ 500 http://se.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
+ $ apt-cache policy linux-image-5.19.0-42-generic
+ linux-image-5.19.0-42-generic:
+   Installed: 5.19.0-42.43~22.04.1
+   Candidate: 5.19.0-42.43~22.04.1
+   Version table:
+  *** 5.19.0-42.43~22.04.1 500
+ 500 http://se.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
+ 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
+ 100 /var/lib/dpkg/status
  
  What I expected to happen: No crash.
  What happened instead: The crash in the attached log.

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

Title:
  Kernel BUG (null ptr dereference) with linux-image-5.19.0-42-generic
  (HWE kernel on 22.04)

Status in linux-signed-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  I use Ubuntu 22.04 in VMWare Player 17.0.2 (Windows host, due to
  corporate IT...). I installed the HWE kernel since I have an Intel CPU
  with P/E-cores. 3D acceleration is enabled in VMWare.

  With linux-image-5.19.0-41-generic it is rock solid. With linux-
  image-5.19.0-42-generic it invariably crashes after anything between a
  minute and an hour.

  In the journalctl after rebooting it showed that X.Org had crashed
  followed by a Kernel BUG/Oops due to NULL pointer dereference in
  drm_gem_object_release_handle. A journalctl log from the Xorg crash up
  until the kernel OOPS has been attached to this case.

  This issue happened twice with this kernel. In addition, after trying
  to reproduce it with kdump tools installed, I got a different issue:
  refcount_t: saturated; leaking memory. in the log, leading to the OOM
  killing everything on the system, including (based on what was printed
  on the terminal), systemd-udevd and journald. That OOM killing never
  made it into the journal however, as can be expected. I have attached
  what I could get from the journal for this case as well.

  One thing that helped trigger this bug (but not every time) was
  launching Firefox, but once it didn't crash from that and only crashed
  much much later.

  Unfortunately I could not get ubuntu-bug to work for this case. I
  tried "ubuntu-bug

[Kernel-packages] [Bug 2020757] Re: Kernel BUG (null ptr dereference) with linux-image-5.19.0-42-generic (HWE kernel on 22.04)

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

** Changed in: linux-signed-hwe-5.19 (Ubuntu)
Status: New => Confirmed

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

Title:
Kernel BUG (null ptr dereference) with linux-image-5.19.0-42-generic
(HWE kernel on 22.04)

Status in linux-signed-hwe-5.19 package in Ubuntu:
Confirmed

With linux-image-5.19.0-41-generic it is rock solid. With linux-
image-5.19.0-42-generic it invariably crashes after anything between a
minute and an hour.

One thing that helped trigger this bug (but not every time) was
launching Firefox, but once it didn't crash from that and only crashed
much much later.

$ lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04
$ apt-cache policy linux-generic-hwe-22.04
linux-generic-hwe-22.04:
Installed: 5.19.0.42.43~22.04.15
Candidate: 5.19.0.42.43~22.04.15
Version table:
*** 5.19.0.42.43~22.04.15 500
500 http://se.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64
Packages
100 /var/lib/dpkg/status
5.15.0.25.27 500
500 http://se.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
$ apt-cache policy linux-image-5.19.0-42-generic
linux-image-5.19.0-42-generic:
Installed: 5.19.0-42.43~22.04.1
Candidate: 5.19.0-42.43~22.04.1
Version table:
*** 5.19.0-42.43~22.04.1 500
500 http://se.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64
Packages
100 /var/lib/dpkg/status

What I expected to happen: No crash.
What happened instead: The crash in the attached log.

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

[Kernel-packages] [Bug 2015956] Re: selftest: fib_tests: Always cleanup before exit

This bug is awaiting verification that the linux-aws/5.19.0-1027.28
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-kinetic' to 'verification-done-kinetic'. If the
problem still exists, change the tag 'verification-needed-kinetic' to
'verification-failed-kinetic'.

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 removed: verification-done-kinetic
** Tags added: kernel-spammed-kinetic-linux-aws verification-needed-kinetic

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

Title:
   selftest: fib_tests: Always cleanup before exit

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux-oem-6.0 source package in Focal:
  Invalid
Status in linux-oem-6.1 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-5.17 source package in Lunar:
  Invalid
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  Copied from the commit message:
  Usage of `set -e` before executing a command causes immediate exit
  on failure, without cleanup up the resources allocated at setup.
  This can affect the next tests that use the same resources,
  leading to a chain of failures.

  A simple fix is to always call cleanup function when the script exists.
  This approach is already used by other existing tests.

  [Fix]
  * b60417a9f2 selftest: fib_tests: Always cleanup before exit

  This patch can be cherry-picked into affected kernels.

  [Test]
  Run the patched fib_tests.sh on KVM kernels, which is expected to fail 
  due to bug 2007458.
  Check with `ip netns`, the ns1 added during setup() should be removed.

  [Where problems could occur]
  Test robustness improvement, this should not break things.

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


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

[Kernel-packages] [Bug 2015498] Re: Debian autoreconstruct Fix restoration of execute permissions

This bug is awaiting verification that the linux-aws/5.19.0-1027.28
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-kinetic' to 'verification-done-kinetic'. If the
problem still exists, change the tag 'verification-needed-kinetic' to
'verification-failed-kinetic'.

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-kinetic-linux-aws

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

Title:
  Debian autoreconstruct Fix restoration of execute permissions

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Confirmed

Bug description:
  SRU justification

  [Impact]

  Debian source package diffs cannot represent that a file should
  be executable.
  gen-auto-reconstruct detects when a commit adds a script that is supposed to 
be invoked during the build and restores the execute permissions in the 
reconstruct script by adding `chmod +x $file`.

  But, if a file removes its execute permission, this will change it back.
  This happened in the last jammy release (version 5.15.0-70.77) where a commit 
from upstream
  removed the execute permission for a header file but then our scripts brought 
it back.

  [Fix]
  Andy proposed the following fix
  https://dpaste.com/6SJ8YR3BM
  Basically it checks if the permission was added or removed and uses either +x 
or -x.

  [Test plan]
  Easily tested with jammy-kvm, latest release where a rebase picked this commit
  "treewide: fix up files incorrectly marked executable" where 
`drivers/gpu/drm/vmwgfx/vmwgfx_msg_arm64.h` changed its permission from 755 to 
644 (removed execute).
  When debian packages are prepared, you'll notice the file has changed its 
permission back to 755.
  With the fix, it should be the same.

  [Regression potential]
  Low, it is a small fix. Scripts will still have execute permission.

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


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

[Kernel-packages] [Bug 2013209] Re: expoline.o is packaged unconditionally for s390x

This bug is awaiting verification that the linux-aws/5.19.0-1027.28
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-kinetic' to 'verification-done-kinetic'. If the
problem still exists, change the tag 'verification-needed-kinetic' to
'verification-failed-kinetic'.

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-kinetic-linux-aws

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

Title:
  expoline.o is packaged unconditionally for s390x

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.15 package in Ubuntu:
  New
Status in linux-hwe-5.15 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  https://bugs.launchpad.net/bugs/1639924 enabled CONFIG_EXPOLINE_EXTERN
  for s390x in Jammy. While this works as expected on Jammy, it won't
  work on some derivatives of it: for example focal:hwe-5.15. On Focal,
  this config can't be enabled due to the GCC version it comes with.
  CONFIG_EXPOLINE_EXTERN requires >= 110200 while Focal comes with
  90400.

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


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

[Kernel-packages] [Bug 2013088] Re: kernel: fix __clear_user() inline assembly constraints

This bug is awaiting verification that the linux-aws/5.19.0-1027.28
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-kinetic' to 'verification-done-kinetic'. If the
problem still exists, change the tag 'verification-needed-kinetic' to
'verification-failed-kinetic'.

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 removed: verification-done-kinetic
** Tags added: kernel-spammed-kinetic-linux-aws verification-needed-kinetic

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

Title:
  kernel: fix __clear_user() inline assembly constraints

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [ Impact ]

   * In case clear_user() crosses two pages and faults on the second page
 the kernel may write lowcore contents to the first page, instead of
     clearing it.

   * The __clear_user() inline assembly misses earlyclobber constraint
     modifiers. Depending on compiler and compiler options this may lead to
     incorrect code which copies kernel lowcore contents to user space 
 instead of clearing memory, in case clear_user() faults.

  [Fix]

   * For Kinetic and Jammy cherrypick of
 89aba4c26fae 89aba4c26fae4e459f755a18912845c348ee48f3
 "s390/uaccess: add missing earlyclobber annotations to __clear_user()"

   * For Focal and Bionic a backport of the above commit is needed:
 https://launchpadlibrarian.net/659551648/s390-uaccess.patch

  [ Test Plan ]

   * A test program in C is needed and used for testing.

   * The test will be done by IBM.

  [ Where problems could occur ]

   * The modification is limited to function 'long __clear_user'.

   * And there, just to one inline assembly constraints line.

   * This is usually difficult to trace.

   * A erroneous modification may lead to a wrong behavior in
     'long __clear_user',

   * and maybe returning a wrong size (in uaccess.c).

  [ Other Info ]

   * This affects all Ubuntu releases in service, down to 18.04.

   * Since we are close to 23.04 kernel freeze, I submit a patch request for
     23.04 separately, and submit the SRU request for the all other
     Ubuntu releases later.

  __

  Description:   kernel: fix __clear_user() inline assembly constraints

  Symptom:   In case clear_user() crosses two pages and faults on the
     second page the kernel may write lowcore contents to the
     first page, instead of clearing it.

  Problem:   The __clear_user() inline assembly misses earlyclobber
     constraint modifiers. Depending on compiler and compiler
     options this may lead to incorrect code which copies kernel
     lowcore contents to user space instead of clearing memory,
     in case clear_user() faults.

  Solution:  Add missing earlyclobber constraint modifiers.
  Preventive:yes

  Upstream-ID:   89aba4c26fae4e459f755a18912845c348ee48f3

  Affected Releases:
     18.04
     20.04
     22.04
     22.10
     23.04

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


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

[Kernel-packages] [Bug 2011616] Re: Connection timeout due to conntrack limits

This bug is awaiting verification that the linux-aws/5.19.0-1027.28
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-kinetic' to 'verification-done-kinetic'. If the
problem still exists, change the tag 'verification-needed-kinetic' to
'verification-failed-kinetic'.

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-kinetic-linux-aws

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

Title:
  Connection timeout due to conntrack limits

Status in linux package in Ubuntu:
  In Progress
Status in linux-gcp package in Ubuntu:
  New
Status in linux source package in Jammy:
  Fix Released
Status in linux-gcp source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-gcp source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  In Progress
Status in linux-gcp source package in Lunar:
  New

Bug description:
  Customers of GKE 1.25 and 1.26 are affected by the conntrack
  performance issue that causes random connection timeouts. The fix has
  been committed to to the upstream's net git repo and to prodkernel and
  needs to be backported to Ubuntu versions with kernel 5.15.

  https://partnerissuetracker.corp.google.com/issues/272090522

  Fix:

  
https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git/commit/?id=c77737b736ceb50fdf150434347dbd81ec76dbb1

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


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

[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)

This bug is awaiting verification that the linux-aws/5.19.0-1027.28
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-kinetic' to 'verification-done-kinetic'. If the
problem still exists, change the tag 'verification-needed-kinetic' to
'verification-failed-kinetic'.

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-kinetic-linux-aws

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

Title:
  No HDMI audio under 5.19.0-35 & -37 (regression from -32)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Invalid
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  For amdgpu/i915, hdmi audio output device has disappeared.

  [Fix]
  The latest fix for the non-contiguous memalloc helper changed the
  allocation method for a non-IOMMU system to use only the fallback
  allocator.  This should have worked, but it caused a problem sometimes
  when too many non-contiguous pages are allocated that can't be treated
  by HD-audio controller.
  
  As a quirk workaround, go back to the original strategy: use
  dma_alloc_noncontiguous() at first, and apply the fallback only when
  it fails, but only for non-IOMMU case

  [Test Case]
  1. boot with kernel applied the patches.
  2. check the cards in /proc/asound/cards.
 Get the hdmi cards.

   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xe232 irq 137
   1 [HDMI ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xe226 irq 134

  [Where problems could occur]
  Low, this is just workaround and may have a better solution in the future.

  [Misc]
  All patches has been landed on OEM-6.1 and lunar.

  ~~
  CLARIFICATION: Just to avoid any confusion for those coming to this bug 
report; the "Jammy: invalid" status above does *not* mean that this bug doesn't 
affect jammy -- it does, and the kernel team is aware of this. All it reflects 
is that the fix has to go into the kinetic kernel package which will then flow 
into the kernel-hwe package implicitly.

  Currently known affected cards:

  * HD 7700 (comment 8)
  * R9 290 (comment 21)
  * RX 550 (LP: #2012141, and comment 27)
  * RX 570 (mine)
  * RX 580 (LP: #2009276, and comment 28)
  * WX 3200 (comment 29)
  * RX 6600 (LP: #2009542)
  * RX 6700 (LP: #2009275)

  [ Original Description ]

  After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of
  the kernel, I found my HDMI audio output device had disappeared.
  Reverting to the -32 release caused it to appear again (hence why I'm
  filing the bug against the kernel rather than pulseaudio). I'm
  attaching the dmesg output from immediately after booting each kernel,
  but after a bit of trimming and diffing I *think* the following lines
  are the salient ones:

  input: HDA ATI HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12
  input: HDA ATI HDMI HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13
  input: HDA ATI HDMI HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14
  input: HDA ATI HDMI HDMI/DP,pcm=9 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15
  input: HDA ATI HDMI HDMI/DP,pcm=10 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16
  input: HDA ATI HDMI HDMI/DP,pcm=11 as 
/devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17
  snd_hda_intel :2b:00.1: bound :2b:00.0 (ops 
amdgpu_dm_audio_component_bind_ops [amdgpu])

  These lines appear in the dmesg of the -32 kernel, but not in the -35
  kernel's log. Meanwhile, the following lines appear in the -35
  kernel's log but not in the -32:

  hdaudio hdaudioC0D0: no AFG or MFG node found
  snd_hda_intel :2b:00.1: no codecs initialized

  I'll also attach the output of "pactl list" under each kernel (this
  shows the HDMI audio sink showing up under -32, but not -35) just in
  case that helps shed any light on things.

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


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

[Kernel-packages] [Bug 2006453] Re: Fix selftests/ftracetests/Meta-selftests

This bug is awaiting verification that the linux-aws/5.19.0-1027.28
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-kinetic' to 'verification-done-kinetic'. If the
problem still exists, change the tag 'verification-needed-kinetic' to
'verification-failed-kinetic'.

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-kinetic-linux-aws

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

Title:
  Fix selftests/ftracetests/Meta-selftests

Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem-6.1 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-6.1 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [SRU Justification]

  == Impact ==
  This subtest checks for bashisms in the test scripts of ftracetests. A recent 
stable change added such a case. This is harmless but causes the Meta-selftests 
to fail. The offending commit is "selftests/ftrace: event_triggers: wait longer 
for test_event_enable" which adds:
  +   if [ "$e" == $val ]; then

  == Fix ==
  Replace the test with
  +   if [ "$e" = $val ]; then

  == Testcase ==
  Running the kernel selftests/ftracetest (done in ADT and RT) should no longer 
show "Meta-selftests" as FAILed.

  == Regression Potential ==
  This affects only the selftest suite and only ftrace subtests. Any change 
would only be observable there.

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


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

[Kernel-packages] [Bug 2004262] Re: Intel E810 NICs driver in causing hangs when booting and bonds configured

This bug is awaiting verification that the linux-aws/5.19.0-1027.28
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-kinetic' to 'verification-done-kinetic'. If the
problem still exists, change the tag 'verification-needed-kinetic' to
'verification-failed-kinetic'.

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-kinetic-linux-aws

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

Title:
  Intel E810 NICs driver in causing hangs when booting and bonds
  configured

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Confirmed

Bug description:
  [Impact]
* Intel E810-family NICs cause system hangs when booting with bonding 
enabled
* This happens due to the driver unplugging auxiliary devices
* The unplug event happens under RTNL lock context, which causes a deadlock 
where the RDMA driver waits for the RNL lock to complete removal

  [Test Plan]
* Users have reported that after setting up bonding on switch and server 
side, the system will hang when starting network services

  [Fix]
* The upstream patch defers unplugging/re-plugging of the auxiliary device, 
so that it's not performed under the RTNL lock context.
* Fix was introduced by commit:
248401cb2c46 ice: avoid bonding causing auxiliary plug/unplug under 
RTNL lock

  [Regression Potential]
* Regressions would manifest in devices that support RDMA functionality and
  have been added to a bond
* We should look out for auxiliary devices that haven't been properly
  unplugged, or that cause further issues with
  ice_plug_aux_dev()/ice_unplug_aux_dev()

  
  [Original Description]
  jammy 22.04.1
  linux-image-generic 5.15.0-58-generic
  Intel E810-XXV Dual Port NICs in Dell PowerEdge 650

  - 5.15 in jammy -> reproducible
  - 5.19 in hwe-edge -> reproducible
  - 6.2.rc6 in the mainline build -> works
  - Intel's ice driver 1.10.1.2.2 -> works

  After beonding is enabled on switch and server side, the system will
  hang at initialing ubuntu.  The kernel loads but around starting the
  Network Services the system can hang for sometimes 5 minutes, and in
  other cases, indefinitely.

  The message of:

  echo 0 > /proc/sys/kernel/hung_task_timeout_sec”  systemd-resolve
  blocked for more than 120 seconds

  appears, and eventually the Network services just attempts to start
  and never does.  This is with or without DHCP enabled.

  Tried this same setup with the hwe-22.04, hwe-20.04, hwe-22.04-ege and
  linux-oem kernels and all exhibit the same failure.

  To work around this. installing the Intel 'ice' driver of version
  1.10.1.2.2 works.  The system doesn't even remotely hang at startup
  and all networking functions remain working (ping, DNS, general
  accessibility).

  The driver can be found at 
https://downloadmirror.intel.com/763930/ice-1.10.1.2.2.tar.gz
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 31 13:08 seq
   crw-rw 1 root audio 116, 33 Jan 31 13:08 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  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
  CasperMD5json:
   {
     "result": "skip"
   }DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-01-27 (3 days ago)InstallationMedia: 
Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge R650
  Package: linux (not installed)
  PciMultimedia:

  ProcFB: 0 mgag200drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=668aab7c-abe9-434b-a810-acc6eab76cbc ro fsck.mode=skip
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'Tags:  jammy 
uec-images
  Uname: Linux 5.15.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 09/14/2022
  dmi.bios.release: 1.8

[Kernel-packages] [Bug 1988346] Re: cm32181 module error blocking suspend

This bug is awaiting verification that the linux-aws/5.19.0-1027.28
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-kinetic' to 'verification-done-kinetic'. If the
problem still exists, change the tag 'verification-needed-kinetic' to
'verification-failed-kinetic'.

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-kinetic-linux-aws

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

Title:
  cm32181 module error blocking suspend

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  After updating to 22.04.1 (from 20.04) suspend gets interrupted and
  the system returns after a few seconds.

  journalctl output
  ```
  Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep)
  Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds
  Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... 
(elapsed 0.002 seconds) done.
  Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled.
  Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... 
(elapsed 3.894 seconds) done.
  Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use 
no_console_suspend to debug)
  Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI 
cache
  Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): 
acpi_subsys_suspend+0x0/0x60 returns -121
  Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to 
suspend: error -121
  Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk
  Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or 
early wake event detected
  Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk
  Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated 
(0x6)
  Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled.
  Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done.
  Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake 
event 0x0
  Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit
  Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle)
  Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds
  Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... 
(elapsed 0.005 seconds) done.
  Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled.
  Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... 
  Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM 
TrackPoint firmware: 0x0e, buttons: 3/3
  Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as 
/devices/rmi4-00/rmi4-00.fn03/serio2/input/input196
  Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done.
  Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use 
no_console_suspend to debug)
  Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI 
cache
  Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): 
acpi_subsys_suspend+0x0/0x60 returns -121
  Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to 
suspend: error -121
  Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk
  Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or 
early wake event detected
  Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk
  Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated 
(0x6)
  Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled.
  Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done.
  Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit
  Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: 
Deactivated successfully.
  Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake 
event 0x0
  Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to 
sleep. System resumed again: Remote I/O error
  Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda:
  Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]:  setting Advanced Power 
Management level to 0xfe (254)
  Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]:  APM_level= 254
  Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]:   
[1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 
uid=0 result="success"
  Aug 31 19:59:44 nmurphy-laptop systemd[1]: s

[Kernel-packages] [Bug 1937133] Re: devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute (KeyError: 'flavour')

This bug is awaiting verification that the linux-aws/5.19.0-1027.28
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-kinetic' to 'verification-done-kinetic'. If the
problem still exists, change the tag 'verification-needed-kinetic' to
'verification-failed-kinetic'.

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-kinetic-linux-aws

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

Title:
  devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute
  (KeyError: 'flavour')

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Hirsute:
  Won't Fix
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  On s390x LPAR instances, this test will fail with:
  #   File "linux/tools/testing/selftests/net/devlink_port_split.py", line 
64, in get_if_names
  # if ports[port]['flavour'] == 'physical':
  # KeyError: 'flavour'
not ok 1 selftests: net: devlink_port_split.py # exit=1

  This is because the mlx4 driver in use on this instance does not set
  attributes, therefore `devlink -j port show` command output does not
  contain this "flavour" key.

  [Fix]
  * 3de66d08d3 selftests: net: devlink_port_split.py: skip test if no
suitable device available

  This patch can be cherry-picked into our J/K/L kernels.

  [Test]
  Run the patched devlink_port_split.py on s390x LPAR, and it won't
  fail with # KeyError: 'flavour' but marked as SKIP instead.

  [Where problems could occur]
  If this change is incorrect, it may affect the test result, however it's
  limited to testing tools, no actual impact to kernel functions.


  [Original Bug Report]
  Failing on hirsute/linux 5.11.0-26.28  host s2lp4

  Not a regression as this is also failing on 5.11.0-24.25

  17:16:32 DEBUG| [stdout] # selftests: net: devlink_port_split.py
  17:16:32 DEBUG| [stdout] # Traceback (most recent call last):
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 283, in 
  17:16:32 DEBUG| [stdout] # main()
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 256, in main
  17:16:32 DEBUG| [stdout] # ports = devlink_ports(dev)
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 70, in __init__
  17:16:32 DEBUG| [stdout] # self.if_names = devlink_ports.get_if_names(dev)
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 64, in get_if_names
  17:16:32 DEBUG| [stdout] # if ports[port]['flavour'] == 'physical':
  17:16:32 DEBUG| [stdout] # KeyError: 'flavour'
  17:16:32 DEBUG| [stdout] not ok 44 selftests: net: devlink_port_split.py # 
exit=1

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


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

[Kernel-packages] [Bug 2019869] Re: nvidia-dkms-390: better support for kernel 6.2

Wrong debdiff, here's a new one cleaned up properly, ignore comment #5.

** Patch added: "nvidia-dkms-390-lunar-better-support-for-linux-6.2-v2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019869/+attachment/5675615/+files/nvidia-dkms-390-lunar-better-support-for-linux-6.2-v2.debdiff

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

Title:
  nvidia-dkms-390: better support for kernel 6.2

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-390 source package in Lunar:
  Confirmed
Status in nvidia-graphics-drivers-390 source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  Instead of disabling acpi support completely with nvidia-dkms-390, we
  should try instead to see if it's possible to support it somehow.

  [Fix]

  This patch looks promising (even if it says huge hack in the comments...):
  
https://gitlab.com/herecura/packages/nvidia-390xx-dkms/-/blob/780a3c8b159f24c14e6c1cb35fd747338aefea39/kernel-6.2.patch

  Apply this patch and drop any 6.0 and 6.2 related patches.

  [Regression potential]

  With this patch nvidia-dkms-390 should build against 6.2 kernels
  without disabling any feature, but users of this driver may experience
  kernel bugs / crashes. However, the nvidia 390 driver is unmaintained
  so we should start to consider phasing it out.

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


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

[Kernel-packages] [Bug 2019869] Re: nvidia-dkms-390: better support for kernel 6.2

And here's the debdiff for jammy. Same fix.

** Patch added: "nvidia-dkms-390-jammy-better-support-for-linux-6.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019869/+attachment/5675616/+files/nvidia-dkms-390-jammy-better-support-for-linux-6.2.debdiff

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

Title:
  nvidia-dkms-390: better support for kernel 6.2

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-390 source package in Lunar:
  Confirmed
Status in nvidia-graphics-drivers-390 source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  Instead of disabling acpi support completely with nvidia-dkms-390, we
  should try instead to see if it's possible to support it somehow.

  [Fix]

  This patch looks promising (even if it says huge hack in the comments...):
  
https://gitlab.com/herecura/packages/nvidia-390xx-dkms/-/blob/780a3c8b159f24c14e6c1cb35fd747338aefea39/kernel-6.2.patch

  Apply this patch and drop any 6.0 and 6.2 related patches.

  [Regression potential]

  With this patch nvidia-dkms-390 should build against 6.2 kernels
  without disabling any feature, but users of this driver may experience
  kernel bugs / crashes. However, the nvidia 390 driver is unmaintained
  so we should start to consider phasing it out.

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


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

[Kernel-packages] [Bug 2020685] Re: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics

2023-05-25 Thread Timo Aaltonen

6.0 is done at this point

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
   Status: In Progress => Won't Fix

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

Title:
  System either hang with black screen or rebooted on entering suspend
  on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.0 source package in Mantic:
  Invalid
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  To reproduce:

  ```
  $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto
  # or
  $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30
  ```

  Proposed fixes from AMD:
  * 
https://github.com/torvalds/linux/commit/5591a051b86be170a84943698ab140342602ff7b
  * 
https://github.com/torvalds/linux/commit/d5aa417808cf14c052ca042920b3c6b9f1dc6aa4

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


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

[Kernel-packages] [Bug 2020783] [NEW] Lunar update: v6.3.4 upstream stable release

Public bug reported:


SRU Justification

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

   v6.3.4 upstream stable release
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

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

Title:
  Lunar update: v6.3.4 upstream stable release

Status in linux-raspi package in Ubuntu:
  Confirmed
Status in linux-raspi source package in Lunar:
  New

Bug description:
  
  SRU Justification

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

 v6.3.4 upstream stable release
 from git://git.kernel.org/

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


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

[Kernel-packages] [Bug 2020781] [NEW] Lunar update: v6.3.3 upstream stable release

Public bug reported:


SRU Justification

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

   v6.3.3 upstream stable release
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

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

Title:
  Lunar update: v6.3.3 upstream stable release

Status in linux-raspi package in Ubuntu:
  Confirmed
Status in linux-raspi source package in Lunar:
  New

Bug description:
  
  SRU Justification

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

 v6.3.3 upstream stable release
 from git://git.kernel.org/

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


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

[Kernel-packages] [Bug 2020779] [NEW] Lunar update: v6.3.1 upstream stable release

Public bug reported:


SRU Justification

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

   v6.3.1 upstream stable release
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

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

Title:
  Lunar update: v6.3.1 upstream stable release

Status in linux-raspi package in Ubuntu:
  Confirmed
Status in linux-raspi source package in Lunar:
  New

Bug description:
  
  SRU Justification

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

 v6.3.1 upstream stable release
 from git://git.kernel.org/

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


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

[Kernel-packages] [Bug 2020780] [NEW] Lunar update: v6.3.2 upstream stable release

Public bug reported:


SRU Justification

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

   v6.3.2 upstream stable release
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

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

Title:
  Lunar update: v6.3.2 upstream stable release

Status in linux-raspi package in Ubuntu:
  Confirmed
Status in linux-raspi source package in Lunar:
  New

Bug description:
  
  SRU Justification

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

 v6.3.2 upstream stable release
 from git://git.kernel.org/

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


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

[Kernel-packages] [Bug 2015972] Re: Dell: Enable speaker mute hotkey LED indicator

2023-05-25 Thread Andreas Hasenack

Thank you, so we have verification on the oem kernels, and the proposed
kernels, for jammy, kinetic, and lunar.

Did you try alsa-ucm-conf with the currently released kernels for those
ubuntu releases? I wouldn't expect the LED to work, if it requires a
newer kernel, but just to check if nothing breaks with the currently
released kernels and this new alsa-ucm-conf package.

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

Title:
  Dell: Enable speaker mute hotkey LED indicator

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in alsa-ucm-conf source package in Kinetic:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in alsa-ucm-conf source package in Lunar:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Feature Description]
  When users press the speaker mute hotkey and the speaker is muted, 
  the speaker mute LED indicator will light up. 
  When the speaker is not muted, 
  the speaker mute LED indicator will light out.

  [Test Case]
  1. run G16 with target kernel.
  2. press the mute hotkey
  3. check if speaker mute led can be switched.

  [Where problems could occur]
  Low, just register a speaker mute led control for dell-laptop.

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


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

[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM

2023-05-25 Thread Giuliano Lotta

@kolbj...@blix-dahle.no 
I see your have a ID 0408:4033 Quanta Computer, Inc. ACER HD, like @samer has.

Which ubuntu version, and kernel version are you using ?
Can you provide Samer with some better instructions on how to make it work ?

BR

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

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing',
  USB 0408:4035.

  The camera is reported to have problems by many users:  
  https://linux-hardware.org/?id=usb:0408-4035
  The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera 
is “recongized” but fails installation.

  My console commands report similar info to other users: 
  
https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58

  
  PROPOSED SOLUTION 
  I got in contact with laurent.pinch...@ideasonboard.com   and with 
riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And  
me...@vger.kernel.org mailinglist.

  Laurent proposed me a fix and I modified the 5,15 uvc_driver.c
  version, and loaded it on github

  https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-
  Facing-0x0408-0x4035-/blob/main/uvc_driver.c

  I offered to test the fix, so I tried to compile the module with the
  new source.

  COMPILING PROBLEMS
  I’m running **Ubuntu 22.04.1 LTS, with kernel 
  giuliano@Astra2A:/usr/src$ cat /proc/version_signature
  Ubuntu 5.15.0-56.62-generic 5.15.64

  BUT  the linux-source that I found installed seems to be different
  tgiuliano@Astra2A:/usr/src$ ls -al linux-so*
  lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> 
linux-source-5.15.0/linux-source-5.15.0.tar.bz2

  I expanded  the tar file, configured the IDE and compiled without error  any 
errors… 
  I manually copied the uvcvideo.ko in 
  /lib/modules/5.15.0-56-
  sudo cp…...

  then tryed to intall the new uvcvideo.ko module
  sudo rmmod uvcvideo && sudo modprobe uvcvideo

  BUT… IT FAILS
  giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo
  modprobe: ERROR: could not insert 'uvcvideo': Exec format error

  and dmesg shows
  [25961.151982] usbcore: registered new interface driver uvcvideo
  [26323.125534] usbcore: deregistering interface driver uvcvideo
  [26323.189294] uvcvideo: disagrees about version of symbol module_layout


  These are the TWO modinfo from the old and new uvcvideo modules
  https://pastebin.com/tSj8Exm6
  Basically
  OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions 
  NEW module: vermagic: 5.15.64 SMP mod_unload modversions


  -kindly ASK

  HOW can FORCE the uvcdriver.c to match mi kernel version ?
  Have I got OTHER ways to make the kernel module I’m compiling, match my 
running system ?

  I would like to test the module so to confirm the patch and let it
  enter the kernel main stream...

  
  BR
  Giuliano

  PS
  btw…. to allow Eclipse to compile the kernel, I had to pass this commands
  scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_TRUSTED_KEYS

  hope that this does not affect the module layout & checking
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giuliano   2142 F pulseaudio
   /dev/snd/pcmC1D0p:   giuliano   2142 F...m pulseaudio
   /dev/snd/controlC0:  giuliano   2142 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-03 (66 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Nitro AN517-55
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-57-generic N/A
   linux-backports-modules-5.15.0-57-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  Tags:  jammy
  Uname: Linux 5.15.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/20/2022
  dmi.bios.release: 1.6
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Boa

[Kernel-packages] [Bug 2020413] Re: fix typo in config-checks invocation

2023-05-25 Thread Andrei Gherzan

Because this was not included in the 20230515 cycle for Jammy, any
derivative of it using the old configs+annotations model will hit a
build failure and will need to cherry-pick the fix from jammy:linux:

https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master-
next&id=bccfa4179c2411415214e580a917a0b25f20d882

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

Title:
  fix typo in config-checks invocation

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

Bug description:
  [Impact]

  After migrating to the new annotations-only model in jammy we
  introduced a typo in debian/rules.d/4-checks.mk, that is triggered if
  we opt to not migrate to the new model and still use the old
  configs+annotations.

  [Test case]

  With debian./config/config.common.ubuntu present run the
  following command:

   $ fakeroot debian/rules clean updateconfigs

  [Fix]

  Replace @perl -> perl.

  [Regression potential]

  It's a trivial typo fix. Regressions can be introduced only if we are
  still using the old configs+annotations model.

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


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

[Kernel-packages] [Bug 1861633] Re: Rx vega m gl undervolt and overclock pp_od_clk_voltage values cannot be changed using echo

2023-05-25 Thread Bug Watch Updater

** Changed in: linux
   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/1861633

Title:
  Rx vega m gl undervolt and overclock pp_od_clk_voltage values cannot
  be changed using echo

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  New

Bug description:
  GPU=Rx vega m gl
  Release=Focal, 20.04 (development)
  xserver-xorg-video-amdgpu version=19.1.0-1 (active development)

  /sys/class/drm/card1/device/pp_od_clk_voltage cannot be change beyond
  the parameters stated at the bottom of this file within the title
  OD_RANGE, as follows:

  OD_RANGE:
  SCLK: 225MHz   1011MHz
  MCLK: 300MHz700MHz
  VDDC: 750mV 750mV

  The parameters in OD_RANGE are too constrictive and do not allow
  practicable overclocking/undervolting. Please could these values be
  changed to the following?:

  OD_RANGE:
  SCLK: 225MHz   1500MHz
  MCLK: 300MHz850MHz
  VDDC: 300mV 1500mV

  This bug was also found here;
  https://gitlab.freedesktop.org/drm/amd/issues/574

  The voltages and clock speeds cannot be amended above 1011Mhz, the
  HBM2 cannot exceed 700MHz and all voltages can only equal 750mV.

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


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

[Kernel-packages] [Bug 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G

2023-05-25 Thread Bug Watch Updater

** Changed in: linux
   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/1848900

Title:
  [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Fix Released

Bug description:
  Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and
  55-75 Hz monitor.

  Booting Xubuntu 19.10 live iso with safe graphics options did give a
  stable desktop display, but

  xubuntu@xubuntu:~$ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
  default connected 1920x1080+0+0 0mm x 0mm
 1920x1080 77.00* 
  xubuntu@xubuntu:~$ 

  The monitor is only supposed to have a maximum vertical refresh rate
  of 75 Hz. Xrandr reports 77 Hz as the only choice.  The monitor
  reports 60 Hz, not that I trust the monitor.

  Swapping monitors and running many reboots the situation seems to
  be...

  Old versions of Ubuntu (Bionic and Dingo) can handle the hardware.
  Standard boot sometimes gives a blank screen.  
  Standard boot sometimes gives a badly pixelated display 
  (Ctl-Alt-F6, Ctl-Alt-F7 temporarily improves it).  
  Connecting a 144 Hz monitor convinces something (the firmware?) 
  that fast refreshes are OK on a slow monitor, or at least it fails to 
  reread and abide by the slow monitor's limitations when swapping back.
  Something, I don't know what, convinces the computer to run the display 
  at 60 Hz, sometimes. 

  The motherboard has three video ports; DP, HDMI and VGA (using an onboard 
  DP? to VGA converter chip).  The fast monitor has DP, HDMI and VGA ports, 
  but I only experimented with the DP connection.  The slow monitor has VGA and 
  DVI-D ports.  I experimented with VGA to VGA and HDMI via a passive adapter 
  to DVI.  When running in the badly pixelated mode xorg seems to think that 
  the VGA port is "DP-1".

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.427
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Oct 20 00:17:34 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash nomodeset ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.40
  dmi.board.name: B450 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd07/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Oct 19 23:52:52 2019
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191

[Kernel-packages] [Bug 2020413] Re: fix typo in config-checks invocation

2023-05-25 Thread Andrei Gherzan

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

** Changed in: linux-kvm (Ubuntu Jammy)
 Assignee: (unassigned) => Andrei Gherzan (agherzan)

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

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

Title:
  fix typo in config-checks invocation

Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Jammy:
  Incomplete
Status in linux-kvm source package in Jammy:
  Confirmed

Bug description:
  [Impact]

  After migrating to the new annotations-only model in jammy we
  introduced a typo in debian/rules.d/4-checks.mk, that is triggered if
  we opt to not migrate to the new model and still use the old
  configs+annotations.

  [Test case]

  With debian./config/config.common.ubuntu present run the
  following command:

   $ fakeroot debian/rules clean updateconfigs

  [Fix]

  Replace @perl -> perl.

  [Regression potential]

  It's a trivial typo fix. Regressions can be introduced only if we are
  still using the old configs+annotations model.

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


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

2023-05-25 Thread Ubuntu SRU Bot

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

lttng-modules/2.13.8-1~ubuntu22.10.0 (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/kinetic/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 2020794] [NEW] Black screen doesn't wake up in wayland with Nvidia

2023-05-25 Thread Soumyadeep Ghosh

Public bug reported:

In the wayland session, if the deviced gets the screen black for once,
it doesn't comeup. And I have bring it up either via pressing the
physical suspend button(which also sometimes doesn't work), or via
forcefully restarting it down.

The package I've reported the bug with is a randomly chosen nvidia
package. I don't know what's the real reason. But. before this I used a
custom kernel in Ubuntu 22.10, this issue happened very less frequently
there.

https://kernel.ubuntu.com/~kernel-ppa

I used the kernel from here.
My Graphics Card: Nvidia RTX 3050

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: nvidia-kernel-common-525 525.105.17-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu May 25 20:37:56 2023
InstallationDate: Installed on 2023-02-02 (112 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
SourcePackage: nvidia-graphics-drivers-525
UpgradeStatus: Upgraded to lunar on 2023-04-21 (33 days ago)

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


** Tags: amd64 apport-bug lunar

** Description changed:

  In the wayland session, if the deviced gets the screen black for once,
  it doesn't comeup. And I have bring it up either via pressing the
  physical suspend button(which also sometimes doesn't work), or via
  forcefully restarting it down.
  
  The package I've reported the bug with is a randomly chosen nvidia
  package. I don't know what's the real reason. But. before this I used a
  custom kernel in Ubuntu 22.10, this issue happened very less frequently
  there.
  
  https://kernel.ubuntu.com/~kernel-ppa
  
  I used the kernel from here.
+ My Graphics Card: Nvidia RTX 3050
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: nvidia-kernel-common-525 525.105.17-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 25 20:37:56 2023
  InstallationDate: Installed on 2023-02-02 (112 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: nvidia-graphics-drivers-525
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (33 days ago)

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

Title:
  Black screen doesn't wake up in wayland with Nvidia

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

Bug description:
  In the wayland session, if the deviced gets the screen black for once,
  it doesn't comeup. And I have bring it up either via pressing the
  physical suspend button(which also sometimes doesn't work), or via
  forcefully restarting it down.

  The package I've reported the bug with is a randomly chosen nvidia
  package. I don't know what's the real reason. But. before this I used
  a custom kernel in Ubuntu 22.10, this issue happened very less
  frequently there.

  https://kernel.ubuntu.com/~kernel-ppa

  I used the kernel from here.
  My Graphics Card: Nvidia RTX 3050

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: nvidia-kernel-common-525 525.105.17-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 25 20:37:56 2023
  InstallationDate: Installed on 2023-02-02 (112 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: nvidia-graphics-drivers-525
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (33 days ago)

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


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

[Kernel-packages] [Bug 2018593] Re: Azure: Enable MANA Jumbo Frame Support reprise

2023-05-25 Thread Tim Gardner

** Changed in: linux-azure (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Changed in: linux-azure (Ubuntu Kinetic)
   Status: In Progress => Fix Committed

** Changed in: linux-azure (Ubuntu Lunar)
   Status: In Progress => Fix Committed

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

Title:
  Azure: Enable MANA Jumbo Frame Support reprise

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Jammy:
  Fix Committed
Status in linux-azure source package in Kinetic:
  Fix Committed
Status in linux-azure source package in Lunar:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  The MANA driver is missing 2 commits in support of jumbo frames.

  [Fix]

  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/ethernet/microsoft/mana?id=df18f2da302f169e1a29098c6ca3b474f1b0269e

  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/ethernet/microsoft/mana?id=5c74064f43c291d9add2b436a2d70205b71a7cc7

  [Test Plan]

  Microsoft tested

  [Regression Potential]

  Regular frames could be discarded.

  [Other Info]

  SF: #00358566

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


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

[Kernel-packages] [Bug 2020413] Re: fix typo in config-checks invocation

2023-05-25 Thread Andrei Gherzan

This is another required fix here:
https://lists.ubuntu.com/archives/kernel-team/2023-May/139767.html

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

Title:
  fix typo in config-checks invocation

Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Jammy:
  Incomplete
Status in linux-kvm source package in Jammy:
  Confirmed

Bug description:
  [Impact]

  After migrating to the new annotations-only model in jammy we
  introduced a typo in debian/rules.d/4-checks.mk, that is triggered if
  we opt to not migrate to the new model and still use the old
  configs+annotations.

  [Test case]

  With debian./config/config.common.ubuntu present run the
  following command:

   $ fakeroot debian/rules clean updateconfigs

  [Fix]

  Replace @perl -> perl.

  [Regression potential]

  It's a trivial typo fix. Regressions can be introduced only if we are
  still using the old configs+annotations model.

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


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

[Kernel-packages] [Bug 2019009] Re: Azure: Limit Hyperv error messages

2023-05-25 Thread Tim Gardner

** Changed in: linux-azure (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Changed in: linux-azure (Ubuntu Kinetic)
   Status: In Progress => Fix Committed

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

Title:
  Azure: Limit Hyperv error messages

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Jammy:
  Fix Committed
Status in linux-azure source package in Kinetic:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  Hyperv can emit copious numbers of error messages "Unable to send
  packet via vmbus".

  [Test Plan]

  Microsoft tested, patches are upstream.

  [Regression Potential]

  Commit 19b5e6659eaf537ebeac90ae30c7df0296fe5ab9 ('drm/hyperv: Don't
  overwrite dirt_needed value set by host') fixes a race condition that
  could have unforeseen side effects.

  [Other Info]

  SF: #00359893

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


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

[Kernel-packages] [Bug 2019869] Re: nvidia-dkms-390: better support for kernel 6.2

2023-05-25 Thread Alberto Milone

** Changed in: nvidia-graphics-drivers-390 (Ubuntu Mantic)
 Assignee: (unassigned) => Andrea Righi (arighi)

** Changed in: nvidia-graphics-drivers-390 (Ubuntu Lunar)
 Assignee: (unassigned) => Andrea Righi (arighi)

** Changed in: nvidia-graphics-drivers-390 (Ubuntu Lunar)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-390 (Ubuntu Mantic)
   Importance: Undecided => Medium

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

Title:
  nvidia-dkms-390: better support for kernel 6.2

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-390 source package in Lunar:
  Confirmed
Status in nvidia-graphics-drivers-390 source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  Instead of disabling acpi support completely with nvidia-dkms-390, we
  should try instead to see if it's possible to support it somehow.

  [Fix]

  This patch looks promising (even if it says huge hack in the comments...):
  
https://gitlab.com/herecura/packages/nvidia-390xx-dkms/-/blob/780a3c8b159f24c14e6c1cb35fd747338aefea39/kernel-6.2.patch

  Apply this patch and drop any 6.0 and 6.2 related patches.

  [Regression potential]

  With this patch nvidia-dkms-390 should build against 6.2 kernels
  without disabling any feature, but users of this driver may experience
  kernel bugs / crashes. However, the nvidia 390 driver is unmaintained
  so we should start to consider phasing it out.

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


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

[Kernel-packages] [Bug 2018716] Re: zfs-dkms: support linux >= 6.3

2023-05-25 Thread Dimitri John Ledkov

** Tags removed: block-proposed-mantic

** Changed in: zfs-linux (Ubuntu Mantic)
   Status: In Progress => Fix Committed

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

Title:
  zfs-dkms: support linux >= 6.3

Status in zfs-linux package in Ubuntu:
  Fix Committed
Status in zfs-linux source package in Mantic:
  Fix Committed

Bug description:
  [Impact]

  The current version of zfs-dkms available in lunar fails to build with
  kernels >= 6.3.

  [Test case]

  $ apt install zfs-dkms

  [Fix]

  Resync with zfs version in Debian (2.1.1) and apply the usual Ubuntu
  specific changes.

  [Regression potential]

  We may experience zfs regressions due to a new major version,
  especially on zfs volumes / filesystems created with the previous
  versions. However this goes in pair with the new major kernel version
  and we need to upgrade the version of zfs to properly support the new
  kernels >= 6.3.

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


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

[Kernel-packages] [Bug 2020656] Re: system freeze (cpu fan goes high)

2023-05-25 Thread __JEAN_FRANCOIS__

Go the message below, my vscode window (through ssh) is freezed but the
system is still running

# uptime -p
up 6 hours, 23 minutes

extract from journalctl -f

```
mai 25 18:51:32 jf-ThinkPad-P14s kernel: BUG: kernel NULL pointer dereference, 
address: 0008
mai 25 18:51:32 jf-ThinkPad-P14s kernel: #PF: supervisor read access in kernel 
mode
mai 25 18:51:32 jf-ThinkPad-P14s kernel: #PF: error_code(0x) - not-present 
page
mai 25 18:51:32 jf-ThinkPad-P14s kernel: PGD 0 P4D 0
mai 25 18:51:32 jf-ThinkPad-P14s kernel: Oops:  [#1] PREEMPT SMP NOPTI
mai 25 18:51:32 jf-ThinkPad-P14s kernel: CPU: 5 PID: 24230 Comm: 
ThreadPoolForeg Not tainted 5.19.0-42-generic #43~22.04.1-Ubuntu
mai 25 18:51:32 jf-ThinkPad-P14s kernel: Hardware name: LENOVO 
21J5CTO1WW/21J5CTO1WW, BIOS R23ET65W (1.35 ) 03/21/2023
mai 25 18:51:32 jf-ThinkPad-P14s kernel: RIP: 
0010:syscall_exit_to_user_mode+0x0/0x50
mai 25 18:51:32 jf-ThinkPad-P14s kernel: Code: 1f 44 00 00 5d 31 c0 89 c2 89 c1 
89 c6 89 c7 c3 cc cc cc cc 66 0f 1f 44 00 00 eb 07 0f 00 2d c7 06 51 00 c3 cc 
cc cc cc 66 90 <55> 65 48 8b 04 25 c0 fb 01 00 48 89 e5 41 54 48 8b 70 08 49 89 
fc
mai 25 18:51:32 jf-ThinkPad-P14s kernel: RSP: 0018:a8e40b0a3e78 EFLAGS: 
00010246
mai 25 18:51:32 jf-ThinkPad-P14s kernel: RAX:  RBX: 
 RCX: 
mai 25 18:51:32 jf-ThinkPad-P14s kernel: RDX:  RSI: 
 RDI: a8e40b0a3f58
mai 25 18:51:32 jf-ThinkPad-P14s kernel: RBP: a8e40b0a3f48 R08: 
 R09: 
mai 25 18:51:32 jf-ThinkPad-P14s kernel: R10:  R11: 
 R12: a8e40b0a3f58
mai 25 18:51:32 jf-ThinkPad-P14s kernel: R13:  R14: 
 R15: 
mai 25 18:51:32 jf-ThinkPad-P14s kernel: FS:  7ff53f1bc640() 
GS:92c761f4() knlGS:
mai 25 18:51:32 jf-ThinkPad-P14s kernel: CS:  0010 DS:  ES:  CR0: 
80050033
mai 25 18:51:32 jf-ThinkPad-P14s kernel: CR2: 0008 CR3: 
00011c2b8000 CR4: 00750ee0
mai 25 18:51:32 jf-ThinkPad-P14s kernel: PKRU: 5558
mai 25 18:51:32 jf-ThinkPad-P14s kernel: Call Trace:
mai 25 18:51:32 jf-ThinkPad-P14s kernel:  
mai 25 18:51:32 jf-ThinkPad-P14s kernel:  ? do_syscall_64+0x69/0x90
mai 25 18:51:32 jf-ThinkPad-P14s kernel:  ? __x64_sys_futex+0x78/0x1f0
mai 25 18:51:32 jf-ThinkPad-P14s kernel:  ? __secure_computing+0x9b/0x110
mai 25 18:51:32 jf-ThinkPad-P14s kernel:  ? 
syscall_trace_enter.constprop.0+0xb5/0x1c0
mai 25 18:51:32 jf-ThinkPad-P14s kernel:  ? exit_to_user_mode_prepare+0x3b/0xd0
mai 25 18:51:32 jf-ThinkPad-P14s kernel:  ? syscall_exit_to_user_mode+0x2a/0x50
mai 25 18:51:32 jf-ThinkPad-P14s kernel:  ? do_syscall_64+0x69/0x90
mai 25 18:51:32 jf-ThinkPad-P14s kernel:  ? irqentry_exit+0x43/0x50
mai 25 18:51:32 jf-ThinkPad-P14s kernel:  ? exc_page_fault+0x92/0x1b0
mai 25 18:51:32 jf-ThinkPad-P14s kernel:  
entry_SYSCALL_64_after_hwframe+0x63/0xcd
mai 25 18:51:32 jf-ThinkPad-P14s kernel: RIP: 0033:0x7ff58b6913b7
mai 25 18:51:32 jf-ThinkPad-P14s kernel: Code: 81 00 00 00 b8 ca 00 00 00 0f 05 
c3 0f 1f 80 00 00 00 00 f3 0f 1e fa 40 80 f6 81 45 31 d2 ba 01 00 00 00 b8 ca 
00 00 00 0f 05  0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 8b 05 d5 7b 18 00 48 
89
mai 25 18:51:32 jf-ThinkPad-P14s kernel: RSP: 002b:7ff53f1bade8 EFLAGS: 
0246 ORIG_RAX: 00ca
mai 25 18:51:32 jf-ThinkPad-P14s kernel: RAX:  RBX: 
13cb031a161c RCX: 7ff58b6913b7
mai 25 18:51:32 jf-ThinkPad-P14s kernel: RDX: 0001 RSI: 
0081 RDI: 39240031c648
mai 25 18:51:32 jf-ThinkPad-P14s kernel: RBP: 7ff53f1bae70 R08: 
 R09: 
mai 25 18:51:32 jf-ThinkPad-P14s kernel: R10:  R11: 
0246 R12: 7ff53f1bb1b0
mai 25 18:51:32 jf-ThinkPad-P14s kernel: R13: 13cb0318 R14: 
39240031c648 R15: 13cb031a2de5
mai 25 18:51:32 jf-ThinkPad-P14s kernel:  
mai 25 18:51:32 jf-ThinkPad-P14s kernel: Modules linked in: snd_seq_dummy 
rfcomm qrtr_mhi cmac algif_hash algif_skcipher af_alg bnep snd_ctl_led 
snd_soc_acp6x_mach snd_acp6x_pdm_dma snd_soc_dmic snd_hda_codec_realtek 
snd_sof_amd_renoir snd_hda_codec_generic snd_sof_amd_acp snd_sof_pci snd_sof 
snd_sof_utils snd_hda_codec_hdmi qrtr snd_soc_core snd_hda_intel ath11k_pci 
snd_intel_dspcfg intel_rapl_msr snd_intel_sdw_acpi snd_compress 
intel_rapl_common ath11k edac_mce_amd uvcvideo ac97_bus snd_hda_codec 
snd_pcm_dmaengine videobuf2_vmalloc btusb snd_pci_ps videobuf2_memops 
snd_hda_core snd_acp_pci btrtl videobuf2_v4l2 qmi_helpers kvm_amd btbcm 
videobuf2_common binfmt_misc snd_pci_acp6x snd_hwdep btintel mac80211 kvm 
thinkpad_acpi videodev hid_magicmouse btmtk nvram snd_seq_midi think_lmi 
nls_iso8859_1 rapl serio_raw snd_pcm snd_seq_midi_event 
firmware_attributes_class wmi_bmof hid_multitouch mc joydev input_leds 
ledtrig_audio apple_mfi_fastcharge snd_rawmidi bluetooth snd_seq

Re: [Kernel-packages] [Bug 2015972] Re: Dell: Enable speaker mute hotkey LED indicator

2023-05-25 Thread koba

Yes, I tried alsa-ucm-conf on kernels w/ w/o patches.

On Thu, May 25, 2023, 9:46 PM Andreas Hasenack <2015...@bugs.launchpad.net>
wrote:

> Thank you, so we have verification on the oem kernels, and the proposed
> kernels, for jammy, kinetic, and lunar.
>
> Did you try alsa-ucm-conf with the currently released kernels for those
> ubuntu releases? I wouldn't expect the LED to work, if it requires a
> newer kernel, but just to check if nothing breaks with the currently
> released kernels and this new alsa-ucm-conf package.
>
> --
> You received this bug notification because you are a member of Canonical
> Hardware Enablement, which is subscribed to the bug report.
> https://bugs.launchpad.net/bugs/2015972
>
> Title:
>   Dell: Enable speaker mute hotkey LED indicator
>
> Status in HWE Next:
>   New
> Status in OEM Priority Project:
>   New
> Status in alsa-ucm-conf package in Ubuntu:
>   Fix Released
> Status in linux package in Ubuntu:
>   In Progress
> Status in linux-oem-6.1 package in Ubuntu:
>   Invalid
> Status in alsa-ucm-conf source package in Jammy:
>   Fix Committed
> Status in linux source package in Jammy:
>   Fix Committed
> Status in linux-oem-6.1 source package in Jammy:
>   Fix Released
> Status in alsa-ucm-conf source package in Kinetic:
>   Fix Committed
> Status in linux source package in Kinetic:
>   Fix Committed
> Status in linux-oem-6.1 source package in Kinetic:
>   Invalid
> Status in alsa-ucm-conf source package in Lunar:
>   Fix Committed
> Status in linux source package in Lunar:
>   Fix Committed
> Status in linux-oem-6.1 source package in Lunar:
>   Invalid
>
> Bug description:
>   [Feature Description]
>   When users press the speaker mute hotkey and the speaker is muted,
>   the speaker mute LED indicator will light up.
>   When the speaker is not muted,
>   the speaker mute LED indicator will light out.
>
>   [Test Case]
>   1. run G16 with target kernel.
>   2. press the mute hotkey
>   3. check if speaker mute led can be switched.
>
>   [Where problems could occur]
>   Low, just register a speaker mute led control for dell-laptop.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/hwe-next/+bug/2015972/+subscriptions
>
>

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

Title:
  Dell: Enable speaker mute hotkey LED indicator

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in alsa-ucm-conf source package in Jammy:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in alsa-ucm-conf source package in Kinetic:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in alsa-ucm-conf source package in Lunar:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Feature Description]
  When users press the speaker mute hotkey and the speaker is muted, 
  the speaker mute LED indicator will light up. 
  When the speaker is not muted, 
  the speaker mute LED indicator will light out.

  [Test Case]
  1. run G16 with target kernel.
  2. press the mute hotkey
  3. check if speaker mute led can be switched.

  [Where problems could occur]
  Low, just register a speaker mute led control for dell-laptop.

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


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

[Kernel-packages] [Bug 2015972] Re: Dell: Enable speaker mute hotkey LED indicator

This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu9

---
alsa-ucm-conf (1.2.6.3-1ubuntu9) lunar; urgency=medium

  * d/p/0006-sof-hda-dsp-Add-speaker-led-support.patch
 - Backport patch to fix speaker mute led (LP: #2015972)

 -- Koba Ko   Wed, 19 Apr 2023 09:50:30 +0800

** Changed in: alsa-ucm-conf (Ubuntu Lunar)
   Status: Fix Committed => Fix Released

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

Title:
  Dell: Enable speaker mute hotkey LED indicator

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in alsa-ucm-conf source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in alsa-ucm-conf source package in Kinetic:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in alsa-ucm-conf source package in Lunar:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Feature Description]
  When users press the speaker mute hotkey and the speaker is muted, 
  the speaker mute LED indicator will light up. 
  When the speaker is not muted, 
  the speaker mute LED indicator will light out.

  [Test Case]
  1. run G16 with target kernel.
  2. press the mute hotkey
  3. check if speaker mute led can be switched.

  [Where problems could occur]
  Low, just register a speaker mute led control for dell-laptop.

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


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

[Kernel-packages] [Bug 2015972] Update Released

2023-05-25 Thread Andreas Hasenack

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

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

Title:
  Dell: Enable speaker mute hotkey LED indicator

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in alsa-ucm-conf source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in alsa-ucm-conf source package in Kinetic:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in alsa-ucm-conf source package in Lunar:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Feature Description]
  When users press the speaker mute hotkey and the speaker is muted, 
  the speaker mute LED indicator will light up. 
  When the speaker is not muted, 
  the speaker mute LED indicator will light out.

  [Test Case]
  1. run G16 with target kernel.
  2. press the mute hotkey
  3. check if speaker mute led can be switched.

  [Where problems could occur]
  Low, just register a speaker mute led control for dell-laptop.

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


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

[Kernel-packages] [Bug 2015972] Re: Dell: Enable speaker mute hotkey LED indicator

This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu4.3

---
alsa-ucm-conf (1.2.6.3-1ubuntu4.3) kinetic; urgency=medium

  * d/p/0006-sof-hda-dsp-Add-speaker-led-support.patch
 - Backport patch to fix speaker mute led (LP: #2015972)

 -- Koba Ko   Wed, 19 Apr 2023 09:40:32 +0800

** Changed in: alsa-ucm-conf (Ubuntu Kinetic)
   Status: Fix Committed => Fix Released

** Changed in: alsa-ucm-conf (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Dell: Enable speaker mute hotkey LED indicator

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in alsa-ucm-conf source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in alsa-ucm-conf source package in Kinetic:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in alsa-ucm-conf source package in Lunar:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Feature Description]
  When users press the speaker mute hotkey and the speaker is muted, 
  the speaker mute LED indicator will light up. 
  When the speaker is not muted, 
  the speaker mute LED indicator will light out.

  [Test Case]
  1. run G16 with target kernel.
  2. press the mute hotkey
  3. check if speaker mute led can be switched.

  [Where problems could occur]
  Low, just register a speaker mute led control for dell-laptop.

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


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

[Kernel-packages] [Bug 2015972] Re: Dell: Enable speaker mute hotkey LED indicator