On Mon, Aug 18, 2025 at 10:59:18AM +0200, Jarle Greipsland wrote:
> Greg Troxel <g...@lexort.com> writes:
> > Christof Meerwald <cme...@cmeerw.org> writes:
> >> I am not sure about a missed interrupt (or even anything kernel
> >> related) - wouldn't that also affect pings and TCP connections?
> > 
> > If the disk interrrupts were missed, and network interrupts were ok, it
> > could be consistent.  I'm just guessing.
> > 
> >> To me it would feel more like maybe syslogd blocking on something
> >> (which might then also block anything trying to log something via
> >> syslog)?
> > 
> > I wouldn't expect syslog clients to block.
> > 
> > You also haven't described the machine.  If you're doing anything other
> > than setting YES in rc.conf to start things at boot, please explain.
> > 
> > Also, you could explain the history and frequency.  Did this arise
> > recently?
> To what kind of (virtualized) disk controller is the disk
> connected?

[     1.007675] virtio1 at pci0 dev 4 function 0
[     1.007675] virtio1: SCSI device (id 8, rev. 0x00)
[     1.007675] vioscsi0 at virtio1: features: 0x10000000<INDIRECT_DESC>
[     1.007675] virtio1: allocated 86016 byte for virtqueue 0 for control, size 
256
[     1.007675] virtio1: using 73728 byte (4608 entries) indirect descriptors
[     1.007675] virtio1: allocated 86016 byte for virtqueue 1 for event, size 
256
[     1.007675] virtio1: using 73728 byte (4608 entries) indirect descriptors
[     1.007675] virtio1: allocated 86016 byte for virtqueue 2 for request, size 
256
[     1.007675] virtio1: using 73728 byte (4608 entries) indirect descriptors
[     1.007675] vioscsi0: cmd_per_lun 128 qsize 256 seg_max 254 max_target 255 
max_lun 16383
[     1.007675] virtio1: config interrupting at msix1 vec 0
[     1.007675] virtio1: queues interrupting at msix1 vec 1

[     1.007675] virtio3 at pci0 dev 7 function 0
[     1.007675] virtio3: block device (id 2, rev. 0x00)
[     1.007675] ld0 at virtio3: features: 
0x10000a54<INDIRECT_DESC,CONFIG_WCE,FLUSH,BLK_SIZE,GEOMETRY,SEG_MAX>
[     1.007675] ld0: Unknown SIZE_MAX, assuming 65536
[     1.007675] ld0: max 254 segs of max 65536 bytes
[     1.007675] virtio3: allocated 1060864 byte for virtqueue 0 for I/O 
request, size 256
[     1.007675] virtio3: using 1048576 byte (65536 entries) indirect descriptors
[     1.007675] virtio3: config interrupting at msix3 vec 0
[     1.007675] virtio3: queues interrupting at msix3 vec 1
[     1.007675] ld0: 25600 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 
52428800 sectors

I have now set up a script to send to ps output over UDP to a remote
server (via a wireguard VPN) - let's see if that will show any useful
information.


Christof

-- 
https://cmeerw.org                             sip:cmeerw at cmeerw.org
mailto:cmeerw at cmeerw.org                   xmpp:cmeerw at cmeerw.org

Reply via email to