[Kernel-packages] [Bug 2051720]
(In reply to Luiz Von Dentz from comment #16) > Can you guys try with the following change: > > https://patchwork.kernel.org/project/bluetooth/patch/20240401193515.2525201- > 1-luiz.de...@gmail.com/ I have the same issue and applied this patch to my kernel, but it seems to have broken the btintel module. I get a null pointer deref on boot and bluetooth is broken: [2.317366] BUG: kernel NULL pointer dereference, address: 0070 [2.317699] #PF: supervisor read access in kernel mode [2.317993] #PF: error_code(0x) - not-present page [2.318280] PGD 0 P4D 0 [2.318283] Oops: [#1] PREEMPT SMP NOPTI [2.318842] CPU: 3 PID: 185 Comm: kworker/u33:0 Not tainted 6.8.3-gentoo-dist #1 [2.318844] Hardware name: AZW SER/SER, BIOS SER7PRO_P5C8V30 09/15/2023 [2.318845] Workqueue: hci0 hci_alloc_dev_priv [bluetooth] [2.319426] RIP: 0010:btintel_configure_setup+0x245/0x970 [btintel] [2.320365] Code: 85 ff 75 a1 f0 41 80 8e 51 06 00 00 02 f0 41 80 8e 51 06 00 00 04 f0 41 80 8e 51 06 00 00 08 49 c7 86 38 17 00 00 b0 63 66 c1 <83> 7b 70 0a 75 7b 48 8b 83 d0 00 00 00 80 78 01 37 75 6e 0f 1f 44 [2.320691] RSP: 0018:a215005cfd48 EFLAGS: 00010202 [2.321452] RAX: RBX: RCX: 8026 [2.321760] RDX: 8027 RSI: d3238404d700 RDI: [2.322437] RBP: 91a940ccc6c8 R08: 8027 R09: 8026 [2.322438] R10: 0001 R11: R12: 91a940ccc6d0 [2.322439] R13: 91a947f50c00 R14: 91a940ccc000 R15: 91a940ccca88 [2.322441] FS: () GS:91af820c() knlGS: [2.323737] CS: 0010 DS: ES: CR0: 80050033 [2.323739] CR2: 0070 CR3: 00010dfa2000 CR4: 00f50ef0 [2.323740] PKRU: 5554 [2.323740] Call Trace: [2.323743] [2.326248] ? __die_body+0x68/0xb0 [2.326253] ? page_fault_oops+0x3a3/0x400 [2.326256] ? exc_page_fault+0x60/0xf0 [2.326265] ? asm_exc_page_fault+0x26/0x30 [2.326269] ? btintel_configure_setup+0x245/0x970 [btintel] [2.328091] ? btintel_configure_setup+0x16c/0x970 [btintel] [2.328093] ? __ia32_compat_sys_sysinfo+0x230/0x270 [2.329006] hci_dev_open_sync+0x166/0x1610 [bluetooth] [2.329013] ? srso_alias_return_thunk+0x5/0xfbef5 [2.329015] ? srso_alias_return_thunk+0x5/0xfbef5 [2.329016] ? srso_alias_return_thunk+0x5/0xfbef5 [2.329018] hci_alloc_dev_priv+0x164e/0x1bc0 [bluetooth] [2.329023] process_scheduled_works+0x24b/0x450 [2.329026] worker_thread+0x2c3/0x420 [2.329028] ? __pfx_worker_thread+0x10/0x10 [2.329030] kthread+0xe8/0x110 [2.329032] ? __pfx_kthread+0x10/0x10 [2.329033] ret_from_fork+0x37/0x50 [2.329036] ? __pfx_kthread+0x10/0x10 [2.329038] ret_from_fork_asm+0x1b/0x30 [2.329043] [2.329043] Modules linked in: amdxcp(+) ac97_bus(+) iwlwifi(+) snd_hda_codec(+) btusb snd_pcm_dmaengine gpu_sched vfat btbcm snd_pci_ps drm_suballoc_helper btintel i2c_algo_bit fat snd_rpl_pci_acp6x kvm(+) drm_ttm_helper snd_hda_core snd_acp_pci btrtl ttm snd_acp_legacy_common btmtk snd_pci_acp6x irqbypass drm_exec snd_hwdep snd_pci_acp5x snd_pcm drm_display_helper bluetooth snd_rn_pci_acp3x wmi_bmof cfg80211 snd_timer snd_acp_config rapl cec snd_soc_acpi snd pcspkr drm_buddy soundcore i2c_piix4 k10temp snd_pci_acp3x rfkill amd_pmc fuse loop nfnetlink crct10dif_pclmul crc32_pclmul crc32c_intel nvme polyval_clmulni polyval_generic ghash_clmulni_intel thunderbolt sha512_ssse3 sha256_ssse3 sha1_ssse3 nvme_core amd_sfh ccp sp5100_tco r8169 nvme_auth realtek video wmi i2c_hid_acpi i2c_hid serio_raw [2.329083] CR2: 0070 [2.329085] ---[ end trace ]--- [2.329087] RIP: 0010:btintel_configure_setup+0x245/0x970 [btintel] [2.329089] Code: 85 ff 75 a1 f0 41 80 8e 51 06 00 00 02 f0 41 80 8e 51 06 00 00 04 f0 41 80 8e 51 06 00 00 08 49 c7 86 38 17 00 00 b0 63 66 c1 <83> 7b 70 0a 75 7b 48 8b 83 d0 00 00 00 80 78 01 37 75 6e 0f 1f 44 [2.329090] RSP: 0018:a215005cfd48 EFLAGS: 00010202 [2.329091] RAX: RBX: RCX: 8026 [2.329092] RDX: 8027 RSI: d3238404d700 RDI: [2.329093] RBP: 91a940ccc6c8 R08: 8027 R09: 8026 [2.329093] R10: 0001 R11: R12: 91a940ccc6d0 [2.329094] R13: 91a947f50c00 R14: 91a940ccc000 R15: 91a940ccca88 [2.329095] FS: () GS:91af820c() knlGS: [2.329096] CS: 0010 DS: ES: CR0: 80050033 [2.329096] CR2: 0070 CR3: 00010dfa2000 CR4: 00f50ef0 [2.329097] PKRU: 5554 [2.329098] note: kworker/u33:0[185] exited with irqs disabled -- You received this bug notification because you are a member of
[Kernel-packages] [Bug 2060373] [NEW] package linux-generic-hwe-22.04 6.5.0.26.26 failed to install/upgrade: 의존성 문제 - 설정하지 않고 남겨둠
Public bug reported:
This occured while system updater installing packages with no user
operation.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-generic-hwe-22.04 6.5.0.26.26
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jungwonyong 2613 F wireplumber
/dev/snd/controlC0: jungwonyong 2613 F wireplumber
/dev/snd/seq:jungwonyong 2607 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sun Apr 7 12:08:46 2024
ErrorMessage: 의존성 문제 - 설정하지 않고 남겨둠
InstallationDate: Installed on 2024-01-25 (73 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ricifp@/vmlinuz-6.5.0-21-generic
root=ZFS=rpool/ROOT/ubuntu_ricifp ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-generic-hwe-22.04 6.5.0.26.26 failed to install/upgrade:
의존성 문제 - 설정하지 않고 남겨둠
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/08/2021
dmi.bios.release: 16.20
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1620
dmi.board.asset.tag: Default string
dmi.board.name: PRIME H470-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1620:bd07/08/2021:br16.20:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH470-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-package mantic need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2060373
Title:
package linux-generic-hwe-22.04 6.5.0.26.26 failed to install/upgrade:
의존성 문제 - 설정하지 않고 남겨둠
Status in linux package in Ubuntu:
New
Bug description:
This occured while system updater installing packages with no user
operation.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-generic-hwe-22.04 6.5.0.26.26
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jungwonyong 2613 F wireplumber
/dev/snd/controlC0: jungwonyong 2613 F wireplumber
/dev/snd/seq:jungwonyong 2607 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sun Apr 7 12:08:46 2024
ErrorMessage: 의존성 문제 - 설정하지 않고 남겨둠
InstallationDate: Installed on 2024-01-25 (73 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ricifp@/vmlinuz-6.5.0-21-generic
root=ZFS=rpool/ROOT/ubuntu_ricifp ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-generic-hwe-22.04 6.5.0.26.26 failed to install/upgrade:
의존성 문제 - 설정하지 않고 남겨둠
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/08/2021
dmi.bios.release: 16.20
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1620
dmi.board.asset.tag: Default string
dmi.board.name: PRIME H470-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
[Kernel-packages] [Bug 2048951] Re: Kernel Oops - kernel NULL pointer dereference (apparmor_bprm_creds_for_exec, profile_transition) with linux-image-6.5.0-18-generic (linux-image-generic-hwe-22.04)
Still reproducible with 6.5.0-26-generic kdump won't generate any dump or send anything over ssh. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048951 Title: Kernel Oops - kernel NULL pointer dereference (apparmor_bprm_creds_for_exec, profile_transition) with linux- image-6.5.0-18-generic (linux-image-generic-hwe-22.04) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few minutes after the boot. I can't find anything in the journal for the previous boot it just ends without any error. Remote syslog server does not receive any error log from this host. I've tried running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+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 2059978] Re: linux-aws-5.15 ADT test MISS because it's unable to find package
The issue is likely somewhere in https://salsa.debian.org/ci- team/autopkgtest/-/blob/933bd29bb628bad8a66b877298ebcfaeb4aa41a6/runner/autopkgtest#L348 -- 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/2059978 Title: linux-aws-5.15 ADT test MISS because it's unable to find package Status in Auto Package Testing: New Status in linux package in Ubuntu: New Bug description: SRU cycle 2024.03.04 Focal aws-5.15 ADT test linux-aws-5.15 for both amd64 and arm64 results in a MISS with the error message below. It seems like the test was unable to locate the kernel-testing--linux- aws-5.15--modules-extra--preferred$ package which led to other missing packages and the test erroring out with exit code 1. This test has been SKIPPED before but with seemingly different reasons. I have also attached the whole log amd64 output to this bug report. "339s Reading state information... 339s E: Unable to locate package ^kernel-testing--linux-aws-5.15--modules-extra--preferred$ 339s E: Couldn't find any package by glob '^kernel-testing--linux-aws-5.15--modules-extra--preferred$' 339s E: Couldn't find any package by regex '^kernel-testing--linux-aws-5.15--modules-extra--preferred$' 339s Reading package lists... 339s Building dependency tree... 339s Reading state information... 339s E: Unable to locate package ^linux-modules-extra-aws-5.15$ 339s E: Couldn't find any package by glob '^linux-modules-extra-aws-5.15$' 339s E: Couldn't find any package by regex '^linux-modules-extra-aws-5.15$' 339s autopkgtest [16:53:45]: rebooting testbed after setup commands that affected boot 363s autopkgtest [16:54:09]: testbed running kernel: Linux 5.15.0-1057-aws #63~20.04.1-Ubuntu SMP Mon Mar 25 10:28:36 UTC 2024 363s autopkgtest [16:54:09]: apt-source linux-aws-5.15 364s blame: linux-aws-5.15 364s badpkg: rules extract failed with exit code 1 364s autopkgtest [16:54:10]: ERROR: erroneous package: rules extract failed with exit code 1" To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2059978/+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 2060216] [NEW] Focal update: v5.4.271 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.271 upstream stable release from git://git.kernel.org/ netlink: Fix kernel-infoleak-after-free in __skb_datagram_iter net: ip_tunnel: prevent perpetual headroom growth tun: Fix xdp_rxq_info's queue_index when detaching ipv6: fix potential "struct net" leak in inet6_rtm_getaddr() lan78xx: enable auto speed configuration for LAN7850 if no EEPROM is detected net: usb: dm9601: fix wrong return value in dm9601_mdio_read Bluetooth: Avoid potential use-after-free in hci_error_reset Bluetooth: hci_event: Fix handling of HCI_EV_IO_CAPA_REQUEST Bluetooth: Enforce validation on max value of connection interval netfilter: nf_tables: allow NFPROTO_INET in nft_(match/target)_validate() rtnetlink: fix error logic of IFLA_BRIDGE_FLAGS writing back efi/capsule-loader: fix incorrect allocation size power: supply: bq27xxx-i2c: Do not free non existing IRQ ALSA: Drop leftover snd-rtctimer stuff from Makefile afs: Fix endless loop in directory parsing gtp: fix use-after-free and null-ptr-deref in gtp_newlink() wifi: nl80211: reject iftype change with mesh ID change btrfs: dev-replace: properly validate device names dmaengine: fsl-qdma: fix SoC may hang on 16 byte unaligned read dmaengine: fsl-qdma: init irq after reg initialization mmc: core: Fix eMMC initialization with 1-bit bus connection x86/cpu/intel: Detect TME keyid bits before setting MTRR mask registers cachefiles: fix memory leak in cachefiles_add_cache() fs,hugetlb: fix NULL pointer dereference in hugetlbs_fill_super gpio: 74x164: Enable output pins after registers are reset Linux 5.4.271 UBUNTU: Upstream stable to v5.4.271 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Manuel Diewald (diewald) Status: In Progress ** 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 ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Manuel Diewald (diewald) ** Description changed: 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.271 upstream stable release from git://git.kernel.org/ - + netlink: Fix kernel-infoleak-after-free in __skb_datagram_iter + net: ip_tunnel: prevent perpetual headroom growth + tun: Fix xdp_rxq_info's queue_index when detaching + ipv6: fix potential "struct net" leak in inet6_rtm_getaddr() + lan78xx: enable auto speed configuration for LAN7850 if no EEPROM is detected + net: usb: dm9601: fix wrong return value in dm9601_mdio_read + Bluetooth: Avoid potential use-after-free in hci_error_reset + Bluetooth: hci_event: Fix handling of HCI_EV_IO_CAPA_REQUEST + Bluetooth: Enforce validation on max value of connection interval + netfilter: nf_tables: allow NFPROTO_INET in nft_(match/target)_validate() + rtnetlink: fix error logic of IFLA_BRIDGE_FLAGS writing back + efi/capsule-loader: fix incorrect allocation size + power: supply: bq27xxx-i2c: Do not free non existing IRQ + ALSA: Drop leftover snd-rtctimer stuff from Makefile + afs: Fix endless loop in directory parsing + gtp: fix use-after-free and null-ptr-deref in gtp_newlink() + wifi: nl80211: reject iftype change with mesh ID change + btrfs: dev-replace: properly validate device names + dmaengine: fsl-qdma: fix SoC may hang on 16 byte unaligned read + dmaengine: fsl-qdma: init irq after reg initialization + mmc: core: Fix eMMC initialization with 1-bit bus connection + x86/cpu/intel: Detect TME keyid bits before setting MTRR mask registers + cachefiles: fix memory leak in cachefiles_add_cache() + fs,hugetlb: fix NULL pointer dereference in hugetlbs_fill_super + gpio: 74x164: Enable output pins after registers are reset Linux 5.4.271 - gpio: 74x164: Enable
[Kernel-packages] [Bug 2058477] Re: [Ubuntu 22.04.4/linux-image-6.5.0-26-generic] Kernel output "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux-hwe-6.5-6.5.0/drivers/net/hyperv/
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058477 Title: [Ubuntu 22.04.4/linux-image-6.5.0-26-generic] Kernel output "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux- hwe-6.5-6.5.0/drivers/net/hyperv/netvsc.c:1445:41" multiple times, especially during boot. Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in linux source package in Mantic: Confirmed Bug description: Overview: A newly installed Ubuntu Server 22.04.4 on a Hyper-V virtual machine outputs error message "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux- hwe-6.5-6.5.0/drivers/net/hyperv/netvsc.c:1446:41" multiple times, especially during boot. Reproducing steps: 1. Download ubuntu-22.04.4-live-server-amd64.iso 2. Create a Hyper-V virtual machine. 3. Install Ubuntu 22.04.4 Server on the VM with the downloaded iso normally. 4. Boot the machine. Additional Information: - Host machine: Windows 10 Pro 22H2 OS Build 19045.3758 - Hyper-V configuration version: 9.0 - The error message "UBSAN: array-index-out-of-bounds" is similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008157, but the drivers are different. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058477/+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 2060268] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2060268/+attachment/5761623/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060268 Title: Phantom 46" monitor (simpledrm) after installing the Nvidia driver Status in linux package in Ubuntu: New Status in nvidia-graphics-drivers-545 package in Ubuntu: New Bug description: After installing Nvidia driver 545 on a single (27") monitor system, Settings shows a phantom 46" monitor of the same resolution. It looks like the phantom monitor is /dev/dri/card0 which is still controlled by simpledrm, while Nvidia uses /dev/dri/card1. --- ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:dan4631 F pipewire /dev/snd/controlC1: dan4636 F wireplumber CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-01-04 (92 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) MachineType: Intel(R) Client Systems NUC12DCMi7 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240318.git3b128b60-0ubuntu1 Tags: noble Uname: Linux 6.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7: dmi.product.family: DC dmi.product.name: NUC12DCMi7 dmi.product.sku: RNUC12DCMi7 dmi.product.version: M30143-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060268/+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 2052835] Re: Error running program on cifs filesystem
mounting with -o cache=loose seems to circumvent the issue for me. This is probably not safe if multiple machines are accessing the same files. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2052835 Title: Error running program on cifs filesystem Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: Hi When I try and run a shell script which is on a cifs mounted system I get an error. This is on a 22.04 system - Linux bicr-compression 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux nkhan@bicr-compression:/mnt/cephfs/home/users/nkhan$ ~/data/NKHAN/linux-home/date.sh bash: /nfs/home/users/nkhan/data/NKHAN/linux-home/date.sh: /usr/bin/bash: bad interpreter: Input/output error In the kernel log there is: Feb 9 20:10:01 bicr-compression kernel: [ 1421.014745] [ cut here ] Feb 9 20:10:01 bicr-compression kernel: [ 1421.014761] WARNING: CPU: 16 PID: 5834 at fs/smb/client/file.c:3341 cifs_limit_bvec_subset.constprop.0+0x11a/0x190 [cifs] Feb 9 20:10:01 bicr-compression kernel: [ 1421.014849] Modules linked in: cmac nls_utf8 cifs cifs_arc4 cifs_md4 nfsv3 nfs_acl nfs lockd grace fscache netfs vsock_loopback vmw_vsock_virtio_transport_common intel_rapl_msr vmw_vsock_vmci_transport intel_rapl_common vsock intel_uncore_frequency_common binfmt_misc coretemp rapl nls_iso8859_1 vmw_balloon input_leds joydev serio_raw vmw_vmci mac_hid sch_fq_codel msr parport_pc auth_rpcgss ppdev lp parport efi_pstore sunrpc ip_tables x_tables autofs4 vmwgfx crct10dif_pclmul drm_ttm_helper crc32_pclmul polyval_clmulni ttm polyval_generic ghash_clmulni_intel drm_kms_helper aesni_intel crypto_simd mptspi mptscsih cryptd mptbase ahci drm psmouse libahci vmxnet3 scsi_transport_spi i2c_piix4 pata_acpi Feb 9 20:10:01 bicr-compression kernel: [ 1421.014910] CPU: 16 PID: 5834 Comm: bash Tainted: GW 6.5.0-17-generic #17~22.04.1-Ubuntu Feb 9 20:10:01 bicr-compression kernel: [ 1421.014914] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 09/30/2014 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014916] RIP: 0010:cifs_limit_bvec_subset.constprop.0+0x11a/0x190 [cifs] Feb 9 20:10:01 bicr-compression kernel: [ 1421.014969] Code: c0 48 29 c2 75 c4 41 89 0b 4c 89 c0 48 8b 5d f8 c9 31 d2 31 c9 31 f6 31 ff 45 31 c0 45 31 c9 45 31 d2 45 31 db c3 cc cc cc cc <0f> 0b 45 31 c0 4c 89 c0 31 d2 31 c9 31 f6 31 ff 45 31 c0 45 31 c9 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014971] RSP: 0018:b4ee07117b90 EFLAGS: 00010297 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014974] RAX: 9de487836418 RBX: 9de4878363c0 RCX: Feb 9 20:10:01 bicr-compression kernel: [ 1421.014975] RDX: b4ee07117bdc RSI: 0100 RDI: 9de487836418 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014977] RBP: b4ee07117c18 R08: 0100 R09: Feb 9 20:10:01 bicr-compression kernel: [ 1421.014978] R10: R11: R12: 9de48f998000 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014979] R13: 9de48f982400 R14: 0100 R15: 9de49ba32000 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014981] FS: 7f8f2ae67740() GS:9dfb5e20() knlGS: Feb 9 20:10:01 bicr-compression kernel: [ 1421.014982] CS: 0010 DS: ES: CR0: 80050033 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014984] CR2: 558a1cb1bf98 CR3: 0001abfd4001 CR4: 003706e0 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015030] DR0: DR1: DR2: Feb 9 20:10:01 bicr-compression kernel: [ 1421.015033] DR3: DR6: fffe0ff0 DR7: 0400 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015034] Call Trace: Feb 9 20:10:01 bicr-compression kernel: [ 1421.015036] Feb 9 20:10:01 bicr-compression kernel: [ 1421.015040] ? show_regs+0x6d/0x80 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015116] ? __warn+0x89/0x160 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015127] ? cifs_limit_bvec_subset.constprop.0+0x11a/0x190 [cifs] Feb 9 20:10:01 bicr-compression kernel: [ 1421.015181] ? report_bug+0x17e/0x1b0 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015198] ? handle_bug+0x46/0x90 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015212] ? exc_invalid_op+0x18/0x80 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015215] ? asm_exc_invalid_op+0x1b/0x20 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015226] ? cifs_limit_bvec_subset.constprop.0+0x11a/0x190 [cifs] Feb 9 20:10:01 bicr-compression kernel: [ 1421.015277] ?
[Kernel-packages] [Bug 2020917] Re: ethtool -m produces unreadable output for devices managed by the Intel ice driver
It looks like installation of this update may have resolved the issue on our systems: ethtool/jammy-updates 1:5.16-1ubuntu0.1 I believe that release was put together as a result of this bug report, which may or may not be a duplicate: https://bugs.launchpad.net/ubuntu/+source/ethtool/+bug/2043983 -- 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/2020917 Title: ethtool -m produces unreadable output for devices managed by the Intel ice driver Status in linux package in Ubuntu: Confirmed Bug description: We have a Supermicro X12SDV-8C-SP6F motherboard with a pair of SFP28 ports managed by an Intel E823-L for SFP controller. On this machine the SFP28 ports are eno3 and eno4. When asking ethtool for information about the installed SFP modules, we get this unhelpful output on Ubuntu Server 22.04 LTS: sudo ethtool --module-info eno3 Offset Values -- -- 0x: 03 04 07 20 00 00 02 00 00 00 00 06 67 02 0a 64 0x0010: 00 00 00 00 46 53 20 20 20 20 20 20 20 20 20 20 0x0020: 20 20 20 20 00 00 1b 21 53 46 50 2d 31 30 47 4c 0x0030: 52 2d 33 31 20 20 20 20 41 20 20 20 05 1e 00 d3 0x0040: 00 3a 00 00 46 32 30 33 30 33 32 32 36 38 39 20 0x0050: 20 20 20 20 32 32 30 34 30 32 20 20 68 fa 02 f1 0x0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 I suspect this is the same bug that was reported by Red Hat here (access requires a Red Hat account): https://access.redhat.com/solutions/6999793 This patch in netdev seems relevant: https://lore.kernel.org/netdev/20230228204139.2264495-1-po...@redhat.com/T/ If I understand that patch correctly, this might a netdev issue that was exposed by a change in ethtool. If that's the case, then it's possible this shouldn't be classified as an ethtool bug, but I figured I'd start here. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ethtool 1:5.16-1 ProcVersionSignature: Ubuntu 5.15.0-72.79-generic 5.15.98 Uname: Linux 5.15.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri May 26 17:29:58 2023 ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: ethtool UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 27 01:43 seq crw-rw 1 root audio 116, 33 May 27 01:43 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-05-25 (2 days ago) InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro SYS-E300-12D-8CN6P Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-72-generic root=UUID=b7ac1431-c6b1-4cef-af60-2626e4d6aab4 ro ProcVersionSignature: Ubuntu 5.15.0-72.79-generic 5.15.98 RelatedPackageVersions: linux-restricted-modules-5.15.0-72-generic N/A linux-backports-modules-5.15.0-72-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy Uname: Linux 5.15.0-72-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/08/2023 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X12SDV-8C-SP6F dmi.board.vendor: Supermicro dmi.board.version: 1.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.2:bd02/08/2023:br5.24:svnSupermicro:pnSYS-E300-12D-8CN6P:pvr0123456789:rvnSupermicro:rnX12SDV-8C-SP6F:rvr1.10:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: Family dmi.product.name: SYS-E300-12D-8CN6P dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to:
[Kernel-packages] [Bug 2020917] Re: ethtool -m produces unreadable output for devices managed by the Intel ice driver
I just went back to another machine that doesn't have "ethtool/jammy- updates 1:5.16-1ubuntu0.1" installed yet. It also produces correct output when I run "sudo ethtool --module-info eno3" now. I think it's likely that this issue was fixed by some previous release and I just didn't notice it until today. -- 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/2020917 Title: ethtool -m produces unreadable output for devices managed by the Intel ice driver Status in linux package in Ubuntu: Confirmed Bug description: We have a Supermicro X12SDV-8C-SP6F motherboard with a pair of SFP28 ports managed by an Intel E823-L for SFP controller. On this machine the SFP28 ports are eno3 and eno4. When asking ethtool for information about the installed SFP modules, we get this unhelpful output on Ubuntu Server 22.04 LTS: sudo ethtool --module-info eno3 Offset Values -- -- 0x: 03 04 07 20 00 00 02 00 00 00 00 06 67 02 0a 64 0x0010: 00 00 00 00 46 53 20 20 20 20 20 20 20 20 20 20 0x0020: 20 20 20 20 00 00 1b 21 53 46 50 2d 31 30 47 4c 0x0030: 52 2d 33 31 20 20 20 20 41 20 20 20 05 1e 00 d3 0x0040: 00 3a 00 00 46 32 30 33 30 33 32 32 36 38 39 20 0x0050: 20 20 20 20 32 32 30 34 30 32 20 20 68 fa 02 f1 0x0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 I suspect this is the same bug that was reported by Red Hat here (access requires a Red Hat account): https://access.redhat.com/solutions/6999793 This patch in netdev seems relevant: https://lore.kernel.org/netdev/20230228204139.2264495-1-po...@redhat.com/T/ If I understand that patch correctly, this might a netdev issue that was exposed by a change in ethtool. If that's the case, then it's possible this shouldn't be classified as an ethtool bug, but I figured I'd start here. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ethtool 1:5.16-1 ProcVersionSignature: Ubuntu 5.15.0-72.79-generic 5.15.98 Uname: Linux 5.15.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri May 26 17:29:58 2023 ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: ethtool UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 27 01:43 seq crw-rw 1 root audio 116, 33 May 27 01:43 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-05-25 (2 days ago) InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro SYS-E300-12D-8CN6P Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-72-generic root=UUID=b7ac1431-c6b1-4cef-af60-2626e4d6aab4 ro ProcVersionSignature: Ubuntu 5.15.0-72.79-generic 5.15.98 RelatedPackageVersions: linux-restricted-modules-5.15.0-72-generic N/A linux-backports-modules-5.15.0-72-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy Uname: Linux 5.15.0-72-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/08/2023 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X12SDV-8C-SP6F dmi.board.vendor: Supermicro dmi.board.version: 1.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.2:bd02/08/2023:br5.24:svnSupermicro:pnSYS-E300-12D-8CN6P:pvr0123456789:rvnSupermicro:rnX12SDV-8C-SP6F:rvr1.10:cvnSupermicro:ct1:cvr0123456789:skuTobefilledbyO.E.M.: dmi.product.family: Family dmi.product.name: SYS-E300-12D-8CN6P dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to:
[Kernel-packages] [Bug 2060337] [NEW] apply NVIDIA patches Mar 22 - April 5, 2024
Public bug reported: NVIDIA patches Mar 22 - April 5, 2024. NVIDIA tracking details soc/tegra: fuse: Remove security_mode fuse from keepout list https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107228 soc/tegra: fuse: Update Tegra234 nvmem keepout list https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107227 arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107255 arm64: defconfig: Enable DMATEST https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3105125 PCI: tegra194: Fix probe path for Endpoint mode https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3104622 arm64: configs: enable hidraw https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3103367 ** Affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New ** Affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2060337 Title: apply NVIDIA patches Mar 22 - April 5, 2024 Status in linux-nvidia-tegra package in Ubuntu: New Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: NVIDIA patches Mar 22 - April 5, 2024. NVIDIA tracking details soc/tegra: fuse: Remove security_mode fuse from keepout list https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107228 soc/tegra: fuse: Update Tegra234 nvmem keepout list https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107227 arm64: configs: Enable CONFIG_CRYPTO_USER_API_* as module https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3107255 arm64: defconfig: Enable DMATEST https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3105125 PCI: tegra194: Fix probe path for Endpoint mode https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3104622 arm64: configs: enable hidraw https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3103367 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2060337/+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 2060071] Re: Add initial r36.3 out-of-tree module meta packages
** Description changed: We want to enable tracks for different versions of the out-of-tree modules. For now we only have R36.3, so create the meta packages for that version. These meta packages include: - * linux-nvidia-tegra-igx-r36.3-igpu: for non-realtime kernel, R36.3 OOTM, and iGPU display drivers - * linux-nvidia-tegra-igx-rt-r36.3-igpu: for realtime kernel, R36.3 OOTM, and iGPU display drivers - * linux-nvidia-tegra-igx-r36.3-dgpu: for non-realtime kernel, R36.3 OOTM, and dGPU display drivers + * linux-nvidia-tegra-igx-r36.3: for non-realtime kernel, R36.3 OOTM + * linux-nvidia-tegra-igx-rt-r36.3: for realtime kernel, R36.3 OOTM -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx-modules-signed in Ubuntu. https://bugs.launchpad.net/bugs/2060071 Title: Add initial r36.3 out-of-tree module meta packages Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu: Fix Committed Bug description: We want to enable tracks for different versions of the out-of-tree modules. For now we only have R36.3, so create the meta packages for that version. These meta packages include: * linux-nvidia-tegra-igx-r36.3: for non-realtime kernel, R36.3 OOTM * linux-nvidia-tegra-igx-rt-r36.3: for realtime kernel, R36.3 OOTM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx-modules-signed/+bug/2060071/+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 2060327] [NEW] Reapply the linux-nvidia kernel config options from the 5.15 and 6.5 kernels
Public bug reported: There are a number of configuration options that were set in the 5.15. and 6.5 nvidia kernels. When the 6.8 based linux-nvidia kernel was created those config options were not brought forward. This patch set brings them into the 6.8 kernel. ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2060327 Title: Reapply the linux-nvidia kernel config options from the 5.15 and 6.5 kernels Status in linux-nvidia package in Ubuntu: New Bug description: There are a number of configuration options that were set in the 5.15. and 6.5 nvidia kernels. When the 6.8 based linux-nvidia kernel was created those config options were not brought forward. This patch set brings them into the 6.8 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2060327/+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 1981141] Re: Acer Swift SF114-34 standby/suspend/resume issue
This bug is still present in Ubuntu 22.04.4 LTS with current patches. I'm glad to have found the workaround mentioned above. -- 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/1981141 Title: Acer Swift SF114-34 standby/suspend/resume issue Status in linux package in Ubuntu: Confirmed Bug description: When I close the lid the laptop does not go to standby. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pbuzas 2163 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-11 (90 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 003: ID 1c7a:0575 LighTuning Technology Inc. EgisTec EH575 Bus 001 Device 002: ID 0408:a094 Quanta Computer, Inc. HD User Facing Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Swift SF114-34 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: wayland-session jammy Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/02/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Labatt_JL dmi.board.vendor: JSL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd08/02/2021:br1.11:efr1.11:svnAcer:pnSwiftSF114-34:pvrV1.11:rvnJSL:rnLabatt_JL:rvrV1.11:cvnAcer:ct10:cvrChassisVersion:sku: dmi.product.family: Swift 1 dmi.product.name: Swift SF114-34 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981141/+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 2060303] [NEW] ubuntu 22.04.4 lock up with nvidia driver, "NVRM: GPU 0000:01:00.0: GPU has fallen off the bus."
Public bug reported: I'm using Nvidia's driver on Ubuntu 22.04.4 without major issues since about a year (or so) on this DELL Latitude 5531 notebook (01:00.0 3D controller: NVIDIA Corporation TU117M [GeForce MX550] (rev a1)). Yesterday, I had an ubuntu update, so I use driver 535 now, the previous one was 525. After some hours after going to have lunch, I found my notebook locked up, I could not use my keyboard, mouse, and the fan of the notebook was almost "screaming" already. I don't remember a single event like this before the upgrade (with 525, and older ones before). Now, it happened again after a hour or so, and seems to be a regular theme from now :( Which is - for sure - very problematic since I had to hard power-off the system losing all non-saved work and workflow all the time. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-driver-535 535.161.07-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 15:52:11 2024 InstallationDate: Installed on 2022-09-23 (560 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: nvidia-graphics-drivers-535 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2060303 Title: ubuntu 22.04.4 lock up with nvidia driver, "NVRM: GPU :01:00.0: GPU has fallen off the bus." Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: I'm using Nvidia's driver on Ubuntu 22.04.4 without major issues since about a year (or so) on this DELL Latitude 5531 notebook (01:00.0 3D controller: NVIDIA Corporation TU117M [GeForce MX550] (rev a1)). Yesterday, I had an ubuntu update, so I use driver 535 now, the previous one was 525. After some hours after going to have lunch, I found my notebook locked up, I could not use my keyboard, mouse, and the fan of the notebook was almost "screaming" already. I don't remember a single event like this before the upgrade (with 525, and older ones before). Now, it happened again after a hour or so, and seems to be a regular theme from now :( Which is - for sure - very problematic since I had to hard power-off the system losing all non-saved work and workflow all the time. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-driver-535 535.161.07-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 15:52:11 2024 InstallationDate: Installed on 2022-09-23 (560 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: nvidia-graphics-drivers-535 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2060303/+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 2059961] Re: genetlink: fix single op policy dump when do is present
This bug is awaiting verification that the linux- bluefield/5.15.0-1040.42 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. 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-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2059961 Title: genetlink: fix single op policy dump when do is present Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: Fix Committed Bug description: intro - Our internal test triggers a kernel crash dump below [ 888.690348] Sun Mar 24 23:51:59 2024: DriVerTest - Start Test [ 888.691834] [ 888.983912] mlx5_core :08:00.1 eth3: Link up [ 888.987644] IPv6: ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready [ 889.336577] mlx5_core :08:00.0 eth2: Link up [ 894.635836] Sun Mar 24 11:52:04 PM IST 2024 - DriVerTest Debug Heartbeat [ 940.431644] general protection fault, probably for non-canonical address 0x80020014: [#1] SMP NOPTI [ 940.432866] CPU: 7 PID: 94305 Comm: ethtool Tainted: G OE 5.15.0-1039.17.g0d63875-bluefield #1 [ 940.433970] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 [ 940.435220] RIP: 0010:netlink_policy_dump_add_policy+0x95/0x160 [ 940.435893] Code: 48 c1 e0 04 4c 8b 34 01 4d 85 f6 74 5b 31 db eb 10 4c 89 e8 83 c3 01 48 c1 e0 04 39 5c 01 08 72 3f 89 d8 48 c1 e0 04 4c 01 f0 <0f> b6 10 83 ea 08 83 fa 01 77 dc 0f b7 50 02 48 8b 70 08 48 8d 7c [ 940.437921] RSP: 0018:ffa002d37a08 EFLAGS: 00010286 [ 940.438551] RAX: 80020014 RBX: RCX: ff1100027d00 [ 940.439351] RDX: fff8 RSI: 0018 RDI: ffa002d37a10 [ 940.440131] RBP: 0003 R08: 0040 R09: ff1100027d2d0f10 [ 940.440900] R10: 0318 R11: R12: ff1100011fa59bc0 [ 940.441683] R13: 0004 R14: 80020014 R15: 83fa6540 [ 940.442459] FS: 7f4a17993740() GS:ff1100085f9c() knlGS: [ 940.443394] CS: 0010 DS: ES: CR0: 80050033 [ 940.444044] CR2: 00429f50 CR3: 00012fc2e002 CR4: 00771ee0 [ 940.444847] DR0: DR1: DR2: [ 940.445639] DR3: DR6: fffe0ff0 DR7: 0400 [ 940.446431] PKRU: 5554 [ 940.446795] Call Trace: [ 940.447144] [ 940.447444] ? __die_body+0x1b/0x60 [ 940.447880] ? die_addr+0x39/0x60 [ 940.448315] ? exc_general_protection+0x1bc/0x3c0 [ 940.448867] ? asm_exc_general_protection+0x22/0x30 [ 940.449445] ? netlink_policy_dump_add_policy+0x95/0x160 [ 940.450058] ? netlink_policy_dump_add_policy+0xb2/0x160 [ 940.450714] ? ethtool_get_phc_vclocks+0x70/0x70 [ 940.451272] ctrl_dumppolicy_start+0xc4/0x2a0 [ 940.451788] ? ethnl_reply_init+0xd0/0xd0 [ 940.452284] ? __nla_parse+0x22/0x30 [ 940.452734] ? __cond_resched+0x15/0x30 [ 940.453211] ? kmem_cache_alloc_trace+0x44/0x390 [ 940.453750] genl_start+0xc3/0x150 [ 940.454179] __netlink_dump_start+0x175/0x250 [ 940.454706] genl_family_rcv_msg_dumpit.isra.0+0x9a/0x100 [ 940.455334] ? genl_family_rcv_msg_attrs_parse.isra.0+0xe0/0xe0 [ 940.455998] ? genl_unlock+0x20/0x20 [ 940.456453] ? genl_parallel_done+0x40/0x40 [ 940.456957] genl_rcv_msg+0x11f/0x2b0 [ 940.457421] ? genl_get_cmd+0x170/0x170 [ 940.457890] ? ctrl_dumppolicy_put_op.isra.0+0x1e0/0x1e0 [ 940.458515] ? genl_lock_done+0x60/0x60 [ 940.458987] ? genl_family_rcv_msg_doit.isra.0+0x110/0x110 [ 940.459634] netlink_rcv_skb+0x54/0x100 [ 940.460107] genl_rcv+0x24/0x40 [ 940.460504] netlink_unicast+0x18d/0x230 [ 940.460983] netlink_sendmsg+0x240/0x4a0 [ 940.461472] __sock_sendmsg+0x2f/0x40 [ 940.461922] __sys_sendto+0xee/0x160 [ 940.462384] ? __sys_recvmsg+0x56/0xa0 [ 940.462854] ? exit_to_user_mode_prepare+0x35/0x170 [ 940.463439] __x64_sys_sendto+0x25/0x30 [ 940.463906]
[Kernel-packages] [Bug 2040977] Re: Mouse cursor stutters if nothing else is animating on screen
This bug was fixed in the package mutter - 46.0-1ubuntu6 --- mutter (46.0-1ubuntu6) noble; urgency=medium * Rebuild for CVE-2024-3094 -- Jeremy Bícha Sun, 31 Mar 2024 10:24:22 -0400 ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-3094 -- 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/2040977 Title: Mouse cursor stutters if nothing else is animating on screen Status in Mutter: New Status in linux package in Ubuntu: Opinion Status in mutter package in Ubuntu: Fix Released Bug description: Using the touchpad on an X1 Carbon G10 with 90Hz OLED the mouse cursor stutters, unless something else is changing on screen (like running glmark2-wayland). Workaround: Put this in /etc/environment: MUTTER_DEBUG_FORCE_KMS_MODE=simple and reboot. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 15:48:28 2023 InstallationDate: Installed on 2023-10-23 (3 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2040977/+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 2059279] Re: mlxbf_gige: replace SAUCE patch for pause frame counters
This bug is awaiting verification that the linux- bluefield/5.15.0-1040.42 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. 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-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2059279 Title: mlxbf_gige: replace SAUCE patch for pause frame counters Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] The support for mlxbf_gige pause frame counters was added to Jammy via a SAUCE patch. After upstream review, a small issue was fixed that makes the SAUCE patch different from the upstream commit. [Fix] The fix is to replace the SAUCE patch in the Jammy repo with the upstream equivalent. [Test Case] * Boot BF platform and bring up "oob_net0" interface * Execute the command "ethtool -I -a oob_net0" to get baseline stats * Send heavy traffic into "oob_net0" interface * Re-run the above ethtool command, noting the pause frame counters [Regression Potential] There is low potential for regression as this brings in upstream content. [Other] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2059279/+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 2059951] Re: mlxbf_gige: stop interface during shutdown
This bug is awaiting verification that the linux- bluefield/5.15.0-1040.42 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. 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-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2059951 Title: mlxbf_gige: stop interface during shutdown Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] The mlxbf_gige driver shutdown() is invoked during reboot processing, but the stop() logic is not guaranteed to execute on all distros. If stop() does not execute NAPI remains enabled during system shutdown and can cause an exception if NAPI is scheduled when interface is shutdown but not stopped. [Fix] The networking interface managed by the mlxbf_gige driver must be stopped during reboot processing so that it is put into a clean state and driver callbacks won't be called. [Test Case] * Put BF platform into a reboot loop * Ensure that BF platform brings up "oob_net0" interface each reboot, and that no mlxbf_gige driver exceptions occur [Regression Potential] There is low potential for regression as this brings in upstream content. [Other] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2059951/+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 2056445] Re: external monitors flash white with every interrupt
I have a suspicion the root cause of the white screen could be fixed in BIOS 3.05. https://community.frame.work/t/framework- laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle-beta/48276 Can you still reproduce it with no workarounds, 6.8.0-20 and the BIOS upgrade? -- 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/2056445 Title: external monitors flash white with every interrupt Status in Linux: New Status in linux package in Ubuntu: Triaged Bug description: an interesting amdgpu issue: I currently have two external monitors, and only one will display the desktop at a time - the other is completely white. The interesting thing is that with each interrupt that the kernel receives from keyboard / mouse, the screens will flip which one is visible. With my monitors positioned above and to the left of the laptop's built-in display, the flashing monitors feel akin to attending an electronic light show, or perhaps a display of fireworks - the monitors flip visibility with each keypress. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 05:23:23 2024 InstallationDate: Installed on 2024-02-02 (34 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP07 dmi.board.vendor: Framework dmi.board.version: A7 dmi.chassis.asset.tag: FRANDGCPA735010072 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A7 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP07 dmi.product.version: A7 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2056445/+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 2060320] [NEW] executing a script or elf-file on a mounted share result in I/O Error in ubuntu 22.04, works on 18.04 (other shares work)
Public bug reported: The problem only exist with (all conditions must be true) - Ubuntu 22.04.4 LTS - kernel >= 6.5.0-14 (6.5.0-14 ist the oldes 6.5 I found in the repos) - mounted share from a Fritz-Box (works on mount from another linux PC) If I use kernel 6.2.0-39 (that's the newest Kernel before 6.5.0-14 in the repos) everything works. I first think it was a Shebang Problem, but the I/O error happens althougth when trying to start an elf-file. If using a shell script, I can use a workaround (see below): # > cat /t.sh #!/usr/bin/env bash echo "Hello bash" > /t.sh ... I/O-Error > bash /t.sh Hello bash # I coulnd find any problem on the Fritz-Box, the sniffs of the SMB messages seams to be OK. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 20:04:51 2024 InstallationDate: Installed on 2023-02-28 (402 days ago) InstallationMedia: SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2060320 Title: executing a script or elf-file on a mounted share result in I/O Error in ubuntu 22.04, works on 18.04 (other shares work) Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: The problem only exist with (all conditions must be true) - Ubuntu 22.04.4 LTS - kernel >= 6.5.0-14 (6.5.0-14 ist the oldes 6.5 I found in the repos) - mounted share from a Fritz-Box (works on mount from another linux PC) If I use kernel 6.2.0-39 (that's the newest Kernel before 6.5.0-14 in the repos) everything works. I first think it was a Shebang Problem, but the I/O error happens althougth when trying to start an elf-file. If using a shell script, I can use a workaround (see below): # > cat /t.sh #!/usr/bin/env bash echo "Hello bash" > /t.sh ... I/O-Error > bash /t.sh Hello bash # I coulnd find any problem on the Fritz-Box, the sniffs of the SMB messages seams to be OK. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 20:04:51 2024 InstallationDate: Installed on 2023-02-28 (402 days ago) InstallationMedia: SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2060320/+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 2060308] [NEW] no bluettoth detected
Public bug reported: no bluetooth detected ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 16:52:43 2024 InstallationDate: Installed on 2022-12-17 (475 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2060308 Title: no bluettoth detected Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: no bluetooth detected ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 16:52:43 2024 InstallationDate: Installed on 2022-12-17 (475 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2060308/+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 2060268] Re: Phantom 46" monitor (simpledrm) shown in Settings after installing the Nvidia driver
Probably nvidia.ko is missing a call to drm_aperture_remove_conflicting_pci_framebuffers() -- 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/2060268 Title: Phantom 46" monitor (simpledrm) shown in Settings after installing the Nvidia driver Status in linux package in Ubuntu: New Status in nvidia-graphics-drivers-545 package in Ubuntu: New Bug description: After installing Nvidia driver 545 on a single (27") monitor system, Settings shows a phantom 46" monitor of the same resolution. It looks like the phantom monitor is /dev/dri/card0 which is still controlled by simpledrm, while Nvidia uses /dev/dri/card1. --- ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:dan4631 F pipewire /dev/snd/controlC1: dan4636 F wireplumber CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-01-04 (92 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) MachineType: Intel(R) Client Systems NUC12DCMi7 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240318.git3b128b60-0ubuntu1 Tags: noble Uname: Linux 6.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7: dmi.product.family: DC dmi.product.name: NUC12DCMi7 dmi.product.sku: RNUC12DCMi7 dmi.product.version: M30143-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060268/+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 2060268] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2060268/+attachment/5761624/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060268 Title: Phantom 46" monitor (simpledrm) after installing the Nvidia driver Status in linux package in Ubuntu: New Status in nvidia-graphics-drivers-545 package in Ubuntu: New Bug description: After installing Nvidia driver 545 on a single (27") monitor system, Settings shows a phantom 46" monitor of the same resolution. It looks like the phantom monitor is /dev/dri/card0 which is still controlled by simpledrm, while Nvidia uses /dev/dri/card1. --- ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:dan4631 F pipewire /dev/snd/controlC1: dan4636 F wireplumber CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-01-04 (92 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) MachineType: Intel(R) Client Systems NUC12DCMi7 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240318.git3b128b60-0ubuntu1 Tags: noble Uname: Linux 6.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7: dmi.product.family: DC dmi.product.name: NUC12DCMi7 dmi.product.sku: RNUC12DCMi7 dmi.product.version: M30143-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060268/+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 2056491] Re: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block`
Fantastic, thanks for re-testing and confirming! Closing this ticket as Fix Released. ** Changed in: ubuntu-power-systems Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056491 Title: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block` Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: After I select `Try or Install Ubuntu Server` on a PowerVM ppc64le Power9 or Power10 : error: out of memory. Press any key to continue... OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 6.8.0-11-generic (buildd@bos01-ppc64el-003) (powerpc64le-linux-gnu-gcc-13 (Ubuntu 13.2.0-13ubuntu1) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 (Ubuntu 6.8.0-11.11-generic 6.8.0-rc4) Detected machine type: 0101 command line: BOOT_IMAGE=/casper/vmlinux quiet --- Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0e67 alloc_top: 2000 alloc_top_hi : 2000 rmo_top : 2000 ram_top : 2000 instantiating rtas at 0x1ec3... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x1078 -> 0x1078179e Device tree struct 0x1079 -> 0x107a Quiescing Open Firmware ... Booting Linux via __start() @ 0x0a75 ... [0.019184] plpks: POWER LPAR Platform KeyStore is not supported or enabled [0.114052] SED: plpks not available [0.114507] /dev/root: Can't open blockdev [0.114520] List of all bdev filesystems: [0.114523] ext3 [0.114523] ext2 [0.114525] ext4 [0.114527] squashfs [0.114529] vfat [0.114531] fuseblk [0.114532] [0.114535] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.114540] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.8.0-11-generic #11-Ubuntu [0.114545] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1030.00 (NH1030_017) hv:phyp pSeries [0.114551] Call Trace: [0.114553] [c6403b40] [c16b2f28] dump_stack_lvl+0x70/0xb4 (unreliable) [0.114562] [c6403b70] [c01926ec] panic+0x300/0x524 [0.114568] [c6403c10] [c301146c] mount_root_generic+0x208/0x448 [0.114574] [c6403ce0] [c30118d8] prepare_namespace+0x98/0x430 [0.114580] [c6403d70] [c3010820] kernel_init_freeable+0x32c/0x37c [0.114585] [c6403de0] [c00115ec] kernel_init+0x34/0x298 [0.114591] [c6403e50] [c000dfbc] ret_from_kernel_user_thread+0x14/0x1c [0.114596] --- interrupt: 0 at 0x0 [0.117006] pstore: backend (nvram) writing error (-1) [0.119362] Rebooting in 10 seconds.. This is the message from a Power10(9080-HEX), but the same is happening on a PowrerVM-Power9 (9009-22A) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056491/+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 2060268] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2060268/+attachment/5761626/+files/acpidump.txt ** Also affects: nvidia-graphics-drivers-545 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Phantom 46" monitor after installing the Nvidia driver + Phantom 46" monitor (simpledrm) after installing the Nvidia driver ** Changed in: nvidia-graphics-drivers-545 (Ubuntu) Importance: Undecided => Low -- 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/2060268 Title: Phantom 46" monitor (simpledrm) after installing the Nvidia driver Status in linux package in Ubuntu: New Status in nvidia-graphics-drivers-545 package in Ubuntu: New Bug description: After installing Nvidia driver 545 on a single (27") monitor system, Settings shows a phantom 46" monitor of the same resolution. It looks like the phantom monitor is /dev/dri/card0 which is still controlled by simpledrm, while Nvidia uses /dev/dri/card1. --- ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:dan4631 F pipewire /dev/snd/controlC1: dan4636 F wireplumber CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-01-04 (92 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) MachineType: Intel(R) Client Systems NUC12DCMi7 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240318.git3b128b60-0ubuntu1 Tags: noble Uname: Linux 6.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7: dmi.product.family: DC dmi.product.name: NUC12DCMi7 dmi.product.sku: RNUC12DCMi7 dmi.product.version: M30143-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060268/+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 2059310] Re: mlxbf_gige: call request_irq() after NAPI initialized
This bug is awaiting verification that the linux- bluefield/5.15.0-1040.42 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'. 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-bluefield-v2 verification-needed-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2059310 Title: mlxbf_gige: call request_irq() after NAPI initialized Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] The mlxbf_gige driver encounters a NULL pointer exception in mlxbf_gige_open() when kdump is enabled. The exception happens because there is a pending RX interrupt before the call to request_irq(RX IRQ) executes. Then, the RX IRQ handler fires immediately after this request_irq() completes. The RX IRQ handler runs "napi_schedule()" before NAPI is fully initialized via "netif_napi_add()" and "napi_enable()", both which happen later in the open() logic. [Fix] The logic in mlxbf_gige_open() must fully initialize NAPI before any calls to request_irq() execute. [Test Case] * Boot BF platform and bring up "oob_net0" interface * Enable kdump completely * Trigger kdump via "echo c > /proc/sysrq-trigger" * There should be no exceptions from mlxbf_gige driver [Regression Potential] There is low potential for regression as this brings in upstream content. [Other] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2059310/+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 2060268] [NEW] Phantom 46" monitor (simpledrm) after installing the Nvidia driver
Public bug reported: After installing Nvidia driver 545 on a single (27") monitor system, Settings shows a phantom 46" monitor of the same resolution. It looks like the phantom monitor is /dev/dri/card0 which is still controlled by simpledrm, while Nvidia uses /dev/dri/card1. --- ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:dan4631 F pipewire /dev/snd/controlC1: dan4636 F wireplumber CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-01-04 (92 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) MachineType: Intel(R) Client Systems NUC12DCMi7 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240318.git3b128b60-0ubuntu1 Tags: noble Uname: Linux 6.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7: dmi.product.family: DC dmi.product.name: NUC12DCMi7 dmi.product.sku: RNUC12DCMi7 dmi.product.version: M30143-302 dmi.sys.vendor: Intel(R) Client Systems ** Affects: linux (Ubuntu) Importance: Low Status: New ** Affects: nvidia-graphics-drivers-545 (Ubuntu) Importance: Low Status: New ** Tags: apport-collected noble nvidia simpledrm ** Tags added: apport-collected ** Description changed: After installing Nvidia driver 545 on a single (27") monitor system, Settings shows a phantom 46" monitor of the same resolution. - It looks like the phantom monitor is /dev/dri/card0 which is still - controlled by simpledrm, while Nvidia uses /dev/dri/card1. + It looks like the phantom monitor is /dev/dri/card0 which is still controlled by simpledrm, while Nvidia uses /dev/dri/card1. + --- + ProblemType: Bug + ApportVersion: 2.28.0-0ubuntu1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/seq:dan4631 F pipewire + /dev/snd/controlC1: dan4636 F wireplumber + CRDA: N/A + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 24.04 + InstallationDate: Installed on 2024-01-04 (92 days ago) + InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) + MachineType: Intel(R) Client Systems NUC12DCMi7 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= + ProcFB: 0 simpledrmdrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7 + ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 + RelatedPackageVersions: + linux-restricted-modules-6.8.0-11-generic N/A + linux-backports-modules-6.8.0-11-generic N/A + linux-firmware20240318.git3b128b60-0ubuntu1 + Tags: noble + Uname: Linux 6.8.0-11-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sudo users + _MarkForUpload: True + dmi.bios.date: 12/20/2021 + dmi.bios.release: 5.24 + dmi.bios.vendor: Intel Corp. + dmi.bios.version: EDADL579.0046.2021.1220.2351 + dmi.board.name: NUC12EDBi7 + dmi.board.vendor: Intel Corporation + dmi.board.version: M27908-302 + dmi.chassis.type: 35 + dmi.chassis.vendor: Intel Corporation + dmi.chassis.version: 2.0 + dmi.ec.firmware.release: 3.7 + dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7: + dmi.product.family: DC + dmi.product.name: NUC12DCMi7 + dmi.product.sku: RNUC12DCMi7 +
[Kernel-packages] [Bug 2056491] Re: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block`
I was able to successfully install and boot PowerVM partitions - Power9 and Power10 with the latest kernel `6.8.0-20.20` (today's image - 20240405) : POWER10 LPAR: ``` patricia@noble-a5:~$ cat /var/log/installer/media-info Ubuntu-Server 24.04 LTS "Noble Numbat" - Daily ppc64el (20240405)patricia@noble-a5:~$ patricia@noble-a5:~$ uname -a Linux noble-a5 6.8.0-20-generic #20-Ubuntu SMP Mon Mar 18 11:46:05 UTC 2024 ppc64le ppc64le ppc64le GNU/Linux patricia@noble-a5:~$ lscpu |grep Model Model name: POWER10 (architected), altivec supported ``` and POWER9 LPAR: ``` patricia@p9g-lpar-i:~$ lscpu |grep Model && uname -a Model name: POWER9 (architected), altivec supported Model:2.2 (pvr 004e 0202) Linux p9g-lpar-i 6.8.0-20-generic #20-Ubuntu SMP Mon Mar 18 11:46:05 UTC 2024 ppc64le ppc64le ppc64le GNU/Linux ``` -- 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/2056491 Title: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block` Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: After I select `Try or Install Ubuntu Server` on a PowerVM ppc64le Power9 or Power10 : error: out of memory. Press any key to continue... OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 6.8.0-11-generic (buildd@bos01-ppc64el-003) (powerpc64le-linux-gnu-gcc-13 (Ubuntu 13.2.0-13ubuntu1) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 (Ubuntu 6.8.0-11.11-generic 6.8.0-rc4) Detected machine type: 0101 command line: BOOT_IMAGE=/casper/vmlinux quiet --- Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0e67 alloc_top: 2000 alloc_top_hi : 2000 rmo_top : 2000 ram_top : 2000 instantiating rtas at 0x1ec3... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x1078 -> 0x1078179e Device tree struct 0x1079 -> 0x107a Quiescing Open Firmware ... Booting Linux via __start() @ 0x0a75 ... [0.019184] plpks: POWER LPAR Platform KeyStore is not supported or enabled [0.114052] SED: plpks not available [0.114507] /dev/root: Can't open blockdev [0.114520] List of all bdev filesystems: [0.114523] ext3 [0.114523] ext2 [0.114525] ext4 [0.114527] squashfs [0.114529] vfat [0.114531] fuseblk [0.114532] [0.114535] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.114540] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.8.0-11-generic #11-Ubuntu [0.114545] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1030.00 (NH1030_017) hv:phyp pSeries [0.114551] Call Trace: [0.114553] [c6403b40] [c16b2f28] dump_stack_lvl+0x70/0xb4 (unreliable) [0.114562] [c6403b70] [c01926ec] panic+0x300/0x524 [0.114568] [c6403c10] [c301146c] mount_root_generic+0x208/0x448 [0.114574] [c6403ce0] [c30118d8] prepare_namespace+0x98/0x430 [0.114580] [c6403d70] [c3010820] kernel_init_freeable+0x32c/0x37c [0.114585] [c6403de0] [c00115ec] kernel_init+0x34/0x298 [0.114591] [c6403e50] [c000dfbc] ret_from_kernel_user_thread+0x14/0x1c [0.114596] --- interrupt: 0 at 0x0 [0.117006] pstore: backend (nvram) writing error (-1) [0.119362] Rebooting in 10 seconds.. This is the message from a Power10(9080-HEX), but the same is happening on a PowrerVM-Power9 (9009-22A) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056491/+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 2048768] Re: Autopkgtest failures on amd64
This bug was fixed in the package gcc-12 - 12.3.0-17ubuntu1 --- gcc-12 (12.3.0-17ubuntu1) noble; urgency=medium * Merge with Debian; remaining changes: - Build from upstream sources. gcc-12 (12.3.0-17) unstable; urgency=medium * Fix typo in distro_defaults spec. gcc-12 (12.3.0-16) unstable; urgency=medium * Update to git 20240403 from the gcc-12 branch. - Fix PR tree-optimization/111407, PR target/113233 (loong64), PR sanitizer/97696, PR tree-optimization/110838, PR tree-optimization/91838, PR target/108743 (Darwin), PR target/101737 (SH), PR tree-optimization/110221, PR ada/113979, PR d/112285, PR d/112290, PR d/114171, PR d/113758, PR d/113125, PR fortran/107426, PR fortran/50410, PR fortran/103715, PR libstdc++/40380, PR libstdc++/107376, PR libstdc++/112473, PR libstdc++/72, PR libstdc++/112089, PR libstdc++/113960, PR libstdc++/108846, PR libstdc++/86419, PR libstdc++/109758, PR libstdc++/110593, PR libstdc++/66146, PR libstdc++/107500, PR libstdc++/114147, PR libstdc++/110167. * ASan: move allocator base to avoid conflict with high-entropy ASLR for x86-64 Linux. Patch taken from LLVM. LP: #2048768. * Make vhdl known to the PPC backend. * libsanitizer: Remove crypt and crypt_r interceptors for releases with glibc (>= 2.31). * d/p/gcc-distro-defaults: Make -fstack-protector-explicit known. * Move the _FORTIFY_SOURCE setting from cc1 to the driver. * Update the proposed patch to fix PR ada/114064. * Apply proposed patch for PR libquadmath/114533 (Simon Chopin). Addresses: #1064426. LP: #2052929. * Refresh patches. -- Matthias Klose Wed, 03 Apr 2024 14:27:33 +0200 ** Changed in: gcc-12 (Ubuntu Noble) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2048768 Title: Autopkgtest failures on amd64 Status in gcc-10 package in Ubuntu: Confirmed Status in gcc-11 package in Ubuntu: Confirmed Status in gcc-12 package in Ubuntu: Fix Released Status in gcc-13 package in Ubuntu: Fix Released Status in gcc-8 package in Ubuntu: Invalid Status in gcc-9 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in llvm-toolchain-14 package in Ubuntu: Confirmed Status in llvm-toolchain-15 package in Ubuntu: Confirmed Status in llvm-toolchain-16 package in Ubuntu: Confirmed Status in gcc-10 source package in Noble: Won't Fix Status in gcc-11 source package in Noble: Won't Fix Status in gcc-12 source package in Noble: Fix Released Status in gcc-13 source package in Noble: Fix Released Status in gcc-8 source package in Noble: Invalid Status in gcc-9 source package in Noble: Won't Fix Status in linux source package in Noble: Fix Released Status in llvm-toolchain-14 source package in Noble: Won't Fix Status in llvm-toolchain-15 source package in Noble: Won't Fix Status in llvm-toolchain-16 source package in Noble: Confirmed Bug description: Some tests related to the address sanitizer are occasionally failing on amd64 (also for llvm-toolchain-15 and 16): -- FAIL: LLVM regression suite :: test_leaksan.c (38 of 45) 746s TEST 'LLVM regression suite :: test_leaksan.c' FAILED 746s Script: 746s -- 746s : 'RUN: at line 4'; /usr/bin/clang-14 -o /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp -fsanitize=address -g /tmp/autopkgtest.gHVujV/autopkgtest_tmp/tests/test_leaksan.c 746s : 'RUN: at line 5'; env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s : 'RUN: at line 6'; grep -q "detected memory leaks" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s -- 746s Exit Code: 139 746s 746s Command Output (stderr): 746s -- 746s /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.script: line 3: 3335 Segmentation fault (core dumped) env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out -- If you run the test manually you'll notice that it works but eventually crashes: ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8631==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5e9c3441ed12 in __interceptor_malloc
[Kernel-packages] [Bug 2042546] Re: Include cifs.ko in linux-modules package
** Description changed: + [Impact] + + Commit: "smb: move client and server files to common directory fs/smb" moved the fs/cifs directory to fs/sb/client. The inclusion list for linux-modules was not updated, it still contains the old path. This means that the cifs.ko module cannot be loaded if only linux-modules package is installed, now being part of linux-modules-extra. + For the main kernels this is not a problem because linux-modules-extra is always installed, but for derivatives like aws, azure etc, this module cannot be loaded without explicitly installing linux-modules-extra. + + [How to reproduce it]: + 1. Install the latest azure kernel 6.5.0-1016.16 + 2. Load cifs module + $ modprobe cifs + modprobe: FATAL: Module cifs not found in directory /lib/modules/6.5.0-1016-azure + If modules-extra is installed, this works. + + [Fix] + + Replace fs/cifs/* with fs/smb/client/* in + debian./control.d/.inclusion-list + + [Test Plan] + + 1. Apply the fix to one of the derivative (azure), build a new kernel and install it + 2. Load cifs module + $ modprobe cifs + It should work without installing modules-extra. + + [Regression potential] + + Very low, it's a straightforward fix. + + [Other Info] + Sending a patch for every derivative takes time and each derivative will be fixed once this proposal is acked via cranky fix. + + Original for lunar only SRU Justification: [Impact] Commit: "smb: move client and server files to common directory fs/smb" introduced in 2023.09.04 moved the fs/cifs directory to fs/sb/client. The inclusion list for linux-modules was not updated, it still contains the old path. This means that the cifs.ko module cannot be loaded if only linux-modules package is installed, now being part of linux-modules-extra. For lunar:main this is not a problem because linux-modules-extra is always installed, but for derivatives like aws, azure etc, this module cannot be loaded without explicitly installing linux-modules-extra. [How to reproduce it]: 1. Install the latest azure kernel 6.2.0-1016.16 2. Load cifs module $ modprobe cifs modprobe: FATAL: Module cifs not found in directory /lib/modules/6.2.0-1016-azure If modules-extra is installed, this works. [Fix] Replace fs/cifs/* with fs/smb/client/* in debian./control.d/.inclusiojn-list This is going to be done in s2023.10.02 cycle for derivatives. [Test Plan] 1. Apply the fix to one of the derivative (azure), build a new kernel and install it 2. Load cifs module $ modprobe cifs It should work without installing modules-extra. [Regression potential] Very low, it's a straightforward fix. [Other Info] Sending a patch for every derivative takes time and each derivative will be fixed once this proposal is acked. There is also the possibility to do it via cranky fix, but owners may omit it during security updates and it's hard to enforce it. Plus, it is a one-time change. ** Description changed: [Impact] Commit: "smb: move client and server files to common directory fs/smb" moved the fs/cifs directory to fs/sb/client. The inclusion list for linux-modules was not updated, it still contains the old path. This means that the cifs.ko module cannot be loaded if only linux-modules package is installed, now being part of linux-modules-extra. For the main kernels this is not a problem because linux-modules-extra is always installed, but for derivatives like aws, azure etc, this module cannot be loaded without explicitly installing linux-modules-extra. [How to reproduce it]: - 1. Install the latest azure kernel 6.5.0-1016.16 + 1. Install the latest azure kernel 6.5.0-1017.17 2. Load cifs module $ modprobe cifs - modprobe: FATAL: Module cifs not found in directory /lib/modules/6.5.0-1016-azure + modprobe: FATAL: Module cifs not found in directory /lib/modules/6.5.0-1017-azure If modules-extra is installed, this works. [Fix] Replace fs/cifs/* with fs/smb/client/* in debian./control.d/.inclusion-list [Test Plan] 1. Apply the fix to one of the derivative (azure), build a new kernel and install it 2. Load cifs module $ modprobe cifs It should work without installing modules-extra. [Regression potential] Very low, it's a straightforward fix. [Other Info] Sending a patch for every derivative takes time and each derivative will be fixed once this proposal is acked via cranky fix. Original for lunar only SRU Justification: [Impact] Commit: "smb: move client and server files to common directory fs/smb" introduced in 2023.09.04 moved the fs/cifs directory to fs/sb/client. The inclusion list for linux-modules was not updated, it still contains the old path. This means that the cifs.ko module cannot be loaded if only linux-modules package is installed, now being part of linux-modules-extra. For lunar:main this is not a problem because linux-modules-extra is always
[Kernel-packages] [Bug 2060300] [NEW] KMS overlay causes OOM oops on 3A+
Public bug reported: Came across something bizarre when investigating the audio situation with server on the Pi 5 (LP: #2038924). Moving the server images to use the KMS overlay solves the situation, and would be preferable as it would eliminate another difference between server and desktop images. However, it also renders the 512MB 3A+ unbootable with an out-of-memory error. The reason this is strange is that the 512MB Zero 2W continues to boot quite happily. I'm attaching the serial output from the kernel up to the point of the crash (screenlog.0). The only changes made to the stock server config.txt were the addition of these lines under the final "[all]" section: [all] dtoverlay=vc4-kms-v3d disable_fw_kms_setup=1 This setup booted happily on all other boards. A trivial workaround is to manually specify a smaller CMA on the 3A+ with: dtoverlay=vc4-kms-v3d,cma-128 With this alteration, it boots happily (and I'll be using this in an appropriate [section] to work around the issue), but it might be nice to understand why this is required on this board specifically (and why the 512MB Zero 2W doesn't exhibit the same issue). ** Affects: linux-raspi (Ubuntu) Importance: Low Status: New ** Attachment added: "screenlog.0" https://bugs.launchpad.net/bugs/2060300/+attachment/5761694/+files/screenlog.0 ** Changed in: linux-raspi (Ubuntu) Importance: Undecided => Low -- 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/2060300 Title: KMS overlay causes OOM oops on 3A+ Status in linux-raspi package in Ubuntu: New Bug description: Came across something bizarre when investigating the audio situation with server on the Pi 5 (LP: #2038924). Moving the server images to use the KMS overlay solves the situation, and would be preferable as it would eliminate another difference between server and desktop images. However, it also renders the 512MB 3A+ unbootable with an out- of-memory error. The reason this is strange is that the 512MB Zero 2W continues to boot quite happily. I'm attaching the serial output from the kernel up to the point of the crash (screenlog.0). The only changes made to the stock server config.txt were the addition of these lines under the final "[all]" section: [all] dtoverlay=vc4-kms-v3d disable_fw_kms_setup=1 This setup booted happily on all other boards. A trivial workaround is to manually specify a smaller CMA on the 3A+ with: dtoverlay=vc4-kms-v3d,cma-128 With this alteration, it boots happily (and I'll be using this in an appropriate [section] to work around the issue), but it might be nice to understand why this is required on this board specifically (and why the 512MB Zero 2W doesn't exhibit the same issue). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2060300/+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
