date:20240419

[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mutter (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [nvidia] Second (external) monitor not active after screen lock in
  Xorg

Status in mutter package in Ubuntu:
  Expired
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Expired

Bug description:
  After switching back to Xorg, I have encountered the issue with the
  second (external) monitor - after the screen is locked and I unlock
  it, the second monitor either shows a blank black screen or is not
  even active in Display settings. It's like the configuration is lost
  during lock/unclock process.

  I am using USB-C to HDMI cable with the second screen and Xorg as
  display manager.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 13 12:53:24 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:24dc] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[17aa:3a58]
  InstallationDate: Installed on 2024-01-12 (32 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=9943bf1f-3749-4bb4-89b5-33eeb86f8afc ro quiet splash 
amd_pstate=guided vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2023
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN64WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K17763 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.64
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN64WW:bd12/07/2023:br1.64:efr1.64:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2053019] Re: [nvidia] Second (external) monitor not active after screen lock in Xorg

[Expired for nvidia-graphics-drivers-535 (Ubuntu) because there has been
no activity for 60 days.]

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

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

Title:
  [nvidia] Second (external) monitor not active after screen lock in
  Xorg

Status in mutter package in Ubuntu:
  Expired
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Expired

Bug description:
  After switching back to Xorg, I have encountered the issue with the
  second (external) monitor - after the screen is locked and I unlock
  it, the second monitor either shows a blank black screen or is not
  even active in Display settings. It's like the configuration is lost
  during lock/unclock process.

  I am using USB-C to HDMI cable with the second screen and Xorg as
  display manager.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 13 12:53:24 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:24dc] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[17aa:3a58]
  InstallationDate: Installed on 2024-01-12 (32 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=9943bf1f-3749-4bb4-89b5-33eeb86f8afc ro quiet splash 
amd_pstate=guided vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2023
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN64WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K17763 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.64
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN64WW:bd12/07/2023:br1.64:efr1.64:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2054181] Re: Monitor Not Detected when Connected to Belkin Docking Station via DisplayPort on Ubuntu

[Expired for linux-hwe-6.5 (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: linux-hwe-6.5 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Monitor Not Detected when Connected to Belkin Docking Station via
  DisplayPort on Ubuntu

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

Bug description:
  Dear Ubuntu Bug Tracking Team,

  I hope this message finds you well. I am writing to report an issue I
  have encountered while using Ubuntu.

  Issue Description:
  When connecting my BenQ monitor to a Belkin docking station via DisplayPort, 
Ubuntu fails to detect the monitor. Other monitor connected to same docking 
station via hdmi is working

  
  Thank you for your attention to this matter.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 17 12:33:13 2024
  DistUpgraded: 2022-09-23 16:50:19,545 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: nct6687d/20240204-15, 6.5.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo CometLake-U GT2 [UHD Graphics] [17aa:22ac]
  InstallationDate: Installed on 2020-06-01 (1355 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20SDCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=b6e3b307-fcfb-4b70-ba21-5b72784f279c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to jammy on 2022-09-23 (511 days ago)
  dmi.bios.date: 07/17/2023
  dmi.bios.release: 1.25
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2SET31W (1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2SET31W(1.25):bd07/17/2023:br1.25:efr1.6:svnLENOVO:pn20SDCTO1WW:pvrThinkPadX390:rvnLENOVO:rn20SDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20SD_BU_Think_FM_ThinkPadX390:
  dmi.product.family: ThinkPad X390
  dmi.product.name: 20SDCTO1WW
  dmi.product.sku: LENOVO_MT_20SD_BU_Think_FM_ThinkPad X390
  dmi.product.version: ThinkPad X390
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2060378] Re: ubuntu stuck at every day

2024-04-19 Thread Seth Arnold

Hello, input/output errors like this are usually an indicator of failing
hardware. Make sure your backups are in good working order, and make
sure you don't overwrite backups with bad data.

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

Title:
  ubuntu stuck at every day

Status in linux package in Ubuntu:
  New

Bug description:
  Whenever I open my laptop and start working, after some time ,
  everything will stuck at a point and if i want to open any application
  then say

  "failed to launch "application name" 
   failed to execute child process 
"/usr/lib/*86_64-linux/gnu/glib-2.0/gio-launch-desktop" (input/output error)"

  this things automatically starts happening for all the applications
  (terminal and all application ). and this happens every day And the
  laptop stops working. Even the laptop doesn't turn off. i forcefully
  close the laptop ( i already make 30gb swap partition) . and when i
  hover on anything , my cursor look like square

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


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

[Kernel-packages] [Bug 2062412] Re: No input through internal microphone (Ryzen 6000)

2024-04-19 Thread blszyn

Commit b44a34f581b0 applies to type 21J2 but Lenovo Thinkpad P14s (AMD)
Gen 4 is type 21K5.

Mario - you commented on a commit regarding type 21K5 here

https://lore.kernel.org/lkml/cbf8ac6f-5e8d-4430-aba7-853cded5a...@michaelkloos.com/T/

Should 21K5 be included in the Quirks List?

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

Title:
  No input through internal microphone (Ryzen 6000)

Status in linux package in Ubuntu:
  New

Bug description:
  The microphone in a Thinkpad P14S (AMD) Gen 4 stopped working after
  updating from 23.10 to 24.04 Beta with kernel 6.8.0-22-generic. This
  is a known problem and a patch may be included in kernel 6.8.3.

  Is it possible to backport this patch? Or is the plan to wait for a
  kernel update? It would be good use the microphone in 24.04.

  The symptoms are exactly as described in
  https://bbs.archlinux.org/viewtopic.php?pid=2162297#p2162297

  Reportedly the patch is included in
  
https://github.com/zen-kernel/zen-kernel/blob/6.7/main/sound/soc/amd/yc/acp6x-mach.c#L59

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


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

[Kernel-packages] [Bug 2049793] Re: [MTL] x86: Fix Cache info sysfs is not populated

2024-04-19 Thread Bun K Tan

https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/noble/commit/?id=95dc0f6212b9eb8769fb40b2359a0a61cfac8494

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

Title:
  [MTL] x86: Fix Cache info sysfs is not populated

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Noble:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  The interface /sys/devices/system/cpu/cpuX/cache is broken (not populated) if
  CPUs have different numbers of subleaves in CPUID 4. This is the case of Intel
  Meteor Lake.

  [Fix]

  
https://lore.kernel.org/all/2023121519.12834-1-ricardo.neri-calde...@linux.intel.com/
  Reviewed, but probably will only land in v6.9.

  [Test Case]

  Check existence of cpu cache info:

$ ls /sys/devices/system/cpu/cpu0/cache/
index0 index1 index2 index3 uevent

  [Where problems could occur]

  This populates sysfs entries that should have been available, not
  something new or alters existing interface.

  [Other Info]

  While this is targets v6.8 for Intel LPMD (Low Power Model Daemon)'s
  use, only Noble and Unstable will be nominated for fix.

  == original bug report ==

  [Description]
    The interface /sys/devices/system/cpu/cpu*/cache is empty. In Meteorlake, 
not all CPUs have the same number of subleaves in the CPUID 4 leaf. The compute 
die CPUs have 3 subleaves whereas the CPUs in the SoC die have 2. This problem 
happens because Linux assumes that all CPUs have the same number of subleaves.

  [Hardware Information]
    Architecture:
  Intel / AMD (x86_64)
    Platform(s):
  Meteor Lake
    Date HW is expected at Canonical:

    Component(s):
  x86

  [Software Information]
    Target Version:
  24.04
    Target Kernel:
  6.8
    Commit IDs:
  TBD
    External Links:
  
https://lore.kernel.org/all/2023121519.12834-5-ricardo.neri-calde...@linux.intel.com/

  [Business Justification]

  [Testing guidance]

  [External ID]
    LFE-6901

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


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

[Kernel-packages] [Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

Partial review of the Jammy debdiff.
(Still in progress.)

Started with Jammy's patches 0012-0036, which are Mantic's patches 0001-0024 
(already reviewed).
Most patches are identical, and some have context-line changes, as expected 
(8.0.2/8.0.0 delta).
Just had a few changes.

$ for ((i=1; i<=24; i++)); do 
echo "PATCH $i"
echo
diff -U0 \
  mantic/crash-8.0.2/debian/patches/lp2038249-$(printf '%04d' $i)-*.patch \
  jammy/crash-8.0.0/debian/patches/lp2038249-$(printf '%04d' 
$((i+12)))-*.patch
echo
  done 2>&1 | less

patch 13
actually a backport, context line changes

patch 4
likewise

patch 8
augment backport notes

patch 11
actually a backport, context line changes, more
indentation issue, fixed

patch 36 (same note as patch 24/mantic)

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Jammy:
  In Progress
Status in crash source package in Lunar:
  Won't Fix
Status in crash source package in Mantic:
  In Progress
Status in crash source package in Noble:
  Fix Released

Bug description:
  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==

  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==

  In 8.0.1:
  - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB

  In 8.0.2:
  - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing

  In 8.0.3:
  - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later

  In 8.0.4
  - 7750e61fdb2a Support module memory layout change on Linux 6.4
  - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  - 4ee56105881d Fix compilation error due to new strlcpy function that glibc  
added

  ==

  [Test Plan]

  On Jammy (LTS), which provides HWE (6.5) and GA (5.15) kernels,
  perform testing on both HWE (verify fixes) and GA (verify no regressions).

  There are detailed/per-commit test plans in the attachments:
  `crash_jammy_test_plan.txt.txt` and `crash_lunar_test_plan.txt`.

  And the general sysrq-trigger/makedumpfile/crash test:

  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll 
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  3. To trigger a crash dump forcefully, execute the `echo c | sudo tee 
/proc/sysrq-trigger` command.
  4. Download the kernel .ddeb file, which will be used for analyzing the dump 
file.
  # sudo -i
  # cd /var/crash
  # pull-lp-ddebs linux-image-unsigned-$(uname -r)
  # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
  5. Utilize the "crash" utility to parse and analyze the dump file.
  crash 8.0.0
  Copyright (C) 2002-2021  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C)

[Kernel-packages] [Bug 2060727] Re: The keyboard does not work after latest kernel update

2024-04-19 Thread James Fox

The fix hasn't been released yet.

"Fix Committed" status means the source has been updated but hasn't been
released in a package.

"Fix Released" status means the new package has the fix.

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

Title:
  The keyboard does not work after latest kernel update

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not
  work after the latest kernel update and its subsequent reboot of the
  laptop. Nothing else is connected to the laptop.

  --

  In /var/log/apt/history.log , the latest we can see is:

  Start-Date: 2024-04-09  12:37:28
  Commandline: apt full-upgrade
  Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), 
linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic)
  Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), 
linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 
(6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28)
  End-Date: 2024-04-09  12:37:51

  --

  $ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.10
  Release:23.10

  $ # Note: It's Kubuntu 23.10

  --

  $ uname -a
  Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 18:21:00 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  SRU Justification:
  ==
  [Impact]
  Keyboard is lost after updated to 6.5.0-27 and oem-6.5-1019 kernel
  versions.

  [Fix]
  Regression commit is found commit:
  936e4d49ecbc ("Input: atkbd - skip ATKBD_CMD_GETID in translated mode")

  Fixes:
  9cf6e24c9fbf1 Input: atkbd - do not skip atkbd_deactivate() when
  skipping ATKBD_CMD_GETID
  683cd8259a9b8 Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping
  ATKBD_CMD_GETID

  [Test]
  Tested on hardware, keyboard works fine after bootup.

  The regression commit is only in 6.5 stable, so SRU for 6.5 only.

  [Where problems could occur]
  It may break keyboard.

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


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

[Kernel-packages] [Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

Today, I tackled the Mantic debdiff (made only a few changes; below).

It's now currently building in a PPA for all supported architectures,
(ppa:mfo/lp2038249) and if all goes well I will upload it to Mantic.

Thanks!
Mauricio

---

All 24 commits are included in Noble (12 in 8.0.4 and 12 in 8.0.3).
changelog OK
DEP3 tags OK

I reviewed each commit, with the exception of the big code additions
(patches 8,16: for maple tree and module memory layout): all look OK.

I fixed up patch 24, which is originally 2 trivial and short changes,
but had like ~3800 lines of indentation/formatting changes included
(certainly this wasn't intented, and mistakes happen; so I fixed it).

$ git show 55a43bcefa20161c7e56ed0e309e90e941f47efc | wc -l
57

$ wc -l 
debian/patches/lp2038249-0024-Fix-compilation-error-and-warning-with-gcc-4.8.5.patch
3865 
debian/patches/lp2038249-0024-Fix-compilation-error-and-warning-with-gcc-4.8.5.patch

We can all learn from this -- I will check .patch files with diffstat!

I also just augmented backport notes (thanks for those) to indicate
which functions/hunks had context lines modified/adjusted/refreshed,
since the patch is big (patch 15), and clarify variables (not) used.

-+[chengen - modify x86_64.c context]
++[chengen - modify context in x86_64.c: x86_64_ORC_init() and 
x86_64_get_framesize()]

-+[chengen - initialize init_tss to zero in xen_hyper.c]
++[chengen - initialize only init_tss to zero in xen_hyper.c (there is 
no stack_base yet)]

Very importantly, the detailed test plan will be key to validate the
changes are working correctly, considering their number and size.
Thanks again for it!

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Jammy:
  In Progress
Status in crash source package in Lunar:
  Won't Fix
Status in crash source package in Mantic:
  In Progress
Status in crash source package in Noble:
  Fix Released

Bug description:
  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==

  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==

  In 8.0.1:
  - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB

  In 8.0.2:
  - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing

  In 8.0.3:
  - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later

  In 8.0.4
  - 7750e61fdb2a Support module memory layout change on Linux 6.4
  - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  - 4ee56105881d Fix compilation error due to new strlcpy function that glibc  
added

  ==

  [Test Plan]

  On Jammy (LTS), which provides HWE (6.5) and GA (5.15) kernels,
  perform testing on both HWE (verify fixes) and GA (verify no regressions).

  There are detailed/per-commit test plans in the attachments:
  `crash_jammy_test_plan.txt.txt` and `crash_lunar_test_plan.txt`.

  And the general sysrq-trigger/makedumpfile/crash test:

  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p

[Kernel-packages] [Bug 1991130] Re: Add lrm autogenerated transitional independent of variants

This bug was fixed in the package linux-restricted-modules - 6.8.0-28.28

---
linux-restricted-modules (6.8.0-28.28) noble; urgency=medium

  * Main version: 6.8.0-28.28

  * Packaging resync (LP: #1786013)
- [Packaging] debian/tracking-bug -- resync from main package

 -- Paolo Pisati   Tue, 16 Apr 2024 19:03:14
+0200

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

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

Title:
  Add lrm autogenerated transitional independent of variants

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in linux-restricted-modules-hwe-5.15 package in Ubuntu:
  Invalid
Status in linux-restricted-modules-hwe-5.19 package in Ubuntu:
  Invalid
Status in linux-restricted-modules source package in Focal:
  Invalid
Status in linux-restricted-modules-hwe-5.15 source package in Focal:
  Fix Released
Status in linux-restricted-modules-hwe-5.19 source package in Focal:
  Invalid
Status in linux-restricted-modules source package in Jammy:
  Invalid
Status in linux-restricted-modules-hwe-5.15 source package in Jammy:
  Invalid
Status in linux-restricted-modules-hwe-5.19 source package in Jammy:
  In Progress
Status in linux-restricted-modules source package in Lunar:
  Invalid
Status in linux-restricted-modules-hwe-5.15 source package in Lunar:
  Invalid
Status in linux-restricted-modules-hwe-5.19 source package in Lunar:
  Invalid
Status in linux-restricted-modules source package in Mantic:
  New
Status in linux-restricted-modules-hwe-5.15 source package in Mantic:
  Invalid
Status in linux-restricted-modules-hwe-5.19 source package in Mantic:
  Invalid

Bug description:
  [Impact]

  The kernel lrm packages have a mechanism to auto-generate transitional
  packages by adding a line to 'debian/package.config' in the following
  format

  transitional   

  Example:

  transitional 450-oem-20.04 450-generic amd64

  When being processed by 'debian/scripts/gen-rules.lrm' the
  autogenerated contents are added to 'debian/control.d/transitionals-
  local'. However, this file is not included in the final
  'debian/control' for packages which does not contain the default
  variant '--' (see debian/rules.in). This is intentional to prevent
  unwanted transitionals.

  However, there are some cases where we want to transition packages to
  kernels which are not the default variant in a series (e.g. hwe
  kernels).

  [Fix]

  The proposed fix is to add a new command "migrate", which does exactly
  what "transitional" does but adding the content to
  'debian/control.d/migrate-local' which would get added to the final
  'debian/control' independently of the source's variants.

  [Test Case]

  Add "migrate" entries to 'debian/package.config' and check whether
  they get added to 'debian/control' even for non default variant
  packages.

  [Where problems could occur]

  If not used correctly, unwanted transitionals could be generated
  causing issues to the archive. However, this is a new command and
  should not impact any of the previously set transitionals and it needs
  to be explicitly used.

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


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

[Kernel-packages] [Bug 2046315] Re: panel flickering after the i915.psr2 is enabled

This bug was fixed in the package linux-oem-6.8 - 6.8.0-1004.4

---
linux-oem-6.8 (6.8.0-1004.4) noble; urgency=medium

  * noble/linux-oem-6.8: 6.8.0-1004.4 -proposed tracker (LP: #2062020)

  * panel flickering after the i915.psr2 is enabled (LP: #2046315)
- drm/i915/alpm: Add ALPM register definitions
- drm/i915/psr: Add alpm_parameters struct
- drm/i915/alpm: Calculate ALPM Entry check
- drm/i915/alpm: Alpm aux wake configuration for lnl
- drm/i915/display: Make intel_dp_aux_fw_sync_len available for PSR code
- drm/i915/psr: Improve fast and IO wake lines calculation
- drm/i915/psr: Calculate IO wake and fast wake lines for DISPLAY_VER < 12
- drm/i915/display: Increase number of fast wake precharge pulses

  * Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- [Packaging] update update.conf
- debian.oem/dkms-versions -- update from kernel-versions (main/d2024.04.04)

  * intel_rapl_common: Add support for ARL and LNL (LP: #2061953)
- powercap: intel_rapl: Add support for Lunar Lake-M paltform
- powercap: intel_rapl: Add support for Arrow Lake

  [ Ubuntu: 6.8.0-28.28 ]

  * noble/linux: 6.8.0-28.28 -proposed tracker (LP: #2061867)
  * linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor
profiles/features (LP: #2061851)
- SAUCE: apparmor4.0.0 [92/90]: fix address mapping for recvfrom

  [ Ubuntu: 6.8.0-25.25 ]

  * noble/linux: 6.8.0-25.25 -proposed tracker (LP: #2061083)
  * Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
  (main/d2024.04.04)
  * Apply mitigations for the native BHI hardware vulnerabilty (LP: #2060909)
- x86/cpufeatures: Add new word for scattered features
- x86/bugs: Change commas to semicolons in 'spectre_v2' sysfs file
- x86/syscall: Don't force use of indirect calls for system calls
- x86/bhi: Add support for clearing branch history at syscall entry
- x86/bhi: Define SPEC_CTRL_BHI_DIS_S
- x86/bhi: Enumerate Branch History Injection (BHI) bug
- x86/bhi: Add BHI mitigation knob
- x86/bhi: Mitigate KVM by default
- KVM: x86: Add BHI_NO
- x86: set SPECTRE_BHI_ON as default
- [Config] enable spectre_bhi=auto by default
  * update apparmor and LSM stacking patch set (LP: #2028253)
- SAUCE: apparmor4.0.0 [01/90]: LSM stacking v39: integrity: disassociate
  ima_filter_rule from security_audit_rule
- SAUCE: apparmor4.0.0 [02/90]: LSM stacking v39: SM: Infrastructure
  management of the sock security
- SAUCE: apparmor4.0.0 [03/90]: LSM stacking v39: LSM: Add the lsmblob data
  structure.
- SAUCE: apparmor4.0.0 [04/90]: LSM stacking v39: IMA: avoid label 
collisions
  with stacked LSMs
- SAUCE: apparmor4.0.0 [05/90]: LSM stacking v39: LSM: Use lsmblob in
  security_audit_rule_match
- SAUCE: apparmor4.0.0 [06/90]: LSM stacking v39: LSM: Add lsmblob_to_secctx
  hook
- SAUCE: apparmor4.0.0 [07/90]: LSM stacking v39: Audit: maintain an lsmblob
  in audit_context
- SAUCE: apparmor4.0.0 [08/90]: LSM stacking v39: LSM: Use lsmblob in
  security_ipc_getsecid
- SAUCE: apparmor4.0.0 [09/90]: LSM stacking v39: Audit: Update shutdown LSM
  data
- SAUCE: apparmor4.0.0 [10/90]: LSM stacking v39: LSM: Use lsmblob in
  security_current_getsecid
- SAUCE: apparmor4.0.0 [11/90]: LSM stacking v39: LSM: Use lsmblob in
  security_inode_getsecid
- SAUCE: apparmor4.0.0 [12/90]: LSM stacking v39: Audit: use an lsmblob in
  audit_names
- SAUCE: apparmor4.0.0 [13/90]: LSM stacking v39: LSM: Create new
  security_cred_getlsmblob LSM hook
- SAUCE: apparmor4.0.0 [14/90]: LSM stacking v39: Audit: Change context data
  from secid to lsmblob
- SAUCE: apparmor4.0.0 [15/90]: LSM stacking v39: Netlabel: Use lsmblob for
  audit data
- SAUCE: apparmor4.0.0 [16/90]: LSM stacking v39: LSM: Ensure the correct 
LSM
  context releaser
- SAUCE: apparmor4.0.0 [17/90]: LSM stacking v39: LSM: Use lsmcontext in
  security_secid_to_secctx
- SAUCE: apparmor4.0.0 [18/90]: LSM stacking v39: LSM: Use lsmcontext in
  security_lsmblob_to_secctx
- SAUCE: apparmor4.0.0 [19/90]: LSM stacking v39: LSM: Use lsmcontext in
  security_inode_getsecctx
- SAUCE: apparmor4.0.0 [20/90]: LSM stacking v39: LSM: Use lsmcontext in
  security_dentry_init_security
- SAUCE: apparmor4.0.0 [21/90]: LSM stacking v39: LSM:
  security_lsmblob_to_secctx module selection
- SAUCE: apparmor4.0.0 [22/90]: LSM stacking v39: Audit: Create audit_stamp
  structure
- SAUCE: apparmor4.0.0 [23/90]: LSM stacking v39: Audit: Allow multiple
  records in an audit_buffer
- SAUCE: apparmor4.0.0 [24/90]: LSM stacking v39: Audit: Add record for
  multiple task security contexts
- SAUCE: apparmor4.0.0 [25/90]: LSM stacking v39: audit: multiple subject 
lsm
  values for netlabel

[Kernel-packages] [Bug 2049793] Re: [MTL] x86: Fix Cache info sysfs is not populated

This bug was fixed in the package linux - 6.8.0-28.28

---
linux (6.8.0-28.28) noble; urgency=medium

  * noble/linux: 6.8.0-28.28 -proposed tracker (LP: #2061867)

  * linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor
profiles/features (LP: #2061851)
- SAUCE: apparmor4.0.0 [92/90]: fix address mapping for recvfrom

 -- Paolo Pisati   Tue, 16 Apr 2024 18:29:17
+0200

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

Title:
  [MTL] x86: Fix Cache info sysfs is not populated

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Noble:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  The interface /sys/devices/system/cpu/cpuX/cache is broken (not populated) if
  CPUs have different numbers of subleaves in CPUID 4. This is the case of Intel
  Meteor Lake.

  [Fix]

  
https://lore.kernel.org/all/2023121519.12834-1-ricardo.neri-calde...@linux.intel.com/
  Reviewed, but probably will only land in v6.9.

  [Test Case]

  Check existence of cpu cache info:

$ ls /sys/devices/system/cpu/cpu0/cache/
index0 index1 index2 index3 uevent

  [Where problems could occur]

  This populates sysfs entries that should have been available, not
  something new or alters existing interface.

  [Other Info]

  While this is targets v6.8 for Intel LPMD (Low Power Model Daemon)'s
  use, only Noble and Unstable will be nominated for fix.

  == original bug report ==

  [Description]
    The interface /sys/devices/system/cpu/cpu*/cache is empty. In Meteorlake, 
not all CPUs have the same number of subleaves in the CPUID 4 leaf. The compute 
die CPUs have 3 subleaves whereas the CPUs in the SoC die have 2. This problem 
happens because Linux assumes that all CPUs have the same number of subleaves.

  [Hardware Information]
    Architecture:
  Intel / AMD (x86_64)
    Platform(s):
  Meteor Lake
    Date HW is expected at Canonical:

    Component(s):
  x86

  [Software Information]
    Target Version:
  24.04
    Target Kernel:
  6.8
    Commit IDs:
  TBD
    External Links:
  
https://lore.kernel.org/all/2023121519.12834-5-ricardo.neri-calde...@linux.intel.com/

  [Business Justification]

  [Testing guidance]

  [External ID]
    LFE-6901

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


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

[Kernel-packages] [Bug 2059147] Re: New upstream relase 535.171.04

This bug was fixed in the package nvidia-graphics-drivers-535 -
535.171.04-0ubuntu2

---
nvidia-graphics-drivers-535 (535.171.04-0ubuntu2) noble; urgency=medium

  * remove 
debian/dkms_nvidia/patches/buildfix_kernel_6.8-nv_drm_ioctls-DRM_UNLOCKED-is-now-the-default-behavi.patch
  * remove debian/dkms_nvidia/patches/buildfix_kernel_6.8-gpl-pfn_valid.patch
  * remove 
debian/open-kernel/patches/buildfix_kernel_6.8-nv_drm_ioctls-DRM_UNLOCKED-is-now-the-default-behavi.patch
  * remove debian/open-kernel/patches/buildfix_kernel_6.8-gpl-pfn_valid.patch

 -- Bartlomiej Zolnierkiewicz 
Wed, 27 Mar 2024 14:45:04 +0100

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

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

Title:
  New upstream relase 535.171.04

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  Fix Released

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

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

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

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

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

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

  [Discussion]

  [Changelog]

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


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

[Kernel-packages] [Bug 2056475] Re: aws: Backport latest ENA driver in upstream Linux to enable IRQ moderation

This bug was fixed in the package linux-aws - 6.8.0-1006.6

---
linux-aws (6.8.0-1006.6) noble; urgency=medium

  * noble/linux-aws: 6.8.0-1006.6 -proposed tracker (LP: #2061868)

  * Rebase on 6.8.0-28.28

 -- Andrea Righi   Tue, 16 Apr 2024 19:26:16
+0200

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

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

Title:
  aws: Backport latest ENA driver in upstream Linux to enable IRQ
  moderation

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Focal:
  Fix Released
Status in linux-aws source package in Jammy:
  Fix Released
Status in linux-aws source package in Mantic:
  Fix Released
Status in linux-aws source package in Noble:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

  In Ubuntu AMIs for x86 and Graviton based EC2 instances, the standard
  Ubuntu AMI comes without IRQ moderation enabled for ENA, which for our
  latest generation instances with networking heavy workloads is up to a
  25% performance regression (i.e. NGINX in a load-balancing
  configuration).

  
  [Fix]

  
  The mainline Linux kernel will now support IRQ moderation by default for ENA 
in the 6.9 kernel release via this patch: 
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/ethernet/amazon/ena?id=50d7a2660579889fba28b7e4543d4ce85aa2311b

  [Test Plan]

  AWS tested

  [Where problems could occur]

  By enabling adaptive coalescing, the default interrupt behaviour will
  by changed to be more adaptive, which shows improvements on heavy
  network workloads, but my change the behaviour and performance on
  other network workloads differently.   Rather than handling the
  interrupts based off of a fixed amount of time elapsed, it will change
  to an adaptive based approach.   There should be no negative impact on
  light workloads, and a positive impact on heavy work loads.  If there
  is an impact though, this option can be disabled via the ethtool
  command.

  [Other Info]

  SF: 00380449

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


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

[Kernel-packages] [Bug 2052469] Re: Provide an arm64 linux-oracle 64k kernel variant

This bug was fixed in the package linux-oracle - 6.8.0-1004.4

---
linux-oracle (6.8.0-1004.4) noble; urgency=medium

  * noble/linux-oracle: 6.8.0-1004.4 -proposed tracker (LP: #2061873)

  * Rebase on Ubuntu-6.8.0-28.28

 -- Paolo Pisati   Tue, 16 Apr 2024 19:36:13
+0200

** Changed in: linux-oracle (Ubuntu Noble)
   Status: In Progress => Fix Released

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

Title:
  Provide an arm64 linux-oracle 64k kernel variant

Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-oracle-6.5 package in Ubuntu:
  Invalid
Status in linux-oracle source package in Jammy:
  Invalid
Status in linux-oracle-6.5 source package in Jammy:
  Fix Released
Status in linux-oracle source package in Mantic:
  Fix Released
Status in linux-oracle-6.5 source package in Mantic:
  Invalid
Status in linux-oracle source package in Noble:
  Fix Released
Status in linux-oracle-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]

  * Oracle requested 64k page size flavour.

  [Fix]

  * Add flavour and configs for 64k flavour

  [Test Case]

  * Compile tested
  * Boot tested

  [Where things could go wrong]

  * Low chance of regression. Isolated logic fix.

  [Other Info]

  * SF #00377602

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


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

[Kernel-packages] [Bug 2060909] Re: Apply mitigations for the native BHI hardware vulnerabilty

This bug was fixed in the package linux - 6.8.0-28.28

---
linux (6.8.0-28.28) noble; urgency=medium

  * noble/linux: 6.8.0-28.28 -proposed tracker (LP: #2061867)

  * linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor
profiles/features (LP: #2061851)
- SAUCE: apparmor4.0.0 [92/90]: fix address mapping for recvfrom

 -- Paolo Pisati   Tue, 16 Apr 2024 18:29:17
+0200

** Changed in: linux (Ubuntu Noble)
   Status: Fix Committed => 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/2060909

Title:
  Apply mitigations for the native BHI hardware vulnerabilty

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

Bug description:
  [Impact]

  Branch History Injection (BHI) attacks may allow a malicious
  application to influence indirect branch prediction in kernel by
  poisoning the branch history. eIBRS isolates indirect branch targets
  in ring0.

  The BHB can still influence the choice of indirect branch predictor
  entry, and although branch predictor entries are isolated between
  modes when eIBRS is enabled, the BHB itself is not isolated between
  modes.

  Previously the only known real-world BHB attack vector was via
  unprivileged eBPF. Further research has found attacks that don't
  require unprivileged eBPF.

  See also:
  https://www.phoronix.com/news/Linux-BHI-Branch-History-Inject

  [Test case]

  https://www.vusec.net/projects/native-bhi/

  [Fix]

  Backport from upstream the merge that introduces spectre_bhi= boot
  option to control BHI mitigation:

   2bb69f5fc721 ("Merge tag 'nativebhi' of 
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip")
   ed2e8d49b54d ("KVM: x86: Add BHI_NO")
   95a6ccbdc719 ("x86/bhi: Mitigate KVM by default")
   ec9404e40e8f ("x86/bhi: Add BHI mitigation knob")
   be482ff95009 ("x86/bhi: Enumerate Branch History Injection (BHI) bug")
   0f4a837615ff ("x86/bhi: Define SPEC_CTRL_BHI_DIS_S")
   7390db8aea0d ("x86/bhi: Add support for clearing branch history at syscall 
entry")
   1e3ad78334a6 ("x86/syscall: Don't force use of indirect calls for system 
calls")
   0cd01ac5dcb1 ("x86/bugs: Change commas to semicolons in 'spectre_v2' sysfs 
file")

  Also set spectre_bhi=auto by default, that will rely on the BHI_DIS_S
  hardware control if it's available on the system CPUs, otherwise a
  proper software sequence will be executed at VMexit.

  NOTE: we may get these changes via stable update in 6.8, when that
  happens we can drop this backport and apply the patch set like any
  other regular stable update.

  [Regression potential]

  We may experience performance regressions with this new mitigation
  enabled, especially in VMs and CPUs that don't have the BHI hardware
  support capability (due to the extra software sequence executed at
  VMexit).

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


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

[Kernel-packages] [Bug 2061851] Re: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor profiles/features

This bug was fixed in the package linux - 6.8.0-28.28

---
linux (6.8.0-28.28) noble; urgency=medium

  * noble/linux: 6.8.0-28.28 -proposed tracker (LP: #2061867)

  * linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor
profiles/features (LP: #2061851)
- SAUCE: apparmor4.0.0 [92/90]: fix address mapping for recvfrom

 -- Paolo Pisati   Tue, 16 Apr 2024 18:29:17
+0200

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

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

Title:
  linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new
  apparmor profiles/features

Status in chrony package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-ibm package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New
Status in chrony source package in Noble:
  Invalid
Status in linux source package in Noble:
  Fix Released
Status in linux-aws source package in Noble:
  New
Status in linux-azure source package in Noble:
  New
Status in linux-gcp source package in Noble:
  New
Status in linux-ibm source package in Noble:
  New
Status in linux-oracle source package in Noble:
  New
Status in snapd source package in Noble:
  New

Bug description:
  * Canonical Public Cloud discovered that `chronyc -c sources` now fails with 
`506 Cannot talk to daemon` with the latest kernels. We are seeing this in 
linux-azure and linux-gcp kernels (6.8.0-1005.5)
  * Disabling AppArmor (`sudo systemctl stop apparmor`) completely results in 
no regression and `chronyc -c sources` returns as expected
  * Disabling the apparmor profile for `chronyd` only results in no regression 
and `chronyc -c sources` returns as expected
  * There are zero entries in dmesg when this occurs
  * There are zero entries in dmesg when this occurs if the  apparmor profile 
for `chronyd` is placed in complain mode instead of enforce mode
  * We changed the time server from the internal GCP metadata.google.internal 
to the ubuntu time server ntp.ubuntu.com with no change in behaviour

  
  We also noted issues with DNS resolution in snaps like `google-cloud-cli` in 
GCE images. 

  * Disabling apparmor completely for snaps too (`sudo systemctl stop
  snapd.apparmor`) results in no regression and calling the snaps
  returns as expected.

  
  The same issues are present in azure kernel `linux-azure` `6.8.0-1005.5` and 
the -proposed `6.8.0-25.25` generic kernel. 

  This is a release blocker for Noble release

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


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

[Kernel-packages] [Bug 2061953] Re: intel_rapl_common: Add support for ARL and LNL

This bug was fixed in the package linux-oem-6.8 - 6.8.0-1004.4

---
linux-oem-6.8 (6.8.0-1004.4) noble; urgency=medium

  * noble/linux-oem-6.8: 6.8.0-1004.4 -proposed tracker (LP: #2062020)

  * panel flickering after the i915.psr2 is enabled (LP: #2046315)
- drm/i915/alpm: Add ALPM register definitions
- drm/i915/psr: Add alpm_parameters struct
- drm/i915/alpm: Calculate ALPM Entry check
- drm/i915/alpm: Alpm aux wake configuration for lnl
- drm/i915/display: Make intel_dp_aux_fw_sync_len available for PSR code
- drm/i915/psr: Improve fast and IO wake lines calculation
- drm/i915/psr: Calculate IO wake and fast wake lines for DISPLAY_VER < 12
- drm/i915/display: Increase number of fast wake precharge pulses

  * Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- [Packaging] update update.conf
- debian.oem/dkms-versions -- update from kernel-versions (main/d2024.04.04)

  * intel_rapl_common: Add support for ARL and LNL (LP: #2061953)
- powercap: intel_rapl: Add support for Lunar Lake-M paltform
- powercap: intel_rapl: Add support for Arrow Lake

  [ Ubuntu: 6.8.0-28.28 ]

  * noble/linux: 6.8.0-28.28 -proposed tracker (LP: #2061867)
  * linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor
profiles/features (LP: #2061851)
- SAUCE: apparmor4.0.0 [92/90]: fix address mapping for recvfrom

  [ Ubuntu: 6.8.0-25.25 ]

  * noble/linux: 6.8.0-25.25 -proposed tracker (LP: #2061083)
  * Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
  (main/d2024.04.04)
  * Apply mitigations for the native BHI hardware vulnerabilty (LP: #2060909)
- x86/cpufeatures: Add new word for scattered features
- x86/bugs: Change commas to semicolons in 'spectre_v2' sysfs file
- x86/syscall: Don't force use of indirect calls for system calls
- x86/bhi: Add support for clearing branch history at syscall entry
- x86/bhi: Define SPEC_CTRL_BHI_DIS_S
- x86/bhi: Enumerate Branch History Injection (BHI) bug
- x86/bhi: Add BHI mitigation knob
- x86/bhi: Mitigate KVM by default
- KVM: x86: Add BHI_NO
- x86: set SPECTRE_BHI_ON as default
- [Config] enable spectre_bhi=auto by default
  * update apparmor and LSM stacking patch set (LP: #2028253)
- SAUCE: apparmor4.0.0 [01/90]: LSM stacking v39: integrity: disassociate
  ima_filter_rule from security_audit_rule
- SAUCE: apparmor4.0.0 [02/90]: LSM stacking v39: SM: Infrastructure
  management of the sock security
- SAUCE: apparmor4.0.0 [03/90]: LSM stacking v39: LSM: Add the lsmblob data
  structure.
- SAUCE: apparmor4.0.0 [04/90]: LSM stacking v39: IMA: avoid label 
collisions
  with stacked LSMs
- SAUCE: apparmor4.0.0 [05/90]: LSM stacking v39: LSM: Use lsmblob in
  security_audit_rule_match
- SAUCE: apparmor4.0.0 [06/90]: LSM stacking v39: LSM: Add lsmblob_to_secctx
  hook
- SAUCE: apparmor4.0.0 [07/90]: LSM stacking v39: Audit: maintain an lsmblob
  in audit_context
- SAUCE: apparmor4.0.0 [08/90]: LSM stacking v39: LSM: Use lsmblob in
  security_ipc_getsecid
- SAUCE: apparmor4.0.0 [09/90]: LSM stacking v39: Audit: Update shutdown LSM
  data
- SAUCE: apparmor4.0.0 [10/90]: LSM stacking v39: LSM: Use lsmblob in
  security_current_getsecid
- SAUCE: apparmor4.0.0 [11/90]: LSM stacking v39: LSM: Use lsmblob in
  security_inode_getsecid
- SAUCE: apparmor4.0.0 [12/90]: LSM stacking v39: Audit: use an lsmblob in
  audit_names
- SAUCE: apparmor4.0.0 [13/90]: LSM stacking v39: LSM: Create new
  security_cred_getlsmblob LSM hook
- SAUCE: apparmor4.0.0 [14/90]: LSM stacking v39: Audit: Change context data
  from secid to lsmblob
- SAUCE: apparmor4.0.0 [15/90]: LSM stacking v39: Netlabel: Use lsmblob for
  audit data
- SAUCE: apparmor4.0.0 [16/90]: LSM stacking v39: LSM: Ensure the correct 
LSM
  context releaser
- SAUCE: apparmor4.0.0 [17/90]: LSM stacking v39: LSM: Use lsmcontext in
  security_secid_to_secctx
- SAUCE: apparmor4.0.0 [18/90]: LSM stacking v39: LSM: Use lsmcontext in
  security_lsmblob_to_secctx
- SAUCE: apparmor4.0.0 [19/90]: LSM stacking v39: LSM: Use lsmcontext in
  security_inode_getsecctx
- SAUCE: apparmor4.0.0 [20/90]: LSM stacking v39: LSM: Use lsmcontext in
  security_dentry_init_security
- SAUCE: apparmor4.0.0 [21/90]: LSM stacking v39: LSM:
  security_lsmblob_to_secctx module selection
- SAUCE: apparmor4.0.0 [22/90]: LSM stacking v39: Audit: Create audit_stamp
  structure
- SAUCE: apparmor4.0.0 [23/90]: LSM stacking v39: Audit: Allow multiple
  records in an audit_buffer
- SAUCE: apparmor4.0.0 [24/90]: LSM stacking v39: Audit: Add record for
  multiple task security contexts
- SAUCE: apparmor4.0.0 [25/90]: LSM stacking v39: audit: multiple subject 
lsm
  values for netlabel

[Kernel-packages] [Bug 2062545] Re: Still, No keyboard after kernel update Linux t-l15 6.5.0-1020-oem

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

Title:
  Still, No keyboard after kernel update Linux t-l15 6.5.0-1020-oem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I use the ThinkPad L15 Gen4, BIOS version R24ET38W(1.21) together with
  Xubuntu 22.04.04 LTS kernel 6.5.0-1020-oem, the CPU type is i7-1355U.
  This combination gives still a not working keyboard after booting.

  Today the system has upgraded the kernel to Linux version
  6.5.0-1020-oem this should solves the keyboard problem introduced in
  kernel 6.5.0-1019-oem and already reported in:

  - https://bugs.launchpad.net/bugs/2060727
  - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060866

  This bug fix does not work, I still have no internal keyboard.

  For the moment I am using kernel 6.5.0-1018-oem which workes fine.

  Who can/will help?

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


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

[Kernel-packages] [Bug 2060727] Re: The keyboard does not work after latest kernel update

2024-04-19 Thread Ganton

> Is this new kernel working for you, Ganton?

No, it does not.

I've updated the kernel:
$ uname -a
Linux hostname 6.5.0-28-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 28 
23:46:48 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
although in the end, after rebooting, I have experimented the same problem.

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

Title:
  The keyboard does not work after latest kernel update

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not
  work after the latest kernel update and its subsequent reboot of the
  laptop. Nothing else is connected to the laptop.

  --

  In /var/log/apt/history.log , the latest we can see is:

  Start-Date: 2024-04-09  12:37:28
  Commandline: apt full-upgrade
  Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), 
linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic)
  Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), 
linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 
(6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28)
  End-Date: 2024-04-09  12:37:51

  --

  $ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.10
  Release:23.10

  $ # Note: It's Kubuntu 23.10

  --

  $ uname -a
  Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 18:21:00 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  SRU Justification:
  ==
  [Impact]
  Keyboard is lost after updated to 6.5.0-27 and oem-6.5-1019 kernel
  versions.

  [Fix]
  Regression commit is found commit:
  936e4d49ecbc ("Input: atkbd - skip ATKBD_CMD_GETID in translated mode")

  Fixes:
  9cf6e24c9fbf1 Input: atkbd - do not skip atkbd_deactivate() when
  skipping ATKBD_CMD_GETID
  683cd8259a9b8 Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping
  ATKBD_CMD_GETID

  [Test]
  Tested on hardware, keyboard works fine after bootup.

  The regression commit is only in 6.5 stable, so SRU for 6.5 only.

  [Where problems could occur]
  It may break keyboard.

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


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

[Kernel-packages] [Bug 2061897] Re: Enable Milk-V Mars board

This bug was fixed in the package linux-riscv - 6.8.0-28.28.1

---
linux-riscv (6.8.0-28.28.1) noble; urgency=medium

  * noble/linux-riscv: 6.8.0-28.28.1 -proposed tracker (LP: #2061974)

  * Packaging resync (LP: #1786013)
- [Packaging] drop getabis data
- [Packaging] debian.riscv/dkms-versions -- update from kernel-versions
  (main/d2024.04.04)

  * Enable Milk-V Mars board (LP: #2061897)
- SAUCE: riscv: dts: starfive: add 'cpus' label to jh7110 and jh7100 soc 
dtsi
- SAUCE: dt-bindings: riscv: starfive: add Milkv Mars board
- SAUCE: riscv: dts: starfive: visionfive 2: update sound and codec dt node
  name
- SAUCE: riscv: dts: starfive: visionfive 2: use cpus label for timebase 
freq
- SAUCE: riscv: dts: starfive: introduce a common board dtsi for jh7110 
based
  boards
- SAUCE: riscv: dts: starfive: add Milkv Mars board device tree

  * Enable StarFive VisionFive 2 board (LP: #2013232)
- SAUCE: riscv: dts: starfive: visionfive 2: Remove non-existing TDM 
hardware
- SAUCE: riscv: dts: starfive: visionfive 2: Remove non-existing I2S 
hardware

  [ Ubuntu: 6.8.0-28.28 ]

  * noble/linux: 6.8.0-28.28 -proposed tracker (LP: #2061867)
  * linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor
profiles/features (LP: #2061851)
- SAUCE: apparmor4.0.0 [92/90]: fix address mapping for recvfrom

  [ Ubuntu: 6.8.0-25.25 ]

  * noble/linux: 6.8.0-25.25 -proposed tracker (LP: #2061083)
  * Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
  (main/d2024.04.04)
  * Apply mitigations for the native BHI hardware vulnerabilty (LP: #2060909)
- x86/cpufeatures: Add new word for scattered features
- x86/bugs: Change commas to semicolons in 'spectre_v2' sysfs file
- x86/syscall: Don't force use of indirect calls for system calls
- x86/bhi: Add support for clearing branch history at syscall entry
- x86/bhi: Define SPEC_CTRL_BHI_DIS_S
- x86/bhi: Enumerate Branch History Injection (BHI) bug
- x86/bhi: Add BHI mitigation knob
- x86/bhi: Mitigate KVM by default
- KVM: x86: Add BHI_NO
- x86: set SPECTRE_BHI_ON as default
- [Config] enable spectre_bhi=auto by default
  * update apparmor and LSM stacking patch set (LP: #2028253)
- SAUCE: apparmor4.0.0 [01/90]: LSM stacking v39: integrity: disassociate
  ima_filter_rule from security_audit_rule
- SAUCE: apparmor4.0.0 [02/90]: LSM stacking v39: SM: Infrastructure
  management of the sock security
- SAUCE: apparmor4.0.0 [03/90]: LSM stacking v39: LSM: Add the lsmblob data
  structure.
- SAUCE: apparmor4.0.0 [04/90]: LSM stacking v39: IMA: avoid label 
collisions
  with stacked LSMs
- SAUCE: apparmor4.0.0 [05/90]: LSM stacking v39: LSM: Use lsmblob in
  security_audit_rule_match
- SAUCE: apparmor4.0.0 [06/90]: LSM stacking v39: LSM: Add lsmblob_to_secctx
  hook
- SAUCE: apparmor4.0.0 [07/90]: LSM stacking v39: Audit: maintain an lsmblob
  in audit_context
- SAUCE: apparmor4.0.0 [08/90]: LSM stacking v39: LSM: Use lsmblob in
  security_ipc_getsecid
- SAUCE: apparmor4.0.0 [09/90]: LSM stacking v39: Audit: Update shutdown LSM
  data
- SAUCE: apparmor4.0.0 [10/90]: LSM stacking v39: LSM: Use lsmblob in
  security_current_getsecid
- SAUCE: apparmor4.0.0 [11/90]: LSM stacking v39: LSM: Use lsmblob in
  security_inode_getsecid
- SAUCE: apparmor4.0.0 [12/90]: LSM stacking v39: Audit: use an lsmblob in
  audit_names
- SAUCE: apparmor4.0.0 [13/90]: LSM stacking v39: LSM: Create new
  security_cred_getlsmblob LSM hook
- SAUCE: apparmor4.0.0 [14/90]: LSM stacking v39: Audit: Change context data
  from secid to lsmblob
- SAUCE: apparmor4.0.0 [15/90]: LSM stacking v39: Netlabel: Use lsmblob for
  audit data
- SAUCE: apparmor4.0.0 [16/90]: LSM stacking v39: LSM: Ensure the correct 
LSM
  context releaser
- SAUCE: apparmor4.0.0 [17/90]: LSM stacking v39: LSM: Use lsmcontext in
  security_secid_to_secctx
- SAUCE: apparmor4.0.0 [18/90]: LSM stacking v39: LSM: Use lsmcontext in
  security_lsmblob_to_secctx
- SAUCE: apparmor4.0.0 [19/90]: LSM stacking v39: LSM: Use lsmcontext in
  security_inode_getsecctx
- SAUCE: apparmor4.0.0 [20/90]: LSM stacking v39: LSM: Use lsmcontext in
  security_dentry_init_security
- SAUCE: apparmor4.0.0 [21/90]: LSM stacking v39: LSM:
  security_lsmblob_to_secctx module selection
- SAUCE: apparmor4.0.0 [22/90]: LSM stacking v39: Audit: Create audit_stamp
  structure
- SAUCE: apparmor4.0.0 [23/90]: LSM stacking v39: Audit: Allow multiple
  records in an audit_buffer
- SAUCE: apparmor4.0.0 [24/90]: LSM stacking v39: Audit: Add record for
  multiple task security contexts
- SAUCE: apparmor4.0.0 [25/90]: LSM stacking v39: audit: multiple subject 
lsm
  values for netlabel
- SAUCE:

[Kernel-packages] [Bug 2062534] Re: GDM3 autologin might be racy on GCP resulting in inconsistent state of the wayland setup of seat0

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

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

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

Title:
  GDM3 autologin might be racy on GCP resulting in inconsistent state of
  the wayland setup of seat0

Status in gdm3 package in Ubuntu:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Confirmed

Bug description:
  This might not be a bug really about linux-gcp, but this is following
  the work on bug 2039732 and so far I could not reproduce that locally.

  Setup is 22.04 uptodate on GCP n2-standard instances, without GPU
  attached thus relying on vkms. I have reproduced locally a similar
  setup but on a KVM host.

  We rely on 
https://github.com/taskcluster/taskcluster/tree/main/workers/generic-worker#readme
 to run tasks on CI, and especially generic-worker will:
   - create a new task_XXX user
   - make it autologin in gdm3 config
   - generic-worker has code to probe for existence of the GNOME Wayland 
session before launching the task

  We relied on wl-clipboard package installed for verifying the status
  of wayland

  On top of that setup, here is the issue.

  We issue a TC task with payload:
  > export WAYLAND_DISPLAY=wayland-0
  > export XDG_RUNTIME_DIR=/run/user/$(id -u)
  > wl-paste -l -p

  We expect that payload to report "No selection", but on GCP instances
  we mostly always end up with "This seat has no keyboard". There were
  also cases were the session would not be Wayland at all but rather
  X11. I think this suggests something around the availability of
  /dev/dri/card0, but forcing the gdm3 service to wait for its
  availability and adding extra waiting time after card0 is present
  would still not get us somewhere.

  We enabled gdm3 as well as mutter debugging but never found anything
  that would be a good lead on why it was not yet ready.

  At some point, the seat0 session of our user was shown as inactive and
  the active one was tied to gdm so we suspected this was the reason,
  but both forcing the session to be active and terminating the gdm
  session would still not unblock us.

  We also suspected the desktop to be locking itself so we disabled locking 
with the following, but iit did not help much:
  > cat > /etc/dconf/profile/user << EOF
  > user-db:user
  > system-db:local
  > EOF
  > 
  > mkdir /etc/dconf/db/local.d/
  > # dconf user settings
  > cat > /etc/dconf/db/local.d/00-tc-gnome-settings << EOF
  > # /org/gnome/desktop/session/idle-delay
  > [org/gnome/desktop/session]
  > idle-delay=uint32 0
  > # /org/gnome/desktop/lockdown/disable-lock-screen
  > [org/gnome/desktop/lockdown]
  > disable-lock-screen=true
  > EOF
  > 
  > sudo dconf update

  
  In the end, the only viable and reliable (verified over hundreds of runs now) 
fix that lasted was to add a "/bin/sleep 30" all to the gdm3 startup:
  > mkdir -p /etc/systemd/system/gdm.service.d/
  > cat > /etc/systemd/system/gdm.service.d/gdm-wait.conf << EOF
  > [Unit]
  > Description=Extra 30s wait
  > [Service]
  > ExecStartPre=/bin/sleep 30
  > EOF

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


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

[Kernel-packages] [Bug 2062534] Re: GDM3 autologin might be racy on GCP resulting in inconsistent state of the wayland setup of seat0

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

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

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

Title:
  GDM3 autologin might be racy on GCP resulting in inconsistent state of
  the wayland setup of seat0

Status in gdm3 package in Ubuntu:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Confirmed

Bug description:
  This might not be a bug really about linux-gcp, but this is following
  the work on bug 2039732 and so far I could not reproduce that locally.

  Setup is 22.04 uptodate on GCP n2-standard instances, without GPU
  attached thus relying on vkms. I have reproduced locally a similar
  setup but on a KVM host.

  We rely on 
https://github.com/taskcluster/taskcluster/tree/main/workers/generic-worker#readme
 to run tasks on CI, and especially generic-worker will:
   - create a new task_XXX user
   - make it autologin in gdm3 config
   - generic-worker has code to probe for existence of the GNOME Wayland 
session before launching the task

  We relied on wl-clipboard package installed for verifying the status
  of wayland

  On top of that setup, here is the issue.

  We issue a TC task with payload:
  > export WAYLAND_DISPLAY=wayland-0
  > export XDG_RUNTIME_DIR=/run/user/$(id -u)
  > wl-paste -l -p

  We expect that payload to report "No selection", but on GCP instances
  we mostly always end up with "This seat has no keyboard". There were
  also cases were the session would not be Wayland at all but rather
  X11. I think this suggests something around the availability of
  /dev/dri/card0, but forcing the gdm3 service to wait for its
  availability and adding extra waiting time after card0 is present
  would still not get us somewhere.

  We enabled gdm3 as well as mutter debugging but never found anything
  that would be a good lead on why it was not yet ready.

  At some point, the seat0 session of our user was shown as inactive and
  the active one was tied to gdm so we suspected this was the reason,
  but both forcing the session to be active and terminating the gdm
  session would still not unblock us.

  We also suspected the desktop to be locking itself so we disabled locking 
with the following, but iit did not help much:
  > cat > /etc/dconf/profile/user << EOF
  > user-db:user
  > system-db:local
  > EOF
  > 
  > mkdir /etc/dconf/db/local.d/
  > # dconf user settings
  > cat > /etc/dconf/db/local.d/00-tc-gnome-settings << EOF
  > # /org/gnome/desktop/session/idle-delay
  > [org/gnome/desktop/session]
  > idle-delay=uint32 0
  > # /org/gnome/desktop/lockdown/disable-lock-screen
  > [org/gnome/desktop/lockdown]
  > disable-lock-screen=true
  > EOF
  > 
  > sudo dconf update

  
  In the end, the only viable and reliable (verified over hundreds of runs now) 
fix that lasted was to add a "/bin/sleep 30" all to the gdm3 startup:
  > mkdir -p /etc/systemd/system/gdm.service.d/
  > cat > /etc/systemd/system/gdm.service.d/gdm-wait.conf << EOF
  > [Unit]
  > Description=Extra 30s wait
  > [Service]
  > ExecStartPre=/bin/sleep 30
  > EOF

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


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

[Kernel-packages] [Bug 2062412] Re: No input through internal microphone (Ryzen 6000)

2024-04-19 Thread Mario Limonciello

This is the upstream solution:

https://github.com/torvalds/linux/commit/861b3415e4dee06cc00cd1754808a7827b9105bf

Here is the commit from 6.8.3:

b44a34f581b0 ("ASoC: amd: yc: Revert "Fix non-functional mic on Lenovo
21J2"")

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

Title:
  No input through internal microphone (Ryzen 6000)

Status in linux package in Ubuntu:
  New

Bug description:
  The microphone in a Thinkpad P14S (AMD) Gen 4 stopped working after
  updating from 23.10 to 24.04 Beta with kernel 6.8.0-22-generic. This
  is a known problem and a patch may be included in kernel 6.8.3.

  Is it possible to backport this patch? Or is the plan to wait for a
  kernel update? It would be good use the microphone in 24.04.

  The symptoms are exactly as described in
  https://bbs.archlinux.org/viewtopic.php?pid=2162297#p2162297

  Reportedly the patch is included in
  
https://github.com/zen-kernel/zen-kernel/blob/6.7/main/sound/soc/amd/yc/acp6x-mach.c#L59

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


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

[Kernel-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

This bug was fixed in the package zfs-linux - 2.2.2-0ubuntu9

---
zfs-linux (2.2.2-0ubuntu9) noble; urgency=medium

  * 
debian/patches/0007-Linux-6.8-compat-use-splice_copy_file_range-for-fallback.patch
- Linux 6.8 support(LP: #2058179)
  * debian/control:
- add libtirpc-dev as build dependency

 -- John Cabaj   Thu, 18 Apr 2024 23:00:06
-0500

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

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

Title:
  Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

Status in Native ZFS for Linux:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in systemd source package in Noble:
  Fix Committed
Status in zfs-linux source package in Noble:
  Fix Released

Bug description:
  As per https://github.com/openzfs/zfs/issues/15930

  ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
  copy_file_range, breaking a multitude of applications.

  Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
  2.2.2.

  One notable issue is when running Root on ZFS: systemd-sysusers will
  always fail to create users/groups with the error "Failed to backup
  /etc/{group,passwd}: Operation not supported" due to the call to
  copy_file_range.

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


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

[Kernel-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

2024-04-19 Thread antst

Yep, I agree that it would be important to push some number of backports
like this one to kernel module before release. Ideally, 2.2.3 would be
better for 6.8

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

Title:
  Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

Status in Native ZFS for Linux:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in zfs-linux package in Ubuntu:
  In Progress
Status in systemd source package in Noble:
  Fix Committed
Status in zfs-linux source package in Noble:
  In Progress

Bug description:
  As per https://github.com/openzfs/zfs/issues/15930

  ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
  copy_file_range, breaking a multitude of applications.

  Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
  2.2.2.

  One notable issue is when running Root on ZFS: systemd-sysusers will
  always fail to create users/groups with the error "Failed to backup
  /etc/{group,passwd}: Operation not supported" due to the call to
  copy_file_range.

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


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

[Kernel-packages] [Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

** Description changed:

  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==
  
  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==
  
  In 8.0.1:
  - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB
  
  In 8.0.2:
  - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing
  
  In 8.0.3:
  - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later
  
  In 8.0.4
  - 7750e61fdb2a Support module memory layout change on Linux 6.4
  - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  - 4ee56105881d Fix compilation error due to new strlcpy function that glibc  
added
  
  ==
  
  [Test Plan]
  
+ On Jammy (LTS), which provides HWE (6.5) and GA (5.15) kernels,
+ perform testing on both HWE (verify fixes) and GA (verify no regressions).
  
  There are detailed/per-commit test plans in the attachments:
  `crash_jammy_test_plan.txt.txt` and `crash_lunar_test_plan.txt`.
  
  And the general sysrq-trigger/makedumpfile/crash test:
  
  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump
  
  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll 
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  3. To trigger a crash dump forcefully, execute the `echo c | sudo tee 
/proc/sysrq-trigger` command.
  4. Download the kernel .ddeb file, which will be used for analyzing the dump 
file.
  # sudo -i
  # cd /var/crash
  # pull-lp-ddebs linux-image-unsigned-$(uname -r)
  # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
  5. Utilize the "crash" utility to parse and analyze the dump file.
  crash 8.0.0
  Copyright (C) 2002-2021  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2021  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
  
  WARNING: VA_BITS: calculated: 46  vmcoreinfo: 48
  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "aarch64-unknown-linux-gnu".
  Type "show configuration" for configuration details.
  Find the GDB manual and other documentation resources online at:
  .
  
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  
  crash: seek error: kernel virtual

[Kernel-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

2024-04-19 Thread Nick Rosbrook

** Changed in: systemd (Ubuntu Noble)
   Status: In Progress => Fix Committed

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

Title:
  Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

Status in Native ZFS for Linux:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in zfs-linux package in Ubuntu:
  In Progress
Status in systemd source package in Noble:
  Fix Committed
Status in zfs-linux source package in Noble:
  In Progress

Bug description:
  As per https://github.com/openzfs/zfs/issues/15930

  ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
  copy_file_range, breaking a multitude of applications.

  Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
  2.2.2.

  One notable issue is when running Root on ZFS: systemd-sysusers will
  always fail to create users/groups with the error "Failed to backup
  /etc/{group,passwd}: Operation not supported" due to the call to
  copy_file_range.

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


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

[Kernel-packages] [Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)

2024-04-19 Thread dann frazier

Thank Utkarsh. Yeah, we just dropped the ball on not getting this done
sooner. I'd like to see if we can make the case for SRU'ing 6.8 in, so
let's convert the bug to that.

I don't think we can justify dropping FAN support in an SRU, so let's
add that port back in.

We'll need to make a convincing case to the SRU team that the risk of
regression is minimal. Our partners at NVIDIA/Mellanox have offered to
put this release through their testing. I'll see if they can provide
details on what their tests will cover.

@matttbe - is there any documentation about upstream compatibility
guarantees and regression testing done that you're aware of, or any
tests that we could run beyond those in our autopkgtests?

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

Title:
[FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from
testing/unstable (main)

Status in iproute2 package in Ubuntu:
Incomplete

Bug description:
iproute2 upstream produces releases coinciding with upstream kernel
releases to support the latest kernel features. Noble's iproute2 is
still back at v6.1 even though it will use the v6.8 kernel. This means
we provide no userspace interface for newer features - some of which
are noted by a networking hardware partner in bug 2060969.

Ubuntu's iproute2 has diverged from Debian's to add support for Ubuntu
FAN. Noble has dropped kernel support for Ubuntu FAN, so those are no
longer needed, and we could now just do a merge. We could also port
the FAN patches forward if we can identify a need (see the original
description of this bug to a link to such a port), but I have not done
any testing with that.

I have built Debian's iproute2 in a noble ppa at ppa:dannf/test and
smoke tested it on an amd64 virtual machine:

ubuntu@cortez-vm-0:~$ sudo dpkg -i iproute2_6.8.0-1~24.04.1_amd64.deb
(Reading database ... 83134 files and directories currently installed.)
Preparing to unpack iproute2_6.8.0-1~24.04.1_amd64.deb ...
Unpacking iproute2 (6.8.0-1~24.04.1) over (6.1.0-1ubuntu6) ...
dpkg: warning: unable to delete old directory '/etc/iproute2/rt_tables.d':
Directory not empty
dpkg: warning: unable to delete old directory '/etc/iproute2/rt_protos.d':
Directory not empty
dpkg: warning: unable to delete old directory '/etc/iproute2': Directory not
empty
Setting up iproute2 (6.8.0-1~24.04.1) ...
Removing obsolete conffile /etc/iproute2/group ...
Removing obsolete conffile /etc/iproute2/rt_realms ...
Removing obsolete conffile /etc/iproute2/rt_scopes ...
Removing obsolete conffile /etc/iproute2/rt_tables ...
Removing obsolete conffile /etc/iproute2/rt_tables.d/README ...
Removing obsolete conffile /etc/iproute2/rt_protos.d/README ...
Removing obsolete conffile /etc/iproute2/rt_protos ...
Removing obsolete conffile /etc/iproute2/rt_dsfield ...
Removing obsolete conffile /etc/iproute2/nl_protos ...
Removing obsolete conffile /etc/iproute2/ematch_map ...
Removing obsolete conffile /etc/iproute2/bpf_pinning ...
Processing triggers for man-db (2.12.0-4build1) ...

The system rebooted fine. The ip command seems to behave normally.

Since the upstream test suite only appears to run at autopkgtest time, I
triggered a run in my PPA, and it passed:

https://autopkgtest.ubuntu.com/results/autopkgtest-noble-dannf-test/noble/amd64/i/iproute2/20240412_210819_97417@/log.gz

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

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

[Kernel-packages] [Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

crash 8.0.4 is available in noble (bug 2047861); checking the stable
releases' debdiffs.

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

** Description changed:

  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==
  
  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==
  
  In 8.0.1:
  - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB
  
  In 8.0.2:
  - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing
  
  In 8.0.3:
  - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later
  
- In 8.0.3++ (8.0.4 development)
+ In 8.0.4
  - 7750e61fdb2a Support module memory layout change on Linux 6.4
  - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  - 4ee56105881d Fix compilation error due to new strlcpy function that glibc  
added
  
  ==
  
  [Test Plan]
  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump
  
  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll 
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  3. To trigger a crash dump forcefully, execute the `echo c | sudo tee 
/proc/sysrq-trigger` command.
  4. Download the kernel .ddeb file, which will be used for analyzing the dump 
file.
  # sudo -i
  # cd /var/crash
  # pull-lp-ddebs linux-image-unsigned-$(uname -r)
  # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
  5. Utilize the "crash" utility to parse and analyze the dump file.
  crash 8.0.0
  Copyright (C) 2002-2021  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2021  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
  
  WARNING: VA_BITS: calculated: 46  vmcoreinfo: 48
  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "aarch64-unknown-linux-gnu".
  Type "show configuration" for configuration details.
  Find the GDB manual and other documentation resources online at:
  .
  
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  
  crash: seek error: kernel virtual address: d59a92d48ae8  type: "possible"
  WARNING: cannot read cpu_possible_map
  crash: seek error: kernel virtual address:

[Kernel-packages] [Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

Marking Lunar as Won't Fix (EOL).

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Jammy:
  In Progress
Status in crash source package in Lunar:
  Won't Fix
Status in crash source package in Mantic:
  In Progress
Status in crash source package in Noble:
  Fix Released

Bug description:
  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==

  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==

  In 8.0.1:
  - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB

  In 8.0.2:
  - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing

  In 8.0.3:
  - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later

  In 8.0.4
  - 7750e61fdb2a Support module memory layout change on Linux 6.4
  - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  - 4ee56105881d Fix compilation error due to new strlcpy function that glibc  
added

  ==

  [Test Plan]

  
  There are detailed/per-commit test plans in the attachments:
  `crash_jammy_test_plan.txt.txt` and `crash_lunar_test_plan.txt`.

  And the general sysrq-trigger/makedumpfile/crash test:

  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll 
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  3. To trigger a crash dump forcefully, execute the `echo c | sudo tee 
/proc/sysrq-trigger` command.
  4. Download the kernel .ddeb file, which will be used for analyzing the dump 
file.
  # sudo -i
  # cd /var/crash
  # pull-lp-ddebs linux-image-unsigned-$(uname -r)
  # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
  5. Utilize the "crash" utility to parse and analyze the dump file.
  crash 8.0.0
  Copyright (C) 2002-2021  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2021  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  WARNING: VA_BITS: calculated: 46  vmcoreinfo: 48
  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show

[Kernel-packages] [Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

Updated the SRU template as requested in comment #11 with the detailed
test plans provided in comments #16-#20.

** Changed in: crash (Ubuntu Lunar)
   Status: In Progress => Won't Fix

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

** Changed in: crash (Ubuntu Lunar)
 Assignee: Chengen Du (chengendu) => (unassigned)

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Jammy:
  In Progress
Status in crash source package in Lunar:
  Won't Fix
Status in crash source package in Mantic:
  In Progress
Status in crash source package in Noble:
  Fix Released

Bug description:
  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==

  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==

  In 8.0.1:
  - 14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  - 5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  - b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB

  In 8.0.2:
  - f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if 
vabits_actual is missing

  In 8.0.3:
  - d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  - df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  - 120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  - ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later

  In 8.0.4
  - 7750e61fdb2a Support module memory layout change on Linux 6.4
  - 88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  - 4ee56105881d Fix compilation error due to new strlcpy function that glibc  
added

  ==

  [Test Plan]

  
  There are detailed/per-commit test plans in the attachments:
  `crash_jammy_test_plan.txt.txt` and `crash_lunar_test_plan.txt`.

  And the general sysrq-trigger/makedumpfile/crash test:

  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll 
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  3. To trigger a crash dump forcefully, execute the `echo c | sudo tee 
/proc/sysrq-trigger` command.
  4. Download the kernel .ddeb file, which will be used for analyzing the dump 
file.
  # sudo -i
  # cd /var/crash
  # pull-lp-ddebs linux-image-unsigned-$(uname -r)
  # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
  5. Utilize the "crash" utility to parse and analyze the dump file.
  crash 8.0.0
  Copyright (C) 2002-2021  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2021  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  WARNING: VA_BITS: calculated: 46  vmcoreinfo:

[Kernel-packages] [Bug 2062545] Re: Still, No keyboard after kernel update Linux t-l15 6.5.0-1020-oem

The previously attached file dmesg20240419_2020.txt contains the dmesg
data booting the 1020 kernel.

Attached you find the dmesg file booting the 1018 kernel.

** Attachment added: "dmesg20240419_1018.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062545/+attachment/5768356/+files/dmesg20240419_1018.txt

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

Title:
  Still, No keyboard after kernel update Linux t-l15 6.5.0-1020-oem

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  I use the ThinkPad L15 Gen4, BIOS version R24ET38W(1.21) together with
  Xubuntu 22.04.04 LTS kernel 6.5.0-1020-oem, the CPU type is i7-1355U.
  This combination gives still a not working keyboard after booting.

  Today the system has upgraded the kernel to Linux version
  6.5.0-1020-oem this should solves the keyboard problem introduced in
  kernel 6.5.0-1019-oem and already reported in:

  - https://bugs.launchpad.net/bugs/2060727
  - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060866

  This bug fix does not work, I still have no internal keyboard.

  For the moment I am using kernel 6.5.0-1018-oem which workes fine.

  Who can/will help?

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


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

[Kernel-packages] [Bug 2060727] Re: The keyboard does not work after latest kernel update

Today the system has upgraded the kernel to Linux version 6.5.0-1020-oem
this should solves the keyboard problem introduced in kernel
6.5.0-1019-oem and already reported in:

- https://bugs.launchpad.net/bugs/2060727
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060866

This bug fix does not work, I still have no internal keyboard.

I made a new bug report, 2062545.

Is this new kernel working for you Ganton?

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

Title:
  The keyboard does not work after latest kernel update

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not
  work after the latest kernel update and its subsequent reboot of the
  laptop. Nothing else is connected to the laptop.

  --

  In /var/log/apt/history.log , the latest we can see is:

  Start-Date: 2024-04-09  12:37:28
  Commandline: apt full-upgrade
  Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), 
linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), 
linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic)
  Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), 
linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 
(6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28)
  End-Date: 2024-04-09  12:37:51

  --

  $ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.10
  Release:23.10

  $ # Note: It's Kubuntu 23.10

  --

  $ uname -a
  Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 18:21:00 
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  SRU Justification:
  ==
  [Impact]
  Keyboard is lost after updated to 6.5.0-27 and oem-6.5-1019 kernel
  versions.

  [Fix]
  Regression commit is found commit:
  936e4d49ecbc ("Input: atkbd - skip ATKBD_CMD_GETID in translated mode")

  Fixes:
  9cf6e24c9fbf1 Input: atkbd - do not skip atkbd_deactivate() when
  skipping ATKBD_CMD_GETID
  683cd8259a9b8 Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping
  ATKBD_CMD_GETID

  [Test]
  Tested on hardware, keyboard works fine after bootup.

  The regression commit is only in 6.5 stable, so SRU for 6.5 only.

  [Where problems could occur]
  It may break keyboard.

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


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

[Kernel-packages] [Bug 2062667] [NEW] Fails on (and should be removed from) raspi desktop

2024-04-19 Thread Dave Jones

Public bug reported:

The protection-domain-mapper package (and qrtr-tools) are both installed
by default on the Ubuntu Desktop for Raspberry Pi images, thanks to
their inclusion in the desktop-minimal seed for arm64. However, there's
no hardware that they target on these platforms, and the result is a
permanently failed service (pd-mapper.service).

It appears these were added to support the X13s laptop [1]. I've
attempted to work around the issue by excluding these packages in the
desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
this does not work (the packages still appear in the built images).
Ideally, these packages should be moved into a hardware-specific seed
for the X13s (and/or whatever other laptops need these things).
Alternatively, at a bare minimum, the package should have some
conditional that causes the service not to attempt to start when it's
not on Qualcomm hardware.

[1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
seeds/+git/ubuntu/commit/desktop-
minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

[2]: https://git.launchpad.net/~waveform/ubuntu-
seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

** Affects: protection-domain-mapper (Ubuntu)
 Importance: Undecided
 Status: New

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

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

** Summary changed:

- Fails (and should be removed from) raspi desktop
+ Fails on (and should be removed from) raspi desktop

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  New
Status in qrtr package in Ubuntu:
  New

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions


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

[Kernel-packages] [Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)

2024-04-19 Thread Utkarsh Gupta

Hello,

After looking at it and discussing this with Dann Frazier yesterday (via
IRC on #ubuntu-release), we discussed that iproute2 is an important
package, it's in main, and has a huge bunch of reverse dependencies.
Bumping from 6.1.x to 6.8.x is a bit too much atm, especially given how
much is already happening and this being an LTS release.

So with that, I'm going to NACK it for FFe and ask this to be uploaded
via 0-day SRU or a regular SRU. :)

Sorry but I hope you understand.

** Changed in: iproute2 (Ubuntu)
Status: Confirmed => Won't Fix

** Changed in: iproute2 (Ubuntu)
Status: Won't Fix => Incomplete

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

Title:
[FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from
testing/unstable (main)

Status in iproute2 package in Ubuntu:
Incomplete

I have built Debian's iproute2 in a noble ppa at ppa:dannf/test and
smoke tested it on an amd64 virtual machine:

The system rebooted fine. The ip command seems to behave normally.

Since the upstream test suite only appears to run at autopkgtest time, I
triggered a run in my PPA, and it passed:

https://autopkgtest.ubuntu.com/results/autopkgtest-noble-dannf-test/noble/amd64/i/iproute2/20240412_210819_97417@/log.gz

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

[Kernel-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

2024-04-19 Thread Brian Murray

** Changed in: systemd (Ubuntu Noble)
Milestone: None => ubuntu-24.04

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

Title:
  Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

Status in Native ZFS for Linux:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in zfs-linux package in Ubuntu:
  In Progress
Status in systemd source package in Noble:
  In Progress
Status in zfs-linux source package in Noble:
  In Progress

Bug description:
  As per https://github.com/openzfs/zfs/issues/15930

  ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
  copy_file_range, breaking a multitude of applications.

  Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
  2.2.2.

  One notable issue is when running Root on ZFS: systemd-sysusers will
  always fail to create users/groups with the error "Failed to backup
  /etc/{group,passwd}: Operation not supported" due to the call to
  copy_file_range.

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


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

[Kernel-packages] [Bug 2062280] Re: Bluetooth Broken In Kernel Versions 6.5+ (Realtek)

2024-04-19 Thread Rex Tsai

Please describe how to reproduce the issue. The bug report was based on
a self-built bluez, and did not explain what was the profile were
tested, which the built in UI or via an application talk to bluetoothd


When you are able to reproduce the issue, please run the following command, and 
upload the lp2062280 to this bug.
 
ubuntu-bug --save=lp2062280 bluez

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

Title:
  Bluetooth Broken In Kernel Versions 6.5+ (Realtek)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Starting with kernel 6.5 the external Bluetooth USB dongle based on
  Realtek stop working.

  This issue occurs on either UBuntu 22.04, 23.10 and 24.04 when kernel
  version is > 6.5. On a lower kernel version it works as we were using
  it for almost 2 years without issues.

  Version signature: Ubuntu 6.8.0-22.22-generic 6.8.1
  USB bluetooth device: Bus 001 Device 003: ID 0bda:a729 Realtek Semiconductor 
Corp. Bluetooth Radio

  ```
  $ uname -a
  Linux bomi-edge 6.8.0-22-generic #22-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr  4 
22:30:32 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
  ```

  ```
  $ lsusb | grep -i bluetooth
  Bus 001 Device 003: ID 0bda:a729 Realtek Semiconductor Corp. Bluetooth Radio
  ```

  Journalctl logs after the OS is starting
  ```
  journalctl -b | egrep -i bluetooth
  Apr 18 07:16:29 bomi-edge kernel: usb 1-9: Product: Bluetooth Radio
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: Core ver 2.22
  Apr 18 07:16:30 bomi-edge kernel: NET: Registered PF_BLUETOOTH protocol family
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI device and connection 
manager initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: L2CAP socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: SCO socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=000b lmp_ver=0a lmp_subver=8761
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: rom_version status=0 
version=1
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_fw.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_config.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 
30210
  Apr 18 07:16:30 bomi-edge systemd[1]: Reached target bluetooth.target - 
Bluetooth Support.
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922
  root@bomi-edge:/home/edge# journalctl -b | egrep -i bluetooth
  Apr 18 07:16:29 bomi-edge kernel: usb 1-9: Product: Bluetooth Radio
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: Core ver 2.22
  Apr 18 07:16:30 bomi-edge kernel: NET: Registered PF_BLUETOOTH protocol family
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI device and connection 
manager initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: L2CAP socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: SCO socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=000b lmp_ver=0a lmp_subver=8761
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: rom_version status=0 
version=1
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_fw.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_config.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 
30210
  Apr 18 07:16:30 bomi-edge systemd[1]: Reached target bluetooth.target - 
Bluetooth Support.
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922
  ```

  I have installed BlueZ package https://www.bluez.org/ and trying to
  discover the device which worked but i am always getting errors when
  trying to connect to the device via BT (after pairing)

  ```
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/adapter.c:property_set_mode() 
sending Set Discoverable command for index 0
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() 
[0x] command 0x0007
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() 
[0x] command 0x0007 complete: 0x00
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() 
[0x] command 0x0006
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() 
[0x] command 0x0006 complete: 0x00
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: 
src/adapter.c:property_set_mode_complete() Success (0x00)
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: 
src/adapter.c:new_settings_callback() Settings: 0x0adb
  Apr 18 09:22:37 bomi-edge

[Kernel-packages] [Bug 2062545] Re: Still, No keyboard after kernel update Linux t-l15 6.5.0-1020-oem

** Summary changed:

- Still, No keybord after kernel update Linux t-l15 6.5.0-1020-oem
+ Still, No keyboard after kernel update Linux t-l15 6.5.0-1020-oem

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

Title:
  Still, No keyboard after kernel update Linux t-l15 6.5.0-1020-oem

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  I use the ThinkPad L15 Gen4, BIOS version R24ET38W(1.21) together with
  Xubuntu 22.04.04 LTS kernel 6.5.0-1020-oem, the CPU type is i7-1355U.
  This combination gives still a not working keyboard after booting.

  Today the system has upgraded the kernel to Linux version
  6.5.0-1020-oem this should solves the keyboard problem introduced in
  kernel 6.5.0-1019-oem and already reported in:

  - https://bugs.launchpad.net/bugs/2060727
  - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060866

  This bug fix does not work, I still have no internal keyboard.

  For the moment I am using kernel 6.5.0-1018-oem which workes fine.

  Who can/will help?

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


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

[Kernel-packages] [Bug 2061949] Re: nouveau error

2024-04-19 Thread Islam

I also noticed this crash just before the Xwayland error:


[  108.391556] [ cut here ]
[  108.391560] WARNING: CPU: 7 PID: 6474 at kernel/workqueue.c:1790 
__queue_work.part.0+0x30c/0x3e0
[  108.391570] Modules linked in: uhid vboxnetadp(O) vboxnetflt(O) vboxdrv(O) 
ccm rfcomm snd_seq_dummy snd_hrtimer cmac algif_hash algif_skcipher af_alg qrtr 
bnep snd_ctl_led snd_soc_skl_hda_dsp snd_soc_hdac_hdmi snd_sof_probes 
snd_soc_intel_hda_dsp_common snd_hda_codec_hdmi snd_hda_codec_realtek 
snd_hda_codec_generic snd_soc_dmic snd_sof_pci_intel_tgl 
snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink 
soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof 
snd_sof_utils snd_soc_hdac_hda xt_multiport snd_hda_ext_core xt_tcpudp 
snd_soc_acpi_intel_match snd_soc_acpi xe xt_conntrack 
soundwire_generic_allocation soundwire_bus nf_conntrack nf_defrag_ipv6 
snd_soc_core nf_defrag_ipv4 nft_compat snd_compress ac97_bus nf_tables 
snd_pcm_dmaengine drm_suballoc_helper binfmt_misc libcrc32c snd_hda_intel 
snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_uncore_frequency 
snd_hda_core intel_uncore_frequency_common intel_tcc_cooling nouveau 
nls_iso8859_1 snd_hw
 dep x86_pkg_temp_thermal snd_pcm
[  108.391611]  intel_powerclamp i915 snd_seq_midi snd_seq_midi_event btusb 
drm_gpuvm btrtl uvcvideo coretemp processor_thermal_device_pci_legacy 
snd_rawmidi drm_exec iwlmvm btintel cmdlinepart videobuf2_vmalloc 
processor_thermal_device kvm_intel gpu_sched snd_seq btbcm uvc spi_nor 
processor_thermal_wt_hint videobuf2_memops snd_seq_device drm_ttm_helper 
drm_buddy btmtk mac80211 videobuf2_v4l2 mfd_aaeon asus_nb_wmi mei_hdcp mei_pxp 
mtd intel_rapl_msr libarc4 snd_timer kvm processor_thermal_rfim asus_wmi 
videodev bluetooth ttm iwlwifi processor_thermal_rapl irqbypass ledtrig_audio 
snd drm_display_helper intel_rapl_common videobuf2_common sparse_keymap rapl 
spi_intel_pci mei_me ecdh_generic i2c_i801 mc intel_cstate ecc platform_profile 
wmi_bmof mxm_wmi cec soundcore spi_intel processor_thermal_wt_req i2c_smbus 
cfg80211 mei rc_core processor_thermal_power_floor processor_thermal_mbox 
i2c_algo_bit igen6_edac intel_soc_dts_iosf int3403_thermal intel_pmc_core 
int340x_thermal_zone int3400_th
 ermal intel_vsec acpi_thermal_rel
[  108.391665]  pmt_telemetry joydev input_leds pmt_class acpi_pad acpi_tad 
mac_hid serio_raw msr parport_pc ppdev lp parport efi_pstore nfnetlink 
dmi_sysfs ip_tables x_tables autofs4 usbhid dm_crypt nvme hid_multitouch 
nvme_core hid_generic nvme_auth crct10dif_pclmul crc32_pclmul polyval_clmulni 
polyval_generic ghash_clmulni_intel intel_lpss_pci rtsx_pci_sdmmc sha256_ssse3 
i2c_hid_acpi intel_lpss ucsi_acpi sha1_ssse3 xhci_pci thunderbolt i2c_hid 
rtsx_pci video vmd idma64 typec_ucsi xhci_pci_renesas typec hid wmi 
pinctrl_tigerlake aesni_intel crypto_simd cryptd
[  108.391701] CPU: 7 PID: 6474 Comm: Xwayland Tainted: G   O   
6.8.0-22-generic #22-Ubuntu
[  108.391703] Hardware name: ASUSTeK COMPUTER INC. ZenBook 
UX435EG_UX435EG/UX435EG, BIOS UX435EG.315 04/22/2022
[  108.391705] RIP: 0010:__queue_work.part.0+0x30c/0x3e0
[  108.391709] Code: 4c 8b 30 49 89 c7 49 39 fe 0f 84 5a fe ff ff 0f 0b e9 53 
fe ff ff 65 8b 3d cd df b0 54 e8 3c c0 ff ff 89 45 d0 e9 23 fd ff ff <0f> 0b e9 
e2 fe ff ff 48 8b 0b 44 89 e0 49 8d 57 68 83 c8 07 83 e1
[  108.391711] RSP: 0018:b10c894b3818 EFLAGS: 00010082
[  108.391713] RAX:  RBX: 951d37d1f4c0 RCX: 
[  108.391714] RDX:  RSI:  RDI: 
[  108.391715] RBP: b10c894b3850 R08:  R09: 
[  108.391716] R10:  R11:  R12: 2000
[  108.391717] R13: 951d37d1f4c8 R14: 9520877b4500 R15: 951d001df200
[  108.391718] FS:  7142ceae08c0() GS:95208778() 
knlGS:
[  108.391720] CS:  0010 DS:  ES:  CR0: 80050033
[  108.391721] CR2: 7889cbf77000 CR3: 00015f1fa006 CR4: 00f70ef0
[  108.391723] PKRU: 5554
[  108.391724] Call Trace:
[  108.391726]  
[  108.391730]  ? show_regs+0x6d/0x80
[  108.391733]  ? __warn+0x89/0x160
[  108.391736]  ? __queue_work.part.0+0x30c/0x3e0
[  108.391739]  ? report_bug+0x17e/0x1b0
[  108.391742]  ? handle_bug+0x51/0xa0
[  108.391746]  ? exc_invalid_op+0x18/0x80
[  108.391749]  ? asm_exc_invalid_op+0x1b/0x20
[  108.391755]  ? __queue_work.part.0+0x30c/0x3e0
[  108.391758]  ? __queue_work.part.0+0xf7/0x3e0
[  108.391760]  ? __pfx_pci_pm_runtime_resume+0x10/0x10
[  108.391764]  __queue_work+0x36/0xa0
[  108.391767]  queue_work_on+0x67/0x70
[  108.391771]  nouveau_display_hpd_resume+0x49/0x60 [nouveau]
[  108.391897]  nouveau_pmops_runtime_resume+0xef/0x1a0 [nouveau]
[  108.391986]  pci_pm_runtime_resume+0xa0/0x100
[  108.391989]  __rpm_callback+0x4d/0x170
[  108.391992]  rpm_callback+0x6d/0x80
[  108.391993]  ? __pfx_pci_pm_runtime_resume+0x10/0x10
[

[Kernel-packages] [Bug 2062579] [NEW] Kernel 6.5.0-28 errors during boot.

2024-04-19 Thread Alan Knepper

Public bug reported:

Installed new kernel as test to diagnose 5.15.0-102 kernel.
With 6.5 I am getting the errors in attached screen shot.

Also the keyboard stops working when I do a sleep/suspend and wake.

This line in grub fixes the keyboard inop issue and sleep issues both.
However with the dumbkbd entry, the caps-lock key is not working.

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.dumbkbd=1 i8042.nomux=1 
i8042.noaux=1"
alan: ~ $ lsb_release -rd
Description: Linux Mint 21.3
Release: 21.3

Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13

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

** Description changed:

- Installed new kernel as test to diagnose 5.15.0-102 kernel.   
+ Installed new kernel as test to diagnose 5.15.0-102 kernel.
  With 6.5 I am getting the errors in attached screen shot.
  
  Also the keyboard stops working when I do a sleep/suspend and wake.
  
  This line in grub fixes the keyboard inop issue and sleep issues both.
  However with the dumbkbd entry, the caps-lock key is not working.
  
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.dumbkbd=1 i8042.nomux=1 
i8042.noaux=1"
  alan: ~ $ lsb_release -rd
  Description: Linux Mint 21.3
  Release: 21.3
+ 
+ Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13

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

Title:
  Kernel 6.5.0-28 errors during boot.

Status in linux package in Ubuntu:
  New

Bug description:
  Installed new kernel as test to diagnose 5.15.0-102 kernel.
  With 6.5 I am getting the errors in attached screen shot.

  Also the keyboard stops working when I do a sleep/suspend and wake.

  This line in grub fixes the keyboard inop issue and sleep issues both.
  However with the dumbkbd entry, the caps-lock key is not working.

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.dumbkbd=1 i8042.nomux=1 
i8042.noaux=1"
  alan: ~ $ lsb_release -rd
  Description: Linux Mint 21.3
  Release: 21.3

  Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13

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


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

[Kernel-packages] [Bug 2062576] [NEW] Keyboard stops working after suspend 5.15.0-105

2024-04-19 Thread Alan Knepper

Public bug reported:

Kernel updates on Apr 8 '24 started the issue of keyboard not working after 
sleep/suspend.
Kernel 5.15.0-97 works, other kernels after 97 need grub modified to make them 
work.  
Changed:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.dumbkbd=1 i8042.nomux=1 
i8042.noaux=1"

Only negative side effect of the i8042.dumbkbd entry is that the caps-
lock light does not work. Otherwise on suspend and wake the keyboard
works.

I even tried the 6.6.0-26 kernel with same issue.

version.log: Ubuntu 5.15.0-105.115-generic 5.15.148

alan: ~ $ lsb_release -rd
Description:Linux Mint 21.3
Release:21.3

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

** Attachment added: "output of lspci -vnvn"
   
https://bugs.launchpad.net/bugs/2062576/+attachment/5768322/+files/lspci-vnvn.log

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

Title:
  Keyboard stops working after suspend 5.15.0-105

Status in linux package in Ubuntu:
  New

Bug description:
  Kernel updates on Apr 8 '24 started the issue of keyboard not working after 
sleep/suspend.
  Kernel 5.15.0-97 works, other kernels after 97 need grub modified to make 
them work.  
  Changed:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.dumbkbd=1 i8042.nomux=1 
i8042.noaux=1"

  Only negative side effect of the i8042.dumbkbd entry is that the caps-
  lock light does not work. Otherwise on suspend and wake the keyboard
  works.

  I even tried the 6.6.0-26 kernel with same issue.

  version.log: Ubuntu 5.15.0-105.115-generic 5.15.148

  alan: ~ $ lsb_release -rd
  Description:  Linux Mint 21.3
  Release:  21.3

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


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

[Kernel-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

2024-04-19 Thread Grant Pannell

Could someone please advise how these issues can float a little higher
before kernel freeze things happen? I tried to get this on the books
quite early by doing a Ubuntu Root on ZFS setup and giving it a test. I
know it's not directly related to the issue, but I tried to raise
awareness of this quite a while ago with no interest. Is this the right
place for reports like this?

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

Title:
  Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

Status in Native ZFS for Linux:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in zfs-linux package in Ubuntu:
  In Progress
Status in systemd source package in Noble:
  In Progress
Status in zfs-linux source package in Noble:
  In Progress

Bug description:
  As per https://github.com/openzfs/zfs/issues/15930

  ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
  copy_file_range, breaking a multitude of applications.

  Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
  2.2.2.

  One notable issue is when running Root on ZFS: systemd-sysusers will
  always fail to create users/groups with the error "Failed to backup
  /etc/{group,passwd}: Operation not supported" due to the call to
  copy_file_range.

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


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

[Kernel-packages] [Bug 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

2024-04-19 Thread Bogdan Melnik

I think I have the same issue which translates to the fact that I can't
boot the x13s image from https://cdimage.ubuntu.com/daily-live/current/
(2024-04-17 06:17).

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Noble:
  Confirmed

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

2024-04-19 Thread Nick Rosbrook

Since kernel rebuilds are required for the ZFS fix to be readily
available, I am uploading the systemd workaround to help mitigate the
problem.

** Changed in: systemd (Ubuntu Noble)
   Status: Triaged => In Progress

** Changed in: systemd (Ubuntu Noble)
   Importance: Medium => Critical

** Changed in: systemd (Ubuntu Noble)
 Assignee: (unassigned) => Nick Rosbrook (enr0n)

** Tags removed: systemd-sru-next

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

Title:
  Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

Status in Native ZFS for Linux:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress
Status in zfs-linux package in Ubuntu:
  In Progress
Status in systemd source package in Noble:
  In Progress
Status in zfs-linux source package in Noble:
  In Progress

Bug description:
  As per https://github.com/openzfs/zfs/issues/15930

  ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
  copy_file_range, breaking a multitude of applications.

  Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
  2.2.2.

  One notable issue is when running Root on ZFS: systemd-sysusers will
  always fail to create users/groups with the error "Failed to backup
  /etc/{group,passwd}: Operation not supported" due to the call to
  copy_file_range.

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


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

[Kernel-packages] [Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

Running an apt upgrade rather than apt-get upgrade installed the new kernel now.
Just installed on testserver and tried CIFS mounts with a short test.
It seems working now, thanks !
I'll install as soon as possible this kernel on 2 more productive servers and 
try what's happen  
Bye
Axel

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

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

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo
  Tue Apr  9 04:11:05 PM CEST 2024 hallo
  Tue Apr  9 04:11:06 PM CEST 2024 hallo
  Tue Apr  9 04:11:07 PM CEST 2024 hallo
  Tue Apr  9 04:11:08 PM CEST 2024 hallo
  Tue Apr  9 04:11:09 PM CEST 2024 hallo
  Tue Apr  9 04:11:10 PM CEST 2024 hallo

  While doing this, both servers tell me, the resource is unavailable

  root@:~# df -h /mnt
  df: /mnt: Resource temporarily unavailable

  root@:~$ df -h /mnt
  df: /mnt: Resource temporarily unavailable

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


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

[Kernel-packages] [Bug 2061006] Re: aws: KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call

2024-04-19 Thread Philip Cox

** Also affects: linux-aws (Ubuntu Noble)
   Importance: Undecided
 Assignee: Philip Cox (philcox)
   Status: New

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

** Changed in: linux-aws (Ubuntu Mantic)
 Assignee: (unassigned) => Philip Cox (philcox)

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

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

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

Title:
  aws: KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call

Status in linux-aws package in Ubuntu:
  In Progress
Status in linux-aws source package in Mantic:
  In Progress
Status in linux-aws source package in Noble:
  In Progress

Bug description:
  SRU Justification:

  [Impact]
  PSCI v1.3 adds support for SYSTEM_OFF2 which is analogous to ACPI S4 state.

  This will allow hosting environments to determine that a guest is
  hibernated rather than just powered off, and ensure that they preserve
  the virtual environment appropriately to allow the guest to resume
  safely (or bump the hardware_signature in the FACS to trigger a clean
  reboot instead).

  [Fix]
  This adds support for it to KVM, and to the guest hibernate code.

  https://lore.kernel.org/lkml/20240312135958.727765-1-dw...@infradead.org

  [Test Plan]
  AWS tested.

  [Where problems could occur]
  If the final spec of the PSCI v1.3 changes, there may be changes required to 
this patch series.

  [Other Info]

  SF# 00383181

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


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

[Kernel-packages] [Bug 2060992] Re: aws: Guest kernel support for clean boot on demand

2024-04-19 Thread Philip Cox

** Also affects: linux-aws (Ubuntu Noble)
   Importance: Undecided
 Assignee: Philip Cox (philcox)
   Status: New

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

** Changed in: linux-aws (Ubuntu Mantic)
 Assignee: (unassigned) => Philip Cox (philcox)

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

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

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

Title:
  aws: Guest kernel support for clean boot on demand

Status in linux-aws package in Ubuntu:
  In Progress
Status in linux-aws source package in Mantic:
  In Progress
Status in linux-aws source package in Noble:
  In Progress

Bug description:
  SRU Justification:

  [Impact]
  The FACS field in the ACPI table is optional, but can be used communicate the 
hardware_signature field.  If this field changes on resuming from a hibernation 
a clean reboot should happen rather than the resume from hibernation.

  On hardware reduced platforms[0] this field may exist but it is not
  exposed currently.

  [Fix]
  Expose this field even on hardware reduced platforms.

  https://lore.kernel.org/lkml/20240312134148.727454-1-dw...@infradead.org

  [Test Plan]
  AWS test.

  [Where problems could occur]
  If on hardware reduced platforms that incorrectly support/advertise the FACS 
field, hibernation may break if it returns a hardware signature that changes.

  [Other info]
  SF# 00383181

  [0]: See Section 4.1 of the ACPI spec for info on hardware-reduced platforms.
  
https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/04_ACPI_Hardware_Specification/ACPI_Hardware_Specification.html

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


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

[Kernel-packages] [Bug 2059143] Re: Remove getabis scripts

2024-04-19 Thread Ubuntu Kernel Bot

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


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


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


** Tags added: kernel-spammed-focal-linux-gcp-tcpx-v2 
verification-needed-focal-linux-gcp-tcpx

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

Title:
  Remove getabis scripts

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

Bug description:
  SRU Justification

  [Impact]
  With ABI checks removed from the tree (#LP2055685), there's no need to
  download the buildinfo from a previous version.

  [Fix]
  This is needed only in the main kernels.
  1. remove the common getabis script
  2. remove per kernel getabis file (this will be done with cranky fix)

  [Test]
  Build test on cbd. No issue found. Also cranked the kernels in advance to see 
if there were issues, but no issue was found.

  [Regression potential]
  In the current cycle, the ABI checks have been removed and this is not used 
anymore. No issues have been found. Now we're just removing an unused feature, 
therefore the regression potential is none.

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


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

[Kernel-packages] [Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

2024-04-19 Thread Ubuntu Kernel Bot

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


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


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


** Tags added: kernel-spammed-focal-linux-gcp-tcpx-v2 
verification-needed-focal-linux-gcp-tcpx

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

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

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo
  Tue Apr  9 04:11:05 PM CEST 2024 hallo
  Tue Apr  9 04:11:06 PM CEST 2024 hallo
  Tue Apr  9 04:11:07 PM CEST 2024 hallo
  Tue Apr  9 04:11:08 PM CEST 2024 hallo
  Tue Apr  9 04:11:09 PM CEST 2024 hallo
  Tue Apr  9 04:11:10 PM CEST 2024 hallo

  While doing this, both servers tell me, the resource is unavailable

  root@:~# df -h /mnt
  df: /mnt: Resource temporarily unavailable

  root@:~$ df -h /mnt
  df: /mnt: Resource temporarily unavailable

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


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

[Kernel-packages] [Bug 2062556] Re: [Ubuntu-24.04] Hugepage memory is not getting released even after destroying the guest!

2024-04-19 Thread Thibf

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

Title:
  [Ubuntu-24.04] Hugepage memory is not getting released even after
  destroying the guest!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ---Problem Description---

  Hugepages memory is not getting released even after destroying the guest
   
  Machine Type = P10 Denali LPAR 
   
  ---uname output---
  Linux ubuntu2404lp3 6.8.0-22-generic #22-Ubuntu SMP Thu Apr  4 22:47:57 UTC 
2024 ppc64le ppc64le ppc64le GNU/Linux

   
  ---Steps to Reproduce---
  1. Create a guest which is backed by hugepages.
  2. Destroy the guest
  3. execute "free -h" or "cat /proc/meminfo" to see that Hugepage memory is 
still getting held.
   
   
  HugePages_Total:   20480
  HugePages_Free:20419
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   2048 kB
  Hugetlb:41943040 kB
  DirectMap4k:   0 kB
  DirectMap64k:52428800 kB
  DirectMap2M:   0 kB
  DirectMap1G:   0 kB
  root@ubuntu2404lp3:~# virsh list --all
   Id   Name   State
  ---
   -ramlp2g1   shut off
   -ramlp2g2   shut off
   -ramlp2g3   shut off
   -ramlp3g3   shut off

  root@ubuntu2404lp3:~# free -h
 totalusedfree  shared  buff/cache   
available
  Mem:48Gi43Gi   4.6Gi   2.6Mi   277Mi   
4.6Gi
  Swap:  8.0Gi   243Mi   7.8Gi
  root@ubuntu2404lp3:~#

  
  This is an issue created by commit 1b151e2435fc ("block: Remove 
special-casing of compound pages") that moved the direct-io hugetlb handling 
from compound pages to folios.

  Following commit has been proposed and merged into 6.9-rc1 which fixes this 
issue.
  38b43539d64b2fa020b3b9a752a986769f87f7a6("block: Fix page refcounts for 
unaligned buffers in __bio_release_pages()")

  So the same needs to be backported to the Ubuntu24.04 kernel as well.

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


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

[Kernel-packages] [Bug 2062562] Re: Keyboard not working after resume from suspend on Dell XPS 13 laptop

2024-04-19 Thread Sebastian Podjasek

Maybe this is related with this: https://lore.kernel.org/linux-
input/20240126160724.13278-1-hdego...@redhat.com/

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

Title:
  Keyboard not working after resume from suspend on Dell XPS 13 laptop

Status in linux-signed package in Ubuntu:
  New

Bug description:
  After upgrade to 6.5.0-27-generic keyboard stopped working when laptop comes 
back to life after suspend.
  When booted with 6.5.0-26-generic everything is fine.

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


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

[Kernel-packages] [Bug 2062562] [NEW] Keyboard not working after resume from suspend on Dell XPS 13 laptop

2024-04-19 Thread Sebastian Podjasek

Public bug reported:

After upgrade to 6.5.0-27-generic keyboard stopped working when laptop comes 
back to life after suspend.
When booted with 6.5.0-26-generic everything is fine.

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

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

Title:
  Keyboard not working after resume from suspend on Dell XPS 13 laptop

Status in linux-signed package in Ubuntu:
  New

Bug description:
  After upgrade to 6.5.0-27-generic keyboard stopped working when laptop comes 
back to life after suspend.
  When booted with 6.5.0-26-generic everything is fine.

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


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

[Kernel-packages] [Bug 2062556] [NEW] [Ubuntu-24.04] Hugepage memory is not getting released even after destroying the guest!

2024-04-19 Thread bugproxy

Public bug reported:

---Problem Description---

Hugepages memory is not getting released even after destroying the guest
 
Machine Type = P10 Denali LPAR 
 
---uname output---
Linux ubuntu2404lp3 6.8.0-22-generic #22-Ubuntu SMP Thu Apr  4 22:47:57 UTC 
2024 ppc64le ppc64le ppc64le GNU/Linux

 
---Steps to Reproduce---
1. Create a guest which is backed by hugepages.
2. Destroy the guest
3. execute "free -h" or "cat /proc/meminfo" to see that Hugepage memory is 
still getting held.
 
 
HugePages_Total:   20480
HugePages_Free:20419
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize:   2048 kB
Hugetlb:41943040 kB
DirectMap4k:   0 kB
DirectMap64k:52428800 kB
DirectMap2M:   0 kB
DirectMap1G:   0 kB
root@ubuntu2404lp3:~# virsh list --all
 Id   Name   State
---
 -ramlp2g1   shut off
 -ramlp2g2   shut off
 -ramlp2g3   shut off
 -ramlp3g3   shut off

root@ubuntu2404lp3:~# free -h
   totalusedfree  shared  buff/cache   available
Mem:48Gi43Gi   4.6Gi   2.6Mi   277Mi   4.6Gi
Swap:  8.0Gi   243Mi   7.8Gi
root@ubuntu2404lp3:~#


This is an issue created by commit 1b151e2435fc ("block: Remove special-casing 
of compound pages") that moved the direct-io hugetlb handling from compound 
pages to folios.

Following commit has been proposed and merged into 6.9-rc1 which fixes this 
issue.
38b43539d64b2fa020b3b9a752a986769f87f7a6("block: Fix page refcounts for 
unaligned buffers in __bio_release_pages()")

So the same needs to be backported to the Ubuntu24.04 kernel as well.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-206058 severity-high 
targetmilestone-inin2404

** Tags added: architecture-ppc64le bugnameltc-206058 severity-high
targetmilestone-inin2404

** Changed in: ubuntu
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

** Package changed: 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/2062556

Title:
  [Ubuntu-24.04] Hugepage memory is not getting released even after
  destroying the guest!

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---

  Hugepages memory is not getting released even after destroying the guest
   
  Machine Type = P10 Denali LPAR 
   
  ---uname output---
  Linux ubuntu2404lp3 6.8.0-22-generic #22-Ubuntu SMP Thu Apr  4 22:47:57 UTC 
2024 ppc64le ppc64le ppc64le GNU/Linux

   
  ---Steps to Reproduce---
  1. Create a guest which is backed by hugepages.
  2. Destroy the guest
  3. execute "free -h" or "cat /proc/meminfo" to see that Hugepage memory is 
still getting held.
   
   
  HugePages_Total:   20480
  HugePages_Free:20419
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   2048 kB
  Hugetlb:41943040 kB
  DirectMap4k:   0 kB
  DirectMap64k:52428800 kB
  DirectMap2M:   0 kB
  DirectMap1G:   0 kB
  root@ubuntu2404lp3:~# virsh list --all
   Id   Name   State
  ---
   -ramlp2g1   shut off
   -ramlp2g2   shut off
   -ramlp2g3   shut off
   -ramlp3g3   shut off

  root@ubuntu2404lp3:~# free -h
 totalusedfree  shared  buff/cache   
available
  Mem:48Gi43Gi   4.6Gi   2.6Mi   277Mi   
4.6Gi
  Swap:  8.0Gi   243Mi   7.8Gi
  root@ubuntu2404lp3:~#

  
  This is an issue created by commit 1b151e2435fc ("block: Remove 
special-casing of compound pages") that moved the direct-io hugetlb handling 
from compound pages to folios.

  Following commit has been proposed and merged into 6.9-rc1 which fixes this 
issue.
  38b43539d64b2fa020b3b9a752a986769f87f7a6("block: Fix page refcounts for 
unaligned buffers in __bio_release_pages()")

  So the same needs to be backported to the Ubuntu24.04 kernel as well.

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


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

[Kernel-packages] [Bug 2062556] [NEW] [Ubuntu-24.04] Hugepage memory is not getting released even after destroying the guest!

You have been subscribed to a public bug:

---Problem Description---

Hugepages memory is not getting released even after destroying the guest
 
Machine Type = P10 Denali LPAR 
 
---uname output---
Linux ubuntu2404lp3 6.8.0-22-generic #22-Ubuntu SMP Thu Apr  4 22:47:57 UTC 
2024 ppc64le ppc64le ppc64le GNU/Linux

 
---Steps to Reproduce---
1. Create a guest which is backed by hugepages.
2. Destroy the guest
3. execute "free -h" or "cat /proc/meminfo" to see that Hugepage memory is 
still getting held.
 
 
HugePages_Total:   20480
HugePages_Free:20419
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize:   2048 kB
Hugetlb:41943040 kB
DirectMap4k:   0 kB
DirectMap64k:52428800 kB
DirectMap2M:   0 kB
DirectMap1G:   0 kB
root@ubuntu2404lp3:~# virsh list --all
 Id   Name   State
---
 -ramlp2g1   shut off
 -ramlp2g2   shut off
 -ramlp2g3   shut off
 -ramlp3g3   shut off

root@ubuntu2404lp3:~# free -h
   totalusedfree  shared  buff/cache   available
Mem:48Gi43Gi   4.6Gi   2.6Mi   277Mi   4.6Gi
Swap:  8.0Gi   243Mi   7.8Gi
root@ubuntu2404lp3:~#


This is an issue created by commit 1b151e2435fc ("block: Remove special-casing 
of compound pages") that moved the direct-io hugetlb handling from compound 
pages to folios.

Following commit has been proposed and merged into 6.9-rc1 which fixes this 
issue.
38b43539d64b2fa020b3b9a752a986769f87f7a6("block: Fix page refcounts for 
unaligned buffers in __bio_release_pages()")

So the same needs to be backported to the Ubuntu24.04 kernel as well.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-206058 severity-high 
targetmilestone-inin2404
-- 
[Ubuntu-24.04] Hugepage memory is not getting released even after destroying 
the guest!
https://bugs.launchpad.net/bugs/2062556
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

Re: [Kernel-packages] [Bug 1936678] [NEW] Samsung Laptop support module doesn't load

2024-04-19 Thread David Johnston

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

Title:
  Samsung Laptop support module doesn't load

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  This is identical to bug # 1170885, which was filed 2013-04-20. The
  last comment on that bug was by Kai-Heng Feng (kaihengfeng), who
  requested a new bug report.

  This is a Samsung laptop NP730QCJ.

  $ sudo modprobe samsung-laptop
  modprobe: ERROR: could not insert 'samsung_laptop': No such device

  About my system:
  $ sudo dmidecode | grep -A 2 -i 'base board'
  Base Board Information
Manufacturer: SAMSUNG ELECTRONICS CO., LTD.
Product Name: NP730QCJ-K01US

  $  cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04.2 LTS"

  $ cat /proc/version_signature
  Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18

  $ file /sys/firmware/efi/
  /sys/firmware/efi/: directory

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


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

[Kernel-packages] [Bug 2062548] [NEW] RISC-V: [drm] Display Core failed to initialize with v3.2.266!

2024-04-19 Thread Heinrich Schuchardt

Public bug reported:

On a riscv64 Unmatched board GPU output fails for a Radeon RX 6400:

[  +0.000917] [drm] Display Core failed to initialize with v3.2.266!
[  +0.24] Unable to handle kernel access to user memory without uaccess 
routines at virtual address 0008

A Radeon R230 works fine but that is using another firmware driver.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-20-generic 6.8.0-20.20.1
ProcVersionSignature: Ubuntu 6.8.0-20.20.1-generic 6.8.1
Uname: Linux 6.8.0-20-generic riscv64
ApportVersion: 2.28.0-0ubuntu1
Architecture: riscv64
CasperMD5json:
 {
   "result": "skip"
 }
Date: Fri Apr 19 13:00:35 2024
InstallationDate: Installed on 2024-04-18 (1 days ago)
InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Beta riscv64 
(20240418)
SourcePackage: linux-riscv
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug noble riscv64

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

Title:
  RISC-V: [drm] Display Core failed to initialize with v3.2.266!

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  On a riscv64 Unmatched board GPU output fails for a Radeon RX 6400:

  [  +0.000917] [drm] Display Core failed to initialize with v3.2.266!
  [  +0.24] Unable to handle kernel access to user memory without uaccess 
routines at virtual address 0008

  A Radeon R230 works fine but that is using another firmware driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-20-generic 6.8.0-20.20.1
  ProcVersionSignature: Ubuntu 6.8.0-20.20.1-generic 6.8.1
  Uname: Linux 6.8.0-20-generic riscv64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: riscv64
  CasperMD5json:
   {
 "result": "skip"
   }
  Date: Fri Apr 19 13:00:35 2024
  InstallationDate: Installed on 2024-04-18 (1 days ago)
  InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Beta riscv64 
(20240418)
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2062548] Re: RISC-V: [drm] Display Core failed to initialize with v3.2.266!

2024-04-19 Thread Heinrich Schuchardt

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2062548/+attachment/5768195/+files/dmesg.txt

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

Title:
  RISC-V: [drm] Display Core failed to initialize with v3.2.266!

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  On a riscv64 Unmatched board GPU output fails for a Radeon RX 6400:

  [  +0.000917] [drm] Display Core failed to initialize with v3.2.266!
  [  +0.24] Unable to handle kernel access to user memory without uaccess 
routines at virtual address 0008

  A Radeon R230 works fine but that is using another firmware driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-20-generic 6.8.0-20.20.1
  ProcVersionSignature: Ubuntu 6.8.0-20.20.1-generic 6.8.1
  Uname: Linux 6.8.0-20-generic riscv64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: riscv64
  CasperMD5json:
   {
 "result": "skip"
   }
  Date: Fri Apr 19 13:00:35 2024
  InstallationDate: Installed on 2024-04-18 (1 days ago)
  InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Beta riscv64 
(20240418)
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

2024-04-19 Thread John Cabaj

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

** Changed in: zfs-linux (Ubuntu Noble)
 Assignee: (unassigned) => John Cabaj (john-cabaj)

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

Title:
  Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

Status in Native ZFS for Linux:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in zfs-linux package in Ubuntu:
  In Progress
Status in systemd source package in Noble:
  Triaged
Status in zfs-linux source package in Noble:
  In Progress

Bug description:
  As per https://github.com/openzfs/zfs/issues/15930

  ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
  copy_file_range, breaking a multitude of applications.

  Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
  2.2.2.

  One notable issue is when running Root on ZFS: systemd-sysusers will
  always fail to create users/groups with the error "Failed to backup
  /etc/{group,passwd}: Operation not supported" due to the call to
  copy_file_range.

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


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

[Kernel-packages] [Bug 2062545] Re: Still, No keybord after kernel update Linux t-l15 6.5.0-1020-oem

This is what today is removed/added to the system:

Start-Date: 2024-04-19  13:33:54
Commandline: apt-get purge linux-image-6.1.0-1028-oem
Requested-By: pi (1000)
Purge: linux-image-6.1.0-1028-oem:amd64 ()
End-Date: 2024-04-19  13:33:54

Start-Date: 2024-04-19  13:34:24
Commandline: apt-get purge linux-image-6.1.0-1029-oem
Requested-By: pi (1000)
Purge: linux-image-6.1.0-1029-oem:amd64 ()
End-Date: 2024-04-19  13:34:24

Start-Date: 2024-04-19  13:34:45
Commandline: apt-get purge linux-image-6.1.0-1033-oem
Requested-By: pi (1000)
Purge: linux-image-6.1.0-1033-oem:amd64 ()
End-Date: 2024-04-19  13:34:45

Start-Date: 2024-04-19  13:35:06
Commandline: apt-get purge linux-image-6.1.0-1034-oem
Requested-By: pi (1000)
Purge: linux-image-6.1.0-1034-oem:amd64 ()
End-Date: 2024-04-19  13:35:06

Start-Date: 2024-04-19  13:35:26
Commandline: apt-get purge linux-image-6.1.0-1035-oem
Requested-By: pi (1000)
Purge: linux-image-6.1.0-1035-oem:amd64 ()
End-Date: 2024-04-19  13:35:26

Start-Date: 2024-04-19  13:35:43
Commandline: apt-get purge linux-image-6.1.0-1036-oem
Requested-By: pi (1000)
Purge: linux-image-6.1.0-1036-oem:amd64 ()
End-Date: 2024-04-19  13:35:43

Start-Date: 2024-04-19  13:37:39
Commandline: apt-get purge linux-image-6.5.0-1019-oem
Requested-By: pi (1000)
Install: linux-headers-6.5.0-1020-oem:amd64 (6.5.0-1020.21, automatic), 
linux-image-6.5.0-1020-oem:amd64 (6.5.0-1020.21, automatic), 
linux-modules-6.5.0-1020-oem:amd64 (6.5.0-1020.21, automatic), 
linux-oem-6.5-headers-6.5.0-1020:amd64 (6.5.0-1020.21, automatic)
Upgrade: linux-headers-oem-22.04:amd64 (6.5.0.1019.21, 6.5.0.1020.22), 
linux-image-oem-22.04d:amd64 (6.5.0.1019.21, 6.5.0.1020.22), 
linux-oem-22.04d:amd64 (6.5.0.1019.21, 6.5.0.1020.22), linux-oem-22.04:amd64 
(6.5.0.1019.21, 6.5.0.1020.22), linux-headers-oem-22.04d:amd64 (6.5.0.1019.21, 
6.5.0.1020.22), linux-image-oem-22.04:amd64 (6.5.0.1019.21, 6.5.0.1020.22)
Purge: linux-image-6.5.0-1019-oem:amd64 (6.5.0-1019.20)
End-Date: 2024-04-19  13:38:06

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

Title:
  Still, No keybord after kernel update Linux t-l15 6.5.0-1020-oem

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  I use the ThinkPad L15 Gen4, BIOS version R24ET38W(1.21) together with
  Xubuntu 22.04.04 LTS kernel 6.5.0-1020-oem, the CPU type is i7-1355U.
  This combination gives still a not working keyboard after booting.

  Today the system has upgraded the kernel to Linux version
  6.5.0-1020-oem this should solves the keyboard problem introduced in
  kernel 6.5.0-1019-oem and already reported in:

  - https://bugs.launchpad.net/bugs/2060727
  - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060866

  This bug fix does not work, I still have no internal keyboard.

  For the moment I am using kernel 6.5.0-1018-oem which workes fine.

  Who can/will help?

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


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

[Kernel-packages] [Bug 2062545] [NEW] Still, No keybord after kernel update Linux t-l15 6.5.0-1020-oem

Public bug reported:

Hello,

I use the ThinkPad L15 Gen4, BIOS version R24ET38W(1.21) together with
Xubuntu 22.04.04 LTS kernel 6.5.0-1020-oem, the CPU type is i7-1355U.
This combination gives still a not working keyboard after booting.

Today the system has upgraded the kernel to Linux version 6.5.0-1020-oem
this should solves the keyboard problem introduced in kernel
6.5.0-1019-oem and already reported in:

- https://bugs.launchpad.net/bugs/2060727
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060866

This bug fix does not work, I still have no internal keyboard.

For the moment I am using kernel 6.5.0-1018-oem which workes fine.

Who can/will help?

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

** Attachment added: "dmesg20240419_2020.txt"
   
https://bugs.launchpad.net/bugs/2062545/+attachment/5768187/+files/dmesg20240419_2020.txt

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

Title:
  Still, No keybord after kernel update Linux t-l15 6.5.0-1020-oem

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  I use the ThinkPad L15 Gen4, BIOS version R24ET38W(1.21) together with
  Xubuntu 22.04.04 LTS kernel 6.5.0-1020-oem, the CPU type is i7-1355U.
  This combination gives still a not working keyboard after booting.

  Today the system has upgraded the kernel to Linux version
  6.5.0-1020-oem this should solves the keyboard problem introduced in
  kernel 6.5.0-1019-oem and already reported in:

  - https://bugs.launchpad.net/bugs/2060727
  - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060866

  This bug fix does not work, I still have no internal keyboard.

  For the moment I am using kernel 6.5.0-1018-oem which workes fine.

  Who can/will help?

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


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

[Kernel-packages] [Bug 2062546] [NEW] Ubuntu 22.04 Lock Screen is changing the brightness level automatically - Asus Vivobook

2024-04-19 Thread Madhan

Public bug reported:

Ubuntu 22.04 Lock Screen is changing the brightness level automatically
- Asus Vivobook OLED 15. Also, fingerprint scanner seems not to work.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 19 17:38:06 2024
InstallationDate: Installed on 2024-04-18 (0 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
SourcePackage: linux-signed-hwe-6.5
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  Ubuntu 22.04 Lock Screen is changing the brightness level
  automatically - Asus Vivobook

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

Bug description:
  Ubuntu 22.04 Lock Screen is changing the brightness level
  automatically - Asus Vivobook OLED 15. Also, fingerprint scanner seems
  not to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 17:38:06 2024
  InstallationDate: Installed on 2024-04-18 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  SourcePackage: linux-signed-hwe-6.5
  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-6.5/+bug/2062546/+subscriptions


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

[Kernel-packages] [Bug 2060716] Re: Screen flickering again

2024-04-19 Thread Bastian

I de-installed the nvidia driver completly and can confirm: This solves
the flickering issue.

Installing it again also adds flickering again.

(Using the 535 "tested" driver from the ubuntu distribution.)

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

Title:
  Screen flickering again

Status in linux package in Ubuntu:
  New

Bug description:
  There is random screen flickering with the build of kernel 6.5.0-27.
  Also other builds of 6.5.0 have this flickering.

  The *only* build of this version that does work without flickering is
  6.5.0-13

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-27-generic 6.5.0-27.28
  ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bf 5114 F pipewire
bf 5119 F wireplumber
   /dev/snd/controlC0:  bf 5119 F wireplumber
   /dev/snd/seq:bf 5114 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 18:48:35 2024
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=be4de94b-3fb1-44d1-875a-edcd620dc310
  InstallationDate: Installed on 2016-03-18 (2944 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic 
root=UUID=17026de9-c699-420e-ae96-01ac290b69ef ro quiet splash 
i915.enable_psr=0 vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-27-generic N/A
   linux-backports-modules-6.5.0-27-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.9
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2023
  dmi.bios.release: 1.30
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2VET45W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TK000AGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2VET45W(1.30):bd08/29/2023:br1.30:efr1.11:svnLENOVO:pn20TK000AGE:pvrThinkPadX1ExtremeGen3:rvnLENOVO:rn20TK000AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TK_BU_Think_FM_ThinkPadX1ExtremeGen3:
  dmi.product.family: ThinkPad X1 Extreme Gen 3
  dmi.product.name: 20TK000AGE
  dmi.product.sku: LENOVO_MT_20TK_BU_Think_FM_ThinkPad X1 Extreme Gen 3
  dmi.product.version: ThinkPad X1 Extreme Gen 3
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

Seems apt-upgrade will not download new kernel:
Die folgenden Pakete sind zurückgehalten worden:
  linux-generic linux-headers-generic linux-image-generic 
ubuntu-advantage-tools ubuntu-pro-client-l10n

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

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

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo
  Tue Apr  9 04:11:05 PM CEST 2024 hallo
  Tue Apr  9 04:11:06 PM CEST 2024 hallo
  Tue Apr  9 04:11:07 PM CEST 2024 hallo
  Tue Apr  9 04:11:08 PM CEST 2024 hallo
  Tue Apr  9 04:11:09 PM CEST 2024 hallo
  Tue Apr  9 04:11:10 PM CEST 2024 hallo

  While doing this, both servers tell me, the resource is unavailable

  root@:~# df -h /mnt
  df: /mnt: Resource temporarily unavailable

  root@:~$ df -h /mnt
  df: /mnt: Resource temporarily unavailable

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


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

[Kernel-packages] [Bug 2062534] Re: GDM3 autologin might be racy on GCP resulting in inconsistent state of the wayland setup of seat0

2024-04-19 Thread Jeremy Bícha

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

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

Title:
  GDM3 autologin might be racy on GCP resulting in inconsistent state of
  the wayland setup of seat0

Status in gdm3 package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New

Bug description:
  This might not be a bug really about linux-gcp, but this is following
  the work on bug 2039732 and so far I could not reproduce that locally.

  Setup is 22.04 uptodate on GCP n2-standard instances, without GPU
  attached thus relying on vkms. I have reproduced locally a similar
  setup but on a KVM host.

  We rely on 
https://github.com/taskcluster/taskcluster/tree/main/workers/generic-worker#readme
 to run tasks on CI, and especially generic-worker will:
   - create a new task_XXX user
   - make it autologin in gdm3 config
   - generic-worker has code to probe for existence of the GNOME Wayland 
session before launching the task

  We relied on wl-clipboard package installed for verifying the status
  of wayland

  On top of that setup, here is the issue.

  We issue a TC task with payload:
  > export WAYLAND_DISPLAY=wayland-0
  > export XDG_RUNTIME_DIR=/run/user/$(id -u)
  > wl-paste -l -p

  We expect that payload to report "No selection", but on GCP instances
  we mostly always end up with "This seat has no keyboard". There were
  also cases were the session would not be Wayland at all but rather
  X11. I think this suggests something around the availability of
  /dev/dri/card0, but forcing the gdm3 service to wait for its
  availability and adding extra waiting time after card0 is present
  would still not get us somewhere.

  We enabled gdm3 as well as mutter debugging but never found anything
  that would be a good lead on why it was not yet ready.

  At some point, the seat0 session of our user was shown as inactive and
  the active one was tied to gdm so we suspected this was the reason,
  but both forcing the session to be active and terminating the gdm
  session would still not unblock us.

  We also suspected the desktop to be locking itself so we disabled locking 
with the following, but iit did not help much:
  > cat > /etc/dconf/profile/user << EOF
  > user-db:user
  > system-db:local
  > EOF
  > 
  > mkdir /etc/dconf/db/local.d/
  > # dconf user settings
  > cat > /etc/dconf/db/local.d/00-tc-gnome-settings << EOF
  > # /org/gnome/desktop/session/idle-delay
  > [org/gnome/desktop/session]
  > idle-delay=uint32 0
  > # /org/gnome/desktop/lockdown/disable-lock-screen
  > [org/gnome/desktop/lockdown]
  > disable-lock-screen=true
  > EOF
  > 
  > sudo dconf update

  
  In the end, the only viable and reliable (verified over hundreds of runs now) 
fix that lasted was to add a "/bin/sleep 30" all to the gdm3 startup:
  > mkdir -p /etc/systemd/system/gdm.service.d/
  > cat > /etc/systemd/system/gdm.service.d/gdm-wait.conf << EOF
  > [Unit]
  > Description=Extra 30s wait
  > [Service]
  > ExecStartPre=/bin/sleep 30
  > EOF

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


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

[Kernel-packages] [Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

I'm totally confused now. Last note her says you're wating for confirmation, 
but I got 2 emails telling me, that the fixed kernel has been released now. But 
when I do a apt-get update and apt-get upgrade still 104 will be installed? Did 
I misunderstood something?
Axel

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

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

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo
  Tue Apr  9 04:11:05 PM CEST 2024 hallo
  Tue Apr  9 04:11:06 PM CEST 2024 hallo
  Tue Apr  9 04:11:07 PM CEST 2024 hallo
  Tue Apr  9 04:11:08 PM CEST 2024 hallo
  Tue Apr  9 04:11:09 PM CEST 2024 hallo
  Tue Apr  9 04:11:10 PM CEST 2024 hallo

  While doing this, both servers tell me, the resource is unavailable

  root@:~# df -h /mnt
  df: /mnt: Resource temporarily unavailable

  root@:~$ df -h /mnt
  df: /mnt: Resource temporarily unavailable

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


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

[Kernel-packages] [Bug 2062534] Re: GDM3 autologin might be racy on GCP resulting in inconsistent state of the wayland setup of seat0

2024-04-19 Thread Pirouette Cacahuète

Current kernel is: Linux gecko-t-t-linux-2204-wayland-exp-a2-mld-
sg4dt5wcf-acfajsmq 6.5.0-1017-gcp #17~22.04.1-Ubuntu SMP Thu Mar 14
20:30:38 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  GDM3 autologin might be racy on GCP resulting in inconsistent state of
  the wayland setup of seat0

Status in linux-gcp package in Ubuntu:
  New

Bug description:
  This might not be a bug really about linux-gcp, but this is following
  the work on bug 2039732 and so far I could not reproduce that locally.

  Setup is 22.04 uptodate on GCP n2-standard instances, without GPU
  attached thus relying on vkms. I have reproduced locally a similar
  setup but on a KVM host.

  We rely on 
https://github.com/taskcluster/taskcluster/tree/main/workers/generic-worker#readme
 to run tasks on CI, and especially generic-worker will:
   - create a new task_XXX user
   - make it autologin in gdm3 config
   - generic-worker has code to probe for existence of the GNOME Wayland 
session before launching the task

  We relied on wl-clipboard package installed for verifying the status
  of wayland

  On top of that setup, here is the issue.

  We issue a TC task with payload:
  > export WAYLAND_DISPLAY=wayland-0
  > export XDG_RUNTIME_DIR=/run/user/$(id -u)
  > wl-paste -l -p

  We expect that payload to report "No selection", but on GCP instances
  we mostly always end up with "This seat has no keyboard". There were
  also cases were the session would not be Wayland at all but rather
  X11. I think this suggests something around the availability of
  /dev/dri/card0, but forcing the gdm3 service to wait for its
  availability and adding extra waiting time after card0 is present
  would still not get us somewhere.

  We enabled gdm3 as well as mutter debugging but never found anything
  that would be a good lead on why it was not yet ready.

  At some point, the seat0 session of our user was shown as inactive and
  the active one was tied to gdm so we suspected this was the reason,
  but both forcing the session to be active and terminating the gdm
  session would still not unblock us.

  We also suspected the desktop to be locking itself so we disabled locking 
with the following, but iit did not help much:
  > cat > /etc/dconf/profile/user << EOF
  > user-db:user
  > system-db:local
  > EOF
  > 
  > mkdir /etc/dconf/db/local.d/
  > # dconf user settings
  > cat > /etc/dconf/db/local.d/00-tc-gnome-settings << EOF
  > # /org/gnome/desktop/session/idle-delay
  > [org/gnome/desktop/session]
  > idle-delay=uint32 0
  > # /org/gnome/desktop/lockdown/disable-lock-screen
  > [org/gnome/desktop/lockdown]
  > disable-lock-screen=true
  > EOF
  > 
  > sudo dconf update

  
  In the end, the only viable and reliable (verified over hundreds of runs now) 
fix that lasted was to add a "/bin/sleep 30" all to the gdm3 startup:
  > mkdir -p /etc/systemd/system/gdm.service.d/
  > cat > /etc/systemd/system/gdm.service.d/gdm-wait.conf << EOF
  > [Unit]
  > Description=Extra 30s wait
  > [Service]
  > ExecStartPre=/bin/sleep 30
  > EOF

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


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

[Kernel-packages] [Bug 2062534] [NEW] GDM3 autologin might be racy on GCP resulting in inconsistent state of the wayland setup of seat0

2024-04-19 Thread Pirouette Cacahuète

Public bug reported:

This might not be a bug really about linux-gcp, but this is following
the work on bug 2039732 and so far I could not reproduce that locally.

Setup is 22.04 uptodate on GCP n2-standard instances, without GPU
attached thus relying on vkms. I have reproduced locally a similar setup
but on a KVM host.

We rely on 
https://github.com/taskcluster/taskcluster/tree/main/workers/generic-worker#readme
 to run tasks on CI, and especially generic-worker will:
 - create a new task_XXX user
 - make it autologin in gdm3 config
 - generic-worker has code to probe for existence of the GNOME Wayland session 
before launching the task

We relied on wl-clipboard package installed for verifying the status of
wayland

On top of that setup, here is the issue.

We issue a TC task with payload:
> export WAYLAND_DISPLAY=wayland-0
> export XDG_RUNTIME_DIR=/run/user/$(id -u)
> wl-paste -l -p

We expect that payload to report "No selection", but on GCP instances we
mostly always end up with "This seat has no keyboard". There were also
cases were the session would not be Wayland at all but rather X11. I
think this suggests something around the availability of /dev/dri/card0,
but forcing the gdm3 service to wait for its availability and adding
extra waiting time after card0 is present would still not get us
somewhere.

We enabled gdm3 as well as mutter debugging but never found anything
that would be a good lead on why it was not yet ready.

At some point, the seat0 session of our user was shown as inactive and
the active one was tied to gdm so we suspected this was the reason, but
both forcing the session to be active and terminating the gdm session
would still not unblock us.

We also suspected the desktop to be locking itself so we disabled locking with 
the following, but iit did not help much:
> cat > /etc/dconf/profile/user << EOF
> user-db:user
> system-db:local
> EOF
> 
> mkdir /etc/dconf/db/local.d/
> # dconf user settings
> cat > /etc/dconf/db/local.d/00-tc-gnome-settings << EOF
> # /org/gnome/desktop/session/idle-delay
> [org/gnome/desktop/session]
> idle-delay=uint32 0
> # /org/gnome/desktop/lockdown/disable-lock-screen
> [org/gnome/desktop/lockdown]
> disable-lock-screen=true
> EOF
> 
> sudo dconf update


In the end, the only viable and reliable (verified over hundreds of runs now) 
fix that lasted was to add a "/bin/sleep 30" all to the gdm3 startup:
> mkdir -p /etc/systemd/system/gdm.service.d/
> cat > /etc/systemd/system/gdm.service.d/gdm-wait.conf << EOF
> [Unit]
> Description=Extra 30s wait
> [Service]
> ExecStartPre=/bin/sleep 30
> EOF

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

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

Title:
  GDM3 autologin might be racy on GCP resulting in inconsistent state of
  the wayland setup of seat0

Status in linux-gcp package in Ubuntu:
  New

Bug description:
  This might not be a bug really about linux-gcp, but this is following
  the work on bug 2039732 and so far I could not reproduce that locally.

  Setup is 22.04 uptodate on GCP n2-standard instances, without GPU
  attached thus relying on vkms. I have reproduced locally a similar
  setup but on a KVM host.

  We rely on 
https://github.com/taskcluster/taskcluster/tree/main/workers/generic-worker#readme
 to run tasks on CI, and especially generic-worker will:
   - create a new task_XXX user
   - make it autologin in gdm3 config
   - generic-worker has code to probe for existence of the GNOME Wayland 
session before launching the task

  We relied on wl-clipboard package installed for verifying the status
  of wayland

  On top of that setup, here is the issue.

  We issue a TC task with payload:
  > export WAYLAND_DISPLAY=wayland-0
  > export XDG_RUNTIME_DIR=/run/user/$(id -u)
  > wl-paste -l -p

  We expect that payload to report "No selection", but on GCP instances
  we mostly always end up with "This seat has no keyboard". There were
  also cases were the session would not be Wayland at all but rather
  X11. I think this suggests something around the availability of
  /dev/dri/card0, but forcing the gdm3 service to wait for its
  availability and adding extra waiting time after card0 is present
  would still not get us somewhere.

  We enabled gdm3 as well as mutter debugging but never found anything
  that would be a good lead on why it was not yet ready.

  At some point, the seat0 session of our user was shown as inactive and
  the active one was tied to gdm so we suspected this was the reason,
  but both forcing the session to be active and terminating the gdm
  session would still not unblock us.

  We also suspected the desktop to be locking itself so we disabled locking 
with the following, but iit did not help much:
  > cat > /etc/dconf/profile/user << EOF
  > user-db:user
  > system-db:local
  > EOF
  > 
  > mkdir

[Kernel-packages] [Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

2024-04-19 Thread Ubuntu Kernel Bot

This bug is awaiting verification that the linux-
fips/5.15.0-105.115+fips1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-fips' to
'verification-done-jammy-linux-fips'. If the problem still exists,
change the tag 'verification-needed-jammy-linux-fips' to 'verification-
failed-jammy-linux-fips'.


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


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


** Tags added: kernel-spammed-jammy-linux-fips-v2 
verification-needed-jammy-linux-fips

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

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

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo
  Tue Apr  9 04:11:05 PM CEST 2024 hallo
  Tue Apr  9 04:11:06 PM CEST 2024 hallo
  Tue Apr  9 04:11:07 PM CEST 2024 hallo
  Tue Apr  9 04:11:08 PM CEST 2024 hallo
  Tue Apr  9 04:11:09 PM CEST 2024 hallo
  Tue Apr  9 04:11:10 PM CEST 2024 hallo

  While doing this, both servers tell me, the resource is unavailable

  root@:~# df -h /mnt
  df: /mnt: Resource temporarily unavailable

  root@:~$ df -h /mnt
  df: /mnt: Resource temporarily unavailable

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


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

[Kernel-packages] [Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).

2024-04-19 Thread Peter Mühlenpfordt

Many thanks for the successful investigation!
Running the ppa test kernel I can't reproduce the problem anymore.  :-)

I use two cifs servers running Debian 11, with a couple of shares. With both 
standard kernels (6.5.0-27, 6.5.0-28) copying inside a share fails immediately 
on any server.
My fstab mounts look like this:
//server/store /mnt/store cifs 
credentials=/home/xxx/.smbpass,uid=1000,gid=1000,_netdev 0 0

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

Title:
  Remote filesystems mounted as CIFS not working after update to Kernel
  "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi
  #17-Ubuntu" (aarch64).

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  New
Status in linux-hwe-6.5 package in Ubuntu:
  Confirmed
Status in linux-raspi package in Ubuntu:
  Confirmed

Bug description:
  Remote filesystems mounted as CIFS are not working after update to
  Kernel "6.5.0-27-generic #28-Ubuntu" for x86_64 (and also after
  updating to Kernel "6.5.0-1014-raspi #17-Ubuntu" in aarch64).

  The remote filesystem is correctly mounted and seems to work but
  trying to write data to the filesystem ends in a kernel error
  exception. After that error the CIFS filesystem just became unusable.

  Previous Kernel version works correctly.

  =
  Example for Kernel "6.5.0-27-generic #28-Ubuntu" (x86_64)
  =
  # lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  # uname -a
  Linux fpgmsi 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 
18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 6.5.0-27.28-generic 6.5.13

  
  How to reproduce the problem
  
  For instance, I'm using KeePassXC 
(https://launchpad.net/ubuntu/+source/keepassxc) to update a database located 
at CIFS filesystem. Any change done to that database causes this Kernel error 
exception:

  abr 11 09:34:59 fpgmsi kernel: BUG: unable to handle page fault for address: 
fffe
  abr 11 09:34:59 fpgmsi kernel: #PF: supervisor read access in kernel mode
  abr 11 09:34:59 fpgmsi kernel: #PF: error_code(0x) - not-present page
  abr 11 09:34:59 fpgmsi kernel: PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 
0 
  abr 11 09:34:59 fpgmsi kernel: Oops:  [#1] PREEMPT SMP NOPTI
  abr 11 09:34:59 fpgmsi kernel: CPU: 0 PID: 28103 Comm: Thread (pooled) 
Tainted: P   OE  6.5.0-27-generic #28-Ubuntu
  abr 11 09:34:59 fpgmsi kernel: Hardware name: Micro-Star International Co., 
Ltd. MAG Z690 Codex X5 (MS-B930)/PRO Z690-A WIFI (MS-7D25), BIOS D.50 04/26/2022
  abr 11 09:34:59 fpgmsi kernel: RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel: Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 
0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 
db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3
  abr 11 09:34:59 fpgmsi kernel: RSP: 0018:aab6865ffbf8 EFLAGS: 00010282
  abr 11 09:34:59 fpgmsi kernel: RAX:  RBX: fffe 
RCX: 
  abr 11 09:34:59 fpgmsi kernel: RDX:  RSI:  
RDI: 
  abr 11 09:34:59 fpgmsi kernel: RBP: aab6865ffc28 R08: 0001 
R09: 
  abr 11 09:34:59 fpgmsi kernel: R10: 00023854 R11:  
R12: 
  abr 11 09:34:59 fpgmsi kernel: R13: aab6865ffc78 R14: 906675d8aed0 
R15: aab6865ffc70
  abr 11 09:34:59 fpgmsi kernel: FS:  7bd4d594b6c0() 
GS:90753f80() knlGS:
  abr 11 09:34:59 fpgmsi kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000 
CR4: 00750ef0
  abr 11 09:34:59 fpgmsi kernel: PKRU: 5554
  abr 11 09:34:59 fpgmsi kernel: Call Trace:
  abr 11 09:34:59 fpgmsi kernel:  
  abr 11 09:34:59 fpgmsi kernel:  ? show_regs+0x6d/0x80
  abr 11 09:34:59 fpgmsi kernel:  ? __die+0x24/0x80
  abr 11 09:34:59 fpgmsi kernel:  ? page_fault_oops+0x99/0x1b0
  abr 11 09:34:59 fpgmsi kernel:  ? kernelmode_fixup_or_oops+0xb2/0x140
  abr 11 09:34:59 fpgmsi kernel:  ? __bad_area_nosemaphore+0x1a5/0x2c0
  abr 11 09:34:59 fpgmsi kernel:  ? bad_area_nosemaphore+0x16/0x30
  abr 11 09:34:59 fpgmsi kernel:  ? do_kern_addr_fault+0x7b/0xa0
  abr 11 09:34:59 fpgmsi kernel:  ? exc_page_fault+0x1a4/0x1b0
  abr 11 09:34:59 fpgmsi kernel:  ? asm_exc_page_fault+0x27/0x30
  abr 11 09:34:59 fpgmsi kernel:  ? cifs_flush_folio+0x41/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  ? cifs_flush_folio+0x37/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel:

[Kernel-packages] [Bug 2060716] Re: Screen flickering again

2024-04-19 Thread AaronMa

Hi,

The system is about 3 years ago, I can't find one to reproduce. Your
help will be great.

I found many nv uvm error in dmesg,
Please uninstall nvidia-driver to check if it's caused by it.

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

Title:
  Screen flickering again

Status in linux package in Ubuntu:
  New

Bug description:
  There is random screen flickering with the build of kernel 6.5.0-27.
  Also other builds of 6.5.0 have this flickering.

  The *only* build of this version that does work without flickering is
  6.5.0-13

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-27-generic 6.5.0-27.28
  ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bf 5114 F pipewire
bf 5119 F wireplumber
   /dev/snd/controlC0:  bf 5119 F wireplumber
   /dev/snd/seq:bf 5114 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 18:48:35 2024
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=be4de94b-3fb1-44d1-875a-edcd620dc310
  InstallationDate: Installed on 2016-03-18 (2944 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic 
root=UUID=17026de9-c699-420e-ae96-01ac290b69ef ro quiet splash 
i915.enable_psr=0 vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-27-generic N/A
   linux-backports-modules-6.5.0-27-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.9
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2023
  dmi.bios.release: 1.30
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2VET45W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TK000AGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2VET45W(1.30):bd08/29/2023:br1.30:efr1.11:svnLENOVO:pn20TK000AGE:pvrThinkPadX1ExtremeGen3:rvnLENOVO:rn20TK000AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TK_BU_Think_FM_ThinkPadX1ExtremeGen3:
  dmi.product.family: ThinkPad X1 Extreme Gen 3
  dmi.product.name: 20TK000AGE
  dmi.product.sku: LENOVO_MT_20TK_BU_Think_FM_ThinkPad X1 Extreme Gen 3
  dmi.product.version: ThinkPad X1 Extreme Gen 3
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2060716] Re: Screen flickering again

2024-04-19 Thread Bastian

Thanks for your reply. I tested now both PSR settings, and the results
are

There is no screen flickering in 6.5.0-13, regardless of enable_psr=0 or
enable_psr=1

There is always screen flickering (every 1-2 minutes) in 6.5.0-27,
regardless of enable_psr=0 or enable_psr=1

So PSR seems to have no influence on this issue.

I Also attached the edid-Data from
/sys/devices/pci:00/:00:02.0/drm/card0/card0-eDP-1/edid



** Attachment added: "edid.dat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060716/+attachment/5768138/+files/edid.dat

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

Title:
  Screen flickering again

Status in linux package in Ubuntu:
  New

Bug description:
  There is random screen flickering with the build of kernel 6.5.0-27.
  Also other builds of 6.5.0 have this flickering.

  The *only* build of this version that does work without flickering is
  6.5.0-13

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-27-generic 6.5.0-27.28
  ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bf 5114 F pipewire
bf 5119 F wireplumber
   /dev/snd/controlC0:  bf 5119 F wireplumber
   /dev/snd/seq:bf 5114 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 18:48:35 2024
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=be4de94b-3fb1-44d1-875a-edcd620dc310
  InstallationDate: Installed on 2016-03-18 (2944 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic 
root=UUID=17026de9-c699-420e-ae96-01ac290b69ef ro quiet splash 
i915.enable_psr=0 vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-27-generic N/A
   linux-backports-modules-6.5.0-27-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.9
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2023
  dmi.bios.release: 1.30
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2VET45W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TK000AGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2VET45W(1.30):bd08/29/2023:br1.30:efr1.11:svnLENOVO:pn20TK000AGE:pvrThinkPadX1ExtremeGen3:rvnLENOVO:rn20TK000AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TK_BU_Think_FM_ThinkPadX1ExtremeGen3:
  dmi.product.family: ThinkPad X1 Extreme Gen 3
  dmi.product.name: 20TK000AGE
  dmi.product.sku: LENOVO_MT_20TK_BU_Think_FM_ThinkPad X1 Extreme Gen 3
  dmi.product.version: ThinkPad X1 Extreme Gen 3
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

2024-04-19 Thread antst

if fixed zfs packages are pushed to the release, then user will have an
option to use DKMS at least (as I do now)

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

Title:
  Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

Status in Native ZFS for Linux:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in zfs-linux package in Ubuntu:
  Confirmed
Status in systemd source package in Noble:
  Triaged
Status in zfs-linux source package in Noble:
  Confirmed

Bug description:
  As per https://github.com/openzfs/zfs/issues/15930

  ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
  copy_file_range, breaking a multitude of applications.

  Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
  2.2.2.

  One notable issue is when running Root on ZFS: systemd-sysusers will
  always fail to create users/groups with the error "Failed to backup
  /etc/{group,passwd}: Operation not supported" due to the call to
  copy_file_range.

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


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

[Kernel-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

2024-04-19 Thread Timo Aaltonen

oh, it needs the kernel module to be rebuilt for the fix.. don't think
we have time for that anymore before the release.

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

Title:
  Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

Status in Native ZFS for Linux:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in zfs-linux package in Ubuntu:
  Confirmed
Status in systemd source package in Noble:
  Triaged
Status in zfs-linux source package in Noble:
  Confirmed

Bug description:
  As per https://github.com/openzfs/zfs/issues/15930

  ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
  copy_file_range, breaking a multitude of applications.

  Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
  2.2.2.

  One notable issue is when running Root on ZFS: systemd-sysusers will
  always fail to create users/groups with the error "Failed to backup
  /etc/{group,passwd}: Operation not supported" due to the call to
  copy_file_range.

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


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

[Kernel-packages] Antw: [Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

Thanks a lot !
Axel
>>> engaging374 <2060...@bugs.launchpad.net> 19.04.2024 10:16 >>>
@Alex

Well it's officially released now. It's up to you to install the patch.
:-)

I think someone needs to verify the patch as soon as it's in -proposed
state. Without verification it will be dropped from the source code. (
-> no official fix will be provided in -updates.)

Normally it's not the case if multiple users are affected. Someone just
needs to do the verification work.

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/2060780


Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

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

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo
  Tue Apr  9 04:11:05 PM CEST 2024 hallo
  Tue Apr  9 04:11:06 PM CEST 2024 hallo
  Tue Apr  9 04:11:07 PM CEST 2024 hallo
  Tue Apr  9 04:11:08 PM CEST 2024 hallo
  Tue Apr  9 04:11:09 PM CEST 2024 hallo
  Tue Apr  9 04:11:10 PM CEST 2024 hallo

  While doing this, both servers tell me, the resource is unavailable

  root@:~# df -h /mnt
  df: /mnt: Resource temporarily unavailable

  root@:~$ df -h /mnt
  df: /mnt: Resource temporarily unavailable

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

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

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

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo

[Kernel-packages] [Bug 2045560] Re: TCP memory leak, slow network (arm64)

2024-04-19 Thread Jonathan Heathcote

I've been digging into this and this appears to be a regression
introduced by the following patch
https://github.com/torvalds/linux/commit/3cd3399dd7a84 which was first
released in Linux 6.0.0.

The bug is not a memory leak but rather a bug in how memory usage is
counted. Excess memory is not actually being consumed, though the bug is
still fatal since the counter controls Linux's memory pressure logic.

The (apparently) responsible patch is a performance optimisation which
attempts to reduce the frequency of writes to the system-wide counter
which (I suspect) is subtly misusing some atomic operation on ARM. If
you undo this patch in a recent kernel, the bug disappears.

I am currently working on a detailed bug report for the relevant Kernel
maintainers.

NB: It appears that the "5.15" kernel shipped by Rocky (and RHEL)
includes a back-port of this bug, hence my seeing the bug in that kernel
version on Rocky Linux. A non-RedHat-patched vanilla build of 5.15 does
not exhibit the bug in my system either.

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

Title:
  TCP memory  leak, slow network (arm64)

Status in linux-signed-aws-6.2 package in Ubuntu:
  Confirmed

Bug description:
  Hello! 

  We have Ubuntu OS-based servers running in both AWS and Azure clouds.
  These servers are handling thousands of connections, and we've been
  experiencing issues with TCP memory usage since upgrading to Ubuntu
  22.04.3 from 22.04.2.

  $ cat /proc/net/sockstat
  sockets: used 6642
  TCP: inuse 5962 orphan 0 tw 292 alloc 6008 mem 128989
  UDP: inuse 5 mem 0
  UDPLITE: inuse 0
  RAW: inuse 0
  FRAG: inuse 0 memory 0

  As shown in the output below, even after stopping all possible
  services and closing all open connections, the TCP memory usage
  remains high and only decreases very slowly.

  $ cat /proc/net/sockstat
  sockets: used 138
  TCP: inuse 2 orphan 0 tw 0 alloc 3 mem 128320
  UDP: inuse 3 mem 0
  UDPLITE: inuse 0
  RAW: inuse 0
  FRAG: inuse 0 memory 0

  I have attached a screenshot of linear TCP memory usage growth, which
  we believe may indicate a TCP memory leak

  When net.ipv4.tcp_mem limit is reached, it causes network slowdown

  We've never had these issues before, and the only solution we've found
  so far is to reboot the node. Do you have any suggestions on how to
  troubleshoot further?

  Thank you for any help or guidance you can provide!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-1015-aws 6.2.0-1015.15~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-1015.15~22.04.1-aws 6.2.16
  Uname: Linux 6.2.0-1015-aws aarch64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudID: aws
  CloudName: aws
  CloudPlatform: ec2
  CloudRegion: us-west-2
  CloudSubPlatform: metadata (http://169.254.169.254)
  Date: Mon Dec  4 13:13:08 2023
  Ec2AMI: ami-095a68e28e781dfe1
  Ec2AMIManifest: (unknown)
  Ec2Architecture: arm64
  Ec2AvailabilityZone: us-west-2b
  Ec2Imageid: ami-095a68e28e781dfe1
  Ec2InstanceType: m7g.large
  Ec2Instancetype: m7g.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Ec2Region: us-west-2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-aws-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).

2024-04-19 Thread johnfoss

In my reproduction environment i am testing against synology smb server
too.

now when i boot the test kernel:
$ uname -rv
6.5.0-27-generic #28~22.04.1+TEST2060919v20240419b1-Ubuntu SMP PREEMPT_DYNAMIC 
Fr
sudo mount -t cifs -o username=jan,uid=1001,gid=1001 //192.168.8.3/home 
testhome/
nautilus testhome
everything works in nautilus and with cp :-)

Thank you very much Matthew Ruffell (mruffell)


When i run current kernel only nautilus File-Manager copy funktion is affected 
here !
I mean i can use cp in terminal without getting a stracktrace in kernel 
linux-image-6.5.0-28-generic

when i do this:
$ uname -rv
6.5.0-28-generic #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr  4 14:39:20 UTC 
2
$ sudo mount -t cifs -o username=ubuntu,$(id -u),gid=$(id -g) 
//192.168.8.3/home testhome/
nautilus testhome
copy any file in testhome to testhome

i get attached stacktrace

** Attachment added: "6.5.0-28-generic_stacktrace"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+attachment/5768110/+files/stacktrace.txt

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

Title:
  Remote filesystems mounted as CIFS not working after update to Kernel
  "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi
  #17-Ubuntu" (aarch64).

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  New
Status in linux-hwe-6.5 package in Ubuntu:
  Confirmed
Status in linux-raspi package in Ubuntu:
  Confirmed

Bug description:
  Remote filesystems mounted as CIFS are not working after update to
  Kernel "6.5.0-27-generic #28-Ubuntu" for x86_64 (and also after
  updating to Kernel "6.5.0-1014-raspi #17-Ubuntu" in aarch64).

  The remote filesystem is correctly mounted and seems to work but
  trying to write data to the filesystem ends in a kernel error
  exception. After that error the CIFS filesystem just became unusable.

  Previous Kernel version works correctly.

  =
  Example for Kernel "6.5.0-27-generic #28-Ubuntu" (x86_64)
  =
  # lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  # uname -a
  Linux fpgmsi 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 
18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 6.5.0-27.28-generic 6.5.13

  
  How to reproduce the problem
  
  For instance, I'm using KeePassXC 
(https://launchpad.net/ubuntu/+source/keepassxc) to update a database located 
at CIFS filesystem. Any change done to that database causes this Kernel error 
exception:

  abr 11 09:34:59 fpgmsi kernel: BUG: unable to handle page fault for address: 
fffe
  abr 11 09:34:59 fpgmsi kernel: #PF: supervisor read access in kernel mode
  abr 11 09:34:59 fpgmsi kernel: #PF: error_code(0x) - not-present page
  abr 11 09:34:59 fpgmsi kernel: PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 
0 
  abr 11 09:34:59 fpgmsi kernel: Oops:  [#1] PREEMPT SMP NOPTI
  abr 11 09:34:59 fpgmsi kernel: CPU: 0 PID: 28103 Comm: Thread (pooled) 
Tainted: P   OE  6.5.0-27-generic #28-Ubuntu
  abr 11 09:34:59 fpgmsi kernel: Hardware name: Micro-Star International Co., 
Ltd. MAG Z690 Codex X5 (MS-B930)/PRO Z690-A WIFI (MS-7D25), BIOS D.50 04/26/2022
  abr 11 09:34:59 fpgmsi kernel: RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel: Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 
0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 
db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3
  abr 11 09:34:59 fpgmsi kernel: RSP: 0018:aab6865ffbf8 EFLAGS: 00010282
  abr 11 09:34:59 fpgmsi kernel: RAX:  RBX: fffe 
RCX: 
  abr 11 09:34:59 fpgmsi kernel: RDX:  RSI:  
RDI: 
  abr 11 09:34:59 fpgmsi kernel: RBP: aab6865ffc28 R08: 0001 
R09: 
  abr 11 09:34:59 fpgmsi kernel: R10: 00023854 R11:  
R12: 
  abr 11 09:34:59 fpgmsi kernel: R13: aab6865ffc78 R14: 906675d8aed0 
R15: aab6865ffc70
  abr 11 09:34:59 fpgmsi kernel: FS:  7bd4d594b6c0() 
GS:90753f80() knlGS:
  abr 11 09:34:59 fpgmsi kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000 
CR4: 00750ef0
  abr 11 09:34:59 fpgmsi kernel: PKRU: 5554
  abr 11 09:34:59 fpgmsi kernel: Call Trace:
  abr 11 09:34:59 fpgmsi kernel:  
  abr 11 09:34:59 fpgmsi kernel:  ? show_regs+0x6d/0x80
  abr 11 09:34:59 fpgmsi kernel:  ? __die+0x24/0x80
  abr 11 09:34:59 fpgmsi kernel:  ?

[Kernel-packages] [Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

2024-04-19 Thread engaging374

@Alex

Well it's officially released now. It's up to you to install the patch.
:-)

I think someone needs to verify the patch as soon as it's in -proposed
state. Without verification it will be dropped from the source code. (
-> no official fix will be provided in -updates.)

Normally it's not the case if multiple users are affected. Someone just
needs to do the verification work.

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

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

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo
  Tue Apr  9 04:11:05 PM CEST 2024 hallo
  Tue Apr  9 04:11:06 PM CEST 2024 hallo
  Tue Apr  9 04:11:07 PM CEST 2024 hallo
  Tue Apr  9 04:11:08 PM CEST 2024 hallo
  Tue Apr  9 04:11:09 PM CEST 2024 hallo
  Tue Apr  9 04:11:10 PM CEST 2024 hallo

  While doing this, both servers tell me, the resource is unavailable

  root@:~# df -h /mnt
  df: /mnt: Resource temporarily unavailable

  root@:~$ df -h /mnt
  df: /mnt: Resource temporarily unavailable

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


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

[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one

2024-04-19 Thread Ubuntu Foundations Team Bug Bot

The attachment
"ipu6-drivers_0~git202404110253.97c94720-0ubuntu1~ppa.1.debdiff" seems
to be a debdiff.  The ubuntu-sponsors team has been subscribed to the
bug report so that they can review and hopefully sponsor the debdiff.
If the attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  obsolete out-of-tree ivsc dkms in favor of in-tree one

Status in ipu6-drivers package in Ubuntu:
  In Progress
Status in ivsc-driver package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.8 package in Ubuntu:
  In Progress
Status in ipu6-drivers source package in Noble:
  In Progress
Status in ivsc-driver source package in Noble:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.8 source package in Noble:
  In Progress

Bug description:
  [SRU Justification]

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

  [Impact]

  Starting from kernel v6.8, Intel demands the use of in-tree VSC driver
  instead of the out-of-tree dkms originated from
  https://github.com/intel/ivsc-driver.

  [Fix]

  The in-tree vsc driver as of v6.8 still need a few fixes to archive
  the same supportness to launched Intel IPU6 Camera devices. Commit
  1,3, and 4 are to add supported devices and platforms. Commit 2
  resolves an issue after resumed.

  [Test Case]

  This is supposed to work together with the updated dkms, which shall
  also be built along with the kernel itself as linux-modules-
  ipu6-. Install the corresponding kernel/modules packages and
  test camera functions.

  [Where problems could occur]

  While this is the first time we switch to in-tree VSC driver, and the
  out-of-tree driver is not aligned at the time of transition and
  probably never will, the provided functions and verified stability
  issues may vary.

  [Other Info]

  The dkms is created to be compatible of multiple versions, yet the in-
  tree vsc driver transitioning should only happen for kernel >= v6.8.
  That is, oem-6.8, noble and linux-unstable will be nominated.

  == original bug description ==

  Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel
  demands the use of in-tree IVSC drivers instead of out-of-tree dkms
  from https://github.com/intel/ivsc-driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+subscriptions


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

[Kernel-packages] [Bug 2062518] [NEW] package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to install/upgrade: installed linux-headers-6.5.0-28-generic package post-installation script subprocess

2024-04-19 Thread chris Livermore

Public bug reported:

Softweare updater continually failing on this.

ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-28-generic 6.5.0-28.29
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  chris  1642 F pipewire
  chris  1646 F wireplumber
 /dev/snd/controlC0:  chris  1646 F wireplumber
 /dev/snd/seq:chris  1642 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Fri Apr 19 08:58:51 2024
ErrorMessage: installed linux-headers-6.5.0-28-generic package 
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2024-04-17 (1 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
IwConfig:
 lono wireless extensions.
 
 wlp109s0f0  no wireless extensions.
 
 enx7e345242890a  no wireless extensions.
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic 
root=UUID=5db60d46-8e67-48c1-a78a-be0d6b68e193 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
SourcePackage: linux
Title: package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to 
install/upgrade: installed linux-headers-6.5.0-28-generic package 
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to mantic on 2024-04-18 (1 days ago)
dmi.bios.date: 03/14/2024
dmi.bios.release: 1.2
dmi.bios.vendor: Alienware
dmi.bios.version: 1.2.1
dmi.board.name: 0KVPC9
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Alienware
dmi.ec.firmware.release: 1.2
dmi.modalias: 
dmi:bvnAlienware:bvr1.2.1:bd03/14/2024:br1.2:efr1.2:svnAlienware:pnAlienwarem18R2:pvr:rvnAlienware:rn0KVPC9:rvrA00:cvnAlienware:ct10:cvr:sku0C9D:
dmi.product.family: Alienware
dmi.product.name: Alienware m18 R2
dmi.product.sku: 0C9D
dmi.sys.vendor: Alienware

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


** Tags: amd64 apport-package mantic need-duplicate-check

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

Title:
  package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to
  install/upgrade: installed linux-headers-6.5.0-28-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  Softweare updater continually failing on this.

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-headers-6.5.0-28-generic 6.5.0-28.29
  ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  1642 F pipewire
chris  1646 F wireplumber
   /dev/snd/controlC0:  chris  1646 F wireplumber
   /dev/snd/seq:chris  1642 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Fri Apr 19 08:58:51 2024
  ErrorMessage: installed linux-headers-6.5.0-28-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2024-04-17 (1 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  IwConfig:
   lono wireless extensions.
   
   wlp109s0f0  no wireless extensions.
   
   enx7e345242890a  no wireless extensions.
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic 
root=UUID=5db60d46-8e67-48c1-a78a-be0d6b68e193 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
  SourcePackage: linux
  Title: package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to 
install/upgrade: installed linux-headers-6.5.0-28-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to mantic on 2024-04-18 (1 days ago)
  dmi.bios.date: 03/14/2024
  dmi.bios.release: 1.2
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.2.1
  dmi.board.name: 0KVPC9
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware

[Kernel-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

2024-04-19 Thread Timo Aaltonen

and a build is available at

https://launchpad.net/~john-cabaj/+archive/ubuntu/zfs-splice-
fix/+packages

feel free to test before it is available in noble

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

Title:
  Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

Status in Native ZFS for Linux:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in zfs-linux package in Ubuntu:
  Confirmed
Status in systemd source package in Noble:
  Triaged
Status in zfs-linux source package in Noble:
  Confirmed

Bug description:
  As per https://github.com/openzfs/zfs/issues/15930

  ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
  copy_file_range, breaking a multitude of applications.

  Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
  2.2.2.

  One notable issue is when running Root on ZFS: systemd-sysusers will
  always fail to create users/groups with the error "Failed to backup
  /etc/{group,passwd}: Operation not supported" due to the call to
  copy_file_range.

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


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

[Kernel-packages] [Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

2024-04-19 Thread engaging374

Hi Matthew,

tested Jammy & Focal (hwe). Looks good for me. :-)

Thank you & the Kernel Team!

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

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

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

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo
  Tue Apr  9 04:11:05 PM CEST 2024 hallo
  Tue Apr  9 04:11:06 PM CEST 2024 hallo
  Tue Apr  9 04:11:07 PM CEST 2024 hallo
  Tue Apr  9 04:11:08 PM CEST 2024 hallo
  Tue Apr  9 04:11:09 PM CEST 2024 hallo
  Tue Apr  9 04:11:10 PM CEST 2024 hallo

  While doing this, both servers tell me, the resource is unavailable

  root@:~# df -h /mnt
  df: /mnt: Resource temporarily unavailable

  root@:~$ df -h /mnt
  df: /mnt: Resource temporarily unavailable

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


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

[Kernel-packages] [Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

This bug was the first time I came into this forum, so sorry if this a dumb 
question:
today I got 3 emails that that a fix might be available and I have to test it. 
If I do nbot the fix will be removed from kernel?
Really? Is it really needed that I do some tests after so many already did? 
Currently I'm out of office so it's complicated to test anything.
As far as I understand it is already fixed and 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/2060780

Title:
  CIFS stopped working/is unstable with kernel update to 5.15.0-102.112

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

Bug description:
  Hi,

  updated some Ubuntu 22.04 systems to lastest available state this
  morning, which caused CIFS mounts (from various fileservers) to stop
  working. Kernel was updated to version 5.15.0-102-generic.

  I can mount the shares without problems (mount -t cifs), but then, df for 
example tells me: df: /mnt: Resource temporarily unavailable.
  I'm able to list and browse all the files, but accessing them (even readonly) 
is very unstable. Sometimes it works and sometimes it just gives me i/o errors. 

  Switching back to  5.15.0-101-generic or 5.15.0-100-generic solves the
  problem and everything works again as expected.

  Seems like some bug has been implemented in 5.15.0-102-generic...

  To reproduce the problem, I started a while loop on one server to
  write to some file on a specific mounted CIFS share and read it from
  another one

  root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; 
sleep 1 ; done
  -bash: /mnt/hallo.txt: Input/output error
  -bash: /mnt/hallo.txt: Input/output error
  ^C

  root@:~$ tail -f /mnt/hallo.txt
  Tue Apr  9 04:10:52 PM CEST 2024 hallo
  Tue Apr  9 04:10:53 PM CEST 2024 hallo
  Tue Apr  9 04:10:54 PM CEST 2024 hallo
  Tue Apr  9 04:10:55 PM CEST 2024 hallo
  Tue Apr  9 04:10:56 PM CEST 2024 hallo
  Tue Apr  9 04:10:57 PM CEST 2024 hallo
  Tue Apr  9 04:10:58 PM CEST 2024 hallo
  Tue Apr  9 04:10:59 PM CEST 2024 hallo
  Tue Apr  9 04:11:00 PM CEST 2024 hallo
  Tue Apr  9 04:11:01 PM CEST 2024 hallo
  tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: 
Resource temporarily unavailable
  Tue Apr  9 04:11:04 PM CEST 2024 hallo
  Tue Apr  9 04:11:05 PM CEST 2024 hallo
  Tue Apr  9 04:11:06 PM CEST 2024 hallo
  Tue Apr  9 04:11:07 PM CEST 2024 hallo
  Tue Apr  9 04:11:08 PM CEST 2024 hallo
  Tue Apr  9 04:11:09 PM CEST 2024 hallo
  Tue Apr  9 04:11:10 PM CEST 2024 hallo

  While doing this, both servers tell me, the resource is unavailable

  root@:~# df -h /mnt
  df: /mnt: Resource temporarily unavailable

  root@:~$ df -h /mnt
  df: /mnt: Resource temporarily unavailable

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


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

[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one

2024-04-19 Thread You-Sheng Yang

PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2061747

Proposed DKMS update for ipu6-drivers/noble based on new upstream
release Release_20240409.

Need sponsor.

** Patch added: "ipu6-drivers_0~git202404110253.97c94720-0ubuntu1~ppa.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.8/+bug/2061747/+attachment/5768025/+files/ipu6-drivers_0~git202404110253.97c94720-0ubuntu1~ppa.1.debdiff

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

Title:
  obsolete out-of-tree ivsc dkms in favor of in-tree one

Status in ipu6-drivers package in Ubuntu:
  In Progress
Status in ivsc-driver package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.8 package in Ubuntu:
  In Progress
Status in ipu6-drivers source package in Noble:
  In Progress
Status in ivsc-driver source package in Noble:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.8 source package in Noble:
  In Progress

Bug description:
  [SRU Justification]

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

  [Impact]

  Starting from kernel v6.8, Intel demands the use of in-tree VSC driver
  instead of the out-of-tree dkms originated from
  https://github.com/intel/ivsc-driver.

  [Fix]

  The in-tree vsc driver as of v6.8 still need a few fixes to archive
  the same supportness to launched Intel IPU6 Camera devices. Commit
  1,3, and 4 are to add supported devices and platforms. Commit 2
  resolves an issue after resumed.

  [Test Case]

  This is supposed to work together with the updated dkms, which shall
  also be built along with the kernel itself as linux-modules-
  ipu6-. Install the corresponding kernel/modules packages and
  test camera functions.

  [Where problems could occur]

  While this is the first time we switch to in-tree VSC driver, and the
  out-of-tree driver is not aligned at the time of transition and
  probably never will, the provided functions and verified stability
  issues may vary.

  [Other Info]

  The dkms is created to be compatible of multiple versions, yet the in-
  tree vsc driver transitioning should only happen for kernel >= v6.8.
  That is, oem-6.8, noble and linux-unstable will be nominated.

  == original bug description ==

  Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel
  demands the use of in-tree IVSC drivers instead of out-of-tree dkms
  from https://github.com/intel/ivsc-driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+subscriptions


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

[Kernel-packages] [Bug 2061894] Re: package linux-image-6.8.0-22-generic 6.8.0-22.22 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11

2024-04-19 Thread Alex Murray

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package linux-image-6.8.0-22-generic 6.8.0-22.22 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with
  return code 11

Status in dkms package in Ubuntu:
  New

Bug description:
  After installing the Nvidia driver, the error was reported. The card
  is nvidia quadro p3200 and the driver is Nvidia-driver-550.

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-22-generic 6.8.0-22.22
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs nvidia_modeset nvidia
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:opi3942 F pipewire
   /dev/snd/controlC0:  opi3945 F wireplumber
   /dev/snd/controlC1:  opi3945 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Apr 16 20:58:41 2024
  ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  InstallationDate: Installed on 2024-04-05 (12 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 0a5c:5832 Broadcom Corp. 5880
   Bus 001 Device 003: ID 0bda:58f6 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 005: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth 
Adapter
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: Dell Inc. Precision 7530
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.12, Python 3.12.2, python3-minimal, 
3.12.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.12-1ubuntu7
  SourcePackage: dkms
  Title: package linux-image-6.8.0-22-generic 6.8.0-22.22 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  UpgradeStatus: Upgraded to noble on 2024-04-15 (1 days ago)
  dmi.bios.date: 01/28/2024
  dmi.bios.release: 1.33
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.33.0
  dmi.board.name: 07NCNV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.33.0:bd01/28/2024:br1.33:svnDellInc.:pnPrecision7530:pvr:rvnDellInc.:rn07NCNV:rvrA00:cvnDellInc.:ct10:cvr:sku0831:
  dmi.product.family: Precision
  dmi.product.name: Precision 7530
  dmi.product.sku: 0831
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).

Tested:

# uname -rv
6.5.0-27-generic #28+TEST2060919v20240419b1-Ubuntu SMP PREEMPT_DYNAMIC Fri Apr 
19

# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 23.10
Release:23.10
Codename:   mantic

# cd /mnt/fpgnas/tmp
/mnt/fpgnas/tmp# touch sample1.txt
/mnt/fpgnas/tmp# cp sample1.txt sample2.txt

Success!

I've tested some other cases as well and CIFS works as expected for all
of them. So I think you have find the culprit.

Thank you very much.

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

Title:
  Remote filesystems mounted as CIFS not working after update to Kernel
  "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi
  #17-Ubuntu" (aarch64).

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  New
Status in linux-hwe-6.5 package in Ubuntu:
  Confirmed
Status in linux-raspi package in Ubuntu:
  Confirmed

Bug description:
  Remote filesystems mounted as CIFS are not working after update to
  Kernel "6.5.0-27-generic #28-Ubuntu" for x86_64 (and also after
  updating to Kernel "6.5.0-1014-raspi #17-Ubuntu" in aarch64).

  The remote filesystem is correctly mounted and seems to work but
  trying to write data to the filesystem ends in a kernel error
  exception. After that error the CIFS filesystem just became unusable.

  Previous Kernel version works correctly.

  =
  Example for Kernel "6.5.0-27-generic #28-Ubuntu" (x86_64)
  =
  # lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  # uname -a
  Linux fpgmsi 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 
18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 6.5.0-27.28-generic 6.5.13

  
  How to reproduce the problem
  
  For instance, I'm using KeePassXC 
(https://launchpad.net/ubuntu/+source/keepassxc) to update a database located 
at CIFS filesystem. Any change done to that database causes this Kernel error 
exception:

  abr 11 09:34:59 fpgmsi kernel: BUG: unable to handle page fault for address: 
fffe
  abr 11 09:34:59 fpgmsi kernel: #PF: supervisor read access in kernel mode
  abr 11 09:34:59 fpgmsi kernel: #PF: error_code(0x) - not-present page
  abr 11 09:34:59 fpgmsi kernel: PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 
0 
  abr 11 09:34:59 fpgmsi kernel: Oops:  [#1] PREEMPT SMP NOPTI
  abr 11 09:34:59 fpgmsi kernel: CPU: 0 PID: 28103 Comm: Thread (pooled) 
Tainted: P   OE  6.5.0-27-generic #28-Ubuntu
  abr 11 09:34:59 fpgmsi kernel: Hardware name: Micro-Star International Co., 
Ltd. MAG Z690 Codex X5 (MS-B930)/PRO Z690-A WIFI (MS-7D25), BIOS D.50 04/26/2022
  abr 11 09:34:59 fpgmsi kernel: RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel: Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 
0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 
db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3
  abr 11 09:34:59 fpgmsi kernel: RSP: 0018:aab6865ffbf8 EFLAGS: 00010282
  abr 11 09:34:59 fpgmsi kernel: RAX:  RBX: fffe 
RCX: 
  abr 11 09:34:59 fpgmsi kernel: RDX:  RSI:  
RDI: 
  abr 11 09:34:59 fpgmsi kernel: RBP: aab6865ffc28 R08: 0001 
R09: 
  abr 11 09:34:59 fpgmsi kernel: R10: 00023854 R11:  
R12: 
  abr 11 09:34:59 fpgmsi kernel: R13: aab6865ffc78 R14: 906675d8aed0 
R15: aab6865ffc70
  abr 11 09:34:59 fpgmsi kernel: FS:  7bd4d594b6c0() 
GS:90753f80() knlGS:
  abr 11 09:34:59 fpgmsi kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000 
CR4: 00750ef0
  abr 11 09:34:59 fpgmsi kernel: PKRU: 5554
  abr 11 09:34:59 fpgmsi kernel: Call Trace:
  abr 11 09:34:59 fpgmsi kernel:  
  abr 11 09:34:59 fpgmsi kernel:  ? show_regs+0x6d/0x80
  abr 11 09:34:59 fpgmsi kernel:  ? __die+0x24/0x80
  abr 11 09:34:59 fpgmsi kernel:  ? page_fault_oops+0x99/0x1b0
  abr 11 09:34:59 fpgmsi kernel:  ? kernelmode_fixup_or_oops+0xb2/0x140
  abr 11 09:34:59 fpgmsi kernel:  ? __bad_area_nosemaphore+0x1a5/0x2c0
  abr 11 09:34:59 fpgmsi kernel:  ? bad_area_nosemaphore+0x16/0x30
  abr 11 09:34:59 fpgmsi kernel:  ? do_kern_addr_fault+0x7b/0xa0
  abr 11 09:34:59 fpgmsi kernel:  ? exc_page_fault+0x1a4/0x1b0
  abr 11 09:34:59 fpgmsi kernel:  ? asm_exc_page_fault+0x27/0x30
  abr 11 09:34:59 fpgmsi kernel:  ? cifs_flush_folio+0x41/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  ?

[Kernel-packages] [Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).

** Attachment added: "dmesg from the test"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+attachment/5768024/+files/dmesg_6.5.0-27-generic_%2328+TEST2060919v20240419b1.txt

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

Title:
  Remote filesystems mounted as CIFS not working after update to Kernel
  "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi
  #17-Ubuntu" (aarch64).

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  New
Status in linux-hwe-6.5 package in Ubuntu:
  Confirmed
Status in linux-raspi package in Ubuntu:
  Confirmed

Bug description:
  Remote filesystems mounted as CIFS are not working after update to
  Kernel "6.5.0-27-generic #28-Ubuntu" for x86_64 (and also after
  updating to Kernel "6.5.0-1014-raspi #17-Ubuntu" in aarch64).

  The remote filesystem is correctly mounted and seems to work but
  trying to write data to the filesystem ends in a kernel error
  exception. After that error the CIFS filesystem just became unusable.

  Previous Kernel version works correctly.

  =
  Example for Kernel "6.5.0-27-generic #28-Ubuntu" (x86_64)
  =
  # lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  # uname -a
  Linux fpgmsi 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 
18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 6.5.0-27.28-generic 6.5.13

  
  How to reproduce the problem
  
  For instance, I'm using KeePassXC 
(https://launchpad.net/ubuntu/+source/keepassxc) to update a database located 
at CIFS filesystem. Any change done to that database causes this Kernel error 
exception:

  abr 11 09:34:59 fpgmsi kernel: BUG: unable to handle page fault for address: 
fffe
  abr 11 09:34:59 fpgmsi kernel: #PF: supervisor read access in kernel mode
  abr 11 09:34:59 fpgmsi kernel: #PF: error_code(0x) - not-present page
  abr 11 09:34:59 fpgmsi kernel: PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 
0 
  abr 11 09:34:59 fpgmsi kernel: Oops:  [#1] PREEMPT SMP NOPTI
  abr 11 09:34:59 fpgmsi kernel: CPU: 0 PID: 28103 Comm: Thread (pooled) 
Tainted: P   OE  6.5.0-27-generic #28-Ubuntu
  abr 11 09:34:59 fpgmsi kernel: Hardware name: Micro-Star International Co., 
Ltd. MAG Z690 Codex X5 (MS-B930)/PRO Z690-A WIFI (MS-7D25), BIOS D.50 04/26/2022
  abr 11 09:34:59 fpgmsi kernel: RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel: Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 
0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 
db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3
  abr 11 09:34:59 fpgmsi kernel: RSP: 0018:aab6865ffbf8 EFLAGS: 00010282
  abr 11 09:34:59 fpgmsi kernel: RAX:  RBX: fffe 
RCX: 
  abr 11 09:34:59 fpgmsi kernel: RDX:  RSI:  
RDI: 
  abr 11 09:34:59 fpgmsi kernel: RBP: aab6865ffc28 R08: 0001 
R09: 
  abr 11 09:34:59 fpgmsi kernel: R10: 00023854 R11:  
R12: 
  abr 11 09:34:59 fpgmsi kernel: R13: aab6865ffc78 R14: 906675d8aed0 
R15: aab6865ffc70
  abr 11 09:34:59 fpgmsi kernel: FS:  7bd4d594b6c0() 
GS:90753f80() knlGS:
  abr 11 09:34:59 fpgmsi kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000 
CR4: 00750ef0
  abr 11 09:34:59 fpgmsi kernel: PKRU: 5554
  abr 11 09:34:59 fpgmsi kernel: Call Trace:
  abr 11 09:34:59 fpgmsi kernel:  
  abr 11 09:34:59 fpgmsi kernel:  ? show_regs+0x6d/0x80
  abr 11 09:34:59 fpgmsi kernel:  ? __die+0x24/0x80
  abr 11 09:34:59 fpgmsi kernel:  ? page_fault_oops+0x99/0x1b0
  abr 11 09:34:59 fpgmsi kernel:  ? kernelmode_fixup_or_oops+0xb2/0x140
  abr 11 09:34:59 fpgmsi kernel:  ? __bad_area_nosemaphore+0x1a5/0x2c0
  abr 11 09:34:59 fpgmsi kernel:  ? bad_area_nosemaphore+0x16/0x30
  abr 11 09:34:59 fpgmsi kernel:  ? do_kern_addr_fault+0x7b/0xa0
  abr 11 09:34:59 fpgmsi kernel:  ? exc_page_fault+0x1a4/0x1b0
  abr 11 09:34:59 fpgmsi kernel:  ? asm_exc_page_fault+0x27/0x30
  abr 11 09:34:59 fpgmsi kernel:  ? cifs_flush_folio+0x41/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  ? cifs_flush_folio+0x37/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  cifs_remap_file_range+0x172/0x660 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  do_clone_file_range+0x101/0x2d0
  abr 11 09:34:59 fpgmsi kernel:  vfs_clone_file_range+0x3f/0x150
  abr 11 09:34:59 fpgmsi kernel:  ioctl_file_clone+0x52/0xc0
  abr 11 09:34:59

[Kernel-packages] [Bug 2062502] [NEW] linux-firmware package breaks iwlwifi

2024-04-19 Thread Benjamin McGough

Public bug reported:

This package version works:

20230919.git3672ccab-0ubuntu2.1

This one causes firmware SW errors and resets - breaking wifi in iwlwifi
driver:

20230919.git3672ccab-0ubuntu2.9

I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade to
...2.9 of the linux-firmware package, I saw many errors that begin like
this in syslog:

2024-04-18T22:30:20.975204-07:00 stormy kernel: [  886.503389] iwlwifi 
:00:14.3: Queue 1 is stuck 0 12
2024-04-18T22:30:20.979152-07:00 stormy kernel: [  886.503652] iwlwifi 
:00:14.3: Microcode SW error detected. Restarting 0x0.
2024-04-18T22:30:20.979167-07:00 stormy kernel: [  886.503764] iwlwifi 
:00:14.3: Start IWL Error Log Dump:
2024-04-18T22:30:20.979169-07:00 stormy kernel: [  886.503768] iwlwifi 
:00:14.3: Transport status: 0x004A, valid: 6
2024-04-18T22:30:20.979170-07:00 stormy kernel: [  886.503772] iwlwifi 
:00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode

Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no
errors.

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

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

Title:
  linux-firmware package breaks iwlwifi

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  This package version works:

  20230919.git3672ccab-0ubuntu2.1

  This one causes firmware SW errors and resets - breaking wifi in
  iwlwifi driver:

  20230919.git3672ccab-0ubuntu2.9

  I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade
  to ...2.9 of the linux-firmware package, I saw many errors that begin
  like this in syslog:

  2024-04-18T22:30:20.975204-07:00 stormy kernel: [  886.503389] iwlwifi 
:00:14.3: Queue 1 is stuck 0 12
  2024-04-18T22:30:20.979152-07:00 stormy kernel: [  886.503652] iwlwifi 
:00:14.3: Microcode SW error detected. Restarting 0x0.
  2024-04-18T22:30:20.979167-07:00 stormy kernel: [  886.503764] iwlwifi 
:00:14.3: Start IWL Error Log Dump:
  2024-04-18T22:30:20.979169-07:00 stormy kernel: [  886.503768] iwlwifi 
:00:14.3: Transport status: 0x004A, valid: 6
  2024-04-18T22:30:20.979170-07:00 stormy kernel: [  886.503772] iwlwifi 
:00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode

  Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no
  errors.

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


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

[Kernel-packages] [Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).

>As promised, I uploaded test kernels to the below ppa:
>
>https://launchpad.net/~mruffell/+archive/ubuntu/lp2060919-test

OK. I'll test once it's built ends. Thank you!

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

Title:
  Remote filesystems mounted as CIFS not working after update to Kernel
  "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi
  #17-Ubuntu" (aarch64).

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  New
Status in linux-hwe-6.5 package in Ubuntu:
  Confirmed
Status in linux-raspi package in Ubuntu:
  Confirmed

Bug description:
  Remote filesystems mounted as CIFS are not working after update to
  Kernel "6.5.0-27-generic #28-Ubuntu" for x86_64 (and also after
  updating to Kernel "6.5.0-1014-raspi #17-Ubuntu" in aarch64).

  The remote filesystem is correctly mounted and seems to work but
  trying to write data to the filesystem ends in a kernel error
  exception. After that error the CIFS filesystem just became unusable.

  Previous Kernel version works correctly.

  =
  Example for Kernel "6.5.0-27-generic #28-Ubuntu" (x86_64)
  =
  # lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  # uname -a
  Linux fpgmsi 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar  7 
18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 6.5.0-27.28-generic 6.5.13

  
  How to reproduce the problem
  
  For instance, I'm using KeePassXC 
(https://launchpad.net/ubuntu/+source/keepassxc) to update a database located 
at CIFS filesystem. Any change done to that database causes this Kernel error 
exception:

  abr 11 09:34:59 fpgmsi kernel: BUG: unable to handle page fault for address: 
fffe
  abr 11 09:34:59 fpgmsi kernel: #PF: supervisor read access in kernel mode
  abr 11 09:34:59 fpgmsi kernel: #PF: error_code(0x) - not-present page
  abr 11 09:34:59 fpgmsi kernel: PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 
0 
  abr 11 09:34:59 fpgmsi kernel: Oops:  [#1] PREEMPT SMP NOPTI
  abr 11 09:34:59 fpgmsi kernel: CPU: 0 PID: 28103 Comm: Thread (pooled) 
Tainted: P   OE  6.5.0-27-generic #28-Ubuntu
  abr 11 09:34:59 fpgmsi kernel: Hardware name: Micro-Star International Co., 
Ltd. MAG Z690 Codex X5 (MS-B930)/PRO Z690-A WIFI (MS-7D25), BIOS D.50 04/26/2022
  abr 11 09:34:59 fpgmsi kernel: RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel: Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 
0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 
db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3
  abr 11 09:34:59 fpgmsi kernel: RSP: 0018:aab6865ffbf8 EFLAGS: 00010282
  abr 11 09:34:59 fpgmsi kernel: RAX:  RBX: fffe 
RCX: 
  abr 11 09:34:59 fpgmsi kernel: RDX:  RSI:  
RDI: 
  abr 11 09:34:59 fpgmsi kernel: RBP: aab6865ffc28 R08: 0001 
R09: 
  abr 11 09:34:59 fpgmsi kernel: R10: 00023854 R11:  
R12: 
  abr 11 09:34:59 fpgmsi kernel: R13: aab6865ffc78 R14: 906675d8aed0 
R15: aab6865ffc70
  abr 11 09:34:59 fpgmsi kernel: FS:  7bd4d594b6c0() 
GS:90753f80() knlGS:
  abr 11 09:34:59 fpgmsi kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000 
CR4: 00750ef0
  abr 11 09:34:59 fpgmsi kernel: PKRU: 5554
  abr 11 09:34:59 fpgmsi kernel: Call Trace:
  abr 11 09:34:59 fpgmsi kernel:  
  abr 11 09:34:59 fpgmsi kernel:  ? show_regs+0x6d/0x80
  abr 11 09:34:59 fpgmsi kernel:  ? __die+0x24/0x80
  abr 11 09:34:59 fpgmsi kernel:  ? page_fault_oops+0x99/0x1b0
  abr 11 09:34:59 fpgmsi kernel:  ? kernelmode_fixup_or_oops+0xb2/0x140
  abr 11 09:34:59 fpgmsi kernel:  ? __bad_area_nosemaphore+0x1a5/0x2c0
  abr 11 09:34:59 fpgmsi kernel:  ? bad_area_nosemaphore+0x16/0x30
  abr 11 09:34:59 fpgmsi kernel:  ? do_kern_addr_fault+0x7b/0xa0
  abr 11 09:34:59 fpgmsi kernel:  ? exc_page_fault+0x1a4/0x1b0
  abr 11 09:34:59 fpgmsi kernel:  ? asm_exc_page_fault+0x27/0x30
  abr 11 09:34:59 fpgmsi kernel:  ? cifs_flush_folio+0x41/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  ? cifs_flush_folio+0x37/0xf0 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  cifs_remap_file_range+0x172/0x660 [cifs]
  abr 11 09:34:59 fpgmsi kernel:  do_clone_file_range+0x101/0x2d0
  abr 11 09:34:59 fpgmsi kernel:  vfs_clone_file_range+0x3f/0x150
  abr 11 09:34:59 fpgmsi kernel:  ioctl_file_clone+0x52/0xc0
  abr 11 09:34:59 fpgmsi kernel:

[Kernel-packages] [Bug 2049634] Re: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data

2024-04-19 Thread Matthew Ruffell

** Changed in: linux (Ubuntu Noble)
   Status: Fix Committed => 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/2049634

Title:
  smb: wsize blocks of bytes followed with binary zeros on copy,
  destroying data

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Mantic:
  Fix Released
Status in linux source package in Noble:
  Fix Released

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

  [Impact]

  Upon installing the 6.5 HWE kernel on Jammy, users with a custom wsize
  set will see data destruction when copying files from their systems
  onto a cifs smb mount.

  wsize defaults to 65535 bytes, but when set to smaller values, like
  16850, users will see blocks of 16850 bytes copied over, followed by
  3900 binary zeros, followed by the next block of data followed by more
  binary zeros. This destroys what you are copying, and the data
  corruption is completely silent.

  A workaround is to set wsize to a multiple of PAGE_SIZE.

  [Fix]

  This was fixed upstream in 6.8-rc5 by the following:

  commit 4860abb91f3d7fbaf8147d54782149bb1fc45892
  Author: Steve French 
  Date: Tue Feb 6 16:34:22 2024 -0600
  Subject: smb: Fix regression in writes when non-standard maximum write size 
negotiated
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4860abb91f3d7fbaf8147d54782149bb1fc45892

  This patch has been selected for upstream stable.

  The patch looks at wsize negotiation from the server, and also what is set on 
the mount command line, and if not a multiple of PAGE_SIZE, rounds it down, 
taking care to not be 0.
  The real corruption bug still exists in netfs/folios subsystems and we are 
looking for it still, but this solves the immediate data corruption issues on 
smb.

  [Testcase]

  Start two VMs, one for the server, and the other, the client.

  Server
  --

  $ sudo apt update
  $ sudo apt upgrade
  $ sudo apt install samba
  $ sudo vim /etc/samba/smb.conf 
  server min protocol = NT1
  [sambashare]
  comment = Samba on Ubuntu
  path = /home/ubuntu/sambashare
  read only = no
  browsable = yes
  $ mkdir ~/sambashare
  $ sudo smbpasswd -a ubuntu

  Client
  --

  $ sudo apt update
  $ sudo apt install cifs-utils
  $ mkdir ~/share
  $ sudo mount -t cifs -o username=ubuntu,vers=1.0,wsize=16850 
//192.168.122.172/sambashare ~/share
  $ ( set -o pipefail && head --bytes=$(( 55 * 1000 )) /dev/zero | openssl enc 
-aes-128-ctr -nosalt -pass "pass:my-seed" -iter 1 | hexdump --no-squeezing 
--format '40/1 "%02x"' --format '"\n"' >"testdata.txt" )
  $ sha256sum testdata.txt 
  9ec09af020dce3270ea76531141940106f173c7243b7193a553480fb8500b3f2  testdata.txt

  Now copy the file to the share.

  Client
  --
  $ cp testdata.txt share/

  Server
  --
  $ sha256sum sambashare/testdata.txt 
  9e573a0aa795f9cd4de4ac684a1c056dbc7d2ba5494d02e71b6225ff5f0fd866  
sambashare/testdata.txt

  The SHA256 hash is different. If you view the file with less, you will
  find a block of wsize=16850 bytes, then 3900 bytes of binary zeros,
  followed by another wsize=16850 bytes, then 3900 bytes of binary
  zeros, etc.

  An example of a broken file is:
  https://launchpadlibrarian.net/712573213/testdata-back-from-server.txt

  [Where problems could occur]

  We are changing the wsize that the SMB server negotiates or the user
  explicitly sets on the mount command line to a safe value, if the
  asked for value was not a multiple of PAGE_SIZE.

  It is unlikely that any users will notice any difference. If the wsize
  happens to be rounded down to a significantly smaller number, there
  may be a small performance impact, e.g. you set wsize=8094 for some
  reason, it would round down to wsize=4096, and lead to double the
  writes. At least you have data integrity though.

  Most users default to wsize=65535, and will have no impact at all.
  Only those with very old smb 1.0 servers that negotiate down to 16850
  will see any difference.

  If a regression were to occur, it could result in user's wsize being
  incorrectly set, leading to the underlying netfs/folios data
  corruption being triggered and causing data corruption.

  [Other info]

  The issue was introduced in 6.3-rc1 by:

  commit d08089f649a0cfb2099c8551ac47eef0cc23fdf2
  Author: David Howells 
  Date: Mon Jan 24 21:13:24 2022 +
  Subject: cifs: Change the I/O paths to use an iterator rather than a page list
  Link: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d08089f649a0cfb2099c8551ac47eef0cc23fdf2

  Upstream mailing list discussion:

  https://lore.kernel.org/linux-
  
cifs/6a65b2d1-7596-438a-8ade-2f7526b15...@rd10.de/T/#m22cd9b7289f87cd945978bd7995bcaf1beebfe67

To manage notifications about this bug go to:

[Kernel-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

2024-04-19 Thread John Cabaj

I've tested an initial version with the upstream patch and attached the
debdiff here. Will work to get this uploaded.

** Patch added: "zfs-linux_2.2.2-0ubuntu9.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2058179/+attachment/5767995/+files/zfs-linux_2.2.2-0ubuntu9.debdiff

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

Title:
  Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported

Status in Native ZFS for Linux:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in zfs-linux package in Ubuntu:
  Confirmed
Status in systemd source package in Noble:
  Triaged
Status in zfs-linux source package in Noble:
  Confirmed

Bug description:
  As per https://github.com/openzfs/zfs/issues/15930

  ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
  copy_file_range, breaking a multitude of applications.

  Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
  2.2.2.

  One notable issue is when running Root on ZFS: systemd-sysusers will
  always fail to create users/groups with the error "Failed to backup
  /etc/{group,passwd}: Operation not supported" due to the call to
  copy_file_range.

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


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

[Kernel-packages] [Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).