Re: panic: Lock vm object not exclusively locked @ /usr/src/sys/vm/vm_page.c:2637

2015-04-05 Thread Alan Cox
>> A> > D> >>> A> > D> Sun Apr 5 06:18:44 PDT 2015 >>> A> > D> >>> A> > D> FreeBSD g1-254.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT >>> #1561 r281106M/281106:1100067: Sun Apr 5 06:01:06 PDT 2015 >>

Re: panic: Lock vm object not exclusively locked @ /usr/src/sys/vm/vm_page.c:2637

2015-04-05 Thread Rui Paulo
gt; A> > D> >> A> > D> FreeBSD g1-254.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT >> #1561 r281106M/281106:1100067: Sun Apr 5 06:01:06 PDT 2015 >> r...@g1-254.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY i386 >> A> > D> >> A

Re: panic: Lock vm object not exclusively locked @ /usr/src/sys/vm/vm_page.c:2637

2015-04-05 Thread Alan Cox
catwhisker.org dumped core - see /var/crash/vmcore.3 > A> > A> > D> > A> > A> > D> Sun Apr 5 06:18:44 PDT 2015 > A> > A> > D> > A> > A> > D> FreeBSD g1-254.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT > #1561 r281106M/2

Re: panic: Lock vm object not exclusively locked @ /usr/src/sys/vm/vm_page.c:2637

2015-04-05 Thread David Wolfskill
On Sun, Apr 05, 2015 at 05:57:08PM -0500, Alan Cox wrote: > ... > > A> Just curious, amd64 or i386? > > > > Panics on amd64, while building a kernel for i386, if that matters :) > > > > Maybe. I didn't trip the assertion building amd64 kernels or world. > Maybe the difference is that the mac

Re: panic: Lock vm object not exclusively locked @ /usr/src/sys/vm/vm_page.c:2637

2015-04-05 Thread Gleb Smirnoff
gt; Sun Apr 5 06:18:44 PDT 2015 A> > A> > D> A> > A> > D> FreeBSD g1-254.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT #1561 r281106M/281106:1100067: Sun Apr 5 06:01:06 PDT 2015 r...@g1-254.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY i386 A> > A>

Re: panic: Lock vm object not exclusively locked @ /usr/src/sys/vm/vm_page.c:2637

2015-04-05 Thread Alan Cox
61 > r281106M/281106:1100067: Sun Apr 5 06:01:06 PDT 2015 > r...@g1-254.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY i386 > A> > D> > A> > D> panic: Lock vm object not exclusively locked @ > /usr/src/sys/vm/vm_page.c:2637 > A> > > A> >

Re: panic: Lock vm object not exclusively locked @ /usr/src/sys/vm/vm_page.c:2637

2015-04-05 Thread Gleb Smirnoff
/crash/vmcore.3 A> > D> A> > D> Sun Apr 5 06:18:44 PDT 2015 A> > D> A> > D> FreeBSD g1-254.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT #1561 r281106M/281106:1100067: Sun Apr 5 06:01:06 PDT 2015 r...@g1-254.catwhisker.org:/common/S4/obj/usr/s

Re: panic: Lock vm object not exclusively locked @ /usr/src/sys/vm/vm_page.c:2637

2015-04-05 Thread David Wolfskill
On Sun, Apr 05, 2015 at 10:47:03AM -0700, David Wolfskill wrote: > ... > > Either this, or vm_page_advise() could be changed to do nothing in the > > case of MADV_DONTNEED operation and a need to call vm_page_dirty(), if > > the object is only read-locked. > > I have since managed to build & (succ

Re: panic: Lock vm object not exclusively locked @ /usr/src/sys/vm/vm_page.c:2637

2015-04-05 Thread David Wolfskill
On Sun, Apr 05, 2015 at 08:37:23PM +0300, Konstantin Belousov wrote: > On Sun, Apr 05, 2015 at 06:47:21PM +0300, Gleb Smirnoff wrote: > > This is r281079. > > > > Since vm_page_advise() may call vm_page_dirty() in the MADV_DONTNEED case, > > the assertion is valid. So, looks like vm_fault_dontneed

Re: panic: Lock vm object not exclusively locked @ /usr/src/sys/vm/vm_page.c:2637

2015-04-05 Thread Alan Cox
org 11.0-CURRENT FreeBSD 11.0-CURRENT #1561 > r281106M/281106:1100067: Sun Apr 5 06:01:06 PDT 2015 > r...@g1-254.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY i386 > D> > D> panic: Lock vm object not exclusively locked @ > /usr/src/sys/vm/vm_page.c:2637 >

Re: panic: Lock vm object not exclusively locked @ /usr/src/sys/vm/vm_page.c:2637

2015-04-05 Thread Konstantin Belousov
On Sun, Apr 05, 2015 at 06:47:21PM +0300, Gleb Smirnoff wrote: > This is r281079. > > Since vm_page_advise() may call vm_page_dirty() in the MADV_DONTNEED case, > the assertion is valid. So, looks like vm_fault_dontneed() needs W-lock on > the first_object. > Either this, or vm_page_advise() coul

Re: panic: Lock vm object not exclusively locked @ /usr/src/sys/vm/vm_page.c:2637

2015-04-05 Thread Gleb Smirnoff
r...@g1-254.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY i386 D> D> panic: Lock vm object not exclusively locked @ /usr/src/sys/vm/vm_page.c:2637 This is r281079. Since vm_page_advise() may call vm_page_dirty() in the MADV_DONTNEED case, the assertion is valid. So, looks like vm_fa

panic: Lock vm object not exclusively locked @ /usr/src/sys/vm/vm_page.c:2637

2015-04-05 Thread David Wolfskill
Sun Apr 5 06:18:44 PDT 2015 FreeBSD g1-254.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT #1561 r281106M/281106:1100067: Sun Apr 5 06:01:06 PDT 2015 r...@g1-254.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY i386 panic: Lock vm object not exclusively locked @ /usr/src/sys/vm/vm_page.c