WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xense-devel

[Xense-devel] Xen 2 Crashes

To: xense-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xense-devel] Xen 2 Crashes
From: "Pradeep Vincent" <pradeep.vincent@xxxxxxxxx>
Date: Mon, 17 Jul 2006 19:30:46 -0700
Delivery-date: Mon, 17 Jul 2006 19:30:54 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=TpUBtLENtZKe4wsF8h97LI6lE3F7rFIyDzuSKTNAVlz9iSYagZuIgyANg4N7MQcsmKmLiTdrW5eO9og+8tQvRKoDeG5rAFXHooD7ARWDJ5dNoYyDR984+at14jz3kIBlpwN/ETQaR1uToQWn+wQqaIZESqaHvpXq+pDnokfmNT0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xense-devel-request@lists.xensource.com?subject=help>
List-id: "A discussion list for those developing security enhancements for Xen." <xense-devel.lists.xensource.com>
List-post: <mailto:xense-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xense-devel>, <mailto:xense-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xense-devel>, <mailto:xense-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xense-devel-bounces@xxxxxxxxxxxxxxxxxxx
I have been seeing kernel address dereference failures on Xen 2 domU
s. They usually happen after the xen kernel kmallocs some memory and
then tries to access it. Looks like the PDE is marked Read / Write
while the PTE  is marked Read-only. I would think it should be the
other way around  under normal circumstances - anybody seen this kind
of problem.

Unable to handle kernel paging request at virtual address ee0f1000
printing eip:
c01ac9d0
*pde=9bdf0063(000b6063)
*pte=89ebd061(2e0f1061)
Oops: 0003
CPU:    0
EIP:    0819:[<c01ac9d0>]    Not tainted
EFLAGS: 00010246
eax: 00000000   ebx: ee0f1000   ecx: 00000400   edx: 00001000
esi: 00001000   edi: ee0f1000   ebp: ec507f58   esp: ec507f38
ds: 0821   es: 0821   ss: 0821
Process wine (pid: 9297, stackpage=ec507000)<1>
Stack: 00001000 000001f0 ec507f5c 00000000 00000000 ec506000 bffffa9c ec507f98
      ec507fa4 c01ad283 ee280eb8 00000200 00000001 40018000 40021000 edce1e60
      40018000 ee280ebc ffffffea ee280e40 00000000 4004bf40 00000420
00000041 Call Trace: [<c01ad283>] [<c01ad2ee>] [<c01aa0e7>]

<1>Unable to handle kernel paging request at virtual address ed8c4000
printing eip:
c01c30ed
*pde=479e9063(000b4063)
*pte=acb5a061(2d8c4061)
Oops: 0003
CPU:    0
EIP:    0819:[<c01c30ed>]    Not tainted
EFLAGS: 00010286
eax: ed8c4000   ebx: c02a5028   ecx: 00000017   edx: 0000005d
esi: c02a5028   edi: ed8c4000   ebp: edba3f5c   esp: edba3ecc
ds: 0821   es: 0821   ss: 0821
Process perl (pid: 1011, stackpage=edba3000)<1>
Stack: edba3f20 c0134084 c1b3a1a0 edba3f04 00000001 c01337ad ed9b8006 edba3f34
      edba3efc 00000001 fffffffe eacbd440 edba3f7c eb79e560 ed9b8006 0000000a
      2a11d6cb edba3f1c 40000000 00001000 edba3f44 c0117853 ee2804e0
40000000 Call Trace: [<c0134084>] [<c01337ad>] [<c0117853>]
[<c01176d1>] [<c0142550>]
  [<c0129326>] [<c01aa0e7>]

<1>Unable to handle kernel paging request at virtual address edb42000
printing eip:
c01ac9d0
*pde=479e9063(000b4063)
*pte=924cc061(2db42061)
Oops: 0003
CPU:    0
EIP:    0819:[<c01ac9d0>]    Not tainted
EFLAGS: 00010246
eax: 00000000   ebx: edb42000   ecx: 00000400   edx: 00001000
esi: 00001000   edi: edb42000   ebp: edac1f58   esp: edac1f38
ds: 0821   es: 0821   ss: 0821
Process wine (pid: 9307, stackpage=edac1000)<1>
Stack: 00001000 000001f0 edac1f5c 00000000 00000000 edac0000 bffffa9c edac1f98
      edac1fa4 c01ad283 ee280cd8 00000200 00000001 e9e99eb4 c0105e56 edac1fa4
      ee280c60 ee280cdc ffffffea ee280c60 00000000 4004bf40 00000420
00000041 Call Trace: [<c01ad283>] [<c0105e56>] [<c01ad2ee>]
[<c01aa147>]

_______________________________________________
Xense-devel mailing list
Xense-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xense-devel

<Prev in Thread] Current Thread [Next in Thread>
  • [Xense-devel] Xen 2 Crashes, Pradeep Vincent <=