date:20231023

This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1018.18~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-linux-
nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'.
If the problem still exists, change the tag 'verification-needed-focal-
linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia-
tegra-5.15'.


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-nvidia-tegra-5.15-v2 
verification-needed-focal-linux-nvidia-tegra-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/2019868

Title:
  ubuntu_kernel_selftests:net:tls: 88 failed test cases on jammy/fips

Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released

Bug description:
  These failures happen on all supported architectures, when fips=1.
  When fips=0, all test cases pass. The results are shown below:

  make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/net'
  make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install
  make[1]: Entering directory '/home/ubuntu/src/linux'
INSTALL ./usr/include
  make[1]: Leaving directory '/home/ubuntu/src/linux'
  TAP version 13
  1..1
  # selftests: net: tls
  # TAP version 13
  # 1..179
  # # Starting 179 tests from 6 test cases.
  # #  RUN   global.non_established ...
  # #OK  global.non_established
  # ok 1 global.non_established
  # #  RUN   global.keysizes ...
  # #OK  global.keysizes
  # ok 2 global.keysizes
  # #  RUN   tls_basic.base_base ...
  # #OK  tls_basic.base_base
  # ok 3 tls_basic.base_base
  # #  RUN   tls.12_gcm.sendfile ...
  # #OK  tls.12_gcm.sendfile
  # ok 4 tls.12_gcm.sendfile
  # #  RUN   tls.12_gcm.send_then_sendfile ...
  # #OK  tls.12_gcm.send_then_sendfile
  # ok 5 tls.12_gcm.send_then_sendfile
  # #  RUN   tls.12_gcm.recv_max ...
  # #OK  tls.12_gcm.recv_max
  # ok 6 tls.12_gcm.recv_max
  # #  RUN   tls.12_gcm.recv_small ...
  # #OK  tls.12_gcm.recv_small
  # ok 7 tls.12_gcm.recv_small
  # #  RUN   tls.12_gcm.msg_more ...
  # #OK  tls.12_gcm.msg_more
  # ok 8 tls.12_gcm.msg_more
  # #  RUN   tls.12_gcm.msg_more_unsent ...
  # #OK  tls.12_gcm.msg_more_unsent
  # ok 9 tls.12_gcm.msg_more_unsent
  # #  RUN   tls.12_gcm.sendmsg_single ...
  # #OK  tls.12_gcm.sendmsg_single
  # ok 10 tls.12_gcm.sendmsg_single
  # #  RUN   tls.12_gcm.sendmsg_fragmented ...
  # #OK  tls.12_gcm.sendmsg_fragmented
  # ok 11 tls.12_gcm.sendmsg_fragmented
  # #  RUN   tls.12_gcm.sendmsg_large ...
  # #OK  tls.12_gcm.sendmsg_large
  # ok 12 tls.12_gcm.sendmsg_large
  # #  RUN   tls.12_gcm.sendmsg_multiple ...
  # #OK  tls.12_gcm.sendmsg_multiple
  # ok 13 tls.12_gcm.sendmsg_multiple
  # #  RUN   tls.12_gcm.sendmsg_multiple_stress ...
  # #OK  tls.12_gcm.sendmsg_multiple_stress
  # ok 14 tls.12_gcm.sendmsg_multiple_stress
  # #  RUN   tls.12_gcm.splice_from_pipe ...
  # #OK  tls.12_gcm.splice_from_pipe
  # ok 15 tls.12_gcm.splice_from_pipe
  # #  RUN   tls.12_gcm.splice_from_pipe2 ...
  # #OK  tls.12_gcm.splice_from_pipe2
  # ok 16 tls.12_gcm.splice_from_pipe2
  # #  RUN   tls.12_gcm.send_and_splice ...
  # #OK  tls.12_gcm.send_and_splice
  # ok 17 tls.12_gcm.send_and_splice
  # #  RUN   tls.12_gcm.splice_to_pipe ...
  # #OK  tls.12_gcm.splice_to_pipe
  # ok 18 tls.12_gcm.splice_to_pipe
  # #  RUN   tls.12_gcm.recvmsg_single ...
  # #OK  tls.12_gcm.recvmsg_single
  # ok 19 tls.12_gcm.recvmsg_single
  # #  RUN   tls.12_gcm.recvmsg_single_max ...
  # #OK  tls.12_gcm.recvmsg_single_max
  # ok 20 tls.12_gcm.recvmsg_single_max
  # #  RUN   tls.12_gcm.recvmsg_multiple ...
  # #OK  tls.12_gcm.recvmsg_multiple
  # ok 21 tls.12_gcm.recvmsg_multiple
  # #  RUN   tls.12_gcm.single_send_multiple_recv ...
  # #OK  tls.12_gcm.single_send_multiple_recv
  # ok 22 tls.12_gcm.single_send_multiple_recv
  # #  RUN   tls.12_gcm.multiple_send_single_recv ...
  # #OK  tls.12_gcm.multiple_send_single_recv
  # ok 23 tls.12_gcm.multiple_send_single_recv
  # #  RUN   tls.12_gcm.single_send_multiple_recv_non_align ...
  # #

[Kernel-packages] [Bug 2019880] Re: ubuntu_kernel_selftests:net:vrf-xfrm-tests.sh: 8 failed test cases on jammy/fips

This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1018.18~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-linux-
nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'.
If the problem still exists, change the tag 'verification-needed-focal-
linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia-
tegra-5.15'.


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-nvidia-tegra-5.15-v2 
verification-needed-focal-linux-nvidia-tegra-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/2019880

Title:
  ubuntu_kernel_selftests:net:vrf-xfrm-tests.sh: 8 failed test cases on
  jammy/fips

Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released

Bug description:
  These failures happen on all supported architectures, when fips=1.
  When fips=0, all test cases pass. Results are shown below:

  make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/net'
  make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install
  make[1]: Entering directory '/home/ubuntu/src/linux'
INSTALL ./usr/include
  make[1]: Leaving directory '/home/ubuntu/src/linux'
  TAP version 13
  1..1
  # selftests: net: vrf-xfrm-tests.sh
  # 
  # No qdisc on VRF device
  # TEST: IPv4 no xfrm policy   [ OK ]
  # TEST: IPv6 no xfrm policy   [ OK ]
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # TEST: IPv4 xfrm policy based on address [FAIL]
  # TEST: IPv6 xfrm policy based on address [FAIL]
  # TEST: IPv6 xfrm policy with VRF in selector [ OK ]
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # TEST: IPv4 xfrm policy with xfrm device [FAIL]
  # TEST: IPv6 xfrm policy with xfrm device [FAIL]
  # 
  # netem qdisc on VRF device
  # TEST: IPv4 no xfrm policy   [ OK ]
  # TEST: IPv6 no xfrm policy   [ OK ]
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # TEST: IPv4 xfrm policy based on address [FAIL]
  # TEST: IPv6 xfrm policy based on address [FAIL]
  # TEST: IPv6 xfrm policy with VRF in selector [ OK ]
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # RTNETLINK answers: Function not implemented
  # TEST: IPv4 xfrm policy with xfrm device [FAIL]
  # TEST: IPv6 xfrm policy with xfrm device [FAIL]
  # 
  # Tests passed:   6
  # Tests failed:   8
  not ok 1 selftests: net: vrf-xfrm-tests.sh # exit=1
  make: Leaving directory '/home/ubuntu/src/linux/tools/testing/selftests/net'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2019880/+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 2022361] Re: Please enable Renesas RZ platform serial installer

This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1018.18~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-linux-
nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'.
If the problem still exists, change the tag 'verification-needed-focal-
linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia-
tegra-5.15'.


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-nvidia-tegra-5.15-v2 
verification-needed-focal-linux-nvidia-tegra-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/2022361

Title:
  Please enable Renesas RZ platform serial installer

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  The ubuntu installer does not work via serial ports for Renesas boards like
  RZ/G2M-HiHope 
(https://www.renesas.com/us/en/products/microcontrollers-microprocessors/rz-mpus/rzg2m-hihope-rzg2m-reference-board,
 RZ/G2L, RZ/G2LC, RZ/G2UL SMARC Board 
(https://renesas.info/wiki/RZ-G/RZ-G2L_SMARC).

  The installation can be done using HDMI ports, but it would be nice to
  support installation via serial port as well.

  [Test case]

  Try to install Ubuntu on a Renesas board.

  [Fix]

  Statically build SuperH SCI(F) serial port support (with
  earlyconsole).

  [Regression potential]

  Statically building an additional driver in the kernel can make the
  kernel image bigger, potentially causing boot issues in small (arm64 /
  armhf) platforms.

  [Original bug report]

  Package: linux
  Version: Ubuntu-6.2.0-21.21
  Severity: normal
  File: /mantic/debian.master/config/annotations

  Dear Maintainer,

  The ubuntu kernel is missing a few configuration options for Renesas
  RZ/G2M MPU as below:

  #Modify the following config from m to y.

  CONFIG_SERIAL_SH_SCI=y

  #add below configuration

  CONFIG_SERIAL_SH_SCI_CONSOLE=y
  CONFIG_SERIAL_SH_SCI_EARLYCON=y

  The above changes are required in annotations file:
  "/mantic/debian.master/config/annotations"

  code location:

  https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/mantic/tree/debian.master/config/annotations#n11372

  #Modify the following line (change 'm' to 'y')

  CONFIG_SERIAL_SH_SCI policy<{'arm64': 'y', 'armhf': 'y'}>

  #Add the following lines:

  CONFIG_SERIAL_SH_SCI_CONSOLE policy<{'arm64': 'y', 'armhf': 'y'}>
  CONFIG_SERIAL_SH_SCI_EARLYCON policy<{'arm64': 'y', 'armhf': 'y'}>

  Could you please add those configuration options to the Ubuntu kernel?

  Best Regards
  John

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


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

[Kernel-packages] [Bug 2028122] Re: Fix unreliable ethernet cable detection on I219 NIC

This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1018.18~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-linux-
nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'.
If the problem still exists, change the tag 'verification-needed-focal-
linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia-
tegra-5.15'.


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-nvidia-tegra-5.15-v2 
verification-needed-focal-linux-nvidia-tegra-5.15

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

Title:
  Fix unreliable ethernet cable detection on I219 NIC

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.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]
  Hotplugging RJ45 ethernet cable only works for one time because ACPI GPE
  wake doesn't working properly anymore.

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2028122/+subscriptions


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

[Kernel-packages] [Bug 2030924] Re: [SRU][Ubuntu 22.04.1] Unable to interpret the frequency values in cpuinfo_min_freq and cpuino_max_freq sysfs files.

This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1018.18~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-linux-
nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'.
If the problem still exists, change the tag 'verification-needed-focal-
linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia-
tegra-5.15'.


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-nvidia-tegra-5.15-v2 
verification-needed-focal-linux-nvidia-tegra-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/2030924

Title:
  [SRU][Ubuntu 22.04.1] Unable to interpret the frequency values in
  cpuinfo_min_freq and cpuino_max_freq sysfs files.

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

Bug description:
  [Impact]

  On DELL EMC PowerEdge system when Ubuntu 22.04.1 OS is Installed,
  Unable to Interpret the values in cpuinfo_max_freq and
  cpuinfo_min_freq sysfs files as per the Intel specs document.

  Steps to Reproduce:

  1. Install one CPU that supports DBS "Demand-Based Power Management".
  2. Install Ubuntu 22.04.1 OS.
  2. Enable "Logical Processor" under CPU Information menu from F2 setup.
  3. Save changes and reboot to Ubuntu 22.04.1 OS.
  4. Right click on "Computer" and select "File system" and check for the 
following CPU directories.

     /sys/devices/system/cpu/cpu0/cpufreq/cpu0
     /sys/devices/system/cpu/cpu0/cpufreq/cpu1

  5. View the Max Frequency and Min Frequency under CPU0 and CPU1 directory.
  6. The Max and Min Frequency did not match as per the Intel specs datasheet.

  Actual results:

   /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_max_freq -> 680
   /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_min_freq -> 80
   /sys/devices/system/cpu/cpu0/cpufreq/cpu0/base_frequency -> 390

   Expected results: As per Intel datasheet specification.

   /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_max_freq -> 5300 MHz
   /sys/devices/system/cpu/cpu0/cpufreq/cpu0/cpuinfo_min_freq -> 800 MHz
   /sys/devices/system/cpu/cpu0/cpufreq/cpu0/base_frequency -> 3000 MHz

  [Fix]
  cpufreq: intel_pstate: Fix scaling for hybrid-capable systems with disabled 
E-cores
  
https://github.com/torvalds/linux/commit/0fcfc9e51990246a9813475716746ff5eb98c6aa
 [github.com]

  [Test Plan]

  Same as steps to reproduce

  [ Where problems could occur ]

  This issue is seen on Intel based system under development which supports DBS 
"Demand-Based Power Management", then install Ubuntu-22.04 and boot into OS then
  check for the frequency values under /sys/devices/system/cpu/cpu0/cpufreq/cpu0
  Regression risk = Low to medium

  [ Other Info ]

  Jammy
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/cpuinfo_freq

  lunar
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/cpuinfo_freq_lunar_2

  Mantic
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/cpuinfo_freq_mantic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030924/+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 2031333] Re: Need to get fine-grained control for FAN(TFN) Participant.

This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1018.18~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-linux-
nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'.
If the problem still exists, change the tag 'verification-needed-focal-
linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia-
tegra-5.15'.


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-nvidia-tegra-5.15-v2 
verification-needed-focal-linux-nvidia-tegra-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/2031333

Title:
  Need to get fine-grained control for FAN(TFN) Participant.

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

Bug description:
  This is a public version of the following bugs:
  https://bugs.launchpad.net/bugs/1987597
  https://bugs.launchpad.net/bugs/2027754

  

  [Feature Description]
  We need Fine-grained Control of TFN participant for enabling active 2 policy 
in Linux/chrome.

  Currently, The kernel has provided __FPS table and cur__state to
  adjust the fan level as per  _FPS table .

  But there is no option to read  *_FIF (Fan Information) and _FST (Fan
  Status).*

  Once the fine-grained control is enabled, we should be able to the set
  the control value from 0-100 through Arg0 of _FSL (Fan Set Level).

  *_FST (Fan Status)*  should report current running RPM and control
  value of the FAN(TFN).

   please refer ACPI spec for more detail.

  [https://uefi.org/specs/ACPI/6.4/11_Thermal_Management/fan-
  device.html]

  [HW/SW Information]
  Hardware: Alder Lake

  Target Release: 22.04
  Target Kernel: 5.15

  
  Merged for 5.18-rc1

  f1197343f077 ACPI: fan: Add additional attributes for fine grain control
  bea2d9868ef5 ACPI: fan: Properly handle fine grain control
  d445571fa369 ACPI: fan: Optimize struct acpi_fan_fif
  00ae053a0533 ACPI: fan: Separate file for attributes creation

  Platform-independent

  [Business Justification]
  Function enabling

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031333/+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 2032164] Re: A general-proteciton exception during guest migration to unsupported PKRU machine

This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1018.18~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-linux-
nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'.
If the problem still exists, change the tag 'verification-needed-focal-
linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia-
tegra-5.15'.


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-nvidia-tegra-5.15-v2 
verification-needed-focal-linux-nvidia-tegra-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/2032164

Title:
  A general-proteciton exception during guest migration to unsupported
  PKRU machine

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged

Bug description:
  [Impact]
  When a host that supports PKRU initiates a guest that lacks PKRU support, the 
flag is enabled on the guest's fpstate.
  This information is then passed to userspace through the vcpu ioctl 
KVM_GET_XSAVE.
  However, a problem arises when the user opts to migrate the mentioned guest 
to another machine that does not support PKRU.
  In this scenario, the new host attempts to restore the guest's fpu registers.
  Nevertheless, due to the absence of PKRU support on the new host, a 
general-protection exception takes place, leading to a guest crash.

  [Fix]
  The problem is resolved by the following upstream commit:
  ad856280ddea x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0

  Additionally, a subsequent fix tackles the migration problem stemming from 
the earlier commit:
  a1020a25e697 KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES

  [Test Plan]
  1. Set up two machines: one with PKRU support and the other without.
  2. Initiate a guest that lacks PKRU support on the machine with PKRU support.
  3. Utilize libvirt to migrate the aforementioned guest to a different machine 
that lacks PKRU support.
  4. The error emerges on the destination machine:
  KVM: entry failed, hardware error 0x8021

  If you're running a guest on an Intel machine without unrestricted mode
  support, the failure can be most likely due to the guest entering an invalid
  state for Intel VT. For example, the guest maybe running in big real mode
  which is not supported on less recent Intel processors.

  EAX=86cf7970 EBX= ECX=0001 EDX=005b0036
  ESI=0087 EDI=0087 EBP=87c03e38 ESP=87c03e18
  EIP=86cf7d5e EFL=0246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   9300
  CS =f000   9b00
  SS =   9300
  DS =   9300
  FS =   9300
  GS =   9300
  LDT=   8200
  TR =   8b00
  GDT=  
  IDT=  
  CR0=6010 CR2= CR3= CR4=
  DR0= DR1= DR2= 
DR3= 
  DR6=0ff0 DR7=0400
  EFER=
  Code=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  2023-07-09T03:03:14.911750Z qemu-system-x86_64: terminating on signal 15 from 
pid 4134 (/usr/sbin/libvirtd)
  2023-07-09 03:03:15.312+: shutting down, reason=destroyed

  [Where problems could occur]
  The introduced commits will impact the guest migration process,
  potentially leading to failures and preventing the guest from operating 
successfully on the migration destination.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032164/+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 2032176] Re: Crashing with CPU soft lock on GA kernel 5.15.0.79.76 and HWE kernel 5.19.0-46.47-22.04.1

This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1018.18~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-linux-
nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'.
If the problem still exists, change the tag 'verification-needed-focal-
linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia-
tegra-5.15'.


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-nvidia-tegra-5.15-v2 
verification-needed-focal-linux-nvidia-tegra-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/2032176

Title:
  Crashing with CPU soft lock on GA kernel 5.15.0.79.76 and HWE kernel
  5.19.0-46.47-22.04.1

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  Impact:
  We had reports of VM setups which would show intermediate crashes and after 
that locking up completely. This could be reproduced with large memory setups.
  The problem seems to be that fixes to performance regressions caused more 
problems in 5.15 kernels and the full fixes are too intrusive to be backported.

  Fix:
  The following patch was recently sent to the upstream stable mailing list and 
looks to be making its way into linux-5.15.y. This changes the default value of 
kvm.tdp_mmu to off (if anyone is willing to take the risks, this can be changed 
back in config).

  Regression potential:
  VM hosts with many large memory tennants might see a performance impact which 
the TDP MMU approach tried to solve. If those did not see other problems they 
might turn this on again.

  Testcase:
  Large openstack instance (64GB memory, AMD CPU (using SVM)) with a large 
second level guest (32GB memory). Repeatedly starting and stopping the 2nd 
level guest.

  
  --- original description ---
  The crash occurred on a juju machine, and the juju agent was lost.
  The juju machine is on an openstack instance provision by juju.

  The openstack console log indicts the it is related to spin_lock and KVM MMU:
  [418200.348830]  ? _raw_spin_lock+0x22/0x30
  [418200.349588]  _raw_write_lock+0x20/0x30
  [418200.350196]  kvm_tdp_mmu_map+0x2b1/0x490 [kvm]
  [418200.351014]  kvm_mmu_notifier_invalidate_range_start+0x1ad/0x300 [kvm]
  [418200.351796]  direct_page_fault+0x206/0x310 [kvm]
  [418200.352667]  __mmu_notifier_invalidate_range_start+0x91/0x1b0
  [418200.353624]  kvm_tdp_page_fault+0x72/0x90 [kvm]
  [418200.354496]  try_to_migrate_one+0x691/0x730
  [418200.355436]  kvm_mmu_page_fault+0x73/0x1c0 [kvm]

  openstack console log: https://pastebin.canonical.com/p/spmH8r3crQ/

  syslog: https://pastebin.canonical.com/p/wFPsFD8G9n/
  The syslog was rotated after the crash occurred, so the syslog at the time of 
the initial crash was lost.

  Other juju machine with 5.15.0.79.76 kernel seems to have the same
  issues.

  We previously have a similar issue with 5.15.0-73. The juju machine
  crashed with raw_spin_lock and kvm mmu in the logs as well:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026229

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: openstack
  CloudName: openstack
  CloudPlatform: openstack
  CloudSubPlatform: metadata (http://169.254.169.254)
  Date: Mon Aug 21 08:59:46 2023
  Ec2AMI: ami-0c61
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: availability-zone-1
  Ec2InstanceType: builder-cpu4-ram72-disk20
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.19
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Aug 23 03:23 seq
   crw-rw 1 root audio 116, 33 Aug 23 03:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64

[Kernel-packages] [Bug 2033007] Re: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64

This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1018.18~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-linux-
nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'.
If the problem still exists, change the tag 'verification-needed-focal-
linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia-
tegra-5.15'.


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-nvidia-tegra-5.15-v2 
verification-needed-focal-linux-nvidia-tegra-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/2033007

Title:
  kdump doesn't work with UEFI secure boot and kernel lockdown enabled
  on ARM64

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  The kdump service operates by utilizing the kexec_file_load system call, 
which loads a new kernel image intended for subsequent execution.
  However, this process encounters a hindrance if the 
CONFIG_KEXEC_IMAGE_VERIFY_SIG option isn't enabled to facilitate signature 
verification.

  In addition, a noteworthy point is that if the kernel image is signed with a 
MOK,
  it will face rejection due to ARM64's reliance solely on the 
.builtin_trusted_keys for verification purposes.
  To enhance flexibility, it's suggested that we align the behavior on x86 
platforms.
  This alignment could potentially involve expanding the scope to encompass 
more keyrings, such as .secondary_trusted_keys and platform keyrings,
  thereby broadening the options available for verification mechanisms.

  [Fix]
  Enabling the CONFIG_KEXEC_IMAGE_VERIFY_SIG option is necessary,
  along with the incorporation of two specific commits, in order to enhance the 
capabilities of the kexec_file_load system call on ARM64.
  The commits that need to be applied are as follows:
  c903dae8941d kexec, KEYS: make the code in bzImage64_verify_sig generic
  0d519cadf751 arm64: kexec_file: use more system keyrings to verify kernel 
image signature

  [Test Plan]
  1. Set up a VM with UEFI secure boot and enabled kernel lockdown on ARM64
  2. Install 'kdump-tools'
  sudo apt install linux-crashdump
  3. Reboot and verify kdump status with 'kdump-config show'
  root@ubuntu:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0xde00
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-78-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-5.15.0-78-generic
  current state:Not ready to kdump

  kexec command:
/sbin/kexec -p -s 
--command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-79-generic 
root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  4. Check the log using 'systemctl status kdump-tools'
  Aug 24 06:08:39 ubuntu systemd[1]: Starting Kernel crash dump capture 
service...
  Aug 24 06:08:39 ubuntu kdump-tools[1750]: Starting kdump-tools:
  Aug 24 06:08:39 ubuntu kdump-tools[1755]:  * Creating symlink 
/var/lib/kdump/vmlinuz
  Aug 24 06:08:39 ubuntu kdump-tools[1755]:  * Creating symlink 
/var/lib/kdump/initrd.img
  Aug 24 06:08:39 ubuntu kdump-tools[1755]:  * /sbin/kexec -p -s 
--command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-78-generic 
root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  Aug 24 06:08:41 ubuntu kernel: [  403.301008] Lockdown: kexec: kexec of 
unsigned images is restricted; see man kernel_lockdown.7
  Aug 24 06:08:41 ubuntu kdump-tools[1755]:  * failed to load kdump kernel
  Aug 24 06:08:41 ubuntu kdump-tools: failed to load kdump kernel
  Aug 24 06:08:41 ubuntu systemd[1]: Finished Kernel crash dump capture service.

  [Where problems could occur]
  The problem is specific to kexec image signature verification on ARM64.
  This change allows additional keyrings and impacts only the ARM64 
kexec_file_load system call.

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


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

[Kernel-packages] [Bug 2033122] Re: Request backport of xen timekeeping performance improvements

This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1018.18~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-linux-
nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'.
If the problem still exists, change the tag 'verification-needed-focal-
linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia-
tegra-5.15'.


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-nvidia-tegra-5.15-v2 
verification-needed-focal-linux-nvidia-tegra-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/2033122

Title:
  Request backport of xen timekeeping performance improvements

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  Users, especially those on EC2, are encouraged to select tsc as their
  default clocksource.  However, this requires manual tuning of the
  operating system. Kvm can determine if it safe to use the tsc, and
  will default to that instead of its pvclock when appropriate.  This
  requests a backport of patch does the same for Xen instances.

  If appropriate, it's fine if this is applied to only the linux-aws
  branches.

  Not all Xen EC2 instances advertise explicit nomigrate support,
  however, on those that do we'll select tsc by default.  On the subset
  of hosts where this is advertised, users will safely default to the
  more performant clocksource.

  [Impact]
  Xen instances default to the xen clocksource which has been documented to be 
slower.  This is required for instances where the tsc is not safe to use, or 
the guest is subject to migration.  On some platforms the performance impact 
can be high, and users are encouraged to select the tsc when appropriate.  
Instead of leaving up to users to figure this out by reading a variety of 
different documents, pick the fast clocksource when it can be determined to be 
safe to do so.

  [Backport]
  Clean cherry pick.  No conflicts applying to 5.15 or 6.2.

  [Test]
  Booted EC2 xen instances with and without this patch and validated that on 
those that properly advertised the required criteria via cpuid, that the 
clocksource defaulted to tsc instead of xen.

  [Potential Regression]
  Potential is low, since only absurd configurations could lead to a problem.  
If this is considered risky, it can be applied to only linux-aws where the 
documented guidance is for users to enable tsc as the clocksource on Xen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033122/+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 2034447] Re: `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic

This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1018.18~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-linux-
nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'.
If the problem still exists, change the tag 'verification-needed-focal-
linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia-
tegra-5.15'.


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-nvidia-tegra-5.15-v2 
verification-needed-focal-linux-nvidia-tegra-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/2034447

Title:
  `refcount_t: underflow; use-after-free.` on hidon w/ 5.15.0-85-generic

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  Seeing a panic on hidon (an Nvidia H100) after booting the
  5.15.0-85-generic kernel:

  [   58.935877] [ cut here ]
  [   58.935893] refcount_t: underflow; use-after-free.
  [   58.935920] WARNING: CPU: 207 PID: 2985 at lib/refcount.c:28 
refcount_warn_saturate+0xf7/0x150
  [   58.935943] Modules linked in: x86_pkg_temp_thermal(+) intel_powerclamp 
coretemp nls_iso8859_1 rapl irdma(+) i40e qat_4xxx(+) isst_if_mbox_pci 
intel_qat pmt_telemetry pmt_crashlog idxd(+) isst_if_mmio pmt_class 
isst_if_common authenc idxd_bus intel_th_gth mei_me intel_th_pci intel_th mei 
switchtec ipmi_ssif acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid 
sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ramoops 
reed_solomon pstore_blk pstore_zone efi_pstore ip_tables x_tables autofs4 btrfs 
blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 multipath linear 
mlx5_ib ib_uverbs ib_core ast i2c_algo_bit drm_vram_helper drm_ttm_helper ttm 
drm_kms_helper raid0 mlx5_core syscopyarea sysfillrect sysimgblt 
crct10dif_pclmul fb_sys_fops crc32_pclmul ixgbe cec mlxfw ghash_clmulni_intel 
aesni_intel psample crypto_simd xfrm_algo ice rc_core cryptd tls nvme i2c_i801 
dca xhci_pci intel_pmt drm
  [   58.936077]  pci_hyperv_intf i2c_ismt i2c_smbus
  [   58.936080] QAT: Could not find a device on node 1
  [   58.936080] QAT: Could not find a device on node 1
  [   58.936080] QAT: Could not find a device on node 1
  [   58.936080] QAT: Could not find a device on node 1
  [   58.936080] QAT: Could not find a device on node 1
  [   58.936080] QAT: Could not find a device on node 1
  [   58.936083]  mdio
  [   58.936096]  xhci_pci_renesas nvme_core wmi pinctrl_emmitsburg
  [   58.936106] CPU: 207 PID: 2985 Comm: systemd-udevd Not tainted 
5.15.0-85-generic #95-Ubuntu
  [   58.936115] Hardware name: NVIDIA DGXH100/DGXH100, BIOS 1.0.7 05/08/2023
  [   58.936119] RIP: 0010:refcount_warn_saturate+0xf7/0x150
  [   58.936130] Code: eb 9e 0f b6 1d 5e e6 b9 01 80 fb 01 0f 87 f4 63 6f 00 83 
e3 01 75 89 48 c7 c7 88 c3 23 9e c6 05 42 e6 b9 01 01 e8 d8 e4 6b 00 <0f> 0b e9 
6f ff ff ff 0f b6 1d 2d e6 b9 01 80 fb 01 0f 87 b1 63 6f
  [   58.936135] RSP: 0018:ff4d5d94b2c7fa28 EFLAGS: 00010282
  [   58.936142] RAX:  RBX:  RCX: 
0027
  [   58.936146] RDX: ff314dbbbf9e0588 RSI: 0001 RDI: 
ff314dbbbf9e0580
  [   58.936149] RBP: ff4d5d94b2c7fa30 R08: 0026 R09: 
ff4d5d94b2c7f9c0
  [   58.936153] R10: 0028 R11: 0001 R12: 

  [   58.936156] R13: ff314cbfdbcb6900 R14: ff314cbfdbcb67b8 R15: 
ff314cbfd24b4000
  [   58.936159] FS:  7fadd2f6c8c0() GS:ff314dbbbf9c() 
knlGS:
  [   58.936163] CS:  0010 DS:  ES:  CR0: 80050033
  [   58.936167] CR2: 7fadd243b584 CR3: 00012972c006 CR4: 
00771ee0
  [   58.936171] DR0:  DR1:  DR2: 

  [   58.936174] DR3:  DR6: fffe07f0 DR7: 
0400
  [   58.936177] PKRU: 5554
  [   58.936179] Call Trace:
  [   58.936184]  
  [   58.936188]  ? show_trace_log_lvl+0x1d6/0x2ea
  [   58.936204]  ? show_trace_log_lvl+0x1d6/0x2ea
  [   58.936212]  ? crypto_mod_put+0x6b/0x80
  [   58.936225]  ? show_regs.part.0+0x23/0x29
  [   58.936232]  ? show_regs.cold+0x8/0xd
  [   58.936239]  ? refcount_warn_saturate+0xf7/0x150
  [   58.936246]  ? __warn+0x8c/0x100
  [   58.936255]  ? refcount_warn_saturate+0xf7/0x150
  [   58.936263]  ? report_bug+0xa4/0xd0
  [   58.936274]  ? down_trylock+0x2e/0x40
  [   58.936285]  ? handle_bug+0x39/0x90
  [   58.936296]  ?

[Kernel-packages] [Bug 2034622] Re: NVIDIA pull requests 1017-001v3

This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1018.18~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-linux-
nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'.
If the problem still exists, change the tag 'verification-needed-focal-
linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia-
tegra-5.15'.


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-nvidia-tegra-5.15-v2 
verification-needed-focal-linux-nvidia-tegra-5.15

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

Title:
  NVIDIA pull requests 1017-001v3

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

Bug description:
  Apply patches from NVIDIA pull request sent on 2023-09-04 to
  jammy:linux-nvidia-tegra.

  1017-001 V3 (2023-09-14):
  Akhil R (1):
NVIDIA: SAUCE: Revert "i2c: tegra: Allocate DMA memory for DMA engine"

  Andy Sobczyk (1):
NVIDIA: SAUCE: arm64: config: Enable MTD_UBI

  Ashish Mhetre (2):
NVIDIA: SAUCE: iommu: Don't reserve IOVA when address and size are zero
NVIDIA: SAUCE: memory: tegra: Add SID override on resume

  Kartik (1):
NVIDIA: SAUCE: mailbox: tegra-hsp: Add sm ops route_irq & set_irq

  Laxman Dewangan (2):
NVIDIA: SAUCE: config: Disable CONFIG_LOCALVERSION_AUTO
NVIDIA: SAUCE: arm64: config: recovery_chain: Enable KEXEC configs

  Mikko Perttunen (2):
thermal: tegra-bpmp: Handle errors in BPMP response
thermal/drivers/tegra-bpmp: Handle offline zones

  Mohan Kumar (1):
NVIDIA: SAUCE: arch: arm64: enable HDA_INTEL config

  Parker Newman (1):
i2c: tegra: Fix i2c-tegra DMA config option processing

  Penny Chiu (1):
NVIDIA: SAUCE: arm64: configs: Enable BINFMT_MISC support

  Sumit Gupta (2):
NVIDIA: SAUCE: driver: cpufreq: remove volatile as not needed
cpufreq: tegra194: add online/offline hooks

  Vishwaroop A (1):
NVIDIA: SAUCE: spi: spi-tegra114: retain the spi mode

  raju patel (1):
NVIDIA: SAUCE: code-owners: Populate OWNERS file

  zuyih (1):
NVIDIA: SAUCE: s25fs: Add post-get-map-id fixup for S25FS512S

  ---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2034622/+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 2035181] Re: Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7

This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1018.18~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-linux-
nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'.
If the problem still exists, change the tag 'verification-needed-focal-
linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia-
tegra-5.15'.


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-nvidia-tegra-5.15-v2 
verification-needed-focal-linux-nvidia-tegra-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/2035181

Title:
  Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Confirmed

Bug description:
  [Impact]
  Commit bdeeed3498c7 ("libbpf: fix offsetof() and container_of() to work
  with CO-RE") from stable update breaks the ubuntu_bpf test build and
  cause net:udpgro_bench.sh, net:udpgro.sh, net:veth.sh in
  ubuntu_kernel_selftests stopped working, as they require bpf selftest
  to be built first.

  The following is extracted from the commit message:
  The problem is the new offsetof() does not play nice with static asserts.
  Given that the context is a static assert (and CO-RE relocation is not
  needed at compile time), offsetof() usage can be replaced by restoring
  the original offsetof() definition as __builtin_offsetof().

  [Test Plan]
  Build bpf selftest in tools/testing/selftests with the following command:
  make headers; make -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS= \
  clean all KDIR=/usr/src/linux-headers-5.15.0-85-generic/

  The build can finish successfully with patched kernel source code.

  [Where problems could occur]
  Fix limited to testing tool, if this fix is incorrect the bpf selftest
  build will remain broken.

  
  == Original bug report ==
  Issue found with Jammy 5.15.0-85.95 in cycle 2023.09.04

  This issue does not exist with 5.15.0-83.92 in cycle 2023.08.07 (-84
  is a security cycle, in which the ubuntu_bpf test was not triggered
  there)

  Test build failed with:
    CLNG-BPF [test_maps] test_btf_map_in_map.o
    CLNG-BPF [test_maps] test_btf_newkv.o
    CLNG-BPF [test_maps] test_btf_nokv.o
    CLNG-BPF [test_maps] test_btf_skc_cls_ingress.o
    CLNG-BPF [test_maps] test_cgroup_link.o
    CLNG-BPF [test_maps] test_check_mtu.o
    CLNG-BPF [test_maps] test_cls_redirect.o
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
  make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
  stderr:
  Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from 
latest version at 'include/uapi/linux/bpf.h'
  Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs 
from latest version at 'include/uapi/linux/netlink.h'
  Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs 
from latest version at 'include/uapi/linux/if_link.h'
  progs/test_cls_redirect.c:90:2: error: static_assert expression is not an 
integral constant expression
  sizeof(flow_ports_t) !=
  ^~~
  progs/test_cls_redirect.c:91:3: note: cast that performs the conversions of a 
reinterpret_cast is not allowed in a constant expression
  offsetofend(struct bpf_sock_tuple, ipv4.dport) -
  ^
  progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
  (offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
   ^
  
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33:
 note: expanded from macro 'offsetof'
  #define offsetof(type, member)  ((unsigned long)&((type *)0)->member)
   ^
  progs/test_cls_redirect.c:95:2: error: static_assert expression is not an 
integral constant expression
  sizeof(flow_ports_t) !=
  ^~~
  progs/test_cls_redirect.c:96:3: note: cast that performs the conversions of a 
reinterpret_cast is not allowed in a constant expression
  offsetofend(struct bpf_sock_tuple, ipv6.dport) -
  ^
  progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
  (offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
   ^

[Kernel-packages] [Bug 2036675] Re: 5.15.0-85 live migration regression

This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1018.18~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-linux-
nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'.
If the problem still exists, change the tag 'verification-needed-focal-
linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia-
tegra-5.15'.


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-nvidia-tegra-5.15-v2 
verification-needed-focal-linux-nvidia-tegra-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/2036675

Title:
  5.15.0-85 live migration regression

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Fix Released

Bug description:
  
  Fixes added for LP 2032164 [0] to resolve an issue in live migration have 
  unfortunately introduced a regression, causing a previously working live 
  migration pattern to fail when tested with the 5.15.0-85 kernel from 
-proposed.

  Specifically, live migration from a PKRU-enabled host running a kernel older
  than 5.15.0-85 to a host running the 5.15.0-85 kernel will fail.  The
  destination can be either with or without PKRU; both cases fail, although
  in different ways (one hangs, the other fails due to a PCID flag issue).

  The commits in question are

  commit fa9225d64f215e8109de10f6b6c7a08f033d0ec0
  Author: Dr. David Alan Gilbert 
  Date:   Mon Aug 21 14:47:28 2023 +0800

  KVM: x86: Always enable legacy FP/SSE in allowed user XFEATURES

  commit 27a189b881278c8ad9c16b0ee05668d724352733
  Author: Leonardo Bras 
  Date:   Mon Aug 21 14:47:27 2023 +0800

  x86/kvm/fpu: Limit guest user_xfeatures to supported bits of XCR0

  
  [0]   https://bugs.launchpad.net/bugs/2032164

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036675/+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 2031982] Re: new Kernel Intel Video Driver 1280. OLD Kernel Video Driver 1366 Video Driver?

2023-10-23 Thread Launchpad Bug Tracker

[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/2031982

Title:
  new Kernel Intel Video Driver 1280.  OLD Kernel Video Driver 1366
  Video Driver?

Status in linux package in Ubuntu:
  Expired

Bug description:
  Kernel: 5.4.0-156-generic x86_64 bits: 64 compiler: gcc v: 9.4.0 
 Desktop: Cinnamon 5.2.7 wm: muffin dm: LightDM Distro: Linux Mint 
20.3 Una 
 base: Ubuntu 20.04 focal 
  Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated 
Graphics 
 vendor: Lenovo ThinkPad T420 driver: i915 v: kernel bus ID: 
00:02.0 chip ID: 8086:0126 
 Display: x11 server: X.Org 1.20.13 driver: modesetting unloaded: 
fbdev,vesa 
 resolution: 1280x720~60Hz, 1280x720~60Hz 
 OpenGL: renderer: Mesa DRI Intel HD Graphics 3000 (SNB GT2) v: 3.3 
Mesa 21.2.6 
 compat-v: 3.0 direct render: Yes 

  NEW KERNEL 1280 Resolution and OLD KERNEL RUNS High DEF at 1366
  Resolution?:

  System:Kernel: 5.4.0-99-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
Desktop: Cinnamon 4.8.6 
 wm: muffin dm: LightDM Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 
20.04 focal 

  Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated 
Graphics 
 vendor: Lenovo ThinkPad T420 driver: i915 v: kernel bus ID: 
00:02.0 chip ID: 8086:0126 
 Display: x11 server: X.Org 1.20.13 driver: modesetting unloaded: 
fbdev,vesa 
 resolution: 1366x768~60Hz, 1366x768~60Hz 
 OpenGL: renderer: Mesa DRI Intel HD Graphics 3000 (SNB GT2) v: 3.3 
Mesa 21.2.6 
 compat-v: 3.0 direct render: Yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031982/+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 1953249] Re: UVD firmware for AMD Southern Islands (GCN 1) GPUs is missing

2023-10-23 Thread Carlos Vieira

Sorry for the edits earlier, I don't know how to indicate this is
affecting 22.04 with 6.5 security fix kernel. Here's what I'm getting:

Setting up linux-image-oem-22.04d (6.5.0.1004.4) ...
Processing triggers for linux-image-6.5.0-1004-oem (6.5.0-1004.4) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.5.0-1004-oem
   ...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.5.0-1004-oem
W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega10_cap.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_cap.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi12_cap.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_6_ta.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_6_sos.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_ta.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_sos.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_cap.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_sjt_mec2.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_sjt_mec.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_9_4_3_rlc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_9_4_3_mec.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_imu.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_rlc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mec.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_me.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_pfp.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sdma_4_4_2.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sdma_6_0_3.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes1.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes1.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes_2.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vcn_4_0_3.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/smu_13_0_10.bin for module 
amdgpu
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'


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

** No longer affects: linux-signed-oem-6.5 (Ubuntu Focal)

** No longer affects: linux-signed-oem-6.5 (Ubuntu)

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

Title:
  UVD firmware for AMD Southern Islands (GCN 1) GPUs is missing

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  AMD GPU not functional on Focal with HWE kernel.

  [ Test Case ]

  See original description below.

  [ Fix ]

  Cherry-pick relevant commit from upstream linux-firmware.

  [ Where Problems Could Occur ]

  Broken graphics with AMD GPUs.

  [ Original Description ]

  Release: up-to-date Focal LTS (20.04.3)
  Package-version: linux-firmware 1.187.20
  Hardware model: [AMD/ATI] Chelsea LP [Radeon HD 7730M]

  With the latest kernel upgrade (5.4 --> 5.11, if I recall correctly),
  my laptop's discrete graphics stopped working. Looking at the logs, I
  found these messages:

  -- snippet --
  kernel: [1.492908] [drm] amdgpu: dpm initialized
  kernel: [1.492932] [drm] AMDGPU Display Connectors
  kernel: [1.492951] amdgpu :01:00.0: Direct firmware load for 
amdgpu/verde_uvd.bin failed with error -2
  kernel: [1.492954] amdgpu :01:00.0: amdgpu: amdgpu_uvd: Can't load 
firmware "amdgpu/verde_uvd.bin"
  kernel: [1.492957] [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* sw_init 
of IP block  failed -2
  kernel: [1.493196] amdgpu :01:00.0: amdgpu: amdgpu_device_ip_init 
failed
  kernel: [1.493198] amdgpu :01:00.0: amdgpu: Fatal error during GPU 
init
  kernel: [1.493200] amdgpu :01:00.0: amdgpu: amdgpu: finishing device.
  -- snippet --

  In fact,

[Kernel-packages] [Bug 2038981] Re: No external output when hotplugging to a DP monitor after the monitor went to sleep for AMD 6300 GPU

2023-10-23 Thread AceLan Kao

** Tags removed: verification-needed-jammy-linux-oem-6.1 
verification-needed-jammy-linux-oem-6.5
** Tags added: verification-done-jammy-linux-oem-6.1 
verification-done-jammy-linux-oem-6.5

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

Title:
  No external output when hotplugging to a DP monitor after the monitor
  went to sleep for AMD 6300 GPU

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

Bug description:
  [Impact]
  With ADM 6300 GPU, there is no external output when plug in a DP monitor 
after the monitor went to sleep

  [Fix]
  Mario provides a patch to fix the issue
  https://patchwork.kernel.org/project/linux-usb/list/?series=790399

  And also below commit is required
  134b8c5d8674 drm/amd: Fix detection of _PR3 on the PCIe root port

  [Test case]
  1. Boot up the system with AMD 6300 GPU and plug DP monitor on the card
  2. Unplug the DP cable and wait the monitor sleeps
  3. Plug in the DP cable again and it should wake up the monitor correctly and 
output the screen to the monitor

  [Where problems could occur]
  The PR3 patch only affects AMD dGPU and should fix AMD BOCO detection logic, 
and UCSI patch try to set the correct power supply scope which should do no 
harm to the existing systems.

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

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 Mantic)
   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/2040194

Title:
  apparmor restricts read access of user namespace mediation sysctls to
  root

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

Bug description:
  lxc and lxd currently need to determine if the apparmor restriction   
  
  on unprivileged user namespaces are being enforced, so that apparmor  
  
  restrictions won't break lxc/d, and they won't clutter the logs   
  
  by doing something like   
  

  
unshare true
  

  
  to test if the restrictions are being enforced.   
  

  
  Ideally access to this information would be restricted so that any
  
  unknown access would be logged, but lxc/d currently aren't ready for  
  
  this so in order to _not_ force lxc/d to probe whether enforcement is 
  
  enabled, open up read access to the sysctls for unprivileged user 
  
  namespace mediation.  
  
   
  https://github.com/canonical/lxd/issues/11920#issuecomment-1756110109

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

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 Mantic)
   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/2040192

Title:
  AppArmor spams kernel log with assert when auditing

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

Bug description:
  A reply to a prompt request that denies all permissions requested will throw 
the following warning, because the auditing code does not expect the request 
field to be empty when generating the audit message.   
   

  Sep 27 22:48:14 ubuntu-mantic snapd[596]: listener.go:189: Sending access 
response back to kernel: {MsgNotification:{MsgHeader:{Length:0 Version:0} 
NotificationType:APPARMOR_NOTIF_RESP Signalled:0 NoCache:1 ID:2 Error:0} 
Error:-13 Allow:0 Deny:4}
  Sep 27 22:48:14 ubuntu-mantic kernel: [ cut here ]
  Sep 27 22:48:14 ubuntu-mantic kernel: AppArmor WARN aa_audit_file: 
((!ad.request)): 
  Sep 27 22:48:14 ubuntu-mantic kernel: WARNING: CPU: 3 PID: 2082 at 
security/apparmor/file.c:268 aa_audit_file+0x2b1/0x310
  Sep 27 22:48:14 ubuntu-mantic kernel: Modules linked in: snd_seq_dummy 
snd_hrtimer snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device 
snd_timer snd soundcore binfmt_misc nls_iso8859_1 kvm_intel kvm irqbypass 
crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic 
ghash_clmulni_intel sha512_ssse3 aesni_intel virtio_gpu crypto_simd cryptd 
virtio_dma_buf drm_shmem_helper 9pnet_virtio drm_kms_helper 9pnet 
vmw_vsock_virtio_transport virtio_input vmw_vsock_virtio_transport_common 
input_leds joydev serio_raw vsock msr parport_pc ppdev lp parport drm virtiofs 
efi_pstore ip_tables x_tables autofs4 virtio_net xhci_pci ahci psmouse 
net_failover libahci xhci_pci_renesas failover virtio_rng
  Sep 27 22:48:14 ubuntu-mantic kernel: CPU: 3 PID: 2082 Comm: bash Not tainted 
6.5.0-5-generic #5+aa4.0.0+debug5-Ubuntu
  Sep 27 22:48:14 ubuntu-mantic kernel: Hardware name: QEMU Standard PC (Q35 + 
ICH9, 2009)/LXD, BIOS unknown 2/2/2022
  Sep 27 22:48:14 ubuntu-mantic kernel: RIP: 0010:aa_audit_file+0x2b1/0x310
  Sep 27 22:48:14 ubuntu-mantic kernel: Code: 3c ff ff ff e8 80 6f a8 ff 44 8b 
95 3c ff ff ff 5a 59 e9 e3 fe ff ff 48 c7 c6 98 5c 08 84 48 c7 c7 90 1a 60 84 
e8 9f da 9d ff <0f> 0b 8b 85 78 ff ff ff e9 05 ff ff ff 48 89 de 4c 89 f7 e8 b7 
f5
  Sep 27 22:48:14 ubuntu-mantic kernel: RSP: 0018:b66a82b57968 EFLAGS: 
00010246
  Sep 27 22:48:14 ubuntu-mantic kernel: RAX:  RBX: 
b66a82b57b24 RCX: 
  Sep 27 22:48:14 ubuntu-mantic kernel: RDX:  RSI: 
 RDI: 
  Sep 27 22:48:14 ubuntu-mantic kernel: RBP: b66a82b57a30 R08: 
 R09: 
  Sep 27 22:48:14 ubuntu-mantic kernel: R10:  R11: 
 R12: 
  Sep 27 22:48:14 ubuntu-mantic kernel: R13: 8b160239d800 R14: 
b66a82b57970 R15: 0001
  Sep 27 22:48:14 ubuntu-mantic kernel: FS:  7f1f7d3b3380() 
GS:8b17778c() knlGS:
  Sep 27 22:48:14 ubuntu-mantic kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Sep 27 22:48:14 ubuntu-mantic kernel: CR2: 55d4482063f0 CR3: 
000137e64000 CR4: 00750ee0
  Sep 27 22:48:14 ubuntu-mantic kernel: PKRU: 5554
  Sep 27 22:48:14 ubuntu-mantic kernel: Call Trace:
  Sep 27 22:48:14 ubuntu-mantic kernel:  
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? show_regs+0x6d/0x80
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? __warn+0x89/0x160
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? aa_audit_file+0x2b1/0x310
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? report_bug+0x17e/0x1b0
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? handle_bug+0x51/0xa0
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? exc_invalid_op+0x18/0x80
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? asm_exc_invalid_op+0x1b/0x20
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? aa_audit_file+0x2b1/0x310
  Sep 27 22:48:14 ubuntu-mantic kernel:  ? aa_audit_file+0x2b1/0x310
  Sep 27 22:48:14 ubuntu-mantic kernel:  __aa_path_perm+0xaf/0x130
  Sep 27 22:48:14 ubuntu-mantic kernel:  aa_path_perm+0xf1/0x1c0
  Sep 27 22:48:14 ubuntu-mantic kernel:  apparmor_file_open+0x1bb/0x2e0
  Sep 27 22:48:14

[Kernel-packages] [Bug 2040194] [NEW] apparmor restricts read access of user namespace mediation sysctls to root

2023-10-23 Thread John Johansen

Public bug reported:

lxc and lxd currently need to determine if the apparmor restriction 
on unprivileged user namespaces are being enforced, so that apparmor
restrictions won't break lxc/d, and they won't clutter the logs 
by doing something like 

  unshare true  

to test if the restrictions are being enforced. 

Ideally access to this information would be restricted so that any  
unknown access would be logged, but lxc/d currently aren't ready for
this so in order to _not_ force lxc/d to probe whether enforcement is   
enabled, open up read access to the sysctls for unprivileged user   
namespace mediation.
 
https://github.com/canonical/lxd/issues/11920#issuecomment-1756110109

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

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

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

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

Title:
  apparmor restricts read access of user namespace mediation sysctls to
  root

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

Bug description:
  lxc and lxd currently need to determine if the apparmor restriction   
  
  on unprivileged user namespaces are being enforced, so that apparmor  
  
  restrictions won't break lxc/d, and they won't clutter the logs   
  
  by doing something like   
  

  
unshare true
  

  
  to test if the restrictions are being enforced.   
  

  
  Ideally access to this information would be restricted so that any
  
  unknown access would be logged, but lxc/d currently aren't ready for  
  
  this so in order to _not_ force lxc/d to probe whether enforcement is 
  
  enabled, open up read access to the sysctls for unprivileged user 
  
  namespace mediation.  
  
   
  https://github.com/canonical/lxd/issues/11920#issuecomment-1756110109

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040194/+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 2040192] [NEW] AppArmor spams kernel log with assert when auditing

2023-10-23 Thread John Johansen

Public bug reported:

A reply to a prompt request that denies all permissions requested will throw 
the following warning, because the auditing code does not expect the request 
field to be empty when generating the audit message.   
 

Sep 27 22:48:14 ubuntu-mantic snapd[596]: listener.go:189: Sending access 
response back to kernel: {MsgNotification:{MsgHeader:{Length:0 Version:0} 
NotificationType:APPARMOR_NOTIF_RESP Signalled:0 NoCache:1 ID:2 Error:0} 
Error:-13 Allow:0 Deny:4}
Sep 27 22:48:14 ubuntu-mantic kernel: [ cut here ]
Sep 27 22:48:14 ubuntu-mantic kernel: AppArmor WARN aa_audit_file: 
((!ad.request)): 
Sep 27 22:48:14 ubuntu-mantic kernel: WARNING: CPU: 3 PID: 2082 at 
security/apparmor/file.c:268 aa_audit_file+0x2b1/0x310
Sep 27 22:48:14 ubuntu-mantic kernel: Modules linked in: snd_seq_dummy 
snd_hrtimer snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device 
snd_timer snd soundcore binfmt_misc nls_iso8859_1 kvm_intel kvm irqbypass 
crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic 
ghash_clmulni_intel sha512_ssse3 aesni_intel virtio_gpu crypto_simd cryptd 
virtio_dma_buf drm_shmem_helper 9pnet_virtio drm_kms_helper 9pnet 
vmw_vsock_virtio_transport virtio_input vmw_vsock_virtio_transport_common 
input_leds joydev serio_raw vsock msr parport_pc ppdev lp parport drm virtiofs 
efi_pstore ip_tables x_tables autofs4 virtio_net xhci_pci ahci psmouse 
net_failover libahci xhci_pci_renesas failover virtio_rng
Sep 27 22:48:14 ubuntu-mantic kernel: CPU: 3 PID: 2082 Comm: bash Not tainted 
6.5.0-5-generic #5+aa4.0.0+debug5-Ubuntu
Sep 27 22:48:14 ubuntu-mantic kernel: Hardware name: QEMU Standard PC (Q35 + 
ICH9, 2009)/LXD, BIOS unknown 2/2/2022
Sep 27 22:48:14 ubuntu-mantic kernel: RIP: 0010:aa_audit_file+0x2b1/0x310
Sep 27 22:48:14 ubuntu-mantic kernel: Code: 3c ff ff ff e8 80 6f a8 ff 44 8b 95 
3c ff ff ff 5a 59 e9 e3 fe ff ff 48 c7 c6 98 5c 08 84 48 c7 c7 90 1a 60 84 e8 
9f da 9d ff <0f> 0b 8b 85 78 ff ff ff e9 05 ff ff ff 48 89 de 4c 89 f7 e8 b7 f5
Sep 27 22:48:14 ubuntu-mantic kernel: RSP: 0018:b66a82b57968 EFLAGS: 
00010246
Sep 27 22:48:14 ubuntu-mantic kernel: RAX:  RBX: 
b66a82b57b24 RCX: 
Sep 27 22:48:14 ubuntu-mantic kernel: RDX:  RSI: 
 RDI: 
Sep 27 22:48:14 ubuntu-mantic kernel: RBP: b66a82b57a30 R08: 
 R09: 
Sep 27 22:48:14 ubuntu-mantic kernel: R10:  R11: 
 R12: 
Sep 27 22:48:14 ubuntu-mantic kernel: R13: 8b160239d800 R14: 
b66a82b57970 R15: 0001
Sep 27 22:48:14 ubuntu-mantic kernel: FS:  7f1f7d3b3380() 
GS:8b17778c() knlGS:
Sep 27 22:48:14 ubuntu-mantic kernel: CS:  0010 DS:  ES:  CR0: 
80050033
Sep 27 22:48:14 ubuntu-mantic kernel: CR2: 55d4482063f0 CR3: 
000137e64000 CR4: 00750ee0
Sep 27 22:48:14 ubuntu-mantic kernel: PKRU: 5554
Sep 27 22:48:14 ubuntu-mantic kernel: Call Trace:
Sep 27 22:48:14 ubuntu-mantic kernel:  
Sep 27 22:48:14 ubuntu-mantic kernel:  ? show_regs+0x6d/0x80
Sep 27 22:48:14 ubuntu-mantic kernel:  ? __warn+0x89/0x160
Sep 27 22:48:14 ubuntu-mantic kernel:  ? aa_audit_file+0x2b1/0x310
Sep 27 22:48:14 ubuntu-mantic kernel:  ? report_bug+0x17e/0x1b0
Sep 27 22:48:14 ubuntu-mantic kernel:  ? handle_bug+0x51/0xa0
Sep 27 22:48:14 ubuntu-mantic kernel:  ? exc_invalid_op+0x18/0x80
Sep 27 22:48:14 ubuntu-mantic kernel:  ? asm_exc_invalid_op+0x1b/0x20
Sep 27 22:48:14 ubuntu-mantic kernel:  ? aa_audit_file+0x2b1/0x310
Sep 27 22:48:14 ubuntu-mantic kernel:  ? aa_audit_file+0x2b1/0x310
Sep 27 22:48:14 ubuntu-mantic kernel:  __aa_path_perm+0xaf/0x130
Sep 27 22:48:14 ubuntu-mantic kernel:  aa_path_perm+0xf1/0x1c0
Sep 27 22:48:14 ubuntu-mantic kernel:  apparmor_file_open+0x1bb/0x2e0
Sep 27 22:48:14 ubuntu-mantic kernel:  security_file_open+0x2e/0x60
Sep 27 22:48:14 ubuntu-mantic kernel:  do_dentry_open+0x10d/0x530
Sep 27 22:48:14 ubuntu-mantic kernel:  vfs_open+0x33/0x50
Sep 27 22:48:14 ubuntu-mantic kernel:  do_open+0x2ed/0x470
Sep 27 22:48:14 ubuntu-mantic kernel:  ? path_init+0x59/0x3d0
Sep 27 22:48:14 ubuntu-mantic kernel:  path_openat+0x135/0x2d0
Sep 27 22:48:14 ubuntu-mantic kernel:  ? _raw_spin_unlock+0xe/0x40
Sep 27 22:48:14 ubuntu-mantic kernel:  do_filp_open+0xaf/0x170
Sep 27 22:48:14 ubuntu-mantic kernel:  do_sys_openat2+0xb3/0xe0
Sep 27 22:48:14 ubuntu-mantic kernel:  __x64_sys_openat+0x55/0xa0
Sep 27 22:48:14 ubuntu-mantic kernel:  do_syscall_64+0x59/0x90
Sep 27 22:48:14 ubuntu-mantic kernel:  ? handle_mm_fault+0xad/0x360
Sep 27 22:48:14 ubuntu-mantic kernel:  ? do_user_addr_fault+0x238/0x6b0
Sep 27 22:48:14 ubuntu-mantic kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
Sep 27 22:48:14 ubuntu-mantic kernel:  ? irqentry_exit_to_user_mode+0x17/0x20
Sep 27 22:48:14 ubuntu-mantic kernel:  ? irqentry_exit+0x43/0x50
Sep 27 22:48:14 ubuntu-mantic

[Kernel-packages] [Bug 2039868]

2023-10-23 Thread mario.limonciello

#98

The amdgpu.mcbp=0  will only help GFX9 products.  For GFX10 this is a
different problem, please open at AMD Gitlab.

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

Title:
  amdgpu reset during usage of firefox

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  Running nightly on 23.10 (since monday), I have been experiencing a
  few amdgpu resets in the past hours

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 18:26:43 2023
  HibernationDevice: RESUME=/dev/mapper/vg--ubuntu-lv--ubuntu--swap
  InstallationDate: Installed on 2022-07-04 (472 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/vg--ubuntu-lv--ubuntu--root ro rootflags=subvol=@ quiet splash 
resume=/dev/mapper/vg--ubuntu-lv--ubuntu--swap vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (3 days ago)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A0CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A0CTO1WW
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039868/+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 2038745] Re: NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox) driver installed

2023-10-23 Thread Ofloo

Upgraded day before yesterday and everything is working now.

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

Title:
  NV31 XTX cannot boot into Ubuntu 22.04.3 Desktop with upstream(inbox)
  driver installed

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

Bug description:
  [Impact]


  NV31 XTX/XTW cannot boot into Ubuntu 22.04.3 after upgrading distro to
  latest Ubuntu 22.04.3 kernel and firmware


  Not repro with NV21 XL or W6800



  [Fix]
  Cherry-pick the latest PMFW 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin



  [Other Info]


  The IMU FW included in Linux firmware package needs to be paired with
  the latest PMFW smu_13_0_0.bin for Navi31

  Jammy firmware updates only include latest IMU firmware.


  https://www.ubuntuupdates.org/package/core/jammy/main/updates/linux-
  firmware


  20220329.git681281e4-0ubuntu3.19


  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/gc_11_0_0_imu.bin
  (Missing) 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu/smu_13_0_0.bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2038745/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

2023-10-23 Thread Quinten Van Ginderen

Hy Endre,

I'm making another attempt on ubuntu 20.04 with kernel 6.1.59.
i will report my findings here, if it doesn't work then i will attempt download 
the current kernel and test it on that.

Happy patching. =D

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

Title:
  Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

Status in ideapad-laptop:
  New
Status in libinput package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed
Status in linux-signed-oem-6.5 package in Ubuntu:
  Confirmed
Status in Fedora:
  New

Bug description:
  Hello.

  Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was
  installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u)
  laptop and it was noticed that keyboard, touchpad and microphone are
  not working. The keyboard and touchpad work fine in BIOS setup and
  till GRUB (command line). It was found that when external devices such
  as keyboard, mouse and microphone are connected through USB and 3.5
  jack, respectively, these work just fine. To confirm these are not
  hardware problems, Microsoft Windows 11  (Home) was installed in
  another disk partition and observed all these working alright. Hence a
  bug is being reported to draw attention of the concerned team and I
  request them to refer this issue and do the needful at the earliest.

  Regards,
  Pradip Kumar Das

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 08:04:42 2023
  InstallationDate: Installed on 2023-08-14 (22 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland

The fixes are identified, I don't think this should wait until GNOME 45.1 
release.
This issue is totally breaking suspend on several of my test systems.  

I've backported the fixes from the GNOME 45 branch onto this PPA build:
https://launchpad.net/~superm1/+archive/ubuntu/lp2034619/+packages

I've also uploaded the mutter package into the proposed queue for SRU
team to look at.

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

** Changed in: mutter (Ubuntu Mantic)
 Assignee: (unassigned) => Mario Limonciello (superm1)

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

Title:
  [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy
  load in Wayland

Status in Linux:
  New
Status in Mutter:
  Fix Released
Status in X.Org X server:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Fix Committed
Status in linux source package in Mantic:
  Triaged
Status in mutter source package in Mantic:
  In Progress

Bug description:
  [ Impact ]

  gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems,
  sometimes when the screen locks, sometimes when launching particular
  apps.

  [ Workaround ]

  Add this to /etc/environment:

    MUTTER_DEBUG_KMS_THREAD_TYPE=user

  and then reboot.

  [ Test Plan ]

  Not all Ryzen systems (including one I just purchased) are able to
  reproduce the bug. We have no choice but to leave final verification
  to the community. Anyone affected should try locking their screen and
  verify they are not instantly returned to the login screen.

  [ Where problems could occur ]

  Anywhere in frame scheduling and particularly for mouse cursor
  movement since that's what the real-time thread exists to optimize.

  [ Original Description ]

  I have this issue on Ubuntu 23.10. Lock screen works only with an external 
monitor connected. Otherwise the session is ended and the user is logged out 
and brought to the gdm screen.
  All works in xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~beta.1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 22:32:22 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2023-09-03 (3 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2034619/+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 2040181] Re: upgrade zfs-linux to 2.2.0 final

2023-10-23 Thread Dimitri John Ledkov

** Description changed:

  [ Impact ]
  
-  * Potential data loss with zfs 2.2.0-rc3 resolved in -rc5, proposal to
+  * Potential data loss with zfs 2.2.0-rc3 resolved in -rc5, proposal to
  update to final
  
-  * Ubuntu Mantic shipped 2.2.0-rc3 with approximately 10 additional
+  * Ubuntu Mantic shipped 2.2.0-rc3 with approximately 10 additional
  cherrypicks, or kernel team created fixes that got contributed &
  accepted upstream. At the time this was the only way to get zfs working
  with  v6.5 kernels and also drop the need for shiftfs (due to zfs
  impovements). Since us shipping this package, upstream has identified
  and fixed multiple small bugfixes in the subsequent RC and the final
  releases, including one bug fix that can lead to potential data loss.
  
-  * The 2.2.0 release branch was frozen for a long time already, and
+  * The 2.2.0 release branch was frozen for a long time already, and
  outstanding number of commits of fixes that Mantic does not have is less
  than 30 small patches.
  
-  * Proposal to upgrade our build to 2.2.0 final, pick up all the
+  * Proposal to upgrade our build to 2.2.0 final, pick up all the
  regression fixes, and drop all the cherrypicked patches that enable v6.5
  support. This will give us the best kernel driver to support in the
  runnup to next Ubuntu LTS.
  
- 
  [ Test Plan ]
  
-  * autopkgtest pass
+  * autopkgtest pass
  
-  * kernel regression zfs testsuite pass
+  * kernel regression zfs testsuite pass
  
-  * zsys integration test pass
+  * zsys integration test pass
  
-  * LXD support retested
- 
+  * LXD support retested
  
  [ Where problems could occur ]
  
-  * LXD snap in edge ships zfs tooling of RC versions, there are no
+  * LXD snap in edge ships zfs tooling of RC versions, there are no
  kernel-userspace incompatiblities between  rc3 & final, but we should
  explicitely test this. And also request LXD to up 2.2.0 tooling to
  final.
  
  [ Other Info ]
-  
-  * Upstream is alerting us to the potential data loss and requesting upgrade 
to 2.2.0-rc5 or better.
+ 
+  * Upstream is alerting us to the potential data loss and requesting
+ upgrade to 2.2.0-rc5 or better.
+ 
+ 
+ [ Abbriviated changes being introduced ]
+ 
+ $ git log --oneline 4a104ac047..95785196f2 -- cmd/ lib/ module/os/linux/ | 
grep -v compat
+ 810fc49a3e Ensure we call fput when cloning fails due to different devices.
+ a80e1f1c90 zvol: Temporally disable blk-mq
+ 33d7c2d165 import: require force when cachefile hostid doesn't match on-disk
+ 8015e2ea66 Add '-u' - nomount flag for zfs set
+ c53bc3837c Improve the handling of sharesmb,sharenfs properties
+ e9dc31c74e Update the behavior of mountpoint property
+ 608741d062 Report ashift of L2ARC devices in zdb
+ 0ce1b2ca19 Invoke zdb by guid to avoid import errors
+ 0aabd6b482 ZIL: Avoid dbuf_read() in ztest_get_data()
+ a199cac6cd status: report pool suspension state under failmode=continue
+ 729507d309 Fix occasional rsend test crashes
+ 3af63683fe cmd: add 'help' subcommand to zpool and zfs
+ 9aa1a2878e Fix incorrect expected error in ztest
+ f7a07d76ee Retire z_nr_znodes
+ 54c6fbd378 zed: Allow autoreplace and fault LEDs for removed vdevs
+ 32949f2560 Relax error reporting in zpool import and zpool split
+ 63159e5bda checkstyle: fix action failures
+ e99e684b33 zed: update zed.d/statechange-slot_off.sh
+ d19304ffee zed: Add zedlet to power off slot when drive is faulted
+ 92f095a903 copy_file_range: fix fallback when source create on same txg
+ 895cb689d3 zfs_clone_range should return a descriptive error codes
+ 6bdc7259d1 libzfs: sendrecv: send_progress_thread: handle SIGINFO/SIGUSR1
+ df8c9f351d ZIL: Second attempt to reduce scope of zl_issuer_lock.
+ 0ae7bfc0a4 zpool_vdev_remove() should handle EALREADY error return
+ bd1eab16eb linux: zfs: ctldir: set [amc]time to snapshot's creation property
+ c47f0f4417 linux/copy_file_range: properly request a fallback copy on Linux 
<5.3
+ 12f2b1f65e zdb: include cloned blocks in block statistics

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

Title:
  upgrade zfs-linux to 2.2.0 final

Status in zfs-linux package in Ubuntu:
  New
Status in zfs-linux source package in Mantic:
  New

Bug description:
  [ Impact ]

   * Potential data loss with zfs 2.2.0-rc3 resolved in -rc5, proposal
  to update to final

   * Ubuntu Mantic shipped 2.2.0-rc3 with approximately 10 additional
  cherrypicks, or kernel team created fixes that got contributed &
  accepted upstream. At the time this was the only way to get zfs
  working with  v6.5 kernels and also drop the need for shiftfs (due to
  zfs impovements). Since us shipping this package, upstream has
  identified and fixed multiple small bugfixes in the subsequent RC and
  the final releases, including one bug fix that can lead to potential
  data loss.

   * The 2.2.0 release branch was frozen for a long time already, and

[Kernel-packages] [Bug 2040181] [NEW] upgrade zfs-linux to 2.2.0 final

2023-10-23 Thread Dimitri John Ledkov

Public bug reported:

[ Impact ]

 * Potential data loss with zfs 2.2.0-rc3 resolved in -rc5, proposal to
update to final

 * Ubuntu Mantic shipped 2.2.0-rc3 with approximately 10 additional
cherrypicks, or kernel team created fixes that got contributed &
accepted upstream. At the time this was the only way to get zfs working
with  v6.5 kernels and also drop the need for shiftfs (due to zfs
impovements). Since us shipping this package, upstream has identified
and fixed multiple small bugfixes in the subsequent RC and the final
releases, including one bug fix that can lead to potential data loss.

 * The 2.2.0 release branch was frozen for a long time already, and
outstanding number of commits of fixes that Mantic does not have is less
than 30 small patches.

 * Proposal to upgrade our build to 2.2.0 final, pick up all the
regression fixes, and drop all the cherrypicked patches that enable v6.5
support. This will give us the best kernel driver to support in the
runnup to next Ubuntu LTS.


[ Test Plan ]

 * autopkgtest pass

 * kernel regression zfs testsuite pass

 * zsys integration test pass

 * LXD support retested


[ Where problems could occur ]

 * LXD snap in edge ships zfs tooling of RC versions, there are no
kernel-userspace incompatiblities between  rc3 & final, but we should
explicitely test this. And also request LXD to up 2.2.0 tooling to
final.

[ Other Info ]
 
 * Upstream is alerting us to the potential data loss and requesting upgrade to 
2.2.0-rc5 or better.

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

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

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

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

Title:
  upgrade zfs-linux to 2.2.0 final

Status in zfs-linux package in Ubuntu:
  New
Status in zfs-linux source package in Mantic:
  New

Bug description:
  [ Impact ]

   * Potential data loss with zfs 2.2.0-rc3 resolved in -rc5, proposal
  to update to final

   * Ubuntu Mantic shipped 2.2.0-rc3 with approximately 10 additional
  cherrypicks, or kernel team created fixes that got contributed &
  accepted upstream. At the time this was the only way to get zfs
  working with  v6.5 kernels and also drop the need for shiftfs (due to
  zfs impovements). Since us shipping this package, upstream has
  identified and fixed multiple small bugfixes in the subsequent RC and
  the final releases, including one bug fix that can lead to potential
  data loss.

   * The 2.2.0 release branch was frozen for a long time already, and
  outstanding number of commits of fixes that Mantic does not have is
  less than 30 small patches.

   * Proposal to upgrade our build to 2.2.0 final, pick up all the
  regression fixes, and drop all the cherrypicked patches that enable
  v6.5 support. This will give us the best kernel driver to support in
  the runnup to next Ubuntu LTS.

  
  [ Test Plan ]

   * autopkgtest pass

   * kernel regression zfs testsuite pass

   * zsys integration test pass

   * LXD support retested

  
  [ Where problems could occur ]

   * LXD snap in edge ships zfs tooling of RC versions, there are no
  kernel-userspace incompatiblities between  rc3 & final, but we should
  explicitely test this. And also request LXD to up 2.2.0 tooling to
  final.

  [ Other Info ]
   
   * Upstream is alerting us to the potential data loss and requesting upgrade 
to 2.2.0-rc5 or better.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2040181/+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 2039926] Re: Error UBSAN: array-index-out-of-bounds amdgpu

2023-10-23 Thread Bug Watch Updater

** Changed in: linux
   Status: Unknown => New

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

Title:
  Error UBSAN: array-index-out-of-bounds amdgpu

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Error in boot:

  [8.597520] UBSAN: array-index-out-of-bounds in 
/build/linux-D15vQj/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4
  [8.597527] index 7 is out of range for type 
'ATOM_Polaris_SCLK_Dependency_Record [1]'

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-generic 6.5.0.9.11
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 09:28:16 2023
  InstallationDate: Installed on 2022-10-12 (373 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=9edc5478-c6c2-4cf3-9de8-01ccb697fb9e ro quiet splash audit=0 
mitigations=off amdgpu.ppfeaturemask=0x vt.global_cursor_default=0 
loglevel=2 rd.systemd.show_status=false rd.udev.log-prority=3 
sysrq_always_enabled=1 audit=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (6 days ago)
  dmi.bios.date: 07/11/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: D3EMW08.110
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: D3F3-EM
  dmi.board.vendor: MEDION
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDION
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrD3EMW08.110:bd07/11/2014:br4.6:svnMEDION:pnD3F3-EM:pvr1.0:rvnMEDION:rnD3F3-EM:rvr1.0:cvnMEDION:ct3:cvr:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: D3F3-EM
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDION

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039926/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

2023-10-23 Thread akshay

I have bought five new AMD laptops, now this issue is hitting me hard.
What is the estimated time for fixing this ?

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

Title:
  Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

Status in ideapad-laptop:
  New
Status in libinput package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed
Status in linux-signed-oem-6.5 package in Ubuntu:
  Confirmed
Status in Fedora:
  New

Bug description:
  Hello.

  Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was
  installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u)
  laptop and it was noticed that keyboard, touchpad and microphone are
  not working. The keyboard and touchpad work fine in BIOS setup and
  till GRUB (command line). It was found that when external devices such
  as keyboard, mouse and microphone are connected through USB and 3.5
  jack, respectively, these work just fine. To confirm these are not
  hardware problems, Microsoft Windows 11  (Home) was installed in
  another disk partition and observed all these working alright. Hence a
  bug is being reported to draw attention of the concerned team and I
  request them to refer this issue and do the needful at the earliest.

  Regards,
  Pradip Kumar Das

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 08:04:42 2023
  InstallationDate: Installed on 2023-08-14 (22 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+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 2036273] Re: 5.15+ GCE Instances are unable to create fb0 with virt mon attached

2023-10-23 Thread Jawed Abbasi

Hi Pete

I provided an update on out internal case, hope that was helpful.

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

Title:
  5.15+ GCE Instances are unable to create fb0 with virt mon attached

Status in linux-gcp package in Ubuntu:
  New

Bug description:
  This is a public facing LP issue to address the content in Canonical's
  SF#00366439.

  Summary:

  Post 18.04 ( or 20.04 prior to moving to 5.15 ), efifb fails to stand up fb0. 
It is assigned, but fb0 is never created, nor are there any errors that I 
noted. Here is an example from a focal using linux-gcp
  ---
  5.15.0-1041-gcp #49~20.04.1-Ubuntu SMP
  kyler_hornor@kyler-focal:~$ sudo dmesg | grep efifb
  [0.925827] pci :00:05.0: BAR 0: assigned to efifb
  ---

  If you then install the generic HWE kernel and reboot, you can see
  that fb0 is successfully summoned:

  ---
  5.15.0-83-generic #92~20.04.1-Ubuntu SMP
  kyler_hornor@kyler-focal:~$ sudo dmesg | grep efifb
  [2.128815] pci :00:05.0: BAR 0: assigned to efifb
  [3.021819] efifb: probing for efifb
  [3.022511] efifb: framebuffer at 0xc000, using 6076k, total 6075k
  [3.023925] efifb: mode is 1920x1080x24, linelength=5760, pages=1
  [3.025382] efifb: scrolling: redraw
  [3.026347] efifb: Truecolor: size=0:8:8:8, shift=0:16:8:0
  ---

  and finally, using linux-gcp-lts on 20.04, it does work (as it's 5.4):
  ---
  5.4.0-1112-gcp #121-Ubuntu SMP
  kyler_hornor@kyler-focal:~$ sudo dmesg | grep efifb
  [0.834541] pci :00:05.0: BAR 0: assigned to efifb
  [1.057258] efifb: probing for efifb
  [1.058182] efifb: framebuffer at 0xc000, using 6076k, total 6075k
  [1.059210] efifb: mode is 1920x1080x24, linelength=5760, pages=1
  [1.060203] efifb: scrolling: redraw
  [1.060722] efifb: Truecolor: size=0:8:8:8, shift=0:16:8:0
  ---

  So some linux-gcp backport or config seems to be breaking this.

  Supplementary to this, the framebuffer can not be leveraged by X and
  throws a fatal error around the time shadow is loaded. This part is
  replicable on -generic, as well as on debian using gdm3/X, so this is
  likely an upstream problem. I tried disabling shadow with an X conf,
  but as it uses 24bppp, it forces it.

  
  For the scope of this LP, we need to figure out the -gcp specific breakage. 
I've reached out to google to see if we can get some contacts on the virt mon 
team to push the other aspect forward.

  Replication:
  Launch any ubuntu 20.04+ GCE instance with the "Display Device" option 
enabled. 

  Expected Behavior:
  We should see the above output in dmesg and also observe /dev/fb0 being 
created.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2036273/+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 2036742] Re: amdgpu crash on Mantic

I'd say let's track the out of bounds stuff in this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039926

** Summary changed:

- amdgpu crash on Mantic 
+ VI dGPU fails to initialize on Intel platforms w/ 5.14+

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

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

Title:
  VI dGPU fails to initialize on Intel platforms w/ 5.14+

Status in linux package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  Booting from USB the latest Mantic Desktop daily image (2023-09-20),
  just after the initial logs, nothing is displayed on screen. The
  system is still alive since _autoinstall_ works as intended. Once
  provisioned, the problem is still present.

  It seems related to https://bugs.launchpad.net/ubuntu/+source/linux-
  firmware/+bug/2029396 .

  dmesg attached.

  [Test Case]

  Live boot Ubuntu Mantic Desktop canary (2023-09-19)

  [Where Problems Could Occur]

  Dell Optiplex 5090
  - Intel Core(TM) i7-11700
  - Advanced Micro Devices, Inc. [AMD/ATI] - 1002:699f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036742/+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 2039926] Re: Error UBSAN: array-index-out-of-bounds amdgpu

** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2874
   https://gitlab.freedesktop.org/drm/amd/-/issues/2874

** Also affects: linux via
   https://gitlab.freedesktop.org/drm/amd/-/issues/2874
   Importance: Unknown
   Status: Unknown

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

Title:
  Error UBSAN: array-index-out-of-bounds amdgpu

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Error in boot:

  [8.597520] UBSAN: array-index-out-of-bounds in 
/build/linux-D15vQj/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4
  [8.597527] index 7 is out of range for type 
'ATOM_Polaris_SCLK_Dependency_Record [1]'

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-generic 6.5.0.9.11
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 09:28:16 2023
  InstallationDate: Installed on 2022-10-12 (373 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=9edc5478-c6c2-4cf3-9de8-01ccb697fb9e ro quiet splash audit=0 
mitigations=off amdgpu.ppfeaturemask=0x vt.global_cursor_default=0 
loglevel=2 rd.systemd.show_status=false rd.udev.log-prority=3 
sysrq_always_enabled=1 audit=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (6 days ago)
  dmi.bios.date: 07/11/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: D3EMW08.110
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: D3F3-EM
  dmi.board.vendor: MEDION
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDION
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrD3EMW08.110:bd07/11/2014:br4.6:svnMEDION:pnD3F3-EM:pvr1.0:rvnMEDION:rnD3F3-EM:rvr1.0:cvnMEDION:ct3:cvr:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: D3F3-EM
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDION

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039926/+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 2040102] Re: kernel warning when open the lid

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=217947
   Importance: Unknown
   Status: Unknown

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

Title:
  kernel warning when open the lid

Status in Linux:
  Unknown
Status in linux-signed-hwe-6.2 package in Ubuntu:
  New

Bug description:
  I always put my thinkpad neo 14 to idle, close the lid, but not
  sleep/suspend, when I open the lid and login, I can see below warning
  from kernel in journal. If my memory is correct, when kernel is still
  around 5.15 or previous hwe(might be 6.0), I just see the first
  message about psmouse, no kernel warning.

  Oct 22 19:52:52 kernel: psmouse serio1: TrackPoint at isa0060/serio1/input0 
lost synchronization, throwing 1 bytes away.
  Oct 22 19:52:52 kernel: [ cut here ]
  Oct 22 19:52:52 kernel: WARNING: CPU: 15 PID: 1674 at 
drivers/acpi/platform_profile.c:74 platform_profile_show+0xae/0xf0 
[platform_profile]
  Oct 22 19:52:52 kernel: Modules linked in: btrfs blake2b_generic xor raid6_pq 
ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs cpuid tls tcp_diag inet_diag 
pppoe pppox rfcomm veth nft_masq dummy bridge stp llc nvme_fabrics 
nf_conntrack_netbio
  s_ns nf_conntrack_broadcast ccm vhost_vsock vmw_vsock_virtio_transport_common 
vhost vhost_iotlb vsock nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib 
nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat 
nf_nat nf_co
  nntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables libcrc32c nfnetlink 
cmac algif_hash algif_skcipher af_alg overlay bnep binfmt_misc zstd snd_ctl_led 
snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi 
snd_sof_probes sn
  d_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic btusb uvcvideo 
btrtl videobuf2_vmalloc btbcm videobuf2_memops btintel videobuf2_v4l2 btmtk 
videodev bluetooth videobuf2_common ecdh_generic mc ecc snd_soc_dmic 
snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel
  Oct 22 19:52:52 kernel:  soundwire_generic_allocation soundwire_cadence 
snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils 
snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi 
soundwire_bus intel_tcc_cooling snd_soc_core x86_pkg_temp_thermal snd_compress 
intel_powerclamp ac97_bus snd_pcm_dmaengine coretemp snd_hda_intel kvm_intel 
snd_intel_dspcfg zfs(PO) i915 snd_intel_sdw_acpi kvm snd_hda_codec zunicode(PO) 
snd_hda_core snd_hwdep zzst
  d(O) irqbypass thinkpad_acpi iwlmvm drm_buddy snd_pcm crct10dif_pclmul nvram 
zlua(O) ttm polyval_clmulni polyval_generic snd_seq_midi drm_display_helper 
zavl(PO) mac80211 ghash_clmulni_intel snd_seq_midi_event cec sha512_ssse3 
icp(PO) snd_rawmidi nls_iso8859_1 rc_core aesni_intel snd_seq 
processor_thermal_device_pci libarc4 drm_kms_helper crypto_simd zcommon(PO) 
snd_seq_device processor_thermal_device i2c_algo_bit cryptd mei_hdcp iwlwifi 
mei_pxp snd_timer znvpair(PO) proces
  sor_thermal_rfim syscopyarea cmdlinepart pmt_telemetry
  Oct 22 19:52:52 kernel:  rapl spi_nor snd intel_rapl_msr pmt_class input_leds 
processor_thermal_mbox sysfillrect mei_me think_lmi spl(O) cfg80211 
processor_thermal_rapl intel_cstate serio_raw firmware_attributes_class 
wmi_bmof mtd sysimgbl
  t soundcore mei intel_rapl_common igen6_edac intel_vsec ledtrig_audio mac_hid 
int3403_thermal int3400_thermal intel_hid soc_button_array platform_profile 
int340x_thermal_zone acpi_thermal_rel acpi_tad sparse_keymap acpi_pad 
sch_fq_codel ms
  r parport_pc lz4 lz4_compress ppdev lp drm zram parport efi_pstore autofs4 
nvme ucsi_acpi spi_intel_pci i2c_i801 xhci_pci typec_ucsi nvme_core video 
crc32_pclmul psmouse thunderbolt spi_intel i2c_smbus xhci_pci_renesas typec 
nvme_common wm
  i pinctrl_tigerlake
  Oct 22 19:52:52 kernel: CPU: 15 PID: 1674 Comm: power-profiles- Tainted: P
W  O   6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 22 19:52:52 kernel: Hardware name: LENOVO 21DN001ACD/21DN001ACD, BIOS 
R1RET48W(1.20) 03/06/2023
  Oct 22 19:52:52 kernel: RIP: 0010:platform_profile_show+0xae/0xf0 
[platform_profile]
  Oct 22 19:52:52 kernel: Code: e7 e8 f6 bb 80 df 48 98 48 8b 55 e8 65 48 2b 14 
25 28 00 00 00 75 33 48 83 c4 10 5b 41 5c 5d 31 d2 31 f6 31 ff c3 cc cc cc cc 
<0f> 0b 48 c7 c0 fb ff ff ff eb d3 48 c7 c7 60 61 54 c0 e8 6b 0e 36
  Oct 22 19:52:52 kernel: RSP: 0018:a5a5c635bce0 EFLAGS: 00010282
  Oct 22 19:52:52 kernel: RAX: ed0fbddb RBX:  RCX: 

  Oct 22 19:52:52 kernel: RDX:  RSI:  RDI: 

  Oct 22 19:52:52 kernel: RBP: a5a5c635bd00 R08: 8cf841f7a880 R09: 
0001
  Oct 22 19:52:52 kernel: R10:  R11:  R12: 
8cf9ddb43000
  Oct 22 19:52:52 kernel: R13: 0001 R14: 8cf8426d40a0 R15:

[Kernel-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems

** Tags removed: foundations-todo

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

Title:
  mantic images after 20230917 are failing to deploy with failure to
  mount root and kernel filesystems

Status in cloud-images:
  Fix Released
Status in maas-images:
  Fix Released
Status in The Ubuntu-power-systems project:
  Invalid
Status in Release Notes for Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in util-linux package in Ubuntu:
  Fix Released
Status in linux source package in Mantic:
  Invalid
Status in systemd source package in Mantic:
  Invalid
Status in util-linux source package in Mantic:
  Fix Released

Bug description:
  Mantic arm64 deploys started failing on Sept 18th with:

  [   41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root 
and Kernel File Systems...
   Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File 
Systems...
  [   41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug 
All udev Devices...
   Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev 
Devices...
  [   41.964758] systemd[1]: Started systemd-journald.service - Journal Service.
  [[0;32m  OK  [0m] Started [0;1;39msystemd-journald.service[0m - Journal 
Service.
  [[0;32m  OK  [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages 
File System.
  [[0;32m  OK  [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message 
Queue File System.
  [[0;32m  OK  [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug 
File System.
  [[0;32m  OK  [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace 
File System.
  [[0;32m  OK  [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console 
keyboard layout.
  [[0;32m  OK  [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static 
Device Nodes.
  [[0;32m  OK  [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or 
progress polling.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel 
Module configfs.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel 
Module dm_mod.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel 
Module drm.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel 
Module efi_pstore.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel 
Module fuse.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel 
Module loop.
  [[0;32m  OK  [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load 
Kernel Modules.
  [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and 
Kernel File Systems.
  See 'systemctl status systemd-remount-fs.service' for details.

  After this many other services and cloud-init fails. See the full
  kopter-0918.log. For comparison, a log from the prior day's test is
  also attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2037417/+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 2018128] Re: Apport does not collect all logs when the package is HWE kernel

Maybe it doesn't matter if the kernel hook is triggered for those since
they never get bug reports anyways :-)

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

Title:
  Apport does not collect all logs when the package is HWE kernel

Status in apport package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 22.04 LTS with kernel 5.19.0-41-generic

  When filing bugs against the package 'linux' apport collects all the logs 
needed
  to the kernel

  But in case the user is not on stock kernel anymore and has the HWE kernel
  apport only imports 2 logs Dependencies.txt + ProcCpuInfoMinimal.txt

  and forwards the package 'linux' towards linux-signed-hwe-5.19 (in my
  case)

  would it be possible to make apport collect all the logs needed in all
  kernel cases?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.4
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 29 05:25:30 2023
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2018128/+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 2002226] Re: Add support for kernels compiled with CONFIG_EFI_ZBOOT

** Tags removed: foundations-todo

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

Title:
  Add support for kernels compiled with CONFIG_EFI_ZBOOT

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-unsigned package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in grub2 source package in Focal:
  Invalid
Status in grub2-unsigned source package in Focal:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in grub2 source package in Jammy:
  Invalid
Status in grub2-unsigned source package in Jammy:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in grub2 source package in Lunar:
  Invalid
Status in grub2-unsigned source package in Lunar:
  Invalid
Status in linux source package in Lunar:
  Invalid

Bug description:
  [Impact]
  Arm64 kernels compiled with CONFIG_EFI_ZBOOT=y don't use the 
ARM64_IMAGE_MAGIC ('ARM\x64') but LINUX_PE_MAGIC (0x818223cd) in the PE Header. 
Our GRUB fails to boot such a kernel.

  We should eliminate the following check:

  grub-core/loader/efi/linux.c:75:
    if (lh->magic != GRUB_LINUX_ARCH_MAGIC_SIGNATURE)
  return grub_error(GRUB_ERR_BAD_OS, "invalid magic number");

  This will allow any EFI binary to be run using the linux command.

  [Test plan]
  * check that grub and EFI based ARM64 machines boot
  * check that MAAS deployment works

  [Where problems could occur]
  * Non-EFI bootloaders want to boot with regular vmlinuz.gz. If one is using 
piboot, u-boot, abootimg likely one still wants to build Image.gz and have 
CONFIG_EFI_ZBOOT disabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2002226/+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 1990964] Re: FTBFS on kinetic

** Tags removed: foundations-todo

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

Title:
  FTBFS on kinetic

Status in linux package in Ubuntu:
  Fix Released
Status in strace package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in strace source package in Kinetic:
  Won't Fix

Bug description:
  As can be seen in [1], strace FTBFS in kinetic: this is caused by the
  kernel headers (linux-libc-dev) which do not define F_GETLK64 and
  other on 64b builds because the kernel contains a bogus commit
  (306f7cc1e906 "uapi: always define F_GETLK64/F_SETLK64/F_SETLKW64 in
  fcntl.h"). This commit actually did the opposite of what it was
  supposed to do, namely defining those macros even on 64b builds. There
  is an attempt here to fix this which was not merged yet:
  
https://lore.kernel.org/lkml/cajf2gtqtnmoeb62-63ou8y4dbrdym7iztdtfluxx9u0ltwu...@mail.gmail.com/T/

  [1]: https://launchpadlibrarian.net/625441996/buildlog_ubuntu-kinetic-
  amd64.strace_5.16-0ubuntu4_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990964/+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 2018128] Re: Apport does not collect all logs when the package is HWE kernel

List of kernel source packages as of 2023/10/23.

** Attachment added: "ubuntu-kernels.list"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018128/+attachment/5712664/+files/ubuntu-kernels.list

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

Title:
  Apport does not collect all logs when the package is HWE kernel

Status in apport package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 22.04 LTS with kernel 5.19.0-41-generic

  When filing bugs against the package 'linux' apport collects all the logs 
needed
  to the kernel

  But in case the user is not on stock kernel anymore and has the HWE kernel
  apport only imports 2 logs Dependencies.txt + ProcCpuInfoMinimal.txt

  and forwards the package 'linux' towards linux-signed-hwe-5.19 (in my
  case)

  would it be possible to make apport collect all the logs needed in all
  kernel cases?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.4
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 29 05:25:30 2023
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2018128/+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 2018128] Re: Apport does not collect all logs when the package is HWE kernel

I don't think we can do this with a regex. There are linux- package
that are not kernels.

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

Title:
  Apport does not collect all logs when the package is HWE kernel

Status in apport package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 22.04 LTS with kernel 5.19.0-41-generic

  When filing bugs against the package 'linux' apport collects all the logs 
needed
  to the kernel

  But in case the user is not on stock kernel anymore and has the HWE kernel
  apport only imports 2 logs Dependencies.txt + ProcCpuInfoMinimal.txt

  and forwards the package 'linux' towards linux-signed-hwe-5.19 (in my
  case)

  would it be possible to make apport collect all the logs needed in all
  kernel cases?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.4
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 29 05:25:30 2023
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2018128/+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 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

2023-10-23 Thread Heitor Alves de Siqueira

As this will need fixing in the development release, I'll re-subscribe
the ubuntu-sponsors team. After this has been fixed there, we can take a
look at the SRU for the other stable releases.

Thanks, Chengen!

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

Title:
  The dump file parsing issue arises from structural changes in Linux
  kernel 6.2

Status in crash package in Ubuntu:
  In Progress
Status in crash source package in Jammy:
  In Progress
Status in crash source package in Lunar:
  In Progress
Status in crash source package in Mantic:
  In Progress

Bug description:
  [Impact]
  Linux kernel 6.2 includes patches with structural changes that may render the 
crash utility unable to parse the dump file.
  ==
  d122019bf061 mm: Split slab into its own type
  401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
  07f910f9b729 mm: Remove slab from struct page
  0d9b1ffefabe arm64: mm: make vabits_actual a build time constant if possible
  e36ce448a08d mm/slab: use kmalloc_node() for off slab freelist_idx_t array 
allocation
  130d4df57390 mm/sl[au]b: rearrange struct slab fields to allow larger rcu_head
  ac3b43283923 module: replace module_layout with module_memory
  b69f0aeb0689 pid: Replace struct pid 1-element array with flex-array
  ==

  [Fix]
  It is advisable to adopt commits that address the structural changes issue.
  ==
  [v8.0.0]
  14f8c460473c memory: Handle struct slab changes on Linux 5.17-rc1 and later
  5f390ed811b0 Fix for "kmem -s|-S" and "bt -F[F]" on Linux 5.17-rc1
  b89f9ccf511a Fix for "kmem -s|-S" on Linux 5.17+ with CONFIG_SLAB
  [v8.0.1]
  f02c8e87fccb arm64: use TCR_EL1_T1SZ to get the correct info if vabits_actual 
is missing
  [v8.0.2]
  d83df2fb66cd SLUB: Fix for offset change of struct slab members on Linux 
6.2-rc1
  df1f0cba729f x86_64: Fix for move of per-cpu variables into struct pcpu_hot
  120d6e89fc14 SLAB: Fix for "kmem -s|-S" options on Linux 6.1 and later
  ac96e17d1de5 SLAB: Fix for "kmem -s|-S" options on Linux 6.2-rc1 and later
  7750e61fdb2a Support module memory layout change on Linux 6.4
  88580068b7dd Fix failure of gathering task table on Linux 6.5-rc1 and later
  4ee56105881d Fix compilation error due to new strlcpy function that glibc 
added
  ==

  [Test Plan]
  1. Install the required packages and then proceed to reboot the machine.
  # sudo apt install crash linux-crashdump -y
  # reboot
  2. To check the status of kdump, use the `kdump-config show` command.
  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x6400
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-6.2.0-33-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0 
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll 
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  3. To trigger a crash dump forcefully, execute the `echo c | sudo tee 
/proc/sysrq-trigger` command.
  4. Download the kernel .ddeb file, which will be used for analyzing the dump 
file.
  # sudo -i
  # cd /var/crash
  # pull-lp-ddebs linux-image-unsigned-$(uname -r)
  # dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
  5. Utilize the "crash" utility to parse and analyze the dump file.
  crash 8.0.0
  Copyright (C) 2002-2021  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011, 2020-2021  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  Copyright (C) 2015, 2021  VMware, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
   
  WARNING: VA_BITS: calculated: 46  vmcoreinfo: 48
  GNU gdb (GDB) 10.2
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "aarch64-unknown-linux-gnu".
  Type "show configuration" for

[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

2023-10-23 Thread Endre Olah

Copying the stock config file to .config, did not cause compilation
issues, but did not change anything at the end. I have the feeling that
I was not downloading the right kernel source, even if I have followed
the instruction on the Ubuntu website.

At my latest trial the installed kernel appears as 6.1.6+, what is weird
as the stock kernel is 6.5.3 which appears as 6.5.0-9-generic. This is
also not really clear why the coding is not following the official base
kernel coding.

I am ok to wait for the solution, as without the background knowledge of
what I am doing, this seems to be an impossible mission. And I am not
Tom Cruise either. :D

So, I leave making the solution to the professionals. :D

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

Title:
  Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop

Status in ideapad-laptop:
  New
Status in libinput package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed
Status in linux-signed-oem-6.5 package in Ubuntu:
  Confirmed
Status in Fedora:
  New

Bug description:
  Hello.

  Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was
  installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u)
  laptop and it was noticed that keyboard, touchpad and microphone are
  not working. The keyboard and touchpad work fine in BIOS setup and
  till GRUB (command line). It was found that when external devices such
  as keyboard, mouse and microphone are connected through USB and 3.5
  jack, respectively, these work just fine. To confirm these are not
  hardware problems, Microsoft Windows 11  (Home) was installed in
  another disk partition and observed all these working alright. Hence a
  bug is being reported to draw attention of the concerned team and I
  request them to refer this issue and do the needful at the earliest.

  Regards,
  Pradip Kumar Das

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 08:04:42 2023
  InstallationDate: Installed on 2023-08-14 (22 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+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 2018128] Re: Apport does not collect all logs when the package is HWE kernel

The source_linux.py package hook could be moved to general-hooks (where
it is always run) and do a regular expression check for the source
package name.

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

Title:
  Apport does not collect all logs when the package is HWE kernel

Status in apport package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 22.04 LTS with kernel 5.19.0-41-generic

  When filing bugs against the package 'linux' apport collects all the logs 
needed
  to the kernel

  But in case the user is not on stock kernel anymore and has the HWE kernel
  apport only imports 2 logs Dependencies.txt + ProcCpuInfoMinimal.txt

  and forwards the package 'linux' towards linux-signed-hwe-5.19 (in my
  case)

  would it be possible to make apport collect all the logs needed in all
  kernel cases?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.4
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 29 05:25:30 2023
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2018128/+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 2036742] Re: amdgpu crash on Mantic

Great!  Thanks I've posted it for review.

https://lore.kernel.org/amd-
gfx/20231023134514.144863-1-mario.limoncie...@amd.com/T/#u

Yes the "UBSAN: array-index-out-of-bounds" traces are to be fixed in
6.7.  If you want to pull those patches early I can point you at them.

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

Title:
  amdgpu crash on Mantic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  Booting from USB the latest Mantic Desktop daily image (2023-09-20),
  just after the initial logs, nothing is displayed on screen. The
  system is still alive since _autoinstall_ works as intended. Once
  provisioned, the problem is still present.

  It seems related to https://bugs.launchpad.net/ubuntu/+source/linux-
  firmware/+bug/2029396 .

  dmesg attached.

  [Test Case]

  Live boot Ubuntu Mantic Desktop canary (2023-09-19)

  [Where Problems Could Occur]

  Dell Optiplex 5090
  - Intel Core(TM) i7-11700
  - Advanced Micro Devices, Inc. [AMD/ATI] - 1002:699f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036742/+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 2036450] Re: Azure: Update CIFS to v6.5

2023-10-23 Thread Tim Gardner

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

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

Title:
  Azure: Update CIFS to v6.5

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  Microsoft has requested this patch set to update CIFS and smbfs to the
  Linux kernel version 6.5.

  [Test Plan]

  Microsoft has tested with positive results.

  [Regression Potential]

  This is a huge patch set. The potential exists for corruption,
  connection instabilities, or other cifs related maladies.

  [Other Info]

  SF: #00365185

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2036450/+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 2018128] Re: Apport does not collect all logs when the package is HWE kernel

Or the kernel package itself needs to provide the symlink.

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

Title:
  Apport does not collect all logs when the package is HWE kernel

Status in apport package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 22.04 LTS with kernel 5.19.0-41-generic

  When filing bugs against the package 'linux' apport collects all the logs 
needed
  to the kernel

  But in case the user is not on stock kernel anymore and has the HWE kernel
  apport only imports 2 logs Dependencies.txt + ProcCpuInfoMinimal.txt

  and forwards the package 'linux' towards linux-signed-hwe-5.19 (in my
  case)

  would it be possible to make apport collect all the logs needed in all
  kernel cases?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.4
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 29 05:25:30 2023
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2018128/+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 2018128] Re: Apport does not collect all logs when the package is HWE kernel

This needs some rework. Kernel source package names change a lot and
with every release so static symlinks will not work. We might have to
query LP to get up-to-date kernel source information.

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

Title:
  Apport does not collect all logs when the package is HWE kernel

Status in apport package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 22.04 LTS with kernel 5.19.0-41-generic

  When filing bugs against the package 'linux' apport collects all the logs 
needed
  to the kernel

  But in case the user is not on stock kernel anymore and has the HWE kernel
  apport only imports 2 logs Dependencies.txt + ProcCpuInfoMinimal.txt

  and forwards the package 'linux' towards linux-signed-hwe-5.19 (in my
  case)

  would it be possible to make apport collect all the logs needed in all
  kernel cases?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.4
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 29 05:25:30 2023
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2018128/+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 2036742] Re: amdgpu crash on Mantic

2023-10-23 Thread Paolo Gentili

Ok the patch fixes the problem! I can see a stack trace still but it's
probably related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036742/comments/13
?

Thanks!

** Attachment added: "dmesg-mantic-6.5.3-patched"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036742/+attachment/5712661/+files/dmesg-mantic-6.5.3-patched

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

Title:
amdgpu crash on Mantic

Status in linux package in Ubuntu:
Confirmed

Bug description:
[Impact]

Booting from USB the latest Mantic Desktop daily image (2023-09-20),
just after the initial logs, nothing is displayed on screen. The
system is still alive since _autoinstall_ works as intended. Once
provisioned, the problem is still present.

It seems related to https://bugs.launchpad.net/ubuntu/+source/linux-
firmware/+bug/2029396 .

dmesg attached.

[Test Case]

Live boot Ubuntu Mantic Desktop canary (2023-09-19)

[Where Problems Could Occur]

Dell Optiplex 5090
- Intel Core(TM) i7-11700
- Advanced Micro Devices, Inc. [AMD/ATI] - 1002:699f

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036742/+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 2040157] Re: Unable to use nvme drive to install Ubuntu 23.10

The upstream fix for this is:

commit 0e4cac557531a4c93de108d9ff11329fcad482ff
[PATCH] misc: rtsx: Fix some platforms can not boot and move the l1ss
 judgment to probe

commit 101bd907b424 ("misc: rtsx: judge ASPM Mode to set PETXCFG Reg")
some readers no longer force #CLKREQ to low
when the system need to enter ASPM.
But some platform maybe not implement complete ASPM?
it causes some platforms can not boot

Like in the past only the platform support L1ss we release the #CLKREQ.
Move the judgment (L1ss) to probe,
we think read config space one time when the driver start is enough

Fixes: 101bd907b424 ("misc: rtsx: judge ASPM Mode to set PETXCFG Reg")
Cc: stable 
Reported-by: Paul Grandperrin 
Signed-off-by: Ricky Wu 
Tested-By: Jade Lovelace 
Link: https://lore.kernel.org/r/37b1afb997f14946a8784c73d1f9a...@realtek.com
Signed-off-by: Greg Kroah-Hartman  High

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

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

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

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

Title:
  Unable to use nvme drive to install Ubuntu 23.10

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged
Status in linux source package in Lunar:
  Triaged
Status in linux source package in Mantic:
  Confirmed

Bug description:
  The 6.5 kernel in the 23.10 installer ISO is unable to work with an
  NVME drive in the laptop, and it is not possible to install Ubuntu. It
  might be related to Kernel bug
  https://bugzilla.kernel.org/show_bug.cgi?id=217802 fixed in 6.5.6.

  dmesg:
  [   42.116742] nvme nvme0: controller is down; will reset: CSTS=0x, 
PCI_STATUS=0x
  [   42.116764] nvme nvme0: Does your device have a faulty power saving mode 
enabled?
  [   42.116769] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 
pcie_aspm=off" and report a bug
  [   42.149334] nvme0n1: I/O Cmd(0x2) @ LBA 370339840, 8 blocks, I/O Error 
(sct 0x3 / sc 0x71) 
  [   42.149357] I/O error, dev nvme0n1, sector 370339840 op 0x0:(READ) flags 
0x80700 phys_seg 1 prio class 2
  [   42.164760] nvme :04:00.0: Unable to change power state from D3cold to 
D0, device inaccessible
  [   42.165160] nvme nvme0: Disabling device after reset failure: -19
  [   42.180818] Buffer I/O error on dev nvme0n1p7, logical block 0, async page 
read

  
  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CasperVersion: 1.486
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 10:53:50 2023
  LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2023
  dmi.bios.release: 1.33
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.33.0
  dmi.board.name: 0R6JFH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.33.0:bd07/04/2023:br1.33:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040157/+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 2040054] Re: Upgrade to next linux kernel fails

2023-10-23 Thread BertN45

DKMS was not installed and on installing dkms, I got the same error see
annex: errordkms.

I assume vboxadd is from Virtualbox and since 10 years I use the latest
version from the www.virtualbox.org website.  The only problems I
remember are with newest Linux kernels, not yet supported by Virtualbox.

** Attachment added: "errordkms"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency-hwe-5.15/+bug/2040054/+attachment/5712660/+files/errordkms

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

Title:
  Upgrade to next linux kernel fails

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

Bug description:
  The upgrade fails, note that Ubuntu Studio is the only flavor that
  failed as follows:

  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up linux-image-5.15.0-87-lowlatency (5.15.0-87.96~20.04.1) ...
  Processing triggers for linux-image-5.15.0-87-lowlatency 
(5.15.0-87.96~20.04.1) 
  ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.15.0-87-lowlatency
  /etc/kernel/postinst.d/vboxadd:
  run-parts: failed to exec /etc/kernel/postinst.d/vboxadd: Exec format error
  run-parts: /etc/kernel/postinst.d/vboxadd exited with return code 1
  dpkg: error processing package linux-image-5.15.0-87-lowlatency (--configure):
   installed linux-image-5.15.0-87-lowlatency package post-installation script 
sub
  process returned error exit status 1
  Errors were encountered while processing:
   linux-image-5.15.0-87-lowlatency
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-87-lowlatency 5.15.0-87.96~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-86.95~20.04.1-lowlatency 5.15.122
  Uname: Linux 5.15.0-86-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Oct 21 09:43:07 2023
  InstallationDate: Installed on 2020-07-02 (1206 days ago)
  InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  SourcePackage: linux-signed-lowlatency-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency-hwe-5.15/+bug/2040054/+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 2040163] 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 2040163

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

Title:
  Azure: Update TDX support

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  SRU Justification

  [Impact]

  Refresh the TDX support and support DDA for a TDX VM with paravisor.
  Ideally we would revert
  commit b8b46adebbd8 ("UBUNTU: SAUCE: Support TDX+HCL (July 9, 2023)"), and
  apply "[PATCH v7 0/8] x86/hyperv: Add AMD sev-snp enlightened guest support 
on hyperv" [1]
  and apply "[PATCH v3 00/10] Support TDX guests on Hyper-V (the Hyper-V 
specific part)" [2]
  (Note: [2] depends on [1]), but that would introduce too many changes, and
  actually "AMD sev-snp enlightened guest support on hyperv" still needs some
  extra patches that are not in the upstream yet, e.g. Tianyu Lan's #HV
  interrupt injection patch [3] is not in the upstream yet.

  So I think a better way to have [2] is to make a patch that adds the missing
  part of [2] for the 6.2-based linux-azure kernel, hence I made this patch.

  This patch mainly does the below two things:

  a) Add commit 23378295042a ("Drivers: hv: vmbus: Bring the post_msg_page back 
for TDX VMs with the paravisor") [4]
  This fixes a bug in the hv_pci driver for device assignment (DDA) for a TDX
  VM with the paravisor: in such a VM, the hyperv_pcpu_input_arg must be
  private (i.e. encrypted), otherwise the hypercalls in hv_pci fail since the
  hypercalls in such a VM is handled by the paravisor rather than by the
  hypervisor.

  b) Undo some hack code introduced by
  commit b8b46adebbd8 ("UBUNTU: SAUCE: Support TDX+HCL (July 9, 2023)"),
  e.g. in hyperv_init(), this patch moves the below code to its original place:

  cpuhp_setup_state(CPUHP_AP_HYPERV_ONLINE, "x86/hyperv_init:online",
   hv_cpu_init, hv_cpu_die);

  With this patch, now hyperv_init() in this 6.2 linux-azure kernel is
  exactly the same as the version in the mainline kernel.

  References:
  [1] https://lwn.net/ml/linux-kernel/ZOQMiLEdPsD+pF8q@liuwe-devbox-debian-v2/
  [2] https://lwn.net/ml/linux-kernel/ZOfwSDjW0wlHozYV@liuwe-devbox-debian-v2/
  [3] 
https://lwn.net/ml/linux-kernel/20230515165917.1306922-3-ltyker...@gmail.com/
  [4] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=23378295042a4bcaeec350733a4771678e7a1f3a

  [Test Plan]

  Microsoft tested.

  I tested the patch for a TDX VM without and with paravisor, a VBS VM,
  a SNP VM with paravisor, and a regular VM. All the VMs have 128 vCPUs
  and 20 GB of memory. All worked as expected.

  [Regression potential]

  Azure TDX enabled VMs could misbehave.

  [Other Info]

  SF: #00364214

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040163/+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 2040163] [NEW] Azure: Update TDX support

2023-10-23 Thread Tim Gardner

Public bug reported:

SRU Justification

[Impact]

Refresh the TDX support and support DDA for a TDX VM with paravisor.
Ideally we would revert
commit b8b46adebbd8 ("UBUNTU: SAUCE: Support TDX+HCL (July 9, 2023)"), and
apply "[PATCH v7 0/8] x86/hyperv: Add AMD sev-snp enlightened guest support on 
hyperv" [1]
and apply "[PATCH v3 00/10] Support TDX guests on Hyper-V (the Hyper-V specific 
part)" [2]
(Note: [2] depends on [1]), but that would introduce too many changes, and
actually "AMD sev-snp enlightened guest support on hyperv" still needs some
extra patches that are not in the upstream yet, e.g. Tianyu Lan's #HV
interrupt injection patch [3] is not in the upstream yet.

So I think a better way to have [2] is to make a patch that adds the missing
part of [2] for the 6.2-based linux-azure kernel, hence I made this patch.

This patch mainly does the below two things:

a) Add commit 23378295042a ("Drivers: hv: vmbus: Bring the post_msg_page back 
for TDX VMs with the paravisor") [4]
This fixes a bug in the hv_pci driver for device assignment (DDA) for a TDX
VM with the paravisor: in such a VM, the hyperv_pcpu_input_arg must be
private (i.e. encrypted), otherwise the hypercalls in hv_pci fail since the
hypercalls in such a VM is handled by the paravisor rather than by the
hypervisor.

b) Undo some hack code introduced by
commit b8b46adebbd8 ("UBUNTU: SAUCE: Support TDX+HCL (July 9, 2023)"),
e.g. in hyperv_init(), this patch moves the below code to its original place:

cpuhp_setup_state(CPUHP_AP_HYPERV_ONLINE, "x86/hyperv_init:online",
 hv_cpu_init, hv_cpu_die);

With this patch, now hyperv_init() in this 6.2 linux-azure kernel is
exactly the same as the version in the mainline kernel.

References:
[1] https://lwn.net/ml/linux-kernel/ZOQMiLEdPsD+pF8q@liuwe-devbox-debian-v2/
[2] https://lwn.net/ml/linux-kernel/ZOfwSDjW0wlHozYV@liuwe-devbox-debian-v2/
[3] 
https://lwn.net/ml/linux-kernel/20230515165917.1306922-3-ltyker...@gmail.com/
[4] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=23378295042a4bcaeec350733a4771678e7a1f3a

[Test Plan]

Microsoft tested.

I tested the patch for a TDX VM without and with paravisor, a VBS VM,
a SNP VM with paravisor, and a regular VM. All the VMs have 128 vCPUs
and 20 GB of memory. All worked as expected.

[Regression potential]

Azure TDX enabled VMs could misbehave.

[Other Info]

SF: #00364214

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

** Description changed:

  SRU Justification
  
  [Impact]
  
  Refresh the TDX support and support DDA for a TDX VM with paravisor.
  Ideally we would revert
- commit b8b46adebbd8 ("UBUNTU: SAUCE: Support TDX+HCL (July 9, 2023)"), and
- apply "[PATCH v7 0/8] x86/hyperv: Add AMD sev-snp enlightened guest 
support on hyperv" [1]
- and apply "[PATCH v3 00/10] Support TDX guests on Hyper-V (the Hyper-V 
specific part)" [2]
- (Note: [2] depends on [1]), but that would introduce too many changes, and
- actually "AMD sev-snp enlightened guest support on hyperv" still needs 
some
- extra patches that are not in the upstream yet, e.g. Tianyu Lan's #HV
- interrupt injection patch [3] is not in the upstream yet.
- 
- So I think a better way to have [2] is to make a patch that adds the 
missing
- part of [2] for the 6.2-based linux-azure kernel, hence I made this patch.
- 
- This patch mainly does the below two things:
- 
- a) Add commit 23378295042a ("Drivers: hv: vmbus: Bring the post_msg_page 
back for TDX VMs with the paravisor") [4]
- This fixes a bug in the hv_pci driver for device assignment (DDA) for a 
TDX
- VM with the paravisor: in such a VM, the hyperv_pcpu_input_arg must be
- private (i.e. encrypted), otherwise the hypercalls in hv_pci fail since 
the
- hypercalls in such a VM is handled by the paravisor rather than by the
- hypervisor.
- 
- b) Undo some hack code introduced by
- commit b8b46adebbd8 ("UBUNTU: SAUCE: Support TDX+HCL (July 9, 2023)"),
- e.g. in hyperv_init(), this patch moves the below code to its original 
place:
- 
-  cpuhp_setup_state(CPUHP_AP_HYPERV_ONLINE, "x86/hyperv_init:online",
-  hv_cpu_init, hv_cpu_die);
- 
- With this patch, now hyperv_init() in this 6.2 linux-azure kernel is
- exactly the same as the version in the mainline kernel.
+ commit b8b46adebbd8 ("UBUNTU: SAUCE: Support TDX+HCL (July 9, 2023)"), and
+ apply "[PATCH v7 0/8] x86/hyperv: Add AMD sev-snp enlightened guest support 
on hyperv" [1]
+ and apply "[PATCH v3 00/10] Support TDX guests on Hyper-V (the Hyper-V 
specific part)" [2]
+ (Note: [2] depends on [1]), but that would introduce too many changes, and
+ actually "AMD sev-snp enlightened guest support on hyperv" still needs some
+ extra patches that are not in the upstream yet, e.g. Tianyu Lan's #HV
+ interrupt injection patch [3] is not in the

[Kernel-packages] [Bug 2040157] Re: Unable to use nvme drive to install Ubuntu 23.10

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

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

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

Title:
  Unable to use nvme drive to install Ubuntu 23.10

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

Bug description:
  The 6.5 kernel in the 23.10 installer ISO is unable to work with an
  NVME drive in the laptop, and it is not possible to install Ubuntu. It
  might be related to Kernel bug
  https://bugzilla.kernel.org/show_bug.cgi?id=217802 fixed in 6.5.6.

  dmesg:
  [   42.116742] nvme nvme0: controller is down; will reset: CSTS=0x, 
PCI_STATUS=0x
  [   42.116764] nvme nvme0: Does your device have a faulty power saving mode 
enabled?
  [   42.116769] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 
pcie_aspm=off" and report a bug
  [   42.149334] nvme0n1: I/O Cmd(0x2) @ LBA 370339840, 8 blocks, I/O Error 
(sct 0x3 / sc 0x71) 
  [   42.149357] I/O error, dev nvme0n1, sector 370339840 op 0x0:(READ) flags 
0x80700 phys_seg 1 prio class 2
  [   42.164760] nvme :04:00.0: Unable to change power state from D3cold to 
D0, device inaccessible
  [   42.165160] nvme nvme0: Disabling device after reset failure: -19
  [   42.180818] Buffer I/O error on dev nvme0n1p7, logical block 0, async page 
read

  
  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CasperVersion: 1.486
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 10:53:50 2023
  LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2023
  dmi.bios.release: 1.33
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.33.0
  dmi.board.name: 0R6JFH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.33.0:bd07/04/2023:br1.33:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040157/+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 2040157] Re: Unable to use nvme drive to install Ubuntu 23.10

Additional note: the comment about blacklisting in the bug report was
somewhat mangled:

> I can confirm that blacklisting the drivers (rtsx_pci_and sdmmc and
rtsx_pci) and rebuilding the initramfs...

I found there is a rtsx_pci_sdmmc module, so potentially the complete
kernel argument is:

module_blacklist=rtsx_pci_sdmmc,rtsx_pci

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

Title:
  Unable to use nvme drive to install Ubuntu 23.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The 6.5 kernel in the 23.10 installer ISO is unable to work with an
  NVME drive in the laptop, and it is not possible to install Ubuntu. It
  might be related to Kernel bug
  https://bugzilla.kernel.org/show_bug.cgi?id=217802 fixed in 6.5.6.

  dmesg:
  [   42.116742] nvme nvme0: controller is down; will reset: CSTS=0x, 
PCI_STATUS=0x
  [   42.116764] nvme nvme0: Does your device have a faulty power saving mode 
enabled?
  [   42.116769] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 
pcie_aspm=off" and report a bug
  [   42.149334] nvme0n1: I/O Cmd(0x2) @ LBA 370339840, 8 blocks, I/O Error 
(sct 0x3 / sc 0x71) 
  [   42.149357] I/O error, dev nvme0n1, sector 370339840 op 0x0:(READ) flags 
0x80700 phys_seg 1 prio class 2
  [   42.164760] nvme :04:00.0: Unable to change power state from D3cold to 
D0, device inaccessible
  [   42.165160] nvme nvme0: Disabling device after reset failure: -19
  [   42.180818] Buffer I/O error on dev nvme0n1p7, logical block 0, async page 
read

  
  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CasperVersion: 1.486
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 10:53:50 2023
  LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2023
  dmi.bios.release: 1.33
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.33.0
  dmi.board.name: 0R6JFH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.33.0:bd07/04/2023:br1.33:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040157/+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 2040157] Re: Unable to use nvme drive to install Ubuntu 23.10

The upstream bug report ends in bisecting to:

commit 69304c8d285b77c9a56d68f5ddb2558f27abf406
Author: Ricky WU 
Date:   Tue Jul 25 09:10:54 2023 +

 misc: rtsx: judge ASPM Mode to set PETXCFG Reg

 commit 101bd907b4244a726980ee67f95ed9cafab6ff7a upstream.

 ASPM Mode is ASPM_MODE_CFG need to judge the value of clkreq_0
 to set HIGH or LOW, if the ASPM Mode is ASPM_MODE_REG
 always set to HIGH during the initialization.

 Cc: sta...@vger.kernel.org
 Signed-off-by: Ricky Wu 
 Link: 
https://lore.kernel.org/r/52906c6836374c8cb068225954c55...@realtek.com
 Signed-off-by: Greg Kroah-Hartman 

  drivers/misc/cardreader/rts5227.c  |  2 +-
  drivers/misc/cardreader/rts5228.c  | 18 --
  drivers/misc/cardreader/rts5249.c  |  3 +--
  drivers/misc/cardreader/rts5260.c  | 18 --
  drivers/misc/cardreader/rts5261.c  | 18 --
  drivers/misc/cardreader/rtsx_pcr.c |  5 -
  6 files changed, 6 insertions(+), 58 deletions(-)

All the changes are not directly in the nvme code but seem to have some
influence there. One comment suggested to blacklist the resulting module
"rtsx_pci". According to kernel-parameters.txt one can pass in a
blacklist via "module_blacklist=rtsx_pci".

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

Title:
  Unable to use nvme drive to install Ubuntu 23.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The 6.5 kernel in the 23.10 installer ISO is unable to work with an
  NVME drive in the laptop, and it is not possible to install Ubuntu. It
  might be related to Kernel bug
  https://bugzilla.kernel.org/show_bug.cgi?id=217802 fixed in 6.5.6.

  dmesg:
  [   42.116742] nvme nvme0: controller is down; will reset: CSTS=0x, 
PCI_STATUS=0x
  [   42.116764] nvme nvme0: Does your device have a faulty power saving mode 
enabled?
  [   42.116769] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 
pcie_aspm=off" and report a bug
  [   42.149334] nvme0n1: I/O Cmd(0x2) @ LBA 370339840, 8 blocks, I/O Error 
(sct 0x3 / sc 0x71) 
  [   42.149357] I/O error, dev nvme0n1, sector 370339840 op 0x0:(READ) flags 
0x80700 phys_seg 1 prio class 2
  [   42.164760] nvme :04:00.0: Unable to change power state from D3cold to 
D0, device inaccessible
  [   42.165160] nvme nvme0: Disabling device after reset failure: -19
  [   42.180818] Buffer I/O error on dev nvme0n1p7, logical block 0, async page 
read

  
  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CasperVersion: 1.486
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 10:53:50 2023
  LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2023
  dmi.bios.release: 1.33
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.33.0
  dmi.board.name: 0R6JFH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.33.0:bd07/04/2023:br1.33:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.

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