From owner-freebsd-current Thu Oct 7 12:11:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 2BCFC14C1A for ; Thu, 7 Oct 1999 12:11:13 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA00921; Thu, 7 Oct 1999 12:01:42 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910071901.MAA00921@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: mjacob@feral.com Cc: freebsd-current@freebsd.org Subject: Re: i386 wierd one...... kernel stack frame pointer corruption(?) In-reply-to: Your message of "Thu, 07 Oct 1999 11:27:56 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Oct 1999 12:01:42 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > One thing that is possible is that it's a very deep callstack... It's > during probing and it may have called completion on a completing command > while down at the bottom of the stack starting another command. If you run > out of kernel stack, don't you get some other kind of fault? That kinda depends on how hard you hit the bottom of the stack. I'd typically expect a double fault though. Note that SMP systems are much better behaved in this case than the old UP kernel stack setup. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message