https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
Mark Johnston changed:
What|Removed |Added
Status|Open|In Progress
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #80 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=015daf5221f7588b9258fe0242cee09bde39fe21
commit 015daf5221f7588b9258fe0242cee09bde39fe21
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #79 from Alexander Sherikov ---
(In reply to Mark Johnston from comment #76)
Works for me on Tuxedo laptop
(https://bsd-hardware.info/?probe=6f779d5170#pci:1002-1637-1d05-109f), FreeBSD
15.0-CURRENT #2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
Graham Perrin changed:
What|Removed |Added
Keywords|needs-qa|
Severity|Affects Only
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #78 from Mark Johnston ---
(In reply to Ivan Rozhuk from comment #77)
Because they do not fix the underlying problem, and the second check is
incorrect.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #77 from Ivan Rozhuk ---
(In reply to Mark Johnston from comment #76)
Why not add additional checks from
https://bugs.freebsd.org/bugzilla/attachment.cgi?id=244703=diff ?
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #76 from Mark Johnston ---
https://reviews.freebsd.org/D41883
Any additional testing would be welcome.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #75 from Oleh Hushchenkov ---
(In reply to Mark Johnston from comment #74)
I got it. Thank you Mark.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #74 from Mark Johnston ---
(In reply to Oleh Hushchenkov from comment #69)
The right way is option number 3. I'll get a patch along those lines reviewed
and committed later this week.
--
You are receiving this mail because:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #73 from Oleh Hushchenkov ---
(In reply to Warner Losh from comment #71)
So how it should be fixed it the right way?
The issue affects many different laptops/computers, looks like AMD based only.
Thas said we can't blame
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #72 from Ivan Rozhuk ---
(In reply to Oleh Hushchenkov from comment #69)
I suggest commit 2 and 3 together to make sure that we never see this panic
again.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #71 from Warner Losh ---
This and Mark's comment lead me to believe we are getting stray interrupts of
various flavors. The 0xfff hack will keep things working while we're
accessing the device in an isr with the card
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #70 from Oleh Hushchenkov ---
(In reply to Mark Johnston from comment #68)
> I'm not particularly sure why my commit would introduce a problem there.
I'm not familiar with the code base, but for me it looks like D34117 added
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #69 from Oleh Hushchenkov ---
(In reply to Mark Johnston from comment #68)
Just moved hdac_irq_alloc() call in hdac_attach() to be after the
hdac_rirb_init() call and rebuilt the kernel.
It fixed the issue for me.
Now I'm
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #68 from Mark Johnston ---
(In reply to Jonathan Vasquez from comment #18)
Looking at this log, it seems that we're getting an interrupt before hdac2 has
finished initializing itself. In particular, hdac_attach() allocates an
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #67 from Oleh Hushchenkov ---
(In reply to Ivan Rozhuk from comment #66)
> Can you please test attached patch?
> (it use continue instead break on NULL pointer)
Attached patch also works for me.
No panic on first boot, sound
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #66 from Ivan Rozhuk ---
(In reply to Oleh Hushchenkov from comment #64)
Can you please test attached patch?
(it use continue instead break on NULL pointer)
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #65 from Ivan Rozhuk ---
Created attachment 244703
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=244703=edit
patch
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #64 from Oleh Hushchenkov ---
(In reply to Ivan Rozhuk from comment #63)
This one also avoids crash on first boot.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #63 from Ivan Rozhuk ---
Why no one suggest patch like this?
diff --git a/sys/dev/sound/pci/hda/hdac.c b/sys/dev/sound/pci/hda/hdac.c
index 82b1baacfa9..f7be436aef6 100644
--- a/sys/dev/sound/pci/hda/hdac.c
+++
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
Ivan Rozhuk changed:
What|Removed |Added
CC||rozhuk...@gmail.com
--- Comment #62
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #60 from Oleh Hushchenkov ---
(In reply to John Grafton from comment #59)
> We tested reverting the patch completely in comment #34 and Jonathan reported
> that the sound didn't work but the system booted.
I see.
> Removing
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #59 from John Grafton ---
(In reply to Oleh Hushchenkov from comment #58)
We tested reverting the patch completely in comment #34 and Jonathan reported
that the sound didn't work but the system booted.
Removing 'intsts !=
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
Oleh Hushchenkov changed:
What|Removed |Added
CC||o.hushchen...@gmail.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #57 from John Grafton ---
(In reply to Warner Losh from comment #54)
You mean like this?
diff --git a/sys/dev/sound/pci/hda/hdac.c b/sys/dev/sound/pci/hda/hdac.c
index 79ab71516cd9..78c99db8e813 100644
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
Mark Linimon changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
Mark Linimon changed:
What|Removed |Added
CC||mate...@yahoo.com
--- Comment #56
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
Mark Linimon changed:
What|Removed |Added
CC||dii...@freebsd.org
--- Comment #55
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
Warner Losh changed:
What|Removed |Added
CC||i...@freebsd.org
--- Comment #54
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
Graham Perrin ◐ changed:
What|Removed |Added
CC||grahamper...@gmail.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
Mark Linimon changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
Mark Linimon changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
Alexander Sherikov changed:
What|Removed |Added
CC||asheri...@yandex.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
Graham Perrin changed:
What|Removed |Added
Keywords||crash
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #46 from John Grafton ---
Thanks for the bug report. Hopefully someone finds it helpful in the future.
Sorry we didn't get it fixed!
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #44 from John Grafton ---
(In reply to Jonathan Vasquez from comment #43)
Huh, likely a driver problem then. Have you tested booting a 13.0 or 12.x
kernel on this system? I'm wondering if the problem was introduced in 13.1.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #38 from John Grafton ---
Hi Jonathan,
You have a common sound chipset that comes with a lot of recent AMD
motherboards (within last couple of years). Here's a link to systems that have
run a BSD hardware probe that have your
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #35 from John Grafton ---
Created attachment 241461
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=241461=edit
delay driver attach by 10 ms
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #34 from John Grafton ---
Created attachment 241460
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=241460=edit
revert commit that coincides with occurance of problem
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #33 from John Grafton ---
Interesting! Okay, I have a couple of patches for you to try. The first patch
reverts a commit to hdac.c that may have caused the problem to occur. The
second patch introduces a delay before the driver
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #29 from John Grafton ---
(In reply to Jonathan Vasquez from comment #28)
Yes, compile using the GENERIC kernel config, it includes the witness debugger.
Then boot from the kernel as normal and see if the system still crashes.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #27 from John Grafton ---
Created attachment 241040
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=241040=edit
lock hdac during init
I have a theory that an interrupt is being triggered before the dma memory is
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #23 from John Grafton ---
(In reply to Jonathan Vasquez from comment #22)
The duplicate comment was just to alert FreeBSD devs that this issue may be
affecting others with the same hardware.
No problem about the dmesg buffer,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #21 from John Grafton ---
Hi Jonathan,
Is the hot boot dmesg output truncated or was that all of it? From the output
it appears hdac2 isn't properly initialized. The ring buffer read pointer
(rirb_rp) starts at 189 instead
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #20 from John Grafton ---
This bug appears to be a duplicate of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264305
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #16 from John Grafton ---
(In reply to Jonathan Vasquez from comment #14)
Hi Jonathan,
All of the crash dump reports you posted appear to have panicked in the
hdac_rirb_flush function. Specifically dereferencing the `rirb`
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
--- Comment #15 from John Grafton ---
Created attachment 240647
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=240647=edit
debugging printfs for hda driver
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
John Grafton changed:
What|Removed |Added
CC||john.graf...@runbox.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393
Graham Perrin changed:
What|Removed |Added
Status|New |Open
CC|
49 matches
Mail list logo