date:20230612

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Amd Radeon Navi RX 6600m poor performance

Status in linux package in Ubuntu:
  Expired
Status in steam package in Ubuntu:
  Expired

Bug description:
  I can't open steam because it crashes and there are strange artifacts
  on the screen, the performance overall is really bad (for example Age
  of empires 2 works bad on 1080p and low settings). I've noticed an
  error message on the terminal that says possibly missing firmware each
  time I update grub.

  Currently using 23.04, no PPA's

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015308/+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 2015308] Re: Amd Radeon Navi RX 6600m poor performance

[Expired for steam (Ubuntu) because there has been no activity for 60
days.]

** Changed in: steam (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Amd Radeon Navi RX 6600m poor performance

Status in linux package in Ubuntu:
  Expired
Status in steam package in Ubuntu:
  Expired

Bug description:
  I can't open steam because it crashes and there are strange artifacts
  on the screen, the performance overall is really bad (for example Age
  of empires 2 works bad on 1080p and low settings). I've noticed an
  error message on the terminal that says possibly missing firmware each
  time I update grub.

  Currently using 23.04, no PPA's

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.19/5.19.0.45.46~22.04.20)

All autopkgtests for the newly accepted linux-meta-hwe-5.19 
(5.19.0.45.46~22.04.20) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

linux-hwe-5.19/5.19.0-45.46~22.04.1 (armhf)
lttng-modules/2.13.8-1~ubuntu22.04.0 (amd64, arm64, armhf, ppc64el, s390x)
openrazer/unknown (arm64)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-hwe-5.19

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2021962] Re: F/xilinx and J/xilinx uses different keyword in /proc/device-tree/compatible

2023-06-12 Thread Portia Stephens

The device trees comes directly from the Xilinx kernel
(https://github.com/Xilinx/linux-xlnx) . It seems like in the focal
kernel the overlay for the KV260 SOM did not set a compatible string so
the it fell back to the compatible string defined by the baseboard
(zynqmp-smk-k26-revA.dts) . When a device tree for rev B of the board
was added the compatible string was added to the rev A device tree as
well.

The change was added here:
https://github.com/Xilinx/linux-xlnx/commit/70604467dc949d3b77eabaa1288365cb25b2ec23#diff-f19b970e083cc67c8063c7698b0bb6554d69d43190d355adc20945526eda5831

I agree with Masahiro that Jammy is correct. Since the device trees are
not in the kernel build and are provided by Xilinx I don't think this is
something we can backport to Focal.

** Changed in: linux-xilinx-zynqmp (Ubuntu)
   Status: New => Won't Fix

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

Title:
  F/xilinx and J/xilinx uses different keyword in /proc/device-
  tree/compatible

Status in ubuntu-kernel-tests:
  New
Status in linux-xilinx-zynqmp package in Ubuntu:
  Won't Fix

Bug description:
  While testing J/xilinx, I noticed that the keyword we use to grep from
  /proc/device-tree/compatible has to be changed into kv26 instead of
  k26 that we used for F/xilinx

  J/xilinx:
  $ cat /proc/device-tree/compatible
  
xlnx,zynqmp-sk-kv260-rev1xlnx,zynqmp-sk-kv260-revBxlnx,zynqmp-sk-kv260xlnx,zynqmp

  F/xilinx:
  $ cat /proc/device-tree/compatible
  
xlnx,zynqmp-smk-k26-rev1xlnx,zynqmp-smk-k26-revBxlnx,zynqmp-smk-k26-revAxlnx,zynqmp-smk-k26xlnx,zynqmp

  From what I can found on the Internet, KV260 is "a vision application
  development platform for Kria K26 SOMs (system-on-module)". But it's
  better to let the kernel maintainer (Portia) to answer that if this
  difference is expected.

  
  Related change for tests:
  
https://code.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests/+merge/443543

  ---
  External link: https://warthogs.atlassian.net/browse/PEL-439

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2021962/+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 2023611] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 2023611

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Unable to remove efi variable with 6.2.0-21.21 or newer lunar kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm seeing an issue on an isolated host, howzit, in which it fails to
  remove boot entries. In my limited testing this worked with the
  6.2.0-20.20 kernel, but not the 21.21 or 23.23 kernel. I have not yet
  tried any of the 6.3 kernels.

  I've only seen this on one host so far, howzit, which is an arm64
  server. I have tested on three other arm64 servers and they don't
  appear to be impacted, so this could be some firmware issue. It
  adversely impacts maas installs and will cause a mantic install (which
  is using 6.2.0-21.21) to fail because it can't modify the boot paths.

  Here's what I see trying to remove a boot entry:
  ubuntu@howzit-kernel:~$ efibootmgr -v
  BootCurrent: 0005
  Timeout: 5 seconds
  BootOrder: 0005,0007,0004,0006
  Boot0004  UEFI: Built-in EFI Shell  
VenMedia(5023b95c-db26-429b-a648-bd47664c8012)..BO
  Boot0005* UEFI: PXE IPv4 Mellanox Network Adapter - 0C:42:A1:52:3D:4C   
PcieRoot(0x3)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(0c42a1523d4c,1)/IPv4(0.0.0.00.0.0.0,0,0)..BO
  Boot0006  UEFI: PXE IPv4 Mellanox Network Adapter - 0C:42:A1:52:3D:4D   
PcieRoot(0x3)/Pci(0x1,0x0)/Pci(0x0,0x1)/MAC(0c42a1523d4d,1)/IPv4(0.0.0.00.0.0.0,0,0)..BO
  Boot0007* ubuntu
HD(1,GPT,6d8df92f-72ad-4c24-bc8d-8236a4c5e222,0x800,0x10)/File(\EFI\UBUNTU\GRUBAA64.EFI)..BO
  ubuntu@howzit-kernel:~$ sudo efibootmgr -B -b 0007
  Could not delete variable: Invalid argument

  The same command will work with the 6.2.0-20.20 kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023611/+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 2023611] [NEW] Unable to remove efi variable with 6.2.0-21.21 or newer lunar kernel

2023-06-12 Thread Francis Ginther

Public bug reported:

I'm seeing an issue on an isolated host, howzit, in which it fails to
remove boot entries. In my limited testing this worked with the
6.2.0-20.20 kernel, but not the 21.21 or 23.23 kernel. I have not yet
tried any of the 6.3 kernels.

I've only seen this on one host so far, howzit, which is an arm64
server. I have tested on three other arm64 servers and they don't appear
to be impacted, so this could be some firmware issue. It adversely
impacts maas installs and will cause a mantic install (which is using
6.2.0-21.21) to fail because it can't modify the boot paths.

Here's what I see trying to remove a boot entry:
ubuntu@howzit-kernel:~$ efibootmgr -v
BootCurrent: 0005
Timeout: 5 seconds
BootOrder: 0005,0007,0004,0006
Boot0004  UEFI: Built-in EFI Shell  
VenMedia(5023b95c-db26-429b-a648-bd47664c8012)..BO
Boot0005* UEFI: PXE IPv4 Mellanox Network Adapter - 0C:42:A1:52:3D:4C   
PcieRoot(0x3)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(0c42a1523d4c,1)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0006  UEFI: PXE IPv4 Mellanox Network Adapter - 0C:42:A1:52:3D:4D   
PcieRoot(0x3)/Pci(0x1,0x0)/Pci(0x0,0x1)/MAC(0c42a1523d4d,1)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0007* ubuntu
HD(1,GPT,6d8df92f-72ad-4c24-bc8d-8236a4c5e222,0x800,0x10)/File(\EFI\UBUNTU\GRUBAA64.EFI)..BO
ubuntu@howzit-kernel:~$ sudo efibootmgr -B -b 0007
Could not delete variable: Invalid argument

The same command will work with the 6.2.0-20.20 kernel.

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


** Tags: lunar

** Tags added: lunar

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

Title:
  Unable to remove efi variable with 6.2.0-21.21 or newer lunar kernel

Status in linux package in Ubuntu:
  New

Bug description:
  I'm seeing an issue on an isolated host, howzit, in which it fails to
  remove boot entries. In my limited testing this worked with the
  6.2.0-20.20 kernel, but not the 21.21 or 23.23 kernel. I have not yet
  tried any of the 6.3 kernels.

  I've only seen this on one host so far, howzit, which is an arm64
  server. I have tested on three other arm64 servers and they don't
  appear to be impacted, so this could be some firmware issue. It
  adversely impacts maas installs and will cause a mantic install (which
  is using 6.2.0-21.21) to fail because it can't modify the boot paths.

  Here's what I see trying to remove a boot entry:
  ubuntu@howzit-kernel:~$ efibootmgr -v
  BootCurrent: 0005
  Timeout: 5 seconds
  BootOrder: 0005,0007,0004,0006
  Boot0004  UEFI: Built-in EFI Shell  
VenMedia(5023b95c-db26-429b-a648-bd47664c8012)..BO
  Boot0005* UEFI: PXE IPv4 Mellanox Network Adapter - 0C:42:A1:52:3D:4C   
PcieRoot(0x3)/Pci(0x1,0x0)/Pci(0x0,0x0)/MAC(0c42a1523d4c,1)/IPv4(0.0.0.00.0.0.0,0,0)..BO
  Boot0006  UEFI: PXE IPv4 Mellanox Network Adapter - 0C:42:A1:52:3D:4D   
PcieRoot(0x3)/Pci(0x1,0x0)/Pci(0x0,0x1)/MAC(0c42a1523d4d,1)/IPv4(0.0.0.00.0.0.0,0,0)..BO
  Boot0007* ubuntu
HD(1,GPT,6d8df92f-72ad-4c24-bc8d-8236a4c5e222,0x800,0x10)/File(\EFI\UBUNTU\GRUBAA64.EFI)..BO
  ubuntu@howzit-kernel:~$ sudo efibootmgr -B -b 0007
  Could not delete variable: Invalid argument

  The same command will work with the 6.2.0-20.20 kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023611/+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 2006994] Re: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep

2023-06-12 Thread Ben Baker

Can you try adding `intel_idle.max_cstate=1` kernel boot arg. So far it
seems to have fixed the suspend-wakeup issue on AC power for me.

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

Title:
Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on
after waking up from sleep

Status in linux package in Ubuntu:
Confirmed

Bug description:
Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on
after waking up from sleep

Scenario:

Fresh and clean Ubuntu 22.10 install on Latitude 7390, requiring
nomodeset kernel boot option to be added in GRUB at boot time when
booting from USB stick. This can be achieved by following instructions
from here: https://www.dell.com/support/kbdoc/en-uk/000123893/manual-
nomodeset-kernel-boot-line-option-for-linux-booting

Then, nomodeset needs to be permanently added to /etc/default/grub
Followed instructions from
https://askubuntu.com/questions/38780/how-do-i-set-nomodeset-after-ive-already-installed-ubuntu

If nomodeset is not added, Dell Latitude 7390 will freeze at one point
or another, either before reaching the Gnome desktop, either little
after. This is the case with both, installing Ubuntu 22.10 from Live
USB and running Ubuntu 22.10 after install the install (and having the
USB stick disconnected).

The issue after having Ubuntu 22.10 installed on Dell Latitude 7390 and
having nomodeset permanently added to GRUB for each boot is:

If by chance the system goes into sleep, after waking up, there is a
totally pitch-black screen; nothing shows up, no screen backlight
either. However, caps-lock works and I am able to log in to the system
via ssh and can see the system is up an running well. I can even issue
a request to send the system to sleep by “sudo systemctl suspend” and
then wake the the system up several times without loosing ssh access,
however, the screen will remain pitch-black.

Other tries to troubleshoot and see if the system can be brought back with a
working display (while nomodeset kernel option is being used):

1. sudo systemctl suspend -i
>>> this will result in an unusable system after waking up, again, with a
pitch-black screen; moreover, the caps-lock would not work, the keyboard
backlight won’t work, ssh won’t work; I need a hard reset to get the system
back up.

2. start the system in single user mode by inserting “single” in GRUB at boot
time;
>>> the system will be unusable after waking up, same as in try 1.

3. after a normal boot into the GNOME desktop with kernel nomodeset
option and investigating the dmesg for any acpi, no error could be
found.

Tried to read up on other possible solutions, while stumbled upon the ubuntu
wiki page below:
https://wiki.ubuntu.com/UnderstandingSuspend
Unfortunately, to not much help so far.

Other notes:
N1. All the above were done by having the latest BIOS v1.30.0
N2. This laptop came with Windows 10 Pro which works fine: goes into suspend
and wakes up fine, with working screen and display.

N3. Dell Latitude 7390 was released on 15 Feb 2018 ( source:
https://www.laptoparena.net/dell/notebook-dell-latitude-7390-n025l739013emea-black-12984
) and the user manual states it has support for Ubuntu. Therefore, other older
and major Ubuntu versions were given a try, along with a new version of Fedora:
N3.1 – Ubuntu 22.04
N3.2 – Ubuntu 18.04.6
N3.3 – Ubuntu 16.04.7
N3.4 – Fedora-Workstation-Live-x86_64-37-1.7
Each of the above will freeze at one point or another if nomodeset is not
used, except the Ubuntu 18.04.6 and Ubuntu 16.04.7 which will run well and
install well from the USB Live stick and will also run fine after the install,
until the system goes into sleep, after which, when the system is awake, the
screen is black and will have nothing displayed.

Any advice will be appreciated. Thank you!

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-31-generic 5.19.0-31.32
ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
Uname: Linux 5.19.0-31-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tuser 2832 F wireplumber
/dev/snd/seq:tuser 2829 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 11 13:37:59 2023
InstallationDate: Installed on 2023-01-15 (27 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. Integrated
Webcam_HD
Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880
Bus 001 Device 001:

[Kernel-packages] [Bug 2011854] Re: cmos_interrupt not getting called

2023-06-12 Thread Po-Hsu Lin

** Tags added: sru-20230515

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

Title:
  cmos_interrupt not getting called

Status in ubuntu-kernel-tests:
  New
Status in linux-oracle-5.15 package in Ubuntu:
  Fix Committed
Status in linux-oracle-5.15 source package in Focal:
  Fix Released
Status in linux-oracle-5.15 source package in Jammy:
  Fix Released

Bug description:
  The ubuntu_ltp_kernel_misc rtc01 test case has exposed a possible
  regression of the RTC cmos driver on certain Oracle clouds.

  This was observed on jammy:linux-oracle-5.15.0-1031.37.
  - VM.DenseIO2.8
  - VM.Standard2.1

  rtc01   0  TINFO  :  RTC READ TEST:
  rtc01   1  TPASS  :  RTC READ TEST Passed
  rtc01   0  TINFO  :  Current RTC date/time is 16-3-2023, 17:36:04.
  rtc01   0  TINFO  :  RTC ALARM TEST :
  rtc01   0  TINFO  :  Alarm time set to 17:36:09.
  rtc01   0  TINFO  :  Waiting 5 seconds for the alarm...
  rtc01   2  TFAIL  :  rtc01.c:151: Timed out waiting for the alarm
  rtc01   0  TINFO  :  RTC UPDATE INTERRUPTS TEST :
  rtc01   0  TINFO  :  Waiting for  5 update interrupts...
  rtc01   3  TFAIL  :  rtc01.c:208: Timed out waiting for the update 
interrupt
  rtc01   0  TINFO  :  RTC Tests Done!

  Notice that we successfully enable RTC_AIE_ON, unlike
  VM.Standard.A1.Flex-4c.8m which does not support it. I confirmed with
  bpftrace on -1029 that we see the cmos interrupt (part of ltp
  read_alarm_test)

  sudo bpftrace -e 'kprobe:cmos_interrupt { printf("%s\n", probe) }'
  Attaching 1 probe...
  kprobe:cmos_interrupt

  On -1031 no interrupt is detected for both the alarm and update tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2011854/+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 2011854] Re: cmos_interrupt not getting called

2023-06-12 Thread Po-Hsu Lin

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

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

Title:
  cmos_interrupt not getting called

Status in ubuntu-kernel-tests:
  New
Status in linux-oracle-5.15 package in Ubuntu:
  Fix Committed
Status in linux-oracle-5.15 source package in Focal:
  Fix Released
Status in linux-oracle-5.15 source package in Jammy:
  Fix Released

Bug description:
  The ubuntu_ltp_kernel_misc rtc01 test case has exposed a possible
  regression of the RTC cmos driver on certain Oracle clouds.

  This was observed on jammy:linux-oracle-5.15.0-1031.37.
  - VM.DenseIO2.8
  - VM.Standard2.1

  rtc01   0  TINFO  :  RTC READ TEST:
  rtc01   1  TPASS  :  RTC READ TEST Passed
  rtc01   0  TINFO  :  Current RTC date/time is 16-3-2023, 17:36:04.
  rtc01   0  TINFO  :  RTC ALARM TEST :
  rtc01   0  TINFO  :  Alarm time set to 17:36:09.
  rtc01   0  TINFO  :  Waiting 5 seconds for the alarm...
  rtc01   2  TFAIL  :  rtc01.c:151: Timed out waiting for the alarm
  rtc01   0  TINFO  :  RTC UPDATE INTERRUPTS TEST :
  rtc01   0  TINFO  :  Waiting for  5 update interrupts...
  rtc01   3  TFAIL  :  rtc01.c:208: Timed out waiting for the update 
interrupt
  rtc01   0  TINFO  :  RTC Tests Done!

  Notice that we successfully enable RTC_AIE_ON, unlike
  VM.Standard.A1.Flex-4c.8m which does not support it. I confirmed with
  bpftrace on -1029 that we see the cmos interrupt (part of ltp
  read_alarm_test)

  sudo bpftrace -e 'kprobe:cmos_interrupt { printf("%s\n", probe) }'
  Attaching 1 probe...
  kprobe:cmos_interrupt

  On -1031 no interrupt is detected for both the alarm and update tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2011854/+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 2016186] Re: 5.19 not reporting cgroups v1 blkio.throttle.io_serviced

Hi Jared you can follow the release of all of the Jammy cloud kernel
here https://kernel.ubuntu.com/sru/dashboards/web/kernel-stable-
board.html , where this fix is included in the 2023.05.15 cycle. They
should be released to updates in the next week.

- Luke

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

Title:
  5.19 not reporting cgroups v1 blkio.throttle.io_serviced

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Kinetic:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Incomplete

Bug description:
  [Impact]

  Commit f382fb0bcef4 ("block: remove legacy IO schedulers") introduced
  a behavior change in the blkio throttle cgroup subsystem: IO
  statistics are not reported anymore unless a throttling rule is
  explicitly defined, because the current code only counts bios that are
  actually throttled.

  This behavior change is potentially breaking some user-space 
  applications that are relying on the old behavior (see original bug 
  report below).

  [Test case]

   - mount cgroup v1
   - create a blkio cgroup
   - move a task into the blkio cgroup
   - perform some I/O (i.e., dd)
   - read the IO stats for the cgroup (blkio.throttle.io_serviced and 
blkio.throttle.io_service_bytes in cgroupfs)
   - IO stats are all 0, unless a throttle rule is defined

  Previous behavior (kernel 5.15) was showing I/O statistics even
  without throttling rules defined.

  [Fix]

  Apply / backport this fix:

  
https://lore.kernel.org/lkml/20230507170631.89607-1-hanjinke@bytedance.com/t/

  [Regression potential]

  The fix is affecting the block IO cgroup subsystem, we may see
  potential regressions in this particular cgroup subsystem with this
  fix applied.

  [Original bug report]

  Hi,

  I'm still investigating but, am a bit stuck. Here's what I've found so
  far.

  Today I've upgraded some nodes in AWS EC2 from the previous v5.15
  linux-aws package to the recently pusblished v5.19 package and
  rebooted. It seems that even when there's disk activity, the files:

  /sys/fs/cgroup/blkio/blkio.throttle.io_serviced
  /sys/fs/cgroup/blkio/blkio.throttle.io_service_bytes

  Are only ever populated with 0's. Prior on v5.15 these would reflect
  the actual disk usage. No other system configuration changes were
  applied just the kernel upgrade and reboot. I've also verified that
  simply rebooting a v5.15 where this does work doesn't break the
  reporting. These EC2 instances are running with cgroups v1 due to
  other compatability issues and I suspect that might be the issue. So
  far, I cannot find any differences. mtab shows the same v1 mount
  setup, the kernel options match betwen v5.15 and v5.19.

  I'm more than happy to fetch whatever info would help out here. I'd
  love to get 5.19 working for us but, we really need the data from
  these files.

  Info:
  Prior version that works: Linux ip-10-128-168-154 5.15.0-1031-aws #35-Ubuntu 
SMP Fri Feb 10 02:07:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  Upgraded version that's broken: Linux ip-10-128-166-219 5.19.0-1022-aws 
#23~22.04.1-Ubuntu SMP Fri Mar 17 15:38:24 UTC 2023 x86_64 x86_64 x86_64 
GNU/Linux

  EC2 instances built off of the published 22.04 LTS AMI in us-east-1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016186/+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 2023603] Re: Kinetic update: upstream stable patchset 2023-06-12

** Description changed:

  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-06-12
+ 
+ Ported from the following upstream stable releases:
+ v5.15.106, v6.1.23
+ v5.15.107, v6.1.24
+ 
     from git://git.kernel.org/
  
  fsverity: don't drop pagecache at end of FS_IOC_ENABLE_VERITY
  kernel: kcsan: kcsan_test: build without structleak plugin
  kcsan: avoid passing -g for test
  ksmbd: don't terminate inactive sessions after a few seconds
  xfrm: Zero padding when dumping algos and encap
  ASoC: codecs: tx-macro: Fix for KASAN: slab-out-of-bounds
  md: avoid signed overflow in slot_store()
  x86/PVH: obtain VGA console info in Dom0
  net: hsr: Don't log netdev_err message on unknown prp dst node
  ALSA: asihpi: check pao in control_message()
  ALSA: hda/ca0132: fixup buffer overrun at tuning_ctl_set()
  fbdev: tgafb: Fix potential divide by zero
  sched_getaffinity: don't assume 'cpumask_size()' is fully initialized
  fbdev: nvidia: Fix potential divide by zero
  fbdev: intelfb: Fix potential divide by zero
  fbdev: lxfb: Fix potential divide by zero
  fbdev: au1200fb: Fix potential divide by zero
  tools/power turbostat: Fix /dev/cpu_dma_latency warnings
  tools/power turbostat: fix decoding of HWP_STATUS
  tracing: Fix wrong return in kprobe_event_gen_test.c
  ca8210: Fix unsigned mac_len comparison with zero in ca8210_skb_tx()
  mips: bmips: BCM6358: disable RAC flush for TP1
  ALSA: usb-audio: Fix recursive locking at XRUN during syncing
  platform/x86: think-lmi: add missing type attribute
  platform/x86: think-lmi: use correct possible_values delimiters
  platform/x86: think-lmi: only display possible_values if available
  platform/x86: think-lmi: Add possible_values for ThinkStation
  mtd: rawnand: meson: invalidate cache on polling ECC bit
  SUNRPC: fix shutdown of NFS TCP client socket
  sfc: ef10: don't overwrite offload features at NIC reset
  scsi: megaraid_sas: Fix crash after a double completion
  scsi: mpt3sas: Don't print sense pool info twice
  ptp_qoriq: fix memory leak in probe()
  net: dsa: microchip: ksz8863_smi: fix bulk access
  r8169: fix RTL8168H and RTL8107E rx crc error
  regulator: Handle deferred clk
  net/net_failover: fix txq exceeding warning
  net: stmmac: don't reject VLANs when IFF_PROMISC is set
  drm/i915/tc: Fix the ICL PHY ownership check in TC-cold state
  platform/x86/intel/pmc: Alder Lake PCH slp_s0_residency fix
  can: bcm: bcm_tx_setup(): fix KMSAN uninit-value in vfs_write
  s390/vfio-ap: fix memory leak in vfio_ap device driver
  loop: LOOP_CONFIGURE: send uevents for partitions
  net: mvpp2: classifier flow fix fragmentation flags
  net: mvpp2: parser fix QinQ
  net: mvpp2: parser fix PPPoE
  smsc911x: avoid PHY being resumed when interface is not up
  ice: add profile conflict check for AVF FDIR
  ice: fix invalid check for empty list in ice_sched_assoc_vsi_to_agg()
  ALSA: ymfpci: Create card with device-managed snd_devm_card_new()
  ALSA: ymfpci: Fix BUG_ON in probe function
  net: ipa: compute DMA pool size properly
  i40e: fix registers dump after run ethtool adapter self test
  bnxt_en: Fix reporting of test result in ethtool selftest
  bnxt_en: Fix typo in PCI id to device description string mapping
  bnxt_en: Add missing 200G link speed reporting
  net: dsa: mv88e6xxx: Enable IGMP snooping on user ports only
  net: ethernet: mtk_eth_soc: fix flow block refcounting logic
  pinctrl: ocelot: Fix alt mode for ocelot
  iommu/vt-d: Allow zero SAGAW if second-stage not supported
  Input: alps - fix compatibility with -funsigned-char
  Input: focaltech - use explicitly signed char type
  cifs: prevent infinite recursion in CIFSGetDFSRefer()
  cifs: fix DFS traversal oops without CONFIG_CIFS_DFS_UPCALL
  Input: goodix - add Lenovo Yoga Book X90F to nine_bytes_report DMI table
  btrfs: fix race between quota disable and quota assign ioctls
  btrfs: scan device in non-exclusive mode
  zonefs: Always invalidate last cached page on append write
  can: j1939: prevent deadlock by moving j1939_sk_errqueue()
  xen/netback: don't do grant copy across page boundary
  net: phy: dp83869: fix default value for tx-/rx-internal-delay
  pinctrl: at91-pio4: fix domain name assignment
  powerpc: Don't try to copy PPR for task with NULL pt_regs
  NFSv4: Fix hangs when recovering open state after a server reboot
  ALSA: hda/conexant: Partial revert of a quirk for Lenovo
  ALSA: usb-audio: Fix regression on detection of Roland VS-100
  ALSA: hda/realtek: Add quirks for

[Kernel-packages] [Bug 2023603] Re: Kinetic update: upstream stable patchset 2023-06-12

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

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

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

** Changed in: linux (Ubuntu Kinetic)
 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:
+    upstream stable patchset 2023-06-12
+    from git://git.kernel.org/
  
-upstream stable patchset 2023-06-12
-from git://git.kernel.org/
+ fsverity: don't drop pagecache at end of FS_IOC_ENABLE_VERITY
+ kernel: kcsan: kcsan_test: build without structleak plugin
+ kcsan: avoid passing -g for test
+ ksmbd: don't terminate inactive sessions after a few seconds
+ xfrm: Zero padding when dumping algos and encap
+ ASoC: codecs: tx-macro: Fix for KASAN: slab-out-of-bounds
+ md: avoid signed overflow in slot_store()
+ x86/PVH: obtain VGA console info in Dom0
+ net: hsr: Don't log netdev_err message on unknown prp dst node
+ ALSA: asihpi: check pao in control_message()
+ ALSA: hda/ca0132: fixup buffer overrun at tuning_ctl_set()
+ fbdev: tgafb: Fix potential divide by zero
+ sched_getaffinity: don't assume 'cpumask_size()' is fully initialized
+ fbdev: nvidia: Fix potential divide by zero
+ fbdev: intelfb: Fix potential divide by zero
+ fbdev: lxfb: Fix potential divide by zero
+ fbdev: au1200fb: Fix potential divide by zero
+ tools/power turbostat: Fix /dev/cpu_dma_latency warnings
+ tools/power turbostat: fix decoding of HWP_STATUS
+ tracing: Fix wrong return in kprobe_event_gen_test.c
+ ca8210: Fix unsigned mac_len comparison with zero in ca8210_skb_tx()
+ mips: bmips: BCM6358: disable RAC flush for TP1
+ ALSA: usb-audio: Fix recursive locking at XRUN during syncing
+ platform/x86: think-lmi: add missing type attribute
+ platform/x86: think-lmi: use correct possible_values delimiters
+ platform/x86: think-lmi: only display possible_values if available
+ platform/x86: think-lmi: Add possible_values for ThinkStation
+ mtd: rawnand: meson: invalidate cache on polling ECC bit
+ SUNRPC: fix shutdown of NFS TCP client socket
+ sfc: ef10: don't overwrite offload features at NIC reset
+ scsi: megaraid_sas: Fix crash after a double completion
+ scsi: mpt3sas: Don't print sense pool info twice
+ ptp_qoriq: fix memory leak in probe()
+ net: dsa: microchip: ksz8863_smi: fix bulk access
+ r8169: fix RTL8168H and RTL8107E rx crc error
+ regulator: Handle deferred clk
+ net/net_failover: fix txq exceeding warning
+ net: stmmac: don't reject VLANs when IFF_PROMISC is set
+ drm/i915/tc: Fix the ICL PHY ownership check in TC-cold state
+ platform/x86/intel/pmc: Alder Lake PCH slp_s0_residency fix
+ can: bcm: bcm_tx_setup(): fix KMSAN uninit-value in vfs_write
+ s390/vfio-ap: fix memory leak in vfio_ap device driver
+ loop: LOOP_CONFIGURE: send uevents for partitions
+ net: mvpp2: classifier flow fix fragmentation flags
+ net: mvpp2: parser fix QinQ
+ net: mvpp2: parser fix PPPoE
+ smsc911x: avoid PHY being resumed when interface is not up
+ ice: add profile conflict check for AVF FDIR
+ ice: fix invalid check for empty list in ice_sched_assoc_vsi_to_agg()
+ ALSA: ymfpci: Create card with device-managed snd_devm_card_new()
+ ALSA: ymfpci: Fix BUG_ON in probe function
+ net: ipa: compute DMA pool size properly
+ i40e: fix registers dump after run ethtool adapter self test
+ bnxt_en: Fix reporting of test result in ethtool selftest
+ bnxt_en: Fix typo in PCI id to device description string mapping
+ bnxt_en: Add missing 200G link speed reporting
+ net: dsa: mv88e6xxx: Enable IGMP snooping on user ports only
+ net: ethernet: mtk_eth_soc: fix flow block refcounting logic
+ pinctrl: ocelot: Fix alt mode for ocelot
+ iommu/vt-d: Allow zero SAGAW if second-stage not supported
+ Input: alps - fix compatibility with -funsigned-char
+ Input: focaltech - use explicitly signed char type
+ cifs: prevent infinite recursion in CIFSGetDFSRefer()
+ cifs: fix DFS traversal oops without CONFIG_CIFS_DFS_UPCALL
+ Input: goodix - add Lenovo Yoga Book X90F to nine_bytes_report

[Kernel-packages] [Bug 2023603] [NEW] Kinetic update: upstream stable patchset 2023-06-12

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-06-12
   from git://git.kernel.org/

fsverity: don't drop pagecache at end of FS_IOC_ENABLE_VERITY
kernel: kcsan: kcsan_test: build without structleak plugin
kcsan: avoid passing -g for test
ksmbd: don't terminate inactive sessions after a few seconds
xfrm: Zero padding when dumping algos and encap
ASoC: codecs: tx-macro: Fix for KASAN: slab-out-of-bounds
md: avoid signed overflow in slot_store()
x86/PVH: obtain VGA console info in Dom0
net: hsr: Don't log netdev_err message on unknown prp dst node
ALSA: asihpi: check pao in control_message()
ALSA: hda/ca0132: fixup buffer overrun at tuning_ctl_set()
fbdev: tgafb: Fix potential divide by zero
sched_getaffinity: don't assume 'cpumask_size()' is fully initialized
fbdev: nvidia: Fix potential divide by zero
fbdev: intelfb: Fix potential divide by zero
fbdev: lxfb: Fix potential divide by zero
fbdev: au1200fb: Fix potential divide by zero
tools/power turbostat: Fix /dev/cpu_dma_latency warnings
tools/power turbostat: fix decoding of HWP_STATUS
tracing: Fix wrong return in kprobe_event_gen_test.c
ca8210: Fix unsigned mac_len comparison with zero in ca8210_skb_tx()
mips: bmips: BCM6358: disable RAC flush for TP1
ALSA: usb-audio: Fix recursive locking at XRUN during syncing
platform/x86: think-lmi: add missing type attribute
platform/x86: think-lmi: use correct possible_values delimiters
platform/x86: think-lmi: only display possible_values if available
platform/x86: think-lmi: Add possible_values for ThinkStation
mtd: rawnand: meson: invalidate cache on polling ECC bit
SUNRPC: fix shutdown of NFS TCP client socket
sfc: ef10: don't overwrite offload features at NIC reset
scsi: megaraid_sas: Fix crash after a double completion
scsi: mpt3sas: Don't print sense pool info twice
ptp_qoriq: fix memory leak in probe()
net: dsa: microchip: ksz8863_smi: fix bulk access
r8169: fix RTL8168H and RTL8107E rx crc error
regulator: Handle deferred clk
net/net_failover: fix txq exceeding warning
net: stmmac: don't reject VLANs when IFF_PROMISC is set
drm/i915/tc: Fix the ICL PHY ownership check in TC-cold state
platform/x86/intel/pmc: Alder Lake PCH slp_s0_residency fix
can: bcm: bcm_tx_setup(): fix KMSAN uninit-value in vfs_write
s390/vfio-ap: fix memory leak in vfio_ap device driver
loop: LOOP_CONFIGURE: send uevents for partitions
net: mvpp2: classifier flow fix fragmentation flags
net: mvpp2: parser fix QinQ
net: mvpp2: parser fix PPPoE
smsc911x: avoid PHY being resumed when interface is not up
ice: add profile conflict check for AVF FDIR
ice: fix invalid check for empty list in ice_sched_assoc_vsi_to_agg()
ALSA: ymfpci: Create card with device-managed snd_devm_card_new()
ALSA: ymfpci: Fix BUG_ON in probe function
net: ipa: compute DMA pool size properly
i40e: fix registers dump after run ethtool adapter self test
bnxt_en: Fix reporting of test result in ethtool selftest
bnxt_en: Fix typo in PCI id to device description string mapping
bnxt_en: Add missing 200G link speed reporting
net: dsa: mv88e6xxx: Enable IGMP snooping on user ports only
net: ethernet: mtk_eth_soc: fix flow block refcounting logic
pinctrl: ocelot: Fix alt mode for ocelot
iommu/vt-d: Allow zero SAGAW if second-stage not supported
Input: alps - fix compatibility with -funsigned-char
Input: focaltech - use explicitly signed char type
cifs: prevent infinite recursion in CIFSGetDFSRefer()
cifs: fix DFS traversal oops without CONFIG_CIFS_DFS_UPCALL
Input: goodix - add Lenovo Yoga Book X90F to nine_bytes_report DMI table
btrfs: fix race between quota disable and quota assign ioctls
btrfs: scan device in non-exclusive mode
zonefs: Always invalidate last cached page on append write
can: j1939: prevent deadlock by moving j1939_sk_errqueue()
xen/netback: don't do grant copy across page boundary
net: phy: dp83869: fix default value for tx-/rx-internal-delay
pinctrl: at91-pio4: fix domain name assignment
powerpc: Don't try to copy PPR for task with NULL pt_regs
NFSv4: Fix hangs when recovering open state after a server reboot
ALSA: hda/conexant: Partial revert of a quirk for Lenovo
ALSA: usb-audio: Fix regression on detection of Roland VS-100
ALSA: hda/realtek: Add quirks for some Clevo laptops
ALSA: hda/realtek: Add quirk for Lenovo ZhaoYang CF4620Z
xtensa: fix KASAN report for show_stack
rcu: Fix rcu_torture_read ftrace event
drm/etnaviv: fix reference leak when mmaping imported buffer
drm/amd/display: Add DSC Support for Synaptics Cascaded MST Hub
KVM: arm64: Disable interrupts while walking userspace PTs
KVM: x86:

[Kernel-packages] [Bug 2007745] Re: [SRU][Jammy] CONFIG_PCI_MESON is not enabled

Thank you @itrue for confirming its enabled. Marking verification done
for both jammy and kinetic.

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

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

Title:
  [SRU][Jammy] CONFIG_PCI_MESON is not enabled

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed

Bug description:
  SRU justification:

  [ Impact ]

  The PCI driver for the amlogic-based Meson platforms
  (CONFIG_PCI_MESON) is not enabled as a module in the kernel
  configuration: https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/focal/tree/debian.master/config/config.common.ubuntu?h=master#n7036

  [ Test Plan ]

  Check if pci_meson.ko is compiled and present in the linux-modules
  package.

  [ Where problems could occur ]

  * Enabling the driver could enable undesired dependencies 
  * Kernel module does not compile and breaks the build

  [ Other Info ]

  This driver is important for systems like the ODROID HC4, which uses a
  PCIE-SATA bridge to provide a storage interface. This system is fully
  supported by the kernel (including a device tree), except for the fact
  that this PCI driver is disabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007745/+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 2008751] Re: [SRU] Backport request for hpwdt from upstream 6.1 to Jammy

>From the comments it seems to have been verified for the 5.15 jammy
kernel. I have build tested when applying and verified the module is
enabled. Will mark both as verification done.

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

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

Title:
  [SRU] Backport request for hpwdt from upstream 6.1 to Jammy

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

Bug description:
  SRU Justification:

  [Impact]

  Please pick up the latest hpwdt from the upstream 6.1 kernel for
  Jammy. This version enables hpwdt on RL300 aarch64.

  [Fix]
  ed835d8171fc watchdog/hpwdt: Include nmi.h only if CONFIG_HPWDT_NMI_DECODING

  891862d5ba11 watchdog/hpwdt: Enable HP_WATCHDOG for ARM64 systems.

  [Test Plan]
  Boot system with the hpwdt enabled on an arm64 system

  [Where Problems Could Occur]

  Regression Risk is Low

  [Other Info]
  Jammy
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008751_hpwdt_1

  Kinetic
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008751_hpwdt_kinetic_1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008751/+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 2023601] [NEW] Focal update: v5.4.240 upstream stable release

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.4.240 upstream stable patchset
   from git://git.kernel.org/

net: tls: fix possible race condition between do_tls_getsockopt_conf() and 
do_tls_setsockopt_conf()
power: supply: da9150: Fix use after free bug in da9150_charger_remove due to 
race condition
iavf: fix inverted Rx hash condition leading to disabled hash
iavf: fix non-tunneled IPv6 UDP packet type and hashing
intel/igbvf: free irq on the error path in igbvf_request_msix()
igbvf: Regard vf reset nack as success
i2c: imx-lpi2c: check only for enabled interrupt flags
scsi: scsi_dh_alua: Fix memleak for 'qdata' in alua_activate()
net: usb: smsc95xx: Limit packet length to skb->len
qed/qed_sriov: guard against NULL derefs from qed_iov_get_vf_info
net: qcom/emac: Fix use after free bug in emac_remove due to race condition
net/ps3_gelic_net: Fix RX sk_buff length
net/ps3_gelic_net: Use dma_mapping_error
keys: Do not cache key in task struct if key is requested from kernel thread
bpf: Adjust insufficient default bpf_jit_limit
net/mlx5: Read the TC mapping of all priorities on ETS query
atm: idt77252: fix kmemleak when rmmod idt77252
erspan: do not use skb_mac_header() in ndo_start_xmit()
net/sonic: use dma_mapping_error() for error check
nvme-tcp: fix nvme_tcp_term_pdu to match spec
hvc/xen: prevent concurrent accesses to the shared ring
net: mdio: thunder: Add missing fwnode_handle_put()
Bluetooth: btqcomsmd: Fix command timeout after setting BD address
platform/chrome: cros_ec_chardev: fix kernel data leak from ioctl
hwmon (it87): Fix voltage scaling for chips with 10.9mV ADCs
scsi: qla2xxx: Perform lockless command completion in abort path
uas: Add US_FL_NO_REPORT_OPCODES for JMicron JMS583Gen 2
thunderbolt: Use const qualifier for `ring_interrupt_index`
riscv: Bump COMMAND_LINE_SIZE value to 1024
ca8210: fix mac_len negative array access
m68k: Only force 030 bus error if PC not in exception table
selftests/bpf: check that modifier resolves after pointer
scsi: target: iscsi: Fix an error message in iscsi_check_key()
scsi: ufs: core: Add soft dependency on governor_simpleondemand
scsi: lpfc: Avoid usage of list iterator variable after loop
net: usb: cdc_mbim: avoid altsetting toggling for Telit FE990
net: usb: qmi_wwan: add Telit 0x1080 composition
sh: sanitize the flags on sigreturn
cifs: empty interface list when server doesn't support query interfaces
scsi: core: Add BLIST_SKIP_VPD_PAGES for SKhynix H28U74301AMR
usb: gadget: u_audio: don't let userspace block driver unbind
fsverity: Remove WQ_UNBOUND from fsverity read workqueue
igb: revert rtnl_lock() that causes deadlock
dm thin: fix deadlock when swapping to thin device
usb: cdns3: Fix issue with using incorrect PCI device function
usb: chipdea: core: fix return -EINVAL if request role is the same with current 
role
usb: chipidea: core: fix possible concurrent when switch role
wifi: mac80211: fix qos on mesh interfaces
nilfs2: fix kernel-infoleak in nilfs_ioctl_wrap_copy()
i2c: xgene-slimpro: Fix out-of-bounds bug in xgene_slimpro_i2c_xfer()
dm stats: check for and propagate alloc_percpu failure
dm crypt: add cond_resched() to dmcrypt_write()
sched/fair: sanitize vruntime of entity being placed
sched/fair: Sanitize vruntime of entity being migrated
tun: avoid double free in tun_free_netdev
ocfs2: fix data corruption after failed write
fsverity: don't drop pagecache at end of FS_IOC_ENABLE_VERITY
bus: imx-weim: fix branch condition evaluates to a garbage value
md: avoid signed overflow in slot_store()
ALSA: asihpi: check pao in control_message()
ALSA: hda/ca0132: fixup buffer overrun at tuning_ctl_set()
fbdev: tgafb: Fix potential divide by zero
sched_getaffinity: don't assume 'cpumask_size()' is fully initialized
fbdev: nvidia: Fix potential divide by zero
fbdev: intelfb: Fix potential divide by zero
fbdev: lxfb: Fix potential divide by zero
fbdev: au1200fb: Fix potential divide by zero
ca8210: Fix unsigned mac_len comparison with zero in ca8210_skb_tx()
dma-mapping: drop the dev argument to arch_sync_dma_for_*
mips: bmips: BCM6358: disable RAC flush for TP1
mtd: rawnand: meson: invalidate cache on polling ECC bit
scsi: megaraid_sas: Fix crash after a double completion
ptp_qoriq: fix memory leak in probe()
regulator: fix spelling mistake "Cant" -> "Can't"
regulator: Handle deferred clk
net/net_failover: fix txq exceeding warning
can: bcm: bcm_tx_setup(): fix KMSAN uninit-value in vfs_write
s390/vfio-ap: fix memory leak in vfio_ap device driver
i40e: fix registers dump after run ethtool adapter self test
bnxt_en: Fix

[Kernel-packages] [Bug 2023600] [NEW] Focal update: v5.4.239 upstream stable release

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.4.239 upstream stable patchset
   from git://git.kernel.org/

Linux 5.4.239
UBUNTU: Upstream stable to v5.4.239

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

** Affects: linux (Ubuntu Focal)
 Importance: Medium
 Assignee: Luke Nowakowski-Krijger (lukenow)
 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 Focal)
   Importance: Undecided
   Status: New

** 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-06-12
+    from git://git.kernel.org/
  
-upstream stable patchset 2023-06-12
-from git://git.kernel.org/
+ Linux 5.4.239
+ UBUNTU: Upstream stable to v5.4.239

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

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Luke Nowakowski-Krijger (lukenow)

** Summary changed:

- Focal update: upstream stable patchset 2023-06-12
+ Focal update: v5.4.239 upstream stable release

** Description changed:

  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-06-12
+    v5.4.239 upstream stable patchset
     from git://git.kernel.org/
  
  Linux 5.4.239
  UBUNTU: Upstream stable to v5.4.239

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

Title:
  Focal update: v5.4.239 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  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:

     v5.4.239 upstream stable patchset
     from git://git.kernel.org/

  Linux 5.4.239
  UBUNTU: Upstream stable to v5.4.239

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023600/+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 2018470] Re: Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1

2023-06-12 Thread Thomas Debesse

Will the patch be dropped if the Nvidia kernel is not tested on AMD
GPUs?

Rebooting the computer affected by the bug will cost me 1 or 2 hours of
work so that's a very high cost for a patch I already marked as
verified.

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

Title:
  Linux 5.19 amdgpu: NULL pointer on GCN2 and invalid load on GCN1

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

Bug description:
  [Impact]
  A regression caused by incomplete stable backports

  [Fix]

  commit 8273b4048664fff356fd10059033f0e2f5a422a1
  Author: Arunpravin Paneer Selvam 
  Date:   Tue Oct 18 07:08:38 2022 -0700

  drm/amdgpu: Fix for BO move issue

  [Test case]

  Install the update, check that display works again on amdgpu

  --

  The day I updated from Ubuntu 22.04 to 22.10 some months ago, I had to
  stick on Linux 5.15 because 5.19 was not working with my computer. The
  last two days I spent time to find a way to run Linux 5.19, and found
  one version working: 5.19.0-23.

  Here are the versions I tested:

  - 5.19.0-23
  - 5.19.0-29
  - 5.19.0-31
  - 5.19.0-42

  In that list, only Linux 5.19.0-23 is working with that computer.

  There may be other versions that work I have not tested, but basically
  the breakages occurred after 5.19.0-23.

  I face two problems, let's talk about the first one, the graphic one
  still present in 5.19.0-42. It starts to occurs with 5.19.0-31
  (5.19.0-29 is not affected): graphic breaks at the moment it should
  switch from low resolution display to high resolution display at the
  very beginning of startup. The computer is not completely broken, but
  the graphic is dead. X11 cannot start, trying to use the framebuffer,
  meaning the amdgpu driver is not functional).

  The second bug is the one I get with the 5.19.0-29 version. Linux
  5.19.0-29 doesn't experience the graphic bug but has another issue
  that makes the computer unusable: some CPU got locked, and some btrfs
  process runs at 100% CPU, syncing never ends, even preventing to
  reboot. This bug is less important because I don't reproduce it on
  version 5.19.0-42, so if 5.19.0-42 fixes the graphic all will be fine.

  I have not updated to Ubuntu 23.04 yet because I'm afraid of newer
  kernels from it would leave my computer totally unusable, I have run
  Ubuntu 22.10 with Ubuntu 22.04's 5.15 kernel until today because of
  that fear.

  It actually took me two work days to test various combinations to boot
  the computer so I'm sticking on 5.19.0-29 for now, and I have limited
  time to test other options. I also tried various BIOS options, and
  also upgraded the BIOS…, and since that ThreadRipper PRO computer has
  very slow booting BIOS, trying various configurations or software
  versions that requires a reboot quickly eats-up whole hours.

  The attached logs may have traces of dkim modules like amdgpu-pro, but
  the first time I experienced the bug I had none of them. I reproduced
  the bug on a 5.19.0-42 kernel free of amdgpu-pro yesterday. I'm simply
  opening the ticket from my working environment, and I decided to not
  spend one more hour just to uninstall amdgpu-pro and reboot only to do
  that ticket.

  Here are some details on the hardware:

  - MOBO: Gigabyte WRX80-SU8-IPMI rev. 1.0 (BIOS version F5, also named 
WRX80PRO-F1 in dmidecode, dated 08/04/2022) 
https://www.gigabyte.com/Motherboard/WRX80-SU8-IPMI-rev-10
  - RAM: 8× Kingston Server Premier 32GB DDR4 3200 MHz ECC CL22 2Rx8 PC4-25600 
KSM32ED8/32ME 16Gbit Micron E
  - CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores (Castle Peak, Zen 2)
  - GPU: AMD Radeon R9 390X (Hawaii/Grenada, GCN2, amdgpu driver)
  - GPU: AMD Radeon R7 240 (Oland, GCN1, amdgpu driver)
  - GPU: ASPEED graphic Family rev 41

  The ASPEED graphic is a small card integrated in the motherboard and
  part of the BMC, I cannot remove it. This may participate in the
  trouble.

  When the graphic works (Linux 5.19.0-23, Linux 5.19.0-29), the boot is
  displayed on all AMD and ASPEED graphic output, then at the moment the
  graphic switches from low resolution to high resolution, the ASPEED
  graphic goes off and the display continue on AMD cards.

  When the graphic doesn't work (5.19.0-31, 5.19.0-42), the boot is
  displayed on all AMD and ASPEED graphic output, then at the moment the
  graphic switches from low resolution to high resolution, the AMD cards
  display garbage but the display continue on the ASPEED card. The
  ASPEED card is a very basic integrated card without hardware
  acceleration and featuring only one VGA output so that's unusable. As
  an additional information I know X11 never start on the ASPEED if
  there are discrete cards plugged in (tested last year).

  So right now that computer is sticking on Linux 5.19.0-23

[Kernel-packages] [Bug 2023337] Re: Kinetic update: upstream stable patchset 2023-06-08

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

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

Title:
  Kinetic update: upstream stable patchset 2023-06-08

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  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:

     upstream stable patchset 2023-06-08

  Ported from the following upstream stable releases:
  v5.15.103, v6.1.20

     from git://git.kernel.org/

  fs: prevent out-of-bounds array speculation when closing a file descriptor
  btrfs: fix percent calculation for bg reclaim message
  perf inject: Fix --buildid-all not to eat up MMAP2
  fork: allow CLONE_NEWTIME in clone3 flags
  x86/CPU/AMD: Disable XSAVES on AMD family 0x17
  drm/amdgpu: fix error checking in amdgpu_read_mm_registers for soc15
  drm/connector: print max_requested_bpc in state debugfs
  staging: rtl8723bs: Pass correct parameters to cfg80211_get_bss()
  ext4: fix cgroup writeback accounting with fs-layer encryption
  ext4: fix RENAME_WHITEOUT handling for inline directories
  ext4: fix another off-by-one fsmap error on 1k block filesystems
  ext4: move where set the MAY_INLINE_DATA flag is set
  ext4: fix WARNING in ext4_update_inline_data
  ext4: zero i_disksize when initializing the bootloader inode
  nfc: change order inside nfc_se_io error path
  KVM: Register /dev/kvm as the _very_ last thing during initialization
  fs: dlm: fix log of lowcomms vs midcomms
  fs: dlm: add midcomms init/start functions
  fs: dlm: start midcomms before scand
  udf: Fix off-by-one error when discarding preallocation
  f2fs: retry to update the inode page given data corruption
  ipmi:ssif: Increase the message retry time
  ipmi:ssif: Add a timer between request retries
  brd: mark as nowait compatible
  RISC-V: Avoid dereferening NULL regs in die()
  riscv: Add header include guards to insn.h
  scsi: core: Remove the /proc/scsi/${proc_name} directory earlier
  regulator: core: Fix off-on-delay-us for always-on/boot-on regulators
  regulator: core: Use ktime_get_boottime() to determine how long a regulator 
was off
  ext4: Fix possible corruption when moving a directory
  drm/nouveau/kms/nv50-: remove unused functions
  drm/nouveau/kms/nv50: fix nv50_wndw_new_ prototype
  drm/msm: Fix potential invalid ptr free
  drm/msm/a5xx: fix setting of the CP_PREEMPT_ENABLE_LOCAL register
  drm/msm/a5xx: fix highest bank bit for a530
  drm/msm/a5xx: fix the emptyness check in the preempt code
  drm/msm/a5xx: fix context faults during ring switch
  bgmac: fix *initial* chip reset to support BCM5358
  nfc: fdp: add null check of devm_kmalloc_array in 
fdp_nci_i2c_read_device_properties
  powerpc: dts: t1040rdb: fix compatible string for Rev A boards
  ila: do not generate empty messages in ila_xlat_nl_cmd_get_mapping()
  selftests: nft_nat: ensuring the listening side is up before starting the 
client
  perf stat: Fix counting when initial delay configured
  net: lan78xx: fix accessing the LAN7800's internal phy specific registers 
from the MAC driver
  net: caif: Fix use-after-free in cfusbl_device_notify()
  ice: copy last block omitted in ice_get_module_eeprom()
  bpf, sockmap: Fix an infinite loop error when len is 0 in 
tcp_bpf_recvmsg_parser()
  drm/msm/dpu: fix len of sc7180 ctl blocks
  net: stmmac: add to set device wake up flag when stmmac init phy
  net: phylib: get rid of unnecessary locking
  bnxt_en: Avoid order-5 memory allocation for TPA data
  netfilter: tproxy: fix deadlock due to missing BH disable
  btf: fix resolving BTF_KIND_VAR after ARRAY, STRUCT, UNION, PTR
  net: phy: smsc: fix link up detection in forced irq mode
  net: ethernet: mtk_eth_soc: fix RX data corruption issue
  scsi: megaraid_sas: Update max supported LD IDs to 240
  platform: x86: MLX_PLATFORM: select REGMAP instead of depending on it
  net/smc: fix fallback failed while sendmsg with fastopen
  octeontx2-af: Unlock contexts in the queue context cache in case of fault 
detection
  SUNRPC: Fix a server shutdown leak
  net: dsa: mt7530: permit port 5 to work without port 6 on MT7621 SoC
  af_unix: fix struct pid leaks in OOB support
  riscv: Use READ_ONCE_NOCHECK in imprecise unwinding stack mode
  RISC-V: Don't check text_mutex during stop_machine
  ext4: Fix deadlock during directory rename
  iommu/amd: Add PCI segment support for

[Kernel-packages] [Bug 2023426] Re: Kinetic update: upstream stable patchset 2023-06-09

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

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

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

Title:
  Kinetic update: upstream stable patchset 2023-06-09

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  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:

     upstream stable patchset 2023-06-09

  Ported from the following upstream stable releases:
  v5.15.104, v6.1.21
  v5.15.105, v6.1.22

     from git://git.kernel.org/

  xfrm: Allow transport-mode states with AF_UNSPEC selector
  drm/panfrost: Don't sync rpm suspension after mmu flushing
  cifs: Move the in_send statistic to __smb_send_rqst()
  drm/meson: fix 1px pink line on GXM when scaling video overlay
  clk: HI655X: select REGMAP instead of depending on it
  docs: Correct missing "d_" prefix for dentry_operations member 
d_weak_revalidate
  scsi: mpt3sas: Fix NULL pointer access in mpt3sas_transport_port_add()
  ALSA: hda: Match only Intel devices with CONTROLLER_IN_GPU()
  netfilter: nft_nat: correct length for loading protocol registers
  netfilter: nft_masq: correct length for loading protocol registers
  netfilter: nft_redir: correct length for loading protocol registers
  netfilter: nft_redir: correct value of inet type `.maxattrs`
  scsi: core: Fix a procfs host directory removal regression
  tcp: tcp_make_synack() can be called from process context
  nfc: pn533: initialize struct pn533_out_arg properly
  ipvlan: Make skb->skb_iif track skb->dev for l3s mode
  i40e: Fix kernel crash during reboot when adapter is in recovery mode
  vdpa_sim: not reset state in vdpasim_queue_ready
  vdpa_sim: set last_used_idx as last_avail_idx in vdpasim_queue_ready
  PCI: s390: Fix use-after-free of PCI resources with per-function hotplug
  drm/i915/display: clean up comments
  net/smc: fix NULL sndbuf_desc in smc_cdc_tx_handler()
  qed/qed_dev: guard against a possible division by zero
  net: dsa: mt7530: remove now incorrect comment regarding port 5
  net: dsa: mt7530: set PLL frequency and trgmii only when trgmii is used
  loop: Fix use-after-free issues
  net: tunnels: annotate lockless accesses to dev->needed_headroom
  net: phy: smsc: bail out in lan87xx_read_status if genphy_read_status fails
  nfc: st-nci: Fix use after free bug in ndlc_remove due to race condition
  net/smc: fix deadlock triggered by cancel_delayed_work_syn()
  net: usb: smsc75xx: Limit packet length to skb->len
  drm/bridge: Fix returned array size name for atomic_get_input_bus_fmts kdoc
  block: null_blk: Fix handling of fake timeout request
  nvme: fix handling single range discard request
  nvmet: avoid potential UAF in nvmet_req_complete()
  block: sunvdc: add check for mdesc_grab() returning NULL
  ice: xsk: disable txq irq before flushing hw
  net: dsa: mv88e6xxx: fix max_mtu of 1492 on 6165, 6191, 6220, 6250, 6290
  ravb: avoid PHY being resumed when interface is not up
  sh_eth: avoid PHY being resumed when interface is not up
  ipv4: Fix incorrect table ID in IOCTL path
  net: usb: smsc75xx: Move packet length check to prevent kernel panic in 
skb_pull
  net/iucv: Fix size of interrupt data
  qed/qed_mng_tlv: correctly zero out ->min instead of ->hour
  ethernet: sun: add check for the mdesc_grab()
  bonding: restore IFF_MASTER/SLAVE flags on bond enslave ether type change
  bonding: restore bond's IFF_SLAVE flag if a non-eth dev enslave fails
  hwmon: (adt7475) Display smoothing attributes in correct order
  hwmon: (adt7475) Fix masking of hysteresis registers
  hwmon: (xgene) Fix use after free bug in xgene_hwmon_remove due to race 
condition
  hwmon: (ina3221) return prober error code
  hwmon: (ucd90320) Add minimum delay between bus accesses
  hwmon: tmp512: drop of_match_ptr for ID table
  kconfig: Update config changed flag before calling callback
  hwmon: (adm1266) Set `can_sleep` flag for GPIO chip
  hwmon: (ltc2992) Set `can_sleep` flag for GPIO chip
  media: m5mols: fix off-by-one loop termination error
  mmc: atmel-mci: fix race between stop command and start of next command
  jffs2: correct logic when creating a hole in jffs2_write_begin
  ext4: fail ext4_iget if special inode unallocated
  ext4: update s_journal_inum if it changes after journal replay
  ext4: fix task hung in

[Kernel-packages] [Bug 2019240] Re: Pull-request to address a number of enablement issues for Orin platforms

This bug was fixed in the package linux-nvidia-tegra - 5.15.0-1014.14

---
linux-nvidia-tegra (5.15.0-1014.14) jammy; urgency=medium

  * jammy/linux-nvidia-tegra: 5.15.0-1014.14 -proposed tracker (LP:
#2021855)

  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts

  * Pull-request to address a number of enablement issues for Orin platforms
(LP: #2019240)
- SAUCE: tegra-epl: Send state notification fsi
- Documentation: Add HTE subsystem guide
- drivers: Add hardware timestamp engine (HTE) subsystem
- hte: Add Tegra194 HTE kernel provider
- dt-bindings: Add HTE bindings
- gpiolib: Add HTE support
- gpio: tegra186: Add HTE support
- gpiolib: cdev: Add hardware timestamp clock type
- tools: gpio: Add new hardware clock type
- hte: Add Tegra HTE test driver
- MAINTAINERS: Add HTE Subsystem
- hte: Remove unused including 
- hte: Fix possible use-after-free in tegra_hte_test_remove()
- hte: Fix off by one in hte_push_ts_ns()
- hte: Uninitialized variable in hte_ts_get()
- dt-bindings: Renamed hte directory to timestamp
- dt-bindings: timestamp: Correct id path
- docs: Move the HTE documentation to driver-api/
- gpiolib: cdev: Fix kernel doc for struct line
- arm64: defconfig: Enable HTE config
- arm64: tegra: Enable GTE nodes
- SAUCE: locking/rtmutex: use cmpxchg in mark_rt_mutex_waiters
- SAUCE: net: fix ubsan warning network layer
- SAUCE: defconfig: tegra: Enable PANIC_ON_OOPS
- SAUCE: mmc: core: separate mmc_test and mmc driver
- SAUCE: drivers: net: phy: Multiple fixes for stability
- SAUCE: arm64: defconfig: enable minimum config to support Docker
- SAUCE: usb: xhci-tegra: don't assign port role by default
- SAUCE: phy: tegra: xusb: fix use-after-free issue
- SAUCE: arm64/configs: enable spi controller driver
- SAUCE: arm64: config: enable spi controller driver
- SAUCE: arm64: configs: Enable ARM64_PTR_AUTH
- SAUCE: spi: add "tegra-spidev" compatible string.
- dma-buf: defer unmapping for dma shared buffer till free
- SAUCE: iommu: arm-smmu: io-pgtable: Add dma_sync API
- SAUCE: usb: xhci: tegra: add shutdown routine
- SAUCE: gpio: timestamping: program timestamp bit
- SAUCE: net: phy: fix data corruption

  * Miscellaneous Ubuntu changes
- [Config] CONFIG_HTE is not set

  [ Ubuntu: 5.15.0-1039.42 ]

  * jammy/linux-realtime: 5.15.0-1039.42 -proposed tracker (LP: #2019627)
  * jammy/linux: 5.15.0-73.80 -proposed tracker (LP: #2019647)
  * CVE-2023-32233
- netfilter: nf_tables: deactivate anonymous set from preparation phase
  * CVE-2023-2612
- SAUCE: shiftfs: prevent lock unbalance in shiftfs_create_object()
  * CVE-2023-31436
- net: sched: sch_qfq: prevent slab-out-of-bounds in qfq_activate_agg
  * CVE-2023-1380
- wifi: brcmfmac: slab-out-of-bounds read in brcmf_get_assoc_ies()
  * CVE-2023-30456
- KVM: nVMX: add missing consistency checks for CR0 and CR4
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts

 -- Brad Figg   Tue, 30 May 2023 10:03:05 -0700

** Changed in: linux-nvidia-tegra (Ubuntu)
   Status: New => Fix Released

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

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

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

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

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

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

Title:
  Pull-request to address a number of enablement issues for Orin
  platforms

Status in linux-nvidia-tegra package in Ubuntu:
  Fix Released

Bug description:
  [impact]
  This patch set addresses a wide variety of bugs and missing features for 
NVIDIA Orin platforms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2019240/+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 1993328] Re: nvidia-graphics-drivers-418-server FTBFS with linux 5.19

This bug was fixed in the package nvidia-graphics-drivers-418-server -
418.226.00-0ubuntu5

---
nvidia-graphics-drivers-418-server (418.226.00-0ubuntu5) lunar; urgency=medium

  [ Andrea Righi ]
  * debian/dkms_nvidia/patches/buildfix_kernel_5.19.patch,
debian/templates/dkms_nvidia.conf.in: apply buildfix_kernel_5.19.patch:
- Add support for Linux 5.19 (LP: #1993328).

 -- Alberto Milone   Mon, 23 Jan 2023
11:31:36 +

** Changed in: nvidia-graphics-drivers-418-server (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  nvidia-graphics-drivers-418-server FTBFS with linux 5.19

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

   * nvidia-graphics-drivers-418-server reached its EOL, however it is
  the last driver supporting certain GPU families. For this reason, to
  give users some time to transition to newer GPUs, we would like to
  move the driver to multiverse for now.

   * The driver should also be patched to be compatible with Kinetic and
  Jammy's kernels.

  
  [ Test Plan ]

   * Install Linux 5.19:

 - In Jammy:
   sudo apt install linux-image-unsigned-5.19.0-30-generic  
linux-image-generic-hwe-22.04-edge linux-headers-5.19.0-30-generic

 - In Kinetic:
   sudo apt install linux-generic

  * Install the nvidia driver from -proposed:
sudo apt install nvidia-driver-418-server

  * Make sure that the driver builds correctly:
dkms status

  
  [ Where problems could occur ]

   * In its current state, the driver does not build against Kinetic's kernel,
 hence no regression is possible, in this sense.

   * As for Jammy, the changes introduced by the patch are well contained,
 and only apply when "LINUX_VERSION_CODE >= KERNEL_VERSION(5, 18, 0)".
 When using linux-image-generic-hwe-22.04-edge, this will be the first
 case of the 418 driver working with it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1993328/+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 2023594] [NEW] Case [Azure] Fix VM crash/hang issues due to fast VF add/remove events

2023-06-12 Thread Tim Gardner

Public bug reported:

SRU Justification

[Impact]

A Linux guest on Hyper-V/Azure can occasionally crash during early Linux kernel 
boot due to a strange host behavior:
1. The host assigns a VF to the guest;
2. The host immediately unassigns the VF from the guest; //Dexuan: due to some 
race conditions bug in Linux vPCI driver, Linux can crash.
3. The host assigns the VF to the guest again.

Starting late 2022 (around Nov 2022), Linux guests on Azure started to
crash more frequently due to a host side update at that time: a new
host/hypervisor feature of handling "correctable memory errors" can
cause a lot of successive VF remove/add events, so the race conditions
bug in Linux vPCI driver can surface much more easily. The Hyper-V team
is implementing a batching mechanism so that the guest will get much
less VF remove/add events (ETA: June 2023), but meanwhile we should also
get the Linux race condition bugs fixed so that Linux guests won't crash
even if it receives the successive VF remove/add events.

[Test Plan]

Microsoft tested

[Regression potential]

PCI devices may not get registered, or VMs may crash.

[Other Info]

SF: #00349076

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

** Affects: linux-azure (Ubuntu Focal)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

** Affects: linux-azure (Ubuntu Jammy)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

** Affects: linux-azure (Ubuntu Lunar)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

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

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

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

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

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

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

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

** Changed in: linux (Ubuntu Lunar)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
   Case [Azure] Fix VM crash/hang issues due to fast VF add/remove
  events

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Focal:
  In Progress
Status in linux-azure source package in Jammy:
  In Progress
Status in linux-azure source package in Lunar:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  A Linux guest on Hyper-V/Azure can occasionally crash during early Linux 
kernel boot due to a strange host behavior:
  1. The host assigns a VF to the guest;
  2. The host immediately unassigns the VF from the guest; //Dexuan: due to 
some race conditions bug in Linux vPCI driver, Linux can crash.
  3. The host assigns the VF to the guest again.

  Starting late 2022 (around Nov 2022), Linux guests on Azure started to
  crash more frequently due to a host side update at that time: a new
  host/hypervisor feature of handling "correctable memory errors" can
  cause a lot of successive VF remove/add events, so the race conditions
  bug in Linux vPCI driver can surface much more easily. The Hyper-V
  team is implementing a batching mechanism so that the guest will get
  much less VF remove/add events (ETA: June 2023), but meanwhile we
  should also get the Linux race condition bugs fixed so that Linux
  guests won't crash even if it receives the successive VF remove/add
  events.

  [Test Plan]

  Microsoft tested

  [Regression potential]

  PCI devices may not get registered, or VMs may crash.

  [Other Info]

  SF: #00349076

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2023594/+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 2023220] Re: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled

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

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

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

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

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

Title:
  Some INVLPG implementations can leave Global translations unflushed
  when PCIDs are enabled

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Incomplete
Status in linux-oem-6.1 source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Incomplete
Status in linux-oem-6.1 source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux-oem-6.1 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-6.1 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  New
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
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:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  When PCIDs are enabled on Alder Lake and Raptor Lake, INVLPG will not flush 
the global TLB entries. This can lead to info leak or undefined behavior.

  [Mitigation]
  Boot with nopcid on affected systems.

  [Test case]
  There is no particular test case.

  [Potential regressions]
  This affects performance on the affected systems. TLB behavior could also be 
affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023220/+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 2019250] Re: power management controller driver fix for Alder lake and raptor lake

Commited as an upstream stable update BugLink:
https://bugs.launchpad.net/bugs/2023233

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

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

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

Title:
  power management controller driver fix for Alder lake and raptor lake

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

Bug description:
  Reported in https://bugs.launchpad.net/bugs/1996592

  SRU Justification:

  
  [Impact]
  On Alder Lake and Raptor lake platforms there is power management driver 
issue in the 5.15 jammy kernel.

  [Fix]
  Lore Link:
  
https://lore.kernel.org/all/20230320212029.3154407-1-david.e@linux.intel.com/

  This is fixed by commit:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/platform/x86/intel/pmc/core.c?h=v6.3-rc7=fb5755100a0a5aa5957bdb204fd1e249684557fc

  [Test Plan]
  I have tested the changes on ADL-S and ADL-P platforms.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp-5.15/5.15.0.1036.44~20.04.1)

All autopkgtests for the newly accepted linux-meta-gcp-5.15 
(5.15.0.1036.44~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/245.4-4ubuntu3.21 (amd64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2023585] [NEW] GPU has fallen off the bus

2023-06-12 Thread Umayr Saghir

Public bug reported:

When playing Assassins Creed Unity through Steam, the game will run fine
for a short period and then pretty quickly in my experience the screen
will go blank, lights on the GPU will turn off and GPU fans will spin at
max RPM.

I checked the dmesg logs from that session and saw at the bottom:

```
Jun 12 19:25:09 pikachu kernel: NVRM: GPU at PCI::0b:00: 
GPU-f888943b-327b-82af-03dd-7c4213dc4788
Jun 12 19:25:09 pikachu kernel: NVRM: Xid (PCI::0b:00): 79, 
pid='', name=, GPU has fallen off the bus.
Jun 12 19:25:09 pikachu kernel: NVRM: GPU :0b:00.0: GPU has fallen off the 
bus.
Jun 12 19:25:09 pikachu kernel: nvidia-gpu :0b:00.3: Unable to change power 
state from D3hot to D0, device inaccessible
Jun 12 19:25:09 pikachu kernel: xhci_hcd :0b:00.2: Unable to change power 
state from D3hot to D0, device inaccessible
Jun 12 19:25:09 pikachu kernel: xhci_hcd :0b:00.2: Unable to change power 
state from D3cold to D0, device inaccessible
Jun 12 19:25:09 pikachu kernel: xhci_hcd :0b:00.2: Controller not ready at 
resume -19
Jun 12 19:25:09 pikachu kernel: xhci_hcd :0b:00.2: PCI post-resume error 
-19!
Jun 12 19:25:09 pikachu kernel: xhci_hcd :0b:00.2: HC died; cleaning up
Jun 12 19:25:09 pikachu kernel: audit: type=1400 audit(1686594309.980:429): 
apparmor="DENIED" operation="open" class="file" 
profile="snap.keepassxc.keepassxc" name="/sys/devices/pci00>
Jun 12 19:25:10 pikachu kernel: nvidia-gpu :0b:00.3: i2c timeout error 

Jun 12 19:25:10 pikachu kernel: ucsi_ccg 0-0008: i2c_transfer failed -110
```

Further up in the logs I also see the following (in case it's related):

```
[drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0b00] 
Failed to grab modeset ownership
```

I am using an RTX 2080Ti on driver version 525.105.17.

I have attached the full dmesg log

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: nvidia-driver-525 525.105.17-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 12 19:35:37 2023
InstallationDate: Installed on 2022-12-06 (187 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
SourcePackage: nvidia-graphics-drivers-525
UpgradeStatus: Upgraded to lunar on 2023-04-21 (51 days ago)

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


** Tags: amd64 apport-bug lunar

** Attachment added: "crash.log"
   https://bugs.launchpad.net/bugs/2023585/+attachment/5679353/+files/crash.log

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

Title:
  GPU has fallen off the bus

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

Bug description:
  When playing Assassins Creed Unity through Steam, the game will run
  fine for a short period and then pretty quickly in my experience the
  screen will go blank, lights on the GPU will turn off and GPU fans
  will spin at max RPM.

  I checked the dmesg logs from that session and saw at the bottom:

  ```
  Jun 12 19:25:09 pikachu kernel: NVRM: GPU at PCI::0b:00: 
GPU-f888943b-327b-82af-03dd-7c4213dc4788
  Jun 12 19:25:09 pikachu kernel: NVRM: Xid (PCI::0b:00): 79, 
pid='', name=, GPU has fallen off the bus.
  Jun 12 19:25:09 pikachu kernel: NVRM: GPU :0b:00.0: GPU has fallen off 
the bus.
  Jun 12 19:25:09 pikachu kernel: nvidia-gpu :0b:00.3: Unable to change 
power state from D3hot to D0, device inaccessible
  Jun 12 19:25:09 pikachu kernel: xhci_hcd :0b:00.2: Unable to change power 
state from D3hot to D0, device inaccessible
  Jun 12 19:25:09 pikachu kernel: xhci_hcd :0b:00.2: Unable to change power 
state from D3cold to D0, device inaccessible
  Jun 12 19:25:09 pikachu kernel: xhci_hcd :0b:00.2: Controller not ready 
at resume -19
  Jun 12 19:25:09 pikachu kernel: xhci_hcd :0b:00.2: PCI post-resume error 
-19!
  Jun 12 19:25:09 pikachu kernel: xhci_hcd :0b:00.2: HC died; cleaning up
  Jun 12 19:25:09 pikachu kernel: audit: type=1400 audit(1686594309.980:429): 
apparmor="DENIED" operation="open" class="file" 
profile="snap.keepassxc.keepassxc" name="/sys/devices/pci00>
  Jun 12 19:25:10 pikachu kernel: nvidia-gpu :0b:00.3: i2c timeout error 

  Jun 12 19:25:10 pikachu kernel: ucsi_ccg 0-0008: i2c_transfer failed -110
  ```

  Further up in the logs I also see the following (in case it's
  related):

  ```
  [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0b00] 
Failed to grab modeset ownership
  ```

  I am using an RTX 2080Ti on driver version 525.105.17.

  I have attached the full dmesg log

  ProblemType: Bug

[Kernel-packages] [Bug 2023396] Re: After an Ubuntu Update, the WiFi was not working. When running the sudo lshw -C network in a terminal window, the statement '*-network UNCLAIMED ' was presented for

2023-06-12 Thread Jon Coomber

The latest update (5.19.0-45-generic) corrected my wifi connectivity
issue.  Thank you!

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

Title:
  After an Ubuntu Update, the WiFi was not working. When running the
  sudo lshw -C network in a terminal window, the  statement '*-network
  UNCLAIMED ' was presented for the network controller (Broadcom
  BCM43142 802.11b/g/n)

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Release information shown after running 'lsb_release -a'
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04
  Codename: jammy


  The printout from the terminal window after running lshw -C network
*-network UNCLAIMED   
 description: Network controller
 product: BCM43142 802.11b/g/n
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0
 bus info: pci@:06:00.0
 version: 01
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress cap_list
 configuration: latency=0
 resources: memory:aa10-aa107fff
*-network
 description: Ethernet interface
 product: RTL810xE PCI Express Fast Ethernet controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:07:00.0
 logical name: enp7s0
 version: 07
 serial: 20:47:47:49:34:06
 capacity: 100Mbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=5.19.0-44-generic firmware=rtl8106e-1_0.0.1 06/29/12 latency=0 
link=no multicast=yes port=twisted pair
 resources: irq:19 ioport:3000(size=256) memory:aa00-aa000fff 
memory:c000-c0003fff

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-firmware 20220329.git681281e4-0ubuntu3.14
  ProcVersionSignature: Ubuntu 5.19.0-44.45~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jon2489 F pulseaudio
   /dev/snd/controlC0:  jon2489 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  9 06:55:51 2023
  Dependencies: firmware-sof-signed 2.0-1ubuntu4.1
  InstallationDate: Installed on 2022-08-23 (289 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  IwConfig:
   lono wireless extensions.
   
   enp7s0no wireless extensions.
  MachineType: Dell Inc. Inspiron 3543
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-44-generic 
root=UUID=ac729c56-ab63-4579-9c28-60763aa3e9f3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-44-generic N/A
   linux-backports-modules-5.19.0-44-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.14
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2019
  dmi.bios.release: 65.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0M9V4C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd09/12/2019:br65.11:svnDellInc.:pnInspiron3543:pvrA11:rvnDellInc.:rn0M9V4C:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:sku0654:
  dmi.product.name: Inspiron 3543
  dmi.product.sku: 0654
  dmi.product.version: A11
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023396/+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 2023577] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 2023577

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

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

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

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

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

Title:
  cls_flower: off-by-one in fl_set_geneve_opt

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete
Status in linux source package in Jammy:
  Incomplete
Status in linux source package in Kinetic:
  Incomplete
Status in linux source package in Lunar:
  Incomplete

Bug description:
  [Impact]
  An unprivileged user may cause an out-of-bounds write by setting up geneve 
options on the flower classifier.

  [Test case]
  https://seclists.org/oss-sec/2023/q2/219

  [Potential regression]
  Users setting up geneve options on the flower tc classifier can be affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023577/+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 2023577] [NEW] cls_flower: off-by-one in fl_set_geneve_opt

2023-06-12 Thread Thadeu Lima de Souza Cascardo

Public bug reported:

[Impact]
An unprivileged user may cause an out-of-bounds write by setting up geneve 
options on the flower classifier.

[Test case]
https://seclists.org/oss-sec/2023/q2/219

[Potential regression]
Users setting up geneve options on the flower tc classifier can be affected.

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

** Affects: linux (Ubuntu Focal)
 Importance: High
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: New

** Affects: linux (Ubuntu Jammy)
 Importance: High
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: New

** Affects: linux (Ubuntu Kinetic)
 Importance: High
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: New

** Affects: linux (Ubuntu Lunar)
 Importance: High
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: New

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

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

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

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

** Changed in: linux (Ubuntu Lunar)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

** Changed in: linux (Ubuntu Kinetic)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

Title:
  cls_flower: off-by-one in fl_set_geneve_opt

Status in linux package in Ubuntu:
  New
Status in linux source package in Focal:
  New
Status in linux source package in Jammy:
  New
Status in linux source package in Kinetic:
  New
Status in linux source package in Lunar:
  New

Bug description:
  [Impact]
  An unprivileged user may cause an out-of-bounds write by setting up geneve 
options on the flower classifier.

  [Test case]
  https://seclists.org/oss-sec/2023/q2/219

  [Potential regression]
  Users setting up geneve options on the flower tc classifier can be affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023577/+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 2023420] Re: Focal update: v5.4.237 upstream stable release

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

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

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

Title:
  Focal update: v5.4.237 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  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:

     v5.4.237 upstream stable patchset
     from git://git.kernel.org/

  fs: prevent out-of-bounds array speculation when closing a file descriptor
  x86/CPU/AMD: Disable XSAVES on AMD family 0x17
  drm/connector: print max_requested_bpc in state debugfs
  ext4: fix RENAME_WHITEOUT handling for inline directories
  ext4: fix another off-by-one fsmap error on 1k block filesystems
  ext4: move where set the MAY_INLINE_DATA flag is set
  ext4: fix WARNING in ext4_update_inline_data
  ext4: zero i_disksize when initializing the bootloader inode
  nfc: change order inside nfc_se_io error path
  iommu/amd: Add PCI segment support for ivrs_[ioapic/hpet/acpihid] commands
  iommu/amd: Fix ill-formed ivrs_ioapic, ivrs_hpet and ivrs_acpihid options
  iommu/amd: Add a length limitation for the ivrs_acpihid command-line parameter
  ipmi:ssif: make ssif_i2c_send() void
  ipmi:ssif: resend_msg() cannot fail
  ipmi:ssif: Remove rtc_us_timer
  ipmi:ssif: Increase the message retry time
  ipmi:ssif: Add a timer between request retries
  irqdomain: Change the type of 'size' in __irq_domain_add() to be consistent
  irqdomain: Fix domain registration race
  iommu/vt-d: Fix PASID directory pointer coherency
  SMB3: Backup intent flag missing from some more ops
  cifs: Fix uninitialized memory read in smb3_qfs_tcon()
  scsi: core: Remove the /proc/scsi/${proc_name} directory earlier
  ext4: Fix possible corruption when moving a directory
  drm/msm/a5xx: fix setting of the CP_PREEMPT_ENABLE_LOCAL register
  nfc: fdp: add null check of devm_kmalloc_array in 
fdp_nci_i2c_read_device_properties
  ila: do not generate empty messages in ila_xlat_nl_cmd_get_mapping()
  selftests: nft_nat: ensuring the listening side is up before starting the 
client
  net: usb: lan78xx: Remove lots of set but unused 'ret' variables
  net: lan78xx: fix accessing the LAN7800's internal phy specific registers 
from the MAC driver
  net: caif: Fix use-after-free in cfusbl_device_notify()
  bnxt_en: Avoid order-5 memory allocation for TPA data
  netfilter: tproxy: fix deadlock due to missing BH disable
  btf: fix resolving BTF_KIND_VAR after ARRAY, STRUCT, UNION, PTR
  scsi: megaraid_sas: Update max supported LD IDs to 240
  net/smc: fix fallback failed while sendmsg with fastopen
  riscv: Use READ_ONCE_NOCHECK in imprecise unwinding stack mode
  ext4: Fix deadlock during directory rename
  MIPS: Fix a compilation issue
  alpha: fix R_ALPHA_LITERAL reloc for large modules
  macintosh: windfarm: Use unsigned type for 1-bit bitfields
  PCI: Add SolidRun vendor ID
  media: ov5640: Fix analogue gain control
  ipmi/watchdog: replace atomic_add() and atomic_sub()
  ipmi:watchdog: Set panic count to proper value on a panic
  drm/i915: Don't use BAR mappings for ring buffers with LLC
  x86, vmlinux.lds: Add RUNTIME_DISCARD_EXIT to generic DISCARDS
  arch: fix broken BuildID for arm64 and riscv
  powerpc/vmlinux.lds: Define RUNTIME_DISCARD_EXIT
  powerpc/vmlinux.lds: Don't discard .rela* for relocatable builds
  s390: define RUNTIME_DISCARD_EXIT to fix link error with GNU ld < 2.36
  sh: define RUNTIME_DISCARD_EXIT
  UML: define RUNTIME_DISCARD_EXIT
  s390/dasd: add missing discipline function
  Linux 5.4.237
  UBUNTU: Upstream stable to v5.4.237

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023420/+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 2023427] Re: Focal update: v5.4.238 upstream stable release

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

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

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

Title:
  Focal update: v5.4.238 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  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:

     v5.4.238 upstream stable patchset
     from git://git.kernel.org/

  ext4: fix cgroup writeback accounting with fs-layer encryption
  xfrm: Allow transport-mode states with AF_UNSPEC selector
  drm/panfrost: Don't sync rpm suspension after mmu flushing
  cifs: Move the in_send statistic to __smb_send_rqst()
  drm/meson: fix 1px pink line on GXM when scaling video overlay
  clk: HI655X: select REGMAP instead of depending on it
  docs: Correct missing "d_" prefix for dentry_operations member 
d_weak_revalidate
  scsi: mpt3sas: Fix NULL pointer access in mpt3sas_transport_port_add()
  ALSA: hda - add Intel DG1 PCI and HDMI ids
  ALSA: hda - controller is in GPU on the DG1
  ALSA: hda: Add Alderlake-S PCI ID and HDMI codec vid
  ALSA: hda: Add Intel DG2 PCI ID and HDMI codec vid
  ALSA: hda: Match only Intel devices with CONTROLLER_IN_GPU()
  netfilter: nft_redir: correct value of inet type `.maxattrs`
  scsi: core: Fix a comment in function scsi_host_dev_release()
  scsi: core: Fix a procfs host directory removal regression
  tcp: tcp_make_synack() can be called from process context
  nfc: pn533: initialize struct pn533_out_arg properly
  ipvlan: Make skb->skb_iif track skb->dev for l3s mode
  i40e: Fix kernel crash during reboot when adapter is in recovery mode
  qed/qed_dev: guard against a possible division by zero
  net: tunnels: annotate lockless accesses to dev->needed_headroom
  net: phy: smsc: bail out in lan87xx_read_status if genphy_read_status fails
  nfc: st-nci: Fix use after free bug in ndlc_remove due to race condition
  net: usb: smsc75xx: Limit packet length to skb->len
  nvmet: avoid potential UAF in nvmet_req_complete()
  block: sunvdc: add check for mdesc_grab() returning NULL
  ipv4: Fix incorrect table ID in IOCTL path
  net: usb: smsc75xx: Move packet length check to prevent kernel panic in 
skb_pull
  net/iucv: Fix size of interrupt data
  ethernet: sun: add check for the mdesc_grab()
  hwmon: (adt7475) Display smoothing attributes in correct order
  hwmon: (adt7475) Fix masking of hysteresis registers
  hwmon: (xgene) Fix use after free bug in xgene_hwmon_remove due to race 
condition
  hwmon: (ina3221) return prober error code
  media: m5mols: fix off-by-one loop termination error
  mmc: atmel-mci: fix race between stop command and start of next command
  jffs2: correct logic when creating a hole in jffs2_write_begin
  ext4: fail ext4_iget if special inode unallocated
  ext4: fix task hung in ext4_xattr_delete_inode
  drm/amdkfd: Fix an illegal memory access
  sh: intc: Avoid spurious sizeof-pointer-div warning
  ext4: fix possible double unlock when moving a directory
  tty: serial: fsl_lpuart: skip waiting for transmission complete when 
UARTCTRL_SBK is asserted
  interconnect: fix mem leak when freeing nodes
  tracing: Check field value in hist_field_name()
  tracing: Make tracepoint lockdep check actually test something
  ftrace: Fix invalid address access in lookup_rec() when index is 0
  fbdev: stifb: Provide valid pixelclock and add fb_check_var() checks
  x86/mm: Fix use of uninitialized buffer in sme_enable()
  drm/i915: Don't use stolen memory for ring buffers with LLC
  serial: 8250_em: Fix UART port type
  s390/ipl: add missing intersection check to ipl_report handling
  PCI: Unify delay handling for reset and resume
  HID: core: Provide new max_buffer_size attribute to over-ride the default
  HID: uhid: Over-ride the default maximum data buffer value with our own
  Linux 5.4.238
  UBUNTU: Upstream stable to v5.4.238

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi-5.4/5.4.0.1087.84)

All autopkgtests for the newly accepted linux-meta-raspi-5.4 (5.4.0.1087.84) 
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

acpi-call/unknown (arm64)
bbswitch/unknown (arm64)
dpdk/unknown (arm64)
fwts/unknown (arm64)
glibc/unknown (arm64)
ktap/unknown (arm64)
langford/unknown (arm64)
linux-raspi-5.4/blacklisted (arm64, armhf)
lxc/3.0.3-0ubuntu1~18.04.3 (arm64)
lxd/unknown (arm64)
nat-rtsp/unknown (arm64)
r8168/unknown (arm64)
rtl8812au/unknown (arm64)
rtl8821ce/unknown (arm64)
spl-linux/unknown (arm64)
west-chamber/unknown (arm64)
wireguard-linux-compat/unknown (arm64)
zfs-linux/unknown (arm64)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-raspi-5.4

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws-5.4/5.4.0.1104.82)

All autopkgtests for the newly accepted linux-meta-aws-5.4 (5.4.0.1104.82) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

kpatch/0.5.0-0ubuntu1.1 (amd64)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-aws-5.4

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp-5.4/5.4.0.1107.83)

All autopkgtests for the newly accepted linux-meta-gcp-5.4 (5.4.0.1107.83) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

dpdk/17.11.10-0ubuntu0.2 (amd64, arm64)
lxc/3.0.3-0ubuntu1~18.04.3 (arm64)
r8168/8.045.08-2ubuntu1 (amd64, arm64)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-gcp-5.4

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-5.4/5.4.0.1110.83)

All autopkgtests for the newly accepted linux-meta-azure-5.4 (5.4.0.1110.83) 
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

asic0x/1.0.1-1 (amd64, arm64)
dahdi-linux/1:2.11.1~dfsg-1ubuntu4.2 (amd64)
kpatch/0.5.0-0ubuntu1.1 (amd64)
v4l2loopback/0.10.0-1ubuntu1.2 (amd64, arm64)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-azure-5.4

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2020463] Re: package linux-headers-5.19.0-42-generic 5.19.0-42.43~22.04.1 failed to install/upgrade: installed linux-headers-5.19.0-42-generic package post-installation script s

2023-06-12 Thread Aril Spetalen

I get a very similar error, adding here my console output:

dpkg: error processing package linux-generic-hwe-20.04 (--configure):
 dependency problems - leaving unconfigured
Processing triggers for linux-image-5.19.0-1024-lowlatency 
(5.19.0-1024.25~22.04.1) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.19.0-1024-lowlatency
   ...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.19.0-1024-lowlatency
/usr/sbin/update-initramfs: 145: sync: not found
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127
dpkg: error processing package linux-image-5.19.0-1024-lowlatency (--configure):
 installed linux-image-5.19.0-1024-lowlatency package post-installation script 
subprocess returned error exit status 1
No apport report written because MaxReports is reached already
  Processing 
triggers for linux-image-5.19.0-43-generic (5.19.0-43.44~22.04.1) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.19.0-43-generic
   ...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.19.0-43-generic
/usr/sbin/update-initramfs: 145: sync: not found
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127
dpkg: error processing package linux-image-5.19.0-43-generic (--configure):
 installed linux-image-5.19.0-43-generic package post-installation script 
subprocess returned error exit status 1
No apport report written because MaxReports is reached already
  Processing 
triggers for linux-image-5.19.0-42-generic (5.19.0-42.43~22.04.1) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.19.0-42-generic
   ...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.19.0-42-generic
/usr/sbin/update-initramfs: 145: sync: not found
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127
dpkg: error processing package linux-image-5.19.0-42-generic (--configure):
 installed linux-image-5.19.0-42-generic package post-installation script 
subprocess returned error exit status 1
No apport report written because MaxReports is reached already
  Errors were 
encountered while processing:
 linux-firmware
 linux-image-generic-hwe-22.04
 linux-generic-hwe-22.04
 linux-image-lowlatency-hwe-22.04
 linux-lowlatency-hwe-22.04
 linux-lowlatency-hwe-20.04
 linux-generic-hwe-20.04
 linux-image-5.19.0-1024-lowlatency
 linux-image-5.19.0-43-generic
 linux-image-5.19.0-42-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
W: Operation was interrupted before it could finish
arils@arils-laptop:~/dev/xochitl$

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

Title:
  package linux-headers-5.19.0-42-generic 5.19.0-42.43~22.04.1 failed to
  install/upgrade: installed linux-headers-5.19.0-42-generic package
  post-installation script subprocess returned error exit status 1

Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  dpkg: error processing package linux-headers-generic-hwe-22.04 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic-hwe-22.04:
   linux-generic-hwe-22.04 depends on linux-headers-generic-hwe-22.04 (= 
5.19.0.42.43~22.04.15); however:
Package linux-headers-generic-hwe-22.04 is not configured yet.

  dpkg: error processing package linux-generic-hwe-22.04 (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.

No apport report written because the error m
  essage indicates its a followup error from a previous failure.
Processing 
triggers for linux-image-5.19.0-42-generic (5.19.0-42.43~22.04.1) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 5.19.0-42-generic
  Error! Could not locate dkms.conf file.
  File: /var/lib/dkms/amdgpu/5.16.9.22.20-1438747~22.04/source/dkms.conf does 
not exist.
 ...fail!
  run-parts: /etc/kernel/postinst.d/dkms exited with return code 4
  dpkg: error processing package linux-image-5.19.0-42-generic (--configure):
   installed linux-image-5.19.0-42-generic package post-installation script 
subprocess returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were

[Kernel-packages] [Bug 2020463] Re: package linux-headers-5.19.0-42-generic 5.19.0-42.43~22.04.1 failed to install/upgrade: installed linux-headers-5.19.0-42-generic package post-installation script s

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package linux-headers-5.19.0-42-generic 5.19.0-42.43~22.04.1 failed to
  install/upgrade: installed linux-headers-5.19.0-42-generic package
  post-installation script subprocess returned error exit status 1

Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  dpkg: error processing package linux-headers-generic-hwe-22.04 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic-hwe-22.04:
   linux-generic-hwe-22.04 depends on linux-headers-generic-hwe-22.04 (= 
5.19.0.42.43~22.04.15); however:
Package linux-headers-generic-hwe-22.04 is not configured yet.

  dpkg: error processing package linux-generic-hwe-22.04 (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.

No apport report written because the error m
  essage indicates its a followup error from a previous failure.
Processing 
triggers for linux-image-5.19.0-42-generic (5.19.0-42.43~22.04.1) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 5.19.0-42-generic
  Error! Could not locate dkms.conf file.
  File: /var/lib/dkms/amdgpu/5.16.9.22.20-1438747~22.04/source/dkms.conf does 
not exist.
 ...fail!
  run-parts: /etc/kernel/postinst.d/dkms exited with return code 4
  dpkg: error processing package linux-image-5.19.0-42-generic (--configure):
   installed linux-image-5.19.0-42-generic package post-installation script 
subprocess returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   linux-headers-5.19.0-42-generic
   linux-headers-generic-hwe-22.04
   linux-generic-hwe-22.04
   linux-image-5.19.0-42-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-headers-5.19.0-42-generic 5.19.0-42.43~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue May 23 10:54:23 2023
  ErrorMessage: installed linux-headers-5.19.0-42-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2022-08-04 (291 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  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.1
   apt  2.4.9
  SourcePackage: linux-hwe-5.19
  Title: package linux-headers-5.19.0-42-generic 5.19.0-42.43~22.04.1 failed to 
install/upgrade: installed linux-headers-5.19.0-42-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2020463/+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 2020413] Re: fix typo in config-checks invocation

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

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

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


** Tags added: kernel-spammed-focal-linux-gcp-5.15 verification-needed-focal

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

Title:
  fix typo in config-checks invocation

Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  Fix Committed
Status in linux source package in Jammy:
  Incomplete
Status in linux-kvm source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  After migrating to the new annotations-only model in jammy we
  introduced a typo in debian/rules.d/4-checks.mk, that is triggered if
  we opt to not migrate to the new model and still use the old
  configs+annotations.

  [Test case]

  With debian./config/config.common.ubuntu present run the
  following command:

   $ fakeroot debian/rules clean updateconfigs

  [Fix]

  Replace @perl -> perl.

  [Regression potential]

  It's a trivial typo fix. Regressions can be introduced only if we are
  still using the old configs+annotations model.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020413/+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 2020531] Re: support python < 3.9 with annotations

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

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

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


** Tags added: kernel-spammed-focal-linux-gcp-5.15

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

Title:
  support python < 3.9 with annotations

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

Bug description:
  [Impact]

  At the moment we can't use the annotations scripts in focal, because
  we are using the'|=' update operator for merging dicts, that has been
  introduced with python 3.9.

  Rewrite the code that is using this operator in a more portable way
  and apply this change everywhere, so that annotations will work on any
  backport/derivative kernels.

  [Test case]

  Run `fakeroot debian/rules updateconfigs` in focal (using the new
  annotations model).

  [Fix]

  Try to use the '|=' operator in a try/except block, if it fails
  fallback to a more portable way.

  [Regression potential]

  With this change applied we may experience regressions during the
  updateconfigs phase.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020531/+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 2015611] Re: Keyboard not working after recent Kinetic kernel update

2023-06-12 Thread kamand kargar

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => kamand kargar (kamandkrg)

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

Title:
  Keyboard not working after recent Kinetic kernel update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I did a fresh installation of Ubuntu 22.10 on my (still new) Maingear
  MG-VCP2-15A3070T (Vector Pro 2) laptop. The base kernel image which
  was installed is 5.19.0-21.21, and the keyboard works fine if I boot
  into this. Subsequent OS updates have installed kernel versions
  5.19.0-35.36, and 5.19.0-38.39, and these caused my keyboard to stop
  working past the Grub menu. I've been booting into the 5.19.0-21.21
  kernel in order to have a working keyboard.

  Here is some additional information on my laptop.
  CPU: AMD Ryzen 9 6900HX
  GPU: NVIDIA GeForce RTX 3070 Ti
  RAM: 32GB DDR5-4800

  Attaching an external keyboard does allow me to use the newer kernels.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-38-generic 5.19.0-38.39
  ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  shahid 3484 F wireplumber
   /dev/snd/controlC1:  shahid 3484 F wireplumber
   /dev/snd/controlC0:  shahid 3484 F wireplumber
   /dev/snd/seq:shahid 3481 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  7 20:06:43 2023
  InstallationDate: Installed on 2023-03-12 (26 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: Micro Electronics Inc MG-VCP2-15A3070T
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-38-generic 
root=/dev/mapper/vg-ubuntu_root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-38-generic N/A
   linux-backports-modules-5.19.0-38-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2022
  dmi.bios.release: 1.5
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: N.1.10MAI05
  dmi.board.asset.tag: Standard
  dmi.board.name: VECTOR Pro 2 15
  dmi.board.vendor: MAINGEAR
  dmi.board.version: Standard
  dmi.chassis.asset.tag: Standard
  dmi.chassis.type: 10
  dmi.chassis.vendor: MAINGEAR
  dmi.chassis.version: Standard
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrN.1.10MAI05:bd07/12/2022:br1.5:efr1.9:svnMicroElectronicsInc:pnMG-VCP2-15A3070T:pvrStandard:rvnMAINGEAR:rnVECTORPro215:rvrStandard:cvnMAINGEAR:ct10:cvrStandard:sku407627:
  dmi.product.family: MAINGEAR
  dmi.product.name: MG-VCP2-15A3070T
  dmi.product.sku: 407627
  dmi.product.version: Standard
  dmi.sys.vendor: Micro Electronics Inc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015611/+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 2021962] Re: F/xilinx and J/xilinx uses different keyword in /proc/device-tree/compatible

2023-06-12 Thread Hon Ming Hui

** Description changed:

  While testing J/xilinx, I noticed that the keyword we use to grep from
  /proc/device-tree/compatible has to be changed into kv26 instead of k26
  that we used for F/xilinx
  
  J/xilinx:
  $ cat /proc/device-tree/compatible
  
xlnx,zynqmp-sk-kv260-rev1xlnx,zynqmp-sk-kv260-revBxlnx,zynqmp-sk-kv260xlnx,zynqmp
  
  F/xilinx:
  $ cat /proc/device-tree/compatible
  
xlnx,zynqmp-smk-k26-rev1xlnx,zynqmp-smk-k26-revBxlnx,zynqmp-smk-k26-revAxlnx,zynqmp-smk-k26xlnx,zynqmp
  
  From what I can found on the Internet, KV260 is "a vision application
  development platform for Kria K26 SOMs (system-on-module)". But it's
  better to let the kernel maintainer (Portia) to answer that if this
  difference is expected.
  
  
  Related change for tests:
  
https://code.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests/+merge/443543
+ 
+ ---
+ External link: https://warthogs.atlassian.net/browse/PEL-439

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

Title:
  F/xilinx and J/xilinx uses different keyword in /proc/device-
  tree/compatible

Status in ubuntu-kernel-tests:
  New
Status in linux-xilinx-zynqmp package in Ubuntu:
  New

Bug description:
  While testing J/xilinx, I noticed that the keyword we use to grep from
  /proc/device-tree/compatible has to be changed into kv26 instead of
  k26 that we used for F/xilinx

  J/xilinx:
  $ cat /proc/device-tree/compatible
  
xlnx,zynqmp-sk-kv260-rev1xlnx,zynqmp-sk-kv260-revBxlnx,zynqmp-sk-kv260xlnx,zynqmp

  F/xilinx:
  $ cat /proc/device-tree/compatible
  
xlnx,zynqmp-smk-k26-rev1xlnx,zynqmp-smk-k26-revBxlnx,zynqmp-smk-k26-revAxlnx,zynqmp-smk-k26xlnx,zynqmp

  From what I can found on the Internet, KV260 is "a vision application
  development platform for Kria K26 SOMs (system-on-module)". But it's
  better to let the kernel maintainer (Portia) to answer that if this
  difference is expected.

  
  Related change for tests:
  
https://code.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests/+merge/443543

  ---
  External link: https://warthogs.atlassian.net/browse/PEL-439

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2021962/+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 2023545] Re: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate

2023-06-12 Thread Frank Heimes

** Package changed: linux (Ubuntu) => openssl (Ubuntu)

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Changed in: openssl (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned)

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

** Changed in: ubuntu-z-systems
   Importance: Undecided => High

** Tags added: rls-jj-incoming

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

Title:
  [UBUNTU 22.04] openssl with ibmca engine configured dumps core when
  creating a new certificate

Status in Ubuntu on IBM z Systems:
  New
Status in openssl package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  OpenSSL with ibmca engine configured dumps core when creating a new 
certificate.

  # openssl engine
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
  # openssl req  -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem 
-keyout __key.pem --subj '/CN=US'
  Segmentation fault (core dumped)

  # journalctl
  Jun 07 13:06:08 SYSTEM kernel: User process fault: interruption code 003b 
ilc:2 in libc.so.6[3ffae08+1ca000]
  Jun 07 13:06:08 SYSTEM kernel: Failing address:  TEID: 
0800
  Jun 07 13:06:08 SYSTEM kernel: Fault in primary space mode while using user 
ASCE.
  Jun 07 13:06:08 SYSTEM kernel: AS:9c2941c7 R3:0024
  Jun 07 13:06:08 SYSTEM kernel: CPU: 2 PID: 2344 Comm: openssl Kdump: loaded 
Not tainted 5.15.0-73-generic #80-Ubuntu
  Jun 07 13:06:08 SYSTEM kernel: Hardware name: IBM 3931 A01 703 (z/VM 7.3.0)
  Jun 07 13:06:08 SYSTEM kernel: User PSW : 070500018000 03ffae11c708
  Jun 07 13:06:08 SYSTEM kernel:R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 
AS:0 CC:0 PM:0 RI:0 EA:3
  Jun 07 13:06:08 SYSTEM kernel: User GPRS: 0007 03ffae11c6f0 
 02aa3289f9d0
  Jun 07 13:06:08 SYSTEM kernel:02aa1825980f 02aa3289f9d0 
 02aa328a4300
  Jun 07 13:06:08 SYSTEM kernel:03ffae870720 03ffae657128 
02aa03ff 
  Jun 07 13:06:08 SYSTEM kernel:03ffae24dd10 03ffae657120 
03ffae437c22 03ffec2fe000
  Jun 07 13:06:08 SYSTEM kernel: User Code: 03ffae11c6fc: b90400b2  
  lgr%r11,%r2
03ffae11c700: 
4700bc0,0
   #03ffae11c704: 
b24f00a0ear%r10,%a0
   >03ffae11c708: 
58102018l%r1,24(%r2)
03ffae11c70c: 
ebaa002dsllg%r10,%r10,32
03ffae11c712: 
b24f00a1ear%r10,%a1
03ffae11c716: 
5910a0d0c%r1,208(%r10)
03ffae11c71a: 
a7840033brc8,03ffae11c780
  Jun 07 13:06:08 SYSTEM kernel: Last Breaking-Event-Address:
  Jun 07 13:06:08 SYSTEM kernel:  [<03ffae33242c>] 0x3ffae33242c
  Jun 07 13:06:08 SYSTEM systemd[1]: Started Process Core Dump (PID 2345/UID 0).
  Jun 07 13:06:08 SYSTEM systemd-coredump[2350]: Process 2344 (openssl) of user 
0 dumped core.

 Found module 
linux-vdso64.so.1 with build-id: bcfab8ac8dbd44c758c3c5494e2952db16905d2e
 Found module 
libica.so.4 with build-id: 0cc5ace50644dfba6d0ecf4f783477cd04a55731
 Found module 
ibmca.so with build-id: 27daaf0ed1857fdad3761c2b3db21020999eee08
 Found module 
ld64.so.1 with build-id: 31d4856f0ba9ea058c91a34f4d684ae0fe01964c
 Found module 
libc.so.6 with build-id: 74250317950da91d3345f258cb2dd12d22c3f2e5
 Found module 
libcrypto.so.3 with build-id: a27f20e6cf293f214d459530ce2c0b2b52fdbdb4
 Found module 
libssl.so.3 with build-id: e2c031c3dac06b5ce43bdea022aee7989f78dde4
 Found module 
openssl with build-id: ed0fe325182e99d135ee6b08e6d90a9d1c42af7f
 Stack trace of 
thread 2344:

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.19/5.19.0.44.45~22.04.19)

All autopkgtests for the newly accepted linux-meta-hwe-5.19 
(5.19.0.44.45~22.04.19) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

lttng-modules/2.13.8-1~ubuntu22.04.0 (amd64, arm64, armhf, ppc64el,
s390x)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-hwe-5.19

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

Re: [Kernel-packages] [Bug 2023446] Re: Excessive Power drain in sleep mode on XPS 9315

2023-06-12 Thread Nick

Hi

I will try that and test this evening

Nick
On Mon, 2023-06-12 at 12:24 +, Kai-Heng Feng wrote:
> Please see if OEM kernel [1] helps.
> 
> [1] https://wiki.ubuntu.com/Kernel/OEMKernel
>

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

Title:
  Excessive Power drain in sleep mode on XPS 9315

Status in linux package in Ubuntu:
  Confirmed

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

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

  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04

  Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17

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

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


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

[Kernel-packages] [Bug 2023446] Re: Excessive Power drain in sleep mode on XPS 9315

2023-06-12 Thread Nick

I will try the OEMKernel as suggested

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

Title:
  Excessive Power drain in sleep mode on XPS 9315

Status in linux package in Ubuntu:
  Confirmed

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

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

  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04

  Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17

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

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


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

[Kernel-packages] [Bug 2018960] Re: linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0

2023-06-12 Thread Tom Söderlund

Seeing this on U18 based gateway nodes running 4.15.0-212-generic.

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

Title:
  linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212
  sk_stream_kill_queues+0xcf/0xe0

Status in linux-signed package in Ubuntu:
  Confirmed
Status in linux-signed-kvm package in Ubuntu:
  Confirmed

Bug description:
  After upgrading and rebooting this Ubuntu 20.04 LTS server (Ubuntu
  Focal), I noticed that it was suddenly getting a bunch of kernel log
  (dmesg) reports like:

  WARNING: CPU: 4 PID: 0 at net/core/stream.c:212
  sk_stream_kill_queues+0xcf/0xe0

  while investigating I determined that it is currently running the
  focal-proposed kernel (linux-image-5.4.0-149-generic), which it turns
  out was enabled for this server (clearly it seemed like a good idea at
  the time).

  I'm not expecting focal-proposed to be fixed as if it were a release
  package, but since I couldn't find any reports on Launchpad I figured
  I should let y'all know this focal-proposed package could do with some
  additional work before it's actually released :-)

  There have been at least 80 such reports in the last 5 hours since the
  server was rebooted, differing only by the CPU core and the process
  reported, although it seems the last one was a couple of hours ago, so
  I guess it's traffic dependent/timing dependent.

  ewen@naosr620:~$ uptime
   16:27:32 up  5:19,  1 user,  load average: 0.08, 0.14, 0.06
  ewen@naosr620:~$ dmesg -t | grep WARNING | sed 's/CPU: [0-9]*/CPU: N/; s/PID: 
[0-9]*/PID: N/;' | uniq -c
   88 WARNING: CPU: N PID: N at net/core/stream.c:212 
sk_stream_kill_queues+0xcf/0xe0
  ewen@naosr620:~$ 

  Ubuntu Release:

  ewen@naosr620:~$ lsb_release -rd
  Description:  Ubuntu 20.04.6 LTS
  Release:  20.04
  ewen@naosr620:~$ 

  
  Kernel/package version affected:

  ewen@naosr620:~$ uname -a
  Linux naosr620 5.4.0-149-generic #166-Ubuntu SMP Tue Apr 18 16:51:45 UTC 2023 
x86_64 x86_64 x86_64 GNU/Linux
  ewen@naosr620:~$ dpkg -l | grep linux-image | grep 149
  ii  linux-image-5.4.0-149-generic  5.4.0-149.166  
   amd64Signed kernel image generic
  ii  linux-image-generic5.4.0.149.147  
   amd64Generic Linux kernel image
  ewen@naosr620:~$ apt-cache policy linux-image-5.4.0-149-generic 
  linux-image-5.4.0-149-generic:
Installed: 5.4.0-149.166
Candidate: 5.4.0-149.166
Version table:
   *** 5.4.0-149.166 500
  500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
  ewen@naosr620:~$ apt-cache policy linux-image-generic
  linux-image-generic:
Installed: 5.4.0.149.147
Candidate: 5.4.0.149.147
Version table:
   *** 5.4.0.149.147 500
  500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.4.0.148.146 500
  500 https://mirror.fsmg.org.nz/ubuntu focal-updates/main amd64 
Packages
  500 https://mirror.fsmg.org.nz/ubuntu focal-security/main amd64 
Packages
   5.4.0.26.32 500
  500 https://mirror.fsmg.org.nz/ubuntu focal/main amd64 Packages
  ewen@naosr620:~$ 
  ewen@naosr620:~$ apt-cache show linux-image-5.4.0-149-generic | grep Source:
  Source: linux-signed
  ewen@naosr620:~$ 

  
  Full example dmesg, including stack trace (they all seem to be WARNINGs, and 
other than filling dmesg / system logs the system "appears to be running okay", 
so I'm not going to rush another reboot now -- near end of business day):

  ewen@naosr620:~$ date
  Tue 09 May 2023 16:34:56 NZST
  ewen@naosr620:~$ dmesg -T | tail -100 | grep -B 150 "end trace" | grep -A 999 
"cut here"
  [Tue May  9 14:21:18 2023] [ cut here ]
  [Tue May  9 14:21:18 2023] WARNING: CPU: 10 PID: 0 at net/core/stream.c:212 
sk_stream_kill_queues+0xcf/0xe0
  [Tue May  9 14:21:18 2023] Modules linked in: mpt3sas raid_class 
scsi_transport_sas mptctl mptbase vhost_net vhost tap ip6t_REJECT 
nf_reject_ipv6 ip6table_mangle ip6table_nat ip6table_raw nf_log_ipv6 xt_recent 
ipt_REJECT nf_reject_ipv4 xt_hashlimit xt_addrtype xt_multiport xt_comment 
xt_conntrack xt_mark iptable_mangle xt_MASQUERADE iptable_nat xt_CT xt_tcpudp 
iptable_raw nfnetlink_log xt_NFLOG nf_log_ipv4 nf_log_common xt_LOG nf_nat_tftp 
nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_irc 
ebtable_filter nf_nat_h323 ebtables nf_nat_ftp nf_nat_amanda ts_kmp 
ip6table_filter nf_conntrack_amanda nf_nat ip6_tables nf_conntrack_sane 
nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_netlink 
nfnetlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc 
nf_conntrack_h323 nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
iptable_filter bpfilter dell_rbu nls_iso8859_1 ipmi_ssif

[Kernel-packages] [Bug 2023446] Re: Excessive Power drain in sleep mode on XPS 9315

2023-06-12 Thread Kai-Heng Feng

Please see if OEM kernel [1] helps.

[1] https://wiki.ubuntu.com/Kernel/OEMKernel

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

Title:
  Excessive Power drain in sleep mode on XPS 9315

Status in linux package in Ubuntu:
  Confirmed

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

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

  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04

  Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17

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

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


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

[Kernel-packages] [Bug 2023544] Status changed to Confirmed

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => 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/2023544

Title:
  touchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am not able to use my mouse as its freeze.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-73-generic 5.15.0-73.80
  ProcVersionSignature: Ubuntu 5.15.0-73.80-generic 5.15.98
  Uname: Linux 5.15.0-73-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  deepak-grid   2491 F pulseaudio
   /dev/snd/pcmC0D6c:   deepak-grid   2491 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 12 17:05:35 2023
  InstallationDate: Installed on 2023-03-17 (86 days ago)
  InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831)
  MachineType: TIMI Mi NoteBook Pro
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-73-generic 
root=UUID=30d2e44c-6fd9-439f-aca6-ac2c793975dd ro quiet i8042.nopnp=1 pci=nocrs
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-73-generic N/A
   linux-backports-modules-5.15.0-73-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.13
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2023-06-12 (0 days ago)
  dmi.bios.date: 10/15/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: TIMI
  dmi.bios.version: RMATG4B1P0F0F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: TM2009
  dmi.board.vendor: TIMI
  dmi.board.version: V44H1
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.ec.firmware.release: 1.15
  dmi.modalias: 
dmi:bvnTIMI:bvrRMATG4B1P0F0F:bd10/15/2021:br1.15:efr1.15:svnTIMI:pnMiNoteBookPro:pvr:rvnTIMI:rnTM2009:rvrV44H1:cvnTIMI:ct10:cvr:skuTM2009-39168:
  dmi.product.family: Mi Laptop
  dmi.product.name: Mi NoteBook Pro
  dmi.product.sku: TM2009-39168
  dmi.sys.vendor: TIMI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023544/+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 2023545] [NEW] [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate

2023-06-12 Thread bugproxy

Public bug reported:

---Problem Description---
OpenSSL with ibmca engine configured dumps core when creating a new certificate.

# openssl engine
(dynamic) Dynamic engine loading support
(ibmca) Ibmca hardware engine support
# openssl req  -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem 
-keyout __key.pem --subj '/CN=US'
Segmentation fault (core dumped)

# journalctl
Jun 07 13:06:08 SYSTEM kernel: User process fault: interruption code 003b ilc:2 
in libc.so.6[3ffae08+1ca000]
Jun 07 13:06:08 SYSTEM kernel: Failing address:  TEID: 
0800
Jun 07 13:06:08 SYSTEM kernel: Fault in primary space mode while using user 
ASCE.
Jun 07 13:06:08 SYSTEM kernel: AS:9c2941c7 R3:0024
Jun 07 13:06:08 SYSTEM kernel: CPU: 2 PID: 2344 Comm: openssl Kdump: loaded Not 
tainted 5.15.0-73-generic #80-Ubuntu
Jun 07 13:06:08 SYSTEM kernel: Hardware name: IBM 3931 A01 703 (z/VM 7.3.0)
Jun 07 13:06:08 SYSTEM kernel: User PSW : 070500018000 03ffae11c708
Jun 07 13:06:08 SYSTEM kernel:R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 
AS:0 CC:0 PM:0 RI:0 EA:3
Jun 07 13:06:08 SYSTEM kernel: User GPRS: 0007 03ffae11c6f0 
 02aa3289f9d0
Jun 07 13:06:08 SYSTEM kernel:02aa1825980f 02aa3289f9d0 
 02aa328a4300
Jun 07 13:06:08 SYSTEM kernel:03ffae870720 03ffae657128 
02aa03ff 
Jun 07 13:06:08 SYSTEM kernel:03ffae24dd10 03ffae657120 
03ffae437c22 03ffec2fe000
Jun 07 13:06:08 SYSTEM kernel: User Code: 03ffae11c6fc: b90400b2
lgr%r11,%r2
  03ffae11c700: 
4700bc0,0
 #03ffae11c704: 
b24f00a0ear%r10,%a0
 >03ffae11c708: 
58102018l%r1,24(%r2)
  03ffae11c70c: 
ebaa002dsllg%r10,%r10,32
  03ffae11c712: 
b24f00a1ear%r10,%a1
  03ffae11c716: 
5910a0d0c%r1,208(%r10)
  03ffae11c71a: 
a7840033brc8,03ffae11c780
Jun 07 13:06:08 SYSTEM kernel: Last Breaking-Event-Address:
Jun 07 13:06:08 SYSTEM kernel:  [<03ffae33242c>] 0x3ffae33242c
Jun 07 13:06:08 SYSTEM systemd[1]: Started Process Core Dump (PID 2345/UID 0).
Jun 07 13:06:08 SYSTEM systemd-coredump[2350]: Process 2344 (openssl) of user 0 
dumped core.

   Found module 
linux-vdso64.so.1 with build-id: bcfab8ac8dbd44c758c3c5494e2952db16905d2e
   Found module 
libica.so.4 with build-id: 0cc5ace50644dfba6d0ecf4f783477cd04a55731
   Found module 
ibmca.so with build-id: 27daaf0ed1857fdad3761c2b3db21020999eee08
   Found module 
ld64.so.1 with build-id: 31d4856f0ba9ea058c91a34f4d684ae0fe01964c
   Found module 
libc.so.6 with build-id: 74250317950da91d3345f258cb2dd12d22c3f2e5
   Found module 
libcrypto.so.3 with build-id: a27f20e6cf293f214d459530ce2c0b2b52fdbdb4
   Found module 
libssl.so.3 with build-id: e2c031c3dac06b5ce43bdea022aee7989f78dde4
   Found module openssl 
with build-id: ed0fe325182e99d135ee6b08e6d90a9d1c42af7f
   Stack trace of 
thread 2344:
   #0  
0x03ffae11c708 __pthread_rwlock_wrlock_full64 (libc.so.6 + 0x9c708)
   #1  
0x03ffae437c22 CRYPTO_THREAD_write_lock (libcrypto.so.3 + 0x1b7c22)
   #2  
0x03ffae3e3472 ENGINE_finish (libcrypto.so.3 + 0x163472)
   #3  
0x03ffae406844 EVP_CIPHER_CTX_reset (libcrypto.so.3 + 0x186844)
   #4  
0x03ffae40688c EVP_CIPHER_CTX_free (libcrypto.so.3 + 0x18688c)
   #5  
0x03ffae4f903c n/a (libcrypto.so.3 + 0x27903c)
   #6  
0x03ffae40ca98 EVP_RAND_CTX_free (libcrypto.so.3 + 0x18ca98)
   #7  
0x03ffae461a92 n/a

[Kernel-packages] [Bug 2023544] [NEW] touchpad not working

2023-06-12 Thread Deepak Deorari

Public bug reported:

I am not able to use my mouse as its freeze.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-73-generic 5.15.0-73.80
ProcVersionSignature: Ubuntu 5.15.0-73.80-generic 5.15.98
Uname: Linux 5.15.0-73-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  deepak-grid   2491 F pulseaudio
 /dev/snd/pcmC0D6c:   deepak-grid   2491 F...m pulseaudio
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 12 17:05:35 2023
InstallationDate: Installed on 2023-03-17 (86 days ago)
InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831)
MachineType: TIMI Mi NoteBook Pro
ProcEnviron:
 LANGUAGE=en_IN:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-73-generic 
root=UUID=30d2e44c-6fd9-439f-aca6-ac2c793975dd ro quiet i8042.nopnp=1 pci=nocrs
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-73-generic N/A
 linux-backports-modules-5.15.0-73-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.13
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2023-06-12 (0 days ago)
dmi.bios.date: 10/15/2021
dmi.bios.release: 1.15
dmi.bios.vendor: TIMI
dmi.bios.version: RMATG4B1P0F0F
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: TM2009
dmi.board.vendor: TIMI
dmi.board.version: V44H1
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: TIMI
dmi.ec.firmware.release: 1.15
dmi.modalias: 
dmi:bvnTIMI:bvrRMATG4B1P0F0F:bd10/15/2021:br1.15:efr1.15:svnTIMI:pnMiNoteBookPro:pvr:rvnTIMI:rnTM2009:rvrV44H1:cvnTIMI:ct10:cvr:skuTM2009-39168:
dmi.product.family: Mi Laptop
dmi.product.name: Mi NoteBook Pro
dmi.product.sku: TM2009-39168
dmi.sys.vendor: TIMI

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


** Tags: amd64 apport-bug 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/2023544

Title:
  touchpad not working

Status in linux package in Ubuntu:
  New

Bug description:
  I am not able to use my mouse as its freeze.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-73-generic 5.15.0-73.80
  ProcVersionSignature: Ubuntu 5.15.0-73.80-generic 5.15.98
  Uname: Linux 5.15.0-73-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  deepak-grid   2491 F pulseaudio
   /dev/snd/pcmC0D6c:   deepak-grid   2491 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 12 17:05:35 2023
  InstallationDate: Installed on 2023-03-17 (86 days ago)
  InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831)
  MachineType: TIMI Mi NoteBook Pro
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-73-generic 
root=UUID=30d2e44c-6fd9-439f-aca6-ac2c793975dd ro quiet i8042.nopnp=1 pci=nocrs
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-73-generic N/A
   linux-backports-modules-5.15.0-73-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.13
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2023-06-12 (0 days ago)
  dmi.bios.date: 10/15/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: TIMI
  dmi.bios.version: RMATG4B1P0F0F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: TM2009
  dmi.board.vendor: TIMI
  dmi.board.version: V44H1
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.ec.firmware.release: 1.15
  dmi.modalias: 
dmi:bvnTIMI:bvrRMATG4B1P0F0F:bd10/15/2021:br1.15:efr1.15:svnTIMI:pnMiNoteBookPro:pvr:rvnTIMI:rnTM2009:rvrV44H1:cvnTIMI:ct10:cvr:skuTM2009-39168:
  dmi.product.family: Mi Laptop
  dmi.product.name: Mi NoteBook Pro
  dmi.product.sku: TM2009-39168
  dmi.sys.vendor: TIMI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023544/+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 2013209] Re: expoline.o is packaged unconditionally for s390x

2023-06-12 Thread Andrei Gherzan

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

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

Title:
  expoline.o is packaged unconditionally for s390x

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.15 package in Ubuntu:
  New
Status in linux-hwe-5.15 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  https://bugs.launchpad.net/bugs/1639924 enabled CONFIG_EXPOLINE_EXTERN
  for s390x in Jammy. While this works as expected on Jammy, it won't
  work on some derivatives of it: for example focal:hwe-5.15. On Focal,
  this config can't be enabled due to the GCC version it comes with.
  CONFIG_EXPOLINE_EXTERN requires >= 110200 while Focal comes with
  90400.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi/5.4.0.1088.118)

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

acpi-call/unknown (arm64)
adv-17v35x/unknown (arm64)
ddcci-driver-linux/unknown (arm64)
dm-writeboost/unknown (arm64)
dpdk/unknown (arm64)
evdi/unknown (arm64)
fwts/unknown (arm64)
glibc/unknown (arm64)
gost-crypto/unknown (arm64)
iptables-netflow/unknown (arm64)
nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (armhf)
systemd/245.4-4ubuntu3.21 (arm64, armhf)
v4l2loopback/unknown (arm64)
zfs-linux/unknown (arm64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2023539] Re: Add audio support for ThinkPad P1 Gen 6

2023-06-12 Thread AaronMa

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

** Changed in: hwe-next
   Status: New => Invalid

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

Title:
  Add audio support for ThinkPad P1 Gen 6

Status in HWE Next:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  [Impact]
  No sound output or sound output is too low on ThinkPad P1 Gen 6

  [Fix]
  Add quirk for ThinkPad P1 Gen 6

  [Test]
  Tested with alsa audio, audio works fine.

  [Where problems could occur]
  Risk low due to specific hardware.

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