Date: Fri, 15 Apr 2005 19:56:50 -0700 (PDT) From: Doug White <dwhite@gumbysoft.com> To: Daniel Eriksson <daniel_k_eriksson@telia.com> Cc: 'FreeBSD Current' <freebsd-current@freebsd.org> Subject: RE: task queue: supervisor write, page not present Message-ID: <20050415195545.W38788@carver.gumbysoft.com> In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA0VcX9IoJqUaXPS8MjT1PdsKAAAAQAAAAAbdICmJNzkmCrRtqFiPMfwEAAAAA@telia.com> References: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA0VcX9IoJqUaXPS8MjT1PdsKAAAAQAAAAAbdICmJNzkmCrRtqFiPMfwEAAAAA@telia.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 15 Apr 2005, Daniel Eriksson wrote: > Doug White wrote: > > > Can you get a crashdump and inspect the taskq with gdb? I'm assuming > > there's a bogus entry thats getting tripped over. > > Dang, I was running low on space and removed the dump I had just a few hours > ago since nobody had replied yet. Sorry, we don't guarantee 4 hour response -- that costs money. :) > Right now I'm back to running CURRENT as of 2005.03.11.12.00.00 (over a > month old) because I know it works pretty well for me. > > I'm not very good with gdb. Are there any specific steps I should take to > get the information needed to track this down (if I upgrade to latest > CURRENT again)? Could this be related to me using a lot of r/w nullfs > mounts? I don't think so... nullfs has it sown problems, but not random memory corruption. Next time, could you make the crashdump and debug kernel available for download? -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050415195545.W38788>