Christopher S. Aker
2009-Jul-16 16:21 UTC
[Xen-devel] d273:v3: reserved bit in page table (ec=0019)
Xen 3.3-testing @ changeset 18651, 64bit dom0 2.6.18.8 @ changeset 888, PAE Files: http://theshore.net/~caker/xen/BUGS/1.22/ (XEN) d273:v3: reserved bit in page table (ec=0019) (XEN) Pagetable walk from 00000000c0101347: (XEN) L4[0x000] = 000000067c36a027 0000000000016495 (XEN) L3[0x003] = 000000067c06c027 0000000000016793 (XEN) L2[0x000] = 00001f5e9d00f403 ffffffffffffffff (XEN) ----[ Xen-3.3.2-rc1 x86_64 debug=y Not tainted ]---- (XEN) CPU: 5 (XEN) RIP: e008:[<ffff828c801c7b50>] show_page_walk+0x1f8/0x244 (XEN) RFLAGS: 0000000000010206 CONTEXT: hypervisor (XEN) rax: ffff830000000000 rbx: 0000000000000001 rcx: 0000000000003b1d (XEN) rdx: 00001f5e9d00f808 rsi: 0000000000000101 rdi: ffff828c80287e70 (XEN) rbp: ffff8300cfcefe88 rsp: ffff8300cfcefe68 r8: 0000000000000004 (XEN) r9: 0000000000000000 r10: 00000000ffffffff r11: 00000000fffffffe (XEN) r12: 00000001f5e9d00f r13: 00000000c0101347 r14: 00000000c0101347 (XEN) r15: 0000000000000000 cr0: 000000008005003b cr4: 00000000000026b0 (XEN) cr3: 00000004ee806000 cr2: ffffa25e9d00f808 (XEN) ds: 007b es: 007b fs: 0000 gs: 0000 ss: 0000 cs: e008 (XEN) Xen stack trace from rsp=ffff8300cfcefe68: (XEN) ffff8300cfceff28 ffff8300cfceff28 00000000c0101347 0000000000000019 (XEN) ffff8300cfcefea8 ffff828c8015a649 ffff8300cecce100 0000000000000019 (XEN) ffff8300cfcefed8 ffff828c8015a7f4 ffff8300cfceff28 ffff8300cf7a8100 (XEN) 00000000c0101347 0000000000000019 ffff8300cfceff18 ffff828c8015eb46 (XEN) 0000000000000000 ffff8300cecce100 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 00007cff303100b7 ffff828c801c56db (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 00000000c13a9fac 00000000deadbeef 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 00000000deadbeef (XEN) 00000000deadbeef 00000000deadbeef 00000000c13a9f80 0000000e00000019 (XEN) 00000000c0101347 0000000000000061 0000000000010a07 00000000c13a9f20 (XEN) 0000000000000069 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000005 ffff8300cecce100 (XEN) Xen call trace: (XEN) [<ffff828c801c7b50>] show_page_walk+0x1f8/0x244 (XEN) [<ffff828c8015a649>] reserved_bit_page_fault+0x53/0x66 (XEN) [<ffff828c8015a7f4>] propagate_page_fault+0x198/0x1ad (XEN) [<ffff828c8015eb46>] do_page_fault+0x516/0x52c (XEN) (XEN) Pagetable walk from ffffa25e9d00f808: (XEN) L4[0x144] = 0000000000000000 ffffffffffffffff (XEN) (XEN) **************************************** (XEN) Panic on CPU 5: (XEN) FATAL PAGE FAULT (XEN) [error_code=0000] (XEN) Faulting linear address: ffffa25e9d00f808 (XEN) **************************************** (XEN) (XEN) Reboot in five seconds... -Chris _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2009-Jul-16 17:05 UTC
Re: [Xen-devel] d273:v3: reserved bit in page table (ec=0019)
On 16/07/2009 17:21, "Christopher S. Aker" <caker@theshore.net> wrote:> Xen 3.3-testing @ changeset 18651, 64bit > dom0 2.6.18.8 @ changeset 888, PAE > > Files: http://theshore.net/~caker/xen/BUGS/1.22/ > > (XEN) d273:v3: reserved bit in page table (ec=0019)Unexpected page fault due to a reserved bit set in a guest page directory entry...> (XEN) Pagetable walk from 00000000c0101347: > (XEN) L4[0x000] = 000000067c36a027 0000000000016495 > (XEN) L3[0x003] = 000000067c06c027 0000000000016793 > (XEN) L2[0x000] = 00001f5e9d00f403 ffffffffffffffff^^^^^^^^^^^^^^^^ Bogus PDE -- the bottom 12 bits are potentially okay (although I don''t think Linux uses the _PAGE_AVAIL bits) but the physical address is definitely bogus. Begs the question where the bogus PDE came from of course, since that would be the actual bug. The crash report here is the symptom when the PDE actually next gets used. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jiang, Yunhong
2009-Jul-17 03:21 UTC
RE: [Xen-devel] d273:v3: reserved bit in page table (ec=0019)
The full log will be helpful. --jyh -----Original Message----- From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Christopher S. Aker Sent: 2009年7月17日 0:21 To: xen devel Subject: [Xen-devel] d273:v3: reserved bit in page table (ec=0019) Xen 3.3-testing @ changeset 18651, 64bit dom0 2.6.18.8 @ changeset 888, PAE Files: http://theshore.net/~caker/xen/BUGS/1.22/ (XEN) d273:v3: reserved bit in page table (ec=0019) (XEN) Pagetable walk from 00000000c0101347: (XEN) L4[0x000] = 000000067c36a027 0000000000016495 (XEN) L3[0x003] = 000000067c06c027 0000000000016793 (XEN) L2[0x000] = 00001f5e9d00f403 ffffffffffffffff (XEN) ----[ Xen-3.3.2-rc1 x86_64 debug=y Not tainted ]---- (XEN) CPU: 5 (XEN) RIP: e008:[<ffff828c801c7b50>] show_page_walk+0x1f8/0x244 (XEN) RFLAGS: 0000000000010206 CONTEXT: hypervisor (XEN) rax: ffff830000000000 rbx: 0000000000000001 rcx: 0000000000003b1d (XEN) rdx: 00001f5e9d00f808 rsi: 0000000000000101 rdi: ffff828c80287e70 (XEN) rbp: ffff8300cfcefe88 rsp: ffff8300cfcefe68 r8: 0000000000000004 (XEN) r9: 0000000000000000 r10: 00000000ffffffff r11: 00000000fffffffe (XEN) r12: 00000001f5e9d00f r13: 00000000c0101347 r14: 00000000c0101347 (XEN) r15: 0000000000000000 cr0: 000000008005003b cr4: 00000000000026b0 (XEN) cr3: 00000004ee806000 cr2: ffffa25e9d00f808 (XEN) ds: 007b es: 007b fs: 0000 gs: 0000 ss: 0000 cs: e008 (XEN) Xen stack trace from rsp=ffff8300cfcefe68: (XEN) ffff8300cfceff28 ffff8300cfceff28 00000000c0101347 0000000000000019 (XEN) ffff8300cfcefea8 ffff828c8015a649 ffff8300cecce100 0000000000000019 (XEN) ffff8300cfcefed8 ffff828c8015a7f4 ffff8300cfceff28 ffff8300cf7a8100 (XEN) 00000000c0101347 0000000000000019 ffff8300cfceff18 ffff828c8015eb46 (XEN) 0000000000000000 ffff8300cecce100 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 00007cff303100b7 ffff828c801c56db (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 00000000c13a9fac 00000000deadbeef 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 00000000deadbeef (XEN) 00000000deadbeef 00000000deadbeef 00000000c13a9f80 0000000e00000019 (XEN) 00000000c0101347 0000000000000061 0000000000010a07 00000000c13a9f20 (XEN) 0000000000000069 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000005 ffff8300cecce100 (XEN) Xen call trace: (XEN) [<ffff828c801c7b50>] show_page_walk+0x1f8/0x244 (XEN) [<ffff828c8015a649>] reserved_bit_page_fault+0x53/0x66 (XEN) [<ffff828c8015a7f4>] propagate_page_fault+0x198/0x1ad (XEN) [<ffff828c8015eb46>] do_page_fault+0x516/0x52c (XEN) (XEN) Pagetable walk from ffffa25e9d00f808: (XEN) L4[0x144] = 0000000000000000 ffffffffffffffff (XEN) (XEN) **************************************** (XEN) Panic on CPU 5: (XEN) FATAL PAGE FAULT (XEN) [error_code=0000] (XEN) Faulting linear address: ffffa25e9d00f808 (XEN) **************************************** (XEN) (XEN) Reboot in five seconds... -Chris _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2009-Jul-17 07:03 UTC
Re: [Xen-devel] d273:v3: reserved bit in page table (ec=0019)
As will reproducibility. This one may need some bisection. -- Keir On 17/07/2009 04:21, "Jiang, Yunhong" <yunhong.jiang@intel.com> wrote:> The full log will be helpful. > > --jyh > > -----Original Message----- > From: xen-devel-bounces@lists.xensource.com > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Christopher S. > Aker > Sent: 2009年7月17日 0:21 > To: xen devel > Subject: [Xen-devel] d273:v3: reserved bit in page table (ec=0019) > > Xen 3.3-testing @ changeset 18651, 64bit dom0 2.6.18.8 @ changeset 888, PAE > > Files: http://theshore.net/~caker/xen/BUGS/1.22/ > > (XEN) d273:v3: reserved bit in page table (ec=0019) > (XEN) Pagetable walk from 00000000c0101347: > (XEN) L4[0x000] = 000000067c36a027 0000000000016495 > (XEN) L3[0x003] = 000000067c06c027 0000000000016793 > (XEN) L2[0x000] = 00001f5e9d00f403 ffffffffffffffff > (XEN) ----[ Xen-3.3.2-rc1 x86_64 debug=y Not tainted ]---- > (XEN) CPU: 5 > (XEN) RIP: e008:[<ffff828c801c7b50>] show_page_walk+0x1f8/0x244 > (XEN) RFLAGS: 0000000000010206 CONTEXT: hypervisor > (XEN) rax: ffff830000000000 rbx: 0000000000000001 rcx: 0000000000003b1d > (XEN) rdx: 00001f5e9d00f808 rsi: 0000000000000101 rdi: ffff828c80287e70 > (XEN) rbp: ffff8300cfcefe88 rsp: ffff8300cfcefe68 r8: 0000000000000004 > (XEN) r9: 0000000000000000 r10: 00000000ffffffff r11: 00000000fffffffe > (XEN) r12: 00000001f5e9d00f r13: 00000000c0101347 r14: 00000000c0101347 > (XEN) r15: 0000000000000000 cr0: 000000008005003b cr4: 00000000000026b0 > (XEN) cr3: 00000004ee806000 cr2: ffffa25e9d00f808 > (XEN) ds: 007b es: 007b fs: 0000 gs: 0000 ss: 0000 cs: e008 > (XEN) Xen stack trace from rsp=ffff8300cfcefe68: > (XEN) ffff8300cfceff28 ffff8300cfceff28 00000000c0101347 0000000000000019 > (XEN) ffff8300cfcefea8 ffff828c8015a649 ffff8300cecce100 0000000000000019 > (XEN) ffff8300cfcefed8 ffff828c8015a7f4 ffff8300cfceff28 ffff8300cf7a8100 > (XEN) 00000000c0101347 0000000000000019 ffff8300cfceff18 ffff828c8015eb46 > (XEN) 0000000000000000 ffff8300cecce100 0000000000000000 0000000000000000 > (XEN) 0000000000000000 0000000000000000 00007cff303100b7 ffff828c801c56db > (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 > (XEN) 00000000c13a9fac 00000000deadbeef 0000000000000000 0000000000000000 > (XEN) 0000000000000000 0000000000000000 0000000000000000 00000000deadbeef > (XEN) 00000000deadbeef 00000000deadbeef 00000000c13a9f80 0000000e00000019 > (XEN) 00000000c0101347 0000000000000061 0000000000010a07 00000000c13a9f20 > (XEN) 0000000000000069 0000000000000000 0000000000000000 0000000000000000 > (XEN) 0000000000000000 0000000000000005 ffff8300cecce100 > (XEN) Xen call trace: > (XEN) [<ffff828c801c7b50>] show_page_walk+0x1f8/0x244 > (XEN) [<ffff828c8015a649>] reserved_bit_page_fault+0x53/0x66 > (XEN) [<ffff828c8015a7f4>] propagate_page_fault+0x198/0x1ad > (XEN) [<ffff828c8015eb46>] do_page_fault+0x516/0x52c > (XEN) > (XEN) Pagetable walk from ffffa25e9d00f808: > (XEN) L4[0x144] = 0000000000000000 ffffffffffffffff > (XEN) > (XEN) **************************************** > (XEN) Panic on CPU 5: > (XEN) FATAL PAGE FAULT > (XEN) [error_code=0000] > (XEN) Faulting linear address: ffffa25e9d00f808 > (XEN) **************************************** > (XEN) > (XEN) Reboot in five seconds... > > -Chris > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jiang, Yunhong
2009-Jul-17 07:06 UTC
RE: [Xen-devel] d273:v3: reserved bit in page table (ec=0019)
I'm just wondering what's the meaning of "PAE" in this output: " Xen 3.3-testing @ changeset 18651, 64bit dom0 2.6.18.8 @ changeset 888, PAE". --jyh Keir Fraser wrote:> As will reproducibility. This one may need some bisection. > > -- Keir > > On 17/07/2009 04:21, "Jiang, Yunhong" <yunhong.jiang@intel.com> wrote: > >> The full log will be helpful. >> >> --jyh >> >> -----Original Message----- >> From: xen-devel-bounces@lists.xensource.com >> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of >> Christopher S. Aker Sent: 2009年7月17日 0:21 >> To: xen devel >> Subject: [Xen-devel] d273:v3: reserved bit in page table (ec=0019) >> >> Xen 3.3-testing @ changeset 18651, 64bit dom0 2.6.18.8 @ changeset >> 888, PAE >> >> Files: http://theshore.net/~caker/xen/BUGS/1.22/ >> >> (XEN) d273:v3: reserved bit in page table (ec=0019) >> (XEN) Pagetable walk from 00000000c0101347: >> (XEN) L4[0x000] = 000000067c36a027 0000000000016495 >> (XEN) L3[0x003] = 000000067c06c027 0000000000016793 >> (XEN) L2[0x000] = 00001f5e9d00f403 ffffffffffffffff >> (XEN) ----[ Xen-3.3.2-rc1 x86_64 debug=y Not tainted ]---- (XEN) >> CPU: 5 (XEN) RIP: e008:[<ffff828c801c7b50>] >> show_page_walk+0x1f8/0x244 (XEN) RFLAGS: 0000000000010206 CONTEXT: >> hypervisor (XEN) rax: ffff830000000000 rbx: 0000000000000001 >> rcx: 0000000000003b1d (XEN) rdx: 00001f5e9d00f808 rsi: >> 0000000000000101 rdi: ffff828c80287e70 (XEN) rbp: ffff8300cfcefe88 >> rsp: ffff8300cfcefe68 r8: 0000000000000004 (XEN) r9: >> 0000000000000000 r10: 00000000ffffffff r11: 00000000fffffffe >> (XEN) r12: 00000001f5e9d00f r13: 00000000c0101347 r14: >> 00000000c0101347 (XEN) r15: 0000000000000000 cr0: 000000008005003b >> cr4: 00000000000026b0 (XEN) cr3: 00000004ee806000 cr2: >> ffffa25e9d00f808 (XEN) ds: 007b es: 007b fs: 0000 gs: 0000 >> ss: 0000 cs: e008 (XEN) Xen stack trace from rsp=ffff8300cfcefe68: >> (XEN) ffff8300cfceff28 ffff8300cfceff28 00000000c0101347 >> 0000000000000019 (XEN) ffff8300cfcefea8 ffff828c8015a649 >> ffff8300cecce100 0000000000000019 (XEN) ffff8300cfcefed8 >> ffff828c8015a7f4 ffff8300cfceff28 ffff8300cf7a8100 (XEN) >> 00000000c0101347 0000000000000019 ffff8300cfceff18 ffff828c8015eb46 >> (XEN) 0000000000000000 ffff8300cecce100 0000000000000000 >> 0000000000000000 (XEN) 0000000000000000 0000000000000000 >> 00007cff303100b7 ffff828c801c56db (XEN) 0000000000000000 >> 0000000000000000 0000000000000000 0000000000000000 (XEN) >> 00000000c13a9fac 00000000deadbeef 0000000000000000 0000000000000000 >> (XEN) 0000000000000000 0000000000000000 0000000000000000 >> 00000000deadbeef (XEN) 00000000deadbeef 00000000deadbeef >> 00000000c13a9f80 0000000e00000019 (XEN) 00000000c0101347 >> 0000000000000061 0000000000010a07 00000000c13a9f20 (XEN) >> 0000000000000069 0000000000000000 0000000000000000 0000000000000000 >> (XEN) 0000000000000000 0000000000000005 ffff8300cecce100 (XEN) >> Xen call trace: (XEN) [<ffff828c801c7b50>] >> show_page_walk+0x1f8/0x244 (XEN) [<ffff828c8015a649>] >> reserved_bit_page_fault+0x53/0x66 (XEN) [<ffff828c8015a7f4>] >> propagate_page_fault+0x198/0x1ad (XEN) [<ffff828c8015eb46>] >> do_page_fault+0x516/0x52c (XEN) (XEN) Pagetable walk from >> ffffa25e9d00f808: (XEN) L4[0x144] = 0000000000000000 >> ffffffffffffffff (XEN) (XEN) >> **************************************** (XEN) Panic on CPU 5: (XEN) >> FATAL PAGE FAULT (XEN) [error_code=0000] (XEN) Faulting linear >> address: ffffa25e9d00f808 (XEN) >> **************************************** (XEN) (XEN) Reboot in five >> seconds... >> >> -Chris >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2009-Jul-17 07:17 UTC
Re: [Xen-devel] d273:v3: reserved bit in page table (ec=0019)
PAE dom0 on 64b Xen, no doubt. The fact the Xen and dom0 decsriptions run into each other has confused you. -- Keir On 17/07/2009 08:06, "Jiang, Yunhong" <yunhong.jiang@intel.com> wrote:> I''m just wondering what''s the meaning of "PAE" in this output: " Xen > 3.3-testing @ changeset 18651, 64bit dom0 2.6.18.8 @ changeset 888, PAE". > > --jyh > > Keir Fraser wrote: >> As will reproducibility. This one may need some bisection. >> >> -- Keir >> >> On 17/07/2009 04:21, "Jiang, Yunhong" <yunhong.jiang@intel.com> wrote: >> >>> The full log will be helpful. >>> >>> --jyh >>> >>> -----Original Message----- >>> From: xen-devel-bounces@lists.xensource.com >>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of >>> Christopher S. Aker Sent: 2009年7月17日 0:21 >>> To: xen devel >>> Subject: [Xen-devel] d273:v3: reserved bit in page table (ec=0019) >>> >>> Xen 3.3-testing @ changeset 18651, 64bit dom0 2.6.18.8 @ changeset >>> 888, PAE >>> >>> Files: http://theshore.net/~caker/xen/BUGS/1.22/ >>> >>> (XEN) d273:v3: reserved bit in page table (ec=0019) >>> (XEN) Pagetable walk from 00000000c0101347: >>> (XEN) L4[0x000] = 000000067c36a027 0000000000016495 >>> (XEN) L3[0x003] = 000000067c06c027 0000000000016793 >>> (XEN) L2[0x000] = 00001f5e9d00f403 ffffffffffffffff >>> (XEN) ----[ Xen-3.3.2-rc1 x86_64 debug=y Not tainted ]---- (XEN) >>> CPU: 5 (XEN) RIP: e008:[<ffff828c801c7b50>] >>> show_page_walk+0x1f8/0x244 (XEN) RFLAGS: 0000000000010206 CONTEXT: >>> hypervisor (XEN) rax: ffff830000000000 rbx: 0000000000000001 >>> rcx: 0000000000003b1d (XEN) rdx: 00001f5e9d00f808 rsi: >>> 0000000000000101 rdi: ffff828c80287e70 (XEN) rbp: ffff8300cfcefe88 >>> rsp: ffff8300cfcefe68 r8: 0000000000000004 (XEN) r9: >>> 0000000000000000 r10: 00000000ffffffff r11: 00000000fffffffe >>> (XEN) r12: 00000001f5e9d00f r13: 00000000c0101347 r14: >>> 00000000c0101347 (XEN) r15: 0000000000000000 cr0: 000000008005003b >>> cr4: 00000000000026b0 (XEN) cr3: 00000004ee806000 cr2: >>> ffffa25e9d00f808 (XEN) ds: 007b es: 007b fs: 0000 gs: 0000 >>> ss: 0000 cs: e008 (XEN) Xen stack trace from rsp=ffff8300cfcefe68: >>> (XEN) ffff8300cfceff28 ffff8300cfceff28 00000000c0101347 >>> 0000000000000019 (XEN) ffff8300cfcefea8 ffff828c8015a649 >>> ffff8300cecce100 0000000000000019 (XEN) ffff8300cfcefed8 >>> ffff828c8015a7f4 ffff8300cfceff28 ffff8300cf7a8100 (XEN) >>> 00000000c0101347 0000000000000019 ffff8300cfceff18 ffff828c8015eb46 >>> (XEN) 0000000000000000 ffff8300cecce100 0000000000000000 >>> 0000000000000000 (XEN) 0000000000000000 0000000000000000 >>> 00007cff303100b7 ffff828c801c56db (XEN) 0000000000000000 >>> 0000000000000000 0000000000000000 0000000000000000 (XEN) >>> 00000000c13a9fac 00000000deadbeef 0000000000000000 0000000000000000 >>> (XEN) 0000000000000000 0000000000000000 0000000000000000 >>> 00000000deadbeef (XEN) 00000000deadbeef 00000000deadbeef >>> 00000000c13a9f80 0000000e00000019 (XEN) 00000000c0101347 >>> 0000000000000061 0000000000010a07 00000000c13a9f20 (XEN) >>> 0000000000000069 0000000000000000 0000000000000000 0000000000000000 >>> (XEN) 0000000000000000 0000000000000005 ffff8300cecce100 (XEN) >>> Xen call trace: (XEN) [<ffff828c801c7b50>] >>> show_page_walk+0x1f8/0x244 (XEN) [<ffff828c8015a649>] >>> reserved_bit_page_fault+0x53/0x66 (XEN) [<ffff828c8015a7f4>] >>> propagate_page_fault+0x198/0x1ad (XEN) [<ffff828c8015eb46>] >>> do_page_fault+0x516/0x52c (XEN) (XEN) Pagetable walk from >>> ffffa25e9d00f808: (XEN) L4[0x144] = 0000000000000000 >>> ffffffffffffffff (XEN) (XEN) >>> **************************************** (XEN) Panic on CPU 5: (XEN) >>> FATAL PAGE FAULT (XEN) [error_code=0000] (XEN) Faulting linear >>> address: ffffa25e9d00f808 (XEN) >>> **************************************** (XEN) (XEN) Reboot in five >>> seconds... >>> >>> -Chris >>> >>> _______________________________________________ >>> Xen-devel mailing list >>> Xen-devel@lists.xensource.com >>> http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jiang, Yunhong
2009-Jul-17 07:37 UTC
RE: [Xen-devel] d273:v3: reserved bit in page table (ec=0019)
Aha, yes, thanks for clarification :-) --jyh Keir Fraser wrote:> PAE dom0 on 64b Xen, no doubt. The fact the Xen and dom0 > decsriptions run > into each other has confused you. > > -- Keir > > On 17/07/2009 08:06, "Jiang, Yunhong" <yunhong.jiang@intel.com> wrote: > >> I'm just wondering what's the meaning of "PAE" in this output: " Xen >> 3.3-testing @ changeset 18651, 64bit dom0 2.6.18.8 @ changeset 888, >> PAE". >> >> --jyh >> >> Keir Fraser wrote: >>> As will reproducibility. This one may need some bisection. >>> >>> -- Keir >>> >>> On 17/07/2009 04:21, "Jiang, Yunhong" > <yunhong.jiang@intel.com> wrote: >>> >>>> The full log will be helpful. >>>> >>>> --jyh >>>> >>>> -----Original Message----- >>>> From: xen-devel-bounces@lists.xensource.com >>>> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of >>>> Christopher S. Aker Sent: 2009年7月17日 0:21 >>>> To: xen devel >>>> Subject: [Xen-devel] d273:v3: reserved bit in page table (ec=0019) >>>> >>>> Xen 3.3-testing @ changeset 18651, 64bit dom0 2.6.18.8 @ changeset >>>> 888, PAE >>>> >>>> Files: http://theshore.net/~caker/xen/BUGS/1.22/ >>>> >>>> (XEN) d273:v3: reserved bit in page table (ec=0019) >>>> (XEN) Pagetable walk from 00000000c0101347: >>>> (XEN) L4[0x000] = 000000067c36a027 0000000000016495 >>>> (XEN) L3[0x003] = 000000067c06c027 0000000000016793 >>>> (XEN) L2[0x000] = 00001f5e9d00f403 ffffffffffffffff >>>> (XEN) ----[ Xen-3.3.2-rc1 x86_64 debug=y Not tainted ]---- (XEN) >>>> CPU: 5 (XEN) RIP: e008:[<ffff828c801c7b50>] >>>> show_page_walk+0x1f8/0x244 (XEN) RFLAGS: 0000000000010206 CONTEXT: >>>> hypervisor (XEN) rax: ffff830000000000 rbx: 0000000000000001 >>>> rcx: 0000000000003b1d (XEN) rdx: 00001f5e9d00f808 rsi: >>>> 0000000000000101 rdi: ffff828c80287e70 (XEN) rbp: >>>> ffff8300cfcefe88 rsp: ffff8300cfcefe68 r8: 0000000000000004 >>>> (XEN) r9: 0000000000000000 r10: 00000000ffffffff r11: >>>> 00000000fffffffe (XEN) r12: 00000001f5e9d00f r13: >>>> 00000000c0101347 r14: 00000000c0101347 (XEN) r15: >>>> 0000000000000000 cr0: 000000008005003b cr4: 00000000000026b0 >>>> (XEN) cr3: 00000004ee806000 cr2: ffffa25e9d00f808 (XEN) ds: 007b >>>> es: 007b fs: 0000 gs: 0000 ss: 0000 cs: e008 (XEN) Xen stack >>>> trace from rsp=ffff8300cfcefe68: (XEN) ffff8300cfceff28 >>>> ffff8300cfceff28 00000000c0101347 0000000000000019 (XEN) >>>> ffff8300cfcefea8 ffff828c8015a649 ffff8300cecce100 >>>> 0000000000000019 (XEN) ffff8300cfcefed8 ffff828c8015a7f4 >>>> ffff8300cfceff28 ffff8300cf7a8100 (XEN) 00000000c0101347 >>>> 0000000000000019 ffff8300cfceff18 ffff828c8015eb46 (XEN) >>>> 0000000000000000 ffff8300cecce100 0000000000000000 >>>> 0000000000000000 (XEN) 0000000000000000 0000000000000000 >>>> 00007cff303100b7 ffff828c801c56db (XEN) 0000000000000000 >>>> 0000000000000000 0000000000000000 0000000000000000 (XEN) >>>> 00000000c13a9fac 00000000deadbeef 0000000000000000 >>>> 0000000000000000 (XEN) 0000000000000000 0000000000000000 >>>> 0000000000000000 00000000deadbeef (XEN) 00000000deadbeef >>>> 00000000deadbeef 00000000c13a9f80 0000000e00000019 (XEN) >>>> 00000000c0101347 0000000000000061 0000000000010a07 >>>> 00000000c13a9f20 (XEN) 0000000000000069 0000000000000000 >>>> 0000000000000000 0000000000000000 (XEN) 0000000000000000 >>>> 0000000000000005 ffff8300cecce100 (XEN) Xen call trace: (XEN) >>>> [<ffff828c801c7b50>] show_page_walk+0x1f8/0x244 (XEN) >>>> [<ffff828c8015a649>] reserved_bit_page_fault+0x53/0x66 (XEN) >>>> [<ffff828c8015a7f4>] propagate_page_fault+0x198/0x1ad (XEN) >>>> [<ffff828c8015eb46>] do_page_fault+0x516/0x52c (XEN) (XEN) >>>> Pagetable walk from ffffa25e9d00f808: (XEN) L4[0x144] >>>> 0000000000000000 ffffffffffffffff (XEN) (XEN) >>>> **************************************** (XEN) Panic on CPU 5: >>>> (XEN) FATAL PAGE FAULT (XEN) [error_code=0000] (XEN) Faulting >>>> linear address: ffffa25e9d00f808 (XEN) >>>> **************************************** (XEN) (XEN) Reboot in >>>> five seconds... >>>> >>>> -Chris >>>> >>>> _______________________________________________ >>>> Xen-devel mailing list >>>> Xen-devel@lists.xensource.com >>>> http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jan Beulich
2009-Jul-17 09:30 UTC
Re: [Xen-devel] d273:v3: reserved bit in page table (ec=0019)
>>> Keir Fraser <keir.fraser@eu.citrix.com> 16.07.09 19:05 >>> >On 16/07/2009 17:21, "Christopher S. Aker" <caker@theshore.net> wrote: >> (XEN) Pagetable walk from 00000000c0101347: >> (XEN) L4[0x000] = 000000067c36a027 0000000000016495 >> (XEN) L3[0x003] = 000000067c06c027 0000000000016793 >> (XEN) L2[0x000] = 00001f5e9d00f403 ffffffffffffffff > ^^^^^^^^^^^^^^^^ >Bogus PDE -- the bottom 12 bits are potentially okay (although I don''t think >Linux uses the _PAGE_AVAIL bits) but the physical address is definitely >bogus. Begs the question where the bogus PDE came from of course, since that >would be the actual bug. The crash report here is the symptom when the PDE >actually next gets used.The low bits are definitely garbage too (unless there''s a kernel component in use that''s not part of the normal 2.6.18-based kernel): L2 entries are only ever written with _PAGE_TABLE attributes, i.e. 0x067. It might be worth dumping out the whole L2 page, though since it''s the first entry it would also seem possible that some physical memory access overran a page boundary. Was there any device pass-through active? Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel