From nobody@FreeBSD.org  Mon Nov  6 23:49:41 2006
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D893116A403
	for <freebsd-gnats-submit@FreeBSD.org>; Mon,  6 Nov 2006 23:49:41 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D0A6543D7C
	for <freebsd-gnats-submit@FreeBSD.org>; Mon,  6 Nov 2006 23:49:37 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id kA6NnbWp051819
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 6 Nov 2006 23:49:37 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id kA6NnbCG051817;
	Mon, 6 Nov 2006 23:49:37 GMT
	(envelope-from nobody)
Message-Id: <200611062349.kA6NnbCG051817@www.freebsd.org>
Date: Mon, 6 Nov 2006 23:49:37 GMT
From: Yoichi NAKAYAMA<yoichi@FreeBSD.org>
To: freebsd-gnats-submit@FreeBSD.org
Subject: panic in sync_fsync
X-Send-Pr-Version: www-3.0

>Number:         105229
>Category:       kern
>Synopsis:       panic in sync_fsync
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Nov 06 23:50:19 GMT 2006
>Closed-Date:    Wed Jul 18 15:07:59 GMT 2007
>Last-Modified:  Wed Jul 18 15:07:59 GMT 2007
>Originator:     Yoichi NAKAYAMA
>Release:        current  (Nov 4 2006)
>Organization:
FreeBSD.org
>Environment:
FreeBSD suigei 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Sun Nov  5 02:05:09 JST 2006     root@suigei:/usr/obj/usr/src/sys/GENERIC  i386

>Description:
My machine with Intel CoreDuo processor panic after few days run:
  CPU: Genuine Intel(R) CPU           T2300  @ 1.66GHz (1666.68-MHz 686-class CPU)
    Origin = "GenuineIntel"  Id = 0x6e8  Stepping = 8
    Features=0xbfe9fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C
  MOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
    Features2=0xc1a9<SSE3,MON,VMX,EST,TM2,XTPR,<b15>>
    AMD Features=0x100000<NX>
    Cores per package: 2
  real memory  = 1065025536 (1015 MB)
  avail memory = 1028730880 (981 MB)

Trace obtained from /var/crash/vmcore.? follows:

(kgdb) bt
#0  doadump () at pcpu.h:166
#1  0xc06b07d8 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:410
#2  0xc06b0aed in panic (fmt=0xc08f04f3 "from debugger")
    at /usr/src/sys/kern/kern_shutdown.c:566
#3  0xc0476116 in db_panic (addr=-1066602469, have_addr=0, count=-1,
    modif=0xe3c27a14 "") at /usr/src/sys/ddb/db_command.c:433
#4  0xc04760af in db_command (last_cmdp=0xc0a05204, cmd_table=0x0)
    at /usr/src/sys/ddb/db_command.c:401
#5  0xc047616a in db_command_loop () at /usr/src/sys/ddb/db_command.c:453
#6  0xc0477db5 in db_trap (type=3, code=0) at /usr/src/sys/ddb/db_main.c:221
#7  0xc06cf2f4 in kdb_trap (type=3, code=0, tf=0xe3c27ba4)
    at /usr/src/sys/kern/subr_kdb.c:502
#8  0xc08a83a4 in trap (frame=
      {tf_fs = 8, tf_es = -473825240, tf_ds = -1066598360, tf_edi = -1064110166, tf_esi = 1, tf_ebp = -473793564, tf_isp = -473793584, tf_ebx = -473793520, tf_edx = 0, tf_ecx = 2, tf_eax = 18, tf_trapno = 3, tf_err = 0, tf_eip = -1066602469, tf_cs = 32, tf_eflags = 662, tf_esp = -473793532, tf_ss = -1066726753})
    at /usr/src/sys/i386/i386/trap.c:622
#9  0xc089317a in calltrap () at /usr/src/sys/i386/i386/exception.s:138
#10 0x00000008 in ?? ()
#11 0xe3c20028 in ?? ()
#12 0xc06d0028 in msgbuf_getchar (mbp=0xe3c27c10)
    at /usr/src/sys/kern/subr_msgbuf.c:145
---Type <return> to continue, or q <return> to quit---
#13 0xc06b0a9f in panic (fmt=0xc092f7aa "mtx_lock() of spin mutex %s @ %s:%d")
    at /usr/src/sys/kern/kern_shutdown.c:550
#14 0xc06a7dac in _mtx_lock_flags (m=0xc6549ba8, opts=0,
    file=0xc093ac72 "/usr/src/sys/kern/vfs_subr.c", line=2858)
    at /usr/src/sys/kern/kern_mutex.c:281
#15 0xc07112d9 in vfs_msync (mp=0xc3c75a50, flags=2)
    at /usr/src/sys/kern/vfs_subr.c:2858
#16 0xc0711a85 in sync_fsync (ap=0x0) at /usr/src/sys/kern/vfs_subr.c:3092
#17 0xc08b9ede in VOP_FSYNC_APV (vop=0x0, a=0xe3c27cb4) at vnode_if.c:1007
#18 0xc070f6b8 in sync_vnode (bo=0xc3d475c8, td=0xc3924a80) at vnode_if.h:537
#19 0xc070f935 in sched_sync () at /usr/src/sys/kern/vfs_subr.c:1690
#20 0xc069b2a4 in fork_exit (callout=0xc070f740 <sched_sync>, arg=0x0,
    frame=0xe3c27d38) at /usr/src/sys/kern/kern_fork.c:830
#21 0xc08931dc in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:199
(kgdb) 

>How-To-Repeat:
Boot the machine and keep it running.
>Fix:

>Release-Note:
>Audit-Trail:

From: Yoichi Nakayama <yoichi@FreeBSD.org>
To: FreeBSD-gnats-submit@FreeBSD.org
Cc: freebsd-current@freebsd.org
Subject: Re: kern/105229: panic in sync_fsync
Date: Wed, 18 Jul 2007 23:10:05 +0900

 At Thu, 9 Nov 2006 13:20:35 +0200,
 Giorgos Keramidas wrote:
 > 
 > On 2006-11-08 23:00, Yoichi Nakayama <yoichi@FreeBSD.org> 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
State-Changed-From-To: open->closed 
State-Changed-By: linimon 
State-Changed-When: Wed Jul 18 15:07:37 UTC 2007 
State-Changed-Why:  
Seems to have been a hardware problem. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=105229 
>Unformatted:
