[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[win-pv-devel] BUG: unable to handle kernel paging request - dom0 with kernel 4.1.6 and xen 4.6.0-rc3

To: Paul Durrant <Paul.Durrant@xxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxx>
From: Fabio Fantoni <fabio.fantoni@xxxxxxx>
Date: Tue, 15 Sep 2015 14:55:43 +0200
Cc: "win-pv-devel@xxxxxxxxxxxxxxxxxxxx" <win-pv-devel@xxxxxxxxxxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, RafaÅ WojdyÅa <omeg@xxxxxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 15 Sep 2015 12:56:02 +0000
List-id: Developer list for the Windows PV Drivers subproject <win-pv-devel.lists.xenproject.org>

Il 10/09/2015 16:36, Fabio Fantoni ha scritto:

Il 07/09/2015 16:41, Paul Durrant ha scritto:

-----Original Message-----
From: Fabio Fantoni [mailto:fabio.fantoni@xxxxxxx]
Sent: 07 September 2015 14:01
To: Paul Durrant; Stefano Stabellini
Cc: RafaÅ WojdyÅa; win-pv-devel@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [win-pv-devel] Problems with xenvbd

Il 07/09/2015 13:57, Paul Durrant ha scritto:

-----Original Message-----
From: Fabio Fantoni [mailto:fabio.fantoni@xxxxxxx]
Sent: 07 September 2015 11:33
To: Paul Durrant; Stefano Stabellini
Cc: RafaÅ WojdyÅa; win-pv-devel@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [win-pv-devel] Problems with xenvbd

Il 07/09/2015 11:26, Paul Durrant ha scritto:

Fabio,

     Can you confirm that you don't see any problem if you use
standard

IDE

emulated disks? I certainly don't.

     Paul

WIth ide instead ahci was with same results but about udev problem
now
seems I found the cause, seems the dom0 kernel.
With kernel 3.2.0-4-amd64 version 3.2.68-1+deb7u3 (from wheezy
repository) don't works without udev file, with 3.16.0-0.bpo.4-amd64
version 3.16.7-ckt11-1+deb8u3~bpo70+1 works.
Initially new pv drivers was with network not working with kernel
<3.14
but after seems was solved (I don't know the exactly commit) but
seems
that xen without udev file a newer kernel is still needed.
With 3.16 kernel I had other problems instead, for example with
balloning (even if should not be used).
With second test with kernel 3.16 I tried to remove a workaround of
balloning problem (dom0_mem=2G,max:3G in grub.cfg instead
dom0_mem=2G,max:2G), I nomore saw kern.log spam but W7 domU
crashed at boot.
Another strange things is even if with trace enabled don't show pv
drivers debug lines with 3.16 kernel (on older tests with 3.16 did
if I
remember good)
In attachment the windows minidump.

That yielded:

0: kd> !analyze -v

**********************************************************
*********************

* *
*                        Bugcheck
Analysis                                    *
* *

**********************************************************
*********************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002a8a7c5, Address of the instruction which caused the

bugcheck

Arg3: fffff88001e86c00, Address of the context record for the
exception

that caused the bugcheck

Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx

referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02a8a7c5 498b08          mov     rcx,qword ptr [r8]

CONTEXT:  fffff88001e86c00 -- (.cxr 0xfffff88001e86c00;r)
rax=0000000026f60003 rbx=0000000000000001 rcx=fffff80002c1fc00
rdx=6c8b4830245c8b41 rsi=fffff80002ccf8d0 rdi=0000000000000000
rip=fffff80002a8a7c5 rsp=fffff88001e875e0 rbp=fffff88001e87640
   r8=6c8b4830245c8b40  r9=fffff80002a1e000 r10=fffff80002c1fc00
r11=0000000000000001 r12=fffff88000967000 r13=0000000000000020
r14=0000000000000000 r15=0000000000001000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053 gs=002b
efl=00010202
nt!ExpInterlockedPopEntrySListFault16:
fffff800`02a8a7c5 498b08          mov     rcx,qword ptr [r8]

ds:002b:6c8b4830`245c8b40=????????????????

Last set context:
rax=0000000026f60003 rbx=0000000000000001 rcx=fffff80002c1fc00
rdx=6c8b4830245c8b41 rsi=fffff80002ccf8d0 rdi=0000000000000000
rip=fffff80002a8a7c5 rsp=fffff88001e875e0 rbp=fffff88001e87640
   r8=6c8b4830245c8b40  r9=fffff80002a1e000 r10=fffff80002c1fc00
r11=0000000000000001 r12=fffff88000967000 r13=0000000000000020
r14=0000000000000000 r15=0000000000001000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053 gs=002b
efl=00010202
nt!ExpInterlockedPopEntrySListFault16:
fffff800`02a8a7c5 498b08          mov     rcx,qword ptr [r8]

ds:002b:6c8b4830`245c8b40=????????????????

Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  lsass.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002a8a7c5

STACK_TEXT:
fffff880`01e875e0 00000000`00000000 : 00000000`00000000

00000000`00000000 00000000`00000000 00000000`00000000 :
nt!ExpInterlockedPopEntrySListFault16


FOLLOWUP_IP:
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02a8a7c5 498b08          mov     rcx,qword ptr [r8]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExpInterlockedPopEntrySListFault16+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  556356e8

IMAGE_VERSION:  6.1.7601.18869

STACK_COMMAND:  .cxr 0xfffff88001e86c00 ; kb

FAILURE_BUCKET_ID: X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0

BUCKET_ID:  X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:

km:x64_0x3b_nt!expinterlockedpopentryslistfault16+0

FAILURE_ID_HASH: {b390bf2a-9c11-079f-34b0-5dffcabffe4b}

Followup: MachineOwner
---------

0: kd> .cxr 0xfffff88001e86c00;r
rax=0000000026f60003 rbx=0000000000000001 rcx=fffff80002c1fc00
rdx=6c8b4830245c8b41 rsi=fffff80002ccf8d0 rdi=0000000000000000
rip=fffff80002a8a7c5 rsp=fffff88001e875e0 rbp=fffff88001e87640
   r8=6c8b4830245c8b40  r9=fffff80002a1e000 r10=fffff80002c1fc00
r11=0000000000000001 r12=fffff88000967000 r13=0000000000000020
r14=0000000000000000 r15=0000000000001000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053 gs=002b
efl=00010202
nt!ExpInterlockedPopEntrySListFault16:
fffff800`02a8a7c5 498b08          mov     rcx,qword ptr [r8]

ds:002b:6c8b4830`245c8b40=????????????????

Last set context:
rax=0000000026f60003 rbx=0000000000000001 rcx=fffff80002c1fc00
rdx=6c8b4830245c8b41 rsi=fffff80002ccf8d0 rdi=0000000000000000
rip=fffff80002a8a7c5 rsp=fffff88001e875e0 rbp=fffff88001e87640
   r8=6c8b4830245c8b40  r9=fffff80002a1e000 r10=fffff80002c1fc00
r11=0000000000000001 r12=fffff88000967000 r13=0000000000000020
r14=0000000000000000 r15=0000000000001000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053 gs=002b
efl=00010202
nt!ExpInterlockedPopEntrySListFault16:
fffff800`02a8a7c5 498b08          mov     rcx,qword ptr [r8]

ds:002b:6c8b4830`245c8b40=????????????????

That's pretty strange. I'd say something is probably corrupt.

The corruption I saw for sure about disks are using btrfs as dom0 fs
(in
rare cases) and with qcow2 overlay.
These tests are instead with ext4 and raw domUs disk.
About others corruptions (not only disks) I don't know.

I'm just using a single layer qcow2.

I'm going crazy with these too many problems and haven't time to
do all
useful tests :(

Too many moving parts I'd say. I've been running with a 4.2-rc dom0

kernel, a Xen from about 3 weeks ago and upstream qemu from Xen's
upstream tag (again from about 3 weeks ago) and I'm not seeing any
problems. I do have a fairly standard config though; ide disks and
std-vga
graphics.

    Paul

About dom0 kernel, are you using build from a package o custom build?
Can be useful for me try kernel 4.2 instead?

I'm building my own. I'm on a wheezy base but 3.2 is much too old a
kernel for me.

   Paul


Added xen-devel on cc and changed title.

I tried with kernel 4.1.6 on dom0 built with make-kpkg with config
from Sid (that use same version) except 2 small changes (in
attachment), xen updated based on 4.6.0-rc3.
I did some tests and domUs with new pv drivers seems ok also without
udev file (seems related to old dom0 kernels with new win pv drivers).
I also tried a qcow2 overlay for some hours without saw errors or leak
on check (I'll keep tested further).
Persist the very strange thing of qemu's xen trace not working even if
built with debug and domU's setting is the same.
I tried also to remove the new pv driver from a W10 domU (for install
the new one), I removed them from control panel and I rebooted windows
but on reboot it hang on windows start.
Nothing useful on qemu log, I did a xl destroy completed successfull
but it didn't kill qemu.
The domU's xl cfg in attachment.

cat /etc/xen/qemu-trace-options
xen_platform_log

xl list
Name                                        ID   Mem VCPUs State
Time(s)
Domain-0                                     0  2048     8 r-----
799.0
(null)                                       5   196     2
--p--d       4.8


In syslog I found this:

Sep 10 15:53:27 testVS01OU kernel: [11777.639088] BUG: unable to
handle kernel paging request at ffff8800159b56c0
Sep 10 15:53:27 testVS01OU kernel: [11777.639133] IP:
[<ffffffff81069b7b>] ptep_set_access_flags+0x1b/0x30
Sep 10 15:53:27 testVS01OU kernel: [11777.639169] PGD 1810067 PUD
1811067 PMD 7fe68067 PTE 80100000159b5065
Sep 10 15:53:27 testVS01OU kernel: [11777.639210] Oops: 0003 [#1] SMP
Sep 10 15:53:27 testVS01OU kernel: [11777.639229] Modules linked in:
xt_physdev br_netfilter iptable_filter ip_tables x_tables tun
xen_pciback xen_netback xen_blkback xen_gntalloc xen_gntdev
xen_evtchn xenfs xen_privcmd ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad
ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi
nfsd auth_rpcgss oid_registry nfs_acl nfs lockd grace fscache sunrpc
bridge stp llc loop mgag200 ttm drm_kms_helper drm iTCO_wdt
iTCO_vendor_support i7core_edac lpc_ich snd_pcm snd_timer snd dcdbas
mfd_core edac_core i2c_algo_bit joydev ipmi_si tpm_tis soundcore
ipmi_msghandler tpm coretemp pcspkr evdev 8250_fintek button
processor wmi acpi_power_meter thermal_sys ext4 crc16 mbcache jbd2
dm_mod sd_mod sg sr_mod cdrom hid_generic ata_generic usbhid hid
crc32c_intel ata_piix libata ehci_pci ehci_hcd bnx2 usbcore
usb_common mpt2sas raid_class scsi_transport_sas scsi_mod
Sep 10 15:53:27 testVS01OU kernel: [11777.639686] CPU: 2 PID: 5782
Comm: qemu-system-i38 Not tainted 4.1.6-0m2r-amd64 #3
Sep 10 15:53:27 testVS01OU kernel: [11777.639721] Hardware name: Dell
Inc. PowerEdge T310/02P9X9, BIOS 1.12.0 09/06/2013
Sep 10 15:53:27 testVS01OU kernel: [11777.639755] task:
ffff880072dae350 ti: ffff88001d52c000 task.ti: ffff88001d52c000
Sep 10 15:53:27 testVS01OU kernel: [11777.639787] RIP:
e030:[<ffffffff81069b7b>]  [<ffffffff81069b7b>]
ptep_set_access_flags+0x1b/0x30
Sep 10 15:53:27 testVS01OU kernel: [11777.639830] RSP:
e02b:ffff88001d52fb08  EFLAGS: 00010202
Sep 10 15:53:27 testVS01OU kernel: [11777.639855] RAX:
0000000002020202 RBX: 0000000000000001 RCX: 8000000318bf2b67
Sep 10 15:53:27 testVS01OU kernel: [11777.639887] RDX:
ffff8800159b56c0 RSI: 00007ffab42d8000 RDI: ffff8800040232f8
Sep 10 15:53:27 testVS01OU kernel: [11777.639918] RBP:
ffffea0000566d70 R08: 0000000000000001 R09: 8000000318bf2b01
Sep 10 15:53:27 testVS01OU kernel: [11777.639950] R10:
0000000000007ff0 R11: ffff8800000006c0 R12: ffff88003260cd08
Sep 10 15:53:27 testVS01OU kernel: [11777.639982] R13:
ffff8800040232f8 R14: ffff8800703f7480 R15: 0000000000000015
Sep 10 15:53:27 testVS01OU kernel: [11777.640021] FS:
00007ffabdff1700(0000) GS:ffff88007c880000(0000) knlGS:0000000000000000
Sep 10 15:53:27 testVS01OU kernel: [11777.640058] CS:  e033 DS: 0000
ES: 0000 CR0: 000000008005003b
Sep 10 15:53:27 testVS01OU kernel: [11777.640084] CR2:
ffff8800159b56c0 CR3: 00000000327fc000 CR4: 0000000000002660
Sep 10 15:53:27 testVS01OU kernel: [11777.640113] Stack:
Sep 10 15:53:27 testVS01OU kernel: [11777.640120] 00007ffab42d8000
ffffffff811927fd ffff880072dae350 ffff88007c88a2f0
Sep 10 15:53:27 testVS01OU kernel: [11777.640145] ffff88001d530000
ffff8800703f74e8 fffffffeffffffff ffff8800703f7500
Sep 10 15:53:27 testVS01OU kernel: [11777.640169] 8000000318bf2327
ffff8800159b56c0 ffffffff815910cf ffff880072dae350
Sep 10 15:53:27 testVS01OU kernel: [11777.640193] Call Trace:
Sep 10 15:53:27 testVS01OU kernel: [11777.640207]
[<ffffffff811927fd>] ? handle_mm_fault+0x28d/0x1700
Sep 10 15:53:27 testVS01OU kernel: [11777.640226]
[<ffffffff815910cf>] ? schedule+0x2f/0x80
Sep 10 15:53:27 testVS01OU kernel: [11777.640245]
[<ffffffff812f8e24>] ? call_rwsem_down_read_failed+0x14/0x30
Sep 10 15:53:27 testVS01OU kernel: [11777.640266]
[<ffffffff81064499>] ? __do_page_fault+0x1b9/0x510
Sep 10 15:53:27 testVS01OU kernel: [11777.640285]
[<ffffffff81596e58>] ? page_fault+0x28/0x30
Sep 10 15:53:27 testVS01OU kernel: [11777.640302]
[<ffffffff812fe903>] ? copy_page_to_iter+0x83/0x320
Sep 10 15:53:27 testVS01OU kernel: [11777.640321]
[<ffffffff81166e20>] ? generic_file_read_iter+0x2c0/0x5c0
Sep 10 15:53:27 testVS01OU kernel: [11777.640341]
[<ffffffff8159491c>] ? _raw_spin_lock_irq+0xc/0x60
Sep 10 15:53:27 testVS01OU kernel: [11777.640360]
[<ffffffff81212835>] ? fsnotify+0x335/0x4b0
Sep 10 15:53:27 testVS01OU kernel: [11777.640378]
[<ffffffff811d302f>] ? __vfs_read+0xaf/0xe0
Sep 10 15:53:27 testVS01OU kernel: [11777.640395]
[<ffffffff811d43ed>] ? vfs_read+0x8d/0x150
Sep 10 15:53:27 testVS01OU kernel: [11777.640411]
[<ffffffff811d46ab>] ? SyS_pread64+0x9b/0xb0
Sep 10 15:53:27 testVS01OU kernel: [11777.640428]
[<ffffffff81594eb2>] ? system_call_fastpath+0x16/0x75
Sep 10 15:53:27 testVS01OU kernel: [11777.640446] Code: c4 18 e9 99
30 10 00 66 0f 1f 84 00 00 00 00 00 66 66 66 66 90 53 48 3b 0a 41 0f
95 c1 45 85 c0 41 0f b6 d9 74 13 45 84 c9 74 0e <48> 89 0a 48 8b 7f
40 66 66 66 90 66 66 90 89 d8 5b c3 0f 1f 00
Sep 10 15:53:27 testVS01OU kernel: [11777.641970] RIP
[<ffffffff81069b7b>] ptep_set_access_flags+0x1b/0x30
Sep 10 15:53:27 testVS01OU kernel: [11777.642711]  RSP
<ffff88001d52fb08>
Sep 10 15:53:27 testVS01OU kernel: [11777.643450] CR2: ffff8800159b56c0
Sep 10 15:53:27 testVS01OU kernel: [11777.647305] ------------[ cut
here ]------------
Sep 10 15:53:27 testVS01OU kernel: [11777.648042] kernel BUG at
arch/x86/mm/pageattr.c:214!
Sep 10 15:53:27 testVS01OU kernel: [11777.648764] invalid opcode:
0000 [#2] SMP
Sep 10 15:53:27 testVS01OU kernel: [11777.649483] Modules linked in:
xt_physdev br_netfilter iptable_filter ip_tables x_tables tun
xen_pciback xen_netback xen_blkback xen_gntalloc xen_gntdev
xen_evtchn xenfs xen_privcmd ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad
ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi
nfsd auth_rpcgss oid_registry nfs_acl nfs lockd grace fscache sunrpc
bridge stp llc loop mgag200 ttm drm_kms_helper drm iTCO_wdt
iTCO_vendor_support i7core_edac lpc_ich snd_pcm snd_timer snd dcdbas
mfd_core edac_core i2c_algo_bit joydev ipmi_si tpm_tis soundcore
ipmi_msghandler tpm coretemp pcspkr evdev 8250_fintek button
processor wmi acpi_power_meter thermal_sys ext4 crc16 mbcache jbd2
dm_mod sd_mod sg sr_mod cdrom hid_generic ata_generic usbhid hid
crc32c_intel ata_piix libata ehci_pci ehci_hcd bnx2 usbcore
usb_common mpt2sas raid_class scsi_transport_sas scsi_mod
Sep 10 15:53:27 testVS01OU kernel: [11777.654889] CPU: 2 PID: 5782
Comm: qemu-system-i38 Not tainted 4.1.6-0m2r-amd64 #3
Sep 10 15:53:27 testVS01OU kernel: [11777.655624] Hardware name: Dell
Inc. PowerEdge T310/02P9X9, BIOS 1.12.0 09/06/2013
Sep 10 15:53:27 testVS01OU kernel: [11777.656353] task:
ffff880072dae350 ti: ffff88001d52c000 task.ti: ffff88001d52c000
Sep 10 15:53:27 testVS01OU kernel: [11777.657082] RIP:
e030:[<ffffffff8106749c>]  [<ffffffff8106749c>]
change_page_attr_set_clr+0x44c/0x450
Sep 10 15:53:27 testVS01OU kernel: [11777.657824] RSP:
e02b:ffff88001d52e9d8  EFLAGS: 00010046
Sep 10 15:53:27 testVS01OU kernel: [11777.658552] RAX:
201008001fc900f5 RBX: 0000000000000000 RCX: 0000000000000000
Sep 10 15:53:27 testVS01OU kernel: [11777.659280] RDX:
0000000000000000 RSI: 0000000000000000 RDI: ffff88001d52ea08
Sep 10 15:53:27 testVS01OU kernel: [11777.660004] RBP:
0000000000000000 R08: 0000000000000001 R09: ffff880000000000
Sep 10 15:53:27 testVS01OU kernel: [11777.660724] R10:
00000000deadbeef R11: 0000000000000000 R12: 0000000000000200
Sep 10 15:53:27 testVS01OU kernel: [11777.661437] R13:
0000000000000001 R14: 0000000000000000 R15: 0000000000000005
Sep 10 15:53:27 testVS01OU kernel: [11777.662148] FS:
00007ffabdff1700(0000) GS:ffff88007c880000(0000) knlGS:0000000000000000
Sep 10 15:53:27 testVS01OU kernel: [11777.662863] CS:  e033 DS: 0000
ES: 0000 CR0: 000000008005003b
Sep 10 15:53:27 testVS01OU kernel: [11777.663570] CR2:
ffff8800159b56c0 CR3: 00000000327fc000 CR4: 0000000000002660
Sep 10 15:53:27 testVS01OU kernel: [11777.664280] Stack:
Sep 10 15:53:27 testVS01OU kernel: [11777.665004] 0000000000000004
ffff880000000000 0000000000000000 0000000000000000
Sep 10 15:53:27 testVS01OU kernel: [11777.665722] 0000001000000040
0000000000000001 0000000000000000 0000000000000000
Sep 10 15:53:27 testVS01OU kernel: [11777.666428] 0000000000000010
0000000000000000 0000000500000001 000000000002348b
Sep 10 15:53:27 testVS01OU kernel: [11777.667143] Call Trace:
Sep 10 15:53:27 testVS01OU kernel: [11777.667834]
[<ffffffff8106760f>] ? _set_pages_array+0xdf/0x130
Sep 10 15:53:27 testVS01OU kernel: [11777.668534]
[<ffffffffa036ef9e>] ? ttm_set_pages_caching+0x4e/0x80 [ttm]
Sep 10 15:53:27 testVS01OU kernel: [11777.669237]
[<ffffffffa036f0d0>] ? ttm_alloc_new_pages.isra.5+0xb0/0x170 [ttm]
Sep 10 15:53:27 testVS01OU kernel: [11777.669952]
[<ffffffffa036fb06>] ? ttm_pool_populate+0x3c6/0x4c0 [ttm]
Sep 10 15:53:27 testVS01OU kernel: [11777.670656]
[<ffffffffa036c262>] ? ttm_bo_move_memcpy+0x582/0x620 [ttm]
Sep 10 15:53:27 testVS01OU kernel: [11777.671355]
[<ffffffff811a2558>] ? __vmalloc_node_range+0x198/0x2a0
Sep 10 15:53:27 testVS01OU kernel: [11777.672057]
[<ffffffffa0369c77>] ? ttm_bo_handle_move_mem+0x267/0x5e0 [ttm]
Sep 10 15:53:27 testVS01OU kernel: [11777.672763]
[<ffffffff810052f9>] ? __raw_callee_save_xen_pmd_val+0x11/0x1e
Sep 10 15:53:27 testVS01OU kernel: [11777.673472]
[<ffffffffa036a8bb>] ? ttm_bo_mem_space+0xeb/0x360 [ttm]
Sep 10 15:53:27 testVS01OU kernel: [11777.674182]
[<ffffffffa036ad0f>] ? ttm_bo_validate+0x1df/0x1f0 [ttm]
Sep 10 15:53:27 testVS01OU kernel: [11777.674886]
[<ffffffff8119fdfa>] ? lazy_max_pages+0x1a/0x30
Sep 10 15:53:27 testVS01OU kernel: [11777.675592]
[<ffffffff811a095d>] ? free_vmap_area_noflush+0x2d/0x60
Sep 10 15:53:27 testVS01OU kernel: [11777.676305]
[<ffffffffa0354b72>] ? mgag200_bo_push_sysram+0x82/0xc0 [mgag200]
Sep 10 15:53:27 testVS01OU kernel: [11777.677025]
[<ffffffffa034f9c1>] ?
mga_crtc_do_set_base.isra.8.constprop.20+0x81/0x3f0 [mgag200]
Sep 10 15:53:27 testVS01OU kernel: [11777.677755]
[<ffffffff813221c8>] ? pci_bus_write_config_dword+0x78/0x90
Sep 10 15:53:27 testVS01OU kernel: [11777.678471]
[<ffffffffa03511ca>] ? mga_crtc_mode_set+0x149a/0x25d0 [mgag200]
Sep 10 15:53:27 testVS01OU kernel: [11777.679178]
[<ffffffff812eb827>] ? idr_get_empty_slot+0x187/0x3e0
Sep 10 15:53:27 testVS01OU kernel: [11777.679872]
[<ffffffff812eb427>] ? idr_mark_full+0x57/0x70
Sep 10 15:53:27 testVS01OU kernel: [11777.680562]
[<ffffffff812ebd66>] ? idr_alloc+0x76/0xd0
Sep 10 15:53:27 testVS01OU kernel: [11777.681251]
[<ffffffffa0388939>] ? drm_crtc_helper_set_mode+0x309/0x540
[drm_kms_helper]
Sep 10 15:53:27 testVS01OU kernel: [11777.681954]
[<ffffffffa0389969>] ? drm_crtc_helper_set_config+0x8d9/0xb00
[drm_kms_helper]
Sep 10 15:53:27 testVS01OU kernel: [11777.682654]
[<ffffffff81594b9c>] ? _raw_spin_unlock_irqrestore+0x1c/0x50
Sep 10 15:53:27 testVS01OU kernel: [11777.683358]
[<ffffffffa0317998>] ? drm_mode_set_config_internal+0x68/0x100 [drm]
Sep 10 15:53:27 testVS01OU kernel: [11777.684050]
[<ffffffffa03947cf>] ? drm_fb_helper_pan_display+0x9f/0xe0
[drm_kms_helper]
Sep 10 15:53:27 testVS01OU kernel: [11777.684726]
[<ffffffff8135ba81>] ? fb_pan_display+0xc1/0x180
Sep 10 15:53:27 testVS01OU kernel: [11777.685384]
[<ffffffff81356166>] ? bit_update_start+0x26/0x50
Sep 10 15:53:27 testVS01OU kernel: [11777.686021]
[<ffffffff81355b01>] ? fbcon_switch+0x391/0x540
Sep 10 15:53:27 testVS01OU kernel: [11777.686641]
[<ffffffff813cd31f>] ? redraw_screen+0x15f/0x240
Sep 10 15:53:27 testVS01OU kernel: [11777.687240]
[<ffffffff813542aa>] ? fbcon_blank+0x23a/0x2f0
Sep 10 15:53:27 testVS01OU kernel: [11777.687819]
[<ffffffff81594b9c>] ? _raw_spin_unlock_irqrestore+0x1c/0x50
Sep 10 15:53:27 testVS01OU kernel: [11777.688391]
[<ffffffff810c923e>] ? console_unlock+0x1ee/0x450
Sep 10 15:53:27 testVS01OU kernel: [11777.688956]
[<ffffffff81150919>] ? irq_work_queue+0x9/0x80
Sep 10 15:53:27 testVS01OU kernel: [11777.689510]
[<ffffffff810c9042>] ? wake_up_klogd+0x32/0x40
Sep 10 15:53:27 testVS01OU kernel: [11777.690054]
[<ffffffff810c9dd0>] ? vprintk_emit+0x2b0/0x4e0
Sep 10 15:53:27 testVS01OU kernel: [11777.690584]
[<ffffffff81594af7>] ? _raw_spin_lock_irqsave+0x17/0x70
Sep 10 15:53:27 testVS01OU kernel: [11777.691112]
[<ffffffff810da4e6>] ? internal_add_timer+0x36/0xa0
Sep 10 15:53:27 testVS01OU kernel: [11777.691639]
[<ffffffff81594b9c>] ? _raw_spin_unlock_irqrestore+0x1c/0x50
Sep 10 15:53:27 testVS01OU kernel: [11777.692173]
[<ffffffff810dc7d4>] ? mod_timer+0x154/0x1d0
Sep 10 15:53:27 testVS01OU kernel: [11777.692708]
[<ffffffff813cde81>] ? do_unblank_screen+0xb1/0x1e0
Sep 10 15:53:27 testVS01OU kernel: [11777.693247]
[<ffffffff812fa209>] ? bust_spinlocks+0x19/0x40
Sep 10 15:53:27 testVS01OU kernel: [11777.693779]
[<ffffffff810196a1>] ? oops_end+0x41/0x120
Sep 10 15:53:27 testVS01OU kernel: [11777.694304]
[<ffffffff8158b86d>] ? no_context+0x2fc/0x336
Sep 10 15:53:27 testVS01OU kernel: [11777.694821]
[<ffffffff81596e58>] ? page_fault+0x28/0x30
Sep 10 15:53:27 testVS01OU kernel: [11777.695330]
[<ffffffff81069b7b>] ? ptep_set_access_flags+0x1b/0x30
Sep 10 15:53:27 testVS01OU kernel: [11777.695834]
[<ffffffff811927fd>] ? handle_mm_fault+0x28d/0x1700
Sep 10 15:53:27 testVS01OU kernel: [11777.696343]
[<ffffffff815910cf>] ? schedule+0x2f/0x80
Sep 10 15:53:27 testVS01OU kernel: [11777.696854]
[<ffffffff812f8e24>] ? call_rwsem_down_read_failed+0x14/0x30
Sep 10 15:53:27 testVS01OU kernel: [11777.697363]
[<ffffffff81064499>] ? __do_page_fault+0x1b9/0x510
Sep 10 15:53:27 testVS01OU kernel: [11777.697896]
[<ffffffff81596e58>] ? page_fault+0x28/0x30
Sep 10 15:53:27 testVS01OU kernel: [11777.698398]
[<ffffffff812fe903>] ? copy_page_to_iter+0x83/0x320
Sep 10 15:53:27 testVS01OU kernel: [11777.698901]
[<ffffffff81166e20>] ? generic_file_read_iter+0x2c0/0x5c0
Sep 10 15:53:27 testVS01OU kernel: [11777.699407]
[<ffffffff8159491c>] ? _raw_spin_lock_irq+0xc/0x60
Sep 10 15:53:27 testVS01OU kernel: [11777.699910]
[<ffffffff81212835>] ? fsnotify+0x335/0x4b0
Sep 10 15:53:27 testVS01OU kernel: [11777.700411]
[<ffffffff811d302f>] ? __vfs_read+0xaf/0xe0
Sep 10 15:53:27 testVS01OU kernel: [11777.700904]
[<ffffffff811d43ed>] ? vfs_read+0x8d/0x150
Sep 10 15:53:27 testVS01OU kernel: [11777.701393]
[<ffffffff811d46ab>] ? SyS_pread64+0x9b/0xb0
Sep 10 15:53:27 testVS01OU kernel: [11777.701877]
[<ffffffff81594eb2>] ? system_call_fastpath+0x16/0x75
Sep 10 15:53:27 testVS01OU kernel: [11777.702365] Code: f7 00 00 e9
25 ff ff ff 0f 0b 4c 89 e8 49 c1 ed 05 48 c1 e8 03 83 e0 03 4c 09 e8
80 b8 44 c9 82 81 00 41 0f 95 c5 e9 19 fd ff ff <0f> 0b 0f 0b 66 66
66 66 90 41 55 45 31 c0 31 d2 41 b9 04 00 00
Sep 10 15:53:27 testVS01OU kernel: [11777.703486] RIP
[<ffffffff8106749c>] change_page_attr_set_clr+0x44c/0x450
Sep 10 15:53:27 testVS01OU kernel: [11777.704013]  RSP
<ffff88001d52e9d8>
Sep 10 15:53:27 testVS01OU kernel: [11777.704528] ---[ end trace
0371e8f24f53a075 ]---


If you need other informations/tests tell me and I'll post them.
Any help is appreciated.

Thanks for any reply and sorry for my bad english.

Attachment: W10.cfg
Description: Text document

Attachment: .config
Description: Text document

_______________________________________________
win-pv-devel mailing list
win-pv-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/win-pv-devel

References:
- Re: [win-pv-devel] Problems with xenvbd
  - From: Paul Durrant
- Re: [win-pv-devel] Problems with xenvbd
  - From: Fabio Fantoni
- Re: [win-pv-devel] Problems with xenvbd
  - From: Paul Durrant
- Re: [win-pv-devel] Problems with xenvbd
  - From: Paul Durrant
- Re: [win-pv-devel] Problems with xenvbd
  - From: Stefano Stabellini
- Re: [win-pv-devel] Problems with xenvbd
  - From: Paul Durrant
- Re: [win-pv-devel] Problems with xenvbd
  - From: Stefano Stabellini
- Re: [win-pv-devel] Problems with xenvbd
  - From: Fabio Fantoni
- Re: [win-pv-devel] Problems with xenvbd
  - From: Paul Durrant
- Re: [win-pv-devel] Problems with xenvbd
  - From: Fabio Fantoni
- Re: [win-pv-devel] Problems with xenvbd
  - From: Paul Durrant
- Re: [win-pv-devel] Problems with xenvbd
  - From: Fabio Fantoni
- Re: [win-pv-devel] Problems with xenvbd
  - From: Paul Durrant
- Re: [win-pv-devel] Problems with xenvbd
  - From: Fabio Fantoni

Prev by Date: Re: [win-pv-devel] Assertion failures in xenvif with DHCP disabled
Next by Date: Re: [win-pv-devel] PV Drivers Offline Removal
Previous by thread: Re: [win-pv-devel] Problems with xenvbd
Next by thread: Re: [win-pv-devel] Problems with xenvbd
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.