From owner-freebsd-multimedia Sat Feb 8 13:57:34 2003 Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D540937B401; Sat, 8 Feb 2003 13:57:32 -0800 (PST) Received: from puma.icir.org (puma.icir.org [192.150.187.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83BE143F85; Sat, 8 Feb 2003 13:57:32 -0800 (PST) (envelope-from hodson@puma.icir.org) Received: from puma.icir.org (localhost [127.0.0.1]) by puma.icir.org (8.12.3/8.12.3) with ESMTP id h18LvQ8J033548; Sat, 8 Feb 2003 13:57:26 -0800 (PST) (envelope-from hodson@puma.icir.org) Message-Id: <200302082157.h18LvQ8J033548@puma.icir.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.3 To: Scott Cc: freebsd-multimedia@freebsd.org, cg@freebsd.org From: Orion Hodson Subject: Re: panic in dsp_ioctl() In-Reply-To: Your message of "Sat, 08 Feb 2003 11:21:23 MST." <3E454AA3.6050503@mho.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 08 Feb 2003 13:57:26 -0800 Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org /-- Scott wrote: | WIth a fairly recent 5-current and ICH3 sound hardware I'm getting a | panic in dsp_ioctl() when running just about anything. Can you be specific about what you are running? I appreciate it might seem like anything you try generates this, but I'm unable to replicate it trivially. Before doing whatever it is that crashes the machine can you: 1. run 'fstat /dev/audio* /dev/dsp*' 2. set 'sysctl hw.snd.verbose=3' and get 'cat /dev/sndstat' You can post this output to cg and myself since it's probably of little interest to anyone else. | Since I'm not doing any recording, I would assume that rdch should be | NULL and the test would avoid the rdch->flags indirection. Fake channels get set by the getchns function, which may be to keep the processing cleaner, ie fewer exceptions. | having a hard time figuring out how rdch actually gets set/initialized | in the driver, and the value that winds up in this code path is very | bogus. This wasn't a problem with my previous build a few weeks ago. Very little in the channel management has changed in the past few weeks. So I'm a bit puzzled why this should occur now, but there are other users reporting problems with locks at present too so there is clearly a problem, probably a result of more people running 5.x these days (a good thing, despite the teething). Cheers - Orion To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message