From owner-freebsd-current@FreeBSD.ORG Wed Dec 17 01:10:21 2003 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 D8C2516A4CE for ; Wed, 17 Dec 2003 01:10:21 -0800 (PST) Received: from exchange-2.srv.unicore.no (punctilious.unicore.no [213.225.74.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 588C043D4C for ; Wed, 17 Dec 2003 01:10:19 -0800 (PST) (envelope-from ltning@anduin.net) Received: from [10.0.16.10] ([10.0.16.10] unverified) by exchange-2.srv.unicore.no with Microsoft SMTPSVC(5.0.2195.6713); Wed, 17 Dec 2003 10:10:17 +0100 From: Eirik Oeverby To: current@freebsd.org Content-Type: text/plain Message-Id: <1071652230.78487.85.camel@eirik> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Wed, 17 Dec 2003 10:10:30 +0100 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 17 Dec 2003 09:10:17.0925 (UTC) FILETIME=[96F74750:01C3C47D] Subject: Distorted sound on -CURRENT 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: Wed, 17 Dec 2003 09:10:22 -0000 Hi all, For a long time I have had problems with sound on my ThinkPad, which has a rather sucky Crystal chipset. The problems consist of skips and pops and crackles when playing back audio, and makes it hopeless to listen to any kind of music while working (or playing ;). There have been attempts at fixing this earlier, which has helped somewhat, but I always thought this was a problem on my chipset only - but this does not seem to be the case. I have now tested in a machine that has a SB Live! card (snd_emu10k1 module), and I'm experience the same problems, just even more pronounced than with the Crystal chipset. The interesting thing is - this is a non-issue in all 4.x versions of FreeBSD, and it's a non-issue in all other OSes I have tried on the respective computers. I am therefore led to believe there has been some kind of screwup with the PCM or chipset drivers in -CURRENT, or perhaps in some underlying code. This has been a problem atleast since 5.1-RELEASE, and I do believe (but cannot confirm) it was a problem with 5.0-RELEASE aswell. Choice of scheduler (SCHED_4BSD or SCHED_ULE) has no influence, neither has there been any difference before or after the i386 interrupt code switch. I home someone can have a look at this, it is of minor importance but major annoyance - and personally I think it should be (attempted) fixed before 5.2-RELEASE, if possible. It does make a bad impression on people, even in a FreeBSD-house such as the one I am working for right now. Best regards, Eirik Oeverby