ome more info:
when the root file system is NOT via NFS all seems ok,
when the root is via NFS, no matter is amd is via NFS or not, it panics:
panic: vm_fault_copy_wired: page missing
cpuid = 1
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2a/frame 0xff814907a7
on 05/04/2013 12:33 Daniel Braniss said the following:
> The system is running FreeBSD-9.1-stable, and is dataless/diskless.
> the culprit is mlockall(2) which is called from the automounter amd/am-utils,
> commenting the call, eliminates the panic.
>
> I don't know when the problem surfaced, I wa
The system is running FreeBSD-9.1-stable, and is dataless/diskless.
the culprit is mlockall(2) which is called from the automounter amd/am-utils,
commenting the call, eliminates the panic.
I don't know when the problem surfaced, I was last hit by this
2 years ago almost to the day - creepy.
I can
...
> > > so IMHO, the problem is somewhere in the fact that root is diskless.
> >
> > Root on nfs means that e.g. libc is still mapped from nfs mount.
>
> argh, forgot about shared libs, so I linked amd static, and it's not
> panicking,
> yet ... [amd is in the root nfs].
it just panicked :-(
>
> --SpFw69Q4vVW19Q1W
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> On Sun, Apr 18, 2010 at 01:21:26PM +0300, Daniel Braniss wrote:
> > > > >=20
> > > > > --QA3RSaXxDkY7tjDy
> > > > > Content-Type: text/plain; charset
On Sun, Apr 18, 2010 at 01:21:26PM +0300, Daniel Braniss wrote:
> > > >
> > > > --QA3RSaXxDkY7tjDy
> > > > Content-Type: text/plain; charset=us-ascii
> > > > Content-Disposition: inline
> > > > Content-Transfer-Encoding: quoted-printable
> > > >
> > > > On Thu, Apr 15, 2010 at 02:54:19PM +0300, D
> > >
> > > --QA3RSaXxDkY7tjDy
> > > Content-Type: text/plain; charset=us-ascii
> > > Content-Disposition: inline
> > > Content-Transfer-Encoding: quoted-printable
> > >
> > > On Thu, Apr 15, 2010 at 02:54:19PM +0300, Daniel Braniss wrote:
> > > >=20
> > > > > Take NFS out of the picture if you c
> >
> > --QA3RSaXxDkY7tjDy
> > Content-Type: text/plain; charset=us-ascii
> > Content-Disposition: inline
> > Content-Transfer-Encoding: quoted-printable
> >
> > On Thu, Apr 15, 2010 at 02:54:19PM +0300, Daniel Braniss wrote:
> > >=20
> > > > Take NFS out of the picture if you can...
> > > >=20
>
>
> --QA3RSaXxDkY7tjDy
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> On Thu, Apr 15, 2010 at 02:54:19PM +0300, Daniel Braniss wrote:
> >=20
> > > Take NFS out of the picture if you can...
> > >=20
> > I've been thinkin
On Thu, Apr 15, 2010 at 02:54:19PM +0300, Daniel Braniss wrote:
>
> > Take NFS out of the picture if you can...
> >
> I've been thinking along those lines, and Kostic is convinced
> that the problem lies there, so I guess I'll give it a try, but
> it's no realy a solution.
Better solution is to
> Take NFS out of the picture if you can...
>
I've been thinking along those lines, and Kostic is convinced
that the problem lies there, so I guess I'll give it a try, but
it's no realy a solution.
cheers,
danny
___
freebsd-stable@freebsd.org
On 04/15/10 13:11, Jeremy Chadwick wrote:
On Thu, Apr 15, 2010 at 02:05:26PM +0300, Daniel Braniss wrote:
On Thu, Apr 15, 2010 at 01:24:14PM +0300, Daniel Braniss wrote:
On Thu, Apr 15, 2010 at 9:22 AM, Daniel Braniss wrote:
Hi,
I'm getting this with FreeBSD-8-stable, it usually happens when
On Thu, Apr 15, 2010 at 02:05:26PM +0300, Daniel Braniss wrote:
> > On Thu, Apr 15, 2010 at 01:24:14PM +0300, Daniel Braniss wrote:
> > > > On Thu, Apr 15, 2010 at 9:22 AM, Daniel Braniss
> > > > wrote:
> > > > > Hi,
> > > > > I'm getting this with FreeBSD-8-stable, it usually happens when
> > >
> On Thu, Apr 15, 2010 at 01:24:14PM +0300, Daniel Braniss wrote:
> > > On Thu, Apr 15, 2010 at 9:22 AM, Daniel Braniss
> > > wrote:
> > > > Hi,
> > > > I'm getting this with FreeBSD-8-stable, it usually happens when
> > > > starting apache:
> > >
> > > alc@ made some VM MFCs yesterday, could yo
On Thu, Apr 15, 2010 at 01:24:14PM +0300, Daniel Braniss wrote:
> > On Thu, Apr 15, 2010 at 9:22 AM, Daniel Braniss wrote:
> > > Hi,
> > > I'm getting this with FreeBSD-8-stable, it usually happens when
> > > starting apache:
> >
> > alc@ made some VM MFCs yesterday, could you try a 13th of April
t; > 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.
>
well, since it's panicking again, there goes the memsize theory.
thi
> On Thu, Apr 15, 2010 at 9:22 AM, Daniel Braniss wrote:
> > Hi,
> > I'm getting this with FreeBSD-8-stable, it usually happens when
> > starting apache:
>
> alc@ made some VM MFCs yesterday, could you try a 13th of April kernel
> and see if it works out for you?
with or without the MFC it's sti
at 10:22:20AM +0300, Daniel Braniss wrote:
> > > Hi,
> > > I'm getting this with FreeBSD-8-stable, it usually happens when
> > > starting apache:
> > >=20
> > > panic: vm_fault_copy_wired: page missing
> > > cpuid =3D 3
> > > KDB: e
eBSD-8-stable, it usually happens when
> > starting apache:
> >=20
> > panic: vm_fault_copy_wired: page missing
> > cpuid =3D 3
> > KDB: enter: panic
> > [thread pid 1013 tid 100106 ]
> > Stopped at kdb_enter+0x3d: movq$0,0x68f170(%rip)
> > db> t
> On Thu, Apr 15, 2010 at 9:22 AM, Daniel Braniss wrote:
> > Hi,
> > I'm getting this with FreeBSD-8-stable, it usually happens when
> > starting apache:
>
> alc@ made some VM MFCs yesterday, could you try a 13th of April kernel
> and see if it works out for you?
the kernel that panics does not i
> On Thu, Apr 15, 2010 at 9:22 AM, Daniel Braniss wrote:
> > Hi,
> > I'm getting this with FreeBSD-8-stable, it usually happens when
> > starting apache:
>
> alc@ made some VM MFCs yesterday, could you try a 13th of April kernel
> and see if it works out for you?
>
asap, btw, I reduced the amoun
> On Thu, Apr 15, 2010 at 11:50:41AM +0300, Daniel Braniss wrote:
> > > On Thu, Apr 15, 2010 at 12:22 AM, Daniel Braniss
> > > wrot=e:
> > > > Hi,
> > > > I'm getting this with FreeBSD-8-stable, it usually happens when
> > > > sta
On Thu, Apr 15, 2010 at 9:22 AM, Daniel Braniss wrote:
> Hi,
> I'm getting this with FreeBSD-8-stable, it usually happens when
> starting apache:
alc@ made some VM MFCs yesterday, could you try a 13th of April kernel
and see if it works out for you?
--
Good, fast & cheap. Pick any two.
___
On Thu, Apr 15, 2010 at 11:50:41AM +0300, Daniel Braniss wrote:
> > On Thu, Apr 15, 2010 at 12:22 AM, Daniel Braniss
> > wrot=e:
> > > Hi,
> > > I'm getting this with FreeBSD-8-stable, it usually happens when
> > > starting apache:
> > >
>
> On Thu, Apr 15, 2010 at 12:22 AM, Daniel Braniss wrot=e:
> > Hi,
> > I'm getting this with FreeBSD-8-stable, it usually happens when
> > starting apache:
> >
> > panic: vm_fault_copy_wired: page missing
> > cpuid = 3
> > KDB: enter: pani
On Thu, Apr 15, 2010 at 01:06:20AM -0700, Garrett Cooper wrote:
> On Thu, Apr 15, 2010 at 12:22 AM, Daniel Braniss wrote:
> > Hi,
> > I'm getting this with FreeBSD-8-stable, it usually happens when
> > starting apache:
> >
> > panic: vm_fault_copy_wired: pag
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:
>
> panic: vm_fault_copy_wired: page missing
> cpuid = 3
> KDB: enter: panic
> [thread pid 1013 tid 100106 ]
>
On Thu, Apr 15, 2010 at 12:22 AM, Daniel Braniss wrote:
> Hi,
> I'm getting this with FreeBSD-8-stable, it usually happens when
> starting apache:
>
> panic: vm_fault_copy_wired: page missing
> cpuid = 3
> KDB: enter: panic
> [thread pid 1013 tid 100106 ]
> Stop
Hi,
I'm getting this with FreeBSD-8-stable, it usually happens when
starting apache:
panic: vm_fault_copy_wired: page missing
cpuid = 3
KDB: enter: panic
[thread pid 1013 tid 100106 ]
Stopped at kdb_enter+0x3d: movq$0,0x68f170(%rip)
db> tr
Tracing pid 1013 tid 1
29 matches
Mail list logo
