[Kernel-packages] [Bug 2062556] Re: [Ubuntu-24.04] Hugepage memory is not getting released even after destroying the guest!
** Also affects: ubuntu-power-systems
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/2062556
Title:
[Ubuntu-24.04] Hugepage memory is not getting released even after
destroying the guest!
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
---Problem Description---
Hugepages memory is not getting released even after destroying the guest
Machine Type = P10 Denali LPAR
---uname output---
Linux ubuntu2404lp3 6.8.0-22-generic #22-Ubuntu SMP Thu Apr 4 22:47:57 UTC
2024 ppc64le ppc64le ppc64le GNU/Linux
---Steps to Reproduce---
1. Create a guest which is backed by hugepages.
2. Destroy the guest
3. execute "free -h" or "cat /proc/meminfo" to see that Hugepage memory is
still getting held.
HugePages_Total: 20480
HugePages_Free:20419
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize: 2048 kB
Hugetlb:41943040 kB
DirectMap4k: 0 kB
DirectMap64k:52428800 kB
DirectMap2M: 0 kB
DirectMap1G: 0 kB
root@ubuntu2404lp3:~# virsh list --all
Id Name State
---
-ramlp2g1 shut off
-ramlp2g2 shut off
-ramlp2g3 shut off
-ramlp3g3 shut off
root@ubuntu2404lp3:~# free -h
totalusedfree shared buff/cache
available
Mem:48Gi43Gi 4.6Gi 2.6Mi 277Mi
4.6Gi
Swap: 8.0Gi 243Mi 7.8Gi
root@ubuntu2404lp3:~#
This is an issue created by commit 1b151e2435fc ("block: Remove
special-casing of compound pages") that moved the direct-io hugetlb handling
from compound pages to folios.
Following commit has been proposed and merged into 6.9-rc1 which fixes this
issue.
38b43539d64b2fa020b3b9a752a986769f87f7a6("block: Fix page refcounts for
unaligned buffers in __bio_release_pages()")
So the same needs to be backported to the Ubuntu24.04 kernel as well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2062556/+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 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!
I have just seen this on 6.8.0-22-generic on a libvirt host running
serveral k8s instances in KVM. Their drivers are backed by ZFS.
I just switched them to cache=writeback for disks, that might trigger
this issue. It happened when they were idle but at a time (8AM) when I
suspect some crons ran.
This message just happened again when I was deleting the VMs (virsh
destroy) and their disks (zfs destroy).
--
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/2037214
Title:
evict_inodes inode xxx, i_count = 1, was skipped!
Status in linux package in Ubuntu:
Confirmed
Status in linux-meta-hwe-6.5 package in Ubuntu:
Confirmed
Status in linux-oem-6.5 package in Ubuntu:
Confirmed
Bug description:
Hi,
during boot the kernel logs the following messages:
# dmesg | grep evict_inodes
[ 12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
[ 12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
[ 12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
[ 12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
[ 12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!
Those messages are not displayed when I boot my system with a mainline Linux
kernel.
Moreover, in the mainline Linux source code, I do not find the lines where
such a message could be printed.
Therefore, those messages are probably caused by an Ubuntu patch.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-5-generic 6.5.0-5.5
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bonnaudl 4827 F wireplumber
/dev/snd/seq:bonnaudl 4808 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 14:39:10 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214/+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 2062556] Re: [Ubuntu-24.04] Hugepage memory is not getting released even after destroying the guest!
I just had a look at noble's master-next tree:
$ git remote get-url origin
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble
$ git branch
* master-next
and found that commit 19c1ceeca8ed is already applied:
$ git log --oneline | grep -n "block: Fix page refcounts for unaligned buffers
in __bio_release_pages"
300:19c1ceeca8ed block: Fix page refcounts for unaligned buffers in
__bio_release_pages()
but not yet tagged with (incl. in) any version:
$ git tag --contains 19c1ceeca8ed
$
This is probably because it just came in via upstream stable updates:
$ git show 19c1ceeca8ed | sed '/^diff --git/q'
commit 19c1ceeca8ed31d207859e659482ee83ea1959f5
Author: Tony Battersby
Date: Thu Feb 29 13:08:09 2024 -0500
block: Fix page refcounts for unaligned buffers in __bio_release_pages()
BugLink: https://bugs.launchpad.net/bugs/2060531
[ Upstream commit 38b43539d64b2fa020b3b9a752a986769f87f7a6 ]
Fix an incorrect number of pages being released for buffers that do not
start at the beginning of a page.
Fixes: 1b151e2435fc ("block: Remove special-casing of compound pages")
Cc: sta...@vger.kernel.org
Signed-off-by: Tony Battersby
Tested-by: Greg Edwards
Link:
https://lore.kernel.org/r/86e592a9-98d4-4cff-a646-0c0084328...@cybernetics.com
Signed-off-by: Jens Axboe
Signed-off-by: Sasha Levin
Signed-off-by: Paolo Pisati
diff --git a/block/bio.c b/block/bio.c
And since the lastest tagged Ubuntu kernel version in master-next is:
Ubuntu-6.8.0-31.31
$ git log --oneline | grep -n $(git describe --tags --abbrev=0)
1170:7fdb45c9bbbc (tag: Ubuntu-6.8.0-31.31) UBUNTU: Ubuntu-6.8.0-31.31
commit 19c1ceeca8ed will be automatically part of the next/upcoming
Ubuntu kernel (> Ubuntu-6.8.0-31.31).
With that I'm updating the status of this bug to Fix Committed.
** Changed in: ubuntu-power-systems
Status: New => Fix Committed
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage
(ubuntu-power-triage)
** Changed in: linux (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
(unassigned)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-power-systems
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2062556
Title:
[Ubuntu-24.04] Hugepage memory is not getting released even after
destroying the guest!
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Bug description:
---Problem Description---
Hugepages memory is not getting released even after destroying the guest
Machine Type = P10 Denali LPAR
---uname output---
Linux ubuntu2404lp3 6.8.0-22-generic #22-Ubuntu SMP Thu Apr 4 22:47:57 UTC
2024 ppc64le ppc64le ppc64le GNU/Linux
---Steps to Reproduce---
1. Create a guest which is backed by hugepages.
2. Destroy the guest
3. execute "free -h" or "cat /proc/meminfo" to see that Hugepage memory is
still getting held.
HugePages_Total: 20480
HugePages_Free:20419
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize: 2048 kB
Hugetlb:41943040 kB
DirectMap4k: 0 kB
DirectMap64k:52428800 kB
DirectMap2M: 0 kB
DirectMap1G: 0 kB
root@ubuntu2404lp3:~# virsh list --all
Id Name State
---
-ramlp2g1 shut off
-ramlp2g2 shut off
-ramlp2g3 shut off
-ramlp3g3 shut off
root@ubuntu2404lp3:~# free -h
totalusedfree shared buff/cache
available
Mem:48Gi43Gi 4.6Gi 2.6Mi 277Mi
4.6Gi
Swap: 8.0Gi 243Mi 7.8Gi
root@ubuntu2404lp3:~#
This is an issue created by commit 1b151e2435fc ("block: Remove
special-casing of compound pages") that moved the direct-io hugetlb handling
from compound pages to folios.
Following commit has been proposed and merged into 6.9-rc1 which fixes this
issue.
38b43539d64b2fa020b3b9a752a986769f87f7a6("block: Fix page refcounts for
unaligned buffers in __bio_release_pages()")
So the same needs to be backported to the Ubuntu24.04 kernel as well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2062556/+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 2059991] Re: Mantic update: upstream stable patchset 2024-04-02
** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2059991 Title: Mantic update: upstream stable patchset 2024-04-02 Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2024-04-02 Ported from the following upstream stable releases: v6.1.78, v6.6.17 from git://git.kernel.org/ ext4: regenerate buddy after block freeing failed if under fc replay dmaengine: fsl-dpaa2-qdma: Fix the size of dma pools dmaengine: ti: k3-udma: Report short packet errors dmaengine: fsl-qdma: Fix a memory leak related to the status queue DMA dmaengine: fsl-qdma: Fix a memory leak related to the queue command DMA phy: renesas: rcar-gen3-usb2: Fix returning wrong error code dmaengine: fix is_slave_direction() return false when DMA_DEV_TO_DEV phy: ti: phy-omap-usb2: Fix NULL pointer dereference for SRP cifs: failure to add channel on iface should bump up weight drm/msms/dp: fixed link clock divider bits be over written in BPC unknown case drm/msm/dp: return correct Colorimetry for DP_TEST_DYNAMIC_RANGE_CEA case drm/msm/dpu: check for valid hw_pp in dpu_encoder_helper_phys_cleanup net: stmmac: xgmac: fix handling of DPP safety error for DMA channels wifi: mac80211: fix waiting for beacons logic netdevsim: avoid potential loop in nsim_dev_trap_report_work() net: atlantic: Fix DMA mapping for PTP hwts ring selftests: net: cut more slack for gro fwd tests. selftests: net: avoid just another constant wait tunnels: fix out of bounds access when building IPv6 PMTU error atm: idt77252: fix a memleak in open_card_ubr0 octeontx2-pf: Fix a memleak otx2_sq_init hwmon: (aspeed-pwm-tacho) mutex for tach reading hwmon: (coretemp) Fix out-of-bounds memory access hwmon: (coretemp) Fix bogus core_id to attr name mapping inet: read sk->sk_family once in inet_recv_error() drm/i915/gvt: Fix uninitialized variable in handle_mmio() rxrpc: Fix response to PING RESPONSE ACKs to a dead call tipc: Check the bearer type before calling tipc_udp_nl_bearer_add() af_unix: Call kfree_skb() for dead unix_(sk)->oob_skb in GC. ppp_async: limit MRU to 64K selftests: cmsg_ipv6: repeat the exact packet netfilter: nft_compat: narrow down revision to unsigned 8-bits netfilter: nft_compat: reject unused compat flag netfilter: nft_compat: restrict match/target protocol to u16 drm/amd/display: Implement bounds check for stream encoder creation in DCN301 netfilter: nft_ct: reject direction for ct id netfilter: nft_set_pipapo: store index in scratch maps netfilter: nft_set_pipapo: add helper to release pcpu scratch area netfilter: nft_set_pipapo: remove scratch_aligned pointer fs/ntfs3: Fix an NULL dereference bug scsi: core: Move scsi_host_busy() out of host lock if it is for per-command blk-iocost: Fix an UBSAN shift-out-of-bounds warning ALSA: usb-audio: Add delay quirk for MOTU M Series 2nd revision ALSA: usb-audio: Add a quirk for Yamaha YIT-W12TX transmitter ALSA: usb-audio: add quirk for RODE NT-USB+ USB: serial: qcserial: add new usb-id for Dell Wireless DW5826e USB: serial: option: add Fibocom FM101-GL variant USB: serial: cp210x: add ID for IMST iM871A-USB usb: dwc3: host: Set XHCI_SG_TRB_CACHE_SIZE_QUIRK usb: host: xhci-plat: Add support for XHCI_SG_TRB_CACHE_SIZE_QUIRK hrtimer: Report offline hrtimer enqueue Input: i8042 - fix strange behavior of touchpad on Clevo NS70PU Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID io_uring/net: fix sr->len for IORING_OP_RECV with MSG_WAITALL and buffers net: stmmac: xgmac: use #define for string constants ALSA: usb-audio: Sort quirk table entries net: stmmac: xgmac: fix a typo of register name in DPP safety handling perf evlist: Fix evlist__new_default() for > 1 core PMU cifs: avoid redundant calls to disable multichannel rust: arc: add explicit `drop()` around `Box::from_raw()` rust: task: remove redundant explicit link rust: print: use explicit link in documentation MAINTAINERS: add Catherine as xfs maintainer for 6.6.y xfs: bump max fsgeom struct version xfs: hoist freeing of rt data fork extent mappings xfs: prevent rt growfs when quota is enabled xfs: rt stubs should retur
[Kernel-packages] [Bug 2061814] Re: Mantic update: upstream stable patchset 2024-04-16
** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2061814 Title: Mantic update: upstream stable patchset 2024-04-16 Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2024-04-16 Ported from the following upstream stable releases: v6.1.79, v6.6.18 from git://git.kernel.org/ btrfs: add and use helper to check if block group is used btrfs: do not delete unused block group if it may be used soon btrfs: forbid creating subvol qgroups btrfs: forbid deleting live subvol qgroup btrfs: send: return EOPNOTSUPP on unknown flags btrfs: don't reserve space for checksums when writing to nocow files btrfs: reject encoded write if inode has nodatasum flag set btrfs: don't drop extent_map for free space inode on write error driver core: Fix device_link_flag_is_sync_state_only() of: unittest: Fix compile in the non-dynamic case KVM: selftests: Fix a semaphore imbalance in the dirty ring logging test wifi: iwlwifi: Fix some error codes wifi: iwlwifi: uninitialized variable in iwl_acpi_get_ppag_table() of: property: Improve finding the supplier of a remote-endpoint property net: openvswitch: limit the number of recursions from action sets lan966x: Fix crash when adding interface under a lag spi: ppc4xx: Drop write-only variable ASoC: rt5645: Fix deadlock in rt5645_jack_detect_work() net: sysfs: Fix /sys/class/net/ path for statistics nouveau/svm: fix kvcalloc() argument order MIPS: Add 'memory' clobber to csum_ipv6_magic() inline assembler i40e: Do not allow untrusted VF to remove administratively set MAC i40e: Fix waiting for queues of all VSIs to be disabled scs: add CONFIG_MMU dependency for vfree_atomic() tracing/trigger: Fix to return error if failed to alloc snapshot mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again scsi: storvsc: Fix ring buffer size calculation dm-crypt, dm-verity: disable tasklets ASoC: amd: yc: Add DMI quirk for MSI Bravo 15 C7VF parisc: Prevent hung tasks when printing inventory on serial console ALSA: hda/realtek: Fix the external mic not being recognised for Acer Swift 1 SF114-32 ALSA: hda/realtek: Enable Mute LED on HP Laptop 14-fq0xxx HID: i2c-hid-of: fix NULL-deref on failed power up HID: wacom: generic: Avoid reporting a serial of '0' to userspace HID: wacom: Do not register input devices until after hid_hw_start iio: hid-sensor-als: Return 0 for HID_USAGE_SENSOR_TIME_TIMESTAMP usb: ucsi: Add missing ppm_lock usb: ulpi: Fix debugfs directory leak usb: ucsi_acpi: Fix command completion handling USB: hub: check for alternate port before enabling A_ALT_HNP_SUPPORT usb: f_mass_storage: forbid async queue when shutdown happen usb: dwc3: gadget: Fix NULL pointer dereference in dwc3_gadget_suspend interconnect: qcom: sc8180x: Mark CO0 BCM keepalive media: ir_toy: fix a memleak in irtoy_tx driver core: fw_devlink: Improve detection of overlapping cycles powerpc/kasan: Fix addr error caused by page alignment cifs: fix underflow in parse_server_interfaces() i2c: qcom-geni: Correct I2C TRE sequence irqchip/loongson-eiointc: Use correct struct type in eiointc_domain_alloc() powerpc/kasan: Limit KASAN thread size increase to 32KB i2c: pasemi: split driver into two separate modules i2c: i801: Fix block process call transactions modpost: trim leading spaces when processing source files list mptcp: get rid of msk->subflow mptcp: fix data re-injection from stale subflow selftests: mptcp: add missing kconfig for NF Filter selftests: mptcp: add missing kconfig for NF Filter in v6 selftests: mptcp: add missing kconfig for NF Mangle selftests: mptcp: increase timeout to 30 min mptcp: drop the push_pending field mptcp: check addrs list in userspace_pm_get_local_id scsi: Revert "scsi: fcoe: Fix potential deadlock on &fip->ctlr_lock" Revert "drm/amd: flush any delayed gfxoff on suspend entry" drm/virtio: Set segment size for virtio_gpu device lsm: fix the logic in security_inode_getsecctx() firewire: core: correct documentation of fw_csr_string() kernel API ALSA: hda/realtek: Apply headset jack quirk for non-bass alc287 thinkpads kbuild: Fix changing ELF f
[Kernel-packages] [Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic
testing with Ubuntu-6.5.0-32-generic, it can't boot up as well. ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- 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/2061940 Title: Some DUTs can't boot up after installing the proposed kernel on Mantic Status in linux package in Ubuntu: In Progress Bug description: During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at very early stage of booting process. The last messages displayed on the screen are: EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Measured initrd data into PCR 9 There are no journal logs existed when it boot with the 6.5.0-33 kernel. Here is the list of the impacted machines that I found so far https://certification.canonical.com/hardware/202106-29206/ https://certification.canonical.com/hardware/202106-29207/ https://certification.canonical.com/hardware/201912-27623/ https://certification.canonical.com/hardware/202007-28059/ https://certification.canonical.com/hardware/202103-28762/ https://certification.canonical.com/hardware/202012-28510/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+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 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one
** Also affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-meta-oem-6.8 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-meta-oem-6.8 (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux-meta-oem-6.8 (Ubuntu Noble) Status: New => Triaged ** Changed in: linux-meta-oem-6.8 (Ubuntu Noble) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-meta (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux-meta (Ubuntu Noble) Status: New => Triaged ** Changed in: linux-meta (Ubuntu Noble) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2061747 Title: obsolete out-of-tree ivsc dkms in favor of in-tree one Status in ipu6-drivers package in Ubuntu: In Progress Status in ivsc-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-oem-6.8 package in Ubuntu: Triaged Status in linux-oem-6.8 package in Ubuntu: In Progress Status in ipu6-drivers source package in Noble: In Progress Status in ivsc-driver source package in Noble: Invalid Status in linux source package in Noble: In Progress Status in linux-meta source package in Noble: Triaged Status in linux-meta-oem-6.8 source package in Noble: Triaged Status in linux-oem-6.8 source package in Noble: In Progress Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The in-tree vsc driver as of v6.8 still needs a few fixes to achieve the same support level to launch Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules- ipu6-. Install the corresponding kernel/modules packages and test camera functions. [Where problems could occur] While this is the first time we switch to in-tree VSC driver, and the out-of-tree driver is not aligned at the time of transition and probably never will, the provided functions and verified stability issues may vary. [Other Info] The dkms is created to be compatible of multiple kernel versions, yet the in-tree vsc driver transitioning should only happen for kernel >= v6.8. That is, oem-6.8, noble and linux-unstable will be nominated. == original bug description == Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+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 2063096] [NEW] RTL8852BE fw security fail then lost WIFI function during suspend/resume cycle
Public bug reported: This is for tracking purpose ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Medium Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Medium Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Medium Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Tags: oem-priority originate-from-2056141 somerville ** Package changed: linux-firmware (Ubuntu) => linux-oem-6.5 (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Hui Wang (hui.wang) ** Tags added: oem-priority originate-from-2056141 somerville -- 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/2063096 Title: RTL8852BE fw security fail then lost WIFI function during suspend/resume cycle Status in HWE Next: New Status in linux 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.5 source package in Jammy: New Status in linux source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: New Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: New Bug description: This is for tracking purpose To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2063096/+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 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic
arm64.nopauth regulator_ignore_unused modprobe.blacklist=qcom_q6v5_pas are required to boot from usb, but then there is a problem with USB, resulting in an endless loop. -- 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/2060868 Title: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Noble: Confirmed Bug description: The last kernel that successfully boots on my Lenovo X13s system is 6.5.0-1004-laptop. With 6.8.0-20-generic no output whatsoever is shown. --- ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:zfsdt 2886 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-12-12 (120 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212) Lspci-vt: -[0002:00]---00.0-[01-ff]00.0 KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) -[0004:00]---00.0-[01-ff]00.0 Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] -[0006:00]---00.0-[01-ff]00.0 Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter MachineType: LENOVO 21BXCTO1WW Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash clk_ignore_unused pd_ignore_unused vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-1004-laptop N/A linux-backports-modules-6.5.0-1004-laptop N/A linux-firmware 20240318.git3b128b60-0ubuntu2 Tags: noble Uname: Linux 6.5.0-1004-laptop aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/05/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N3HET87W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN ptal8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1: dmi.product.family: ThinkPad X13s Gen 1 dmi.product.name: 21BXCTO1WW dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1 dmi.product.version: ThinkPad X13s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2063096] Re: RTL8852BE fw security fail then lost WIFI function during suspend/resume cycle
** Description changed: - This is for tracking purpose + [Impact] + + On a Dell laptop, When we do suspend/resume test, we found the + realtek wifi couldn't work after resume, from the dmesg, we found + the error log as below: + Log: + 三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: fw security fail + 三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: download firmware fail + 三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: [ERR]fwdl 0x1E0 = 0x62 + 三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: [ERR]fwdl 0x83F2 = 0x8 + + [Fix] + + Backport a commit from mainline kernel (linux-next), this will retry firmware + loading for 5 times. + + [Test Case] + + run suspend/resume test case for over 100 times, the wifi still + works. + + [Where problems could occur] + + This commit comes from mailine kernel, and it doesn't change existing + driver except loading firmware a couple of more times if there is an error. + In theory this will not introduce regression. ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid -- 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/2063096 Title: RTL8852BE fw security fail then lost WIFI function during suspend/resume cycle Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Status in linux source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] On a Dell laptop, When we do suspend/resume test, we found the realtek wifi couldn't work after resume, from the dmesg, we found the error log as below: Log: 三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: fw security fail 三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: download firmware fail 三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: [ERR]fwdl 0x1E0 = 0x62 三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: [ERR]fwdl 0x83F2 = 0x8 [Fix] Backport a commit from mainline kernel (linux-next), this will retry firmware loading for 5 times. [Test Case] run suspend/resume test case for over 100 times, the wifi still works. [Where problems could occur] This commit comes from mailine kernel, and it doesn't change existing driver except loading firmware a couple of more times if there is an error. In theory this will not introduce regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2063096/+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 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
> I don't think we can justify dropping FAN support in an SRU, so let's add that port back in. Even if it will not be used in Ubuntu 24.04, and dropping these patches would stop the diversion with Debian? > @matttbe - is there any documentation about upstream compatibility guarantees > and regression testing done that you're aware of, or any tests that we could > run beyond those in our autopkgtests? @dannf: IPRoute2 is following the kernel development, and it is not supposed to break the compatibility with older kernel versions (also because the kernel's user API is not supposed to break). There is a test suite included in the source code, but it looks like it is not tested when building the .deb package, check the 'debian/rules' file: override_dh_auto_test: # upstream test suite needs root and leaves machine unclean, skip it I never used it, (and it looks like it is not often updated), but IPRoute2 (ip, tc, ss, etc.) is also heavily used in the kernel selftests: $ git grep -cw -e ip -e tc -e ss -- tools/testing/selftests/ | wc -l 635 Maybe these tests are already being validated when building a new kernel for Ubuntu? That's another way to validate IPRoute2. Other than that, Debian is using IPRoute2 versions > 6.1 for a long time now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/2051672 Title: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) Status in iproute2 package in Ubuntu: Incomplete Bug description: iproute2 upstream produces releases coinciding with upstream kernel releases to support the latest kernel features. Noble's iproute2 is still back at v6.1 even though it will use the v6.8 kernel. This means we provide no userspace interface for newer features - some of which are noted by a networking hardware partner in bug 2060969. Ubuntu's iproute2 has diverged from Debian's to add support for Ubuntu FAN. Noble has dropped kernel support for Ubuntu FAN, so those are no longer needed, and we could now just do a merge. We could also port the FAN patches forward if we can identify a need (see the original description of this bug to a link to such a port), but I have not done any testing with that. I have built Debian's iproute2 in a noble ppa at ppa:dannf/test and smoke tested it on an amd64 virtual machine: ubuntu@cortez-vm-0:~$ sudo dpkg -i iproute2_6.8.0-1~24.04.1_amd64.deb (Reading database ... 83134 files and directories currently installed.) Preparing to unpack iproute2_6.8.0-1~24.04.1_amd64.deb ... Unpacking iproute2 (6.8.0-1~24.04.1) over (6.1.0-1ubuntu6) ... dpkg: warning: unable to delete old directory '/etc/iproute2/rt_tables.d': Directory not empty dpkg: warning: unable to delete old directory '/etc/iproute2/rt_protos.d': Directory not empty dpkg: warning: unable to delete old directory '/etc/iproute2': Directory not empty Setting up iproute2 (6.8.0-1~24.04.1) ... Removing obsolete conffile /etc/iproute2/group ... Removing obsolete conffile /etc/iproute2/rt_realms ... Removing obsolete conffile /etc/iproute2/rt_scopes ... Removing obsolete conffile /etc/iproute2/rt_tables ... Removing obsolete conffile /etc/iproute2/rt_tables.d/README ... Removing obsolete conffile /etc/iproute2/rt_protos.d/README ... Removing obsolete conffile /etc/iproute2/rt_protos ... Removing obsolete conffile /etc/iproute2/rt_dsfield ... Removing obsolete conffile /etc/iproute2/nl_protos ... Removing obsolete conffile /etc/iproute2/ematch_map ... Removing obsolete conffile /etc/iproute2/bpf_pinning ... Processing triggers for man-db (2.12.0-4build1) ... The system rebooted fine. The ip command seems to behave normally. Since the upstream test suite only appears to run at autopkgtest time, I triggered a run in my PPA, and it passed: https://autopkgtest.ubuntu.com/results/autopkgtest-noble-dannf-test/noble/amd64/i/iproute2/20240412_210819_97417@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+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 2060373] Re: package linux-generic-hwe-22.04 6.5.0.26.26 failed to install/upgrade: 의존성 문제 - 설정하지 않고 남겨둠
/etc/kernel/header_postinst.d/dkms:
* dkms: running auto installation service for kernel 6.5.0-26-generic
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der
Error! The directory /var/lib/dkms/nvidia/535.154.05/source does not appear to
have module source located within it.
Build halted.
dkms autoinstall on 6.5.0-26-generic/x86_64 failed for nvidia(8)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
* dkms: autoinstall for kernel 6.5.0-26-generic
...fail!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
--
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/2060373
Title:
package linux-generic-hwe-22.04 6.5.0.26.26 failed to install/upgrade:
의존성 문제 - 설정하지 않고 남겨둠
Status in linux package in Ubuntu:
New
Bug description:
This occured while system updater installing packages with no user
operation.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-generic-hwe-22.04 6.5.0.26.26
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jungwonyong 2613 F wireplumber
/dev/snd/controlC0: jungwonyong 2613 F wireplumber
/dev/snd/seq:jungwonyong 2607 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sun Apr 7 12:08:46 2024
ErrorMessage: 의존성 문제 - 설정하지 않고 남겨둠
InstallationDate: Installed on 2024-01-25 (73 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ricifp@/vmlinuz-6.5.0-21-generic
root=ZFS=rpool/ROOT/ubuntu_ricifp ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-generic-hwe-22.04 6.5.0.26.26 failed to install/upgrade:
의존성 문제 - 설정하지 않고 남겨둠
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/08/2021
dmi.bios.release: 16.20
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1620
dmi.board.asset.tag: Default string
dmi.board.name: PRIME H470-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1620:bd07/08/2021:br16.20:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH470-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060373/+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 2045560] Re: TCP memory leak, slow network (arm64)
Hi Jonathan, Thanks for all the information and the deep dive into this issue! Please post the link to the kernel bug report here when it's ready. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-aws-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045560 Title: TCP memory leak, slow network (arm64) Status in linux-signed-aws-6.2 package in Ubuntu: Confirmed Bug description: Hello! 👋 We have Ubuntu OS-based servers running in both AWS and Azure clouds. These servers are handling thousands of connections, and we've been experiencing issues with TCP memory usage since upgrading to Ubuntu 22.04.3 from 22.04.2. $ cat /proc/net/sockstat sockets: used 6642 TCP: inuse 5962 orphan 0 tw 292 alloc 6008 mem 128989 UDP: inuse 5 mem 0 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 As shown in the output below, even after stopping all possible services and closing all open connections, the TCP memory usage remains high and only decreases very slowly. $ cat /proc/net/sockstat sockets: used 138 TCP: inuse 2 orphan 0 tw 0 alloc 3 mem 128320 UDP: inuse 3 mem 0 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 I have attached a screenshot of linear TCP memory usage growth, which we believe may indicate a TCP memory leak When net.ipv4.tcp_mem limit is reached, it causes network slowdown We've never had these issues before, and the only solution we've found so far is to reboot the node. Do you have any suggestions on how to troubleshoot further? Thank you for any help or guidance you can provide! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-1015-aws 6.2.0-1015.15~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-1015.15~22.04.1-aws 6.2.16 Uname: Linux 6.2.0-1015-aws aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: aws CloudName: aws CloudPlatform: ec2 CloudRegion: us-west-2 CloudSubPlatform: metadata (http://169.254.169.254) Date: Mon Dec 4 13:13:08 2023 Ec2AMI: ami-095a68e28e781dfe1 Ec2AMIManifest: (unknown) Ec2Architecture: arm64 Ec2AvailabilityZone: us-west-2b Ec2Imageid: ami-095a68e28e781dfe1 Ec2InstanceType: m7g.large Ec2Instancetype: m7g.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Ec2Region: us-west-2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-aws-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-aws-6.2/+bug/2045560/+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 2060648] Re: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/cpupower', which is also in package linux-laptop-tools-common 6.
*** This bug is a duplicate of bug 2048183 ***
https://bugs.launchpad.net/bugs/2048183
** This bug has been marked a duplicate of bug 2048183
Don't produce linux-*-cloud-tools-common, linux-*-tools-common and
linux-*-tools-host binary packages
--
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/2060648
Title:
package linux-tools-common (not installed) failed to install/upgrade:
trying to overwrite '/usr/bin/cpupower', which is also in package
linux-laptop-tools-common 6.5.0-1006.9
Status in linux package in Ubuntu:
New
Bug description:
Tried to fix a package with broken dependencies.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-tools-common (not installed)
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
AptOrdering:
linux-tools-common:amd64: Install
NULL: ConfigurePending
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
Date: Tue Apr 9 12:21:01 2024
DpkgTerminalLog:
Preparing to unpack .../linux-tools-common_6.5.0-9.9_all.deb ...
Unpacking linux-tools-common (6.5.0-9.9) ...
[1mdpkg:[0m error processing archive
/var/cache/apt/archives/linux-tools-common_6.5.0-9.9_all.deb (--unpack):
trying to overwrite '/usr/bin/cpupower', which is also in package
linux-laptop-tools-common 6.5.0-1006.9
ErrorMessage: trying to overwrite '/usr/bin/cpupower', which is also in
package linux-laptop-tools-common 6.5.0-1006.9
InstallationDate: Installed on 2024-04-02 (7 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=4ca7785f-3fe8-4c99-b94a-44af5edc308a ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-tools-common (not installed) failed to install/upgrade:
trying to overwrite '/usr/bin/cpupower', which is also in package
linux-laptop-tools-common 6.5.0-1006.9
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/15/2023
dmi.bios.release: 1.11
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: N.1.20MBB11
dmi.board.asset.tag: Standard
dmi.board.name: X565
dmi.board.vendor: MAIBENBEN
dmi.board.version: Standard
dmi.chassis.asset.tag: Standard
dmi.chassis.type: 10
dmi.chassis.vendor: Standard
dmi.chassis.version: Standard
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrN.1.20MBB11:bd08/15/2023:br1.11:efr1.25:svnMAIBENBEN:pnTyphoonSeries:pvrStandard:rvnMAIBENBEN:rnX565:rvrStandard:cvnStandard:ct10:cvrStandard:skuX565:
dmi.product.family: RMB
dmi.product.name: Typhoon Series
dmi.product.sku: X565
dmi.product.version: Standard
dmi.sys.vendor: MAIBENBEN
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060648/+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 2060591] Re: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/cpupower', which is also in package linux-laptop-tools-common 6.
*** This bug is a duplicate of bug 2048183 ***
https://bugs.launchpad.net/bugs/2048183
** This bug has been marked a duplicate of bug 2048183
Don't produce linux-*-cloud-tools-common, linux-*-tools-common and
linux-*-tools-host binary packages
--
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/2060591
Title:
package linux-tools-common (not installed) failed to install/upgrade:
trying to overwrite '/usr/bin/cpupower', which is also in package
linux-laptop-tools-common 6.5.0-1006.9
Status in linux package in Ubuntu:
New
Bug description:
Just tried to install linux-tools-common
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-tools-common (not installed)
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
AptOrdering:
linux-tools-common:amd64: Install
NULL: ConfigurePending
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
Date: Tue Apr 9 04:46:01 2024
DpkgTerminalLog:
Preparing to unpack .../linux-tools-common_6.5.0-27.28_all.deb ...
Unpacking linux-tools-common (6.5.0-27.28) ...
[1mdpkg:[0m error processing archive
/var/cache/apt/archives/linux-tools-common_6.5.0-27.28_all.deb (--unpack):
trying to overwrite '/usr/bin/cpupower', which is also in package
linux-laptop-tools-common 6.5.0-1006.9
ErrorMessage: trying to overwrite '/usr/bin/cpupower', which is also in
package linux-laptop-tools-common 6.5.0-1006.9
InstallationDate: Installed on 2024-04-02 (6 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=4ca7785f-3fe8-4c99-b94a-44af5edc308a ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-tools-common (not installed) failed to install/upgrade:
trying to overwrite '/usr/bin/cpupower', which is also in package
linux-laptop-tools-common 6.5.0-1006.9
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/15/2023
dmi.bios.release: 1.11
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: N.1.20MBB11
dmi.board.asset.tag: Standard
dmi.board.name: X565
dmi.board.vendor: MAIBENBEN
dmi.board.version: Standard
dmi.chassis.asset.tag: Standard
dmi.chassis.type: 10
dmi.chassis.vendor: Standard
dmi.chassis.version: Standard
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrN.1.20MBB11:bd08/15/2023:br1.11:efr1.25:svnMAIBENBEN:pnTyphoonSeries:pvrStandard:rvnMAIBENBEN:rnX565:rvrStandard:cvnStandard:ct10:cvrStandard:skuX565:
dmi.product.family: RMB
dmi.product.name: Typhoon Series
dmi.product.sku: X565
dmi.product.version: Standard
dmi.sys.vendor: MAIBENBEN
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060591/+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 2060428] Re: package linux-tools-common 5.15.0-101.111 failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common
*** This bug is a duplicate of bug 2048183 *** https://bugs.launchpad.net/bugs/2048183 ** This bug has been marked a duplicate of bug 2048183 Don't produce linux-*-cloud-tools-common, linux-*-tools-common and linux-*-tools-host binary packages -- 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/2060428 Title: package linux-tools-common 5.15.0-101.111 failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1051.57 Status in linux package in Ubuntu: New Bug description: Unpacking linux-modules-nvidia-535-generic-hwe-22.04 (6.5.0-27.28~22.04.1) over (6.5.0-26.26~22.04.1+1) ... Preparing to unpack .../21-linux-tools-common_5.15.0-102.112_all.deb ... Unpacking linux-tools-common (5.15.0-102.112) over (5.15.0-101.111) ... dpkg: error processing archive /tmp/apt-dpkg-install-KxZylP/21-linux-tools-commo n_5.15.0-102.112_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-io tg-tools-common 5.15.0-1051.57 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /tmp/apt-dpkg-install-KxZylP/21-linux-tools-common_5.15.0-102.112_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-tools-common 5.15.0-101.111 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: boul-iisc 2346 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Mon Apr 8 11:24:23 2024 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1051.57 InstallationDate: Installed on 2024-01-11 (88 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Dell Inc. XPS 15 9530 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic root=UUID=bb015bf7-1f70-468a-9510-ceb36baafb05 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 SourcePackage: linux Title: package linux-tools-common 5.15.0-101.111 failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1051.57 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2023 dmi.bios.release: 1.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 01WV13 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd12/18/2023:br1.10:efr1.4:svnDellInc.:pnXPS159530:pvr:rvnDellInc.:rn01WV13:rvrA00:cvnDellInc.:ct10:cvr:sku0BEB: dmi.product.family: XPS dmi.product.name: XPS 15 9530 dmi.product.sku: 0BEB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060428/+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 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic
The daily x13s images are broken. I'm working on it. -- 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/2060868 Title: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Noble: Confirmed Bug description: The last kernel that successfully boots on my Lenovo X13s system is 6.5.0-1004-laptop. With 6.8.0-20-generic no output whatsoever is shown. --- ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:zfsdt 2886 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-12-12 (120 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212) Lspci-vt: -[0002:00]---00.0-[01-ff]00.0 KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) -[0004:00]---00.0-[01-ff]00.0 Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] -[0006:00]---00.0-[01-ff]00.0 Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter MachineType: LENOVO 21BXCTO1WW Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash clk_ignore_unused pd_ignore_unused vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-1004-laptop N/A linux-backports-modules-6.5.0-1004-laptop N/A linux-firmware 20240318.git3b128b60-0ubuntu2 Tags: noble Uname: Linux 6.5.0-1004-laptop aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/05/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N3HET87W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN ptal8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1: dmi.product.family: ThinkPad X13s Gen 1 dmi.product.name: 21BXCTO1WW dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1 dmi.product.version: ThinkPad X13s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2062562] Re: Keyboard not working after resume from suspend on Dell XPS 13 laptop
It seems that this is already fixed with 6.5.0-28-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2062562 Title: Keyboard not working after resume from suspend on Dell XPS 13 laptop Status in linux-signed package in Ubuntu: New Bug description: After upgrade to 6.5.0-27-generic keyboard stopped working when laptop comes back to life after suspend. When booted with 6.5.0-26-generic everything is fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2062562/+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 2063106] [NEW] After upgrading to linux-generic-hwe-22.04 | 6.5.0.28.29~22.04.1 I'm getting hogged CPU errors
Public bug reported: This is my first bug report so please be nice if I made any mistakes. Recently I upgraded packages of my ubuntu 22.04 VM inside of the Vmware Workstation Pro 17. And after the upgrade I'm getting these errors: ``` Apr 22 09:56:06 zwx1309229-virtual-machine kernel: [ 904.562306] workqueue: e1000_watchdog [e1000] hogged CPU for >1us 4 times, consider switching to WQ_UNBOUND Apr 22 09:56:07 zwx1309229-virtual-machine kernel: [ 905.686250] workqueue: blk_mq_run_work_fn hogged CPU for >1us 4 times, consider switching to WQ_UNBOUND ``` ``` zwx1309229@zwx1309229-virtual-machine:~$ sudo apt list | grep hwe | grep installed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-generic-hwe-22.04/jammy-updates,jammy-security,now 6.5.0.28.29~22.04.1 amd64 [installed] linux-headers-generic-hwe-22.04/jammy-updates,jammy-security,now 6.5.0.28.29~22.04.1 amd64 [installed,automatic] linux-hwe-6.5-headers-6.5.0-27/jammy-updates,jammy-updates,jammy-security,jammy-security,now 6.5.0-27.28~22.04.1 all [installed,automatic] linux-hwe-6.5-headers-6.5.0-28/jammy-updates,jammy-updates,jammy-security,jammy-security,now 6.5.0-28.29~22.04.1 all [installed,automatic] linux-image-generic-hwe-22.04/jammy-updates,jammy-security,now 6.5.0.28.29~22.04.1 amd64 [installed,automatic] systemd-hwe-hwdb/jammy-updates,jammy-updates,now 249.11.5 all [installed,automatic] ``` ``` zwx1309229@zwx1309229-virtual-machine:~$ uname -a Linux zwx1309229-virtual-machine 6.5.0-28-generic #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 4 14:39:20 UTC 2 x86_64 x86_64 x86_64 GNU/Linux ``` After these logs appear on my /var/log/kern.log the VM freezes and needs to be restarted from the VMware console. ** Affects: linux-signed-hwe-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2063106 Title: After upgrading to linux-generic-hwe-22.04 | 6.5.0.28.29~22.04.1 I'm getting hogged CPU errors Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: This is my first bug report so please be nice if I made any mistakes. Recently I upgraded packages of my ubuntu 22.04 VM inside of the Vmware Workstation Pro 17. And after the upgrade I'm getting these errors: ``` Apr 22 09:56:06 zwx1309229-virtual-machine kernel: [ 904.562306] workqueue: e1000_watchdog [e1000] hogged CPU for >1us 4 times, consider switching to WQ_UNBOUND Apr 22 09:56:07 zwx1309229-virtual-machine kernel: [ 905.686250] workqueue: blk_mq_run_work_fn hogged CPU for >1us 4 times, consider switching to WQ_UNBOUND ``` ``` zwx1309229@zwx1309229-virtual-machine:~$ sudo apt list | grep hwe | grep installed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-generic-hwe-22.04/jammy-updates,jammy-security,now 6.5.0.28.29~22.04.1 amd64 [installed] linux-headers-generic-hwe-22.04/jammy-updates,jammy-security,now 6.5.0.28.29~22.04.1 amd64 [installed,automatic] linux-hwe-6.5-headers-6.5.0-27/jammy-updates,jammy-updates,jammy-security,jammy-security,now 6.5.0-27.28~22.04.1 all [installed,automatic] linux-hwe-6.5-headers-6.5.0-28/jammy-updates,jammy-updates,jammy-security,jammy-security,now 6.5.0-28.29~22.04.1 all [installed,automatic] linux-image-generic-hwe-22.04/jammy-updates,jammy-security,now 6.5.0.28.29~22.04.1 amd64 [installed,automatic] systemd-hwe-hwdb/jammy-updates,jammy-updates,now 249.11.5 all [installed,automatic] ``` ``` zwx1309229@zwx1309229-virtual-machine:~$ uname -a Linux zwx1309229-virtual-machine 6.5.0-28-generic #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 4 14:39:20 UTC 2 x86_64 x86_64 x86_64 GNU/Linux ``` After these logs appear on my /var/log/kern.log the VM freezes and needs to be restarted from the VMware console. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2063106/+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 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic
** Tags added: kern-10582 -- 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/2060868 Title: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Noble: Confirmed Bug description: The last kernel that successfully boots on my Lenovo X13s system is 6.5.0-1004-laptop. With 6.8.0-20-generic no output whatsoever is shown. --- ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:zfsdt 2886 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-12-12 (120 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212) Lspci-vt: -[0002:00]---00.0-[01-ff]00.0 KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) -[0004:00]---00.0-[01-ff]00.0 Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] -[0006:00]---00.0-[01-ff]00.0 Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter MachineType: LENOVO 21BXCTO1WW Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash clk_ignore_unused pd_ignore_unused vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-1004-laptop N/A linux-backports-modules-6.5.0-1004-laptop N/A linux-firmware 20240318.git3b128b60-0ubuntu2 Tags: noble Uname: Linux 6.5.0-1004-laptop aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/05/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N3HET87W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN ptal8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1: dmi.product.family: ThinkPad X13s Gen 1 dmi.product.name: 21BXCTO1WW dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1 dmi.product.version: ThinkPad X13s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic
** Tags added: kern-10583 ** Tags removed: kern-10582 -- 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/2060868 Title: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Noble: Confirmed Bug description: The last kernel that successfully boots on my Lenovo X13s system is 6.5.0-1004-laptop. With 6.8.0-20-generic no output whatsoever is shown. --- ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:zfsdt 2886 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-12-12 (120 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s (20231212) Lspci-vt: -[0002:00]---00.0-[01-ff]00.0 KIOXIA Corporation NVMe SSD Controller BG5 (DRAM-less) -[0004:00]---00.0-[01-ff]00.0 Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] -[0006:00]---00.0-[01-ff]00.0 Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter MachineType: LENOVO 21BXCTO1WW Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 msmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash clk_ignore_unused pd_ignore_unused vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3 RelatedPackageVersions: linux-restricted-modules-6.5.0-1004-laptop N/A linux-backports-modules-6.5.0-1004-laptop N/A linux-firmware 20240318.git3b128b60-0ubuntu2 Tags: noble Uname: Linux 6.5.0-1004-laptop aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/05/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N3HET87W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN ptal8 dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1: dmi.product.family: ThinkPad X13s Gen 1 dmi.product.name: 21BXCTO1WW dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1 dmi.product.version: ThinkPad X13s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2060458] Re: ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap
hi canonical team , can you please update the target on which this issue is reproduced and the release image information to the bug description. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2060458 Title: ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: Hello, I see the following messages keeps being logged in /var/log/syslog: ``` Apr 8 10:03:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument Apr 8 10:03:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap Apr 8 10:04:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument Apr 8 10:04:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap Apr 8 10:05:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument Apr 8 10:05:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap Apr 8 10:06:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument Apr 8 10:06:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap Apr 8 10:07:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument Apr 8 10:07:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap Apr 8 10:08:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument Apr 8 10:08:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap Apr 8 10:08:48 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument Apr 8 10:08:48 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap Apr 8 10:08:48 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument Apr 8 10:08:48 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap Apr 8 10:09:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument Apr 8 10:09:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap Apr 8 10:10:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument Apr 8 10:10:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap Apr 8 10:11:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument Apr 8 10:11:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap Apr 8 10:12:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument Apr 8 10:12:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap Apr 8 10:13:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument Apr 8 10:13:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap Apr 8 10:14:00 kria /usr/libexec/gdm-x-session[1419]: (WW) ARMSOC(0): flip queue failed: Invalid argument Apr 8 10:14:00 kria /usr/libexec/gdm-x-session[1419]: (EE) ARMSOC(0): [DRI2] DRI2SwapBuffers: driver failed to schedule swap ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7.22.04.4 ProcVersionSignature: Ubuntu 5.15.0-1027.31-xilinx-zynqmp 5.15.136 Uname: Linux 5.15.0-1027-xilinx-zynqmp aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: config-disk (/dev/mmcblk1p1) Date: Mon Apr 8 10:15:18 2024 ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2023-09-20T10:06:31 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2060458/+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 2060984] Re: FFe: New firmware release
** Tags added: kern-10585 -- 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/2060984 Title: FFe: New firmware release Status in linux-firmware package in Ubuntu: New Bug description: A new upstream release of linux-firmware was tagged on 2024.04.10, this would sync us with that. Changes: - imx: sdma: update firmware to v3.6/v4.6 - linux-firmware: mediatek: Update MT8173 VPU firmware to v1.1.8 - amdgpu: DMCUB updates for various AMDGPU ASICs - Intel Bluetooth: Update firmware file for Intel Bluetooth 9260 - Intel Bluetooth: Update firmware file for Intel Bluetooth 9560 - Intel Bluetooth: Update firmware file for Intel Bluetooth AX201 - Intel Bluetooth: Update firmware file for Intel Bluetooth AX200 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX210 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX211 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX211 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX101 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX101 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX211 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX101 - Intel Bluetooth: Update firmware file for Intel Bluetooth BE200 - WHENCE: Link the Raspberry Pi CM4 and 5B to the 4B - Montage: update firmware for Mont-TSSE - linux-firmware: Add firmware for Cirrus CS35L56 for Dell laptops - rtw88: Add RTL8703B firmware v11.0.0 - rtw89: 8922a: add firmware v0.35.18.0 - rtw89: 8852c: update fw to v0.27.56.14 - mekdiatek: Update mt8186 SOF firmware to v2.0.1 - linux-firmware: update firmware for en8811h 2.5G ethernet phy - amdgpu: DMCUB updates for various AMDGPU ASICs - i915: Add DG2 HuC 7.10.15 - ath10k: WCN3990: hw1.0: move firmware back from qcom/ location - ath10k: WCN3990: hw1.0: add qcm2290 firmware API file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2060984/+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 2060904] Re: Fix the RTL8852CE BT FW Crash based on SER false alarm
** Tags added: kern-10584 -- 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/2060904 Title: Fix the RTL8852CE BT FW Crash based on SER false alarm Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: New Status in linux-oem-6.8 source package in Jammy: Invalid Status in linux source package in Mantic: New Status in linux-firmware source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux-oem-6.8 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-firmware source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Status in linux-oem-6.8 source package in Noble: New Bug description: This is SRU template for linux kernel: [Impact] On a Dell laptop, let it connect to a WiFi router, connect a BT device, then disconnect it, connect the bt device again, we expect the device could be connected successfully, but it couldn't and the BT firmeware crashed. [Fix] Need to upgrade the firmware for RTL8852CE and cherry-pick 2 kernel patches, here we send the MR for 2 kernel patches. The firmware PR was already sent out. And one of the patches is from linux-next, the other is from rtw.git and is going to be merged to linux-next soon. [Test Case] With the upgraded firmware + kernel with the 2 kernel patches, bt firmware will not crash anymore and bt could connect / disconnect many many bt devices. [Where problems could occur] This MR comes from upstream commits, it has low possibility to introduce regression. If the bt or wifi on this laptop couldn't work as well as before, it is possible that this MR introduces regression. According to our test, the wifi and bt could work well with upgraded firmware. === This SRU template is for linux-firmware: BugLink: https://bugs.launchpad.net/bugs/2060904 [Impact] On a Dell laptop, let it connect to a WiFi router, connect a BT device, then disconnect it, connect the bt device again, we expect the device could be connected successfully, but it couldn't and the BT firmeware crashed. [Fix] Need to upgrade the firmware for RTL8852CE and cherry-pick 2 kernel patches, here we send the MR for firmware first. And it is backward compatible, the upgraded firmware could work with kernel without those 2 patches as well as before. [Test Case] With the upgraded firmware + kernel without the 2 kernel patches, the wifi and bt could work as well / bad as before. With the upgraded firmware + kernel with the 2 kernel patches, bt firmware will not crash anymore and bt could connect / disconnect many many bt devices. [Where problems could occur] This MR comes from upstream commit, it has low possibility to introduce regression. If the bt or wifi on this laptop couldn't work as well as before, it is possible that this MR introduces regression. According to our test, the wifi and bt could work well with upgraded firmware. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2060904/+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 2060989] Re: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to install/upgrade: installed linux-headers-6.5.0-27-generic package post-installation script subprocess r
nvidia-fs/2.19.6 is not an Ubuntu DKMS. How did you install it, where
did you get it from? You need to install nvidia-fs-dkms from the
archive.
--
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/2060989
Title:
package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to
install/upgrade: installed linux-headers-6.5.0-27-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
In Progress
Bug description:
-
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-27-generic 6.5.0-27.28
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nela 2694 F wireplumber
/dev/snd/controlC1: nela 2694 F wireplumber
/dev/snd/seq:nela 2674 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu Apr 11 10:13:36 2024
ErrorMessage: installed linux-headers-6.5.0-27-generic package
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2024-03-30 (12 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=e960f11c-d239-429e-97af-9073de7f3b3a ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to
install/upgrade: installed linux-headers-6.5.0-27-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/02/2021
dmi.bios.release: 1.27
dmi.bios.vendor: LENOVO
dmi.bios.version: HACN27WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion S7 15ACH6
dmi.ec.firmware.release: 1.27
dmi.modalias:
dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:
dmi.product.family: Legion S7 15ACH6
dmi.product.name: 82K8
dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6
dmi.product.version: Legion S7 15ACH6
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060989/+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 2060989] Re: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to install/upgrade: installed linux-headers-6.5.0-27-generic package post-installation script subprocess r
* dkms: running auto installation service for kernel 6.5.0-27-generic
Deprecated feature: REMAKE_INITRD
(/var/lib/dkms/nvidia-fs/2.19.6/source/dkms.conf)
Deprecated feature: REMAKE_INITRD
(/var/lib/dkms/nvidia-fs/2.19.6/source/dkms.conf)
nvidia-fs/2.19.6 autoinstall failed due to missing dependencies: nvidia
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
* dkms: autoinstall for kernel 6.5.0-27-generic
...fail!
--
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/2060989
Title:
package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to
install/upgrade: installed linux-headers-6.5.0-27-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
In Progress
Bug description:
-
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-27-generic 6.5.0-27.28
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nela 2694 F wireplumber
/dev/snd/controlC1: nela 2694 F wireplumber
/dev/snd/seq:nela 2674 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu Apr 11 10:13:36 2024
ErrorMessage: installed linux-headers-6.5.0-27-generic package
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2024-03-30 (12 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=e960f11c-d239-429e-97af-9073de7f3b3a ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to
install/upgrade: installed linux-headers-6.5.0-27-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/02/2021
dmi.bios.release: 1.27
dmi.bios.vendor: LENOVO
dmi.bios.version: HACN27WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion S7 15ACH6
dmi.ec.firmware.release: 1.27
dmi.modalias:
dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:
dmi.product.family: Legion S7 15ACH6
dmi.product.name: 82K8
dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6
dmi.product.version: Legion S7 15ACH6
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060989/+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 2060142] Re: Jammy update: v5.15.150 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060142 Title: Jammy update: v5.15.150 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.150 upstream stable release from git://git.kernel.org/ net/sched: Retire CBQ qdisc UBUNTU: [Config] updateconfigs for NET_SCH_CBQ net/sched: Retire ATM qdisc UBUNTU: [Config] updateconfigs for NET_SCH_ATM net/sched: Retire dsmark qdisc UBUNTU: [Config] updateconfigs for NET_SCH_DSMARK smb: client: fix potential OOBs in smb2_parse_contexts() smb: client: fix parsing of SMB3.1.1 POSIX create context sched/rt: sysctl_sched_rr_timeslice show default timeslice after reset PCI: dwc: Fix a 64bit bug in dw_pcie_ep_raise_msix_irq() bpf: Merge printk and seq_printf VARARG max macros bpf: Add struct for bin_args arg in bpf_bprintf_prepare bpf: Do cleanup in bpf_bprintf_cleanup only when needed bpf: Remove trace_printk_lock userfaultfd: fix mmap_changing checking in mfill_atomic_hugetlb zonefs: Improve error handling x86/fpu: Stop relying on userspace for info to fault in xsave buffer sched/rt: Fix sysctl_sched_rr_timeslice intial value sched/rt: Disallow writing invalid values to sched_rt_period_us scsi: target: core: Add TMF to tmr_list handling dmaengine: shdma: increase size of 'dev_id' dmaengine: fsl-qdma: increase size of 'irq_name' wifi: cfg80211: fix missing interfaces when dumping wifi: mac80211: fix race condition on enabling fast-xmit fbdev: savage: Error out if pixclock equals zero fbdev: sis: Error out if pixclock equals zero spi: hisi-sfc-v3xx: Return IRQ_NONE if no interrupts were detected ahci: asm1166: correct count of reported ports ahci: add 43-bit DMA address quirk for ASMedia ASM1061 controllers MIPS: reserve exception vector space ONLY ONCE platform/x86: touchscreen_dmi: Add info for the TECLAST X16 Plus tablet ext4: avoid dividing by 0 in mb_update_avg_fragment_size() when block bitmap corrupt ext4: avoid allocating blocks from corrupted group in ext4_mb_try_best_found() ext4: avoid allocating blocks from corrupted group in ext4_mb_find_by_goal() dmaengine: ti: edma: Add some null pointer checks to the edma_probe regulator: pwm-regulator: Add validity checks in continuous .get_voltage nvmet-tcp: fix nvme tcp ida memory leak ALSA: usb-audio: Check presence of valid altsetting control ASoC: sunxi: sun4i-spdif: Add support for Allwinner H616 spi: sh-msiof: avoid integer overflow in constants Input: xpad - add Lenovo Legion Go controllers netfilter: conntrack: check SCTP_CID_SHUTDOWN_ACK for vtag setting in sctp_new ALSA: usb-audio: Ignore clock selector errors for single connection nvme-fc: do not wait in vain when unloading module nvmet-fcloop: swap the list_add_tail arguments nvmet-fc: release reference on target port nvmet-fc: defer cleanup using RCU properly nvmet-fc: hold reference on hostport match nvmet-fc: abort command when there is no binding nvmet-fc: avoid deadlock on delete association path nvmet-fc: take ref count on tgtport before delete assoc ext4: correct the hole length returned by ext4_map_blocks() Input: i8042 - add Fujitsu Lifebook U728 to i8042 quirk table fs/ntfs3: Modified fix directory element type detection fs/ntfs3: Improve ntfs_dir_count fs/ntfs3: Correct hard links updating when dealing with DOS names fs/ntfs3: Print warning while fixing hard links count fs/ntfs3: Fix detected field-spanning write (size 8) of single field "le->name" fs/ntfs3: Add NULL ptr dereference checking at the end of attr_allocate_frame() fs/ntfs3: Disable ATTR_LIST_ENTRY size check fs/ntfs3: use non-movable memory for ntfs3 MFT buffer cache fs/ntfs3: Prevent generic message "attempt to access beyond end of device" fs/ntfs3: Correct function is_rst_area_valid fs/ntfs3: Update inode->i_size after success write into compressed file fs/ntfs3: Fix oob in ntfs_listxattr wifi: mac80211: adding missing drv_mgd_complete_tx() call efi: runtime: Fix potential overflow of soft-reserved region size efi: Don't add memblocks for soft-reserved memory hwmon: (coretemp) Enlarge per package core count limit scsi: lpfc: Use unsigned type for num_sge firewire: core: send bu
[Kernel-packages] [Bug 2061087] Re: Conflict with linux-laptop-tools-common
*** This bug is a duplicate of bug 2048183 *** https://bugs.launchpad.net/bugs/2048183 linux-laptop-tools-common should not exist. Please purge it. In fact you should not have any linux-laptop packages installed unless you have an X13s laptop. ** This bug has been marked a duplicate of bug 2048183 Don't produce linux-*-cloud-tools-common, linux-*-tools-common and linux-*-tools-host binary packages -- 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/2061087 Title: Conflict with linux-laptop-tools-common Status in linux package in Ubuntu: New Bug description: Doing an apt upgrade on Noble today, linux-tools-common is attempting to overwrite /usr/bin/cpupower, which is also provided by linux- laptop-tools-common: ---> Vorbereitung zum Entpacken von .../310-linux-tools-common_6.8.0-22.22_all.deb ... Entpacken von linux-tools-common (6.8.0-22.22) ... dpkg: Fehler beim Bearbeiten des Archivs /tmp/apt-dpkg-install-GERI65/310-linux-tools-common_6.8.0-22.22_all.deb (--unpack): Versuch, »/usr/bin/cpupower« zu überschreiben, welches auch in Paket linux-laptop-tools-common 6.5.0-1004.7 ist dpkg-deb: Fehler: »einfügen«-Unterprozess wurde durch Signal (Broken pipe) getötet <--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061087/+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 2062502] Re: linux-firmware package breaks iwlwifi
** Tags added: kern-10588 -- 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/2062502 Title: linux-firmware package breaks iwlwifi Status in linux-firmware package in Ubuntu: New Bug description: This package version works: 20230919.git3672ccab-0ubuntu2.1 This one causes firmware SW errors and resets - breaking wifi in iwlwifi driver: 20230919.git3672ccab-0ubuntu2.9 I am running 23.10 with "Tiger Lake PCH CNVi WiFi" and after upgrade to ...2.9 of the linux-firmware package, I saw many errors that begin like this in syslog: 2024-04-18T22:30:20.975204-07:00 stormy kernel: [ 886.503389] iwlwifi :00:14.3: Queue 1 is stuck 0 12 2024-04-18T22:30:20.979152-07:00 stormy kernel: [ 886.503652] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. 2024-04-18T22:30:20.979167-07:00 stormy kernel: [ 886.503764] iwlwifi :00:14.3: Start IWL Error Log Dump: 2024-04-18T22:30:20.979169-07:00 stormy kernel: [ 886.503768] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 2024-04-18T22:30:20.979170-07:00 stormy kernel: [ 886.503772] iwlwifi :00:14.3: Loaded firmware version: 77.2df8986f.0 QuZ-a0-hr-b0-77.ucode Downgrading to ..2.1 version of linux-firmware fixes wifi and I see no errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2062502/+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 2062518] Re: package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to install/upgrade: installed linux-headers-6.5.0-28-generic package post-installation script subprocess r
Building module:
Cleaning build area...
'make' -C src/ KERNELDIR=/lib/modules/6.5.0-28-generic/build all...(bad exit
status: 2)
ERROR (dkms apport): binary package for r8125: 9.004.01 not found
Error! Bad return status for module build on kernel: 6.5.0-28-generic (x86_64)
Consult /var/lib/dkms/r8125/9.004.01/build/make.log for more information.
dkms autoinstall on 6.5.0-28-generic/x86_64 failed for r8125(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
* dkms: autoinstall for kernel 6.5.0-28-generic
...fail!
--
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/2062518
Title:
package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to
install/upgrade: installed linux-headers-6.5.0-28-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
Invalid
Bug description:
Softweare updater continually failing on this.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-28-generic 6.5.0-28.29
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: chris 1642 F pipewire
chris 1646 F wireplumber
/dev/snd/controlC0: chris 1646 F wireplumber
/dev/snd/seq:chris 1642 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Fri Apr 19 08:58:51 2024
ErrorMessage: installed linux-headers-6.5.0-28-generic package
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2024-04-17 (1 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64
(20240220)
IwConfig:
lono wireless extensions.
wlp109s0f0 no wireless extensions.
enx7e345242890a no wireless extensions.
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic
root=UUID=5db60d46-8e67-48c1-a78a-be0d6b68e193 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
SourcePackage: linux
Title: package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to
install/upgrade: installed linux-headers-6.5.0-28-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to mantic on 2024-04-18 (1 days ago)
dmi.bios.date: 03/14/2024
dmi.bios.release: 1.2
dmi.bios.vendor: Alienware
dmi.bios.version: 1.2.1
dmi.board.name: 0KVPC9
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Alienware
dmi.ec.firmware.release: 1.2
dmi.modalias:
dmi:bvnAlienware:bvr1.2.1:bd03/14/2024:br1.2:efr1.2:svnAlienware:pnAlienwarem18R2:pvr:rvnAlienware:rn0KVPC9:rvrA00:cvnAlienware:ct10:cvr:sku0C9D:
dmi.product.family: Alienware
dmi.product.name: Alienware m18 R2
dmi.product.sku: 0C9D
dmi.sys.vendor: Alienware
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062518/+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 2062518] Re: package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to install/upgrade: installed linux-headers-6.5.0-28-generic package post-installation script subprocess r
You have an unsupported DKMS module installed which breaks the kernel
header package installation. Please remove it:
$ dkms remove r8125/9.004.01
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2062518
Title:
package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to
install/upgrade: installed linux-headers-6.5.0-28-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
Invalid
Bug description:
Softweare updater continually failing on this.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-28-generic 6.5.0-28.29
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: chris 1642 F pipewire
chris 1646 F wireplumber
/dev/snd/controlC0: chris 1646 F wireplumber
/dev/snd/seq:chris 1642 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Fri Apr 19 08:58:51 2024
ErrorMessage: installed linux-headers-6.5.0-28-generic package
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2024-04-17 (1 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64
(20240220)
IwConfig:
lono wireless extensions.
wlp109s0f0 no wireless extensions.
enx7e345242890a no wireless extensions.
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic
root=UUID=5db60d46-8e67-48c1-a78a-be0d6b68e193 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
SourcePackage: linux
Title: package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to
install/upgrade: installed linux-headers-6.5.0-28-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to mantic on 2024-04-18 (1 days ago)
dmi.bios.date: 03/14/2024
dmi.bios.release: 1.2
dmi.bios.vendor: Alienware
dmi.bios.version: 1.2.1
dmi.board.name: 0KVPC9
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Alienware
dmi.ec.firmware.release: 1.2
dmi.modalias:
dmi:bvnAlienware:bvr1.2.1:bd03/14/2024:br1.2:efr1.2:svnAlienware:pnAlienwarem18R2:pvr:rvnAlienware:rn0KVPC9:rvrA00:cvnAlienware:ct10:cvr:sku0C9D:
dmi.product.family: Alienware
dmi.product.name: Alienware m18 R2
dmi.product.sku: 0C9D
dmi.sys.vendor: Alienware
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062518/+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 2062454] Re: package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to install/upgrade: le sous-processus paquet linux-headers-6.5.0-28-generic script post-installation insta
This is a problem with your (unsupported) DKMS, not the kernel. You need
to find an updated DKMS that supports the 6.5 kernel.
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2062454
Title:
package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to
install/upgrade: le sous-processus paquet linux-
headers-6.5.0-28-generic script post-installation installé a renvoyé
un état de sortie d'erreur 1
Status in linux package in Ubuntu:
Invalid
Bug description:
Error occured when dealing with tuxdo compiling. See message from
terminal below
Cleaning build area...
make -j12 KERNELRELEASE=6.5.0-28-generic
KDIR=/lib/modules/6.5.0-28-generic/build...(bad exit status: 2)
ERROR (dkms apport): binary package for tuxedo-keyboard: 3.2.6 not found
Error! Bad return status for module build on kernel: 6.5.0-28-generic (x86_64)
Consult /var/lib/dkms/tuxedo-keyboard/3.2.6/build/make.log for more
information.
Faithfully
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-28-generic 6.5.0-28.29
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: qashqai 73767 F wireplumber
/dev/snd/controlC1: qashqai 73767 F wireplumber
/dev/snd/seq:qashqai 73761 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Fri Apr 19 07:11:20 2024
ErrorMessage: le sous-processus paquet linux-headers-6.5.0-28-generic script
post-installation installé a renvoyé un état de sortie d'erreur 1
InstallationDate: Installed on 2024-04-09 (10 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230817)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f2:b729 Chicony Electronics Co., Ltd Chicony USB2.0
Camera
Bus 001 Device 015: ID 1ea7:0064 SHARKOON Technologies GmbH 2.4GHz Wireless
rechargeable vertical mouse [More&Better]
Bus 001 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic
root=UUID=dc4efb82-ddbc-4eb5-acde-1e3227bfeee3 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to
install/upgrade: le sous-processus paquet linux-headers-6.5.0-28-generic script
post-installation installé a renvoyé un état de sortie d'erreur 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/28/2021
dmi.bios.release: 1.0
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: FB1
dmi.board.asset.tag: Tag 12345
dmi.board.name: G5 KD
dmi.board.vendor: GIGABYTE
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: GIGABYTE
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.8
dmi.modalias:
dmi:bvnINSYDECorp.:bvrFB1:bd10/28/2021:br1.0:efr7.8:svnGIGABYTE:pnG5KD:pvrNotApplicable:rvnGIGABYTE:rnG5KD:rvrNotApplicable:cvnGIGABYTE:ct10:cvrN/A:skuRC45KD:
dmi.product.family: GIGABYTE
dmi.product.name: G5 KD
dmi.product.sku: RC45KD
dmi.product.version: Not Applicable
dmi.sys.vendor: GIGABYTE
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062454/+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 2062452] Re: package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to install/upgrade: installed linux-headers-6.5.0-28-generic package post-installation script subprocess r
Building module:
Cleaning build area...
make -j4 KERNELRELEASE=6.5.0-27-generic -C /lib/modules/6.5.0-27-generic/build
M=/var/lib/dkms/8192cu/1.11/build...(bad exit status: 2)
ERROR (dkms apport): binary package for 8192cu: 1.11 not found
Error! Bad return status for module build on kernel: 6.5.0-27-generic (x86_64)
Consult /var/lib/dkms/8192cu/1.11/build/make.log for more information.
dkms autoinstall on 6.5.0-27-generic/x86_64 failed for 8192cu(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
* dkms: autoinstall for kernel 6.5.0-27-generic
...fail!
--
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/2062452
Title:
package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to
install/upgrade: installed linux-headers-6.5.0-28-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
Invalid
Bug description:
linux-headers-6.5.0-27-generic
linux-headers-6.5.0-28-generic
linux-headers-generic-hwe-22.04
linux-generic-hwe-22.04
linux-headers-generic
linux-image-6.5.0-27-generic
linux-image-6.5.0-28-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-28-generic 6.5.0-28.29
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: talha-g1584 F wireplumber
/dev/snd/seq:talha-g1580 F pipewire
CasperMD5CheckResult: pass
Date: Fri Apr 19 07:46:04 2024
ErrorMessage: installed linux-headers-6.5.0-28-generic package
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2024-03-19 (31 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=a09c8968-b5f7-4fe1-a194-4150a0ca843e ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to
install/upgrade: installed linux-headers-6.5.0-28-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/29/2021
dmi.bios.release: 1.25
dmi.bios.vendor: LENOVO
dmi.bios.version: DJCN25WW
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ThinkBook 15-IIL
dmi.ec.firmware.release: 1.20
dmi.modalias:
dmi:bvnLENOVO:bvrDJCN25WW:bd03/29/2021:br1.25:efr1.20:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL:skuLENOVO_MT_20SM_BU_idea_FM_Thinkbook15-IIL:
dmi.product.family: Thinkbook 15-IIL
dmi.product.name: 20SM
dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL
dmi.product.version: Lenovo ThinkBook 15-IIL
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062452/+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 2062452] Re: package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to install/upgrade: installed linux-headers-6.5.0-28-generic package post-installation script subprocess r
You have an unsupported DKMS module installed which breaks the kernel
header package installation. Please remove it:
$ dkms remove 8192cu/1.11
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2062452
Title:
package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to
install/upgrade: installed linux-headers-6.5.0-28-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
Invalid
Bug description:
linux-headers-6.5.0-27-generic
linux-headers-6.5.0-28-generic
linux-headers-generic-hwe-22.04
linux-generic-hwe-22.04
linux-headers-generic
linux-image-6.5.0-27-generic
linux-image-6.5.0-28-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-28-generic 6.5.0-28.29
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: talha-g1584 F wireplumber
/dev/snd/seq:talha-g1580 F pipewire
CasperMD5CheckResult: pass
Date: Fri Apr 19 07:46:04 2024
ErrorMessage: installed linux-headers-6.5.0-28-generic package
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2024-03-19 (31 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=a09c8968-b5f7-4fe1-a194-4150a0ca843e ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to
install/upgrade: installed linux-headers-6.5.0-28-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/29/2021
dmi.bios.release: 1.25
dmi.bios.vendor: LENOVO
dmi.bios.version: DJCN25WW
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ThinkBook 15-IIL
dmi.ec.firmware.release: 1.20
dmi.modalias:
dmi:bvnLENOVO:bvrDJCN25WW:bd03/29/2021:br1.25:efr1.20:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL:skuLENOVO_MT_20SM_BU_idea_FM_Thinkbook15-IIL:
dmi.product.family: Thinkbook 15-IIL
dmi.product.name: 20SM
dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL
dmi.product.version: Lenovo ThinkBook 15-IIL
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062452/+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 2063002] Re: Add support for DCN 3.5
** Tags added: kern-10589 -- 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/2063002 Title: Add support for DCN 3.5 Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Noble: New Bug description: Products with DCN 3.5 need linux-firmware to be added for noble. Matching kernel support is already in kernel 6.8. 6bfdacdd amdgpu: add DMCUB 3.5 firmware cb59bf73 amdgpu: add VPE 6.1.0 firmware 3ca35ef5 amdgpu: add VCN 4.0.5 firmware 9a3a6c61 amdgpu: add UMSCH 4.0.0 firmware 62cc1372 amdgpu: add SDMA 6.1.0 firmware b455dd24 amdgpu: add PSP 14.0.0 firmware 30c1adcb amdgpu: add GC 11.5.0 firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2063002/+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 2062966] Re: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common
*** This bug is a duplicate of bug 2048183 *** https://bugs.launchpad.net/bugs/2048183 Remove package linux-intel-iotg-tools-common, it should not exist. ** This bug has been marked a duplicate of bug 2048183 Don't produce linux-*-cloud-tools-common, linux-*-tools-common and linux-*-tools-host binary packages -- 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/2062966 Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1055.61 Status in linux package in Ubuntu: New Bug description: Hello, I wanted to measure the frequency of the processors on my machine, but I couldn't install the package. Thank you. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-tools-common (not installed) ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: linux-tools-common:amd64: Install linux-tools-5.15.0-105:amd64: Install linux-tools-5.15.0-105-generic:amd64: Install linux-tools-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: misha 2313 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Sat Apr 20 13:21:12 2024 DpkgTerminalLog: Preparing to unpack .../linux-tools-common_5.15.0-105.115_all.deb ... Unpacking linux-tools-common (5.15.0-105.115) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-tools-common_5.15.0-105.115_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1055.61 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1055.61 InstallationDate: Installed on 2024-03-29 (21 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) MachineType: HP HP Laptop 17-cn3xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic root=UUID=71c5bf0d-2969-489a-89a0-f76890efa677 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 SourcePackage: linux Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1055.61 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2023 dmi.bios.release: 15.3 dmi.bios.vendor: Insyde dmi.bios.version: F.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8BBA dmi.board.vendor: HP dmi.board.version: 65.13 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 65.13 dmi.modalias: dmi:bvnInsyde:bvrF.03:bd07/18/2023:br15.3:efr65.13:svnHP:pnHPLaptop17-cn3xxx:pvrType1ProductConfigId:rvnHP:rn8BBA:rvr65.13:cvnHP:ct10:cvrChassisVersion:sku8D018EA#BED: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 17-cn3xxx dmi.product.sku: 8D018EA#BED dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
On Mon, Apr 22, 2024 at 11:07:54AM -, Matthieu Baerts wrote: > > I don't think we can justify dropping FAN support in an SRU, so let's > add that port back in. > > Even if it will not be used in Ubuntu 24.04, I'm happy to drop it if the stable release team would accept it. Here's the policy: https://wiki.ubuntu.com/StableReleaseUpdates However, I don't see how we can argue that dropping FAN support is *not* a regression, even if the kernel we ship does not support it. > and dropping these patches would stop the diversion with Debian? That's not a goal of our SRU process. We can always realign with Debian during the next devel cycle. > > @matttbe - is there any documentation about upstream compatibility > > guarantees and regression testing done that you're aware of, or any tests > > that we could run beyond those in our autopkgtests? > > @dannf: IPRoute2 is following the kernel development, and it is not > supposed to break the compatibility with older kernel versions (also > because the kernel's user API is not supposed to break). > > There is a test suite included in the source code, but it looks like it > is not tested when building the .deb package, check the 'debian/rules' > file: > > override_dh_auto_test: > # upstream test suite needs root and leaves machine unclean, skip > it The package does seem to include this in its autopkgtests (debian/tests/testsuite.sh), so I think we have that coverage. > > I never used it, (and it looks like it is not often updated), but IPRoute2 > (ip, tc, ss, etc.) is also heavily used in the kernel selftests: > > $ git grep -cw -e ip -e tc -e ss -- tools/testing/selftests/ | wc -l > 635 > > Maybe these tests are already being validated when building a new kernel for > Ubuntu? That's another way to validate IPRoute2. Thanks for the pointer! -dann > Other than that, Debian is using IPRoute2 versions > 6.1 for a long time > now. > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/2051672 Title: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) Status in iproute2 package in Ubuntu: Incomplete Bug description: iproute2 upstream produces releases coinciding with upstream kernel releases to support the latest kernel features. Noble's iproute2 is still back at v6.1 even though it will use the v6.8 kernel. This means we provide no userspace interface for newer features - some of which are noted by a networking hardware partner in bug 2060969. Ubuntu's iproute2 has diverged from Debian's to add support for Ubuntu FAN. Noble has dropped kernel support for Ubuntu FAN, so those are no longer needed, and we could now just do a merge. We could also port the FAN patches forward if we can identify a need (see the original description of this bug to a link to such a port), but I have not done any testing with that. I have built Debian's iproute2 in a noble ppa at ppa:dannf/test and smoke tested it on an amd64 virtual machine: ubuntu@cortez-vm-0:~$ sudo dpkg -i iproute2_6.8.0-1~24.04.1_amd64.deb (Reading database ... 83134 files and directories currently installed.) Preparing to unpack iproute2_6.8.0-1~24.04.1_amd64.deb ... Unpacking iproute2 (6.8.0-1~24.04.1) over (6.1.0-1ubuntu6) ... dpkg: warning: unable to delete old directory '/etc/iproute2/rt_tables.d': Directory not empty dpkg: warning: unable to delete old directory '/etc/iproute2/rt_protos.d': Directory not empty dpkg: warning: unable to delete old directory '/etc/iproute2': Directory not empty Setting up iproute2 (6.8.0-1~24.04.1) ... Removing obsolete conffile /etc/iproute2/group ... Removing obsolete conffile /etc/iproute2/rt_realms ... Removing obsolete conffile /etc/iproute2/rt_scopes ... Removing obsolete conffile /etc/iproute2/rt_tables ... Removing obsolete conffile /etc/iproute2/rt_tables.d/README ... Removing obsolete conffile /etc/iproute2/rt_protos.d/README ... Removing obsolete conffile /etc/iproute2/rt_protos ... Removing obsolete conffile /etc/iproute2/rt_dsfield ... Removing obsolete conffile /etc/iproute2/nl_protos ... Removing obsolete conffile /etc/iproute2/ematch_map ... Removing obsolete conffile /etc/iproute2/bpf_pinning ... Processing triggers for man-db (2.12.0-4build1) ... The system rebooted fine. The ip command seems to behave normally. Since the upstream test suite only appears to run at autopkgtest time, I triggered a run in my PPA, and it passed: https://autopkgtest.ubuntu.com/results/autopkgtest-noble-dannf-test/noble/amd64/i/iproute2/20240412_210819_97417@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packa
[Kernel-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Kernel -31 fixed the problem for me. Thanks!
--
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/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in zfs-linux package in Ubuntu:
Fix Released
Status in systemd source package in Noble:
Fix Released
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+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 2062280] Re: Bluetooth Broken In Kernel Versions 6.5+ (Realtek)
Steps to reproduce the bug: * install bluez * make sure a USB Bluetooth dongle is attached to your computer * Start bluetoothctl * Run discoverable on * Discover the device using the Android BT manager * On the phone you are ask to confirm the pair key -> Pair * In the bluetoothctl type yes * Connection is establish and it fails immediately with a disconnect error message -> type BR/EDR disconnected with reason 2 -- 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/2062280 Title: Bluetooth Broken In Kernel Versions 6.5+ (Realtek) Status in linux package in Ubuntu: Incomplete Bug description: Starting with kernel 6.5 the external Bluetooth USB dongle based on Realtek stop working. This issue occurs on either UBuntu 22.04, 23.10 and 24.04 when kernel version is > 6.5. On a lower kernel version it works as we were using it for almost 2 years without issues. Version signature: Ubuntu 6.8.0-22.22-generic 6.8.1 USB bluetooth device: Bus 001 Device 003: ID 0bda:a729 Realtek Semiconductor Corp. Bluetooth Radio ``` $ uname -a Linux bomi-edge 6.8.0-22-generic #22-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 4 22:30:32 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux ``` ``` $ lsusb | grep -i bluetooth Bus 001 Device 003: ID 0bda:a729 Realtek Semiconductor Corp. Bluetooth Radio ``` Journalctl logs after the OS is starting ``` journalctl -b | egrep -i bluetooth Apr 18 07:16:29 bomi-edge kernel: usb 1-9: Product: Bluetooth Radio Apr 18 07:16:30 bomi-edge kernel: Bluetooth: Core ver 2.22 Apr 18 07:16:30 bomi-edge kernel: NET: Registered PF_BLUETOOTH protocol family Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI device and connection manager initialized Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI socket layer initialized Apr 18 07:16:30 bomi-edge kernel: Bluetooth: L2CAP socket layer initialized Apr 18 07:16:30 bomi-edge kernel: Bluetooth: SCO socket layer initialized Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1 Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210 Apr 18 07:16:30 bomi-edge systemd[1]: Reached target bluetooth.target - Bluetooth Support. Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922 root@bomi-edge:/home/edge# journalctl -b | egrep -i bluetooth Apr 18 07:16:29 bomi-edge kernel: usb 1-9: Product: Bluetooth Radio Apr 18 07:16:30 bomi-edge kernel: Bluetooth: Core ver 2.22 Apr 18 07:16:30 bomi-edge kernel: NET: Registered PF_BLUETOOTH protocol family Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI device and connection manager initialized Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI socket layer initialized Apr 18 07:16:30 bomi-edge kernel: Bluetooth: L2CAP socket layer initialized Apr 18 07:16:30 bomi-edge kernel: Bluetooth: SCO socket layer initialized Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1 Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210 Apr 18 07:16:30 bomi-edge systemd[1]: Reached target bluetooth.target - Bluetooth Support. Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922 ``` I have installed BlueZ package https://www.bluez.org/ and trying to discover the device which worked but i am always getting errors when trying to connect to the device via BT (after pairing) ``` Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/adapter.c:property_set_mode() sending Set Discoverable command for index 0 Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() [0x] command 0x0007 Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x] command 0x0007 complete: 0x00 Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() [0x] command 0x0006 Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x] command 0x0006 complete: 0x00 Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/adapter.c:property_set_mode_complete() Success (0x00) Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/adapter.c:new_settings_callback() Settings: 0x0adb Apr 18 09:22:37 bomi-edge bluetoothd[2413]: s
[Kernel-packages] [Bug 2062280] Re: Bluetooth Broken In Kernel Versions 6.5+ (Realtek)
i have used also ubuntu-bug to send logs -- 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/2062280 Title: Bluetooth Broken In Kernel Versions 6.5+ (Realtek) Status in linux package in Ubuntu: Incomplete Bug description: Starting with kernel 6.5 the external Bluetooth USB dongle based on Realtek stop working. This issue occurs on either UBuntu 22.04, 23.10 and 24.04 when kernel version is > 6.5. On a lower kernel version it works as we were using it for almost 2 years without issues. Version signature: Ubuntu 6.8.0-22.22-generic 6.8.1 USB bluetooth device: Bus 001 Device 003: ID 0bda:a729 Realtek Semiconductor Corp. Bluetooth Radio ``` $ uname -a Linux bomi-edge 6.8.0-22-generic #22-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 4 22:30:32 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux ``` ``` $ lsusb | grep -i bluetooth Bus 001 Device 003: ID 0bda:a729 Realtek Semiconductor Corp. Bluetooth Radio ``` Journalctl logs after the OS is starting ``` journalctl -b | egrep -i bluetooth Apr 18 07:16:29 bomi-edge kernel: usb 1-9: Product: Bluetooth Radio Apr 18 07:16:30 bomi-edge kernel: Bluetooth: Core ver 2.22 Apr 18 07:16:30 bomi-edge kernel: NET: Registered PF_BLUETOOTH protocol family Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI device and connection manager initialized Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI socket layer initialized Apr 18 07:16:30 bomi-edge kernel: Bluetooth: L2CAP socket layer initialized Apr 18 07:16:30 bomi-edge kernel: Bluetooth: SCO socket layer initialized Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1 Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210 Apr 18 07:16:30 bomi-edge systemd[1]: Reached target bluetooth.target - Bluetooth Support. Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922 root@bomi-edge:/home/edge# journalctl -b | egrep -i bluetooth Apr 18 07:16:29 bomi-edge kernel: usb 1-9: Product: Bluetooth Radio Apr 18 07:16:30 bomi-edge kernel: Bluetooth: Core ver 2.22 Apr 18 07:16:30 bomi-edge kernel: NET: Registered PF_BLUETOOTH protocol family Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI device and connection manager initialized Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI socket layer initialized Apr 18 07:16:30 bomi-edge kernel: Bluetooth: L2CAP socket layer initialized Apr 18 07:16:30 bomi-edge kernel: Bluetooth: SCO socket layer initialized Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1 Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210 Apr 18 07:16:30 bomi-edge systemd[1]: Reached target bluetooth.target - Bluetooth Support. Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922 ``` I have installed BlueZ package https://www.bluez.org/ and trying to discover the device which worked but i am always getting errors when trying to connect to the device via BT (after pairing) ``` Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/adapter.c:property_set_mode() sending Set Discoverable command for index 0 Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() [0x] command 0x0007 Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x] command 0x0007 complete: 0x00 Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() [0x] command 0x0006 Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x] command 0x0006 complete: 0x00 Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/adapter.c:property_set_mode_complete() Success (0x00) Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/adapter.c:new_settings_callback() Settings: 0x0adb Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() Changed settings: 0x0008 Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() Pending settings: 0x0002 Apr 18 09:23:07 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() [0x] event 0x000b Apr 18 09:23:07 bomi-edge bluetoothd[2413]: src/adapter.c:connected_callback() hci0 device 74:9E:F5:28
[Kernel-packages] [Bug 2060209] Re: Jammy update: v5.15.151 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060209 Title: Jammy update: v5.15.151 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.151 upstream stable release from git://git.kernel.org/ netfilter: nf_tables: disallow timeout for anonymous sets mtd: spinand: gigadevice: Fix the get ecc status issue netlink: Fix kernel-infoleak-after-free in __skb_datagram_iter net: ip_tunnel: prevent perpetual headroom growth tun: Fix xdp_rxq_info's queue_index when detaching cpufreq: intel_pstate: fix pstate limits enforcement for adjust_perf call back net: veth: clear GRO when clearing XDP even when down ipv6: fix potential "struct net" leak in inet6_rtm_getaddr() lan78xx: enable auto speed configuration for LAN7850 if no EEPROM is detected net: enable memcg accounting for veth queues veth: try harder when allocating queue memory net: usb: dm9601: fix wrong return value in dm9601_mdio_read uapi: in6: replace temporary label with rfc9486 stmmac: Clear variable when destroying workqueue Bluetooth: Avoid potential use-after-free in hci_error_reset Bluetooth: hci_event: Fix wrongly recorded wakeup BD_ADDR Bluetooth: hci_event: Fix handling of HCI_EV_IO_CAPA_REQUEST netfilter: nf_tables: allow NFPROTO_INET in nft_(match/target)_validate() netfilter: nfnetlink_queue: silence bogus compiler warning netfilter: core: move ip_ct_attach indirection to struct nf_ct_hook netfilter: make function op structures const netfilter: let reset rules clean out conntrack entries netfilter: bridge: confirm multicast packets before passing them up the stack rtnetlink: fix error logic of IFLA_BRIDGE_FLAGS writing back igb: extend PTP timestamp adjustments to i211 tls: rx: don't store the record type in socket context tls: rx: don't store the decryption status in socket context tls: rx: don't issue wake ups when data is decrypted tls: rx: refactor decrypt_skb_update() tls: hw: rx: use return value of tls_device_decrypted() to carry status tls: rx: drop unnecessary arguments from tls_setup_from_iter() tls: rx: don't report text length from the bowels of decrypt tls: rx: wrap decryption arguments in a structure tls: rx: factor out writing ContentType to cmsg tls: rx: don't track the async count tls: rx: move counting TlsDecryptErrors for sync tls: rx: assume crypto always calls our callback tls: rx: use async as an in-out argument tls: decrement decrypt_pending if no async completion will be called efi/capsule-loader: fix incorrect allocation size power: supply: bq27xxx-i2c: Do not free non existing IRQ ALSA: Drop leftover snd-rtctimer stuff from Makefile fbcon: always restore the old font data in fbcon_do_set_font() afs: Fix endless loop in directory parsing riscv: Sparse-Memory/vmemmap out-of-bounds fix tomoyo: fix UAF write bug in tomoyo_write_control() ALSA: firewire-lib: fix to check cycle continuity gtp: fix use-after-free and null-ptr-deref in gtp_newlink() wifi: nl80211: reject iftype change with mesh ID change btrfs: dev-replace: properly validate device names dmaengine: fsl-qdma: fix SoC may hang on 16 byte unaligned read dmaengine: ptdma: use consistent DMA masks dmaengine: fsl-qdma: init irq after reg initialization mmc: core: Fix eMMC initialization with 1-bit bus connection mmc: sdhci-xenon: add timeout for PHY init complete mmc: sdhci-xenon: fix PHY init clock stability pmdomain: qcom: rpmhpd: Fix enabled_corner aggregation x86/cpu/intel: Detect TME keyid bits before setting MTRR mask registers mptcp: move __mptcp_error_report in protocol.c mptcp: process pending subflow error on close mptcp: rename timer related helper to less confusing names selftests: mptcp: add missing kconfig for NF Filter selftests: mptcp: add missing kconfig for NF Filter in v6 mptcp: clean up harmless false expressions mptcp: add needs_id for netlink appending addr mptcp: push at DSS boundaries mptcp: fix possible deadlock in subflow diag cachefiles: fix memory leak in cachefiles_add_cache() fs,hugetlb: fix NULL pointer dereference in hugetlbs_fill_super Revert "drm/bridge: lt8912b: Register and attach our DSI device at probe" af_unix: Drop oob_skb
[Kernel-packages] [Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
> However, I don't see how we can argue that dropping FAN support is > *not* a regression, even if the kernel we ship does not support it. I understand. I guess the situation is a bit particular here. If the official kernel doesn't support it -- something Ubuntu-specific, not upstreamed -- it means Ubuntu FAN cannot be used: there is no way to even validate that these patches work on Ubuntu 24.04. The regression would be more on the kernel side :) >> and dropping these patches would stop the diversion with Debian? > > That's not a goal of our SRU process. We can always realign with > Debian during the next devel cycle. Good point. I just wanted to suggest that dropping these patches could be seen as a "safer approach" as it is closer to the upstream version, what is on Debian and other distributions. > The package does seem to include this in its autopkgtests > (debian/tests/testsuite.sh), so I think we have that coverage. Oh, I missed that, thank you for having checked! Good news then! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/2051672 Title: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) Status in iproute2 package in Ubuntu: Incomplete Bug description: iproute2 upstream produces releases coinciding with upstream kernel releases to support the latest kernel features. Noble's iproute2 is still back at v6.1 even though it will use the v6.8 kernel. This means we provide no userspace interface for newer features - some of which are noted by a networking hardware partner in bug 2060969. Ubuntu's iproute2 has diverged from Debian's to add support for Ubuntu FAN. Noble has dropped kernel support for Ubuntu FAN, so those are no longer needed, and we could now just do a merge. We could also port the FAN patches forward if we can identify a need (see the original description of this bug to a link to such a port), but I have not done any testing with that. I have built Debian's iproute2 in a noble ppa at ppa:dannf/test and smoke tested it on an amd64 virtual machine: ubuntu@cortez-vm-0:~$ sudo dpkg -i iproute2_6.8.0-1~24.04.1_amd64.deb (Reading database ... 83134 files and directories currently installed.) Preparing to unpack iproute2_6.8.0-1~24.04.1_amd64.deb ... Unpacking iproute2 (6.8.0-1~24.04.1) over (6.1.0-1ubuntu6) ... dpkg: warning: unable to delete old directory '/etc/iproute2/rt_tables.d': Directory not empty dpkg: warning: unable to delete old directory '/etc/iproute2/rt_protos.d': Directory not empty dpkg: warning: unable to delete old directory '/etc/iproute2': Directory not empty Setting up iproute2 (6.8.0-1~24.04.1) ... Removing obsolete conffile /etc/iproute2/group ... Removing obsolete conffile /etc/iproute2/rt_realms ... Removing obsolete conffile /etc/iproute2/rt_scopes ... Removing obsolete conffile /etc/iproute2/rt_tables ... Removing obsolete conffile /etc/iproute2/rt_tables.d/README ... Removing obsolete conffile /etc/iproute2/rt_protos.d/README ... Removing obsolete conffile /etc/iproute2/rt_protos ... Removing obsolete conffile /etc/iproute2/rt_dsfield ... Removing obsolete conffile /etc/iproute2/nl_protos ... Removing obsolete conffile /etc/iproute2/ematch_map ... Removing obsolete conffile /etc/iproute2/bpf_pinning ... Processing triggers for man-db (2.12.0-4build1) ... The system rebooted fine. The ip command seems to behave normally. Since the upstream test suite only appears to run at autopkgtest time, I triggered a run in my PPA, and it passed: https://autopkgtest.ubuntu.com/results/autopkgtest-noble-dannf-test/noble/amd64/i/iproute2/20240412_210819_97417@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+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 2061851] Re: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression with new apparmor profiles/features
** Changed in: snapd (Ubuntu Noble) Status: New => Invalid ** Changed in: linux-aws (Ubuntu Noble) Status: New => Fix Released ** Changed in: linux-azure (Ubuntu Noble) Status: New => Fix Released ** Changed in: linux-gcp (Ubuntu Noble) Status: New => Fix Released ** Changed in: linux-ibm (Ubuntu Noble) Status: New => Fix Released ** Changed in: linux-oracle (Ubuntu Noble) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2061851 Title: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression with new apparmor profiles/features Status in chrony package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-ibm package in Ubuntu: Fix Released Status in linux-oracle package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Invalid Status in chrony source package in Noble: Invalid Status in linux source package in Noble: Fix Released Status in linux-aws source package in Noble: Fix Released Status in linux-azure source package in Noble: Fix Released Status in linux-gcp source package in Noble: Fix Released Status in linux-ibm source package in Noble: Fix Released Status in linux-oracle source package in Noble: Fix Released Status in snapd source package in Noble: Invalid Bug description: * Canonical Public Cloud discovered that `chronyc -c sources` now fails with `506 Cannot talk to daemon` with the latest kernels. We are seeing this in linux-azure and linux-gcp kernels (6.8.0-1005.5) * Disabling AppArmor (`sudo systemctl stop apparmor`) completely results in no regression and `chronyc -c sources` returns as expected * Disabling the apparmor profile for `chronyd` only results in no regression and `chronyc -c sources` returns as expected * There are zero entries in dmesg when this occurs * There are zero entries in dmesg when this occurs if the apparmor profile for `chronyd` is placed in complain mode instead of enforce mode * We changed the time server from the internal GCP metadata.google.internal to the ubuntu time server ntp.ubuntu.com with no change in behaviour We also noted issues with DNS resolution in snaps like `google-cloud-cli` in GCE images. * Disabling apparmor completely for snaps too (`sudo systemctl stop snapd.apparmor`) results in no regression and calling the snaps returns as expected. The same issues are present in azure kernel `linux-azure` `6.8.0-1005.5` and the -proposed `6.8.0-25.25` generic kernel. This is a release blocker for Noble release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2061851/+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 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
with 6.8-31 I was able to install 24.04 ubuntu-server-minimal with zfs
boot & root using the OpenZFS tutorial for 22.04 with minimal change.
Since there's no ZFS root install script in subiquity yet the OpenZFS
instructions are going to be the go-to for many people again.
https://github.com/openzfs/zfs/discussions/16120
--
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/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in zfs-linux package in Ubuntu:
Fix Released
Status in systemd source package in Noble:
Fix Released
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+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 2047154] Re: [amdgpu][drm] *ERROR* flip_done timed out
There are many issue in the AMD gitlab referencing flip_done timed out freezes. Seems to affect a lot of people. I'm still locking up daily. Here is an example, FWIW https://gitlab.freedesktop.org/drm/amd/-/issues/1707 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1707 https://gitlab.freedesktop.org/drm/amd/-/issues/1707 -- 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/2047154 Title: [amdgpu][drm] *ERROR* flip_done timed out Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: New Bug description: amdgpu :0c:00.0: [drm] *ERROR* flip_done timed out gru 21 16:32:25 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* [CRTC:84:crtc-0] commit wait timed out gru 21 16:32:36 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* flip_done timed out gru 21 16:32:36 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* [CONNECTOR:119:HDMI-A-1] commit wait timed out gru 21 16:32:40 karol.home.prv dbus-daemon[1317]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=2> gru 21 16:32:46 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* flip_done timed out gru 21 16:32:46 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* [PLANE:67:plane-5] commit wait timed out gru 21 16:32:46 karol.home.prv kernel: [ cut here ] gru 21 16:32:46 karol.home.prv kernel: WARNING: CPU: 3 PID: 100858 at /var/lib/dkms/amdgpu/6.2.4-1664922.22.04/build/amd/amdgpu/../di> gru 21 16:32:46 karol.home.prv kernel: Modules linked in: xt_recent tls xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_i> gru 21 16:32:46 karol.home.prv kernel: reed_solomon pstore_zone efi_pstore sunrpc ip_tables x_tables autofs4 ib_uverbs ib_core amdgp> gru 21 16:32:46 karol.home.prv kernel: CPU: 3 PID: 100858 Comm: Xorg Tainted: PW OE 6.2.0-26-generic #26~22.04.1-Ubuntu gru 21 16:32:46 karol.home.prv kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X470 Master SLI, BIOS P4.40 03/29> gru 21 16:32:46 karol.home.prv kernel: RIP: 0010:amdgpu_dm_atomic_commit_tail+0x3b20/0x4200 [amdgpu] gru 21 16:32:46 karol.home.prv kernel: Code: ff 4c 89 9d 78 fc ff ff ba 01 00 00 00 31 f6 4c 89 95 80 fc ff ff 41 b9 01 00 00 00 50 5> gru 21 16:32:46 karol.home.prv kernel: RSP: 0018:b5fb50ee7818 EFLAGS: 00010002 gru 21 16:32:46 karol.home.prv kernel: RAX: 0246 RBX: 00013195 RCX: gru 21 16:32:46 karol.home.prv kernel: RDX: RSI: RDI: gru 21 16:32:46 karol.home.prv kernel: RBP: b5fb50ee7ba0 R08: R09: gru 21 16:32:46 karol.home.prv kernel: R10: 0002 R11: R12: 0246 gru 21 16:32:46 karol.home.prv kernel: R13: R14: 9710a5d8d118 R15: 9710a5d8d000 gru 21 16:32:46 karol.home.prv kernel: FS: 7f3267b4ea80() GS:97179eac() knlGS: gru 21 16:32:46 karol.home.prv kernel: CS: 0010 DS: ES: CR0: 80050033 gru 21 16:32:46 karol.home.prv kernel: CR2: 55ef7d6bfb20 CR3: 000250f4e000 CR4: 003506e0 gru 21 16:32:46 karol.home.prv kernel: Call Trace: gru 21 16:32:46 karol.home.prv kernel: gru 21 16:32:46 karol.home.prv kernel: commit_tail+0xc5/0x1a0 [drm_kms_helper] gru 21 16:32:46 karol.home.prv kernel: ? drm_atomic_helper_swap_state+0x246/0x380 [drm_kms_helper] gru 21 16:32:46 karol.home.prv kernel: drm_atomic_helper_commit+0x137/0x160 [drm_kms_helper] gru 21 16:32:46 karol.home.prv kernel: drm_atomic_commit+0x99/0xd0 [drm] gru 21 16:32:46 karol.home.prv kernel: ? __pfx___drm_printfn_info+0x10/0x10 [drm] gru 21 16:32:46 karol.home.prv kernel: drm_mode_obj_set_property_ioctl+0x179/0x430 [drm] gru 21 16:32:46 karol.home.prv kernel: ? drm_mode_createblob_ioctl+0xff/0x130 [drm] gru 21 16:32:46 karol.home.prv kernel: ? __pfx_drm_mode_obj_set_property_ioctl+0x10/0x10 [drm] gru 21 16:32:46 karol.home.prv kernel: drm_ioctl_kernel+0xc3/0x160 [drm] gru 21 16:32:46 karol.home.prv kernel: drm_ioctl+0x27b/0x4c0 [drm] gru 21 16:32:46 karol.home.prv kernel: ? __pfx_drm_mode_obj_set_property_ioctl+0x10/0x10 [drm] gru 21 16:32:46 karol.home.prv kernel: ? __pm_runtime_suspend+0x7b/0x110 gru 21 16:32:46 karol.home.prv kernel: amdgpu_drm_ioctl+0x4e/0x90 [amdgpu] gru 21 16:32:46 karol.home.prv kernel: __x64_sys_ioctl+0x9d/0xe0 gru 21 16:32:46 karol.home.prv kernel: do_syscall_64+0x5c/0x90 gru 21 16:32:46 karol.home.prv kernel: ? do_syscall_64+0x69/0x90 gru 21 16:32:46 karol.home.prv kernel: ? exit_to_user_mode_prepare+0x3b/0xd0 gru 21 16:32:46 karol.home.prv kernel: ? syscall_exit_to_user_mode+0x2a/0x50 ? do_syscall_64+0x69/0x
[Kernel-packages] [Bug 2062950] Re: RE: Flickering problems on external monitor with HDMI after installing Ubuntu 23.10
I had the same problem when using another HDMI cable
I couldn't change the external monitor to a lower resolution because it
kept flickering and going to the menu for the external monitor, it would
just reset and send me to the settings for the built-in monitor
I attached a video
** Attachment added: "PXL_20240422_160854627.TS.mp4"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062950/+attachment/5769463/+files/PXL_20240422_160854627.TS.mp4
--
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/2062950
Title:
RE: Flickering problems on external monitor with HDMI after installing
Ubuntu 23.10
Status in linux package in Ubuntu:
Incomplete
Bug description:
this is a continuation of the bug reported in
https://bugs.launchpad.net/ubuntu/+bug/2062504
I reinstalled ubuntu 23, and didn't install anything else. I'm still
having the flickering when connecting an HDMI to an external monitor.
please help
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 19 22:27:21 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c)
(prog-if 00 [VGA controller])
Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a6]
InstallationDate: Installed on 2024-04-20 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic
root=UUID=92611de2-ed0a-4611-b724-820a5d29be02 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/23/2024
dmi.bios.release: 1.23
dmi.bios.vendor: LENOVO
dmi.bios.version: R1UET46W (1.23 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21B4S4QB00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76465 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.14
dmi.modalias:
dmi:bvnLENOVO:bvrR1UET46W(1.23):bd02/23/2024:br1.23:efr1.14:svnLENOVO:pn21B4S4QB00:pvrThinkPadL13Gen3:rvnLENOVO:rn21B4S4QB00:rvrSDK0T76465WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21B4_BU_Think_FM_ThinkPadL13Gen3:
dmi.product.family: ThinkPad L13 Gen 3
dmi.product.name: 21B4S4QB00
dmi.product.sku: LENOVO_MT_21B4_BU_Think_FM_ThinkPad L13 Gen 3
dmi.product.version: ThinkPad L13 Gen 3
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
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/+bug/2062950/+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 2060727] Re: The keyboard does not work after latest kernel update
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1021.22
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-done-
jammy-linux-oem-6.5'. If the problem still exists, change the tag
'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy-
linux-oem-6.5'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-oem-6.5-v2
verification-needed-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/2060727
Title:
The keyboard does not work after latest kernel update
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:
Fix Committed
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not
work after the latest kernel update and its subsequent reboot of the
laptop. Nothing else is connected to the laptop.
--
In /var/log/apt/history.log , the latest we can see is:
Start-Date: 2024-04-09 12:37:28
Commandline: apt full-upgrade
Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic),
linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic),
linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic),
linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic),
linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic)
Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27),
linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64
(6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28)
End-Date: 2024-04-09 12:37:51
--
$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.10
Release:23.10
$ # Note: It's Kubuntu 23.10
--
$ uname -a
Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
SRU Justification:
==
[Impact]
Keyboard is lost after updated to 6.5.0-27 and oem-6.5-1019 kernel
versions.
[Fix]
Regression commit is found commit:
936e4d49ecbc ("Input: atkbd - skip ATKBD_CMD_GETID in translated mode")
Fixes:
9cf6e24c9fbf1 Input: atkbd - do not skip atkbd_deactivate() when
skipping ATKBD_CMD_GETID
683cd8259a9b8 Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping
ATKBD_CMD_GETID
[Test]
Tested on hardware, keyboard works fine after bootup.
The regression commit is only in 6.5 stable, so SRU for 6.5 only.
[Where problems could occur]
It may break keyboard.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+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 2061049] Re: Fix random HuC/GuC initialization failure of Intel i915 driver
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oem-6.5-v2 verification-needed-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/2061049 Title: Fix random HuC/GuC initialization failure of Intel i915 driver Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux-oem-6.8 source package in Jammy: Invalid Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Status in linux-oem-6.8 source package in Noble: New Bug description: [Impact] i915 error can sometimes be found in kernel message when booting the machine w/ power unplugged kernel: i915 :00:02.0: [drm] *ERROR* GT1: GuC initialization failed -EIO kernel: i915 :00:02.0: [drm] *ERROR* GT1: Enabling uc failed (-5) kernel: i915 :00:02.0: [drm] *ERROR* GT1: Failed to initialize GPU, declaring it wedged! The GPU won't work with this failure [Fix] Backport the upatream fix for allowing slow HuC loading. [Test] 1. Unplug the power of the laptop and make sure it's charged by battery 2. Cold boot or Warm boot the machine and check the GuC init fail message. 3. Go to settings - > about --> graphics to make sure the GPU information is correct every boot. [Where problems could occur] Simply increase the loading time of HuC still get a working system. Should be low risk of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2061049/+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 2059263] Re: Fix acpi_power_meter accessing IPMI region before it's ready
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oem-6.5-v2 verification-needed-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/2059263 Title: Fix acpi_power_meter accessing IPMI region before it's ready Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Confirmed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Confirmed Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] ACPI error can be found in kernel message: [3.717920] ACPI Error: No handler for Region [SYSI] (ab9e62c5) [IPMI] (20230628/evregion-130) [Fix] On Dell systems that have IPI0001 device, ensure IPMI region is ready before acpi_power_meter invokes any ACPI method. [Test] With the patch applied, no such error can be found in kernel message. acpi_power_meter sysfs also works correctly. [Where problems could occur] If asynchronous probe is disabled, the device drivers that probe after acpi_power_meter needs to wait until the completion is done, hence the boot time might be slower. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2059263/+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 2063009] Re: package linux-headers-6.5.0-28-generic 6.5.0-28.29~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-28-generic package post-installation script subp
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2063009 Title: package linux-headers-6.5.0-28-generic 6.5.0-28.29~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-28-generic package post-installation script subprocess was killed by signal (Terminated) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: sudo apt-get upgrade -y E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 7444 (apt-get) N: Be aware that removing the lock file is not a solution and may break your system. E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-headers-6.5.0-28-generic 6.5.0-28.29~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Apr 21 09:30:38 2024 ErrorMessage: installed linux-headers-6.5.0-28-generic package post-installation script subprocess was killed by signal (Terminated) InstallationDate: Installed on 2024-04-16 (4 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.12 SourcePackage: linux-hwe-6.5 Title: package linux-headers-6.5.0-28-generic 6.5.0-28.29~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-28-generic package post-installation script subprocess was killed by signal (Terminated) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2063009/+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 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
This bug is awaiting verification that the linux- riscv-5.15/5.15.0-1056.60~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- riscv-5.15' to 'verification-done-focal-linux-riscv-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux- riscv-5.15' to 'verification-failed-focal-linux-riscv-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-riscv-5.15-v2 verification-needed-focal-linux-riscv-5.15 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: Hi, updated some Ubuntu 22.04 systems to lastest available state this morning, which caused CIFS mounts (from various fileservers) to stop working. Kernel was updated to version 5.15.0-102-generic. I can mount the shares without problems (mount -t cifs), but then, df for example tells me: df: /mnt: Resource temporarily unavailable. I'm able to list and browse all the files, but accessing them (even readonly) is very unstable. Sometimes it works and sometimes it just gives me i/o errors. Switching back to 5.15.0-101-generic or 5.15.0-100-generic solves the problem and everything works again as expected. Seems like some bug has been implemented in 5.15.0-102-generic... To reproduce the problem, I started a while loop on one server to write to some file on a specific mounted CIFS share and read it from another one root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; sleep 1 ; done -bash: /mnt/hallo.txt: Input/output error -bash: /mnt/hallo.txt: Input/output error ^C root@:~$ tail -f /mnt/hallo.txt Tue Apr 9 04:10:52 PM CEST 2024 hallo Tue Apr 9 04:10:53 PM CEST 2024 hallo Tue Apr 9 04:10:54 PM CEST 2024 hallo Tue Apr 9 04:10:55 PM CEST 2024 hallo Tue Apr 9 04:10:56 PM CEST 2024 hallo Tue Apr 9 04:10:57 PM CEST 2024 hallo Tue Apr 9 04:10:58 PM CEST 2024 hallo Tue Apr 9 04:10:59 PM CEST 2024 hallo Tue Apr 9 04:11:00 PM CEST 2024 hallo Tue Apr 9 04:11:01 PM CEST 2024 hallo tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: Resource temporarily unavailable Tue Apr 9 04:11:04 PM CEST 2024 hallo Tue Apr 9 04:11:05 PM CEST 2024 hallo Tue Apr 9 04:11:06 PM CEST 2024 hallo Tue Apr 9 04:11:07 PM CEST 2024 hallo Tue Apr 9 04:11:08 PM CEST 2024 hallo Tue Apr 9 04:11:09 PM CEST 2024 hallo Tue Apr 9 04:11:10 PM CEST 2024 hallo While doing this, both servers tell me, the resource is unavailable root@:~# df -h /mnt df: /mnt: Resource temporarily unavailable root@:~$ df -h /mnt df: /mnt: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2063143] [NEW] Frequent boot to black display
Public bug reported: Hardware: AMD Framework 13 OS: Ubuntu Noble 24.04 DE: Plasma Wayland BIOS: version 3.03 and 3.05 (latest new release) Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux This issue started about 2-3 weeks ago I believe around the time that Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages. This issue may not be a kernel regression but instead a wayland regression but I am not certain and looking for help. The issue is that on boot the (internal laptop and external displays if connected) are black but backlight is lit. I am able to boot into recovery mode without issue since the graphics drivers are not loaded in that case (only amd framebuffer driver and userspace mesa llvmpipe). Cold boot from OFF seems to be the most common case for this issue and it happens about 50-75% of the time from there. I have to force power the device off and try again in this case. I don't know how to get proper bootlogs from the previous boot when this is the case since /var/log only seems to contain logs from the current boot. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Mon Apr 22 13:35:21 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Framework Computer Inc. Phoenix1 [f111:0006] InstallationDate: Installed on 2023-11-16 (159 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP05 dmi.board.vendor: Framework dmi.board.version: A5 dmi.chassis.asset.tag: FRANDGCPA5342400SJ dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A5 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP05 dmi.product.version: A5 dmi.sys.vendor: Framework version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze kubuntu noble ubuntu wayland-session ** Also affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** No longer affects: xorg (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2063143 Title: Frequent boot to black display Status in linux-meta package in Ubuntu: New Bug description: Hardware: AMD Framework 13 OS: Ubuntu Noble 24.04 DE: Plasma Wayland BIOS: version 3.03 and 3.05 (latest new release) Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux This issue started about 2-3 weeks ago I believe around the time that Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages. This issue may not be a kernel regression but instead a wayland regression but I am not certain and looking for help. The issue is that on boot the (internal laptop and external displays if connected) are black but backlight is lit. I am able to boot into recovery mode without issue since the graphics drivers are not loaded in that case (only amd framebuffer driver and userspace mesa llvmpipe). Cold boot from OFF seems to be the most co
[Kernel-packages] [Bug 2062325] Re: Failed to read fan data for Asus Zenbook laptop
** Tags added: server-triage-discuss -- 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/2062325 Title: Failed to read fan data for Asus Zenbook laptop Status in linux package in Ubuntu: New Status in lm-sensors package in Ubuntu: New Bug description: Laptop: Asus Zenbook 14 UX435-EG [ 29.311703] asus_wmi: fan_curve_get_factory_default (0x00110024) failed: -19 [ 29.312163] asus_wmi: fan_curve_get_factory_default (0x00110025) failed: -19 [ 29.312630] asus_wmi: fan_curve_get_factory_default (0x00110032) failed: -19 [ 30.186596] thermal thermal_zone7: failed to read out thermal zone (-61) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: lm-sensors 1:3.6.0-9build1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 15:01:26 2024 InstallationDate: Installed on 2024-03-22 (27 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: lm-sensors UpgradeStatus: Upgraded to noble on 2024-04-11 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062325/+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 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
Today, on my setup (TrueNAS-SCALE-22.12.4.2) I didn't notice any problems with new kernel 5.15.0-105-generic #115-Ubuntu when I copied 5 files with a total size of over 430GB from local disk to the mounted network CIFS drive. -- 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/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: Hi, updated some Ubuntu 22.04 systems to lastest available state this morning, which caused CIFS mounts (from various fileservers) to stop working. Kernel was updated to version 5.15.0-102-generic. I can mount the shares without problems (mount -t cifs), but then, df for example tells me: df: /mnt: Resource temporarily unavailable. I'm able to list and browse all the files, but accessing them (even readonly) is very unstable. Sometimes it works and sometimes it just gives me i/o errors. Switching back to 5.15.0-101-generic or 5.15.0-100-generic solves the problem and everything works again as expected. Seems like some bug has been implemented in 5.15.0-102-generic... To reproduce the problem, I started a while loop on one server to write to some file on a specific mounted CIFS share and read it from another one root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; sleep 1 ; done -bash: /mnt/hallo.txt: Input/output error -bash: /mnt/hallo.txt: Input/output error ^C root@:~$ tail -f /mnt/hallo.txt Tue Apr 9 04:10:52 PM CEST 2024 hallo Tue Apr 9 04:10:53 PM CEST 2024 hallo Tue Apr 9 04:10:54 PM CEST 2024 hallo Tue Apr 9 04:10:55 PM CEST 2024 hallo Tue Apr 9 04:10:56 PM CEST 2024 hallo Tue Apr 9 04:10:57 PM CEST 2024 hallo Tue Apr 9 04:10:58 PM CEST 2024 hallo Tue Apr 9 04:10:59 PM CEST 2024 hallo Tue Apr 9 04:11:00 PM CEST 2024 hallo Tue Apr 9 04:11:01 PM CEST 2024 hallo tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: Resource temporarily unavailable Tue Apr 9 04:11:04 PM CEST 2024 hallo Tue Apr 9 04:11:05 PM CEST 2024 hallo Tue Apr 9 04:11:06 PM CEST 2024 hallo Tue Apr 9 04:11:07 PM CEST 2024 hallo Tue Apr 9 04:11:08 PM CEST 2024 hallo Tue Apr 9 04:11:09 PM CEST 2024 hallo Tue Apr 9 04:11:10 PM CEST 2024 hallo While doing this, both servers tell me, the resource is unavailable root@:~# df -h /mnt df: /mnt: Resource temporarily unavailable root@:~$ df -h /mnt df: /mnt: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
This bug is awaiting verification that the linux- aws-5.15/5.15.0-1061.67~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- aws-5.15' to 'verification-done-focal-linux-aws-5.15'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws-5.15' to 'verification-failed-focal-linux-aws-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-aws-5.15-v2 verification-needed-focal-linux-aws-5.15 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: Hi, updated some Ubuntu 22.04 systems to lastest available state this morning, which caused CIFS mounts (from various fileservers) to stop working. Kernel was updated to version 5.15.0-102-generic. I can mount the shares without problems (mount -t cifs), but then, df for example tells me: df: /mnt: Resource temporarily unavailable. I'm able to list and browse all the files, but accessing them (even readonly) is very unstable. Sometimes it works and sometimes it just gives me i/o errors. Switching back to 5.15.0-101-generic or 5.15.0-100-generic solves the problem and everything works again as expected. Seems like some bug has been implemented in 5.15.0-102-generic... To reproduce the problem, I started a while loop on one server to write to some file on a specific mounted CIFS share and read it from another one root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; sleep 1 ; done -bash: /mnt/hallo.txt: Input/output error -bash: /mnt/hallo.txt: Input/output error ^C root@:~$ tail -f /mnt/hallo.txt Tue Apr 9 04:10:52 PM CEST 2024 hallo Tue Apr 9 04:10:53 PM CEST 2024 hallo Tue Apr 9 04:10:54 PM CEST 2024 hallo Tue Apr 9 04:10:55 PM CEST 2024 hallo Tue Apr 9 04:10:56 PM CEST 2024 hallo Tue Apr 9 04:10:57 PM CEST 2024 hallo Tue Apr 9 04:10:58 PM CEST 2024 hallo Tue Apr 9 04:10:59 PM CEST 2024 hallo Tue Apr 9 04:11:00 PM CEST 2024 hallo Tue Apr 9 04:11:01 PM CEST 2024 hallo tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: Resource temporarily unavailable Tue Apr 9 04:11:04 PM CEST 2024 hallo Tue Apr 9 04:11:05 PM CEST 2024 hallo Tue Apr 9 04:11:06 PM CEST 2024 hallo Tue Apr 9 04:11:07 PM CEST 2024 hallo Tue Apr 9 04:11:08 PM CEST 2024 hallo Tue Apr 9 04:11:09 PM CEST 2024 hallo Tue Apr 9 04:11:10 PM CEST 2024 hallo While doing this, both servers tell me, the resource is unavailable root@:~# df -h /mnt df: /mnt: Resource temporarily unavailable root@:~$ df -h /mnt df: /mnt: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2044630] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build
Same here: can't appear to install anything new zfs-2.1.5-1ubuntu6~22.04.4 zfs-kmod-2.2.0-0ubuntu1~23.10.2 I'm not seeing any time-to-fix notices -- 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/2044630 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.2- Kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build kernel module. Genrated Crash report, but couldn't send it on it's own. Error it kept throwing was: >>> Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ... Loading new zfs-2.1.5 DKMS files... Building for 6.2.0-36-generic 6.2.0-37-generic Building initial module for 6.2.0-36-generic configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.2 *** Compatible Kernels: 3.10 - 5.19 ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/zfs-dkms.0.crash' Error! Bad return status for module build on kernel: 6.2.0-36-generic (x86_64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 >>> ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Nov 25 21:00:27 2023 InstallationDate: Installed on 2021-09-23 (793 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-17 (466 days ago) To recreate: - Install Ubuntu 22.04.3. - Update to current. - Install package 'zfs-dkms' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+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 2063143] Re: Frequent boot to black display
** Changed in: linux-meta (Ubuntu) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2063143 Title: Frequent boot to black display Status in linux-meta package in Ubuntu: New Bug description: Hardware: AMD Framework 13 OS: Ubuntu Noble 24.04 DE: Plasma Wayland BIOS: version 3.03 and 3.05 (latest new release) Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux This issue started about 2-3 weeks ago I believe around the time that Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages. This issue may not be a kernel regression but instead a wayland regression but I am not certain and looking for help. The issue is that on boot the (internal laptop and external displays if connected) are black but backlight is lit. I am able to boot into recovery mode without issue since the graphics drivers are not loaded in that case (only amd framebuffer driver and userspace mesa llvmpipe). Cold boot from OFF seems to be the most common case for this issue and it happens about 50-75% of the time from there. I have to force power the device off and try again in this case. I don't know how to get proper bootlogs from the previous boot when this is the case since /var/log only seems to contain logs from the current boot. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Mon Apr 22 13:35:21 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Framework Computer Inc. Phoenix1 [f111:0006] InstallationDate: Installed on 2023-11-16 (159 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP05 dmi.board.vendor: Framework dmi.board.version: A5 dmi.chassis.asset.tag: FRANDGCPA5342400SJ dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A5 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP05 dmi.product.version: A5 dmi.sys.vendor: Framework version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 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-meta/+bug/2063143/+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 2063077] Re: Keyboard does not work after waking up from suspend with 5.15.0-105 (but works with 5.15.0-101)
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Anthony Wong (anthonywong) -- 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/2063077 Title: Keyboard does not work after waking up from suspend with 5.15.0-105 (but works with 5.15.0-101) Status in linux package in Ubuntu: New Bug description: Dear Ubuntu maintainers, I think I found a regression in linux 5.15.0-105. In the past few days, my keyboard stopped working after waking up from suspend (sleep), so I couldn't unlock my laptop. Various workarounds found on the internet helped, but I wanted to investigate if it was a gdm issue, grub, or a hardware failure. I managed to narrow it down to the kernel, which is why I'm filing this bug report. AFAICT the only keys that work are the keyboard lights and the brightness knobs (in the Fn functions). I can confirm that 5.15.0-105 has the issue, and I can consistently reproduce it with the following steps: 1. boot fresh with 5.15.0-105 2. login to my account 3. choose suspend from the power menu 4. wake up Following the same steps above with the last kernel available does not cause the issue (package version 5.15.0-101.111). I'll keep using that one for the time being. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-105-generic 5.15.0-105.115 ProcVersionSignature: Ubuntu 5.15.0-105.115-generic 5.15.148 Uname: Linux 5.15.0-105-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philsf 5465 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 02:58:26 2024 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ab7cb5b3-b98e-4d3a-8923-b75a557d5ddc InstallationDate: Installed on 2018-06-07 (2145 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:28c1 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-105-generic root=UUID=670af779-d73e-4cb4-b272-d3240de0c998 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-5.15.0-105-generic N/A linux-backports-modules-5.15.0-105-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2023 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0TXW78 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/06/2023:br1.14:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0TXW78:rvrA00:cvnDellInc.:ct10:cvr:sku0810: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063077/+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 2063074] Re: Waydroid breaks nouveau
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Anthony Wong (anthonywong) -- 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/2063074 Title: Waydroid breaks nouveau Status in linux package in Ubuntu: New Bug description: https://waydro.id/ The session is forced to logout. nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30070]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30070]] subc 0 class c597 mthd 17e0 data 0018 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30107]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30107]] subc 0 class c597 mthd 17e0 data 0018 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30145]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 5 [007fa46000 RenderThread[30145]] subc 0 class c597 mthd 17e0 data 0018 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 7 [007f898000 RenderThread[26039]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 7 [007f898000 RenderThread[26039]] subc 0 class c597 mthd 17e0 data 000c nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 7 [007f898000 RenderThread[26039]] subc 0 class c597 mthd 17e0 data 0060 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 8 [007f862000 RenderThread[26090]] subc 0 class c597 mthd 0d78 data 0004 nouveau :59:00.0: gr: DATA_ERROR 009c [] ch 8 [007f862000 RenderThread[26090]] subc 0 class c597 mthd 17e0 data 0018 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-31-generic 6.8.0-31.31 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:neo3373 F pipewire /dev/snd/controlC0: neo3373 F pipewire neo3377 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 07:32:35 2024 InstallationDate: Installed on 2024-03-22 (30 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-31-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash ipv6.disable=1 RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-04-11 (11 days ago) dmi.bios.date: 04/22/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX435EG.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX435EG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX435EG_UX435EG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063074/+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 2060748] Re: iwlwifi error popping up every few minutes in Kubuntu 23.10 using Intel AX210 card
For some reason, Launchpad will not let me upload the trace.dat file from trace-cmd. As far as updating firmware for iwlwifi, do you have any guidance for how to upgrade firmware to -84 correctly. I am happy to try to see if it fixes the problem, but I am not familiar with the correct process for updating a firmware module out of standard apt tree and don't want to accidentally break something. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060748 Title: iwlwifi error popping up every few minutes in Kubuntu 23.10 using Intel AX210 card Status in linux package in Ubuntu: New Bug description: I just installed Kubuntu 23.10 (using latest default kernel) on a new desktop PC I built, which uses an AX210NGW DTK M.2 wifi/bluetooth card. Here is output from lspci -v: e4:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz Flags: bus master, fast devsel, latency 0, IRQ 381, IOMMU group 15 Memory at ba30 (64-bit, non-prefetchable) [size=16K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] MSI-X: Enable+ Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] L1 PM Substates Kernel driver in use: iwlwifi Kernel modules: iwlwifi Wifi error popping up every few minutes in Kubuntu I just installed Kubuntu 23.10 on a new desktop PC I built, which uses an AX210NGW DTK M.2 wifi card: Code: e4:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz Flags: bus master, fast devsel, latency 0, IRQ 381, IOMMU group 15 Memory at ba30 (64-bit, non-prefetchable) [size=16K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] MSI-X: Enable+ Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] L1 PM Substates Kernel driver in use: iwlwifi Kernel modules: iwlwifi The internet seems to be somewhat working, but at least once a minute I have two "Network Management" error notifications that pop up in KDE that say "Connection Wired Connection 3 deactivated" and "Wired Interface e2x52e8ae7d39d1: IP configuration was unavailable". I checked the logs in /var/log/dmesg and saw that there were a ton of iwlwifi error messages in there that look like this: [ 44.926474] kernel: Intel(R) Wireless WiFi driver for Linux [ 44.926508] kernel: iwlwifi :e4:00.0: enabling device ( -> 0002) [ 44.927758] kernel: iwlwifi :e4:00.0: Detected crf-id 0x400410, cnv-id 0x400410 wfpm id 0x8000 [ 44.927763] kernel: iwlwifi :e4:00.0: PCI dev 2725/0024, rev=0x420, rfid=0x10d000 [ 44.931064] kernel: iwlwifi :e4:00.0: api flags index 2 larger than supported by driver [ 44.931076] kernel: iwlwifi :e4:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.41 [ 44.931318] kernel: iwlwifi :e4:00.0: loaded firmware version 83.e8f84e98.0 ty-a0-gf-a0-83.ucode op_mode iwlmvm [ 44.955070] kernel: Bluetooth: Core ver 2.22 [ 44.955089] kernel: NET: Registered PF_BLUETOOTH protocol family [ 44.955090] kernel: Bluetooth: HCI device and connection manager initialized [ 44.955095] kernel: Bluetooth: HCI socket layer initialized [ 44.955097] kernel: Bluetooth: L2CAP socket layer initialized [ 44.955101] kernel: Bluetooth: SCO socket layer initialized [ 45.275827] kernel: Bluetooth: hci0: Device revision is 0 [ 45.275833] kernel: Bluetooth: hci0: Secure boot is enabled [ 45.275836] kernel: Bluetooth: hci0: OTP lock is enabled [ 45.275838] kernel: Bluetooth: hci0: API lock is enabled [ 45.275840] kernel: Bluetooth: hci0: Debug lock is disabled [ 45.275842] kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 45.275845] kernel: Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38 [ 45.276888] kernel: nvidia :c1:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none [ 45.278400] kernel: Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi [ 45.278415] kernel: Bluetooth: hci0: Boot Address: 0x100800 [ 45.278416] kernel: Bluetooth: hci0: Firmware Version: 254-28.23 [ 47.405919] kernel: iwlwifi :e4:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20 [ 47.405936] kernel: iwlwifi :e4:00.0: WFPM_LMAC2_PD
[Kernel-packages] [Bug 2063165] [NEW] CPU not thermal throttling at max temp (AMD 7965WX on WRX90E-SAGE motherboard)
Public bug reported:
I am running Ubuntu 23.10, and using an ASUS WRX90E-SAGE motherboard.
My CPU (AMD 7965WX) is not properly thermally throttling, and is
exceeding the max operating temperature of 95C without throttling (it
has gotten as high as 98 before I shut it off).
If I run CPU intensive processes that max out all cores (such as stress-
ng), I can quickly exceed the maximum temp within less than a minute,
and Ubuntu does nothing to throttle the CPU. I'm worried that my CPU is
going to get damaged.
When I look at
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors there
are only "powersave" and "performance" available ("powersave" is what it
is currently set to).
If I try to set to "performance" governor in /etc/init.d/cpufrequtils
and reboot, it has no effect. It just stays in "powersave" mode. (I
don't know that this would help anyway as far as throttling, but I don't
know what else to try)
When I run `systemctl status --lines=50 thermald` I get the following
output:
○ thermald.service - Thermal Daemon Service
Loaded: loaded (/lib/systemd/system/thermald.service; enabled; preset:
enabled)
Active: inactive (dead) since Mon 2024-04-22 14:34:09 PDT; 26min ago
Process: 1878 ExecStart=/usr/sbin/thermald --systemd --dbus-enable
--adaptive (code=exited, status=0/SUCCESS)
Main PID: 1878 (code=exited, status=0/SUCCESS)
CPU: 11ms
Apr 22 14:34:09 ML-tower systemd[1]: Starting thermald.service - Thermal Daemon
Service...
Apr 22 14:34:09 ML-tower thermald[1878]: Unsupported cpu model or platform
Apr 22 14:34:09 ML-tower systemd[1]: thermald.service: Deactivated successfully.
Apr 22 14:34:09 ML-tower systemd[1]: Started thermald.service - Thermal Daemon
Service.
===
Note that it says "Unsupported cpu model or platform". The AMD 7965WX is
definitely supported by this motherboard, so I'm not sure what is going
on.
It does seem to be able to read the CPU thermal sensor, because when I
run `sensors` I get the following output:
k10temp-pci-00c3
Adapter: PCI adapter
Tctl: +46.9°C
Tccd1:+40.4°C
Tccd2:+40.6°C
Tccd3:+40.1°C
Tccd4:+39.6°C
... but I don't know how accurate the readings are, and am concerned
especially since it doesn't appear tyo do anything when max temperature
exceeded.
How can I ensure that my CPU will not exceed a specified temperature
threshold (ideally ~93C or less)?
Please let me know if there is any other information that I could
provide to help debug this issue.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: thermald 2.5.4-2
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Mon Apr 22 17:36:51 2024
InstallationDate: Installed on 2024-04-08 (15 days ago)
InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
SourcePackage: thermald
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.init.thermald.conf: [deleted]
mtime.conffile..etc.thermald.thermal-cpu-cdev-order.xml: 2023-08-25T03:29:11
** Affects: thermald (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic
** Description changed:
I am running Ubuntu 23.10, and using an ASUS WRX90E-SAGE motherboard.
My CPU (AMD 7965WX) is not properly thermally throttling, and is
exceeding the max operating temperature of 95C without throttling (it
has gotten as high as 98 before I shut it off).
If I run CPU intensive processes that max out all cores (such as stress-
ng), I can quickly exceed the maximum temp within less than a minute,
and Ubuntu does nothing to throttle the CPU. I'm worried that my CPU is
going to get damaged.
When I look at
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors there
are only "powersave" and "performance" available ("powersave" is what it
is currently set to).
If I try to set to "performance" governor in /etc/init.d/cpufrequtils
- and reboot, it has no effect. It just stays in "powersave" mode. I don't
- know that this would help anyway as far as throttling, but I don't know
- what else to try.
+ and reboot, it has no effect. It just stays in "powersave" mode. (I
+ don't know that this would help anyway as far as throttling, but I don't
+ know what else to try)
When I run `systemctl status --lines=50 thermald` I get the following
output:
-
- ○ thermald.service - Thermal Daemon Service
- Loaded: loaded (/lib/systemd/system/thermald.service; enabled; preset:
enabled)
- Active: inactive (dead) since Mon 2024-04-22 14:34:09 PDT; 26min ago
- Process: 1878 ExecStart=/usr/sbin/thermald --systemd --dbus-enable
--adaptive (code=exited, status=0/SUCCESS)
-Main PID: 1878 (code=exited, status=0/SUCCESS)
- CPU: 11ms
+ ○ thermald.s
[Kernel-packages] [Bug 2062951] Re: Random flickering with i915 on Linux 6.8
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2062951 Title: Random flickering with i915 on Linux 6.8 Status in linux package in Ubuntu: Confirmed Bug description: After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy flickering at random. It happens after a moderate to heavy on screen activity like window switching, scrolling etc. It never happens when playing video or when there is no interaction using keyboard/pointer. It tend to happen when the mouse cursor is in the bottom quarter of the screen and stops immediately when the cursor leaves that screen region. Around the same time the following appears in kernel log: kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun Happens on both X11 and Wayland on both KDE plasma and Mate (though less). I first encountered the issue with Linux 6.8.0-11 and it still happens with Ubunutu's 6.8.0-28 and Mainline 6.8.7. Kernels 6.6, 6.5, 6.1 and older did not have that issue. Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD Graphics 520] Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26 Attaching kernel log for 6.8.0-28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062951/+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 2060716] Re: Screen flickering again
The lasted nvidia-driver is 535.171.04, 550.67 and 525.147.05
Please try if any of them can fix nvidia error.
--
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/2060716
Title:
Screen flickering again
Status in linux package in Ubuntu:
New
Bug description:
There is random screen flickering with the build of kernel 6.5.0-27.
Also other builds of 6.5.0 have this flickering.
The *only* build of this version that does work without flickering is
6.5.0-13
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-27-generic 6.5.0-27.28
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: bf 5114 F pipewire
bf 5119 F wireplumber
/dev/snd/controlC0: bf 5119 F wireplumber
/dev/snd/seq:bf 5114 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 9 18:48:35 2024
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=be4de94b-3fb1-44d1-875a-edcd620dc310
InstallationDate: Installed on 2016-03-18 (2944 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic
root=UUID=17026de9-c699-420e-ae96-01ac290b69ef ro quiet splash
i915.enable_psr=0 vt.handoff=7
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-27-generic N/A
linux-backports-modules-6.5.0-27-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/29/2023
dmi.bios.release: 1.30
dmi.bios.vendor: LENOVO
dmi.bios.version: N2VET45W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TK000AGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnLENOVO:bvrN2VET45W(1.30):bd08/29/2023:br1.30:efr1.11:svnLENOVO:pn20TK000AGE:pvrThinkPadX1ExtremeGen3:rvnLENOVO:rn20TK000AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TK_BU_Think_FM_ThinkPadX1ExtremeGen3:
dmi.product.family: ThinkPad X1 Extreme Gen 3
dmi.product.name: 20TK000AGE
dmi.product.sku: LENOVO_MT_20TK_BU_Think_FM_ThinkPad X1 Extreme Gen 3
dmi.product.version: ThinkPad X1 Extreme Gen 3
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060716/+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 2063150] Re: No sound after upgrade to 24.04
Please run: alsa-info and attach the text file it creates. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2063150 Title: No sound after upgrade to 24.04 Status in linux package in Ubuntu: Incomplete Status in pipewire package in Ubuntu: New Bug description: After upgrading from Ubuntu 23.10 to 24.04, it does not work on the computer. Work with: 1) Bluetooth 2) Jack 3.5 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: pipewire 1.0.5-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 15:52:58 2024 InstallationDate: Installed on 2024-03-25 (28 days ago) InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: pipewire UpgradeStatus: Upgraded to noble on 2024-04-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063150/+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 2051123] Re: Kernel traces leading to crash - refcount_t: underflow; use-after-free and refcount_t: saturated; leaking memory -- lib/refcount.c
Could you try the latest upstream kernel which convert dm-crypt's
tasklet to BH workqueue? I suppose the commit fb6ad4aec1d0 ("dm-crypt:
Convert from tasklet to BH workqueue") might resolve the issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2051123
Title:
Kernel traces leading to crash - refcount_t: underflow; use-after-free
and refcount_t: saturated; leaking memory -- lib/refcount.c
Status in linux-hwe-6.5 package in Ubuntu:
Confirmed
Bug description:
A few hours after upgrading a machine serving as VM hypervisor running
OpenStack Nova + libvirt from linux kernel 6.2.0-37-generic to
6.5.0-14-generic we observed kernel traces and quick disintegration of
the system and its various processes.
While the TCP connection itself was accepted, we were unable to log in via
SSH anymore or use the console.
A hard reset was required to get the machine back up. We went back to the
former HWE kernel version, 6.2.0-37-generic, and have not observed any issues
since.
Attached is all of the kernel log from bootup to the crash - this is where
the issues started ...
```
[...]
Jan 23 11:36:13 fra-az1-comp-21 kernel: vxlan-304: fa:16:3e:7f:e2:6f migrated
from 10.101.11.98 to 10.101.11.101
Jan 23 11:41:05 fra-az1-comp-21 kernel: hrtimer: interrupt took 32482 ns
Jan 23 12:02:41 fra-az1-comp-21 kernel: clocksource: timekeeping watchdog on
CPU50: hpet wd-wd read-back delay of 245561ns
Jan 23 12:02:41 fra-az1-comp-21 kernel: clocksource: wd-tsc-wd read-back
delay of 245561ns, clock-skew test skipped!
Jan 23 12:18:18 fra-az1-comp-21 kernel: perf: interrupt took too long (2509 >
2500), lowering kernel.perf_event_max_sample_rate to 79500
Jan 23 12:44:35 fra-az1-comp-21 kernel: clocksource: timekeeping watchdog on
CPU127: hpet wd-wd read-back delay of 244863ns
Jan 23 12:44:35 fra-az1-comp-21 kernel: clocksource: wd-tsc-wd read-back
delay of 245352ns, clock-skew test skipped!
Jan 23 13:08:56 fra-az1-comp-21 kernel: clocksource: timekeeping watchdog on
CPU16: hpet wd-wd read-back delay of 243257ns
Jan 23 13:08:56 fra-az1-comp-21 kernel: clocksource: wd-tsc-wd read-back
delay of 247517ns, clock-skew test skipped!
Jan 23 14:13:58 fra-az1-comp-21 kernel: clocksource: timekeeping watchdog on
CPU52: hpet wd-wd read-back delay of 248076ns
Jan 23 14:13:58 fra-az1-comp-21 kernel: clocksource: wd-tsc-wd read-back
delay of 245142ns, clock-skew test skipped!
Jan 23 14:31:18 fra-az1-comp-21 kernel: clocksource: timekeeping watchdog on
CPU124: hpet wd-wd read-back delay of 245073ns
Jan 23 14:31:18 fra-az1-comp-21 kernel: clocksource: wd-tsc-wd read-back
delay of 231034ns, clock-skew test skipped!
Jan 23 15:13:52 fra-az1-comp-21 kernel: clocksource: timekeeping watchdog on
CPU24: hpet wd-wd read-back delay of 244863ns
Jan 23 15:13:52 fra-az1-comp-21 kernel: clocksource: wd-tsc-wd read-back
delay of 245701ns, clock-skew test skipped!
Jan 23 15:35:18 fra-az1-comp-21 kernel: clocksource: timekeeping watchdog on
CPU76: hpet wd-wd read-back delay of 245282ns
Jan 23 15:35:18 fra-az1-comp-21 kernel: clocksource: wd-tsc-wd read-back
delay of 245841ns, clock-skew test skipped!
Jan 23 16:10:49 fra-az1-comp-21 kernel: clocksource: timekeeping watchdog on
CPU27: hpet wd-wd read-back delay of 244653ns
Jan 23 16:10:49 fra-az1-comp-21 kernel: clocksource: wd-tsc-wd read-back
delay of 245980ns, clock-skew test skipped!
Jan 23 16:12:49 fra-az1-comp-21 kernel: workqueue: drain_vmap_area_work
hogged CPU for >1us 4 times, consider switching to WQ_UNBOUND
Jan 23 16:20:56 fra-az1-comp-21 kernel: clocksource: timekeeping watchdog on
CPU0: hpet wd-wd read-back delay of 242907ns
Jan 23 16:20:56 fra-az1-comp-21 kernel: clocksource: wd-tsc-wd read-back
delay of 247796ns, clock-skew test skipped!
Jan 23 16:25:04 fra-az1-comp-21 kernel: [ cut here ]
Jan 23 16:25:04 fra-az1-comp-21 kernel: refcount_t: underflow; use-after-free.
Jan 23 16:25:04 fra-az1-comp-21 kernel: WARNING: CPU: 84 PID: 7072 at
lib/refcount.c:28 refcount_warn_saturate+0xa3/0x150
Jan 23 16:25:04 fra-az1-comp-21 kernel: Modules linked in: xt_multiport
ebt_arp nft_meta_bridge xt_CT xt_mac xt_set xt_state ip_set_hash_net ip_set
vhost_net vhost vhost_iotlb tap xt_policy xt_REDIRECT xt_nat xt_connmark
xt_mark vxlan ip6_udp_tunnel udp_tunnel xt_comment xt_physdev veth xt_CHECKSUM
xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat
nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables
nfnetlink xfrm_user xfrm_algo nvme_fabrics 8021q garp mrp br_netfilter bridge
stp llc bonding binfmt_misc tls nls_ascii ipmi_ssif intel_rapl_msr
intel_rapl_common amd64_edac edac_mce_amd kvm_amd kvm irqbypass rapl wmi_bmof
irdma ib_uverbs ib_core joydev input_leds ccp k10temp ptdma switchtec acpi_ipmi
ipmi_si ipmi_devintf ipmi
[Kernel-packages] [Bug 2062950] Re: RE: Flickering problems on external monitor with HDMI after installing Ubuntu 23.10
Thanks. It was unclear from the first bug which monitor was flickering.
In the first bug it sounded like the laptop. In this second bug it
sounded like the external monitor. Now the video shows it's the laptop
screen.
Is it only the laptop screen flickering?
I'm wondering if this is due to a loss of HDMI connection to the
external monitor causing the system to reconfigure all displays
including the built-in.
Next time the problem happens, please open a Terminal and run:
journalctl -b0 > journal.txt
and attach the resulting file here.
--
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/2062950
Title:
RE: Flickering problems on external monitor with HDMI after installing
Ubuntu 23.10
Status in linux package in Ubuntu:
Incomplete
Bug description:
this is a continuation of the bug reported in
https://bugs.launchpad.net/ubuntu/+bug/2062504
I reinstalled ubuntu 23, and didn't install anything else. I'm still
having the flickering when connecting an HDMI to an external monitor.
please help
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 19 22:27:21 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c)
(prog-if 00 [VGA controller])
Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a6]
InstallationDate: Installed on 2024-04-20 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic
root=UUID=92611de2-ed0a-4611-b724-820a5d29be02 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/23/2024
dmi.bios.release: 1.23
dmi.bios.vendor: LENOVO
dmi.bios.version: R1UET46W (1.23 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21B4S4QB00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76465 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.14
dmi.modalias:
dmi:bvnLENOVO:bvrR1UET46W(1.23):bd02/23/2024:br1.23:efr1.14:svnLENOVO:pn21B4S4QB00:pvrThinkPadL13Gen3:rvnLENOVO:rn21B4S4QB00:rvrSDK0T76465WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21B4_BU_Think_FM_ThinkPadL13Gen3:
dmi.product.family: ThinkPad L13 Gen 3
dmi.product.name: 21B4S4QB00
dmi.product.sku: LENOVO_MT_21B4_BU_Think_FM_ThinkPad L13 Gen 3
dmi.product.version: ThinkPad L13 Gen 3
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
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/+bug/2062950/+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 2059263] Re: Fix acpi_power_meter accessing IPMI region before it's ready
** 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/2059263 Title: Fix acpi_power_meter accessing IPMI region before it's ready Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Confirmed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Confirmed Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] ACPI error can be found in kernel message: [3.717920] ACPI Error: No handler for Region [SYSI] (ab9e62c5) [IPMI] (20230628/evregion-130) [Fix] On Dell systems that have IPI0001 device, ensure IPMI region is ready before acpi_power_meter invokes any ACPI method. [Test] With the patch applied, no such error can be found in kernel message. acpi_power_meter sysfs also works correctly. [Where problems could occur] If asynchronous probe is disabled, the device drivers that probe after acpi_power_meter needs to wait until the completion is done, hence the boot time might be slower. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2059263/+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 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
Nelle, Seems no one else is experiencing the issue I described above, so it's probably a me problem. I will do more troubleshooting on my end. Thanks for sharing your results. -- 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/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: Hi, updated some Ubuntu 22.04 systems to lastest available state this morning, which caused CIFS mounts (from various fileservers) to stop working. Kernel was updated to version 5.15.0-102-generic. I can mount the shares without problems (mount -t cifs), but then, df for example tells me: df: /mnt: Resource temporarily unavailable. I'm able to list and browse all the files, but accessing them (even readonly) is very unstable. Sometimes it works and sometimes it just gives me i/o errors. Switching back to 5.15.0-101-generic or 5.15.0-100-generic solves the problem and everything works again as expected. Seems like some bug has been implemented in 5.15.0-102-generic... To reproduce the problem, I started a while loop on one server to write to some file on a specific mounted CIFS share and read it from another one root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; sleep 1 ; done -bash: /mnt/hallo.txt: Input/output error -bash: /mnt/hallo.txt: Input/output error ^C root@:~$ tail -f /mnt/hallo.txt Tue Apr 9 04:10:52 PM CEST 2024 hallo Tue Apr 9 04:10:53 PM CEST 2024 hallo Tue Apr 9 04:10:54 PM CEST 2024 hallo Tue Apr 9 04:10:55 PM CEST 2024 hallo Tue Apr 9 04:10:56 PM CEST 2024 hallo Tue Apr 9 04:10:57 PM CEST 2024 hallo Tue Apr 9 04:10:58 PM CEST 2024 hallo Tue Apr 9 04:10:59 PM CEST 2024 hallo Tue Apr 9 04:11:00 PM CEST 2024 hallo Tue Apr 9 04:11:01 PM CEST 2024 hallo tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: Resource temporarily unavailable Tue Apr 9 04:11:04 PM CEST 2024 hallo Tue Apr 9 04:11:05 PM CEST 2024 hallo Tue Apr 9 04:11:06 PM CEST 2024 hallo Tue Apr 9 04:11:07 PM CEST 2024 hallo Tue Apr 9 04:11:08 PM CEST 2024 hallo Tue Apr 9 04:11:09 PM CEST 2024 hallo Tue Apr 9 04:11:10 PM CEST 2024 hallo While doing this, both servers tell me, the resource is unavailable root@:~# df -h /mnt df: /mnt: Resource temporarily unavailable root@:~$ df -h /mnt df: /mnt: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2063143] Re: Frequent boot to black display
Also, are there any files in /var/crash ? -- 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/2063143 Title: Frequent boot to black display Status in linux package in Ubuntu: Incomplete Bug description: Hardware: AMD Framework 13 OS: Ubuntu Noble 24.04 DE: Plasma Wayland BIOS: version 3.03 and 3.05 (latest new release) Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux This issue started about 2-3 weeks ago I believe around the time that Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages. This issue may not be a kernel regression but instead a wayland regression but I am not certain and looking for help. The issue is that on boot the (internal laptop and external displays if connected) are black but backlight is lit. I am able to boot into recovery mode without issue since the graphics drivers are not loaded in that case (only amd framebuffer driver and userspace mesa llvmpipe). Cold boot from OFF seems to be the most common case for this issue and it happens about 50-75% of the time from there. I have to force power the device off and try again in this case. I don't know how to get proper bootlogs from the previous boot when this is the case since /var/log only seems to contain logs from the current boot. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Mon Apr 22 13:35:21 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Framework Computer Inc. Phoenix1 [f111:0006] InstallationDate: Installed on 2023-11-16 (159 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP05 dmi.board.vendor: Framework dmi.board.version: A5 dmi.chassis.asset.tag: FRANDGCPA5342400SJ dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A5 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP05 dmi.product.version: A5 dmi.sys.vendor: Framework version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 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/+bug/2063143/+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 2063143] Re: Frequent boot to black display
Next time you have a failed boot followed by a successful boot, please run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Package changed: linux-meta (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: amdgpu -- 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/2063143 Title: Frequent boot to black display Status in linux package in Ubuntu: Incomplete Bug description: Hardware: AMD Framework 13 OS: Ubuntu Noble 24.04 DE: Plasma Wayland BIOS: version 3.03 and 3.05 (latest new release) Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux This issue started about 2-3 weeks ago I believe around the time that Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages. This issue may not be a kernel regression but instead a wayland regression but I am not certain and looking for help. The issue is that on boot the (internal laptop and external displays if connected) are black but backlight is lit. I am able to boot into recovery mode without issue since the graphics drivers are not loaded in that case (only amd framebuffer driver and userspace mesa llvmpipe). Cold boot from OFF seems to be the most common case for this issue and it happens about 50-75% of the time from there. I have to force power the device off and try again in this case. I don't know how to get proper bootlogs from the previous boot when this is the case since /var/log only seems to contain logs from the current boot. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Mon Apr 22 13:35:21 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Framework Computer Inc. Phoenix1 [f111:0006] InstallationDate: Installed on 2023-11-16 (159 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP05 dmi.board.vendor: Framework dmi.board.version: A5 dmi.chassis.asset.tag: FRANDGCPA5342400SJ dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A5 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP05 dmi.product.version: A5 dmi.sys.vendor: Framework version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 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/+bug/2063143/+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 2063179] [NEW] package linux-modules-nvidia-470-6.5.0-27-generic 6.5.0-27.28~22.04.1+2 failed to install/upgrade: installed linux-modules-nvidia-470-6.5.0-27-generic package pos
Public bug reported: the problem occurred during installation while trying to remove previous package ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-nvidia-470-6.5.0-27-generic 6.5.0-27.28~22.04.1+2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Apr 23 09:40:31 2024 ErrorMessage: installed linux-modules-nvidia-470-6.5.0-27-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-01-25 (88 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.12 SourcePackage: linux-restricted-modules-hwe-6.5 Title: package linux-modules-nvidia-470-6.5.0-27-generic 6.5.0-27.28~22.04.1+2 failed to install/upgrade: installed linux-modules-nvidia-470-6.5.0-27-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-restricted-modules-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2063179 Title: package linux-modules-nvidia-470-6.5.0-27-generic 6.5.0-27.28~22.04.1+2 failed to install/upgrade: installed linux- modules-nvidia-470-6.5.0-27-generic package post-installation script subprocess returned error exit status 1 Status in linux-restricted-modules-hwe-6.5 package in Ubuntu: New Bug description: the problem occurred during installation while trying to remove previous package ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-nvidia-470-6.5.0-27-generic 6.5.0-27.28~22.04.1+2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Apr 23 09:40:31 2024 ErrorMessage: installed linux-modules-nvidia-470-6.5.0-27-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-01-25 (88 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.12 SourcePackage: linux-restricted-modules-hwe-6.5 Title: package linux-modules-nvidia-470-6.5.0-27-generic 6.5.0-27.28~22.04.1+2 failed to install/upgrade: installed linux-modules-nvidia-470-6.5.0-27-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-6.5/+bug/2063179/+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 2059263] Re: Fix acpi_power_meter accessing IPMI region before it's ready
** Changed in: linux (Ubuntu Mantic) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Noble) Status: Confirmed => 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/2059263 Title: Fix acpi_power_meter accessing IPMI region before it's ready Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Committed Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] ACPI error can be found in kernel message: [3.717920] ACPI Error: No handler for Region [SYSI] (ab9e62c5) [IPMI] (20230628/evregion-130) [Fix] On Dell systems that have IPI0001 device, ensure IPMI region is ready before acpi_power_meter invokes any ACPI method. [Test] With the patch applied, no such error can be found in kernel message. acpi_power_meter sysfs also works correctly. [Where problems could occur] If asynchronous probe is disabled, the device drivers that probe after acpi_power_meter needs to wait until the completion is done, hence the boot time might be slower. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2059263/+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 2042546] Re: Include cifs.ko in linux-modules package
** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042546 Title: Include cifs.ko in linux-modules package Status in linux package in Ubuntu: In Progress Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: In Progress Bug description: [Impact] Commit: "smb: move client and server files to common directory fs/smb" moved the fs/cifs directory to fs/sb/client. The inclusion list for linux-modules was not updated, it still contains the old path. This means that the cifs.ko module cannot be loaded if only linux-modules package is installed, now being part of linux-modules-extra. For the main kernels this is not a problem because linux-modules-extra is always installed, but for derivatives like aws, azure etc, this module cannot be loaded without explicitly installing linux-modules-extra. [How to reproduce it]: 1. Install the latest azure kernel 6.5.0-1017.17 2. Load cifs module $ modprobe cifs modprobe: FATAL: Module cifs not found in directory /lib/modules/6.5.0-1017-azure If modules-extra is installed, this works. [Fix] Replace fs/cifs/* with fs/smb/client/* in debian./control.d/.inclusion-list. First the main kernels are addressed, derivatives will be fixed via cranky fix. [Test Plan] 1. Apply the fix to one of the derivative (azure), build a new kernel and install it 2. Load cifs module $ modprobe cifs It should work without installing modules-extra. [Regression potential] Very low, it's a straightforward fix. [Other Info] Sending a patch for every derivative takes time and each derivative will be fixed once this proposal is acked via cranky fix. Original for lunar only SRU Justification: [Impact] Commit: "smb: move client and server files to common directory fs/smb" introduced in 2023.09.04 moved the fs/cifs directory to fs/sb/client. The inclusion list for linux-modules was not updated, it still contains the old path. This means that the cifs.ko module cannot be loaded if only linux-modules package is installed, now being part of linux-modules-extra. For lunar:main this is not a problem because linux-modules-extra is always installed, but for derivatives like aws, azure etc, this module cannot be loaded without explicitly installing linux-modules-extra. [How to reproduce it]: 1. Install the latest azure kernel 6.2.0-1016.16 2. Load cifs module $ modprobe cifs modprobe: FATAL: Module cifs not found in directory /lib/modules/6.2.0-1016-azure If modules-extra is installed, this works. [Fix] Replace fs/cifs/* with fs/smb/client/* in debian./control.d/.inclusiojn-list This is going to be done in s2023.10.02 cycle for derivatives. [Test Plan] 1. Apply the fix to one of the derivative (azure), build a new kernel and install it 2. Load cifs module $ modprobe cifs It should work without installing modules-extra. [Regression potential] Very low, it's a straightforward fix. [Other Info] Sending a patch for every derivative takes time and each derivative will be fixed once this proposal is acked. There is also the possibility to do it via cranky fix, but owners may omit it during security updates and it's hard to enforce it. Plus, it is a one-time change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042546/+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
