Re: NTP broken with 2.6.14

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

I have tested the 2.6.10-rc* kernels too. Here is the full list:

2.6.8      : ntpd working : low drift
2.6.9      : ntpd working : low drift
2.6.10-rc1 : ntpd working : low drift
2.6.10-rc2 : ntpd working : low drift
2.6.10-rc3 : ntpd failed  : high drift
2.6.10     : ntpd failed  : high drift
2.6.12     : ntpd failed  : high drift
2.6.14     : ntpd failed  : high drift

The picture is very clear: the problem start from the 2.6.10-rc3 kernel. 
All the kernel that make ntpd failed can be fixed by the "noapic" option 
to make ntpd working.

Log of kernels 2.6.8 to 2.6.10-rc2 say this:

kernel: ENABLING IO-APIC IRQs
kernel: ..TIMER: vector=0x31 pin1=2 pin2=-1
kernel: ..MP-BIOS bug: 8254 timer not connected to IO-APIC
kernel: ...trying to set up timer (IRQ0) through the 8259A ...  failed.
kernel: ...trying to set up timer as Virtual Wire IRQ... failed.
kernel: ...trying to set up timer as ExtINT IRQ... works.

Log of kernel 2.6.10-rc3 to 2.6.14 say this:

kernel: ENABLING IO-APIC IRQs
kernel: ..TIMER: vector=0x31 pin1=0 pin2=-1

I don't understand if the problem is the pin1 that change from 2 to 0 or 
if this is because the code to solve the "MP-BIOS bug" is not executed 
(maybe because it is not in the kernel anymore, I have not verified).

> > More fun now: it look like the BIOS actually used on this mainboard is 
> > not designed for it, but for an other board!!!
> >
> > The board is exactly this one "K7N2 Delta-L":
> > http://www.msi.com.tw/program/support/download/dld/spt_dld_detail.php?UID=436&kind=1
> > And according to MSI it must use a BIOS version 5.9. But when I enter 
> > into the BIOS setup the version info say "W6570MS V7.4 081203".
> >
> > Here is the BIOS version history: 
> > http://www.msi.com.tw/program/support/bios/bos/spt_bos_detail.php?UID=436&kind=1
> > The version 7.4 dated 2003-8-12 has a special note:
> >
> > 1. Only for K7N2 Delta-ILSR
> > 2. This BIOS cannot be used on K7N2 Delta-L
> >
> > Crasy. I use this board without any issue since around two years and 
> > only found the first problem when upgrading to the kernel 2.6.14!
>
>
> Heh. Yea, I'm amazed you were able to flash it and still have the system
> boot. I'd suggest making sure you have the proper and current BIOS, as
> its *very* difficult for folks to help debug problems on unofficial or
> unsupported hardware/firmware configs.
>
> I believe ioapic support should function correctly regardless (or be
> blacklisted and with others reporting problems, its might not be just
> this BIOS issue), so after you get your BIOS sorted out, please let me
> know if the problem still persists.

After trying several time, I am unable to upgrade the BIOS of this 
machine. The flash utility hang all the system at the very beginning of 
the real access to programm the flash! This is maybe because I use a 
freedos image over pxelinux. I will try with a floppy and a MSDOS if I 
found such olds stuffs somehere.

Thanks a lot for the support,
--
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/