From owner-freebsd-hackers  Mon Jan 27 20:58:03 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA17727
          for hackers-outgoing; Mon, 27 Jan 1997 20:58:03 -0800 (PST)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA17721
          for <hackers@freebsd.org>; Mon, 27 Jan 1997 20:58:01 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id UAA13857; Mon, 27 Jan 1997 20:57:43 -0800 (PST)
Message-Id: <199701280457.UAA13857@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: Lars Jonas Olsson <ljo@Mcs.Net>
cc: hackers@freebsd.org
Subject: Re: de0 timeouts w 486 CPU 
In-reply-to: Your message of "Mon, 27 Jan 1997 15:34:19 CST."
             <199701272134.PAA10766@Venus.mcs.net> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Mon, 27 Jan 1997 20:57:43 -0800
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>I have a 486DX4-100 system that is doing make worlds fine, but
>generates a lot of:
>
>de0: system error: master abort
>
>messages with a current kernel. With a 2.1R kernel it was
>generating illegal interrupt errors for de0. 
> Any guess if this is bug in the if_de.c driver or a hardware problem?
>The rate of messages is 5-30/hour on a system not doing much
>networking.

   I would guess that it's a PCI DMA problem on the motherboard. There were
quite a few 486 PCI machines that had really bad PCI performance (perhaps
due to incorrect chipset configuration?). You may wish to look for any BIOS
settings related to PCI write buffer, etc..

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project