From owner-freebsd-hackers Tue Nov 7 5:20:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web3504.mail.yahoo.com (web3504.mail.yahoo.com [204.71.203.71]) by hub.freebsd.org (Postfix) with SMTP id 238A937B4D7 for ; Tue, 7 Nov 2000 05:20:13 -0800 (PST) Message-ID: <20001107132009.23436.qmail@web3504.mail.yahoo.com> Received: from [196.7.146.6] by web3504.mail.yahoo.com; Tue, 07 Nov 2000 05:20:09 PST Date: Tue, 7 Nov 2000 05:20:09 -0800 (PST) From: Jacques Fourie Subject: kernel stack size? To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Please excuse any silly questions, but I am stuck with a problem that I can't find the answer for. I wrote a KLD module that performs encryption on network packets in the kernel. Packets are intercepted for encryption on a ethernet level (in ether_input() and ether_output_frame() respectively). This module is implemented on 4.1.1-RELEASE. For input packets I added my own NETISR as well as interrupt queue. In the ether_input() routine the packets are queued and a software interrupt scheduled. Further processing on the packet then happens at a priority of splnet(). If I do bulk data transfers (encrypted) everything works fine until I run a shell script that does a 'ls -lR' in an infinite loop. A few "virtual time alarm" messages appear and then a kernel panic. Looking at the DDB output, it seems a lot like a kernel stack overflow has resulted. Very strange values for ebp and page faults on stack accesses is making me think along these lines. Does anyone know where I can find more information about the kernel stack at interrupt time (such as the maximum size)? I'm also not quite sure what the "virtual time alarm" messages mean, can anyone help me out? jacques __________________________________________________ Do You Yahoo!? Thousands of Stores. Millions of Products. All in one Place. http://shopping.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message