Date: Mon, 8 Dec 2014 08:38:08 +0100 (CET) From: Wojciech Puchar <wojtek@puchar.net> To: Alfred Perlstein <bright@mu.org> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org>, Alfred Perlstein <alfred@freebsd.org>, "lev@FreeBSD.org" <lev@FreeBSD.org> Subject: Re: 10.1-STABLE one week old from svn - random hangs Message-ID: <alpine.BSF.2.11.1412080837050.6093@laptop> In-Reply-To: <DDCCAEEB-0850-45BF-B9A5-B72E27090DB2@mu.org> References: <alpine.BSF.2.11.1412071035550.697@laptop> <54843BB3.2000602@FreeBSD.org> <548448B1.20907@freebsd.org> <alpine.BSF.2.11.1412071425260.661@laptop> <DDCCAEEB-0850-45BF-B9A5-B72E27090DB2@mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
already sent you kernel messages with debugging diags etc. enabled. lots of them and crashes easily repeatable. got back to 10-STABLE from 2014.06.06 + manually applied patched from security advisories after. NONE of errors happens, no crashes so far. On Sun, 7 Dec 2014, Alfred Perlstein wrote: > > >> On Dec 7, 2014, at 5:25 AM, Wojciech Puchar <wojtek@puchar.net> wrote: >> >> no crashdump. system does not panic >> so i cannot do this > > That is actually better as you can run ddb scripts or if you what you can force a crash. > > Do sysctl -a |grep panic > > > Then set the sysctl node to panic. > > >> >>> 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" > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.11.1412080837050.6093>