NetBSD Problem Report #48572

From martin@duskware.de  Wed Feb  5 09:28:57 2014
Return-Path: <martin@duskware.de>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "Postmaster NetBSD.org" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 9135FA6482
	for <gnats-bugs@gnats.NetBSD.org>; Wed,  5 Feb 2014 09:28:57 +0000 (UTC)
From: martin@NetBSD.org
Reply-To: martin@NetBSD.org
To: gnats-bugs@NetBSD.org
Subject: kirkwood DMA problem
X-Send-Pr-Version: 3.95

>Number:         48572
>Category:       port-arm
>Synopsis:       kirkwood DMA problem
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-arm-maintainer
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Feb 05 09:30:00 +0000 2014
>Closed-Date:    Fri Nov 05 16:37:59 +0000 2021
>Last-Modified:  Fri Nov 05 16:37:59 +0000 2021
>Originator:     Martin Husemann
>Release:        NetBSD 6.99.30
>Organization:
The NetBSD Foundation, Inc.
>Environment:
System: NetBSD plug.duskware.de 6.99.30 NetBSD 6.99.30 (PLUG) #1: Mon Feb 3 21:00:24 CET 2014 martin@night-owl.duskware.de:/usr/src/sys/arch/evbarm/compile/PLUG evbarm
Architecture: earm
Machine: evbarm
>Description:

When stressing the eSATA disk connected to my GuruPlug I sometimes get
this:

wd0a: device timeout writing fsbn 1472999736 of 1472999736-1472999743 (wd0 bn 1472999736; cn 1461309 tn 4 sn 12), retrying
mvsata0:0:0: device disconnect
mvsata0:0:0: EDMA self disable happen 0x88
mvsata0:0:0: unable to stop EDMA
panic: EDMA enabled
cpu0: Begin traceback...
0xcb00cdfc: netbsd:db_panic+0x10
0xcb00ce2c: netbsd:vpanic+0x134
0xcb00ce44: netbsd:snprintf
0xcb00ce74: netbsd:mvsata_pmp_select+0xa8
0xcb00ce9c: netbsd:mvsata_reset_drive+0x4c
0xcb00cecc: netbsd:wddone+0x148
0xcb00cef4: netbsd:mvsata_bio_done+0xc8
0xcb00cf24: netbsd:mvsata_bio_intr+0x1dc
0xcb00cf44: netbsd:mvsata_edma_timeout+0x54
0xcb00cf74: netbsd:callout_softclock+0x188
0xcb00cfac: netbsd:softint_thread+0xac
cpu0: End traceback...

dumping to dev 16,1 offset 5980591
dump mvsata0:0:0: unable to stop EDMA
Skipping crash dump on recursive panic
panic: EDMA enabled
cpu0: Begin traceback...
0xcb00ca5c: netbsd:db_panic+0x10
0xcb00ca8c: netbsd:vpanic+0x134
0xcb00caa4: netbsd:snprintf
0xcb00cad4: netbsd:mvsata_pmp_select+0xa8
0xcb00cafc: netbsd:mvsata_reset_drive+0x4c
0xcb00cb4c: netbsd:wddump+0x1f8
0xcb00cd74: netbsd:cpu_dump+0xec
0xcb00cdc4: netbsd:dodumpsys+0xf4
0xcb00cdfc: netbsd:dumpsys+0x18
0xcb00ce2c: netbsd:vpanic+0x140
0xcb00ce44: netbsd:snprintf
0xcb00ce74: netbsd:mvsata_pmp_select+0xa8
0xcb00ce9c: netbsd:mvsata_reset_drive+0x4c
0xcb00cecc: netbsd:wddone+0x148
0xcb00cef4: netbsd:mvsata_bio_done+0xc8
0xcb00cf24: netbsd:mvsata_bio_intr+0x1dc
xcb00cf44: netbsd:mvsata_edma_timeout+0x54
0xcb00cf74: netbsd:callout_softclock+0x188
0xcb00cfac: netbsd:softint_thread+0xac
cpu0: End traceback...
rebooting...


>How-To-Repeat:
rsync quite a bit of data to a GuruPlug (maybe with a disk that is marginal?)

>Fix:
n/a

>Release-Note:

>Audit-Trail:

State-Changed-From-To: open->feedback
State-Changed-By: skrll@NetBSD.org
State-Changed-When: Sun, 20 Jun 2021 07:26:51 +0000
State-Changed-Why:
Is this still a problem?


State-Changed-From-To: feedback->closed
State-Changed-By: martin@NetBSD.org
State-Changed-When: Fri, 05 Nov 2021 16:37:59 +0000
State-Changed-Why:
Unclear if this still happens, but I am unable to reproduce it on
another GuruPlug with a different disk.


>Unformatted:

Home	PR Database Search