From: Steven Rostedt <rostedt@goodmis.org>
To: "Paul E. McKenney" <paulmck@us.ibm.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
RT <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [BUG RT] - rcupreempt.c:133 on 2.6.23-rc1-rt7
Date: Sun, 05 Aug 2007 00:51:24 -0400 [thread overview]
Message-ID: <1186289484.636.5.camel@localhost.localdomain> (raw)
Why is it, that every time I go to write examples for my chapter in a
book, that I hit a bug!
I got this on bootup of my Thinkpad G41 running SMP.
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
WARNING: at kernel/rcupreempt.c:133 __rcu_read_lock()
[<c010557a>] show_trace_log_lvl+0x35/0x54
[<c01061bd>] show_trace+0x2c/0x2e
[<c01061e8>] dump_stack+0x29/0x2b
[<c01660d9>] __rcu_read_lock+0x13f/0x14e
[<c02f61fd>] ip_local_deliver+0x73/0x2b6
[<c02f5e74>] ip_rcv+0x2d8/0x5ee
[<c02d4324>] netif_receive_skb+0x2b7/0x3fc
[<c02d68b4>] process_backlog+0xb0/0x148
[<c02d6b6a>] net_rx_action+0xe0/0x1dd
[<c01311a8>] ksoftirqd+0x126/0x240
[<c013f9d2>] kthread+0x44/0x69
[<c0105147>] kernel_thread_helper+0x7/0x10
=======================
I don't have time to look further now, and it's something that isn't
easily reproducible (Well, it happened once out of two boots). If you
need me to look further, or need a config or dmesg (I have both), then
just give me a holler.
-- Steve
next reply other threads:[~2007-08-05 4:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 4:51 Steven Rostedt [this message]
2007-08-05 5:05 ` [BUG RT] - rcupreempt.c:133 on 2.6.23-rc1-rt7 Steven Rostedt
2007-08-05 6:59 ` Ingo Molnar
2007-08-05 14:24 ` Steven Rostedt
2007-08-05 15:04 ` Paul E. McKenney
2007-08-05 15:35 ` [PATCH RT] put in a relatively high number for rcu read lock upper limit Steven Rostedt
2007-08-05 17:53 ` Ingo Molnar
2007-08-05 17:58 ` Steven Rostedt
2007-08-06 3:20 ` Paul E. McKenney
2007-08-05 15:26 ` [BUG RT] - rcupreempt.c:133 on 2.6.23-rc1-rt7 Ingo Molnar
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=1186289484.636.5.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@us.ibm.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.