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
13 matches
Mail list logo
