Date: Sat, 20 Feb 2010 23:19:39 +0100 From: Attilio Rao <attilio@freebsd.org> To: Brandon Gooch <jamesbrandongooch@gmail.com> Cc: freebsd-fs@freebsd.org, freebsd-emulation@freebsd.org, stable-list freebsd <freebsd-stable@freebsd.org> Subject: Re: ZFS and sh(1) panic: spin lock [lock addr] (smp rendezvous) held by [sh(1) proc tid] too long Message-ID: <3bbf2fe11002201419v52b249ccg8d82c8ae747cf318@mail.gmail.com> In-Reply-To: <179b97fb1001270941m2d8e9c8au20abc798c16b9c11@mail.gmail.com> References: <179b97fb1001270941m2d8e9c8au20abc798c16b9c11@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2010/1/27 Brandon Gooch <jamesbrandongooch@gmail.com>: > The machine, a Dell Optiplex 755, has been locking up recently. The > situation usually occurs while using VirtualBox (running a 64-bit > Windows 7 instance) and doing anything else in another xterm (such as > rebuilding a port). =C2=A0I've been unable to reliably reproduce it (I'm = in > an X session and the machine will not panic "properly"). > > However, while rebuilding Xorg today at ttyv0 and runnning > VBoxHeadless on ttyv1, I managed to trigger what I believe is the > lockup. > > I've attached a textdump in hopes that someone may be able to take a > look and provide clues or instruction on debugging this. I think that jhb@ saw a similar problem while working on nVidia driver or the like. Not sure if he made any progress to debug this. Attilio --=20 Peace can only be achieved by understanding - A. Einstein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3bbf2fe11002201419v52b249ccg8d82c8ae747cf318>