Re: NTP broken with 2.6.14

[Jean-Christian de Rivaz <jc@eclis.ch>]

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
-
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/