Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750732AbWJPOco (ORCPT ); Mon, 16 Oct 2006 10:32:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750742AbWJPOcn (ORCPT ); Mon, 16 Oct 2006 10:32:43 -0400 Received: from rutherford.zen.co.uk ([212.23.3.142]:15829 "EHLO rutherford.zen.co.uk") by vger.kernel.org with ESMTP id S1750732AbWJPOcm (ORCPT ); Mon, 16 Oct 2006 10:32:42 -0400 From: David Johnson To: Jarek Poplawski Subject: Re: Hardware bug or kernel bug? Date: Mon, 16 Oct 2006 15:32:38 +0100 User-Agent: KMail/1.9.5 References: <20061013085605.GA1690@ff.dom.local> <200610131724.40631.dj@david-web.co.uk> <20061016102500.GA1709@ff.dom.local> In-Reply-To: <20061016102500.GA1709@ff.dom.local> MIME-Version: 1.0 Content-Disposition: inline Cc: Linux Kernel , netdev@vger.kernel.org Reply-To: dj@david-web.co.uk Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200610161532.38663.dj@david-web.co.uk> X-Originating-Rutherford-IP: [82.69.29.67] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1392 Lines: 36 On Monday 16 October 2006 11:25, Jarek Poplawski wrote: > > Was this lock-up effect visible during above 2.6.19-rc1 tests? No, I've not seen anything in Linux other than the reboots, which are instant without any preceding lock-up. > If not I'd try to continue linux debbuging: > - is 2.6.19-rc1 working with "normal" config (use make oldconfig > to "upgrade" .config), With 2.6.19-rc1 and a normal config, I get the reboots as usual. > - is 2.6.17 working with "minimal" config (use make oldconfig), Yes. > - changing one or two options at a time try to find which one makes > the effect returns (acpi, smp...). I've found the culprit - CPU Frequency Scaling. With it enabled I get the reboots, with it disabled I don't. That's the same with every kernel version I've tried (2.6.19-rc1+rc2, 2.6.17.13 & Centos' 2.6.9) The system was using the p4-clockmod driver and the ondemand governor. I'm still not sure exactly what the problem is - the reboots only happen in the circumstances I've mentioned and are not triggered by changes in clock speed alone - but disabling cpufreq seems to make it go away... Thanks for your help, David. - 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/