From: Peter Zijlstra <peterz@infradead.org>
To: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: perf_swevent_add warn_on.
Date: Fri, 30 Aug 2013 10:55:52 +0200 [thread overview]
Message-ID: <20130830085552.GB10002@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20130830035716.GA3713@redhat.com>
On Thu, Aug 29, 2013 at 11:57:16PM -0400, Dave Jones wrote:
> WARNING: CPU: 2 PID: 7498 at kernel/events/core.c:5485 perf_swevent_add+0x18d/0x1a0()
> Modules linked in: snd_seq_dummy 8021q garp stp fuse tun rfcomm hidp nfnetlink ipt_ULOG nfc caif_socket caif af_802154 phonet af_rxrpc bnep bluetooth can_bcm rfkill can_raw can llc2 pppoe pppox ppp_generic slhc irda crc_ccitt scsi_transport_iscsi rds af_key rose x25 atm netrom appletalk ipx p8023 psnap p8022 llc ax25 xfs libcrc32c snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm snd_page_alloc snd_timer snd e1000e usb_debug ptp soundcore pps_core pcspkr
> CPU: 2 PID: 7498 Comm: trinity-child1 Not tainted 3.11.0-rc7+ #32
> ffffffff81a228d4 ffff88022ea55a70 ffffffff816fa71e 0000000000000000
> ffff88022ea55aa8 ffffffff81052ebd ffff88022d147000 ffff88024d9cf3e0
> 0000000000000003 0000000000000001 0000000009527bd7 ffff88022ea55ab8
> Call Trace:
> [<ffffffff816fa71e>] dump_stack+0x54/0x74
> [<ffffffff81052ebd>] warn_slowpath_common+0x7d/0xa0
> [<ffffffff81052f9a>] warn_slowpath_null+0x1a/0x20
> [<ffffffff8113ea2d>] perf_swevent_add+0x18d/0x1a0
> [<ffffffff8113f4e7>] event_sched_in.isra.75+0x87/0x1c0
> [<ffffffff8114035a>] group_sched_in+0x6a/0x1c0
> [<ffffffff81140f21>] ctx_sched_in+0x101/0x290
> [<ffffffff81141110>] perf_event_sched_in+0x60/0x90
> [<ffffffff81144c0b>] perf_event_context_sched_in+0x7b/0xc0
> [<ffffffff81145777>] __perf_event_task_sched_in+0x477/0x490
> [<ffffffff81098c74>] ? arch_vtime_task_switch+0x94/0xa0
> [<ffffffff8108cb70>] finish_task_switch+0xf0/0x130
> [<ffffffff817015fd>] __schedule+0x34d/0x970
> [<ffffffff81701c49>] schedule+0x29/0x70
> [<ffffffff810831b4>] do_cpu_nanosleep+0x154/0x250
> [<ffffffff8108316b>] ? do_cpu_nanosleep+0x10b/0x250
> [<ffffffff810833c9>] posix_cpu_nsleep+0x69/0x120
> [<ffffffff81083493>] process_cpu_nsleep+0x13/0x20
> [<ffffffff8107feaa>] SyS_clock_nanosleep+0x9a/0x110
> [<ffffffff8170ded4>] tracesys+0xdd/0xe2
> ---[ end trace 809ae0fc0cbb6fcc ]---
>
>
> 5484 head = find_swevent_head(swhash, event);
> 5485 if (WARN_ON_ONCE(!head))
> 5486 return -EINVAL;
> 5487
>
Does
http://lkml.kernel.org/r/1377355554-8934-1-git-send-email-jolsa@redhat.com
help with that?
prev parent reply other threads:[~2013-08-30 8:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 3:57 Dave Jones
2013-08-30 8:55 ` Peter Zijlstra [this message]
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=20130830085552.GB10002@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@ghostprotocols.net \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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
all inboxes | Powered by JetHome®