From: Tim Savannah <kata198@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [patch] voluntary-preempt-2.6.9-rc2-mm1-S2
Date: Tue, 21 Sep 2004 16:10:44 -0500 [thread overview]
Message-ID: <249a3f9e0409211410422e1ab1@mail.gmail.com> (raw)
Reports in my dmesg from using voluntary-preempt-2.6.9-rc2-mm1-S2
This doesn't include a bunch of reports from nvidia.
using smp_processor_id() in preemptible code: rmmod/3329
[<c011d200>] smp_processor_id+0x84/0x8a
[<c013b527>] __stop_machine_run+0xc3/0xc7
[<c01376a3>] __try_stop_module+0x0/0x42
[<c013b530>] stop_machine_run+0x5/0x18
[<c013769f>] try_stop_module+0x1f/0x23
[<c0137854>] sys_delete_module+0xef/0x171
[<c014d87f>] unmap_vma_list+0xe/0x17
[<c014dbe9>] do_munmap+0x11a/0x176
[<c0104049>] sysenter_past_esp+0x52/0x71
using smp_processor_id() in preemptible code: gkrellm/3542
[<c011d200>] smp_processor_id+0x84/0x8a
[<c02dc66a>] disk_round_stats+0x23/0x8d
[<c02df0cf>] diskstats_show+0x17/0x312
[<c0243de6>] inode_has_perm+0x53/0x87
[<c024668f>] selinux_file_mmap+0x27/0x135
[<c0275834>] __copy_to_user_ll+0x52/0x61
[<c02758e3>] copy_to_user+0x40/0x53
[<c0161bba>] cp_new_stat64+0xf0/0x102
[<c0246280>] selinux_file_permission+0x111/0x166
[<c01750cb>] seq_read+0xc3/0x273
[<c0158a3a>] vfs_read+0xcd/0x126
[<c0158d00>] sys_read+0x41/0x6a
[<c0104049>] sysenter_past_esp+0x52/0x71
using smp_processor_id() in preemptible code: gkrellm/3542
[<c011d200>] smp_processor_id+0x84/0x8a
[<c02dc66a>] disk_round_stats+0x23/0x8d
[<c02df0cf>] diskstats_show+0x17/0x312
[<c01751db>] seq_read+0x1d3/0x273
[<c0158a3a>] vfs_read+0xcd/0x126
[<c0158d00>] sys_read+0x41/0x6a
[<c0104049>] sysenter_past_esp+0x52/0x71
next reply other threads:[~2004-09-21 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-21 21:10 Tim Savannah [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-06 12:29 [patch] voluntary-preempt-2.6.9-rc1-bk12-R6 Ingo Molnar
2004-09-07 9:26 ` [patch] voluntary-preempt-2.6.9-rc1-bk12-R7 Ingo Molnar
2004-09-07 11:57 ` [patch] voluntary-preempt-2.6.9-rc1-bk12-R8 Ingo Molnar
2004-09-07 22:59 ` Lee Revell
2004-09-08 8:20 ` [patch] voluntary-preempt-2.6.9-rc1-bk12-R9 Ingo Molnar
2004-09-08 22:37 ` Lee Revell
2004-09-09 6:17 ` [patch] voluntary-preempt-2.6.9-rc1-bk12-S0 Ingo Molnar
2004-09-19 12:26 ` [patch] voluntary-preempt-2.6.9-rc2-mm1-S1 Ingo Molnar
2004-09-21 2:07 ` BKL backtraces - was: " K.R. Foley
2004-09-21 7:18 ` Ingo Molnar
2004-09-21 7:44 ` [patch] voluntary-preempt-2.6.9-rc2-mm1-S2 Ingo Molnar
2004-09-21 18:51 ` K.R. Foley
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=249a3f9e0409211410422e1ab1@mail.gmail.com \
--to=kata198@gmail.com \
--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