Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 15 Apr 2010 12:51:52 +0300
From:      Kostik Belousov <kostikbel@gmail.com>
To:        Daniel Braniss <danny@cs.huji.ac.il>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: panic: vm_fault_copy_wired: page missing
Message-ID:  <20100415095152.GC2415@deviant.kiev.zoral.com.ua>
In-Reply-To: <E1O2LXV-000HOu-Nf@kabab.cs.huji.ac.il>
References:  <E1O2JP2-000FbF-No@kabab.cs.huji.ac.il> <20100415082254.GA2415@deviant.kiev.zoral.com.ua> <E1O2LXV-000HOu-Nf@kabab.cs.huji.ac.il>

next in thread | previous in thread | raw e-mail | index | archive | help

--U3Zg06C/E2vtHpAW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Apr 15, 2010 at 12:39:13PM +0300, Daniel Braniss wrote:
> >=20
> > --xFkczX7rH1pKA3aV
> > Content-Type: text/plain; charset=3Dus-ascii
> > Content-Disposition: inline
> > Content-Transfer-Encoding: quoted-printable
> >=20
> > On Thu, Apr 15, 2010 at 10:22:20AM +0300, Daniel Braniss wrote:
> > > Hi,
> > > I'm getting this with FreeBSD-8-stable, it usually happens when
> > > starting apache:
> > >=3D20
> > > panic: vm_fault_copy_wired: page missing
> > > cpuid =3D3D 3
> > > KDB: enter: panic
> > > [thread pid 1013 tid 100106 ]
> > > Stopped at      kdb_enter+0x3d: movq    $0,0x68f170(%rip)
> > > db> tr
> > > Tracing pid 1013 tid 100106 td 0xffffff0007a66ae0
> > > kdb_enter() at kdb_enter+0x3d
> > > panic() at panic+0x17b
> > > vm_fault_copy_entry() at vm_fault_copy_entry+0x283
> > > vmspace_fork() at vmspace_fork+0x4d0
> > > fork1() at fork1+0x35f
> > > fork() at fork+0x1c
> > > syscall() at syscall+0x1e7
> > > Xfast_syscall() at Xfast_syscall+0xe1
> > > --- syscall (2, FreeBSD ELF64, fork), rip =3D3D 0x8009f41ac, rsp =3D3=
D 0x7fff=3D
> > ffffe7d8,=3D20
> > > rbp =3D3D 0x800c34a80 ---
> > >=3D20
> > > any help in tracking this?
> > >=3D20
> > > thanks,
> > > 	danny
> >=20
> > Is it true that the process started, or at least some of loaded dso
> > are from NFS mount ?
> everything is nfs :-), the host is dataless
> but redusing the amount of physical memory has solved the
> problem, so I don't think NFS is the problem.

I do think that NFS is problem. Another key point is that your process
is mlock'ed, right ? This is kind of known issue with NFS and mlock.

--U3Zg06C/E2vtHpAW
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)

iEYEARECAAYFAkvG4bgACgkQC3+MBN1Mb4gn2QCdHlf6scFQfpgHFw7a/iySjrnP
SZoAn1WKC/3wxo2QIY8E8NEkludLi0aN
=vs7j
-----END PGP SIGNATURE-----

--U3Zg06C/E2vtHpAW--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100415095152.GC2415>