From owner-freebsd-current Wed Nov 5 17:25:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA25803 for current-outgoing; Wed, 5 Nov 1997 17:25:57 -0800 (PST) (envelope-from owner-freebsd-current) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA25795 for ; Wed, 5 Nov 1997 17:25:54 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id RAA04958; Wed, 5 Nov 1997 17:28:12 -0800 (PST) Message-Id: <199711060128.RAA04958@implode.root.com> To: "John W. DeBoskey" cc: freebsd-current@FreeBSD.ORG Subject: Re: fxp0 causes machine lockup In-reply-to: Your message of "Wed, 05 Nov 1997 17:09:45 EST." <199711052209.AA29928@iluvatar.unx.sas.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 05 Nov 1997 17:28:11 -0800 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > In looking through the archives I found this message which appears >to be similar, though with different hardware: > >>From: "Mike Durian" >>Date: Wed, 01 Oct 1997 12:45:27 -0600 >>Subject: strange interaction with Pentium and fxp ... That turned out to be caused by some local kernel changes that they had made - they had a SCSI card's EEPROM responding to physical addresses that were in the area of system RAM. This caused the DMA to hang; it wasn't bug in FreeBSD or the hardware and it went away when they fixed their code. I don't have any idea why your machine is hanging. Very odd and your's is the only report I've gotten of a problem like that. The first thing to do would be to figure out if it is a DMA or interrupt problem by adding printf's all over the place inside the driver, and then see where it dies. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project