Date: Sat, 20 Mar 2004 18:25:37 -0800 (PST) From: wpaul@FreeBSD.ORG (Bill Paul) To: julian@elischer.org (Julian Elischer) Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/compat/ndis kern_ndis.c ndis_var.h ntoskrnl_var.h subr_ndis.c subr_ntoskrnl.c src/sys/dev/if_ndi Message-ID: <20040321022537.3910216A4CF@hub.freebsd.org> In-Reply-To: <Pine.BSF.4.21.0403201659410.11551-100000@InterJet.elischer.org> from Julian Elischer at "Mar 20, 2004 05:02:15 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> >
> > options KSTACK_PAGES=8
> >
>
> Actually kernel threads can dynamically change to a different kstack
> and allocate themselves a bigger one.. I forget where it is used but I
> remember that htere is codde in exit to clean up teh extra kernel stack
> if it is being used..
>
> Is this running as a kernel thread or on a user's kernel thread stack?
>
I've been experimenting with that, but it's not helping. :( I think
the problem is occuring in the interrupt handler routine, which is
running in the "ndis swi" thread. Things seem to go fine, right up
until an interrupt fires that causes it to associate to my ad-hoc net,
then I get a double fault. In my experiments, it seems to blow up
when it hits the nanotime() call in ndis_time(). I tried to set a
breakpoint on ndis_time() and was able to stop on it once, but then
trying to do a "trace" from the kernel debugger yielded another fault.
I an only assume this means that by the time we hit this function,
the stack is already hosed.
It's possible I've misdiagnosed this problem and there's something
else afoot. All I know is that KSTACK_PAGES=8 makes it work on my
test box.
-Bill
--
=============================================================================
-Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu
wpaul@windriver.com | Wind River Systems
=============================================================================
<adamw> you're just BEGGING to face the moose
=============================================================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040321022537.3910216A4CF>