Hi all, After resume from ACPI S3 system has only CPU0 enabled, every vCPU from every domain works on CPU0 [1]. When trying to pin some vCPU to CPU1 got error: xl vcpu-pin testvm 1 1 libxl: error: libxl.c:2565:libxl_set_vcpuaffinity setting vcpu affinity: Invalid argument What went wrong? How can I reenable CPU1-CPU3? System info: xen 4.1.3 linux 3.4.18 with acpi-s3 patches from Konrad''s git Processor: Intel i5-2520M dmesg from dom0 and hypervisor attached. BTW Are there any plans to upstream acpi-s3 patches? [1] xl vcpu-list: Name ID VCPU CPU State Time(s) CPU Affinity dom0 0 0 0 r-- 1347.8 any cpu dom0 0 1 0 -b- 594.4 any cpu dom0 0 2 0 -b- 421.1 any cpu dom0 0 3 0 -b- 432.6 any cpu netvm 1 0 0 -b- 596.6 any cpu netvm 1 1 0 -b- 363.7 any cpu firewallvm 2 0 0 -b- 170.5 any cpu firewallvm 2 1 0 -b- 122.5 any cpu devel17 3 0 0 -b- 137.0 any cpu devel17 3 1 0 -b- 112.9 any cpu devel17 3 2 0 -b- 97.9 any cpu devel17 3 3 0 -b- 116.0 any cpu vm2 4 0 0 -b- 418.6 any cpu vm2 4 1 0 -b- 390.2 any cpu private 5 0 0 -b- 175.9 any cpu private 5 1 0 -b- 161.6 any cpu mail 6 0 0 -b- 1587.1 any cpu mail 6 1 0 -b- 1717.5 any cpu testvm 7 0 0 -b- 73.0 any cpu testvm 7 1 0 -b- 68.9 any cpu testvm 7 2 0 -b- 51.4 any cpu testvm 7 3 0 -b- 67.1 any cpu disp1 8 0 0 -b- 199.9 any cpu -- Best Regards / Pozdrawiam, Marek Marczykowski Invisible Things Lab _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
>>> On 29.11.12 at 19:55, Marek Marczykowski <marmarek@invisiblethingslab.com> wrote: > After resume from ACPI S3 system has only CPU0 enabled, every vCPU from > every > domain works on CPU0 [1]. When trying to pin some vCPU to CPU1 got error: > xl vcpu-pin testvm 1 1 > libxl: error: libxl.c:2565:libxl_set_vcpuaffinity setting vcpu affinity: > Invalid argument > > What went wrong? How can I reenable CPU1-CPU3?According to the "xl dmesg" output you sent, CPU1-3 are all online (their presence in the output following "Dumping timer queues:" confirms this). So I suppose you will need to go do some debugging to find out where and why the set-affinity operation fails, and/or why the scheduler puts everything on a single pCPU (if it really does, the output of "xl vcpu-list" is only a hint towards that). Rather than using ''c'', ''r'' might have been the more useful debug key. Jan
On 30.11.2012 10:33, Jan Beulich wrote:>>>> On 29.11.12 at 19:55, Marek Marczykowski <marmarek@invisiblethingslab.com> wrote: >> After resume from ACPI S3 system has only CPU0 enabled, every vCPU from >> every >> domain works on CPU0 [1]. When trying to pin some vCPU to CPU1 got error: >> xl vcpu-pin testvm 1 1 >> libxl: error: libxl.c:2565:libxl_set_vcpuaffinity setting vcpu affinity: >> Invalid argument >> >> What went wrong? How can I reenable CPU1-CPU3? > > According to the "xl dmesg" output you sent, CPU1-3 are all > online (their presence in the output following "Dumping timer > queues:" confirms this). So I suppose you will need to go do > some debugging to find out where and why the set-affinity > operation fails, and/or why the scheduler puts everything on > a single pCPU (if it really does, the output of "xl vcpu-list" is > only a hint towards that). Rather than using ''c'', ''r'' might have > been the more useful debug key.That was the rare case when resume worked at all... in most cased I''ve got reboot, before anything appear on the screen (even backlight is off) - xen panic? dom0 kernel panic? I''ve already rebooted the system, will try above debug key next time. I don''t have serial console, but have USB-to-serial port - is it possible to use it as xen console (in xen 4.1.3)? -- Best Regards / Pozdrawiam, Marek Marczykowski Invisible Things Lab _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
>>> Marek Marczykowski <marmarek@invisiblethingslab.com> 11/30/12 5:07 PM >>> >That was the rare case when resume worked at all... in most cased I''ve got >reboot, before anything appear on the screen (even backlight is off) - xen >panic? dom0 kernel panic?Without serial console we won''t get very far from here.>I don''t have serial console, but have USB-to-serial port - is it possible to >use it as xen console (in xen 4.1.3)?Not that I''m aware of. But 4.1.x isn''t very interesting from a development perspective anyway. If you had the same problems still with 4.3-unstable, then that''s be of much more interest to analyze, and you could use the EHCI debug port (if one of your controllers has one) based serial console. Jan
On 30.11.2012 17:12, Jan Beulich wrote:>>>> Marek Marczykowski <marmarek@invisiblethingslab.com> 11/30/12 5:07 PM >>> >> That was the rare case when resume worked at all... in most cased I''ve got >> reboot, before anything appear on the screen (even backlight is off) - xen >> panic? dom0 kernel panic? > > Without serial console we won''t get very far from here. > >> I don''t have serial console, but have USB-to-serial port - is it possible to >> use it as xen console (in xen 4.1.3)? > > Not that I''m aware of. But 4.1.x isn''t very interesting from a development > perspective anyway. If you had the same problems still with 4.3-unstable, > then that''s be of much more interest to analyze, and you could use the > EHCI debug port (if one of your controllers has one) based serial console.Is it possible to use libxl from xen 4.1 with newer hypervisor? My libxl is somehow patched and porting it to newer version will require some effort. -- Best Regards / Pozdrawiam, Marek Marczykowski Invisible Things Lab _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Thu, Nov 29, 2012 at 07:55:06PM +0100, Marek Marczykowski wrote:> Hi all, > > After resume from ACPI S3 system has only CPU0 enabled, every vCPU from every > domain works on CPU0 [1]. When trying to pin some vCPU to CPU1 got error: > xl vcpu-pin testvm 1 1 > libxl: error: libxl.c:2565:libxl_set_vcpuaffinity setting vcpu affinity: > Invalid argument > > What went wrong? How can I reenable CPU1-CPU3?I think Ben had found some issues with this in the past? CC-ing him here.> > System info: > xen 4.1.3 > linux 3.4.18 with acpi-s3 patches from Konrad''s git > Processor: Intel i5-2520M > > dmesg from dom0 and hypervisor attached. > > BTW Are there any plans to upstream acpi-s3 patches? > > [1] xl vcpu-list: > Name ID VCPU CPU State Time(s) CPU Affinity > dom0 0 0 0 r-- 1347.8 any cpu > dom0 0 1 0 -b- 594.4 any cpu > dom0 0 2 0 -b- 421.1 any cpu > dom0 0 3 0 -b- 432.6 any cpu > netvm 1 0 0 -b- 596.6 any cpu > netvm 1 1 0 -b- 363.7 any cpu > firewallvm 2 0 0 -b- 170.5 any cpu > firewallvm 2 1 0 -b- 122.5 any cpu > devel17 3 0 0 -b- 137.0 any cpu > devel17 3 1 0 -b- 112.9 any cpu > devel17 3 2 0 -b- 97.9 any cpu > devel17 3 3 0 -b- 116.0 any cpu > vm2 4 0 0 -b- 418.6 any cpu > vm2 4 1 0 -b- 390.2 any cpu > private 5 0 0 -b- 175.9 any cpu > private 5 1 0 -b- 161.6 any cpu > mail 6 0 0 -b- 1587.1 any cpu > mail 6 1 0 -b- 1717.5 any cpu > testvm 7 0 0 -b- 73.0 any cpu > testvm 7 1 0 -b- 68.9 any cpu > testvm 7 2 0 -b- 51.4 any cpu > testvm 7 3 0 -b- 67.1 any cpu > disp1 8 0 0 -b- 199.9 any cpu > > > -- > Best Regards / Pozdrawiam, > Marek Marczykowski > Invisible Things Lab> [ 0.000000] Initializing cgroup subsys cpuset > [ 0.000000] Initializing cgroup subsys cpu > [ 0.000000] Linux version 3.4.18-2.pvops.qubes.x86_64 (user@nemezis.marmarek.net) (gcc version 4.4.5 20101112 (Red Hat 4.4.5-2) (GCC) ) #1 SMP Wed Nov 7 22:47:21 EST 2012 > [ 0.000000] Command line: ro root=/dev/mapper/vg_dom0-lv_root rd_LUKS_UUID=luks-400336fa-c7c4-4be3-a244-c909aa16a18c rd_LVM_LV=vg_dom0/lv_root rd_LVM_LV=vg_dom0/lv_swap rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=pl2 rhgb quiet max_loop=255 > [ 0.000000] Freeing 9a-100 pfn range: 102 pages freed > [ 0.000000] 1-1 mapping on 9a->100 > [ 0.000000] Freeing 7eea-7f67 pfn range: 125 pages freed > [ 0.000000] 1-1 mapping on 7eea->7f67 > [ 0.000000] Freeing 7f70-7f76 pfn range: 6 pages freed > [ 0.000000] 1-1 mapping on 7f70->7f76 > [ 0.000000] Freeing 7f78-8000 pfn range: 136 pages freed > [ 0.000000] 1-1 mapping on 7f78->8000 > [ 0.000000] Freeing dffd-e000 pfn range: 3 pages freed > [ 0.000000] 1-1 mapping on dffd->e000 > [ 0.000000] Freeing 20000-20200 pfn range: 512 pages freed > [ 0.000000] 1-1 mapping on 20000->20200 > [ 0.000000] Freeing 40000-40200 pfn range: 512 pages freed > [ 0.000000] 1-1 mapping on 40000->40200 > [ 0.000000] Freeing c83b4-c840a pfn range: 86 pages freed > [ 0.000000] 1-1 mapping on c83b4->c840a > [ 0.000000] Freeing c840e-c840f pfn range: 1 pages freed > [ 0.000000] 1-1 mapping on c840e->c840f > [ 0.000000] Freeing c8411-c8414 pfn range: 3 pages freed > [ 0.000000] 1-1 mapping on c8411->c8414 > [ 0.000000] Freeing c841e-c8428 pfn range: 10 pages freed > [ 0.000000] 1-1 mapping on c841e->c8428 > [ 0.000000] Freeing c8432-c8436 pfn range: 4 pages freed > [ 0.000000] 1-1 mapping on c8432->c8436 > [ 0.000000] Freeing cac00-100000 pfn range: 218112 pages freed > [ 0.000000] 1-1 mapping on cac00->100000 > [ 0.000000] Released 219612 pages of unused memory > [ 0.000000] Set 219612 page(s) to 1-1 mapping > [ 0.000000] BIOS-provided physical RAM map: > [ 0.000000] Xen: 0000000000000000 - 000000000009a000 (usable) > [ 0.000000] Xen: 000000000009a800 - 0000000000100000 (reserved) > [ 0.000000] Xen: 0000000000100000 - 0000000007eea000 (usable) > [ 0.000000] Xen: 0000000007eea000 - 0000000007f67000 (ACPI NVS) > [ 0.000000] Xen: 0000000007f67000 - 0000000007f70000 (usable) > [ 0.000000] Xen: 0000000007f70000 - 0000000007f76000 (ACPI NVS) > [ 0.000000] Xen: 0000000007f76000 - 0000000007f78000 (usable) > [ 0.000000] Xen: 0000000007f78000 - 0000000008000000 (ACPI NVS) > [ 0.000000] Xen: 0000000008000000 - 000000000dffd000 (usable) > [ 0.000000] Xen: 000000000dffd000 - 000000000e000000 (ACPI data) > [ 0.000000] Xen: 000000000e000000 - 0000000020000000 (usable) > [ 0.000000] Xen: 0000000020000000 - 0000000020200000 (reserved) > [ 0.000000] Xen: 0000000020200000 - 0000000040000000 (usable) > [ 0.000000] Xen: 0000000040000000 - 0000000040200000 (reserved) > [ 0.000000] Xen: 0000000040200000 - 00000000c83b4000 (usable) > [ 0.000000] Xen: 00000000c83b4000 - 00000000c840a000 (reserved) > [ 0.000000] Xen: 00000000c840a000 - 00000000c840e000 (usable) > [ 0.000000] Xen: 00000000c840e000 - 00000000c840f000 (reserved) > [ 0.000000] Xen: 00000000c840f000 - 00000000c8411000 (usable) > [ 0.000000] Xen: 00000000c8411000 - 00000000c8414000 (reserved) > [ 0.000000] Xen: 00000000c8414000 - 00000000c841e000 (usable) > [ 0.000000] Xen: 00000000c841e000 - 00000000c8428000 (reserved) > [ 0.000000] Xen: 00000000c8428000 - 00000000c8432000 (usable) > [ 0.000000] Xen: 00000000c8432000 - 00000000c8436000 (reserved) > [ 0.000000] Xen: 00000000c8436000 - 00000000cac00000 (usable) > [ 0.000000] Xen: 00000000cb800000 - 00000000cfa00000 (reserved) > [ 0.000000] Xen: 00000000fec00000 - 00000000fec01000 (reserved) > [ 0.000000] Xen: 00000000fed1c000 - 00000000fed20000 (reserved) > [ 0.000000] Xen: 00000000fee00000 - 00000000fee01000 (reserved) > [ 0.000000] Xen: 00000000ffc00000 - 00000000ffc20000 (reserved) > [ 0.000000] Xen: 0000000100000000 - 000000042e000000 (usable) > [ 0.000000] NX (Execute Disable) protection: active > [ 0.000000] DMI 2.6 present. > [ 0.000000] DMI: Dell Inc. Latitude E6420/0K0DNP, BIOS A13 05/17/2012 > [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved) > [ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable) > [ 0.000000] No AGP bridge found > [ 0.000000] last_pfn = 0x42e000 max_arch_pfn = 0x400000000 > [ 0.000000] x2apic enabled by BIOS, switching to x2apic ops > [ 0.000000] last_pfn = 0xcac00 max_arch_pfn = 0x400000000 > [ 0.000000] found SMP MP-table at [ffff8800000f1ad0] f1ad0 > [ 0.000000] initial memory mapped : 0 - 04ade000 > [ 0.000000] Base memory trampoline at [ffff880000095000] 95000 size 20480 > [ 0.000000] init_memory_mapping: 0000000000000000-00000000cac00000 > [ 0.000000] 0000000000 - 00cac00000 page 4k > [ 0.000000] kernel direct mapping tables up to 0xcabfffff @ [mem 0x009a5000-0x00ffffff] > [ 0.000000] xen: setting RW the range fc4000 - 1000000 > [ 0.000000] init_memory_mapping: 0000000100000000-000000042e000000 > [ 0.000000] 0100000000 - 042e000000 page 4k > [ 0.000000] kernel direct mapping tables up to 0x42dffffff @ [mem 0xc9282000-0xcabfffff] > [ 0.000000] xen: setting RW the range cabff000 - cac00000 > [ 0.000000] RAMDISK: 01e13000 - 04ade000 > [ 0.000000] ACPI: RSDP 00000000000fe300 00024 (v02 DELL ) > [ 0.000000] ACPI: XSDT 000000000dffee18 0007C (v01 DELL CBX3 06222004 MSFT 00010013) > [ 0.000000] ACPI: FACP 0000000007f90d98 000F4 (v04 DELL CBX3 06222004 MSFT 00010013) > [ 0.000000] ACPI Warning: 32/64 FACS address mismatch in FADT - two FACS tables! (20120320/tbfadt-378) > [ 0.000000] ACPI Warning: 32/64X FACS address mismatch in FADT - 0x07FEDE40/0x0000000007FEDD40, using 32 (20120320/tbfadt-502) > [ 0.000000] ACPI: DSDT 0000000007f5e018 08834 (v02 INT430 SYSFexxx 00001001 INTL 20090903) > [ 0.000000] ACPI: FACS 0000000007fede40 00040 > [ 0.000000] ACPI: APIC 000000000dffdf18 000CC (v02 DELL CBX3 06222004 MSFT 00010013) > [ 0.000000] ACPI: TCPA 0000000007feed18 00032 (v02 00000000 00000000) > [ 0.000000] ACPI: SSDT 0000000007f91a98 002F9 (v01 DELLTP TPM 00003000 INTL 20090903) > [ 0.000000] ACPI: MCFG 0000000007feec98 0003C (v01 DELL SNDYBRDG 06222004 MSFT 00000097) > [ 0.000000] ACPI: HPET 0000000007feec18 00038 (v01 A M I PCHHPET 06222004 AMI. 00000003) > [ 0.000000] ACPI: BOOT 0000000007feeb98 00028 (v01 DELL CBX3 06222004 AMI 00010013) > [ 0.000000] ACPI: SSDT 0000000007f75018 00804 (v01 PmRef Cpu0Ist 00003000 INTL 20090903) > [ 0.000000] ACPI: SSDT 0000000007f74018 00996 (v01 PmRef CpuPm 00003000 INTL 20090903) > [ 0.000000] ACPI: XMAR 0000000007f90c18 000E8 (v01 INTEL SNB 00000001 INTL 00000001) > [ 0.000000] ACPI: SLIC 0000000007f7ec18 00176 (v03 DELL CBX3 06222004 MSFT 00010013) > [ 0.000000] ACPI: Local APIC address 0xfee00000 > [ 0.000000] Setting APIC routing to cluster x2apic. > [ 0.000000] Zone PFN ranges: > [ 0.000000] DMA 0x00000010 -> 0x00001000 > [ 0.000000] DMA32 0x00001000 -> 0x00100000 > [ 0.000000] Normal 0x00100000 -> 0x0042e000 > [ 0.000000] Movable zone start PFN for each node > [ 0.000000] Early memory PFN ranges > [ 0.000000] 0: 0x00000010 -> 0x0000009a > [ 0.000000] 0: 0x00000100 -> 0x00007eea > [ 0.000000] 0: 0x00007f67 -> 0x00007f70 > [ 0.000000] 0: 0x00007f76 -> 0x00007f78 > [ 0.000000] 0: 0x00008000 -> 0x0000dffd > [ 0.000000] 0: 0x0000e000 -> 0x00020000 > [ 0.000000] 0: 0x00020200 -> 0x00040000 > [ 0.000000] 0: 0x00040200 -> 0x000c83b4 > [ 0.000000] 0: 0x000c840a -> 0x000c840e > [ 0.000000] 0: 0x000c840f -> 0x000c8411 > [ 0.000000] 0: 0x000c8414 -> 0x000c841e > [ 0.000000] 0: 0x000c8428 -> 0x000c8432 > [ 0.000000] 0: 0x000c8436 -> 0x000cac00 > [ 0.000000] 0: 0x00100000 -> 0x0042e000 > [ 0.000000] On node 0 totalpages: 4163092 > [ 0.000000] DMA zone: 56 pages used for memmap > [ 0.000000] DMA zone: 1572 pages reserved > [ 0.000000] DMA zone: 2350 pages, LIFO batch:0 > [ 0.000000] DMA32 zone: 14280 pages used for memmap > [ 0.000000] DMA32 zone: 810690 pages, LIFO batch:31 > [ 0.000000] Normal zone: 45584 pages used for memmap > [ 0.000000] Normal zone: 3288560 pages, LIFO batch:31 > [ 0.000000] ACPI: PM-Timer IO Port: 0x408 > [ 0.000000] ACPI: Local APIC address 0xfee00000 > [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] disabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] disabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x06] disabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] disabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x08] disabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x09] disabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0a] disabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x0b] disabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x0c] disabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x0d] disabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x0e] disabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x0f] disabled) > [ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) > [ 0.000000] IOAPIC[0]: apic_id 2, version 253, address 0xfec00000, GSI 0-253 > [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) > [ 0.000000] ACPI: IRQ0 used by override. > [ 0.000000] ACPI: IRQ2 used by override. > [ 0.000000] ACPI: IRQ9 used by override. > [ 0.000000] Using ACPI (MADT) for SMP configuration information > [ 0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000 > [ 0.000000] SMP: Allowing 16 CPUs, 12 hotplug CPUs > [ 0.000000] nr_irqs_gsi: 270 > [ 0.000000] Allocating PCI resources starting at cfa00000 (gap: cfa00000:2f200000) > [ 0.000000] Booting paravirtualized kernel on Xen > [ 0.000000] Xen version: 4.1.3 (preserve-AD) > [ 0.000000] setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:16 nr_node_ids:1 > [ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff8803e2800000 s82176 r8192 d24320 u131072 > [ 0.000000] pcpu-alloc: s82176 r8192 d24320 u131072 alloc=1*2097152 > [ 0.000000] pcpu-alloc: [0] 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 > [ 4.119805] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 4101600 > [ 4.119809] Kernel command line: ro root=/dev/mapper/vg_dom0-lv_root rd_LUKS_UUID=luks-400336fa-c7c4-4be3-a244-c909aa16a18c rd_LVM_LV=vg_dom0/lv_root rd_LVM_LV=vg_dom0/lv_swap rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=pl2 rhgb quiet max_loop=255 > [ 4.119915] PID hash table entries: 4096 (order: 3, 32768 bytes) > [ 4.120928] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes) > [ 4.124018] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes) > [ 4.147064] Placing 64MB software IO TLB between ffff8803ce200000 - ffff8803d2200000 > [ 4.147066] software IO TLB at phys 0x3ce200000 - 0x3d2200000 > [ 4.181675] Memory: 14975940k/17530880k available (4557k kernel code, 878512k absent, 1676428k reserved, 4112k data, 552k init) > [ 4.181730] Hierarchical RCU implementation. > [ 4.181731] RCU dyntick-idle grace-period acceleration is enabled. > [ 4.181738] NR_IRQS:33024 nr_irqs:1024 16 > [ 4.181799] xen: sci override: global_irq=9 trigger=0 polarity=0 > [ 4.181801] xen: registering gsi 9 triggering 0 polarity 0 > [ 4.181809] xen: --> pirq=9 -> irq=9 (gsi=9) > [ 4.181829] xen: acpi sci 9 > [ 4.181831] xen: --> pirq=1 -> irq=1 (gsi=1) > [ 4.181834] xen: --> pirq=2 -> irq=2 (gsi=2) > [ 4.181836] xen: --> pirq=3 -> irq=3 (gsi=3) > [ 4.181838] xen: --> pirq=4 -> irq=4 (gsi=4) > [ 4.181840] xen: --> pirq=5 -> irq=5 (gsi=5) > [ 4.181843] xen: --> pirq=6 -> irq=6 (gsi=6) > [ 4.181845] xen: --> pirq=7 -> irq=7 (gsi=7) > [ 4.181847] xen: --> pirq=8 -> irq=8 (gsi=8) > [ 4.181849] xen: --> pirq=10 -> irq=10 (gsi=10) > [ 4.181851] xen: --> pirq=11 -> irq=11 (gsi=11) > [ 4.181854] xen: --> pirq=12 -> irq=12 (gsi=12) > [ 4.181856] xen: --> pirq=13 -> irq=13 (gsi=13) > [ 4.181858] xen: --> pirq=14 -> irq=14 (gsi=14) > [ 4.181860] xen: --> pirq=15 -> irq=15 (gsi=15) > [ 4.182986] Console: colour VGA+ 80x25 > [ 4.183012] console [tty0] enabled > [ 4.183026] Xen: using vcpuop timer interface > [ 4.183030] installing Xen timer for CPU 0 > [ 4.183048] Detected 2494.416 MHz processor. > [ 4.183052] Calibrating delay loop (skipped), value calculated using timer frequency.. 4988.83 BogoMIPS (lpj=9977664) > [ 4.183054] pid_max: default: 32768 minimum: 301 > [ 4.183090] Mount-cache hash table entries: 256 > [ 4.183222] Initializing cgroup subsys cpuacct > [ 4.183224] Initializing cgroup subsys devices > [ 4.183225] Initializing cgroup subsys freezer > [ 4.183227] Initializing cgroup subsys net_cls > [ 4.183228] Initializing cgroup subsys blkio > [ 4.183280] ENERGY_PERF_BIAS: Set to ''normal'', was ''performance'' > [ 4.183281] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8) > [ 4.183284] CPU: Physical Processor ID: 0 > [ 4.183285] CPU: Processor Core ID: 0 > [ 4.184454] ACPI: Core revision 20120320 > [ 4.194658] Performance Events: unsupported p6 CPU model 42 no PMU driver, software events only. > [ 4.194796] installing Xen timer for CPU 1 > [ 4.194988] installing Xen timer for CPU 2 > [ 4.195140] installing Xen timer for CPU 3 > [ 4.195232] Brought up 4 CPUs > [ 4.195477] devtmpfs: initialized > [ 4.199046] PM: Registering ACPI NVS region [mem 0x07eea000-0x07f66fff] (512000 bytes) > [ 4.199056] PM: Registering ACPI NVS region [mem 0x07f70000-0x07f75fff] (24576 bytes) > [ 4.199058] PM: Registering ACPI NVS region [mem 0x07f78000-0x07ffffff] (557056 bytes) > [ 4.199069] Dell Latitude E6420 series board detected. Selecting PCI-method for reboots. > [ 4.199104] Grant tables using version 2 layout. > [ 4.199114] Grant table initialized > [ 4.199158] dummy: > [ 4.199205] RTC time: 1:19:35, date: 11/29/12 > [ 4.199256] NET: Registered protocol family 16 > [ 4.199465] ACPI FADT declares the system doesn''t support PCIe ASPM, so disable it > [ 4.199467] ACPI: bus type pci registered > [ 4.199548] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000) > [ 4.199550] PCI: not using MMCONFIG > [ 4.199552] PCI: Using configuration type 1 for base access > [ 4.199559] dmi type 0xB1 record - unknown flag > [ 4.200155] bio: create slab <bio-0> at 0 > [ 4.200279] ACPI: Added _OSI(Module Device) > [ 4.200280] ACPI: Added _OSI(Processor Device) > [ 4.200282] ACPI: Added _OSI(3.0 _SCP Extensions) > [ 4.200283] ACPI: Added _OSI(Processor Aggregator Device) > [ 4.201815] ACPI: EC: Look up EC in DSDT > [ 4.206932] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored > [ 4.219266] ACPI: SSDT 00000000c8412798 00727 (v01 PmRef Cpu0Cst 00003001 INTL 20090903) > [ 4.219654] ACPI: Dynamic OEM Table Load: > [ 4.219657] ACPI: SSDT (null) 00727 (v01 PmRef Cpu0Cst 00003001 INTL 20090903) > [ 4.220118] ACPI: SSDT 00000000c8413a98 00303 (v01 PmRef ApIst 00003000 INTL 20090903) > [ 4.220555] ACPI: Dynamic OEM Table Load: > [ 4.220558] ACPI: SSDT (null) 00303 (v01 PmRef ApIst 00003000 INTL 20090903) > [ 4.220754] ACPI: SSDT 00000000c8411d98 00119 (v01 PmRef ApCst 00003000 INTL 20090903) > [ 4.221136] ACPI: Dynamic OEM Table Load: > [ 4.221138] ACPI: SSDT (null) 00119 (v01 PmRef ApCst 00003000 INTL 20090903) > [ 4.223275] ACPI: Interpreter enabled > [ 4.223278] ACPI: (supports S0 S3 S5) > [ 4.223294] ACPI: Using IOAPIC for interrupt routing > [ 4.223322] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000) > [ 4.223846] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in ACPI motherboard resources > [ 4.271283] ACPI: EC: GPE = 0x10, I/O: command/status = 0x934, data = 0x930 > [ 4.272424] ACPI: No dock devices found. > [ 4.272428] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug > [ 4.272988] \_SB_.PCI0:_OSC invalid UUID > [ 4.272989] _OSC request data:1 8 1f > [ 4.272992] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e]) > [ 4.273994] pci_root PNP0A08:00: host bridge window [io 0x0000-0x0cf7] > [ 4.273996] pci_root PNP0A08:00: host bridge window [io 0x0d00-0xffff] > [ 4.273998] pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff] > [ 4.274001] pci_root PNP0A08:00: host bridge window [mem 0xcfa00000-0xfeafffff] > [ 4.274003] pci_root PNP0A08:00: host bridge window [mem 0xfed40000-0xfed44fff] > [ 4.274031] PCI host bridge to bus 0000:00 > [ 4.274033] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7] > [ 4.274034] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff] > [ 4.274036] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff] > [ 4.274038] pci_bus 0000:00: root bus resource [mem 0xcfa00000-0xfeafffff] > [ 4.274040] pci_bus 0000:00: root bus resource [mem 0xfed40000-0xfed44fff] > [ 4.274054] pci 0000:00:00.0: [8086:0104] type 00 class 0x060000 > [ 4.274147] pci 0000:00:02.0: [8086:0126] type 00 class 0x030000 > [ 4.274174] pci 0000:00:02.0: reg 10: [mem 0xe1400000-0xe17fffff 64bit] > [ 4.274189] pci 0000:00:02.0: reg 18: [mem 0xd0000000-0xdfffffff 64bit pref] > [ 4.274200] pci 0000:00:02.0: reg 20: [io 0x4000-0x403f] > [ 4.274344] pci 0000:00:16.0: [8086:1c3a] type 00 class 0x078000 > [ 4.274394] pci 0000:00:16.0: reg 10: [mem 0xe2eb0000-0xe2eb000f 64bit] > [ 4.274563] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold > [ 4.274636] pci 0000:00:19.0: [8086:1502] type 00 class 0x020000 > [ 4.274681] pci 0000:00:19.0: reg 10: [mem 0xe2e00000-0xe2e1ffff] > [ 4.274700] pci 0000:00:19.0: reg 14: [mem 0xe2e80000-0xe2e80fff] > [ 4.274719] pci 0000:00:19.0: reg 18: [io 0x4080-0x409f] > [ 4.274883] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold > [ 4.274939] pci 0000:00:1a.0: [8086:1c2d] type 00 class 0x0c0320 > [ 4.274983] pci 0000:00:1a.0: reg 10: [mem 0xe2e70000-0xe2e703ff] > [ 4.275185] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold > [ 4.275243] pci 0000:00:1b.0: [8086:1c20] type 00 class 0x040300 > [ 4.275278] pci 0000:00:1b.0: reg 10: [mem 0xe2e60000-0xe2e63fff 64bit] > [ 4.275456] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold > [ 4.275509] pci 0000:00:1c.0: [8086:1c10] type 01 class 0x060400 > [ 4.275702] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold > [ 4.275760] pci 0000:00:1c.1: [8086:1c12] type 01 class 0x060400 > [ 4.275953] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold > [ 4.276011] pci 0000:00:1c.2: [8086:1c14] type 01 class 0x060400 > [ 4.276205] pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold > [ 4.276264] pci 0000:00:1c.3: [8086:1c16] type 01 class 0x060400 > [ 4.276458] pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold > [ 4.276520] pci 0000:00:1c.5: [8086:1c1a] type 01 class 0x060400 > [ 4.276711] pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold > [ 4.276779] pci 0000:00:1d.0: [8086:1c26] type 00 class 0x0c0320 > [ 4.276823] pci 0000:00:1d.0: reg 10: [mem 0xe2e50000-0xe2e503ff] > [ 4.277025] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold > [ 4.277086] pci 0000:00:1f.0: [8086:1c4f] type 00 class 0x060100 > [ 4.277341] pci 0000:00:1f.2: [8086:1c03] type 00 class 0x010601 > [ 4.277391] pci 0000:00:1f.2: reg 10: [io 0x40d0-0x40d7] > [ 4.277410] pci 0000:00:1f.2: reg 14: [io 0x40c0-0x40c3] > [ 4.277429] pci 0000:00:1f.2: reg 18: [io 0x40b0-0x40b7] > [ 4.277449] pci 0000:00:1f.2: reg 1c: [io 0x40a0-0x40a3] > [ 4.277468] pci 0000:00:1f.2: reg 20: [io 0x4060-0x407f] > [ 4.277486] pci 0000:00:1f.2: reg 24: [mem 0xe2e40000-0xe2e407ff] > [ 4.277613] pci 0000:00:1f.2: PME# supported from D3hot > [ 4.277657] pci 0000:00:1f.3: [8086:1c22] type 00 class 0x0c0500 > [ 4.277694] pci 0000:00:1f.3: reg 10: [mem 0xe2e30000-0xe2e300ff 64bit] > [ 4.277749] pci 0000:00:1f.3: reg 20: [io 0x4040-0x405f] > [ 4.277920] pci 0000:00:1c.0: PCI bridge to [bus 01-01] > [ 4.278353] pci 0000:02:00.0: [8086:422b] type 00 class 0x028000 > [ 4.278708] pci 0000:02:00.0: reg 10: [mem 0xe2d00000-0xe2d01fff 64bit] > [ 4.280508] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold > [ 4.285361] pci 0000:00:1c.1: PCI bridge to [bus 02-02] > [ 4.285374] pci 0000:00:1c.1: bridge window [mem 0xe2d00000-0xe2dfffff] > [ 4.285490] pci 0000:00:1c.2: PCI bridge to [bus 03-08] > [ 4.285498] pci 0000:00:1c.2: bridge window [io 0x3000-0x3fff] > [ 4.285505] pci 0000:00:1c.2: bridge window [mem 0xe2200000-0xe2bfffff] > [ 4.285517] pci 0000:00:1c.2: bridge window [mem 0xe0a00000-0xe13fffff 64bit pref] > [ 4.285625] pci 0000:00:1c.3: PCI bridge to [bus 09-09] > [ 4.285632] pci 0000:00:1c.3: bridge window [io 0x2000-0x2fff] > [ 4.285639] pci 0000:00:1c.3: bridge window [mem 0xe1800000-0xe21fffff] > [ 4.285651] pci 0000:00:1c.3: bridge window [mem 0xe0000000-0xe09fffff 64bit pref] > [ 4.285818] pci 0000:0a:00.0: [1217:8221] type 00 class 0x080501 > [ 4.285872] pci 0000:0a:00.0: reg 10: [mem 0xe2c20000-0xe2c201ff] > [ 4.286294] pci 0000:0a:00.0: supports D1 D2 > [ 4.286295] pci 0000:0a:00.0: PME# supported from D0 D1 D2 D3hot D3cold > [ 4.286432] pci 0000:0a:00.1: [1217:8231] type 00 class 0x018000 > [ 4.286486] pci 0000:0a:00.1: reg 10: [mem 0xe2c10000-0xe2c10fff] > [ 4.286563] pci 0000:0a:00.1: reg 18: [mem 0xe2c00000-0xe2c007ff] > [ 4.286908] pci 0000:0a:00.1: supports D1 D2 > [ 4.286909] pci 0000:0a:00.1: PME# supported from D0 D1 D2 D3hot D3cold > [ 4.293400] pci 0000:00:1c.5: PCI bridge to [bus 0a-0a] > [ 4.293412] pci 0000:00:1c.5: bridge window [mem 0xe2c00000-0xe2cfffff] > [ 4.293479] pci_bus 0000:00: on NUMA node 0 > [ 4.293483] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] > [ 4.293612] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT] > [ 4.293647] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP02._PRT] > [ 4.293682] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP04._PRT] > [ 4.293717] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP06._PRT] > [ 4.293762] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP03._PRT] > [ 4.293857] \_SB_.PCI0:_OSC invalid UUID > [ 4.293858] _OSC request data:1 1f 1f > [ 4.293861] pci0000:00: Requesting ACPI _OSC control (0x1d) > [ 4.293906] \_SB_.PCI0:_OSC invalid UUID > [ 4.293907] _OSC request data:1 0 1d > [ 4.293910] pci0000:00: ACPI _OSC request failed (AE_ERROR), returned control mask: 0x1d > [ 4.293911] ACPI _OSC control for PCIe not granted, disabling ASPM > [ 4.297639] ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 12 14 15) *11 > [ 4.297702] ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 11 12 14 15) *10 > [ 4.297761] ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 12 14 15) *11 > [ 4.297820] ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 11 12 14 15) *10 > [ 4.297878] ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 *5 6 7 10 12 14 15) > [ 4.297937] ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 11 12 14 15) *0, disabled. > [ 4.297996] ACPI: PCI Interrupt Link [LNKG] (IRQs 1 *3 4 5 6 7 10 12 14 15) > [ 4.298054] ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 7 11 12 14 15) *0, disabled. > [ 4.298087] xen/balloon: Initialising balloon driver. > [ 4.301022] xen-balloon: Initialising balloon driver. > [ 4.301062] xen/balloon: Xen selfballooning driver disabled for domain0. > [ 4.301148] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none > [ 4.301157] vgaarb: loaded > [ 4.301157] vgaarb: bridge control possible 0000:00:02.0 > [ 4.301279] PCI: Using ACPI for IRQ routing > [ 4.305930] PCI: pci_cache_line_size set to 64 bytes > [ 4.306106] reserve RAM buffer: 000000000009a000 - 000000000009ffff > [ 4.306108] reserve RAM buffer: 0000000007eea000 - 0000000007ffffff > [ 4.306110] reserve RAM buffer: 0000000007f70000 - 0000000007ffffff > [ 4.306112] reserve RAM buffer: 0000000007f78000 - 0000000007ffffff > [ 4.306113] reserve RAM buffer: 000000000dffd000 - 000000000fffffff > [ 4.306115] reserve RAM buffer: 00000000c83b4000 - 00000000cbffffff > [ 4.306118] reserve RAM buffer: 00000000c840e000 - 00000000cbffffff > [ 4.306121] reserve RAM buffer: 00000000c8411000 - 00000000cbffffff > [ 4.306123] reserve RAM buffer: 00000000c841e000 - 00000000cbffffff > [ 4.306125] reserve RAM buffer: 00000000c8432000 - 00000000cbffffff > [ 4.306127] reserve RAM buffer: 00000000cac00000 - 00000000cbffffff > [ 4.306129] reserve RAM buffer: 000000042e000000 - 000000042fffffff > [ 4.306235] Switching to clocksource xen > [ 4.307726] pnp: PnP ACPI init > [ 4.307738] ACPI: bus type pnp registered > [ 4.308287] pnp 00:00: [bus 00-3e] > [ 4.308289] pnp 00:00: [io 0x0000-0x0cf7 window] > [ 4.308291] pnp 00:00: [io 0x0cf8-0x0cff] > [ 4.308293] pnp 00:00: [io 0x0d00-0xffff window] > [ 4.308295] pnp 00:00: [mem 0x000a0000-0x000bffff window] > [ 4.308296] pnp 00:00: [mem 0x000c0000-0x000c3fff window] > [ 4.308298] pnp 00:00: [mem 0x000c4000-0x000c7fff window] > [ 4.308300] pnp 00:00: [mem 0x000c8000-0x000cbfff window] > [ 4.308301] pnp 00:00: [mem 0x000cc000-0x000cffff window] > [ 4.308303] pnp 00:00: [mem 0x000d0000-0x000d3fff window] > [ 4.308305] pnp 00:00: [mem 0x000d4000-0x000d7fff window] > [ 4.308307] pnp 00:00: [mem 0x000d8000-0x000dbfff window] > [ 4.308309] pnp 00:00: [mem 0x000dc000-0x000dffff window] > [ 4.308310] pnp 00:00: [mem 0x000e0000-0x000e3fff window] > [ 4.308312] pnp 00:00: [mem 0x000e4000-0x000e7fff window] > [ 4.308314] pnp 00:00: [mem 0x000e8000-0x000ebfff window] > [ 4.308315] pnp 00:00: [mem 0x000ec000-0x000effff window] > [ 4.308317] pnp 00:00: [mem 0x000f0000-0x000fffff window] > [ 4.308319] pnp 00:00: [mem 0xcfa00000-0xfeafffff window] > [ 4.308320] pnp 00:00: [mem 0xfed40000-0xfed44fff window] > [ 4.308385] pnp 00:00: Plug and Play ACPI device, IDs PNP0a08 PNP0a03 (active) > [ 4.308398] pnp 00:01: [io 0x0000-0x001f] > [ 4.308400] pnp 00:01: [io 0x0081-0x0091] > [ 4.308401] pnp 00:01: [io 0x0093-0x009f] > [ 4.308403] pnp 00:01: [io 0x00c0-0x00df] > [ 4.308404] pnp 00:01: [dma 4] > [ 4.308422] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active) > [ 4.308429] pnp 00:02: [mem 0xff000000-0xffffffff] > [ 4.308445] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active) > [ 4.308540] pnp 00:03: [mem 0xfed00000-0xfed003ff] > [ 4.308572] system 00:03: [mem 0xfed00000-0xfed003ff] has been reserved > [ 4.308575] system 00:03: Plug and Play ACPI device, IDs PNP0103 PNP0c01 (active) > [ 4.308584] pnp 00:04: [io 0x00f0] > [ 4.308587] xen: registering gsi 13 triggering 1 polarity 0 > [ 4.308609] pnp 00:04: [irq 13] > [ 4.308626] pnp 00:04: Plug and Play ACPI device, IDs PNP0c04 (active) > [ 4.308636] pnp 00:05: [io 0x002e-0x002f] > [ 4.308637] pnp 00:05: [io 0x004e-0x004f] > [ 4.308639] pnp 00:05: [io 0x0061] > [ 4.308640] pnp 00:05: [io 0x0063] > [ 4.308641] pnp 00:05: [io 0x0065] > [ 4.308642] pnp 00:05: [io 0x0067] > [ 4.308644] pnp 00:05: [io 0x0070] > [ 4.308645] pnp 00:05: [io 0x0080] > [ 4.308646] pnp 00:05: [io 0x0092] > [ 4.308648] pnp 00:05: [io 0x00b2-0x00b3] > [ 4.308649] pnp 00:05: [io 0x0680-0x069f] > [ 4.308651] pnp 00:05: [io 0x1000-0x100f] > [ 4.308653] pnp 00:05: [io 0xffff] > [ 4.308654] pnp 00:05: [io 0xffff] > [ 4.308655] pnp 00:05: [io 0x0400-0x047f] > [ 4.308656] pnp 00:05: [io 0x0500-0x057f] > [ 4.308658] pnp 00:05: [io 0x164e-0x164f] > [ 4.308689] system 00:05: [io 0x0680-0x069f] has been reserved > [ 4.308691] system 00:05: [io 0x1000-0x100f] has been reserved > [ 4.308693] system 00:05: [io 0xffff] has been reserved > [ 4.308695] system 00:05: [io 0xffff] has been reserved > [ 4.308697] system 00:05: [io 0x0400-0x047f] has been reserved > [ 4.308700] system 00:05: [io 0x0500-0x057f] has been reserved > [ 4.308701] system 00:05: [io 0x164e-0x164f] has been reserved > [ 4.308704] system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active) > [ 4.308711] pnp 00:06: [io 0x0070-0x0077] > [ 4.308713] xen: registering gsi 8 triggering 1 polarity 0 > [ 4.308730] pnp 00:06: [irq 8] > [ 4.308749] pnp 00:06: Plug and Play ACPI device, IDs PNP0b00 (active) > [ 4.308758] pnp 00:07: [io 0x0060] > [ 4.308759] pnp 00:07: [io 0x0064] > [ 4.308761] xen: registering gsi 1 triggering 1 polarity 0 > [ 4.308777] pnp 00:07: [irq 1] > [ 4.308794] pnp 00:07: Plug and Play ACPI device, IDs PNP0303 (active) > [ 4.309984] pnp 00:08: Plug and Play ACPI device, IDs PNP0401 (disabled) > [ 4.309993] xen: registering gsi 12 triggering 1 polarity 0 > [ 4.310011] pnp 00:09: [irq 12] > [ 4.310030] pnp 00:09: Plug and Play ACPI device, IDs DLL0493 PNP0f13 (active) > [ 4.310065] pnp 00:0a: [mem 0xfed40000-0xfed44fff] > [ 4.310086] pnp 00:0a: Plug and Play ACPI device, IDs BCM0102 PNP0c31 (active) > [ 4.310291] pnp 00:0b: [mem 0xfed1c000-0xfed1ffff] > [ 4.310292] pnp 00:0b: [mem 0xfed10000-0xfed17fff] > [ 4.310294] pnp 00:0b: [mem 0xfed18000-0xfed18fff] > [ 4.310296] pnp 00:0b: [mem 0xfed19000-0xfed19fff] > [ 4.310298] pnp 00:0b: [mem 0xf8000000-0xfbffffff] > [ 4.310309] pnp 00:0b: [mem 0xfed20000-0xfed3ffff] > [ 4.310310] pnp 00:0b: [mem 0xfed90000-0xfed93fff] > [ 4.310312] pnp 00:0b: [mem 0xfed45000-0xfed8ffff] > [ 4.310313] pnp 00:0b: [mem 0xff000000-0xffffffff] > [ 4.310315] pnp 00:0b: [mem 0xfee00000-0xfeefffff] > [ 4.310317] pnp 00:0b: [mem 0x00000000-0xffffffffffffffff disabled] > [ 4.310318] pnp 00:0b: [mem 0x00000000-0xffffffffffffffff disabled] > [ 4.310359] system 00:0b: [mem 0xfed1c000-0xfed1ffff] has been reserved > [ 4.310361] system 00:0b: [mem 0xfed10000-0xfed17fff] has been reserved > [ 4.310363] system 00:0b: [mem 0xfed18000-0xfed18fff] has been reserved > [ 4.310365] system 00:0b: [mem 0xfed19000-0xfed19fff] has been reserved > [ 4.310367] system 00:0b: [mem 0xf8000000-0xfbffffff] has been reserved > [ 4.310369] system 00:0b: [mem 0xfed20000-0xfed3ffff] has been reserved > [ 4.310371] system 00:0b: [mem 0xfed90000-0xfed93fff] has been reserved > [ 4.310373] system 00:0b: [mem 0xfed45000-0xfed8ffff] has been reserved > [ 4.310375] system 00:0b: [mem 0xff000000-0xffffffff] could not be reserved > [ 4.310377] system 00:0b: [mem 0xfee00000-0xfeefffff] could not be reserved > [ 4.310380] system 00:0b: Plug and Play ACPI device, IDs PNP0c02 (active) > [ 4.310956] xen: registering gsi 23 triggering 1 polarity 0 > [ 4.310967] xen: --> pirq=23 -> irq=23 (gsi=23) > [ 4.310985] pnp 00:0c: [irq 23] > [ 4.311015] pnp 00:0c: Plug and Play ACPI device, IDs SMO8800 (active) > [ 4.315528] pnp 00:0d: [mem 0x20000000-0x201fffff] > [ 4.315531] pnp 00:0d: [mem 0x40000000-0x401fffff] > [ 4.339851] system 00:0d: [mem 0x20000000-0x201fffff] has been reserved > [ 4.339854] system 00:0d: [mem 0x40000000-0x401fffff] has been reserved > [ 4.339857] system 00:0d: Plug and Play ACPI device, IDs PNP0c01 (active) > [ 4.339865] pnp: PnP ACPI: found 14 devices > [ 4.339867] ACPI: ACPI bus type pnp unregistered > [ 4.346178] PM-Timer failed consistency check (0x0xffffff) - aborting. > [ 4.346274] pci 0000:00:1c.0: PCI bridge to [bus 01-01] > [ 4.346306] pci 0000:00:1c.1: PCI bridge to [bus 02-02] > [ 4.346315] pci 0000:00:1c.1: bridge window [mem 0xe2d00000-0xe2dfffff] > [ 4.346332] pci 0000:00:1c.2: PCI bridge to [bus 03-08] > [ 4.346336] pci 0000:00:1c.2: bridge window [io 0x3000-0x3fff] > [ 4.346347] pci 0000:00:1c.2: bridge window [mem 0xe2200000-0xe2bfffff] > [ 4.346354] pci 0000:00:1c.2: bridge window [mem 0xe0a00000-0xe13fffff 64bit pref] > [ 4.346366] pci 0000:00:1c.3: PCI bridge to [bus 09-09] > [ 4.346370] pci 0000:00:1c.3: bridge window [io 0x2000-0x2fff] > [ 4.346379] pci 0000:00:1c.3: bridge window [mem 0xe1800000-0xe21fffff] > [ 4.346386] pci 0000:00:1c.3: bridge window [mem 0xe0000000-0xe09fffff 64bit pref] > [ 4.346399] pci 0000:00:1c.5: PCI bridge to [bus 0a-0a] > [ 4.346408] pci 0000:00:1c.5: bridge window [mem 0xe2c00000-0xe2cfffff] > [ 4.346434] xen: registering gsi 16 triggering 0 polarity 1 > [ 4.346442] xen: --> pirq=16 -> irq=16 (gsi=16) > [ 4.346469] xen: registering gsi 17 triggering 0 polarity 1 > [ 4.346473] xen: --> pirq=17 -> irq=17 (gsi=17) > [ 4.346498] xen: registering gsi 18 triggering 0 polarity 1 > [ 4.346502] xen: --> pirq=18 -> irq=18 (gsi=18) > [ 4.346527] xen: registering gsi 19 triggering 0 polarity 1 > [ 4.346531] xen: --> pirq=19 -> irq=19 (gsi=19) > [ 4.346556] xen: registering gsi 17 triggering 0 polarity 1 > [ 4.346558] Already setup the GSI :17 > [ 4.346563] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7] > [ 4.346565] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff] > [ 4.346566] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff] > [ 4.346568] pci_bus 0000:00: resource 7 [mem 0xcfa00000-0xfeafffff] > [ 4.346570] pci_bus 0000:00: resource 8 [mem 0xfed40000-0xfed44fff] > [ 4.346572] pci_bus 0000:02: resource 1 [mem 0xe2d00000-0xe2dfffff] > [ 4.346574] pci_bus 0000:03: resource 0 [io 0x3000-0x3fff] > [ 4.346575] pci_bus 0000:03: resource 1 [mem 0xe2200000-0xe2bfffff] > [ 4.346577] pci_bus 0000:03: resource 2 [mem 0xe0a00000-0xe13fffff 64bit pref] > [ 4.346579] pci_bus 0000:09: resource 0 [io 0x2000-0x2fff] > [ 4.346581] pci_bus 0000:09: resource 1 [mem 0xe1800000-0xe21fffff] > [ 4.346582] pci_bus 0000:09: resource 2 [mem 0xe0000000-0xe09fffff 64bit pref] > [ 4.346584] pci_bus 0000:0a: resource 1 [mem 0xe2c00000-0xe2cfffff] > [ 4.346672] NET: Registered protocol family 2 > [ 4.346732] IP route cache hash table entries: 524288 (order: 10, 4194304 bytes) > [ 4.347207] TCP established hash table entries: 262144 (order: 10, 4194304 bytes) > [ 4.347753] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) > [ 4.347872] TCP: Hash tables configured (established 262144 bind 65536) > [ 4.347874] TCP: reno registered > [ 4.347877] UDP hash table entries: 8192 (order: 6, 262144 bytes) > [ 4.347921] UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes) > [ 4.348067] NET: Registered protocol family 1 > [ 4.348085] pci 0000:00:02.0: Boot video device > [ 4.348108] xen: registering gsi 16 triggering 0 polarity 1 > [ 4.348112] Already setup the GSI :16 > [ 4.348203] xen: registering gsi 17 triggering 0 polarity 1 > [ 4.348205] Already setup the GSI :17 > [ 4.348298] PCI: CLS 64 bytes, default 64 > [ 4.348333] Unpacking initramfs... > [ 4.384265] Freeing initrd memory: 45868k freed > [ 4.392440] Simple Boot Flag at 0xf3 set to 0x1 > [ 4.392900] audit: initializing netlink socket (disabled) > [ 4.392911] type=2000 audit(1354151975.383:1): initialized > [ 4.411688] VFS: Disk quotas dquot_6.5.2 > [ 4.411715] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) > [ 4.411870] msgmni has been set to 29339 > [ 4.412010] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) > [ 4.412013] io scheduler noop registered > [ 4.412015] io scheduler deadline registered > [ 4.412036] io scheduler cfq registered (default) > [ 4.412666] intel_idle: does not run on family 6 model 42 > [ 4.412741] ACPI: Requesting acpi_cpufreq > [ 4.459643] Non-volatile memory driver v1.3 > [ 4.459654] ramoops: platform device not found, using module parameters > [ 4.459670] ramoops: The memory size and the record size must be non-zero > [ 4.459703] ramoops: probe of ramoops failed with error -22 > [ 4.474892] loop: module loaded > [ 4.474922] Fixed MDIO Bus: probed > [ 4.474965] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 > [ 4.475166] i8042: Warning: Keylock active > [ 4.476434] serio: i8042 KBD port at 0x60,0x64 irq 1 > [ 4.476439] serio: i8042 AUX port at 0x60,0x64 irq 12 > [ 4.476551] mousedev: PS/2 mouse device common for all mice > [ 4.476707] rtc_cmos 00:06: RTC can wake from S4 > [ 4.476940] rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0 > [ 4.476998] rtc0: alarms up to one year, y3k, 242 bytes nvram > [ 4.477084] device-mapper: uevent: version 1.0.3 > [ 4.477193] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: dm-devel@redhat.com > [ 4.477281] TCP: cubic registered > [ 4.477381] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0 > [ 4.477402] NET: Registered protocol family 10 > [ 4.477644] Registering the dns_resolver key type > [ 4.477791] registered taskstats version 1 > [ 4.478330] Magic number: 4:584:307 > [ 4.478403] tty tty36: hash matches > [ 4.478496] rtc_cmos 00:06: setting system clock to 2012-11-29 01:19:35 UTC (1354151975) > [ 4.478801] Freeing unused kernel memory: 552k freed > [ 4.478847] Write protecting the kernel read-only data: 8192k > [ 4.481908] Freeing unused kernel memory: 1568k freed > [ 4.482112] Freeing unused kernel memory: 24k freed > [ 4.524129] dracut: dracut-005-3.fc13 > [ 4.552311] pciback 0000:00:19.0: seizing device > [ 4.552403] pciback 0000:02:00.0: seizing device > [ 4.552941] xen: registering gsi 17 triggering 0 polarity 1 > [ 4.552952] Already setup the GSI :17 > [ 4.553934] xen: registering gsi 20 triggering 0 polarity 1 > [ 4.553964] xen: --> pirq=20 -> irq=20 (gsi=20) > [ 4.554574] xen-pciback: backend is vpci > [ 4.617471] udev: starting version 151 > [ 4.617770] udevd (80): /proc/80/oom_adj is deprecated, please use /proc/80/oom_score_adj instead. > [ 4.654916] Linux agpgart interface v0.103 > [ 4.655397] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input1 > [ 5.051184] ACPI: Lid Switch [LID] > [ 5.051436] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2 > [ 5.051547] ACPI: Power Button [PBTN] > [ 5.051682] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input3 > [ 5.051760] ACPI: Sleep Button [SBTN] > [ 5.054141] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 > [ 5.054421] ACPI: Power Button [PWRF] > [ 5.056887] agpgart-intel 0000:00:00.0: Intel Sandybridge Chipset > [ 5.058118] agpgart-intel 0000:00:00.0: detected gtt size: 2097152K total, 262144K mappable > [ 5.064439] agpgart-intel 0000:00:00.0: detected 65536K stolen memory > [ 5.064916] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000 > [ 5.070296] [drm] Initialized drm 1.1.0 20060810 > [ 5.080002] xen: registering gsi 16 triggering 0 polarity 1 > [ 5.080015] Already setup the GSI :16 > [ 5.080364] i915 0000:00:02.0: setting latency timer to 64 > [ 5.190295] [drm] MTRR allocation failed. Graphics performance may suffer. > [ 5.190491] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). > [ 5.190493] [drm] Driver supports precise vblank timestamp query. > [ 5.190554] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem > [ 5.548301] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off > [ 5.591093] input: DualPoint Stick as /devices/platform/i8042/serio1/input/input5 > [ 5.606212] input: AlpsPS/2 ALPS DualPoint TouchPad as /devices/platform/i8042/serio1/input/input6 > [ 5.806814] fbcon: inteldrmfb (fb0) is primary device > [ 6.095967] Console: switching to colour frame buffer device 200x56 > [ 6.101477] fb0: inteldrmfb frame buffer device > [ 6.101478] drm: registered panic notifier > [ 6.130833] acpi device:38: registered as cooling_device4 > [ 6.133713] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input7 > [ 6.133915] ACPI: Video Device [VID] (multi-head: yes rom: no post: no) > [ 6.135082] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0 > [ 6.185946] dracut: Starting plymouth daemon > [ 6.479391] dracut: rd_NO_DM: removing DM RAID activation > [ 6.489309] dracut: rd_NO_MD: removing MD RAID activation > [ 6.542596] wmi: Mapper loaded > [ 6.564439] usbcore: registered new interface driver usbfs > [ 6.564463] usbcore: registered new interface driver hub > [ 6.568901] SCSI subsystem initialized > [ 6.569574] usbcore: registered new device driver usb > [ 6.570692] ehci_hcd: USB 2.0 ''Enhanced'' Host Controller (EHCI) Driver > [ 6.570723] xen: registering gsi 16 triggering 0 polarity 1 > [ 6.570728] Already setup the GSI :16 > [ 6.570776] ehci_hcd 0000:00:1a.0: setting latency timer to 64 > [ 6.570782] ehci_hcd 0000:00:1a.0: EHCI Host Controller > [ 6.570814] ehci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 1 > [ 6.570879] ehci_hcd 0000:00:1a.0: debug port 2 > [ 6.573720] libata version 3.00 loaded. > [ 6.574777] ehci_hcd 0000:00:1a.0: cache line size of 64 is not supported > [ 6.574832] ehci_hcd 0000:00:1a.0: irq 16, io mem 0xe2e70000 > [ 6.586344] ehci_hcd 0000:00:1a.0: USB 2.0 started, EHCI 1.00 > [ 6.586369] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 > [ 6.586372] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 > [ 6.586375] usb usb1: Product: EHCI Host Controller > [ 6.586376] usb usb1: Manufacturer: Linux 3.4.18-2.pvops.qubes.x86_64 ehci_hcd > [ 6.586378] usb usb1: SerialNumber: 0000:00:1a.0 > [ 6.586506] hub 1-0:1.0: USB hub found > [ 6.586511] hub 1-0:1.0: 2 ports detected > [ 6.586604] xen: registering gsi 17 triggering 0 polarity 1 > [ 6.586609] Already setup the GSI :17 > [ 6.586663] ehci_hcd 0000:00:1d.0: setting latency timer to 64 > [ 6.586668] ehci_hcd 0000:00:1d.0: EHCI Host Controller > [ 6.586678] ehci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2 > [ 6.586734] ehci_hcd 0000:00:1d.0: debug port 2 > [ 6.590650] ehci_hcd 0000:00:1d.0: cache line size of 64 is not supported > [ 6.590709] ehci_hcd 0000:00:1d.0: irq 17, io mem 0xe2e50000 > [ 6.606335] ehci_hcd 0000:00:1d.0: USB 2.0 started, EHCI 1.00 > [ 6.606364] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 > [ 6.606367] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 > [ 6.606370] usb usb2: Product: EHCI Host Controller > [ 6.606371] usb usb2: Manufacturer: Linux 3.4.18-2.pvops.qubes.x86_64 ehci_hcd > [ 6.606373] usb usb2: SerialNumber: 0000:00:1d.0 > [ 6.606519] hub 2-0:1.0: USB hub found > [ 6.606524] hub 2-0:1.0: 2 ports detected > [ 6.606620] ahci 0000:00:1f.2: version 3.0 > [ 6.606641] xen: registering gsi 18 triggering 0 polarity 1 > [ 6.606647] Already setup the GSI :18 > [ 6.606896] ahci: SSS flag set, parallel bus scan disabled > [ 6.626400] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x3b impl SATA mode > [ 6.626405] ahci 0000:00:1f.2: flags: 64bit ncq sntf stag pm led clo pio slum part ems sxs apst > [ 6.626414] ahci 0000:00:1f.2: setting latency timer to 64 > [ 6.673732] scsi0 : ahci > [ 6.683363] scsi1 : ahci > [ 6.697268] scsi2 : ahci > [ 6.711526] scsi3 : ahci > [ 6.733931] scsi4 : ahci > [ 6.739603] scsi5 : ahci > [ 6.842106] ata1: SATA max UDMA/133 abar m2048@0xe2e40000 port 0xe2e40100 irq 293 > [ 6.842118] ata2: SATA max UDMA/133 abar m2048@0xe2e40000 port 0xe2e40180 irq 293 > [ 6.842124] ata3: DUMMY > [ 6.842129] ata4: SATA max UDMA/133 abar m2048@0xe2e40000 port 0xe2e40280 irq 293 > [ 6.842136] ata5: SATA max UDMA/133 abar m2048@0xe2e40000 port 0xe2e40300 irq 293 > [ 6.842143] ata6: SATA max UDMA/133 abar m2048@0xe2e40000 port 0xe2e40380 irq 293 > [ 6.898480] usb 1-1: new high-speed USB device number 2 using ehci_hcd > [ 7.031312] usb 1-1: New USB device found, idVendor=8087, idProduct=0024 > [ 7.031323] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 > [ 7.032072] hub 1-1:1.0: USB hub found > [ 7.032344] hub 1-1:1.0: 6 ports detected > [ 7.142515] usb 2-1: new high-speed USB device number 2 using ehci_hcd > [ 7.162484] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) > [ 7.268594] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04) > [ 7.268770] ata1.00: ATA-9: KINGSTON SV200S3256G, E111008a, max UDMA/100 > [ 7.268778] ata1.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 31/32), AA > [ 7.272554] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04) > [ 7.272758] ata1.00: configured for UDMA/100 > [ 7.273314] scsi 0:0:0:0: Direct-Access ATA KINGSTON SV200S3 E111 PQ: 0 ANSI: 5 > [ 7.274861] usb 2-1: New USB device found, idVendor=8087, idProduct=0024 > [ 7.274870] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 > [ 7.275358] hub 2-1:1.0: USB hub found > [ 7.275521] hub 2-1:1.0: 8 ports detected > [ 7.346717] usb 1-1.4: new full-speed USB device number 3 using ehci_hcd > [ 7.443529] usb 1-1.4: New USB device found, idVendor=413c, idProduct=8187 > [ 7.443539] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > [ 7.443546] usb 1-1.4: Product: DW375 Bluetooth Module > [ 7.443550] usb 1-1.4: Manufacturer: Dell Computer Corp > [ 7.443555] usb 1-1.4: SerialNumber: D0DF9A40FE60 > [ 7.514736] usb 1-1.5: new high-speed USB device number 4 using ehci_hcd > [ 7.590440] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > [ 7.593835] ata2.00: ATAPI: HL-DT-ST DVD+/-RW GU60N, A103, max UDMA/133 > [ 7.604147] ata2.00: configured for UDMA/133 > [ 7.614746] usb 1-1.5: New USB device found, idVendor=05ca, idProduct=181c > [ 7.614757] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 > [ 7.614763] usb 1-1.5: Product: Laptop_Integrated_Webcam_FHD > [ 7.614768] usb 1-1.5: Manufacturer: CN0CJ3P27248717F040SA01 > [ 7.618662] scsi 1:0:0:0: CD-ROM HL-DT-ST DVD+-RW GU60N A103 PQ: 0 ANSI: 5 > [ 7.686581] usb 2-1.6: new high-speed USB device number 3 using ehci_hcd > [ 7.795399] usb 2-1.6: New USB device found, idVendor=413c, idProduct=818d > [ 7.795410] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > [ 7.795416] usb 2-1.6: Product: DW5550 > [ 7.795420] usb 2-1.6: Manufacturer: Dell > [ 7.795425] usb 2-1.6: SerialNumber: 88FA653FDF944970 > [ 7.902770] usb 2-1.8: new full-speed USB device number 4 using ehci_hcd > [ 7.938478] ata4: SATA link down (SStatus 0 SControl 300) > [ 8.017319] usb 2-1.8: New USB device found, idVendor=0a5c, idProduct=5801 > [ 8.017330] usb 2-1.8: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > [ 8.017336] usb 2-1.8: Product: 5880 > [ 8.017340] usb 2-1.8: Manufacturer: Broadcom Corp > [ 8.017344] usb 2-1.8: SerialNumber: 0123456789ABCD > [ 8.017794] usb 2-1.8: config 0 descriptor?? > [ 8.258411] ata5: SATA link down (SStatus 0 SControl 300) > [ 8.578480] ata6: SATA link down (SStatus 0 SControl 300) > [ 8.588630] sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB) > [ 8.588846] sd 0:0:0:0: [sda] Write Protect is off > [ 8.588861] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 > [ 8.588967] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn''t support DPO or FUA > [ 8.590122] sda: sda1 sda2 > [ 8.591059] sd 0:0:0:0: [sda] Attached SCSI disk > [ 8.609438] sr0: scsi3-mmc drive: 24x/8x writer dvd-ram cd/rw xa/form2 cdda tray > [ 8.609451] cdrom: Uniform CD-ROM driver Revision: 3.20 > [ 8.609737] sr 1:0:0:0: Attached scsi CD-ROM sr0 > [ 8.714515] dracut: luksOpen /dev/sda2 luks-400336fa-c7c4-4be3-a244-c909aa16a18c > [ 13.862564] dracut: Scanning devices dm-0 for LVM logical volumes vg_dom0/lv_root vg_dom0/lv_swap > [ 13.907639] dracut: inactive ''/dev/vg_dom0/lv_root'' [221.62 GiB] inherit > [ 13.907708] dracut: inactive ''/dev/vg_dom0/lv_swap'' [16.34 GiB] inherit > [ 14.162684] EXT4-fs (dm-1): INFO: recovery required on readonly filesystem > [ 14.162693] EXT4-fs (dm-1): write access will be enabled during recovery > [ 14.775779] EXT4-fs (dm-1): orphan cleanup on readonly fs > [ 14.775800] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting unreferenced inode 5767209 > [ 14.775909] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting unreferenced inode 5767207 > [ 14.776007] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting unreferenced inode 5767205 > [ 14.776035] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting unreferenced inode 5767206 > [ 14.776062] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting unreferenced inode 5767204 > [ 14.776088] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting unreferenced inode 5767202 > [ 14.776117] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting unreferenced inode 5767198 > [ 14.776146] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting unreferenced inode 5767196 > [ 14.776172] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting unreferenced inode 5767191 > [ 14.776198] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting unreferenced inode 5767189 > [ 14.776227] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting unreferenced inode 5767188 > [ 14.776274] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting unreferenced inode 5767187 > [ 14.777018] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting unreferenced inode 5767186 > [ 14.777060] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting unreferenced inode 5767184 > [ 14.777089] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting unreferenced inode 5767183 > [ 14.777117] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting unreferenced inode 5767171 > [ 14.777146] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting unreferenced inode 5767170 > [ 14.777172] EXT4-fs (dm-1): 17 orphan inodes deleted > [ 14.777177] EXT4-fs (dm-1): recovery complete > [ 14.797124] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) > [ 14.806762] dracut: Mounted root filesystem /dev/mapper/vg_dom0-lv_root > [ 14.957211] dracut: Switching root > [ 15.599261] udev: starting version 151 > [ 15.673674] iTCO_vendor_support: vendor-support=0 > [ 15.676374] mei: module is from the staging directory, the quality is unknown, you have been warned. > [ 15.676488] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07 > [ 15.676679] iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460) > [ 15.676711] xen: registering gsi 16 triggering 0 polarity 1 > [ 15.676716] Already setup the GSI :16 > [ 15.676725] mei 0000:00:16.0: setting latency timer to 64 > [ 15.676754] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) > [ 15.712582] sd 0:0:0:0: Attached scsi generic sg0 type 0 > [ 15.712620] sr 1:0:0:0: Attached scsi generic sg1 type 5 > [ 15.730448] input: PC Speaker as /devices/platform/pcspkr/input/input8 > [ 15.734494] xen: registering gsi 18 triggering 0 polarity 1 > [ 15.734500] Already setup the GSI :18 > [ 15.734506] ACPI Warning: 0x0000000000004040-0x000000000000405f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20120320/utaddress-251) > [ 15.734512] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver > [ 15.737002] microcode: CPU0 sig=0x206a7, pf=0x10, revision=0x23 > [ 15.741412] watchdog: INTCAMT: cannot register miscdev on minor=130 (err=-16) > [ 15.741418] watchdog: error registering /dev/watchdog (err=-16) > [ 15.741422] mei 0000:00:16.0: unable to register watchdog device. > [ 15.790637] thermal LNXTHERM:00: registered as thermal_zone0 > [ 15.790641] ACPI: Thermal Zone [THM] (25 C) > [ 15.814551] ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared > [ 15.814559] ACPI: Battery Slot [BAT0] (battery present) > [ 15.815037] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared > [ 15.815521] ACPI: AC Adapter [AC] (on-line) > [ 15.867835] usbcore: registered new interface driver usbback > [ 15.975826] ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared > [ 15.975836] ACPI: Battery Slot [BAT1] (battery absent) > [ 16.102871] ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared > [ 16.102882] ACPI: Battery Slot [BAT2] (battery absent) > [ 16.106793] sdhci: Secure Digital Host Controller Interface driver > [ 16.106797] sdhci: Copyright(c) Pierre Ossman > [ 16.107131] parport_pc 00:08: [io 0x0378-0x037b] > [ 16.107296] parport_pc 00:08: [irq 5] > [ 16.107709] sdhci-pci 0000:0a:00.0: SDHCI controller found [1217:8221] (rev 5) > [ 16.159148] xen: registering gsi 17 triggering 0 polarity 1 > [ 16.159156] Already setup the GSI :17 > [ 16.159241] sdhci-pci 0000:0a:00.0: Invalid iomem size. You may experience problems. > [ 16.159319] 0000:0a:00.0 supply vmmc not found, using dummy regulator > [ 16.159384] Registered led device: mmc0:: > [ 16.160442] mmc0: SDHCI controller on PCI [0000:0a:00.0] using DMA > [ 16.160928] sdhci-pci 0000:0a:00.0: could not set regulator OCR (-22) > [ 16.171737] Linux video capture interface: v2.00 > [ 16.192158] cdc_wdm 2-1.6:1.5: cdc-wdm0: USB WDM device > [ 16.192211] cdc_wdm 2-1.6:1.8: cdc-wdm1: USB WDM device > [ 16.192234] usbcore: registered new interface driver cdc_wdm > [ 16.195744] cdc_acm 2-1.6:1.1: ttyACM0: USB ACM device > [ 16.198739] sdhci-pci 0000:0a:00.0: could not set regulator OCR (-22) > [ 16.220532] cdc_acm 2-1.6:1.3: ttyACM1: USB ACM device > [ 16.223728] cdc_acm 2-1.6:1.9: ttyACM2: USB ACM device > [ 16.235089] sdhci-pci 0000:0a:00.0: could not set regulator OCR (-22) > [ 16.235234] usbcore: registered new interface driver cdc_acm > [ 16.235236] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters > [ 16.240235] uvcvideo: Found UVC 1.00 device Laptop_Integrated_Webcam_FHD (05ca:181c) > [ 16.269474] input: Laptop_Integrated_Webcam_FHD as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input9 > [ 16.269579] usbcore: registered new interface driver uvcvideo > [ 16.269581] USB Video Class driver (1.1.1) > [ 16.277415] sdhci-pci 0000:0a:00.0: could not set regulator OCR (-22) > [ 16.296646] usb 2-1.6: MAC-Address: 02:80:37:ec:02:00 > [ 16.296810] cdc_ncm 2-1.6:1.6: usb0: register ''cdc_ncm'' at usb-0000:00:1d.0-1.6, CDC NCM, 02:80:37:ec:02:00 > [ 16.296847] usbcore: registered new interface driver cdc_ncm > [ 16.310604] parport_pc 00:08: activated > [ 16.310611] parport_pc 00:08: reported by Plug and Play ACPI > [ 16.310781] parport_pc 00:08: disabled > [ 16.311583] tpm_tis 00:0a: 1.2 TPM (device-id 0x2001, rev-id 32) > [ 16.399296] Bluetooth: Core ver 2.16 > [ 16.399312] NET: Registered protocol family 31 > [ 16.399314] Bluetooth: HCI device and connection manager initialized > [ 16.399317] Bluetooth: HCI socket layer initialized > [ 16.399318] Bluetooth: L2CAP socket layer initialized > [ 16.399325] Bluetooth: SCO socket layer initialized > [ 16.450583] xen: registering gsi 22 triggering 0 polarity 1 > [ 16.450600] xen: --> pirq=22 -> irq=22 (gsi=22) > [ 16.567577] usbcore: registered new interface driver btusb > [ 16.739259] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2) > [ 16.819125] input: Dell WMI hotkeys as /devices/virtual/input/input10 > [ 16.925000] microcode: CPU1 sig=0x206a7, pf=0x10, revision=0x23 > [ 16.929246] ppdev: user-space parallel port driver > [ 16.954783] microcode: CPU2 sig=0x206a7, pf=0x10, revision=0x23 > [ 16.975176] microcode: CPU3 sig=0x206a7, pf=0x10, revision=0x23 > [ 17.004696] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba > [ 17.067123] ALSA hda_codec.c:5101 autoconfig: line_outs=1 (0xe/0x0/0x0/0x0/0x0) type:line > [ 17.067127] ALSA hda_codec.c:5105 speaker_outs=1 (0xd/0x0/0x0/0x0/0x0) > [ 17.067129] ALSA hda_codec.c:5109 hp_outs=1 (0xb/0x0/0x0/0x0/0x0) > [ 17.067131] ALSA hda_codec.c:5110 mono: mono_out=0x0 > [ 17.067133] ALSA hda_codec.c:5114 inputs: > [ 17.067135] ALSA hda_codec.c:5118 Mic=0xa > [ 17.067137] ALSA hda_codec.c:5118 Dock Mic=0xf > [ 17.067139] ALSA hda_codec.c:5120 > [ 17.067637] ALSA patch_sigmatel.c:3117 stac92xx: dac_nids=1 (0x13/0x0/0x0/0x0/0x0) > [ 17.081104] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11 > [ 17.081194] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12 > [ 17.081250] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13 > [ 17.081342] input: HDA Intel PCH Dock Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14 > [ 17.081432] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input15 > [ 17.081522] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input16 > [ 17.081610] input: HDA Intel PCH Dock Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input17 > [ 17.265462] Event-channel device installed. > [ 17.661764] EXT4-fs (dm-1): re-mounted. Opts: (null) > [ 17.802446] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) > [ 19.361631] Adding 17137660k swap on /dev/mapper/vg_dom0-lv_swap. Priority:-1 extents:1 across:17137660k SS > [ 22.602549] ehci_hcd 0000:00:1a.0: remove, state 1 > [ 22.602568] usb usb1: USB disconnect, device number 1 > [ 22.602573] usb 1-1: USB disconnect, device number 2 > [ 22.602578] usb 1-1.4: USB disconnect, device number 3 > [ 22.605235] usb 1-1.5: USB disconnect, device number 4 > [ 22.636910] ehci_hcd 0000:00:1a.0: USB bus 1 deregistered > [ 22.637183] pciback 0000:00:1a.0: seizing device > [ 22.637235] xen: registering gsi 16 triggering 0 polarity 1 > [ 22.637241] Already setup the GSI :16 > [ 22.662363] ehci_hcd 0000:00:1d.0: remove, state 1 > [ 22.662371] usb usb2: USB disconnect, device number 1 > [ 22.662373] usb 2-1: USB disconnect, device number 2 > [ 22.662376] usb 2-1.6: USB disconnect, device number 3 > [ 22.668531] cdc_ncm 2-1.6:1.6: usb0: unregister ''cdc_ncm'' usb-0000:00:1d.0-1.6, CDC NCM > [ 22.694795] usb 2-1.8: USB disconnect, device number 4 > [ 22.699298] ehci_hcd 0000:00:1d.0: USB bus 2 deregistered > [ 22.699577] pciback 0000:00:1d.0: seizing device > [ 22.699632] xen: registering gsi 17 triggering 0 polarity 1 > [ 22.699637] Already setup the GSI :17 > [ 23.684708] xen-pciback: vpci: 0000:00:19.0: assign to virtual slot 0 > [ 23.685240] xen-pciback: vpci: 0000:00:1a.0: assign to virtual slot 1 > [ 23.685722] xen-pciback: vpci: 0000:00:1d.0: assign to virtual slot 2 > [ 23.686764] xen-pciback: vpci: 0000:02:00.0: assign to virtual slot 3 > [ 23.909636] pciback 0000:00:19.0: Driver tried to write to a read-only configuration space field at offset 0xd2, size 2. This may be harmless, but if you have problems with your device: > [ 23.909638] 1) see permissive attribute in sysfs > [ 23.909638] 2) report problems to the xen-devel mailing list along with details of your device obtained from lspci. > [ 23.917523] pciback 0000:02:00.0: Driver tried to write to a read-only configuration space field at offset 0xd2, size 2. This may be harmless, but if you have problems with your device: > [ 23.917526] 1) see permissive attribute in sysfs > [ 23.917526] 2) report problems to the xen-devel mailing list along with details of your device obtained from lspci. > [ 24.123663] xen-blkback:ring-ref 9, event-channel 14, protocol 1 (x86_64-abi) > [ 24.140460] xen-blkback:ring-ref 10, event-channel 15, protocol 1 (x86_64-abi) > [ 24.151420] xen-blkback:ring-ref 11, event-channel 16, protocol 1 (x86_64-abi) > [ 24.158428] xen-blkback:ring-ref 12, event-channel 17, protocol 1 (x86_64-abi) > [ 28.697615] pciback 0000:00:1a.0: enabling device (0000 -> 0002) > [ 28.697628] xen: registering gsi 16 triggering 0 polarity 1 > [ 28.697634] Already setup the GSI :16 > [ 28.697805] pciback 0000:00:1a.0: setting latency timer to 64 > [ 28.713578] pciback 0000:00:19.0: enabling device (0000 -> 0003) > [ 28.713591] xen: registering gsi 20 triggering 0 polarity 1 > [ 28.713598] Already setup the GSI :20 > [ 28.713858] pciback 0000:00:19.0: setting latency timer to 64 > [ 29.021371] pciback 0000:00:1d.0: enabling device (0000 -> 0002) > [ 29.021389] xen: registering gsi 17 triggering 0 polarity 1 > [ 29.021400] Already setup the GSI :17 > [ 29.021805] pciback 0000:00:1d.0: setting latency timer to 64 > [ 29.150053] pciback 0000:02:00.0: enabling device (0000 -> 0002) > [ 29.150122] xen: registering gsi 17 triggering 0 polarity 1 > [ 29.150150] Already setup the GSI :17 > [ 33.635416] xen-blkback:ring-ref 9, event-channel 14, protocol 1 (x86_64-abi) > [ 33.643330] xen-blkback:ring-ref 10, event-channel 15, protocol 1 (x86_64-abi) > [ 33.651561] xen-blkback:ring-ref 11, event-channel 16, protocol 1 (x86_64-abi) > [ 33.672105] xen-blkback:ring-ref 12, event-channel 17, protocol 1 (x86_64-abi) > [ 104.230911] xen-blkback:ring-ref 9, event-channel 24, protocol 1 (x86_64-abi) > [ 104.252421] xen-blkback:ring-ref 10, event-channel 25, protocol 1 (x86_64-abi) > [ 104.253177] xen-blkback:ring-ref 11, event-channel 26, protocol 1 (x86_64-abi) > [ 104.254220] xen-blkback:ring-ref 12, event-channel 27, protocol 1 (x86_64-abi) > [ 105.086732] xen-blkback:ring-ref 9, event-channel 14, protocol 1 (x86_64-abi) > [ 105.105505] xen-blkback:ring-ref 10, event-channel 15, protocol 1 (x86_64-abi) > [ 105.115951] xen-blkback:ring-ref 11, event-channel 16, protocol 1 (x86_64-abi) > [ 105.127384] xen-blkback:ring-ref 12, event-channel 17, protocol 1 (x86_64-abi) > [ 105.929760] xen-blkback:ring-ref 9, event-channel 14, protocol 1 (x86_64-abi) > [ 105.934841] xen-blkback:ring-ref 10, event-channel 15, protocol 1 (x86_64-abi) > [ 105.973920] xen-blkback:ring-ref 11, event-channel 16, protocol 1 (x86_64-abi) > [ 105.975320] xen-blkback:ring-ref 12, event-channel 17, protocol 1 (x86_64-abi) > [ 107.191781] xen-blkback:ring-ref 9, event-channel 14, protocol 1 (x86_64-abi) > [ 107.203711] xen-blkback:ring-ref 10, event-channel 15, protocol 1 (x86_64-abi) > [ 107.208481] xen-blkback:ring-ref 11, event-channel 16, protocol 1 (x86_64-abi) > [ 107.212081] xen-blkback:ring-ref 12, event-channel 17, protocol 1 (x86_64-abi) > [ 733.434608] PM: Syncing filesystems ... done. > [ 733.436228] PM: Preparing system for mem sleep > [ 733.514803] Freezing user space processes ... (elapsed 0.01 seconds) done. > [ 733.530594] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. > [ 733.546589] PM: Entering mem sleep > [ 733.546741] Suspending console(s) (use no_console_suspend to debug) > [ 733.547431] sd 0:0:0:0: [sda] Synchronizing SCSI cache > [ 733.558336] sd 0:0:0:0: [sda] Stopping disk > [ 734.194656] PM: suspend of devices complete after 647.504 msecs > [ 734.195026] PM: late suspend of devices complete after 0.359 msecs > [ 734.210655] PM: noirq suspend of devices complete after 15.614 msecs > [ 734.211326] ACPI: Preparing to enter system sleep state S3 > [ 734.235008] PM: Saving platform NVS memory > [ 734.328066] Disabling non-boot CPUs ... > [ 735.945491] ACPI: Low-level resume complete > [ 735.945579] PM: Restoring platform NVS memory > [ 736.000094] Enabling non-boot CPUs ... > [ 736.000256] installing Xen timer for CPU 1 > [ 736.004594] CPU1 is up > [ 736.004819] installing Xen timer for CPU 2 > [ 736.067516] CPU2 is up > [ 736.067770] installing Xen timer for CPU 3 > [ 736.101535] CPU3 is up > [ 736.102470] ACPI: Waking up from system sleep state S3 > [ 736.555932] PM: noirq resume of devices complete after 7.970 msecs > [ 736.556506] PM: early resume of devices complete after 0.387 msecs > [ 736.660336] i915 0000:00:02.0: setting latency timer to 64 > [ 736.660404] pciback 0000:00:19.0: setting latency timer to 64 > [ 736.660453] xen: registering gsi 16 triggering 0 polarity 1 > [ 736.660460] Already setup the GSI :16 > [ 736.660490] pciback 0000:00:1a.0: setting latency timer to 64 > [ 736.660605] xen: registering gsi 17 triggering 0 polarity 1 > [ 736.660610] Already setup the GSI :17 > [ 736.660641] pciback 0000:00:1d.0: setting latency timer to 64 > [ 736.660696] xen: registering gsi 22 triggering 0 polarity 1 > [ 736.660701] Already setup the GSI :22 > [ 736.661221] ahci 0000:00:1f.2: setting latency timer to 64 > [ 736.689606] xen: registering gsi 18 triggering 0 polarity 1 > [ 736.689608] Already setup the GSI :18 > [ 736.689704] xen: registering gsi 17 triggering 0 polarity 1 > [ 736.689706] Already setup the GSI :17 > [ 736.711623] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off > [ 736.802676] watchdog: INTCAMT: cannot register miscdev on minor=130 (err=-16) > [ 736.802678] watchdog: error registering /dev/watchdog (err=-16) > [ 736.802680] mei 0000:00:16.0: unable to register watchdog device. > [ 737.060106] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > [ 737.060330] ata4: SATA link down (SStatus 0 SControl 300) > [ 737.060372] ata5: SATA link down (SStatus 0 SControl 300) > [ 737.074123] ata2.00: configured for UDMA/133 > [ 737.117629] ata6: SATA link down (SStatus 0 SControl 300) > [ 738.619036] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) > [ 738.743565] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04) > [ 738.901088] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04) > [ 738.903441] ata1.00: configured for UDMA/100 > [ 738.903843] sd 0:0:0:0: [sda] Starting disk > [ 738.905367] PM: resume of devices complete after 2348.851 msecs > [ 738.905922] PM: Finishing wakeup. > [ 738.905926] Restarting tasks ... done. > [ 738.911334] video LNXVIDEO:00: Restoring backlight state > [ 739.836250] dell_wmi: Received unknown WMI event (0x0) > [ 740.184759] sdhci-pci 0000:0a:00.0: could not set regulator OCR (-22) > [ 740.239730] sdhci-pci 0000:0a:00.0: could not set regulator OCR (-22) > [ 740.327711] sdhci-pci 0000:0a:00.0: could not set regulator OCR (-22) > [ 740.373931] sdhci-pci 0000:0a:00.0: could not set regulator OCR (-22) > [ 742.542022] hrtimer: interrupt took 102980031 ns > [ 757.609031] [sched_delayed] sched: RT throttling activated > [ 760.164427] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.> (XEN) Xen version 4.1.3 (user@marmarek.net) (gcc version 4.4.5 20101112 (Red Hat 4.4.5-2) (GCC) ) Mon Nov 26 15:25:32 EST 2012 > (XEN) Latest ChangeSet: unavailable > (XEN) Bootloader: GNU GRUB 0.97 > (XEN) Command line: console=none cpufreq=verbose=1 > (XEN) Video information: > (XEN) VGA is text mode 80x25, font 8x16 > (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds > (XEN) Disc information: > (XEN) Found 1 MBR signatures > (XEN) Found 1 EDD information structures > (XEN) Xen-e820 RAM map: > (XEN) 0000000000000000 - 000000000009a800 (usable) > (XEN) 000000000009a800 - 00000000000a0000 (reserved) > (XEN) 00000000000e0000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 0000000007eea000 (usable) > (XEN) 0000000007eea000 - 0000000007f67000 (ACPI NVS) > (XEN) 0000000007f67000 - 0000000007f70000 (usable) > (XEN) 0000000007f70000 - 0000000007f76000 (ACPI NVS) > (XEN) 0000000007f76000 - 0000000007f78000 (usable) > (XEN) 0000000007f78000 - 0000000008000000 (ACPI NVS) > (XEN) 0000000008000000 - 000000000dffd000 (usable) > (XEN) 000000000dffd000 - 000000000e000000 (ACPI data) > (XEN) 000000000e000000 - 0000000020000000 (usable) > (XEN) 0000000020000000 - 0000000020200000 (reserved) > (XEN) 0000000020200000 - 0000000040000000 (usable) > (XEN) 0000000040000000 - 0000000040200000 (reserved) > (XEN) 0000000040200000 - 00000000c83b4000 (usable) > (XEN) 00000000c83b4000 - 00000000c840a000 (reserved) > (XEN) 00000000c840a000 - 00000000c840e000 (usable) > (XEN) 00000000c840e000 - 00000000c840f000 (reserved) > (XEN) 00000000c840f000 - 00000000c8411000 (usable) > (XEN) 00000000c8411000 - 00000000c8414000 (reserved) > (XEN) 00000000c8414000 - 00000000c841e000 (usable) > (XEN) 00000000c841e000 - 00000000c8428000 (reserved) > (XEN) 00000000c8428000 - 00000000c8432000 (usable) > (XEN) 00000000c8432000 - 00000000c8436000 (reserved) > (XEN) 00000000c8436000 - 00000000cac00000 (usable) > (XEN) 00000000cb800000 - 00000000cfa00000 (reserved) > (XEN) 00000000fed1c000 - 00000000fed20000 (reserved) > (XEN) 00000000ffc00000 - 00000000ffc20000 (reserved) > (XEN) 0000000100000000 - 000000042e000000 (usable) > (XEN) ACPI: RSDP 000FE300, 0024 (r2 DELL ) > (XEN) ACPI: XSDT 0DFFEE18, 007C (r1 DELL CBX3 6222004 MSFT 10013) > (XEN) ACPI: FACP 07F90D98, 00F4 (r4 DELL CBX3 6222004 MSFT 10013) > (XEN) ACPI: DSDT 07F5E018, 8834 (r2 INT430 SYSFexxx 1001 INTL 20090903) > (XEN) ACPI: FACS 07FEDD40, 0040 > (XEN) ACPI: APIC 0DFFDF18, 00CC (r2 DELL CBX3 6222004 MSFT 10013) > (XEN) ACPI: TCPA 07FEED18, 0032 (r2 0 0) > (XEN) ACPI: SSDT 07F91A98, 02F9 (r1 DELLTP TPM 3000 INTL 20090903) > (XEN) ACPI: MCFG 07FEEC98, 003C (r1 DELL SNDYBRDG 6222004 MSFT 97) > (XEN) ACPI: HPET 07FEEC18, 0038 (r1 A M I PCHHPET 6222004 AMI. 3) > (XEN) ACPI: BOOT 07FEEB98, 0028 (r1 DELL CBX3 6222004 AMI 10013) > (XEN) ACPI: SSDT 07F75018, 0804 (r1 PmRef Cpu0Ist 3000 INTL 20090903) > (XEN) ACPI: SSDT 07F74018, 0996 (r1 PmRef CpuPm 3000 INTL 20090903) > (XEN) ACPI: DMAR 07F90C18, 00E8 (r1 INTEL SNB 1 INTL 1) > (XEN) ACPI: SLIC 07F7EC18, 0176 (r3 DELL CBX3 6222004 MSFT 10013) > (XEN) System RAM: 16262MB (16652432kB) > (XEN) Domain heap initialised > (XEN) ACPI: 32/64X FACS address mismatch in FADT - 07fede40/0000000007fedd40, using 32 > (XEN) Processor #0 6:10 APIC version 21 > (XEN) Processor #2 6:10 APIC version 21 > (XEN) Processor #1 6:10 APIC version 21 > (XEN) Processor #3 6:10 APIC version 21 > (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > (XEN) Table is not found! > (XEN) Switched to APIC driver x2apic_cluster. > (XEN) Using scheduler: SMP Credit Scheduler (credit) > (XEN) Detected 2494.416 MHz processor. > (XEN) Initing memory sharing. > (XEN) Intel VT-d supported page sizes: 4kB. > (XEN) Intel VT-d supported page sizes: 4kB. > (XEN) Intel VT-d Snoop Control not enabled. > (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. > (XEN) Intel VT-d Queued Invalidation enabled. > (XEN) Intel VT-d Interrupt Remapping enabled. > (XEN) Intel VT-d Shared EPT tables not enabled. > (XEN) I/O virtualisation enabled > (XEN) - Dom0 mode: Relaxed > (XEN) Enabled directed EOI with ioapic_ack_old on! > (XEN) ENABLING IO-APIC IRQs > (XEN) -> Using old ACK method > (XEN) Platform timer appears to have unexpectedly wrapped 1 times. > (XEN) Platform timer is 14.318MHz HPET > (XEN) Allocated console ring of 16 KiB. > (XEN) VMX: Supported advanced features: > (XEN) - APIC MMIO access virtualisation > (XEN) - APIC TPR shadow > (XEN) - Extended Page Tables (EPT) > (XEN) - Virtual-Processor Identifiers (VPID) > (XEN) - Virtual NMI > (XEN) - MSR direct-access bitmap > (XEN) - Unrestricted Guest > (XEN) HVM: ASIDs enabled. > (XEN) HVM: VMX enabled > (XEN) HVM: Hardware Assisted Paging (HAP) detected > (XEN) HVM: HAP page sizes: 4kB, 2MB > (XEN) Brought up 4 CPUs > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1e13000 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 0000000418000000->000000041c000000 (4046567 pages to be allocated) > (XEN) Init. ramdisk: 000000042b335000->000000042dfffc00 > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: ffffffff81000000->ffffffff81e13000 > (XEN) Init. ramdisk: ffffffff81e13000->ffffffff84addc00 > (XEN) Phys-Mach map: ffffffff84ade000->ffffffff869f3d90 > (XEN) Start info: ffffffff869f4000->ffffffff869f44b4 > (XEN) Page tables: ffffffff869f5000->ffffffff86a2e000 > (XEN) Boot stack: ffffffff86a2e000->ffffffff86a2f000 > (XEN) TOTAL: ffffffff80000000->ffffffff86c00000 > (XEN) ENTRY ADDRESS: ffffffff8188e200 > (XEN) Dom0 has maximum 4 VCPUs > (XEN) Scrubbing Free RAM: .done. > (XEN) Xen trace buffers: disabled > (XEN) Std. Loglevel: Errors and warnings > (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen) > (XEN) Freed 216kB init memory. > (XEN) no cpu_id for acpi_id 5 > (XEN) no cpu_id for acpi_id 6 > (XEN) no cpu_id for acpi_id 7 > (XEN) no cpu_id for acpi_id 8 > (XEN) physdev.c:171: dom0: wrong map_pirq type 3 > (XEN) traps.c:2488:d1 Domain attempted WRMSR 0000000000000079 from 0x0000000000000000 to 0xffffc9000057b030. > (XEN) traps.c:2488:d1 Domain attempted WRMSR 0000000000000079 from 0x0000000000000000 to 0xffffc90000718030. > (XEN) traps.c:2488:d2 Domain attempted WRMSR 0000000000000079 from 0x0000000000000000 to 0xffffc900004f2030. > (XEN) traps.c:2488:d2 Domain attempted WRMSR 0000000000000079 from 0x0000000000000000 to 0xffffc900004fa030. > (XEN) traps.c:2488:d3 Domain attempted WRMSR 0000000000000079 from 0x0000000000000000 to 0xffffc90000251030. > (XEN) traps.c:2488:d3 Domain attempted WRMSR 0000000000000079 from 0x0000000000000000 to 0xffffc90000263030. > (XEN) traps.c:2488:d3 Domain attempted WRMSR 0000000000000079 from 0x0000000000000000 to 0xffffc9000026b030. > (XEN) traps.c:2488:d3 Domain attempted WRMSR 0000000000000079 from 0x0000000000000000 to 0xffffc90000273030. > (XEN) traps.c:2488:d4 Domain attempted WRMSR 0000000000000079 from 0x0000000000000000 to 0xffffc900004f2030. > (XEN) traps.c:2488:d4 Domain attempted WRMSR 0000000000000079 from 0x0000000000000000 to 0xffffc90000015030. > (XEN) traps.c:2488:d5 Domain attempted WRMSR 0000000000000079 from 0x0000000000000000 to 0xffffc900004f2030. > (XEN) traps.c:2488:d5 Domain attempted WRMSR 0000000000000079 from 0x0000000000000000 to 0xffffc90000015030. > (XEN) traps.c:2488:d6 Domain attempted WRMSR 0000000000000079 from 0x0000000000000000 to 0xffffc900004f2030. > (XEN) traps.c:2488:d6 Domain attempted WRMSR 0000000000000079 from 0x0000000000000000 to 0xffffc900004fa030. > (XEN) Disabling non-boot CPUs ... > (XEN) Broke affinity for irq 1 > (XEN) Broke affinity for irq 8 > (XEN) Broke affinity for irq 9 > (XEN) Broke affinity for irq 12 > (XEN) Broke affinity for irq 17 > (XEN) Broke affinity for irq 31 > (XEN) Broke affinity for irq 16 > (XEN) Broke affinity for irq 20 > (XEN) Entering ACPI S3 state. > (XEN) mce_intel.c:1162: MCA Capability: BCAST 1 SER 0 CMCI 1 firstbank 0 extended MCE MSR 0 > (XEN) CPU0 CMCI LVT vector (0xf7) already installed > (XEN) CPU0: Thermal LVT vector (0xfa) already installed > (XEN) Finishing wakeup from ACPI S3 state. > (XEN) Enabling non-boot CPUs ... > (XEN) traps.c:2488:d7 Domain attempted WRMSR 0000000000000079 from 0x0000000000000000 to 0xffffc90000524030. > (XEN) traps.c:2488:d7 Domain attempted WRMSR 0000000000000079 from 0x0000000000000000 to 0xffffc9000052c030. > (XEN) traps.c:2488:d7 Domain attempted WRMSR 0000000000000079 from 0x0000000000000000 to 0xffffc90000015030. > (XEN) traps.c:2488:d7 Domain attempted WRMSR 0000000000000079 from 0x0000000000000000 to 0xffffc9000001d030. > (XEN) Dumping timer queues: > (XEN) CPU00: > (XEN) ex= 126us timer=ffff8300c83b0060 cb=ffff82c48011e420(ffff8300c83b0000) vcpu_singleshot_timer_fn+0x0/0x10 > (XEN) ex= 1778us timer=ffff8304222f9de8 cb=ffff82c480118250(0000000000000000) csched_tick+0x0/0x2e0 > (XEN) ex= 126us timer=ffff8300c81fc060 cb=ffff82c48011e420(ffff8300c81fc000) vcpu_singleshot_timer_fn+0x0/0x10 > (XEN) ex= 17227us timer=ffff82c4802bb980 cb=ffff82c480138ff0(ffff82c4802bb940) do_dbs_timer+0x0/0x250 > (XEN) ex= 20744us timer=ffff830030094060 cb=ffff82c48011e420(ffff830030094000) vcpu_singleshot_timer_fn+0x0/0x10 > (XEN) ex= 27945us timer=ffff8304222fdde0 cb=ffff82c480116f20(ffff8304222fddc0) csched_acct+0x0/0x460 > (XEN) ex= 29949us timer=ffff82c4802bb760 cb=ffff82c48011ded0(0000000000000000) s_timer_fn+0x0/0x20 > (XEN) ex= 87774us timer=ffff83008db6a060 cb=ffff82c48011e420(ffff83008db6a000) vcpu_singleshot_timer_fn+0x0/0x10 > (XEN) ex= 79252us timer=ffff82c4802b3880 cb=ffff82c480177160(0000000000000000) time_calibration+0x0/0x60 > (XEN) ex= 703146us timer=ffff8300a6b9c060 cb=ffff82c48011e420(ffff8300a6b9c000) vcpu_singleshot_timer_fn+0x0/0x10 > (XEN) ex= 35612us timer=ffff8300330dc060 cb=ffff82c48011e420(ffff8300330dc000) vcpu_singleshot_timer_fn+0x0/0x10 > (XEN) ex= 97688us timer=ffff8300a6b98060 cb=ffff82c48011e420(ffff8300a6b98000) vcpu_singleshot_timer_fn+0x0/0x10 > (XEN) ex= 30003us timer=ffff8300b129a060 cb=ffff82c48011e420(ffff8300b129a000) vcpu_singleshot_timer_fn+0x0/0x10 > (XEN) ex= 92679us timer=ffff8300c94a6060 cb=ffff82c48011e420(ffff8300c94a6000) vcpu_singleshot_timer_fn+0x0/0x10 > (XEN) ex= 4135118us timer=ffff8300bdca6060 cb=ffff82c48011e420(ffff8300bdca6000) vcpu_singleshot_timer_fn+0x0/0x10 > (XEN) ex= 96411us timer=ffff8300b128e060 cb=ffff82c48011e420(ffff8300b128e000) vcpu_singleshot_timer_fn+0x0/0x10 > (XEN) ex= 1337866us timer=ffff8300a6b94060 cb=ffff82c48011e420(ffff8300a6b94000) vcpu_singleshot_timer_fn+0x0/0x10 > (XEN) ex= 91194us timer=ffff830034b98060 cb=ffff82c48011e420(ffff830034b98000) vcpu_singleshot_timer_fn+0x0/0x10 > (XEN) ex= 97955us timer=ffff83007d948060 cb=ffff82c48011e420(ffff83007d948000) vcpu_singleshot_timer_fn+0x0/0x10 > (XEN) ex= 4135163us timer=ffff8300c5336060 cb=ffff82c48011e420(ffff8300c5336000) vcpu_singleshot_timer_fn+0x0/0x10 > (XEN) ex=123464409us timer=ffff82c4802b3980 cb=ffff82c480176ef0(0000000000000000) plt_overflow+0x0/0x190 > (XEN) ex= 95968us timer=ffff8300a6b96060 cb=ffff82c48011e420(ffff8300a6b96000) vcpu_singleshot_timer_fn+0x0/0x10 > (XEN) ex=12401701us timer=ffff82c4802b65a0 cb=ffff82c48019eb10(0000000000000000) mce_work_fn+0x0/0xd0 > (XEN) ex= 97804us timer=ffff8300301a8060 cb=ffff82c48011e420(ffff8300301a8000) vcpu_singleshot_timer_fn+0x0/0x10 > (XEN) ex= 97841us timer=ffff8300bd810060 cb=ffff82c48011e420(ffff8300bd810000) vcpu_singleshot_timer_fn+0x0/0x10 > (XEN) ex= 98039us timer=ffff83007d94c060 cb=ffff82c48011e420(ffff83007d94c000) vcpu_singleshot_timer_fn+0x0/0x10 > (XEN) ex= 94727us timer=ffff83008db6e060 cb=ffff82c48011e420(ffff83008db6e000) vcpu_singleshot_timer_fn+0x0/0x10 > (XEN) ex= 319927us timer=ffff8300c840c060 cb=ffff82c48011e420(ffff8300c840c000) vcpu_singleshot_timer_fn+0x0/0x10 > (XEN) CPU01: > (XEN) CPU02: > (XEN) CPU03: > (XEN) ''c'' pressed -> printing ACPI Cx structures > (XEN) ==cpu0=> (XEN) active state: C3 > (XEN) max_cstate: C7 > (XEN) states: > (XEN) C1: type[C1] latency[000] usage[00254665] method[ HALT] duration[62720099833] > (XEN) C2: type[C2] latency[080] usage[00069505] method[SYSIO] duration[36499255195] > (XEN) *C3: type[C3] latency[109] usage[01828952] method[SYSIO] duration[5562126933174] > (XEN) C0: usage[02153122] duration[2042526389598] > (XEN) PC3[0] PC6[0] PC7[0] > (XEN) CC3[0] CC6[0] > (XEN) ==cpu1=> (XEN) active state: C1 > (XEN) max_cstate: C7 > (XEN) states: > (XEN) *C1: type[C1] latency[000] usage[00808027] method[ HALT] duration[6978799306750] > (XEN) C0: usage[00808027] duration[725073398104] > (XEN) PC3[0] PC6[0] PC7[0] > (XEN) CC3[0] CC6[0] > (XEN) ==cpu2=> (XEN) active state: C1 > (XEN) max_cstate: C7 > (XEN) states: > (XEN) *C1: type[C1] latency[000] usage[00825022] method[ HALT] duration[6981527416097] > (XEN) C0: usage[00825022] duration[722345319882] > (XEN) PC3[0] PC6[0] PC7[0] > (XEN) CC3[0] CC6[0] > (XEN) ==cpu3=> (XEN) active state: C1 > (XEN) max_cstate: C7 > (XEN) states: > (XEN) *C1: type[C1] latency[000] usage[00810292] method[ HALT] duration[6980835907857] > (XEN) C0: usage[00810292] duration[723036844779] > (XEN) PC3[0] PC6[0] PC7[0] > (XEN) CC3[0] CC6[0]> _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel
I had similar, but (I think) different issues. See the following thread: http://markmail.org/search/?q=e4a31205766d518276d0fbc1780bcd63db1a502d#query:e4a31205766d518276d0fbc1780bcd63db1a502d+page:1+mid:udkd2qcvtyqj75re+state:results I still have a patch reverting part of this changeset to get S3 working with pinning CPU affinity... the affinity doesn''t get restored on resume, however. I don''t have much experience with this on Xen 4.1, as I ran into the issue when bringing up Xen-4.2, from Xen 4.0 However, I could see how this could be related, since it is in the scheduler... On Fri, Nov 30, 2012 at 4:33 PM, Konrad Rzeszutek Wilk <konrad@kernel.org>wrote:> On Thu, Nov 29, 2012 at 07:55:06PM +0100, Marek Marczykowski wrote: > > Hi all, > > > > After resume from ACPI S3 system has only CPU0 enabled, every vCPU from > every > > domain works on CPU0 [1]. When trying to pin some vCPU to CPU1 got > error: > > xl vcpu-pin testvm 1 1 > > libxl: error: libxl.c:2565:libxl_set_vcpuaffinity setting vcpu affinity: > > Invalid argument > > > > What went wrong? How can I reenable CPU1-CPU3? > > I think Ben had found some issues with this in the past? CC-ing him > here. > > > > System info: > > xen 4.1.3 > > linux 3.4.18 with acpi-s3 patches from Konrad''s git > > Processor: Intel i5-2520M > > > > dmesg from dom0 and hypervisor attached. > > > > BTW Are there any plans to upstream acpi-s3 patches? > > > > [1] xl vcpu-list: > > Name ID VCPU CPU State Time(s) CPU > Affinity > > dom0 0 0 0 r-- 1347.8 any > cpu > > dom0 0 1 0 -b- 594.4 any > cpu > > dom0 0 2 0 -b- 421.1 any > cpu > > dom0 0 3 0 -b- 432.6 any > cpu > > netvm 1 0 0 -b- 596.6 any > cpu > > netvm 1 1 0 -b- 363.7 any > cpu > > firewallvm 2 0 0 -b- 170.5 any > cpu > > firewallvm 2 1 0 -b- 122.5 any > cpu > > devel17 3 0 0 -b- 137.0 any > cpu > > devel17 3 1 0 -b- 112.9 any > cpu > > devel17 3 2 0 -b- 97.9 any > cpu > > devel17 3 3 0 -b- 116.0 any > cpu > > vm2 4 0 0 -b- 418.6 any > cpu > > vm2 4 1 0 -b- 390.2 any > cpu > > private 5 0 0 -b- 175.9 any > cpu > > private 5 1 0 -b- 161.6 any > cpu > > mail 6 0 0 -b- 1587.1 any > cpu > > mail 6 1 0 -b- 1717.5 any > cpu > > testvm 7 0 0 -b- 73.0 any > cpu > > testvm 7 1 0 -b- 68.9 any > cpu > > testvm 7 2 0 -b- 51.4 any > cpu > > testvm 7 3 0 -b- 67.1 any > cpu > > disp1 8 0 0 -b- 199.9 any > cpu > > > > > > -- > > Best Regards / Pozdrawiam, > > Marek Marczykowski > > Invisible Things Lab > > > [ 0.000000] Initializing cgroup subsys cpuset > > [ 0.000000] Initializing cgroup subsys cpu > > [ 0.000000] Linux version 3.4.18-2.pvops.qubes.x86_64 ( > user@nemezis.marmarek.net) (gcc version 4.4.5 20101112 (Red Hat 4.4.5-2) > (GCC) ) #1 SMP Wed Nov 7 22:47:21 EST 2012 > > [ 0.000000] Command line: ro root=/dev/mapper/vg_dom0-lv_root > rd_LUKS_UUID=luks-400336fa-c7c4-4be3-a244-c909aa16a18c > rd_LVM_LV=vg_dom0/lv_root rd_LVM_LV=vg_dom0/lv_swap rd_NO_MD rd_NO_DM > LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=pl2 rhgb quiet > max_loop=255 > > [ 0.000000] Freeing 9a-100 pfn range: 102 pages freed > > [ 0.000000] 1-1 mapping on 9a->100 > > [ 0.000000] Freeing 7eea-7f67 pfn range: 125 pages freed > > [ 0.000000] 1-1 mapping on 7eea->7f67 > > [ 0.000000] Freeing 7f70-7f76 pfn range: 6 pages freed > > [ 0.000000] 1-1 mapping on 7f70->7f76 > > [ 0.000000] Freeing 7f78-8000 pfn range: 136 pages freed > > [ 0.000000] 1-1 mapping on 7f78->8000 > > [ 0.000000] Freeing dffd-e000 pfn range: 3 pages freed > > [ 0.000000] 1-1 mapping on dffd->e000 > > [ 0.000000] Freeing 20000-20200 pfn range: 512 pages freed > > [ 0.000000] 1-1 mapping on 20000->20200 > > [ 0.000000] Freeing 40000-40200 pfn range: 512 pages freed > > [ 0.000000] 1-1 mapping on 40000->40200 > > [ 0.000000] Freeing c83b4-c840a pfn range: 86 pages freed > > [ 0.000000] 1-1 mapping on c83b4->c840a > > [ 0.000000] Freeing c840e-c840f pfn range: 1 pages freed > > [ 0.000000] 1-1 mapping on c840e->c840f > > [ 0.000000] Freeing c8411-c8414 pfn range: 3 pages freed > > [ 0.000000] 1-1 mapping on c8411->c8414 > > [ 0.000000] Freeing c841e-c8428 pfn range: 10 pages freed > > [ 0.000000] 1-1 mapping on c841e->c8428 > > [ 0.000000] Freeing c8432-c8436 pfn range: 4 pages freed > > [ 0.000000] 1-1 mapping on c8432->c8436 > > [ 0.000000] Freeing cac00-100000 pfn range: 218112 pages freed > > [ 0.000000] 1-1 mapping on cac00->100000 > > [ 0.000000] Released 219612 pages of unused memory > > [ 0.000000] Set 219612 page(s) to 1-1 mapping > > [ 0.000000] BIOS-provided physical RAM map: > > [ 0.000000] Xen: 0000000000000000 - 000000000009a000 (usable) > > [ 0.000000] Xen: 000000000009a800 - 0000000000100000 (reserved) > > [ 0.000000] Xen: 0000000000100000 - 0000000007eea000 (usable) > > [ 0.000000] Xen: 0000000007eea000 - 0000000007f67000 (ACPI NVS) > > [ 0.000000] Xen: 0000000007f67000 - 0000000007f70000 (usable) > > [ 0.000000] Xen: 0000000007f70000 - 0000000007f76000 (ACPI NVS) > > [ 0.000000] Xen: 0000000007f76000 - 0000000007f78000 (usable) > > [ 0.000000] Xen: 0000000007f78000 - 0000000008000000 (ACPI NVS) > > [ 0.000000] Xen: 0000000008000000 - 000000000dffd000 (usable) > > [ 0.000000] Xen: 000000000dffd000 - 000000000e000000 (ACPI data) > > [ 0.000000] Xen: 000000000e000000 - 0000000020000000 (usable) > > [ 0.000000] Xen: 0000000020000000 - 0000000020200000 (reserved) > > [ 0.000000] Xen: 0000000020200000 - 0000000040000000 (usable) > > [ 0.000000] Xen: 0000000040000000 - 0000000040200000 (reserved) > > [ 0.000000] Xen: 0000000040200000 - 00000000c83b4000 (usable) > > [ 0.000000] Xen: 00000000c83b4000 - 00000000c840a000 (reserved) > > [ 0.000000] Xen: 00000000c840a000 - 00000000c840e000 (usable) > > [ 0.000000] Xen: 00000000c840e000 - 00000000c840f000 (reserved) > > [ 0.000000] Xen: 00000000c840f000 - 00000000c8411000 (usable) > > [ 0.000000] Xen: 00000000c8411000 - 00000000c8414000 (reserved) > > [ 0.000000] Xen: 00000000c8414000 - 00000000c841e000 (usable) > > [ 0.000000] Xen: 00000000c841e000 - 00000000c8428000 (reserved) > > [ 0.000000] Xen: 00000000c8428000 - 00000000c8432000 (usable) > > [ 0.000000] Xen: 00000000c8432000 - 00000000c8436000 (reserved) > > [ 0.000000] Xen: 00000000c8436000 - 00000000cac00000 (usable) > > [ 0.000000] Xen: 00000000cb800000 - 00000000cfa00000 (reserved) > > [ 0.000000] Xen: 00000000fec00000 - 00000000fec01000 (reserved) > > [ 0.000000] Xen: 00000000fed1c000 - 00000000fed20000 (reserved) > > [ 0.000000] Xen: 00000000fee00000 - 00000000fee01000 (reserved) > > [ 0.000000] Xen: 00000000ffc00000 - 00000000ffc20000 (reserved) > > [ 0.000000] Xen: 0000000100000000 - 000000042e000000 (usable) > > [ 0.000000] NX (Execute Disable) protection: active > > [ 0.000000] DMI 2.6 present. > > [ 0.000000] DMI: Dell Inc. Latitude E6420/0K0DNP, BIOS A13 05/17/2012 > > [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 > (usable) ==> (reserved) > > [ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 > (usable) > > [ 0.000000] No AGP bridge found > > [ 0.000000] last_pfn = 0x42e000 max_arch_pfn = 0x400000000 > > [ 0.000000] x2apic enabled by BIOS, switching to x2apic ops > > [ 0.000000] last_pfn = 0xcac00 max_arch_pfn = 0x400000000 > > [ 0.000000] found SMP MP-table at [ffff8800000f1ad0] f1ad0 > > [ 0.000000] initial memory mapped : 0 - 04ade000 > > [ 0.000000] Base memory trampoline at [ffff880000095000] 95000 size > 20480 > > [ 0.000000] init_memory_mapping: 0000000000000000-00000000cac00000 > > [ 0.000000] 0000000000 - 00cac00000 page 4k > > [ 0.000000] kernel direct mapping tables up to 0xcabfffff @ [mem > 0x009a5000-0x00ffffff] > > [ 0.000000] xen: setting RW the range fc4000 - 1000000 > > [ 0.000000] init_memory_mapping: 0000000100000000-000000042e000000 > > [ 0.000000] 0100000000 - 042e000000 page 4k > > [ 0.000000] kernel direct mapping tables up to 0x42dffffff @ [mem > 0xc9282000-0xcabfffff] > > [ 0.000000] xen: setting RW the range cabff000 - cac00000 > > [ 0.000000] RAMDISK: 01e13000 - 04ade000 > > [ 0.000000] ACPI: RSDP 00000000000fe300 00024 (v02 DELL ) > > [ 0.000000] ACPI: XSDT 000000000dffee18 0007C (v01 DELL CBX3 > 06222004 MSFT 00010013) > > [ 0.000000] ACPI: FACP 0000000007f90d98 000F4 (v04 DELL CBX3 > 06222004 MSFT 00010013) > > [ 0.000000] ACPI Warning: 32/64 FACS address mismatch in FADT - two > FACS tables! (20120320/tbfadt-378) > > [ 0.000000] ACPI Warning: 32/64X FACS address mismatch in FADT - > 0x07FEDE40/0x0000000007FEDD40, using 32 (20120320/tbfadt-502) > > [ 0.000000] ACPI: DSDT 0000000007f5e018 08834 (v02 INT430 SYSFexxx > 00001001 INTL 20090903) > > [ 0.000000] ACPI: FACS 0000000007fede40 00040 > > [ 0.000000] ACPI: APIC 000000000dffdf18 000CC (v02 DELL CBX3 > 06222004 MSFT 00010013) > > [ 0.000000] ACPI: TCPA 0000000007feed18 00032 (v02 > 00000000 00000000) > > [ 0.000000] ACPI: SSDT 0000000007f91a98 002F9 (v01 DELLTP TPM > 00003000 INTL 20090903) > > [ 0.000000] ACPI: MCFG 0000000007feec98 0003C (v01 DELL SNDYBRDG > 06222004 MSFT 00000097) > > [ 0.000000] ACPI: HPET 0000000007feec18 00038 (v01 A M I PCHHPET > 06222004 AMI. 00000003) > > [ 0.000000] ACPI: BOOT 0000000007feeb98 00028 (v01 DELL CBX3 > 06222004 AMI 00010013) > > [ 0.000000] ACPI: SSDT 0000000007f75018 00804 (v01 PmRef Cpu0Ist > 00003000 INTL 20090903) > > [ 0.000000] ACPI: SSDT 0000000007f74018 00996 (v01 PmRef CpuPm > 00003000 INTL 20090903) > > [ 0.000000] ACPI: XMAR 0000000007f90c18 000E8 (v01 INTEL SNB > 00000001 INTL 00000001) > > [ 0.000000] ACPI: SLIC 0000000007f7ec18 00176 (v03 DELL CBX3 > 06222004 MSFT 00010013) > > [ 0.000000] ACPI: Local APIC address 0xfee00000 > > [ 0.000000] Setting APIC routing to cluster x2apic. > > [ 0.000000] Zone PFN ranges: > > [ 0.000000] DMA 0x00000010 -> 0x00001000 > > [ 0.000000] DMA32 0x00001000 -> 0x00100000 > > [ 0.000000] Normal 0x00100000 -> 0x0042e000 > > [ 0.000000] Movable zone start PFN for each node > > [ 0.000000] Early memory PFN ranges > > [ 0.000000] 0: 0x00000010 -> 0x0000009a > > [ 0.000000] 0: 0x00000100 -> 0x00007eea > > [ 0.000000] 0: 0x00007f67 -> 0x00007f70 > > [ 0.000000] 0: 0x00007f76 -> 0x00007f78 > > [ 0.000000] 0: 0x00008000 -> 0x0000dffd > > [ 0.000000] 0: 0x0000e000 -> 0x00020000 > > [ 0.000000] 0: 0x00020200 -> 0x00040000 > > [ 0.000000] 0: 0x00040200 -> 0x000c83b4 > > [ 0.000000] 0: 0x000c840a -> 0x000c840e > > [ 0.000000] 0: 0x000c840f -> 0x000c8411 > > [ 0.000000] 0: 0x000c8414 -> 0x000c841e > > [ 0.000000] 0: 0x000c8428 -> 0x000c8432 > > [ 0.000000] 0: 0x000c8436 -> 0x000cac00 > > [ 0.000000] 0: 0x00100000 -> 0x0042e000 > > [ 0.000000] On node 0 totalpages: 4163092 > > [ 0.000000] DMA zone: 56 pages used for memmap > > [ 0.000000] DMA zone: 1572 pages reserved > > [ 0.000000] DMA zone: 2350 pages, LIFO batch:0 > > [ 0.000000] DMA32 zone: 14280 pages used for memmap > > [ 0.000000] DMA32 zone: 810690 pages, LIFO batch:31 > > [ 0.000000] Normal zone: 45584 pages used for memmap > > [ 0.000000] Normal zone: 3288560 pages, LIFO batch:31 > > [ 0.000000] ACPI: PM-Timer IO Port: 0x408 > > [ 0.000000] ACPI: Local APIC address 0xfee00000 > > [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) > > [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) > > [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled) > > [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled) > > [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x04] disabled) > > [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] disabled) > > [ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x06] disabled) > > [ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] disabled) > > [ 0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x08] disabled) > > [ 0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x09] disabled) > > [ 0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0a] disabled) > > [ 0.000000] ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x0b] disabled) > > [ 0.000000] ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x0c] disabled) > > [ 0.000000] ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x0d] disabled) > > [ 0.000000] ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x0e] disabled) > > [ 0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x0f] disabled) > > [ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) > > [ 0.000000] IOAPIC[0]: apic_id 2, version 253, address 0xfec00000, > GSI 0-253 > > [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > > [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high > level) > > [ 0.000000] ACPI: IRQ0 used by override. > > [ 0.000000] ACPI: IRQ2 used by override. > > [ 0.000000] ACPI: IRQ9 used by override. > > [ 0.000000] Using ACPI (MADT) for SMP configuration information > > [ 0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000 > > [ 0.000000] SMP: Allowing 16 CPUs, 12 hotplug CPUs > > [ 0.000000] nr_irqs_gsi: 270 > > [ 0.000000] Allocating PCI resources starting at cfa00000 (gap: > cfa00000:2f200000) > > [ 0.000000] Booting paravirtualized kernel on Xen > > [ 0.000000] Xen version: 4.1.3 (preserve-AD) > > [ 0.000000] setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 > nr_cpu_ids:16 nr_node_ids:1 > > [ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff8803e2800000 s82176 > r8192 d24320 u131072 > > [ 0.000000] pcpu-alloc: s82176 r8192 d24320 u131072 alloc=1*2097152 > > [ 0.000000] pcpu-alloc: [0] 00 01 02 03 04 05 06 07 08 09 10 11 12 13 > 14 15 > > [ 4.119805] Built 1 zonelists in Zone order, mobility grouping on. > Total pages: 4101600 > > [ 4.119809] Kernel command line: ro root=/dev/mapper/vg_dom0-lv_root > rd_LUKS_UUID=luks-400336fa-c7c4-4be3-a244-c909aa16a18c > rd_LVM_LV=vg_dom0/lv_root rd_LVM_LV=vg_dom0/lv_swap rd_NO_MD rd_NO_DM > LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=pl2 rhgb quiet > max_loop=255 > > [ 4.119915] PID hash table entries: 4096 (order: 3, 32768 bytes) > > [ 4.120928] Dentry cache hash table entries: 2097152 (order: 12, > 16777216 bytes) > > [ 4.124018] Inode-cache hash table entries: 1048576 (order: 11, > 8388608 bytes) > > [ 4.147064] Placing 64MB software IO TLB between ffff8803ce200000 - > ffff8803d2200000 > > [ 4.147066] software IO TLB at phys 0x3ce200000 - 0x3d2200000 > > [ 4.181675] Memory: 14975940k/17530880k available (4557k kernel code, > 878512k absent, 1676428k reserved, 4112k data, 552k init) > > [ 4.181730] Hierarchical RCU implementation. > > [ 4.181731] RCU dyntick-idle grace-period acceleration is > enabled. > > [ 4.181738] NR_IRQS:33024 nr_irqs:1024 16 > > [ 4.181799] xen: sci override: global_irq=9 trigger=0 polarity=0 > > [ 4.181801] xen: registering gsi 9 triggering 0 polarity 0 > > [ 4.181809] xen: --> pirq=9 -> irq=9 (gsi=9) > > [ 4.181829] xen: acpi sci 9 > > [ 4.181831] xen: --> pirq=1 -> irq=1 (gsi=1) > > [ 4.181834] xen: --> pirq=2 -> irq=2 (gsi=2) > > [ 4.181836] xen: --> pirq=3 -> irq=3 (gsi=3) > > [ 4.181838] xen: --> pirq=4 -> irq=4 (gsi=4) > > [ 4.181840] xen: --> pirq=5 -> irq=5 (gsi=5) > > [ 4.181843] xen: --> pirq=6 -> irq=6 (gsi=6) > > [ 4.181845] xen: --> pirq=7 -> irq=7 (gsi=7) > > [ 4.181847] xen: --> pirq=8 -> irq=8 (gsi=8) > > [ 4.181849] xen: --> pirq=10 -> irq=10 (gsi=10) > > [ 4.181851] xen: --> pirq=11 -> irq=11 (gsi=11) > > [ 4.181854] xen: --> pirq=12 -> irq=12 (gsi=12) > > [ 4.181856] xen: --> pirq=13 -> irq=13 (gsi=13) > > [ 4.181858] xen: --> pirq=14 -> irq=14 (gsi=14) > > [ 4.181860] xen: --> pirq=15 -> irq=15 (gsi=15) > > [ 4.182986] Console: colour VGA+ 80x25 > > [ 4.183012] console [tty0] enabled > > [ 4.183026] Xen: using vcpuop timer interface > > [ 4.183030] installing Xen timer for CPU 0 > > [ 4.183048] Detected 2494.416 MHz processor. > > [ 4.183052] Calibrating delay loop (skipped), value calculated using > timer frequency.. 4988.83 BogoMIPS (lpj=9977664) > > [ 4.183054] pid_max: default: 32768 minimum: 301 > > [ 4.183090] Mount-cache hash table entries: 256 > > [ 4.183222] Initializing cgroup subsys cpuacct > > [ 4.183224] Initializing cgroup subsys devices > > [ 4.183225] Initializing cgroup subsys freezer > > [ 4.183227] Initializing cgroup subsys net_cls > > [ 4.183228] Initializing cgroup subsys blkio > > [ 4.183280] ENERGY_PERF_BIAS: Set to ''normal'', was ''performance'' > > [ 4.183281] ENERGY_PERF_BIAS: View and update with > x86_energy_perf_policy(8) > > [ 4.183284] CPU: Physical Processor ID: 0 > > [ 4.183285] CPU: Processor Core ID: 0 > > [ 4.184454] ACPI: Core revision 20120320 > > [ 4.194658] Performance Events: unsupported p6 CPU model 42 no PMU > driver, software events only. > > [ 4.194796] installing Xen timer for CPU 1 > > [ 4.194988] installing Xen timer for CPU 2 > > [ 4.195140] installing Xen timer for CPU 3 > > [ 4.195232] Brought up 4 CPUs > > [ 4.195477] devtmpfs: initialized > > [ 4.199046] PM: Registering ACPI NVS region [mem > 0x07eea000-0x07f66fff] (512000 bytes) > > [ 4.199056] PM: Registering ACPI NVS region [mem > 0x07f70000-0x07f75fff] (24576 bytes) > > [ 4.199058] PM: Registering ACPI NVS region [mem > 0x07f78000-0x07ffffff] (557056 bytes) > > [ 4.199069] Dell Latitude E6420 series board detected. Selecting > PCI-method for reboots. > > [ 4.199104] Grant tables using version 2 layout. > > [ 4.199114] Grant table initialized > > [ 4.199158] dummy: > > [ 4.199205] RTC time: 1:19:35, date: 11/29/12 > > [ 4.199256] NET: Registered protocol family 16 > > [ 4.199465] ACPI FADT declares the system doesn''t support PCIe ASPM, > so disable it > > [ 4.199467] ACPI: bus type pci registered > > [ 4.199548] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem > 0xf8000000-0xfbffffff] (base 0xf8000000) > > [ 4.199550] PCI: not using MMCONFIG > > [ 4.199552] PCI: Using configuration type 1 for base access > > [ 4.199559] dmi type 0xB1 record - unknown flag > > [ 4.200155] bio: create slab <bio-0> at 0 > > [ 4.200279] ACPI: Added _OSI(Module Device) > > [ 4.200280] ACPI: Added _OSI(Processor Device) > > [ 4.200282] ACPI: Added _OSI(3.0 _SCP Extensions) > > [ 4.200283] ACPI: Added _OSI(Processor Aggregator Device) > > [ 4.201815] ACPI: EC: Look up EC in DSDT > > [ 4.206932] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored > > [ 4.219266] ACPI: SSDT 00000000c8412798 00727 (v01 PmRef Cpu0Cst > 00003001 INTL 20090903) > > [ 4.219654] ACPI: Dynamic OEM Table Load: > > [ 4.219657] ACPI: SSDT (null) 00727 (v01 PmRef Cpu0Cst > 00003001 INTL 20090903) > > [ 4.220118] ACPI: SSDT 00000000c8413a98 00303 (v01 PmRef ApIst > 00003000 INTL 20090903) > > [ 4.220555] ACPI: Dynamic OEM Table Load: > > [ 4.220558] ACPI: SSDT (null) 00303 (v01 PmRef ApIst > 00003000 INTL 20090903) > > [ 4.220754] ACPI: SSDT 00000000c8411d98 00119 (v01 PmRef ApCst > 00003000 INTL 20090903) > > [ 4.221136] ACPI: Dynamic OEM Table Load: > > [ 4.221138] ACPI: SSDT (null) 00119 (v01 PmRef ApCst > 00003000 INTL 20090903) > > [ 4.223275] ACPI: Interpreter enabled > > [ 4.223278] ACPI: (supports S0 S3 S5) > > [ 4.223294] ACPI: Using IOAPIC for interrupt routing > > [ 4.223322] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem > 0xf8000000-0xfbffffff] (base 0xf8000000) > > [ 4.223846] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in > ACPI motherboard resources > > [ 4.271283] ACPI: EC: GPE = 0x10, I/O: command/status = 0x934, data > 0x930 > > [ 4.272424] ACPI: No dock devices found. > > [ 4.272428] PCI: Using host bridge windows from ACPI; if necessary, > use "pci=nocrs" and report a bug > > [ 4.272988] \_SB_.PCI0:_OSC invalid UUID > > [ 4.272989] _OSC request data:1 8 1f > > [ 4.272992] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e]) > > [ 4.273994] pci_root PNP0A08:00: host bridge window [io > 0x0000-0x0cf7] > > [ 4.273996] pci_root PNP0A08:00: host bridge window [io > 0x0d00-0xffff] > > [ 4.273998] pci_root PNP0A08:00: host bridge window [mem > 0x000a0000-0x000bffff] > > [ 4.274001] pci_root PNP0A08:00: host bridge window [mem > 0xcfa00000-0xfeafffff] > > [ 4.274003] pci_root PNP0A08:00: host bridge window [mem > 0xfed40000-0xfed44fff] > > [ 4.274031] PCI host bridge to bus 0000:00 > > [ 4.274033] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7] > > [ 4.274034] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff] > > [ 4.274036] pci_bus 0000:00: root bus resource [mem > 0x000a0000-0x000bffff] > > [ 4.274038] pci_bus 0000:00: root bus resource [mem > 0xcfa00000-0xfeafffff] > > [ 4.274040] pci_bus 0000:00: root bus resource [mem > 0xfed40000-0xfed44fff] > > [ 4.274054] pci 0000:00:00.0: [8086:0104] type 00 class 0x060000 > > [ 4.274147] pci 0000:00:02.0: [8086:0126] type 00 class 0x030000 > > [ 4.274174] pci 0000:00:02.0: reg 10: [mem 0xe1400000-0xe17fffff > 64bit] > > [ 4.274189] pci 0000:00:02.0: reg 18: [mem 0xd0000000-0xdfffffff > 64bit pref] > > [ 4.274200] pci 0000:00:02.0: reg 20: [io 0x4000-0x403f] > > [ 4.274344] pci 0000:00:16.0: [8086:1c3a] type 00 class 0x078000 > > [ 4.274394] pci 0000:00:16.0: reg 10: [mem 0xe2eb0000-0xe2eb000f > 64bit] > > [ 4.274563] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold > > [ 4.274636] pci 0000:00:19.0: [8086:1502] type 00 class 0x020000 > > [ 4.274681] pci 0000:00:19.0: reg 10: [mem 0xe2e00000-0xe2e1ffff] > > [ 4.274700] pci 0000:00:19.0: reg 14: [mem 0xe2e80000-0xe2e80fff] > > [ 4.274719] pci 0000:00:19.0: reg 18: [io 0x4080-0x409f] > > [ 4.274883] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold > > [ 4.274939] pci 0000:00:1a.0: [8086:1c2d] type 00 class 0x0c0320 > > [ 4.274983] pci 0000:00:1a.0: reg 10: [mem 0xe2e70000-0xe2e703ff] > > [ 4.275185] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold > > [ 4.275243] pci 0000:00:1b.0: [8086:1c20] type 00 class 0x040300 > > [ 4.275278] pci 0000:00:1b.0: reg 10: [mem 0xe2e60000-0xe2e63fff > 64bit] > > [ 4.275456] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold > > [ 4.275509] pci 0000:00:1c.0: [8086:1c10] type 01 class 0x060400 > > [ 4.275702] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold > > [ 4.275760] pci 0000:00:1c.1: [8086:1c12] type 01 class 0x060400 > > [ 4.275953] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold > > [ 4.276011] pci 0000:00:1c.2: [8086:1c14] type 01 class 0x060400 > > [ 4.276205] pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold > > [ 4.276264] pci 0000:00:1c.3: [8086:1c16] type 01 class 0x060400 > > [ 4.276458] pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold > > [ 4.276520] pci 0000:00:1c.5: [8086:1c1a] type 01 class 0x060400 > > [ 4.276711] pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold > > [ 4.276779] pci 0000:00:1d.0: [8086:1c26] type 00 class 0x0c0320 > > [ 4.276823] pci 0000:00:1d.0: reg 10: [mem 0xe2e50000-0xe2e503ff] > > [ 4.277025] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold > > [ 4.277086] pci 0000:00:1f.0: [8086:1c4f] type 00 class 0x060100 > > [ 4.277341] pci 0000:00:1f.2: [8086:1c03] type 00 class 0x010601 > > [ 4.277391] pci 0000:00:1f.2: reg 10: [io 0x40d0-0x40d7] > > [ 4.277410] pci 0000:00:1f.2: reg 14: [io 0x40c0-0x40c3] > > [ 4.277429] pci 0000:00:1f.2: reg 18: [io 0x40b0-0x40b7] > > [ 4.277449] pci 0000:00:1f.2: reg 1c: [io 0x40a0-0x40a3] > > [ 4.277468] pci 0000:00:1f.2: reg 20: [io 0x4060-0x407f] > > [ 4.277486] pci 0000:00:1f.2: reg 24: [mem 0xe2e40000-0xe2e407ff] > > [ 4.277613] pci 0000:00:1f.2: PME# supported from D3hot > > [ 4.277657] pci 0000:00:1f.3: [8086:1c22] type 00 class 0x0c0500 > > [ 4.277694] pci 0000:00:1f.3: reg 10: [mem 0xe2e30000-0xe2e300ff > 64bit] > > [ 4.277749] pci 0000:00:1f.3: reg 20: [io 0x4040-0x405f] > > [ 4.277920] pci 0000:00:1c.0: PCI bridge to [bus 01-01] > > [ 4.278353] pci 0000:02:00.0: [8086:422b] type 00 class 0x028000 > > [ 4.278708] pci 0000:02:00.0: reg 10: [mem 0xe2d00000-0xe2d01fff > 64bit] > > [ 4.280508] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold > > [ 4.285361] pci 0000:00:1c.1: PCI bridge to [bus 02-02] > > [ 4.285374] pci 0000:00:1c.1: bridge window [mem > 0xe2d00000-0xe2dfffff] > > [ 4.285490] pci 0000:00:1c.2: PCI bridge to [bus 03-08] > > [ 4.285498] pci 0000:00:1c.2: bridge window [io 0x3000-0x3fff] > > [ 4.285505] pci 0000:00:1c.2: bridge window [mem > 0xe2200000-0xe2bfffff] > > [ 4.285517] pci 0000:00:1c.2: bridge window [mem > 0xe0a00000-0xe13fffff 64bit pref] > > [ 4.285625] pci 0000:00:1c.3: PCI bridge to [bus 09-09] > > [ 4.285632] pci 0000:00:1c.3: bridge window [io 0x2000-0x2fff] > > [ 4.285639] pci 0000:00:1c.3: bridge window [mem > 0xe1800000-0xe21fffff] > > [ 4.285651] pci 0000:00:1c.3: bridge window [mem > 0xe0000000-0xe09fffff 64bit pref] > > [ 4.285818] pci 0000:0a:00.0: [1217:8221] type 00 class 0x080501 > > [ 4.285872] pci 0000:0a:00.0: reg 10: [mem 0xe2c20000-0xe2c201ff] > > [ 4.286294] pci 0000:0a:00.0: supports D1 D2 > > [ 4.286295] pci 0000:0a:00.0: PME# supported from D0 D1 D2 D3hot > D3cold > > [ 4.286432] pci 0000:0a:00.1: [1217:8231] type 00 class 0x018000 > > [ 4.286486] pci 0000:0a:00.1: reg 10: [mem 0xe2c10000-0xe2c10fff] > > [ 4.286563] pci 0000:0a:00.1: reg 18: [mem 0xe2c00000-0xe2c007ff] > > [ 4.286908] pci 0000:0a:00.1: supports D1 D2 > > [ 4.286909] pci 0000:0a:00.1: PME# supported from D0 D1 D2 D3hot > D3cold > > [ 4.293400] pci 0000:00:1c.5: PCI bridge to [bus 0a-0a] > > [ 4.293412] pci 0000:00:1c.5: bridge window [mem > 0xe2c00000-0xe2cfffff] > > [ 4.293479] pci_bus 0000:00: on NUMA node 0 > > [ 4.293483] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] > > [ 4.293612] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT] > > [ 4.293647] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP02._PRT] > > [ 4.293682] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP04._PRT] > > [ 4.293717] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP06._PRT] > > [ 4.293762] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP03._PRT] > > [ 4.293857] \_SB_.PCI0:_OSC invalid UUID > > [ 4.293858] _OSC request data:1 1f 1f > > [ 4.293861] pci0000:00: Requesting ACPI _OSC control (0x1d) > > [ 4.293906] \_SB_.PCI0:_OSC invalid UUID > > [ 4.293907] _OSC request data:1 0 1d > > [ 4.293910] pci0000:00: ACPI _OSC request failed (AE_ERROR), > returned control mask: 0x1d > > [ 4.293911] ACPI _OSC control for PCIe not granted, disabling ASPM > > [ 4.297639] ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 12 > 14 15) *11 > > [ 4.297702] ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 11 12 > 14 15) *10 > > [ 4.297761] ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 12 > 14 15) *11 > > [ 4.297820] ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 11 12 > 14 15) *10 > > [ 4.297878] ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 *5 6 7 10 12 > 14 15) > > [ 4.297937] ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 11 12 > 14 15) *0, disabled. > > [ 4.297996] ACPI: PCI Interrupt Link [LNKG] (IRQs 1 *3 4 5 6 7 10 12 > 14 15) > > [ 4.298054] ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 7 11 12 > 14 15) *0, disabled. > > [ 4.298087] xen/balloon: Initialising balloon driver. > > [ 4.301022] xen-balloon: Initialising balloon driver. > > [ 4.301062] xen/balloon: Xen selfballooning driver disabled for > domain0. > > [ 4.301148] vgaarb: device added: > PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none > > [ 4.301157] vgaarb: loaded > > [ 4.301157] vgaarb: bridge control possible 0000:00:02.0 > > [ 4.301279] PCI: Using ACPI for IRQ routing > > [ 4.305930] PCI: pci_cache_line_size set to 64 bytes > > [ 4.306106] reserve RAM buffer: 000000000009a000 - 000000000009ffff > > [ 4.306108] reserve RAM buffer: 0000000007eea000 - 0000000007ffffff > > [ 4.306110] reserve RAM buffer: 0000000007f70000 - 0000000007ffffff > > [ 4.306112] reserve RAM buffer: 0000000007f78000 - 0000000007ffffff > > [ 4.306113] reserve RAM buffer: 000000000dffd000 - 000000000fffffff > > [ 4.306115] reserve RAM buffer: 00000000c83b4000 - 00000000cbffffff > > [ 4.306118] reserve RAM buffer: 00000000c840e000 - 00000000cbffffff > > [ 4.306121] reserve RAM buffer: 00000000c8411000 - 00000000cbffffff > > [ 4.306123] reserve RAM buffer: 00000000c841e000 - 00000000cbffffff > > [ 4.306125] reserve RAM buffer: 00000000c8432000 - 00000000cbffffff > > [ 4.306127] reserve RAM buffer: 00000000cac00000 - 00000000cbffffff > > [ 4.306129] reserve RAM buffer: 000000042e000000 - 000000042fffffff > > [ 4.306235] Switching to clocksource xen > > [ 4.307726] pnp: PnP ACPI init > > [ 4.307738] ACPI: bus type pnp registered > > [ 4.308287] pnp 00:00: [bus 00-3e] > > [ 4.308289] pnp 00:00: [io 0x0000-0x0cf7 window] > > [ 4.308291] pnp 00:00: [io 0x0cf8-0x0cff] > > [ 4.308293] pnp 00:00: [io 0x0d00-0xffff window] > > [ 4.308295] pnp 00:00: [mem 0x000a0000-0x000bffff window] > > [ 4.308296] pnp 00:00: [mem 0x000c0000-0x000c3fff window] > > [ 4.308298] pnp 00:00: [mem 0x000c4000-0x000c7fff window] > > [ 4.308300] pnp 00:00: [mem 0x000c8000-0x000cbfff window] > > [ 4.308301] pnp 00:00: [mem 0x000cc000-0x000cffff window] > > [ 4.308303] pnp 00:00: [mem 0x000d0000-0x000d3fff window] > > [ 4.308305] pnp 00:00: [mem 0x000d4000-0x000d7fff window] > > [ 4.308307] pnp 00:00: [mem 0x000d8000-0x000dbfff window] > > [ 4.308309] pnp 00:00: [mem 0x000dc000-0x000dffff window] > > [ 4.308310] pnp 00:00: [mem 0x000e0000-0x000e3fff window] > > [ 4.308312] pnp 00:00: [mem 0x000e4000-0x000e7fff window] > > [ 4.308314] pnp 00:00: [mem 0x000e8000-0x000ebfff window] > > [ 4.308315] pnp 00:00: [mem 0x000ec000-0x000effff window] > > [ 4.308317] pnp 00:00: [mem 0x000f0000-0x000fffff window] > > [ 4.308319] pnp 00:00: [mem 0xcfa00000-0xfeafffff window] > > [ 4.308320] pnp 00:00: [mem 0xfed40000-0xfed44fff window] > > [ 4.308385] pnp 00:00: Plug and Play ACPI device, IDs PNP0a08 PNP0a03 > (active) > > [ 4.308398] pnp 00:01: [io 0x0000-0x001f] > > [ 4.308400] pnp 00:01: [io 0x0081-0x0091] > > [ 4.308401] pnp 00:01: [io 0x0093-0x009f] > > [ 4.308403] pnp 00:01: [io 0x00c0-0x00df] > > [ 4.308404] pnp 00:01: [dma 4] > > [ 4.308422] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active) > > [ 4.308429] pnp 00:02: [mem 0xff000000-0xffffffff] > > [ 4.308445] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active) > > [ 4.308540] pnp 00:03: [mem 0xfed00000-0xfed003ff] > > [ 4.308572] system 00:03: [mem 0xfed00000-0xfed003ff] has been > reserved > > [ 4.308575] system 00:03: Plug and Play ACPI device, IDs PNP0103 > PNP0c01 (active) > > [ 4.308584] pnp 00:04: [io 0x00f0] > > [ 4.308587] xen: registering gsi 13 triggering 1 polarity 0 > > [ 4.308609] pnp 00:04: [irq 13] > > [ 4.308626] pnp 00:04: Plug and Play ACPI device, IDs PNP0c04 (active) > > [ 4.308636] pnp 00:05: [io 0x002e-0x002f] > > [ 4.308637] pnp 00:05: [io 0x004e-0x004f] > > [ 4.308639] pnp 00:05: [io 0x0061] > > [ 4.308640] pnp 00:05: [io 0x0063] > > [ 4.308641] pnp 00:05: [io 0x0065] > > [ 4.308642] pnp 00:05: [io 0x0067] > > [ 4.308644] pnp 00:05: [io 0x0070] > > [ 4.308645] pnp 00:05: [io 0x0080] > > [ 4.308646] pnp 00:05: [io 0x0092] > > [ 4.308648] pnp 00:05: [io 0x00b2-0x00b3] > > [ 4.308649] pnp 00:05: [io 0x0680-0x069f] > > [ 4.308651] pnp 00:05: [io 0x1000-0x100f] > > [ 4.308653] pnp 00:05: [io 0xffff] > > [ 4.308654] pnp 00:05: [io 0xffff] > > [ 4.308655] pnp 00:05: [io 0x0400-0x047f] > > [ 4.308656] pnp 00:05: [io 0x0500-0x057f] > > [ 4.308658] pnp 00:05: [io 0x164e-0x164f] > > [ 4.308689] system 00:05: [io 0x0680-0x069f] has been reserved > > [ 4.308691] system 00:05: [io 0x1000-0x100f] has been reserved > > [ 4.308693] system 00:05: [io 0xffff] has been reserved > > [ 4.308695] system 00:05: [io 0xffff] has been reserved > > [ 4.308697] system 00:05: [io 0x0400-0x047f] has been reserved > > [ 4.308700] system 00:05: [io 0x0500-0x057f] has been reserved > > [ 4.308701] system 00:05: [io 0x164e-0x164f] has been reserved > > [ 4.308704] system 00:05: Plug and Play ACPI device, IDs PNP0c02 > (active) > > [ 4.308711] pnp 00:06: [io 0x0070-0x0077] > > [ 4.308713] xen: registering gsi 8 triggering 1 polarity 0 > > [ 4.308730] pnp 00:06: [irq 8] > > [ 4.308749] pnp 00:06: Plug and Play ACPI device, IDs PNP0b00 (active) > > [ 4.308758] pnp 00:07: [io 0x0060] > > [ 4.308759] pnp 00:07: [io 0x0064] > > [ 4.308761] xen: registering gsi 1 triggering 1 polarity 0 > > [ 4.308777] pnp 00:07: [irq 1] > > [ 4.308794] pnp 00:07: Plug and Play ACPI device, IDs PNP0303 (active) > > [ 4.309984] pnp 00:08: Plug and Play ACPI device, IDs PNP0401 > (disabled) > > [ 4.309993] xen: registering gsi 12 triggering 1 polarity 0 > > [ 4.310011] pnp 00:09: [irq 12] > > [ 4.310030] pnp 00:09: Plug and Play ACPI device, IDs DLL0493 PNP0f13 > (active) > > [ 4.310065] pnp 00:0a: [mem 0xfed40000-0xfed44fff] > > [ 4.310086] pnp 00:0a: Plug and Play ACPI device, IDs BCM0102 PNP0c31 > (active) > > [ 4.310291] pnp 00:0b: [mem 0xfed1c000-0xfed1ffff] > > [ 4.310292] pnp 00:0b: [mem 0xfed10000-0xfed17fff] > > [ 4.310294] pnp 00:0b: [mem 0xfed18000-0xfed18fff] > > [ 4.310296] pnp 00:0b: [mem 0xfed19000-0xfed19fff] > > [ 4.310298] pnp 00:0b: [mem 0xf8000000-0xfbffffff] > > [ 4.310309] pnp 00:0b: [mem 0xfed20000-0xfed3ffff] > > [ 4.310310] pnp 00:0b: [mem 0xfed90000-0xfed93fff] > > [ 4.310312] pnp 00:0b: [mem 0xfed45000-0xfed8ffff] > > [ 4.310313] pnp 00:0b: [mem 0xff000000-0xffffffff] > > [ 4.310315] pnp 00:0b: [mem 0xfee00000-0xfeefffff] > > [ 4.310317] pnp 00:0b: [mem 0x00000000-0xffffffffffffffff disabled] > > [ 4.310318] pnp 00:0b: [mem 0x00000000-0xffffffffffffffff disabled] > > [ 4.310359] system 00:0b: [mem 0xfed1c000-0xfed1ffff] has been > reserved > > [ 4.310361] system 00:0b: [mem 0xfed10000-0xfed17fff] has been > reserved > > [ 4.310363] system 00:0b: [mem 0xfed18000-0xfed18fff] has been > reserved > > [ 4.310365] system 00:0b: [mem 0xfed19000-0xfed19fff] has been > reserved > > [ 4.310367] system 00:0b: [mem 0xf8000000-0xfbffffff] has been > reserved > > [ 4.310369] system 00:0b: [mem 0xfed20000-0xfed3ffff] has been > reserved > > [ 4.310371] system 00:0b: [mem 0xfed90000-0xfed93fff] has been > reserved > > [ 4.310373] system 00:0b: [mem 0xfed45000-0xfed8ffff] has been > reserved > > [ 4.310375] system 00:0b: [mem 0xff000000-0xffffffff] could not be > reserved > > [ 4.310377] system 00:0b: [mem 0xfee00000-0xfeefffff] could not be > reserved > > [ 4.310380] system 00:0b: Plug and Play ACPI device, IDs PNP0c02 > (active) > > [ 4.310956] xen: registering gsi 23 triggering 1 polarity 0 > > [ 4.310967] xen: --> pirq=23 -> irq=23 (gsi=23) > > [ 4.310985] pnp 00:0c: [irq 23] > > [ 4.311015] pnp 00:0c: Plug and Play ACPI device, IDs SMO8800 (active) > > [ 4.315528] pnp 00:0d: [mem 0x20000000-0x201fffff] > > [ 4.315531] pnp 00:0d: [mem 0x40000000-0x401fffff] > > [ 4.339851] system 00:0d: [mem 0x20000000-0x201fffff] has been > reserved > > [ 4.339854] system 00:0d: [mem 0x40000000-0x401fffff] has been > reserved > > [ 4.339857] system 00:0d: Plug and Play ACPI device, IDs PNP0c01 > (active) > > [ 4.339865] pnp: PnP ACPI: found 14 devices > > [ 4.339867] ACPI: ACPI bus type pnp unregistered > > [ 4.346178] PM-Timer failed consistency check (0x0xffffff) - > aborting. > > [ 4.346274] pci 0000:00:1c.0: PCI bridge to [bus 01-01] > > [ 4.346306] pci 0000:00:1c.1: PCI bridge to [bus 02-02] > > [ 4.346315] pci 0000:00:1c.1: bridge window [mem > 0xe2d00000-0xe2dfffff] > > [ 4.346332] pci 0000:00:1c.2: PCI bridge to [bus 03-08] > > [ 4.346336] pci 0000:00:1c.2: bridge window [io 0x3000-0x3fff] > > [ 4.346347] pci 0000:00:1c.2: bridge window [mem > 0xe2200000-0xe2bfffff] > > [ 4.346354] pci 0000:00:1c.2: bridge window [mem > 0xe0a00000-0xe13fffff 64bit pref] > > [ 4.346366] pci 0000:00:1c.3: PCI bridge to [bus 09-09] > > [ 4.346370] pci 0000:00:1c.3: bridge window [io 0x2000-0x2fff] > > [ 4.346379] pci 0000:00:1c.3: bridge window [mem > 0xe1800000-0xe21fffff] > > [ 4.346386] pci 0000:00:1c.3: bridge window [mem > 0xe0000000-0xe09fffff 64bit pref] > > [ 4.346399] pci 0000:00:1c.5: PCI bridge to [bus 0a-0a] > > [ 4.346408] pci 0000:00:1c.5: bridge window [mem > 0xe2c00000-0xe2cfffff] > > [ 4.346434] xen: registering gsi 16 triggering 0 polarity 1 > > [ 4.346442] xen: --> pirq=16 -> irq=16 (gsi=16) > > [ 4.346469] xen: registering gsi 17 triggering 0 polarity 1 > > [ 4.346473] xen: --> pirq=17 -> irq=17 (gsi=17) > > [ 4.346498] xen: registering gsi 18 triggering 0 polarity 1 > > [ 4.346502] xen: --> pirq=18 -> irq=18 (gsi=18) > > [ 4.346527] xen: registering gsi 19 triggering 0 polarity 1 > > [ 4.346531] xen: --> pirq=19 -> irq=19 (gsi=19) > > [ 4.346556] xen: registering gsi 17 triggering 0 polarity 1 > > [ 4.346558] Already setup the GSI :17 > > [ 4.346563] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7] > > [ 4.346565] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff] > > [ 4.346566] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff] > > [ 4.346568] pci_bus 0000:00: resource 7 [mem 0xcfa00000-0xfeafffff] > > [ 4.346570] pci_bus 0000:00: resource 8 [mem 0xfed40000-0xfed44fff] > > [ 4.346572] pci_bus 0000:02: resource 1 [mem 0xe2d00000-0xe2dfffff] > > [ 4.346574] pci_bus 0000:03: resource 0 [io 0x3000-0x3fff] > > [ 4.346575] pci_bus 0000:03: resource 1 [mem 0xe2200000-0xe2bfffff] > > [ 4.346577] pci_bus 0000:03: resource 2 [mem 0xe0a00000-0xe13fffff > 64bit pref] > > [ 4.346579] pci_bus 0000:09: resource 0 [io 0x2000-0x2fff] > > [ 4.346581] pci_bus 0000:09: resource 1 [mem 0xe1800000-0xe21fffff] > > [ 4.346582] pci_bus 0000:09: resource 2 [mem 0xe0000000-0xe09fffff > 64bit pref] > > [ 4.346584] pci_bus 0000:0a: resource 1 [mem 0xe2c00000-0xe2cfffff] > > [ 4.346672] NET: Registered protocol family 2 > > [ 4.346732] IP route cache hash table entries: 524288 (order: 10, > 4194304 bytes) > > [ 4.347207] TCP established hash table entries: 262144 (order: 10, > 4194304 bytes) > > [ 4.347753] TCP bind hash table entries: 65536 (order: 8, 1048576 > bytes) > > [ 4.347872] TCP: Hash tables configured (established 262144 bind > 65536) > > [ 4.347874] TCP: reno registered > > [ 4.347877] UDP hash table entries: 8192 (order: 6, 262144 bytes) > > [ 4.347921] UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes) > > [ 4.348067] NET: Registered protocol family 1 > > [ 4.348085] pci 0000:00:02.0: Boot video device > > [ 4.348108] xen: registering gsi 16 triggering 0 polarity 1 > > [ 4.348112] Already setup the GSI :16 > > [ 4.348203] xen: registering gsi 17 triggering 0 polarity 1 > > [ 4.348205] Already setup the GSI :17 > > [ 4.348298] PCI: CLS 64 bytes, default 64 > > [ 4.348333] Unpacking initramfs... > > [ 4.384265] Freeing initrd memory: 45868k freed > > [ 4.392440] Simple Boot Flag at 0xf3 set to 0x1 > > [ 4.392900] audit: initializing netlink socket (disabled) > > [ 4.392911] type=2000 audit(1354151975.383:1): initialized > > [ 4.411688] VFS: Disk quotas dquot_6.5.2 > > [ 4.411715] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) > > [ 4.411870] msgmni has been set to 29339 > > [ 4.412010] Block layer SCSI generic (bsg) driver version 0.4 loaded > (major 253) > > [ 4.412013] io scheduler noop registered > > [ 4.412015] io scheduler deadline registered > > [ 4.412036] io scheduler cfq registered (default) > > [ 4.412666] intel_idle: does not run on family 6 model 42 > > [ 4.412741] ACPI: Requesting acpi_cpufreq > > [ 4.459643] Non-volatile memory driver v1.3 > > [ 4.459654] ramoops: platform device not found, using module > parameters > > [ 4.459670] ramoops: The memory size and the record size must be > non-zero > > [ 4.459703] ramoops: probe of ramoops failed with error -22 > > [ 4.474892] loop: module loaded > > [ 4.474922] Fixed MDIO Bus: probed > > [ 4.474965] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] > at 0x60,0x64 irq 1,12 > > [ 4.475166] i8042: Warning: Keylock active > > [ 4.476434] serio: i8042 KBD port at 0x60,0x64 irq 1 > > [ 4.476439] serio: i8042 AUX port at 0x60,0x64 irq 12 > > [ 4.476551] mousedev: PS/2 mouse device common for all mice > > [ 4.476707] rtc_cmos 00:06: RTC can wake from S4 > > [ 4.476940] rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0 > > [ 4.476998] rtc0: alarms up to one year, y3k, 242 bytes nvram > > [ 4.477084] device-mapper: uevent: version 1.0.3 > > [ 4.477193] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) > initialised: dm-devel@redhat.com > > [ 4.477281] TCP: cubic registered > > [ 4.477381] input: AT Translated Set 2 keyboard as > /devices/platform/i8042/serio0/input/input0 > > [ 4.477402] NET: Registered protocol family 10 > > [ 4.477644] Registering the dns_resolver key type > > [ 4.477791] registered taskstats version 1 > > [ 4.478330] Magic number: 4:584:307 > > [ 4.478403] tty tty36: hash matches > > [ 4.478496] rtc_cmos 00:06: setting system clock to 2012-11-29 > 01:19:35 UTC (1354151975) > > [ 4.478801] Freeing unused kernel memory: 552k freed > > [ 4.478847] Write protecting the kernel read-only data: 8192k > > [ 4.481908] Freeing unused kernel memory: 1568k freed > > [ 4.482112] Freeing unused kernel memory: 24k freed > > [ 4.524129] dracut: dracut-005-3.fc13 > > [ 4.552311] pciback 0000:00:19.0: seizing device > > [ 4.552403] pciback 0000:02:00.0: seizing device > > [ 4.552941] xen: registering gsi 17 triggering 0 polarity 1 > > [ 4.552952] Already setup the GSI :17 > > [ 4.553934] xen: registering gsi 20 triggering 0 polarity 1 > > [ 4.553964] xen: --> pirq=20 -> irq=20 (gsi=20) > > [ 4.554574] xen-pciback: backend is vpci > > [ 4.617471] udev: starting version 151 > > [ 4.617770] udevd (80): /proc/80/oom_adj is deprecated, please use > /proc/80/oom_score_adj instead. > > [ 4.654916] Linux agpgart interface v0.103 > > [ 4.655397] input: Lid Switch as > /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input1 > > [ 5.051184] ACPI: Lid Switch [LID] > > [ 5.051436] input: Power Button as > /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2 > > [ 5.051547] ACPI: Power Button [PBTN] > > [ 5.051682] input: Sleep Button as > /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input3 > > [ 5.051760] ACPI: Sleep Button [SBTN] > > [ 5.054141] input: Power Button as > /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 > > [ 5.054421] ACPI: Power Button [PWRF] > > [ 5.056887] agpgart-intel 0000:00:00.0: Intel Sandybridge Chipset > > [ 5.058118] agpgart-intel 0000:00:00.0: detected gtt size: 2097152K > total, 262144K mappable > > [ 5.064439] agpgart-intel 0000:00:00.0: detected 65536K stolen memory > > [ 5.064916] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ > 0xd0000000 > > [ 5.070296] [drm] Initialized drm 1.1.0 20060810 > > [ 5.080002] xen: registering gsi 16 triggering 0 polarity 1 > > [ 5.080015] Already setup the GSI :16 > > [ 5.080364] i915 0000:00:02.0: setting latency timer to 64 > > [ 5.190295] [drm] MTRR allocation failed. Graphics performance may > suffer. > > [ 5.190491] [drm] Supports vblank timestamp caching Rev 1 > (10.10.2010). > > [ 5.190493] [drm] Driver supports precise vblank timestamp query. > > [ 5.190554] vgaarb: device changed decodes: > PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem > > [ 5.548301] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off > > [ 5.591093] input: DualPoint Stick as > /devices/platform/i8042/serio1/input/input5 > > [ 5.606212] input: AlpsPS/2 ALPS DualPoint TouchPad as > /devices/platform/i8042/serio1/input/input6 > > [ 5.806814] fbcon: inteldrmfb (fb0) is primary device > > [ 6.095967] Console: switching to colour frame buffer device 200x56 > > [ 6.101477] fb0: inteldrmfb frame buffer device > > [ 6.101478] drm: registered panic notifier > > [ 6.130833] acpi device:38: registered as cooling_device4 > > [ 6.133713] input: Video Bus as > /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input7 > > [ 6.133915] ACPI: Video Device [VID] (multi-head: yes rom: no post: > no) > > [ 6.135082] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on > minor 0 > > [ 6.185946] dracut: Starting plymouth daemon > > [ 6.479391] dracut: rd_NO_DM: removing DM RAID activation > > [ 6.489309] dracut: rd_NO_MD: removing MD RAID activation > > [ 6.542596] wmi: Mapper loaded > > [ 6.564439] usbcore: registered new interface driver usbfs > > [ 6.564463] usbcore: registered new interface driver hub > > [ 6.568901] SCSI subsystem initialized > > [ 6.569574] usbcore: registered new device driver usb > > [ 6.570692] ehci_hcd: USB 2.0 ''Enhanced'' Host Controller (EHCI) Driver > > [ 6.570723] xen: registering gsi 16 triggering 0 polarity 1 > > [ 6.570728] Already setup the GSI :16 > > [ 6.570776] ehci_hcd 0000:00:1a.0: setting latency timer to 64 > > [ 6.570782] ehci_hcd 0000:00:1a.0: EHCI Host Controller > > [ 6.570814] ehci_hcd 0000:00:1a.0: new USB bus registered, assigned > bus number 1 > > [ 6.570879] ehci_hcd 0000:00:1a.0: debug port 2 > > [ 6.573720] libata version 3.00 loaded. > > [ 6.574777] ehci_hcd 0000:00:1a.0: cache line size of 64 is not > supported > > [ 6.574832] ehci_hcd 0000:00:1a.0: irq 16, io mem 0xe2e70000 > > [ 6.586344] ehci_hcd 0000:00:1a.0: USB 2.0 started, EHCI 1.00 > > [ 6.586369] usb usb1: New USB device found, idVendor=1d6b, > idProduct=0002 > > [ 6.586372] usb usb1: New USB device strings: Mfr=3, Product=2, > SerialNumber=1 > > [ 6.586375] usb usb1: Product: EHCI Host Controller > > [ 6.586376] usb usb1: Manufacturer: Linux 3.4.18-2.pvops.qubes.x86_64 > ehci_hcd > > [ 6.586378] usb usb1: SerialNumber: 0000:00:1a.0 > > [ 6.586506] hub 1-0:1.0: USB hub found > > [ 6.586511] hub 1-0:1.0: 2 ports detected > > [ 6.586604] xen: registering gsi 17 triggering 0 polarity 1 > > [ 6.586609] Already setup the GSI :17 > > [ 6.586663] ehci_hcd 0000:00:1d.0: setting latency timer to 64 > > [ 6.586668] ehci_hcd 0000:00:1d.0: EHCI Host Controller > > [ 6.586678] ehci_hcd 0000:00:1d.0: new USB bus registered, assigned > bus number 2 > > [ 6.586734] ehci_hcd 0000:00:1d.0: debug port 2 > > [ 6.590650] ehci_hcd 0000:00:1d.0: cache line size of 64 is not > supported > > [ 6.590709] ehci_hcd 0000:00:1d.0: irq 17, io mem 0xe2e50000 > > [ 6.606335] ehci_hcd 0000:00:1d.0: USB 2.0 started, EHCI 1.00 > > [ 6.606364] usb usb2: New USB device found, idVendor=1d6b, > idProduct=0002 > > [ 6.606367] usb usb2: New USB device strings: Mfr=3, Product=2, > SerialNumber=1 > > [ 6.606370] usb usb2: Product: EHCI Host Controller > > [ 6.606371] usb usb2: Manufacturer: Linux 3.4.18-2.pvops.qubes.x86_64 > ehci_hcd > > [ 6.606373] usb usb2: SerialNumber: 0000:00:1d.0 > > [ 6.606519] hub 2-0:1.0: USB hub found > > [ 6.606524] hub 2-0:1.0: 2 ports detected > > [ 6.606620] ahci 0000:00:1f.2: version 3.0 > > [ 6.606641] xen: registering gsi 18 triggering 0 polarity 1 > > [ 6.606647] Already setup the GSI :18 > > [ 6.606896] ahci: SSS flag set, parallel bus scan disabled > > [ 6.626400] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps > 0x3b impl SATA mode > > [ 6.626405] ahci 0000:00:1f.2: flags: 64bit ncq sntf stag pm led clo > pio slum part ems sxs apst > > [ 6.626414] ahci 0000:00:1f.2: setting latency timer to 64 > > [ 6.673732] scsi0 : ahci > > [ 6.683363] scsi1 : ahci > > [ 6.697268] scsi2 : ahci > > [ 6.711526] scsi3 : ahci > > [ 6.733931] scsi4 : ahci > > [ 6.739603] scsi5 : ahci > > [ 6.842106] ata1: SATA max UDMA/133 abar m2048@0xe2e40000 port > 0xe2e40100 irq 293 > > [ 6.842118] ata2: SATA max UDMA/133 abar m2048@0xe2e40000 port > 0xe2e40180 irq 293 > > [ 6.842124] ata3: DUMMY > > [ 6.842129] ata4: SATA max UDMA/133 abar m2048@0xe2e40000 port > 0xe2e40280 irq 293 > > [ 6.842136] ata5: SATA max UDMA/133 abar m2048@0xe2e40000 port > 0xe2e40300 irq 293 > > [ 6.842143] ata6: SATA max UDMA/133 abar m2048@0xe2e40000 port > 0xe2e40380 irq 293 > > [ 6.898480] usb 1-1: new high-speed USB device number 2 using ehci_hcd > > [ 7.031312] usb 1-1: New USB device found, idVendor=8087, > idProduct=0024 > > [ 7.031323] usb 1-1: New USB device strings: Mfr=0, Product=0, > SerialNumber=0 > > [ 7.032072] hub 1-1:1.0: USB hub found > > [ 7.032344] hub 1-1:1.0: 6 ports detected > > [ 7.142515] usb 2-1: new high-speed USB device number 2 using ehci_hcd > > [ 7.162484] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) > > [ 7.268594] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by > device (Stat=0x51 Err=0x04) > > [ 7.268770] ata1.00: ATA-9: KINGSTON SV200S3256G, E111008a, max > UDMA/100 > > [ 7.268778] ata1.00: 500118192 sectors, multi 16: LBA48 NCQ (depth > 31/32), AA > > [ 7.272554] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by > device (Stat=0x51 Err=0x04) > > [ 7.272758] ata1.00: configured for UDMA/100 > > [ 7.273314] scsi 0:0:0:0: Direct-Access ATA KINGSTON SV200S3 > E111 PQ: 0 ANSI: 5 > > [ 7.274861] usb 2-1: New USB device found, idVendor=8087, > idProduct=0024 > > [ 7.274870] usb 2-1: New USB device strings: Mfr=0, Product=0, > SerialNumber=0 > > [ 7.275358] hub 2-1:1.0: USB hub found > > [ 7.275521] hub 2-1:1.0: 8 ports detected > > [ 7.346717] usb 1-1.4: new full-speed USB device number 3 using > ehci_hcd > > [ 7.443529] usb 1-1.4: New USB device found, idVendor=413c, > idProduct=8187 > > [ 7.443539] usb 1-1.4: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > > [ 7.443546] usb 1-1.4: Product: DW375 Bluetooth Module > > [ 7.443550] usb 1-1.4: Manufacturer: Dell Computer Corp > > [ 7.443555] usb 1-1.4: SerialNumber: D0DF9A40FE60 > > [ 7.514736] usb 1-1.5: new high-speed USB device number 4 using > ehci_hcd > > [ 7.590440] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > > [ 7.593835] ata2.00: ATAPI: HL-DT-ST DVD+/-RW GU60N, A103, max > UDMA/133 > > [ 7.604147] ata2.00: configured for UDMA/133 > > [ 7.614746] usb 1-1.5: New USB device found, idVendor=05ca, > idProduct=181c > > [ 7.614757] usb 1-1.5: New USB device strings: Mfr=1, Product=2, > SerialNumber=0 > > [ 7.614763] usb 1-1.5: Product: Laptop_Integrated_Webcam_FHD > > [ 7.614768] usb 1-1.5: Manufacturer: CN0CJ3P27248717F040SA01 > > [ 7.618662] scsi 1:0:0:0: CD-ROM HL-DT-ST DVD+-RW GU60N > A103 PQ: 0 ANSI: 5 > > [ 7.686581] usb 2-1.6: new high-speed USB device number 3 using > ehci_hcd > > [ 7.795399] usb 2-1.6: New USB device found, idVendor=413c, > idProduct=818d > > [ 7.795410] usb 2-1.6: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > > [ 7.795416] usb 2-1.6: Product: DW5550 > > [ 7.795420] usb 2-1.6: Manufacturer: Dell > > [ 7.795425] usb 2-1.6: SerialNumber: 88FA653FDF944970 > > [ 7.902770] usb 2-1.8: new full-speed USB device number 4 using > ehci_hcd > > [ 7.938478] ata4: SATA link down (SStatus 0 SControl 300) > > [ 8.017319] usb 2-1.8: New USB device found, idVendor=0a5c, > idProduct=5801 > > [ 8.017330] usb 2-1.8: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > > [ 8.017336] usb 2-1.8: Product: 5880 > > [ 8.017340] usb 2-1.8: Manufacturer: Broadcom Corp > > [ 8.017344] usb 2-1.8: SerialNumber: 0123456789ABCD > > [ 8.017794] usb 2-1.8: config 0 descriptor?? > > [ 8.258411] ata5: SATA link down (SStatus 0 SControl 300) > > [ 8.578480] ata6: SATA link down (SStatus 0 SControl 300) > > [ 8.588630] sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 > GB/238 GiB) > > [ 8.588846] sd 0:0:0:0: [sda] Write Protect is off > > [ 8.588861] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 > > [ 8.588967] sd 0:0:0:0: [sda] Write cache: enabled, read cache: > enabled, doesn''t support DPO or FUA > > [ 8.590122] sda: sda1 sda2 > > [ 8.591059] sd 0:0:0:0: [sda] Attached SCSI disk > > [ 8.609438] sr0: scsi3-mmc drive: 24x/8x writer dvd-ram cd/rw > xa/form2 cdda tray > > [ 8.609451] cdrom: Uniform CD-ROM driver Revision: 3.20 > > [ 8.609737] sr 1:0:0:0: Attached scsi CD-ROM sr0 > > [ 8.714515] dracut: luksOpen /dev/sda2 > luks-400336fa-c7c4-4be3-a244-c909aa16a18c > > [ 13.862564] dracut: Scanning devices dm-0 for LVM logical volumes > vg_dom0/lv_root vg_dom0/lv_swap > > [ 13.907639] dracut: inactive ''/dev/vg_dom0/lv_root'' [221.62 GiB] > inherit > > [ 13.907708] dracut: inactive ''/dev/vg_dom0/lv_swap'' [16.34 GiB] > inherit > > [ 14.162684] EXT4-fs (dm-1): INFO: recovery required on readonly > filesystem > > [ 14.162693] EXT4-fs (dm-1): write access will be enabled during > recovery > > [ 14.775779] EXT4-fs (dm-1): orphan cleanup on readonly fs > > [ 14.775800] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting > unreferenced inode 5767209 > > [ 14.775909] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting > unreferenced inode 5767207 > > [ 14.776007] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting > unreferenced inode 5767205 > > [ 14.776035] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting > unreferenced inode 5767206 > > [ 14.776062] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting > unreferenced inode 5767204 > > [ 14.776088] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting > unreferenced inode 5767202 > > [ 14.776117] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting > unreferenced inode 5767198 > > [ 14.776146] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting > unreferenced inode 5767196 > > [ 14.776172] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting > unreferenced inode 5767191 > > [ 14.776198] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting > unreferenced inode 5767189 > > [ 14.776227] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting > unreferenced inode 5767188 > > [ 14.776274] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting > unreferenced inode 5767187 > > [ 14.777018] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting > unreferenced inode 5767186 > > [ 14.777060] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting > unreferenced inode 5767184 > > [ 14.777089] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting > unreferenced inode 5767183 > > [ 14.777117] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting > unreferenced inode 5767171 > > [ 14.777146] EXT4-fs (dm-1): ext4_orphan_cleanup: deleting > unreferenced inode 5767170 > > [ 14.777172] EXT4-fs (dm-1): 17 orphan inodes deleted > > [ 14.777177] EXT4-fs (dm-1): recovery complete > > [ 14.797124] EXT4-fs (dm-1): mounted filesystem with ordered data > mode. Opts: (null) > > [ 14.806762] dracut: Mounted root filesystem > /dev/mapper/vg_dom0-lv_root > > [ 14.957211] dracut: Switching root > > [ 15.599261] udev: starting version 151 > > [ 15.673674] iTCO_vendor_support: vendor-support=0 > > [ 15.676374] mei: module is from the staging directory, the quality is > unknown, you have been warned. > > [ 15.676488] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07 > > [ 15.676679] iTCO_wdt: Found a Cougar Point TCO device (Version=2, > TCOBASE=0x0460) > > [ 15.676711] xen: registering gsi 16 triggering 0 polarity 1 > > [ 15.676716] Already setup the GSI :16 > > [ 15.676725] mei 0000:00:16.0: setting latency timer to 64 > > [ 15.676754] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) > > [ 15.712582] sd 0:0:0:0: Attached scsi generic sg0 type 0 > > [ 15.712620] sr 1:0:0:0: Attached scsi generic sg1 type 5 > > [ 15.730448] input: PC Speaker as /devices/platform/pcspkr/input/input8 > > [ 15.734494] xen: registering gsi 18 triggering 0 polarity 1 > > [ 15.734500] Already setup the GSI :18 > > [ 15.734506] ACPI Warning: 0x0000000000004040-0x000000000000405f > SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 > (20120320/utaddress-251) > > [ 15.734512] ACPI: If an ACPI driver is available for this device, you > should use it instead of the native driver > > [ 15.737002] microcode: CPU0 sig=0x206a7, pf=0x10, revision=0x23 > > [ 15.741412] watchdog: INTCAMT: cannot register miscdev on minor=130 > (err=-16) > > [ 15.741418] watchdog: error registering /dev/watchdog (err=-16) > > [ 15.741422] mei 0000:00:16.0: unable to register watchdog device. > > [ 15.790637] thermal LNXTHERM:00: registered as thermal_zone0 > > [ 15.790641] ACPI: Thermal Zone [THM] (25 C) > > [ 15.814551] ACPI: Deprecated procfs I/F for battery is loaded, please > retry with CONFIG_ACPI_PROCFS_POWER cleared > > [ 15.814559] ACPI: Battery Slot [BAT0] (battery present) > > [ 15.815037] ACPI: Deprecated procfs I/F for AC is loaded, please > retry with CONFIG_ACPI_PROCFS_POWER cleared > > [ 15.815521] ACPI: AC Adapter [AC] (on-line) > > [ 15.867835] usbcore: registered new interface driver usbback > > [ 15.975826] ACPI: Deprecated procfs I/F for battery is loaded, please > retry with CONFIG_ACPI_PROCFS_POWER cleared > > [ 15.975836] ACPI: Battery Slot [BAT1] (battery absent) > > [ 16.102871] ACPI: Deprecated procfs I/F for battery is loaded, please > retry with CONFIG_ACPI_PROCFS_POWER cleared > > [ 16.102882] ACPI: Battery Slot [BAT2] (battery absent) > > [ 16.106793] sdhci: Secure Digital Host Controller Interface driver > > [ 16.106797] sdhci: Copyright(c) Pierre Ossman > > [ 16.107131] parport_pc 00:08: [io 0x0378-0x037b] > > [ 16.107296] parport_pc 00:08: [irq 5] > > [ 16.107709] sdhci-pci 0000:0a:00.0: SDHCI controller found > [1217:8221] (rev 5) > > [ 16.159148] xen: registering gsi 17 triggering 0 polarity 1 > > [ 16.159156] Already setup the GSI :17 > > [ 16.159241] sdhci-pci 0000:0a:00.0: Invalid iomem size. You may > experience problems. > > [ 16.159319] 0000:0a:00.0 supply vmmc not found, using dummy regulator > > [ 16.159384] Registered led device: mmc0:: > > [ 16.160442] mmc0: SDHCI controller on PCI [0000:0a:00.0] using DMA > > [ 16.160928] sdhci-pci 0000:0a:00.0: could not set regulator OCR (-22) > > [ 16.171737] Linux video capture interface: v2.00 > > [ 16.192158] cdc_wdm 2-1.6:1.5: cdc-wdm0: USB WDM device > > [ 16.192211] cdc_wdm 2-1.6:1.8: cdc-wdm1: USB WDM device > > [ 16.192234] usbcore: registered new interface driver cdc_wdm > > [ 16.195744] cdc_acm 2-1.6:1.1: ttyACM0: USB ACM device > > [ 16.198739] sdhci-pci 0000:0a:00.0: could not set regulator OCR (-22) > > [ 16.220532] cdc_acm 2-1.6:1.3: ttyACM1: USB ACM device > > [ 16.223728] cdc_acm 2-1.6:1.9: ttyACM2: USB ACM device > > [ 16.235089] sdhci-pci 0000:0a:00.0: could not set regulator OCR (-22) > > [ 16.235234] usbcore: registered new interface driver cdc_acm > > [ 16.235236] cdc_acm: USB Abstract Control Model driver for USB modems > and ISDN adapters > > [ 16.240235] uvcvideo: Found UVC 1.00 device > Laptop_Integrated_Webcam_FHD (05ca:181c) > > [ 16.269474] input: Laptop_Integrated_Webcam_FHD as > /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input9 > > [ 16.269579] usbcore: registered new interface driver uvcvideo > > [ 16.269581] USB Video Class driver (1.1.1) > > [ 16.277415] sdhci-pci 0000:0a:00.0: could not set regulator OCR (-22) > > [ 16.296646] usb 2-1.6: MAC-Address: 02:80:37:ec:02:00 > > [ 16.296810] cdc_ncm 2-1.6:1.6: usb0: register ''cdc_ncm'' at > usb-0000:00:1d.0-1.6, CDC NCM, 02:80:37:ec:02:00 > > [ 16.296847] usbcore: registered new interface driver cdc_ncm > > [ 16.310604] parport_pc 00:08: activated > > [ 16.310611] parport_pc 00:08: reported by Plug and Play ACPI > > [ 16.310781] parport_pc 00:08: disabled > > [ 16.311583] tpm_tis 00:0a: 1.2 TPM (device-id 0x2001, rev-id 32) > > [ 16.399296] Bluetooth: Core ver 2.16 > > [ 16.399312] NET: Registered protocol family 31 > > [ 16.399314] Bluetooth: HCI device and connection manager initialized > > [ 16.399317] Bluetooth: HCI socket layer initialized > > [ 16.399318] Bluetooth: L2CAP socket layer initialized > > [ 16.399325] Bluetooth: SCO socket layer initialized > > [ 16.450583] xen: registering gsi 22 triggering 0 polarity 1 > > [ 16.450600] xen: --> pirq=22 -> irq=22 (gsi=22) > > [ 16.567577] usbcore: registered new interface driver btusb > > [ 16.739259] dcdbas dcdbas: Dell Systems Management Base Driver > (version 5.6.0-3.2) > > [ 16.819125] input: Dell WMI hotkeys as /devices/virtual/input/input10 > > [ 16.925000] microcode: CPU1 sig=0x206a7, pf=0x10, revision=0x23 > > [ 16.929246] ppdev: user-space parallel port driver > > [ 16.954783] microcode: CPU2 sig=0x206a7, pf=0x10, revision=0x23 > > [ 16.975176] microcode: CPU3 sig=0x206a7, pf=0x10, revision=0x23 > > [ 17.004696] microcode: Microcode Update Driver: v2.00 < > tigran@aivazian.fsnet.co.uk>, Peter Oruba > > [ 17.067123] ALSA hda_codec.c:5101 autoconfig: line_outs=1 > (0xe/0x0/0x0/0x0/0x0) type:line > > [ 17.067127] ALSA hda_codec.c:5105 speaker_outs=1 > (0xd/0x0/0x0/0x0/0x0) > > [ 17.067129] ALSA hda_codec.c:5109 hp_outs=1 (0xb/0x0/0x0/0x0/0x0) > > [ 17.067131] ALSA hda_codec.c:5110 mono: mono_out=0x0 > > [ 17.067133] ALSA hda_codec.c:5114 inputs: > > [ 17.067135] ALSA hda_codec.c:5118 Mic=0xa > > [ 17.067137] ALSA hda_codec.c:5118 Dock Mic=0xf > > [ 17.067139] ALSA hda_codec.c:5120 > > [ 17.067637] ALSA patch_sigmatel.c:3117 stac92xx: dac_nids=1 > (0x13/0x0/0x0/0x0/0x0) > > [ 17.081104] input: HDA Intel PCH HDMI/DP,pcm=8 as > /devices/pci0000:00/0000:00:1b.0/sound/card0/input11 > > [ 17.081194] input: HDA Intel PCH HDMI/DP,pcm=7 as > /devices/pci0000:00/0000:00:1b.0/sound/card0/input12 > > [ 17.081250] input: HDA Intel PCH HDMI/DP,pcm=3 as > /devices/pci0000:00/0000:00:1b.0/sound/card0/input13 > > [ 17.081342] input: HDA Intel PCH Dock Mic as > /devices/pci0000:00/0000:00:1b.0/sound/card0/input14 > > [ 17.081432] input: HDA Intel PCH Mic as > /devices/pci0000:00/0000:00:1b.0/sound/card0/input15 > > [ 17.081522] input: HDA Intel PCH Headphone as > /devices/pci0000:00/0000:00:1b.0/sound/card0/input16 > > [ 17.081610] input: HDA Intel PCH Dock Line Out as > /devices/pci0000:00/0000:00:1b.0/sound/card0/input17 > > [ 17.265462] Event-channel device installed. > > [ 17.661764] EXT4-fs (dm-1): re-mounted. Opts: (null) > > [ 17.802446] EXT4-fs (sda1): mounted filesystem with ordered data > mode. Opts: (null) > > [ 19.361631] Adding 17137660k swap on /dev/mapper/vg_dom0-lv_swap. > Priority:-1 extents:1 across:17137660k SS > > [ 22.602549] ehci_hcd 0000:00:1a.0: remove, state 1 > > [ 22.602568] usb usb1: USB disconnect, device number 1 > > [ 22.602573] usb 1-1: USB disconnect, device number 2 > > [ 22.602578] usb 1-1.4: USB disconnect, device number 3 > > [ 22.605235] usb 1-1.5: USB disconnect, device number 4 > > [ 22.636910] ehci_hcd 0000:00:1a.0: USB bus 1 deregistered > > [ 22.637183] pciback 0000:00:1a.0: seizing device > > [ 22.637235] xen: registering gsi 16 triggering 0 polarity 1 > > [ 22.637241] Already setup the GSI :16 > > [ 22.662363] ehci_hcd 0000:00:1d.0: remove, state 1 > > [ 22.662371] usb usb2: USB disconnect, device number 1 > > [ 22.662373] usb 2-1: USB disconnect, device number 2 > > [ 22.662376] usb 2-1.6: USB disconnect, device number 3 > > [ 22.668531] cdc_ncm 2-1.6:1.6: usb0: unregister ''cdc_ncm'' > usb-0000:00:1d.0-1.6, CDC NCM > > [ 22.694795] usb 2-1.8: USB disconnect, device number 4 > > [ 22.699298] ehci_hcd 0000:00:1d.0: USB bus 2 deregistered > > [ 22.699577] pciback 0000:00:1d.0: seizing device > > [ 22.699632] xen: registering gsi 17 triggering 0 polarity 1 > > [ 22.699637] Already setup the GSI :17 > > [ 23.684708] xen-pciback: vpci: 0000:00:19.0: assign to virtual slot 0 > > [ 23.685240] xen-pciback: vpci: 0000:00:1a.0: assign to virtual slot 1 > > [ 23.685722] xen-pciback: vpci: 0000:00:1d.0: assign to virtual slot 2 > > [ 23.686764] xen-pciback: vpci: 0000:02:00.0: assign to virtual slot 3 > > [ 23.909636] pciback 0000:00:19.0: Driver tried to write to a > read-only configuration space field at offset 0xd2, size 2. This may be > harmless, but if you have problems with your device: > > [ 23.909638] 1) see permissive attribute in sysfs > > [ 23.909638] 2) report problems to the xen-devel mailing list along > with details of your device obtained from lspci. > > [ 23.917523] pciback 0000:02:00.0: Driver tried to write to a > read-only configuration space field at offset 0xd2, size 2. This may be > harmless, but if you have problems with your device: > > [ 23.917526] 1) see permissive attribute in sysfs > > [ 23.917526] 2) report problems to the xen-devel mailing list along > with details of your device obtained from lspci. > > [ 24.123663] xen-blkback:ring-ref 9, event-channel 14, protocol 1 > (x86_64-abi) > > [ 24.140460] xen-blkback:ring-ref 10, event-channel 15, protocol 1 > (x86_64-abi) > > [ 24.151420] xen-blkback:ring-ref 11, event-channel 16, protocol 1 > (x86_64-abi) > > [ 24.158428] xen-blkback:ring-ref 12, event-channel 17, protocol 1 > (x86_64-abi) > > [ 28.697615] pciback 0000:00:1a.0: enabling device (0000 -> 0002) > > [ 28.697628] xen: registering gsi 16 triggering 0 polarity 1 > > [ 28.697634] Already setup the GSI :16 > > [ 28.697805] pciback 0000:00:1a.0: setting latency timer to 64 > > [ 28.713578] pciback 0000:00:19.0: enabling device (0000 -> 0003) > > [ 28.713591] xen: registering gsi 20 triggering 0 polarity 1 > > [ 28.713598] Already setup the GSI :20 > > [ 28.713858] pciback 0000:00:19.0: setting latency timer to 64 > > [ 29.021371] pciback 0000:00:1d.0: enabling device (0000 -> 0002) > > [ 29.021389] xen: registering gsi 17 triggering 0 polarity 1 > > [ 29.021400] Already setup the GSI :17 > > [ 29.021805] pciback 0000:00:1d.0: setting latency timer to 64 > > [ 29.150053] pciback 0000:02:00.0: enabling device (0000 -> 0002) > > [ 29.150122] xen: registering gsi 17 triggering 0 polarity 1 > > [ 29.150150] Already setup the GSI :17 > > [ 33.635416] xen-blkback:ring-ref 9, event-channel 14, protocol 1 > (x86_64-abi) > > [ 33.643330] xen-blkback:ring-ref 10, event-channel 15, protocol 1 > (x86_64-abi) > > [ 33.651561] xen-blkback:ring-ref 11, event-channel 16, protocol 1 > (x86_64-abi) > > [ 33.672105] xen-blkback:ring-ref 12, event-channel 17, protocol 1 > (x86_64-abi) > > [ 104.230911] xen-blkback:ring-ref 9, event-channel 24, protocol 1 > (x86_64-abi) > > [ 104.252421] xen-blkback:ring-ref 10, event-channel 25, protocol 1 > (x86_64-abi) > > [ 104.253177] xen-blkback:ring-ref 11, event-channel 26, protocol 1 > (x86_64-abi) > > [ 104.254220] xen-blkback:ring-ref 12, event-channel 27, protocol 1 > (x86_64-abi) > > [ 105.086732] xen-blkback:ring-ref 9, event-channel 14, protocol 1 > (x86_64-abi) > > [ 105.105505] xen-blkback:ring-ref 10, event-channel 15, protocol 1 > (x86_64-abi) > > [ 105.115951] xen-blkback:ring-ref 11, event-channel 16, protocol 1 > (x86_64-abi) > > [ 105.127384] xen-blkback:ring-ref 12, event-channel 17, protocol 1 > (x86_64-abi) > > [ 105.929760] xen-blkback:ring-ref 9, event-channel 14, protocol 1 > (x86_64-abi) > > [ 105.934841] xen-blkback:ring-ref 10, event-channel 15, protocol 1 > (x86_64-abi) > > [ 105.973920] xen-blkback:ring-ref 11, event-channel 16, protocol 1 > (x86_64-abi) > > [ 105.975320] xen-blkback:ring-ref 12, event-channel 17, protocol 1 > (x86_64-abi) > > [ 107.191781] xen-blkback:ring-ref 9, event-channel 14, protocol 1 > (x86_64-abi) > > [ 107.203711] xen-blkback:ring-ref 10, event-channel 15, protocol 1 > (x86_64-abi) > > [ 107.208481] xen-blkback:ring-ref 11, event-channel 16, protocol 1 > (x86_64-abi) > > [ 107.212081] xen-blkback:ring-ref 12, event-channel 17, protocol 1 > (x86_64-abi) > > [ 733.434608] PM: Syncing filesystems ... done. > > [ 733.436228] PM: Preparing system for mem sleep > > [ 733.514803] Freezing user space processes ... (elapsed 0.01 seconds) > done. > > [ 733.530594] Freezing remaining freezable tasks ... (elapsed 0.01 > seconds) done. > > [ 733.546589] PM: Entering mem sleep > > [ 733.546741] Suspending console(s) (use no_console_suspend to debug) > > [ 733.547431] sd 0:0:0:0: [sda] Synchronizing SCSI cache > > [ 733.558336] sd 0:0:0:0: [sda] Stopping disk > > [ 734.194656] PM: suspend of devices complete after 647.504 msecs > > [ 734.195026] PM: late suspend of devices complete after 0.359 msecs > > [ 734.210655] PM: noirq suspend of devices complete after 15.614 msecs > > [ 734.211326] ACPI: Preparing to enter system sleep state S3 > > [ 734.235008] PM: Saving platform NVS memory > > [ 734.328066] Disabling non-boot CPUs ... > > [ 735.945491] ACPI: Low-level resume complete > > [ 735.945579] PM: Restoring platform NVS memory > > [ 736.000094] Enabling non-boot CPUs ... > > [ 736.000256] installing Xen timer for CPU 1 > > [ 736.004594] CPU1 is up > > [ 736.004819] installing Xen timer for CPU 2 > > [ 736.067516] CPU2 is up > > [ 736.067770] installing Xen timer for CPU 3 > > [ 736.101535] CPU3 is up > > [ 736.102470] ACPI: Waking up from system sleep state S3 > > [ 736.555932] PM: noirq resume of devices complete after 7.970 msecs > > [ 736.556506] PM: early resume of devices complete after 0.387 msecs > > [ 736.660336] i915 0000:00:02.0: setting latency timer to 64 > > [ 736.660404] pciback 0000:00:19.0: setting latency timer to 64 > > [ 736.660453] xen: registering gsi 16 triggering 0 polarity 1 > > [ 736.660460] Already setup the GSI :16 > > [ 736.660490] pciback 0000:00:1a.0: setting latency timer to 64 > > [ 736.660605] xen: registering gsi 17 triggering 0 polarity 1 > > [ 736.660610] Already setup the GSI :17 > > [ 736.660641] pciback 0000:00:1d.0: setting latency timer to 64 > > [ 736.660696] xen: registering gsi 22 triggering 0 polarity 1 > > [ 736.660701] Already setup the GSI :22 > > [ 736.661221] ahci 0000:00:1f.2: setting latency timer to 64 > > [ 736.689606] xen: registering gsi 18 triggering 0 polarity 1 > > [ 736.689608] Already setup the GSI :18 > > [ 736.689704] xen: registering gsi 17 triggering 0 polarity 1 > > [ 736.689706] Already setup the GSI :17 > > [ 736.711623] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off > > [ 736.802676] watchdog: INTCAMT: cannot register miscdev on minor=130 > (err=-16) > > [ 736.802678] watchdog: error registering /dev/watchdog (err=-16) > > [ 736.802680] mei 0000:00:16.0: unable to register watchdog device. > > [ 737.060106] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > > [ 737.060330] ata4: SATA link down (SStatus 0 SControl 300) > > [ 737.060372] ata5: SATA link down (SStatus 0 SControl 300) > > [ 737.074123] ata2.00: configured for UDMA/133 > > [ 737.117629] ata6: SATA link down (SStatus 0 SControl 300) > > [ 738.619036] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) > > [ 738.743565] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by > device (Stat=0x51 Err=0x04) > > [ 738.901088] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by > device (Stat=0x51 Err=0x04) > > [ 738.903441] ata1.00: configured for UDMA/100 > > [ 738.903843] sd 0:0:0:0: [sda] Starting disk > > [ 738.905367] PM: resume of devices complete after 2348.851 msecs > > [ 738.905922] PM: Finishing wakeup. > > [ 738.905926] Restarting tasks ... done. > > [ 738.911334] video LNXVIDEO:00: Restoring backlight state > > [ 739.836250] dell_wmi: Received unknown WMI event (0x0) > > [ 740.184759] sdhci-pci 0000:0a:00.0: could not set regulator OCR (-22) > > [ 740.239730] sdhci-pci 0000:0a:00.0: could not set regulator OCR (-22) > > [ 740.327711] sdhci-pci 0000:0a:00.0: could not set regulator OCR (-22) > > [ 740.373931] sdhci-pci 0000:0a:00.0: could not set regulator OCR (-22) > > [ 742.542022] hrtimer: interrupt took 102980031 ns > > [ 757.609031] [sched_delayed] sched: RT throttling activated > > [ 760.164427] hda-intel: IRQ timing workaround is activated for card > #0. Suggest a bigger bdl_pos_adj. > > > (XEN) Xen version 4.1.3 (user@marmarek.net) (gcc version 4.4.5 20101112 > (Red Hat 4.4.5-2) (GCC) ) Mon Nov 26 15:25:32 EST 2012 > > (XEN) Latest ChangeSet: unavailable > > (XEN) Bootloader: GNU GRUB 0.97 > > (XEN) Command line: console=none cpufreq=verbose=1 > > (XEN) Video information: > > (XEN) VGA is text mode 80x25, font 8x16 > > (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds > > (XEN) Disc information: > > (XEN) Found 1 MBR signatures > > (XEN) Found 1 EDD information structures > > (XEN) Xen-e820 RAM map: > > (XEN) 0000000000000000 - 000000000009a800 (usable) > > (XEN) 000000000009a800 - 00000000000a0000 (reserved) > > (XEN) 00000000000e0000 - 0000000000100000 (reserved) > > (XEN) 0000000000100000 - 0000000007eea000 (usable) > > (XEN) 0000000007eea000 - 0000000007f67000 (ACPI NVS) > > (XEN) 0000000007f67000 - 0000000007f70000 (usable) > > (XEN) 0000000007f70000 - 0000000007f76000 (ACPI NVS) > > (XEN) 0000000007f76000 - 0000000007f78000 (usable) > > (XEN) 0000000007f78000 - 0000000008000000 (ACPI NVS) > > (XEN) 0000000008000000 - 000000000dffd000 (usable) > > (XEN) 000000000dffd000 - 000000000e000000 (ACPI data) > > (XEN) 000000000e000000 - 0000000020000000 (usable) > > (XEN) 0000000020000000 - 0000000020200000 (reserved) > > (XEN) 0000000020200000 - 0000000040000000 (usable) > > (XEN) 0000000040000000 - 0000000040200000 (reserved) > > (XEN) 0000000040200000 - 00000000c83b4000 (usable) > > (XEN) 00000000c83b4000 - 00000000c840a000 (reserved) > > (XEN) 00000000c840a000 - 00000000c840e000 (usable) > > (XEN) 00000000c840e000 - 00000000c840f000 (reserved) > > (XEN) 00000000c840f000 - 00000000c8411000 (usable) > > (XEN) 00000000c8411000 - 00000000c8414000 (reserved) > > (XEN) 00000000c8414000 - 00000000c841e000 (usable) > > (XEN) 00000000c841e000 - 00000000c8428000 (reserved) > > (XEN) 00000000c8428000 - 00000000c8432000 (usable) > > (XEN) 00000000c8432000 - 00000000c8436000 (reserved) > > (XEN) 00000000c8436000 - 00000000cac00000 (usable) > > (XEN) 00000000cb800000 - 00000000cfa00000 (reserved) > > (XEN) 00000000fed1c000 - 00000000fed20000 (reserved) > > (XEN) 00000000ffc00000 - 00000000ffc20000 (reserved) > > (XEN) 0000000100000000 - 000000042e000000 (usable) > > (XEN) ACPI: RSDP 000FE300, 0024 (r2 DELL ) > > (XEN) ACPI: XSDT 0DFFEE18, 007C (r1 DELL CBX3 6222004 MSFT > 10013) > > (XEN) ACPI: FACP 07F90D98, 00F4 (r4 DELL CBX3 6222004 MSFT > 10013) > > (XEN) ACPI: DSDT 07F5E018, 8834 (r2 INT430 SYSFexxx 1001 INTL > 20090903) > > (XEN) ACPI: FACS 07FEDD40, 0040 > > (XEN) ACPI: APIC 0DFFDF18, 00CC (r2 DELL CBX3 6222004 MSFT > 10013) > > (XEN) ACPI: TCPA 07FEED18, 0032 (r2 0 > 0) > > (XEN) ACPI: SSDT 07F91A98, 02F9 (r1 DELLTP TPM 3000 INTL > 20090903) > > (XEN) ACPI: MCFG 07FEEC98, 003C (r1 DELL SNDYBRDG 6222004 MSFT > 97) > > (XEN) ACPI: HPET 07FEEC18, 0038 (r1 A M I PCHHPET 6222004 AMI. > 3) > > (XEN) ACPI: BOOT 07FEEB98, 0028 (r1 DELL CBX3 6222004 AMI > 10013) > > (XEN) ACPI: SSDT 07F75018, 0804 (r1 PmRef Cpu0Ist 3000 INTL > 20090903) > > (XEN) ACPI: SSDT 07F74018, 0996 (r1 PmRef CpuPm 3000 INTL > 20090903) > > (XEN) ACPI: DMAR 07F90C18, 00E8 (r1 INTEL SNB 1 INTL > 1) > > (XEN) ACPI: SLIC 07F7EC18, 0176 (r3 DELL CBX3 6222004 MSFT > 10013) > > (XEN) System RAM: 16262MB (16652432kB) > > (XEN) Domain heap initialised > > (XEN) ACPI: 32/64X FACS address mismatch in FADT - > 07fede40/0000000007fedd40, using 32 > > (XEN) Processor #0 6:10 APIC version 21 > > (XEN) Processor #2 6:10 APIC version 21 > > (XEN) Processor #1 6:10 APIC version 21 > > (XEN) Processor #3 6:10 APIC version 21 > > (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 > > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > > (XEN) Table is not found! > > (XEN) Switched to APIC driver x2apic_cluster. > > (XEN) Using scheduler: SMP Credit Scheduler (credit) > > (XEN) Detected 2494.416 MHz processor. > > (XEN) Initing memory sharing. > > (XEN) Intel VT-d supported page sizes: 4kB. > > (XEN) Intel VT-d supported page sizes: 4kB. > > (XEN) Intel VT-d Snoop Control not enabled. > > (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. > > (XEN) Intel VT-d Queued Invalidation enabled. > > (XEN) Intel VT-d Interrupt Remapping enabled. > > (XEN) Intel VT-d Shared EPT tables not enabled. > > (XEN) I/O virtualisation enabled > > (XEN) - Dom0 mode: Relaxed > > (XEN) Enabled directed EOI with ioapic_ack_old on! > > (XEN) ENABLING IO-APIC IRQs > > (XEN) -> Using old ACK method > > (XEN) Platform timer appears to have unexpectedly wrapped 1 times. > > (XEN) Platform timer is 14.318MHz HPET > > (XEN) Allocated console ring of 16 KiB. > > (XEN) VMX: Supported advanced features: > > (XEN) - APIC MMIO access virtualisation > > (XEN) - APIC TPR shadow > > (XEN) - Extended Page Tables (EPT) > > (XEN) - Virtual-Processor Identifiers (VPID) > > (XEN) - Virtual NMI > > (XEN) - MSR direct-access bitmap > > (XEN) - Unrestricted Guest > > (XEN) HVM: ASIDs enabled. > > (XEN) HVM: VMX enabled > > (XEN) HVM: Hardware Assisted Paging (HAP) detected > > (XEN) HVM: HAP page sizes: 4kB, 2MB > > (XEN) Brought up 4 CPUs > > (XEN) *** LOADING DOMAIN 0 *** > > (XEN) Xen kernel: 64-bit, lsb, compat32 > > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1e13000 > > (XEN) PHYSICAL MEMORY ARRANGEMENT: > > (XEN) Dom0 alloc.: 0000000418000000->000000041c000000 (4046567 pages > to be allocated) > > (XEN) Init. ramdisk: 000000042b335000->000000042dfffc00 > > (XEN) VIRTUAL MEMORY ARRANGEMENT: > > (XEN) Loaded kernel: ffffffff81000000->ffffffff81e13000 > > (XEN) Init. ramdisk: ffffffff81e13000->ffffffff84addc00 > > (XEN) Phys-Mach map: ffffffff84ade000->ffffffff869f3d90 > > (XEN) Start info: ffffffff869f4000->ffffffff869f44b4 > > (XEN) Page tables: ffffffff869f5000->ffffffff86a2e000 > > (XEN) Boot stack: ffffffff86a2e000->ffffffff86a2f000 > > (XEN) TOTAL: ffffffff80000000->ffffffff86c00000 > > (XEN) ENTRY ADDRESS: ffffffff8188e200 > > (XEN) Dom0 has maximum 4 VCPUs > > (XEN) Scrubbing Free RAM: .done. > > (XEN) Xen trace buffers: disabled > > (XEN) Std. Loglevel: Errors and warnings > > (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) > > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch > input to Xen) > > (XEN) Freed 216kB init memory. > > (XEN) no cpu_id for acpi_id 5 > > (XEN) no cpu_id for acpi_id 6 > > (XEN) no cpu_id for acpi_id 7 > > (XEN) no cpu_id for acpi_id 8 > > (XEN) physdev.c:171: dom0: wrong map_pirq type 3 > > (XEN) traps.c:2488:d1 Domain attempted WRMSR 0000000000000079 from > 0x0000000000000000 to 0xffffc9000057b030. > > (XEN) traps.c:2488:d1 Domain attempted WRMSR 0000000000000079 from > 0x0000000000000000 to 0xffffc90000718030. > > (XEN) traps.c:2488:d2 Domain attempted WRMSR 0000000000000079 from > 0x0000000000000000 to 0xffffc900004f2030. > > (XEN) traps.c:2488:d2 Domain attempted WRMSR 0000000000000079 from > 0x0000000000000000 to 0xffffc900004fa030. > > (XEN) traps.c:2488:d3 Domain attempted WRMSR 0000000000000079 from > 0x0000000000000000 to 0xffffc90000251030. > > (XEN) traps.c:2488:d3 Domain attempted WRMSR 0000000000000079 from > 0x0000000000000000 to 0xffffc90000263030. > > (XEN) traps.c:2488:d3 Domain attempted WRMSR 0000000000000079 from > 0x0000000000000000 to 0xffffc9000026b030. > > (XEN) traps.c:2488:d3 Domain attempted WRMSR 0000000000000079 from > 0x0000000000000000 to 0xffffc90000273030. > > (XEN) traps.c:2488:d4 Domain attempted WRMSR 0000000000000079 from > 0x0000000000000000 to 0xffffc900004f2030. > > (XEN) traps.c:2488:d4 Domain attempted WRMSR 0000000000000079 from > 0x0000000000000000 to 0xffffc90000015030. > > (XEN) traps.c:2488:d5 Domain attempted WRMSR 0000000000000079 from > 0x0000000000000000 to 0xffffc900004f2030. > > (XEN) traps.c:2488:d5 Domain attempted WRMSR 0000000000000079 from > 0x0000000000000000 to 0xffffc90000015030. > > (XEN) traps.c:2488:d6 Domain attempted WRMSR 0000000000000079 from > 0x0000000000000000 to 0xffffc900004f2030. > > (XEN) traps.c:2488:d6 Domain attempted WRMSR 0000000000000079 from > 0x0000000000000000 to 0xffffc900004fa030. > > (XEN) Disabling non-boot CPUs ... > > (XEN) Broke affinity for irq 1 > > (XEN) Broke affinity for irq 8 > > (XEN) Broke affinity for irq 9 > > (XEN) Broke affinity for irq 12 > > (XEN) Broke affinity for irq 17 > > (XEN) Broke affinity for irq 31 > > (XEN) Broke affinity for irq 16 > > (XEN) Broke affinity for irq 20 > > (XEN) Entering ACPI S3 state. > > (XEN) mce_intel.c:1162: MCA Capability: BCAST 1 SER 0 CMCI 1 firstbank 0 > extended MCE MSR 0 > > (XEN) CPU0 CMCI LVT vector (0xf7) already installed > > (XEN) CPU0: Thermal LVT vector (0xfa) already installed > > (XEN) Finishing wakeup from ACPI S3 state. > > (XEN) Enabling non-boot CPUs ... > > (XEN) traps.c:2488:d7 Domain attempted WRMSR 0000000000000079 from > 0x0000000000000000 to 0xffffc90000524030. > > (XEN) traps.c:2488:d7 Domain attempted WRMSR 0000000000000079 from > 0x0000000000000000 to 0xffffc9000052c030. > > (XEN) traps.c:2488:d7 Domain attempted WRMSR 0000000000000079 from > 0x0000000000000000 to 0xffffc90000015030. > > (XEN) traps.c:2488:d7 Domain attempted WRMSR 0000000000000079 from > 0x0000000000000000 to 0xffffc9000001d030. > > (XEN) Dumping timer queues: > > (XEN) CPU00: > > (XEN) ex= 126us timer=ffff8300c83b0060 > cb=ffff82c48011e420(ffff8300c83b0000) vcpu_singleshot_timer_fn+0x0/0x10 > > (XEN) ex= 1778us timer=ffff8304222f9de8 > cb=ffff82c480118250(0000000000000000) csched_tick+0x0/0x2e0 > > (XEN) ex= 126us timer=ffff8300c81fc060 > cb=ffff82c48011e420(ffff8300c81fc000) vcpu_singleshot_timer_fn+0x0/0x10 > > (XEN) ex= 17227us timer=ffff82c4802bb980 > cb=ffff82c480138ff0(ffff82c4802bb940) do_dbs_timer+0x0/0x250 > > (XEN) ex= 20744us timer=ffff830030094060 > cb=ffff82c48011e420(ffff830030094000) vcpu_singleshot_timer_fn+0x0/0x10 > > (XEN) ex= 27945us timer=ffff8304222fdde0 > cb=ffff82c480116f20(ffff8304222fddc0) csched_acct+0x0/0x460 > > (XEN) ex= 29949us timer=ffff82c4802bb760 > cb=ffff82c48011ded0(0000000000000000) s_timer_fn+0x0/0x20 > > (XEN) ex= 87774us timer=ffff83008db6a060 > cb=ffff82c48011e420(ffff83008db6a000) vcpu_singleshot_timer_fn+0x0/0x10 > > (XEN) ex= 79252us timer=ffff82c4802b3880 > cb=ffff82c480177160(0000000000000000) time_calibration+0x0/0x60 > > (XEN) ex= 703146us timer=ffff8300a6b9c060 > cb=ffff82c48011e420(ffff8300a6b9c000) vcpu_singleshot_timer_fn+0x0/0x10 > > (XEN) ex= 35612us timer=ffff8300330dc060 > cb=ffff82c48011e420(ffff8300330dc000) vcpu_singleshot_timer_fn+0x0/0x10 > > (XEN) ex= 97688us timer=ffff8300a6b98060 > cb=ffff82c48011e420(ffff8300a6b98000) vcpu_singleshot_timer_fn+0x0/0x10 > > (XEN) ex= 30003us timer=ffff8300b129a060 > cb=ffff82c48011e420(ffff8300b129a000) vcpu_singleshot_timer_fn+0x0/0x10 > > (XEN) ex= 92679us timer=ffff8300c94a6060 > cb=ffff82c48011e420(ffff8300c94a6000) vcpu_singleshot_timer_fn+0x0/0x10 > > (XEN) ex= 4135118us timer=ffff8300bdca6060 > cb=ffff82c48011e420(ffff8300bdca6000) vcpu_singleshot_timer_fn+0x0/0x10 > > (XEN) ex= 96411us timer=ffff8300b128e060 > cb=ffff82c48011e420(ffff8300b128e000) vcpu_singleshot_timer_fn+0x0/0x10 > > (XEN) ex= 1337866us timer=ffff8300a6b94060 > cb=ffff82c48011e420(ffff8300a6b94000) vcpu_singleshot_timer_fn+0x0/0x10 > > (XEN) ex= 91194us timer=ffff830034b98060 > cb=ffff82c48011e420(ffff830034b98000) vcpu_singleshot_timer_fn+0x0/0x10 > > (XEN) ex= 97955us timer=ffff83007d948060 > cb=ffff82c48011e420(ffff83007d948000) vcpu_singleshot_timer_fn+0x0/0x10 > > (XEN) ex= 4135163us timer=ffff8300c5336060 > cb=ffff82c48011e420(ffff8300c5336000) vcpu_singleshot_timer_fn+0x0/0x10 > > (XEN) ex=123464409us timer=ffff82c4802b3980 > cb=ffff82c480176ef0(0000000000000000) plt_overflow+0x0/0x190 > > (XEN) ex= 95968us timer=ffff8300a6b96060 > cb=ffff82c48011e420(ffff8300a6b96000) vcpu_singleshot_timer_fn+0x0/0x10 > > (XEN) ex=12401701us timer=ffff82c4802b65a0 > cb=ffff82c48019eb10(0000000000000000) mce_work_fn+0x0/0xd0 > > (XEN) ex= 97804us timer=ffff8300301a8060 > cb=ffff82c48011e420(ffff8300301a8000) vcpu_singleshot_timer_fn+0x0/0x10 > > (XEN) ex= 97841us timer=ffff8300bd810060 > cb=ffff82c48011e420(ffff8300bd810000) vcpu_singleshot_timer_fn+0x0/0x10 > > (XEN) ex= 98039us timer=ffff83007d94c060 > cb=ffff82c48011e420(ffff83007d94c000) vcpu_singleshot_timer_fn+0x0/0x10 > > (XEN) ex= 94727us timer=ffff83008db6e060 > cb=ffff82c48011e420(ffff83008db6e000) vcpu_singleshot_timer_fn+0x0/0x10 > > (XEN) ex= 319927us timer=ffff8300c840c060 > cb=ffff82c48011e420(ffff8300c840c000) vcpu_singleshot_timer_fn+0x0/0x10 > > (XEN) CPU01: > > (XEN) CPU02: > > (XEN) CPU03: > > (XEN) ''c'' pressed -> printing ACPI Cx structures > > (XEN) ==cpu0=> > (XEN) active state: C3 > > (XEN) max_cstate: C7 > > (XEN) states: > > (XEN) C1: type[C1] latency[000] usage[00254665] method[ HALT] > duration[62720099833] > > (XEN) C2: type[C2] latency[080] usage[00069505] method[SYSIO] > duration[36499255195] > > (XEN) *C3: type[C3] latency[109] usage[01828952] method[SYSIO] > duration[5562126933174] > > (XEN) C0: usage[02153122] duration[2042526389598] > > (XEN) PC3[0] PC6[0] PC7[0] > > (XEN) CC3[0] CC6[0] > > (XEN) ==cpu1=> > (XEN) active state: C1 > > (XEN) max_cstate: C7 > > (XEN) states: > > (XEN) *C1: type[C1] latency[000] usage[00808027] method[ HALT] > duration[6978799306750] > > (XEN) C0: usage[00808027] duration[725073398104] > > (XEN) PC3[0] PC6[0] PC7[0] > > (XEN) CC3[0] CC6[0] > > (XEN) ==cpu2=> > (XEN) active state: C1 > > (XEN) max_cstate: C7 > > (XEN) states: > > (XEN) *C1: type[C1] latency[000] usage[00825022] method[ HALT] > duration[6981527416097] > > (XEN) C0: usage[00825022] duration[722345319882] > > (XEN) PC3[0] PC6[0] PC7[0] > > (XEN) CC3[0] CC6[0] > > (XEN) ==cpu3=> > (XEN) active state: C1 > > (XEN) max_cstate: C7 > > (XEN) states: > > (XEN) *C1: type[C1] latency[000] usage[00810292] method[ HALT] > duration[6980835907857] > > (XEN) C0: usage[00810292] duration[723036844779] > > (XEN) PC3[0] PC6[0] PC7[0] > > (XEN) CC3[0] CC6[0] > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xen.org > > http://lists.xen.org/xen-devel > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
>>> On 30.11.12 at 17:18, Marek Marczykowski <marmarek@invisiblethingslab.com>wrote:> On 30.11.2012 17:12, Jan Beulich wrote: >>>>> Marek Marczykowski <marmarek@invisiblethingslab.com> 11/30/12 5:07 PM >>> >>> That was the rare case when resume worked at all... in most cased I''ve got >>> reboot, before anything appear on the screen (even backlight is off) - xen >>> panic? dom0 kernel panic? >> >> Without serial console we won''t get very far from here. >> >>> I don''t have serial console, but have USB-to-serial port - is it possible to >>> use it as xen console (in xen 4.1.3)? >> >> Not that I''m aware of. But 4.1.x isn''t very interesting from a development >> perspective anyway. If you had the same problems still with 4.3-unstable, >> then that''s be of much more interest to analyze, and you could use the >> EHCI debug port (if one of your controllers has one) based serial console. > > Is it possible to use libxl from xen 4.1 with newer hypervisor? My libxl is > somehow patched and porting it to newer version will require some effort.I don''t think so, but I also don''t think you need a libxl at all for the purposes here (dealing with S3 is a Dom0-only thing). Jan
On 03.12.2012 08:39, Jan Beulich wrote:>>>> On 30.11.12 at 17:18, Marek Marczykowski <marmarek@invisiblethingslab.com> > wrote: >> On 30.11.2012 17:12, Jan Beulich wrote: >>>>>> Marek Marczykowski <marmarek@invisiblethingslab.com> 11/30/12 5:07 PM >>> >>>> That was the rare case when resume worked at all... in most cased I''ve got >>>> reboot, before anything appear on the screen (even backlight is off) - xen >>>> panic? dom0 kernel panic? >>> >>> Without serial console we won''t get very far from here. >>> >>>> I don''t have serial console, but have USB-to-serial port - is it possible to >>>> use it as xen console (in xen 4.1.3)? >>> >>> Not that I''m aware of. But 4.1.x isn''t very interesting from a development >>> perspective anyway. If you had the same problems still with 4.3-unstable, >>> then that''s be of much more interest to analyze, and you could use the >>> EHCI debug port (if one of your controllers has one) based serial console. >> >> Is it possible to use libxl from xen 4.1 with newer hypervisor? My libxl is >> somehow patched and porting it to newer version will require some effort. > > I don''t think so, but I also don''t think you need a libxl at all for the > purposes here (dealing with S3 is a Dom0-only thing).I''ve tested xen 4.2 hypervisor (without serial console) and also rebooted during resume. But it works with xen 4.1.2, so the problem was introduced between 4.1.2 and 4.1.3. Will try to get console messages from xen-unstable - perhaps this will give some hints. -- Best Regards / Pozdrawiam, Marek Marczykowski Invisible Things Lab _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On 04.12.2012 14:27, Marek Marczykowski wrote:> On 03.12.2012 08:39, Jan Beulich wrote: >>>>> On 30.11.12 at 17:18, Marek Marczykowski <marmarek@invisiblethingslab.com> >> wrote: >>> On 30.11.2012 17:12, Jan Beulich wrote: >>>>>>> Marek Marczykowski <marmarek@invisiblethingslab.com> 11/30/12 5:07 PM >>> >>>>> That was the rare case when resume worked at all... in most cased I''ve got >>>>> reboot, before anything appear on the screen (even backlight is off) - xen >>>>> panic? dom0 kernel panic? >>>> >>>> Without serial console we won''t get very far from here. >>>> >>>>> I don''t have serial console, but have USB-to-serial port - is it possible to >>>>> use it as xen console (in xen 4.1.3)? >>>> >>>> Not that I''m aware of. But 4.1.x isn''t very interesting from a development >>>> perspective anyway. If you had the same problems still with 4.3-unstable, >>>> then that''s be of much more interest to analyze, and you could use the >>>> EHCI debug port (if one of your controllers has one) based serial console. >>> >>> Is it possible to use libxl from xen 4.1 with newer hypervisor? My libxl is >>> somehow patched and porting it to newer version will require some effort. >> >> I don''t think so, but I also don''t think you need a libxl at all for the >> purposes here (dealing with S3 is a Dom0-only thing). > > I''ve tested xen 4.2 hypervisor (without serial console) and also rebooted > during resume. But it works with xen 4.1.2, so the problem was introduced > between 4.1.2 and 4.1.3. Will try to get console messages from xen-unstable - > perhaps this will give some hints.It still doesn''t work on xen 4.1.4, system reboots at resume. Same on 4.3-unstable (today). Can you give me some hints about using EHCI debug port? I''ve found some info on coreboot page[1]. Is there any way to use it without NET20DC device? According to lspci my controller have debug port capability. [1] http://www.coreboot.org/EHCI_Debug_Port -- Best Regards / Pozdrawiam, Marek Marczykowski Invisible Things Lab _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
>>> On 20.12.12 at 16:59, Marek Marczykowski <marmarek@invisiblethingslab.com> wrote: > It still doesn''t work on xen 4.1.4, system reboots at resume. Same on > 4.3-unstable (today). > Can you give me some hints about using EHCI debug port? I''ve found some info > on coreboot page[1]. Is there any way to use it without NET20DC device?No, you need such a special device (not sure if what they name there is the only one, as mine isn''t named that way iirc).> According to lspci my controller have debug port capability.You also need to check that you system''s designers didn''t put an internal hub in between (which would prevent the debug port from actually working).> [1] http://www.coreboot.org/EHCI_Debug_PortOr Linux''es Documentation/x86/earlyprintk.txt. Jan
See if the attached patch helps. This was a patch I forgot was still in my queue, that Jan had some objections about (though I don''t recall specifically what they were) I had found that the scheduler was removing all cpus during suspend, and this seemed to help with that, IIRC. That said - I''m starting to be forced to look back into S3 issues, as while I thought they were all resolved, they are not. I have an Ivybridge laptop that I didn''t have back in May that exhibits some issues very similar to those that I was trying to solve with Jan in the thread I pasted above. This particular machine goes to sleep, and when it resumes, the disk light flashes briefly, and then the sleep led goes back to pulsing. Not much to go on, at this point. /btg On Thu, Dec 20, 2012 at 10:59 AM, Marek Marczykowski < marmarek@invisiblethingslab.com> wrote:> On 04.12.2012 14:27, Marek Marczykowski wrote: > > On 03.12.2012 08:39, Jan Beulich wrote: > >>>>> On 30.11.12 at 17:18, Marek Marczykowski < > marmarek@invisiblethingslab.com> > >> wrote: > >>> On 30.11.2012 17:12, Jan Beulich wrote: > >>>>>>> Marek Marczykowski <marmarek@invisiblethingslab.com> 11/30/12 > 5:07 PM >>> > >>>>> That was the rare case when resume worked at all... in most cased > I''ve got > >>>>> reboot, before anything appear on the screen (even backlight is off) > - xen > >>>>> panic? dom0 kernel panic? > >>>> > >>>> Without serial console we won''t get very far from here. > >>>> > >>>>> I don''t have serial console, but have USB-to-serial port - is it > possible to > >>>>> use it as xen console (in xen 4.1.3)? > >>>> > >>>> Not that I''m aware of. But 4.1.x isn''t very interesting from a > development > >>>> perspective anyway. If you had the same problems still with > 4.3-unstable, > >>>> then that''s be of much more interest to analyze, and you could use the > >>>> EHCI debug port (if one of your controllers has one) based serial > console. > >>> > >>> Is it possible to use libxl from xen 4.1 with newer hypervisor? My > libxl is > >>> somehow patched and porting it to newer version will require some > effort. > >> > >> I don''t think so, but I also don''t think you need a libxl at all for the > >> purposes here (dealing with S3 is a Dom0-only thing). > > > > I''ve tested xen 4.2 hypervisor (without serial console) and also rebooted > > during resume. But it works with xen 4.1.2, so the problem was introduced > > between 4.1.2 and 4.1.3. Will try to get console messages from > xen-unstable - > > perhaps this will give some hints. > > It still doesn''t work on xen 4.1.4, system reboots at resume. Same on > 4.3-unstable (today). > Can you give me some hints about using EHCI debug port? I''ve found some > info > on coreboot page[1]. Is there any way to use it without NET20DC device? > According to lspci my controller have debug port capability. > > [1] http://www.coreboot.org/EHCI_Debug_Port > > -- > Best Regards / Pozdrawiam, > Marek Marczykowski > Invisible Things Lab > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On 20.12.2012 20:41, Ben Guthro wrote:> See if the attached patch helps. > This was a patch I forgot was still in my queue, that Jan had some > objections about (though I don''t recall specifically what they were) > I had found that the scheduler was removing all cpus during suspend, and > this seemed to help with that, IIRC. > > That said - I''m starting to be forced to look back into S3 issues, as while > I thought they were all resolved, they are not. > I have an Ivybridge laptop that I didn''t have back in May that exhibits > some issues very similar to those that I was trying to solve with Jan in > the thread I pasted above. > > This particular machine goes to sleep, and when it resumes, the disk light > flashes briefly, and then the sleep led goes back to pulsing.With this patch applied (on 4.1.4 and 4.3-unstable), I''ve got original symptom - only CPU0 active after ACPI S3. Didn''t get reboot after few tries. "xl debug-key r" output attached. Anyway it looks like bug was introduced somehow between 4.1.2 and 4.1.3 - on 4.1.2 none of above problems happened. -- Best Regards / Pozdrawiam, Marek Marczykowski Invisible Things Lab _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On 21.12.2012 00:17, Marek Marczykowski wrote:> On 20.12.2012 20:41, Ben Guthro wrote: >> See if the attached patch helps. >> This was a patch I forgot was still in my queue, that Jan had some >> objections about (though I don''t recall specifically what they were) >> I had found that the scheduler was removing all cpus during suspend, and >> this seemed to help with that, IIRC. >> >> That said - I''m starting to be forced to look back into S3 issues, as while >> I thought they were all resolved, they are not. >> I have an Ivybridge laptop that I didn''t have back in May that exhibits >> some issues very similar to those that I was trying to solve with Jan in >> the thread I pasted above. >> >> This particular machine goes to sleep, and when it resumes, the disk light >> flashes briefly, and then the sleep led goes back to pulsing. > > With this patch applied (on 4.1.4 and 4.3-unstable), I''ve got original symptom > - only CPU0 active after ACPI S3. Didn''t get reboot after few tries. > "xl debug-key r" output attached. > Anyway it looks like bug was introduced somehow between 4.1.2 and 4.1.3 - on > 4.1.2 none of above problems happened.I''ve done bisect on xen 4.1 and found problematic commit: http://xenbits.xen.org/hg/xen-4.1-testing.hg/rev/1f95b55ef427 Unfortunately in xen-unstable parent of corresponding commit still have the same problem, so there must be something more wrong. -- Best Regards / Pozdrawiam, Marek Marczykowski Invisible Things Lab _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
>>> On 21.12.12 at 05:52, Marek Marczykowski <marmarek@invisiblethingslab.com> wrote: > On 21.12.2012 00:17, Marek Marczykowski wrote: >> With this patch applied (on 4.1.4 and 4.3-unstable), I''ve got original > symptom >> - only CPU0 active after ACPI S3. Didn''t get reboot after few tries. >> "xl debug-key r" output attached. >> Anyway it looks like bug was introduced somehow between 4.1.2 and 4.1.3 - on >> 4.1.2 none of above problems happened. > > I''ve done bisect on xen 4.1 and found problematic commit: > http://xenbits.xen.org/hg/xen-4.1-testing.hg/rev/1f95b55ef427In that case, using "sched_ratelimit_us=0" should make the problem go away again - did you try that?> Unfortunately in xen-unstable parent of corresponding commit still have the > same problem, so there must be something more wrong.Which is why we''d need to be really certain that the c/s you spotted really is relevant here (to me it doesn''t look like having an effect on resume at all). Jan
On 21.12.2012 09:55, Jan Beulich wrote:>>>> On 21.12.12 at 05:52, Marek Marczykowski <marmarek@invisiblethingslab.com> wrote: >> On 21.12.2012 00:17, Marek Marczykowski wrote: >>> With this patch applied (on 4.1.4 and 4.3-unstable), I''ve got original >> symptom >>> - only CPU0 active after ACPI S3. Didn''t get reboot after few tries. >>> "xl debug-key r" output attached. >>> Anyway it looks like bug was introduced somehow between 4.1.2 and 4.1.3 - on >>> 4.1.2 none of above problems happened. >> >> I''ve done bisect on xen 4.1 and found problematic commit: >> http://xenbits.xen.org/hg/xen-4.1-testing.hg/rev/1f95b55ef427 > > In that case, using "sched_ratelimit_us=0" should make the > problem go away again - did you try that?This option does not help when trying 4.1.4, but does when trying xen compiled from above c/s.>> Unfortunately in xen-unstable parent of corresponding commit still have the >> same problem, so there must be something more wrong. > > Which is why we''d need to be really certain that the c/s you > spotted really is relevant here (to me it doesn''t look like having > an effect on resume at all).So perhaps there is other problematic commit, which was backported to 4.1 later (than it is in xen-unstable). -- Best Regards / Pozdrawiam, Marek Marczykowski Invisible Things Lab _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On 21.12.2012 14:33, Marek Marczykowski wrote:> On 21.12.2012 09:55, Jan Beulich wrote: >>>>> On 21.12.12 at 05:52, Marek Marczykowski <marmarek@invisiblethingslab.com> wrote: >>> On 21.12.2012 00:17, Marek Marczykowski wrote: >>>> With this patch applied (on 4.1.4 and 4.3-unstable), I''ve got original >>> symptom >>>> - only CPU0 active after ACPI S3. Didn''t get reboot after few tries. >>>> "xl debug-key r" output attached. >>>> Anyway it looks like bug was introduced somehow between 4.1.2 and 4.1.3 - on >>>> 4.1.2 none of above problems happened. >>> >>> I''ve done bisect on xen 4.1 and found problematic commit: >>> http://xenbits.xen.org/hg/xen-4.1-testing.hg/rev/1f95b55ef427 >> >> In that case, using "sched_ratelimit_us=0" should make the >> problem go away again - did you try that? > > This option does not help when trying 4.1.4, but does when trying xen compiled > from above c/s. > >>> Unfortunately in xen-unstable parent of corresponding commit still have the >>> same problem, so there must be something more wrong. >> >> Which is why we''d need to be really certain that the c/s you >> spotted really is relevant here (to me it doesn''t look like having >> an effect on resume at all). > > So perhaps there is other problematic commit, which was backported to 4.1 > later (than it is in xen-unstable).Or above commit only trigger some other bug... -- Best Regards / Pozdrawiam, Marek Marczykowski Invisible Things Lab _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
>>> On 21.12.12 at 14:33, Marek Marczykowski <marmarek@invisiblethingslab.com>wrote:> On 21.12.2012 09:55, Jan Beulich wrote: >>>>> On 21.12.12 at 05:52, Marek Marczykowski <marmarek@invisiblethingslab.com> > wrote: >>> On 21.12.2012 00:17, Marek Marczykowski wrote: >>>> With this patch applied (on 4.1.4 and 4.3-unstable), I''ve got original >>> symptom >>>> - only CPU0 active after ACPI S3. Didn''t get reboot after few tries. >>>> "xl debug-key r" output attached. >>>> Anyway it looks like bug was introduced somehow between 4.1.2 and 4.1.3 - on >>>> 4.1.2 none of above problems happened. >>> >>> I''ve done bisect on xen 4.1 and found problematic commit: >>> http://xenbits.xen.org/hg/xen-4.1-testing.hg/rev/1f95b55ef427 >> >> In that case, using "sched_ratelimit_us=0" should make the >> problem go away again - did you try that? > > This option does not help when trying 4.1.4, but does when trying xen > compiled > from above c/s.Which basically calls for you doing another bisection round, this time with that option in place. But for the moment, as said earlier, it escapes me how that change would have an impact on resume (the more that we have no logs). Will need to look at this in closer detail after New Year (and George, maybe you could take a look too). You don''t happen to use "dom0_vcpus_pin", do you? Jan
On 21.12.2012 14:42, Jan Beulich wrote:>>>> On 21.12.12 at 14:33, Marek Marczykowski <marmarek@invisiblethingslab.com> > wrote: >> On 21.12.2012 09:55, Jan Beulich wrote: >>>>>> On 21.12.12 at 05:52, Marek Marczykowski <marmarek@invisiblethingslab.com> >> wrote: >>>> On 21.12.2012 00:17, Marek Marczykowski wrote: >>>>> With this patch applied (on 4.1.4 and 4.3-unstable), I''ve got original >>>> symptom >>>>> - only CPU0 active after ACPI S3. Didn''t get reboot after few tries. >>>>> "xl debug-key r" output attached. >>>>> Anyway it looks like bug was introduced somehow between 4.1.2 and 4.1.3 - on >>>>> 4.1.2 none of above problems happened. >>>> >>>> I''ve done bisect on xen 4.1 and found problematic commit: >>>> http://xenbits.xen.org/hg/xen-4.1-testing.hg/rev/1f95b55ef427 >>> >>> In that case, using "sched_ratelimit_us=0" should make the >>> problem go away again - did you try that? >> >> This option does not help when trying 4.1.4, but does when trying xen >> compiled >> from above c/s. > > Which basically calls for you doing another bisection round, this > time with that option in place.Will try, but not sure if will have time for it before Christmas.> > But for the moment, as said earlier, it escapes me how that change > would have an impact on resume (the more that we have no logs). > Will need to look at this in closer detail after New Year (and George, > maybe you could take a look too). > > You don''t happen to use "dom0_vcpus_pin", do you?I don''t. Should I try? -- Best Regards / Pozdrawiam, Marek Marczykowski Invisible Things Lab _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Fri, Dec 21, 2012 at 8:59 AM, Marek Marczykowski < marmarek@invisiblethingslab.com> wrote:> > You don''t happen to use "dom0_vcpus_pin", do you? > > I don''t. Should I try?Probably not. I ran into issues with it the last go-around with Jan whilst trying to debug S3 issues. It turned out it got in the way of some scheduling stuff. S3 will break the CPU affinity set up by that pinning, and it can lead to some unexpected behavior, and/or crashing upon resume. I''d recommend against it. /btg _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
>>> On 21.12.12 at 14:59, Marek Marczykowski <marmarek@invisiblethingslab.com> wrote: > On 21.12.2012 14:42, Jan Beulich wrote: >> You don''t happen to use "dom0_vcpus_pin", do you? > > I don''t. Should I try?No - iirc that was the cause for Ben''s problems. Jan
On 21.12.2012 14:59, Marek Marczykowski wrote:> On 21.12.2012 14:42, Jan Beulich wrote: >>>>> On 21.12.12 at 14:33, Marek Marczykowski <marmarek@invisiblethingslab.com> >> wrote: >>> On 21.12.2012 09:55, Jan Beulich wrote: >>>>>>> On 21.12.12 at 05:52, Marek Marczykowski <marmarek@invisiblethingslab.com> >>> wrote: >>>>> On 21.12.2012 00:17, Marek Marczykowski wrote: >>>>>> With this patch applied (on 4.1.4 and 4.3-unstable), I''ve got original >>>>> symptom >>>>>> - only CPU0 active after ACPI S3. Didn''t get reboot after few tries. >>>>>> "xl debug-key r" output attached. >>>>>> Anyway it looks like bug was introduced somehow between 4.1.2 and 4.1.3 - on >>>>>> 4.1.2 none of above problems happened. >>>>> >>>>> I''ve done bisect on xen 4.1 and found problematic commit: >>>>> http://xenbits.xen.org/hg/xen-4.1-testing.hg/rev/1f95b55ef427 >>>> >>>> In that case, using "sched_ratelimit_us=0" should make the >>>> problem go away again - did you try that? >>> >>> This option does not help when trying 4.1.4, but does when trying xen >>> compiled >>> from above c/s. >> >> Which basically calls for you doing another bisection round, this >> time with that option in place. > > Will try, but not sure if will have time for it before Christmas.Next bisection (this time with sched_ratelimit_us=0) gives this commit: http://xenbits.xen.org/hg/xen-4.1-testing.hg/rev/d67e4d12723f I''ve tried also xen-4.1 tip with Ben''s patch and sched_ratelimit_us=0, but it didn''t worked well - got all vCPUs on pCPU 0, instead on reboot (more common effect). Not sure if this is really different effect or just non-deterministic behavior of the same bug. -- Best Regards / Pozdrawiam, Marek Marczykowski Invisible Things Lab _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Fri, Dec 21, 2012 at 10:30 AM, Marek Marczykowski < marmarek@invisiblethingslab.com> wrote:> > > Will try, but not sure if will have time for it before Christmas. > > Next bisection (this time with sched_ratelimit_us=0) gives this commit: > http://xenbits.xen.org/hg/xen-4.1-testing.hg/rev/d67e4d12723f > >This is interesting, as it is this same equivalent changeset in unstable that I came up with, as problematic. The xen-unstable equivalent patch is here: http://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=269f543ea750ed567d18f2e819e5d5ce58eda5c5 My patch simply reverts part of this patch, specifically, the hunk in xen/common/schedule.c _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
>>> On 21.12.12 at 16:30, Marek Marczykowski <marmarek@invisiblethingslab.com> wrote: > Next bisection (this time with sched_ratelimit_us=0) gives this commit: > http://xenbits.xen.org/hg/xen-4.1-testing.hg/rev/d67e4d12723fBen, wasn''t this where your bisection ended up too? Jan
On Dec 21, 2012, at 11:03 AM, Jan Beulich <JBeulich@suse.com> wrote:>>>> On 21.12.12 at 16:30, Marek Marczykowski <marmarek@invisiblethingslab.com> wrote: >> Next bisection (this time with sched_ratelimit_us=0) gives this commit: >> http://xenbits.xen.org/hg/xen-4.1-testing.hg/rev/d67e4d12723f > > Ben, wasn''t this where your bisection ended up too?Yes, for the dom0_pin_vcpus issue.> > >
On 21.12.2012 17:18, Ben Guthro wrote:> On Dec 21, 2012, at 11:03 AM, Jan Beulich <JBeulich@suse.com> wrote: > >>>>> On 21.12.12 at 16:30, Marek Marczykowski <marmarek@invisiblethingslab.com> wrote: >>> Next bisection (this time with sched_ratelimit_us=0) gives this commit: >>> http://xenbits.xen.org/hg/xen-4.1-testing.hg/rev/d67e4d12723f >> >> Ben, wasn''t this where your bisection ended up too? > > Yes, for the dom0_pin_vcpus issue.Ok, I can confirm that on xen-4.1-testing tip with above commit reverted completely problem has gone away, even without sched_ratelimit_us=0. With Ben''s patch (partially revert) no reboot observed, but still sometimes only pCPU0 is used after resume. -- Best Regards / Pozdrawiam, Marek Marczykowski Invisible Things Lab _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Interesting. I had started by reverting the commit entirely, but settled on only reverting the part causing the scheduling issues. I''m not sure if I was as thorough in my testing this fix, across a lot of laptop generations. I''ll test reverting the full commit in the new year, and report back. I think that, at a minimum - the commit should get some scrutiny by people who might understand the subtleties, and/or unintended side effects better than I. -Ben On Sat, Dec 22, 2012 at 9:49 PM, Marek Marczykowski < marmarek@invisiblethingslab.com> wrote:> On 21.12.2012 17:18, Ben Guthro wrote: > > On Dec 21, 2012, at 11:03 AM, Jan Beulich <JBeulich@suse.com> wrote: > > > >>>>> On 21.12.12 at 16:30, Marek Marczykowski < > marmarek@invisiblethingslab.com> wrote: > >>> Next bisection (this time with sched_ratelimit_us=0) gives this commit: > >>> http://xenbits.xen.org/hg/xen-4.1-testing.hg/rev/d67e4d12723f > >> > >> Ben, wasn''t this where your bisection ended up too? > > > > Yes, for the dom0_pin_vcpus issue. > > Ok, I can confirm that on xen-4.1-testing tip with above commit reverted > completely problem has gone away, even without sched_ratelimit_us=0. With > Ben''s patch (partially revert) no reboot observed, but still sometimes only > pCPU0 is used after resume. > > -- > Best Regards / Pozdrawiam, > Marek Marczykowski > Invisible Things Lab > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Sadly, the full revert of this changeset in Xen-4.2 did not solve the resume issue I am seeing on the Lenovo T430. My current suspicion is irq delivery, because of the following messages I see on the console on the way down: (XEN) Preparing system for ACPI S3 state. (XEN) Disabling non-boot CPUs ... (XEN) Broke affinity for irq 1 (XEN) Broke affinity for irq 9 (XEN) Broke affinity for irq 12 (XEN) Broke affinity for irq 26 (XEN) Broke affinity for irq 30 (XEN) Broke affinity for irq 1 (XEN) Broke affinity for irq 1 (XEN) Entering ACPI S3 state. I am not currently running with pinning dom0 vcpus Of course, this is merely a suspicion, and I don''t have a lot of hard evidence to back this up. I''ve requested an ITP be budgeted to debug these issues on Intel SDPs, but I think it may be some months before I see the results of that. Jan - any suggestions on how to procede with this? FWIW, Xen 4.0.y suspends on this machine reliably. /btg On Sun, Dec 23, 2012 at 8:45 AM, Ben Guthro <ben.guthro@gmail.com> wrote:> Interesting. > > I had started by reverting the commit entirely, but settled on only > reverting the part causing the scheduling issues. > I''m not sure if I was as thorough in my testing this fix, across a lot of > laptop generations. > > I''ll test reverting the full commit in the new year, and report back. > > I think that, at a minimum - the commit should get some scrutiny by people > who might understand the subtleties, and/or unintended side effects better > than I. > > > -Ben > > > On Sat, Dec 22, 2012 at 9:49 PM, Marek Marczykowski < > marmarek@invisiblethingslab.com> wrote: > >> On 21.12.2012 17:18, Ben Guthro wrote: >> > On Dec 21, 2012, at 11:03 AM, Jan Beulich <JBeulich@suse.com> wrote: >> > >> >>>>> On 21.12.12 at 16:30, Marek Marczykowski < >> marmarek@invisiblethingslab.com> wrote: >> >>> Next bisection (this time with sched_ratelimit_us=0) gives this >> commit: >> >>> http://xenbits.xen.org/hg/xen-4.1-testing.hg/rev/d67e4d12723f >> >> >> >> Ben, wasn''t this where your bisection ended up too? >> > >> > Yes, for the dom0_pin_vcpus issue. >> >> Ok, I can confirm that on xen-4.1-testing tip with above commit reverted >> completely problem has gone away, even without sched_ratelimit_us=0. With >> Ben''s patch (partially revert) no reboot observed, but still sometimes >> only >> pCPU0 is used after resume. >> >> -- >> Best Regards / Pozdrawiam, >> Marek Marczykowski >> Invisible Things Lab >> >> >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
>>> On 21.12.12 at 14:33, Marek Marczykowski <marmarek@invisiblethingslab.com>wrote:> On 21.12.2012 09:55, Jan Beulich wrote: >>>>> On 21.12.12 at 05:52, Marek Marczykowski <marmarek@invisiblethingslab.com> > wrote: >>> On 21.12.2012 00:17, Marek Marczykowski wrote: >>>> With this patch applied (on 4.1.4 and 4.3-unstable), I''ve got original >>> symptom >>>> - only CPU0 active after ACPI S3. Didn''t get reboot after few tries. >>>> "xl debug-key r" output attached. >>>> Anyway it looks like bug was introduced somehow between 4.1.2 and 4.1.3 - on >>>> 4.1.2 none of above problems happened. >>> >>> I''ve done bisect on xen 4.1 and found problematic commit: >>> http://xenbits.xen.org/hg/xen-4.1-testing.hg/rev/1f95b55ef427 >> >> In that case, using "sched_ratelimit_us=0" should make the >> problem go away again - did you try that? > > This option does not help when trying 4.1.4, but does when trying xen > compiled from above c/s.Are you saying that on 4.1.4 this doesn''t take effect? Are there any log messages indicating so? The above being the top most change to sched_credit.c, this difference in behavior pretty odd. On 4.2, this wouldn''t be surprising, given that without -unstable c/s 26266:8d209624ea83 the =0 special case didn''t get handled (broken by 24880:dd9e8f1ebed1). Jan
>>> On 31.12.12 at 13:51, Ben Guthro <ben.guthro@gmail.com> wrote: > My current suspicion is irq delivery, because of the following messages I > see on the console on the way down: > > (XEN) Preparing system for ACPI S3 state. > (XEN) Disabling non-boot CPUs ... > (XEN) Broke affinity for irq 1 > (XEN) Broke affinity for irq 9 > (XEN) Broke affinity for irq 12 > (XEN) Broke affinity for irq 26 > (XEN) Broke affinity for irq 30 > (XEN) Broke affinity for irq 1 > (XEN) Broke affinity for irq 1 > (XEN) Entering ACPI S3 state.No, that''s normal behavior. But you ought to be able to verify by pinning Dom0''s vCPU 0 to pCPU 0, and within Dom0 setting the affinities of all interrupts to CPU 0 - that should make all of these messages go away.> Jan - any suggestions on how to procede with this? FWIW, Xen 4.0.y suspends > on this machine reliably.With two scheduler related changesets having got spotted as problematic by now (23255:1f95b55ef427 and 23269:d67e4d12723f, albeit the latter not really scheduler specific), I''m really very much hoping for George to have an idea, the more that ... Jan
On 03.01.2013 09:52, Jan Beulich wrote:>>>> On 21.12.12 at 14:33, Marek Marczykowski <marmarek@invisiblethingslab.com> > wrote: >> On 21.12.2012 09:55, Jan Beulich wrote: >>>>>> On 21.12.12 at 05:52, Marek Marczykowski <marmarek@invisiblethingslab.com> >> wrote: >>>> On 21.12.2012 00:17, Marek Marczykowski wrote: >>>>> With this patch applied (on 4.1.4 and 4.3-unstable), I''ve got original >>>> symptom >>>>> - only CPU0 active after ACPI S3. Didn''t get reboot after few tries. >>>>> "xl debug-key r" output attached. >>>>> Anyway it looks like bug was introduced somehow between 4.1.2 and 4.1.3 - on >>>>> 4.1.2 none of above problems happened. >>>> >>>> I''ve done bisect on xen 4.1 and found problematic commit: >>>> http://xenbits.xen.org/hg/xen-4.1-testing.hg/rev/1f95b55ef427 >>> >>> In that case, using "sched_ratelimit_us=0" should make the >>> problem go away again - did you try that? >> >> This option does not help when trying 4.1.4, but does when trying xen >> compiled from above c/s. > > Are you saying that on 4.1.4 this doesn''t take effect? Are there > any log messages indicating so? The above being the top most > change to sched_credit.c, this difference in behavior pretty odd.I can no longer reproduce this bug on 4.1.3-rc1-pre (above sched_credit c/s) with or without sched_ratelimit_us=0. So it must be some mistake during previous testing. Also the problem from email subject is rather rare and not observed after ~20 suspend-resume cycles... Just to summary: 4.1.3-rc1-pre (above sched_credit c/s) - works ok 4.1.4 regardless of sched_ratelimit_us=0 reboots at resume 4.1.5-pre reboots at resume regardless of sched_ratelimit_us option 4.1.5-pre with "Introduce system_state variable" reverted works fine - regardless of sched_ratelimit_us option "4.1.5-pre" was c/s 23436:2ae6267371d8, but still the same effects on 23441:2a91623a5807.> On 4.2, this wouldn''t be surprising, given that without -unstable > c/s 26266:8d209624ea83 the =0 special case didn''t get handled > (broken by 24880:dd9e8f1ebed1). > > Jan >-- Best Regards / Pozdrawiam, Marek Marczykowski Invisible Things Lab _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On 12.01.2013 08:05, Marek Marczykowski wrote:> On 03.01.2013 09:52, Jan Beulich wrote: >>>>> On 21.12.12 at 14:33, Marek Marczykowski <marmarek@invisiblethingslab.com> >> wrote: >>> On 21.12.2012 09:55, Jan Beulich wrote: >>>>>>> On 21.12.12 at 05:52, Marek Marczykowski <marmarek@invisiblethingslab.com> >>> wrote: >>>>> On 21.12.2012 00:17, Marek Marczykowski wrote: >>>>>> With this patch applied (on 4.1.4 and 4.3-unstable), I''ve got original >>>>> symptom >>>>>> - only CPU0 active after ACPI S3. Didn''t get reboot after few tries. >>>>>> "xl debug-key r" output attached. >>>>>> Anyway it looks like bug was introduced somehow between 4.1.2 and 4.1.3 - on >>>>>> 4.1.2 none of above problems happened. >>>>> >>>>> I''ve done bisect on xen 4.1 and found problematic commit: >>>>> http://xenbits.xen.org/hg/xen-4.1-testing.hg/rev/1f95b55ef427 >>>> >>>> In that case, using "sched_ratelimit_us=0" should make the >>>> problem go away again - did you try that? >>> >>> This option does not help when trying 4.1.4, but does when trying xen >>> compiled from above c/s. >> >> Are you saying that on 4.1.4 this doesn''t take effect? Are there >> any log messages indicating so? The above being the top most >> change to sched_credit.c, this difference in behavior pretty odd. > > I can no longer reproduce this bug on 4.1.3-rc1-pre (above sched_credit c/s) > with or without sched_ratelimit_us=0. So it must be some mistake during > previous testing. > Also the problem from email subject is rather rare and not observed after ~20 > suspend-resume cycles... > > Just to summary: > 4.1.3-rc1-pre (above sched_credit c/s) - works ok > 4.1.4 regardless of sched_ratelimit_us=0 reboots at resume > 4.1.5-pre reboots at resume regardless of sched_ratelimit_us option > 4.1.5-pre with "Introduce system_state variable" reverted works fine - > regardless of sched_ratelimit_us option > > "4.1.5-pre" was c/s 23436:2ae6267371d8, but still the same effects on > 23441:2a91623a5807.Just after sending this email I''ve suspended laptop (running 4.1.5-pre with above commit reverted, but without sched_ratelimit_us=0 option). After few hours it hanged at resume (don''t know at which state, but somehow early - before reinitialize of console). The same xen version suspended for shorter time period (2-5min) resumed without problem. I''ve retried suspend for 4-5h and got reboot. The same version (still with "system_state" commit reverted), but _with_ sched_ratelimit_us=0 resumes well even after many hours. So sched_ratelimit_us option makes some difference even on most recent 4.1 xen, but it needs patience to spot it... Maybe above "works ok" for 4.1.3-rc1-pre isn''t really true because I''ve tested short suspend periods. -- Best Regards / Pozdrawiam, Marek Marczykowski Invisible Things Lab _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On 03/01/13 08:52, Jan Beulich wrote:>>>> On 31.12.12 at 13:51, Ben Guthro <ben.guthro@gmail.com> wrote: >> My current suspicion is irq delivery, because of the following messages I >> see on the console on the way down: >> >> (XEN) Preparing system for ACPI S3 state. >> (XEN) Disabling non-boot CPUs ... >> (XEN) Broke affinity for irq 1 >> (XEN) Broke affinity for irq 9 >> (XEN) Broke affinity for irq 12 >> (XEN) Broke affinity for irq 26 >> (XEN) Broke affinity for irq 30 >> (XEN) Broke affinity for irq 1 >> (XEN) Broke affinity for irq 1 >> (XEN) Entering ACPI S3 state. > No, that''s normal behavior. But you ought to be able to verify by > pinning Dom0''s vCPU 0 to pCPU 0, and within Dom0 setting the > affinities of all interrupts to CPU 0 - that should make all of these > messages go away. > >> Jan - any suggestions on how to procede with this? FWIW, Xen 4.0.y suspends >> on this machine reliably. > With two scheduler related changesets having got spotted as > problematic by now (23255:1f95b55ef427 and 23269:d67e4d12723f, > albeit the latter not really scheduler specific), I''m really very much > hoping for George to have an idea, the more that ...Marek, Sorry I haven''t been following the thread -- have you tested this with 4.2, with and without the corresponding patch reverted (25079:d5ccb2d1dbd1)? That might tell us whether the patch itself was wrong, or whether there was a mistake in back-porting the patch (possibly because of different invariants outside of the patched code). Jan, the commit message isn''t very informative -- can you point me to a conversation describing the problem you''re fixing wrt suspend/resume, and/or describe what you were trying to do? Given the results, the whole thing about not disabling scheduling during suspend seems a bit suspect... -George
On 16/01/13 11:22, George Dunlap wrote:> On 03/01/13 08:52, Jan Beulich wrote: >>>>> On 31.12.12 at 13:51, Ben Guthro <ben.guthro@gmail.com> wrote: >>> My current suspicion is irq delivery, because of the following >>> messages I >>> see on the console on the way down: >>> >>> (XEN) Preparing system for ACPI S3 state. >>> (XEN) Disabling non-boot CPUs ... >>> (XEN) Broke affinity for irq 1 >>> (XEN) Broke affinity for irq 9 >>> (XEN) Broke affinity for irq 12 >>> (XEN) Broke affinity for irq 26 >>> (XEN) Broke affinity for irq 30 >>> (XEN) Broke affinity for irq 1 >>> (XEN) Broke affinity for irq 1 >>> (XEN) Entering ACPI S3 state. >> No, that''s normal behavior. But you ought to be able to verify by >> pinning Dom0''s vCPU 0 to pCPU 0, and within Dom0 setting the >> affinities of all interrupts to CPU 0 - that should make all of these >> messages go away. >> >>> Jan - any suggestions on how to procede with this? FWIW, Xen 4.0.y >>> suspends >>> on this machine reliably. >> With two scheduler related changesets having got spotted as >> problematic by now (23255:1f95b55ef427 and 23269:d67e4d12723f, >> albeit the latter not really scheduler specific), I''m really very much >> hoping for George to have an idea, the more that ... > > Marek, > > Sorry I haven''t been following the thread -- have you tested this with > 4.2, with and without the corresponding patch reverted > (25079:d5ccb2d1dbd1)? That might tell us whether the patch itself was > wrong, or whether there was a mistake in back-porting the patch > (possibly because of different invariants outside of the patched code). > > Jan, the commit message isn''t very informative -- can you point me to > a conversation describing the problem you''re fixing wrt > suspend/resume, and/or describe what you were trying to do? Given the > results, the whole thing about not disabling scheduling during suspend > seems a bit suspect...In particular, just on a fairly cursory bit of function call skimming, it looks like: * This change means that cpupool.c:cpu_callback() won''t call cpupool_cpu_add() when resuming * cpupool_cpu_add() does a bunch of paperwork (which would be unnecessary given the changes re suspend), but also calls cpupool_assign_cpu_locked() * cpupool_assign_cpu_locked() calls schedule_cpu_switch() * schedule_cpu_switch() calls the scheduler''s tick_resume() So is it possible that on resume ticks are not being re-enabled, or something like that? (And possibly related to Ben''s problem, ticks are not being disabled on suspend?) -George
>>> On 16.01.13 at 12:58, George Dunlap <george.dunlap@eu.citrix.com> wrote: > On 16/01/13 11:22, George Dunlap wrote: >> Jan, the commit message isn''t very informative -- can you point me toWhich commit message?>> a conversation describing the problem you''re fixing wrt >> suspend/resume, and/or describe what you were trying to do? Given the >> results, the whole thing about not disabling scheduling during suspend >> seems a bit suspect... > > In particular, just on a fairly cursory bit of function call skimming, > it looks like: > * This change means that cpupool.c:cpu_callback() won''t call > cpupool_cpu_add() when resuming > * cpupool_cpu_add() does a bunch of paperwork (which would be > unnecessary given the changes re suspend), but also calls > cpupool_assign_cpu_locked() > * cpupool_assign_cpu_locked() calls schedule_cpu_switch() > * schedule_cpu_switch() calls the scheduler''s tick_resume() > > So is it possible that on resume ticks are not being re-enabled, or > something like that?I don''t see a problem here - it''s symmetric (nothing done on suspend, and nothing done on resume). Jan
On 16/01/13 13:08, Jan Beulich wrote:>>>> On 16.01.13 at 12:58, George Dunlap <george.dunlap@eu.citrix.com> wrote: >> On 16/01/13 11:22, George Dunlap wrote: >>> Jan, the commit message isn''t very informative -- can you point me to > Which commit message? > >>> a conversation describing the problem you''re fixing wrt >>> suspend/resume, and/or describe what you were trying to do? Given the >>> results, the whole thing about not disabling scheduling during suspend >>> seems a bit suspect... >> In particular, just on a fairly cursory bit of function call skimming, >> it looks like: >> * This change means that cpupool.c:cpu_callback() won''t call >> cpupool_cpu_add() when resuming >> * cpupool_cpu_add() does a bunch of paperwork (which would be >> unnecessary given the changes re suspend), but also calls >> cpupool_assign_cpu_locked() >> * cpupool_assign_cpu_locked() calls schedule_cpu_switch() >> * schedule_cpu_switch() calls the scheduler''s tick_resume() >> >> So is it possible that on resume ticks are not being re-enabled, or >> something like that? > I don''t see a problem here - it''s symmetric (nothing done on > suspend, and nothing done on resume).Well it would be if it was only data, but it''s not. That''s my point. Before this changeset (xen-unstable 25079:d5ccb2d1dbd1), ticks were suspended and resumed on the CPU (i.e., timer interrupts turned off and on), and after the patch, they''re not. Doesn''t suspend disable / muck with timer interrupts? -George
>>> On 16.01.13 at 14:58, George Dunlap <george.dunlap@eu.citrix.com> wrote: > On 16/01/13 13:08, Jan Beulich wrote: >>>>> On 16.01.13 at 12:58, George Dunlap <george.dunlap@eu.citrix.com> wrote: >>> On 16/01/13 11:22, George Dunlap wrote: >>>> Jan, the commit message isn''t very informative -- can you point me to >> Which commit message? >> >>>> a conversation describing the problem you''re fixing wrt >>>> suspend/resume, and/or describe what you were trying to do? Given the >>>> results, the whole thing about not disabling scheduling during suspend >>>> seems a bit suspect... >>> In particular, just on a fairly cursory bit of function call skimming, >>> it looks like: >>> * This change means that cpupool.c:cpu_callback() won''t call >>> cpupool_cpu_add() when resuming >>> * cpupool_cpu_add() does a bunch of paperwork (which would be >>> unnecessary given the changes re suspend), but also calls >>> cpupool_assign_cpu_locked() >>> * cpupool_assign_cpu_locked() calls schedule_cpu_switch() >>> * schedule_cpu_switch() calls the scheduler''s tick_resume() >>> >>> So is it possible that on resume ticks are not being re-enabled, or >>> something like that? >> I don''t see a problem here - it''s symmetric (nothing done on >> suspend, and nothing done on resume). > > Well it would be if it was only data, but it''s not. That''s my point. > Before this changeset (xen-unstable 25079:d5ccb2d1dbd1), ticks were > suspended and resumed on the CPU (i.e., timer interrupts turned off and > on), and after the patch, they''re not. Doesn''t suspend disable / muck > with timer interrupts?Oh, I see. But assuming we don''t want to re-introduce what Juergen tried to fix back then, shouldn''t we instead call sched_tick_{suspend,resume}() directly? Wouldn''t that even be more consistent than relying on the calls hidden underneath the CPU pool code? Jan