linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Michel Lespinasse <walken@zoy.org>
Cc: Chuck Ebbert <cebbert@redhat.com>,
	linux-kernel@vger.kernel.org, Dave Jones <davej@redhat.com>,
	Jeb Cramer <cramerj@intel.com>,
	John Ronciak <john.ronciak@intel.com>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Subject: Re: 24 lost ticks with 2.6.20.10 kernel
Date: Wed, 02 May 2007 11:14:52 -0700	[thread overview]
Message-ID: <4638D51C.7010603@intel.com> (raw)
In-Reply-To: <20070502084146.GA6089@zoy.org>

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

  parent reply	other threads:[~2007-05-02 18:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01 13:07 24 lost ticks with 2.6.20.10 kernel Michel Lespinasse
2007-05-01 15:34 ` Chuck Ebbert
2007-05-01 21:49   ` Michel Lespinasse
2007-05-01 22:08     ` Kok, Auke
2007-05-01 22:41       ` Chuck Ebbert
2007-05-01 22:45         ` Kok, Auke
2007-05-02  0:06       ` Lee Revell
2007-05-02  8:41       ` Michel Lespinasse
2007-05-02 16:07         ` Kok, Auke
2007-05-02 18:14         ` Kok, Auke [this message]
2007-05-03  6:27           ` e1000 issue on DQ965GF board (was 24 lost ticks with 2.6.20.10 kernel) Michel Lespinasse
2007-05-03 15:36             ` Kok, Auke
2007-05-03 15:56               ` Allan, Bruce W
2007-05-04 18:25             ` Kok, Auke
2007-05-04 21:15               ` Michel Lespinasse
2007-05-02 12:54 ` 24 lost ticks with 2.6.20.10 kernel Andi Kleen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4638D51C.7010603@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=cebbert@redhat.com \
    --cc=cramerj@intel.com \
    --cc=davej@redhat.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=john.ronciak@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=walken@zoy.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).