From: Andrew Morton <akpm@osdl.org>
To: linux@horizon.com
Cc: kerndev@sc-software.com, linux-kernel@vger.kernel.org,
Neil Brown <neilb@cse.unsw.edu.au>
Subject: Re: 2.6.6 is crashing repeatedly
Date: Wed, 19 May 2004 21:23:28 -0700 [thread overview]
Message-ID: <20040519212328.0eea3350.akpm@osdl.org> (raw)
In-Reply-To: <20040520040505.14642.qmail@science.horizon.com>
linux@horizon.com wrote:
>
> I already reported (I thought) this message:
>
> May 19 02:23:47: Unable to handle kernel paging request at virtual address efd78000
> May 19 02:23:47: printing eip:
> May 19 02:23:47: c01a999b
> May 19 02:23:47: *pde = 004a7067
> May 19 02:23:47: *pte = 2fd78000
> May 19 02:23:47: Oops: 0002 [#1]
> May 19 02:23:47: DEBUG_PAGEALLOC
> May 19 02:23:47: CPU: 0
> May 19 02:23:47: EIP: 0060:[<c01a999b>] Not tainted
> May 19 02:23:47: EFLAGS: 00010246 (2.6.6)
> May 19 02:23:47: EIP is at encode_entry+0x4b/0x530
> May 19 02:23:47: eax: 00000000 ebx: 00000000 ecx: 00000644 edx: f3532df8
> May 19 02:23:47: esi: efd78000 edi: e4a19644 ebp: 00000654 esp: f14b7b98
> May 19 02:23:47: ds: 007b es: 007b ss: 0068
> May 19 02:23:47: Process nfsd (pid: 1029, threadinfo=f14b6000 task=f1532a80)
> May 19 02:23:47: Stack: 00000008 0000002f f5217080 00000027 00000000 f5217084 f3532df8 00000006
> May 19 02:23:47: e4a1964c 0000001c 02000001 04000900 0019a291 0022e7a8 14343bfc 0022e76b
> May 19 02:23:47: 14343b61 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> May 19 02:23:47: Call Trace:
> May 19 02:23:47: [<c016af1f>] ext3_bread+0x1f/0x90
> May 19 02:23:47: [<c0168505>] ext3_readdir+0x305/0x490
> May 19 02:23:47: [<c011dd18>] in_group_p+0x38/0x70
> May 19 02:23:47: [<c01a9ed0>] nfs3svc_encode_entry_plus+0x0/0x50
> May 19 02:23:47: [<c019d930>] fh_verify+0x280/0x550
> May 19 02:23:47: [<c019d5d0>] nfsd_acceptable+0x0/0xe0
> May 19 02:23:47: [<c013da8c>] open_private_file+0x1c/0x90
> May 19 02:23:47: [<c014ba2d>] vfs_readdir+0x7d/0x90
> May 19 02:23:47: [<c01a11f9>] nfsd_readdir+0x79/0xc0
> May 19 02:23:47: [<c01a6b8a>] nfsd3_proc_readdirplus+0xda/0x1d0
> May 19 02:23:47: [<c01a9ed0>] nfs3svc_encode_entry_plus+0x0/0x50
> May 19 02:23:47: [<c01a8e90>] nfs3svc_decode_readdirplusargs+0x0/0x180
> May 19 02:23:47: [<c019bce6>] nfsd_dispatch+0xb6/0x1a0
> May 19 02:23:47: [<c03139fd>] svc_authenticate+0x4d/0x80
> May 19 02:23:47: [<c03112d7>] svc_process+0x487/0x5f0
> May 19 02:23:47: [<c0103b6c>] common_interrupt+0x18/0x20
> May 19 02:23:47: [<c019bad9>] nfsd+0x179/0x2d0
> May 19 02:23:47: [<c019b960>] nfsd+0x0/0x2d0
> May 19 02:23:47: [<c0101fbd>] kernel_thread_helper+0x5/0x18
> May 19 02:23:47:
> May 19 02:23:47: Code: 89 06 89 c8 0f c8 89 46 04 81 7c 24 1c 00 01 00 00 b8 ff 00
Is it repeatable? If so, does it go away if you disable
CONFIG_DEBUG_PAGEALLOC?
> Which later turned into a reboot-requiring cascade of these:
>
> May 19 06:29:57: <4>qmail-rspawn: page allocation failure. order:0, mode:0x20
> May 19 06:29:57: Call Trace:
> May 19 06:29:57: [<c0127395>] __alloc_pages+0x2d5/0x330
> May 19 06:29:57: [<c012740f>] __get_free_pages+0x1f/0x40
> May 19 06:29:57: [<c012a961>] cache_grow+0x91/0x270
> May 19 06:29:57: [<c012ae3e>] cache_alloc_refill+0x2fe/0x400
> May 19 06:29:57: [<c01261a7>] mempool_alloc+0x67/0x110
hm, you seem to be totally out of memory in the swapout path and in the
tulip Rx ISR. Both codepaths handle that OK as it's not uncommon. This is
probably unrelated to the oops, but it's not good.
next prev parent reply other threads:[~2004-05-22 0:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 4:05 2.6.6 is crashing repeatedly linux
2004-05-20 4:23 ` Andrew Morton [this message]
2004-05-20 5:29 ` Neil Brown
2004-05-20 6:08 ` linux
2004-05-27 11:25 ` linux
2004-05-27 11:35 ` Neil Brown
2004-05-27 12:06 ` Olaf Kirch
2004-05-28 2:42 ` Neil Brown
-- strict thread matches above, loose matches on Subject: below --
2004-05-15 6:22 linux
2004-05-15 6:28 ` Andrew Morton
2004-05-15 7:56 ` linux
2004-05-15 10:07 ` John Heil
2004-05-14 14:46 linux
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=20040519212328.0eea3350.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=kerndev@sc-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.com \
--cc=neilb@cse.unsw.edu.au \
/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.