Public bug reported: The following boot logs were noted on Questing deployment on lubba with questing 6.17.0-29.29 deployment through testfinger:
[ 69.979129] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000cc^M [ 69.979141] Mem abort info:^M [ 69.979145] ESR = 0x0000000096000004^M [ 69.979146] EC = 0x25: DABT (current EL), IL = 32 bits^M [ 69.979147] SET = 0, FnV = 0^M [ 69.979148] EA = 0, S1PTW = 0^M [ 69.979148] FSC = 0x04: level 0 translation fault^M [ 69.979149] Data abort info:^M [ 69.979150] ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000^M [ 69.979150] CM = 0, WnR = 0, TnD = 0, TagAccess = 0^M [ 69.979151] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0^M [ 69.979152] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000112a9e000^M [ 69.979154] [00000000000000cc] pgd=0000000000000000, p4d=0000000000000000^M [ 69.979158] Internal error: Oops: 0000000096000004 [#1] SMP^M [^[[0;32m OK ^[[0m] Listening on ^[[ 70.055117] Modules linked in: nouveau(+) gpu_sched drm_gpuvm drm_exec drm_ttm_helper ttm dax_hmem cxl_acpi drm_display_helper cxl_port cxl_core ast cec nvidia_cspmu rc_core einj ipmi_ssif(+) i2c_algo_bit arm_smmuv3_pmu arm_cspmu_module arm_spe_pmu uio_pdrv_genirq acpi_power_meter uio mlx5_fwctl acpi_ipmi spi_nor fwctl ipmi_devintf mtd cppc_cpufreq ipmi_msghandler sch_fq_codel efi_pstore dm_multipath nfnetlink dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq raid1 raid0 linear mlx5_ib ib_uverbs macsec ib_core mlx5_dpll uas polyval_ce usb_storage ghash_ce sm4_ce_gcm sm4_ce_ccm mlx5_core sm4_ce i2c_smbus nvme mlxfw sm4_ce_cipher nvme_core psample sm4 nvme_keyring sm3_ce tls sha3_ce xhci_pci_renesas pci_hyperv_intf nvme_auth i2c_tegra aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher^M [ 70.138368] CPU: 0 UID: 0 PID: 816 Comm: kworker/0:3 Not tainted 6.17.0-29-generic #29-Ubuntu PREEMPT(voluntary) ^M [ 70.148863] Hardware name: /P3880, BIOS 01.02.01 20240207^M [ 70.155180] Workqueue: events work_for_cpu_fn^M [ 70.159639] pstate: 63400009 (nZCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)^M [ 70.166755] pc : bit_entry+0x20/0x160 [nouveau]^M [ 70.171466] lr : nvbios_pmuTe+0x60/0x160 [nouveau]^M [ 70.176422] sp : ffff80008c943740^M [ 70.179804] x29: ffff80008c943740 x28: 0000000000028648 x27: 0000000000000030^M [ 70.187099] x26: 0000000000000180 x25: 0000000000000180 x24: 0000000000000019^M [ 70.194393] x23: ffff80008c9437f7 x22: 0000000000000070 x21: ffff80008c94383f^M [ 70.201688] x20: ffff80008c94383e x19: 0000000000000000 x18: ffff80008c93b0d8^M [ 70.208983] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000^M [ 70.216278] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000^M [ 70.223572] x11: 0000000000000000 x10: 0000000000000000 x9 : ffffc70f0fe8a6a8^M [ 70.230866] x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000000^M [ 70.238161] x5 : ffff0000a4944700 x4 : ffff80008c9437f7 x3 : ffff80008c9437f6^M [ 70.245456] x2 : ffff80008c943792 x1 : 0000000000000070 x0 : 0000000000000000^M [ 70.252752] Call trace:^M [ 70.255246] bit_entry+0x20/0x160 [nouveau] (P)^M [ 70.259929] nvbios_pmuTe+0x60/0x160 [nouveau]^M [ 70.264517] nvbios_pmuEp+0x60/0x120 [nouveau]^M [ 70.269102] nvkm_gsp_fwsec_init+0x90/0x1e0 [nouveau]^M [ 70.274311] nvkm_gsp_fwsec_sb_ctor+0x2c/0x60 [nouveau]^M [ 70.279693] r535_gsp_rm_boot_ctor+0x2c/0x138 [nouveau]^M [ 70.285072] r535_gsp_oneinit+0x258/0x340 [nouveau]^M [ 70.290093] gh100_gsp_oneinit+0x280/0x450 [nouveau]^M [ 70.295200] nvkm_gsp_oneinit+0x2c/0x70 [nouveau]^M [ 70.300040] nvkm_subdev_oneinit_+0x60/0x150 [nouveau]^M [ 70.305327] nvkm_subdev_init_+0x4c/0x190 [nouveau]^M [ 70.310345] nvkm_subdev_init+0x74/0xd8 [nouveau]^M [ 70.315184] nvkm_device_init+0x180/0x298 [nouveau]^M [ 70.320216] nvkm_udevice_init+0x78/0xa0 [nouveau]^M [ 70.325157] nvkm_object_init+0x50/0x200 [nouveau]^M [ 70.330094] nvkm_ioctl_new+0x198/0x280 [nouveau]^M [ 70.334938] nvkm_ioctl+0xd8/0x300 [nouveau]^M [ 70.339335] nvkm_client_ioctl+0x1c/0x48 [nouveau]^M [ 70.344285] nvif_object_ctor+0xf8/0x218 [nouveau]^M [ 70.349225] nvif_device_ctor+0x44/0xf0 [nouveau]^M [ 70.354070] nouveau_drm_device_new+0x1ec/0x438 [nouveau]^M [ 70.359639] nouveau_drm_probe+0xdc/0x250 [nouveau]^M [ 70.364672] local_pci_probe+0x48/0xd8^M [ 70.368505] work_for_cpu_fn+0x28/0x58^M [ 70.372335] process_one_work+0x174/0x428^M [ 70.376432] worker_thread+0x310/0x440^M [ 70.380262] kthread+0x110/0x130^M [ 70.383558] ret_from_fork+0x10/0x20^M [ 70.387215] Code: a9bc7bfd 910003fd a9025bf5 12001c36 (b940cc01) ^M [ 70.393445] ---[ end trace 0000000000000000 ]---^M Similar error was also noted on hinyari with full boot log attached. This causes undefined behavior, where in some cases the kernel boots up as well. The issue was reported upstream: https://lore.kernel.org/all/176698808133.6372.2408917375327107249@copycat/ and the fix has been accepted: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/nouveau?h=v7.1-rc5&id=e8b3627bec357698f2d4d6dbf27cdcfa0e9d8715 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Hinyari boot log on questing 6.17.0-29.29 deployment through testflinger" https://bugs.launchpad.net/bugs/2154481/+attachment/5974034/+files/hinyari-questing.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2154481 Title: Generic questing kernel oops on bootup with newer Nvidia machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154481/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
