| 1 |
David Sommerseth wrote: |
| 2 |
> atoth@××××××××××.hu wrote: |
| 3 |
>> PCI-X dual port Broadcom NetXtreme BCM5704 Gigabit Ethernet (rev 03) |
| 4 |
>> adapter is working fine here driven by tg3, 2.6.27-hardened-r1. The driver |
| 5 |
>> doesn't seem to be borked with my card. |
| 6 |
>> |
| 7 |
>> Did you check out the "error" field of ifconfig's output for the interface |
| 8 |
>> of your card? |
| 9 |
>> |
| 10 |
>> Regards, |
| 11 |
>> Dw. |
| 12 |
> |
| 13 |
> Hmmm ... No, I have not had that opportunity. The server is located 2000km away from me, and I |
| 14 |
> usually call a guy (who is not a technician)to go in and press CTRL-ALT-DEL on a keyboard. That is |
| 15 |
> the short-time "fix". But I'm going to have a look physically on the server in a couple of weeks, |
| 16 |
> so if I get positive feedbacks from others as well regarding 2.6.27 kernel, I'm willing to try that |
| 17 |
> upgrade. |
| 18 |
> |
| 19 |
> This interface is an on-board interface in an IBM eServer. The first time it happened, it was no |
| 20 |
> problems for about 28 days. Now it was 13 days. So I expect it to happen again, soon enough. |
| 21 |
> |
| 22 |
> I'll try to hack the shutdown scripts to dump the ifconfig info somewhere somehow. |
| 23 |
|
| 24 |
Then it happened again ... and I have ifconfig stats for the interface: |
| 25 |
|
| 26 |
eth0 Link encap:Ethernet HWaddr 00:14:5e:5d:3c:d0 |
| 27 |
inet6 addr: fe80::214:5eff:fe5d:3cd0/64 Scope:Link |
| 28 |
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 |
| 29 |
RX packets:10551633 errors:4294967239 dropped:767 overruns:0 |
| 30 |
frame:170 |
| 31 |
TX packets:9371606 errors:4294967239 dropped:0 overruns:0 carrier:0 |
| 32 |
collisions:4294967239 txqueuelen:1000 |
| 33 |
RX bytes:28237000 (26.9 MiB) TX bytes:163377979 (155.8 MiB) |
| 34 |
Interrupt:16 |
| 35 |
|
| 36 |
From the kernel log I see this: |
| 37 |
|
| 38 |
Dec 12 12:19:21 fw [74355.059369] tg3: tg3_abort_hw timed out for world, |
| 39 |
TX_MODE_ENABLE will not clear MAC_TX_MODE=ffffffff |
| 40 |
Dec 12 12:19:24 fw [74357.842979] tg3: world: No firmware running. |
| 41 |
Dec 12 12:19:41 fw [74374.992867] tg3: world: Link is down. |
| 42 |
|
| 43 |
I'm surprised by the errors and collision numbers here, as I checked it the |
| 44 |
other day, and all of them was 0. I also know that the TX and RX values |
| 45 |
was above 3-4GB, but don't remember which was what. |
| 46 |
|
| 47 |
Could this be an overflow bug of some kind? |
| 48 |
|
| 49 |
I have also found out that IBM have released an updated firmware to this |
| 50 |
network device, so I'll try to upgrade it during Christmas when I'm close |
| 51 |
to the box again. In the mean time I have a little ping-script, which |
| 52 |
restarts network (incl. reloading of the tg3 module) when the network dies. |
| 53 |
This restart gives me minimal downtime. |
| 54 |
|
| 55 |
But I do not understand why this box was so rock solid until I upgraded |
| 56 |
from 2.6.22-hardened-r8 to 2.6.25-hardened-r8. The new kernel driver |
| 57 |
obviously does something it didn't do before. Unfortunately I can't find |
| 58 |
anything particular in the kernel git logs for the tg3.[ch] files which |
| 59 |
could pin-point anything particular. |
| 60 |
|
| 61 |
|
| 62 |
Does anyone have any experiences regarding firmware upgrades on these |
| 63 |
cards? The instructions seems pretty much forward, but if you know about |
| 64 |
anything, whatever, I would appreciate that. |
| 65 |
|
| 66 |
|
| 67 |
kind regards, |
| 68 |
|
| 69 |
David Sommerseth |
Archives