RX packets errors when using forcedeth

High number of RX errors are seen in the output of 'ifconfig'; for instance: 

eth0      Link encap:Ethernet  HWaddr 00:21:28:3D:82:76  
          inet addr:172.16.132.129  Bcast:172.16.135.255  Mask:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9500332 errors:8391748 dropped:0 overruns:0 frame:0
          TX packets:345393 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:990047637 (944.1 Mb)  TX bytes:41187532 (39.2 Mb)
          Interrupt:106 Base address:0x6000 

For SLES 10-SP3, the patch is already available in the kernel maintenance 
update (2.6.16.60-0.62.1 or higher). 
The following is a short guide on how to deploy the  solution with the official kernel:

1. Install the latest kernel maintenance update (2.6.16.60-0.62.1 or higher). The KMP package is not needed anymore. In fact, it would be better to remove it before updating the kernel.

2. Blacklist "forcedeth":

 # echo "blacklist forcedeth">> /etc/modprobe.d/blacklist

3. Use YaST to bind their NIC's PCI-ID to forcedeth_new:

 Go to YaST -> System -> System Settings -> Add -> Manually; and fill the
 following fields:

   Driver: forcedeth_new
   Vendor: 10DE
   Device: 0373

NB: This process might certainly be automatized. 

If installing the kernel versions mentioned above does not help to fix the issue, please contact Technical Support. The PCI-ID of the network card is probably not bound in the driver.