From: Nivedita Singhvi <niv@us.ibm.com>
To: xen-devel@lists.xensource.com
Subject: Oops in zap_pmd_range
Date: Wed, 13 Apr 2005 11:44:37 -0700 [thread overview]
Message-ID: <425D6895.4050601@us.ibm.com> (raw)
I got the following on the April 1st nightly source release
of the unstable tree.
2 CPU machine, SMP not configured, default configs for
dom0 (256MB) and dom1 (512MB).
Idle system for the most part, and I wasn't at the machine,
came back to find this scrolling of my screen and in /var/log
messages. Dom1 was hosed. Had to reboot subsequently.
Ran some tests (netperf) between dom0 and dom1 to see
if I could reproduce it, but haven't. I've since upgraded
to 4/12/05 nightly snapshot. Haven't seen it again yet.
Does this look like a valid kernel/oops? Any info that
I could dig up?
Apr 12 15:29:48 nivdom1 kernel: Unable to handle kernel paging request
at virtua
l address c6ec35e4
Apr 12 15:29:48 nivdom1 kernel: printing eip:
Apr 12 15:29:48 nivdom1 kernel: c01434f6
Apr 12 15:29:48 nivdom1 kernel: *pde = ma 7ff64067 pa 00019067
Apr 12 15:29:48 nivdom1 kernel: *pte = ma 079aa063 pa 06ec3063
Apr 12 15:29:48 nivdom1 kernel: [<c0143718>] zap_pmd_range+0x57/0x75
Apr 12 15:29:48 nivdom1 kernel: [<c0143770>] zap_pud_range+0x3a/0x5e
Apr 12 15:29:48 nivdom1 kernel: [<c0143808>] unmap_page_range+0x74/0x8b
Apr 12 15:29:48 nivdom1 kernel: [<c014391c>] unmap_vmas+0xfd/0x223
Apr 12 15:29:48 nivdom1 kernel: [<c01489b7>] exit_mmap+0x84/0x156
Apr 12 15:29:48 nivdom1 kernel: [<c01158ee>] mmput+0x2b/0x94
Apr 12 15:29:48 nivdom1 kernel: [<c015e899>] exec_mmap+0xcb/0x12b
Apr 12 15:29:48 nivdom1 kernel: [<c015eaae>] flush_old_exec+0x123/0x9ca
Apr 12 15:29:48 nivdom1 kernel: [<c015436b>] vfs_read+0xb9/0x129
Apr 12 15:29:48 nivdom1 kernel: [<c015e7c5>] kernel_read+0x4a/0x53
Apr 12 15:29:48 nivdom1 kernel: [<c017c627>] load_elf_binary+0x37d/0xc9a
Apr 12 15:29:48 nivdom1 kernel: [<c013910e>] buffered_rmqueue+0x153/0x2ba
Apr 12 15:29:48 nivdom1 kernel: [<c02016e9>] copy_from_user+0x3d/0x64
Apr 12 15:29:48 nivdom1 kernel: [<c017c2aa>] load_elf_binary+0x0/0xc9a
Apr 12 15:29:48 nivdom1 kernel: [<c015f5ee>]
search_binary_handler+0xbb/0x2e9
thanks,
Nivedita
reply other threads:[~2005-04-13 18:44 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=425D6895.4050601@us.ibm.com \
--to=niv@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/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.