Date: Thu, 11 Jan 2001 17:15:26 +0530 (IST) From: Mohana Krishna Penumetcha <pmk@sasi.com> To: Alfred Perlstein <bright@wintelcom.net> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: kernel debugging!!! Message-ID: <Pine.LNX.4.10.10101111709560.1340-100000@pcs113.sasi.com> In-Reply-To: <20010111031049.Y7240@fw.wintelcom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> * Mohana Krishna Penumetcha <pmk@sasi.com> [010111 03:08] wrote: > > > > > > > Afaik, on i386 you have ~4k of kernel stack, however you have to > > > realize that driver entry can come from an interrupt generated when > > > the stack is already nearly exhausted. I'm not really that much > > > of a driver programmer, but I've heard of people facing this problem > > > before, solutions varied, but since each driver instance is single > > > threaded you can pre-allocate via malloc (i think) the space you > > > need and attach it to the per-driver data structure (softc afaik). > > > > i am confused between the kernel stack in kernel space (where ISRs > > are called) and kernel stack each process has. the UPAGES constant > > defines the size of process kernel stack. does it define kernel stack in > > kernel space also?? (fig 3.1, page 51, BSD book) > > > > BTW, memory for softc is allocated from the heap in newbus > > architecture. > > I'm pretty sure interrupts are piggybacked on the user-kernel-stack. > this is o.k. when the system is up and running. but what about boot-up time when there is no process, is there any stack meant for this? > How about trying the simple printf idea and letting us know if that > works? panic is coming in the middle of the routine. i am printing many messages before the panic. -- mohan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.10.10101111709560.1340-100000>