From: Jiri Slaby <jirislaby@gmail.com>
To: Marco Schwarz <marco.schwarz@gmx.net>
Cc: linux-kernel@vger.kernel.org, trond.myklebust@fys.uio.no
Subject: Re: Kernel error messages
Date: Wed, 08 Nov 2006 16:15:57 +0100 [thread overview]
Message-ID: <4551F4AD.4020401@gmail.com> (raw)
In-Reply-To: <20061108141801.241790@gmx.net>
Cc: trond.myklebust@fys.uio.no
Marco Schwarz wrote:
> Hi,
>
> with a vanilla 2.6.18.2 Kernel I get the following messages when I run a process with high CPU/memory consumption:
>
> Nov 8 15:08:24 linux kernel: BUG: unable to handle kernel paging request at virtual address 6e696c43
> Nov 8 15:08:24 linux kernel: printing eip:
> Nov 8 15:08:12 linux last message repeated 146 times
Which message? (some kind of cut&paste mismatch?)
> Nov 8 15:08:24 linux kernel: c043d3d5
> Nov 8 15:08:24 linux kernel: *pde = 00000000
> Nov 8 15:08:24 linux kernel: Oops: 0000 [#1]
> Nov 8 15:08:24 linux kernel: SMP
> Nov 8 15:08:24 linux kernel: Modules linked in:
> Nov 8 15:08:24 linux kernel: CPU: 1
> Nov 8 15:08:24 linux kernel: EIP: 0060:[<c043d3d5>] Not tainted VLI
> Nov 8 15:08:24 linux kernel: EFLAGS: 00010246 (2.6.18.2 #8)
> Nov 8 15:08:24 linux kernel: EIP is at rpcauth_refreshcred+0x15/0x50
> Nov 8 15:08:24 linux kernel: eax: df6df240 ebx: df6df240 ecx: 00000001 edx: 6e696c2f
> Nov 8 15:08:24 linux kernel: esi: df1b5000 edi: 00000000 ebp: df6df2a8 esp: d8ccfd00
> Nov 8 15:08:24 linux kernel: ds: 007b es: 007b ss: 0068
> Nov 8 15:08:24 linux kernel: Process ln (pid: 11343, ti=d8cce000 task=d5d5a030 task.ti=d8cce000)
> Nov 8 15:08:24 linux kernel: Stack: df6df240 00000000 c043bfcd df6df240 00000000 d8ccfd48 d8ccfd20 c0436ecd
> Nov 8 15:08:24 linux kernel: 00000000 00000000 df1e1410 df1b5000 d8ccfd58 00000006 c01ff735 dd24e7a4
> Nov 8 15:08:24 linux kernel: df1e12f8 df1e12f0 c050ee20 d8ccfd68 00000006 df1b5000 00000017 d8ccfed8
> Nov 8 15:08:24 linux kernel: Call Trace:
> Nov 8 15:08:24 linux kernel: [<c043bfcd>] __rpc_execute+0x4d/0x1f0
> Nov 8 15:08:24 linux kernel: [<c0436ecd>] rpc_call_sync+0x8d/0xb0
> Nov 8 15:08:24 linux kernel: [<c01ff735>] nfs_proc_symlink+0xd5/0x150
> Nov 8 15:08:24 linux kernel: [<c01f8159>] nfs_symlink+0x89/0x190
> Nov 8 15:08:24 linux kernel: [<c0175556>] d_alloc+0xf6/0x180
> Nov 8 15:08:24 linux kernel: [<c0175b1d>] __d_lookup+0x8d/0x110
> Nov 8 15:08:24 linux kernel: [<c0269e8b>] _atomic_dec_and_lock+0x2b/0x50
> Nov 8 15:08:24 linux kernel: [<c01793e3>] mntput_no_expire+0x13/0x70
> Nov 8 15:08:24 linux kernel: [<c016bbe0>] __link_path_walk+0x3f0/0xef0
> Nov 8 15:08:24 linux kernel: [<c0175b1d>] __d_lookup+0x8d/0x110
> Nov 8 15:08:24 linux kernel: [<c01f8841>] nfs_permission+0xb1/0x160
> Nov 8 15:08:24 linux kernel: [<c01f8790>] nfs_permission+0x0/0x160
> Nov 8 15:08:24 linux kernel: [<c016b23a>] permission+0xba/0xe0
> Nov 8 15:08:24 linux kernel: [<c016bb83>] __link_path_walk+0x393/0xef0
> Nov 8 15:08:24 linux kernel: [<c01793e3>] mntput_no_expire+0x13/0x70
> Nov 8 15:08:24 linux kernel: [<c016c74b>] link_path_walk+0x6b/0xd0
> Nov 8 15:08:24 linux kernel: [<c0175b1d>] __d_lookup+0x8d/0x110
> Nov 8 15:08:24 linux kernel: [<c01f8790>] nfs_permission+0x0/0x160
> Nov 8 15:08:24 linux kernel: [<c016b23a>] permission+0xba/0xe0
> Nov 8 15:08:24 linux kernel: [<c016e511>] vfs_symlink+0x91/0x100
> Nov 8 15:08:24 linux kernel: [<c016e5f7>] sys_symlinkat+0x77/0xc0
> Nov 8 15:08:24 linux kernel: [<c016e651>] sys_symlink+0x11/0x20
> Nov 8 15:08:24 linux kernel: [<c0102b4d>] sysenter_past_esp+0x56/0x79
> Nov 8 15:08:24 linux kernel: Code: e8 31 16 ce ff 83 c4 10 eb a2 8d b6 00 00 00 00 8d bf 00 00 00 00 56 53 8b 70 28 89 c3 f6 05 68 da 67 c0 10 75 16 8b 56 08 89 d8 <ff> 52 14 8
> 5 c0 78 04 5b 5e c3 90 89 43 18 5b 5e c3 56 8b 40 10
> Nov 8 15:08:24 linux kernel: EIP: [<c043d3d5>] rpcauth_refreshcred+0x15/0x50 SS:ESP 0068:d8ccfd00
>
> Anyone knows what could be going wrong ?
regards,
--
http://www.fi.muni.cz/~xslaby/ Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8 22A0 32CC 55C3 39D4 7A7E
next prev parent reply other threads:[~2006-11-08 15:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 14:18 Kernel error messages Marco Schwarz
2006-11-08 15:15 ` Jiri Slaby [this message]
2006-11-08 16:57 ` Marco Schwarz
2006-11-08 17:27 ` Trond Myklebust
2006-11-08 17:34 ` Marco Schwarz
-- strict thread matches above, loose matches on Subject: below --
2003-12-29 21:37 Piotr Neuman
2003-08-04 9:49 Erik Rask
2003-07-13 22:06 kernel " Russell Coker
2003-07-14 8:46 ` Oleg Drokin
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=4551F4AD.4020401@gmail.com \
--to=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.schwarz@gmx.net \
--cc=trond.myklebust@fys.uio.no \
/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.