netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Karl Meyer" <adhocrocker@gmail.com>
To: "Francois Romieu" <romieu@fr.zoreil.com>
Cc: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out"
Date: Mon, 1 Oct 2007 13:42:30 +0200	[thread overview]
Message-ID: <be1b757c0710010442w2dbf6751g259b8cb3354a929e@mail.gmail.com> (raw)
In-Reply-To: <20070912205025.GA31709@electric-eye.fr.zoreil.com>

Hi,

after reading about issues with the nics on kontron boards I did a
bios upgrade,
but this did not change anything.
However, yesterday the nic (onboard) I used died. No link at all,
after switching to
the next onboard  nic I got a NETDEV transmit timeout with that one on
kernel 2.6.22-r2.
It seems the whole thing is a hardware issue. I will try to figure out
with kontron.

Sorry :(

Karl

2007/9/12, Francois Romieu <romieu@fr.zoreil.com>:
> Karl Meyer <adhocrocker@gmail.com> :
> [...]
> > am am looking for this issue for some time now, but there where no
> > errors in 2.6.22-r2 (gentoo speak, I guess this is 2.6.22.2
> > officially), I also ran git-bisect (for more information see the older
> > messages in this thread).
>
> 2.6.22-r2 in gentoo is based on 2.6.22.1. It is way before
> 0e4851502f846b13b29b7f88f1250c980d57e944 that you reported to work.
> Thus it is not surprizing that it works.
>
> Any update regarding the patchkit that I sent on 2007/08/16 ?
>
> It would help to narrow the culprit.
>
> --
> Ueimor
>

      parent reply	other threads:[~2007-10-01 11:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <be1b757c0708130435y689b9dd8raf9ac9f9c0fcc976@mail.gmail.com>
2007-08-13 16:58 ` PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out" Francois Romieu
     [not found]   ` <be1b757c0708131027v5c57822as2d9bd3190fd19b71@mail.gmail.com>
     [not found]     ` <20070814070901.GA14693@electric-eye.fr.zoreil.com>
     [not found]       ` <be1b757c0708141425qd887581n3922702b84a21758@mail.gmail.com>
     [not found]         ` <20070814224629.GB3495@electric-eye.fr.zoreil.com>
2007-08-16 14:11           ` Francois Romieu
2007-08-16 21:03             ` Karl Meyer
2007-08-20  9:25             ` Karl Meyer
2007-08-21 10:56             ` Karl Meyer
2007-08-27 12:50               ` Jarek Poplawski
2007-09-01 19:24             ` Karl Meyer
2007-09-02 22:15               ` Michal Piotrowski
2007-09-02 22:21                 ` Karl Meyer
2007-09-12 20:50                   ` Francois Romieu
2007-09-26  9:07                     ` Karl Meyer
2007-10-01 11:42                     ` Karl Meyer [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=be1b757c0710010442w2dbf6751g259b8cb3354a929e@mail.gmail.com \
    --to=adhocrocker@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=romieu@fr.zoreil.com \
    /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).