From owner-freebsd-current@FreeBSD.ORG  Thu Aug 28 05:04:40 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 CDE1D16A4BF
	for <freebsd-current@FreeBSD.ORG>;
	Thu, 28 Aug 2003 05:04:40 -0700 (PDT)
Received: from mail.gmx.net (pop.gmx.de [213.165.64.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id 4949043FDD
	for <freebsd-current@FreeBSD.ORG>;
	Thu, 28 Aug 2003 05:04:39 -0700 (PDT)	(envelope-from pilkis@gmx.net)
Received: (qmail 1840 invoked by uid 65534); 28 Aug 2003 12:04:37 -0000
Received: from unknown (EHLO pilkisnotexp) (62.68.42.70)
  by mail.gmx.net (mp001) with SMTP; 28 Aug 2003 14:04:37 +0200
Message-ID: <142b01c36d5c$8d235e30$0464a8c0@spotripoli.local>
From: "Putinas" <pilkis@gmx.net>
To: "Soren Schmidt" <sos@spider.deepcore.dk>
References: <200308281143.h7SBhWj3023899@spider.deepcore.dk>
Date: Thu, 28 Aug 2003 14:04:35 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.3790.0
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Sil3112 dma errors
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Aug 2003 12:04:40 -0000

1. It's written only Advance Peripherals , looks like this
http://www7.alternate.de/prodpic/200x200/f/fpba03.jpg
2. Nope , network is connected only to 100 mbit switch, and most often the
problem occurs when there is higher i/o with disk ( like kernel compiling or
make buildworld ) which I usually do over ssh remotely, but same thing
happened via console and even when booting on the starting up services.

----- Original Message ----- 
From: Soren Schmidt
To: Putinas
Cc: freebsd-current@FreeBSD.ORG
Sent: Thursday, August 28, 2003 13:43 PM
Subject: Re: Sil3112 dma errors


It seems Putinas wrote:
> Hi all,
> recently I upgraded my kernel to the last version  ( Aug 28 now, before
was
> runing Aug 5 version ), and I startet to get error like this:
> Aug 27 17:03:23 pilkishome kernel: ad4: WARNING - WRITE_DMA recovered from
> missing interrupt
> Aug 27 17:03:23 pilkishome kernel: ad4: WARNING - WRITE_DMA soft error
(ECC
> corrected)ad4: FAILURE - WRITE_DMA
> status=ff<BUSY,READY,DMA_READY,DSC,DRQ,CORRECTABLE,INDEX,ERROR> error=0...
> <here ends syslogd>
> ad4: WARNING - WRITE_DMA recovery from missing interupt
> ad4: timeout sending command=ca
> ad4: error issuing DMA command
>
> after where is coming dma timeout, but in the syslog already nothing,
system
> becomes unresponsible

Hmm two things:
what kind of SATA->PATA dongles are you using ?
Do you have any significant traffic on the gigE interface ?

-Søren
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"