AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070814115044.03d8e8aa@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<sandrine.boulanger@onstor.com>,<larry.scheer@onstor.com>,<maxim.kozlovsky@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E0267A49B@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Tue, 14 Aug 2007 11:51:08 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Sandrine Boulanger" <sandrine.boulanger@onstor.com>
Cc: Larry Scheer <larry.scheer@onstor.com>, Maxim Kozlovsky
 <maxim.kozlovsky@onstor.com>
Subject: Re: error for eth1 on ssc console for linux on bobcat
Message-ID: <20070814115108.24688a67@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0267A49B@onstor-exch02.onstor.net>
References: <20070814113434.477183f7@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E0267A49B@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

The bug is specific to Bobcat Linux as opposed to Linux in general or
Cougar, so it's not scheduled to be fixed at the moment.  You'll have
to do what testing you can without redundant links until actual cougar
hardware becomes available.

a

 On Tue,
14 Aug 2007 11:35:37 -0700 "Sandrine Boulanger"
<sandrine.boulanger@onstor.com> wrote:

> Has to be fixed before since this interface is mandatory in cluster
> setup for redundancy.
> 
> -----Original Message-----
> From: Andy Sharp 
> Sent: Tuesday, August 14, 2007 11:35 AM
> To: Sandrine Boulanger
> Cc: Larry Scheer; Maxim Kozlovsky
> Subject: Re: error for eth1 on ssc console for linux on bobcat
> 
> Yes, this is a known bug.  Probably won't be fixed until after cougar,
> if there ever is such a time.
> 
> On Tue, 14 Aug 2007 11:27:05 -0700
> "Sandrine Boulanger" <sandrine.boulanger@onstor.com> wrote:
> 
> > eth1: Setting full-duplex based on negotiated link capability.
> > eth1: Tx/Rx process did not stop in 2000 usec.
> > eth1: Wake-up event 0xffffffff
> > eth1: Setting full-duplex based on negotiated link capability.
> > eth1: Tx/Rx process did not stop in 2000 usec.
> > eth1: Wake-up event 0xffffffff
> > eth1: Setting full-duplex based on negotiated link capability.
> > eth1: Tx/Rx process did not stop in 2000 usec.
> > eth1: Wake-up event 0xffffffff
> > eth1: Setting full-duplex based on negotiated link capability.
> > eth1: Tx/Rx process did not stop in 2000 usec.
> > eth1: Wake-up event 0xffffffff
> > eth1: Setting full-duplex based on negotiated link capability.
