linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: linux-next: Tree for July 9
Date: Thu, 10 Jul 2008 00:17:03 +0200	[thread overview]
Message-ID: <200807100017.04397.rjw@sisk.pl> (raw)
In-Reply-To: <20080709183047.0eb1eb72.sfr@canb.auug.org.au>

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

  parent reply	other threads:[~2008-07-09 22:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-09  8:30 linux-next: Tree for July 9 Stephen Rothwell
2008-07-09 11:40 ` Liam Girdwood
2008-07-09 14:30 ` Heiko Carstens
2008-07-09 14:59 ` Alan Cox
2008-07-09 16:51   ` Stephen Rothwell
2008-07-09 22:17 ` Rafael J. Wysocki [this message]
2008-07-09 22:25   ` linux-next: Tree for July 9 (kmemcheck: Caught 8-bit read from freed memory (ffff880127c120e8)) Rafael J. Wysocki
     [not found]     ` <200807100025.13973.rjw-KKrjLPT3xs0@public.gmane.org>
2008-07-10  7:19       ` Vegard Nossum
2008-07-10  7:24         ` Pekka Enberg
  -- strict thread matches above, loose matches on Subject: below --
2009-07-09  6:30 linux-next: Tree for July 9 Stephen Rothwell
2010-07-09  5:01 Stephen Rothwell
2012-07-09  6:53 Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200807100017.04397.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).