Date: Mon, 27 Jul 2009 14:31:58 +0200 From: Attilio Rao <attilio@freebsd.org> To: barbara <barbara.xxx1975@libero.it> Cc: FreeBSD-stable <FreeBSD-stable@freebsd.org>, bug-followup <bug-followup@freebsd.org> Subject: Re: kern/134584: [panic] spin lock held too long Message-ID: <3bbf2fe10907270531u121bacb9y17d5bb624b3bc23b@mail.gmail.com> In-Reply-To: <KNDMU8$8EFE8DA350FF14C54F1F3D61C7265B47@libero.it> References: <KNDMU8$8EFE8DA350FF14C54F1F3D61C7265B47@libero.it>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/7/26 barbara <barbara.xxx1975@libero.it>: > It happened again, on shutdown. > As the previous time, it happened after a high (for a desktop) uptime and, if it could matter, after running net-p2p/transmission-gtk2 for several hours. > I don't know if it's related, but often quitting transmission, doesn't terminate the process. Sometimes it end after several minutes the gui exited, sometimes it's still running after hours. > I've noticed it as the destination folder is on a manually mounted device and I can't umount it as fstat reports the device used by a transmission process. > So I often have to kill it. > This happened both the time I had this kind of panic. What hw is that? How many CPUs does it have? Attilio -- 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?3bbf2fe10907270531u121bacb9y17d5bb624b3bc23b>