----- 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]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <netdev@vger.kernel.org>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; "Andi Kleen" <[EMAIL PROTECTED]>; "Jeff Garzik" <[EMAIL PROTECTED]> Sent: Friday, March 31, 2006 2:07 PM Subject: Re: [e1000 debug] KERNEL: assertion (!sk_forward_alloc) failed...
> Hello, Herbert Xu. > > On 31.03.2006 14:39 you said the following: > > > On Fri, Mar 31, 2006 at 02:16:38PM +0400, Boris B. Zhmurov wrote: > > > >>And xdelta tells, that e1000.ko was modified :) > > > > > > Thanks for checking again. > > > > Anyway, it didn't take long to find another bug in the same area. > > I'm afraid this driver does seem to be full of them :) > > > > It sets last_tx_tso in between computing the number of descriptors and > > calling e1000_tx_map. This is bad because e1000_tx_map gets the wrong > > value for last_tx_tso and therefore may corrupt memory for every TSO > > packet when the ring is almost full. > > > > This bug exists on UP as well as SMP. > > > > Signed-off-by: Herbert Xu <[EMAIL PROTECTED]> > > > > Please try this in conjunction with the previous patch. > > > > Cheers, > > > David, Herbert - FYI. One of my colleague confirmed, that idea "bug > reproducible only if there is more then one e1000 adapter onboard" is > true. He has a 3 servers with double intel pro 1000 adapters, and that > bug occurs. Also, he has 4 servers with double intel pro 1000 adapters > onboard, but _only one_ of them is up. And there is no such messages in > dmesg at all! Inetresting... This is not an unique thing! Only _one_ of my 2 equal NIC get this message NETDEV WATCHDOG: eth0: transmit timed out e1000: eth0: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex with the old 2.6.15.* e1000 driver! Not the all e1000 chips ar really equal with the same P/N Number! This can be hardware based problem, and needs workaround? Cheers, > > -- > Boris B. Zhmurov > mailto: [EMAIL PROTECTED] > "wget http://kernelpanic.ru/bb_public_key.pgp -O - | gpg --import" > > _____________ 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
