Hi James,

Thanks for reporting this. If you don’t mind, please file a bug here: 
https://bugs.freebsd.org/bugzilla/enter_bug.cgi so this doesn’t fall off our 
radar. We’re pretty sure we know what is happening and how to fix it. 
Basically, the Linux PF driver that AWS is using doesn’t support mailbox API 
version 1.2. The latest released Linux PF driver does, but we can’t control 
what driver AWS uses. To work around this, we need a to add a failover to ixv 
so it can fall back to 1.1.

Thanks.
Jeff

On 7/12/17, 9:11 PM, "owner-freebsd-...@freebsd.org on behalf of James 
Jernigan" <owner-freebsd-...@freebsd.org on behalf of jwje...@g.clemson.edu> 
wrote:

    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
    _______________________________________________
    freebsd-net@freebsd.org mailing list
    https://lists.freebsd.org/mailman/listinfo/freebsd-net
    To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
    

_______________________________________________
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Reply via email to