From owner-freebsd-current@FreeBSD.ORG Thu Jan 8 12:37:12 2004 Return-Path: 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 531E716A4CE for ; Thu, 8 Jan 2004 12:37:12 -0800 (PST) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FE4B43D1D for ; Thu, 8 Jan 2004 12:37:08 -0800 (PST) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i08Kb07E020742; Thu, 8 Jan 2004 12:37:04 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200401082037.i08Kb07E020742@gw.catspoiler.org> Date: Thu, 8 Jan 2004 12:36:59 -0800 (PST) From: Don Lewis To: shoesoft@gmx.net In-Reply-To: <1073579992.722.6.camel@shoeserv.freebsd> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: current@FreeBSD.org Subject: Re: sound/pcm/* bugs (was: Re: page fault panic tracked down (selwakeuppri()) - really sound/pcm/*) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jan 2004 20:37:12 -0000 On 8 Jan, Stefan Ehmann wrote: > On Thu, 2004-01-08 at 10:58, Don Lewis wrote: >> On 7 Jan, Stefan Ehmann wrote: >> Some other wierdness that I noticed is that if one of the >> chn_setblocksize() is called for one of the vchans, vchan_setblocksize() >> will get called, which will call chn_notify(parent, CHN_N_BLOCKSIZE). >> When this happens, the parent will interate over all of its children >> looking for the one with the minimum bufhard blksz. It will then call >> chn_setblocksize() on itself, and chn_setblocksize() will call >> sndbuf_remalloc() on its bufsoft, which will set reallocate the buffer >> with the size (blkcnt * blksz). If this channel is the parent vchan and >> the new size of bufsoft is smaller than the size of bufhard (which never >> gets reallocated), feed_vchan_s16() will write past the end of bufsoft >> and things will go boom sometime later. >> >> Try the patch below in place of my previous patch. As you might guess, >> I'm grasping at straws. > > Again - no luck. This time even disabling vchans doesn't help. No sound > at all. The code seems to be really tricky. > > I get: > kernel: pcm0:virtual:0: play interrupt timeout, channel dead > kernel: pcm0:play:0: play interrupt timeout, channel dead > each try to change vchans aftet that results in a > kernel: x: 2 (last message repeated 9 times) I don't understand why it is failing that way. Are you sure that the previous change to chn_intr() was backed out? > At least our assumption that the panic only occurs with vchans enabled > seems to be true (~ 8 hrs uptime). >