Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Apr 2010 15:34:52 GMT
From:      Gennady Kudryashoff <gennady@gmx.com>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   kern/145918: After spontaneous ae0 "watchdog timeout", "stray Tx interrupt(s)", "size mismatch" messages, interface hangs up
Message-ID:  <201004211534.o3LFYqGI032718@www.freebsd.org>
Resent-Message-ID: <201004211540.o3LFe2Wa068643@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         145918
>Category:       kern
>Synopsis:       After spontaneous ae0 "watchdog timeout", "stray Tx interrupt(s)", "size mismatch" messages, interface hangs up
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Apr 21 15:40:02 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator:     Gennady Kudryashoff
>Release:        FreeBSD 7.3 Release
>Organization:
Federal Migration Service, Russia, Moscow branch
>Environment:
FreeBSD morannon.home 7.3-RELEASE FreeBSD 7.3-RELEASE #0: Sun Mar 21 06:15:01 UTC 2010     root@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
The box works as test NAT+Router+Firewall machine (AsusEEE PC 701), ae0 is internal network interface (ext is axe0).

There are spontaneous messages like that:

ae0: Size mismatch: TxS:384 TxD:14900
ae0: Received stray Tx interrupt(s).
ae0: Size mismatch: TxS:392 TxD:12336
ae0: Size mismatch: TxS:388 TxD:29285
ae0: Size mismatch: TxS:368 TxD:28270
ae0: Size mismatch: TxS:400 TxD:14896
ae0: Size mismatch: TxS:382 TxD:25445
ae0: watchdog timeout - resetting.

or

ae0: watchdog timeout - resetting.

or

ae0: Size mismatch: TxS:384 TxD:2573
ae0: Received stray Tx interrupt(s).
ae0: watchdog timeout - resetting.

After that messages appears on console and dmesg, interface doesn't respond. The only solution is

ifconfig ae0 down && ifconfig ae0 up

to make it work properly.

This behaviour is unpredictable on time and appears both under mid-heavy load and in idle state (no internal connections).

Also, according to message in http://forums.freebsd.org/showthread.php?s=3a2a2318a953d85109318a2ca26f24f0&t=11528 such behaviour seems to appear on FreeBSD 8.

I believe that a problem in the driver, because OpenBSD with different driver implementation (lii) and ArchLinux with 2.6.33 kernel works well.

>How-To-Repeat:
Install FreeBSD 7.3 on AsusEEE 701, and just wait some time (from 2h to 48h).

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201004211534.o3LFYqGI032718>