lkml.org 
[lkml]   [2004]   [Jul]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: 8139too in 2.6.x tx timeout
From
Date
Zinx Verituse <zinx@epicsol.org> writes:

> Up with some other files:
> http://zinx.xmms.org/misc/tmp/8139too/
> linux-2.6.7-mobius-dotconfig (.config being used for the kernel)

Probably this isn't fix the problem, but can you try the following?

CONFIG_8139TOO_PIO=n
CONFIG_8139TOO_TUNE_TWISTER=n

(both config to "n")

> On the ping -c1: several pings made it, then it didn't reply for one,
> but also reported no timeout in the messages. Another ping caused it
> to not reply _and_ to timeout/reset.

This may not be the problem of 8139too driver, because 2.4.24's
driver didn't fix.

Umm.. possible of cable or hub problem, but 2.4.24 is work...
Do you know lastest worked version?

> By the way, I downloaded the specs for the 8139C and noticed immediately
> it claims writing to the ISR has no effect and that reading it clears it.
> The drivers appear to indicate this documentation is entirely wrong --
> Is there any real documentation for this chipset?

Indeed. I think you are reading the same document with me. Docs says it,
however, the interrupt status wasn't cleared by read.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:04    [W:0.053 / U:0.840 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site