From owner-freebsd-hackers Wed Apr 21 13:50:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 55D5915876 for ; Wed, 21 Apr 1999 13:50:29 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id QAA21541 for ; Wed, 21 Apr 1999 16:48:00 -0400 (EDT) Message-Id: <199904212048.QAA21541@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: Deadlock on -stable Date: Wed, 21 Apr 1999 16:48:01 -0400 From: "David E. Cross" 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 Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message