From owner-freebsd-current Thu Aug 22 19:19:54 2002 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 88C1E37B400 for ; Thu, 22 Aug 2002 19:19:51 -0700 (PDT) Received: from sbk-gw.sibnet.ru (sbk-gw.sibnet.ru [217.70.96.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9D1843E7B for ; Thu, 22 Aug 2002 19:19:49 -0700 (PDT) (envelope-from stranger@sberbank.sibnet.ru) Received: from sbk-gw.sibnet.ru (localhost.sibnet.ru [127.0.0.1]) by sbk-gw.sibnet.ru (8.12.5/8.12.5) with ESMTP id g7N2JYsL044886; Fri, 23 Aug 2002 09:19:34 +0700 (NOVST) (envelope-from stranger@sberbank.sibnet.ru) Received: from localhost (stranger@localhost) by sbk-gw.sibnet.ru (8.12.5/8.12.5/Submit) with ESMTP id g7N2JWEj044883; Fri, 23 Aug 2002 09:19:32 +0700 (NOVST) X-Authentication-Warning: sbk-gw.sibnet.ru: stranger owned process doing -bs Date: Fri, 23 Aug 2002 09:19:32 +0700 (NOVST) From: "Maxim M. Kazachek" X-X-Sender: stranger@sbk-gw.sibnet.ru To: Soeren Schmidt Cc: Martin Blapp , Don Lewis , , , , Subject: Re: Memory corruption in CURRENT In-Reply-To: <200208220909.g7M99NcS077303@freebsd.dk> Message-ID: <20020823083920.R39441-100000@sbk-gw.sibnet.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I saw SIG4 on gnome-sawfish on Compaq iPAQ C700/i815E/320Mb RAM It just happens sometimes Sincerely, Maxim M. Kazachek mailto:stranger@sberbank.sibnet.ru mailto:stranger@fpm.ami.nstu.ru On Thu, 22 Aug 2002, Soeren Schmidt wrote: >It seems Martin Blapp wrote: >> >> Hi all, >> >> I suspect all the SIG4 and SIG11 problems we see are due >> memory corruption in CURRENT. >.... >> > The file is correct after a reboot, so the corruption was limited to the >> > copy cached in RAM. >> >> Thats memory corruption. I'm also not able anymore >> to make 10 buildworlds (without -j, that triggers >> panics in pmap code). >> >> Bye the way, I'm experiencing this since about 4-5 months. >> >> All hackers, please help to track this down. > >Hmm, I haven't seen this at all, but I've just started buildworld loops on >two machines here, but I normally do at least a couble buildworlds a day >and I havn't notice problems like the above (but plenty of bad commits etc). > >However, this kind of problem in most cases spells bad HW to me, >ie subspec RAM, poor powersupply, badly cooled CPU, overclocking etc etc... > >-Søren > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message