RE: [Xen-devel] Re: Reproducable data corruption on xen-unstable

[Rik van Riel <riel@xxxxxxxxxx>]

On Fri, 4 Feb 2005, Ian Pratt wrote:

> (vm86 is not widely used, so I can belive we could have lurking bugs on 
> that path).
Confirmed, by running Dave Jones's scrashme program, inside a
xenU domain with 32 virtual CPUs:

vm86: could not access userspace vm86_info
Unable to handle kernel paging request at virtual address 000171d3
 printing eip:
0000ec83
*pde = ma 308ac067 pa 01709067
*pte = ma 00000000 pa 55555000
 [<c0108d4b>] syscall_call+0x7/0xb
Oops: 0000 [#2]
SMP
Modules linked in: nfs lockd md5 ipv6 autofs4 sunrpc dm_mod
CPU:    0
EIP:    0855:[<0000ec83>]    Not tainted VLI
EFLAGS: 00030f42   (2.6.10-1.1121_FC4xenU)
EIP is at 0xec83
eax: 64e9000b   ebx: 0038cc83   ecx: 2cd0e800   edx: 1ee9000b
esi: 8dffffff   edi: 0038cc83   ebp: 2cc0e800   esp: c62fdf24
ds: 0000   es: 0000   ss: 0069
Process scrashme (pid: 19875, threadinfo=c62fc000 task=c82fd020)
Stack: 104613c3 00008d00 00000003 00000fc2 00000001 00006693 31ff31ff f05589f6
       0026b48d 8d000000 000027bc fe830000 8b187406 448b084d 453b40b1 890c74f0
       07e82404 8d00047f 4601387c 7e0cfe83 74778ddd e8243489 ffff4162 c789c085
Call Trace:
 [<c0108d4b>] syscall_call+0x7/0xb
Code:  Bad EIP value.

--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel