System Hung frequently Generates Core file

Hi All,
One of my workstation is getting hung frequently when i kill that session it generates core file and the details are as follows.
Hardware : Sun Blade 2500
Memory: 2 GB
Operating System : Solaris 8 2/04
Patch Version : Generic_117350-12
I found following error in core file:
XtToolkitError.XtToolkitError
CancelDrag
typeConversionError.noConverter
typeConversionError.noConverter
files.so/usr/lib/locale/C/LC_CTYPE/textboundary.so.1
override
rter registered for 'Pixel' to 'SelectColor' conversion.
No type converter registered for 'Pixel' to 'SelectColor' conversion.
ListKbdCancel
Cp9{
override
No type converter registered for '%s' to '%s' conversion.
No type converter registered for '%s' to '%s' conversion.
Please help me to fix this issue.
Thanks & Regards,
Ramana

Hi,
These files are getting generated because your JVM is getting crashed frequently.
When JVM crash, JVM captures the state of the JVM at the time of crash and these files generate.
Please study your std_server log very carefully and you will find some lines like "Out of Memory" kind of error.
Now if you can stop the crash of the JVM, these files wont generate any more.
I have faced the same issue and Fix it using the following ways.
1)  Upgrade your JVM to the latest version so that better memory management will be in place.
2) If still these files getting generated, you can tune the new version of the JVM.
With Regards,
Saurabh

Similar Messages

  • Application running in Solaris 9 container generating core files. what to do?

    My solaris 9 zone configuration in solaris 10 looks like:
    zonecfg:sms> info
    zonename: sms
    zonepath: /zone/sms
    brand: solaris9
    autoboot: true
    bootargs:
    pool:
    limitpriv: default,proc_priocntl,proc_clock_highres,proc_lock_memory,sys_time,priv_proc_priocntl,priv_sys_time,net_rawaccess,sys_ipc_config,priv_proc_lock_memory
    scheduling-class:
    ip-type: exclusive
    hostid:
    [max-shm-memory: 4G]
    [max-shm-ids: 100]
    [max-sem-ids: 100]
    fs:
      dir: /var
      special: /dev/dsk/c1t0d0s5
      raw: /dev/rdsk/c1t0d0s5
      type: ufs
      options: []
    net:
      address not specified
      physical: bge0
      defrouter not specified
    device
      match: /dev/dsk/c1t0d0s5
    device
      match: /dev/rdsk/c1t0d0s5
    device
      match: /dev/dsk/c1t0d0s6
    device
      match: /dev/rdsk/c1t0d0s6
    device
      match: /dev/dsk/c1t0d0s7
    device
      match: /dev/rdsk/c1t0d0s7
    capped-cpu:
      [ncpus: 2.00]
    capped-memory:
      physical: 4G
      [swap: 8G]
      [locked: 2G]
    attr:
      name: hostid
      type: string
      value: 84b18f64
    attr:
      name: machine
      type: string
      value: sun4u
    rctl:
      name: zone.max-sem-ids
      value: (priv=privileged,limit=100,action=deny)
    rctl:
      name: zone.max-shm-ids
      value: (priv=privileged,limit=100,action=deny)
    rctl:
      name: zone.max-shm-memory
      value: (priv=privileged,limit=4294967296,action=deny)
    rctl:
      name: zone.max-swap
      value: (priv=privileged,limit=8589934592,action=deny)
    rctl:
      name: zone.max-locked-memory
      value: (priv=privileged,limit=2147483648,action=deny)
    rctl:
      name: zone.cpu-cap
      value: (priv=privileged,limit=200,action=deny)
    Solaris 9 zone /etc/system file looks like:
    * The directive below is not applicable in the virtualized environment.
    * The directive below is not applicable in the virtualized environment.
    * The directive below is not applicable in the virtualized environment.
    * The directive below is not applicable in the virtualized environment.
    * The directive below is not applicable in the virtualized environment.
    * The directive below is not applicable in the virtualized environment.
    set noexec_user_stack=1
    set semsys:seminfo_semmni=100
    set semsys:seminfo_semmns=1024
    set semsys:seminfo_semmsl=256
    set semsys:seminfo_semvmx=32767
    set shmsys:shminfo_shmmax=4294967295
    set shmsys:shminfo_shmmin=1
    set shmsys:shminfo_shmmni=100
    set shmsys:shminfo_shmseg=10
    set rlim_fd_max=65536
    set rlim_fd_cur=60000
    * The directive below is not applicable in the virtualized environment.
    My questions are:
    1. Application running in solaris 9 container generating core files. what to do???
    2. My prstat -Z for zone shows almost 95% percent cpu usage. what to do???
    3. Kindly can share how to move solaris 9 into solaris 10 containers ??

    Based on the new questions for the same post you wrote in the other communities, some posts are removed as duplicate, here is the answer :
    For the point #3, please look on table 17-1 in the following URL :
    Zone Components - System Administration Guide: Oracle Solaris Containers-Resource Management and Oracle Solaris Zones
    You can also customize your container /etc/system file but it cannot exceeds the global zone and the zone configuration value.
    For the other point, #2, this can be complicated without a complete image of what the complete system do.
    Try fist to check if you have not a busy process in your zone, then you can check if a bottleneck exists in the I/O side. You use maybe wrong parameters, a wrong configuration or your system configuration is insufficient in term of resources.
    What I can see in the outputs that you provided is that the S9 zone uses the half of the swap space. This can impact your zone performance and I/O activity, and can have in this case a side effect on some processes. Check why your zone uses the swap and how you can remedy this.

  • Solaris 10 update 6 keeps generating core file (/core)

    I wonder if somebody has encountered the following issue.
    I did a fresh install of Solaris 10 update 6 on two servers (T5140 and T524) from DVD.
    I noticed that a core file was in the root filesystem (/core).
    So, I deleted it.
    As soon as I delete the core file, another one is generated.
    This is happening on both servers where I installed Solaris 10 update 6 from the DVD.
    This is not a live update install. Solaris was installed from scratch. When prompted to preserve previous data, I replied with 'do not preserve data'
    Does anybody know where the core file is coming from and how to stop it being generated?
    Found out that is coming from vold
    SunOS b1osdtsun02 5.10 Generic_137137-09 sun4v sparc SUNW,T5240
    # more /etc/release
                          Solaris 10 10/08 s10s_u6wos_07b SPARC
               Copyright 2008 Sun Microsystems, Inc.  All Rights Reserved.
                            Use is subject to license terms.
                                Assembled 27 October 2008
    # mdb /core
    Loading modules: [ libsysevent.so.1 libnvpair.so.1 libc.so.1 ld.so.1 ]
    ::statusdebugging core file of vold (32-bit) from b1osdtsun02
    file: /usr/sbin/vold
    initial argv: /usr/sbin/vold -f /etc/vold.conf
    threading model: multi-threaded
    status: process terminated by SIGSEGV (Segmentation Fault)
    ::stacklibc.so.1`strlen+0x18(408450a5, 0, 0, 88b70, 600, 180)
    read_slices+0x114(874a0, b, 889a0, feeafd34, 1, 5)
    read_hsfs_partition+0x88(b, 46c00, 6d0000, 2c, 34400, 1010101)
    read_partition+0x30(874a0, 341a4, 3, 34000, 34400, 9)
    create_top_partition+0x140(7cbe0, 7cc24, 7cbe0, 874a0, ffffffff, b)
    0x265e0(800012, feeaff9c, c, 598e0, 7cbe0, ffffffff)
    create_medium+0x74(800012, feeaff9c, 20, 12, 47800, c)
    0x2232c(5d278, 0, 0, 800012, 20, 33000)
    libc.so.1`_lwp_start(0, 0, 0, 0, 0, 0)
    >
    #It seems that vold is failing to mount the DVD on both servers after Solaris was installed.
    Is this a Solaris 10 update 6 bug?
    Edited by: shen on Jan 29, 2009 8:45 PM

    Never mind.
    It is a known bug documented on manual " [Solaris 10 10/08 Release Notes, Chapter 2 Solaris Runtime Issues|http://docs.sun.com/app/docs/doc/820-5245/chapter2-1000?a=view] " as shown below.
    The solution is to apply vold patch [138130-01|http://sunsolve.sun.com/search/document.do?assetkey=1-21-138130-01-1].
    Solaris 10 10/08 DVD Media Might Not be Automatically Mounted by vold (6712352)
    The Solaris 10 10/08 DVD does not mount by default during runtime. No error message is displayed.
    Workaround: Perform the following steps:
       1. Become superuser.
       2. Disable vold:
          * On Solaris 10 Systems:
                # svcadm disable -t volfs
          * On Solaris 8 and Solaris 9 systems:
                /etc/init.d/volmgt stop
       3. Mount the media manually by using the # mount -F hsfs path to block device path to mount point command. For example:
          # mount -F hsfs /dev/rdsk/c0t2d0s2 /mnt

  • Frequently generating the core files /var/core in 11.5.10

    Hi,
    We have recently moved our production server from NETAPPS to EMC storage . After this we checked that lot of core files are generating by different modules like GL,AP etc...
    If someone has encountered the same issue, please let us know the reason.
    Regards,

    User;
    If my program is completed succesfully , eventhough core files are generating.
    Please let me know , reason of the core files , even the program are completed successfully.
    File-name like.
    core_<server name>GLPPOS504_501_1266506917_27175
    Did you check my previous post? Did you check Note:- Program Was Terminated By Signal 11 On GLLEZL After Applying Patch 11I.ATG_PF.H.DELTA.6 Doc Id: 580120.1 , did you try to Relink GLLEZL via adadmin and retest issue?
    Regard
    Helios

  • OMS generates tones of core files in OMS_HOME?

    Hi,
    We recently upgraded OMS to 10.2.0.4 and found that OMS has generated lot of core files where the file size is 0 bytes.Please let me know,what might could be the cause.
    Thanks,
    Regards,
    Vinoth

    Hi,
    Thanks for your response.
    File name format will be.
    core.3586
    core.3587
    core.35XX
    core.****
    Rest you can guess it.
    Thanks,
    Regards,
    Vinoth

  • Core file generating in tuxedo8.1

    Hi,
    we are using tuxedo8.1 and we are seeing core file getting generated and not able to identify the reason for the same.
    below are the details
    using debugger below is the output we got
    file core
    core: ELF-64 core file - IA64 from 'ck_CustomerUdt' - received SIGSEGV
    Core was generated by `ck_CustomerUdt'.
    warning: ck_CustomerUdt is 14 characters in length. Due to a limitation
    in the HP-UX kernel, core files contain only the first 14 characters
    of an executable's name. Check if ck_CustomerUdt is a truncated name.
    If it is so, core-file, packcore and other commands dealing with
    core files will exhibit incorrect behavior. To avoid this, issue
    exec-file and symbol-file commands with the full name of the executable
    that produced the core; then issue the core-file, packcore or other
    core file command of interest.
    Program terminated with signal 11, Segmentation fault.
    SEGV_MAPERR - Address not mapped to object
    warning: Load module /oraclehometux/oracle/product/10.2.0/db_1/lib/libclntsh.so.10.1 has been stripped.
    Debugging information is not available.
    warning: Load module /oraclehometux/oracle/product/10.2.0/db_1/lib/libnnz10.so has been stripped.
    Debugging information is not available.
    #0 0xc00000000866d1f0:0 in UDTProcess () at udt_Process.c:89
    89 udt_Process.c: No such file or directory.
    in udt_Process.c
    (gdb) bt
    #0 0xc00000000866d1f0:0 in UDTProcess () at udt_Process.c:89
    #1 0xc0000000214e33c0:0 in ck_CustomerUdtRequest () at udt.c:616
    #2 0x400000000000b800:0 in commonServiceWrapper () at ck_CustomerUdt.c:866
    #3 0x40000000000101e0:0 in I_CustomerUdtRequest () at ck_CustomerUdt.c:1285
    #4 0xc000000003c15020:0 in _tmsvcdsp () at tmsvcdsp.c:545
    #5 0xc000000003c66bb0:0 in _tmrunserver () at tmrunsvr.c:2015
    #6 0xc000000003c12a90:0 in _tmstartserver () at tmstrtsrvr.c:141
    #7 0x4000000000005240:0 in main () at BS-109a.c:76
    Current language: auto; currently c
    showing as udt_Process.c no such file.
    please help as we are facing this eery day. and every time core generating with same error

    Hi,
    Well from the call stack it looks like your server made a bad pointer reference on line 89 in file udt_Process.c. This really is unlikely to be a Tuxedo related issue. More likely just a coding error in the service.
    Regards,
    Todd Little
    Oracle Tuxedo Chief Architect

  • Generate IP core files from a xco file

    I have a .xco file and it is indicated to me that I need to generate other IP core files by running my .xco file.
    Q1. How is that done? 
    Q2. Do I need to use the Xilinx Core Generator to do this? Do I have to create a 'project' in Xilinx Core Generator?
    Thanks for the help

    Nevermind! I figured out how to do it. For anyone else out there that might have this problem...
    ->Create a new project in the XILINX CORE Generator
    ->Import your desired .xco file.
    ->Double click on the Instance Name of the IP
    ->Setup your IP as desired
    ->Click 'Generate'
    This should generate all of the needed files for you to use your IP block in EDK.
    This was for ISE 14.4

  • Lot of core files are generated in webserver machine.......

    we have a iplanet webserver running in our production environment........it is creating lot of entries in the file /var/adm/messages...............
    Aug 11 13:00:01 uk17 sendmail[1449]: [ID 702911 mail.warning] gethostbyaddr(192.168.245.62) failed: 1
    Aug 11 13:00:01 uk17 sendmail[1449]: [ID 702911 mail.warning] gethostbyaddr(192.168.245.64) failed: 1
    Aug 11 13:00:01 uk17 sendmail[1449]: [ID 702911 mail.warning] gethostbyaddr(192.168.245.84) failed: 1
    Aug 11 13:00:01 uk17 sendmail[1449]: [ID 702911 mail.warning] gethostbyaddr(192.168.245.88) failed: 1
    Aug 11 13:00:01 uk17 sendmail[1449]: [ID 702911 mail.warning] gethostbyaddr(192.168.245.90) failed: 1
    Aug 11 13:00:01 uk17 sendmail[1449]: [ID 702911 mail.warning] gethostbyaddr(192.168.245.92) failed: 1
    Aug 11 13:00:01 uk17 sendmail[1449]: [ID 702911 mail.warning] gethostbyaddr(192.168.245.94) failed: 1
    Aug 11 13:00:01 uk17 sendmail[1449]: [ID 702911 mail.warning] gethostbyaddr(192.168.245.106) failed: 1
    Aug 11 13:00:01 uk17 sendmail[1449]: [ID 702911 mail.warning] gethostbyaddr(192.168.245.108) failed: 1
    Aug 11 13:00:01 uk17 sendmail[1449]: [ID 702911 mail.warning] gethostbyaddr(192.168.245.110) failed: 1
    It is creating lot of core files in /var/core/ with the name.......
    ore.ns-httpd.14156.uk17.0.0.1218243851
    core.ns-httpd.14922.uk17.0.0.1217950925
    core.ns-httpd.14922.uk17.0.0.1217950926
    core.ns-httpd.14937.uk17.0.0.1218243696
    core.ns-httpd.14937.uk17.0.0.1218243697
    core.ns-httpd.14949.uk17.0.0.1218243760
    core.ns-httpd.14949.uk17.0.0.1218243762
    core.ns-httpd.14955.uk17.0.0.1218243765
    core.ns-httpd.14955.uk17.0.0.1218243767
    core.ns-httpd.14977.uk17.0.0.1218243777
    those files are in byte code so unable to read those file.............
    Please any one help me on this issue...............

    First migrate your server to the latest Web Server 7.0 update 3
    http://www.sun.com/software/products/web_srvr/index.xml
    https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=SJWS-7.0U3-OTH-G-F@CDS-CDS_SMI
    You are getting those messages as gethostbyaddr(192.168.245.92) is failing. Try writing a small C program which calls gethostbyaddr(192.168.245.92) and see if its an o/s issue.
    If you are on Solaris 10 try to see why Web Server is dumping core by
    mdb core.pid
    ::stackAre you sure you have patch levels as recommended in the release notes of Web Server?
    Have you enabled IPv6? Since when are you seeing these core dumps?

  • Illustrator CS4 - frequently generates corrupt EPS files that will not parse

    I have used many versions of Illustrator prior to and including the CS lines.  I am currently running CS4 and this is the first time I have experienced this issue.  Approximately half of my EPS formatted illustrator files will not parse.  I use Quark Xpress 7 for my layout (never liked any of the Indesign programs).  If I try to generate a PDF with my CS4 generated EPS files placed at least 60% of the time the placed file will corrupt the PDF export resulting in no PDF being generated. 
    Further to this PDF export issue, if I attempt to parse the same EPS file into Photoshop, Photoshop will give me the error message "Could not complete your request because Photoshop was unable to parse the PostScript" and it will abort the attempt to open the file.
    Anyone else having Illustrator EPS file issues?
    Background info (if needed) Dual 2.0 Ghz, PowerMac G5, 8 gb RAM, running Tiger 10.4.11
    I have attached a sample Illustrator file that will not Parse.  It will open in Illustrator but not parse into Photoshop or if placed in Quark will not parse and allow for a PDF to be exported.

    Thanks for taking the time to write Steve. 
    I understand that I can drag and drop between programs.  Ultimately, when attempting to parse an EPS in photoshop I am merely doing it to confirm that the EPS is indeed corrupt. 
    As mentioned previously, I predominately use Quark Xpress for my page layout program and until I installed CS4 I have had zero complications with using EPS files.  Now I quite commonly can not export PDFs due to corrupt EPS files. 
    My question to the public is I am alone in this glitch or do others experience the same issue.  My first thoughts are that CS4 has a glitch and I should be expecting an update in the near future.  But, if I am the only person suffering from this issue than maybe I should be looking at my own software.

  • OEM Grid generating too many core files

    Hi all,
    Database: Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production
    OEM (OMS and Agent): 10.2.0.5
    OS: Solaris 10 (SPARC 64bit)
    I have a weird problem concerning the agent, each an every time I start the agent, the cdump directory will be filled with hundreds of core files (66 MB each), thus feeling up the whole filesystem where the cdump directory resides. I'm not sure why this is happening. Is this a bug? Has anyone experienced this before?
    Thanks in advance for your help.
    Regards,
    Durbanite - South Africa

    Hi again,
    This is the content of the alert log:
    bash-3.00$ tail alert_clpr1.log
    ORA-07445: exception encountered: core dump [00000001002258A4] [SIGBUS] [Invalid address alignment] [0x60708090A0B0002] [] []
    Fri Jul 17 10:01:11 2009
    Errors in file /udd001/app/oracle/admin/clpr/udump/clpr1_ora_27740.trc:
    ORA-07445: exception encountered: core dump [00000001002258A4] [SIGBUS] [Invalid address alignment] [0x60708090A0B0002] [] []
    bash-3.00$ tail /udd001/app/oracle/admin/clpr/udump/clpr1_ora_27839.trc
    FD6C6EF9:00005D6A 265 0 10280 1 0x0000000000000109
    F3FED575:00005992 266 0 10280 1 0x000000000000010A
    FD6E1007:00005D6B 266 0 10280 1 0x000000000000010A
    F40260C6:00005994 267 0 10280 1 0x000000000000010B
    F40735E8:00005995 268 0 10280 1 0x000000000000010C
    F40C0992:00005997 269 0 10280 1 0x000000000000010D
    F40F9C50:00005999 270 0 10280 1 0x000000000000010E
    KSTDUMP: End of in-memory trace dump
    ssexhd: crashing the process...
    Shadow_Core_Dump = PARTIAL
    I think I might need to contact Oracle Supprt for this one, I'll start by using the ORA-07445 tool on metalink.
    Thanks and regards,
    Durbanited

  • System hungs up after an upgrade (because of the virtualbox ?)

    I just update my system's virtualbox to the newest version.
    After the upgrade I found my system hungs up after an random period of running...
    anybody knows what happened ?
    Last edited by Hacksign (2013-10-23 02:31:17)

    jasonwryan wrote:
    Your system in Virtualbox, ie., a virtual machine? Or your actual (host) system?
    Logs are accessed via journalctl or, for the packages you upgraded, /var/log/pacman.
    It's my actual system.
    The actual system hung up ... no any response.
    and I guess, it is because the virtualbox, because it is ok when there is no virtual machine running ...
    here is the log of last time, which is generated by this command "journalctl --since=today | tac | sed -n '/-- Reboot --/{n;:r;/-- Reboot --/q;p;n;b r}' | tac"
    (I didn't find any thing valueable )
    -- Logs begin at 三 2013-02-06 10:14:14 CST, end at 三 2013-10-23 10:49:52 CST. --
    10月 23 09:19:05 XSign systemd-journal[105]: Runtime journal is using 636.0K (max 176.5M, leaving 264.8M of free 1.7G, current limit 176.5M).
    10月 23 09:19:05 XSign systemd-journal[105]: Runtime journal is using 640.0K (max 176.5M, leaving 264.8M of free 1.7G, current limit 176.5M).
    10月 23 09:19:05 XSign kernel: Initializing cgroup subsys cpuset
    10月 23 09:19:05 XSign kernel: Initializing cgroup subsys cpu
    10月 23 09:19:05 XSign kernel: Initializing cgroup subsys cpuacct
    10月 23 09:19:05 XSign kernel: Linux version 3.11.6-1-ARCH (nobody@var-lib-archbuild-extra-i686-thomas) (gcc version 4.8.1 20130725 (prerelease) (GCC) ) #1 SMP PREEMPT Sat Oct 19 00:29:46 CEST 2013
    10月 23 09:19:05 XSign kernel: e820: BIOS-provided physical RAM map:
    10月 23 09:19:05 XSign kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
    10月 23 09:19:05 XSign kernel: BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
    10月 23 09:19:05 XSign kernel: BIOS-e820: [mem 0x00000000000e4000-0x00000000000fffff] reserved
    10月 23 09:19:05 XSign kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000df68ffff] usable
    10月 23 09:19:05 XSign kernel: BIOS-e820: [mem 0x00000000df690000-0x00000000df69dfff] ACPI data
    10月 23 09:19:05 XSign kernel: BIOS-e820: [mem 0x00000000df69e000-0x00000000df6cffff] ACPI NVS
    10月 23 09:19:05 XSign kernel: BIOS-e820: [mem 0x00000000df6d0000-0x00000000df6ddfff] reserved
    10月 23 09:19:05 XSign kernel: BIOS-e820: [mem 0x00000000df6e0000-0x00000000df6fffff] reserved
    10月 23 09:19:05 XSign kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
    10月 23 09:19:05 XSign kernel: BIOS-e820: [mem 0x00000000fff00000-0x00000000ffffffff] reserved
    10月 23 09:19:05 XSign kernel: BIOS-e820: [mem 0x0000000100000000-0x000000011fffffff] usable
    10月 23 09:19:05 XSign kernel: Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
    10月 23 09:19:05 XSign kernel: SMBIOS 2.5 present.
    10月 23 09:19:05 XSign kernel: DMI: System manufacturer System Product Name/P5KPL-AM SE, BIOS 0311 10/30/2008
    10月 23 09:19:05 XSign kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    10月 23 09:19:05 XSign kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    10月 23 09:19:05 XSign kernel: e820: last_pfn = 0xdf690 max_arch_pfn = 0x100000
    10月 23 09:19:05 XSign kernel: MTRR default type: uncachable
    10月 23 09:19:05 XSign kernel: MTRR fixed ranges enabled:
    10月 23 09:19:05 XSign kernel: 00000-9FFFF write-back
    10月 23 09:19:05 XSign kernel: A0000-BFFFF uncachable
    10月 23 09:19:05 XSign kernel: C0000-DFFFF write-protect
    10月 23 09:19:05 XSign kernel: E0000-EFFFF write-through
    10月 23 09:19:05 XSign kernel: F0000-FFFFF write-protect
    10月 23 09:19:05 XSign kernel: MTRR variable ranges enabled:
    10月 23 09:19:05 XSign kernel: 0 base 0E0000000 mask FE0000000 uncachable
    10月 23 09:19:05 XSign kernel: 1 base 000000000 mask F00000000 write-back
    10月 23 09:19:05 XSign kernel: 2 base 100000000 mask FE0000000 write-back
    10月 23 09:19:05 XSign kernel: 3 base 0DF700000 mask FFFF00000 uncachable
    10月 23 09:19:05 XSign kernel: 4 base 0DF800000 mask FFF800000 uncachable
    10月 23 09:19:05 XSign kernel: 5 disabled
    10月 23 09:19:05 XSign kernel: 6 disabled
    10月 23 09:19:05 XSign kernel: 7 disabled
    10月 23 09:19:05 XSign kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    10月 23 09:19:05 XSign kernel: e820: update [mem 0xdf700000-0xffffffff] usable ==> reserved
    10月 23 09:19:05 XSign kernel: found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [c00ff780]
    10月 23 09:19:05 XSign kernel: Scanning 1 areas for low memory corruption
    10月 23 09:19:05 XSign kernel: initial memory mapped: [mem 0x00000000-0x00bfffff]
    10月 23 09:19:05 XSign kernel: Base memory trampoline at [c009b000] 9b000 size 16384
    10月 23 09:19:05 XSign kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
    10月 23 09:19:05 XSign kernel: [mem 0x00000000-0x000fffff] page 4k
    10月 23 09:19:05 XSign kernel: init_memory_mapping: [mem 0x37000000-0x373fffff]
    10月 23 09:19:05 XSign kernel: [mem 0x37000000-0x373fffff] page 2M
    10月 23 09:19:05 XSign kernel: init_memory_mapping: [mem 0x30000000-0x36ffffff]
    10月 23 09:19:05 XSign kernel: [mem 0x30000000-0x36ffffff] page 2M
    10月 23 09:19:05 XSign kernel: init_memory_mapping: [mem 0x00100000-0x2fffffff]
    10月 23 09:19:05 XSign kernel: [mem 0x00100000-0x003fffff] page 4k
    10月 23 09:19:05 XSign kernel: [mem 0x00400000-0x2fffffff] page 2M
    10月 23 09:19:05 XSign kernel: init_memory_mapping: [mem 0x37400000-0x377fdfff]
    10月 23 09:19:05 XSign kernel: [mem 0x37400000-0x377fdfff] page 4k
    10月 23 09:19:05 XSign kernel: BRK [0x00877000, 0x00877fff] PGTABLE
    10月 23 09:19:05 XSign kernel: RAMDISK: [mem 0x7fd60000-0x7ffeffff]
    10月 23 09:19:05 XSign kernel: Allocated new RAMDISK: [mem 0x3756e000-0x377fdf01]
    10月 23 09:19:05 XSign kernel: Move RAMDISK from [mem 0x7fd60000-0x7ffeff01] to [mem 0x3756e000-0x377fdf01]
    10月 23 09:19:05 XSign kernel: ACPI: RSDP 000fbf00 00014 (v00 ACPIAM)
    10月 23 09:19:05 XSign kernel: ACPI: RSDT df690000 0003C (v01 A_M_I_ OEMRSDT 10000830 MSFT 00000097)
    10月 23 09:19:05 XSign kernel: ACPI: FACP df690200 00084 (v02 A_M_I_ OEMFACP 10000830 MSFT 00000097)
    10月 23 09:19:05 XSign kernel: ACPI: DSDT df6905c0 077A2 (v01 A1126 A1126000 00000000 INTL 20051117)
    10月 23 09:19:05 XSign kernel: ACPI: FACS df69e000 00040
    10月 23 09:19:05 XSign kernel: ACPI: APIC df690390 0006C (v01 A_M_I_ OEMAPIC 10000830 MSFT 00000097)
    10月 23 09:19:05 XSign kernel: ACPI: MCFG df690400 0003C (v01 A_M_I_ OEMMCFG 10000830 MSFT 00000097)
    10月 23 09:19:05 XSign kernel: ACPI: OEMB df69e040 00080 (v01 A_M_I_ AMI_OEM 10000830 MSFT 00000097)
    10月 23 09:19:05 XSign kernel: ACPI: HPET df697d70 00038 (v01 A_M_I_ OEMHPET 10000830 MSFT 00000097)
    10月 23 09:19:05 XSign kernel: ACPI: GSCI df69e0c0 02024 (v01 A_M_I_ GMCHSCI 10000830 MSFT 00000097)
    10月 23 09:19:05 XSign kernel: ACPI: Local APIC address 0xfee00000
    10月 23 09:19:05 XSign kernel: 2686MB HIGHMEM available.
    10月 23 09:19:05 XSign kernel: 887MB LOWMEM available.
    10月 23 09:19:05 XSign kernel: mapped low ram: 0 - 377fe000
    10月 23 09:19:05 XSign kernel: low ram: 0 - 377fe000
    10月 23 09:19:05 XSign kernel: BRK [0x00878000, 0x00878fff] PGTABLE
    10月 23 09:19:05 XSign kernel: Zone ranges:
    10月 23 09:19:05 XSign kernel: DMA [mem 0x00001000-0x00ffffff]
    10月 23 09:19:05 XSign kernel: Normal [mem 0x01000000-0x377fdfff]
    10月 23 09:19:05 XSign kernel: HighMem [mem 0x377fe000-0xdf68ffff]
    10月 23 09:19:05 XSign kernel: Movable zone start for each node
    10月 23 09:19:05 XSign kernel: Early memory node ranges
    10月 23 09:19:05 XSign kernel: node 0: [mem 0x00001000-0x0009efff]
    10月 23 09:19:05 XSign kernel: node 0: [mem 0x00100000-0xdf68ffff]
    10月 23 09:19:05 XSign kernel: On node 0 totalpages: 914990
    10月 23 09:19:05 XSign kernel: free_area_init_node: node 0, pgdat c06d7740, node_mem_map f597e020
    10月 23 09:19:05 XSign kernel: DMA zone: 32 pages used for memmap
    10月 23 09:19:05 XSign kernel: DMA zone: 0 pages reserved
    10月 23 09:19:05 XSign kernel: DMA zone: 3998 pages, LIFO batch:0
    10月 23 09:19:05 XSign kernel: Normal zone: 1744 pages used for memmap
    10月 23 09:19:05 XSign kernel: Normal zone: 223230 pages, LIFO batch:31
    10月 23 09:19:05 XSign kernel: HighMem zone: 5374 pages used for memmap
    10月 23 09:19:05 XSign kernel: HighMem zone: 687762 pages, LIFO batch:31
    10月 23 09:19:05 XSign kernel: Using APIC driver default
    10月 23 09:19:05 XSign kernel: ACPI: PM-Timer IO Port: 0x808
    10月 23 09:19:05 XSign kernel: ACPI: Local APIC address 0xfee00000
    10月 23 09:19:05 XSign kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    10月 23 09:19:05 XSign kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
    10月 23 09:19:05 XSign kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled)
    10月 23 09:19:05 XSign kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled)
    10月 23 09:19:05 XSign kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
    10月 23 09:19:05 XSign kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
    10月 23 09:19:05 XSign kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    10月 23 09:19:05 XSign kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    10月 23 09:19:05 XSign kernel: ACPI: IRQ0 used by override.
    10月 23 09:19:05 XSign kernel: ACPI: IRQ2 used by override.
    10月 23 09:19:05 XSign kernel: ACPI: IRQ9 used by override.
    10月 23 09:19:05 XSign kernel: Using ACPI (MADT) for SMP configuration information
    10月 23 09:19:05 XSign kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000
    10月 23 09:19:05 XSign kernel: smpboot: Allowing 4 CPUs, 2 hotplug CPUs
    10月 23 09:19:05 XSign kernel: nr_irqs_gsi: 40
    10月 23 09:19:05 XSign kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
    10月 23 09:19:05 XSign kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000e3fff]
    10月 23 09:19:05 XSign kernel: PM: Registered nosave memory: [mem 0x000e4000-0x000fffff]
    10月 23 09:19:05 XSign kernel: e820: [mem 0xdf700000-0xfedfffff] available for PCI devices
    10月 23 09:19:05 XSign kernel: Booting paravirtualized kernel on bare hardware
    10月 23 09:19:05 XSign kernel: setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:4 nr_node_ids:1
    10月 23 09:19:05 XSign kernel: PERCPU: Embedded 14 pages/cpu @f5934000 s33536 r0 d23808 u57344
    10月 23 09:19:05 XSign kernel: pcpu-alloc: s33536 r0 d23808 u57344 alloc=14*4096
    10月 23 09:19:05 XSign kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
    10月 23 09:19:05 XSign kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 913214
    10月 23 09:19:05 XSign kernel: Kernel command line: root=/dev/sda2 ro init=/usr/lib/systemd/systemd
    10月 23 09:19:05 XSign kernel: PID hash table entries: 4096 (order: 2, 16384 bytes)
    10月 23 09:19:05 XSign kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
    10月 23 09:19:05 XSign kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
    10月 23 09:19:05 XSign kernel: Initializing CPU#0
    10月 23 09:19:05 XSign kernel: allocated 7320696 bytes of page_cgroup
    10月 23 09:19:05 XSign kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
    10月 23 09:19:05 XSign kernel: Initializing HighMem for node 0 (000377fe:000df690)
    10月 23 09:19:05 XSign kernel: Memory: 3612756K/3659960K available (4262K kernel code, 426K rwdata, 1356K rodata, 608K init, 948K bss, 47204K reserved, 2751048K highmem)
    10月 23 09:19:05 XSign kernel: virtual kernel memory layout:
    fixmap : 0xfff15000 - 0xfffff000 ( 936 kB)
    pkmap : 0xff800000 - 0xffc00000 (4096 kB)
    vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB)
    lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB)
    .init : 0xc06e9000 - 0xc0781000 ( 608 kB)
    .data : 0xc0529d5e - 0xc06e8a00 (1787 kB)
    .text : 0xc0100000 - 0xc0529d5e (4263 kB)
    10月 23 09:19:05 XSign kernel: Checking if this processor honours the WP bit even in supervisor mode...Ok.
    10月 23 09:19:05 XSign kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
    10月 23 09:19:05 XSign kernel: Preemptible hierarchical RCU implementation.
    10月 23 09:19:05 XSign kernel: RCU dyntick-idle grace-period acceleration is enabled.
    10月 23 09:19:05 XSign kernel: Dump stacks of tasks blocking RCU-preempt GP.
    10月 23 09:19:05 XSign kernel: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
    10月 23 09:19:05 XSign kernel: NR_IRQS:2304 nr_irqs:712 16
    10月 23 09:19:05 XSign kernel: CPU 0 irqstacks, hard=f4c08000 soft=f4c0a000
    10月 23 09:19:05 XSign kernel: Console: colour VGA+ 80x25
    10月 23 09:19:05 XSign kernel: console [tty0] enabled
    10月 23 09:19:05 XSign kernel: hpet clockevent registered
    10月 23 09:19:05 XSign kernel: tsc: Fast TSC calibration using PIT
    10月 23 09:19:05 XSign kernel: tsc: Detected 3010.099 MHz processor
    10月 23 09:19:05 XSign kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6022.03 BogoMIPS (lpj=10033663)
    10月 23 09:19:05 XSign kernel: pid_max: default: 32768 minimum: 301
    10月 23 09:19:05 XSign kernel: Security Framework initialized
    10月 23 09:19:05 XSign kernel: AppArmor: AppArmor disabled by boot time parameter
    10月 23 09:19:05 XSign kernel: Yama: becoming mindful.
    10月 23 09:19:05 XSign kernel: Mount-cache hash table entries: 512
    10月 23 09:19:05 XSign kernel: Initializing cgroup subsys memory
    10月 23 09:19:05 XSign kernel: Initializing cgroup subsys devices
    10月 23 09:19:05 XSign kernel: Initializing cgroup subsys freezer
    10月 23 09:19:05 XSign kernel: Initializing cgroup subsys net_cls
    10月 23 09:19:05 XSign kernel: Initializing cgroup subsys blkio
    10月 23 09:19:05 XSign kernel: CPU: Physical Processor ID: 0
    10月 23 09:19:05 XSign kernel: CPU: Processor Core ID: 0
    10月 23 09:19:05 XSign kernel: mce: CPU supports 6 MCE banks
    10月 23 09:19:05 XSign kernel: CPU0: Thermal monitoring enabled (TM2)
    10月 23 09:19:05 XSign 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
    10月 23 09:19:05 XSign kernel: Freeing SMP alternatives memory: 20K (c0781000 - c0786000)
    10月 23 09:19:05 XSign kernel: ACPI: Core revision 20130517
    10月 23 09:19:05 XSign kernel: ACPI: All ACPI Tables successfully acquired
    10月 23 09:19:05 XSign kernel: ftrace: allocating 19099 entries in 38 pages
    10月 23 09:19:05 XSign kernel: Enabling APIC mode: Flat. Using 1 I/O APICs
    10月 23 09:19:05 XSign kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    10月 23 09:19:05 XSign kernel: smpboot: CPU0: Intel(R) Core(TM)2 Duo CPU E6850 @ 3.00GHz (fam: 06, model: 0f, stepping: 0b)
    10月 23 09:19:05 XSign kernel: APIC calibration not consistent with PM-Timer: 139ms instead of 100ms
    10月 23 09:19:05 XSign kernel: APIC delta adjusted to PM-Timer: 2090297 (2926401)
    10月 23 09:19:05 XSign kernel: Performance Events: PEBS fmt0+, 4-deep LBR, Core2 events, Intel PMU driver.
    10月 23 09:19:05 XSign kernel: perf_event_intel: PEBS disabled due to CPU errata
    10月 23 09:19:05 XSign kernel: ... version: 2
    10月 23 09:19:05 XSign kernel: ... bit width: 40
    10月 23 09:19:05 XSign kernel: ... generic registers: 2
    10月 23 09:19:05 XSign kernel: ... value mask: 000000ffffffffff
    10月 23 09:19:05 XSign kernel: ... max period: 000000007fffffff
    10月 23 09:19:05 XSign kernel: ... fixed-purpose events: 3
    10月 23 09:19:05 XSign kernel: ... event mask: 0000000700000003
    10月 23 09:19:05 XSign kernel: CPU 1 irqstacks, hard=f4cce000 soft=f4cd8000
    10月 23 09:19:05 XSign kernel: Initializing CPU#1
    10月 23 09:19:05 XSign kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    10月 23 09:19:05 XSign kernel: smpboot: Booting Node 0, Processors #1
    10月 23 09:19:05 XSign kernel: Brought up 2 CPUs
    10月 23 09:19:05 XSign kernel: smpboot: Total of 2 processors activated (12045.07 BogoMIPS)
    10月 23 09:19:05 XSign kernel: devtmpfs: initialized
    10月 23 09:19:05 XSign kernel: PM: Registering ACPI NVS region [mem 0xdf69e000-0xdf6cffff] (204800 bytes)
    10月 23 09:19:05 XSign kernel: RTC time: 9:19:01, date: 10/23/13
    10月 23 09:19:05 XSign kernel: NET: Registered protocol family 16
    10月 23 09:19:05 XSign kernel: ACPI: bus type PCI registered
    10月 23 09:19:05 XSign kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
    10月 23 09:19:05 XSign kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf0000000-0xf3ffffff] (base 0xf0000000)
    10月 23 09:19:05 XSign kernel: PCI: not using MMCONFIG
    10月 23 09:19:05 XSign kernel: PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=3
    10月 23 09:19:05 XSign kernel: PCI: Using configuration type 1 for base access
    10月 23 09:19:05 XSign kernel: bio: create slab <bio-0> at 0
    10月 23 09:19:05 XSign kernel: ACPI: Added _OSI(Module Device)
    10月 23 09:19:05 XSign kernel: ACPI: Added _OSI(Processor Device)
    10月 23 09:19:05 XSign kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
    10月 23 09:19:05 XSign kernel: ACPI: Added _OSI(Processor Aggregator Device)
    10月 23 09:19:05 XSign kernel: ACPI: EC: Look up EC in DSDT
    10月 23 09:19:05 XSign kernel: ACPI: Executed 1 blocks of module-level executable AML code
    10月 23 09:19:05 XSign kernel: ACPI: SSDT df6a00f0 001D2 (v01 AMI CPU1PM 00000001 INTL 20060113)
    10月 23 09:19:05 XSign kernel: ACPI: Dynamic OEM Table Load:
    10月 23 09:19:05 XSign kernel: ACPI: SSDT (null) 001D2 (v01 AMI CPU1PM 00000001 INTL 20060113)
    10月 23 09:19:05 XSign kernel: ACPI: SSDT df6a02d0 00143 (v01 AMI CPU2PM 00000001 INTL 20060113)
    10月 23 09:19:05 XSign kernel: ACPI: Dynamic OEM Table Load:
    10月 23 09:19:05 XSign kernel: ACPI: SSDT (null) 00143 (v01 AMI CPU2PM 00000001 INTL 20060113)
    10月 23 09:19:05 XSign kernel: ACPI: Interpreter enabled
    10月 23 09:19:05 XSign kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130517/hwxface-571)
    10月 23 09:19:05 XSign kernel: ACPI: (supports S0 S1 S3 S4 S5)
    10月 23 09:19:05 XSign kernel: ACPI: Using IOAPIC for interrupt routing
    10月 23 09:19:05 XSign kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf0000000-0xf3ffffff] (base 0xf0000000)
    10月 23 09:19:05 XSign kernel: PCI: MMCONFIG at [mem 0xf0000000-0xf3ffffff] reserved in ACPI motherboard resources
    10月 23 09:19:05 XSign kernel: PCI: Using MMCONFIG for extended config space
    10月 23 09:19:05 XSign kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    10月 23 09:19:05 XSign kernel: ACPI: No dock devices found.
    10月 23 09:19:05 XSign kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    10月 23 09:19:05 XSign kernel: acpi PNP0A08:00: ACPI _OSC support notification failed, disabling PCIe ASPM
    10月 23 09:19:05 XSign kernel: acpi PNP0A08:00: Unable to request _OSC control (_OSC support mask: 0x08)
    10月 23 09:19:05 XSign kernel: acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
    10月 23 09:19:05 XSign kernel: PCI host bridge to bus 0000:00
    10月 23 09:19:05 XSign kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
    10月 23 09:19:05 XSign kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
    10月 23 09:19:05 XSign kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    10月 23 09:19:05 XSign kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    10月 23 09:19:05 XSign kernel: pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000dffff]
    10月 23 09:19:05 XSign kernel: pci_bus 0000:00: root bus resource [mem 0xdf700000-0xffffffff]
    10月 23 09:19:05 XSign kernel: pci 0000:00:00.0: [8086:29c0] type 00 class 0x060000
    10月 23 09:19:05 XSign kernel: pci 0000:00:02.0: [8086:29c2] type 00 class 0x030000
    10月 23 09:19:05 XSign kernel: pci 0000:00:02.0: reg 0x10: [mem 0xfea80000-0xfeafffff]
    10月 23 09:19:05 XSign kernel: pci 0000:00:02.0: reg 0x14: [io 0xdc00-0xdc07]
    10月 23 09:19:05 XSign kernel: pci 0000:00:02.0: reg 0x18: [mem 0xe0000000-0xefffffff pref]
    10月 23 09:19:05 XSign kernel: pci 0000:00:02.0: reg 0x1c: [mem 0xfe900000-0xfe9fffff]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1b.0: [8086:27d8] type 00 class 0x040300
    10月 23 09:19:05 XSign kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xfea78000-0xfea7bfff 64bit]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: [8086:27d0] type 01 class 0x060400
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.1: [8086:27d2] type 01 class 0x060400
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.1: System wakeup disabled by ACPI
    10月 23 09:19:05 XSign kernel: pci 0000:00:1d.0: [8086:27c8] type 00 class 0x0c0300
    10月 23 09:19:05 XSign kernel: pci 0000:00:1d.0: reg 0x20: [io 0xd400-0xd41f]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
    10月 23 09:19:05 XSign kernel: pci 0000:00:1d.1: [8086:27c9] type 00 class 0x0c0300
    10月 23 09:19:05 XSign kernel: pci 0000:00:1d.1: reg 0x20: [io 0xd480-0xd49f]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1d.1: System wakeup disabled by ACPI
    10月 23 09:19:05 XSign kernel: pci 0000:00:1d.2: [8086:27ca] type 00 class 0x0c0300
    10月 23 09:19:05 XSign kernel: pci 0000:00:1d.2: reg 0x20: [io 0xd800-0xd81f]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1d.2: System wakeup disabled by ACPI
    10月 23 09:19:05 XSign kernel: pci 0000:00:1d.3: [8086:27cb] type 00 class 0x0c0300
    10月 23 09:19:05 XSign kernel: pci 0000:00:1d.3: reg 0x20: [io 0xd880-0xd89f]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1d.3: System wakeup disabled by ACPI
    10月 23 09:19:05 XSign kernel: pci 0000:00:1d.7: [8086:27cc] type 00 class 0x0c0320
    10月 23 09:19:05 XSign kernel: pci 0000:00:1d.7: reg 0x10: [mem 0xfea77c00-0xfea77fff]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
    10月 23 09:19:05 XSign kernel: pci 0000:00:1d.7: System wakeup disabled by ACPI
    10月 23 09:19:05 XSign kernel: pci 0000:00:1e.0: [8086:244e] type 01 class 0x060401
    10月 23 09:19:05 XSign kernel: pci 0000:00:1e.0: System wakeup disabled by ACPI
    10月 23 09:19:05 XSign kernel: pci 0000:00:1f.0: [8086:27b8] type 00 class 0x060100
    10月 23 09:19:05 XSign kernel: pci 0000:00:1f.0: address space collision: [io 0x0800-0x087f] conflicts with ACPI CPU throttle [??? 0x00000810-0x00000815 flags 0x80000000]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1f.0: quirk: [io 0x0480-0x04bf] claimed by ICH6 GPIO
    10月 23 09:19:05 XSign kernel: pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0294 (mask 0003)
    10月 23 09:19:05 XSign kernel: pci 0000:00:1f.1: [8086:27df] type 00 class 0x01018a
    10月 23 09:19:05 XSign kernel: pci 0000:00:1f.1: reg 0x10: [io 0x0000-0x0007]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1f.1: reg 0x14: [io 0x0000-0x0003]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1f.1: reg 0x18: [io 0x08f0-0x08f7]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1f.1: reg 0x1c: [io 0x08f8-0x08fb]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1f.1: reg 0x20: [io 0xffa0-0xffaf]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1f.2: [8086:27c0] type 00 class 0x01018f
    10月 23 09:19:05 XSign kernel: pci 0000:00:1f.2: reg 0x10: [io 0xd080-0xd087]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1f.2: reg 0x14: [io 0xd000-0xd003]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1f.2: reg 0x18: [io 0xcc00-0xcc07]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1f.2: reg 0x1c: [io 0xc880-0xc883]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1f.2: reg 0x20: [io 0xc800-0xc80f]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1f.2: PME# supported from D3hot
    10月 23 09:19:05 XSign kernel: pci 0000:00:1f.3: [8086:27da] type 00 class 0x0c0500
    10月 23 09:19:05 XSign kernel: pci 0000:00:1f.3: reg 0x20: [io 0x0400-0x041f]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
    10月 23 09:19:05 XSign kernel: pci 0000:01:00.0: [10ec:8136] type 00 class 0x020000
    10月 23 09:19:05 XSign kernel: pci 0000:01:00.0: reg 0x10: [io 0xe800-0xe8ff]
    10月 23 09:19:05 XSign kernel: pci 0000:01:00.0: reg 0x18: [mem 0xfdfff000-0xfdffffff 64bit pref]
    10月 23 09:19:05 XSign kernel: pci 0000:01:00.0: reg 0x20: [mem 0xfdfe0000-0xfdfeffff 64bit pref]
    10月 23 09:19:05 XSign kernel: pci 0000:01:00.0: reg 0x30: [mem 0xfebf0000-0xfebfffff pref]
    10月 23 09:19:05 XSign kernel: pci 0000:01:00.0: supports D1 D2
    10月 23 09:19:05 XSign kernel: pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.1: PCI bridge to [bus 01]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.1: bridge window [io 0xe000-0xefff]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.1: bridge window [mem 0xfeb00000-0xfebfffff]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.1: bridge window [mem 0xfdf00000-0xfdffffff 64bit pref]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1e.0: PCI bridge to [bus 03] (subtractive decode)
    10月 23 09:19:05 XSign kernel: pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
    10月 23 09:19:05 XSign kernel: pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
    10月 23 09:19:05 XSign kernel: pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
    10月 23 09:19:05 XSign kernel: pci 0000:00:1e.0: bridge window [mem 0x000d0000-0x000dffff] (subtractive decode)
    10月 23 09:19:05 XSign kernel: pci 0000:00:1e.0: bridge window [mem 0xdf700000-0xffffffff] (subtractive decode)
    10月 23 09:19:05 XSign kernel: pci_bus 0000:00: on NUMA node 0
    10月 23 09:19:05 XSign kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15)
    10月 23 09:19:05 XSign kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
    10月 23 09:19:05 XSign kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs *3 4 5 6 7 10 11 12 14 15)
    10月 23 09:19:05 XSign kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 *7 10 11 12 14 15)
    10月 23 09:19:05 XSign kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
    10月 23 09:19:05 XSign kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
    10月 23 09:19:05 XSign kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
    10月 23 09:19:05 XSign kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 6 7 10 11 12 14 15)
    10月 23 09:19:05 XSign kernel: ACPI: Enabled 2 GPEs in block 00 to 1F
    10月 23 09:19:05 XSign kernel: ACPI: \_SB_.PCI0: notify handler is installed
    10月 23 09:19:05 XSign kernel: Found 1 acpi root devices
    10月 23 09:19:05 XSign kernel: vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
    10月 23 09:19:05 XSign kernel: vgaarb: loaded
    10月 23 09:19:05 XSign kernel: vgaarb: bridge control possible 0000:00:02.0
    10月 23 09:19:05 XSign kernel: PCI: Using ACPI for IRQ routing
    10月 23 09:19:05 XSign kernel: PCI: pci_cache_line_size set to 64 bytes
    10月 23 09:19:05 XSign kernel: e820: reserve RAM buffer [mem 0x0009fc00-0x0009ffff]
    10月 23 09:19:05 XSign kernel: e820: reserve RAM buffer [mem 0xdf690000-0xdfffffff]
    10月 23 09:19:05 XSign kernel: NetLabel: Initializing
    10月 23 09:19:05 XSign kernel: NetLabel: domain hash size = 128
    10月 23 09:19:05 XSign kernel: NetLabel: protocols = UNLABELED CIPSOv4
    10月 23 09:19:05 XSign kernel: NetLabel: unlabeled traffic allowed by default
    10月 23 09:19:05 XSign kernel: HPET: 3 timers in total, 0 timers will be used for per-cpu timer
    10月 23 09:19:05 XSign kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
    10月 23 09:19:05 XSign kernel: hpet0: 3 comparators, 64-bit 14.318180 MHz counter
    10月 23 09:19:05 XSign kernel: Switched to clocksource hpet
    10月 23 09:19:05 XSign kernel: pnp: PnP ACPI init
    10月 23 09:19:05 XSign kernel: ACPI: bus type PNP registered
    10月 23 09:19:05 XSign kernel: system 00:00: [mem 0xfed14000-0xfed19fff] has been reserved
    10月 23 09:19:05 XSign kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
    10月 23 09:19:05 XSign kernel: pnp 00:01: [dma 4]
    10月 23 09:19:05 XSign kernel: pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
    10月 23 09:19:05 XSign kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
    10月 23 09:19:05 XSign kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0800 (active)
    10月 23 09:19:05 XSign kernel: pnp 00:04: Plug and Play ACPI device, IDs PNP0c04 (active)
    10月 23 09:19:05 XSign kernel: system 00:05: [io 0x0290-0x0297] has been reserved
    10月 23 09:19:05 XSign kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
    10月 23 09:19:05 XSign kernel: system 00:06: [io 0x04d0-0x04d1] has been reserved
    10月 23 09:19:05 XSign kernel: system 00:06: [io 0x0800-0x087f] could not be reserved
    10月 23 09:19:05 XSign kernel: system 00:06: [io 0x0480-0x04bf] has been reserved
    10月 23 09:19:05 XSign kernel: system 00:06: [mem 0xfed1c000-0xfed1ffff] has been reserved
    10月 23 09:19:05 XSign kernel: system 00:06: [mem 0xfed20000-0xfed8ffff] has been reserved
    10月 23 09:19:05 XSign kernel: system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
    10月 23 09:19:05 XSign kernel: pnp 00:07: Plug and Play ACPI device, IDs PNP0103 (active)
    10月 23 09:19:05 XSign kernel: pnp 00:08: Plug and Play ACPI device, IDs INT0800 (active)
    10月 23 09:19:05 XSign kernel: system 00:09: [mem 0xffc00000-0xffefffff] has been reserved
    10月 23 09:19:05 XSign kernel: system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
    10月 23 09:19:05 XSign kernel: system 00:0a: [mem 0xfec00000-0xfec00fff] could not be reserved
    10月 23 09:19:05 XSign kernel: system 00:0a: [mem 0xfee00000-0xfee00fff] has been reserved
    10月 23 09:19:05 XSign kernel: system 00:0a: Plug and Play ACPI device, IDs PNP0c02 (active)
    10月 23 09:19:05 XSign kernel: pnp 00:0b: Plug and Play ACPI device, IDs PNP0303 PNP030b (active)
    10月 23 09:19:05 XSign kernel: pnp 00:0c: Plug and Play ACPI device, IDs PNP0f03 PNP0f13 (active)
    10月 23 09:19:05 XSign kernel: pnp 00:0d: [dma 0 disabled]
    10月 23 09:19:05 XSign kernel: pnp 00:0d: Plug and Play ACPI device, IDs PNP0501 (active)
    10月 23 09:19:05 XSign kernel: system 00:0e: [mem 0xf0000000-0xf3ffffff] has been reserved
    10月 23 09:19:05 XSign kernel: system 00:0e: Plug and Play ACPI device, IDs PNP0c02 (active)
    10月 23 09:19:05 XSign kernel: system 00:0f: [mem 0x00000000-0x0009ffff] could not be reserved
    10月 23 09:19:05 XSign kernel: system 00:0f: [mem 0x000c0000-0x000cffff] could not be reserved
    10月 23 09:19:05 XSign kernel: system 00:0f: [mem 0x000e0000-0x000fffff] could not be reserved
    10月 23 09:19:05 XSign kernel: system 00:0f: [mem 0x00100000-0xdf6fffff] could not be reserved
    10月 23 09:19:05 XSign kernel: system 00:0f: Plug and Play ACPI device, IDs PNP0c01 (active)
    10月 23 09:19:05 XSign kernel: pnp: PnP ACPI: found 16 devices
    10月 23 09:19:05 XSign kernel: ACPI: bus type PNP unregistered
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: bridge window [io 0x1000-0x0fff] to [bus 02] add_size 1000
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 02] add_size 200000
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 02] add_size 200000
    10月 23 09:19:05 XSign kernel: pci 0000:00:1f.0: BAR 13: [io 0x0800-0x087f] has bogus alignment
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x000fffff] get_res_add_size add_size 200000
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: BAR 14: assigned [mem 0xdf700000-0xdf8fffff]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: BAR 15: assigned [mem 0xdf900000-0xdfafffff 64bit pref]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: BAR 13: assigned [io 0x1000-0x1fff]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: bridge window [io 0x1000-0x1fff]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: bridge window [mem 0xdf700000-0xdf8fffff]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: bridge window [mem 0xdf900000-0xdfafffff 64bit pref]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.1: PCI bridge to [bus 01]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.1: bridge window [io 0xe000-0xefff]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.1: bridge window [mem 0xfeb00000-0xfebfffff]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.1: bridge window [mem 0xfdf00000-0xfdffffff 64bit pref]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1e.0: PCI bridge to [bus 03]
    10月 23 09:19:05 XSign kernel: pci 0000:00:1c.0: enabling device (0104 -> 0107)
    10月 23 09:19:05 XSign kernel: pci 0000:00:1e.0: setting latency timer to 64
    10月 23 09:19:05 XSign kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    10月 23 09:19:05 XSign kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    10月 23 09:19:05 XSign kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    10月 23 09:19:05 XSign kernel: pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000dffff]
    10月 23 09:19:05 XSign kernel: pci_bus 0000:00: resource 8 [mem 0xdf700000-0xffffffff]
    10月 23 09:19:05 XSign kernel: pci_bus 0000:02: resource 0 [io 0x1000-0x1fff]
    10月 23 09:19:05 XSign kernel: pci_bus 0000:02: resource 1 [mem 0xdf700000-0xdf8fffff]
    10月 23 09:19:05 XSign kernel: pci_bus 0000:02: resource 2 [mem 0xdf900000-0xdfafffff 64bit pref]
    10月 23 09:19:05 XSign kernel: pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
    10月 23 09:19:05 XSign kernel: pci_bus 0000:01: resource 1 [mem 0xfeb00000-0xfebfffff]
    10月 23 09:19:05 XSign kernel: pci_bus 0000:01: resource 2 [mem 0xfdf00000-0xfdffffff 64bit pref]
    10月 23 09:19:05 XSign kernel: pci_bus 0000:03: resource 4 [io 0x0000-0x0cf7]
    10月 23 09:19:05 XSign kernel: pci_bus 0000:03: resource 5 [io 0x0d00-0xffff]
    10月 23 09:19:05 XSign kernel: pci_bus 0000:03: resource 6 [mem 0x000a0000-0x000bffff]
    10月 23 09:19:05 XSign kernel: pci_bus 0000:03: resource 7 [mem 0x000d0000-0x000dffff]
    10月 23 09:19:05 XSign kernel: pci_bus 0000:03: resource 8 [mem 0xdf700000-0xffffffff]
    10月 23 09:19:05 XSign kernel: NET: Registered protocol family 2
    10月 23 09:19:05 XSign kernel: TCP established hash table entries: 8192 (order: 4, 65536 bytes)
    10月 23 09:19:05 XSign kernel: TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
    10月 23 09:19:05 XSign kernel: TCP: Hash tables configured (established 8192 bind 8192)
    10月 23 09:19:05 XSign kernel: TCP: reno registered
    10月 23 09:19:05 XSign kernel: UDP hash table entries: 512 (order: 2, 16384 bytes)
    10月 23 09:19:05 XSign kernel: UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
    10月 23 09:19:05 XSign kernel: NET: Registered protocol family 1
    10月 23 09:19:05 XSign kernel: pci 0000:00:02.0: Boot video device
    10月 23 09:19:05 XSign kernel: PCI: CLS 32 bytes, default 64
    10月 23 09:19:05 XSign kernel: Unpacking initramfs...
    10月 23 09:19:05 XSign kernel: Freeing initrd memory: 2624K (f756e000 - f77fe000)
    10月 23 09:19:05 XSign kernel: apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
    10月 23 09:19:05 XSign kernel: apm: disabled - APM is not SMP safe.
    10月 23 09:19:05 XSign kernel: Scanning for low memory corruption every 60 seconds
    10月 23 09:19:05 XSign kernel: audit: initializing netlink socket (disabled)
    10月 23 09:19:05 XSign kernel: type=2000 audit(1382519941.199:1): initialized
    10月 23 09:19:05 XSign kernel: bounce pool size: 64 pages
    10月 23 09:19:05 XSign kernel: HugeTLB registered 4 MB page size, pre-allocated 0 pages
    10月 23 09:19:05 XSign kernel: zbud: loaded
    10月 23 09:19:05 XSign kernel: VFS: Disk quotas dquot_6.5.2
    10月 23 09:19:05 XSign kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    10月 23 09:19:05 XSign kernel: msgmni has been set to 1688
    10月 23 09:19:05 XSign kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    10月 23 09:19:05 XSign kernel: io scheduler noop registered
    10月 23 09:19:05 XSign kernel: io scheduler deadline registered
    10月 23 09:19:05 XSign kernel: io scheduler cfq registered (default)
    10月 23 09:19:05 XSign kernel: pcieport 0000:00:1c.0: irq 40 for MSI/MSI-X
    10月 23 09:19:05 XSign kernel: pcieport 0000:00:1c.1: irq 41 for MSI/MSI-X
    10月 23 09:19:05 XSign kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    10月 23 09:19:05 XSign kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
    10月 23 09:19:05 XSign kernel: intel_idle: does not run on family 6 model 15
    10月 23 09:19:05 XSign kernel: GHES: HEST is not enabled!
    10月 23 09:19:05 XSign kernel: isapnp: Scanning for PnP cards...
    10月 23 09:19:05 XSign kernel: isapnp: No Plug & Play device found
    10月 23 09:19:05 XSign kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    10月 23 09:19:05 XSign kernel: 00:0d: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    10月 23 09:19:05 XSign kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
    10月 23 09:19:05 XSign kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
    10月 23 09:19:05 XSign kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
    10月 23 09:19:05 XSign kernel: mousedev: PS/2 mouse device common for all mice
    10月 23 09:19:05 XSign kernel: rtc_cmos 00:02: RTC can wake from S4
    10月 23 09:19:05 XSign kernel: rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
    10月 23 09:19:05 XSign kernel: rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
    10月 23 09:19:05 XSign kernel: cpuidle: using governor ladder
    10月 23 09:19:05 XSign kernel: cpuidle: using governor menu
    10月 23 09:19:05 XSign kernel: drop_monitor: Initializing network drop monitor service
    10月 23 09:19:05 XSign kernel: TCP: cubic registered
    10月 23 09:19:05 XSign kernel: NET: Registered protocol family 10
    10月 23 09:19:05 XSign kernel: NET: Registered protocol family 17
    10月 23 09:19:05 XSign kernel: Key type dns_resolver registered
    10月 23 09:19:05 XSign kernel: Using IPI No-Shortcut mode
    10月 23 09:19:05 XSign kernel: PM: Hibernation image not present or could not be loaded.
    10月 23 09:19:05 XSign kernel: registered taskstats version 1
    10月 23 09:19:05 XSign kernel: Magic number: 1:976:323
    10月 23 09:19:05 XSign kernel: tty tty48: hash matches
    10月 23 09:19:05 XSign kernel: rtc_cmos 00:02: setting system clock to 2013-10-23 09:19:02 UTC (1382519942)
    10月 23 09:19:05 XSign kernel: Freeing unused kernel memory: 608K (c06e9000 - c0781000)
    10月 23 09:19:05 XSign kernel: Write protecting the kernel text: 4264k
    10月 23 09:19:05 XSign kernel: Write protecting the kernel read-only data: 1360k
    10月 23 09:19:05 XSign systemd-udevd[47]: starting version 208
    10月 23 09:19:05 XSign kernel: ACPI: bus type USB registered
    10月 23 09:19:05 XSign kernel: usbcore: registered new interface driver usbfs
    10月 23 09:19:05 XSign kernel: usbcore: registered new interface driver hub
    10月 23 09:19:05 XSign kernel: usbcore: registered new device driver usb
    10月 23 09:19:05 XSign kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    10月 23 09:19:05 XSign kernel: uhci_hcd: USB Universal Host Controller Interface driver
    10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.0: setting latency timer to 64
    10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.0: UHCI Host Controller
    10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
    10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000d400
    10月 23 09:19:05 XSign kernel: hub 1-0:1.0: USB hub found
    10月 23 09:19:05 XSign kernel: hub 1-0:1.0: 2 ports detected
    10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.1: setting latency timer to 64
    10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.1: UHCI Host Controller
    10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
    10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000d480
    10月 23 09:19:05 XSign kernel: hub 2-0:1.0: USB hub found
    10月 23 09:19:05 XSign kernel: hub 2-0:1.0: 2 ports detected
    10月 23 09:19:05 XSign kernel: SCSI subsystem initialized
    10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.2: setting latency timer to 64
    10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.2: UHCI Host Controller
    10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
    10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000d800
    10月 23 09:19:05 XSign kernel: hub 3-0:1.0: USB hub found
    10月 23 09:19:05 XSign kernel: hub 3-0:1.0: 2 ports detected
    10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.3: setting latency timer to 64
    10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.3: UHCI Host Controller
    10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
    10月 23 09:19:05 XSign kernel: uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000d880
    10月 23 09:19:05 XSign kernel: hub 4-0:1.0: USB hub found
    10月 23 09:19:05 XSign kernel: hub 4-0:1.0: 2 ports detected
    10月 23 09:19:05 XSign kernel: ehci-pci: EHCI PCI platform driver
    10月 23 09:19:05 XSign kernel: ehci-pci 0000:00:1d.7: setting latency timer to 64
    10月 23 09:19:05 XSign kernel: ehci-pci 0000:00:1d.7: EHCI Host Controller
    10月 23 09:19:05 XSign kernel: ehci-pci 0000:00:1d.7: new USB bus registered, assigned bus number 5
    10月 23 09:19:05 XSign kernel: ehci-pci 0000:00:1d.7: debug port 1
    10月 23 09:19:05 XSign kernel: ACPI: bus type ATA registered
    10月 23 09:19:05 XSign kernel: ehci-pci 0000:00:1d.7: cache line size of 32 is not supported
    10月 23 09:19:05 XSign kernel: ehci-pci 0000:00:1d.7: irq 23, io mem 0xfea77c00
    10月 23 09:19:05 XSign kernel: libata version 3.00 loaded.
    10月 23 09:19:05 XSign kernel: ehci-pci 0000:00:1d.7: USB 2.0 started, EHCI 1.00
    10月 23 09:19:05 XSign kernel: hub 5-0:1.0: USB hub found
    10月 23 09:19:05 XSign kernel: hub 5-0:1.0: 8 ports detected
    10月 23 09:19:05 XSign kernel: hub 1-0:1.0: USB hub found
    10月 23 09:19:05 XSign kernel: hub 1-0:1.0: 2 ports detected
    10月 23 09:19:05 XSign kernel: hub 2-0:1.0: USB hub found
    10月 23 09:19:05 XSign kernel: hub 2-0:1.0: 2 ports detected
    10月 23 09:19:05 XSign kernel: hub 3-0:1.0: USB hub found
    10月 23 09:19:05 XSign kernel: hub 3-0:1.0: 2 ports detected
    10月 23 09:19:05 XSign kernel: hub 4-0:1.0: USB hub found
    10月 23 09:19:05 XSign kernel: hub 4-0:1.0: 2 ports detected
    10月 23 09:19:05 XSign kernel: ata_piix 0000:00:1f.1: version 2.13
    10月 23 09:19:05 XSign kernel: ata_piix 0000:00:1f.1: setting latency timer to 64
    10月 23 09:19:05 XSign kernel: scsi0 : ata_piix
    10月 23 09:19:05 XSign kernel: scsi1 : ata_piix
    10月 23 09:19:05 XSign kernel: ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
    10月 23 09:19:05 XSign kernel: ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
    10月 23 09:19:05 XSign kernel: ata_piix 0000:00:1f.2: MAP [
    10月 23 09:19:05 XSign kernel: P0 P2 P1 P3 ]
    10月 23 09:19:05 XSign kernel: ata_piix 0000:00:1f.2: setting latency timer to 64
    10月 23 09:19:05 XSign kernel: scsi2 : ata_piix
    10月 23 09:19:05 XSign kernel: scsi3 : ata_piix
    10月 23 09:19:05 XSign kernel: ata3: SATA max UDMA/133 cmd 0xd080 ctl 0xd000 bmdma 0xc800 irq 19
    10月 23 09:19:05 XSign kernel: ata4: SATA max UDMA/133 cmd 0xcc00 ctl 0xc880 bmdma 0xc808 irq 19
    10月 23 09:19:05 XSign kernel: ata3.00: ATA-8: ST3500410AS, CC31, max UDMA/133
    10月 23 09:19:05 XSign kernel: ata3.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    10月 23 09:19:05 XSign kernel: ata3.01: ATA-8: ST3500418AS, CC38, max UDMA/133
    10月 23 09:19:05 XSign kernel: ata3.01: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    10月 23 09:19:05 XSign kernel: usb 5-2: new high-speed USB device number 2 using ehci-pci
    10月 23 09:19:05 XSign kernel: ata3.00: configured for UDMA/133
    10月 23 09:19:05 XSign kernel: ata3.01: configured for UDMA/133
    10月 23 09:19:05 XSign kernel: scsi 2:0:0:0: Direct-Access ATA ST3500410AS CC31 PQ: 0 ANSI: 5
    10月 23 09:19:05 XSign kernel: scsi 2:0:1:0: Direct-Access ATA ST3500418AS CC38 PQ: 0 ANSI: 5
    10月 23 09:19:05 XSign kernel: sd 2:0:1:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
    10月 23 09:19:05 XSign kernel: sd 2:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
    10月 23 09:19:05 XSign kernel: sd 2:0:1:0: [sdb] Write Protect is off
    10月 23 09:19:05 XSign kernel: sd 2:0:1:0: [sdb] Mode Sense: 00 3a 00 00
    10月 23 09:19:05 XSign kernel: sd 2:0:0:0: [sda] Write Protect is off
    10月 23 09:19:05 XSign kernel: sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
    10月 23 09:19:05 XSign kernel: sd 2:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    10月 23 09:19:05 XSign kernel: sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    10月 23 09:19:05 XSign kernel: sdb: sdb1 sdb2 < sdb5 sdb6 sdb7 >
    10月 23 09:19:05 XSign kernel: hidraw: raw HID events driver (C) Jiri Kosina
    10月 23 09:19:05 XSign kernel: usbcore: registered new interface driver usbhid
    10月 23 09:19:05 XSign kernel: usbhid: USB HID core driver
    10月 23 09:19:05 XSign kernel: usb-storage 5-2:1.0: USB Mass Storage device detected
    10月 23 09:19:05 XSign kernel: scsi4 : usb-storage 5-2:1.0
    10月 23 09:19:05 XSign kernel: usbcore: registered new interface driver usb-storage
    10月 23 09:19:05 XSign kernel: input: Smart KM Link as /devices/pci0000:00/0000:00:1d.7/usb5/5-2/5-2:1.1/input/input0
    10月 23 09:19:05 XSign kernel: hid-generic 0003:0EA0:2211.0001: input,hidraw0: USB HID v1.00 Mouse [ Smart KM Link ] on usb-0000:00:1d.7-2/input1
    10月 23 09:19:05 XSign kernel: input: Smart KM Link as /devices/pci0000:00/0000:00:1d.7/usb5/5-2/5-2:1.2/input/input1
    10月 23 09:19:05 XSign kernel: hid-generic 0003:0EA0:2211.0002: input,hidraw1: USB HID v1.00 Keyboard [ Smart KM Link ] on usb-0000:00:1d.7-2/input2
    10月 23 09:19:05 XSign kernel: sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >
    10月 23 09:19:05 XSign kernel: sd 2:0:1:0: [sdb] Attached SCSI disk
    10月 23 09:19:05 XSign kernel: sd 2:0:0:0: [sda] Attached SCSI disk
    10月 23 09:19:05 XSign kernel: usb 5-3: new high-speed USB device number 3 using ehci-pci
    10月 23 09:19:05 XSign kernel: tsc: Refined TSC clocksource calibration: 3010.028 MHz
    10月 23 09:19:05 XSign kernel: hub 5-3:1.0: USB hub found
    10月 23 09:19:05 XSign kernel: hub 5-3:1.0: 2 ports detected
    10月 23 09:19:05 XSign kernel: usb 5-3.1: new full-speed USB device number 4 using ehci-pci
    10月 23 09:19:05 XSign kernel: input: Razer Razer Mamba as /devices/pci0000:00/0000:00:1d.7/usb5/5-3/5-3.1/5-3.1:1.0/input/input2
    10月 23 09:19:05 XSign kernel: hid-generic 0003:1532:0024.0003: input,hidraw2: USB HID v1.11 Mouse [Razer Razer Mamba] on usb-0000:00:1d.7-3.1/input0
    10月 23 09:19:05 XSign kernel: input: Razer Razer Mamba as /devices/pci0000:00/0000:00:1d.7/usb5/5-3/5-3.1/5-3.1:1.1/input/input3
    10月 23 09:19:05 XSign kernel: hid-generic 0003:1532:0024.0004: input,hidraw3: USB HID v1.11 Keyboard [Razer Razer Mamba] on usb-0000:00:1d.7-3.1/input1
    10月 23 09:19:05 XSign kernel: usb 5-3.2: new full-speed USB device number 5 using ehci-pci
    10月 23 09:19:05 XSign kernel: input: Heng Yu Technology Poker Pro S as /devices/pci0000:00/0000:00:1d.7/usb5/5-3/5-3.2/5-3.2:1.0/input/input4
    10月 23 09:19:05 XSign kernel: hid-generic 0003:0F39:0611.0005: input,hidraw4: USB HID v1.10 Keyboard [Heng Yu Technology Poker Pro S] on usb-0000:00:1d.7-3.2/input0
    10月 23 09:19:05 XSign kernel: input: Heng Yu Technology Poker Pro S as /devices/pci0000:00/0000:00:1d.7/usb5/5-3/5-3.2/5-3.2:1.1/input/input5
    10月 23 09:19:05 XSign kernel: hid-generic 0003:0F39:0611.0006: input,hidraw5: USB HID v1.10 Device [Heng Yu Technology Poker Pro S] on usb-0000:00:1d.7-3.2/input1
    10月 23 09:19:05 XSign kernel: scsi 4:0:0:0: CD-ROM Smart KM Link 2.00 PQ: 0 ANSI: 0
    10月 23 09:19:05 XSign kernel: sr0: scsi-1 drive
    10月 23 09:19:05 XSign kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
    10月 23 09:19:05 XSign kernel: sr 4:0:0:0: Attached scsi CD-ROM sr0
    10月 23 09:19:05 XSign kernel: Switched to clocksource tsc
    10月 23 09:19:05 XSign kernel: REISERFS (device sda2): found reiserfs format "3.6" with standard journal
    10月 23 09:19:05 XSign kernel: REISERFS (device sda2): using ordered data mode
    10月 23 09:19:05 XSign kernel: reiserfs: using flush barriers
    10月 23 09:19:05 XSign kernel: REISERFS (device sda2): journal params: device sda2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
    10月 23 09:19:05 XSign kernel: REISERFS (device sda2): checking transaction log (sda2)
    10月 23 09:19:05 XSign kernel: REISERFS (device sda2): Using r5 hash to sort names
    10月 23 09:19:05 XSign systemd[1]: RTC configured in localtime, applying delta of 480 minutes to system time.
    10月 23 09:19:05 XSign systemd[1]: systemd 208 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
    10月 23 09:19:05 XSign systemd[1]: Set hostname to <XSign>.
    10月 23 09:19:05 XSign systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
    10月 23 09:19:05 XSign systemd[1]: Started Forward Password Requests to Wall Directory Watch.
    10月 23 09:19:05 XSign systemd[1]: Starting Syslog Socket.
    10月 23 09:19:05 XSign systemd[1]: Listening on Syslog Socket.
    10月 23 09:19:05 XSign systemd[1]: Starting Remote File Systems.
    10月 23 09:19:05 XSign systemd[1]: Reached target Remote File Systems.
    10月 23 09:19:05 XSign systemd[1]: Starting Device-mapper event daemon FIFOs.
    10月 23 09:19:05 XSign systemd[1]: Listening on Device-mapper event daemon FIFOs.
    10月 23 09:19:05 XSign systemd[1]: Starting Delayed Shutdown Socket.
    10月 23 09:19:05 XSign systemd[1]: Listening on Delayed Shutdown Socket.
    10月 23 09:19:05 XSign systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
    10月 23 09:19:05 XSign systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
    10月 23 09:19:05 XSign systemd[1]: Starting LVM2 metadata daemon socket.
    10月 23 09:19:05 XSign systemd[1]: Listening on LVM2 metadata daemon socket.
    10月 23 09:19:05 XSign systemd[1]: Starting Encrypted Volumes.
    10月 23 09:19:05 XSign systemd[1]: Reached target Encrypted Volumes.
    10月 23 09:19:05 XSign systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
    10月 23 09:19:05 XSign systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    10月 23 09:19:05 XSign systemd[1]: Starting Paths.
    10月 23 09:19:05 XSign systemd[1]: Reached target Paths.
    10月 23 09:19:05 XSign systemd[1]: Starting udev Kernel Socket.
    10月 23 09:19:05 XSign systemd[1]: Listening on udev Kernel Socket.
    10月 23 09:19:05 XSign systemd[1]: Starting udev Control Socket.
    10月 23 09:19:05 XSign systemd[1]: Listening on udev Control Socket.
    10月 23 09:19:05 XSign systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
    10月 23 09:19:05 XSign systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
    10月 23 09:19:05 XSign systemd[1]: Starting Journal Socket.
    10月 23 09:19:05 XSign systemd[1]: Listening on Journal Socket.
    10月 23 09:19:05 XSign systemd[1]: Starting Apply Kernel Variables...
    10月 23 09:19:05 XSign systemd[1]: Mounting POSIX Message Queue File System...
    10月 23 09:19:05 XSign systemd[1]: Starting Create list of required static device nodes for the current kernel...
    10月 23 09:19:05 XSign systemd[1]: Starting udev Coldplug all Devices...
    10月 23 09:19:05 XSign systemd[1]: Mounting Debug File System...
    10月 23 09:19:05 XSign systemd[1]: Mounting Huge Pages File System...
    10月 23 09:19:05 XSign systemd[1]: Starting Journal Service...
    10月 23 09:19:05 XSign systemd[1]: Started Journal Service.
    10月 23 09:19:05 XSign kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
    10月 23 09:19:05 XSign kernel: r8169 0000:01:00.0: can't disable ASPM; OS doesn't have ASPM control
    10月 23 09:19:05 XSign kernel: r8169 0000:01:00.0: irq 42 for MSI/MSI-X
    10月 23 09:19:05 XSign kernel: r8169 0000:01:00.0 eth0: RTL8102e at 0xf8804000, 00:23:54:dd:9d:c4, XID 04a00000 IRQ 42
    10月 23 09:19:05 XSign systemd-journal[105]: Journal started
    10月 23 09:19:05 XSign systemd[1]: Starting Set Up Additional Binary Formats...
    10月 23 09:19:05 XSign systemd[1]: Starting Load Kernel Modules...
    10月 23 09:19:05 XSign systemd[1]: Starting Setup Virtual Console...
    10月 23 09:19:05 XSign systemd[1]: Expecting device dev-disk-by\x2duuid-b9fe1d55\x2db46c\x2d45a1\x2da068\x2d9e754189e7f3.device...
    10月 23 09:19:05 XSign systemd[1]: Starting File System Check on Root Device...
    10月 23 09:19:05 XSign systemd[1]: Expecting device dev-disk-by\x2duuid-20723153\x2dd5da\x2d4091\x2d807d\x2d6a8d945f9b22.device...
    10月 23 09:19:05 XSign systemd[1]: Expecting device dev-disk-by\x2duuid-61e54abe\x2d34cd\x2d4bd0\x2db225\x2dd187ac5137f2.device...
    10月 23 09:19:05 XSign systemd[1]: Expecting device dev-disk-by\x2duuid-7f64c378\x2d6403\x2d4786\x2daec0\x2d1c6e42532175.device...
    10月 23 09:19:05 XSign systemd[1]: Expecting device dev-disk-by\x2duuid-86b99089\x2d3393\x2d4c20\x2dbce8\x2d0018e6cf5c85.device...
    10月 23 09:19:05 XSign systemd[1]: Expecting device dev-sdb1.device...
    10月 23 09:19:05 XSign systemd[1]: Expecting device dev-sdb5.device...
    10月 23 09:19:05 XSign systemd[1]: Expecting device dev-sdb6.device...
    10月 23 09:19:05 XSign systemd-modules-load[108]: Inserted module 'r8169'
    10月 23 09:19:05 XSign systemd[1]: Starting Root Slice.
    10月 23 09:19:05 XSign systemd[1]: Created slice Root Slice.
    10月 23 09:19:05 XSign systemd[1]: Starting User and Session Slice.
    10月 23 09:19:05 XSign systemd[1]: Created slice User and Session Slice.
    10月 23 09:19:05 XSign systemd[1]: Starting System Slice.
    10月 23 09:19:05 XSign systemd[1]: Created slice System Slice.
    10月 23 09:19:05 XSign systemd[1]: Starting system-getty.slice.
    10月 23 09:19:05 XSign systemd[1]: Created slice system-getty.slice.
    10月 23 09:19:05 XSign systemd[1]: Starting Slices.
    10月 23 09:19:05 XSign systemd[1]: Reached target Slices.
    10月 23 09:19:05 XSign systemd[1]: Expecting device dev-sdb7.device...
    10月 23 09:19:05 XSign systemd[1]: Started Apply Kernel Variables.
    10月 23 09:19:05 XSign systemd[1]: Mounted POSIX Message Queue File System.
    10月 23 09:19:05 XSign systemd[1]: Mounted Debug File System.
    10月 23 09:19:05 XSign systemd[1]: Mounted Huge Pages File System.
    10月 23 09:19:05 XSign systemd[1]: Started Setup Virtual Console.
    10月 23 09:19:05 XSign systemd[1]: Started File System Check on Root Device.
    10月 23 09:19:05 XSign systemd[1]: Starting Remount Root and Kernel File Systems...
    10月 23 09:19:05 XSign systemd[1]: Mounting Arbitrary Executable File Formats File System...
    10月 23 09:19:05 XSign systemd-fsck[110]: Reiserfs super block in block 16 on 0x802 of format 3.6 with standard journal
    10月 23 09:19:05 XSign systemd-fsck[110]: Blocks (total/free): 12500576/9229679 by 4096 bytes
    10月 23 09:19:05 XSign systemd-fsck[110]: Filesystem is clean
    10月 23 09:19:05 XSign kernel: vboxdrv: Found 2 processor cores.
    10月 23 09:19:05 XSign systemd-modules-load[108]: Inserted module 'vboxdrv'
    10月 23 09:19:05 XSign kernel: vboxdrv: fAsync=0 offMin=0x1c2 offMax=0xd5c
    10月 23 09:19:05 XSign kernel: vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
    10月 23 09:19:05 XSign kernel: vboxdrv: Successfully loaded version 4.3.0_OSE (interface 0x001a0005).
    10月 23 09:19:05 XSign systemd-modules-load[108]: Inserted module 'vboxnetflt'
    10月 23 09:19:05 XSign systemd-modules-load[108]: Inserted module 'vboxnetadp'
    10月 23 09:19:05 XSign systemd[1]: Started Load Kernel Modules.
    10月 23 09:19:05 XSign systemd[1]: Started udev Coldplug all Devices.
    10月 23 09:19:05 XSign systemd[1]: Mounting Configuration File System...
    10月 23 09:19:05 XSign systemd[1]: Mounted FUSE Control File System.
    10月 23 09:19:05 XSign systemd[1]: Mounted Arbitrary Executable File Formats File System.
    10月 23 09:19:05 XSign systemd[1]: Mounted Configuration File System.
    10月 23 09:19:05 XSign systemd[1]: Started Set Up Additional Binary Formats.
    10月 23 09:19:06 XSign systemd[1]: Started Create list of required static device nodes for the current kernel.
    10月 23 09:19:06 XSign systemd[1]: Starting Create static device nodes in /dev...
    10月 23 09:19:06 XSign kernel: reiserfs: enabling write barrier flush mode
    10月 23 09:19:06 XSign systemd[1]: Started Create static device nodes in /dev.
    10月 23 09:19:06 XSign systemd[1]: Starting udev Kernel Device Manager...
    10月 23 09:19:06 XSign systemd[1]: Started udev Kernel Device Manager.
    10月 23 09:19:06 XSign systemd-udevd[137]: starting version 208
    10月 23 09:19:06 XSign systemd[1]: Started Remount Root and Kernel File Systems.
    10月 23 09:19:06 XSign systemd[1]: Starting Local File Systems (Pre).
    10月 23 09:19:06 XSign systemd[1]: Reached target Local File Systems (Pre).
    10月 23 09:19:06 XSign kernel: ACPI: Requesting acpi_cpufreq
    10月 23 09:19:06 XSign kernel: Linux agpgart interface v0.103
    10月 23 09:19:06 XSign kernel: [drm] Initialized drm 1.1.0 20060810
    10月 23 09:19:06 XSign kernel: agpgart-intel 0000:00:00.0: Intel G33 Chipset
    10月 23 09:19:06 XSign kernel: agpgart-intel 0000:00:00.0: detected gtt size: 524288K total, 262144K mappable
    10月 23 09:19:06 XSign kernel: agpgart-intel 0000:00:00.0: detected 8192K stolen memory
    10月 23 09:19:06 XSign kernel: agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xe0000000
    10月 23 09:19:06 XSign kernel: input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input6
    10月 23 09:19:06 XSign kernel: ACPI: Power Button [PWRB]
    10月 23 09:19:06 XSign kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input7
    10月 23 09:19:06 XSign kernel: ACPI: Power Button [PWRF]
    10月 23 09:19:06 XSign kernel: [drm] Memory usable by graphics device = 512M
    10月 23 09:19:06 XSign kernel: i915 0000:00:02.0: setting latency timer to 64
    10月 23 09:19:06 XSign kernel: i915 0000:00:02.0: irq 43 for MSI/MSI-X
    10月 23 09:19:06 XSign kernel: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
    10月 23 09:19:06 XSign kernel: [drm] Driver supports precise vblank timestamp query.
    10月 23 09:19:06 XSign kernel: vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
    10月 23 09:19:06 XSign kernel: [drm] initialized overlay support
    10月 23 09:19:06 XSign kernel: intel_rng: FWH not detected
    10月 23 09:19:06 XSign kernel: fbcon: inteldrmfb (fb0) is primary device
    10月 23 09:19:06 XSign kernel: Console: switching to colour frame buffer device 240x67
    10月 23 09:19:06 XSign kernel: i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
    10月 23 09:19:06 XSign kernel: i915 0000:00:02.0: registered panic notifier
    10月 23 09:19:06 XSign kernel: i915: No ACPI video bus found
    10月 23 09:19:06 XSign kernel: [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
    10月 23 09:19:06 XSign kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
    10月 23 09:19:06 XSign kernel: input: PC Speaker as /devices/platform/pcspkr/input/input8
    10月 23 09:19:06 XSign kernel: snd_hda_intel 0000:00:1b.0: irq 44 for MSI/MSI-X
    10月 23 09:19:07 XSign kernel: leds_ss4200: no LED devices found
    10月 23 09:19:07 XSign kernel: microcode: CPU0 sig=0x6fb, pf=0x1, revision=0xb6
    10月 23 09:19:07 XSign kernel: iTCO_vendor_support: vendor-support=0
    10月 23 09:19:07 XSign kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
    10月 23 09:19:07 XSign kernel: iTCO_wdt: Found a ICH7 or ICH7R TCO device (Version=2, TCOBASE=0x0860)
    10月 23 09:19:07 XSign kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
    10月 23 09:19:07 XSign kernel: input: HDA Intel Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
    10月 23 09:19:07 XSign kernel: input: HDA Intel Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
    10月 23 09:19:07 XSign kernel: input: HDA Intel Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
    10月 23 09:19:07 XSign kernel: input: HDA Intel Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
    10月 23 09:19:07 XSign kernel: input: HDA Intel Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
    10月 23 09:19:07 XSign kernel: i801_smbus 0000:00:1f.3: SMBus using PCI Interrupt
    10月 23 09:19:07 XSign systemd[1]: Starting Sound Card.
    10月 23 09:19:07 XSign systemd[1]: Reached target Sound Card.
    10月 23 09:19:07 XSign kernel: microcode: CPU1 sig=0x6fb, pf=0x1, revision=0xb6
    10月 23 09:19:07 XSign kernel: microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
    10月 23 09:19:07 XSign kernel: gpio_ich: GPIO from 206 to 255 on gpio_ich
    10月 23 09:19:07 XSign kernel: coretemp coretemp.0: Using relative temperature scale!
    10月 23 09:19:07 XSign kernel: coretemp coretemp.0: Using relative temperature scale!
    10月 23 09:19:08 XSign systemd[1]: Found device ST3500418AS.
    10月 23 09:19:08 XSign systemd[1]: Starting File System Check on /dev/sdb5...
    10月 23 09:19:08 XSign systemd[1]: Found device ST3500410AS.
    10月 23 09:19:08 XSign systemd[1]: Starting File System Check on /dev/disk/by-uuid/86b99089-3393-4c20-bce8-0018e6cf5c85...
    10月 23 09:19:08 XSign systemd-fsck[211]: fsck: fsck.ntfs-3g: not found
    10月 23 09:19:08 XSign systemd-fsck[211]: fsck: error 2 while executing fsck.ntfs-3g for /dev/sdb5
    10月 23 09:19:08 XSign systemd-fsck[211]: fsck failed with error code 8.
    10月 23 09:19:08 XSign systemd-fsck[211]: Ignoring error.
    10月 23 09:19:08 XSign systemd[1]: Started File System Check on /dev/sdb5.
    10月 23 09:19:08 XSign systemd[1]: Mounting /mnt/sdb5...
    10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0]
    10月 23 09:19:08 XSign kernel: Result: hostbyte=0x00 driverbyte=0x08
    10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0]
    10月 23 09:19:08 XSign kernel: Sense Key : 0x5 [current]
    10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0]
    10月 23 09:19:08 XSign kernel: ASC=0x21 ASCQ=0x0
    10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0] CDB:
    10月 23 09:19:08 XSign kernel: cdb[0]=0x28: 28 00 00 00 04 00 00 00 02 00
    10月 23 09:19:08 XSign kernel: end_request: critical target error, dev sr0, sector 4096
    10月 23 09:19:08 XSign kernel: Buffer I/O error on device sr0, logical block 512
    10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0]
    10月 23 09:19:08 XSign kernel: Result: hostbyte=0x00 driverbyte=0x08
    10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0]
    10月 23 09:19:08 XSign kernel: Sense Key : 0x5 [current]
    10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0]
    10月 23 09:19:08 XSign kernel: ASC=0x21 ASCQ=0x0
    10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0] CDB:
    10月 23 09:19:08 XSign kernel: cdb[0]=0x28: 28 00 00 00 04 00 00 00 02 00
    10月 23 09:19:08 XSign kernel: end_request: critical target error, dev sr0, sector 4096
    10月 23 09:19:08 XSign kernel: Buffer I/O error on device sr0, logical block 512
    10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0]
    10月 23 09:19:08 XSign kernel: Result: hostbyte=0x00 driverbyte=0x08
    10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0]
    10月 23 09:19:08 XSign kernel: Sense Key : 0x5 [current]
    10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0]
    10月 23 09:19:08 XSign kernel: ASC=0x21 ASCQ=0x0
    10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0] CDB:
    10月 23 09:19:08 XSign kernel: cdb[0]=0x28: 28 00 00 00 04 00 00 00 02 00
    10月 23 09:19:08 XSign kernel: end_request: critical target error, dev sr0, sector 4096
    10月 23 09:19:08 XSign kernel: Buffer I/O error on device sr0, logical block 512
    10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0]
    10月 23 09:19:08 XSign kernel: Result: hostbyte=0x00 driverbyte=0x08
    10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0]
    10月 23 09:19:08 XSign kernel: Sense Key : 0x5 [current]
    10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0]
    10月 23 09:19:08 XSign kernel: ASC=0x21 ASCQ=0x0
    10月 23 09:19:08 XSign kernel: sr 4:0:0:0: [sr0] CDB:
    10月 23 09:19:08 XSign kernel: cdb[0]=0x28: 28 00 00 00 04 00 00 00 02 00
    10月 23 09:19:08 XSign kernel: end_request: critical target error, dev sr0, sector 4096
    10月 23 09:19:08 XSign kernel: Buffer I/O error on device sr0, logical block 512
    10月 23 09:19:08 XSign systemd-fsck[214]: Reiserfs super block in block 16 on 0x803 of format 3.6 with standard journal
    10月 23 09:

  • How to generate xml-file for SAP Fiori (UI add-on) with Solution Manager 7.0.1?

    Hello Guru,
    could you please help with my issue with Fiori Installation.
    We want to install SAP Fiori Front-End (GW+UI) on the Sandbox system with SAP Netweaver 7.3.1. (SP14)
    Gateway component (SAP GW CORE 200 SP10) was installed without any problems.
    But I need to install UI-add-on (NW UI Extensions v1.0) and when I try to install it via SAINT, transaction said me that I need to generate xml-file for it (as in General notes for UI add-on mentioned).
    But I have Solution Manager 7.0.1 and in MOPZ for this version I do not have option  "install Add-on" as it written in Guide for ui add-on installation.
    Could you please help me with advice how to generate xml-file for UI add-on installation on SolMan v.7.0.1?
    If where is no way, but only to upgrade Solution Manager, maybe somebody could give me xml-file for your system (for NW 731) and I will change it to my needs, I will be very grateful!
    Thanks in advance for any help!!!
    Bets regards,
    Natalia.

    Hello Guru,
    could you please help with my issue with Fiori Installation.
    We want to install SAP Fiori Front-End (GW+UI) on the Sandbox system with SAP Netweaver 7.3.1. (SP14)
    Gateway component (SAP GW CORE 200 SP10) was installed without any problems.
    But I need to install UI-add-on (NW UI Extensions v1.0) and when I try to install it via SAINT, transaction said me that I need to generate xml-file for it (as in General notes for UI add-on mentioned).
    But I have Solution Manager 7.0.1 and in MOPZ for this version I do not have option  "install Add-on" as it written in Guide for ui add-on installation.
    Could you please help me with advice how to generate xml-file for UI add-on installation on SolMan v.7.0.1?
    If where is no way, but only to upgrade Solution Manager, maybe somebody could give me xml-file for your system (for NW 731) and I will change it to my needs, I will be very grateful!
    Thanks in advance for any help!!!
    Bets regards,
    Natalia.

  • Fpga compilation problem (generating cores)

    Hello.  I am working in a lab trying to compile an FPGA for the cRIO 9074 module.  There are no erros when beginning the compilation, and it runs smoothly until it reaches the "generating cores" step.  At this point the following message repeats itself
    All runtime messages will be recorded in
    C:\NIFPGA\jobs\XR923g4_G4EhsMk\coregen.log
    Saved CGP file for project 'coregen'.
    Resolving generics for 'ReallyLongUniqueName_ReallyLongUniqueName'...
    Applying external generics to 'ReallyLongUniqueName_ReallyLongUniqueName'...
    Delivering associated files for 'ReallyLongUniqueName_ReallyLongUniqueName'...
    Generating implementation netlist for
    'ReallyLongUniqueName_ReallyLongUniqueName'...
    Running synthesis for 'ReallyLongUniqueName_ReallyLongUniqueName'
    This message repeats every 5 min or so for around 29 minutes, at which point the compiler stops, presenting the following error
    ERROR:sim - Cannot rename dependency database for library "mult_gen_v11_0", file
       is
       "_cg/_dbg/ReallyLongUniqueName_ReallyLongUniqueName_xsd/mult_gen_v11_0/hdpdep
       s.ref", Temporary database file
       "C:\NIFPGA\jobs\I1wyNri_G4EhsMk\core_NiLvXipFloat32Add\tmp\_cg\_dbg\ReallyLon
       gUniqueName_ReallyLongUniqueName_xsd\mult_gen_v11_0\xil_95296_48" will
       remain.  System error message is:  File exists
    ERROR:sim - Failed executing Tcl generator.
    ERROR:sim - Failed to generate 'ReallyLongUniqueName_ReallyLongUniqueName'.
       Failed executing Tcl generator.
    ERROR:sim:877 - Error found during execution of IP 'Floating-point v5.0'
    I have included the xilinx log.  For good measure I compiled an older FPGA we have running on a different chassis and it ran just fine, so it's not a problem with xilinx (at least I don't think it is).  I have spent the better part of two days wrestling with this issue and have found no viable solutions.  Any and all help would be greatly appreciated.  Thanks!
    Cheers,
    David
    Attachments:
    compilationfailure_log.txt ‏179 KB

    Check out this document from Xilinx. It may be caused by your antivirus not allowing access to the files that Xilinx needs to overwrite while compiling.

  • Generating Peak File for...

    Wow, this has been going on for 3-4 hours already.
    Unacceptable, and I can't find any reference to this process in the Adobe Docs for PP. I have no idea where it is in the process. Is it almost done? Does it have another 12 hours to go? What is the deal with this? I have not touched my computer in hours.
    I have a PP Project with about 10 bins with about 1 hour of video in each.
    Should I break my project down so I have 10 PP files with 1 hour of video per project?
    I was hoping to keep everything in one PP file, but that is looking like a really bad idea right now. I don't remember having to suffer through anything like with when working with Final Cut Pro.
    Will these stupid Peak Files be saved? Is there a chance they will get corrupt and have to regenerate? This took a whole half day, and more, since it's still ongoing. This is on my MBP 2.4GHz. If I want to move the files back and forth between my laptop and my Windows Core i7 920 desktop (I have Production Premium on both platforms), will I have to suffer the Peak File Generation everytime?
    All video was captured in OnLocation, straight from the camera. That part of the process seemed really cool. This part with the Peak File is really lame.
    Any tips on getting to a workable workflow with PP, or should I just bag it, and buy another editor (Final Cut Express would even probably do the simple cut edits I want to do) ? I do most everything in After Effects.

    count_schemula wrote:
    The solution? I'm going to edit on my windows desktop.
    OMG, what have I gotten myself into?
    Same problem on my PC. Premiere Pro 4.2 on Windows 7 64 bit. Freshly installed. All legit software.
    I made a new project, import all the video, and let it generate all peak files.
    It finishes. Close Premeire. Open Premiere... Generating Peak File for...
    My heart sinks so low.
    I delete the .pek files and the database files and in the preferences, I set it to save cache and database files to a folder within my project folder.
    It dutifully generates all new .pek file and database files. I watch it write them one by one. It does not write anything in the original Adobe shared cache folders. It completes. I quickly edit up one segment, just so I have some work to show for my 4 days of messing around with this.
    Close Premiere. Open Premiere.
    Generating Peak File for...
    I'm speechless.
    Footage was captured to disc using OnLocation on a Mac from a Panasonic AG-HVX200a via fireware.
    If you want to call me an idiot, point out where I'm not doing something right.
    If you want to blame my rig(s) just know that I push these systems hard daily with ZERO issues in other apps.
    I'm blaming Premiere at this point. Something about how this program works is just not right. In both cases it writes over already existing .pek files. I have 4 channels per clip, so 4 .pek files for every clip I have. It's towards 1000. pek files.

  • Crashing When "Generating Peak Files"

    Experts...
    I new in town, and to CS3.
    Premier CS3 is working just fine on my system with one major exception...
    Ecah time I import media I get a small progress bar in the bottom right corner of the status bar that reports "Generating Peak File for 123.avi" where 123.avi is the name of the file I have just imported.
    As this progress bar reaches completion Premier hangs. No error message, just becomes unresponsive.
    This is consistent for all imported media and very predictable, easy to replicate.
    Any ideas?

    Welcome! You will also find links to many free tutorials in the
    Premiere Pro Wiki that will quickly
    show you how things are done in PPro.
    Cheers
    Eddie
    Forum FAQ
    Premiere Pro Wiki
    - Over 250 frequently answered questions
    - Over 100 free tutorials
    - Maintained by editors like
    you

Maybe you are looking for

  • Error during BAPI_GOODSMVT_CREATE(during GR)

    Hi all, i am using BAPI_GOODSMVT_CREATE to do GR.In the selection screen of my program, i am inputting 1)PO number 2)material--MCU-FUS(I ENTERED) 3)vendor 4)delivery order 5)GR quantity--6000( i entered) After execution of my program , i am getting t

  • Distribute spacing value needs to be sticky

    The Distribute Spacing value needs to remain sticky based on the last value I gave it. If I have previously distributed a series of objects to a set spacing value and then set it back to Auto prior to distributing another series of objects the value

  • FrameSet in Wallaby

    j'ai une animation Flash a été fais avec flash CS3 et aprés je l'ai converti en cs5 pour la mettre en HTML5 avec Wallby mais j'ai trouvé une probleme et il m'indiqu ce Warning Unsupported feature: Actionscript Version Not Supported Context stack:   A

  • "Revert to Original" Grayed out

    I notice on all photos in my iPhoto '08 library that the "Revert to Original" item is grayed out in the menu. This appears for all photos, but I know the originals are in the system, as they can be found in Finder, in the unaltered state that I impor

  • USB Connect Cisco for Mac does not work

    I created a USB for Cisco Connect on my desktop with Windows XP but it will not work to connect a Mac to the Internet. When I insert the USB, the Connect Icon will not execute. Is there something special that has to be done?