From: Jens Axboe <axboe@suse.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: mikem <mikem@beardog.cca.cpqcorp.net>,
akpm@osdl.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, sitniko@infonet.ee
Subject: Re: [PATCH 1/3] cciss: bug fix for hpacucli
Date: Mon, 21 Nov 2005 18:45:29 +0100 [thread overview]
Message-ID: <20051121174529.GJ15804@suse.de> (raw)
In-Reply-To: <438205EC.9040906@zytor.com>
On Mon, Nov 21 2005, H. Peter Anvin wrote:
> mikem wrote:
> >>
> >>This sort-of makes it work. I get some complaints about unaligned access
> >>when setting up a test array:
> >>
> >>=> controller slot=0 create type=logicaldrive drives=all raid=1
> >>drivetype=sas
> >>.hpacucli(12458): unaligned access to 0x60000fffffcb370e,
> >>ip=0x40000000003c8550
> >>=> controller slot=0 create type=logicaldrive drives=all raid=1
> >>drivetype=sata
> >>.hpacucli(12458): unaligned access to 0x60000fffffcb4aee,
> >>ip=0x40000000003c8550
> >>.hpacucli(12458): unaligned access to 0x60000fffffcb370e,
> >>ip=0x40000000003c8550
> >>.hpacucli(12458): unaligned access to 0x60000fffffcb370e,
> >>ip=0x40000000003c8550
> >
> >This seems to be coming out of user space. We'll work with the application
> >folks to investigate. There is a library called infomanager that's used
> >by the app. There may be an issue there. Call you strace the program and
> >send me the results? I haven't seen this in my lab with a vendor kernel.
> >
>
> What machine is this for? For x86-64, the above are non-canonical
> addresses. IA64?
Yup, ia64.
--
Jens Axboe
next prev parent reply other threads:[~2005-11-21 17:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 16:33 [PATCH 1/3] cciss: bug fix for hpacucli mikem
2005-11-18 20:49 ` Jens Axboe
2005-11-21 8:28 ` Jens Axboe
2005-11-21 16:46 ` mikem
2005-11-21 17:23 ` Jens Axboe
2005-11-21 17:37 ` H. Peter Anvin
2005-11-21 17:45 ` Jens Axboe [this message]
2005-11-18 21:45 ` Philippe Pegon
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=20051121174529.GJ15804@suse.de \
--to=axboe@suse.de \
--cc=akpm@osdl.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mikem@beardog.cca.cpqcorp.net \
--cc=sitniko@infonet.ee \
/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.