From nobody Sun Jun 13 23:49:07 2021 X-Original-To: bugs@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 63CC4F7F3E1 for ; Sun, 13 Jun 2021 23:49:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4G3BBC0MQ5z3NDk for ; Sun, 13 Jun 2021 23:49:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id E684D26B6 for ; Sun, 13 Jun 2021 23:49:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 15DNn6PQ015873 for ; Sun, 13 Jun 2021 23:49:06 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 15DNn692015872 for bugs@FreeBSD.org; Sun, 13 Jun 2021 23:49:06 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 255289] panic: mmc: host bridge didn't serialize us Date: Sun, 13 Jun 2021 23:49:07 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 12.2-RELEASE X-Bugzilla-Keywords: panic, regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: 9k0yuncu@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255289 Gokhan Koyuncu <9k0yuncu@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |9k0yuncu@gmail.com, | |imp@FreeBSD.org, | |marius@FreeBSD.org --- Comment #2 from Gokhan Koyuncu <9k0yuncu@gmail.com> --- Hello, I suffer from the same panic - though the stack is different: panic() at panic+0x43/frame 0xfffffe008e4cc3a0 mmc_acquire_bus() at mmc_acquire_bus+0x439/frame 0xfffffe008e4cc440 mmcsd_flush_cache() at mmcsd_flush_cache+0x68/frame 0xfffffe008e4cc480 mmcsd_close() at mmcsd_close+0x1f/frame 0xfffffe008e4cc4a0 g_disk_access() at g_disk_access+0x238/frame 0xfffffe008e4cc4e0 g_access() at g_access+0x1c0/frame 0xfffffe008e4cc570 g_dev_close() at g_dev_close+0x17a/frame 0xfffffe008e4cc5d0 devfs_close() at devfs_close+0x36f/frame 0xfffffe008e4cc640 VOP_CLOSE_APV() at VOP_CLOSE_APV+0x7a/frame 0xfffffe008e4cc670 vn_close1() at vn_close1+0x138/frame 0xfffffe008e4cc6f0 vn_closefile() at vn_closefile+0x4e/frame 0xfffffe008e4cc770 devfs_close_f() at devfs_close_f+0x2c/frame 0xfffffe008e4cc7a0 _fdrop() at _fdrop+0x29/frame 0xfffffe008e4cc7c0 closef() at closef+0x24a/frame 0xfffffe008e4cc850 closefp() at closefp+0x9e/frame 0xfffffe008e4cc890 I use 10/stable (amd64) (I know it is unsupported now). The platform is Int= el Apollo Lake with eMMC 5.0 controller (no other special patch or configurati= on). I can reproduce the panic with some networking activity that, I guess, trig= gers some disk activity which I can't characterize for now). How can I proceed with this issue? Any pointers are highly appreciated! I c= an provide further information. --=20 You are receiving this mail because: You are the assignee for the bug.=