From owner-freebsd-hackers Tue Feb 17 16:20:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28574 for freebsd-hackers-outgoing; Tue, 17 Feb 1998 16:20:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28469 for ; Tue, 17 Feb 1998 16:19:45 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id QAA03678; Tue, 17 Feb 1998 16:17:47 -0800 (PST) Message-Id: <199802180017.QAA03678@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Eivind Eklund cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: ed overwrite clue? In-reply-to: Your message of "Wed, 18 Feb 1998 00:28:52 +0100." <19980218002852.55010@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 17 Feb 1998 16:17:47 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > I think what you're seeing there is you're taking interrupts on two > > different stacks. The 0xefb* addresses are around _kstack, which is at > > 0xefbfe000. The other one could be the user stack. > > _kstack is the bottom end of the stack; the top end looks like it is > at 0xefc0000. All of the crashing addresses I've seen so far are in > the top 256 bytes of the kstack, so it doesn't look like I'm running > out of stack. Ok. Pity though, it would have been a convenient answer. 8) > > > I'm about to start trigging some crashdumps on purpose now, so I can > > > get a good look at how a dump for an OK case is. > > > > Do you have any custom code in the kernel? > > Yes. And the system won't boot without it, so ripping it out is > really not an option. I could try to revert as much as possible, but > it really doesn't look like any of the code that is revertible is at > fault; almost none of it has been excersised yet. The only reason I asked was inre: stack overflow. > And the exact same kernel run fine with another NE2000-clone (on > another port and IRQ, though, but there are no IRQ-conflicts). 8( Try matching the two, just in case this is a real heisenbug... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message