public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean-Christian de Rivaz <jc@eclis.ch>
To: john stultz <johnstul@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, dean@arctic.org, zippel@linux-m68k.org
Subject: Re: NTP broken with 2.6.14
Date: Thu, 03 Nov 2005 23:10:35 +0100	[thread overview]
Message-ID: <436A8ADB.2090307@eclis.ch> (raw)
In-Reply-To: <1131054087.27168.595.camel@cog.beaverton.ibm.com>

john stultz a écrit :
> On Thu, 2005-11-03 at 22:12 +0100, Jean-Christian de Rivaz wrote:
> 
>>A have tested 7 differents vanilla kernel on the same suspect hardware:
>>
>>                2.6.8  : ntpd working : drift from    -77ppm to   -144ppm
>>                2.6.9  : ntpd working : drift from    -99ppm to   -231ppm
>>                2.6.10 : ntpd failed  : drift from -37825ppm to -29912ppm
>>                2.6.12 : ntpd failed  : drift from -43429ppm to -45251ppm
> 
> 
> Ok, that makes it pretty clear we have a regression w/ 2.6.10. I really
> appreciate your helping narrow down this issue. If you have the time,
> could you test the three 2.6.10-rcX patches? 
> 
> You can find them here: 
> ftp://ftp.kernel.org/pub/linux/kernel/v2.6/testing/
> 
> And they apply independently (not cumulatively) ontop of 2.6.9

I will try, but compiling the kernels take time even with 3 machines 
(one per kernel version)...


I compared the dmesg log of the different kernel, but since I don't know 
what I should find it's a little difficult. There is many differences 
between each kernels. Despit that, I noticed this difference between the 
kernel 2.6.9 (ntps working) and the kernel 2.6.10 (ntpd failed):

--- linux-2.6.9.txt  2005-11-03 22:49:29.000000000 +0100
+++ linux-2.6.10.txt  2005-11-03 22:48:41.000000000 +0100
[...snip...]
@@ -67,16 +68,12 @@
   Enabling unmasked SIMD FPU exception support... done.
   Checking 'hlt' instruction... OK.
   ENABLING IO-APIC IRQs
- vector=0x31 pin1=2 pin2=-1
- 8254 timer not connected to IO-APIC
- ...trying to set up timer (IRQ0) through the 8259A ...  failed.
- ...trying to set up timer as Virtual Wire IRQ... failed.
- ...trying to set up timer as ExtINT IRQ... works.
+ vector=0x31 pin1=0 pin2=-1
   Registered protocol family 16
   PCI BIOS revision 2.10 entry at 0xfbbb0, last bus=3
   Using configuration type 1
[..snip...]

Maybe a way to go ?

-- 
Jean-Christian de Rivaz

  reply	other threads:[~2005-11-03 22:10 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-02 23:05 NTP broken with 2.6.14 Jean-Christian de Rivaz
2005-11-02 23:21 ` john stultz
2005-11-02 23:37   ` Jean-Christian de Rivaz
2005-11-03  0:15     ` john stultz
2005-11-03  0:45       ` Jean-Christian de Rivaz
2005-11-03  1:07         ` john stultz
2005-11-03  2:26           ` Jean-Christian de Rivaz
2005-11-03 19:32             ` john stultz
2005-11-03 19:51               ` Lennart Sorensen
2005-11-03 20:11                 ` john stultz
2005-11-03 20:48                   ` Lennart Sorensen
2005-11-03 21:00                     ` john stultz
2005-11-03 21:12                       ` Lennart Sorensen
2005-11-03 21:28                   ` Jean-Christian de Rivaz
2005-11-03 21:12               ` Jean-Christian de Rivaz
2005-11-03 21:41                 ` john stultz
2005-11-03 22:10                   ` Jean-Christian de Rivaz [this message]
2005-11-03 22:54                     ` john stultz
2005-11-04  0:15                       ` Jean-Christian de Rivaz
2005-11-04  0:40                         ` john stultz
2005-11-04  2:50                           ` Jean-Christian de Rivaz
2005-11-06 22:49                             ` Hans-Peter Jansen
2005-11-07 21:44                               ` Jean-Christian de Rivaz
2005-11-04 12:40                       ` Maciej W. Rozycki
2005-11-02 23:24 ` john stultz
2005-11-03  0:36 ` Roman Zippel
2005-11-03  1:13   ` Jean-Christian de Rivaz
2005-11-03  9:42     ` Roman Zippel
  -- strict thread matches above, loose matches on Subject: below --
2005-11-04  3:44 Brown, Len
2005-11-04  4:07 ` john stultz
2005-11-04 13:51   ` Lennart Sorensen
2005-11-04 16:39   ` Jean-Christian de Rivaz
2005-11-04 17:41     ` Jean-Christian de Rivaz

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=436A8ADB.2090307@eclis.ch \
    --to=jc@eclis.ch \
    --cc=dean@arctic.org \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.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