From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: Meelis Roos <mroos-Y27EyoLml9s@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
linux-parisc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: zalon scsi WARNINGs at kernel/dma/mapping.c:290 dma_free_attrs+0x5c/0x84
Date: Tue, 19 Feb 2019 16:16:09 +0100 [thread overview]
Message-ID: <20190219151609.GA4121@lst.de> (raw)
In-Reply-To: <f7cf6b8f-671b-e01f-fa1f-6ca82c4af819-Y27EyoLml9s@public.gmane.org>
On Tue, Feb 19, 2019 at 12:57:18AM +0200, Meelis Roos wrote:
> I tried latest Linux on HP A180C (32-bit pa-risc). It works but the Zalon SCSI driver barfs warnings for GSC addon differential scsi board.
>
> The warnings seem to be DMA API related. Packaged 4.19 and self-compiled 5.0.0-rc7 exhibit the same problem.
It looks like the driver is trying to free DMA coherent memory with irqs
disabled, which is a big no-go on most non-coherent architectures (which
includes parisc).
The DMA coherent code in this driver is pretty convoluted, but I'll see
what I can do. The warning has been there for a couple kernel release,
and the issue basically goes back to day 0 of support for non-coherent
architectures.
prev parent reply other threads:[~2019-02-19 15:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 22:57 zalon scsi WARNINGs at kernel/dma/mapping.c:290 dma_free_attrs+0x5c/0x84 Meelis Roos
[not found] ` <f7cf6b8f-671b-e01f-fa1f-6ca82c4af819-Y27EyoLml9s@public.gmane.org>
2019-02-19 15:16 ` Christoph Hellwig [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=20190219151609.GA4121@lst.de \
--to=hch-jcswghmuv9g@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-parisc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mroos-Y27EyoLml9s@public.gmane.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