[Kernel-packages] [Bug 1998285] Re: 5.15.0-53-UBSAN: shift-out-of-bounds in amdgpu

[Kai-Heng Feng]

Jarkko, I think opting for a newer kernel can be a solution:

$ sudo apt install linux-oem-22.04d

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

Title:
  5.15.0-53-UBSAN: shift-out-of-bounds in amdgpu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  from dmesg

   1.313665] UBSAN: shift-out-of-bounds in 
/build/linux-JjvoxS/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32
  [1.313668] shift exponent 64 is too large for 64-bit type 'long long 
unsigned int'

  there is also a crash but i don't know if it's related.

  1.313671] Call Trace:
  [1.313672]  
  [1.313673]  show_stack+0x52/0x5c
  [1.313676]  dump_stack_lvl+0x4a/0x63
  [1.313678]  dump_stack+0x10/0x16
  [1.313679]  ubsan_epilogue+0x9/0x49
  [1.313680]  __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef
  [1.313682]  initialize_nocpsch.cold+0x15/0x59 [amdgpu]
  [1.313841]  device_queue_manager_init+0x208/0x3b0 [amdgpu]
  [1.313946]  kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu]
  [1.314079]  amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu]
  [1.314178]  amdgpu_device_ip_init+0x681/0x6a4 [amdgpu]
  [1.314323]  amdgpu_device_init.cold+0x25b/0x7db [amdgpu]
  [1.314463]  ? do_pci_enable_device+0xdb/0x110
  [1.314466]  amdgpu_driver_load_kms+0x1e/0x270 [amdgpu]
  [1.314556]  amdgpu_pci_probe+0x1ce/0x260 [amdgpu]
  [1.314642]  local_pci_probe+0x48/0x90
  [1.314644]  pci_device_probe+0x119/0x1f0
  [1.314645]  really_probe+0x21f/0x420
  [1.314647]  __driver_probe_device+0x119/0x190
  [1.314648]  driver_probe_device+0x23/0xc0
  [1.314650]  __driver_attach+0xbd/0x1f0
  [1.314651]  ? __device_attach_driver+0x120/0x120
  [1.314652]  bus_for_each_dev+0x7c/0xd0
  [1.314654]  driver_attach+0x1e/0x30
  [1.314655]  bus_add_driver+0x148/0x220
  [1.314656]  driver_register+0x95/0x100
  [1.314657]  __pci_register_driver+0x68/0x70
  [1.314659]  amdgpu_init+0x7c/0x1000 [amdgpu]
  [1.314747]  ? 0xc0fc
  [1.314748]  do_one_initcall+0x46/0x1e0
  [1.314750]  ? kmem_cache_alloc_trace+0x19e/0x2e0
  [1.314752]  do_init_module+0x52/0x260
  [1.314753]  load_module+0xb2b/0xbc0
  [1.314754]  __do_sys_finit_module+0xbf/0x120
  [1.314756]  __x64_sys_finit_module+0x18/0x20
  [1.314757]  do_syscall_64+0x59/0xc0
  [1.314758]  ? ksys_lseek+0x85/0xc0
  [1.314759]  ? exit_to_user_mode_prepare+0x37/0xb0
  [1.314761]  ? syscall_exit_to_user_mode+0x27/0x50
  [1.314762]  ? __x64_sys_lseek+0x18/0x20
  [1.314763]  ? do_syscall_64+0x69/0xc0
  [1.314764]  entry_SYSCALL_64_after_hwframe+0x61/0xcb
  [1.314766] RIP: 0033:0x7fef87ab8a3d
  [1.314767] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48
  [1.314768] RSP: 002b:7fffe67aa7c8 EFLAGS: 0246 ORIG_RAX: 
0139
  [1.314770] RAX: ffda RBX: 55d1d00078a0 RCX: 
7fef87ab8a3d
  [1.314771] RDX:  RSI: 7fef87c4f441 RDI: 
0018
  [1.314772] RBP: 0002 R08:  R09: 
0002
  [1.314772] R10: 0018 R11: 0246 R12: 
7fef87c4f441
  [1.314773] R13: 55d1d002ea30 R14: 55d1d0011600 R15: 
55d1d002eb10
  [1.314774]  
  [1.314778] 


  
  gpu is Amd r 380 tonga 4Gb.
  I was adviced to try 6.0 series of kernel and I dont see the ubsan error 
there but I would like to get the fixes backported 5.15 series.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jarkko 1322 F pulseaudio
   /dev/snd/controlC1:  jarkko 1322 F pulseaudio
  CasperMD5json: {
  CurrentDesktop: MATE
  DistroRelease: Linux Mint 21
  InstallationDate: Installed on 2022-09-19 (71 days ago)
  InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
  MachineType: ASUS System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1007-oem 
root=UUID=62a471af-17fd-40e2-9304-b3e113e4f47f ro quiet splash
  ProcVersionSignature: Ubuntu 6.0.0-1007.7-oem 6.0.3
  RelatedPackageVersions:
   linux-restricted-modules-6.0.0-1007-oem N/A
   linux-backports-modules-6.0.0-1007-oem  N/A
   linux-firmware  20220329.git681281e4-0ubuntu3.7
  Tags:  vanessa
  Uname: Linux 6.0.0-1007-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom 

[Kernel-packages] [Bug 2032164] Re: A general-proteciton exception during guest migration to unsupported PKRU machine

[Chengen Du]

The kernels (5.15.0-85.95) have been tested without any issues.

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

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

Title:
  A general-proteciton exception during guest migration to unsupported
  PKRU machine

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  When a host that supports PKRU initiates a guest that lacks PKRU support, the 
flag is enabled on the guest's fpstate.
  This information is then passed to userspace through the vcpu ioctl 
KVM_GET_XSAVE.
  However, a problem arises when the user opts to migrate the mentioned guest 
to another machine that does not support PKRU.
  In this scenario, the new host attempts to restore the guest's fpu registers.
  Nevertheless, due to the absence of PKRU support on the new host, a 
general-protection exception takes place, leading to a guest crash.

  [Fix]
  The problem is resolved by the following upstream commit:
  ad856280ddea x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0

  Additionally, a subsequent fix tackles the migration problem stemming from 
the earlier commit:
  a1020a25e697 KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES

  [Test Plan]
  1. Set up two machines: one with PKRU support and the other without.
  2. Initiate a guest that lacks PKRU support on the machine with PKRU support.
  3. Utilize libvirt to migrate the aforementioned guest to a different machine 
that lacks PKRU support.
  4. The error emerges on the destination machine:
  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  EAX=86cf7970 EBX= ECX=0001 EDX=005b0036
  ESI=0087 EDI=0087 EBP=87c03e38 ESP=87c03e18
  EIP=86cf7d5e EFL=0246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   9300
  CS =f000   9b00
  SS =   9300
  DS =   9300
  FS =   9300
  GS =   9300
  LDT=   8200
  TR =   8b00
  GDT=  
  IDT=  
  CR0=6010 CR2= CR3= CR4=
  DR0= DR1= DR2= 
DR3= 
  DR6=0ff0 DR7=0400
  EFER=
  Code=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  2023-07-09T03:03:14.911750Z qemu-system-x86_64: terminating on signal 15 from 
pid 4134 (/usr/sbin/libvirtd)
  2023-07-09 03:03:15.312+: shutting down, reason=destroyed

  [Where problems could occur]
  The introduced commits will impact the guest migration process,
  potentially leading to failures and preventing the guest from operating 
successfully on the migration destination.

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


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

[Kernel-packages] [Bug 2033553] Re: SD Card not detected, rtsx_pci_sdmmc reload required

[Chris]

Is there anything I can do to help with this report?

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

Title:
  SD Card not detected, rtsx_pci_sdmmc reload required

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

Bug description:
  The SD card reader (Realtek Semiconductor Co., Ltd. RTS5260 PCI Express Card 
Reader) does not detect a SD card when it is inserted. 
  Only when the card was inserted during boot, or when called

  sudo rmmod rtsx_pci_sdmmc && sudo modprobe rtsx_pci_sdmmc

  the SD card is detected and can be used as usual. Running the modprobe 
without a card and inserting it then doesn't (temporarily) fix the issue. Also 
a change of card doesn't work.
  => The work around is always to insert the card and then remove and reload 
the module.

  Loading the module shows this message in dmesg:
  **
  [  651.937165] mmc0: cannot verify signal voltage switch
  [  652.053032] mmc0: new ultra high speed SDR104 SDHC card at address 59b4
  [  652.053708] mmcblk0: mmc0:59b4 SDU1  29.8 GiB (ro)
  [  652.055090]  mmcblk0: p1
  **

  Kubuntu-Version:
  $ lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  $ uname -a
  Linux gandalf 6.2.0-31-generic #31~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Aug 
16 13:45:26 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

  
  Note:
  This bug reports seem to show a very similar behavior: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-31-generic 6.2.0-31.31~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15
  Uname: Linux 6.2.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Aug 30 21:36:45 2023
  InstallationDate: Installed on 2023-08-26 (4 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  SourcePackage: linux-signed-hwe-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-hwe-6.2/+bug/2033553/+subscriptions


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

[Kernel-packages] [Bug 2034578] Re: Support IPSEC full offload implementation

[Bodong Wang]

** Merge proposal linked:
   
https://code.launchpad.net/~bodong-wang/ubuntu/+source/linux-bluefield/+git/jammy/+merge/450970

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

Title:
  Support IPSEC full offload implementation

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  Summary:
  Align Kernel IPsec Full offload implementation in the DPU to the upstream Full
  offload in all components: OFED, Strongswan, etc.
  This is in order for DPU Kernel IPsec to include policy offload and be fully
  aligned to what CX Kernel customers will use.

  How to test:
  Host 1:
  /opt/mellanox/iproute2/sbin/devlink dev eswitch set pci/:03:00.0 mode 
legacy
  echo 'dmfs' > 
/sys/bus/pci/devices/:03:00.0/net/p0/compat/devlink/steering_mode
  echo 'full' > /sys/class/net/p0/compat/devlink/ipsec_mode
  /opt/mellanox/iproute2/sbin/devlink dev eswitch set pci/:03:00.0 mode 
switchdev

  BF on host 1:
  /opt/mellanox/iproute2/sbin/ip xfrm policy add src 196.234.181.165 dst 
196.234.182.166 dir out tmpl src 196.234.181.165/16 dst 196.234.182.166/16 
proto esp reqid 0xefa83812 mode transport priority 10
  /opt/mellanox/iproute2/sbin/ip xfrm policy add src 196.234.182.166 dst 
196.234.181.165 dir in tmpl src 196.234.182.166/16 dst 196.234.181.165/16 proto 
esp reqid 0x63a7db74 mode transport priority 10
  /opt/mellanox/iproute2/sbin/ip xfrm policy add src 196.234.182.166 dst 
196.234.181.165 dir fwd tmpl src 196.234.182.166/16 dst 196.234.181.165/16 
proto esp reqid 0x63a7db74 mode transport priority 10
  /opt/mellanox/iproute2/sbin/ip xfrm state add src 196.234.181.165/16 dst 
196.234.182.166/16 proto esp spi 0xefa83812 reqid 0xefa83812 mode transport 
aead 'rfc4106(gcm(aes))' 0xe2fe3857301d8f72b5d71d295a462ef21868e407 128 offload 
packet dev p0 dir out sel src 196.234.181.165/16 dst 196.234.182.166/16 flag 
esn replay-window 32
  /opt/mellanox/iproute2/sbin/ip xfrm state add src 196.234.182.166/16 dst 
196.234.181.165/16 proto esp spi 0x63a7db74 reqid 0x63a7db74 mode transport 
aead 'rfc4106(gcm(aes))' 0xe916c4d0db1886e8c877b023e8cebef53b4d2d0f 128 offload 
packet dev p0 dir in sel src 196.234.182.166/16 dst 196.234.181.165/16 flag esn 
replay-window 32

  Start OVS and set following configure on BF:
  /usr/bin/ovs-vsctl set Open_vSwitch . other_config:hw-offload=true
  /usr/bin/ovs-vsctl set Open_vSwitch . other_config:max-idle=30

  Host2:
  /opt/mellanox/iproute2/sbin/devlink dev eswitch set pci/:03:00.1 mode 
legacy
  echo 'dmfs' > 
/sys/bus/pci/devices/:03:00.1/net/p1/compat/devlink/steering_mode
  echo 'full' > /sys/class/net/p1/compat/devlink/ipsec_mode
  /opt/mellanox/iproute2/sbin/devlink dev eswitch set pci/:03:00.1 mode 
switchdev

  BF on host 2:
  /opt/mellanox/iproute2/sbin/ip xfrm policy add src 196.234.182.166 dst 
196.234.181.165 dir out tmpl src 196.234.182.166/16 dst 196.234.181.165/16 
proto esp reqid 0xefa83812 mode transport priority 10
  /opt/mellanox/iproute2/sbin/ip xfrm policy add src 196.234.181.165 dst 
196.234.182.166 dir in tmpl src 196.234.181.165/16 dst 196.234.182.166/16 proto 
esp reqid 0x63a7db74 mode transport priority 10
  /opt/mellanox/iproute2/sbin/ip xfrm policy add src 196.234.181.165 dst 
196.234.182.166 dir fwd tmpl src 196.234.181.165/16 dst 196.234.182.166/16 
proto esp reqid 0x63a7db74 mode transport priority 10
  /opt/mellanox/iproute2/sbin/ip xfrm state add src 196.234.181.165 dst 
196.234.182.166 proto esp spi 0xefa83812 reqid 0xefa83812 mode transport aead 
'rfc4106(gcm(aes))' 0xe2fe3857301d8f72b5d71d295a462ef21868e407 128 offload 
packet dev p0 dir out sel src 196.234.181.165/16 dst 196.234.182.166/16 flag 
esn replay-window 32
  /opt/mellanox/iproute2/sbin/ip xfrm state add src 196.234.181.165 dst 
196.234.182.166 proto esp spi 0x63a7db74 reqid 0x63a7db74 mode transport aead 
'rfc4106(gcm(aes))' 0xe916c4d0db1886e8c877b023e8cebef53b4d2d0f 128 offload 
packet dev p0 dir in sel src 196.234.181.165/16 dst 196.234.182.166/16 flag esn 
replay-window 32

  Start OVS and set following configure on BF:
  /usr/bin/ovs-vsctl set Open_vSwitch . other_config:hw-offload=true
  /usr/bin/ovs-vsctl set Open_vSwitch . other_config:max-idle=30

  Send the traffic between host 1 and host 2 and check IPsec counters in
  "ethtool -S" statistics on both BF.

  How to fix:
  Need to backport a series of xfrm patches into BlueField 5.15 kernel, from 
6.0 upstream kernel.
  Patches needed for 5.15 kernel:
  afe9e47 xfrm: fix conflict for netdev and tx stats
  6aff54d xfrm: don't skip free of empty state in acquire policy
  692fecb xfrm: delete offloaded policy
  91b6276 xfrm: Support UDP encapsulation in packet offload mode
  69e168a xfrm: add missed call to delete offloaded policies
  9724724 xfrm: release all offloaded policy memory
  e57b7ec xfrm: don't require advance ESN callback for packet offload
  9e98488 xfrm: 

[Kernel-packages] [Bug 2034747] [NEW] Azure: Fix Infiniband identifier order

[Tim Gardner]

Public bug reported:

SRU Justification

[Impact]

Commit ad95515bf1d391326b362d8b0c1e6e3bd74046b6 ('RDMA/mana_ib: Add a
driver for Microsoft Azure Network Adapter') is part of the MANA
Infiniband backport. However, a commit was missed that updated the 'enum
rdma_driver_id' list of identifiers. Since these are order and value
specific user space applications are not able to correctly identify the
MANA RDMA driver.

[Test Plan]

MSFT tested.

[Regression Potential]

Existing applications don't work with MANA RDMA anyway, so there is no
regression potential.

[Other Info]

SF: #00368017

** Affects: linux-azure (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: linux-azure (Ubuntu Jammy)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)

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

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

** Changed in: linux-azure (Ubuntu Jammy)
   Importance: Undecided => Medium

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

** Changed in: linux-azure (Ubuntu Jammy)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

** Summary changed:

- Azure: Fix Infiniband verb order
+ Azure: Fix Infiniband identifier order

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

Title:
  Azure: Fix Infiniband identifier order

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

Bug description:
  SRU Justification

  [Impact]

  Commit ad95515bf1d391326b362d8b0c1e6e3bd74046b6 ('RDMA/mana_ib: Add a
  driver for Microsoft Azure Network Adapter') is part of the MANA
  Infiniband backport. However, a commit was missed that updated the
  'enum rdma_driver_id' list of identifiers. Since these are order and
  value specific user space applications are not able to correctly
  identify the MANA RDMA driver.

  [Test Plan]

  MSFT tested.

  [Regression Potential]

  Existing applications don't work with MANA RDMA anyway, so there is no
  regression potential.

  [Other Info]

  SF: #00368017

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


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

[Kernel-packages] [Bug 2034747] Re: Azure: Fix Infiniband identifier order

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2023-September/142590.html

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

Title:
  Azure: Fix Infiniband identifier order

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

Bug description:
  SRU Justification

  [Impact]

  Commit ad95515bf1d391326b362d8b0c1e6e3bd74046b6 ('RDMA/mana_ib: Add a
  driver for Microsoft Azure Network Adapter') is part of the MANA
  Infiniband backport. However, a commit was missed that updated the
  'enum rdma_driver_id' list of identifiers. Since these are order and
  value specific user space applications are not able to correctly
  identify the MANA RDMA driver.

  [Test Plan]

  MSFT tested.

  [Regression Potential]

  Existing applications don't work with MANA RDMA anyway, so there is no
  regression potential.

  [Other Info]

  SF: #00368017

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


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

[Kernel-packages] [Bug 2031093] Re: libgnutls report "trap invalid opcode" when trying to install packages over https

[Ubuntu Kernel Bot]

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

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-azure-v2 
verification-needed-jammy-linux-azure

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

Title:
  libgnutls report "trap invalid opcode" when trying to install packages
  over https

Status in ubuntu-kernel-tests:
  New
Status in gnutls28 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in gnutls28 source package in Focal:
  Confirmed
Status in linux source package in Focal:
  Fix Released
Status in gnutls28 source package in Jammy:
  Confirmed
Status in linux source package in Jammy:
  Fix Released
Status in gnutls28 source package in Lunar:
  Confirmed
Status in linux source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  When booting linux with Gather Data Sampling mitigations without updated 
microcode on an affected CPU, AVX will be disabled. This will cause programs 
connecting to https using gnutls on Jammy to break, including apt and git.

  [Test case]
  git clone 
https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests
  Cloning into 'autotest-client-tests'...
  error: git-remote-https died of signal 4

  dmesg:
  [  806.072080] traps: git-remote-http[2561] trap invalid opcode 
ip:7fa2e7dac44a sp:7ffed6796480 error:0 in 
libgnutls.so.30.31.0[7fa2e7c85000+129000]

  Works fine with the mitigation disabled by default.

  [Potential regressions]
  Users booting on affected parts without microcode updates will be subject to 
Gather Data Sampling attacks (which can be done by local untrusted attackers), 
which may leak confidential data, including keys.

  
  -

  When trying to install linux-libc-dev on Oracle BM.Standard2.52 (seems to be 
the only affected instance) with Jammy 5.15.0-81-generic, it will get 
interrupted with:
  E: Method https has died unexpectedly!
  E: Sub-process https received signal 4.

  $ sudo apt install linux-libc-dev
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following NEW packages will be installed:
    linux-libc-dev
  0 upgraded, 1 newly installed, 0 to remove and 54 not upgraded.
  Need to get 1353 kB of archives.
  After this operation, 6943 kB of additional disk space will be used.
  E: Method https has died unexpectedly!
  E: Sub-process https received signal 4.

  From dmesg you will see:
  [ 1078.750067] traps: https[4572] trap invalid opcode ip:7f3c1e6316be 
sp:7ffea26b61c0 error:0 in libgnutls.so.30.31.0[7f3c1e50f000+129000]

  Also, git clone is not working as well.

  $ git clone --depth=1 
https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests
  Cloning into 'autotest-client-tests'...
  error: git-remote-https died of signal 4

  dmesg:
  [  806.072080] traps: git-remote-http[2561] trap invalid opcode 
ip:7fa2e7dac44a sp:7ffed6796480 error:0 in 
libgnutls.so.30.31.0[7fa2e7c85000+129000]

  libgnutls30 version:3.7.3-4ubuntu1.2

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


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

[Kernel-packages] [Bug 2016398] Re: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?)

[Ubuntu Kernel Bot]

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

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-azure-v2 
verification-needed-jammy-linux-azure

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

Title:
  stacked overlay file system mounts that have chroot() called against
  them appear to be getting locked (by the kernel most likely?)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  Won't Fix
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Confirmed

Bug description:
  [Impact]

  Opened files reported in /proc/pid/map_files can be shows with the
  wrong mount point using overlayfs with filesystem namspaces.

  This incorrect behavior is fixed:

UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from
  map_files

  However, the fix introduced a new regression, the reference to the
  original file stored in vma->vm_prfile is not properly released when
  vma->vm_prfile is replaced with a new file.

  This can cause a reference counter unbalance, leading errors such as
  "target is busy" when trying to unmount overlayfs, even if the
  filesystem has not active reference.

  [Test case]

  Reproducer provided by original bug reporter:
  https://launchpadlibrarian.net/663151659/overlayfsscript_example

  [Fix]

  Fix by properly releasing the original file stored in vm_prfile.

  [Regression potential]

  This fix seems to solve the reported bug (verified with the
  reproducer) and it doesn't seem to introduce other regressions or
  behavior change.

  However, we may experience regressions in overlayfs or potentially
  other "target is busy" errors when unmounting overlayfs filesystems
  with this fix applied, if there are still other corner cases not
  covered properly.

  [Original bug report]

  Hi

  BACKGROUND:
  ---
  I have a set of scripts that debootstraps and builds vanilla Debian installs, 
where the only modifications are what packages are installed. Then that becomes 
the lower directory of an overlayfs mount, a tmpfs becomes the upperdir, and 
then that becomes the chroot where config changes are made with more scripts. 
This overlayfs is mounted in its own mount namespace as the script is unshare'd

  Within these scripts, I make packages with a fork of checkinstall I
  made which uses the / as the lowerdir, as overlayfs allows that, a
  tmpfs as the upperdir, the install command is run with chroot, and
  then the contents are copied.

  THE ISSUE:
  --
  I noticed that it appears that my ramdisks are remaining in memory, I have 
isolated it out to the overlayfs mounts with the overlayfs as the lowerdir 
where chroot is being called on it. I tried entering the namespace myself and 
umounting it, and notice I get the error "Target is busy"

  With the "Target Is Busy" issue, I tried to `lsof` and `fuser` and
  `lsfd` as much as I could, but every user mode tool shows absolutely
  NO files open at all

  I was using Kubuntu 18.04, it was an old install and 32 bit, so I had
  no upgrade path to be using more recent versions. Now I am on 23.04,
  but I also think this is happening on a 22.10 laptop

  DIAGNOSIS:
  --
  I am able to isolate it out, and get this to replicate in the smallest script 
that I could that is now attached. the chroot is important. I am able to 
unmount the second overlayfs if chroot is never called. Nothing ever has to run 
IN the chroot, trying to call a binary that does not exist, and then trying to 
unmount it results in "target is busy" with no open files reportable by user 
mode tools

  FURTHER TESTING:
  
  Trying to find out the version of Linux this was introduced, I made a script 
that builds a very minimal ext4 file for a VM with a small debootstrapped 
system, builds a kernel, and runs the kernel with QEMU..
  but when I started, after all that, I can't replicate it at all with a 
vanilla 6.2.0 kernel. I used the same config out of my /boot to the .config, 
only tweaking a few options like SYSTEM_TRUSTED_KEYS. Trying to unmount the 
second filesystem actually results in success

  

[Kernel-packages] [Bug 2015400] Re: losetup with mknod fails on jammy with kernel 5.15.0-69-generic

[Ubuntu Kernel Bot]

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

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-azure-v2 
verification-needed-jammy-linux-azure

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

Title:
  losetup with mknod fails on jammy with kernel 5.15.0-69-generic

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Invalid

Bug description:
  [ Impact ]

   * Regression in the loop block driver in Jammy kernel
     between 5.15.0-67 to 5.15.0-68 (in v5.15.86 stable),
     due to a change in the default behavior (value) of
     kernel parameter `max_loop` (from 0 to 8) in commit:
     `loop: Fix the max_loop commandline argument treatment
     when it is set to 0` (comment #6).

   * Users of loop devices (major 7) with minor >= 8 now
     fail to `open()` a loop device created with `mknod()`.

   * This is a corner case, as most people use `losetup`
     with usual /dev/loopNUMBER (or `--find`) which are
     not affected as it uses a different code path.
     (`losetup` for `/dev/loopNOT-A-NUMBER` is affected.)

   * Workaround: kernel parameter `max_loop=0`.

  [ Test Steps ]

   * Run the test cases (losetup and test-loop.c in comment #6):
     - max_loop not set (default)
     - max_loop=0
     - max_loop=8

   * Verify the default behavior (max_loop not set) is restored.

   * Verify the modified behavior (max_loop is set) is unchanged.

  [ Regression Potential ]

   * Regressions would be limited to the loop block driver,
     more specifically its default behavior (but it's that now)
     or specific usage of max_loop parameter (tested; looks OK).

  [ Other Info ]

   * Patch 1 [1] is not quite a fix, but adds CONFIG guards that
 Patch 2 [2] depends on. (Alternatively, a Patch 2 backport
 with that could be done, but Patch 1 seems trivial enough.)

   * The fix on Jammy is only Patch 2, with a trivial backport
 (that CONFIG option is not in Jammy/v5.15, only in v5.18).

   * The fix on Lunar is both patches; clean cherry-picks.

   * The fix on Mantic is both patches too,
 now in v6.5-rc3, which should be automatically incorporated
 as Mantic apparently will release with the 6.5 kernel [3]

     [1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=23881aec85f3219e8462e87c708815ee2cd82358
     [2] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bb5faa99f0ce40756ab7bbbce4f16c01ca5ebd5a
     [3] 
https://discourse.ubuntu.com/t/introducing-kernel-6-5-for-the-23-10-mantic-minotaur-release

  Original Description:
  ---

  losetup fails with devices created manually by mknod on kernel
  5.15.0-69-generic

  # fallocate -l 1G test
  # mknod -m 660 /dev/loop8 b 7 8
  # chown root:disk /dev/loop8
  # losetup /dev/loop8 ./test
  losetup: ./test: failed to set up loop device: Device or resource busy

  Possibly as a result of this patch:
  
https://lore.kernel.org/lkml/20221208200605.756287-1-isaacmanjar...@google.com/T/

  which was introduced in 5.15.0-68:
  
http://launchpadlibrarian.net/653145495/linux_5.15.0-67.74_5.15.0-68.75.diff.gz

  On a machine prior to this change (no issue with losetup):
  # cat /sys/module/loop/parameters/max_loop
  0
  # uname -r
  5.15.0-58-generic

  On a machine after the change (has losetup issue as described above):
  # cat /sys/module/loop/parameters/max_loop
  8
  # uname -r
  5.15.0-69-generic

  So it looks like the default changed and the max amount of loop
  devices that can be created with mknod (not loop-control) is 8. If we
  set max_loop=0 on the kernel command line, it works as before. Cannot
  unload and reload module on a running system to change the parameter
  because it is built into the kernel.

  Another workaround is to use `losetup --find` but that means you
  cannot create with named devices created with mknod.

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


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

[Kernel-packages] [Bug 2020295] Re: Include the MAC address pass through function on RTL8153DD-CG

[Ubuntu Kernel Bot]

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

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-azure-v2 
verification-needed-jammy-linux-azure

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

Title:
  Include the MAC address pass through function on RTL8153DD-CG

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

Bug description:
  [Impact]
  When user connect network cable on the RJ45 port of RTL8153DD-CG on dock, it 
should show pass through MAC address set in BIOS. But the LAN MAC address pass 
through doesn't function on RTL8153DD-CG sku.

  [Fix]
  Commit in v6.3-rc1 fixes the issue.
  ec51fbd1b8a2 r8152: add USB device driver for config selection

  [Test]
  Verified by OEM.

  [Where problems could occur]
  It won't affect the old behavior if there is no preferred cfg is configured 
and will select the preferred one while probing.

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


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

[Kernel-packages] [Bug 2026028] Re: usbrtl sometimes doesn't reload firmware

[Ubuntu Kernel Bot]

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

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-azure-v2 
verification-needed-jammy-linux-azure

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

Title:
  usbrtl sometimes doesn't reload firmware

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

Bug description:
  [Impact]

  The btrtl driver in the 5.15 jammy kernel sometimes doesn't (re-) load
  firmware which results in the BT adapter running potentially old
  firmware rather than the current version from /lib/firmware provided
  by the linux-firmware package.

  This will show in logs like so:
  Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=dfc6 lmp_ver=0a lmp_subver=d922
  Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: unknown IC info, lmp 
subver d922, hci rev dfc6, hci ver 000a
  Jul 04 14:57:23 vivo kernel: Bluetooth: hci0: RTL: assuming no firmware 
upload needed

  The driver reads subver from the adapter to determine chip type. But
  that value is overwritten by a firmware load. In the above case, a
  firmware was already loaded which returns subver d922 which the driver
  does not recognize and it therefore won't load new firmware.

  [Test Case]

  1) Boot machine with USB adapter plugged in.
  2) Verify firmware is loaded.
  3) Reboot a couple of times and verify that firmware is reloaded every time.

  [Where Problems Could Occur]

  Limited to Realtek USB bluetooth adapters that use the btrtl driver.
  Issues could show up as Bluetooth connection/initialization problems.

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


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

[Kernel-packages] [Bug 2028550] Re: Backport support to tolerate ZSTD compressed firmware files

[Ubuntu Kernel Bot]

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

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-azure-v2 
verification-needed-jammy-linux-azure

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

Title:
  Backport support to tolerate ZSTD compressed firmware files

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

   * To ensure reliable dist-upgrades in case of partial upgrades or
  upgrade failures, it is desirable for LTS GA kernel to support
  features that next-LTS GA kernel will rely on.

   * Specifically it is being discussed to switch linux-firmware to ZSTD
  compressed one (see bug #1942260)

   * To ensure that failed dist-upgrades can still boot after-partial
  upgrade it is desirable to suppport zstd compressed firmware

  [ Test Plan ]

   * Boot new build of GA linux kernel with
  CONFIG_FW_LOADER_COMPRESS_ZSTD

   * Check that existing firmware files loaded on a given machine can be
  compressed with zstd and still loaded by this kernel

   * Check that depmod / initramfs-tools all support .zst compressed
  firmware

  [ Where problems could occur ]

   * Once this is inroduced in jammy-GA kernel it may cripple into
  focal-hwe kernels too, and people may start relying on this feature
  despite not universally supported by all other focal kernels. This
  should be trivial to catch in SRUs for example, do not accept SRUs of
  firmwares that ship themselves as .zst in Jammy  and lower.

  [ Other Info ]

   * See https://lists.ubuntu.com/archives/ubuntu-
  devel/2023-July/042652.html and
  https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042707.html

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


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

[Kernel-packages] [Bug 2029138] Re: cifs: fix mid leak during reconnection after timeout threshold

[Ubuntu Kernel Bot]

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

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-azure-v2 
verification-needed-jammy-linux-azure

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

Title:
  cifs: fix mid leak during reconnection after timeout threshold

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Fix Committed
Status in linux-azure source package in Jammy:
  In Progress
Status in linux source package in Lunar:
  Fix Committed
Status in linux-azure source package in Lunar:
  Fix Released

Bug description:
  SRU Justification

  [Impact]
  A regression in the Ubuntu 5.15 kernel has been causing problems for multiple 
customers on Azure.

  This bug has been fixed in the mainline kernel:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=69cba9d3c1284e0838ae408830a02c4a063104bc

  [Test Plan]

  Microsoft tested

  [Regression Potential]

  Reconnections could fail.

  [Other Info]

  SF: #00365185

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


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

[Kernel-packages] [Bug 2034745] [NEW] [regression] Unable to initialize SGX enclaves with XFRM other than 3

[Jethro Beekman]

Public bug reported:

In 5.15.0-1045, only loading enclaves with XFRM set to 3 works,
sgx_encl_init returns EINVAL. The only reason this wouldn't work
properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine
in 5.15.0-1043.

Likely cause:
1045 adds this patch: 
https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4
 . This later patch indicates that the former patch introduced some ordering 
problems. 
https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5
 . That later patch isn't applied to 1045.

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

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

Title:
  [regression] Unable to initialize SGX enclaves with XFRM other than 3

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

Bug description:
  In 5.15.0-1045, only loading enclaves with XFRM set to 3 works,
  sgx_encl_init returns EINVAL. The only reason this wouldn't work
  properly is if sgx_drv_init thinks XSAVE isn't enabled. This works
  fine in 5.15.0-1043.

  Likely cause:
  1045 adds this patch: 
https://github.com/torvalds/linux/commit/b81fac906a8f9e682e513ddd95697ec7a20878d4
 . This later patch indicates that the former patch introduced some ordering 
problems. 
https://github.com/torvalds/linux/commit/2c66ca3949dc701da7f4c9407f2140ae425683a5
 . That later patch isn't applied to 1045.

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


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

[Kernel-packages] [Bug 2034718] Re: Backport request: drm/amdgpu: fix clearing mappings for BOs that are always valid in VM

[kisak]

I do not believe that logs are necessary or beneficial for this bug
report given that the nature of the issue is well understood.

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

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

Title:
  Backport request: drm/amdgpu: fix clearing mappings for BOs that are
  always valid in VM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Good day Ubuntu kernel maintainers,

  Please evaluate
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ea2c3c08554601b051d91403a241266e1cf490a5
  for backport into all actively maintained Ubuntu flavors of the Linux
  kernel.

  This commit is needed to stabilize Starfield with mesa/RADV. There was
  a stopgap workaround put into mesa 23.1.4, but that workaround harmed
  other games and it needed to be fixed properly in the kernel. The mesa
  workaround is removed in mesa 23.1.7 and mesa git main.

  As far as I can tell, all Ubuntu kernels do not meet the 5.15.121+,
  6.1.40+ or 6.4.5+ baseline noted in
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/24774

  There's what looks like an automated mailing list message that this
  commit was queued for the upstream 5.4 series at some point near
  5.4.250, but it's not in the linux changelog, so there might be a
  conflict denominating it from that kernel.

  Expected kernels affected: Focal HWE and Jammy (5.15 based), Jammy HWE
  and Lunar (6.2 based), and Mantic (6.3 based)

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


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

[Kernel-packages] [Bug 2032378] Re: Devlink backport: fix race and lock issue

[Bodong Wang]

** Merge proposal linked:
   
https://code.launchpad.net/~bodong-wang/ubuntu/+source/linux-bluefield/+git/jammy/+merge/450916

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

Title:
  Devlink backport: fix race and lock issue

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  Summary:
  machine get stuck if try to switch to switchdev mode while toggling ns over 
BF kernel.
  This is due to missing lock refactor series devlink and driver from kernel 6.0

  How to test:
  1. Configure SRIOV
  2. Enable switchdev mode
  3. Devlink reload
  4. Add/Del network namespace

  Note: Need to run the test multiple times to reproduce the issue.

  How to fix:
  Need to backport a series of devlink patches into BlueField 5.15 kernel, from 
6.0 upstream kernel.
  Patches needed for 5.4/5.15 kernel:

  First series: 367dfa121205^..f0680ef0f949

  second series: 5502e8712c9b^..c90005b5f75c

  Also needed: 644a66c60f02

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


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

[Kernel-packages] [Bug 2034732] Re: The 50-kdump-tools.rules file needs update for latest kernel 6.6 feature

[Eric DeVolder]

** Summary changed:

- The 98-kexec.rules file needs update for latest kernel 6.6 feature
+ The 50-kdump-tools.rules file needs update for latest kernel 6.6 feature

** Description changed:

  The following series has landed in mainline, and will be present in 6.6.
  
-  "crash: Kernel handling of CPU and memory hot un/plug"
-  https://lore.kernel.org/lkml/20230814214446.6659-1-eric.devol...@oracle.com/
+  "crash: Kernel handling of CPU and memory hot un/plug"
+  https://lore.kernel.org/lkml/20230814214446.6659-1-eric.devol...@oracle.com/
  
- 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d68b4b6f307d155475cce541f2aee938032ed22e
+  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d68b4b6f307d155475cce541f2aee938032ed22e
  
- To take advantage of the performance benefits of that series, 98-kexec.rules
+ To take advantage of the performance benefits of that series, 
50-kdump-tools.rules
  needs an update to optimize the handling of CPU and memory hotplug changes.
- 
- These lines need to be added to the top of 98-kexec.rules:
- 
-# The kernel updates the crash elfcorehdr for CPU and memory changes
-SUBSYSTEM=="cpu", ATTRS{crash_hotplug}=="1", GOTO="kdump_reload_end"
-SUBSYSTEM=="memory", ATTRS{crash_hotplug}=="1", GOTO="kdump_reload_end"
  
  It is safe to deploy these rule updates now, ahead of distros/kernels
  enabling the feature, since the crash_hotplug sysfs nodes would not be
- present and thus the newly introduced rules in 98-kexec would act as a
+ present and thus the newly introduced rules in 50-kdump-tools would act as a
  nop-op and fall thru for legacy behavior. But when distros/kernels
- enable the feature, then 98-kexec rules is ready and can properly take
+ enable the feature, then 50-kdump-tools rules is ready and can properly take
  advantage.

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

Title:
  The 50-kdump-tools.rules file needs update for latest kernel 6.6
  feature

Status in kexec-tools package in Ubuntu:
  New

Bug description:
  The following series has landed in mainline, and will be present in
  6.6.

   "crash: Kernel handling of CPU and memory hot un/plug"
   https://lore.kernel.org/lkml/20230814214446.6659-1-eric.devol...@oracle.com/

   
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d68b4b6f307d155475cce541f2aee938032ed22e

  To take advantage of the performance benefits of that series, 
50-kdump-tools.rules
  needs an update to optimize the handling of CPU and memory hotplug changes.

  It is safe to deploy these rule updates now, ahead of distros/kernels
  enabling the feature, since the crash_hotplug sysfs nodes would not be
  present and thus the newly introduced rules in 50-kdump-tools would act as a
  nop-op and fall thru for legacy behavior. But when distros/kernels
  enable the feature, then 50-kdump-tools rules is ready and can properly take
  advantage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/2034732/+subscriptions


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

[Kernel-packages] [Bug 2034732] [NEW] The 98-kexec.rules file needs update for latest kernel 6.6 feature

[Eric DeVolder]

Public bug reported:

The following series has landed in mainline, and will be present in 6.6.

 "crash: Kernel handling of CPU and memory hot un/plug"
 https://lore.kernel.org/lkml/20230814214446.6659-1-eric.devol...@oracle.com/

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d68b4b6f307d155475cce541f2aee938032ed22e

To take advantage of the performance benefits of that series, 98-kexec.rules
needs an update to optimize the handling of CPU and memory hotplug changes.

These lines need to be added to the top of 98-kexec.rules:

   # The kernel updates the crash elfcorehdr for CPU and memory changes
   SUBSYSTEM=="cpu", ATTRS{crash_hotplug}=="1", GOTO="kdump_reload_end"
   SUBSYSTEM=="memory", ATTRS{crash_hotplug}=="1", GOTO="kdump_reload_end"

It is safe to deploy these rule updates now, ahead of distros/kernels
enabling the feature, since the crash_hotplug sysfs nodes would not be
present and thus the newly introduced rules in 98-kexec would act as a
nop-op and fall thru for legacy behavior. But when distros/kernels
enable the feature, then 98-kexec rules is ready and can properly take
advantage.

** Affects: kexec-tools (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  The 98-kexec.rules file needs update for latest kernel 6.6 feature

Status in kexec-tools package in Ubuntu:
  New

Bug description:
  The following series has landed in mainline, and will be present in
  6.6.

   "crash: Kernel handling of CPU and memory hot un/plug"
   https://lore.kernel.org/lkml/20230814214446.6659-1-eric.devol...@oracle.com/

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d68b4b6f307d155475cce541f2aee938032ed22e

  To take advantage of the performance benefits of that series, 98-kexec.rules
  needs an update to optimize the handling of CPU and memory hotplug changes.

  These lines need to be added to the top of 98-kexec.rules:

 # The kernel updates the crash elfcorehdr for CPU and memory changes
 SUBSYSTEM=="cpu", ATTRS{crash_hotplug}=="1", GOTO="kdump_reload_end"
 SUBSYSTEM=="memory", ATTRS{crash_hotplug}=="1", GOTO="kdump_reload_end"

  It is safe to deploy these rule updates now, ahead of distros/kernels
  enabling the feature, since the crash_hotplug sysfs nodes would not be
  present and thus the newly introduced rules in 98-kexec would act as a
  nop-op and fall thru for legacy behavior. But when distros/kernels
  enable the feature, then 98-kexec rules is ready and can properly take
  advantage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/2034732/+subscriptions


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

[Kernel-packages] [Bug 2031352] Re: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen

[Juerg Haefliger]

Derp, yes, you're right. There seem to be two different issues that
result in similarly looking reboot/poweroff/suspend/resume problems. I
shouldn't have used your bug to track the nouveau issue, since you're
not using nouveau but I've missed that. Apologies for the mess. There's
the other bug 2031969 that is probably your problem.

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

Title:
  Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot
  screen

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-6.2 package in Ubuntu:
  Confirmed
Status in linux-hwe-6.2 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed

Bug description:
  [Impact]

  After updating to Kernel 6.2 a few days ago, I have been experiencing
  issues with my system's shutdown and reboot functions. During these
  processes, the system becomes unresponsive and hangs on a black
  screen, which displays both the Dell and Ubuntu logos. This issue is
  inconsistent; it happens sporadically. Currently, the only workaround
  I've found to successfully shut down the system is to forcibly power
  off the machine by holding down the power button for 5 seconds.

  I've also tested a fresh installation of Ubuntu 22.04.3.

  [Fix]

  Updated patch from linux-next:
  https://patchwork.freedesktop.org/patch/538562/

  [Test Case]

  Suspend,resume,shutdown,reboot should all work correctly. No nouveau
  stack trace in the kernel log.

  [Where Problems Could Occur]

  Limited to nouveau driver that wants to load nonexistent ACR firmware.
  Only nvidia GPUs are affected.

  [Additional information]

  

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd 249.11-0ubuntu3.9
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 14 22:41:14 2023
  InstallationDate: Installed on 2023-08-14 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813)
  MachineType: Dell Inc. XPS 8930
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2023
  dmi.bios.release: 1.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.30
  dmi.board.name: 0T88YD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.sku: 0859
  dmi.product.version: 1.1.30
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-08-13T20:57:27
  mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27

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


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

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

[Ubuntu Kernel Bot]

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

apport-collect 2034718

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

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

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

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

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

Title:
  Backport request: drm/amdgpu: fix clearing mappings for BOs that are
  always valid in VM

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Good day Ubuntu kernel maintainers,

  Please evaluate
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ea2c3c08554601b051d91403a241266e1cf490a5
  for backport into all actively maintained Ubuntu flavors of the Linux
  kernel.

  This commit is needed to stabilize Starfield with mesa/RADV. There was
  a stopgap workaround put into mesa 23.1.4, but that workaround harmed
  other games and it needed to be fixed properly in the kernel. The mesa
  workaround is removed in mesa 23.1.7 and mesa git main.

  As far as I can tell, all Ubuntu kernels do not meet the 5.15.121+,
  6.1.40+ or 6.4.5+ baseline noted in
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/24774

  There's what looks like an automated mailing list message that this
  commit was queued for the upstream 5.4 series at some point near
  5.4.250, but it's not in the linux changelog, so there might be a
  conflict denominating it from that kernel.

  Expected kernels affected: Focal HWE and Jammy (5.15 based), Jammy HWE
  and Lunar (6.2 based), and Mantic (6.3 based)

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


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

[Kernel-packages] [Bug 2034106] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

Title:
  Bluetooth is scanning for devices but it does not find anything, even
  if I have bluetooth devices close to the laptop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I had the same problem with the previous version of Ubuntu, but I
  updated to Ubuntu 23.04, because I was thinking that with the update
  the bug would be fixed. I can turn on or off Bluetooth on my Asus
  Vivobook, but nothing happens, it does not find any device, like
  smartphone, speaker, etc.

  I did a little research on forums, and it seems that there is not a
  problem with the laptop's Bluetooth adapter, but with the kernel. So I
  decided to try this and it seems that if I boot Kernel version 6.0.19
  everything is working fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubuntu-release-upgrader-core 1:23.04.6
  ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  5 10:21:56 2023
  InstallationDate: Installed on 2023-08-26 (9 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

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


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

[Kernel-packages] [Bug 2034106] Re: Bluetooth is scanning for devices but it does not find anything, even if I have bluetooth devices close to the laptop

[Nick Rosbrook]

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

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

Title:
  Bluetooth is scanning for devices but it does not find anything, even
  if I have bluetooth devices close to the laptop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I had the same problem with the previous version of Ubuntu, but I
  updated to Ubuntu 23.04, because I was thinking that with the update
  the bug would be fixed. I can turn on or off Bluetooth on my Asus
  Vivobook, but nothing happens, it does not find any device, like
  smartphone, speaker, etc.

  I did a little research on forums, and it seems that there is not a
  problem with the laptop's Bluetooth adapter, but with the kernel. So I
  decided to try this and it seems that if I boot Kernel version 6.0.19
  everything is working fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: ubuntu-release-upgrader-core 1:23.04.6
  ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  5 10:21:56 2023
  InstallationDate: Installed on 2023-08-26 (9 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

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


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

[Kernel-packages] [Bug 2034106] [NEW] Bluetooth is scanning for devices but it does not find anything, even if I have bluetooth devices close to the laptop

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I had the same problem with the previous version of Ubuntu, but I
updated to Ubuntu 23.04, because I was thinking that with the update the
bug would be fixed. I can turn on or off Bluetooth on my Asus Vivobook,
but nothing happens, it does not find any device, like smartphone,
speaker, etc.

I did a little research on forums, and it seems that there is not a
problem with the laptop's Bluetooth adapter, but with the kernel. So I
decided to try this and it seems that if I boot Kernel version 6.0.19
everything is working fine.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: ubuntu-release-upgrader-core 1:23.04.6
ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16
Uname: Linux 6.2.0-32-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep  5 10:21:56 2023
InstallationDate: Installed on 2023-08-26 (9 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeTermlog:

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


** Tags: amd64 apport-bug dist-upgrade lunar wayland-session
-- 
Bluetooth is scanning for devices but it does not find anything, even if I have 
bluetooth devices close to the laptop
https://bugs.launchpad.net/bugs/2034106
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

[Kernel-packages] [Bug 2034718] [NEW] Backport request: drm/amdgpu: fix clearing mappings for BOs that are always valid in VM

[kisak]

Public bug reported:

Good day Ubuntu kernel maintainers,

Please evaluate
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ea2c3c08554601b051d91403a241266e1cf490a5
for backport into all actively maintained Ubuntu flavors of the Linux
kernel.

This commit is needed to stabilize Starfield with mesa/RADV. There was a
stopgap workaround put into mesa 23.1.4, but that workaround harmed
other games and it needed to be fixed properly in the kernel. The mesa
workaround is removed in mesa 23.1.7 and mesa git main.

As far as I can tell, all Ubuntu kernels do not meet the 5.15.121+,
6.1.40+ or 6.4.5+ baseline noted in
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/24774

There's what looks like an automated mailing list message that this
commit was queued for the upstream 5.4 series at some point near
5.4.250, but it's not in the linux changelog, so there might be a
conflict denominating it from that kernel.

Expected kernels affected: Focal HWE and Jammy (5.15 based), Jammy HWE
and Lunar (6.2 based), and Mantic (6.3 based)

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

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

Title:
  Backport request: drm/amdgpu: fix clearing mappings for BOs that are
  always valid in VM

Status in linux package in Ubuntu:
  New

Bug description:
  Good day Ubuntu kernel maintainers,

  Please evaluate
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ea2c3c08554601b051d91403a241266e1cf490a5
  for backport into all actively maintained Ubuntu flavors of the Linux
  kernel.

  This commit is needed to stabilize Starfield with mesa/RADV. There was
  a stopgap workaround put into mesa 23.1.4, but that workaround harmed
  other games and it needed to be fixed properly in the kernel. The mesa
  workaround is removed in mesa 23.1.7 and mesa git main.

  As far as I can tell, all Ubuntu kernels do not meet the 5.15.121+,
  6.1.40+ or 6.4.5+ baseline noted in
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/24774

  There's what looks like an automated mailing list message that this
  commit was queued for the upstream 5.4 series at some point near
  5.4.250, but it's not in the linux changelog, so there might be a
  conflict denominating it from that kernel.

  Expected kernels affected: Focal HWE and Jammy (5.15 based), Jammy HWE
  and Lunar (6.2 based), and Mantic (6.3 based)

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


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

[Kernel-packages] [Bug 2031352] Re: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen

[Cristiano Fraga G. Nunes]

Hi @juergh,

I'd like to inform you that I was the one who reported this bug. All
attached logs are from my machine.

I noticed that you changed the bug description, pointing to an issue
with the "Nouveau" driver.

But I'd like to clarify that at no point did I use the Nouveau driver.

Best regards,

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

Title:
  Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot
  screen

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-6.2 package in Ubuntu:
  Confirmed
Status in linux-hwe-6.2 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed

Bug description:
  [Impact]

  After updating to Kernel 6.2 a few days ago, I have been experiencing
  issues with my system's shutdown and reboot functions. During these
  processes, the system becomes unresponsive and hangs on a black
  screen, which displays both the Dell and Ubuntu logos. This issue is
  inconsistent; it happens sporadically. Currently, the only workaround
  I've found to successfully shut down the system is to forcibly power
  off the machine by holding down the power button for 5 seconds.

  I've also tested a fresh installation of Ubuntu 22.04.3.

  [Fix]

  Updated patch from linux-next:
  https://patchwork.freedesktop.org/patch/538562/

  [Test Case]

  Suspend,resume,shutdown,reboot should all work correctly. No nouveau
  stack trace in the kernel log.

  [Where Problems Could Occur]

  Limited to nouveau driver that wants to load nonexistent ACR firmware.
  Only nvidia GPUs are affected.

  [Additional information]

  

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd 249.11-0ubuntu3.9
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 14 22:41:14 2023
  InstallationDate: Installed on 2023-08-14 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813)
  MachineType: Dell Inc. XPS 8930
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2023
  dmi.bios.release: 1.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.30
  dmi.board.name: 0T88YD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.sku: 0859
  dmi.product.version: 1.1.30
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-08-13T20:57:27
  mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27

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


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

[Kernel-packages] [Bug 2034594] Re: mlxbf-ptm: add thermal envelope debugfs node

[Tim Gardner]

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

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

Title:
  mlxbf-ptm: add thermal envelope debugfs node

Status in linux-bluefield package in Ubuntu:
  New
Status in linux-bluefield source package in Jammy:
  New

Bug description:
  SRU Justification:

  [Impact]

  mlxbf-ptm is a kernel driver that provides debufgs interface for system
  software to monitor Bluefield devices' power and thermal management
  parameters.

  [Fix]

  This change:
  * This change adds additional debugfs node that gets the current thermal
    envelope set in the thermal state machine

  [Test Case]

  * After installing the kernel module, debugfs entry at
    /sys/kernel/debug/mlxbf-ptm will be created
  * monitors/status folder contains read-only parameters reported from the
    Bluefield device
  * cat /sys/kernel/debug/mlxbf-ptm/temp_envelope shows current thermal
    envelope

  [Regression Potential]

  * Minimal - as these are read-only parameters that report Bluefield device
    information.

  [Other]

  * This code is likely to change depending on feedback we received from
    maintainers.

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


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

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

[Ubuntu Kernel Bot]

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

apport-collect 2034701

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

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

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

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

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

Title:
  unexpected system behaviour after kernel update

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  since last kernel updates on ubuntu 20.04 and 22.04 we see lines like
  this in syslog after boot:

  Sep  7 13:10:53 myhost kernel: [1.202296] pci :00:15.4: BAR 13: no 
space for [io  size 0x1000]
  Sep  7 13:10:53 myhost kernel: [1.202387] pci :00:15.4: BAR 13: 
failed to assign [io  size 0x1000]

  
  We see this on Ubuntu 20.04 after installing kernel 5.4.0-162-generic and on 
ubuntu 22.04 after installing kernel 5.15.0-83-generic

  Since this time we notice some strange server behaviour.

  - unexpected reboots during workhours
  - systems hanging/freezing which requires a hardstop of the machine
  - systems with high load but no significant number of processes, even on non 
productive machines with usually zero load.

  We use most of our ubuntu servers as virtual machines in a VMWare Environment 
with VSphere and ESXi 7.0.3
  There were no VMWare updates. I can say this with certainty because iam the 
responsible person for VMWare too and i did not install any ESXi Updates last 
days.
  Other OS not affected as i can see.

  Thank you,
  Hans

  p.s. i wanted to help and wanted to choose fitting package from dropdown "
  In what package did you find this bug?" above this Inputfield, but it seems 
that packages like linux-image-5.15.0-83-generic (or similiar i tried 
somethging...) are unknown and search respondes with improper suggestions.

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


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

[Kernel-packages] [Bug 2034701] Re: unexpected system behaviour after kernel update

[Paul White]

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

** Tags added: focal jammy

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

Title:
  unexpected system behaviour after kernel update

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  since last kernel updates on ubuntu 20.04 and 22.04 we see lines like
  this in syslog after boot:

  Sep  7 13:10:53 myhost kernel: [1.202296] pci :00:15.4: BAR 13: no 
space for [io  size 0x1000]
  Sep  7 13:10:53 myhost kernel: [1.202387] pci :00:15.4: BAR 13: 
failed to assign [io  size 0x1000]

  
  We see this on Ubuntu 20.04 after installing kernel 5.4.0-162-generic and on 
ubuntu 22.04 after installing kernel 5.15.0-83-generic

  Since this time we notice some strange server behaviour.

  - unexpected reboots during workhours
  - systems hanging/freezing which requires a hardstop of the machine
  - systems with high load but no significant number of processes, even on non 
productive machines with usually zero load.

  We use most of our ubuntu servers as virtual machines in a VMWare Environment 
with VSphere and ESXi 7.0.3
  There were no VMWare updates. I can say this with certainty because iam the 
responsible person for VMWare too and i did not install any ESXi Updates last 
days.
  Other OS not affected as i can see.

  Thank you,
  Hans

  p.s. i wanted to help and wanted to choose fitting package from dropdown "
  In what package did you find this bug?" above this Inputfield, but it seems 
that packages like linux-image-5.15.0-83-generic (or similiar i tried 
somethging...) are unknown and search respondes with improper suggestions.

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


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

[Kernel-packages] [Bug 2029328] Re: [ADL-N][RPL-S] support ISHTP module

[Jian Hui Lee]

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

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

Title:
  [ADL-N][RPL-S] support ISHTP module

Status in linux-intel-iotg package in Ubuntu:
  Invalid
Status in linux-intel-iotg source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  support ishtp module on intel adl-n/rpl-s platform

  [Fix]
  add the corresponding pci id for each platform.
  the rest of the patches are requested by intel. they belong to code revised, 
bug fixed and device setup.

  [Test]
  1. compile test
  2. run the kernel on the target platform to see if the module is loaded 
correctly.
  3. run suspend/reboot to see if any error occurs.

  [Where problems could occur]
  all of the patches are quite clear and easy to understand, so the regression 
risk should be low.

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


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

[Kernel-packages] [Bug 2031057] Re: [EHL] Screen flickering when the setup is in multiple monitors with mirror mode output

[Jian Hui Lee]

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

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

Title:
  [EHL] Screen flickering when the setup is in multiple monitors with
  mirror mode output

Status in linux-intel-iotg package in Ubuntu:
  Invalid
Status in linux-intel-iotg source package in Jammy:
  Fix Committed

Bug description:
  [Summary]
  Display is flickering in Mirror mode and below 30 Hz refresh rate
  [Steps to reproduce]
  1. Install Ubuntu Desktop 22.04.2
  2. Boot to desktop
  3. Connect 2 FHD monitors to DP ports and HDMI port
  4. Change to Mirror Mode.
  5. Change back to Joint Mode and change refresh rate to 30 Hz (or below)

  [Expected result]
  1. Display on both DP and HDMI show correctly on Mirror mode
  2. Display on both DP and HDMI show correctly on refresh rate below 30Hz

  [Actual result]
  1. Display Flicker on display in Mirror Mode.
  2. Display Flicker on display when select 30 Hz on refresh rate

  [Failure rate]
  100%

  [Additional information]
  bios-version: V1.11
  CPU: Intel(R) Celeron(R) N6210 @ 1.20GHz (Elkhart Lake)
  GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 4555 (rev 01)
  kernel-version: 5.15.0-1027-intel-iotg

  Note:
  Single mode does not have this issue.

  LP: #2020412
  LP: #2031056

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


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

[Kernel-packages] [Bug 2034701] [NEW] unexpected system behaviour after kernel update

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hello,

since last kernel updates on ubuntu 20.04 and 22.04 we see lines like
this in syslog after boot:

Sep  7 13:10:53 myhost kernel: [1.202296] pci :00:15.4: BAR 13: no 
space for [io  size 0x1000]
Sep  7 13:10:53 myhost kernel: [1.202387] pci :00:15.4: BAR 13: failed 
to assign [io  size 0x1000]


We see this on Ubuntu 20.04 after installing kernel 5.4.0-162-generic and on 
ubuntu 22.04 after installing kernel 5.15.0-83-generic

Since this time we notice some strange server behaviour.

- unexpected reboots during workhours
- systems hanging/freezing which requires a hardstop of the machine
- systems with high load but no significant number of processes, even on non 
productive machines with usually zero load.

We use most of our ubuntu servers as virtual machines in a VMWare Environment 
with VSphere and ESXi 7.0.3
There were no VMWare updates. I can say this with certainty because iam the 
responsible person for VMWare too and i did not install any ESXi Updates last 
days.
Other OS not affected as i can see.

Thank you,
Hans

p.s. i wanted to help and wanted to choose fitting package from dropdown "
In what package did you find this bug?" above this Inputfield, but it seems 
that packages like linux-image-5.15.0-83-generic (or similiar i tried 
somethging...) are unknown and search respondes with improper suggestions.

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


** Tags: bot-comment
-- 
unexpected system behaviour after kernel update
https://bugs.launchpad.net/bugs/2034701
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

[Kernel-packages] [Bug 2022361] Re: Please enable Renesas RZ platform serial installer

[Ubuntu Kernel Bot]

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

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-v2 verification-needed-focal-linux

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

Title:
  Please enable Renesas RZ platform serial installer

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  [Impact]

  The ubuntu installer does not work via serial ports for Renesas boards like
  RZ/G2M-HiHope 
(https://www.renesas.com/us/en/products/microcontrollers-microprocessors/rz-mpus/rzg2m-hihope-rzg2m-reference-board,
 RZ/G2L, RZ/G2LC, RZ/G2UL SMARC Board 
(https://renesas.info/wiki/RZ-G/RZ-G2L_SMARC).

  The installation can be done using HDMI ports, but it would be nice to
  support installation via serial port as well.

  [Test case]

  Try to install Ubuntu on a Renesas board.

  [Fix]

  Statically build SuperH SCI(F) serial port support (with
  earlyconsole).

  [Regression potential]

  Statically building an additional driver in the kernel can make the
  kernel image bigger, potentially causing boot issues in small (arm64 /
  armhf) platforms.

  [Original bug report]

  Package: linux
  Version: Ubuntu-6.2.0-21.21
  Severity: normal
  File: /mantic/debian.master/config/annotations

  Dear Maintainer,

  The ubuntu kernel is missing a few configuration options for Renesas
  RZ/G2M MPU as below:

  #Modify the following config from m to y.

  CONFIG_SERIAL_SH_SCI=y

  #add below configuration

  CONFIG_SERIAL_SH_SCI_CONSOLE=y
  CONFIG_SERIAL_SH_SCI_EARLYCON=y

  The above changes are required in annotations file:
  "/mantic/debian.master/config/annotations"

  code location:

  https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/mantic/tree/debian.master/config/annotations#n11372

  #Modify the following line (change 'm' to 'y')

  CONFIG_SERIAL_SH_SCI policy<{'arm64': 'y', 'armhf': 'y'}>

  #Add the following lines:

  CONFIG_SERIAL_SH_SCI_CONSOLE policy<{'arm64': 'y', 'armhf': 'y'}>
  CONFIG_SERIAL_SH_SCI_EARLYCON policy<{'arm64': 'y', 'armhf': 'y'}>

  Could you please add those configuration options to the Ubuntu kernel?

  Best Regards
  John

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


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

[Kernel-packages] [Bug 2030872] Re: Azure: hv_netvsc: add support for vlans in AF_PACKET mode

[Ubuntu Kernel Bot]

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

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-v2 verification-needed-focal-linux

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

Title:
  Azure: hv_netvsc: add support for vlans in AF_PACKET mode

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

Bug description:
  SRU Justification

  [Impact]

  Microsoft has requested the inclusion of [1] into the Focal Azure
  kernel.

  [1] -
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fdd8fac47ce67bae17feed9b74b3505e432fe561

  [Test Plan]

  Microsoft Tested

  [Regression potential]

  Could affect 802.1Q packets

  [Other Info]

  SF: #00365836

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


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

[Kernel-packages] [Bug 2034491] Re: Fix blank display when Thunderbolt monitor is plugged second time

[Timo Aaltonen]

** Changed in: linux-oem-6.1 (Ubuntu Jammy)
   Status: Confirmed => Fix Committed

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

Title:
  Fix blank display when Thunderbolt monitor is plugged second time

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Confirmed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  When a Thunderbolt monitor gets plugged to an AMD laptop for second time, the 
Thunderbolt monitor remains blank.

  [Fix]
  Reinitialize TMU and perform proper Time Synchronization Handshake every time.

  [Test]
  The Thunderbolt monitor still has image after many replugging.

  [Where problems could occur]
  This change the flow on disabling TMU, which is responsible for time 
synchronization, so behavior of Thunderbolt docking might be affected. Per my 
limited test no issue has been observed.

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


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

[Kernel-packages] [Bug 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)

[ahmed hanafi al-sayed]

done @Juerg Haefliger I restarted the pc will monitor and update this
comment if any thing happened

uname -a

Linux OptiPlex-3090 6.2.0-32-generic #32+lp2031537 SMP PREEMPT_DYNAMIC
Tue Sep  5 07:27:25 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

sudo dmesg

[sudo] password for : 
[0.00] Linux version 6.2.0-32-generic (ubuntu@ip-10-0-61-144) 
(x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~23.04) 12.3.0, GNU ld (GNU 
Binutils for Ubuntu) 2.40) #32+lp2031537 SMP PREEMPT_DYNAMIC Tue Sep  5 
07:27:25 UTC 2023 (Ubuntu 6.2.0-32.32+lp2031537-generic 6.2.16)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic 
root=UUID=bad00fc3-af76-403c-a8f8-e4b840d16e23 ro quiet splash vt.handoff=7

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

Title:
  Ethernet not stable 23.04 (RTL8168/8169)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  hello,
  it is my first time reporting a pug hope it is the last

  there is thread here
  https://ubuntuforums.org/showthread.php?t=2489146=14151513

  another user experienced similar issue

  my network work fine at startup keep working for hours then disconnect and 
cannot reconnect without a restart
  I tested the cable using another pc and it was working repluged with no 
difference

  I thought it is caused by nvidia driver so changed it and the problem
  persist

  I use systemd-networkd

  
  uname -a
  Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed 
Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  
  lspci:
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b)

  
  dmesg:

  [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): 
apparmor="ALLOWED" operation="file_perm" class="file" 
profile="libreoffice-oosplash" 
name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" 
pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
  [Mon Aug 7 12:39:19 2023] [ cut here ]
  [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 
timed out
  [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at 
net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250
  [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer 
nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 
snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common 
soundwire_intel soundwire_generic_allocation soundwire_cadence 
snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp 
snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core 
snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel 
snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr 
intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep 
intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 
snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm 
irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec 
polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clm
 ulni_intel rc_core
  [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper 
snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas 
syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd 
sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof 
firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc 
ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 
hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci 
spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus 
xhci_pci_renesas idma64 wmi pinctrl_cannonlake
  [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 
6.2.0-26-generic #26-Ubuntu
  [Mon Aug 7 12:39:19 2023] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 
2.13.1 05/10/2023
  [Mon Aug 7 12:39:19 2023] RIP: 0010:dev_watchdog+0x23a/0x250
  [Mon Aug 7 12:39:19 2023] Code: 00 e9 2b ff ff ff 48 89 df c6 05 ba a6 d5 01 
01 e8 3b 07 f8 ff 44 89 f1 48 89 de 48 c7 c7 f8 25 67 9d 48 89 c2 e8 06 09 29 
ff <0f> 0b e9 1c ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00
  [Mon Aug 7 12:39:19 2023] RSP: 0018:b40c40254e38 EFLAGS: 00010246
  [Mon Aug 7 12:39:19 2023] RAX:  RBX: 997996868000 RCX: 

  [Mon Aug 7 12:39:19 2023] RDX:  RSI:  RDI: 

  [Mon Aug 7 12:39:19 2023] RBP: b40c40254e68 R08:  R09: 

  [Mon Aug 7 12:39:19 2023] R10:  R11:  

[Kernel-packages] [Bug 2034688] Re: installation of kernel headers fail with "Read-only file system" error

[Dimitri John Ledkov]

# ls -latr /lib/modules/6.3.0-7-generic/build
lrwxrwxrwx 1 root root 38 Jun  8 14:44 /lib/modules/6.3.0-7-generic/build -> 
/usr/src/linux-headers-6.3.0-7-generic


Pondering if such a link should be shipped by all the snaps.

And pondering if .deb should change it from a shipped file, to a
postinst scriplet that creates it dynamically.

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

Title:
  installation of kernel headers fail with "Read-only file system" error

Status in ubuntu-desktop-installer:
  Triaged
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Mantic 20230907

  Installation of packages that ship files in /lib/modules or
  /lib/firmware are expected to fail, so their installation must be
  prevented.

  For instance:

  $ apt install linux-headers-generic-6.3.0-7
  Reading package lists...
  Building dependency tree...
  Reading state information...
  linux-headers-6.3.0-7 is already the newest version (6.3.0-7.7).
  The following packages will be upgraded:
linux-headers-6.3.0-7-generic
  1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  51 not fully installed or removed.
  Need to get 0 B/3,667 kB of archives.
  After this operation, 27.9 MB of additional disk space will be used.
  (Reading database ... 132615 files and directories currently installed.)
  Preparing to unpack .../linux-headers-6.3.0-7-generic_6.3.0-7.7_amd64.deb ...
  Unpacking linux-headers-6.3.0-7-generic (6.3.0-7.7) over (6.3.0-7.7) ...
  dpkg: error processing archive 
/var/cache/apt/archives/linux-headers-6.3.0-7-generic_6.3.0-7.7_amd64.deb 
(--unpack):
   error creating symbolic link './lib/modules/6.3.0-7-generic/build': 
Read-only file system
  dpkg: error while cleaning up:
   unable to remove newly-extracted version of 
'/lib/modules/6.3.0-7-generic/build': Read-only file system
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-headers-6.3.0-7-generic_6.3.0-7.7_amd64.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2034688/+subscriptions


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

[Kernel-packages] [Bug 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)

[Juerg Haefliger]

The test is meaningless with 'pcie_aspm=off`. The test kernel has to
work without that parameter and if it doesn't it means the fix is no
good. Please test without the parameter.

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

Title:
  Ethernet not stable 23.04 (RTL8168/8169)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  hello,
  it is my first time reporting a pug hope it is the last

  there is thread here
  https://ubuntuforums.org/showthread.php?t=2489146=14151513

  another user experienced similar issue

  my network work fine at startup keep working for hours then disconnect and 
cannot reconnect without a restart
  I tested the cable using another pc and it was working repluged with no 
difference

  I thought it is caused by nvidia driver so changed it and the problem
  persist

  I use systemd-networkd

  
  uname -a
  Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed 
Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  
  lspci:
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b)

  
  dmesg:

  [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): 
apparmor="ALLOWED" operation="file_perm" class="file" 
profile="libreoffice-oosplash" 
name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" 
pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
  [Mon Aug 7 12:39:19 2023] [ cut here ]
  [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 
timed out
  [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at 
net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250
  [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer 
nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 
snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common 
soundwire_intel soundwire_generic_allocation soundwire_cadence 
snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp 
snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core 
snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel 
snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr 
intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep 
intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 
snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm 
irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec 
polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clm
 ulni_intel rc_core
  [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper 
snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas 
syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd 
sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof 
firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc 
ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 
hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci 
spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus 
xhci_pci_renesas idma64 wmi pinctrl_cannonlake
  [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 
6.2.0-26-generic #26-Ubuntu
  [Mon Aug 7 12:39:19 2023] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 
2.13.1 05/10/2023
  [Mon Aug 7 12:39:19 2023] RIP: 0010:dev_watchdog+0x23a/0x250
  [Mon Aug 7 12:39:19 2023] Code: 00 e9 2b ff ff ff 48 89 df c6 05 ba a6 d5 01 
01 e8 3b 07 f8 ff 44 89 f1 48 89 de 48 c7 c7 f8 25 67 9d 48 89 c2 e8 06 09 29 
ff <0f> 0b e9 1c ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00
  [Mon Aug 7 12:39:19 2023] RSP: 0018:b40c40254e38 EFLAGS: 00010246
  [Mon Aug 7 12:39:19 2023] RAX:  RBX: 997996868000 RCX: 

  [Mon Aug 7 12:39:19 2023] RDX:  RSI:  RDI: 

  [Mon Aug 7 12:39:19 2023] RBP: b40c40254e68 R08:  R09: 

  [Mon Aug 7 12:39:19 2023] R10:  R11:  R12: 
9979968684c8
  [Mon Aug 7 12:39:19 2023] R13: 99799686841c R14:  R15: 

  [Mon Aug 7 12:39:19 2023] FS: () 
GS:997da930() knlGS:
  [Mon Aug 7 12:39:19 2023] CS: 0010 DS:  ES:  CR0: 80050033
  [Mon Aug 7 12:39:19 2023] CR2: 0c4c01aa8000 CR3: 000329810004 CR4: 
003726e0
  [Mon Aug 7 12:39:19 2023] Call Trace:
  [Mon Aug 7 12:39:19 2023] 
  [Mon Aug 7 12:39:19 2023] ? __pfx_dev_watchdog+0x10/0x10
  [Mon 

Re: [Kernel-packages] [Bug 2033421] Re: package linux-headers-6.2.0-31-generic 6.2.0-31.31~22.04.1 failed to install/upgrade: installed linux-headers-6.2.0-31-generic package post-installation script

[John Brandon Olsen]

Thank you Juerg,

I am now struggling with failures because the dkms.conf is missing for 
that package.


/etc/kernel/header_postinst.d/dkms:
  * dkms: running auto installation service for kernel 6.2.0-32-generic
Error! Could not locate dkms.conf file.
File:
/var/lib/dkms/intel-platform-vsec-dkms/2023.20.0-21/source/dkms.conf
does not exist.
    ...fail!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 4
dpkg: error processing package linux-headers-6.2.0-32-generic
(--configure):
  installed linux-headers-6.2.0-32-generic package post-installation
script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of
linux-headers-generic-hwe-22.04:
  linux-headers-generic-hwe-22.04 depends on
linux-headers-6.2.0-32-generic; however:
   Package linux-headers-6.2.0-32-generic is not configured yet.

dpkg: error processing package linux-headers-generic-hwe-22.04
(--configure):
  dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of
linux-generic-hwe-22.04:
  linux-generic-hwe-22.04 depends on linux-headers-generic-hwe-22.04
(= 6.2.0.32.32~22.04.9); however:
   Package linux-headers-generic-hwe-22.04 is not configured yet.

dpkg: error processing package linux-generic-hwe-22.04 (--configure):
  dependency problems - leaving unconfigured
No apport report written because the error message indicates its a
followup error from a previous failure.
No apport report written because the erro
r message indicates its a followup error from a previous failure.
Processing triggers for linux-image-6.2.0-32-generic
(6.2.0-32.32~22.04.1) ...
/etc/kernel/postinst.d/dkms:
  * dkms: running auto installation service for kernel 6.2.0-32-generic
Error! Could not locate dkms.conf file.
File:
/var/lib/dkms/intel-platform-vsec-dkms/2023.20.0-21/source/dkms.conf
does not exist.
    ...fail!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 4
dpkg: error processing package linux-image-6.2.0-32-generic
(--configure):
  installed linux-image-6.2.0-32-generic package post-installation
script subprocess returned error exit status 1
No apport report written because MaxReports is reached already
Errors were encountered while processing:
  linux-headers-6.2.0-32-generic
  linux-headers-generic-hwe-22.04
  linux-generic-hwe-22.04
  linux-image-6.2.0-32-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)


On 8/30/23 02:38, Juerg Haefliger wrote:
> Your installation is botched. Remove that broken/unsupported DKMS:
>
> $ dkms remove intel-platform-vsec-dkms/2023.20.0-21 --all
>
> ** Changed in: linux-hwe-6.2 (Ubuntu)
> Status: New => Invalid
>
-- 

johnbrandonolsen Masthead Image    
John Brandon Olsen
(828) 490-9152
www.johnbrandonolsen.com 

  * Follow me on Twitter! 
  * Connected with me on LinkedIn!

  * Let's be friends on Facebook.


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

Title:
  package linux-headers-6.2.0-31-generic 6.2.0-31.31~22.04.1 failed to
  install/upgrade: installed linux-headers-6.2.0-31-generic package
  post-installation script subprocess returned error exit status 1

Status in linux-hwe-6.2 package in Ubuntu:
  Invalid

Bug description:
  Failed to install?

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-headers-6.2.0-31-generic 6.2.0-31.31~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Aug 29 08:00:32 2023
  ErrorMessage: installed linux-headers-6.2.0-31-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-05-03 (118 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.10
  SourcePackage: linux-hwe-6.2
  Title: package linux-headers-6.2.0-31-generic 6.2.0-31.31~22.04.1 failed to 
install/upgrade: installed linux-headers-6.2.0-31-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

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

[Ubuntu Kernel Bot]

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

apport-collect 2034688

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

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

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

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

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

Title:
  installation of kernel headers fail with "Read-only file system" error

Status in ubuntu-desktop-installer:
  Triaged
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Mantic 20230907

  Installation of packages that ship files in /lib/modules or
  /lib/firmware are expected to fail, so their installation must be
  prevented.

  For instance:

  $ apt install linux-headers-generic-6.3.0-7
  Reading package lists...
  Building dependency tree...
  Reading state information...
  linux-headers-6.3.0-7 is already the newest version (6.3.0-7.7).
  The following packages will be upgraded:
linux-headers-6.3.0-7-generic
  1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  51 not fully installed or removed.
  Need to get 0 B/3,667 kB of archives.
  After this operation, 27.9 MB of additional disk space will be used.
  (Reading database ... 132615 files and directories currently installed.)
  Preparing to unpack .../linux-headers-6.3.0-7-generic_6.3.0-7.7_amd64.deb ...
  Unpacking linux-headers-6.3.0-7-generic (6.3.0-7.7) over (6.3.0-7.7) ...
  dpkg: error processing archive 
/var/cache/apt/archives/linux-headers-6.3.0-7-generic_6.3.0-7.7_amd64.deb 
(--unpack):
   error creating symbolic link './lib/modules/6.3.0-7-generic/build': 
Read-only file system
  dpkg: error while cleaning up:
   unable to remove newly-extracted version of 
'/lib/modules/6.3.0-7-generic/build': Read-only file system
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-headers-6.3.0-7-generic_6.3.0-7.7_amd64.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2034688/+subscriptions


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

[Kernel-packages] [Bug 2034699] [NEW] zram-config has a missing dependency on linux-modules-extra-xxxx-generic

[Martin Wolf]

Public bug reported:

I am running a virtual sever at Hetzner who provides a very slim
preconfigured installation.

zram-config was not installed so I ran

```
apt install zram-config
```
which installed it without any dependencies.

after I started the service with
```
systemctl start zram-config.service
```
I got the following error message in journal:

```
Sep 07 10:53:00 Valheim-Server systemd[1]: Starting Initializes zram swaping...
Sep 07 10:53:00 Valheim-Server init-zram-swapping[747]: modprobe: FATAL: Module 
zram not found in directory /lib/modules/5.15.0-83-generic
Sep 07 10:53:00 Valheim-Server init-zram-swapping[745]: 
/usr/bin/init-zram-swapping: 10: cannot create /sys/block/zram0/disksize: 
Directory nonexistent
Sep 07 10:53:00 Valheim-Server init-zram-swapping[756]: mkswap: cannot open 
/dev/zram0: No such file or directory
Sep 07 10:53:00 Valheim-Server init-zram-swapping[758]: swapon: cannot open 
/dev/zram0: No such file or directory
```

I tried to locate zram.ko, but it was missing, so I tried to find out with
```
dkpg -S zram.ko
```
which package contained it: linux-modules-extra-5.15.0-83-generic

After I manually installed that specific package, zram started working with
```
systemctl restart zram-config.service
```

I know, this might be a corner-case, but I found at least two other
posts with the same problem in a very short time.

Now my question. Would it be possible to add linux-modules-extra--
generic as a dependency zo zram-config, since it is not useable without
it?

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-83-generic 5.15.0-83.92
ProcVersionSignature: Ubuntu 5.15.0-83.92-generic 5.15.116
Uname: Linux 5.15.0-83-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Sep  7 10:52 seq
 crw-rw 1 root audio 116, 33 Sep  7 10:52 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudID: hetzner
CloudName: hetzner
CloudPlatform: hetzner
CloudSubPlatform: metadata (http://169.254.169.254/hetzner/v1/metadata)
Date: Thu Sep  7 11:15:24 2023
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M
MachineType: Hetzner vServer
PciMultimedia:
 
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 virtio_gpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic 
root=UUID=35547664-ba55-4fc4-8762-754c30e132f0 ro consoleblank=0 
systemd.show_status=true console=tty1 console=ttyS0
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-83-generic N/A
 linux-backports-modules-5.15.0-83-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.18
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/11/2017
dmi.bios.release: 1.0
dmi.bios.vendor: Hetzner
dmi.bios.version: 2017
dmi.board.name: Standard PC (Q35 + ICH9, 2009)
dmi.board.vendor: KVM
dmi.board.version: pc-q35-6.2
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: NotSpecified
dmi.modalias: 
dmi:bvnHetzner:bvr2017:bd11/11/2017:br1.0:svnHetzner:pnvServer:pvr2017:rvnKVM:rnStandardPC(Q35+ICH9,2009):rvrpc-q35-6.2:cvnQEMU:ct1:cvrNotSpecified:skuTM:
dmi.product.family: Hetzner_vServer
dmi.product.name: vServer
dmi.product.sku: TM
dmi.product.version: 2017
dmi.sys.vendor: Hetzner

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


** Tags: amd64 apport-bug jammy uec-images

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

Title:
  zram-config has a missing dependency on linux-modules-extra--
  generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running a virtual sever at Hetzner who provides a very slim
  preconfigured installation.

  zram-config was not installed so I ran

  ```
  apt install zram-config
  ```
  which installed it without any dependencies.

  after I started the service with
  ```
  systemctl start zram-config.service
  ```
  I got the following error message in journal:

  ```
  Sep 07 

[Kernel-packages] [Bug 2034688] Re: installation of kernel headers fail with "Read-only file system" error

[Dimitri John Ledkov]

in general, it is useful to be able to install kernel headers even on
the confined system.

Potentially need to change something on either the deb, snap, or both
side to make all of that work.

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

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

Title:
  installation of kernel headers fail with "Read-only file system" error

Status in ubuntu-desktop-installer:
  Triaged
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Mantic 20230907

  Installation of packages that ship files in /lib/modules or
  /lib/firmware are expected to fail, so their installation must be
  prevented.

  For instance:

  $ apt install linux-headers-generic-6.3.0-7
  Reading package lists...
  Building dependency tree...
  Reading state information...
  linux-headers-6.3.0-7 is already the newest version (6.3.0-7.7).
  The following packages will be upgraded:
linux-headers-6.3.0-7-generic
  1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  51 not fully installed or removed.
  Need to get 0 B/3,667 kB of archives.
  After this operation, 27.9 MB of additional disk space will be used.
  (Reading database ... 132615 files and directories currently installed.)
  Preparing to unpack .../linux-headers-6.3.0-7-generic_6.3.0-7.7_amd64.deb ...
  Unpacking linux-headers-6.3.0-7-generic (6.3.0-7.7) over (6.3.0-7.7) ...
  dpkg: error processing archive 
/var/cache/apt/archives/linux-headers-6.3.0-7-generic_6.3.0-7.7_amd64.deb 
(--unpack):
   error creating symbolic link './lib/modules/6.3.0-7-generic/build': 
Read-only file system
  dpkg: error while cleaning up:
   unable to remove newly-extracted version of 
'/lib/modules/6.3.0-7-generic/build': Read-only file system
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-headers-6.3.0-7-generic_6.3.0-7.7_amd64.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2034688/+subscriptions


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

[Kernel-packages] [Bug 2034699] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

Title:
  zram-config has a missing dependency on linux-modules-extra--
  generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running a virtual sever at Hetzner who provides a very slim
  preconfigured installation.

  zram-config was not installed so I ran

  ```
  apt install zram-config
  ```
  which installed it without any dependencies.

  after I started the service with
  ```
  systemctl start zram-config.service
  ```
  I got the following error message in journal:

  ```
  Sep 07 10:53:00 Valheim-Server systemd[1]: Starting Initializes zram 
swaping...
  Sep 07 10:53:00 Valheim-Server init-zram-swapping[747]: modprobe: FATAL: 
Module zram not found in directory /lib/modules/5.15.0-83-generic
  Sep 07 10:53:00 Valheim-Server init-zram-swapping[745]: 
/usr/bin/init-zram-swapping: 10: cannot create /sys/block/zram0/disksize: 
Directory nonexistent
  Sep 07 10:53:00 Valheim-Server init-zram-swapping[756]: mkswap: cannot open 
/dev/zram0: No such file or directory
  Sep 07 10:53:00 Valheim-Server init-zram-swapping[758]: swapon: cannot open 
/dev/zram0: No such file or directory
  ```

  I tried to locate zram.ko, but it was missing, so I tried to find out with
  ```
  dkpg -S zram.ko
  ```
  which package contained it: linux-modules-extra-5.15.0-83-generic

  After I manually installed that specific package, zram started working with
  ```
  systemctl restart zram-config.service
  ```

  I know, this might be a corner-case, but I found at least two other
  posts with the same problem in a very short time.

  Now my question. Would it be possible to add linux-modules-extra--
  generic as a dependency zo zram-config, since it is not useable
  without it?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-83-generic 5.15.0-83.92
  ProcVersionSignature: Ubuntu 5.15.0-83.92-generic 5.15.116
  Uname: Linux 5.15.0-83-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep  7 10:52 seq
   crw-rw 1 root audio 116, 33 Sep  7 10:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: hetzner
  CloudName: hetzner
  CloudPlatform: hetzner
  CloudSubPlatform: metadata (http://169.254.169.254/hetzner/v1/metadata)
  Date: Thu Sep  7 11:15:24 2023
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: Hetzner vServer
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-83-generic 
root=UUID=35547664-ba55-4fc4-8762-754c30e132f0 ro consoleblank=0 
systemd.show_status=true console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-83-generic N/A
   linux-backports-modules-5.15.0-83-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.18
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2017
  dmi.bios.release: 1.0
  dmi.bios.vendor: Hetzner
  dmi.bios.version: 2017
  dmi.board.name: Standard PC (Q35 + ICH9, 2009)
  dmi.board.vendor: KVM
  dmi.board.version: pc-q35-6.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: NotSpecified
  dmi.modalias: 
dmi:bvnHetzner:bvr2017:bd11/11/2017:br1.0:svnHetzner:pnvServer:pvr2017:rvnKVM:rnStandardPC(Q35+ICH9,2009):rvrpc-q35-6.2:cvnQEMU:ct1:cvrNotSpecified:skuTM:
  dmi.product.family: Hetzner_vServer
  dmi.product.name: vServer
  dmi.product.sku: TM
  dmi.product.version: 2017
  dmi.sys.vendor: Hetzner

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


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

[Kernel-packages] [Bug 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)

[ahmed hanafi al-sayed]

thanks @Juery I reversed my comment #38 I want it to be up for as long
as possible to test it so if I don't have to I will keep is running till
the next reboot when pcie_aspm=off would be removed

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

Title:
  Ethernet not stable 23.04 (RTL8168/8169)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  hello,
  it is my first time reporting a pug hope it is the last

  there is thread here
  https://ubuntuforums.org/showthread.php?t=2489146=14151513

  another user experienced similar issue

  my network work fine at startup keep working for hours then disconnect and 
cannot reconnect without a restart
  I tested the cable using another pc and it was working repluged with no 
difference

  I thought it is caused by nvidia driver so changed it and the problem
  persist

  I use systemd-networkd

  
  uname -a
  Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed 
Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  
  lspci:
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b)

  
  dmesg:

  [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): 
apparmor="ALLOWED" operation="file_perm" class="file" 
profile="libreoffice-oosplash" 
name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" 
pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
  [Mon Aug 7 12:39:19 2023] [ cut here ]
  [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 
timed out
  [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at 
net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250
  [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer 
nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 
snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common 
soundwire_intel soundwire_generic_allocation soundwire_cadence 
snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp 
snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core 
snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel 
snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr 
intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep 
intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 
snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm 
irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec 
polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clm
 ulni_intel rc_core
  [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper 
snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas 
syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd 
sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof 
firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc 
ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 
hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci 
spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus 
xhci_pci_renesas idma64 wmi pinctrl_cannonlake
  [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 
6.2.0-26-generic #26-Ubuntu
  [Mon Aug 7 12:39:19 2023] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 
2.13.1 05/10/2023
  [Mon Aug 7 12:39:19 2023] RIP: 0010:dev_watchdog+0x23a/0x250
  [Mon Aug 7 12:39:19 2023] Code: 00 e9 2b ff ff ff 48 89 df c6 05 ba a6 d5 01 
01 e8 3b 07 f8 ff 44 89 f1 48 89 de 48 c7 c7 f8 25 67 9d 48 89 c2 e8 06 09 29 
ff <0f> 0b e9 1c ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00
  [Mon Aug 7 12:39:19 2023] RSP: 0018:b40c40254e38 EFLAGS: 00010246
  [Mon Aug 7 12:39:19 2023] RAX:  RBX: 997996868000 RCX: 

  [Mon Aug 7 12:39:19 2023] RDX:  RSI:  RDI: 

  [Mon Aug 7 12:39:19 2023] RBP: b40c40254e68 R08:  R09: 

  [Mon Aug 7 12:39:19 2023] R10:  R11:  R12: 
9979968684c8
  [Mon Aug 7 12:39:19 2023] R13: 99799686841c R14:  R15: 

  [Mon Aug 7 12:39:19 2023] FS: () 
GS:997da930() knlGS:
  [Mon Aug 7 12:39:19 2023] CS: 0010 DS:  ES:  CR0: 80050033
  [Mon Aug 7 12:39:19 2023] CR2: 0c4c01aa8000 CR3: 000329810004 CR4: 
003726e0
  [Mon Aug 7 12:39:19 2023] Call Trace:
  [Mon Aug 7 12:39:19 2023] 
  [Mon Aug 7 12:39:19 2023] ? 

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

[Eli]

I have some ~different behavior, but I was still able to achieve bug 1.

Initially I saw some intel_pstate/max_perf_pct getting set to 90, but it
would recover quickly.

long_term_power would fluctuate from very low values all the way up to
the nominal 65. Previously when triggering the bug it would slowly go
mostly down toward 0.125, getting stuck between 0.125 and ~4.0, with the
cpu clocked at 400Mhz.  Now it will go up, seemingly reset up to 65, and
allow the max frequencies.

I was able to get something like bug 1 to happen twice.
long_term_power got stuck at 19.5 (unusual, might have been 18.5 the first time)
long_term_time got stuck at 28.0 (typical, its usually this or 32.0)

This happened when I toggled between one and two pegged cores to keep
the temperature at a maximum. If I killed the stress commands at the
right moment while the fan was spun up, while long_term_power was in the
high teens, if I then waited for the spans to spin down - I would get
into a situation where I could not sustain maximum clocks long enough to
reach temperatures to trigger thermald to poke whatever it is that
resets long_term_power back up to 65.

I was able to do this twice.
On my third attempt I accidentally got a long_term_power value 1f 12.5.  I 
waited for fans to spin down, started stressing again, and it pretty 
immediately dropped to 0.125 with cpu speeds locked to 400Mhz. I also noticed 
at the end that intelpstate/max_perf_pct was at 90.

Finally after resetting the long_power_mode to 65 I noticed that I still
couldn't get the fan up because intelpstate/max_perf_pct 90 results in a
maximum core speed of 4.3Ghz which is too low to trigger thermald.

(Likely irrelevant: even though I see there is that intel wireless
driver deb package (I installed all of the packages) in that 6.2-26
kernel folder you shared with me, my intel wifi card does not work when
booted into it.)

this was with the thermald build in adaptive mode, the full command was:
sudo ./thermald --no-daemon --adaptive --loglevel=debug


** Attachment added: "thermaldLog_Adaptive_202309070444.zip"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026658/+attachment/5698212/+files/thermaldLog_Adaptive_202309070444.zip

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

Title:
  CPU frequency governor broken after upgrading from 22.10 to 23.04,
  stuck at 400Mhz on Alder Lake

Status in linux package in Ubuntu:
  Incomplete
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  I've tried to include as much detail as possible in this bug report, I
  originally assembled it just after the release of ubuntu 23.04.  There
  has been no change since then.

  
  I have had substantial performance problems since updating from ubuntu 22.10 
to 23.04.
  The computer in question is the 17 inch Razer Blade laptop from 2022 with an 
intel i7-12800H.
  Current kernel is 6.2.0-20-generic.  (now I'm on 6.2.0-24-generic and nothing 
has changed.)
  This issue occurs regardless of whether the OpenRazer 
(https://openrazer.github.io/) drivers etc are installed.

  
  Description of problem:
  I have discovered what may be two separate bugs involving low level power 
management details on the cpu, they involve the cpu entering different types of 
throttled states and never recovering. These issues appeared immediately after 
upgrading from ubuntu 22.10.  The computer is a large ~gaming laptop with 
plenty of thermal headroom, cpu temperatures cannot reach concerning values 
except when using stress testing tools.

  (I don't know how to propery untangle these two issues, so I'm posting
  them as one. I apologize for the review complexity this causes, but I
  think posting the information all in one spot is more constructive
  here.)

  
  High level testing notes:
  - This issue occurs with use of both the intel_pstate driver and the cpufreq 
driver. (I don't have the same level of detail for cpufreq, but the issue still 
occurs.)
  - I have additionally tested a handful of intel_pstate parameters (and 
others) via grub kernel command line arguments to no effect. All testing 
reported here was done with:
GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau"
GRUB_CMDLINE_LINUX=""
(loading nouveau caused problems for me on 22.10, I have not bothered 
reinvestigating it on 23.04)
  - There is a firmware update available from the manufacture when I boot into 
Windows, I have not installed it (yet).
  - - Update: I installed it. No change.
  - Changing the cpu governor setting from "powersave" to "performance" using 
`cpupower frequency-set -g performance` has no effect. (Note: this action is 
separate from the intel_pstate's power-saver/balanced/performance setting 
visible with the `powerprofilesctl` utility. It doesn't seem to be a governor 
bug.
  - - (There is a tertiary issue where I also see substantial 

[Kernel-packages] [Bug 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)

[Juerg Haefliger]

Remove 'pcie_aspm=off', that should not be necessary anymore.

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

Title:
  Ethernet not stable 23.04 (RTL8168/8169)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  hello,
  it is my first time reporting a pug hope it is the last

  there is thread here
  https://ubuntuforums.org/showthread.php?t=2489146=14151513

  another user experienced similar issue

  my network work fine at startup keep working for hours then disconnect and 
cannot reconnect without a restart
  I tested the cable using another pc and it was working repluged with no 
difference

  I thought it is caused by nvidia driver so changed it and the problem
  persist

  I use systemd-networkd

  
  uname -a
  Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed 
Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  
  lspci:
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b)

  
  dmesg:

  [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): 
apparmor="ALLOWED" operation="file_perm" class="file" 
profile="libreoffice-oosplash" 
name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" 
pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
  [Mon Aug 7 12:39:19 2023] [ cut here ]
  [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 
timed out
  [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at 
net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250
  [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer 
nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 
snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common 
soundwire_intel soundwire_generic_allocation soundwire_cadence 
snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp 
snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core 
snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel 
snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr 
intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep 
intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 
snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm 
irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec 
polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clm
 ulni_intel rc_core
  [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper 
snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas 
syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd 
sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof 
firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc 
ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 
hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci 
spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus 
xhci_pci_renesas idma64 wmi pinctrl_cannonlake
  [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 
6.2.0-26-generic #26-Ubuntu
  [Mon Aug 7 12:39:19 2023] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 
2.13.1 05/10/2023
  [Mon Aug 7 12:39:19 2023] RIP: 0010:dev_watchdog+0x23a/0x250
  [Mon Aug 7 12:39:19 2023] Code: 00 e9 2b ff ff ff 48 89 df c6 05 ba a6 d5 01 
01 e8 3b 07 f8 ff 44 89 f1 48 89 de 48 c7 c7 f8 25 67 9d 48 89 c2 e8 06 09 29 
ff <0f> 0b e9 1c ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00
  [Mon Aug 7 12:39:19 2023] RSP: 0018:b40c40254e38 EFLAGS: 00010246
  [Mon Aug 7 12:39:19 2023] RAX:  RBX: 997996868000 RCX: 

  [Mon Aug 7 12:39:19 2023] RDX:  RSI:  RDI: 

  [Mon Aug 7 12:39:19 2023] RBP: b40c40254e68 R08:  R09: 

  [Mon Aug 7 12:39:19 2023] R10:  R11:  R12: 
9979968684c8
  [Mon Aug 7 12:39:19 2023] R13: 99799686841c R14:  R15: 

  [Mon Aug 7 12:39:19 2023] FS: () 
GS:997da930() knlGS:
  [Mon Aug 7 12:39:19 2023] CS: 0010 DS:  ES:  CR0: 80050033
  [Mon Aug 7 12:39:19 2023] CR2: 0c4c01aa8000 CR3: 000329810004 CR4: 
003726e0
  [Mon Aug 7 12:39:19 2023] Call Trace:
  [Mon Aug 7 12:39:19 2023] 
  [Mon Aug 7 12:39:19 2023] ? __pfx_dev_watchdog+0x10/0x10
  [Mon Aug 7 12:39:19 2023] call_timer_fn+0x29/0x160
  [Mon Aug 7 12:39:19 2023] ? __pfx_dev_watchdog+0x10/0x10
  [Mon Aug 7 

[Kernel-packages] [Bug 2034686] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

Title:
  intermittent 6.2.0-32 kernel oops on plugging in USB-C dock

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [ 2437.122866] BUG: kernel NULL pointer dereference, address: 
  [ 2437.122874] #PF: supervisor read access in kernel mode
  [ 2437.122879] #PF: error_code(0x) - not-present page
  [ 2437.122882] PGD 0 P4D 0 
  [ 2437.122888] Oops:  [#1] PREEMPT SMP NOPTI
  [ 2437.122893] CPU: 14 PID: 18940 Comm: kworker/u32:6 Not tainted 
6.2.0-32-generic #32-Ubuntu
  [ 2437.122899] Hardware name: HP HP Pavilion Aero Laptop 13-be0xxx/8916, BIOS 
F.12 04/11/2023
  [ 2437.122902] Workqueue: USBC000:00-con1 ucsi_poll_worker [typec_ucsi]
  [ 2437.122918] RIP: 0010:ucsi_acpi_async_write+0x31/0x60 [ucsi_acpi]
  [ 2437.122929] Code: 89 e5 41 56 49 89 ce 41 55 49 89 d5 41 54 53 89 f3 e8 83 
8b fe ff 4c 89 f2 4c 89 ee 89 df 48 03 78 10 49 89 c4 e8 2f 1e 8f ea <49> 8b 45 
00 4c 89 e7 be 01 00 00 00 49 89 44 24 50 e8 c9 fc ff ff
  [ 2437.122933] RSP: 0018:9e7f98e2fd78 EFLAGS: 00010282
  [ 2437.122937] RAX: 9e7f80c8cc86 RBX: 0002 RCX: 

  [ 2437.122940] RDX:  RSI:  RDI: 
9e7f80c8cc86
  [ 2437.122943] RBP: 9e7f98e2fd98 R08:  R09: 

  [ 2437.122945] R10:  R11:  R12: 
8e24d229e4a8
  [ 2437.122947] R13:  R14:  R15: 
8e24d225a7b8
  [ 2437.122949] FS:  () GS:8e27ce98() 
knlGS:
  [ 2437.122953] CS:  0010 DS:  ES:  CR0: 80050033
  [ 2437.122956] CR2:  CR3: 00025361 CR4: 
00750ee0
  [ 2437.122959] PKRU: 5554
  [ 2437.122961] Call Trace:
  [ 2437.122964]  
  [ 2437.122968]  ? show_regs+0x6d/0x80
  [ 2437.122976]  ? __die+0x24/0x80
  [ 2437.122980]  ? page_fault_oops+0x99/0x1b0
  [ 2437.122988]  ? do_user_addr_fault+0x2f3/0x620
  [ 2437.122992]  ? exc_page_fault+0x80/0x1b0
  [ 2437.122999]  ? asm_exc_page_fault+0x27/0x30
  [ 2437.123007]  ? ucsi_acpi_async_write+0x31/0x60 [ucsi_acpi]
  [ 2437.123016]  ? ucsi_acpi_async_write+0x31/0x60 [ucsi_acpi]
  [ 2437.123024]  ucsi_exec_command+0xe2/0x100 [typec_ucsi]
  [ 2437.123034]  ucsi_send_command+0x4b/0xf0 [typec_ucsi]
  [ 2437.123045]  ucsi_get_src_pdos+0x46/0x110 [typec_ucsi]
  [ 2437.123055]  ucsi_poll_worker+0x40/0xf0 [typec_ucsi]
  [ 2437.123064]  process_one_work+0x225/0x430
  [ 2437.123072]  worker_thread+0x50/0x3e0
  [ 2437.123076]  ? __pfx_worker_thread+0x10/0x10
  [ 2437.123081]  kthread+0xe9/0x110
  [ 2437.123087]  ? __pfx_kthread+0x10/0x10
  [ 2437.123093]  ret_from_fork+0x2c/0x50
  [ 2437.123100]  
  [ 2437.123102] Modules linked in: rfcomm snd_seq_dummy snd_hrtimer ccm cmac 
algif_hash algif_skcipher af_alg bnep amdgpu binfmt_misc snd_soc_dmic 
snd_acp3x_rn snd_acp3x_pdm_dma snd_sof_amd_rembrandt snd_ctl_led 
snd_sof_amd_renoir snd_sof_amd_acp snd_hda_codec_realtek rtw89_8852ae 
snd_hda_codec_generic snd_hda_codec_hdmi snd_sof_pci snd_sof_xtensa_dsp 
rtw89_8852a ledtrig_audio uvcvideo intel_rapl_msr snd_sof snd_hda_intel 
snd_usb_audio rtw89_pci snd_sof_utils intel_rapl_common snd_hda_codec 
snd_intel_dspcfg rtw89_core snd_hda_core snd_usbmidi_lib snd_intel_sdw_acpi 
snd_soc_core iommu_v2 snd_hwdep drm_buddy gpu_sched videobuf2_vmalloc 
edac_mce_amd drm_ttm_helper snd_compress videobuf2_memops snd_seq_midi mac80211 
videobuf2_v4l2 ac97_bus kvm_amd snd_pcm_dmaengine videodev ttm 
snd_seq_midi_event kvm btusb snd_pci_ps btrtl snd_rawmidi drm_display_helper 
snd_rpl_pci_acp6x snd_acp_pci btbcm snd_pci_acp6x snd_pcm irqbypass btintel cec 
snd_seq videobuf2_common crct10dif_pclmul hid_cmedia
  [ 2437.123185]  polyval_clmulni snd_pci_acp5x nls_iso8859_1 polyval_generic 
cfg80211 hid_microsoft rc_core ghash_clmulni_intel mc ff_memless snd_seq_device 
btmtk drm_kms_helper snd_timer bluetooth sha512_ssse3 snd_rn_pci_acp3x 
i2c_algo_bit libarc4 snd snd_acp_config syscopyarea aesni_intel ecdh_generic 
hp_wmi crypto_simd snd_soc_acpi sysfillrect cryptd soundcore ecc sysimgblt 
joydev k10temp input_leds snd_pci_acp3x serio_raw rapl sparse_keymap ccp 
platform_profile wmi_bmof hid_multitouch amd_pmc acpi_tad mac_hid msr 
parport_pc ppdev lp parport drm efi_pstore dmi_sysfs ip_tables x_tables autofs4 
r8153_ecm cdc_ether usbnet usbhid r8152 mii uas usb_storage btrfs 
blake2b_generic xor raid6_pq libcrc32c hid_sensor_hub nvme nvme_core ucsi_acpi 
hid_generic typec_ucsi xhci_pci crc32_pclmul amd_sfh typec i2c_piix4 
xhci_pci_renesas nvme_common i2c_hid_acpi video i2c_hid hid wmi
  [ 2437.123277] CR2: 
  [ 2437.123280] ---[ end trace  ]---
  [ 2437.135902] usb 2-1: New USB device 

[Kernel-packages] [Bug 2034686] [NEW] intermittent 6.2.0-32 kernel oops on plugging in USB-C dock

[Chris Bainbridge]

Public bug reported:

[ 2437.122866] BUG: kernel NULL pointer dereference, address: 
[ 2437.122874] #PF: supervisor read access in kernel mode
[ 2437.122879] #PF: error_code(0x) - not-present page
[ 2437.122882] PGD 0 P4D 0 
[ 2437.122888] Oops:  [#1] PREEMPT SMP NOPTI
[ 2437.122893] CPU: 14 PID: 18940 Comm: kworker/u32:6 Not tainted 
6.2.0-32-generic #32-Ubuntu
[ 2437.122899] Hardware name: HP HP Pavilion Aero Laptop 13-be0xxx/8916, BIOS 
F.12 04/11/2023
[ 2437.122902] Workqueue: USBC000:00-con1 ucsi_poll_worker [typec_ucsi]
[ 2437.122918] RIP: 0010:ucsi_acpi_async_write+0x31/0x60 [ucsi_acpi]
[ 2437.122929] Code: 89 e5 41 56 49 89 ce 41 55 49 89 d5 41 54 53 89 f3 e8 83 
8b fe ff 4c 89 f2 4c 89 ee 89 df 48 03 78 10 49 89 c4 e8 2f 1e 8f ea <49> 8b 45 
00 4c 89 e7 be 01 00 00 00 49 89 44 24 50 e8 c9 fc ff ff
[ 2437.122933] RSP: 0018:9e7f98e2fd78 EFLAGS: 00010282
[ 2437.122937] RAX: 9e7f80c8cc86 RBX: 0002 RCX: 
[ 2437.122940] RDX:  RSI:  RDI: 9e7f80c8cc86
[ 2437.122943] RBP: 9e7f98e2fd98 R08:  R09: 
[ 2437.122945] R10:  R11:  R12: 8e24d229e4a8
[ 2437.122947] R13:  R14:  R15: 8e24d225a7b8
[ 2437.122949] FS:  () GS:8e27ce98() 
knlGS:
[ 2437.122953] CS:  0010 DS:  ES:  CR0: 80050033
[ 2437.122956] CR2:  CR3: 00025361 CR4: 00750ee0
[ 2437.122959] PKRU: 5554
[ 2437.122961] Call Trace:
[ 2437.122964]  
[ 2437.122968]  ? show_regs+0x6d/0x80
[ 2437.122976]  ? __die+0x24/0x80
[ 2437.122980]  ? page_fault_oops+0x99/0x1b0
[ 2437.122988]  ? do_user_addr_fault+0x2f3/0x620
[ 2437.122992]  ? exc_page_fault+0x80/0x1b0
[ 2437.122999]  ? asm_exc_page_fault+0x27/0x30
[ 2437.123007]  ? ucsi_acpi_async_write+0x31/0x60 [ucsi_acpi]
[ 2437.123016]  ? ucsi_acpi_async_write+0x31/0x60 [ucsi_acpi]
[ 2437.123024]  ucsi_exec_command+0xe2/0x100 [typec_ucsi]
[ 2437.123034]  ucsi_send_command+0x4b/0xf0 [typec_ucsi]
[ 2437.123045]  ucsi_get_src_pdos+0x46/0x110 [typec_ucsi]
[ 2437.123055]  ucsi_poll_worker+0x40/0xf0 [typec_ucsi]
[ 2437.123064]  process_one_work+0x225/0x430
[ 2437.123072]  worker_thread+0x50/0x3e0
[ 2437.123076]  ? __pfx_worker_thread+0x10/0x10
[ 2437.123081]  kthread+0xe9/0x110
[ 2437.123087]  ? __pfx_kthread+0x10/0x10
[ 2437.123093]  ret_from_fork+0x2c/0x50
[ 2437.123100]  
[ 2437.123102] Modules linked in: rfcomm snd_seq_dummy snd_hrtimer ccm cmac 
algif_hash algif_skcipher af_alg bnep amdgpu binfmt_misc snd_soc_dmic 
snd_acp3x_rn snd_acp3x_pdm_dma snd_sof_amd_rembrandt snd_ctl_led 
snd_sof_amd_renoir snd_sof_amd_acp snd_hda_codec_realtek rtw89_8852ae 
snd_hda_codec_generic snd_hda_codec_hdmi snd_sof_pci snd_sof_xtensa_dsp 
rtw89_8852a ledtrig_audio uvcvideo intel_rapl_msr snd_sof snd_hda_intel 
snd_usb_audio rtw89_pci snd_sof_utils intel_rapl_common snd_hda_codec 
snd_intel_dspcfg rtw89_core snd_hda_core snd_usbmidi_lib snd_intel_sdw_acpi 
snd_soc_core iommu_v2 snd_hwdep drm_buddy gpu_sched videobuf2_vmalloc 
edac_mce_amd drm_ttm_helper snd_compress videobuf2_memops snd_seq_midi mac80211 
videobuf2_v4l2 ac97_bus kvm_amd snd_pcm_dmaengine videodev ttm 
snd_seq_midi_event kvm btusb snd_pci_ps btrtl snd_rawmidi drm_display_helper 
snd_rpl_pci_acp6x snd_acp_pci btbcm snd_pci_acp6x snd_pcm irqbypass btintel cec 
snd_seq videobuf2_common crct10dif_pclmul hid_cmedia
[ 2437.123185]  polyval_clmulni snd_pci_acp5x nls_iso8859_1 polyval_generic 
cfg80211 hid_microsoft rc_core ghash_clmulni_intel mc ff_memless snd_seq_device 
btmtk drm_kms_helper snd_timer bluetooth sha512_ssse3 snd_rn_pci_acp3x 
i2c_algo_bit libarc4 snd snd_acp_config syscopyarea aesni_intel ecdh_generic 
hp_wmi crypto_simd snd_soc_acpi sysfillrect cryptd soundcore ecc sysimgblt 
joydev k10temp input_leds snd_pci_acp3x serio_raw rapl sparse_keymap ccp 
platform_profile wmi_bmof hid_multitouch amd_pmc acpi_tad mac_hid msr 
parport_pc ppdev lp parport drm efi_pstore dmi_sysfs ip_tables x_tables autofs4 
r8153_ecm cdc_ether usbnet usbhid r8152 mii uas usb_storage btrfs 
blake2b_generic xor raid6_pq libcrc32c hid_sensor_hub nvme nvme_core ucsi_acpi 
hid_generic typec_ucsi xhci_pci crc32_pclmul amd_sfh typec i2c_piix4 
xhci_pci_renesas nvme_common i2c_hid_acpi video i2c_hid hid wmi
[ 2437.123277] CR2: 
[ 2437.123280] ---[ end trace  ]---
[ 2437.135902] usb 2-1: New USB device found, idVendor=03f0, idProduct=066b, 
bcdDevice= 6.11
[ 2437.135907] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2437.135910] usb 2-1: Product: HP USB-C Dock G5
[ 2437.135913] usb 2-1: Manufacturer: Microchip
[ 2437.161655] hub 2-1:1.0: USB hub found
[ 2437.161680] hub 2-1:1.0: 4 ports detected
[ 2437.225016] usb 1-1.2: new high-speed USB device number 115 using xhci_hcd
[ 2437.329245] RIP: 0010:ucsi_acpi_async_write+0x31/0x60 [ucsi_acpi]
[ 

[Kernel-packages] [Bug 2034504] Re: Enable ASPM for NVMe behind VMD

[Kai-Chuan Hsieh]

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

** Tags added: originate-from-2032928

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

Title:
  Enable ASPM for NVMe behind VMD

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  New
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux-oem-6.5 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Confirmed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  ASPM of NVMe behind VMD is not enabled when BIOS FADT doesn't allow ASPM to 
be modified.
  That causes higher overall power consumption.

  [Fix]
  Allow ASPM to be enabled.
  While at this, remove old cruft that can interfere upstream VMD driver.

  [Test]
  Check the value of `/sys/kernel/debug/pmc_core/slp_s0_residency_usec`. Now 
system can reach deepest power saving state during sleep.

  [Where problems could occur]
  Some NVMe may have I/O issue when ASPM is enabled. But for this scenario the 
issue will also appear when VMD is disabled.

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


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

[Kernel-packages] [Bug 2033025] Re: Fix numerous AER related issues

[Kai-Chuan Hsieh]

** Tags added: originate-from-202

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

Title:
  Fix numerous AER related issues

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  Numerous issues triggered from AER/DPC services
  - When AER is shared with PME, cutting the power off the device can trigger 
AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, 
preventing the system from entering sleep.

  - When system resume from S3, device can reset itself and start
  sending PTM messages, triggering AER and reset the entire hierarchy.
  Since the hardware/firmware starts before software, it's never soon
  enough to put a band-aid from kernel.

  - Following above one, device firmware restarts before kernel resume,
  when DPC is triggered then the device is gone without any recovering
  method. We really want to prevent that from happening.

  [Fix]
  Disable and re-enable AER and DPC services on suspend and resume, 
respectively.
  Right now the the PCI mailing list doesn't have a consensus which PCI state 
(D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate 
the old workaround for now.

  [Test]
  One the workaround is applied, symptoms described above can no longer be 
observed.

  [Where problems could occur]
  Theoretically there can be some "real" issues get unnoticed once AER gets 
temporarily disabled, but the benefit far outweighs the downside.

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


-- 
Mailing list: https://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 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

[koba]

@Eli,
could you run this scripts and upload the log? thanks
~~~
// could find this repor, https://github.com/intel/thermal_daemon
thermal_daemon/test/thermal-debug-dump-ubuntu.sh
~~~

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

Title:
  CPU frequency governor broken after upgrading from 22.10 to 23.04,
  stuck at 400Mhz on Alder Lake

Status in linux package in Ubuntu:
  Incomplete
Status in thermald package in Ubuntu:
  In Progress

Bug description:
  I've tried to include as much detail as possible in this bug report, I
  originally assembled it just after the release of ubuntu 23.04.  There
  has been no change since then.

  
  I have had substantial performance problems since updating from ubuntu 22.10 
to 23.04.
  The computer in question is the 17 inch Razer Blade laptop from 2022 with an 
intel i7-12800H.
  Current kernel is 6.2.0-20-generic.  (now I'm on 6.2.0-24-generic and nothing 
has changed.)
  This issue occurs regardless of whether the OpenRazer 
(https://openrazer.github.io/) drivers etc are installed.

  
  Description of problem:
  I have discovered what may be two separate bugs involving low level power 
management details on the cpu, they involve the cpu entering different types of 
throttled states and never recovering. These issues appeared immediately after 
upgrading from ubuntu 22.10.  The computer is a large ~gaming laptop with 
plenty of thermal headroom, cpu temperatures cannot reach concerning values 
except when using stress testing tools.

  (I don't know how to propery untangle these two issues, so I'm posting
  them as one. I apologize for the review complexity this causes, but I
  think posting the information all in one spot is more constructive
  here.)

  
  High level testing notes:
  - This issue occurs with use of both the intel_pstate driver and the cpufreq 
driver. (I don't have the same level of detail for cpufreq, but the issue still 
occurs.)
  - I have additionally tested a handful of intel_pstate parameters (and 
others) via grub kernel command line arguments to no effect. All testing 
reported here was done with:
GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau"
GRUB_CMDLINE_LINUX=""
(loading nouveau caused problems for me on 22.10, I have not bothered 
reinvestigating it on 23.04)
  - There is a firmware update available from the manufacture when I boot into 
Windows, I have not installed it (yet).
  - - Update: I installed it. No change.
  - Changing the cpu governor setting from "powersave" to "performance" using 
`cpupower frequency-set -g performance` has no effect. (Note: this action is 
separate from the intel_pstate's power-saver/balanced/performance setting 
visible with the `powerprofilesctl` utility. It doesn't seem to be a governor 
bug.
  - - (There is a tertiary issue where I also see substantial (+50%) 
performance degredation using the "performance" profile in a test suite I run 
constantly for my job; that is clearly a problem but it is an unrelated bug 
that has existed for quite some time.)

  
  Summary and my own conclusions:
  These are my takeaways, the ~raw data is in the followup section.

  
  Bug 1)
  The reported cpu power limits are progressively constrained over time. Once 
this failure mode starts the performance never recovers.
- As this situation progresses the observed cpu speeds (I'm using htop) 
list as 2800Mhz at idle, but the instant any load at all is placed on a cpu 
core that core immediately drops to exactly 400Mhz.
- This situation occurs quite quickly in human terms, frequently within 20 
minutes of normal usage after a boot, but it will also occur when the computer 
is just sitting there unused for a handful of hours.
- This occurs when using the cpufreq gevernor (by including 
"intel_pstate=disable" on the grub command line args.)
- At boot the default value for short_term_time looks wrong to me. This is 
the duration of higher thermal targets in seconds, ~0.002 seconds seems 
extremely short. A normal value would be a handful of seconds.
- This situation can be remedied by running the following python script. It 
uses the undervolt package (pip install undervolt==0.3.0) to force particular 
power limits (the provided values are intentional overkill):
   1   │ from undervolt import read_power_limit, set_power_limit, 
PowerLimit, ADDRESSES
   2   │ from pprint import pprint
   3   │ 
   4   │ limits = read_power_limit(ADDRESSES)
   5   │ pprint(vars(limits))  # print current values before setting them
   6   │ 
   7   │ POWER_LIMITS = PowerLimit()
   8   │ POWER_LIMITS.locked = True  # lock means don't allow the value to 
be reset until a reboot.
   9   │ POWER_LIMITS.backup_rest = 281474976776192  # afaik this is just a 
backup-on-failure setting, it has no effect here.
  10   │ POWER_LIMITS.long_term_enabled = 

[Kernel-packages] [Bug 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)

[ahmed hanafi al-sayed]

thanks @Juery,

I am on the test kernel now with pcie_aspm=off for 19 hours : 15 mins
hope the network never let me down again I will modify this comment if
any change happened

uname -a
Linux OptiPlex-3090 6.2.0-32-generic #32+lp2031537 SMP PREEMPT_DYNAMIC Tue Sep  
5 07:27:25 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

sudo dmesg
[sudo] password for : 
[0.00] Linux version 6.2.0-32-generic (ubuntu@ip-10-0-61-144) 
(x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~23.04) 12.3.0, GNU ld (GNU 
Binutils for Ubuntu) 2.40) #32+lp2031537 SMP PREEMPT_DYNAMIC Tue Sep  5 
07:27:25 UTC 2023 (Ubuntu 6.2.0-32.32+lp2031537-generic 6.2.16)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic 
root=UUID=bad00fc3-af76-403c-a8f8-e4b840d16e23 ro quiet splash pcie_aspm=off 
vt.handoff=7

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

Title:
  Ethernet not stable 23.04 (RTL8168/8169)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  hello,
  it is my first time reporting a pug hope it is the last

  there is thread here
  https://ubuntuforums.org/showthread.php?t=2489146=14151513

  another user experienced similar issue

  my network work fine at startup keep working for hours then disconnect and 
cannot reconnect without a restart
  I tested the cable using another pc and it was working repluged with no 
difference

  I thought it is caused by nvidia driver so changed it and the problem
  persist

  I use systemd-networkd

  
  uname -a
  Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed 
Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  
  lspci:
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b)

  
  dmesg:

  [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): 
apparmor="ALLOWED" operation="file_perm" class="file" 
profile="libreoffice-oosplash" 
name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" 
pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
  [Mon Aug 7 12:39:19 2023] [ cut here ]
  [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 
timed out
  [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at 
net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250
  [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer 
nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 
snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common 
soundwire_intel soundwire_generic_allocation soundwire_cadence 
snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp 
snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core 
snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel 
snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr 
intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep 
intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 
snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm 
irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec 
polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clm
 ulni_intel rc_core
  [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper 
snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas 
syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd 
sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof 
firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc 
ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 
hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci 
spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus 
xhci_pci_renesas idma64 wmi pinctrl_cannonlake
  [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 
6.2.0-26-generic #26-Ubuntu
  [Mon Aug 7 12:39:19 2023] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 
2.13.1 05/10/2023
  [Mon Aug 7 12:39:19 2023] RIP: 0010:dev_watchdog+0x23a/0x250
  [Mon Aug 7 12:39:19 2023] Code: 00 e9 2b ff ff ff 48 89 df c6 05 ba a6 d5 01 
01 e8 3b 07 f8 ff 44 89 f1 48 89 de 48 c7 c7 f8 25 67 9d 48 89 c2 e8 06 09 29 
ff <0f> 0b e9 1c ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00
  [Mon Aug 7 12:39:19 2023] RSP: 0018:b40c40254e38 EFLAGS: 00010246
  [Mon Aug 7 12:39:19 2023] RAX:  RBX: 997996868000 RCX: 

  [Mon Aug 7 12:39:19 2023] RDX:  RSI:  RDI: 

  [Mon Aug 7 12:39:19 2023] RBP: b40c40254e68 R08:  

[Kernel-packages] [Bug 2032176] Re: Crashing with CPU soft lock on GA kernel 5.15.0.79.76 and HWE kernel 5.19.0-46.47-22.04.1

[Andrew Liaw]

Currently, testing out the linux/5.15.0-85.95 version of kernel.

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

Title:
  Crashing with CPU soft lock on GA kernel 5.15.0.79.76 and HWE kernel
  5.19.0-46.47-22.04.1

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

Bug description:
  Impact:
  We had reports of VM setups which would show intermediate crashes and after 
that locking up completely. This could be reproduced with large memory setups.
  The problem seems to be that fixes to performance regressions caused more 
problems in 5.15 kernels and the full fixes are too intrusive to be backported.

  Fix:
  The following patch was recently sent to the upstream stable mailing list and 
looks to be making its way into linux-5.15.y. This changes the default value of 
kvm.tdp_mmu to off (if anyone is willing to take the risks, this can be changed 
back in config).

  Regression potential:
  VM hosts with many large memory tennants might see a performance impact which 
the TDP MMU approach tried to solve. If those did not see other problems they 
might turn this on again.

  Testcase:
  Large openstack instance (64GB memory, AMD CPU (using SVM)) with a large 
second level guest (32GB memory). Repeatedly starting and stopping the 2nd 
level guest.

  
  --- original description ---
  The crash occurred on a juju machine, and the juju agent was lost.
  The juju machine is on an openstack instance provision by juju.

  The openstack console log indicts the it is related to spin_lock and KVM MMU:
  [418200.348830]  ? _raw_spin_lock+0x22/0x30
  [418200.349588]  _raw_write_lock+0x20/0x30
  [418200.350196]  kvm_tdp_mmu_map+0x2b1/0x490 [kvm]
  [418200.351014]  kvm_mmu_notifier_invalidate_range_start+0x1ad/0x300 [kvm]
  [418200.351796]  direct_page_fault+0x206/0x310 [kvm]
  [418200.352667]  __mmu_notifier_invalidate_range_start+0x91/0x1b0
  [418200.353624]  kvm_tdp_page_fault+0x72/0x90 [kvm]
  [418200.354496]  try_to_migrate_one+0x691/0x730
  [418200.355436]  kvm_mmu_page_fault+0x73/0x1c0 [kvm]

  openstack console log: https://pastebin.canonical.com/p/spmH8r3crQ/

  syslog: https://pastebin.canonical.com/p/wFPsFD8G9n/
  The syslog was rotated after the crash occurred, so the syslog at the time of 
the initial crash was lost.

  Other juju machine with 5.15.0.79.76 kernel seems to have the same
  issues.

  We previously have a similar issue with 5.15.0-73. The juju machine
  crashed with raw_spin_lock and kvm mmu in the logs as well:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026229

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: openstack
  CloudName: openstack
  CloudPlatform: openstack
  CloudSubPlatform: metadata (http://169.254.169.254)
  Date: Mon Aug 21 08:59:46 2023
  Ec2AMI: ami-0c61
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: availability-zone-1
  Ec2InstanceType: builder-cpu4-ram72-disk20
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.19
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 23 03:23 seq
   crw-rw 1 root audio 116, 33 Aug 23 03:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: openstack
  CloudName: openstack
  CloudPlatform: openstack
  CloudSubPlatform: metadata (http://169.254.169.254)
  DistroRelease: Ubuntu 22.04
  Ec2AMI: ami-0fbb
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: availability-zone-2
  Ec2InstanceType: builder-cpu2-ram44-disk20
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
  MachineType: OpenStack Foundation OpenStack Nova
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   

[Kernel-packages] [Bug 2033455] Re: Missing BT IDs for support for Intel Discrete Misty Peak2/BE202

[Juerg Haefliger]

** Tags added: kern-7929

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

Title:
  Missing BT IDs for support for Intel Discrete Misty Peak2/BE202

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-firmware source package in Jammy:
  Incomplete
Status in linux-oem-6.5 source package in Jammy:
  In Progress
Status in linux source package in Mantic:
  In Progress
Status in linux-firmware source package in Mantic:
  Incomplete
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [SRU Justification]

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

  [Impact]

  Missing BT IDs for support for Intel Discrete Misty Peak2/BE202.

  [Fix]

  Bluetooth:
  a. kernel driver:
 - 
https://lore.kernel.org/linux-bluetooth/20230829124024.40592-1-vijay.sat...@intel.com/T/#t
 - Also depends on patches for Gale Peak(BE200) from bug 2028065.
  b. firmware (shared with Gale Peak, to be released):
 - intel/ibt-0191-0191.sfi
 - intel/ibt-0191-0191.ddc

  [Test Case]

  To boot with patched kernel and prereleased firmware blob and check
  basic Bluetooth functions.

  [Where problems could occur]

  New device. Expect incomplete functions and bugs.

  [Other Info]

  Targets 6.5 kernels, so only nominated for Mantic and oem-6.5.

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


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

[Kernel-packages] [Bug 2033007] Re: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64

[Chengen Du]

The kernels (5.15.0-85.95/6.2.0-34.34) have been tested without any
issues.

** Tags removed: verification-needed-jammy-linux verification-needed-lunar-linux
** Tags added: verification-done-jammy-linux verification-done-lunar-linux

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

Title:
  kdump doesn't work with UEFI secure boot and kernel lockdown enabled
  on ARM64

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed

Bug description:
  [Impact]
  The kdump service operates by utilizing the kexec_file_load system call, 
which loads a new kernel image intended for subsequent execution.
  However, this process encounters a hindrance if the 
CONFIG_KEXEC_IMAGE_VERIFY_SIG option isn't enabled to facilitate signature 
verification.

  In addition, a noteworthy point is that if the kernel image is signed with a 
MOK,
  it will face rejection due to ARM64's reliance solely on the 
.builtin_trusted_keys for verification purposes.
  To enhance flexibility, it's suggested that we align the behavior on x86 
platforms.
  This alignment could potentially involve expanding the scope to encompass 
more keyrings, such as .secondary_trusted_keys and platform keyrings,
  thereby broadening the options available for verification mechanisms.

  [Fix]
  Enabling the CONFIG_KEXEC_IMAGE_VERIFY_SIG option is necessary,
  along with the incorporation of two specific commits, in order to enhance the 
capabilities of the kexec_file_load system call on ARM64.
  The commits that need to be applied are as follows:
  c903dae8941d kexec, KEYS: make the code in bzImage64_verify_sig generic
  0d519cadf751 arm64: kexec_file: use more system keyrings to verify kernel 
image signature

  [Test Plan]
  1. Set up a VM with UEFI secure boot and enabled kernel lockdown on ARM64
  2. Install 'kdump-tools'
  sudo apt install linux-crashdump
  3. Reboot and verify kdump status with 'kdump-config show'
  root@ubuntu:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0xde00
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-78-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-5.15.0-78-generic
  current state:Not ready to kdump

  kexec command:
/sbin/kexec -p -s 
--command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-79-generic 
root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  4. Check the log using 'systemctl status kdump-tools'
  Aug 24 06:08:39 ubuntu systemd[1]: Starting Kernel crash dump capture 
service...
  Aug 24 06:08:39 ubuntu kdump-tools[1750]: Starting kdump-tools:
  Aug 24 06:08:39 ubuntu kdump-tools[1755]:  * Creating symlink 
/var/lib/kdump/vmlinuz
  Aug 24 06:08:39 ubuntu kdump-tools[1755]:  * Creating symlink 
/var/lib/kdump/initrd.img
  Aug 24 06:08:39 ubuntu kdump-tools[1755]:  * /sbin/kexec -p -s 
--command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-78-generic 
root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  Aug 24 06:08:41 ubuntu kernel: [  403.301008] Lockdown: kexec: kexec of 
unsigned images is restricted; see man kernel_lockdown.7
  Aug 24 06:08:41 ubuntu kdump-tools[1755]:  * failed to load kdump kernel
  Aug 24 06:08:41 ubuntu kdump-tools: failed to load kdump kernel
  Aug 24 06:08:41 ubuntu systemd[1]: Finished Kernel crash dump capture service.

  [Where problems could occur]
  The problem is specific to kexec image signature verification on ARM64.
  This change allows additional keyrings and impacts only the ARM64 
kexec_file_load system call.

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


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

[Kernel-packages] [Bug 2031537] Re: Ethernet not stable 23.04 (RTL8168/8169)

[Juerg Haefliger]

That looks good. Reboot and select the kernel in grub and then check
with 'uname -a'. Don't forget to disable SecureBoot first (in the BIOS).

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

Title:
  Ethernet not stable 23.04 (RTL8168/8169)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  hello,
  it is my first time reporting a pug hope it is the last

  there is thread here
  https://ubuntuforums.org/showthread.php?t=2489146=14151513

  another user experienced similar issue

  my network work fine at startup keep working for hours then disconnect and 
cannot reconnect without a restart
  I tested the cable using another pc and it was working repluged with no 
difference

  I thought it is caused by nvidia driver so changed it and the problem
  persist

  I use systemd-networkd

  
  uname -a
  Linux ahmed-OptiPlex-3090 6.2.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Wed 
Jul 12 22:39:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  
  lspci:
  02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 1b)

  
  dmesg:

  [Mon Aug 7 12:36:47 2023] audit: type=1400 audit(1691401007.881:150): 
apparmor="ALLOWED" operation="file_perm" class="file" 
profile="libreoffice-oosplash" 
name="/tmp/OSL_PIPE_1000_SingleOfficeIPC_74ed987bff2950ad36ea f76d6640d9dc" 
pid=14414 comm="oosplash" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
  [Mon Aug 7 12:39:19 2023] [ cut here ]
  [Mon Aug 7 12:39:19 2023] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 
timed out
  [Mon Aug 7 12:39:19 2023] WARNING: CPU: 4 PID: 0 at 
net/sched/sch_generic.c:525 dev_watchdog+0x23a/0x250
  [Mon Aug 7 12:39:19 2023] Modules linked in: snd_seq_dummy snd_hrtimer 
nvidia_uvm(PO) bridge stp llc cfg80211 binfmt_misc nvidia_drm(PO) nls_iso8859_1 
snd_ctl_led nvidia_modeset(PO) snd_sof_pci_intel_cnl snd_sof_intel_hda_common 
soundwire_intel soundwire_generic_allocation soundwire_cadence 
snd_sof_intel_hda snd_sof_pci snd_hda_codec_realtek snd_sof_xtensa_dsp 
snd_hda_codec_generic snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core 
snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel 
snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_rapl_msr 
intel_rapl_common snd_hda_core intel_tcc_cooling x86_pkg_temp_thermal snd_hwdep 
intel_powerclamp coretemp nvidia(PO) snd_pcm kvm_intel snd_seq_midi i915 
snd_seq_midi_event mei_hdcp mei_pxp snd_rawmidi kvm drm_buddy snd_seq ttm 
irqbypass drm_display_helper snd_seq_device crct10dif_pclmul cec 
polyval_clmulni snd_timer polyval_generic dell_wmi ghash_clm
 ulni_intel rc_core
  [Mon Aug 7 12:39:19 2023] sha512_ssse3 cmdlinepart aesni_intel drm_kms_helper 
snd mei_me spi_nor crypto_simd i2c_algo_bit dell_smbios cryptd soundcore dcdbas 
syscopyarea sysfillrect ledtrig_audio dell_wmi_sysman sysimgblt mei rapl mtd 
sparse_keymap dell_wmi_descriptor intel_pch_thermal intel_cstate wmi_bmof 
firmware_attributes_class ee1004 input_leds acpi_pad mac_hid msr parport_pc 
ppdev lp drm parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 
hid_generic usbhid hid ahci crc32_pclmul r8169 video intel_lpss_pci 
spi_intel_pci i2c_i801 libahci xhci_pci spi_intel intel_lpss realtek i2c_smbus 
xhci_pci_renesas idma64 wmi pinctrl_cannonlake
  [Mon Aug 7 12:39:19 2023] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P O 
6.2.0-26-generic #26-Ubuntu
  [Mon Aug 7 12:39:19 2023] Hardware name: Dell Inc. OptiPlex 3090/0492YX, BIOS 
2.13.1 05/10/2023
  [Mon Aug 7 12:39:19 2023] RIP: 0010:dev_watchdog+0x23a/0x250
  [Mon Aug 7 12:39:19 2023] Code: 00 e9 2b ff ff ff 48 89 df c6 05 ba a6 d5 01 
01 e8 3b 07 f8 ff 44 89 f1 48 89 de 48 c7 c7 f8 25 67 9d 48 89 c2 e8 06 09 29 
ff <0f> 0b e9 1c ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00
  [Mon Aug 7 12:39:19 2023] RSP: 0018:b40c40254e38 EFLAGS: 00010246
  [Mon Aug 7 12:39:19 2023] RAX:  RBX: 997996868000 RCX: 

  [Mon Aug 7 12:39:19 2023] RDX:  RSI:  RDI: 

  [Mon Aug 7 12:39:19 2023] RBP: b40c40254e68 R08:  R09: 

  [Mon Aug 7 12:39:19 2023] R10:  R11:  R12: 
9979968684c8
  [Mon Aug 7 12:39:19 2023] R13: 99799686841c R14:  R15: 

  [Mon Aug 7 12:39:19 2023] FS: () 
GS:997da930() knlGS:
  [Mon Aug 7 12:39:19 2023] CS: 0010 DS:  ES:  CR0: 80050033
  [Mon Aug 7 12:39:19 2023] CR2: 0c4c01aa8000 CR3: 000329810004 CR4: 
003726e0
  [Mon Aug 7 12:39:19 2023] Call Trace:
  [Mon Aug 7 12:39:19 2023] 
  [Mon Aug 7 12:39:19 2023] ? __pfx_dev_watchdog+0x10/0x10
  [Mon Aug 7 12:39:19 2023] 

[Kernel-packages] [Bug 2031352] Re: Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot screen

[Juerg Haefliger]

@cfgnunes This bug report is exclusively about the nouveau driver crash.
Yours is a different issue. See bug 2031969.

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

Title:
  Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot
  screen

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-6.2 package in Ubuntu:
  Confirmed
Status in linux-hwe-6.2 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed

Bug description:
  [Impact]

  After updating to Kernel 6.2 a few days ago, I have been experiencing
  issues with my system's shutdown and reboot functions. During these
  processes, the system becomes unresponsive and hangs on a black
  screen, which displays both the Dell and Ubuntu logos. This issue is
  inconsistent; it happens sporadically. Currently, the only workaround
  I've found to successfully shut down the system is to forcibly power
  off the machine by holding down the power button for 5 seconds.

  I've also tested a fresh installation of Ubuntu 22.04.3.

  [Fix]

  Updated patch from linux-next:
  https://patchwork.freedesktop.org/patch/538562/

  [Test Case]

  Suspend,resume,shutdown,reboot should all work correctly. No nouveau
  stack trace in the kernel log.

  [Where Problems Could Occur]

  Limited to nouveau driver that wants to load nonexistent ACR firmware.
  Only nvidia GPUs are affected.

  [Additional information]

  

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd 249.11-0ubuntu3.9
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 14 22:41:14 2023
  InstallationDate: Installed on 2023-08-14 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813)
  MachineType: Dell Inc. XPS 8930
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2023
  dmi.bios.release: 1.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.30
  dmi.board.name: 0T88YD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.sku: 0859
  dmi.product.version: 1.1.30
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-08-13T20:57:27
  mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27

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


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

[Kernel-packages] [Bug 2033025] Re: Fix numerous AER related issues

[Kai-Heng Feng]

** Tags removed: verification-needed-jammy-linux-oem-6.5 
verification-needed-lunar-linux verification-needed-mantic-linux
** Tags added: verification-done-jammy-linux-oem-6.5 
verification-done-lunar-linux verification-done-mantic-linux

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

Title:
  Fix numerous AER related issues

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  Numerous issues triggered from AER/DPC services
  - When AER is shared with PME, cutting the power off the device can trigger 
AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, 
preventing the system from entering sleep.

  - When system resume from S3, device can reset itself and start
  sending PTM messages, triggering AER and reset the entire hierarchy.
  Since the hardware/firmware starts before software, it's never soon
  enough to put a band-aid from kernel.

  - Following above one, device firmware restarts before kernel resume,
  when DPC is triggered then the device is gone without any recovering
  method. We really want to prevent that from happening.

  [Fix]
  Disable and re-enable AER and DPC services on suspend and resume, 
respectively.
  Right now the the PCI mailing list doesn't have a consensus which PCI state 
(D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate 
the old workaround for now.

  [Test]
  One the workaround is applied, symptoms described above can no longer be 
observed.

  [Where problems could occur]
  Theoretically there can be some "real" issues get unnoticed once AER gets 
temporarily disabled, but the benefit far outweighs the downside.

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


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