All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Nizette <bn@niasdigital.com>
To: kernel <kernel@avr32linux.org>,
	Haavard Skinnemoen <hskinnemoen@atmel.com>,
	slipszi@gmail.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [BUG, bisected] atmel_spi: hard lockups in transfer
Date: Sun, 06 Apr 2008 09:28:38 +1000	[thread overview]
Message-ID: <1207438118.3319.8.camel@moss.renham> (raw)

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

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.

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

Thanks,
	--Ben.

[1] http://www.avrfreaks.net
[2]
http://www.avrfreaks.net/index.php?name=PNphpBB2&file=viewtopic&t=61891&start=20&sid=ef480fc809343ec9eff35b0cda643ffc

             reply	other threads:[~2008-04-05 23:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-05 23:28 Ben Nizette [this message]
2008-04-06 22:18 ` [BUG, bisected] atmel_spi: hard lockups in transfer Haavard Skinnemoen
2008-04-09 12:00   ` Marc Pignat
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=1207438118.3319.8.camel@moss.renham \
    --to=bn@niasdigital.com \
    --cc=hskinnemoen@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.