I wonder if there have been any bug fixes in that area over the past year or so.
Any help and pointers are welcome.
Hi,
A long time ago I fixed an issue for ARM:
http://svnweb.freebsd.org/changeset/base/265913
I've always wondered why x86 does some fixed amount of idle spins before
going to
On 11/12/2019 13:05, Konstantin Belousov wrote:
> On Wed, Dec 11, 2019 at 12:48:36PM +0200, Andriy Gapon wrote:
...
>> tdq_oldswitchcnt = 26, tdq_lowpri = 92 '\\', tdq_ipipending = 0 '\000',
>> tdq_idx
...
> What is the value of tdq_ipipending ?
> See https://reviews.freebsd.org/D22758
It's
On 11/12/2019 12:48, Andriy Gapon wrote:
> So, if I am not confused, it appears like possibly a notification from a
> waking
> CPU to the woken CPU (CPU3) was never delivered.
> Potentially, a problem with cpu_idle_wakeup() ?
>
> I wonder if there have been any bug fixes in that area over the
On Wed, Dec 11, 2019 at 12:48:36PM +0200, Andriy Gapon wrote:
>
> I am investigating a problem that originally looked like a ZFS I/O hang.
> But it quickly became obvious that the GEOM "up" queue was not being
> processed.
> (kgdb) p g_bio_run_up
> $54 = {bio_queue = {tqh_first =
I am investigating a problem that originally looked like a ZFS I/O hang.
But it quickly became obvious that the GEOM "up" queue was not being processed.
(kgdb) p g_bio_run_up
$54 = {bio_queue = {tqh_first = 0xf801d8627178, tqh_last =
0xf80134751658}, bio_queue_lock = {lock_object =
