On 09/05/2012 04:41 PM, Eddie Wai wrote: > Hello Mike, > > The reason why the bnx2 nic somethings yield a 0 MAC is because of a > handshake race condition exist between the driver reading this info and > the running firmware. The reliability is based upon the firmware being > settled down after being reset/downloaded which would only be guaranteed > after executing the ifup procedure. Without up-ing to the corresponding > interface, the MAC matching would sometimes fail. > > Although this might sound like a workaround for our solution, I think > ensuring the corresponding L2 interface to be up prior to iboot is > nonetheless the right thing to do...
Agree. Merged in commit f0a8c95426d21413d9980d31740e193208e3280e. > > Eddie > > On Wed, 2012-09-05 at 16:15 -0500, Mike Christie wrote: >> On 09/05/2012 04:14 PM, Eddie Wai wrote: >>> This is needed for the iSCSI offload boot. >>> >>> Snip from M. Christie: >>> Note that we must bring up the interface before >>> iface_setup_from_boot_context, >>> because we will want iscsi_sysfs_get_host_no_from_hwaddress to be able to >>> match >>> a MAC to a iscsi host. For some bnx2i cards, the card has to be ifupd for >>> the >>> iscsi interface to have a MAC. If it is not ifupd we have seen MACs with all >>> zeros or no iscsi_hosts on different cards. >>> >> >> Did you figure out why it sometimes needs to be brought up and why it >> sometimes does not? Was it a user error on my part? >> > > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
