From nobody Mon Apr 27 23:19:44 2026 X-Original-To: freebsd-stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4g4KKQ5NGwz6Zr1H for ; Mon, 27 Apr 2026 23:19:54 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4g4KKQ01VLz3rjH for ; Mon, 27 Apr 2026 23:19:53 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; none Received: from delta.joker.local (124-18-6-240.area1c.commufa.jp [124.18.6.240]) (authenticated bits=0) by www121.sakura.ne.jp (8.18.1/8.17.1/[SAKURA-WEB]/20201212) with ESMTPA id 63RNJiT6023993; Tue, 28 Apr 2026 08:19:44 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dec.sakura.ne.jp; s=s2405; t=1777331985; bh=yKaK3wuzVSk1GNfrgHNKbz09jzn3XAYJrGTTMHv+fmU=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=t//NGiYc5ynGANo3TN3OFKGNR/Qv+eVYYWnp2pt2HZ5Vrm8Id4VBfzCV9uITAzCsv +hR/kg5PNgEgBKqgL9GHb9U94XF1aw1IHu95dCdx3gHx1mVg/2Pc58U8H2uVfhpXJd N9BUSMHnk0AJAHm68yF7BjwCYklIbUW6L94lvBT4= Date: Tue, 28 Apr 2026 08:19:44 +0900 From: Tomoaki AOKI To: Quentin =?UTF-8?B?VGjDqWJhdWx0?= Cc: "freebsd-stable@FreeBSD.org" Subject: Re: stable/15 crash on boot with amdgpu Message-Id: <20260428081944.9bc83a60b6ad703048d4fef5@dec.sakura.ne.jp> In-Reply-To: References: Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd15.0) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP] X-Rspamd-Queue-Id: 4g4KKQ01VLz3rjH X-Spamd-Bar: ---- On Mon, 27 Apr 2026 13:08:53 +0000 Quentin Thébault 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