From owner-freebsd-hackers Wed Nov 17 22:13:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D478014A1F for ; Wed, 17 Nov 1999 22:13:48 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA09843; Wed, 17 Nov 1999 23:13:47 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA21369; Wed, 17 Nov 1999 23:14:08 -0700 (MST) Message-Id: <199911180614.XAA21369@harmony.village.org> To: "David E. Cross" Subject: Re: AMD wedging Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 17 Nov 1999 19:47:41 EST." <199911180054.TAA48910@cs.rpi.edu> References: <199911180054.TAA48910@cs.rpi.edu> Date: Wed, 17 Nov 1999 23:14:08 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911180054.TAA48910@cs.rpi.edu> "David E. Cross" writes: : 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? -stable or -current? If -stable, then there is a well known bug that prevents AMD from NFS mounting local file systems. I have a kludge that is gross beyond words that I came up with, but haven't had a time to made it any less gross. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message