Hi
We have been seeing similar behavior for bnx drivers but in a
completely different use case. We loose one of the bnx2 devices in a
network bond after a period of heavy traffic. I include a small
extract from an internal email:

Red Hat bugzilla 520888 describes our symptoms very closely -
unfortunately it hasn't seen much attention. On first contact our RH
TAM has suggested it's related to BZ432451 and that, essentially, a
solution will not be forthcoming, and the only option is to disable
MSI.

Our fix has been to do the following:
modprobe bnx2 disable_msi=1
in /etc/modprobe.conf

This might be related or might not be at all but I thought the problem
similar enough to make mention of it.

Regards

On Thu, Mar 11, 2010 at 8:17 AM, Ciprian Vizitiu (GBIF)
<[email protected]> wrote:
> Murray wrote:
>>
>> While modinfo reports that bnx2i is the iscsi driver for this card, /
>> var/log/messages reports otherwise.
>> What seems to happen is that the system attempts to load the bnx2i
>> module, fails and then falls back to bnx2. This was when I had forced
>> eth1 to use bnx2i via /etc/modprobe.conf :
>>
>> Mar  8 17:51:37 ndsfdh1 kernel: iscsi: registered transport (bnx2i)
>> Mar  8 17:52:48 ndsfdh1 kernel: bnx2: eth1: using MSI
>> Mar  8 17:52:48 ndsfdh1 kernel: bnx2i: iSCSI not supported, dev=eth1
>> Mar  8 17:52:50 ndsfdh1 kernel: bnx2i: iSCSI not supported, dev=eth1
>>
>
> Perhaps a silly question: do you have the "key" so that the Broadcom's
> firmware does accelerated iSCSI?
>
> --
> You received this message because you are subscribed to the Google Groups
> "open-iscsi" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/open-iscsi?hl=en.
>
>



-- 
Gerhardus Geldenhuis

-- 
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/open-iscsi?hl=en.

Reply via email to