https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253860
Mark Linimon changed:
What|Removed |Added
Status|Closed |Open
Resolution|FIXED
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253860
--- Comment #11 from Joshua Kinard ---
(In reply to John Baldwin from comment #10)
Already opened Bug #276587 for my issue, since this one was closed, so my bad.
I've added the procstat -kk output there.
--
You are receiving this mail b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253860
--- Comment #10 from John Baldwin ---
Perhaps stay with this bug for now, but can you get 'procstat -kk ' for
the sysctl process when it hangs as the next debugging step?
--
You are receiving this mail because:
You are the assignee for th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253860
--- Comment #9 from Joshua Kinard ---
(In reply to John Baldwin from comment #8)
It didn't take long, but I've actually found a new problem w/ ccp(4), and
that's "sysctl -a" haning if ccp is loaded and is being used by something (in
my cas
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253860
John Baldwin changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253860
--- Comment #7 from Joshua Kinard ---
FYI, it looks like ccp(4) got some kind of fixing in 14.0-RELEASE and it now
appears to work on my Ryzen 3 2200G:
dmesg:
> # dmesg | grep ccp
> ccp0: mem 0xfc70-0xfc7f,0xfc884000-0xfc885fff ir
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253860
--- Comment #6 from Andriy Gapon ---
(In reply to Joshua Kinard from comment #5)
Who knows... there is no public documentation for it.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253860
--- Comment #5 from Joshua Kinard ---
Just ran into this on my NAS box which has an AMD Ryzen 3 2200G CPU, running
13.0-RELEASE-p6. If this hardware didn't generate an interrupt under both
FreeBSD and Linux, is it a hardware bug of some ki
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253860
--- Comment #4 from Andriy Gapon ---
I can also add that on my Ryzen 3 3200U with Radeon Vega Mobile the hardware
looked like it worked but it never generated an interrupt (or, at least, it was
never received). Tested with both our ccp and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253860
--- Comment #3 from Conrad Meyer ---
Sure, let’s disable it.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.fre
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253860
--- Comment #2 from Alan Somers ---
I found an earlier bug about a panic; I didn't find any about a hang. Should
we disable ccp from the GENERIC build?
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253860
--- Comment #1 from Conrad Meyer ---
I think there is an earlier ccp/geli bug you can dupe this to. I suggest not
loading ccp.ko.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253860
Bug ID: 253860
Summary: ccp(4) immediately hangs when creating geli device
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
S
13 matches
Mail list logo
