Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S265681AbUATSi0 (ORCPT <rfc822;willy@w.ods.org>);
	Tue, 20 Jan 2004 13:38:26 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265684AbUATShQ
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Tue, 20 Jan 2004 13:37:16 -0500
Received: from mta7.pltn13.pbi.net ([64.164.98.8]:31407 "EHLO
	mta7.pltn13.pbi.net") by vger.kernel.org with ESMTP id S265680AbUATSgH
	(ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Tue, 20 Jan 2004 13:36:07 -0500
Date: Tue, 20 Jan 2004 10:35:56 -0800
From: Mike Fedyk <mfedyk@matchmail.com>
To: Oliver Kiddle <okiddle@yahoo.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: page allocation failure
Message-ID: <20040120183556.GE23765@srv-lnx2600.matchmail.com>
Mail-Followup-To: Oliver Kiddle <okiddle@yahoo.co.uk>,
	linux-kernel@vger.kernel.org
References: <7641.1074512162@gmcs3.local> <20040119193837.6369d498.akpm@osdl.org> <30705.1074618514@gmcs3.local>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <30705.1074618514@gmcs3.local>
User-Agent: Mutt/1.5.5.1+cvs20040105i
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 4588
Lines: 105

On Tue, Jan 20, 2004 at 06:08:34PM +0100, Oliver Kiddle wrote:
> the message about the tape device. As suggested by Mike Fedyk, I had
> the nmi_watchdog stuff enabled. Didn't see any output from it though.
> Would that have displayed its output to the console?

It should have.  Run cat /proc/interrupts and again afew seconds later, does
the NMI: number change?

> 
> patch         D 00000000     0 11620    966                     (NOTLB)
> d7bb7aa8 00000082 c03676c0 00000000 0000000c 00000050 00000000 c03677d4 
>        c0138240 00001fec 536f5e97 00000bc6 f6d0f2e0 f6d0f4a0 00c029db d7bb7abc 
>        c041dedc d7bb7ae8 c0121b9c d7bb7abc 00c029db 0000007b c040e460 f6c41920 

There should be some lines above this in your log...

BTW, the NMI watchdog is supposed to oops when your system hangs so we can
see where the hang is coming from.  What was running when this oops happened?

> Call Trace:
>  [<c0138240>] try_to_free_pages+0x9f/0x15f
>  [<c0121b9c>] schedule_timeout+0x63/0xb7
>  [<c0121b30>] process_timeout+0x0/0x9
>  [<c01186f4>] io_schedule_timeout+0x11/0x19
>  [<c024e343>] blk_congestion_wait+0x7e/0x8d
>  [<c0118cd6>] autoremove_wake_function+0x0/0x4f
>  [<c0118cd6>] autoremove_wake_function+0x0/0x4f
>  [<c0132cd1>] __alloc_pages+0x294/0x319
>  [<c012f3d5>] find_or_create_page+0xa0/0xaa
>  [<c0214daf>] _pagebuf_lookup_pages+0x2fa/0x398
>  [<c0215131>] pagebuf_get+0xba/0x135
>  [<c0208a70>] xfs_trans_read_buf+0x32f/0x38b
>  [<c01d8df1>] xfs_da_do_buf+0x6b1/0x9a6
>  [<c01d9198>] xfs_da_read_buf+0x57/0x5b
>  [<c01dcf5c>] xfs_dir2_block_lookup_int+0x52/0x192
>  [<c01dcf5c>] xfs_dir2_block_lookup_int+0x52/0x192
>  [<c01dce71>] xfs_dir2_block_lookup+0x2f/0xc8
>  [<c01db3a8>] xfs_dir2_lookup+0xc4/0x13b
>  [<c01db401>] xfs_dir2_lookup+0x11d/0x13b
>  [<c0209afe>] xfs_dir_lookup_int+0x4c/0x12b
>  [<c020f3d6>] xfs_lookup+0x50/0x88
>  [<c021cae0>] linvfs_lookup+0x67/0x9f
>  [<c0152ea2>] real_lookup+0xc8/0xea
>  [<c01530f3>] do_lookup+0x96/0xa1
>  [<c0153508>] link_path_walk+0x40a/0x7db
>  [<c0154116>] open_namei+0x83/0x3e1
>  [<c0146b0f>] filp_open+0x3e/0x64
>  [<c0146e98>] sys_open+0x5b/0x8b
>  [<c0108ab7>] syscall_call+0x7/0xb
> 
> 
> xfsdump       D 9855CCF6  2760   676    673                     (NOTLB)
> ece09b04 00000082 f7f9e080 9855ccf6 00000baf 00000000 9855ccf6 00000baf 
>        f7f9e080 000012f8 9855d254 00000baf f51106a0 f5110860 f7ffe760 00000000 
>        f7ffe778 ece09b0c c01186db ece09b3c c0131c2b 00000000 00000000 00000000 
> Call Trace:
>  [<c01186db>] io_schedule+0xe/0x16
>  [<c0131c2b>] mempool_alloc+0xfa/0x117
>  [<c0118cd6>] autoremove_wake_function+0x0/0x4f
>  [<c021789b>] linvfs_get_block_core+0x87/0x2ab
>  [<c0118cd6>] autoremove_wake_function+0x0/0x4f
>  [<c0139296>] __blk_queue_bounce+0x1a1/0x232
>  [<c013935d>] blk_queue_bounce+0x36/0x4d
>  [<c024e510>] __make_request+0x4c/0x537
>  [<c0162ff5>] do_mpage_readpage+0x1a9/0x32a
>  [<c024eb04>] generic_make_request+0x109/0x18a
>  [<c022765b>] radix_tree_node_alloc+0x1f/0x5a
>  [<c02277f4>] radix_tree_insert+0x82/0xb8
>  [<c024ebc2>] submit_bio+0x3d/0x6b
>  [<c0162d26>] mpage_bio_submit+0x23/0x32
>  [<c016324b>] mpage_readpages+0xd5/0x162
>  [<c0217abf>] linvfs_get_block+0x0/0x43
>  [<c0134460>] read_pages+0x134/0x13d
>  [<c0217abf>] linvfs_get_block+0x0/0x43
>  [<c0132ae3>] __alloc_pages+0xa6/0x319
>  [<c010adcd>] do_IRQ+0xc4/0xdf
>  [<c0109424>] common_interrupt+0x18/0x20
>  [<c013469c>] do_page_cache_readahead+0xbf/0x109
>  [<c0134852>] page_cache_readahead+0x16c/0x198
>  [<c012f8d7>] do_generic_mapping_read+0x3c1/0x3d3
>  [<c012f8e9>] file_read_actor+0x0/0xec
>  [<c012fb91>] __generic_file_aio_read+0x1bc/0x1ee
>  [<c012f8e9>] file_read_actor+0x0/0xec
>  [<c021dcb2>] xfs_read+0x15a/0x26c
>  [<c0117d92>] wait_for_completion+0x65/0x95
>  [<c02181af>] linvfs_read_invis+0x90/0xa2
>  [<c0147549>] do_sync_read+0x8b/0xb7
>  [<c01217fa>] update_process_times+0x46/0x52
>  [<c0121674>] update_wall_time+0xd/0x36
>  [<c0121a6c>] do_timer+0xdf/0xe4
>  [<c0147625>] vfs_read+0xb0/0x119
>  [<c01478a0>] sys_read+0x42/0x63
>  [<c0108ab7>] syscall_call+0x7/0xb
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/