Re: port-alpha/38335 (kernel freeze on alpha MP system)

[Jarle Greipsland <jarle%uninett.no@localhost>]

The following reply was made to PR port-alpha/38335; it has been noted by GNATS.

From: Jarle Greipsland <jarle%uninett.no@localhost>
To: mhitch%lightning.msu.montana.edu@localhost
Cc: gnats-bugs%NetBSD.org@localhost, gnats-admin%netbsd.org@localhost
Subject: Re: port-alpha/38335 (kernel freeze on alpha MP system)
Date: Thu, 08 Oct 2009 16:16:03 +0200 (CEST)

 Jarle Greipsland <jarle%uninett.no@localhost> writes:
 > Jarle Greipsland <jarle%uninett.no@localhost> writes:
 > > Ah.  That's what happens when one manually applies a patch :-(
 > > Oh well.  I have since updated my kernel, and am now running a
 > > -current GENERIC.MP kernel with the IPL_VM -> IPL_SCHED
 > > modification.  I have started a "build -j4" job, and I'll
 > > see how that works out.
 > Another data point: It crashed again; still with the same panic
 > from your patch, which I forgot to comment out when I updated my
 > sources.  So, even with the IPL_VM->IPL_SCHED change in, it still
 > reaches the "Whoa!  pool_cache_get returned an in-use entry!"
 > printf statement.  I have no idea whether that's significant or
 > not.
 > 
 > I'll comment out the "Oops"-panic now, and see what happens
 > then.
 The system then keeps on running.  Though for every "build -j4"
 job I run I get approximately one
   "Whoa!  pool_cache_get returned an in-use entry!"
 message on the console.  I guess this means we have a
 papered-over bug now?
                                        -jarle
 -- 
 Q: What's the difference between programming and bug collecting?
 A: None.