SCIENTIFIC-LINUX-USERS Archives

March 2009

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV
Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
Mailling list for Scientific Linux users worldwide <[log in to unmask]>
Date:
Tue, 31 Mar 2009 09:39:35 +0200
MIME-version:
1.0
Reply-To:
Stephan Wiesand <[log in to unmask]>
Content-type:
TEXT/PLAIN; format=flowed; charset=US-ASCII
Subject:
Re: SL5.2 Machine freeze due to CPU100% in relation with the bond0 module
From:
Stephan Wiesand <[log in to unmask]>
In-Reply-To:
<[log in to unmask]>
Comments:
To: Jean-Michel Barbet <[log in to unmask]> cc: "[log in to unmask]" <[log in to unmask]>
Parts/Attachments:
TEXT/PLAIN (31 lines) 
On Tue, 31 Mar 2009, Jean-Michel Barbet wrote:

> Michael Mansour wrote:
>
>> For this (on a 5.2 i386 box), I have:
>> options bond0 mode=1 miimon=100 use_carrier=1
>> and it's never failed.
>
> Thanks Michael, it could be x86_64 specific maybe...

Or it could be pure statistics. It also depends on usage. We're seeing 
this problem frequently lately (x86_64, kernels 91.1.6 and 92.1.22 at 
least). Out of a few dozen nodes with two bonded GbE links, one or two 
per week develop such a soft lockup. It seems to be much more likely to 
happen when the links are very busy.

The latest kernel (128.1.1) has a fix in the locking code in the bonding 
module, so this one may fix it.

Any insights very welcome, since this problem is quite serious for 
us as well.

Regards,
 	Stephan

-- 
Stephan Wiesand
   DESY - DV -
   Platanenallee 6
   15738 Zeuthen, Germany

ATOM RSS1 RSS2