Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756687Ab0KSUXB (ORCPT ); Fri, 19 Nov 2010 15:23:01 -0500 Received: from ogre.sisk.pl ([217.79.144.158]:38063 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754797Ab0KSUW7 (ORCPT ); Fri, 19 Nov 2010 15:22:59 -0500 From: "Rafael J. Wysocki" To: Chris Vine Subject: Re: [Bug #20172] 2.6.36-rc7 boot stalls unless nolapic_timer - Lenovo S12 Date: Fri, 19 Nov 2010 21:22:05 +0100 User-Agent: KMail/1.13.5 (Linux/2.6.37-rc2-rjw+; KDE/4.4.4; x86_64; ; ) Cc: Linux Kernel Mailing List , Kernel Testers List , Maciej Rutecki , Florian Mickler References: <20101119150632.23e4b4af@boulder.homenet> In-Reply-To: <20101119150632.23e4b4af@boulder.homenet> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201011192122.05570.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1871 Lines: 41 On Friday, November 19, 2010, Chris Vine wrote: > On Fri, 19 Nov 2010 00:53:35 +0100 (CET) > "Rafael J. Wysocki" wrote: > > This message has been generated automatically as a part of a report > > of regressions introduced between 2.6.35 and 2.6.36. > > > > The following bug entry is on the current list of known regressions > > introduced between 2.6.35 and 2.6.36. Please verify if it still > > should be listed and let the tracking team know (either way). > > > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=20172 > > Subject : 2.6.36-rc7 boot stalls unless nolapic_timer > > - Lenovo S12 Submitter : Chris Vine > > Date : 2010-10-10 12:59 > > (40 days old) Message-ID : > > <<20101010135912.76eb61b7@boulder.homenet>> References : > > http://marc.info/?l=linux-kernel&m=128671620721712&w=2 > > This bug is still present in 2.6.37-rc2, but (as the original reporter) > I now doubt it should be classified as a regression. It looked as if > it was a regression because in the 2.6.35 kernel (the first kernel to > include intel idle), intel idle was available as a kernel module and > that module never in fact loaded on my hardware and so never caused a > hang. In 2.6.36 onwards, intel idle is only available directly compiled > into the kernel and that is when the hang became apparent: subsequent > testing shows that the hang also occurs with 2.6.35 if intel idle is > compiled in rather than as a module. > > So it is a bug, which is still present, but not necessarily a > regression. OK, dropped from the list of recent regressions. Thanks, Rafael -- 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/