Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 93301 - skge network driver reports "hw tcp v4 csum failed"
Summary: skge network driver reports "hw tcp v4 csum failed"
Status: RESOLVED LATER
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: AMD64 Linux
: High minor (vote)
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-20 00:59 UTC by Sebastian Spaeth
Modified: 2005-09-11 08:10 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastian Spaeth 2005-05-20 00:59:32 UTC
my dmesg:
skge eth0: enabling interface
skge eth0: Link is up at 100 Mbps, full duplex, flow control none
hw tcp v4 csum failed
hw tcp v4 csum failed
hw tcp v4 csum failed
...
The last line is repeated hundreds of times in dmesg. The network don't seems to
malfunction though. Just a too verbose debug message or an indicator for bad stuff?

my lspci:
0000:00:0a.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit
Ethernet Controller (rev 13)


Reproducible: Always
Steps to Reproduce:
Comment 1 Daniel Drake (RETIRED) gentoo-dev 2005-05-21 05:08:02 UTC
Please add:
#define DEBUG 1
to start of drivers/net/skge.c

Recompile your kernel with skge as a module. Don't autoload it. Reboot.
Load the module with:
  modprobe skge debug=16

Run dmesg and see if you can see any of the "csum failed messages" (they will be
mixed in with some other debug info). If you can't, you might need to bring the
network interface up first (/etc/init.d/net.eth0 start)
Once you've got that far, please attach the dmesg output here.
Comment 2 Sebastian Spaeth 2005-05-22 02:23:47 UTC
OK, when compiling the module I get:
drivers/net/skge.c: In function `skge_xmit_frame':
drivers/net/skge.c:2379: Warnung: int Format, anderer Typ Argument (Argument 3)
drivers/net/skge.c: In function `skge_poll':
drivers/net/skge.c:2610: Warnung: int Format, anderer Typ Argument (Argument 3)
drivers/net/skge.c: In function `skge_tx_intr':
drivers/net/skge.c:2670: Warnung: int Format, anderer Typ Argument (Argument 3)

I suppose this is because I run an 64 bit system (athlon64).
Next, I loaded it. Dmesg output:

skge addr 0xfdb00000 irq 177 chip Yukon-Lite rev 7
skge eth0: addr 00:11:2f:61:63:bb
skge eth0: enabling interface
yukon_init
skge_up completed
yukon phy intr istat=1c40 phy_stat=7d00
yukon_link_up
skge eth0: Link is up at 100 Mbps, full duplex, flow control none


a "watch "dmesg|grep csum"" did not show anything for the first hours (I think).
But now after quite a while running I get bad csum messages frequently. Here are
two example snippets from dmesg:

skge eth0: rx slot 324 status 0x5bc0100 len 1468
eth0: tx queued, slot 47, len 54
skge eth0: tx done slot 47 status 0x0
skge eth0: rx slot 325 status 0x5bc0100 len 1468
eth0: tx queued, slot 48, len 54
skge eth0: tx done slot 48 status 0x0
skge eth0: rx slot 326 status 0x420100 len 66
skge eth0: rx slot 327 status 0x4e0100 len 78
hw tcp v4 csum failed
skge eth0: rx slot 328 status 0x3f60100 len 1014
eth0: tx queued, slot 49, len 54
skge eth0: tx done slot 49 status 0x0
skge eth0: rx slot 329 status 0x5e20100 len 1506
skge eth0: rx slot 330 status 0x38f0100 len 911
skge eth0: rx slot 331 status 0x6a0100 len 106
eth0: tx queued, slot 50, len 1494
skge eth0: tx done slot 50 status 0x0


eth0: tx queued, slot 121, len 66
skge eth0: tx done slot 121 status 0x0
skge eth0: rx slot 342 status 0x4b30100 len 1203
skge eth0: rx slot 343 status 0x1ad0100 len 429
eth0: tx queued, slot 122, len 54
skge eth0: tx done slot 122 status 0x0
skge eth0: rx slot 344 status 0x3e0100 len 62
hw tcp v4 csum failed
skge eth0: rx slot 345 status 0x5bc0100 len 1468
eth0: tx queued, slot 123, len 54
skge eth0: tx done slot 123 status 0x0
skge eth0: rx slot 346 status 0x5bc0100 len 1468
eth0: tx queued, slot 124, len 54
skge eth0: tx done slot 124 status 0x0
skge eth0: rx slot 347 status 0x5e20100 len 1506
skge eth0: rx slot 348 status 0x6a0100 len 106
Comment 3 Daniel Drake (RETIRED) gentoo-dev 2005-05-23 07:50:47 UTC
Stephen,

Sorry to bother you with another skge issue. Is this bug report anything to
worry about? (I'm not even sure if it directly relates to skge)
Comment 4 Perry Lu 2005-06-24 12:59:56 UTC
I'm experiencing the same problem, though I'm not noticing anything bad
happening, it's indeed quite annoying to see my kernel log flooded with it. The
msg disappears after I switched back to sk98lin.


here's my emerge info:

Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130,
glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r11 i686)
=================================================================
System uname: 2.6.11-gentoo-r11 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz
Gentoo Base System version 1.6.12
Python:              dev-lang/python-2.3.5 [2.3.5 (#1, Jun 16 2005, 05:33:57)]
ccache version 2.3 [enabled]
dev-lang/python:     2.3.5
sys-apps/sandbox:    1.2.9
sys-devel/autoconf:  2.59-r6, 2.13
sys-devel/automake:  1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.5
sys-devel/binutils:  2.15.92.0.2-r10
sys-devel/libtool:   1.5.16
virtual/os-headers:  2.6.8.1-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -march=prescott -fomit-frame-pointer -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/
/usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/
/usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=prescott -fomit-frame-pointer -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache digest distlocks fixpackages sandbox
sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
LANG="en_CA.utf8"
LDFLAGS="-Wl,-O1"
LINGUAS="en ja zh_CN zh_TW"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portagejp /usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 16bit X a52 aac aalib acpi alsa avi berkdb cairo ccache cdr cjk crypt
cups curl dga dhcp directfb divx4linux dvd dvdr elibc_glibc emboss encode esd
fam firefox flac font-server fortran gdbm gif gimp gimpprint gnome gpm gstreamer
gtk gtk2 gtkhtml hal imagemagick imlib ipv6 java jpeg kernel_linux ldap libg++
libwww lm_sensors mad maildir matroska mikmod mime mmx mono motif mp3 mpeg
mplayer mysql ncurses nfs nls nptl nvidia offensive ogg oggvorbis opengl pam
pdflib perl png posix python quicktime readline real rtc samba sdl slang spell
sse sse2 ssl svga tcltk tcpd tetex theora tiff truetype truetype-fonts
type1-fonts unicode usb userlocales v4l vorbis win32codecs xinetd xml xml2 xmms
xprint xscreensaver xv xvid zlib linguas_en linguas_ja linguas_zh_CN
linguas_zh_TW userland_GNU"
Unset:  ASFLAGS, CBUILD, CTARGET, LC_ALL
Comment 5 Daniel Drake (RETIRED) gentoo-dev 2005-06-27 15:54:34 UTC
This will be fixed in future versions of skge. This is nothing to worry about -
the fix will simply involve ignoring the checksum value, so just ignore it for
now. Thanks Stephen.
Comment 6 Stephen Hemminger 2005-09-01 21:56:38 UTC
Please try 
http://developer.osdl.org/~shemminger/prototypes/skge-1.0.tar.bz2
Comment 7 Daniel Drake (RETIRED) gentoo-dev 2005-09-11 08:10:45 UTC
FYI skge-1.0 is included in gentoo-sources-2.6.13-r1
Sebastian/Perry, please confirm the problem no longer exists there.