search for: diagnozed

...t beeing held: rw_enter(&pbuf->b_hdr->b_datalock, RW_READER); err = arc_read_nolock(pio, spa, bp, done, private, priority, flags, arc_flags, zb); rw_exit(&pbuf->b_hdr->b_datalock); <--- THIS ONE The only possiblity was that b_hdr for pbuf was changed somewhere. We diagnozed this further and the b_hdr field is changed in arc_release() function, here: buf->b_hdr = nhdr; Backtrace for this change is the following: arc_release() at arc_release+0x4ec dbuf_write() at dbuf_write+0x26b dbuf_sync_list() at dbuf_sync_list+0x3eb dbuf_sync_list() at dbuf_sync_list+0x17f db...

Hello, I was wondering anyone here could take a look at some issues a NUT user has with the drivers for their devices which seem to report some bogus information at times (numbers out of range, BYPASS/OFF states appearing and disappearing, etc.), or if you could forward the question to some colleagues that can? https://github.com/networkupstools/nut/issues/1895