From: Christopher Warner <chris@servertogo.com>
To: Andi Kleen <ak@suse.de>
Cc: Dave Jones <davej@redhat.com>, Hugh Dickins <hugh@veritas.com>,
cwarner@kernelcode.com, Chris Wright <chrisw@osdl.org>,
"Sergey S. Kostyliov" <rathamahata@ehouse.ru>,
Clem Taylor <clem.taylor@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: x86-64 bad pmds in 2.6.11.6 II
Date: Tue, 10 May 2005 05:36:54 -0400 [thread overview]
Message-ID: <1115717814.7679.2.camel@jasmine> (raw)
In-Reply-To: <1115047729.19314.1.camel@jasmine>
2.6.11.5 kernel,
Tyan S2882/dual AMD 246 opterons
sh:18983: mm/memory.c:99: bad pmd ffff810005974cc8(00007ffffffffe46).
sh:18983: mm/memory.c:99: bad pmd ffff810005974cd0(00007ffffffffe47).
sh:18983: mm/memory.c:99: bad pmd ffff810005974cd8(00007ffffffffe48).
sh:18983: mm/memory.c:99: bad pmd ffff810005974ce0(00007ffffffffe49).
sh:18983: mm/memory.c:99: bad pmd ffff810005974ce8(00007ffffffffe4a).
sh:18983: mm/memory.c:99: bad pmd ffff810005974cf0(00007ffffffffe4b).
sh:18983: mm/memory.c:99: bad pmd ffff810005974cf8(00007ffffffffe4c).
sh:18983: mm/memory.c:99: bad pmd ffff810005974d00(00007ffffffffe4d).
sh:18983: mm/memory.c:99: bad pmd ffff810005974d08(00007ffffffffe4e).
sh:18983: mm/memory.c:99: bad pmd ffff810005974d10(00007ffffffffe4f).
sh:18983: mm/memory.c:99: bad pmd ffff810005974d18(00007ffffffffe50).
sh:18983: mm/memory.c:99: bad pmd ffff810005974d20(00007ffffffffe51).
sh:18983: mm/memory.c:99: bad pmd ffff810005974d30(0000000000000010).
sh:18983: mm/memory.c:99: bad pmd ffff810005974d38(00000000078bfbff).
sh:18983: mm/memory.c:99: bad pmd ffff810005974d40(0000000000000006).
sh:18983: mm/memory.c:99: bad pmd ffff810005974d48(0000000000001000).
sh:18983: mm/memory.c:99: bad pmd ffff810005974d50(0000000000000011).
sh:18983: mm/memory.c:99: bad pmd ffff810005974d58(0000000000000064).
sh:18983: mm/memory.c:99: bad pmd ffff810005974d60(0000000000000003).
sh:18983: mm/memory.c:99: bad pmd ffff810005974d68(0000000000400040).
sh:18983: mm/memory.c:99: bad pmd ffff810005974d70(0000000000000004).
sh:18983: mm/memory.c:99: bad pmd ffff810005974d78(0000000000000038).
sh:18983: mm/memory.c:99: bad pmd ffff810005974d80(0000000000000005).
sh:18983: mm/memory.c:99: bad pmd ffff810005974d88(0000000000000008).
sh:18983: mm/memory.c:99: bad pmd ffff810005974d90(0000000000000007).
sh:18983: mm/memory.c:99: bad pmd ffff810005974d98(00002aaaaaaab000).
sh:18983: mm/memory.c:99: bad pmd ffff810005974da0(0000000000000008).
sh:18983: mm/memory.c:99: bad pmd ffff810005974db0(0000000000000009).
sh:18983: mm/memory.c:99: bad pmd ffff810005974db8(0000000000413a00).
sh:18983: mm/memory.c:99: bad pmd ffff810005974dc0(000000000000000b).
sh:18983: mm/memory.c:99: bad pmd ffff810005974dc8(00000000000007d3).
sh:18983: mm/memory.c:99: bad pmd ffff810005974dd0(000000000000000c).
sh:18983: mm/memory.c:99: bad pmd ffff810005974dd8(00000000000007d3).
sh:18983: mm/memory.c:99: bad pmd ffff810005974de0(000000000000000d).
sh:18983: mm/memory.c:99: bad pmd ffff810005974df0(000000000000000e).
sh:18983: mm/memory.c:99: bad pmd ffff810005974e00(0000000000000017).
sh:18983: mm/memory.c:99: bad pmd ffff810005974e10(000000000000000f).
sh:18983: mm/memory.c:99: bad pmd ffff810005974e18(00007ffffffffe3a).
sh:18983: mm/memory.c:99: bad pmd ffff810005974e38(34365f3638780000)
next prev parent reply other threads:[~2005-05-10 14:21 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 21:44 x86-64 bad pmds in 2.6.11.6 Dave Jones
2005-03-31 10:41 ` Andi Kleen
2005-03-31 21:52 ` Dave Jones
2005-04-01 11:52 ` Sergey S. Kostyliov
2005-04-07 2:49 ` Dave Jones
2005-04-07 6:29 ` Andi Kleen
2005-04-14 13:54 ` Hugh Dickins
2005-04-14 17:01 ` Andi Kleen
2005-04-14 17:34 ` Hugh Dickins
2005-04-14 18:10 ` Andi Kleen
2005-04-14 18:11 ` x86-64 bad pmds in 2.6.11.6 II Andi Kleen
2005-04-14 18:27 ` Chris Wright
2005-04-15 17:24 ` Andi Kleen
2005-04-15 17:28 ` Chris Wright
2005-04-15 17:58 ` Hugh Dickins
2005-04-15 18:07 ` Dave Jones
2005-04-22 17:37 ` Debugging patch was " Andi Kleen
2005-04-27 14:23 ` New debugging " Andi Kleen
2005-04-27 17:37 ` Dave Jones
2005-04-29 11:07 ` Hans Kristian Rosbach
2005-04-19 13:35 ` Andi Kleen
2005-04-19 15:52 ` Hugh Dickins
2005-04-29 11:12 ` Christopher Warner
2005-04-29 16:13 ` Chris Wright
2005-04-29 17:32 ` Dave Jones
2005-05-02 17:00 ` Andi Kleen
2005-05-02 15:28 ` Christopher Warner
2005-05-02 20:33 ` Chris Wright
2005-05-02 21:08 ` Dave Jones
2005-05-03 14:28 ` Andi Kleen
2005-05-03 15:15 ` Dave Jones
2005-05-10 9:36 ` Christopher Warner [this message]
2005-05-10 16:26 ` Chris Wright
2005-05-10 12:03 ` Christopher Warner
2005-05-10 16:38 ` Dave Jones
2005-05-10 16:46 ` Andi Kleen
2005-05-10 16:59 ` Dave Jones
2005-05-10 20:32 ` Andi Kleen
2005-05-10 20:43 ` Chris Wright
2005-05-12 21:23 ` Andi Kleen
2005-05-13 21:51 ` Peter J. Stieber
2005-05-14 17:29 ` Peter J. Stieber
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=1115717814.7679.2.camel@jasmine \
--to=chris@servertogo.com \
--cc=ak@suse.de \
--cc=chrisw@osdl.org \
--cc=clem.taylor@gmail.com \
--cc=cwarner@kernelcode.com \
--cc=davej@redhat.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rathamahata@ehouse.ru \
/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