Re: e1000 issue on DQ965GF board (was 24 lost ticks with 2.6.20.10 kernel)

2007-05-04 Thread Michel Lespinasse
On Fri, May 04, 2007 at 11:25:43AM -0700, Kok, Auke wrote: > can you try turning off the "management enable" function in the BIOS of the > DQ965GF? That fixes this issue for us in our labs. A fix for this is also > available in our standalone 7.5.5.1 driver (obtainable from e1000.sf.net), > but

Re: e1000 issue on DQ965GF board (was 24 lost ticks with 2.6.20.10 kernel)

2007-05-04 Thread Kok, Auke
Michel Lespinasse wrote: On Wed, May 02, 2007 at 11:14:52AM -0700, Kok, Auke wrote: 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

RE: e1000 issue on DQ965GF board (was 24 lost ticks with 2.6.20.10 kernel)

2007-05-03 Thread Allan, Bruce W
se Cc: Kok, Auke-jan H; Chuck Ebbert; linux-kernel@vger.kernel.org; Dave Jones; cramerj; Ronciak, John; Brandeburg, Jesse; Kirsher, Jeffrey T; Allan, Bruce W Subject: Re: e1000 issue on DQ965GF board (was 24 lost ticks with 2.6.20.10 kernel) [Adding Bruce to the Cc, reply below] Michel Lespinasse

Re: e1000 issue on DQ965GF board (was 24 lost ticks with 2.6.20.10 kernel)

2007-05-03 Thread Kok, Auke
[Adding Bruce to the Cc, reply below] Michel Lespinasse wrote: On Wed, May 02, 2007 at 11:14:52AM -0700, Kok, Auke wrote: 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.or

e1000 issue on DQ965GF board (was 24 lost ticks with 2.6.20.10 kernel)

2007-05-02 Thread Michel Lespinasse
On Wed, May 02, 2007 at 11:14:52AM -0700, Kok, Auke wrote: > 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 Go

Re: 24 lost ticks with 2.6.20.10 kernel

2007-05-02 Thread Kok, Auke
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 th

Re: 24 lost ticks with 2.6.20.10 kernel

2007-05-02 Thread Kok, Auke
Michel Lespinasse wrote: On my system, every e1000_watchdog() invocation calls e1000_read_phy_reg() twice: first near the top of e1000_check_for_link() within the e1000_media_type_copper && hw->get_link_status condition, then within e1000_update_stats() to read and update the idle_errors statisti

Re: 24 lost ticks with 2.6.20.10 kernel

2007-05-02 Thread Andi Kleen
Michel Lespinasse <[EMAIL PROTECTED]> writes: > > running with report_lost_ticks, I see the following: > > May 1 12:58:57 server kernel: time.c: Lost 24 timer tick(s)! rip > _spin_unlock_irqrestore+0x8/0x9) > May 1 12:58:59 server kernel: time.c: Lost 24 timer tick(s)! rip > _spin_unlock_irqr

Re: 24 lost ticks with 2.6.20.10 kernel

2007-05-02 Thread Michel Lespinasse
On Tue, May 01, 2007 at 03:08:48PM -0700, Kok, Auke wrote: > Michel Lespinasse wrote: > >(I've added the E1000 maintainers to the thread as I found the issue > >seems to go away after I compile out that driver. For reference, I was > >trying to figure out why I lose exactly 24 ticks about every two

Re: 24 lost ticks with 2.6.20.10 kernel

2007-05-01 Thread Lee Revell
On 5/1/07, Kok, Auke <[EMAIL PROTECTED]> wrote: Michel Lespinasse wrote: > (I've added the E1000 maintainers to the thread as I found the issue > seems to go away after I compile out that driver. For reference, I was > trying to figure out why I lose exactly 24 ticks about every two > seconds, as

Re: 24 lost ticks with 2.6.20.10 kernel

2007-05-01 Thread Kok, Auke
Chuck Ebbert wrote: Kok, Auke wrote: Michel Lespinasse wrote: (I've added the E1000 maintainers to the thread as I found the issue seems to go away after I compile out that driver. For reference, I was trying to figure out why I lose exactly 24 ticks about every two seconds, as shown with repor

Re: 24 lost ticks with 2.6.20.10 kernel

2007-05-01 Thread Chuck Ebbert
Kok, Auke wrote: > Michel Lespinasse wrote: >> (I've added the E1000 maintainers to the thread as I found the issue >> seems to go away after I compile out that driver. For reference, I was >> trying to figure out why I lose exactly 24 ticks about every two >> seconds, as shown with report_lost_tic

Re: 24 lost ticks with 2.6.20.10 kernel

2007-05-01 Thread Kok, Auke
Michel Lespinasse wrote: (I've added the E1000 maintainers to the thread as I found the issue seems to go away after I compile out that driver. For reference, I was trying to figure out why I lose exactly 24 ticks about every two seconds, as shown with report_lost_ticks. This is with a DQ965GF mo

Re: 24 lost ticks with 2.6.20.10 kernel

2007-05-01 Thread Michel Lespinasse
(I've added the E1000 maintainers to the thread as I found the issue seems to go away after I compile out that driver. For reference, I was trying to figure out why I lose exactly 24 ticks about every two seconds, as shown with report_lost_ticks. This is with a DQ965GF motherboard with onboard E100

Re: 24 lost ticks with 2.6.20.10 kernel

2007-05-01 Thread Chuck Ebbert
Michel Lespinasse wrote: > > I'm having an issue with lost ticks, runnign linux 2.6.20.10 on an > intel DQ965GF motherboard. For some reason this occurs with clock-like > regularity, always exactly 24 lost ticks, about every two seconds. > This is running with 250-HZ ticks, and the small pause eve

24 lost ticks with 2.6.20.10 kernel

2007-05-01 Thread Michel Lespinasse
Hi, Sorry if this is known, I am not on the list. I'm having an issue with lost ticks, runnign linux 2.6.20.10 on an intel DQ965GF motherboard. For some reason this occurs with clock-like regularity, always exactly 24 lost ticks, about every two seconds. This is running with 250-HZ ticks, and the