Claudiu Cismaru wrote:
>
> while ((status = inw(ioaddr + EL3_STATUS)) &
> (IntLatch | RxComplete | StatsFull)) {
> > Cauta si tu mai departe in source ce inseamna IntLatch, RxComplete,
> StatsFull...
Nu stiu daca am skills sau "voie" sa ma bag asa jos.
> <o posibila presupunere> E posibil ca handler-ul de functie
> (intrerupere) sa nu ti se apeleze o perioada mai mare de timp, iar cand
> se apeleaza sa fie prea multa informatie de procesat ?? Adica din cauza
> aia sa nu-i fie suficient un 20 iteratii sa proceseze toate
> informatiile. Sau poate ca informatiile sa nu fie citite corect din
> placa... </o posibila presupunere>
cam asa : (sorry de url-ul wrapped)
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&safe=off&threadm=347D8D6D.2EC5B16B%40anti-spam.bbsrc.ac.uk&rnum=8&prev=/groups%3Foi%3Ddjq%26as_q%3D%2522Infinite%2Bloop%2Bin%2Binterrupt%2522%26num%3D100
quote :
The message is generated when the interrupt handler is exited when there
are still more events to process. The routine is configured to handle a
maximum of 10 events per interrupt(at least at 2.0.32). The status is
saying the interrupt is latched and receive complete(2011). For a diskless
machine that is a slower i386 maybe you will want to tune the 10 events per
interrupt up a little. There is a #define at the beginning of the code for
this and some comments about the assumptions in programming the card that
will be of particular interest to you.
I assume the adapter is not in promiscuous mode and these messages are
occurring with normal load, so you may want to tune it up a little for your
environment. Some of those status messages are saying stats full
(2081,2091), which may indicate that you may occasionally be loosing
some packets since your not always keeping up.
/quote
treaba e ca interfata aia e in promisc din cauza snort-ului (toate sunt).
thanks pt raspuns. .. dar tot nu inteleg :
1.daca asta imi cauzeaza inghetarea sistemului
2. de ce numai una din placi face figurile astea . ( poate asa am motiv
de upgrade :)
numa' bine
Dragos.
