From: Hanna Hawa <hannah@marvell.com>
To: <torvalds@linux-foundation.org>
Cc: <corbet@lwn.net>, <davem@davemloft.net>, <edumazet@google.com>,
<gregkh@linuxfoundation.org>, <griebichler.josef@gmx.at>,
<hannes@redhat.com>, <jbrouer@redhat.com>,
<linux-kernel@vger.kernel.org>, <linux-media@vger.kernel.org>,
<linux-usb@vger.kernel.org>, <mchehab@s-opensource.com>,
<mingo@kernel.org>, <netdev@vger.kernel.org>, <pabeni@redhat.com>,
<peterz@infradead.org>, <riel@redhat.com>,
<stern@rowland.harvard.edu>, <dmaengine@vger.kernel.org>,
<vkoul@kernel.org>, <dan.j.williams@intel.com>,
<nadavh@marvell.com>, <thomas.petazzoni@bootlin.com>,
Omri Itach <omrii@marvell.com>
Subject: Re: dvb usb issues since kernel 4.9
Date: Tue, 17 Jul 2018 14:54:20 +0300 [thread overview]
Message-ID: <1d3d0fe3-bc02-7720-15ac-6bc06e00067c@marvell.com> (raw)
In-Reply-To: <CA+55aFwuAojr7vAfiRO-2je-wDs7pu+avQZNhX_k9NN=D7_zVQ@mail.gmail.com>
Hi,
I'm a software developer working in Marvell SoC team.
I'm facing kernel panic issue while running raid 5 on sata disks
connected to Macchiatobin (Marvell community board with Armada-8040 SoC
with 4 ARMv8 cores of CA72)
Raid 5 built with Marvell DMA engine and async_tx mechanism
(ASYNC_TX_DMA [=y]); the DMA driver (mv_xor_v2) uses a tasklet to clean
the done descriptors from the queue.
The panic (see below) occurs while building the RAID-5 (mdadm) or while
writing/reading to the raid partition.
After some debug/bisect/diff, found that patch "softirq: Let ksoftirqd
do its job" is problematic patch.
- Using v4.14.0 and problematic patch reverted - no timout issue.
- Using v4.14.0 (including softirq patch) and the additional fix
proposed by Linus - no timeout issue.
As others have reported in this thread, the softirq change is causing
some regression.
Would it be possible to either revert the patch or apply a fix such as
the one proposed by Linus ?
Below panic message:
[ 25.371495] mv_xor_v2 f0400000.xor: dma_sync_wait: timeout!
[ 25.377101] Kernel panic - not syncing: async_tx_quiesce: DMA error
waiting for transaction
[ 25.377101]
[ 25.386973] CPU: 0 PID: 1417 Comm: md0_raid5 Not tainted 4.14.0 #16
[ 25.393264] Hardware name: Marvell Armada 8040 DB board (DT)
[ 25.398946] Call trace:
[ 25.401410] [<ffff000008089310>] dump_backtrace+0x0/0x380
[ 25.406831] [<ffff0000080896a4>] show_stack+0x14/0x20
[ 25.411904] [<ffff00000890fa78>] dump_stack+0x98/0xb8
[ 25.416976] [<ffff0000080c8ef0>] panic+0x118/0x280
[ 25.421788] [<ffff000008386a44>] async_tx_quiesce+0x74/0x78
[ 25.427382] [<ffff000008386ca4>] async_memcpy+0x1a4/0x2a0
[ 25.432806] [<ffff000008747f9c>] async_copy_data.isra.16+0x1b4/0x280
[ 25.439186] [<ffff00000874b6fc>] raid_run_ops+0x514/0x1320
[ 25.444694] [<ffff000008751550>] handle_stripe+0x1040/0x2848
[ 25.450377] [<ffff000008752f98>]
handle_active_stripes.isra.28+0x240/0x460
[ 25.457279] [<ffff000008753468>] raid5d+0x2b0/0x450
[ 25.462177] [<ffff00000875ead4>] md_thread+0x104/0x160
[ 25.467338] [<ffff0000080e638c>] kthread+0xfc/0x128
[ 25.472234] [<ffff000008085354>] ret_from_fork+0x10/0x1c
[ 25.477571] Kernel Offset: disabled
[ 25.481073] CPU features: 0x002000
[ 25.484487] Memory Limit: none
[ 25.487556] ---[ end Kernel panic - not syncing: async_tx_quiesce:
DMA error waiting for transaction
[ 25.487556]
Thanks,
Hanna
next prev parent reply other threads:[~2018-07-17 11:58 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <trinity-35b3a044-b548-4a31-9646-ed9bc83e6846-1513505978471@3c-app-gmx-bs03>
[not found] ` <20171217120634.pmmuhdqyqmbkxrvl@gofer.mess.org>
[not found] ` <20171217112738.4f3a4f9b@recife.lan>
[not found] ` <trinity-1fa14556-8596-44b1-95cb-b8919d94d2d4-1515251056328@3c-app-gmx-bs15>
2018-01-06 19:54 ` Mauro Carvalho Chehab
2018-01-06 21:07 ` Aw: " Josef Griebichler
2018-01-06 21:44 ` Alan Stern
2018-01-07 11:03 ` Mauro Carvalho Chehab
2018-01-07 15:41 ` Alan Stern
2018-01-07 17:01 ` Aw: " Josef Griebichler
2018-01-08 9:43 ` Mauro Carvalho Chehab
2018-01-08 16:10 ` Alan Stern
2018-01-08 16:26 ` Aw: " Josef Griebichler
2018-01-08 16:31 ` Alan Stern
2018-01-08 17:15 ` Aw: " Josef Griebichler
2018-01-08 17:35 ` Alan Stern
2018-01-08 20:40 ` Jesper Dangaard Brouer
2018-01-08 21:31 ` Jesper Dangaard Brouer
2018-01-08 21:44 ` Peter Zijlstra
2018-01-08 22:16 ` Jesper Dangaard Brouer
2018-01-09 16:51 ` Aw: " Josef Griebichler
2018-01-09 17:27 ` Eric Dumazet
2018-01-09 17:48 ` Linus Torvalds
2018-01-09 17:57 ` Eric Dumazet
2018-01-09 18:58 ` Linus Torvalds
2018-01-09 21:48 ` Eric Dumazet
2018-01-10 9:45 ` Jesper Dangaard Brouer
2018-01-12 21:13 ` Mauro Carvalho Chehab
2018-01-12 21:48 ` Eric Dumazet
2018-01-13 9:09 ` Mauro Carvalho Chehab
2018-01-13 10:46 ` Mauro Carvalho Chehab
2018-01-07 21:23 ` Linus Torvalds
2018-01-08 10:02 ` Mauro Carvalho Chehab
2018-01-08 11:59 ` Jesper Dangaard Brouer
2018-01-08 12:53 ` Mauro Carvalho Chehab
2018-01-08 16:25 ` Alan Stern
2018-01-08 17:55 ` Ingo Molnar
2018-01-08 18:32 ` Linus Torvalds
2018-01-08 19:15 ` Alan Stern
2018-01-08 19:51 ` Linus Torvalds
2018-01-09 17:42 ` Mauro Carvalho Chehab
2018-01-09 17:55 ` Linus Torvalds
2018-01-09 21:26 ` Jesper Dangaard Brouer
2018-01-10 3:02 ` Mike Galbraith
2018-07-17 11:54 ` Hanna Hawa [this message]
2018-07-17 17:09 ` Linus Torvalds
2018-07-17 18:07 ` Hanna Hawa
2018-07-17 22:21 ` Mauro Carvalho Chehab
2018-01-26 14:17 ` Mauro Carvalho Chehab
2018-01-26 19:37 ` Mauro Carvalho Chehab
2018-01-29 13:51 ` Mauro Carvalho Chehab
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=1d3d0fe3-bc02-7720-15ac-6bc06e00067c@marvell.com \
--to=hannah@marvell.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=davem@davemloft.net \
--cc=dmaengine@vger.kernel.org \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=griebichler.josef@gmx.at \
--cc=hannes@redhat.com \
--cc=jbrouer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@s-opensource.com \
--cc=mingo@kernel.org \
--cc=nadavh@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=omrii@marvell.com \
--cc=pabeni@redhat.com \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=stern@rowland.harvard.edu \
--cc=thomas.petazzoni@bootlin.com \
--cc=torvalds@linux-foundation.org \
--cc=vkoul@kernel.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
all inboxes | Powered by JetHome®