Date: Thu, 25 May 2006 12:46:08 -0600 From: Scott Long <scottl@samsco.org> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: callout_reset page fault panic Message-ID: <4475FB70.5060808@samsco.org> In-Reply-To: <200605251349.55945.jhb@freebsd.org> References: <446F1806.4050301@gmail.com> <200605241406.28235.jhb@freebsd.org> <4474C07E.5060905@gmail.com> <200605251349.55945.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin wrote: > On Wednesday 24 May 2006 16:22, Pawel Worach wrote: > >>John Baldwin wrote: >> >>>On Saturday 20 May 2006 09:22, Pawel Worach wrote: >>> >>>>One day old CURRENT, i368 UP. Died while installing some ports and >>>>running mplayer. vmcore and kernel available (minidumps kick ass!). >>>> >>>>Unread portion of the kernel message buffer: >>>>kernel trap 12 with interrupts disabled >>> >>>I think the previous 'struct callout' on the callout wheel >>>is unmapped, maybe a kernel module was unloaded and it forgot >>>to do a callout_stop() or callout_drain() or somehow did a >>>callout_reset() after doing the stop() or drain()? >>> >> >>If nothing was unloaded automagically it's unlikely. > > > It could have been free'd perhaps and the page later subsequently unmapped > from KVA? (Not sure if that can happen.) > That's how these kind of panics usually happen, actually. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4475FB70.5060808>