Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755057AbYGIWPZ (ORCPT ); Wed, 9 Jul 2008 18:15:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751489AbYGIWPN (ORCPT ); Wed, 9 Jul 2008 18:15:13 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:48597 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751076AbYGIWPL (ORCPT ); Wed, 9 Jul 2008 18:15:11 -0400 From: "Rafael J. Wysocki" To: Stephen Rothwell Subject: Re: linux-next: Tree for July 9 Date: Thu, 10 Jul 2008 00:17:03 +0200 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) Cc: linux-next@vger.kernel.org, LKML , Ingo Molnar References: <20080709183047.0eb1eb72.sfr@canb.auug.org.au> In-Reply-To: <20080709183047.0eb1eb72.sfr@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807100017.04397.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1669 Lines: 49 On Wednesday, 9 of July 2008, Stephen Rothwell wrote: > Hi all, > > Changes since next-20080708: > > Temporarily dropped tree: ttydev (since it would not import on top of any > tree I have) > > The x86 tree lost a conflict against the ftrace tree. > > The ide tree gained 2 conflicts against Linus' tree. > > The nfs tree gained a conflict against Linus' tree. > > The acpi tree lost 5 conflicts against various trees but gained another > against the x86 tree. > > The net tree lost 2 conflicts against the x86 wireless-current trees. > > I have also applied the following patches for known problems (I assume > that these will be merged into their appropriate trees shortly): > > linux-next: zero based percpu build error on s390 > sparc64: sysdev API change fallout > > I no longer needed to revert the commits from the mmc tree. > ---------------------------------------------------------------------------- With this tree (and several previous ones, it appears) my quad core test box's CPU is detected as one core. With 2.6.26-rc9 four cores are detected as appropriate. dmesg from the failing kernel (today's linux-next) is at: http://www.sisk.pl/kernel/debug/20080709/dmesg-20080709.log dmesg from a non-failing kernel (2.6.26-rc9) is at: http://www.sisk.pl/kernel/debug/20080709/dmesg-rc9.log .config is at: http://www.sisk.pl/kernel/debug/20080709/next-config I'll bisect tomorrow. 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/