From: Ben Nizette <bn@niasdigital.com>
To: Marc Pignat <marc.pignat@hevs.ch>
Cc: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>,
kernel <kernel@avr32linux.org>,
slipszi@gmail.com, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUG, bisected] atmel_spi: hard lockups in transfer
Date: Thu, 10 Apr 2008 07:50:49 +1000 [thread overview]
Message-ID: <1207777849.3327.6.camel@moss.renham> (raw)
In-Reply-To: <200804091400.56727.marc.pignat@hevs.ch>
On Wed, 2008-04-09 at 14:00 +0200, Marc Pignat wrote:
> > Ben Nizette <bn@niasdigital.com> wrote:
> >
> > As I say, this is present in .24+ so any fix will be a stable candidate
> > as well as .25 material (if we haven't missed the boat by then).
> mainline .24+ is not affected (linux-2.6.24.3.atmel.3.tar.bz2 is).
>
Hmm, I was sure I'd seen reports on vanilla kernels too. I've confirmed
it's present in avr32-2.6.git/master/HEAD and the patch is in mainline
so I would expect the bug to be there, even if the symptoms are lacking.
Adding #define DEBUG to the top of atmel_spi.c changed the point at
which the bug triggers, there may be a similar coincidental
alignment-of-the-planets in mainline which means this bug doesn't
trigger at all.
Hmm..
> >
> > I'm afraid I don't have much time to look at this right now...but I'll
> > see what I can do. It's strange that I never noticed this problem
> > myself -- I did see some overrun issues, but I blamed it on the
> > throughput improvements and just reduced the speed slightly.
> This patch seems to have problems at least on avr32, since this is only
> a speed-up patch, we should revert them.
I would think that's a good move in the short term but obviously speed
is a good thing and I would really like to see us get to the bottom of
this :-)
--Ben.
next prev parent reply other threads:[~2008-04-09 22:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-05 23:28 Ben Nizette
2008-04-06 22:18 ` Haavard Skinnemoen
2008-04-09 12:00 ` Marc Pignat
2008-04-09 21:50 ` Ben Nizette [this message]
2008-04-07 0:24 ` Szilveszter Ordog
2008-04-08 5:33 ` Ben Nizette
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=1207777849.3327.6.camel@moss.renham \
--to=bn@niasdigital.com \
--cc=haavard.skinnemoen@atmel.com \
--cc=kernel@avr32linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.pignat@hevs.ch \
--cc=slipszi@gmail.com \
/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®