From: Mark Burton <mark@helenandmark.org>
To: Mark Burton <mark@helenandmark.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tx queue start entry x dirty entry y (was 8139too PCI IRQ issues)
Date: Thu, 28 Jul 2005 14:06:08 +0200 [thread overview]
Message-ID: <b7628665a1ab5a48aa9bed28256a6dfc@helenandmark.org> (raw)
In-Reply-To: <e93921519c29efda5b7a304d019dcc94@helenandmark.org>
For reference,
Thanks to Ogawa Hirofumi,
the solution was to use noapic on the boot line, as my machine is too
old to handle APIC well.
Cheers
Mark.
On 19 Jul 2005, at 18:00, Mark Burton wrote:
> Hi,
> I'm getting similar results to Nick Warne, in that when my ethernet is
> stressed at all (for instance by NFS), I end up with
> nfs: server..... not responding, still trying
> nfs: server .... OK
>
> With a realtec card, I get errors in /var/spool/messages along the
> lines of:
> Jul 3 14:31:13 localhost kernel: eth1: Transmit timeout, status 0c
> 0005 c07f media 00.
> Jul 3 14:31:13 localhost kernel: eth1: Tx queue start entry 1160
> dirty entry 1156.
> Jul 3 14:31:13 localhost kernel: eth1: Tx descriptor 0 is 0008a03c.
> (queue head)
>
> I have no TPM (as far as I can find)
>
> Hence I dont think this is the same problem, but it's manifestation is
> identical.
>
> I was using a realtec card, using the 8139too driver, hence I first
> suspected that. As a test, I have an even older 3com509B, using that
> gives exactly the same results (though it doens't seem to be kind
> enough to output anything to /var/log/debug, so all you get are the
> "server not responding" messages under heavy NFS load.
> lsmod however, shows both modules loaded....
>
> I'm running debian, and recently got a recent kernel image
> /proc/version gives:
> Linux version 2.6.11-1-386 (dannf@firetheft) (gcc version 3.3.6
> (Debian 1:3.3.6-6)) #1 Mon Jun 20 20:53:17 MDT 2005
>
> Im not a kernel expert at all, any help sorting this problem would be
> appreciated, but Its only worth fixing if it's a general problem --
> if' I'm on my own, I'll fix it with a band-aid :-)
>
> Cheers
>
> Mark.
>
>
> -
> 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/
prev parent reply other threads:[~2005-07-28 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 16:00 Mark Burton
2005-07-23 19:11 ` OGAWA Hirofumi
2005-07-25 6:30 ` Mark Burton
2005-07-28 12:06 ` Mark Burton [this message]
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=b7628665a1ab5a48aa9bed28256a6dfc@helenandmark.org \
--to=mark@helenandmark.org \
--cc=linux-kernel@vger.kernel.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®