From owner-freebsd-current  Sun Mar 10 16:27:42 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id QAA02993
          for current-outgoing; Sun, 10 Mar 1996 16:27:42 -0800 (PST)
Received: from mpp.minn.net (root@mpp.Minn.Net [204.157.201.242])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA02983
          for <current@Freebsd.ORG>; Sun, 10 Mar 1996 16:27:35 -0800 (PST)
Received: (from mpp@localhost) by mpp.minn.net (8.7.3/8.6.9) id SAA00399; Sun, 10 Mar 1996 18:27:17 -0600 (CST)
Message-Id: <199603110027.SAA00399@mpp.minn.net>
Subject: Re: vm/kern_lock.c:lock_read hang ?
To: mrl@teleport.com (Mostyn/Annabella)
Date: Sun, 10 Mar 1996 18:27:17 -0600 (CST)
From: "Mike Pritchard" <mpp@mpp.minn.net>
Cc: current@Freebsd.ORG, mrl@teleport.com
In-Reply-To: <199603101751.JAA23037@linda.teleport.com> from "Mostyn/Annabella" at Mar 10, 96 09:51:05 am
X-Mailer: ELM [version 2.4 PL25 ME8b]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@Freebsd.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Mostyn/Annabella wrote:
> 
> Hi,
> My occaisional ppp (kernel) hangs seem to boil down to processes
> sleeping at the tsleep(l, PVM, "lockrd", 0); statement in
> lock_read in vm/kern_lock.c.
> Any attempt to do anything at this point permanently hangs the
> machine.
> 
> Another way to create an instant panic is to go into ddb
> (cntl/alt/esc) and type -
> 
> show map
> 
> which goes off to vm_map_print and panics.
> 
> 
> This with a kernel from March 3rd.

Try adding "-bsdcomp" to your /etc/ppp/options file and see
if the problem goes away.  Something in that code seems to
trash the swaplist and who knows what else.  I've been unable to
track down exactly what in that code is causing the kernel
memory corruption.
-- 
Mike Pritchard
mpp@minn.net
"Go that way.  Really fast.  If something gets in your way, turn"