Date: Thu, 17 Apr 2008 20:03:18 -0400 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Pascal Hofstee <caelian@gmail.com> Cc: gnome@freebsd.org Subject: Re: CURRENT, devbuf memory allocation and hald Message-ID: <1208476998.80837.25.camel@shumai.marcuscom.com> In-Reply-To: <d8a0b7620804170403l4f233aben82ff9803aebc33a8@mail.gmail.com> References: <d8a0b7620804170403l4f233aben82ff9803aebc33a8@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-HniUDH/GPZ0NqwXa78Zk Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2008-04-17 at 13:03 +0200, Pascal Hofstee wrote: > Hi, >=20 > After updating my CURRENT system i noticed that my system started to > completely break down after a while (ususally after coming home from a > day at college) with the console spewing loads of messages about > ata-subsystem(s) being unable to allocate any memory, existing shells > no longer being able to fork new subprocesses because of memory > problems etc. Initially i had assumed it might bave been a rare side > effect of the recent commits to the ATA-system, at least one of which > Soren mentioned fixed a couple of bogons. >=20 > Now after some additionial investigation i have come to the > realisation that the most likely source of the problem was because > according to vmstat -m the "InUse" statistics for the memory type > "devbuf" were consistently increasing by about 140k over a 10 second > time peroid. I decided to shoot down any daemons originating from > port-installed software to ensure the problem was indeed caused by > some part of the base system and not some 3rd party influence and i > managed to trace the problem down to hald. >=20 > Whenever i halted hald the increase in devbuf-usage would halt (not > decline simply stay at the same value), and as soon as i started hald > again the increase would resume with the 140k/10s ratio until hald was > stopped again. >=20 > If anyone in the FreeBSD-GNOME team might have any idea with regards > to what may be causing this problem i am more than happy to cooperate > in trying to resolve this issue. >=20 > The system in question is an AMD Athlon64 3800+, 2GB RAM using an MSI > K9N-Neo (nVidia MCP55-based mainboard) running FreeBSD/i386 > 8.0-CURRENT as of April 16th late afternoon CET. I just upgraded to: FreeBSD lasagna.marcuscom.com 8.0-CURRENT FreeBSD 8.0-CURRENT #38: Thu Apr 17 19:26:21 EDT 2008 marcus@lasagna.marcuscom.com:/usr/obj/usr/src/sys/LASAGNA amd64 And I can no longer reproduce. Running -CURRENT from yesterday did exhibit the problem, though. Joe --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-HniUDH/GPZ0NqwXa78Zk Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEABECAAYFAkgH5UYACgkQb2iPiv4Uz4fO9QCggScV4Jgfi1gz9InWgYmQwhQR HbAAoJ38RScAzuEEsX4n7ocFJsk/yREJ =yA3C -----END PGP SIGNATURE----- --=-HniUDH/GPZ0NqwXa78Zk--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1208476998.80837.25.camel>