Re[2]: eth

[amon <amon@mikule.net>]

Hello Cezary,

hym, w serwerze sa 3 karty, ciecie ruchu jest na eth1 i eth2.
na eth2 jest chyba z 5 userow na eth1 ponad 200.
i pada ta mniej obciazona?
co ciekawe co jakis czas ta karta poprostu przestaje dzialac
blokuje cala transmisje.

mozna zobaczycjeszcze cos takiego:
eth1      Link encap:Ethernet  HWaddr 00:10:4B:65:23:FC
          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:10589325 errors:2 dropped:0 overruns:2497 frame:2
          TX packets:11167944 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:2954549095 (2.7 GiB)  TX bytes:1655793497 (1.5 GiB)
          Interrupt:10 Base address:0xe000

eth2      Link encap:Ethernet  HWaddr 00:50:04:87:27:B7
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9007821 errors:20466 dropped:0 overruns:501 frame:30743
          TX packets:7929922 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:3084507737 (2.8 GiB)  TX bytes:3606342257 (3.3 GiB)
          Interrupt:12 Base address:0xe400
pozdrowka
jr


Saturday, December 7, 2002, 2:44:57 AM, you wrote:


CB> Najczesciej takie komunikaty pojawiaja sie przy cieciu ruchu na karcie
CB> przepelniaja sie bufory i leci info do kernela
CB> ale na 100% nie powiem ze to nie awaria
CB> pzw
CB> CB
>> Hello debian-user-polish,
>>
>> czy ta karta jest uszkodzona czy to cos programowego?
>> pasuje mi na awarie sprzetowa, ale chce sie upewnic.
>> z gory dzieki za pomoc
>> jr
>>
>> Dec  6 16:32:55 elgrom kernel: eth2: transmit timed out, tx_status 00
CB> status e080.
>> Dec  6 16:32:55 elgrom kernel:   diagnostics: net 0ec0 media 88a0 dma
CB> 000000a0.
>> Dec  6 16:32:55 elgrom kernel:   Flags; bus-master 1, dirty 979(3) current
CB> 995(3)
>> Dec  6 16:32:55 elgrom kernel:   Transmit list 0193c200 vs. c193c2c0.
>> Dec  6 16:32:55 elgrom kernel:   0: @c193c200  length 80000103 status
CB> 00000103
>> Dec  6 16:32:55 elgrom kernel:   1: @c193c240  length 800000da status
CB> 800000da
>> Dec  6 16:32:55 elgrom kernel:   2: @c193c280  length 8000002a status
CB> 8000002a
>> Dec  6 16:32:55 elgrom kernel:   3: @c193c2c0  length 8000003e status
CB> 0001003e
>> Dec  6 16:32:55 elgrom kernel:   4: @c193c300  length 8000003e status
CB> 0001003e
>> Dec  6 16:32:55 elgrom kernel:   5: @c193c340  length 8000002a status
CB> 0001002a
>> Dec  6 16:32:55 elgrom kernel:   6: @c193c380  length 8000018c status
CB> 0001018c
>> Dec  6 16:32:55 elgrom kernel:   7: @c193c3c0  length 80000042 status
CB> 00010042
>> Dec  6 16:32:55 elgrom kernel:   8: @c193c400  length 8000003e status
CB> 0001003e
>> Dec  6 16:32:55 elgrom kernel:   9: @c193c440  length 800002af status
CB> 000102af
>> Dec  6 16:32:55 elgrom kernel:   10: @c193c480  length 8000002a status
CB> 0001002a
>> Dec  6 16:32:55 elgrom kernel:   11: @c193c4c0  length 8000002a status
CB> 0001002a
>> Dec  6 16:32:55 elgrom kernel:   12: @c193c500  length 8000002a status
CB> 0001002a
>> Dec  6 16:32:55 elgrom kernel:   13: @c193c540  length 8000003e status
CB> 0001003e
>> Dec  6 16:32:55 elgrom kernel:   14: @c193c580  length 8000002a status
CB> 0001002a
>> Dec  6 16:32:55 elgrom kernel:   15: @c193c5c0  length 8000002a status
CB> 0001002a
>> Dec  6 16:32:55 elgrom kernel: eth2: Resetting the Tx ring pointer.
>>
>> --
>> Best regards,
>>  amon                          mailto:amon@mikule.net
>>




-- 
Best regards,
 amon                            mailto:amon@mikule.net