Date: Thu, 03 Jun 2010 10:43:26 +0300 From: Alexander Motin <mav@FreeBSD.org> To: Matthew Jacob <mj@feral.com>, current <current@freebsd.org> Subject: Re: ata panic: "mtx_lock of destroyed mutex" Message-ID: <4C075D1E.7040406@FreeBSD.org> In-Reply-To: <mailpost.1275501555.6745010.86478.mailing.freebsd.current@FreeBSD.cs.nctu.edu.tw> References: <20100602185714.000069be@unknown> <mailpost.1275501555.6745010.86478.mailing.freebsd.current@FreeBSD.cs.nctu.edu.tw>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Jacob wrote: > Hmm. I just fixed that at Panasas, and I'm pretty sure that I gave the > patch to Alexander Motin to put in. Do you mean one committed at r207221 or something else? >> I've been setting up an amd64 VirtualBox machine with the latest >> 9-CURRENT and got the following panic when booting it (another machine >> updated and booting at the same time didn't panic): >> >> ata1: WARNING - READ_TOC read data overrun 18>12 >> panic: mtx_lock of destroyed mutex @ /usr/src/sys/kern/kern_sema.c:79 >> cpuid = 0 >> >> with the following stack trace: >> >> kdb_enter >> panic >> _mtx_lock_flags >> _sema_post >> ata_completed >> taskqueue_run >> intr_event_execute_handlers >> ithread_loop >> fork_exit >> fork_trampoline -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C075D1E.7040406>