NetBSD Problem Report #54345

From gson@gson.org  Fri Jul  5 18:34:27 2019
Return-Path: <gson@gson.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-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 C07847A162
	for <gnats-bugs@gnats.NetBSD.org>; Fri,  5 Jul 2019 18:34:27 +0000 (UTC)
Message-Id: <20190705183359.4F9B3989E15@guava.gson.org>
Date: Fri,  5 Jul 2019 21:33:59 +0300 (EEST)
From: gson@gson.org (Andreas Gustafsson)
Reply-To: gson@gson.org (Andreas Gustafsson)
To: gnats-bugs@NetBSD.org
Subject: panic: kernel diagnostic assertion "xfer != NULL" in wdc.c
X-Send-Pr-Version: 3.95

>Number:         54345
>Category:       kern
>Synopsis:       panic: kernel diagnostic assertion "xfer != NULL" in wdc.c
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Jul 05 18:35:00 +0000 2019
>Closed-Date:    Sun Jul 25 09:07:53 +0000 2021
>Last-Modified:  Sun Jul 25 09:07:53 +0000 2021
>Originator:     Andreas Gustafsson
>Release:        NetBSD-current
>Organization:

>Environment:
System: NetBSD
Architecture: i386
Machine: i386
>Description:

On the TNF i386 testbed, the qemu guest running the ATF tests has
recently paniced several times with an assertion failure in wdc.c, as
seen by grepping the logs on the testbed (sorry about the long lines):

  babylon5.netbsd.org /bracket/i386/results$ find . -name test.log.gz | xargs zgrep 'xfer != NULL' | grep -v savecore
  ./2019/2019.06.21.14.58.32/test.log.gz:    too_many_args: [ 70855.0868137] panic: kernel diagnostic assertion "xfer != NULL" failed: file "/tmp/bracket/build/2019.06.21.14.58.32-i386/src/sys/dev/ic/wdc.c", line 1342 
  ./2019/2019.06.25.04.25.11/test.log.gz:    ipsec_update_sp_ah_hmacsha512: [ 30591.2890487] panic: kernel diagnostic assertion "xfer != NULL" failed: file "/tmp/bracket/build/2019.06.25.04.25.11-i386/src/sys/dev/ic/wdc.c", line 1342 
  ./2019/2019.06.25.05.04.35/test.log.gz:    ipsec_esp_camelliacbc_valid_keys: [ 23122.7142124] panic: kernel diagnostic assertion "xfer != NULL" failed: file "/tmp/bracket/build/2019.06.25.05.04.35-i386/src/sys/dev/ic/wdc.c", line 1342 
  ./2019/2019.06.25.07.14.45/test.log.gz:    dad_duplicated: [ 15478.1861096] panic: kernel diagnostic assertion "xfer != NULL" failed: file "/tmp/bracket/build/2019.06.25.07.14.45-i386/src/sys/dev/ic/wdc.c", line 1342 
  ./2019/2019.06.25.10.30.29/test.log.gz:    c_comments: [ 7511.6765260] panic: kernel diagnostic assertion "xfer != NULL" failed: file "/tmp/bracket/build/2019.06.25.10.30.29-i386/src/sys/dev/ic/wdc.c", line 1342 
  ./2019/2019.06.25.16.58.02/test.log.gz:    shrink_24M_16M_v0_4096: [ 51100.3032982] panic: kernel diagnostic assertion "xfer != NULL" failed: file "/tmp/bracket/build/2019.06.25.16.58.02-i386/src/sys/dev/ic/wdc.c", line 1342 
  ./2019/2019.07.03.23.10.43/test.log.gz:    traceme_sendsignal_ignored3: [ 9684.6583573] panic: kernel diagnostic assertion "xfer != NULL" failed: file "/tmp/bracket/build/2019.07.03.23.10.43-i386/src/sys/dev/ic/wdc.c", line 1342 
  ./2019/2019.07.04.09.02.24/test.log.gz:    ipsec_tunnel_ipv4_ah_hmacsha1: [ 36364.6862198] panic: kernel diagnostic assertion "xfer != NULL" failed: file "/tmp/bracket/build/2019.07.04.09.02.24-i386/src/sys/dev/ic/wdc.c", line 1342

The logs grepped above go back to 2011, but the message "xfer != NULL"
only appears in the logs from the last couple of weeks, so this looks
very much like a recent regression.
-- 
Andreas Gustafsson, gson@gson.org

>How-To-Repeat:

>Fix:

Unknown
>Release-Note:

>Audit-Trail:

State-Changed-From-To: open->feedback
State-Changed-By: jakllsch@NetBSD.org
State-Changed-When: Sat, 20 Jun 2020 12:51:10 +0000
State-Changed-Why:
There have been some ata/wdc commits in mid-May by jdolecek that addressed issues on qemu; is the reported issue still occuring?


From: Andreas Gustafsson <gson@gson.org>
To: gnats-bugs@netbsd.org
Cc: kern-bug-people@netbsd.org,
    netbsd-bugs@netbsd.org,
    gnats-admin@netbsd.org,
    jakllsch@NetBSD.org,
    gson@gson.org (Andreas Gustafsson)
Subject: Re: kern/54345 (panic: kernel diagnostic assertion "xfer != NULL" in wdc.c)
Date: Sat, 20 Jun 2020 18:21:27 +0300

 jakllsch@NetBSD.org wrote:
 > There have been some ata/wdc commits in mid-May by jdolecek that
 > addressed issues on qemu; is the reported issue still occuring?

 It's hard to tell because the failures have been so sporadic.  On
 the TNF i386 testbed, the failures so far were testing sources
 from the following dates:

   2019.06.21.14.58.32
   2019.06.25.04.25.11
   2019.06.25.05.04.35
   2019.06.25.07.14.45
   2019.06.25.10.30.29
   2019.06.25.16.58.02
   2019.07.03.23.10.43
   2019.07.04.09.02.24
   2019.07.09.02.50.24
   2019.07.14.11.27.33
   2019.08.01.17.50.16
   2019.09.23.18.43.59
   2020.03.15.07.56.19
   2020.03.15.12.12.42
   2020.03.23.15.32.56

 That's a period of almost six months with no failures before
 the latest set of failures in March.  Unless someone can come up
 with a reliable way of reproducing the bug, I figure we have to
 wait at least a year before we can be be reasonably sure it has
 been fixed.
 -- 
 Andreas Gustafsson, gson@gson.org

From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: kern/54345 (panic: kernel diagnostic assertion "xfer != NULL" in
 wdc.c)
Date: Sat, 24 Jul 2021 20:40:24 +0000

 On Sat, Jun 20, 2020 at 03:25:01PM +0000, Andreas Gustafsson wrote:
  >  That's a period of almost six months with no failures before
  >  the latest set of failures in March.  Unless someone can come up
  >  with a reliable way of reproducing the bug, I figure we have to
  >  wait at least a year before we can be be reasonably sure it has
  >  been fixed.

 It's been a(nother) year, how's it looking?

 -- 
 David A. Holland
 dholland@netbsd.org

State-Changed-From-To: feedback->closed
State-Changed-By: gson@NetBSD.org
State-Changed-When: Sun, 25 Jul 2021 09:07:53 +0000
State-Changed-Why:
No further failures since 2020.03.23.15.32.56, assuming fixed.


>Unformatted:

Home	PR Database Search