> 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'sdriver 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" inthe body of a message to majordomo@vger.kernel.orgMore majordomo info at http://vger.kernel.org/majordomo-info.htmlPlease read the FAQ at http://www.tux.org/lkml/