From owner-freebsd-current@FreeBSD.ORG Tue Nov 27 14:24:22 2007 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 CD5FB16A41B for ; Tue, 27 Nov 2007 14:24:22 +0000 (UTC) (envelope-from matej.kubik@dial.sk) Received: from saratoga.zuikaku.org (unknown [IPv6:2001:1ba0::20a:e4ff:fe5a:25bb]) by mx1.freebsd.org (Postfix) with ESMTP id 5FAEE13C467 for ; Tue, 27 Nov 2007 14:24:22 +0000 (UTC) (envelope-from matej.kubik@dial.sk) Received: from saratoga.zuikaku.org (localhost [127.0.0.1]) by saratoga.zuikaku.org (8.14.1/8.14.1) with ESMTP id lAREOJkR003368 for ; Tue, 27 Nov 2007 15:24:19 +0100 (CET) (envelope-from matej.kubik@dial.sk) Received: (from kockac@localhost) by saratoga.zuikaku.org (8.14.1/8.14.1/Submit) id lAREOJkh003367 for current@FreeBSD.ORG; Tue, 27 Nov 2007 15:24:19 +0100 (CET) (envelope-from matej.kubik@dial.sk) X-Authentication-Warning: saratoga.zuikaku.org: kockac set sender to matej.kubik@dial.sk using -f Date: Tue, 27 Nov 2007 15:24:19 +0100 From: "'Kockac' Matej Kubik" To: current@FreeBSD.ORG Message-ID: <20071127142419.GA2999@saratoga.zuikaku.org> References: <512683.5780.qm@web63911.mail.re1.yahoo.com> <474BCA95.6000403@deepcore.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <474BCA95.6000403@deepcore.dk> User-Agent: Mutt/1.4.2.3i X-Mailman-Approved-At: Tue, 27 Nov 2007 14:38:45 +0000 Cc: Subject: Re: Any successful installs on a Broadcom HT1000 chipset? 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: Tue, 27 Nov 2007 14:24:22 -0000 On Tue, Nov 27, 2007 at 08:43:17AM +0100, S?ren Schmidt wrote: > Looks like a pattern, something outside of ATA also caused HW issues on > some Promise controllers to appear in this period. I'd say so too. In my case the cause seems to be clear - I'm running an older version of 7-current for about 2 months (with frequent reboots) and no sign of file corruption. (Newer versions are usually not able to run at even /bin/sh on my system.) I'm able to pinpoint the exact patch that causes these problems _for me_ - it's a VM patch (new physical memory allocator) from June the 16th. Unfortunately I can neither grant access to the machine for debugging nor send in another board (I only have one) but I can provide debugging information or test something... By the way, I think it would be interesting to know if others do have the problems even with older -current. Matej Kubik