From owner-freebsd-mobile Mon Jul 8 15:30:16 2002 Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70D9C37B400 for ; Mon, 8 Jul 2002 15:30:13 -0700 (PDT) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA1EB43E52 for ; Mon, 8 Jul 2002 15:30:12 -0700 (PDT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP id GQF37091; Mon, 08 Jul 2002 15:28:45 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Postfix) with ESMTP id 4A6F85D07; Mon, 8 Jul 2002 15:30:11 -0700 (PDT) To: chris-freebsd@randomcamel.net Cc: Sean Chittenden , freebsd-mobile@freebsd.org Subject: Re: pcm0 not responding on -CURRENT... In-reply-to: Your message of "Mon, 08 Jul 2002 14:48:16 PDT." <20020708214816.GA32249@zot.electricrain.com> Date: Mon, 08 Jul 2002 15:30:11 -0700 From: "Kevin Oberman" Message-Id: <20020708223011.4A6F85D07@ptavv.es.net> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Date: Mon, 8 Jul 2002 14:48:16 -0700 > From: Chris Doherty > Sender: owner-freebsd-mobile@FreeBSD.ORG > > At some point, Sean Chittenden said: > > pcm0:play:0: play interrupt timeout, channel dead > [snip] > > My best/wild/flailing guess is that one of the airtools did something > > to my sound card... but I don't know how to reset the hardware config > > for the snd card. eh? -sc > > I get this error reliably on a Thinkpad 600E (under 4.5-stable and > 4.6-stable) when I try to use sound after a suspend. I use bsd-airtools > without any problems, though. I looked at the sound driver source but > haven't had time or motivation to try writing something to reset the > device. :-) The problem here is with the integration of the Crystal Sound driver in pcm with APM. After the card is powered down, it is dead (or worse) until a re-boot initializes it. Waking up from suspend does not do it. Since it's really in an unknown state, it can behave very strangely after a suspend. Dead is probably the best result! This is not the problem seen here. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message