nve timeout (and down) regression?

Bjoern A. Zeeb bzeeb-lists at lists.zabbadoz.net
Thu Mar 23 19:00:11 UTC 2006

On Thu, 23 Mar 2006, JoaoBR wrote:


>> The other patch cited in the message has never been made:
>> diff -u -r1.7.2.4 if_nve.c
>> --- if_nve.c    9 Oct 2005 04:18:17 -0000
>> +++ if_nve.c    27 Oct 2005 09:58:45 -0000
>> @@ -727,7 +727,7 @@
>>         DEBUGOUT(NVE_DEBUG_INIT, "nve: nve_init_rings - entry\n");
>> -       sc->cur_rx = sc->cur_tx = sc->pending_rxs = sc->pending_txs = 0;
>> +       sc->cur_rx = sc->cur_tx = sc->pending_rxs = 0;
> and I did this part and my NIC is running, as I said still lot of collisions
> caused by it but it is running

If you have collisions you have most likeely a duplex mismatch.

If you read the code and I remember right   the above change is a NOP.

The timeouts have been there and are there. The difference with the
last commits is that a lot of people couldn't get the NIC working at
all before   and now it works (somewhat) but there are timeouts from
time to time which for some people seem to auto-recover and for
others still get things 'stuck'.

The problem is to diagnose what everyone really has
- branch running (RELENG_6 or HEAD)
- i386 or amd64
- exact FreeBSD revisions for if_nve.c
- if using patches which
- pciconf -lv | grep -A4 ^nve
- which board
- exact problems
 	* is the interface working at all
 	* is it just stuck from time to time
 	* ...

See http://www.freebsd.org/cgi/query-pr.cgi?pr=94524 for more
questions. You my want to submit a fllow up and add your description
with the answer to these questions there.

Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT

More information about the freebsd-stable mailing list