From: Nicolas Turro <Nicolas.Turro@sophia.inria.fr>
To: Ion Badulescu <ionut@badula.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: FW: am-utils or kernel bug ? Seems to be kernel or glibc bug...
Date: 14 May 2003 10:27:41 +0200 [thread overview]
Message-ID: <1052900861.24411.121.camel@atlas.inria.fr> (raw)
In-Reply-To: <Pine.LNX.4.44.0305132214120.2091-100000@moisil.badula.org>
On Wed, 2003-05-14 at 04:23, Ion Badulescu wrote:
> > > i am running Redhat 9.0 ( kernel 2.4.20 )
> > > and am-utils (am-utils-6.0.9-2) (because i need the browsing
feature
> > > that automount doen't support).
> > >
> > > Unfortunatelly, amd sometimes hangs at boot time during its
> > > initialization (/etc/rc.d/init.d/amd ).
> > > I can reproduce this bug with /etc/rc.d/init.d/amd start / stop
> > > sequences, sometimes the start hangs sometimes it works.
> > > This bug occurs on ALL RedHat 9.0 boxes we have (7 PC with totally
> > > different hardware).
...
> > > [root@redhat-serv root]# strace -p 2454
> > > futex(0x4212e1c8, FUTEX_WAIT, -2, NULL <unfinished ...>
> > >
> > >
> > > [root@redhat-serv root]# strace -p 2455
> > > select(1024, [4 5 6 7], NULL, NULL, {932, 980000} <unfinished ...>
>
> I'll be damned if I understand what the futex is used for here. But since
> that's the parent amd, presumably it's waiting for the child to complete
> something, probably a mount.
>
> As for the second trace, we need to know what the four filedescriptors are
> for. 'lsof -p 2455' should shed some light...
>
> I suspect either a bug in glibc (likely), or a bug in the way amd uses
> some Unix primitives and which just happen to work on older glibc's (less
> likely). It's going to be rather hard to debug, however, if we can't
> reproduce it locally.
>
> Another suggestion I have is this: boot into an older kernel without futex
> support (2.4.18-27.7.x should do just fine, ignore the missing
> dependencies because they are not fatal). Glibc will adjust to the older
> kernel and use other mechanisms, and we'll see if the hang still occurs.
> Basically, since futexes were back-ported by Red Hat from 2.5 kernels, I
> suspect there might be some bugs or races in there, and this test would
> help to clear it out.
You were right, Ion,
switching to a RH8 kernel ( 2.4.18-14 ) , solved the issue. I cannot
reproduce this futex bug on the father process...
Who should i contact in order to correct things ?
--
Nicolas Turro <Nicolas.Turro@sophia.inria.fr>
INRIA
next parent reply other threads:[~2003-05-14 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0305132214120.2091-100000@moisil.badula.org>
2003-05-14 8:27 ` Nicolas Turro [this message]
2003-05-14 13:35 ` FW: am-utils or kernel bug ? Seems to be kernel or glibc bug Ion Badulescu
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=1052900861.24411.121.camel@atlas.inria.fr \
--to=nicolas.turro@sophia.inria.fr \
--cc=ionut@badula.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.