From owner-freebsd-current@FreeBSD.ORG Wed Jul 18 14:36:39 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 84CDC16A59E; Wed, 18 Jul 2007 14:36:39 +0000 (UTC) (envelope-from yoichi@FreeBSD.org) Received: from alcoholic.geiin.org (x006014.ppp.asahi-net.or.jp [122.249.6.14]) by mx1.freebsd.org (Postfix) with ESMTP id 46F1A13C428; Wed, 18 Jul 2007 14:36:39 +0000 (UTC) (envelope-from yoichi@FreeBSD.org) Received: from tequila.local-net.geiin.org (tequila-air.local-net [192.168.1.6]) by alcoholic.geiin.org (Postfix) with ESMTP id 2869E1DEE3; Wed, 18 Jul 2007 23:10:03 +0900 (JST) Date: Wed, 18 Jul 2007 23:10:05 +0900 Message-ID: <87fy3l3irm.wl%yoichi@FreeBSD.org> From: Yoichi Nakayama To: FreeBSD-gnats-submit@FreeBSD.org In-Reply-To: <20061109112035.GA1722@kobe.laptop> References: <200611062349.kA6NnbCG051817@www.freebsd.org> <20061107192218.GB1624@kobe.laptop> <878ximm418.wl%yoichi@FreeBSD.org> <20061109112035.GA1722@kobe.laptop> User-Agent: Wanderlust/2.15.5 (Almost Unreal) EMIKO/1.14.1 (Choanoflagellata) FLIM/1.14.8 (=?ISO-2022-JP?B?GyRCO00+chsoQg==?=) APEL/10.7 Emacs/22.1.50 (i686-pc-linux-gnu) MULE/5.0 (=?ISO-2022-JP?B?GyRCOC1MWhsoQg==?=) Organization: FreeBSD.org X-Face: wLZki+KbGjgKe0,<&3g*rA|R**vj[a8L%[v]ecJh1L(Uqm|LBx; v7Nq7n%?0d.aS]F#[~C\!{m?m,C&#U5}$_pZvBR>5VmX1Ol0`P\M-U8`sUF<5Quj'z&zzW8r|Zl9#W7Wut3duYzpKrP{n+AbarKtJ!i"Al7]P; -?[=iBZa*]r=>C':0~JECx]IH+RXq=/hUX}MB9e]oQKBxsDd/ MIME-Version: 1.0 (generated by EMIKO 1.14.1 - "Choanoflagellata") Content-Type: text/plain; charset=US-ASCII Cc: freebsd-current@freebsd.org Subject: Re: kern/105229: panic in sync_fsync 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, 18 Jul 2007 14:36:39 -0000 At Thu, 9 Nov 2006 13:20:35 +0200, Giorgos Keramidas wrote: > > On 2006-11-08 23:00, Yoichi Nakayama wrote: > >At Tue, 7 Nov 2006 21:22:18 +0200, > >Giorgos Keramidas wrote: > >> Hi NAKAYAMA-san :) > >> > >> In general, we handle CURRENT problems in the freebsd-current mailing > >> list, instead of opening problem reports. > > > > I'm sorry for my mistake. > > Nothing to worry about :) > > >> The build from `2006.11.07.05.51.41', as I said seems to work fine. > >> > >> Can you try re-syncing your source tree to see if a newer commit has > >> fixed this in CURRENT? > > > > Thanks for your suggestion. I've already synced it to current > > yesterday (after the time vfs_subr.c Revision 1.691 was committed at > > Nov 7 19:45:05 2006 UTC), and I'm keeping it running. > > > > I'll post a report to freebsd-current list after one week trial. > > I've met the same problem for some number of times after 2-7 days run. > > Cool! Unfortunately, I don't leave my laptop running for so long. > If this is related to staying up several days, I wouldn't notice it > easily :) I reproduce the problem with configuration: - 512MBx2 on two slots - 512MBx1 on one of the slots (tried with both RAMs) and then I tried with Windows XP and get similar result (rebooted after a few weeks). Although no problem occurred with - 512MBx1 on another slot (tried with both RAMs) Finally, I conclude the problem is in one of the memory slot on my motherboard (ASUS N4L-VM DH). Please close this PR. I'm sorry for bothering you. -- Yoichi NAKAYAMA