Re: 24 lost ticks with 2.6.20.10 kernel

["Kok, Auke" <auke-jan.h.kok@intel.com>]

Michel Lespinasse wrote:
> > I've had good results with 2.6.21.1 (even running tickless :)) on these 
> > NICs. Have you tried that yet?
>
> Not yet. Coming up... I'd prefer not to rely on new kernels at this
> point though - but I can certainly try it just to report on current status.

I just checked and the fix I was referring to earlier didn't make it into 
2.6.21-final. You can get 2.6.21-git1 from kernel.org which has the fix. See

http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.21-git1.log

for the changelog and commit id's for the patch:

commit c58b8e4a25a1ba347a0e5d21984c97bd296f1691
Merge: afc2e82... f50393f...
Author: Linus Torvalds <torvalds@woody.linux-foundation.org>
Date:   Fri Apr 27 10:14:53 2007 -0700

    Merge branch 'e1000-fixes' of 
master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6

    * 'e1000-fixes' of 
master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6:
      e1000: FIX: Stop raw interrupts disabled nag from RT
      e1000: FIX: firmware handover bits
      e1000: FIX: be ready for incoming irq at pci_request_irq

Please give this a try and see if it resolves your issues.

hth,

Auke
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/