From: "Martin J. Bligh" <mbligh@mbligh.org>
To: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: 2.6.17-mm5
Date: Sun, 02 Jul 2006 16:27:55 -0700 [thread overview]
Message-ID: <44A8567B.2010309@mbligh.org> (raw)
Panic on NUMA-Q (mm4 was fine). Presumably some new scheduler patch
divide error: 0000 [#1]
8K_STACKS SMP
last sysfs file:
Modules linked in:
CPU: 1
EIP: 0060:[<c0112b6e>] Not tainted VLI
EFLAGS: 00010046 (2.6.17-mm5-autokern1 #1)
EIP is at find_busiest_group+0x1a3/0x47c
eax: 00000000 ebx: 00000007 ecx: 00000000 edx: 00000000
esi: 00000000 edi: e75ff264 ebp: e7405ec8 esp: e7405e58
ds: 007b es: 007b ss: 0068
Process swapper (pid: 0, ti=e7404000 task=c13f8560 task.ti=e7404000)
Stack: e75ff264 00000010 c0119020 00000000 00000000 00000000 00000000 00000000
ffffffff 00000000 00000000 00000001 00000001 00000001 00000080 00000000
00000000 00000200 00000020 00000080 00000000 00000000 e75ff260 c1364960
Call Trace:
[<c0119020>] vprintk+0x5f/0x213
[<c0112efb>] load_balance+0x54/0x1d6
[<c011332d>] rebalance_tick+0xc5/0xe3
[<c01137a3>] scheduler_tick+0x2cb/0x2d3
[<c01215b4>] update_process_times+0x51/0x5d
[<c010c224>] smp_apic_timer_interrupt+0x5a/0x61
[<c0102d5b>] apic_timer_interrupt+0x1f/0x24
[<c01006c0>] default_idle+0x0/0x59
[<c01006f1>] default_idle+0x31/0x59
[<c0100791>] cpu_idle+0x64/0x79
Code: 00 5b 83 f8 1f 89 c6 5f 0f 8e 63 ff ff ff 8b 45 e0 8b 55 e8 01 45 dc 8b 4a 08 89 c2 01 4d d4 c1 e2 07 89 d0 31 d2 89 ce c1 ee 07 <f7> f1 83 7d 9c 00 89 45 e0 74 17 89 45 d8 8b 55 e8 8b 4d a4 8b
EIP: [<c0112b6e>] find_busiest_group+0x1a3/0x47c SS:ESP 0068:e7405e58
next reply other threads:[~2006-07-02 23:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-02 23:27 Martin J. Bligh [this message]
2006-07-02 23:41 ` 2.6.17-mm5 Andrew Morton
2006-07-03 5:25 ` [patch] sched: fix macro -> inline function conversion bug Ingo Molnar
2006-07-03 5:42 ` Andrew Morton
2006-07-03 6:03 ` Ingo Molnar
2006-07-03 6:08 ` Ingo Molnar
2006-07-05 19:36 ` Siddha, Suresh B
2006-07-05 20:02 ` Ingo Molnar
2006-07-05 21:09 ` Siddha, Suresh B
2006-07-05 21:17 ` Ingo Molnar
2006-07-05 21:21 ` Siddha, Suresh B
2006-07-06 8:27 ` Andy Whitcroft
2006-07-03 6:06 ` Peter Williams
2006-07-03 8:23 ` 2.6.17-mm5 Andy Whitcroft
2006-07-03 14:19 ` 2.6.17-mm5 Andy Whitcroft
-- strict thread matches above, loose matches on Subject: below --
2006-07-01 10:35 2.6.17-mm5 Andrew Morton
[not found] <20060701175444.958D6E00608B@knarzkiste.dyndns.org>
2006-07-01 10:35 ` 2.6.17-mm5 Andrew Morton
2006-07-01 11:08 ` 2.6.17-mm5 Reuben Farrelly
2006-07-01 11:51 ` 2.6.17-mm5 Andrew Morton
2006-07-01 12:31 ` 2.6.17-mm5 Reuben Farrelly
2006-07-01 13:06 ` 2.6.17-mm5 Brice Goglin
2006-07-01 17:00 ` 2.6.17-mm5 Greg KH
2006-07-01 18:03 ` 2.6.17-mm5 Ralf Hildebrandt
[not found] ` <20060701142419.GB28750@tlg.swandive.local>
2006-07-01 21:30 ` 2.6.17-mm5 Andrew Morton
2006-07-01 22:26 ` 2.6.17-mm5 James Bottomley
2006-07-01 22:32 ` 2.6.17-mm5 Neil Brown
2006-07-01 22:56 ` 2.6.17-mm5 Jeff Garzik
2006-07-02 0:10 ` 2.6.17-mm5 James Bottomley
2006-07-01 22:54 ` 2.6.17-mm5 Jeff Garzik
2006-07-27 21:02 ` 2.6.17-mm5 Ming Zhang
2006-07-02 10:03 ` 2.6.17-mm5 Andy Whitcroft
2006-07-02 10:14 ` 2.6.17-mm5 Andrew Morton
2006-07-02 10:40 ` 2.6.17-mm5 Andy Whitcroft
2006-07-02 11:14 ` 2.6.17-mm5 Andrew Morton
2006-07-03 0:47 ` 2.6.17-mm5 Theodore Tso
2006-07-03 7:32 ` 2.6.17-mm5 Heiko Carstens
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=44A8567B.2010309@mbligh.org \
--to=mbligh@mbligh.org \
--cc=akpm@osdl.org \
--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 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.