Date: Thu, 20 Jul 2017 02:56:45 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 220872] ixv driver 12.0 crash in AWS/EC2 Message-ID: <bug-220872-8@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220872 Bug ID: 220872 Summary: ixv driver 12.0 crash in AWS/EC2 Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: jwjerni@g.clemson.edu 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. Let me know if I can provide any further information. Thanks, James -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-220872-8>