From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Jarod Wilson <jwilson@redhat.com>
Cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firewire: fw-ohci: sync AT dma buffer before use
Date: Thu, 13 Mar 2008 09:49:03 +0100 [thread overview]
Message-ID: <47D8EA7F.8040703@s5r6.in-berlin.de> (raw)
In-Reply-To: <200803122111.55754.jwilson@redhat.com>
Jarod Wilson wrote:
> On Wednesday 12 March 2008 07:16:43 pm Stefan Richter wrote:
>> Jarod Wilson wrote:
>>> See http://bugzilla.kernel.org/show_bug.cgi?id=9617
>> Alas the panic from comment #10 is still there, i.e. instant crash when
>> plugging in an LSI based CD-RW (shortly after SCSI inquiry) --- but only
>> if CONFIG_DEBUG_PAGEALLOC=y.
>>
>> Jarod, did your crashes happen with CONFIG_DEBUG_PAGEALLOC=n?
>
> No, they're with it turned on (and still on w/this change where it doesn't
> panic). If I run with CONFIG_DEBUG_PAGEALLOC=n, no panic.
So then that's like "my" panic.
The other thing that I see here is that it only happens with my two LSI
based devices (both CD-RWs), always quickly after SCSI inquiry.
I shall test with my Prolific based DVD-RW to find out whether it is
about some requests that are sent to CD/DVD-RWs or about the split
transactions that I get from the LSI bridges. (See bugzilla.)
>> So this patch shouldn't do
>> anything, except that it inserts a call which happens to have barrier
>> characteristics on some platforms.
...and potentially delays execution.
> ...but got lucky in that it actually helps this particular setup (x86_64
> kernel, dual quad-core opteron, 8G RAM, 3 FireWire controllers). Hrm.
Unless you or I spot the real solution earlier, you could also try
replacing your dma_sync_ with mb() and with mdelay() respectively to see
what aspect of the dma_sync_ is fixing your setup. Also move the mb()
to other interesting places of the involved code.
--
Stefan Richter
-=====-==--- --== -==-=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2008-03-13 8:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 21:43 Jarod Wilson
2008-03-12 22:35 ` David Moore
2008-03-12 23:24 ` Stefan Richter
2008-03-12 23:16 ` Stefan Richter
2008-03-13 1:11 ` Jarod Wilson
2008-03-13 8:49 ` Stefan Richter [this message]
2008-03-14 18:26 ` Jarod Wilson
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=47D8EA7F.8040703@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=jwilson@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®