Skip to contentSkip to conversation

Timeouts on EP-HDA3+ Motherboard

VIA-RHINE Peter Schaefer 2 participants 7 messages Aug 9, 2004 – Aug 11, 2004

lore
Share & tools
lore
#0 lore raw

Hello!

I'm getting reproducable errors when Samba is transferring large files:

eth0: Transmit timed out, status 0000, PHY status 786d, resetting...

This is not the case if such a file is transferred using FTP.

And yes, im running with "pci=noacpi,usepirqmask,biosirq noapic" (otherwise the problem happens so frequently that eth0 is more or less unusable).

I know that the Via-Rhine hardware and/or the driver isn't perfect, but b/c i'm having a reproducable testcase here, i thought i might be able to assist in fixing this problem (if it is fixable at all, of course). In addition, as this machine is mainly a Samba fileserver it's getting pretty annoying.

I'm using an Epox EP-8HDA3+ Athlon64 Motherboard with VIA K8T800 chipset. The board has two on-board ethernet devices, the VIA Rhine 100BaseT and an 3Com/Marvell 1000BaseT chip. Both are sharing it's interrupts with each other and on-board USB devices (however i'm neither using the Marvell nor any USB peripherals):

PCI: Sharing IRQ 12 with 0000:00:08.0
PCI: Sharing IRQ 12 with 0000:00:10.0
PCI: Sharing IRQ 12 with 0000:00:10.1
PCI: Sharing IRQ 12 with 0000:00:12.0

0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8385 [K8T800 AGP] Host Bridge (rev 01)
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800 South]
0000:00:08.0 Ethernet controller: 3Com Corporation 3c940 10/100/1000Base-T [Marvell] (rev 12)
0000:00:09.0 SCSI storage controller: Adaptec AHA-2940U/UW/D / AIC-7881U
0000:00:0e.0 RAID bus controller: Silicon Image, Inc. (formerly CMD Technology Inc) SiI 3114 [SATALink/SATARaid] Serial ATA Controller (rev 02) 0000:00:0f.0 IDE interface: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
0000:00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
0000:00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
0000:00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [K8T800 South]
0000:00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE]

*Please CC me, because i'm not subscribed to the list*

Thanks and best regards,

Peter

#1 lore raw
Quoted 4 lines · Peter Schaefer

I'm getting reproducable errors when Samba is transferring large files:

eth0: Transmit timed out, status 0000, PHY status 786d, resetting...

What kernel? (my crystal ball is in repair)

Roger

#2 lore raw
Quoted 9 lines · Roger Luethi
Quoted 4 lines · Peter Schaefer

I'm getting reproducable errors when Samba is transferring large files:

eth0: Transmit timed out, status 0000, PHY status 786d, resetting...

What kernel? (my crystal ball is in repair)

Oops. I'm sorry, i thought the version number of the driver might be enough...

The box is currently running 2.6.7 vanilla. I've installed it starting with 2.6.1 (as 2.4.x doesn't support the hardware proberly) and the problem has existed ever since.

Best regards,

Peter

#6 lore raw
In reply to Roger Luethi
Quoted 7 lines
Quoted 2 lines · Peter Schaefer

On 09.08.2004 23:54, Roger Luethi wrote:
What kernel? (my crystal ball is in repair)

Oops. I'm sorry, i thought the version number of the driver might be enough...

Argh! I didn't copy that part into my first mail:

via-rhine.c:v1.10-LK1.1.20-2.6 May-23-2004 Written by Donald Becker
eth0: VIA VT6102 Rhine-II at 0xe8187000, 00:04:61:fe:fe:fe, IRQ 12.
eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 40a1.

Sorry, again.

Best regards,

Peter

#3 lore raw
In reply to Peter Schaefer
Quoted 3 lines · Peter Schaefer

The box is currently running 2.6.7 vanilla. I've installed it starting with 2.6.1 (as 2.4.x doesn't support the hardware proberly) and the problem has existed ever since.

Try 2.6.8-rc3 or later. Let me know if it works (if it doesn't, I'm not sure I want to know :-/).

Roger

#4 lore raw
Quoted 9 lines · Roger Luethi
Quoted 3 lines · Peter Schaefer

The box is currently running 2.6.7 vanilla. I've installed it starting with 2.6.1 (as 2.4.x doesn't support the hardware proberly) and the problem has existed ever since.

Try 2.6.8-rc3 or later. Let me know if it works (if it doesn't, I'm not sure I want to know :-/).

As this is a production machine i haven't had the balls to move to 2.6.8-rc3. Instead, i took only the via-rhine.c from 2.6.8-rc4-mm1 applied your last patch to it and recompiled the module.

What should i say: It works! I wasn't able to trigger the error with my standard test (copying a 680MB ISO image from/to Samba shares in parallel). An this even with "large readwrite" enabled in smb.conf.

So, i consider this gone - for now :)

(But perhaps you should update the drivers version number)

Thank you very much!

Best regards,

Peter

#5 lore raw
Quoted 3 lines · Peter Schaefer

As this is a production machine i haven't had the balls to move to 2.6.8-rc3. Instead, i took only the via-rhine.c from 2.6.8-rc4-mm1 applied your last patch to it and recompiled the module.

Odd. AFAIK 2.6.8-rc4-mm1 has all the patches merged. My most recent patch was for mainline only.

Quoted 3 lines

What should i say: It works! I wasn't able to trigger the error with my standard test (copying a 680MB ISO image from/to Samba shares in parallel). An this even with "large readwrite" enabled in smb.conf.

Cool. Thanks for the report.

Quoted 1 line

(But perhaps you should update the drivers version number)

2.6.7 had 1.1.20-2.6. The driver in 2.6.8-rc4-mm1 is 1.2.0-2.6. The driver in 2.6.8 (mainline) is patch-wise somewhere in between but still called 1.1.20-2.6. Ah well.

Roger