看板 DFBSD_bugs 關於我們 聯絡資訊
Aleksej Lebedev <a@umc8.ru> added the comment: On Sun, 14 Nov 2010 16:46:54 +0000, "Matthew Dillon \(via DragonFly issue tracker\)" <bugs@crater.dragonflybsd.org> wrote: > Matthew Dillon <dillon@apollo.backplane.com> added the comment: The first > thing to do is to compile up the latest 2.8.x kernel in the release branch. > Your freezes are probably related to a console deadlock that we have fixed. > On swap use and memory use, we don't have enough information. 90% of the bug > reports related to memory use turn out to be misinterpretations of system > statistics, since DragonFly (like all BSDs) use all available free memory to > cache file data and drop the cache as memory is needed. If swap is growing > unbounded over time and you are seeing constant paging activity then it could > be a runaway process running on your machine, which you should be able to > locate using miscellanious system tools such as 'ps axl'. > -Matt Thank you for your answer. I am alreay using v2.8.2.16.gfc7bf0-RELEASE. Isn't it the latest 2.8.x kernel? Maybe you are right about misinterpretation of memory statistics, because what I see in "top" now is: == top == Memory: 2978M Active, 1482M Inact, 1171M Wired, 215M Cache, 605M Buf, 62M Free == top == Total amount is 6513M which is more than I have: == dmesg.boot == real memory = 6440680448 (6142 MB) avail memory = 6037917696 (5758 MB) == dmesg.boot == So now I'm not sure whether the number less than 6G indicates that anything is wrong ether. Anyway I started to collect memory and swap statistics with munin, so that next time it hangs I will see what happened in details. -- Aleksej Lebedev ---------- status: unread -> chatting _____________________________________________________ DragonFly issue tracker <bugs@lists.dragonflybsd.org> <http://bugs.dragonflybsd.org/issue1908> _____________________________________________________