linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stef Simoens <stef.simoens@scarlet.be>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: BUG in dma-mapping.h:218 // MESH SCSI driver not working
Date: Fri, 24 Jul 2009 18:52:33 +1000	[thread overview]
Message-ID: <1248425553.25467.20.camel@pasglop> (raw)
In-Reply-To: <4A68E1CE.4040307@scarlet.be>

On Fri, 2009-07-24 at 00:18 +0200, Stef Simoens wrote:
> I tried the latest 2.6.31-rc3-git3 (without any other patch).
> However, I have the same behaviour as the patched 2.6.30 (so: no BUG, 
> but the mesh_abort messages).
> 
> Anybody knows what's going wrong, and how to fix it? I've read the 
> history of this list of June and July ... but I didn't find any other 
> reports of the problem I'm encountering...
> 
Would it be possible for you to roughly find out at what kernel version
it stopped working ? (Some kernels may need my patch to avoid crashing)

I have a machine with a MESH here that -appears- to work, at least it
did last time I tried it which was a couple of weeks ago, I'll try again
just to be sure.

Cheers,
Ben.

  reply	other threads:[~2009-07-24  8:52 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 [this message]
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

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=1248425553.25467.20.camel@pasglop \
    --to=benh@kernel.crashing.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).