On Tue, Jul 09, 2024 at 01:10:04AM -0400, George Koehler wrote:
> On Sun, 7 Jul 2024 22:03:20 +0000
> Anon Loli <anonloli@autistici.org> wrote:
> 
> > I've tried the following solution:
> > https://marc.info/?l=openbsd-tech&m=167800286026964&w=2
> > but instead of that line, I purged the 1st line:
> > > case PCI_PRODUCT_AMD_17_HDA:
> > and recompiled, of course
> > I also just tried commenting out that entire IF block just in case, but
> > it did exactly nothing
> 
> Those are not fixes.  You want the diff in
> https://marc.info/?l=openbsd-tech&m=171588776531605&w=2
> 
> This was committed to OpenBSD-current azalia.c r1.287, but you are
> missing it because you are running 7.5.
> --gkoehler

Oh, that sounds and looks promising!
Will it work on 7.5 release?
I believe that azalia.c was changed from 7.5 to -current, even though it says
that both are "revision 1.286", because a few hunks failed, and where it says
to delete this and this and this line, some of those lines differ

I think that line 722 differs, for example in the 7.5 azalia.c it says
> if (intsts & az->pstream.intr_bit) {

and in the patch, it's
> if (intsts &amp; az-&gt; pstream.intr_bit) {

I could update to -current, but I don't feel like updating everything often
(like once a week or something like that)
Let me know your opinion on this matter
I think that a lot of people tell you to update OpenBSD frequent if you're
running -current, but that doesn't make a ton of sense to me, which is probably
because I don't realize how updating works on OpenBSD when it comes to snapshots

I want to test this and make cook this fucking bug so that we can eat it and
move on already... even if it means the trouble of frequent updating, but I'd
like to know more...