[Kernel-packages] [Bug 1956561] Re: 5.15 / 5.19 kernel selftest srv6_end_dt46_l3vpn_test.sh failure (SRv6 VPN connectivity test)

2023-12-27 Thread Po-Hsu Lin
This issue has gone on Jammy+, but still visible on Focal 5.15 variants.

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

Title:
  5.15 / 5.19 kernel selftest srv6_end_dt46_l3vpn_test.sh failure (SRv6
  VPN connectivity test)

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Confirmed
Status in linux source package in Kinetic:
  Won't Fix

Bug description:
  Kernel selftest srv6_end_dt46_l3vpn_test.sh reports the following
  error (it seems to be an upstream issue):

  # ###
  # TEST SECTION: SRv6 VPN connectivity test among hosts in the same tenant
  # ###
  #
  # TEST: IPv6 Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100)[ OK ]
  #
  # TEST: IPv4 Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100)[FAIL]
  #
  # TEST: IPv6 Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100)[ OK ]
  #
  # TEST: IPv4 Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100)[FAIL]
  #
  # TEST: IPv6 Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200)[ OK ]
  #
  # TEST: IPv4 Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200)[FAIL]
  #
  # TEST: IPv6 Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200)[ OK ]
  #
  # TEST: IPv4 Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200)[FAIL]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1956561/+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 1956562] Re: 5.15 kernel selftest srv6_end_dt4_l3vpn_test.sh failure

2023-12-27 Thread Po-Hsu Lin
This issue has gone on Jammy+, but still visible on Focal 5.15 variants.

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

Title:
  5.15 kernel selftest srv6_end_dt4_l3vpn_test.sh failure

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Confirmed
Status in linux source package in Kinetic:
  Won't Fix

Bug description:
  Script srv6_end_dt4_l3vpn_test.sh reports the following failure
  (upstream issue).

  With Jammy 5.15:
   # ###
   # TEST SECTION: IPv6 routers connectivity test
   # ###
   #
   #  TEST: Routers connectivity: rt-1 -> rt-2   [FAIL]
   #
   #  TEST: Routers connectivity: rt-2 -> rt-1   [FAIL]
   # ###
   # TEST SECTION: SRv6 VPN connectivity test among hosts in the same tenant
   # ###
   #
   #  TEST: Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100)  [FAIL]
   #
   #  TEST: Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100)  [FAIL]
   #
   #  TEST: Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200)  [FAIL]
   #
   #  TEST: Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200)  [FAIL]
   #

  With Kinetic 5.19:
   # ###
   # TEST SECTION: IPv6 routers connectivity test
   # ###
   # 
   #  TEST: Routers connectivity: rt-1 -> rt-2   [FAIL]
   # 
   #  TEST: Routers connectivity: rt-2 -> rt-1   [ OK ]
  # 
   # TEST SECTION: SRv6 VPN connectivity test among hosts in the same tenant
   # ###
   #
   #  TEST: Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100)  [FAIL]
   #
   #  TEST: Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100)  [FAIL]
   #
   #  TEST: Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200)  [FAIL]
   #
   #  TEST: Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200)  [FAIL]
   #

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1956562/+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 2042500] Re: Fix after-suspend-mediacard/sdhc-insert test failed

2023-12-27 Thread AceLan Kao
** Changed in: linux (Ubuntu Jammy)
   Status: In Progress => Invalid

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

Title:
  Fix after-suspend-mediacard/sdhc-insert test failed

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.1 source package in Noble:
  Invalid
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [Impact]
  checkbox test case, after-suspend-mediacard/sdhc-insert, failed.

  [Fix]
  Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability
  for suspend/resume"") reverted saving and restoring of ASPM L1 Substates
  due to a regression that caused resume from suspend to fail on certain
  systems. However, we never added this capability back and this is now
  causing systems fail to enter low power CPU states, drawing more power
  from the battery.
  
  The original revert mentioned that we restore L1 PM substate configuration
  even though ASPM L1 may already be enabled. This is due the fact that
  the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state().
  
  Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4
  more closely by:
  
  1) Do not restore ASPM configuration in pci_restore_pcie_state() but
 do that after PCIe capability is restored in pci_restore_aspm_state()
 following PCIe r6.0, sec 5.5.4.
  
  2) ASPM is first enabled on the upstream component and then downstream
 (this is already forced by the parent-child ordering of Linux
 Device Power Management framework).
  
  3) Program ASPM L1 PM substate configuration before L1 enables.
  
  4) Program ASPM L1 PM substate enables last after rest of the fields
 in the capability are programmed.
  
  5) Add denylist that skips restoring on the ASUS and TUXEDO systems
 where these regressions happened, just in case. For the TUXEDO case
 we only skip restore if the BIOS is involved in system suspend
 (that's forcing "mem_sleep=deep" in the command line). This is to
 avoid possible power regression when the default suspend to idle is
 used, and at the same time make sure the devices continue working
 after resume when the BIOS is involved.

  [Test Case]
  1. suspend and resume.
  2. check if the error appears in dmesg
  ~~~
   pcieport :00:1c.0: pciehp: Slot(5): Card not present
   rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device 
inaccessible
   rtsx_pci :05:00.0: Unable to change power state from D3cold to D0, 
device inaccessible
  ~~~

  [where the issue could happen]
  low, the patch works well on the reported malfunctioned ASUS platform too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042500/+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 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu

2023-12-27 Thread Seth Arnold
Microsoft has implemented an IPSec stack:
https://learn.microsoft.com/en-us/windows/win32/fwp/ipsec-
configuration#how-to-use-wfp-to-configure-ipsec-policies

"The Microsoft implementation of IPsec uses Windows Filtering Platform
to setup IPsec policies."

This page is a bit thin on which applications to open, which buttons to
click, etc, but they do have IPSec available in their ecosystem.

Microsoft has implemented LT2P: https://learn.microsoft.com/en-
US/troubleshoot/windows-server/networking/configure-l2tp-ipsec-server-
behind-nat-t-device

"This article describes how to configure a L2TP/IPsec server behind a
NAT-T device."

A third party has implemented OpenVPN for Windows:
https://openvpn.net/client/client-connect-vpn-for-windows/

"For Windows 7, 8, 10, and 11.
Note: Windows 7 and 8 are not officially supported anymore."

A third party has implemented Wireguard for Windows:
https://www.wireguard.com/install/#windows-7-81-10-11-2008r2-2012r2-2016-2019-2022

" Windows [7, 8.1, 10, 11, 2008R2, 2012R2, 2016, 2019, 2022 – v0.5.3]"

Selecting a replacement requires some effort on the part of the network
administrator with knowledge of what features and operating systems they
need for their environment.

I think pptp is bad enough that removing it makes sense.

On the other hand, we still have telnet, and there's appropriate uses
and inappropriate uses, and maybe this falls into the same category of
compatibility software where users should expect a significant reduction
in security if it is used.

Thanks

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

Title:
  RM: Remove dangerously insecure MPPE PPTP from Ubuntu

Status in linux package in Ubuntu:
  New
Status in network-manager-pptp package in Ubuntu:
  New
Status in pptp-linux package in Ubuntu:
  New
Status in pptpd package in Ubuntu:
  Incomplete

Bug description:
  Remove dangerously insecure MPPE PPTP from Ubuntu

  https://pptpclient.sourceforge.net/protocol-security.phtml

  It has been dead for over 20 years now.

  IPSec OpenVPN Strongswan are much better alternatives.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041751/+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 2047590] [NEW] 6.5.0-14 kernel will not boot

2023-12-27 Thread Geoff123
Public bug reported:

The computer hangs during boot with kernel 6.5.0-14-generic.  However,
kernel 6.2.0-39-generic works fine.  This was a recent upgrade from an
earlier Ubuntu version.

I see on the screen:
Loading Linux 6.5.014-generic...
Loading initial ramdisk ...

I waited several minutes before pushing the reset button.

Other system information should be attached.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-14-generic 6.5.0-14.14
ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gsking 1759 F wireplumber
 /dev/snd/controlC1:  gsking 1759 F wireplumber
 /dev/snd/seq:gsking 1745 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 27 16:45:06 2023
InstallationDate: Installed on 2023-07-03 (177 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
IwConfig:
 lono wireless extensions.
 
 enp3s0no wireless extensions.
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=5a06426c-3de2-4755-be67-fdc02ccff00d ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-6.2.0-39-generic N/A
 linux-backports-modules-6.2.0-39-generic  N/A
 linux-firmware20230919.git3672ccab-0ubuntu2.4
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-12-05 (22 days ago)
dmi.bios.date: 08/10/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F11
dmi.board.name: P55A-UD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
dmi.product.name: P55A-UD3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug mantic

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

Title:
  6.5.0-14 kernel will not boot

Status in linux package in Ubuntu:
  New

Bug description:
  The computer hangs during boot with kernel 6.5.0-14-generic.  However,
  kernel 6.2.0-39-generic works fine.  This was a recent upgrade from an
  earlier Ubuntu version.

  I see on the screen:
  Loading Linux 6.5.014-generic...
  Loading initial ramdisk ...

  I waited several minutes before pushing the reset button.

  Other system information should be attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14
  ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gsking 1759 F wireplumber
   /dev/snd/controlC1:  gsking 1759 F wireplumber
   /dev/snd/seq:gsking 1745 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 27 16:45:06 2023
  InstallationDate: Installed on 2023-07-03 (177 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=5a06426c-3de2-4755-be67-fdc02ccff00d ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-39-generic N/A
   linux-backports-modules-6.2.0-39-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.4
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-12-05 (22 days ago)
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11
  dmi.board.name: P55A-UD3
  dmi.b

[Kernel-packages] [Bug 2047518] Re: Fix BCM57416 lost after resume

2023-12-27 Thread AaronMa
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: New => In Progress

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

Title:
  Fix BCM57416 lost after resume

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

Bug description:
  [Impact]
  BCM57416 is lost after resume.
  Error log:
  [ 1261.429834] bnxt_en :82:00.1 enp130s0f1np1: hwrm req_type 0x50 seq id 
0x125d error 0x4
  [ 1261.429843] bnxt_en :82:00.1 enp130s0f1np1: hwrm_ring_alloc type 1 
failed. rc:ffe4 err:4
  [ 1261.429846] bnxt_en :82:00.1 enp130s0f1np1: hwrm ring alloc failure 
rc: fffb
  [ 1261.437389] bnxt_en :82:00.1 enp130s0f1np1: bnxt_init_nic err: fffb

  [Fix]
  Clear the reservations in driver after reset the ethernet card.

  [Test]
  Tested on hardware, after 10 times of suspend/resume, bnxt ethernet works 
fine.

  [Where problems could occur]
  It may break broadcom bnxt driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2047518/+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 2047518] [NEW] Fix BCM57416 lost after resume

2023-12-27 Thread AaronMa
Public bug reported:

[Impact]
BCM57416 is lost after resume.
Error log:
[ 1261.429834] bnxt_en :82:00.1 enp130s0f1np1: hwrm req_type 0x50 seq id 
0x125d error 0x4
[ 1261.429843] bnxt_en :82:00.1 enp130s0f1np1: hwrm_ring_alloc type 1 
failed. rc:ffe4 err:4
[ 1261.429846] bnxt_en :82:00.1 enp130s0f1np1: hwrm ring alloc failure rc: 
fffb
[ 1261.437389] bnxt_en :82:00.1 enp130s0f1np1: bnxt_init_nic err: fffb

[Fix]
Clear the reservations in driver after reset the ethernet card.

[Test]
Tested on hardware, after 10 times of suspend/resume, bnxt ethernet works fine.

[Where problems could occur]
It may break broadcom bnxt driver.

** Affects: hwe-next
 Importance: High
 Assignee: AaronMa (mapengyu)
 Status: In Progress

** Affects: linux (Ubuntu)
 Importance: High
 Status: In Progress

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

** Affects: linux (Ubuntu Jammy)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem-6.5 (Ubuntu Jammy)
 Importance: High
 Status: New

** Affects: linux (Ubuntu Mantic)
 Importance: High
 Status: In Progress

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

** Affects: linux (Ubuntu Noble)
 Importance: High
 Status: In Progress

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


** Tags: oem-priority originate-from-2045608 sutton

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

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

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

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

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

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

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

** Tags added: oem-priority originate-from-2045608 sutton

** Changed in: hwe-next
 Assignee: (unassigned) => AaronMa (mapengyu)

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

** Changed in: hwe-next
   Importance: Undecided => High

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

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

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

** Changed in: linux-oem-6.5 (Ubuntu Mantic)
   Status: New => Invalid

** Changed in: linux-oem-6.5 (Ubuntu Noble)
   Status: New => Invalid

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

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

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

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

Title:
  Fix BCM57416 lost after resume

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

Bug description:
  [Impact]
  BCM57416 is lost after resume.
  Error log:
  [ 1261.429834] bnxt_en :82:00.1 enp130s0f1np1: hwrm req_type 0x50 seq id 
0x125d error 0x4
  [ 1261.429843] bnxt_en :82:00.1 enp130s0f1np1: hwrm_ring_alloc type 1 
failed. rc:ffe4 err:4
  [ 1261.429846] bnxt_en :82:00.1 enp130s0f1np1: hwrm ring alloc failure 
rc: fffb
  [ 1261.437389] bnxt_en :82:00.1 enp130s0f1np1: bnxt_init_nic err: fffb

  [Fix]
  Clear the reservations in driver after reset the ethernet card.

  [Test]
  Tested on hardware, after 10 times of suspend/resume, bnxt ethernet works 
fine.

  [Where problems could occur]
  It may break broadcom bnxt driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2047518/+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 2047504] Re: Mute/mic LEDs and speaker no function on some HP platforms

2023-12-27 Thread Andy Chi
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: Confirmed => Fix Committed

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

Title:
  Mute/mic LEDs and speaker no function on some HP platforms

Status in OEM Priority Project:
  Fix Committed
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  The mic mute/audio mute LEDS and speaker are not work on some HP platforms.

  [Fix]
  It needs the specific quirk for the hardware layout.
  Thus, add the quirks to make it works.

  [Test]
  After applying the quirk, the audio/mic mute LEDs and speaker are working 
good.
  Applied on oem-6.5 and it works fine.

  [Where problems could occur]
  If HP ships the different system boards design with the same subsystem ID of 
audio codec which is using different GPIO pins (different layout), then the 
quirk will not work (LEDs will not work when muting audio-output or microphone).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2047504/+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 2047504] Re: Mute/mic LEDs and speaker no function on some HP platforms

2023-12-27 Thread Anthony Wong
** Changed in: linux-oem-6.5 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Mute/mic LEDs and speaker no function on some HP platforms

Status in OEM Priority Project:
  Fix Committed
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Confirmed

Bug description:
  [Impact]
  The mic mute/audio mute LEDS and speaker are not work on some HP platforms.

  [Fix]
  It needs the specific quirk for the hardware layout.
  Thus, add the quirks to make it works.

  [Test]
  After applying the quirk, the audio/mic mute LEDs and speaker are working 
good.
  Applied on oem-6.5 and it works fine.

  [Where problems could occur]
  If HP ships the different system boards design with the same subsystem ID of 
audio codec which is using different GPIO pins (different layout), then the 
quirk will not work (LEDs will not work when muting audio-output or microphone).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2047504/+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 2047504] Re: Mute/mic LEDs and speaker no function on some HP platforms

2023-12-27 Thread Andy Chi
SRU sent:
https://kernel.ubuntu.com/gitea/kernel/jammy-linux-oem/pulls/123

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

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

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
 Assignee: (unassigned) => Andy Chi (andch)

** Changed in: oem-priority
   Status: New => In Progress

** Changed in: oem-priority
   Status: In Progress => Fix Committed

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
   Status: In Progress => Confirmed

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

Title:
  Mute/mic LEDs and speaker no function on some HP platforms

Status in OEM Priority Project:
  Fix Committed
Status in linux-oem-6.5 package in Ubuntu:
  Confirmed
Status in linux-oem-6.5 source package in Jammy:
  Confirmed

Bug description:
  [Impact]
  The mic mute/audio mute LEDS and speaker are not work on some HP platforms.

  [Fix]
  It needs the specific quirk for the hardware layout.
  Thus, add the quirks to make it works.

  [Test]
  After applying the quirk, the audio/mic mute LEDs and speaker are working 
good.
  Applied on oem-6.5 and it works fine.

  [Where problems could occur]
  If HP ships the different system boards design with the same subsystem ID of 
audio codec which is using different GPIO pins (different layout), then the 
quirk will not work (LEDs will not work when muting audio-output or microphone).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2047504/+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 2000030] Re: Soundwire support for the Intel RPL Gen 0C40/0C11 platforms

2023-12-27 Thread You-Sheng Yang
v6.2-rc4 or newer has:
* b25a31b463391 ASoC: Intel: soc-acpi: add configuration for variant of 0C11 
product
* 896c3dc21f1e8 ASoC: Intel: soc-acpi: add configuration for variant of 0C40 
product

Identical to what were proposed in comment #3.

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

Title:
  Soundwire support for the Intel RPL Gen 0C40/0C11 platforms

Status in firmware-sof package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  Missing support for two additional product model of Intel RPL Gen
  Soundwire.

  [Fix]

  Two additional commits merged in upstream sof development repository
  on GitHub.

  [Test Case]

  Apply the two changes along with an alsa ucm conf fix, then perform audio
  automatic/manual checkbox tests.

  [Where problems could occur]

  New hardware. No known issue so far, but might have minor issues in
  the future.

  [Other Info]

  Nominated for U/L/OEM-6.0/OEM-6.1. Depending on fixes from bug
  1997944.

  == original bug report ==

  This is a follow-up to bug 1997944 that supports more RPL gen
  platforms.

  Staging fixes:
  * 
https://github.com/thesofproject/linux/commit/9aacc6f5c422b98ef8ea98d190a8f6db9aa447c4
 ("ASoC: Intel: soc-acpi: add configuration for variant of 0C40 product")
  * 
https://github.com/thesofproject/linux/commit/e3707e4dd275bc731f6ed4067a2694534675ca52
 ("ASoC: Intel: soc-acpi: add configuration for variant of 0C11 product")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/230/+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 2047504] Re: Mute/mic LEDs and speaker no function on some HP platforms

2023-12-27 Thread Andy Chi
** Tags added: oem-priority originate-from-2047209 stella

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

Title:
  Mute/mic LEDs and speaker no function on some HP platforms

Status in OEM Priority Project:
  New
Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux-oem-6.5 source package in Jammy:
  New

Bug description:
  [Impact]
  The mic mute/audio mute LEDS and speaker are not work on some HP platforms.

  [Fix]
  It needs the specific quirk for the hardware layout.
  Thus, add the quirks to make it works.

  [Test]
  After applying the quirk, the audio/mic mute LEDs and speaker are working 
good.
  Applied on oem-6.5 and it works fine.

  [Where problems could occur]
  If HP ships the different system boards design with the same subsystem ID of 
audio codec which is using different GPIO pins (different layout), then the 
quirk will not work (LEDs will not work when muting audio-output or microphone).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2047504/+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 2047504] [NEW] Mute/mic LEDs and speaker no function on some HP platforms

2023-12-27 Thread Andy Chi
Public bug reported:

[Impact]
The mic mute/audio mute LEDS and speaker are not work on some HP platforms.

[Fix]
It needs the specific quirk for the hardware layout.
Thus, add the quirks to make it works.

[Test]
After applying the quirk, the audio/mic mute LEDs and speaker are working good.
Applied on oem-6.5 and it works fine.

[Where problems could occur]
If HP ships the different system boards design with the same subsystem ID of 
audio codec which is using different GPIO pins (different layout), then the 
quirk will not work (LEDs will not work when muting audio-output or microphone).

** Affects: linux-oem-6.5 (Ubuntu)
 Importance: Medium
 Assignee: Andy Chi (andch)
 Status: New

** Affects: linux-oem-6.5 (Ubuntu Jammy)
 Importance: Medium
 Assignee: Andy Chi (andch)
 Status: New

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

** Package changed: linux-oem-6.1 (Ubuntu) => linux-oem-6.5 (Ubuntu)

** Changed in: linux-oem-6.5 (Ubuntu)
   Importance: Undecided => Medium

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

** Changed in: linux-oem-6.5 (Ubuntu)
 Assignee: (unassigned) => Andy Chi (andch)

** Changed in: linux-oem-6.5 (Ubuntu Jammy)
 Assignee: (unassigned) => Andy Chi (andch)

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

Title:
  Mute/mic LEDs and speaker no function on some HP platforms

Status in linux-oem-6.5 package in Ubuntu:
  New
Status in linux-oem-6.5 source package in Jammy:
  New

Bug description:
  [Impact]
  The mic mute/audio mute LEDS and speaker are not work on some HP platforms.

  [Fix]
  It needs the specific quirk for the hardware layout.
  Thus, add the quirks to make it works.

  [Test]
  After applying the quirk, the audio/mic mute LEDs and speaker are working 
good.
  Applied on oem-6.5 and it works fine.

  [Where problems could occur]
  If HP ships the different system boards design with the same subsystem ID of 
audio codec which is using different GPIO pins (different layout), then the 
quirk will not work (LEDs will not work when muting audio-output or microphone).

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