Re: -current: panic at setrunqueue

[Mike <owensmk@earthlink.net>]

Yep. 'make clean.' Why didn't I just do that from the start? Thanks for
tolerating me.

Artur Grabowski wrote:
> 
> Brian Somers <brian@Awfulhak.org> writes:
> 
> > > I haven't seen any messages regarding this, so perhaps it's just me:
> > > when I built a generic kernel from today's -current, it panics at
> > > setrunqueue and drops into ddb. Granted I have only rebuilt the system
> > > three or four times in my life ---over the last month or so---I don't
> > > think I have changed anything significantly, if at all, on my system to
> > > produce this. I updated once more a couple of hours later and the same
> > > result ensued. Just thought I would mention it.
> >
> > If it's any consolation, I'm suffering from this too.  To boot, cvs
> > has stopped working....  The answer is almost definitely to re-sup
> > and rebuild after booting with your old kernel, but I haven't been in
> > the house (where the box is) for long in the past few days, so I
> > haven't been able to fix things yet :-(
> 
> I think this is because of the bug in kernel/1154. Do a "make clean" before
> building a kernel and this should go away.
> 
> //art