Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161003AbVKDAku (ORCPT ); Thu, 3 Nov 2005 19:40:50 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1161002AbVKDAku (ORCPT ); Thu, 3 Nov 2005 19:40:50 -0500 Received: from e32.co.us.ibm.com ([32.97.110.150]:27084 "EHLO e32.co.us.ibm.com") by vger.kernel.org with ESMTP id S1161003AbVKDAkt (ORCPT ); Thu, 3 Nov 2005 19:40:49 -0500 Subject: Re: NTP broken with 2.6.14 From: john stultz To: Jean-Christian de Rivaz Cc: rddunlap@osdl.org, Len Brown , macro@linux-mips.org, linux-kernel@vger.kernel.org, dean@arctic.org, zippel@linux-m68k.org In-Reply-To: <436AA822.9060403@eclis.ch> References: <4369464B.6040707@eclis.ch> <1130973717.27168.504.camel@cog.beaverton.ibm.com> <43694DD1.3020908@eclis.ch> <1130976935.27168.512.camel@cog.beaverton.ibm.com> <43695D94.10901@eclis.ch> <1130980031.27168.527.camel@cog.beaverton.ibm.com> <43697550.7030400@eclis.ch> <1131046348.27168.537.camel@cog.beaverton.ibm.com> <436A7D4B.8080109@eclis.ch> <1131054087.27168.595.camel@cog.beaverton.ibm.com> <436A8ADB.2090307@eclis.ch> <1131058482.27168.612.camel@cog.beaverton.ibm.com> <436AA822.9060403@eclis.ch> Content-Type: text/plain; charset=ISO-8859-1 Date: Thu, 03 Nov 2005 16:40:45 -0800 Message-Id: <1131064846.27168.619.camel@cog.beaverton.ibm.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1989 Lines: 49 On Fri, 2005-11-04 at 01:15 +0100, Jean-Christian de Rivaz wrote: > john stultz a ?crit : > > You might check booting w/ noapic to see if that changes the behaviour > > in 2.6.10. > > Yes! With a vanilla 2.6.10, the noapic solve the problem and ntpd is happy. Great. Glad you have a workaround now. > > Jean-Christian: Since it ACPI is involved, have you verified that you're > > running the current BIOS for your system? > > 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. thanks -john - 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/