[DRBD-user] DRBD serious locking due to TOE

Ben Clewett ben at roadrunner.uk.com
Fri Dec 14 17:50:37 CET 2007



Florian,

Thanks for the advise.

 > - You mention "NetXtreme II BCM5708 1000Base-SX" cards.
 >   2. I believe the chipset identifier you mentioned is wrong, should
 > be "BCM5708S". Whether or not these differ greatly from their copper 
sibling

'dmesg' is telling me  it is BCM5708.  I don't know how reliable that is.

Also I am not using SELinux.

My efforts to upgrade the Firmware are going slowly.  HP label my 
'Broadcom NetXtreme II BCM5708 1000Base-SX' as an 'HP NC373F 1000SX'. 
They offer a tool to take this to version 2.0.9 from 2007-11-03.   But 
the upgrade software tells me I don't have an 'HP NC*' installed, which 
is a little confusing.

When I have worked it out, I will let you know if this has sorted the 
problem.

Ben Clewett.




Florian Haas wrote:
> Ben,
> 
> On Friday 14 December 2007 16:09:44 Ben Clewett wrote:
>> Hi Dr J Pelan,
>>
>> My name sake Ben Lavender solved his similar problem by entirely
>> disabling ToE, by removing a form of jumper on the NIC PCB.
>>
>> I am still trying the fix Florian suggested.  However this has made no
>> difference yet.
>>
>> Since I have the same chip set as Ben, all be it on a different NIC, I
>> think this suggests some bug on the NIC card firmware.  (Since DELL
>> actually added a jumper to their NIC to disable ToE, it might suggest
>> they are worried about it's effect on the NIC, despite the drivers used.
>>   But on the from HP version...)
> 
> OK, if you are really suspecting a hardware issue, and before you accidentally 
> run off on an irrelevant tangent, try to establish whether Ben Lavender's 
> issue really applies to you. Maybe he can jump in on this if he's still 
> monitoring the list. A few things that come to mind:
> 
> - Ben mentiones "onboard Broadcom Gigabit Ethernet NICs" in his 
> August/September thread. I don't think he ever mentioned his actual chipset, 
> or even whether he's using the bnx2 or the old tg3 driver.
> 
> - You mention "NetXtreme II BCM5708 1000Base-SX" cards.
>   1. This is a FO card, not a copper interface like Ben's.
>   2. I believe the chipset identifier you mentioned is wrong, should 
> be "BCM5708S". Whether or not these differ greatly from their copper sibling 
> in chipset terms I don't know.
>   3. I know of at least a revision 11 and 12 I've seen of that chipset 
> recently, so find out what revision your hardware is and attempt to correlate 
> with Ben's.
> 
> - Ben's system ran with SELinux enabled, I don't know if yours does.
> 
>> There is a new version of the firmware out there which I have just
>> found, so this must be my next option....
> 
> Possibly, but as I said be warned not to draw premature conclusions from 
> similarities to an earlier issue someone mentioned on this list, whose 
> circumstances may or may not match yours. YMMV. Please share your results.
> 
> Florian
> 


*************************************************************************
This e-mail is confidential and may be legally privileged. It is intended
solely for the use of the individual(s) to whom it is addressed. Any
content in this message is not necessarily a view or statement from Road
Tech Computer Systems Limited but is that of the individual sender. If
you are not the intended recipient, be advised that you have received
this e-mail in error and that any use, dissemination, forwarding,
printing, or copying of this e-mail is strictly prohibited. We use
reasonable endeavours to virus scan all e-mails leaving the company but
no warranty is given that this e-mail and any attachments are virus free.
You should undertake your own virus checking. The right to monitor e-mail
communications through our networks is reserved by us

  Road Tech Computer Systems Ltd. Shenley Hall, Rectory Lane, Shenley,
  Radlett, Hertfordshire, WD7 9AN. - VAT Registration No GB 449 3582 17
  Registered in England No: 02017435, Registered Address: Charter Court, 
  Midland Road, Hemel Hempstead,  Hertfordshire, HP2 5GE. 
*************************************************************************



More information about the drbd-user mailing list