From owner-freebsd-current@FreeBSD.ORG Thu Jul 1 15:47:08 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C0DC16A4CE; Thu, 1 Jul 2004 15:47:08 +0000 (GMT) Received: from kilowog.blockstackers.com (ip199-194.digitalrealm.net [216.144.199.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6D0B43D39; Thu, 1 Jul 2004 15:47:07 +0000 (GMT) (envelope-from pater@kilowog.blockstackers.com) Received: from pater by kilowog.blockstackers.com with local (Exim 3.35 #1 (Debian)) id 1Bg3lW-0000qf-00; Thu, 01 Jul 2004 11:46:22 -0400 Date: Thu, 1 Jul 2004 11:46:21 -0400 From: Jonathan Pater To: Bill Paul Message-ID: <20040701154621.GA2683@slashdot.org> References: <20040630162723.GA17170@slashdot.org> <20040630232436.BE68216A4CF@hub.freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bp/iNruPH9dso1Pn" Content-Disposition: inline In-Reply-To: <20040630232436.BE68216A4CF@hub.freebsd.org> User-Agent: Mutt/1.3.28i Sender: Jonathan Pater cc: freebsd-current@freebsd.org Subject: Re: issues with em, ndis & 1 gig RAM in -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2004 15:47:08 -0000 --bp/iNruPH9dso1Pn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 30, 2004 at 11:24:36PM +0000, Bill Paul wrote: > Unfortunately, I can't really help you with this problem: Intel wrote > the em(4) driver, and I'm not terribly familiar with it. Did you > try locking the speed down instead of leaving it with autoneg on? > (That would be ifconfig em0 media 100baseTX. NOTE: I left the > "mediaopt full-duplex" part off on purpose. Just trust me on this. > Leave the switch set for autoneg and do "ifconfig em0 media 100baseTX" > and see what happens.) That didn't help me, but a new hard drive and a different OS confirm that this isn't a software problem, but a hardware one. Sometime in the week between when I first installed the machine and noticing the problem, my network card went south. Sorry for wasting your time with this. > Unfortunately, there's only one way you can help (as far as ndis is > concerned), and that's to fix it so I can debug the machine remotely. I > don't have access to any hardware even remotely like this (except > possibly for the LinkSys wireless card), so it's impossible for me to > test or debug this myself. >=20 > There are two things that could be going wrong here: >=20 > 1) NDIS is doing something wrong with busdma and is not DMA mapping > buffers in the other gigabyte of memory correctly > 2) NDIS is doing something wrong with resource allocation and isn't > mapping the PCI memory mapped register window correctly >=20 > It's hard to tell. You provided a dmesg with the machine configured > with 1GB of RAM (the working case) but not with 2GB of RAM (the > failure case), so I can't make a comparison. Regardless, without > access to the box, I'm sort of stuck. I'm working on getting the machine up with a new network card (the old one was onboard) and it might require me replacing the motherboard, but once I do, I can set you up with an account to poke around at things. thanks much, --=20 Jonathan "CowboyNeal" Pater | pater@slashdot.org http://cowboyneal.org/ | http://slashdot.org/ "I'm sure we can do this ourselves, Donny. This isn't our first barbeque." -- Space Ghost, to Donny Osmond --bp/iNruPH9dso1Pn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFA5DHN9K43x2NK81ERAsnSAJoDTXUumplCdRU2tK+O5eUvuynktACfSrCU GwapY7IsZoISdfoYHOxqLjw= =wosk -----END PGP SIGNATURE----- --bp/iNruPH9dso1Pn--