[Kernel-packages] [Bug 2038263] Re: Add SoF topology support on Intel RaptorLake DELL SKU 0C11

[Chris Chiu]

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

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

Title:
  Add SoF topology support on Intel RaptorLake DELL SKU 0C11

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

Bug description:
  SRU Jusitification for firmware-sof

  [Impact]
  To support audio functions on RPL Dell SKU 0C11, it requires the topology 
file from sof-tplg-v2.2.7

  [Fix]
  Pull the sof-rpl-rt711-l0-rt1316-l12.tplg from 
https://github.com/thesofproject/sof-bin/releases/tag/v2023.09

  [Test Case]
  Install the fixes on the target platform(RPL Dell SKU 0C11) and verify the 
audio function.
  1. Install the firmware-sof on platform(RPL) Dell SKU 0C11
  2. Make sure the audio output/input devices are not dummy in audio settings.

  [Where problems could occur]
  New firmware is only for the RPL platforms which requires the specific 
topology file.

  [Misc]
  https://github.com/thesofproject/sof-bin/releases/tag/v2023.09

  

  [Impact]
  Audio play/capture are not functional on specific Dell machines of Intel RPL 
platforms

  [Fix]
  Backport the fix from Intel in https://github.com/thesofproject/linux

  [Test Case]
  1. Power on the machine and open the audio settings
  2. Verify it's not `Dummy` shown on the Audio output/input option

  [Where problems could occur]
  Only affect specific Intel RPL platforms. The risk of regression is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2038263/+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 1987190] Re: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1

[Richard Brooksby]

This caused me a major headache and a lot of server downtime.  I have
written a detailed description of the situation and how I worked around
it on zfs-discuss here https://zfsonlinux.topicbox.com/groups/zfs-
discuss/Ta4f2dccd6172681c/partial-pool-loss-on-ubuntu-22-upgrade and it
may help others.  I have not applied this patch.

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

Title:
  ZFS unrecoverable error after upgrading from 20.04 to 22.04.1

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  I have a server that has been running its data volume using ZFS in
  20.04 without any problem. The volume is using ZFS encryption and a
  raidz1-0 configuration. I performed a scrub operations before the
  upgrade and it did not find any problem. After the reboot for the
  upgrade, I was welcomed with the following message:

  status: One or more devices has experienced an error resulting in data
  corruption.  Applications may be affected.
  action: Restore the file in question if possible.  Otherwise restore the
  entire pool from backup.
 see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A

  The volumes still do not have any checksum error but there are 5 zvols
  that are not accessible. zpool status displays a line similar to the
  below for each of the five:

  errors: Permanent errors have been detected in the following files:   



  tank/data/data:<0x0>

  I run a scrub and it has not identified any problem but the error
  messages are not there and the data is still not available. There are
  10+ other zvols in the zpool that do not have any kind of problem. I
  have been unable to identify any correlation between the zvols that
  are failing.

  I have seen people reporting similar problems in github after the
  20.04 to the 22.04 upgrade (see
  https://github.com/openzfs/zfs/issues/13763). I wonder how widespread
  the problem will be as more people upgrades to 22.04.

  I will try to downgrade the version of zfs in the system and report
  back

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: zfsutils-linux 2.1.4-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sat Aug 20 22:24:54 2022
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to jammy on 2022-08-20 (0 days ago)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1987190/+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 2038583] Re: Turning COMPAT_32BIT_TIME off on s390x

[Dimitri John Ledkov]

Studying this more, this is likely to only affect trying to run
libc6-s390 that is from 18.04 bionic or older. As later versions of
libc6-s390 wrap 64bit syscall, instead of calling 32bit syscall
directly.

However, ideally we would drop all s390 (31 bit) binaries from Ubuntu,
and turn off COMPAT / COMPAT_32BIT_TIME in the 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/2038583

Title:
  Turning COMPAT_32BIT_TIME off on s390x

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This will prevent existing s390 binaries to operate correctly, if they
  are still using 32bit time.

  24.04 LTS is likely to be used for 10 years. And if allowed to overrun
  and remain active in the field in 2038 can lead to catastrophic
  failure in the field due to these syscalls enabled and used.

  I would like to request if we can turn off COMPAT_32BIT_TIME on every
  architecture, thus this will be arch by arch bug report, and arch by
  arch decision.

  This needs to be a per-arch decision, potentially taking into
  consideration bi-arch userspace support.

  config COMPAT_32BIT_TIME
   bool "Provide system calls for 32-bit time_t"
   default !64BIT || COMPAT
   help
 This enables 32 bit time_t support in addition to 64 bit time_t support.
 This is relevant on all 32-bit architectures, and 64-bit architectures
 as part of compat syscall handling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2038583/+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 2037224] Re: Multiple RTL8851BE BT stability issues

[You-Sheng Yang]

verified linux-firmware/jammy version 20220329.git681281e4-0ubuntu3.21

** Tags added: verification-done-jammy

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

Title:
  Multiple RTL8851BE BT stability issues

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

Bug description:
  [SRU Justification]

  [Impact]

  There are multiple stability issues for RTL8851B.

  Issue-1:

  After disabling BT and leaving it idle for a period, manually turning on the
  RTL8851BE will fail.

  Issue-2:

  Failed to probe Bluetooth USB interface after resumed from suspend. There may 
be
  either failure to read device descriptors:

usb 1-14: device descriptor read/64, error -71

  or tx command timeout:

Bluetooth: hci0: Opcode 0x2041 failed: -110
Bluetooth: hci0: command 0x2041 tx timeout

  [Fix]

  Upstream commit addc33924 ("rtl_bt: Update RTL8851B BT USB firmware to
  0x048A_D230").

  [Test Case]

  $ checkbox-cli run
  com.canonical.plainbox::suspend/suspend_advanced_auto

  [Where problems could occur]

  This updates opaque firmware blobs, so it could bring further stability issues
  and/or power consumption changes.

  [Other Info]

  While RTL8851B is only supported in oem-6.5 and linux/mantic >= 6.4, only 
jammy
  and mantic are nominated for fix.

  = original bug report ==

  [issue 1]

  After disabling BT and leaving it idle for a period, manually turning
  on the RTL8851BE will fail. (Can't reproduce on Wifi functionality.)

  Test step:
  1. Insert RTL8851BE Wifi card and install Ubuntu 22.04 OS. (Kernel : 6.5.0)
  2. Check BT function after boot into OS.
  3. Manually turn OFF BT function. Then wait for 1 minute.
  4. Manually turn ON the BT function.
  5. Unable to enable BT function. (issue occurs)

  [issue 2]

  System usb got tx command timeout after suspend resume.

  Log:

  Got read usb descriptor fail after suspend resume.

  Sep 11 16:37:37 ubuntu kernel: usb 1-14: reset full-speed USB device number 3 
using xhci_hcd
  Sep 11 16:37:37 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
  Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
  Sep 11 16:37:38 ubuntu kernel: usb 1-14: reset full-speed USB device number 3 
using xhci_hcd
  Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
  Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71
  Sep 11 16:37:39 ubuntu kernel: usb 1-14: reset full-speed USB device number 3 
using xhci_hcd

  And tx command timeout.

  Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: Opcode 0x2041 failed: -110
  Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: command 0x2041 tx timeout
  Sep 11 16:37:41 ubuntu kernel: usb 1-14: new full-speed USB device number 4 
using xhci_hcd
  Sep 11 16:37:41 ubuntu kernel: usb 1-14: device descriptor read/64, error -71

  Test step:
  1. Install dell-bto-jammy-jellyfish-abra-X96-20230822-1.iso
  2. Boot into OS
  3. checkbox-cli run com.canonical.plainbox::suspend/suspend_advanced_auto

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-6.2/6.2.0.1016.16~22.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-azure-6.2 
(6.2.0.1016.16~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

linux-azure-6.2/6.2.0-1016.16~22.04.1 (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-azure-6.2

[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 2039110] [NEW] Lunar update: upstream stable patchset 2023-10-11

[Kamal Mostafa]

Public bug reported:

SRU Justification

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

   upstream stable patchset 2023-10-11

Ported from the following upstream stable releases:
v6.1.47, v6.4.12

   from git://git.kernel.org/

selftests: forwarding: tc_actions: cleanup temporary files when test is aborted
net/smc: replace mutex rmbs_lock and sndbufs_lock with rw_semaphore
net: phy: at803x: Use devm_regulator_get_enable_optional()
net: phy: at803x: fix the wol setting functions
drm/amdgpu: fix calltrace warning in amddrm_buddy_fini
drm/amdgpu: Fix integer overflow in amdgpu_cs_pass1
drm/amdgpu: fix memory leak in mes self test
ASoC: Intel: sof_sdw: add quirk for MTL RVP
ASoC: Intel: sof_sdw: add quirk for LNL RVP
PCI: tegra194: Fix possible array out of bounds access
ASoC: SOF: amd: Add pci revision id check
drm/stm: ltdc: fix late dereference check
drm: rcar-du: remove R-Car H3 ES1.* workarounds
ASoC: amd: vangogh: Add check for acp config flags in vangogh platform
ARM: dts: imx6dl: prtrvt, prtvt7, prti6q, prtwd2: fix USB related warnings
ASoC: Intel: sof_sdw_rt_sdca_jack_common: test SOF_JACK_JDSRC in _exit
ASoC: Intel: sof_sdw: Add support for Rex soundwire
iopoll: Call cpu_relax() in busy loops
ASoC: SOF: Intel: fix SoundWire/HDaudio mutual exclusion
dma-remap: use kvmalloc_array/kvfree for larger dma memory remap
accel/habanalabs: add pci health check during heartbeat
HID: logitech-hidpp: Add USB and Bluetooth IDs for the Logitech G915 TKL 
Keyboard
iommu/amd: Introduce Disable IRTE Caching Support
drm/amdgpu: install stub fence into potential unused fence pointers
drm/amd/display: Apply 60us prefetch for DCFCLK <= 300Mhz
RDMA/mlx5: Return the firmware result upon destroying QP/RQ
drm/amd/display: Skip DPP DTO update if root clock is gated
drm/amd/display: Enable dcn314 DPP RCO
ASoC: SOF: core: Free the firmware trace before calling snd_sof_shutdown()
HID: intel-ish-hid: ipc: Add Arrow Lake PCI device ID
ALSA: hda/realtek: Add quirks for ROG ALLY CS35l41 audio
smb: client: fix warning in cifs_smb3_do_mount()
cifs: fix session state check in reconnect to avoid use-after-free issue
serial: stm32: Ignore return value of uart_remove_one_port() in .remove()
led: qcom-lpg: Fix resource leaks in for_each_available_child_of_node() loops
media: v4l2-mem2mem: add lock to protect parameter num_rdy
media: camss: set VFE bpl_alignment to 16 for sdm845 and sm8250
usb: gadget: u_serial: Avoid spinlock recursion in __gs_console_push
usb: gadget: uvc: queue empty isoc requests if no video buffer is available
media: platform: mediatek: vpu: fix NULL ptr dereference
thunderbolt: Read retimer NVM authentication status prior 
tb_retimer_set_inbound_sbtx()
usb: chipidea: imx: don't request QoS for imx8ulp
usb: chipidea: imx: add missing USB PHY DPDM wakeup setting
gfs2: Fix possible data races in gfs2_show_options()
pcmcia: rsrc_nonstatic: Fix memory leak in nonstatic_release_resource_db()
thunderbolt: Add Intel Barlow Ridge PCI ID
thunderbolt: Limit Intel Barlow Ridge USB3 bandwidth
firewire: net: fix use after free in fwnet_finish_incoming_packet()
watchdog: sp5100_tco: support Hygon FCH/SCH (Server Controller Hub)
Bluetooth: L2CAP: Fix use-after-free
Bluetooth: btusb: Add MT7922 bluetooth ID for the Asus Ally
ceph: try to dump the msgs when decoding fails
drm/amdgpu: Fix potential fence use-after-free v2
fs/ntfs3: Enhance sanity check while generating attr_list
fs: ntfs3: Fix possible null-pointer dereferences in mi_read()
fs/ntfs3: Mark ntfs dirty when on-disk struct is corrupted
ALSA: hda/realtek: Add quirks for Unis H3C Desktop B760 & Q760
ALSA: hda: fix a possible null-pointer dereference due to data race in 
snd_hdac_regmap_sync()
ALSA: hda/realtek: Add quirk for ASUS ROG GX650P
ALSA: hda/realtek: Add quirk for ASUS ROG GA402X
ALSA: hda/realtek: Add quirk for ASUS ROG GZ301V
powerpc/kasan: Disable KCOV in KASAN code
Bluetooth: MGMT: Use correct address for memcpy()
ring-buffer: Do not swap cpu_buffer during resize process
igc: read before write to SRRCTL register
drm/amd/display: save restore hdcp state when display is unplugged from mst hub
drm/amd/display: phase3 mst hdcp for multiple displays
drm/amd/display: fix access hdcp_workqueue assert
fbdev/hyperv-fb: Do not set struct fb_info.apertures
btrfs: move out now unused BG from the reclaim list
btrfs: fix use-after-free of new block group that became unused
virtio-mmio: don't break lifecycle of vm_dev
vduse: Use proper spinlock for IRQ injection
vdpa/mlx5: Fix mr->initialized semantics
vdpa/mlx5: Delete control vq iotlb in destroy_mr only 

[Kernel-packages] [Bug 2035135] Re: Oracle Cloud systems not getting Jammy kernel updates

[David Myers]

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

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

Title:
  Oracle Cloud systems not getting Jammy kernel updates

Status in linux-meta-oracle package in Ubuntu:
  Fix Released

Bug description:
  (Please forgive my ignorance of the kernel release process, maybe I've
  gotten this all wrong.)

  There have been several kernel releases for Jammy lately but the two
  systems I have on Oracle Cloud (one amd64 and one arm64) have not been
  receiving updates since kernel 5.15.0-1040. It looks like the linux-
  oracle package is no longer getting updated? Were we supposed to
  change to a new package called linux-oracle-lts-22.04?

  lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  apt-cache policy linux-oracle
  linux-oracle:
Installed: 5.15.0.1040.35
Candidate: 5.15.0.1040.35
Version table:
   *** 5.15.0.1040.35 500
  500 http://iad-ad-3.clouds.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.1002.2 500
  500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages

  apt-cache policy linux-oracle-lts-22.04
  linux-oracle-lts-22.04:
Installed: (none)
Candidate: 5.15.0.1042.37
Version table:
   5.15.0.1042.37 500
  500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu 
jammy-updates/main amd64 Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages

  Thanks!

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

[Thadeu Lima de Souza Cascardo]

Testing with that commit reverted, it works. Testing on a 6.5 kernel on
jammy fails. When testing on mantic, it works. When testing on mantic,
on an lxc jammy container, it fails inside the container, with that same
kernel.

So, it looks like systemd-networkd sets up the Local tunnel address as
the IFLA_ADDR, and the Remote tunnel address as the IFLA_BROADCAST
netlink attributes. This is what the validation from commit b0ad3c179059
is trying to validate. Those attributes are supposed to be hardware
addresses, not the tunnel addresses.

This needs to be investigated on the systemd side. As I read the systemd
code from the jammy version, I didn't find where this would be
incorrectly set. It may be necessary to revert this kernel code, fix
systemd, and wait for some time before reintroducing this kernel fix.
That all depends on why exactly systemd is doing this. Depending on the
resulting investigation, we will need to reassess if this can be
reasonably be used to revert that commit upstream. But given newer
systemd does the right thing, it might be hard to do it.

Cascardo.

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

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

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

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Invalid
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
  

[Kernel-packages] [Bug 2039099] [NEW] [X13s] Enable UEFI SecureBoot

[Dimitri John Ledkov]

Public bug reported:

Create vmlinuz that is a valid UKI - with sd-boot stub, .linux section,
.devicetree section, and without initrd and ensure that it is signed at
first with test keys, followed by production keys.

** Affects: ubuntu-concept
 Importance: Undecided
 Status: New

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

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

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

Title:
  [X13s] Enable UEFI SecureBoot

Status in ubuntu-concept:
  New
Status in linux-laptop package in Ubuntu:
  New

Bug description:
  Create vmlinuz that is a valid UKI - with sd-boot stub, .linux
  section, .devicetree section, and without initrd and ensure that it is
  signed at first with test keys, followed by production keys.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-concept/+bug/2039099/+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 2037204] Re: [X13s] Latest Ubuntu X13s concept still resets sometimes

[Dimitri John Ledkov]

** Summary changed:

- Latest Ubuntu X13s concept still resets
+ [X13s] Latest Ubuntu X13s concept still resets sometimes

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

** Tags added: arm64 x13s

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

Title:
  [X13s] Latest Ubuntu X13s concept still resets sometimes

Status in ubuntu-concept:
  New
Status in linux-laptop package in Ubuntu:
  New

Bug description:
  Also the latest Ubuntu X13s concept—after release upgrade to Mantic
  (6.5.0-1002-laptop)—still resets „randomly“. Though the uptime is now
  sometimes hours (not minutes) it‘s still not reliable.

  It seems this behavior is Ubuntu related, as folks from
  #aarch64-laptops running WIP branches or mainline on arch and xorg are
  not seeing this.

  Unfort. I do not have a pointer to some err logs. But will update if
  find something.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-concept/+bug/2037204/+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 2037534] Re: [X13s] Set unique bluetooth mac address

[Dimitri John Ledkov]

** Summary changed:

- set unique bluetooth mac address
+ [X13s] Set unique bluetooth mac address

** Tags added: x13s

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

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

Title:
  [X13s] Set unique bluetooth mac address

Status in systemd:
  New
Status in ubuntu-concept:
  New
Status in linux-meta-laptop package in Ubuntu:
  New

Bug description:
  On windows side MAC address for WLAN and Bluetooth are similar - like
  off by 4 from each other. I am guessing that a range of MACs is used
  per device (i.e. sequentially for wlan, sim cards, bluetooth).

  On linux side we do not currently have ability to find out the
  expected device MAC.

  Currently setting to static one is ok, but will not work when all of
  us are in Riga with all of our X13s devices.

  [Unit]
  Description=Set Bluetooth Address
  After=bluetooth.target
  Requires=bluetooth.target

  [Service]
  Type=simple
  ExecStartPre=/usr/bin/sleep 5
  ExecStart=/bin/bash -c "/usr/bin/yes | /usr/bin/btmgmt public-addr 
AD:5A:00:F0:FD:8C"

  [Install]
  WantedBy=multi-user.target

  Imho this should be impoved as follows:

  1) make this wantedby individual bluetooth device, not bluetooth.target
  2) make it bind to bluetooth device, such that it is stopped/started upon 
device poweroff/poweron (need to check if needed to set address every time)
  3) make it conditional on btmgmt to be available
  4) set or derive MAC from /etc/machine-id (maybe systemd should be able to do 
this for us?)
  5) use btmgmt --timeout option for interactive use
  6) Hopefully above will mean there is no need to do sleep 5 either

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/2037534/+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 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs

[de Chalain]

I have the same issue on Ubuntu 23.04 using NVIDIA 470.199.02

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

Title:
  Having a video playing/paused when switched to another user generates
  gigabytes of error logs

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Confirmed

Bug description:
  To replicate:

  1. Start a video playing, for example in vlc. 'avcodec decoder: Using
  NVIDIA VDPAU Driver Shared Library  418.56  Fri Mar 15 12:31:51 CDT
  2019 for hardware decoding'

  2. Optionally pause it.

  3. Switch to another user.

  The original user's ~/.xsession-errors will rapidly fill up with
  errors along the lines of "vdpau_chroma filter error".

  At the same time, errors are put in /var/log/syslog as well:

  [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: 
An invalid handle value was provided.
  (repeat ad nauseum)

  At least one of the two will rapidly fill up its partition and
  problems will arise.

  With AMD video hardware and driver, the video continues playing - you
  can hear the sound despite being in the other user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+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 2038782] Re: linux-firmware halts boot before grub screen on clean install-upgrade to Ubuntu 22.04.3

[Juerg Haefliger]

Which kernel are you running? Can you provide logs from one of those
boots with 3.21?

$ journalctl -b 0 (or -b - for a previous boot)


** Tags removed: verification-failed-jammy

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

Title:
  linux-firmware halts boot before grub screen on clean install-upgrade
  to Ubuntu 22.04.3

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  
  System halts just after filesystem journaling after USB install of LTS Ubuntu 
22.04.2 to Ubuntu 22.04.3, never makes it to grub screen, can't boot system. 

  Another bug report from 2020 says their system gets past grub screen
  and then gets stuck, I don't even make it that far, no other bug
  reports I found seems similar. Since I can't get to grub, I can't
  adjust boot options because it's apparently not going to load the OS.

  I receive no errors. Since the OS isn't loaded, nothing shows up in
  the filesystem logs.

  
  Can CTRL+ALT+DEL reboot, but can't get past journaling and into GRUB.

  
  Since system won't proceed further after journaling completes, apport can't 
start or dump a report.


  
  Steps to Reproduce:
  ---

  * Boot from official USB 22.04.2 USB image made as per Ubuntu instructions 
using Ubuntu bootable disk tool 
  * Accept all installation defaults
  * reboot

  Once rebooted and at 22.04.2 desktop, open terminal and issue:

  * sudo apt update

  (You will be told 340+ packages need to be installed)

  * sudo apt upgrade

  (wait for apt upgrade to complete)

  * reboot

  After rebooting from upgrade, system halts after filesystem journaling
  (which reports filesystem is in a good state on my system), yet system
  will not continue to grub/OS boot options screen despite filesystem
  being OK.

  I left system running at that spot overnight, no change in the AM,
  still stuck at journaling screen.

  Again, journaling reports no errors, computer simply won't boot.


  HOW I VERIFIED:
  ---

  Wiped disk (full overwrite erase)

  Reinstalled as per above

  sudo apt update
  sudo apt-mark hold linux-firmware
  sudo apt upgrade
  reboot

  After above steps, system boots & runs (using same system now to write
  this bug report).

  At this time, the system is as fully patched as I can get it:

  user@myhost:~$ sudo apt list --upgradeable
  [sudo] password for user: 
  Listing... Done
  gjs/jammy-updates 1.72.4-0ubuntu0.22.04.1 amd64 [upgradable from: 
1.72.2-0ubuntu1]
  libgjs0g/jammy-updates 1.72.4-0ubuntu0.22.04.1 amd64 [upgradable from: 
1.72.2-0ubuntu1]
  linux-firmware/jammy-updates,jammy-updates 20220329.git681281e4-0ubuntu3.19 
all [upgradable from: 20220329.git681281e4-0ubuntu3.10]


  
  ADDITIONAL NOTES:
  

  Booting into a stand-alone memory test on the system finds no memory
  faults or errors.

  Video stress-test of all functions (2D, shaders, vector, bump, buffer,
  raytrace etc.) performed on the system prior to running "sudo apt
  upgrade".  No failure, no crash, frame rates on par with public
  benchmarks. Crushed the card at 4K resolution, and also ran it with
  eight 1k instances with no problems. Video card ruled out.

  Replaced hard disk with new disk from different vendor, (even though
  journal finds no errors), problem persisted.

  
  Simply placing a hold on linux-firmware package prevents the problem reliably 
regardless of hardware setup.

  
  System up and stable now across multiple reboots and software installs for 6 
hours and now has full software load, including qemu/kvm.


  
  DIAGNOSTICS
  ---

  user@myhost:~$ sudo lshw -short

  H/W path  Device  Class  Description
  
system System Product Name 
(SKU)
  /0busTUF GAMING B550-PLUS 
WIFI II
  /0/0  memory 64KiB BIOS
  /0/34 memory 64GiB System Memory
  /0/34/0   memory 16GiB DIMM DDR4 
Synchronous Unbuffered (Unregistered) 2400 MHz (0.4 ns)
  /0/34/1   memory 16GiB DIMM DDR4 
Synchronous Unbuffered (Unregistered) 2400 MHz (0.4 ns)
  /0/34/2   memory 16GiB DIMM DDR4 
Synchronous Unbuffered (Unregistered) 2400 MHz (0.4 ns)
  /0/34/3   memory 16GiB DIMM DDR4 
Synchronous Unbuffered (Unregistered) 2400 MHz (0.4 ns)
  /0/37 memory 512KiB L1 cache
  /0/38 memory 4MiB L2 cache
  /0/39 memory 32MiB L3 cache
  /0/3a 

[Kernel-packages] [Bug 2038782] Re: linux-firmware halts boot before grub screen on clean install-upgrade to Ubuntu 22.04.3

[John Patterson]

** Tags added: verification-failed-jammy

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

Title:
  linux-firmware halts boot before grub screen on clean install-upgrade
  to Ubuntu 22.04.3

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  
  System halts just after filesystem journaling after USB install of LTS Ubuntu 
22.04.2 to Ubuntu 22.04.3, never makes it to grub screen, can't boot system. 

  Another bug report from 2020 says their system gets past grub screen
  and then gets stuck, I don't even make it that far, no other bug
  reports I found seems similar. Since I can't get to grub, I can't
  adjust boot options because it's apparently not going to load the OS.

  I receive no errors. Since the OS isn't loaded, nothing shows up in
  the filesystem logs.

  
  Can CTRL+ALT+DEL reboot, but can't get past journaling and into GRUB.

  
  Since system won't proceed further after journaling completes, apport can't 
start or dump a report.


  
  Steps to Reproduce:
  ---

  * Boot from official USB 22.04.2 USB image made as per Ubuntu instructions 
using Ubuntu bootable disk tool 
  * Accept all installation defaults
  * reboot

  Once rebooted and at 22.04.2 desktop, open terminal and issue:

  * sudo apt update

  (You will be told 340+ packages need to be installed)

  * sudo apt upgrade

  (wait for apt upgrade to complete)

  * reboot

  After rebooting from upgrade, system halts after filesystem journaling
  (which reports filesystem is in a good state on my system), yet system
  will not continue to grub/OS boot options screen despite filesystem
  being OK.

  I left system running at that spot overnight, no change in the AM,
  still stuck at journaling screen.

  Again, journaling reports no errors, computer simply won't boot.


  HOW I VERIFIED:
  ---

  Wiped disk (full overwrite erase)

  Reinstalled as per above

  sudo apt update
  sudo apt-mark hold linux-firmware
  sudo apt upgrade
  reboot

  After above steps, system boots & runs (using same system now to write
  this bug report).

  At this time, the system is as fully patched as I can get it:

  user@myhost:~$ sudo apt list --upgradeable
  [sudo] password for user: 
  Listing... Done
  gjs/jammy-updates 1.72.4-0ubuntu0.22.04.1 amd64 [upgradable from: 
1.72.2-0ubuntu1]
  libgjs0g/jammy-updates 1.72.4-0ubuntu0.22.04.1 amd64 [upgradable from: 
1.72.2-0ubuntu1]
  linux-firmware/jammy-updates,jammy-updates 20220329.git681281e4-0ubuntu3.19 
all [upgradable from: 20220329.git681281e4-0ubuntu3.10]


  
  ADDITIONAL NOTES:
  

  Booting into a stand-alone memory test on the system finds no memory
  faults or errors.

  Video stress-test of all functions (2D, shaders, vector, bump, buffer,
  raytrace etc.) performed on the system prior to running "sudo apt
  upgrade".  No failure, no crash, frame rates on par with public
  benchmarks. Crushed the card at 4K resolution, and also ran it with
  eight 1k instances with no problems. Video card ruled out.

  Replaced hard disk with new disk from different vendor, (even though
  journal finds no errors), problem persisted.

  
  Simply placing a hold on linux-firmware package prevents the problem reliably 
regardless of hardware setup.

  
  System up and stable now across multiple reboots and software installs for 6 
hours and now has full software load, including qemu/kvm.


  
  DIAGNOSTICS
  ---

  user@myhost:~$ sudo lshw -short

  H/W path  Device  Class  Description
  
system System Product Name 
(SKU)
  /0busTUF GAMING B550-PLUS 
WIFI II
  /0/0  memory 64KiB BIOS
  /0/34 memory 64GiB System Memory
  /0/34/0   memory 16GiB DIMM DDR4 
Synchronous Unbuffered (Unregistered) 2400 MHz (0.4 ns)
  /0/34/1   memory 16GiB DIMM DDR4 
Synchronous Unbuffered (Unregistered) 2400 MHz (0.4 ns)
  /0/34/2   memory 16GiB DIMM DDR4 
Synchronous Unbuffered (Unregistered) 2400 MHz (0.4 ns)
  /0/34/3   memory 16GiB DIMM DDR4 
Synchronous Unbuffered (Unregistered) 2400 MHz (0.4 ns)
  /0/37 memory 512KiB L1 cache
  /0/38 memory 4MiB L2 cache
  /0/39 memory 32MiB L3 cache
  /0/3a processor  AMD Ryzen 7 5800X 
8-Core Processor
  /0/100bridge Starship/Matisse 
Root 

[Kernel-packages] [Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

[Thadeu Lima de Souza Cascardo]

Upstream commit b0ad3c179059089d809b477a1d445c1183a7b8fe ("rtnetlink:
call validate_linkmsg in rtnl_create_link") sounds like a good candidate
as the culprit here. I see no fixes referencing it upstream, though.

-- 
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 linux source package in Jammy:
  Confirmed

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 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

[Łukasz Zemczak]

** Tags added: kernel-bug regression-update

-- 
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 linux source package in Jammy:
  Confirmed

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 2028830] Re: [mpt3sas, UBSAN] ]linux 6.5-rc give error messages at boot

[koba]

@Keeley, please check the comments from here
https://lore.kernel.org/lkml/202310101748.5E39C3A@keescook/

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

Title:
  [mpt3sas, UBSAN] ]linux 6.5-rc give error messages at boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu release:

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

  Package:

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

  Expectation: System boots normally

  Actual results: See below

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

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

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

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

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

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

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

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

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

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

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

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

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

  [EDIT] the next error, repeating for ~1½ hours before finishing boot,
  was unrelated to mpt2sas and UBSAN.

  That error was "Timed out for waiting the udey queue being empty."

  Bug subject altered to reflect this.

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


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

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

[Timo Aaltonen]

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

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

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 2019000] Re: Use new annotations model

[Thibf]

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

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

** Changed in: linux-kvm (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: linux-kvm (Ubuntu Focal)
 Assignee: (unassigned) => Thibf (thibf)

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

Title:
  Use new annotations model

Status in linux package in Ubuntu:
  Invalid
Status in linux-gcp package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Focal:
  Fix Committed
Status in linux-gcp source package in Focal:
  New
Status in linux-kvm source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Released
Status in linux-gcp source package in Jammy:
  Fix Released
Status in linux-kvm source package in Jammy:
  New
Status in linux source package in Kinetic:
  Confirmed
Status in linux-gcp source package in Kinetic:
  Invalid
Status in linux-kvm source package in Kinetic:
  Invalid

Bug description:
  [Impact]

  Starting with lunar we have introduced a new way to manage kernel
  configs, unifying the duplicated information defined in the
  annotations file + config chunks into an annotations-only model.

  [Test case]

  A kernel build can be considered a valid test case, in particular the
  specific command that is used to update the .config's for all the
  supported architectures and flavours:

   $ fakeroot debian/rules updateconfigs

  [Fix]

  Import the required changes in debian/ from lunar (with the required
  adjustments) to support the annotations-only model also in all the
  previous releases.

  [Regression potential]

  We may experience regressions during the updateconfigs step,
  especially with derivatives. Moreover, derivatives that want to
  transition to the new annotations model require to adjust the header
  in the annotations file as following (make sure to define the
  corresponding architectures and flavours):

  # FORMAT: 4
  # ARCH: amd64 arm64 armhf ppc64el s390x
  # FLAVOUR: amd64-generic amd64-lowlatency arm64-generic arm64-generic-64k 
arm64-lowlatency arm64-lowlatency-64k armhf-generic armhf-generic-lpae 
ppc64el-generic s390x-generic

  After adjusting the header a special command is provided to transition
  to the new annotations-only model:

   $ fakeroot debian/rules migrateconfigs

  This command should automatically import the old configs into the new
  annotations file.

  A kernel with this change applied can still support the old
  annotations+configs model, the transition to the new model is not
  mandatory.

  Basically without using `fakeroot debian/rules migrateconfigs` the
  updateconfigs step will continue to use the old model and the old
  scripts (that is the safest approach to avoid potential unexpected
  .config changes).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019000/+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 1975501] Re: bfq_deactivate_entity: NULL pointer dereference

[alexey]

Hello!
Problem still appear on 5.4.0-150 kernel version!

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

Title:
  bfq_deactivate_entity: NULL pointer dereference

Status in linux-hwe package in Ubuntu:
  New

Bug description:
  Hello. We meet a kernel panic with next trace:

  bfq_insert+0x5c/0x70 [bfq]
  __bfq_deactivate_entity+0xe7/0x1b0 [bfq]
  bfq_deactivate_entity+0x5d/0xd0 [bfq]
  bfq_del_bfqq_busy+0xac/0x150 [bfq]
  __bfq_bfqq_expire+0x64/0xd0 [bfq]
  bfq_bfqq_expire+0x331/0x930 [bfq]
  ? try_to_wake_up+0x235/0x5f0
  ? bfq_dispatch_request+0xf70/0xf70 [bfq]
  bfq_idle_slice_timer+0x6d/0xc0 [bfq]
  __hrtimer_run_queues+0x10f/0x280
  hrtimer_interrupt+0xe7/0x230
  smp_apic_timer_interrupt+0x6f/0x130
  apic_timer_interrupt+0xf/0x20

  After little research i found out that bug was reported by Fedora and 
openSUSE community earlier.
  https://bugzilla.redhat.com/show_bug.cgi?id=2022819
  https://bugzilla.opensuse.org/show_bug.cgi?id=1192714

  And patch for this bug already exist
  https://lore.kernel.org/all/20220401102325.17617-1-j...@suse.cz/

  Since there are no similar reports in the Ubuntu community, I decided to make 
this report.
  Full dmesg log in attachments.
  Also have a crash dump file, can attach that file if it necessary. 

  

  Environment:
Distributor ID: Ubuntu
Description: Ubuntu 18.04.6 LTS
Release: 18.04
Codename: bionic
kernel: 5.4.0-110-generic #124~18.04.1-Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1975501/+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 1987190] Re: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1

[Walter]

And, step 3 should be:

=== Step 3: confirm that the module is loaded ===

# cat /sys/module/zfs/version 
2.1.5-1ubuntu6~22.04.1+ossomacfix


=== Summarizing for 2.1.5 ===
```
cd /tmp

wget https://bugs.launchpad.net/ubuntu/+source/zfs-
linux/+bug/1987190/+attachment/5704587/+files/zfs-dkms-2.1.5-1-fix-zero-
mac-io-error.patch

apt-get install zfs-dkms

dkms remove -m zfs -v 2.1.5 -k $(uname -r)

dkms status

cd /usr/src/zfs-2.1.5

patch -p1 < /tmp/zfs-dkms-2.1.5-1-fix-zero-mac-io-error.patch

dkms install -m zfs -v 2.1.5 -k $(uname -r)

update-initramfs -uk $(uname -r)

#reboot
```

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

Title:
  ZFS unrecoverable error after upgrading from 20.04 to 22.04.1

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  I have a server that has been running its data volume using ZFS in
  20.04 without any problem. The volume is using ZFS encryption and a
  raidz1-0 configuration. I performed a scrub operations before the
  upgrade and it did not find any problem. After the reboot for the
  upgrade, I was welcomed with the following message:

  status: One or more devices has experienced an error resulting in data
  corruption.  Applications may be affected.
  action: Restore the file in question if possible.  Otherwise restore the
  entire pool from backup.
 see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A

  The volumes still do not have any checksum error but there are 5 zvols
  that are not accessible. zpool status displays a line similar to the
  below for each of the five:

  errors: Permanent errors have been detected in the following files:   



  tank/data/data:<0x0>

  I run a scrub and it has not identified any problem but the error
  messages are not there and the data is still not available. There are
  10+ other zvols in the zpool that do not have any kind of problem. I
  have been unable to identify any correlation between the zvols that
  are failing.

  I have seen people reporting similar problems in github after the
  20.04 to the 22.04 upgrade (see
  https://github.com/openzfs/zfs/issues/13763). I wonder how widespread
  the problem will be as more people upgrades to 22.04.

  I will try to downgrade the version of zfs in the system and report
  back

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: zfsutils-linux 2.1.4-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sat Aug 20 22:24:54 2022
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to jammy on 2022-08-20 (0 days ago)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1987190/+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 2038928] Re: Unable to handle kernel paging request at virtual address ffffff8a012abe1a

[Heinrich Schuchardt]

With u-boot-starfive - 2023.09.22-next-5d2fae79c7d6-0ubuntu1~ppa4 from
ppa:ubuntu-risc-v-team/release the problem is resolved.

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

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

Title:
  Unable to handle kernel paging request at virtual address
  ff8a012abe1a

Status in linux-riscv package in Ubuntu:
  Invalid

Bug description:
  I have been running the Mantic preinstalled image on the VisionFive 2 1.3B 
board.
  
http://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/20231010/mantic-preinstalled-server-riscv64+visionfive2.img.xz

  Kernel Ubuntu 6.5.0-9.9.1-generic 6.5.3

  [ 4050.418337] Unable to handle kernel paging request at virtual address 
ffb4fffc
  [ 4050.426326] Oops [#1]
  [ 4050.428601] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 
cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart 
snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd 
snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore 
uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables 
autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core 
dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c 
clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc 
pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common 
clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi
  [ 4050.503975] CPU: 1 PID: 1866 Comm: check-new-relea Not tainted 
6.5.0-9-generic #9.1-Ubuntu
  [ 4050.512235] Hardware name: StarFive VisionFive 2 v1.3B (DT)
  [ 4050.517804] epc : __d_lookup_rcu+0x4a/0x100
  [ 4050.521997]  ra : lookup_fast+0x36/0xfc
  [ 4050.525837] epc : 80315146 ra : 803042bc sp : 
ffc800a6bab0
  [ 4050.533056]  gp : 822602d8 tp : ffd8c56ea880 t0 : 
ffc800a6bce8
  [ 4050.540279]  t1 :  t2 : 812002e8 s0 : 
ffc800a6bae0
  [ 4050.547502]  s1 : ffc800a6bc00 a0 : ffd8c9fd8a80 a1 : 
ffc800a6bc10
  m[ 4050.554810]  a2 : ffc800a6bc44 a3 : 0001 a4 : 
00015635
  [ 4050.562033]  a5 : 00015635 a6 : 00035238 a7 : 

  [ 4050.569254]  s2 : 0002 s3 : ffd8c9fd8a80 s4 : 
002e
  [ 4050.576476]  s5 : 0020 s6 : 0070 s7 : 
fff6
  [ 4050.583697]  s8 : 0002 s9 : ffd8ca244025 s10: 
ffc800a6bc00
  [ 4050.590918]  s11: 002f t3 : ffd8c9fd8a80 t4 : 
000335238e2d
  [ 4050.598141]  t5 : ffc800a6bc44 t6 : ffd8ca244021
  [ 4050.603452] status: 00020120 badaddr: ffb4fffc cause: 
000d
  [ 4050.611367] [] __d_lookup_rcu+0x4a/0x100
  [ 4050.616858] [] walk_component+0x26/0x194
  [ 4050.622348] [] 
link_path_walk.part.0.constprop.0+0x1c2/0x2c2
  [ 4050.629575] [] path_parentat+0x48/0x96
  [ 4050.634890] [] __filename_parentat+0x9e/0x188
  [ 4050.640813] [] do_renameat2+0xc8/0x4e2
  [ 4050.646128] [] sys_renameat2+0x5a/0x76
  [ 4050.651441] [] do_trap_ecall_u+0xd6/0x154
  [ 4050.657018] [] ret_from_exception+0x0/0x64
  [ 4050.662691] Code: 4685 8e2a 8f32 7793 ffe7 e563 00e6 a885 639c c7b5 (a703) 
ffc7 
  [ 4050.670148] ---[ end trace  ]---
  [ 4050.670271] Unable to handle kernel paging request at virtual address 
005dfffc
  [ 4050.670360] Unable to handle kernel paging request at virtual address 
ffb4fffc
  [ 4050.670368] Oops [#2]
  [ 4050.670371] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 
cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart 
snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd 
snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore 
uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables 
autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core 
dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c 
clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc 
pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common 
clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi
  [ 4050.670556] CPU: 3 PID: 788 Comm: rs:main Q:Reg Tainted: G  D  
  6.5.0-9-generic #9.1-Ubuntu
  [ 4050.670562] Hardware name: StarFive VisionFive 2 v1.3B (DT)
  [ 4050.670565] epc : __d_lookup_rcu+0x4a/0x100
  [ 4050.670574]  ra : lookup_fast+0x36/0xfc
  [ 4050.670582] 

[Kernel-packages] [Bug 2039039] [NEW] [Dell ] Call trace are observed in dmesg for UBUNTU 22.04.3 OS using H355 Perc on Poweredge system

[Chaitra Kengar]

Private bug reported:

Steps to repro:
1) Installed UBUNTU 22.04.3 OS
2) After the successful installation of OS, checked for dmesg logs.
3) Ran the command "dmesg -T | grep -i RIP" where RIP errors are observed.

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

** Information type changed from Public to Private

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

Title:
  [Dell ] Call trace are observed in dmesg for UBUNTU 22.04.3 OS using
  H355 Perc on Poweredge system

Status in linux package in Ubuntu:
  New

Bug description:
  Steps to repro:
  1) Installed UBUNTU 22.04.3 OS
  2) After the successful installation of OS, checked for dmesg logs.
  3) Ran the command "dmesg -T | grep -i RIP" where RIP errors are observed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039039/+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 2038920] Re: Nezha D1: usb 1-1: device descriptor read/64, error -71

[Heinrich Schuchardt]

** Summary changed:

- Nezahl D1: usb 1-1: device descriptor read/64, error -71
+ Nezha D1: usb 1-1: device descriptor read/64, error -71

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

Title:
  Nezha D1: usb 1-1: device descriptor read/64, error -71

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  On the Nezha D1 board USB does not work correctly.

  I have connected a USB keyboard and get errors like:

  [ 4458.313671] usb 1-1: device descriptor read/64, error -71
  [ 4459.189686] usb 1-1: device descriptor read/64, error -71
  [ 4460.157594] usb 4-1: device descriptor read/64, error -62
  [ 4460.461621] usb 4-1: device descriptor read/64, error -62
  [ 4460.953646] usb 4-1: device descriptor read/64, error -62
  [ 4461.257626] usb 4-1: device descriptor read/64, error -62

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20231010
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue Oct 10 12:20:40 2023
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

[Endre Olah]

According to the Kernel list 6.5 is the latest available/official, but
even that was not solving the problem.

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

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

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  Hello.

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

  Regards,
  Pradip Kumar Das

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

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


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

[Kernel-packages] [Bug 2038920] Re: Nezahl D1: usb 1-1: device descriptor read/64, error -71

[Utkarsh Gupta]

** Changed in: linux-riscv (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Nezahl D1: usb 1-1: device descriptor read/64, error -71

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  On the Nezha D1 board USB does not work correctly.

  I have connected a USB keyboard and get errors like:

  [ 4458.313671] usb 1-1: device descriptor read/64, error -71
  [ 4459.189686] usb 1-1: device descriptor read/64, error -71
  [ 4460.157594] usb 4-1: device descriptor read/64, error -62
  [ 4460.461621] usb 4-1: device descriptor read/64, error -62
  [ 4460.953646] usb 4-1: device descriptor read/64, error -62
  [ 4461.257626] usb 4-1: device descriptor read/64, error -62

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20231010
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue Oct 10 12:20:40 2023
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2038920/+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 2038893] Re: probe-bcache[132]: unhandled signal 11 code 0x1 at 0x0038004000000004

[Utkarsh Gupta]

** Changed in: bcache-tools (Ubuntu)
   Importance: Undecided => Low

** Changed in: linux-riscv (Ubuntu)
   Importance: Undecided => Low

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

Title:
  probe-bcache[132]: unhandled signal 11 code 0x1 at 0x00380044

Status in bcache-tools package in Ubuntu:
  New
Status in linux-riscv package in Ubuntu:
  New

Bug description:
  Running http://cdimage.ubuntu.com/ubuntu-server/daily-
  preinstalled/20231010/mantic-preinstalled-server-riscv64.img.xz on
  QEMU with

  qemu-system-riscv64 -machine virt -nographic -m 2048 -smp 4 -bios
  /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel
  /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf -device virtio-net-
  device,netdev=eth0 -netdev user,id=eth0 -device virtio-rng-pci -drive
  file=mantic-preinstalled-server-riscv64.img,format=raw,if=virtio

  a crash was reported:

  Starting systemd-udevd version 253.5-1ubuntu6
  [3.919909] probe-bcache[132]: unhandled signal 11 code 0x1 at 
0x00380044
  [3.920554] CPU: 3 PID: 132 Comm: probe-bcache Not tainted 6.5.0-9-generic 
#9.1-Ubuntu
  [3.921064] Hardware name: riscv-virtio,qemu (DT)
  [3.921382] epc : 00380044 ra : 7fffadf8ac82 sp : 
7fffce174160
  [3.921750]  gp : 5fd56800 tp : 7fffade18780 t0 : 
1000
  [3.922110]  t1 : 5fd53a3c t2 : 0034e6b4 s0 : 
7fffae006ae0
  [3.922422]  s1 : 7fffce174c78 a0 : 7fffce174178 a1 : 
7fffae006ae0
  [3.922751]  a2 : 00022560 a3 : 7fff a4 : 

  [3.923121]  a5 : 00380045 a6 : 0007d436 a7 : 
001d
  [3.923576]  s2 : 0001 s3 : 7fffae005d80 s4 : 
0003
  [3.923913]  s5 : 7d4352a0 s6 :  s7 : 
7fffce174160
  [3.924251]  s8 : 7fffce174a30 s9 : 7fffadfb86f0 s10: 
7fffce174178
  [3.924585]  s11: 7fffce174188 t3 : 7fffadf8abe8 t4 : 

  [3.924897]  t5 : 7fffadfdda40 t6 : 7fffadfde028
  [3.925090] status: 00024020 badaddr: 00380044 cause: 
000c
  [3.933878] probe-bcache[130]: unhandled signal 11 code 0x1 at 
0x00380044
  [3.934386] CPU: 1 PID: 130 Comm: probe-bcache Not tainted 6.5.0-9-generic 
#9.1-Ubuntu
  [3.934742] Hardware name: riscv-virtio,qemu (DT)
  [3.934974] epc : 00380044 ra : 7fff9b9acc82 sp : 
7fffe3a88160
  [3.935316]  gp : 91f30800 tp : 7fff9b83a780 t0 : 
1000
  [3.935869]  t1 : 91f2da3c t2 : 0034e6b4 s0 : 
7fff9ba28ae0
  [3.936224]  s1 : 7fffe3a88c78 a0 : 7fffe3a88178 a1 : 
7fff9ba28ae0
  [3.936606]  a2 : 00022560 a3 : 7fff a4 : 

  [3.937030]  a5 : 00380045 a6 : 000b3fa0 a7 : 
001d
  [3.937443]  s2 : 0001 s3 : 7fff9ba27d80 s4 : 
0003
  [3.937868]  s5 : b3f9f2a0 s6 :  s7 : 
7fffe3a88160
  [3.938261]  s8 : 7fffe3a88a30 s9 : 7fff9b9da6f0 s10: 
7fffe3a88178
  [3.938681]  s11: 7fffe3a88188 t3 : 7fff9b9acbe8 t4 : 

  [3.939113]  t5 : 7fff9b9ffa40 t6 : 7fff9ba00028
  [3.939469] status: 00024020 badaddr: 00380044 cause: 
000c
  [3.951861] probe-bcache[129]: unhandled signal 11 code 0x1 at 
0x00380044
  [3.952290] CPU: 0 PID: 129 Comm: probe-bcache Not tainted 6.5.0-9-generic 
#9.1-Ubuntu
  [3.952680] Hardware name: riscv-virtio,qemu (DT)
  [3.952887] epc : 00380044 ra : 7fff86598c82 sp : 
7fffea625160
  [3.953236]  gp : 74eb1800 tp : 7fff86426780 t0 : 
1000
  [3.953582]  t1 : 74eaea3c t2 : 0034e6b4 s0 : 
7fff86614ae0
  [3.953936]  s1 : 7fffea625c78 a0 : 7fffea625178 a1 : 
7fff86614ae0
  [3.954302]  a2 : 00022560 a3 : 7fff a4 : 

  [3.954700]  a5 : 00380045 a6 : 0009411b a7 : 
001d
  [3.955114]  s2 : 0001 s3 : 7fff86613d80 s4 : 
0003
  [3.955657]  s5 : 9411a2a0 s6 :  s7 : 
7fffea625160
  [3.956018]  s8 : 7fffea625a30 s9 : 7fff865c66f0 s10: 
7fffea625178
  [3.956368]  s11: 7fffea625188 t3 : 7fff86598be8 t4 : 

  [3.956741]  t5 : 7fff865eba40 t6 : 7fff865ec028
  [3.957026] status: 00024020 badaddr: 00380044 cause: 
000c
  Begin: Loading essential drivers ... [6.255484] raid6: int64x8  gen()   
635 MB/s

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 

[Kernel-packages] [Bug 2028830] Re: [mpt3sas, UBSAN] ]linux 6.5-rc give error messages at boot

[Keeley Hoek]

I have just upgraded to 23.10 beta and have a large number of these
spammed to the console. Does that patch fix the problem? Is there any
more information you need?/why didn't that patch go into Linux 6.5?

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

Title:
  [mpt3sas, UBSAN] ]linux 6.5-rc give error messages at boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu release:

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

  Package:

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

  Expectation: System boots normally

  Actual results: See below

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

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

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

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

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

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

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

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

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

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

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

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

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

  [EDIT] the next error, repeating for ~1½ hours before finishing boot,
  was unrelated to mpt2sas and UBSAN.

  That error was "Timed out for waiting the udey queue being empty."

  Bug subject altered to reflect this.

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


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

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

[AceLan Kao]

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

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

** Changed in: linux-oem-6.1 (Ubuntu Jammy)
 Assignee: (unassigned) => AceLan Kao (acelankao)

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

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

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 2038942] Re: [MIR] protection-domain-mapper & qrtr

[Łukasz Zemczak]

I have promoted both packages to main:

$ change-override -S -s mantic -c main protection-domain-mapper
Override component to main
protection-domain-mapper 1.0-4ubuntu2 in mantic: universe/misc -> main
protection-domain-mapper 1.0-4ubuntu2 in mantic amd64: 
universe/net/optional/100% -> main
protection-domain-mapper 1.0-4ubuntu2 in mantic arm64: 
universe/net/optional/100% -> main
protection-domain-mapper 1.0-4ubuntu2 in mantic armhf: 
universe/net/optional/100% -> main
protection-domain-mapper 1.0-4ubuntu2 in mantic ppc64el: 
universe/net/optional/100% -> main
protection-domain-mapper 1.0-4ubuntu2 in mantic riscv64: 
universe/net/optional/100% -> main
protection-domain-mapper 1.0-4ubuntu2 in mantic s390x: 
universe/net/optional/100% -> main
Override [y|N]? y
7 publications overridden.

$ change-override -S -s mantic -c main qrtr
Override component to main
qrtr 1.0-2ubuntu1 in mantic: universe/misc -> main
libqrtr-dev 1.0-2ubuntu1 in mantic amd64: universe/libdevel/optional/100% -> 
main
libqrtr-dev 1.0-2ubuntu1 in mantic arm64: universe/libdevel/optional/100% -> 
main
libqrtr-dev 1.0-2ubuntu1 in mantic armhf: universe/libdevel/optional/100% -> 
main
libqrtr-dev 1.0-2ubuntu1 in mantic ppc64el: universe/libdevel/optional/100% -> 
main
libqrtr-dev 1.0-2ubuntu1 in mantic riscv64: universe/libdevel/optional/100% -> 
main
libqrtr-dev 1.0-2ubuntu1 in mantic s390x: universe/libdevel/optional/100% -> 
main
libqrtr1 1.0-2ubuntu1 in mantic amd64: universe/libs/optional/100% -> main
libqrtr1 1.0-2ubuntu1 in mantic arm64: universe/libs/optional/100% -> main
libqrtr1 1.0-2ubuntu1 in mantic armhf: universe/libs/optional/100% -> main
libqrtr1 1.0-2ubuntu1 in mantic ppc64el: universe/libs/optional/100% -> main
libqrtr1 1.0-2ubuntu1 in mantic riscv64: universe/libs/optional/100% -> main
libqrtr1 1.0-2ubuntu1 in mantic s390x: universe/libs/optional/100% -> main
qrtr-tools 1.0-2ubuntu1 in mantic amd64: universe/net/optional/100% -> main
qrtr-tools 1.0-2ubuntu1 in mantic arm64: universe/net/optional/100% -> main
qrtr-tools 1.0-2ubuntu1 in mantic armhf: universe/net/optional/100% -> main
qrtr-tools 1.0-2ubuntu1 in mantic ppc64el: universe/net/optional/100% -> main
qrtr-tools 1.0-2ubuntu1 in mantic riscv64: universe/net/optional/100% -> main
qrtr-tools 1.0-2ubuntu1 in mantic s390x: universe/net/optional/100% -> main
Override [y|N]? y
19 publications overridden.

** Changed in: protection-domain-mapper (Ubuntu)
   Status: Fix Committed => Fix Released

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

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

Title:
  [MIR] protection-domain-mapper & qrtr

Status in protection-domain-mapper package in Ubuntu:
  Fix Released
Status in qrtr package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
  The package protection-domain-mapper is already in Ubuntu universe.
  The package protection-domain-mapper build for the architectures it is 
designed to work on.
  It currently builds and works for architectures: any, verified as working on 
arm64
  Link to package https://launchpad.net/ubuntu/+source/protection-domain-mapper

  [Rationale]

  - The package protection-domain-mapper is required in Ubuntu main for
    ubuntu-desktop on ARM64, as it enables power-indicator (among other
    things) on most Windows on Arm laptops (qcom based laptops ~7 SKUs
    and more coming). There is no other way to implement this.

  - protection-domain-mapper depends on qrtr for library and a systemd
    service it provides.

  - There is no other/better way to solve this that is already in main
    or should go universe->main instead of this. As this is the only
    implementation of talking to the qcom hardware.

  - The package protection-domain-mapper is required in Ubuntu main no
    later than today due to Mantic release, if we want to have the best
    impression of Ubuntu Desktop in the live session on x13s.

  - If that fails, having it fixed as SRU is the next best option.

  [Security]

  - No CVEs/security issues in this software in the past. This is a
    reference open source implementation of these tools, which otherwise
    are used on qcom Android devices

  - no `suid` or `sgid` binaries no executables in `/sbin` and
    `/usr/sbin`

  - Package does install services: pd-mapper.service & qrtr-ns.service
    which allow runtime access to the qcom hardware which are run as
    root

  - Security has been kept in mind and common isolation/risk-mitigation
  patterns are in place utilizing the following features:

  - Packages does not open privileged ports (ports < 1024).

  - Package does not expose any external endpoints

  - Packages does not contain extensions to security-sensitive software
    (filters, scanners, plugins, UI skins, ...)

  [Quality assurance - function/usage]

  - The package works well right after install, i.e. power 

[Kernel-packages] [Bug 2039010] Missing required logs.

[Ubuntu Kernel Bot]

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

apport-collect 2039010

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

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

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

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

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

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

Title:
  revert support for arbitrary symbol length in modversion in hwe
  kernels

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

Bug description:
  The following patch may break user-space, providing an actual ABI
  change:

UBUNTU: SAUCE: modpost: support arbitrary symbol length in
  modversion

  This is not critical for new releases (also considering that the
  potential breakage is unlikely to happen, unless some
  tools/scripts/apps are inspecting modules' internals - likely only
  kmod tools, that are ok with this change), but for LTS releases it is
  just safer to prevent adding this change.

  Keep in mind that this patch is required to enable Rust support in the
  generic kernel, but it is not required for hwe kernels, because we do
  not enable Rust support for them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039010/+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 2038928] Re: Unable to handle kernel paging request at virtual address ffffff8a012abe1a

[Brian Murray]

Setting to Incomplete pending the results of the testing in comment #6.

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

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

Title:
  Unable to handle kernel paging request at virtual address
  ff8a012abe1a

Status in linux-riscv package in Ubuntu:
  Incomplete

Bug description:
  I have been running the Mantic preinstalled image on the VisionFive 2 1.3B 
board.
  
http://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/20231010/mantic-preinstalled-server-riscv64+visionfive2.img.xz

  Kernel Ubuntu 6.5.0-9.9.1-generic 6.5.3

  [ 4050.418337] Unable to handle kernel paging request at virtual address 
ffb4fffc
  [ 4050.426326] Oops [#1]
  [ 4050.428601] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 
cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart 
snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd 
snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore 
uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables 
autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core 
dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c 
clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc 
pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common 
clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi
  [ 4050.503975] CPU: 1 PID: 1866 Comm: check-new-relea Not tainted 
6.5.0-9-generic #9.1-Ubuntu
  [ 4050.512235] Hardware name: StarFive VisionFive 2 v1.3B (DT)
  [ 4050.517804] epc : __d_lookup_rcu+0x4a/0x100
  [ 4050.521997]  ra : lookup_fast+0x36/0xfc
  [ 4050.525837] epc : 80315146 ra : 803042bc sp : 
ffc800a6bab0
  [ 4050.533056]  gp : 822602d8 tp : ffd8c56ea880 t0 : 
ffc800a6bce8
  [ 4050.540279]  t1 :  t2 : 812002e8 s0 : 
ffc800a6bae0
  [ 4050.547502]  s1 : ffc800a6bc00 a0 : ffd8c9fd8a80 a1 : 
ffc800a6bc10
  m[ 4050.554810]  a2 : ffc800a6bc44 a3 : 0001 a4 : 
00015635
  [ 4050.562033]  a5 : 00015635 a6 : 00035238 a7 : 

  [ 4050.569254]  s2 : 0002 s3 : ffd8c9fd8a80 s4 : 
002e
  [ 4050.576476]  s5 : 0020 s6 : 0070 s7 : 
fff6
  [ 4050.583697]  s8 : 0002 s9 : ffd8ca244025 s10: 
ffc800a6bc00
  [ 4050.590918]  s11: 002f t3 : ffd8c9fd8a80 t4 : 
000335238e2d
  [ 4050.598141]  t5 : ffc800a6bc44 t6 : ffd8ca244021
  [ 4050.603452] status: 00020120 badaddr: ffb4fffc cause: 
000d
  [ 4050.611367] [] __d_lookup_rcu+0x4a/0x100
  [ 4050.616858] [] walk_component+0x26/0x194
  [ 4050.622348] [] 
link_path_walk.part.0.constprop.0+0x1c2/0x2c2
  [ 4050.629575] [] path_parentat+0x48/0x96
  [ 4050.634890] [] __filename_parentat+0x9e/0x188
  [ 4050.640813] [] do_renameat2+0xc8/0x4e2
  [ 4050.646128] [] sys_renameat2+0x5a/0x76
  [ 4050.651441] [] do_trap_ecall_u+0xd6/0x154
  [ 4050.657018] [] ret_from_exception+0x0/0x64
  [ 4050.662691] Code: 4685 8e2a 8f32 7793 ffe7 e563 00e6 a885 639c c7b5 (a703) 
ffc7 
  [ 4050.670148] ---[ end trace  ]---
  [ 4050.670271] Unable to handle kernel paging request at virtual address 
005dfffc
  [ 4050.670360] Unable to handle kernel paging request at virtual address 
ffb4fffc
  [ 4050.670368] Oops [#2]
  [ 4050.670371] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 
cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart 
snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd 
snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore 
uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables 
autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core 
dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c 
clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc 
pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common 
clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi
  [ 4050.670556] CPU: 3 PID: 788 Comm: rs:main Q:Reg Tainted: G  D  
  6.5.0-9-generic #9.1-Ubuntu
  [ 4050.670562] Hardware name: StarFive VisionFive 2 v1.3B (DT)
  [ 4050.670565] epc : __d_lookup_rcu+0x4a/0x100
  [ 4050.670574]  ra : lookup_fast+0x36/0xfc
  [ 4050.670582] epc : 80315146 ra : 803042bc sp : 

Re: [Kernel-packages] [Bug 2038436] Re: System doesnt recognize second monitor

[MUHAMMAD HATTA BIN MUHAMMAD PAUZI]

Hello, can i get at least a reply... I need to know as this monitor needed
to be somewhere

On Mon, Oct 9, 2023, 10:01 PM Muhammad Hatta 
wrote:

> Glad to help, so is it fixed in the next update? or i need to do it
> manually
>
> On Mon, Oct 9, 2023, 5:30 PM Daniel van Vugt <2038...@bugs.launchpad.net>
> wrote:
>
>> Thanks. That confirms it's the kernel not detecting the monitor.
>>
>> ** Package changed: ubuntu => linux-hwe-6.2 (Ubuntu)
>>
>> ** Changed in: linux-hwe-6.2 (Ubuntu)
>>Status: Incomplete => New
>>
>> ** Summary changed:
>>
>> - System doesnt recognize second monitor
>> + [i915] System doesn't recognize second monitor
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/2038436
>>
>> Title:
>>   [i915] System doesn't recognize second monitor
>>
>> Status in linux-hwe-6.2 package in Ubuntu:
>>   New
>>
>> Bug description:
>>   I am using an old monitor which using a DVI connectors but I used a
>>   DVI to HDMI adapter which works fine on Windows operating system... My
>>   monitor is HP W2072a... I hope with the information provided helps...
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 22.04
>>   Package: xorg 1:7.7+23ubuntu2
>>   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.20.11-0ubuntu82.5
>>   Architecture: amd64
>>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>>   CasperMD5CheckResult: pass
>>   CompositorRunning: None
>>   CurrentDesktop: ubuntu:GNOME
>>   Date: Wed Oct  4 21:17:37 2023
>>   DistUpgraded: Fresh install
>>   DistroCodename: jammy
>>   DistroVariant: ubuntu
>>   ExtraDebuggingInterest: Yes, if not too technical
>>   GraphicsCard:
>>Intel Corporation Alder Lake-P Integrated Graphics Controller
>> [8086:46a6] (rev 0c) (prog-if 00 [VGA controller])
>>  Subsystem: Device [1b50:1018]
>>   InstallationDate: Installed on 2023-09-30 (3 days ago)
>>   InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
>> (20230807.2)
>>   MachineType: ILLEGEAR SDN BHD ATOMIC 16
>>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic
>> root=UUID=e60cc65c-b597-415b-b294-3cb6a76ecbd0 ro quiet splash vt.handoff=7
>>   SourcePackage: xorg
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>   dmi.bios.date: 07/26/2022
>>   dmi.bios.release: 0.2
>>   dmi.bios.vendor: American Megatrends Inc.
>>   dmi.bios.version: Q3AIL.02
>>   dmi.board.asset.tag: Default string be filled by O.E.M
>>   dmi.board.name: ATOMIC
>>   dmi.board.vendor: ILLEGEAR SDN BHD
>>   dmi.board.version: Default string be filled by O.E.M
>>   dmi.chassis.asset.tag: Default string be filled by O.E.M
>>   dmi.chassis.type: 9
>>   dmi.chassis.vendor: Default string be filled by O.E.M
>>   dmi.chassis.version: Default string be filled by O.E.M
>>   dmi.modalias:
>> dmi:bvnAmericanMegatrendsInc.:bvrQ3AIL.02:bd07/26/2022:br0.2:svnILLEGEARSDNBHD:pnATOMIC16:pvrDefaultstringbefilledbyO.E.M:rvnILLEGEARSDNBHD:rnATOMIC:rvrDefaultstringbefilledbyO.E.M:cvnDefaultstringbefilledbyO.E.M:ct9:cvrDefaultstringbefilledbyO.E.M:skuATOMIC16-ADL1:
>>   dmi.product.family: ATOMIC
>>   dmi.product.name: ATOMIC 16
>>   dmi.product.sku: ATOMIC16-ADL1
>>   dmi.product.version: Default string be filled by O.E.M
>>   dmi.sys.vendor: ILLEGEAR SDN BHD
>>   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.1
>>   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.2/+bug/2038436/+subscriptions
>>
>>

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

Title:
  [i915] System doesn't recognize second monitor

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

Bug description:
  I am using an old monitor which using a DVI connectors but I used a
  DVI to HDMI adapter which works fine on Windows operating system... My
  monitor is HP W2072a... I hope with the information provided helps...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  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.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  

[Kernel-packages] [Bug 2039009] Missing required logs.

[Ubuntu Kernel Bot]

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

apport-collect 2039009

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

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

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

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

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

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

Title:
  do not ship ZSTD compressed modules in jammy/hwe-6.5 kernels

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

Bug description:
  Providing zstd compressed modules may break user-space
  scripts/tools/binaries that are relying on the .ko naming schema.

  The kernel can still support ZSTD compressed modules (via
  CONFIG_MODULE_COMPRESS_ZSTD), but our shipped kernel modules will be
  just regular .ko files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039009/+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 2038981] Re: No external output when hotplugging to a DP monitor after the monitor went to sleep for AMD 6300 GPU

[AceLan Kao]

** Tags added: originate-from-2031598

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

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 2039010] [NEW] revert support for arbitrary symbol length in modversion in hwe kernels

[Andrea Righi]

Public bug reported:

The following patch may break user-space, providing an actual ABI
change:

  UBUNTU: SAUCE: modpost: support arbitrary symbol length in modversion

This is not critical for new releases (also considering that the
potential breakage is unlikely to happen, unless some tools/scripts/apps
are inspecting modules' internals - likely only kmod tools, that are ok
with this change), but for LTS releases it is just safer to prevent
adding this change.

Keep in mind that this patch is required to enable Rust support in the
generic kernel, but it is not required for hwe kernels, because we do
not enable Rust support for them.

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

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

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

Title:
  revert support for arbitrary symbol length in modversion in hwe
  kernels

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

Bug description:
  The following patch may break user-space, providing an actual ABI
  change:

UBUNTU: SAUCE: modpost: support arbitrary symbol length in
  modversion

  This is not critical for new releases (also considering that the
  potential breakage is unlikely to happen, unless some
  tools/scripts/apps are inspecting modules' internals - likely only
  kmod tools, that are ok with this change), but for LTS releases it is
  just safer to prevent adding this change.

  Keep in mind that this patch is required to enable Rust support in the
  generic kernel, but it is not required for hwe kernels, because we do
  not enable Rust support for them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039010/+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 2039009] [NEW] do not ship ZSTD compressed modules in jammy/hwe-6.5 kernels

[Andrea Righi]

Public bug reported:

Providing zstd compressed modules may break user-space
scripts/tools/binaries that are relying on the .ko naming schema.

The kernel can still support ZSTD compressed modules (via
CONFIG_MODULE_COMPRESS_ZSTD), but our shipped kernel modules will be
just regular .ko files.

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

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

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

Title:
  do not ship ZSTD compressed modules in jammy/hwe-6.5 kernels

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

Bug description:
  Providing zstd compressed modules may break user-space
  scripts/tools/binaries that are relying on the .ko naming schema.

  The kernel can still support ZSTD compressed modules (via
  CONFIG_MODULE_COMPRESS_ZSTD), but our shipped kernel modules will be
  just regular .ko files.

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

[Juan Pedro Paredes]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/2038777/+attachment/5708517/+files/acpidump.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/2038777

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HiperV VM network problems

  [   19.259297] 

  [   19.259536] UBSAN: array-index-out-of-bounds in 
/build/linux-7dWMY3/linux-6.5.0/drivers/net/hyperv/netvsc.c:1445:41
  [   19.259715] index 1 is out of range for type 'vmtransfer_page_range [1]'
  [   19.259896] CPU: 1 PID: 1306 Comm: (udev-worker) Not tainted 
6.5.0-7-generic #7-Ubuntu
  [   19.259898] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [   19.259899] Call Trace:
  [   19.259901]  
  [   19.259902]  dump_stack_lvl+0x48/0x70
  [   19.259908]  dump_stack+0x10/0x20
  [   19.259909]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [   19.259912]  netvsc_receive+0x437/0x490 [hv_netvsc]
  [   19.259917]  netvsc_poll+0x176/0x4b0 [hv_netvsc]
  [   19.259921]  __napi_poll+0x30/0x1f0
  [   19.259924]  net_rx_action+0x181/0x2e0
  [   19.259925]  __do_softirq+0xd6/0x346
  [   19.259927]  ? _raw_spin_unlock+0xe/0x40
  [   19.259929]  __irq_exit_rcu+0x75/0xa0
  [   19.259932]  irq_exit_rcu+0xe/0x20
  [   19.259933]  sysvec_hyperv_callback+0x92/0xd0
  [   19.259935]  
  [   19.259935]  

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.8
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CrashDB: ubuntu
  Date: Sun Oct  8 23:09:45 2023
  InstallationDate: Installed on 2021-03-07 (945 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  PackageArchitecture: all
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 oct  9 20:46 seq
   crw-rw 1 root audio 116, 33 oct  9 20:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.27.0-0ubuntu5
  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: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2021-03-07 (948 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  ProcFB: 0 hyperv_drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off iommu=pt
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (2 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2022
  dmi.bios.release: 4.1
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.1
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.1
  dmi.chassis.asset.tag: 

[Kernel-packages] [Bug 2038777] UdevDb.txt

[Juan Pedro Paredes]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/2038777/+attachment/5708515/+files/UdevDb.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/2038777

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HiperV VM network problems

  [   19.259297] 

  [   19.259536] UBSAN: array-index-out-of-bounds in 
/build/linux-7dWMY3/linux-6.5.0/drivers/net/hyperv/netvsc.c:1445:41
  [   19.259715] index 1 is out of range for type 'vmtransfer_page_range [1]'
  [   19.259896] CPU: 1 PID: 1306 Comm: (udev-worker) Not tainted 
6.5.0-7-generic #7-Ubuntu
  [   19.259898] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [   19.259899] Call Trace:
  [   19.259901]  
  [   19.259902]  dump_stack_lvl+0x48/0x70
  [   19.259908]  dump_stack+0x10/0x20
  [   19.259909]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [   19.259912]  netvsc_receive+0x437/0x490 [hv_netvsc]
  [   19.259917]  netvsc_poll+0x176/0x4b0 [hv_netvsc]
  [   19.259921]  __napi_poll+0x30/0x1f0
  [   19.259924]  net_rx_action+0x181/0x2e0
  [   19.259925]  __do_softirq+0xd6/0x346
  [   19.259927]  ? _raw_spin_unlock+0xe/0x40
  [   19.259929]  __irq_exit_rcu+0x75/0xa0
  [   19.259932]  irq_exit_rcu+0xe/0x20
  [   19.259933]  sysvec_hyperv_callback+0x92/0xd0
  [   19.259935]  
  [   19.259935]  

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.8
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CrashDB: ubuntu
  Date: Sun Oct  8 23:09:45 2023
  InstallationDate: Installed on 2021-03-07 (945 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  PackageArchitecture: all
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 oct  9 20:46 seq
   crw-rw 1 root audio 116, 33 oct  9 20:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.27.0-0ubuntu5
  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: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2021-03-07 (948 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  ProcFB: 0 hyperv_drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off iommu=pt
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (2 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2022
  dmi.bios.release: 4.1
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.1
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.1
  dmi.chassis.asset.tag: 

[Kernel-packages] [Bug 2038777] WifiSyslog.txt

[Juan Pedro Paredes]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/2038777/+attachment/5708516/+files/WifiSyslog.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/2038777

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HiperV VM network problems

  [   19.259297] 

  [   19.259536] UBSAN: array-index-out-of-bounds in 
/build/linux-7dWMY3/linux-6.5.0/drivers/net/hyperv/netvsc.c:1445:41
  [   19.259715] index 1 is out of range for type 'vmtransfer_page_range [1]'
  [   19.259896] CPU: 1 PID: 1306 Comm: (udev-worker) Not tainted 
6.5.0-7-generic #7-Ubuntu
  [   19.259898] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [   19.259899] Call Trace:
  [   19.259901]  
  [   19.259902]  dump_stack_lvl+0x48/0x70
  [   19.259908]  dump_stack+0x10/0x20
  [   19.259909]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [   19.259912]  netvsc_receive+0x437/0x490 [hv_netvsc]
  [   19.259917]  netvsc_poll+0x176/0x4b0 [hv_netvsc]
  [   19.259921]  __napi_poll+0x30/0x1f0
  [   19.259924]  net_rx_action+0x181/0x2e0
  [   19.259925]  __do_softirq+0xd6/0x346
  [   19.259927]  ? _raw_spin_unlock+0xe/0x40
  [   19.259929]  __irq_exit_rcu+0x75/0xa0
  [   19.259932]  irq_exit_rcu+0xe/0x20
  [   19.259933]  sysvec_hyperv_callback+0x92/0xd0
  [   19.259935]  
  [   19.259935]  

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.8
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CrashDB: ubuntu
  Date: Sun Oct  8 23:09:45 2023
  InstallationDate: Installed on 2021-03-07 (945 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  PackageArchitecture: all
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 oct  9 20:46 seq
   crw-rw 1 root audio 116, 33 oct  9 20:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.27.0-0ubuntu5
  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: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2021-03-07 (948 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  ProcFB: 0 hyperv_drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off iommu=pt
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (2 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2022
  dmi.bios.release: 4.1
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.1
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.1
  dmi.chassis.asset.tag: 

[Kernel-packages] [Bug 2038777] ProcModules.txt

[Juan Pedro Paredes]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/2038777/+attachment/5708514/+files/ProcModules.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/2038777

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HiperV VM network problems

  [   19.259297] 

  [   19.259536] UBSAN: array-index-out-of-bounds in 
/build/linux-7dWMY3/linux-6.5.0/drivers/net/hyperv/netvsc.c:1445:41
  [   19.259715] index 1 is out of range for type 'vmtransfer_page_range [1]'
  [   19.259896] CPU: 1 PID: 1306 Comm: (udev-worker) Not tainted 
6.5.0-7-generic #7-Ubuntu
  [   19.259898] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [   19.259899] Call Trace:
  [   19.259901]  
  [   19.259902]  dump_stack_lvl+0x48/0x70
  [   19.259908]  dump_stack+0x10/0x20
  [   19.259909]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [   19.259912]  netvsc_receive+0x437/0x490 [hv_netvsc]
  [   19.259917]  netvsc_poll+0x176/0x4b0 [hv_netvsc]
  [   19.259921]  __napi_poll+0x30/0x1f0
  [   19.259924]  net_rx_action+0x181/0x2e0
  [   19.259925]  __do_softirq+0xd6/0x346
  [   19.259927]  ? _raw_spin_unlock+0xe/0x40
  [   19.259929]  __irq_exit_rcu+0x75/0xa0
  [   19.259932]  irq_exit_rcu+0xe/0x20
  [   19.259933]  sysvec_hyperv_callback+0x92/0xd0
  [   19.259935]  
  [   19.259935]  

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.8
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CrashDB: ubuntu
  Date: Sun Oct  8 23:09:45 2023
  InstallationDate: Installed on 2021-03-07 (945 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  PackageArchitecture: all
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 oct  9 20:46 seq
   crw-rw 1 root audio 116, 33 oct  9 20:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.27.0-0ubuntu5
  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: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2021-03-07 (948 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  ProcFB: 0 hyperv_drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off iommu=pt
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (2 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2022
  dmi.bios.release: 4.1
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.1
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.1
  dmi.chassis.asset.tag: 

[Kernel-packages] [Bug 2038777] ProcCpuinfoMinimal.txt

[Juan Pedro Paredes]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2038777/+attachment/5708512/+files/ProcCpuinfoMinimal.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/2038777

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HiperV VM network problems

  [   19.259297] 

  [   19.259536] UBSAN: array-index-out-of-bounds in 
/build/linux-7dWMY3/linux-6.5.0/drivers/net/hyperv/netvsc.c:1445:41
  [   19.259715] index 1 is out of range for type 'vmtransfer_page_range [1]'
  [   19.259896] CPU: 1 PID: 1306 Comm: (udev-worker) Not tainted 
6.5.0-7-generic #7-Ubuntu
  [   19.259898] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [   19.259899] Call Trace:
  [   19.259901]  
  [   19.259902]  dump_stack_lvl+0x48/0x70
  [   19.259908]  dump_stack+0x10/0x20
  [   19.259909]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [   19.259912]  netvsc_receive+0x437/0x490 [hv_netvsc]
  [   19.259917]  netvsc_poll+0x176/0x4b0 [hv_netvsc]
  [   19.259921]  __napi_poll+0x30/0x1f0
  [   19.259924]  net_rx_action+0x181/0x2e0
  [   19.259925]  __do_softirq+0xd6/0x346
  [   19.259927]  ? _raw_spin_unlock+0xe/0x40
  [   19.259929]  __irq_exit_rcu+0x75/0xa0
  [   19.259932]  irq_exit_rcu+0xe/0x20
  [   19.259933]  sysvec_hyperv_callback+0x92/0xd0
  [   19.259935]  
  [   19.259935]  

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.8
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CrashDB: ubuntu
  Date: Sun Oct  8 23:09:45 2023
  InstallationDate: Installed on 2021-03-07 (945 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  PackageArchitecture: all
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 oct  9 20:46 seq
   crw-rw 1 root audio 116, 33 oct  9 20:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.27.0-0ubuntu5
  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: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2021-03-07 (948 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  ProcFB: 0 hyperv_drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off iommu=pt
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (2 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2022
  dmi.bios.release: 4.1
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.1
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.1
  dmi.chassis.asset.tag: 

[Kernel-packages] [Bug 2038777] ProcInterrupts.txt

[Juan Pedro Paredes]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/2038777/+attachment/5708513/+files/ProcInterrupts.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/2038777

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HiperV VM network problems

  [   19.259297] 

  [   19.259536] UBSAN: array-index-out-of-bounds in 
/build/linux-7dWMY3/linux-6.5.0/drivers/net/hyperv/netvsc.c:1445:41
  [   19.259715] index 1 is out of range for type 'vmtransfer_page_range [1]'
  [   19.259896] CPU: 1 PID: 1306 Comm: (udev-worker) Not tainted 
6.5.0-7-generic #7-Ubuntu
  [   19.259898] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [   19.259899] Call Trace:
  [   19.259901]  
  [   19.259902]  dump_stack_lvl+0x48/0x70
  [   19.259908]  dump_stack+0x10/0x20
  [   19.259909]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [   19.259912]  netvsc_receive+0x437/0x490 [hv_netvsc]
  [   19.259917]  netvsc_poll+0x176/0x4b0 [hv_netvsc]
  [   19.259921]  __napi_poll+0x30/0x1f0
  [   19.259924]  net_rx_action+0x181/0x2e0
  [   19.259925]  __do_softirq+0xd6/0x346
  [   19.259927]  ? _raw_spin_unlock+0xe/0x40
  [   19.259929]  __irq_exit_rcu+0x75/0xa0
  [   19.259932]  irq_exit_rcu+0xe/0x20
  [   19.259933]  sysvec_hyperv_callback+0x92/0xd0
  [   19.259935]  
  [   19.259935]  

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.8
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CrashDB: ubuntu
  Date: Sun Oct  8 23:09:45 2023
  InstallationDate: Installed on 2021-03-07 (945 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  PackageArchitecture: all
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 oct  9 20:46 seq
   crw-rw 1 root audio 116, 33 oct  9 20:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.27.0-0ubuntu5
  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: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2021-03-07 (948 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  ProcFB: 0 hyperv_drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off iommu=pt
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (2 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2022
  dmi.bios.release: 4.1
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.1
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.1
  dmi.chassis.asset.tag: 

[Kernel-packages] [Bug 2038777] ProcCpuinfo.txt

[Juan Pedro Paredes]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/2038777/+attachment/5708511/+files/ProcCpuinfo.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/2038777

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HiperV VM network problems

  [   19.259297] 

  [   19.259536] UBSAN: array-index-out-of-bounds in 
/build/linux-7dWMY3/linux-6.5.0/drivers/net/hyperv/netvsc.c:1445:41
  [   19.259715] index 1 is out of range for type 'vmtransfer_page_range [1]'
  [   19.259896] CPU: 1 PID: 1306 Comm: (udev-worker) Not tainted 
6.5.0-7-generic #7-Ubuntu
  [   19.259898] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [   19.259899] Call Trace:
  [   19.259901]  
  [   19.259902]  dump_stack_lvl+0x48/0x70
  [   19.259908]  dump_stack+0x10/0x20
  [   19.259909]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [   19.259912]  netvsc_receive+0x437/0x490 [hv_netvsc]
  [   19.259917]  netvsc_poll+0x176/0x4b0 [hv_netvsc]
  [   19.259921]  __napi_poll+0x30/0x1f0
  [   19.259924]  net_rx_action+0x181/0x2e0
  [   19.259925]  __do_softirq+0xd6/0x346
  [   19.259927]  ? _raw_spin_unlock+0xe/0x40
  [   19.259929]  __irq_exit_rcu+0x75/0xa0
  [   19.259932]  irq_exit_rcu+0xe/0x20
  [   19.259933]  sysvec_hyperv_callback+0x92/0xd0
  [   19.259935]  
  [   19.259935]  

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.8
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CrashDB: ubuntu
  Date: Sun Oct  8 23:09:45 2023
  InstallationDate: Installed on 2021-03-07 (945 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  PackageArchitecture: all
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 oct  9 20:46 seq
   crw-rw 1 root audio 116, 33 oct  9 20:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.27.0-0ubuntu5
  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: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2021-03-07 (948 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  ProcFB: 0 hyperv_drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off iommu=pt
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (2 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2022
  dmi.bios.release: 4.1
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.1
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.1
  dmi.chassis.asset.tag: 

[Kernel-packages] [Bug 2038777] PaInfo.txt

[Juan Pedro Paredes]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/2038777/+attachment/5708510/+files/PaInfo.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/2038777

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HiperV VM network problems

  [   19.259297] 

  [   19.259536] UBSAN: array-index-out-of-bounds in 
/build/linux-7dWMY3/linux-6.5.0/drivers/net/hyperv/netvsc.c:1445:41
  [   19.259715] index 1 is out of range for type 'vmtransfer_page_range [1]'
  [   19.259896] CPU: 1 PID: 1306 Comm: (udev-worker) Not tainted 
6.5.0-7-generic #7-Ubuntu
  [   19.259898] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [   19.259899] Call Trace:
  [   19.259901]  
  [   19.259902]  dump_stack_lvl+0x48/0x70
  [   19.259908]  dump_stack+0x10/0x20
  [   19.259909]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [   19.259912]  netvsc_receive+0x437/0x490 [hv_netvsc]
  [   19.259917]  netvsc_poll+0x176/0x4b0 [hv_netvsc]
  [   19.259921]  __napi_poll+0x30/0x1f0
  [   19.259924]  net_rx_action+0x181/0x2e0
  [   19.259925]  __do_softirq+0xd6/0x346
  [   19.259927]  ? _raw_spin_unlock+0xe/0x40
  [   19.259929]  __irq_exit_rcu+0x75/0xa0
  [   19.259932]  irq_exit_rcu+0xe/0x20
  [   19.259933]  sysvec_hyperv_callback+0x92/0xd0
  [   19.259935]  
  [   19.259935]  

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.8
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CrashDB: ubuntu
  Date: Sun Oct  8 23:09:45 2023
  InstallationDate: Installed on 2021-03-07 (945 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  PackageArchitecture: all
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 oct  9 20:46 seq
   crw-rw 1 root audio 116, 33 oct  9 20:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.27.0-0ubuntu5
  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: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2021-03-07 (948 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  ProcFB: 0 hyperv_drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off iommu=pt
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (2 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2022
  dmi.bios.release: 4.1
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.1
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.1
  dmi.chassis.asset.tag: 

[Kernel-packages] [Bug 2038777] Re: UBSAN: array-index-out-of-bounds

[Juan Pedro Paredes]

apport information

** Description changed:

  HiperV VM network problems
  
  [   19.259297] 

  [   19.259536] UBSAN: array-index-out-of-bounds in 
/build/linux-7dWMY3/linux-6.5.0/drivers/net/hyperv/netvsc.c:1445:41
  [   19.259715] index 1 is out of range for type 'vmtransfer_page_range [1]'
  [   19.259896] CPU: 1 PID: 1306 Comm: (udev-worker) Not tainted 
6.5.0-7-generic #7-Ubuntu
  [   19.259898] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [   19.259899] Call Trace:
  [   19.259901]  
  [   19.259902]  dump_stack_lvl+0x48/0x70
  [   19.259908]  dump_stack+0x10/0x20
  [   19.259909]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [   19.259912]  netvsc_receive+0x437/0x490 [hv_netvsc]
  [   19.259917]  netvsc_poll+0x176/0x4b0 [hv_netvsc]
  [   19.259921]  __napi_poll+0x30/0x1f0
  [   19.259924]  net_rx_action+0x181/0x2e0
  [   19.259925]  __do_softirq+0xd6/0x346
  [   19.259927]  ? _raw_spin_unlock+0xe/0x40
  [   19.259929]  __irq_exit_rcu+0x75/0xa0
  [   19.259932]  irq_exit_rcu+0xe/0x20
  [   19.259933]  sysvec_hyperv_callback+0x92/0xd0
  [   19.259935]  
  [   19.259935]  
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.8
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CrashDB: ubuntu
  Date: Sun Oct  8 23:09:45 2023
  InstallationDate: Installed on 2021-03-07 (945 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  PackageArchitecture: all
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 oct  9 20:46 seq
   crw-rw 1 root audio 116, 33 oct  9 20:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.27.0-0ubuntu5
  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: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2021-03-07 (948 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  ProcFB: 0 hyperv_drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off iommu=pt
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (2 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2022
  dmi.bios.release: 4.1
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.1
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.1
  dmi.chassis.asset.tag: 4585-4991-9142-0880-5352-0701-05
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.1
  dmi.modalias: 

[Kernel-packages] [Bug 2038777] acpidump.txt

[Juan Pedro Paredes]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/2038777/+attachment/5708508/+files/acpidump.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/2038777

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HiperV VM network problems

  [   19.259297] 

  [   19.259536] UBSAN: array-index-out-of-bounds in 
/build/linux-7dWMY3/linux-6.5.0/drivers/net/hyperv/netvsc.c:1445:41
  [   19.259715] index 1 is out of range for type 'vmtransfer_page_range [1]'
  [   19.259896] CPU: 1 PID: 1306 Comm: (udev-worker) Not tainted 
6.5.0-7-generic #7-Ubuntu
  [   19.259898] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [   19.259899] Call Trace:
  [   19.259901]  
  [   19.259902]  dump_stack_lvl+0x48/0x70
  [   19.259908]  dump_stack+0x10/0x20
  [   19.259909]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [   19.259912]  netvsc_receive+0x437/0x490 [hv_netvsc]
  [   19.259917]  netvsc_poll+0x176/0x4b0 [hv_netvsc]
  [   19.259921]  __napi_poll+0x30/0x1f0
  [   19.259924]  net_rx_action+0x181/0x2e0
  [   19.259925]  __do_softirq+0xd6/0x346
  [   19.259927]  ? _raw_spin_unlock+0xe/0x40
  [   19.259929]  __irq_exit_rcu+0x75/0xa0
  [   19.259932]  irq_exit_rcu+0xe/0x20
  [   19.259933]  sysvec_hyperv_callback+0x92/0xd0
  [   19.259935]  
  [   19.259935]  

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.8
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CrashDB: ubuntu
  Date: Sun Oct  8 23:09:45 2023
  InstallationDate: Installed on 2021-03-07 (945 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  PackageArchitecture: all
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 oct  9 20:46 seq
   crw-rw 1 root audio 116, 33 oct  9 20:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.27.0-0ubuntu5
  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: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2021-03-07 (948 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  ProcFB: 0 hyperv_drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off iommu=pt
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (2 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2022
  dmi.bios.release: 4.1
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.1
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.1
  dmi.chassis.asset.tag: 

[Kernel-packages] [Bug 2038777] UdevDb.txt

[Juan Pedro Paredes]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/2038777/+attachment/5708506/+files/UdevDb.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/2038777

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HiperV VM network problems

  [   19.259297] 

  [   19.259536] UBSAN: array-index-out-of-bounds in 
/build/linux-7dWMY3/linux-6.5.0/drivers/net/hyperv/netvsc.c:1445:41
  [   19.259715] index 1 is out of range for type 'vmtransfer_page_range [1]'
  [   19.259896] CPU: 1 PID: 1306 Comm: (udev-worker) Not tainted 
6.5.0-7-generic #7-Ubuntu
  [   19.259898] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [   19.259899] Call Trace:
  [   19.259901]  
  [   19.259902]  dump_stack_lvl+0x48/0x70
  [   19.259908]  dump_stack+0x10/0x20
  [   19.259909]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [   19.259912]  netvsc_receive+0x437/0x490 [hv_netvsc]
  [   19.259917]  netvsc_poll+0x176/0x4b0 [hv_netvsc]
  [   19.259921]  __napi_poll+0x30/0x1f0
  [   19.259924]  net_rx_action+0x181/0x2e0
  [   19.259925]  __do_softirq+0xd6/0x346
  [   19.259927]  ? _raw_spin_unlock+0xe/0x40
  [   19.259929]  __irq_exit_rcu+0x75/0xa0
  [   19.259932]  irq_exit_rcu+0xe/0x20
  [   19.259933]  sysvec_hyperv_callback+0x92/0xd0
  [   19.259935]  
  [   19.259935]  

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.8
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CrashDB: ubuntu
  Date: Sun Oct  8 23:09:45 2023
  InstallationDate: Installed on 2021-03-07 (945 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  PackageArchitecture: all
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 oct  9 20:46 seq
   crw-rw 1 root audio 116, 33 oct  9 20:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.27.0-0ubuntu5
  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: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2021-03-07 (948 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  ProcFB: 0 hyperv_drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off iommu=pt
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (2 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2022
  dmi.bios.release: 4.1
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.1
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.1
  dmi.chassis.asset.tag: 

[Kernel-packages] [Bug 2038777] WifiSyslog.txt

[Juan Pedro Paredes]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/2038777/+attachment/5708507/+files/WifiSyslog.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/2038777

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HiperV VM network problems

  [   19.259297] 

  [   19.259536] UBSAN: array-index-out-of-bounds in 
/build/linux-7dWMY3/linux-6.5.0/drivers/net/hyperv/netvsc.c:1445:41
  [   19.259715] index 1 is out of range for type 'vmtransfer_page_range [1]'
  [   19.259896] CPU: 1 PID: 1306 Comm: (udev-worker) Not tainted 
6.5.0-7-generic #7-Ubuntu
  [   19.259898] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [   19.259899] Call Trace:
  [   19.259901]  
  [   19.259902]  dump_stack_lvl+0x48/0x70
  [   19.259908]  dump_stack+0x10/0x20
  [   19.259909]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [   19.259912]  netvsc_receive+0x437/0x490 [hv_netvsc]
  [   19.259917]  netvsc_poll+0x176/0x4b0 [hv_netvsc]
  [   19.259921]  __napi_poll+0x30/0x1f0
  [   19.259924]  net_rx_action+0x181/0x2e0
  [   19.259925]  __do_softirq+0xd6/0x346
  [   19.259927]  ? _raw_spin_unlock+0xe/0x40
  [   19.259929]  __irq_exit_rcu+0x75/0xa0
  [   19.259932]  irq_exit_rcu+0xe/0x20
  [   19.259933]  sysvec_hyperv_callback+0x92/0xd0
  [   19.259935]  
  [   19.259935]  

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.8
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CrashDB: ubuntu
  Date: Sun Oct  8 23:09:45 2023
  InstallationDate: Installed on 2021-03-07 (945 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  PackageArchitecture: all
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 oct  9 20:46 seq
   crw-rw 1 root audio 116, 33 oct  9 20:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.27.0-0ubuntu5
  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: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2021-03-07 (948 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  ProcFB: 0 hyperv_drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off iommu=pt
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (2 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2022
  dmi.bios.release: 4.1
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.1
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.1
  dmi.chassis.asset.tag: 

[Kernel-packages] [Bug 2038777] ProcModules.txt

[Juan Pedro Paredes]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/2038777/+attachment/5708505/+files/ProcModules.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/2038777

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HiperV VM network problems

  [   19.259297] 

  [   19.259536] UBSAN: array-index-out-of-bounds in 
/build/linux-7dWMY3/linux-6.5.0/drivers/net/hyperv/netvsc.c:1445:41
  [   19.259715] index 1 is out of range for type 'vmtransfer_page_range [1]'
  [   19.259896] CPU: 1 PID: 1306 Comm: (udev-worker) Not tainted 
6.5.0-7-generic #7-Ubuntu
  [   19.259898] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [   19.259899] Call Trace:
  [   19.259901]  
  [   19.259902]  dump_stack_lvl+0x48/0x70
  [   19.259908]  dump_stack+0x10/0x20
  [   19.259909]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [   19.259912]  netvsc_receive+0x437/0x490 [hv_netvsc]
  [   19.259917]  netvsc_poll+0x176/0x4b0 [hv_netvsc]
  [   19.259921]  __napi_poll+0x30/0x1f0
  [   19.259924]  net_rx_action+0x181/0x2e0
  [   19.259925]  __do_softirq+0xd6/0x346
  [   19.259927]  ? _raw_spin_unlock+0xe/0x40
  [   19.259929]  __irq_exit_rcu+0x75/0xa0
  [   19.259932]  irq_exit_rcu+0xe/0x20
  [   19.259933]  sysvec_hyperv_callback+0x92/0xd0
  [   19.259935]  
  [   19.259935]  

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.8
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CrashDB: ubuntu
  Date: Sun Oct  8 23:09:45 2023
  InstallationDate: Installed on 2021-03-07 (945 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  PackageArchitecture: all
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 oct  9 20:46 seq
   crw-rw 1 root audio 116, 33 oct  9 20:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.27.0-0ubuntu5
  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: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2021-03-07 (948 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  ProcFB: 0 hyperv_drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off iommu=pt
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (2 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2022
  dmi.bios.release: 4.1
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.1
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.1
  dmi.chassis.asset.tag: 

[Kernel-packages] [Bug 2038777] ProcCpuinfoMinimal.txt

[Juan Pedro Paredes]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2038777/+attachment/5708503/+files/ProcCpuinfoMinimal.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/2038777

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HiperV VM network problems

  [   19.259297] 

  [   19.259536] UBSAN: array-index-out-of-bounds in 
/build/linux-7dWMY3/linux-6.5.0/drivers/net/hyperv/netvsc.c:1445:41
  [   19.259715] index 1 is out of range for type 'vmtransfer_page_range [1]'
  [   19.259896] CPU: 1 PID: 1306 Comm: (udev-worker) Not tainted 
6.5.0-7-generic #7-Ubuntu
  [   19.259898] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [   19.259899] Call Trace:
  [   19.259901]  
  [   19.259902]  dump_stack_lvl+0x48/0x70
  [   19.259908]  dump_stack+0x10/0x20
  [   19.259909]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [   19.259912]  netvsc_receive+0x437/0x490 [hv_netvsc]
  [   19.259917]  netvsc_poll+0x176/0x4b0 [hv_netvsc]
  [   19.259921]  __napi_poll+0x30/0x1f0
  [   19.259924]  net_rx_action+0x181/0x2e0
  [   19.259925]  __do_softirq+0xd6/0x346
  [   19.259927]  ? _raw_spin_unlock+0xe/0x40
  [   19.259929]  __irq_exit_rcu+0x75/0xa0
  [   19.259932]  irq_exit_rcu+0xe/0x20
  [   19.259933]  sysvec_hyperv_callback+0x92/0xd0
  [   19.259935]  
  [   19.259935]  

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.8
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CrashDB: ubuntu
  Date: Sun Oct  8 23:09:45 2023
  InstallationDate: Installed on 2021-03-07 (945 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  PackageArchitecture: all
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 oct  9 20:46 seq
   crw-rw 1 root audio 116, 33 oct  9 20:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.27.0-0ubuntu5
  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: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2021-03-07 (948 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  ProcFB: 0 hyperv_drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off iommu=pt
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (2 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2022
  dmi.bios.release: 4.1
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.1
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.1
  dmi.chassis.asset.tag: 

[Kernel-packages] [Bug 2038777] ProcInterrupts.txt

[Juan Pedro Paredes]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/2038777/+attachment/5708504/+files/ProcInterrupts.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/2038777

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HiperV VM network problems

  [   19.259297] 

  [   19.259536] UBSAN: array-index-out-of-bounds in 
/build/linux-7dWMY3/linux-6.5.0/drivers/net/hyperv/netvsc.c:1445:41
  [   19.259715] index 1 is out of range for type 'vmtransfer_page_range [1]'
  [   19.259896] CPU: 1 PID: 1306 Comm: (udev-worker) Not tainted 
6.5.0-7-generic #7-Ubuntu
  [   19.259898] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [   19.259899] Call Trace:
  [   19.259901]  
  [   19.259902]  dump_stack_lvl+0x48/0x70
  [   19.259908]  dump_stack+0x10/0x20
  [   19.259909]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [   19.259912]  netvsc_receive+0x437/0x490 [hv_netvsc]
  [   19.259917]  netvsc_poll+0x176/0x4b0 [hv_netvsc]
  [   19.259921]  __napi_poll+0x30/0x1f0
  [   19.259924]  net_rx_action+0x181/0x2e0
  [   19.259925]  __do_softirq+0xd6/0x346
  [   19.259927]  ? _raw_spin_unlock+0xe/0x40
  [   19.259929]  __irq_exit_rcu+0x75/0xa0
  [   19.259932]  irq_exit_rcu+0xe/0x20
  [   19.259933]  sysvec_hyperv_callback+0x92/0xd0
  [   19.259935]  
  [   19.259935]  

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.8
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CrashDB: ubuntu
  Date: Sun Oct  8 23:09:45 2023
  InstallationDate: Installed on 2021-03-07 (945 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  PackageArchitecture: all
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 oct  9 20:46 seq
   crw-rw 1 root audio 116, 33 oct  9 20:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.27.0-0ubuntu5
  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: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2021-03-07 (948 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  ProcFB: 0 hyperv_drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off iommu=pt
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (2 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2022
  dmi.bios.release: 4.1
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.1
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.1
  dmi.chassis.asset.tag: 

[Kernel-packages] [Bug 2038777] ProcCpuinfo.txt

[Juan Pedro Paredes]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/2038777/+attachment/5708502/+files/ProcCpuinfo.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/2038777

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HiperV VM network problems

  [   19.259297] 

  [   19.259536] UBSAN: array-index-out-of-bounds in 
/build/linux-7dWMY3/linux-6.5.0/drivers/net/hyperv/netvsc.c:1445:41
  [   19.259715] index 1 is out of range for type 'vmtransfer_page_range [1]'
  [   19.259896] CPU: 1 PID: 1306 Comm: (udev-worker) Not tainted 
6.5.0-7-generic #7-Ubuntu
  [   19.259898] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [   19.259899] Call Trace:
  [   19.259901]  
  [   19.259902]  dump_stack_lvl+0x48/0x70
  [   19.259908]  dump_stack+0x10/0x20
  [   19.259909]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [   19.259912]  netvsc_receive+0x437/0x490 [hv_netvsc]
  [   19.259917]  netvsc_poll+0x176/0x4b0 [hv_netvsc]
  [   19.259921]  __napi_poll+0x30/0x1f0
  [   19.259924]  net_rx_action+0x181/0x2e0
  [   19.259925]  __do_softirq+0xd6/0x346
  [   19.259927]  ? _raw_spin_unlock+0xe/0x40
  [   19.259929]  __irq_exit_rcu+0x75/0xa0
  [   19.259932]  irq_exit_rcu+0xe/0x20
  [   19.259933]  sysvec_hyperv_callback+0x92/0xd0
  [   19.259935]  
  [   19.259935]  

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.8
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CrashDB: ubuntu
  Date: Sun Oct  8 23:09:45 2023
  InstallationDate: Installed on 2021-03-07 (945 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  PackageArchitecture: all
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 oct  9 20:46 seq
   crw-rw 1 root audio 116, 33 oct  9 20:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.27.0-0ubuntu5
  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: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2021-03-07 (948 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  ProcFB: 0 hyperv_drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off iommu=pt
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (2 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2022
  dmi.bios.release: 4.1
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.1
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.1
  dmi.chassis.asset.tag: 

[Kernel-packages] [Bug 2038777] PaInfo.txt

[Juan Pedro Paredes]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/2038777/+attachment/5708501/+files/PaInfo.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/2038777

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HiperV VM network problems

  [   19.259297] 

  [   19.259536] UBSAN: array-index-out-of-bounds in 
/build/linux-7dWMY3/linux-6.5.0/drivers/net/hyperv/netvsc.c:1445:41
  [   19.259715] index 1 is out of range for type 'vmtransfer_page_range [1]'
  [   19.259896] CPU: 1 PID: 1306 Comm: (udev-worker) Not tainted 
6.5.0-7-generic #7-Ubuntu
  [   19.259898] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [   19.259899] Call Trace:
  [   19.259901]  
  [   19.259902]  dump_stack_lvl+0x48/0x70
  [   19.259908]  dump_stack+0x10/0x20
  [   19.259909]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [   19.259912]  netvsc_receive+0x437/0x490 [hv_netvsc]
  [   19.259917]  netvsc_poll+0x176/0x4b0 [hv_netvsc]
  [   19.259921]  __napi_poll+0x30/0x1f0
  [   19.259924]  net_rx_action+0x181/0x2e0
  [   19.259925]  __do_softirq+0xd6/0x346
  [   19.259927]  ? _raw_spin_unlock+0xe/0x40
  [   19.259929]  __irq_exit_rcu+0x75/0xa0
  [   19.259932]  irq_exit_rcu+0xe/0x20
  [   19.259933]  sysvec_hyperv_callback+0x92/0xd0
  [   19.259935]  
  [   19.259935]  

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.8
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CrashDB: ubuntu
  Date: Sun Oct  8 23:09:45 2023
  InstallationDate: Installed on 2021-03-07 (945 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  PackageArchitecture: all
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 oct  9 20:46 seq
   crw-rw 1 root audio 116, 33 oct  9 20:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.27.0-0ubuntu5
  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: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2021-03-07 (948 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lspci-vt:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  ProcFB: 0 hyperv_drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off iommu=pt
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (2 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2022
  dmi.bios.release: 4.1
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.1
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.1
  dmi.chassis.asset.tag: 

[Kernel-packages] [Bug 2038777] Re: UBSAN: array-index-out-of-bounds

[Juan Pedro Paredes]

** Tags added: apport-collected

** Description changed:

  HiperV VM network problems
  
  [   19.259297] 

  [   19.259536] UBSAN: array-index-out-of-bounds in 
/build/linux-7dWMY3/linux-6.5.0/drivers/net/hyperv/netvsc.c:1445:41
  [   19.259715] index 1 is out of range for type 'vmtransfer_page_range [1]'
  [   19.259896] CPU: 1 PID: 1306 Comm: (udev-worker) Not tainted 
6.5.0-7-generic #7-Ubuntu
  [   19.259898] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
  [   19.259899] Call Trace:
  [   19.259901]  
  [   19.259902]  dump_stack_lvl+0x48/0x70
  [   19.259908]  dump_stack+0x10/0x20
  [   19.259909]  __ubsan_handle_out_of_bounds+0xc6/0x110
  [   19.259912]  netvsc_receive+0x437/0x490 [hv_netvsc]
  [   19.259917]  netvsc_poll+0x176/0x4b0 [hv_netvsc]
  [   19.259921]  __napi_poll+0x30/0x1f0
  [   19.259924]  net_rx_action+0x181/0x2e0
  [   19.259925]  __do_softirq+0xd6/0x346
  [   19.259927]  ? _raw_spin_unlock+0xe/0x40
  [   19.259929]  __irq_exit_rcu+0x75/0xa0
  [   19.259932]  irq_exit_rcu+0xe/0x20
  [   19.259933]  sysvec_hyperv_callback+0x92/0xd0
  [   19.259935]  
  [   19.259935]  
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.8
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CrashDB: ubuntu
  Date: Sun Oct  8 23:09:45 2023
  InstallationDate: Installed on 2021-03-07 (945 days ago)
  InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
  PackageArchitecture: all
  ProcEnviron:
   LANG=es_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to mantic on 2023-10-08 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
+ --- 
+ ProblemType: Bug
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 oct  9 20:46 seq
+  crw-rw 1 root audio 116, 33 oct  9 20:46 timer
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
+ ApportVersion: 2.27.0-0ubuntu5
+ 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: pass
+ CloudArchitecture: x86_64
+ CloudID: none
+ CloudName: none
+ CloudPlatform: none
+ CloudSubPlatform: config
+ DistroRelease: Ubuntu 23.10
+ InstallationDate: Installed on 2021-03-07 (948 days ago)
+ InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210201.2)
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
+ Lspci:
+  
+ Lspci-vt:
+  
+ Lsusb: Error: command ['lsusb'] failed with exit code 1:
+ Lsusb-t:
+  
+ Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
+ MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  LANG=es_ES.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=xterm
+  XDG_RUNTIME_DIR=
+ ProcFB: 0 hyperv_drmdrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off iommu=pt
+ ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ 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
+ RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
+ Tags: mantic
+ Uname: Linux 6.5.0-9-generic x86_64
+ UpgradeStatus: Upgraded to mantic on 2023-10-08 (2 days ago)
+ UserGroups: N/A
+ _MarkForUpload: True
+ dmi.bios.date: 04/06/2022
+ dmi.bios.release: 4.1
+ dmi.bios.vendor: Microsoft Corporation
+ dmi.bios.version: Hyper-V UEFI Release v4.1
+ dmi.board.asset.tag: None
+ dmi.board.name: Virtual Machine
+ dmi.board.vendor: Microsoft Corporation
+ dmi.board.version: Hyper-V UEFI Release v4.1
+ dmi.chassis.asset.tag: 4585-4991-9142-0880-5352-0701-05
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Microsoft Corporation
+ dmi.chassis.version: Hyper-V UEFI Release v4.1
+ dmi.modalias: 

[Kernel-packages] [Bug 2036515] Re: Fix system boot hang caused by devlink

[Kai-Heng Feng]

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

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

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

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

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

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

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

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

** Changed in: linux (Ubuntu Lunar)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

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

Title:
  Fix system boot hang caused by devlink

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

Bug description:
  [Impact]
  System stuck at boot when Intel 7560 is in use, because devlink
  is waiting for reference to be released.

  [Fix]
  Commit "devlink: remove the registration guarantee of references"
  weakens the refcount requirement for devlink {,un}registering,

  [Test]
  System reboots over 2000 times when the fix is applied.

  [Where problems could occur]
  devlink is part of net core API, so it has many users, therefore all of
  devlink users can be affected by this fix. However, all the devlink
  users can be affected by the same issue (i.e. waiting for reference to
  decrease to 0), hence this is still a desirable fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2036515/+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 2037513] Re: HP ProBook 450 G8 Notebook fail to wifi test

[Kai-Heng Feng]

** Tags added: oem-priority originate-from-1942020 stella

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

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

** Also affects: linux-signed-hwe-5.15 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: linux-signed-hwe-5.15 (Ubuntu)
   Status: In Progress => Invalid

** Changed in: linux-signed-hwe-5.15 (Ubuntu Jammy)
   Status: New => Invalid

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

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

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

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

Title:
  HP ProBook 450 G8 Notebook fail to wifi test

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-signed-hwe-5.15 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Confirmed
Status in linux-signed-hwe-5.15 source package in Jammy:
  Invalid

Bug description:
  I'm reviewing the SRU test result on this machine.
  I found that this machine always fails to wifi test and also pop out a lot of 
error message in dmesg.

  It's not a regression, since according to previous test run it has failed 
already.
  Just because we missed reviewing it for a while.

  The journal log is attach, please check further hardware informations
  at https://certification.canonical.com/hardware/202106-29176/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-86-generic 5.15.0-86.96~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122
  Uname: Linux 5.15.0-86-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep 27 15:47:37 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-focal-amd64-20220621-7+pc-stella-cmit-focal-amd64+X00
  InstallationDate: Installed on 2023-09-25 (2 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20220621-04:14
  SourcePackage: linux-signed-hwe-5.15
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2037513/+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 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs

[Launchpad Bug Tracker]

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

** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Having a video playing/paused when switched to another user generates
  gigabytes of error logs

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Confirmed

Bug description:
  To replicate:

  1. Start a video playing, for example in vlc. 'avcodec decoder: Using
  NVIDIA VDPAU Driver Shared Library  418.56  Fri Mar 15 12:31:51 CDT
  2019 for hardware decoding'

  2. Optionally pause it.

  3. Switch to another user.

  The original user's ~/.xsession-errors will rapidly fill up with
  errors along the lines of "vdpau_chroma filter error".

  At the same time, errors are put in /var/log/syslog as well:

  [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: 
An invalid handle value was provided.
  [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: 
An invalid handle value was provided.
  (repeat ad nauseum)

  At least one of the two will rapidly fill up its partition and
  problems will arise.

  With AMD video hardware and driver, the video continues playing - you
  can hear the sound despite being in the other user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+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