[Bug 225791] ena driver causing kernel panics on AWS EC2

2018-06-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791 --- Comment #8 from Richard Paul --- Just to help you out with pts - To run the benchmark in pts you need to install it using the phoronix-test-suite package: #~ pkg install phoronix-test-suite #~ phoronix-test

[Bug 225791] ena driver causing kernel panics on AWS EC2

2018-06-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791 --- Comment #7 from Richard Paul --- I missed a couple of configuration options we'd set: -- sysctl: kern.ipc.soacceptqueue: 8192

[Bug 225791] ena driver causing kernel panics on AWS EC2

2018-06-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791 --- Comment #6 from Richard Paul --- Okay, with a bit of effort and this is testing against the v0.7.0 ENA driver on FreeBSD 11.1p11 I got a reboot. But this was not easy to get to reproduce. Here's what I did to get this to die.event

[Bug 222996] FreeBSD 11.1 on Hyper-V with PCI Express Pass Through

2018-06-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #9 from Dmitry --- Created attachment 194707 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=194707&action=edit pciconf -lbv -- You are receiving this mail because: You are the assignee for the bug. _

[Bug 222996] FreeBSD 11.1 on Hyper-V with PCI Express Pass Through

2018-06-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222996 --- Comment #8 from Dmitry --- (In reply to Dexuan Cui from comment #7) here is. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org

[Bug 225791] ena driver causing kernel panics on AWS EC2

2018-06-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791 --- Comment #5 from Richard Paul --- Hi Colin, Thanks for responding to this issue. You're right to point out that this may be down to the difference in hypervisors. M5 seem to be based on HVM too so for our purposes maybe moving over to