[Kernel-packages] [Bug 1829983] Re: memcg_stat from controllers test suite in LTP failed (hierarchical_memory_limit is 4096, 8192 expected)

[Po-Hsu Lin]

** Summary changed:

- memcg_stat from controllers test suite in LTP failed
+ memcg_stat from controllers test suite in LTP failed 
(hierarchical_memory_limit is 4096, 8192 expected)

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

Title:
  memcg_stat from controllers test suite in LTP failed
  (hierarchical_memory_limit is 4096, 8192 expected)

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux source package in Bionic:
  Confirmed
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Cosmic:
  Confirmed
Status in linux-aws source package in Cosmic:
  New

Bug description:
   memcg_stat_test 1 TINFO: Starting test 1
   sh: echo: I/O error
   memcg_stat_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 1 TINFO: Running memcg_process --shm -k 3 -s 135168
   memcg_stat_test 1 TINFO: Warming up pid: 31352
   memcg_stat_test 1 TINFO: Process is still here after warm up: 31352
   memcg_stat_test 1 TPASS: cache is 135168 as expected
   memcg_stat_test 2 TINFO: Starting test 2
   sh: echo: I/O error
   memcg_stat_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 2 TINFO: Running memcg_process --mmap-file -s 135168
   memcg_stat_test 2 TINFO: Warming up pid: 31380
   memcg_stat_test 2 TINFO: Process is still here after warm up: 31380
   memcg_stat_test 2 TPASS: mapped_file is 135168 as expected
   memcg_stat_test 3 TINFO: Starting test 3
   sh: echo: I/O error
   memcg_stat_test 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 3 TINFO: Running memcg_process --mmap-lock1 -s 4096
   memcg_stat_test 3 TINFO: Warming up pid: 31409
   memcg_stat_test 3 TINFO: Process is still here after warm up: 31409
   memcg_stat_test 3 TPASS: unevictable is 4096 as expected
   memcg_stat_test 4 TINFO: Starting test 4
   sh: echo: I/O error
   memcg_stat_test 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 4 TINFO: Running memcg_process --mmap-lock2 -s 4096
   memcg_stat_test 4 TINFO: Warming up pid: 31434
   memcg_stat_test 4 TINFO: Process is still here after warm up: 31434
   memcg_stat_test 4 TPASS: unevictable is 4096 as expected
   memcg_stat_test 5 TINFO: Starting test 5
   sh: echo: I/O error
   memcg_stat_test 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 5 TPASS: hierarchical_memory_limit is 4096 as expected
   memcg_stat_test 6 TINFO: Starting test 6
   sh: echo: I/O error
   memcg_stat_test 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   sh: echo: I/O error
   memcg_stat_test 6 TFAIL: hierarchical_memory_limit is 4096, 8192 expected
   memcg_stat_test 7 TINFO: Starting test 7
   sh: echo: I/O error
   memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 7 TCONF: mem+swap is not enabled
   memcg_stat_test 7 TINFO: Starting test 8
   sh: echo: I/O error
   memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_stat_test 7 TCONF: mem+swap is not enabled
   tag=memcg_stat stime=1558504742 dur=4 exit=exited stat=33 core=no cu=16 cs=10

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [14538.862950] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed May 22 07:17:43 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No 

[Kernel-packages] [Bug 2025106] Re: No sounds output after resume from shutdown and reboot

[Jian Hui Lee]

the test case is passed on target device after upgrading to
5.15.0-1037-intel-iotg

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

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

Title:
  No sounds output after resume from shutdown and reboot

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

Bug description:
  [ Impact ]

   * when unmuting mic, there is no sound output after resuming or
  rebooting. unless mute and unmute the mic again.

  [ Test Plan ]

   * boot into the system and unmute the mic by alsamixer.
   * reboot or suspend/resume
   * make sure there is sound from the speaker.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2025106/+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 2023325] Re: [IoTG] TSN commits tracker for bug fix

[Jian Hui Lee]

the network testing in kernel selftest is passed in 5.15.0-1037-intel-
iotg

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

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

Title:
  [IoTG] TSN commits tracker for bug fix

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

Bug description:
  This is a public version of  https://bugs.launchpad.net/bugs/2021543

  This is to add another patch to encounter the reverting patches effect
  in this bug list : https://bugs.launchpad.net/ubuntu-kernel-
  tests/+bug/2008085

  Hi,
  I would like to add one patch to correct the effect of these 5 reverted 
patches in this bug list : 
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2008085

  The reverted patches :
* net:veth.sh in ubuntu_kernel_selftests hang with J-intel-iotg (BUG: unable
  to handle page fault) (LP: #2008085)
  - Revert "rtnetlink: Add return value check"
  - Revert "rtnetlink: Fix unchecked return value of dev_xdp_query_md_btf()"
  - Revert "igc: Enable HW RX Timestamp for AF_XDP ZC"
  - Revert "igc: Add BTF based metadata for XDP"
  - Revert "net/core: XDP metadata BTF netlink API"

  Please find attached our new patch to replace the functionality of 5
  reverted patches . This will ensure the XDP RX HWstamp feature is
  still supported.

  NOTE to Canonical team. Please MAINTAIN the reverted state of the 5
  patches. Just add this one new patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2023325/+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 2026322] Re: Fix non-working MT7921e when pre-boot WiFi is enabled

[Kai-Heng Feng]

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

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

Title:
  Fix non-working MT7921e when pre-boot WiFi is enabled

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

Bug description:
  [Impact]
  When "pre-boot WiFi" is enabled in UEFI, MT7921e WiFi doesn't work under
  Linux.

  [Fix]
  Reset the device earlier at the probing process.

  [Test]
  With the patch applied, WiFi always works regardless of pre-boot WiFi is
  toggled or not.

  [Where problems could occur]
  Probe routine might fail one some other corner cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2026322/+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 2028122] Re: Fix unreliable ethernet cable detection on I219 NIC

[Kai-Heng Feng]

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

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

Title:
  Fix unreliable ethernet cable detection on I219 NIC

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Confirmed
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Confirmed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Confirmed
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  Hotplugging RJ45 ethernet cable only works for one time because ACPI GPE
  wake doesn't working properly anymore.

  [Fix]
  Always use PME poll to read PCI PME to know if there's wake event.

  [Test]
  With the patch applied, ethernet cable can always be detected.

  [Where problems could occur]
  PME poll mechanism periodically reads the PMCTRL register, so the power
  consumption can be slightly higher. The increase will be very low,
  probably won't be noticeable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2028122/+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 2026470] Re: AX210 (8086:6024) WLAN init failed ucode -5 on 5.15 intel IoTG kernel

[Jian Hui Lee]

the wifi AX210 (8086:6024) is workable after upgrading to
5.15.0-1037-intel-iotg

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

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

Title:
   AX210 (8086:6024) WLAN init failed ucode -5 on 5.15 intel IoTG kernel

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

Bug description:
  [Summary]
  AX210 (8086:6024) WLAN init failed ucode -5 on 5.15 Intel IoTG kernel.

  [Steps to reproduce]
  install 5.15 Intel IoTG kernel.

  [Expected result]
  WLAN works with no problem.

  [Actual result]
  Can't detect WLAN.

  [Failure rate]
  100%

  The ucode version 66 would not be loaded successfully on this model with
  the folloing error messages:

  [5.704854] iwlwifi :01:00.0: Detected RF GF, rfid=0x10d000
  [5.706056] iwlwifi :01:00.0: Microcode SW error detected. Restarting 
0x0.
  [5.706258] iwlwifi :01:00.0: Start IWL Error Log Dump:
  [5.706265] iwlwifi :01:00.0: Transport status: 0x004A, valid: 6
  [5.706273] iwlwifi :01:00.0: Loaded firmware version: 66.f1c864e0.0 
ty-a0-gf-a0-66.ucode
  [5.706281] iwlwifi :01:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
  [5.706288] iwlwifi :01:00.0: 0x002002F0 | trm_hw_status0
  [5.706294] iwlwifi :01:00.0: 0x | trm_hw_status1
  [5.706299] iwlwifi :01:00.0: 0x004DA722 | branchlink2
  [5.706306] iwlwifi :01:00.0: 0x004D0CCE | interruptlink1
  [5.706311] iwlwifi :01:00.0: 0x004D0CCE | interruptlink2
  ...
  [6.726292] iwlwifi :01:00.0: Failed to run INIT ucode: -5

  Since ucode version 63 works well on this, and we did the api version
  limitation to the same series model (8086:6020) before, so do the trick
  as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2026470/+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 2028059] Re: remove debug kernel notice in dmesg caused by trace_printk()

[Jian Hui Lee]

the debug kernel notice is gone in 5.15.0-1037-intel-iotg.

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

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

Title:
  remove debug kernel notice in dmesg caused by trace_printk()

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

Bug description:
  [Impact]
  a test kernel notice in dmesg would confuse users.

  [Test Plan]
  1. compile test.
  2. install the kernel and boot into it.
  3. check there is no test kernel notice in dmesg.

  [Regression potential]
  Low. remove/replace trace_printk does not affect the functions.

  [Other info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2028059/+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 2023176] Re: system hang after running stress-ng softlockup stressor while iwlwifi is connected to the station

[Jian Hui Lee]

tried the test case three times on intel wifi machine and passed the
test.

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

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

Title:
  system hang after running stress-ng softlockup stressor while iwlwifi
  is connected to the station

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

Bug description:
  [ Impact ]

   * system got hang after running stress-ng softlockup test while
  iwlwifi is connected to the station

  [ Test Plan ]

   * connect wifi (iwlwifi) to any station. (must do this)

   * execute the following command:
  $ sudo stress-ng --softlockup NUM_CPU_CORES --timeout 30

   * make sure the system still responses after testing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2023176/+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 1964335] Re: Excessive size of kernel modules on RISC-V - modules unstripped

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-starfive/6.2.0-1002.2
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-lunar' to 'verification-done-lunar'. If the
problem still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

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

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


** Tags added: kernel-spammed-lunar-linux-starfive verification-needed-lunar

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

Title:
  Excessive size of kernel modules on RISC-V - modules unstripped

Status in linux-riscv package in Ubuntu:
  Fix Released

Bug description:
  The size of kernel modules on RISC-V indicates that there is a build
  problem:

  kernel/drivers/ata/sata_mv.ko
  amd64: 81713 bytes
  arm64: 85505 bytes
  riscv64: 601417 bytes

  objdump -h shows that there is no section beyond 0xc6fc in the riscv64 file.
  The size of the sections matches what we see on the other architectures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1964335/+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 1975580] Re: Enable StarFive VisionFive board

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-starfive/6.2.0-1002.2
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-lunar' to 'verification-done-lunar'. If the
problem still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

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

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


** Tags added: kernel-spammed-lunar-linux-starfive verification-needed-lunar

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

Title:
  Enable StarFive VisionFive board

Status in linux-starfive-5.17 package in Ubuntu:
  Fix Released
Status in linux-starfive-5.17 source package in Jammy:
  Fix Released

Bug description:
  Enable StarFive VisionFive board

  Apply relevant patches to linux-riscv-5.17 kernel to enable visionfive
  kernel flavour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-starfive-5.17/+bug/1975580/+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 2013232] Re: Enable StarFive VisionFive 2 board

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-starfive/6.2.0-1002.2
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-lunar' to 'verification-done-lunar'. If the
problem still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

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

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


** Tags added: kernel-spammed-lunar-linux-starfive verification-needed-lunar

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

Title:
  Enable StarFive VisionFive 2 board

Status in linux-riscv package in Ubuntu:
  Fix Released

Bug description:
  Apply relevant patches to the linux-riscv kernel to support the
  StarFive JH7110 SoC and their StarFive VisionFive 2 board.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2013232/+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 2028891] [NEW] HTTP boot grub issue

[Asmaa Mnebhi]

Public bug reported:

SRU Justification:

[Impact]

We have tested PXE boot successfully on the BlueField using grubaa64.efi and 
grub.cfg but HTTP boot does not work. 
During HTTP boot, UEFI is able to load the grubaa64.efi but doesn’t load 
grub.cfg and goes instead into the grub rescue shell.
From the grub shell, I try to load the grub.cfg file manually, but I get the 
error shown below.

grub> set
?=0
cmdpath=(http,192.168.200.1)
color_highlight=black/light-gray
color_normal=light-gray/black
feature_200_final=y
feature_all_video_module=y
feature_chainloader_bpb=y
feature_default_font_path=y
feature_menuentry_id=y
feature_menuentry_options=y
feature_nativedisk_cmd=y
feature_ntldr=y
feature_platform_search_hint=y
feature_timeout_style=y
grub_cpu=arm64
grub_netfs_type=efi
grub_platform=efi
lang=
locale_dir=
net_default_interface=efinet2
net_default_ip=192.168.200.2
net_default_mac=
net_default_server=192.168.200.1
net_efinet2_ip=192.168.200.2
net_efinet2_mac=
package_version=2.06-2ubuntu14.1
pager=
prefix=(http,192.168.200.1)/grub
pxe_default_server=192.168.200.1
root=http,192.168.200.1
secondary_locale_dir=

configfile (http,192.168.200.1)/grub/grub.cfg
this doesn't works: error: Fail to send a request! status=0x8002.

However it works if I run:
configfile (tftp,192.168.200.1)/grub/grub.cfg

This forum discusses a similar issue which points to a grub issue:
https://groups.google.com/g/linux.debian.bugs.dist/c/CqfwbhAd-Xg

Could you please help investigate this? Or point me to the right person?


[Fix]

* Unknown yet. Investigate grub.

[Test Case]

* HTTP boot via OOB
* HTTP boot via Connect X

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

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

Title:
  HTTP boot grub issue

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]

  We have tested PXE boot successfully on the BlueField using grubaa64.efi and 
grub.cfg but HTTP boot does not work. 
  During HTTP boot, UEFI is able to load the grubaa64.efi but doesn’t load 
grub.cfg and goes instead into the grub rescue shell.
  From the grub shell, I try to load the grub.cfg file manually, but I get the 
error shown below.

  grub> set
  ?=0
  cmdpath=(http,192.168.200.1)
  color_highlight=black/light-gray
  color_normal=light-gray/black
  feature_200_final=y
  feature_all_video_module=y
  feature_chainloader_bpb=y
  feature_default_font_path=y
  feature_menuentry_id=y
  feature_menuentry_options=y
  feature_nativedisk_cmd=y
  feature_ntldr=y
  feature_platform_search_hint=y
  feature_timeout_style=y
  grub_cpu=arm64
  grub_netfs_type=efi
  grub_platform=efi
  lang=
  locale_dir=
  net_default_interface=efinet2
  net_default_ip=192.168.200.2
  net_default_mac=
  net_default_server=192.168.200.1
  net_efinet2_ip=192.168.200.2
  net_efinet2_mac=
  package_version=2.06-2ubuntu14.1
  pager=
  prefix=(http,192.168.200.1)/grub
  pxe_default_server=192.168.200.1
  root=http,192.168.200.1
  secondary_locale_dir=

  configfile (http,192.168.200.1)/grub/grub.cfg
  this doesn't works: error: Fail to send a request! status=0x8002.

  However it works if I run:
  configfile (tftp,192.168.200.1)/grub/grub.cfg

  This forum discusses a similar issue which points to a grub issue:
  https://groups.google.com/g/linux.debian.bugs.dist/c/CqfwbhAd-Xg

  Could you please help investigate this? Or point me to the right
  person?


  [Fix]

  * Unknown yet. Investigate grub.

  [Test Case]

  * HTTP boot via OOB
  * HTTP boot via Connect X

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2028891/+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 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

[Eli]

I'm running day-to-day without thermald installed, so I will need to
find time to do this. But yes I can.

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

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

Status in linux package in Ubuntu:
  Incomplete
Status in thermald package in Ubuntu:
  New

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

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

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

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

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

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

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

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

[Dimitri John Ledkov]

https://lists.ubuntu.com/archives/kernel-team/2023-July/141443.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/2028550

Title:
  Backport support to tolerate ZSTD compressed firmware files

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

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

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

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

  [ Test Plan ]

   * Boot new build of GA linux kernel with
  CONFIG_FW_LOADER_COMPRESS_ZSTD

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

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

  [ Where problems could occur ]

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

  [ Other Info ]

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

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


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

[Kernel-packages] [Bug 2020627] Re: upgrade iwlwifi firmware of FW API 72 for WiFi 6E support in Malaysia and Morocco

[Timo Aaltonen]

nevermind, adding the tag back according to your comment in #5

** Tags added: verification-done-jammy

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

Title:
  upgrade iwlwifi firmware of FW API 72 for WiFi 6E support in Malaysia
  and Morocco

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Jammy:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  iwlwifi takes firmware updates to support WiFi 6E in Malaysia and
  Morocco. The models in concern are AX210 (iwlwifi-ty-a0-gf-a0-*),
  AX211 (iwlwifi-so-a0-gf-a0-*) and AX411 (iwlwifi-so-a0-gf4-a0-*).

  [Fix]

  pnvm along with the ucode firmware from upstream commit 5bc279fb161d
  ("iwlwifi:  update core69 and core72 firmwares for So device") are
  required. While the pnvm and ucode blobs may not be upgraded
  simultaneously in one single commit, those involved in the upgrade
  path are also pulled.

  [Test Case]

  Use `iw` to enumerate supported WiFi 6E band:

  $ iw reg get
  global
  country : DFS-FCC
  ...
  (5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN

  [Where problems could occur]

  Currently linux-5.15 has FW API 66, linux-hwe-5.19 or above has 72,
  linux-6.3 has 74, and linux-unstable (v6.4) or above has 78, so this
  will update iwlwifi firmware usage for kernels <= 6.2 in Jammy, e.g.
  linux-oem-6.1, linux-5.15.

  [Other Info]

  Blobs with FW APIs >= 72 do no harm to jammy kernels, but will be
  referenced in oem-6.5 if planned.

  These commits have been included in linux-firmware/lunar, so only
  Jammy is nominated for fix.

  == original bug report ==

  AX210:
  -72 ucode: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-ty-a0-gf-a0-72.ucode?id=4309412c0d872897dc913c7d2797bb5ce05893ad
  pnvm: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81

  AX211:
  -72 ucode: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf-a0-72.ucode?id=5bc279fb161d529baaf8e837d900235fbbe9bf2f
  pnvm: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81

  AX411:
  -72 ucode: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf4-a0-72.ucode?id=5bc279fb161d529baaf8e837d900235fbbe9bf2f
  pnvm: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf4-a0.pnvm?id=78a8782a9e51e502a6ed267d270c6925fb738805

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2020627/+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 2024427] Re: potential S3 issue for amdgpu Navi 31/Navi33

[Timo Aaltonen]

lunar needs to be verified as well

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

Title:
  potential S3 issue for amdgpu Navi 31/Navi33

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  In Progress
Status in linux-firmware source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Triaged
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [SRU Justification]

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

  [Impact]

  Under stress testing it was reported that the amdgpu Navi31/Navi33 platforms
  will sometimes fail to wake from S3.

  [Fix]

  kernel patches:
  ac2f5739fdca drm/amdgpu/mes11: enable reg active poll
  a2fe4534bb38 drm/amd/amdgpu: update mes11 api def
  da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin
  616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2
  09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4

  firmware patches:
  * Navi31: ffe1a41e2ddb amdgpu: update GC 11.0.0 firmware for amd.5.5 release
  * Navi33: a5d7b4df1a76 amdgpu: update GC 11.0.2 firmware for amd.5.5 release

  [Test Case]

  $ checkbox-cli run com.canonical.certification::stress-
  suspend-30-cycles-with-reboots-automated

  [Where problems could occur]

  Little we know about the firmware fixes. However, while with these commits 
have
  been pulled via stable kernel fixes, the driver begins to request new firmware
  blobs of a different filename.

  [Other Info]

  The kernel driver commits are in v6.4-rc1, backported to v6.3.4, v6.1.31, and
  partially (missing da9a8dc33da2, 616843d5a11b) v6.2.16. Only linux/lunar has 
to
  be fixed.

  For the firmware parts, they have been included in linux-firmware/mantic,
  leaving linux-firmware/lunar and linux-firmware/jammy to be fixed.

  == original bug report ==

  amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue.

  amdgpu:
  ac2f5739fdca drm/amdgpu/mes11: enable reg active poll
  a2fe4534bb38 drm/amd/amdgpu: update mes11 api def
  da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin
  616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2
  09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4

  Navi31:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ffe1a41e2ddbc39109b12d95dcac282d90eba8fc
  Navi33:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a5d7b4df1a76f82e2ecb725cc1b56ce111830bac

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2024427/+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 2024774] Re: AMD Rembrandt / Phoenix PSR-SU related freezes

[Timo Aaltonen]

how about verifying lunar too?

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

Title:
  AMD Rembrandt / Phoenix PSR-SU related freezes

Status in Linux Firmware:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Lunar:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   When using kernel 6.2 or later AMD has enabled PSR selective update (PSR-SU).
   After a non-deterministic amount of time the system may hang with a message 
like this in the logs:
   "[amdgpu :67:00.0: [drm] *ERROR* [CONNECTOR:78:eDP-1] commit wait timed 
out]"

   Affects users of laptops that contain:
   * AMD Rembrandt (Yellow Carp) or AMD Phoenix (Pink Sardine) chips
   * eDP panels with Parade TCONs (8-03 and 8-01 both reported to fail)

  [ Test Plan ]

   * Test an affected laptop with the newer firmware and ensure that PSR-SU 
function can be enabled and system is stable.
   * Ensure other functions such as hotplugging monitors and suspending 
continue to work.

  [ Where problems could occur ]

   * Affected firmware only is loaded on Rembrandt and Phoenix laptops.
  Problems would be localized to these machines.

  [ Other Info ]
  The minimum firmware needed to help these hangs:
  * Rembrandt: 0x43a or later
  * Phoenix: 0x8001000 or later

  The following commit upgrades the firmware for Rembrandt 
(amdgpu/yellow_carp_dmcub.bin) to 0x43c:
  9dbd8ec2 ("amdgpu: DMCUB updates for various AMDGPU asics")

  The following commit upgrades the firmware for Phoenix 
(amdgpu/dcn_3_1_4_dmcub.bin) to 0x8001a00:
  045b2136 ("amdgpu: update DMCUB to v0.0.172.0 for various AMDGPU ASICs")

  The TCON in a given laptop can be identified from the DPCD with this script:
  https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/psr.py

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/2024774/+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 2020627] Re: upgrade iwlwifi firmware of FW API 72 for WiFi 6E support in Malaysia and Morocco

[Timo Aaltonen]

why did you remove the verification-done-jammy tag, if it's working?

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

Title:
  upgrade iwlwifi firmware of FW API 72 for WiFi 6E support in Malaysia
  and Morocco

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Jammy:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  iwlwifi takes firmware updates to support WiFi 6E in Malaysia and
  Morocco. The models in concern are AX210 (iwlwifi-ty-a0-gf-a0-*),
  AX211 (iwlwifi-so-a0-gf-a0-*) and AX411 (iwlwifi-so-a0-gf4-a0-*).

  [Fix]

  pnvm along with the ucode firmware from upstream commit 5bc279fb161d
  ("iwlwifi:  update core69 and core72 firmwares for So device") are
  required. While the pnvm and ucode blobs may not be upgraded
  simultaneously in one single commit, those involved in the upgrade
  path are also pulled.

  [Test Case]

  Use `iw` to enumerate supported WiFi 6E band:

  $ iw reg get
  global
  country : DFS-FCC
  ...
  (5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN

  [Where problems could occur]

  Currently linux-5.15 has FW API 66, linux-hwe-5.19 or above has 72,
  linux-6.3 has 74, and linux-unstable (v6.4) or above has 78, so this
  will update iwlwifi firmware usage for kernels <= 6.2 in Jammy, e.g.
  linux-oem-6.1, linux-5.15.

  [Other Info]

  Blobs with FW APIs >= 72 do no harm to jammy kernels, but will be
  referenced in oem-6.5 if planned.

  These commits have been included in linux-firmware/lunar, so only
  Jammy is nominated for fix.

  == original bug report ==

  AX210:
  -72 ucode: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-ty-a0-gf-a0-72.ucode?id=4309412c0d872897dc913c7d2797bb5ce05893ad
  pnvm: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81

  AX211:
  -72 ucode: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf-a0-72.ucode?id=5bc279fb161d529baaf8e837d900235fbbe9bf2f
  pnvm: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81

  AX411:
  -72 ucode: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf4-a0-72.ucode?id=5bc279fb161d529baaf8e837d900235fbbe9bf2f
  pnvm: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf4-a0.pnvm?id=78a8782a9e51e502a6ed267d270c6925fb738805

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2020627/+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 2018236] Re: Fix ADL: System shutdwon automically when run Prime95 with i9-12900K

[Andreas Hasenack]

I'm just noticing the discrepancy between the test plan, and the test
execution. If you are confident that a 10min run reproduces the problem,
then please update the test plan accordingly, because it currently says
6h.

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

Title:
  Fix ADL: System shutdwon automically when run Prime95 with
  i9-12900K

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

Bug description:
  [Description]
  System shutdown automatically when stressing the machine.

  [Fix]
  Need these two to fix the issue.

  cbdd92b) Parse idsp and trips
  d385f20) Use PL1 max/min from PPCC when policies match
  
https://github.com/intel/thermal_daemon/commit/d385f20764e1e5477450405be71ec719adc973be

  [Test Case]
  1. Find a unit with i9-12900k CPU and air cooling
  2. Install tools
  #sudo apt install stress-ng s-tui
  #sudo systemctl stop thermald
  #sudo thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > 
thermald_log.txt &
  #download prime95 linux version: p95v308b15.linux64.tar.gz and decompress
  4. Stress test: (you may need to open multiple terminals for the test)
  #./mprime
  #sudo stress-ng -a 0 --class cpu,cpu-cache --ignite-cpu -v
  5. monitor cpu temperature for 6 hours if you didn’t hit overheat and 
shutdown issue.
  #sudo s-tui -c

  [Where problems could occur]
  low

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2018236/+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 2018236] Re: Fix ADL: System shutdwon automically when run Prime95 with i9-12900K

[koba]

@Andreas, as per personal experience, if issue is occurred, it would shutdown 
less than 10 mins.
so is it necessary to run 6 hours?

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

Title:
  Fix ADL: System shutdwon automically when run Prime95 with
  i9-12900K

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

Bug description:
  [Description]
  System shutdown automatically when stressing the machine.

  [Fix]
  Need these two to fix the issue.

  cbdd92b) Parse idsp and trips
  d385f20) Use PL1 max/min from PPCC when policies match
  
https://github.com/intel/thermal_daemon/commit/d385f20764e1e5477450405be71ec719adc973be

  [Test Case]
  1. Find a unit with i9-12900k CPU and air cooling
  2. Install tools
  #sudo apt install stress-ng s-tui
  #sudo systemctl stop thermald
  #sudo thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > 
thermald_log.txt &
  #download prime95 linux version: p95v308b15.linux64.tar.gz and decompress
  4. Stress test: (you may need to open multiple terminals for the test)
  #./mprime
  #sudo stress-ng -a 0 --class cpu,cpu-cache --ignite-cpu -v
  5. monitor cpu temperature for 6 hours if you didn’t hit overheat and 
shutdown issue.
  #sudo s-tui -c

  [Where problems could occur]
  low

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2018236/+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 2007579] Re: Raptor Lake Thermald ITMT version 2 support

[koba]

@Andreas, correct it.

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

Title:
  Raptor Lake Thermald ITMT version 2 support

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Bionic:
  Won't Fix
Status in thermald source package in Focal:
  Won't Fix
Status in thermald source package in Jammy:
  Fix Committed
Status in thermald source package in Kinetic:
  Fix Released
Status in thermald source package in Lunar:
  Fix Released

Bug description:
  == SRU Justification Kinetic ==

  Raptor Lake system uses ITMT v2 instead of V1 for thermal
  configuration via GDDV.

  This was observed on Dell XPS 9320 system.
  Because thermald can't parse V2 table, it is not getting correct thermal 
threshold temperature and power limits.

  == The Fix ==

  This is fixed in upstream thermald by the patch:
  
https://github.com/intel/thermal_daemon/commit/90d56bc06cdcf78e7398ea7da389401516591774
  This fix is part of Thermald 2.5.2 release.

  The fix applies cleanly and this is already in Ubuntu Lunar in
  thermald 2.5.2.  The fix checks for illegal ITMT version and handles
  version 2 as a specific exceptional case.

  == Regression Risks ==

  For systems that do not used ITMT, no change in behaviour will occur.
  Systems with versions > 2 (currently not valid) will not have ITMT
  parsed anymore; this will avoid misinterpreting unsupported ITMT data.
  Finally, version 2 of ITMT will be now parsed differently and
  additional fields will be parsed and these will be ignored as
  intended.

  == Test Plan ==

  Test against a Dell XPS 9320 system. See if it handles the ITMT correctly. 
The thermald log should indicate version 2 is being used with the message: 
  "ignore dummy_str: ds d1 d2 d3 " where ds = a string, d1 .. d3 are uint64 
values that are parsed and ignored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2007579/+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 2012260] Re: Add support for Alder Lake N

[koba]

@Andreas, it also work on generic jammy kernel.

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

Title:
  Add support for Alder Lake N

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Jammy:
  Fix Committed
Status in thermald source package in Kinetic:
  Won't Fix

Bug description:
  [Impact]

   * Support thermald on Alder Lake N CPU.

  [Test Plan]

   * Use a machine with a Alder Lake N cpu.

   * systemctl status thermald

   * Status of thermald should be `running`

  [Where problems could occur]

   * This change is to add support for Alder Lake N in thermald, which
  won't impact other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2012260/+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 2018236] Re: Fix ADL: System shutdwon automically when run Prime95 with i9-12900K

[Andreas Hasenack]

The test plan calls for a 6h run:
"""
5. monitor cpu temperature for 6 hours if you didn’t hit overheat and shutdown 
issue.
"""

Yet the verification says it ran for only 15min?

Is the original test plan wrong, or why is a 15min run ok?


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

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

Title:
  Fix ADL: System shutdwon automically when run Prime95 with
  i9-12900K

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

Bug description:
  [Description]
  System shutdown automatically when stressing the machine.

  [Fix]
  Need these two to fix the issue.

  cbdd92b) Parse idsp and trips
  d385f20) Use PL1 max/min from PPCC when policies match
  
https://github.com/intel/thermal_daemon/commit/d385f20764e1e5477450405be71ec719adc973be

  [Test Case]
  1. Find a unit with i9-12900k CPU and air cooling
  2. Install tools
  #sudo apt install stress-ng s-tui
  #sudo systemctl stop thermald
  #sudo thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > 
thermald_log.txt &
  #download prime95 linux version: p95v308b15.linux64.tar.gz and decompress
  4. Stress test: (you may need to open multiple terminals for the test)
  #./mprime
  #sudo stress-ng -a 0 --class cpu,cpu-cache --ignite-cpu -v
  5. monitor cpu temperature for 6 hours if you didn’t hit overheat and 
shutdown issue.
  #sudo s-tui -c

  [Where problems could occur]
  low

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2018236/+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 2012260] Re: Add support for Alder Lake N

[Andreas Hasenack]

kinetic is eol

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

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

Title:
  Add support for Alder Lake N

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Jammy:
  Fix Committed
Status in thermald source package in Kinetic:
  Won't Fix

Bug description:
  [Impact]

   * Support thermald on Alder Lake N CPU.

  [Test Plan]

   * Use a machine with a Alder Lake N cpu.

   * systemctl status thermald

   * Status of thermald should be `running`

  [Where problems could occur]

   * This change is to add support for Alder Lake N in thermald, which
  won't impact other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2012260/+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 2012260] Re: Add support for Alder Lake N

[Andreas Hasenack]

Hm, question: I see you are running an oem kernel. Does this thermald
fix only work when running on that specific kernel? Or will it also work
on the normal jammy kernel?

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

Title:
  Add support for Alder Lake N

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Jammy:
  Fix Committed
Status in thermald source package in Kinetic:
  Won't Fix

Bug description:
  [Impact]

   * Support thermald on Alder Lake N CPU.

  [Test Plan]

   * Use a machine with a Alder Lake N cpu.

   * systemctl status thermald

   * Status of thermald should be `running`

  [Where problems could occur]

   * This change is to add support for Alder Lake N in thermald, which
  won't impact other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2012260/+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 2012260] Re: Add support for Alder Lake N

[Andreas Hasenack]

I'm adding notes do these thermald bugs because it's one upload
addressing 7 bugs, and some have verification done in other bugs, so it
can be hard to track.

This verification is ok.

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

Title:
  Add support for Alder Lake N

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Jammy:
  Fix Committed
Status in thermald source package in Kinetic:
  Won't Fix

Bug description:
  [Impact]

   * Support thermald on Alder Lake N CPU.

  [Test Plan]

   * Use a machine with a Alder Lake N cpu.

   * systemctl status thermald

   * Status of thermald should be `running`

  [Where problems could occur]

   * This change is to add support for Alder Lake N in thermald, which
  won't impact other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2012260/+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 2007579] Re: Raptor Lake Thermald ITMT version 2 support

[Andreas Hasenack]

Hi @koba,

I think you pasted the wrong log in this bug here. You pasted the
verification for INT3400 (bug #1989044)?


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

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

Title:
  Raptor Lake Thermald ITMT version 2 support

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Bionic:
  Won't Fix
Status in thermald source package in Focal:
  Won't Fix
Status in thermald source package in Jammy:
  Fix Committed
Status in thermald source package in Kinetic:
  Fix Released
Status in thermald source package in Lunar:
  Fix Released

Bug description:
  == SRU Justification Kinetic ==

  Raptor Lake system uses ITMT v2 instead of V1 for thermal
  configuration via GDDV.

  This was observed on Dell XPS 9320 system.
  Because thermald can't parse V2 table, it is not getting correct thermal 
threshold temperature and power limits.

  == The Fix ==

  This is fixed in upstream thermald by the patch:
  
https://github.com/intel/thermal_daemon/commit/90d56bc06cdcf78e7398ea7da389401516591774
  This fix is part of Thermald 2.5.2 release.

  The fix applies cleanly and this is already in Ubuntu Lunar in
  thermald 2.5.2.  The fix checks for illegal ITMT version and handles
  version 2 as a specific exceptional case.

  == Regression Risks ==

  For systems that do not used ITMT, no change in behaviour will occur.
  Systems with versions > 2 (currently not valid) will not have ITMT
  parsed anymore; this will avoid misinterpreting unsupported ITMT data.
  Finally, version 2 of ITMT will be now parsed differently and
  additional fields will be parsed and these will be ignored as
  intended.

  == Test Plan ==

  Test against a Dell XPS 9320 system. See if it handles the ITMT correctly. 
The thermald log should indicate version 2 is being used with the message: 
  "ignore dummy_str: ds d1 d2 d3 " where ds = a string, d1 .. d3 are uint64 
values that are parsed and ignored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2007579/+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 1989044] Re: RPL: Add INT3400 base path

[Andreas Hasenack]

I'm adding notes do these thermald bugs because it's one upload
addressing 7 bugs, and some have verification done in other bugs, so it
can be hard to track.

This verification is ok.

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

Title:
  RPL: Add INT3400 base path

Status in thermald package in Ubuntu:
  New
Status in thermald source package in Focal:
  In Progress
Status in thermald source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
   * Add INT3400 base path for Raptor Lake CPU.

  [Test Plan]
   * Use a machine with a Raptor Lake cpu.
   * check the thermald log.
   * Get the base path of INT3400.

  [Where problems could occur]
   * This change is to add path in INT3400 for Raptor Lake, which won't impact 
other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1989044/+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 1981087] Re: thermald prematurely throttling GPU

[Andreas Hasenack]

We talked OOB, and I think this would be enough for test 1:
- run some workload (the benchmark might be fine) that, with thermald from 
jammy (2.4.9-1ubuntu0.2), will throttle the GPU "too soon". I assume there will 
be some log message about this throttling. Note the benchmark should exercise 
the GPU, as that is what was reported here in this bug.
- run the same workload with thermald from proposed (2.4.9-1ubuntu0.3). If the 
throttling is now happening later, which is expected, then we should a) have 
better benchmark numbers; b) no throttling in the logs, or  throttling 
happening at higher GPU temperatures

Test 2 results are in
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1995606/comments/25
? Ok, I'll check, but for the next time please try to keep the bug
verifications in the bugs they are meant to, as this upload has 7
associated bugs :)

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

Title:
  thermald prematurely throttling GPU

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

Bug description:
  [Impact]
   * thermald prematurely throttling GPU

  [Fix]
  This fix is removed the code refactoring part and keep the necessary.

  (patch: 0009-Install-passive-default.patch)
  82609c7) Separate Adaptive engine and GDDV

  [Test Plan]
  Test1,
   * Run game on the target machine.
   * the FPS must not be significantly reduced.
  Test2,
   * Run on others platform, ADL/TGL/CML/CFL/KBL.
   * Use monitoring tool(e.g. s-tui) and stress-ng to verify if the machine 
runs normally.

  [Where problems could occur]
   * better support for Passive Policy. currently passive policy 1 is supported 
and it should have a bug if the machine only enable pssive policy 2.

  ~~~
  I got a new game and started playing it
  It would run at over 100 FPS solidly some of the time and then cyclically dip 
down to below 20 FPS for a few minutes

  I determined that it was thermald trying to keep my GPU below 70°C
  to determine this I sudo systemctl stop thermald
  The game ran solidly and consistently with the GPU at 75°C

  This is well below the specs set by the manufacturer and perhaps
  unreasonably low for a laptop

  But more importantly I was given no indication this was happening. I
  had to sleuth it out myself.

  Perhaps it is impossible to determine good defaults for all hardware,
  I don't know. However without an indication that this is happening
  there will be a lot of people with a mysteriously broken experience.
  This was extremely difficult for me to find and I had several friend
  who are experts on linux gaming and video drivers trying to track this
  down. I discovered it by luck and perseverance.

  This absolutely needs some sort of indication and hopefully a way to
  remedy it from the GUI. ideally it would set thermal limits that are
  more in line with what the device is designed for and not a
  conservative default if at all possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: thermald 2.4.9-1
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Fri Jul  8 16:08:55 2022
  InstallationDate: Installed on 2020-10-19 (626 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: thermald
  UpgradeStatus: Upgraded to jammy on 2022-06-17 (20 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1981087/+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 1981087] Re: thermald prematurely throttling GPU

[koba]

@Andreas, 
for the test 1, actually i can't hit the issue on my side so just show the 
benchmark between the proposded and upstream version. 
i can ran the previous version to compare.
i still need Colette's help to verify but didnt get the reply.

for test 2, it just to run thermald and check if the cpu is throttled.
please review this in LP#1995606, #25.

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

Title:
  thermald prematurely throttling GPU

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

Bug description:
  [Impact]
   * thermald prematurely throttling GPU

  [Fix]
  This fix is removed the code refactoring part and keep the necessary.

  (patch: 0009-Install-passive-default.patch)
  82609c7) Separate Adaptive engine and GDDV

  [Test Plan]
  Test1,
   * Run game on the target machine.
   * the FPS must not be significantly reduced.
  Test2,
   * Run on others platform, ADL/TGL/CML/CFL/KBL.
   * Use monitoring tool(e.g. s-tui) and stress-ng to verify if the machine 
runs normally.

  [Where problems could occur]
   * better support for Passive Policy. currently passive policy 1 is supported 
and it should have a bug if the machine only enable pssive policy 2.

  ~~~
  I got a new game and started playing it
  It would run at over 100 FPS solidly some of the time and then cyclically dip 
down to below 20 FPS for a few minutes

  I determined that it was thermald trying to keep my GPU below 70°C
  to determine this I sudo systemctl stop thermald
  The game ran solidly and consistently with the GPU at 75°C

  This is well below the specs set by the manufacturer and perhaps
  unreasonably low for a laptop

  But more importantly I was given no indication this was happening. I
  had to sleuth it out myself.

  Perhaps it is impossible to determine good defaults for all hardware,
  I don't know. However without an indication that this is happening
  there will be a lot of people with a mysteriously broken experience.
  This was extremely difficult for me to find and I had several friend
  who are experts on linux gaming and video drivers trying to track this
  down. I discovered it by luck and perseverance.

  This absolutely needs some sort of indication and hopefully a way to
  remedy it from the GUI. ideally it would set thermal limits that are
  more in line with what the device is designed for and not a
  conservative default if at all possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: thermald 2.4.9-1
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Fri Jul  8 16:08:55 2022
  InstallationDate: Installed on 2020-10-19 (626 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: thermald
  UpgradeStatus: Upgraded to jammy on 2022-06-17 (20 days ago)

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


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

Re: [Kernel-packages] [Bug 2028800] Re: Kubuntu 23.04 boots with 6.2.0-24-generic but not 6.2.0-25-generic or 6.2.0-26-generic

[John Hayes]

I here is the final output printed to the screen when booting with 
6.2.0-26-generic:

8.958982] usb 3-1: 3:1: cannot get freg at ep ex86
9.012274] snd_hda_intel o000:23:00.4: no codecs found!
9.028482] usb 3-1: 3:2: cannot get freq at ep exB6
9.092481] usb 3-1: 3:3: cannot get freq at ep exB6
9.318232] usb 3-1: Failed to query (GET-INFO) UVC control 9 on unit 1: 
-32 (exp. 1).
12.755762] over layfs : miss ing "lowerdir'


On 7/27/23 04:25, Stefan Bader wrote:
> At an initial glance this might not be hanging but not showing anything.
> Comparing the two logs the GPU driver (amdgpu) does not seem to get
> loaded or start. Also some messages related to the IOMMU (Amd-Vi) are
> missing.
>
-- 
Cheers,
John Hayes

Veteran / Developer / Data Analyst
Linkedin 
Twitter: @HayesJohnD

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

Title:
  Kubuntu 23.04 boots with 6.2.0-24-generic but not 6.2.0-25-generic or
  6.2.0-26-generic

Status in linux package in Ubuntu:
  New

Bug description:
  I can run Kubuntu 23.04 with kernel 6.2.0-24-generic but not
  6.2.0-25-generic or 6.2.0-26-generic. I have installed the latest AMD
  microcode, but that did not help. I am attaching the journalctl report
  for 6.2.0-24-generic that boots fully and the journalctl report for
  6.2.0-26-generic that does not boot fully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028800/+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 1981087] Re: thermald prematurely throttling GPU

[Andreas Hasenack]

Hi koba, thanks for your update.

I don't know how to interpret it, though, I'm not familiar with that
benchmark you ran. The test plan asks for a game (let's call it
workload) to be used, and to show that the game is not throttled, i.e.,
FPS is not reduced.

We could transpose that to "run benchmark and show that the performance
is not reduced" I suppose, but then we would need numbers from a run
with the previous thermald and the new one. You showed numbers between
the proposed thermald and a later upstream one. And did thermald kick
in? Was the GPU throttled? The [impact] section of this bug says that
thermald was prematurely throttling the GPU. How can you show that now
it's not doing it anymore?

And what about test 2?
" * Run on others platform, ADL/TGL/CML/CFL/KBL."

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

Title:
  thermald prematurely throttling GPU

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

Bug description:
  [Impact]
   * thermald prematurely throttling GPU

  [Fix]
  This fix is removed the code refactoring part and keep the necessary.

  (patch: 0009-Install-passive-default.patch)
  82609c7) Separate Adaptive engine and GDDV

  [Test Plan]
  Test1,
   * Run game on the target machine.
   * the FPS must not be significantly reduced.
  Test2,
   * Run on others platform, ADL/TGL/CML/CFL/KBL.
   * Use monitoring tool(e.g. s-tui) and stress-ng to verify if the machine 
runs normally.

  [Where problems could occur]
   * better support for Passive Policy. currently passive policy 1 is supported 
and it should have a bug if the machine only enable pssive policy 2.

  ~~~
  I got a new game and started playing it
  It would run at over 100 FPS solidly some of the time and then cyclically dip 
down to below 20 FPS for a few minutes

  I determined that it was thermald trying to keep my GPU below 70°C
  to determine this I sudo systemctl stop thermald
  The game ran solidly and consistently with the GPU at 75°C

  This is well below the specs set by the manufacturer and perhaps
  unreasonably low for a laptop

  But more importantly I was given no indication this was happening. I
  had to sleuth it out myself.

  Perhaps it is impossible to determine good defaults for all hardware,
  I don't know. However without an indication that this is happening
  there will be a lot of people with a mysteriously broken experience.
  This was extremely difficult for me to find and I had several friend
  who are experts on linux gaming and video drivers trying to track this
  down. I discovered it by luck and perseverance.

  This absolutely needs some sort of indication and hopefully a way to
  remedy it from the GUI. ideally it would set thermal limits that are
  more in line with what the device is designed for and not a
  conservative default if at all possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: thermald 2.4.9-1
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Fri Jul  8 16:08:55 2022
  InstallationDate: Installed on 2020-10-19 (626 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: thermald
  UpgradeStatus: Upgraded to jammy on 2022-06-17 (20 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1981087/+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 2028800] Re: Kubuntu 23.04 boots with 6.2.0-24-generic but not 6.2.0-25-generic or 6.2.0-26-generic

[koba]

maybe you also need linux-modules-extra-6.2.0-25-generic

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

Title:
  Kubuntu 23.04 boots with 6.2.0-24-generic but not 6.2.0-25-generic or
  6.2.0-26-generic

Status in linux package in Ubuntu:
  New

Bug description:
  I can run Kubuntu 23.04 with kernel 6.2.0-24-generic but not
  6.2.0-25-generic or 6.2.0-26-generic. I have installed the latest AMD
  microcode, but that did not help. I am attaching the journalctl report
  for 6.2.0-24-generic that boots fully and the journalctl report for
  6.2.0-26-generic that does not boot fully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028800/+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 2028800] Re: Kubuntu 23.04 boots with 6.2.0-24-generic but not 6.2.0-25-generic or 6.2.0-26-generic

[Mario Limonciello]

Something that I notice in both logs:

/etc/udev/rules.d/70-amdgpu.rules:1 Invalid operator for GROUP.

Where did this file come from and what's in it?

Also; is it possible you're just missing the matching linux-
modules-6.2.0-25-generic/linux-modules-6.2.0-26-generic?

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

Title:
  Kubuntu 23.04 boots with 6.2.0-24-generic but not 6.2.0-25-generic or
  6.2.0-26-generic

Status in linux package in Ubuntu:
  New

Bug description:
  I can run Kubuntu 23.04 with kernel 6.2.0-24-generic but not
  6.2.0-25-generic or 6.2.0-26-generic. I have installed the latest AMD
  microcode, but that did not help. I am attaching the journalctl report
  for 6.2.0-24-generic that boots fully and the journalctl report for
  6.2.0-26-generic that does not boot fully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028800/+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 1942260] Re: compress firmware in /lib/firmware

[Benjamin Drung]

Then setting ZSTD_CLEVEL in debian/scripts/install-firmware should do
the trick (needs testing!):

ZSTD_CLEVEL=19 ./copy-firmware.sh --zstd "${staging_dir}"

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

Title:
  compress firmware in /lib/firmware

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-firmware-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  -- initramfs-tools

  [Impact]

   * linux supports xz compressed linux-firmware which saves disk space.
  In focal, initramfs-tools only knows how to included uncompressed
  firmware files (even when kernel supports loading compressed ones).
  Newer releases of linux-firmware may use compressed firmware files
  only, in such cases it would be nice for focal's initramfs-tools to
  support compressed firmware files in case of partial or incomplete
  upgrades (i.e. linux-firmware force installed or upgraded, without
  newer initramfs-tools). The proposed changes to initramfs-tools are
  backwards and forwards compatible, they prefer to include uncompressed
  firmware files; and if missing, include compressed firmware files in
  their uncompressed form. Thus maintaining compatibility with any
  kernels, irrespective of compressed/uncompressed firmware inputs.

  [Test Plan]

   * Compress all files shipped by linux-firmware with xz

   * Rebuild initrd

   * Check that all the same firmware files are still included in the
  initramfs, in their uncompressed form as before

  [Where problems could occur]

   * This SRU is precautionary to prevent accidental installation of
  compressed linux-firmware from generating incorrect initramfs. It
  should be noted that whilst initramfs-tools would create a compatible
  initramfs with any kernels, pre-v5.3 kernels do not support xz
  compressed firmware files at runtime. Mixing this new initramfs with
  compressed firmwares and pre 5.3 kernels may lead to expectations of
  supporting compressed firmware files with them only working at initrd
  stage and not at runtime.

  [Other Info]
  Original bug report

  Some facts:
   - The linux kernel has supported loading xz compressed firmware since 5.3
   - The size of /lib/firmware in impish is ~650Mb (and growing)
   - The compressed size of firmware could be ~230Mb

  It would be nice to install compressed firmware to save space.

  Here are the plans from the Fedora project:
  https://fedoraproject.org/wiki/Changes/CompressKernelFirmware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1942260/+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 1942260] Re: compress firmware in /lib/firmware

[Adrien Nader]

Have you tried environment variables?


From the xz manpage:

ENVIRONMENT
   xz parses space-separated lists of options from the  environment  vari‐
   ables XZ_DEFAULTS and XZ_OPT, in this order, before parsing the options
   from the command line.  Note that only options are parsed from the  en‐
   vironment  variables; all non-options are silently ignored.  Parsing is
   done with getopt_long(3) which is used also for the command line  argu‐
   ments.

   XZ_DEFAULTS
  User-specific or system-wide default options.  Typically this is
  set in a shell initialization script to enable xz's memory usage
  limiter  by default.  Excluding shell initialization scripts and
  similar special cases, scripts must never set  or  unset  XZ_DE‐
  FAULTS.

   XZ_OPT
  This is for passing options to xz when it is not possible to set
  the options directly on the xz command line.  This is  the  case
  when xz is run by a script or tool, for example, GNU tar(1):

 XZ_OPT=-2v tar caf foo.tar.xz foo

  Scripts  may use XZ_OPT, for example, to set script-specific de‐
  fault compression options.  It is  still  recommended  to  allow
  users to override XZ_OPT if that is reasonable.  For example, in
  sh(1) scripts one may use something like this:

 XZ_OPT=${XZ_OPT-"-7e"}
 export XZ_OPT


From the zstd manpage:

   Environment Variables
   Employing environment variables to set parameters has security implica‐
   tions.   Therefore,   this   avenue   is  intentionally  limited.  Only
   ZSTD_CLEVEL and ZSTD_NBTHREADS are currently supported.  They  set  the
   compression  level and number of threads to use during compression, re‐
   spectively.

   ZSTD_CLEVEL can be used to set the level between 1 and 19 (the "normal"
   range).  If the value of ZSTD_CLEVEL is not a valid integer, it will be
   ignored with a warning message. ZSTD_CLEVEL just replaces  the  default
   compression level (3).

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

Title:
  compress firmware in /lib/firmware

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-firmware-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  -- initramfs-tools

  [Impact]

   * linux supports xz compressed linux-firmware which saves disk space.
  In focal, initramfs-tools only knows how to included uncompressed
  firmware files (even when kernel supports loading compressed ones).
  Newer releases of linux-firmware may use compressed firmware files
  only, in such cases it would be nice for focal's initramfs-tools to
  support compressed firmware files in case of partial or incomplete
  upgrades (i.e. linux-firmware force installed or upgraded, without
  newer initramfs-tools). The proposed changes to initramfs-tools are
  backwards and forwards compatible, they prefer to include uncompressed
  firmware files; and if missing, include compressed firmware files in
  their uncompressed form. Thus maintaining compatibility with any
  kernels, irrespective of compressed/uncompressed firmware inputs.

  [Test Plan]

   * Compress all files shipped by linux-firmware with xz

   * Rebuild initrd

   * Check that all the same firmware files are still included in the
  initramfs, in their uncompressed form as before

  [Where problems could occur]

   * This SRU is precautionary to prevent accidental installation of
  compressed linux-firmware from generating incorrect initramfs. It
  should be noted that whilst initramfs-tools would create a compatible
  initramfs with any kernels, pre-v5.3 kernels do not support xz
  compressed firmware files at runtime. Mixing this new initramfs with
  compressed firmwares and pre 5.3 kernels may lead to expectations of
  supporting compressed firmware files with them only working at initrd
  stage and not at runtime.

  [Other Info]
  Original bug report

  Some facts:
   - The linux kernel has supported loading xz compressed firmware since 5.3
   - The size of /lib/firmware in impish is ~650Mb (and growing)
   - The compressed size of firmware could be ~230Mb

  It would be nice to install compressed firmware to save space.

  Here are the plans from the Fedora project:
  https://fedoraproject.org/wiki/Changes/CompressKernelFirmware

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


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

[Kernel-packages] [Bug 1990621] Re: [SRU] PXE Boot contains wrong suggested link to ISO for live file system

[Łukasz Zemczak]

Hello James, or anyone else affected,

Accepted casper into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/casper/1.470.3 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  To properly test it you
will need to obtain and boot a daily build of a Live CD for jammy.  Your
feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: casper (Ubuntu Jammy)
   Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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

Title:
  [SRU] PXE Boot contains wrong suggested link to ISO for live file
  system

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

Bug description:
  [ Impact ]

   * What are the effects of the bug on users?
     casper's intercative netmount fails to download the latest
     Ubuntu LTS ISOs after the release of the first point release
     (e.g. 22.04.1)

   * What is the justification for backporting the fix to the
     There are at least 2 bug reports about this problem
     (LP: #1990621, #1948884) and this fix will improve the
     user experience with a low probaility of side effects.

   * How does the upload fix the bug?

     - The patch adds a '-latest' to the download URLs (see more
   details here: 
https://git.launchpad.net/casper/diff/scripts/casper?id=5075686ba44c942e58c71d2c99076fe72fe64022).
     - Additionaly Łukasz Zemczak (sil2100) created symlinks that
   (as the name of the urls imply) always points to the latest
   Ubuntu ISO for a given version.

  [ Test Plan ]

   * How to reproduce the bug?

     - Just run the failling parts of the casper script on a
   22.04.1 <= x < 22.10 machine:

   # would normally be set by initramfs-tools
   $ DPKG_ARCH=amd64

   # sets UBUNTU_CODENAME=jammy and VERSION_ID="22.04"
   $ source /etc/os-release

   # see 
https://git.launchpad.net/casper/tree/scripts/casper?id=eb5ef85cb33fba28f9ae6e8da6194aaa521d5a49#n388
   $ 
server_url=https://releases.ubuntu.com/$UBUNTU_CODENAME/ubuntu-$VERSION_ID-live-server-$DPKG_ARCH.iso

   # see 
https://git.launchpad.net/casper/tree/scripts/casper?id=eb5ef85cb33fba28f9ae6e8da6194aaa521d5a49#n267
   $ wget "${server_url}" -O /dev/null

   # You should observe an ERROR 404: Not Found.

   * Test that the new links work:
     - Test Script: 
https://gist.github.com/dviererbe/0255733d25a27c9a3ddc0bfc9535c243
     - New -latest URLs
   - 
https://releases.ubuntu.com/jammy/ubuntu-22.04-latest-live-server-amd64.iso
   - https://releases.ubuntu.com/jammy/ubuntu-22.04-latest-desktop-amd64.iso
   - 
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-arm64.iso
   - 
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-ppc64el.iso
   - 
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-s390x.iso

   * Łukasz Zemczak (sil2100) tested that casper can handle
     HTTP 301 redirects. (See 
https://code.launchpad.net/~dviererbe/casper/+git/casper/+merge/446497/comments/1193559)

  [ Where problems could occur ]

   * The Ubuntu Release Team could forget or the automation
     could stop working to update the -latest links, but this
     would, in the worst case, result in a not more worse
     situation than the current bug.

  [ Other Info ]

   * Nick Rosbrook (enr0n) pointed out in comment #3 that the
     script allows the user to provide their own url.
     This should only be considered a temporary workaround as
     a user has to be aware of this bug and has to aquire a
     URL by themself. Copy & pasting URLs from the web is
     potentialy error prone and unsafe.

   * As far as I am aware, there was a discussion between
     Łukasz Zemczak (sil2100), Brian Murray (brian-murray) and
     Steve 

[Kernel-packages] [Bug 2027804] Re: Fix GUI hang in login menu on Intel GPU

[AaronMa]

Updated to 6.1.0-1018-oem, the GUI works fine.

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

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

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

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

Title:
  Fix GUI hang in login menu on Intel GPU

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  Intel GPU hang on 6.1 stable kernel in login menu after boot.

  [Fix]
  Add missing DC_OFF power domain for GPU.

  [Test]
  Tested on Intel RPL iGPU and DG2 GPU.

  [Where problems could occur]
  Low risk, the fix is in 6.2-rc1,
  the issue is only reproduced on oem-6.1 kernel,
  not reproduced on jammy kernel.
  So SRU for oem-6.1 only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2027804/+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 2028849] [NEW] package nvidia-dkms-418-server (not installed) failed to install/upgrade: le sous-processus paquet nvidia-dkms-418-server script post-installation installé a renv

[RENAUD]

Public bug reported:

i have a trouble with my mouse since an update
the mouse is freezing
i try to find the bug

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-dkms-418-server (not installed)
Uname: Linux 6.4.6-060406-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Thu Jul 27 11:49:37 2023
ErrorMessage: le sous-processus paquet nvidia-dkms-418-server script 
post-installation installé a renvoyé un état de sortie d'erreur 10
InstallationDate: Installed on 2023-05-01 (86 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.9
SourcePackage: nvidia-graphics-drivers-418-server
Title: package nvidia-dkms-418-server (not installed) failed to 
install/upgrade: le sous-processus paquet nvidia-dkms-418-server script 
post-installation installé a renvoyé un état de sortie d'erreur 10
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package jammy

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

Title:
  package nvidia-dkms-418-server (not installed) failed to
  install/upgrade: le sous-processus paquet nvidia-dkms-418-server
  script post-installation installé a renvoyé un état de sortie d'erreur
  10

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  New

Bug description:
  i have a trouble with my mouse since an update
  the mouse is freezing
  i try to find the bug

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: nvidia-dkms-418-server (not installed)
  Uname: Linux 6.4.6-060406-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jul 27 11:49:37 2023
  ErrorMessage: le sous-processus paquet nvidia-dkms-418-server script 
post-installation installé a renvoyé un état de sortie d'erreur 10
  InstallationDate: Installed on 2023-05-01 (86 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.9
  SourcePackage: nvidia-graphics-drivers-418-server
  Title: package nvidia-dkms-418-server (not installed) failed to 
install/upgrade: le sous-processus paquet nvidia-dkms-418-server script 
post-installation installé a renvoyé un état de sortie d'erreur 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/2028849/+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 2028848] [NEW] Regression: amdgpu mirror mode broken in -1018

[Timo Aaltonen]

Public bug reported:

[Impact]

OEM-6.1 1018 picks up this patch which was accidentally introduced even
though reverted upstream.

- drm/amd/display: edp do not add non-edid timings

It's already reverted in 6.5 and being reverted in 6.1.42, can you
please revert in advance in Ubuntu's kernel so we don't have the
regression for a whole Canonical kernel cycle?

It will break mirror mode for all external monitors.

Here is the discussion on the revert.
https://lore.kernel.org/stable/2023072548-basics-estranged-5e99@gregkh/

[Test case]

Check mirror mode with the commit reverted.

[Where things could go wrong]

This is an upstream revert removing a broken commit, so it should not
cause unrelated issues.

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

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

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

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

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

Title:
  Regression: amdgpu mirror mode broken in -1018

Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  New

Bug description:
  [Impact]

  OEM-6.1 1018 picks up this patch which was accidentally introduced
  even though reverted upstream.

  - drm/amd/display: edp do not add non-edid timings

  It's already reverted in 6.5 and being reverted in 6.1.42, can you
  please revert in advance in Ubuntu's kernel so we don't have the
  regression for a whole Canonical kernel cycle?

  It will break mirror mode for all external monitors.

  Here is the discussion on the revert.
  https://lore.kernel.org/stable/2023072548-basics-estranged-5e99@gregkh/

  [Test case]

  Check mirror mode with the commit reverted.

  [Where things could go wrong]

  This is an upstream revert removing a broken commit, so it should not
  cause unrelated issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2028848/+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 1876687] Re: func_traceonoff_triggers.tc from ubuntu_kselftests_ftrace flaky (Tracing file is still changing)

[Po-Hsu Lin]

** Description changed:

  Issue found on Focal 5.4.0-29.33 with node amaura (passed on rizzo,
  rizzo failed with other failures)
  
  utils:0116| Running './ftracetest -vvv 
test.d/ftrace/func_traceonoff_triggers.tc'
  utils:0153| [stdout] === Ftrace unit tests ===
  utils:0153| [stderr] + initialize_ftrace
  utils:0153| [stderr] + disable_tracing
  utils:0153| [stderr] + echo 0
  utils:0153| [stderr] + reset_tracer
  utils:0153| [stderr] + echo nop
  utils:0153| [stderr] + reset_trigger
  utils:0153| [stderr] + [ -d events/synthetic ]
- ...
+ (long output skipped)
+ utils:0153| [stderr] + read line
+ (long output skipped)
+ utils:0153| [stderr] + read line
+ (long output skipped)
+ utils:0153| [stderr] + reset_events_filter
+ utils:0153| [stderr] + read line
+ (long output skipped)
+ utils:0153| [stderr] + reset_ftrace_filter
+ utils:0153| [stderr] + [ ! -f set_ftrace_filter ]
+ utils:0153| [stderr] + echo
+ utils:0153| [stderr] + grep -v ^# set_ftrace_filter
+ utils:0153| [stderr] + read t
+ utils:0153| [stderr] + disable_events
+ utils:0153| [stderr] + echo 0
+ utils:0153| [stderr] + [ -f set_event_pid ]
+ utils:0153| [stderr] + echo
+ utils:0153| [stderr] + [ -f set_ftrace_pid ]
+ utils:0153| [stdout] [1] ftrace - test for function traceon/off triggers
+ utils:0153| [stderr] + echo
+ utils:0153| [stderr] + [ -f set_ftrace_notrace ]
+ utils:0153| [stderr] + echo
+ utils:0153| [stderr] + [ -f set_graph_function ]
+ utils:0153| [stderr] + tee set_graph_function set_graph_notrace
+ utils:0153| [stderr] + echo
+ utils:0153| [stderr] + [ -f stack_trace_filter ]
+ utils:0153| [stderr] + echo
+ utils:0153| [stderr] + [ -f kprobe_events ]
+ utils:0153| [stderr] + echo
+ utils:0153| [stderr] + [ -f uprobe_events ]
+ utils:0153| [stderr] + echo
+ utils:0153| [stderr] + [ -f synthetic_events ]
+ utils:0153| [stderr] + echo
+ utils:0153| [stderr] + [ -f snapshot ]
+ utils:0153| [stderr] + echo 0
+ utils:0153| [stderr] + clear_trace
+ utils:0153| [stdout] Testing function probes with enabling disabling tracing:
+ utils:0153| [stdout] ** DISABLE TRACING
+ utils:0153| [stderr] + echo
+ utils:0153| [stderr] + enable_tracing
+ utils:0153| [stderr] + echo 1
+ utils:0153| [stderr] + . 
/home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/ftrace/func_traceonoff_triggers.tc
+ utils:0153| [stderr] + [ ! -f set_ftrace_filter ]
+ utils:0153| [stderr] + SLEEP_TIME=.1
+ utils:0153| [stderr] + echo Testing function probes with enabling disabling 
tracing:
+ utils:0153| [stderr] + echo ** DISABLE TRACING
+ utils:0153| [stderr] + disable_tracing
+ utils:0153| [stderr] + echo 0
+ utils:0153| [stderr] + clear_trace
+ utils:0153| [stderr] + echo
+ utils:0153| [stderr] + cnt_trace
+ utils:0153| [stderr] + + grep -v ^# trace
+ utils:0153| [stderr] wc -l
+ utils:0153| [stdout] ** ENABLE EVENTS
+ utils:0153| [stderr] + cnt=0
+ utils:0153| [stderr] + [ 0 -ne 0 ]
+ utils:0153| [stderr] + echo ** ENABLE EVENTS
+ utils:0153| [stderr] + echo 1
+ utils:0153| [stdout] ** ENABLE TRACING
+ utils:0153| [stderr] + echo ** ENABLE TRACING
+ utils:0153| [stderr] + enable_tracing
+ utils:0153| [stderr] + echo 1
+ utils:0153| [stderr] + cnt_trace
+ utils:0153| [stderr] + wc -l
+ utils:0153| [stderr] + grep -v ^# trace
+ utils:0153| [stderr] + cnt=4077
+ utils:0153| [stderr] + [ 4077 -eq 0 ]
+ utils:0153| [stderr] + func=schedule
+ utils:0153| [stderr] + available_file=available_filter_functions
+ utils:0153| [stderr] + [ -d ../../instances -a -f 
../../available_filter_functions ]
+ utils:0153| [stderr] + grep ^\.schedule$ available_filter_functions
+ utils:0153| [stderr] + wc -l
+ utils:0153| [stdout] ** SET TRACEOFF
+ utils:0153| [stderr] + x=0
+ utils:0153| [stderr] + [ 0 -eq 1 ]
+ utils:0153| [stderr] + echo ** SET TRACEOFF
+ utils:0153| [stderr] + echo schedule:traceoff
+ utils:0153| [stderr] + [ -d ../../instances ]
+ utils:0153| [stderr] + + wc -l
+ utils:0153| [stderr] grep schedule set_ftrace_filter
+ utils:0153| [stderr] + cnt=1
+ utils:0153| [stderr] + [ 1 -ne 1 ]
+ utils:0153| [stderr] + cnt_trace
+ utils:0153| [stderr] + wc -l
+ utils:0153| [stderr] + grep -v ^# trace
+ utils:0153| [stderr] + cnt=21814
+ utils:0153| [stderr] + sleep .1
+ utils:0153| [stderr] + cnt_trace
+ utils:0153| [stderr] + grep+ wc -v ^# trace
+ utils:0153| [stderr]  -l
+ utils:0153| [stderr] + cnt2=21814
+ utils:0153| [stderr] + [ 21814 -ne 21814 ]
+ utils:0153| [stderr] + cat tracing_on
+ utils:0153| [stderr] + on=0
+ utils:0153| [stderr] + [ 0 != 0 ]
+ utils:0153| [stderr] + md5sum trace
+ utils:0153| [stderr] + csum1=c6e4ee60fb108d69d9bbfe7e1db1063e  trace
+ utils:0153| [stderr] + sleep .1
+ utils:0153| [stderr] + md5sum trace
+ utils:0153| [stderr] + csum2=e4031c9f7b2a802822472087feacd82f  trace
+ utils:0153| [stderr] + [ c6e4ee60fb108d69d9bbfe7e1db1063e  trace != 
e4031c9f7b2a802822472087feacd82f  trace ]
+ utils:0153| [stderr] + fail Tracing file is still changing
+ utils:0153| [stderr] + echo Tracing file 

[Kernel-packages] [Bug 2028165] Re: nvidia-dkms-* FTBS with linux 6.5

[Paolo Pisati]

450-server Linux 6.5 fix.

** Also affects: nvidia-graphics-drivers-450-server (Ubuntu)
   Importance: Undecided
   Status: New

** Patch added: "nvidia-graphics-drivers-450-server_450.248.02-0ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450-server/+bug/2028165/+attachment/5688839/+files/nvidia-graphics-drivers-450-server_450.248.02-0ubuntu2.debdiff

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

Title:
  nvidia-dkms-* FTBS with linux 6.5

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  In Progress
Status in nvidia-graphics-drivers-450-server source package in Mantic:
  New
Status in nvidia-graphics-drivers-470 source package in Mantic:
  In Progress
Status in nvidia-graphics-drivers-470-server source package in Mantic:
  In Progress
Status in nvidia-graphics-drivers-525 source package in Mantic:
  In Progress
Status in nvidia-graphics-drivers-525-server source package in Mantic:
  New

Bug description:
  [Impact]

  ...
  In file included from 
/var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21,
   from 
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function 
‘NV_GET_USER_PAGES_REMOTE’:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing 
argument 1 of ‘get_user_pages_remote’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
    164 |return get_user_pages_remote(tsk, mm, start, nr_pages, 
flags,
    | ^~~
    | |
    | struct task_struct *
  ...

  
  [Fix]

  Apply the attached fix.

  [How to test]

  Install (and build) the patched packet.

  [Regression potential]

  The fix is composed of two patches:

  1) the first patch simply garbage collect a reference to a function
  that was never used but that had the API changed in Linux 6.5 - so,
  it's a trivial change.

  2) the second patch actually reimplement part of the vma scanning that was 
removed in __get_user_pages_locked() in upstream commit 
b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas
  array from internal GUP functions" - here is where most likely any regression 
could be found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+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 2028844] Re: package linux-headers-6.2.0-26-generic 6.2.0-26.26 failed to install/upgrade: installed linux-headers-6.2.0-26-generic package post-installation script subprocess r

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-headers-6.2.0-26-generic 6.2.0-26.26 failed to
  install/upgrade: installed linux-headers-6.2.0-26-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  This error occured during upgrading the ubuntu distribution from current 
22.04 to 23.04
  I don't know what other information I need to provide here, but everything 
seemed smooth till this error occured and I ama thinking this kernel failure 
might gonna be an issue after complition of the upgrade and after the initial 
restart.

  installed linux-image-6.2.0-26-generic package post-installation
  script subprocess returned error exit status 1

  $ cat /proc/version_signature > version.log
  output: Ubuntu 5.15.0-76.83-generic 5.15.99
  $ sudo lspci -vnvn > lspci-vnvn.log
  output: has been attached, Was too long for here

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-26-generic 6.2.0-26.26
  ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99
  Uname: Linux 5.15.0-76-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  subhashish   6049 F pulseaudio
   /dev/snd/controlC0:  subhashish   6049 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Thu Jul 27 14:48:47 2023
  ErrorMessage: installed linux-headers-6.2.0-26-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2021-07-09 (747 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 82K2
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-76-generic 
root=UUID=0af4adb7-9098-4ed9-bf6f-c38b1f885d13 ro splash acpi_backlight=vendor 
amdgpu.backlight=0 vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux
  Title: package linux-headers-6.2.0-26-generic 6.2.0-26.26 failed to 
install/upgrade: installed linux-headers-6.2.0-26-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-07-27 (0 days ago)
  dmi.bios.date: 02/23/2022
  dmi.bios.release: 1.32
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H3CN32WW(V2.02)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76485 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Gaming 3 15ACH6
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrH3CN32WW(V2.02):bd02/23/2022:br1.32:efr1.32:svnLENOVO:pn82K2:pvrIdeaPadGaming315ACH6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76485WIN:cvnLENOVO:ct10:cvrIdeaPadGaming315ACH6:skuLENOVO_MT_82K2_BU_idea_FM_IdeaPadGaming315ACH6:
  dmi.product.family: IdeaPad Gaming 3 15ACH6
  dmi.product.name: 82K2
  dmi.product.sku: LENOVO_MT_82K2_BU_idea_FM_IdeaPad Gaming 3 15ACH6
  dmi.product.version: IdeaPad Gaming 3 15ACH6
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028844/+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 2028844] [NEW] package linux-headers-6.2.0-26-generic 6.2.0-26.26 failed to install/upgrade: installed linux-headers-6.2.0-26-generic package post-installation script subprocess

[Subhashish Mishra]

Public bug reported:

This error occured during upgrading the ubuntu distribution from current 22.04 
to 23.04
I don't know what other information I need to provide here, but everything 
seemed smooth till this error occured and I ama thinking this kernel failure 
might gonna be an issue after complition of the upgrade and after the initial 
restart.

installed linux-image-6.2.0-26-generic package post-installation script
subprocess returned error exit status 1

$ cat /proc/version_signature > version.log
output: Ubuntu 5.15.0-76.83-generic 5.15.99
$ sudo lspci -vnvn > lspci-vnvn.log
output: has been attached, Was too long for here

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-headers-6.2.0-26-generic 6.2.0-26.26
ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99
Uname: Linux 5.15.0-76-generic x86_64
NonfreeKernelModules: wl nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  subhashish   6049 F pulseaudio
 /dev/snd/controlC0:  subhashish   6049 F pulseaudio
CasperMD5CheckResult: unknown
Date: Thu Jul 27 14:48:47 2023
ErrorMessage: installed linux-headers-6.2.0-26-generic package 
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2021-07-09 (747 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: LENOVO 82K2
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-76-generic 
root=UUID=0af4adb7-9098-4ed9-bf6f-c38b1f885d13 ro splash acpi_backlight=vendor 
amdgpu.backlight=0 vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: /usr/bin/python3.11, Python 3.11.2, python-is-python3, 3.11.1-3
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc 2.06-2ubuntu16
SourcePackage: linux
Title: package linux-headers-6.2.0-26-generic 6.2.0-26.26 failed to 
install/upgrade: installed linux-headers-6.2.0-26-generic package 
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to lunar on 2023-07-27 (0 days ago)
dmi.bios.date: 02/23/2022
dmi.bios.release: 1.32
dmi.bios.vendor: LENOVO
dmi.bios.version: H3CN32WW(V2.02)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76485 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad Gaming 3 15ACH6
dmi.ec.firmware.release: 1.32
dmi.modalias: 
dmi:bvnLENOVO:bvrH3CN32WW(V2.02):bd02/23/2022:br1.32:efr1.32:svnLENOVO:pn82K2:pvrIdeaPadGaming315ACH6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76485WIN:cvnLENOVO:ct10:cvrIdeaPadGaming315ACH6:skuLENOVO_MT_82K2_BU_idea_FM_IdeaPadGaming315ACH6:
dmi.product.family: IdeaPad Gaming 3 15ACH6
dmi.product.name: 82K2
dmi.product.sku: LENOVO_MT_82K2_BU_idea_FM_IdeaPad Gaming 3 15ACH6
dmi.product.version: IdeaPad Gaming 3 15ACH6
dmi.sys.vendor: LENOVO
modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

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


** Tags: amd64 apport-package lunar

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

Title:
  package linux-headers-6.2.0-26-generic 6.2.0-26.26 failed to
  install/upgrade: installed linux-headers-6.2.0-26-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  This error occured during upgrading the ubuntu distribution from current 
22.04 to 23.04
  I don't know what other information I need to provide here, but everything 
seemed smooth till this error occured and I ama thinking this kernel failure 
might gonna be an issue after complition of the upgrade and after the initial 
restart.

  installed linux-image-6.2.0-26-generic package post-installation
  script subprocess returned error exit status 1

  $ cat /proc/version_signature > version.log
  output: Ubuntu 5.15.0-76.83-generic 5.15.99
  $ sudo lspci -vnvn > lspci-vnvn.log
  output: has been attached, Was too long for here

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-26-generic 6.2.0-26.26
  ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99
  Uname: Linux 5.15.0-76-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  subhashish   6049 F pulseaudio
   /dev/snd/controlC0:  subhashish   6049 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Thu Jul 27 14:48:47 2023
  ErrorMessage: installed 

[Kernel-packages] [Bug 1876687] Re: func_traceonoff_triggers.tc from ubuntu_kselftests_ftrace flaky (Tracing file is still changing)

[Po-Hsu Lin]

** Description changed:

  Issue found on Focal 5.4.0-29.33 with node amaura (passed on rizzo,
  rizzo failed with other failures)
  
- # [27] ftrace - test for function traceon/off triggers [FAIL]
+ utils:0116| Running './ftracetest -vvv 
test.d/ftrace/func_traceonoff_triggers.tc'
+ utils:0153| [stdout] === Ftrace unit tests ===
+ utils:0153| [stderr] + initialize_ftrace
+ utils:0153| [stderr] + disable_tracing
+ utils:0153| [stderr] + echo 0
+ utils:0153| [stderr] + reset_tracer
+ utils:0153| [stderr] + echo nop
+ utils:0153| [stderr] + reset_trigger
+ utils:0153| [stderr] + [ -d events/synthetic ]
+ ...
+ utils:0153| [stderr] + reset_ftrace_filter
+ utils:0153| [stderr] + [ ! -f set_ftrace_filter ]
+ utils:0153| [stderr] + echo
+ utils:0153| [stderr] + read t
+ utils:0153| [stderr] + grep -v ^# set_ftrace_filter
+ utils:0153| [stderr] + disable_events
+ utils:0153| [stderr] + echo 0
+ utils:0153| [stderr] + [ -f set_event_pid ]
+ utils:0153| [stderr] + echo
+ utils:0153| [stderr] + [ -f set_ftrace_pid ]
+ utils:0153| [stderr] + echo
+ utils:0153| [stderr] + [ -f set_ftrace_notrace ]
+ utils:0153| [stderr] + echo
+ utils:0153| [stderr] + [ -f set_graph_function ]
+ utils:0153| [stderr] + [ -f stack_trace_filter ]
+ utils:0153| [stderr] + [ -f kprobe_events ]
+ utils:0153| [stderr] + [ -f uprobe_events ]
+ utils:0153| [stderr] + [ -f synthetic_events ]
+ utils:0153| [stderr] + [ -f snapshot ]
+ utils:0153| [stderr] + echo 0
+ utils:0153| [stderr] + clear_trace
+ utils:0153| [stdout] [2] (instance)  ftrace - test for function traceon/off 
triggersTesting function probes with enabling disabling tracing:
+ utils:0153| [stdout] ** DISABLE TRACING
+ utils:0153| [stderr] + echo
+ utils:0153| [stderr] + enable_tracing
+ utils:0153| [stderr] + echo 1
+ utils:0153| [stderr] + . 
/home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/ftrace/func_traceonoff_triggers.tc
+ utils:0153| [stderr] + [ ! -f set_ftrace_filter ]
+ utils:0153| [stderr] + SLEEP_TIME=.1
+ utils:0153| [stderr] + echo Testing function probes with enabling disabling 
tracing:
+ utils:0153| [stderr] + echo ** DISABLE TRACING
+ utils:0153| [stderr] + disable_tracing
+ utils:0153| [stderr] + echo 0
+ utils:0153| [stderr] + clear_trace
+ utils:0153| [stderr] + echo
+ utils:0153| [stderr] + cnt_trace
+ utils:0153| [stderr] + wc -l
+ utils:0153| [stderr] + grep -v ^# trace
+ utils:0153| [stdout] ** ENABLE EVENTS
+ utils:0153| [stdout] ** ENABLE TRACING
+ utils:0153| [stderr] + cnt=0
+ utils:0153| [stderr] + [ 0 -ne 0 ]
+ utils:0153| [stderr] + echo ** ENABLE EVENTS
+ utils:0153| [stderr] + echo 1
+ utils:0153| [stderr] + echo ** ENABLE TRACING
+ utils:0153| [stderr] + enable_tracing
+ utils:0153| [stderr] + echo 1
+ utils:0153| [stderr] + cnt_trace
+ utils:0153| [stderr] + wc -l
+ utils:0153| [stderr] + grep -v ^# trace
+ utils:0153| [stderr] + cnt=6780
+ utils:0153| [stderr] + [ 6780 -eq 0 ]
+ utils:0153| [stderr] + func=schedule
+ utils:0153| [stderr] + available_file=available_filter_functions
+ utils:0153| [stderr] + [ -d ../../instances -a -f 
../../available_filter_functions ]
+ utils:0153| [stderr] + available_file=../../available_filter_functions
+ utils:0153| [stderr] + grep ^\.schedule$ available_filter_functions
+ utils:0153| [stderr] + wc -l
+ utils:0153| [stderr] grep: available_filter_functions: No such file or 
directory
+ utils:0153| [stderr] + x=0
+ utils:0153| [stderr] + [ 0 -eq 1 ]
+ utils:0153| [stderr] + echo ** SET TRACEOFF
+ utils:0153| [stderr] + echo schedule:traceoff
+ utils:0153| [stdout] ** SET TRACEOFF
+ utils:0153| [stderr] + [ -d ../../instances ]
+ utils:0153| [stderr] + cat set_ftrace_filter
+ utils:0153| [stderr] + cur= all functions enabled 
+ utils:0153| [stderr] schedule:traceoff:unlimited
+ utils:0153| [stderr] + cat ../../set_ftrace_filter
+ utils:0153| [stderr] + top= all functions enabled 
+ utils:0153| [stderr] schedule:traceoff:unlimited
+ utils:0153| [stderr] + [  all functions enabled 
+ utils:0153| [stderr] schedule:traceoff:unlimited =  all functions enabled 

+ utils:0153| [stderr] schedule:traceoff:unlimited ]
+ utils:0153| [stderr] + echo This kernel is too old to support per instance 
filter
+ utils:0153| [stdout] This kernel is too old to support per instance filter
+ utils:0153| [stderr] + reset_ftrace_filter
+ utils:0153| [stderr] + [ ! -f set_ftrace_filter ]
+ utils:0153| [stderr] + echo
+ utils:0153| [stderr] + grep -v+  ^#read t
+ utils:0153| [stderr]  set_ftrace_filter
+ utils:0153| [stderr] + echo schedule:traceoff:unlimited
+ utils:0153| [stderr] + cut -d: -f2
+ utils:0153| [stderr] + tr=traceoff
+ utils:0153| [stderr] + [ traceoff =  ]
+ utils:0153| [stderr] + grep -q schedule:traceoff:unlimited set_ftrace_filter
+ utils:0153| [stderr] + echo schedule:traceoff:unlimited
+ utils:0153| [stderr] + cut -d: -f1
+ utils:0153| [stderr] + cut -d  -f1
+ utils:0153| [stderr] + name=schedule
+ utils:0153| [stderr] + [ 

[Kernel-packages] [Bug 2028190] Re: kernel panic when using conntrack tcp pedit

[Bartlomiej Zolnierkiewicz]

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

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

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


** Tags added: verification-needed-jammy

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

Title:
  kernel panic when using conntrack tcp pedit

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

Bug description:
  * Explain the bug(s)

  when setting up conntrack offload with tcp pedit (test-ct-tcp-
  pedit.sh), encounter kernel panic.

  * brief explanation of fixes

  In tc_setup_flow_action, need to properly assign action.
  Which fixes previous commit ("UBUNTU: SAUCE: net/sched: Provide act to 
offload action")

  * Kernel log

  [  226.156222] Unable to handle kernel access to user memory outside uaccess 
routines at
  [  226.177783] Mem abort info:
  [  226.183408]   ESR = 0x9604
  [  226.190953]   EC = 0x25: DABT (current EL), IL = 32 bits
  [  226.201641]   SET = 0, FnV = 0
  [  226.207786]   EA = 0, S1PTW = 0
  [  226.214095]   FSC = 0x04: level 0 translation fault
  [  226.223906] Data abort info:
  [  226.229695]   ISV = 0, ISS = 0x0004
  [  226.237410]   CM = 0, WnR = 0
  [  226.243372] user pgtable: 4k pages, 48-bit VAs, pgdp=000123f25000
  [  226.256328] [0090] pgd=, p4d=
  [  226.269984] Internal error: Oops: 9604 [#1] SMP
  [  226.279779] Modules linked in: act_pedit act_ct nf_flow_table iptable_raw 
xt_CT xt_tcpudp bpfilter xt_comment xt_mark
  [  226.279938]  async_raid6_recov async_memcpy async_pq async_xor async_tx 
xor xor_neon raid6_pq raid1 raid0 multipath
  [  226.544260] CPU: 2 PID: 4293 Comm: handler3 Tainted: G
  [  226.565581] Hardware name: https://www.mellanox.com BlueField 
SoC/BlueField SoC, BIOS 4.2.0.12795 Jun 30 2023
  [  226.585497] pstate: a045 (NzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
  [  226.599481] pc : tcf_action_update_stats+0x8/0xc4
  [  226.608933] lr : mlx5e_tc_act_stats_fill_stats+0xf8/0x19c [mlx5_core]
  [  226.622089] sp : 8e073130
  [  226.628735] x29: 8e073130 x28: 0008 x27: 
0020
  [  226.643067] x26: ffe0 x25: 5913c62dfe71 x24: 
5913c62dfe00
  [  226.657398] x23:  x22:  x21: 
5913c62dfe70
  [  226.671730] x20: 5913c2fc3b00 x19: 5913f0058000 x18: 
0014
  [  226.686059] x17: b96d1a87 x16: c6320acb93e0 x15: 

  [  226.700390] x14: 0001 x13:  x12: 
0002
  [  226.714720] x11: 7f7f7f7f7f7f7f7f x10:  x9 : 
c631ce0b66ac
  [  226.729052] x8 : 8e073130 x7 :  x6 : 
000d
  [  226.743384] x5 : 0c62 x4 : 0001 x3 : 

  [  226.757715] x2 :  x1 :  x0 : 

  [  226.772047] Call trace:
  [  226.776947]  tcf_action_update_stats+0x8/0xc4
  [  226.785695]  mlx5e_tc_act_stats_fill_stats_flow+0x78/0xc0 [mlx5_core]
  [  226.798833]  mlx5e_stats_flower+0x394/0x3c0 [mlx5_core]
  [  226.809502]  mlx5e_rep_setup_tc_cls_flower+0x8c/0xa0 [mlx5_core]
  [  226.821732]  mlx5e_rep_setup_tc_cb+0x74/0xb0 [mlx5_core]
  [  226.832549]  tc_setup_cb_call+0xa4/0x160
  [  226.840426]  fl_hw_update_stats+0x98/0x164 [cls_flower]
  [  226.850927]  fl_dump.part.0+0x224/0x260 [cls_flower]
  [  226.860891]  fl_dump+0x20/0x34 [cls_flower]
  [  226.869284]  tcf_fill_node+0x164/0x244
  [  226.876803]  tfilter_notify+0xc0/0x140
  [  226.884323]  tc_new_tfilter+0x454/0x8bc
  [  226.892018]  rtnetlink_rcv_msg+0x2e8/0x3cc
  [  226.900245]  netlink_rcv_skb+0x64/0x130
  [  226.907942]  rtnetlink_rcv+0x20/0x30
  [  226.915110]  netlink_unicast+0x2ec/0x360
  [  226.922977]  netlink_sendmsg+0x278/0x490
  [  226.930846]  sock_sendmsg+0x5c/0x6c
  [  226.937845]  sys_sendmsg+0x290/0x2d4
  [  226.945712]  ___sys_sendmsg+0x84/0xd0
  [  226.953059]  __sys_sendmsg+0x70/0xd0
  [  226.960229]  __arm64_sys_sendmsg+0x2c/0x40
  [  226.968447]  invoke_syscall+0x78/0x100
  [  226.975974]  el0_svc_common.constprop.0+0x54/0x184
  [  226.985587]  do_el0_svc+0x30/0xac
  [  226.992231]  el0_svc+0x48/0x160
  [  226.998528]  el0t_64_sync_handler+0xa4/0x130
  [  227.007094]  el0t_64_sync+0x1a4/0x1a8
  [  227.01] 

[Kernel-packages] [Bug 2028197] Re: rshim console truncates dmesg output due to tmfifo issue

[Bartlomiej Zolnierkiewicz]

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

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

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


** Tags added: verification-needed-jammy

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

Title:
  rshim console truncates dmesg output due to tmfifo issue

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  New
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  mlxbf_tmfifo driver does not always schedule work for VIRTIO CONSOLE
  nottification. The result is with rshim console, the dmesg output
  would be cut off or simply cat a big text file to stdout.

  [Fix]

  * Make sure TM_TX_LWM_IRQ bit is set when there is a notification of
  virtio console event.

  [Test Case]

  * Compare the output of dmesg from rshim console and ssh session. Make sure 
both are the same.
  * Issue is reproduced w/o fix and compare the same dmesg output from the same 
as above.

  [Regression Potential]

  The changes affect only virtio console event handling only and been
  tested fully.

  [Others]
  This issue is the same on focal and Jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2028197/+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 2028309] Re: mlxbf-bootctl: Fix kernel panic due to buffer overflow

[Bartlomiej Zolnierkiewicz]

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

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

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


** Tags added: verification-needed-jammy

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

Title:
  mlxbf-bootctl: Fix kernel panic due to buffer overflow

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

Bug description:
  SRU Justification:

  [Impact]

  Running the following LTP (linux-test-project) script, causes
  a kernel panic and a reboot of the DPU:
  ltp/testcases/bin/read_all -d /sys -q -r 10

  The above test reads all directory and files under /sys.
  Reading the sysfs entry "large_icm" causes the kernel panic
  due to a garbage value returned via i2c read. That garbage
  value causes a buffer overflow in sprintf.

  
  [Fix]

  * Replace sprintf with snprintf. And also add missing lock and
  increase the buffer size to PAGE_SIZE.

  [Test Case]

  * Run from linux:
  ltp/testcases/bin/read_all -d /sys -q -r 10

  [Regression Potential]

  no known regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2028309/+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 2028800] Re: Kubuntu 23.04 boots with 6.2.0-24-generic but not 6.2.0-25-generic or 6.2.0-26-generic

[Stefan Bader]

At an initial glance this might not be hanging but not showing anything.
Comparing the two logs the GPU driver (amdgpu) does not seem to get
loaded or start. Also some messages related to the IOMMU (Amd-Vi) are
missing.

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

Title:
  Kubuntu 23.04 boots with 6.2.0-24-generic but not 6.2.0-25-generic or
  6.2.0-26-generic

Status in linux package in Ubuntu:
  New

Bug description:
  I can run Kubuntu 23.04 with kernel 6.2.0-24-generic but not
  6.2.0-25-generic or 6.2.0-26-generic. I have installed the latest AMD
  microcode, but that did not help. I am attaching the journalctl report
  for 6.2.0-24-generic that boots fully and the journalctl report for
  6.2.0-26-generic that does not boot fully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028800/+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 1942260] Re: compress firmware in /lib/firmware

[Dimitri John Ledkov]

** Changed in: linux-firmware (Ubuntu)
Milestone: None => ubuntu-23.10-beta

** Changed in: linux-firmware-raspi2 (Ubuntu)
Milestone: None => ubuntu-23.10

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

Title:
  compress firmware in /lib/firmware

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-firmware-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  -- initramfs-tools

  [Impact]

   * linux supports xz compressed linux-firmware which saves disk space.
  In focal, initramfs-tools only knows how to included uncompressed
  firmware files (even when kernel supports loading compressed ones).
  Newer releases of linux-firmware may use compressed firmware files
  only, in such cases it would be nice for focal's initramfs-tools to
  support compressed firmware files in case of partial or incomplete
  upgrades (i.e. linux-firmware force installed or upgraded, without
  newer initramfs-tools). The proposed changes to initramfs-tools are
  backwards and forwards compatible, they prefer to include uncompressed
  firmware files; and if missing, include compressed firmware files in
  their uncompressed form. Thus maintaining compatibility with any
  kernels, irrespective of compressed/uncompressed firmware inputs.

  [Test Plan]

   * Compress all files shipped by linux-firmware with xz

   * Rebuild initrd

   * Check that all the same firmware files are still included in the
  initramfs, in their uncompressed form as before

  [Where problems could occur]

   * This SRU is precautionary to prevent accidental installation of
  compressed linux-firmware from generating incorrect initramfs. It
  should be noted that whilst initramfs-tools would create a compatible
  initramfs with any kernels, pre-v5.3 kernels do not support xz
  compressed firmware files at runtime. Mixing this new initramfs with
  compressed firmwares and pre 5.3 kernels may lead to expectations of
  supporting compressed firmware files with them only working at initrd
  stage and not at runtime.

  [Other Info]
  Original bug report

  Some facts:
   - The linux kernel has supported loading xz compressed firmware since 5.3
   - The size of /lib/firmware in impish is ~650Mb (and growing)
   - The compressed size of firmware could be ~230Mb

  It would be nice to install compressed firmware to save space.

  Here are the plans from the Fedora project:
  https://fedoraproject.org/wiki/Changes/CompressKernelFirmware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1942260/+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 1876687] Re: func_traceonoff_triggers.tc from ubuntu_kselftests_ftrace flaky

[Po-Hsu Lin]

The actual test case is test.d/ftrace/func_traceonoff_triggers.tc
I will modify the content and title accordingly.

** Summary changed:

- function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on 
B/F
+ func_traceonoff_triggers.tc from ubuntu_kselftests_ftrace flaky

** Summary changed:

- func_traceonoff_triggers.tc from ubuntu_kselftests_ftrace flaky
+ func_traceonoff_triggers.tc from ubuntu_kselftests_ftrace flaky (Tracing file 
is still changing)

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

Title:
  func_traceonoff_triggers.tc from ubuntu_kselftests_ftrace flaky
  (Tracing file is still changing)

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue found on Focal 5.4.0-29.33 with node amaura (passed on rizzo,
  rizzo failed with other failures)

  # [27] ftrace - test for function traceon/off triggers [FAIL]

  Need to retest on amaura to check if this is just a glitch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1876687/+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 2028568] Re: Ship kernel modules Zstd compressed

[Dimitri John Ledkov]

This will be available in the next kernel builds, likely as part of
landing v6.5 kernel into mantic.

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

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

Title:
  Ship kernel modules Zstd compressed

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  To reduce the size of the initramfs and also to speed up the boot (by
  only decompressing the modules that are needed), please compress the
  kernel modules. From size and speed perspective, either use zstd or
  xz. I suggest to go with zstd -19.

  This change is independent of the initramfs-tools version. Old
  initramfs-tools versions will decompress the kernel modules before
  putting them in the initramfs. New initramfs-tools versions will put
  the compressed kernel modules into an uncompressed cpio archive (see
  bug #2028567).

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028568/+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 2028830] Re: [mpt3sas, UBSAN] ]linux 6.5-rc won't boot

[koba]

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => koba (kobako)

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

Title:
  [mpt3sas, UBSAN] ]linux 6.5-rc won't boot

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Ubuntu release:

  sune@jekaterina:~/src/deb$ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04
  sune@jekaterina:~/src/deb$ 

  Package:

  linux-image-
  unsigned-6.5.0-060500rc1-generic_6.5.0-060500rc1.202307232333_amd64.deb
  from https://kernel.ubuntu.com/~kernel-ppa/mainline (rc2 and rc3 also
  affected)

  Expectation: System boots normally

  Actual results: See below

  On the request of Koba Ko on the kernel-t...@lists.ubuntu.com mailing
  list, I hereby submit the following:

  Do note that two "types" are mentioned, and that I am willing the
  assist in testing, as, obviously, I have a system with a controller
  covered by the mpt3sas driver.

  This is output from attempted boot of 6.5-rc3 from kernel-ppa, but it
  is similar to rcs 1 and 2:

  UBSAN: array-index-out-of-bounds in 
/home/kerne1/COD/linux/drivers/scsi/npt3sas/mpt3sas_scsih.c:4667:12
  index 1 is out of range for type ’MPI12_EVENT_SAS_TOPO_PHY_ENTRY [1]'

  UBSAN: array-index—out-of-bounds in 
/home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih-c:4023:12
  index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]'

  UBSAN: array-index—out-of-bounds in 
/home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6810:36
  index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]'

  UBSAN: array-index—out—of-bounds in 
/home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6598:38
  index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]'

  UBSAN: array-index—out—of-bounds in 
/home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6602:36
  index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]'

  UBSAN: array-index—out—of—bounds in 
/home/kernel/COD/linux-drivers/scsi/mpt3sas/mpt3sas_scsih.c:6619:7
  index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]'

  UBSAN: array-index—out—of—bounds in 
/home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c::21
  index 1 is out of range for type ’MPI2_SAS_IO_UNIT0_PHY_DATA [1]'

  UBSAN: array-index—out—of—bounds in 
/home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7649:32
  index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]'

  UBSAN: array-index-out-of—bounds in 
/home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7651:23
  index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]'

  UBSAN: array-index-out-of-bounds in 
/home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7655:12
  index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]'

  Timed out for waiting the udey queue being empty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028830/+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 2027773] Re: UBSAN: shift-out-of-bounds in amd_sfh

[Andy Chi]

Enable -proposed on LOX14-PV-SKU6 and installed 6.1.0-1018.18, the error
is gone.

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027773/+attachment/5688775/+files/dmesg.txt

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

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

Title:
  UBSAN: shift-out-of-bounds in amd_sfh

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

Bug description:
  [SRU Justification]

  [Impact]

  UBSAN: shift-out-of-bounds in 
drivers/hid/amd-sfh-hid/sfh1_1/amd_sfh_desc.c:149:50
  [ 7.928631] shift exponent 103 is too large for 64-bit type 'long unsigned 
int'
  [ 9.877309] Workqueue: events amd_sfh_work_buffer \[amd_sfh]
  [ 9.877327] Call Trace:
  [ 9.877331] \
  [ 9.877335] dump_stack_lvl+0x49/0x63
  [ 9.877346] dump_stack+0x10/0x16
  [ 9.877348] ubsan_epilogue+0x9/0x36
  [ 9.877357] __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef
  [ 9.877363] ? _raw_spin_lock+0x17/0x50
  [ 9.877369] ? raw_spin_rq_lock_nested+0x2e/0xa0
  [ 9.877378] ? psi_group_change+0x1e2/0x4a0
  [ 9.877385] float_to_int.cold+0x18/0xc8 \[amd_sfh]
  [ 9.877394] ? get_feature_rep+0xb0/0xb0 \[amd_sfh]
  [ 9.877402] get_input_rep+0x219/0x2f0 \[amd_sfh]
  [ 9.877409] ? up+0x37/0x70
  [ 9.877414] ? hid_input_report+0x104/0x170 \[hid]
  [ 9.877428] amd_sfh_work_buffer+0x94/0x150 \[amd_sfh]
  [ 9.877436] process_one_work+0x21f/0x3f0
  [ 9.877443] worker_thread+0x50/0x3e0
  [ 9.877446] ? process_one_work+0x3f0/0x3f0
  [ 9.877449] kthread+0xfd/0x130
  [ 9.877452] ? kthread_complete_and_exit+0x20/0x20
  [ 9.877454] ret_from_fork+0x22/0x30
  [ 9.877463] \

  [Fix]

  Fixes in:
  * commit c1685a862a4b ("HID: amd_sfh: Rename the float32 variable")
  * commit 878543661764 ("HID: amd_sfh: Fix for shift-out-of-bounds")

  [Test Case]

  The affected platform should no longer has such error dumped in kernel dmesg 
at
  boot.

  [Where problems could occur]

  This renamed a variable and corrected the way shift offset is calculated. No
  known side effect.

  [Other Info]

  The affects kernel >= v6.0 and < v6.5, so Unstable/Mantis/Lunar/OEM-6.1 are
  nominated for fix.

  == original bug report ==

  UBSAN: shift-out-of-bounds in 
drivers/hid/amd-sfh-hid/sfh1_1/amd_sfh_desc.c:149:50
  [ 7.928631] shift exponent 103 is too large for 64-bit type 'long unsigned 
int'
  [ 9.877309] Workqueue: events amd_sfh_work_buffer [amd_sfh]
  [ 9.877327] Call Trace:
  [ 9.877331] 
  [ 9.877335] dump_stack_lvl+0x49/0x63
  [ 9.877346] dump_stack+0x10/0x16
  [ 9.877348] ubsan_epilogue+0x9/0x36
  [ 9.877357] __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef
  [ 9.877363] ? _raw_spin_lock+0x17/0x50
  [ 9.877369] ? raw_spin_rq_lock_nested+0x2e/0xa0
  [ 9.877378] ? psi_group_change+0x1e2/0x4a0
  [ 9.877385] float_to_int.cold+0x18/0xc8 [amd_sfh]
  [ 9.877394] ? get_feature_rep+0xb0/0xb0 [amd_sfh]
  [ 9.877402] get_input_rep+0x219/0x2f0 [amd_sfh]
  [ 9.877409] ? up+0x37/0x70
  [ 9.877414] ? hid_input_report+0x104/0x170 [hid]
  [ 9.877428] amd_sfh_work_buffer+0x94/0x150 [amd_sfh]
  [ 9.877436] process_one_work+0x21f/0x3f0
  [ 9.877443] worker_thread+0x50/0x3e0
  [ 9.877446] ? process_one_work+0x3f0/0x3f0
  [ 9.877449] kthread+0xfd/0x130
  [ 9.877452] ? kthread_complete_and_exit+0x20/0x20
  [ 9.877454] ret_from_fork+0x22/0x30
  [ 9.877463] 

  Fixes in:
  
https://github.com/torvalds/linux/commit/c1685a862a4bea863537f06abaa37a123aef493c
  
https://github.com/torvalds/linux/commit/87854366176403438d01f368b09de3ec2234e0f5

  This affects kernel >= v6.0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2027773/+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 1239459] Re: 1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few seconds

[utils world]

download digital audio workstation software
https://utils-world.com/fl-studio-21-crack/

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

Title:
  1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few
  seconds

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  With the new 3.11.0-12-generic kernel, wifi has problems to connect with many 
errors like these:
  Oct 13 23:50:03 ubuntotto kernel: [ 1186.580726] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:50:03 ubuntotto kernel: [ 1186.740659] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:50:04 ubuntotto kernel: [ 1186.900544] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:50:04 ubuntotto kernel: [ 1187.060571] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:50:04 ubuntotto kernel: [ 1187.096576] ieee80211 phy0: 
rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0
  Oct 13 23:50:05 ubuntotto kernel: [ 1188.280106] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:50:05 ubuntotto kernel: [ 1188.440128] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:51:06 ubuntotto kernel: [ 1249.560697] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:51:06 ubuntotto kernel: [ 1249.720644] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  Oct 13 23:51:07 ubuntotto kernel: [ 1249.880590] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
  Oct 13 23:51:07 ubuntotto kernel: [ 1250.040543] ieee80211 phy0: 
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-12-generic 3.11.0-12.19
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrea 1791 F pulseaudio
  Date: Sun Oct 13 23:45:04 2013
  HibernationDevice: RESUME=UUID=297ef090-5420-41f6-8439-f1254f3e9e15
  InstallationDate: Installed on 2013-10-12 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: ASUSTeK COMPUTER INC. X200CA
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=088f2a7d-b78f-4bdd-a184-754b70a3184a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-12-generic N/A
   linux-backports-modules-3.11.0-12-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-10-13 (0 days ago)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200CA.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX200CA.208:bd09/18/2013:svnASUSTeKCOMPUTERINC.:pnX200CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X200CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1239459/+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 2023446] Re: Excessive Power drain in sleep mode on XPS 9315

[Nick]

Since I switched it back to AHCI mode in the BIOS, it has really
improved. In RAID mode, the drain is very noticable. I'll be interested
to know how you get on.

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

Title:
  Excessive Power drain in sleep mode on XPS 9315

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a new Dell XPS 9315, with Ubuntu 22.04 installed (from vanilla
  image, downloaded from the Ubuntu site). The machine was sold with an
  OEM 20.04 image which I am no longer using.

  From a full charge, I close the lid and the machine enters sleep. Over
  the course of 8Hrs, the battery drops from 100% to 80%.

  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04

  Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17

  See attached log
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  noutram2273 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-06-08 (1 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: Dell Inc. XPS 9315
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-43-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-43-generic N/A
   linux-backports-modules-5.19.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.13
  Tags:  jammy
  Uname: Linux 5.19.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 04/12/2023
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 02GGG1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd04/12/2023:br1.11:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn02GGG1:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:
  dmi.product.family: XPS
  dmi.product.name: XPS 9315
  dmi.product.sku: 0B14
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023446/+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 2027773] Re: UBSAN: shift-out-of-bounds in amd_sfh

[Andy Chi]

** Tags added: originate-from-2026812 stella

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

Title:
  UBSAN: shift-out-of-bounds in amd_sfh

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

Bug description:
  [SRU Justification]

  [Impact]

  UBSAN: shift-out-of-bounds in 
drivers/hid/amd-sfh-hid/sfh1_1/amd_sfh_desc.c:149:50
  [ 7.928631] shift exponent 103 is too large for 64-bit type 'long unsigned 
int'
  [ 9.877309] Workqueue: events amd_sfh_work_buffer \[amd_sfh]
  [ 9.877327] Call Trace:
  [ 9.877331] \
  [ 9.877335] dump_stack_lvl+0x49/0x63
  [ 9.877346] dump_stack+0x10/0x16
  [ 9.877348] ubsan_epilogue+0x9/0x36
  [ 9.877357] __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef
  [ 9.877363] ? _raw_spin_lock+0x17/0x50
  [ 9.877369] ? raw_spin_rq_lock_nested+0x2e/0xa0
  [ 9.877378] ? psi_group_change+0x1e2/0x4a0
  [ 9.877385] float_to_int.cold+0x18/0xc8 \[amd_sfh]
  [ 9.877394] ? get_feature_rep+0xb0/0xb0 \[amd_sfh]
  [ 9.877402] get_input_rep+0x219/0x2f0 \[amd_sfh]
  [ 9.877409] ? up+0x37/0x70
  [ 9.877414] ? hid_input_report+0x104/0x170 \[hid]
  [ 9.877428] amd_sfh_work_buffer+0x94/0x150 \[amd_sfh]
  [ 9.877436] process_one_work+0x21f/0x3f0
  [ 9.877443] worker_thread+0x50/0x3e0
  [ 9.877446] ? process_one_work+0x3f0/0x3f0
  [ 9.877449] kthread+0xfd/0x130
  [ 9.877452] ? kthread_complete_and_exit+0x20/0x20
  [ 9.877454] ret_from_fork+0x22/0x30
  [ 9.877463] \

  [Fix]

  Fixes in:
  * commit c1685a862a4b ("HID: amd_sfh: Rename the float32 variable")
  * commit 878543661764 ("HID: amd_sfh: Fix for shift-out-of-bounds")

  [Test Case]

  The affected platform should no longer has such error dumped in kernel dmesg 
at
  boot.

  [Where problems could occur]

  This renamed a variable and corrected the way shift offset is calculated. No
  known side effect.

  [Other Info]

  The affects kernel >= v6.0 and < v6.5, so Unstable/Mantis/Lunar/OEM-6.1 are
  nominated for fix.

  == original bug report ==

  UBSAN: shift-out-of-bounds in 
drivers/hid/amd-sfh-hid/sfh1_1/amd_sfh_desc.c:149:50
  [ 7.928631] shift exponent 103 is too large for 64-bit type 'long unsigned 
int'
  [ 9.877309] Workqueue: events amd_sfh_work_buffer [amd_sfh]
  [ 9.877327] Call Trace:
  [ 9.877331] 
  [ 9.877335] dump_stack_lvl+0x49/0x63
  [ 9.877346] dump_stack+0x10/0x16
  [ 9.877348] ubsan_epilogue+0x9/0x36
  [ 9.877357] __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef
  [ 9.877363] ? _raw_spin_lock+0x17/0x50
  [ 9.877369] ? raw_spin_rq_lock_nested+0x2e/0xa0
  [ 9.877378] ? psi_group_change+0x1e2/0x4a0
  [ 9.877385] float_to_int.cold+0x18/0xc8 [amd_sfh]
  [ 9.877394] ? get_feature_rep+0xb0/0xb0 [amd_sfh]
  [ 9.877402] get_input_rep+0x219/0x2f0 [amd_sfh]
  [ 9.877409] ? up+0x37/0x70
  [ 9.877414] ? hid_input_report+0x104/0x170 [hid]
  [ 9.877428] amd_sfh_work_buffer+0x94/0x150 [amd_sfh]
  [ 9.877436] process_one_work+0x21f/0x3f0
  [ 9.877443] worker_thread+0x50/0x3e0
  [ 9.877446] ? process_one_work+0x3f0/0x3f0
  [ 9.877449] kthread+0xfd/0x130
  [ 9.877452] ? kthread_complete_and_exit+0x20/0x20
  [ 9.877454] ret_from_fork+0x22/0x30
  [ 9.877463] 

  Fixes in:
  
https://github.com/torvalds/linux/commit/c1685a862a4bea863537f06abaa37a123aef493c
  
https://github.com/torvalds/linux/commit/87854366176403438d01f368b09de3ec2234e0f5

  This affects kernel >= v6.0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2027773/+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 2028830] [NEW] [mpt3sas, UBSAN] ]linux 6.5-rc won't boot

[Fjodor]

Public bug reported:

Ubuntu release:

sune@jekaterina:~/src/deb$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.04
Release:23.04
sune@jekaterina:~/src/deb$ 

Package:

linux-image-
unsigned-6.5.0-060500rc1-generic_6.5.0-060500rc1.202307232333_amd64.deb
from https://kernel.ubuntu.com/~kernel-ppa/mainline (rc2 and rc3 also
affected)

Expectation: System boots normally

Actual results: See below

On the request of Koba Ko on the kernel-t...@lists.ubuntu.com mailing
list, I hereby submit the following:

Do note that two "types" are mentioned, and that I am willing the assist
in testing, as, obviously, I have a system with a controller covered by
the mpt3sas driver.

This is output from attempted boot of 6.5-rc3 from kernel-ppa, but it is
similar to rcs 1 and 2:

UBSAN: array-index-out-of-bounds in 
/home/kerne1/COD/linux/drivers/scsi/npt3sas/mpt3sas_scsih.c:4667:12
index 1 is out of range for type ’MPI12_EVENT_SAS_TOPO_PHY_ENTRY [1]'

UBSAN: array-index—out-of-bounds in 
/home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih-c:4023:12
index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]'

UBSAN: array-index—out-of-bounds in 
/home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6810:36
index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]'

UBSAN: array-index—out—of-bounds in 
/home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6598:38
index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]'

UBSAN: array-index—out—of-bounds in 
/home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6602:36
index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]'

UBSAN: array-index—out—of—bounds in 
/home/kernel/COD/linux-drivers/scsi/mpt3sas/mpt3sas_scsih.c:6619:7
index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]'

UBSAN: array-index—out—of—bounds in 
/home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c::21
index 1 is out of range for type ’MPI2_SAS_IO_UNIT0_PHY_DATA [1]'

UBSAN: array-index—out—of—bounds in 
/home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7649:32
index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]'

UBSAN: array-index-out-of—bounds in 
/home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7651:23
index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]'

UBSAN: array-index-out-of-bounds in 
/home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7655:12
index 1 is out of range for type ’MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]'

Timed out for waiting the udey queue being empty.

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

** Attachment added: "PXL_20230724_221218763.jpg"
   
https://bugs.launchpad.net/bugs/2028830/+attachment/5688770/+files/PXL_20230724_221218763.jpg

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

Title:
  [mpt3sas, UBSAN] ]linux 6.5-rc won't boot

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu release:

  sune@jekaterina:~/src/deb$ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04
  sune@jekaterina:~/src/deb$ 

  Package:

  linux-image-
  unsigned-6.5.0-060500rc1-generic_6.5.0-060500rc1.202307232333_amd64.deb
  from https://kernel.ubuntu.com/~kernel-ppa/mainline (rc2 and rc3 also
  affected)

  Expectation: System boots normally

  Actual results: See below

  On the request of Koba Ko on the kernel-t...@lists.ubuntu.com mailing
  list, I hereby submit the following:

  Do note that two "types" are mentioned, and that I am willing the
  assist in testing, as, obviously, I have a system with a controller
  covered by the mpt3sas driver.

  This is output from attempted boot of 6.5-rc3 from kernel-ppa, but it
  is similar to rcs 1 and 2:

  UBSAN: array-index-out-of-bounds in 
/home/kerne1/COD/linux/drivers/scsi/npt3sas/mpt3sas_scsih.c:4667:12
  index 1 is out of range for type ’MPI12_EVENT_SAS_TOPO_PHY_ENTRY [1]'

  UBSAN: array-index—out-of-bounds in 
/home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih-c:4023:12
  index 1 is out of range for type 'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]'

  UBSAN: array-index—out-of-bounds in 
/home/kernel/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6810:36
  index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]'

  UBSAN: array-index—out—of-bounds in 
/home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6598:38
  index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]'

  UBSAN: array-index—out—of-bounds in 
/home/kerne1/COD/linux/drivers/scsi/mpt3sas/mpt3sas_scsih_c:6602:36
  index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]'

  UBSAN: array-index—out—of—bounds in 
/home/kernel/COD/linux-drivers/scsi/mpt3sas/mpt3sas_scsih.c:6619:7
  index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA [1]'

  UBSAN: 

[Kernel-packages] [Bug 2028788] Re: package linux-headers-5.15.0-78 (not installed) failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-headers-5.15.0-78.list-new': Operatio

[Juerg Haefliger]

Do you have any sort of antivirus software installed?

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

Title:
  package linux-headers-5.15.0-78 (not installed) failed to
  install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-
  headers-5.15.0-78.list-new': Operation not permitted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Error encountered while trying to install a Ubuntu update.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-headers-5.15.0-78 (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  sabiddle0   3715 F pulseaudio
   /dev/snd/controlC2:  sabiddle0   3715 F pulseaudio
   /dev/snd/controlC0:  sabiddle0   3715 F pulseaudio
   /dev/snd/controlC1:  sabiddle0   3715 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Wed Jul 26 11:19:38 2023
  DuplicateSignature:
   package:linux-headers-5.15.0-78:(not installed)
   Unpacking linux-modules-5.15.0-78-generic (5.15.0-78.85) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-YdkwAy/161-linux-modules-5.15.0-78-generic_5.15.0-78.85_amd64.deb
 (--unpack):
unable to open '/lib/modules/5.15.0-78-generic/kernel/zfs/zfs.ko.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to create new file 
'/var/lib/dpkg/info/linux-headers-5.15.0-78.list-new': Operation not permitted
  HibernationDevice: RESUME=UUID=1bad61d2-b6eb-4fea-9226-5934cbee77f7
  InstallationDate: Installed on 2018-05-17 (1895 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic 
root=/dev/mapper/ubuntu--vg-root 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.
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-5.15.0-78 (not installed) failed to 
install/upgrade: unable to create new file 
'/var/lib/dpkg/info/linux-headers-5.15.0-78.list-new': Operation not permitted
  UpgradeStatus: Upgraded to jammy on 2022-08-13 (347 days ago)
  dmi.bios.date: 10/27/2016
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H270M-ITX/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/27/2016:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028788/+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 1882669] Re: Focal Azure instances crash with ftrace/test.d/00basic/basic2.tc in ubuntu_kselftests_ftrace and ubuntu_ftrace_smoke_test

[Po-Hsu Lin]

This is not affecting AWS anymore.

** Summary changed:

- Focal / Groovy aws and azure instances crash with ftracetest in 
ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test
+ Focal Azure instances crash with ftrace/test.d/00basic/basic2.tc in 
ubuntu_kselftests_ftrace and ubuntu_ftrace_smoke_test

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

** Tags added: sru-20230710

** Summary changed:

- Focal Azure instances crash with ftrace/test.d/00basic/basic2.tc in 
ubuntu_kselftests_ftrace and ubuntu_ftrace_smoke_test
+ Focal Azure AMD64 instances crash with ftrace/test.d/00basic/basic2.tc in 
ubuntu_kselftests_ftrace and ubuntu_ftrace_smoke_test

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

Title:
  Focal Azure AMD64 instances crash with ftrace/test.d/00basic/basic2.tc
  in ubuntu_kselftests_ftrace and ubuntu_ftrace_smoke_test

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Focal:
  Confirmed
Status in linux-azure source package in Groovy:
  Fix Released

Bug description:
  Issue found on 5.4.0-1013.13

  The ftrace in ubuntu_kernel_selftests failed on the second test:
  # === Ftrace unit tests ===
  # [1] Basic trace file check  [PASS]
  # [2] Basic test for tracers
  (System hang here)

  Syslog:
  kernel: [ 2234.408225] in mmio_trace_init
  kernel: [ 2234.988256] mmiotrace: Disabling non-boot CPUs...
  kernel: [ 2235.028451] mmiotrace: Error taking CPU1 down: -16
  kernel: [ 2235.052564] mmiotrace: Error taking CPU2 down: -16
  kernel: [ 2235.076593] mmiotrace: Error taking CPU3 down: -16
  kernel: [ 2235.096576] mmiotrace: Error taking CPU4 down: -16
  kernel: [ 2235.116487] mmiotrace: Error taking CPU5 down: -16
  kernel: [ 2235.132446] mmiotrace: Error taking CPU6 down: -16
  kernel: [ 2235.152488] mmiotrace: Error taking CPU7 down: -16
  kernel: [ 2235.172526] mmiotrace: Error taking CPU8 down: -16
  kernel: [ 2235.192486] mmiotrace: Error taking CPU9 down: -16
  kernel: [ 2235.212455] mmiotrace: Error taking CPU10 down: -16
  kernel: [ 2235.233020] mmiotrace: Error taking CPU11 down: -16
  kernel: [ 2235.256355] mmiotrace: Error taking CPU12 down: -16
  kernel: [ 2235.272473] mmiotrace: Error taking CPU13 down: -16
  kernel: [ 2235.292393] mmiotrace: Error taking CPU14 down: -16
  kernel: [ 2235.312426] mmiotrace: Error taking CPU15 down: -16
  kernel: [ 2235.344407] mmiotrace: Error taking CPU16 down: -16
  kernel: [ 2235.380494] mmiotrace: Error taking CPU17 down: -16
  kernel: [ 2235.400319] mmiotrace: Error taking CPU18 down: -16
  kernel: [ 2235.432631] mmiotrace: Error taking CPU19 down: -16
  kernel: [ 2235.456453] mmiotrace: Error taking CPU20 down: -16
  kernel: [ 2235.480432] mmiotrace: Error taking CPU21 down: -16
  kernel: [ 2235.496501] mmiotrace: Error taking CPU22 down: -16
  kernel: [ 2235.516442] mmiotrace: Error taking CPU23 down: -16
  kernel: [ 2235.536394] mmiotrace: Error taking CPU24 down: -16
  kernel: [ 2235.556489] mmiotrace: Error taking CPU25 down: -16
  kernel: [ 2235.573759] smpboot: CPU 26 is now offline
  kernel: [ 2235.575071] mmiotrace: CPU26 is down.
  kernel: [ 2235.585643] smpboot: CPU 27 is now offline
  kernel: [ 2235.586699] mmiotrace: CPU27 is down.
  kernel: [ 2235.609679] smpboot: CPU 28 is now offline
  kernel: [ 2235.610788] mmiotrace: CPU28 is down.
  kernel: [ 2235.633530] smpboot: CPU 29 is now offline
  kernel: [ 2235.634511] mmiotrace: CPU29 is down.
  kernel: [ 2235.653652] smpboot: CPU 30 is now offline
  kernel: [ 2235.655415] mmiotrace: CPU30 is down.
  kernel: [ 2235.678126] smpboot: CPU 31 is now offline
  kernel: [ 2235.679061] mmiotrace: CPU31 is down.
  kernel: [ 2235.679062] mmiotrace: multiple CPUs still online, may miss events.
  kernel: [ 2235.679063] mmiotrace: enabled.
  kernel: [ 2235.679128] in mmio_trace_reset
  kernel: [ 2235.696163] mmiotrace: Re-enabling CPUs...
  kernel: [ 2235.732157] mmiotrace: enabled CPU1.
  kernel: [ 2235.772207] mmiotrace: enabled CPU2.
  kernel: [ 2235.812216] mmiotrace: enabled CPU3.
  kernel: [ 2235.844220] mmiotrace: enabled CPU4.
  kernel: [ 2235.876211] mmiotrace: enabled CPU5.
  kernel: [ 2235.916159] mmiotrace: enabled CPU6.
  kernel: [ 2235.956214] mmiotrace: enabled CPU7.
  kernel: [ 2235.988145] mmiotrace: enabled CPU8.
  kernel: [ 2236.020214] mmiotrace: enabled CPU9.
  kernel: [ 2236.060207] mmiotrace: enabled CPU10.
  kernel: [ 2236.096208] mmiotrace: enabled CPU11.
  kernel: [ 2236.128205] mmiotrace: enabled CPU12.
  /usr/sbin/irqbalance: WARNING, didn't collect load info for all cpus, 
balancing is broken
  kernel: [ 2236.168204] mmiotrace: enabled CPU13.
  kernel: [ 2236.200206] mmiotrace: enabled CPU14.
  kernel: [ 2236.232207] mmiotrace: enabled CPU15.
  kernel: [ 2236.264224] mmiotrace: enabled 

[Kernel-packages] [Bug 2021525] Re: [iotg][ADL-P] gpu performance patches

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-jammy-linux-intel-iotg verification-needed-jammy

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

Title:
  [iotg][ADL-P] gpu performance patches

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

Bug description:
  This is a public version of https://bugs.launchpad.net/bugs/2018575

  ---

  Description

  When testing Ubuntu 22.04 with 5.15 iotg kernel for ADL-P platform, we
  discovered that GPU performance when running oneapi application is
  about 7X slower when compare to kernel 5.19.

  The current 5.15 iotg kernel missing the patches to boost GPU
  frequency. This affects ADL platform. Attached patches fix the issue.

  ./matrix_multiply
  Running on device: Intel(R) Graphics [0x46a6]
  Success!
  GFlops: 3.29845

  Once the kernel is patched:

  ./matrix_multiply
  Running on device: Intel(R) Graphics [0x46a6]
  Success!
  GFlops: 47.5939

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2021525/+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 2023176] Re: system hang after running stress-ng softlockup stressor while iwlwifi is connected to the station

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-jammy-linux-intel-iotg verification-needed-jammy

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

Title:
  system hang after running stress-ng softlockup stressor while iwlwifi
  is connected to the station

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

Bug description:
  [ Impact ]

   * system got hang after running stress-ng softlockup test while
  iwlwifi is connected to the station

  [ Test Plan ]

   * connect wifi (iwlwifi) to any station. (must do this)

   * execute the following command:
  $ sudo stress-ng --softlockup NUM_CPU_CORES --timeout 30

   * make sure the system still responses after testing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2023176/+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 2023325] Re: [IoTG] TSN commits tracker for bug fix

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-jammy-linux-intel-iotg verification-needed-jammy

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

Title:
  [IoTG] TSN commits tracker for bug fix

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

Bug description:
  This is a public version of  https://bugs.launchpad.net/bugs/2021543

  This is to add another patch to encounter the reverting patches effect
  in this bug list : https://bugs.launchpad.net/ubuntu-kernel-
  tests/+bug/2008085

  Hi,
  I would like to add one patch to correct the effect of these 5 reverted 
patches in this bug list : 
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2008085

  The reverted patches :
* net:veth.sh in ubuntu_kernel_selftests hang with J-intel-iotg (BUG: unable
  to handle page fault) (LP: #2008085)
  - Revert "rtnetlink: Add return value check"
  - Revert "rtnetlink: Fix unchecked return value of dev_xdp_query_md_btf()"
  - Revert "igc: Enable HW RX Timestamp for AF_XDP ZC"
  - Revert "igc: Add BTF based metadata for XDP"
  - Revert "net/core: XDP metadata BTF netlink API"

  Please find attached our new patch to replace the functionality of 5
  reverted patches . This will ensure the XDP RX HWstamp feature is
  still supported.

  NOTE to Canonical team. Please MAINTAIN the reverted state of the 5
  patches. Just add this one new patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2023325/+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 2025106] Re: No sounds output after resume from shutdown and reboot

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-jammy-linux-intel-iotg verification-needed-jammy

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

Title:
  No sounds output after resume from shutdown and reboot

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

Bug description:
  [ Impact ]

   * when unmuting mic, there is no sound output after resuming or
  rebooting. unless mute and unmute the mic again.

  [ Test Plan ]

   * boot into the system and unmute the mic by alsamixer.
   * reboot or suspend/resume
   * make sure there is sound from the speaker.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2025106/+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 2026470] Re: AX210 (8086:6024) WLAN init failed ucode -5 on 5.15 intel IoTG kernel

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-jammy-linux-intel-iotg verification-needed-jammy

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

Title:
   AX210 (8086:6024) WLAN init failed ucode -5 on 5.15 intel IoTG kernel

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

Bug description:
  [Summary]
  AX210 (8086:6024) WLAN init failed ucode -5 on 5.15 Intel IoTG kernel.

  [Steps to reproduce]
  install 5.15 Intel IoTG kernel.

  [Expected result]
  WLAN works with no problem.

  [Actual result]
  Can't detect WLAN.

  [Failure rate]
  100%

  The ucode version 66 would not be loaded successfully on this model with
  the folloing error messages:

  [5.704854] iwlwifi :01:00.0: Detected RF GF, rfid=0x10d000
  [5.706056] iwlwifi :01:00.0: Microcode SW error detected. Restarting 
0x0.
  [5.706258] iwlwifi :01:00.0: Start IWL Error Log Dump:
  [5.706265] iwlwifi :01:00.0: Transport status: 0x004A, valid: 6
  [5.706273] iwlwifi :01:00.0: Loaded firmware version: 66.f1c864e0.0 
ty-a0-gf-a0-66.ucode
  [5.706281] iwlwifi :01:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
  [5.706288] iwlwifi :01:00.0: 0x002002F0 | trm_hw_status0
  [5.706294] iwlwifi :01:00.0: 0x | trm_hw_status1
  [5.706299] iwlwifi :01:00.0: 0x004DA722 | branchlink2
  [5.706306] iwlwifi :01:00.0: 0x004D0CCE | interruptlink1
  [5.706311] iwlwifi :01:00.0: 0x004D0CCE | interruptlink2
  ...
  [6.726292] iwlwifi :01:00.0: Failed to run INIT ucode: -5

  Since ucode version 63 works well on this, and we did the api version
  limitation to the same series model (8086:6020) before, so do the trick
  as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2026470/+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 2028059] Re: remove debug kernel notice in dmesg caused by trace_printk()

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-jammy-linux-intel-iotg verification-needed-jammy

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

Title:
  remove debug kernel notice in dmesg caused by trace_printk()

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

Bug description:
  [Impact]
  a test kernel notice in dmesg would confuse users.

  [Test Plan]
  1. compile test.
  2. install the kernel and boot into it.
  3. check there is no test kernel notice in dmesg.

  [Regression potential]
  Low. remove/replace trace_printk does not affect the functions.

  [Other info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2028059/+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 2028253] Re: update apparmor and LSM stacking patch set

[Andrea Righi]

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

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

Title:
  update apparmor and LSM stacking patch set

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  [Impact]

  Provide an updated patch set for apparmor / LSM stacking with all the
  custom features that we need in the Ubuntu kernel.

  This patch set is required to provide the proper confinement with
  snaps and other Ubuntu-specific security features.

  [Fix]

  Apply the latest updated patch set from:

   https://gitlab.com/jjohansen/apparmor-kernel

  [Test case]

  Run the apparmor test case suite.

  [Regression potential]

  This patch set introduces significant non-upstream changes to the
  security layer, so we may expect generic regressions in the kernel,
  especially running applications that are stressing the security layer
  (such as systemd, snapd, lxd, etc.).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028253/+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 2023193] Re: Add firmware files for HP G10 series laptops

[Andy Chi]

Enable lunar-proposed and install linux-
firmware/20230323.gitbcdcfbcf-0ubuntu1.4 on MEDUSA-
PV2-SKU13_202305-31610. The sound output is louder.

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2023193/+attachment/5688711/+files/dmesg.txt

** Tags added: verification-done-lunar

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

Title:
  Add firmware files for HP G10 series laptops

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

Bug description:
  [ Impact ]
  HP G10 laptops need more Cirrus firmware files to enable all amplifiers to 
output audio with expected level.

  [ Test Plan ]
   * Power up the HP G10 series laptops and adjust the output volume to MAX
   * Verify speaker output volume by ears.

  [ Where problems could occur ]
   * The firmware files are released by Cirrus codec for particular HP series 
laptops.
   * The risk of regression should only impact particular models

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2023193/+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