date:20250109

** Changed in: hwe-next
   Status: In Progress => Fix Released

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

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

Title:
  Fix regression and add more region support of QCOM WiFi WCN7850

Status in HWE Next:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-firmware source package in Noble:
  Fix Released
Status in linux-firmware source package in Oracular:
  Fix Released

Bug description:
  [Impact]
  Qualcomm WiFi chip WCN7850 failed to load board data,
  ath12k can not work due to previous update of board-2.bin.

  Also add more region support again.

  [Fix]
  Update board-2.bin in linux-firmware.

  [Test]
  Tested on 2 models of Thinkpad, WiFi works fine.
  Bootup with the new fw, connect to AP,
  use iperf3:
  - - - - - - - - - - - - - - - - - - - - - - - - -
  [ ID] Interval   Transfer Bitrate Retr
  [  5]   0.00-10.00  sec   164 MBytes   138 Mbits/sec0 sender
  [  5]   0.00-10.05  sec   163 MBytes   136 Mbits/sec  receiver

  [Where problems could occur]
  It may break Qualcomm WiFi WCN7850.

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


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

[Kernel-packages] [Bug 2083022] Re: [SRU] Fix AST DP output after resume

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

** Changed in: linux-oem-6.8 (Ubuntu Jammy)
   Status: Won't Fix => 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/2083022

Title:
  [SRU] Fix AST DP output after resume

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.8 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.8 source package in Jammy:
  Fix Released
Status in linux source package in Noble:
  Fix Released
Status in linux-oem-6.8 source package in Noble:
  Fix Released
Status in linux source package in Oracular:
  Fix Released
Status in linux-oem-6.8 source package in Oracular:
  Invalid

Bug description:
  [Impact]
  After resume from suspend, the mini-DP output from ASPEED BMC card
  is either blank or mess up.

  [Fix]
  From upstream 6.11 kernel,

  1, a fix of the blank screen after resume:
  12c35c5582acb drm/ast: Fix black screen after resume

  2, DP detection fix:
  0ce91928ec62d drm/ast: astdp: Wake up during connector status detection

  3, the patchset refactors the CRTC's mode-setting code:
  https://lore.kernel.org/all/20240627153638.8765-1-tzimmerm...@suse.de/

  [Test]
  Tested on hardware by vendor for 10 times of suspend and resume.
  The screen is OK.

  [Where problems could occur]
  It may break ASPEED drm support.

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


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

[Kernel-packages] [Bug 2083022] Re: [SRU] Fix AST DP output after resume

The kernel 6.8.0-50.51~22.04.1 got the fix and set it as fixed.

** Changed in: hwe-next
   Status: In Progress => Fix Released

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

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

Title:
  [SRU] Fix AST DP output after resume

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.8 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.8 source package in Jammy:
  Fix Released
Status in linux source package in Noble:
  Fix Released
Status in linux-oem-6.8 source package in Noble:
  Fix Released
Status in linux source package in Oracular:
  Fix Released
Status in linux-oem-6.8 source package in Oracular:
  Invalid

Bug description:
  [Impact]
  After resume from suspend, the mini-DP output from ASPEED BMC card
  is either blank or mess up.

  [Fix]
  From upstream 6.11 kernel,

  1, a fix of the blank screen after resume:
  12c35c5582acb drm/ast: Fix black screen after resume

  2, DP detection fix:
  0ce91928ec62d drm/ast: astdp: Wake up during connector status detection

  3, the patchset refactors the CRTC's mode-setting code:
  https://lore.kernel.org/all/20240627153638.8765-1-tzimmerm...@suse.de/

  [Test]
  Tested on hardware by vendor for 10 times of suspend and resume.
  The screen is OK.

  [Where problems could occur]
  It may break ASPEED drm support.

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


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

[Kernel-packages] [Bug 2081810] Re: [SRU] uncore: Add ARL and LNL support on 6.11

Tested on 6.11.0-12-generic and 6.11.0-13-generic

$ cat /sys/devices/uncore_*/type
18
19
14
15
16
17
22
23
20
21
25
26
24


** Tags removed: verification-needed-oracular-linux
** Tags added: verification-done-oracular-linux

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

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  [SRU] uncore: Add ARL and LNL support on 6.11

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in linux source package in Noble:
  Invalid
Status in linux-oem-6.11 source package in Noble:
  Fix Released
Status in linux source package in Oracular:
  Fix Released
Status in linux-oem-6.11 source package in Oracular:
  Invalid

Bug description:
  [Impact]
  perf/uncore is not supported on Oracular and OEM-6.11 kernel.

  [Fix]
  Add LNL and ARL support, the commits are just landed in upstream.

  [Test]
  Tested on hardware, the sysfs show:
  On ARL:
  $ cat /sys/devices/uncore_*/type
  30
  31
  16
  26
  27
  17
  18
  19
  20
  21
  22
  23
  24
  25
  34
  28
  29
  32
  33
  36
  37
  38
  39
  35

  On LNL:
  $ cat  /sys/devices/uncore_*/type
  21
  22
  17
  18
  19
  20
  25
  26
  23
  24
  28
  29
  27

  [Where problems could occur]
  It may break uncore support on LNL and ARL.

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


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

[Kernel-packages] [Bug 2089067] Re: IPU6 camera not working with Dell XPS 9315

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

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

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

Title:
  IPU6 camera not working with Dell XPS 9315

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Under Software and Updates -> Additional Drivers, I have enabled the IPU6 
Driver for the webcam
  Now at least this seems to install without a crash
  However, no application can detect a camera (Skype, Cheese, Gnome Camera)

  If I query the devices, this is the output.

  $ v4l2-ctl --list-devices
  ipu6 (PCI:pci:pci:00):
/dev/video0
/dev/video1
/dev/video2
/dev/video3
/dev/video4
/dev/video5
/dev/video6
/dev/video7

  ipu6 (pci:pci:00):
/dev/media0

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-48-generic 6.8.0-48.48
  ProcVersionSignature: Ubuntu 6.8.0-48.48-generic 6.8.12
  Uname: Linux 6.8.0-48-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:noutram6244 F pipewire
   /dev/snd/controlC0:  noutram6244 F pipewire
noutram6246 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 22:34:40 2024
  InstallationDate: Installed on 2024-10-25 (25 days ago)
  InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 
(20240827.1)
  MachineType: Dell Inc. XPS 9315
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-48-generic 
root=UUID=565ec2a5-4079-4e55-b46f-3cdb8d11d281 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-48-generic N/A
   linux-backports-modules-6.8.0-48-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2024
  dmi.bios.release: 1.24
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.24.0
  dmi.board.name: 02GGG1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.24.0:bd09/11/2024:br1.24:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn02GGG1:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:
  dmi.product.family: XPS
  dmi.product.name: XPS 9315
  dmi.product.sku: 0B14
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2081685] Re: [Ubuntu 24.04-generic Kernel-6.8]Hard lockup on 8 Socket System, ThinkSystem SR950 V3.

2025-01-09 Thread Amy Gou

Hi Paolo,

Do you advise when the new test build of kernel will be released for
validation test?

Thanks.

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

Title:
  [Ubuntu 24.04-generic Kernel-6.8]Hard lockup on 8 Socket System,
  ThinkSystem SR950 V3.

Status in linux package in Ubuntu:
  New
Status in linux source package in Noble:
  In Progress
Status in linux source package in Oracular:
  New

Bug description:
  There is CPU hard Lockup detected under Ubuntu 24.04 LTS (kernel
  6.8.0-38). see attachment"dmesg0723-Lockup-Ubuntu24.04.log"

  ubuntu@SR950V3:~$ cat /var/log/dmesg | grep -i  lockup

  [   15.241164] kernel: watchdog: Watchdog detected hard LOCKUP on cpu
  124

  [   15.241164] kernel:  ? watchdog_hardlockup_check+0x1cb/0x3b0

  
  Besides, the issue does not occur on upstream kernel 6.8，6.9, 6.10, 6.11-rc*, 
then only ubuntu kernel issue. see  attachment "dmesg0923-No-Lockup-Kernel 
6-10.log". 
  According to the dmesg log, the "hard lockup" is not a real lockup, 
  Because many CPU try to get cache_disable_lock spin lock at the same time 
when kernel boot. And competition has occurred here. 
  Every CPU's TLB will be flushed in the critical zone, the flushing TLB is a 
time-consuming operation, and there are so many CPUs,
  so the false "hard lockup" was detected by kernel. To avoid customer confuse, 
when Canonical do the fix?

  
  HW Config:
  ThinkSystem SR950 V3

  CPU: 8*  Intel(R) Xeon(R) Platinum 8490H 60 Core 3.5GHz

  MEM:  2TB = SK Hynix 356GB DDR5 4800MHz 3DS (2015.1GB)

  Raid: ThinkSystem RAID 940-8i 4GB Flash PCIe Gen4 12Gb Adapter

  Storage: Micron_7450_MTFDKBA960TFR *1

  Samsung 30.7TB 24Gbps SAS 2.5" SSD

  NIC: ThinkSystem Intel X710-T4L 10GBASE-T 4-Port OCP Ethernet Adapter

  OS: ubuntu 24.04 LTS( kernel 6.8.0-38-generic)

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


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

[Kernel-packages] [Bug 2092284] Re: [Sony Vaio VPCF11M1E] nouveau driver in combination with xorg gives wrong resolution during installation

2025-01-09 Thread Daniel van Vugt

The next step I would recommend is to open an upstream bug with the Nouveau 
developers:
https://gitlab.freedesktop.org/drm/nouveau/-/issues

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

Title:
  [Sony Vaio VPCF11M1E] nouveau driver in combination with xorg gives
  wrong resolution during installation

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

Bug description:
  When booting the installation of 24.04 (LTS) I will be presented with
  a nice screen. However the resolution is wrong. My screen is actually
  1920x1080. However the installation uses a resolution of 2048x1536.
  It's a wrong aspect ratio as well, 16:9 vs 4:3.

  The weird thing is that when having the wrong resolution (2048x1536)
  the pixels actually look crisp as if a native resolution is used.
  Usually in the top right some icons are displayed which I can't see.
  It appears the desktop is expanded beyond the visible screen on the
  right and bottom of the screen. Also when I move my pointer there and
  move it back it will need to travel the same distance to be visible
  again on the screen. I notice it will actually go to the invisible
  desktop, unlike the left and top side of the desktop where the pointer
  stays visible.

  When I right-click on the desktop and select "Display Settings" I am
  able to change the resolution. However the same happens, as described
  above, where the pointer is able to travel beyond the borders of the
  right and bottom side of the screen. The resolution doesn't look crisp
  anymore and appears to be squished together.

  I've traced back where the resolution does appear to be correct and
  that is in the 20.04 LTS release. I've only checked LTS releases.

  My guess is that there is a bug with the nouveau driver. I can't
  change out the graphics card as this happens on a Sony Vaio laptop. I
  do notice the same behavior with the Arch install as well. I have not
  checked other recent distro's.

  My graphics hardware is an NVidia GT330M. I don't actually want to use
  the older nvidia 340 driver as I believe that isn't supported anymore.
  Which is fine. The nouveau driver is probably good enough for me. I
  just want the correct resolution :) .

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  Uname: Linux 6.8.0-41-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CasperVersion: 1.498
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 20 11:26:32 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Sony Corporation GT216M [GeForce GT 330M] [104d:9067]
  LiveMediaBuild: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1)
  MachineType: Sony Corporation VPCF11M1E
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2010
  dmi.bios.release: 2.80
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0280Y6
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 2.80
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0280Y6:bd05/14/2010:br2.80:efr2.80:svnSonyCorporation:pnVPCF11M1E:pvrC604GVG5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:skuN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCF11M1E
  dmi.product.sku: N/A
  dmi.product.version: C604GVG5
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this

[Kernel-packages] [Bug 2093376] [NEW] Random keys "stick" repeating until any key is pressed

2025-01-09 Thread Alexander

Public bug reported:

Bug found on the brand new Dell Vostro laptop with preinstalled Ubuntu
20.04 LTS.

Any key at any random moment (might be once an hour or more often) may
"stick" repeating itself like I would holding it pressed. Any other or
the same key must be pressed to stop this. It's not a hardware keyboard
issue itself, since it happens with the external keyboard as well, but
not happens on other OS on the same computer.

Other users reported facing this bug too mostly with Dell laptops on
20.04, 22.04 which are still in LTS and I'm providing links here because
some useful research is done there which may help to locate the issue.

https://askubuntu.com/questions/1446583/ubuntu-22-04-infrequent-random-key-sticking-on-dell-g15-5521-that-immediately-c/1494501
https://askubuntu.com/questions/1454666/keys-start-repeating-as-if-they-were-stuck-ubuntu-20-04-and-others-on-laptop

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.15.0-126-generic 5.15.0-126.136~20.04.1
ProcVersionSignature: Ubuntu 5.15.0-126.136~20.04.1-generic 5.15.167
Uname: Linux 5.15.0-126-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 10 00:10:40 2025
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-focal-amd64-20200502-85
InstallationDate: Installed on 2024-10-08 (93 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
SourcePackage: linux-signed-hwe-5.15
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug dell focal keyboard

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

Title:
  Random keys "stick" repeating until any key is pressed

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

Bug description:
  Bug found on the brand new Dell Vostro laptop with preinstalled Ubuntu
  20.04 LTS.

  Any key at any random moment (might be once an hour or more often) may
  "stick" repeating itself like I would holding it pressed. Any other or
  the same key must be pressed to stop this. It's not a hardware
  keyboard issue itself, since it happens with the external keyboard as
  well, but not happens on other OS on the same computer.

  Other users reported facing this bug too mostly with Dell laptops on
  20.04, 22.04 which are still in LTS and I'm providing links here
  because some useful research is done there which may help to locate
  the issue.

  
https://askubuntu.com/questions/1446583/ubuntu-22-04-infrequent-random-key-sticking-on-dell-g15-5521-that-immediately-c/1494501
  
https://askubuntu.com/questions/1454666/keys-start-repeating-as-if-they-were-stuck-ubuntu-20-04-and-others-on-laptop

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-126-generic 5.15.0-126.136~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-126.136~20.04.1-generic 5.15.167
  Uname: Linux 5.15.0-126-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 10 00:10:40 2025
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2024-10-08 (93 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  SourcePackage: linux-signed-hwe-5.15
  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.15/+bug/2093376/+subscriptions


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

[Kernel-packages] [Bug 2070339] Re: [Lenovo Ubuntu 24.04 Bug] dmesg show "spi-nor: probe of spi0.0 failed with error -95"

** Description changed:

  Fresh install Ubuntu 24.04 on Lenovo systems with Birch Stream SFR and
  check kernel boot log "dmesg", there is an error of spi-nor show up as
  follows:
  
  spi-nor: probe of spi0.0 failed with error -95
  
  while open kernel dynamic debugging of spi-nor, kernel log show as:
  
  [7.143574] calling  spi_nor_module_init+0x0/0xff0 [spi_nor] @ 1714
  [7.145046] calling  iaa_crypto_init_module+0x0/0xff0 [iaa_crypto] @ 1611
  [7.146116] [1714] spi-nor spi0.0: Manufacturer and device ID: ef602000
  [7.146133] [1714] spi-nor spi0.0: error -95 reading CR
  [7.146135] spi-nor: probe of spi0.0 failed with error -95
  
  Since upstream 6.7.0 has more details info output, I applied it and it
  was:
  
  [   15.425497] calling  spi_nor_module_init+0x0/0xff0 [spi_nor] @ 2944
  [   15.426707] spi-nor spi0.0: w25q512nwq (65536 Kbytes)
  [   15.426714] [2944] spi-nor spi0.0: mtd .name = :00:1f.5, .size = 
0x400 (64MiB), .erasesize = 0x1000 (4KiB) .numeraseregions = 0
  [   15.426735] [2944] spi-nor spi0.0: error -524 reading CR
  [   15.426738] spi-nor: probe of spi0.0 failed with error -524
  [   15.426780] probe of spi0.0 returned 524 after 1247 usecs
  [   15.426797] initcall spi_nor_module_init+0x0/0xff0 [spi_nor] returned 0 
after 1282 usecs
+ 
+ 
+ SRU Justification:
+ ==
+ [Impact]
+ During bootup, the error is shown in dmesg:
+ [ 7.146116] [1714] spi-nor spi0.0: Manufacturer and device ID: ef602000
+ [ 7.146133] [1714] spi-nor spi0.0: error -95 reading CR
+ [ 7.146135] spi-nor: probe of spi0.0 failed with error -95
+ 
+ [Fix]
+ Handle the failed case of -EOPNOTSUPP,
+ and correct the condition of error report.
+ upstream commit in 6.10:
+ fe0b8213c0129 mtd: core: Don't fail mtd_otp_nvmem_add() if OTP is unsupported
+ 5043e55536015 mtd: core: Align comment with an action in mtd_otp_nvmem_add()
+ 
+ [Test]
+ Vendor tested on hardware, there is no error on the testing built
+ kernel.
+ 
+ [Where problems could occur]
+ It may break spi-nor flash support.
+ 
+ Both 2 commits are in 6.10 kernel, so SRU for noble-6.8 only.

** Changed in: linux (Ubuntu)
 Assignee: Leo Lin (0xff07) => AaronMa (mapengyu)

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

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

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

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

Title:
  [Lenovo Ubuntu 24.04 Bug] dmesg show "spi-nor: probe of spi0.0 failed
  with error -95"

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Noble:
  In Progress

Bug description:
  Fresh install Ubuntu 24.04 on Lenovo systems with Birch Stream SFR and
  check kernel boot log "dmesg", there is an error of spi-nor show up as
  follows:

  spi-nor: probe of spi0.0 failed with error -95

  while open kernel dynamic debugging of spi-nor, kernel log show as:

  [7.143574] calling  spi_nor_module_init+0x0/0xff0 [spi_nor] @ 1714
  [7.145046] calling  iaa_crypto_init_module+0x0/0xff0 [iaa_crypto] @ 1611
  [7.146116] [1714] spi-nor spi0.0: Manufacturer and device ID: ef602000
  [7.146133] [1714] spi-nor spi0.0: error -95 reading CR
  [7.146135] spi-nor: probe of spi0.0 failed with error -95

  Since upstream 6.7.0 has more details info output, I applied it and it
  was:

  [   15.425497] calling  spi_nor_module_init+0x0/0xff0 [spi_nor] @ 2944
  [   15.426707] spi-nor spi0.0: w25q512nwq (65536 Kbytes)
  [   15.426714] [2944] spi-nor spi0.0: mtd .name = :00:1f.5, .size = 
0x400 (64MiB), .erasesize = 0x1000 (4KiB) .numeraseregions = 0
  [   15.426735] [2944] spi-nor spi0.0: error -524 reading CR
  [   15.426738] spi-nor: probe of spi0.0 failed with error -524
  [   15.426780] probe of spi0.0 returned 524 after 1247 usecs
  [   15.426797] initcall spi_nor_module_init+0x0/0xff0 [spi_nor] returned 0 
after 1282 usecs

  
  SRU Justification:
  ==
  [Impact]
  During bootup, the error is shown in dmesg:
  [ 7.146116] [1714] spi-nor spi0.0: Manufacturer and device ID: ef602000
  [ 7.146133] [1714] spi-nor spi0.0: error -95 reading CR
  [ 7.146135] spi-nor: probe of spi0.0 failed with error -95

  [Fix]
  Handle the failed case of -EOPNOTSUPP,
  and correct the condition of error report.
  upstream commit in 6.10:
  fe0b8213c0129 mtd: core: Don't fail mtd_otp_nvmem_add() if OTP is unsupported
  5043e55536015 mtd: core: Align comment with an action in mtd_otp_nvmem_add()

  [Test]
  Vendor tested on hardware, there is no error on the testing built
  kernel.

  [Where problems could occur]
  It may break spi-nor flash support.

  Both 2 commits are in 6.10 kernel, so SRU for noble-6.8 only.

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

[Kernel-packages] [Bug 2070339] Re: [Lenovo Ubuntu 24.04 Bug] dmesg show "spi-nor: probe of spi0.0 failed with error -95"

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

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

Title:
  [Lenovo Ubuntu 24.04 Bug] dmesg show "spi-nor: probe of spi0.0 failed
  with error -95"

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Noble:
  In Progress

Bug description:
  Fresh install Ubuntu 24.04 on Lenovo systems with Birch Stream SFR and
  check kernel boot log "dmesg", there is an error of spi-nor show up as
  follows:

  spi-nor: probe of spi0.0 failed with error -95

  while open kernel dynamic debugging of spi-nor, kernel log show as:

  [7.143574] calling  spi_nor_module_init+0x0/0xff0 [spi_nor] @ 1714
  [7.145046] calling  iaa_crypto_init_module+0x0/0xff0 [iaa_crypto] @ 1611
  [7.146116] [1714] spi-nor spi0.0: Manufacturer and device ID: ef602000
  [7.146133] [1714] spi-nor spi0.0: error -95 reading CR
  [7.146135] spi-nor: probe of spi0.0 failed with error -95

  Since upstream 6.7.0 has more details info output, I applied it and it
  was:

  [   15.425497] calling  spi_nor_module_init+0x0/0xff0 [spi_nor] @ 2944
  [   15.426707] spi-nor spi0.0: w25q512nwq (65536 Kbytes)
  [   15.426714] [2944] spi-nor spi0.0: mtd .name = :00:1f.5, .size = 
0x400 (64MiB), .erasesize = 0x1000 (4KiB) .numeraseregions = 0
  [   15.426735] [2944] spi-nor spi0.0: error -524 reading CR
  [   15.426738] spi-nor: probe of spi0.0 failed with error -524
  [   15.426780] probe of spi0.0 returned 524 after 1247 usecs
  [   15.426797] initcall spi_nor_module_init+0x0/0xff0 [spi_nor] returned 0 
after 1282 usecs

  
  SRU Justification:
  ==
  [Impact]
  During bootup, the error is shown in dmesg:
  [ 7.146116] [1714] spi-nor spi0.0: Manufacturer and device ID: ef602000
  [ 7.146133] [1714] spi-nor spi0.0: error -95 reading CR
  [ 7.146135] spi-nor: probe of spi0.0 failed with error -95

  [Fix]
  Handle the failed case of -EOPNOTSUPP,
  and correct the condition of error report.
  upstream commit in 6.10:
  fe0b8213c0129 mtd: core: Don't fail mtd_otp_nvmem_add() if OTP is unsupported
  5043e55536015 mtd: core: Align comment with an action in mtd_otp_nvmem_add()

  [Test]
  Vendor tested on hardware, there is no error on the testing built
  kernel.

  [Where problems could occur]
  It may break spi-nor flash support.

  Both 2 commits are in 6.10 kernel, so SRU for noble-6.8 only.

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


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

[Kernel-packages] [Bug 2085162] Update Released

2025-01-09 Thread Andreas Hasenack

The verification of the Stable Release Update for bluez 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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2085162

Title:
  Bluetooth devices can't reconnect after reboot or sleep

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Noble:
  Confirmed
Status in bluez source package in Oracular:
  Fix Released
Status in bluez source package in Plucky:
  Fix Released

Bug description:
  [ Impact ]

  Bluetooth devices fail to reconnect after a suspend or system restart

  [ Test Plan ]

  1. Put the headphones into discovery mode.
  2. Go to Settings -> Bluetooth and connect to the headphones.
  3. Reboot the laptop.
  4. Go to Settings -> Bluetooth
  5. Click on the headphones.
  6. Try to connect to the headphones.
  7. If step 6. fails try to disconnect.
  8. Go to step 6.

  Expected result:
  After step 6 for headphones to be connected and for headphones to announce 
"Bluetooth connected".

  [ Where problems could occur ]

  The change is in the reading of stored device keys. If the patch is
  wrong it could be that paired devices will not reconnect correctly or
  might use an incorrect profile.

  [ Other Info ]

  How reproducible is the problem:
  Fairly reproducible. It can sometimes takes 30 or more connection attempts 
before a real connection is established.

  Version information:
  Ubuntu 24.10

  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0
  Uname: Linux 6.11.0-9-generic x86_64
  ApportVersion: 2.30.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:sitsofe8130 F pipewire
   /dev/snd/controlC0:  sitsofe8136 F wireplumber
   /dev/snd/controlC1:  sitsofe8136 F wireplumber
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 21 21:34:28 2024
  InstallationDate: Installed on 2024-10-14 (7 days ago)
  InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4)
  MachineType: LENOVO 82KD
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2021
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLCN42WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V15 G2 ALC
  dmi.ec.firmware.release: 1.42
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLCN42WW:bd12/13/2021:br1.42:efr1.42:svnLENOVO:pn82KD:pvrLenovoV15G2ALC:rvnLENOVO:rnLNVNB161216:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrLenovoV15G2ALC:skuLENOVO_MT_82KD_BU_idea_FM_V15G2ALC:
  dmi.product.family: V15 G2 ALC
  dmi.product.name: 82KD
  dmi.product.sku: LENOVO_MT_82KD_BU_idea_FM_V15 G2 ALC
  dmi.product.version: Lenovo V15 G2 ALC
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2085162] Re: Bluetooth devices can't reconnect after reboot or sleep

2025-01-09 Thread Andreas Hasenack

These new test runs now passed and are green.

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

Title:
  Bluetooth devices can't reconnect after reboot or sleep

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Noble:
  Confirmed
Status in bluez source package in Oracular:
  Fix Released
Status in bluez source package in Plucky:
  Fix Released

Bug description:
  [ Impact ]

  Bluetooth devices fail to reconnect after a suspend or system restart

  [ Test Plan ]

  1. Put the headphones into discovery mode.
  2. Go to Settings -> Bluetooth and connect to the headphones.
  3. Reboot the laptop.
  4. Go to Settings -> Bluetooth
  5. Click on the headphones.
  6. Try to connect to the headphones.
  7. If step 6. fails try to disconnect.
  8. Go to step 6.

  Expected result:
  After step 6 for headphones to be connected and for headphones to announce 
"Bluetooth connected".

  [ Where problems could occur ]

  The change is in the reading of stored device keys. If the patch is
  wrong it could be that paired devices will not reconnect correctly or
  might use an incorrect profile.

  [ Other Info ]

  How reproducible is the problem:
  Fairly reproducible. It can sometimes takes 30 or more connection attempts 
before a real connection is established.

  Version information:
  Ubuntu 24.10

  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0
  Uname: Linux 6.11.0-9-generic x86_64
  ApportVersion: 2.30.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:sitsofe8130 F pipewire
   /dev/snd/controlC0:  sitsofe8136 F wireplumber
   /dev/snd/controlC1:  sitsofe8136 F wireplumber
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 21 21:34:28 2024
  InstallationDate: Installed on 2024-10-14 (7 days ago)
  InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4)
  MachineType: LENOVO 82KD
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2021
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLCN42WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V15 G2 ALC
  dmi.ec.firmware.release: 1.42
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLCN42WW:bd12/13/2021:br1.42:efr1.42:svnLENOVO:pn82KD:pvrLenovoV15G2ALC:rvnLENOVO:rnLNVNB161216:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrLenovoV15G2ALC:skuLENOVO_MT_82KD_BU_idea_FM_V15G2ALC:
  dmi.product.family: V15 G2 ALC
  dmi.product.name: 82KD
  dmi.product.sku: LENOVO_MT_82KD_BU_idea_FM_V15 G2 ALC
  dmi.product.version: Lenovo V15 G2 ALC
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2085162] Re: Bluetooth devices can't reconnect after reboot or sleep

This bug was fixed in the package bluez - 5.77-0ubuntu2

---
bluez (5.77-0ubuntu2) oracular; urgency=medium

  * debian/patches/git-reconnect-fix.patch:
   - cherry pick an upstream fix to resolve reconnection problems for
 devices after a suspend or restart (lp: #2085162)

 -- Sebastien Bacher   Fri, 22 Nov 2024 11:10:16
+0100

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

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

Title:
  Bluetooth devices can't reconnect after reboot or sleep

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Noble:
  Confirmed
Status in bluez source package in Oracular:
  Fix Released
Status in bluez source package in Plucky:
  Fix Released

Bug description:
  [ Impact ]

  Bluetooth devices fail to reconnect after a suspend or system restart

  [ Test Plan ]

  1. Put the headphones into discovery mode.
  2. Go to Settings -> Bluetooth and connect to the headphones.
  3. Reboot the laptop.
  4. Go to Settings -> Bluetooth
  5. Click on the headphones.
  6. Try to connect to the headphones.
  7. If step 6. fails try to disconnect.
  8. Go to step 6.

  Expected result:
  After step 6 for headphones to be connected and for headphones to announce 
"Bluetooth connected".

  [ Where problems could occur ]

  The change is in the reading of stored device keys. If the patch is
  wrong it could be that paired devices will not reconnect correctly or
  might use an incorrect profile.

  [ Other Info ]

  How reproducible is the problem:
  Fairly reproducible. It can sometimes takes 30 or more connection attempts 
before a real connection is established.

  Version information:
  Ubuntu 24.10

  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0
  Uname: Linux 6.11.0-9-generic x86_64
  ApportVersion: 2.30.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:sitsofe8130 F pipewire
   /dev/snd/controlC0:  sitsofe8136 F wireplumber
   /dev/snd/controlC1:  sitsofe8136 F wireplumber
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 21 21:34:28 2024
  InstallationDate: Installed on 2024-10-14 (7 days ago)
  InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4)
  MachineType: LENOVO 82KD
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2021
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLCN42WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V15 G2 ALC
  dmi.ec.firmware.release: 1.42
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLCN42WW:bd12/13/2021:br1.42:efr1.42:svnLENOVO:pn82KD:pvrLenovoV15G2ALC:rvnLENOVO:rnLNVNB161216:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrLenovoV15G2ALC:skuLENOVO_MT_82KD_BU_idea_FM_V15G2ALC:
  dmi.product.family: V15 G2 ALC
  dmi.product.name: 82KD
  dmi.product.sku: LENOVO_MT_82KD_BU_idea_FM_V15 G2 ALC
  dmi.product.version: Lenovo V15 G2 ALC
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2093336] [NEW] CIFS crash mounting DFS share in 24.04

2025-01-09 Thread Steffen Schreiber

Public bug reported:

Hello,

I am trying to mount a DFS share in Ubuntu 24.04 LTS and get a kernel
issue with cifs.

---
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 24.04.1 LTS
Release:24.04
Codename:   noble
---
sudo mount -t cifs \
   -o user=${_user},password=${_pass},domain=${_proxy},uid=$(id 
-u),gid=$(id -g),vers=2.1 \
   "${_source}" "${_target}"
---
$ sudo dmesg
[19822.866881] BUG: kernel NULL pointer dereference, address: 0050
[19822.866896] #PF: supervisor read access in kernel mode
[19822.866902] #PF: error_code(0x) - not-present page
[19822.866906] PGD 0 P4D 0 
[19822.866914] Oops:  [#1] PREEMPT SMP NOPTI
[19822.866922] CPU: 3 PID: 83700 Comm: mount.cifs Tainted: P   O   
6.8.0-51-generic #52-Ubuntu
[19822.866929] Hardware name: HP HP Z8 G4 Workstation/81C7, BIOS P60 v02.82 
04/22/2022
[19822.866934] RIP: 0010:cifs_mount_get_tcon+0x8e/0x300 [cifs]
[19822.867074] Code: 00 f0 ff ff 0f 87 39 02 00 00 0f b6 80 8e 06 00 00 3c 01 
0f 87 b4 c2 07 00 a8 01 74 05 41 83 4d 2c 40 48 8b 53 50 48 8b 42 60 <48> 8b 40 
50 8b 40 44 23 82 a0 00 00 00 0f 85 6c 01 00 00 80 a3 8d
[19822.867079] RSP: 0018:b4e0413ef728 EFLAGS: 00010246
[19822.867085] RAX:  RBX: 90dcd134a000 RCX: 
[19822.867090] RDX: 90dcd631a000 RSI:  RDI: 
[19822.867094] RBP: b4e0413ef758 R08:  R09: 
[19822.867097] R10:  R11:  R12: b4e0413ef890
[19822.867101] R13: 90de332f2c00 R14: 90dcc7ecdc00 R15: 90ddca76d000
[19822.867104] FS:  73295972b780() GS:90ebfff8() 
knlGS:
[19822.867109] CS:  0010 DS:  ES:  CR0: 80050033
[19822.867114] CR2: 0050 CR3: 001142b4e002 CR4: 007706f0
[19822.867118] DR0:  DR1:  DR2: 
[19822.867121] DR3:  DR6: fffe0ff0 DR7: 0400
[19822.867125] PKRU: 5554
[19822.867128] Call Trace:
[19822.867132]  
[19822.867157]  ? show_regs+0x6d/0x80
[19822.867173]  ? __die+0x24/0x80
[19822.867181]  ? page_fault_oops+0x99/0x1b0
[19822.867199]  ? do_user_addr_fault+0x2e9/0x670
[19822.867212]  ? exc_page_fault+0x83/0x1b0
[19822.867227]  ? asm_exc_page_fault+0x27/0x30
[19822.867252]  ? cifs_mount_get_tcon+0x8e/0x300 [cifs]
[19822.867366]  ? cifs_mount_get_tcon+0x5f/0x300 [cifs]
[19822.867479]  __dfs_referral_walk+0x462/0x4b0 [cifs]
[19822.867626]  __dfs_mount_share+0x25f/0x310 [cifs]
[19822.867762]  ? dfs_cache_find+0xa6/0x110 [cifs]
[19822.867898]  dfs_mount_share+0x1be/0x2d0 [cifs]
[19822.868036]  cifs_mount+0x64/0x2e0 [cifs]
[19822.868161]  cifs_smb3_do_mount+0x187/0x3d0 [cifs]
[19822.868277]  smb3_get_tree+0x48/0x80 [cifs]
[19822.868412]  vfs_get_tree+0x27/0x100
[19822.868428]  do_new_mount+0x1a0/0x340
[19822.868443]  path_mount+0x1e0/0x830
[19822.868459]  bpf_trampoline_6442499846+0x91/0x138
[19822.868471]  path_mount+0x5/0x830
[19822.868476]  ? __x64_sys_mount+0x127/0x160
[19822.868488]  x64_sys_call+0x1e57/0x25a0
[19822.868497]  do_syscall_64+0x7f/0x180
[19822.868507]  ? __pfx_put_cred_rcu+0x10/0x10
[19822.868518]  ? call_rcu+0x34/0x50
[19822.868528]  ? security_prepare_creds+0x5c/0x100
[19822.868538]  ? __put_cred+0x61/0x80
[19822.868544]  ? commit_creds+0x237/0x2b0
[19822.868553]  ? __do_sys_capset+0x15a/0x1f0
[19822.868568]  ? syscall_exit_to_user_mode+0x86/0x260
[19822.868578]  ? do_syscall_64+0x8c/0x180
[19822.868584]  ? asm_exc_page_fault+0x27/0x30
[19822.868603]  ? __put_user_8+0xd/0x20
[19822.868615]  ? rseq_ip_fixup+0x90/0x1f0
[19822.868629]  ? ptep_set_access_flags+0x4a/0x70
[19822.868638]  ? wp_page_reuse+0x95/0xc0
[19822.868647]  ? do_wp_page+0xed/0x490
[19822.868658]  ? handle_pte_fault+0x1be/0x1d0
[19822.868668]  ? __handle_mm_fault+0x653/0x790
[19822.868687]  ? __count_memcg_events+0x6b/0x120
[19822.868700]  ? count_memcg_events.constprop.0+0x2a/0x50
[19822.868712]  ? handle_mm_fault+0xad/0x380
[19822.868724]  ? do_user_addr_fault+0x333/0x670
[19822.868731]  ? irqentry_exit_to_user_mode+0x7b/0x260
[19822.868741]  ? irqentry_exit+0x43/0x50
[19822.868747]  ? clear_bhb_loop+0x15/0x70
[19822.868752]  ? clear_bhb_loop+0x15/0x70
[19822.868756]  ? clear_bhb_loop+0x15/0x70
[19822.868764]  entry_SYSCALL_64_after_hwframe+0x78/0x80
[19822.868771] RIP: 0033:0x73295952af0e
[19822.868813] Code: 48 8b 0d 0d 7f 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 
0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d da 7e 0d 00 f7 d8 64 89 01 48
[19822.868818] RSP: 002b:7ffcbb68bad8 EFLAGS: 0246 ORIG_RAX: 
00a5
[19822.868825] RAX: ffda RBX: 000a

[Kernel-packages] [Bug 2062951] Re: Random flickering with Intel i915 (Gen4+ GPUs) on Linux

2025-01-09 Thread Leo Vleeshouwers

I would like to assist.
However, if you really want me to test the new kernel, I need more detailed 
instruction.
I gave it a try, but my update manager crashed several times.
As yet, I leave testing the new kernel to the Ubuntu experts.

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

Title:
  Random flickering with Intel i915 (Gen4+ GPUs) on Linux

Status in Linux:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-6.8 package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Confirmed
Status in linux-hwe-6.8 source package in Jammy:
  Fix Released
Status in linux source package in Noble:
  Fix Released
Status in linux-hwe-6.8 source package in Noble:
  Confirmed
Status in linux source package in Oracular:
  Fix Released
Status in linux-hwe-6.8 source package in Oracular:
  Confirmed

Bug description:
  SRU Justification

  [Impact]
  The flickering predominantly occurs when the mouse cursor is in the bottom 
quarter of the screen and stops when the cursor leaves this area.
  Extensive testing across various kernel versions revealed that the issue 
became apparent from kernel version 6.8.0 onward, correlating with the 
mentioned configuration changes, CONFIG_INTEL_IOMMU_DEFAULT_ON and 
CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON.
  The problem persists in the latest drm tip.

  [Fix]
  As an immediate workaround, adding 'intel_iommu=igfx_off' to the kernel 
command line has been found to effectively eliminate the flickering issue. 
  This patch proposes the same behavior as 'intel_iommu=igfx_off' and apply the 
rule to all Intel SKL GPU IDs.

  [Test]
  1. Boot up to desktop with 6.8.0-x kernels
  2. Moving cursor around the desktop
  3. There should be no flicker while cursor is moving

  [Where problems could occur]
  For virtualized environments using hardware-assisted virtualization for 
graphics (such as VFIO or mediated pass-through), disabling IOMMU for graphics 
could either disable these features or reduce their security and efficiency.
  Usually, users pass the 'intel_iommu=on' by themselves when they are using 
related features. So, the impact of this change is minimal.

  ===

  After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy 
flickering at random.
  It happens after a moderate to heavy on screen activity like window 
switching, scrolling etc.
  It never happens when playing video or when there is no interaction using 
keyboard/pointer.

  It tend to happen when the mouse cursor is in the bottom quarter of the 
screen and stops immediately when the cursor leaves that screen region.
  Around the same time the following appears in kernel log:
  kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun

  Happens on both X11 and Wayland on both KDE plasma and Mate (though
  less).

  I first encountered the issue with Linux 6.8.0-11 and it still happens with 
Ubunutu's 6.8.0-28 and Mainline 6.8.7.
  Kernels 6.6, 6.5, 6.1 and older did not have that issue.

  Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD 
Graphics 520]
  Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26

  Attaching kernel log for 6.8.0-28

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


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

[Kernel-packages] [Bug 2073274] Autopkgtest regression report (wireless-regdb/2024.07.04-0ubuntu1~22.04.1)

2025-01-09 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted wireless-regdb 
(2024.07.04-0ubuntu1~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

linux-azure-6.5/6.5.0-1025.26~22.04.1 (arm64)
linux-gcp-6.8/unknown (amd64)
linux-gke/5.15.0-1071.77 (amd64)
linux-oracle-6.5/6.5.0-1027.27~22.04.1 (arm64)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#wireless-regdb

[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 wireless-regdb in Ubuntu.
https://bugs.launchpad.net/bugs/2073274

Title:
   2024.07.04 new upstream release

Status in wireless-regdb package in Ubuntu:
  Fix Released
Status in wireless-regdb source package in Trusty:
  Fix Committed
Status in wireless-regdb source package in Xenial:
  Fix Committed
Status in wireless-regdb source package in Bionic:
  Fix Committed
Status in wireless-regdb source package in Focal:
  Fix Committed
Status in wireless-regdb source package in Jammy:
  Fix Committed
Status in wireless-regdb source package in Noble:
  Fix Committed
Status in wireless-regdb source package in Oracular:
  Fix Released

Bug description:
  [Impact]

  New upstream release. This is a database of wireless regulations, and
  should updated in all releases to ensure users have the most up-to-
  date regulatory information.

  [Test Case]

  Following reboot after installing the new database, it should be
  possible to query and change the regulatory domain using 'iw reg get'
  and 'iw reg set'.

  [Where problems could occur]

  If crda (<< k4.15) or the kernel is unable to use the new database,
  users may be stuck using the default "world" regulatory domain which
  is quite restrictive, therefore they may be unable to use wireless
  channels that they were able to use previously. Regulatory rules may
  have also changed for the user's region, which could also make some
  channels unusable, but this would not be a bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/2073274/+subscriptions


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

[Kernel-packages] [Bug 2089891] Re: [SRU] Add audio rt713 and rt718 support on ThinkPad TM2

Installed firmware-sof-signed 2024.06-1ubuntu1.2.

Tested as above, the speaker and mic works too.

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

Title:
  [SRU] Add audio rt713 and rt718 support on ThinkPad TM2

Status in HWE Next:
  In Progress
Status in firmware-sof package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Invalid
Status in linux-oem-6.11 source package in Noble:
  Fix Released
Status in firmware-sof source package in Oracular:
  Fix Committed
Status in linux source package in Oracular:
  In Progress
Status in linux-oem-6.11 source package in Oracular:
  Invalid

Bug description:
  [Impact]
  There is no sound cards on Intel LNL platform of ThinkPad TM2.

  [Fix]
  Add soc-acpi table entry on LNL for ThinkPad TME laptop
  with rt713 and rt718.

  This kernel patch depends on new sof firmware:
  db771bf v2.11.x: add new 2.11.2 topology2 production binaries
  665e39d Add SOF v2.11.1 signed Intel binaries for MTL/LNL/ARL

  The sof-firmware will be SRU in bug 2086250

  [Test]
  Tested on hardware, audio input and output can work
  with the patch and new sof-firmware.

  $ cat /proc/asound/cards
   0 [sofsoundwire   ]: sof-soundwire - sof-soundwire
    LENOVO-21NTZCF5CN-ThinkPadX1CarbonGen13
  $ speaker-test -c 2
  $ arecord -f cd cd.wav

  [Where problems could occur]
  It may break audio on Intel LNL platform.

  The commit is from 6.12 kernel;
  LNL is only supported on 6.11+ kernel;
  So SRU for oem-6.11 and oracular only.

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


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

[Kernel-packages] [Bug 2089891] Re: [SRU] Add audio rt713 and rt718 support on ThinkPad TM2

Tested on 6.11.0-1011-oem.

firmware-sof:
2023.12.1-1ubuntu1.3

$ speaker-test -c 2

$ arecord -f cd a.wav

The speaker output is good.
The mic recording is good too.

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

Title:
  [SRU] Add audio rt713 and rt718 support on ThinkPad TM2

Status in HWE Next:
  In Progress
Status in firmware-sof package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Invalid
Status in linux-oem-6.11 source package in Noble:
  Fix Released
Status in firmware-sof source package in Oracular:
  Fix Committed
Status in linux source package in Oracular:
  In Progress
Status in linux-oem-6.11 source package in Oracular:
  Invalid

Bug description:
  [Impact]
  There is no sound cards on Intel LNL platform of ThinkPad TM2.

  [Fix]
  Add soc-acpi table entry on LNL for ThinkPad TME laptop
  with rt713 and rt718.

  This kernel patch depends on new sof firmware:
  db771bf v2.11.x: add new 2.11.2 topology2 production binaries
  665e39d Add SOF v2.11.1 signed Intel binaries for MTL/LNL/ARL

  The sof-firmware will be SRU in bug 2086250

  [Test]
  Tested on hardware, audio input and output can work
  with the patch and new sof-firmware.

  $ cat /proc/asound/cards
   0 [sofsoundwire   ]: sof-soundwire - sof-soundwire
    LENOVO-21NTZCF5CN-ThinkPadX1CarbonGen13
  $ speaker-test -c 2
  $ arecord -f cd cd.wav

  [Where problems could occur]
  It may break audio on Intel LNL platform.

  The commit is from 6.12 kernel;
  LNL is only supported on 6.11+ kernel;
  So SRU for oem-6.11 and oracular only.

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


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

[Kernel-packages] [Bug 2086250] Re: Adding support for Realtek sof-soundwire audio on Dell GhostRider platform

2025-01-09 Thread Andreas Hasenack

> 2. Make sure firmware-sof, alsa-ucm-conf and kernel version support
RT722+RT1320.

alsa-ucm-conf is missing the verification on
https://launchpad.net/bugs/2089273

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

Title:
  Adding support for Realtek sof-soundwire audio on Dell GhostRider
  platform

Status in HWE Next:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in firmware-sof package in Ubuntu:
  Fix Released
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in alsa-ucm-conf source package in Noble:
  Fix Committed
Status in firmware-sof source package in Noble:
  Fix Released
Status in linux-firmware source package in Noble:
  Invalid
Status in linux-oem-6.11 source package in Noble:
  Fix Released
Status in alsa-ucm-conf source package in Oracular:
  Fix Committed
Status in firmware-sof source package in Oracular:
  Fix Committed
Status in linux-oem-6.11 source package in Oracular:
  New
Status in alsa-ucm-conf source package in Plucky:
  Fix Released
Status in firmware-sof source package in Plucky:
  Fix Released
Status in linux-firmware source package in Plucky:
  Invalid
Status in linux-oem-6.11 source package in Plucky:
  Invalid

Bug description:
  [SRU Justifications]

  == linux ==

  [Impact]

  Dell GhostRider comes with Realtek RT722 codec + RT1320 amplifier on
  Intel ARL platform. It needs the latest driver from Realtek on kernel
  6.12 to have all audio function working correctly

  [Fix]
  Backport the patchset from Realtek for RT722 and RT1320 on 6.12.

  
  == firmware-sof ==
  [Fix]
  sof-arl-rt722-l0_rt1320-l2.tplg and sof-arl.ri are required and on the 2.11.2 
upstream. 

  == alsa-ucm-conf ==
  [Fix]
  Need following patches for the RT722+RT1320 support.
  d/p/0001-ucm2-soundwire-add-rt722-SDCA-device.patch
  d/p/0001-sof-soundwire-fix-missing-MultiCodec1-initialization.patch
  d/p/0001-ucm2-sof-soundwire-add-RT1320-amplifier.patch
  d/p/0001-rt722-add-mic-led-support.patch

  [Test Case]
  1. Boot up the Dell GhostRider laptops.
  2. Make sure firmware-sof, alsa-ucm-conf and kernel version support 
RT722+RT1320. 
  3. check with the `aplay -l` commands to see if any valid audio output 
devices.
  4. Make sure the audio play/record function is working.

  [Where problems could occur]
  It add support the RT722+RT1320 configuration on Intel ARL platform. Also 
need new firmware-sof and alsa-ucm-conf to support. No regression expected at 
the current stage.

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


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

[Kernel-packages] [Bug 2091352] Re: Enable Realtek NIC ASPM on one Dell Tower platform

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

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

Title:
  Enable Realtek NIC ASPM on one Dell Tower platform

Status in HWE Next:
  New
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in linux-oem-6.11 source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  The /sys/power/suspend_stats/total_hw_sleep desn't increase while suspended, 
because of the ASPM feature is not enabled on Realtek NIC.

  [Fix]
  Added a quirk to while list the platform

  [Test]
  1. check the value of /sys/power/suspend_stats/total_hw_sleep
  2. suspend and resume the system
  3. the value of /sys/power/suspend_stats/total_hw_sleep increases

  [Where problems could occur]
  Enable the ASPM on Realtek NIC sometimes lead to different abnormal behaviors.
  We have done extensive tests on the target platform and make sure there is no 
issue introduced by the ASPM feature.

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


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

[Kernel-packages] [Bug 2093330] Re: Fix audio output fail after resume from suspend with CS42L43 codec

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

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

Title:
  Fix audio output fail after resume from suspend with CS42L43 codec

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.11 package in Ubuntu:
  New
Status in linux source package in Noble:
  New
Status in linux-oem-6.11 source package in Noble:
  Fix Committed
Status in linux source package in Oracular:
  New
Status in linux-oem-6.11 source package in Oracular:
  New
Status in linux source package in Plucky:
  New
Status in linux-oem-6.11 source package in Plucky:
  New

Bug description:
  [SRU Justifications]

  == linux ==

  [Impact]
  audio output will fail to play after resume from suspend

  [Fix]
  backport the fix from 
https://lore.kernel.org/all/20250109093822.5745-1-mstro...@opensource.cirrus.com/T/#u
 to ensures codec will resume after suspending during playback.

  [Test Case]
  1. Boot up the machine with CS42L42 audio codec (Tarako RPL/ARL)
  2. open g-c-c sound panel
  3. suspend/resume
  4. Play sound from the internal speaker on g-c-c sound panel. Make sure audio 
output OK.

  [Where problems could occur]
  This commit simply add force suspend/resume in pm_ops for CS42L43 codec. 
Should be low risk.

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


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

[Kernel-packages] [Bug 2092746] Re: mt7925: system will sometimes hang while rebooting

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

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

Title:
  mt7925: system will sometimes hang while rebooting

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in linux source package in Noble:
  Invalid
Status in linux-oem-6.11 source package in Noble:
  Fix Committed
Status in linux source package in Oracular:
  New
Status in linux-oem-6.11 source package in Oracular:
  New
Status in linux source package in Plucky:
  New
Status in linux-oem-6.11 source package in Plucky:
  Invalid

Bug description:
  [Impact]
  In a MT7925 Dell Platform device, the system would hang when running 
Checkbox's warm-boot test with failure rate 5/30.

  [Fix]
  Cherry-pick the following patches from mainline kernel:

  defc33b5541e Bluetooth: btusb: mediatek: change the conditions for ISO 
interface
  489304e67087 Bluetooth: btusb: mediatek: add intf release flow when usb 
disconnect
  cea1805f165c Bluetooth: btusb: mediatek: add callback function in 
btusb_disconnect
  ad0c6f603bb0 Bluetooth: btusb: mediatek: move Bluetooth power off command 
position

  [Test Plan]
  1. Boot into Ubuntu OS with 6.11 OEM kernel
  2. checkbox-cli run com.canonical.certification::warm-boot-stress-test

  [Where problems could occur]
  May cause regression at USB suspend or USB disconnect.

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


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

[Kernel-packages] [Bug 2092373] Re: Hotplug in HDMI cable on the dock leads to many xe driver warning messages

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

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

Title:
  Hotplug in HDMI cable on the dock leads to many xe driver warning
  messages

Status in HWE Next:
  New
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in linux-oem-6.11 source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  lots of the following warning messages shown in dmesg while plug in HDMI 
cable on the dock.

  [  198.450672] xe :00:02.0: [drm] drm_WARN_ON(!domains || domains->aux_io 
== POWER_DOMAIN_INVALID)
  [  198.450733] WARNING: CPU: 1 PID: 1919 at 
drivers/gpu/drm/i915/display/intel_display_power.c:2527 
intel_display_power_aux_io_domain+0x66/0x90 [xe]

  [Fix]
  The following commit in v6.13 fixes the issue
  f7c2ed9d4ce8 drm/i915/dp: Fix AUX IO power enabling for eDP PSR

  [Test]
  1. Boot up the lunar lake system with a dock connected
  2. Connect HDMI external monitor on the dock
  3. There should be no any error messages shown in dmesg

  [Where problems could occur]
  Restrict the AUX IO power only for eDP/PSR outputs which may potentially lead 
to the monitor which requires AUX IO power doesn't light up .

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


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

[Kernel-packages] [Bug 2093315] Re: Stuck forever while accessing HID-SENSOR-200011.5.auto/iio:device1 device

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

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

Title:
  Stuck forever while accessing HID-SENSOR-200011.5.auto/iio:device1
  device

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in linux source package in Noble:
  New
Status in linux-oem-6.11 source package in Noble:
  Fix Committed
Status in linux source package in Oracular:
  New
Status in linux-oem-6.11 source package in Oracular:
  Invalid
Status in linux source package in Plucky:
  New
Status in linux-oem-6.11 source package in Plucky:
  Invalid

Bug description:
  [Impact]
  While using iio_info to read the devices info, it stuck forever while 
accessing HID-SENSOR-200011.5.auto/iio:device1 device

  [Fix]
  The patch invalidates this kind of device, so interface won't be created

  
https://lore.kernel.org/lkml/20250109040006.1273797-1-acelan@canonical.com/T/

  [Test]
  1. Boots up the machine with this USB camera which comes with an invalid i2c 
sensor
 Bus 003 Device 002: ID 0408:5473 Quanta Computer, Inc. HP 5MP Camera
  2. Run iio_info, it should return the iio information immediately

  [Where problems could occur]
  It won't impact the existing iio devices, the index lower than 0 is invalid.

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


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

[Kernel-packages] [Bug 2092186] Re: xe driver can't detect hotplug monitor

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

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

Title:
  xe driver can't detect hotplug monitor

Status in HWE Next:
  New
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in linux-oem-6.11 source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  Hotplug the external monitor doesn't work.

  [Fix]
  The 2 commits from v6.12 fix the issue
  6a9d2e2988fa drm/xe/display: Add missing HPD interrupt enabling during 
non-d3cold RPM resume
  dcb6c1d07171 drm/xe/display: Separate the d3cold and non-d3cold runtime PM 
handling

  cherry picked the following 2 commits to fix the conflicts
  474f64cb988a drm/xe: Fix missing conversion to xe_display_pm_runtime_resume
  f90491d4b64e drm/xe: Remove runtime argument from display s/r functions

  [Test]
  1. Wait for a while to let the screen dim(not suspend)
  2. Touch keyboard/touchpad to wake up the system
  3. Plug in HDMI monitor to the machine
  4. The external monitor should work

  [Where problems could occur]
  It may affect the behavior of hotplugging in monitors.

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


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

[Kernel-packages] [Bug 2093400] Re: With OLED panel attached to amdgpu the glxgear fps is too low

2025-01-09 Thread You-Sheng Yang

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

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

Title:
  With OLED panel attached to amdgpu the glxgear fps is too low

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Noble:
  New
Status in linux-firmware source package in Oracular:
  New
Status in linux-firmware source package in Plucky:
  Fix Released

Bug description:
  [Summary]
  The oled panel is support 120HZ, but the fps is very low in glxgear.
  In AC mod is around 8x fps, and in DC mode is around 60 fps

  [edid]
  ubuntu@localhost:~$ edid-decode < /sys/class/drm/card1-eDP-1/edid
  edid-decode (hex):

  00 ff ff ff ff ff ff 00 4c 83 b3 41 01 ff 00 00
  00 22 01 04 b5 1e 13 78 03 cf d1 ae 51 3e b6 23
  0b 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01
  01 01 01 01 01 01 cb fe 40 64 b0 08 18 70 20 08
  88 00 2e bd 10 00 00 1b cb fe 40 64 b0 08 c8 7a
  20 08 88 00 2e bd 10 00 00 1b 00 00 00 fd 00 30
  78 da da 42 01 00 00 00 00 00 00 00 00 00 00 02
  00 00 00 00 19 96 c8 3a 15 46 c8 00 00 00 01 33

  70 20 79 02 00 20 00 0c ba 41 59 b3 41 00 00 00
  00 00 18 00 21 00 1d b8 0b 6c 07 40 0b 08 07 00
  ee ea 50 ec d3 b6 3d 42 0b 01 45 54 40 5e d0 60
  18 10 23 78 26 00 09 07 06 03 00 00 00 50 00 00
  22 00 14 e7 f3 09 85 3f 0b 63 00 1f 00 07 00 07
  07 17 00 07 00 07 00 81 00 1f 73 1a 00 00 03 03
  30 78 00 a0 74 02 60 02 78 00 00 00 00 8d e3 05
  80 00 e6 06 05 01 74 60 02 00 00 00 00 00 fe 90

  

  Block 0, Base EDID:
  EDID Structure Version & Revision: 1.4
  Vendor & Product Identification:
  Manufacturer: SDC
  Model: 16819
  Serial Number: 65281
  Made in: 2024
  Basic Display Parameters & Features:
  Digital display
  Bits per primary color channel: 10
  DisplayPort interface
  Maximum image size: 30 cm x 19 cm
  Gamma: 2.20
  Supported color formats: RGB 4:4:4
  First detailed timing includes the native pixel format and preferred refresh 
rate
  Display is continuous frequency
  Color Characteristics:
  Red  : 0.6826, 0.3164
  Green: 0.2451, 0.7138
  Blue : 0.1396, 0.0439
  White: 0.3125, 0.3291
  Established Timings I & II: none
  Standard Timings: none
  Detailed Timing Descriptors:
  DTD 1:  2880x1800  120.001398 Hz   8:5218.883 kHz652.27 MHz (302 
mm x 189 mm)
  Hfront   32 Hsync   8 Hback   60 Hpol P
  Vfront8 Vsync   8 Vback8 Vpol N
  DTD 2:  2880x1800   48.000559 Hz   8:5218.883 kHz652.27 MHz (302 
mm x 189 mm)
  Hfront   32 Hsync   8 Hback   60 Hpol P
  Vfront8 Vsync   8 Vback 2744 Vpol N
  Display Range Limits:
  Monitor ranges (Bare Limits): 48-120 Hz V, 218-218 kHz H, max dotclock 660 MHz
  Manufacturer-Specified Display Descriptor (0x02): 00 02 00 00 00 00 19 96 c8 
3a 15 46 c8 00 00 00 '.:.F'
  Extension blocks: 1
  Checksum: 0x33

  

  Block 1, DisplayID Extension Block:
  Version: 2.0
  Extension Count: 0
  Display Product Primary Use Case: None of the listed primary use cases; 
generic display
  Product Identification Data Block (0x20), OUI BA-41-59:
  Product Code: 16819
  Year of Manufacture: 2024
  Display Parameters Data Block (0x21):
  Image size: 300.0 mm x 190.0 mm
  Display native pixel format: 2880x1800
  Scan Orientation: Left to Right, Top to Bottom
  Luminance Information: Minimum guaranteed value
  Color Information: CIE 1931
  Audio Speaker Information: integrated
  Native Color Chromaticity:
  Primary #1:  (0.683105, 0.315918)
  Primary #2:  (0.245117, 0.714111)
  Primary #3:  (0.139893, 0.043945)
  White Point: (0.312744, 0.329102)
  Native Maximum Luminance (Full Coverage): 400.00 cd/m^2
  Native Maximum Luminance (10% Rectangular Coverage): 616.00 cd/m^2
  Native Minimum Luminance: 0.000500 cd/m^2
  Native Color Depth: 12 bpc
  Display Device Technology: Organic LED
  Native Gamma EOTF: 2.20
  Display Interface Features Data Block:
  Supported bpc for RGB encoding: 6, 8, 10
  Supported bpc for YCbCr 4:4:4 encoding: 8, 10
  Supported bpc for YCbCr 4:2:2 encoding: 8, 10
  Supported color space and EOTF standard combination 1: DCI-P3, BT.2020/SMPTE 
ST 2084
  Video Timing Modes Type 7 - Detailed Timings Data Block:
  DTD:  2880x1800  120.000294 Hz  16:10   218.881 kHz652.264000 MHz (aspect 
16:10, no 3D stereo, preferred)
  Hfront   32 Hsync   8 Hback   60 Hpol N
  Vfront8 Vsync   8 Vback8 Vpol N
  CTA-861 DisplayID Data Block:
  Vendor-Specific Data Block (AMD), OUI 00-00-1A:
  Version: 3.3
  Minimum Refresh Rate: 48 Hz
  Maximum Refresh Rate: 120 Hz
  Flags 1.x: 0x00
  Flags 2.x: 0xa0
  Maximum luminance: 116 (616.884 cd/m^2)
  Minimum luminance: 2 (0.000 cd/m^2)
  Unknown: 0x60 0x02
  Colorimetry Data Block:
  BT2020RGB
  HDR Static Metadata Data Block:
  Electro optical transfer functions:
  Traditional gamma - SDR luminance ran

[Kernel-packages] [Bug 2092655] Re: Audio dropouts with bluetooth earbuds for 3-5 seconds every few minutes

2025-01-09 Thread Daniel van Vugt

I think "scan off" failing just means it wasn't already on. So not an
error, just a bad user interface.

I don't know what Bluetooth stack SteamOS 3.x uses on the Steam Deck.
And although the first error here:

  bluetoothd[60568]: profiles/audio/avdtp.c:cancel_request() Start:
Connection timed out (110)

is coming from BlueZ, it could be due to a kernel problem, a hardware
problem, an environmental problem, or just the Bluetooth audio stack
(provided by Pipewire) not setting up a big enough buffer. So I am out
of ideas right now.

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

Title:
  Audio dropouts with bluetooth earbuds for 3-5 seconds every few
  minutes

Status in linux package in Ubuntu:
  New

Bug description:
  I am using Ubuntu 24.10 and I get a bluetooth audio dropout where the
  desktop environment switches from my headphones to the speaker and
  back to the headphones within the span of 5 seconds. This happens
  quite frequently and even when audio is playing. The syslog shows:

  2024-12-29T00:52:53.732631-08:00 iroh bluetoothd[60568]: 
profiles/audio/avdtp.c:cancel_request() Start: Connection timed out (110)
  2024-12-29T00:52:53.733093-08:00 iroh wireplumber[10903]: spa.bluez5: Acquire 
/org/bluez/hci0/dev_24_95_2F_AF_2A_3D/fd20 returned error: 
org.bluez.Error.Failed
  2024-12-29T00:52:53.733398-08:00 iroh wireplumber[10903]: pw.node: 
(bluez_output.24_95_2F_AF_2A_3D.1-130) running -> error (Received error event)
  2024-12-29T00:52:53.733503-08:00 iroh wireplumber[10903]: spa.bluez5: Failure 
in Bluetooth audio transport /org/bluez/hci0/dev_24_95_2F_AF_2A_3D/fd20
  2024-12-29T00:52:53.733699-08:00 iroh pipewire[10899]: pw.node: 
(bluez_output.24_95_2F_AF_2A_3D.1-130) idle -> error (Received error event)
  2024-12-29T00:52:53.751050-08:00 iroh kded6[2621]: org.kde.pulseaudio: No 
object for name "bluez_output.24_95_2F_AF_2A_3D.1"
  2024-12-29T00:52:53.751500-08:00 iroh plasmashell[2660]: org.kde.pulseaudio: 
No object for name "bluez_output.24_95_2F_AF_2A_3D.1"

  At the exact time that these dropouts happen. The same earbuds work
  fine on android and on the steam deck so I think the problem is with
  the laptop setup. Can anyone help?

  Core Info:
  * Ubuntu 24.10
  * Pixel Buds Pro 2 earbuds
  * 6.11 kernel default with 24.10
  * AX211 CNVi wifi/bt integrated onto motherboard
  * Happens with bluez 5.77-0ubuntu1, 5.77-0ubuntu2, (5.79-1 from 25.04 repos)
  * latest linux-firmware in ubuntu 24.10 20240913.gita34e7a5f-0ubuntu2.2

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


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

[Kernel-packages] [Bug 2092655] Re: Audio dropouts with bluetooth earbuds for 3-5 seconds every few minutes

2025-01-09 Thread Rohit

Thanks for the follow up. Here's what I tried and the results:

I set up a 5GHz and 6GHz network and I still have problems with the
disconnects

I tried:

bluetoothctl
# scan off
# Failed to stop discovery: org.bluez.Error.Failed

I can't turn scan off and this seems to be common when I do a bit of
googling.

Any other advice? I am surprised that the steam deck doesn't have the
same issues as it's probably in a similar stack.

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

Title:
  Audio dropouts with bluetooth earbuds for 3-5 seconds every few
  minutes

Status in linux package in Ubuntu:
  New

Bug description:
  I am using Ubuntu 24.10 and I get a bluetooth audio dropout where the
  desktop environment switches from my headphones to the speaker and
  back to the headphones within the span of 5 seconds. This happens
  quite frequently and even when audio is playing. The syslog shows:

  2024-12-29T00:52:53.732631-08:00 iroh bluetoothd[60568]: 
profiles/audio/avdtp.c:cancel_request() Start: Connection timed out (110)
  2024-12-29T00:52:53.733093-08:00 iroh wireplumber[10903]: spa.bluez5: Acquire 
/org/bluez/hci0/dev_24_95_2F_AF_2A_3D/fd20 returned error: 
org.bluez.Error.Failed
  2024-12-29T00:52:53.733398-08:00 iroh wireplumber[10903]: pw.node: 
(bluez_output.24_95_2F_AF_2A_3D.1-130) running -> error (Received error event)
  2024-12-29T00:52:53.733503-08:00 iroh wireplumber[10903]: spa.bluez5: Failure 
in Bluetooth audio transport /org/bluez/hci0/dev_24_95_2F_AF_2A_3D/fd20
  2024-12-29T00:52:53.733699-08:00 iroh pipewire[10899]: pw.node: 
(bluez_output.24_95_2F_AF_2A_3D.1-130) idle -> error (Received error event)
  2024-12-29T00:52:53.751050-08:00 iroh kded6[2621]: org.kde.pulseaudio: No 
object for name "bluez_output.24_95_2F_AF_2A_3D.1"
  2024-12-29T00:52:53.751500-08:00 iroh plasmashell[2660]: org.kde.pulseaudio: 
No object for name "bluez_output.24_95_2F_AF_2A_3D.1"

  At the exact time that these dropouts happen. The same earbuds work
  fine on android and on the steam deck so I think the problem is with
  the laptop setup. Can anyone help?

  Core Info:
  * Ubuntu 24.10
  * Pixel Buds Pro 2 earbuds
  * 6.11 kernel default with 24.10
  * AX211 CNVi wifi/bt integrated onto motherboard
  * Happens with bluez 5.77-0ubuntu1, 5.77-0ubuntu2, (5.79-1 from 25.04 repos)
  * latest linux-firmware in ubuntu 24.10 20240913.gita34e7a5f-0ubuntu2.2

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


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

[Kernel-packages] [Bug 2092655] Re: Audio dropouts with bluetooth earbuds for 3-5 seconds every few minutes

2025-01-09 Thread Rohit

Is there a way to set the pipewire buffer length? I would try with a
newer kernel but the mainline kernel ppa isn't updating again. Seems
like something is broken on the ppa.

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

Title:
  Audio dropouts with bluetooth earbuds for 3-5 seconds every few
  minutes

Status in linux package in Ubuntu:
  New

Bug description:
  I am using Ubuntu 24.10 and I get a bluetooth audio dropout where the
  desktop environment switches from my headphones to the speaker and
  back to the headphones within the span of 5 seconds. This happens
  quite frequently and even when audio is playing. The syslog shows:

  2024-12-29T00:52:53.732631-08:00 iroh bluetoothd[60568]: 
profiles/audio/avdtp.c:cancel_request() Start: Connection timed out (110)
  2024-12-29T00:52:53.733093-08:00 iroh wireplumber[10903]: spa.bluez5: Acquire 
/org/bluez/hci0/dev_24_95_2F_AF_2A_3D/fd20 returned error: 
org.bluez.Error.Failed
  2024-12-29T00:52:53.733398-08:00 iroh wireplumber[10903]: pw.node: 
(bluez_output.24_95_2F_AF_2A_3D.1-130) running -> error (Received error event)
  2024-12-29T00:52:53.733503-08:00 iroh wireplumber[10903]: spa.bluez5: Failure 
in Bluetooth audio transport /org/bluez/hci0/dev_24_95_2F_AF_2A_3D/fd20
  2024-12-29T00:52:53.733699-08:00 iroh pipewire[10899]: pw.node: 
(bluez_output.24_95_2F_AF_2A_3D.1-130) idle -> error (Received error event)
  2024-12-29T00:52:53.751050-08:00 iroh kded6[2621]: org.kde.pulseaudio: No 
object for name "bluez_output.24_95_2F_AF_2A_3D.1"
  2024-12-29T00:52:53.751500-08:00 iroh plasmashell[2660]: org.kde.pulseaudio: 
No object for name "bluez_output.24_95_2F_AF_2A_3D.1"

  At the exact time that these dropouts happen. The same earbuds work
  fine on android and on the steam deck so I think the problem is with
  the laptop setup. Can anyone help?

  Core Info:
  * Ubuntu 24.10
  * Pixel Buds Pro 2 earbuds
  * 6.11 kernel default with 24.10
  * AX211 CNVi wifi/bt integrated onto motherboard
  * Happens with bluez 5.77-0ubuntu1, 5.77-0ubuntu2, (5.79-1 from 25.04 repos)
  * latest linux-firmware in ubuntu 24.10 20240913.gita34e7a5f-0ubuntu2.2

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


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

[Kernel-packages] [Bug 2092284] Re: [Sony Vaio VPCF11M1E] nouveau driver in combination with xorg gives wrong resolution during installation

2025-01-09 Thread Daniel van Vugt

OK, we've established the problem is originating in the kernel/BIOS
anyway. It sounds like you need either a BIOS fix or a quirk for this
machine model implemented in the kernel.

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

Title:
  [Sony Vaio VPCF11M1E] nouveau driver in combination with xorg gives
  wrong resolution during installation

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

Bug description:
  When booting the installation of 24.04 (LTS) I will be presented with
  a nice screen. However the resolution is wrong. My screen is actually
  1920x1080. However the installation uses a resolution of 2048x1536.
  It's a wrong aspect ratio as well, 16:9 vs 4:3.

  The weird thing is that when having the wrong resolution (2048x1536)
  the pixels actually look crisp as if a native resolution is used.
  Usually in the top right some icons are displayed which I can't see.
  It appears the desktop is expanded beyond the visible screen on the
  right and bottom of the screen. Also when I move my pointer there and
  move it back it will need to travel the same distance to be visible
  again on the screen. I notice it will actually go to the invisible
  desktop, unlike the left and top side of the desktop where the pointer
  stays visible.

  When I right-click on the desktop and select "Display Settings" I am
  able to change the resolution. However the same happens, as described
  above, where the pointer is able to travel beyond the borders of the
  right and bottom side of the screen. The resolution doesn't look crisp
  anymore and appears to be squished together.

  I've traced back where the resolution does appear to be correct and
  that is in the 20.04 LTS release. I've only checked LTS releases.

  My guess is that there is a bug with the nouveau driver. I can't
  change out the graphics card as this happens on a Sony Vaio laptop. I
  do notice the same behavior with the Arch install as well. I have not
  checked other recent distro's.

  My graphics hardware is an NVidia GT330M. I don't actually want to use
  the older nvidia 340 driver as I believe that isn't supported anymore.
  Which is fine. The nouveau driver is probably good enough for me. I
  just want the correct resolution :) .

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  Uname: Linux 6.8.0-41-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CasperVersion: 1.498
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 20 11:26:32 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Sony Corporation GT216M [GeForce GT 330M] [104d:9067]
  LiveMediaBuild: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1)
  MachineType: Sony Corporation VPCF11M1E
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2010
  dmi.bios.release: 2.80
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0280Y6
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 2.80
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0280Y6:bd05/14/2010:br2.80:efr2.80:svnSonyCorporation:pnVPCF11M1E:pvrC604GVG5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:skuN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCF11M1E
  dmi.product.sku: N/A
  dmi.product.version: C604GVG5
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2buil

[Kernel-packages] [Bug 2092284] Re: [Sony Vaio VPCF11M1E] nouveau driver in combination with xorg gives wrong resolution during installation

2025-01-09 Thread Marcel van den Bosch

No I can't select anything on the login screen, This happens during the
launch of the installation.

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

Title:
  [Sony Vaio VPCF11M1E] nouveau driver in combination with xorg gives
  wrong resolution during installation

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

Bug description:
  When booting the installation of 24.04 (LTS) I will be presented with
  a nice screen. However the resolution is wrong. My screen is actually
  1920x1080. However the installation uses a resolution of 2048x1536.
  It's a wrong aspect ratio as well, 16:9 vs 4:3.

  The weird thing is that when having the wrong resolution (2048x1536)
  the pixels actually look crisp as if a native resolution is used.
  Usually in the top right some icons are displayed which I can't see.
  It appears the desktop is expanded beyond the visible screen on the
  right and bottom of the screen. Also when I move my pointer there and
  move it back it will need to travel the same distance to be visible
  again on the screen. I notice it will actually go to the invisible
  desktop, unlike the left and top side of the desktop where the pointer
  stays visible.

  When I right-click on the desktop and select "Display Settings" I am
  able to change the resolution. However the same happens, as described
  above, where the pointer is able to travel beyond the borders of the
  right and bottom side of the screen. The resolution doesn't look crisp
  anymore and appears to be squished together.

  I've traced back where the resolution does appear to be correct and
  that is in the 20.04 LTS release. I've only checked LTS releases.

  My guess is that there is a bug with the nouveau driver. I can't
  change out the graphics card as this happens on a Sony Vaio laptop. I
  do notice the same behavior with the Arch install as well. I have not
  checked other recent distro's.

  My graphics hardware is an NVidia GT330M. I don't actually want to use
  the older nvidia 340 driver as I believe that isn't supported anymore.
  Which is fine. The nouveau driver is probably good enough for me. I
  just want the correct resolution :) .

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  Uname: Linux 6.8.0-41-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CasperVersion: 1.498
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 20 11:26:32 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Sony Corporation GT216M [GeForce GT 330M] [104d:9067]
  LiveMediaBuild: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1)
  MachineType: Sony Corporation VPCF11M1E
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2010
  dmi.bios.release: 2.80
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0280Y6
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 2.80
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0280Y6:bd05/14/2010:br2.80:efr2.80:svnSonyCorporation:pnVPCF11M1E:pvrC604GVG5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:skuN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCF11M1E
  dmi.product.sku: N/A
  dmi.product.version: C604GVG5
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ub

[Kernel-packages] [Bug 2093139] Re: listmount04 from ubuntu_ltp_syscalls failed on Noble

2025-01-09 Thread Po-Hsu Lin

listmount04.c:130: TFAIL: invalid mnt_id_req.param invalid retval 25:
SUCCESS (0)

This can be fixed by
https://github.com/torvalds/linux/commit/4bed843b10004d9101b49ac7270131051c39a9

However this cannot be cherry-picked like the previous one, it will need
to be backported to add corresponding code in place.

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

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

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

** Changed in: linux (Ubuntu Noble)
   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/2093139

Title:
  listmount04 from ubuntu_ltp_syscalls failed on Noble

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Noble:
  Confirmed

Bug description:
  This is a new test case added in 2024 Oct. 09 [1] therefore this is
  not a regression but a new failure after updating our LTP fork.

  Failure found on Noble 6.8.0-51.52 (test require 6.8 and higher),
  Oracular is good.

  Log:
  INFO: Test start time: Tue Dec 31 09:44:04 UTC 2024
  COMMAND:/opt/ltp/bin/ltp-pan -q  -e -S   -a 132284 -n 132284  -f 
/tmp/ltp-eo3P32dP5x/alltests -l /dev/null  -C /dev/null -T /dev/null
  LOG File: /dev/null
  FAILED COMMAND File: /dev/null
  TCONF COMMAND File: /dev/null
  Running tests...
  tst_buffers.c:57: TINFO: Test is using guarded buffers
  tst_test.c:1893: TINFO: LTP version: 20240930
  tst_test.c:1897: TINFO: Tested kernel: 6.8.0-51-generic #52-Ubuntu SMP 
PREEMPT_DYNAMIC Thu Dec  5 13:09:44 UTC 2024 x86_64
  tst_test.c:1728: TINFO: Timeout per run is 0h 00m 30s
  listmount04.c:130: TPASS: request points to unaccessible memory : EFAULT (14)
  listmount04.c:130: TPASS: mnt_ids points to unaccessible memory : EFAULT (14)
  listmount04.c:130: TPASS: invalid flags : EINVAL (22)
  listmount04.c:130: TPASS: insufficient mnt_id_req.size : EINVAL (22)
  listmount04.c:130: TPASS: invalid mnt_id_req.spare : EINVAL (22)
  listmount04.c:130: TFAIL: invalid mnt_id_req.param invalid retval 25: SUCCESS 
(0)
  listmount04.c:130: TFAIL: invalid mnt_id_req.mnt_id expected EINVAL: ENOENT 
(2)
  listmount04.c:130: TPASS: non-existant mnt_id : ENOENT (2)

  Summary:
  passed   6
  failed   2
  broken   0
  skipped  0
  warnings 0
  INFO: ltp-pan reported some tests FAIL
  LTP Version: 20240930
  INFO: Test end time: Tue Dec 31 09:44:04 UTC 2024

  [1] https://github.com/linux-test-
  project/ltp/commit/141958ad3e13705bc2e7e1895ac83823e5c0a5ca

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


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

[Kernel-packages] [Bug 2093077] Re: Fix Mic Mute LED not working problem on Dell Tarako platform

2025-01-09 Thread Juerg Haefliger

Source packages uploaded. Note that the previous version is still stuck in 
oracular-proposed:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2089891/comments/11

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

Title:
  Fix Mic Mute LED not working problem on Dell Tarako platform

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  New
Status in firmware-sof source package in Noble:
  New
Status in firmware-sof source package in Oracular:
  New
Status in firmware-sof source package in Plucky:
  New

Bug description:
  [SRU Justifications]

  == firmware-sof ==

  [Impact]
  The mic-mute led not working on Dell Tarako laptops with Cirrus Audio Codec.

  [Fix]
  For firmware-sof, it required the updated sof-rpl-cs42l43-l0.tplg to remove 
the useless 'PGA5.0 5 Master Capture Switch' and 'PGA2.0 2 Master Capture 
Switch' for Mic Mute LED control

  [Test Case]
  1. install firmware-sof-signed with version >= 2023.12.1-1ubuntu1.4.
  2. press mic-mute hot-key and check if mic-mute LED is toggled correctly and 
aligned with the Mic-Mute status.

  [Where problems could occur]
  The topology only affects the particular Intel platforms with configuration 
which connects the cs42l43 codec on link #0 of soundwire. Should be low risk 
for regression.

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


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

[Kernel-packages] [Bug 2092284] Re: [Sony Vaio VPCF11M1E] nouveau driver in combination with xorg gives wrong resolution during installation

2025-01-09 Thread Marcel van den Bosch

I just tried to see if a newer BIOS is available, but unfortunately for
my model no downloads are available anymore as support has been dropped.
(See https://www.sony.nl/electronics/support/laptop-pc-vpc-
series/vpcf11m1e/downloads)

What's the process from here? It probably is a quirk for this machine
model. How big is the change this does get fixed?

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

Title:
[Sony Vaio VPCF11M1E] nouveau driver in combination with xorg gives
wrong resolution during installation

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

Bug description:
When booting the installation of 24.04 (LTS) I will be presented with
a nice screen. However the resolution is wrong. My screen is actually
1920x1080. However the installation uses a resolution of 2048x1536.
It's a wrong aspect ratio as well, 16:9 vs 4:3.

The weird thing is that when having the wrong resolution (2048x1536)
the pixels actually look crisp as if a native resolution is used.
Usually in the top right some icons are displayed which I can't see.
It appears the desktop is expanded beyond the visible screen on the
right and bottom of the screen. Also when I move my pointer there and
move it back it will need to travel the same distance to be visible
again on the screen. I notice it will actually go to the invisible
desktop, unlike the left and top side of the desktop where the pointer
stays visible.

When I right-click on the desktop and select "Display Settings" I am
able to change the resolution. However the same happens, as described
above, where the pointer is able to travel beyond the borders of the
right and bottom side of the screen. The resolution doesn't look crisp
anymore and appears to be squished together.

I've traced back where the resolution does appear to be correct and
that is in the 20.04 LTS release. I've only checked LTS releases.

My guess is that there is a bug with the nouveau driver. I can't
change out the graphics card as this happens on a Sony Vaio laptop. I
do notice the same behavior with the Arch install as well. I have not
checked other recent distro's.

My graphics hardware is an NVidia GT330M. I don't actually want to use
the older nvidia 340 driver as I believe that isn't supported anymore.
Which is fine. The nouveau driver is probably good enough for me. I
just want the correct resolution :) .

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
Uname: Linux 6.8.0-41-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CasperVersion: 1.498
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 20 11:26:32 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00
[VGA controller])
Subsystem: Sony Corporation GT216M [GeForce GT 330M] [104d:9067]
LiveMediaBuild: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1)
MachineType: Sony Corporation VPCF11M1E
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/14/2010
dmi.bios.release: 2.80
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R0280Y6
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.ec.firmware.release: 2.80
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrR0280Y6:bd05/14/2010:br2.80:efr2.80:svnSonyCorporation:pnVPCF11M1E:pvrC604GVG5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:skuN/A:
dmi.product.family: VAIO
dmi.product.name: VPCF11M1E
dmi.product.sku: N/A
dmi.product.version: C604GVG5
dmi.sys.vendor: Sony Corporation
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build

[Kernel-packages] [Bug 2093330] [NEW] Fix audio output fail after resume from suspend with CS42L43 codec

2025-01-09 Thread Chris Chiu

Public bug reported:

[SRU Justifications]

== linux ==

[Impact]
audio input/out will fail to work after resume from suspend

[Fix]
backport the fix from 
https://lore.kernel.org/all/20250109093822.5745-1-mstro...@opensource.cirrus.com/T/#u
 to ensures codec will resume after suspending during playback.

[Test Case]
1. Boot up the machine with CS42L42 audio codec (Tarako RPL/ARL)
2. open g-c-c sound panel
3. suspend/resume
4. Play sound from the internal speaker on g-c-c sound panel. Make sure audio 
output OK.

[Where problems could occur]
This commit simply add force suspend/resume in pm_ops for CS42L43 codec. Should 
be low risk.

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

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

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

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

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

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

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

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

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


** Tags: jira-somerville-1356 oem-priority

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

** No longer affects: firmware-sof (Ubuntu)

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

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

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

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

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

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

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

** Tags added: jira-somerville-1356 oem-priority

** Description changed:

  [SRU Justifications]
  
  == linux ==
  
  [Impact]
  audio input/out will fail to work after resume from suspend
  
  [Fix]
  backport the fix from 
https://lore.kernel.org/all/20250109093822.5745-1-mstro...@opensource.cirrus.com/T/#u
 to ensures codec will resume after suspending during playback.
  
  [Test Case]
  1. Boot up the machine with CS42L42 audio codec (Tarako RPL/ARL)
  2. open g-c-c sound panel
  3. suspend/resume
  4. Play sound from the internal speaker on g-c-c sound panel. Make sure audio 
output OK.
  
  [Where problems could occur]
- This commit simply ensures the resume process is enabled in runtime resume on 
CS42L43 codec. Should be low risk.
+ This commit simply add force suspend/resume in pm_ops for CS42L43 codec. 
Should be low risk.

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

Title:
  Fix audio output fail after resume from suspend with CS42L43 codec

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.11 package in Ubuntu:
  New
Status in linux source package in Noble:
  New
Status in linux-oem-6.11 source package in Noble:
  New
Status in linux source package in Oracular:
  New
Status in linux-oem-6.11 source package in Oracular:
  New
Status in linux source package in Plucky:
  New
Status in linux-oem-6.11 source package in Plucky:
  New

Bug description:
  [SRU Justifications]

  == linux ==

  [Impact]
  audio input/out will fail to work after resume from suspend

  [Fix]
  backport the fix from 
https://lore.kernel.org/all/20250109093822.5745-1-mstro...@opensource.cirrus.com/T/#u
 to ensures codec will resume after suspending during playback.

  [Test Case]
  1. Boot up the machine with CS42L42 audio codec (Tarako RPL/ARL)
  2. open g-c-c sound panel
  3. suspend/resume
  4. Play sound from the internal speaker on g-c-c sound panel. Make sure audio 
output OK.

  [Where problems could occur]
  This commit simply add force suspend/resume in pm_ops for CS42L43 codec. 
Should be low risk.

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


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

[Kernel-packages] [Bug 2093330] Re: Fix audio output fail after resume from suspend with CS42L43 codec

2025-01-09 Thread Chris Chiu

** Description changed:

  [SRU Justifications]
  
  == linux ==
  
  [Impact]
- audio input/out will fail to work after resume from suspend
+ audio output will fail to play after resume from suspend
  
  [Fix]
  backport the fix from 
https://lore.kernel.org/all/20250109093822.5745-1-mstro...@opensource.cirrus.com/T/#u
 to ensures codec will resume after suspending during playback.
  
  [Test Case]
  1. Boot up the machine with CS42L42 audio codec (Tarako RPL/ARL)
  2. open g-c-c sound panel
  3. suspend/resume
  4. Play sound from the internal speaker on g-c-c sound panel. Make sure audio 
output OK.
  
  [Where problems could occur]
  This commit simply add force suspend/resume in pm_ops for CS42L43 codec. 
Should be low risk.

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

Title:
  Fix audio output fail after resume from suspend with CS42L43 codec

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.11 package in Ubuntu:
  New
Status in linux source package in Noble:
  New
Status in linux-oem-6.11 source package in Noble:
  New
Status in linux source package in Oracular:
  New
Status in linux-oem-6.11 source package in Oracular:
  New
Status in linux source package in Plucky:
  New
Status in linux-oem-6.11 source package in Plucky:
  New

Bug description:
  [SRU Justifications]

  == linux ==

  [Impact]
  audio output will fail to play after resume from suspend

  [Fix]
  backport the fix from 
https://lore.kernel.org/all/20250109093822.5745-1-mstro...@opensource.cirrus.com/T/#u
 to ensures codec will resume after suspending during playback.

  [Test Case]
  1. Boot up the machine with CS42L42 audio codec (Tarako RPL/ARL)
  2. open g-c-c sound panel
  3. suspend/resume
  4. Play sound from the internal speaker on g-c-c sound panel. Make sure audio 
output OK.

  [Where problems could occur]
  This commit simply add force suspend/resume in pm_ops for CS42L43 codec. 
Should be low risk.

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


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

[Kernel-packages] [Bug 2091565] Re: Crackling and skipping audio via amdgpu HDMI/DP since linux-image-6.8.0-50-generic

2025-01-09 Thread Amos

Confirmed this is a problem for me too.


echo "options snd-hda-intel snoop=0" | sudo tee 
/etc/modprobe.d/hdmisoundfix.conf
sudo update-initramfs -u -k all


Worked for me (but only use one output device).

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

Title:
  Crackling and skipping audio via amdgpu HDMI/DP since linux-
  image-6.8.0-50-generic

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

Bug description:
  Since the update to Linux 6.8.0-50-generic, HDMI/DP audio output
  crackles and skips, and is completely unusable. This is via an AMD
  Radeon RX 550 using the default amdgpu driver.

  I have no issues with my USB DAC or the analog and SPDIF outputs of my
  onboard sound card. They all work fine.

  The problem is caused by conditional snooping being enabled for AMD
  GPU's. This patch has been reverted upstream in the Linux kernel
  because it breaks a lot of hardware. Debian has also reverted the
  patch in all of their kernels.

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081833
  https://bugzilla.kernel.org/show_bug.cgi?id=219087
  https://www.spinics.net/lists/stable-commits/msg376549.html

  Rebooting and selecting Linux 6.8.0-49-generic in GRUB completely
  solves the issue, so I am 100% sure this is a regression in the latest
  kernel and not a hardware issue.

  So please revert "ALSA: hda: Conditionally use snooping for AMD HDMI".

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-50-generic 6.8.0-50.51
  ProcVersionSignature: Ubuntu 6.8.0-50.51-generic 6.8.12
  Uname: Linux 6.8.0-50-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Dec 11 16:37:20 2024
  HibernationDevice: RESUME=UUID=5d72bb4c-ca50-4252-ada7-c6f8c515d0a5
  MachineType: ASUS P8Z77-V
  ProcEnviron:
   LANG=nl_NL.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-50-generic 
root=UUID=81f554dc-4199-4f5c-a5a5-0d5436da969a ro quiet splash loglevel=3 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-50-generic N/A
   linux-backports-modules-6.8.0-50-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to noble on 2024-04-20 (235 days ago)
  dmi.bios.date: 05/14/2024
  dmi.bios.release: 24.5
  dmi.bios.vendor: coreboot
  dmi.bios.version: 24.05
  dmi.board.name: P8Z77-V
  dmi.board.vendor: ASUS
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: ASUS
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr24.05:bd05/14/2024:br24.5:efr0.0:svnASUS:pnP8Z77-V:pvr1.0:rvnASUS:rnP8Z77-V:rvr1.0:cvnASUS:ct3:cvr:sku:
  dmi.product.name: P8Z77-V
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUS

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


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

[Kernel-packages] [Bug 2091444] Re: BMG support improvement / SRF TDX enablement

2025-01-09 Thread Thibf

** Changed in: linux-intel (Ubuntu Oracular)
   Status: New => Fix Committed

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

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

Title:
  BMG support improvement / SRF TDX enablement

Status in linux-intel package in Ubuntu:
  New
Status in linux-intel source package in Oracular:
  Fix Released

Bug description:
  Support latest improvement of the graphic driver for Battlemage (BMG)
  and enable SRF TDX module.

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


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

[Kernel-packages] [Bug 2086212] Re: IDPF driver should be module, not built-in

2025-01-09 Thread Ian Whitfield

** Also affects: linux-gke (Ubuntu Plucky)
   Importance: Medium
 Assignee: Ian Whitfield (ijwhitfield)
   Status: In Progress

** Also affects: linux-gcp (Ubuntu Plucky)
   Importance: Medium
 Assignee: Ian Whitfield (ijwhitfield)
   Status: In Progress

** No longer affects: linux-gke (Ubuntu Plucky)

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

Title:
  IDPF driver should be module, not built-in

Status in linux-gcp package in Ubuntu:
  In Progress
Status in linux-gke package in Ubuntu:
  In Progress
Status in linux-gcp source package in Jammy:
  Fix Released
Status in linux-gke source package in Jammy:
  Fix Released
Status in linux-gcp source package in Noble:
  Fix Released
Status in linux-gke source package in Noble:
  Fix Released
Status in linux-gcp source package in Oracular:
  Fix Released
Status in linux-gcp source package in Plucky:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  Google requested the IDPF driver be changed from a built-in module to
  a loadable module in the linux-modules package.

  [Fix]

  Add drivers/net/ethernet/intel/idpf/* to the inclusion-list and change
  CONFIG_IDPF to build the driver as a loadable module rather than a
  built-in.

  [Test Plan]

  List files in the linux-modules package and verify that idpf.ko is
  there.

  [Regression potential]

  The regression potential is very low since we are provably moving a
  module to linux-modules.

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


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

[Kernel-packages] [Bug 2093077] Re: Fix Mic Mute LED not working problem on Dell Tarako platform

This bug was fixed in the package firmware-sof - 2024.06-1ubuntu4

---
firmware-sof (2024.06-1ubuntu4) plucky; urgency=medium

  * Update sof-rpl-cs42l43-l0.tplg to fix Mic Mute LED. (LP: #2093077)
- Update v2.2.13 topology files for Intel platforms

 -- Chris Chiu   Tue, 07 Jan 2025 12:31:08
+0800

** Changed in: firmware-sof (Ubuntu Plucky)
   Status: New => Fix Released

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

Title:
  Fix Mic Mute LED not working problem on Dell Tarako platform

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  Fix Released
Status in firmware-sof source package in Noble:
  New
Status in firmware-sof source package in Oracular:
  New
Status in firmware-sof source package in Plucky:
  Fix Released

Bug description:
  [SRU Justifications]

  == firmware-sof ==

  [Impact]
  The mic-mute led not working on Dell Tarako laptops with Cirrus Audio Codec.

  [Fix]
  For firmware-sof, it required the updated sof-rpl-cs42l43-l0.tplg to remove 
the useless 'PGA5.0 5 Master Capture Switch' and 'PGA2.0 2 Master Capture 
Switch' for Mic Mute LED control

  [Test Case]
  1. install firmware-sof-signed with version >= 2023.12.1-1ubuntu1.4.
  2. press mic-mute hot-key and check if mic-mute LED is toggled correctly and 
aligned with the Mic-Mute status.

  [Where problems could occur]
  The topology only affects the particular Intel platforms with configuration 
which connects the cs42l43 codec on link #0 of soundwire. Should be low risk 
for regression.

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


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

[Kernel-packages] [Bug 2092222] Re: ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error

2025-01-09 Thread Juerg Haefliger

The fix you propose is a revert of 'ata: libata-scsi: Honor the D_SENSE
bit for CK_COND=1 and no error' but we don't have that commit in 6.8. In
fact that commit was added in 6.10.

It seems yours is a different problem. Has this worked correctly with
older Ubuntu kernels?

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

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

Title:
  ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I’m running Ubuntu 24.04.1 LTS (GNU/Linux 6.8.0-51-generic x86_64) as
  a guest system in Proxmox VE 8.3.2. I have connected a WD SATA-HDD via
  passthrough directly to the Ubuntu guest system. It is mountable and
  works flawlessly.

  However, I want it to spin down to “standby” state if it is not in
  use. So, I ran the “hdparm” command to check the current power mode
  status. The status of the SATA-HDD had been “idle” or “active” at this
  point:

  root@xyz:~# hdparm -C /dev/sdb

  /dev/sdb:
  SG_IO: bad/missing sense data, sb: 70 00 05 00 00 00 00 0a 00 00 00 00 20 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 drive state is: standby

  As you can see, “hdparm” threw an error and returned the wrong power
  mode state “standby”. I doublechecked by touching the SATA-HDD. It was
  spinning and the head was moving.

  After, I did some googling and found a post in the Majaro (sorry!) forum 
exactly matching this issue:
  
https://forum.manjaro.org/t/ata-libata-scsi-sense-data-errors-breaking-hdparm-with-wd-drives/166634/10

  The post also points out the solution - a kernel fix as part of the 
linux6.10.6-1 point release:
  
https://git.kernel.org/pub/scm/linux/kernel/git/libata/linux.git/commit/?id=fa0db8e5

  Now my request - Could you please add this fix also to one of the next point 
releases of Ubuntu 24.04.1 LTS’s “Linux 6.8.0-5x” kernel?
  I would really like to avoid introducing a “custom” kernel into my 
100%-standard Ubuntu LTS system.

  Thanks in advance!

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


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

[Kernel-packages] [Bug 2089891] Re: [SRU] Add audio rt713 and rt718 support on ThinkPad TM2

2025-01-09 Thread Timo Aaltonen

thanks Chris, I did actually release this for oracular too, but LP
oopsed when copying...

the other bugs were properly verified, and I missed that this one was
not :/

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

Title:
  [SRU] Add audio rt713 and rt718 support on ThinkPad TM2

Status in HWE Next:
  In Progress
Status in firmware-sof package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Noble:
  Fix Released
Status in linux source package in Noble:
  Invalid
Status in linux-oem-6.11 source package in Noble:
  Fix Released
Status in firmware-sof source package in Oracular:
  Fix Committed
Status in linux source package in Oracular:
  In Progress
Status in linux-oem-6.11 source package in Oracular:
  Invalid

Bug description:
  [Impact]
  There is no sound cards on Intel LNL platform of ThinkPad TM2.

  [Fix]
  Add soc-acpi table entry on LNL for ThinkPad TME laptop
  with rt713 and rt718.

  This kernel patch depends on new sof firmware:
  db771bf v2.11.x: add new 2.11.2 topology2 production binaries
  665e39d Add SOF v2.11.1 signed Intel binaries for MTL/LNL/ARL

  The sof-firmware will be SRU in bug 2086250

  [Test]
  Tested on hardware, audio input and output can work
  with the patch and new sof-firmware.

  $ cat /proc/asound/cards
   0 [sofsoundwire   ]: sof-soundwire - sof-soundwire
    LENOVO-21NTZCF5CN-ThinkPadX1CarbonGen13
  $ speaker-test -c 2
  $ arecord -f cd cd.wav

  [Where problems could occur]
  It may break audio on Intel LNL platform.

  The commit is from 6.12 kernel;
  LNL is only supported on 6.11+ kernel;
  So SRU for oem-6.11 and oracular only.

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


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

[Kernel-packages] [Bug 2092222] Re: ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error

2025-01-09 Thread phaze75

Ok, thanks for clarifying that!

Well, I had the WD SATA-HDD working correctly concerning its power mode
states. But the drive had been connected to a virtualized Win2000 server
passed through by an XCP-ng-XenServer environment. So, that can't be
really compared, aside from the "passthrough setup".

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

Title:
  ata: libata-scsi: Honor the D_SENSE bit for CK_COND=1 and no error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I’m running Ubuntu 24.04.1 LTS (GNU/Linux 6.8.0-51-generic x86_64) as
  a guest system in Proxmox VE 8.3.2. I have connected a WD SATA-HDD via
  passthrough directly to the Ubuntu guest system. It is mountable and
  works flawlessly.

  However, I want it to spin down to “standby” state if it is not in
  use. So, I ran the “hdparm” command to check the current power mode
  status. The status of the SATA-HDD had been “idle” or “active” at this
  point:

  root@xyz:~# hdparm -C /dev/sdb

  /dev/sdb:
  SG_IO: bad/missing sense data, sb: 70 00 05 00 00 00 00 0a 00 00 00 00 20 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 drive state is: standby

  As you can see, “hdparm” threw an error and returned the wrong power
  mode state “standby”. I doublechecked by touching the SATA-HDD. It was
  spinning and the head was moving.

  After, I did some googling and found a post in the Majaro (sorry!) forum 
exactly matching this issue:
  
https://forum.manjaro.org/t/ata-libata-scsi-sense-data-errors-breaking-hdparm-with-wd-drives/166634/10

  The post also points out the solution - a kernel fix as part of the 
linux6.10.6-1 point release:
  
https://git.kernel.org/pub/scm/linux/kernel/git/libata/linux.git/commit/?id=fa0db8e5

  Now my request - Could you please add this fix also to one of the next point 
releases of Ubuntu 24.04.1 LTS’s “Linux 6.8.0-5x” kernel?
  I would really like to avoid introducing a “custom” kernel into my 
100%-standard Ubuntu LTS system.

  Thanks in advance!

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


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

[Kernel-packages] [Bug 2073274] Autopkgtest regression report (wireless-regdb/2024.07.04-0ubuntu1~20.04.1)

2025-01-09 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted wireless-regdb 
(2024.07.04-0ubuntu1~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

linux-gcp-5.15/unknown (amd64)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#wireless-regdb

[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 wireless-regdb in Ubuntu.
https://bugs.launchpad.net/bugs/2073274

Title:
   2024.07.04 new upstream release

Status in wireless-regdb package in Ubuntu:
  Fix Released
Status in wireless-regdb source package in Trusty:
  Fix Committed
Status in wireless-regdb source package in Xenial:
  Fix Committed
Status in wireless-regdb source package in Bionic:
  Fix Committed
Status in wireless-regdb source package in Focal:
  Fix Committed
Status in wireless-regdb source package in Jammy:
  Fix Committed
Status in wireless-regdb source package in Noble:
  Fix Committed
Status in wireless-regdb source package in Oracular:
  Fix Released

Bug description:
  [Impact]

  New upstream release. This is a database of wireless regulations, and
  should updated in all releases to ensure users have the most up-to-
  date regulatory information.

  [Test Case]

  Following reboot after installing the new database, it should be
  possible to query and change the regulatory domain using 'iw reg get'
  and 'iw reg set'.

  [Where problems could occur]

  If crda (<< k4.15) or the kernel is unable to use the new database,
  users may be stuck using the default "world" regulatory domain which
  is quite restrictive, therefore they may be unable to use wireless
  channels that they were able to use previously. Regulatory rules may
  have also changed for the user's region, which could also make some
  channels unusable, but this would not be a bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/2073274/+subscriptions


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

[Kernel-packages] [Bug 2093338] Re: Keyboard not working after kernel upgrade

2025-01-09 Thread Julian Andres Klode

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

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

Title:
  Keyboard not working after kernel upgrade

Status in linux package in Ubuntu:
  New

Bug description:
  On 8.01.2024 I executed `apt upgrade` which upgraded by kernel version from 
6.8.0-41 to 6.8.0-51 and since then I'm not able to enter the encryption 
password on system boot.
  I try to type but no response on the UI.
  It works normally when I start my system with 6.8.0-41 kernel.

  ```
  No LSB modules are available.
  Description:Ubuntu 24.04.1 LTS
  Release:24.04

  6.8.0-41-generic #41-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug  2 20:41:06 UTC 2024 
x86_64 x86_64 x86_64 GNU/Linux
  ```

  
  ```plain
  Start-Date: 2025-01-08  08:40:29
  Commandline: apt upgrade
  Requested-By: anna (1000)
  Install: linux-modules-6.8.0-51-generic:amd64 (6.8.0-51.52, automatic), 
linux-image-6.8.0-51-generic:amd64 (6.8.0-51.52, automatic), 
linux-headers-6.8.0-51-generic:amd64 (6.8.0-51.52, automatic), 
linux-tools-6.8.0-51:amd64 (6.8.0-51.52, automatic), 
linux-tools-6.8.0-51-generic:amd64 (6.8.0-51.52, automatic), 
linux-headers-6.8.0-51:amd64 (6.8.0-51.52, automatic), 
linux-modules-extra-6.8.0-51-generic:amd64 (6.8.0-51.52, automatic)
  Upgrade: dmidecode:amd64 (3.5-3build1, 3.5-3ubuntu0.1), dmeventd:amd64 
(2:1.02.185-3ubuntu3, 2:1.02.185-3ubuntu3.1), libreoffice-calc:amd64 
(4:24.2.5-0ubuntu0.24.04.2, 4:24.2.7-0ubuntu0.24.04.1), 
initramfs-tools-core:amd64 (0.142ubuntu25.1, 0.142ubuntu25.4), libpulse0:amd64 
(1:16.1+dfsg1-2ubuntu10, 1:16.1+dfsg1-2ubuntu10.1), linux-tools-common:amd64 
(6.8.0-41.41, 6.8.0-51.52), krb5-locales:amd64 (1.20.1-6ubuntu2.1, 
1.20.1-6ubuntu2.2), python3.12:amd64 (3.12.3-1ubuntu0.1, 3.12.3-1ubuntu0.3), 
uno-libs-private:amd64 (4:24.2.5-0ubuntu0.24.04.2, 4:24.2.7-0ubuntu0.24.04.1), 
libreoffice-base-core:amd64 (4:24.2.5-0ubuntu0.24.04.2, 
4:24.2.7-0ubuntu0.24.04.1), libgssapi-krb5-2:amd64 (1.20.1-6ubuntu2.1, 
1.20.1-6ubuntu2.2), libglx-mesa0:amd64 (24.0.9-0ubuntu0.1, 24.0.9-0ubuntu0.3), 
linux-headers-generic:amd64 (6.8.0-41.41, 6.8.0-51.52), libaudit-common:amd64 
(1:3.1.2-2.1build1, 1:3.1.2-2.1build1.1), acl:amd64 (2.3.2-1build1, 
2.3.2-1build1.1), bubblewrap:amd64 (0.9.0-1build1, 0.9.0-1ubuntu0.1),
  libreoffice-uiconfig-impress:amd64 (4:24.2.5-0ubuntu0.24.04.2, 
4:24.2.7-0ubuntu0.24.04.1), libreoffice-core:amd64 (4:24.2.5-0ubuntu0.24.04.2, 
4:24.2.7-0ubuntu0.24.04.1), packagekit-tools:amd64 (1.2.8-2build3, 
1.2.8-2ubuntu1.1), software-properties-qt:amd64 (0.99.48.1, 0.99.49.1), 
libldap2:amd64 (2.6.7+dfsg-1~exp1ubuntu8, 2.6.7+dfsg-1~exp1ubuntu8.1), 
cryptsetup-bin:amd64 (2:2.7.0-1ubuntu4, 2:2.7.0-1ubuntu4.1), cups-bsd:amd64 
(2.4.7-1.2ubuntu7.2, 2.4.7-1.2ubuntu7.3), libacl1:amd64 (2.3.2-1build1, 
2.3.2-1build1.1), libglib2.0-bin:amd64 (2.80.0-6ubuntu3.1, 2.80.0-6ubuntu3.2), 
cups-common:amd64 (2.4.7-1.2ubuntu7.2, 2.4.7-1.2ubuntu7.3), 
python3-tornado:amd64 (6.4.0-1build1, 6.4.0-1ubuntu0.1), libldap-common:amd64 
(2.6.7+dfsg-1~exp1ubuntu8, 2.6.7+dfsg-1~exp1ubuntu8.1), 
gir1.2-gstreamer-1.0:amd64 (1.24.2-1, 1.24.2-1ubuntu0.1), 
xserver-xorg-core:amd64 (2:21.1.12-1ubuntu1, 2:21.1.12-1ubuntu1.1), 
gstreamer1.0-gl:amd64 (1.24.2-1ubuntu0.1, 1.24.2-1ubuntu0.2), 
libpipewire-0.3-common:amd64 (1.0.5
 -1ubuntu1, 1.0.5-1ubuntu2), pipewire-pulse:amd64 (1.0.5-1ubuntu1, 
1.0.5-1ubuntu2), libreoffice-uiconfig-math:amd64 (4:24.2.5-0ubuntu0.24.04.2, 
4:24.2.7-0ubuntu0.24.04.1), libreoffice-common:amd64 
(4:24.2.5-0ubuntu0.24.04.2, 4:24.2.7-0ubuntu0.24.04.1), 
libreoffice-uiconfig-writer:amd64 (4:24.2.5-0ubuntu0.24.04.2, 
4:24.2.7-0ubuntu0.24.04.1), libuno-sal3t64:amd64 (4:24.2.5-0ubuntu0.24.04.2, 
4:24.2.7-0ubuntu0.24.04.1), libheif1:amd64 (1.17.6-1ubuntu4, 
1.17.6-1ubuntu4.1), apport-kde:amd64 (2.28.1-0ubuntu3.1, 2.28.1-0ubuntu3.3), 
ure:amd64 (4:24.2.5-0ubuntu0.24.04.2, 4:24.2.7-0ubuntu0.24.04.1), vim:amd64 
(2:9.1.0016-1ubuntu7.1, 2:9.1.0016-1ubuntu7.5), gir1.2-glib-2.0:amd64 
(2.80.0-6ubuntu3.1, 2.80.0-6ubuntu3.2), libgbm1:amd64 (24.0.9-0ubuntu0.1, 
24.0.9-0ubuntu0.3), xxd:amd64 (2:9.1.0016-1ubuntu7.1, 2:9.1.0016-1ubuntu7.5), 
libheif-plugin-libde265:amd64 (1.17.6-1ubuntu4, 1.17.6-1ubuntu4.1), 
libexpat1:amd64 (2.6.1-2build1, 2.6.1-2ubuntu0.2), zip:amd64 (3.0-13build1, 
3.0-13ubuntu0.1), libfwupd
 2:amd64 (1.9.16-1, 1.9.27-0ubuntu1~24.04.1), ubuntu-drivers-common:amd64 
(1:0.9.7.6ubuntu3, 1:0.9.7.6ubuntu3.1), initramfs-tools-bin:amd64 
(0.142ubuntu25.1, 0.142ubuntu25.4), libpython3.12-minimal:amd64 
(3.12.3-1ubuntu0.1, 3.12.3-1ubuntu0.3), apparmor:amd64 
(4.0.1really4.0.0-beta3-0ubuntu0.1, 4.0.1really4.0.1-0ubuntu0.24.04.3), 
libgs10-common:amd64 (10.02.1~dfsg1-0ubuntu7.3, 10.02.1~dfsg1-0ubuntu7.4), 
firmware-sof-signed:amd64 (2023.12.1-1ubuntu1, 2023.12.1-1ubuntu1.3), 
cups-client:amd64 (2.4.7-1.2ubuntu7.2, 2.4.7-1.2ubuntu7.3), cups-ppdc:amd64 
(2.

[Kernel-packages] [Bug 2093338] [NEW] Keyboard not working after kernel upgrade