Date: Sun, 6 Nov 2016 15:46:03 -0700 From: Scott Long <scottl@samsco.org> To: Michael Tuexen <tuexen@FreeBSD.org> Cc: Sean Bruno <sbruno@freebsd.org>, freebsd-scsi <freebsd-scsi@freebsd.org> Subject: Re: mpt driver issue? Message-ID: <D7516284-A279-469F-9FE3-A0E6A88791C3@samsco.org> In-Reply-To: <CA6234F2-C0BF-472E-B904-FFBAE0ED29F9@freebsd.org> References: <CA9B9B19-5311-4A4E-87ED-8771C1000BEC@freebsd.org> <4398FA07-AABF-441E-A412-42BABCD59444@freebsd.org> <e9698b93-11e6-530a-1d27-ef45706eae66@freebsd.org> <CA6234F2-C0BF-472E-B904-FFBAE0ED29F9@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Nov 6, 2016, at 1:57 PM, Michael Tuexen <tuexen@FreeBSD.org> wrote: > >> On 6 Nov 2016, at 20:41, Sean Bruno <sbruno@freebsd.org> wrote: >> >> >> >> On 11/06/16 10:54, Michael Tuexen wrote: >>> Dear all, >>> >>> it was suggested on current@ to forward this to freebsd-scsi@ >>> >>> The problem shows up since r308268 and it looks like an issue >>> in the mpt driver... >>> >>> Best regards >>> Michael >> >> I don't see any *obvious* reason that we should hold the mpt lock here. >> It looks ok to just drop it. > I tried that and the system (with WITNESS) panic'ed... > Can't write a core (not a surprise). Any info on where the panic was? Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D7516284-A279-469F-9FE3-A0E6A88791C3>