From: Arjan van de Ven <arjan@linux.intel.com>
To: NetDev <netdev@vger.kernel.org>
Cc: ilpo.jarvinen@helsinki.fi, David Miller <davem@davemloft.net>
Subject: Two TCP/IP warnings in 2.6.25-rc7-git1
Date: Mon, 31 Mar 2008 14:05:04 -0700 [thread overview]
Message-ID: <47F15200.3060706@linux.intel.com> (raw)
Hi,
kerneloops.org still has 3 tcp/ip related warnings in the top 15 of oopses/warnings
that users (mostly of Fedora 9 alpha/beta, but also LKML and netdev) see.
All three have been seen as recent as 2.6.25-rc7-git1, but seem to date back to around
2.6.24-rc4 era.
Number 1 is a WARN_ON in tcp_ack(), there are several backtraces at
http://www.kerneloops.org/search.php?search=tcp_ack but the core
comes down to the following:
tcp_ack
tcp_rcv_established
tcp_v4_do_rcv
tcp_v4_rcv
ip_local_deliver_finish
ip_local_deliver
ip_rcv_finish
ip_rcv
netif_receive_skb
tg3_poll or nv_napi_poll or the e1000 equivalent
net_rx_action
__do_softirq
do_softirq
irq_exit
do_IRQ
Number 2 is a WARN_ON in tcp_enter_frto(), backtraces at
http://www.kerneloops.org/search.php?search=tcp_enter_frto
the core backtrace comes down to
tcp_enter_frto
tcp_write_timer
run_timer_softirq
__do_softirq
do_softirq
Number 3 is a WARN_ON in tcp_mark_head+lost, backtraces at
http://www.kerneloops.org/search.php?search=tcp_mark_head_lost
the core backtrace comes down to
tcp_mark_head_lost
tcp_ack
tcp_rcv_established
tcp_v4_do_rcv
tcp_v4_rcv
ip_local_deliver_finish
ip_local_deliver
ip_rcv_finish
ip_rcv
netif_receive_skb
tg3_poll or nv_napi_poll
net_rx_action
__do_softirq
The URLs link to several mailinglist/bugzilla postings for these.
Note that not all backtraces have such a thing; a lot of these backtraces
are collected by an automated daemon and submitted directly from testers/users
systems to the database.
next reply other threads:[~2008-03-31 21:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 21:05 Arjan van de Ven [this message]
2008-04-03 5:21 ` Three TCP/IP warnings in 2.6.25-rc7-git1 Arjan van de Ven
2008-04-03 5:28 ` David Miller
2008-04-03 5:40 ` Arjan van de Ven
2008-04-03 5:56 ` Denys Fedoryshchenko
2008-04-03 9:53 ` Ilpo Järvinen
2008-04-03 12:14 ` Denys Fedoryshchenko
2008-04-03 13:11 ` Ilpo Järvinen
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=47F15200.3060706@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=davem@davemloft.net \
--cc=ilpo.jarvinen@helsinki.fi \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).