mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Steve Lord <lord@sgi.com>
Cc: ak@muc.de, clubneon@hereintown.net, linux-kernel@vger.kernel.org,
	linux-xfs@oss.sgi.com
Subject: Re: Hang when mounting XFS root in 2.6.0 tests on x86-64
Date: Fri, 22 Aug 2003 11:26:42 +0200	[thread overview]
Message-ID: <20030822112642.46d3f538.ak@suse.de> (raw)
In-Reply-To: <1061513734.1622.55.camel@laptop.americas.sgi.com>

On 21 Aug 2003 19:55:32 -0500
Steve Lord <lord@sgi.com> wrote:

> On Thu, 2003-08-21 at 16:00, Andi Kleen wrote:
> > Chris Meadors <clubneon@hereintown.net> writes:
> > 
> > Better report it to linux-xfs@oss.sgi.com (cc'ed) too.
> > 
> > > I'm trying to get a 2.6.0-test kernel to boot on my Opteron system.  It
> > > has SuSE's 2.4.19-SMP kernel on it now, and it boots with that, mounts
> > > the XFS root just fine.  But I build a vanilla 2.6.0-test3 with no
> > > module support, everything included that I would need.  The last line
> > > that it prints during boot is the NET4.0
> > >
> > > Repeated presses of Alt+SysRq+P seems to show RIP looping in xfs_xlatesb
> > > and xfs_lowbit64.
> 
> Seems to suggest a platform specific problem with this code, Andi,
> didn't you write the function behind xfs_lowbit64?

First at least the comment on top of xfs_lowbit64() is not correct.
ffs() only handles an 32bit argument, not 64bit. Hope that isn't a problem.

Hmm, one difference is that the x86-64 ffs will return 32 on zero, while
i386 returns -1.

Does this patch fix it?

--- linux-2.6.0test3-amd64/include/asm-x86_64/bitops.h-o	2003-07-11 13:34:21.000000000 +0200
+++ linux-2.6.0test3-amd64/include/asm-x86_64/bitops.h	2003-08-22 11:17:53.000000000 +0200
@@ -466,7 +466,7 @@
 
 	__asm__("bsfl %1,%0\n\t"
 		"cmovzl %2,%0" 
-		: "=r" (r) : "g" (x), "r" (32));
+		: "=r" (r) : "g" (x), "r" (-1));
 	return r+1;
 }
 

If that doesn't help I would also try it with -O1 and possibly a different compiler
(e.g. gcc 3.2 if you're using 3.3 or the other way round) to rule out a compiler problem
 
-Andi



  reply	other threads:[~2003-08-22  9:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <n4o5.8ga.21@gated-at.bofh.it>
2003-08-21 21:00 ` Andi Kleen
2003-08-22  0:55   ` Steve Lord
2003-08-22  9:26     ` Andi Kleen [this message]
2003-08-22 19:34       ` Chris Meadors
2003-08-22  6:53   ` Seth Mos
2003-08-21 20:21 Chris Meadors

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=20030822112642.46d3f538.ak@suse.de \
    --to=ak@suse.de \
    --cc=ak@muc.de \
    --cc=clubneon@hereintown.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=lord@sgi.com \
    /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

all inboxes | Powered by JetHome®