NetBSD Problem Report #56375

From martin@aprisoft.de  Wed Aug 25 11:50:12 2021
Return-Path: <martin@aprisoft.de>
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 CF1B21A9239
	for <gnats-bugs@gnats.NetBSD.org>; Wed, 25 Aug 2021 11:50:12 +0000 (UTC)
Message-Id: <20210825114941.12DDB5CC84B@emmas.aprisoft.de>
Date: Wed, 25 Aug 2021 13:49:41 +0200 (CEST)
From: martin@NetBSD.org
Reply-To: martin@NetBSD.org
To: gnats-bugs@NetBSD.org
Subject: kernel crashes from wdc dma
X-Send-Pr-Version: 3.95

>Number:         56375
>Category:       port-macppc
>Synopsis:       kernel crashes from wdc dma
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    port-macppc-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Aug 25 11:55:00 +0000 2021
>Last-Modified:  Thu Aug 26 16:30:01 +0000 2021
>Originator:     Martin Husemann
>Release:        NetBSD 9.99.88
>Organization:
The NetBSD Foundation, Inc.
>Environment:
System: NetBSD gethsemane.aprisoft.de 9.99.88 NetBSD 9.99.88 (GETHSEMANE) #126: Wed Aug 25 10:24:48 CEST 2021 martin@seven-days-to-the-wolves.aprisoft.de:/work/src/sys/arch/macppc/compile/GETHSEMANE macppc
Architecture: powerpc
Machine: macppc
>Description:

During hard disk usage (but nothing special) I repeatadly got:

[ 3910.7564579] panic: pmap_pvo_find_va: returning NULL for kernel pmap, va: 0x4e65000
[ 3910.7564579] cpu0: Begin traceback...
[ 3910.7564579] 0x10003aa0: at vpanic+0x12c
[ 3910.7564579] 0x10003ad0: at panic+0x50
[ 3910.7564579] 0x10003b10: at pmap_pvo_find_va+0x134
[ 3910.7564579] 0x10003b20: at pmap_extract+0xc8
[ 3910.7564579] 0x10003b40: at wdc_obio_dma_init+0x374
[ 3910.7564579] 0x10003bb0: at wdc_ata_bio_start+0x2bc
[ 3910.7564579] 0x10003c10: at ata_xfer_start+0x4c
[ 3910.7564579] 0x10003c30: at atastart+0x298
[ 3910.7564579] 0x10003c70: at wdstart1+0x1d0
[ 3910.7564579] 0x10003c90: at wd_diskstart+0xa0
[ 3910.7564579] 0x10003cb0: at dk_start+0x128
[ 3910.7564579] 0x10003cf0: at wdc_ata_bio_done+0x88
[ 3910.7564579] 0x10003d10: at wdc_ata_bio_intr+0x204
[ 3910.7564579] 0x10003d40: at wdcintr+0xdc



>How-To-Repeat:
n/a

>Fix:
n/a

>Audit-Trail:
From: Michael <macallan@netbsd.org>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: port-macppc/56375: kernel crashes from wdc dma
Date: Wed, 25 Aug 2021 12:07:20 -0400

 Is that the Quicksilver or some older wdc at obio variant?
 I tortured mine quite a bit without any disk DMA related problems but
 that was a few weeks ago. 
 My first guess would be something fishy with the dbdma code...

 have fun
 Michael

From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: port-macppc/56375: kernel crashes from wdc dma
Date: Wed, 25 Aug 2021 19:19:12 +0200

 On Wed, Aug 25, 2021 at 04:10:02PM +0000, Michael wrote:
 >  Is that the Quicksilver or some older wdc at obio variant?

 Yes, quicksilver.

 Martin

From: Michael <macallan@netbsd.org>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: port-macppc/56375: kernel crashes from wdc dma
Date: Thu, 26 Aug 2021 12:09:19 -0400

 I must have seen this before since there's debug code in my wdc_obio.c
 that looks like it's trying to catch this.
 Do you have a more or less reliable way to trigger the panic?

 have fun
 Michael

From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: port-macppc/56375: kernel crashes from wdc dma
Date: Thu, 26 Aug 2021 18:27:11 +0200

 On Thu, Aug 26, 2021 at 04:15:02PM +0000, Michael wrote:
 >  Do you have a more or less reliable way to trigger the panic?

 Unfortunately not. It happened for me twice yesterday while unpacking
 all sets during an update.

 Martin

Home	PR Database Search