From: Ed L Cashin <ecashin@coraid.com>
To: linux-kernel@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Jim MacBaine <jmacbaine@gmail.com>
Subject: Re: aoe fails on sparc64
Date: Fri, 09 Sep 2005 10:06:12 -0400 [thread overview]
Message-ID: <87r7bygwtn.fsf@coraid.com> (raw)
In-Reply-To: 87ll2agcq0.fsf@coraid.com
Ed L Cashin <ecashin@coraid.com> writes:
...
> Let's take this discussion off the lkml, because I doubt there's a
> problem with the aoe driver in the kernel, and I can easily follow up
> to the lkml with a synopsis if it turns out I'm wrong.
It looks like I was probably wrong. I need to do some debugging, but
the only sparc64 machine here at hand is in use.
If anybody would be up for running 2.6.13 on a sparc64 host and
running tests with a patched aoe driver, please let me know. A test
would look something like this, using an x86 host and a sparc64 host
on the same LAN.
x86$ dd if=/dev/zero of=/tmp/0x1234567 bs=1k count=1 seek=19088742
x86$ vblade 0 1 eth0 /tmp/0x1234567
sparc64$ rmmod aoe
sparc64$ cd ~/linux-2.6.13
sparc64$ patch -p1 < aoe.diff
sparc64$ make && make modules_install
sparc64$ modprobe aoe
I'd email you patches, and you'd email me the printk messages that
show up in the logs. Such help would be much appreciated.
--
Ed L Cashin <ecashin@coraid.com>
next prev parent reply other threads:[~2005-09-09 14:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 13:30 aoe fails on sparc64 Jim MacBaine
2005-08-31 15:50 ` Ed L Cashin
2005-09-01 6:24 ` David S. Miller
2005-09-01 19:13 ` Ed L Cashin
2005-09-01 19:45 ` David S. Miller
2005-09-03 16:06 ` Jim MacBaine
2005-09-06 20:31 ` Ed L Cashin
2005-09-09 14:06 ` Ed L Cashin [this message]
2005-09-16 13:36 ` Ed L Cashin
2005-09-16 20:34 ` David S. Miller
2005-09-16 23:35 ` David S. Miller
2005-09-17 10:10 ` Jim MacBaine
2005-09-18 6:12 ` David S. Miller
2005-09-19 14:24 ` Ed L Cashin
2005-09-19 18:21 ` David S. Miller
2005-09-19 18:29 ` Roland Dreier
2005-09-19 18:38 ` Ed L Cashin
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=87r7bygwtn.fsf@coraid.com \
--to=ecashin@coraid.com \
--cc=davem@davemloft.net \
--cc=jmacbaine@gmail.com \
--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