From owner-freebsd-current@FreeBSD.ORG  Fri Jun  4 22:14:35 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0580716A4CE
	for <freebsd-current@FreeBSD.org>;
	Fri,  4 Jun 2004 22:14:35 -0700 (PDT)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9E76C43D2D
	for <freebsd-current@FreeBSD.org>;
	Fri,  4 Jun 2004 22:14:34 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.11/8.12.11) with ESMTP id i555EPJM004758;
	Fri, 4 Jun 2004 22:14:29 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200406050514.i555EPJM004758@gw.catspoiler.org>
Date: Fri, 4 Jun 2004 22:14:25 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: avatar@mmlab.cse.yzu.edu.tw
In-Reply-To: <040604202926C.61952@www.mmlab.cse.yzu.edu.tw>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: freebsd-current@FreeBSD.org
cc: dl@leo.org
Subject: Re: LOR No 9 and strange other kernel messages
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jun 2004 05:14:35 -0000

On  4 Jun, Tai-hwa Liang wrote:
> On Fri, 4 Jun 2004, Daniel Lang wrote:
>> Hi,
>>
>> I just went through my syslog and stumbled across a LOR, which is
>> documented on the Zabbadoz LOR page (id 009).
>>
>> The reason for this mail is the following kernel messages:
>>
>> [..]
>> Jun  1 11:08:06 atrbg11 kernel: x: 2
>> Jun  1 11:08:06 atrbg11 kernel: x: 2
>> [..]
>>
>> Seems some leftovers from a developer who did not want to
>> bother others with the gory details. ;-))
> 
> I guess that came from sys/dev/sound/pcm/sound.c:872. My Thinkpad T40 also
> ran into this when the disk/network(combination) load is high enough.

Looks likely, but I'd expect this would only get triggered when sysctl
is used to set or query the number of vchans.  In any case, this marks
another spot where locking is broken in the sound code.