From: "Noah Watkins" <noahwatkins@gmail.com>
To: "Steven Rostedt" <rostedt@goodmis.org>
Cc: "Sven-Thorsten Dietrich" <sven@thebigcorporation.com>,
LKML <linux-kernel@vger.kernel.org>,
RT <linux-rt-users@vger.kernel.org>,
"Ingo Molnar" <mingo@elte.hu>,
"Thomas Gleixner" <tglx@linutronix.de>,
paulmck <paulmck@linux.vnet.ibm.com>
Subject: Re: [BUG RT] 2.6.25.8-rt7 on 8-way
Date: Tue, 1 Jul 2008 14:08:51 -0500 [thread overview]
Message-ID: <7618ba960807011208n3aacbc65l41255e3996d2ee4b@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0806300835050.5403@gandalf.stny.rr.com>
While I have disabled RCU tracing to suppress the messages, I am
getting them in another context:
BUG: using smp_processor_id() in preemptible [00000000] code: sshd/3114
caller is __qdisc_run+0x12e/0x1b5
Pid: 3114, comm: sshd Not tainted 2.6.25.8-rt7 #3
Call Trace:
[<ffffffff8112da39>] debug_smp_processor_id+0xad/0xb8
[<ffffffff8120e264>] __qdisc_run+0x12e/0x1b5
[<ffffffff811ff1c8>] dev_queue_xmit+0x140/0x278
[<ffffffff8122239e>] ip_queue_xmit+0x2c2/0x350
[<ffffffff8127f8a6>] add_preempt_count+0x12/0x94
[<ffffffff8108263e>] __inc_zone_state+0x6a/0x88
[<ffffffff81231ffe>] tcp_transmit_skb+0x77e/0x7ba
[<ffffffff8109aa60>] kmem_cache_alloc_node+0x129/0x152
[<ffffffff81233a75>] __tcp_push_pending_frames+0x713/0x7df
[<ffffffff81228da2>] tcp_sendmsg+0x93a/0xa52
[<ffffffff811f0e97>] sock_aio_write+0xf8/0x110
[<ffffffff8109feeb>] do_sync_write+0xc9/0x10c
[<ffffffff81046da6>] autoremove_wake_function+0x0/0x2e
[<ffffffff8103868b>] current_fs_time+0x1e/0x24
[<ffffffff810a06ae>] vfs_write+0xc0/0x156
[<ffffffff810a0c67>] sys_write+0x48/0x74
[<ffffffff8100bf6b>] tracesys+0xdc/0xe1
On Mon, Jun 30, 2008 at 7:37 AM, Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Sun, 29 Jun 2008, Sven-Thorsten Dietrich wrote:
>
>>
>> On Sun, 2008-06-29 at 16:32 -0500, Noah Watkins wrote:
>> > My kernel is very, very noisy with the following bug:
>> >
>> > - Full dmesg below
>> > - Please CC me
>> >
>>
>> I found this as well (adding Paul).
>>
>> If you disable CONFIG_PREEMPT_RCU_BOOST, does it go away?
>>
>
> Turning off CONFIG_RCU_TRACE will also make it go away. The bug is that
> the tracing of the RCU boost code uses smp_processor_id while the RCU
> boost code is not in an atomic section.
>
> Paul has a fix for this already, and will be out in the next releases.
>
> -- Steve
>
next prev parent reply other threads:[~2008-07-01 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-29 21:32 Noah Watkins
2008-06-29 22:23 ` Sven-Thorsten Dietrich
2008-06-29 23:18 ` Noah Watkins
2008-06-29 23:28 ` Paul E. McKenney
2008-06-30 12:37 ` Steven Rostedt
2008-07-01 19:08 ` Noah Watkins [this message]
2008-07-01 19:42 ` Steven Rostedt
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=7618ba960807011208n3aacbc65l41255e3996d2ee4b@mail.gmail.com \
--to=noahwatkins@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=sven@thebigcorporation.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 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®