NetBSD Problem Report #56646

From he@smistad.uninett.no  Thu Jan 20 08:48:23 2022
Return-Path: <he@smistad.uninett.no>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 5DADC1A9239
	for <gnats-bugs@gnats.NetBSD.org>; Thu, 20 Jan 2022 08:48:23 +0000 (UTC)
Message-Id: <20220120084818.4138743FFD9@smistad.uninett.no>
Date: Thu, 20 Jan 2022 09:48:18 +0100 (CET)
From: he@NetBSD.org
Reply-To: he@NetBSD.org
To: gnats-bugs@NetBSD.org
Subject: mvsata: wd0 read error -> panic w/diag assertion(?)
X-Send-Pr-Version: 3.95

>Number:         56646
>Category:       port-evbarm
>Synopsis:       mvsata: wd0 read error -> panic w/diag assertion(?)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-evbarm-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jan 20 08:50:00 +0000 2022
>Last-Modified:  Thu Jan 20 09:15:01 +0000 2022
>Originator:     Havard Eidnes
>Release:        NetBSD 9.2
>Organization:
	I try...
>Environment:
System: NetBSD kb.urc.uninett.no 9.2 NetBSD 9.2 (KUROBOX_PRO) #0: Wed May 12 13:15:55 UTC 2021  mkrepro@mkrepro.NetBSD.org:/usr/src/sys/arch/evbarm/compile/KUROBOX_PRO evbarm
Architecture: earm
Machine: evbarm
>Description:

	Overnight, this box saw the following errors / crash on a
	KUROBOX_PRO.
	I suspect they are related(?)

mvsata0:0:0: device error, recovering
[ 86371.9795547] wd0d: error reading fsbn 565381856 of 565381856-565381887 (wd0 bn 567865568; cn 563358 tn 11 sn 11), xfer f00, retry 0
[ 86371.9795547] wd0: (uncorrectable data error)
mvsata0:0:0: device error, recovering
[ 86375.0796640] wd0d: error reading fsbn 565381856 of 565381856-565381887 (wd0 bn 567865568; cn 563358 tn 11 sn 11), xfer f00, retry 1
[ 86375.0796640] wd0: (uncorrectable data error)
mvsata0:0:0: device error, recovering
[ 86377.4697474] wd0d: error reading fsbn 565381856 of 565381856-565381887 (wd0 bn 567865568; cn 563358 tn 11 sn 11), xfer f00, retry 2
[ 86377.4697474] wd0: (uncorrectable data error)
mvsata0:0:0: device error, recovering
[ 86379.8598317] wd0d: error reading fsbn 565381856 of 565381856-565381887 (wd0 bn 567865568; cn 563358 tn 11 sn 11), xfer f00, retry 3
[ 86379.8598317] wd0: (uncorrectable data error)
[ 86380.3898562] panic: kernel diagnostic assertion "((xfer->c_flags & C_DMA) != 0) == (mvport->port_edmamode_curr != nodma)" failed: file "/usr/src/sys/dev/ic/mvsata.c", line 1250 DMA mode mismatch: flags 0 vs edmamode 3 != 0
[ 86380.3898562] cpu0: Begin traceback...
[ 86380.3898562] 0xc8aace9c: netbsd:db_panic+0x10
[ 86380.3898562] 0xc8aaceb4: netbsd:vpanic+0x140
[ 86380.3898562] 0xc8aacecc: netbsd:kern_assert+0x40
[ 86380.3898562] 0xc8aacf4c: netbsd:mvsata_bio_start+0x7b0
[ 86380.3898562] 0xc8aacf74: netbsd:ata_xfer_start+0x40
[ 86380.3898562] 0xc8aacfac: netbsd:atabus_thread+0x2b0
[ 86380.3898562] cpu0: End traceback...

[ 86380.3898562] dumping to dev 16,1 offset 787183
[ 86380.3898562] dump Mutex error: mutex_vector_enter,484: locking against myself

[ 86380.3898562] lock address : 0x00000000c2417018
[ 86380.3898562] current cpu  :                  0
[ 86380.3898562] current lwp  : 0x00000000c23ee600
[ 86380.3898562] owner field  : 0x0000000000010500 wait/spin:                0/1

[ 86380.3898562] Skipping crash dump on recursive panic
[ 86380.3898562] panic: lock error: Mutex: mutex_vector_enter,484: locking against myself: lock 0xc2417018 cpu 0 lwp 0xc23ee600
[ 86380.3898562] cpu0: Begin traceback...
[ 86380.3898562] 0xc8aaca9c: netbsd:db_panic+0x10
[ 86380.3898562] 0xc8aacab4: netbsd:vpanic+0x140
[ 86380.3898562] 0xc8aacacc: netbsd:snprintf
[ 86380.3898562] 0xc8aacb14: netbsd:lockdebug_abort+0xb4
[ 86380.3898562] 0xc8aacb2c: netbsd:mutex_abort+0x2c
[ 86380.3898562] 0xc8aacb5c: netbsd:wd_dumpblocks+0x170
[ 86380.3898562] 0xc8aacbbc: netbsd:dk_dump_flags+0x254
[ 86380.3898562] 0xc8aacbfc: netbsd:wddump+0x94
[ 86380.3898562] 0xc8aace24: netbsd:cpu_dump+0xe0
[ 86380.3898562] 0xc8aace6c: netbsd:dodumpsys+0xe8
[ 86380.3898562] 0xc8aace9c: netbsd:dumpsys+0x1c
[ 86380.3898562] 0xc8aaceb4: netbsd:vpanic+0x14c
[ 86380.3898562] 0xc8aacecc: netbsd:kern_assert+0x40
[ 86380.3898562] 0xc8aacf4c: netbsd:mvsata_bio_start+0x7b0
[ 86380.3898562] 0xc8aacf74: netbsd:ata_xfer_start+0x40
[ 86380.3898562] 0xc8aacfac: netbsd:atabus_thread+0x2b0
[ 86380.3898562] cpu0: End traceback...
[ 86380.3898562] rebooting...

>How-To-Repeat:
	Not entirely sure, see above.

>Fix:
	Sorry, have not looked closer.

>Audit-Trail:
From: Rin Okuyama <rokuyama.rk@gmail.com>
To: gnats-bugs@netbsd.org, Havard Eidnes <he@netbsd.org>
Cc: 
Subject: Re: port-evbarm/56646: mvsata: wd0 read error -> panic w/diag
 assertion(?)
Date: Thu, 20 Jan 2022 18:13:32 +0900

 Hi,

 mvsata(4) has been terribly broken; see

 - kern/53997
 - kern/52419
 - kern/52126

 for more details.

 For mvsoc(4)-based machines,

 - NFS root with internal NIC
 - nvme(4) or ahcisata(4) for PCIe slot

 work just fine for me.

 Thanks,
 rin

Home	PR Database Search