Denys <[EMAIL PROTECTED]> :
> Maybe it is good idea to print some registers/etc in watchdog message?
>
> I will try to reproduce problem with debug enabled, maybe it will be possible
> to catch problem with more debug.
Your customers will not necessarily like it but it could be useful to
trace
Maybe it is good idea to print some registers/etc in watchdog message?
I will try to reproduce problem with debug enabled, maybe it will be possible
to catch problem with more debug.
On Sun, 18 Nov 2007 22:00:38 +0100, Francois Romieu wrote
> Denys <[EMAIL PROTECTED]> :
> >
> > Before it happe
Denys <[EMAIL PROTECTED]> :
>
> Before it happens on 2.6.22, i tried to attach good cable, plug-unplug,
> whatever, interface up/down - card still remains dead.
A few things have changed since 2.6.22 but I'll take that it is a
real bug and that 2.6.23 would not recover either. Can you fill a
PR
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
Denys <[EMAIL PROTECTED]> :
[...]
> 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:
Hi
Recently i start to use r8169 cards and faced some issues.
How to reproduce (kind of difficult, and i cannot that on my live server
anymore):
1)Badly crimped cable.
2)PCI-Express R8169 card
Kernel 2.6.23.1
05:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit
Ether
Hello,
* Francois Romieu <[EMAIL PROTECTED]> [2007-01-29 08:56]:
> Bernhard Walle <[EMAIL PROTECTED]> :
>
> > @@ -1371,10 +1371,9 @@ static inline void rtl8169_request_timer
> > return;
> >
> > init_timer(timer);
> > - timer->expires = jiffies + RTL8169_PHY_TIMEOUT
Bernhard Walle <[EMAIL PROTECTED]> :
[...]
> Doesn't compile, I think you mean this?
Yes.
> @@ -1371,10 +1371,9 @@ static inline void rtl8169_request_timer
> return;
>
> init_timer(timer);
> - timer->expires = jiffies + RTL8169_PHY_TIMEOUT;
> timer->data =
* Francois Romieu <[EMAIL PROTECTED]> [2007-01-28 20:04]:
> Bernhard Walle <[EMAIL PROTECTED]> :
> [...]
> > Simple fix is attached. Although that seems to fix the symptom and not
> > the cause, please apply it if you don't have a better solution.
>
> What about the patch below ?
>
> diff --git a
Bernhard Walle <[EMAIL PROTECTED]> :
[...]
> Simple fix is attached. Although that seems to fix the symptom and not
> the cause, please apply it if you don't have a better solution.
What about the patch below ?
diff --git a/drivers/net/r8169.c b/drivers/net/r8169.c
index 577babd..4e22af7 100644
-
Hello,
also after applying the latest patch that was posted on that mailing
list, I have still the problem described in
http://bugzilla.kernel.org/show_bug.cgi?id=5137.
So after a network hang with several
NETDEV WATCHDOG: eth0: transmit timed out
in the kernel log, I removed the drive
11 matches
Mail list logo
