Date: Thu, 13 Jul 2017 00:11:43 -0400 From: James Jernigan <jwjerni@g.clemson.edu> To: freebsd-net@freebsd.org Subject: ixv driver 12.0 crash in AWS Message-ID: <CAK6pMswaS62v8%2BBBDP667yKuruSOjsNEm0k4GZWG6a%2BADwBBHA@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hey freebsd net, I have created a few instances in AWS using the lastest AMI for the CURRENT branch: FreeBSD 12.0-CURRENT-amd64-2017-07-11 (ami-847b7992) A couple of these have started up just fine, but the rest of the instances are inaccessible due to the network driver crashing on startup and rendering the machines inaccessible by SSH. I have one working instance, but even creating more based off of that configuration are failing to start networking properly. Restarting the instances does not fix the problem. I have pulled the following logs from the AWS web console for two m4.10xlarge instances with the same configuration and AMI. Working instance: > ixv0: <Intel(R) PRO/10GbE Virtual Function Network Driver, Version - > 1.5.13-k> mem 0xf3000000-0xf3003fff,0xf3004000-0xf3007fff at device 3.0 on > pci0 > ixv0: Using MSI-X interrupts with 2 vectors > ixv0: Ethernet address: 0a:2f:e8:85:2f:38 > ixv0: netmap queues/slots: TX 1/1024, RX 1/1024 Malfunctioning instance: > ixv0: <Intel(R) PRO/10GbE Virtual Function Network Driver, Version - > 1.5.13-k> mem 0xf3000000-0xf3003fff,0xf3004000-0xf3007fff at device 3.0 on > pci0 > ixv0: MBX API 1.2 negotiation failed! Error -32 The error appears to be coming from sys/dev/ixgbe/if_ixv.c in the source. Does this appear to be an AWS specific issue or a more widespread one? Let me know if I can provide any further information. Thanks, James
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAK6pMswaS62v8%2BBBDP667yKuruSOjsNEm0k4GZWG6a%2BADwBBHA>