[Kernel-packages] [Bug 1990697] Re: Crash on resume from sleep - 22.04, Thinkpad T14 (AMD) Gen 2

[Kai-Heng Feng]

Is there any log under /var/lib/systemd/pstore?

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

Title:
  Crash on resume from sleep - 22.04, Thinkpad T14 (AMD) Gen 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm seeing this 2-3 times per week.  My system is configured with
  "Linux Suspend" in the BIOS (not the Windows/Modern setting).
  Furthermore, when plugged in, my system does not sleep.

  When I come up to my laptop after inactivity, the screens are dark
  (but as noted above, it is not suspended).  If I click on a key and
  wait for both external monitors to light up, I can generally hit enter
  at that point, type my password and get in.

  If, however, I'm in a hurry or not thinking about it and just walk up
  to the machine, hit enter, type my password and hit enter a second
  time, I can generally reproduce the problem.  The screen either goes
  to a backlit entirely black view, or (more commonly) a light grey (not
  the same color of grey as the Ubuntu login screen, much more white in
  the crashed state).

  The system is completely unresponsive and cannot be pinged or ssh'ed
  into from the outside.  The only cure is to long-press the power
  button until it powers down, wait a moment and press it again to
  restart.

  Upon suggestions from the #Ubuntu mattermost channel, I ran:

  # journalctl -xe -b -1

  That generated the following data:

  Sep 23 11:35:35 T14 kernel: RIP: 0010:update_config+0x11b/0x280 [amdgpu]
  Sep 23 11:35:35 T14 kernel: Code: 13 0f 00 00 41 0f b6 44 24 03 88 83 1e 0f 
00 >
  Sep 23 11:35:35 T14 kernel: RSP: 0018:9b4743bab618 EFLAGS: 00010202
  Sep 23 11:35:35 T14 kernel: RAX:  RBX: 8a578653cf88 RCX: 
ff>
  Sep 23 11:35:35 T14 kernel: RDX: 8a578653dea0 RSI: 9b4743bab668 RDI: 
ff>
  Sep 23 11:35:35 T14 kernel: RBP: 9b4743bab658 R08:  R09: 
00>
  Sep 23 11:35:35 T14 kernel: R10: 5649 R11: 0010 R12: 
ff>
  Sep 23 11:35:35 T14 kernel: R13: 8a57a5eda000 R14: 0001 R15: 
ff>
  Sep 23 11:35:35 T14 kernel: FS:  7fb5f59a35c0() 
GS:8a5e4f04(000>
  Sep 23 11:35:35 T14 kernel: CS:  0010 DS:  ES:  CR0: 80050033
  Sep 23 11:35:35 T14 kernel: CR2:  CR3: 0001704d6000 CR4: 
00>
  Sep 23 11:35:35 T14 kernel: PKRU: 5554
  Sep 23 11:35:38 T14 kernel: input: PLT V5200 Series (AVRCP) as 
/devices/virtual>
  Sep 23 11:35:38 T14 pulseaudio[3488]: Battery Level: 90%
  Sep 23 11:35:38 T14 pulseaudio[3488]: Dock Status: undocked
  Sep 23 11:35:38 T14 systemd-logind[1832]: Watching system buttons on 
/dev/input>
  Sep 23 11:35:39 T14 bluetoothd[1809]: 
/org/bluez/hci0/dev_BC_F2_92_A0_AC_33/sep>
  Sep 23 11:35:39 T14 rtkit-daemon[2111]: Supervising 9 threads of 4 processes 
of>
  Sep 23 11:35:39 T14 rtkit-daemon[2111]: Successfully made thread 41544 of 
proce>
  Sep 23 11:35:39 T14 rtkit-daemon[2111]: Supervising 10 threads of 4 processes 
o>
  Sep 23 11:35:39 T14 pulseaudio[3488]: org.freedesktop.DBus.Properties.Get 
/org/>
  Sep 23 11:35:41 T14 audit[4797]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 
subj>
  Sep 23 11:35:41 T14 kernel: audit: type=1326 audit(1663947341.195:578): 
auid=10>
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  bceverly   2902 F pulseaudio
   /dev/snd/controlC1:  bceverly   2902 F pulseaudio
   /dev/snd/controlC2:  bceverly   2902 F pulseaudio
   /dev/snd/controlC0:  bceverly   2902 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-30 (116 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 20XK0015US
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic 
root=UUID=162f2be8-a3c8-4554-a76a-2cbb2ce3e446 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-48-generic N/A
   linux-backports-modules-5.15.0-48-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  Tags:  jammy
  Uname: Linux 5.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 06/27/2022
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET49W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 

[Kernel-packages] [Bug 1983656] Re: iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500

[Matthew Ruffell]

** Tags added: focal jammy kinetic

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

Title:
  iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  In Progress

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

  [Impact]

  Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b]
  get no traffic flow and produce error messages in both the host and
  guest during network configuration.

  Environment: Ubuntu OpenStack Focal-Ussuri with OVN
  Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE
  Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy

  Host Error Messages:
  ice :98:00.1: VF 7 failed opcode 6, retval: -5

  Guest Error Messages:
  iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6

  In the context of these errors "6" refers to the value of
  VIRTCHNL_OP_CONFIG_VSI_QUEUES

  It was found in these cases that the VM is able to successfully
  transmit packets but never receives any and the RX packet drop
  counters for the VF in "ip link" on the host increase equal to the RX
  packet count.

  There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d
  claiming to resolve this error in some cases. It is already included
  in 5.15.0-41-generic and did not resolve the issue.

  The following conditions are required to trigger the bug:
  - A port VLAN must be assigned by the host
  - The MTU must be set >1500 by the guest

  There is no workaround, Intel E810 SR-IOV VFs with MTU >1500 cannot be
  used without these patches.

  [Fix]

  iavf currently sets the maximum packet size to IAVF_MAX_RXBUFFER, but
  on the previous ice driver, it was decremented by VLAN_HLEN to make
  some space to fit the VLAN header. This doesn't happen on iavf, and we
  end up trying to use a packet size larger than IAVF_MAX_RXBUFFER,
  causing the IAVF_ERR_PARAM error.

  The fix is to change the maximum packet size from IAVF_MAX_RXBUFFER to
  max_mtu received from the PF via GET_VF_RESOURCES msg.

  Also pick up a necessary commit for i40e to announce the correct
  maximum packet size by GET_VF_RESOURCES msg.

  This has been fixed by the following commits:

  commit 399c98c4dc50b7eb7e9f24da7ffdda6f025676ef
  Author: Michal Jaron 
  Date:   Tue Sep 13 15:38:35 2022 +0200
  Subject: iavf: Fix set max MTU size with port VLAN and jumbo frames
  Link: 
https://github.com/torvalds/linux/commit/399c98c4dc50b7eb7e9f24da7ffdda6f025676ef

  commit 372539def2824c43b6afe2403045b140f65c5acc
  Author: Michal Jaron 
  Date:   Tue Sep 13 15:38:36 2022 +0200
  Subject: i40e: Fix VF set max MTU size
  Link: 
https://github.com/torvalds/linux/commit/372539def2824c43b6afe2403045b140f65c5acc

  A test kernel is available in the following ppa:

  https://launchpad.net/~arif-ali/+archive/ubuntu/sf00343742

  If you install the test kernel to a compute host and VM, when you
  attach a VF and set the MTU to 9000, it succeeds, and traffic can
  flow.

  [Test Plan]

  Create a Focal VM and assign an Intel E810 (ice) SR-IOV VF with a port
  vlan:

  Openstack works, as does creating a VM directly with uvtool/libvirt.

  $ uvt-kvm create focal-test release=focal

  Using the document to understand SRIOV basics in the link below

  
https://www.intel.com/content/www/us/en/developer/articles/technical/configure-
  sr-iov-network-virtual-functions-in-linux-kvm.html

  The following command show all the bus info for all the network
  devices

  $ lshw -c network -businfo

  Choose one, as shown below

  pci@:17:01.4  ens2f0v4 networkEthernet Adaptive
  Virtual Function

  We can then add the following into the XML definition via “virsh edit
  focal-test”

  
    
  
    
   
  
    
  

  Then we stop and start the VM via "virsh shutdown focal-test" and then
  "virsh start focal-test". We can then login to the VM using the
  command below

  $ uvt-kvm ssh focal-test

  Once you have logged in, run the following ip parameters

  $ sudo ip a a 192.168.1.7/24 dev enp7s0
  $ sudo ip link set up dev enp7s0
  $ sudo ip link set mtu 9000 dev enp7s0

  Now check dmesg, and we will find the error

  [   61.529605] iavf :07:00.0: PF returned error -5
  (IAVF_ERR_PARAM) to our request 6

  Setting the IP and bringing the link up

  [   36.228877] iavf :07:00.0 enp7s0: NIC Link is Up Speed is 25 Gbps Full 
Duplex
  [   36.228887] IPv6: ADDRCONF(NETDEV_CHANGE): enp7s0: link becomes ready
  [   45.740100] crng init done
  [   45.740102] random: 7 urandom warning(s) missed due to ratelimiting

  Then setting the MTU

  [   61.433706] iavf :07:00.0: Received 16 queues, but can only have a max 
of 4
  [   

[Kernel-packages] [Bug 1983656] Re: iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500

[Matthew Ruffell]

** Summary changed:

- SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)
+ iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500

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

** Also affects: linux (Ubuntu Kinetic)
   Importance: High
 Assignee: Trent Lloyd (lathiat)
   Status: Confirmed

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

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

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

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

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Matthew Ruffell (mruffell)

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Matthew Ruffell (mruffell)

** Description changed:

+ BugLink: https://bugs.launchpad.net/bugs/1983656
+ 
+ [Impact]
+ 
  Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b] get
  no traffic flow and produce error messages in both the host and guest
  during network configuration.
  
  Environment: Ubuntu OpenStack Focal-Ussuri with OVN
  Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE
  Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy
  
  Host Error Messages:
  ice :98:00.1: VF 7 failed opcode 6, retval: -5
  
  Guest Error Messages:
  iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6
  
  In the context of these errors "6" refers to the value of
  VIRTCHNL_OP_CONFIG_VSI_QUEUES
  
  It was found in these cases that the VM is able to successfully transmit
  packets but never receives any and the RX packet drop counters for the
  VF in "ip link" on the host increase equal to the RX packet count.
  
  There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d
  claiming to resolve this error in some cases. It is already included in
- the test kernel v5.15.0-41 and did not resolve the issue.
+ 5.15.0-41-generic and did not resolve the issue.
  
  The following conditions are required to trigger the bug:
  - A port VLAN must be assigned by the host
  - The MTU must be set >1500 by the guest
  
- It appears that this ice/iavf driver is quite immature as many
- significant SR-IOV related fixes have landed in each of the recent
- kernel releases and we may need to consider pro-actively backporting
- more fixes.
+ There is no workaround, Intel E810 SR-IOV VFs with MTU >1500 cannot be
+ used without these patches.
  
- [ Impact ]
+ [Fix]
  
- Intel E810 (host: ice) SR-IOV VFs (guest: iavf) fail when a port VLAN is
- assigned by the host and the guest changes the MTU >1500. The guest iavf
- driver logs the following error and traffic flow stops:
- iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6
+ iavf currently sets the maximum packet size to IAVF_MAX_RXBUFFER, but on
+ the previous ice driver, it was decremented by VLAN_HLEN to make some
+ space to fit the VLAN header. This doesn't happen on iavf, and we end up
+ trying to use a packet size larger than IAVF_MAX_RXBUFFER, causing the
+ IAVF_ERR_PARAM error.
  
- There is no workaround, Intel E810 SR-IOV VFs with MTU >1500 cannot be
- used without this patch.
+ The fix is to change the maximum packet size from IAVF_MAX_RXBUFFER to
+ max_mtu received from the PF via GET_VF_RESOURCES msg.
  
- [ Fix ]
+ Also pick up a necessary commit for i40e to announce the correct maximum
+ packet size by GET_VF_RESOURCES msg.
  
- During queue configuration, VF's max packet size was set to
- IAVF_MAX_RXBUFFER but on ice max frame size was smaller by VLAN_HLEN
- due to making some space for port VLAN as VF is not aware whether it's
- in a port VLAN. This mismatch in sizes caused ice to reject queue
- configuration with ERR_PARAM error. Proper max_mtu is sent from ice PF
- to VF with GET_VF_RESOURCES msg but VF does not look at this.
+ This has been fixed by the following commits:
  
- In iavf change max_frame from IAVF_MAX_RXBUFFER to max_mtu
- received from pf with GET_VF_RESOURCES msg to make vf's
- max_frame_size dependent from pf. Add check if received max_mtu is
- not in eligible range then set it to IAVF_MAX_RXBUFFER.
+ commit 399c98c4dc50b7eb7e9f24da7ffdda6f025676ef
+ Author: Michal Jaron 
+ Date:   Tue Sep 13 15:38:35 2022 +0200
+ Subject: iavf: Fix set max MTU size with port VLAN and jumbo frames
+ Link: 
https://github.com/torvalds/linux/commit/399c98c4dc50b7eb7e9f24da7ffdda6f025676ef
  
- [ Test Plan ]
+ commit 372539def2824c43b6afe2403045b140f65c5acc
+ Author: Michal Jaron 
+ Date:   Tue Sep 13 15:38:36 2022 +0200
+ Subject: i40e: Fix VF set max MTU size
+ Link: 
https://github.com/torvalds/linux/commit/372539def2824c43b6afe2403045b140f65c5acc
  
- 1. Create a focal VM and assign an Intel E810 (ice) SR-IOV VF with a port
- vlan
+ A 

[Kernel-packages] [Bug 1991608] [NEW] TEE Support for CCP driver

[You-Sheng Yang]

Public bug reported:

Client and datacenter Zen4 SOC same PCI-ID but offer different
functionality from the PSP.

Genoa offers SEV, Client part offers TEE.
This patch fixes an ERR level message and CCP driver functionality not working.

ccp :02:00.5: tee: missing driver data
ccp :02:00.5: tee initialization failed

https://lore.kernel.org/linux-
crypto/20220928184506.13981-1-mario.limoncie...@amd.com/T/#m1b933ea4b961d17cb1be5be74e2d22a860507ca0

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

** Affects: linux-oem-6.0 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem-6.0 (Ubuntu Jammy)
 Importance: Undecided
 Status: In Progress

** Affects: linux-oem-6.0 (Ubuntu Kinetic)
 Importance: Undecided
 Status: Invalid


** Tags: amd oem-priority originate-from-1991371

** Tags added: amd oem-priority originate-from-1991371

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

** No longer affects: linux (Ubuntu)

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

** Also affects: linux-oem-6.0 (Ubuntu Kinetic)
   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/1991608

Title:
  TEE Support for CCP driver

Status in HWE Next:
  New
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  Client and datacenter Zen4 SOC same PCI-ID but offer different
  functionality from the PSP.

  Genoa offers SEV, Client part offers TEE.
  This patch fixes an ERR level message and CCP driver functionality not 
working.

  ccp :02:00.5: tee: missing driver data
  ccp :02:00.5: tee initialization failed

  https://lore.kernel.org/linux-
  
crypto/20220928184506.13981-1-mario.limoncie...@amd.com/T/#m1b933ea4b961d17cb1be5be74e2d22a860507ca0

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1991608/+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 1987312] Re: IWLMEI may cause device down at resuming from s2idle

[You-Sheng Yang]

Also fixed in upstream v6.0 commit 8997f5c8a627 (“wifi: iwlwifi: Mark
IWLMEI as broken”).

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

Title:
  IWLMEI may cause device down at resuming from s2idle

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms source package in Jammy:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in backport-iwlwifi-dkms source package in Kinetic:
  Fix Released
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  WiFi interfaces unsolicitedly down at resuming from s2idle.

  [Fix]

  Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN
  POR is only for Windows project design. Please remove or disable
  CONFIG_IWLMEI from Linux.

  [Test Case]

  Make sure iwlmei.ko is not built.

  [Where problems could occur]

  iwlmei was not enabled before 5.17 and was turned on automatically since
  then. This restores the state and shall not have impact on existing
  devices.

  == original bug report ==

  Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN
  POR is only for Windows project design. Please remove or disable
  CONFIG_IWLMEI from Linux.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1987312/+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 1987312] Re: IWLMEI may cause device down at resuming from s2idle

[You-Sheng Yang]

verified linux-oem-6.0/jammy version 6.0.0-1004.4.

$ find lib -name iwl\*
lib/modules/6.0.0-1004-oem/kernel/drivers/net/wireless/intel/iwlegacy
lib/modules/6.0.0-1004-oem/kernel/drivers/net/wireless/intel/iwlegacy/iwl3945.ko
lib/modules/6.0.0-1004-oem/kernel/drivers/net/wireless/intel/iwlegacy/iwl4965.ko
lib/modules/6.0.0-1004-oem/kernel/drivers/net/wireless/intel/iwlegacy/iwlegacy.ko
lib/modules/6.0.0-1004-oem/kernel/drivers/net/wireless/intel/iwlwifi
lib/modules/6.0.0-1004-oem/kernel/drivers/net/wireless/intel/iwlwifi/dvm/iwldvm.ko
lib/modules/6.0.0-1004-oem/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko
lib/modules/6.0.0-1004-oem/kernel/drivers/net/wireless/intel/iwlwifi/mvm/iwlmvm.ko
$ grep IWLMEI boot/config-6.0.0-1004-oem
# CONFIG_IWLMEI is not set

** Tags added: verification-done-jammy

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

Title:
  IWLMEI may cause device down at resuming from s2idle

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms source package in Jammy:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in backport-iwlwifi-dkms source package in Kinetic:
  Fix Released
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  WiFi interfaces unsolicitedly down at resuming from s2idle.

  [Fix]

  Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN
  POR is only for Windows project design. Please remove or disable
  CONFIG_IWLMEI from Linux.

  [Test Case]

  Make sure iwlmei.ko is not built.

  [Where problems could occur]

  iwlmei was not enabled before 5.17 and was turned on automatically since
  then. This restores the state and shall not have impact on existing
  devices.

  == original bug report ==

  Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN
  POR is only for Windows project design. Please remove or disable
  CONFIG_IWLMEI from Linux.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gke/5.4.0.1084.92)

[Ubuntu SRU Bot]

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

r8168/8.048.00-1ubuntu0.20.04.2 (amd64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all

[Chris Chiu]

According to the init_pin_configs of the attached alsainfo.txt, this
machine has already been applied with the fixup ALC294_FIXUP_ASUS_HPE.
But you might need more EAPD setting to enable the speaker.

Please try the following commands to see if speaker works.
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x40
sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x8800 

Remember to install alsa-tools if command `hda-verb` not found.

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

Title:
  [Asus Zenbook UX3402ZA] Sound doesn't work at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sound/speakers don't work at all on Asus Zenbook 14 OLED and other
  similar models with Realtek ALC294.

  No solution works. Audio is not muted, tried adding snd-hda arguments
  - no dice.

  This has been reported numerous times, when will a fix finally be
  rolled out?!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1730 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 12 13:57:05 2022
  InstallationDate: Installed on 2022-07-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX3402ZA.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX3402ZA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.5
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
  dmi.product.family: Zenbook
  dmi.product.name: Zenbook UX3402ZA_UX3402ZA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981433/+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 1988488] Re: Screen freeze at the moment of login on VirtualBox: [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.

[Daniel van Vugt]

Thanks. Indeed it seems the workaround is to just avoid selecting the
third party software option during install.


** Package changed: linux (Ubuntu) => ubuntu-restricted-extras (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/1988488

Title:
  Screen freeze at the moment of login on VirtualBox: [drm:vmw_msg_ioctl
  [vmwgfx]] *ERROR* Failed to open channel.

Status in ubuntu-restricted-extras package in Ubuntu:
  Confirmed

Bug description:
  The problem started to appear 2 weeks ago after one of my daily
  updates. It also happens after I re-install the system from a freshly
  downloaded ISO file. The system freezes at the moment, it starts the
  gnome display manager.

  I file the bug-report after a partial upgrade just before I will
  reboot the system. If needed I can reboot in recovery mode, since the
  gnome display manager is not started in that case.

  I tried the continue button without effect and also "apt upgrade" and
  "apt dist-upgrade" do have the same effect

  I run the VM from the Host-OpenZFS file system, so I can restore to
  before the update. Recently I use a Virtualbox snapshot to restore the
  system to before the update/upgrade.

  If you need log files, let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: systemd 251.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  1 19:42:04 2022
  InstallationDate: Installed on 2022-05-28 (96 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox 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/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-restricted-extras/+bug/1988488/+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 1990330] Re: System hang during S3 test

[AceLan Kao]

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

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

Title:
  System hang during S3 test

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  It hangs while doing S3 test on the platform with CPU Intel(R) Pentium(R) 
Silver N6005 @ 2.00GHz

  [Fix]
  Can't reproduce this issue with v5.18-rc1 kernel, so bisecting the kernel and 
found this below commit
  567511462387 mm/memcg: protect memcg_stock with a local_lock_t
  For safty, I backported the series of the patch
  https://www.spinics.net/lists/cgroups/msg31595.html
  But I still can reproduce the issue after applied those patches on top of 
5.17 oem kernel.
  So, I did a second round of bisecting and found below commit is required, too
  a74c6c00b1cb mm/memremap: avoid calling kasan_remove_zero_shadow() for device 
private memory

  [Test]
  Done the S3 test 400 times on the target and it's still working well.

  [Where problems could occur]
  Hard to evaluate the impact, but from the overnight test, the memory usage is 
still low, so there should be no memory leakage, and can't find any fix patch 
for those applied commits from upstream and linux-next trees.
  The patches are all from v5.18-rc1, so we only need them to be applied on 
oem-5.17 kernel, and will let QA to do thoroughly tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1990330/+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 1990997] Re: en_ZA locale not correct in applications

[Kai-Heng Feng]

** Package changed: linux (Ubuntu) => libreoffice (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/1990997

Title:
  en_ZA locale not correct in applications

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  In all Ubuntu based distributions I have found that in applications
  such as LibreOffice Calc where I need to see formats applicable to my
  locale en_ZA (South Africa) the decimal place is denoted by , in the
  application even though the file /usr/share/i18n/locales/en_ZA is
  correct in specifying the decimal place as denoted by a .

  This is the same for monetary values where it is showing , in
  applications instead of the . as specified in the locale file. The
  comma was deprecated in South Africa in the 1990s and the generally
  accepted decimal is .

  This makes it extremely difficult to transfer Windows Excel files that
  have decimal points to a Linux distro that strictly enforces
  recognising a decimal with a comma and hence renders the Windows Excel
  file useless in Linux.

  The Windows feature of customising locales in terms of date, time,
  decimal place and digit grouping within the GUI is sorely missing from
  all desktops in Linux and so this cannot be fixed by the end-user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1990997/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[Steve Langasek]

** Changed in: grub2-signed (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320

   * Test source code: https://github.com/os369510/grub2/tree/lp1842320

   * If you built the package, then test grubx64.efi is under
  “obj/monolithic/grub-efi-amd64/grubx64.efi”, in my case:
  

[Kernel-packages] [Bug 1991593] [NEW] nvidia-kernel-source-460 460.80-0ubuntu0.20.04.2: nvidia kernel module failed to build

[Sadeen Alaa]

Public bug reported:

It's a pop up message that appears to me.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-kernel-source-460 460.80-0ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39
Uname: Linux 5.15.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
DKMSKernelVersion: 5.15.0-46-generic
Date: Tue Oct  4 01:38:30 2022
Dependencies:
 
DuplicateSignature: 
dkms:nvidia-kernel-source-460:460.80-0ubuntu0.20.04.2:/var/lib/dkms/nvidia/460.80/build/common/inc/nv-time.h:208:18:
 error: ‘struct task_struct’ has no member named ‘state’; did you mean 
‘__state’?
InstallationDate: Installed on 2020-09-11 (752 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageVersion: 460.80-0ubuntu0.20.04.2
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.8
SourcePackage: nvidia-graphics-drivers-460
Title: nvidia-kernel-source-460 460.80-0ubuntu0.20.04.2: nvidia kernel module 
failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal need-duplicate-check

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

Title:
  nvidia-kernel-source-460 460.80-0ubuntu0.20.04.2: nvidia kernel module
  failed to build

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

Bug description:
  It's a pop up message that appears to me.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-kernel-source-460 460.80-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.15.0-46-generic
  Date: Tue Oct  4 01:38:30 2022
  Dependencies:
   
  DuplicateSignature: 
dkms:nvidia-kernel-source-460:460.80-0ubuntu0.20.04.2:/var/lib/dkms/nvidia/460.80/build/common/inc/nv-time.h:208:18:
 error: ‘struct task_struct’ has no member named ‘state’; did you mean 
‘__state’?
  InstallationDate: Installed on 2020-09-11 (752 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageVersion: 460.80-0ubuntu0.20.04.2
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.8
  SourcePackage: nvidia-graphics-drivers-460
  Title: nvidia-kernel-source-460 460.80-0ubuntu0.20.04.2: nvidia kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1991593/+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 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems

[Jeff Lane ]

Focal requires 1 addtional patch:
fa583f71a99c8 2019-10-24 Yin Fengwei ACPI: processor_idle: Skip dummy wait if 
kernel is in guest

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

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

Title:
  ACPI: processor idle: Practically limit "Dummy wait" workaround to old
  Intel systems

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  In Progress

Bug description:
  IMPACT:
  Old, circa 2002 chipsets have a bug: they don't go idle when they are
  supposed to.  So, a workaround was added to slow the CPU down and
  ensure that the CPU waits a bit for the chipset to actually go idle.
  This workaround is ancient and has been in place in some form since
  the original kernel ACPI implementation.

  But, this workaround is very painful on modern systems.  The "inl()"
  can take thousands of cycles (see Link: for some more detailed
  numbers and some fun kernel archaeology).

  First and foremost, modern systems should not be using this code.
  Typical Intel systems have not used it in over a decade because it is
  horribly inferior to MWAIT-based idle.

  Despite this, people do seem to be tripping over this workaround on
  AMD system today.

  Limit the "dummy wait" workaround to Intel systems.  Keep Modern AMD
  systems from tripping over the workaround.  Remotely modern Intel
  systems use intel_idle instead of this code and will, in practice,
  remain unaffected by the dummy wait.

  Reported-by: K Prateek Nayak 
  Suggested-by: Rafael J. Wysocki 
  Signed-off-by: Dave Hansen 
  Reviewed-by: Mario Limonciello 
  Tested-by: K Prateek Nayak 
  Link: 
https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/
  Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com

  FIX:

  This issue pertains to  all Zen based processors starting with
  Naples(Zen1). All LTS releases will need this fix:

  
https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9

  TESTCASE:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990985/+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 1970957] Re: suspend problem

[dnsem]

Same problem with Ubuntu 22.10 beta

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

Title:
  suspend problem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok
  intermittently. Some times it works fine, other times the computer
  does not enter the suspend mode (the screen gets blank, but the
  machine is still running and the ThinPad led is on, and there is no
  way out... no response from keyboard or mouse... the only solution is
  to switch off manually hitting and holding the power button), other
  times the machine does not wakes up from suspension mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 29 10:53:59 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-24 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  leoca  1913 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-24 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 20KQ000EBR
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/14/2018
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0PET42W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KQ000EBR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.19
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480:
  dmi.product.family: ThinkPad E480
  dmi.product.name: 20KQ000EBR
  dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480
  dmi.product.version: ThinkPad E480
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+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 1971193] Re: Server Crash while running IO and switch port bounce test with 2K login session

[Laurie Barry]

Yes, this is verified complete from our perspective based Development's
verification.

Was the test kernel you gave us was from your formal build process or
whether it was your personal sandbox build?

If what we've already received is a formal build then we will forward in
our DVT test organization and let you now if we find any other issues
but we don't anticipate any.

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

Title:
  Server Crash while running IO and switch port bounce test with 2K
  login session

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

Bug description:
  [Impact]
  Server crash and Call trace reported on one of the servers running IO and
  switch port bounce test from the 2K login session configuration.

  Call Trace:
  [56048.470488] Call Trace:
  [56048.470489]  _raw_spin_lock_irqsave+0x32/0x40
  [56048.470489]  lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc]
  [56048.470490]  lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc]
  [56048.470490]  lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc]
  [56048.470490]  lpfc_els_flush_cmd+0x43c/0x670 [lpfc]
  [56048.470491]  lpfc_els_flush_all_cmd+0x37/0x60 [lpfc]
  [56048.470491]  lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc]
  [56048.470492]  lpfc_do_work+0x1485/0x1d70 [lpfc]
  [56048.470492]  ? __schedule+0x280/0x700
  [56048.470492]  ? finish_wait+0x80/0x80
  [56048.470493]  ? lpfc_unregister_unused_fcf+0x80/0x80 [lpfc]
  [56048.470493]  kthread+0x112/0x130
  [56048.470493]  ? kthread_flush_work_fn+0x10/0x10
  [56048.470494]  ret_from_fork+0x1f/0x40
  [56048.470494] Kernel panic - not syncing: Hard LOCKUP
  [56048.470495] CPU: 0 PID: 682 Comm: lpfc_worker_0 Kdump: loaded Tainted: G
   IOE- -  - 4.18.0-240.el8.x86_64 #1
  [56048.470496] Hardware name: Dell Inc. PowerEdge R740/0DY2X0, BIOS 2.11.2
  004/21/2021
  [56048.470496] Call Trace:
  [56048.470496]  
  [56048.470496]  dump_stack+0x5c/0x80
  [56048.470497]  panic+0xe7/0x2a9
  [56048.470497]  ? __switch_to_asm+0x51/0x70
  [56048.470497]  nmi_panic.cold.9+0xc/0xc
  [56048.470498]  watchdog_overflow_callback.cold.7+0x5c/0x70
  [56048.470498]  __perf_event_overflow+0x52/0xf0
  [56048.470499]  handle_pmi_common+0x1db/0x270
  [56048.470499]  ? __set_pte_vaddr+0x32/0x50
  [56048.470499]  ? __native_set_fixmap+0x24/0x30
  [56048.470500]  ? ghes_copy_tofrom_phys+0xd3/0x1c0
  [56048.470500]  ? __ghes_peek_estatus.isra.12+0x49/0xa0
  [56048.470500]  intel_pmu_handle_irq+0xbf/0x160
  [56048.470501]  perf_event_nmi_handler+0x2d/0x50
  [56048.470501]  nmi_handle+0x63/0x110
  [56048.470501]  default_do_nmi+0x4e/0x100
  [56048.470502]  do_nmi+0x128/0x190
  [56048.470502]  end_repeat_nmi+0x16/0x6a
  [56048.470503] RIP: 0010:native_queued_spin_lock_slowpath+0x5d/0x1d0
  [56048.470504] Code: 0f ba 2f 08 0f 92 c0 0f b6 c0 c1 e0 08 89 c2 8b 07 30 e4
  09 d0 a9 00 01 ff ff 75 47 85 c0 74 0e 8b 07 84 c0 74 08 f3 90 8b 07 <84> c0 
75
  f8 b8 01 00 00 00 66 89 07 c3 8b 37 81 fe 00 01 00 00 75
  [56048.470504] RSP: 0018:acebc7877ca8 EFLAGS: 0002
  [56048.470505] RAX: 0101 RBX: 0246 RCX:
  001f
  [56048.470505] RDX:  RSI:  RDI:
  94dcf5341dc0
  [56048.470506] RBP: 94dcf534 R08: 0002 R09:
  00029600
  [56048.470506] R10: 60d29656a45c R11: 94dcf534fd12 R12:
  94dcf5341db0
  [56048.470507] R13: 94dcf5341dc0 R14: 94dcc4ae8a00 R15:
  0003
  [56048.470507]  ? native_queued_spin_lock_slowpath+0x5d/0x1d0
  [56048.470507]  ? native_queued_spin_lock_slowpath+0x5d/0x1d0
  [56048.470508]  
  [56048.470508]  _raw_spin_lock_irqsave+0x32/0x40
  [56048.470509]  lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc]
  [56048.470509]  lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc]
  [56048.470509]  lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc]
  [56048.470510]  lpfc_els_flush_cmd+0x43c/0x670 [lpfc]
  [56048.470510]  lpfc_els_flush_all_cmd+0x37/0x60 [lpfc]
  [56048.470510]  lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc]
  [56048.470511]  lpfc_do_work+0x1485/0x1d70 [lpfc]
  [56048.470511]  ? __schedule+0x280/0x700
  [56048.470511]  ? finish_wait+0x80/0x80
  [56048.470512]  ? lpfc_unregister_unused_fcf+0x80/0x80 [lpfc]
  [56048.470512]  kthread+0x112/0x130
  [56048.470513]  ? kthread_flush_work_fn+0x10/0x10
  [56048.470513]  ret_from_fork+0x1f/0x40
  [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]#

  [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat
  /etc/redhat-release
  Red Hat Enterprise Linux release 8.3 (Ootpa)

  [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat
  /sys/module/lpfc/version
  0:14.0.390.2

  [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat
  /sys/class/scsi_host/host*/modeldesc
  Emulex LightPulse LPe32002-M2 2-Port 32Gb Fibre Channel Adapter
  Emulex LightPulse LPe32002-M2 2-Port 32Gb Fibre Channel 

[Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all

[Arun]

Do let me know if there is anything you want me to look/check/test.

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

Title:
  [Asus Zenbook UX3402ZA] Sound doesn't work at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sound/speakers don't work at all on Asus Zenbook 14 OLED and other
  similar models with Realtek ALC294.

  No solution works. Audio is not muted, tried adding snd-hda arguments
  - no dice.

  This has been reported numerous times, when will a fix finally be
  rolled out?!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1730 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 12 13:57:05 2022
  InstallationDate: Installed on 2022-07-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX3402ZA.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX3402ZA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.5
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
  dmi.product.family: Zenbook
  dmi.product.name: Zenbook UX3402ZA_UX3402ZA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981433/+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 1988488] Re: Screen freeze at the moment of login on VirtualBox: [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.

[BertN45]

A screenshot of my settings in Virtualbox are in the attachment. If
needed I can also send the vbox file. Note that the first thing I do, if
I run into display/video issues, is switching off 3D acceleration, but
that did not help this time.

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988488/+attachment/5620817/+files/Screenshot%20from%202022-10-03%2015-23-22.png

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

Title:
  Screen freeze at the moment of login on VirtualBox: [drm:vmw_msg_ioctl
  [vmwgfx]] *ERROR* Failed to open channel.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The problem started to appear 2 weeks ago after one of my daily
  updates. It also happens after I re-install the system from a freshly
  downloaded ISO file. The system freezes at the moment, it starts the
  gnome display manager.

  I file the bug-report after a partial upgrade just before I will
  reboot the system. If needed I can reboot in recovery mode, since the
  gnome display manager is not started in that case.

  I tried the continue button without effect and also "apt upgrade" and
  "apt dist-upgrade" do have the same effect

  I run the VM from the Host-OpenZFS file system, so I can restore to
  before the update. Recently I use a Virtualbox snapshot to restore the
  system to before the update/upgrade.

  If you need log files, let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: systemd 251.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  1 19:42:04 2022
  InstallationDate: Installed on 2022-05-28 (96 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox 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/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988488/+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 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41

[Gannet]

The same is in Linux 6.0.0-06-generic:

[2.208269] kernel: fbcon: Taking over console
[2.208274] kernel: UBSAN: array-index-out-of-bounds in 
/home/kernel/COD/linux/drivers/ata/libahci.c:986:41
[2.208280] kernel: index 15 is out of range for type 'ahci_em_priv [8]'
[2.208284] kernel: CPU: 2 PID: 211 Comm: scsi_eh_8 Not tainted 
6.0.0-06-generic #202210022231
[2.208288] kernel: Hardware name: System manufacturer System Product 
Name/P5Q3, BIOS 110206/11/2010
[2.208290] kernel: Call Trace:
[2.208293] kernel:  
[2.208296] kernel:  show_stack+0x4e/0x61
[2.208302] kernel:  dump_stack_lvl+0x4a/0x6d
[2.208306] kernel:  dump_stack+0x10/0x18
[2.208309] kernel:  ubsan_epilogue+0x9/0x43
[2.208312] kernel:  __ubsan_handle_out_of_bounds.cold+0x42/0x47
[2.208315] kernel:  ahci_qc_issue+0x17e/0x190 [libahci]
[2.208322] kernel:  ata_qc_issue+0x138/0x2d0
[2.208326] kernel:  ata_exec_internal_sg+0x27e/0x560
[2.208330] kernel:  ata_exec_internal+0x85/0xd0
[2.208333] kernel:  sata_pmp_read+0x8d/0xd0
[2.208336] kernel:  sata_pmp_read_gscr+0x3b/0x80
[2.208339] kernel:  sata_pmp_attach+0x71/0x2e0
[2.208342] kernel:  ? ata_eh_reset+0x99d/0x1200
[2.208346] kernel:  ata_eh_revalidate_and_attach+0x276/0x4b0
[2.208350] kernel:  ata_eh_recover+0x691/0xa80
[2.208353] kernel:  ? ahci_do_softreset+0x240/0x240 [libahci]
[2.208358] kernel:  ? ahci_stop_engine+0xc0/0xc0 [libahci]
[2.208363] kernel:  ? ahci_do_hardreset+0x180/0x180 [libahci]
[2.208368] kernel:  ? ata_id_n_sectors+0xb0/0xb0
[2.208371] kernel:  ? __flush_work.isra.0+0x206/0x350
[2.208375] kernel:  sata_pmp_eh_recover.isra.0+0xe7/0x4c0
[2.208379] kernel:  sata_pmp_error_handler+0x22/0x40
[2.208382] kernel:  ahci_error_handler+0x45/0x90 [libahci]
[2.208387] kernel:  ata_scsi_port_error_handler+0x2ab/0x5f0
[2.208391] kernel:  ata_scsi_error+0x95/0xd0
[2.208394] kernel:  scsi_error_handler+0x98/0x190
[2.208398] kernel:  ? scsi_unjam_host+0x1d0/0x1d0
[2.208401] kernel:  kthread+0xe9/0x110
[2.208409] kernel:  ? kthread_complete_and_exit+0x20/0x20
[2.208412] kernel:  ret_from_fork+0x22/0x30
[2.208416] 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/1970074

Title:
  UBSAN: array-index-out-of-bounds in
  /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Something wrong with ata driver in dmesg found:

  [1.980693] kernel: 

  [1.980699] kernel: fbcon: Taking over console
  [1.980703] kernel: UBSAN: array-index-out-of-bounds in 
/build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
  [1.980709] kernel: index 15 is out of range for type 'ahci_em_priv [8]'
  [1.980713] kernel: CPU: 0 PID: 209 Comm: scsi_eh_8 Not tainted 
5.15.0-25-generic #25-Ubuntu
  [1.980716] kernel: Hardware name: System manufacturer System Product 
Name/P5Q3, BIOS 110206/11/2010
  [1.980718] kernel: Call Trace:
  [1.980721] kernel:  
  [1.980723] kernel:  show_stack+0x52/0x58
  [1.980729] kernel:  dump_stack_lvl+0x4a/0x5f
  [1.980734] kernel:  dump_stack+0x10/0x12
  [1.980736] kernel:  ubsan_epilogue+0x9/0x45
  [1.980739] kernel:  __ubsan_handle_out_of_bounds.cold+0x44/0x49
  [1.980742] kernel:  ahci_qc_issue+0x166/0x170 [libahci]
  [1.980748] kernel:  ata_qc_issue+0x135/0x240
  [1.980752] kernel:  ata_exec_internal_sg+0x2c4/0x580
  [1.980754] kernel:  ? vprintk_default+0x1d/0x20
  [1.980759] kernel:  ata_exec_internal+0x67/0xa0
  [1.980762] kernel:  sata_pmp_read+0x8d/0xc0
  [1.980765] kernel:  sata_pmp_read_gscr+0x3c/0x90
  [1.980768] kernel:  sata_pmp_attach+0x8b/0x310
  [1.980771] kernel:  ata_eh_revalidate_and_attach+0x28c/0x4b0
  [1.980775] kernel:  ata_eh_recover+0x6b6/0xb30
  [1.980778] kernel:  ? ahci_do_hardreset+0x180/0x180 [libahci]
  [1.980783] kernel:  ? ahci_stop_engine+0xb0/0xb0 [libahci]
  [1.980787] kernel:  ? ahci_do_softreset+0x290/0x290 [libahci]
  [1.980792] kernel:  ? 
trace_event_raw_event_ata_eh_link_autopsy_qc+0xe0/0xe0
  [1.980795] kernel:  sata_pmp_eh_recover.isra.0+0x214/0x560
  [1.980799] kernel:  sata_pmp_error_handler+0x23/0x40
  [1.980802] kernel:  ahci_error_handler+0x43/0x80 [libahci]
  [1.980806] kernel:  ata_scsi_port_error_handler+0x2b1/0x600
  [1.980810] kernel:  ata_scsi_error+0x9c/0xd0
  [1.980813] kernel:  scsi_error_handler+0xa1/0x180
  [1.980817] kernel:  ? scsi_unjam_host+0x1c0/0x1c0
  [1.980820] kernel:  kthread+0x12a/0x150
  [1.980823] kernel:  ? set_kthread_struct+0x50/0x50
  [1.980826] kernel:  ret_from_fork+0x22/0x30
  [1.980831] kernel:  

  ProblemType: Bug
  

[Kernel-packages] [Bug 1971193] Re: Server Crash while running IO and switch port bounce test with 2K login session

[Jeff Lane ]

Hi Laurie,

Just wanted to confirm that it's sufficient for this to be in 22.04 GA
(5.15) before I close it out

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

Title:
  Server Crash while running IO and switch port bounce test with 2K
  login session

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

Bug description:
  [Impact]
  Server crash and Call trace reported on one of the servers running IO and
  switch port bounce test from the 2K login session configuration.

  Call Trace:
  [56048.470488] Call Trace:
  [56048.470489]  _raw_spin_lock_irqsave+0x32/0x40
  [56048.470489]  lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc]
  [56048.470490]  lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc]
  [56048.470490]  lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc]
  [56048.470490]  lpfc_els_flush_cmd+0x43c/0x670 [lpfc]
  [56048.470491]  lpfc_els_flush_all_cmd+0x37/0x60 [lpfc]
  [56048.470491]  lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc]
  [56048.470492]  lpfc_do_work+0x1485/0x1d70 [lpfc]
  [56048.470492]  ? __schedule+0x280/0x700
  [56048.470492]  ? finish_wait+0x80/0x80
  [56048.470493]  ? lpfc_unregister_unused_fcf+0x80/0x80 [lpfc]
  [56048.470493]  kthread+0x112/0x130
  [56048.470493]  ? kthread_flush_work_fn+0x10/0x10
  [56048.470494]  ret_from_fork+0x1f/0x40
  [56048.470494] Kernel panic - not syncing: Hard LOCKUP
  [56048.470495] CPU: 0 PID: 682 Comm: lpfc_worker_0 Kdump: loaded Tainted: G
   IOE- -  - 4.18.0-240.el8.x86_64 #1
  [56048.470496] Hardware name: Dell Inc. PowerEdge R740/0DY2X0, BIOS 2.11.2
  004/21/2021
  [56048.470496] Call Trace:
  [56048.470496]  
  [56048.470496]  dump_stack+0x5c/0x80
  [56048.470497]  panic+0xe7/0x2a9
  [56048.470497]  ? __switch_to_asm+0x51/0x70
  [56048.470497]  nmi_panic.cold.9+0xc/0xc
  [56048.470498]  watchdog_overflow_callback.cold.7+0x5c/0x70
  [56048.470498]  __perf_event_overflow+0x52/0xf0
  [56048.470499]  handle_pmi_common+0x1db/0x270
  [56048.470499]  ? __set_pte_vaddr+0x32/0x50
  [56048.470499]  ? __native_set_fixmap+0x24/0x30
  [56048.470500]  ? ghes_copy_tofrom_phys+0xd3/0x1c0
  [56048.470500]  ? __ghes_peek_estatus.isra.12+0x49/0xa0
  [56048.470500]  intel_pmu_handle_irq+0xbf/0x160
  [56048.470501]  perf_event_nmi_handler+0x2d/0x50
  [56048.470501]  nmi_handle+0x63/0x110
  [56048.470501]  default_do_nmi+0x4e/0x100
  [56048.470502]  do_nmi+0x128/0x190
  [56048.470502]  end_repeat_nmi+0x16/0x6a
  [56048.470503] RIP: 0010:native_queued_spin_lock_slowpath+0x5d/0x1d0
  [56048.470504] Code: 0f ba 2f 08 0f 92 c0 0f b6 c0 c1 e0 08 89 c2 8b 07 30 e4
  09 d0 a9 00 01 ff ff 75 47 85 c0 74 0e 8b 07 84 c0 74 08 f3 90 8b 07 <84> c0 
75
  f8 b8 01 00 00 00 66 89 07 c3 8b 37 81 fe 00 01 00 00 75
  [56048.470504] RSP: 0018:acebc7877ca8 EFLAGS: 0002
  [56048.470505] RAX: 0101 RBX: 0246 RCX:
  001f
  [56048.470505] RDX:  RSI:  RDI:
  94dcf5341dc0
  [56048.470506] RBP: 94dcf534 R08: 0002 R09:
  00029600
  [56048.470506] R10: 60d29656a45c R11: 94dcf534fd12 R12:
  94dcf5341db0
  [56048.470507] R13: 94dcf5341dc0 R14: 94dcc4ae8a00 R15:
  0003
  [56048.470507]  ? native_queued_spin_lock_slowpath+0x5d/0x1d0
  [56048.470507]  ? native_queued_spin_lock_slowpath+0x5d/0x1d0
  [56048.470508]  
  [56048.470508]  _raw_spin_lock_irqsave+0x32/0x40
  [56048.470509]  lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc]
  [56048.470509]  lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc]
  [56048.470509]  lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc]
  [56048.470510]  lpfc_els_flush_cmd+0x43c/0x670 [lpfc]
  [56048.470510]  lpfc_els_flush_all_cmd+0x37/0x60 [lpfc]
  [56048.470510]  lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc]
  [56048.470511]  lpfc_do_work+0x1485/0x1d70 [lpfc]
  [56048.470511]  ? __schedule+0x280/0x700
  [56048.470511]  ? finish_wait+0x80/0x80
  [56048.470512]  ? lpfc_unregister_unused_fcf+0x80/0x80 [lpfc]
  [56048.470512]  kthread+0x112/0x130
  [56048.470513]  ? kthread_flush_work_fn+0x10/0x10
  [56048.470513]  ret_from_fork+0x1f/0x40
  [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]#

  [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat
  /etc/redhat-release
  Red Hat Enterprise Linux release 8.3 (Ootpa)

  [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat
  /sys/module/lpfc/version
  0:14.0.390.2

  [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat
  /sys/class/scsi_host/host*/modeldesc
  Emulex LightPulse LPe32002-M2 2-Port 32Gb Fibre Channel Adapter
  Emulex LightPulse LPe32002-M2 2-Port 32Gb Fibre Channel Adapter

  [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat
  /sys/class/scsi_host/host*/fwrev
  14.0.390.1, sli-4:2:c
  14.0.390.1, sli-4:2:c

  [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat
  

[Kernel-packages] [Bug 1971193] Re: Server Crash while running IO and switch port bounce test with 2K login session

[Jeff Lane ]

** Also affects: linux (Ubuntu Jammy)
   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/1971193

Title:
  Server Crash while running IO and switch port bounce test with 2K
  login session

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

Bug description:
  [Impact]
  Server crash and Call trace reported on one of the servers running IO and
  switch port bounce test from the 2K login session configuration.

  Call Trace:
  [56048.470488] Call Trace:
  [56048.470489]  _raw_spin_lock_irqsave+0x32/0x40
  [56048.470489]  lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc]
  [56048.470490]  lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc]
  [56048.470490]  lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc]
  [56048.470490]  lpfc_els_flush_cmd+0x43c/0x670 [lpfc]
  [56048.470491]  lpfc_els_flush_all_cmd+0x37/0x60 [lpfc]
  [56048.470491]  lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc]
  [56048.470492]  lpfc_do_work+0x1485/0x1d70 [lpfc]
  [56048.470492]  ? __schedule+0x280/0x700
  [56048.470492]  ? finish_wait+0x80/0x80
  [56048.470493]  ? lpfc_unregister_unused_fcf+0x80/0x80 [lpfc]
  [56048.470493]  kthread+0x112/0x130
  [56048.470493]  ? kthread_flush_work_fn+0x10/0x10
  [56048.470494]  ret_from_fork+0x1f/0x40
  [56048.470494] Kernel panic - not syncing: Hard LOCKUP
  [56048.470495] CPU: 0 PID: 682 Comm: lpfc_worker_0 Kdump: loaded Tainted: G
   IOE- -  - 4.18.0-240.el8.x86_64 #1
  [56048.470496] Hardware name: Dell Inc. PowerEdge R740/0DY2X0, BIOS 2.11.2
  004/21/2021
  [56048.470496] Call Trace:
  [56048.470496]  
  [56048.470496]  dump_stack+0x5c/0x80
  [56048.470497]  panic+0xe7/0x2a9
  [56048.470497]  ? __switch_to_asm+0x51/0x70
  [56048.470497]  nmi_panic.cold.9+0xc/0xc
  [56048.470498]  watchdog_overflow_callback.cold.7+0x5c/0x70
  [56048.470498]  __perf_event_overflow+0x52/0xf0
  [56048.470499]  handle_pmi_common+0x1db/0x270
  [56048.470499]  ? __set_pte_vaddr+0x32/0x50
  [56048.470499]  ? __native_set_fixmap+0x24/0x30
  [56048.470500]  ? ghes_copy_tofrom_phys+0xd3/0x1c0
  [56048.470500]  ? __ghes_peek_estatus.isra.12+0x49/0xa0
  [56048.470500]  intel_pmu_handle_irq+0xbf/0x160
  [56048.470501]  perf_event_nmi_handler+0x2d/0x50
  [56048.470501]  nmi_handle+0x63/0x110
  [56048.470501]  default_do_nmi+0x4e/0x100
  [56048.470502]  do_nmi+0x128/0x190
  [56048.470502]  end_repeat_nmi+0x16/0x6a
  [56048.470503] RIP: 0010:native_queued_spin_lock_slowpath+0x5d/0x1d0
  [56048.470504] Code: 0f ba 2f 08 0f 92 c0 0f b6 c0 c1 e0 08 89 c2 8b 07 30 e4
  09 d0 a9 00 01 ff ff 75 47 85 c0 74 0e 8b 07 84 c0 74 08 f3 90 8b 07 <84> c0 
75
  f8 b8 01 00 00 00 66 89 07 c3 8b 37 81 fe 00 01 00 00 75
  [56048.470504] RSP: 0018:acebc7877ca8 EFLAGS: 0002
  [56048.470505] RAX: 0101 RBX: 0246 RCX:
  001f
  [56048.470505] RDX:  RSI:  RDI:
  94dcf5341dc0
  [56048.470506] RBP: 94dcf534 R08: 0002 R09:
  00029600
  [56048.470506] R10: 60d29656a45c R11: 94dcf534fd12 R12:
  94dcf5341db0
  [56048.470507] R13: 94dcf5341dc0 R14: 94dcc4ae8a00 R15:
  0003
  [56048.470507]  ? native_queued_spin_lock_slowpath+0x5d/0x1d0
  [56048.470507]  ? native_queued_spin_lock_slowpath+0x5d/0x1d0
  [56048.470508]  
  [56048.470508]  _raw_spin_lock_irqsave+0x32/0x40
  [56048.470509]  lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc]
  [56048.470509]  lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc]
  [56048.470509]  lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc]
  [56048.470510]  lpfc_els_flush_cmd+0x43c/0x670 [lpfc]
  [56048.470510]  lpfc_els_flush_all_cmd+0x37/0x60 [lpfc]
  [56048.470510]  lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc]
  [56048.470511]  lpfc_do_work+0x1485/0x1d70 [lpfc]
  [56048.470511]  ? __schedule+0x280/0x700
  [56048.470511]  ? finish_wait+0x80/0x80
  [56048.470512]  ? lpfc_unregister_unused_fcf+0x80/0x80 [lpfc]
  [56048.470512]  kthread+0x112/0x130
  [56048.470513]  ? kthread_flush_work_fn+0x10/0x10
  [56048.470513]  ret_from_fork+0x1f/0x40
  [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]#

  [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat
  /etc/redhat-release
  Red Hat Enterprise Linux release 8.3 (Ootpa)

  [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat
  /sys/module/lpfc/version
  0:14.0.390.2

  [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat
  /sys/class/scsi_host/host*/modeldesc
  Emulex LightPulse LPe32002-M2 2-Port 32Gb Fibre Channel Adapter
  Emulex LightPulse LPe32002-M2 2-Port 32Gb Fibre Channel Adapter

  [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat
  /sys/class/scsi_host/host*/fwrev
  14.0.390.1, sli-4:2:c
  14.0.390.1, sli-4:2:c

  [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat
  /sys/class/fc_host/host*/port_name
  0x1090faf09459
  

[Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04

[Jeff Lane ]

PRs made for both Jammy and Kinetic. Kinetic was only missing the last 6
patches.

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

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

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Jeff Lane  (bladernr)

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

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

** Changed in: linux (Ubuntu Kinetic)
 Assignee: (unassigned) => Jeff Lane  (bladernr)

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

Title:
  Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04

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

Bug description:
  [IMPACT/Justification]
  There are numerous bug fixes included in the more recent version of lpfc that 
Broadcom has asked to pull into Jammy and Kinetic.  These all are limited to 
the lpfc driver itself, no patches to core code are requested.

  [FIX]

  A few of these were already landed in Jammy, and all but 6 (ones
  landed in 6.0 upstream) were already in Kinetic.

  b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches
  71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5
  b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into 
lpfc_sli_prep_abort_xri()
  ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved 
configuration
  ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress test
  2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue CMF 
WQE
  0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in 
queuecommand after VMID
  35251b4d79db scsi: lpfc: Set PU field when providing D_ID in 
XMIT_ELS_RSP64_CX iocb
  f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with 
malformed user input
  4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in 
lpfc_nvme_cancel_iocb()
  1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4
  2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for 
nvme_admin_async_event cmd completion
  ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for 
aborted NVMe cmds
  336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT 
topology
  b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is 
aborted
  6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after 
starget_to_rport()
  e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path 
refactoring
  24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort path 
refactoring
  44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in 
lpfc_ct_reject_event()
  a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices
  348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol 
independent
  ed913cf4a533 scsi: lpfc: Commonize VMID code location
  fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3
  a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros for 
NVMe I/O
  e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic
  de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up
  5099478e436f scsi: lpfc: Change VMID registration to be based on fabric 
parameters
  dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if 
lpfc_err_lost_link()
  4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in 
rscn_recovery_check()
  596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event()
  ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is inserted
  b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion
  ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths
  84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()
  775266207105 scsi: lpfc: Correct BDE DMA address assignment for GEN_REQ_WQE
  cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE
  c2024e3b33ee scsi: lpfc: Remove redundant lpfc_sli_prep_wqe() call
  92bd903da12b scsi: lpfc: Fix additional reference counting in 
lpfc_bsg_rport_els()
  db05628435aa blk-cgroup: move blkcg_{get,set}_fc_appid out of line
  646db1a560f4 scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp()
  3d1d34ec1fbc scsi: lpfc: Remove unnecessary null ndlp check in 
lpfc_sli_prep_wqe()
  a346f28ad231 scsi: lpfc: Remove unneeded variable
  66c20a97367a scsi: lpfc: Copyright updates for 14.2.0.2 patches
  4af4d0e2ea94 scsi: lpfc: Update lpfc version to 14.2.0.2
  fd4a0c6da5c1 scsi: lpfc: Expand setting ELS_ID field in ELS_REQUEST64_WQE
  f4fbf4acaa50 scsi: lpfc: Update stat accounting for READ_STATUS mbox command
  ef47575fd982 scsi: lpfc: Refactor cleanup of 

[Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all

[Arun]

Tried the kernel from the link you sent, still no sound yet. :(

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

Title:
  [Asus Zenbook UX3402ZA] Sound doesn't work at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sound/speakers don't work at all on Asus Zenbook 14 OLED and other
  similar models with Realtek ALC294.

  No solution works. Audio is not muted, tried adding snd-hda arguments
  - no dice.

  This has been reported numerous times, when will a fix finally be
  rolled out?!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1730 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 12 13:57:05 2022
  InstallationDate: Installed on 2022-07-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX3402ZA.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX3402ZA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.5
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
  dmi.product.family: Zenbook
  dmi.product.name: Zenbook UX3402ZA_UX3402ZA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981433/+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 1988488] Re: Screen freeze at the moment of login on VirtualBox: [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.

[Marian Rainer-Harbach]

Hi Daniel, I played around with VirtualBox settings and Ubuntu installer
settings: The problem seems to occur only when "Install third-party
software for graphics and Wi-Fi hardware and additional media formats"
is selected in the Ubuntu installer.

If the option is _not_ selected, the installed system boots normally.
And indeed, after then installing the package ubuntu-restricted-extras,
the problem occurs on the next boot.

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

Title:
  Screen freeze at the moment of login on VirtualBox: [drm:vmw_msg_ioctl
  [vmwgfx]] *ERROR* Failed to open channel.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The problem started to appear 2 weeks ago after one of my daily
  updates. It also happens after I re-install the system from a freshly
  downloaded ISO file. The system freezes at the moment, it starts the
  gnome display manager.

  I file the bug-report after a partial upgrade just before I will
  reboot the system. If needed I can reboot in recovery mode, since the
  gnome display manager is not started in that case.

  I tried the continue button without effect and also "apt upgrade" and
  "apt dist-upgrade" do have the same effect

  I run the VM from the Host-OpenZFS file system, so I can restore to
  before the update. Recently I use a Virtualbox snapshot to restore the
  system to before the update/upgrade.

  If you need log files, let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: systemd 251.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  1 19:42:04 2022
  InstallationDate: Installed on 2022-05-28 (96 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox 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/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988488/+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 1991551] Re: i2c-mlxbf.c: Sync up driver with upstreaming

[Asmaa Mnebhi]

** Description changed:

  SRU Justification:
  
  [Impact]
  
  Several i2c-mlxbf.c patches have been upstreamed recently and are in
  linux-next at the moment. So revert all changes in both Focal (5.4) and
  Jammy (5.15) and cherry-pick all changes from linux-next master.
  
- IMPORTANT NOTE: please make sure you also load the latest UEFI (EDK2)
- firmware because there are dependencies.
+ IMPORTANT NOTE: The new linux i2c support for BF3 also REQUIRES
+ upgrading the UEFI firmware version. For BF1 and BF2 however, this
+ driver should be backward compatible with older UEFI versions.
  
  [Fix]
  
  * There is a total of 17 commits: 8 reverts, 8 cherry-picks from linux-
  next and one internal "UBUNTU: SAUCE:" to ad the driver version.
  Following is the list of commits cherry-picked.
  
  * i2c: mlxbf: incorrect base address passed during io write
  From 

  
  * i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction()
  From 

  
  * i2c: mlxbf: remove IRQF_ONESHOT
  From 

  
  * i2c: mlxbf: Fix frequency calculation
  From 

  
  * i2c: mlxbf: support lock mechanism
  From 

  
  * i2c: mlxbf: add multi slave functionality
  From 

  
  * i2c: mlxbf: support BlueField-3 SoC
  From 

  
  * i2c: mlxbf: remove device tree support
  From 

  
  * Also add the i2c driver version to keep track of the changes
  internally.
  
  [Test Case]
  
  * Check that the i2c driver loads without errors on BF1 and BF2 (dmesg, and 
check i2c1 sysfs is created)
  * Check that the i2c module can be removed and reloaded without errors.
  * Check that IPMB services work successfully on systems with BMC. This is the 
best way to test the i2c driver. Run ipmitool command from the BF: ipmitool mc 
info
  * Run ipmitool from the BMC as well: ipmitool -I ipmb mc info
+ * This driver should be backward compatible
+ * Make sure this driver is backward compatible with older UEFI version (only 
applicable for BF1 and BF2)
+ * Make sure this driver works for BF1, BF2 and BF3 with the latest UEFI 
version.
  
  [Regression Potential]
  
  * The i2c driver could fail to load because the UEFI firmware hasn't been 
upgraded
  * The i2c driver would fail to load due to a bug
  * IPMB code which utilises the i2c driver fails to work (ipmitool commands)

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

Title:
  i2c-mlxbf.c: Sync up driver with upstreaming

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]

  Several i2c-mlxbf.c patches have been upstreamed recently and are in
  linux-next at the moment. So revert all changes in both Focal (5.4)
  and Jammy (5.15) and cherry-pick all changes from linux-next master.

  IMPORTANT NOTE: The new linux i2c support for BF3 also REQUIRES
  upgrading the UEFI firmware version. For BF1 and BF2 however, this
  driver should be backward compatible with older UEFI versions.

  [Fix]

  * There is a total of 17 commits: 8 reverts, 8 cherry-picks from
  linux-next and one internal "UBUNTU: SAUCE:" to ad the driver version.
  Following is the list of commits cherry-picked.

  * i2c: mlxbf: incorrect base address passed during io write
  From 


  * i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction()
  From 


  * i2c: mlxbf: remove IRQF_ONESHOT
  From 


  * i2c: mlxbf: Fix frequency calculation
  From 


  * i2c: mlxbf: support lock mechanism
  From 

[Kernel-packages] [Bug 1961338] Re: Disable unprivileged BPF by default

[Thadeu Lima de Souza Cascardo]

** Tags added: verification-done-focal

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

Title:
  Disable unprivileged BPF by default

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Unprivileged users have access to BPF, allowing them to execute code in the 
kernel under their control. Though restricted and verified, a lot of security 
issues have been uncovered over the years, indicating that it should be 
disabled by default in order to protect our users.

  Admins can reenable that access or give CAP_BPF to programs if needed.

  [Test case]
  A qa-regression-testing testcase has been added that checks for the ability 
to load BPF programs under different circumstances.

  [Potential regression]
  Users who rely on unprivileged BPF access will need to change the setting or 
give CAP_BPF to their programs. Also, sysctl and bpf code might be affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961338/+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 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04

[Jeff Lane ]

Hi, could you please update the summary with a test case that verifies
this fix?

** Description changed:

  [IMPACT/Justification]
- 
+ There are numerous bug fixes included in the more recent version of lpfc that 
Broadcom has asked to pull into Jammy and Kinetic.  These all are limited to 
the lpfc driver itself, no patches to core code are requested.
  
  [FIX]
  
- Please integrate the latest set of bug fix patches accepted in mkp/scsi
- 5.20/scsi-staging
+ A few of these were already landed in Jammy, and all but 6 (ones landed
+ in 6.0 upstream) were already in Kinetic.
  
  b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches
  71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5
  b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into 
lpfc_sli_prep_abort_xri()
  ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved 
configuration
  ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress test
  2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue CMF 
WQE
  0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in 
queuecommand after VMID
  35251b4d79db scsi: lpfc: Set PU field when providing D_ID in 
XMIT_ELS_RSP64_CX iocb
  f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with 
malformed user input
  4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in 
lpfc_nvme_cancel_iocb()
  1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4
  2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for 
nvme_admin_async_event cmd completion
  ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for 
aborted NVMe cmds
  336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT 
topology
  b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is 
aborted
  6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after 
starget_to_rport()
  e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path 
refactoring
  24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort path 
refactoring
  44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in 
lpfc_ct_reject_event()
  a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices
  348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol 
independent
  ed913cf4a533 scsi: lpfc: Commonize VMID code location
  fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3
  a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros for 
NVMe I/O
  e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic
  de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up
  5099478e436f scsi: lpfc: Change VMID registration to be based on fabric 
parameters
  dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if 
lpfc_err_lost_link()
  4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in 
rscn_recovery_check()
  596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event()
  ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is inserted
  b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion
  ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths
  84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()
  775266207105 scsi: lpfc: Correct BDE DMA address assignment for GEN_REQ_WQE
  cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE
  c2024e3b33ee scsi: lpfc: Remove redundant lpfc_sli_prep_wqe() call
  92bd903da12b scsi: lpfc: Fix additional reference counting in 
lpfc_bsg_rport_els()
  db05628435aa blk-cgroup: move blkcg_{get,set}_fc_appid out of line
  646db1a560f4 scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp()
  3d1d34ec1fbc scsi: lpfc: Remove unnecessary null ndlp check in 
lpfc_sli_prep_wqe()
  a346f28ad231 scsi: lpfc: Remove unneeded variable
  66c20a97367a scsi: lpfc: Copyright updates for 14.2.0.2 patches
  4af4d0e2ea94 scsi: lpfc: Update lpfc version to 14.2.0.2
  fd4a0c6da5c1 scsi: lpfc: Expand setting ELS_ID field in ELS_REQUEST64_WQE
  f4fbf4acaa50 scsi: lpfc: Update stat accounting for READ_STATUS mbox command
  ef47575fd982 scsi: lpfc: Refactor cleanup of mailbox commands
  d51cf5bd926c scsi: lpfc: Fix field overload in lpfc_iocbq data structure
  1045592fc968 scsi: lpfc: Introduce FC_RSCN_MEMENTO flag for tracking post 
RSCN completion
  6c983d327b9e scsi: lpfc: Register for Application Services FC-4 type in 
Fabric topology
  6c8a3ce64b2c scsi: lpfc: Remove false FDMI NVMe FC-4 support for NPIV ports
  c364c453d30a scsi: lpfc: Revise FDMI reporting of supported port speed for 
trunk groups
  d6d45f67a111 scsi: lpfc: Fix call trace observed during I/O with CMF enabled
  5295d19d4f97 scsi: lpfc: Correct CRC32 calculation for congestion stats
  39a1a86b9da2 scsi: lpfc: Move MI module parameter check to handle dynamic 
disable
  d531d9874da8 scsi: lpfc: Remove unnecessary NULL pointer assignment for 
ELS_RDF path
  

[Kernel-packages] [Bug 1991551] [NEW] i2c-mlxbf.c: Sync up driver with upstreaming

[Asmaa Mnebhi]

Public bug reported:

SRU Justification:

[Impact]

Several i2c-mlxbf.c patches have been upstreamed recently and are in
linux-next at the moment. So revert all changes in both Focal (5.4) and
Jammy (5.15) and cherry-pick all changes from linux-next master.

IMPORTANT NOTE: please make sure you also load the latest UEFI (EDK2)
firmware because there are dependencies.

[Fix]

* There is a total of 17 commits: 8 reverts, 8 cherry-picks from linux-
next and one internal "UBUNTU: SAUCE:" to ad the driver version.
Following is the list of commits cherry-picked.

* i2c: mlxbf: incorrect base address passed during io write
>From 
>

* i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction()
>From 
>

* i2c: mlxbf: remove IRQF_ONESHOT
>From 
>

* i2c: mlxbf: Fix frequency calculation
>From 
>

* i2c: mlxbf: support lock mechanism
>From 
>

* i2c: mlxbf: add multi slave functionality
>From 
>

* i2c: mlxbf: support BlueField-3 SoC
>From 
>

* i2c: mlxbf: remove device tree support
>From 
>

* Also add the i2c driver version to keep track of the changes
internally.

[Test Case]

* Check that the i2c driver loads without errors on BF1 and BF2 (dmesg, and 
check i2c1 sysfs is created)
* Check that the i2c module can be removed and reloaded without errors.
* Check that IPMB services work successfully on systems with BMC. This is the 
best way to test the i2c driver. Run ipmitool command from the BF: ipmitool mc 
info
* Run ipmitool from the BMC as well: ipmitool -I ipmb mc info

[Regression Potential]

* The i2c driver could fail to load because the UEFI firmware hasn't been 
upgraded
* The i2c driver would fail to load due to a bug
* IPMB code which utilises the i2c driver fails to work (ipmitool commands)

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

** Description changed:

  SRU Justification:
  
  [Impact]
  
  Several i2c-mlxbf.c patches have been upstreamed recently and are in
  linux-next at the moment. So revert all changes in both Focal (5.4) and
  Jammy (5.15) and cherry-pick all changes from linux-next master.
  
  IMPORTANT NOTE: please make sure you also load the latest UEFI (EDK2)
  firmware because there are dependencies.
  
  [Fix]
  
+ * There is a total of 17 commits: 8 reverts, 8 cherry-picks from linux-
+ next and one internal "UBUNTU: SAUCE:" to ad the driver version.
+ Following is the list of commits cherry-picked.
+ 
  * i2c: mlxbf: incorrect base address passed during io write
- From 

 
+ From 

  
  * i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction()
- From 

 
+ From 

  
  * i2c: mlxbf: remove IRQF_ONESHOT
- From 

 
+ From 

  
  * i2c: mlxbf: Fix frequency calculation
- From 

 
+ From 

  
  * i2c: mlxbf: support lock mechanism
- From 

 
+ From 

  
  * i2c: mlxbf: add 

[Kernel-packages] [Bug 1968604] Re: rtl8761b usb bluetooth doesn't work following reboot until unplug/replug

[Bert RAM Aerts]

Update on Ubuntu 22.10 beta with kernel 5.19
Same issue as kernel 5.15 and same solution with symbolic links so that "bu" is 
in fact "b".

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

Title:
  rtl8761b usb bluetooth doesn't work following reboot until
  unplug/replug

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I have usb bluetooth 5.0 dongle which uses Realtek RTL8761B chip.
  0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio

  USB adapter very often stops working, can't connect or find other
  bluetooth devices. The adapter can't work even after reboots.

  The following entries appear in the log:
  апр 11 13:47:14 desktop kernel: Bluetooth: hci0: command 0x2005 tx timeout
  апр 11 13:47:16 desktop kernel: Bluetooth: hci0: command 0x2041 tx timeout
  апр 11 13:47:18 desktop kernel: Bluetooth: hci0: command 0x2042 tx timeout

  Firmware loaded correctly, but something is not working.
  апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=000b lmp_ver=0a lmp_subver=8761
  апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: rom_version status=0 
version=1
  апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_fw.bin
  апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_config.bin
  апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 27814

  1) I use:
  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04
  2) linux-firmware: 20220329.git681281e4-0ubuntu1
  3) What you expected to happen? I expect a well working bluetooth adapter.
  4) What happened instead? My bluetooth adapter may work, may not. The adapter 
may stop finding and connecting to other devices.

  I've found the same bug https://bugzilla.kernel.org/show_bug.cgi?id=214111#c1
  I've downloaded Windows's archive 
http://download.windowsupdate.com/d/msdownload/update/driver/drvs/2021/05/ca0e770c-6a5d-4de0-b37a-f4b91cccd8c3_7778831d2b9d721cf94d5a8d8c0676ff1b96c874.cab
  I've unpacked file rtl8761b_mp_chip_bt40_fw_asic_rom_patch_new.dll and 
replaced /usr/lib/firmware/rtl_bt/rtl8761bu_fw.bin and deleted 
rtl8761bu_config.bin
  After I changed firmware my usb dongle work fine.

  Could you change firmware rtl8761bu_fw.bin rtl8761bu_config.bin to other 
correct version?
  Could you move Realtek's rtl_bt firmware or RTL8761B's firmware into separate 
packages. I will remove the RTL8761B firmware package and put them manually.

  bluetoothctl --version
  bluetoothctl: 5.64

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:E0:4C:FC:E2:03  ACL MTU: 1021:6  SCO MTU: 255:12
  UP RUNNING
  RX bytes:5751 acl:49 sco:0 events:489 errors:0
  TX bytes:219114 acl:398 sco:0 commands:83 errors:0
  Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
  Link policy: RSWITCH HOLD SNIFF PARK
  Link mode: PERIPHERAL ACCEPT
  Name: 'desktop'
  Class: 0x7c0104
  Service Classes: Rendering, Capturing, Object Transfer, Audio, 
Telephony
  Device Class: Computer, Desktop workstation
  HCI Version: 5.1 (0xa)  Revision: 0x97b
  LMP Version: 5.1 (0xa)  Subversion: 0xec43
  Manufacturer: Realtek Semiconductor Corporation (93)

  rfkill list
  0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  Realtek's worker updated these bad firmware.
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=45dc5f0b8e2f2d43312d22511cb26658b9ee2c80

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1968604/+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 1908894] Re: USB controllers disconnects after random time

[Piotr Henryk Dabrowski]

I had problems with my USB 3.5" hard disk case disconnecting randomly.

I found recommendation to turn off USB xHCI Handoff option in BIOS.

I also disabled USB autosuspend with `usbcore.autosuspend=-1` kernel
parameter (`GRUB_CMDLINE_LINUX_DEFAULT="..."` in /etc/default/grub, then
`sudo update-grub`)

Neither of the above helped.

Then I added `no-usb-handoff` kernel parameter,
and also `usbcore.quirks=1234:5678:en` quirk [1],
where 1234:5678 is the idVendor:idProduct identifier of your device, obtainable 
with `lsusb`:

e = USB_QUIRK_RESET (device can't be reset (e.g morph devices), don't use 
reset);
n = USB_QUIRK_DELAY_CTRL_MSG (Device needs a pause after every control message);

And that seems to have finally done the trick. No more disconnects.

[1] https://www.kernel.org/doc/html/v5.0/admin-guide/kernel-
parameters.html

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

Title:
  USB controllers disconnects after random time

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since I installed Ubuntu on my new convertible laptop, I got issues with the 
USB. Just after boot my USB controller is working properly (I can connect usb 
sticks, mices, and my internal camera works) and at some point long after it 
suddenly stop working (mices suddenly stop moving even when used, webcam and 
sticks no more detected).
  This can happend few minuts after boot, or several days after.
  Yet I have not been able to find what triggers the failure. It happends at 
any time during normal usage of the computer, including during the usb usage.

  more concrete infos:
  after failure, I get
  $ dmesg

  [ 2671.894099] perf: interrupt took too long (2512 > 2500), lowering 
kernel.perf_event_max_sample_rate to 79500
  [ 3262.197917] xhci_hcd :03:00.3: Mismatch between completed Set TR Deq 
Ptr command & xHCI internal state.
  [ 3262.197927] xhci_hcd :03:00.3: ep deq seg = 8dafef36, deq ptr 
= 5f96ce32
  [ 3262.198052] xhci_hcd :03:00.3: AMD-Vi: Event logged [IO_PAGE_FAULT 
domain=0x000a address=0x0 flags=0x]
  [ 3267.250397] xhci_hcd :03:00.3: xHCI host not responding to stop 
endpoint command.
  [ 3267.250428] xhci_hcd :03:00.3: xHCI host controller not responding, 
assume dead
  [ 3267.250463] xhci_hcd :03:00.3: HC died; cleaning up
  [ 3267.250499] usb 1-3: USB disconnect, device number 2
  [ 3267.311251] usb 1-4: USB disconnect, device number 3

  and lsusb doesn't show my devices anymore, even the newly inserted
  ones

  config: Asus Zenbook flip 14 UM462DA

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jimy   1523 F pulseaudio
   /dev/snd/controlC0:  jimy   1523 F pulseaudio
   /dev/snd/pcmC1D0p:   jimy   1523 F...m pulseaudio
   /dev/snd/timer:  jimy   1523 f pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Dec 21 11:51:08 2020
  InstallationDate: Installed on 2020-07-28 (146 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX462DA
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=ba0f4ac4-b614-4882-83d6-485690f9a61a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/28/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX462DA.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX462DA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX462DA.307:bd09/28/2020:svnASUSTeKCOMPUTERINC.:pnZenBookUX462DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX462DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX462DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1970957] Re: suspend problem

[dnsem]

I have same problem - suspend is OK but resume leaves no signal on monitor. I 
can ssh to the machine and reboot.
This is irrespective of Wayland/Xorg, BIOS security etc.
Tried with kernels 5.15.0-48-generic and 5.17.0-1018-oem.

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

Title:
  suspend problem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok
  intermittently. Some times it works fine, other times the computer
  does not enter the suspend mode (the screen gets blank, but the
  machine is still running and the ThinPad led is on, and there is no
  way out... no response from keyboard or mouse... the only solution is
  to switch off manually hitting and holding the power button), other
  times the machine does not wakes up from suspension mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 29 10:53:59 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-24 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  leoca  1913 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-24 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 20KQ000EBR
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/14/2018
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0PET42W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KQ000EBR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.19
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480:
  dmi.product.family: ThinkPad E480
  dmi.product.name: 20KQ000EBR
  dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480
  dmi.product.version: ThinkPad E480
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+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 1961338] Re: Disable unprivileged BPF by default

[Ubuntu Kernel Bot]

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

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!

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

Title:
  Disable unprivileged BPF by default

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Unprivileged users have access to BPF, allowing them to execute code in the 
kernel under their control. Though restricted and verified, a lot of security 
issues have been uncovered over the years, indicating that it should be 
disabled by default in order to protect our users.

  Admins can reenable that access or give CAP_BPF to programs if needed.

  [Test case]
  A qa-regression-testing testcase has been added that checks for the ability 
to load BPF programs under different circumstances.

  [Potential regression]
  Users who rely on unprivileged BPF access will need to change the setting or 
give CAP_BPF to their programs. Also, sysctl and bpf code might be affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961338/+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 1960324] Re: [VROC] Kernel does not contain fixes for iostat for md devices

[Kinga Tanska]

Hello @bladernr,

do you have any update of this issue?

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

Title:
  [VROC] Kernel does not contain fixes for iostat for md devices

Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe-5.13 package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Invalid
Status in linux-hwe-5.13 source package in Focal:
  In Progress
Status in linux source package in Impish:
  Won't Fix
Status in linux-hwe-5.13 source package in Impish:
  Invalid

Bug description:
  Hello,

  I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does
  not contain fixes for IO statistics for md devices. IO statistics for
  md devices were added to kernel 5.10
  
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d)
  but then bug for double fault was reported and this patch was reverted
  by Guoqing Jiang
  
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8).

  Guoqing Jiang added series of patches which fixes problem and adds IO stats 
for md devices on top on the revert patch:
  - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f 
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f)
  - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b 
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b)

  I checked that kernel used in ubuntu 22.04 contains only patch with revert - 
iostat does not report for md devices 
(https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13=author=Guoqing+Jiang)
  Please consider adding series of patches described above.

  Regards,
  Kinga Tanska

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960324/+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 1991254] Re: No HDMI sound output from alsa in server (no KMS)

[Juerg Haefliger]

A DT change broke the audio driver. Working on it.

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

** Changed in: linux-raspi (Ubuntu Kinetic)
   Status: New => In Progress

** Changed in: linux-raspi (Ubuntu Kinetic)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

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

Title:
  No HDMI sound output from alsa in server (no KMS)

Status in linux-raspi package in Ubuntu:
  In Progress
Status in linux-raspi source package in Kinetic:
  In Progress

Bug description:
  During ISO testing of the beta Ubuntu Server 22.10 for Raspberry Pi
  image, on a Raspberry Pi 4B and 3B, I noted that the HDMI "sound card"
  no longer appears in /proc/asound/cards; only the Headphones output
  (from the AUX socket on the board) appears.

  I checked with the current linux-raspi in the release pocket
  (5.19.0-1001-raspi), and the new one in proposed (5.19.0-1002-raspi),
  and both exhibit the same issue.

  On Kinetic:

  $ cat /proc/asound/cards
   0 [Headphones ]: bcm2835_headpho - bcm2835 Headphones
    bcm2835 Headphones

  On Jammy:

  $ cat /proc/asound/cards
   0 [b1 ]: bcm2835_hdmi - bcm2835 HDMI 1
    bcm2835 HDMI 1
   1 [Headphones ]: bcm2835_headpho - bcm2835 Headphones
    bcm2835 Headphones

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1991254/+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 1970957] Re: suspend problem

[dnsem]

I have same problem - suspend is OK but resume leaves no signal on monitor. I 
can ssh to the machine and reboot.
This is irrespective of Wayland/Xorg, BIOS security etc.

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

Title:
  suspend problem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok
  intermittently. Some times it works fine, other times the computer
  does not enter the suspend mode (the screen gets blank, but the
  machine is still running and the ThinPad led is on, and there is no
  way out... no response from keyboard or mouse... the only solution is
  to switch off manually hitting and holding the power button), other
  times the machine does not wakes up from suspension mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 29 10:53:59 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-24 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  leoca  1913 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-24 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 20KQ000EBR
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/14/2018
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0PET42W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KQ000EBR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.19
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480:
  dmi.product.family: ThinkPad E480
  dmi.product.name: 20KQ000EBR
  dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480
  dmi.product.version: ThinkPad E480
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+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 1971075] Re: external monitor vga port with internal intel graphic not working with ubuntu 20.04 wayland

[Jerry Salfian]

Still confuse on how to fix this :

Bug #1971075
External monitor vga port with internal intel graphic not working with ubuntu 
20.04 wayland

Anyone?


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

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/linux/+question/703371

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

Title:
  external monitor vga port with internal intel graphic not working with
  ubuntu 20.04 wayland

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hello There,

  I'm using ubuntu desktop for about 12 years Using the LTS released.
  and using External monitor (Acer G195HOV) vga port connected to my laptop 
hp2540p.
  It's working good within ubuntu desktop 16.04 LTS,
  and "working for a while" after upgrade to ubuntu 20.04 LTS.
  After the kernel updated to version 5.10 the external monitor stop 
working Blank screen.

  FYI:
  Currently I'm using ubuntu 20.04 with kernel 5.15.

  jerry@hp-2540p:~$ hostnamectl
 Static hostname: hp-2540p
   Icon name: computer-laptop
 Chassis: laptop
  Machine ID: de4b56ef6180e8fc7e641c9d5fddb479
 Boot ID: fb02c732e3cf4de2bd716259ecfdee56
Operating System: Ubuntu 20.04.4 LTS
  Kernel: Linux 5.15.0-17-generic
Architecture: x86-64

  jerry@hp-2540p:~$ echo $XDG_SESSION_TYPE
  wayland

  
  jerry@hp-2540p:~$ sudo lspci -v
  [sudo] password for jerry: 
  00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
Subsystem: Hewlett-Packard Company Core Processor DRAM Controller
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=0c 

  00:02.0 VGA compatible controller: Intel Corporation Core Processor 
Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller])
DeviceName: 32
Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller
Flags: bus master, fast devsel, latency 0, IRQ 29
Memory at d000 (64-bit, non-prefetchable) [size=4M]
Memory at c000 (64-bit, prefetchable) [size=256M]
I/O ports at 5058 [size=8]
Expansion ROM at 000c [virtual] [disabled] [size=128K]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
Kernel modules: i915

  00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series 
Chipset HECI Controller (rev 06)
Subsystem: Hewlett-Packard Company 5 Series/3400 Series Chipset HECI 
Controller
Flags: bus master, fast devsel, latency 0, IRQ 30
Memory at d4724000 (64-bit, non-prefetchable) [size=16]
Capabilities: [50] Power Management version 3
Capabilities: [8c] MSI: Enable+ Count=1/1 Maskable- 64bit+
Kernel driver in use: mei_me
Kernel modules: mei_me

  00:16.3 Serial controller: Intel Corporation 5 Series/3400 Series Chipset KT 
Controller (rev 06) (prog-if 02 [16550])
Subsystem: Hewlett-Packard Company 5 Series/3400 Series Chipset KT 
Controller
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 17
I/O ports at 5050 [size=8]
Memory at d472b000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
Kernel driver in use: serial

  00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network 
Connection (rev 05)
Subsystem: Hewlett-Packard Company 82577LM Gigabit Network Connection
Flags: bus master, fast devsel, latency 0, IRQ 27
Memory at d470 (32-bit, non-prefetchable) [size=128K]
Memory at d472a000 (32-bit, non-prefetchable) [size=4K]
I/O ports at 5020 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] PCI Advanced Features
Kernel driver in use: e1000e
Kernel modules: e1000e

  00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 
Enhanced Host Controller (rev 05) (prog-if 20 [EHCI])
Subsystem: Hewlett-Packard Company 5 Series/3400 Series Chipset USB2 
Enhanced Host Controller
Flags: bus master, medium devsel, latency 0, IRQ 16
Memory at d4729000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCI Advanced Features
Kernel driver in use: ehci-pci

  00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio (rev 05)
Subsystem: 

[Kernel-packages] [Bug 1961338] Re: Disable unprivileged BPF by default

[Ubuntu Kernel Bot]

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

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!

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

Title:
  Disable unprivileged BPF by default

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Unprivileged users have access to BPF, allowing them to execute code in the 
kernel under their control. Though restricted and verified, a lot of security 
issues have been uncovered over the years, indicating that it should be 
disabled by default in order to protect our users.

  Admins can reenable that access or give CAP_BPF to programs if needed.

  [Test case]
  A qa-regression-testing testcase has been added that checks for the ability 
to load BPF programs under different circumstances.

  [Potential regression]
  Users who rely on unprivileged BPF access will need to change the setting or 
give CAP_BPF to their programs. Also, sysctl and bpf code might be affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961338/+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 1853306] Re: [22.04 FEAT] Enhanced Interpretation for PCI Functions on s390x - kernel part

[Frank Heimes]

This is now incl. in linux-generic | 5.19.0.18.18 | kinetic-proposed
hence updating the status to Fix Committed.

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

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

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

Title:
  [22.04 FEAT] Enhanced Interpretation for PCI Functions on s390x -
  kernel part

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  The PCI Passthrough implementation is based on intercepting PCI I/O 
instructions which leads to a reduced I/O performance compared to execution of 
PCI instructions in LPAR. 
  For improved performance the interpretive execution of the PCI store and PCI 
load instructions get enabled. 
  Further improvement is achieved by enabling the Adapter-Event-Notification

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1853306/+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 1639924] Re: Kernel livepatch support for for s390x

[Frank Heimes]

Everything regarding kernel is incl. in linux-generic 5.19.0-17.17
(meanwhile overruled by 5.19.0.18.18) and is with that in kinetic-
proposed, hence updating the status to Fix Committed - for kinetic.

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

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

Title:
  Kernel livepatch support for for s390x

Status in Ubuntu on IBM z Systems:
  Triaged
Status in gcc-11 package in Ubuntu:
  Fix Released
Status in kpatch package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in gcc-11 source package in Jammy:
  Fix Released
Status in kpatch source package in Jammy:
  New
Status in linux source package in Jammy:
  New
Status in gcc-11 source package in Kinetic:
  Fix Released
Status in kpatch source package in Kinetic:
  New
Status in linux source package in Kinetic:
  Fix Committed

Bug description:
  Kernel live-patch is afaik fully upstream and available for 'all' platforms 
(incl. s390x).
  But the kpatch-build tool does only support amd64 as of today.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1639924/+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 1959542] Re: [22.10 FEAT] [IO2201] Independent Usage of Secondary Physical Function

[Frank Heimes]

This is now incl. in linux-generic | 5.19.0.18.18 | kinetic-proposed
hence updating the status to Fix Committed.

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

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

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

Title:
  [22.10 FEAT] [IO2201] Independent Usage of Secondary Physical Function

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Title: Independent Usage of Secondary Physical Function"

  Description:
  "This feature adds the ability for a Linux running in LPAR to use the 
Physical Function (PF) associated with the second port of a ConnectX-5/6 card 
independent of that of the first port.
  Prior to this feature, if the secondary PF was attached to an LPAR without 
also attaching the primary PF, no PCI function would be visible in Linux. The 
function would instead remain
  in a hidden and disabled state. Conversely it has always been possible to use 
the primary PF without attaching the secondary PF. This existing behavior is 
confusing and needlessly
  restricts flexible usage of these powerful network cards. The new behavior of 
allowing independent usage is also in accordance with the PCI SR-IOV 
specification which explicitly
  defines the dependencies between PCI functions in the Dependency Link field 
which is still honored and for ConnectX-5/6 cards allows this independent 
usage."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959542/+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 1959940] Re: [22.10 FEAT] KVM: Secure Execution guest dump encryption with customer keys - kernel part

[Frank Heimes]

This is incl. in linux-generic 5.19.0-17.17 (which got overruled by
5.19.0.18.18) and is with that in kinetic-proposed, hence updating the
status to Fix Committed.

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

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

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

Title:
  [22.10 FEAT] KVM: Secure Execution guest dump encryption with customer
  keys - kernel part

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  KVM: Secure Execution guest dump encryption with customer keys -
  kernel part

  Description:
  Hypervisor-initiated dumps for Secure Execution guests are not helpful 
because memory and CPU state is encrypted by a transient key only available to 
the Ultravisor.  Workload owners can still configure kdump in order to obtain 
kernel crash infomation, but there are situation where kdump doesn't work. In 
such situations problem determination is severely impeded. This feature will 
implement dumps created in a way that can only be decrypted by the owner of the 
guest image and be used for problem determination.

  Request Type: Kernel - Enhancement from IBM
  Upstream Acceptance: In Progress
  Code Contribution: IBM code

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959940/+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 1959890] Re: [22.04 FEAT] Deactivitate CONFIG_QETH_OSX kernel config option

[Frank Heimes]

This is incl. in linux-generic 5.19.0-16.16 (meanwhile overruled by
5.19.0.18.18) and is with that in kinetic-proposed, hence updating the
status to Fix Committed.


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

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

Title:
  [22.04 FEAT] Deactivitate  CONFIG_QETH_OSX kernel config option

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed

Bug description:
  Deactivitate CONFIG_QETH_OSX by dropping this kernel config option

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959890/+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 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all

[Chris Chiu]

Got it. Just google for the UX3402ZA, it supports multi-dimensional
audio and may indicate the it needs some extra settings for the
speakers. The fixup ALC289_FIXUP_ASUS_GA401 may be useful. Could you
help try my test kernel debian and update the result for me?

https://people.canonical.com/~mschiu77/lp1981433/

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

Title:
  [Asus Zenbook UX3402ZA] Sound doesn't work at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sound/speakers don't work at all on Asus Zenbook 14 OLED and other
  similar models with Realtek ALC294.

  No solution works. Audio is not muted, tried adding snd-hda arguments
  - no dice.

  This has been reported numerous times, when will a fix finally be
  rolled out?!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1730 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 12 13:57:05 2022
  InstallationDate: Installed on 2022-07-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX3402ZA.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX3402ZA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.5
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku:
  dmi.product.family: Zenbook
  dmi.product.name: Zenbook UX3402ZA_UX3402ZA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981433/+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