From owner-freebsd-security Tue Mar 9 13:59:58 1999 Delivered-To: freebsd-security@freebsd.org Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (Postfix) with ESMTP id A4FF414C09; Tue, 9 Mar 1999 13:59:38 -0800 (PST) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id OAA15811; Tue, 9 Mar 1999 14:59:12 -0700 (MST) Message-Id: <4.1.19990309145714.00c7ec80@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 09 Mar 1999 14:59:03 -0700 To: Eivind Eklund , alphen@craxx.com From: Brett Glass Subject: Re: NIC memory corrupt Cc: freebsd-security@FreeBSD.ORG In-Reply-To: <19990309162258.D63685@bitbox.follo.net> References: <000901be698e$69776f20$0a0010ac@ren.craxx.com> <000601be698c$914db740$0a0010ac@ren.craxx.com> <000901be698e$69776f20$0a0010ac@ren.craxx.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 04:22 PM 3/9/99 +0100, Eivind Eklund wrote: >I'm getting these (with 8440 replaced by 40) from a bunch of RealTek >cards that otherwise seem to work fine. Always comes on bootup (just >as the first packet is sent) on a bunch of different machines. > >Eivind. I got these on Artisoft AE-3 cards when I expanded the RAM. It seems to happen when the buffer pointer gets lost or when the buffer isn't at the address where the driver thinks it is. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message