AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070814120709.00b8d79a@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<larry.scheer@onstor.com>,<sandrine.boulanger@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	BB375AF679D4A34E9CA8DFA650E2B04E0221597D@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Tue, 14 Aug 2007 12:07:20 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Larry Scheer" <larry.scheer@onstor.com>
Cc: "Sandrine Boulanger" <sandrine.boulanger@onstor.com>, "Maxim Kozlovsky"
 <maxim.kozlovsky@onstor.com>
Subject: Re: error for eth1 on ssc console for linux on bobcat
Message-ID: <20070814120720.04c2b501@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0221597D@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E0267A49C@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E0221597D@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

Let's discuss at the cougar meeting today.  You will be there, right
Sandrine?  It's at 2 in Hawaii.

Cheers,

a

On Tue, 14 Aug 2007 11:55:19 -0700 "Larry Scheer"
<larry.scheer@onstor.com> wrote:

> I think we want to start filing defects against cougar in ClearQuest
> if I am remembering what Tim said correctly. Max, Andy, any comment?
> Much of what we find in Bobcat-Linux applies to Cougar as well. For
> instance the unusual mgmt vsvr name is a candidate for cougar defect.
> 
> But in this case this defect is specific to bobcat-linux so maybe we
> have a separate category for bobcat-linux kernel bugs?
> 
> -----Original Message-----
> From: Sandrine Boulanger 
> Sent: Tuesday, August 14, 2007 11:43 AM
> To: Andy Sharp
> Cc: Larry Scheer; Maxim Kozlovsky
> Subject: RE: error for eth1 on ssc console for linux on bobcat
> 
> By the way, where do we keep track of existing defects for Cougar
> right now?
> 
> -----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.
