From: "J.A. Magallon" <jamagallon@able.es>
To: linux-kernel@vger.kernel.org
Subject: Re: Stack traces in 2.6.9-rc2-mm4
Date: Mon, 27 Sep 2004 23:12:33 +0000 [thread overview]
Message-ID: <1096326753l.5222l.2l@werewolf.able.es> (raw)
In-Reply-To: <20040927085744.GA32407@elte.hu> (from mingo@elte.hu on Mon Sep 27 10:57:44 2004)
On 2004.09.27, Ingo Molnar wrote:
>
> * Reuben Farrelly <reuben-lkml@reub.net> wrote:
>
> > Since upgrading from -mm3 to -mm4, I'm now getting messages like this
> > logged every second or so:
> >
> > Sep 27 18:28:06 tornado kernel: using smp_processor_id() in preemptible code: swapper/1
> > Sep 27 18:28:06 tornado kernel: [<c0104dce>] dump_stack+0x17/0x19
> > Sep 27 18:28:06 tornado kernel: [<c0117fc6>] smp_processor_id+0x80/0x86
> > Sep 27 18:28:06 tornado kernel: [<c0282bf3>] make_request+0x174/0x2e7
> > Sep 27 18:28:06 tornado kernel: [<c02073dd>] generic_make_request+0xda/0x190
>
> this is the remove-bkl patch's debugging feature showing that there's
> more preempt-unsafe disk statistics code in the RAID code.
>
> i've attached a patch that introduces preempt and non-preempt versions
> of the statistics code and updates the block code to use the appropriate
> ones - does this fix all the smp_processor_id() warnings you get?
>
I got the same on another place...
Sep 28 00:48:51 werewolf xinetd[4228]: Reading included configuration file: /etc/xinetd.d/sshd-xinetd [file=/etc/xinetd.d/sshd-xinetd] [line=12]
Sep 28 00:48:51 werewolf kernel: using smp_processor_id() in preemptible code: X/4012
Sep 28 00:48:51 werewolf kernel: [smp_processor_id+135/141] smp_processor_id+0x87/0x8d
Sep 28 00:48:51 werewolf kernel: [add_timer_randomness+314/365] add_timer_randomness+0x13a/0x16d
Sep 28 00:48:51 werewolf kernel: [<b0206733>] add_timer_randomness+0x13a/0x16d
Sep 28 00:48:51 werewolf kernel: [input_event+85/999] input_event+0x55/0x3e7
Sep 28 00:48:51 werewolf kernel: [<b027fff1>] input_event+0x55/0x3e7
Sep 28 00:48:51 werewolf kernel: [kbd_rate+69/129] kbd_rate+0x45/0x81
Sep 28 00:48:51 werewolf kernel: [<b0213258>] kbd_rate+0x45/0x81
Sep 28 00:48:51 werewolf kernel: [vt_ioctl+1629/7101] vt_ioctl+0x65d/0x1bbd
Sep 28 00:48:51 werewolf kernel: [<b020fb81>] vt_ioctl+0x65d/0x1bbd
Sep 28 00:48:51 werewolf kernel: [handle_mm_fault+333/437] handle_mm_fault+0x14d/0x1b5
Sep 28 00:48:51 werewolf kernel: [<b0149579>] handle_mm_fault+0x14d/0x1b5
Sep 28 00:48:51 werewolf kernel: [do_page_fault+477/1427] do_page_fault+0x1dd/0x593
Sep 28 00:48:51 werewolf xinetd[4228]: Reading included configuration file: /etc/xinetd.d/talk [file=/etc/xinetd.d/talk] [line=16]
Sep 28 00:48:52 werewolf kernel: [<b0117479>] do_page_fault+0x1dd/0x593
Sep 28 00:48:52 werewolf kernel: [destroy_inode+53/55] destroy_inode+0x35/0x37
Sep 28 00:48:52 werewolf kernel: [<b016d407>] destroy_inode+0x35/0x37
Sep 28 00:48:52 werewolf kernel: [tty_ioctl+1224/1256] tty_ioctl+0x4c8/0x4e8
Sep 28 00:48:52 werewolf kernel: [<b020adda>] tty_ioctl+0x4c8/0x4e8
Sep 28 00:48:52 werewolf kernel: [sys_ioctl+489/581] sys_ioctl+0x1e9/0x245
Sep 28 00:48:52 werewolf kernel: [<b0167410>] sys_ioctl+0x1e9/0x245
Sep 28 00:48:52 werewolf kernel: [sysenter_past_esp+82/113] sysenter_past_esp+0x52/0x71
Sep 28 00:48:52 werewolf kernel: [<b0103fd1>] sysenter_past_esp+0x52/0x71
Sep 28 00:48:52 werewolf kernel: using smp_processor_id() in preemptible code: X/4012
Sep 28 00:48:52 werewolf kernel: [smp_processor_id+135/141] smp_processor_id+0x87/0x8d
Sep 28 00:48:52 werewolf kernel: [<b011bc8f>] smp_processor_id+0x87/0x8d
Sep 28 00:48:52 werewolf kernel: [add_timer_randomness+314/365] add_timer_randomness+0x13a/0x16d
Sep 28 00:48:52 werewolf kernel: [<b0206733>] add_timer_randomness+0x13a/0x16d
Sep 28 00:48:52 werewolf kernel: [input_event+85/999] input_event+0x55/0x3e7
Sep 28 00:48:52 werewolf kernel: [<b027fff1>] input_event+0x55/0x3e7
Sep 28 00:48:52 werewolf kernel: [kbd_rate+96/129] kbd_rate+0x60/0x81
Sep 28 00:48:52 werewolf kernel: [<b0213273>] kbd_rate+0x60/0x81
Sep 28 00:48:52 werewolf kernel: [vt_ioctl+1629/7101] vt_ioctl+0x65d/0x1bbd
Sep 28 00:48:52 werewolf kernel: [<b020fb81>] vt_ioctl+0x65d/0x1bbd
Sep 28 00:48:52 werewolf kernel: [handle_mm_fault+333/437] handle_mm_fault+0x14d/0x1b5
Sep 28 00:48:52 werewolf kernel: [<b0149579>] handle_mm_fault+0x14d/0x1b5
Sep 28 00:48:52 werewolf kernel: [do_page_fault+477/1427] do_page_fault+0x1dd/0x593
Sep 28 00:48:52 werewolf kernel: [<b0117479>] do_page_fault+0x1dd/0x593
Sep 28 00:48:52 werewolf kernel: [destroy_inode+53/55] destroy_inode+0x35/0x37
Sep 28 00:48:52 werewolf kernel: [<b016d407>] destroy_inode+0x35/0x37
Sep 28 00:48:52 werewolf kernel: [tty_ioctl+1224/1256] tty_ioctl+0x4c8/0x4e8
Sep 28 00:48:52 werewolf kernel: [<b020adda>] tty_ioctl+0x4c8/0x4e8
Sep 28 00:48:52 werewolf kernel: [sys_ioctl+489/581] sys_ioctl+0x1e9/0x245
Sep 28 00:48:52 werewolf kernel: [<b0167410>] sys_ioctl+0x1e9/0x245
Sep 28 00:48:52 werewolf kernel: [sysenter_past_esp+82/113] sysenter_past_esp+0x52/0x71
Sep 28 00:48:52 werewolf kernel: [<b0103fd1>] sysenter_past_esp+0x52/0x71
Sep 28 00:48:52 werewolf xinetd[4228]: Reading included configuration file: /etc/xinetd.d/tftp [file=/etc/xinetd.d/tftp] [line=12]
....
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandrakelinux release 10.1 (Community) for i586
Linux 2.6.9-rc2-mm4 (gcc 3.4.1 (Mandrakelinux (Alpha 3.4.1-3mdk)) #2
next prev parent reply other threads:[~2004-09-27 23:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 8:01 Reuben Farrelly
2004-09-27 8:23 ` Nick Piggin
2004-09-27 8:57 ` Ingo Molnar
2004-09-27 9:14 ` Reuben Farrelly
2004-09-27 23:12 ` J.A. Magallon [this message]
2004-09-28 7:21 ` Ingo Molnar
2004-09-28 7:49 ` Nick Piggin
2004-09-28 10:24 ` Ingo Molnar
2004-09-28 10:48 ` Nick Piggin
2004-09-30 21:58 ` J.A. Magallon
2004-09-30 22:56 ` Ingo Molnar
2004-09-30 23:16 ` J.A. Magallon
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=1096326753l.5222l.2l@werewolf.able.es \
--to=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
/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®