From owner-freebsd-hackers Wed Apr 21 14:10:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id C7418158E0 for ; Wed, 21 Apr 1999 14:10:13 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA08532; Wed, 21 Apr 1999 14:07:32 -0700 (PDT) (envelope-from dillon) Date: Wed, 21 Apr 1999 14:07:32 -0700 (PDT) From: Matthew Dillon Message-Id: <199904212107.OAA08532@apollo.backplane.com> To: "David E. Cross" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Deadlock on -stable References: <199904212048.QAA21541@cs.rpi.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :This is a continuation of the 'pausing' problem I described earlier. I am now :able to easily reproduce it. I have a ddb induced panic/corefile of one of :the systems I paused. Since I can do this at will, I can get you and ddb :information that you may need. : :I have reproduced this on systems built 60 days ago, and one built ~18 days :ago. : :Is there anything people wish me to look at? : :-- :David Cross | email: crossd@cs.rpi.edu :Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd If you have a core file, do a 'man ps' and look at the -M and -N options. vmstat and netstat also have these options. Then try to get as much info as you can out of the core file using these commands w/ the appropriate options. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message