Date: Sat, 23 May 2009 12:40:29 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Stefan Bethke <stb@lassitu.de> Cc: Attilio Rao <attilio@freebsd.org>, "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: spinlock held too long on reboot Message-ID: <alpine.BSF.2.00.0905231239230.75344@fledge.watson.org> In-Reply-To: <226F1AFF-45D8-4E4C-BE7F-D2EDC35EC8F6@lassitu.de> References: <746CE32B-BCF8-460A-982D-25341554E8FD@lassitu.de> <3bbf2fe10905221234k12c45932gb1e197143cd74b5d@mail.gmail.com> <FCCBA84A-1B9E-4C63-BD42-452565BE9292@lassitu.de> <20090522230333.X72053@maildrop.int.zabbadoz.net> <3bbf2fe10905221846q7fd1fe9cue744de61f9e12612@mail.gmail.com> <226F1AFF-45D8-4E4C-BE7F-D2EDC35EC8F6@lassitu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 23 May 2009, Stefan Bethke wrote: > I've only seen this once. If I should encounter it again, is there > something you'd like me to look at? I've now seen this twice, both times on SMP VMWare installations. I theorized that perhaps it was because one of the virtual CPUs wasn't time sliced for over our spinlock wait threshold due to load in the host OS, but if it's also being seen on real hardware it's presumably not that. Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0905231239230.75344>