From owner-freebsd-multimedia@FreeBSD.ORG Mon Apr 26 11:00:12 2010 Return-Path: Delivered-To: freebsd-multimedia@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ECA3B106566B for ; Mon, 26 Apr 2010 11:00:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DBD618FC1A for ; Mon, 26 Apr 2010 11:00:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o3QB0CFp095271 for ; Mon, 26 Apr 2010 11:00:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o3QB0CWv095264; Mon, 26 Apr 2010 11:00:12 GMT (envelope-from gnats) Date: Mon, 26 Apr 2010 11:00:12 GMT Message-Id: <201004261100.o3QB0CWv095264@freefall.freebsd.org> To: freebsd-multimedia@FreeBSD.org From: Garrett Cooper Cc: Subject: Re: kern/146031: [snd_hda] race condition when kldunload snd_hda sound called X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Garrett Cooper List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Apr 2010 11:00:13 -0000 The following reply was made to PR kern/146031; it has been noted by GNATS. From: Garrett Cooper To: Alexander Best Cc: bug-followup@freebsd.org Subject: Re: kern/146031: [snd_hda] race condition when kldunload snd_hda sound called Date: Mon, 26 Apr 2010 03:58:06 -0700 On Mon, Apr 26, 2010 at 3:23 AM, Alexander Best wrote: > Garrett Cooper schrieb am 2010-04-26: > > [snip] > >> Hi Alexander, >> =A0 =A0 1. How many cores and processors does your machine have? >> =A0 =A0 2. Do you have SMP enabled? >> Thanks, >> -Garrett > > 1. one cpu with 2 cores. > 2. yes and using the old bsd4 scheduler. Ok... now this is definitely non-standard. 1. My laptop is a dual-core Core2Duo proc (the full details are in the original PR). 2. I'm using SCHED_ULE, like most other folks post-7.x. I suggest using SCHED_ULE instead of SCHED_4BSD. You might only be able to run into the issue with SCHED_ULE because of how it schedules tasks. Thanks, -Garrett