From owner-freebsd-hackers@FreeBSD.ORG  Fri Sep 21 00:57:44 2012
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 6D1AC1065670
	for <freebsd-hackers@freebsd.org>; Fri, 21 Sep 2012 00:57:44 +0000 (UTC)
	(envelope-from dieterbsd@engineer.com)
Received: from mailout-us.gmx.com (mailout-us.gmx.com [74.208.5.67])
	by mx1.freebsd.org (Postfix) with SMTP id 13F1A8FC1D
	for <freebsd-hackers@freebsd.org>; Fri, 21 Sep 2012 00:57:44 +0000 (UTC)
Received: (qmail 10128 invoked by uid 0); 21 Sep 2012 00:57:43 -0000
Received: from 67.206.186.97 by rms-us009 with HTTP
Content-Type: text/plain; charset="utf-8"
Date: Thu, 20 Sep 2012 20:57:39 -0400
From: "Dieter BSD" <dieterbsd@engineer.com>
Message-ID: <20120921005740.165830@gmx.com>
MIME-Version: 1.0
To: freebsd-hackers@freebsd.org
X-Authenticated: #74169980
X-Flags: 0001
X-Mailer: GMX.com Web Mailer
x-registered: 0
Content-Transfer-Encoding: 8bit
X-GMX-UID: 094pcKMh3zOlNR3dAHAhy1B+IGRvb8Ab
Subject: Re: FreeBSD 8.0 suddenly freezing
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Sep 2012 00:57:44 -0000

> In the last 72 hours, we've had two different systems freeze; they don't
> apparently recognize any interrupts, they won't respond to ping, and
> they require a powercycle to reboot. We can't easily generate an NMI on
> these boxes.

> Just on the off chance, does this sound like a familiar -- and
> preferably soluble -- problem?

Only theory I can think of is that some device driver shuts off
all interrupts and then goes into an infinite loop.

I have had trouble with at least four different device drivers
locking everything out long enough to lose incoming data.
Usually it recovers without a reboot. Not an infinte loop, just
way way too long to leave interrupts shut off.

See also the "How to diagnose system freezes?" thread from July-August.
Yuri found that a particular rev of the nvidia driver went into
an infinite loop.