[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-lowlatency/6.2.0.1005.5)
All autopkgtests for the newly accepted linux-meta-lowlatency (6.2.0.1005.5) for lunar have finished running. The following regressions have been reported in tests triggered by the package: dahdi-linux/1:2.11.1.0.20170917~dfsg-8.4ubuntu1 (amd64) linux-lowlatency/6.2.0-1005.5 (amd64, arm64) systemd/252.5-2ubuntu3 (amd64, arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/lunar/update_excuses.html#linux-meta-lowlatency [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 2022826] Re: Ethernet hangs
@John, could you switch to another router for verification? -- 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/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2022826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/6.2.0.1005.5)
All autopkgtests for the newly accepted linux-meta-azure (6.2.0.1005.5) for lunar have finished running. The following regressions have been reported in tests triggered by the package: systemd/252.5-2ubuntu3 (amd64, arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/lunar/update_excuses.html#linux-meta-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023427] [NEW] Focal update: v5.4.238 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.238 upstream stable patchset from git://git.kernel.org/ ext4: fix cgroup writeback accounting with fs-layer encryption xfrm: Allow transport-mode states with AF_UNSPEC selector drm/panfrost: Don't sync rpm suspension after mmu flushing cifs: Move the in_send statistic to __smb_send_rqst() drm/meson: fix 1px pink line on GXM when scaling video overlay clk: HI655X: select REGMAP instead of depending on it docs: Correct missing "d_" prefix for dentry_operations member d_weak_revalidate scsi: mpt3sas: Fix NULL pointer access in mpt3sas_transport_port_add() ALSA: hda - add Intel DG1 PCI and HDMI ids ALSA: hda - controller is in GPU on the DG1 ALSA: hda: Add Alderlake-S PCI ID and HDMI codec vid ALSA: hda: Add Intel DG2 PCI ID and HDMI codec vid ALSA: hda: Match only Intel devices with CONTROLLER_IN_GPU() netfilter: nft_redir: correct value of inet type `.maxattrs` scsi: core: Fix a comment in function scsi_host_dev_release() scsi: core: Fix a procfs host directory removal regression tcp: tcp_make_synack() can be called from process context nfc: pn533: initialize struct pn533_out_arg properly ipvlan: Make skb->skb_iif track skb->dev for l3s mode i40e: Fix kernel crash during reboot when adapter is in recovery mode qed/qed_dev: guard against a possible division by zero net: tunnels: annotate lockless accesses to dev->needed_headroom net: phy: smsc: bail out in lan87xx_read_status if genphy_read_status fails nfc: st-nci: Fix use after free bug in ndlc_remove due to race condition net: usb: smsc75xx: Limit packet length to skb->len nvmet: avoid potential UAF in nvmet_req_complete() block: sunvdc: add check for mdesc_grab() returning NULL ipv4: Fix incorrect table ID in IOCTL path net: usb: smsc75xx: Move packet length check to prevent kernel panic in skb_pull net/iucv: Fix size of interrupt data ethernet: sun: add check for the mdesc_grab() hwmon: (adt7475) Display smoothing attributes in correct order hwmon: (adt7475) Fix masking of hysteresis registers hwmon: (xgene) Fix use after free bug in xgene_hwmon_remove due to race condition hwmon: (ina3221) return prober error code media: m5mols: fix off-by-one loop termination error mmc: atmel-mci: fix race between stop command and start of next command jffs2: correct logic when creating a hole in jffs2_write_begin ext4: fail ext4_iget if special inode unallocated ext4: fix task hung in ext4_xattr_delete_inode drm/amdkfd: Fix an illegal memory access sh: intc: Avoid spurious sizeof-pointer-div warning ext4: fix possible double unlock when moving a directory tty: serial: fsl_lpuart: skip waiting for transmission complete when UARTCTRL_SBK is asserted interconnect: fix mem leak when freeing nodes tracing: Check field value in hist_field_name() tracing: Make tracepoint lockdep check actually test something ftrace: Fix invalid address access in lookup_rec() when index is 0 fbdev: stifb: Provide valid pixelclock and add fb_check_var() checks x86/mm: Fix use of uninitialized buffer in sme_enable() drm/i915: Don't use stolen memory for ring buffers with LLC serial: 8250_em: Fix UART port type s390/ipl: add missing intersection check to ipl_report handling PCI: Unify delay handling for reset and resume HID: core: Provide new max_buffer_size attribute to over-ride the default HID: uhid: Over-ride the default maximum data buffer value with our own Linux 5.4.238 UBUNTU: Upstream stable to v5.4.238 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Luke Nowakowski-Krijger (lukenow) Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Summary changed: - Focal update: upstream stable patchset 2023-06-09 + Focal update: v5.4.238 upstream stable release ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Luke Nowakowski-Krijger (lukenow) ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by
[Kernel-packages] [Bug 2023426] [NEW] Kinetic update: upstream stable patchset 2023-06-09
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2023-06-09 Ported from the following upstream stable releases: v5.15.104, v6.1.21 v5.15.105, v6.1.22 from git://git.kernel.org/ xfrm: Allow transport-mode states with AF_UNSPEC selector drm/panfrost: Don't sync rpm suspension after mmu flushing cifs: Move the in_send statistic to __smb_send_rqst() drm/meson: fix 1px pink line on GXM when scaling video overlay clk: HI655X: select REGMAP instead of depending on it docs: Correct missing "d_" prefix for dentry_operations member d_weak_revalidate scsi: mpt3sas: Fix NULL pointer access in mpt3sas_transport_port_add() ALSA: hda: Match only Intel devices with CONTROLLER_IN_GPU() netfilter: nft_nat: correct length for loading protocol registers netfilter: nft_masq: correct length for loading protocol registers netfilter: nft_redir: correct length for loading protocol registers netfilter: nft_redir: correct value of inet type `.maxattrs` scsi: core: Fix a procfs host directory removal regression tcp: tcp_make_synack() can be called from process context nfc: pn533: initialize struct pn533_out_arg properly ipvlan: Make skb->skb_iif track skb->dev for l3s mode i40e: Fix kernel crash during reboot when adapter is in recovery mode vdpa_sim: not reset state in vdpasim_queue_ready vdpa_sim: set last_used_idx as last_avail_idx in vdpasim_queue_ready PCI: s390: Fix use-after-free of PCI resources with per-function hotplug drm/i915/display: clean up comments net/smc: fix NULL sndbuf_desc in smc_cdc_tx_handler() qed/qed_dev: guard against a possible division by zero net: dsa: mt7530: remove now incorrect comment regarding port 5 net: dsa: mt7530: set PLL frequency and trgmii only when trgmii is used loop: Fix use-after-free issues net: tunnels: annotate lockless accesses to dev->needed_headroom net: phy: smsc: bail out in lan87xx_read_status if genphy_read_status fails nfc: st-nci: Fix use after free bug in ndlc_remove due to race condition net/smc: fix deadlock triggered by cancel_delayed_work_syn() net: usb: smsc75xx: Limit packet length to skb->len drm/bridge: Fix returned array size name for atomic_get_input_bus_fmts kdoc block: null_blk: Fix handling of fake timeout request nvme: fix handling single range discard request nvmet: avoid potential UAF in nvmet_req_complete() block: sunvdc: add check for mdesc_grab() returning NULL ice: xsk: disable txq irq before flushing hw net: dsa: mv88e6xxx: fix max_mtu of 1492 on 6165, 6191, 6220, 6250, 6290 ravb: avoid PHY being resumed when interface is not up sh_eth: avoid PHY being resumed when interface is not up ipv4: Fix incorrect table ID in IOCTL path net: usb: smsc75xx: Move packet length check to prevent kernel panic in skb_pull net/iucv: Fix size of interrupt data qed/qed_mng_tlv: correctly zero out ->min instead of ->hour ethernet: sun: add check for the mdesc_grab() bonding: restore IFF_MASTER/SLAVE flags on bond enslave ether type change bonding: restore bond's IFF_SLAVE flag if a non-eth dev enslave fails hwmon: (adt7475) Display smoothing attributes in correct order hwmon: (adt7475) Fix masking of hysteresis registers hwmon: (xgene) Fix use after free bug in xgene_hwmon_remove due to race condition hwmon: (ina3221) return prober error code hwmon: (ucd90320) Add minimum delay between bus accesses hwmon: tmp512: drop of_match_ptr for ID table kconfig: Update config changed flag before calling callback hwmon: (adm1266) Set `can_sleep` flag for GPIO chip hwmon: (ltc2992) Set `can_sleep` flag for GPIO chip media: m5mols: fix off-by-one loop termination error mmc: atmel-mci: fix race between stop command and start of next command jffs2: correct logic when creating a hole in jffs2_write_begin ext4: fail ext4_iget if special inode unallocated ext4: update s_journal_inum if it changes after journal replay ext4: fix task hung in ext4_xattr_delete_inode drm/amdkfd: Fix an illegal memory access net/9p: fix bug in client create for .L sh: intc: Avoid spurious sizeof-pointer-div warning drm/amd/display: fix shift-out-of-bounds in CalculateVMAndRowBytes ext4: fix possible double unlock when moving a directory tty: serial: fsl_lpuart: skip waiting for transmission complete when UARTCTRL_SBK is asserted serial: 8250_em: Fix UART port type serial: 8250_fsl: fix handle_irq locking firmware: xilinx: don't make a sleepable memory allocation from an atomic context s390/ipl: add missing intersection check to ipl_report handling interconnect: fix mem leak when freeing nodes
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws/6.2.0.1005.6)
All autopkgtests for the newly accepted linux-meta-aws (6.2.0.1005.6) for lunar have finished running. The following regressions have been reported in tests triggered by the package: dahdi-linux/1:2.11.1.0.20170917~dfsg-8.4ubuntu1 (amd64) systemd/252.5-2ubuntu3 (amd64, arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/lunar/update_excuses.html#linux-meta-aws [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gke-5.15/5.15.0.1036.41~20.04.1)
All autopkgtests for the newly accepted linux-meta-gke-5.15 (5.15.0.1036.41~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-gke-5.15/5.15.0-1036.41~20.04.1 (arm64) systemd/245.4-4ubuntu3.21 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-gke-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2016908
Title:
udev fails to make prctl() syscall with apparmor=0 (as used by maas by
default)
Status in AppArmor:
New
Status in MAAS:
Fix Committed
Status in maas-images:
Invalid
Status in apparmor package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Fix Committed
Status in systemd package in Ubuntu:
Invalid
Status in apparmor source package in Lunar:
Confirmed
Status in linux source package in Lunar:
Fix Committed
Status in systemd source package in Lunar:
Invalid
Bug description:
I'm assuming the image being used for these deploys is 20230417 or
20230417.1 based on the fact that I saw a 6.2 kernel being used which
I don't believe was part of the 20230319 serial. I don't have access
to the maas server, so I can't directly check any log files.
MAAS Version: 3.3.2
Here's where the serial log indicates it can't download the squashfs. The
full log is attached as scobee-lunar-no-squashfs.log (there are some other
console message intermixed):
no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf
/run/net6
-*.conf
::
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
date/squa[ 206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes,
fsverity
=yes
shfs
:: mount_squash downloading
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
4/lunar/candidate/squashfs to /root.tmp.img
Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
wget: can't connect to remote host (10.229.32.21): Network is unreachable
:: mount -t squashfs -o loop '/root.tmp.img' '/root.tmp'
mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
done.
Still gathering logs and info and will update as I go.
Kernel Bug / Apparmor
reproducer
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
$ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'
#start the VM
Starting systemd-udevd version 252.5-2ubuntu3
Spawning shell within the initramfs
BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) udevadm info --export-db
Failed to set death signal: Invalid argument
Observe that udevadm fails to setup death signal, with in systemd code
is this
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
util.c#L1252
if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ?
SIGINT : SIGTERM) < 0) {
log_full_errno(prio, errno, "Failed to set death
signal: %m");
_exit(EXIT_FAILURE);
}
workaround set kernel commandline to `apparmor=1`
MAAS bug
Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor.
Even for deployment and commisioning.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2016908/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023420] [NEW] Focal update: v5.4.237 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.237 upstream stable patchset
from git://git.kernel.org/
fs: prevent out-of-bounds array speculation when closing a file descriptor
x86/CPU/AMD: Disable XSAVES on AMD family 0x17
drm/connector: print max_requested_bpc in state debugfs
ext4: fix RENAME_WHITEOUT handling for inline directories
ext4: fix another off-by-one fsmap error on 1k block filesystems
ext4: move where set the MAY_INLINE_DATA flag is set
ext4: fix WARNING in ext4_update_inline_data
ext4: zero i_disksize when initializing the bootloader inode
nfc: change order inside nfc_se_io error path
iommu/amd: Add PCI segment support for ivrs_[ioapic/hpet/acpihid] commands
iommu/amd: Fix ill-formed ivrs_ioapic, ivrs_hpet and ivrs_acpihid options
iommu/amd: Add a length limitation for the ivrs_acpihid command-line parameter
ipmi:ssif: make ssif_i2c_send() void
ipmi:ssif: resend_msg() cannot fail
ipmi:ssif: Remove rtc_us_timer
ipmi:ssif: Increase the message retry time
ipmi:ssif: Add a timer between request retries
irqdomain: Change the type of 'size' in __irq_domain_add() to be consistent
irqdomain: Fix domain registration race
iommu/vt-d: Fix PASID directory pointer coherency
SMB3: Backup intent flag missing from some more ops
cifs: Fix uninitialized memory read in smb3_qfs_tcon()
scsi: core: Remove the /proc/scsi/${proc_name} directory earlier
ext4: Fix possible corruption when moving a directory
drm/msm/a5xx: fix setting of the CP_PREEMPT_ENABLE_LOCAL register
nfc: fdp: add null check of devm_kmalloc_array in
fdp_nci_i2c_read_device_properties
ila: do not generate empty messages in ila_xlat_nl_cmd_get_mapping()
selftests: nft_nat: ensuring the listening side is up before starting the client
net: usb: lan78xx: Remove lots of set but unused 'ret' variables
net: lan78xx: fix accessing the LAN7800's internal phy specific registers from
the MAC driver
net: caif: Fix use-after-free in cfusbl_device_notify()
bnxt_en: Avoid order-5 memory allocation for TPA data
netfilter: tproxy: fix deadlock due to missing BH disable
btf: fix resolving BTF_KIND_VAR after ARRAY, STRUCT, UNION, PTR
scsi: megaraid_sas: Update max supported LD IDs to 240
net/smc: fix fallback failed while sendmsg with fastopen
riscv: Use READ_ONCE_NOCHECK in imprecise unwinding stack mode
ext4: Fix deadlock during directory rename
MIPS: Fix a compilation issue
alpha: fix R_ALPHA_LITERAL reloc for large modules
macintosh: windfarm: Use unsigned type for 1-bit bitfields
PCI: Add SolidRun vendor ID
media: ov5640: Fix analogue gain control
ipmi/watchdog: replace atomic_add() and atomic_sub()
ipmi:watchdog: Set panic count to proper value on a panic
drm/i915: Don't use BAR mappings for ring buffers with LLC
x86, vmlinux.lds: Add RUNTIME_DISCARD_EXIT to generic DISCARDS
arch: fix broken BuildID for arm64 and riscv
powerpc/vmlinux.lds: Define RUNTIME_DISCARD_EXIT
powerpc/vmlinux.lds: Don't discard .rela* for relocatable builds
s390: define RUNTIME_DISCARD_EXIT to fix link error with GNU ld < 2.36
sh: define RUNTIME_DISCARD_EXIT
UML: define RUNTIME_DISCARD_EXIT
s390/dasd: add missing discipline function
Linux 5.4.237
UBUNTU: Upstream stable to v5.4.237
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Focal)
Importance: Undecided
Assignee: Luke Nowakowski-Krijger (lukenow)
Status: Confirmed
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Summary changed:
- Focal update: upstream stable patchset 2023-06-09
+ Focal update: v5.4.237 upstream stable release
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Focal)
Status: New => Confirmed
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-
[Kernel-packages] [Bug 1685291] Re: RFC: virtio and virtio-scsi should be built in
This bug is awaiting verification that the linux- nvidia-6.2/6.2.0-1003.3~22.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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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-nvidia-6.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/1685291 Title: RFC: virtio and virtio-scsi should be built in Status in linux package in Ubuntu: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: Hi, I was trying to verify bug 1677376 yesterday, and came to find out that our kernel does not have virtio or virtio-scsi builtin drivers. This generally has not been a problem as initramfs has been used. However, as there is recently an interest in booting without initramfs it would seem to make sense to have popular drivers builtin to -generic to allow that. Also, from a priority perspective, if we're going to have any block devices builtin to the -generic kernel, then i'd think that virtio and virtio-scsi would make more sense than an IDE driver. I understand there are tradeoffs involved. Related bugs: * bug 1677376: growing partitions does not work when booted without initramfs ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: User Name 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 19 20:07 seq crw-rw 1 root audio 116, 33 Apr 19 20:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Thu Apr 20 19:37:23 2017 Ec2AMI: ami-0019 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.1-1ubuntu1~cloud0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-zesty dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.1-1ubuntu1~cloud0:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr15.0.2:cvnQEMU:ct1:cvrpc-i440fx-zesty: dmi.product.name: OpenStack Nova dmi.product.version: 15.0.2 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685291/+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 2001599] Re: Lost display on built-in monitor after suspend
This bug is awaiting verification that the linux- nvidia-6.2/6.2.0-1003.3~22.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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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-nvidia-6.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2001599 Title: Lost display on built-in monitor after suspend Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] On some laptops, the eDP blinking slowly after resuming from S3 [Fix] The series of patches which were in drp-tip fix the isue https://patchwork.freedesktop.org/series/110693/ In v6.3-rc1 4c0eb35fc103 drm/i915: Improve PPS debugs ed5509d1d451 drm/i915: Fix whitespace 1e47e035bb73 drm/i915: Print the PPS registers using consistent format ba21bb24810f drm/i915: Reject unusable power sequencers d83804f22d85 drm/i915: Extend dual PPS handlind for ICP+ bf38bba3e7d6 drm/i915: Try to use the correct power sequencer intiially on bxt/glk 209074fd5a82 drm/i915: Generalize the PPS vlv_pipe_check() stuff 3f9ffce5765d drm/i915: Do panel VBT init early if the VBT declares an explicit panel type f70f8153e364 drm/i915: Introduce intel_panel_init_alloc() [Test] ODM and I confirmed the issue is fixed after the patches have been applied. [Where problems may occur] This series of patches fixes a dedicate issue and change the power sequence for the eDP panel. eDP panel may stay blank if the rules are wrong. Our QA will help us to verify this kind of issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2001599/+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 2002968] Re: Fix flicker display problem on some panels which support PSR2
This bug is awaiting verification that the linux- nvidia-6.2/6.2.0-1003.3~22.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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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-nvidia-6.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2002968 Title: Fix flicker display problem on some panels which support PSR2 Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] On some PSR2 supported panels, which connects to Intel Graphics has flicker symptom. It gets normal after booting the kernel with parameter `i915. enable_psr=0` [Fix] Backport one patch from upstream. https://cgit.freedesktop.org/drm-tip/commit/drivers/gpu/drm/i915/display/intel_psr.c?id=084aab04cc60e5eab32287d0483c33e12c92da87 [Test] Booting the patched kernel with problematic panel (LGD LCD_VD78M), check if the display has abnormal flickering problem on graphics interfaces. [Where problems could occur] The risk of regression is low. It only fixes problem on panels which support PSR2. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002968/+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 2007745] Re: [SRU][Jammy] CONFIG_PCI_MESON is not enabled
This bug is awaiting verification that the linux- nvidia-6.2/6.2.0-1003.3~22.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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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-nvidia-6.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/2007745 Title: [SRU][Jammy] CONFIG_PCI_MESON is not enabled Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: SRU justification: [ Impact ] The PCI driver for the amlogic-based Meson platforms (CONFIG_PCI_MESON) is not enabled as a module in the kernel configuration: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/tree/debian.master/config/config.common.ubuntu?h=master#n7036 [ Test Plan ] Check if pci_meson.ko is compiled and present in the linux-modules package. [ Where problems could occur ] * Enabling the driver could enable undesired dependencies * Kernel module does not compile and breaks the build [ Other Info ] This driver is important for systems like the ODROID HC4, which uses a PCIE-SATA bridge to provide a storage interface. This system is fully supported by the kernel (including a device tree), except for the fact that this PCI driver is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008824] Re: sched: cpumask: improve on cpumask_local_spread() locality
This bug is awaiting verification that the linux- nvidia-6.2/6.2.0-1003.3~22.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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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-nvidia-6.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/2008824 Title: sched: cpumask: improve on cpumask_local_spread() locality Status in linux package in Ubuntu: In Progress Bug description: A patch series landed upstream during the v6.3 merge window that shows impressive performance improvements in iperf3 multi-stream performance on NUMA based systems w/ Mellanox network controllers: https://www.spinics.net/lists/linux-rdma/msg115357.html It would be valuable to land those in lunar, allowing our LTS users to adopt them more quickly starting with the HWE kernel in 22.04.3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008824/+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 2011389] Re: vmd may fail to create sysfs entry while `pci_rescan_bus()` called in some other drivers like wwan
This bug is awaiting verification that the linux- nvidia-6.2/6.2.0-1003.3~22.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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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-nvidia-6.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011389 Title: vmd may fail to create sysfs entry while `pci_rescan_bus()` called in some other drivers like wwan Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] With wwan t7xx driver patched, vmd may fail the probe process because it does not lock properly. [Fix] https://lore.kernel.org/linux- pci/20230313173733.1815277-1-vicamo.y...@canonical.com/T/#u [Test Case] Verify on platforms with FM350 wwan module with prebuilt oem-6.1 or above kernels. No vmd probe error should be found in dmesg. [Where problems could occur] This is the way it should have been done. [Other Info] This is not reproducible with v6.0 or older kernels, so only Lunar and oem-6.1 are nominated for fix. OEM-6.0 patch goes to Gerrit instead. == original bug report == vmd may fail to create sysfs entry while `pci_rescan_bus()` called in some other drivers like wwan. This happens after bug 2002089 re-added pci rescan feature back to wwan t7xx driver to support firmware updates via devlink. t7xx may call `pci_rescan_bus()` with proper locks, but vmd doesn't. sysfs: cannot create duplicate filename '/devices/.../resource0' Call Trace: sysfs_warn_dup.cold+0x17/0x34 sysfs_add_bin_file_mode_ns+0xc0/0xf0 sysfs_create_bin_file+0x6d/0xb0 pci_create_attr+0x117/0x260 pci_create_resource_files+0x6b/0x150 pci_create_sysfs_dev_files+0x18/0x30 pci_bus_add_device+0x30/0x80 pci_bus_add_devices+0x31/0x80 pci_bus_add_devices+0x5b/0x80 vmd_enable_domain.constprop.0+0x6b7/0x880 [vmd] vmd_probe+0x16d/0x193 [vmd] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2011389/+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 2012019] Re: Fix E-star testing failure with RTK 8852BE
This bug is awaiting verification that the linux- nvidia-6.2/6.2.0-1003.3~22.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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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-nvidia-6.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2012019 Title: Fix E-star testing failure with RTK 8852BE Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: New Bug description: [Impact] E-star testing failure on machine with RTK 8852BE configuration. [Fix] 1. Enable CLKREQ to reduce power consumption. 2. release RX standby timer of beamformee to save power [Test Case] 1. Prepare one system with RTK 8852BE WLAN/BT. 2. Run E-star testing. 3. The result must meet PASS criteria. [Where problems could occur] Low, may face the performance issue during throughput verification. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2012019/+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 2015498] Re: Debian autoreconstruct Fix restoration of execute permissions
This bug is awaiting verification that the linux- nvidia-6.2/6.2.0-1003.3~22.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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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-nvidia-6.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/2015498 Title: Debian autoreconstruct Fix restoration of execute permissions Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Confirmed Bug description: SRU justification [Impact] Debian source package diffs cannot represent that a file should be executable. gen-auto-reconstruct detects when a commit adds a script that is supposed to be invoked during the build and restores the execute permissions in the reconstruct script by adding `chmod +x $file`. But, if a file removes its execute permission, this will change it back. This happened in the last jammy release (version 5.15.0-70.77) where a commit from upstream removed the execute permission for a header file but then our scripts brought it back. [Fix] Andy proposed the following fix https://dpaste.com/6SJ8YR3BM Basically it checks if the permission was added or removed and uses either +x or -x. [Test plan] Easily tested with jammy-kvm, latest release where a rebase picked this commit "treewide: fix up files incorrectly marked executable" where `drivers/gpu/drm/vmwgfx/vmwgfx_msg_arm64.h` changed its permission from 755 to 644 (removed execute). When debian packages are prepared, you'll notice the file has changed its permission back to 755. With the fix, it should be the same. [Regression potential] Low, it is a small fix. Scripts will still have execute permission. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015498/+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 2015867] Re: Kernel 6.1 bumped the disk consumption on default images by 15%
This bug is awaiting verification that the linux- nvidia-6.2/6.2.0-1003.3~22.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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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-nvidia-6.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/2015867 Title: Kernel 6.1 bumped the disk consumption on default images by 15% Status in linux package in Ubuntu: Confirmed Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Confirmed Bug description: [Impact] After enabling Rust support in the kernel we noticed an increased size in linux-headers, because all the Rust libraries required to build out-of-tree kernel modules are now included in linux-headers directly. The increased size goes from ~30MB to ~100MB. This extra size is not worth it, considering the small amount of users that are going to experiment Rust in the kernel at the moment. [Test case] Install linux-headers and check the size of /usr/src/linux- headers-`uname -r`. [Fix] Some work has already done to reduce the size of linux-headers by dropping some binary artifacts (*.o and *.cmd) that are not required to build out-of-tree kernel modules. Ideally it'd be nicer to provide a separate package (called for example linux-lib-rust-`uname -r`) to ship the Rust-specific dependencies (libraries / headers). In this way linux-headers would be restored back to the original size, those that want to experiment Rust in the kernel can simply install linux-lib-rust and we can prevent wasting space in the cloud images. [Regression potential] Introducing a new package in the kernel may break something in our kernel promotion workflow, so with this change applied we need to pay a little more attention when the kernel is going to be promoted to release/updates. [Original bug report] Hi, in the regular monitoring of metrics there was a bump in disk size last week. The default image once installed consumes now 994 (formerly 859) megabytes. Looking at the consumers there was much noise, but the biggest change was linux-headers-5.19.0-1008-kvm 25197 -> linux-headers-6.2.0-1002-kvm 108072 linux-modules-5.19.0-1008-kvm 76090 -> linux-modules-6.2.0-1002-kvm 97221 I haven't looked deeper yet. Is that an accident and will be fixed soon, is that a change we can do nothing about, anything in between? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015867/+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 2015972] Re: Dell: Enable speaker mute hotkey LED indicator
This bug is awaiting verification that the linux- nvidia-6.2/6.2.0-1003.3~22.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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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 removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-nvidia-6.2 verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2015972 Title: Dell: Enable speaker mute hotkey LED indicator Status in HWE Next: New Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in alsa-ucm-conf source package in Jammy: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Released Status in alsa-ucm-conf source package in Kinetic: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-6.1 source package in Kinetic: Invalid Status in alsa-ucm-conf source package in Lunar: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Feature Description] When users press the speaker mute hotkey and the speaker is muted, the speaker mute LED indicator will light up. When the speaker is not muted, the speaker mute LED indicator will light out. [Test Case] 1. run G16 with target kernel. 2. press the mute hotkey 3. check if speaker mute led can be switched. [Where problems could occur] Low, just register a speaker mute led control for dell-laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2015972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016186] Re: 5.19 not reporting cgroups v1 blkio.throttle.io_serviced
This bug is awaiting verification that the linux-
nvidia-6.2/6.2.0-1003.3~22.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-jammy' to
'verification-done-jammy'. If the problem still exists, change the tag
'verification-needed-jammy' to 'verification-failed-jammy'.
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-nvidia-6.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/2016186
Title:
5.19 not reporting cgroups v1 blkio.throttle.io_serviced
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Kinetic:
Fix Committed
Status in linux source package in Lunar:
Fix Committed
Status in linux source package in Mantic:
Incomplete
Bug description:
[Impact]
Commit f382fb0bcef4 ("block: remove legacy IO schedulers") introduced
a behavior change in the blkio throttle cgroup subsystem: IO
statistics are not reported anymore unless a throttling rule is
explicitly defined, because the current code only counts bios that are
actually throttled.
This behavior change is potentially breaking some user-space
applications that are relying on the old behavior (see original bug
report below).
[Test case]
- mount cgroup v1
- create a blkio cgroup
- move a task into the blkio cgroup
- perform some I/O (i.e., dd)
- read the IO stats for the cgroup (blkio.throttle.io_serviced and
blkio.throttle.io_service_bytes in cgroupfs)
- IO stats are all 0, unless a throttle rule is defined
Previous behavior (kernel 5.15) was showing I/O statistics even
without throttling rules defined.
[Fix]
Apply / backport this fix:
https://lore.kernel.org/lkml/20230507170631.89607-1-hanjinke@bytedance.com/t/
[Regression potential]
The fix is affecting the block IO cgroup subsystem, we may see
potential regressions in this particular cgroup subsystem with this
fix applied.
[Original bug report]
Hi,
I'm still investigating but, am a bit stuck. Here's what I've found so
far.
Today I've upgraded some nodes in AWS EC2 from the previous v5.15
linux-aws package to the recently pusblished v5.19 package and
rebooted. It seems that even when there's disk activity, the files:
/sys/fs/cgroup/blkio/blkio.throttle.io_serviced
/sys/fs/cgroup/blkio/blkio.throttle.io_service_bytes
Are only ever populated with 0's. Prior on v5.15 these would reflect
the actual disk usage. No other system configuration changes were
applied just the kernel upgrade and reboot. I've also verified that
simply rebooting a v5.15 where this does work doesn't break the
reporting. These EC2 instances are running with cgroups v1 due to
other compatability issues and I suspect that might be the issue. So
far, I cannot find any differences. mtab shows the same v1 mount
setup, the kernel options match betwen v5.15 and v5.19.
I'm more than happy to fetch whatever info would help out here. I'd
love to get 5.19 working for us but, we really need the data from
these files.
Info:
Prior version that works: Linux ip-10-128-168-154 5.15.0-1031-aws #35-Ubuntu
SMP Fri Feb 10 02:07:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Upgraded version that's broken: Linux ip-10-128-166-219 5.19.0-1022-aws
#23~22.04.1-Ubuntu SMP Fri Mar 17 15:38:24 UTC 2023 x86_64 x86_64 x86_64
GNU/Linux
EC2 instances built off of the published 22.04 LTS AMI in us-east-1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016186/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)
This bug is awaiting verification that the linux-
nvidia-6.2/6.2.0-1003.3~22.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-jammy' to
'verification-done-jammy'. If the problem still exists, change the tag
'verification-needed-jammy' to 'verification-failed-jammy'.
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-nvidia-6.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/2016908
Title:
udev fails to make prctl() syscall with apparmor=0 (as used by maas by
default)
Status in AppArmor:
New
Status in MAAS:
Fix Committed
Status in maas-images:
Invalid
Status in apparmor package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Fix Committed
Status in systemd package in Ubuntu:
Invalid
Status in apparmor source package in Lunar:
Confirmed
Status in linux source package in Lunar:
Fix Committed
Status in systemd source package in Lunar:
Invalid
Bug description:
I'm assuming the image being used for these deploys is 20230417 or
20230417.1 based on the fact that I saw a 6.2 kernel being used which
I don't believe was part of the 20230319 serial. I don't have access
to the maas server, so I can't directly check any log files.
MAAS Version: 3.3.2
Here's where the serial log indicates it can't download the squashfs. The
full log is attached as scobee-lunar-no-squashfs.log (there are some other
console message intermixed):
no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf
/run/net6
-*.conf
::
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
date/squa[ 206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes,
fsverity
=yes
shfs
:: mount_squash downloading
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
4/lunar/candidate/squashfs to /root.tmp.img
Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
wget: can't connect to remote host (10.229.32.21): Network is unreachable
:: mount -t squashfs -o loop '/root.tmp.img' '/root.tmp'
mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
done.
Still gathering logs and info and will update as I go.
Kernel Bug / Apparmor
reproducer
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
$ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'
#start the VM
Starting systemd-udevd version 252.5-2ubuntu3
Spawning shell within the initramfs
BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) udevadm info --export-db
Failed to set death signal: Invalid argument
Observe that udevadm fails to setup death signal, with in systemd code
is this
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
util.c#L1252
if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ?
SIGINT : SIGTERM) < 0) {
log_full_errno(prio, errno, "Failed to set death
signal: %m");
_exit(EXIT_FAILURE);
}
workaround set kernel commandline to `apparmor=1`
MAAS bug
Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor.
Even for deployment and commisioning.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2016908/+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 2017444] Re: Computer with Intel Atom CPU will not boot with Kernel 6.2.0-20
This bug is awaiting verification that the linux-
nvidia-6.2/6.2.0-1003.3~22.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-jammy' to
'verification-done-jammy'. If the problem still exists, change the tag
'verification-needed-jammy' to 'verification-failed-jammy'.
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-nvidia-6.2
--
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/2017444
Title:
Computer with Intel Atom CPU will not boot with Kernel 6.2.0-20
Status in linux package in Ubuntu:
Confirmed
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux source package in Lunar:
Fix Committed
Status in linux-firmware source package in Lunar:
Invalid
Bug description:
== SRU Justification ==
[Impact]
Some Atom based system cannot boot on kernel 6.2 because of atomisp
driver.
[Fix]
Disable the driver via config, suggested by the driver dev.
[Test]
Users confirmed disabling the config works.
[Where problems could occur]
The ISP camera dever worked on Linux. So disabling it shouldn't
introduce any surprise.
== Original Bug Report ==
Computers with Intel Atom CPU will not boot with Kernel 6.2.0-20 OR any other
Kernel in 6.2 series or Kernel 6.3.0.
This bug affects all Intel Atom CPU computers in all Linux
distributions making impossible to install or boot to OS with kernel
6.2 or higher.
The bug is caused by Intel atomisp camera driver module which has
firmware missing: shisp_2401a_v21.bin. Missing firmware causes a
watchdog bug notice and Soft Lockup of boot sequence.
NEW SOLUTION AND NOTICE TO UBUNTU KERNEL MAINTAINERS, April 29th:
The following persons are in charge of atomisp kernel development:
Hans de Goede (maintainer:STAGING - ATOMISP DRIVER)
Mauro Carvalho Chehab (maintainer:STAGING - ATOMISP
DRIVER)
Sakari Ailus (reviewer:STAGING - ATOMISP
DRIVER)
Greg Kroah-Hartman (supporter:STAGING SUBSYSTEM)
linux-me...@vger.kernel.org (open list:STAGING - ATOMISP DRIVER)
linux-stag...@lists.linux.dev (open list:STAGING SUBSYSTEM)
linux-ker...@vger.kernel.org (open list)
April 29th Hans de Goede adviced me personally(
https://github.com/linux-surface/linux-surface/issues/1095 ), that
atomisp driver is still in development and should be disabled. By
disabling driver he meant disabling atomisp modules in kernel.
OLD SOLUTION FOR THIS BUG:
Copying (installing) firmware shisp_2401a0_v21.bin from:
https://github.com/intel-aero/meta-intel-aero-
base/blob/master/recipes-kernel/linux/linux-yocto/shisp_2401a0_v21.bin
to /lib/firmware will solve the bug (partially - it still gives error
messages - but at least the computer boots).**
(dmesg.log with shisp-file with kernel 6.2.0-06 and 6.3.0-06 as
attachments 9. and 10.)
(Another solution - which Manjaro kernel maintainer did - was to
disable atomisp and related modules).
Afterwards Intel Atom CPU computer will be able to boot with kernel
6.2.
DMESG.LOG OF KUBUNTU 23.04 LIVE USB AND MORE INFORMATION IN:
https://askubuntu.com/questions/1464926/not-able-to-boot-
kubuntu-23-04-with-kernel-6-2-and-intel-atom-cpu
The last stable Ubuntu Kernel Intel Atom CPU computer will boot with
is 6.1.25.
This bug was already in 5.19, as you can see from dmesg.logs. It
appears that atomisp failes to launch in both 5.19.0-40 and 6.1.25 but
still the computer boots.
This bug is also reported in Manjaro ( " https://github.com/linux-
surface/linux-surface/issues/1095 ")and Arch Linux ("
https://bbs.archlinux.org/viewtopic.php?id=283920 ") so it is not
limited to Ubuntu Kernels.
This bug has already been reported for Ubuntu 23.04 Beta in Ubuntu
bugtracking system (" https://www.mail-archive.com/kernel-
packa...@lists.launchpad.net/msg501664.html ") with Bug number
#2015794.
Attachments:
1. Picture of stuck boot sequence of HP x2 210 G2 with Intel Atom CPU trying
to boot in to Kubuntu 23.04 with Kernel 6.2.0-20.
2. dmesg.log of the computer with Ubuntu Kernel 6.1.25.
3. xsession-errors of the computer with Ubuntu Kernel 6.1.25.
4. dmesg.log of the computer with Ubuntu Kernel 5.19.0-40.
5. Video of boot sequence with Kernel 6.2.0-20.
6. uname-a.log of Kernel 6.1.25.
7. lspci-vvnn.log of Kernel 6.1.25.
8. version.log of Kernel 5.19.0-40.
9. dmesg.log with shisp-file with ubuntu kernel 6.2.0-06.**
10. dmesg.log with shisp-file with ubuntu kernel 6.3.0-06**
P.S. The apport-collect data is from Kernel 5.19.0-40.
P.S.P.S I had
[Kernel-packages] [Bug 2017903] Re: LSM stacking and AppArmor for 6.2: additional fixes
This bug is awaiting verification that the linux- nvidia-6.2/6.2.0-1003.3~22.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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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-nvidia-6.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/2017903 Title: LSM stacking and AppArmor for 6.2: additional fixes Status in linux package in Ubuntu: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: [Impact] We maintain custom LSM stacking and AppArmor SAUCE patches in our kernel to provide additional features that are not available in the upstream AppArmor. We have experienced occasional bugs in the lunar kernel (specifically with the environ.sh test) that can lead to system crashes / failures (such as potential NULL pointer dereference). [Test case] Run AppArmor autopkgtest / qa-regression-testing. [Fix] Apply the following additional fixes provided by AppArmor upstream maintainer: UBUNTU: SAUCE: apparmor: fix policy_compat perms remap for file dfa UBUNTU: SAUCE: apparmor: fix profile verification and enable it UBUNTU: SAUCE: apparmor: fix: add missing failure check in compute_xmatch_perms UBUNTU: SAUCE: apparmor: fix: kzalloc perms tables for shared dfas [Regression potential] Additional fixes are touching only AppArmor specific code, so we may experience regressions (bugs / behavior change) only in apparmor by applying them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017903/+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 2018655] Re: Update I915 PSR calculation on Linux 6.2
This bug is awaiting verification that the linux- nvidia-6.2/6.2.0-1003.3~22.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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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-nvidia-6.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/2018655 Title: Update I915 PSR calculation on Linux 6.2 Status in linux package in Ubuntu: Incomplete Status in linux source package in Lunar: Fix Committed Bug description: [Impact] PSR flickering on SHP 5457 was workarounded by a quirk. Use proper fix from upstream instead. [Fix] Update AUX sync pulse to follow eDP spec. [Test] Use naked eye to ensure the issue is not observed when the fix gets applied. [Where problems could occur] The fix relax the parameter to make eDP work. Though unlikely, DP on i915 might break. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018655/+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 2021605] Re: introduce do_lib_rust=true|false to enable/disable linux-lib-rust package
This bug is awaiting verification that the linux- nvidia-6.2/6.2.0-1003.3~22.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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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-nvidia-6.2 verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2021605 Title: introduce do_lib_rust=true|false to enable/disable linux-lib-rust package Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux source package in Lunar: Incomplete Status in linux-aws source package in Lunar: Fix Committed Status in linux source package in Mantic: Incomplete Status in linux-aws source package in Mantic: New Bug description: [Impact] Provide a variable do_lib_rust=true|false in the kernel build system to selectively enable the Rust packaging (linux-lib-rust) with specific kernels and specific architectures. Right now Rust should be enabled only in lunar and mantic and only on amd64. [Test case] Build the kernel producing all the debs. [Fix] Introduce a do_lib_rust=true variable that will be defined only in debian.master/rules.d/amd64.mk for now. [Regression potential] Kernels may need to set this variables if they want to enable the Rust support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021605/+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 2022001] Re: Kernel 5.19.0-42 onward crashes with VMSVGA + 3D acceleration
Upon further investigation, this is an issue that the package "xserver- xorg-video-vmware" causes to start happening, as on a perfectly fine working Kubuntu 22.04 installing that package only, and restarting, causes the issue to be immediately reproducible, versus non-reproducible without that package being installed. ** Also affects: xserver-xorg-video-vmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2022001 Title: Kernel 5.19.0-42 onward crashes with VMSVGA + 3D acceleration Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-vmware package in Ubuntu: New Bug description: KDE Neon 5.27 (Ubuntu 22.04 Jammy) Kernel: linux-image-5.19.0-43-generic Steps to reproduce: 0. Install KDE Neon into Virtualbox 1. Install kernel version 5.19.0-42 or -43 (-generic) 2. Boot the system 3. Log in to KDE desktop 4. Try and open a window or right-click on the desktop Expected outcome: A window opens, or a desktop context menu opens Actual outcome: - opening a window: X server crashes. Logging in again and opening a window: system crash - opening a desktop context menu: desktop crashes, after that system freezes Additional info: - dmesg shows a kernel crash trace - kernel 5.19.0-38-generic works OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022001/+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 2022001] Re: Kernel 5.19.0-42 onward crashes with VMSVGA + 3D acceleration
A friend of mine also just reproduced the same issue just now on Kubuntu 22.04.2 LTS (a fresh Ubuntu 22.04.2 installation with kubuntu-desktop installed onto it, more-so) using VMWare 16. -- 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/2022001 Title: Kernel 5.19.0-42 onward crashes with VMSVGA + 3D acceleration Status in linux package in Ubuntu: Confirmed Bug description: KDE Neon 5.27 (Ubuntu 22.04 Jammy) Kernel: linux-image-5.19.0-43-generic Steps to reproduce: 0. Install KDE Neon into Virtualbox 1. Install kernel version 5.19.0-42 or -43 (-generic) 2. Boot the system 3. Log in to KDE desktop 4. Try and open a window or right-click on the desktop Expected outcome: A window opens, or a desktop context menu opens Actual outcome: - opening a window: X server crashes. Logging in again and opening a window: system crash - opening a desktop context menu: desktop crashes, after that system freezes Additional info: - dmesg shows a kernel crash trace - kernel 5.19.0-38-generic works OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022001/+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 2022001] Re: Kernel 5.19.0-42 onward crashes with VMSVGA + 3D acceleration
Can reproduce the exact same issue on Feren OS 2023.07 Alpha 2, with the exact same kernel version causing the issue and the exact same last working kernel version as the OP states. For Feren OS, it triggers upon a window spawning in KDE Plasma. -- 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/2022001 Title: Kernel 5.19.0-42 onward crashes with VMSVGA + 3D acceleration Status in linux package in Ubuntu: Confirmed Bug description: KDE Neon 5.27 (Ubuntu 22.04 Jammy) Kernel: linux-image-5.19.0-43-generic Steps to reproduce: 0. Install KDE Neon into Virtualbox 1. Install kernel version 5.19.0-42 or -43 (-generic) 2. Boot the system 3. Log in to KDE desktop 4. Try and open a window or right-click on the desktop Expected outcome: A window opens, or a desktop context menu opens Actual outcome: - opening a window: X server crashes. Logging in again and opening a window: system crash - opening a desktop context menu: desktop crashes, after that system freezes Additional info: - dmesg shows a kernel crash trace - kernel 5.19.0-38-generic works OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020413] Re: fix typo in config-checks invocation
** Changed in: linux-kvm (Ubuntu Jammy) Status: Confirmed => Fix Committed ** Changed in: linux-kvm (Ubuntu) Status: New => Fix Committed ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2020413 Title: fix typo in config-checks invocation Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: Fix Committed Status in linux source package in Jammy: Incomplete Status in linux-kvm source package in Jammy: Fix Committed Bug description: [Impact] After migrating to the new annotations-only model in jammy we introduced a typo in debian/rules.d/4-checks.mk, that is triggered if we opt to not migrate to the new model and still use the old configs+annotations. [Test case] With debian./config/config.common.ubuntu present run the following command: $ fakeroot debian/rules clean updateconfigs [Fix] Replace @perl -> perl. [Regression potential] It's a trivial typo fix. Regressions can be introduced only if we are still using the old configs+annotations model. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020413/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019203] Re: mysql 8.0.33 binary crashes on startup on armhf
> I filed a bug about this with the MySQL project back in April. They closed it as 'not a bug'. > https://bugs.mysql.com/bug.php?id=110752=2=67 FWIW we got MySQL to at least acknowledge/verify the issue. So they may end up fixing this themselves. -- 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/2019203 Title: mysql 8.0.33 binary crashes on startup on armhf Status in MySQL Server: Unknown Status in glibc package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in mysql-8.0 package in Ubuntu: Fix Released Status in glibc source package in Focal: Invalid Status in linux source package in Focal: Incomplete Status in mysql-8.0 source package in Focal: Fix Released Status in glibc source package in Jammy: Invalid Status in linux source package in Jammy: Incomplete Status in mysql-8.0 source package in Jammy: Fix Released Status in glibc source package in Kinetic: Invalid Status in linux source package in Kinetic: Incomplete Status in mysql-8.0 source package in Kinetic: Fix Released Status in glibc source package in Lunar: Invalid Status in linux source package in Lunar: Incomplete Status in mysql-8.0 source package in Lunar: Fix Released Status in glibc source package in Mantic: Invalid Status in linux source package in Mantic: Incomplete Status in mysql-8.0 source package in Mantic: Fix Released Bug description: From mantic autopkgtests: Setting up mysql-server-8.0 (8.0.33-0ubuntu2) ... update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf (my.cnf) in auto mode Renaming removed key_buffer and myisam-recover options (if present) ERROR: Unable to start MySQL server: 2023-05-09T17:23:22Z UTC - mysqld got signal 11 ; Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware. BuildID[sha1]=facf2109b23102b169b11737a1fc4bd99de4be1b Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x10 /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x2b) [0x205e0bc] /usr/sbin/mysqld(print_fatal_signal(int)+0x29d) [0x1533ba2] /usr/sbin/mysqld(handle_fatal_signal+0x71) [0x1533c9e] /lib/arm-linux-gnueabihf/libc.so.6(+0x2d750) [0xf6e7b750] /usr/sbin/mysqld(memory::Aligned_atomic::Aligned_atomic()+0x51) [0x1e0d49a] /usr/sbin/mysqld(Delegate::Delegate(unsigned int)+0x3b) [0x1e0d6c4] /usr/sbin/mysqld(delegates_init()+0x37) [0x1e0d804] /usr/sbin/mysqld(+0x8ec92c) [0x139592c] /usr/sbin/mysqld(mysqld_main(int, char**)+0x1959) [0x139a22a] /lib/arm-linux-gnueabihf/libc.so.6(+0x1d7da) [0xf6e6b7da] /lib/arm-linux-gnueabihf/libc.so.6(__libc_start_main+0x5d) [0xf6e6b87e] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. Please take a look at https://wiki.debian.org/Teams/MySQL/FAQ for tips on fixing common upgrade issues. Once the problem is resolved, run apt-get --fix-broken install to retry. dpkg: error processing package mysql-server-8.0 (--configure): installed mysql-server-8.0 package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/2019203/+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 2023075] Re: pc switching off while am busy and keyboard and mouse stack
Thank you for using Ubuntu and taking the time to report a bug. Your report should contain, at a minimum, the following information so we can better find the source of the bug and work to resolve it. Submitting the bug about the proper source package is essential. For help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally, in the report please include: 1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> About Ubuntu. 2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by checking in Synaptic. 3) What happened and what you expected to happen. The Ubuntu community has also created debugging procedures for a wide variety of packages at https://wiki.ubuntu.com/DebuggingProcedures . Following the debugging instructions for the affected package will make your bug report much more complete. Thanks! ** Information type changed from Private Security to Public ** 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/2023075 Title: pc switching off while am busy and keyboard and mouse stack Status in linux package in Ubuntu: Invalid Bug description: pc switching off while am busy and keyboard and mouse stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023075/+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 2022981] Re: Frequent hard reboots on RaptorLake
Interesting, maybe something is triggering a controlled shutdown for some reason then? For context, here's what I'm seeing: https://drive.google.com/file/d/1OlPV7akUgekD9-rl1gsMes_zhO68aius/view?usp=sharing My gnome shell is now crashing while trying to upload the crash file for the gnome crash, and I'm not seeing the same timestamps as my reboots for anything on https://errors.ubuntu.com/user/ID. However, there are some issues related to kdeconnect, apport, and gnome-shell that could be relevant, so here are the links to those: https://errors.ubuntu.com/oops/156e3de2-06ed-11ee-a27e-fa163e993415 https://errors.ubuntu.com/oops/127fe0f8-06ed-11ee-b088-fa163e55efd0 https://errors.ubuntu.com/oops/43df2b8e-063c-11ee-bccf-fa163ef35206 https://errors.ubuntu.com/oops/18bb3ea2-0623-11ee-b07b-fa163e55efd0 You said to file as a separate bug in a previous comment, so would you prefer to close this one out and have me add those links to a new bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2022981 Title: Frequent hard reboots on RaptorLake Status in linux-hwe-5.19 package in Ubuntu: Incomplete Bug description: I can repro in multiple ways: 1. Unplug my HDMI monitor. This is pretty much a guaranteed reboot. 2. Using hardware accelerated Chromium, switching between google profiles seems to trigger a crash and full reboot pretty often. These could be two separate bugs. I'm not sure I'd be unlucky enough to have two full reboot bugs at the same time though. Happy to help with more debugging Release: Jammy Chromium version: 115.0.5762.4-hwacc snap refresh --channel=latest/edge/hwacc chromium What you expected to happen 1. HDMI monitor disconnects, and no reboots happen. 2. I can switch Chromium profiles without a reboot What happened instead Both actions cause a reboot ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 6 16:09:12 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms/23.01.00, 5.19.0-41-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms/23.01.00, 5.19.0-43-generic, x86_64: installed (WARNING! Diff between built and installed module!) tp_smapi/0.43, 5.19.0-41-generic, x86_64: installed tp_smapi/0.43, 5.19.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:a7a0] (rev 04) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:5630] NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:25a2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:] InstallationDate: Installed on 2023-04-20 (46 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: System76 Gazelle ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_90m3zy@/vmlinuz-5.19.0-43-generic root=ZFS=rpool/ROOT/ubuntu_90m3zy ro drm.debug=0xe quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2023 dmi.bios.release: 4.19 dmi.bios.vendor: coreboot dmi.bios.version: 2023-03-22_799ed79 dmi.board.name: Gazelle dmi.board.vendor: System76 dmi.board.version: gaze18 dmi.chassis.type: 9 dmi.chassis.vendor: System76 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr2023-03-22_799ed79:bd03/22/2023:br4.19:efr0.0:svnSystem76:pnGazelle:pvrgaze18:rvnSystem76:rnGazelle:rvrgaze18:cvnSystem76:ct9:cvr:sku: dmi.product.name: Gazelle dmi.product.version: gaze18 dmi.sys.vendor: System76 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati:
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/6.2.0.1006.6)
All autopkgtests for the newly accepted linux-meta-kvm (6.2.0.1006.6) for lunar have finished running. The following regressions have been reported in tests triggered by the package: dahdi-linux/1:2.11.1.0.20170917~dfsg-8.4ubuntu1 (amd64) lttng-modules/2.13.8-1 (amd64) oss4/4.2-build2020-1ubuntu1 (amd64) sl-modem/2.9.11~20110321-16ubuntu4 (amd64) xtrx-dkms/0.0.1+git20190320.5ae3a3e-3.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/lunar/update_excuses.html#linux-meta-kvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023396] Re: After an Ubuntu Update, the WiFi was not working. When running the sudo lshw -C network in a terminal window, the statement '*-network UNCLAIMED ' was presented for
Hi Jon we recently identified regressions in our kernels that breaks WiFi, which very well could be what you are experiencing here. We should have a new Jammy-hwe kernel 5.19.0-45.46~22.04.1 in ~proposed on Monday which should fix this issue. - Luke -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2023396 Title: After an Ubuntu Update, the WiFi was not working. When running the sudo lshw -C network in a terminal window, the statement '*-network UNCLAIMED ' was presented for the network controller (Broadcom BCM43142 802.11b/g/n) Status in linux-firmware package in Ubuntu: New Bug description: The Ubuntu Release information shown after running 'lsb_release -a' No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.2 LTS Release: 22.04 Codename: jammy The printout from the terminal window after running lshw -C network *-network UNCLAIMED description: Network controller product: BCM43142 802.11b/g/n vendor: Broadcom Inc. and subsidiaries physical id: 0 bus info: pci@:06:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress cap_list configuration: latency=0 resources: memory:aa10-aa107fff *-network description: Ethernet interface product: RTL810xE PCI Express Fast Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:07:00.0 logical name: enp7s0 version: 07 serial: 20:47:47:49:34:06 capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=5.19.0-44-generic firmware=rtl8106e-1_0.0.1 06/29/12 latency=0 link=no multicast=yes port=twisted pair resources: irq:19 ioport:3000(size=256) memory:aa00-aa000fff memory:c000-c0003fff ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.14 ProcVersionSignature: Ubuntu 5.19.0-44.45~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jon2489 F pulseaudio /dev/snd/controlC0: jon2489 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 9 06:55:51 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-23 (289 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Dell Inc. Inspiron 3543 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-44-generic root=UUID=ac729c56-ab63-4579-9c28-60763aa3e9f3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-44-generic N/A linux-backports-modules-5.19.0-44-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.14 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/12/2019 dmi.bios.release: 65.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0M9V4C dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA11:bd09/12/2019:br65.11:svnDellInc.:pnInspiron3543:pvrA11:rvnDellInc.:rn0M9V4C:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:sku0654: dmi.product.name: Inspiron 3543 dmi.product.sku: 0654 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2023396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021830] Re: GVE: Performance improvement for "jumbo" frames
** Tags removed: verification-needed-kinetic
** Tags added: verification-done-kinetic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2021830
Title:
GVE: Performance improvement for "jumbo" frames
Status in linux-gcp package in Ubuntu:
New
Status in linux-gcp source package in Kinetic:
Fix Committed
Bug description:
This patch
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=82fd151d38d9fda714c5bb2e9e79ecd6bdc72da6
is a performance improvement fix for handling 9k frames on gvnic and
is being requested by GCP for the 5.19 kernel.
Testing:
- Boot tested with gvnic, tested basic networking functionality
Regression potential:
- Small regression potential - impact limited to the gvnic driver ("gve")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2021830/+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 2017846] Re: System kept waking up after pressing power button
I do see the behavior you are describing in those logs: Apr 27 00:34:53 Y4M1-II systemd-logind[2855]: Power key pressed short. Apr 27 00:34:53 Y4M1-II systemd-logind[2855]: The system will suspend now! Apr 27 00:35:10 Y4M1-II systemd-logind[2855]: Operation 'sleep' finished. Apr 27 00:35:45 Y4M1-II systemd-logind[2855]: Power key pressed short. Apr 27 00:35:45 Y4M1-II systemd-logind[2855]: The system will suspend now! Apr 27 00:36:02 Y4M1-II systemd-logind[2855]: Operation 'sleep' finished. Apr 27 00:40:00 Y4M1-II systemd-logind[2855]: Power key pressed short. Apr 27 00:40:00 Y4M1-II systemd-logind[2855]: The system will suspend now! Apr 27 00:40:17 Y4M1-II systemd-logind[2855]: Operation 'sleep' finished. Apr 27 00:50:15 Y4M1-II systemd-logind[2855]: The system will power off now! Apr 27 00:50:15 Y4M1-II systemd-logind[2855]: System is powering down. Each gap is 17 seconds, which is interesting I guess. If you are using suspend-then-hibernate (/etc/systemd/sleep.conf) and your battery is low, the system might be waking up from suspend to then hibernate (it does not look like you are on batter power though). Otherwise there might be a timer unit installed with WakeSystem=true that happens to be firing when you suspend. Besides that I don't think systemd would do anything else to wake the system (I don't see any other relevant uses of CLOCK_BOOTTIME_ALARM). If you want to investigate systemd involvement further, than you can enable debug logs for systemd- logind and attach updated logs if this issue occurs again. $ cat > /etc/systemd/system/systemd-logind.service.d/debug-logs.conf << EOF [Service] Environment=SYSTEMD_LOG_LEVEL=debug EOF Probably best to reboot for that to take effect. -- 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/2017846 Title: System kept waking up after pressing power button Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Bug description: Tried it 3 times in the last 15min, each time it keeps waking back up. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yamiyuki 42974 F wireplumber /dev/snd/controlC3: yamiyuki 42974 F wireplumber /dev/snd/controlC0: yamiyuki 42974 F wireplumber /dev/snd/seq:yamiyuki 42972 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 27 00:45:37 2023 InstallationDate: Installed on 2022-01-14 (468 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic 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.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-01 (25 days ago) dmi.bios.date: 02/08/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F5a dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu
[Kernel-packages] [Bug 2019240] Re: Pull-request to address a number of enablement issues for Orin platforms
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2019240 Title: Pull-request to address a number of enablement issues for Orin platforms Status in linux-nvidia-tegra package in Ubuntu: New Bug description: [impact] This patch set addresses a wide variety of bugs and missing features for NVIDIA Orin platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2019240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023396] Re: After an Ubuntu Update, the WiFi was not working. When running the sudo lshw -C network in a terminal window, the statement '*-network UNCLAIMED ' was presented for
** Package changed: ubuntu => linux-firmware (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2023396 Title: After an Ubuntu Update, the WiFi was not working. When running the sudo lshw -C network in a terminal window, the statement '*-network UNCLAIMED ' was presented for the network controller (Broadcom BCM43142 802.11b/g/n) Status in linux-firmware package in Ubuntu: New Bug description: The Ubuntu Release information shown after running 'lsb_release -a' No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.2 LTS Release: 22.04 Codename: jammy The printout from the terminal window after running lshw -C network *-network UNCLAIMED description: Network controller product: BCM43142 802.11b/g/n vendor: Broadcom Inc. and subsidiaries physical id: 0 bus info: pci@:06:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress cap_list configuration: latency=0 resources: memory:aa10-aa107fff *-network description: Ethernet interface product: RTL810xE PCI Express Fast Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:07:00.0 logical name: enp7s0 version: 07 serial: 20:47:47:49:34:06 capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=5.19.0-44-generic firmware=rtl8106e-1_0.0.1 06/29/12 latency=0 link=no multicast=yes port=twisted pair resources: irq:19 ioport:3000(size=256) memory:aa00-aa000fff memory:c000-c0003fff ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.14 ProcVersionSignature: Ubuntu 5.19.0-44.45~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jon2489 F pulseaudio /dev/snd/controlC0: jon2489 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 9 06:55:51 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-23 (289 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Dell Inc. Inspiron 3543 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-44-generic root=UUID=ac729c56-ab63-4579-9c28-60763aa3e9f3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-44-generic N/A linux-backports-modules-5.19.0-44-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.14 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/12/2019 dmi.bios.release: 65.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0M9V4C dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA11:bd09/12/2019:br65.11:svnDellInc.:pnInspiron3543:pvrA11:rvnDellInc.:rn0M9V4C:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:sku0654: dmi.product.name: Inspiron 3543 dmi.product.sku: 0654 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2023396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020413] Re: fix typo in config-checks invocation
This bug is awaiting verification that the linux-gke/5.15.0-1036.41 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' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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-gke -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2020413 Title: fix typo in config-checks invocation Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux source package in Jammy: Incomplete Status in linux-kvm source package in Jammy: Confirmed Bug description: [Impact] After migrating to the new annotations-only model in jammy we introduced a typo in debian/rules.d/4-checks.mk, that is triggered if we opt to not migrate to the new model and still use the old configs+annotations. [Test case] With debian./config/config.common.ubuntu present run the following command: $ fakeroot debian/rules clean updateconfigs [Fix] Replace @perl -> perl. [Regression potential] It's a trivial typo fix. Regressions can be introduced only if we are still using the old configs+annotations model. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020413/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020531] Re: support python < 3.9 with annotations
This bug is awaiting verification that the linux-gke/5.15.0-1036.41 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' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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-gke -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2020531 Title: support python < 3.9 with annotations Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: [Impact] At the moment we can't use the annotations scripts in focal, because we are using the'|=' update operator for merging dicts, that has been introduced with python 3.9. Rewrite the code that is using this operator in a more portable way and apply this change everywhere, so that annotations will work on any backport/derivative kernels. [Test case] Run `fakeroot debian/rules updateconfigs` in focal (using the new annotations model). [Fix] Try to use the '|=' operator in a try/except block, if it fails fallback to a more portable way. [Regression potential] With this change applied we may experience regressions during the updateconfigs phase. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2022098] Re: Severe NFS performance degradation after LP #2003053
This bug is awaiting verification that the linux- gke-5.15/5.15.0-1036.41~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-gke-5.15 verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2022098 Title: Severe NFS performance degradation after LP #2003053 Status in linux package in Ubuntu: Incomplete Status in linux-gke package in Ubuntu: New Status in linux source package in Focal: In Progress Status in linux-gke source package in Focal: Fix Released Status in linux source package in Jammy: In Progress Status in linux-gke source package in Jammy: Fix Released Bug description: The fix to LP #2003053 has caused massively increased NFS server access in some use-cases, which caused severe performance degradation to the point of being unusable in some cases. The solution to this issue, at least temporarily and at least for linux-gke, is to make the new behaviour optional using the "nfs_fasc=1" module parameter. Without this parameter specified, (or specified as =0) will keep the old behaviour. Regresion potential: - Regression potential is considered low considering the scope of the change and is limited to NFS only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022098/+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 1699942] Re: network-manager fails to deprecate addresses
This bug is stale, and it remains unclear if there is a systemd bug, so marking invalid. ** Changed in: systemd (Ubuntu) Status: Incomplete => 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/1699942 Title: network-manager fails to deprecate addresses Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: Invalid Bug description: network manager does not properly deprecate autoconfigured temporary IP addresses when ValidLifetime for a prefix is 0 in router advertisements. This behaviour is non-compliant with RFC 4861 § 6.3.4, which reads: If the prefix is already present in the host's Prefix List as the result of a previously received advertisement, reset its invalidation timer to the Valid Lifetime value in the Prefix Information option. If the new Lifetime value is zero, time-out the prefix immediately. The hosts instead continued to use temporary addresses configured until they reached their timeout, rather than immediately dropping the addresses. It further appears that it is generating new temporary addresses when the previous ones expire, but I have not been monitoring hosts closely enough to tell for sure---I will update on this when I have further information. This problem was discovered on Ubuntu Studio 16.04.2; it is not present on Ubuntu Server (which uses Debian networking scripts). Additional Info: $ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 $ apt-cache policy network-manager network-manager: Installed: 1.2.6-0ubuntu0.16.04.1 Candidate: 1.2.6-0ubuntu0.16.04.1 Version table: *** 1.2.6-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.2-0ubuntu0.16.04.4 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 1.1.93-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699942/+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 1979352] Re: system frozen after sleep
** Changed in: systemd (Ubuntu) Status: Incomplete => 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/1979352 Title: system frozen after sleep Status in Ubuntu MATE: Incomplete Status in acpid package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Status in upower package in Ubuntu: Incomplete Bug description: Linux V330 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux This is a bug that I reported with Ubuntu Mate 20.04 if I remember correctly but, at that time it was only apparent when I was using video ripping software on separate laptops and only when the machines became idle once the ripping program had finished. I don't think this bug was ever fixed and so I'm returning to it because I left my laptop in sleep mode over meal time to come back to a frozen system. I was not using the video ripping program this time, just surfing the Net. No other program was open. I run a Lenovo i7 V330-151KB and a Lenovo i5 Z50 but, the bug has happened when using an old Dell 1530 laptop. I do not believe I am unique in having this bug as someone has a similar bug when they have minimised Google Chrome and their system had went to sleep. I was also using Chrome this time but, as I have already said I was having this happen using another program and not using Chrome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1979352/+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 2011421] Autopkgtest regression report (glibc/2.35-0ubuntu3.2)
All autopkgtests for the newly accepted glibc (2.35-0ubuntu3.2) for jammy have finished running. The following regressions have been reported in tests triggered by the package: adsys/0.9.2~22.04.1 (armhf) bbmap/38.95+dfsg-1 (armhf) boost1.74/1.74.0-14ubuntu3 (armhf) breezy/3.2.1+bzr7585-1build1 (armhf) casync/2+20201210-1build1 (ppc64el) cmake/3.22.1-1ubuntu1.22.04.1 (amd64, arm64, armhf) cython/0.29.28-1ubuntu3 (i386) dbus-test-runner/16.10.0~bzr100+repack1-4.1 (armhf) exim4/4.95-4ubuntu2.2 (ppc64el) fwupd/1.7.9-1~22.04.1 (armhf) glib-networking/2.72.0-1 (i386) golang-github-influxdata-tail/1.0.0+git20180327.c434825-4 (ppc64el) golang-gogoprotobuf/1.3.2-1 (arm64) grubzfs-testsuite/0.4.15build1 (amd64) gtk+3.0/3.24.33-1ubuntu2 (i386) gyoto/1.4.4-7build1 (amd64, arm64, s390x) ksh93u+m/1.0.0~beta.2-1 (ppc64el) libassuan/2.5.5-1build1 (amd64) libflame/5.2.0-3ubuntu3 (s390x) libite/2.5.1-1 (s390x) linux-aws-5.19/5.19.0-1027.28~22.04.1 (amd64, arm64) linux-azure-5.19/5.19.0-1027.30~22.04.2 (amd64) linux-gcp-5.19/5.19.0-1026.28~22.04.1 (arm64) linux-gke/5.15.0-1034.39 (arm64) linux-hwe-5.19/5.19.0-44.45~22.04.1 (amd64) linux-lowlatency-hwe-5.19/5.19.0-1026.27~22.04.1 (amd64) linux-oracle-5.19/5.19.0-1025.28~22.04.1 (amd64) mercurial/6.1.1-1ubuntu1 (amd64) mtail/3.0.0~rc48-3 (ppc64el) mutter/42.5-0ubuntu1 (amd64) mypy/0.942-1ubuntu1 (armhf) mysql-8.0/8.0.33-0ubuntu0.22.04.2 (s390x) netgen/6.2.2006+really6.2.1905+dfsg-5build1 (armhf) notcurses/3.0.6+dfsg.1-1 (armhf) pango1.0/1.50.6+ds-2ubuntu1 (i386) phcpack/2.4.85+dfsg-5build1 (arm64) pinentry/1.1.1-1build2 (i386) puma/5.5.2-2ubuntu2 (amd64, arm64) pycryptodome/3.11.0+dfsg1-3build1 (i386) pygobject/3.42.1-0ubuntu1 (i386) python-evdev/1.4.0+dfsg-1build2 (i386) python-llfuse/1.3.8+dfsg-2build1 (armhf) python-lz4/3.1.3+dfsg-1build3 (i386) python3.10/3.10.6-1~22.04.2ubuntu1.1 (arm64) pyyaml/5.4.1-1ubuntu1 (i386) r-bioc-rhdf5/2.38.0+dfsg-2 (amd64) r-cran-randomfieldsutils/1.1.0-1 (armhf) r-cran-spc/1:0.6.5-1 (armhf) rsync/3.2.7-0ubuntu0.22.04.2 (i386) ruby-nio4r/2.5.8-2 (amd64) ruby-nokogiri/1.13.1+dfsg-2 (amd64) ruby-prof/1.3.1-2build2 (amd64, ppc64el) rustc/1.65.0+dfsg0ubuntu1-0ubuntu0.22.04.1 (arm64) seqkit/2.1.0+ds-1 (arm64, s390x) stunnel4/3:5.63-1build1 (i386) swtpm/0.6.3-0ubuntu3.2 (s390x) systemd/249.11-0ubuntu3.9 (amd64, arm64, ppc64el, s390x) taptempo/1.4.5-1 (amd64) texinfo/6.8-4build1 (armhf) ubiquity/22.04.19 (amd64, arm64, armhf, ppc64el) udisks2/2.9.4-1ubuntu2 (arm64) utox/0.18.1-1build1 (armhf) vlc/3.0.16-1build7 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#glibc [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2011421 Title: TDX azure instances crash during boot because of glibc bug Status in glibc package in Ubuntu: New Status in linux-azure package in Ubuntu: Fix Released Status in glibc source package in Jammy: Fix Committed Status in linux-azure source package in Jammy: Invalid Status in glibc source package in Kinetic: Won't Fix Status in linux-azure source package in Kinetic: In Progress Status in glibc source package in Lunar: Fix Released Status in linux-azure source package in Lunar: New Bug description: [IMPACT] Glibc in jammy and kinetic is affected by the following bug : https://sourceware.org/bugzilla/show_bug.cgi?id=29953 When cpuid reports no information on a shared cache, the x86_non_temporal_threshold will be set to zero, causing memcpy/memset to behave wrong for mid-sized operations. sysdeps/x86/dl-cacheinfo.h indicates that the minimum value must be 0x4040, but this is not enforced for the default value. The issue was reported because jammy tdx instances are failing to boot (crashing) on azure. The bug has been resolved upstream in https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b [TEST CASE] Test case requires an azure tdx instance. Microsoft has tested a test package with the above commit and confirmed that instances boot successfully. [REGRESSION POTENTIAL] The patches have been accepted upstream. They modify code for x86 architecture, so any potential regression would affect x86. [OTHER] Bug upstream: https://sourceware.org/bugzilla/show_bug.cgi?id=29953 Duplicate bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30037 In jammy we need 2 commits : https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=b446822b6ae4e8149902a78cdd4a886634ad6321 https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b In kinetic we just need :
[Kernel-packages] [Bug 2023394] Re: package linux-modules-nvidia-530-5.19.0-44-generic 5.19.0-44.45~22.04.1+1 failed to install/upgrade: installed linux-modules-nvidia-530-5.19.0-44-generic package po
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2023394 Title: package linux-modules-nvidia-530-5.19.0-44-generic 5.19.0-44.45~22.04.1+1 failed to install/upgrade: installed linux- modules-nvidia-530-5.19.0-44-generic package post-installation script subprocess returned error exit status 127 Status in linux-restricted-modules-hwe-5.19 package in Ubuntu: New Bug description: the version reported that there is a new update so when i tried to install this new update it gave me this error mentioned in the summary . am using DellG15 5520 RTX3050 there is a lot of bugs related to the NVIDIA drivers which is affecting the performance of the laptop so bad . ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-nvidia-530-5.19.0-44-generic 5.19.0-44.45~22.04.1+1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jun 9 16:51:30 2023 DuplicateSignature: package:linux-modules-nvidia-530-5.19.0-44-generic:5.19.0-44.45~22.04.1+1 Setting up linux-modules-nvidia-530-5.19.0-44-generic (5.19.0-44.45~22.04.1+1) ... /var/lib/dpkg/info/linux-modules-nvidia-530-5.19.0-44-generic.config: 6: /etc/default/linux-modules-nvidia: linux-modules-nvidia-530-open-5.19.0-43-generic: not found dpkg: error processing package linux-modules-nvidia-530-5.19.0-44-generic (--configure): installed linux-modules-nvidia-530-5.19.0-44-generic package post-installation script subprocess returned error exit status 127 ErrorMessage: installed linux-modules-nvidia-530-5.19.0-44-generic package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2023-05-17 (22 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: linux-restricted-modules-hwe-5.19 Title: package linux-modules-nvidia-530-5.19.0-44-generic 5.19.0-44.45~22.04.1+1 failed to install/upgrade: installed linux-modules-nvidia-530-5.19.0-44-generic package post-installation script subprocess returned error exit status 127 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-5.19/+bug/2023394/+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 2023394] [NEW] package linux-modules-nvidia-530-5.19.0-44-generic 5.19.0-44.45~22.04.1+1 failed to install/upgrade: installed linux-modules-nvidia-530-5.19.0-44-generic package
Public bug reported: the version reported that there is a new update so when i tried to install this new update it gave me this error mentioned in the summary . am using DellG15 5520 RTX3050 there is a lot of bugs related to the NVIDIA drivers which is affecting the performance of the laptop so bad . ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-nvidia-530-5.19.0-44-generic 5.19.0-44.45~22.04.1+1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jun 9 16:51:30 2023 DuplicateSignature: package:linux-modules-nvidia-530-5.19.0-44-generic:5.19.0-44.45~22.04.1+1 Setting up linux-modules-nvidia-530-5.19.0-44-generic (5.19.0-44.45~22.04.1+1) ... /var/lib/dpkg/info/linux-modules-nvidia-530-5.19.0-44-generic.config: 6: /etc/default/linux-modules-nvidia: linux-modules-nvidia-530-open-5.19.0-43-generic: not found dpkg: error processing package linux-modules-nvidia-530-5.19.0-44-generic (--configure): installed linux-modules-nvidia-530-5.19.0-44-generic package post-installation script subprocess returned error exit status 127 ErrorMessage: installed linux-modules-nvidia-530-5.19.0-44-generic package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2023-05-17 (22 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: linux-restricted-modules-hwe-5.19 Title: package linux-modules-nvidia-530-5.19.0-44-generic 5.19.0-44.45~22.04.1+1 failed to install/upgrade: installed linux-modules-nvidia-530-5.19.0-44-generic package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-restricted-modules-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy package-from-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2023394 Title: package linux-modules-nvidia-530-5.19.0-44-generic 5.19.0-44.45~22.04.1+1 failed to install/upgrade: installed linux- modules-nvidia-530-5.19.0-44-generic package post-installation script subprocess returned error exit status 127 Status in linux-restricted-modules-hwe-5.19 package in Ubuntu: New Bug description: the version reported that there is a new update so when i tried to install this new update it gave me this error mentioned in the summary . am using DellG15 5520 RTX3050 there is a lot of bugs related to the NVIDIA drivers which is affecting the performance of the laptop so bad . ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-nvidia-530-5.19.0-44-generic 5.19.0-44.45~22.04.1+1 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jun 9 16:51:30 2023 DuplicateSignature: package:linux-modules-nvidia-530-5.19.0-44-generic:5.19.0-44.45~22.04.1+1 Setting up linux-modules-nvidia-530-5.19.0-44-generic (5.19.0-44.45~22.04.1+1) ... /var/lib/dpkg/info/linux-modules-nvidia-530-5.19.0-44-generic.config: 6: /etc/default/linux-modules-nvidia: linux-modules-nvidia-530-open-5.19.0-43-generic: not found dpkg: error processing package linux-modules-nvidia-530-5.19.0-44-generic (--configure): installed linux-modules-nvidia-530-5.19.0-44-generic package post-installation script subprocess returned error exit status 127 ErrorMessage: installed linux-modules-nvidia-530-5.19.0-44-generic package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2023-05-17 (22 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: linux-restricted-modules-hwe-5.19 Title: package linux-modules-nvidia-530-5.19.0-44-generic 5.19.0-44.45~22.04.1+1 failed to install/upgrade: installed linux-modules-nvidia-530-5.19.0-44-generic package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug
[Kernel-packages] [Bug 1977827] Re: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm
kprobe_events are not available (seems related to CONFIG_KALLSYMS disabled) and this test `tools/testing/selftests/ftrace/test.d/dynevent/test_duplicates.tc` doesn't seems to works well in this case as it fails quickly: ``` + echo e:egroup/eevent syscalls/sys_enter_openat file=+0($filename):ustring ./ftracetest: 18: echo: echo: I/O error ``` ** Summary changed: - ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm + ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm -- 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/1977827 Title: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: Issue found on Jammy 5.15.0-36.37 with Power9 node baltar Test failed with: # [15] Generic dynamic event - check if duplicate events are caught [FAIL] Test Log: make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' TAP version 13 1..1 # selftests: ftrace: ftracetest # === Ftrace unit tests === # [1] Basic trace file check [PASS] # [2] Basic test for tracers [PASS] # [3] Basic trace clock test [PASS] # [4] Basic event tracing check [PASS] # [5] Change the ringbuffer size [PASS] # [6] Snapshot and tracing setting [PASS] # [7] trace_pipe and trace_marker[PASS] # [8] Test ftrace direct functions against tracers [UNRESOLVED] # [9] Test ftrace direct functions against kprobes [UNRESOLVED] # [10] Generic dynamic event - add/remove eprobe events [PASS] # [11] Generic dynamic event - add/remove kprobe events [PASS] # [12] Generic dynamic event - add/remove synthetic events [PASS] # [13] Generic dynamic event - selective clear (compatibility) [PASS] # [14] Generic dynamic event - generic clear event [PASS] # [15] Generic dynamic event - check if duplicate events are caught [FAIL] # [16] event tracing - enable/disable with event level files [PASS] # [17] event tracing - restricts events based on pid notrace filtering [PASS] # [18] event tracing - restricts events based on pid [PASS] # [19] event tracing - enable/disable with subsystem level files [PASS] # [20] event tracing - enable/disable with top level files [PASS] # [21] Test trace_printk from module [PASS] # [22] ftrace - function graph filters with stack tracer [PASS] # [23] ftrace - function graph filters [PASS] # [24] ftrace - function pid notrace filters [PASS] # [25] ftrace - function pid filters [PASS] # [26] ftrace - stacktrace filter command[PASS] # [27] ftrace - function trace with cpumask [PASS] # [28] ftrace - test for function event triggers [PASS] # [29] ftrace - function trace on module [PASS] # [30] ftrace - function profiling [PASS] # [31] ftrace - function profiler with function tracing [PASS] # [32] ftrace - test reading of set_ftrace_filter[PASS] # [33] ftrace - test for function traceon/off triggers [PASS] # [34] ftrace - test tracing error log support [PASS] # [35] Test creation and deletion of trace instances while setting an event [PASS] # [36] Test creation and deletion of trace instances [PASS] # [37] Kprobe dynamic event - adding and removing[PASS] # [38] Kprobe dynamic event - busy event check [PASS] # [39] Kprobe dynamic event with arguments [PASS] # [40] Kprobe event with comm arguments [PASS] # [41] Kprobe event string type argument [PASS] # [42] Kprobe event symbol argument [PASS] # [43] Kprobe event argument syntax [PASS] # [44] Kprobes event arguments with types[PASS] # [45] Kprobe event user-memory access [UNSUPPORTED] # [46] Kprobe event auto/manual naming [PASS] # [47] Kprobe dynamic event with function tracer [PASS] # [48] Create/delete multiprobe on kprobe event [PASS] # [49] Kprobe event parser error log check [PASS] # [50] Kretprobe dynamic event with arguments[PASS] # [51] Kretprobe dynamic event with maxactive[PASS] # [52] Kretprobe %return suffix test [PASS] # [53] Register/unregister many kprobe events[PASS] # [54] Kprobe profile[PASS] # [55] Uprobe event parser error log check [PASS] # [56] test for the preemptirqsoff tracer[UNSUPPORTED] # [57] Meta-selftest: Checkbashisms [PASS] # [58] Test wakeup tracer[PASS] # [59] Test wakeup RT tracer [PASS] # [60] event trigger - test inter-event histogram trigger expected fail actions
[Kernel-packages] [Bug 2023391] [NEW] Getting interrupts on isolated cores which causes significant jitter during low-latency work
Public bug reported: Summary: LOC, IWI, RES and CAL interrupts are observed on isolated cores on which low-latency benchmark is performed. Interrupts are caused by simple Go application (printing "Hello world" every 1 second) which runs on different, non-isolated cores. Similar Python application doesn't cause such problems. Tested on Ubuntu 22.04.2 LTS (GNU/Linux 5.15.0-68-lowlatency x86_64) (compiled with: "Full Dynticks System (tickless)" and "No Forced Preemption (Server)"). Would like to find out what causes this issue (Go itself? Kernel issue? Lack of proper kernel settings/parameters? Other?). Looking for help with hunting down root cause! Reason: To run Go-based applications on environments when lowlatency workloads are executed. Details: Hardware: 2 x Intel(R) Xeon(R) Gold 6438N (32 cores each) BIOS: Hyperthreading disabled OS and configuration: Ubuntu 22.04.2 LTS (GNU/Linux 5.15.0-68-lowlatency x86_64) (compiled with: "Full Dynticks System (tickless)" and "No Forced Preemption (Server)" from https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/log/?h=lowlatency-next) irqbalance stopped and disabled: systemctl stop irqbalance.service systemctl disable irqbalance.service Based on workload type, experiments and knowledge found in the Internet, following kernel parameters were used: cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.15.0-68-lowlatency root=UUID=5c9c2ea3-e0c6-4dd8-ae70-57e0c0af20d3 ro ro rhgb quiet ipv6.disable=1 audit=0 selinux=0 hugepages=256 hugepagesz=1G intel_iommu=on iommu=pt nmi_watchdog=0 mce=off tsc=reliable nosoftlockup hpet=disable skew_tick=1 acpi_pad.disable=1 nowatchdog nomce numa_balancing=disable irqaffinity=0 rcu_nocb_poll processor.max_cstate=0 clocksource=tsc nosmt nohz=on nohz_full=20-23 rcu_nocbs=20-23 isolcpus=nohz,domain,managed_irq,20-23 For every core/socket: Cx states (for x > 0) were disabled, particular power governor was used and fixed uncore values were set. To achieve that power.py script from https://github.com/intel/CommsPowerManagement was used. Check "prepare_cpus.sh" for particular commands and "cpu_prepared.png" for results. CPUs 20-23 are "isolated" (thanks to proper kernel parameters) - benchmark/workload will be run on them. cat /sys/devices/virtual/workqueue/cpumask ,ff0f (kernel threads moved from CPU20-23) "get_irqs.sh" - script which checks which target CPUs are permitted for a given IRQ sources. "get_irqs_output.txt" contains output of mentioned script. "lscpu_output.txt" - contains output of 'lscpu' command. JITTER tool - Baseline jitter is benchmarking tool which is meant for measuring the "jitter" in the execution time caused by OS and/or the underlying architecture. git clone https://github.com/FDio/archived-pma_tools cd archived-pma_tools/jitter Put "run_jitter.sh" script inside above directory. Run: make ./run_jitter.sh Results: - "jitter_base.txt" - output from "run_jitter.sh" script - "jitter_base.png" - chart created from above output Comment: jitter tool shows intervals and jitter in CPU Core cycles. Benchmark is done on 2000 MHz core so on graph values are divided by 2 and presented in nanoseconds. Very stable results, no significant jitters (max jitter: 51ns) during 335 seconds. No interruptions made on isolated CPU20 during benchmark. JITTER tool - Python "hello.py" - simple Python app which prints "Hello world" every 1 second "run_python_hello.sh" - script to run python app on particular (non-isolated) core python3 --version Python 3.10.6 In first console "./run_python_hello.sh" was started, in second console "./run_jitter.sh" was run. Results: - "jitter_python.txt" - output from "run_jitter.sh" script - "jitter_python.png" - chart created from above output Comment: Acceptable result, one noticeable jitter (1190ns), the remaining jitters did not exceed 60ns during 336 seconds. No interruptions made on isolated CPU20 during benchmark. JITTER tool - Golang "hello.go" - simple Golang app which prints "Hello world" every 1 second "go.mod" - go module definition "run_go_hello.sh" - script to run Go app on particular (non-isolated) core go version go version go1.20.5 linux/amd64 In first console Go app was built: "go build" and started: "./run_go_hello.sh", in second console "./run_jitter.sh" was run. Results: - "jitter_go.txt" - output from "run_jitter.sh" script - "jitter_go.png" - chart created from above output Comment: 34 significant jitters (the worst had: 44961ns) during 335 seconds. Following interruptions were made on isolated CPU20 during benchmark: LOC: 67 IWI: 34 RES: 34 RES: 34 It seems that every jitter is made every ~10s. What is also interesting that for idle and isolated CPU22 and CPU23 no interruptions were made during benchmark. For CPU24 (not isolated) only LOC were made (335283 of them). Notes: 1. Instead of static isolation (using kernel parameters) I tried also with cpuset and its shield turned on. Unfortunately,
[Kernel-packages] [Bug 2023391] Re: Getting interrupts on isolated cores which causes significant jitter during low-latency work
Archive contained all files/scripts/results mentioned ** Attachment added: "Archive contained and files/scripts/results mentioned" https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/2023391/+attachment/5678810/+files/files.zip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2023391 Title: Getting interrupts on isolated cores which causes significant jitter during low-latency work Status in linux-lowlatency package in Ubuntu: New Bug description: Summary: LOC, IWI, RES and CAL interrupts are observed on isolated cores on which low-latency benchmark is performed. Interrupts are caused by simple Go application (printing "Hello world" every 1 second) which runs on different, non-isolated cores. Similar Python application doesn't cause such problems. Tested on Ubuntu 22.04.2 LTS (GNU/Linux 5.15.0-68-lowlatency x86_64) (compiled with: "Full Dynticks System (tickless)" and "No Forced Preemption (Server)"). Would like to find out what causes this issue (Go itself? Kernel issue? Lack of proper kernel settings/parameters? Other?). Looking for help with hunting down root cause! Reason: To run Go-based applications on environments when lowlatency workloads are executed. Details: Hardware: 2 x Intel(R) Xeon(R) Gold 6438N (32 cores each) BIOS: Hyperthreading disabled OS and configuration: Ubuntu 22.04.2 LTS (GNU/Linux 5.15.0-68-lowlatency x86_64) (compiled with: "Full Dynticks System (tickless)" and "No Forced Preemption (Server)" from https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/log/?h=lowlatency-next) irqbalance stopped and disabled: systemctl stop irqbalance.service systemctl disable irqbalance.service Based on workload type, experiments and knowledge found in the Internet, following kernel parameters were used: cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.15.0-68-lowlatency root=UUID=5c9c2ea3-e0c6-4dd8-ae70-57e0c0af20d3 ro ro rhgb quiet ipv6.disable=1 audit=0 selinux=0 hugepages=256 hugepagesz=1G intel_iommu=on iommu=pt nmi_watchdog=0 mce=off tsc=reliable nosoftlockup hpet=disable skew_tick=1 acpi_pad.disable=1 nowatchdog nomce numa_balancing=disable irqaffinity=0 rcu_nocb_poll processor.max_cstate=0 clocksource=tsc nosmt nohz=on nohz_full=20-23 rcu_nocbs=20-23 isolcpus=nohz,domain,managed_irq,20-23 For every core/socket: Cx states (for x > 0) were disabled, particular power governor was used and fixed uncore values were set. To achieve that power.py script from https://github.com/intel/CommsPowerManagement was used. Check "prepare_cpus.sh" for particular commands and "cpu_prepared.png" for results. CPUs 20-23 are "isolated" (thanks to proper kernel parameters) - benchmark/workload will be run on them. cat /sys/devices/virtual/workqueue/cpumask ,ff0f (kernel threads moved from CPU20-23) "get_irqs.sh" - script which checks which target CPUs are permitted for a given IRQ sources. "get_irqs_output.txt" contains output of mentioned script. "lscpu_output.txt" - contains output of 'lscpu' command. JITTER tool - Baseline jitter is benchmarking tool which is meant for measuring the "jitter" in the execution time caused by OS and/or the underlying architecture. git clone https://github.com/FDio/archived-pma_tools cd archived-pma_tools/jitter Put "run_jitter.sh" script inside above directory. Run: make ./run_jitter.sh Results: - "jitter_base.txt" - output from "run_jitter.sh" script - "jitter_base.png" - chart created from above output Comment: jitter tool shows intervals and jitter in CPU Core cycles. Benchmark is done on 2000 MHz core so on graph values are divided by 2 and presented in nanoseconds. Very stable results, no significant jitters (max jitter: 51ns) during 335 seconds. No interruptions made on isolated CPU20 during benchmark. JITTER tool - Python "hello.py" - simple Python app which prints "Hello world" every 1 second "run_python_hello.sh" - script to run python app on particular (non-isolated) core python3 --version Python 3.10.6 In first console "./run_python_hello.sh" was started, in second console "./run_jitter.sh" was run. Results: - "jitter_python.txt" - output from "run_jitter.sh" script - "jitter_python.png" - chart created from above output Comment: Acceptable result, one noticeable jitter (1190ns), the remaining jitters did not exceed 60ns during 336 seconds. No interruptions made on isolated CPU20 during benchmark. JITTER tool - Golang "hello.go" - simple Golang app which prints "Hello world" every 1 second "go.mod" - go module definition "run_go_hello.sh" - script to run Go app on particular (non-isolated) core go version go version go1.20.5 linux/amd64 In first console Go app was built: "go build" and started: "./run_go_hello.sh",
[Kernel-packages] [Bug 1975592] Re: Enable Nezha board
** No longer affects: u-boot-nezha (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-allwinner in Ubuntu. https://bugs.launchpad.net/bugs/1975592 Title: Enable Nezha board Status in linux-allwinner package in Ubuntu: Fix Released Status in linux-riscv package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: Confirmed Bug description: [Impact] integrate linux-allwinner patches into linux-riscv kernel [Test] * Newly built images should boot and work on both nezha and licheerv * Upgraded systems using old images should reboot and work on both nezha and licheerv * Once this migrates, mantic+ livecd-rootfs can be improved to use generic kernel [Implementation details] * linux[-image]-allwinner depends on new enough generic kernel with allwinner support pull request applied; and on an updated u-boot-nezha package * new enough u-boot-nezha package ensures that MMC driver is included in the initramfs, and triggers initramfs update at the end of the apt transaction * End result, nezha/licheerv systems switch from tracking allwinner kernel to tracking generic kernel with initrd that contains MMC driver which used to be built-in. [Regression potential] Ensure this new build of linux-riscv doesn't regress on existing supported systems (sifive & qemu) scope: linux-riscv https://lists.ubuntu.com/archives/kernel-team/2023-May/139655.html u-boot-nezha patch attached linux-meta-riscv patch attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/1975592/+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 1975592] Re: Enable Nezha board
** Changed in: u-boot-nezha (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1975592 Title: Enable Nezha board Status in linux-allwinner package in Ubuntu: Fix Released Status in linux-riscv package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: Confirmed Status in u-boot-nezha package in Ubuntu: Won't Fix Bug description: [Impact] integrate linux-allwinner patches into linux-riscv kernel [Test] * Newly built images should boot and work on both nezha and licheerv * Upgraded systems using old images should reboot and work on both nezha and licheerv * Once this migrates, mantic+ livecd-rootfs can be improved to use generic kernel [Implementation details] * linux[-image]-allwinner depends on new enough generic kernel with allwinner support pull request applied; and on an updated u-boot-nezha package * new enough u-boot-nezha package ensures that MMC driver is included in the initramfs, and triggers initramfs update at the end of the apt transaction * End result, nezha/licheerv systems switch from tracking allwinner kernel to tracking generic kernel with initrd that contains MMC driver which used to be built-in. [Regression potential] Ensure this new build of linux-riscv doesn't regress on existing supported systems (sifive & qemu) scope: linux-riscv https://lists.ubuntu.com/archives/kernel-team/2023-May/139655.html u-boot-nezha patch attached linux-meta-riscv patch attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/1975592/+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 2019203] Re: mysql 8.0.33 binary crashes on startup on armhf
> The build at https://launchpad.net/ubuntu/+source/mysql-8.0/8.0.33-0ubuntu2 passed for armhf and MTR/CI did not fail. Why is it failing for users then? The tests are disabled on armhf: ifneq (,$(filter $(ARCH), amd64 i386)) TESTSUITE_FAIL_CMD:=exit 1 else TESTSUITE_FAIL_CMD:=true endif And autopkgtests have always failed on armhf also. -- 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/2019203 Title: mysql 8.0.33 binary crashes on startup on armhf Status in MySQL Server: Unknown Status in glibc package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in mysql-8.0 package in Ubuntu: Fix Released Status in glibc source package in Focal: Invalid Status in linux source package in Focal: Incomplete Status in mysql-8.0 source package in Focal: Fix Released Status in glibc source package in Jammy: Invalid Status in linux source package in Jammy: Incomplete Status in mysql-8.0 source package in Jammy: Fix Released Status in glibc source package in Kinetic: Invalid Status in linux source package in Kinetic: Incomplete Status in mysql-8.0 source package in Kinetic: Fix Released Status in glibc source package in Lunar: Invalid Status in linux source package in Lunar: Incomplete Status in mysql-8.0 source package in Lunar: Fix Released Status in glibc source package in Mantic: Invalid Status in linux source package in Mantic: Incomplete Status in mysql-8.0 source package in Mantic: Fix Released Bug description: From mantic autopkgtests: Setting up mysql-server-8.0 (8.0.33-0ubuntu2) ... update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf (my.cnf) in auto mode Renaming removed key_buffer and myisam-recover options (if present) ERROR: Unable to start MySQL server: 2023-05-09T17:23:22Z UTC - mysqld got signal 11 ; Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware. BuildID[sha1]=facf2109b23102b169b11737a1fc4bd99de4be1b Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x10 /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x2b) [0x205e0bc] /usr/sbin/mysqld(print_fatal_signal(int)+0x29d) [0x1533ba2] /usr/sbin/mysqld(handle_fatal_signal+0x71) [0x1533c9e] /lib/arm-linux-gnueabihf/libc.so.6(+0x2d750) [0xf6e7b750] /usr/sbin/mysqld(memory::Aligned_atomic::Aligned_atomic()+0x51) [0x1e0d49a] /usr/sbin/mysqld(Delegate::Delegate(unsigned int)+0x3b) [0x1e0d6c4] /usr/sbin/mysqld(delegates_init()+0x37) [0x1e0d804] /usr/sbin/mysqld(+0x8ec92c) [0x139592c] /usr/sbin/mysqld(mysqld_main(int, char**)+0x1959) [0x139a22a] /lib/arm-linux-gnueabihf/libc.so.6(+0x1d7da) [0xf6e6b7da] /lib/arm-linux-gnueabihf/libc.so.6(__libc_start_main+0x5d) [0xf6e6b87e] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. Please take a look at https://wiki.debian.org/Teams/MySQL/FAQ for tips on fixing common upgrade issues. Once the problem is resolved, run apt-get --fix-broken install to retry. dpkg: error processing package mysql-server-8.0 (--configure): installed mysql-server-8.0 package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/2019203/+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 2022826] Re: Ethernet hangs
@juergh Tech Support Realtek told me to disable Secure Boot which I have done. I was then able to compile & install r8125, r8128 & r8128 modules obtained from Realtek website. 'lsmod | grep r81' showed all 3 modules. ifconfig showed the ethernet interface Ok (as enp3s0). However, ethernet still hung on connection. So I rebooted and did 'lsmod | grep 81' only showed r8125! 'modinfo r8169 | grep 8125' showed nothing. Help please! -- 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/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2022826/+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 1988836] Re: LRMv7: Enable the open NVIDIA kernel modules
** Tags removed: verification-needed verification-needed-focal verification-needed-jammy ** Tags added: verification-done verification-done-jammy verification-needed-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 2023359] [NEW] raspi-nolpae flavor is pointless nowadays
Public bug reported: linux-raspi 5.4 in Focal is the first kernel that supports Pi 4B which requires LPAE to be enabled for armhf. Since we currently don't support board-specific kernels but follow a one-kernel-fits-all strategy, the LPAE kernel is also used on Pi 3 and 2 boards. Back then, running an armhf LPAE kernel on a Pi 3/2 resulted in additional kernel memory consumption of ~70MB compared to arm64 and non-LPAE kernels. For that reason I decided to introduce a raspi-nolpae flavor which can be used on Pi 3 and 2 (only). That flavor was never officially announced nor installed automatically anywhere. A user has to install in manually. We never had any complaints about kernel memory consumption so never directed anybody at installing this flavor. Therefore I'm assuming it's not being used... Turns out that the early 5.4 kernels were broken and incorrectly initialized a 64MB SWIOTLB buffer which is the reason for the above additional memory consumption. This was fixed here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fcf044891c84e38fc90eb736b818781bccf94e38 With this commit, the memory consumption of both the armhf raspi and raspi-nolpae flavor are pretty much on par and there is really no reason anymore to keep the raspi-nolpae flavor around. So let's get rid of it and introduce a transitional package that replaces installed raspi- nolpae packages with raspi packages. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux-raspi (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-raspi (Ubuntu Kinetic) Importance: Undecided Status: New ** Affects: linux-raspi (Ubuntu Lunar) Importance: Undecided Status: New ** Affects: linux-raspi (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Mantic) Importance: Undecided Status: New ** Summary changed: - -nolpae flavor is pointless nowadays + raspi-nolpae flavor is pointless nowadays ** Changed in: linux-raspi (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2023359 Title: raspi-nolpae flavor is pointless nowadays Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Focal: Invalid Status in linux-raspi source package in Jammy: New Status in linux-raspi source package in Kinetic: New Status in linux-raspi source package in Lunar: New Status in linux-raspi source package in Mantic: New Bug description: linux-raspi 5.4 in Focal is the first kernel that supports Pi 4B which requires LPAE to be enabled for armhf. Since we currently don't support board-specific kernels but follow a one-kernel-fits-all strategy, the LPAE kernel is also used on Pi 3 and 2 boards. Back then, running an armhf LPAE kernel on a Pi 3/2 resulted in additional kernel memory consumption of ~70MB compared to arm64 and non-LPAE kernels. For that reason I decided to introduce a raspi-nolpae flavor which can be used on Pi 3 and 2 (only). That flavor was never officially announced nor installed automatically anywhere. A user has to install in manually. We never had any complaints about kernel memory consumption so never directed anybody at installing this flavor. Therefore I'm assuming it's not being used... Turns out that the early 5.4 kernels were broken and incorrectly initialized a 64MB SWIOTLB buffer which is the reason for the above additional memory consumption. This was fixed here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fcf044891c84e38fc90eb736b818781bccf94e38 With this commit, the memory consumption of both the armhf raspi and raspi-nolpae flavor are pretty much on par and there is really no reason anymore to keep the raspi-nolpae flavor around. So let's get rid of it and introduce a transitional package that replaces installed raspi-nolpae packages with raspi packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2023359/+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
