From owner-freebsd-current@FreeBSD.ORG Wed Apr 16 19:40:48 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37283106564A for ; Wed, 16 Apr 2008 19:40:48 +0000 (UTC) (envelope-from caelian@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.154]) by mx1.freebsd.org (Postfix) with ESMTP id BB65C8FC31 for ; Wed, 16 Apr 2008 19:40:47 +0000 (UTC) (envelope-from caelian@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so2802583fgg.35 for ; Wed, 16 Apr 2008 12:40:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject:message-id:x-mailer:mime-version:content-type:content-transfer-encoding; bh=bjVIWUcG78GD+xL9yMTfhmLpFRiQ5E5AHXRLlTtqCk0=; b=I6kz3liPM7kARTTKyIRQIPgGeG9oLD3zBz9ujOtiwmvPRWB25G/v0Sk4E7bl0PLacBfu2FmhP8XOsYVnSnwjTGjxi2NnT9HRBOrtgJope0RPKRXl3W7ZcrhY2PVBIPzZpnKeR3bpFRKJhAbTM7MI70kcYbX/rb88yLcuuZovQ/E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:x-mailer:mime-version:content-type:content-transfer-encoding; b=LYgBIxu5hWXaBW1QvKfUnpt0PqXNR+JUv7I3JWVEjHjTHohIa/jvD4BD47BPA/5KM/l0F5Zc60RMLKcW2zHGocMf5x1fvDDFSh2eui6rzS9twbYrNquUiMZDKU9xxGzfdqzkYayYxZ07mvrreKK2T6KSRcr2IJP/5L6fokgnwwI= Received: by 10.86.30.9 with SMTP id d9mr675790fgd.77.1208373351865; Wed, 16 Apr 2008 12:15:51 -0700 (PDT) Received: from nebuchadnezzar ( [87.151.46.173]) by mx.google.com with ESMTPS id e20sm8137515fga.1.2008.04.16.12.15.50 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 16 Apr 2008 12:15:51 -0700 (PDT) Date: Wed, 16 Apr 2008 21:15:44 +0200 From: Pascal Hofstee To: current@freebsd.org Message-ID: <20080416211544.62f5bd28@nebuchadnezzar> X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.9; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: potential malloc problem with recent ATA commits ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Apr 2008 19:40:48 -0000 Hi, Since i recently updated my CURRENT system from a March 26 build to a fresh CURRENT i noticed that after a while the system seems to run itself into a state wherein it is entirely out of memory. The problem has presented itself so far during the last couple of days when i come back home from a day at college to find the console spewing tons of messages about (iirc) ata3/ata6 being unable to alloc memory, shell processes that were still running being unable to fork new processes because of memory shortage etc. The system in question is an AMD Athlon64 3800+ using an MSI K9N-Neo (nVidia MPC55-based) mainboard, with 2 GB RAM and 4 GB SWAP space. The system has been running fine on the March 26 kernel but so far both an April 12 as well as an April 16 kernel seem to exhibit the memory problems. Considering a large batch of changes to the ATA system seem to have been commited around April 10th and a.o. the console spamming about ata-subsystem components having malloc problems i was wondering if perhaps the recent ATA changesets might be responsible for this behaviour. Any suggestions on how to proceed from here ? With kind regards, Pascal Hofstee