Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 4 Jun 2004 22:14:25 -0700 (PDT)
From:      Don Lewis <truckman@FreeBSD.org>
To:        avatar@mmlab.cse.yzu.edu.tw
Cc:        dl@leo.org
Subject:   Re: LOR No 9 and strange other kernel messages
Message-ID:  <200406050514.i555EPJM004758@gw.catspoiler.org>
In-Reply-To: <040604202926C.61952@www.mmlab.cse.yzu.edu.tw>

next in thread | previous in thread | raw e-mail | index | archive | help
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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200406050514.i555EPJM004758>