From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 22:12:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C194E16A4CE for ; Wed, 17 Nov 2004 22:12:38 +0000 (GMT) Received: from av7-2-sn1.fre.skanova.net (av7-2-sn1.fre.skanova.net [81.228.11.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 166A343D54 for ; Wed, 17 Nov 2004 22:12:36 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av7-2-sn1.fre.skanova.net (Postfix, from userid 502) id 3F86338106; Wed, 17 Nov 2004 23:12:35 +0100 (CET) Received: from smtp3-1-sn1.fre.skanova.net (smtp3-1-sn1.fre.skanova.net [81.228.11.163]) by av7-2-sn1.fre.skanova.net (Postfix) with ESMTP id 3053A37EA6 for ; Wed, 17 Nov 2004 23:12:35 +0100 (CET) Received: from sentinel (h130n1fls11o822.telia.com [213.64.66.130]) by smtp3-1-sn1.fre.skanova.net (Postfix) with ESMTP id 1C6FD37E46 for ; Wed, 17 Nov 2004 23:12:35 +0100 (CET) From: "Daniel Eriksson" To: Date: Wed, 17 Nov 2004 23:12:31 +0100 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 Thread-Index: AcTMlYq7bsZgjuZ/Qn2QnvJiCjO8NgAXIgwg In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Subject: RE: uma_zfree_internal crash, if_em related? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 17 Nov 2004 22:12:38 -0000 I wrote: > After upgrading my 6-CURRENT box to 2004.11.14.16.00.00 (and also > 2004.11.16.19.15.00), I have encountered this crash twice in > 24 hours. [...] > Stopped at uma_zfree_internal+0xcc: movl %edx,0(%eax) It is possible that this error was hardware related. Earlier today one stick of RAM went completely nuts and had to be replaced. The errors I reported could have been early effects of the RAM going bad. If I see the same problem again I'll post another report in this thread. /Daniel Eriksson