Date: Wed, 21 Dec 2011 02:36:36 GMT From: Oleg Ginzburg <olevole@olevole.ru> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/163493: FreeBSD 9x amd64 unstable while work with RAM Message-ID: <201112210236.pBL2aaNA064874@red.freebsd.org> Resent-Message-ID: <201112210240.pBL2e94l059720@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 163493 >Category: kern >Synopsis: FreeBSD 9x amd64 unstable while work with RAM >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Dec 21 02:40:09 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Oleg Ginzburg >Release: 9.0-RC3 >Organization: >Environment: >Description: I have found out stable lag of systems amd64 at employment of all memory. This problem isn't reproduced on i386 ( I have checked up on FreeBSD-current on my Asus EE PC Book - problems aren't present. Also has checked up in VirtualBox with FreeBSD 9.0-RC3/i386. Both systems has written "No space left on device" at my method of testing (see below)) Also, in the absence of any special tuning options in sysctl.conf and loader.conf (like maxusers etc) I see on many systems incorrect value vm.kmem_size_max (amd64 only). The unstable condition remains when i set vm.kmem_size\* equal or less then the hw.physmem >How-To-Repeat: 1) mdconfig -a -t malloc -s Ng Where num N is greater then RAM ( the problem also is actual while N < physmem+swap ) 2) dd if=/dev/random of=/dev/md0 bs=10m 3) watch on the top. At exhaustion Free memory the problem is comes >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201112210236.pBL2aaNA064874>