From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 2 22:38:18 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ECCAD106566B for ; Thu, 2 Aug 2012 22:38:17 +0000 (UTC) (envelope-from dieterbsd@engineer.com) Received: from mailout-us.mail.com (mailout-us.gmx.com [74.208.5.67]) by mx1.freebsd.org (Postfix) with SMTP id 94E1A8FC08 for ; Thu, 2 Aug 2012 22:38:17 +0000 (UTC) Received: (qmail 20152 invoked by uid 0); 2 Aug 2012 22:38:10 -0000 Received: from 67.206.185.58 by rms-us002 with HTTP Content-Type: text/plain; charset="utf-8" Date: Thu, 02 Aug 2012 18:38:08 -0400 From: "Dieter BSD" Message-ID: <20120802223810.298390@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: BWRpcOsV3zOlNR3dAHAhvl9+IGRvb8Ck Subject: Re: How to diagnose system freezes? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Aug 2012 22:38:18 -0000 Yuri writes: > One of my 9.1-BETA1 systems periodically freezes. If sound was playing, > it would usually cycle with a very short period. And system stops being > sensitive to keyboard/mouse. Also ping of this system doesn't get a > response. So the sound continues, on and off, while everything else freezes? I would suspect that the sound device driver is locking out other devices and hogging the system. WHY does FreeBSD allow one device driver to lock out out everything else? And what can we do about it? I've seen a device driver lock out everything else for minutes-on-end, which of course resulted in data being lost. Losing data is one of the worst things an OS can do. This needs to be fixed.