https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244079
--- Comment #2 from John Hartley ---
Hi Vladimir,
thank you very much for response.
I have done as suggested:
<>
# dmesg | grep USB
uhci0: port 0xb0a0-0xb0bf irq 16 at device
29.0 on pci0
uhci1: port 0xb080-0xb09f irq 17 at device
29.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235856
--- Comment #21 from Colin Percival ---
(In reply to mail from comment #18)
Ruben: Looking at those logs... is the second system in a different timezone
from the first? The first one looks very much like it's glitching when the
'periodic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235856
--- Comment #20 from Colin Percival ---
Hi Ruben,
I'd love to be able to reproduce this -- do you have some sort of "canned
workload" which will do it? I hesitate about asking for access to "live"
systems since as soon as I can reproduce
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235856
--- Comment #19 from m...@rubenvos.com ---
Hi Colin,
After some further thought: If you'd like, we could provision an additional set
of r4/r5 machines and give you access to them?
Kind regards,
Ruben
--
You are receiving this mail becau
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235856
--- Comment #18 from m...@rubenvos.com ---
Hi Colin,
> 1. How repeatable is this? Does it happen to every instance you launch
> (after a variable number of days)?
Unfortunately we are not in the habit of often redeplying our zfs nodes (s
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235856
--- Comment #17 from Alex Dupre ---
(In reply to Colin Percival from comment #16)
Unfortunately I had to switch off those EC2 instances, so I cannot say if it'd
still happen or not.
I didn't try FreeBSD 13 nor AMD instances.
--
You are
