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>
Subject: Re: linux-next: Tree for June 23
Date: Mon, 23 Jun 2008 12:23:52 +0200 [thread overview]
Message-ID: <19f34abd0806230323o6373015fj93a85b929545a7a8@mail.gmail.com> (raw)
In-Reply-To: <20080623182549.b0552851.sfr@canb.auug.org.au>
On Mon, Jun 23, 2008 at 10:25 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
> (patches at
> http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/). If you
> are tracking the linux-next tree using git, you should not use "git pull"
> to do so as that will try to merge the new linux-next release with the
> old one. You should use "git fetch" as mentioned in the FAQ on the wiki
> (see below).
Hi,
I got this:
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
[<c01388a4>] warn_on_slowpath+0x54/0x70
[<c015a9d5>] ? trace_hardirqs_off_caller+0x15/0xb0
[<c015aa7b>] ? trace_hardirqs_off+0xb/0x10
[<c0109e85>] ? native_sched_clock+0xb5/0x110
[<c05bdb28>] ? _spin_unlock_irqrestore+0x48/0x80
[<c02b5748>] ? debug_locks_off+0x8/0x50
[<c017dcbe>] ? ftrace_record_ip+0x12e/0x240
[<c010455c>] ? mcount_call+0x5/0x9
[<c0159f22>] check_flags+0x142/0x160
[<c014d3c0>] ? kthreadd+0xf0/0x160
[<c015e089>] lock_acquire+0x59/0xd0
[<c014d3c0>] ? kthreadd+0xf0/0x160
[<c05bd2ad>] _spin_lock+0x3d/0x70
[<c014d3c0>] ? kthreadd+0xf0/0x160
[<c014d3c0>] kthreadd+0xf0/0x160
[<c014d2d0>] ? kthreadd+0x0/0x160
[<c0104547>] kernel_thread_helper+0x7/0x10
=======================
---[ end trace a7919e7f17c0a725 ]---
possible reason: unannotated irqs-on.
irq event stamp: 3198
hardirqs last enabled at (3197): [<c015cb2b>] trace_hardirqs_on+0xb/0x10
hardirqs last disabled at (3198): [<c015aa7b>] trace_hardirqs_off+0xb/0x10
softirqs last enabled at (0): [<c01370ad>] copy_process+0x43d/0x1120
softirqs last disabled at (0): [<00000000>] 0x0
PASSED
Testing tracer wakeup: PASSED
Also, shouldn't there be a MAINTAINERS entry or some file in
Documentation/ for ftrace?
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
next prev parent reply other threads:[~2008-06-23 10:24 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 [this message]
2008-06-23 10:26 ` Vegard Nossum
2008-06-23 11:02 ` Vegard Nossum
2008-06-23 12:26 ` Vegard Nossum
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=19f34abd0806230323o6373015fj93a85b929545a7a8@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).