Date: Mon, 28 Nov 2016 07:49:34 -0500 From: David Cross <dcrosstech@gmail.com> To: Fabian Keil <freebsd-listen@fabiankeil.de> Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD 11 i386 disk deadlock (I think) (now with reproduction steps!) Message-ID: <CAM9edeMz7xu5TXajTAJ9RxTDt9gi1hBq5RAyNxFb2kNs6P2gXw@mail.gmail.com> In-Reply-To: <20161128133936.7e815c9a@fabiankeil.de> References: <CAM9edeMYMhnkWid7Lig5D-FjhahniFm0VbFRm8ysyb85h29wXg@mail.gmail.com> <20161128133936.7e815c9a@fabiankeil.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Indeed... this sounds like it, and exactly the path I was going to look down. On Mon, Nov 28, 2016 at 7:39 AM, Fabian Keil <freebsd-listen@fabiankeil.de> wrote: > David Cross <dcrosstech@gmail.com> wrote: > > > So, narrowing this down, I think it has something to do with geli swap > > (since I can easily reproduce it with geli swap, but have yet to > > reproduce it without).. and I have a bit of a convoluted way almost > > anyone can reproduce it with bhyve. (Note, I haven't been able to get a > > crashdump, since apparently the VM system being locked up prevents that, > > but with watchdogd, I have been able to get into DDB) > > Sounds familiar: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209759 > > Fabian >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAM9edeMz7xu5TXajTAJ9RxTDt9gi1hBq5RAyNxFb2kNs6P2gXw>