mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Pignat <marc.pignat@hevs.ch>
To: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Cc: Ben Nizette <bn@niasdigital.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: Wed, 9 Apr 2008 14:00:55 +0200	[thread overview]
Message-ID: <200804091400.56727.marc.pignat@hevs.ch> (raw)
In-Reply-To: <20080406181817.5824f962@siona.local>

On Monday 07 April 2008, Haavard Skinnemoen wrote:
> On Sun, 06 Apr 2008 09:28:38 +1000
> Ben Nizette <bn@niasdigital.com> wrote:
> 
> > Hi,
> > 
> > For some weeks now there have been reports flying across the main AVR32
> > support forum, avrfreaks [1], that atmel_spi now hard-hangs on most
> > transfers.  The behaviour is not apparent in .23 and is in .24+.  One
> > tester was good enough to bisect the problem and turned up
> 
> Thanks for reporting this.
> 
> > 154443c72f47169ebcb3a7befbff0e934c49bff3
> > atmel_spi: chain DMA transfers
> > 
> > as the culprit.  The tester also had to revert 
> > 
> > commit 8bacb219018a52e6f02a3cff6a7badf102ddfc44
> > atmel_spi: fix dmachain oops with DEBUG enabled
> > 
> > when they reverted 154443 as they were not confident enough to resolve
> > the conflicts that resulted from just reverting the first one.
> 
> That is indeed the correct way to resolve the conflict since the latter
> fixes a bug introduced by the former.
> 
> > The discussion thread involving this can be seen at [2].
> > 
> > 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).

> 
> 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.

Regards

Marc


  reply	other threads:[~2008-04-09 12:01 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 [this message]
2008-04-09 21:50     ` Ben Nizette
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=200804091400.56727.marc.pignat@hevs.ch \
    --to=marc.pignat@hevs.ch \
    --cc=bn@niasdigital.com \
    --cc=haavard.skinnemoen@atmel.com \
    --cc=kernel@avr32linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --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®