From: Denis Vlasenko <vda.linux@googlemail.com>
To: Manfred Spraul <manfred@colorfullife.com>,
Jeff Garzik <jeff@garzik.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: 2.6.18 forcedeth GSO panic on send
Date: Fri, 27 Oct 2006 01:17:57 +0200 [thread overview]
Message-ID: <200610270117.57877.vda.linux@googlemail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
Hello,
I am using an AMD64 box with 32bit userspace / 64bit kernel.
Kernels 2.6.18 and 2.6.18.1 semi-randomly hang when I upload stuff
over the net - for example, "svn commit", scp are affected.
2.6.17.11 does not seem to be affected.
Unfortunately even 60-line screen is not big enough
to catch whole trace. There are at least two traces,
and first scrolls off. I have a photo at
http://busybox.net/~vda/gso_panic/forcedeth_gso_panic.jpg
Something bad is happening here, when kernel tries
to send some data:
...
error_exit
skb_over_panic
skb_over_panic
skb_segment
tcp_tso_segment
inet_gso_segment
skb_gso_segment
dev_hard_start_xmit
dev_queue_xmit
...
Looks like it is related to hardware accel in forcedeth.
I will try disabling all hw accel.
Please find in attached tarball:
.config
dmesg
ethtool-k
lspci
lspci-v
--
vda
[-- Attachment #2: gso_panic.tar.bz2 --]
[-- Type: application/x-tbz, Size: 15933 bytes --]
next reply other threads:[~2006-10-26 23:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 23:17 Denis Vlasenko [this message]
2006-10-27 3:58 ` 2.6.18 forcedeth GSO panic on send Herbert Xu
2006-10-29 12:55 ` Denis Vlasenko
2006-10-29 14:10 ` Herbert Xu
2006-10-29 21:45 ` Denis Vlasenko
2006-10-29 21:57 ` Denis Vlasenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200610270117.57877.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.