X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7DEA6.7190E046@onstor-exch02.onstor.net>; Tue, 14 Aug 2007 11:08:05 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: error for eth1 on ssc console for linux on bobcat
Date: Tue, 14 Aug 2007 11:08:05 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0267A4A2@onstor-exch02.onstor.net>
In-Reply-To: <20070814120720.04c2b501@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: error for eth1 on ssc console for linux on bobcat
Thread-Index: AcfeplcNHXBDhOUHR46x6t+d2g7rPgAAAlJw
From: "Sandrine Boulanger" <sandrine.boulanger@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	"Larry Scheer" <larry.scheer@onstor.com>
Cc: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>

Yes, I'll be there since my other meeting is cancelled today.

-----Original Message-----
From: Andy Sharp=20
Sent: Tuesday, August 14, 2007 12:07 PM
To: Larry Scheer
Cc: Sandrine Boulanger; Maxim Kozlovsky
Subject: Re: error for eth1 on ssc console for linux on bobcat

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.
>=20
> But in this case this defect is specific to bobcat-linux so maybe we
> have a separate category for bobcat-linux kernel bugs?
>=20
> -----Original Message-----
> From: Sandrine Boulanger=20
> 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
>=20
> By the way, where do we keep track of existing defects for Cougar
> right now?
>=20
> -----Original Message-----
> From: Andy Sharp=20
> 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
>=20
> Yes, this is a known bug.  Probably won't be fixed until after cougar,
> if there ever is such a time.
>=20
> On Tue, 14 Aug 2007 11:27:05 -0700
> "Sandrine Boulanger" <sandrine.boulanger@onstor.com> wrote:
>=20
> > 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.
