From: "Denys" <nuclearcat@nuclearcat.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@vger.kernel.org
Subject: Re: r8169 crash
Date: Sun, 18 Nov 2007 00:44:38 +0200 [thread overview]
Message-ID: <20071117224224.M6133@nuclearcat.com> (raw)
In-Reply-To: <20071117220759.GA2862@electric-eye.fr.zoreil.com>
Before it happens on 2.6.22, i tried to attach good cable, plug-unplug,
whatever, interface up/down - card still remains dead.
I try to plug cable to laptop with rtl8139 and pc with e100 - it is worked
when i shake bad cable(interface was going up/down as well), and good cable
also worked fine, and never crashed. On 2.6.22 i was able to reproduce it
easily, but later i can't cause it is server in internet cafe, and customers
going crazy.
On Sat, 17 Nov 2007 23:07:59 +0100, Francois Romieu wrote
> Denys <nuclearcat@nuclearcat.com> :
> [...]
> > After that i have.
> > Nov 15 22:11:37 vzone NETDEV WATCHDOG: eth1: transmit timed out
> > Nov 15 22:11:49 vzone NETDEV WATCHDOG: eth1: transmit timed out
> > Nov 15 22:12:01 vzone NETDEV WATCHDOG: eth1: transmit timed out
> > Nov 15 22:12:13 vzone NETDEV WATCHDOG: eth1: transmit timed out
> > Nov 15 22:12:25 vzone NETDEV WATCHDOG: eth1: transmit timed out
> > Nov 15 22:12:37 vzone NETDEV WATCHDOG: eth1: transmit timed out
> > Nov 15 22:12:49 vzone NETDEV WATCHDOG: eth1: transmit timed out
> > Nov 15 22:13:01 vzone NETDEV WATCHDOG: eth1: transmit timed out
>
> Is there a chance for you to verify that the network interface does
> not recover if a real cable is plugged at this point ?
>
> --
> Ueimor
--
Denys Fedoryshchenko
Technical Manager
Virtual ISP S.A.L.
next prev parent reply other threads:[~2007-11-17 22:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-17 5:39 r8169 crash Denys
2007-11-17 22:07 ` Francois Romieu
2007-11-17 22:44 ` Denys [this message]
2007-11-18 21:00 ` Francois Romieu
2007-11-18 23:31 ` Denys
2007-11-19 23:24 ` Francois Romieu
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=20071117224224.M6133@nuclearcat.com \
--to=nuclearcat@nuclearcat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.