Date: Tue, 28 Apr 2026 08:19:44 +0900 From: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> To: Quentin =?UTF-8?B?VGjDqWJhdWx0?= <quentin.thebault@defenso.fr> Cc: "freebsd-stable@FreeBSD.org" <freebsd-stable@FreeBSD.org> Subject: Re: stable/15 crash on boot with amdgpu Message-ID: <20260428081944.9bc83a60b6ad703048d4fef5@dec.sakura.ne.jp> In-Reply-To: <MR0P264MB704858730D1F7A2A5EA00F0AF5362@MR0P264MB7048.FRAP264.PROD.OUTLOOK.COM>
index | next in thread | previous in thread | raw e-mail
On Mon, 27 Apr 2026 13:08:53 +0000 Quentin Thébault <quentin.thebault@defenso.fr> wrote: > Hello, > > I have been running 15-STABLE for a few weeks and since around three weeks ago I have had to come back to an older BE (stable/15-n283067-e9d3512bb587) because I get an amdgpu-related panic on boot. > > You will find attached two crashinfos: > - core.txt.8 is with drm-66-kmod built from the ports tree, > KDB: stack backtrace: > #0 0xffffffff80bcf71d at kdb_backtrace+0x5d > #1 0xffffffff80b80316 at vpanic+0x136 > #2 0xffffffff80b801d3 at panic+0x43 > #3 0xffffffff81091b88 at trap_fatal+0x68 > #4 0xffffffff81067b78 at calltrap+0x8 > #5 0xffffffff80e0832a at lkpi_devm_device_add_group+0x3a > #6 0xffffffff84615ab2 at amdgpu_device_init+0x1cf2 > #7 0xffffffff84636fc6 at amdgpu_driver_load_kms+0x16 > #8 0xffffffff846268df at amdgpu_pci_probe+0x29f > #9 0xffffffff80e10dcc at linux_pci_attach_device+0x57c > #10 0xffffffff80bbe5cd at device_attach+0x43d > #11 0xffffffff80bc0323 at bus_generic_driver_added+0x73 > #12 0xffffffff80bbbb89 at devclass_driver_added+0x29 > #13 0xffffffff80bbbb1e at devclass_add_driver+0x11e > #14 0xffffffff80e11e2c at _linux_pci_register_driver+0xcc > #15 0xffffffff84626633 at amdgpu_evh+0x73 > #16 0xffffffff80b5a5a5 at module_register_init+0x85 > #17 0xffffffff80b4b12f at linker_load_module+0xc0f > > - core.txt.9 is with drm-latest-kmod from pkg. > KDB: stack backtrace: > #0 0xffffffff80bcf71d at kdb_backtrace+0x5d > #1 0xffffffff80b80316 at vpanic+0x136 > #2 0xffffffff80b801d3 at panic+0x43 > #3 0xffffffff81091fcd at trap_pfault+0x37d > #4 0xffffffff81067b78 at calltrap+0x8 > #5 0xffffffff80e1f997 at xa_load+0x77 > #6 0xffffffff84536966 at drm_sched_entity_pop_job+0x86 > #7 0xffffffff84535445 at drm_sched_run_job_work+0x215 > #8 0xffffffff80e1ece4 at linux_work_fn+0xe4 > #9 0xffffffff80be6212 at taskqueue_run_locked+0x182 > #10 0xffffffff80be73e2 at taskqueue_thread_loop+0xc2 > #11 0xffffffff80b36b5b at fork_exit+0x7b > #12 0xffffffff81068b9e at fork_trampoline+0xe > > Is this a know bug? Is there something I can do? > > Kind regards, > -- > Quentin THÉBAULT How do you upgrading base ports? If it's via official pkgs, you need to wait base upgrading until builder jail for stable/15 is upgraded into exactly the same commit (to be safest) of the kernel you're willing to upgrade to. Not all, but any updates to LinuxKPI could cause breakage on already-built DRM/KMS kmods. The safest is to build at least kmod ports that wants LinuxKPI locally. But even in this case, possibly you need to wait for upgrades of graphics/drm-*-kmod you're using (I assume graphics/drm-66-kmod as it's the default installed via graphics/drm-kmod metaport). Subscribe or watch via web archive of dev-commits-src-branches ML to see if there are any commits to LinuxKPI codes. https://lists.freebsd.org/archives/dev-commits-src-branches/ Regards. -- Tomoaki AOKI <junchoon@dec.sakura.ne.jp>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20260428081944.9bc83a60b6ad703048d4fef5>