Hi,
I've been building KDE on a new -CURRENT system with ZFS and hit a
panic - vm_object_page_collect_flush failed (more info is at
http://www.cran.org.uk/~brucec/freebsd/zfs_vm_panic.txt).
#9 0x802a6190 in panic (fmt=Variable fmt is not available.
)
at
On Sat, Nov 20, 2010 at 02:48:15PM +, Bruce Cran wrote:
Hi,
I've been building KDE on a new -CURRENT system with ZFS and hit a
panic - vm_object_page_collect_flush failed (more info is at
http://www.cran.org.uk/~brucec/freebsd/zfs_vm_panic.txt).
#9 0x802a6190 in panic
panic: lockmgr: locking against myself
Debugger(panic)
Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0
dbtrace
Debugger(c0381630,c03e4ee0,c037fd14,da447c28,1) at Debugger+0x54
panic(c037fd14,0,c037fc88,eb,1fb) at panic+0xab
lockmgr(c138e85c,2,0,c3c150e0,c3c1514) at lockmgr+0x512
Apparently, On Thu, Jan 23, 2003 at 11:45:13AM +0800,
David Xu said words to the effect of;
panic: lockmgr: locking against myself
Debugger(panic)
Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0
dbtrace
Debugger(c0381630,c03e4ee0,c037fd14,da447c28,1) at Debugger+0x54
What kind of value do you use for N? It looks like lately the makefiles
are too aggressive when using -j, so you end up with N * N * 2 processes
running simultaneously. On my -current box with 128M RAM, I used -j13
for a long time, but that runs out of swap nowadays, so I'm using -j4
which
Matthew N. Dodd wrote:
On Sat, 17 Aug 2002, Mark Murray wrote:
If I do a make -jN world build on my dual MMX/200 box, I usually end
up in tears (well, a panic anyway). This is completely reproducible, and
the panic always happens in swapout_procs while vmdaemon is running.
Anyone else
On Mon, 19 Aug 2002, Jason wrote:
Wierd, I have it running just peachy on a dual P3 900 box
It runs mostly okay on my dual P3/600, although for the last couple of
months it has a tendency to panic with a bdwrite: buffer is not busy on
average 2-3 times a day (per approx 15 hour run) Such is
On Mon, 19 Aug 2002, Jason wrote:
Wierd, I have it running just peachy on a dual P3 900 box
Just so nobody else replies to this with something similar we're talking
about PENTIUMS.
Not the P3, P2, Alpha or anything else.
--
| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E |
Matthew N. Dodd wrote:
On Mon, 19 Aug 2002, Jason wrote:
Wierd, I have it running just peachy on a dual P3 900 box
Just so nobody else replies to this with something similar we're talking
about PENTIUMS.
Not the P3, P2, Alpha or anything else.
Yes. My ASUS Dual P90 machine has the
On Mon, 19 Aug 2002, Terry Lambert wrote:
Yes. My ASUS Dual P90 machine has the same problem. I just thought it
was the MP Spec compliance level of the BIOS, and gave up running
-current. I guess it's not just me. 8-(.
Its likely that we've got the same motherboard.
Mine is a
On Sat, 17 Aug 2002, Mark Murray wrote:
If I do a make -jN world build on my dual MMX/200 box, I usually end
up in tears (well, a panic anyway). This is completely reproducible, and
the panic always happens in swapout_procs while vmdaemon is running.
Anyone else getting this?
I'm amazed
Date: Sun, 18 Aug 2002 20:44:52 -0400 (EDT)
From: Matthew N. Dodd [EMAIL PROTECTED]
On Sat, 17 Aug 2002, Mark Murray wrote:
If I do a make -jN world build on my dual MMX/200 box, I usually end
up in tears (well, a panic anyway). This is completely reproducible, and
the panic always happens in
I'm amazed you've got a dual Pentium running -CURRENT at all.
both of mine haven't worked with SMP kernels for months. (dual P54C and
dual P55C).
I am running SMP CURRENT kernel on 4-Alpha processors . No problems
for a lot of months.
Yuri.
To Unsubscribe: send mail to [EMAIL PROTECTED]
In the last episode (Aug 18), David Wolfskill said:
From: Matthew N. Dodd [EMAIL PROTECTED]
I'm amazed you've got a dual Pentium running -CURRENT at all.
I'm not.
both of mine haven't worked with SMP kernels for months. (dual P54C
and dual P55C).
freebeast(5.0-C)[2] uname -a
CPU:
Hi all
If I do a make -jN world build on my dual MMX/200 box, I usually end
up in tears (well, a panic anyway). This is completely reproducible, and
the panic always happens in swapout_procs while vmdaemon is running.
Anyone else getting this?
M
--
o Mark Murray
\_
O.\_Warning: this
If I do a make -jN world build on my dual MMX/200 box, I usually end
up in tears (well, a panic anyway). This is completely reproducible, and
the panic always happens in swapout_procs while vmdaemon is running.
Anyone else getting this?
What kind of value do you use for N? It looks like
panic: vm_page_insert: already inserted
syncing disks...
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
It looks like you guys got it! What is currently checked in (by Assar)
is working fine! :-)
M
:--=-=-=
:
:Matt Dillon [EMAIL PROTECTED] writes:
: Well, yes... that's essentially what I suggested. You didn't say
: anything about removing the externalized inlines, which is what you
:
:It looks like you guys got it! What is currently checked in (by Assar)
:is working fine! :-)
:
:M
Excellent news!
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hi Matt
I'm getting a reliable panic on CURRENT (2000/12/26) with INVARIANTS
set. I suppose I could "fix" this by taking out INVARIANTS, but it
seems to make more sense to try to get it fixed.
The panic() is "freeing free entry", and the traceback (minus most
of the numbers) is:
panic
zerror
:Hi Matt
:
:I'm getting a reliable panic on CURRENT (2000/12/26) with INVARIANTS
:set. I suppose I could "fix" this by taking out INVARIANTS, but it
:seems to make more sense to try to get it fixed.
:
:The panic() is "freeing free entry", and the traceback (minus most
:of the numbers) is:
:
On Tue, Dec 26, 2000 at 02:00:54PM +0200, Mark Murray wrote:
I'm getting a reliable panic on CURRENT (2000/12/26) with INVARIANTS
set. I suppose I could "fix" this by taking out INVARIANTS, but it
seems to make more sense to try to get it fixed.
Do you have NFS compiled in to the kernel?
:Do you have NFS compiled in to the kernel? I've had trouble using
:INVARIANTS in the kernel and NFS as a module many times - it always
:panics in the zone allocation stuff.
:
:(Either you always need to compile modules with the same INVARIENTS
:options as the kernel, or we need to fix INVARIENTS
Matt Dillon [EMAIL PROTECTED] writes:
I think the only real solution is to rip out the externally visible
zalloc/zfree inlines and replace them with real routines. I will happily
do this, those inlines have always been an eyesore to me and the
performance benefit is minimal
:
:Matt Dillon [EMAIL PROTECTED] writes:
: I think the only real solution is to rip out the externally visible
: zalloc/zfree inlines and replace them with real routines. I will happily
: do this, those inlines have always been an eyesore to me and the
: performance benefit is
Matt Dillon [EMAIL PROTECTED] writes:
We can't just go do an end-run around the established API as a
hack around the problem.
I fail too se how my suggestion would change the API at all, but in
case I was unclear, diffs are below.
/assar
Index: vm_zone.c
:Matt Dillon [EMAIL PROTECTED] writes:
: We can't just go do an end-run around the established API as a
: hack around the problem.
:
:I fail too se how my suggestion would change the API at all, but in
:case I was unclear, diffs are below.
:
:/assar
:
Well, yes... that's essentially
Matt Dillon [EMAIL PROTECTED] writes:
Well, yes... that's essentially what I suggested. You didn't say
anything about removing the externalized inlines, which is what you
do in your patch. Looks like a fine patch to me.
Except it didn't work. Now here's a patch that survived
:--=-=-=
:
:Matt Dillon [EMAIL PROTECTED] writes:
: Well, yes... that's essentially what I suggested. You didn't say
: anything about removing the externalized inlines, which is what you
: do in your patch. Looks like a fine patch to me.
:
:Except it didn't work. Now here's a
On Tue, Dec 26, 2000 at 02:00:54PM +0200, Mark Murray wrote:
I'm getting a reliable panic on CURRENT (2000/12/26) with INVARIANTS
set. I suppose I could "fix" this by taking out INVARIANTS, but it
seems to make more sense to try to get it fixed.
Do you have NFS compiled in to the
30 matches
Mail list logo
