From: John M Flinchbaugh <john@hjsoft.com>
To: linux-kernel@vger.kernel.org
Subject: forcedeth trouble in 2.6.19(.1)
Date: Tue, 19 Dec 2006 07:24:47 -0500 [thread overview]
Message-ID: <20061219122447.GA23367@hjsoft.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
I saw a mention of interrupt handling for forcedeth cards is the
2.6.19.1 changelog, but I still see this error in 2.6.19.1. It started
in 2.6.19, and it didn't happen in 2.6.18.1.
Dec 17 05:35:29 butterfly kernel: [184432.371636] eth3: Tx timed out,
lost interrupt? TSR=0x3, ISR=0x97, t=2222.
Dec 17 05:35:31 butterfly kernel: [184433.370864] NETDEV WATCHDOG: eth3:
transmit timed out
Dec 17 05:35:31 butterfly kernel: [184433.370871] eth3: Tx timed out,
lost interrupt? TSR=0x3, ISR=0x3, t=1190.
Dec 17 05:35:34 butterfly kernel: [184434.869718] NETDEV WATCHDOG: eth3:
transmit timed out
Dec 17 05:35:34 butterfly kernel: [184434.869725] eth3: Tx timed out,
lost interrupt? TSR=0x3, ISR=0x3, t=1189.
Dec 17 05:35:37 butterfly kernel: [184436.368072] NETDEV WATCHDOG: eth3:
transmit timed out
Dec 17 05:35:37 butterfly kernel: [184436.368080] eth3: Tx timed out,
lost interrupt? TSR=0x3, ISR=0x97, t=2189.
Dec 17 05:35:39 butterfly kernel: [184437.367308] NETDEV WATCHDOG: eth3:
transmit timed out
Dec 17 05:35:39 butterfly kernel: [184437.367315] eth3: Tx timed out,
lost interrupt? TSR=0x3, ISR=0x3, t=1188.
Is this the same issue? Thanks.
--
John M Flinchbaugh
john@hjsoft.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-12-19 12:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 12:24 John M Flinchbaugh [this message]
2006-12-19 21:18 ` forcedeth trouble in 2.6.19(.1) Daniel Barkalow
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=20061219122447.GA23367@hjsoft.com \
--to=john@hjsoft.com \
--cc=linux-kernel@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.