From: Alexey Dobriyan <adobriyan@sw.ru>
To: torvalds@osdl.org, len.brown@intel.com, ak@suse.de
Cc: linux-kernel@vger.kernel.org
Subject: 2.6.23-rc4: maxcpus still broken
Date: Tue, 28 Aug 2007 15:14:31 +0400 [thread overview]
Message-ID: <20070828111431.GA27707@localhost.sw.ru> (raw)
Every time I try to boot with maxcpus=1 it dies show_stat():
for_each_possible_cpu(i) {
int j;
HERE ==> user = cputime64_add(user, kstat_cpu(i).cpustat.user);
$ grep ACPI .config
$ grep APIC .config
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_LOCAL_APIC=y
Unable to handle kernel paging request at ffffffff804ed6e0 RIP:
[<ffffffff802a5cd0>] show_stat+0xc8/0x3a6
PGD 203067 PUD 207063 PMD 17fc27163 PTE 4ed000
Oops: 0000 [1] SMP
CPU 0
Modules linked in:
Pid: 380, comm: udevd Not tainted 2.6.23-rc4-utrace #1
RIP: 0010:[<ffffffff802a5cd0>] [<ffffffff802a5cd0>] show_stat+0xc8/0x3a6
RSP: 0018:ffff81017ed77d88 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000001
RDX: ffffffff804ed6e0 RSI: 0000000000000000 RDI: 0000000000000001
RBP: 0000000000000022 R08: 0000000000000000 R09: 0000000000000000
R10: ffff81017fd52080 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000011d R14: 0000000000000000 R15: 00007fff33944ef0
FS: 00002b32774b26d0(0000) GS:ffffffff804aa000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: ffffffff804ed6e0 CR3: 000000017f38f000 CR4: 00000000000006a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process udevd (pid: 380, threadinfo ffff81017ed76000, task ffff81017fd52080)
Stack: ffff81017fd52080 ffffffff802418ac ffff81017fd52810 ffff81017fd52080
0000000000000003 ffffffff80241d15 ffff81017fd52810 ffff81017f79d668
0000000046d3d6bf ffffffff80241e73 ffff81017f79d698 ffff81017fd52080
Call Trace:
[<ffffffff802418ac>] check_usage_backwards+0x1e/0x43
[<ffffffff80241d15>] mark_lock+0x367/0x47c
[<ffffffff80241e73>] mark_held_locks+0x49/0x67
[<ffffffff803b1cf8>] __mutex_lock_slowpath+0x254/0x26a
[<ffffffff803b1d03>] __mutex_lock_slowpath+0x25f/0x26a
[<ffffffff8028a216>] seq_read+0x10b/0x2a1
[<ffffffff8028a10b>] seq_read+0x0/0x2a1
[<ffffffff802a0590>] proc_reg_read+0x80/0x9a
[<ffffffff80272a9b>] vfs_read+0x91/0xb5
[<ffffffff80272dd3>] sys_read+0x45/0x6e
[<ffffffff8020b5ae>] system_call+0x7e/0x83
Code: 48 8b 0c 02 48 01 4c 24 68 48 8b 4c 02 08 48 01 4c 24 70 48
RIP [<ffffffff802a5cd0>] show_stat+0xc8/0x3a6
RSP <ffff81017ed77d88>
CR2: ffffffff804ed6e0
awk used greatest stack depth: 4272 bytes left
next reply other threads:[~2007-08-28 11:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-28 11:14 Alexey Dobriyan [this message]
2007-08-28 23:35 ` 2.6.23-rc4: maxcpus still broken Michal Piotrowski
2007-08-29 4:39 ` Alexey Dobriyan
2007-08-29 5:03 ` Hugh Dickins
2007-08-29 5:23 ` Alexey Dobriyan
2007-08-29 6:41 ` Len Brown
2007-08-29 7:25 ` Alexey Dobriyan
2007-08-31 3:26 ` [PATCH] fix maxcpus=1 oops in show_stat() Hugh Dickins
2007-08-31 4:33 ` Linus Torvalds
2007-08-31 7:37 ` Alexey Dobriyan
2007-08-29 20:20 ` 2.6.23-rc4: maxcpus still broken Hugh Dickins
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=20070828111431.GA27707@localhost.sw.ru \
--to=adobriyan@sw.ru \
--cc=ak@suse.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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