from:"Wei"

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

** Changed in: linux-hwe-6.8 (Ubuntu Noble)
   Status: New => Invalid

** Changed in: linux-hwe-6.8 (Ubuntu Oracular)
   Status: New => Invalid

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

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

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

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

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

** Changed in: linux-oem-6.11 (Ubuntu Oracular)
   Status: New => Invalid

** Changed in: linux (Ubuntu Noble)
 Assignee: (unassigned) => En-Wei Wu (rickywu)

** Changed in: linux (Ubuntu Oracular)
 Assignee: (unassigned) => En-Wei Wu (rickywu)

** Changed in: linux-hwe-6.8 (Ubuntu Jammy)
     Assignee: (unassigned) => En-Wei Wu (rickywu)

** Changed in: linux-oem-6.11 (Ubuntu Noble)
 Assignee: (unassigned) => En-Wei Wu (rickywu)

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

Title:
  rtw89: Support hardware rfkill

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-6.8 package in Ubuntu:
  Invalid
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-hwe-6.8 source package in Jammy:
  In Progress
Status in linux-oem-6.11 source package in Jammy:
  Invalid
Status in linux source package in Noble:
  In Progress
Status in linux-hwe-6.8 source package in Noble:
  Invalid
Status in linux-oem-6.11 source package in Noble:
  In Progress
Status in linux source package in Oracular:
  In Progress
Status in linux-hwe-6.8 source package in Oracular:
  Invalid
Status in linux-oem-6.11 source package in Oracular:
  Invalid

Bug description:
  [Impact]
  With RTL8851BE and "Control WLAN radio" (in Dell BIOS setting) on, wifi 
function is not be disabled when we plug in the Ethernet cable. The issue is 
because the rtw89 driver doesn't have the hardware rfkill mechanism.

  [Fix]
  Backport the Realtek patch in linux-next:

  https://lore.kernel.org/linux-
  
wireless/20240724052626.12774-1-pks...@realtek.com/T/#m1361ad1d6125d64976677fea4ba2e3aff219d1ad

  [Test Plan]
  1. Enable Control WLAN radio in BIOS setting
  2. Boot into OS
  2. Plug in Ethernet cable.
  3. Check if the WiFi function being HW blocked

  [Where problems could occur]
  May disrupt the software rfkill.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2077384/+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 2077384] Re: rtw89: Support hardware rfkill

** Tags added: civet-cat oem-priority originate-from-2058176

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

Title:
  rtw89: Support hardware rfkill

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-hwe-6.8 package in Ubuntu:
  New
Status in linux-oem-6.11 package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-hwe-6.8 source package in Jammy:
  New
Status in linux-oem-6.11 source package in Jammy:
  New
Status in linux source package in Noble:
  New
Status in linux-hwe-6.8 source package in Noble:
  New
Status in linux-oem-6.11 source package in Noble:
  New
Status in linux source package in Oracular:
  New
Status in linux-hwe-6.8 source package in Oracular:
  New
Status in linux-oem-6.11 source package in Oracular:
  New

Bug description:
  [Impact]
  With RTL8851BE and "Control WLAN radio" (in Dell BIOS setting) on, wifi 
function is not be disabled when we plug in the Ethernet cable. The issue is 
because the rtw89 driver doesn't have the hardware rfkill mechanism.

  [Fix]
  Backport the Realtek patch in linux-next:

  https://lore.kernel.org/linux-
  
wireless/20240724052626.12774-1-pks...@realtek.com/T/#m1361ad1d6125d64976677fea4ba2e3aff219d1ad

  [Test Plan]
  1. Enable Control WLAN radio in BIOS setting
  2. Boot into OS
  2. Plug in Ethernet cable.
  3. Check if the WiFi function being HW blocked

  [Where problems could occur]
  May disrupt the software rfkill.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2077384/+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 2077384] [NEW] rtw89: Support hardware rfkill

Public bug reported:

[Impact]
With RTL8851BE and "Control WLAN radio" (in Dell BIOS setting) on, wifi 
function is not be disabled when we plug in the Ethernet cable. The issue is 
because the rtw89 driver doesn't have the hardware rfkill mechanism.

[Fix]
Backport the Realtek patch in linux-next:

https://lore.kernel.org/linux-
wireless/20240724052626.12774-1-pks...@realtek.com/T/#m1361ad1d6125d64976677fea4ba2e3aff219d1ad

[Test Plan]
1. Enable Control WLAN radio in BIOS setting
2. Boot into OS
2. Plug in Ethernet cable.
3. Check if the WiFi function being HW blocked

[Where problems could occur]
May disrupt the software rfkill.

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

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

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

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

** Affects: linux-hwe-6.8 (Ubuntu Jammy)
 Importance: Undecided
 Status: New

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Also affects: linux-oem-6.11 (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/2077384

Title:
  rtw89: Support hardware rfkill

Status in linux package in Ubuntu:
  New
Status in linux-hwe-6.8 package in Ubuntu:
  New
Status in linux-oem-6.11 package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-hwe-6.8 source package in Jammy:
  New
Status in linux-oem-6.11 source package in Jammy:
  New
Status in linux source package in Noble:
  New
Status in linux-hwe-6.8 source package in Noble:
  New
Status in linux-oem-6.11 source package in Noble:
  New
Status in linux source package in Oracular:
  New
Status in linux-hwe-6.8 source package in Oracular:
  New
Status in linux-oem-6.11 source package in Oracular:
  New

Bug description:
  [Impact]
  With RTL8851BE and "Control WLAN radio" (in Dell BIOS setting) on, wifi 
function is not be disabled when we plug in the Ethernet cable. The issue is 
because the rtw89 driver doesn't have the hardware rfkill mechanism.

  [Fix]
  Backport the Realtek patch in linux-next:

  https://lore.kernel.org/linux-
  
wireless/20240724052626.12774-1-pks...@realtek.com/T/#m1361ad1d6125d64976677fea4ba2e3aff219d1ad

  [Test Plan]
  1. Enable Control WLAN radio in BIOS setting
  2. Boot into OS
  2. Plug in Ethernet cable.
  3. Check if the WiFi function being HW blocked

  [Where problems could occur]
  May disrupt the software rfkill.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077384/+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 2076881] Re: btintel: Prevent BRI traffic crosstalking with WiFi module

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

** Tags added: originate-from-2059878

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

Title:
  btintel: Prevent BRI traffic crosstalking with WiFi module

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

Bug description:
  [Impact]
  BRI (Bluetooth Radio Interface) traffic from CNVr to CNVi was found causing
  cross talk step errors to WiFi. Therefore, Bluetooth is turned on, the WiFi
  may be disrupted by Bluetooth and thus not work reliably.

  [Fix]
  Apply the patch 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/bluetooth/btintel.c?id=c707097a446ce3d284bc9f05736dc4701d2b8168
 on noble-oem-6.11

  [Test Plan]
  1. Compile noble-oem-6.11
  2. Include Bluetooth FWs ibt-0190-0291-iml.sfi, ibt-0190-0291.ddc, 
ibt-0190-0291.sfi in /lib/firmware/intel/
  ( These FWs are not public yet. We're going to do SRU in the future once the 
FWs are landed on the upstream linux-firmrware)
  3. Include WiFi FWs bz-b0-fm-c0-92.ucode in /lib/firmware/
  ( The same. These FWs are not public yet )
  4. Boot the noble-oem-6.11 kernel
  5. Test WiFi functionality.

  [Where problems could occur]
  The patch makes use of UEFI variable. If the variable is somehow not shown in 
the ROM, there might be some error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2076881/+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 2074049] Re: please help enable more EROFS compression algorithms

2024-08-18 Thread En-Wei Wu

Hi @Gao Xiang,

Sorry about the mistake. I will send another patch to remove the last
line above:

CONFIG_EROFS_FS_ZIP_ZSTD policy<{'amd64': 'n', 'arm64': 'n', 'armhf':
'n', 'ppc64el': 'n', 'riscv64': 'n', 's390x': 'n'}>

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

Title:
  please help enable more EROFS compression algorithms

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

Bug description:
  Hi,

  Could you please enable more EROFS compression algorithms for better
  compression ratios to end users on Ubuntu?

  CONFIG_EROFS_FS_ZIP_LZMA=y  (Kernel 5.16+)
  CONFIG_EROFS_FS_ZIP_DEFLATE=y   (Kernel 6.6+)
  CONFIG_EROFS_FS_ZIP_ZSTD=y (Kernel 6.10+)

  so that users can use these algorithms directly with shipped kernels
  in addition to the default LZ4 one.

  Thanks in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074049/+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 2076861] Re: [Invalid] rtw89: Support hardware rfkill and reset IDMEM mode to prevent download firmware failure

2024-08-18 Thread En-Wei Wu

Sorry, this bug is invalid now. Please ignore it. Thanks.

** Summary changed:

- rtw89: Support hardware rfkill and reset IDMEM mode to prevent download 
firmware failure
+ [Invalid] rtw89: Support hardware rfkill and reset IDMEM mode to prevent 
download firmware failure

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

Title:
  [Invalid] rtw89: Support hardware rfkill and reset IDMEM mode to
  prevent download firmware failure

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-6.8 package in Ubuntu:
  Invalid
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-hwe-6.8 source package in Jammy:
  New
Status in linux-oem-6.11 source package in Jammy:
  Invalid
Status in linux source package in Noble:
  New
Status in linux-hwe-6.8 source package in Noble:
  Invalid
Status in linux-oem-6.11 source package in Noble:
  New
Status in linux source package in Oracular:
  In Progress
Status in linux-hwe-6.8 source package in Oracular:
  Invalid
Status in linux-oem-6.11 source package in Oracular:
  Invalid

Bug description:
  [Impact]
  There are two issues with Realtek RTL8851BE/RTL8852BE:
  Issue 1: After reboot from UEFI HTTPs boot, RTL8851BE wifi were not working 
due to the firmware download fail

  Issue 2: With RTL8851BE and "Control WLAN radio" (in BIOS setting) on,
  wifi function is not be disabled when we plug in the Ethernet cable

  [Fix]
  Apply the four Realtek patches from linux-next:

  bd4a3b10fa0e wifi: rtw89: add EVM statistics for 1SS rate
  0b38e6277aed wifi: rtw89: add support for hardware rfkill
  80fb81bb46a5 wifi: rtw89: 885xb: reset IDMEM mode to prevent download 
firmware failure
  27d90ad37771 wifi: rtw89: fix typo of rtw89_phy_ra_updata_XXX

  Link: https://lore.kernel.org/linux-
  
wireless/20240724052626.12774-1-pks...@realtek.com/T/#m20642bad88583db3ef5957b701c216d93e68c14d

  [Test Plan]
  Issue 1:
  1. Install Ubuntu image and boot into the OS，then power off system.
  2. power on SUT, press F12 to choose UEFI HTTPs Boot.
  3. wait 10 seconds and when see the available wireless networks，press 
Ctrl+Alt+Delete
  4. Boot to OS, check if the WiFi function works

  Issue 2:
  1. Enable Control WLAN radio in BIOS setting
  2. Boot into OS
  2. Plug in Ethernet cable.
  3. Check if the WiFi function being disabled

  [Where problems could occur]
  May disrupt the software rfkill.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076861/+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 2069993] Re: Panels show garbage or flickering when i915.psr2 enabled

2024-08-14 Thread En-Wei Wu

Patches for Noble is now under review:
https://lists.ubuntu.com/archives/kernel-team/2024-August/152815.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/2069993

Title:
  Panels show garbage or flickering when i915.psr2 enabled

Status in linux package in Ubuntu:
  New
Status in linux-oem-6.8 package in Ubuntu:
  Invalid
Status in linux source package in Noble:
  Confirmed
Status in linux-oem-6.8 source package in Noble:
  Fix Released

Bug description:
  SRU verification for oem-6.8-noble:

  [Impact]
  In https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2046315,
  we've cherry-picked the 8 patches from the most recent mainline kernel to 
oem-6.8
  to fix the panel flickering problem in the Dell OEM project. However,
  OEM reports that the patches have regression on 6.8.0-1006-oem.

  For now, we apply the workaround patches from oem-6.5 to fix the bug.
  In the meantime, we've reported the issue to Intel and are waiting for the 
fix.
  Once the fix is available in the mainline kernel, we'll backport the fix into
  oem-6.8 kernel and revert the workaround patches.

  Upstream bug: https://gitlab.freedesktop.org/drm/intel/-/issues/9739

  [Fix]
  Apply workaround patches from oem-6.5 to oem-6.8

  [Test Plan]
  The machines mentioned in the attachment (containing the problematic panel's 
EDID) would have flickering graphics with the linux-6.8.0-1006-oem kernel.

  The flickering graphic is gone after applying the workaround patches.

  [Where problems could occur]
  The workaround patches add some quirks that disable PSR2 on some panels. So 
far, there are 7 panels listed in the quirks (other panels used by OEM products 
are flickering-free without the patches).

  If OEM starts using other panels in the future, it's not sure that the
  panels will be flickering-free.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069993/+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 2076861] Re: rtw89: Support hardware rfkill and reset IDMEM mode to prevent download firmware failure

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

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

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

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

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

** Also affects: linux (Ubuntu Oracular)
   Importance: Undecided
 Assignee: En-Wei Wu (rickywu)
   Status: In Progress

** Also affects: linux-hwe-6.8 (Ubuntu Oracular)
   Importance: Undecided
 Assignee: En-Wei Wu (rickywu)
   Status: In Progress

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

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

** Changed in: linux-hwe-6.8 (Ubuntu Oracular)
   Status: In Progress => Invalid

** Changed in: linux-hwe-6.8 (Ubuntu Noble)
   Status: New => Invalid

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

** Changed in: linux-oem-6.11 (Ubuntu Oracular)
   Status: New => Invalid

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

Title:
  rtw89: Support hardware rfkill and reset IDMEM mode to prevent
  download firmware failure

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-6.8 package in Ubuntu:
  Invalid
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-hwe-6.8 source package in Jammy:
  New
Status in linux-oem-6.11 source package in Jammy:
  Invalid
Status in linux source package in Noble:
  New
Status in linux-hwe-6.8 source package in Noble:
  Invalid
Status in linux-oem-6.11 source package in Noble:
  New
Status in linux source package in Oracular:
  In Progress
Status in linux-hwe-6.8 source package in Oracular:
  Invalid
Status in linux-oem-6.11 source package in Oracular:
  Invalid

Bug description:
  [Impact]
  There are two issues with Realtek RTL8851BE/RTL8852BE:
  Issue 1: After reboot from UEFI HTTPs boot, RTL8851BE wifi were not working 
due to the firmware download fail

  Issue 2: With RTL8851BE and "Control WLAN radio" (in BIOS setting) on,
  wifi function is not be disabled when we plug in the Ethernet cable

  [Fix]
  Apply the four Realtek patches from linux-next:

  bd4a3b10fa0e wifi: rtw89: add EVM statistics for 1SS rate
  0b38e6277aed wifi: rtw89: add support for hardware rfkill
  80fb81bb46a5 wifi: rtw89: 885xb: reset IDMEM mode to prevent download 
firmware failure
  27d90ad37771 wifi: rtw89: fix typo of rtw89_phy_ra_updata_XXX

  Link: https://lore.kernel.org/linux-
  
wireless/20240724052626.12774-1-pks...@realtek.com/T/#m20642bad88583db3ef5957b701c216d93e68c14d

  [Test Plan]
  Issue 1:
  1. Install Ubuntu image and boot into the OS，then power off system.
  2. power on SUT, press F12 to choose UEFI HTTPs Boot.
  3. wait 10 seconds and when see the available wireless networks，press 
Ctrl+Alt+Delete
  4. Boot to OS, check if the WiFi function works

  Issue 2:
  1. Enable Control WLAN radio in BIOS setting
  2. Boot into OS
  2. Plug in Ethernet cable.
  3. Check if the WiFi function being disabled

  [Where problems could occur]
  May disrupt the software rfkill.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076861/+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 2076881] Re: btintel: Prevent BRI traffic crosstalking with WiFi module

** Description changed:

  [Impact]
  BRI (Bluetooth Radio Interface) traffic from CNVr to CNVi was found causing
  cross talk step errors to WiFi. Therefore, Bluetooth is turned on, the WiFi
  may be disrupted by Bluetooth and thus not work reliably.
  
  [Fix]
  Apply the patch 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/bluetooth/btintel.c?id=c707097a446ce3d284bc9f05736dc4701d2b8168
 on noble-oem-6.11
  
  [Test Plan]
- 1. Compile noble-oem-6.11 with config BT_INTEL_PCIE on
+ 1. Compile noble-oem-6.11
  2. Include Bluetooth FWs ibt-0190-0291-iml.sfi, ibt-0190-0291.ddc, 
ibt-0190-0291.sfi in /lib/firmware/intel/
  ( These FWs are not public yet. We're going to do SRU in the future once the 
FWs are landed on the upstream linux-firmrware)
  3. Include WiFi FWs bz-b0-fm-c0-92.ucode in /lib/firmware/
  ( The same. These FWs are not public yet )
  4. Boot the noble-oem-6.11 kernel
  5. Test WiFi functionality.
  
  [Where problems could occur]
  The patch makes use of UEFI variable. If the variable is somehow not shown in 
the ROM, there might be some error.

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

Title:
  btintel: Prevent BRI traffic crosstalking with WiFi module

Status in linux package in Ubuntu:
  New
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in linux source package in Noble:
  Invalid
Status in linux-oem-6.11 source package in Noble:
  New
Status in linux source package in Oracular:
  New
Status in linux-oem-6.11 source package in Oracular:
  Invalid

Bug description:
  [Impact]
  BRI (Bluetooth Radio Interface) traffic from CNVr to CNVi was found causing
  cross talk step errors to WiFi. Therefore, Bluetooth is turned on, the WiFi
  may be disrupted by Bluetooth and thus not work reliably.

  [Fix]
  Apply the patch 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/bluetooth/btintel.c?id=c707097a446ce3d284bc9f05736dc4701d2b8168
 on noble-oem-6.11

  [Test Plan]
  1. Compile noble-oem-6.11
  2. Include Bluetooth FWs ibt-0190-0291-iml.sfi, ibt-0190-0291.ddc, 
ibt-0190-0291.sfi in /lib/firmware/intel/
  ( These FWs are not public yet. We're going to do SRU in the future once the 
FWs are landed on the upstream linux-firmrware)
  3. Include WiFi FWs bz-b0-fm-c0-92.ucode in /lib/firmware/
  ( The same. These FWs are not public yet )
  4. Boot the noble-oem-6.11 kernel
  5. Test WiFi functionality.

  [Where problems could occur]
  The patch makes use of UEFI variable. If the variable is somehow not shown in 
the ROM, there might be some error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076881/+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 2076881] Re: btintel: Prevent BRI traffic crosstalking with WiFi module

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

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

** Also affects: linux-oem-6.11 (Ubuntu Oracular)
   Importance: Undecided
 Assignee: En-Wei Wu (rickywu)
   Status: New

** Changed in: linux-oem-6.11 (Ubuntu Oracular)
   Status: New => Invalid

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

** Changed in: linux (Ubuntu Noble)
 Assignee: (unassigned) => En-Wei Wu (rickywu)

** Changed in: linux (Ubuntu Oracular)
 Assignee: (unassigned) => En-Wei Wu (rickywu)

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

Title:
  btintel: Prevent BRI traffic crosstalking with WiFi module

Status in linux package in Ubuntu:
  New
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in linux source package in Noble:
  Invalid
Status in linux-oem-6.11 source package in Noble:
  New
Status in linux source package in Oracular:
  New
Status in linux-oem-6.11 source package in Oracular:
  Invalid

Bug description:
  [Impact]
  BRI (Bluetooth Radio Interface) traffic from CNVr to CNVi was found causing
  cross talk step errors to WiFi. Therefore, Bluetooth is turned on, the WiFi
  may be disrupted by Bluetooth and thus not work reliably.

  [Fix]
  Apply the patch 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/bluetooth/btintel.c?id=c707097a446ce3d284bc9f05736dc4701d2b8168
 on noble-oem-6.11

  [Test Plan]
  1. Compile noble-oem-6.11 with config BT_INTEL_PCIE on
  2. Include Bluetooth FWs ibt-0190-0291-iml.sfi, ibt-0190-0291.ddc, 
ibt-0190-0291.sfi in /lib/firmware/intel/
  ( These FWs are not public yet. We're going to do SRU in the future once the 
FWs are landed on the upstream linux-firmrware)
  3. Include WiFi FWs bz-b0-fm-c0-92.ucode in /lib/firmware/
  ( The same. These FWs are not public yet )
  4. Boot the noble-oem-6.11 kernel
  5. Test WiFi functionality.

  [Where problems could occur]
  The patch makes use of UEFI variable. If the variable is somehow not shown in 
the ROM, there might be some error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076881/+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 2076881] [NEW] btintel: Prevent BRI traffic crosstalking with WiFi module

Public bug reported:

[Impact]
BRI (Bluetooth Radio Interface) traffic from CNVr to CNVi was found causing
cross talk step errors to WiFi.

[Fix]
Apply the patch 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/bluetooth/btintel.c?id=c707097a446ce3d284bc9f05736dc4701d2b8168
 on noble-oem-6.11

[Test Plan]
1. Compile noble-oem-6.11 with config BT_INTEL_PCIE on
2. Include ibt-0190-0291-iml.sfi, ibt-0190-0291.ddc, ibt-0190-0291.sfi in 
/lib/firmware/intel/
3. Boot the noble-oem-6.11 kernel
4. Run "hcitool scan"

[Where problems could occur]
The patch makes use of UEFI variable. If the variable is somehow not shown in 
the ROM, there might be some error.
Add tags Tag

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

** Changed in: linux-hwe-6.8 (Ubuntu)
 Assignee: (unassigned) => En-Wei Wu (rickywu)

** Package changed: linux-hwe-6.8 (Ubuntu) => linux-oem-6.11 (Ubuntu)

** Changed in: linux-oem-6.11 (Ubuntu)
     Assignee: En-Wei Wu (rickywu) => (unassigned)

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

Title:
  btintel: Prevent BRI traffic crosstalking with WiFi module

Status in linux-oem-6.11 package in Ubuntu:
  New

Bug description:
  [Impact]
  BRI (Bluetooth Radio Interface) traffic from CNVr to CNVi was found causing
  cross talk step errors to WiFi.

  [Fix]
  Apply the patch 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/bluetooth/btintel.c?id=c707097a446ce3d284bc9f05736dc4701d2b8168
 on noble-oem-6.11

  [Test Plan]
  1. Compile noble-oem-6.11 with config BT_INTEL_PCIE on
  2. Include ibt-0190-0291-iml.sfi, ibt-0190-0291.ddc, ibt-0190-0291.sfi in 
/lib/firmware/intel/
  3. Boot the noble-oem-6.11 kernel
  4. Run "hcitool scan"

  [Where problems could occur]
  The patch makes use of UEFI variable. If the variable is somehow not shown in 
the ROM, there might be some error.
  Add tags Tag

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.11/+bug/2076881/+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 2076861] Re: rtw89: Support hardware rfkill and reset IDMEM mode to prevent download firmware failure

** Description changed:

  SRU verification for oem-6.11-noble:
  
  [Impact]
  There are two issues with Realtek RTL8851BE/RTL8852BE:
  Issue 1: After reboot from UEFI HTTPs boot, RTL8851BE wifi were not working 
due to the firmware download fail
  
  Issue 2: With RTL8851BE and "Control WLAN radio" (in BIOS setting) on,
  wifi function is not be disabled when we plug in the Ethernet cable
  
  [Fix]
  Apply the four Realtek patches from linux-next:
  
  bd4a3b10fa0e wifi: rtw89: add EVM statistics for 1SS rate
  0b38e6277aed wifi: rtw89: add support for hardware rfkill
  80fb81bb46a5 wifi: rtw89: 885xb: reset IDMEM mode to prevent download 
firmware failure
  27d90ad37771 wifi: rtw89: fix typo of rtw89_phy_ra_updata_XXX
  
  Link: https://lore.kernel.org/linux-
  
wireless/20240724052626.12774-1-pks...@realtek.com/T/#m20642bad88583db3ef5957b701c216d93e68c14d
  
  [Test Plan]
- Issue 1: 
+ Issue 1:
  1. Install Ubuntu image and boot into the OS，then power off system.
  2. power on SUT, press F12 to choose UEFI HTTPs Boot.
  3. wait 10 seconds and when see the available wireless networks，press 
Ctrl+Alt+Delete
  4. Boot to OS, check if the WiFi function works
  
  Issue 2:
  1. Enable Control WLAN radio in BIOS setting
  2. Boot into OS
  2. Plug in Ethernet cable.
  3. Check if the WiFi function being disabled
  
  [Where problems could occur]
- Hardware rfkill failed for WiFi hardware other than RTL8851BE/RTL8852BE.
+ May disrupt the software rfkill.

** Description changed:

- SRU verification for oem-6.11-noble:
- 
  [Impact]
  There are two issues with Realtek RTL8851BE/RTL8852BE:
  Issue 1: After reboot from UEFI HTTPs boot, RTL8851BE wifi were not working 
due to the firmware download fail
  
  Issue 2: With RTL8851BE and "Control WLAN radio" (in BIOS setting) on,
  wifi function is not be disabled when we plug in the Ethernet cable
  
  [Fix]
  Apply the four Realtek patches from linux-next:
  
  bd4a3b10fa0e wifi: rtw89: add EVM statistics for 1SS rate
  0b38e6277aed wifi: rtw89: add support for hardware rfkill
  80fb81bb46a5 wifi: rtw89: 885xb: reset IDMEM mode to prevent download 
firmware failure
  27d90ad37771 wifi: rtw89: fix typo of rtw89_phy_ra_updata_XXX
  
  Link: https://lore.kernel.org/linux-
  
wireless/20240724052626.12774-1-pks...@realtek.com/T/#m20642bad88583db3ef5957b701c216d93e68c14d
  
  [Test Plan]
  Issue 1:
  1. Install Ubuntu image and boot into the OS，then power off system.
  2. power on SUT, press F12 to choose UEFI HTTPs Boot.
  3. wait 10 seconds and when see the available wireless networks，press 
Ctrl+Alt+Delete
  4. Boot to OS, check if the WiFi function works
  
  Issue 2:
  1. Enable Control WLAN radio in BIOS setting
  2. Boot into OS
  2. Plug in Ethernet cable.
  3. Check if the WiFi function being disabled
  
  [Where problems could occur]
  May disrupt the software rfkill.

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

Title:
  rtw89: Support hardware rfkill and reset IDMEM mode to prevent
  download firmware failure

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-6.8 package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  There are two issues with Realtek RTL8851BE/RTL8852BE:
  Issue 1: After reboot from UEFI HTTPs boot, RTL8851BE wifi were not working 
due to the firmware download fail

  Issue 2: With RTL8851BE and "Control WLAN radio" (in BIOS setting) on,
  wifi function is not be disabled when we plug in the Ethernet cable

  [Fix]
  Apply the four Realtek patches from linux-next:

  bd4a3b10fa0e wifi: rtw89: add EVM statistics for 1SS rate
  0b38e6277aed wifi: rtw89: add support for hardware rfkill
  80fb81bb46a5 wifi: rtw89: 885xb: reset IDMEM mode to prevent download 
firmware failure
  27d90ad37771 wifi: rtw89: fix typo of rtw89_phy_ra_updata_XXX

  Link: https://lore.kernel.org/linux-
  
wireless/20240724052626.12774-1-pks...@realtek.com/T/#m20642bad88583db3ef5957b701c216d93e68c14d

  [Test Plan]
  Issue 1:
  1. Install Ubuntu image and boot into the OS，then power off system.
  2. power on SUT, press F12 to choose UEFI HTTPs Boot.
  3. wait 10 seconds and when see the available wireless networks，press 
Ctrl+Alt+Delete
  4. Boot to OS, check if the WiFi function works

  Issue 2:
  1. Enable Control WLAN radio in BIOS setting
  2. Boot into OS
  2. Plug in Ethernet cable.
  3. Check if the WiFi function being disabled

  [Where problems could occur]
  May disrupt the software rfkill.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076861/+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 2076861] Re: rtw89: Support hardware rfkill and reset IDMEM mode to prevent download firmware failure

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => En-Wei Wu (rickywu)

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

Title:
  rtw89: Support hardware rfkill and reset IDMEM mode to prevent
  download firmware failure

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-6.8 package in Ubuntu:
  In Progress

Bug description:
  SRU verification for oem-6.11-noble:

  [Impact]
  There are two issues with Realtek RTL8851BE/RTL8852BE:
  Issue 1: After reboot from UEFI HTTPs boot, RTL8851BE wifi were not working 
due to the firmware download fail

  Issue 2: With RTL8851BE and "Control WLAN radio" (in BIOS setting) on,
  wifi function is not be disabled when we plug in the Ethernet cable

  [Fix]
  Apply the four Realtek patches from linux-next:

  bd4a3b10fa0e wifi: rtw89: add EVM statistics for 1SS rate
  0b38e6277aed wifi: rtw89: add support for hardware rfkill
  80fb81bb46a5 wifi: rtw89: 885xb: reset IDMEM mode to prevent download 
firmware failure
  27d90ad37771 wifi: rtw89: fix typo of rtw89_phy_ra_updata_XXX

  Link: https://lore.kernel.org/linux-
  
wireless/20240724052626.12774-1-pks...@realtek.com/T/#m20642bad88583db3ef5957b701c216d93e68c14d

  [Test Plan]
  Issue 1: 
  1. Install Ubuntu image and boot into the OS，then power off system.
  2. power on SUT, press F12 to choose UEFI HTTPs Boot.
  3. wait 10 seconds and when see the available wireless networks，press 
Ctrl+Alt+Delete
  4. Boot to OS, check if the WiFi function works

  Issue 2:
  1. Enable Control WLAN radio in BIOS setting
  2. Boot into OS
  2. Plug in Ethernet cable.
  3. Check if the WiFi function being disabled

  [Where problems could occur]
  Hardware rfkill failed for WiFi hardware other than RTL8851BE/RTL8852BE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076861/+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 2076861] Re: rtw89: Support hardware rfkill and reset IDMEM mode to prevent download firmware failure

** Package changed: linux-oem-6.11 (Ubuntu) => linux-hwe-6.8 (Ubuntu)

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

Title:
  rtw89: Support hardware rfkill and reset IDMEM mode to prevent
  download firmware failure

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-6.8 package in Ubuntu:
  In Progress

Bug description:
  SRU verification for oem-6.11-noble:

  [Impact]
  There are two issues with Realtek RTL8851BE/RTL8852BE:
  Issue 1: After reboot from UEFI HTTPs boot, RTL8851BE wifi were not working 
due to the firmware download fail

  Issue 2: With RTL8851BE and "Control WLAN radio" (in BIOS setting) on,
  wifi function is not be disabled when we plug in the Ethernet cable

  [Fix]
  Apply the four Realtek patches from linux-next:

  bd4a3b10fa0e wifi: rtw89: add EVM statistics for 1SS rate
  0b38e6277aed wifi: rtw89: add support for hardware rfkill
  80fb81bb46a5 wifi: rtw89: 885xb: reset IDMEM mode to prevent download 
firmware failure
  27d90ad37771 wifi: rtw89: fix typo of rtw89_phy_ra_updata_XXX

  Link: https://lore.kernel.org/linux-
  
wireless/20240724052626.12774-1-pks...@realtek.com/T/#m20642bad88583db3ef5957b701c216d93e68c14d

  [Test Plan]
  Issue 1: 
  1. Install Ubuntu image and boot into the OS，then power off system.
  2. power on SUT, press F12 to choose UEFI HTTPs Boot.
  3. wait 10 seconds and when see the available wireless networks，press 
Ctrl+Alt+Delete
  4. Boot to OS, check if the WiFi function works

  Issue 2:
  1. Enable Control WLAN radio in BIOS setting
  2. Boot into OS
  2. Plug in Ethernet cable.
  3. Check if the WiFi function being disabled

  [Where problems could occur]
  Hardware rfkill failed for WiFi hardware other than RTL8851BE/RTL8852BE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076861/+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 2076861] [NEW] rtw89: Support hardware rfkill and reset IDMEM mode to prevent download firmware failure

Public bug reported:

SRU verification for oem-6.11-noble:

[Impact]
There are two issues with Realtek RTL8851BE/RTL8852BE:
Issue 1: After reboot from UEFI HTTPs boot, RTL8851BE wifi were not working due 
to the firmware download fail

Issue 2: With RTL8851BE and "Control WLAN radio" (in BIOS setting) on,
wifi function is not be disabled when we plug in the Ethernet cable

[Fix]
Apply the four Realtek patches from linux-next:

bd4a3b10fa0e wifi: rtw89: add EVM statistics for 1SS rate
0b38e6277aed wifi: rtw89: add support for hardware rfkill
80fb81bb46a5 wifi: rtw89: 885xb: reset IDMEM mode to prevent download firmware 
failure
27d90ad37771 wifi: rtw89: fix typo of rtw89_phy_ra_updata_XXX

Link: https://lore.kernel.org/linux-
wireless/20240724052626.12774-1-pks...@realtek.com/T/#m20642bad88583db3ef5957b701c216d93e68c14d

[Test Plan]
Issue 1: 
1. Install Ubuntu image and boot into the OS，then power off system.
2. power on SUT, press F12 to choose UEFI HTTPs Boot.
3. wait 10 seconds and when see the available wireless networks，press 
Ctrl+Alt+Delete
4. Boot to OS, check if the WiFi function works

Issue 2:
1. Enable Control WLAN radio in BIOS setting
2. Boot into OS
2. Plug in Ethernet cable.
3. Check if the WiFi function being disabled

[Where problems could occur]
Hardware rfkill failed for WiFi hardware other than RTL8851BE/RTL8852BE.

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

** Changed in: linux-oem-6.8 (Ubuntu)
 Assignee: (unassigned) => En-Wei Wu (rickywu)

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

** Package changed: linux-oem-6.8 (Ubuntu) => linux-oem-6.11 (Ubuntu)

** Changed in: linux-oem-6.11 (Ubuntu)
     Assignee: En-Wei Wu (rickywu) => (unassigned)

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

Title:
  rtw89: Support hardware rfkill and reset IDMEM mode to prevent
  download firmware failure

Status in linux-oem-6.11 package in Ubuntu:
  In Progress

Bug description:
  SRU verification for oem-6.11-noble:

  [Impact]
  There are two issues with Realtek RTL8851BE/RTL8852BE:
  Issue 1: After reboot from UEFI HTTPs boot, RTL8851BE wifi were not working 
due to the firmware download fail

  Issue 2: With RTL8851BE and "Control WLAN radio" (in BIOS setting) on,
  wifi function is not be disabled when we plug in the Ethernet cable

  [Fix]
  Apply the four Realtek patches from linux-next:

  bd4a3b10fa0e wifi: rtw89: add EVM statistics for 1SS rate
  0b38e6277aed wifi: rtw89: add support for hardware rfkill
  80fb81bb46a5 wifi: rtw89: 885xb: reset IDMEM mode to prevent download 
firmware failure
  27d90ad37771 wifi: rtw89: fix typo of rtw89_phy_ra_updata_XXX

  Link: https://lore.kernel.org/linux-
  
wireless/20240724052626.12774-1-pks...@realtek.com/T/#m20642bad88583db3ef5957b701c216d93e68c14d

  [Test Plan]
  Issue 1: 
  1. Install Ubuntu image and boot into the OS，then power off system.
  2. power on SUT, press F12 to choose UEFI HTTPs Boot.
  3. wait 10 seconds and when see the available wireless networks，press 
Ctrl+Alt+Delete
  4. Boot to OS, check if the WiFi function works

  Issue 2:
  1. Enable Control WLAN radio in BIOS setting
  2. Boot into OS
  2. Plug in Ethernet cable.
  3. Check if the WiFi function being disabled

  [Where problems could occur]
  Hardware rfkill failed for WiFi hardware other than RTL8851BE/RTL8852BE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.11/+bug/2076861/+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 2074520] Re: Linux 5.15.0-116 or greater breaks xmrig

2024-08-05 Thread En-Wei Wu

Hi @Anant,

Could you please run the apport-collect on your 5.15.0-116 kernel? We
need the information of your system when the problem occurred.

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

Title:
  Linux 5.15.0-116 or greater breaks xmrig

Status in linux package in Ubuntu:
  New
Status in xmrig package in Ubuntu:
  New

Bug description:
  I am suddenly getting hashrates between 0.63 to 0.74 H/s where I would
  get 640 to 730 H/s earlier (1000x slower). Initially, it would go away
  after a few reboots but now it won't.

  I stumbled upon the problem when using Linux Mint, but it hinges on
  the kernels, which Ubuntu ships.

  I initially encountered it when using linux 5.15.0-116-generic &
  5.15.0-117-generic on Mint 21.3. It also occurs when using kernel
  6.8.0-39-generic, when using Mint 22.

  5.15.0-113 was the kernel available immediately preceding 5.15.0-116
  in Mint 21.3, and there were no problems when using this kernel.

  My CPU is an i3-6006U, unsure if that matters.

  XMRig version latest:
  https://github.com/xmrig/xmrig/releases/download/v6.21.3/xmrig-6.21.3-linux-
  static-x64.tar.gz

  Discussed on the Linux Mint forums, is a bug in the kernel ubuntu
  ships:
  
https://forums.linuxmint.com/viewtopic.php?p=2501154&sid=d324ed8ce5b30d882e3b5ac217436968#p2501154

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074520/+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 2073538] Re: kacpi_notify high cpu on interrupt gpe17

2024-08-05 Thread En-Wei Wu

Hi @Bill,

Sorry for the late reply. It seems like the problem is strongly related to the 
error message in comment #3. However, the clue is not that clear. Could you 
please try the following steps to help us get more debug info:
1. Blacklist the ucsi_acpi.ko and boot
2. Login as root, then $ echo 'file ucsi.c +p' > 
/sys/kernel/debug/dynamic_debug/control
3. Load the ucsi_acpi.ko
4. Dump the dmesg here

Thank you for your time.

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

Title:
  kacpi_notify high cpu on interrupt gpe17

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Picked up a HP laptop during July sales, and found the CPU soars to 80+ with 
kacpi_notify hitting GPE17.
  I would like some help finding the cause.  Google searches were vague about 
masking the interrupt which did NOT help.  If we can find what is calling the 
interrupts maybe we can better document a solution.

  top - 20:00:05 up 10 min,  1 user,  load average: 86.24, 76.27, 42.44
  Tasks: 453 total,   2 running, 451 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.1 us,  8.5 sy,  0.0 ni, 91.4 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 
st 
  MiB Mem :  62040.5 total,  51595.7 free,   3166.0 used,   8146.3 buff/cache   
  
  MiB Swap:  0.0 total,  0.0 free,  0.0 used.  58874.4 avail Mem 

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ 
COMMAND 
 
  127 root  20   0   0  0  0 D   1.3   0.0   0:03.71 
[kworker/11:1+kacpi_notify] 
 
  280 root  20   0   0  0  0 D   1.3   0.0   0:06.63 
[kworker/5:5+kacpi_notify]  
 
  314 root  20   0   0  0  0 D   1.3   0.0   0:06.68 
[kworker/5:12+kacpi_notify]  

  ubuntu@ubuntu:~$ grep . -r /sys/firmware/acpi/interrupts/ | awk '$2 > 0'
  /sys/firmware/acpi/interrupts/sci:1907
  /sys/firmware/acpi/interrupts/gpe_all:1907
  /sys/firmware/acpi/interrupts/gpe17:1907  EN enabled  unmasked

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-31-generic 6.8.0-31.31
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:ubuntu 2813 F pipewire
   /dev/snd/controlC1:  ubuntu 2815 F wireplumber
   /dev/snd/controlC0:  ubuntu 2815 F wireplumber
   /dev/snd/controlC2:  ubuntu 2815 F wireplumber
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CasperVersion: 1.498
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 18 19:52:46 2024
  LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: HP Victus by HP Gaming Laptop 15-fb2xxx
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-31-generic N/A
   linux-backports-modules-6.8.0-31-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2024
  dmi.bios.release: 15.3
  dmi.bios.vendor: AMI
  dmi.bios.version: F.03
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8C2F
  dmi.board.vendor: HP
  dmi.board.version: 04.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 4.14
  dmi.modalias: 
dmi:bvnAMI:bvrF.03:bd05/20/2024:br15.3:efr4.14:svnHP:pnVictusbyHPGamingLaptop15-fb2xxx:pvr:rvnHP:rn8C2F:rvr04.14:cvnHP:ct10:cvrChassisVersion:skuA14MNUA#ABA:
  dmi.product.family: 103C_5335M7 HP Victus
  dmi.product.name: Victus by HP Gaming Laptop 15-fb2xxx
  dmi.product.sku: A14MNUA#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073538/+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 2074049] Re: please help enable more EROFS compression algorithms

Hi @Gao,

I've sent a patch adding these configs:
https://lists.ubuntu.com/archives/kernel-team/2024-July/152509.html

Once we have any update I will notify you.

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

Title:
  please help enable more EROFS compression algorithms

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,

  Could you please enable more EROFS compression algorithms for better
  compression ratios to end users on Ubuntu?

  CONFIG_EROFS_FS_ZIP_LZMA=y  (Kernel 5.16+)
  CONFIG_EROFS_FS_ZIP_DEFLATE=y   (Kernel 6.6+)
  CONFIG_EROFS_FS_ZIP_ZSTD=y (Kernel 6.10+)

  so that users can use these algorithms directly with shipped kernels
  in addition to the default LZ4 one.

  Thanks in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074049/+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 2074520] Re: Linux 5.15.0-116 or greater breaks xmrig

Hi, @Anant.

Thank you for your report. Could you please run the following command to
help us collecting the information of your system?

apport-collect 2074520

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

Title:
  Linux 5.15.0-116 or greater breaks xmrig

Status in linux package in Ubuntu:
  New
Status in xmrig package in Ubuntu:
  New

Bug description:
  I am suddenly getting hashrates between 0.63 to 0.74 H/s where I would
  get 640 to 730 H/s earlier (1000x slower). Initially, it would go away
  after a few reboots but now it won't.

  I stumbled upon the problem when using Linux Mint, but it hinges on
  the kernels, which Ubuntu ships.

  I initially encountered it when using linux 5.15.0-116-generic &
  5.15.0-117-generic on Mint 21.3. It also occurs when using kernel
  6.8.0-39-generic, when using Mint 22.

  5.15.0-113 was the kernel available immediately preceding 5.15.0-116
  in Mint 21.3, and there were no problems when using this kernel.

  My CPU is an i3-6006U, unsure if that matters.

  XMRig version latest:
  https://github.com/xmrig/xmrig/releases/download/v6.21.3/xmrig-6.21.3-linux-
  static-x64.tar.gz

  Discussed on the Linux Mint forums, is a bug in the kernel ubuntu
  ships:
  
https://forums.linuxmint.com/viewtopic.php?p=2501154&sid=d324ed8ce5b30d882e3b5ac217436968#p2501154

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074520/+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 2073676] Re: after update of kernel HDMI audio is not working

** Changed in: linux (Ubuntu)
 Assignee: En-Wei Wu (rickywu) => Chris Chiu (mschiu77)

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

Title:
  after update of kernel HDMI audio is not working

Status in linux package in Ubuntu:
  New

Bug description:
  after update of kernel the Audio output via dock - HDMI is no longer
  working.

  the display is showing that the audio i receving but there is no
  audio. If I switch to normal speakers on the laptop the audio is
  working.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-38-generic 6.8.0-38.38
  ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
  Uname: Linux 6.8.0-38-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 20 18:45:44 2024
  InstallationDate: Installed on 2024-03-11 (131 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: LENOVO 20XK007DMX
  ProcEnviron:
   LANG=da_DK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-38-generic 
root=UUID=735a8489-6e61-48ac-a281-46d43115ef53 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.8.0-38-generic N/A
   linux-backports-modules-6.8.0-38-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to noble on 2024-05-22 (59 days ago)
  dmi.bios.date: 10/30/2023
  dmi.bios.release: 1.25
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET55W (1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XK007DMX
  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.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET55W(1.25):bd10/30/2023:br1.25:efr1.25:svnLENOVO:pn20XK007DMX:pvrThinkPadT14Gen2a:rvnLENOVO:rn20XK007DMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XK_BU_Think_FM_ThinkPadT14Gen2a:
  dmi.product.family: ThinkPad T14 Gen 2a
  dmi.product.name: 20XK007DMX
  dmi.product.sku: LENOVO_MT_20XK_BU_Think_FM_ThinkPad T14 Gen 2a
  dmi.product.version: ThinkPad T14 Gen 2a
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073676/+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 2074202] Re: Segfault in perf (__perf_cpu_map__nr) on Linux 6.5.0-45

Hi @Tim,

Thank you for your report.

Since this issue is like to be an issue from upstream Linux kernel, I
suggest that you can file a bug report on Linux Bugzilla:
https://bugzilla.kernel.org/.

Thanks again.

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

Title:
  Segfault in perf (__perf_cpu_map__nr) on Linux 6.5.0-45

Status in linux package in Ubuntu:
  New

Bug description:
  With package linux-tools-6.5.0-45-generic, perf will reproducibly
  segfault on startup:

  $ SYSFS_PATH=/nonexistent perf record /bin/echo
  Failed to read max cpus, using default of 4096
  libperf: Miscounted nr_mmaps 0 vs 1
  WARNING: No sample_id_all support, falling back to unordered processing
  perf: Segmentation fault

  Under gdb:

  Thread 1 "perf" received signal SIGSEGV, Segmentation fault.
  0x55739ca3 in __perf_cpu_map__nr (cpus=0x0) at cpumap.c:283
  283 cpumap.c: No such file or directory.
  (gdb) bt
  #0  0x55739ca3 in __perf_cpu_map__nr (cpus=0x0) at cpumap.c:283
  #1  0x55739f37 in perf_cpu_map__max (map=0x0) at cpumap.c:371
  #2  0x556ac264 in cpu_map_data__alloc 
(syn_data=syn_data@entry=0x7fff8860, header_size=header_size@entry=8) at 
util/synthetic-events.c:1273
  #3  0x556af6a6 in cpu_map_event__new (map=) at 
util/synthetic-events.c:1321
  #4  perf_event__synthesize_cpu_map (tool=tool@entry=0x55e62300 , 
map=, process=process@entry=0x55596d40 
, machine=machine@entry=0x0)
  at util/synthetic-events.c:1341
  #5  0x55594ddf in record__synthesize (tail=tail@entry=false, 
rec=0x55e62300 ) at builtin-record.c:2050
  #6  0x5559891f in __cmd_record (argc=, argv=, rec=0x55e62300 ) at builtin-record.c:2512
  #7  0x5559b95f in cmd_record (argc=1, argv=0x7fffe450) at 
builtin-record.c:4260
  #8  0x556073f1 in run_builtin (p=p@entry=0x55e64868 
, argc=argc@entry=2, argv=argv@entry=0x7fffe450) at perf.c:323
  #9  0x5558580e in handle_internal_command (argv=0x7fffe450, 
argc=2) at perf.c:377
  #10 run_argv (argv=, argcp=) at 
perf.c:421
  #11 main (argc=2, argv=0x7fffe450) at perf.c:537

  The SYSFS_PATH environment variable is for your convenient
  reproduction. My actual problem is that I'm trying to use perf inside
  a systemd-nspawn container. The /proc/mounts looks like this:

  tmpfs /sys tmpfs 
ro,nosuid,nodev,noexec,relatime,size=4096k,nr_inodes=1024,mode=555,inode64 0 0
  ...
  sysfs /sys/block sysfs ro,nosuid,nodev,noexec,relatime 0 0
  sysfs /sys/bus sysfs ro,nosuid,nodev,noexec,relatime 0 0
  sysfs /sys/class sysfs ro,nosuid,nodev,noexec,relatime 0 0
  sysfs /sys/dev sysfs ro,nosuid,nodev,noexec,relatime 0 0
  sysfs /sys/devices sysfs ro,nosuid,nodev,noexec,relatime 0 0
  sysfs /sys/kernel sysfs ro,nosuid,nodev,noexec,relatime 0 0

  Perf looks for the first mount point with type "sysfs" and so
  concludes sysfs is mounted at /sys/block. Thus it can't find any
  relevant file and fails to detect relevant information about the
  system. Then it segfaults with a null pointer dereference.

  A workaround is to set SYSFS_PATH=/sys.

  Apologies if this is not the right place. Perf is in the kernel source
  tree so for most purposes it is a kernel bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074202/+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 2074049] Re: please help enable more EROFS compression algorithms

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => En-Wei Wu (rickywu)

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

Title:
  please help enable more EROFS compression algorithms

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,

  Could you please enable more EROFS compression algorithms for better
  compression ratios to end users on Ubuntu?

  CONFIG_EROFS_FS_ZIP_LZMA=y  (Kernel 5.16+)
  CONFIG_EROFS_FS_ZIP_DEFLATE=y   (Kernel 6.6+)
  CONFIG_EROFS_FS_ZIP_ZSTD=y (Kernel 6.10+)

  so that users can use these algorithms directly with shipped kernels
  in addition to the default LZ4 one.

  Thanks in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074049/+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 2073676] Re: after update of kernel HDMI audio is not working

Hi @Theis,

Thank you for your report.

I'm wondering if it is a regression because you said the HDMI is
malfunctioned after updating the system.

Before the 6.8.0-38-generic, what kernel version did you use with HDMI
well functioning? It will help us a lot to know if the issue can/can't
be reproduced on a certain version.

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

Title:
  after update of kernel HDMI audio is not working

Status in linux package in Ubuntu:
  New

Bug description:
  after update of kernel the Audio output via dock - HDMI is no longer
  working.

  the display is showing that the audio i receving but there is no
  audio. If I switch to normal speakers on the laptop the audio is
  working.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-38-generic 6.8.0-38.38
  ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
  Uname: Linux 6.8.0-38-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 20 18:45:44 2024
  InstallationDate: Installed on 2024-03-11 (131 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: LENOVO 20XK007DMX
  ProcEnviron:
   LANG=da_DK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-38-generic 
root=UUID=735a8489-6e61-48ac-a281-46d43115ef53 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.8.0-38-generic N/A
   linux-backports-modules-6.8.0-38-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to noble on 2024-05-22 (59 days ago)
  dmi.bios.date: 10/30/2023
  dmi.bios.release: 1.25
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET55W (1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XK007DMX
  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.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET55W(1.25):bd10/30/2023:br1.25:efr1.25:svnLENOVO:pn20XK007DMX:pvrThinkPadT14Gen2a:rvnLENOVO:rn20XK007DMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XK_BU_Think_FM_ThinkPadT14Gen2a:
  dmi.product.family: ThinkPad T14 Gen 2a
  dmi.product.name: 20XK007DMX
  dmi.product.sku: LENOVO_MT_20XK_BU_Think_FM_ThinkPad T14 Gen 2a
  dmi.product.version: ThinkPad T14 Gen 2a
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073676/+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 2073676] Re: after update of kernel HDMI audio is not working

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => En-Wei Wu (rickywu)

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

Title:
  after update of kernel HDMI audio is not working

Status in linux package in Ubuntu:
  New

Bug description:
  after update of kernel the Audio output via dock - HDMI is no longer
  working.

  the display is showing that the audio i receving but there is no
  audio. If I switch to normal speakers on the laptop the audio is
  working.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-38-generic 6.8.0-38.38
  ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
  Uname: Linux 6.8.0-38-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 20 18:45:44 2024
  InstallationDate: Installed on 2024-03-11 (131 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: LENOVO 20XK007DMX
  ProcEnviron:
   LANG=da_DK.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-38-generic 
root=UUID=735a8489-6e61-48ac-a281-46d43115ef53 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.8.0-38-generic N/A
   linux-backports-modules-6.8.0-38-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to noble on 2024-05-22 (59 days ago)
  dmi.bios.date: 10/30/2023
  dmi.bios.release: 1.25
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET55W (1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XK007DMX
  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.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET55W(1.25):bd10/30/2023:br1.25:efr1.25:svnLENOVO:pn20XK007DMX:pvrThinkPadT14Gen2a:rvnLENOVO:rn20XK007DMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XK_BU_Think_FM_ThinkPadT14Gen2a:
  dmi.product.family: ThinkPad T14 Gen 2a
  dmi.product.name: 20XK007DMX
  dmi.product.sku: LENOVO_MT_20XK_BU_Think_FM_ThinkPad T14 Gen 2a
  dmi.product.version: ThinkPad T14 Gen 2a
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073676/+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 2074110] Re: Trying to resolve NordVpn configuration issues

Hi @ice,

Thank you for your report.

Can you describe more detailed about how you encountered this issue?
That is, how to reproduce this issue.

Thanks again.

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => En-Wei Wu (rickywu)

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

Title:
  Trying to resolve NordVpn configuration issues

Status in linux package in Ubuntu:
  New

Bug description:
  k0j1r0@Zaku01:~$ ubuntu-bug linux
  Gtk-Message: 15:18:24.841: Failed to load module "xapp-gtk3-module"

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-39-generic 6.8.0-39.39
  ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
  Uname: Linux 6.8.0-39-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:k0j1r0 2347 F pipewire
   /dev/snd/controlC0:  k0j1r0 2349 F wireplumber
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jul 25 15:17:47 2024
  InstallationDate: Installed on 2024-07-13 (12 days ago)
  InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Release amd64 
(20240425.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 045e:07b2 Microsoft Corp. 2.4GHz Transceiver v8.0 
used by mouse Wireless Desktop 900
   Bus 001 Device 004: ID 5986:2113 Bison Electronics Inc. SunplusIT Integrated 
Camera
   Bus 001 Device 005: ID 06cb:00a2 Synaptics, Inc. Metallica MOH Touch 
Fingerprint Reader
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: LENOVO 20N8001AUS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-39-generic 
root=UUID=89139a69-e296-4079-8822-adc316cd31c7 ro quiet splash 
resume=UUID=8ae8ec48-36fd-4e43-afd3-865ea771e68b clearcpubuffers=full 
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.8.0-39-generic N/A
   linux-backports-modules-6.8.0-39-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2024
  dmi.bios.release: 1.37
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0YET54W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20N8001AUS
  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.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0YET54W(1.37):bd03/04/2024:br1.37:efr1.23:svnLENOVO:pn20N8001AUS:pvrThinkPadE490:rvnLENOVO:rn20N8001AUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20N8_BU_SMB_FM_ThinkPadE490:
  dmi.product.family: ThinkPad E490
  dmi.product.name: 20N8001AUS
  dmi.product.sku: LENOVO_MT_20N8_BU_SMB_FM_ThinkPad E490
  dmi.product.version: ThinkPad E490
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074110/+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 2074084] Re: Caplock inversed in Ubuntu 23.10

Hi @Danny,

Thank you for your report.

As the issue seems to be an ACPI/BIOS problem and not a kernel issue, I
suggest that you file a bug report on HP community and possibly update
your BIOS to the latest one.

Thanks.

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

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

Title:
  Caplock inversed in Ubuntu 23.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The Caplock button on my OMEN16 Ubuntu 23.10/Win 11 laptop is inversed, it is 
lit when it is not in Caplock state and vice virsa. For more detailed 
information, see this bug report. 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/267999
  I basically just want to provide my system data to deal with that bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-44-generic 6.5.0-44.44
  ProcVersionSignature: Ubuntu 6.5.0-44.44-generic 6.5.13
  Uname: Linux 6.5.0-44-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  danny-wenjue-zhang   3833 F pipewire
danny-wenjue-zhang   3836 F wireplumber
   /dev/snd/controlC0:  danny-wenjue-zhang   3836 F wireplumber
   /dev/snd/seq:danny-wenjue-zhang   3833 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 25 21:31:53 2024
  InstallationDate: Installed on 2024-01-06 (201 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-44-generic 
root=UUID=89848867-b092-4ef7-ae34-4b3c80a5da79 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.5.0-44-generic N/A
   linux-backports-modules-6.5.0-44-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.10
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2024
  dmi.bios.release: 15.21
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8BAB
  dmi.board.vendor: HP
  dmi.board.version: 76.53
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 76.53
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd05/29/2024:br15.21:efr76.53:svnHP:pnOMENbyHPGamingLaptop16-wf0xxx:pvrType1ProductConfigId:rvnHP:rn8BAB:rvr76.53:cvnHP:ct10:cvrChassisVersion:sku81L09PA#AB2:
  dmi.product.family: 103C_5335M7 HP OMEN
  dmi.product.name: OMEN by HP Gaming Laptop 16-wf0xxx
  dmi.product.sku: 81L09PA#AB2
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074084/+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 2074136] Re: VirtualBox 6.1.5 does not work anymore.

Hi @syos,

could you please boot into your Ubuntu kernel and execute the following
command only once, as it will automatically gather debugging
information, in a terminal:

apport-collect 2074136

This can help us examine the issue.

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

Title:
  VirtualBox 6.1.5 does not work anymore.

Status in linux package in Ubuntu:
  New

Bug description:
  Kernel 5.15.0.116 and 117: VirtualBox 6.1.5 does not work anymore.
  Ok with Kernel 5.15.0.113

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074136/+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 2074084] Re: Caplock inversed in Ubuntu 23.10

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => En-Wei Wu (rickywu)

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

Title:
  Caplock inversed in Ubuntu 23.10

Status in linux package in Ubuntu:
  New

Bug description:
  The Caplock button on my OMEN16 Ubuntu 23.10/Win 11 laptop is inversed, it is 
lit when it is not in Caplock state and vice virsa. For more detailed 
information, see this bug report. 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/267999
  I basically just want to provide my system data to deal with that bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-44-generic 6.5.0-44.44
  ProcVersionSignature: Ubuntu 6.5.0-44.44-generic 6.5.13
  Uname: Linux 6.5.0-44-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  danny-wenjue-zhang   3833 F pipewire
danny-wenjue-zhang   3836 F wireplumber
   /dev/snd/controlC0:  danny-wenjue-zhang   3836 F wireplumber
   /dev/snd/seq:danny-wenjue-zhang   3833 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 25 21:31:53 2024
  InstallationDate: Installed on 2024-01-06 (201 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-44-generic 
root=UUID=89848867-b092-4ef7-ae34-4b3c80a5da79 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.5.0-44-generic N/A
   linux-backports-modules-6.5.0-44-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.10
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2024
  dmi.bios.release: 15.21
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8BAB
  dmi.board.vendor: HP
  dmi.board.version: 76.53
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 76.53
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd05/29/2024:br15.21:efr76.53:svnHP:pnOMENbyHPGamingLaptop16-wf0xxx:pvrType1ProductConfigId:rvnHP:rn8BAB:rvr76.53:cvnHP:ct10:cvrChassisVersion:sku81L09PA#AB2:
  dmi.product.family: 103C_5335M7 HP OMEN
  dmi.product.name: OMEN by HP Gaming Laptop 16-wf0xxx
  dmi.product.sku: 81L09PA#AB2
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074084/+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 2074095] Re: kernel 5.15.0-117 VirtualBox Error

Hi Andreas.

Could you please boot into a Ubuntu kernel (not Linux Mint) and execute
the following command only once, as it will automatically gather
debugging information, in a terminal:

apport-collect 2074095

This can help us examine the issue.

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

Title:
  kernel 5.15.0-117  VirtualBox Error

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Virtualbox Version 6.1.50_Ubuntu r161033 is not starting any virtual machine 
likewise  do the 116, I switched back to 113.
  Description:  Linux Mint 21.1
  Release:  21.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074095/+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 2073001] Re: Regression: kernel bug upon keyboard disconnect

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

Title:
  Regression: kernel bug upon keyboard disconnect

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a Dell Venue 7140 tablet with the keyboard/touchpad/battery dock
  when disconnecting the dock there is a kernel bug observed in dmesg:

  [   83.719050] usb 1-4: USB disconnect, device number 3
  [   83.861800] intel-vbtn INT33D6:00: Registering Intel Virtual Switches 
input-dev after receiving a switch event
  [   83.861858] input: Intel Virtual Switches as 
/devices/pci:00/:00:1f.0/PNP0C09:00/INT33D6:00/input/input17
  [   83.861865] intel-vbtn INT33D6:00: Registering Intel Virtual Switches 
input-dev after receiving a switch event
  [   83.861872] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:1f.0/PNP0C09:00/INT33D6:00/input/input17'
  [   83.861874] CPU: 2 PID: 1161 Comm: kworker/2:4 Not tainted 
6.8.0-40-generic #40-Ubuntu
  [   83.861877] Hardware name: Dell Inc. Venue 11 Pro 7140/0XMVMH, BIOS A20 
11/18/2019
  [   83.861879] Workqueue: kacpi_notify acpi_os_execute_deferred
  [   83.861885] Call Trace:
  [   83.861887]  
  [   83.861890]  dump_stack_lvl+0x76/0xa0
  [   83.861894]  dump_stack+0x10/0x20
  [   83.861897]  sysfs_warn_dup+0x8a/0xb0
  [   83.861901]  sysfs_create_dir_ns+0xe0/0x100
  [   83.861905]  kobject_add_internal+0xa8/0x2f0
  [   83.861908]  kobject_add+0x93/0x100
  [   83.861912]  ? get_device_parent+0xd0/0x210
  [   83.861917]  device_add+0xe0/0x740
  [   83.861919]  input_register_device+0xe8/0x370
  [   83.861924]  notify_handler+0x12e/0x1a0 [intel_vbtn]
  [   83.861930]  acpi_ev_notify_dispatch+0x59/0xa0
  [   83.861934]  acpi_os_execute_deferred+0x1a/0x40
  [   83.861937]  process_one_work+0x16f/0x350
  [   83.861941]  worker_thread+0x306/0x440
  [   83.861945]  ? _raw_spin_lock_irqsave+0xe/0x20
  [   83.861948]  ? __pfx_worker_thread+0x10/0x10
  [   83.861951]  kthread+0xf2/0x120
  [   83.861954]  ? __pfx_kthread+0x10/0x10
  [   83.861956]  ret_from_fork+0x47/0x70
  [   83.861959]  ? __pfx_kthread+0x10/0x10
  [   83.861962]  ret_from_fork_asm+0x1b/0x30
  [   83.861965]  
  [   83.861967] kobject: kobject_add_internal failed for input17 with -EEXIST, 
don't try to register things with the same name in the same directory.
  [   83.877338] BUG: kernel NULL pointer dereference, address: 0018
  [   83.877347] #PF: supervisor read access in kernel mode
  [   83.877350] #PF: error_code(0x) - not-present page
  [   83.877353] PGD 0 P4D 0 
  [   83.877358] Oops:  [#1] PREEMPT SMP PTI
  [   83.877362] CPU: 2 PID: 56 Comm: kworker/2:1 Not tainted 6.8.0-40-generic 
#40-Ubuntu
  [   83.877366] Hardware name: Dell Inc. Venue 11 Pro 7140/0XMVMH, BIOS A20 
11/18/2019
  [   83.877369] Workqueue: kacpi_notify acpi_os_execute_deferred
  [   83.877378] RIP: 0010:klist_add_tail+0x2a/0x80
  [   83.877385] Code: 55 48 89 e5 41 55 4c 8d 6f 08 41 54 49 89 fc 53 48 89 f3 
48 89 37 83 e6 01 4c 89 6f 08 4c 89 6f 10 c7 47 18 01 00 00 00 75 4d <48> 8b 43 
18 48 85 c0 74 08 4c 89 e7 e8 85 38 0c 00 48 89 df e8 dd
  [   83.877389] RSP: 0018:b6dec022bc98 EFLAGS: 00010246
  [   83.877393] RAX: 96b9c82fbc00 RBX:  RCX: 

  [   83.877396] RDX:  RSI:  RDI: 
96b9c82fbc28
  [   83.877399] RBP: b6dec022bcb0 R08:  R09: 

  [   83.877402] R10:  R11:  R12: 
96b9c82fbc28
  [   83.877406] R13: 96b9c82fbc30 R14:  R15: 
96ba13371090
  [   83.877409] FS:  () GS:96bad650() 
knlGS:
  [   83.877413] CS:  0010 DS:  ES:  CR0: 80050033
  [   83.877416] CR2: 0018 CR3: 00010d080005 CR4: 
003706f0
  [   83.877419] DR0:  DR1:  DR2: 

  [   83.877422] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   83.877424] Call Trace:
  [   83.877428]  
  [   83.877432]  ? show_regs+0x6d/0x80
  [   83.877438]  ? __die+0x24/0x80
  [   83.877442]  ? page_fault_oops+0x99/0x1b0
  [   83.877448]  ? do_user_addr_fault+0x2e2/0x670
  [   83.877453]  ? exc_page_fault+0x83/0x1b0
  [   83.877459]  ? asm_exc_page_fault+0x27/0x30
  [   83.877468]  ? klist_add_tail+0x2a/0x80
  [   83.877473]  device_add+0x590/0x740
  [   83.877479]  cdev_device_add+0x4e/0xc0
  [   83.877483]  ? cdev_init+0x56/0x70
  [   83.877488]  evdev_connect+0x1a9/0x210
  [   83.877493]  input_attach_handler.isra.0+0x84/0xc0
  [   83.877498]  input_register_device+0x231/0x370
  [   83.877505]  notify_handler+0x12e/0x1a0 [intel_vbtn]
  [   83.877514]  acpi_ev_notify_dispatch+0x59/0xa0
  [   83.877520]  acpi_os_execute_deferred+0x1a/0x40
  [   83.877525]  proce

[Kernel-packages] [Bug 2073001] Re: Regression: kernel bug upon keyboard disconnect

Hi @kmstoilov,

Thank you for your quick reply and testing. Please file another bug and
we'll work on it. 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/2073001

Title:
  Regression: kernel bug upon keyboard disconnect

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Dell Venue 7140 tablet with the keyboard/touchpad/battery dock
  when disconnecting the dock there is a kernel bug observed in dmesg:

  [   83.719050] usb 1-4: USB disconnect, device number 3
  [   83.861800] intel-vbtn INT33D6:00: Registering Intel Virtual Switches 
input-dev after receiving a switch event
  [   83.861858] input: Intel Virtual Switches as 
/devices/pci:00/:00:1f.0/PNP0C09:00/INT33D6:00/input/input17
  [   83.861865] intel-vbtn INT33D6:00: Registering Intel Virtual Switches 
input-dev after receiving a switch event
  [   83.861872] sysfs: cannot create duplicate filename 
'/devices/pci:00/:00:1f.0/PNP0C09:00/INT33D6:00/input/input17'
  [   83.861874] CPU: 2 PID: 1161 Comm: kworker/2:4 Not tainted 
6.8.0-40-generic #40-Ubuntu
  [   83.861877] Hardware name: Dell Inc. Venue 11 Pro 7140/0XMVMH, BIOS A20 
11/18/2019
  [   83.861879] Workqueue: kacpi_notify acpi_os_execute_deferred
  [   83.861885] Call Trace:
  [   83.861887]  
  [   83.861890]  dump_stack_lvl+0x76/0xa0
  [   83.861894]  dump_stack+0x10/0x20
  [   83.861897]  sysfs_warn_dup+0x8a/0xb0
  [   83.861901]  sysfs_create_dir_ns+0xe0/0x100
  [   83.861905]  kobject_add_internal+0xa8/0x2f0
  [   83.861908]  kobject_add+0x93/0x100
  [   83.861912]  ? get_device_parent+0xd0/0x210
  [   83.861917]  device_add+0xe0/0x740
  [   83.861919]  input_register_device+0xe8/0x370
  [   83.861924]  notify_handler+0x12e/0x1a0 [intel_vbtn]
  [   83.861930]  acpi_ev_notify_dispatch+0x59/0xa0
  [   83.861934]  acpi_os_execute_deferred+0x1a/0x40
  [   83.861937]  process_one_work+0x16f/0x350
  [   83.861941]  worker_thread+0x306/0x440
  [   83.861945]  ? _raw_spin_lock_irqsave+0xe/0x20
  [   83.861948]  ? __pfx_worker_thread+0x10/0x10
  [   83.861951]  kthread+0xf2/0x120
  [   83.861954]  ? __pfx_kthread+0x10/0x10
  [   83.861956]  ret_from_fork+0x47/0x70
  [   83.861959]  ? __pfx_kthread+0x10/0x10
  [   83.861962]  ret_from_fork_asm+0x1b/0x30
  [   83.861965]  
  [   83.861967] kobject: kobject_add_internal failed for input17 with -EEXIST, 
don't try to register things with the same name in the same directory.
  [   83.877338] BUG: kernel NULL pointer dereference, address: 0018
  [   83.877347] #PF: supervisor read access in kernel mode
  [   83.877350] #PF: error_code(0x) - not-present page
  [   83.877353] PGD 0 P4D 0 
  [   83.877358] Oops:  [#1] PREEMPT SMP PTI
  [   83.877362] CPU: 2 PID: 56 Comm: kworker/2:1 Not tainted 6.8.0-40-generic 
#40-Ubuntu
  [   83.877366] Hardware name: Dell Inc. Venue 11 Pro 7140/0XMVMH, BIOS A20 
11/18/2019
  [   83.877369] Workqueue: kacpi_notify acpi_os_execute_deferred
  [   83.877378] RIP: 0010:klist_add_tail+0x2a/0x80
  [   83.877385] Code: 55 48 89 e5 41 55 4c 8d 6f 08 41 54 49 89 fc 53 48 89 f3 
48 89 37 83 e6 01 4c 89 6f 08 4c 89 6f 10 c7 47 18 01 00 00 00 75 4d <48> 8b 43 
18 48 85 c0 74 08 4c 89 e7 e8 85 38 0c 00 48 89 df e8 dd
  [   83.877389] RSP: 0018:b6dec022bc98 EFLAGS: 00010246
  [   83.877393] RAX: 96b9c82fbc00 RBX:  RCX: 

  [   83.877396] RDX:  RSI:  RDI: 
96b9c82fbc28
  [   83.877399] RBP: b6dec022bcb0 R08:  R09: 

  [   83.877402] R10:  R11:  R12: 
96b9c82fbc28
  [   83.877406] R13: 96b9c82fbc30 R14:  R15: 
96ba13371090
  [   83.877409] FS:  () GS:96bad650() 
knlGS:
  [   83.877413] CS:  0010 DS:  ES:  CR0: 80050033
  [   83.877416] CR2: 0018 CR3: 00010d080005 CR4: 
003706f0
  [   83.877419] DR0:  DR1:  DR2: 

  [   83.877422] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   83.877424] Call Trace:
  [   83.877428]  
  [   83.877432]  ? show_regs+0x6d/0x80
  [   83.877438]  ? __die+0x24/0x80
  [   83.877442]  ? page_fault_oops+0x99/0x1b0
  [   83.877448]  ? do_user_addr_fault+0x2e2/0x670
  [   83.877453]  ? exc_page_fault+0x83/0x1b0
  [   83.877459]  ? asm_exc_page_fault+0x27/0x30
  [   83.877468]  ? klist_add_tail+0x2a/0x80
  [   83.877473]  device_add+0x590/0x740
  [   83.877479]  cdev_device_add+0x4e/0xc0
  [   83.877483]  ? cdev_init+0x56/0x70
  [   83.877488]  evdev_connect+0x1a9/0x210
  [   83.877493]  input_attach_handler.isra.0+0x84/0xc0
  [   83.877498]  input_register_device+0x231/0x370
  [   83.877505]  notify_handler+0x12e/0x1a0 [intel_vbtn]
  [   83.877514]  acpi_ev_notify_dispatch+0x59/0xa0
  [   83.877520]  acpi_os_exec

[Kernel-packages] [Bug 2060989] Re: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to install/upgrade: installed linux-headers-6.5.0-27-generic package post-installation script subprocess r

2024-04-26 Thread En-Wei Wu

The problem is caused by line 51 in src/dkms.conf (nvidia-fs/2.19.6):
```
BUILD_DEPENDS[0]="nvidia"
```

The `dkms autoinstall` assume we've installed nvidia driver by dkms, but
we're not.

Comment out this line works successfully. I'm wondering if we should
upstream the change.

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

Title:
  package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to
  install/upgrade: installed linux-headers-6.5.0-27-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  In Progress

Bug description:
  -

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-headers-6.5.0-27-generic 6.5.0-27.28
  ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nela   2694 F wireplumber
   /dev/snd/controlC1:  nela   2694 F wireplumber
   /dev/snd/seq:nela   2674 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Thu Apr 11 10:13:36 2024
  ErrorMessage: installed linux-headers-6.5.0-27-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2024-03-30 (12 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic 
root=UUID=e960f11c-d239-429e-97af-9073de7f3b3a ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to 
install/upgrade: installed linux-headers-6.5.0-27-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: HACN27WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion S7 15ACH6
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:
  dmi.product.family: Legion S7 15ACH6
  dmi.product.name: 82K8
  dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6
  dmi.product.version: Legion S7 15ACH6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060989/+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 2060989] Re: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to install/upgrade: installed linux-headers-6.5.0-27-generic package post-installation script subprocess r

2024-04-26 Thread En-Wei Wu

I got the nvidia-fs/2.19.6 from https://github.com/NVIDIA/gds-nvidia-
fs/tree/master.

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

Title:
  package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to
  install/upgrade: installed linux-headers-6.5.0-27-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  In Progress

Bug description:
  -

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-headers-6.5.0-27-generic 6.5.0-27.28
  ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nela   2694 F wireplumber
   /dev/snd/controlC1:  nela   2694 F wireplumber
   /dev/snd/seq:nela   2674 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Thu Apr 11 10:13:36 2024
  ErrorMessage: installed linux-headers-6.5.0-27-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2024-03-30 (12 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic 
root=UUID=e960f11c-d239-429e-97af-9073de7f3b3a ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to 
install/upgrade: installed linux-headers-6.5.0-27-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: HACN27WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion S7 15ACH6
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:
  dmi.product.family: Legion S7 15ACH6
  dmi.product.name: 82K8
  dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6
  dmi.product.version: Legion S7 15ACH6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060989/+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 2060989] Re: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to install/upgrade: installed linux-headers-6.5.0-27-generic package post-installation script subprocess r

2024-04-16 Thread En-Wei Wu

>From the make.log above, it seems that the dkms built nvidia-fs-2.19.6
on 6.5.0-26-generic kernel header. Could you try dkms build the nvidia-
fs-2.19.6 on 6.5.0-27-generic kernel header on your own? (add the -k
6.5.0-27-generic on dkms build)

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

Title:
  package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to
  install/upgrade: installed linux-headers-6.5.0-27-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  In Progress

Bug description:
  -

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-headers-6.5.0-27-generic 6.5.0-27.28
  ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nela   2694 F wireplumber
   /dev/snd/controlC1:  nela   2694 F wireplumber
   /dev/snd/seq:nela   2674 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Thu Apr 11 10:13:36 2024
  ErrorMessage: installed linux-headers-6.5.0-27-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2024-03-30 (12 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic 
root=UUID=e960f11c-d239-429e-97af-9073de7f3b3a ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to 
install/upgrade: installed linux-headers-6.5.0-27-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: HACN27WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion S7 15ACH6
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:
  dmi.product.family: Legion S7 15ACH6
  dmi.product.name: 82K8
  dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6
  dmi.product.version: Legion S7 15ACH6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060989/+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 2060989] Re: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to install/upgrade: installed linux-headers-6.5.0-27-generic package post-installation script subprocess r

2024-04-16 Thread En-Wei Wu

Could you provide the build log of dkms (run by the apt post script)?
Probably in /var/lib/dkms/gds-nvidia-
fs/2.19.6/6.5.0-27-generic/x86_64/log/make.log.

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

Title:
  package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to
  install/upgrade: installed linux-headers-6.5.0-27-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  In Progress

Bug description:
  -

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-headers-6.5.0-27-generic 6.5.0-27.28
  ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nela   2694 F wireplumber
   /dev/snd/controlC1:  nela   2694 F wireplumber
   /dev/snd/seq:nela   2674 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Thu Apr 11 10:13:36 2024
  ErrorMessage: installed linux-headers-6.5.0-27-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2024-03-30 (12 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic 
root=UUID=e960f11c-d239-429e-97af-9073de7f3b3a ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to 
install/upgrade: installed linux-headers-6.5.0-27-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: HACN27WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion S7 15ACH6
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:
  dmi.product.family: Legion S7 15ACH6
  dmi.product.name: 82K8
  dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6
  dmi.product.version: Legion S7 15ACH6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060989/+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 2060989] Re: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to install/upgrade: installed linux-headers-6.5.0-27-generic package post-installation script subprocess r

2024-04-14 Thread En-Wei Wu

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

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

Title:
  package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to
  install/upgrade: installed linux-headers-6.5.0-27-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  In Progress

Bug description:
  -

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-headers-6.5.0-27-generic 6.5.0-27.28
  ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nela   2694 F wireplumber
   /dev/snd/controlC1:  nela   2694 F wireplumber
   /dev/snd/seq:nela   2674 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Thu Apr 11 10:13:36 2024
  ErrorMessage: installed linux-headers-6.5.0-27-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2024-03-30 (12 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic 
root=UUID=e960f11c-d239-429e-97af-9073de7f3b3a ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to 
install/upgrade: installed linux-headers-6.5.0-27-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2021
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: HACN27WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion S7 15ACH6
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:
  dmi.product.family: Legion S7 15ACH6
  dmi.product.name: 82K8
  dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6
  dmi.product.version: Legion S7 15ACH6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060989/+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 2046714] Re: Boot failed, /dev/mapper/ubuntu--vg-ubuntu--lv does not exist.

2023-12-20 Thread Larry Wei

Ok, thanks.

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

Title:
  Boot failed, /dev/mapper/ubuntu--vg-ubuntu--lv does not exist.

Status in linux-meta-starfive package in Ubuntu:
  Invalid

Bug description:
  I have installed Ubuntu Server on My VisionFive v2, the Kernel version is 
6.5.0-14-generic, I notice the new Kernel linux-image-starfive(= 6.5.0.1005.7) 
was released and I upgrade it, and then VisionFive v2 crashes while it boots. 
the initramfs message:
  ALERT!  /dev/mapper/ubuntu--vg-ubuntu--lv does not exist.  Dropping to a 
shell!
  Hope it could be fixed soon. Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-starfive 6.5.0.1005.7
  ProcVersionSignature: Ubuntu 6.5.0-14.14.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic riscv64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: riscv64
  CasperMD5json:
   {
 "result": "skip"
   }
  Date: Mon Dec 18 07:00:45 2023
  InstallationDate: Installed on 2023-09-19 (90 days ago)
  InstallationMedia: Ubuntu-Server 23.10 "Mantic Minotaur" - Release riscv64 
(20231011)
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=tmux-256color
  SourcePackage: linux-meta-starfive
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-starfive/+bug/2046714/+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 2046714] [NEW] Boot failed, /dev/mapper/ubuntu--vg-ubuntu--lv does not exist.

2023-12-17 Thread Larry Wei

Public bug reported:

I have installed Ubuntu Server on My VisionFive v2, the Kernel version is 
6.5.0-14-generic, I notice the new Kernel linux-image-starfive(= 6.5.0.1005.7) 
was released and I upgrade it, and then VisionFive v2 crashes while it boots. 
the initramfs message:
ALERT!  /dev/mapper/ubuntu--vg-ubuntu--lv does not exist.  Dropping to a shell!
Hope it could be fixed soon. Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-starfive 6.5.0.1005.7
ProcVersionSignature: Ubuntu 6.5.0-14.14.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic riscv64
ApportVersion: 2.27.0-0ubuntu5
Architecture: riscv64
CasperMD5json:
 {
   "result": "skip"
 }
Date: Mon Dec 18 07:00:45 2023
InstallationDate: Installed on 2023-09-19 (90 days ago)
InstallationMedia: Ubuntu-Server 23.10 "Mantic Minotaur" - Release riscv64 
(20231011)
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=tmux-256color
SourcePackage: linux-meta-starfive
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug mantic riscv64

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

Title:
  Boot failed, /dev/mapper/ubuntu--vg-ubuntu--lv does not exist.

Status in linux-meta-starfive package in Ubuntu:
  New

Bug description:
  I have installed Ubuntu Server on My VisionFive v2, the Kernel version is 
6.5.0-14-generic, I notice the new Kernel linux-image-starfive(= 6.5.0.1005.7) 
was released and I upgrade it, and then VisionFive v2 crashes while it boots. 
the initramfs message:
  ALERT!  /dev/mapper/ubuntu--vg-ubuntu--lv does not exist.  Dropping to a 
shell!
  Hope it could be fixed soon. Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-starfive 6.5.0.1005.7
  ProcVersionSignature: Ubuntu 6.5.0-14.14.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic riscv64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: riscv64
  CasperMD5json:
   {
 "result": "skip"
   }
  Date: Mon Dec 18 07:00:45 2023
  InstallationDate: Installed on 2023-09-19 (90 days ago)
  InstallationMedia: Ubuntu-Server 23.10 "Mantic Minotaur" - Release riscv64 
(20231011)
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=tmux-256color
  SourcePackage: linux-meta-starfive
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-starfive/+bug/2046714/+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 2046608] [NEW] The fan of VisionFive2 still works after I power it off.

2023-12-16 Thread Larry Wei

Public bug reported:

The fan of VisionFive2 still works after I power it off.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.4
ProcVersionSignature: Ubuntu 6.5.0-14.14.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic riscv64
ApportVersion: 2.27.0-0ubuntu5
Architecture: riscv64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5json:
 {
   "result": "skip"
 }
Date: Sat Dec 16 10:23:41 2023
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1.2
InstallationDate: Installed on 2023-09-19 (88 days ago)
InstallationMedia: Ubuntu-Server 23.10 "Mantic Minotaur" - Release riscv64 
(20231011)
Lspci-vt:
 -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805/806 xHCI USB 3.0 
Controller
 -[0001:00]---00.0-[01]00.0  Silicon Motion, Inc. SM2263EN/SM2263XT 
(DRAM-less) NVMe SSD Controllers
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 
802.11n Wireless Network Adapter
 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
 |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
 |__ Port 4: Dev 3, If 0, Class=Vendor Specific Class, Driver=rtl8xxxu, 
480M
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=tmux-256color
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-6.5.0-14-generic N/A
 linux-backports-modules-6.5.0-14-generic  N/A
 linux-firmware20230919.git3672ccab-0ubuntu2.4
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux-firmware
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:

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


** Tags: apport-bug mantic riscv64

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

Title:
  The fan of VisionFive2 still works after I power it off.

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  The fan of VisionFive2 still works after I power it off.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230919.git3672ccab-0ubuntu2.4
  ProcVersionSignature: Ubuntu 6.5.0-14.14.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic riscv64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: riscv64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5json:
   {
 "result": "skip"
   }
  Date: Sat Dec 16 10:23:41 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1.2
  InstallationDate: Installed on 2023-09-19 (88 days ago)
  InstallationMedia: Ubuntu-Server 23.10 "Mantic Minotaur" - Release riscv64 
(20231011)
  Lspci-vt:
   -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805/806 xHCI USB 
3.0 Controller
   -[0001:00]---00.0-[01]00.0  Silicon Motion, Inc. SM2263EN/SM2263XT 
(DRAM-less) NVMe SSD Controllers
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 
802.11n Wireless Network Adapter
   Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
   |__ Port 4: Dev 3, If 0, Class=Vendor Specific Class, 
Driver=rtl8xxxu, 480M
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=tmux-256color
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.4
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:

To manage notifications about this bug go to

[Kernel-packages] [Bug 2009496] Re: Backlight Adjusting doesn't work for linux-image-6.1.0-16-generic.

2023-03-06 Thread Larry Wei

** Description changed:

  Backlight Adjusting doesn't work for linux-image-6.1.0-16-generic.
  
- My laptop is under `Software Rendering`, after I upgraded Ubuntu 22.10
- to 23.04, the brightness adjusting is unavailable and my monitor is much
- bright. However I change the Kernel to `linux-image-5.19.0-35-generic`,
- the backlight adjusting works normally,
+ My laptop is under `Software Rendering`(GPU: llvmpipe (LLVM 15.0.7, 256
+ bits)), after I upgraded Ubuntu 22.10 to 23.04, the brightness adjusting
+ is unavailable and my monitor is much bright. However I change the
+ Kernel to `linux-image-5.19.0-35-generic`, the backlight adjusting works
+ normally,
  
  The `lshw display` information:
  $ sudo lshw -c display
    *-display UNCLAIMED
     description: VGA compatible controller
     product: ZX-E C-960 GPU
     vendor: Zhaoxin
     physical id: 1
     bus info: pci@:00:01.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi vga_controller bus_master cap_list
     configuration: latency=0
     resources: memory:c010-c017 memory:a000-bfff 
memory:c-d
    *-graphics
     product: EFI VGA
     physical id: 2
     logical name: /dev/fb0
     capabilities: fb
     configuration: depth=32 resolution=1920,1080
  
  Hope I can get some help.
  
  Regards，
  larryw3i

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

Title:
  Backlight Adjusting doesn't  work for linux-image-6.1.0-16-generic.

Status in linux-signed package in Ubuntu:
  New

Bug description:
  Backlight Adjusting doesn't work for linux-image-6.1.0-16-generic.

  My laptop is under `Software Rendering`(GPU: llvmpipe (LLVM 15.0.7,
  256 bits)), after I upgraded Ubuntu 22.10 to 23.04, the brightness
  adjusting is unavailable and my monitor is much bright. However I
  change the Kernel to `linux-image-5.19.0-35-generic`, the backlight
  adjusting works normally,

  The `lshw display` information:
  $ sudo lshw -c display
    *-display UNCLAIMED
     description: VGA compatible controller
     product: ZX-E C-960 GPU
     vendor: Zhaoxin
     physical id: 1
     bus info: pci@:00:01.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi vga_controller bus_master cap_list
     configuration: latency=0
     resources: memory:c010-c017 memory:a000-bfff 
memory:c-d
    *-graphics
     product: EFI VGA
     physical id: 2
     logical name: /dev/fb0
     capabilities: fb
     configuration: depth=32 resolution=1920,1080

  Hope I can get some help.

  Regards，
  larryw3i

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2009496/+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 2009496] [NEW] Backlight Adjusting doesn't work for linux-image-6.1.0-16-generic.

2023-03-06 Thread Larry Wei

Public bug reported:

Backlight Adjusting doesn't work for linux-image-6.1.0-16-generic.

My laptop is under `Software Rendering`, after I upgraded Ubuntu 22.10
to 23.04, the brightness adjusting is unavailable and my monitor is much
bright. However I change the Kernel to `linux-image-5.19.0-35-generic`,
the backlight adjusting works normally,

The `lshw display` information:
$ sudo lshw -c display
  *-display UNCLAIMED
   description: VGA compatible controller
   product: ZX-E C-960 GPU
   vendor: Zhaoxin
   physical id: 1
   bus info: pci@:00:01.0
   version: 00
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi vga_controller bus_master cap_list
   configuration: latency=0
   resources: memory:c010-c017 memory:a000-bfff 
memory:c-d
  *-graphics
   product: EFI VGA
   physical id: 2
   logical name: /dev/fb0
   capabilities: fb
   configuration: depth=32 resolution=1920,1080

Hope I can get some help.

Regards，
larryw3i

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

** Summary changed:

- Backlight Adjusting doesn't for linux-image-6.1.0-16-generic.
+ Backlight Adjusting doesn't  work for linux-image-6.1.0-16-generic.

** Description changed:

- Backlight Adjusting doesn't for linux-image-6.1.0-16-generic.
+ Backlight Adjusting doesn't work for linux-image-6.1.0-16-generic.
  
  My laptop is under `Software Rendering`, after I upgraded Ubuntu 22.10
  to 23.04, the brightness adjusting is unavailable and my monitor is much
  bright. However I change the Kernel to `linux-image-5.19.0-35-generic`,
  the backlight adjusting works normally,
  
- The `lshw display` information:  
+ The `lshw display` information:
  $ sudo lshw -c display
-   *-display UNCLAIMED   
-description: VGA compatible controller
-product: ZX-E C-960 GPU
-vendor: Zhaoxin
-physical id: 1
-bus info: pci@:00:01.0
-version: 00
-width: 64 bits
-clock: 33MHz
-capabilities: pm msi vga_controller bus_master cap_list
-configuration: latency=0
-resources: memory:c010-c017 memory:a000-bfff 
memory:c-d
-   *-graphics
-product: EFI VGA
-physical id: 2
-logical name: /dev/fb0
-capabilities: fb
-configuration: depth=32 resolution=1920,1080
+   *-display UNCLAIMED
+    description: VGA compatible controller
+    product: ZX-E C-960 GPU
+    vendor: Zhaoxin
+    physical id: 1
+    bus info: pci@:00:01.0
+    version: 00
+    width: 64 bits
+    clock: 33MHz
+    capabilities: pm msi vga_controller bus_master cap_list
+    configuration: latency=0
+    resources: memory:c010-c017 memory:a000-bfff 
memory:c-d
+   *-graphics
+    product: EFI VGA
+    physical id: 2
+    logical name: /dev/fb0
+    capabilities: fb
+    configuration: depth=32 resolution=1920,1080
  
  Hope I can get some help.
  
  Regards，
  larryw3i

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

Title:
  Backlight Adjusting doesn't  work for linux-image-6.1.0-16-generic.

Status in linux-signed package in Ubuntu:
  New

Bug description:
  Backlight Adjusting doesn't work for linux-image-6.1.0-16-generic.

  My laptop is under `Software Rendering`, after I upgraded Ubuntu 22.10
  to 23.04, the brightness adjusting is unavailable and my monitor is
  much bright. However I change the Kernel to `linux-
  image-5.19.0-35-generic`, the backlight adjusting works normally,

  The `lshw display` information:
  $ sudo lshw -c display
    *-display UNCLAIMED
     description: VGA compatible controller
     product: ZX-E C-960 GPU
     vendor: Zhaoxin
     physical id: 1
     bus info: pci@:00:01.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi vga_controller bus_master cap_list
     configuration: latency=0
     resources: memory:c010-c017 memory:a000-bfff 
memory:c-d
    *-graphics
     product: EFI VGA
     physical id: 2
     logical name: /dev/fb0
     capabilities: fb
     configuration: depth=32 resolution=1920,1080

  Hope I can get some help.

  Regards，
  larryw3i

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2009496/+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 2008882] Re: Remove all other acpi_video backlight interface on Dell AIO platforms

2023-03-06 Thread Larry Wei

Hopeful! My screen is much bright and I have to stop my job!

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

Title:
  Remove all other acpi_video backlight interface on Dell AIO platforms

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 source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  In Progress
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  There are acpi_video* sysfs backlight interface in the system which are not 
working.
  For Dell AIO platforms, we use dell_uart_backlight to control the display 
brightness.
  The old way to fix this is to unregister acpi backlight interfaces in the 
backlight driver, but it may lead to some issues and the unregister function 
has been removed since v6.1-rc1
  77ab9d4d44cd ("ACPI: video: Remove acpi_video_set_dmi_backlight_type()")

  [Fix]
  The new way to do this is to collect all the quirk and auto detection method 
in video_detect.c
  I added an audo detection for the Dell AIO platoform to the driver which 
should do the same thing as the old way.

  [Test]
  Verified on the Dell AIO platform and confirmed there is only on 
dell_uart_backlight in the sysfs, and no acpi_video* interface.

  [Where problems could occur]
  There should be no regression potential, it uses different way to do the same 
thing, should be pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2008882/+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 2008882] Re: Remove all other acpi_video backlight interface on Dell AIO platforms

2023-03-05 Thread Larry Wei

After upgrading Ubuntu to `Lunar Lobster`, I couldn't adjust the
brightness of my laptop under `Software Rendering` now😥.

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

Title:
  Remove all other acpi_video backlight interface on Dell AIO platforms

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 source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  In Progress
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  There are acpi_video* sysfs backlight interface in the system which are not 
working.
  For Dell AIO platforms, we use dell_uart_backlight to control the display 
brightness.
  The old way to fix this is to unregister acpi backlight interfaces in the 
backlight driver, but it may lead to some issues and the unregister function 
has been removed since v6.1-rc1
  77ab9d4d44cd ("ACPI: video: Remove acpi_video_set_dmi_backlight_type()")

  [Fix]
  The new way to do this is to collect all the quirk and auto detection method 
in video_detect.c
  I added an audo detection for the Dell AIO platoform to the driver which 
should do the same thing as the old way.

  [Test]
  Verified on the Dell AIO platform and confirmed there is only on 
dell_uart_backlight in the sysfs, and no acpi_video* interface.

  [Where problems could occur]
  There should be no regression potential, it uses different way to do the same 
thing, should be pretty safe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2008882/+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 2000418] [NEW] Linux Image 5.15.0-56.62 (Jammy) crashes Surface Book 2

2022-12-24 Thread Wei Tsui

Public bug reported:

Problem Version:
  linux (5.15.0-56.62) jammy; urgency=medium

Good Version:
  linux (5.15.0-53.59) jammy; urgency=medium

Laptop:
  Microsoft Surface Book 2

OS Used:
  Ubuntu 22.04 x86_64

Descripe:
  Ubuntu 22.04 ran well on Surface Book 2 until linux-image==5.15.0-53.59. 
Yesterday I upgrade the latest kernel 5.15.0-56.62 and then graphic driver is 
totally crashed. I have to fall back to use 5.15.0-53.59 instead.

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

** Summary changed:

- Upgrade to 
+ Linux Image 5.15.0-56.62 (Jammy) crashes Surface Book 2

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

Title:
  Linux Image 5.15.0-56.62 (Jammy) crashes Surface Book 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Problem Version:
linux (5.15.0-56.62) jammy; urgency=medium

  Good Version:
linux (5.15.0-53.59) jammy; urgency=medium

  Laptop:
Microsoft Surface Book 2

  OS Used:
Ubuntu 22.04 x86_64

  Descripe:
Ubuntu 22.04 ran well on Surface Book 2 until linux-image==5.15.0-53.59. 
Yesterday I upgrade the latest kernel 5.15.0-56.62 and then graphic driver is 
totally crashed. I have to fall back to use 5.15.0-53.59 instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000418/+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 1959728] Re: trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

2022-08-18 Thread Wei

I am pretty sure ``the Sensel Forcepad Device Firmware'' does not
available outside Windows, at least they are not listed on the support
page posted by Alan.

I suggest you can set up a dual boot and install Windows. It is likely
windows will be automatically activated. I guess many firmware updates
might only be available in windows.

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

Title:
  trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my X1 Yoga Titanium (which has a fancy new "Sensel" trackpad with
  haptic response to clicks), the trackpad stops working after a
  suspend/resume cycle, although the red trackpoint continues to work
  fine for controlling the pointer.  I believe this system is using S0i3
  for suspend, in case that's relevant.

  If I boot from power off, then the trackpad works fine in both the
  pre-boot BIOS and in Ubuntu 22.04 (prerelease), including haptic
  response to clicks.  After a suspend/resume cycle, the trackpad stops
  responding, although a lot of swiping/pressing will occasionally
  produce a button press event.  This state persists even if I reboot
  out of Linux (without a power cycle) - for example the trackpad no
  longer works for the pre-boot BIOS configuration screen, until a full
  power cycle (which fixes the trackpad).

  Possibly relevant, the trackpad seems to be this device to the kernel:

  [2.016917] input: SNSL0001:00 2C2F:0006 Mouse as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input6
  [2.016964] input: SNSL0001:00 2C2F:0006 Touchpad as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input7
  [2.017027] hid-generic 0018:2C2F:0006.0001: input,hidraw0: I2C HID v1.00 
Mouse [SNSL0001:00 2C2F:0006] on i2c-SNSL0001:00

  and the last kernel messages before suspend are:

  [  305.216189] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [  305.217435] printk: Suspending console(s) (use no_console_suspend to debug)
  [  305.274332] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: lost 
arbitration
  [  306.030947] i2c_hid_acpi i2c-SNSL0001:00: failed to set a report to device.
  [  306.616463] ACPI: EC: interrupt blocked
  [  331.551118] ACPI: EC: interrupt unblocked

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bina   1543 F pipewire
bina   1544 F pipewire-media-
bina   1545 F pulseaudio
   /dev/snd/seq:bina   1543 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  1 14:54:14 2022
  InstallationDate: Installed on 2022-02-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  MachineType: LENOVO 20QA000EUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-18-generic N/A
   linux-backports-modules-5.15.0-18-generic  N/A
   linux-firmware 20220124.git0c6a7b3b-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2021
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2MET53W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QA000EUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2MET53W(1.18):bd09/30/2021:br1.18:efr1.11:svnLENOVO:pn20QA000EUS:pvrThinkPadX1TitaniumGen1:rvnLENOVO:rn20QA000EUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20QA_BU_Think_FM_ThinkPadX1TitaniumGen1:
  dmi.product.family: ThinkPad X1 Titanium Gen 1
  dmi.product.name: 20QA000EUS
  dmi.product.sku: LENOVO_MT_20QA_BU_Think_FM_ThinkPad X1 Titanium Gen 1
  dmi.product.version: ThinkPad X1 Titanium Gen 1
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1959728] Re: trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

2022-08-17 Thread Wei

I shall confirm that after the fix mentioned above, my trackpad has been 
working very well.
I think that is a software issue.
I have some suggestions to try:
- verify if this issue happens also in windows?
- try update all drivers using the tools provided by Lenovo
- maybe update BIOS
- in Windows, there is the Senel driver software, launch it, see their menu, 
look for something that may make a change
- stay in Windows for it to automatically update
- update Ubuntu (which I think you must have already did), I am using 20.04

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

Title:
  trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my X1 Yoga Titanium (which has a fancy new "Sensel" trackpad with
  haptic response to clicks), the trackpad stops working after a
  suspend/resume cycle, although the red trackpoint continues to work
  fine for controlling the pointer.  I believe this system is using S0i3
  for suspend, in case that's relevant.

  If I boot from power off, then the trackpad works fine in both the
  pre-boot BIOS and in Ubuntu 22.04 (prerelease), including haptic
  response to clicks.  After a suspend/resume cycle, the trackpad stops
  responding, although a lot of swiping/pressing will occasionally
  produce a button press event.  This state persists even if I reboot
  out of Linux (without a power cycle) - for example the trackpad no
  longer works for the pre-boot BIOS configuration screen, until a full
  power cycle (which fixes the trackpad).

  Possibly relevant, the trackpad seems to be this device to the kernel:

  [2.016917] input: SNSL0001:00 2C2F:0006 Mouse as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input6
  [2.016964] input: SNSL0001:00 2C2F:0006 Touchpad as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input7
  [2.017027] hid-generic 0018:2C2F:0006.0001: input,hidraw0: I2C HID v1.00 
Mouse [SNSL0001:00 2C2F:0006] on i2c-SNSL0001:00

  and the last kernel messages before suspend are:

  [  305.216189] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [  305.217435] printk: Suspending console(s) (use no_console_suspend to debug)
  [  305.274332] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: lost 
arbitration
  [  306.030947] i2c_hid_acpi i2c-SNSL0001:00: failed to set a report to device.
  [  306.616463] ACPI: EC: interrupt blocked
  [  331.551118] ACPI: EC: interrupt unblocked

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bina   1543 F pipewire
bina   1544 F pipewire-media-
bina   1545 F pulseaudio
   /dev/snd/seq:bina   1543 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  1 14:54:14 2022
  InstallationDate: Installed on 2022-02-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  MachineType: LENOVO 20QA000EUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-18-generic N/A
   linux-backports-modules-5.15.0-18-generic  N/A
   linux-firmware 20220124.git0c6a7b3b-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2021
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2MET53W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QA000EUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2MET53W(1.18):bd09/30/2021:br1.18:efr1.11:svnLENOVO:pn20QA000EUS:pvrThinkPadX1TitaniumGen1:rvnLENOVO:rn20QA000EUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20QA_BU_Think_FM_ThinkPadX1TitaniumGen1:
  dmi.product.family: ThinkPad X1 Titanium Gen 1
  dmi.product.name: 20QA000EUS
  dmi.product.sku: LENOVO_MT_20QA_BU_Think_FM_ThinkPad X1 Titanium Gen 1
  dmi.product.version: ThinkPad X1 Titanium Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.la

[Kernel-packages] [Bug 1980884] Re: ubuntu guest kernel panics when a sev guest with passthrough mlx5 VF is used

2022-08-01 Thread Si-Wei Liu

It is verified SEV works for the v5.15 kernel where we wants SEV to be
supported. Closing this one for v5.11 now.

** Changed in: linux-oracle-5.11 (Ubuntu)
   Status: New => Invalid

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

Title:
  ubuntu guest kernel panics when a sev guest with passthrough mlx5 VF
  is used

Status in linux-oracle-5.11 package in Ubuntu:
  Invalid

Bug description:
  Guest kernel panic can be observed when Ubuntu SEV guest with mlx5 vfio-pci 
is started
  as iperf3 server using "iperf3 -s" and as soon as the client tries to connect
  with it.

  Steps to reproduce:

  HOST INFO
  Host type : OCI (Oracle Cloud) Bare-Metal Server
  Server/Machine: ORACLE SERVER E4-2c
  CPU model : AMD EPYC 7J13 64-Core Processor
  Architecture  : x86_64
  Host OS   : Oracle Linux Server release 7.9
  Host Kernel   : 5.4.17-2136.309.3.el7uek.x86_64 #2 SMP Tue Jun 14 21:58:29 
PDT 2022
  Hypervisor: QEMU emulator version 4.2.1 (qemu-4.2.1-17.1.el7)
  OVMF/AAVMF: OVMF-1.6.2-2.el7.noarch
  libiscsi  : libiscsi-1.19.0-1.el7.x86_64
  Guest Kernel  : 5.11.0-1028-ORACLE

  1) Start Ubuntu 20.04/18.04 SEV guest with vfio-pci:

  /usr/bin/qemu-system-x86_64 -machine q35 -name OL20.04-uefi -enable-kvm
  -nodefaults -cpu host,+host-phys-bits -m 8G -smp 8,maxcpus=240 -monitor stdio
  -vnc 0.0.0.0:0,to=999 -vga std -drive
  
file=/usr/share/OVMF/OVMF_CODE.pure-efi.fd,index=0,if=pflash,format=raw,readonly
 -drive file=OVMF_VARS.pure-efi.fd.ol20.04,index=1,if=pflash,format=raw
  -device
  virtio-scsi-pci,id=virtio-scsi-pci0,disable-legacy=on,iommu_platform=true
  -drive
  
file=/systest/atanveer/scripts/Ubuntu-20.04-2022.02.15-0-uefi-x86_64.qcow2,if=none,id=local_disk0,format=qcow2,media=disk
 -device
  ide-hd,drive=local_disk0,id=local_disk1,bootindex=0  -net none -device
  vfio-pci,host=:21:10.1 -qmp tcp:127.0.0.1:3334,server,nowait -serial
  telnet:127.0.0.1:,server,nowait  -D ./OL20.04-uefi.log -device
  virtio-rng-pci,disable-legacy=on,iommu_platform=true -object
  sev-guest,id=sev0,cbitpos=51,reduced-phys-bits=1 -machine
  memory-encryption=sev0

  2) Start a client guest OL/Ubuntu:

  /usr/bin/qemu-system-x86_64 -machine q35 -name OL18.04-uefi -enable-kvm
  -nodefaults -cpu host,+host-phys-bits -m 8G -smp 8,maxcpus=240 -monitor stdio
  -vnc 0.0.0.0:0,to=999 -vga std -drive
  
file=/usr/share/OVMF/OVMF_CODE.pure-efi.fd,index=0,if=pflash,format=raw,readonly
 -drive file=OVMF_VARS.pure-efi.fd.ol18.04,index=1,if=pflash,format=raw
  -device
  virtio-scsi-pci,id=virtio-scsi-pci0,disable-legacy=on,iommu_platform=true
  -drive
  
file=/systest/atanveer/scripts/Ubuntu-18.04-2022.02.13-0-uefi-x86_64.qcow2,if=none,id=local_disk0,format=qcow2,media=disk
 -device
  ide-hd,drive=local_disk0,id=local_disk1,bootindex=0  -net none -device
  vfio-pci,host=:21:10.2 -qmp tcp:127.0.0.1:,server,nowait -serial
  telnet:127.0.0.1:,server,nowait  -D ./OL18.04-uefi.log -device
  virtio-rng-pci,disable-legacy=on,iommu_platform=true -object
  sev-guest,id=sev0,cbitpos=51,reduced-phys-bits=1 -machine
  memory-encryption=sev0

  3) Flush iptables on both the VMs using "iptables -F"

  4) Start the iperf3 server on the first VM using "iperf3 -s"

  5) Start the iperf3 client on the second VM using "iperf3 -c  -4
  -f M -i 0 -t 70 -O 10 -P 64"

  The kernel panic is seen on the first VM i.e. Ubuntu 20.04 with iperf3 also
  showing "Bad Address" error.

  Console logs:

  root@ubuntu-20-04:~# iperf3 -s
  ---
  Server listening on 5201
  ---
  Accepted connection from 10.196.246.104, port 33732
  [  5] local 10.196.247.88 port 5201 connected to 10.196.246.104 port 33734
  [  8] local 10.196.247.88 port 5201 connected to 10.196.246.104 port 33736
  [ 10] local 10.196.247.88 port 5201 connected to 10.196.246.104 port 33738
  iperf3: error - unable to read from stream socket: Bad address
  ---
  Server listening on 5201
  ---
  [   91.083856] general protection fault:  [#1] SMP NOPTI
  [   91.084591] CPU: 4 PID: 0 Comm: swapper/4 Not tainted 5.11.0-1028-oracle
  #31~20.04.1-Ubuntu
  [   91.085393] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.6.2
  06/01/2022
  [   91.086205] RIP: 0010:memcpy_erms+0x6/0x10
  [   91.086640] Code: cc cc cc cc eb 1e 0f 1f 00 48 89 f8 48 89 d1 48 c1 e9 03
  83 e2 07 f3 48 a5 89 d1 f3 a4 c3 66 0f 1f 44 00 00 48 89 f8 48 89 d1  a4
  c3 0f 1f 80 00 00 00 00 48 89 f8 48 83 fa 20 72 7e 40 38 fe
  [   91.088559] RSP: 0018:a9c1408e4b60 EFLAGS: 00010282
  [   91.089105] RAX: 938cd8e48000 RBX: 1000 RCX:
  1000
  [   91.089843] RDX: 1000 RSI: bb6

[Kernel-packages] [Bug 1980884] Re: ubuntu guest kernel panics when a sev guest with passthrough mlx5 VF is used

2022-07-21 Thread Si-Wei Liu

Thanks for the info, Fabio. I didn't realize the 5.11 kernel is past EoL
already. I'll ask the team to check the result on v5.4 and v5.15 kernel.
Stay tuned.

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

Title:
  ubuntu guest kernel panics when a sev guest with passthrough mlx5 VF
  is used

Status in linux-oracle-5.11 package in Ubuntu:
  New

Bug description:
  Guest kernel panic can be observed when Ubuntu SEV guest with mlx5 vfio-pci 
is started
  as iperf3 server using "iperf3 -s" and as soon as the client tries to connect
  with it.

  Steps to reproduce:

  HOST INFO
  Host type : OCI (Oracle Cloud) Bare-Metal Server
  Server/Machine: ORACLE SERVER E4-2c
  CPU model : AMD EPYC 7J13 64-Core Processor
  Architecture  : x86_64
  Host OS   : Oracle Linux Server release 7.9
  Host Kernel   : 5.4.17-2136.309.3.el7uek.x86_64 #2 SMP Tue Jun 14 21:58:29 
PDT 2022
  Hypervisor: QEMU emulator version 4.2.1 (qemu-4.2.1-17.1.el7)
  OVMF/AAVMF: OVMF-1.6.2-2.el7.noarch
  libiscsi  : libiscsi-1.19.0-1.el7.x86_64
  Guest Kernel  : 5.11.0-1028-ORACLE

  1) Start Ubuntu 20.04/18.04 SEV guest with vfio-pci:

  /usr/bin/qemu-system-x86_64 -machine q35 -name OL20.04-uefi -enable-kvm
  -nodefaults -cpu host,+host-phys-bits -m 8G -smp 8,maxcpus=240 -monitor stdio
  -vnc 0.0.0.0:0,to=999 -vga std -drive
  
file=/usr/share/OVMF/OVMF_CODE.pure-efi.fd,index=0,if=pflash,format=raw,readonly
 -drive file=OVMF_VARS.pure-efi.fd.ol20.04,index=1,if=pflash,format=raw
  -device
  virtio-scsi-pci,id=virtio-scsi-pci0,disable-legacy=on,iommu_platform=true
  -drive
  
file=/systest/atanveer/scripts/Ubuntu-20.04-2022.02.15-0-uefi-x86_64.qcow2,if=none,id=local_disk0,format=qcow2,media=disk
 -device
  ide-hd,drive=local_disk0,id=local_disk1,bootindex=0  -net none -device
  vfio-pci,host=:21:10.1 -qmp tcp:127.0.0.1:3334,server,nowait -serial
  telnet:127.0.0.1:,server,nowait  -D ./OL20.04-uefi.log -device
  virtio-rng-pci,disable-legacy=on,iommu_platform=true -object
  sev-guest,id=sev0,cbitpos=51,reduced-phys-bits=1 -machine
  memory-encryption=sev0

  2) Start a client guest OL/Ubuntu:

  /usr/bin/qemu-system-x86_64 -machine q35 -name OL18.04-uefi -enable-kvm
  -nodefaults -cpu host,+host-phys-bits -m 8G -smp 8,maxcpus=240 -monitor stdio
  -vnc 0.0.0.0:0,to=999 -vga std -drive
  
file=/usr/share/OVMF/OVMF_CODE.pure-efi.fd,index=0,if=pflash,format=raw,readonly
 -drive file=OVMF_VARS.pure-efi.fd.ol18.04,index=1,if=pflash,format=raw
  -device
  virtio-scsi-pci,id=virtio-scsi-pci0,disable-legacy=on,iommu_platform=true
  -drive
  
file=/systest/atanveer/scripts/Ubuntu-18.04-2022.02.13-0-uefi-x86_64.qcow2,if=none,id=local_disk0,format=qcow2,media=disk
 -device
  ide-hd,drive=local_disk0,id=local_disk1,bootindex=0  -net none -device
  vfio-pci,host=:21:10.2 -qmp tcp:127.0.0.1:,server,nowait -serial
  telnet:127.0.0.1:,server,nowait  -D ./OL18.04-uefi.log -device
  virtio-rng-pci,disable-legacy=on,iommu_platform=true -object
  sev-guest,id=sev0,cbitpos=51,reduced-phys-bits=1 -machine
  memory-encryption=sev0

  3) Flush iptables on both the VMs using "iptables -F"

  4) Start the iperf3 server on the first VM using "iperf3 -s"

  5) Start the iperf3 client on the second VM using "iperf3 -c  -4
  -f M -i 0 -t 70 -O 10 -P 64"

  The kernel panic is seen on the first VM i.e. Ubuntu 20.04 with iperf3 also
  showing "Bad Address" error.

  Console logs:

  root@ubuntu-20-04:~# iperf3 -s
  ---
  Server listening on 5201
  ---
  Accepted connection from 10.196.246.104, port 33732
  [  5] local 10.196.247.88 port 5201 connected to 10.196.246.104 port 33734
  [  8] local 10.196.247.88 port 5201 connected to 10.196.246.104 port 33736
  [ 10] local 10.196.247.88 port 5201 connected to 10.196.246.104 port 33738
  iperf3: error - unable to read from stream socket: Bad address
  ---
  Server listening on 5201
  ---
  [   91.083856] general protection fault:  [#1] SMP NOPTI
  [   91.084591] CPU: 4 PID: 0 Comm: swapper/4 Not tainted 5.11.0-1028-oracle
  #31~20.04.1-Ubuntu
  [   91.085393] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.6.2
  06/01/2022
  [   91.086205] RIP: 0010:memcpy_erms+0x6/0x10
  [   91.086640] Code: cc cc cc cc eb 1e 0f 1f 00 48 89 f8 48 89 d1 48 c1 e9 03
  83 e2 07 f3 48 a5 89 d1 f3 a4 c3 66 0f 1f 44 00 00 48 89 f8 48 89 d1  a4
  c3 0f 1f 80 00 00 00 00 48 89 f8 48 83 fa 20 72 7e 40 38 fe
  [   91.088559] RSP: 0018:a9c1408e4b60 EFLAGS: 00010282
  [   91.089105] RAX: 938cd8e48000 RBX: 1000 RCX:
  1000
  [   91.089843] RDX: 1000 RSI: bb62fcf4fd5bf3d6 RDI:
  938cd8e4

[Kernel-packages] [Bug 1980884] Re: ubuntu guest kernel panics when a sev guest with passthrough mlx5 VF is used

2022-07-08 Thread Si-Wei Liu

** Description changed:

  Guest kernel panic can be observed when Ubuntu SEV guest with mlx5 vfio-pci 
is started
  as iperf3 server using "iperf3 -s" and as soon as the client tries to connect
  with it.
  
  Steps to reproduce:
  
  HOST INFO
  Host type : OCI (Oracle Cloud) Bare-Metal Server
  Server/Machine: ORACLE SERVER E4-2c
  CPU model : AMD EPYC 7J13 64-Core Processor
  Architecture  : x86_64
  Host OS   : Oracle Linux Server release 7.9
  Host Kernel   : 5.4.17-2136.309.3.el7uek.x86_64 #2 SMP Tue Jun 14 21:58:29 
PDT 2022
- Hypervisor: QEMU emulator version 4.2.1 (qemu-4.2.1-17.1.oci.el7)
+ Hypervisor: QEMU emulator version 4.2.1 (qemu-4.2.1-17.1.el7)
  OVMF/AAVMF: OVMF-1.6.2-2.el7.noarch
- libiscsi  : libiscsi-1.19.0-1.oci.el7.x86_64
+ libiscsi  : libiscsi-1.19.0-1.el7.x86_64
  Guest Kernel  : 5.11.0-1028-ORACLE
  
  1) Start Ubuntu 20.04/18.04 SEV guest with vfio-pci:
  
  /usr/bin/qemu-system-x86_64 -machine q35 -name OL20.04-uefi -enable-kvm
  -nodefaults -cpu host,+host-phys-bits -m 8G -smp 8,maxcpus=240 -monitor stdio
  -vnc 0.0.0.0:0,to=999 -vga std -drive
  
file=/usr/share/OVMF/OVMF_CODE.pure-efi.fd,index=0,if=pflash,format=raw,readonly
 -drive file=OVMF_VARS.pure-efi.fd.ol20.04,index=1,if=pflash,format=raw
  -device
  virtio-scsi-pci,id=virtio-scsi-pci0,disable-legacy=on,iommu_platform=true
  -drive
  
file=/systest/atanveer/scripts/Ubuntu-20.04-2022.02.15-0-uefi-x86_64.qcow2,if=none,id=local_disk0,format=qcow2,media=disk
 -device
  ide-hd,drive=local_disk0,id=local_disk1,bootindex=0  -net none -device
  vfio-pci,host=:21:10.1 -qmp tcp:127.0.0.1:3334,server,nowait -serial
  telnet:127.0.0.1:,server,nowait  -D ./OL20.04-uefi.log -device
  virtio-rng-pci,disable-legacy=on,iommu_platform=true -object
  sev-guest,id=sev0,cbitpos=51,reduced-phys-bits=1 -machine
  memory-encryption=sev0
  
  2) Start a client guest OL/Ubuntu:
  
  /usr/bin/qemu-system-x86_64 -machine q35 -name OL18.04-uefi -enable-kvm
  -nodefaults -cpu host,+host-phys-bits -m 8G -smp 8,maxcpus=240 -monitor stdio
  -vnc 0.0.0.0:0,to=999 -vga std -drive
  
file=/usr/share/OVMF/OVMF_CODE.pure-efi.fd,index=0,if=pflash,format=raw,readonly
 -drive file=OVMF_VARS.pure-efi.fd.ol18.04,index=1,if=pflash,format=raw
  -device
  virtio-scsi-pci,id=virtio-scsi-pci0,disable-legacy=on,iommu_platform=true
  -drive
  
file=/systest/atanveer/scripts/Ubuntu-18.04-2022.02.13-0-uefi-x86_64.qcow2,if=none,id=local_disk0,format=qcow2,media=disk
 -device
  ide-hd,drive=local_disk0,id=local_disk1,bootindex=0  -net none -device
  vfio-pci,host=:21:10.2 -qmp tcp:127.0.0.1:,server,nowait -serial
  telnet:127.0.0.1:,server,nowait  -D ./OL18.04-uefi.log -device
  virtio-rng-pci,disable-legacy=on,iommu_platform=true -object
  sev-guest,id=sev0,cbitpos=51,reduced-phys-bits=1 -machine
  memory-encryption=sev0
  
  3) Flush iptables on both the VMs using "iptables -F"
  
  4) Start the iperf3 server on the first VM using "iperf3 -s"
  
  5) Start the iperf3 client on the second VM using "iperf3 -c  -4
  -f M -i 0 -t 70 -O 10 -P 64"
  
  The kernel panic is seen on the first VM i.e. Ubuntu 20.04 with iperf3 also
  showing "Bad Address" error.
  
  Console logs:
  
  root@ubuntu-20-04:~# iperf3 -s
  ---
  Server listening on 5201
  ---
  Accepted connection from 10.196.246.104, port 33732
  [  5] local 10.196.247.88 port 5201 connected to 10.196.246.104 port 33734
  [  8] local 10.196.247.88 port 5201 connected to 10.196.246.104 port 33736
  [ 10] local 10.196.247.88 port 5201 connected to 10.196.246.104 port 33738
  iperf3: error - unable to read from stream socket: Bad address
  ---
  Server listening on 5201
  ---
  [   91.083856] general protection fault:  [#1] SMP NOPTI
  [   91.084591] CPU: 4 PID: 0 Comm: swapper/4 Not tainted 5.11.0-1028-oracle
  #31~20.04.1-Ubuntu
  [   91.085393] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.6.2
  06/01/2022
  [   91.086205] RIP: 0010:memcpy_erms+0x6/0x10
  [   91.086640] Code: cc cc cc cc eb 1e 0f 1f 00 48 89 f8 48 89 d1 48 c1 e9 03
  83 e2 07 f3 48 a5 89 d1 f3 a4 c3 66 0f 1f 44 00 00 48 89 f8 48 89 d1  a4
  c3 0f 1f 80 00 00 00 00 48 89 f8 48 83 fa 20 72 7e 40 38 fe
  [   91.088559] RSP: 0018:a9c1408e4b60 EFLAGS: 00010282
  [   91.089105] RAX: 938cd8e48000 RBX: 1000 RCX:
  1000
  [   91.089843] RDX: 1000 RSI: bb62fcf4fd5bf3d6 RDI:
  938cd8e48000
  [   91.090578] RBP: a9c1408e4c00 R08: ef2745639200 R09:
  
  [   91.091309] R10: ef27456399c8 R11: 4209 R12:
  1000
  [   91.092043] R13: ef2745639200 R14: 1000 R15:
  0d558380
  [   91.092782] FS:  () GS:938df430

[Kernel-packages] [Bug 1980884] Re: ubuntu guest kernel panics when a sev guest with passthrough mlx5 VF is used

2022-07-08 Thread Si-Wei Liu

** Description changed:

  Guest kernel panic can be observed when Ubuntu SEV guest with mlx5 vfio-pci 
is started
  as iperf3 server using "iperf3 -s" and as soon as the client tries to connect
  with it.
  
  Steps to reproduce:
  
  HOST INFO
  Host type : OCI (Oracle Cloud) Bare-Metal Server
  Server/Machine: ORACLE SERVER E4-2c
  CPU model : AMD EPYC 7J13 64-Core Processor
  Architecture  : x86_64
  Host OS   : Oracle Linux Server release 7.9
  Host Kernel   : 5.4.17-2136.309.3.el7uek.x86_64 #2 SMP Tue Jun 14 21:58:29 
PDT 2022
  Hypervisor: QEMU emulator version 4.2.1 (qemu-4.2.1-17.1.oci.el7)
  OVMF/AAVMF: OVMF-1.6.2-2.el7.noarch
  libiscsi  : libiscsi-1.19.0-1.oci.el7.x86_64
  Guest Kernel  : 5.11.0-1028-ORACLE
  
- 
  1) Start Ubuntu 20.04/18.04 SEV guest with vfio-pci:
  
  /usr/bin/qemu-system-x86_64 -machine q35 -name OL20.04-uefi -enable-kvm
  -nodefaults -cpu host,+host-phys-bits -m 8G -smp 8,maxcpus=240 -monitor stdio
  -vnc 0.0.0.0:0,to=999 -vga std -drive
  
file=/usr/share/OVMF/OVMF_CODE.pure-efi.fd,index=0,if=pflash,format=raw,readonly
 -drive file=OVMF_VARS.pure-efi.fd.ol20.04,index=1,if=pflash,format=raw
  -device
  virtio-scsi-pci,id=virtio-scsi-pci0,disable-legacy=on,iommu_platform=true
- -fw_cfg name=opt/ovmf/OCI-ENABLE,string=0x1  -drive
+ -drive
  
file=/systest/atanveer/scripts/Ubuntu-20.04-2022.02.15-0-uefi-x86_64.qcow2,if=none,id=local_disk0,format=qcow2,media=disk
 -device
  ide-hd,drive=local_disk0,id=local_disk1,bootindex=0  -net none -device
  vfio-pci,host=:21:10.1 -qmp tcp:127.0.0.1:3334,server,nowait -serial
  telnet:127.0.0.1:,server,nowait  -D ./OL20.04-uefi.log -device
  virtio-rng-pci,disable-legacy=on,iommu_platform=true -object
  sev-guest,id=sev0,cbitpos=51,reduced-phys-bits=1 -machine
  memory-encryption=sev0
  
  2) Start a client guest OL/Ubuntu:
  
  /usr/bin/qemu-system-x86_64 -machine q35 -name OL18.04-uefi -enable-kvm
  -nodefaults -cpu host,+host-phys-bits -m 8G -smp 8,maxcpus=240 -monitor stdio
  -vnc 0.0.0.0:0,to=999 -vga std -drive
  
file=/usr/share/OVMF/OVMF_CODE.pure-efi.fd,index=0,if=pflash,format=raw,readonly
 -drive file=OVMF_VARS.pure-efi.fd.ol18.04,index=1,if=pflash,format=raw
  -device
  virtio-scsi-pci,id=virtio-scsi-pci0,disable-legacy=on,iommu_platform=true
- -fw_cfg name=opt/ovmf/OCI-ENABLE,string=0x1  -drive
+ -drive
  
file=/systest/atanveer/scripts/Ubuntu-18.04-2022.02.13-0-uefi-x86_64.qcow2,if=none,id=local_disk0,format=qcow2,media=disk
 -device
  ide-hd,drive=local_disk0,id=local_disk1,bootindex=0  -net none -device
  vfio-pci,host=:21:10.2 -qmp tcp:127.0.0.1:,server,nowait -serial
  telnet:127.0.0.1:,server,nowait  -D ./OL18.04-uefi.log -device
  virtio-rng-pci,disable-legacy=on,iommu_platform=true -object
  sev-guest,id=sev0,cbitpos=51,reduced-phys-bits=1 -machine
  memory-encryption=sev0
  
  3) Flush iptables on both the VMs using "iptables -F"
  
  4) Start the iperf3 server on the first VM using "iperf3 -s"
  
  5) Start the iperf3 client on the second VM using "iperf3 -c  -4
  -f M -i 0 -t 70 -O 10 -P 64"
  
  The kernel panic is seen on the first VM i.e. Ubuntu 20.04 with iperf3 also
  showing "Bad Address" error.
- 
  
  Console logs:
  
  root@ubuntu-20-04:~# iperf3 -s
  ---
  Server listening on 5201
  ---
  Accepted connection from 10.196.246.104, port 33732
  [  5] local 10.196.247.88 port 5201 connected to 10.196.246.104 port 33734
  [  8] local 10.196.247.88 port 5201 connected to 10.196.246.104 port 33736
  [ 10] local 10.196.247.88 port 5201 connected to 10.196.246.104 port 33738
  iperf3: error - unable to read from stream socket: Bad address
  ---
  Server listening on 5201
  ---
  [   91.083856] general protection fault:  [#1] SMP NOPTI
  [   91.084591] CPU: 4 PID: 0 Comm: swapper/4 Not tainted 5.11.0-1028-oracle
  #31~20.04.1-Ubuntu
  [   91.085393] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.6.2
  06/01/2022
  [   91.086205] RIP: 0010:memcpy_erms+0x6/0x10
  [   91.086640] Code: cc cc cc cc eb 1e 0f 1f 00 48 89 f8 48 89 d1 48 c1 e9 03
  83 e2 07 f3 48 a5 89 d1 f3 a4 c3 66 0f 1f 44 00 00 48 89 f8 48 89 d1  a4
  c3 0f 1f 80 00 00 00 00 48 89 f8 48 83 fa 20 72 7e 40 38 fe
  [   91.088559] RSP: 0018:a9c1408e4b60 EFLAGS: 00010282
  [   91.089105] RAX: 938cd8e48000 RBX: 1000 RCX:
  1000
  [   91.089843] RDX: 1000 RSI: bb62fcf4fd5bf3d6 RDI:
  938cd8e48000
  [   91.090578] RBP: a9c1408e4c00 R08: ef2745639200 R09:
  
  [   91.091309] R10: ef27456399c8 R11: 4209 R12:
  1000
  [   91.092043] R13: ef2745639200 R14: 1000 R15:
  0d558380
  [   91.092782] FS:  () GS:938df430(

[Kernel-packages] [Bug 1944435] Re: Backlight on P17 Gen 1 not working Nvidia 470

2022-04-13 Thread Chi-Wei Chen

@Aaron, @David,

It looks BIOS for P15/P17 Gen1 N30ET45W(1.28) is released to LVFS
already. R510 NV driver with this BIOS can resolve this issue.

https://fwupd.org/lvfs/devices/com.lenovo.ThinkPadN30ET.firmware

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

Title:
  Backlight on P17 Gen 1 not working Nvidia 470

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated to the Nvidia 460 driver and backlight (screen brightness) was not 
working so updated to the 470.63.01 before opening ticket as it also is not 
wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was working fine 
before the updates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z  2151 F pulseaudio
   /dev/snd/controlC1:  z  2151 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-04 (259 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201012-17:03
  MachineType: LENOVO 20SNZ5GCUS
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-34-generic N/A
   linux-backports-modules-5.11.0-34-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2021
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET40W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SNZ5GCUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET40W(1.23):bd08/03/2021:br1.23:efr1.11:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SNZ5GCUS
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+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 1967067] Re: WCN6856 BT keep in OFF state after coldboot system

2022-04-11 Thread Yao Wei

** Attachment added: "lp1967067-bt-test.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967067/+attachment/5579243/+files/lp1967067-bt-test.tar.xz

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

Title:
  WCN6856 BT keep in OFF state after coldboot system

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  WCN6856 BT keep in OFF state after coldboot system.

  [Fix]

  Mainline commit 599ece4f8f07 ("Bluetooth: btusb: Improve stability for
  QCA devices") added a 100ms delay for the underlying hw to apply
  downloaded firmware.

  [Test Case]

  This can be reproduced and therefore verified by checkbox poweroff
  stress test:

$ checkbox-cli run com.canonical.certification::stress/poweroff

  [Where problems could occur]

  Unlikely to have side effect so far except slowing down boot process for
  a tiny moment.

  [Other Info]

  While this is only in the v5.18 merge window, all the kernels in use are
  affected and nominated here.

  == original bug report ==

  [Reproduce Steps]
  1.Insert WCN6856 card to SUT.
  2.Press power button to power on SUT.
  3.Clean install Ubuntu 20.04.
  4.Check BT function after installation is complete.
  5.Coldboot system and check the BT function.
  6.Repeat step5, Issue occur.
  7.Only found with CB, can't reproduce on WB.

  [Results]
   Expected Result
   BT function work normally.
   Actual Result
   BT has no function. Can't turn ON BT function. Need CB to recover BT 
function.
   "WB" and "swicth tab" cannot restore the BT function.

  [Others]
  Wifi function work normally.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1967067/+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 1967067] Re: WCN6856 BT keep in OFF state after coldboot system

2022-04-11 Thread Yao Wei

With linux-oem-5.14/5.14.0-1033.36, this issue is not reproducible
within 20 cold reboots.

A script is used to run rtcwake to cold boot 20 times and attach
`bluetoothctl scan on` result to a log file.  If the bluetooth device
cannot be probed, the scan should output "No default controller
available".  There was no such error when using 5.14.0-1033.36 kernel.

** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

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

Title:
  WCN6856 BT keep in OFF state after coldboot system

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  WCN6856 BT keep in OFF state after coldboot system.

  [Fix]

  Mainline commit 599ece4f8f07 ("Bluetooth: btusb: Improve stability for
  QCA devices") added a 100ms delay for the underlying hw to apply
  downloaded firmware.

  [Test Case]

  This can be reproduced and therefore verified by checkbox poweroff
  stress test:

$ checkbox-cli run com.canonical.certification::stress/poweroff

  [Where problems could occur]

  Unlikely to have side effect so far except slowing down boot process for
  a tiny moment.

  [Other Info]

  While this is only in the v5.18 merge window, all the kernels in use are
  affected and nominated here.

  == original bug report ==

  [Reproduce Steps]
  1.Insert WCN6856 card to SUT.
  2.Press power button to power on SUT.
  3.Clean install Ubuntu 20.04.
  4.Check BT function after installation is complete.
  5.Coldboot system and check the BT function.
  6.Repeat step5, Issue occur.
  7.Only found with CB, can't reproduce on WB.

  [Results]
   Expected Result
   BT function work normally.
   Actual Result
   BT has no function. Can't turn ON BT function. Need CB to recover BT 
function.
   "WB" and "swicth tab" cannot restore the BT function.

  [Others]
  Wifi function work normally.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1967067/+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 1959728] Re: trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

2022-04-04 Thread Wei

I found this issue fixed after a Senel firmware update (v0.22.520, 28 Mar 
2022): 
https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-series-laptops/thinkpad-x1-titanium-type-20qa-20qb/downloads/driver-list/component?name=Mouse,%20Touchpad,%20Keyboard%20and%20Pen
The update is applied in windows.

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

Title:
  trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my X1 Yoga Titanium (which has a fancy new "Sensel" trackpad with
  haptic response to clicks), the trackpad stops working after a
  suspend/resume cycle, although the red trackpoint continues to work
  fine for controlling the pointer.  I believe this system is using S0i3
  for suspend, in case that's relevant.

  If I boot from power off, then the trackpad works fine in both the
  pre-boot BIOS and in Ubuntu 22.04 (prerelease), including haptic
  response to clicks.  After a suspend/resume cycle, the trackpad stops
  responding, although a lot of swiping/pressing will occasionally
  produce a button press event.  This state persists even if I reboot
  out of Linux (without a power cycle) - for example the trackpad no
  longer works for the pre-boot BIOS configuration screen, until a full
  power cycle (which fixes the trackpad).

  Possibly relevant, the trackpad seems to be this device to the kernel:

  [2.016917] input: SNSL0001:00 2C2F:0006 Mouse as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input6
  [2.016964] input: SNSL0001:00 2C2F:0006 Touchpad as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input7
  [2.017027] hid-generic 0018:2C2F:0006.0001: input,hidraw0: I2C HID v1.00 
Mouse [SNSL0001:00 2C2F:0006] on i2c-SNSL0001:00

  and the last kernel messages before suspend are:

  [  305.216189] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [  305.217435] printk: Suspending console(s) (use no_console_suspend to debug)
  [  305.274332] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: lost 
arbitration
  [  306.030947] i2c_hid_acpi i2c-SNSL0001:00: failed to set a report to device.
  [  306.616463] ACPI: EC: interrupt blocked
  [  331.551118] ACPI: EC: interrupt unblocked

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bina   1543 F pipewire
bina   1544 F pipewire-media-
bina   1545 F pulseaudio
   /dev/snd/seq:bina   1543 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  1 14:54:14 2022
  InstallationDate: Installed on 2022-02-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  MachineType: LENOVO 20QA000EUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-18-generic N/A
   linux-backports-modules-5.15.0-18-generic  N/A
   linux-firmware 20220124.git0c6a7b3b-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2021
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2MET53W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QA000EUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2MET53W(1.18):bd09/30/2021:br1.18:efr1.11:svnLENOVO:pn20QA000EUS:pvrThinkPadX1TitaniumGen1:rvnLENOVO:rn20QA000EUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20QA_BU_Think_FM_ThinkPadX1TitaniumGen1:
  dmi.product.family: ThinkPad X1 Titanium Gen 1
  dmi.product.name: 20QA000EUS
  dmi.product.sku: LENOVO_MT_20QA_BU_Think_FM_ThinkPad X1 Titanium Gen 1
  dmi.product.version: ThinkPad X1 Titanium Gen 1
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1967067] Re: WCN6856 BT keep in OFF state after coldboot system

2022-03-30 Thread Yao Wei

Can confirm that 5.14.0-9031.34+exp.62 fixed this bug. cold-boot 50
times by script and BT can scan normally in all reboots.

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

Title:
  WCN6856 BT keep in OFF state after coldboot system

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  New
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Triaged
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Incomplete
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  New

Bug description:
  [Reproduce Steps]
  1.Insert WCN6856 card to SUT.
  2.Press power button to power on SUT.
  3.Clean install Ubuntu 20.04.
  4.Check BT function after installation is complete.
  5.Coldboot system and check the BT function.
  6.Repeat step5, Issue occur.
  7.Only found with CB, can't reproduce on WB.

  [Results]
   Expected Result
   BT function work normally.
   Actual Result
   BT has no function. Can't turn ON BT function. Need CB to recover BT 
function.
   "WB" and "swicth tab" cannot restore the BT function.

  [Others]
  Wifi function work normally.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1967067/+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 1959728] Re: trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

2022-03-23 Thread Wei

Same machine and same issues here. works fine in Windows.

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

Title:
  trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my X1 Yoga Titanium (which has a fancy new "Sensel" trackpad with
  haptic response to clicks), the trackpad stops working after a
  suspend/resume cycle, although the red trackpoint continues to work
  fine for controlling the pointer.  I believe this system is using S0i3
  for suspend, in case that's relevant.

  If I boot from power off, then the trackpad works fine in both the
  pre-boot BIOS and in Ubuntu 22.04 (prerelease), including haptic
  response to clicks.  After a suspend/resume cycle, the trackpad stops
  responding, although a lot of swiping/pressing will occasionally
  produce a button press event.  This state persists even if I reboot
  out of Linux (without a power cycle) - for example the trackpad no
  longer works for the pre-boot BIOS configuration screen, until a full
  power cycle (which fixes the trackpad).

  Possibly relevant, the trackpad seems to be this device to the kernel:

  [2.016917] input: SNSL0001:00 2C2F:0006 Mouse as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input6
  [2.016964] input: SNSL0001:00 2C2F:0006 Touchpad as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input7
  [2.017027] hid-generic 0018:2C2F:0006.0001: input,hidraw0: I2C HID v1.00 
Mouse [SNSL0001:00 2C2F:0006] on i2c-SNSL0001:00

  and the last kernel messages before suspend are:

  [  305.216189] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [  305.217435] printk: Suspending console(s) (use no_console_suspend to debug)
  [  305.274332] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: lost 
arbitration
  [  306.030947] i2c_hid_acpi i2c-SNSL0001:00: failed to set a report to device.
  [  306.616463] ACPI: EC: interrupt blocked
  [  331.551118] ACPI: EC: interrupt unblocked

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bina   1543 F pipewire
bina   1544 F pipewire-media-
bina   1545 F pulseaudio
   /dev/snd/seq:bina   1543 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  1 14:54:14 2022
  InstallationDate: Installed on 2022-02-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  MachineType: LENOVO 20QA000EUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-18-generic N/A
   linux-backports-modules-5.15.0-18-generic  N/A
   linux-firmware 20220124.git0c6a7b3b-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2021
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2MET53W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QA000EUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2MET53W(1.18):bd09/30/2021:br1.18:efr1.11:svnLENOVO:pn20QA000EUS:pvrThinkPadX1TitaniumGen1:rvnLENOVO:rn20QA000EUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20QA_BU_Think_FM_ThinkPadX1TitaniumGen1:
  dmi.product.family: ThinkPad X1 Titanium Gen 1
  dmi.product.name: 20QA000EUS
  dmi.product.sku: LENOVO_MT_20QA_BU_Think_FM_ThinkPad X1 Titanium Gen 1
  dmi.product.version: ThinkPad X1 Titanium Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959728/+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 1954938] Re: Include the QCA WCN 6856 v2.1 support

2022-03-03 Thread Yao Wei

With Linux kernel 5.14.0-1024-oem and linux-firmware 1.187.27 (in
-proposed), it is confirmed that both WiFi and Bluetooth on WCN6856 A00
can be probed and used.

Excerpt from dmesg:

[6.188795] kernel: ath11k_pci :02:00.0: BAR 0: assigned [mem 
0x7520-0x753f 64bit]
[6.188815] kernel: ath11k_pci :02:00.0: enabling device ( -> 0002)
[6.189145] kernel: ath11k_pci :02:00.0: wcn6855 hw2.0
[7.244333] kernel: ath11k_pci :02:00.0: chip_id 0x12 chip_family 0xb 
board_id 0xff soc_id 0x400c1211
[7.244347] kernel: ath11k_pci :02:00.0: fw_version 0x11080bbb 
fw_build_timestamp 2021-12-16 03:42 fw_build_id 
QC_IMAGE_VERSION_STRING=WLAN.HSP.1.1-03003-QCAHSPSWPL_V1_V2_SILICONZ_LITE-2
[7.552211] kernel: ath11k_pci :02:00.0 wlp2s0: renamed from wlan0


** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

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

Title:
  Include the QCA WCN 6856 v2.1 support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Won't Fix
Status in linux-firmware source package in Impish:
  Won't Fix
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  WCN685x hw2.1 takes additional/updated firmware for both WiFi and
  Bluetooth function.

  ath11k_pci :71:00.0: BAR 0: assigned [mem 0xa600-0xa61f 64bit]
  ath11k_pci :71:00.0: enabling device ( -> 0002)
  ath11k_pci :71:00.0: Unsupported WCN6855 SOC hardware version: 18 17
  ath11k_pci: probe of :71:00.0 failed with error -95

  [Fix]

  WCN685x hw2.1 currently shares most WiFi firmware with hw2.0 except
  for the directory path and a board-2.bin.

  For Bluetooth, updated revision of qca/nvm_usb_00130201_gf* from
  mainline are neccessary for Focal. Jammy has all of them already.

  For kernel, many of the prerequisite works have been committed for
  hw2.0 in bug 1945154, 1952215 and 1958850. Currently, while WiFi 6G
  will be turned off for the lack of userspace support, the only fix
  necessary is to correct read mask of version info register.

  ath11k 6G band lives in mainline v5.16 and was backported to oem-5.14
  in bug 1939528, so only oem-5.14 has to be reverted.

  [Test Case]

  WiFi and Bluetooth devices should be up and running, pass basic
  operations.

  $ lspci -nnk|grep -A3 Network
  :71:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01)
  Subsystem: Foxconn International, Inc. Device [105b:e0ce]
  Kernel driver in use: ath11k_pci
  Kernel modules: ath11k_pci

  $ lsusb
  Bus 003 Device 004: ID 0489:e0e3 Foxconn / Hon Hai

  [Where problems could occur]

  At the time being, WCN685x WiFi 6G support will be turnef off
  deliberately due to the lack of full support in the userspace
  management tools.

  [Other Info]

  While this is a new hardware model from OEM program, it's only
  nominated for Focal oem-5.14 kernel and the coming LTS Jammy.

  == original bug report ==

  ath11k_pci :71:00.0: BAR 0: assigned [mem 0xa600-0xa61f 64bit]
  ath11k_pci :71:00.0: enabling device ( -> 0002)
  ath11k_pci :71:00.0: Unsupported WCN6855 SOC hardware version: 18 17
  ath11k_pci: probe of :71:00.0 failed with error -95

  $ lspci -nnk|grep -A3 Network
  :71:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01)
  Subsystem: Foxconn International, Inc. Device [105b:e0ce]
  Kernel driver in use: ath11k_pci
  Kernel modules: ath11k_pci

  $ lsusb
  Bus 003 Device 004: ID 0489:e0e3 Foxconn / Hon Hai

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954938/+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 1944435] Re: Backlight on P17 Gen 1 not working Nvidia 470

2022-02-10 Thread Chi-Wei Chen

Aaron,
I'm not sure if R510 NV driver can fix this or not. Sorry, we cannot find this 
system panel combination on hand, could you help to check this on your end? 
Thanks
https://www.nvidia.com/Download/driverResults.aspx/186156/en-us

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

Title:
  Backlight on P17 Gen 1 not working Nvidia 470

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated to the Nvidia 460 driver and backlight (screen brightness) was not 
working so updated to the 470.63.01 before opening ticket as it also is not 
wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was working fine 
before the updates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z  2151 F pulseaudio
   /dev/snd/controlC1:  z  2151 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-04 (259 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201012-17:03
  MachineType: LENOVO 20SNZ5GCUS
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-34-generic N/A
   linux-backports-modules-5.11.0-34-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2021
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET40W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SNZ5GCUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET40W(1.23):bd08/03/2021:br1.23:efr1.11:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SNZ5GCUS
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+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 1944435] Re: Backlight on P17 Gen 1 not working Nvidia 470

2022-02-10 Thread Chi-Wei Chen

Aaron,
I'm not sure if R510 NV driver can fix this or not. Sorry, we cannot find this 
system panel combination on hand, could you help to check this on your end? 
Thanks
https://www.nvidia.com/Download/driverResults.aspx/186156/en-us

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

Title:
  Backlight on P17 Gen 1 not working Nvidia 470

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated to the Nvidia 460 driver and backlight (screen brightness) was not 
working so updated to the 470.63.01 before opening ticket as it also is not 
wortking on the P17 Gen 1 with BOE panel NE173QUM-N42.  It was working fine 
before the updates
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z  2151 F pulseaudio
   /dev/snd/controlC1:  z  2151 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-04 (259 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20201012-17:03
  MachineType: LENOVO 20SNZ5GCUS
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-34-generic N/A
   linux-backports-modules-5.11.0-34-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/03/2021
  dmi.bios.release: 1.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET40W (1.23 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SNZ5GCUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET40W(1.23):bd08/03/2021:br1.23:efr1.11:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SNZ5GCUS
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+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 1952823] Re: Screen blinks when entering suspend

2021-11-30 Thread Yao Wei

** Attachment added: "lp1952823.webm"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1952823/+attachment/5544516/+files/lp1952823.webm

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

Title:
  Screen blinks when entering suspend

Status in OEM Priority Project:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  [Summary]
  The screen turns on for a moment when laptop is entering suspend.

  This issue happens on Dell Latitude 5421.

  [Steps to reproduce]
  1. Enter suspend via power menu
  2. Observe the display

  (Note that `rtcwake` may not able to reproduce this issue. `systemctl
  suspend` may reproduce this.)

  [Expected result]
  The screen should not turn back on if the system is going to suspend.

  [Actual result]
  When "Suspend" is clicked, screen turns off, then turns back on for a moment, 
then turns off before laptop entering suspend.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1952823/+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 1952823] Re: Screen blinks when entering suspend

2021-11-30 Thread Yao Wei

** Description changed:

  [Summary]
- The system screen turns on for a moment after entering suspend.
+ The screen turns on for a moment when laptop is entering suspend.
  
  This issue happens on Dell Latitude 5421.
  
  [Steps to reproduce]
  1. Enter suspend via power menu
  2. Observe the display
  
  (Note that `rtcwake` may not able to reproduce this issue. `systemctl
  suspend` may reproduce this.)
  
  [Expected result]
  The screen should not turn back on if the system is going to suspend.
  
  [Actual result]
  When "Suspend" is clicked, screen turns off, then turns back on for a moment, 
then turns off before laptop entering suspend.

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

Title:
  Screen blinks when entering suspend

Status in OEM Priority Project:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  [Summary]
  The screen turns on for a moment when laptop is entering suspend.

  This issue happens on Dell Latitude 5421.

  [Steps to reproduce]
  1. Enter suspend via power menu
  2. Observe the display

  (Note that `rtcwake` may not able to reproduce this issue. `systemctl
  suspend` may reproduce this.)

  [Expected result]
  The screen should not turn back on if the system is going to suspend.

  [Actual result]
  When "Suspend" is clicked, screen turns off, then turns back on for a moment, 
then turns off before laptop entering suspend.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1952823/+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 1952823] Re: Screen blinks when entering suspend

2021-11-30 Thread Yao Wei

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

** Tags added: originate-from-1945730

** Tags added: originate-from-1949668

** Tags added: originate-from-1947975

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

Title:
  Screen blinks when entering suspend

Status in OEM Priority Project:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  [Summary]
  The system screen turns on for a moment after entering suspend.

  This issue happens on Dell Latitude 5421.

  [Steps to reproduce]
  1. Enter suspend via power menu
  2. Observe the display

  (Note that `rtcwake` may not able to reproduce this issue. `systemctl
  suspend` may reproduce this.)

  [Expected result]
  The screen should not turn back on if the system is going to suspend.

  [Actual result]
  When "Suspend" is clicked, screen turns off, then turns back on for a moment, 
then turns off before laptop entering suspend.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1952823/+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 1952823] Re: Screen blinks when entering suspend

2021-11-30 Thread Yao Wei

** Description changed:

[Summary]
The system screen turns on for a moment after entering suspend.

This issue happens on Dell Latitude 5421.

[Steps to reproduce]
1. Enter suspend via power menu
2. Observe the display

(Note that `rtcwake` may not able to reproduce this issue. `systemctl
suspend` may reproduce this.)

[Expected result]
- The system should not turn back on if the system is going to suspend.
+ The screen should not turn back on if the system is going to suspend.

[Actual result]
When "Suspend" is clicked, screen turns off, then turns back on for a moment,
then turns off before laptop entering suspend.

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

Title:
Screen blinks when entering suspend

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

Bug description:
[Summary]
The system screen turns on for a moment after entering suspend.

This issue happens on Dell Latitude 5421.

[Steps to reproduce]
1. Enter suspend via power menu
2. Observe the display

(Note that `rtcwake` may not able to reproduce this issue. `systemctl
suspend` may reproduce this.)

[Expected result]
The screen should not turn back on if the system is going to suspend.

[Actual result]
When "Suspend" is clicked, screen turns off, then turns back on for a moment,
then turns off before laptop entering suspend.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1952823/+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 1952823] Re: Screen blinks when entering suspend

2021-11-30 Thread Yao Wei

** Attachment added: "nvidia-bug-report.log.gz"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1952823/+attachment/5544481/+files/nvidia-bug-report.log.gz

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

Title:
  Screen blinks when entering suspend

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

Bug description:
  [Summary]
  The system screen turns on for a moment after entering suspend.

  This issue happens on Dell Latitude 5421.

  [Steps to reproduce]
  1. Enter suspend via power menu
  2. Observe the display

  (Note that `rtcwake` may not able to reproduce this issue. `systemctl
  suspend` may reproduce this.)

  [Expected result]
  The screen should not turn back on if the system is going to suspend.

  [Actual result]
  When "Suspend" is clicked, screen turns off, then turns back on for a moment, 
then turns off before laptop entering suspend.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1952823/+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 1952823] [NEW] Screen blinks when entering suspend

2021-11-30 Thread Yao Wei

Public bug reported:

[Summary]
The system screen turns on for a moment after entering suspend.

This issue happens on Dell Latitude 5421.

[Steps to reproduce]
1. Enter suspend via power menu
2. Observe the display

(Note that `rtcwake` may not able to reproduce this issue. `systemctl
suspend` may reproduce this.)

[Expected result]
The screen should not turn back on if the system is going to suspend.

[Actual result]
When "Suspend" is clicked, screen turns off, then turns back on for a moment,
then turns off before laptop entering suspend.

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

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

Title:
Screen blinks when entering suspend

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

Bug description:
[Summary]
The system screen turns on for a moment after entering suspend.

This issue happens on Dell Latitude 5421.

[Steps to reproduce]
1. Enter suspend via power menu
2. Observe the display

(Note that `rtcwake` may not able to reproduce this issue. `systemctl
suspend` may reproduce this.)

[Expected result]
The screen should not turn back on if the system is going to suspend.

[Actual result]
When "Suspend" is clicked, screen turns off, then turns back on for a moment,
then turns off before laptop entering suspend.

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

[Kernel-packages] [Bug 1951861] Re: Fix non-working e1000e device after resume

2021-11-23 Thread Yao Wei

** Tags added: originate-from-1947661

** Tags added: originate-from-1947678

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

Title:
  Fix non-working e1000e device after resume

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.13 source package in Focal:
  Confirmed
Status in linux-oem-5.14 source package in Focal:
  Confirmed
Status in linux source package in Impish:
  Confirmed
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [Impact]
  e1000e devices stop working after s2idle resume.

  [Fix] 
  Revert the offending patch series, which is to bring some minor power
  saving.
   
  [Test]
  Vendor did extensive tests and didn't find any regression, and the power
  consumption remains the same.

  [Where problems could occur]
  Maybe on some system the series can save some energy, so reverting will
  cause some power consumption increase.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1951861/+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 1950042] Re: Let NVMe with HMB use native power control again

2021-11-10 Thread Yao Wei

Verified pass on focal that the system can enter PC10 and SLP_S0.

On 5.14.0-1007-oem:

turbostat --quiet -S --show Pkg%pc2,Pkg%pc3,Pk%pc10,CPU%LPI,SYS%LPI
rtcwake -m freeze -s 15 | tee s0ix-diag.txt

rtcwake: assuming RTC uses UTC ...
rtcwake: wakeup from "freeze" using /dev/rtc0 at Thu Nov 11 01:39:29 2021
16.659672 sec
Pkg%pc2 Pkg%pc3 Pk%pc10 CPU%LPI SYS%LPI
1.5986.66   0.000.000.00

On 5.14.0-1008-oem (proposed):

turbostat --quiet -S --show Pkg%pc2,Pkg%pc3,Pk%pc10,CPU%LPI,SYS%LPI
rtcwake -m freeze -s 15 | tee s0ix-diag.txt

rtcwake: assuming RTC uses UTC ...
rtcwake: wakeup from "freeze" using /dev/rtc0 at Thu Nov 11 01:53:24 2021
16.661935 sec
Pkg%pc2 Pkg%pc3 Pk%pc10 CPU%LPI SYS%LPI
0.821.9686.22   87.40   85.27


** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

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

Title:
  Let NVMe with HMB use native power control again

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.10 source package in Focal:
  Confirmed
Status in linux-oem-5.13 source package in Focal:
  Confirmed
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Confirmed
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux-oem-5.14 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Confirmed
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  Impact]
  NVMe with HMB may still do DMA during suspend, so there was a commit
  that put the NVMe to PCI D3 during suspend to prevent DMA activities.
  However, this makes them consumes much more power because modern NVMe
  requires to stay at PCI D0 to make its natve power control work. 

  [Fix]
  Instead of put the NVMe to PCI D3 and reset it afterward, simply disable
  HMB and re-enable HMB, for suspend and resume respectively.

  [Test]
  On affected system, Intel SoC can only reach PC3 during suspend.
  With the SRU applied, the Intel SoC can reach PC10 and SLP_S0 and use
  significant less power.

  [Where problems could occur]
  The original approach, i.e. disable NVMe and put it to PCI D3 to prevent
  DMA activies, was just a precaution. There wasn't any case that
  indicates it happens in practice.

  This is a different approach to the same problem, which is a theoretical
  problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1950042/+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 1930754] Re: e1000e extremly slow

2021-09-10 Thread Yao Wei

** Tags added: originate-from-1942834

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

Title:
  e1000e extremly slow

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux-oem-5.10 package in Ubuntu:
  Confirmed

Bug description:
  We have dell latitude 5420 & 5520 laptops with onboard intel ethernet 
controller.
  Problem is that the ethernet port is extremely slow. about 100kbyte/s 
download throughput while on a gigabit connection. Upload seems to work just 
fine.

  Also when I pxe boot the system it's also painfully slow.

  But here comes the funny part. When I attach a usb memory stick the
  throughput of the networkcontroller is as expected.

  I've used latest ubuntu 20.04.2 kernel 5.8.0-55
  I've used latest ubuntu 20.04.2 kernel 5.10.0-1029-oem

  Turns out this problem is not showing up when I manually install the
  5.8.18 kernel.

  Also when I create my own iso with the help of Cubic and install the
  5.8.18 kernel in it the pxe boot is working as expected with high
  throughput

  system: Dell latitude 5420 + 5520
  nic: Ethernet Connection (13) I219-LM
  ubuntu 20.04.2
  module: e1000e

  Please assist. Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1930754/+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 1930754] Re: e1000e extremly slow

2021-09-10 Thread Yao Wei

** Tags added: fossa-edge-staging

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

Title:
  e1000e extremly slow

Status in OEM Priority Project:
  Confirmed
Status in linux-oem-5.10 package in Ubuntu:
  Confirmed

Bug description:
  We have dell latitude 5420 & 5520 laptops with onboard intel ethernet 
controller.
  Problem is that the ethernet port is extremely slow. about 100kbyte/s 
download throughput while on a gigabit connection. Upload seems to work just 
fine.

  Also when I pxe boot the system it's also painfully slow.

  But here comes the funny part. When I attach a usb memory stick the
  throughput of the networkcontroller is as expected.

  I've used latest ubuntu 20.04.2 kernel 5.8.0-55
  I've used latest ubuntu 20.04.2 kernel 5.10.0-1029-oem

  Turns out this problem is not showing up when I manually install the
  5.8.18 kernel.

  Also when I create my own iso with the help of Cubic and install the
  5.8.18 kernel in it the pxe boot is working as expected with high
  throughput

  system: Dell latitude 5420 + 5520
  nic: Ethernet Connection (13) I219-LM
  ubuntu 20.04.2
  module: e1000e

  Please assist. Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1930754/+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 1940262] Re: The modalias in 470 is not compatible to 460

2021-08-30 Thread Yao Wei

Splitting RTX A5000 from Dell to LP: #1942080

** Tags removed: originate-from-1941823 somerville

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

Title:
  The modalias in 470 is not compatible to 460

Status in OEM Priority Project:
  Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Committed

Bug description:
  There are many modalias be removed from 470 those supporting in 460.
  If 470 is a LTS version and 460 will be transited to 470 then the driver 
installing will have different behavior between both version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1940262/+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 1942080] [NEW] ubuntu-driver should suggest nvidia-driver-470 for RTX A5000

2021-08-30 Thread Yao Wei

Public bug reported:

Split from bug LP: #1940262

The following modalias of RTX A5000 (notably, for Dell OEM) is missing:

pci:v10DEd2231sv1028sd147Ebc03sc00i00

This results in ubuntu-drivers not suggesting nvidia-driver-470.

** Affects: oem-priority
 Importance: Undecided
 Status: New

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


** Tags: oem-priority originate-from-1941823 somerville

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

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

Title:
  ubuntu-driver should suggest nvidia-driver-470 for RTX A5000

Status in OEM Priority Project:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  Split from bug LP: #1940262

  The following modalias of RTX A5000 (notably, for Dell OEM) is
  missing:

  pci:v10DEd2231sv1028sd147Ebc03sc00i00

  This results in ubuntu-drivers not suggesting nvidia-driver-470.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1942080/+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 1940262] Re: The modalias in 470 is not compatible to 460

2021-08-26 Thread Yao Wei

Reuploading the script

** Attachment removed: "nvidia_supported"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1940262/+attachment/5521045/+files/nvidia_supported

** Attachment added: "nvidia_supported"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1940262/+attachment/5521048/+files/nvidia_supported

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

Title:
  The modalias in 470 is not compatible to 460

Status in OEM Priority Project:
  Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Committed

Bug description:
  There are many modalias be removed from 470 those supporting in 460.
  If 470 is a LTS version and 460 will be transited to 470 then the driver 
installing will have different behavior between both version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1940262/+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 1940262] Re: The modalias in 470 is not compatible to 460

2021-08-26 Thread Yao Wei

** Tags added: originate-from-1941823 somerville

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

Title:
  The modalias in 470 is not compatible to 460

Status in OEM Priority Project:
  Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Committed

Bug description:
  There are many modalias be removed from 470 those supporting in 460.
  If 470 is a LTS version and 460 will be transited to 470 then the driver 
installing will have different behavior between both version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1940262/+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 1940262] Re: The modalias in 470 is not compatible to 460

2021-08-26 Thread Yao Wei

I would like to propose fix to nvidia_supported script that parses
README.txt.

On the line with RTX A5000, there are 2 spaces after the PCI IDs.
Current nvidia_supported script assumes there are at least 3 spaces
before VDPAU features column, which is not the case in this line.

My proposal of parsing this list is to use offset to get the column of
Device PCI ID, and get 1-3 hex strings after the offset.

** Attachment added: "nvidia_supported"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1940262/+attachment/5521045/+files/nvidia_supported

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

Title:
  The modalias in 470 is not compatible to 460

Status in OEM Priority Project:
  Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Committed

Bug description:
  There are many modalias be removed from 470 those supporting in 460.
  If 470 is a LTS version and 460 will be transited to 470 then the driver 
installing will have different behavior between both version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1940262/+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 1930903] Re: Frequent kernel oops related to nvidia / nv_drm_master_set

2021-08-13 Thread Yao Wei

** No longer affects: oem-priority

** Tags removed: oem-priority originate-from-1939083

** Tags removed: somerville

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

Title:
  Frequent kernel oops related to nvidia / nv_drm_master_set

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

Bug description:
  After upgrading yesterday from ubuntu 20 to 21.04 my machine now
  exhibits frequent involuntary restarts, related to a kernel oops of
  the form

  Jun  3 10:48:32 zotac kernel: [   20.464926] RIP: 
0010:nv_drm_master_set+0x27/0x30 [nvidia_drm]
  [...]
  Jun  3 10:48:32 zotac kernel: [   20.464958] Call Trace:
  Jun  3 10:48:32 zotac kernel: [   20.464964]  drm_new_set_master+0x7e/0x100 
[drm]
  Jun  3 10:48:32 zotac kernel: [   20.464994]  drm_master_open+0x6e/0xa0 [drm]
  Jun  3 10:48:32 zotac kernel: [   20.465017]  drm_open+0xf8/0x250 [drm]
  Jun  3 10:48:32 zotac kernel: [   20.465044]  drm_stub_open+0xba/0x140 [drm]
  Jun  3 10:48:32 zotac kernel: [   20.465070]  chrdev_open+0xf7/0x220
  Jun  3 10:48:32 zotac kernel: [   20.465075]  ? cdev_device_add+0x90/0x90
  Jun  3 10:48:32 zotac kernel: [   20.465078]  do_dentry_open+0x156/0x370
  Jun  3 10:48:32 zotac kernel: [   20.465081]  vfs_open+0x2d/0x30
  Jun  3 10:48:32 zotac kernel: [   20.465084]  do_open+0x1c3/0x340
  Jun  3 10:48:32 zotac kernel: [   20.465087]  path_openat+0x10a/0x1d0
  Jun  3 10:48:32 zotac kernel: [   20.465090]  do_filp_open+0x8c/0x130
  Jun  3 10:48:32 zotac kernel: [   20.465093]  ? __check_object_size+0x1c/0x20
  Jun  3 10:48:32 zotac kernel: [   20.465096]  do_sys_openat2+0x9b/0x150
  Jun  3 10:48:32 zotac kernel: [   20.465099]  __x64_sys_openat+0x56/0x90
  Jun  3 10:48:32 zotac kernel: [   20.465102]  do_syscall_64+0x38/0x90
  Jun  3 10:48:32 zotac kernel: [   20.465105]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Jun  3 10:48:32 zotac kernel: [   20.465108] RIP: 0033:0x7fe6ea270954

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.80  Fri May  7 06:55:54 
UTC 2021
   GCC version:  gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1)
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Jun  4 17:00:45 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 460.80, 5.11.0-18-generic, x86_64: installed
   nvidia, 460.80, 5.8.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] 
[19da:2438]
  InstallationDate: Installed on 2020-05-09 (391 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: NA ZBOX-ER51070
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic 
root=UUID=4e73512b-1846-4fe4-87d1-079bbaae2a1a ro quiet splash 
crashkernel=512M-:192M vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Default string
  dmi.board.name: ZBOX-ER51070
  dmi.board.vendor: NA
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd04/25/2019:br5.12:svnNA:pnZBOX-ER51070:pvrDefaultstring:rvnNA:rnZBOX-ER51070:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: ZBOX-ER51070
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: NA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xser

[Kernel-packages] [Bug 1930903] Re: Frequent kernel oops related to nvidia / nv_drm_master_set

2021-08-05 Thread Yao Wei

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

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

Title:
  Frequent kernel oops related to nvidia / nv_drm_master_set

Status in OEM Priority Project:
  New
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  New

Bug description:
  After upgrading yesterday from ubuntu 20 to 21.04 my machine now
  exhibits frequent involuntary restarts, related to a kernel oops of
  the form

  Jun  3 10:48:32 zotac kernel: [   20.464926] RIP: 
0010:nv_drm_master_set+0x27/0x30 [nvidia_drm]
  [...]
  Jun  3 10:48:32 zotac kernel: [   20.464958] Call Trace:
  Jun  3 10:48:32 zotac kernel: [   20.464964]  drm_new_set_master+0x7e/0x100 
[drm]
  Jun  3 10:48:32 zotac kernel: [   20.464994]  drm_master_open+0x6e/0xa0 [drm]
  Jun  3 10:48:32 zotac kernel: [   20.465017]  drm_open+0xf8/0x250 [drm]
  Jun  3 10:48:32 zotac kernel: [   20.465044]  drm_stub_open+0xba/0x140 [drm]
  Jun  3 10:48:32 zotac kernel: [   20.465070]  chrdev_open+0xf7/0x220
  Jun  3 10:48:32 zotac kernel: [   20.465075]  ? cdev_device_add+0x90/0x90
  Jun  3 10:48:32 zotac kernel: [   20.465078]  do_dentry_open+0x156/0x370
  Jun  3 10:48:32 zotac kernel: [   20.465081]  vfs_open+0x2d/0x30
  Jun  3 10:48:32 zotac kernel: [   20.465084]  do_open+0x1c3/0x340
  Jun  3 10:48:32 zotac kernel: [   20.465087]  path_openat+0x10a/0x1d0
  Jun  3 10:48:32 zotac kernel: [   20.465090]  do_filp_open+0x8c/0x130
  Jun  3 10:48:32 zotac kernel: [   20.465093]  ? __check_object_size+0x1c/0x20
  Jun  3 10:48:32 zotac kernel: [   20.465096]  do_sys_openat2+0x9b/0x150
  Jun  3 10:48:32 zotac kernel: [   20.465099]  __x64_sys_openat+0x56/0x90
  Jun  3 10:48:32 zotac kernel: [   20.465102]  do_syscall_64+0x38/0x90
  Jun  3 10:48:32 zotac kernel: [   20.465105]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Jun  3 10:48:32 zotac kernel: [   20.465108] RIP: 0033:0x7fe6ea270954

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.80  Fri May  7 06:55:54 
UTC 2021
   GCC version:  gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1)
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Jun  4 17:00:45 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 460.80, 5.11.0-18-generic, x86_64: installed
   nvidia, 460.80, 5.8.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] 
[19da:2438]
  InstallationDate: Installed on 2020-05-09 (391 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: NA ZBOX-ER51070
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic 
root=UUID=4e73512b-1846-4fe4-87d1-079bbaae2a1a ro quiet splash 
crashkernel=512M-:192M vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Default string
  dmi.board.name: ZBOX-ER51070
  dmi.board.vendor: NA
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd04/25/2019:br5.12:svnNA:pnZBOX-ER51070:pvrDefaultstring:rvnNA:rnZBOX-ER51070:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: ZBOX-ER51070
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: NA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati

[Kernel-packages] [Bug 1881097] Re: [Thinkpad X1C7][Thinkpad X1C8]F1 and F4 Hotkey LED Light Stays ON/OFF when USB Headset is attached.

2021-05-07 Thread Chi-Wei Chen

@Jasonyen,
We just noticed that the F1 mute LED issue is also encountered for External 
Monitor Speaker on X1C9.
Is it the same limitation as this ticket or it would be better to raise another 
ticket to discuss?

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

Title:
  [Thinkpad X1C7][Thinkpad X1C8]F1 and F4 Hotkey LED Light Stays ON/OFF
  when USB Headset is attached.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Problem Description:

  Using Ubuntu 20.04 on a Thinkpad X1C7 machine.
  Speaker(F1) and Microphone(F4) Hotkey LED Light Stays ON/OFF when USB Headset 
is attached.

  -

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  Ubuntu Software: 3.36.1

  -

  Expected Result:
  When LED light of Speaker(F1)/Microphone (F4) hotkeys is ON/OFF and then we 
connect USB Headset and press Speaker(F1)/Microphone (F4) hotkeys again -> LED 
light state will change accordingly.

  Actual Result:
  1. When LED light of Speaker(F1)/Microphone (F4) hotkeys is OFF and then we 
connect USB Headset and press Speaker(F1)/Microphone (F4) hotkeys again -> LED 
light will STAY OFF and remains in OFF State always on the duration that the 
USB headset is attached to the machine.
  2. If LED light of Speaker(F1)/Microphone (F4) hotkeys is ON and then we 
connect USB Headset and press Speaker(F1)/Microphone (F4) hotkeys again -> LED 
will STAY ON and remains in ON State on the duration that the USB headset is 
attached to the machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-33-generic 5.4.0-33.37
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1410 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 28 18:48:04 2020
  InstallationDate: Installed on 2020-05-28 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20U9SITR38
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=ab59da99-085b-4f8d-af14-4fc4240a8f83 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET11C (1.01C )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9SITR38
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET11C(1.01C):bd02/12/2020:svnLENOVO:pn20U9SITR38:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9SITR38:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9SITR38
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881097/+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 1829236] [NEW] RaspberryPi PoE hat fan speed cannot be controlled

2019-05-15 Thread Zhenfang Wei

Public bug reported:

In Disco branch of linux-raspi2 package, the support of Raspberry Pi's PoE Hat 
is added. Unfortunately the fan speed cannot be controlled the same way as in 
Raspbian.
In Raspbian, we could set the fan to spin when temperature exceeds certain 
value by adding dtparam in conifg.txt file such as below (this will let the fan 
start to spin only if CPU temperature exceeds 80 C):

dtparam=poe_fan_temp0=8,poe_fan_temp0_hyst=5000
dtparam=poe_fan_temp1=82000,poe_fan_temp1_hyst=2000

Unfortunately, with the linux-raspi2 package in Ubuntu Disco for
RaspberryPi, the fan never stops and it makes the Raspberry Pi extremely
noisy.

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

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

Title:
  RaspberryPi PoE hat fan speed cannot be controlled

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  In Disco branch of linux-raspi2 package, the support of Raspberry Pi's PoE 
Hat is added. Unfortunately the fan speed cannot be controlled the same way as 
in Raspbian.
  In Raspbian, we could set the fan to spin when temperature exceeds certain 
value by adding dtparam in conifg.txt file such as below (this will let the fan 
start to spin only if CPU temperature exceeds 80 C):

  dtparam=poe_fan_temp0=8,poe_fan_temp0_hyst=5000
  dtparam=poe_fan_temp1=82000,poe_fan_temp1_hyst=2000

  Unfortunately, with the linux-raspi2 package in Ubuntu Disco for
  RaspberryPi, the fan never stops and it makes the Raspberry Pi
  extremely noisy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1829236/+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 1825229] [NEW] request to supercede the interim changes for 1815268 with upstream commit 8065a779

2019-04-17 Thread Si-Wei Liu

Public bug reported:

The interm patch in LP# 1815268 was positioned as a way of mitigation to
the rename race condition as described in that bug. Now, the upstream
patch has been accepted and it eliminates the need of the delay. The
patch is now in staging tree and should be pulled into mainline soon:

https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=8065a779f17e94536a1c4dcee4f9d88011672f97

Hence we request to back out the delay patch for 1815268 and instead
apply the upstream patch above.

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

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

Title:
  request to supercede the interim changes for 1815268  with upstream
  commit 8065a779

Status in linux package in Ubuntu:
  New

Bug description:
  The interm patch in LP# 1815268 was positioned as a way of mitigation
  to the rename race condition as described in that bug. Now, the
  upstream patch has been accepted and it eliminates the need of the
  delay. The patch is now in staging tree and should be pulled into
  mainline soon:

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=8065a779f17e94536a1c4dcee4f9d88011672f97

  Hence we request to back out the delay patch for 1815268 and instead
  apply the upstream patch above.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825229/+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 1815268] Re: hot add VF to net_failover - could not rename interface '8' from 'eth0' to 'ens4': Device or resource busy

2019-02-22 Thread Si-Wei Liu

Note the patch attached is a tentative workaround that helps mitigate
the issue, but not intended to be a suggested fix. I've initiated a
thread in the Linux netdev mailing list for the resolution. Please find
the relevant thread starting at:

https://www.mail-archive.com/netdev@vger.kernel.org/msg286707.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/1815268

Title:
  hot add VF to net_failover - could not rename interface '8' from
  'eth0' to 'ens4': Device or resource busy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Host has a QEMU/KVM setup with standby virtio-net [1]:

  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on
  -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

  Guest is loaded with Xenial Xerus (16.04.5),

  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/";
  SUPPORT_URL="http://help.ubuntu.com/";
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 

  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever

  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)

  VF now shows up in guest as "eth0" instead of the expected "ens4":

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  6: eth0:  mtu 1500 qdisc mq master ens3 
state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  vsbalakr@ubuntu-16:~$

  /var/log/syslog shows that renaming to "ens4" had failed because of
  "Device or resource busy",

  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.231623] ixgbevf :00:04.0: NIC 
Link is Up 10 Gbps
  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.233188] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link is not ready
  Feb  8 18:24:05 u

[Kernel-packages] [Bug 1815268] Re: hot add VF to net_failover - could not rename interface '8' from 'eth0' to 'ens4': Device or resource busy

2019-02-11 Thread Si-Wei Liu

Please find attached a patch (from Oracle Linux) that mitigates the race
with a tunable delay of 100ms.

** Patch added: 
"0001-net_failover-delay-taking-over-primary-device-to-acc.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815268/+attachment/5237749/+files/0001-net_failover-delay-taking-over-primary-device-to-acc.patch

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

Title:
  hot add VF to net_failover - could not rename interface '8' from
  'eth0' to 'ens4': Device or resource busy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Host has a QEMU/KVM setup with standby virtio-net [1]:

  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on
  -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

  Guest is loaded with Xenial Xerus (16.04.5),

  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/";
  SUPPORT_URL="http://help.ubuntu.com/";
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 

  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever

  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)

  VF now shows up in guest as "eth0" instead of the expected "ens4":

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  6: eth0:  mtu 1500 qdisc mq master ens3 
state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  vsbalakr@ubuntu-16:~$

  /var/log/syslog shows that renaming to "ens4" had failed because of
  "Device or resource busy",

  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.231623] ixgbevf :00:04.0: NIC 
Link is Up 10 Gbps
  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.233188] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link

[Kernel-packages] [Bug 1815268] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1815268/+attachment/5237190/+files/ProcInterrupts.txt

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

Title:
  hot add VF to net_failover - could not rename interface '8' from
  'eth0' to 'ens4': Device or resource busy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Host has a QEMU/KVM setup with standby virtio-net [1]:

  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on
  -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

  Guest is loaded with Xenial Xerus (16.04.5),

  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/";
  SUPPORT_URL="http://help.ubuntu.com/";
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 

  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever

  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)

  VF now shows up in guest as "eth0" instead of the expected "ens4":

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  6: eth0:  mtu 1500 qdisc mq master ens3 
state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  vsbalakr@ubuntu-16:~$

  /var/log/syslog shows that renaming to "ens4" had failed because of
  "Device or resource busy",

  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.231623] ixgbevf :00:04.0: NIC 
Link is Up 10 Gbps
  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.233188] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link is not ready
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: RUN 'ifupdown-hotplug' 
/lib/udev/rules.d/80-ifupdown.rules:5
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: IMPORT builtin 'pa

[Kernel-packages] [Bug 1815268] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1815268/+attachment/5237192/+files/PulseList.txt

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

Title:
  hot add VF to net_failover - could not rename interface '8' from
  'eth0' to 'ens4': Device or resource busy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Host has a QEMU/KVM setup with standby virtio-net [1]:

  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on
  -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

  Guest is loaded with Xenial Xerus (16.04.5),

  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/";
  SUPPORT_URL="http://help.ubuntu.com/";
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 

  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever

  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)

  VF now shows up in guest as "eth0" instead of the expected "ens4":

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  6: eth0:  mtu 1500 qdisc mq master ens3 
state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  vsbalakr@ubuntu-16:~$

  /var/log/syslog shows that renaming to "ens4" had failed because of
  "Device or resource busy",

  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.231623] ixgbevf :00:04.0: NIC 
Link is Up 10 Gbps
  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.233188] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link is not ready
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: RUN 'ifupdown-hotplug' 
/lib/udev/rules.d/80-ifupdown.rules:5
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: IMPORT builtin 'path_id' 
/l

[Kernel-packages] [Bug 1815268] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1815268/+attachment/5237193/+files/UdevDb.txt

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

Title:
  hot add VF to net_failover - could not rename interface '8' from
  'eth0' to 'ens4': Device or resource busy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Host has a QEMU/KVM setup with standby virtio-net [1]:

  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on
  -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

  Guest is loaded with Xenial Xerus (16.04.5),

  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/";
  SUPPORT_URL="http://help.ubuntu.com/";
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 

  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever

  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)

  VF now shows up in guest as "eth0" instead of the expected "ens4":

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  6: eth0:  mtu 1500 qdisc mq master ens3 
state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  vsbalakr@ubuntu-16:~$

  /var/log/syslog shows that renaming to "ens4" had failed because of
  "Device or resource busy",

  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.231623] ixgbevf :00:04.0: NIC 
Link is Up 10 Gbps
  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.233188] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link is not ready
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: RUN 'ifupdown-hotplug' 
/lib/udev/rules.d/80-ifupdown.rules:5
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: IMPORT builtin 'path_id' 
/lib/udev

[Kernel-packages] [Bug 1815268] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1815268/+attachment/5237185/+files/CurrentDmesg.txt

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

Title:
  hot add VF to net_failover - could not rename interface '8' from
  'eth0' to 'ens4': Device or resource busy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Host has a QEMU/KVM setup with standby virtio-net [1]:

  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on
  -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

  Guest is loaded with Xenial Xerus (16.04.5),

  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/";
  SUPPORT_URL="http://help.ubuntu.com/";
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 

  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever

  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)

  VF now shows up in guest as "eth0" instead of the expected "ens4":

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  6: eth0:  mtu 1500 qdisc mq master ens3 
state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  vsbalakr@ubuntu-16:~$

  /var/log/syslog shows that renaming to "ens4" had failed because of
  "Device or resource busy",

  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.231623] ixgbevf :00:04.0: NIC 
Link is Up 10 Gbps
  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.233188] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link is not ready
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: RUN 'ifupdown-hotplug' 
/lib/udev/rules.d/80-ifupdown.rules:5
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: IMPORT builtin 'path_i

[Kernel-packages] [Bug 1815268] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1815268/+attachment/5237194/+files/WifiSyslog.txt

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

Title:
  hot add VF to net_failover - could not rename interface '8' from
  'eth0' to 'ens4': Device or resource busy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Host has a QEMU/KVM setup with standby virtio-net [1]:

  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on
  -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

  Guest is loaded with Xenial Xerus (16.04.5),

  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/";
  SUPPORT_URL="http://help.ubuntu.com/";
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 

  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever

  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)

  VF now shows up in guest as "eth0" instead of the expected "ens4":

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  6: eth0:  mtu 1500 qdisc mq master ens3 
state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  vsbalakr@ubuntu-16:~$

  /var/log/syslog shows that renaming to "ens4" had failed because of
  "Device or resource busy",

  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.231623] ixgbevf :00:04.0: NIC 
Link is Up 10 Gbps
  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.233188] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link is not ready
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: RUN 'ifupdown-hotplug' 
/lib/udev/rules.d/80-ifupdown.rules:5
  Feb

[Kernel-packages] [Bug 1815268] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1815268/+attachment/5237191/+files/ProcModules.txt

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

Title:
  hot add VF to net_failover - could not rename interface '8' from
  'eth0' to 'ens4': Device or resource busy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Host has a QEMU/KVM setup with standby virtio-net [1]:

  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on
  -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

  Guest is loaded with Xenial Xerus (16.04.5),

  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/";
  SUPPORT_URL="http://help.ubuntu.com/";
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 

  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever

  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)

  VF now shows up in guest as "eth0" instead of the expected "ens4":

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  6: eth0:  mtu 1500 qdisc mq master ens3 
state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  vsbalakr@ubuntu-16:~$

  /var/log/syslog shows that renaming to "ens4" had failed because of
  "Device or resource busy",

  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.231623] ixgbevf :00:04.0: NIC 
Link is Up 10 Gbps
  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.233188] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link is not ready
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: RUN 'ifupdown-hotplug' 
/lib/udev/rules.d/80-ifupdown.rules:5
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: IMPORT builtin 'path_id'

[Kernel-packages] [Bug 1815268] Re: hot add VF to net_failover - could not rename interface '8' from 'eth0' to 'ens4': Device or resource busy