date:20240122

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.15.143 upstream stable release
+    from git://git.kernel.org/
  
-v5.15.143 upstream stable release
-from git://git.kernel.org/
- 
- 
+ vdpa/mlx5: preserve CVQ vringh index
+ hrtimers: Push pending hrtimers away from outgoing CPU earlier
+ i2c: designware: Fix corrupted memory seen in the ISR
+ netfilter: ipset: fix race condition between swap/destroy and kernel side 
add/del/test
+ tg3: Move the [rt]x_dropped counters to tg3_napi
+ tg3: Increment tx_dropped in tg3_tso_bug()
+ kconfig: fix memory leak from range properties
+ drm/amdgpu: correct chunk_ptr to a pointer to chunk.
+ platform/x86: asus-wmi: Adjust tablet/lidflip handling to use enum
+ platform/x86: asus-wmi: Add support for ROG X13 tablet mode
+ platform/x86: asus-wmi: Simplify tablet-mode-switch probing
+ platform/x86: asus-wmi: Simplify tablet-mode-switch handling
+ platform/x86: asus-wmi: Move i8042 filter install to shared asus-wmi code
+ of: dynamic: Fix of_reconfig_get_state_change() return value documentation
+ platform/x86: wmi: Allow duplicate GUIDs for drivers that use struct 
wmi_driver
+ platform/x86: wmi: Skip blocks with zero instances
+ ipv6: fix potential NULL deref in fib6_add()
+ octeontx2-pf: Add missing mutex lock in otx2_get_pauseparam
+ octeontx2-af: Check return value of nix_get_nixlf before using nixlf
+ hv_netvsc: rndis_filter needs to select NLS
+ r8152: Rename RTL8152_UNPLUG to RTL8152_INACCESSIBLE
+ r8152: Add RTL8152_INACCESSIBLE checks to more loops
+ r8152: Add RTL8152_INACCESSIBLE to r8156b_wait_loading_flash()
+ r8152: Add RTL8152_INACCESSIBLE to r8153_pre_firmware_1()
+ r8152: Add RTL8152_INACCESSIBLE to r8153_aldps_en()
+ mlxbf-bootctl: correctly identify secure boot with development keys
+ platform/mellanox: Add null pointer checks for devm_kasprintf()
+ platform/mellanox: Check devm_hwmon_device_register_with_groups() return value
+ arcnet: restoring support for multiple Sohard Arcnet cards
+ net: stmmac: fix FPE events losing
+ octeontx2-af: fix a use-after-free in rvu_npa_register_reporters
+ i40e: Fix unexpected MFS warning message
+ net: bnxt: fix a potential use-after-free in bnxt_init_tc
+ ionic: fix snprintf format length warning
+ ionic: Fix dim work handling in split interrupt mode
+ ipv4: ip_gre: Avoid skb_pull() failure in ipgre_xmit()
+ net: hns: fix fake link up on xge port
+ octeontx2-af: Update Tx link register range
+ netfilter: nf_tables: validate family when identifying table via handle
+ netfilter: xt_owner: Fix for unsafe access of sk->sk_socket
+ tcp: do not accept ACK of bytes we never sent
+ bpf: sockmap, updating the sg structure should also update curr
+ psample: Require 'CAP_NET_ADMIN' when joining "packets" group
+ net: add missing kdoc for struct genl_multicast_group::flags
+ drop_monitor: Require 'CAP_SYS_ADMIN' when joining "events" group
+ tee: optee: Fix supplicant based device enumeration
+ RDMA/hns: Fix unnecessary err return when using invalid congest control 
algorithm
+ RDMA/irdma: Do not modify to SQD on error
+ RDMA/irdma: Add wait for suspend on SQD
+ arm64: dts: rockchip: Expand reg size of vdec node for RK3399
+ RDMA/rtrs-srv: Do not unconditionally enable irq
+ RDMA/rtrs-clt: Start hb after path_up
+ RDMA/rtrs-srv: Check return values while processing info request
+ RDMA/rtrs-srv: Free srv_mr iu only when always_invalidate is true
+ RDMA/rtrs-srv: Destroy path files after making sure no IOs in-flight
+ RDMA/rtrs-clt: Fix the max_send_wr setting
+ RDMA/rtrs-clt: Remove the warnings for req in_use check
+ RDMA/bnxt_re: Correct module description string
+ hwmon: (acpi_power_meter) Fix 4.29 MW bug
+ hwmon: (nzxt-kraken2) Fix error handling path in kraken2_probe()
+ ASoC: wm_adsp: fix memleak in wm_adsp_buffer_populate
+ RDMA/core: Fix umem iterator when PAGE_SIZE is greater then HCA pgsz
+ RDMA/irdma: Avoid free the non-cqp_request scratch
+ arm64: dts: imx8mq: drop usb3-resume-missing-cas from usb
+ arm64: dts: imx8mp: imx8mq: Add parkmode-disable-ss-quirk on DWC3
+ ARM: dts:

[Kernel-packages] [Bug 2050858] Re: Jammy update: v5.15.143 upstream stable release

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

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

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

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Portia Stephens (portias)

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

Title:
  Jammy update: v5.15.143 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

  
  Linux 5.15.143
  devcoredump: Send uevent once devcd is ready
  devcoredump : Serialize devcd_del work
  smb: client: fix potential NULL deref in parse_dfs_referrals()
  cifs: Fix non-availability of dedup breaking generic/304
  Revert "btrfs: add dmesg output for first mount and last unmount of a 
filesystem"
  MIPS: Loongson64: Enable DMA noncoherent support
  MIPS: Loongson64: Reserve vgabios memory on boot
  KVM: SVM: Update EFER software model on CR0 trap for SEV-ES
  KVM: s390/mm: Properly reset no-dat
  x86/CPU/AMD: Check vendor in the AMD microcode callback
  serial: 8250_omap: Add earlycon support for the AM654 UART controller
  serial: 8250: 8250_omap: Do not start RX DMA on THRI interrupt
  serial: 8250: 8250_omap: Clear UART_HAS_RHR_IT_DIS bit
  serial: sc16is7xx: address RX timeout interrupt errata
  ARM: PL011: Fix DMA support
  usb: typec: class: fix typec_altmode_put_partner to put plugs
  Revert "xhci: Loosen RPM as default policy to cover for AMD xHC 1.1"
  parport: Add support for Brainboxes IX/UC/PX parallel cards
  usb: gadget: f_hid: fix report descriptor allocation
  drm/amdgpu: correct the amdgpu runtime dereference usage count
  drm/amd/amdgpu: Fix warnings in amdgpu/amdgpu_display.c
  gpiolib: sysfs: Fix error handling on failed export
  perf: Fix perf_event_validate_size()
  perf/core: Add a new read format to get a number of lost samples
  arm64: dts: mt8183: kukui: Fix underscores in node names
  arm64: dts: mediatek: add missing space before {
  arm64: dts: mediatek: mt8183: Move thermal-zones to the root node
  arm64: dts: mediatek: align thermal zone node names with dtschema
  tools headers UAPI: Sync linux/perf_event.h with the kernel sources
  docs/process/howto: Replace C89 with C11
  platform/x86: asus-wmi: Fix kbd_dock_devid tablet-switch reporting
  netfilter: nft_set_pipapo: skip inactive elements during set walk
  io_uring/af_unix: disable sending io_uring over sockets
  mm: fix oops when filemap_map_pmd() without prealloc_pte
  r8169: fix rtl8125b PAUSE frames blasting when suspended
  tracing: Stop current tracer when resizing buffer
  tracing: Set actual size after ring buffer resize
  ring-buffer: Force absolute timestamp on discard of event
  misc: mei: client.c: fix problem of return '-EOVERFLOW' in mei_cl_write
  misc: mei: client.c: return negative error code in mei_cl_write
  coresight: etm4x: Remove bogous __exit annotation for some functions
  coresight: etm4x: Make etm4_remove_dev() return void
  kallsyms: Make kallsyms_on_each_symbol generally available
  binder: fix memory leaks of spam and pending work
  arm64: dts: mediatek: mt8183: Fix unit address for scp reserved memory
  arm64: dts: mediatek: mt8173-evb: Fix regulator-fixed node names
  arm64: dts: mediatek: mt8183-kukui-jacuzzi: fix dsi unnecessary cells 
properties
  arm64: dts: mediatek: mt7622: fix memory node warning check
  platform/surface: aggregator: fix recv_buf() return value
  regmap: fix bogus error on regcache_sync success
  packet: Move reference count in packet_sock to atomic_long_t
  tracing: Fix a possible race when disabling buffered events
  tracing: Fix incomplete locking when disabling buffered events
  tracing: Disable snapshot buffer when stopping instance tracers
  tracing: Always update snapshot buffer size
  checkstack: fix printed address
  nilfs2: prevent WARNING in nilfs_sufile_set_segment_usage()
  nilfs2: fix missing error check for sb_set_blocksize call
  ALSA: hda/realtek: Enable headset on Lenovo M90 Gen5
  ALSA: pcm: fix out-of-bounds in snd_pcm_state_names
  ALSA: usb-audio: Add Pioneer DJM-450 mixer controls
  io_uring: fix mutex_unlock with unreferenced ctx
  nvme-pci: Add sleep quirk for Kingston drives
  kprobes: consistent rcu api usage for kretprobe holder
  md:

[Kernel-packages] [Bug 2050858] [NEW] Jammy update: v5.15.143 upstream stable release

Public bug reported:


SRU Justification

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

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


Linux 5.15.143
devcoredump: Send uevent once devcd is ready
devcoredump : Serialize devcd_del work
smb: client: fix potential NULL deref in parse_dfs_referrals()
cifs: Fix non-availability of dedup breaking generic/304
Revert "btrfs: add dmesg output for first mount and last unmount of a 
filesystem"
MIPS: Loongson64: Enable DMA noncoherent support
MIPS: Loongson64: Reserve vgabios memory on boot
KVM: SVM: Update EFER software model on CR0 trap for SEV-ES
KVM: s390/mm: Properly reset no-dat
x86/CPU/AMD: Check vendor in the AMD microcode callback
serial: 8250_omap: Add earlycon support for the AM654 UART controller
serial: 8250: 8250_omap: Do not start RX DMA on THRI interrupt
serial: 8250: 8250_omap: Clear UART_HAS_RHR_IT_DIS bit
serial: sc16is7xx: address RX timeout interrupt errata
ARM: PL011: Fix DMA support
usb: typec: class: fix typec_altmode_put_partner to put plugs
Revert "xhci: Loosen RPM as default policy to cover for AMD xHC 1.1"
parport: Add support for Brainboxes IX/UC/PX parallel cards
usb: gadget: f_hid: fix report descriptor allocation
drm/amdgpu: correct the amdgpu runtime dereference usage count
drm/amd/amdgpu: Fix warnings in amdgpu/amdgpu_display.c
gpiolib: sysfs: Fix error handling on failed export
perf: Fix perf_event_validate_size()
perf/core: Add a new read format to get a number of lost samples
arm64: dts: mt8183: kukui: Fix underscores in node names
arm64: dts: mediatek: add missing space before {
arm64: dts: mediatek: mt8183: Move thermal-zones to the root node
arm64: dts: mediatek: align thermal zone node names with dtschema
tools headers UAPI: Sync linux/perf_event.h with the kernel sources
docs/process/howto: Replace C89 with C11
platform/x86: asus-wmi: Fix kbd_dock_devid tablet-switch reporting
netfilter: nft_set_pipapo: skip inactive elements during set walk
io_uring/af_unix: disable sending io_uring over sockets
mm: fix oops when filemap_map_pmd() without prealloc_pte
r8169: fix rtl8125b PAUSE frames blasting when suspended
tracing: Stop current tracer when resizing buffer
tracing: Set actual size after ring buffer resize
ring-buffer: Force absolute timestamp on discard of event
misc: mei: client.c: fix problem of return '-EOVERFLOW' in mei_cl_write
misc: mei: client.c: return negative error code in mei_cl_write
coresight: etm4x: Remove bogous __exit annotation for some functions
coresight: etm4x: Make etm4_remove_dev() return void
kallsyms: Make kallsyms_on_each_symbol generally available
binder: fix memory leaks of spam and pending work
arm64: dts: mediatek: mt8183: Fix unit address for scp reserved memory
arm64: dts: mediatek: mt8173-evb: Fix regulator-fixed node names
arm64: dts: mediatek: mt8183-kukui-jacuzzi: fix dsi unnecessary cells properties
arm64: dts: mediatek: mt7622: fix memory node warning check
platform/surface: aggregator: fix recv_buf() return value
regmap: fix bogus error on regcache_sync success
packet: Move reference count in packet_sock to atomic_long_t
tracing: Fix a possible race when disabling buffered events
tracing: Fix incomplete locking when disabling buffered events
tracing: Disable snapshot buffer when stopping instance tracers
tracing: Always update snapshot buffer size
checkstack: fix printed address
nilfs2: prevent WARNING in nilfs_sufile_set_segment_usage()
nilfs2: fix missing error check for sb_set_blocksize call
ALSA: hda/realtek: Enable headset on Lenovo M90 Gen5
ALSA: pcm: fix out-of-bounds in snd_pcm_state_names
ALSA: usb-audio: Add Pioneer DJM-450 mixer controls
io_uring: fix mutex_unlock with unreferenced ctx
nvme-pci: Add sleep quirk for Kingston drives
kprobes: consistent rcu api usage for kretprobe holder
md: don't leave 'MD_RECOVERY_FROZEN' in error path of md_set_readonly()
md: introduce md_ro_state
riscv: fix misaligned access handling of C.SWSP and C.SDSP
ARM: dts: imx28-xea: Pass the 'model' property
ARM: dts: imx7: Declare timers compatible with fsl,imx6dl-gpt
ARM: imx: Check return value of devm_kasprintf in imx_mmdc_perf_init
scsi: be2iscsi: Fix a memleak in beiscsi_init_wrb_handle()
tracing: Fix a warning when allocating buffered events fails
ARM: dts: imx6ul-pico: Describe the Ethernet PHY clock
arm64: dts: imx8mp: imx8mq: Add parkmode-disable-ss-quirk on DWC3
arm64: dts: imx8mq: drop usb3-resume-missing-cas from usb
RDMA/irdma: Avoid free the non-cqp_request scratch
RDMA/core: Fix umem iterator when PAGE_SIZE is greater then HCA pgsz
ASoC: wm_adsp: fix memleak in

[Kernel-packages] [Bug 2029405] Re: Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64

2024-01-22 Thread Po-Hsu Lin

There is no ARM64 for intel iotg kernel.

** Tags removed: verification-needed-jammy-linux-intel-iotg
** Tags added: verification-dibe-jammy-linux-intel-iotg

** Tags removed: verification-dibe-jammy-linux-intel-iotg
** Tags added: verification-done-jammy-linux-intel-iotg

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

Title:
  Change in trace file leads to test timeout in ftrace tests on 5.15
  ARM64

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

Bug description:
  [Impact]
  On ARM64 systems, tests like subsystem-enable.tc, event-enable.tc,
  event-pid.tc in linux/tools/testing/selftests/ftrace will take too
  much time to run and consequently leads to test timeout.

  The culprit is the `cat` command on the changing trace file.

  [Fix]
  * 25b9513872 selftests/ftrace: Stop tracing while reading the trace
    file by default

  This patch can be cherry-picked into Jammy. I didn't see this issue in
  our 5.4 kernels. And it's already landed in newer kernels.

  [Test]
  On an ARM64 testing node, apply this patch to the kernel tree and run
  event-pid.tc test in linux/tools/testing/selftests/ftrace with:

    sudo ./ftracetest -vvv test.d/event/event-pid.tc

  The test should finish within a few minutes.

  [Regression Potential]
  Change limited to testing tools, it should not have any actual impact
  to kernel functions.

  == Original Bug Report ==
  First time seen this since ftrace refactor out from ubuntu_kernel_selftests 
to ubuntu-kselftests-ftrace

  Issue found on ARM64 nodes with both generic / generic-64k kernel.

  Partial test log:
   Running './ftracetest -vvv test.d/event/subsystem-enable.tc'
   === Ftrace unit tests ===
   
   [1] event tracing - enable/disable with event level files
   + [ 2 -eq 1 ]
   + [ -f set_event_pid ]
   + echo
   + [ -f set_ftrace_pid ]
   + echo
   + [ -f set_ftrace_notrace ]
   + echo
   + [ -f set_graph_function ]
   + echo
   + tee set_graph_function set_graph_notrace
   + [ -f stack_trace_filter ]
   + echo
   + [ -f kprobe_events ]
   + echo
   + [ -f uprobe_events ]
   + echo
   + [ -f synthetic_events ]
   + echo
   + [ -f snapshot ]
   + echo 0
   + clear_trace
   + echo
   + enable_tracing
   + echo 1
   + . 
/home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/event/event-enable.tc
   + echo sched:sched_switch
   + yield
   + ping 127.0.0.1 -c 1
   PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
   64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.096 ms

   --- 127.0.0.1 ping statistics ---
   1 packets transmitted, 1 received, 0% packet loss, time 0ms
   rtt min/avg/max/mdev = 0.096/0.096/0.096/0.000 ms
   + cat trace
   + grep sched_switch
   + wc -l
   Timer expired (600 sec.), nuking pid 20982

  From the code (tools/testing/selftests/ftrace/test.d/event/event-
  enable.tc) this test is trying to run:

  count=`cat trace | grep sched_switch | wc -l`

  This command caused the timeout as `cat trace` seems to be never
  ending.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2029405/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble

2024-01-22 Thread dann frazier

I ran the above test:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-dannf-test/jammy/amd64/l/livecd-rootfs/20240123_035147_6470b@/log.gz

It does appear that systemd-udevd is trying to scan partitions at the
same time as losetup:

1599s ++ losetup --show -f -P -v binary/boot/disk-uefi.ext4
1600s + loop_device=/dev/loop0
1600s + '[' '!' -b /dev/loop0 ']'
1600s + rootfs_dev_mapper=/dev/loop0p1
1600s + '[' '!' -b /dev/loop0p1 ']'
1600s + echo '/dev/loop0p1 is not a block device'
1600s /dev/loop0p1 is not a block device
1600s + echo '=== dmesg ==='
1600s === dmesg ===
1600s + dmesg -c
1600s [  986.014824] EXT4-fs (loop0p1): mounted filesystem with ordered data 
mode. Opts: (null). Quota mode: none.
1600s [  992.684380] EXT4-fs (loop0p1): mounted filesystem with ordered data 
mode. Opts: (null). Quota mode: none.
1600s [ 1043.171603] loop0: detected capacity change from 0 to 4612096
1600s [ 1043.171924]  loop0: p1 p14 p15
1600s [ 1043.190421]  loop0: p1 p14 p15
1600s + cat /sys/kernel/debug/tracing/trace
1600s # tracer: function
1600s #
1600s # entries-in-buffer/entries-written: 2/2   #P:4
1600s #
1600s #_-=> irqs-off
1600s #   / _=> need-resched
1600s #  | / _---=> hardirq/softirq
1600s #  || / _--=> preempt-depth
1600s #  ||| / _-=> migrate-disable
1600s #   / delay
1600s #   TASK-PID CPU#  |  TIMESTAMP  FUNCTION
1600s #  | | |   | | |
1600s  losetup-50167   [002] .  1043.176845: bdev_disk_changed 
<-loop_reread_partitions
1600ssystemd-udevd-321 [000] .  1043.195003: bdev_disk_changed 
<-blkdev_get_whole
1600s + echo 0
1600s + ls -l /dev/loop0p1
1600s brw--- 1 root root 259, 3 Jan 23 03:51 /dev/loop0p1
1600s + exit 1
1600s + clean_loops


Maybe we just need something like this?

diff --git a/drivers/block/loop.c b/drivers/block/loop.c
index 48c530b83000e..52fda87f5d674 100644
--- a/drivers/block/loop.c
+++ b/drivers/block/loop.c
@@ -1366,13 +1366,13 @@ static int loop_configure(struct loop_device *lo, 
fmode_t mode,
if (partscan)
lo->lo_disk->flags &= ~GENHD_FL_NO_PART_SCAN;
 
-   /* enable and uncork uevent now that we are done */
-   dev_set_uevent_suppress(disk_to_dev(lo->lo_disk), 0);
-
loop_global_unlock(lo, is_loop);
if (partscan)
loop_reread_partitions(lo);
 
+   /* enable and uncork uevent now that we are done */
+   dev_set_uevent_suppress(disk_to_dev(lo->lo_disk), 0);
+
if (!(mode & FMODE_EXCL))
bd_abort_claiming(bdev, loop_configure);

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

Title:
  livecd-rootfs uses losetup -P for theoretically reliable/synchronous
  partition setup but it's not reliable in noble

Status in linux package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  In mantic, we migrated livecd-rootfs to use losetup -P instead of
  kpartx, with the expectation that this would give us a reliable, race-
  free way of loop-mounting partitions from a disk image during image
  build.

  In noble, we are finding that it is no longer reliable, and in fact
  fails rather often.

  It is most noticeable with riscv64 builds, which is the architecture
  where we most frequently ran into problems before with kpartx.  The
  first riscv64+generic build in noble where the expected loop partition
  device is not available is

https://launchpad.net/~ubuntu-
  cdimage/+livefs/ubuntu/noble/cpc/+build/531790

  The failure is however not unique to riscv64, and the autopkgtest for
  the latest version of livecd-rootfs (24.04.7) - an update that
  specifically tries to add more debugging code for this scenario - has
  also failed on ppc64el.

https://autopkgtest.ubuntu.com/packages/l/livecd-
  rootfs/noble/ppc64el

  The first failure happened on November 16.  While there has been an
  update to the util-linux package in noble, this did not land until
  November 23.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2049637] Re: Some SPR systems throw kernel warnings from uncore_discovery.c

2024-01-22 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  Some SPR systems throw kernel warnings from uncore_discovery.c

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

Bug description:
  [Impact]
  On some Sapphire Rapids CPUs we are seeing Kernel warnings in the kern.log:
  https://certification.canonical.com/hardware/202311-32288/submission/341156/
  Intel(R) Xeon(R) Gold 6442Y

  Oct 31 03:35:55 N8 kernel: [   92.770372] [ cut here ]
  Oct 31 03:35:55 N8 kernel: [   92.825738] WARNING: CPU: 48 PID: 1 at 
arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350
  Oct 31 03:35:55 N8 kernel: [   92.953850] Modules linked in:
  Oct 31 03:35:55 N8 kernel: [   92.990464] CPU: 48 PID: 1 Comm: swapper/0 Not 
tainted 5.15.0-88-generic #98-Ubuntu
  Oct 31 03:35:55 N8 kernel: [   93.082179] Hardware name: ASUSTeK COMPUTER 
INC. ESC N8-E11/Z13PN-D32 Series, BIOS 0402 09/08/2023
  Oct 31 03:35:55 N8 kernel: [   93.189501] RIP: 
0010:uncore_insert_box_info+0x134/0x350
  Oct 31 03:35:55 N8 kernel: [   93.206419] Freeing initrd memory: 106936K
  Oct 31 03:35:55 N8 kernel: [   93.253138] Code: c2 01 48 83 c0 04 39 d1 0f 8e 
c6 01 00 00 49 8b 4c 24 38 8b 0c 01 41 89 0c 07 49 8b 74 24 40 8b 34 06 41 89 
34 06 39 f9 75 cf <0f> 0b 4c 89 ff e8 b2 07 33 00 4c 89 f7 e8 aa 07 33 00 5b 41 
5c 41
  Oct 31 03:35:55 N8 kernel: [   93.527071] RSP: :ff5c25ed800efc98 EFLAGS: 
00010246
  Oct 31 03:35:55 N8 kernel: [   93.589669] RAX: 0008 RBX: 
 RCX: 0003
  Oct 31 03:35:55 N8 kernel: [   93.675160] RDX: 0002 RSI: 
00018000 RDI: 0003
  Oct 31 03:35:55 N8 kernel: [   93.760654] RBP: ff5c25ed800efcc0 R08: 
0010 R09: ff32ac8a801df260
  Oct 31 03:35:55 N8 kernel: [   93.846130] R10: 0246 R11: 
 R12: ff32ac8a8b8412a0
  Oct 31 03:35:55 N8 kernel: [   93.931613] R13: ff5c25ed800efcf8 R14: 
ff32ac8a8aa32cb0 R15: ff32ac8a801df260
  Oct 31 03:35:55 N8 kernel: [   94.017099] FS:  () 
GS:ff32ac99bfa0() knlGS:
  Oct 31 03:35:55 N8 kernel: [   94.114042] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 31 03:35:55 N8 kernel: [   94.182871] CR2:  CR3: 
000d07e10001 CR4: 00771ee0
  Oct 31 03:35:55 N8 kernel: [   94.268360] DR0:  DR1: 
 DR2: 
  Oct 31 03:35:55 N8 kernel: [   94.353828] DR3:  DR6: 
fffe07f0 DR7: 0400
  Oct 31 03:35:55 N8 kernel: [   94.439332] PKRU: 5554
  Oct 31 03:35:55 N8 kernel: [   94.471788] Call Trace:
  Oct 31 03:35:55 N8 kernel: [   94.501100]  
  Oct 31 03:35:55 N8 kernel: [   94.526275]  ? show_trace_log_lvl+0x1d6/0x2ea
  Oct 31 03:35:55 N8 kernel: [   94.578457]  ? show_trace_log_lvl+0x1d6/0x2ea
  Oct 31 03:35:55 N8 kernel: [   94.630686]  ? 
parse_discovery_table.isra.0+0x162/0x1a0
  Oct 31 03:35:55 N8 kernel: [   94.693295]  ? show_regs.part.0+0x23/0x29
  Oct 31 03:35:55 N8 kernel: [   94.741331]  ? show_regs.cold+0x8/0xd
  Oct 31 03:35:55 N8 kernel: [   94.785212]  ? 
uncore_insert_box_info+0x134/0x350
  Oct 31 03:35:55 N8 kernel: [   94.841591]  ? __warn+0x8c/0x100
  Oct 31 03:35:55 N8 kernel: [   94.880281]  ? 
uncore_insert_box_info+0x134/0x350
  Oct 31 03:35:55 N8 kernel: [   94.936636]  ? report_bug+0xa4/0xd0
  Oct 31 03:35:55 N8 kernel: [   94.978460]  ? handle_bug+0x39/0x90
  Oct 31 03:35:55 N8 kernel: [   95.020246]  ? exc_invalid_op+0x19/0x70
  Oct 31 03:35:55 N8 kernel: [   95.066232]  ? asm_exc_invalid_op+0x1b/0x20
  Oct 31 03:35:55 N8 kernel: [   95.116341]  ? 
uncore_insert_box_info+0x134/0x350
  Oct 31 03:35:55 N8 kernel: [   95.172708]  ? uncore_insert_box_info+0xe3/0x350
  Oct 31 03:35:55 N8 kernel: [   95.228032]  
parse_discovery_table.isra.0+0x162/0x1a0
  Oct 31 03:35:55 N8 cloud-init[1992]: |.+.o  .o   .o o +|
  Oct 31 03:35:55 N8 kernel: [   95.288570]  
intel_uncore_has_discovery_tables+0x19e/0x270
  Oct 31 03:35:55 N8 kernel: [   95.354298]  ? type_pmu_register+0x2f/0x42
  Oct 31 03:35:55 N8 kernel: [   95.403385]  intel_uncore_init+0xe3/0x226
  Oct 31 03:35:55 N8 kernel: [   95.451409]  ? type_pmu_register+0x42/0x42
  Oct 31 03:35:55 N8 kernel: [   95.500506]  do_one_initcall+0x46/0x1e0
  Oct 31 03:35:55 N8 kernel: [   95.546475]  do_initcalls+0x12f/0x159
  Oct 31 03:35:55 N8 kernel: [   95.590372]  kernel_init_freeable+0x162/0x1b5
  Oct 31 03:35:55 N8 kernel: [   95.642556]  ? rest_init+0x100/0x100
  Oct 31 03:35:55 N8 kernel: [   95.685405]  kernel_init+0x1b/0x150
  Oct 31 03:35:55 N8 kernel: [   95.727228]  ? rest_init+0x100/0x100
  Oct 31 03:35:55 N8 kernel: [   95.770054]  ret_from_fork+0x1f/0x30
  Oct 31 03:35:55 N8 kernel: [   95.812906]  
  Oct 31

[Kernel-packages] [Bug 2050849] Re: Jammy update: v5.15.142 upstream stable release

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.15.142 upstream stable release
+    from git://git.kernel.org/
  
-v5.15.142 upstream stable release
-from git://git.kernel.org/
- 
- 
+ locking/ww_mutex/test: Fix potential workqueue corruption
+ perf/core: Bail out early if the request AUX area is out of bound
+ clocksource/drivers/timer-imx-gpt: Fix potential memory leak
+ clocksource/drivers/timer-atmel-tcb: Fix initialization on SAM9 hardware
+ workqueue: Provide one lock class key per work_on_cpu() callsite
+ x86/mm: Drop the 4 MB restriction on minimal NUMA node memory size
+ wifi: mac80211_hwsim: fix clang-specific fortify warning
+ wifi: mac80211: don't return unset power in ieee80211_get_tx_power()
+ atl1c: Work around the DMA RX overflow issue
+ bpf: Detect IP == ksym.end as part of BPF program
+ wifi: ath9k: fix clang-specific fortify warnings
+ wifi: ath10k: fix clang-specific fortify warning
+ net: annotate data-races around sk->sk_tx_queue_mapping
+ net: annotate data-races around sk->sk_dst_pending_confirm
+ wifi: ath10k: Don't touch the CE interrupt registers after power up
+ Bluetooth: btusb: Add date->evt_skb is NULL check
+ Bluetooth: Fix double free in hci_conn_cleanup
+ platform/x86: thinkpad_acpi: Add battery quirk for Thinkpad X120e
+ drm/komeda: drop all currently held locks if deadlock happens
+ drm/amdkfd: Fix a race condition of vram buffer unref in svm code
+ drm/amd/display: use full update for clip size increase of large plane source
+ string.h: add array-wrappers for (v)memdup_user()
+ kernel: kexec: copy user-array safely
+ kernel: watch_queue: copy user-array safely
+ drm: vmwgfx_surface.c: copy user-array safely
+ drm/msm/dp: skip validity check for DP CTS EDID checksum
+ drm/amd: Fix UBSAN array-index-out-of-bounds for SMU7
+ drm/amd: Fix UBSAN array-index-out-of-bounds for Polaris and Tonga
+ drm/amdgpu: Fix potential null pointer derefernce
+ drm/panel: fix a possible null pointer dereference
+ drm/panel/panel-tpo-tpg110: fix a possible null pointer dereference
+ drm/amdgpu/vkms: fix a possible null pointer dereference
+ drm/panel: st7703: Pick different reset sequence
+ drm/amdkfd: Fix shift out-of-bounds issue
+ drm/amdgpu: Fix a null pointer access when the smc_rreg pointer is NULL
+ arm64: dts: ls208xa: use a pseudo-bus to constrain usb dma size
+ selftests/efivarfs: create-read: fix a resource leak
+ ASoC: soc-card: Add storage for PCI SSID
+ crypto: pcrypt - Fix hungtask for PADATA_RESET
+ RDMA/hfi1: Use FIELD_GET() to extract Link Width
+ scsi: hisi_sas: Set debugfs_dir pointer to NULL after removing debugfs
+ scsi: ibmvfc: Remove BUG_ON in the case of an empty event pool
+ fs/jfs: Add check for negative db_l2nbperpage
+ fs/jfs: Add validity check for db_maxag and db_agpref
+ jfs: fix array-index-out-of-bounds in dbFindLeaf
+ jfs: fix array-index-out-of-bounds in diAlloc
+ HID: lenovo: Detect quirk-free fw on cptkbd and stop applying workaround
+ ARM: 9320/1: fix stack depot IRQ stack filter
+ ALSA: hda: Fix possible null-ptr-deref when assigning a stream
+ PCI: tegra194: Use FIELD_GET()/FIELD_PREP() with Link Width fields
+ atm: iphase: Do PCI error checks on own line
+ scsi: libfc: Fix potential NULL pointer dereference in fc_lport_ptp_setup()
+ PCI: Use FIELD_GET() to extract Link Width
+ PCI: Extract ATS disabling to a helper function
+ PCI: Disable ATS for specific Intel IPU E2000 devices
+ misc: pci_endpoint_test: Add Device ID for R-Car S4-8 PCIe controller
+ PCI: Use FIELD_GET() in Sapphire RX 5600 XT Pulse quirk
+ HID: Add quirk for Dell Pro Wireless Keyboard and Mouse KM5221W
+ exfat: support handle zero-size directory
+ tty: vcc: Add check for kstrdup() in vcc_probe()
+ usb: gadget: f_ncm: Always set current gadget in ncm_bind()
+ 9p/trans_fd: Annotate data-racy writes to file::f_flags
+ 9p: v9fs_listxattr: fix %s null argument warning
+ i3c: mipi-i3c-hci: Fix out of bounds access in hci_dma_irq_handler
+ i2c: sun6i-p2wi: Prevent potential division by zero
+ virtio-blk: fix implicit overflow on virtio_max_dma_size
+

[Kernel-packages] [Bug 2050849] [NEW] Jammy update: v5.15.142 upstream stable release

Public bug reported:

SRU Justification

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

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

pinctrl: avoid reload of p state in list iteration
firewire: core: fix possible memory leak in create_units()
mmc: cqhci: Increase recovery halt timeout
mmc: cqhci: Warn of halt or task clear failure
mmc: cqhci: Fix task clearing in CQE error recovery
mmc: block: Retry commands in CQE error recovery
mmc: block: Do not lose cache flush during CQE error recovery
mmc: block: Be sure to wait while busy in CQE error recovery
ALSA: hda: Disable power-save on KONTRON SinglePC
ALSA: hda/realtek: Headset Mic VREF to 100%
ALSA: hda/realtek: Add supported ALC257 for ChromeOS
dm-verity: align struct dm_verity_fec_io properly
dm verity: don't perform FEC for failed readahead IO
bcache: revert replacing IS_ERR_OR_NULL with IS_ERR
iommu/vt-d: Add MTL to quirk list to skip TE disabling
powerpc: Don't clobber f0/vs0 during fp|altivec register save
parisc: Drop the HP-UX ENOSYM and EREMOTERELEASE error codes
btrfs: ref-verify: fix memory leaks in btrfs_ref_tree_mod()
btrfs: fix off-by-one when checking chunk map includes logical address
btrfs: send: ensure send_fd is writable
btrfs: make error messages more clear when getting a chunk map
Input: xpad - add HyperX Clutch Gladiate Support
vlan: introduce vlan_dev_free_egress_priority
vlan: move dev_put into vlan_dev_uninit
rcu: Avoid tracing a few functions executed in stop machine
hv_netvsc: fix race of netvsc and VF register_netdevice
USB: core: Change configuration warnings to notices
usb: config: fix iteration issue in 'usb_get_bos_descriptor()'
dpaa2-eth: increase the needed headroom to account for alignment
uapi: propagate __struct_group() attributes to the container union
selftests/net: ipsec: fix constant out of range
octeontx2-af: Fix possible buffer overflow
net: stmmac: xgmac: Disable FPE MMC interrupts
octeontx2-pf: Fix adding mbox work queue entry when num_vfs > 64
Revert "workqueue: remove unused cancel_work()"
r8169: prevent potential deadlock in rtl8169_close
ravb: Fix races between ravb_tx_timeout_work() and net related ops
net: ravb: Check return value of reset_control_deassert()
net: ravb: Use pm_runtime_resume_and_get()
net: ravb: Start TX queues after HW initialization succeeded
net: ravb: Stop DMA in case of failures on ravb_open()
perf intel-pt: Fix async branch flags
selftests/resctrl: Add missing SPDX license to Makefile
selftests/resctrl: Move _GNU_SOURCE define into Makefile
smb3: fix touch -h of symlink
ASoC: Intel: Move soc_intel_is_foo() helpers to a generic header
ASoC: SOF: sof-pci-dev: use community key on all Up boards
ASoC: SOF: sof-pci-dev: add parameter to override topology filename
ASoC: SOF: sof-pci-dev: don't use the community key on APL Chromebooks
ASoC: SOF: sof-pci-dev: Fix community key quirk detection
fbdev: stifb: Make the STI next font pointer a 32-bit signed offset
fs: add ctime accessors infrastructure
smb3: fix caching of ctime on setxattr
cpufreq: imx6q: don't warn for disabling a non-existing frequency
cpufreq: imx6q: Don't disable 792 Mhz OPP unnecessarily
iommu/vt-d: Omit devTLB invalidation requests when TES=0
iommu/vt-d: Make context clearing consistent with context mapping
mmc: core: add helpers mmc_regulator_enable/disable_vqmmc
mmc: sdhci-sprd: Fix vqmmc not shutting down after the card was pulled
r8169: disable ASPM in case of tx timeout
r8169: fix deadlock on RTL8125 in jumbo mtu mode
iomap: update ki_pos a little later in iomap_dio_complete
Linux 5.15.142
UBUNTU: Upstream stable to v5.15.142

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

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

Title:
  Jammy update: v5.15.142 upstream stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either

[Kernel-packages] [Bug 2049637] Re: Some SPR systems throw kernel warnings from uncore_discovery.c

2024-01-22 Thread yunyings

Commit 65248a9a9ee1 (perf/x86/uncore: Add a quirk for UPI on SPR) needs
some code adaptations when backporting to kernel 5.15.

I just made an adapted patch locally. Here attached. Please try to apply
and test.

** Patch added: "0001-perf-x86-uncore-Add-a-quirk-for-UPI-on-SPR.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049637/+attachment/5741513/+files/0001-perf-x86-uncore-Add-a-quirk-for-UPI-on-SPR.patch

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

Title:
  Some SPR systems throw kernel warnings from uncore_discovery.c

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

Bug description:
  [Impact]
  On some Sapphire Rapids CPUs we are seeing Kernel warnings in the kern.log:
  https://certification.canonical.com/hardware/202311-32288/submission/341156/
  Intel(R) Xeon(R) Gold 6442Y

  Oct 31 03:35:55 N8 kernel: [   92.770372] [ cut here ]
  Oct 31 03:35:55 N8 kernel: [   92.825738] WARNING: CPU: 48 PID: 1 at 
arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350
  Oct 31 03:35:55 N8 kernel: [   92.953850] Modules linked in:
  Oct 31 03:35:55 N8 kernel: [   92.990464] CPU: 48 PID: 1 Comm: swapper/0 Not 
tainted 5.15.0-88-generic #98-Ubuntu
  Oct 31 03:35:55 N8 kernel: [   93.082179] Hardware name: ASUSTeK COMPUTER 
INC. ESC N8-E11/Z13PN-D32 Series, BIOS 0402 09/08/2023
  Oct 31 03:35:55 N8 kernel: [   93.189501] RIP: 
0010:uncore_insert_box_info+0x134/0x350
  Oct 31 03:35:55 N8 kernel: [   93.206419] Freeing initrd memory: 106936K
  Oct 31 03:35:55 N8 kernel: [   93.253138] Code: c2 01 48 83 c0 04 39 d1 0f 8e 
c6 01 00 00 49 8b 4c 24 38 8b 0c 01 41 89 0c 07 49 8b 74 24 40 8b 34 06 41 89 
34 06 39 f9 75 cf <0f> 0b 4c 89 ff e8 b2 07 33 00 4c 89 f7 e8 aa 07 33 00 5b 41 
5c 41
  Oct 31 03:35:55 N8 kernel: [   93.527071] RSP: :ff5c25ed800efc98 EFLAGS: 
00010246
  Oct 31 03:35:55 N8 kernel: [   93.589669] RAX: 0008 RBX: 
 RCX: 0003
  Oct 31 03:35:55 N8 kernel: [   93.675160] RDX: 0002 RSI: 
00018000 RDI: 0003
  Oct 31 03:35:55 N8 kernel: [   93.760654] RBP: ff5c25ed800efcc0 R08: 
0010 R09: ff32ac8a801df260
  Oct 31 03:35:55 N8 kernel: [   93.846130] R10: 0246 R11: 
 R12: ff32ac8a8b8412a0
  Oct 31 03:35:55 N8 kernel: [   93.931613] R13: ff5c25ed800efcf8 R14: 
ff32ac8a8aa32cb0 R15: ff32ac8a801df260
  Oct 31 03:35:55 N8 kernel: [   94.017099] FS:  () 
GS:ff32ac99bfa0() knlGS:
  Oct 31 03:35:55 N8 kernel: [   94.114042] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 31 03:35:55 N8 kernel: [   94.182871] CR2:  CR3: 
000d07e10001 CR4: 00771ee0
  Oct 31 03:35:55 N8 kernel: [   94.268360] DR0:  DR1: 
 DR2: 
  Oct 31 03:35:55 N8 kernel: [   94.353828] DR3:  DR6: 
fffe07f0 DR7: 0400
  Oct 31 03:35:55 N8 kernel: [   94.439332] PKRU: 5554
  Oct 31 03:35:55 N8 kernel: [   94.471788] Call Trace:
  Oct 31 03:35:55 N8 kernel: [   94.501100]  
  Oct 31 03:35:55 N8 kernel: [   94.526275]  ? show_trace_log_lvl+0x1d6/0x2ea
  Oct 31 03:35:55 N8 kernel: [   94.578457]  ? show_trace_log_lvl+0x1d6/0x2ea
  Oct 31 03:35:55 N8 kernel: [   94.630686]  ? 
parse_discovery_table.isra.0+0x162/0x1a0
  Oct 31 03:35:55 N8 kernel: [   94.693295]  ? show_regs.part.0+0x23/0x29
  Oct 31 03:35:55 N8 kernel: [   94.741331]  ? show_regs.cold+0x8/0xd
  Oct 31 03:35:55 N8 kernel: [   94.785212]  ? 
uncore_insert_box_info+0x134/0x350
  Oct 31 03:35:55 N8 kernel: [   94.841591]  ? __warn+0x8c/0x100
  Oct 31 03:35:55 N8 kernel: [   94.880281]  ? 
uncore_insert_box_info+0x134/0x350
  Oct 31 03:35:55 N8 kernel: [   94.936636]  ? report_bug+0xa4/0xd0
  Oct 31 03:35:55 N8 kernel: [   94.978460]  ? handle_bug+0x39/0x90
  Oct 31 03:35:55 N8 kernel: [   95.020246]  ? exc_invalid_op+0x19/0x70
  Oct 31 03:35:55 N8 kernel: [   95.066232]  ? asm_exc_invalid_op+0x1b/0x20
  Oct 31 03:35:55 N8 kernel: [   95.116341]  ? 
uncore_insert_box_info+0x134/0x350
  Oct 31 03:35:55 N8 kernel: [   95.172708]  ? uncore_insert_box_info+0xe3/0x350
  Oct 31 03:35:55 N8 kernel: [   95.228032]  
parse_discovery_table.isra.0+0x162/0x1a0
  Oct 31 03:35:55 N8 cloud-init[1992]: |.+.o  .o   .o o +|
  Oct 31 03:35:55 N8 kernel: [   95.288570]  
intel_uncore_has_discovery_tables+0x19e/0x270
  Oct 31 03:35:55 N8 kernel: [   95.354298]  ? type_pmu_register+0x2f/0x42
  Oct 31 03:35:55 N8 kernel: [   95.403385]  intel_uncore_init+0xe3/0x226
  Oct 31 03:35:55 N8 kernel: [   95.451409]  ? type_pmu_register+0x42/0x42
  Oct 31 03:35:55 N8 kernel: [   95.500506]  do_one_initcall+0x46/0x1e0
  Oct 31 03:35:55 N8 kernel: [   95.546475]  do_initcalls+0x12f/0x159

[Kernel-packages] [Bug 2050805] Re: [HP EliteBook 8560w] Can't change screen brightness

** Summary changed:

- brightness 
+ [HP EliteBook 8560w] Can't change screen brightness

** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)

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

Title:
  [HP EliteBook 8560w] Can't change screen brightness

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

Bug description:
  hi , i can't change my brightness it s blocked on max even if i us
  fn+f9 it show the bar of brightness changing but not the brightness in
  my screen

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 22 19:36:53 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GF106GLM [Quadro 2000M] [103c:1631]
  InstallationDate: Installed on 2024-01-16 (6 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Hewlett-Packard HP EliteBook 8560w
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=a21fb944-4d22-4f82-b6f9-85577ca2ec3d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/05/2012
  dmi.bios.release: 15.34
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SVD Ver. F.22
  dmi.board.name: 1631
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 01.39
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 1.57
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SVDVer.F.22:bd01/05/2012:br15.34:efr1.57:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.39:cvnHewlett-Packard:ct10:cvr:skuWX563AV:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8560w
  dmi.product.sku: WX563AV
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

Re: [Kernel-packages] [Bug 2039167] Re: I get this message "array-index-out-of-bounds" every time I turn on my laptop since I upgraded from 23.04. to 23.10. (drivers/gpu/drm/amd/amdgpu/../pm/powerplay

2024-01-22 Thread Bruno Maderni

amdgpu.mcbp=0

Does not work for me.

On Mon, Jan 22, 2024 at 7:51 PM samuelbailey <2039...@bugs.launchpad.net>
wrote:

> Not completely sure whether this is an identical issue, but at the very
> least looks very similar, I was seeing:
>
> UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-
>
> hwe-6.5-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/vega10_processpptables.c:621:5
>
> A workaround appears to have been found here:
> https://bugzilla.kernel.org/show_bug.cgi?id=201957#c94
>
> Setting the kernel parameter amdgpu.mcbp=0 appears to have stopped the
> crashing for me.
>
> ** Bug watch added: Linux Kernel Bug Tracker #201957
>https://bugzilla.kernel.org/show_bug.cgi?id=201957
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (2049971).
> https://bugs.launchpad.net/bugs/2039167
>
> Title:
>   I get this message "array-index-out-of-bounds"  every time I turn on
>   my laptop since I upgraded from 23.04. to 23.10.
>   (drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039167/+subscriptions
>
>

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

Title:
  I get this message "array-index-out-of-bounds"  every time I turn on
  my laptop since I upgraded from 23.04. to 23.10.
  (drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  UBSAN: array-index-out-of-bounds in 
/build/linux-D15vQj/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:929:40
  index 1 is out of range for type 'UCHAR [1]'

  My firmware version is X515DAP.311.
  OS type 64-bit.
  GNOME version 45.0.
  Kernel version Linux 6.5.0-9-generic.

  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zoran  2329 F wireplumber
   /dev/snd/controlC0:  zoran  2329 F wireplumber
   /dev/snd/seq:zoran  2316 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 13:42:16 2023
  InstallationDate: Installed on 2023-09-21 (21 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=9b0c8205-22d2-4c7e-8e53-959a91e2174d ro quiet splash 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-12 (0 days ago)
  dmi.bios.date: 01/06/2023
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X515DAP.311
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X515DAP
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX515DAP.311:bd01/06/2023:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX515DAP_M515DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX515DAP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUSLaptop
  dmi.product.name: VivoBook_ASUSLaptop X515DAP_M515DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039167/+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 2049958] Re: package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/bluetooth/obexd' before installing new version: Input/output e

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

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

Title:
  package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to
  make backup link of './usr/lib/bluetooth/obexd' before installing new
  version: Input/output error

Status in Ubuntu:
  Incomplete

Bug description:
  bug found during software update launched from bootable usb

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: bluez-obexd 5.68-0ubuntu1
  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
  CasperMD5CheckMismatches: ./casper/minimal.squashfs
  CasperMD5CheckResult: fail
  CasperVersion: 1.486
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  Date: Sat Jan 20 00:18:32 2024
  DuplicateSignature:
   package:bluez-obexd:5.68-0ubuntu1
   Unpacking bluez-obexd (5.68-0ubuntu1.1) over (5.68-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-MsVzUs/045-bluez-obexd_5.68-0ubuntu1.1_amd64.deb 
(--unpack):
unable to make backup link of './usr/lib/bluetooth/obexd' before installing 
new version: Input/output error
  ErrorMessage: unable to make backup link of './usr/lib/bluetooth/obexd' 
before installing new version: Input/output error
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz persistent 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: bluez
  Title: package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to 
make backup link of './usr/lib/bluetooth/obexd' before installing new version: 
Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2018
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 306
  dmi.board.asset.tag: Default string
  dmi.board.name: GL553VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr306:bd09/26/2018:br5.6:svnASUSTeKCOMPUTERINC.:pnGL553VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: GL
  dmi.product.name: GL553VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D0:57:7B:12:13:2F  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING 
RX bytes:1345 acl:0 sco:0 events:90 errors:0
TX bytes:3835 acl:0 sco:0 commands:90 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2049958/+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 2050805] [NEW] [HP EliteBook 8560w] Can't change screen brightness

You have been subscribed to a public bug:

hi , i can't change my brightness it s blocked on max even if i us fn+f9
it show the bar of brightness changing but not the brightness in my
screen

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 22 19:36:53 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company GF106GLM [Quadro 2000M] [103c:1631]
InstallationDate: Installed on 2024-01-16 (6 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
MachineType: Hewlett-Packard HP EliteBook 8560w
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=a21fb944-4d22-4f82-b6f9-85577ca2ec3d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/05/2012
dmi.bios.release: 15.34
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68SVD Ver. F.22
dmi.board.name: 1631
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 01.39
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.ec.firmware.release: 1.57
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SVDVer.F.22:bd01/05/2012:br15.34:efr1.57:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.39:cvnHewlett-Packard:ct10:cvr:skuWX563AV:
dmi.product.family: 103C_5336AN
dmi.product.name: HP EliteBook 8560w
dmi.product.sku: WX563AV
dmi.product.version: A0001D02
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu wayland-session
-- 
[HP EliteBook 8560w] Can't change screen brightness
https://bugs.launchpad.net/bugs/2050805
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-hwe-6.5 in Ubuntu.

-- 
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 1942935] Re: kernel io hangs during mdcheck/resync

2024-01-22 Thread Brian Corriveau

I was able to reproduce the hang problem using the script mdhang.sh
(modified for my raid device location) on 22.04 with kernel 5.15 several
times, usually within 10-15 minutes.

Using 22.04 hwe kernel 6.5 I was not able to reproduce the problem with
a 25+ hours run of the same script. Seems something has been fixed in
the newer hwe kernel.

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

Title:
  kernel io hangs during mdcheck/resync

Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.11 package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.15 package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.4 package in Ubuntu:
  Confirmed

Bug description:
  It seems to always occur during an mdcheck/resync, if I am logged in
  via SSH it is still somewhat responsive and basic utilities like dmesg
  will work.  But it apppears any write I/O will hang the terminal and
  nothing is written to syslog (presumably because it is blocked).

  Below is output of dmesg and cat /proc/mdstat, it appears the data
  check was interrupted and /proc/mdstat still shows progress, and a
  whole slew of hung tasks including md1_resync itself.

  [756484.534293] md: data-check of RAID array md0
  [756484.628039] md: delaying data-check of md1 until md0 has finished (they 
share one or more physical units)
  [756493.808773] md: md0: data-check done.
  [756493.829760] md: data-check of RAID array md1
  [778112.446410] md: md1: data-check interrupted.
  [810654.608102] md: data-check of RAID array md1
  [832291.201064] md: md1: data-check interrupted.
  [899745.389485] md: data-check of RAID array md1
  [921395.835305] md: md1: data-check interrupted.
  [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 
seconds.
  [921588.558846]   Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu
  [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [921588.558854] task:systemd-journal state:D stack:0 pid:  376 ppid: 
1 flags:0x0220
  [921588.558859] Call Trace:
  [921588.558864]  __schedule+0x44c/0x8a0
  [921588.558872]  schedule+0x4f/0xc0
  [921588.558876]  md_write_start+0x150/0x240
  [921588.558880]  ? wait_woken+0x80/0x80
  [921588.558886]  raid5_make_request+0x88/0x890 [raid456]
  [921588.558898]  ? wait_woken+0x80/0x80
  [921588.558901]  ? mempool_kmalloc+0x17/0x20
  [921588.558904]  md_handle_request+0x12d/0x1a0
  [921588.558907]  ? __part_start_io_acct+0x51/0xf0
  [921588.558912]  md_submit_bio+0xca/0x100
  [921588.558915]  submit_bio_noacct+0x112/0x4f0
  [921588.558918]  ? ext4_fc_reserve_space+0x110/0x230
  [921588.558922]  submit_bio+0x51/0x1a0
  [921588.558925]  ? _cond_resched+0x19/0x30
  [921588.558928]  ? kmem_cache_alloc+0x38e/0x440
  [921588.558932]  ? ext4_init_io_end+0x1f/0x50
  [921588.558936]  ext4_io_submit+0x4d/0x60
  [921588.558940]  ext4_writepages+0x2c6/0xcd0
  [921588.558944]  do_writepages+0x43/0xd0
  [921588.558948]  ? do_writepages+0x43/0xd0
  [921588.558951]  ? fault_dirty_shared_page+0xa5/0x110
  [921588.558955]  __filemap_fdatawrite_range+0xcc/0x110
  [921588.558960]  file_write_and_wait_range+0x74/0xc0
  [921588.558962]  ext4_sync_file+0xf5/0x350
  [921588.558967]  vfs_fsync_range+0x49/0x80
  [921588.558970]  do_fsync+0x3d/0x70
  [921588.558973]  __x64_sys_fsync+0x14/0x20
  [921588.558976]  do_syscall_64+0x38/0x90
  [921588.558980]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [921588.558984] RIP: 0033:0x7f4c97ee832b
  [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 
004a
  [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 
7f4c97ee832b
  [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 
0021
  [921588.558995] RBP: 0001 R08:  R09: 
7ffdceb29fa8
  [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 
7ffdceb29fa8
  [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 
55ced34bcf90
  [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds.
  [921588.559018]   Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu
  [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [921588.559025] task:mysqld  state:D stack:0 pid: 1505 ppid: 
1 flags:0x
  [921588.559030] Call Trace:
  [921588.559032]  __schedule+0x44c/0x8a0
  [921588.559036]  schedule+0x4f/0xc0
  [921588.559040]  md_write_start+0x150/0x240
  [921588.559044]  ? wait_woken+0x80/0x80
  [921588.559047]  raid5_make_request+0x88/0x890 [raid456]
  [921588.559056]  ? wait_woken+0x80/0x80
  [921588.559059]  ? mempool_kmalloc+0x17/0x20
  [921588.559062]  md_handle_request+0x12d/0x1a0
  [921588.559065]  ? __part_start_io_acct+0x51/0xf0
  [921588.559068]  md_submit_bio+0xca/0x100
  [921588.559071]

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-lowlatency/5.15.0.94.94)

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

linux-lowlatency/5.15.0-94.104 (amd64, arm64)
systemd/249.11-0ubuntu3.11 (arm64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2049635] Re: Roll UDA & ERD drivers from 525 to 535

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

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

Title:
  Roll UDA & ERD drivers from 525 to 535

Status in fabric-manager-535 package in Ubuntu:
  New
Status in libnvidia-nscq-535 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  New

Bug description:
  [ Impact ]

   * 525 series of drivers is now end of life, roll these to 535 via
  transitional packages

   * 535 is a longterm branch

  [ Test Plan ]

   * Install 525, 525-open, 525-server drivers with LRM using ubuntu-drivers
   * Enable proposed
   * apt full-upgrade should upgrade both userspace drivers and LRM to 
respective 535, 535-open, 535-server drivers

  [ Where problems could occur ]

   * Virtual provides in the past have caused kernel flavour switch during such 
rolls before, this remains unresolved.
   * All cards supported by 525 series of the driver are supported by the 535 
driver, thus there is no loss of functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2049635/+subscriptions


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-nvidia/5.15.0.1044.44)

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

wireguard/unknown (arm64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2039167] Re: I get this message "array-index-out-of-bounds" every time I turn on my laptop since I upgraded from 23.04. to 23.10. (drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwm

2024-01-22 Thread samuelbailey

Not completely sure whether this is an identical issue, but at the very
least looks very similar, I was seeing:

UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-
hwe-6.5-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/vega10_processpptables.c:621:5

A workaround appears to have been found here:
https://bugzilla.kernel.org/show_bug.cgi?id=201957#c94

Setting the kernel parameter amdgpu.mcbp=0 appears to have stopped the
crashing for me.

** Bug watch added: Linux Kernel Bug Tracker #201957
   https://bugzilla.kernel.org/show_bug.cgi?id=201957

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

Title:
  I get this message "array-index-out-of-bounds"  every time I turn on
  my laptop since I upgraded from 23.04. to 23.10.
  (drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  UBSAN: array-index-out-of-bounds in 
/build/linux-D15vQj/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:929:40
  index 1 is out of range for type 'UCHAR [1]'

  My firmware version is X515DAP.311.
  OS type 64-bit.
  GNOME version 45.0.
  Kernel version Linux 6.5.0-9-generic.

  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zoran  2329 F wireplumber
   /dev/snd/controlC0:  zoran  2329 F wireplumber
   /dev/snd/seq:zoran  2316 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 13:42:16 2023
  InstallationDate: Installed on 2023-09-21 (21 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=9b0c8205-22d2-4c7e-8e53-959a91e2174d ro quiet splash 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-12 (0 days ago)
  dmi.bios.date: 01/06/2023
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X515DAP.311
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X515DAP
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX515DAP.311:bd01/06/2023:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX515DAP_M515DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX515DAP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUSLaptop
  dmi.product.name: VivoBook_ASUSLaptop X515DAP_M515DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039167/+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 2007055] Re: cifs/samba mount not preserving file timestamps

2024-01-22 Thread Nicholas Neumann

So I encountered this recently as well. I've got some strong evidence
that at least part of the problem is the SMB *server*, specifically a
Synology NAS.

We are migrating from a TrueNAS to Synology, and I noticed the timestamp
issue after rsync'ing files from an Ubuntu 22.04 client. I simplified by
switching to cp -p and then proceeded to grab network captures of
copying a single file from the client via cp -p.

Performing cp -p to the TrueNAS device preserves modification time. The same 
command to the synology device does not. The network captures are very similar. 
Of particular note, they both send the same SMB2_FILE_BASIC_INFO:
SMB2_FILE_BASIC_INFO
Create: No time specified (0)
Last Access: Jan 22, 2024 13:15:35.923752400 Central Standard Time
Last Write: Nov 22, 2023 13:15:09.416423500 Central Standard Time
Last Change: Jan 22, 2024 13:23:52.482749400 Central Standard Time
File Attributes: 0x
Unknown: 

Interestingly, on Windows, where a simple "copy" command line operation 
preserves the file modification time on the Synology share, sends slightly 
different info:
SMB2_FILE_BASIC_INFO
Create: No time specified (0)
Last Access: No time specified (0)
Last Write: Nov 22, 2023 13:15:09.416423500 Central Standard Time
Last Change: Jan 22, 2024 13:34:57.144137700 Central Standard Time
File Attributes: 0x
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/2007055

Title:
  cifs/samba mount not preserving file timestamps

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

Bug description:
  I think I've found a bug or regression in something when trying to
  mount a remote samba share. Modified/Created times are not properly
  preserved in newer versions of Ubuntu. Because of this, rsync thinks
  files are different based on their modified times and keeps re-syncing
  them.

  I have a NAS on my network, running samba.

  I have two devices, a desktop and laptop. Both are running Ubuntu, and
  set up the exact same way. The desktop is running ubuntu 20.04, the
  laptop 22.04.

  I have mounted the NAS on both devices the exact same way. I attempt
  to copy a file (rsync) the exact same way. On the 20.04 desktop, this
  works perfectly fine. On the 22.04 laptop, the modified times are not
  preserved and set to the current time, preventing things like rsync -t
  from working.

  The only difference i can find is that between the two systems, the newer 
laptop 22.04 mount adds a few more options than the older system to the cifs 
mount options. These are added automatically without being specified explicitly 
(see the mount -v output below): 
  * 'forceuid'/'forcegid' are changed to 'noforceuid'/'noforcegid
  *  iocharset=utf8 added
  *  serverino added

  desktop:

  $ lsb_release -rd
  Description:Ubuntu 20.04.5 LTS
  Release:20.04
  $ apt-cache policy cifs-utils
  cifs-utils:
Installed: 2:6.9-1ubuntu0.2
Candidate: 2:6.9-1ubuntu0.2
Version table:
   *** 2:6.9-1ubuntu0.2 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2:6.9-1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  $ uname -a
  Linux desktop 5.4.0-132-generic #148-Ubuntu SMP Mon Oct 17 16:02:06 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux
  $ mount -v 
  //nas/backup on /media/scratch type cifs 
(rw,relatime,vers=3.0,cache=strict,username=nas_rw,uid=1000,forceuid,gid=1000,forcegid,addr=192.168.1.10,file_mode=0664,dir_mode=0775,soft,nounix,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1)

  
  laptop:

  $ lsb_release -rd
  Description:KDE neon 5.26
  Release:22.04
  $ apt-cache policy cifs-utils
  cifs-utils:
Installed: 2:6.14-1ubuntu0.1
Candidate: 2:6.14-1ubuntu0.1
Version table:
   *** 2:6.14-1ubuntu0.1 500
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   2:6.14-1build1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  $ uname -a
  Linux laptop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 
x86_64 x86_64 x86_64 GNU/Linux
  $ mount -v
  //nas/backup on /media/scratch type cifs 
(rw,relatime,vers=3.0,cache=strict,username=nas_rw,uid=1000,noforceuid,gid=1000,noforcegid,addr=192.168.1.10,file_mode=0664,dir_mode=0775,iocharset=utf8,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1)

  the remote NAS is a synology appliance, running Samba version 4.10.18.
  SMB version 3

  Steps to reproduce:
  1. Similar setup, 1 device running 20.04,

[Kernel-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

2024-01-22 Thread Steve Langasek

Removing packages from noble:
nvidia-graphics-drivers-515-server 515.105.01-0ubuntu2 in noble
libnvidia-cfg1-510-server 515.105.01-0ubuntu2 in noble amd64
libnvidia-cfg1-510-server 515.105.01-0ubuntu2 in noble arm64
libnvidia-common-510-server 515.105.01-0ubuntu2 in noble amd64
libnvidia-common-510-server 515.105.01-0ubuntu2 in noble arm64
libnvidia-common-510-server 515.105.01-0ubuntu2 in noble armhf
libnvidia-common-510-server 515.105.01-0ubuntu2 in noble i386
libnvidia-common-510-server 515.105.01-0ubuntu2 in noble ppc64el
libnvidia-common-510-server 515.105.01-0ubuntu2 in noble riscv64
libnvidia-common-510-server 515.105.01-0ubuntu2 in noble s390x
libnvidia-common-515-server 515.105.01-0ubuntu2 in noble amd64
libnvidia-common-515-server 515.105.01-0ubuntu2 in noble arm64
libnvidia-common-515-server 515.105.01-0ubuntu2 in noble armhf
libnvidia-common-515-server 515.105.01-0ubuntu2 in noble i386
libnvidia-common-515-server 515.105.01-0ubuntu2 in noble ppc64el
libnvidia-common-515-server 515.105.01-0ubuntu2 in noble riscv64
libnvidia-common-515-server 515.105.01-0ubuntu2 in noble s390x
libnvidia-compute-510-server 515.105.01-0ubuntu2 in noble amd64
libnvidia-compute-510-server 515.105.01-0ubuntu2 in noble arm64
libnvidia-compute-510-server 515.105.01-0ubuntu2 in noble i386
libnvidia-decode-510-server 515.105.01-0ubuntu2 in noble amd64
libnvidia-decode-510-server 515.105.01-0ubuntu2 in noble arm64
libnvidia-decode-510-server 515.105.01-0ubuntu2 in noble i386
libnvidia-encode-510-server 515.105.01-0ubuntu2 in noble amd64
libnvidia-encode-510-server 515.105.01-0ubuntu2 in noble arm64
libnvidia-encode-510-server 515.105.01-0ubuntu2 in noble i386
libnvidia-extra-510-server 515.105.01-0ubuntu2 in noble amd64
libnvidia-extra-510-server 515.105.01-0ubuntu2 in noble arm64
libnvidia-extra-510-server 515.105.01-0ubuntu2 in noble i386
libnvidia-fbc1-510-server 515.105.01-0ubuntu2 in noble amd64
libnvidia-fbc1-510-server 515.105.01-0ubuntu2 in noble arm64
libnvidia-fbc1-510-server 515.105.01-0ubuntu2 in noble i386
libnvidia-gl-510-server 515.105.01-0ubuntu2 in noble amd64
libnvidia-gl-510-server 515.105.01-0ubuntu2 in noble arm64
libnvidia-gl-510-server 515.105.01-0ubuntu2 in noble i386
nvidia-compute-utils-510-server 515.105.01-0ubuntu2 in noble 
amd64
nvidia-compute-utils-510-server 515.105.01-0ubuntu2 in noble 
arm64
nvidia-dkms-510-server 515.105.01-0ubuntu2 in noble amd64
nvidia-dkms-510-server 515.105.01-0ubuntu2 in noble arm64
nvidia-driver-510-server 515.105.01-0ubuntu2 in noble amd64
nvidia-driver-510-server 515.105.01-0ubuntu2 in noble arm64
nvidia-headless-510-server 515.105.01-0ubuntu2 in noble amd64
nvidia-headless-510-server 515.105.01-0ubuntu2 in noble arm64
nvidia-headless-no-dkms-510-server 515.105.01-0ubuntu2 in noble 
amd64
nvidia-headless-no-dkms-510-server 515.105.01-0ubuntu2 in noble 
arm64
nvidia-kernel-common-510-server 515.105.01-0ubuntu2 in noble 
amd64
nvidia-kernel-common-510-server 515.105.01-0ubuntu2 in noble 
arm64
nvidia-kernel-source-510-server 515.105.01-0ubuntu2 in noble 
amd64
nvidia-kernel-source-510-server 515.105.01-0ubuntu2 in noble 
arm64
nvidia-utils-510-server 515.105.01-0ubuntu2 in noble amd64
nvidia-utils-510-server 515.105.01-0ubuntu2 in noble arm64
xserver-xorg-video-nvidia-510-server 515.105.01-0ubuntu2 in 
noble amd64
xserver-xorg-video-nvidia-510-server 515.105.01-0ubuntu2 in 
noble arm64
Comment: Unsupported driver version; LP: #2048087
1 package successfully removed.


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

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450

[Kernel-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

2024-01-22 Thread Steve Langasek

Removing packages from noble:
nvidia-graphics-drivers-460 460.91.03-0ubuntu1 in noble
libnvidia-cfg1-450 460.91.03-0ubuntu1 in noble amd64
libnvidia-cfg1-455 460.91.03-0ubuntu1 in noble amd64
libnvidia-common-450 460.91.03-0ubuntu1 in noble amd64
libnvidia-common-450 460.91.03-0ubuntu1 in noble arm64
libnvidia-common-450 460.91.03-0ubuntu1 in noble armhf
libnvidia-common-450 460.91.03-0ubuntu1 in noble i386
libnvidia-common-450 460.91.03-0ubuntu1 in noble ppc64el
libnvidia-common-450 460.91.03-0ubuntu1 in noble riscv64
libnvidia-common-450 460.91.03-0ubuntu1 in noble s390x
libnvidia-common-455 460.91.03-0ubuntu1 in noble amd64
libnvidia-common-455 460.91.03-0ubuntu1 in noble arm64
libnvidia-common-455 460.91.03-0ubuntu1 in noble armhf
libnvidia-common-455 460.91.03-0ubuntu1 in noble i386
libnvidia-common-455 460.91.03-0ubuntu1 in noble ppc64el
libnvidia-common-455 460.91.03-0ubuntu1 in noble riscv64
libnvidia-common-455 460.91.03-0ubuntu1 in noble s390x
libnvidia-common-460 460.91.03-0ubuntu1 in noble amd64
libnvidia-common-460 460.91.03-0ubuntu1 in noble arm64
libnvidia-common-460 460.91.03-0ubuntu1 in noble armhf
libnvidia-common-460 460.91.03-0ubuntu1 in noble i386
libnvidia-common-460 460.91.03-0ubuntu1 in noble ppc64el
libnvidia-common-460 460.91.03-0ubuntu1 in noble riscv64
libnvidia-common-460 460.91.03-0ubuntu1 in noble s390x
libnvidia-compute-450 460.91.03-0ubuntu1 in noble amd64
libnvidia-compute-450 460.91.03-0ubuntu1 in noble i386
libnvidia-compute-455 460.91.03-0ubuntu1 in noble amd64
libnvidia-compute-455 460.91.03-0ubuntu1 in noble i386
libnvidia-decode-450 460.91.03-0ubuntu1 in noble amd64
libnvidia-decode-450 460.91.03-0ubuntu1 in noble i386
libnvidia-decode-455 460.91.03-0ubuntu1 in noble amd64
libnvidia-decode-455 460.91.03-0ubuntu1 in noble i386
libnvidia-encode-450 460.91.03-0ubuntu1 in noble amd64
libnvidia-encode-450 460.91.03-0ubuntu1 in noble i386
libnvidia-encode-455 460.91.03-0ubuntu1 in noble amd64
libnvidia-encode-455 460.91.03-0ubuntu1 in noble i386
libnvidia-extra-450 460.91.03-0ubuntu1 in noble amd64
libnvidia-extra-450 460.91.03-0ubuntu1 in noble i386
libnvidia-extra-455 460.91.03-0ubuntu1 in noble amd64
libnvidia-extra-455 460.91.03-0ubuntu1 in noble i386
libnvidia-fbc1-450 460.91.03-0ubuntu1 in noble amd64
libnvidia-fbc1-450 460.91.03-0ubuntu1 in noble i386
libnvidia-fbc1-455 460.91.03-0ubuntu1 in noble amd64
libnvidia-fbc1-455 460.91.03-0ubuntu1 in noble i386
libnvidia-gl-450 460.91.03-0ubuntu1 in noble amd64
libnvidia-gl-450 460.91.03-0ubuntu1 in noble i386
libnvidia-gl-455 460.91.03-0ubuntu1 in noble amd64
libnvidia-gl-455 460.91.03-0ubuntu1 in noble i386
libnvidia-ifr1-450 460.91.03-0ubuntu1 in noble amd64
libnvidia-ifr1-450 460.91.03-0ubuntu1 in noble i386
libnvidia-ifr1-455 460.91.03-0ubuntu1 in noble amd64
libnvidia-ifr1-455 460.91.03-0ubuntu1 in noble i386
nvidia-compute-utils-450 460.91.03-0ubuntu1 in noble amd64
nvidia-compute-utils-455 460.91.03-0ubuntu1 in noble amd64
nvidia-dkms-450 460.91.03-0ubuntu1 in noble amd64
nvidia-dkms-455 460.91.03-0ubuntu1 in noble amd64
nvidia-driver-450 460.91.03-0ubuntu1 in noble amd64
nvidia-driver-455 460.91.03-0ubuntu1 in noble amd64
nvidia-headless-450 460.91.03-0ubuntu1 in noble amd64
nvidia-headless-455 460.91.03-0ubuntu1 in noble amd64
nvidia-headless-no-dkms-450 460.91.03-0ubuntu1 in noble amd64
nvidia-headless-no-dkms-455 460.91.03-0ubuntu1 in noble amd64
nvidia-kernel-common-450 460.91.03-0ubuntu1 in noble amd64
nvidia-kernel-common-455 460.91.03-0ubuntu1 in noble amd64
nvidia-kernel-source-450 460.91.03-0ubuntu1 in noble amd64
nvidia-kernel-source-455 460.91.03-0ubuntu1 in noble amd64
nvidia-utils-450 460.91.03-0ubuntu1 in noble amd64
nvidia-utils-455 460.91.03-0ubuntu1 in noble amd64
xserver-xorg-video-nvidia-450 460.91.03-0ubuntu1 in noble amd64
xserver-xorg-video-nvidia-455 460.91.03-0ubuntu1 in noble amd64
Comment:

[Kernel-packages] [Bug 2047712] Re: FS disconnects on WD PC SN810 SDCPNRZ HP FW

2024-01-22 Thread Martin Kvanta

Hello,

After some additional investigation it seems more to some kind of problem with 
Standby mode.
I checked this discussion and tried the AMD S2IDLE analysis script to debug 
ACPI standby. 
https://discussion.fedoraproject.org/t/please-improve-the-s0ix-experience-under-linux/79113/2
But no new info found. 

As next step I will try to install other SSD from Kingston to check if
this is Disk or System error.

For now I configured system to use Hibernation instead to Standby (only 
available is s2idle).
I followed this Discussion to enable Hibernation in System menu:
https://askubuntu.com/questions/1405990/hibernate-entry-in-the-menu-on-22-04

m

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

Title:
  FS disconnects on WD PC SN810 SDCPNRZ HP FW

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  I bought notebook HP ZBook Firefly 14 G10 A with AMD Ryzen 7 7840HS CPU.
  This notebook have nvme SSD WD PC SN810 SDCPNRZ-2T00 with HPS2 firmware.

  When I use standard Ubuntu kernel 6.5.0-14-generic, disk regularly 
disconnects and FS become ReadOnly.
  I found similar issue with eg. Kingston A2000 nvme disk. This seems to 
Firmware bug.
  I tried same solution and this worked.

  As first workaround I tried add kernel parameter 
"nvme_core.default_ps_max_latency_us=1".
  Behavior was much better, but sometimes disk still disconnects (after connect 
disconnect from Thunderbolt docking station or after several sleep/wake cycles)

  Second workaround was update kernel source code and setup quirk 
"NVME_QUIRK_NO_DEEPEST_PS" for disk identifier. Then I build kernel package and 
install it on notebook with Ubuntu 23.10.
  After ~4days of usage it seems that this is working solution.

  Now I running my own kernel build 6.5.3 (from sources downloaded via
  apt package manager), this is reason why I cannot provide "ubuntu-bug
  linux" output.

  Will be possible to add this solution to the default kernel image please? 
  I'm not a developer and not sure if this is all you need.
  I can provide additional info or testing if will be needed.

  --
  Updated was file "linux-6.5.0/drivers/nvme/host/pci.c" with following lines:

  --- drivers-nvme-host-pci.c.original  2023-12-29 20:48:38.048105439 +0100
  +++ drivers-nvme-host-pci.c.new   2023-12-29 20:48:38.064104967 +0100
  @@ -3399,6 +3399,8 @@
.driver_data = NVME_QUIRK_BOGUS_NID, },
{ PCI_DEVICE(0x15b7, 0x2001),   /*  Sandisk Skyhawk */
.driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
  + { PCI_DEVICE(0x15b7, 0x5011),   /* Sandisk Corp WD PC SN810 
SDCPNRZ-2T00 (HPS2 FW) */
  +.driver_data = NVME_QUIRK_NO_DEEPEST_PS, },  
{ PCI_DEVICE(0x1d97, 0x2263),   /* SPCC */
.driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
{ PCI_DEVICE(0x144d, 0xa80b),   /* Samsung PM9B1 256G and 512G */

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

  --
  $ apt-cache policy linux-image-6.5.0-14-generic 
  linux-image-6.5.0-14-generic:
Installed: 6.5.0-14.14
Candidate: 6.5.0-14.14
Version table:
   *** 6.5.0-14.14 500
  500 http://sk.archive.ubuntu.com/ubuntu mantic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu mantic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy linux-image-6.5.3 
  linux-image-6.5.3:
Installed: 6.5.3-2
Candidate: 6.5.3-2
Version table:
   *** 6.5.3-2 100
  100 /var/lib/dpkg/status

  --
  $ sudo smartctl -ic /dev/nvme0n1
  smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.5.3] (local build)
  Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF INFORMATION SECTION ===
  Model Number:   WD PC SN810 SDCPNRZ-2T00-1006
  Serial Number:  
  Firmware Version:   HPS2
  PCI Vendor/Subsystem ID:0x15b7
  IEEE OUI Identifier:0x001b44
  Total NVM Capacity: 2 048 408 248 320 [2,04 TB]
  Unallocated NVM Capacity:   0
  Controller ID:  8224
  NVMe Version:   1.4
  Number of Namespaces:   1
  Namespace 1 Size/Capacity:  2 048 408 248 320 [2,04 TB]
  Namespace 1 Formatted LBA Size: 512
  Namespace 1 IEEE EUI-64:001b44 8b4a02b37b
  Local Time is:  Fri Dec 29 21:04:43 2023 CET
  Firmware Updates (0x14):2 Slots, no Reset required
  Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
  Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat 
Timestmp
  Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg 
Pers_Ev_Lg
  Maximum Data Transfer Size: 128 Pages

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-nvidia/5.15.0-1044.44)

All autopkgtests for the newly accepted linux-restricted-modules-nvidia 
(5.15.0-1044.44) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (armhf)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-nvidia

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Same for 515-server:

$ reverse-depends src:nvidia-graphics-drivers-515-server
Reverse-Depends
===
* libnvidia-decode-510-server (for libnvidia-decode-515-server)
* libnvidia-encode-510-server (for libnvidia-encode-515-server)

these too have transitionals via 515-server to 525-server, in a similar
manner, in jammy chroot:

# apt install libnvidia-decode-510-server libnvidia-encode-510-server
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  libbsd0 libmd0 libnvidia-compute-525-server libnvidia-decode-515-server
  libnvidia-decode-525-server libnvidia-encode-515-server 
libnvidia-encode-525-server
  libx11-6 libx11-data libxau6 libxcb1 libxdmcp6 libxext6
The following NEW packages will be installed:
  libbsd0 libmd0 libnvidia-compute-525-server libnvidia-decode-510-server
  libnvidia-decode-515-server libnvidia-decode-525-server 
libnvidia-encode-510-server
  libnvidia-encode-515-server libnvidia-encode-525-server libx11-6 libx11-data 
libxau6
  libxcb1 libxdmcp6 libxext6


** Changed in: nvidia-graphics-drivers-515-server (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: nvidia-graphics-drivers-515-server (Ubuntu)
 Assignee: (unassigned) => Steve Langasek (vorlon)

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Fix Released

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+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 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

About this:

$ reverse-depends src:nvidia-graphics-drivers-460
Reverse-Depends
===
* libnvidia-decode-455 (for libnvidia-decode-460)
* libnvidia-encode-455 (for libnvidia-encode-460)
* nvidia-headless-455 [amd64] (for nvidia-headless-460)
* nvidia-kernel-common-455 [amd64]

Packages without architectures listed are reverse-dependencies in:
amd64, i386


in all rmadison releases the above -455 binary packages have versions 
460.91.03-*, meaning they got transitioned / taken over by 
nvidia-graphics-drivers-460.

in turn the equivalent -460 packages, have versions 470.* meaning they
all got taken over by nvidia-graphics-drivers-470 (still supported).
This is true in all updates, but also jammy release pocket.

This means it is safe to drop them from noble.

In jammy chroot:

(jammy-amd64)root@xnox-Inspiron-7400:~# apt install libnvidia-decode-455 
libnvidia-encode-455 nvidia-headless-455 nvidia-kernel-common-455
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  cpp-12 dctrl-tools dkms gcc-12 kmod libasan8 libbsd0 libgcc-12-dev libmd0
  libnvidia-cfg1-470 libnvidia-compute-470 libnvidia-decode-460 
libnvidia-decode-470
  libnvidia-encode-460 libnvidia-encode-470 libpciaccess0 libtsan2 libx11-6 
libx11-data
  libxau6 libxcb1 libxdmcp6 libxext6 nvidia-compute-utils-470 nvidia-dkms-470
  nvidia-headless-460 nvidia-headless-470 nvidia-headless-no-dkms-470
  nvidia-kernel-common-460 nvidia-kernel-common-470 nvidia-kernel-source-470

Please let me know if above inspection is sufficient, or if you want me
to upload nvidia-graphics-drivers-470 that explicitly produces the 455
transitionals, to avoid double source/binary package jump chain?

** Changed in: nvidia-graphics-drivers-460 (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: nvidia-graphics-drivers-460 (Ubuntu)
 Assignee: (unassigned) => Steve Langasek (vorlon)

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Fix Released

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.15/5.15.0.94.104~20.04.50)

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

systemd/245.4-4ubuntu3.22 (armhf)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble

2024-01-22 Thread dann frazier

I ran into this on jammy/amd64:
https://autopkgtest.ubuntu.com/results/autopkgtest-
jammy/jammy/amd64/l/livecd-rootfs/20240121_173406_e4f9a@/log.gz

I downloaded all of the amd64 failures and searched for this failure
pattern. These were the kernels that were running at the time:

"Linux 5.15.0-91-generic #101-Ubuntu SMP Tue Nov 14 13:30:08 UTC 2023"
"Linux 6.2.0-21-generic #21-Ubuntu SMP PREEMPT_DYNAMIC Fri Apr 14 12:34:02 UTC 
2023"
"Linux 6.3.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Jun  8 16:02:30 UTC 
2023"
"Linux 6.5.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Sat Oct  7 01:35:40 UTC 
2023"
"Linux 6.6.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 30 10:27:29 UTC 
2023"

Here's the count of failures per image type:
 12 017-disk-image-uefi.binary
  3 018-disk-image.binary
  3 020-kvm-image.binary
  1 023-vagrant.binary
  1 024-vagrant.binary

I can confirm that /dev/loop0p1 is created by devtmpfs. This surprised
me because I'd never actually need to know what devtmpfs was, and I saw
devices being created even though I had SIGSTOP'd systemd-udevd. But
watching udevadm monitor and forktrace output convinced me.

I had a theory that something was opening the first created partition before 
all partitions were created. loop_reread_partitions() can fail without 
returning an error to userspace:
 https://elixir.bootlin.com/linux/v5.15.147/source/drivers/block/loop.c#L676

that could happen if bdev_disk_changed() aborts because it finds another 
partition on the device is open:
 https://elixir.bootlin.com/linux/v5.15.147/source/block/partitions/core.c#L662

But then we should see this in dmesg:
  pr_warn("%s: partition scan of loop%d (%s) failed (rc=%d)\n"

I added dmesg calls to check that:
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-dannf-test/jammy/amd64/l/livecd-rootfs/20240122_161631_62ecd@/log.gz

.. but no such message appeared, so that's not it. But what *is*
interesting there is that it shows *2* partition scan lines:

1248s [  990.855361] loop0: detected capacity change from 0 to 4612096
1248s [  990.855628]  loop0: p1 p14 p15
1248s [  990.874241]  loop0: p1 p14 p15

Previously we just saw 1:

1189s [  932.268459] loop0: detected capacity change from 0 to 4612096
1189s [  932.268715]  loop0: p1 p14 p15

That only gets printed when bdev_disk_changed() is called. So do we have
2 racing callers?

One thing that seems off is that loop_configure() unsuppresses uevents
for the full device before the partition scan, but loop_change_fd()
waits until the partition scan is complete. Shouldn't they be following
the same pattern? I wonder if that could cause the following race:

[livecd-rootfs] losetup creates /dev/loop0
[livecd-rootfs] kernel sends uevent for /dev/loop0
[livecd-rootfs] /dev/loop0p* appear in devtmpfs
  [udev] receives uevent for loop0
  [udev] partprobe /dev/loop0
[livecd-rootfs] losetup exit(0)
  [partprobe] /dev/loop0p* cleared
[livecd-rootfs] check for /dev/loop0p1 FAILS
  [partprobe] /dev/loop0p* recreated

I tried checking for this using ftrace in a local jammy VM. I haven't been able 
to reproduce this in a local VM, but I wanted to see what happens in a normal 
losetup.. er... setup.
 
> First I used losetup to create the device:

root@dannf-livecd-rootfs-debug:/sys/kernel/debug/tracing# loopdev="$(losetup 
--show -f -P -v /home/ubuntu/disk.img)"
root@dannf-livecd-rootfs-debug:/sys/kernel/debug/tracing# cat trace
# tracer: function
#
# entries-in-buffer/entries-written: 1/1   #P:1
#
#_-=> irqs-off
#   / _=> need-resched
#  | / _---=> hardirq/softirq
#  || / _--=> preempt-depth
#  ||| / _-=> migrate-disable
#   / delay
#   TASK-PID CPU#  |  TIMESTAMP  FUNCTION
#  | | |   | | |
 losetup-1996[000] .   657.573994: bdev_disk_changed 
<-loop_reread_partitions

> Only the expected bdev_disk_change() call
> Then I remove the device:

root@dannf-livecd-rootfs-debug:/sys/kernel/debug/tracing# losetup -v -d $loopdev
root@dannf-livecd-rootfs-debug:/sys/kernel/debug/tracing# cat trace
# tracer: function
#
# entries-in-buffer/entries-written: 3/3   #P:1
#
#_-=> irqs-off
#   / _=> need-resched
#  | / _---=> hardirq/softirq
#  || / _--=> preempt-depth
#  ||| / _-=> migrate-disable
#   / delay
#   TASK-PID CPU#  |  TIMESTAMP  FUNCTION
#  | | |   | | |
 losetup-1996[000] .   657.573994: bdev_disk_changed 
<-loop_reread_partitions
   systemd-udevd-2524[000] .   680.555336: bdev_disk_changed 
<-blkdev_get_whole

[Kernel-packages] [Bug 2049991] Re: zswap is not working with Linux Kernel 6.5.x

2024-01-22 Thread Eugene San

Hello Mathew,

Thanks for responding so promptly.

I did test 6.8-rc1 and ZSWAP works as expected.

But I've noticed something odd.
To quickly test ZSWAP, I use eatmemory tool to allocate 7GB of 8GB on my system.
Allocating worked and ZSWAP activated but freeing 7GB of memory took ~45s 
(system was barely responsive) instead of usual 1-2s.
I tested on freshly booted machine on native text console (no Graphics DE) and 
I didn't see that behavior on other kernels even with very busy system.
Looks like 6.8 needs some work or maybe there were some commits that altered 
swap/zswap behavior after 6.7.1.
So if you are planning on backporting patches to 6.5 I'd base those on 6.7.1 
instead of 6.8.

I am back to using Noble's 6.6.0-14.14 which works ok for now.

P.S.
When testing mainline 6.6.13 I've had dead keyboard after suspend on my 
XPS13-9350, not sure if Nobles 6.6 has some XPS related fixes or I just was 
lucky to not catch the bug again ;-)
Please let me know if I need to open a separate bug for that.

Thanks,
Eugene.

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

Title:
  zswap is not working with Linux Kernel 6.5.x

Status in linux package in Ubuntu:
  New

Bug description:
  I recently migrated to Mantic from Jammy and noticed that 6.5.0 has
  "DEAD" zswap. It also didn't work with HWE-6.5.0 (both -9 and -14) on
  Jammy.

  Everything seems normal, all the parameters and no error msgs but frontswap 
stays 0k at all times and everything gets swapped directly to disk.
  No usage is reported in /sys/module/zswap/parameters and 
/sys/kernel/debug/zswap.

  Jammy with HWE 6.2.0 and Mantic with
  https://kernel.ubuntu.com/mainline/v6.6.13/ and
  https://kernel.ubuntu.com/mainline/v6.7.1/ work fine.

  I was able to reproduce the issue with 
https://kernel.ubuntu.com/mainline/v6.5.3/.
  (I would try the latest https://kernel.ubuntu.com/mainline/v6.5.13/ but the 
build failed due building host issues.)

  Seems like an upstream problem but not sure how to resolve it since
  Upstream 6.5 is abandoned and Jammy/Mantic 6.6 is months away...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049991/+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 2050830] Re: linux-kvm ADT test test_snapd_snap_with_vendored_apparmor failure with linux-kvm/5.15.0-1050.55

2024-01-22 Thread Kevin Becker

** Summary changed:

- linux-kvm ADT test failure with linux-kvm/5.15.0-1050.55
+ linux-kvm ADT test test_snapd_snap_with_vendored_apparmor failure with 
linux-kvm/5.15.0-1050.55

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

Title:
  linux-kvm ADT test test_snapd_snap_with_vendored_apparmor failure with
  linux-kvm/5.15.0-1050.55

Status in linux-kvm package in Ubuntu:
  New

Bug description:
  This is a scripted bug report about ADT failures while running linux-
  kvm tests for linux-kvm/5.15.0-1050.55 on jammy. Whether this is
  caused by the dep8 tests of the tested source or the kernel has yet to
  be determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-kvm/20240118_121042_1259e@/log.gz

  As part of ubuntu_qrt_apparmor, we get the following error. This also
  seems to lead to further apparmor errors.

  3461s 10:50:40 DEBUG| [stdout] Running test: './test-apparmor.py' distro: 
'Ubuntu 22.04' kernel: '5.15.0-1050.55 (Ubuntu 5.15.0-1050.55-kvm 5.15.136)' 
arch: 'amd64' init: 'systemd' uid: 0/0 SUDO_USER: 'ubuntu')
  3461s 10:50:40 ERROR| [stderr] test_snapd_snap_with_vendored_apparmor 
(__main__.ApparmorTest)
  3461s 10:50:40 ERROR| [stderr] Test snapd snap ... FAIL
  3461s 10:50:40 ERROR| [stderr] 
  3461s 10:50:40 ERROR| [stderr] 
==
  3461s 10:50:40 ERROR| [stderr] FAIL: test_snapd_snap_with_vendored_apparmor 
(__main__.ApparmorTest)
  3461s 10:50:40 ERROR| [stderr] Test snapd snap
  3461s 10:50:40 ERROR| [stderr] 
--
  3461s 10:50:40 ERROR| [stderr] Traceback (most recent call last):
  3461s 10:50:40 ERROR| [stderr]   File 
"/tmp/autopkgtest.S8Qdzf/build.EE2/src/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/./test-apparmor.py",
 line 321, in test_snapd_snap_with_vendored_apparmor
  3461s 10:50:40 ERROR| [stderr] self.install_snap("snapd", 
track="latest/stable", classic=False)
  3461s 10:50:40 ERROR| [stderr]   File 
"/tmp/autopkgtest.S8Qdzf/build.EE2/src/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/testlib.py",
 line 1339, in install_snap
  3461s 10:50:40 ERROR| [stderr] self.assertEqual(0, rc, "Failed to install 
snap %s from track %s (classic: %s)\nOutput:\n%s" %
  3461s 10:50:40 ERROR| [stderr] AssertionError: 0 != 127 : Failed to install 
snap snapd from track latest/stable (classic: False)
  3461s 10:50:40 ERROR| [stderr] Output:
  3461s 10:50:40 ERROR| [stderr] [Errno 2] No such file or directory: 'snap'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/2050830/+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 2050830] [NEW] linux-kvm ADT test failure with linux-kvm/5.15.0-1050.55

2024-01-22 Thread Kevin Becker

Public bug reported:

This is a scripted bug report about ADT failures while running linux-kvm
tests for linux-kvm/5.15.0-1050.55 on jammy. Whether this is caused by
the dep8 tests of the tested source or the kernel has yet to be
determined.

Testing failed on:
amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-kvm/20240118_121042_1259e@/log.gz

As part of ubuntu_qrt_apparmor, we get the following error. This also
seems to lead to further apparmor errors.

3461s 10:50:40 DEBUG| [stdout] Running test: './test-apparmor.py' distro: 
'Ubuntu 22.04' kernel: '5.15.0-1050.55 (Ubuntu 5.15.0-1050.55-kvm 5.15.136)' 
arch: 'amd64' init: 'systemd' uid: 0/0 SUDO_USER: 'ubuntu')
3461s 10:50:40 ERROR| [stderr] test_snapd_snap_with_vendored_apparmor 
(__main__.ApparmorTest)
3461s 10:50:40 ERROR| [stderr] Test snapd snap ... FAIL
3461s 10:50:40 ERROR| [stderr] 
3461s 10:50:40 ERROR| [stderr] 
==
3461s 10:50:40 ERROR| [stderr] FAIL: test_snapd_snap_with_vendored_apparmor 
(__main__.ApparmorTest)
3461s 10:50:40 ERROR| [stderr] Test snapd snap
3461s 10:50:40 ERROR| [stderr] 
--
3461s 10:50:40 ERROR| [stderr] Traceback (most recent call last):
3461s 10:50:40 ERROR| [stderr]   File 
"/tmp/autopkgtest.S8Qdzf/build.EE2/src/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/./test-apparmor.py",
 line 321, in test_snapd_snap_with_vendored_apparmor
3461s 10:50:40 ERROR| [stderr] self.install_snap("snapd", 
track="latest/stable", classic=False)
3461s 10:50:40 ERROR| [stderr]   File 
"/tmp/autopkgtest.S8Qdzf/build.EE2/src/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/testlib.py",
 line 1339, in install_snap
3461s 10:50:40 ERROR| [stderr] self.assertEqual(0, rc, "Failed to install 
snap %s from track %s (classic: %s)\nOutput:\n%s" %
3461s 10:50:40 ERROR| [stderr] AssertionError: 0 != 127 : Failed to install 
snap snapd from track latest/stable (classic: False)
3461s 10:50:40 ERROR| [stderr] Output:
3461s 10:50:40 ERROR| [stderr] [Errno 2] No such file or directory: 'snap'

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


** Tags: 5.15 amd64 jammy kernel-adt-failure kvm sru-20240108

** Tags added: kernel-adt-failure

** Description changed:

  This is a scripted bug report about ADT failures while running linux-kvm
  tests for linux-kvm/5.15.0-1050.55 on jammy. Whether this is caused by
  the dep8 tests of the tested source or the kernel has yet to be
  determined.
  
  Testing failed on:
- amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-kvm/20240118_121042_1259e@/log.gz
+ amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-kvm/20240118_121042_1259e@/log.gz
+ 
+ As part of ubuntu_qrt_apparmor, we get the following error. This also
+ seems to lead to further apparmor errors.
+ 
+ 3461s 10:50:40 DEBUG| [stdout] Running test: './test-apparmor.py' distro: 
'Ubuntu 22.04' kernel: '5.15.0-1050.55 (Ubuntu 5.15.0-1050.55-kvm 5.15.136)' 
arch: 'amd64' init: 'systemd' uid: 0/0 SUDO_USER: 'ubuntu')
+ 3461s 10:50:40 ERROR| [stderr] test_snapd_snap_with_vendored_apparmor 
(__main__.ApparmorTest)
+ 3461s 10:50:40 ERROR| [stderr] Test snapd snap ... FAIL
+ 3461s 10:50:40 ERROR| [stderr] 
+ 3461s 10:50:40 ERROR| [stderr] 
==
+ 3461s 10:50:40 ERROR| [stderr] FAIL: test_snapd_snap_with_vendored_apparmor 
(__main__.ApparmorTest)
+ 3461s 10:50:40 ERROR| [stderr] Test snapd snap
+ 3461s 10:50:40 ERROR| [stderr] 
--
+ 3461s 10:50:40 ERROR| [stderr] Traceback (most recent call last):
+ 3461s 10:50:40 ERROR| [stderr]   File 
"/tmp/autopkgtest.S8Qdzf/build.EE2/src/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/./test-apparmor.py",
 line 321, in test_snapd_snap_with_vendored_apparmor
+ 3461s 10:50:40 ERROR| [stderr] self.install_snap("snapd", 
track="latest/stable", classic=False)
+ 3461s 10:50:40 ERROR| [stderr]   File 
"/tmp/autopkgtest.S8Qdzf/build.EE2/src/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/testlib.py",
 line 1339, in install_snap
+ 3461s 10:50:40 ERROR| [stderr] self.assertEqual(0, rc, "Failed to install 
snap %s from track %s (classic: %s)\nOutput:\n%s" %
+ 3461s 10:50:40 ERROR| [stderr] AssertionError: 0 != 127 : Failed to install 
snap snapd from track latest/stable (classic: False)
+ 3461s 10:50:40 ERROR| [stderr] Output:
+ 3461s 10:50:40 ERROR| [stderr] [Errno 2] No such file or directory: 'snap'

** Tags added: 5.15 amd64 jammy kvm sru-20240108

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.

[Kernel-packages] [Bug 2049689] Re: linux-image-5.15.0-94-generic breaks partprobe on empty loopback device

2024-01-22 Thread Allison Karlitskaya

A fix is available upstream: https://lore.kernel.org/all/f6e687cc-
debd-4864-901a-fb35be9f2...@kernel.dk/T/

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

Title:
  linux-image-5.15.0-94-generic breaks partprobe on empty loopback
  device

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

Bug description:
  This is with the kernel from jammy-proposed (linux-
  image-5.15.0-94-generic 5.15.0-94.104).

  Do this:

  # dd if=/dev/zero of=/tmp/file bs=1M count=50
  # partprobe "$(losetup --show --find /tmp/file)"

  Notice this very odd error message:

  Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
  16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32,
  33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49,
  50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on
  /dev/loop2 have been written, but we have been unable to inform the
  kernel of the change, probably because it/they are in use.  As a
  result, the old partition(s) will remain in use.  You should reboot
  now before making further changes.

  That's a result of an ioctl changing its error code in an incompatible
  way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing
  partprobe.

  5.15.0.91.88:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or 
address)

  5.15.0.94.91:
  ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0, 
length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument)

  This is a userspace API break which impacts GNU parted and util-linux
  (as confirmed by the util-linux maintainer).

  This issue was discovered as part of Cockpit CI here:
  https://github.com/cockpit-project/bots/pull/5793

  This issue is being discussed on LKML here (with a patch likely to
  land soon): https://lkml.org/lkml/2024/1/15/147

  lsb_release -rd:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049689/+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 2049922] Re: PCI ATS quirk patch needed for IDPF

2024-01-22 Thread Joseph Salisbury

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

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

** Changed in: linux-gcp (Ubuntu Bionic)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux-gcp (Ubuntu Focal)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux-gcp (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

** Changed in: linux-gcp (Ubuntu Bionic)
   Importance: Undecided => Medium

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

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

Title:
  PCI ATS quirk patch needed for IDPF

Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Bionic:
  In Progress
Status in linux-gcp source package in Focal:
  In Progress

Bug description:
  [Impact]

  * Request from Google to include Intel patches for IDPF support if used from 
out-of-tree module to
prevent system instability

  [Fix]

  * Upstream
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.7=a18615b1cfc04f00548c60eb9a77e0ce56e848fd

  [Test Case]

  * Compile test
  * Boot test
  * Test on non-IDPF instance

  [Where things could go wrong]

  * Low chance of regression, changes very isolated

  [Other Info]

  * SF #00376470

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2049922/+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 2042726] Re: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returne

** Tags removed: need-duplicate-check

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

Title:
  package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8 failed to
  install/upgrade: installed bcmwl-kernel-source package post-
  installation script subprocess returned error exit status 10

Status in bcmwl package in Ubuntu:
  New

Bug description:
  Hardware: TP-Link AC 1300 PCI

  Recognized in Ubuntu 22.04.3 LTS
  Using Broadcom 802.11 Linux STA wireless driver source from 
bcmwl-kernel-source (open source)
  However, unable to activate Wifi. Status reported as no Wifi adapter detected.

  Action: trying to troubleshoot by following the guideline at 
https://forums.linuxmint.com/viewtopic.php?t=292225
  sudo apt-get install linux-headers-generic
  sudo apt-get --reinstall install bcmwl-kernel-source

  Error package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8 failed
  to install/upgrade: installed bcmwl-kernel-source package post-
  installation script subprocess returned error exit status 10

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_6_2_0_26_26_generic_98 nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Nov  4 20:30:25 2023
  ErrorMessage: installed bcmwl-kernel-source package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2023-03-20 (228 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.9
  SourcePackage: bcmwl
  Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8 failed to 
install/upgrade: installed bcmwl-kernel-source package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/2042726/+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 2043333] Re: package linux-image-6.5.0-10-generic 6.5.0-10.10 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-6.5.0-10-generic 6.5.0-10.10 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with
  return code 11

Status in dkms package in Ubuntu:
  New

Bug description:
  I have an AMD Ryzen 7745hx CPU and the iGPU (integrated GPU from the
  CPU) is not recognised. It seems to be related to the error I
  received.

  My computer with Mantic only runs on the Nvidia graphic card because
  it doesn't take the iGPU into account. I suypposed it is because the
  CPU is fairly new to the market and that Igpu drivers are not
  integrates into the linux-genereic-6.5

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-10-generic 6.5.0-10.10
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  AptOrdering:
   gnome-metronome:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun Nov 12 21:58:39 2023
  DpkgHistoryLog:
   Start-Date: 2023-11-12  21:58:16
   Commandline: packagekit role='install-packages'
   Requested-By: kevin (1000)
   Install: gnome-metronome:amd64 (1.3.0-0ubuntu4)
  ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  InstallationDate: Installed on 2023-10-24 (19 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=b0f42ab3-3f84-4147-8b10-99e7e7ff4a5e ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: dkms
  Title: package linux-image-6.5.0-10-generic 6.5.0-10.10 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2023
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: LPCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Pro 5 16ARX8
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrLPCN44WW:bd06/28/2023:br1.44:efr1.44:svnLENOVO:pn82WM:pvrLegionPro516ARX8:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionPro516ARX8:skuLENOVO_MT_82WM_BU_idea_FM_LegionPro516ARX8:
  dmi.product.family: Legion Pro 5 16ARX8
  dmi.product.name: 82WM
  dmi.product.sku: LENOVO_MT_82WM_BU_idea_FM_Legion Pro 5 16ARX8
  dmi.product.version: Legion Pro 5 16ARX8
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/204/+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 2044412] Re: package linux-image-6.2.0-37-generic 6.2.0-37.38 failed to install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-6.2.0-37-generic 6.2.0-37.38 failed to
  install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited
  with return code 11

Status in dkms package in Ubuntu:
  New

Bug description:
  idk

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-37-generic 6.2.0-37.38
  ProcVersionSignature: Ubuntu 6.2.0-36.37-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2.1
  AptOrdering:
   linux-modules-6.2.0-37-generic:amd64: Install
   linux-image-6.2.0-37-generic:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gpalikian   2066 F pipewire
gpalikian   2079 F wireplumber
   /dev/snd/controlC0:  gpalikian   2079 F wireplumber
   /dev/snd/seq:gpalikian   2066 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Thu Nov 23 23:53:34 2023
  ErrorMessage: run-parts: /etc/kernel/header_postinst.d/dkms exited with 
return code 11
  InstallationDate: Installed on 2023-08-10 (104 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: HP OMEN Laptop 15-ek0xxx
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic 
root=UUID=e5fba644-6e55-4d06-a0dc-488db2f2f4ae ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: /usr/bin/python3.11, Python 3.11.4, python-is-python3, 3.11.1-3
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: dkms
  Title: package linux-image-6.2.0-37-generic 6.2.0-37.38 failed to 
install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with 
return code 11
  UpgradeStatus: Upgraded to lunar on 2023-11-23 (0 days ago)
  dmi.bios.date: 08/23/2021
  dmi.bios.release: 15.10
  dmi.bios.vendor: AMI
  dmi.bios.version: F.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 878A
  dmi.board.vendor: HP
  dmi.board.version: 17.29
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 17.29
  dmi.modalias: 
dmi:bvnAMI:bvrF.10:bd08/23/2021:br15.10:efr17.29:svnHP:pnOMENLaptop15-ek0xxx:pvr:rvnHP:rn878A:rvr17.29:cvnHP:ct10:cvrChassisVersion:sku2X0K2EA#ACB:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN Laptop 15-ek0xxx
  dmi.product.sku: 2X0K2EA#ACB
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2044412/+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 2045353] Re: package linux-modules-nvidia-525-6.2.0-1012-nvidia 6.2.0-1012.12 failed to install/upgrade: installed linux-modules-nvidia-525-6.2.0-1012-nvidia package post-instal

** Tags removed: need-duplicate-check

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

Title:
  package linux-modules-nvidia-525-6.2.0-1012-nvidia 6.2.0-1012.12
  failed to install/upgrade: installed linux-modules-
  nvidia-525-6.2.0-1012-nvidia package post-installation script
  subprocess returned error exit status 1

Status in linux-restricted-modules-nvidia-6.2 package in Ubuntu:
  New

Bug description:
  This issue actually started installing the nvidia 535 driver, it
  failed to install, and updated my kernel with a bad initramfs. I
  reverted back to nouveau and I purged all nvidia drivers now I'm
  trying to install the last known working driver on my system (525) and
  still having issues.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-modules-nvidia-525-6.2.0-1012-nvidia 6.2.0-1012.12
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Dec  1 14:02:13 2023
  ErrorMessage: installed linux-modules-nvidia-525-6.2.0-1012-nvidia package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-10-28 (33 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0
  SourcePackage: linux-restricted-modules-nvidia-6.2
  Title: package linux-modules-nvidia-525-6.2.0-1012-nvidia 6.2.0-1012.12 
failed to install/upgrade: installed linux-modules-nvidia-525-6.2.0-1012-nvidia 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-nvidia-6.2/+bug/2045353/+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 2046345] Re: package linux-modules-nvidia-535-6.5.0-9-generic 6.5.0-9.9 failed to install/upgrade: installed linux-modules-nvidia-535-6.5.0-9-generic package post-installation s

** Tags removed: need-duplicate-check

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

Title:
  package linux-modules-nvidia-535-6.5.0-9-generic 6.5.0-9.9 failed to
  install/upgrade: installed linux-modules-nvidia-535-6.5.0-9-generic
  package post-installation script subprocess returned error exit status
  1

Status in linux-restricted-modules package in Ubuntu:
  Confirmed

Bug description:
  Occurs when upgrading to an unreleased version
  Setting up linux-modules-nvidia-535-6.5.0-9-generic (6.5.0-9.9) ...
  linux-image-nvidia-6.5.0-9-generic: constructing .ko files
  make: arch/x86/Makefile.postlink: No such file or directory
  make: *** No rule to make target 'arch/x86/Makefile.postlink'.  Stop.
  make: arch/x86/Makefile.postlink: No such file or directory
  make: *** No rule to make target 'arch/x86/Makefile.postlink'.  Stop.
  make: arch/x86/Makefile.postlink: No such file or directory
  make: *** No rule to make target 'arch/x86/Makefile.postlink'.  Stop.
  make: arch/x86/Makefile.postlink: No such file or directory
  make: *** No rule to make target 'arch/x86/Makefile.postlink'.  Stop.
  make: arch/x86/Makefile.postlink: No such file or directory
  make: *** No rule to make target 'arch/x86/Makefile.postlink'.  Stop.
  nvidia-drm.ko: FAILED
  nvidia-modeset.ko: FAILED
  nvidia-peermem.ko: OK
  nvidia-uvm.ko: FAILED
  nvidia.ko: FAILED
  sha256sum: WARNING: 4 computed checksums did NOT match
  dpkg: error processing package linux-modules-nvidia-535-6.5.0-9-generic 
(--configure):
   installed linux-modules-nvidia-535-6.5.0-9-generic package post-installation 
script subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of 
linux-modules-nvidia-535-generic-hwe-22.04:
   linux-modules-nvidia-535-generic-hwe-22.04 depends on 
linux-modules-nvidia-535-6.5.0-9-generic (= 6.5.0-9.9); however:
Package linux-modules-nvidia-535-6.5.0-9-generic is not configured yet.

  dpkg: error processing package linux-modules-nvidia-535-generic-hwe-22.04 
(--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of 
linux-modules-nvidia-530-generic-hwe-22.04:
   linux-modules-nvidia-530-generic-hwe-22.04 depends on 
linux-modules-nvidia-535-generic-hwe-22.04; however:
Package linux-modules-nvidia-535-generic-hwe-22.04 is not configured yet.

  dpkg: error processing package linux-modules-nvidia-530-generic-hwe-22.04 
(--configure):
   dependency problems - leaving unconfigured
  Errors were encountered while processing:
   linux-modules-nvidia-535-6.5.0-9-generic
   linux-modules-nvidia-535-generic-hwe-22.04
   linux-modules-nvidia-530-generic-hwe-22.04

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: linux-modules-nvidia-535-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Dec 13 14:36:34 2023
  ErrorMessage: installed linux-modules-nvidia-535-6.5.0-9-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-02-17 (299 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5
  PythonDetails: /usr/bin/python3.11, Python 3.11.7, python-is-python3, 3.11.4-1
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.22.1ubuntu3
   apt  2.7.6
  SourcePackage: linux-restricted-modules
  Title: package linux-modules-nvidia-535-6.5.0-9-generic 6.5.0-9.9 failed to 
install/upgrade: installed linux-modules-nvidia-535-6.5.0-9-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to noble on 2023-12-13 (0 days ago)
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2046345/+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 2048504] Re: package linux-headers-6.2.0-39-generic 6.2.0-39.40 failed to install/upgrade: installed linux-headers-6.2.0-39-generic package post-installation script subprocess r

** Tags removed: need-duplicate-check

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

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

Status in linux package in Ubuntu:
  New

Bug description:
   fv

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-39-generic 6.2.0-39.40
  ProcVersionSignature: Ubuntu 6.2.0-36.37-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mdcir  2337 F pipewire
mdcir  2340 F wireplumber
   /dev/snd/seq:mdcir  2337 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Mon Jan  8 09:25:27 2024
  DpkgHistoryLog:
   Start-Date: 2024-01-08  09:25:26
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: thunderbird:amd64 (1:115.5.0+build1-0ubuntu0.23.04.1, 
1:115.6.0+build2-0ubuntu0.23.04.1), thunderbird-locale-en:amd64 
(1:115.5.0+build1-0ubuntu0.23.04.1, 1:115.6.0+build2-0ubuntu0.23.04.1), 
thunderbird-locale-zh-hant:amd64 (1:115.5.0+build1-0ubuntu0.23.04.1, 
1:115.6.0+build2-0ubuntu0.23.04.1), thunderbird-locale-en-gb:amd64 
(1:115.5.0+build1-0ubuntu0.23.04.1, 1:115.6.0+build2-0ubuntu0.23.04.1), 
thunderbird-locale-en-us:amd64 (1:115.5.0+build1-0ubuntu0.23.04.1, 
1:115.6.0+build2-0ubuntu0.23.04.1), thunderbird-gnome-support:amd64 
(1:115.5.0+build1-0ubuntu0.23.04.1, 1:115.6.0+build2-0ubuntu0.23.04.1)
  ErrorMessage: installed linux-headers-6.2.0-39-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-10-06 (93 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Dell Inc. XPS 15 9530
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic 
root=UUID=0a8a6779-7f01-4cb5-aa7b-2ba2d0ad4a06 ro quiet splash
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-6.2.0-39-generic 6.2.0-39.40 failed to 
install/upgrade: installed linux-headers-6.2.0-39-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2023
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 01WV13
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.4
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd09/19/2023:br1.8:efr1.4:svnDellInc.:pnXPS159530:pvr:rvnDellInc.:rn01WV13:rvrA00:cvnDellInc.:ct10:cvr:sku0BEB:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9530
  dmi.product.sku: 0BEB
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048504/+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 2049958] Re: package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/bluetooth/obexd' before installing new version: Input/output e

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

** Tags removed: need-duplicate-check

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

Title:
  package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to
  make backup link of './usr/lib/bluetooth/obexd' before installing new
  version: Input/output error

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  bug found during software update launched from bootable usb

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: bluez-obexd 5.68-0ubuntu1
  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
  CasperMD5CheckMismatches: ./casper/minimal.squashfs
  CasperMD5CheckResult: fail
  CasperVersion: 1.486
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  Date: Sat Jan 20 00:18:32 2024
  DuplicateSignature:
   package:bluez-obexd:5.68-0ubuntu1
   Unpacking bluez-obexd (5.68-0ubuntu1.1) over (5.68-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-MsVzUs/045-bluez-obexd_5.68-0ubuntu1.1_amd64.deb 
(--unpack):
unable to make backup link of './usr/lib/bluetooth/obexd' before installing 
new version: Input/output error
  ErrorMessage: unable to make backup link of './usr/lib/bluetooth/obexd' 
before installing new version: Input/output error
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz persistent 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: bluez
  Title: package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to 
make backup link of './usr/lib/bluetooth/obexd' before installing new version: 
Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2018
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 306
  dmi.board.asset.tag: Default string
  dmi.board.name: GL553VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr306:bd09/26/2018:br5.6:svnASUSTeKCOMPUTERINC.:pnGL553VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: GL
  dmi.product.name: GL553VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D0:57:7B:12:13:2F  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING 
RX bytes:1345 acl:0 sco:0 events:90 errors:0
TX bytes:3835 acl:0 sco:0 commands:90 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049958/+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 2038508] Re: package linux-image-6.2.0-34-generic 6.2.0-34.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-6.2.0-34-generic 6.2.0-34.34 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with
  return code 11

Status in dkms package in Ubuntu:
  Confirmed

Bug description:
  xxx

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-34-generic 6.2.0-34.34
  ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16
  Uname: Linux 6.2.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  willem 3916 F wireplumber
   /dev/snd/controlC1:  willem 3916 F wireplumber
   /dev/snd/seq:willem 3902 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Thu Oct  5 09:13:13 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  InstallationDate: Installed on 2022-10-21 (348 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: ASUSTeK COMPUTER INC. G752VM
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=9ff90b05-46f4-428b-adbd-875a3dc2cc0c ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: dkms
  Title: package linux-image-6.2.0-34-generic 6.2.0-34.34 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/24/2019
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VM.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VM.308:bd04/24/2019:br5.11:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: G
  dmi.product.name: G752VM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2038508/+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 2040081] Re: package firmware-b43-installer 1:019-8 failed to install/upgrade: installed firmware-b43-installer package post-installation script subprocess returned error exit s

** Tags removed: need-duplicate-check

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

Title:
  package firmware-b43-installer 1:019-8 failed to install/upgrade:
  installed firmware-b43-installer package post-installation script
  subprocess returned error exit status 1

Status in b43-fwcutter package in Ubuntu:
  Confirmed

Bug description:
  b43-installer failed while upgrading.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: firmware-b43-installer 1:019-8
  ProcVersionSignature: Ubuntu 5.19.0-42.43-generic 5.19.17
  Uname: Linux 5.19.0-42-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Oct 22 08:00:48 2023
  ErrorMessage: installed firmware-b43-installer package post-installation 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-10-21 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0
  SourcePackage: b43-fwcutter
  Title: package firmware-b43-installer 1:019-8 failed to install/upgrade: 
installed firmware-b43-installer package post-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-10-22 (0 days ago)
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/2040081/+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 2042661] Re: package linux-modules-nvidia-535-6.2.0-36-generic 6.2.0-36.37~22.04.1+1 failed to install/upgrade: installed linux-modules-nvidia-535-6.2.0-36-generic package post-

** Tags removed: need-duplicate-check

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

Title:
  package linux-modules-nvidia-535-6.2.0-36-generic
  6.2.0-36.37~22.04.1+1 failed to install/upgrade: installed linux-
  modules-nvidia-535-6.2.0-36-generic package post-installation script
  subprocess returned error exit status 1

Status in linux-restricted-modules-hwe-6.2 package in Ubuntu:
  New

Bug description:
  System update

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-nvidia-535-6.2.0-36-generic 6.2.0-36.37~22.04.1+1
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Nov  3 08:50:39 2023
  ErrorMessage: installed linux-modules-nvidia-535-6.2.0-36-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-10-06 (27 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.10
  SourcePackage: linux-restricted-modules-hwe-6.2
  Title: package linux-modules-nvidia-535-6.2.0-36-generic 
6.2.0-36.37~22.04.1+1 failed to install/upgrade: installed 
linux-modules-nvidia-535-6.2.0-36-generic package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-6.2/+bug/2042661/+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 2042078] Re: package linux-image-6.2.0-36-generic 6.2.0-36.37 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-6.2.0-36-generic 6.2.0-36.37 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with
  return code 11

Status in dkms package in Ubuntu:
  Confirmed

Bug description:
  during googling face this pop up and send the error.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-36-generic 6.2.0-36.37
  ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sunny  1644 F wireplumber
   /dev/snd/seq:sunny  1641 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Oct 31 13:33:10 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  InstallationDate: Installed on 2023-04-29 (184 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: ASUSTeK COMPUTER INC. X540UV
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=f083fc1e-8354-4bb4-b672-973d36f4def2 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: dkms
  Title: package linux-image-6.2.0-36-generic 6.2.0-36.37 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540UV.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540UV
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540UV.204:bd10/05/2017:br5.12:svnASUSTeKCOMPUTERINC.:pnX540UV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540UV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: X
  dmi.product.name: X540UV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2042078/+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 2042654] Re: package linux-image-5.15.0-84-generic (not installed) failed to install/upgrade: unable to open '/boot/vmlinuz-5.15.0-84-generic.dpkg-new': Operation not permitted

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-5.15.0-84-generic (not installed) failed to
  install/upgrade: unable to open '/boot/vmlinuz-5.15.0-84-generic.dpkg-
  new': Operation not permitted

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

Bug description:
  Not able to install updates of ubuntu system is getting slow

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-84-generic (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-83.92~20.04.1-generic 5.15.116
  Uname: Linux 5.15.0-83-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Nov  3 15:14:34 2023
  DpkgHistoryLog:
   Start-Date: 2023-11-03  15:13:01
   Commandline: apt-get install -f
   Requested-By: admin1 (1000)
   Install: linux-hwe-5.15-headers-5.15.0-88:amd64 (5.15.0-88.98~20.04.1, 
automatic), linux-modules-extra-5.15.0-88-generic:amd64 (5.15.0-88.98~20.04.1, 
automatic), linux-modules-5.15.0-88-generic:amd64 (5.15.0-88.98~20.04.1, 
automatic), linux-headers-5.15.0-88-generic:amd64 (5.15.0-88.98~20.04.1, 
automatic), linux-image-5.15.0-84-generic:amd64 (5.15.0-84.93~20.04.1, 
automatic), linux-image-5.15.0-86-generic:amd64 (5.15.0-86.96~20.04.1, 
automatic), linux-image-5.15.0-88-generic:amd64 (5.15.0-88.98~20.04.1, 
automatic)
   Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.15.0.86.96~20.04.44, 
5.15.0.88.98~20.04.46), linux-image-generic-hwe-20.04:amd64 
(5.15.0.86.96~20.04.44, 5.15.0.88.98~20.04.46), linux-generic-hwe-20.04:amd64 
(5.15.0.86.96~20.04.44, 5.15.0.88.98~20.04.46)
  DuplicateSignature:
   package:linux-image-5.15.0-84-generic:(not installed)
   Unpacking linux-image-5.15.0-84-generic (5.15.0-84.93~20.04.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-2gOGNH/8-linux-image-5.15.0-84-generic_5.15.0-84.93~20.04.1_amd64.deb
 (--unpack):
unable to open '/boot/vmlinuz-5.15.0-84-generic.dpkg-new': Operation not 
permitted
  ErrorMessage: unable to open '/boot/vmlinuz-5.15.0-84-generic.dpkg-new': 
Operation not permitted
  InstallationDate: Installed on 2023-09-12 (51 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.4
  SourcePackage: linux-signed-hwe-5.15
  Title: package linux-image-5.15.0-84-generic (not installed) failed to 
install/upgrade: unable to open '/boot/vmlinuz-5.15.0-84-generic.dpkg-new': 
Operation not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2042654/+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 2042707] Re: package nvidia-dkms-470 470.223.02-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-470 package post-installation script subprocess returned error

** Tags removed: need-duplicate-check

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

Title:
  package nvidia-dkms-470 470.223.02-0ubuntu0.22.04.1 failed to
  install/upgrade: installed nvidia-dkms-470 package post-installation
  script subprocess returned error exit status 10

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

Bug description:
  System reported an error and asked to submit a bug. Video resolution
  suddenly was stuck on 1024x768, after upgrade it restored back to
  1080p

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: nvidia-dkms-470 470.223.02-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126
  Uname: Linux 5.15.0-88-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Nov  2 21:58:28 2023
  ErrorMessage: installed nvidia-dkms-470 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2019-12-28 (1406 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.10
  SourcePackage: nvidia-graphics-drivers-470
  Title: package nvidia-dkms-470 470.223.02-0ubuntu0.22.04.1 failed to 
install/upgrade: installed nvidia-dkms-470 package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: Upgraded to jammy on 2022-06-25 (496 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2042707/+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 2049245] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exi

** Tags removed: need-duplicate-check

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

Title:
  package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to
  install/upgrade: installed nvidia-dkms-390 package post-installation
  script subprocess returned error exit status 10

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

Bug description:
  cannot select screen resolution other then 1024 X 768 after
  implementing the latest ubuntu update.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  AptOrdering:
   nvidia-kernel-source-390:amd64: Install
   nvidia-kernel-common-390:amd64: Install
   nvidia-dkms-390:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Jan 13 15:29:03 2024
  ErrorMessage: installed nvidia-dkms-390 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2023-05-04 (253 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: nvidia-graphics-drivers-390
  Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to 
install/upgrade: installed nvidia-dkms-390 package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049245/+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 2049688] Re: nvidia stoped working, , package nvidia-dkms-390 390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subp

** Tags removed: need-duplicate-check

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

Title:
  nvidia stoped working,, package nvidia-dkms-390
  390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed nvidia-
  dkms-390 package post-installation script subprocess returned error
  exit status 10

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

Bug description:
  after latest update on 22.04 nvidia driver stoped working, gpu not
  found, cannot reinstall, even after upgrade I get : package nvidia-
  dkms-390 390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed
  nvidia-dkms-390 package post-installation script subprocess returned
  error exit status 10.

  I also had errors with dependencies, when trying to reinstall and with
  kernel headers.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: nvidia-dkms-390 390.157-0ubuntu5.23.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Jan 17 22:54:39 2024
  ErrorMessage: installed nvidia-dkms-390 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2023-11-28 (50 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-390
  Title: package nvidia-dkms-390 390.157-0ubuntu5.23.04.1 failed to 
install/upgrade: installed nvidia-dkms-390 package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: Upgraded to lunar on 2024-01-17 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049688/+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 2049674] Re: package libnvidia-compute-390 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other

** Tags removed: need-duplicate-check

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

Title:
  package libnvidia-compute-390 (not installed) failed to
  install/upgrade: trying to overwrite shared
  '/etc/OpenCL/vendors/nvidia.icd', which is different from other
  instances of package libnvidia-compute-390:amd64

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

Bug description:
  I tried to switch from nouveau to nvdidia-390 (in Additional Drivers)
  and got the above error message.  The proprietary driver will not
  install.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libnvidia-compute-390 (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Jan 17 14:30:02 2024
  DuplicateSignature:
   package:libnvidia-compute-390:(not installed)
   Unpacking libnvidia-compute-390:amd64 (390.157-0ubuntu0.22.04.2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-QgW0Up/63-libnvidia-compute-390_390.157-0ubuntu0.22.04.2_amd64.deb
 (--unpack):
trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is 
different from other instances of package libnvidia-compute-390:amd64
  ErrorMessage: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', 
which is different from other instances of package libnvidia-compute-390:amd64
  InstallationDate: Installed on 2024-01-16 (1 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: nvidia-graphics-drivers-390
  Title: package libnvidia-compute-390 (not installed) failed to 
install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', 
which is different from other instances of package libnvidia-compute-390:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049674/+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 2039363] Re: package linux-modules-nvidia-535-6.2.0-34-generic 6.2.0-34.34~22.04.1+1 failed to install/upgrade: installed linux-modules-nvidia-535-6.2.0-34-generic package post-

** Tags removed: need-duplicate-check

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

Title:
  package linux-modules-nvidia-535-6.2.0-34-generic
  6.2.0-34.34~22.04.1+1 failed to install/upgrade: installed linux-
  modules-nvidia-535-6.2.0-34-generic package post-installation script
  subprocess returned error exit status 1

Status in linux-restricted-modules-hwe-6.2 package in Ubuntu:
  New

Bug description:
  I tried to change the repository and switched from kinetic to jammy
  jellyfish. Nearly everything worked there was a text saying, nivida
  driver was not up to date and then it occurred when i did the sudo
  ubunut-driver autoinstall command.

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: linux-modules-nvidia-535-6.2.0-34-generic 6.2.0-34.34~22.04.1+1
  ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3.2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Oct 14 18:41:41 2023
  ErrorMessage: installed linux-modules-nvidia-535-6.2.0-34-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-02-08 (247 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: linux-restricted-modules-hwe-6.2
  Title: package linux-modules-nvidia-535-6.2.0-34-generic 
6.2.0-34.34~22.04.1+1 failed to install/upgrade: installed 
linux-modules-nvidia-535-6.2.0-34-generic package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-6.2/+bug/2039363/+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 2043426] Re: package linux-modules-nvidia-470-5.15.0-82-generic (not installed) failed to install/upgrade: installed linux-modules-nvidia-470-5.15.0-82-generic package post-inst

** Tags removed: need-duplicate-check

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

Title:
  package linux-modules-nvidia-470-5.15.0-82-generic (not installed)
  failed to install/upgrade: installed linux-modules-
  nvidia-470-5.15.0-82-generic package post-installation script
  subprocess returned error exit status 1

Status in linux-restricted-modules package in Ubuntu:
  New

Bug description:
  I was upgrading from focal to jammy. This error appeared after a
  reboot. Thanks

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-nvidia-470-5.15.0-82-generic (not installed)
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Nov 13 13:37:50 2023
  ErrorMessage: installed linux-modules-nvidia-470-5.15.0-82-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2023-08-20 (85 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.10
  SourcePackage: linux-restricted-modules
  Title: package linux-modules-nvidia-470-5.15.0-82-generic (not installed) 
failed to install/upgrade: installed linux-modules-nvidia-470-5.15.0-82-generic 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2043426/+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 2039924] Re: package linux-image-6.2.0-35-generic 6.2.0-35.35 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-6.2.0-35-generic 6.2.0-35.35 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with
  return code 11

Status in dkms package in Ubuntu:
  Confirmed

Bug description:
  This error emerged when worked with Intellij

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-35-generic 6.2.0-35.35
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  andrew 2569 F wireplumber
   /dev/snd/controlC1:  andrew 2569 F wireplumber
   /dev/snd/controlC2:  andrew 2569 F wireplumber
   /dev/snd/seq:andrew 2565 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Fri Oct 20 10:24:34 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  InstallationDate: Installed on 2023-03-08 (225 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: Micro-Star International Co., Ltd. MS-7D28
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic 
root=UUID=8a4a53bf-0539-4847-80b7-e688eea77975 ro quiet nomodeset
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: dkms
  Title: package linux-image-6.2.0-35-generic 6.2.0-35.35 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/07/2022
  dmi.bios.release: 5.27
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.90
  dmi.board.asset.tag: Default string
  dmi.board.name: MEG Z690 UNIFY (MS-7D28)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.90:bd11/07/2022:br5.27:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D28:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMEGZ690UNIFY(MS-7D28):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7D28
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2039924/+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 2043449] Re: package zfs-dkms 2.1.5-1ubuntu6~22.04.1 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10

** Tags removed: need-duplicate-check

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

Title:
  package zfs-dkms 2.1.5-1ubuntu6~22.04.1 failed to install/upgrade:
  installed zfs-dkms package post-installation script subprocess
  returned error exit status 10

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  hedgemonkey@orangemonkey:~$ sudo apt-get install zfs-dkms
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Suggested packages:
debhelper
  Recommended packages:
zfs-zed zfsutils-linux
  The following packages will be REMOVED:
zfsutils-linux
  The following NEW packages will be installed:
zfs-dkms
  0 upgraded, 1 newly installed, 1 to remove and 3 not upgraded.
  Need to get 2,345 kB of archives.
  After this operation, 16.5 MB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Get:1 http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe arm64 
zfs-dkms all 2.1.5-1ubuntu6~22.04.1 [2,345 kB]
  Fetched 2,345 kB in 0s (21.2 MB/s) 
  Preconfiguring packages ...
  (Reading database ... 200773 files and directories currently installed.)
  Removing zfsutils-linux (2.1.6-0york1~22.04) ...
  Selecting previously unselected package zfs-dkms.
  (Reading database ... 200500 files and directories currently installed.)
  Preparing to unpack .../zfs-dkms_2.1.5-1ubuntu6~22.04.1_all.deb ...
  Unpacking zfs-dkms (2.1.5-1ubuntu6~22.04.1) ...
  Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.1) ...
  Loading new zfs-2.1.5 DKMS files...
  Building for 5.10.160-rockchip
  Building initial module for 5.10.160-rockchip
  configure: error: 
*** None of the expected "file_fallocate" interfaces were detected.
*** This may be because your kernel version is newer than what is
*** supported, or you are using a patched custom kernel with
*** incompatible modifications.
***
*** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.1
*** Compatible Kernels: 3.10 - 5.19

  ERROR (dkms apport): kernel package linux-headers-5.10.160-rockchip is not 
supported
  Error! Bad return status for module build on kernel: 5.10.160-rockchip 
(aarch64)
  Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information.
  dpkg: error processing package zfs-dkms (--configure):
   installed zfs-dkms package post-installation script subprocess returned 
error exit status 10
  Processing triggers for man-db (2.10.2-1) ...
  Processing triggers for initramfs-tools (0.140ubuntu13.4) ...
  update-initramfs: Generating /boot/initrd.img-5.10.160-rockchip
  flash-kernel: installing version 5.10.160-rockchip
  Errors were encountered while processing:
   zfs-dkms
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: zfs-dkms 2.1.5-1ubuntu6~22.04.1
  Uname: Linux 5.10.160-rockchip aarch64
  ApportVersion: 2.20.11-0ubuntu82.5
  AptOrdering:
   zfsutils-linux:arm64: Remove
   zfs-dkms:arm64: Install
   NULL: ConfigurePending
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Tue Nov 14 08:39:28 2023
  ErrorMessage: installed zfs-dkms package post-installation script subprocess 
returned error exit status 10
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.10
  SourcePackage: zfs-linux
  Title: package zfs-dkms 2.1.5-1ubuntu6~22.04.1 failed to install/upgrade: 
installed zfs-dkms package post-installation script subprocess returned error 
exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2043449/+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 2049958] [NEW] package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/bluetooth/obexd' before installing new version: Input/output

You have been subscribed to a public bug:

bug found during software update launched from bootable usb

ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: bluez-obexd 5.68-0ubuntu1
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
CasperMD5CheckMismatches: ./casper/minimal.squashfs
CasperMD5CheckResult: fail
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
Date: Sat Jan 20 00:18:32 2024
DuplicateSignature:
 package:bluez-obexd:5.68-0ubuntu1
 Unpacking bluez-obexd (5.68-0ubuntu1.1) over (5.68-0ubuntu1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-MsVzUs/045-bluez-obexd_5.68-0ubuntu1.1_amd64.deb 
(--unpack):
  unable to make backup link of './usr/lib/bluetooth/obexd' before installing 
new version: Input/output error
ErrorMessage: unable to make backup link of './usr/lib/bluetooth/obexd' before 
installing new version: Input/output error
InterestingModules: rfcomm bnep btusb bluetooth
LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz persistent 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.22.0ubuntu1
 apt  2.7.3
SourcePackage: bluez
Title: package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to 
make backup link of './usr/lib/bluetooth/obexd' before installing new version: 
Input/output error
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/26/2018
dmi.bios.release: 5.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 306
dmi.board.asset.tag: Default string
dmi.board.name: GL553VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No  Asset  Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr306:bd09/26/2018:br5.6:svnASUSTeKCOMPUTERINC.:pnGL553VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
dmi.product.family: GL
dmi.product.name: GL553VW
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: D0:57:7B:12:13:2F  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING 
RX bytes:1345 acl:0 sco:0 events:90 errors:0
TX bytes:3835 acl:0 sco:0 commands:90 errors:0

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


** Tags: amd64 apport-package mantic need-duplicate-check
-- 
package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to make 
backup link of './usr/lib/bluetooth/obexd' before installing new version: 
Input/output error
https://bugs.launchpad.net/bugs/2049958
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to bluez in Ubuntu.

-- 
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 2045483] Re: package linux-image-5.15.0-88-generic 5.15.0-88.98 failed to install/upgrade: installed linux-image-5.15.0-88-generic package pre-removal script subprocess returned

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-5.15.0-88-generic 5.15.0-88.98 failed to
  install/upgrade: installed linux-image-5.15.0-88-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  was trying to clan up the /boot

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-88-generic 5.15.0-88.98
  ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126
  Uname: Linux 5.15.0-88-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wboshinski   4285 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat Dec  2 19:31:31 2023
  ErrorMessage: installed linux-image-5.15.0-88-generic package pre-removal 
script subprocess returned error exit status 1
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2020-02-22 (1379 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 10d7:b012 Actions general adapter
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge T30
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-88-generic 
root=/dev/mapper/hostname--vg-root ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-5.15.0-88-generic 5.15.0-88.98 failed to 
install/upgrade: installed linux-image-5.15.0-88-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-08-23 (466 days ago)
  dmi.bios.date: 05/21/2019
  dmi.bios.release: 1.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 07T4MC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd05/21/2019:br1.1:svnDellInc.:pnPowerEdgeT30:pvr:rvnDellInc.:rn07T4MC:rvrA12:cvnDellInc.:ct6:cvr:sku07C5:
  dmi.product.name: PowerEdge T30
  dmi.product.sku: 07C5
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045483/+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 2045969] Re: package linux-image-6.2.0-39-generic 6.2.0-39.40 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-6.2.0-39-generic 6.2.0-39.40 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with
  return code 11

Status in linux-signed package in Ubuntu:
  New

Bug description:
  I don't kno why my computer is blocked just 15 s afeter start up

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-39-generic 6.2.0-39.40
  ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2.1
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Fri Dec  8 12:03:31 2023
  DpkgHistoryLog:
   Start-Date: 2023-12-08  12:03:21
   Commandline: /usr/bin/unattended-upgrade
   Install: linux-signatures-nvidia-6.2.0-39-generic:amd64 (6.2.0-39.40, 
automatic), linux-modules-6.2.0-39-generic:amd64 (6.2.0-39.40, automatic), 
linux-modules-nvidia-525-6.2.0-39-generic:amd64 (6.2.0-39.40, automatic), 
linux-image-6.2.0-39-generic:amd64 (6.2.0-39.40, automatic), 
linux-objects-nvidia-525-6.2.0-39-generic:amd64 (6.2.0-39.40, automatic)
   Upgrade: linux-modules-nvidia-525-generic-hwe-22.04:amd64 (6.2.0-37.38+1, 
6.2.0-39.40), linux-modules-nvidia-510-generic-hwe-22.04:amd64 (6.2.0-37.38+1, 
6.2.0-39.40), linux-libc-dev:amd64 (6.2.0-37.38, 6.2.0-39.40)
  ErrorMessage: installed linux-image-6.2.0-39-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2022-10-31 (403 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming A17 FA706ICB_TUF706ICB
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic 
root=UUID=8e316101-89cb-4820-a4b4-a076b22a5c2c ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux-signed
  Title: package linux-image-6.2.0-39-generic 6.2.0-39.40 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2022
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA706ICB.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FA706ICB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFA706ICB.304:bd04/11/2022:br5.16:efr3.2:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingA17FA706ICB_TUF706ICB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA706ICB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUS TUF Gaming A17
  dmi.product.name: ASUS TUF Gaming A17 FA706ICB_TUF706ICB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2045969/+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 2049086] Re: General upgrade to 22.04 leads to second monitor not being recognised package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 [modified: usr/src/nvidia-390.157/dkms.conf]

** Tags removed: need-duplicate-check

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

Title:
  General upgrade to 22.04 leads to second monitor not being recognised
  package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 [modified:
  usr/src/nvidia-390.157/dkms.conf] failed to install/upgrade: installed
  nvidia-dkms-390 package post-installation script subprocess returned
  error exit status 10

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

Bug description:
  Upgraded using sudo apt upgrade 
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  
  system fails to boot - blank screen - no activity

  recovery mode coaxed system to startup but error happens with nvidia
  drivers

  system has two monitors, one works (DVI) the second (VGA) does not.

  suspect ancient video card (geforce 610) and issues with compatibility

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 [modified: 
usr/src/nvidia-390.157/dkms.conf]
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  AptOrdering:
   nvidia-kernel-source-390:amd64: Install
   nvidia-kernel-common-390:amd64: Install
   nvidia-dkms-390:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jan 11 15:20:51 2024
  ErrorMessage: installed nvidia-dkms-390 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2022-07-30 (529 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python3, 3.9.2-2
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: nvidia-graphics-drivers-390
  Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 [modified: 
usr/src/nvidia-390.157/dkms.conf] failed to install/upgrade: installed 
nvidia-dkms-390 package post-installation script subprocess returned error exit 
status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049086/+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 2049666] Re: package linux-image-6.2.0-39-generic 6.2.0-39.40 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-6.2.0-39-generic 6.2.0-39.40 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with
  return code 11

Status in dkms package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-39-generic 6.2.0-39.40
  ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
  Uname: Linux 6.2.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  anil   1418 F wireplumber
   /dev/snd/controlC1:  anil   1418 F wireplumber
   /dev/snd/controlC0:  anil   1418 F wireplumber
   /dev/snd/seq:anil   1405 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Wed Jan 17 20:17:47 2024
  ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  InstallationDate: Installed on 2022-07-16 (549 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  IwConfig:
   lono wireless extensions.
   
   enp12s0   no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic 
root=UUID=7d0201f7-e7d8-4247-8f8c-d9bd80ffb976 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: dkms
  Title: package linux-image-6.2.0-39-generic 6.2.0-39.40 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  UpgradeStatus: Upgraded to lunar on 2023-07-15 (185 days ago)
  dmi.bios.date: 04/08/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX/GEN3 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/08/2014:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX/GEN3R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2049666/+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 2050098] Re: cgroup2 appears to be broken

I narrowed this down a bit further. Last working kernel version is
5.15.0-89-generic. The problem starts to show up with 5.15.0-90-generic.

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

Title:
  cgroup2 appears to be broken

Status in linux package in Ubuntu:
  New

Bug description:
  We're using Slurm workload manager in a cluster with Ubuntu 22.04 and
  the linux-generic kernel (amd64). We  use cgroups (cgroup2) for
  resource allocation with Slurm. With kernel version

  linux-image-5.15.0-91-generic 5.15.0-91.101
  amd64

  I'm seeing a new issue. This must have been introduces recently, I can
  confirm that with kernel 5.15.0-88-generic the issue does not exist.
  When I request a single GPU on a node with kernel 5.15.0-88-generic
  all is well:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  GPU 0: NVIDIA [...]

  
  Instead with kernel 5.15.0-91-generic:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  slurmstepd: error: load_ebpf_prog: BPF load error (No space left on device). 
Please check your system limits (MEMLOCK).
  GPU 0: NVIDIA [...]
  GPU 1: NVIDIA [...]
  GPU 2: NVIDIA [...]
  GPU 3: NVIDIA [...]
  GPU 4: NVIDIA [...]
  GPU 5: NVIDIA [...]
  GPU 6: NVIDIA [...]
  GPU 7: NVIDIA [...]

  So I get this error regarding MEMLOCK limit and see all GPUs in the
  system instead of only the one requested. Hence I assume the problem
  is related to cgroups.

  $ cat /proc/version_signature 
  Ubuntu 5.15.0-91.101-generic 5.15.131

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

2024-01-22 Thread Łukasz Zemczak

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

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

Title:
  systemd mount units fail during boot, while file system is correctly
  mounted

Status in systemd:
  New
Status in Ubuntu Pro:
  In Progress
Status in Ubuntu Pro 18.04 series:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in systemd source package in Bionic:
  Won't Fix
Status in linux source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  systemd mount units fail during boot, and the system boots into emergency mode

  [Test Plan]
  This issue seems to happen randomly, and doesn't seem related to a specific 
mount unit.

  We've used a test script with good results during investigation to
  reproduce similar mount failures in a running system, and have seen a
  strong correlation between the script failures and the boot time mount
  failures.

  The attached 'rep-tmpfs.sh' script should be used to validate that
  mount points are working correctly under stress. One can run through
  the different variants as below:

  # ./rep-tmpfs.sh --variant-0
  # ./rep-tmpfs.sh --variant-1
  # ./rep-tmpfs.sh --variant-2
  # ./rep-tmpfs.sh --variant-3
  # ./rep-tmpfs.sh --variant-4

  All of these should run successfully without any reported errors.

  [Where problems could occur]
  The patches change the way systemd tracks and handles mount points in 
general, so potential regressions could affect other mount units. We should 
keep an eye out for any issues with mounting file systems, as well as rapid 
mount/unmount operations. Successful test runs with the reproducer script 
should increase reliability in having no new regressions.

  [Other Info]
  This has been tackled upstream with several attempts, which have resulted in 
the final patch from 2022:
    01400460ae16 core/mount: adjust deserialized state based on 
/proc/self/mountinfo

  For Bionic, systemd requires several dependency patches as below:
    6a1d4d9fa6b9 core: properly reset all ExecStatus structures when entering a 
new unit cycle
    7eba1463dedc mount: flush out cycle state on DEAD→MOUNTED only, not the 
other way round
    350804867dbc mount: rescan /proc/self/mountinfo before processing waitid() 
results
    1d086a6e5972 mount: mark an existing "mounting" unit from 
/proc/self/mountinfo as "just_mounted"

  Additionally, the kernel also requires the following patches:
    28ca0d6d39ab list: introduce list_for_each_continue()
    9f6c61f96f2d proc/mounts: add cursor

  [Original Description]
  In Ubuntu 18.04 at least, we sometimes get a random server in emergency mode 
with a failed mount unit (ext4 file system), while the corresponding file 
system is in fact correctly mounted. It happens roughly once every 1000 reboots.

  It seems to be related with this bug :
  https://github.com/systemd/systemd/issues/10872

  Is it possible to apply the fix
  
(https://github.com/systemd/systemd/commit/350804867dbcc9b7ccabae1187d730d37e2d8a21)
  in Ubuntu 18.04 ?

  Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1837227/+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 1837227] Re: systemd mount units fail during boot, while file system is correctly mounted

This bug was fixed in the package systemd - 245.4-4ubuntu3.23

---
systemd (245.4-4ubuntu3.23) focal; urgency=medium

  [ Nick Rosbrook ]
  * core/device: ignore DEVICE_FOUND_UDEV bit on switching root (LP: #2037281)
File: 
debian/patches/lp2037281-core-device-ignore-DEVICE_FOUND_UDEV-bit-on-switching-roo.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7793563bb38a84a3dc6bc0da1c08546c3b915ab8
  * dns-query: bump CNAME_MAX to 16 (LP: #2024009)
File: debian/patches/lp2024009-dns-query-bump-CNAME_MAX-to-16.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=193899d103d44c642d362e9916b14df844ec702f
  * Fall back to kexec when no kexec binary exists (LP: #1969365)
File: 
debian/patches/lp1969365-Fall-back-to-kexec-when-no-kexec-binary-exists.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3934f3794427dee4e72824998dd4c6e6d5875289
  * test: ignore LXC filesystem when checking for writable locations (LP: 
#2029352)
File: 
debian/patches/lp2029352-test-ignore-LXC-filesystem-when-checking-for-writable-loc.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=70facbfbf54c4ffb31ba392dbe3fec3084fdf3bc

  [ Heitor Alves de Siqueira ]
  * core/mount: adjust deserialized state based on /proc/self/mountinfo (LP: 
#1837227)
Author: Heitor Alves de Siqueira
File: 
debian/patches/lp1837227-core-mount-adjust-deserialized-state-based-on-proc-self-m.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a0a749953d309f48bc45140102adf205d1071c4d

 -- Nick Rosbrook   Tue, 21 Nov 2023 16:10:21 -0500

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

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

Title:
  systemd mount units fail during boot, while file system is correctly
  mounted

Status in systemd:
  New
Status in Ubuntu Pro:
  In Progress
Status in Ubuntu Pro 18.04 series:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in systemd source package in Bionic:
  Won't Fix
Status in linux source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  systemd mount units fail during boot, and the system boots into emergency mode

  [Test Plan]
  This issue seems to happen randomly, and doesn't seem related to a specific 
mount unit.

  We've used a test script with good results during investigation to
  reproduce similar mount failures in a running system, and have seen a
  strong correlation between the script failures and the boot time mount
  failures.

  The attached 'rep-tmpfs.sh' script should be used to validate that
  mount points are working correctly under stress. One can run through
  the different variants as below:

  # ./rep-tmpfs.sh --variant-0
  # ./rep-tmpfs.sh --variant-1
  # ./rep-tmpfs.sh --variant-2
  # ./rep-tmpfs.sh --variant-3
  # ./rep-tmpfs.sh --variant-4

  All of these should run successfully without any reported errors.

  [Where problems could occur]
  The patches change the way systemd tracks and handles mount points in 
general, so potential regressions could affect other mount units. We should 
keep an eye out for any issues with mounting file systems, as well as rapid 
mount/unmount operations. Successful test runs with the reproducer script 
should increase reliability in having no new regressions.

  [Other Info]
  This has been tackled upstream with several attempts, which have resulted in 
the final patch from 2022:
    01400460ae16 core/mount: adjust deserialized state based on 
/proc/self/mountinfo

  For Bionic, systemd requires several dependency patches as below:
    6a1d4d9fa6b9 core: properly reset all ExecStatus structures when entering a 
new unit cycle
    7eba1463dedc mount: flush out cycle state on DEAD→MOUNTED only, not the 
other way round
    350804867dbc mount: rescan /proc/self/mountinfo before processing waitid() 
results
    1d086a6e5972 mount: mark an existing "mounting" unit from 
/proc/self/mountinfo as "just_mounted"

  Additionally, the kernel also requires the following patches:
    28ca0d6d39ab list: introduce list_for_each_continue()
    9f6c61f96f2d proc/mounts: add cursor

  [Original Description]
  In Ubuntu 18.04 at least, we sometimes get a random server in emergency mode 
with a failed mount unit (ext4 file system), while the corresponding file 
system is in fact correctly mounted. It happens roughly once every 1000 reboots.

  It seems to be related with this bug :

[Kernel-packages] [Bug 2050103] Re: Integrated Laptop screen not detected on 6.5 hwe - Intel UHD 630 Coffee Lake

2024-01-22 Thread Nick White

Added Package

** Package changed: ubuntu => linux-hwe-6.5 (Ubuntu)

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

Title:
  Integrated Laptop screen not detected on 6.5 hwe - Intel UHD 630
  Coffee Lake

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

Bug description:
  lsb_release
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04
  Codename: jammy

  Laptop: Rebadged Clevo
  Graphics: on-board Intel UHD 630 

  Updated from kernel 6.2.0-39-generic to 6.5.0-14-generic

  Problem:- LCD laptop screen not detected on kernel 6.5.0-14

  The laptop LCD screen is black but the external RGB monitor works
  fine. Using kernel 6.2.0-39, both the LCD and external monitor work.

  inxi -Gxx  on 6.2 kernel shows 2 Monitors - DP-1 is the external and eDP-1 is 
the LCD
  Graphics:
Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: CLEVO/KAPOK
  driver: i915 v: kernel ports: active: DP-1,eDP-1 empty: HDMI-A-1,HDMI-A-2
  bus-ID: 00:02.0 chip-ID: 8086:3e9b
Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 1-8:4
  chip-ID: 5986:2110
Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.1
  compositor: gnome-shell v: 42.9 driver: X: loaded: vesa
  unloaded: fbdev,modesetting gpu: i915 display-ID: 0
Monitor-1: DP-1 model: Vw19B2 res: 1440x900 dpi: 89 diag: 483mm (19")
Monitor-2: eDP-1 model: LG res: 1920x1080 dpi: 128 diag: 438mm (17.3")
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
  v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes

  inxi -Gxx  on 6.5 kernel shows 1 Monitor - DP-1 is the external
  Graphics:
Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: CLEVO/KAPOK
  driver: i915 v: kernel ports: active: DP-1 empty: HDMI-A-1,HDMI-A-2
  bus-ID: 00:02.0 chip-ID: 8086:3e9b
Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 1-8:4
  chip-ID: 5986:2110
Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.1
  compositor: gnome-shell v: 42.9 driver: X: loaded: vesa
  unloaded: fbdev,modesetting gpu: i915 display-ID: 0
Monitor-1: DP-1 model: Vw19B2 res: 1440x900 dpi: 89 diag: 483mm (19")
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
  v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes

  This line using journalctl is in the boot log of kernel 6.2 but not in the 
boot log of 6.5(probably not relevant)
  Jan 14 15:27:20 hybris kernel: i915 :00:02.0: [drm] Skipping 
intel_backlight registration

  Have noticed Bug:- https://answers.launchpad.net/bugs/2049245 which is
  against nvidia graphics but will try 1024x768 resolution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2050103/+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 2050098] Re: cgroup2 appears to be broken

Seems like the problem occurs here

```
[2024-01-22T17:13:16.819] [63786.0] cgroup/v2: cgroup_p_constrain_apply: 
CGROUP: EBPF Closing and loading bpf program into 
/sys/fs/cgroup/system.slice/slurmstepd.scope/job_63786/step_0/user
[2024-01-22T17:13:16.819] [63786.0] error: load_ebpf_prog: BPF load error (No 
space left on device). Please check your system limits (MEMLOCK).
```

Either Slurm is doing things in a wrong way (and that wrong way was
working until now) or the changes in the kernel between -89 to -91
actually broke something.

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

Title:
  cgroup2 appears to be broken

Status in linux package in Ubuntu:
  New

Bug description:
  We're using Slurm workload manager in a cluster with Ubuntu 22.04 and
  the linux-generic kernel (amd64). We  use cgroups (cgroup2) for
  resource allocation with Slurm. With kernel version

  linux-image-5.15.0-91-generic 5.15.0-91.101
  amd64

  I'm seeing a new issue. This must have been introduces recently, I can
  confirm that with kernel 5.15.0-88-generic the issue does not exist.
  When I request a single GPU on a node with kernel 5.15.0-88-generic
  all is well:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  GPU 0: NVIDIA [...]

  
  Instead with kernel 5.15.0-91-generic:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  slurmstepd: error: load_ebpf_prog: BPF load error (No space left on device). 
Please check your system limits (MEMLOCK).
  GPU 0: NVIDIA [...]
  GPU 1: NVIDIA [...]
  GPU 2: NVIDIA [...]
  GPU 3: NVIDIA [...]
  GPU 4: NVIDIA [...]
  GPU 5: NVIDIA [...]
  GPU 6: NVIDIA [...]
  GPU 7: NVIDIA [...]

  So I get this error regarding MEMLOCK limit and see all GPUs in the
  system instead of only the one requested. Hence I assume the problem
  is related to cgroups.

  $ cat /proc/version_signature 
  Ubuntu 5.15.0-91.101-generic 5.15.131

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2050098/+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 2050098] Re: cgroup2 appears to be broken

I just noticed that 5.15.0-94.104 is available in jammy-proposed and
tested that. Same problem as with -91

I've enabled debug messages for slurmd with regards to cgroup, log
attached.

** Attachment added: "Slurmd cgroup debug log"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2050098/+attachment/5741437/+files/slurmd_cgroup_log.txt

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

Title:
cgroup2 appears to be broken

Status in linux package in Ubuntu:
New

Bug description:
We're using Slurm workload manager in a cluster with Ubuntu 22.04 and
the linux-generic kernel (amd64). We use cgroups (cgroup2) for
resource allocation with Slurm. With kernel version

linux-image-5.15.0-91-generic 5.15.0-91.101
amd64

I'm seeing a new issue. This must have been introduces recently, I can
confirm that with kernel 5.15.0-88-generic the issue does not exist.
When I request a single GPU on a node with kernel 5.15.0-88-generic
all is well:

$ srun -G 1 -w gpu59 nvidia-smi -L
GPU 0: NVIDIA [...]

Instead with kernel 5.15.0-91-generic:

$ srun -G 1 -w gpu59 nvidia-smi -L
slurmstepd: error: load_ebpf_prog: BPF load error (No space left on device).
Please check your system limits (MEMLOCK).
GPU 0: NVIDIA [...]
GPU 1: NVIDIA [...]
GPU 2: NVIDIA [...]
GPU 3: NVIDIA [...]
GPU 4: NVIDIA [...]
GPU 5: NVIDIA [...]
GPU 6: NVIDIA [...]
GPU 7: NVIDIA [...]

So I get this error regarding MEMLOCK limit and see all GPUs in the
system instead of only the one requested. Hence I assume the problem
is related to cgroups.

$ cat /proc/version_signature
Ubuntu 5.15.0-91.101-generic 5.15.131

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2050098/+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 2049922] Re: PCI ATS quirk patch needed for IDPF

2024-01-22 Thread Joseph Salisbury

The requested commit (a18615b1cfc0) has the following prerequisite
commit:

f18b1137d38c ("PCI: Extract ATS disabling to a helper function")

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

Title:
  PCI ATS quirk patch needed for IDPF

Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Bionic:
  New
Status in linux-gcp source package in Focal:
  New

Bug description:
  [Impact]

  * Request from Google to include Intel patches for IDPF support if used from 
out-of-tree module to
prevent system instability

  [Fix]

  * Upstream
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.7=a18615b1cfc04f00548c60eb9a77e0ce56e848fd

  [Test Case]

  * Compile test
  * Boot test
  * Test on non-IDPF instance

  [Where things could go wrong]

  * Low chance of regression, changes very isolated

  [Other Info]

  * SF #00376470

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2049922/+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 2050103] [NEW] Integrated Laptop screen not detected on 6.5 hwe - Intel UHD 630 Coffee Lake

You have been subscribed to a public bug:

lsb_release
Description:Ubuntu 22.04.3 LTS
Release:22.04
Codename:   jammy

Laptop: Rebadged Clevo
Graphics: on-board Intel UHD 630 

Updated from kernel 6.2.0-39-generic to 6.5.0-14-generic

Problem:- LCD laptop screen not detected on kernel 6.5.0-14

The laptop LCD screen is black but the external RGB monitor works fine.
Using kernel 6.2.0-39, both the LCD and external monitor work.

inxi -Gxx  on 6.2 kernel shows 2 Monitors - DP-1 is the external and eDP-1 is 
the LCD
Graphics:
  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: CLEVO/KAPOK
driver: i915 v: kernel ports: active: DP-1,eDP-1 empty: HDMI-A-1,HDMI-A-2
bus-ID: 00:02.0 chip-ID: 8086:3e9b
  Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 1-8:4
chip-ID: 5986:2110
  Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.1
compositor: gnome-shell v: 42.9 driver: X: loaded: vesa
unloaded: fbdev,modesetting gpu: i915 display-ID: 0
  Monitor-1: DP-1 model: Vw19B2 res: 1440x900 dpi: 89 diag: 483mm (19")
  Monitor-2: eDP-1 model: LG res: 1920x1080 dpi: 128 diag: 438mm (17.3")
  OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes

inxi -Gxx  on 6.5 kernel shows 1 Monitor - DP-1 is the external
Graphics:
  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: CLEVO/KAPOK
driver: i915 v: kernel ports: active: DP-1 empty: HDMI-A-1,HDMI-A-2
bus-ID: 00:02.0 chip-ID: 8086:3e9b
  Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 1-8:4
chip-ID: 5986:2110
  Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.1
compositor: gnome-shell v: 42.9 driver: X: loaded: vesa
unloaded: fbdev,modesetting gpu: i915 display-ID: 0
  Monitor-1: DP-1 model: Vw19B2 res: 1440x900 dpi: 89 diag: 483mm (19")
  OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes

This line using journalctl is in the boot log of kernel 6.2 but not in the boot 
log of 6.5(probably not relevant)
Jan 14 15:27:20 hybris kernel: i915 :00:02.0: [drm] Skipping 
intel_backlight registration

Have noticed Bug:- https://answers.launchpad.net/bugs/2049245 which is
against nvidia graphics but will try 1024x768 resolution.

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


** Tags: bot-comment
-- 
Integrated Laptop screen not detected on 6.5 hwe - Intel UHD 630 Coffee Lake
https://bugs.launchpad.net/bugs/2050103
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-hwe-6.5 in Ubuntu.

-- 
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 1959113] Re: missing built-in disk encryption at install time

2024-01-22 Thread Dave Jones

rpi-imager currently has no facility to encrypt the image it flashes to
the storage on the Pi (and making such a facility generic enough that it
would fit all potentially interested distros is a daunting task to say
the least), so this isn't valid for rpi-imager.

I *did* add some initial steps towards this in the lunar desktop images,
which preserve space at the end of the root partition for LUKS headers
(by ensuring the root file-system doesn't expand *all* the way to the
partition size) which should make this easier to achieve in future, but
there's still plenty of work to be done here.

** Changed in: rpi-imager (Ubuntu)
   Status: New => Invalid

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

Title:
  missing built-in disk encryption at install time

Status in Ubuntu:
  New
Status in linux-firmware-raspi package in Ubuntu:
  New
Status in linux-raspi package in Ubuntu:
  New
Status in rpi-imager package in Ubuntu:
  Invalid

Bug description:
  Is there a simple way to install Ubuntu on SD card for Raspberry Pi4
  with full disk encryption?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1959113/+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 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

2024-01-22 Thread Lukas Märdian

We talked to our systemd maintainer inside foundations and also reached
out to upstream system [1], which didn't lead anywhere. We shouldn't
need to bisect systemd-networkd and do a high impact systemd SRU to fix
a regression in a kernel update, where we can pinpoint the exact (small)
git commit.

We'd like to ask to have the kernel commit b0ad3c179059 reverted in the
Jammy kernels, to mitigate this regression.


[1] 
https://lists.freedesktop.org/archives/systemd-devel/2023-November/049693.html

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

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

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 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: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+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 2048901] Re: Update the NVIDIA ERD 535 series to 535.154.05

** Changed in: fabric-manager-535 (Ubuntu Bionic)
   Status: New => Fix Released

** Changed in: libnvidia-nscq-535 (Ubuntu Bionic)
   Status: New => Fix Released

** Changed in: nvidia-graphics-drivers-535 (Ubuntu Bionic)
   Status: New => Fix Released

** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Bionic)
   Status: New => Fix Released

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

Title:
  Update the NVIDIA ERD 535 series to 535.154.05

Status in fabric-manager-535 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Fix Committed
Status in fabric-manager-535 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-535 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Bionic:
  Fix Released
Status in fabric-manager-535 source package in Focal:
  Fix Released
Status in libnvidia-nscq-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in fabric-manager-535 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in fabric-manager-535 source package in Mantic:
  Fix Released
Status in libnvidia-nscq-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Mantic:
  Fix Released
Status in fabric-manager-535 source package in Noble:
  Fix Released
Status in libnvidia-nscq-535 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  Fix Committed
Status in nvidia-graphics-drivers-535-server source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2048901/+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 2048901] Re: Update the NVIDIA ERD 535 series to 535.154.05

This bug was fixed in the package libnvidia-nscq-535 -
535.154.05-0ubuntu0.22.04.1

---
libnvidia-nscq-535 (535.154.05-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #2048901)
  * Make orig tarballs reproducible

 -- Dimitri John Ledkov   Thu, 11 Jan 2024
12:20:05 +

** Changed in: libnvidia-nscq-535 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Update the NVIDIA ERD 535 series to 535.154.05

Status in fabric-manager-535 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Fix Committed
Status in fabric-manager-535 source package in Bionic:
  New
Status in libnvidia-nscq-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535-server source package in Bionic:
  New
Status in fabric-manager-535 source package in Focal:
  Fix Released
Status in libnvidia-nscq-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in fabric-manager-535 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in fabric-manager-535 source package in Mantic:
  Fix Released
Status in libnvidia-nscq-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Mantic:
  Fix Released
Status in fabric-manager-535 source package in Noble:
  Fix Released
Status in libnvidia-nscq-535 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  Fix Committed
Status in nvidia-graphics-drivers-535-server source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2048901/+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 2049930] Re: mlxbf_gige: disable RX_DMA during NAPI poll

2024-01-22 Thread Bartlomiej Zolnierkiewicz

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

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

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

Title:
  mlxbf_gige: disable RX_DMA during NAPI poll

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

Bug description:
  SRU Justification:

  [Impact]

  A regression has been introduced in the latest 22.04 kernel by including
  the following two commits:
 revert "UBUNTU: SAUCE: Fix OOB handling RX packets in heavy traffic"
 addition of upstream "mlxbf_gige: fix receive packet race condition"
  The regression will manifest as connectivity problems on "oob_net0" interface

  [Fix]

  Modify the GIGE driver to include the RX_DMA disable logic in its NAPI poll 
routine
  This logic was part of "UBUNTU: SAUCE: Fix OOB handling RX packets in heavy 
traffic"
  but not part of upstream "mlxbf_gige: fix receive packet race condition"

  [Test Case]

  Boot BF3 platform and ensure oob_net0 interface is up and has IP address
  Bring up many IP interfaces, including oob_net0, and make sure OOB interface
  is continually accessible (e.g. via ping)

  [Regression Potential]

  Low risk change, adding back in prior logic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2049930/+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 2048901] Re: Update the NVIDIA ERD 535 series to 535.154.05

This bug was fixed in the package fabric-manager-535 -
535.154.05-0ubuntu0.23.10.1

---
fabric-manager-535 (535.154.05-0ubuntu0.23.10.1) mantic; urgency=medium

  * New upstream release (LP: #2048901)
  * Make orig tarballs reproducible

 -- Dimitri John Ledkov   Wed, 10 Jan 2024
16:55:17 +

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

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

Title:
  Update the NVIDIA ERD 535 series to 535.154.05

Status in fabric-manager-535 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Fix Committed
Status in fabric-manager-535 source package in Bionic:
  New
Status in libnvidia-nscq-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535-server source package in Bionic:
  New
Status in fabric-manager-535 source package in Focal:
  Fix Released
Status in libnvidia-nscq-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in fabric-manager-535 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-535 source package in Jammy:
  Fix Committed
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in fabric-manager-535 source package in Mantic:
  Fix Released
Status in libnvidia-nscq-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Mantic:
  Fix Released
Status in fabric-manager-535 source package in Noble:
  Fix Released
Status in libnvidia-nscq-535 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  Fix Committed
Status in nvidia-graphics-drivers-535-server source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2048901/+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 2048901] Re: Update the NVIDIA ERD 535 series to 535.154.05

This bug was fixed in the package libnvidia-nscq-535 -
535.154.05-0ubuntu0.23.10.1

---
libnvidia-nscq-535 (535.154.05-0ubuntu0.23.10.1) mantic; urgency=medium

  * New upstream release (LP: #2048901)
  * Make orig tarballs reproducible

 -- Dimitri John Ledkov   Thu, 11 Jan 2024
12:20:19 +

** Changed in: fabric-manager-535 (Ubuntu Mantic)
   Status: Fix Committed => Fix Released

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

Title:
  Update the NVIDIA ERD 535 series to 535.154.05

Status in fabric-manager-535 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Fix Committed
Status in fabric-manager-535 source package in Bionic:
  New
Status in libnvidia-nscq-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535-server source package in Bionic:
  New
Status in fabric-manager-535 source package in Focal:
  Fix Released
Status in libnvidia-nscq-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in fabric-manager-535 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-535 source package in Jammy:
  Fix Committed
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in fabric-manager-535 source package in Mantic:
  Fix Released
Status in libnvidia-nscq-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Mantic:
  Fix Released
Status in fabric-manager-535 source package in Noble:
  Fix Released
Status in libnvidia-nscq-535 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  Fix Committed
Status in nvidia-graphics-drivers-535-server source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2048901/+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 2048901] Re: Update the NVIDIA ERD 535 series to 535.154.05

This bug was fixed in the package nvidia-graphics-drivers-535 -
535.154.05-0ubuntu0.23.10.1

---
nvidia-graphics-drivers-535 (535.154.05-0ubuntu0.23.10.1) mantic; urgency=medium

  * New upstream release (LP: #2048901)
  * Make orig tarballs reproducible

 -- Dimitri John Ledkov   Mon, 15 Jan 2024
15:52:03 +

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

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

Title:
  Update the NVIDIA ERD 535 series to 535.154.05

Status in fabric-manager-535 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Fix Committed
Status in fabric-manager-535 source package in Bionic:
  New
Status in libnvidia-nscq-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535-server source package in Bionic:
  New
Status in fabric-manager-535 source package in Focal:
  Fix Released
Status in libnvidia-nscq-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in fabric-manager-535 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-535 source package in Jammy:
  Fix Committed
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in fabric-manager-535 source package in Mantic:
  Fix Released
Status in libnvidia-nscq-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Mantic:
  Fix Released
Status in fabric-manager-535 source package in Noble:
  Fix Released
Status in libnvidia-nscq-535 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  Fix Committed
Status in nvidia-graphics-drivers-535-server source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2048901/+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 2048901] Re: Update the NVIDIA ERD 535 series to 535.154.05

This bug was fixed in the package nvidia-graphics-drivers-535-server -
535.154.05-0ubuntu0.22.04.1

---
nvidia-graphics-drivers-535-server (535.154.05-0ubuntu0.22.04.1) jammy; 
urgency=medium

  * New upstream release (LP: #2048901)
  * Make orig tarballs reproducible

 -- Dimitri John Ledkov   Wed, 10 Jan 2024
16:17:36 +

** Changed in: libnvidia-nscq-535 (Ubuntu Mantic)
   Status: Fix Committed => Fix Released

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

Title:
  Update the NVIDIA ERD 535 series to 535.154.05

Status in fabric-manager-535 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Fix Committed
Status in fabric-manager-535 source package in Bionic:
  New
Status in libnvidia-nscq-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535-server source package in Bionic:
  New
Status in fabric-manager-535 source package in Focal:
  Fix Released
Status in libnvidia-nscq-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in fabric-manager-535 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-535 source package in Jammy:
  Fix Committed
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in fabric-manager-535 source package in Mantic:
  Fix Released
Status in libnvidia-nscq-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Mantic:
  Fix Released
Status in fabric-manager-535 source package in Noble:
  Fix Released
Status in libnvidia-nscq-535 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  Fix Committed
Status in nvidia-graphics-drivers-535-server source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2048901/+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 2048901] Re: Update the NVIDIA ERD 535 series to 535.154.05

This bug was fixed in the package nvidia-graphics-drivers-535 -
535.154.05-0ubuntu0.22.04.1

---
nvidia-graphics-drivers-535 (535.154.05-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #2048901)
  * Make orig tarballs reproducible

 -- Dimitri John Ledkov   Mon, 15 Jan 2024
15:53:54 +

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

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

Title:
  Update the NVIDIA ERD 535 series to 535.154.05

Status in fabric-manager-535 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Fix Committed
Status in fabric-manager-535 source package in Bionic:
  New
Status in libnvidia-nscq-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535-server source package in Bionic:
  New
Status in fabric-manager-535 source package in Focal:
  Fix Released
Status in libnvidia-nscq-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in fabric-manager-535 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-535 source package in Jammy:
  Fix Committed
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in fabric-manager-535 source package in Mantic:
  Fix Released
Status in libnvidia-nscq-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Mantic:
  Fix Released
Status in fabric-manager-535 source package in Noble:
  Fix Released
Status in libnvidia-nscq-535 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  Fix Committed
Status in nvidia-graphics-drivers-535-server source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2048901/+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 2048901] Re: Update the NVIDIA ERD 535 series to 535.154.05

This bug was fixed in the package nvidia-graphics-drivers-535-server -
535.154.05-0ubuntu0.20.04.1

---
nvidia-graphics-drivers-535-server (535.154.05-0ubuntu0.20.04.1) focal; 
urgency=medium

  * New upstream release (LP: #2048901)
  * Make orig tarballs reproducible

 -- Dimitri John Ledkov   Wed, 10 Jan 2024
16:22:49 +

** Changed in: fabric-manager-535 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Update the NVIDIA ERD 535 series to 535.154.05

Status in fabric-manager-535 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Fix Committed
Status in fabric-manager-535 source package in Bionic:
  New
Status in libnvidia-nscq-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535-server source package in Bionic:
  New
Status in fabric-manager-535 source package in Focal:
  Fix Released
Status in libnvidia-nscq-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in fabric-manager-535 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-535 source package in Jammy:
  Fix Committed
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in fabric-manager-535 source package in Mantic:
  Fix Released
Status in libnvidia-nscq-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Mantic:
  Fix Released
Status in fabric-manager-535 source package in Noble:
  Fix Released
Status in libnvidia-nscq-535 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  Fix Committed
Status in nvidia-graphics-drivers-535-server source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2048901/+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 2048901] Re: Update the NVIDIA ERD 535 series to 535.154.05

This bug was fixed in the package fabric-manager-535 -
535.154.05-0ubuntu0.22.04.1

---
fabric-manager-535 (535.154.05-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #2048901)
  * Make orig tarballs reproducible

 -- Dimitri John Ledkov   Wed, 10 Jan 2024
16:55:48 +

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

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

Title:
  Update the NVIDIA ERD 535 series to 535.154.05

Status in fabric-manager-535 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Fix Committed
Status in fabric-manager-535 source package in Bionic:
  New
Status in libnvidia-nscq-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535-server source package in Bionic:
  New
Status in fabric-manager-535 source package in Focal:
  Fix Released
Status in libnvidia-nscq-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in fabric-manager-535 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-535 source package in Jammy:
  Fix Committed
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in fabric-manager-535 source package in Mantic:
  Fix Released
Status in libnvidia-nscq-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Mantic:
  Fix Released
Status in fabric-manager-535 source package in Noble:
  Fix Released
Status in libnvidia-nscq-535 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  Fix Committed
Status in nvidia-graphics-drivers-535-server source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2048901/+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 2048901] Re: Update the NVIDIA ERD 535 series to 535.154.05

This bug was fixed in the package nvidia-graphics-drivers-535 -
535.154.05-0ubuntu0.20.04.1

---
nvidia-graphics-drivers-535 (535.154.05-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #2048901)
  * Make orig tarballs reproducible

 -- Dimitri John Ledkov   Mon, 15 Jan 2024
15:54:07 +

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

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

Title:
  Update the NVIDIA ERD 535 series to 535.154.05

Status in fabric-manager-535 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Fix Committed
Status in fabric-manager-535 source package in Bionic:
  New
Status in libnvidia-nscq-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535-server source package in Bionic:
  New
Status in fabric-manager-535 source package in Focal:
  Fix Released
Status in libnvidia-nscq-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in fabric-manager-535 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-535 source package in Jammy:
  Fix Committed
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in fabric-manager-535 source package in Mantic:
  Fix Released
Status in libnvidia-nscq-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Mantic:
  Fix Released
Status in fabric-manager-535 source package in Noble:
  Fix Released
Status in libnvidia-nscq-535 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  Fix Committed
Status in nvidia-graphics-drivers-535-server source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2048901/+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 2048901] Re: Update the NVIDIA ERD 535 series to 535.154.05

This bug was fixed in the package fabric-manager-535 -
535.154.05-0ubuntu0.20.04.1

---
fabric-manager-535 (535.154.05-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #2048901)
  * Make orig tarballs reproducible

 -- Dimitri John Ledkov   Wed, 10 Jan 2024
16:56:04 +

** Changed in: fabric-manager-535 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

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

Title:
  Update the NVIDIA ERD 535 series to 535.154.05

Status in fabric-manager-535 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Fix Committed
Status in fabric-manager-535 source package in Bionic:
  New
Status in libnvidia-nscq-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535-server source package in Bionic:
  New
Status in fabric-manager-535 source package in Focal:
  Fix Released
Status in libnvidia-nscq-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in fabric-manager-535 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-535 source package in Jammy:
  Fix Committed
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in fabric-manager-535 source package in Mantic:
  Fix Released
Status in libnvidia-nscq-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Mantic:
  Fix Released
Status in fabric-manager-535 source package in Noble:
  Fix Released
Status in libnvidia-nscq-535 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  Fix Committed
Status in nvidia-graphics-drivers-535-server source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2048901/+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 2050098] [NEW] cgroup2 appears to be broken

Public bug reported:

We're using Slurm workload manager in a cluster with Ubuntu 22.04 and
the linux-generic kernel (amd64). We  use cgroups (cgroup2) for resource
allocation with Slurm. With kernel version

linux-image-5.15.0-91-generic 5.15.0-91.101
amd64

I'm seeing a new issue. This must have been introduces recently, I can
confirm that with kernel 5.15.0-88-generic the issue does not exist.
When I request a single GPU on a node with kernel 5.15.0-88-generic all
is well:

$ srun -G 1 -w gpu59 nvidia-smi -L
GPU 0: NVIDIA [...]


Instead with kernel 5.15.0-91-generic:

$ srun -G 1 -w gpu59 nvidia-smi -L
slurmstepd: error: load_ebpf_prog: BPF load error (No space left on device). 
Please check your system limits (MEMLOCK).
GPU 0: NVIDIA [...]
GPU 1: NVIDIA [...]
GPU 2: NVIDIA [...]
GPU 3: NVIDIA [...]
GPU 4: NVIDIA [...]
GPU 5: NVIDIA [...]
GPU 6: NVIDIA [...]
GPU 7: NVIDIA [...]

So I get this error regarding MEMLOCK limit and see all GPUs in the
system instead of only the one requested. Hence I assume the problem is
related to cgroups.

$ cat /proc/version_signature 
Ubuntu 5.15.0-91.101-generic 5.15.131

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

** Attachment added: "ubuntu-bug linux output"
   
https://bugs.launchpad.net/bugs/2050098/+attachment/5741416/+files/apport.linux-image-5.15.0-91-generic.l9ripain.apport

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

Title:
  cgroup2 appears to be broken

Status in linux package in Ubuntu:
  New

Bug description:
  We're using Slurm workload manager in a cluster with Ubuntu 22.04 and
  the linux-generic kernel (amd64). We  use cgroups (cgroup2) for
  resource allocation with Slurm. With kernel version

  linux-image-5.15.0-91-generic 5.15.0-91.101
  amd64

  I'm seeing a new issue. This must have been introduces recently, I can
  confirm that with kernel 5.15.0-88-generic the issue does not exist.
  When I request a single GPU on a node with kernel 5.15.0-88-generic
  all is well:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  GPU 0: NVIDIA [...]

  
  Instead with kernel 5.15.0-91-generic:

  $ srun -G 1 -w gpu59 nvidia-smi -L
  slurmstepd: error: load_ebpf_prog: BPF load error (No space left on device). 
Please check your system limits (MEMLOCK).
  GPU 0: NVIDIA [...]
  GPU 1: NVIDIA [...]
  GPU 2: NVIDIA [...]
  GPU 3: NVIDIA [...]
  GPU 4: NVIDIA [...]
  GPU 5: NVIDIA [...]
  GPU 6: NVIDIA [...]
  GPU 7: NVIDIA [...]

  So I get this error regarding MEMLOCK limit and see all GPUs in the
  system instead of only the one requested. Hence I assume the problem
  is related to cgroups.

  $ cat /proc/version_signature 
  Ubuntu 5.15.0-91.101-generic 5.15.131

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2050098/+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 2048901] Re: Update the NVIDIA ERD 535 series to 535.154.05

This bug was fixed in the package libnvidia-nscq-535 -
535.154.05-0ubuntu0.20.04.1

---
libnvidia-nscq-535 (535.154.05-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #2048901)
  * Make orig tarballs reproducible

 -- Dimitri John Ledkov   Thu, 11 Jan 2024
12:19:54 +

** Changed in: libnvidia-nscq-535 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Update the NVIDIA ERD 535 series to 535.154.05

Status in fabric-manager-535 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-535 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  Fix Committed
Status in fabric-manager-535 source package in Bionic:
  New
Status in libnvidia-nscq-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535 source package in Bionic:
  New
Status in nvidia-graphics-drivers-535-server source package in Bionic:
  New
Status in fabric-manager-535 source package in Focal:
  Fix Released
Status in libnvidia-nscq-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Focal:
  Fix Released
Status in fabric-manager-535 source package in Jammy:
  Fix Released
Status in libnvidia-nscq-535 source package in Jammy:
  Fix Committed
Status in nvidia-graphics-drivers-535 source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Jammy:
  Fix Released
Status in fabric-manager-535 source package in Mantic:
  Fix Released
Status in libnvidia-nscq-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-535-server source package in Mantic:
  Fix Released
Status in fabric-manager-535 source package in Noble:
  Fix Released
Status in libnvidia-nscq-535 source package in Noble:
  Fix Released
Status in nvidia-graphics-drivers-535 source package in Noble:
  Fix Committed
Status in nvidia-graphics-drivers-535-server source package in Noble:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2048901/+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 2039231] Re: UBSAN: array-index-out-of-bounds in /build/linux-oem-6.5-XiW3QL/linux-oem-6.5-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7655:12

2024-01-22 Thread Joel

I too have this issue: 
01:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2308 PCI-Express 
Fusion-MPT SAS-2 (rev 05)
Subsystem: Broadcom / LSI 9207-8i SAS2.1 HBA
Kernel driver in use: mpt3sas
Kernel modules: mpt3sas

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

Title:
   UBSAN: array-index-out-of-bounds in /build/linux-
  oem-6.5-XiW3QL/linux-
  oem-6.5-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:7655:12

Status in linux-oem-6.5 package in Ubuntu:
  Confirmed

Bug description:
  Dmesg is full of UBSAN errors to do with the mpt3sas driver when
  initializing an mpt2sas device.

  [5.012673] UBSAN: array-index-out-of-bounds in 
/build/linux-oem-6.5-XiW3QL/linux-oem-6.5-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12
  [5.014521] index 1 is out of range for type 
'MPI2_EVENT_SAS_TOPO_PHY_ENTRY [1]'
  [5.015606] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 6.5.0-1004-oem 
#4-Ubuntu
  [5.015611] Hardware name: Supermicro C7Q67/C7Q67, BIOS 2.1a 11/10/2015
  [5.015613] Call Trace:
  [5.015617]  
  [5.015621]  dump_stack_lvl+0x48/0x70
  [5.015632]  dump_stack+0x10/0x20
  [5.015637]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [5.015646]  _scsih_check_topo_delete_events+0x2dc/0x350 [mpt3sas]
  [5.015698]  mpt3sas_scsih_event_callback+0x21f/0x630 [mpt3sas]
  [5.015735]  _base_async_event.isra.0+0x73/0x190 [mpt3sas]
  [5.015769]  _base_process_reply_queue+0x3a0/0x720 [mpt3sas]
  [5.015799]  _base_interrupt+0x4e/0x70 [mpt3sas]
  [5.015829]  __handle_irq_event_percpu+0x4f/0x1c0
  [5.015835]  handle_irq_event+0x39/0x80
  [5.015839]  handle_edge_irq+0x8c/0x250
  [5.015844]  __common_interrupt+0x56/0x110
  [5.015850]  common_interrupt+0x9f/0xb0
  [5.015854]  
  [5.015856]  
  [5.015858]  asm_common_interrupt+0x27/0x40
  [5.015865] RIP: 0010:cpuidle_enter_state+0xda/0x720
  [5.015872] Code: 25 07 ff e8 a8 f5 ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 
31 ff e8 46 d1 05 ff 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 
0f 88 f7 01 00 00 4d 63 ee 49 83 fd 09 0f 87 19 05 00 00
  [5.015876] RSP: 0018:ac24c00bbe18 EFLAGS: 0246
  [5.015881] RAX:  RBX: a0abc03beb00 RCX: 

  [5.015884] RDX: 0003 RSI:  RDI: 

  [5.015886] RBP: ac24c00bbe68 R08:  R09: 

  [5.015888] R10:  R11:  R12: 
b64d1ac0
  [5.015890] R13: 0004 R14: 0004 R15: 
00012ab445e7
  [5.015895]  ? cpuidle_enter_state+0xca/0x720
  [5.015901]  ? tick_nohz_stop_tick+0x90/0x210
  [5.015908]  cpuidle_enter+0x2e/0x50
  [5.015912]  call_cpuidle+0x23/0x60
  [5.015918]  cpuidle_idle_call+0x11d/0x190
  [5.015922]  do_idle+0x82/0xf0
  [5.015926]  cpu_startup_entry+0x1d/0x20
  [5.015930]  start_secondary+0x129/0x160
  [5.015936]  secondary_startup_64_no_verify+0x17e/0x18b
  [5.015944]  
  [5.015946] 

  [5.017993] mpt2sas_cm0: hba_port entry: fd3a54f4, port: 255 is 
added to hba_port list
  [5.018324] 

  [5.019566] UBSAN: array-index-out-of-bounds in 
/build/linux-oem-6.5-XiW3QL/linux-oem-6.5-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:6810:36
  [5.021429] index 1 is out of range for type 'MPI2_SAS_IO_UNIT0_PHY_DATA 
[1]'
  [5.022478] CPU: 2 PID: 153 Comm: kworker/u8:7 Not tainted 6.5.0-1004-oem 
#4-Ubuntu
  [5.022483] Hardware name: Supermicro C7Q67/C7Q67, BIOS 2.1a 11/10/2015
  [5.022486] Workqueue: fw_event_mpt2sas0 _firmware_event_work [mpt3sas]
  [5.022533] Call Trace:
  [5.022536]  
  [5.022539]  dump_stack_lvl+0x48/0x70
  [5.022547]  dump_stack+0x10/0x20
  [5.022551]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [5.022559]  _scsih_sas_host_add+0x669/0x700 [mpt3sas]
  [5.022597]  _mpt3sas_fw_work+0x753/0xbc0 [mpt3sas]
  [5.022633]  ? raw_spin_rq_unlock+0x10/0x40
  [5.022637]  ? finish_task_switch.isra.0+0x85/0x2a0
  [5.022642]  ? __schedule+0x2d4/0x750
  [5.022648]  _firmware_event_work+0x16/0x20 [mpt3sas]
  [5.022681]  process_one_work+0x240/0x450
  [5.022688]  worker_thread+0x50/0x3f0
  [5.022693]  ? __pfx_worker_thread+0x10/0x10
  [5.022698]  kthread+0xf2/0x120
  [5.022704]  ? __pfx_kthread+0x10/0x10
  [5.022710]  ret_from_fork+0x47/0x70
  [5.022717]  ? __pfx_kthread+0x10/0x10
  [5.022722]  ret_from_fork_asm+0x1b/0x30
  [5.022728]  
  [5.022729] 

  [5.025642] mpt2sas_cm0: host_add: handle(0x0001),

[Kernel-packages] [Bug 2049750] Re: "kvm: enabling virtualization on CPUx failed" on "Ubuntu 22.04.03 with kernel 6.5.0-14-generic"

2024-01-22 Thread Lancillotto

My logs simply report the message "kvm: enabling virtualization on CPUx
failed" for each CPU.

No other messages are present.

Could you be interested in my hardware specs?

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

Title:
  "kvm: enabling virtualization on CPUx failed" on "Ubuntu 22.04.03 with
  kernel 6.5.0-14-generic"

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

Bug description:
  Hi, I am on Ubuntu 22.04.03 with kernel 6.5.0-14-generic.

  Running a VM by AndroidStudio, it does not start, and into the DMSG
  log I see a message like "kvm: enabling virtualization on CPUx failed"
  for each CPU.

  It works with kernel 6.2.

  Regards,
  Antonio Petricca

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


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

[Kernel-packages] [Bug 2028253] Re: update apparmor and LSM stacking patch set

2024-01-22 Thread Andrea Righi

** Also affects: linux (Ubuntu Noble)
   Importance: Critical
   Status: Fix Released

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

Title:
  update apparmor and LSM stacking patch set

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Mantic:
  Fix Released
Status in linux source package in Noble:
  Fix Released

Bug description:
  [Impact]

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

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

  [Fix]

  Apply the latest updated patch set from:

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

  [Test case]

  Run the apparmor test case suite.

  [Regression potential]

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

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


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

[Kernel-packages] [Bug 2049750] Re: "kvm: enabling virtualization on CPUx failed" on "Ubuntu 22.04.03 with kernel 6.5.0-14-generic"

2024-01-22 Thread Roxana Nicolescu

Can you include some logs so we can properly investigate.
Follow 'Adding debug info to a bug report' from 
https://wiki.ubuntu.com/Kernel/Bugs

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

Title:
  "kvm: enabling virtualization on CPUx failed" on "Ubuntu 22.04.03 with
  kernel 6.5.0-14-generic"

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

Bug description:
  Hi, I am on Ubuntu 22.04.03 with kernel 6.5.0-14-generic.

  Running a VM by AndroidStudio, it does not start, and into the DMSG
  log I see a message like "kvm: enabling virtualization on CPUx failed"
  for each CPU.

  It works with kernel 6.2.

  Regards,
  Antonio Petricca

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2049750/+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 2050083] [NEW] generate and ship vmlinux.h to allow packages to build BPF CO-RE

2024-01-22 Thread Luca Boccassi

Public bug reported:

A vmlinux.h header generated from a kernel build with bpftool is needed to 
build and ship BPF CO-RE programs. We are looking to ship these in the next 
version of systemd.
vmlinux.h being generated depends on the kernel version, architecture and 
kconfig. There are some vague promises of backward compatibility, but it is 
hard to gauge.

We definitely do not want this file to be generated from the kernel
running the build machine when building a package though, as very often
these are very old and stable kernels building packages for the bleeding
edge.

In Fedora and now Debian we generate vmlinux.h at kernel package build
time, and ship it with the other kernel headers (_not_ UAPI, the
internal headers): https://salsa.debian.org/kernel-
team/linux/-/commit/ac6f7eda4c3e8b0d0db20ad4bb8236371cf8d38e

Please consider doing the same in Ubuntu's linux-headers.

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

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

Title:
  generate and ship vmlinux.h to allow packages to build BPF CO-RE

Status in linux package in Ubuntu:
  New

Bug description:
  A vmlinux.h header generated from a kernel build with bpftool is needed to 
build and ship BPF CO-RE programs. We are looking to ship these in the next 
version of systemd.
  vmlinux.h being generated depends on the kernel version, architecture and 
kconfig. There are some vague promises of backward compatibility, but it is 
hard to gauge.

  We definitely do not want this file to be generated from the kernel
  running the build machine when building a package though, as very
  often these are very old and stable kernels building packages for the
  bleeding edge.

  In Fedora and now Debian we generate vmlinux.h at kernel package build
  time, and ship it with the other kernel headers (_not_ UAPI, the
  internal headers): https://salsa.debian.org/kernel-
  team/linux/-/commit/ac6f7eda4c3e8b0d0db20ad4bb8236371cf8d38e

  Please consider doing the same in Ubuntu's linux-headers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2050083/+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 2008583] Re: VMware nested under KVM stopped working on 5.19 kernel on Ryzen: Invalid VMCB.

2024-01-22 Thread dfdfdf

The patch is in 6.8-rc1, how can we make Canonical to cherry-pick that
patch into current 6.5 kernel?

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

Title:
   VMware nested under KVM stopped working on 5.19 kernel on Ryzen:
  Invalid VMCB.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My setup:

  Host: Ubuntu Linux 22.04.1, kernel 5.15, Ryzen 5900x
  Hypervisor: KVM
  Windows VM with VMware Workstation 16

  Running nested VMs in VMware works ok.

  It fails if Linux host kernel is updated to 5.19 (22.04.2) with

  MONITOR PANIC: Invalid VMCB.
  VMware Workstation unrecoverable error: (vcpu-0)
  vcpu-0:Invalid VMCB.

  If I update to Workstation 17 it fails with

  2023-02-24T15:21:35.112Z In(05) vmx The following features are required for 
SVM support in VMware Workstation; however, these features are not available on 
this host:
  2023-02-24T15:21:35.112Z In(05) vmxFlush by ASID.
  This host supports AMD-V, but the AMD-V implementation is incompatible with 
VMware Workstation.
  VMware Workstation does not support the user level monitor on this host.
  Module 'MonitorMode' power on failed.

   
  The same VM works ok on 5.19 kernel on my Intel PC.

  So it has to do with updated Linux kernel and AMD virtualization and
  VMware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008583/+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 2049022] Re: virtualbox-dkms.0.crash VirtualBox DKMS module NOT working

2024-01-22 Thread Roxana Nicolescu

I just tried installing virtualbox dkms and it did build. Version
6.1.48-dfsg-1~ubuntu1.22.04.1.

Are you using a different version?
And some logs from virtualbox client will help.

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

Title:
  virtualbox-dkms.0.crash VirtualBox DKMS module NOT working

Status in linux-signed-hwe-6.5 package in Ubuntu:
  Confirmed

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  vcarceler@zvezda:~$ lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04
  vcarceler@zvezda:~$

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  vcarceler@zvezda:~$ apt-cache policy linux-generic-hwe-22.04
  linux-generic-hwe-22.04:
Instalados: 6.5.0.14.14~22.04.7
Candidato:  6.5.0.14.14~22.04.7
Tabla de versión:
   *** 6.5.0.14.14~22.04.7 500
  500 http://es.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://es.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  vcarceler@zvezda:~$

  3) What you expected to happen

  VirtualBox works

  4) What happened instead

  VirtualBox not working

  Building virtualbox module fails. It's not possible to run virtual
  machines with virtualbox.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2049022/+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 2050017] Re: [24.04 FEAT] [SEC2339] HSM protected signing support for Apache httpd for openSSL 3.0 with PKCS #11 provider

2024-01-22 Thread Frank Heimes

** Information type changed from Private to Public

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

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

Title:
  [24.04 FEAT] [SEC2339] HSM protected signing support for Apache httpd
  for openSSL 3.0 with PKCS #11 provider

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

Bug description:
  Enable an E2E use case that allows to configure an Apache webserver to
  protect its private keys with an HSM that is addressable via an PKCS
  #11 (signing) provider configured for an openSSL 3.0 library.

  Accepted for httpd > 2.4.58, see
  https://svn.apache.org/viewvc?view=revision=1914365

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2050017/+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 1970069] Re: Annoying boot messages interfering with splash screen

The kernel patch is still in progress but I also wonder if plymouthd
starts early enough to do all the console blocking? If so then it could
FBIOPUT_CON2FBMAP like con2fbmap does, to umap the console from the
framebuffer. But that's still racing with other kernel things which
might have already dumped text onto the console. So a kernel patch is
probably still the only fully reliable solution.

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

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid

Bug description:
  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 2048945] Re: scsi_eh_* process using idle CPU after upgrade to kernel 6.5

2024-01-22 Thread Roxana Nicolescu

This should be solved in the lastest jammy:hwe-6.5 version. It's gonna
be in -proposed these days.

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

Title:
  scsi_eh_* process using idle CPU after upgrade to kernel 6.5

Status in linux:
  Confirmed
Status in linux-aws-6.5 package in Ubuntu:
  New
Status in linux-hwe-6.5 package in Ubuntu:
  New
Status in linux-meta-hwe-6.5 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  Possibly related to https://lkml.kernel.org/linux-
  scsi/7611d95d0aada3814a5b140661b3b5188b8b86bb.ca...@redhat.com/T/

  Getting alerts from monitoring tools about high average CPU usage.
  Machine reporting the following:

  root@server:~# uptime
   17:04:34 up 14 days,  6:33,  2 users,  load average: 15.66, 15.88, 15.94

  root@server:~# top -d 1

  top - 17:04:49 up 14 days,  6:33,  2 users,  load average: 15.59, 15.85, 15.93
  Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  0.7 us,  1.4 sy,  0.0 ni, 49.3 id, 48.6 wa,  0.0 hi,  0.0 si,  0.0 
st
  MiB Mem :   7896.6 total,   1772.6 free,   1163.9 used,   4960.0 buff/cache
  MiB Swap:   2048.0 total,   1784.6 free,263.4 used.   6431.6avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
   88 root  20   0   0  0  0 D  55.4   0.0  11275:46 
scsi_eh_1

  root@server:~# lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  root@server:~# apt-cache policy linux-image-virtual-hwe-22.04-edge
  linux-image-virtual-hwe-22.04-edge:
Installed: 6.5.0.14.14~22.04.6
Candidate: 6.5.0.14.14~22.04.7
Version table:
   6.5.0.14.14~22.04.7 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   *** 6.5.0.14.14~22.04.6 100
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Jan 10 17:02:50 2024
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  Package: linux-image-virtual-hwe-22.04-edge 6.5.0.14.14~22.04.6
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Tags: jammy third-party-packages
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 10:31 seq
   crw-rw 1 root audio 116, 33 Dec 27 10:31 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
  DistroRelease: Ubuntu 22.04
  HibernationDevice: #RESUME=UUID=9bf7612f-b07b-4adf-9760-0c14b8d7d6fc
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vmwgfxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=07ffde4f-b32f-41fe-81dd-4fe4b186dab4 ro
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.23
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-05-02 (253 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date:

[Kernel-packages] [Bug 2049924] Re: WireGuard broken on Noble ppc64el

2024-01-22 Thread Lukas Märdian

** Tags added: update-excuse

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

Title:
  WireGuard broken on Noble ppc64el

Status in linux package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New
Status in linux source package in Noble:
  New
Status in netplan.io source package in Noble:
  New

Bug description:
  Netplan autopkgtests related to Wireguard are currently failing (see
  below) on Noble ppc64el. Trying it manually on a ppc64el system, I
  can't load the kernel module:

  ~# modprobe wireguard
  modprobe: ERROR: could not insert 'wireguard': No such device

  
  And because of that the interface can't be created:

  Jan 19 15:47:59 mantic-bos01-ppc64el NetworkManager[2414]:   
[1705679279.5797] platform-linux: do-add-link[wg0/wireguard]: failure 95 
(Operation not supported - Unknown device type)
  Jan 19 15:47:59 mantic-bos01-ppc64el NetworkManager[2414]:  
[1705679279.5797] manager: (netplan-wg0) couldn't create the device: Failed to 
create WireGuard interface 'wg0' for 'netplan-wg0': Operation not supported

  
  Jan 19 15:45:08 mantic-bos01-ppc64el systemd-networkd[731]: 
/run/systemd/network/10-netplan-wg0.netdev has 0644 mode that is too 
permissive, please adjust the ownership and access mode.
  Jan 19 15:45:08 mantic-bos01-ppc64el systemd-networkd[731]: wg0: netdev could 
not be created: Operation not supported

  
  Autopkgtest error:

  2690s .Interface "wg0" not found.
  2691s .Interface "wg0" not found.
  2692s .Interface "wg0" not found.
  2693s ..Interface "wg0" not found.
  2694s Interface "wg0" not found.
  2695s .Interface "wg0" not found.
  2696s .Interface "wg0" not found.
  2697s .Interface "wg0" not found.
  2697s FAIL
  2697s 
  2697s ==
  2697s FAIL: test_tunnel_wireguard 
(__main__.TestNetworkManager.test_tunnel_wireguard)
  2697s --
  2697s Traceback (most recent call last):
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/tunnels.py", line 126, 
in test_tunnel_wireguard
  2697s self.generate_and_settle(['wg0', 'wg1'])
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 363, in 
generate_and_settle
  2697s self.nm_wait_connected(iface, 60)
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 419, in 
nm_wait_connected
  2697s self.wait_output(['nmcli', 'dev', 'show', iface], '(connected', 
timeout)
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 416, in 
wait_output
  2697s self.fail('timed out waiting for "{}" to appear in 
{}'.format(expected_output, cmd))
  2697s AssertionError: timed out waiting for "(connected" to appear in 
['nmcli', 'dev', 'show', 'wg0']
  2697s 
  2697s ==
  2697s FAIL: test_tunnel_wireguard 
(__main__.TestNetworkd.test_tunnel_wireguard)
  2697s --
  2697s Traceback (most recent call last):
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/tunnels.py", line 126, 
in test_tunnel_wireguard
  2697s self.generate_and_settle(['wg0', 'wg1'])
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 365, in 
generate_and_settle
  2697s self.networkd_wait_connected(iface, 60)
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 423, in 
networkd_wait_connected
  2697s self.wait_output(['networkctl', 'status', iface], '(configured', 
timeout)
  2697s   File 
"/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 416, in 
wait_output
  2697s self.fail('timed out waiting for "{}" to appear in 
{}'.format(expected_output, cmd))
  2697s AssertionError: timed out waiting for "(configured" to appear in 
['networkctl', 'status', 'wg0']
  2697s 
  2697s --
  2697s Ran 26 tests in 294.247s

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049924/+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 1989046] Re: support independent clock and LED GPIOs for Intel IPU6 platforms

2024-01-22 Thread You-Sheng Yang

For v6.3-rc1 or above, mainline commit 5ae20a8050d08 ("platform/x86:
int3472/discrete: Create a LED class device for the privacy LED")
replaced that sauced patch.

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

Title:
  support independent clock and LED GPIOs for Intel IPU6 platforms

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  When migrated from power_ctrl_logic driver to int3472, two additional
  independent CLK/LED GPIOs other than powerdown/reset must be probed
  exceptionally.

  [Fix]

  Vendor provided patch in
  
https://github.com/intel/ipu6-drivers/blob/2b8a592dc63e117d8f5af5f32a10d7e0651832d2/patch/int3472-support-independent-clock-and-LED-gpios-5.17+.patch.

  [Test Case]

  Tested on both TGL/ADL platforms against nominated kernels.

  [Where problems could occur]

  This adds exceptional cases with fallbacks to the original function. No
  one else is affected.

  [Other Info]

  This is an essential part for switching from power_ctrl_logic based GPIO
  control mechanism to the generic, upstreamed int3472 driver. Affects all
  IPU6 platforms that are to run new IPU6 driver dump in 202208.

  == original bug report ==

  Per
  
https://github.com/intel/ipu6-drivers/commit/f771bd3cb9f324a393a75e068a039bd1f9611026
  and
  
https://github.com/intel/ipu6-drivers/commit/2b8a592dc63e117d8f5af5f32a10d7e0651832d2,
  additional fix for INT3472 is necessary to probe camera sensor GPIOs
  on Intel IPU6 platforms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1989046/+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 1989046] Re: support independent clock and LED GPIOs for Intel IPU6 platforms

2024-01-22 Thread Anthony Wong

** Tags added: fixed-linux-oem-6.5

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

Title:
  support independent clock and LED GPIOs for Intel IPU6 platforms

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  When migrated from power_ctrl_logic driver to int3472, two additional
  independent CLK/LED GPIOs other than powerdown/reset must be probed
  exceptionally.

  [Fix]

  Vendor provided patch in
  
https://github.com/intel/ipu6-drivers/blob/2b8a592dc63e117d8f5af5f32a10d7e0651832d2/patch/int3472-support-independent-clock-and-LED-gpios-5.17+.patch.

  [Test Case]

  Tested on both TGL/ADL platforms against nominated kernels.

  [Where problems could occur]

  This adds exceptional cases with fallbacks to the original function. No
  one else is affected.

  [Other Info]

  This is an essential part for switching from power_ctrl_logic based GPIO
  control mechanism to the generic, upstreamed int3472 driver. Affects all
  IPU6 platforms that are to run new IPU6 driver dump in 202208.

  == original bug report ==

  Per
  
https://github.com/intel/ipu6-drivers/commit/f771bd3cb9f324a393a75e068a039bd1f9611026
  and
  
https://github.com/intel/ipu6-drivers/commit/2b8a592dc63e117d8f5af5f32a10d7e0651832d2,
  additional fix for INT3472 is necessary to probe camera sensor GPIOs
  on Intel IPU6 platforms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1989046/+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 2049442] Re: Enable symbols for all Xilinx device trees

** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy)
   Status: New => Fix Committed

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

Title:
  Enable symbols for all Xilinx device trees

Status in linux-xilinx-zynqmp package in Ubuntu:
  New
Status in linux-xilinx-zynqmp source package in Jammy:
  Fix Committed
Status in linux-xilinx-zynqmp source package in Noble:
  New

Bug description:
  [ Impact ]

  * This enables symbols for all device trees built for Xilinx products.
  * Currently only device trees which have overlays applied have symbols 
enabled.
  * Most Xilinx device trees are currently overlayed (thus have the symbols 
already included) so this should have minimal size impact.

  [ Test Plan ]

  * Xilinx will verify they can load the dtbo's for the FPGA during
  runtime

  [ Where problems could occur ]

  * There could be an unexpected impact on other FPGA runtime overlays
  that are already working.

  [ Other Info ]

  * Xilinx platforms apply dtbo's during runtime when loading FPGA firmware.
  * Xilinx Yocto distribution handle's this in the yocto recipes which is why 
this change is not upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2049442/+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 1970069] Re: Annoying boot messages interfering with splash screen