From: Stef Simoens <stef.simoens@scarlet.be>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: BUG in dma-mapping.h:218 // MESH SCSI driver not working
Date: Thu, 30 Jul 2009 01:42:12 +0200 [thread overview]
Message-ID: <4A70DE54.5090406@scarlet.be> (raw)
In-Reply-To: <1248910358.1509.27.camel@pasglop>
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
Benjamin Herrenschmidt schreef:
> On Wed, 2009-07-29 at 20:22 +0200, Stef Simoens wrote:
>
>> 2.6.29 works OK
>> 2.6.30-rc1 doesn't work (BUG...)
>> 2.6.30-rc1 with your patch ... seems to hang when it should be
>> mounting the root directory.
>>
>> Is it worthwhile doing a git bisect?
>>
>
> It probably is, since it should work with my patch, so something else
> changed, maybe in the SCSI stack.
>
What would be the best approach?
- if the kernel boots, it's obviously 'good'
- but what if the kernel hits the 'BUG', should I apply your patch then?
If it doesn't work with your patch, would it be 'bad' then?
> One thing I know is that the MESH HW has "issues" that make it very
> sensitive to alignment DMA buffers, it's possible that the SCSI stack no
> longer aligns some stuff ?
>
Hmm, great... how can I verify this?
--
Regards,
Stef Simoens
[-- Attachment #2: Type: text/html, Size: 1422 bytes --]
next prev parent reply other threads:[~2009-07-29 23:42 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 [this message]
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
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=4A70DE54.5090406@scarlet.be \
--to=stef.simoens@scarlet.be \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).