From owner-freebsd-hackers Wed Nov 17 16:55: 4 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 4F0EA1501E for ; Wed, 17 Nov 1999 16:54:59 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (loot.cs.rpi.edu [128.213.16.22]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id TAA48910; Wed, 17 Nov 1999 19:54:57 -0500 (EST) Message-Id: <199911180054.TAA48910@cs.rpi.edu> To: freebsd-hackers@freebsd.org Cc: crossd@cs.rpi.edu Subject: AMD wedging Date: Wed, 17 Nov 1999 19:47:41 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been noticing of late a disturbing trend of AMD wedging and eventually taking the entire system down. The WCHAN that it is locked in is "sbwait". I now have the luxury of having this happen on a non-critical system with DDB compiled in (the system is the one I am typing on now). How would I go about finding exactly what it is stuck on so I may correct the bug in the kernel or amd? -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD 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