Date: Sat, 15 Feb 2020 01:32:33 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 244118] 13-CURRENT Kernel post r357547 hang during boot on PowerMac G5Q Message-ID: <bug-244118-227-viL1GAx6q5@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-244118-227@https.bugs.freebsd.org/bugzilla/> References: <bug-244118-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=3D244118 --- Comment #9 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Mark Millard from comment #8) I got to thinking about my history investigating and I think this is too early for the device to be available for dump to use. Also the hangup likely prevents getting to ddb. So I set up -r357550's artifact materials on a SSD and got into ddb somewhat before the lockup. One part of acttrace looked potentially interesting (typed from a picture and avoiding typing everything for now): Tracing command cam pid 7 tid 100034 td . . . (CPU3) intr_event_handle powerpc_dispatch_intr openpic_dispatch powerpc_interrupt kernel EXI trap by __mtx_unlock_flags __mtx_unlock_flags xpt_copy_path xpt_async cam_periph_error probe_done xpt_done_process xpt_done_td fork_exit fork_trampoline -0x04 I've still got the picture to extract other details from if required. For thread 100034, "show locks" reported one: (I split the line below) exclusive sleep mutex CAM device lock (CAM device lock) r =3D 0 (. . .) locked @ /usr/src/sys/cam/cam_xpt.c:5490 --=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-244118-227-viL1GAx6q5>