Date: Wed, 17 Aug 2011 17:01:05 -0700 From: Chip Camden <sterling@camdensoftware.com> To: freebsd-stable@FreeBSD.org Subject: Re: panic: spin lock held too long (RELENG_8 from today) Message-ID: <20110818000105.GC2489@libertas.local.camdensoftware.com> In-Reply-To: <20110817210446.GA49737@icarus.home.lan> References: <20110707082027.GX48734@deviant.kiev.zoral.com.ua> <4E159959.2070401@sentex.net> <4E15A08C.6090407@sentex.net> <20110818.023832.373949045518579359.hrs@allbsd.org> <20110817175201.GB1973@libertas.local.camdensoftware.com> <20110817210446.GA49737@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
--VywGB/WGlW4DM4P8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoth Jeremy Chadwick on Wednesday, 17 August 2011: > >=20 > > I'm also getting similar panics on 8.2-STABLE. Locks up everything and= I > > have to power off. Once, I happened to be looking at the console when = it > > happened and copied dow the following: > >=20 > > Sleeping thread (tif 100037, pid 0) owns a non-sleepable lock > > panic: sleeping thread > > cpuid=3D1 >=20 > No idea, might be relevant to the thread. >=20 > > Another time I got: > >=20 > > lock order reversal: > > 1st 0xffffff000593e330 snaplk (snaplk) @ /usr/src/sys/kern/vfr_vnops.c:= 296 > > 2nd 0xffffff0005e5d578 ufs (ufs) @ /usr/src/sys/ufs/ffs/ffs_snapshot.c:= 1587 > >=20 > > I didn't copy down the traceback. >=20 > "snaplk" refers to UFS snapshots. The above must have been typed in > manually as well, due to some typos in filenames as well. >=20 > Either this is a different problem, or if everyone in this thread is > doing UFS snapshots (dump -L, mksnap_ffs, etc.) and having this problem > happen then I recommend people stop using UFS snapshots. I've ranted > about their unreliability in the past (years upon years ago -- still > seems valid) and just how badly they can "wedge" a system. This is one > of the many (MANY!) reasons why we use rsnapshot/rsync instead. The > atime clobbering issue is the only downside. >=20 If I'm doing UFS snapshots, I didn't know it. Yes, everything was copied manually because it only displays on the console and the keyboard does not respond after that point. So I copied first to paper, then had to decode my lousy handwriting to put it in an email. Sorry for the scribal errors. --=20 =2EO. | Sterling (Chip) Camden | http://camdensoftware.com =2E.O | sterling@camdensoftware.com | http://chipsquips.com OOO | 2048R/D6DBAF91 | http://chipstips.com --VywGB/WGlW4DM4P8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJOTFZBAAoJEIpckszW26+RRtsH/jPEUungeBO9a3idYOTECrqg BsEo0zyyyz76sd3bkyVVx5QNRlfAygoxhReUsD1r6GC9QhapR0m91qUD1bYNK3yv wCxKp3bCOCbh4HOG5efwDFBKisfKLRKjyQp2SQ7d2R+RHO6fsk9VHvrPS6LQ3skH AJ0fvCUd+0GCpvKsLHzV+MqrGJpiMdz2dwPpo+Jwv+EzGZ8H2gJwrzZD4OUAkGC4 gXBqT+YTiJLNQIOr0dteYO037yymUxYRqB9q8lbNcl6RKp3s1NHQWUU3IhDJjeSL 5qTCr9j9wSOomxBCskWXsy6XzEdmc3dzMPBS95D5zbZWDYxl5JXFAE8hLKanWkw= =cyZM -----END PGP SIGNATURE----- --VywGB/WGlW4DM4P8--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110818000105.GC2489>