public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marco Roeland <marco.roeland@xs4all.nl>
To: Marco Fais <marco.fais@abbeynet.it>
Cc: Marco Roeland <marco.roeland@xs4all.nl>, linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at page_alloc.c:98 -- compiling with distcc
Date: Mon, 5 Apr 2004 13:46:50 +0200	[thread overview]
Message-ID: <20040405114650.GA16079@localhost> (raw)
In-Reply-To: <407137FD.3040407@abbeynet.it>

On Monday April 5th 2004 Marco Fais wrote:

> I was not saying *this is the problem*, just noticing that all the 
> systems that show this problem have this network card, while the other 
> systems that are working perfectly are using other network hardware 
> (e100 driver) :)

Yes, my conclusion was too hasty, it *is* driver related! ;-)

With hindsight we also should have tried, of course, a 'strace distccd
--no-detach' in a crashing and a non-crashing situation. This would
probably have shown that 'sendfile()' was the first missing system call
(and therefore likely the culprit) in the crashing situation. Oh, well...
 
> If you read Andrew's message, seems that distcc uses a function that 
> trigger the problem -- sendfile() -- so, if netcat doesn't use it, it's 
> clear why doesn't panic the kernel.

Yes, sendfile() in combination with the 8139too driver seems to be
causing the trouble. Until that will hopefully be fixed, it doesn't seem
easy to workaround against. At the moment it looks like it is not an
easy configurable option to *not* want to use zero_copy functionality,
either in the kernel, nor in distcc.

There is an '8139cp' driver too, it's supposed to be working better
as well, perhaps that one might not free the pages that are to be
zero_copied across the network before they are sent?! That is the real
problem if I understand Andrew's mail correctly.

You might send a 'linux 8139too sendfile() panic' kind of bugreport
to the 'netdev@oss.sgi.com' mailing list. That is the list where the
networking gurus are supposed to be hanging out. Although IMVHO this bug
is more on the kernel than on the network side. Also filing an entry to
bugzilla.kernel.org might speed up someone fixing the real problem.

Easiest workaround might be to just use a customised distcc for the
machines involved: just download the source from 'distcc.samba.org', do
a regular './configure', and then in the generated 'src/config.h' hand
edit '#undef HAVE_SENDFILE' and '#undef HAVE_SYS_SENDFILE_H'. That
should stop distcc from using sendfile().
-- 
Marco Roeland

  reply	other threads:[~2004-04-05 11:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-02 10:21 kernel BUG at page_alloc.c:98 -- compiling with distcc Marco Fais
2004-04-02 13:15 ` Marco Roeland
     [not found]   ` <6.0.0.22.2.20040402163334.02abe7d8@pop.localnet>
2004-04-02 15:05     ` Marco Roeland
2004-04-05 10:42       ` Marco Fais
2004-04-05 11:46         ` Marco Roeland [this message]
2004-04-05 14:08           ` Marco Fais
2004-04-05 14:36             ` Marco Roeland
2004-04-05 17:03       ` Max Valdez
2004-04-02 23:36 ` Andrew Morton
2004-04-05 10:47   ` Marco Fais
2004-04-05 10:56     ` Andrew Morton
2004-04-05 13:58       ` Marco Fais
2004-05-04  1:07 ` Marcelo Tosatti
2004-05-05 16:25   ` Carson Gaspar
2004-05-05 16:28     ` Marc-Christian Petersen
2004-05-05 18:35     ` Marcelo Tosatti
2004-05-19 11:59       ` Marcelo Tosatti
2004-05-19 15:50         ` Marc-Christian Petersen
2004-05-20 12:21           ` Marcelo Tosatti
2004-05-19 20:21         ` Carson Gaspar
  -- strict thread matches above, loose matches on Subject: below --
2004-04-23 22:33 Carson Gaspar
2004-04-28  2:02 ` Jeff Moyer
2004-04-29 21:09   ` Marcelo Tosatti
2004-04-29 21:28     ` Andrew Morton
2004-04-29 22:49       ` Andrea Arcangeli
2004-04-29 23:26         ` Andrew Morton
2004-04-30  0:15           ` Andrea Arcangeli

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=20040405114650.GA16079@localhost \
    --to=marco.roeland@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marco.fais@abbeynet.it \
    /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