From: Jiri Slaby <jirislaby@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: mm-commits@vger.kernel.org, akpm@linux-foundation.org,
Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
tglx@linutronix.de, x86@kernel.org
Subject: Re: mmotm 2009-02-17-12-33 uploaded
Date: Wed, 18 Feb 2009 00:21:01 +0100 [thread overview]
Message-ID: <499B465D.9080502@gmail.com> (raw)
In-Reply-To: <200902172050.n1HKorvc028933@imap1.linux-foundation.org>
On 17.2.2009 21:33, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2009-02-17-12-33 has been uploaded to
Hi,
I'm getting the page fault below everytime during bootup. This is how
__task_rq_lock looks like:
for (;;) {
struct rq *rq;
printk("CPU=%u %p %p %p %s\n", task_cpu(p), p,
task_thread_info(p)->task,
task_thread_info(p), p->comm);
rq = task_rq(p);
spin_lock(&rq->lock);
if (likely(rq == task_rq(p)))
return rq;
spin_unlock(&rq->lock);
}
CPU=2303197184 ffff880012497d90 b8005f57df1d8948 ffffffff80262d0a
migration/0
BUG: unable to handle kernel paging request at 00000003cabbb780
IP: [<ffffffff802399eb>] __sched_setscheduler+0x17b/0x4a0
PGD 0
Oops: 0000 [#1] SMP
last sysfs file:
CPU 0
Modules linked in:
Pid: 1, comm: swapper Not tainted 2.6.29-rc5-mm1_64 #578
RIP: 0010:[<ffffffff802399eb>] [<ffffffff802399eb>]
__sched_setscheduler+0x17b/0x4a0
RSP: 0018:ffff880012497cc0 EFLAGS: 00000086
RAX: 0000000089480000 RBX: ffffffff80262d0a RCX: 00000000ffffffff
RDX: 000000000000d7d7 RSI: 0000000000000046 RDI: ffffffff80835334
RBP: ffff880012497d30 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000010180
R13: 0000000000000000 R14: ffff880012497d90 R15: 0000000000010180
FS: 0000000000000000(0000) GS:ffff880001007000(0000) knlGS:0000000000000000
CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 00000003cabbb780 CR3: 0000000000201000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 0000000000000000 DR7: 0000000000000000
Process swapper (pid: 1, threadinfo ffff880012496000, task ffff880012478000)
Stack:
0000000000000000 ffff880012497dc0 ffff880012498270 ffffffff12478000
0000000000000000 ffffffff80262d0a ffff8800124980f0 0000000000000046
0000000000000246 ffff880012497d50 ffffffff806f1065 0000000000000000
Call Trace:
[<ffffffff80262d0a>] ? tick_check_broadcast_device+0x3a/0x70
[<ffffffff80239d1b>] sched_setscheduler_nocheck+0xb/0x10
[<ffffffff80256ad7>] kthread_create+0xe7/0x120
[<ffffffff8023b820>] ? migration_thread+0x0/0x230
[<ffffffff80262d0a>] ? tick_check_broadcast_device+0x3a/0x70
[<ffffffff80262109>] ? tick_notify+0x369/0x410
[<ffffffff807d9598>] ? migration_init+0x0/0x5c
[<ffffffff805de278>] migration_call+0x376/0x4ed
[<ffffffff807d9598>] ? migration_init+0x0/0x5c
[<ffffffff807d95be>] migration_init+0x26/0x5c
[<ffffffff807d9598>] ? migration_init+0x0/0x5c
[<ffffffff8020904c>] do_one_initcall+0x3c/0x170
[<ffffffff807d31c4>] ? native_smp_prepare_cpus+0x1c0/0x311
[<ffffffff807ca559>] kernel_init+0x76/0x1bc
[<ffffffff8020d8da>] child_rip+0xa/0x20
[<ffffffff807ca4e3>] ? kernel_init+0x0/0x1bc
[<ffffffff8020d8d0>] ? child_rip+0x0/0x20
Code: 69 3a 00 49 8b 5e 08 4c 8b 45 08 48 8b 0b ba db 08 00 00 48 c7 c6
e0 4a 6e 80 48 c7 c7 ce 99 6e 80 31 c0 e8 0b 69 3a 00 8b 43 18 <4c> 03
24 c5 80 b7 7b 80 4c 89 e7 e8 e5 97 3a 00 49 8b 5e 08 31
RIP [<ffffffff802399eb>] __sched_setscheduler+0x17b/0x4a0
RSP <ffff880012497cc0>
CR2: 00000003cabbb780
---[ end trace 4eaa2a86a8e2da22 ]---
next prev parent reply other threads:[~2009-02-17 23:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 20:33 mmotm 2009-02-17-12-33 uploaded akpm
2009-02-17 23:21 ` Jiri Slaby [this message]
2009-02-17 23:31 ` Andrew Morton
2009-02-18 8:45 ` Jiri Slaby
2009-02-18 9:19 ` Jiri Slaby
2009-02-18 9:35 ` Jiri Slaby
2009-02-18 9:53 ` Andrew Morton
2009-02-18 12:15 ` Rusty Russell
2009-02-18 14:50 ` Oleg Nesterov
2009-04-28 19:22 ` Oleg Nesterov
2009-04-28 19:48 ` Andrew Morton
2009-04-28 20:13 ` Oleg Nesterov
2009-02-18 0:52 ` mmotm 2009-02-17-12-33 uploaded (nr_pdflush_threads_min sysctl build error) Randy Dunlap
2009-02-18 1:40 ` Andrew Morton
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=499B465D.9080502@gmail.com \
--to=jirislaby@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mm-commits@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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 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.