From: Clemens Schwaighofer <cs@tequila.co.jp>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: 2.6.7 and khelper
Date: Fri, 25 Jun 2004 19:04:04 +0900 [thread overview]
Message-ID: <40DBF894.5000306@tequila.co.jp> (raw)
In-Reply-To: <20040624184749.008358b0.akpm@osdl.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andrew Morton wrote:
| Strange. I assume that what's happening is that the children of khelper
| are being created and are dying, and init is somehow seeing this happen.
| Maybe SIGCHLD, probably via wait4(). Perhaps init should be changed
to not
| complain about processes which it did't parent. But then, that should
| already be the case.
|
|
| Could you please apply the below debug patch, then send us all the
relevant
| syslog output, including the messages from init?
I have applied the patch against a vanilla 2.6.7, but until now i
haven't got any output. But after the next crontab run, I'll see that.
I'll push that later.
- --
Clemens Schwaighofer - IT Engineer & System Administration
==========================================================
TEQUILA\Japan, 6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN
Tel: +81-(0)3-3545-7703 Fax: +81-(0)3-3545-7343
http://www.tequila.co.jp
==========================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFA2/iUjBz/yQjBxz8RAit0AJ9pt1gKbEfyvTQRQuAjN15Wsj1MugCgr6I+
wqHSBXyxgsCbDaKVHSVIs1I=
=6wlJ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-06-25 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-25 0:50 2.6.7 and khelper Clemens Schwaighofer
2004-06-25 1:47 ` Andrew Morton
2004-06-25 10:04 ` Clemens Schwaighofer [this message]
2004-06-25 10:56 ` Matthias Urlichs
2004-06-28 0:29 ` Clemens Schwaighofer
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=40DBF894.5000306@tequila.co.jp \
--to=cs@tequila.co.jp \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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