Topic: eepro100

[maccamob]

Hi all,
its been a while since ive had to touch my SME 5.5 it really is that good.

i have an intermitant problem and not knowing too much about linux cannot really diagnose it.
every so often my network will stop completely as if the DHCP function on the SME has been switched off, no client machines have any network coonectivity
i.e. no internet email file share etc.
so i get a phone call where ever i am, i VPN into the box and give it a remote reboot,it comes back up perfectly.

i've interegated the logs and they dont make much sense at all to me, but i do see somehing which keeps cropping up each time this happens

May  8 04:23:26 pjpdc1 e-smith[2420]: Processing event: mysql-delete-dumps
May  8 04:23:26 pjpdc1 e-smith[2420]: Running event handler: /etc/e-smith/events/mysql-delete-dumps/S10mysql-delete-dumped-tables
May  8 04:23:27 pjpdc1 e-smith[2420]: S10mysql-delete-dumped-tables=action|Event|mysql-delete-dumps|Action|S10mysql-delete-dumped-tables|Start|1052367806 969693|End|1052367807 120858|Elapsed|0.151165
May  8 05:24:25 pjpdc1 kernel: eepro100: cmd_wait for(0xffffff80) timedout with(0xffffff80)!
May  8 05:24:57 pjpdc1 last message repeated 16 times
May  8 05:25:58 pjpdc1 last message repeated 35 times
May  8 05:26:06 pjpdc1 last message repeated 9 times
May  8 05:26:10 pjpdc1 kernel: eth0: Transmit timed out: status 0090  0c80 at 46970/47033 command 000c0000.
May  8 05:26:10 pjpdc1 kernel: eepro100: cmd_wait for(0xffffff80) timedout with(0xffffff80)!
May  8 05:26:10 pjpdc1 kernel: eth0: Tx ring dump,  Tx queue 47033 / 46970:
May  8 05:26:10 pjpdc1 kernel: eth0:     0 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:     1 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:     2 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:     3 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:     4 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:     5 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:     6 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:     7 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:     8 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:     9 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    10 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    11 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    12 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    13 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    14 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    15 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    16 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    17 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    18 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    19 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    20 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    21 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    22 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    23 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    24 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    25 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    26 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    27 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    28 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    29 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    30 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    31 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    32 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    33 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    34 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    35 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    36 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    37 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    38 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    39 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    40 000c0000.
May  8 05:26:10 pjpdc1 kernel: eth0:    41 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    42 000c0000.
May  8 05:26:10 pjpdc1 kernel: eth0:    43 000c0000.
May  8 05:26:10 pjpdc1 kernel: eth0:    44 000c0000.
May  8 05:26:10 pjpdc1 kernel: eth0:    45 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    46 000c0000.
May  8 05:26:10 pjpdc1 kernel: eth0:    47 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    48 200c0000.
May  8 05:26:10 pjpdc1 kernel: eth0:    49 000c0000.
May  8 05:26:10 pjpdc1 kernel: eth0:    50 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    51 000c0000.
May  8 05:26:10 pjpdc1 kernel: eth0:    52 000c0000.
May  8 05:26:10 pjpdc1 kernel: eth0:    53 000c0000.
May  8 05:26:10 pjpdc1 kernel: eth0:    54 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    55 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    56 40030000.
May  8 05:26:10 pjpdc1 kernel: eth0:   =57 0003a000.
May  8 05:26:10 pjpdc1 kernel: eth0:  * 58 000c0000.
May  8 05:26:10 pjpdc1 kernel: eth0:    59 000c0000.
May  8 05:26:10 pjpdc1 kernel: eth0:    60 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    61 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    62 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0:    63 00030000.
May  8 05:26:10 pjpdc1 kernel: eth0: Printing Rx ring (next to receive into 44093, dirty index 44093).

sorry about all that, i've got my suspiscions its the network card intel pro 100

if so can i just swap this out for either intel pro 100 or a totally different model? do i need to worry about drivers etc? will they need loading after reboot? or will the system need a rebuild?

many thanks in advance for any advice you fellas can give me

cheers
Maccamob

[Bill Talcott]

If you swap cards, just rerun the configuration (login as admin).

[Grub]

Can you give more hardware information... mainboard etc. ???

[maccamob]

yes sorry forgot about that
its a dell poweredge 4400
dual xeon 633's
512mb ram
2x18g scsi drive's (software raid)
not to sure on the mainboard's exact model sorry

silly me i forgot all about the reconfiguration option

cheers

may have a go this weekend

cheers

[A.J.]

There seems to be some sort of sleep command that kicks in under load with this family of NIC cards, I had the same problem. There is a diagnostic program that fixes it. The source for this program is: ftp://ftp.scyld.com/pub/diag/eepro100-diag.c . You need to compile it using the commands found in the text at the bottom of the file.
   Put the program that results from compiling, eepro100-diag, in your home directory and make it executable ( chmod 755 eepro100-diag ). If you read inside the source file, it will give you a list of flags to run such as
( ./eepro100-diag  -aem ). It’s been a while since I’ve done it, but I believe if it encounters a sleep mode setting, it will advise you which command to run.
   If you don't have access to a linux system that can compile, I can email the compiled program to you.

   Let me know how it goes. By the way, if you google “eepro100-diag” you will see it’s a common problem.

A.J.
Las Vegas, NV