Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Thu, 22 Jan 2004 15:44:30 -0500 (EST)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: RE: Win XP crash with inetd  ftp server
In-Reply-To: <NUTMEGUXPXF2aZcdjaS00000190@NUTMEG.CAM.ARTIMI.COM>
Message-ID: <Pine.GSO.4.56.0401221543590.21894@slinky.cs.nyu.edu>
References: <NUTMEGUXPXF2aZcdjaS00000190 AT NUTMEG DOT CAM DOT ARTIMI DOT COM>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 22 Jan 2004, Dave Korn wrote:

> > -----Original Message-----
> > From: cygwin-owner On Behalf Of Charles L. Werner
>
> > My XP Professional SP1 system had a kernel crash apparently
> > related to the tcpip,  related  I believe to the inetd
> > service running Here is the event information
> >
> > Symbolic name:
> > ER_KRNLCRASH_LOG
> > Error code 0000004e, parameter1 00000002, parameter2
> > 00000058, parameter3 0007ff2f, parameter4 00000001.
> >
> > The network adapter os a 3Com Gigabit LOM (3c940)
> >
> > Attached is the cygcheck -svr and the output of netstat -a
> >
> > Have others experienced system crashes with the cygwin inetd service?
> > this has happened several times.
> >
> > When I disabled the inetd service, the sudden crashes ceased.
>
>   Nonetheless, the odds are that this is only indirectly caused by running
> an ftp server.  My bet is that your network card has a buggy driver.  Error
> 0x4e means the virtual memory page frame number list has been corrupted.
> Only a kernel-mode device driver could hope to achieve this.  It may be the
> case that the bug in the device driver is triggered by some ioctl that
> cygwin happens to send that most win32 applications don't, but your best bet
> is still going to be surfing the 3com website and seeing if there's a newer
> version of the driver.
>
>   If you have windbg and the xp debugging symbols installed, you could check
> the memory.dmp file that was created by the bsod.  Or you might wish to run
> the driver verifier on it in order to show that the driver definitely was or
> was not at fault.  However these are fairly advanced topics and it really
> doesn't look like this is a cygwin problem.
>
>     cheers,
>       DaveK

Yeah.  See <http://cygwin.com/acronyms/#BSOD>. ;-)
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
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/