From: Andrew Morton <akpm@digeo.com>
To: tomlins@cam.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.52-mm1
Date: Wed, 18 Dec 2002 08:37:17 -0800 [thread overview]
Message-ID: <3E00A43D.ADB20C26@digeo.com> (raw)
In-Reply-To: 20021218122602.288D52230@oscar.casa.dyndns.org
Ed Tomlinson wrote:
>
> Hi
>
> Got this oops this morning reading news:
>
> Dec 18 07:15:29 oscar kernel: printing eip:
> Dec 18 07:15:29 oscar kernel: c0140317
> Dec 18 07:15:29 oscar kernel: Oops: 0002
> Dec 18 07:15:29 oscar kernel: CPU: 0
> Dec 18 07:15:29 oscar kernel: EIP: 0060:[remove_inode_buffers+67/116] Not tainted
> Dec 18 07:15:29 oscar kernel: EFLAGS: 00010246
> Dec 18 07:15:29 oscar kernel: EIP is at remove_inode_buffers+0x43/0x74
> Dec 18 07:15:29 oscar kernel: eax: 0dc4c344 ebx: c3440dc4 ecx: c3440dc6 edx: 0000c344
> Dec 18 07:15:29 oscar kernel: esi: c3440cd4 edi: 00000001 ebp: dfdb9ebc esp: dfdb9e8c
> Dec 18 07:15:29 oscar kernel: ds: 0068 es: 0068 ss: 0068
> Dec 18 07:15:29 oscar kernel: Process kswapd0 (pid: 7, threadinfo=dfdb8000 task=dfdcb860)
> Dec 18 07:15:29 oscar kernel: Stack: c3440cd4 c3440cdc dfdb8000 c0152ff7 c3440cd4 00000080 00000923 d
> Dec 18 07:15:29 oscar kernel: 00000036 00000036 c3440b5c d76876dc 00000000 c01530db 00000080 c
> Dec 18 07:15:29 oscar kernel: 00000080 000001d0 00000221 c02a5374 fffffe27 0000000c 0d024a92 0
Wow, what a mess. Something has written this "c3440cd4" value
into the stack and most of the registers. Presumably it was
some interrupt. Don't know, sorry.
prev parent reply other threads:[~2002-12-18 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 8:36 2.5.52-mm1 Andrew Morton
2002-12-16 8:36 ` 2.5.52-mm1 Andrew Morton
2002-12-17 8:19 ` 2.5.52-mm1 kernel BUG at mm/page_walk.c:430! Helge Hafting
2002-12-17 17:10 ` Andrew Morton
2002-12-18 12:26 ` 2.5.52-mm1 Ed Tomlinson
2002-12-18 16:37 ` Andrew Morton [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=3E00A43D.ADB20C26@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tomlins@cam.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.