From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Zinx Verituse <zinx@epicsol.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 8139too in 2.6.x tx timeout
Date: Mon, 05 Jul 2004 13:30:22 +0900 [thread overview]
Message-ID: <873c4713fl.fsf@ibmpc.myhome.or.jp> (raw)
In-Reply-To: <20040704194009.GA2029@bliss>
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>
next prev parent reply other threads:[~2004-07-05 4:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-26 22:23 Zinx Verituse
2004-07-04 11:07 ` OGAWA Hirofumi
2004-07-04 11:16 ` bert hubert
2004-07-04 13:26 ` OGAWA Hirofumi
2004-07-04 19:40 ` Zinx Verituse
2004-07-05 4:30 ` OGAWA Hirofumi [this message]
2004-07-06 5:33 ` Zinx Verituse
2004-07-06 6:47 ` Zinx Verituse
2004-07-06 15:29 ` OGAWA Hirofumi
2004-07-06 17:25 ` Zinx Verituse
2004-07-06 20:47 Nick Warne
2004-07-07 19:22 ` OGAWA Hirofumi
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=873c4713fl.fsf@ibmpc.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=zinx@epicsol.org \
/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®