linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Adrian C." <drupix@gmail.com>
To: gerardo juarez-mondragon <gjuarezmondragon@metacrawler.com>
Cc: linux-admin@vger.kernel.org
Subject: Re: Unknown log entries
Date: Thu, 18 Aug 2005 11:02:59 +0300	[thread overview]
Message-ID: <60a7468905081801027f894dad@mail.gmail.com> (raw)
In-Reply-To: <135E2CB4B8F27CB4987C5C4EB14650A1@gjuarezmondragon.metacrawler.com>

Despite all the strange kernel warnings this card generates i'm
running tens of routers with these being the primary interfaces and no
problems whatsoever occured. What revision is it? C C+ D ? linux 2.4
or 2.6?

On 8/16/05, gerardo juarez-mondragon <gjuarezmondragon@metacrawler.com> wrote:
> 
> Hi,
> 
> I have recently been finding these messages in
> the log of my server, which is named 'marvin':
> 
> Aug 16 13:59:07 marvin kernel: eth1: Transmit
>  timeout, status 0d 0000 media 18.
> Aug 16 13:59:07 marvin kernel: eth1: Tx queue
> start entry 273147  dirty entry 273143.
> 
> Sometimes they occur repeatedly (every few
> seconds) and sometimes they are spaced in time
> (minutes or hours), so they seem to happen randomly.
> 
> Does any of you have some idea what this type of
> message means? (hardware, driver, other problem)?
> 
> Oh! by the way, eth1 is an rtl8139 card.
> 
> Thanks,
> Gerardo
> 
> 
> Searching for the best free email?  Try MetaCrawler Mail, from the #1 metasearch service on the Web, http://www.metacrawler.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

      reply	other threads:[~2005-08-18  8:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16 19:02 Unknown log entries gerardo juarez-mondragon
2005-08-18  8:02 ` Adrian C. [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=60a7468905081801027f894dad@mail.gmail.com \
    --to=drupix@gmail.com \
    --cc=gjuarezmondragon@metacrawler.com \
    --cc=linux-admin@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;
as well as URLs for NNTP newsgroup(s).