Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 12 Sep 2003 13:46:02 -0400
From:      Mike Tancsa <mike@sentex.net>
To:        Info Account <info@PerryResearch.com>, freebsd-stable@freebsd.org
Subject:   Re: recent stability problems with fxp driver
Message-ID:  <6.0.0.22.0.20030912134112.05891060@209.112.4.2>
In-Reply-To: <1063383965.3f61f39d6a97d@www.tacosalad.org>
References:  <1063383965.3f61f39d6a97d@www.tacosalad.org>

next in thread | previous in thread | raw e-mail | index | archive | help
At 12:26 PM 12/09/2003, Info Account wrote:
>I've spent the past four days or so updating machines here to 4.8/9-stable via
>cvsup, and have done a complete make buildworld/kernel on each machine (some
>SMP, some single processor).  It seems something is broken with the latest fxp
>driver, on each machine (different mobos and hardware configs) heavy network
>traffic with fxp NICs causes timeouts and random kernel panics.

I have a few boxes pushing over 50Mb with fxp cards and havent seen this 
problem.  What type of fxp cards do you have ?  What does
  pciconf -v -l
show for the Intel types ?

Also, I have found in the past that I would see this behavior if I changed 
NICs and didnt do a PCIconfig reset in the MB BIOS.  There is something 
about Intel nics and Adaptec and 3ware cards that particularly require 
this.  Also, make sure that you dont have some duplex mismatches on the 
nics.  I have seen where excessive errors combined with high traffic will 
cause panics.

Also, please post the actual error messages on each of the machines.

         ---Mike




>First machine to experience the problem was a single proc PIII-650 with 
>512M and
>Adaptec 2940UW, one fxp, doing a backup via scp, after 10 megs or so starting
>giving fxp0 timeout errors and dropping the connection (host was not pingable
>and dropped all arp entries).  The only way to restart the scp was to ifconfig
>fxp0 back up with the same IP and netmask.
>
>Second machine is a dual proc PIII-650 with 512M, MegaRAID, one fxp - after a
>minute or so of scp'ing the machine completely locked, had to be hard reset.
>Second attempt caused a panic that seized entire machine with instant reboot.
>
>Few more machines, same problems, all with varying SCSI subsystems and 
>with one
>fxp NIC.  After replacing each machine's fxp with crappy tulip and/or $12 
>kmart
>linksys NIC, I've had no problems at all.
>
>---------------------------------
>
>Perry Research, Inc.
>5450 Bruce B. Downs Blvd #313
>Wesley Chapel, FL 33543
>p: 813-864-7659 f: 813-862-2015
>
>http://www.PerryResearch.com
>
>
>
>_______________________________________________
>freebsd-stable@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.0.0.22.0.20030912134112.05891060>