On 3/3/2020 6:04 PM, Mark Saad wrote:
> Mike
> Not the best solution but switch from “latest” to “quarterly” in the pkg
> config . The quarterly repos are unaffected.
Thanks! That will be good enough for this project and works for now
---Mike
_
I met an Issue:
When I kldload jedec_dimm durig runtime, it works just as expected,
and the DIMM data appears in sysctl.
But when I do
* load the jedec_dimm at the loader prompt, or
* add it to loader.conf, or
* compile it into a custom kernel,
it does not boot anymore.
My custom kernel doe
Front up: I do not like loadable modules. They are nice to try
something out, but when you start to depend on some dozen loaded
modules, debugging becomes a living hell: say you hunt some spurious
misbehaviour and compare logfiles with those from four weeks ago,
you will not know exactly which modu
On Wed, Mar 4, 2020 at 9:14 AM Peter wrote:
>
> I met an Issue:
>
> When I kldload jedec_dimm durig runtime, it works just as expected,
> and the DIMM data appears in sysctl.
>
> But when I do
> * load the jedec_dimm at the loader prompt, or
> * add it to loader.conf, or
> * compile it into a
On 04.03.2020 19:09, Peter wrote:
I met an Issue:
When I kldload jedec_dimm durig runtime, it works just as expected,
and the DIMM data appears in sysctl.
But when I do
* load the jedec_dimm at the loader prompt, or
* add it to loader.conf, or
* compile it into a custom kernel,
it does n
Hi everyone,
a recent 12-stable rev 358557 amd64 build hangs on kldunload of
geom_journal.
To reproduce:
kldload geom_journal
kldunload geom_journal
kldunload just hangs indefinitely. top says the state is "jfini:". It's
using some cpu time though.
procstat -k hangs as well.
Very reproduc
On Wed, Mar 04, 2020 at 11:41:22PM +0300, Yuri Pankov wrote:
! On 04.03.2020 19:09, Peter wrote:
! > When I kldload jedec_dimm durig runtime, it works just as expected,
! > and the DIMM data appears in sysctl.
! >
! > But when I do
! > * load the jedec_dimm at the loader prompt, or
! > * add i
Hi Dewayne,
Sorry for the delay. Unfortunately, I can't really suggest anything -
it's not clear to me why ntpd would prefer a stratum 14 clock over a
stratum 2 clock. Have you tried looking through the debugging hints
page (https://www.eecis.udel.edu/~mills/ntp/html/debug.html)?
I haven't seen
