Date: Sun, 13 Jun 2021 23:49:07 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 255289] panic: mmc: host bridge didn't serialize us Message-ID: <bug-255289-227-V1Z68Halku@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-255289-227@https.bugs.freebsd.org/bugzilla/> References: <bug-255289-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-255289-227-V1Z68Halku>