linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Marek Behun <marek.behun@nic.cz>
Cc: "Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
	"Bjorn Helgaas" <helgaas@kernel.org>,
	linux-pci@vger.kernel.org,
	"Grégory Clement" <gregory.clement@free-electrons.com>,
	"Antoine Ténart" <antoine.tenart@free-electrons.com>,
	"Miquèl Raynal" <miquel.raynal@free-electrons.com>
Subject: Re: pci-aardvark ath9k arm64 issues
Date: Tue, 16 Jan 2018 11:21:53 +0100	[thread overview]
Message-ID: <20180116112153.5cd06eb0@windsurf> (raw)
In-Reply-To: <20180113002234.0ae646d6@nic.cz>

Hello Marek,

Thanks for your bug report!

On Sat, 13 Jan 2018 00:22:34 +0100, Marek Behun wrote:

> we are having a CPU stall issue with ath9k driver on pci-aardvark
> (Marvell Armada 3720 (arm64)).
> 
> The ath9k driver loads correctly and the interface connects and for
> some time it works correctly, but then CPU stalls and kernel dumps
> self-detected stall on CPU.
> 
> I don't know if this is issue with aardvark or whole arm64 (someone had
> a similar problem, see
> https://www.spinics.net/lists/linux-wireless/msg157038.html ), but
> ath10k doesn't have this problem.
> 
> I am attaching the rcu_sched stall detection backtrace (although I
> don't know if contains needed information).
> 
> Can you please point me how to debug/solve this issue?

Could you try to apply the following patches ?

  https://patchwork.ozlabs.org/patch/819586/
  https://patchwork.ozlabs.org/patch/819589/
  https://patchwork.ozlabs.org/patch/819587/
  https://patchwork.ozlabs.org/patch/819592/
  https://patchwork.ozlabs.org/patch/819590/
  https://patchwork.ozlabs.org/patch/819591/
  https://patchwork.ozlabs.org/patch/819588/

And see if it helps? If it does help, could you try with just
https://patchwork.ozlabs.org/patch/819592/ applied ?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      parent reply	other threads:[~2018-01-16 10:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-12 23:22 pci-aardvark ath9k arm64 issues Marek Behun
2018-01-16 10:09 ` Lorenzo Pieralisi
2018-01-16 10:21 ` Thomas Petazzoni [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=20180116112153.5cd06eb0@windsurf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=antoine.tenart@free-electrons.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=helgaas@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=marek.behun@nic.cz \
    --cc=miquel.raynal@free-electrons.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;
as well as URLs for NNTP newsgroup(s).