linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: alex@digriz.org.uk (Alexander Clouter)
To: linux-arm-kernel@lists.infradead.org
Subject: Kirkwood/OpenRD-Base System Crash from DMA
Date: Sat, 16 Jan 2010 00:16:13 +0000	[thread overview]
Message-ID: <d3d727-505.ln1@chipmunk.wormnet.eu> (raw)
In-Reply-To: 20100116001307.GH16062@voodoowarez.com

rektide <rektide@voodoowarez.com> wrote:
>
> I'm attempting to use 2.6.32.3 on a Kirkwood/OpenRD-Base system.  This 
> system has been serving fine playing MP3's via PulseAudio and MPD for 
> >5 months now.  However other activities will sometime cause the 
> system to lock up.  The most reliable activity is to do a "git pull", 
> from anywhere.  Secondly, writing files onto the system via a Samba 
> share causes a lockup.
> 
> [snipped]
> 
> There's a thread on the OpenRD google group with multiple people confirming the issue:
> http://groups.google.com/group/openrd/browse_thread/thread/d435787eb4e4ffd0
> 
> One person has confirmed the issue goes away when CONFIG_NET_DMA and 
> CONFIG_ASYNC_TX_DMA are disabled.  I'm building a kernel now to 
> confirm this myself, and will report back tomorrow.
> 
I can say it's a "me too" on mine, however I never reported the issue as 
it's a known problem:

http://marc.info/?l=linux-raid&m=123606440522693&w=2

I ran into it on a USB key RAID setup when I started up a huge rsync.  I 
didn't even get a trace in that situation, just a hard lockup.

Not looked at it since.

Cheers

-- 
Alexander Clouter
.sigmonster says: A dwarf is passing out somewhere in Detroit!

      reply	other threads:[~2010-01-16  0:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-16  0:13 Kirkwood/OpenRD-Base System Crash from DMA rektide
2010-01-16  0:16 ` Alexander Clouter [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=d3d727-505.ln1@chipmunk.wormnet.eu \
    --to=alex@digriz.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).