- Original Message -
From: "JaniD++" <[EMAIL PROTECTED]>
To: "BRM" <[EMAIL PROTECTED]>
Cc:
Sent: Friday, March 31, 2006 9:33 AM
Subject: Re: e1000 - packet lost bug in 6.3.9 (old version :NETDEV WATCHDOG:
eth0: transmit timed out)
>
>
- Original Message -
From: "Boris B. Zhmurov" <[EMAIL PROTECTED]>
To: "Herbert Xu" <[EMAIL PROTECTED]>
Cc: "David S. Miller" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED
- Original Message -
From: "Herbert Xu" <[EMAIL PROTECTED]>
To: "David S. Miller" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECT
- Original Message -
From: "BRM" <[EMAIL PROTECTED]>
To: "JaniD++" <[EMAIL PROTECTED]>
Sent: Friday, March 31, 2006 12:05 AM
Subject: Re: e1000 - packet lost bug in 6.3.9 (old version :NETDEV WATCHDOG:
eth0: transmit timed out)
> I saw your mes
Hello, list,
I have one big raid array from 4 nbd device.
If i use the 2.6.15.7 i get this message sometimes:
NETDEV WATCHDOG: eth0: transmit timed out
e1000: eth0: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex
After this message (and some minute) usually the packet is retried, and
Hello,
>Motherboard?
Intel SE7520AF2 (Dual Xeon)
>Are you all using iptables?
YES
>Are you all routing?
NO
>From the reports I assume none of you are using an 82571/2/3 (pci express)?
08:04.0 Ethernet controller: Intel Corp.: Unknown device 1079 (rev 03)
Subsystem: Intel Corp.: Unk
Hello, list,
I have this issue too sometimes (~daily), and i can help to find this one if
somebody send me a debug patch! ;-)
Cheers,
Janos
- Original Message -
From: "Jesse Brandeburg" <[EMAIL PROTECTED]>
To: "Arnaldo Carvalho de Melo" <[EMAIL PROTECTED]>
Cc: "Phil Oester" <[EMAIL PROT
- Original Message -
From: "Prosenjit Kundu" <[EMAIL PROTECTED]>
To: "JaniD++" <[EMAIL PROTECTED]>
Cc:
Sent: Wednesday, March 01, 2006 12:18 PM
Subject: Re: netconsole problem
> Can you connect a serial cable and send the dump?
Yes, the serial cable
Hello, list,
BUG #1
I found this on my node #1 (st-0001) dmesg:
nfs: server 192.168.0.1 OK
nfs: server 192.168.0.1 OK
Dead loop on netdevice eth0, fix it urgently!
Dead loop on netdevice eth0, fix it urgently!
Dead loop on netdevice eth0, fix it urgently!
Dead loop on netdevice eth0, fix it urgen
Hi,
Thanks, the patch fix the problem for me. :-)
Today is the first time, i will try the jumbo network.
I am very concerned to the result...
The new 6.3.9 driver looks like better! :-)
Cheers,
Janos
- Original Message -
From: "Jesse Brandeburg" <[EMAIL PROTECTED
Hello,
- Original Message -
From: "Stephen Hemminger" <[EMAIL PROTECTED]>
To: "JaniD++" <[EMAIL PROTECTED]>
Cc:
Sent: Thursday, January 12, 2006 10:40 PM
Subject: Re: Marvell driver question
> On Thu, 12 Jan 2006 21:15:21 +0100
> "JaniD++&qu
Hello,
>
> I would suggest trying the latest released driver 6.2.15. It
> performance enhancements added, which should help.
>
> http://sourceforge.net/projects/e1000
Finally i can build and insert the new module. :-)
But the performance problem is still here.
This is the /sys/block/nbd#/stat f
- Original Message -
From: "Benjamin LaHaise" <[EMAIL PROTECTED]>
To: "JaniD++" <[EMAIL PROTECTED]>
Cc:
Sent: Friday, December 02, 2005 10:26 PM
Subject: Re: e1000 performance question.
> On Fri, Dec 02, 2005 at 09:23:33PM +0100, JaniD++ wrote:
>
Hi,
> > OK, i will try it, if i can (this is a productive online system,
maybe
> > next reboot)
>
> I'd rather suggest to _not_ run -rc kernels on productive systems. :)
Thanks for the warning! :-)
I know it, already.
But have no choice. :(
The older kernels didnt know what i have needed! :-
14 matches
Mail list logo
