Date: Mon, 07 Nov 2016 14:47:06 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 213371] panic: spin lock held too long Message-ID: <bug-213371-8-oDvxGt2ahc@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-213371-8@https.bugs.freebsd.org/bugzilla/> References: <bug-213371-8@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=3D213371 --- Comment #60 from Andriy Gapon <avg@FreeBSD.org> --- (In reply to Wojciech Giel from comment #59) Thank you! TLDR version of the screenshot for anyone else interested in the problem: one thread panics because it waits "too long" to acquire the ipi spin lock, the lock is held by a thread waiting for the targeted tlb shootdown to be executed by other cpus, the rest of the cpus are idle, acpi_cpu_idle_mwait = is used for that. Interesting attachments: https://bz-attachments.freebsd.org/attachment.cgi?id=3D176718 https://bz-attachments.freebsd.org/attachment.cgi?id=3D176719 https://bz-attachments.freebsd.org/attachment.cgi?id=3D176720 Wojciech, could you please try setting the following at loader prompt before booting = the kernel? debug.acpi.disabled=3Dmwait --=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-213371-8-oDvxGt2ahc>