From: Steven Cole <elenstev@mesatop.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: 2.6.12-rc2 oops PREEMPT DEBUG_PAGEALLOC sysenter_past_esp+0x3/0x75
Date: Sat, 9 Apr 2005 08:38:56 -0600 [thread overview]
Message-ID: <200504090838.56671.elenstev@mesatop.com> (raw)
I got around to booting 2.6.12-rc2 here at home last night, and got several (12) oops.
Here is a typical one. They all have the same trace, but occured on differing processes.
[18008.409586] <1>Unable to handle kernel paging request at virtual address c2166000
[24538.187178] printing eip:
[24538.187188] c0102b5c
[24538.187195] *pde = 00007067
[24538.187203] *pte = 02166000
[24538.187214] Oops: 0000 [#4]
[24538.187220] PREEMPT DEBUG_PAGEALLOC
[24538.187239] CPU: 0
[24538.187244] EIP: 0060:[<c0102b5c>] Not tainted VLI
[24538.187251] EFLAGS: 00010046 (2.6.12-rc2)
[24538.187274] EIP is at restore_all+0x4/0x18
[24538.187286] eax: 00000282 ebx: 00000006 ecx: 00000000 edx: 00000001
[24538.187302] esi: 081530d8 edi: 0817f428 ebp: c2164000 esp: c2165fc8
[24538.187315] ds: 007b es: 007b ss: 0068
[24538.187328] Process kppp (pid: 7305, threadinfo=c2164000 task=cb69db10)
[24538.187338] Stack: 00000006 0000541b bfb6d950 081530d8 0817f428 bfb6d928 00000036 c010007b
[24538.187366] 0000007b ffffff00 c0102a9a 00000060 00000282 0000007b
[24538.187387] Call Trace:
[24538.187396] [<c0102a9a>] sysenter_past_esp+0x3/0x75
Prior to that, I'd been running 2.6.12-rc1 without these problems.
Apologies in advance if I don't respond for additional information right
away. I'll be away from the computer for a while today.
Anticipating one question:
[steven@spc testing-2.6]$ grep PREEMPT .config
CONFIG_PREEMPT=y
CONFIG_PREEMPT_BKL=y
# CONFIG_DEBUG_PREEMPT is not set
Steven
reply other threads:[~2005-04-09 14:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200504090838.56671.elenstev@mesatop.com \
--to=elenstev@mesatop.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®