X-Spam-Check-By: sourceware.org
Message-ID: <4643C865.70606@sun.com>
Date: Thu, 10 May 2007 15:35:33 -1000
From: Joseph Kowalski <jek3 AT sun DOT com>
User-Agent: Thunderbird 1.5.0.5 (X11/20060925)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: DualCores and Current Cygwin problems
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com


Rene Berber wrote:

 > My problem, I think, is a bad network driver... or at least it takes 
too long for it to "start up". The network card is surely completely 
different from what you use (an Intel PRO/1000 MT with driver from Intel.

Don't be too sure.  The configuration I described also has an Intel 
PRO/1000 MT with driver from Intel (via Microsoft).

Another experiment I didn't mention is I loaded the same software stack 
on to another machine with a single core processor (Shuttle FX41).  It 
also has an Intel PRO/1000 MT.  It showed no problems.

However, I suspect this is just coincidence.  My build is "network 
silent".  The network adapter shouldn't be involved.

- Joseph Kowalski

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/