From: Andi Kleen <ak@muc.de>
To: Chris Meadors <clubneon@hereintown.net>
Cc: 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: Thu, 21 Aug 2003 23:00:42 +0200 [thread overview]
Message-ID: <m3r83en2th.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <n4o5.8ga.21@gated-at.bofh.it> (Chris Meadors's message of "Thu, 21 Aug 2003 22:40:13 +0200")
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.
>
> I've tried -test3-bk9 and also went back to -test2 and -test1.
>
> Earlier when playing with this machine I built 2.6.0-test3 with a 32 bit
> only version of gcc, but still optimized for the Opteron. This one had
> no problem booting and mounting the XFS root.
>
> This is easy to reproduce, so let me know if more information is needed.
I test XFS (but not as root) occasionally on x86-64 and seen no problems
so far. I haven't tested it with test2+ yet though.
What compiler are you using?
-Andi
next parent reply other threads:[~2003-08-21 21:01 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 [this message]
2003-08-22 0:55 ` Hang when mounting XFS root in 2.6.0 tests on x86-64 Steve Lord
2003-08-22 9:26 ` Andi Kleen
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=m3r83en2th.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=clubneon@hereintown.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.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 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.