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: [EMAIL PROTECTED] 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 _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
