Update of 640 kernel files fails

Hi all,
I am experiencing a rather strange situation here. I am on Windows 2003 server and MSSQL, running SAP R/3 4.7x200. I am trying to update the kernel files from kernel patch 80 to 154. After I stop SAP and SAPOSCOL and SAP<SID>_00 services, I successfully replace the kernel files in ...\exe\run. I then start the services again and then SAP in SAPMMC. This is where the strange behaviour happends. I have done the exact same kernel upgrade in a sandbox system earlier without any problems. When I start SAPGUI and log in successfully, and check the kernel version, it is still patch 80, and not 154 as expected! I then return to \exe\run, and discover that the files I previously had overwritten are back to the old files! I have done this three times now, and I have checked every file that I overwrite that it has the correct size and date.
It is quite urgent that we get this kernel upgrade in place, as we are in the process of upgrading our systems.
Have anyone else experienced something like this? Please let me know if you can help!
Regards,
Thomas

Hi Srikishan,
I have done as you asked.
In the new kernel files directory the disp+work.exe -version gives me 154.
I then copy & paste the kernel files into \usr\sap\SID\SYS\exe\run. I then run dispwork.exe -version on the dispwork.exe in \usr\sap\SID\SYS\exe\run, and once again I get version 154.
When I restart the services and SAP in MMC, I get a funny message at first when looking at the process list. It says: sapcpe.exe Executable copy.
When I run dispwork.exe -version now on the dispwork.exe in \usr\sap\SID\SYS\exe\run I get the old kernel version, 80.
How can this be, and do you have any idea about what I have to do?
Should I restart the server after I have updated the kernel files, but before I start SAP, or can this cause problems?
Regards,
Thomas

Similar Messages

Updating Adobe Community Help files fails every time after starting

Hello,
I e.g. go to «Support Center for Photoshop» from the menu within the app. Adobe Community Help starts up and tells me theres new content, do I want to download that. It seems to start the dl just fine, then reports an error «16882» (if I'm remembering it right).
Why? We have very fast very broadband internet connection and I use a 2011 27" iMac with max Gig RAM installed.
Any hints there would be appreciated.
Thanks!

Thanks, Mister Kapoor,
that solved my problem!
All the best to you, sincerely,
Olaf Mueller
Mit freundlichen Grüssen,
Olaf Müller
COMPLOT AG Multimedia Project, Gerberngasse 44, Postfach, 3000 Bern 13
Tel. ++41 31.313 30 33
Fax ++41 31.313 30 39
[email protected]
http://www.complot.ch
THE ULTIMATE PARTNERS
- RITTER KREATIV
Unternehmensberatung+Kommunikation,
integrales Marketing, Werbung, Promotion, PR
- Complot AG Multimedia Project
Interactive Solutions, Internet, Intranet, E-Business, CD-ROM, DVD, Hosting
- FOTarena
Studio-Pool für Foto, Video, Bildbearbeitung
Am 24.04.2012 um 12:30 schrieb Arpit Kapoor:
Re: Updating Adobe Community Help files fails every time after starting
created by Arpit Kapoor in Downloading, Installing, Setting Up - View the full discussion
Seems Adobe Air or Cummunity help has gone cprrupt. Lets follow the below suggestions:
Step 1: Uninstall adobe air from Utilities and re-install the latest adobe AIR from "http://get.adobe.com/air/otherversions/"
Step 2: Follow "http://kb2.adobe.com/cps/842/cpsid_84215.html" and re-install the Community Help Air application.
Step 3: Restart the machine and launch adobe Community Help and try to install all the updates and check if it works fine.
Hope that Helps!.
Arpit
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4356729#4356729
To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4356729#4356729. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Downloading, Installing, Setting Up by email or at Adobe Forums
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

Adobe Photoshop CS5 Windows Finnish update files failed to install/load

Adobe Photoshop CS5 Windows Finnish update files failed to install/load.
Loading updates fails at the end of the loading. Tried it yesterday and today same errors. Are the files corrupted at server or how to fix this ?
Adobe Bridge CS5 4.0.5-update
Adobe Extension Manager CS5 5.0-update
Photoshop Camera Raw 6.7-update
Photoshop CS5:n Photoshop 12.0.4-update

update by downloading the files directly and then applying them:
pre cc updates: http://www.adobe.com/downloads/updates/

Update to 31.0 "stub" file and full install file fail to install Firefox. Removed Firefox and tried and it STILL does not install. Windows 7 OS

The 31.0 stub file failed to upgrade on my XP system but was able to overwrite with full install file. But the Windows 7 refuses to update or overwrite. It gets as far as extracting the files and then just stops.

Try this:
*Download the full Firefox installer and save the file to the desktop<br>http://www.mozilla.org/en-US/firefox/all.html
*Start the installation with a double-click on the desktop icon

New pc with windows 8.1, downloaded and installed cs5,no problem open bridge and cs5, but can't read raw file , try to update, can't complete or failed updating, please help

new pc with windows 8.1, downloaded and installed cs5,no problem open bridge and cs5, but can't read raw file , try to update, can't complete or failed updating, please help

Sounds like you somehow got the mac version.
Download the windows 6.7 camera raw update from this link:
Adobe - Photoshop : For Windows : Camera Raw 6.7 Update

Update of kernel: file in /etc/modprobe.d missing

That it's missing I know. I tried to apply a fix to the "Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after" by adding a file in /etc/modprobe.d according to some suggestions I found, but it didn't really fixing anything and hence I removed the file.
Now when updating the kernel it complains each time about that missing file and I can't find any information to why and based on what it still looks for that file. How do I fix this?
It doesn't affect the system as far as I can see, but the message is annoying and I prefer to clean this little mess up.

OK, let me show the output of pacman:
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.28-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
:: Begin dry run
:: Parsing hook [base]
ERROR: file '/etc/modprobe.d/usb-load-ehci-first' does not exist
:: Parsing hook [udev]
:: Parsing hook [autodetect]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [usbinput]
:: Parsing hook [keymap]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/kernel26.img'...SUCCESS
==> SUCCESS
As can be seen it still after I don't know how many updates look for a file I only once tested. So somewhere it's registered as needed parameter.
Last edited by KimTjik (2009-02-11 19:45:42)

"BIOS ME update....file not found " since a P67A-GD65 bios update failed

Hi everyone,
I've decided to post this little message after looking for a solution over the web and over the MSI forum because I've got a problem since the BIOS update of my P67A-GD65 MB.
I've followed the update process for the 4.32 BIOS using an USB key, the update started but did not continue after reboot, and since My PC is out of order
The "BIOS ME update....file not found " message is displayed after lots of booting tries, using plenty of methods.
I've looked and tried all the techniques I could find over the web, I've tried :
-PC with and without SATA drives connected
-the last 4 versions of the bios found on-line, even the original version of my MB before updating (1.19)
-4 different usb keys (from 128 Mb to 4 GB)
-all front and back usb ports
Each time, on each usb key, there were several bios versions, even one renamed to AMIBOOT.ROM for testing the recovery method.
I've also tried to make the keys bootable by using the “MSIHQ USB Bootable” tool with the 1.19 bios (after the boot fix), the usb key appears in the F11 boot menu but when I select it, the PC boots but still shows me the "BIOS ME update....file not found " message.
I've also tried a clear CMOS with several power off.
I've also tried to burn a CD containing only a AMIBOOT.ROM file, and to boot on it, but same problem occurs.
In brief, it seems that my PC does not recognize my Key's content, whatever it is.
I've you got an idea to help me ?
Last precision, the update process that failed was using the 4.3 bios version, but my CPU is a not an IvyBridge .
thanks for your help

HI
I've tried with your file , that's better but not solved
the "BIOS ME update....file not found" has gone but my bios is still inacessible.
I put the usb key (with the decompressed file) and the PC starts, displays the MSI boot logo, and then shows a message for hitting F1 or F2 bla bla bla...
Whatever the key that has been hit (F1 or F2, and only the first time), the pc boots again and again after displaying the boot logo, followed by a 30 seconds black screen.
If I remove the key, I've got a message that says I have to put a key on an usb port, and when I put back the usb key , the PC starts to boot again and again.
Once again , I'm stuck.
thanks for your help

Tried to updated to new ios 6.1 but the prep file failed in itunes...now my iphone4s is stuck on the screen to connect usb to itunes BUT nothhing happens when connected. HELP HELP

tried to updated to new ios 6.1 but the prep file failed in itunes...now my iphone4s is stuck on the screen to connect usb to itunes BUT nothing happens when connected. HELP HELP
I tired reboot the phone and placing the DFU BUT still the phone reverts back to itunes logo and ucb connection sceen

Place the device in DFU mode, connect to the computer and restore.

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)

DVD from previously prepared files - fails

I am trying to make a DVD of a project that I did in Sony Vegas Pro on my PC. I have made hundreds of DVD's on the PC by opening Nero and burning the AUDIO_TS and VIDEO_TS files to the DVD.
I have a week old MBP and am a Mac Newbie.
When I do this with XP to my Sony DVD burner, it usually takes about 15 minutes a disk for a 115 min project.
On the MBP, it took almost 2 hours to burn and over an hour to verify.
What is up with this? Surely I am doing something drastically wrong?
Why is it taking so long? The OS reported that the disk was burnable at 8x, should have taken 15 minutes like my PC does.
Please help!
Thanks,
Kirk

Hi Srikishan,
I have done as you asked.
In the new kernel files directory the disp+work.exe -version gives me 154.
I then copy & paste the kernel files into \usr\sap\SID\SYS\exe\run. I then run dispwork.exe -version on the dispwork.exe in \usr\sap\SID\SYS\exe\run, and once again I get version 154.
When I restart the services and SAP in MMC, I get a funny message at first when looking at the process list. It says: sapcpe.exe Executable copy.
When I run dispwork.exe -version now on the dispwork.exe in \usr\sap\SID\SYS\exe\run I get the old kernel version, 80.
How can this be, and do you have any idea about what I have to do?
Should I restart the server after I have updated the kernel files, but before I start SAP, or can this cause problems?
Regards,
Thomas

ITunes 9.2 update on windows 7 x64 failed What I did to fix it

Seems like everybody else had the same problems. In my case the upgrade originally failed with a 2324 error. It suggested trying again and if it continued that I should select tools download only. That is what I did. It will save the files to: C:\Users\YourUserName\AppData\Local\Apple\Apple Software Update .
The five files are:
AppleApplicationSupport
AppleMobileDeviceSupport64
Bonjour64
iTunes64
SetupAdmin
1. I started by running SetupAdmin.
2. Then I tried to install Bonjour64. Opps there is my 2324 error. So I clocked Start->Run->Services.msc In the list of services rightclick on Bonjour and select Stop Service. Then Click Start->Control Panel->Programs and Features Right Click on Bonjour and select uninstall. While here I decided to uninstall all of the other Apple programs (Don't forget Quicktime.)
Install Bonjour64
3. Install AppleApplicationSupport
4. Install AppleMobileDeviceSupport64
5. Install iTunes64
Opps there is the second error. Quicktime didn't install properly. Downloaded quicktime and installed it (don't do this). Ran qt and checked for upgrade. I have the latest available. Ran iTunes64 opps Quicktime didn't install properly.
***! Why is it even trying to reinstall qt if I have the latest?
6. Uninstall qt. Download iTunes 9.2+QT for x64
7. Install the download with no problems.
I then Disabled Bonjour since it causes problems on my system.
What I discovered. Bonjour is stealthed in. It should be an OPTION like safari. The Bonjour was not able to stop and uninstall the existing disabled Bonjour. Evidently the Quicktime player was also no able to be uninstalled by the upgrade. When manually uninstalled the upgrade could still not install qt.
The upgrade is not properly checking for installed versions. It forces an unneeded reinstall of qt.
The upgrade program is seriously broken and needs to be fixed.

Seems like everybody else had the same problems. In my case the upgrade originally failed with a 2324 error. It suggested trying again and if it continued that I should select tools download only. That is what I did. It will save the files to: C:\Users\YourUserName\AppData\Local\Apple\Apple Software Update .
The five files are:
AppleApplicationSupport
AppleMobileDeviceSupport64
Bonjour64
iTunes64
SetupAdmin
1. I started by running SetupAdmin.
2. Then I tried to install Bonjour64. Opps there is my 2324 error. So I clocked Start->Run->Services.msc In the list of services rightclick on Bonjour and select Stop Service. Then Click Start->Control Panel->Programs and Features Right Click on Bonjour and select uninstall. While here I decided to uninstall all of the other Apple programs (Don't forget Quicktime.)
Install Bonjour64
3. Install AppleApplicationSupport
4. Install AppleMobileDeviceSupport64
5. Install iTunes64
Opps there is the second error. Quicktime didn't install properly. Downloaded quicktime and installed it (don't do this). Ran qt and checked for upgrade. I have the latest available. Ran iTunes64 opps Quicktime didn't install properly.
***! Why is it even trying to reinstall qt if I have the latest?
6. Uninstall qt. Download iTunes 9.2+QT for x64
7. Install the download with no problems.
I then Disabled Bonjour since it causes problems on my system.
What I discovered. Bonjour is stealthed in. It should be an OPTION like safari. The Bonjour was not able to stop and uninstall the existing disabled Bonjour. Evidently the Quicktime player was also no able to be uninstalled by the upgrade. When manually uninstalled the upgrade could still not install qt.
The upgrade is not properly checking for installed versions. It forces an unneeded reinstall of qt.
The upgrade program is seriously broken and needs to be fixed.

Auto Update of Server.xml file

Hi
i'm running JDev 9i (9.0.2) with oc4j server (also 9.0.2).
I have one project containg Stateless Session bean (WizDecodeCodes)
I have also another project that calls this Bean. (From Servlet)
This works fine when you manually update the Parent attribute in the Server.XML file on OC4J after Every deployment.
Is there a way to configure Jdev to do dependancy updates like this when deploying?
Tks
andre

HI Curt
At this stage I have only got 1 JSP calling about 10 Servlets with only 2 of the Servlets calling the Single EJB that I have. Only started of with this.
Found that without the parent entry in the Server.XML file, the Servlet runs fine with the EJB from JDev but the moment you deploy to the same App Server it fails without the Parent entry.
I'm now starting on more advanced EJB's and it doesn't look that rosy if I look at this problem.
The other thing is that JDev always adds the last project deployed to the end of the Server.xml file, even if it was deployed before.
Thus making the sequence of deployement, update of Server.xml file in the correct sequence, etc a real nightmare when the applications grow.
Any suggestions on how to keep this up to date is welcome. We haven't got a Deployment guy so we have to do all this ourselves!
Cheers
Andre

Newbie help please: "Validation of XML file failed."

Hopefully my question is short and easy.
I'm a developer and haven't used FrameMaker before. However for unforeseen reasons, I've inherited our technical help documentation constructed in FrameMaker which I've never used. Unfortunately I'm under a very tight deadline and I'm attempting to update our already existing and fairly extensive application help files.
However, I'm getting a "Validation of XML file failed" error for 90% of our .xml help docs. I opened our .book file in FrameMaker fairly easily, and can see all of our .xml files. However the variables already embedded in the documents aren't being recognized and seem to be causing the above error. I've located our variable definition files (xml) in the concepts folder, but FrameMaker doesn't seem to recognize them. Any suggestions on what I can check or how I can get FM to refer to the variable definitions? I'm working with a new installation of FM, is there some setup I overlooked?
Many thanks,
dana.

Sheila and Rick,
Thank you both so much for your offer of help. My apologies for not replying earlier. Other 'emergencies' and priorities at work took me in other directions. It turns out another solution has been found for the time being. But thank you again for your replies. They say a lot about this community and its support. :)
Thanks again,
dana.

"file failed to be converted using Adobe ExportPDF online"

I have been getting errors for about a week when trying to convert a PDF to a word document. In Acrobat I get the error "File failed to be converted using Adobe ExportPDF Online" and when online using ExportPDF I get a conversion failure.
Please help.

Hi PeterChick,
Does it occur with all files or a specific file?
Are you trying to convert from within Reader or from Browser?
If from Reader then make sure you are signed in within Reader, also try updating Reader to the latest v11.0.09 and check.
If from Browser then have you checked with a different browser if possible?
Regards,
Florence

Having trouble using ExportPDf message file failed to be converted using Adobe ExportPDF online

need help
file failed to be converted using Adobe ExportPDF online

Hi PeterChick,
Does it occur with all files or a specific file?
Are you trying to convert from within Reader or from Browser?
If from Reader then make sure you are signed in within Reader, also try updating Reader to the latest v11.0.09 and check.
If from Browser then have you checked with a different browser if possible?
Regards,
Florence

Update of 640 kernel files fails

Similar Messages

Maybe you are looking for