From: Allan Schrum <aschrum@ecdeliverysystems.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: [1.7] Pipes intermittently lose data on Cygwin 1.7
Date: Tue, 23 Dec 2008 03:03:00 -0000 [thread overview]
Message-ID: <9BE596E8BDDC3443BF23B9678D03CC2928DF6EA0@ECDS-CLT-MX1.ecdeliverysystems.com> (raw)
In-Reply-To: <49504CA2.5040200@i12.com>
> -----Original Message-----
> From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On
> Behalf Of Lawrence Mayer
> Sent: Monday, December 22, 2008 9:28 PM
> To: cygwin@cygwin.com
> Subject: Re: [1.7] Pipes intermittently lose data on Cygwin 1.7
>
> On 081222 16:48, Allan Schrum wrote:
> > The numbers 5,132,288 and 5,138,895 are multiples of 4096.
>
> Thanks for writing Allan. I think you mean 5,132,288 and 5,136,384 (the
> two output sizes) are multiples of 4096.
>
Yes - thanks - copying too many numbers can result in silly errors.
> > Lawrence: what is the hardware that your are running this test upon?
> What other processes are running at the same time (e.g. CPU usage, I/O
> usage, etc.)?
>
> Please see my previous post, where I found the same bug on different
> hardware running a different OS. Here are more details:
>
> Computer 1 (from my original post):
> Motherboard: Shuttle AK31 v3.1
> Chipset: Via KT266 northbridge, VT8233 southbridge
> CPU: Athlon XP 2000+ @ 2 GHz
> Memory: 512 MB DDR
> OS: Windows Server 2003 sp2 32 bit on NTFS
> CPU usage: 0-1% normally, 22-23% max during Cygwin tests
> Handles 3907 Threads 192 Processes 23
> Commit Charge (K): Total 294448 Limit 533992 Peak 426364
> Physical Memory (K): Total 523752 Available 180124 System Cache 235732
> Kernel Memory (K): Total 53912 Paged 34284 Nonpaged 19628
>
>
> Computer 2 (from my previous post):
> Motherboard: MSI K7N2 Delta
> Chipset: Nvidia Nforce2
> CPU: Athlon XP 3200+ @ 2.13 GHz
> Memory: 2 GB DDR
> OS: Windows XP Home sp2 32 bit on NTFS
> CPU usage: 0-1% normally, 21-22% max during Cygwin tests
> Handles 3904 Threads 193 Processes 23
> Commit Charge (K): Total 717884 Limit 1964364 Peak 841376
> Physical Memory (K): Total 2096624 Available 1161980 System Cache
> 1298916
> Kernel Memory (K): Total 104788 Paged 76104 Nonpaged 28696
>
Would it be worth trying to heavily load one of your computers to see if the problem presents itself differently? It is obvious that your systems are fast!
--
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/
next prev parent reply other threads:[~2008-12-23 3:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-20 9:15 Lawrence Mayer
2008-12-20 20:31 ` Lawrence Mayer
2008-12-22 17:32 ` Christopher Faylor
2008-12-22 18:32 ` Lawrence Mayer
2008-12-22 18:47 ` Christopher Faylor
2008-12-22 20:07 ` Lawrence Mayer
2008-12-22 22:41 ` Christopher Faylor
2008-12-23 0:28 ` Lawrence Mayer
2008-12-23 19:00 ` Christopher Faylor
2008-12-23 20:32 ` Lawrence Mayer
2008-12-23 0:49 ` Allan Schrum
2008-12-23 2:36 ` Lawrence Mayer
2008-12-23 3:03 ` Allan Schrum [this message]
2008-12-23 6:43 ` Lawrence Mayer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9BE596E8BDDC3443BF23B9678D03CC2928DF6EA0@ECDS-CLT-MX1.ecdeliverysystems.com \
--to=aschrum@ecdeliverysystems.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).