https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235856
--- Comment #10 from m...@rubenvos.com --- Hmm. We have a standby machine for this instance (same specs) that has similar log entries, but has not "frozen" yet: Nov 18 16:51:32 zfs02 kernel: link is UP Nov 18 16:55:50 zfs02 kernel: nvme1: Missing interrupt Nov 18 17:01:39 zfs02 dhclient[75125]: send_packet6: Network is down Nov 18 17:01:39 zfs02 dhclient[75125]: dhc6: send_packet6() sent -1 of 52 bytes Nov 19 03:30:59 zfs02 kernel: nvme1: cpl does not map to outstanding cmd Nov 19 03:30:59 zfs02 kernel: cdw0:00000000 sqhd:0006 sqid:0001 cid:000d p:0 sc:00 sct:0 m:0 dnr:0 Nov 19 03:30:59 zfs02 kernel: nvme1: Resetting controller due to a timeout. Nov 19 03:30:59 zfs02 kernel: nvme1: resetting controller Nov 19 03:30:59 zfs02 kernel: nvme1: temperature threshold not supported Nov 19 03:30:59 zfs02 kernel: nvme1: aborting outstanding i/o Nov 19 03:31:28 zfs02 dhclient[75125]: send_packet6: Network is down Nov 19 03:31:28 zfs02 dhclient[75125]: dhc6: send_packet6() sent -1 of 52 bytes Nov 19 03:31:29 zfs02 kernel: Nov 19 03:31:29 zfs02 kernel: stray irq260 I'm curious when the "freezing" will initiate... Is there any way to increase the verbosity / usefullness of the logs? -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
