linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "KOSAKI Motohiro" <kosaki.motohiro@jp.fujitsu.com>
To: "Mel Gorman" <mel@csn.ul.ie>
Cc: mingo@elte.hu, linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	apw@shadowen.org
Subject: Re: [PATCH 0/2] Relax restrictions on setting CONFIG_NUMA on x86
Date: Sun, 27 Jan 2008 15:54:06 +0900	[thread overview]
Message-ID: <2f11576a0801262254i55cb2c96q40023aa0e53bffce@mail.gmail.com> (raw)
In-Reply-To: <20080126171803.GA29252@csn.ul.ie>

Hi Mel

> > my patch stack is
> >   2.6.24-rc7 +
> >   http://lkml.org/lkml/2007/8/24/220 +
>
> Can you replace this patch with the patch below instead and try again
> please? This is the patch that is actually in git-x86. Out of
> curiousity, have you tried the latest mm branch from git-x86?

to be honest, I didn't understand usage of git, sorry.
I learned method of git checkout today and test again (head of git-x86
+ your previous patch).

result
       -> panic again.

-------------------------------------------------------------------------------------------
  Booting 'kosatest'

root (hd0,0)
 Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz-kosatest ro root=/dev/VolGroup00/LogVol00 rhgb quiet console=tt
y0 console=ttyS0,9600n8r
   [Linux-bzImage, setup=0x2800, size=0x27bd58]
initrd /initrd-kosatest.img
   [Linux-initrd @ 0x1f3bc000, 0x2c052c bytes]

Bad page state in process 'swapper'
page:c13ecfa0 flags:0x00000000 mapping:00000000 mapcount:1 count:0
Trying to fix it up, but a reboot is needed
Backtrace:
Bad page state in process 'swapper'
page:c13ecfc0 flags:0x00000000 mapping:00000000 mapcount:1 count:0
Trying to fix it up, but a reboot is needed
Backtrace:
Bad page state in process 'swapper'
page:c13ecfe0 flags:0x00000000 mapping:00000000 mapcount:1 count:0
Trying to fix it up, but a reboot is needed
Backtrace:
Bad page state in process 'swapper'
page:c13ed000 flags:0xfffedb08 mapping:00000000 mapcount:1 count:-268393021
Trying to fix it up, but a reboot is needed
Backtrace:
BUG: unable to handle kernel paging request at virtual address f000a5c7
printing eip: c014d9b8 *pdpt = 0000000000004001 *pde = 0000000000000000
Oops: 0002 [#1] SMP
Modules linked in:

Pid: 0, comm: swapper Tainted: G    B   (2.6.24-g34984208-dirty #3)
EIP: 0060:[<c014d9b8>] EFLAGS: 00010016 CPU: 0
EIP is at free_hot_cold_page+0xe8/0x14b
EAX: c13ed018 EBX: c13ed000 ECX: 0000000c EDX: f000a5c3
ESI: 00000000 EDI: 00000246 EBP: 00000c00 ESP: c059bf24
 DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
Process swapper (pid: 0, ti=c059a000 task=c05443a0 task.ti=c059a000)
Stack: 00000000 c13ed000 00000fff 0001f680 00000001 c05b19cb c0686000 c05fa520
       0001f680 0001e590 0001f68c 00000001 00000000 00000000 00000000 00000020
       c05ae9dd c04d59e6 c059bf7c c059bf7c c05b2eca c04d59e6 c04d7a11 00008000
Call Trace:
 [<c05b19cb>] free_all_bootmem_core+0x115/0x1b1
 [<c05ae9dd>] mem_init+0x7f/0x368
 [<c05b2eca>] alloc_large_system_hash+0x226/0x251
 [<c05b3dfc>] inode_init_early+0x49/0x72
 [<c05a15ca>] start_kernel+0x281/0x30c
 [<c05a10e0>] unknown_bootoption+0x0/0x195
 =======================
Code: 75 7a 6b f7 14 64 a1 08 40 5e c0 03 74 85 28 9c 5f fa 64 8b 15
10 61 5e c0 b8 40 74 5e c0 ff 44 02 20 8b 56 0c 8d 43 18 8d 4e 0c <89>
42 04 89 53 18 89 48 04 89 46 0c 31 c0 83 3d 98 83 59 c0 00
EIP: [<c014d9b8>] free_hot_cold_page+0xe8/0x14b SS:ESP 0068:c059bf24
---[ end trace ca143223eefdc828 ]---
Kernel panic - not syncing: Attempted to kill the idle task!

  reply	other threads:[~2008-01-27  6:54 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-18 15:35 [PATCH 0/2] Relax restrictions on setting CONFIG_NUMA on x86 Mel Gorman
2008-01-18 15:35 ` [PATCH 1/2] Do not require CONFIG_HIGHMEM64G to set " Mel Gorman
2008-01-18 16:17   ` Ingo Molnar
2008-01-18 15:36 ` [PATCH 2/2] Allow any x86 sub-architecture type to set CONFIG_NUMA Mel Gorman
2008-01-18 16:17   ` Ingo Molnar
2008-01-19  6:35 ` [PATCH 0/2] Relax restrictions on setting CONFIG_NUMA on x86 Andi Kleen
2008-01-19 16:07   ` Mel Gorman
2008-01-22 12:14     ` Ingo Molnar
2008-01-22 12:29       ` Mel Gorman
2008-01-22 15:39         ` Ingo Molnar
2008-01-22 13:33     ` Andi Kleen
2008-01-23 10:28       ` Mel Gorman
2008-01-23 10:45         ` Andi Kleen
2008-01-23 10:57           ` Mel Gorman
2008-01-23 11:11             ` Andi Kleen
2008-01-23 11:15             ` [PATCH 0/2] Relax restrictions on setting CONFIG_NUMA on x86 II Andi Kleen
2008-01-23 11:24               ` Mel Gorman
2008-01-23 13:48                 ` Andi Kleen
2008-01-23 14:15                   ` Mel Gorman
2008-01-21  0:38 ` [PATCH 0/2] Relax restrictions on setting CONFIG_NUMA on x86 KOSAKI Motohiro
2008-01-21 14:35   ` Mel Gorman
2008-01-21 14:49     ` Ingo Molnar
2008-01-21 16:27       ` Mel Gorman
2008-01-23  2:04   ` KOSAKI Motohiro
2008-01-23 10:22     ` Mel Gorman
2008-01-24  3:19       ` KOSAKI Motohiro
2008-01-23 10:23     ` Mel Gorman
2008-01-26 14:10       ` KOSAKI Motohiro
2008-01-26 17:10         ` KOSAKI Motohiro
2008-01-26 17:18         ` Mel Gorman
2008-01-27  6:54           ` KOSAKI Motohiro [this message]
2008-01-28 15:02             ` Ingo Molnar
2008-01-29  2:57               ` KOSAKI Motohiro
2008-01-29 11:34             ` Mel Gorman
2008-02-03  9:32               ` KOSAKI Motohiro

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=2f11576a0801262254i55cb2c96q40023aa0e53bffce@mail.gmail.com \
    --to=kosaki.motohiro@jp.fujitsu.com \
    --cc=apw@shadowen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=mingo@elte.hu \
    /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;
as well as URLs for NNTP newsgroup(s).