linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philippe Troin <phil@fifi.org>
To: Nicolas Turro <Nicolas.Turro@sophia.inria.fr>
Cc: linux-kernel@vger.kernel.org, amd-dev@cs.columbia.edu
Subject: Re: am-utils or kernel bug ? Seems to be kernel  bug.. Any news ?
Date: 15 Jul 2003 20:28:47 -0700	[thread overview]
Message-ID: <87znjfup3k.fsf@ceramic.fifi.org> (raw)
In-Reply-To: 1058285921.19183.63.camel@atlas.inria.fr

Nicolas Turro <Nicolas.Turro@sophia.inria.fr> writes:

> On Tue, 2003-07-15 at 16:35, Philippe Troin wrote:
> > Nicolas Turro <Nicolas.Turro@sophia.inria.fr> writes:
> > 
> > > Hi, i posted a bug about amd hanging at boot time a few week ago,
> > > does anybody has a fix for it ?
> > > The bug is described here :
> > > 
> > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=90902
> > > 
> > > it seems that several groups of users besides me encounter the same
> > > bug....
> > > 
> > > If not, i'll have to post-install a 2.4.18 kernel on all my new
> > > RH9 boxes :-(
> > 
> > Looks like YAFP (Yet Another Futex Problem).
> > 
> > Have you tried running with LD_ASSUME_KERNEL=2.2.5 ?
> 
> You are right, setting LD_ASSUME_KERNEL=2.2.5 (or
> LD_ASSUME_KERNEL=2.4.1) corrects the problem.
> Do you have more info on this ´bug'  ?

As a rule of thumb, whenever a program deadlocks in a futex call,
setting this variable to a < 2.5.x value might prevent the deadlock.
Google around for the exact reason why.

AFAIU, it's a RH 9.0 bug.

Phil.

      reply	other threads:[~2003-07-16  3:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15  8:34 am-utils or kernel bug ? Seems to be kernel bug.. Any news ? Nicolas Turro
2003-07-15 14:35 ` Philippe Troin
2003-07-15 16:18   ` Nicolas Turro
2003-07-16  3:28     ` Philippe Troin [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=87znjfup3k.fsf@ceramic.fifi.org \
    --to=phil@fifi.org \
    --cc=Nicolas.Turro@sophia.inria.fr \
    --cc=amd-dev@cs.columbia.edu \
    --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 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 NNTP newsgroup(s).