mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>
Subject: Re: [BUG?] sendfile / distcc
Date: Fri, 12 Sep 2008 09:45:58 +0200	[thread overview]
Message-ID: <1221205558.6407.3.camel@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1221121607.4415.1073.camel@twins.programming.kicks-ass.net>

On Thu, 2008-09-11 at 10:26 +0200, Peter Zijlstra wrote:
> On Wed, 2008-09-10 at 23:44 -0700, Andrew Morton wrote:
> > On Wed, 10 Sep 2008 11:27:51 +0200 Peter Zijlstra <peterz@infradead.org> wrote:
> > 
> > > Hi,
> > > 
> > > I've been seeing this for a while now, but its still present with -rc5+
> > > kernels. Its always the local machine failing, never the remotes.
> > > 
> > > [root@twins linux-2.6-rt]# nice ./k opteron build
> > > time distmake x86_64 O=opteron-build ARCH=x86_64
> > > testing twins:    distccd running
> > > testing opteron:  DOWN
> > > testing taijtu:   distccd running
> > > testing dyad:     distccd running
> > > testing lappy:    host running
> > > testing ubuntu:   host running
> > > DISTCC_HOSTS= twins/8 taijtu/32 dyad/32
> > > DISTCC_DIR=/dev/shm/distcc
> > > DISTCC_SLOTS=72
> > > 
> > > ...
> > > 
> > > distcc[9931] (dcc_writex) ERROR: failed to write: Connection reset by peer
> > > distcc[9931] Warning: failed to distribute /mnt/build/linux-2.6-rt/kernel/fork.c to twins/8, running locally instead
> > > 
> > > ...
> > > 
> > > distcc[12078] (dcc_pump_sendfile) ERROR: sendfile failed: Connection reset by peer
> > > distcc[12078] (dcc_readx) ERROR: unexpected eof on fd4
> > > distcc[12078] (dcc_r_token_int) ERROR: read failed while waiting for token "DONE"
> > > distcc[12078] Warning: failed to distribute /mnt/build/linux-2.6-rt/init/version.c to twins/8, running locally instead
> > > 
> > 
> > distcc is very good at breaking networking.  I assume 2.6.26 is OK?
> 
> I think it was - whew .26 was a long time ago already ;-)
> 
> I'll build and boot one today to confirm.

It seems I can reproduce similar errors with .26 - I'll be traveling
soon and this box is one of those without serial console so It'll have
to wait until I get back.


      reply	other threads:[~2008-09-12  7:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-10  9:27 Peter Zijlstra
2008-09-11  6:44 ` Andrew Morton
2008-09-11  8:26   ` Peter Zijlstra
2008-09-12  7:45     ` Peter Zijlstra [this message]

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=1221205558.6407.3.camel@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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

Powered by JetHome