From owner-freebsd-stable@FreeBSD.ORG Tue Dec 28 02:27:06 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EEE4016A4CE for ; Tue, 28 Dec 2004 02:27:06 +0000 (GMT) Received: from maxlor.mine.nu (c-213-160-32-54.customer.ggaweb.ch [213.160.32.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54D5043D5A for ; Tue, 28 Dec 2004 02:27:06 +0000 (GMT) (envelope-from benlutz@datacomm.ch) Received: from localhost (localhost [127.0.0.1]) by maxlor.mine.nu (Postfix) with ESMTP id D04C624A; Tue, 28 Dec 2004 03:27:04 +0100 (CET) Received: from maxlor.mine.nu ([127.0.0.1]) by localhost (midgard [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 69146-02; Tue, 28 Dec 2004 03:27:04 +0100 (CET) Received: from merlin.intranet (merlin.intranet [10.0.0.16]) by maxlor.mine.nu (Postfix) with ESMTP id 0BC0C43; Tue, 28 Dec 2004 03:27:04 +0100 (CET) From: Benjamin Lutz To: Peter Jeremy Date: Tue, 28 Dec 2004 03:27:00 +0100 User-Agent: KMail/1.7.2 References: <200412260814.53592.benlutz@datacomm.ch> <20041228013844.GC7189@cirb503493.alcatel.com.au> In-Reply-To: <20041228013844.GC7189@cirb503493.alcatel.com.au> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3367878.W7ad2OSuXX"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412280327.03752.benlutz@datacomm.ch> X-Virus-Scanned: by amavisd-new at maxlor.mine.nu cc: freebsd-stable@freebsd.org Subject: Re: slow system freeze - data X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 02:27:07 -0000 --nextPart3367878.W7ad2OSuXX Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello Peter, > The info you dumped shows that there's a filesystem deadlock on > ad4s1f. In case you haven't guessed, that'd be my /usr. > Unfortunately, it's not clear (to me) where to go next. Printing the > locked vnodes might help but that's not easy to do without gdb. You mean that's the point where I need serial console access? I hope to=20 have that running after the holidays. > >The first app that froze as far as I could tell was xmms. > > Actually, the locks suggest that the problem started with pid 678 - > kdeinit. This is unlikely to be Well, xmms is just the first app where it became apparent :) PID 678 is really kded (at least it is at the moment - It is very likely=20 it was then too, since these low PIDs seem to generally be assigned the=20 same way with each boot). kded appears to be some CORBA-related tool used=20 by KDE. Btw, is my assumption that this is a kernel problem, not a problem with=20 any of my applications, correct? Anyway, many thanks for your help and insight so far, it is appreciated. Greetings Benjamin --nextPart3367878.W7ad2OSuXX Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD4DBQBB0MR3gShs4qbRdeQRAtiYAJ418FNV/TcMhH3WHpTOXMSU2jKNXQCXc/us hWLM/9CS3hMfXbKzN5XJcg== =HlTk -----END PGP SIGNATURE----- --nextPart3367878.W7ad2OSuXX--