mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Francois Romieu <romieu@fr.zoreil.com>
To: Udo van den Heuvel <udovdh@xs4all.nl>
Cc: LKML <linux-kernel@vger.kernel.org>, netdev@vger.kernel.org
Subject: Re: kernel: TD structure error TDindex=e
Date: Sun, 20 Jul 2008 18:08:12 +0200	[thread overview]
Message-ID: <20080720160812.GA23652@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <48835302.1090708@xs4all.nl>

Udo van den Heuvel <udovdh@xs4all.nl> :
[...]
> 16:41:09 recorder kernel: TD structure error TDindex=e
> 
> This was on a VIA EN12000 board (with VIA Velocity Gbit ethernet,
> running 2.6.25.7) while doing a file transfer. The card was `down` after
> that.
[...]
> How can I avoid/fix/etc this situation ?

Can you apply the patch below to get some more information ?

May I assume that it does not count as a regression ?

Thanks in advance.

diff --git a/drivers/net/via-velocity.c b/drivers/net/via-velocity.c
index 370ce30..57ee35b 100644
--- a/drivers/net/via-velocity.c
+++ b/drivers/net/via-velocity.c
@@ -1743,7 +1743,8 @@ static void velocity_error(struct velocity_info *vptr, int status)
 	if (status & ISR_TXSTLI) {
 		struct mac_regs __iomem * regs = vptr->mac_regs;
 
-		printk(KERN_ERR "TD structure error TDindex=%hx\n", readw(&regs->TDIdx[0]));
+		printk(KERN_ERR "Tx process error TDIdx=0x%04x TXESR=0x%02x\n",
+		       readw(&regs->TDIdx[0]), readb(&regs->TXESR));
 		BYTE_REG_BITS_ON(TXESR_TDSTR, &regs->TXESR);
 		writew(TRDCSR_RUN, &regs->TDCSRClr);
 		netif_stop_queue(vptr->dev);
-- 
Ueimor

  reply	other threads:[~2008-07-20 16:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-20 15:00 Udo van den Heuvel
2008-07-20 16:08 ` Francois Romieu [this message]
2008-07-20 16:14   ` Udo van den Heuvel
     [not found]   ` <48836EB3.3050707@xs4all.nl>
     [not found]     ` <20080720171440.GB23278@electric-eye.fr.zoreil.com>
2008-07-23 15:52       ` Udo van den Heuvel
2008-07-26 13:31       ` Udo van den Heuvel

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=20080720160812.GA23652@electric-eye.fr.zoreil.com \
    --to=romieu@fr.zoreil.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=udovdh@xs4all.nl \
    /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

all inboxes | Powered by JetHome®