From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 14:43:53 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2BBE1B41; Sun, 7 Dec 2014 14:43:53 +0000 (UTC) Received: from puchar.net (puchar.net [188.252.31.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BDE90A92; Sun, 7 Dec 2014 14:43:52 +0000 (UTC) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.14.9/8.14.9) with ESMTP id sB7Ehnig070413; Sun, 7 Dec 2014 15:43:50 +0100 (CET) (envelope-from wojtek@puchar.net) Date: Sun, 7 Dec 2014 15:43:45 +0100 (CET) From: Wojciech Puchar X-X-Sender: wojtek@laptop To: Oliver Pinter Subject: Re: 10.1-STABLE one week old from svn - random hangs In-Reply-To: Message-ID: References: <54843BB3.2000602@FreeBSD.org> <548448B1.20907@freebsd.org> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (puchar.net [10.0.1.1]); Sun, 07 Dec 2014 15:43:50 +0100 (CET) Cc: FreeBSD Hackers , Alfred Perlstein , lev@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 14:43:53 -0000 yes i do use geli. On Sun, 7 Dec 2014, Oliver Pinter wrote: > Guys, do you have enabled GELI or encrypted partition? > > On Sun, Dec 7, 2014 at 2:37 PM, Wojciech Puchar wrote: >> how to get via svn or other means sources of 10*-STABLE from 18.06.2014? >> >> to get back to working system. >> >> >> On Sun, 7 Dec 2014, Wojciech Puchar wrote: >> >>> no crashdump. system does not panic >>> so i cannot do this >>> >>> On Sun, 7 Dec 2014, Alfred Perlstein wrote: >>> >>>> Can you enable crashdumps please and then send a traceback? >>>> >>>> >>>> https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html >>>> >>>> These two are most helpful: >>>> >>>> https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html#kerneldebug-obtain >>>> >>>> https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html >>>> >>>> >>>> On 12/7/14, 3:36 AM, Lev Serebryakov wrote: >>>>> >>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>> Hash: SHA512 >>>>> >>>>> On 07.12.2014 12:40, Wojciech Puchar wrote: >>>>> >>>>>> The problem. At random moment system I/O stops. If you are running >>>>>> top at this moment, there are lots of prosesses stalled in vnread >>>>>> or biord. network keeps running, processes that doesn't need I/O >>>>>> still runs. >>>>>> >>>>>> top often reports at least 10MB free memory. >>>>>> >>>>>> seems like a deadlock. Anyone know that problem. How to trace it >>>>>> down? >>>>> >>>>> Looks like I have same problem sometimes. And you could not run any >>>>> new process, you could not login on console, but you could switch >>>>> virtual consoles & if "top" is running on one of them, it doesn't hang >>>>> itself, right? >>>>> >>>>> I get this typically when "svnsync" synchronize my local FreeBSD repo >>>>> mirror and after that FS (UFS2 with SUJ) with my repo is heavily >>>>> damaged. >>>>> >>>>> - -- // Lev Serebryakov AKA Black Lion >>>>> -----BEGIN PGP SIGNATURE----- >>>>> Version: GnuPG v2.0.22 (MingW32) >>>>> >>>>> iQJ8BAEBCgBmBQJUhDuzXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w >>>>> ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF >>>>> QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePuI8QANK2Xw8oUrApeMMsCqWs6mGo >>>>> NsijmCLWhTBNGLszEk1pD/GQrqVZRIm8qmn3GReknYZzMdiYYc89b+9ou5nZnQfk >>>>> +j+ngdBWNTGkxBa5qjBTLSZm2yYZ70rxxIUs4HualK6kgF2CLlLA9XEWlm+pBtCG >>>>> ZaBWCP/vH5mBvLk+YUOtZtPlMhC7ckNe4Uq13gSkZRaZBtHy0WZ+1nqZz7Xi1nFx >>>>> XBAlcJMUi4c9EAtBJGovKAVXjkIk6TINhDF+76J8aQlL4drliLvRZQjCnulbQecc >>>>> VMQP4hFKghmdH1DTSwPX4R44hZd7TF1CW7FNT/qZLyPuZHIcwVYOsH+5gq95liCP >>>>> CDCt5N8dF/q8wgyMGRyHv8PCdOA9MK8/6PtZY2KAXdIkfPZ6u0bTMHXPWb3qDWPX >>>>> kdYPIKYZ5rzF3oY6Yuk6Mn4OIJ+Aww5FhNQ5ad4IkUty7p06JMt+sw9X9VEbyZYC >>>>> ejQ96Tquy9Si2TnjZZbtSySvUZAlJxDT5z5eBvOh9BoexEsrKG8pV1nMv3LMgat8 >>>>> 0kKxWTXtkD/NPO4+FGFasV/lSgteXWGjRv3s+g1cqmCSWRn4ed8xhFcLoTzbJLQf >>>>> a5E1LGIDGJPsARmfyD1FF1RS/kYdfWlG7BA6mg91zExZpuuS4oFexh4YaAbfjTe/ >>>>> oeXgB3qxqhPtvfDmUm+X >>>>> =R88v >>>>> -----END PGP SIGNATURE----- >>>>> _______________________________________________ >>>>> freebsd-hackers@freebsd.org mailing list >>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>>>> To unsubscribe, send any mail to >>>>> "freebsd-hackers-unsubscribe@freebsd.org" >>>>> >>>> >>>> _______________________________________________ >>>> freebsd-hackers@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>>> To unsubscribe, send any mail to >>>> "freebsd-hackers-unsubscribe@freebsd.org" >>>> >>>> >>> _______________________________________________ >>> freebsd-hackers@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >>> >>> >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > >