From garrett.barry at sycamorenet.com Wed Nov 1 08:03:06 2006 From: garrett.barry at sycamorenet.com (Barry, Garrett) Date: Tue Nov 9 01:14:29 2010 Subject: [scyld-users] intel etherpro 100 problems Message-ID: <0679BA70A2F59E49B186858B47F4595CE483EA@viper.sycamorenet.com> Hi, I am seeing MAC address corruption problems in the eeprom of the 82559. We see the MAC address corruption after we modify the sleep bit of the eeprom configuration. Anyone ever see issues simular to this ?? we are using the eepro100-diag.c stuff to modify the eeprom. Only a single byte of the MAC address stored in the eeprom is corrupted. We see this after a system has been up and running for a very long time. All of a sudden can't communicate to the port and see a bads mac address in the eeprom. From becker at scyld.com Wed Nov 1 13:28:10 2006 From: becker at scyld.com (Donald Becker) Date: Tue Nov 9 01:14:29 2010 Subject: [scyld-users] intel etherpro 100 problems In-Reply-To: <0679BA70A2F59E49B186858B47F4595CE483EA@viper.sycamorenet.com> Message-ID: On Wed, 1 Nov 2006, Barry, Garrett wrote: > I am seeing MAC address corruption problems in the eeprom of the 82559. > We see the MAC address corruption after we modify the sleep bit of the > eeprom configuration. Anyone ever see issues simular to this ?? Which way do you modify the sleep bit -- are you clearing it? (It's probably not related to this issue, just checking.) > we are using the eepro100-diag.c stuff to modify the eeprom. Only a > single byte of the MAC address stored in the eeprom is corrupted. We > see this after a system has been up and running for a very long time. > All of a sudden can't communicate to the port and see a bads mac > address in the eeprom. Hmm, that is curious. That suggests that some other part of the system is writing into the NIC. The EEPROM is used only when the driver is loaded. The driver reads and remembers the important fields. If the EEPROM word was just randomly being overwritten by electrical noise or internal firmware, you wouldn't notice a problem until the next time the driver was started. Reading and writing the 82559 EEPROM is non-trivial. The diagnostic program does it the documented way -- generating a bit-serial data stream by writing the EEPROM control register. To generate the command to write an EEPROM word requires over 50 register writes, so it's not a single errant write causing the problem. Which word of the EEPROM is being overwritten? What is the changed value? (The MAC address is stored in the first three words of the EEPROM. Each word is 16 bits, so typically a pair of bytes would be changed at once.) -- Donald Becker becker@scyld.com Scyld Software Scyld Beowulf cluster systems 914 Bay Ridge Road, Suite 220 www.scyld.com Annapolis MD 21403 410-990-9993 From orsobrux at infinito.it Sun Nov 5 14:43:48 2006 From: orsobrux at infinito.it (orsobrux@infinito.it) Date: Tue Nov 9 01:14:29 2010 Subject: [scyld-users] source code for ethernet card RTL8139 Message-ID: <20061105234343.C3C1.ORSOBRUX@infinito.it> 05/11/2006 I need, if possible, your help, because in the hardware I found only that: "If your kernel doesn't support RTL8139 series, you should compiler driver by yourself. Please contact http://www.scyld.com/network/rtl8139.html to get source code. The compiler command is located on the end of source code." Someone can tell me where I can get the source code? Thank you Orsini From orsobrux at tiscali.it Sun Nov 5 14:44:48 2006 From: orsobrux at tiscali.it (Orsi) Date: Tue Nov 9 01:14:29 2010 Subject: [scyld-users] source code for ethernet card RTL8139 Message-ID: I need, if possible, your help, because in the hardware I found only that: "If your kernel doesn't support RTL8139 series, you should compiler driver by yourself. Please contact http://www.scyld.com/network/rtl8139.html to get source code. The compiler command is located on the end of source code." Someone can tell me where I can get the source code? Thank you Orsini