From nobody Sat Aug 20 18:45:31 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4M96y41nbGz4Z0Fv for ; Sat, 20 Aug 2022 18:45:32 +0000 (UTC) (envelope-from verm@darkbeer.org) Received: from mx.coeval.ca (mx.coeval.ca [184.75.211.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4M96y35Btsz3l8Z for ; Sat, 20 Aug 2022 18:45:31 +0000 (UTC) (envelope-from verm@darkbeer.org) Received: from mx.darkbeer.org (unknown [192.168.211.20]) by mx.coeval.ca (Postfix) with ESMTP id 1B87343605C for ; Sat, 20 Aug 2022 18:45:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=darkbeer.org; s=mail; t=1661021131; bh=NZvJrBN93UYE8trFv3Dxc0uNi15/Lx8zOQbiCX2Cp0Q=; h=Date:From:To:Subject:References:In-Reply-To; b=rc5M/BbxeJe2SZGTQ35HDlW/0FkWIa33hvj2LxjVUbRV5RvndSX6WrJPk4+rHs6rn KLz+e2RqL6GV8tULq8j2SivfKGssuUxAdtWPOZ+RbW7U1f5NBLqKGfxmaH/r1A2abY MAWU5QbkL8+4m90al2dUjd6OgkQd5w/KMa1pn3Ms= Received: by mx.darkbeer.org (Postfix, from userid 1001) id 17C50470BFD; Sat, 20 Aug 2022 18:45:31 +0000 (UTC) Date: Sat, 20 Aug 2022 18:45:31 +0000 From: Amar Takhar To: freebsd-current@freebsd.org Subject: Re: Status of Alder Lake support Message-ID: <20220820184531.GA6367@darkbeer.org> Mail-Followup-To: freebsd-current@freebsd.org References: <2ba3e191-64c1-b854-3eb3-080345b56839@FreeBSD.org> <20220820181357.GA5624@darkbeer.org> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Rspamd-Queue-Id: 4M96y35Btsz3l8Z X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=darkbeer.org header.s=mail header.b="rc5M/Bbx"; dmarc=none; spf=pass (mx1.freebsd.org: domain of verm@darkbeer.org designates 184.75.211.21 as permitted sender) smtp.mailfrom=verm@darkbeer.org X-Spamd-Result: default: False [-3.50 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.999]; R_DKIM_ALLOW(-0.20)[darkbeer.org:s=mail]; R_SPF_ALLOW(-0.20)[+ip4:184.75.211.21:c]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[darkbeer.org:+]; DMARC_NA(0.00)[darkbeer.org]; ARC_NA(0.00)[]; ASN(0.00)[asn:32489, ipnet:184.75.211.0/24, country:CA]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; TO_DN_NONE(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On 2022-08-20 11:36 -0700, Kevin Oberman wrote: > Wow! That's a little more disturbing.  Especially since it's a i9-12900KF so I have a whole 8 cores disabled! > As to the audio issue, I've been having a similar issue for some time, > especially with Firefox using any of the available audio systems. Works best > with OSS. > > What I hear is not popping, but brief dropouts which I perceived as pops. It > sounds a lot like data rate mismatch where the audio is output at a slightly > faster rate than it is input.  As a result, the buffers empty periodically and > you hear a fraction of a second of silence. Yes exactly. Sorry it's better described as clipping and that is exactly what I thought was happening too. There were some suggestions in that ticket I tried to no avail. It's almost like something is blocking the buffer from being filled. The same issue happens when I use an external USB audio card but it's nowhere near as bad. After this many months I'd like to say I've gotten used to it but some videos are particularly bad so there is some correlation to what audio is being played. > This is not an Alder Lake issue as it's been hitting me on my Comet Lake > processor.  Oh well that's good to know you should update that ticket (#263385) as I've only known Alder Lake to be an issue up to this point. Is this happening on CURRENT? I'll upgrade for sure if I can use my E cores and avoid UFS corruption. Amar.