Date: Wed, 19 May 2004 00:39:57 +0100 From: Colin Percival <colin.percival@wadham.ox.ac.uk> To: jhb@freebsd.org Cc: thierry@herbelot.com Subject: Re: [long] panic on a recent current Message-ID: <6.1.0.6.1.20040519003345.03f1f2c0@popserver.sfu.ca> In-Reply-To: <200405182105.04275.thierry@herbelot.com> References: <200405182105.04275.thierry@herbelot.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 20:05 18/05/2004, Thierry Herbelot wrote: >on a recent -current, running KDE and simultaneously building the world. >[snip] Short answer: Blame jhb. :-) Long answer: When he split sleepq_wakeup_thread() in revision 1.6 of subr_sleepqueue.c, he left a window open between sleepq_remove_thread and sleepq_resume_thread where td_wchan has been set to NULL but the TDI_SLEEPING bit has not yet been removed from td_inhibitors. This causes a panic when tdsigwakeup() calls sleepq_abort() on a thread which has been removed from the sleepqueue but not yet resumed. Colin Percival
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.1.0.6.1.20040519003345.03f1f2c0>