From owner-freebsd-hackers Tue Feb 17 04:10:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA11192 for freebsd-hackers-outgoing; Tue, 17 Feb 1998 04:10:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA11069 for ; Tue, 17 Feb 1998 04:09:59 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id MAA05862; Tue, 17 Feb 1998 12:09:57 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id NAA14134; Tue, 17 Feb 1998 13:09:57 +0100 (MET) Message-ID: <19980217130957.45413@follo.net> Date: Tue, 17 Feb 1998 13:09:57 +0100 From: Eivind Eklund To: Mike Smith Cc: hackers@FreeBSD.ORG Subject: Re: ed overwrite clue? References: <19980217122904.27594@follo.net> <199802171140.DAA01667@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199802171140.DAA01667@dingo.cdrom.com>; from Mike Smith on Tue, Feb 17, 1998 at 03:40:24AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 17, 1998 at 03:40:24AM -0800, Mike Smith wrote: > > I'm not certain about anything right now - I started reproducing this > > about an hour ago. It might even be a hardware failure (but I've > > tried with different cards of the same type, and all fail, while a > > Kingston Ne2000-clone works flawlessly). > > That in particular is kinda odd. What NIC is the Kingston card using? > Is it a "real" 8390x, or another clone? It's another clone. It is marked with Kingston EtheRx LC KTC 8890-AXCM > I have the RTL8019 documentation around here somewhere; it's in an odd > format that I didn't get to print (a self-extracting nonstandard-format > Windows executable I think). If you're really stuffed let me know and > I'll dig it out. Thanks for the offer! (I don't need it yet, but might need it if everything goes west). > One question; the destination of the insw - is that actually a > legitimate address? ie. is it on the kernel stack, or somewhere > else? It looks like the destination is on the kernel stack. The source looks more suspicious - it is at 0x6200... Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message