date:20230726

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

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

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

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

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()

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

2023-07-26 Thread 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

2023-07-26 Thread 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

[Kernel-packages] [Bug 2028187] Re: Bluetooth audio locked to device disallows other devices to use Bluetooth speaker

2023-07-26 Thread Daniel van Vugt

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

  apport-collect 2028187

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

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

Title:
  Bluetooth audio locked to device disallows other devices to use
  Bluetooth speaker

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Not sure which layer is causing this. I switch bluetooth audio sources
  going to my AVR frequently throughout the day. After an update, Ubuntu
  seems to continue sending something like a keepalive to the bluetooth
  receiver despite no audio being played on the computer. This prohibits
  switching to my phone as the audio source. For example if I play a
  youtube video in Chrome, and then stop the video and then play Amazon
  Music or Spotify, the device is connected but I get no audio. If I
  close Chrome, no change. If I disconnect Ubuntu from that bluetooth
  device, audio starts coming through. No change to bluetooth receiver,
  but there was a Samsung update the other day.

  Interestingly, I disconnected Ubuntu from my BT device. Connected my
  phone, played some audio, then disconnected my phone from the BT
  device. Ubuntu then automatically connected back to that BT device and
  prohibits my phone from using it. This was clearly a change to the
  bluetooth stack that doesn't release the BT device when audio is
  stopped by the application.

  Linux gnosis 5.15.0-76-generic #83

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

2023-07-26 Thread koba

@Eli, could you provide the thermald logs? thanks
#sudo systemctl stop thermald
#sudo thermald --no-daemon --adaptive --loglevel=debug >> 
thermald_debug_202307270935

-- 
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_LIM

[Kernel-packages] [Bug 2016459] Re: NVRM: RmInitAdapter failed! , failed to copy vbios to system memory

2023-07-26 Thread ServerBoy

Hi
Just wanted to add my experience with this error message also.
If i install a fresh copy of ubuntu from the site ver 22.0.4.2 with kernel 
5.15.76 I have no issues installing my P2200 Quadro.
The ubuntu server is a vm running on my esxi server running 7.0.3N. 

The card is passed through and works fine if i do the necessary stuff
such as blacklist the nouveau drivers etc using a file entry in
modprobe.

soon as i do apt update and upgrade which updates the kernel to 5.15.78
it breaks everything and I get the same errors as above in the oringal
post.

I have even tried spinning a fresh VM and updating to the latest kernel then 
doing the GPU install an get the same problem. VM can see the card but 
NVIDIA-SMI just does not want to recognise the device.
DMESG shows the following if install Driver 470

[Wed Jul 26 23:38:47 2023] NVRM: GPU :0b:00.0: RmInitAdapter failed! 
(0x23:0x:1195)
[Wed Jul 26 23:38:47 2023] NVRM: GPU :0b:00.0: rm_init_adapter failed, 
device minor number 0
[Wed Jul 26 23:38:47 2023] NVRM: GPU :0b:00.0: RmInitAdapter failed! 
(0x23:0x:1195)
[Wed Jul 26 23:38:47 2023] NVRM: GPU :0b:00.0: rm_init_adapter failed, 
device minor number 0

If i install the latest driver 535 i get the following

[Thu Jul 27 00:01:13 2023] nvidia: loading out-of-tree module taints kernel.
[Thu Jul 27 00:01:13 2023] nvidia: module license 'NVIDIA' taints kernel.
[Thu Jul 27 00:01:13 2023] nvidia: module verification failed: signature and/or 
required key missing - tainting kernel
[Thu Jul 27 00:01:13 2023] nvidia-nvlink: Nvlink Core is being initialized, 
major device number 236
[Thu Jul 27 00:01:13 2023] nvidia :0b:00.0: enabling device ( -> 0003)
[Thu Jul 27 00:01:13 2023] nvidia :0b:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=none
[Thu Jul 27 00:01:13 2023] nvidia-modeset: Loading NVIDIA Kernel Mode Setting 
Driver for UNIX platforms  535.54.03  Tue Jun  6 22:17:39 UTC 2023
[Thu Jul 27 00:01:13 2023] [drm] [nvidia-drm] [GPU ID 0x0b00] Loading driver
[Thu Jul 27 00:01:13 2023] [drm:nv_drm_load [nvidia_drm]] *ERROR* [nvidia-drm] 
[GPU ID 0x0b00] Failed to allocate NvKmsKapiDevice
[Thu Jul 27 00:01:13 2023] [drm:nv_drm_probe_devices [nvidia_drm]] *ERROR* 
[nvidia-drm] [GPU ID 0x0b00] Failed to register device
[Thu Jul 27 00:01:15 2023] nvidia_uvm: module uses symbols from proprietary 
module nvidia, inheriting taint.
[Thu Jul 27 00:01:15 2023] nvidia-uvm: Loaded the UVM driver, major device 
number 234.
[Thu Jul 27 00:01:16 2023] audit: type=1400 audit(1690416077.083:2): 
apparmor="STATUS" operation="profile_load" profile="unconfined" 
name="nvidia_modprobe" pid=710 comm="apparmor_parser"
[Thu Jul 27 00:01:16 2023] audit: type=1400 audit(1690416077.083:3): 
apparmor="STATUS" operation="profile_load" profile="unconfined" 
name="nvidia_modprobe//kmod" pid=710 comm="apparmor_parse

Is this a bug with the kernel or am i doing something wrong here.

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

Title:
  NVRM: RmInitAdapter failed! , failed to copy vbios to system memory

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  Hi, just performed a do-release_upgrade -d to try 23.10 on my lenovo T430 
laptop with Nvidia chipset (NVIDIA NVS 5200M).
  Upgrade went smooth, but noticed my external displays where not seen. a 
checkup shows nvidia-settings doesn't show full as usual, and noticed messages 
in recarding NVRM which i had never before.

  ```
  [35057.710742] NVRM: RmInitAdapter failed! (0x30:0x:663)
  [35057.710792] NVRM: rm_init_adapter failed for device bearing minor number 0
  [35060.706390] NVRM: failed to copy vbios to system memory.
  [35060.706501] NVRM: RmInitAdapter failed! (0x30:0x:663)
  [35060.706562] NVRM: rm_init_adapter failed for device bearing minor number 0
  [35063.708929] NVRM: failed to copy vbios to system memory.
  [35063.709041] NVRM: RmInitAdapter failed! (0x30:0x:663)
  [35063.709087] NVRM: rm_init_adapter failed for device bearing minor number 0

  ```

  searching for nvidia
  ```
  2023-04-16T22:15:49.402742+02:00 T430-i7 kernel: [   14.428429] nvidia: 
loading out-of-tree module taints kernel.
  2023-04-16T22:15:49.402743+02:00 T430-i7 kernel: [   14.428443] nvidia: 
module license 'NVIDIA' taints kernel.
  2023-04-16T22:15:49.402757+02:00 T430-i7 kernel: [   14.528477] 
nvidia-nvlink: Nvlink Core is being initialized, major device number 234
  2023-04-16T22:15:49.402845+02:00 T430-i7 kernel: [   14.529212] nvidia 
:01:00.0: enabling device ( -> 0003)
  2023-04-16T22:15:49.402847+02:00 T430-i7 kernel: [   14.529674] nvidia 
:01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=none
  2023-04-16T22:15:49.402857+02:00 T430-i7 kernel: [   14.589081] 
nvidia-modeset: Loading NVIDIA Kernel Mode

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

2023-07-26 Thread Benjamin Drung

** Description changed:

  [ Impact ]
  
-  * To ensure reliable dist-upgrades in case of partial upgrades or
+  * 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
+  * Specifically it is being discussed to switch linux-firmware to ZSTD
  compressed one
  
-  * To ensure that failed dist-upgrades can still boot after-partial
+  * 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
+  * 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
+  * 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
+  * 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-
+  * 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
+ 
+  * See https://lists.ubuntu.com/archives/ubuntu-
+ devel/2023-July/042652.html and
+ https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042707.html

** Description changed:

  [ 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
+ 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

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


-- 
Mai

[Kernel-packages] [Bug 2028568] Re: Ship kernel modules Zstd compressed

2023-07-26 Thread Benjamin Drung

** Description changed:

  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
+ devel/2023-July/042652.html and
+ https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042707.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/2028568

Title:
  Ship kernel modules Zstd compressed

Status in linux package in Ubuntu:
  In Progress

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 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13

2023-07-26 Thread Chris Adams

I am also having this issue with an ASMedia controller, and I think this
is a duplicate bug https://bugs.launchpad.net/ubuntu/+source/linux-
signed-hwe/+bug/1874442

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

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in HWE Next:
  Fix Released
Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux package in Arch Linux:
  New
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Confirmed

Bug description:
  [SRU Justification]

  [Impact] 
  Dell TB16 docking station has issue to use gigabit ethernet. The ethernet
  will disconnect unless it's changed to 100Mb/s.

  
  [Test Case]
  Download some big files from the web.
  User confirms the patch fixes the issue.

  [Regression Potential] 
  This patch only effects ASMEDIA's ASM1042A.
  The regression potential is low, also limited to the specific device.

  ---

  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3.

  I get usb related kernel error messages when I initiate a high speed
  transfer (by issuing wget http://cdimage.ubuntu.com/daily-
  live/current/zesty-desktop-amd64.iso) and the download fails.

  This does not happened when the Ethernet adapter is connected to a
  100Mb/s switch, but only when connected to 1000Mb/s. It also does not
  happened with slow traffic (e.g. web page browsing). This is not a new
  bug with kernel 4.10, but has been going on since at least 4.7 and
  maybe (probably?) since forever. I'm aware of several others with this
  configuration (RTL8153 on usb3 behind thunderbolt 3) that have the
  same issue. This bug is also not specific to Ubuntu; I also get it on
  Arch Linux. I've also tested and seen this bug with several different
  models of thunderbolt 3 docks.

  Here are the relevant kernel log messages:

  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9070 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9080 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start

[Kernel-packages] [Bug 1874442] Re: ERROR Transfer event TRB DMA ptr not part of current TD

2023-07-26 Thread Chris Adams

I am having the same problem with the same hardware. On my laptop also
it works which is an Intel controller. On every AMD EPYC machine
(starship USB controller) I have tried I get libusb timeouts and nothing
in the kernel logs. Using a PCIe riser card ASMedia ASM3142 I get the
same errors as you. By turning debug on I get some more output

[20047.573189] xhci_hcd :68:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 1
[20047.573198] xhci_hcd :68:00.0: Looking for event-dma fffc30b0 
trb-start fffc4fb0 trb-end  seg-start fffc4000 
seg-end fffc4ff0
[20047.573204] xhci_hcd :68:00.0: Looking for event-dma fffc30b0 
trb-start fffc3000 trb-end fffc3070 seg-start fffc3000 
seg-end fffc3ff0
[20052.571651] xhci_hcd :68:00.0: Cancel URB d0831cdb, dev 1, ep 
0x81, starting at offset 0xfffc3040
[20052.571671] xhci_hcd :68:00.0: // Ding dong!
[20052.571790] xhci_hcd :68:00.0: Stopped on No-op or Link TRB for slot 8 
ep 2
[20052.571837] xhci_hcd :68:00.0: Removing canceled TD starting at 
0xfffc3040 (dma) in stream 0 URB d0831cdb
[20052.571850] xhci_hcd :68:00.0: xhci_giveback_invalidated_tds: Giveback 
cancelled URB d0831cdb TD
[20053.572166] xhci_hcd :68:00.0: Cancel URB 4ef649ab, dev 1, ep 
0x81, starting at offset 0xfffc3080
[20053.572188] xhci_hcd :68:00.0: // Ding dong!
[20053.572308] xhci_hcd :68:00.0: Stopped on No-op or Link TRB for slot 8 
ep 2
[20053.572355] xhci_hcd :68:00.0: Removing canceled TD starting at 
0xfffc3080 (dma) in stream 0 URB 4ef649ab
[20053.572364] xhci_hcd :68:00.0: xhci_giveback_invalidated_tds: Giveback 
cancelled URB 4ef649ab TD 

There are a number of related issues,
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750 and
https://lore.kernel.org/lkml/55b228a4.2020...@linux.intel.com/t/ amongst
others.

It seems in some instances it is solved with a patch that was made to
the 4 series kernel but it has resurfaced recently.

Did you ever resolve the issue?

Btw I am on Ubuntu 20.04, 5.15.0-76-generic kernel

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

Title:
  ERROR Transfer event TRB DMA ptr not part of current TD

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

Bug description:
  I'm developing a software that talks with a device based on Cypress
  FX3 USB3 controller. In my laptop all works well, I developed it for
  months by now. In my desktop computer it crashes the xhci module:

  Apr 23 12:39:11 phoenix kernel: [  679.386166] xhci_hcd :04:00.0: ERROR 
Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13
  Apr 23 12:39:11 phoenix kernel: [  679.386169] xhci_hcd :04:00.0: Looking 
for event-dma 3cd0f020 trb-start 3cd0f000 trb-end 
3cd0f000 seg-start 3cd0f000 seg-end 3cd0fff0
  Apr 23 12:39:11 phoenix kernel: [  679.386287] xhci_hcd :04:00.0: ERROR 
Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13
  Apr 23 12:39:11 phoenix kernel: [  679.386289] xhci_hcd :04:00.0: Looking 
for event-dma 3cd0f050 trb-start 3cd0f000 trb-end 
3cd0f000 seg-start 3cd0f000 seg-end 3cd0fff0
  Apr 23 12:39:11 phoenix kernel: [  679.386411] xhci_hcd :04:00.0: ERROR 
Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13
  Apr 23 12:39:11 phoenix kernel: [  679.386413] xhci_hcd :04:00.0: Looking 
for event-dma 3cd0f070 trb-start 3cd0f000 trb-end 
3cd0f000 seg-start 3cd0f000 seg-end 3cd0fff0

  and so on (one per libusb transfer, it seems).

  
  Sometimes it even gives a core dump:

  
  Apr 23 13:33:23 phoenix kernel: [  122.974398] swiotlb_tbl_map_single: 6 
callbacks suppressed
  Apr 23 13:33:23 phoenix kernel: [  122.974401] xhci_hcd :04:00.0: swiotlb 
buffer is full (sz: 1572864 bytes), total 32768 (slots), used 516 (slots)
  Apr 23 13:33:23 phoenix kernel: [  122.974403] xhci_hcd :04:00.0: 
overflow 0x00015420+1572864 of DMA mask  bus mask 0
  Apr 23 13:33:23 phoenix kernel: [  122.974412] WARNING: CPU: 7 PID: 3280 at 
/build/linux-hwe-3vURZB/linux-hwe-5.3.0/kernel/dma/direct.c:35 
report_addr+0x33/0x90
  Apr 23 13:33:23 phoenix kernel: [  122.974413] Modules linked in: rfcomm 
hid_logitech_hidpp bnep intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal 
intel_powerclamp nvidia_uvm(POE) coretemp nls_iso8859_1 kvm_intel 
nvidia_drm(POE) kvm 
  joydev input_leds mei_hdcp nvidia_modeset(POE) irqbypass nvidia(POE) 
snd_hda_codec_hdmi snd_hda_codec_realtek hid_logitech_dj snd_hda_codec_generic 
ledtrig_audio crct10dif_pclmul crc32_pclmul snd_hda_intel ghash_clmulni_intel 
snd_usb_aud
  io snd_intel_nhlt snd_hda_codec

[Kernel-packages] [Bug 2028808] Re: Lunar update: upstream stable patchset 2023-07-26

2023-07-26 Thread Kamal Mostafa

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    upstream stable patchset 2023-07-26
+    from git://git.kernel.org/
  
-upstream stable patchset 2023-07-26
-from git://git.kernel.org/
+ drm/fbdev-generic: prohibit potential out-of-bounds access
+ drm/mipi-dsi: Set the fwnode for mipi_dsi_device
+ ARM: 9296/1: HP Jornada 7XX: fix kernel-doc warnings
+ net: skb_partial_csum_set() fix against transport header magic value
+ net: mdio: mvusb: Fix an error handling path in mvusb_mdio_probe()
+ scsi: ufs: core: Fix I/O hang that occurs when BKOPS fails in W-LUN suspend
+ tick/broadcast: Make broadcast device replacement work correctly
+ linux/dim: Do nothing if no time delta between samples
+ net: stmmac: Initialize MAC_ONEUS_TIC_COUNTER register
+ net: Fix load-tearing on sk->sk_stamp in sock_recv_cmsgs().
+ net: phy: bcm7xx: Correct read from expansion register
+ netfilter: nf_tables: always release netdev hooks from notifier
+ netfilter: conntrack: fix possible bug_on with enable_hooks=1
+ bonding: fix send_peer_notif overflow
+ netlink: annotate accesses to nlk->cb_running
+ net: annotate sk->sk_err write from do_recvmmsg()
+ net: deal with most data-races in sk_wait_event()
+ net: add vlan_get_protocol_and_depth() helper
+ tcp: add annotations around sk->sk_shutdown accesses
+ gve: Remove the code of clearing PBA bit
+ net: mscc: ocelot: fix stat counter register values
+ net: datagram: fix data-races in datagram_poll()
+ af_unix: Fix a data race of sk->sk_receive_queue->qlen.
+ af_unix: Fix data races around sk->sk_shutdown.
+ drm/i915/guc: Don't capture Gen8 regs on Xe devices
+ drm/i915: Fix NULL ptr deref by checking new_crtc_state
+ drm/i915/dp: prevent potential div-by-zero
+ drm/i915: Expand force_probe to block probe of devices as well.
+ drm/i915: taint kernel when force probing unsupported devices
+ fbdev: arcfb: Fix error handling in arcfb_probe()
+ ext4: reflect error codes from ext4_multi_mount_protect() to its callers
+ ext4: allow to find by goal if EXT4_MB_HINT_GOAL_ONLY is set
+ ext4: allow ext4_get_group_info() to fail
+ refscale: Move shutdown from wait_event() to wait_event_idle()
+ selftests: cgroup: Add 'malloc' failures checks in test_memcontrol
+ rcu: Protect rcu_print_task_exp_stall() ->exp_tasks access
+ open: return EINVAL for O_DIRECTORY | O_CREAT
+ fs: hfsplus: remove WARN_ON() from hfsplus_cat_{read,write}_inode()
+ drm/displayid: add displayid_get_header() and check bounds better
+ drm/amd/display: populate subvp cmd info only for the top pipe
+ drm/amd/display: Correct DML calculation to align HW formula
+ platform/x86: x86-android-tablets: Add Acer Iconia One 7 B1-750 data
+ drm/amd/display: Enable HostVM based on rIOMMU active
+ drm/amd/display: Use DC_LOG_DC in the trasform pixel function
+ regmap: cache: Return error in cache sync operations for REGCACHE_NONE
+ remoteproc: imx_dsp_rproc: Add custom memory copy implementation for i.MX DSP 
Cores
+ arm64: dts: qcom: msm8996: Add missing DWC3 quirks
+ media: cx23885: Fix a null-ptr-deref bug in buffer_prepare() and 
buffer_finish()
+ media: pci: tw68: Fix null-ptr-deref bug in buf prepare and finish
+ media: pvrusb2: VIDEO_PVRUSB2 depends on DVB_CORE to use dvb_* symbols
+ ACPI: processor: Check for null return of devm_kzalloc() in fch_misc_setup()
+ drm/rockchip: dw_hdmi: cleanup drm encoder during unbind
+ arm64: dts: imx8mq-librem5: Remove dis_u3_susphy_quirk from usb_dwc3_0
+ firmware: arm_sdei: Fix sleep from invalid context BUG
+ ACPI: EC: Fix oops when removing custom query handlers
+ drm/amd/display: fixed dcn30+ underflow issue
+ remoteproc: stm32_rproc: Add mutex protection for workqueue
+ drm/tegra: Avoid potential 32-bit integer overflow
+ drm/msm/dp: Clean up handling of DP AUX interrupts
+ ACPICA: Avoid undefined behavior: applying zero offset to null pointer
+ ACPICA: ACPICA: check null return of ACPI_ALLOCATE_ZEROED in 
acpi_db_display_objects
+ arm64: dts: qcom: sdm845-polaris: Drop inexistent properties
+ irqchip/gicv3: Workaround for NVIDIA erratum T241-FABRIC-4
+ ACPI: video: Remove des

[Kernel-packages] [Bug 2028808] [NEW] Lunar update: upstream stable patchset 2023-07-26

2023-07-26 Thread Kamal Mostafa

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   upstream stable patchset 2023-07-26
   from git://git.kernel.org/

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

** Affects: linux (Ubuntu Lunar)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

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

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

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

** Changed in: linux (Ubuntu Lunar)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

Title:
  Lunar update: upstream stable patchset 2023-07-26

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Lunar:
  In Progress

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 upstream stable patchset 2023-07-26
 from git://git.kernel.org/

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

https://lists.ubuntu.com/archives/kernel-team/2023-July/141412.html

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

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

Title:
  Ship kernel modules Zstd compressed

Status in linux package in Ubuntu:
  In Progress

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

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 1990621] Re: [SRU] PXE Boot contains wrong suggested link to ISO for live file system

2023-07-26 Thread Dominik Viererbe

** Description changed:

  [ 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 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. 
+  * 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.
+  * 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?
+  * 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
+    - Just run the failling parts of the casper script on a
+  22.04.1 <= x < 22.10 machine:
  
-  # sets UBUNTU_CODENAME=jammy and VERSION_ID="22.04"
-  $ source /etc/os-release
+  # would normally be set by initramfs-tools
+  $ DPKG_ARCH=amd64
  
-  # 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
+  # sets UBUNTU_CODENAME=jammy and VERSION_ID="22.04"
+  $ source /etc/os-release
  
-  # You should observe an ERROR 404: Not Found.
+  # 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
  
-  * 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
+  # 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-desktop-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-desktop-ppc64el.iso
-  - 
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-riscv64.iso
-  - 
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-desktop-riscv64.iso
   - 
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-s390x.iso
-  - 
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-desktop-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)
-  
+  * Łukasz Zemczak (sil2100) tested that casper can handle
+    HTTP 301 redirects. (See 
https://code.launchpad.net/~

[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

2023-07-26 Thread John Hayes

This is the journlctl report of 6.2.0-24-generic that fully boots if it
helps any.

** Attachment added: "This is the journalctl report for 6.2.0-24-generic that 
fully boots"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028800/+attachment/5688607/+files/journalctl%20report%20will%20boot%206.2.24.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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] [NEW] Kubuntu 23.04 boots with 6.2.0-24-generic but not 6.2.0-25-generic or 6.2.0-26-generic

2023-07-26 Thread John Hayes

Public bug reported:

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.

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

** Attachment added: "This journalctl report is for 6.2.0-26-generic that will 
not boot"
   
https://bugs.launchpad.net/bugs/2028800/+attachment/5688606/+files/journalctl%20report%20will%20not%20boot%206.2.0-26.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 2028799] [NEW] Jammy update: v5.15.115 upstream stable release

2023-07-26 Thread Kamal Mostafa

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.15.115 upstream stable release
   from git://git.kernel.org/

power: supply: bq27xxx: expose battery data when CI=1
power: supply: bq27xxx: Move bq27xxx_battery_update() down
power: supply: bq27xxx: Ensure power_supply_changed() is called on current sign 
changes
power: supply: bq27xxx: After charger plug in/out wait 0.5s for things to 
stabilize
power: supply: core: Refactor 
power_supply_set_input_current_limit_from_supplier()
power: supply: bq24190: Call power_supply_changed() after updating input current
bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps
net/mlx5: devcom only supports 2 ports
net/mlx5e: Fix deadlock in tc route query code
net/mlx5: Devcom, serialize devcom registration
platform/x86: ISST: PUNIT device mapping with Sub-NUMA clustering
platform/x86: ISST: Remove 8 socket limit
net: phy: mscc: enable VSC8501/2 RGMII RX clock
net: dsa: introduce helpers for iterating through ports using dp
net: dsa: mt7530: rework mt753[01]_setup
net: dsa: mt7530: split-off common parts from mt7531_setup
net: dsa: mt7530: fix network connectivity with multiple CPU ports
Bonding: add arp_missed_max option
bonding: fix send_peer_notif overflow
binder: fix UAF caused by faulty buffer cleanup
irqchip/mips-gic: Get rid of the reliance on irq_cpu_online()
irqchip/mips-gic: Use raw spinlock for gic_lock
net/mlx5e: Fix SQ wake logic in ptp napi_poll context
xdp: Allow registering memory model without rxq reference
net: page_pool: use in_softirq() instead
page_pool: fix inconsistency for page_pool_ring_[un]lock()
irqchip/mips-gic: Don't touch vl_map if a local interrupt is not routable
xdp: xdp_mem_allocator can be NULL in trace_mem_connect().
bluetooth: Add cmd validity checks at the start of hci_sock_ioctl()
Revert "binder_alloc: add missing mmap_lock calls when using the VMA"
Revert "android: binder: stop saving a pointer to the VMA"
binder: add lockless binder_alloc_(set|get)_vma()
binder: fix UAF of alloc->vma in race with munmap()
ipv{4,6}/raw: fix output xfrm lookup wrt protocol
netfilter: ctnetlink: Support offloaded conntrack entry deletion
Linux 5.15.115
UBUNTU: Upstream stable to v5.15.115

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

** Affects: linux (Ubuntu Jammy)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

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

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

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

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.15.115 upstream stable release
+    from git://git.kernel.org/
  
-v5.15.115 upstream stable release
-from git://git.kernel.org/
+ power: supply: bq27xxx: expose battery data when CI=1
+ power: supply: bq27xxx: Move bq27xxx_battery_update() down
+ power: supply: bq27xxx: Ensure power_supply_changed() is called on current 
sign changes
+ power: supply: bq27xxx: After charger plug in/out wait 0.5s for things to 
stabilize
+ power: supply: core: Refactor 
power_supply_set_input_current_limit_from_supplier()
+ power: supply: bq24190: Call power_supply_changed() after updating input 
current
+ bpf: fix a memory leak in the LRU and LRU_PERCPU

[Kernel-packages] [Bug 2020524] Re: iptables physdev match broken via upstream stable patchset 2023-04-06 / v5.15.93, fixed upstream in 5.15.109

2023-07-26 Thread Birgit Edel

Fixed in:
Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Available on jammy via:
linux-image-generic-hwe-22.04-edge

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

** Description changed:

  physdev iptables match was broken in a stable update.
  
  A fix was already committed in upstream releases
  5.4.242
  5.15.109
  6.1.26
- 6.2.13 / LP: #2023929
+ 6.2.13 / LP: #2023929 / LP: #2026752
  
  == Regression details ==
  Discovered in version: 5.19.0-42.43~22.04.1
  Last known good version: 5.19.0-41.42~22.04.1
  
  How to tell? Add & use a bridge interface, add catchall filter (no -j ACTION 
needed) see if *any* bridge traffic is tracked:
  # iptables -A INPUT -m physdev --physdev-in + -m comment --comment "watch me"
  # iptables -nvL INPUT | grep watch
  
  The match behaves as if the matched packets were not bridge traffic, and
  consistently so: negation works. Security impact highly depends on rule
  design. KVM hosts, probably.
  
  bug introduced, bridge info discarded
  5.4.232 dffe83a198a6c293155f99958e51ab84442424c5 LP: #2011625
  5.15.93 89a69216f17005e28bd9a333662dcb3247dd0f56 LP: #2015511
  6.1.11 a1512f11ec02458c0986f169f29c90a92c150cc4 LP: #2012665
  6.2 2b272bb558f1d3a5aa95ed8a82253786fd1a48ba
  netfilter: br_netfilter: disable sabotage_in hook after first suppression
  
  fixed, bridge info no longer discarded
  5.4.242 36f098e1e4d1a372329c6244b220047a19e60dbd
  5.15.109 cb9b96c154a10dd4802b82281c9246eabe081026
  6.1.26 ea854a25c8327f51f7ff529b745794a985185563
  6.2.13 22134b86de9c2afe28e1f406062cd93bdcac4149
  master 94623f579ce338b5fa61b5acaa5beb8aa657fb9e
  netfilter: br_netfilter: fix recent physdev match breakage
  
  related module names: xt_physdev nft_meta_bridge br_netfilter

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

Title:
  iptables physdev match broken via upstream stable patchset 2023-04-06
  / v5.15.93, fixed upstream in 5.15.109

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  physdev iptables match was broken in a stable update.

  A fix was already committed in upstream releases
  5.4.242
  5.15.109
  6.1.26
  6.2.13 / LP: #2023929 / LP: #2026752

  == Regression details ==
  Discovered in version: 5.19.0-42.43~22.04.1
  Last known good version: 5.19.0-41.42~22.04.1

  How to tell? Add & use a bridge interface, add catchall filter (no -j ACTION 
needed) see if *any* bridge traffic is tracked:
  # iptables -A INPUT -m physdev --physdev-in + -m comment --comment "watch me"
  # iptables -nvL INPUT | grep watch

  The match behaves as if the matched packets were not bridge traffic,
  and consistently so: negation works. Security impact highly depends on
  rule design. KVM hosts, probably.

  bug introduced, bridge info discarded
  5.4.232 dffe83a198a6c293155f99958e51ab84442424c5 LP: #2011625
  5.15.93 89a69216f17005e28bd9a333662dcb3247dd0f56 LP: #2015511
  6.1.11 a1512f11ec02458c0986f169f29c90a92c150cc4 LP: #2012665
  6.2 2b272bb558f1d3a5aa95ed8a82253786fd1a48ba
  netfilter: br_netfilter: disable sabotage_in hook after first suppression

  fixed, bridge info no longer discarded
  5.4.242 36f098e1e4d1a372329c6244b220047a19e60dbd
  5.15.109 cb9b96c154a10dd4802b82281c9246eabe081026
  6.1.26 ea854a25c8327f51f7ff529b745794a985185563
  6.2.13 22134b86de9c2afe28e1f406062cd93bdcac4149
  master 94623f579ce338b5fa61b5acaa5beb8aa657fb9e
  netfilter: br_netfilter: fix recent physdev match breakage

  related module names: xt_physdev nft_meta_bridge br_netfilter

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020524/+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 1978079] Re: EFI pstore not cleared on boot

2023-07-26 Thread William Tu

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

** No longer affects: linux-bluefield (Ubuntu Impish)

** No longer affects: linux-bluefield (Ubuntu Kinetic)

** Changed in: linux-bluefield (Ubuntu)
 Assignee: (unassigned) => William Tu (wtu)

** Changed in: linux-bluefield (Ubuntu Focal)
 Assignee: (unassigned) => William Tu (wtu)

** Changed in: linux-bluefield (Ubuntu Jammy)
 Assignee: (unassigned) => William Tu (wtu)

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

Title:
  EFI pstore not cleared on boot

Status in linux-bluefield package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in linux-bluefield source package in Focal:
  New
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Impish:
  Won't Fix
Status in linux-bluefield source package in Jammy:
  New
Status in systemd source package in Jammy:
  Fix Released
Status in systemd source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  Systemd has a systemd-pstore component that scans the pstore on boot
  and if non-empty, takes all previously created dumps, transfers them
  into its journal and removes the pstore elements. This is very
  important on UEFI systems, which only have a limited amount of space
  for variables.

  In Ubuntu, the kernel is configured with CONFIG_EFI_VARS_PSTORE=m
  which means the EFI pstore support gets loaded dynamically. In all of
  my boots, this dynamic module loading happened *after* systemd tried
  to check for pstore variables. So systemd-pstore never starts and
  never clears the UEFI variable store. I see this happening in AWS on
  Graviton instances, which eventually run out of space to store the
  dumps. On real hardware, this behavior may lead to unbootable systems.

  ```
  $ systemctl status systemd-pstore
  ○ systemd-pstore.service - Platform Persistent Storage Archival
   Loaded: loaded (/lib/systemd/system/systemd-pstore.service; enabled; 
vendor preset: enabled)
   Active: inactive (dead)
    Condition: start condition failed at Thu 2022-06-09 09:11:41 UTC; 29min ago
   └─ ConditionDirectoryNotEmpty=/sys/fs/pstore was not met
     Docs: man:systemd-pstore(8)

  Jun 09 09:11:41 ip-172-31-0-61 systemd[1]: Condition check resulted in
  Platform Persistent Storage Archival being skipped.

  $ ls -la /sys/fs/pstore
  total 0
  drwxr-x--- 2 root root0 Jun  9 09:11 .
  drwxr-xr-x 8 root root0 Jun  9 09:11 ..
  -r--r--r-- 1 root root 1803 Jun  9 09:07 dmesg-efi-165476562001001
  -r--r--r-- 1 root root 1777 Jun  9 09:07 dmesg-efi-165476562002001
  -r--r--r-- 1 root root 1773 Jun  9 09:07 dmesg-efi-165476562003001
  -r--r--r-- 1 root root 1815 Jun  9 09:07 dmesg-efi-165476562004001
  -r--r--r-- 1 root root 1826 Jun  9 09:07 dmesg-efi-165476562005001
  -r--r--r-- 1 root root 1754 Jun  9 09:07 dmesg-efi-165476562006001
  -r--r--r-- 1 root root 1821 Jun  9 09:07 dmesg-efi-165476562007001
  -r--r--r-- 1 root root 1767 Jun  9 09:07 dmesg-efi-165476562008001
  -r--r--r-- 1 root root 1729 Jun  9 09:07 dmesg-efi-165476562009001
  -r--r--r-- 1 root root 1819 Jun  9 09:07 dmesg-efi-165476562010001
  -r--r--r-- 1 root root 1767 Jun  9 09:07 dmesg-efi-165476562011001
  -r--r--r-- 1 root root 1775 Jun  9 09:07 dmesg-efi-165476562012001
  -r--r--r-- 1 root root 1802 Jun  9 09:07 dmesg-efi-165476562013001
  -r--r--r-- 1 root root 1812 Jun  9 09:07 dmesg-efi-165476562014001
  -r--r--r-- 1 root root 1764 Jun  9 09:07 dmesg-efi-165476562015001
  -r--r--r-- 1 root root 1795 Jun  9 09:11 dmesg-efi-165476589801001
  -r--r--r-- 1 root root 1785 Jun  9 09:11 dmesg-efi-165476589802001
  -r--r--r-- 1 root root 1683 Jun  9 09:11 dmesg-efi-165476589803001
  -r--r--r-- 1 root root 1785 Jun  9 09:11 dmesg-efi-165476589804001
  -r--r--r-- 1 root root 1771 Jun  9 09:11 dmesg-efi-165476589805001
  -r--r--r-- 1 root root 1797 Jun  9 09:11 dmesg-efi-165476589806001
  -r--r--r-- 1 root root 1805 Jun  9 09:11 dmesg-efi-165476589807001
  -r--r--r-- 1 root root 1781 Jun  9 09:11 dmesg-efi-165476589808001
  -r--r--r-- 1 root root 1806 Jun  9 09:11 dmesg-efi-165476589809001
  -r--r--r-- 1 root root 1821 Jun  9 09:11 dmesg-efi-165476589810001
  -r--r--r-- 1 root root 1763 Jun  9 09:11 dmesg-efi-165476589811001
  -r--r--r-- 1 root root 1783 Jun  9 09:11 dmesg-efi-165476589812001
  -r--r--r-- 1 root root 1788 Jun  9 09:11 dmesg-efi-165476589813001
  -r--r--r-- 1 root root 1788 Jun  9 09:11 dmesg-efi-165476589814001
  -r--r--r-- 1 root root 1786 Jun  9 09:11 dmesg-efi-165476589815001
  ```

  This problem affects (at least) Ubuntu 20.04 and 22.04. A quick fix
  would be to configure CONFIG_EFI_VARS_PSTORE=y so that it's always
  available. A long term fix would make systemd rescan the directory
  after all module probing settled.

  [Test Plan]

  In order to be

[Kernel-packages] [Bug 2028791] [NEW] Mantic update: v6.4.6 upstream stable release

2023-07-26 Thread Andrea Righi

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v6.4.6 upstream stable release
   from git://git.kernel.org/


Linux 6.4.6
x86/cpu/amd: Add a Zenbleed fix
x86/cpu/amd: Move the errata checking functionality up

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

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


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

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

Title:
  Mantic update: v6.4.6 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Mantic:
  Confirmed

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 v6.4.6 upstream stable release
 from git://git.kernel.org/

  
  Linux 6.4.6
  x86/cpu/amd: Add a Zenbleed fix
  x86/cpu/amd: Move the errata checking functionality up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028791/+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 2028790] [NEW] Mantic update: v6.4.5 upstream stable release

2023-07-26 Thread Andrea Righi

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v6.4.5 upstream stable release
   from git://git.kernel.org/


Linux 6.4.5
net/ncsi: change from ndo_set_mac_address to dev_set_mac_address
net/ncsi: make one oem_gma function for all mfr id
drm/atomic: Fix potential use-after-free in nonblocking commits
Revert "drm/amd: Disable PSR-SU on Parade 0803 TCON"
MIPS: kvm: Fix build error with KVM_MIPS_DEBUG_COP0_COUNTERS enabled
net: dsa: ocelot: unlock on error in vsc9959_qos_port_tas_set()
scsi: qla2xxx: Fix end of loop test
scsi: qla2xxx: Remove unused nvme_ls_waitq wait queue
scsi: qla2xxx: Pointer may be dereferenced
scsi: qla2xxx: Correct the index of array
scsi: qla2xxx: Check valid rport returned by fc_bsg_to_rport()
scsi: qla2xxx: Fix potential NULL pointer dereference
scsi: qla2xxx: Fix buffer overrun
scsi: qla2xxx: Avoid fcport pointer dereference
scsi: qla2xxx: Array index may go out of bound
scsi: qla2xxx: Fix mem access after free
scsi: qla2xxx: Wait for io return on terminate rport
scsi: qla2xxx: Fix hang in task management
scsi: qla2xxx: Fix task management cmd fail due to unavailable resource
scsi: qla2xxx: Fix task management cmd failure
scsi: qla2xxx: Multi-que support for TMF
tracing/user_events: Fix struct arg size match check
tracing/probes: Fix to record 0-length data_loc in fetch_store_string*() if 
fails
Revert "tracing: Add "(fault)" name injection to kernel probes"
tracing/probes: Fix to update dynamic data counter if fetcharg uses it
tracing/probes: Fix not to count error code to total length
tracing/probes: Fix to avoid double count of the string length on the array
smb: client: Fix -Wstringop-overflow issues
selftests: mptcp: pm_nl_ctl: fix 32-bit support
selftests: mptcp: depend on SYN_COOKIES
selftests: mptcp: userspace_pm: report errors with 'remove' tests
selftests: mptcp: userspace_pm: use correct server port
selftests: mptcp: sockopt: return error if wrong mark
selftests: mptcp: connect: fail if nft supposed to work
selftests: mptcp: sockopt: use 'iptables-legacy' if available
mptcp: ensure subflow is unhashed before cleaning the backlog
mptcp: do not rely on implicit state check in mptcp_listen()
tracing: Fix null pointer dereference in tracing_err_log_open()
fprobe: Ensure running fprobe_exit_handler() finished before calling 
rethook_free()
fprobe: Release rethook after the ftrace_ops is unregistered
accel/ivpu: Clear specific interrupt status bits on C0
accel/ivpu: Fix VPU register access in irq disable
pwm: meson: fix handling of period/duty if greater than UINT_MAX
pwm: meson: modify and simplify calculation in meson_pwm_get_state
PM: QoS: Restore support for default value on frequency QoS
perf/x86: Fix lockdep warning in for_each_sibling_event() on SPR
xtensa: ISS: fix call to split_if_spec
cifs: if deferred close is disabled then close files immediately
drm/amd/pm: conditionally disable pcie lane/speed switching for SMU13
drm/amd/pm: share the code around SMU13 pcie parameters update
ftrace: Fix possible warning on checking all pages used in ftrace_process_locs()
ring-buffer: Fix deadloop issue on reading trace_pipe
net: ena: fix shift-out-of-bounds in exponential backoff
regmap-irq: Fix out-of-bounds access when allocating config buffers
perf: RISC-V: Remove PERF_HES_STOPPED flag checking in riscv_pmu_start()
samples: ftrace: Save required argument registers in sample trampolines
nvme: don't reject probe due to duplicate IDs for single-ported PCIe devices
tracing: Fix memory leak of iter->temp when reading trace_pipe
tracing/histograms: Add histograms to hist_vars if they have referenced 
variables
dm: verity-loadpin: Add NULL pointer check for 'bdev' parameter
s390/decompressor: fix misaligned symbol build error
bus: ixp4xx: fix IXP4XX_EXP_T1_MASK
Revert "8250: add support for ASIX devices with a FIFO bug"
media: uapi: Fix [GS]_ROUTING ACTIVE flag value
soundwire: qcom: fix storing port config out-of-bounds
opp: Fix use-after-free in lazy_opp_tables after probe deferral
meson saradc: fix clock divider mask length
xhci: Show ZHAOXIN xHCI root hub speed correctly
xhci: Fix TRB prefetch issue of ZHAOXIN hosts
xhci: Fix resume issue of some ZHAOXIN hosts
arm64: errata: Mitigate Ampere1 erratum AC03_CPU_38 at stage-2
nfp: clean mc addresses in application firmware when closing port
ceph: don't let check_caps skip sending responses for revoke msgs
ceph: fix blindly expanding the readahead windows
ceph: add a dedicated private data for netfs rreq
libceph: harden msgr2.1 frame segment length checks
firmware: stratix10-svc: Fix a potenti

[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

2023-07-26 Thread 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/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:
  New

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 2028788] [NEW] 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': Operat

2023-07-26 Thread Steve Biddle

Public bug reported:

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.

** Affects: linux (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 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:
  New

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 spl

[Kernel-packages] [Bug 2028534] Re: Jammy update: v6.1.40 upstream stable release

2023-07-26 Thread Mario Limonciello

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

This breaks mirror mode.  It's already reverted in 6.5 and being
reverted in 6.1.42.

Can you please revert in OEM 6.1 1018 as well?

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

Title:
  Jammy update: v6.1.40 upstream stable release

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

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 v6.1.40 upstream stable release
 from git://git.kernel.org/

  
  Linux 6.1.40
  net/ncsi: change from ndo_set_mac_address to dev_set_mac_address
  net/ncsi: make one oem_gma function for all mfr id
  drm/atomic: Fix potential use-after-free in nonblocking commits
  net/sched: sch_qfq: reintroduce lmax bound check for MTU
  swiotlb: mark swiotlb_memblock_alloc() as __init
  Revert "drm/amd: Disable PSR-SU on Parade 0803 TCON"
  MIPS: kvm: Fix build error with KVM_MIPS_DEBUG_COP0_COUNTERS enabled
  scsi: qla2xxx: Fix end of loop test
  scsi: qla2xxx: Remove unused nvme_ls_waitq wait queue
  scsi: qla2xxx: Pointer may be dereferenced
  scsi: qla2xxx: Correct the index of array
  scsi: qla2xxx: Check valid rport returned by fc_bsg_to_rport()
  scsi: qla2xxx: Fix potential NULL pointer dereference
  scsi: qla2xxx: Fix buffer overrun
  scsi: qla2xxx: Avoid fcport pointer dereference
  scsi: qla2xxx: Array index may go out of bound
  scsi: qla2xxx: Fix mem access after free
  scsi: qla2xxx: Wait for io return on terminate rport
  scsi: qla2xxx: Fix hang in task management
  scsi: qla2xxx: Fix task management cmd fail due to unavailable resource
  scsi: qla2xxx: Fix task management cmd failure
  scsi: qla2xxx: Multi-que support for TMF
  tracing/user_events: Fix struct arg size match check
  tracing/probes: Fix to update dynamic data counter if fetcharg uses it
  tracing/probes: Fix not to count error code to total length
  selftests: mptcp: pm_nl_ctl: fix 32-bit support
  selftests: mptcp: depend on SYN_COOKIES
  selftests: mptcp: userspace_pm: report errors with 'remove' tests
  selftests: mptcp: userspace_pm: use correct server port
  selftests: mptcp: sockopt: return error if wrong mark
  selftests: mptcp: connect: fail if nft supposed to work
  tracing: Fix null pointer dereference in tracing_err_log_open()
  fprobe: Ensure running fprobe_exit_handler() finished before calling 
rethook_free()
  fprobe: Release rethook after the ftrace_ops is unregistered
  pwm: meson: fix handling of period/duty if greater than UINT_MAX
  pwm: meson: modify and simplify calculation in meson_pwm_get_state
  PM: QoS: Restore support for default value on frequency QoS
  perf/x86: Fix lockdep warning in for_each_sibling_event() on SPR
  xtensa: ISS: fix call to split_if_spec
  cifs: if deferred close is disabled then close files immediately
  drm/amd/pm: conditionally disable pcie lane/speed switching for SMU13
  drm/amd/pm: share the code around SMU13 pcie parameters update
  ftrace: Fix possible warning on checking all pages used in 
ftrace_process_locs()
  ring-buffer: Fix deadloop issue on reading trace_pipe
  net: ena: fix shift-out-of-bounds in exponential backoff
  regmap-irq: Fix out-of-bounds access when allocating config buffers
  perf: RISC-V: Remove PERF_HES_STOPPED flag checking in riscv_pmu_start()
  samples: ftrace: Save required argument registers in sample trampolines
  nvme: don't reject probe due to duplicate IDs for single-ported PCIe devices
  tracing: Fix memory leak of iter->temp when reading trace_pipe
  tracing/histograms: Add histograms to hist_vars if they have referenced 
variables
  dm: verity-loadpin: Add NULL pointer check for 'bdev' parameter
  s390/decompressor: fix misaligned symbol build error
  bus: ixp4xx: fix IXP4XX_EXP_T1_MASK
  Revert "8250: add support for ASIX devices with a FIFO bug"
  soundwire: qcom: fix storing port config out-of-bounds
  opp: Fix use-after-free in lazy_opp_tables after probe deferral
  meson saradc: fix clock divider mask length
  xhci: Show ZHAOXIN xHCI root hub speed correctly
  xhci: Fix TRB prefetch issue of ZHAOXIN hosts
  xhci: Fix resume issue of some ZHAOXIN hosts
  ceph: don't let check_caps skip sending responses for revoke msgs
  ceph: fix blindly expanding the readahead windows
  ceph: add a dedicated private data for netfs

[Kernel-packages] [Bug 2024479] Re: kdump fails on big arm64 systems when offset is not specified

2023-07-26 Thread Mauricio Faria de Oliveira

The kernel changes are Fix Committed in the Azure kernel packages,
and should land slightly earlier than the Generic kernel packages.

linux-azure (5.15.0-1043.50) jammy-proposed
linux-azure-5.15 (5.15.0-1043.50~20.04.1) focal-proposed

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

Title:
  kdump fails on big arm64 systems when offset is not specified

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe-5.15 package in Ubuntu:
  Invalid
Status in kexec-tools source package in Focal:
  Fix Released
Status in linux source package in Focal:
  Won't Fix
Status in linux-hwe-5.15 source package in Focal:
  In Progress
Status in kexec-tools source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  In Progress
Status in linux-hwe-5.15 source package in Jammy:
  Invalid
Status in kexec-tools source package in Kinetic:
  Won't Fix
Status in linux source package in Kinetic:
  Won't Fix
Status in linux-hwe-5.15 source package in Kinetic:
  Invalid
Status in kexec-tools source package in Lunar:
  Fix Released
Status in kexec-tools source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  kdump fails on arm64, on machines with a lot of memory when offset is not 
specified,
  e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"

  If kdump-tools.cfg specifies the offset e.g.:
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
  it works ok.

  The reason for this is that the kernel needs to allocate memory for the 
crashkernel both
  in low and high memory.
  This is addressed in kernel 6.2.
  In addition kexec-tools needs to support more than one crash kernel region.

  [Fix]

  To address this issue the following upstream commits are needed:

  - From the kernel side:

  commit a9ae89df737756d92f0e14873339cf393f7f7eb0
  Author: Zhen Lei 
  Date: Wed Nov 16 20:10:44 2022 +0800

  arm64: kdump: Support crashkernel=X fall back to reserve region
  above DMA zones

  commit a149cf00b158e1793a8dd89ca492379c366300d2
  Author: Zhen Lei 
  Date: Wed Nov 16 20:10:43 2022 +0800

  arm64: kdump: Provide default size when crashkernel=Y,low is not
  specified

  - From kexec-tools:

  commit b5a34a20984c4ad27cc5054d9957af8130b42a50
  Author: Chen Zhou 
  Date: Mon Jan 10 18:20:08 2022 +0800

  arm64: support more than one crash kernel regions

  Affected releases:
  Jammy, Focal, Bionic

  For Bionic we won't fix it as we need to backport a lot of code and the 
regression potential is too high.
  The same applies for the Focal 5.4 kernel.
  Only the Focal 5.15 hwe kernel (from Jammy) will be fixed.

  [Test Plan]

  You need an arm64 machine (can be a VM too) with large memory e.g. 128G.
  Install linux-crashdump, configure the crash kernel size, and trigger a crash.

  1) Failing scenario (crashkernel >= 4G, without offset "@"):

  It won't work unless the offset is specified because the memory
  crashkernel cannot be allocated.

  With the patches applied it works as expected without having to
  specify the offset.

  2) Working scenario (crashkernel < 4G, e.g., 'crashkernel=1G')

  This must continue to work with the new patches (ie, no regressions),
  including patched kexec-tools on unpatched kernel (eg, 5.4 kernel on
  Focal).

  [Regression Potential]

  KERNEL 5.15 - Jammy (and Focal via the HWE kernel):

  To address this problem in the 5.15 kernel we need to pull in 7 commits (see 
[Other] section for details.
  All the commits are changing code only for arm64 architecture and only the 
code related to reserving the crashkernel.
  This means that any regression potential will affect only the arm64 
architecture and in particular the crash/kdump functionality.
  However, since the reservation of the crashkernel occurs at boot up, 
potentially things could go wrong there as well.

  kexec-tools - FOCAL:

  To fix the kexec_tools in focal we need to pull in 6 commits (see [Other 
section for details]). They all cherry pick.
  Four out of six commits touch only arm64 code. Any regression potential 
because of these commits  would regard either crashdump or kexec functionality.
  Commit cf977b1af9ec67fab adds code without altering current functionality.
  Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive 
it moves the code from vmcore-dmesg.c  to elf_info.c so it can be used by other 
features.

  kexec-tools - JAMMY, LUNAR, MANTIC:

  Commit b5a34a20984c is pulled in, it cherry-picks. It changes only
  arm64 code. It enables kexec to recognise that the reserved kernel may
  use more than one kernel region. Things could go worng when gatherinng
  a crashdump.

  [Other]

  Commits to backport

  - MANTIC:

  kernel 6.3:

[Kernel-packages] [Bug 2023952] Re: UNII-4 5.9G Band support request on 8852BE

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1018.18
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-oem-6.1 verification-needed-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/2023952

Title:
  UNII-4 5.9G Band support request on 8852BE

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

Bug description:
  [Impact]
  The platform can't connect to AP with Wi-Fi 5.9G capability and wifi function 
doesn't work properly.

  [Fix]
  Realtek has verified the 5.9G function with 8852BE WLAN on WarlockMLK2 Intel 
platform and submitted upstream.
  
https://lore.kernel.org/linux-wireless/20230508081211.38760-1-pks...@realtek.com/

  Included in v6.5-rc
  e3b77c06c886 wifi: rtw89: support U-NII-4 channels on 5GHz band
  a002f98123dd wifi: rtw89: regd: judge UNII-4 according to BIOS and chip
  e897b0bef38a wifi: rtw89: introduce realtek ACPI DSM method

  [Test]
  Verified by ODM and can connect to 5.9G AP

  [Where problems could occur]
  commit 5 added new callback functions which change the device behavior during 
suspending/resuming, not sure if this impacts old chips.
  Other commits looks normal and should not lead to regressions.

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

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1018.18
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-oem-6.1 verification-needed-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 2027773] Re: UBSAN: shift-out-of-bounds in amd_sfh

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1018.18
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-oem-6.1 verification-needed-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 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://launchpa

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

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1018.18
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-oem-6.1 verification-needed-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/2027804

Title:
  Fix GUI hang in login menu on Intel GPU

Status in HWE Next:
  In Progress
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 Committed

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 2027957] Re: Fix AMDGPU: the screen freeze with W7500

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1018.18
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-oem-6.1 verification-needed-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/2027957

Title:
  Fix AMDGPU: the screen freeze with W7500

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

Bug description:
  [impact]
  While booting into OOBE, the screen freeze [AMD W7500 only]

  [fix]
  AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled.
  Intel CPU may not support the dynamic lane/speed switching.

  Solution is,
  - Detect Intel x86 systems that don't support dynamic switching
  - Override the input caps to maximum supported for that system
  - Force all PCIe levels to use the same settings, rather than try to 
configure each level differently.

  [test cases]
  1. boot with w7500
  2. the screen doesn't freeze and can't find the error message in dmesg.
  "amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out"

  [where the issue could happen]
  low, this could lead issue when setting higher speeds than supported.

  [Misc]
  1. jammy, amdgpu isn't loaded on this platform with 5.15-73-generic.
  2. kinetic, amdgpu failed to probe the vga controller with 5.19-46-generic.
  3. Passed cbd build against Mantic&Lunar.

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

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1018.18
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-oem-6.1 verification-needed-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 1942260] Re: compress firmware in /lib/firmware

2023-07-26 Thread Benjamin Drung

Both linux-firmware patches were accepted upstream. Upstream currently
does not set a compression level and has no way to specify it.

-- 
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 1932329] Re: Support compressed kernel modules in initramfs-tools and kernel

moving linux tasks to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028568

** No longer affects: linux (Ubuntu Jammy)

** No longer affects: linux (Ubuntu)

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

Title:
  Support compressed kernel modules in initramfs-tools and kernel

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Focal:
  New
Status in initramfs-tools source package in Impish:
  Won't Fix
Status in initramfs-tools source package in Jammy:
  Fix Released

Bug description:
  --- initramfs-tools

  [Impact]

   * Initramfs-tools already supports compressed kernel modules.
  However, in focal and impish it does so inefficiently. It is always
  better to have a compressed initramfs of uncommpressed kernel modules,
  than a compressed initrd of compressed kernel modules. Thus when
  kernel module compression is turned on, it is prudent for initramfs-
  tools to pre-uncompress kernel modules when building initramfs.

  [Test Plan]

   * Compress all kernel modules with xz for a current kernel, check
  that all of them have .ko.xz extension and no .ko ones available

   * Rerun depmod

   * Update initramfs with update-initramfs -u

   * lsinitramfs contents and check that all kernel modules are present,
  and are uncompressed (.ko extension)

  [Where problems could occur]

   * This optimization for compressed kernel modules will make initramfs
  build time longer (due to decompression) whilst improving bootspeed
  (overall smaller size of the initrd).

  [Other Info]

   * Original bug report re kernel feature

  --- linux

  Symbol: MODULE_COMPRESS_ZSTD [=n]
  Type  : bool

  = Impacts to measure and observe =

  == Disk space ==

  * Inspect linux-modules-* and linux-modules-extra* deb package
  Installed-Size and Download-Size changes, i.e.

  $ apt show linux-modules-5.8.0-53-generic linux-modules-
  extra-5.8.0-53-generic  | grep -e Package: -e Size:

  Package: linux-modules-5.8.0-53-generic
  Installed-Size: 81.5 MB
  Download-Size: 15.5 MB

  Package: linux-modules-extra-5.8.0-53-generic
  Installed-Size: 215 MB
  Download-Size: 41.5 MB

  In theory, there should not be a significant change in the Download-
  size. It is desired that there is a significant reduction in
  Installed-Size. Modules take up about 300MB and normally one has upto
  three kernel version installed, resulting in about of 1GB of disk
  space that one constantly pays for.

  == Boot Speed ==

  In theory, boot speed may either improve or regress. It depends if
  disk IO is slower than decompression speed, meaning loading compressed
  modules is faster.

  Also one has to observe the changes in the initrd size. zstd(zstd)
  compression may result in slight growth, which shouldn't impact boot
  speed too much.

  = Outcomes =

  If installed size savings can be achieved without regressing bootspeed
  we should enable CONFIG_MODULE_COMPRESS_ZSTD=y by default.

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

** Summary changed:

- Ship kernel modules compressed
+ Ship kernel modules Zstd compressed

-- 
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:
  New

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

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 2024479] Re: kdump fails on big arm64 systems when offset is not specified

This bug was fixed in the package kexec-tools - 1:2.0.18-1ubuntu1.1

---
kexec-tools (1:2.0.18-1ubuntu1.1) focal; urgency=medium

  * Support more than one crash kernel regions for arm64 (LP: #2024479)
- d/p/lp2024479-0001-util_lib-Add-functionality-to-read-elf-notes.patch
- 
d/p/lp2024479-0002-arm64-Add-support-to-read-PHYS_OFFSET-from-kcore-pt_.patch
- 
d/p/lp2024479-0003-kexec-add-variant-helper-functions-for-handling-memo.patch
- 
d/p/lp2024479-0004-arm64-kexec-allocate-memory-space-avoiding-reserved-.patch
- 
d/p/lp2024479-0005-arm64-kdump-deal-with-a-lot-of-resource-entries-in-p.patch
- d/p/lp2024479-0006-arm64-support-more-than-one-crash-kernel-regions.patch

 -- Ioanna Alifieraki   Mon, 03
Jul 2023 16:29:58 +0300

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

Title:
  kdump fails on big arm64 systems when offset is not specified

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe-5.15 package in Ubuntu:
  Invalid
Status in kexec-tools source package in Focal:
  Fix Released
Status in linux source package in Focal:
  Won't Fix
Status in linux-hwe-5.15 source package in Focal:
  In Progress
Status in kexec-tools source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  In Progress
Status in linux-hwe-5.15 source package in Jammy:
  Invalid
Status in kexec-tools source package in Kinetic:
  Won't Fix
Status in linux source package in Kinetic:
  Won't Fix
Status in linux-hwe-5.15 source package in Kinetic:
  Invalid
Status in kexec-tools source package in Lunar:
  Fix Released
Status in kexec-tools source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  kdump fails on arm64, on machines with a lot of memory when offset is not 
specified,
  e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"

  If kdump-tools.cfg specifies the offset e.g.:
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
  it works ok.

  The reason for this is that the kernel needs to allocate memory for the 
crashkernel both
  in low and high memory.
  This is addressed in kernel 6.2.
  In addition kexec-tools needs to support more than one crash kernel region.

  [Fix]

  To address this issue the following upstream commits are needed:

  - From the kernel side:

  commit a9ae89df737756d92f0e14873339cf393f7f7eb0
  Author: Zhen Lei 
  Date: Wed Nov 16 20:10:44 2022 +0800

  arm64: kdump: Support crashkernel=X fall back to reserve region
  above DMA zones

  commit a149cf00b158e1793a8dd89ca492379c366300d2
  Author: Zhen Lei 
  Date: Wed Nov 16 20:10:43 2022 +0800

  arm64: kdump: Provide default size when crashkernel=Y,low is not
  specified

  - From kexec-tools:

  commit b5a34a20984c4ad27cc5054d9957af8130b42a50
  Author: Chen Zhou 
  Date: Mon Jan 10 18:20:08 2022 +0800

  arm64: support more than one crash kernel regions

  Affected releases:
  Jammy, Focal, Bionic

  For Bionic we won't fix it as we need to backport a lot of code and the 
regression potential is too high.
  The same applies for the Focal 5.4 kernel.
  Only the Focal 5.15 hwe kernel (from Jammy) will be fixed.

  [Test Plan]

  You need an arm64 machine (can be a VM too) with large memory e.g. 128G.
  Install linux-crashdump, configure the crash kernel size, and trigger a crash.

  1) Failing scenario (crashkernel >= 4G, without offset "@"):

  It won't work unless the offset is specified because the memory
  crashkernel cannot be allocated.

  With the patches applied it works as expected without having to
  specify the offset.

  2) Working scenario (crashkernel < 4G, e.g., 'crashkernel=1G')

  This must continue to work with the new patches (ie, no regressions),
  including patched kexec-tools on unpatched kernel (eg, 5.4 kernel on
  Focal).

  [Regression Potential]

  KERNEL 5.15 - Jammy (and Focal via the HWE kernel):

  To address this problem in the 5.15 kernel we need to pull in 7 commits (see 
[Other] section for details.
  All the commits are changing code only for arm64 architecture and only the 
code related to reserving the crashkernel.
  This means that any regression potential will affect only the arm64 
architecture and in particular the crash/kdump functionality.
  However, since the reservation of the crashkernel occurs at boot up, 
potentially things could go wrong there as well.

  kexec-tools - FOCAL:

  To fix the kexec_tools in focal we need to pull in 6 commits (see [Other 
section for details]). They all cherry pick.
  Four out of six commits touch only arm64 code. Any regression potential 
because of these commits  would regard either crashdump or kexec functionality.
  Commit cf977b1af9ec67fab adds code without alteri

[Kernel-packages] [Bug 2024479] Re: kdump fails on big arm64 systems when offset is not specified

This bug was fixed in the package kexec-tools - 1:2.0.22-2ubuntu3.1

---
kexec-tools (1:2.0.22-2ubuntu3.1) lunar; urgency=medium

  * Support more than one crash kernel regions for arm64 (LP: #2024479)
- d/p/lp2024479-arm64-support-more-than-one-crash-kernel-regions.patch

 -- Ioanna Alifieraki   Mon, 03
Jul 2023 15:28:52 +0300

** Changed in: kexec-tools (Ubuntu Lunar)
   Status: Fix Committed => Fix Released

** Changed in: kexec-tools (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  kdump fails on big arm64 systems when offset is not specified

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe-5.15 package in Ubuntu:
  Invalid
Status in kexec-tools source package in Focal:
  Fix Released
Status in linux source package in Focal:
  Won't Fix
Status in linux-hwe-5.15 source package in Focal:
  In Progress
Status in kexec-tools source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  In Progress
Status in linux-hwe-5.15 source package in Jammy:
  Invalid
Status in kexec-tools source package in Kinetic:
  Won't Fix
Status in linux source package in Kinetic:
  Won't Fix
Status in linux-hwe-5.15 source package in Kinetic:
  Invalid
Status in kexec-tools source package in Lunar:
  Fix Released
Status in kexec-tools source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  kdump fails on arm64, on machines with a lot of memory when offset is not 
specified,
  e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"

  If kdump-tools.cfg specifies the offset e.g.:
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
  it works ok.

  The reason for this is that the kernel needs to allocate memory for the 
crashkernel both
  in low and high memory.
  This is addressed in kernel 6.2.
  In addition kexec-tools needs to support more than one crash kernel region.

  [Fix]

  To address this issue the following upstream commits are needed:

  - From the kernel side:

  commit a9ae89df737756d92f0e14873339cf393f7f7eb0
  Author: Zhen Lei 
  Date: Wed Nov 16 20:10:44 2022 +0800

  arm64: kdump: Support crashkernel=X fall back to reserve region
  above DMA zones

  commit a149cf00b158e1793a8dd89ca492379c366300d2
  Author: Zhen Lei 
  Date: Wed Nov 16 20:10:43 2022 +0800

  arm64: kdump: Provide default size when crashkernel=Y,low is not
  specified

  - From kexec-tools:

  commit b5a34a20984c4ad27cc5054d9957af8130b42a50
  Author: Chen Zhou 
  Date: Mon Jan 10 18:20:08 2022 +0800

  arm64: support more than one crash kernel regions

  Affected releases:
  Jammy, Focal, Bionic

  For Bionic we won't fix it as we need to backport a lot of code and the 
regression potential is too high.
  The same applies for the Focal 5.4 kernel.
  Only the Focal 5.15 hwe kernel (from Jammy) will be fixed.

  [Test Plan]

  You need an arm64 machine (can be a VM too) with large memory e.g. 128G.
  Install linux-crashdump, configure the crash kernel size, and trigger a crash.

  1) Failing scenario (crashkernel >= 4G, without offset "@"):

  It won't work unless the offset is specified because the memory
  crashkernel cannot be allocated.

  With the patches applied it works as expected without having to
  specify the offset.

  2) Working scenario (crashkernel < 4G, e.g., 'crashkernel=1G')

  This must continue to work with the new patches (ie, no regressions),
  including patched kexec-tools on unpatched kernel (eg, 5.4 kernel on
  Focal).

  [Regression Potential]

  KERNEL 5.15 - Jammy (and Focal via the HWE kernel):

  To address this problem in the 5.15 kernel we need to pull in 7 commits (see 
[Other] section for details.
  All the commits are changing code only for arm64 architecture and only the 
code related to reserving the crashkernel.
  This means that any regression potential will affect only the arm64 
architecture and in particular the crash/kdump functionality.
  However, since the reservation of the crashkernel occurs at boot up, 
potentially things could go wrong there as well.

  kexec-tools - FOCAL:

  To fix the kexec_tools in focal we need to pull in 6 commits (see [Other 
section for details]). They all cherry pick.
  Four out of six commits touch only arm64 code. Any regression potential 
because of these commits  would regard either crashdump or kexec functionality.
  Commit cf977b1af9ec67fab adds code without altering current functionality.
  Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive 
it moves the code from vmcore-dmesg.c  to elf_info.c so it can be used by other 
features.

  kexec-tools - JAMMY, LUNAR, MANTIC:

  Commit

[Kernel-packages] [Bug 2024479] Re: kdump fails on big arm64 systems when offset is not specified

This bug was fixed in the package kexec-tools -
1:2.0.22-2ubuntu2.22.04.1

---
kexec-tools (1:2.0.22-2ubuntu2.22.04.1) jammy; urgency=medium

  * Support more than one crash kernel regions for arm64 (LP: #2024479)
- d/p/lp2024479-arm64-support-more-than-one-crash-kernel-regions.patch

 -- Ioanna Alifieraki   Mon, 03
Jul 2023 15:34:26 +0300

** Changed in: kexec-tools (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  kdump fails on big arm64 systems when offset is not specified

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe-5.15 package in Ubuntu:
  Invalid
Status in kexec-tools source package in Focal:
  Fix Released
Status in linux source package in Focal:
  Won't Fix
Status in linux-hwe-5.15 source package in Focal:
  In Progress
Status in kexec-tools source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  In Progress
Status in linux-hwe-5.15 source package in Jammy:
  Invalid
Status in kexec-tools source package in Kinetic:
  Won't Fix
Status in linux source package in Kinetic:
  Won't Fix
Status in linux-hwe-5.15 source package in Kinetic:
  Invalid
Status in kexec-tools source package in Lunar:
  Fix Released
Status in kexec-tools source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  kdump fails on arm64, on machines with a lot of memory when offset is not 
specified,
  e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"

  If kdump-tools.cfg specifies the offset e.g.:
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
  it works ok.

  The reason for this is that the kernel needs to allocate memory for the 
crashkernel both
  in low and high memory.
  This is addressed in kernel 6.2.
  In addition kexec-tools needs to support more than one crash kernel region.

  [Fix]

  To address this issue the following upstream commits are needed:

  - From the kernel side:

  commit a9ae89df737756d92f0e14873339cf393f7f7eb0
  Author: Zhen Lei 
  Date: Wed Nov 16 20:10:44 2022 +0800

  arm64: kdump: Support crashkernel=X fall back to reserve region
  above DMA zones

  commit a149cf00b158e1793a8dd89ca492379c366300d2
  Author: Zhen Lei 
  Date: Wed Nov 16 20:10:43 2022 +0800

  arm64: kdump: Provide default size when crashkernel=Y,low is not
  specified

  - From kexec-tools:

  commit b5a34a20984c4ad27cc5054d9957af8130b42a50
  Author: Chen Zhou 
  Date: Mon Jan 10 18:20:08 2022 +0800

  arm64: support more than one crash kernel regions

  Affected releases:
  Jammy, Focal, Bionic

  For Bionic we won't fix it as we need to backport a lot of code and the 
regression potential is too high.
  The same applies for the Focal 5.4 kernel.
  Only the Focal 5.15 hwe kernel (from Jammy) will be fixed.

  [Test Plan]

  You need an arm64 machine (can be a VM too) with large memory e.g. 128G.
  Install linux-crashdump, configure the crash kernel size, and trigger a crash.

  1) Failing scenario (crashkernel >= 4G, without offset "@"):

  It won't work unless the offset is specified because the memory
  crashkernel cannot be allocated.

  With the patches applied it works as expected without having to
  specify the offset.

  2) Working scenario (crashkernel < 4G, e.g., 'crashkernel=1G')

  This must continue to work with the new patches (ie, no regressions),
  including patched kexec-tools on unpatched kernel (eg, 5.4 kernel on
  Focal).

  [Regression Potential]

  KERNEL 5.15 - Jammy (and Focal via the HWE kernel):

  To address this problem in the 5.15 kernel we need to pull in 7 commits (see 
[Other] section for details.
  All the commits are changing code only for arm64 architecture and only the 
code related to reserving the crashkernel.
  This means that any regression potential will affect only the arm64 
architecture and in particular the crash/kdump functionality.
  However, since the reservation of the crashkernel occurs at boot up, 
potentially things could go wrong there as well.

  kexec-tools - FOCAL:

  To fix the kexec_tools in focal we need to pull in 6 commits (see [Other 
section for details]). They all cherry pick.
  Four out of six commits touch only arm64 code. Any regression potential 
because of these commits  would regard either crashdump or kexec functionality.
  Commit cf977b1af9ec67fab adds code without altering current functionality.
  Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive 
it moves the code from vmcore-dmesg.c  to elf_info.c so it can be used by other 
features.

  kexec-tools - JAMMY, LUNAR, MANTIC:

  Commit b5a34a20984c is pulled in, it cherry-picks. It changes only
  arm64 code. It

[Kernel-packages] [Bug 2024479] Update Released

2023-07-26 Thread Robie Basak

The verification of the Stable Release Update for kexec-tools has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  kdump fails on big arm64 systems when offset is not specified

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe-5.15 package in Ubuntu:
  Invalid
Status in kexec-tools source package in Focal:
  Fix Released
Status in linux source package in Focal:
  Won't Fix
Status in linux-hwe-5.15 source package in Focal:
  In Progress
Status in kexec-tools source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  In Progress
Status in linux-hwe-5.15 source package in Jammy:
  Invalid
Status in kexec-tools source package in Kinetic:
  Won't Fix
Status in linux source package in Kinetic:
  Won't Fix
Status in linux-hwe-5.15 source package in Kinetic:
  Invalid
Status in kexec-tools source package in Lunar:
  Fix Released
Status in kexec-tools source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  kdump fails on arm64, on machines with a lot of memory when offset is not 
specified,
  e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"

  If kdump-tools.cfg specifies the offset e.g.:
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
  it works ok.

  The reason for this is that the kernel needs to allocate memory for the 
crashkernel both
  in low and high memory.
  This is addressed in kernel 6.2.
  In addition kexec-tools needs to support more than one crash kernel region.

  [Fix]

  To address this issue the following upstream commits are needed:

  - From the kernel side:

  commit a9ae89df737756d92f0e14873339cf393f7f7eb0
  Author: Zhen Lei 
  Date: Wed Nov 16 20:10:44 2022 +0800

  arm64: kdump: Support crashkernel=X fall back to reserve region
  above DMA zones

  commit a149cf00b158e1793a8dd89ca492379c366300d2
  Author: Zhen Lei 
  Date: Wed Nov 16 20:10:43 2022 +0800

  arm64: kdump: Provide default size when crashkernel=Y,low is not
  specified

  - From kexec-tools:

  commit b5a34a20984c4ad27cc5054d9957af8130b42a50
  Author: Chen Zhou 
  Date: Mon Jan 10 18:20:08 2022 +0800

  arm64: support more than one crash kernel regions

  Affected releases:
  Jammy, Focal, Bionic

  For Bionic we won't fix it as we need to backport a lot of code and the 
regression potential is too high.
  The same applies for the Focal 5.4 kernel.
  Only the Focal 5.15 hwe kernel (from Jammy) will be fixed.

  [Test Plan]

  You need an arm64 machine (can be a VM too) with large memory e.g. 128G.
  Install linux-crashdump, configure the crash kernel size, and trigger a crash.

  1) Failing scenario (crashkernel >= 4G, without offset "@"):

  It won't work unless the offset is specified because the memory
  crashkernel cannot be allocated.

  With the patches applied it works as expected without having to
  specify the offset.

  2) Working scenario (crashkernel < 4G, e.g., 'crashkernel=1G')

  This must continue to work with the new patches (ie, no regressions),
  including patched kexec-tools on unpatched kernel (eg, 5.4 kernel on
  Focal).

  [Regression Potential]

  KERNEL 5.15 - Jammy (and Focal via the HWE kernel):

  To address this problem in the 5.15 kernel we need to pull in 7 commits (see 
[Other] section for details.
  All the commits are changing code only for arm64 architecture and only the 
code related to reserving the crashkernel.
  This means that any regression potential will affect only the arm64 
architecture and in particular the crash/kdump functionality.
  However, since the reservation of the crashkernel occurs at boot up, 
potentially things could go wrong there as well.

  kexec-tools - FOCAL:

  To fix the kexec_tools in focal we need to pull in 6 commits (see [Other 
section for details]). They all cherry pick.
  Four out of six commits touch only arm64 code. Any regression potential 
because of these commits  would regard either crashdump or kexec functionality.
  Commit cf977b1af9ec67fab adds code without altering current functionality.
  Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive 
it moves the code from vmcore-dmesg.c  to elf_info.c so it can be used by other 
features.

  kexec-tools - JAMMY, LUNAR, MANTIC:

  Commit b5a34a20984c is pulled in, it cherry-picks. It changes

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

** Merge proposal linked:
   https://code.launchpad.net/~dviererbe/casper/+git/casper/+merge/447782

-- 
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:
  Triaged
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
   - 
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-desktop-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-desktop-ppc64el.iso
   - 
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-riscv64.iso
   - 
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-desktop-riscv64.iso
   - 
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-s390x.iso
   - 
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-desktop-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 Langasek (~vorlon) about the link namining. Neither 
 was particularly happy about the current solution, but no
 better solution was found.

   * Original Bug report:

  When PXE booting without pulling in squashfs correctly the system
  tried to be helpful (:-) and grab an ISO. The 22.04.1 Jammy release
  contains a link to the old version which is not present anymore.

  ---
  Unable to find a medium containing a live file system
  Attempt interactive netboot from a URL?
  yes no (default yes):
  Two methods available for IP configuration:
    * stati

[Kernel-packages] [Bug 2028770] [NEW] package nvidia-dkms-525-server (not installed) failed to install/upgrade: подпроцесс из пакета nvidia-dkms-525-server установлен сценарий post-installation возвра

2023-07-26 Thread Paul Ananev

Public bug reported:

1

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-dkms-525-server (not installed)
ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17
Uname: Linux 5.19.0-50-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Jul 26 11:57:56 2023
ErrorMessage: подпроцесс из пакета nvidia-dkms-525-server установлен сценарий 
post-installation возвратил код ошибки 10
InstallationDate: Installed on 2023-04-13 (104 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-525-server
Title: package nvidia-dkms-525-server (not installed) failed to 
install/upgrade: подпроцесс из пакета nvidia-dkms-525-server установлен 
сценарий post-installation возвратил код ошибки 10
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-525-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-525-server in
Ubuntu.
https://bugs.launchpad.net/bugs/2028770

Title:
  package nvidia-dkms-525-server (not installed) failed to
  install/upgrade: подпроцесс из пакета nvidia-dkms-525-server
  установлен сценарий post-installation возвратил код ошибки 10

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

Bug description:
  1

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: nvidia-dkms-525-server (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17
  Uname: Linux 5.19.0-50-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Jul 26 11:57:56 2023
  ErrorMessage: подпроцесс из пакета nvidia-dkms-525-server установлен сценарий 
post-installation возвратил код ошибки 10
  InstallationDate: Installed on 2023-04-13 (104 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-525-server
  Title: package nvidia-dkms-525-server (not installed) failed to 
install/upgrade: подпроцесс из пакета nvidia-dkms-525-server установлен 
сценарий post-installation возвратил код ошибки 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-525-server/+bug/2028770/+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 1990621] Re: PXE Boot contains wrong suggested link to ISO for live file system

2023-07-26 Thread Dominik Viererbe

** Description changed:

+ [ 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
+  - 
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-desktop-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-desktop-ppc64el.iso
+  - 
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-riscv64.iso
+  - 
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-desktop-riscv64.iso
+  - 
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-s390x.iso
+  - 
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-desktop-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 Langasek (~vorlon) about the link namining. Neither 
+was particularly happy about the current solution, but no
+better solution was found.
+ 
+  * Original Bug report:
+ 
  When PXE booting without pulling in squashfs correctly the system tried
  to be helpful (:-) and grab an ISO. The 22.04.1 Jammy release contains a
  link to the old version which is not present anymore.
  
  ---
  Unable to find a medium containing a live file system
  Attempt interactive netboot from a URL?
- yes no (default yes): 
+ yes no (default yes):
  Two methods available for IP configuration:
-   * static: for static IP configuration
-   * dhcp: for automatic IP configuration
- static dhcp (default 'dhcp'): 
- vlan id (optional): 
-  https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso 
(default)
-  https://releases.ubuntu.com/jammy/ubuntu-22.04-desktop-amd64.iso
- url: 
- http_proxy (optional): 
+   * static: for static IP configuration
+   * dhcp: for automatic IP configuration
+ static dhcp (default 'dhcp'):
+ vlan id (optional):
+  https://releases.ubuntu.com

[Kernel-packages] [Bug 2028366] Re: Kernel header installation fails for incompatible DKMS modules

2023-07-26 Thread Juerg Haefliger

Should we put this into lunar as well? I'm still seeing occasional bug
reports because of this issue.

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

Title:
  Kernel header installation fails for incompatible DKMS modules

Status in dkms package in Ubuntu:
  Triaged

Bug description:
  If a new kernel is installed, all installed DKMS modules are built for
  that new kernel. There might be incompatible modules that won't
  compile for the new kernel which results in a kernel header package
  installation failure. That's bad and not really correct, the
  incompatible DKMS module is the problem and not the new kernel.

  In this case, DKMS module build failures should be ignored so that the
  kernel installation completes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2028366/+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 2026211] Re: [23.10 FEAT] [VS2111] KVM: Enhance CCW address translation architectural compliance

2023-07-26 Thread Frank Heimes

** Changed in: linux (Ubuntu)
 Assignee: Frank Heimes (fheimes) => (unassigned)

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

Title:
  [23.10 FEAT] [VS2111] KVM: Enhance CCW address translation
  architectural compliance

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

Bug description:
  Currently, CCW passthrough relies on every I/O containing only direct-
  addressed CCWs or a 4K Format-2 IDA, which is sufficient for Linux.
  Other operating systems may however require different formats and can
  fail on I/O.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2026211/+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 2026213] Re: [23.10 FEAT] [VS2208] KVM: Provide Atomic Memop for Key-Checked Compare-and-swap

2023-07-26 Thread Frank Heimes

I've verified if the commits listed in the bug description are incl. in current 
mantic master-next and they are, incl. all of them.
And since we already have a linux-generic kernel 6.3 in mantic:
 linux-generic | 6.3.0.7.8 | mantic | amd64, arm64, armhf, ppc64el, s390x
 linux-generic | 6.3.0.7.9 | mantic-proposed | amd64, arm64, armhf, ppc64el, 
s390x
I'm updating this ticket to Fix Released.

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

** Changed in: ubuntu-z-systems
   Status: Confirmed => Fix Released

** Information type changed from Private to Public

** Changed in: linux (Ubuntu)
 Assignee: Frank Heimes (fheimes) => (unassigned)

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

Title:
  [23.10 FEAT] [VS2208] KVM: Provide Atomic Memop for Key-Checked
  Compare-and-swap

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

Bug description:
  Currently, userspace has to perform two operations in order to do a 
storage-key-checked compare-and-swap:
  1. Keycheck memop, followed by
  2. compare-and-swap.
  While not a problem with currently known hypervisor and O/S combinations it 
is theoretically possible, that the storage key of the operand is changed after 
1 and before 2. From an architectural perspective it would be preferable to 
have a truly atomic memop for this purpose, which is implemented by this 
feature.

  Unrelated commits but part of memup selftest for v6.3:

  7d42b38de992 ("KVM: s390: selftest: memop: Pass mop_desc via pointer")
  12d27074193b ("KVM: s390: selftest: memop: Replace macros by functions")
  de14e014a7c6 ("KVM: s390: selftest: memop: Move testlist into main")
  06e5da81c66c ("KVM: s390: selftest: memop: Add bad address test")
  76a2ee43ed9a ("KVM: s390: selftest: memop: Fix typo")
  12c12a9924b4 ("KVM: s390: selftest: memop: Fix wrong address being used in 
test")
  dc55ceaef616 ("KVM: s390: selftest: memop: Fix integer literal")
  a41f505e9f7f ("KVM: s390: Move common code of mem_op functions into function")
  8550bcb754bc ("KVM: s390: Dispatch to implementing function at top level of 
vm mem_op")
  0d6d4d23955c ("KVM: s390: Refactor absolute vm mem_op function")
  701422b34382 ("KVM: s390: Refactor vcpu mem_op function")

  Commits related to LI for v6.3:

  3fd49805d19d ("KVM: s390: Extend MEM_OP ioctl by storage key checked cmpxchg")
  a7b041732802 ("Documentation: KVM: s390: Describe KVM_S390_MEMOP_F_CMPXCHG")
  0dd714bfd200 ("KVM: s390: selftest: memop: Add cmpxchg tests")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2026213/+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 2028187] Re: Bluetooth audio locked to device disallows other devices to use Bluetooth speaker

2023-07-26 Thread Paul White

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

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

Title:
  Bluetooth audio locked to device disallows other devices to use
  Bluetooth speaker

Status in bluez package in Ubuntu:
  New

Bug description:
  Not sure which layer is causing this. I switch bluetooth audio sources
  going to my AVR frequently throughout the day. After an update, Ubuntu
  seems to continue sending something like a keepalive to the bluetooth
  receiver despite no audio being played on the computer. This prohibits
  switching to my phone as the audio source. For example if I play a
  youtube video in Chrome, and then stop the video and then play Amazon
  Music or Spotify, the device is connected but I get no audio. If I
  close Chrome, no change. If I disconnect Ubuntu from that bluetooth
  device, audio starts coming through. No change to bluetooth receiver,
  but there was a Samsung update the other day.

  Interestingly, I disconnected Ubuntu from my BT device. Connected my
  phone, played some audio, then disconnected my phone from the BT
  device. Ubuntu then automatically connected back to that BT device and
  prohibits my phone from using it. This was clearly a change to the
  bluetooth stack that doesn't release the BT device when audio is
  stopped by the application.

  Linux gnosis 5.15.0-76-generic #83

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2028187/+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 2026211] Re: [23.10 FEAT] [VS2111] KVM: Enhance CCW address translation architectural compliance

2023-07-26 Thread Frank Heimes

I've verified if the commits listed in comment #1 are incl. in current mantic 
master-next and they are, incl. all optional and suggested ones.
And since we already have a linux-generic kernel 6.3 in mantic:
 linux-generic | 6.3.0.7.8  | mantic   | amd64, arm64, 
armhf, ppc64el, s390x
 linux-generic | 6.3.0.7.9  | mantic-proposed  | amd64, arm64, 
armhf, ppc64el, s390x

I'm updating this ticket to Fix Released.

** Changed in: ubuntu-z-systems
   Status: Confirmed => Fix Released

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

** Information type changed from Private to Public

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

Title:
  [23.10 FEAT] [VS2111] KVM: Enhance CCW address translation
  architectural compliance

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

Bug description:
  Currently, CCW passthrough relies on every I/O containing only direct-
  addressed CCWs or a 4K Format-2 IDA, which is sufficient for Linux.
  Other operating systems may however require different formats and can
  fail on I/O.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2026211/+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 2028165] Re: nvidia-dkms-* FTBS with linux 6.5

2023-07-26 Thread Paolo Pisati

525-server fix for Linux 6.5

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

** Patch added: "nvidia-graphics-drivers-525-server_525.125.06-0ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525-server/+bug/2028165/+attachment/5688552/+files/nvidia-graphics-drivers-525-server_525.125.06-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-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-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 1950792] Re: No boot possible - Cannot open root device

2023-07-26 Thread Bartosz Woronicz

I also encountered something similar, some computes randomly are unable to boot
I may check disabling this HTTP boot

$ maas root maas get-config name=kernel_opts
Success.
Machine-readable output follows:
"console=tty0 console=ttyS0,115200n8"

** Attachment added: "Screenshot from 2023-07-26 10-43-06.png"

https://bugs.launchpad.net/maas/+bug/1950792/+attachment/5688544/+files/Screenshot%20from%202023-07-26%2010-43-06.png

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

Title:
No boot possible - Cannot open root device

Status in MAAS:
Triaged
Status in linux package in Ubuntu:
Incomplete

Bug description:
MaaS cannot boot on my X11DPi-NT and will therefore fail to
commission. It will instantly fail after grub.

It will fail to boot saying that is not able to open root device. I
even tried supplying the squashfs via python on a different port as
the url is somehow cut off a bit, but to no avail. The python
webserver doesn't even see any connection try.

( custom kernel params: root=squash:http://10.0.33.253:8080/squashfs
python webserver: python3 -m http.server 8080)

Steps to reproduce:

1. Setup maas ;)
2. Try to commision server
3. See the kernel and initrd download fly by
4. Boom kernel panic

Hardware:
Supermicro X11DPi-NT with UEFI http Networkboot enabled
NIC: Intel X722

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1950792/+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 2023313] Re: gcp: backport "iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support"

This bug was fixed in the package linux-gcp-5.19 -
5.19.0-1030.32~22.04.1

---
linux-gcp-5.19 (5.19.0-1030.32~22.04.1) jammy; urgency=medium

  * jammy/linux-gcp-5.19: 5.19.0-1030.32~22.04.1 -proposed tracker
(LP: #2027609)

  * gcp: backport "iommu/amd: Add map/unmap_pages() iommu_domain_ops  callback
support" (LP: #2023313)
- iommu/amd/io-pgtable: Implement map_pages io_pgtable_ops callback
- iommu/amd/io-pgtable: Implement unmap_pages io_pgtable_ops callback
- iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support

linux-gcp-5.19 (5.19.0-1029.31~22.04.1) jammy; urgency=medium

  * jammy/linux-gcp-5.19: 5.19.0-1029.31~22.04.1 -proposed tracker
(LP: #2026451)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf

  [ Ubuntu: 5.19.0-50.50 ]

  * jammy/linux-hwe-5.19: 5.19.0-50.50 -proposed tracker (LP: #2026456)
  * CVE-2023-2640 // CVE-2023-32629
- Revert "UBUNTU: SAUCE: overlayfs: handle idmapped mounts in
  ovl_do_(set|remove)xattr"
- Revert "UBUNTU: SAUCE: overlayfs: Skip permission checking for
  trusted.overlayfs.* xattrs"
- SAUCE: overlayfs: default to userxattr when mounted from non initial user
  namespace
  * CVE-2023-35001
- netfilter: nf_tables: prevent OOB access in nft_byteorder_eval
  * CVE-2023-31248
- netfilter: nf_tables: do not ignore genmask when looking up chain by id
  * CVE-2023-3389
- io_uring: hold uring mutex around poll removal
  * CVE-2023-3390
- netfilter: nf_tables: incorrect error path handling with NFT_MSG_NEWRULE
  * CVE-2023-3141
- memstick: r592: Fix UAF bug in r592_remove due to race condition
  * CVE-2023-3090
- ipvlan:Fix out-of-bounds caused by unclear skb->cb
  * CVE-2022-48502
- fs/ntfs3: Check fields while reading
  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf

 -- Thadeu Lima de Souza Cascardo   Wed, 12 Jul
2023 16:00:46 -0300

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-48502

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-2640

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3090

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-31248

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3141

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-32629

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3389

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3390

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-35001

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

Title:
  gcp: backport "iommu/amd: Add map/unmap_pages() iommu_domain_ops
  callback support"

Status in linux-gcp package in Ubuntu:
  In Progress
Status in linux-gcp-5.19 package in Ubuntu:
  New
Status in linux-gcp source package in Jammy:
  Invalid
Status in linux-gcp-5.19 source package in Jammy:
  Fix Released
Status in linux-gcp source package in Kinetic:
  In Progress
Status in linux-gcp-5.19 source package in Kinetic:
  Invalid

Bug description:
  GCP is requesting the backport of the patch "6b080c4e815ceba3c08f
  iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support"
  from upstream 6.2 to the 5.19 gcp kernel

  The following two patches are required for the backport:
   6b080c4e815ceba3c08ffa980c858595c07e7 iommu/amd/io-pgtable: Implement 
map_pages io_pgtable_ops callback
   251c4db699ca7b966db7e59e8663a231c96ba iommu/amd/io-pgtable: Implement 
unmap_pages io_pgtable_ops callback

  More info at
  https://canonical.lightning.force.com/lightning/r/Case/5008e0CjJJCAA3/view

  Impact:
   - This allows the AMD iommu driver to map/unmap multiple pages in one call. 
GCP states that these changes also have a security side-effect which they are 
interested in.

  Testing:
   - Boot-tested the changes in SEV, SEV-SNP and non-SEV environments on AMD 
hardware.

  Regression potential:
   - The changes are limited to the AMD iommu driver. Regression potential 
could impact virtualization on AMD hardware. Risk is considered low as the 
changes are limited and apply cleanly from upstream. The requested patch is 
from 6.2 and there have been no follow-up fixes since.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2023313/+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 2028366] Re: Kernel header installation fails for incompatible DKMS modules

** Changed in: dkms (Ubuntu)
   Status: New => Triaged

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

Title:
  Kernel header installation fails for incompatible DKMS modules

Status in dkms package in Ubuntu:
  Triaged

Bug description:
  If a new kernel is installed, all installed DKMS modules are built for
  that new kernel. There might be incompatible modules that won't
  compile for the new kernel which results in a kernel header package
  installation failure. That's bad and not really correct, the
  incompatible DKMS module is the problem and not the new kernel.

  In this case, DKMS module build failures should be ignored so that the
  kernel installation completes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2028366/+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 2028366] Re: Kernel header installation fails for incompatible DKMS modules

This looks good, trying to see how i can make current ubuntu8 dkms
migrate, before uploading this one.

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

Title:
  Kernel header installation fails for incompatible DKMS modules

Status in dkms package in Ubuntu:
  New

Bug description:
  If a new kernel is installed, all installed DKMS modules are built for
  that new kernel. There might be incompatible modules that won't
  compile for the new kernel which results in a kernel header package
  installation failure. That's bad and not really correct, the
  incompatible DKMS module is the problem and not the new kernel.

  In this case, DKMS module build failures should be ignored so that the
  kernel installation completes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2028366/+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 2000708] Re: udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with K-5.19 (Missing nat6to4 helper)

2023-07-26 Thread Po-Hsu Lin

This issue does not exist in Lunar anymore.
Hints removed. Closing this bug.

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

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

** Changed in: ubuntu-kernel-tests
   Status: In Progress => Fix Released

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

Title:
  udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with
  K-5.19 (Missing nat6to4 helper)

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  Issue found with 5.19.0-28.29

  Running 'make run_tests -C net TEST_PROGS=udpgro_frglist.sh TEST_GEN_PROGS='' 
TEST_CUSTOM_PROGS='''
   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
   make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install
   make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
 INSTALL ./usr/include
   make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
   TAP version 13
   1..1
   # selftests: net: udpgro_frglist.sh
   # Missing nat6to4 helper. Build bpfnat6to4.o selftest first
   not ok 1 selftests: net: udpgro_frglist.sh # exit=255

  
  This is not a regression as the net test build was blocked with bug 1993155

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000708/+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 compressed

hi, i like portions of the patch, but not quite where in the machinery
it is implemented.

As we have many more packages that ship .ko modules, and those debs
should not be compressed.

And also i'd want to enable in-kernel decompressor too.

-- 
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 compressed

Status in linux package in Ubuntu:
  New

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

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 2018657] Re: Sound output fails