From owner-freebsd-current Fri Jan 19 22:43:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 5F0F437B400 for ; Fri, 19 Jan 2001 22:43:38 -0800 (PST) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.11.1/8.11.0) with ESMTP id f0K6haY00891; Fri, 19 Jan 2001 23:43:37 -0700 (MST) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.1/8.8.3) with ESMTP id f0K6gXs19678; Fri, 19 Jan 2001 23:42:33 -0700 (MST) Message-Id: <200101200642.f0K6gXs19678@billy-club.village.org> To: Sean Kelly Subject: Re: pcm status Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sat, 20 Jan 2001 00:24:18 CST." <20010120002418.A4673@edgemaster.zombie.org> References: <20010120002418.A4673@edgemaster.zombie.org> Date: Fri, 19 Jan 2001 23:42:32 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010120002418.A4673@edgemaster.zombie.org> Sean Kelly writes: : I did not have this behavior in -STABLE, but now I do since I upgraded : to -CURRENT. -current's interrupt latency is horrible these days, which seems to manifest itself in problem with the sound driver. I have a -current laptop and get all kinds of artifacts on it. I have a laptop that is running -stable and has 1/3 the power of the -current laptop and plays w/o a hitch. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message