Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 30 Dec 2020 16:36:23 +0100
From:   Greg KH <gregkh@linuxfoundation.org>
To:     Christian Labisch <clnetbox@gmail.com>
Cc:     stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: sound
Message-ID: <X+yedztHPUK4Qryc@kroah.com>
References: <d1b1e6b0e3af13f3756a34131ffb84df6a209ee0.camel@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <d1b1e6b0e3af13f3756a34131ffb84df6a209ee0.camel@gmail.com>
Precedence: bulk

On Wed, Dec 30, 2020 at 04:26:00PM +0100, Christian Labisch wrote:
> Hello !
> 
> I could need your help ... I have tested the new kernel 5.10.3 and sound doesn't work with this
> version.
> Seems the new Intel audio drivers are the main reason. What can be done ? Do you have any ideas ?
> 
> Intel Catpt driver support is new ... This deprecates the previous Haswell SoC audio driver code
> previously providing the audio capabilities.
> And I am having a Haswell CPU -> Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core
> Processor HD Audio Controller (rev 06)

Can you try 5.10.4?  I think a fix for this is in there as was reported
by another user yesterday.

If not, can you run 'git bisect' on the kernels between the last good
one that worked for you, and the one that doesn't?

thanks,

greg k-h