From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: James.Bottomley@HansenPartnership.com,
linuxppc-dev@lists.ozlabs.org, linux-scsi@vger.kernel.org,
stef.simoens@scarlet.be
Subject: Re: BUG in dma-mapping.h:218 // MESH SCSI driver not working
Date: Wed, 05 Aug 2009 11:11:50 +1000 [thread overview]
Message-ID: <1249434710.18245.48.camel@pasglop> (raw)
In-Reply-To: <20090805100424U.fujita.tomonori@lab.ntt.co.jp>
On Wed, 2009-08-05 at 10:04 +0900, FUJITA Tomonori wrote:
>
> Looks like that READ CAPACITY fails. We use kmalloc'ed buffer for READ
> CAPACITY so I'm not sure about an alignment issue that you mentioned
> in this thread earlier.
>
> You said your machine with a MESH appears to work. Did you confirm it?
>
Not yet. It's a fishy machine that needs other patches to get back to
working condition, I haven't had time yet (everybody's sick at home so
I've been mostly off the office and the machine is there).
I'm pretty sure the MESH will have issues though if the DMA buffers
aren't at least 16 (or maybe it's 32) bytes aligned. I don't think it's
a cache alignment issue, I suspect it's an issue with the DBDMA engine
queue on those chips though (it -could- be cache coherency bugs too,
never know with those old Apple home made chipsets).
I remember we had problems in the past with IDENTIFY iirc, which would
work normally as kmalloc() would return something cache line aligned...
until one enabled SLAB debugging.
Cheers,
Ben.
prev parent reply other threads:[~2009-08-05 1:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 22:18 BUG in dma-mapping.h:218 // MESH SCSI driver not working Stef Simoens
2009-07-24 8:52 ` Benjamin Herrenschmidt
2009-07-24 11:55 ` Stef Simoens
2010-03-18 23:21 ` Stef Simoens
2010-03-18 23:35 ` Benjamin Herrenschmidt
2009-07-29 18:22 ` Stef Simoens
2009-07-29 23:32 ` Benjamin Herrenschmidt
2009-07-29 23:42 ` Stef Simoens
2009-07-30 0:52 ` Benjamin Herrenschmidt
2009-08-02 8:52 ` Stef Simoens
2009-08-02 23:13 ` Benjamin Herrenschmidt
2009-08-05 1:04 ` FUJITA Tomonori
2009-08-05 1:11 ` Benjamin Herrenschmidt [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=1249434710.18245.48.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=stef.simoens@scarlet.be \
/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).