From: Jay Lan <jlan@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: IA64 Kexec-Kdump kernel patch
Date: Thu, 17 Aug 2006 18:53:19 +0000 [thread overview]
Message-ID: <44E4BB1F.5060004@sgi.com> (raw)
In-Reply-To: <1155538073.2585.44.camel@linux-znh>
Jack Steiner wrote:
> On Wed, Aug 16, 2006 at 03:34:52PM -0700, Jay Lan wrote:
> >
>
> Why did the crash occur? Was the disk full? Otherwise, the cached
> pages _should_ have been written to disk.
>
> Do you have a console log?
>
Hi Jack,
I reserved insufficient memory for the crash dump kernel.
Once i increased from 128M to 256M, the problem went away.
Thanks,
- jay
oom-killer: gfp_mask=0x200d2, order=0
Call Trace:
[<a0000001000138e0>] show_stack+0x40/0xa0
spà00000015d57a40 bspà00000015d514a0
[<a000000100013970>] dump_stack+0x30/0x60
spà00000015d57c10 bspà00000015d51488
[<a0000001000eb000>] out_of_memory+0x60/0x3a0
spà00000015d57c10 bspà00000015d51448
[<a0000001000eeb50>] __alloc_pages+0x3d0/0x520
spà00000015d57c20 bspà00000015d513d0
[<a0000001000e65d0>] generic_file_buffered_write+0x310/0xd00
spà00000015d57c30 bspà00000015d512f0
[<a0000001000e7620>] __generic_file_aio_write_nolock+0x660/0x740
spà00000015d57cc0 bspà00000015d51280
[<a0000001000e77f0>] generic_file_aio_write+0xf0/0x200
spà00000015d57d30 bspà00000015d51220
[<a0000001002343c0>] ext3_file_write+0x60/0x200
spà00000015d57d40 bspà00000015d511e0
[<a00000010012e470>] do_sync_write+0x170/0x1e0
spà00000015d57d40 bspà00000015d511a0
[<a00000010012fb30>] vfs_write+0x1b0/0x340
spà00000015d57e20 bspà00000015d51150
[<a0000001001307b0>] sys_write+0x70/0xe0
spà00000015d57e20 bspà00000015d510d8
[<a00000010000c180>] ia64_ret_from_syscall+0x0/0x20
spà00000015d57e30 bspà00000015d510d8
[<a000000000010620>] __kernel_syscall_via_break+0x0/0x20
spà00000015d58000
bspà00000015d510d8
prev parent reply other threads:[~2006-08-17 18:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 6:47 IA64 Kexec-Kdump kernel patch Zou Nan hai
2006-08-14 21:24 ` Bob Montgomery
2006-08-15 0:47 ` Zou Nan hai
2006-08-15 1:56 ` Jay Lan
2006-08-15 17:39 ` Bob Montgomery
2006-08-15 19:15 ` Jay Lan
2006-08-15 19:31 ` Bob Montgomery
2006-08-15 19:46 ` Keshavamurthy Anil S
2006-08-15 22:36 ` Zou Nan hai
2006-08-15 22:40 ` Zou Nan hai
2006-08-16 18:25 ` Bob Montgomery
2006-08-16 22:34 ` Jay Lan
2006-08-16 22:46 ` Jay Lan
2006-08-17 0:34 ` Jay Lan
2006-08-17 0:38 ` Jack Steiner
2006-08-17 2:57 ` Horms
2006-08-17 3:56 ` Zou Nan hai
2006-08-17 18:53 ` Jay Lan [this message]
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=44E4BB1F.5060004@sgi.com \
--to=jlan@sgi.com \
--cc=linux-ia64@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.