Skip to contentSkip to conversation

kernel: TD structure error TDindex=e

DISCUSSION Udo van den Heuvel 2 participants 5 messages Jul 20, 2008 – Jul 26, 2008 2 messages not in the archive

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

Hello,

In the logs I found a message:

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.
After ifconfig eth0 down, ifconfig eth0 up the device was functional again but the system froze at a new file transfer attempt.

How can I avoid/fix/etc this situation?

Kind regards,
Udo

#1 lore raw

Udo van den Heuvel <[email protected]> :
[...]

Quoted 5 lines

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.

[...]

Quoted 1 line

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.

drivers/net/via-velocity.c +2 -1
index 370ce30..57ee35b 100644
@@ -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);
Signature · 1 line
Ueimor
#2 lore raw
Quoted 3 lines · Francois Romieu

Udo van den Heuvel <[email protected]> :
[...]

Quoted 1 line

16:41:09 recorder kernel: TD structure error TDindex=e

(...)

Quoted 3 lines
Quoted 1 line

How can I avoid/fix/etc this situation ?

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

Will do, will look for an earliest opportinuty to boot the machine with the patched kernel.

Quoted 1 line

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

Can't confirm/deny.
It has 'hung' before.

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#5 lore raw
Quoted 7 lines · Francois Romieu

Udo van den Heuvel <[email protected]> :

Quoted 6 lines
Quoted 1 line · Francois Romieu

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

Patch applied well.
Did come file transfers (recordings from MythTV via MythWeb). Worked Ok until after a few files the system hang. No special logging, though:

Quoted 9 lines
Quoted 4 lines
Jul 20 18:24:31 recorder ntpd[1524]: synchronized to 192.168.10.98,
stratum 1
Jul 20 18:24:48 recorder kernel: eth0: excessive work at interrupt.
Jul 20 18:26:44 recorder kernel: eth0: excessive work at interrupt.

Shit.

Can you apply the bandaid below too ?

With that patch, so far, it doesn't hang. I transfered multiple GB's from the EN12000 via it's MythTV web interface, receiving the data on my workstation with wget.
I get transfers of ~40MB/s.
Transfers are 40+MB/s with some small pauses here and there.

I only see sometimes messages like kernel: eth0: excessive work at interrupt. Not often.

Kind regards,
Udo

#6 lore raw
In reply to a message not in the archive
Quoted 1 line · Francois Romieu

Can you apply the bandaid below too ?

Today, during a http transfer of a 5.xGB file the EN12000 system hang. There was nothing in /var/log/messages.

So even with this patch something still goes wrong during high-speed/large transfers, be it perhaps less often (as it appears) since using the patch.

Udo