From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: bert hubert <ahu@ds9a.nl>
Cc: Zinx Verituse <zinx@epicsol.org>, linux-kernel@vger.kernel.org
Subject: Re: 8139too in 2.6.x tx timeout
Date: Sun, 04 Jul 2004 22:26:34 +0900 [thread overview]
Message-ID: <87llhzlx85.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <20040704111623.GA12255@outpost.ds9a.nl>
bert hubert <ahu@ds9a.nl> writes:
> On Sun, Jul 04, 2004 at 08:07:40PM +0900, OGAWA Hirofumi wrote:
>
> > NETDEV WATCHDOG: eth0: transmit timed out
> > eth0: Transmit timeout, status 0d 0000 c07f media 08.
> > eth0: Tx queue start entry 25 dirty entry 21.
> > eth0: Tx descriptor 0 is 10080062.
> > eth0: Tx descriptor 1 is 00080062. (queue head)
> > eth0: Tx descriptor 2 is 00080062.
> > eth0: Tx descriptor 3 is 00080062.
> > eth0: link up, 10Mbps, half-duplex, lpa 0x0000
> > rtl8139_hw_start: init buffer addresses
>
> I've solved this exact problem in the bios by changing interrupts from level
> to edge, or the other way around, unsure.
>
> Earlier 2.6 did not have problems with that bios setting.
Yes. 8139too.c with NAPI requires the level triggered interrrut. (PCI
spec also requires it)
However, this registers doesn't indicate the lost interrupt problem.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2004-07-04 13:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-26 22:23 8139too in 2.6.x tx timeout Zinx Verituse
2004-07-04 11:07 ` OGAWA Hirofumi
2004-07-04 11:16 ` bert hubert
2004-07-04 13:26 ` OGAWA Hirofumi [this message]
2004-07-04 19:40 ` Zinx Verituse
2004-07-05 4:30 ` OGAWA Hirofumi
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
-- strict thread matches above, loose matches on Subject: below --
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=87llhzlx85.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=ahu@ds9a.nl \
--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