linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>,
	"Steven Rostedt" <srostedt@redhat.com>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	"Pekka Enberg" <penberg@cs.helsinki.fi>,
	"Christoph Lameter" <clameter@sgi.com>
Subject: Re: linux-next: Tree for June 23
Date: Mon, 23 Jun 2008 14:26:28 +0200	[thread overview]
Message-ID: <19f34abd0806230526j77fc20e7w3d92cbe67ad4c552@mail.gmail.com> (raw)
In-Reply-To: <19f34abd0806230402x502eca3cna927eb8742553570@mail.gmail.com>

On Mon, Jun 23, 2008 at 1:02 PM, Vegard Nossum <vegard.nossum@gmail.com> wrote:
> On Mon, Jun 23, 2008 at 12:26 PM, Vegard Nossum <vegard.nossum@gmail.com> wrote:
>> On Mon, Jun 23, 2008 at 12:23 PM, Vegard Nossum <vegard.nossum@gmail.com> wrote:
>>> Testing tracer sched_switch: PASSED
>>> Testing tracer sysprof: PASSED
>>> Testing tracer ftrace: PASSED
>>> Testing dynamic ftrace: PASSED
>>> Testing tracer irqsoff: PASSED
>>> Testing tracer preemptoff: PASSED
>>> Testing tracer preemptirqsoff: <4>------------[ cut here ]------------
>>> WARNING: at kernel/lockdep.c:2680 check_flags+0x142/0x160()
>>> Pid: 2, comm: kthreadd Not tainted 2.6.26-rc6-next-20080620 #34
>>
>> <-- Oops, wrong version :-(
>>
>> Will try the latest one as well.
>
> Okay, I can confirm that this happens with today's tree too. I also
> get this (new) warning:
>
> mm/slub.c: In function 'kmem_cache_defrag':
> mm/slub.c:3046: warning: 'reclaimed' may be used uninitialized in this function
>
> Otherwise things seem to work good :-)

In fact, I got this stacktrace when I shut down (but I was in a hurry
so I didn't have the time to really investigate it):

http://www.kernel.org/pub/linux/kernel/people/vegard/kernels/20080623-next/DSCF3014.JPG

$ addr2line -e vmlinux -i c01fd0c1
fs/sysfs/dir.c:380

And additionally, the next two boots hung here (but the third one was okay):

http://www.kernel.org/pub/linux/kernel/people/vegard/kernels/20080623-next/DSCF3015.JPG

I don't know what these issues are related too. I can try
debug_initcall for the hang.


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036

  reply	other threads:[~2008-06-23 12:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23  8:25 linux-next: Tree for June 23 Stephen Rothwell
2008-06-23 10:23 ` Vegard Nossum
2008-06-23 10:26   ` Vegard Nossum
2008-06-23 11:02     ` Vegard Nossum
2008-06-23 12:26       ` Vegard Nossum [this message]
2008-06-23 17:26         ` Vegard Nossum
2008-06-23 17:43           ` Vegard Nossum
2008-06-23 18:56       ` Pekka J Enberg
2008-06-23 19:21         ` Christoph Lameter
2009-06-23  5:33 Stephen Rothwell
2009-06-23  6:07 ` Stephen Rothwell
2010-06-23  5:45 Stephen Rothwell
2011-06-23  5:54 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=19f34abd0806230526j77fc20e7w3d92cbe67ad4c552@mail.gmail.com \
    --to=vegard.nossum@gmail.com \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=sfr@canb.auug.org.au \
    --cc=srostedt@redhat.com \
    /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).