Re: kern/51133: KASSERT on shutdown

[Martin Husemann <martin%duskware.de@localhost>]

The following reply was made to PR kern/51133; it has been noted by GNATS.

From: Martin Husemann <martin%duskware.de@localhost>
To: Ryota Ozaki <ozaki-r%netbsd.org@localhost>
Cc: "gnats-bugs%NetBSD.org@localhost" <gnats-bugs%netbsd.org@localhost>
Subject: Re: kern/51133: KASSERT on shutdown
Date: Fri, 13 May 2016 12:21:49 +0200

 On Fri, May 13, 2016 at 09:36:09AM +0900, Ryota Ozaki wrote:
 > Backtrace?
 
 Not that easy, but I changed the KASSERT to a KASSERTMSG:
 
 panic: kernel diagnostic assertion "!cpu_intr_p()" failed: file "../../../../kern/subr_xcall.c", line 353 xc__highpri_intr called from interrupt context, func=0x14fcd40 arg1=0x0 arg2=0x0
 db{0}> x/i 0x14fcd40
 netbsd:nullop:  jmpl            [%o7 + 0x8], %g0
 
 this time we seem to be processing softclock and softser:
 
 0    >  18 7   1       201          103b6b0c0             idle/1
 0       17 3   0       200          103b6b4e0             sysmon smtaskq
 0       16 3   0       200          103b6b900          cryptoret crypto_w
 0       15 3   0       200          103b58020         pmfsuspend pmfsuspend
 0       14 3   1       200          103b58440           pmfevent pmfevent
 0       13 3   1       200          103b58860         sopendfree sopendfr
 0       12 3   0       200          103b58c80           nfssilly nfssilly
 0       11 3   1       200          103b590a0            cachegc cachegc
 0       10 3   0       200          103b594c0              vrele vrele
 0        9 3   1       200          103b598e0             vdrain vdrain
 0        8 3   1       200          103b48000          modunload mod_unld
 0        7 3   0       200          103b48420            xcall/0 xcall
 0    >   6 7   0       200          103b48840          softser/0
 0    >   5 7   0       200          103b48c60          softclk/0
 0        4 1   0       200          103b49080          softbio/0
 0        3 1   0       200          103b494a0          softnet/0
 0    >   2 7   0       201          103b498c0             idle/0
 0        1 3   0       200            1c8a200            swapper uvm
 
 
 ddb doesn't like to print a backtrace, trying to get a crash dump
 I get:
 
  netbsd:vpanic+0x16c(18806d8, 1ce6ac0, 18893d0, 1b026fc58, 1ce6bc0, 1c67000) fp = 1b026f261
  netbsd:kern_assert+0x34(18893d0, 1b026fc58, 1ce5800, 1ce6ac0, 1ce6800, 4) fp = 1b026f311
  netbsd:xc__highpri_intr+0xc4(18893d0, 18053c0, 1869640, 18893b0, 161, 17f8e08) fp = 1b026f3d1
  netbsd:softint_dispatch+0xf8(1c9a000, 1c8b3a0, 50, 1c8b3a0, 276, aa670ae38cc28e39) fp = 1b026f4a1
  netbsd:softint_fastintr+0x80(0, 4, 103b48840, 0, 1b018e178, 1b018e388) fp = 1b026f571
  netbsd:softint_schedule+0x4(103b48840, 4, 1cdd800, 103b498c0, 0, 2014000) fp = 1b026f621
  netbsd:100030+0(f005eab8, 112f00, 1, f, fedc9c48, 0) fp = fedc9651
 
 
 Martin