From: Philip Prindeville <philipp_subx@redfish-solutions.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: Seeing transmit timeouts on 8139cp
Date: Sat, 08 Jan 2011 13:09:06 -0800 [thread overview]
Message-ID: <4D28D272.2070900@redfish-solutions.com> (raw)
In-Reply-To: <4C99A289.2030109@redfish-solutions.com>
On 9/21/10 11:30 PM, Philip Prindeville wrote:
> On 9/17/10 1:00 PM, Francois Romieu wrote:
>> Philip Prindeville<philipp_subx@redfish-solutions.com> :
>> [...]
>>> Does this look familiar to anyone?
>> 349124a00754129a5f1e43efa84733e364bf3749 ?
>>
>> It would be a bit too easy.
>>
> Thanks. I'll give it a try now.
No, that's not the problem. Still seeing traces, even after applying that patch.
This is in 2.6.27.57:
Jan 8 00:11:25 pdx user.warn kernel: ------------[ cut here ]------------
Jan 8 00:11:25 pdx user.warn kernel: WARNING: at net/sched/sch_generic.c:219 dev_watchdog+0xf1/0x176()
Jan 8 00:11:25 pdx user.info kernel: NETDEV WATCHDOG: eth1 (8139cp): transmit timed out
Jan 8 00:11:25 pdx user.warn kernel: Modules linked in: pppoatm pppox ppp_generic slhc bridge stp llc solos_pci atm dummy ath5k mac80211 ath cfg80211 rfkill_backport compat dahdi sha512_generic sha256_generic deflate zlib_deflate arc4 ecb sha1_generic blowfish des
Jan 8 00:11:25 pdx user.warn kernel: Pid: 0, comm: swapper Tainted: P 2.6.27.57-astlinux #1
Jan 8 00:11:25 pdx user.warn kernel: [<c0115462>] warn_slowpath+0x61/0x84
Jan 8 00:11:25 pdx user.warn kernel: [<c026649b>] nf_hook_slow+0x44/0xb1
Jan 8 00:11:25 pdx user.warn kernel: [<e018d968>] br_nf_pre_routing_finish+0x0/0x257 [bridge]
Jan 8 00:11:25 pdx user.warn kernel: [<e018e5a3>] br_nf_pre_routing+0x532/0x54b [bridge]
Jan 8 00:11:25 pdx user.warn kernel: [<c01065e8>] read_tsc+0x6/0x22
Jan 8 00:11:25 pdx user.warn kernel: [<c01289a6>] getnstimeofday+0x4a/0xc7
Jan 8 00:11:25 pdx user.warn kernel: [<c01267ca>] ktime_get_ts+0x1d/0x3f
Jan 8 00:11:25 pdx user.warn kernel: [<c0126056>] hrtimer_forward+0xe2/0xfe
Jan 8 00:11:25 pdx user.warn kernel: [<c025e0b3>] dev_watchdog+0x0/0x176
Jan 8 00:11:25 pdx user.warn kernel: [<c01cfb57>] strlcpy+0x15/0x62
Jan 8 00:11:25 pdx user.warn kernel: [<c025e1a4>] dev_watchdog+0xf1/0x176
Jan 8 00:11:25 pdx user.warn kernel: [<e00e7f3c>] coretimer_func+0xb1/0x133 [dahdi]
Jan 8 00:11:25 pdx user.warn kernel: [<c011c05a>] run_timer_softirq+0x116/0x17a
Jan 8 00:11:25 pdx user.warn kernel: [<c0118ce4>] __do_softirq+0x35/0x75
Jan 8 00:11:25 pdx user.warn kernel: [<c0118d46>] do_softirq+0x22/0x26
Jan 8 00:11:25 pdx user.warn kernel: [<c0118f20>] irq_exit+0x25/0x30
Jan 8 00:11:25 pdx user.warn kernel: [<c010477c>] do_IRQ+0x4d/0x5d
Jan 8 00:11:25 pdx user.warn kernel: [<c010394b>] common_interrupt+0x23/0x28
Jan 8 00:11:25 pdx user.warn kernel: [<c0106f3d>] default_idle+0x25/0x38
Jan 8 00:11:25 pdx user.warn kernel: [<c010254b>] cpu_idle+0x37/0x5f
Jan 8 00:11:25 pdx user.warn kernel: =======================
Jan 8 00:11:25 pdx user.warn kernel: ---[ end trace 4eb2e0ef5bc6569d ]---
Jan 8 00:11:25 pdx user.warn kernel: eth1: Transmit timeout, status c 2b 0 80ff
Any other ideas?
Thanks.
prev parent reply other threads:[~2011-01-08 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 5:10 Seeing transmit timeouts on 8139cp Philip Prindeville
2010-09-17 20:00 ` Francois Romieu
2010-09-22 6:30 ` Philip Prindeville
2011-01-08 21:09 ` Philip Prindeville [this message]
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=4D28D272.2070900@redfish-solutions.com \
--to=philipp_subx@redfish-solutions.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/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.