From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757462AbYDGLrn (ORCPT ); Mon, 7 Apr 2008 07:47:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754131AbYDGLrc (ORCPT ); Mon, 7 Apr 2008 07:47:32 -0400 Received: from mail.ift.unesp.br ([200.145.46.3]:49185 "EHLO mail.ift.unesp.br" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753927AbYDGLrc (ORCPT ); Mon, 7 Apr 2008 07:47:32 -0400 Date: Mon, 7 Apr 2008 08:46:53 -0300 From: "Carlos R. Mafra" To: "Pallipadi, Venkatesh" Cc: Ray Lee , "Rafael J. Wysocki" , Linux Kernel Mailing List , Soeren Sonnenburg , rui.zhang@intel.com Subject: Re: 2.6.25-current-git hangs on boot unless CONFIG_CPU_IDLE=n-Apple Message-ID: <20080407114653.GA29733@localhost.ift.unesp.br> References: <924EFEDD5F540B4284297C4DC59F3DEED0EA1E@orsmsx423.amr.corp.intel.com> <20080404011053.GA21254@localhost.ift.unesp.br> <2c0942db0804032015y57e91811r37b729cd836cef6d@mail.gmail.com> <20080404114756.GA3890@localhost.ift.unesp.br> <924EFEDD5F540B4284297C4DC59F3DEED0EB77@orsmsx423.amr.corp.intel.com> <20080404155155.GA6578@localhost.ift.unesp.br> <924EFEDD5F540B4284297C4DC59F3DEED0EEC6@orsmsx423.amr.corp.intel.com> <20080406205610.GA4647@localhost.ift.unesp.br> <924EFEDD5F540B4284297C4DC59F3DEED0F279@orsmsx423.amr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <924EFEDD5F540B4284297C4DC59F3DEED0F279@orsmsx423.amr.corp.intel.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun 6.Apr'08 at 22:31:17 -0700, Pallipadi, Venkatesh wrote: > >On Fri 4.Apr'08 at 13:41:45 -0700, Pallipadi, Venkatesh wrote: > >> [...] > >> >>> >I've uploaded the picture where it hangs, it is in the very > >> >>beginning > >> >>> >of the boot process: > >> >>> > > >> >>> >http://www.ift.unesp.br/users/crmafra/dsc04673.jpg > >> >>> > >> >>> > >> >>> Can you try the latest git and see whether this still is > >a problem? > >> >> > >> >>I've just updated to latest git, but it may take some time for it > >> >>to happen again (the first 3 boots were okay). Last time > >it happened > >> >>with 2.6.25-rc7-00149-gaf8be4e (I checked now). > >> >> > >> >>Do you have reasons to believe this issue was fixed since then? > >> > > >> >Yes. I think the patch here should have fixed the problem.... > >> >Patch : http://marc.info/?l=linux-kernel&m=120674502201007&w=4 > >> > > >> > >> Hmmmm.... Looking at latest git, > >> The above patch is not yet in git. Can you please apply the > >above patch > >> and see whether do you still see the problem..... > > > >I applied Venkatesh's patch from the link above on top of > >v2.6.25-rc8-139-ge315c12, but my laptop hung at the 11th boot with the > >same state show here: > >http://www.ift.unesp.br/users/crmafra/dsc04673.jpg > > > >I waited 3'30" but the boot process never resumed, so I pressed > >the power button. > > > >Any further patches I might try? > > Carlos, > > Hmm. So, we still have some bug hidden in there.. > As this is similar to 10117, we should probably track this there. > 10093 is a different cpuidle specific bug looks like, as it happens at a > different place while switching between governors. > > Can you attach your kernel config, acpidump output and dmesg when kernel > boots ok to that bugzilla. I uploaded the kernel config and dmesg to the bugzilla a few minutes ago. I don't have a copy of the acpidump with me right now (laptop is at home, I am at the physics institute now), but if there is urgency you can look at the acpidump I've sent here http://lkml.org/lkml/2008/2/11/364 > Also, if you can please try processor.max_cstate=2 boot option and see > whether you still can reproduce the problem. If you can, then try > processor.max_cstate=1. For this boot option to work, you have to have > ACPI_PROCESSOR built into your kernel (and should not be a module). Ok, I will try them. > One more qn. Did you see this problem witj 2.6.24 as well or is this > something that you started seeing only recently? It started more or less at the same time as 2.6.25-rc1 was released. It was not there at 2.6.24. Well, at first I thought it was related to drivers/acpi/thermal.c, because the next kernel message (in a successfull boot) after the point in which it fails is ACPI: LNXTHERM:01 is registered as thermal_zone0 and there were some changes to that file a bit before -rc1 was out. For example, commits 3f655ef8 and ce44e19701. I don't know if this is recommended, but I added Zhang Rui to the Cc: list to exclude or confirm this possibility.