From: Jim Gifford <maillist@jg555.com>
To: sparclinux@vger.kernel.org
Subject: Re: Netra X1 - Tulip Issues - Since 2.6.24
Date: Mon, 06 Oct 2008 02:40:22 +0000 [thread overview]
Message-ID: <48E97A96.6040403@jg555.com> (raw)
In-Reply-To: <48E652A7.3010202@jg555.com>
BERTRAND Joel wrote:
> Jim Gifford a écrit :
>> Currently running 2.6.24-gentoo-r8 and 2.6.25-gentoo-r7. Also have
>> tried the vanilla kernel as well.
>>
>> It appears the issues seems to be isolated tot he Sparc X1's my x86's
>> using the tulip driver are not having the issue.
>>
>> Not sure if it's a reporting issue or just a problem with the driver.
>> Every packet seems to be an error. I've ran out of resources trying
>> to figure this out on my own, but no luck. Seems to be TX issue only.
>
> This is a known trouble that seems to be fixed in 2.6.26. If I
> remember, this trouble is older than 2.6.24. I have seen the same with
> 3Com adapter since 2.6.19 and it affected all archs.
>
> Regards,
>
> JKB
> --
> To unsubscribe from this list: send the line "unsubscribe sparclinux" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Just put on 2.6.26 on there, still happening, not as much. It dies with
these errors under 2.6.26. Here are the 2 last ones. It takes a few
hours to bomb, but it does.
Oct 5 04:33:09 mail kernel: [13368.070731] NETDEV WATCHDOG: eth0:
transmit timed out
Oct 5 04:33:09 mail kernel: [13368.072165] ------------[ cut here
]------------
Oct 5 04:33:09 mail kernel: [13368.072177] WARNING: at
net/sched/sch_generic.c:222 dev_watchdog+0x10c/0x140()
Oct 5 04:33:09 mail kernel: [13368.072189] Modules linked in:
openpromfs tulip
Oct 5 04:33:09 mail kernel: [13368.072204] Call Trace:
Oct 5 04:33:09 mail kernel: [13368.072212] [00000000005e68cc]
dev_watchdog+0x114/0x140
Oct 5 04:33:09 mail kernel: [13368.072227] [000000000045fc8c]
run_timer_softirq+0x174/0x1e0
Oct 5 04:33:09 mail kernel: [13368.072249] [000000000045b0bc]
__do_softirq+0x64/0xe0
Oct 5 04:33:09 mail kernel: [13368.072264] [000000000045b198]
do_softirq+0x60/0x80
Oct 5 04:33:09 mail kernel: [13368.072277] [000000000045b344]
irq_exit+0x8c/0xc0
Oct 5 04:33:09 mail kernel: [13368.072290] [000000000043307c]
timer_interrupt+0x64/0xc0
Oct 5 04:33:09 mail kernel: [13368.072306] [00000000004209d4]
tl0_irq14+0x1c/0x20
Oct 5 04:33:09 mail kernel: [13368.072323] [0000000000427d00]
cpu_idle+0x28/0xc0
Oct 5 04:33:09 mail kernel: [13368.072338] [000000000070ca1c]
start_kernel+0x284/0x2c0
Oct 5 04:33:09 mail kernel: [13368.072365] [000000000063c964]
tlb_fixup_done+0x88/0x9c
Oct 5 04:33:09 mail kernel: [13368.072380] [0000000000000000] 0x8
Oct 5 04:33:09 mail kernel: [13368.072392] ---[ end trace
bad8983fa8581c2e ]---
Oct 5 13:47:51 mail kernel: [11186.068395] NETDEV WATCHDOG: eth0:
transmit timed out
Oct 5 13:47:51 mail kernel: [11186.069824] ------------[ cut here
]------------
Oct 5 13:47:51 mail kernel: [11186.069836] WARNING: at
net/sched/sch_generic.c:222 dev_watchdog+0x10c/0x140()
Oct 5 13:47:51 mail kernel: [11186.069847] Modules linked in:
openpromfs tulip
Oct 5 13:47:51 mail kernel: [11186.069863] Call Trace:
Oct 5 13:47:51 mail kernel: [11186.069870] [00000000005e68cc]
dev_watchdog+0x114/0x140
Oct 5 13:47:51 mail kernel: [11186.069885] [000000000045fc8c]
run_timer_softirq+0x174/0x1e0
Oct 5 13:47:51 mail kernel: [11186.069906] [000000000045b0bc]
__do_softirq+0x64/0xe0
Oct 5 13:47:51 mail kernel: [11186.069921] [000000000045b198]
do_softirq+0x60/0x80
Oct 5 13:47:51 mail kernel: [11186.069934] [000000000045b344]
irq_exit+0x8c/0xc0
Oct 5 13:47:51 mail kernel: [11186.069946] [000000000043307c]
timer_interrupt+0x64/0xc0
Oct 5 13:47:51 mail kernel: [11186.069963] [00000000004209d4]
tl0_irq14+0x1c/0x20
Oct 5 13:47:51 mail kernel: [11186.069979] [0000000000427d0c]
cpu_idle+0x34/0xc0
Oct 5 13:47:51 mail kernel: [11186.069994] [000000000070ca1c]
start_kernel+0x284/0x2c0
Oct 5 13:47:51 mail kernel: [11186.070020] [000000000063c964]
tlb_fixup_done+0x88/0x9c
Oct 5 13:47:51 mail kernel: [11186.070035] [0000000000000000] 0x8
Oct 5 13:47:51 mail kernel: [11186.070047] ---[ end trace
57f9d9a3f577b443 ]---
Oct 5 13:47:59 mail kernel: [11194.064398] NETDEV WATCHDOG: eth0:
transmit timed out
Oct 5 13:48:07 mail kernel: [11202.060400] NETDEV WATCHDOG: eth0:
transmit timed out
Oct 5 13:48:15 mail kernel: [11210.056403] NETDEV WATCHDOG: eth0:
transmit timed out
Oct 5 13:48:23 mail kernel: [11218.052407] NETDEV WATCHDOG: eth0:
transmit timed out
Oct 5 13:48:31 mail kernel: [11226.048412] NETDEV WATCHDOG: eth0:
transmit timed out
Oct 5 13:48:39 mail kernel: [11234.044411] NETDEV WATCHDOG: eth0:
transmit timed out
prev parent reply other threads:[~2008-10-06 2:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 17:13 Netra X1 - Tulip Issues - Since 2.6.24 Jim Gifford
2008-10-03 17:44 ` BERTRAND Joel
2008-10-06 2:40 ` Jim Gifford [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=48E97A96.6040403@jg555.com \
--to=maillist@jg555.com \
--cc=sparclinux@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.