----- Original Message ----- From: "JaniD++" <[EMAIL PROTECTED]> To: "BRM" <[EMAIL PROTECTED]> Cc: <netdev@vger.kernel.org> 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: "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 message below and was wondering if the > > symptoms I posted about in the linked message below > > (though for a different card) could be for the same > > reason: > > > > http://www.spinics.net/lists/netdev/msg02074.html > > Thanks for the answer! > > I read this, but i think this is different. > > Previously i have report the watchdog-issue bug on 2.6.13 (or 14), and get > this answer: > "this is a software and hardware error both a little." > > Now i test the new driver, and found some packet lost, but the known error > message is missing! > ... > At this time i need to test more, because i found another problem on my lan, > and i think the original issue easy can be the performance difference > between the 2 version of drivers! > > If i clean out my network, and retest it, i will repost the bug again... The cleanout is done, but i found another issue: Mar 31 13:27:18 dy-xeon-1 kernel: nfs: server 192.168.2.1 not responding, still trying Mar 31 13:27:18 dy-xeon-1 kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Mar 31 13:27:18 dy-xeon-1 kernel: Tx Queue <0> Mar 31 13:27:18 dy-xeon-1 kernel: TDH <1c> Mar 31 13:27:18 dy-xeon-1 kernel: TDT <9> Mar 31 13:27:18 dy-xeon-1 kernel: next_to_use <9> Mar 31 13:27:18 dy-xeon-1 kernel: next_to_clean <1b> Mar 31 13:27:18 dy-xeon-1 kernel: buffer_info[next_to_clean] Mar 31 13:27:18 dy-xeon-1 kernel: time_stamp <3abf4> Mar 31 13:27:18 dy-xeon-1 kernel: next_to_watch <1f> Mar 31 13:27:18 dy-xeon-1 kernel: jiffies <3acfc> Mar 31 13:27:18 dy-xeon-1 kernel: next_to_watch.status <0> Mar 31 13:27:18 dy-xeon-1 kernel: nfs: server 192.168.2.1 not responding, still trying After this, the server is unreachable, and need to reset. (only ping reply in eth1) The other machines on the lan, accounts some dropped package. (During the network structure cleanout, i have installed an extra e100 [not e1000] card to this machine, and it work as eth2.) The driver is 6.3.9, kernel 2.6.15.7. Thanks, Janos > > Thanks a lot, > Janos > > > > > > > > > Thanks, > > > > Ben > > > > --- JaniD++ <[EMAIL PROTECTED]> wrote: > > > > > 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 > > > everything is back to normal. > > > > > > But with 2.6.15.7 + the e1000 driver from 2.6.16.1, > > > this message never > > > comes, but usually the NBD is disconnected instead! > > > (time out???) > > > > > > Thanks, > > > Janos > > > > > > - > > > To unsubscribe from this list: send the line > > > "unsubscribe netdev" in > > > the body of a message to [EMAIL PROTECTED] > > > More majordomo info at > > > http://vger.kernel.org/majordomo-info.html > > > > > - > To unsubscribe from this list: send the line "unsubscribe netdev" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > > _____________ NOD32 1.584 (20031220) Információ _____________ > > Az üzenetet a NOD32 Antivirus System megvizsgálta. > http://www.nod32.hu > > - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
