Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Jul 1999 09:13:37 -0400 (EDT)
From:      "Andrew Atrens" <atrens@nortelnetworks.com>
To:        Kirk McKusick <mckusick@flamingo.McKusick.COM>
Cc:        current@freebsd.org, peter@freebsd.org, dg@root.com
Subject:   Re: lockmanager panic
Message-ID:  <Pine.BSF.4.10.9907200907220.725-100000@hcarp00g.ca.nortel.com>
In-Reply-To: <199907200459.VAA18341@flamingo.McKusick.COM>

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

I think I'm up to date :) ... Unfortunately I won't be able to try out
your fix until this evening :( ...

Cheers,

Andrew.

--

$ ident swap_pager.c
swap_pager.c:
     $Id: swap_pager.c,v 1.121 1999/07/16 05:11:35 alc Exp $

$ grep BUF_KERNPROC swap_pager.c
        BUF_KERNPROC(bp);
                        BUF_KERNPROC(bp);



On Mon, 19 Jul 1999, Kirk McKusick wrote:

> Date: Mon, 19 Jul 1999 21:59:51 -0700
> From: Kirk McKusick <mckusick@flamingo.McKusick.COM>
> To: "Atrens, Andrew (A.B.) [EXCHANGE:SKY:1U33:BNR]"
    <atrens@americasm01.nt.com>
> Cc: current@freebsd.org, peter@freebsd.org, dg@root.com
> Subject: Re: lockmanager panic
> 
> Please be sure that you are running with vm/swap_pager.c
> at version 1.120 or later. In particular, you should have
> two calls to the macro BUF_KERNPROC in that file. If you
> are missing those two calls, you will get the panic. If
> you do have those two calls in that code, then (and *only*
> then) try the following patch to see if it helps. It is
> making use of BUF_KERNPROC for cases in which it is not
> intended, but if it gets around your current problem, then
> gives a good indication of what to look for as a real fix.
> 
> 	Kirk McKusick



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9907200907220.725-100000>