Kernel 2.6.35-1 and 2.6.35-2 crash amuled

On the same machine, with kernel 2.6.34.2 and kernel 2.6.34.2-bfs amuled runs normal. Only the 2.6.35 kernel from testing crashes amule every time - and I tried it very, very often ^.^
----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
Current version is: aMuled 2.2.6 using wxGTK2 v2.8.10
Running on: Linux 2.6.35-ARCH i686
[2] ?? in amuled[0x8057c81]
[3] wxFatalSignalHandler in /usr/lib/libwx_baseu-2.8.so.0[0xb76f3c76]
[4] ?? in [0xb77e6400]
[5] GSocket::Input_Timeout() in /usr/lib/libwx_baseu_net-2.8.so.0[0xb777c133]
[6] GSocket::Read(char*, int) in /usr/lib/libwx_baseu_net-2.8.so.0[0xb777cd64]
[7] wxSocketBase::_Read(void*, unsigned int) in /usr/lib/libwx_baseu_net-2.8.so.0[0xb777878f]
[8] wxSocketBase::Peek(void*, unsigned int) in /usr/lib/libwx_baseu_net-2.8.so.0[0xb77788f7]
[9] wxProtocol::ReadLine(wxSocketBase*, wxString&) in /usr/lib/libwx_baseu_net-2.8.so.0[0xb777312e]
[10] wxHTTP::ParseHeaders() in /usr/lib/libwx_baseu_net-2.8.so.0[0xb777111f]
[11] wxHTTP::BuildRequest(wxString const&, wxHTTP::wxHTTP_Req) in /usr/lib/libwx_baseu_net-2.8.so.0[0xb7771f90]
[12] wxHTTP::GetInputStream(wxString const&) in /usr/lib/libwx_baseu_net-2.8.so.0[0xb77721cc]
[13] ?? in amuled[0x80c2dbc]
[14] ?? in amuled[0x80c329d]
[15] wxThreadInternal::PthreadStart(wxThread*) in /usr/lib/libwx_baseu-2.8.so.0[0xb76eec50]
[16] wxPthreadStart in /usr/lib/libwx_baseu-2.8.so.0[0xb76eecbd]
[17] ?? in /lib/libpthread.so.0[0xb77a2e60]
[18] clone in /lib/libc.so.6[0xb746720e]
Now I'm compiling amule-devel in the hope, that it helps.
Have fun,
Karl

patroclo7
Wireless extensions are included and I did make/make install and everything seemed to go right - no errors! And I have allways used rt2500-cvs-daily -drivers because they have been very stable (in my system).
nightfrost
Code:   
modprobe -l | grep rt2
Thanks for that - there was missing rt2500.ko module and I added it in place and wlan is now working.
But now I have nvidia-problems... maybe I can solve it later 

Similar Messages

  • Xen Kernel randomly fails to load and goes out of range

    Been having an on/off issue lately that requires a hard reset of my system.  Essentially what happens is the system begins to load when my monitor reports an error that the signal is out of range.  I try to pretend login and reboot, but it does not work.  Instead, I am forced to simply reset the system and once reset it appears to boot OK without any issues.  In fact I can go a few reboots before once again it decides to break.  Below is what should be one of the logs from a failed boot, in fact, the system is in this same failed state right now as well.
    arch_1 ~ :( # journalctl -b -1
    -- Logs begin at Sat 2013-12-28 00:39:50 EST, end at Thu 2014-01-02 23:28:03 EST. --
    Jan 02 23:22:36 arch_1 systemd-journal[129]: Runtime journal is using 332.0K (max 91.3M, leaving 137.0M of fre
    Jan 02 23:22:36 arch_1 systemd-journal[129]: Runtime journal is using 336.0K (max 91.3M, leaving 137.0M of fre
    Jan 02 23:22:36 arch_1 kernel: Initializing cgroup subsys cpuset
    Jan 02 23:22:36 arch_1 kernel: Initializing cgroup subsys cpu
    Jan 02 23:22:36 arch_1 kernel: Initializing cgroup subsys cpuacct
    Jan 02 23:22:36 arch_1 kernel: Linux version 3.12.6-1-ARCH (tobias@T-POWA-LX) (gcc version 4.8.2 (GCC) ) #1 SM
    Jan 02 23:22:36 arch_1 kernel: Command line: /vmlinuz-linux root=/dev/mapper/vg_arch-lv_root rw console=tty0
    Jan 02 23:22:36 arch_1 kernel: Freeing 9e-100 pfn range: 98 pages freed
    Jan 02 23:22:36 arch_1 kernel: 1-1 mapping on 9e->100
    Jan 02 23:22:36 arch_1 kernel: 1-1 mapping on bd9ff->100000
    Jan 02 23:22:36 arch_1 kernel: Released 98 pages of unused memory
    Jan 02 23:22:36 arch_1 kernel: Set 271971 page(s) to 1-1 mapping
    Jan 02 23:22:36 arch_1 kernel: Populating 80000-80062 pfn range: 98 pages added
    Jan 02 23:22:36 arch_1 kernel: e820: BIOS-provided physical RAM map:
    Jan 02 23:22:36 arch_1 kernel: Xen: [mem 0x0000000000000000-0x000000000009dfff] usable
    Jan 02 23:22:36 arch_1 kernel: Xen: [mem 0x00000000000a0000-0x00000000000fffff] reserved
    Jan 02 23:22:36 arch_1 kernel: Xen: [mem 0x0000000000100000-0x00000000bd9fefff] usable
    Jan 02 23:22:36 arch_1 kernel: Xen: [mem 0x00000000bd9ffc00-0x00000000bda53bff] ACPI NVS
    Jan 02 23:22:36 arch_1 kernel: Xen: [mem 0x00000000bda53c00-0x00000000bda55bff] ACPI data
    Jan 02 23:22:36 arch_1 kernel: Xen: [mem 0x00000000bda55c00-0x00000000bfffffff] reserved
    Jan 02 23:22:36 arch_1 kernel: Xen: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
    Jan 02 23:22:36 arch_1 kernel: Xen: [mem 0x00000000fec00000-0x00000000fed003ff] reserved
    Jan 02 23:22:36 arch_1 kernel: Xen: [mem 0x00000000fed20000-0x00000000fed9ffff] reserved
    Jan 02 23:22:36 arch_1 kernel: Xen: [mem 0x00000000fee00000-0x00000000feefffff] reserved
    Jan 02 23:22:36 arch_1 kernel: Xen: [mem 0x00000000ffb00000-0x00000000ffffffff] reserved
    Jan 02 23:22:36 arch_1 kernel: Xen: [mem 0x0000000100000000-0x0000000237ffffff] usable
    Jan 02 23:22:36 arch_1 kernel: NX (Execute Disable) protection: active
    Jan 02 23:22:36 arch_1 kernel: SMBIOS 2.5 present.
    Jan 02 23:22:36 arch_1 kernel: DMI: Dell Inc. OptiPlex 960 /0Y958C, BIOS A10 12/20/2010
    Jan 02 23:22:36 arch_1 kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    Jan 02 23:22:36 arch_1 kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    Jan 02 23:22:36 arch_1 kernel: No AGP bridge found
    Jan 02 23:22:36 arch_1 kernel: e820: last_pfn = 0x238000 max_arch_pfn = 0x400000000
    Jan 02 23:22:36 arch_1 kernel: e820: last_pfn = 0xbd9ff max_arch_pfn = 0x400000000
    Jan 02 23:22:36 arch_1 kernel: Scanning 1 areas for low memory corruption
    Jan 02 23:22:36 arch_1 kernel: Base memory trampoline at [ffff880000098000] 98000 size 24576
    Jan 02 23:22:36 arch_1 kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
    Jan 02 23:22:36 arch_1 kernel: [mem 0x00000000-0x000fffff] page 4k
    Jan 02 23:22:36 arch_1 kernel: init_memory_mapping: [mem 0x7fe00000-0x7fffffff]
    Jan 02 23:22:36 arch_1 kernel: [mem 0x7fe00000-0x7fffffff] page 4k
    Jan 02 23:22:36 arch_1 kernel: BRK [0x01b47000, 0x01b47fff] PGTABLE
    Jan 02 23:22:36 arch_1 kernel: BRK [0x01b48000, 0x01b48fff] PGTABLE
    Jan 02 23:22:36 arch_1 kernel: init_memory_mapping: [mem 0x7c000000-0x7fdfffff]
    Jan 02 23:22:36 arch_1 kernel: [mem 0x7c000000-0x7fdfffff] page 4k
    Jan 02 23:22:36 arch_1 kernel: BRK [0x01b49000, 0x01b49fff] PGTABLE
    Jan 02 23:22:36 arch_1 kernel: BRK [0x01b4a000, 0x01b4afff] PGTABLE
    Jan 02 23:22:36 arch_1 kernel: BRK [0x01b4b000, 0x01b4bfff] PGTABLE
    Jan 02 23:22:36 arch_1 kernel: BRK [0x01b4c000, 0x01b4cfff] PGTABLE
    Jan 02 23:22:36 arch_1 kernel: init_memory_mapping: [mem 0x00100000-0x7bffffff]
    Jan 02 23:22:36 arch_1 kernel: [mem 0x00100000-0x7bffffff] page 4k
    Jan 02 23:22:36 arch_1 kernel: init_memory_mapping: [mem 0x80000000-0xbd9fefff]
    Jan 02 23:22:36 arch_1 kernel: [mem 0x80000000-0xbd9fefff] page 4k
    Jan 02 23:22:36 arch_1 kernel: init_memory_mapping: [mem 0x100000000-0x237ffffff]
    Jan 02 23:22:36 arch_1 kernel: [mem 0x100000000-0x237ffffff] page 4k
    Jan 02 23:22:36 arch_1 kernel: RAMDISK: [mem 0x01f54000-0x029fefff]
    Jan 02 23:22:36 arch_1 kernel: ACPI: RSDP 00000000000fec00 00024 (v02 DELL )
    Jan 02 23:22:36 arch_1 kernel: ACPI: XSDT 00000000000fc7d7 00084 (v01 DELL B10K 00000015 ASL 00000061)
    Jan 02 23:22:36 arch_1 kernel: ACPI: FACP 00000000000fc907 000F4 (v03 DELL B10K 00000015 ASL 00000061)
    Jan 02 23:22:36 arch_1 kernel: ACPI: DSDT 00000000ffe9e423 05744 (v01 DELL dt_ex 00001000 INTL 20050624)
    Jan 02 23:22:36 arch_1 kernel: ACPI: FACS 00000000bd9ffc00 00040
    Jan 02 23:22:36 arch_1 kernel: ACPI: SSDT 00000000ffea3d30 00087 (v01 DELL st_ex 00001000 INTL 20050624)
    Jan 02 23:22:36 arch_1 kernel: ACPI: APIC 00000000000fc9fb 00092 (v01 DELL B10K 00000015 ASL 00000061)
    Jan 02 23:22:36 arch_1 kernel: ACPI: BOOT 00000000000fca8d 00028 (v01 DELL B10K 00000015 ASL 00000061)
    Jan 02 23:22:36 arch_1 kernel: ACPI: ASF! 00000000000fcab5 00096 (v32 DELL B10K 00000015 ASL 00000061)
    Jan 02 23:22:36 arch_1 kernel: ACPI: MCFG 00000000000fcb4b 0003C (v01 DELL B10K 00000015 ASL 00000061)
    Jan 02 23:22:36 arch_1 kernel: ACPI: HPET 00000000000fcb87 00038 (v01 DELL B10K 00000015 ASL 00000061)
    Jan 02 23:22:36 arch_1 kernel: ACPI: TCPA 00000000000fcde3 00032 (v01 DELL B10K 00000015 ASL 00000061)
    Jan 02 23:22:36 arch_1 kernel: ACPI: DMAR 00000000000fce15 00108 (v01 DELL B10K 00000015 ASL 00000061)
    Jan 02 23:22:36 arch_1 kernel: ACPI: SSDT 00000000bd9ffc40 001F9 (v01 DpgPmm Cpu0Ist 00000011 INTL 20050624)
    Jan 02 23:22:36 arch_1 kernel: ACPI: SSDT 00000000bda00049 001F9 (v01 DpgPmm Cpu1Ist 00000011 INTL 20050624)
    Jan 02 23:22:36 arch_1 kernel: ACPI: SSDT 00000000bda00452 00190 (v01 DpgPmm CpuPm 00000010 INTL 20050624)
    Jan 02 23:22:36 arch_1 kernel: ACPI: Local APIC address 0xfee00000
    Jan 02 23:22:36 arch_1 kernel: NUMA turned off
    Jan 02 23:22:36 arch_1 kernel: Faking a node at [mem 0x0000000000000000-0x0000000237ffffff]
    Jan 02 23:22:36 arch_1 kernel: Initmem setup node 0 [mem 0x00000000-0x237ffffff]
    Jan 02 23:22:36 arch_1 kernel: NODE_DATA [mem 0x7f0c7000-0x7f0cbfff]
    Jan 02 23:22:36 arch_1 kernel: Zone ranges:
    Jan 02 23:22:36 arch_1 kernel: DMA [mem 0x00001000-0x00ffffff]
    Jan 02 23:22:36 arch_1 kernel: DMA32 [mem 0x01000000-0xffffffff]
    Jan 02 23:22:36 arch_1 kernel: Normal [mem 0x100000000-0x237ffffff]
    Jan 02 23:22:36 arch_1 kernel: Movable zone start for each node
    Jan 02 23:22:36 arch_1 kernel: Early memory node ranges
    Jan 02 23:22:36 arch_1 kernel: node 0: [mem 0x00001000-0x0009dfff]
    Jan 02 23:22:36 arch_1 kernel: node 0: [mem 0x00100000-0xbd9fefff]
    Jan 02 23:22:36 arch_1 kernel: node 0: [mem 0x100000000-0x237ffffff]
    Jan 02 23:22:36 arch_1 kernel: On node 0 totalpages: 2054556
    Jan 02 23:22:36 arch_1 kernel: DMA zone: 64 pages used for memmap
    Jan 02 23:22:36 arch_1 kernel: DMA zone: 21 pages reserved
    Jan 02 23:22:36 arch_1 kernel: DMA zone: 3997 pages, LIFO batch:0
    Jan 02 23:22:36 arch_1 kernel: DMA32 zone: 12072 pages used for memmap
    Jan 02 23:22:36 arch_1 kernel: DMA32 zone: 772607 pages, LIFO batch:31
    Jan 02 23:22:36 arch_1 kernel: Normal zone: 19968 pages used for memmap
    Jan 02 23:22:36 arch_1 kernel: Normal zone: 1277952 pages, LIFO batch:31
    Jan 02 23:22:36 arch_1 kernel: ACPI: PM-Timer IO Port: 0x808
    Jan 02 23:22:36 arch_1 kernel: ACPI: Local APIC address 0xfee00000
    Jan 02 23:22:36 arch_1 kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    Jan 02 23:22:36 arch_1 kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
    Jan 02 23:22:36 arch_1 kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x05] disabled)
    Jan 02 23:22:36 arch_1 kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] disabled)
    Jan 02 23:22:36 arch_1 kernel: ACPI: LAPIC (acpi_id[0x05] lapic_id[0x00] disabled)
    Jan 02 23:22:36 arch_1 kernel: ACPI: LAPIC (acpi_id[0x06] lapic_id[0x01] disabled)
    Jan 02 23:22:36 arch_1 kernel: ACPI: LAPIC (acpi_id[0x07] lapic_id[0x02] disabled)
    Jan 02 23:22:36 arch_1 kernel: ACPI: LAPIC (acpi_id[0x08] lapic_id[0x03] disabled)
    Jan 02 23:22:36 arch_1 kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1])
    Jan 02 23:22:36 arch_1 kernel: ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
    Jan 02 23:22:36 arch_1 kernel: IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
    Jan 02 23:22:36 arch_1 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    Jan 02 23:22:36 arch_1 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    Jan 02 23:22:36 arch_1 kernel: ACPI: IRQ0 used by override.
    Jan 02 23:22:36 arch_1 kernel: ACPI: IRQ2 used by override.
    Jan 02 23:22:36 arch_1 kernel: ACPI: IRQ9 used by override.
    Jan 02 23:22:36 arch_1 kernel: Using ACPI (MADT) for SMP configuration information
    Jan 02 23:22:36 arch_1 kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000
    Jan 02 23:22:36 arch_1 kernel: smpboot: Allowing 8 CPUs, 6 hotplug CPUs
    Jan 02 23:22:36 arch_1 kernel: nr_irqs_gsi: 40
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000fffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xbd9ff000-0xbd9fffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xbda00000-0xbda52fff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xbda53000-0xbda53fff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xbda54000-0xbda54fff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xbda55000-0xbda55fff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xbda56000-0xbfffffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xc0000000-0xf7ffffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfecfffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfed1ffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xfed20000-0xfed9ffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xfeda0000-0xfedfffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xfee00000-0xfeefffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xfef00000-0xffafffff]
    Jan 02 23:22:36 arch_1 kernel: PM: Registered nosave memory: [mem 0xffb00000-0xffffffff]
    Jan 02 23:22:36 arch_1 kernel: e820: [mem 0xc0000000-0xf7ffffff] available for PCI devices
    Jan 02 23:22:36 arch_1 kernel: Booting paravirtualized kernel on Xen
    Jan 02 23:22:36 arch_1 kernel: Xen version: 4.3.1 (preserve-AD)
    Jan 02 23:22:36 arch_1 kernel: setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:8 nr_node_ids:1
    Jan 02 23:22:36 arch_1 kernel: PERCPU: Embedded 29 pages/cpu @ffff88007ee00000 s86464 r8192 d24128 u262144
    Jan 02 23:22:36 arch_1 kernel: pcpu-alloc: s86464 r8192 d24128 u262144 alloc=1*2097152
    Jan 02 23:22:36 arch_1 kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7
    Jan 02 23:22:36 arch_1 kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 2022431
    Jan 02 23:22:36 arch_1 kernel: Policy zone: Normal
    Jan 02 23:22:36 arch_1 kernel: Kernel command line: /vmlinuz-linux root=/dev/mapper/vg_arch-lv_root rw console
    Jan 02 23:22:36 arch_1 kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
    Jan 02 23:22:36 arch_1 kernel: xsave: enabled xstate_bv 0x3, cntxt size 0x240
    Jan 02 23:22:36 arch_1 kernel: software IO TLB [mem 0x72a00000-0x76a00000] (64MB) mapped at [ffff880072a00000-
    Jan 02 23:22:36 arch_1 kernel: Memory: 1857868K/8218224K available (5124K kernel code, 807K rwdata, 1628K roda
    Jan 02 23:22:36 arch_1 kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
    Jan 02 23:22:36 arch_1 kernel: Preemptible hierarchical RCU implementation.
    Jan 02 23:22:36 arch_1 kernel: RCU dyntick-idle grace-period acceleration is enabled.
    Jan 02 23:22:36 arch_1 kernel: Dump stacks of tasks blocking RCU-preempt GP.
    Jan 02 23:22:36 arch_1 kernel: RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=2.
    Jan 02 23:22:36 arch_1 kernel: NR_IRQS:8448 nr_irqs:512 16
    Jan 02 23:22:36 arch_1 kernel: xen: sci override: global_irq=9 trigger=0 polarity=0
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 9 triggering 0 polarity 0
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=9 -> irq=9 (gsi=9)
    Jan 02 23:22:36 arch_1 kernel: xen: acpi sci 9
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=1 -> irq=1 (gsi=1)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=2 -> irq=2 (gsi=2)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=3 -> irq=3 (gsi=3)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=4 -> irq=4 (gsi=4)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=5 -> irq=5 (gsi=5)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=6 -> irq=6 (gsi=6)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=7 -> irq=7 (gsi=7)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=8 -> irq=8 (gsi=8)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=10 -> irq=10 (gsi=10)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=11 -> irq=11 (gsi=11)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=12 -> irq=12 (gsi=12)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=13 -> irq=13 (gsi=13)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=14 -> irq=14 (gsi=14)
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=15 -> irq=15 (gsi=15)
    Jan 02 23:22:36 arch_1 kernel: Console: colour VGA+ 80x25
    Jan 02 23:22:36 arch_1 kernel: console [tty0] enabled
    Jan 02 23:22:36 arch_1 kernel: allocated 33030144 bytes of page_cgroup
    Jan 02 23:22:36 arch_1 kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
    Jan 02 23:22:36 arch_1 kernel: Xen: using vcpuop timer interface
    Jan 02 23:22:36 arch_1 kernel: installing Xen timer for CPU 0
    Jan 02 23:22:36 arch_1 kernel: tsc: Detected 2992.224 MHz processor
    Jan 02 23:22:36 arch_1 kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 5986
    Jan 02 23:22:36 arch_1 kernel: pid_max: default: 32768 minimum: 301
    Jan 02 23:22:36 arch_1 kernel: Security Framework initialized
    Jan 02 23:22:36 arch_1 kernel: AppArmor: AppArmor disabled by boot time parameter
    Jan 02 23:22:36 arch_1 kernel: Yama: becoming mindful.
    Jan 02 23:22:36 arch_1 kernel: Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
    Jan 02 23:22:36 arch_1 kernel: Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
    Jan 02 23:22:36 arch_1 kernel: Mount-cache hash table entries: 256
    Jan 02 23:22:36 arch_1 kernel: Initializing cgroup subsys memory
    Jan 02 23:22:36 arch_1 kernel: Initializing cgroup subsys devices
    Jan 02 23:22:36 arch_1 kernel: Initializing cgroup subsys freezer
    Jan 02 23:22:36 arch_1 kernel: Initializing cgroup subsys net_cls
    Jan 02 23:22:36 arch_1 kernel: Initializing cgroup subsys blkio
    Jan 02 23:22:36 arch_1 kernel: CPU: Physical Processor ID: 0
    Jan 02 23:22:36 arch_1 kernel: CPU: Processor Core ID: 0
    Jan 02 23:22:36 arch_1 kernel: mce: CPU supports 2 MCE banks
    Jan 02 23:22:36 arch_1 kernel: Last level iTLB entries: 4KB 128, 2MB 4, 4MB 4
    Last level dTLB entries: 4KB 256, 2MB 0, 4MB 32
    tlb_flushall_shift: -1
    Jan 02 23:22:36 arch_1 kernel: Freeing SMP alternatives memory: 20K (ffffffff819e9000 - ffffffff819ee000)
    Jan 02 23:22:36 arch_1 kernel: ACPI: Core revision 20130725
    Jan 02 23:22:36 arch_1 kernel: ACPI: All ACPI Tables successfully acquired
    Jan 02 23:22:36 arch_1 kernel: ftrace: allocating 20318 entries in 80 pages
    Jan 02 23:22:36 arch_1 kernel: Performance Events: unsupported p6 CPU model 23 no PMU driver, software events
    Jan 02 23:22:36 arch_1 kernel: NMI watchdog: disabled (cpu0): hardware events not enabled
    Jan 02 23:22:36 arch_1 kernel: installing Xen timer for CPU 1
    Jan 02 23:22:36 arch_1 kernel: Brought up 2 CPUs
    Jan 02 23:22:36 arch_1 kernel: devtmpfs: initialized
    Jan 02 23:22:36 arch_1 kernel: PM: Registering ACPI NVS region [mem 0xbd9ffc00-0xbda53bff] (344064 bytes)
    Jan 02 23:22:36 arch_1 kernel: xen:grant_table: Grant tables using version 2 layout
    Jan 02 23:22:36 arch_1 kernel: Grant table initialized
    Jan 02 23:22:36 arch_1 kernel: RTC time: 4:22:33, date: 01/03/14
    Jan 02 23:22:36 arch_1 kernel: NET: Registered protocol family 16
    Jan 02 23:22:36 arch_1 kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
    Jan 02 23:22:36 arch_1 kernel: ACPI: bus type PCI registered
    Jan 02 23:22:36 arch_1 kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
    Jan 02 23:22:36 arch_1 kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base
    Jan 02 23:22:36 arch_1 kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
    Jan 02 23:22:36 arch_1 kernel: PCI: Using configuration type 1 for base access
    Jan 02 23:22:36 arch_1 kernel: dmi type 0xB1 record - unknown flag
    Jan 02 23:22:36 arch_1 kernel: bio: create slab <bio-0> at 0
    Jan 02 23:22:36 arch_1 kernel: ACPI: Added _OSI(Module Device)
    Jan 02 23:22:36 arch_1 kernel: ACPI: Added _OSI(Processor Device)
    Jan 02 23:22:36 arch_1 kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
    Jan 02 23:22:36 arch_1 kernel: ACPI: Added _OSI(Processor Aggregator Device)
    Jan 02 23:22:36 arch_1 kernel: ACPI: EC: Look up EC in DSDT
    Jan 02 23:22:36 arch_1 kernel: [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
    Jan 02 23:22:36 arch_1 kernel: ACPI BIOS Warning (bug): Incorrect checksum in table [TCPA] - 0x00, should be 0
    Jan 02 23:22:36 arch_1 kernel: ACPI: Interpreter enabled
    Jan 02 23:22:36 arch_1 kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130725/hw
    Jan 02 23:22:36 arch_1 kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20130725/hw
    Jan 02 23:22:36 arch_1 kernel: ACPI: (supports S0 S1 S4 S5)
    Jan 02 23:22:36 arch_1 kernel: ACPI: Using IOAPIC for interrupt routing
    Jan 02 23:22:36 arch_1 kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and rep
    Jan 02 23:22:36 arch_1 kernel: ACPI: ACPI Dock Station Driver: 1 docks/bays found
    Jan 02 23:22:36 arch_1 kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    Jan 02 23:22:36 arch_1 kernel: acpi PNP0A03:00: ACPI _OSC support notification failed, disabling PCIe ASPM
    Jan 02 23:22:36 arch_1 kernel: acpi PNP0A03:00: Unable to request _OSC control (_OSC support mask: 0x08)
    Jan 02 23:22:36 arch_1 kernel: acpi PNP0A03:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only par
    Jan 02 23:22:36 arch_1 kernel: PCI host bridge to bus 0000:00
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000effff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [mem 0x000f0000-0x000fffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [mem 0xfc000000-0xfec00000]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [mem 0xbdb00000-0xf7ffffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [mem 0xff980000-0xff980fff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [mem 0xff97c000-0xff97ffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [mem 0xff970000-0xff9707ff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [mem 0xfed20000-0xfed9ffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [mem 0xfeda6000-0xfeda6fff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: root bus resource [mem 0xfeda7000-0xfeda7fff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:00.0: [8086:2e10] type 00 class 0x060000
    Jan 02 23:22:36 arch_1 kernel: DMAR: Forcing write-buffer flush capability
    Jan 02 23:22:36 arch_1 kernel: DMAR: Disabling IOMMU for graphics on this chipset
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:01.0: [8086:2e11] type 01 class 0x060400
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:02.0: [8086:2e12] type 00 class 0x030000
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:02.0: reg 0x10: [mem 0xf7c00000-0xf7ffffff 64bit]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:02.0: reg 0x18: [mem 0xe0000000-0xefffffff 64bit pref]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:02.0: reg 0x20: [io 0xecb0-0xecb7]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:02.1: [8086:2e13] type 00 class 0x038000
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:02.1: reg 0x10: [mem 0xf7b00000-0xf7bfffff 64bit]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:03.0: [8086:2e14] type 00 class 0x078000
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:03.0: reg 0x10: [mem 0xfeda6000-0xfeda600f 64bit]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:03.2: [8086:2e16] type 00 class 0x010185
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:03.2: reg 0x10: [io 0xfe80-0xfe87]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:03.2: reg 0x14: [io 0xfe90-0xfe93]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:03.2: reg 0x18: [io 0xfea0-0xfea7]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:03.2: reg 0x1c: [io 0xfeb0-0xfeb3]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:03.2: reg 0x20: [io 0xfef0-0xfeff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:03.3: [8086:2e17] type 00 class 0x070002
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:03.3: reg 0x10: [io 0xecb8-0xecbf]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:03.3: reg 0x14: [mem 0xf7adc000-0xf7adcfff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:19.0: [8086:10de] type 00 class 0x020000
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:19.0: reg 0x10: [mem 0xf7ae0000-0xf7afffff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:19.0: reg 0x14: [mem 0xf7add000-0xf7addfff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:19.0: reg 0x18: [io 0xece0-0xecff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1a.0: [8086:3a67] type 00 class 0x0c0300
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1a.0: reg 0x20: [io 0xff20-0xff3f]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1a.0: System wakeup disabled by ACPI
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1a.1: [8086:3a68] type 00 class 0x0c0300
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1a.1: reg 0x20: [io 0xff00-0xff1f]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1a.1: System wakeup disabled by ACPI
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1a.2: [8086:3a69] type 00 class 0x0c0300
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1a.2: reg 0x20: [io 0xfc00-0xfc1f]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1a.2: System wakeup disabled by ACPI
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1a.7: [8086:3a6c] type 00 class 0x0c0320
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1a.7: reg 0x10: [mem 0xf7ade000-0xf7ade3ff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: [8086:3a70] type 01 class 0x060400
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: [8086:3a72] type 01 class 0x060400
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: System wakeup disabled by ACPI
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1d.0: [8086:3a64] type 00 class 0x0c0300
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1d.0: reg 0x20: [io 0xff80-0xff9f]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1d.1: [8086:3a65] type 00 class 0x0c0300
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1d.1: reg 0x20: [io 0xff60-0xff7f]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1d.1: System wakeup disabled by ACPI
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1d.2: [8086:3a66] type 00 class 0x0c0300
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1d.2: reg 0x20: [io 0xff40-0xff5f]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1d.2: System wakeup disabled by ACPI
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1d.7: [8086:3a6a] type 00 class 0x0c0320
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1d.7: reg 0x10: [mem 0xff980000-0xff9803ff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: [8086:244e] type 01 class 0x060401
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: System wakeup disabled by ACPI
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1f.0: [8086:3a14] type 00 class 0x060100
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1f.2: [8086:3a02] type 00 class 0x010601
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1f.2: reg 0x10: [io 0xfe00-0xfe07]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1f.2: reg 0x14: [io 0xfe10-0xfe13]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1f.2: reg 0x18: [io 0xfe20-0xfe27]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1f.2: reg 0x1c: [io 0xfe30-0xfe33]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1f.2: reg 0x20: [io 0xfec0-0xfedf]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xff970000-0xff9707ff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1f.2: PME# supported from D3hot
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1f.3: [8086:3a60] type 00 class 0x0c0500
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xf7adf000-0xf7adf0ff 64bit]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1f.3: reg 0x20: [io 0x0940-0x095f]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:01:00.0: [8086:105e] type 00 class 0x020000
    Jan 02 23:22:36 arch_1 kernel: pci 0000:01:00.0: reg 0x10: [mem 0xf7880000-0xf789ffff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:01:00.0: reg 0x14: [mem 0xf78a0000-0xf78bffff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:01:00.0: reg 0x18: [io 0xdcc0-0xdcdf]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:01:00.0: reg 0x30: [mem 0xf7900000-0xf791ffff pref]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
    Jan 02 23:22:36 arch_1 kernel: pci 0000:01:00.1: [8086:105e] type 00 class 0x020000
    Jan 02 23:22:36 arch_1 kernel: pci 0000:01:00.1: reg 0x10: [mem 0xf78c0000-0xf78dffff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:01:00.1: reg 0x14: [mem 0xf78e0000-0xf78fffff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:01:00.1: reg 0x18: [io 0xdce0-0xdcff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:01:00.1: PME# supported from D0 D3hot D3cold
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:01.0: bridge window [io 0xd000-0xdfff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:01.0: bridge window [mem 0xf7800000-0xf79fffff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: bridge window [mem 0xf7700000-0xf77fffff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: PCI bridge to [bus 03]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: bridge window [mem 0xf7600000-0xf76fffff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:04:00.0: [1102:0007] type 00 class 0x040100
    Jan 02 23:22:36 arch_1 kernel: pci 0000:04:00.0: reg 0x10: [io 0xcce0-0xccff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:04:00.0: supports D1 D2
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: PCI bridge to [bus 04] (subtractive decode)
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [io 0xc000-0xcfff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive deco
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [mem 0x000c0000-0x000effff] (subtractive deco
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [mem 0x000f0000-0x000fffff] (subtractive deco
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [mem 0xfc000000-0xfec00000] (subtractive deco
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [mem 0xbdb00000-0xf7ffffff] (subtractive deco
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [mem 0xff980000-0xff980fff] (subtractive deco
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [mem 0xff97c000-0xff97ffff] (subtractive deco
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [mem 0xff970000-0xff9707ff] (subtractive deco
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [mem 0xfed20000-0xfed9ffff] (subtractive deco
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [mem 0xfeda6000-0xfeda6fff] (subtractive deco
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [mem 0xfeda7000-0xfeda7fff] (subtractive deco
    Jan 02 23:22:36 arch_1 kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 15)
    Jan 02 23:22:36 arch_1 kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 6 7 9 10 11 12 15)
    Jan 02 23:22:36 arch_1 kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *9 10 11 12 15)
    Jan 02 23:22:36 arch_1 kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 *10 11 12 15)
    Jan 02 23:22:36 arch_1 kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 15) *0, disabled.
    Jan 02 23:22:36 arch_1 kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 *4 5 6 7 9 10 11 12 15)
    Jan 02 23:22:36 arch_1 kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 *5 6 7 9 10 11 12 15)
    Jan 02 23:22:36 arch_1 kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs *3 4 5 6 7 9 10 11 12 15)
    Jan 02 23:22:36 arch_1 kernel: ACPI: Enabled 2 GPEs in block 00 to 3F
    Jan 02 23:22:36 arch_1 kernel: ACPI: \_SB_.PCI0: notify handler is installed
    Jan 02 23:22:36 arch_1 kernel: Found 1 acpi root devices
    Jan 02 23:22:36 arch_1 kernel: xen:balloon: Initialising balloon driver
    Jan 02 23:22:36 arch_1 kernel: xen_balloon: Initialising balloon driver
    Jan 02 23:22:36 arch_1 kernel: vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
    Jan 02 23:22:36 arch_1 kernel: vgaarb: loaded
    Jan 02 23:22:36 arch_1 kernel: vgaarb: bridge control possible 0000:00:02.0
    Jan 02 23:22:36 arch_1 kernel: PCI: Using ACPI for IRQ routing
    Jan 02 23:22:36 arch_1 kernel: PCI: pci_cache_line_size set to 64 bytes
    Jan 02 23:22:36 arch_1 kernel: Expanded resource reserved due to conflict with PCI Bus 0000:00
    Jan 02 23:22:36 arch_1 kernel: Expanded resource reserved due to conflict with PCI Bus 0000:00
    Jan 02 23:22:36 arch_1 kernel: e820: reserve RAM buffer [mem 0x0009e000-0x0009ffff]
    Jan 02 23:22:36 arch_1 kernel: e820: reserve RAM buffer [mem 0xbd9ff000-0xbfffffff]
    Jan 02 23:22:36 arch_1 kernel: NetLabel: Initializing
    Jan 02 23:22:36 arch_1 kernel: NetLabel: domain hash size = 128
    Jan 02 23:22:36 arch_1 kernel: NetLabel: protocols = UNLABELED CIPSOv4
    Jan 02 23:22:36 arch_1 kernel: NetLabel: unlabeled traffic allowed by default
    Jan 02 23:22:36 arch_1 kernel: Switched to clocksource xen
    Jan 02 23:22:36 arch_1 kernel: pnp: PnP ACPI init
    Jan 02 23:22:36 arch_1 kernel: ACPI: bus type PNP registered
    Jan 02 23:22:36 arch_1 kernel: system 00:00: [io 0x0800-0x085f] could not be reserved
    Jan 02 23:22:36 arch_1 kernel: system 00:00: [io 0x0c00-0x0c7f] has been reserved
    Jan 02 23:22:36 arch_1 kernel: system 00:00: [io 0x0860-0x08ff] has been reserved
    Jan 02 23:22:36 arch_1 kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
    Jan 02 23:22:36 arch_1 kernel: pnp 00:01: [dma 4]
    Jan 02 23:22:36 arch_1 kernel: pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 13 triggering 1 polarity 0
    Jan 02 23:22:36 arch_1 kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0c04 (active)
    Jan 02 23:22:36 arch_1 kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0800 (active)
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 8 triggering 1 polarity 0
    Jan 02 23:22:36 arch_1 kernel: pnp 00:04: Plug and Play ACPI device, IDs PNP0b00 (active)
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 6 triggering 1 polarity 0
    Jan 02 23:22:36 arch_1 kernel: pnp 00:05: [dma 2]
    Jan 02 23:22:36 arch_1 kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0700 (active)
    Jan 02 23:22:36 arch_1 kernel: pnp 00:06: Plug and Play ACPI device, IDs PNP0103 (active)
    Jan 02 23:22:36 arch_1 kernel: pnp: PnP ACPI: found 7 devices
    Jan 02 23:22:36 arch_1 kernel: ACPI: bus type PNP unregistered
    Jan 02 23:22:36 arch_1 kernel: PM-Timer failed consistency check (0xffffff) - aborting.
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: bridge window [io 0x1000-0x0fff] to [bus 02] add_size 1000
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: bridge window [io 0x1000-0x0fff] to [bus 03] add_size 1000
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_si
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_si
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: BAR 15: assigned [mem 0xfc000000-0xfc1fffff 64bit pref]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: BAR 15: assigned [mem 0xfc200000-0xfc3fffff 64bit pref]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: BAR 13: assigned [io 0x1000-0x1fff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: BAR 13: assigned [io 0x2000-0x2fff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:01.0: bridge window [io 0xd000-0xdfff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:01.0: bridge window [mem 0xf7800000-0xf79fffff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: bridge window [io 0x1000-0x1fff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: bridge window [mem 0xf7700000-0xf77fffff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.0: bridge window [mem 0xfc000000-0xfc1fffff 64bit pref]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: PCI bridge to [bus 03]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: bridge window [io 0x2000-0x2fff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: bridge window [mem 0xf7600000-0xf76fffff]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1c.1: bridge window [mem 0xfc200000-0xfc3fffff 64bit pref]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: PCI bridge to [bus 04]
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:1e.0: bridge window [io 0xc000-0xcfff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000effff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 8 [mem 0x000f0000-0x000fffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 9 [mem 0xfc000000-0xfec00000]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 10 [mem 0xbdb00000-0xf7ffffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 11 [mem 0xff980000-0xff980fff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 12 [mem 0xff97c000-0xff97ffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 13 [mem 0xff970000-0xff9707ff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 14 [mem 0xfed20000-0xfed9ffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 15 [mem 0xfeda6000-0xfeda6fff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:00: resource 16 [mem 0xfeda7000-0xfeda7fff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:01: resource 0 [io 0xd000-0xdfff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:01: resource 1 [mem 0xf7800000-0xf79fffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:02: resource 0 [io 0x1000-0x1fff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:02: resource 1 [mem 0xf7700000-0xf77fffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:02: resource 2 [mem 0xfc000000-0xfc1fffff 64bit pref]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:03: resource 0 [io 0x2000-0x2fff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:03: resource 1 [mem 0xf7600000-0xf76fffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:03: resource 2 [mem 0xfc200000-0xfc3fffff 64bit pref]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 0 [io 0xc000-0xcfff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 4 [io 0x0000-0x0cf7]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 5 [io 0x0d00-0xffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 6 [mem 0x000a0000-0x000bffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 7 [mem 0x000c0000-0x000effff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 8 [mem 0x000f0000-0x000fffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 9 [mem 0xfc000000-0xfec00000]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 10 [mem 0xbdb00000-0xf7ffffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 11 [mem 0xff980000-0xff980fff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 12 [mem 0xff97c000-0xff97ffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 13 [mem 0xff970000-0xff9707ff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 14 [mem 0xfed20000-0xfed9ffff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 15 [mem 0xfeda6000-0xfeda6fff]
    Jan 02 23:22:36 arch_1 kernel: pci_bus 0000:04: resource 16 [mem 0xfeda7000-0xfeda7fff]
    Jan 02 23:22:36 arch_1 kernel: NET: Registered protocol family 2
    Jan 02 23:22:36 arch_1 kernel: TCP established hash table entries: 65536 (order: 8, 1048576 bytes)
    Jan 02 23:22:36 arch_1 kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
    Jan 02 23:22:36 arch_1 kernel: TCP: Hash tables configured (established 65536 bind 65536)
    Jan 02 23:22:36 arch_1 kernel: TCP: reno registered
    Jan 02 23:22:36 arch_1 kernel: UDP hash table entries: 4096 (order: 5, 131072 bytes)
    Jan 02 23:22:36 arch_1 kernel: UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
    Jan 02 23:22:36 arch_1 kernel: NET: Registered protocol family 1
    Jan 02 23:22:36 arch_1 kernel: pci 0000:00:02.0: Boot video device
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 16 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=16 -> irq=16 (gsi=16)
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 17 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=17 -> irq=17 (gsi=17)
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 22 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=22 -> irq=22 (gsi=22)
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 22 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :22
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 23 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=23 -> irq=23 (gsi=23)
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 17 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :17
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 18 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: xen: --> pirq=18 -> irq=18 (gsi=18)
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 23 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :23
    Jan 02 23:22:36 arch_1 kernel: PCI: CLS 64 bytes, default 64
    Jan 02 23:22:36 arch_1 kernel: Unpacking initramfs...
    Jan 02 23:22:36 arch_1 kernel: Freeing initrd memory: 10924K (ffff880001f54000 - ffff8800029ff000)
    Jan 02 23:22:36 arch_1 kernel: Simple Boot Flag at 0x7a set to 0x1
    Jan 02 23:22:36 arch_1 kernel: Scanning for low memory corruption every 60 seconds
    Jan 02 23:22:36 arch_1 kernel: audit: initializing netlink socket (disabled)
    Jan 02 23:22:36 arch_1 kernel: type=2000 audit(1388722954.276:1): initialized
    Jan 02 23:22:36 arch_1 kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
    Jan 02 23:22:36 arch_1 kernel: zbud: loaded
    Jan 02 23:22:36 arch_1 kernel: VFS: Disk quotas dquot_6.5.2
    Jan 02 23:22:36 arch_1 kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    Jan 02 23:22:36 arch_1 kernel: msgmni has been set to 3650
    Jan 02 23:22:36 arch_1 kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    Jan 02 23:22:36 arch_1 kernel: io scheduler noop registered
    Jan 02 23:22:36 arch_1 kernel: io scheduler deadline registered
    Jan 02 23:22:36 arch_1 kernel: io scheduler cfq registered (default)
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 16 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :16
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 16 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :16
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 17 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :17
    Jan 02 23:22:36 arch_1 kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    Jan 02 23:22:36 arch_1 kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
    Jan 02 23:22:36 arch_1 kernel: intel_idle: does not run on family 6 model 23
    Jan 02 23:22:36 arch_1 kernel: GHES: HEST is not enabled!
    Jan 02 23:22:36 arch_1 kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 17 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :17
    Jan 02 23:22:36 arch_1 kernel: 0000:00:03.3: ttyS0 at I/O 0xecb8 (irq = 17, base_baud = 115200) is a 16550A
    Jan 02 23:22:36 arch_1 kernel: hpet_acpi_add: no address or irqs in _CRS
    Jan 02 23:22:36 arch_1 kernel: Linux agpgart interface v0.103
    Jan 02 23:22:36 arch_1 kernel: i8042: PNP: No PS/2 controller found. Probing ports directly.
    Jan 02 23:22:36 arch_1 kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
    Jan 02 23:22:36 arch_1 kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
    Jan 02 23:22:36 arch_1 kernel: mousedev: PS/2 mouse device common for all mice
    Jan 02 23:22:36 arch_1 kernel: rtc_cmos 00:04: RTC can wake from S4
    Jan 02 23:22:36 arch_1 kernel: rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
    Jan 02 23:22:36 arch_1 kernel: rtc_cmos 00:04: alarms up to one day, 242 bytes nvram
    Jan 02 23:22:36 arch_1 kernel: drop_monitor: Initializing network drop monitor service
    Jan 02 23:22:36 arch_1 kernel: TCP: cubic registered
    Jan 02 23:22:36 arch_1 kernel: NET: Registered protocol family 10
    Jan 02 23:22:36 arch_1 kernel: NET: Registered protocol family 17
    Jan 02 23:22:36 arch_1 kernel: Key type dns_resolver registered
    Jan 02 23:22:36 arch_1 kernel: registered taskstats version 1
    Jan 02 23:22:36 arch_1 kernel: Magic number: 14:436:362
    Jan 02 23:22:36 arch_1 kernel: rtc_cmos 00:04: setting system clock to 2014-01-03 04:22:34 UTC (1388722954)
    Jan 02 23:22:36 arch_1 kernel: PM: Hibernation image not present or could not be loaded.
    Jan 02 23:22:36 arch_1 kernel: Freeing unused kernel memory: 1144K (ffffffff818cb000 - ffffffff819e9000)
    Jan 02 23:22:36 arch_1 kernel: Write protecting the kernel read-only data: 8192k
    Jan 02 23:22:36 arch_1 kernel: Freeing unused kernel memory: 1008K (ffff880001504000 - ffff880001600000)
    Jan 02 23:22:36 arch_1 kernel: Freeing unused kernel memory: 420K (ffff880001797000 - ffff880001800000)
    Jan 02 23:22:36 arch_1 systemd-udevd[50]: starting version 208
    Jan 02 23:22:36 arch_1 kernel: Floppy drive(s): fd0 is 1.44M
    Jan 02 23:22:36 arch_1 kernel: ACPI: bus type USB registered
    Jan 02 23:22:36 arch_1 kernel: usbcore: registered new interface driver usbfs
    Jan 02 23:22:36 arch_1 kernel: usbcore: registered new interface driver hub
    Jan 02 23:22:36 arch_1 kernel: SCSI subsystem initialized
    Jan 02 23:22:36 arch_1 kernel: usbcore: registered new device driver usb
    Jan 02 23:22:36 arch_1 kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    Jan 02 23:22:36 arch_1 kernel: ehci-pci: EHCI PCI platform driver
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 22 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :22
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1a.7: setting latency timer to 64
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1a.7: EHCI Host Controller
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1a.7: new USB bus registered, assigned bus number 1
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1a.7: debug port 1
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd: USB Universal Host Controller Interface driver
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1a.7: cache line size of 64 is not supported
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1a.7: irq 22, io mem 0xf7ade000
    Jan 02 23:22:36 arch_1 kernel: FDC 0 is a post-1991 82077
    Jan 02 23:22:36 arch_1 kernel: libata version 3.00 loaded.
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1a.7: USB 2.0 started, EHCI 1.00
    Jan 02 23:22:36 arch_1 kernel: hub 1-0:1.0: USB hub found
    Jan 02 23:22:36 arch_1 kernel: hub 1-0:1.0: 6 ports detected
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 16 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :16
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1a.0: setting latency timer to 64
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1a.0: UHCI Host Controller
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 2
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1a.0: irq 16, io base 0x0000ff20
    Jan 02 23:22:36 arch_1 kernel: hub 2-0:1.0: USB hub found
    Jan 02 23:22:36 arch_1 kernel: hub 2-0:1.0: 2 ports detected
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 17 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :17
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1a.1: setting latency timer to 64
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1a.1: UHCI Host Controller
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 3
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1a.1: irq 17, io base 0x0000ff00
    Jan 02 23:22:36 arch_1 kernel: hub 3-0:1.0: USB hub found
    Jan 02 23:22:36 arch_1 kernel: hub 3-0:1.0: 2 ports detected
    Jan 02 23:22:36 arch_1 kernel: ahci 0000:00:1f.2: version 3.0
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 18 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :18
    Jan 02 23:22:36 arch_1 kernel: ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 6 ports 3 Gbps 0x2f impl SATA mode
    Jan 02 23:22:36 arch_1 kernel: ahci 0000:00:1f.2: flags: 64bit ncq sntf led clo pio ems sxs
    Jan 02 23:22:36 arch_1 kernel: ahci 0000:00:1f.2: setting latency timer to 64
    Jan 02 23:22:36 arch_1 kernel: scsi0 : ahci
    Jan 02 23:22:36 arch_1 kernel: scsi1 : ahci
    Jan 02 23:22:36 arch_1 kernel: scsi2 : ahci
    Jan 02 23:22:36 arch_1 kernel: scsi3 : ahci
    Jan 02 23:22:36 arch_1 kernel: scsi4 : ahci
    Jan 02 23:22:36 arch_1 kernel: scsi5 : ahci
    Jan 02 23:22:36 arch_1 kernel: ata1: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970100 irq 58
    Jan 02 23:22:36 arch_1 kernel: ata2: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970180 irq 58
    Jan 02 23:22:36 arch_1 kernel: ata3: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970200 irq 58
    Jan 02 23:22:36 arch_1 kernel: ata4: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970280 irq 58
    Jan 02 23:22:36 arch_1 kernel: ata5: DUMMY
    Jan 02 23:22:36 arch_1 kernel: ata6: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970380 irq 58
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 18 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :18
    Jan 02 23:22:36 arch_1 kernel: pata_acpi 0000:00:03.2: setting latency timer to 64
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 22 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :22
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1a.2: setting latency timer to 64
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1a.2: UHCI Host Controller
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 4
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1a.2: irq 22, io base 0x0000fc00
    Jan 02 23:22:36 arch_1 kernel: hub 4-0:1.0: USB hub found
    Jan 02 23:22:36 arch_1 kernel: hub 4-0:1.0: 2 ports detected
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 23 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :23
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1d.0: setting latency timer to 64
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1d.0: UHCI Host Controller
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 5
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000ff80
    Jan 02 23:22:36 arch_1 kernel: hub 5-0:1.0: USB hub found
    Jan 02 23:22:36 arch_1 kernel: hub 5-0:1.0: 2 ports detected
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 17 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :17
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1d.1: setting latency timer to 64
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1d.1: UHCI Host Controller
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 6
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1d.1: irq 17, io base 0x0000ff60
    Jan 02 23:22:36 arch_1 kernel: hub 6-0:1.0: USB hub found
    Jan 02 23:22:36 arch_1 kernel: hub 6-0:1.0: 2 ports detected
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 18 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :18
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1d.2: setting latency timer to 64
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1d.2: UHCI Host Controller
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 7
    Jan 02 23:22:36 arch_1 kernel: uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000ff40
    Jan 02 23:22:36 arch_1 kernel: hub 7-0:1.0: USB hub found
    Jan 02 23:22:36 arch_1 kernel: hub 7-0:1.0: 2 ports detected
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 23 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :23
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1d.7: setting latency timer to 64
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1d.7: EHCI Host Controller
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1d.7: new USB bus registered, assigned bus number 8
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1d.7: debug port 1
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1d.7: cache line size of 64 is not supported
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1d.7: irq 23, io mem 0xff980000
    Jan 02 23:22:36 arch_1 kernel: ehci-pci 0000:00:1d.7: USB 2.0 started, EHCI 1.00
    Jan 02 23:22:36 arch_1 kernel: hub 8-0:1.0: USB hub found
    Jan 02 23:22:36 arch_1 kernel: hub 8-0:1.0: 6 ports detected
    Jan 02 23:22:36 arch_1 kernel: hub 5-0:1.0: USB hub found
    Jan 02 23:22:36 arch_1 kernel: hub 5-0:1.0: 2 ports detected
    Jan 02 23:22:36 arch_1 kernel: hub 6-0:1.0: USB hub found
    Jan 02 23:22:36 arch_1 kernel: hub 6-0:1.0: 2 ports detected
    Jan 02 23:22:36 arch_1 kernel: hub 7-0:1.0: USB hub found
    Jan 02 23:22:36 arch_1 kernel: hub 7-0:1.0: 2 ports detected
    Jan 02 23:22:36 arch_1 kernel: xen: registering gsi 18 triggering 0 polarity 1
    Jan 02 23:22:36 arch_1 kernel: Already setup the GSI :18
    Jan 02 23:22:36 arch_1 kernel: ata_generic 0000:00:03.2: setting latency timer to 64
    Jan 02 23:22:36 arch_1 kernel: scsi6 : ata_generic
    Jan 02 23:22:36 arch_1 kernel: scsi7 : ata_generic
    Jan 02 23:22:36 arch_1 kernel: ata7: PATA max UDMA/100 cmd 0xfe80 ctl 0xfe90 bmdma 0xfef0 irq 18
    Jan 02 23:22:36 arch_1 kernel: ata8: PATA max UDMA/100 cmd 0xfea0 ctl 0xfeb0 bmdma 0xfef8 irq 18
    Jan 02 23:22:36 arch_1 kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    Jan 02 23:22:36 arch_1 kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Jan 02 23:22:36 arch_1 kernel: ata4: SATA link down (SStatus 0 SControl 300)
    Jan 02 23:22:36 arch_1 kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    Jan 02 23:22:36 arch_1 kernel: ata6: SATA link down (SStatus 0 SControl 300)
    Jan 02 23:22:36 arch_1 kernel: ata2.00: ATAPI: PIONEER DVD-RW DVR-217D, 1.07, max UDMA/66
    Jan 02 23:22:36 arch_1 kernel: ata3.00: ATA-8: WDC WD15EARX-00ZUDB0, 80.00A80, max UDMA/133
    Jan 02 23:22:36 arch_1 kernel: ata3.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
    Jan 02 23:22:36 arch_1 kernel: ata1.00: ATA-6: WDC WD360GD-00FNA0, 34.06J34, max UDMA/133
    Jan 02 23:22:36 arch_1 kernel: ata1.00: 72303840 sectors, multi 0: LBA48
    Jan 02 23:22:36 arch_1 kernel: ata1.00: applying bridge limits
    Jan 02 23:22:36 arch_1 kernel: ata2.00: configured for UDMA/66
    Jan 02 23:22:36 arch_1 kernel: ata3.00: configured for UDMA/133
    Jan 02 23:22:36 arch_1 kernel: ata1.00: configured for UDMA/100
    Jan 02 23:22:36 arch_1 kernel: scsi 0:0:0:0: Direct-Access ATA WDC WD360GD-00FN 34.0 PQ: 0 ANSI: 5
    Jan 02 23:22:36 arch_1 kernel: scsi 1:0:0:0: CD-ROM PIONEER DVD-RW DVR-217D 1.07 PQ: 0 ANSI: 5
    Jan 02 23:22:36 arch_1 kernel: scsi 2:0:0:0: Direct-Access ATA WDC WD15EARX-00Z 80.0 PQ: 0 ANSI: 5
    Jan 02 23:22:36 arch_1 kernel: sd 0:0:0:0: [sda] 72303840 512-byte logical blocks: (37.0 GB/34.4 GiB)
    Jan 02 23:22:36 arch_1 kernel: sd 2:0:0:0: [sdb] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
    Jan 02 23:22:36 arch_1 kernel: sd 2:0:0:0: [sdb] 4096-byte physical blocks
    Jan 02 23:22:36 arch_1 kernel: sd 0:0:0:0: [sda] Write Protect is off
    Jan 02 23:22:36 arch_1 kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
    Jan 02 23:22:36 arch_1 kernel: sd 2:0:0:0: [sdb] Write Protect is off
    Jan 02 23:22:36 arch_1 kernel: sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
    Jan 02 23:22:36 arch_1 kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DP
    Jan 02 23:22:36 arch_1 kernel: sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DP
    Jan 02 23:22:36 arch_1 kernel: sda: sda1 sda2
    Jan 02 23:22:36 arch_1 kernel: sdb: sdb1
    Jan 02 23:22:36 arch_1 kernel: sd 0:0:0:0: [sda] Attached SCSI disk
    Jan 02 23:22:36 arch_1 kernel: sd 2:0:0:0: [sdb] Attached SCSI disk
    Jan 02 23:22:36 arch_1 kernel: sr0: scsi3-mmc drive: 16x/16x writer cd/rw xa/form2 cdda tray
    Jan 02 23:22:36 arch_1 kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
    Jan 02 23:22:36 arch_1 kernel: sr 1:0:0:0: Attached scsi CD-ROM sr0
    Jan 02 23:22:36 arch_1 kernel: usb 3-2: new full-speed USB device number 2 using uhci_hcd
    Jan 02 23:22:36 arch_1 kernel: end_request: I/O error, dev fd0, sector 0
    Jan 02 23:22:36 arch_1 kernel: end_request: I/O error, dev fd0, sector 0
    Jan 02 23:22:36 arch_1 kernel: hub 3-2:1.0: USB hub found
    Jan 02 23:22:36 arch_1 kernel: hub 3-2:1.0: 3 ports detected
    Jan 02 23:22:36 arch_1 kernel: device-mapper: uevent: version 1.0.3
    Jan 02 23:22:36 arch_1 kernel: device-mapper: ioctl: 4.26.0-ioctl (2013-08-15) initialised: [email protected]
    Jan 02 23:22:36 arch_1 kernel: bio: create slab <bio-1> at 1
    Jan 02 23:22:36 arch_1 kernel: usb 3-2.2: new full-speed USB device number 3 using uhci_hcd
    Jan 02 23:22:36 arch_1 kernel: hidraw: raw HID events driver (C) Jiri Kosina
    Jan 02 23:22:36 arch_1 kernel: usbcore: registered new interface driver usbhid
    Jan 02 23:22:36 arch_1 kernel: usbhid: USB HID core driver
    Jan 02 23:22:36 arch_1 kernel: input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:1a.1/u
    Jan 02 23:22:36 arch_1 kernel: hid-generic 0003:046D:C713.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitec
    Jan 02 23:22:36 arch_1 kernel: EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
    Jan 02 23:22:36 arch_1 kernel: usb 3-2.3: new full-speed USB device number 4 using uhci_hcd
    Jan 02 23:22:36 arch_1 systemd[1]: systemd 208 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SY
    Jan 02 23:22:36 arch_1 systemd[1]: Detected virtualization 'xen'.
    Jan 02 23:22:36 arch_1 systemd[1]: Set hostname to <arch_1>.
    Jan 02 23:22:36 arch_1 systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit
    Jan 02 23:22:36 arch_1 systemd[1]: Expecting device dev-hvc0.device...
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
    Jan 02 23:22:36 arch_1 systemd[1]: Started Forward Password Requests to Wall Directory Watch.
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Remote File Systems.
    Jan 02 23:22:36 arch_1 systemd[1]: Reached target Remote File Systems.
    Jan 02 23:22:36 arch_1 systemd[1]: Expecting device sys-subsystem-net-devices-enp0s25.device...
    Jan 02 23:22:36 arch_1 systemd[1]: Starting LVM2 metadata daemon socket.
    Jan 02 23:22:36 arch_1 systemd[1]: Listening on LVM2 metadata daemon socket.
    Jan 02 23:22:36 arch_1 systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
    Jan 02 23:22:36 arch_1 systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Delayed Shutdown Socket.
    Jan 02 23:22:36 arch_1 systemd[1]: Listening on Delayed Shutdown Socket.
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Device-mapper event daemon FIFOs.
    Jan 02 23:22:36 arch_1 systemd[1]: Listening on Device-mapper event daemon FIFOs.
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
    Jan 02 23:22:36 arch_1 systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Paths.
    Jan 02 23:22:36 arch_1 systemd[1]: Reached target Paths.
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Journal Socket.
    Jan 02 23:22:36 arch_1 systemd[1]: Listening on Journal Socket.
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Setup Virtual Console...
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Load Kernel Modules...
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Journal Service...
    Jan 02 23:22:36 arch_1 systemd[1]: Started Journal Service.
    Jan 02 23:22:36 arch_1 systemd-journal[129]: Journal started
    Jan 02 23:22:36 arch_1 systemd[1]: Starting udev Kernel Socket.
    Jan 02 23:22:36 arch_1 systemd[1]: Listening on udev Kernel Socket.
    Jan 02 23:22:36 arch_1 systemd[1]: Starting udev Control Socket.
    Jan 02 23:22:36 arch_1 systemd[1]: Listening on udev Control Socket.
    Jan 02 23:22:36 arch_1 systemd[1]: Starting udev Coldplug all Devices...
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
    Jan 02 23:22:36 arch_1 systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Po
    Jan 02 23:22:36 arch_1 systemd[1]: Started Set Up Additional Binary Formats.
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Create list of required static device nodes for the current kernel
    Jan 02 23:22:36 arch_1 systemd[1]: Mounting Huge Pages File System...
    Jan 02 23:22:36 arch_1 systemd[1]: Starting Encrypted Volumes.
    Jan 02 23:22:36 arch_1 systemd[1]: Reached target Encrypted Volumes.
    Jan 02 23:22:36 arch_1 systemd[1]: Mounting Debug File System...
    Jan 02 23:22:36 arch_1 systemd[1]: Mounting POSIX Message Queue File System...
    Jan 02 23:22:37 arch_1 systemd[1]: Starting Apply Kernel Variables...
    Jan 02 23:22:37 arch_1 systemd[1]: Starting Swap.
    Jan 02 23:22:37 arch_1 systemd[1]: Reached target Swap.
    Jan 02 23:22:37 arch_1 systemd[1]: Started File System Check on Root Device.
    Jan 02 23:22:37 arch_1 systemd[1]: Starting Remount Root and Kernel File Systems...
    Jan 02 23:22:37 arch_1 systemd[1]: Expecting device dev-disk-by\x2duuid-1f355bf1\x2d1469\x2d4722\x2d8f65\x2d01
    Jan 02 23:22:37 arch_1 systemd[1]: Starting Root Slice.
    Jan 02 23:22:37 arch_1 systemd[1]: Created slice Root Slice.
    Jan 02 23:22:37 arch_1 systemd[1]: Starting User and Session Slice.
    Jan 02 23:22:37 arch_1 systemd[1]: Created slice User and Session Slice.
    Jan 02 23:22:37 arch_1 systemd[1]: Starting System Slice.
    Jan 02 23:22:37 arch_1 systemd[1]: Created slice System Slice.
    Jan 02 23:22:37 arch_1 systemd[1]: Starting system-netctl.slice.
    Jan 02 23:22:37 arch_1 systemd[1]: Created slice system-netctl.slice.
    Jan 02 23:22:37 arch_1 systemd[1]: Starting system-getty.slice.
    Jan 02 23:22:37 arch_1 systemd[1]: Created slice system-getty.slice.
    Jan 02 23:22:37 arch_1 systemd[1]: Starting system-serial\x2dgetty.slice.
    Jan 02 23:22:37 arch_1 systemd[1]: Created slice system-serial\x2dgetty.slice.
    Jan 02 23:22:37 arch_1 systemd[1]: Starting Slices.
    Jan 02 23:22:37 arch_1 systemd[1]: Reached target Slices.
    Jan 02 23:22:37 arch_1 systemd[1]: Started udev Coldplug all Devices.
    Jan 02 23:22:37 arch_1 kernel: FS-Cache: Loaded
    Jan 02 23:22:37 arch_1 kernel: RPC: Registered named UNIX socket transport module.
    Jan 02 23:22:37 arch_1 kernel: RPC: Registered udp transport module.
    Jan 02 23:22:37 arch_1 kernel: RPC: Registered tcp transport module.
    Jan 02 23:22:37 arch_1 kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
    Jan 02 23:22:37 arch_1 systemd-modules-load[128]: Inserted module 'nfs'
    Jan 02 23:22:37 arch_1 kernel: FS-Cache: Netfs 'nfs' registered for caching
    Jan 02 23:22:37 arch_1 systemd-modules-load[128]: Inserted module 'xen_evtchn'
    Jan 02 23:22:37 arch_1 kernel: xen:xen_evtchn: Event-channel device installed
    Jan 02 23:22:37 arch_1 systemd-modules-load[128]: Inserted module 'xen_gntdev'
    Jan 02 23:22:37 arch_1 systemd-modules-load[128]: Inserted module 'xen_gntalloc'
    Jan 02 23:22:37 arch_1 systemd-modules-load[128]: Inserted module 'xen_blkback'
    Jan 02 23:22:37 arch_1 systemd-modules-load[128]: Inserted module 'xen_netback'
    Jan 02 23:22:37 arch_1 systemd-modules-load[128]: Inserted module 'xen_pciback'
    Jan 02 23:22:37 arch_1 kernel: xen_pciback: backend is vpci
    Jan 02 23:22:37 arch_1 kernel: ACPI: Requesting acpi_cpufreq
    Jan 02 23:22:37 arch_1 kernel: Monitor-Mwait will be used to enter C-1 state
    Jan 02 23:22:37 arch_1 kernel: Warning: Processor Platform Limit not supported.
    Jan 02 23:22:37 arch_1 systemd[1]: Started Apply Kernel Variables.
    Jan 02 23:22:37 arch_1 systemd[1]: Started Setup Virtual Console.
    Jan 02 23:22:37 arch_1 systemd[1]: Mounted Huge Pages File System.
    Jan 02 23:22:37 arch_1 kernel: xen_acpi_processor: Uploading Xen processor PM info
    Jan 02 23:22:37 arch_1 systemd[1]: Mounted Debug File System.
    Jan 02 23:22:37 arch_1 systemd-modules-load[128]: Inserted module 'xen_acpi_processor'
    Jan 02 23:22:37 arch_1 systemd[1]: Mounted POSIX Message Queue File System.
    Jan 02 23:22:37 arch_1 systemd[1]: Started Load Kernel Modules.
    Jan 02 23:22:37 arch_1 systemd[1]: Mounting Configuration File System...
    Jan 02 23:22:37 arch_1 systemd[1]: Mounted FUSE Control File System.
    Jan 02 23:22:37 arch_1 systemd[1]: Mounted Configuration File System.
    Jan 02 23:22:37 arch_1 systemd[1]: Started Create list of required static device nodes for the current kernel.
    Jan 02 23:22:37 arch_1 systemd[1]: Starting Create static device nodes in /dev...
    Jan 02 23:22:37 arch_1 systemd[1]: Started Remount Root and Kernel File Systems.
    Jan 02 23:22:37 arch_1 systemd[1]: Starting Load/Save Random Seed...
    Jan 02 23:22:37 arch_1 kernel: EXT4-fs (dm-0): re-mounted. Opts: data=ordered
    Jan 02 23:22:37 arch_1 systemd[1]: Started Load/Save Random Seed.
    Jan 02 23:22:37 arch_1 systemd[1]: Started Create static device nodes in /dev.
    Jan 02 23:22:37 arch_1 systemd[1]: Starting udev Kernel Device Manager...
    Jan 02 23:22:37 arch_1 systemd[1]: Starting Local File Systems (Pre).
    Jan 02 23:22:37 arch_1 systemd[1]: Reached target Local File Systems (Pre).
    Jan 02 23:22:37 arch_1 systemd[1]: Mounting /tmp...
    Jan 02 23:22:37 arch_1 systemd[1]: Mountin

    I have the same problem on Fedora Core 20 with xen 4.3.1 32bit Sempron3200+ with turned off HPET tables on South bridge and these boot options
    xen: noreboot nosmp console_to_ring console=vga vga=text-80x50
    linux: pci=noacpi pci=nommconf
    Image on Yandex disk
    When I solve it I notify you.
    Last edited by maskimko (2014-01-16 08:12:35)

  • Multiple kernel panics related to java and NTFS

    Over the past week, I have experienced at least three separate kernel panics, but only two have had their event recorded by the System Diagnostic Reports.  I was wondering if there are any known issues that could cause kernel panic, such as the ones my system has received.  I have attached the result of the most recent panic below.
    Please note that I am running OS X 10.7.4 on a Mac Pro (early 2008) with 14GB RAM.  At the time the panics occurred, CrashPlan was in the process of backing up files (to CrashPlan Central) from my Boot Camp partition, which has Windows XP installed on a NTFS drive.  I mention this, because the fault appears to be related to NTFS and Java.  My understanding is that CrashPlan uses Java, and I don't believe I have many other (if any) applications running on it typically.
    I should also mentioned that I may have had Parallels Desktop running at the same time, and had a Windows XP virtual running the CrashPlan client for Windows that was overseeing the backup on my Synology DiskStation NAS.  At this time, I do not believe this is related to the panic, as I have been using Parallels in such a manner for weeks prior, and never received a panic.  Also, while the CrashPlan client in Windows also uses java, due to the VM sandbox, I believe the java is handled internally by Parallels, and doesn't utilize any java thread outside of Parallels.
    As I mentioned earlier, I have two recorded panics apparently caused by the same issue, having occurred in the "java" thread and related to "ntfs_attr_record_move_for_attr_list_attribute()".  I noticed that the other report also includes a section at the bottom for "System Profile" with information, such as:
    Model: MacPro3,1, BootROM MP31.006C.B05, 8 processors, Quad-Core Intel Xeon, 2.8 GHz, 14 GB, SMC 1.25f4
    Graphics: ATI Radeon HD 5770, ATI Radeon HD 5770, PCIe, 1024 MB
    Memory Module: DIMM Riser B/DIMM 1, 2 GB, DDR2 FB-DIMM, 800 MHz, 0x0000, 0x000000463732353642363145353830304600
    Memory Module: DIMM Riser B/DIMM 2, 2 GB, DDR2 FB-DIMM, 800 MHz, 0x0000, 0x000000463732353642363145353830304600
    Memory Module: DIMM Riser A/DIMM 1, 4 GB, DDR2 FB-DIMM, 800 MHz, 0x80AD, 0x485900503132354637324350344E332D5336
    ... ETC ...
    Why would some kernel panics include the system profile while others do not?  Are the panic logs "complete" or can they be incomplete due to the kernel locking up before writing the entire log?
    I have been using this system since 2008, and gone through numerous OS and Parallels updates over the years.  At this time, I appear to be update-to-date on all software.  I do not recall ever having received a kernel panic in the past, and if I have, it would have been extremely infrequent with the last occurring many years ago.
    An seemingly similar report:  https://discussions.apple.com/message/16566759#16566759
    Thu Jun  7 01:59:30 2012
    panic(cpu 1 caller 0xffffff7f80b50b57): "ntfs_attr_record_move_for_attr_list_attribute(): err\n"@/SourceCache/ntfs/ntfs-80.1/kext/ntfs_attr.c:3612
    Backtrace (CPU 1), Frame : Return Address
    0xffffff8197f9b590 : 0xffffff8000220792
    0xffffff8197f9b610 : 0xffffff7f80b50b57
    0xffffff8197f9b680 : 0xffffff7f80b68017
    0xffffff8197f9b7d0 : 0xffffff7f80b57b60
    0xffffff8197f9b880 : 0xffffff7f80b44bc9
    0xffffff8197f9b930 : 0xffffff7f80b38eea
    0xffffff8197f9b990 : 0xffffff80003196cb
    0xffffff8197f9b9d0 : 0xffffff80003183c7
    0xffffff8197f9ba60 : 0xffffff80002f6904
    0xffffff8197f9baa0 : 0xffffff80002f6e7d
    0xffffff8197f9baf0 : 0xffffff80002f7262
    0xffffff8197f9bb70 : 0xffffff80002f5eac
    0xffffff8197f9bc10 : 0xffffff8000308a62
    0xffffff8197f9bd90 : 0xffffff80003094ec
    0xffffff8197f9bf50 : 0xffffff80005cd61b
    0xffffff8197f9bfb0 : 0xffffff80002daa13
          Kernel Extensions in backtrace:
            com.apple.filesystems.ntfs(3.10.1)[13494759-5AEF-34F4-BD38-E47CDA5F2867]@0xffff ff7f80b31000->0xffffff7f80b8cfff
    BSD process name corresponding to current thread: java
    Boot args: -v
    Mac OS version:
    11E53
    Kernel version:
    Darwin Kernel Version 11.4.0: Mon Apr  9 19:32:15 PDT 2012; root:xnu-1699.26.8~1/RELEASE_X86_64
    Kernel UUID: A8ED611D-FB0F-3729-8392-E7A32C5E7D74
    System model name: MacPro3,1 (Mac-F42C88C8)
    System uptime in nanoseconds: 33615123826096
    last loaded kext at 27671676915162: com.apple.filesystems.ntfs    3.10.1 (addr 0xffffff7f80b31000, size 376832)
    last unloaded kext at 23373040217579: com.apple.driver.AppleUSBCDC    4.1.17 (addr 0xffffff7f807c6000, size 12288)
    loaded kexts:
    com.parallels.filesystems.prlufs    2010.12.28
    com.parallels.kext.prl_vnic    7.0 15094.749908
    com.parallels.kext.prl_netbridge    7.0 15094.749908
    com.parallels.kext.prl_hid_hook    7.0 15094.749908
    com.parallels.kext.prl_hypervisor    7.0 15094.749908
    com.parallels.kext.prl_usb_connect    7.0 15094.749908
    com.apple.filesystems.ntfs    3.10.1
    com.apple.filesystems.afpfs    9.8.1
    com.apple.nke.asp_tcp    6.0.1
    com.apple.filesystems.smbfs    1.7.2
    com.apple.filesystems.autofs    3.0
    com.apple.driver.AudioAUUC    1.59
    com.apple.driver.AppleHDA    2.2.0f3
    com.apple.driver.AppleUpstreamUserClient    3.5.9
    com.apple.driver.AppleMCCSControl    1.0.26
    com.apple.kext.ATIFramebuffer    7.1.8
    com.apple.ATIRadeonX3000    7.1.8
    com.apple.iokit.IOUserEthernet    1.0.0d1
    com.apple.iokit.IOBluetoothSerialManager    4.0.5f11
    com.apple.driver.AppleMCEDriver    1.1.9
    com.apple.Dont_Steal_Mac_OS_X    7.0.0
    com.apple.driver.AudioIPCDriver    1.2.2
    com.apple.driver.ACPI_SMC_PlatformPlugin    5.0.0d0
    com.apple.driver.AppleLPC    1.5.8
    com.apple.driver.CSRUSBBluetoothHCIController    4.0.5f11
    com.apple.iokit.SCSITaskUserClient    3.2.0
    com.apple.driver.XsanFilter    404
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless    1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib    1.0.0d1
    com.apple.BootCache    33
    com.apple.iokit.IOAHCIBlockStorage    2.0.3
    com.apple.driver.AppleUSBOHCI    4.4.5
    com.apple.driver.AppleAHCIPort    2.3.0
    com.apple.driver.AppleIntelPIIXATA    2.5.1
    com.apple.driver.AppleUSBHub    4.5.0
    com.apple.driver.AppleIntel8254XEthernet    2.1.3b1
    com.apple.driver.AppleFWOHCI    4.8.9
    com.apple.driver.AppleUSBEHCI    4.5.8
    com.apple.driver.AppleUSBUHCI    4.4.5
    com.apple.driver.AppleEFINVRAM    1.5.0
    com.apple.driver.AppleACPIButtons    1.5
    com.apple.driver.AppleRTC    1.5
    com.apple.driver.AppleHPET    1.6
    com.apple.driver.AppleSMBIOS    1.8
    com.apple.driver.AppleACPIEC    1.5
    com.apple.driver.AppleAPIC    1.5
    com.apple.driver.AppleIntelCPUPowerManagementClient    193.0.0
    com.apple.nke.applicationfirewall    3.2.30
    com.apple.security.quarantine    1.3
    com.apple.driver.AppleIntelCPUPowerManagement    193.0.0
    com.apple.security.SecureRemotePassword    1.0
    com.apple.kext.triggers    1.0
    com.apple.driver.DspFuncLib    2.2.0f3
    com.apple.kext.ATI5000Controller    7.1.8
    com.apple.kext.ATISupport    7.1.8
    com.apple.iokit.IOSurface    80.0.2
    com.apple.iokit.IOSerialFamily    10.0.5
    com.apple.iokit.IOFireWireIP    2.2.4
    com.apple.iokit.IOAudioFamily    1.8.6fc17
    com.apple.kext.OSvKernDSPLib    1.3
    com.apple.driver.AppleHDAController    2.2.0f3
    com.apple.iokit.IOHDAFamily    2.2.0f3
    com.apple.driver.ApplePolicyControl    3.0.16
    com.apple.driver.AppleGraphicsControl    3.0.16
    com.apple.iokit.IONDRVSupport    2.3.2
    com.apple.iokit.IOGraphicsFamily    2.3.2
    com.apple.driver.AppleSMC    3.1.3d8
    com.apple.driver.IOPlatformPluginLegacy    5.0.0d0
    com.apple.driver.IOPlatformPluginFamily    5.1.0d17
    com.apple.driver.AppleUSBBluetoothHCIController    4.0.5f11
    com.apple.iokit.IOBluetoothFamily    4.0.5f11
    com.apple.driver.AppleUSBHIDKeyboard    160.7
    com.apple.driver.AppleHIDKeyboard    160.7
    com.apple.iokit.IOUSBHIDDriver    4.4.5
    com.apple.iokit.IOSCSIBlockCommandsDevice    3.2.0
    com.apple.iokit.IOUSBMassStorageClass    3.0.1
    com.apple.driver.AppleUSBMergeNub    4.5.3
    com.apple.driver.AppleUSBComposite    4.5.8
    com.apple.iokit.IOSCSIMultimediaCommandsDevice    3.2.0
    com.apple.iokit.IOBDStorageFamily    1.6
    com.apple.iokit.IODVDStorageFamily    1.7
    com.apple.iokit.IOCDStorageFamily    1.7
    com.apple.iokit.IOATAPIProtocolTransport    3.0.0
    com.apple.iokit.IOSCSIArchitectureModelFamily    3.2.0
    com.apple.iokit.IOAHCIFamily    2.0.8
    com.apple.iokit.IOATAFamily    2.5.1
    com.apple.iokit.IONetworkingFamily    2.1
    com.apple.iokit.IOUSBUserClient    4.5.8
    com.apple.iokit.IOFireWireFamily    4.4.5
    com.apple.iokit.IOUSBFamily    4.5.8
    com.apple.driver.AppleEFIRuntime    1.5.0
    com.apple.iokit.IOHIDFamily    1.7.1
    com.apple.iokit.IOSMBusFamily    1.1
    com.apple.security.sandbox    177.5
    com.apple.kext.AppleMatch    1.0.0d1
    com.apple.security.TMSafetyNet    7
    com.apple.driver.DiskImages    331.6
    com.apple.iokit.IOStorageFamily    1.7.1
    com.apple.driver.AppleKeyStore    28.18
    com.apple.driver.AppleACPIPlatform    1.5
    com.apple.iokit.IOPCIFamily    2.6.8
    com.apple.iokit.IOACPIFamily    1.4

    What might I find by running XP natively?  I won't get kernel panics under XP.  I haven't run it natively in many months.
    I thought that Parallels actually uses Paragon NTFS (or at least a variant of it) to read and write to the NTFS drives.  It's possible that I am mistaken, as many years have passed since I last looked at Paragon NTFS.
    Is the Paragon driver intended to replace the OS X default NTFS driver or Parallels?  I'm not sure how Parallels will respond to the Paragon driver.
    Parallels should be up-to-date.  It reports build 7.0.15094.
    Regarding Windows XP, this is the only system I have that is still running XP on Boot Camp.  I rarely use it these days, and wouldn't be now, if I wasn't trying to back it up using CrashPlan.  My plan is upgrade when I have time.  All my other systems have Windows 7 on the Boot Camp drives.
    I do have a few VMs that use XP, because I haven't had the chance to replace them with Windows 7 installs, and they are generally used for infrequent development tasks and for running Beyond Compare.  Also, I believe there may have been license issues with the version of Windows 7 that I'm own when used with VMs (meaning they're not allowed) ... but don't quote me on this.
    I noticed that Riser B/DIMM 1 and 2 do not report the Manufacturer.  I'm pretty sure the 2GB and 4GB DIMMs are OWC.  The 1GB DIMMs are OEM from Apple.
    Memory:
    Memory Slots:
      ECC:          Enabled
    DIMM Riser B/DIMM 1:
      Size:          2 GB
      Type:          DDR2 FB-DIMM
      Speed:          800 MHz
      Status:          OK
      Manufacturer:          0x0000
      Part Number:          0x000000463732353642363145353830304600
    DIMM Riser B/DIMM 2:
      Size:          2 GB
      Type:          DDR2 FB-DIMM
      Speed:          800 MHz
      Status:          OK
      Manufacturer:          0x0000
      Part Number:          0x000000463732353642363145353830304600
    DIMM Riser A/DIMM 1:
      Size:          4 GB
      Type:          DDR2 FB-DIMM
      Speed:          800 MHz
      Status:          OK
      Manufacturer:          0x80AD
      Part Number:          0x485900503132354637324350344E332D5336
    DIMM Riser A/DIMM 2:
      Size:          4 GB
      Type:          DDR2 FB-DIMM
      Speed:          800 MHz
      Status:          OK
      Manufacturer:          0x80AD
      Part Number:          0x485900503132354637324350344E332D5336
    DIMM Riser B/DIMM 3:
      Size:          Empty
      Type:          Empty
      Speed:          Empty
      Status:          Empty
      Manufacturer:          Empty
      Part Number:          Empty
    DIMM Riser B/DIMM 4:
      Size:          Empty
      Type:          Empty
      Speed:          Empty
      Status:          Empty
      Manufacturer:          Empty
      Part Number:          Empty
    DIMM Riser A/DIMM 3:
      Size:          1 GB
      Type:          DDR2 FB-DIMM
      Speed:          800 MHz
      Status:          OK
      Manufacturer:          0x80AD
      Part Number:          0x48594D5035313241373243503844332D5335
    DIMM Riser A/DIMM 4:
      Size:          1 GB
      Type:          DDR2 FB-DIMM
      Speed:          800 MHz
      Status:          OK
      Manufacturer:          0x80AD
      Part Number:          0x48594D5035313241373243503844332D5335

  • Kernel panics with iBook G4 and 10.3.9 (modem kext)

    Upon upgrading my iBook G4 to 10.3.9, I began recieving a rash of kernel panics (about 1-2 a day) . This was quite a change from the relatively solid machine I had previous ( about a panic a month with 10.3.8 with heavy daily use ). I initially suspected some ram failure but after extensive testing (bit flip, pattern, etc.) in single user mode eliminated that possibility.
    The panic log contiuously pointed at the MotorolaSM56K driver. I now suspected a kernel module/kernel incompatibility problem. After activating root and kextunloading that class I was able to regain some measure of stabilty ( about 4-5 days between crashes ). This stability varied as the class would be reloaded by OS under certain (unknown) conditions. As I have actually never used the built-in modem I have now decided to fully unload the AppleI2SModemFamily.kext extension, to avoid the SM56K class from starting.
    Have others noticed similar issues when upgrading from 10.3.8 to 10.3.9? or with the modem kext? I am suprised at the poor quality of this "upgrade", having used X since 10.1 on my ibook G3 (that I have now kept at 10.3.8)
    Is the modem kernel extension a red herring and its truly an issue in the kernel (that the modem extension exposes)?
    attached are some snippets from my (now very long) panic.log:
    Wed Nov 23 14:35:32 2005
    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000000000025C PC=0x000000000008D810
    Latest crash info for cpu 0:
    Exception state (sv=0x326E3280)
    PC=0x0008D810; MSR=0x00001030; DAR=0x0000025C; DSISR=0x40000000; LR=0x0001784C; R1=0x121EBC50; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x000177F4 0x00014774 0x000219F8 0x00040DC4 0x00016360 0x000189D4 0x0001C9E0 0x00027444
    0x00094318 0x0079003E
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.driver.MotorolaSM56K(1.3.1)@0x6ef000
    dependency: com.apple.driver.AppleI2SModemFamily(1.1.2)@0x6e4000
    dependency: com.apple.iokit.IOSerialFamily(6.0.1d20)@0x49d000
    Proceeding back via exception chain:
    Exception state (sv=0x326E3280)
    previously dumped as "Latest" state. skipping...
    Exception state (sv=0x259F4A00)
    PC=0x900106D8; MSR=0x0000F030; DAR=0x1C348004; DSISR=0x40000000; LR=0x901D9778; R1=0xBFFFEDB0; XCP=0x00000030 (0xC00 - System call)
    Kernel version:
    Darwin Kernel Version 7.9.0:
    Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC
    panic(cpu 0): 0x300 - Data access
    Latest stack backtrace for cpu 0:
    Backtrace:
    0x00083498 0x0008397C 0x0001EDA4 0x00090C38 0x0009402C
    Proceeding back via exception chain:
    Exception state (sv=0x326E3280)
    PC=0x0008D810; MSR=0x00001030; DAR=0x0000025C; DSISR=0x40000000; LR=0x0001784C; R1=0x121EBC50; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x000177F4 0x00014774 0x000219F8 0x00040DC4 0x00016360 0x000189D4 0x0001C9E0 0x00027444
    0x00094318 0x0079003E
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.driver.MotorolaSM56K(1.3.1)@0x6ef000
    dependency: com.apple.driver.AppleI2SModemFamily(1.1.2)@0x6e4000
    dependency: com.apple.iokit.IOSerialFamily(6.0.1d20)@0x49d000
    Exception state (sv=0x259F4A00)
    PC=0x900106D8; MSR=0x0000F030; DAR=0x1C348004; DSISR=0x40000000; LR=0x901D9778; R1=0xBFFFEDB0; XCP=0x00000030 (0xC00 - System call)
    Kernel version:
    Darwin Kernel Version 7.9.0:
    Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC
    Wed Nov 23 20:54:17 2005
    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000000000025C PC=0x000000000008D810
    Latest crash info for cpu 0:
    Exception state (sv=0x326E3280)
    PC=0x0008D810; MSR=0x00001030; DAR=0x0000025C; DSISR=0x40000000; LR=0x0001784C; R1=0x121EBC50; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x000177F4 0x00014774 0x000219F8 0x00040DC4 0x00016360 0x000189D4 0x0001C9E0 0x00027444
    0x00094318 0x0079003E
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.driver.MotorolaSM56K(1.3.1)@0x6ef000
    dependency: com.apple.driver.AppleI2SModemFamily(1.1.2)@0x6e4000
    dependency: com.apple.iokit.IOSerialFamily(6.0.1d20)@0x49d000
    Proceeding back via exception chain:
    Exception state (sv=0x326E3280)
    previously dumped as "Latest" state. skipping...
    Exception state (sv=0x259F4A00)
    PC=0x900106D8; MSR=0x0000F030; DAR=0x1C348004; DSISR=0x40000000; LR=0x901D9778; R1=0xBFFFEDB0; XCP=0x00000030 (0xC00 - System call)
    Kernel version:
    Darwin Kernel Version 7.9.0:
    Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC
    panic(cpu 0): 0x300 - Data access
    Latest stack backtrace for cpu 0:
    Backtrace:
    0x00083498 0x0008397C 0x0001EDA4 0x00090C38 0x0009402C
    Proceeding back via exception chain:
    Exception state (sv=0x326E3280)
    PC=0x0008D810; MSR=0x00001030; DAR=0x0000025C; DSISR=0x40000000; LR=0x0001784C; R1=0x121EBC50; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x000177F4 0x00014774 0x000219F8 0x00040DC4 0x00016360 0x000189D4 0x0001C9E0 0x00027444
    0x00094318 0x0079003E
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.driver.MotorolaSM56K(1.3.1)@0x6ef000
    dependency: com.apple.driver.AppleI2SModemFamily(1.1.2)@0x6e4000
    dependency: com.apple.iokit.IOSerialFamily(6.0.1d20)@0x49d000
    Exception state (sv=0x259F4A00)
    PC=0x900106D8; MSR=0x0000F030; DAR=0x1C348004; DSISR=0x40000000; LR=0x901D9778; R1=0xBFFFEDB0; XCP=0x00000030 (0xC00 - System call)
    Kernel version:
    Darwin Kernel Version 7.9.0:
    Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC
    iBook G4   Mac OS X (10.3.9)  

    A reasonable possibility is that you upgraded without
    first repairing the hard drive and permissions.
    Although this may not help after the fact, I suggest
    you give it a try:
    Boot from your OS X Installer. Be sure to use the
    installer for the version of OS X you have installed.
    After the installer loads select Disk Utility from
    the Installer menu (or Utilities menu if using
    Tiger.) After DU loads select your OS X volume from
    the list on the left, click on the First Aid tab,
    then click on the Repair Disk button. If DU reports
    any errors that have been fixed, then re-run Repair
    Disk until no errors are reported. If no errors are
    reported click on the Repair Permissions button. Wait
    until the operation completes, then quit DU and
    return to the installer. Now shutdown the computer
    for a couple of minutes and then restart normally.
    This I did yesterday and found a slew of permission setting problems - speaking to some endemic issues in the OS software/installation scripts. But after doing this repair (all were repairable) and reinstalling the COMBO update to 10.3.9 the problem persists. Thanks for the tip.
    Keep in mind that RAM can pass the memory tests yet
    not work properly with OS X. Therefore, you cannot
    assume that because the RAM passed the memory tests
    that it is fully functional with OS X. If you have
    installed third-party RAM, the only definitive test
    is to remove it and see if the kernel panics cease.
    If they do, then add one module at a time and
    re-test. When the panics recur you have identified
    the faulty module.
    Though I find disconcerting that Apple's POST routines are not sufficient to identify out of spec/incompatible RAM, I fully tested my memory (as mentioned) using memtest in single user mode. Memtest is a gnu program ported over from BSD unix that does exhaustive memory testing (ie the patterns, walking, etc that I mentioned)
    Of course it's also possible there is a hardware
    problem with the modem itself or that your upgrade to
    10.3.9 is defective. After repairing the hard drive
    and permissions you should reinstall the 10.3.9
    update, but be sure to do so using the Combo updater.
    You can download it from Apple's download site.
    How the modem hardware failure mysteriously coincided with my 10.3.9 upgrade begs the question on how could be anything but a software issue...

  • I just updated my RAM and I keep getting a crash report. I have a 21.5 Inch mid 2010 imac. I also am experiencing slow load times and when I try to open Final Cut it says that quartz extreme is not compatible and that I have no VRAM even though I do.

    I just updated my RAM (replaced the two 2 gig cards with two Corsair 8 gig cards) and I keep getting a crash report. I have a 21.5 Inch mid 2010 imac. I also am experiencing slow load times with Photoshop and when I try to open Final Cut it says that quartz extreme is not compatible and that I have no VRAM even though I do.
    Here is the crash report:
    Interval Since Last Panic Report:  5426204 sec
    Panics Since Last Report:          2
    Anonymous UUID:                    2DD57DDB-BB42-5614-395A-CA6225BDAFD9
    Wed Mar 20 11:36:53 2013
    panic(cpu 0 caller 0xffffff801aa43d8e): "a freed zone element has been modified in zone: maps"@/SourceCache/xnu/xnu-2050.18.24/osfmk/kern/zalloc.c:219
    Backtrace (CPU 0), Frame : Return Address
    0xffffff81eb0eb950 : 0xffffff801aa1d626
    0xffffff81eb0eb9c0 : 0xffffff801aa43d8e
    0xffffff81eb0eba00 : 0xffffff801aa435d2
    0xffffff81eb0ebae0 : 0xffffff801aa663f7
    0xffffff81eb0ebb20 : 0xffffff801aa67398
    0xffffff81eb0ebc70 : 0xffffff801aa6887c
    0xffffff81eb0ebd20 : 0xffffff801ad5b8fe
    0xffffff81eb0ebf50 : 0xffffff801ade182a
    0xffffff81eb0ebfb0 : 0xffffff801aaced33
    BSD process name corresponding to current thread: launchd
    Mac OS version:
    Not yet set
    Kernel version:
    Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
    Kernel UUID: 69A5853F-375A-3EF4-9247-478FD0247333
    Kernel slide:     0x000000001a800000
    Kernel text base: 0xffffff801aa00000
    System model name: iMac11,2 (Mac-F2238AC8)
    System uptime in nanoseconds: 1070542822
    last loaded kext at 707348380: com.apple.driver.AppleIRController    320.15 (addr 0xffffff7f9c53e000, size 28672)
    loaded kexts:
    at.obdev.nke.LittleSnitch    3908
    com.apple.driver.AppleIRController    320.15
    com.apple.driver.AppleUSBCardReader    3.1.0
    com.apple.driver.AppleFileSystemDriver    3.0.1
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless    1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib    1.0.0d1
    com.apple.BootCache    34
    com.apple.iokit.SCSITaskUserClient    3.5.1
    com.apple.driver.XsanFilter    404
    com.apple.iokit.IOAHCIBlockStorage    2.2.2
    com.apple.driver.AppleUSBHub    5.2.5
    com.apple.driver.AppleFWOHCI    4.9.6
    com.apple.driver.AirPort.Atheros40    600.70.23
    com.apple.driver.AppleUSBEHCI    5.4.0
    com.apple.driver.AppleAHCIPort    2.4.1
    com.apple.iokit.AppleBCM5701Ethernet    3.2.5b3
    com.apple.driver.AppleUSBUHCI    5.2.5
    com.apple.driver.AppleEFINVRAM    1.6.1
    com.apple.driver.AppleACPIButtons    1.6
    com.apple.driver.AppleRTC    1.5
    com.apple.driver.AppleHPET    1.7
    com.apple.driver.AppleSMBIOS    1.9
    com.apple.driver.AppleACPIEC    1.6
    com.apple.driver.AppleAPIC    1.6
    com.apple.driver.AppleIntelCPUPowerManagementClient    196.0.0
    com.apple.nke.applicationfirewall    4.0.39
    com.apple.security.quarantine    2
    com.apple.driver.AppleIntelCPUPowerManagement    196.0.0
    com.apple.iokit.IOUSBHIDDriver    5.2.5
    com.apple.iokit.IOSCSIBlockCommandsDevice    3.5.1
    com.apple.iokit.IOUSBMassStorageClass    3.5.0
    com.apple.driver.AppleUSBMergeNub    5.2.5
    com.apple.driver.AppleUSBComposite    5.2.5
    com.apple.iokit.IOSCSIMultimediaCommandsDevice    3.5.1
    com.apple.iokit.IOBDStorageFamily    1.7
    com.apple.iokit.IODVDStorageFamily    1.7.1
    com.apple.iokit.IOCDStorageFamily    1.7.1
    com.apple.iokit.IOAHCISerialATAPI    2.5.0
    com.apple.iokit.IOSCSIArchitectureModelFamily    3.5.1
    com.apple.iokit.IOUSBUserClient    5.2.5
    com.apple.iokit.IOFireWireFamily    4.5.5
    com.apple.iokit.IO80211Family    500.15
    com.apple.iokit.IOAHCIFamily    2.2.1
    com.apple.iokit.IOEthernetAVBController    1.0.2b1
    com.apple.iokit.IONetworkingFamily    3.0
    com.apple.iokit.IOUSBFamily    5.4.0
    com.apple.driver.AppleEFIRuntime    1.6.1
    com.apple.iokit.IOHIDFamily    1.8.0
    com.apple.iokit.IOSMBusFamily    1.1
    com.apple.security.sandbox    220
    com.apple.kext.AppleMatch    1.0.0d1
    com.apple.security.TMSafetyNet    7
    com.apple.driver.DiskImages    344
    com.apple.iokit.IOStorageFamily    1.8
    com.apple.driver.AppleKeyStore    28.21
    com.apple.driver.AppleACPIPlatform    1.6
    com.apple.iokit.IOPCIFamily    2.7.2
    com.apple.iokit.IOACPIFamily    1.4
    com.apple.kec.corecrypto    1.0
    Model: iMac11,2, BootROM IM112.0057.B00, 2 processors, Intel Core i3, 3.2 GHz, 16 GB, SMC 1.64f5
    Graphics: ATI Radeon HD 5670, ATI Radeon HD 5670, PCIe, 512 MB
    Memory Module: BANK 0/DIMM1, 8 GB, DDR3, 1333 MHz, 0x029E, 0x434D5341384758334D314131333333433920
    Memory Module: BANK 1/DIMM1, 8 GB, DDR3, 1333 MHz, 0x029E, 0x434D5341384758334D314131333333433920
    AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x8F), Atheros 9280: 4.0.70.23-P2P
    Bluetooth: Version 4.0.9f33 10885, 2 service, 18 devices, 0 incoming serial ports
    Network Service: AirPort, AirPort, en1
    Serial ATA Device: ST31000528AS, 1 TB
    Serial ATA Device: HL-DT-STDVDRW  GA32N
    USB Device: hub_device, 0x0424  (SMSC), 0x2514, 0xfd100000 / 2
    USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd120000 / 4
    USB Device: Built-in iSight, apple_vendor_id, 0x8502, 0xfd110000 / 3
    USB Device: hub_device, 0x0424  (SMSC), 0x2514, 0xfa100000 / 2
    USB Device: BRCM2046 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0xfa110000 / 4
    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8215, 0xfa111000 / 6
    USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0xfa120000 / 3

    There have been a few reports on here where Corsair RAM seems to have caused users a lot of grief with crashes.
    The recommendation on here, mostly, is to only buy RAM from macsales.com or crucial.com as they guarantee their modules will work and offer a no quibble lifetime guarantee.
    I'd put the original RAM back in, return the Corsair chips for a refund and re-order from one of those two companies.
    http://eshop.macsales.com/shop/apple/memory/iMac
    http://www.crucial.com/

  • 10.4.9, Quark 6.52, and an OpenType face = quark crash.

    I am on an iMac intel 2.0ghz dual core, with os 10.4.9, QuarkXPress 6.52, Extensis Fusion, and it's a weekly paper which I need to layout today! deadlines loom!
    After much troubleshooting over the last 18 hours and an install of a Markzware xtension, I have been able to find the source of a problem I've been having with opening a very particular Quark file which I desperately need to be able to open.
    I installed 10.4.9 last monday and didn't experience any issues until I restarted my system over the weekend. I would open the file, or similar versions, and get an unexpected quit in quark. So I turned off fusion. I had limited success with opening the file, but navigating it would crash it, and then I couldn't open them at all. I trashed my font database in suitcase, then quit using suitcase altogether. I loaded some necessary fonts in my User/Library/Fonts folder, doing it the older way. No success. Markzware's xtn was able to open a file without my stylesheets active, which gave me a starting point. After some more troubleshooting in to different versions I have over time of my weekly paper, I have been able to pinpoint that Quark is having an issue with ITC Franklin Gothic Medium.
    This is a font I purchased directly online a month ago, and I have tried reverting to the original font in my Fonts folder with no success. I Have this in multiple stylesheets in a third party program that tracks reporter's articles. I have to use this font. If I select it at all in the menu, or try a Find and Replace, or anything, it crashes Quark.
    I used this font and Fusion flawlessly for more than a month until the 10.4.9 release.
    If anyone has any input or ideas, please let me know. I think I can workaround it but it really needs to be resolved.
    This has been xposted in quarks forums. need info! This was not an issue until after 10.4.9.

    Looks like the panic is being caused by your Sophos kernel extension.
    Is the Sophos suite compatible with Mac OS X 10.4.9?
    I also assume you are being made to run Sophos due to work rules; since there are no known Mac OS X virii, running anti-virus software on the Mac almost always causes more problems than it solves.

  • I want Firefox to open to my homepage every time after it crashes. I do not want it to return to the tabs and applications that caused the crash. I am willing to lose information. How do I do this?

    Firefox crashes or seizes up when there are too many tabs and applications open, and causes my computer to crash or seize up. I use task manager to close Firefox or I restart my computer. Then, when Firefox restarts again, it automatically re-opens all the tabs and applications that caused the computer to seize or crash in first place. This is a waste of my time. I want Firefox to reopen to my homepage even if it crashes. I am willing to lose information to have Firefox reopen to a low-memory homepage. How do I do this?

    Set the Integer pref browser.sessionstore.max_resumed_crashes to 0 on the about:config page to get the about:sessionrestore page immediately with the first restart after a crash has occurred or the Task Manager was used to close Firefox.
    * http://kb.mozillazine.org/browser.sessionstore.max_resumed_crashes
    That will allow you to deselect the tab(s) that you do not want to reopen, but will allow to reopen other tabs.
    See:
    * http://kb.mozillazine.org/Session_Restore#Restoring_a_session_after_a_crash
    * http://kb.mozillazine.org/Browser.sessionstore.max_resumed_crashes
    See also:
    * https://wiki.mozilla.org/Session_Restore#Preferences
    To open the <i>about:config</i> page, type <b>about:config</b> in the location (address) bar and press the "<i>Enter</i>" key, just like you type the url of a website to open a website.<br />
    If you see a warning then you can confirm that you want to access that page.<br />
    *Use the Filter bar at to top of the about:config page to locate a preference more easily.
    *Preferences that have been modified show as bold (user set).
    *Preferences can be reset to the default via the right-click context menu if they are user set
    *Preferences can be changed via the right-click context menu: Modify (String or Integer) or Toggle (Boolean)

  • I have a macbook pro, and my hard disc currently crashed. I lost everything on my computer, but luckily I have an iPod nano with all my music saved on it. How can I now transfer my music from my ipod to my mac?

    I have a macbook pro, and the hard disc recently crashed. I lost everthing, but luckily i have my music saved on my ipod nano. How can I now transfer my music from my nano to my mac for free?

    Hi there ovadia!
    You can transfer the music purchased by your iTunes account from your iPod nano to your MacBook Pro by following the steps outlined in this article:
    iTunes Store: Transferring purchases from your iOS device or iPod to a computer
    http://support.apple.com/kb/HT1848
    Thanks for using the Apple Support Communities!
    Cheers,
    Braden

  • I am trying to add a footer and Adobe Pro XI keeps crashing

    I am trying to add a footer to my document and Adobe Pro XI keeps crashing.  Any ideas?

    What is your Acrobat XI version?  If less than 11.0.09 I suggest you update to that latest version.
    Note that you posted in the forum for Acrobat.com online services; you may get better help if you ask in the Acrobat forum.  You should also state your operating system.

  • HT3986 I have a pc that is one year old and the hard drive is crashing we use it only for quick books to run our small business I would like to buy amac and install the OS  forom the pc to the apple product i will not use the pc after can i use the OS off

    I have a pc that is one year old and the hard drive is crashing we use it only for quick books to run our small business I would like to buy a macmini and install the OS  from the pc to the apple product i will not use the pc after, can i use the OS off the pc or do I have to purchase another?

    I think you can get Windows 7 for around $99. Install the 64bit version as the 32bit version will not be able to use all your new computer's ram if you have more than about 3.5gb.
    Back up your quick books data now before the old hard drive dies. You can copy your data over to your new installation of Windows and quick books.
    By the way, there is quick books for Mac http://quickbooks.intuit.com/mac/?sc=BNR-000-COR-quickbooks&priorityCode=4902000 000&cid=ppc_google_QB-Intuit-Core-Brand-Mac_quick-books-for-mac_exact&site=&ad_i d=9347918288&raw_keyword=quick%20books%20for%20mac
    So you may not need to install Windows at all.

  • Why Do Both Photoshop CS5 (64 Bit) and Premiere Pro (64 Bit) Crash on Start up.

    Both Photoshop CS5 (64 Bit) and Premiere Pro (64 Bit) Crash on Start up. 32 bit version of Photoshop works fine.
    Here is the problem signature when they crash.
    Problem signature:
      Problem Event Name:          APPCRASH
      Application Name:          Photoshop.exe
      Application Version:          12.0.0.0
      Application Timestamp:          4bbc5b10
      Fault Module Name:          CoolType.dll
      Fault Module Version:          5.7.82.7602
      Fault Module Timestamp:          4b980c97
      Exception Code:          c0000005
      Exception Offset:          0000000000073a92
      OS Version:          6.1.7601.2.1.0.256.48
      Locale ID:          1033
      Additional Information 1:          7c82
      Additional Information 2:          7c821a1fc13b00b508d1bb6ee7ecaf44
      Additional Information 3:          019c
      Additional Information 4:          019cb6db15489631b8a43faf27e30830
    Problem signature:
      Problem Event Name:          APPCRASH
      Application Name:          Adobe Premiere Pro.exe
      Application Version:          5.0.3.0
      Application Timestamp:          4ce382d1
      Fault Module Name:          CoolType.dll
      Fault Module Version:          5.7.82.7449
      Fault Module Timestamp:          4b7b1af3
      Exception Code:          c0000005
      Exception Offset:          00000000000739ea
      OS Version:          6.1.7601.2.1.0.256.48
      Locale ID:          1033
      Additional Information 1:          889a
      Additional Information 2:          889afed61eb6ddf1c1c3419adc6026b6
      Additional Information 3:          8235
      Additional Information 4:          823549a371dff618695395cc0a8514ee
    Both are referencing cooltype.dll. I ran Font Doctor on all system and non-system fonts and found no errors. Booted without Extensis Suitcase loading. Nothing works. All 32 bit programs work fine. Any clues would be appreciated.

    It does not necessarily mean a "corrupt" font, but can be a font that PrPro, and PS, cannot handle.
    Though I have read that changes have been made, Open Office's DejaVu font would crash PrPro's Titler - every time. There are quite a few others. Font Dr, and similar utilities, will not see the font(s) as corrupt, but they are so poorly designed, that PrPro and PS cannot deal with them.
    Though it can be a long, drawn out process, one can often zero in on the problem font(s), with a little work. This is accomplished by first defining the "System Fonts," and not touching them. Then, uninstall half of the remaining fonts, and testing PrPro and PS. If they launch fine, you know that somewhere in that list of fonts, the problem exists. If there is still a failure to launch, chances are good that the problem font(s) reside in that half, that are still installed. Note: because the problem still exists, does not guarantee that there are NOT problem fonts in that uninstalled group, so keep that in mind.
    Repeat the proces, by uninstalling half of the remaining fonts and testing.
    If necessary, repeat by removing half of the now remaining fonts and testing.
    When you get to a point, where you are no longer getting problems, reinstall fonts, in small groups, testing in between. The smaller the groups, the easier it will be to pinpoint the problem font(s).
    Keep notes on which fonts you are uninstalling and reinstalling, until you narrow it down to the problem font(s).
    I would start by uninstalling any "free fonts," and then commercial, 3rd party fonts. A lot of free fonts are just poorly designed, and can cause issues, though they might work fine in some other programs.
    I use a font manager, so that I only have ~ 350 fonts installed at one time, and then dynamically install fonts, as needed for Projects. That keeps my machine clean, and if, upon installation, I get a crash/hang, I know that at least one font in that Set is causing it. This helps, as my workstation has ~ 19,000 fonts on it, and some are free fonts, and many are from 3rd parties. Some are also very, very old.
    Good luck,
    Hunt
    PS - one common cause for hangs on loading PrPro can be from VST's, used in Audio-editing. If you also have a lot of VST's, you could have two issues with two separate programs, i..e. PS hanging on fonts, and PrPro hanging on VST's. The results would be the same, but the causes could be different. That leads to even more work. For PrPro, also see this ARTICLE. If you get PS launching, but PrPro is still not functioning, drop by the PrPro Forum, and someone can help you there.

  • Every time I right click on an image and select Download image Firefox crashes . I have reinstalled; uninstalled and deleted folders and then reinstalled; added

    Every time I right click on an image and select Download image Firefox crashes . I have reinstalled; uninstalled and deleted folders and then reinstalled; added no plugins; checked I can DL the same images in IE-works good.I use Win7 pro and it works in other profiles in Windows 7. I created a new profile in Windows and that worked for about 2 months and now that has gone the same way as my admin profile has done. I deleted the sqlite download file-still same prob..Please help. I use Firefox 13.0.1

    That sounds very frustrating.
    By the way, does it say "Download image" or "Save Image As"? Just checking whether you have an add-on downloader in the mix that might be relevant. If you do have an add-on, try using the built-in command.
    Do you also crash if you save from here:
    right-click page > View Page Info > Media tab > (select image) > Save As
    I assume you have seen this article and tried these things: [[What to do if you can't download or save files]].
    Have you tried the new Reset feature in Firefox 13? This duplicates certain key data from your active settings folder into a new one, bypassing some add-ons and custom settings. Your plugins will still be active, but could be disabled manually if you like.
    More information in this article: [[Reset Firefox – easily fix most problems]].
    If the new settings folder has the same problem, you can switch back if you like using Firefox's Profile Manager.
    Does it make any difference?

  • Help apple help me, at first I was new to iphone registration 1 apple ID account but because I hardly use icloud account. so I do not remember the password and login name, my computer crash when I decided to run the software on ios7.1, but do not expect m

    help apple help me, at first I was new to iphone registration 1 apple ID account but because I hardly use icloud account. so I do not remember the password and login name, my computer crash when I decided to run the software on ios7.1, but do not expect me to be locked iclou account, I hope this mail unlocked apple for my apple account. I'm currently using the machine iphone 5, IME: ********. thank you ... ask yourself? machine is in warranty period warranty icloud error not send mail to me at mail
    <Personal Information Edited by Host>

    Contact iTunes Customer Service and request assistance
    Use this Link  >  Apple  Support  iTunes Store  Contact

  • Firefox crashes instantly on startup. i double-click on the icon and i instantly get a crash report asking to restart or quit. if i hit restart another crash report instantly comes up. im not sure what t do here

    firefox crashes instantly on startup. i double-click on the icon and i instantly get a crash report asking to restart or quit. if i hit restart another crash report instantly comes up. im not sure what t do here

    See:
    * http://kb.mozillazine.org/Firefox_crashes
    * https://support.mozilla.org/kb/Firefox+crashes

  • Is there any official market or store or anything in Egypt to fix my iphone 4 it jumped from 5th floor and the back hous was crashed and the network sensor was not working good but the phone and the screen and the others things are ok so plz help ???

    Is there any official market or store or anything in Egypt to fix my iphone 4 it jumped from 5th floor and the back hous was crashed and the network sensor was not working good but the phone and the screen and the others things are ok so plz help ???
    my iphone is now just coverd with case and the back house is crased

    Etisalat, Mobinil and Vodafone provide warranty service in your country.  You can also search Google for a 3rd party repair shop near you.

Maybe you are looking for

  • How to upload more than one file in struts?

    thanks first. I want to upload more than one file at once. So I modify the the example of the struts 1.1. I changed : protected FormFile theFile; to protected FormFile [] theFile; and add indexed getter and setter method. public FormFile getTheFileIn

  • Gantt drag and drop

    Hi. I'm trying to implement drag and drop in a dvt:schedulingGantt ADF component. I've managed to get it sort of working. I can click on a 'taskbar' and drag it to another 'resource'. But how can I get a reference to the Task that is being dragged? I

  • Photoshop CS4 & Lightroom 2.6 X64 funktionieren nicht mehr

    Hallo, bis vor einer Woche war alles OK - Photoshop & Lightroom funktionierte normal. Mein PC ist eine HP Workstation XW8200 mit Windows 7 X64. Alle anderen Anwendungen inkl. Adobe Anwendungen funktionieren normal. Eine Woche später lassen sich beide

  • How many states are there in a second?

    Hi I have to make an animation in fireworks and I am working in seconds. I can't work out how many states are there in a second. Please help. Thanks in advance.

  • Mobile Phone to PC via Bluetooth

    I am investigating the posibility for a certain function for an application on a mobile phone. An Single Sign-On (SSO) application. This application is going to transmit its authentication data to the PC and cause the Web browser to open and log in t