Replication Log, PC Shutdown

If a computer is shutdown before replication has completed, does it show up in the replication log? If so, how does it show in the replication log?

Hi Jonathan,
No, a system shutdown won't be explicitly recorded in the dbremote output / console log. dbremote entries typically look like this between dbremote runs (shut down / start-up):
     I. 2014-04-24 16:41:06. Execution completed
     I. 2014-04-24 16:41:09. SQL Remote Message Agent Version 16.0.0.1824
System Shutdowns / Start-ups are recorded in the "System" Event log on Microsoft Windows:
     Control Panel > Administrative Tools > Event Viewer > System
Look for 'Kernel-General' entries:
     ===========================================
     Log Name:      System
     Source:        Microsoft-Windows-Kernel-General
     Date:          23/4/2014 5:08:31 PM
     Event ID:      13
     Task Category: None
     Level:         Information
     Keywords:     
     User:          N/A
     Computer:      hostname
     Description:
     The operating system is shutting down at system time 2014-04-23T21:08:31.001823500Z.
     ===========================================
Regards,
Jeff Albion
SAP Active Global Support

Similar Messages

  • Replication Log Reader stopped unexpectedly

    This morning our websites stopped serving pages.  Whilst investigating I notice that the Replication Sql LogReader had stopped running and was reporting the error:
    "SubSystem Message - Job 'XXX582060-XXXXX-1' (0x6D6877EFE4F8EA4D930F8C967FE49BE5), step
    2 - A time out occurred while waiting for memory resources to execute the query. Rerun the query."
    I have restarted the LogReader and it seems to be working fine but I'd really like to get to the bottom of why it stopped in the first place so I can prevent happening in the future.
    Any help would be great.
    Thanks
    Mike

    Check this blog -
    http://blogs.msdn.com/b/sqlqueryprocessing/archive/2006/11/14/query-execution-timeouts-in-sql-server-part-1-of-2.aspx
    Check your SQL Server error logs to see if you find any Memory related errors or Memory dumps. It looks like there was a memory crunch during the time forcing log reader to stop.
    Also make sure that you have configured your memory settings properly.
    Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

  • Asynchronous multimaster replication and DB shutdown

    Hi
    I have a question:
    What Happen if in replication environment (Asynch multimaster) master defenition site or other master site shutdown?
    Are transaction remained in deffered queue?

    Thank you, so I should write in documentation that shutdown Abort is forbidden

  • Replication : Directory Server shutdown while creating user

    Hi,
    We are trying to do a load test with multiple threads trying to create entries in LDAP Replication setup. The load test is being done using a in-house test tool which spawns multiple threads and uses a JAVA API provided by iPlanet Directory Server to create entries in Directory Server.
    The test runs fine in Single Directory Server setup. But when we repeat the same test by using a replicated setup (both Single Master as well as Multi Master) we face an issue as listed below:
    - First entry gets created and also replicated across
    - When the request for second entry is recieved , the directory server shuts down without any error in the log file.
    Any urgent help is highly appreciated.
    Type and Version : iPlanet Directory Server 5.1
    OS : Windows 2000 server
    Thanks in advance,
    Krishna Kumar

    Hi ,
    We are actually using iPlanet Directory Server 5.1 SP1 here.
    We had even tried SP2 for the above issue, still we are getting the above problem. Is there any other patches available for the above problem, please let us know about it.
    Thanks,
    Krishna Kumar

  • Replication Log

    Hi,
    Where can I see log of replication. I need to find out who ( User name) actually has performed the replication in the system. Can you please let me know where can I see it.
    Thanks.

    Check this blog -
    http://blogs.msdn.com/b/sqlqueryprocessing/archive/2006/11/14/query-execution-timeouts-in-sql-server-part-1-of-2.aspx
    Check your SQL Server error logs to see if you find any Memory related errors or Memory dumps. It looks like there was a memory crunch during the time forcing log reader to stop.
    Also make sure that you have configured your memory settings properly.
    Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

  • Transaction log usage grows due to replication even if I don't use replication at all

    Hi
    The transaction log usage keeps growing a lot on my user database since few days back. the database is in full recovery model and I do transaction log backups every 10 minutes. The DB was part of Database Mirroring but I removed it. The usage was controlled
    for many years by the backups but something happened that is messing up the transaction log
    this is DBCC OPENTRAN
    Transaction information for database 'MyDB'.
    Replicated Transaction Information:
            Oldest distributed LSN     : (0:0:0)
            Oldest non-distributed LSN : (1450911:6823:1)
    DBCC execution completed. If DBCC printed error messages, contact your system administrator.
    log_reuse_wait_desc reports REPLICATION
    the funny thing is that I am not using replication at all. I am using CDC.
    To reduce the transaction log usage I run below statement every day since the problem started
    EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, 
        @numtrans = 0, @time = 0, @reset = 1
    Any idea what should I do to solve this problem and be back on a normal situation?
    BTW, The server is SQL 2012 (11.0.2383)
    Thanks
    Javier Villegas |
    @javier_vill | http://sql-javier-villegas.blogspot.com/
    Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you

    CDC uses the replication log reader agent and if you manually ran sp_repldone like that you lost information in your CDC capture.  If the capture job can't keep up with the workload or is not running for CDC, you would have the exact problems you describe.
     If you execute sp_repldone like that, you might as well disable CDC.
    http://technet.microsoft.com/en-us/library/dd266396(v=sql.100).aspx
    Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
    My Blog |
    Twitter |
    MVP Profile
    Training |
    Consulting |
    Become a SQLskills Insider
    Troubleshooting SQL Server

  • 1.4 Logging (shutdown hook question really)

    If I have a handler configured and log a record inside a thread running as a shutdown hook, more times than not I get nothing in the log file (or console, or wherever) and have to resort to System.err.println().
    Now, from studying the code for LogManager this turns out to be the result of the inner Cleaner thread (which is the log managers shutdown hook) calling reset() on the manager.
    So, this question morphs itself into how to get my shutdown hook to run before the one that resets the log manager.
    Any ideas or adjsting the priority (order of execution) of shutdown hooks?

    Guys (silkm, trejkaz and the good doctor),
    That's for the input. Appreciate it.
    On shutdown hooks being bad design - interesting. In the case I'm thinking of, the entry point class for a distributed task manager (see http://forum.java.sun.com/thread.jsp?forum=4&thread=335843&tstart=0&trange=30) is "embedded" in consumer code and does indead have a clean shutdown method that we hope the consumer code will invoke before shutting itself down. But in the same was as the logging subsystem can not rely on it's consumer code to "do the right thing", we can't rely on our consumer code to behave itself. In addition, we do want to catch the case where an operator re-starts the consumer system (internal procedure demands unix processes are sent an interrupt rather than a kill). The code invoked by the clean shutdown and the caught shutdown persists (as XML) the state of the task manager which is read on re-start to perform recovery operations. Now, before you all dive in and say "save the state every time it changes" let me say that the state changes very rapidly and the I/O overhead of saving it is considerable. Also, having a background thread that persists state on a regular basis was considered, but it introduces the problem that it becomes different to gaurantee the validity of the persisted state.
    On setting the thread priority - that had occured to me and I shall be using this as one of my test cases to see what happens. As mentioned, the effects this has will vary by platform and VM. However, as the component in question will be running in a controlled environment we should be able to pick a configuration that works.
    On Linux threads and processes - Good point. But do unstarted threads have a process? This is significant to us as the target platforms for the task manager are Solaris and Linux.
    On java.lang.Runtime's implementation of shutdown hooks - I tend to agree that it's a bit simplistic. Maybe we should raise a change request to allow greater control over how hooks are executed.
    Thanks again and please chip in if you have any other ideas.

  • [SOLVED] shutdown log

    Hi, I've googled the heck out of this with no love. I'm getting a message on shutdwon that goes by so fast I can't read it. I've checked all logs with no results. Is there some way to log the shutdown?
    Last edited by oboedad55 (2011-11-09 17:33:17)

    falconindy wrote:I can't find the bug report, so the tl;dr version is: you have a swap partition which emits a CHANGED uevent when its disabled during shutdown. The event is handled by udev which immediately gets told to quit after receiving the event, and in turn, shuts down its children. One of these children is running blkid on the swap device that it received the CHANGED uevent for. The result is that you see the 'terminated' message for the udev child that's running blkid. In the end, it's harmless. Maybe some day I'll get around to implementing something like a --files-only flag for swapoff.
    Ah OK, falconindy, thanks for the reply. That makes sense. It wasn't causing a problem, but I like to have everything working properly.

  • Logmnr/capure error b'coz of corruption of redo log block

    Hi,
    We all know that capture process reads the REDO entries from redo log files or archived log files. Therefore we need to ahev db in ARCHIVELOG mode.
    In alert log file, I found error saying :
    Creating archive destination LOG_ARCHIVE_DEST_1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\LOCATION01\1_36.ARC'
    ARC0: Log corruption near block 66922 change 0 time ?
    ARC0: All Archive destinations made inactive due to error 354
    Fri Apr 04 12:57:44 2003
    Errors in file e:\oracle\admin\repf\bdump\trishul_arc0_1724.trc:
    ORA-00354: corrupt redo log block header
    ORA-00353: log corruption near block 66922 change 0 time 04/04/2003 11:05:40
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
    As a normal practice, we do have multiplexing of redo log files at diff location, but even that second copy of redo log is of no use to recover the redo log. This explains redo log could not be archived, since it can't be read. Same is true even for Logmnr process, it could not read the redo log file and it failed. Now, we have wae to recover from this situation (as far as DB is concern, not Stream Replication), since the shutdown after this error was IMMEDIATE causing checkpoing, and rollback/rollforward is not required during system startup. (No instance recovery) We can make db NOARCHIVELOG mode, drop that particular group, and create new one, and turn db to ARCHIVELOG mode This will certainly serve the purpose as far as consistency of DB is concern.
    Here is a catch for Stream Replication. The redo log that got corrupted must be having few transaction which are not being archived, and each will be having corresponding SCN. Now, Capture Process read the info sequentially in order of SCN. Few transaction are now missed, and Capture process can't jump to next SCN skipping few SCN in between. So, we have to re-instantiate the objects on the another system which has no erros, and start working on it. My botheration is what will happen to those missed transaction on the another database. It's absolete loss of the data. In development I can manage that. But in real time Production stage, this is a critical situation. How to recover from this situation to get back the corrupted info from redo log ?
    I have not dropped any of the log group yet. B'coz I would like to recover from this situation without LOSS of data.
    Thanx, & regards,
    Kamlesh Chaudhary
    Content of trace files :
    Dump file e:\oracle\admin\repf\bdump\trishul_arc0_1724.trc
    Fri Apr 04 12:57:31 2003
    ORACLE V9.2.0.2.1 - Production vsnsta=0
    vsnsql=12 vsnxtr=3
    Windows 2000 Version 5.0 Service Pack 2, CPU type 586
    Oracle9i Enterprise Edition Release 9.2.0.2.1 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.2.0 - Production
    Windows 2000 Version 5.0 Service Pack 2, CPU type 586
    Instance name: trishul
    Redo thread mounted by this instance: 1
    Oracle process number: 16
    Windows thread id: 1724, image: ORACLE.EXE
    *** SESSION ID:(13.1) 2003-04-04 12:57:31.000
    - Created archivelog as 'E:\ORACLE\ORADATA\REPF\ARCHIVE\LOCATION02\1_36.ARC'
    - Created archivelog as 'E:\ORACLE\ORADATA\REPF\ARCHIVE\LOCATION01\1_36.ARC'
    *** 2003-04-04 12:57:44.000
    ARC0: All Archive destinations made inactive due to error 354
    *** 2003-04-04 12:57:44.000
    kcrrfail: dest:2 err:354 force:0
    *** 2003-04-04 12:57:44.000
    kcrrfail: dest:1 err:354 force:0
    ORA-00354: corrupt redo log block header
    ORA-00353: log corruption near block 66922 change 0 time 04/04/2003 11:05:40
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
    *** 2003-04-04 12:57:44.000
    ARC0: Archiving not possible: error count exceeded
    ORA-16038: log 2 sequence# 36 cannot be archived
    ORA-00354: corrupt redo log block header
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
    ORA-16014: log 2 sequence# 36 not archived, no available destinations
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
    ORA-16014: log 2 sequence# 36 not archived, no available destinations
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
    ORA-16014: log 2 sequence# 36 not archived, no available destinations
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
    ORA-16014: log 2 sequence# 36 not archived, no available destinations
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
    ORA-16014: log 2 sequence# 36 not archived, no available destinations
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG
    Dump file e:\oracle\admin\repf\udump\trishul_cp01_2048.trc
    Fri Apr 04 12:57:27 2003
    ORACLE V9.2.0.2.1 - Production vsnsta=0
    vsnsql=12 vsnxtr=3
    Windows 2000 Version 5.0 Service Pack 2, CPU type 586
    Oracle9i Enterprise Edition Release 9.2.0.2.1 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.2.0 - Production
    Windows 2000 Version 5.0 Service Pack 2, CPU type 586
    Instance name: trishul
    Redo thread mounted by this instance: 1
    Oracle process number: 30
    Windows thread id: 2048, image: ORACLE.EXE (CP01)
    *** 2003-04-04 12:57:28.000
    *** SESSION ID:(27.42) 2003-04-04 12:57:27.000
    TLCR process death detected. Shutting down TLCR
    error 1280 in STREAMS process
    ORA-01280: Fatal LogMiner Error.
    OPIRIP: Uncaught error 447. Error stack:
    ORA-00447: fatal error in background process
    ORA-01280: Fatal LogMiner Error
    **********************

    I have the similar problem - I am using Steams environment, and have got this
    "ORA-00353: log corruption near block" errors in the alert.log file
    during capture the changes on the primary database, and Capture
    process became aborted after that.
    Was that transactions lost, or after i've started the Capture process
    again the were captured and send to the target database?
    Have anyone solved that problem?
    Can you help me with it?

  • [systemd] shutdown takes a long time

    Hello.
    It takes quite a long time for my system to shutdown. The systemd ArchWiki suggests to log the shutdown like this. I am not quite sure what to look for. I suspect that smplayer or deluged might be the problem. Am I right and furthermore what can I do about it?
    Thank you for your time.
    Here the shutdown log:
    [ 0.000000] Initializing cgroup subsys cpuset
    [ 0.000000] Initializing cgroup subsys cpu
    [ 0.000000] Linux version 3.5.3-1-ARCH (tobias@T-POWA-LX) (gcc version 4.7.1 20120721 (prerelease) (GCC) ) #1 SMP PREEMPT Sun Aug 26 09:14:51 CEST 2012
    [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=55614e59-14b9-47c5-a609-fd76662e6403 ro systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0 quiet
    [ 0.000000] e820: BIOS-provided physical RAM map:
    [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009bfff] usable
    [ 0.000000] BIOS-e820: [mem 0x000000000009c000-0x000000000009ffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000005ffeffff] usable
    [ 0.000000] BIOS-e820: [mem 0x000000005fff0000-0x000000005fff2fff] ACPI NVS
    [ 0.000000] BIOS-e820: [mem 0x000000005fff3000-0x000000005fffffff] ACPI data
    [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000ffffffff] reserved
    [ 0.000000] NX (Execute Disable) protection: active
    [ 0.000000] DMI 2.2 present.
    [ 0.000000] DMI: /MS-7030, BIOS 6.00 PG 11/10/2005
    [ 0.000000] e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
    [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
    [ 0.000000] AGP bridge at 00:00:00
    [ 0.000000] Aperture from AGP @ e0000000 old size 32 MB
    [ 0.000000] Aperture size 4096 MB (APSIZE 0) is not right, using settings from NB
    [ 0.000000] Aperture from AGP @ e0000000 size 32 MB (APSIZE 0)
    [ 0.000000] e820: last_pfn = 0x5fff0 max_arch_pfn = 0x400000000
    [ 0.000000] MTRR default type: uncachable
    [ 0.000000] MTRR fixed ranges enabled:
    [ 0.000000] 00000-9FFFF write-back
    [ 0.000000] A0000-BFFFF uncachable
    [ 0.000000] C0000-C7FFF write-protect
    [ 0.000000] C8000-FFFFF uncachable
    [ 0.000000] MTRR variable ranges enabled:
    [ 0.000000] 0 base 0000000000 mask FFC0000000 write-back
    [ 0.000000] 1 base 0040000000 mask FFE0000000 write-back
    [ 0.000000] 2 base 00E0000000 mask FFF0000000 write-combining
    [ 0.000000] 3 disabled
    [ 0.000000] 4 disabled
    [ 0.000000] 5 disabled
    [ 0.000000] 6 disabled
    [ 0.000000] 7 disabled
    [ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    [ 0.000000] found SMP MP-table at [mem 0x000f4fc0-0x000f4fcf] mapped at [ffff8800000f4fc0]
    [ 0.000000] initial memory mapped: [mem 0x00000000-0x1fffffff]
    [ 0.000000] Base memory trampoline at [ffff880000096000] 96000 size 24576
    [ 0.000000] init_memory_mapping: [mem 0x00000000-0x5ffeffff]
    [ 0.000000] [mem 0x00000000-0x5fdfffff] page 2M
    [ 0.000000] [mem 0x5fe00000-0x5ffeffff] page 4k
    [ 0.000000] kernel direct mapping tables up to 0x5ffeffff @ [mem 0x1fcfd000-0x1fffffff]
    [ 0.000000] log_buf_len: 1048576
    [ 0.000000] early log buf free: 521388(99%)
    [ 0.000000] RAMDISK: [mem 0x37a32000-0x37d10fff]
    [ 0.000000] ACPI: RSDP 00000000000f8eb0 00014 (v00 Nvidia)
    [ 0.000000] ACPI: RSDT 000000005fff3040 00034 (v01 Nvidia AWRDACPI 42302E31 AWRD 00000000)
    [ 0.000000] ACPI: FACP 000000005fff30c0 00074 (v01 Nvidia AWRDACPI 42302E31 AWRD 00000000)
    [ 0.000000] ACPI: DSDT 000000005fff3180 048C1 (v01 NVIDIA AWRDACPI 00001000 MSFT 0100000E)
    [ 0.000000] ACPI: FACS 000000005fff0000 00040
    [ 0.000000] ACPI: SSDT 000000005fff7b80 000D6 (v01 PTLTD POWERNOW 00000001 LTP 00000001)
    [ 0.000000] ACPI: SRAT 000000005fff7cc0 00090 (v01 AMD HAMMER 00000001 AMD 00000001)
    [ 0.000000] ACPI: APIC 000000005fff7ac0 0007C (v01 Nvidia AWRDACPI 42302E31 AWRD 00000000)
    [ 0.000000] ACPI: Local APIC address 0xfee00000
    [ 0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
    [ 0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x0009ffff]
    [ 0.000000] SRAT: Node 0 PXM 0 [mem 0x00100000-0x5fffffff]
    [ 0.000000] NUMA: Node 0 [mem 0x00000000-0x0009ffff] + [mem 0x00100000-0x5ffeffff] -> [mem 0x00000000-0x5ffeffff]
    [ 0.000000] Initmem setup node 0 [mem 0x00000000-0x5ffeffff]
    [ 0.000000] NODE_DATA [mem 0x5feec000-0x5feeffff]
    [ 0.000000] [ffffea0000000000-ffffea00017fffff] PMD -> [ffff88005de00000-ffff88005f5fffff] on node 0
    [ 0.000000] Zone ranges:
    [ 0.000000] DMA [mem 0x00010000-0x00ffffff]
    [ 0.000000] DMA32 [mem 0x01000000-0xffffffff]
    [ 0.000000] Normal empty
    [ 0.000000] Movable zone start for each node
    [ 0.000000] Early memory node ranges
    [ 0.000000] node 0: [mem 0x00010000-0x0009bfff]
    [ 0.000000] node 0: [mem 0x00100000-0x5ffeffff]
    [ 0.000000] On node 0 totalpages: 393084
    [ 0.000000] DMA zone: 64 pages used for memmap
    [ 0.000000] DMA zone: 6 pages reserved
    [ 0.000000] DMA zone: 3910 pages, LIFO batch:0
    [ 0.000000] DMA32 zone: 6080 pages used for memmap
    [ 0.000000] DMA32 zone: 383024 pages, LIFO batch:31
    [ 0.000000] Nvidia board detected. Ignoring ACPI timer override.
    [ 0.000000] If you got timer trouble try acpi_use_timer_override
    [ 0.000000] ACPI: PM-Timer IO Port: 0x4008
    [ 0.000000] ACPI: Local APIC address 0xfee00000
    [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled)
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
    [ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
    [ 0.000000] IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    [ 0.000000] ACPI: BIOS IRQ0 override ignored.
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
    [ 0.000000] ACPI: IRQ9 used by override.
    [ 0.000000] ACPI: IRQ14 used by override.
    [ 0.000000] ACPI: IRQ15 used by override.
    [ 0.000000] Using ACPI (MADT) for SMP configuration information
    [ 0.000000] SMP: Allowing 2 CPUs, 1 hotplug CPUs
    [ 0.000000] nr_irqs_gsi: 40
    [ 0.000000] PM: Registered nosave memory: 000000000009c000 - 00000000000a0000
    [ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
    [ 0.000000] PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
    [ 0.000000] e820: [mem 0x60000000-0xfebfffff] available for PCI devices
    [ 0.000000] Booting paravirtualized kernel on bare hardware
    [ 0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:2 nr_node_ids:1
    [ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff88005fc00000 s83392 r8192 d23104 u1048576
    [ 0.000000] pcpu-alloc: s83392 r8192 d23104 u1048576 alloc=1*2097152
    [ 0.000000] pcpu-alloc: [0] 0 1
    [ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 386934
    [ 0.000000] Policy zone: DMA32
    [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=55614e59-14b9-47c5-a609-fd76662e6403 ro systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0 quiet
    [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
    [ 0.000000] __ex_table already sorted, skipping sort
    [ 0.000000] Checking aperture...
    [ 0.000000] AGP bridge at 00:00:00
    [ 0.000000] Aperture from AGP @ e0000000 old size 32 MB
    [ 0.000000] Aperture size 4096 MB (APSIZE 0) is not right, using settings from NB
    [ 0.000000] Aperture from AGP @ e0000000 size 32 MB (APSIZE 0)
    [ 0.000000] Node 0: aperture @ e0000000 size 256 MB
    [ 0.000000] Memory: 1532356k/1572800k available (4635k kernel code, 464k absent, 39980k reserved, 4212k data, 756k init)
    [ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
    [ 0.000000] Preemptible hierarchical RCU implementation.
    [ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
    [ 0.000000] Dump stacks of tasks blocking RCU-preempt GP.
    [ 0.000000] NR_IRQS:4352 nr_irqs:512 16
    [ 0.000000] spurious 8259A interrupt: IRQ7.
    [ 0.000000] Console: colour dummy device 80x25
    [ 0.000000] console [tty0] enabled
    [ 0.000000] allocated 6291456 bytes of page_cgroup
    [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
    [ 0.000000] Fast TSC calibration using PIT
    [ 0.000000] Detected 2009.231 MHz processor.
    [ 0.000000] Marking TSC unstable due to TSCs unsynchronized
    [ 0.006673] Calibrating delay loop (skipped), value calculated using timer frequency.. 4020.89 BogoMIPS (lpj=6697436)
    [ 0.006678] pid_max: default: 32768 minimum: 301
    [ 0.006716] Security Framework initialized
    [ 0.006725] AppArmor: AppArmor disabled by boot time parameter
    [ 0.006963] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
    [ 0.010848] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
    [ 0.012136] Mount-cache hash table entries: 256
    [ 0.012496] Initializing cgroup subsys cpuacct
    [ 0.012500] Initializing cgroup subsys memory
    [ 0.012520] Initializing cgroup subsys devices
    [ 0.012522] Initializing cgroup subsys freezer
    [ 0.012524] Initializing cgroup subsys net_cls
    [ 0.012526] Initializing cgroup subsys blkio
    [ 0.012564] tseg: 0000000000
    [ 0.012585] mce: CPU supports 5 MCE banks
    [ 0.012635] SMP alternatives: switching to UP code
    [ 0.018800] ACPI: Core revision 20120320
    [ 0.022927] ftrace: allocating 17956 entries in 71 pages
    [ 0.030518] ..TIMER: vector=0x30 apic1=0 pin1=0 apic2=-1 pin2=-1
    [ 0.064541] CPU0: AMD Athlon(tm) 64 Processor 3000+ stepping 00
    [ 0.066663] Performance Events: AMD PMU driver.
    [ 0.066663] ... version: 0
    [ 0.066663] ... bit width: 48
    [ 0.066663] ... generic registers: 4
    [ 0.066663] ... value mask: 0000ffffffffffff
    [ 0.066663] ... max period: 00007fffffffffff
    [ 0.066663] ... fixed-purpose events: 0
    [ 0.066663] ... event mask: 000000000000000f
    [ 0.083576] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    [ 0.083636] Brought up 1 CPUs
    [ 0.083638] Total of 1 processors activated (4020.89 BogoMIPS).
    [ 0.084405] devtmpfs: initialized
    [ 0.086410] PM: Registering ACPI NVS region [mem 0x5fff0000-0x5fff2fff] (12288 bytes)
    [ 0.087408] NET: Registered protocol family 16
    [ 0.087567] node 0 link 0: io port [9000, ffff]
    [ 0.087570] TOM: 0000000060000000 aka 1536M
    [ 0.087573] node 0 link 0: mmio [a0000, bffff]
    [ 0.087577] node 0 link 0: mmio [d0000000, fe02ffff]
    [ 0.087580] bus: [00, 02] on node 0 link 0
    [ 0.087583] bus: 00 [io 0x0000-0xffff]
    [ 0.087585] bus: 00 [mem 0x000a0000-0x000bffff]
    [ 0.087587] bus: 00 [mem 0x60000000-0xfcffffffff]
    [ 0.087627] ACPI: bus type pci registered
    [ 0.087696] PCI: Using configuration type 1 for base access
    [ 0.088295] bio: create slab <bio-0> at 0
    [ 0.088374] ACPI: Added _OSI(Module Device)
    [ 0.088376] ACPI: Added _OSI(Processor Device)
    [ 0.088378] ACPI: Added _OSI(3.0 _SCP Extensions)
    [ 0.088380] ACPI: Added _OSI(Processor Aggregator Device)
    [ 0.089228] ACPI: EC: Look up EC in DSDT
    [ 0.093337] ACPI: Interpreter enabled
    [ 0.093342] ACPI: (supports S0 S1 S4 S5)
    [ 0.093368] ACPI: Using IOAPIC for interrupt routing
    [ 0.094190] ACPI: Power Resource [ISAV] (on)
    [ 0.099077] ACPI: No dock devices found.
    [ 0.099086] PCI: Ignoring host bridge windows from ACPI; if necessary, use "pci=use_crs" and report a bug
    [ 0.099148] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    [ 0.099226] pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7] (ignored)
    [ 0.099229] pci_root PNP0A03:00: host bridge window [io 0x0d00-0xffff] (ignored)
    [ 0.099233] pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff] (ignored)
    [ 0.099236] pci_root PNP0A03:00: host bridge window [mem 0x000c0000-0x000dffff] (ignored)
    [ 0.099238] pci_root PNP0A03:00: host bridge window [mem 0x60000000-0xfebfffff] (ignored)
    [ 0.099241] PCI: root bus 00: hardware-probed resources
    [ 0.099287] PCI host bridge to bus 0000:00
    [ 0.099291] pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
    [ 0.099293] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    [ 0.099296] pci_bus 0000:00: root bus resource [mem 0x60000000-0xfcffffffff]
    [ 0.099312] pci 0000:00:00.0: [10de:00e1] type 00 class 0x060000
    [ 0.099321] pci 0000:00:00.0: reg 10: [mem 0xe0000000-0xefffffff pref]
    [ 0.099381] pci 0000:00:01.0: [10de:00e0] type 00 class 0x060100
    [ 0.099413] pci 0000:00:01.1: [10de:00e4] type 00 class 0x0c0500
    [ 0.099420] pci 0000:00:01.1: reg 10: [io 0xfc00-0xfc1f]
    [ 0.099432] pci 0000:00:01.1: reg 20: [io 0x4c00-0x4c3f]
    [ 0.099437] pci 0000:00:01.1: reg 24: [io 0x4c40-0x4c7f]
    [ 0.099451] pci 0000:00:01.1: PME# supported from D3hot D3cold
    [ 0.099470] pci 0000:00:02.0: [10de:00e7] type 00 class 0x0c0310
    [ 0.099477] pci 0000:00:02.0: reg 10: [mem 0xfe02f000-0xfe02ffff]
    [ 0.099502] pci 0000:00:02.0: supports D1 D2
    [ 0.099504] pci 0000:00:02.0: PME# supported from D0 D1 D2 D3hot D3cold
    [ 0.099518] pci 0000:00:02.1: [10de:00e7] type 00 class 0x0c0310
    [ 0.099525] pci 0000:00:02.1: reg 10: [mem 0xfe02e000-0xfe02efff]
    [ 0.099550] pci 0000:00:02.1: supports D1 D2
    [ 0.099552] pci 0000:00:02.1: PME# supported from D0 D1 D2 D3hot D3cold
    [ 0.099567] pci 0000:00:02.2: [10de:00e8] type 00 class 0x0c0320
    [ 0.099575] pci 0000:00:02.2: reg 10: [mem 0xfe02d000-0xfe02d0ff]
    [ 0.099605] pci 0000:00:02.2: supports D1 D2
    [ 0.099607] pci 0000:00:02.2: PME# supported from D0 D1 D2 D3hot D3cold
    [ 0.099628] pci 0000:00:06.0: [10de:00ea] type 00 class 0x040100
    [ 0.099635] pci 0000:00:06.0: reg 10: [io 0xf000-0xf0ff]
    [ 0.099640] pci 0000:00:06.0: reg 14: [io 0xec00-0xec7f]
    [ 0.099645] pci 0000:00:06.0: reg 18: [mem 0xfe02c000-0xfe02cfff]
    [ 0.099665] pci 0000:00:06.0: supports D1 D2
    [ 0.099680] pci 0000:00:08.0: [10de:00e5] type 00 class 0x01018a
    [ 0.099696] pci 0000:00:08.0: reg 20: [io 0xe000-0xe00f]
    [ 0.099723] pci 0000:00:09.0: [10de:00ee] type 00 class 0x010185
    [ 0.099730] pci 0000:00:09.0: reg 10: [io 0x09e0-0x09e7]
    [ 0.099735] pci 0000:00:09.0: reg 14: [io 0x0be0-0x0be3]
    [ 0.099740] pci 0000:00:09.0: reg 18: [io 0x0960-0x0967]
    [ 0.099744] pci 0000:00:09.0: reg 1c: [io 0x0b60-0x0b63]
    [ 0.099749] pci 0000:00:09.0: reg 20: [io 0xcc00-0xcc0f]
    [ 0.099754] pci 0000:00:09.0: reg 24: [io 0xc800-0xc87f]
    [ 0.099779] pci 0000:00:0a.0: [10de:00e3] type 00 class 0x010185
    [ 0.099786] pci 0000:00:0a.0: reg 10: [io 0x09f0-0x09f7]
    [ 0.099791] pci 0000:00:0a.0: reg 14: [io 0x0bf0-0x0bf3]
    [ 0.099796] pci 0000:00:0a.0: reg 18: [io 0x0970-0x0977]
    [ 0.099801] pci 0000:00:0a.0: reg 1c: [io 0x0b70-0x0b73]
    [ 0.099806] pci 0000:00:0a.0: reg 20: [io 0xb400-0xb40f]
    [ 0.099810] pci 0000:00:0a.0: reg 24: [io 0xb000-0xb07f]
    [ 0.099834] pci 0000:00:0b.0: [10de:00e2] type 01 class 0x060400
    [ 0.099865] pci 0000:00:0e.0: [10de:00ed] type 01 class 0x060400
    [ 0.099892] pci 0000:00:18.0: [1022:1100] type 00 class 0x060000
    [ 0.099913] pci 0000:00:18.1: [1022:1101] type 00 class 0x060000
    [ 0.099931] pci 0000:00:18.2: [1022:1102] type 00 class 0x060000
    [ 0.099951] pci 0000:00:18.3: [1022:1103] type 00 class 0x060000
    [ 0.100003] pci 0000:01:00.0: [10de:0221] type 00 class 0x030000
    [ 0.100017] pci 0000:01:00.0: reg 10: [mem 0xfa000000-0xfaffffff]
    [ 0.100025] pci 0000:01:00.0: reg 14: [mem 0xd0000000-0xdfffffff pref]
    [ 0.100033] pci 0000:01:00.0: reg 18: [mem 0xfb000000-0xfbffffff]
    [ 0.100056] pci 0000:01:00.0: reg 30: [mem 0x00000000-0x0001ffff pref]
    [ 0.100111] pci 0000:00:0b.0: PCI bridge to [bus 01-01]
    [ 0.100115] pci 0000:00:0b.0: bridge window [io 0xa000-0xafff]
    [ 0.100119] pci 0000:00:0b.0: bridge window [mem 0xfa000000-0xfcffffff]
    [ 0.100123] pci 0000:00:0b.0: bridge window [mem 0xd0000000-0xdfffffff pref]
    [ 0.100147] pci 0000:02:07.0: [1814:0301] type 00 class 0x028000
    [ 0.100158] pci 0000:02:07.0: reg 10: [mem 0xfdff0000-0xfdff7fff]
    [ 0.100216] pci 0000:02:08.0: [10ec:8139] type 00 class 0x020000
    [ 0.100228] pci 0000:02:08.0: reg 10: [io 0x9c00-0x9cff]
    [ 0.100235] pci 0000:02:08.0: reg 14: [mem 0xfdfff000-0xfdfff0ff]
    [ 0.100260] pci 0000:02:08.0: reg 30: [mem 0x00000000-0x0000ffff pref]
    [ 0.100278] pci 0000:02:08.0: supports D1 D2
    [ 0.100280] pci 0000:02:08.0: PME# supported from D1 D2 D3hot D3cold
    [ 0.100298] pci 0000:02:09.0: [1106:3038] type 00 class 0x0c0300
    [ 0.100326] pci 0000:02:09.0: reg 20: [io 0x9800-0x981f]
    [ 0.100351] pci 0000:02:09.0: supports D1 D2
    [ 0.100354] pci 0000:02:09.0: PME# supported from D0 D1 D2 D3hot D3cold
    [ 0.100371] pci 0000:02:09.1: [1106:3038] type 00 class 0x0c0300
    [ 0.100399] pci 0000:02:09.1: reg 20: [io 0x9400-0x941f]
    [ 0.100424] pci 0000:02:09.1: supports D1 D2
    [ 0.100427] pci 0000:02:09.1: PME# supported from D0 D1 D2 D3hot D3cold
    [ 0.100445] pci 0000:02:09.2: [1106:3104] type 00 class 0x0c0320
    [ 0.100456] pci 0000:02:09.2: reg 10: [mem 0xfdffe000-0xfdffe0ff]
    [ 0.100499] pci 0000:02:09.2: supports D1 D2
    [ 0.100501] pci 0000:02:09.2: PME# supported from D0 D1 D2 D3hot D3cold
    [ 0.100527] pci 0000:00:0e.0: PCI bridge to [bus 02-02]
    [ 0.100531] pci 0000:00:0e.0: bridge window [io 0x9000-0x9fff]
    [ 0.100534] pci 0000:00:0e.0: bridge window [mem 0xfdf00000-0xfdffffff]
    [ 0.100537] pci 0000:00:0e.0: bridge window [mem 0xfde00000-0xfdefffff pref]
    [ 0.100546] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    [ 0.100629] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
    [ 0.100813] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
    [ 0.100901] pci0000:00: Unable to request _OSC control (_OSC support mask: 0x1e)
    [ 0.125942] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 *10 11 12 14 15)
    [ 0.125994] ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 5 6 7 10 *11 12 14 15)
    [ 0.126043] ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 *5 6 7 10 11 12 14 15)
    [ 0.126092] ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 5 6 7 *10 11 12 14 15)
    [ 0.126140] ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
    [ 0.126195] ACPI: PCI Interrupt Link [LUBA] (IRQs 3 4 5 6 7 *10 11 12 14 15)
    [ 0.126245] ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
    [ 0.126293] ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
    [ 0.126341] ACPI: PCI Interrupt Link [LAPU] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
    [ 0.126391] ACPI: PCI Interrupt Link [LACI] (IRQs 3 4 *5 6 7 10 11 12 14 15)
    [ 0.126440] ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 6 7 10 *11 12 14 15)
    [ 0.126489] ACPI: PCI Interrupt Link [LSMB] (IRQs 3 4 *5 6 7 10 11 12 14 15)
    [ 0.126538] ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 *5 6 7 10 11 12 14 15)
    [ 0.126591] ACPI: PCI Interrupt Link [LFIR] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
    [ 0.126640] ACPI: PCI Interrupt Link [L3CM] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
    [ 0.126697] ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
    [ 0.126753] ACPI: PCI Interrupt Link [LSID] (IRQs 3 4 5 6 7 *10 11 12 14 15)
    [ 0.126812] ACPI: PCI Interrupt Link [LFID] (IRQs 3 4 5 6 7 10 *11 12 14 15)
    [ 0.126889] ACPI: PCI Interrupt Link [APC1] (IRQs 16) *0
    [ 0.126950] ACPI: PCI Interrupt Link [APC2] (IRQs 17) *0
    [ 0.127010] ACPI: PCI Interrupt Link [APC3] (IRQs 18) *0
    [ 0.127070] ACPI: PCI Interrupt Link [APC4] (IRQs 19) *0
    [ 0.127110] ACPI: PCI Interrupt Link [APC5] (IRQs *16), disabled.
    [ 0.127183] ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22 23) *0
    [ 0.127250] ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22 23) *0
    [ 0.127316] ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22 23) *0, disabled.
    [ 0.127382] ACPI: PCI Interrupt Link [APCI] (IRQs 20 21 22 23) *0, disabled.
    [ 0.127449] ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22 23) *0
    [ 0.127515] ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22 23) *0
    [ 0.127581] ACPI: PCI Interrupt Link [APCS] (IRQs 20 21 22 23) *0
    [ 0.127647] ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22 23) *0
    [ 0.127713] ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22 23) *0, disabled.
    [ 0.127780] ACPI: PCI Interrupt Link [AP3C] (IRQs 20 21 22 23) *0, disabled.
    [ 0.127847] ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22 23) *0, disabled.
    [ 0.127919] ACPI: PCI Interrupt Link [APSI] (IRQs 20 21 22 23) *0
    [ 0.127991] ACPI: PCI Interrupt Link [APSJ] (IRQs 20 21 22 23) *0
    [ 0.128144] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
    [ 0.128148] vgaarb: loaded
    [ 0.128149] vgaarb: bridge control possible 0000:01:00.0
    [ 0.128204] PCI: Using ACPI for IRQ routing
    [ 0.128208] PCI: pci_cache_line_size set to 64 bytes
    [ 0.128221] pci 0000:00:00.0: address space collision: [mem 0xe0000000-0xefffffff pref] conflicts with GART [mem 0xe0000000-0xefffffff]
    [ 0.128280] e820: reserve RAM buffer [mem 0x0009c000-0x0009ffff]
    [ 0.128283] e820: reserve RAM buffer [mem 0x5fff0000-0x5fffffff]
    [ 0.128429] NetLabel: Initializing
    [ 0.128430] NetLabel: domain hash size = 128
    [ 0.128432] NetLabel: protocols = UNLABELED CIPSOv4
    [ 0.128453] NetLabel: unlabeled traffic allowed by default
    [ 0.139353] pnp: PnP ACPI init
    [ 0.139383] ACPI: bus type pnp registered
    [ 0.139432] pnp 00:00: [io 0x4000-0x407f]
    [ 0.139434] pnp 00:00: [io 0x4080-0x40ff]
    [ 0.139437] pnp 00:00: [io 0x4400-0x447f]
    [ 0.139439] pnp 00:00: [io 0x4480-0x44ff]
    [ 0.139441] pnp 00:00: [io 0x4800-0x487f]
    [ 0.139444] pnp 00:00: [io 0x4880-0x48ff]
    [ 0.139550] system 00:00: [io 0x4000-0x407f] has been reserved
    [ 0.139554] system 00:00: [io 0x4080-0x40ff] has been reserved
    [ 0.139557] system 00:00: [io 0x4400-0x447f] has been reserved
    [ 0.139560] system 00:00: [io 0x4480-0x44ff] has been reserved
    [ 0.139563] system 00:00: [io 0x4800-0x487f] has been reserved
    [ 0.139566] system 00:00: [io 0x4880-0x48ff] has been reserved
    [ 0.139572] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.139776] pnp 00:01: [mem 0x0009e000-0x000a1fff]
    [ 0.139779] pnp 00:01: [mem 0x000cec00-0x000cffff]
    [ 0.139781] pnp 00:01: [mem 0x000f0000-0x000fbfff]
    [ 0.139784] pnp 00:01: [mem 0x000fc000-0x000fffff]
    [ 0.139786] pnp 00:01: [mem 0x5fff0000-0x5fffffff]
    [ 0.139789] pnp 00:01: [mem 0xffff0000-0xffffffff]
    [ 0.139792] pnp 00:01: [mem 0x00000000-0x0009ffff]
    [ 0.139794] pnp 00:01: [mem 0x00100000-0x5ffeffff]
    [ 0.139797] pnp 00:01: [mem 0xfec00000-0xfec00fff]
    [ 0.139799] pnp 00:01: [mem 0xfee00000-0xfeefffff]
    [ 0.139802] pnp 00:01: [mem 0xfefff000-0xfeffffff]
    [ 0.139804] pnp 00:01: [mem 0xfff80000-0xfff80fff]
    [ 0.139807] pnp 00:01: [mem 0xfff90000-0xfffbffff]
    [ 0.139809] pnp 00:01: [mem 0xfffed000-0xfffeffff]
    [ 0.139815] pnp 00:01: disabling [mem 0x0009e000-0x000a1fff] because it overlaps 0000:00:00.0 BAR 0 [mem 0x00000000-0x0fffffff pref]
    [ 0.139819] pnp 00:01: disabling [mem 0x000cec00-0x000cffff] because it overlaps 0000:00:00.0 BAR 0 [mem 0x00000000-0x0fffffff pref]
    [ 0.139823] pnp 00:01: disabling [mem 0x000f0000-0x000fbfff] because it overlaps 0000:00:00.0 BAR 0 [mem 0x00000000-0x0fffffff pref]
    [ 0.139827] pnp 00:01: disabling [mem 0x000fc000-0x000fffff] because it overlaps 0000:00:00.0 BAR 0 [mem 0x00000000-0x0fffffff pref]
    [ 0.139830] pnp 00:01: disabling [mem 0x00000000-0x0009ffff] because it overlaps 0000:00:00.0 BAR 0 [mem 0x00000000-0x0fffffff pref]
    [ 0.139834] pnp 00:01: disabling [mem 0x00100000-0x5ffeffff] because it overlaps 0000:00:00.0 BAR 0 [mem 0x00000000-0x0fffffff pref]
    [ 0.139885] system 00:01: [mem 0x5fff0000-0x5fffffff] could not be reserved
    [ 0.139889] system 00:01: [mem 0xffff0000-0xffffffff] has been reserved
    [ 0.139892] system 00:01: [mem 0xfec00000-0xfec00fff] could not be reserved
    [ 0.139895] system 00:01: [mem 0xfee00000-0xfeefffff] has been reserved
    [ 0.139898] system 00:01: [mem 0xfefff000-0xfeffffff] has been reserved
    [ 0.139902] system 00:01: [mem 0xfff80000-0xfff80fff] has been reserved
    [ 0.139905] system 00:01: [mem 0xfff90000-0xfffbffff] has been reserved
    [ 0.139908] system 00:01: [mem 0xfffed000-0xfffeffff] has been reserved
    [ 0.139912] system 00:01: Plug and Play ACPI device, IDs PNP0c01 (active)
    [ 0.139976] pnp 00:02: [bus 00-ff]
    [ 0.140003] pnp 00:02: [io 0x0cf8-0x0cff]
    [ 0.140006] pnp 00:02: [io 0x0cf0-0x0cf3]
    [ 0.140009] pnp 00:02: [io 0x0000-0x0cf7 window]
    [ 0.140011] pnp 00:02: [io 0x0d00-0xffff window]
    [ 0.140014] pnp 00:02: [mem 0x000a0000-0x000bffff window]
    [ 0.140017] pnp 00:02: [mem 0x000c0000-0x000dffff window]
    [ 0.140020] pnp 00:02: [mem 0x60000000-0xfebfffff window]
    [ 0.140101] pnp 00:02: Plug and Play ACPI device, IDs PNP0a03 (active)
    [ 0.140629] pnp 00:03: [io 0x0010-0x001f]
    [ 0.140631] pnp 00:03: [io 0x0022-0x003f]
    [ 0.140634] pnp 00:03: [io 0x0044-0x005f]
    [ 0.140636] pnp 00:03: [io 0x0062-0x0063]
    [ 0.140639] pnp 00:03: [io 0x0065-0x006f]
    [ 0.140641] pnp 00:03: [io 0x0074-0x007f]
    [ 0.140644] pnp 00:03: [io 0x0091-0x0093]
    [ 0.140646] pnp 00:03: [io 0x00a2-0x00bf]
    [ 0.140648] pnp 00:03: [io 0x00e0-0x00ef]
    [ 0.140651] pnp 00:03: [io 0x0b78-0x0b7b]
    [ 0.140653] pnp 00:03: [io 0x0f78-0x0f7b]
    [ 0.140656] pnp 00:03: [io 0x0a78-0x0a7b]
    [ 0.140658] pnp 00:03: [io 0x0e78-0x0e7b]
    [ 0.140660] pnp 00:03: [io 0x0bbc-0x0bbf]
    [ 0.140663] pnp 00:03: [io 0x0fbc-0x0fbf]
    [ 0.140665] pnp 00:03: [io 0x04d0-0x04d1]
    [ 0.140741] system 00:03: [io 0x0b78-0x0b7b] has been reserved
    [ 0.140744] system 00:03: [io 0x0f78-0x0f7b] has been reserved
    [ 0.140748] system 00:03: [io 0x0a78-0x0a7b] has been reserved
    [ 0.140751] system 00:03: [io 0x0e78-0x0e7b] has been reserved
    [ 0.140754] system 00:03: [io 0x0bbc-0x0bbf] has been reserved
    [ 0.140757] system 00:03: [io 0x0fbc-0x0fbf] has been reserved
    [ 0.140760] system 00:03: [io 0x04d0-0x04d1] has been reserved
    [ 0.140763] system 00:03: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.140777] pnp 00:04: [dma 4]
    [ 0.140780] pnp 00:04: [io 0x0000-0x000f]
    [ 0.140782] pnp 00:04: [io 0x0080-0x0090]
    [ 0.140785] pnp 00:04: [io 0x0094-0x009f]
    [ 0.140787] pnp 00:04: [io 0x00c0-0x00df]
    [ 0.140832] pnp 00:04: Plug and Play ACPI device, IDs PNP0200 (active)
    [ 0.140844] pnp 00:05: [io 0x0070-0x0073]
    [ 0.140862] pnp 00:05: [irq 8]
    [ 0.140904] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
    [ 0.140914] pnp 00:06: [io 0x0061]
    [ 0.140959] pnp 00:06: Plug and Play ACPI device, IDs PNP0800 (active)
    [ 0.140969] pnp 00:07: [io 0x00f0-0x00ff]
    [ 0.140976] pnp 00:07: [irq 13]
    [ 0.141019] pnp 00:07: Plug and Play ACPI device, IDs PNP0c04 (active)
    [ 0.141243] pnp 00:08: [io 0x03f8-0x03ff]
    [ 0.141251] pnp 00:08: [irq 4]
    [ 0.141340] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
    [ 0.141514] pnp 00:09: [io 0x02f8-0x02ff]
    [ 0.141522] pnp 00:09: [irq 3]
    [ 0.141596] pnp 00:09: Plug and Play ACPI device, IDs PNP0501 (active)
    [ 0.141881] pnp 00:0a: [io 0x0378-0x037f]
    [ 0.141883] pnp 00:0a: [io 0x0778-0x077b]
    [ 0.141890] pnp 00:0a: [irq 7]
    [ 0.141960] pnp 00:0a: Plug and Play ACPI device, IDs PNP0400 (active)
    [ 0.142046] pnp 00:0b: [io 0x0060]
    [ 0.142049] pnp 00:0b: [io 0x0064]
    [ 0.142055] pnp 00:0b: [irq 1]
    [ 0.142106] pnp 00:0b: Plug and Play ACPI device, IDs PNP0303 PNP030b (active)
    [ 0.142129] pnp: PnP ACPI: found 12 devices
    [ 0.142131] ACPI: ACPI bus type pnp unregistered
    [ 0.148689] Switching to clocksource acpi_pm
    [ 0.148760] pci 0000:01:00.0: BAR 6: assigned [mem 0xfc000000-0xfc01ffff pref]
    [ 0.148765] pci 0000:00:0b.0: PCI bridge to [bus 01-01]
    [ 0.148769] pci 0000:00:0b.0: bridge window [io 0xa000-0xafff]
    [ 0.148774] pci 0000:00:0b.0: bridge window [mem 0xfa000000-0xfcffffff]
    [ 0.148778] pci 0000:00:0b.0: bridge window [mem 0xd0000000-0xdfffffff pref]
    [ 0.148787] pci 0000:02:08.0: BAR 6: assigned [mem 0xfde00000-0xfde0ffff pref]
    [ 0.148790] pci 0000:00:0e.0: PCI bridge to [bus 02-02]
    [ 0.148793] pci 0000:00:0e.0: bridge window [io 0x9000-0x9fff]
    [ 0.148796] pci 0000:00:0e.0: bridge window [mem 0xfdf00000-0xfdffffff]
    [ 0.148799] pci 0000:00:0e.0: bridge window [mem 0xfde00000-0xfdefffff pref]
    [ 0.148814] pci 0000:00:0e.0: setting latency timer to 64
    [ 0.148818] pci_bus 0000:00: resource 4 [io 0x0000-0xffff]
    [ 0.148821] pci_bus 0000:00: resource 5 [mem 0x000a0000-0x000bffff]
    [ 0.148824] pci_bus 0000:00: resource 6 [mem 0x60000000-0xfcffffffff]
    [ 0.148827] pci_bus 0000:01: resource 0 [io 0xa000-0xafff]
    [ 0.148829] pci_bus 0000:01: resource 1 [mem 0xfa000000-0xfcffffff]
    [ 0.148832] pci_bus 0000:01: resource 2 [mem 0xd0000000-0xdfffffff pref]
    [ 0.148835] pci_bus 0000:02: resource 0 [io 0x9000-0x9fff]
    [ 0.148837] pci_bus 0000:02: resource 1 [mem 0xfdf00000-0xfdffffff]
    [ 0.148840] pci_bus 0000:02: resource 2 [mem 0xfde00000-0xfdefffff pref]
    [ 0.148906] NET: Registered protocol family 2
    [ 0.149029] IP route cache hash table entries: 65536 (order: 7, 524288 bytes)
    [ 0.149029] TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
    [ 0.153406] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
    [ 0.154706] TCP: Hash tables configured (established 262144 bind 65536)
    [ 0.154710] TCP: reno registered
    [ 0.154724] UDP hash table entries: 1024 (order: 3, 32768 bytes)
    [ 0.154769] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
    [ 0.154934] NET: Registered protocol family 1
    [ 0.155185] ACPI: PCI Interrupt Link [APCF] enabled at IRQ 23
    [ 0.223475] ACPI: PCI Interrupt Link [APCG] enabled at IRQ 22
    [ 0.290128] ACPI: PCI Interrupt Link [APCL] enabled at IRQ 21
    [ 0.290189] pci 0000:01:00.0: Boot video device
    [ 0.290265] ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
    [ 0.290348] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
    [ 0.290425] ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
    [ 0.290445] PCI: CLS 32 bytes, default 64
    [ 0.290526] Unpacking initramfs...
    [ 0.372340] Freeing initrd memory: 2940k freed
    [ 0.379476] agpgart-amd64 0000:00:00.0: AGP bridge [10de/00e1]
    [ 0.379485] agpgart-amd64 0000:00:00.0: aperture size 4096 MB is not right, using settings from NB
    [ 0.379493] agpgart-amd64 0000:00:00.0: setting up Nforce3 AGP
    [ 0.388295] agpgart-amd64 0000:00:00.0: AGP aperture is 256M @ 0xe0000000
    [ 0.388742] audit: initializing netlink socket (disabled)
    [ 0.388762] type=2000 audit(1346927638.386:1): initialized
    [ 0.402840] HugeTLB registered 2 MB page size, pre-allocated 0 pages
    [ 0.405016] VFS: Disk quotas dquot_6.5.2
    [ 0.405085] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    [ 0.405228] msgmni has been set to 2998
    [ 0.405471] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    [ 0.405502] io scheduler noop registered
    [ 0.405504] io scheduler deadline registered
    [ 0.405574] io scheduler cfq registered (default)
    [ 0.412567] vesafb: mode is 1280x1024x32, linelength=5120, pages=0
    [ 0.412569] vesafb: scrolling: redraw
    [ 0.412572] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
    [ 0.412814] vesafb: framebuffer at 0xd0000000, mapped to 0xffffc90000900000, using 5120k, total 5120k
    [ 0.475467] Console: switching to colour frame buffer device 160x64
    [ 0.537946] fb0: VESA VGA frame buffer device
    [ 0.538002] GHES: HEST is not enabled!
    [ 0.538068] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    [ 0.558511] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    [ 0.578950] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
    [ 0.599584] 00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    [ 0.620075] 00:09: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
    [ 0.620233] Linux agpgart interface v0.103
    [ 0.620290] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
    [ 0.620292] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
    [ 0.620995] serio: i8042 KBD port at 0x60,0x64 irq 1
    [ 0.621096] mousedev: PS/2 mouse device common for all mice
    [ 0.621204] rtc_cmos 00:05: RTC can wake from S4
    [ 0.621333] rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0
    [ 0.621357] rtc0: alarms up to one year, y3k, 242 bytes nvram
    [ 0.621367] cpuidle: using governor ladder
    [ 0.621370] cpuidle: using governor menu
    [ 0.621586] drop_monitor: Initializing network drop monitor service
    [ 0.621691] TCP: cubic registered
    [ 0.621838] NET: Registered protocol family 10
    [ 0.622084] NET: Registered protocol family 17
    [ 0.622099] Key type dns_resolver registered
    [ 0.622262] PM: Hibernation image not present or could not be loaded.
    [ 0.622282] registered taskstats version 1
    [ 0.622840] rtc_cmos 00:05: setting system clock to 2012-09-06 10:33:58 UTC (1346927638)
    [ 0.624542] Freeing unused kernel memory: 756k freed
    [ 0.625249] Write protecting the kernel read-only data: 8192k
    [ 0.631386] Freeing unused kernel memory: 1496k freed
    [ 0.635859] Freeing unused kernel memory: 616k freed
    [ 0.647736] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
    [ 0.654805] systemd-udevd[38]: starting version 189
    [ 0.730408] ACPI: bus type usb registered
    [ 0.730453] usbcore: registered new interface driver usbfs
    [ 0.730468] usbcore: registered new interface driver hub
    [ 0.735252] usbcore: registered new device driver usb
    [ 0.735879] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    [ 0.739107] SCSI subsystem initialized
    [ 0.746050] ehci_hcd 0000:00:02.2: setting latency timer to 64
    [ 0.746058] ehci_hcd 0000:00:02.2: EHCI Host Controller
    [ 0.746075] ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 1
    [ 0.746108] ehci_hcd 0000:00:02.2: debug port 1
    [ 0.746114] ehci_hcd 0000:00:02.2: cache line size of 32 is not supported
    [ 0.746141] ehci_hcd 0000:00:02.2: irq 21, io mem 0xfe02d000
    [ 0.749031] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    [ 0.750857] uhci_hcd: USB Universal Host Controller Interface driver
    [ 0.753402] ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00
    [ 0.753609] hub 1-0:1.0: USB hub found
    [ 0.753616] hub 1-0:1.0: 8 ports detected
    [ 0.753784] uhci_hcd 0000:02:09.0: UHCI Host Controller
    [ 0.753793] uhci_hcd 0000:02:09.0: new USB bus registered, assigned bus number 2
    [ 0.753839] uhci_hcd 0000:02:09.0: irq 19, io base 0x00009800
    [ 0.753984] hub 2-0:1.0: USB hub found
    [ 0.753989] hub 2-0:1.0: 2 ports detected
    [ 0.754706] libata version 3.00 loaded.
    [ 0.756811] ohci_hcd 0000:00:02.0: setting latency timer to 64
    [ 0.756817] ohci_hcd 0000:00:02.0: OHCI Host Controller
    [ 0.756829] ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 3
    [ 0.756869] ohci_hcd 0000:00:02.0: irq 23, io mem 0xfe02f000
    [ 0.757452] uhci_hcd 0000:02:09.1: UHCI Host Controller
    [ 0.757461] uhci_hcd 0000:02:09.1: new USB bus registered, assigned bus number 4
    [ 0.757493] uhci_hcd 0000:02:09.1: irq 16, io base 0x00009400
    [ 0.757704] hub 4-0:1.0: USB hub found
    [ 0.757711] hub 4-0:1.0: 2 ports detected
    [ 0.761428] ehci_hcd 0000:02:09.2: EHCI Host Controller
    [ 0.761447] ehci_hcd 0000:02:09.2: new USB bus registered, assigned bus number 5
    [ 0.761512] ehci_hcd 0000:02:09.2: irq 17, io mem 0xfdffe000
    [ 0.770064] ehci_hcd 0000:02:09.2: USB 2.0 started, EHCI 1.00
    [ 0.770287] hub 5-0:1.0: USB hub found
    [ 0.770294] hub 5-0:1.0: 4 ports detected
    [ 0.812239] hub 3-0:1.0: USB hub found
    [ 0.812251] hub 3-0:1.0: 4 ports detected
    [ 0.816572] ohci_hcd 0000:00:02.1: setting latency timer to 64
    [ 0.816577] ohci_hcd 0000:00:02.1: OHCI Host Controller
    [ 0.816589] ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 6
    [ 0.816630] ohci_hcd 0000:00:02.1: irq 22, io mem 0xfe02e000
    [ 0.868954] hub 6-0:1.0: USB hub found
    [ 0.868962] hub 6-0:1.0: 4 ports detected
    [ 0.873501] sata_nv 0000:00:09.0: version 3.5
    [ 0.873756] ACPI: PCI Interrupt Link [APSI] enabled at IRQ 20
    [ 0.873833] sata_nv 0000:00:09.0: setting latency timer to 64
    [ 0.874345] scsi0 : sata_nv
    [ 0.874497] scsi1 : sata_nv
    [ 0.874645] ata1: SATA max UDMA/133 cmd 0x9e0 ctl 0xbe0 bmdma 0xcc00 irq 20
    [ 0.874648] ata2: SATA max UDMA/133 cmd 0x960 ctl 0xb60 bmdma 0xcc08 irq 20
    [ 0.878342] ACPI: PCI Interrupt Link [APSJ] enabled at IRQ 23
    [ 0.878391] sata_nv 0000:00:0a.0: setting latency timer to 64
    [ 0.878840] scsi2 : sata_nv
    [ 0.878963] scsi3 : sata_nv
    [ 0.879110] ata3: SATA max UDMA/133 cmd 0x9f0 ctl 0xbf0 bmdma 0xb400 irq 23
    [ 0.879112] ata4: SATA max UDMA/133 cmd 0x970 ctl 0xb70 bmdma 0xb408 irq 23
    [ 0.886479] pata_acpi 0000:00:08.0: power state changed by ACPI to D0
    [ 0.886484] pata_acpi 0000:00:08.0: power state changed by ACPI to D0
    [ 0.886533] pata_acpi 0000:00:08.0: setting latency timer to 64
    [ 1.186695] ata1: SATA link down (SStatus 0 SControl 300)
    [ 1.343364] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    [ 1.350214] ata3.00: ATA-7: SAMSUNG SP1614C, SW100-34, max UDMA7
    [ 1.350217] ata3.00: 312581808 sectors, multi 16: LBA48
    [ 1.356871] ata3.00: configured for UDMA/133
    [ 1.370024] usb 4-1: new low-speed USB device number 2 using uhci_hcd
    [ 1.500024] ata2: SATA link down (SStatus 0 SControl 300)
    [ 1.500200] scsi 2:0:0:0: Direct-Access ATA SAMSUNG SP1614C SW10 PQ: 0 ANSI: 5
    [ 1.966704] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    [ 2.020180] ata4.00: ATA-8: WDC WD15EARS-00Z5B1, 80.00A80, max UDMA/133
    [ 2.020183] ata4.00: 2930277168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    [ 2.033588] ata4.00: configured for UDMA/133
    [ 2.033760] scsi 3:0:0:0: Direct-Access ATA WDC WD15EARS-00Z 80.0 PQ: 0 ANSI: 5
    [ 2.036921] pata_amd 0000:00:08.0: version 0.4.1
    [ 2.036948] pata_amd 0000:00:08.0: power state changed by ACPI to D0
    [ 2.036952] pata_amd 0000:00:08.0: power state changed by ACPI to D0
    [ 2.037017] pata_amd 0000:00:08.0: setting latency timer to 64
    [ 2.040074] scsi4 : pata_amd
    [ 2.041581] sd 2:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB)
    [ 2.041663] sd 2:0:0:0: [sda] Write Protect is off
    [ 2.041667] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
    [ 2.041692] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 2.042020] scsi5 : pata_amd
    [ 2.042592] ata5: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xe000 irq 14
    [ 2.042595] ata6: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xe008 irq 15
    [ 2.042887] sd 3:0:0:0: [sdb] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
    [ 2.042937] sd 3:0:0:0: [sdb] Write Protect is off
    [ 2.042941] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
    [ 2.042964] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 2.055764] sdb: sdb1
    [ 2.056082] sd 3:0:0:0: [sdb] Attached SCSI disk
    [ 2.056117] usbcore: registered new interface driver usbhid
    [ 2.056119] usbhid: USB HID core driver
    [ 2.073368] sda: sda1 sda2 sda3 sda4
    [ 2.073827] sd 2:0:0:0: [sda] Attached SCSI disk
    [ 2.200466] ata5.00: ATA-6: ST340810A, 3.39, max UDMA/100
    [ 2.200473] ata5.00: 78165360 sectors, multi 16: LBA
    [ 2.200484] ata5: nv_mode_filter: 0x3f39f&0x739f->0x739f, BIOS=0x7000 (0xc000c000) ACPI=0x701f (60:120:0x1b)
    [ 2.213741] ata5.00: configured for UDMA/33
    [ 2.213893] scsi 4:0:0:0: Direct-Access ATA ST340810A 3.39 PQ: 0 ANSI: 5
    [ 2.214133] sd 4:0:0:0: [sdc] 78165360 512-byte logical blocks: (40.0 GB/37.2 GiB)
    [ 2.214189] sd 4:0:0:0: [sdc] Write Protect is off
    [ 2.214193] sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00
    [ 2.214216] sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 2.244630] sdc: sdc1
    [ 2.244919] sd 4:0:0:0: [sdc] Attached SCSI disk
    [ 2.373623] ata6.00: ATAPI: _NEC DVD_RW ND-3540A, 1.01, max UDMA/33
    [ 2.373634] ata6: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc000c000) ACPI=0x701f (60:120:0x1b)
    [ 2.386892] ata6.00: configured for UDMA/33
    [ 2.388189] scsi 5:0:0:0: CD-ROM _NEC DVD_RW ND-3540A 1.01 PQ: 0 ANSI: 5
    [ 2.391609] input: OM as /devices/pci0000:00/0000:00:0e.0/0000:02:09.1/usb4/4-1/4-1:1.0/input/input1
    [ 2.393267] hid-generic 0003:04F3:0234.0001: input,hidraw0: USB HID v1.11 Mouse [OM] on usb-0000:02:09.1-1/input0
    [ 2.397693] sr0: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray
    [ 2.397702] cdrom: Uniform CD-ROM driver Revision: 3.20
    [ 2.397986] sr 5:0:0:0: Attached scsi CD-ROM sr0
    [ 3.150376] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
    [ 3.949356] systemd[1]: Successfully opened /dev/kmsg for logging.
    [ 3.949760] systemd[1]: Mounting cgroup to /sys/fs/cgroup/cpuset of type cgroup with options cpuset.
    [ 3.949905] systemd[1]: Mounting cgroup to /sys/fs/cgroup/cpu,cpuacct of type cgroup with options cpu,cpuacct.
    [ 3.950054] systemd[1]: Mounting cgroup to /sys/fs/cgroup/memory of type cgroup with options memory.
    [ 3.950167] systemd[1]: Mounting cgroup to /sys/fs/cgroup/devices of type cgroup with options devices.
    [ 3.953404] systemd[1]: Mounting cgroup to /sys/fs/cgroup/freezer of type cgroup with options freezer.
    [ 3.953500] systemd[1]: Mounting cgroup to /sys/fs/cgroup/net_cls of type cgroup with options net_cls.
    [ 3.953597] systemd[1]: Mounting cgroup to /sys/fs/cgroup/blkio of type cgroup with options blkio.
    [ 3.956761] systemd[1]: systemd 189 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ; arch)
    [ 3.979310] systemd[1]: Your kernel apparently lacks built-in autofs4 support. Might be a good idea to compile it in. We'll now try to work around this by loading the module...
    [ 4.144298] systemd[1]: Inserted module 'autofs4'
    [ 4.152053] systemd[1]: Set hostname to <box>.
    [ 4.157882] systemd[1]: Using cgroup controller name=systemd. File system hierarchy is at /sys/fs/cgroup/systemd/system.
    [ 4.157991] systemd[1]: Installed release agent.
    [ 4.158142] systemd[1]: Created root group.
    [ 4.158219] systemd[1]: Using notification socket @/org/freedesktop/systemd1/notify
    [ 4.158401] systemd[1]: Successfully created private D-Bus server.
    [ 4.184882] systemd[1]: Spawned /usr/lib/systemd/system-generators/systemd-cryptsetup-generator as 114
    [ 4.185117] systemd[1]: Spawned /usr/lib/systemd/system-generators/systemd-system-update-generator as 115
    [ 4.185365] systemd[1]: Spawned /usr/lib/systemd/system-generators/systemd-getty-generator as 116
    [ 4.185641] systemd[1]: Spawned /usr/lib/systemd/system-generators/systemd-fstab-generator as 117
    [ 4.255375] systemd[1]: /usr/lib/systemd/system-generators/systemd-cryptsetup-generator exited successfully.
    [ 4.255400] systemd[1]: /usr/lib/systemd/system-generators/systemd-system-update-generator exited successfully.
    [ 4.255408] systemd[1]: /usr/lib/systemd/system-generators/systemd-getty-generator exited successfully.
    [ 4.255416] systemd[1]: /usr/lib/systemd/system-generators/systemd-fstab-generator exited successfully.
    [ 4.313459] systemd[1]: Looking for unit files in:
    [ 4.313463] systemd[1]: /etc/systemd/system
    [ 4.313465] systemd[1]: /run/systemd/generator
    [ 4.313468] systemd[1]: /usr/lib/systemd/system
    [ 4.313471] systemd[1]: Disabled SysV init scripts and rcN.d links support
    [ 4.422041] systemd[1]: Failed to load configuration for syslog.service: No such file or directory
    [ 4.495651] systemd[1]: Failed to load configuration for plymouth-start.service: No such file or directory
    [ 4.564783] systemd[1]: Failed to load configuration for rc-local.service: No such file or directory
    [ 4.564799] systemd[1]: Failed to load configuration for plymouth-quit-wait.service: No such file or directory
    [ 4.709247] systemd[1]: Failed to load configuration for auditd.service: No such file or directory
    [ 4.752803] systemd[1]: -.mount changed dead -> mounted
    [ 4.752894] systemd[1]: Activating default unit: default.target
    [ 4.752901] systemd[1]: Trying to enqueue job graphical.target/start/replace
    [ 4.753079] systemd[1]: Installed new job graphical.target/start as 1
    [ 4.753085] systemd[1]: Installed new job multi-user.target/start as 2
    [ 4.753089] systemd[1]: Installed new job basic.target/start as 3
    [ 4.753094] systemd[1]: Installed new job sysinit.target/start as 4
    [ 4.753098] systemd[1]: Installed new job local-fs.target/start as 5
    [ 4.753102] systemd[1]: Installed new job home-hasardeur-Ext.mount/start as 6
    [ 4.753108] systemd[1]: Installed new job systemd-journald.socket/start as 7
    [ 4.753112] systemd[1]: Installed new job systemd-fsck@dev-disk-by\x2duuid-1A54880F5487EBB7.service/start as 9
    [ 4.753116] systemd[1]: Installed new job dev-disk-by\x2duuid-1A54880F5487EBB7.device/start as 10
    [ 4.753138] systemd[1]: Installed new job local-fs-pre.target/start as 11
    [ 4.753142] systemd[1]: Installed new job home-hasardeur-Space.mount/start as 14
    [ 4.753147] systemd[1]: Installed new job systemd-fsck@dev-disk-by\x2duuid-72290182\x2d7429\x2d4fb3\x2da421\x2d1e3bdf21dda9.service/start as 15
    [ 4.753151] systemd[1]: Installed new job dev-disk-by\x2duuid-72290182\x2d7429\x2d4fb3\x2da421\x2d1e3bdf21dda9.device/start as 16
    [ 4.753161] systemd[1]: Installed new job tmp.mount/start as 17
    [ 4.753164] systemd[1]: Installed new job systemd-fsck-root.service/start as 18
    [ 4.753168] systemd[1]: Installed new job systemd-remount-fs.service/start as 19
    [ 4.753172] systemd[1]: Installed new job swap.target/start as 20
    [ 4.753176] systemd[1]: Installed new job dev-disk-by\x2duuid-b5f8685d\x2d2706\x2d44fc\x2d882d\x2d662cc23e7c07.swap/start as 21
    [ 4.753181] systemd[1]: Installed new job dev-disk-by\x2duuid-b5f8685d\x2d2706\x2d44fc\x2d882d\x2d662cc23e7c07.device/start as 22
    [ 4.753191] systemd[1]: Installed new job systemd-udevd.service/start as 23
    [ 4.753195] systemd[1]: Installed new job systemd-udevd-control.socket/start as 24
    [ 4.753198] systemd[1]: Installed new job systemd-udevd-kernel.socket/start as 25
    [ 4.753202] systemd[1]: Installed new job dev-mqueue.mount/start as 26
    [ 4.753206] systemd[1]: Installed new job sys-kernel-config.mount/start as 27
    [ 4.753209] systemd[1]: Installed new job systemd-random-seed-load.service/start as 28
    [ 4.753213] systemd[1]: Installed new job systemd-ask-password-console.path/start as 29
    [ 4.753217] systemd[1]: Installed new job systemd-udev-trigger.service/start as 30
    [ 4.753220] systemd[1]: Installed new job sys-kernel-debug.mount/start as 31
    [ 4.753224] systemd[1]: Installed new job systemd-modules-load.service/start as 32
    [ 4.753228] systemd[1]: Installed new job sys-fs-fuse-connections.mount/start as 33
    [ 4.753231] systemd[1]: Installed new job proc-sys-fs-binfmt_misc.automount/start as 34
    [ 4.753235] systemd[1]: Installed new job systemd-journald.service/start as 35
    [ 4.753239] systemd[1]: Installed new job systemd-journal-flush.service/start as 36
    [ 4.753242] systemd[1]: Installed new job dev-hugepages.mount/start as 37
    [ 4.753246] systemd[1]: Installed new job systemd-tmpfiles-setup.service/start as 38
    [ 4.753249] systemd[1]: Installed new job cryptsetup.target/start as 39
    [ 4.753253] systemd[1]: Installed new job systemd-sysctl.service/start as 40
    [ 4.753256] systemd[1]: Installed new job systemd-vconsole-setup.service/start as 41
    [ 4.753260] systemd[1]: Installed new job systemd-binfmt.service/start as 42
    [ 4.753263] systemd[1]: Installed new job sockets.target/start as 45
    [ 4.753267] systemd[1]: Installed new job dbus.socket/start as 46
    [ 4.753271] systemd[1]: Installed new job systemd-initctl.socket/start as 47
    [ 4.753274] systemd[1]: Installed new job systemd-shutdownd.socket/start as 48
    [ 4.753278] systemd[1]: Installed new job alsa-restore.service/start as 49
    [ 4.753281] systemd[1]: Installed new job console-kit-log-system-start.service/start as 50
    [ 4.753285] systemd[1]: Installed new job systemd-tmpfiles-clean.timer/start as 51
    [ 4.753289] systemd[1]: Installed new job ntpd.service/start as 52
    [ 4.753292] systemd[1]: Installed new job remote-fs.target/start as 53
    [ 4.753296] systemd[1]: Installed new job netcfg.service/start as 54
    [ 4.753299] systemd[1]: Installed new job network.target/start as 55
    [ 4.753302] systemd[1]: Installed new job cronie.service/start as 56
    [ 4.753306] systemd[1]: Installed new job getty.target/start as 57
    [ 4.753309] systemd[1]: Installed new job [email protected]/start as 58
    [ 4.753313] systemd[1]: Installed new job systemd-ask-password-wall.path/start as 59
    [ 4.753316] systemd[1]: Installed new job dbus.service/start as 60
    [ 4.753320] systemd[1]: Installed new job systemd-logind.service/start as 61
    [ 4.753323] systemd[1]: Installed new job systemd-user-sessions.service/start as 62
    [ 4.753327] systemd[1]: Installed new job systemd-update-utmp-runlevel.service/start as 63
    [ 4.753331] systemd[1]: Installed new job lxdm.service/start as 66
    [ 4.753365] systemd[1]: Enqueued job graphical.target/start as 1
    [ 4.753380] systemd[1]: Loaded units and determined initial transaction in 594ms 940us.
    [ 4.753507] systemd[1]: Got SIGCHLD for process 113 (switch_root)
    [ 4.753580] systemd[1]: Child 113 died (code=exited, status=0/SUCCESS)
    [ 4.753667] systemd[1]: systemd-ask-password-wall.path changed dead -> waiting
    [ 4.753676] systemd[1]: Job systemd-ask-password-wall.path/start finished, result=done
    [ 4.753692] systemd[1]: remote-fs.target changed dead -> active
    [ 4.753700] systemd[1]: Job remote-fs.target/start finished, result=done
    [ 4.753747] systemd[1]: systemd-shutdownd.socket changed dead -> listening
    [ 4.753755] systemd[1]: Job systemd-shutdownd.socket/start finished, result=done
    [ 4.753786] systemd[1]: systemd-initctl.socket changed dead -> listening
    [ 4.753793] systemd[1]: Job systemd-initctl.socket/start finished, result=done
    [ 4.753807] systemd[1]: cryptsetup.target changed dead -> active
    [ 4.753815] systemd[1]: Job cryptsetup.target/start finished, result=done
    [ 4.753875] systemd[1]: Autofs kernel version 1.0
    [ 4.753969] systemd[1]: Autofs protocol version 5.2
    [ 4.753979] systemd[1]: proc-sys-fs-binfmt_misc.automount changed dead -> waiting
    [ 4.753987] systemd[1]: Job proc-sys-fs-binfmt_misc.automount/start finished, result=done
    [ 4.754036] systemd[1]: systemd-ask-password-console.path changed dead -> waiting
    [ 4.754044] systemd[1]: Job systemd-ask-password-console.path/start finished, result=done
    [ 4.754155] systemd[1]: systemd-udevd-kernel.socket changed dead -> listening
    [ 4.754164] systemd[1]: Job systemd-udevd-kernel.socket/start finished, result=done
    [ 4.754246] systemd[1]: systemd-udevd-control.socket changed dead -> listening
    [ 4.754254] systemd[1]: Job systemd-udevd-control.socket/start finished, result=done
    [ 4.754341] systemd[1]: systemd-journald.socket changed dead -> listening
    [ 4.754349] systemd[1]: Job systemd-journald.socket/start finished, result=done
    [ 4.754375] systemd[1]: Starting of systemd-fsck-root.service requested but condition failed. Ignoring.
    [ 4.754379] systemd[1]: Job systemd-fsck-root.service/start finished, result=done
    [ 4.754453] systemd[1]: About to execute: /usr/lib/systemd/systemd-remount-fs
    [ 4.758929] systemd[1]: Forked /usr/lib/systemd/systemd-remount-fs as 118
    [ 4.759050] systemd[1]: systemd-remount-fs.service changed dead -> start
    [ 4.759250] systemd[1]: About to execute: /usr/lib/systemd/systemd-udevd
    [ 4.826866] systemd[1]: Forked /usr/lib/systemd/systemd-udevd as 120
    [ 4.826993] systemd[1]: systemd-udevd.service changed dead -> start
    [ 4.827101] systemd[1]: About to execute: /bin/mount mqueue /dev/mqueue -t mqueue
    [ 4.828859] systemd[1]: Forked /bin/mount as 121
    [ 4.828923] systemd[1]: dev-mqueue.mount changed dead -> mounting
    [ 4.829234] systemd[1]: About to execute: /usr/bin/udevadm trigger --type=subsystems --action=add
    [ 4.833375] systemd[1]: Forked /usr/bin/udevadm as 122
    [ 4.833513] systemd[1]: systemd-udev-trigger.service changed dead -> start
    [ 4.833594] systemd[1]: About to execute: /bin/mount debugfs /sys/kernel/debug -t debugfs
    [ 4.834846] systemd[1]: Forked /bin/mount as 123
    [ 4.834893] systemd[1]: sys-kernel-debug.mount changed dead -> mounting
    [ 4.859660] systemd[1]: About to execute: /usr/lib/systemd/systemd-modules-load
    [ 4.860937] systemd[1]: Forked /usr/lib/systemd/systemd-modules-load as 124
    [ 4.861068] systemd[1]: systemd-modules-load.service changed dead -> start
    [ 4.861180] systemd[1]: About to execute: /bin/mount hugetlbfs /dev/hugepages -t hugetlbfs
    [ 4.863410] systemd[1]: Forked /bin/mount as 125
    [ 4.863451] systemd[1]: dev-hugepages.mount changed dead -> mounting
    [ 4.917003] systemd[1]: About to execute: /usr/lib/systemd/systemd-sysctl
    [ 4.918344] systemd[1]: Forked /usr/lib/systemd/systemd-sysctl as 126
    [ 4.918493] systemd[1]: systemd-sysctl.service changed dead -> start
    [ 4.918602] systemd[1]: About to execute: /usr/lib/systemd/systemd-vconsole-setup
    [ 4.920070] systemd[1]: Forked /usr/lib/systemd/systemd-vconsole-setup as 127
    [ 4.920224] systemd[1]: systemd-vconsole-setup.service changed dead -> start
    [ 4.926908] systemd[1]: Starting of systemd-binfmt.service requested but condition failed. Ignoring.
    [ 4.926918] systemd[1]: Job systemd-binfmt.service/start finished, result=done
    [ 4.927036] systemd[1]: About to execute: /usr/lib/systemd/systemd-journald
    [ 4.928214] systemd[1]: Forked /usr/lib/systemd/systemd-journald as 128
    [ 4.928417] systemd[1]: systemd-journald.service changed dead -> running
    [ 4.928436] systemd[1]: Job systemd-journald.service/start finished, result=done
    [ 4.928562] systemd[1]: Running GC...
    [ 4.929089] systemd[1]: Received SIGCHLD from PID 116 (n/a).
    [ 4.929352] systemd[1]: Incoming traffic on systemd-journald.socket
    [ 4.929370] systemd[1]: systemd-journald.socket changed listening -> running
    [ 4.957457] systemd[1]: Got notification message for unit systemd-udevd.service
    [ 4.957468] systemd[1]: systemd-udevd.service: Got message
    [ 4.957473] systemd[1]: systemd-udevd.service: got READY=1
    [ 4.957551] systemd[1]: systemd-udevd.service changed start -> running
    [ 4.957567] systemd[1]: Job systemd-udevd.service/start finished, result=done
    [ 4.957642] systemd-udevd[120]: starting version 189
    [ 5.064497] systemd[1]: Incoming traffic on systemd-udevd-kernel.socket
    [ 5.064520] systemd[1]: systemd-udevd-kernel.socket changed listening -> running
    [ 5.066198] systemd[1]: Received SIGCHLD from PID 122 (udevadm).
    [ 5.066234] systemd[1]: Got SIGCHLD for process 122 (udevadm)
    [ 5.066313] systemd[1]: Child 122 died (code=exited, status=0/SUCCESS)
    [ 5.066317] systemd[1]: Child 122 belongs to systemd-udev-trigger.service
    [ 5.066333] systemd[1]: systemd-udev-trigger.service: main process exited, code=exited, status=0
    [ 5.066341] systemd[1]: systemd-udev-trigger.service running next main command for state start
    [ 5.066359] systemd[1]: About to execute: /usr/bin/udevadm trigger --type=devices --action=add
    [ 5.067931] systemd[1]: Forked /usr/bin/udevadm as 130
    [ 5.083596] systemd[1]: Received SIGCHLD from PID 130 (udevadm).
    [ 5.083638] systemd[1]: Got SIGCHLD for process 130 (udevadm)
    [ 5.083717] systemd[1]: Child 130 died (code=exited, status=0/SUCCESS)
    [ 5.083721] systemd[1]: Child 130 belongs to systemd-udev-trigger.service
    [ 5.083737] systemd[1]: systemd-udev-trigger.service: main process exited, code=exited, status=0
    [ 5.084106] systemd[1]: systemd-udev-trigger.service changed start -> exited
    [ 5.084118] systemd[1]: Job systemd-udev-trigger.service/start finished, result=done
    [ 5.088748] systemd[1]: Received SIGCHLD from PID 126 (systemd-sysctl).
    [ 5.088779] systemd[1]: Got SIGCHLD for process 126 (systemd-sysctl)
    [ 5.088852] systemd[1]: Child 126 died (code=exited, status=0/SUCCESS)
    [ 5.088856] systemd[1]: Child 126 belongs to systemd-sysctl.service
    [ 5.088873] systemd[1]: systemd-sysctl.service: main process exited, code=exited, status=0
    [ 5.089199] systemd[1]: systemd-sysctl.service changed start -> exited
    [ 5.089210] systemd[1]: Job systemd-sysctl.service/start finished, result=done
    [ 5.336181] FS-Cache: Loaded
    [ 5.379562] RPC: Registered named UNIX socket transport module.
    [ 5.379567] RPC: Registered udp transport module.
    [ 5.379569] RPC: Registered tcp transport module.
    [ 5.379570] RPC: Registered tcp NFSv4.1 backchannel transport module.
    [ 5.585237] NFS: Registering the id_resolver key type
    [ 5.585264] Key type id_resolver registered
    [ 5.585266] Key type id_legacy registered
    [ 5.585278] FS-Cache: Netfs 'nfs' registered for caching
    [ 5.586108] systemd[1]: Received SIGCHLD from PID 124 (systemd-modules).
    [ 5.586146] systemd[1]: Got SIGCHLD for process 124 (systemd-modules)
    [ 5.586225] systemd[1]: Child 124 died (code=exited, status=0/SUCCESS)
    [ 5.586229] systemd[1]: Child 124 belongs to systemd-modules-load.service
    [ 5.586250] systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=0
    [ 5.586590] systemd[1]: systemd-modules-load.service changed start -> exited
    [ 5.586605] systemd[1]: Job systemd-modules-load.service/start finished, result=done
    [ 5.586717] systemd[1]: Starting of sys-kernel-config.mount requested but condition failed. Ignoring.
    [ 5.586722] systemd[1]: Job sys-kernel-config.mount/start finished, result=done
    [ 5.586742] systemd[1]: Starting of sys-fs-fuse-connections.mount requested but condition failed. Ignoring.
    [ 5.586746] systemd[1]: Job sys-fs-fuse-connections.mount/start finished, result=done
    [ 5.615412] systemd[1]: Accepted connection on private bus.
    [ 5.725920] systemd-journald[128]: Successfully opened /dev/kmsg for logging.
    [ 5.758577] systemd-journald[128]: Fixed max_use=75.1M max_size=9.3M min_size=64.0K keep_free=37.5M
    [ 5.758646] systemd-journald[128]: Reserving 17095 entries in hash table.
    [ 5.759414] systemd-journald[128]: Vacuuming...
    [ 5.759466] systemd-journald[128]: Flushing /dev/kmsg...
    [ 5.777632] systemd[1]: dev-hugepages.mount changed mounting -> mounting-done
    [ 5.777647] systemd[1]: Job dev-hugepages.mount/start finished, result=done
    [ 5.777687] systemd[1]: sys-kernel-debug.mount changed mounting -> mounting-done
    [ 5.777694] systemd[1]: Job sys-kernel-debug.mount/start finished, result=done
    [ 5.777716] systemd[1]: dev-mqueue.mount changed mounting -> mounting-done
    [ 5.777724] systemd[1]: Job dev-mqueue.mount/start finished, result=done
    [ 5.777819] systemd[1]: Received SIGCHLD from PID 125 (mount).
    [ 5.777855] systemd[1]: Got SIGCHLD for process 121 (mount)
    [ 5.777932] systemd[1]: Child 121 died (code=exited, status=0/SUCCESS)
    [ 5.777935] systemd[1]: Child 121 belongs to dev-mqueue.mount
    [ 5.777949] systemd[1]: dev-mqueue.mount mount process exited, code=exited status=0
    [ 5.777962] systemd[1]: dev-mqueue.mount changed mounting-done -> mounted
    [ 5.777998] systemd[1]: Got SIGCHLD for process 123 (mount)
    [ 5.778052] systemd[1]: Child 123 died (code=exited, status=0/SUCCESS)
    [ 5.778056] systemd[1]: Child 123 belongs to sys-kernel-debug.mount
    [ 5.778064] systemd[1]: sys-kernel-debug.mount mount process exited, code=exited status=0
    [ 5.778073] systemd[1]: sys-kernel-debug.mount changed mounting-done -> mounted
    [ 5.778104] systemd[1]: Got SIGCHLD for process 125 (mount)
    [ 5.778159] systemd[1]: Child 125 died (code=exited, status=0/SUCCESS)
    [ 5.778163] systemd[1]: Child 125 belongs to dev-hugepages.mount
    [ 5.778171] systemd[1]: dev-hugepages.mount mount process exited, code=exited status=0
    [ 5.778179] systemd[1]: dev-hugepages.mount changed mounting-done -> mounted
    [ 5.778270] systemd[1]: Accepted connection on private bus.
    [ 5.778429] systemd[1]: Accepted connection on private bus.
    [ 5.778509] systemd[1]: Accepted connection on private bus.
    [ 5.779032] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 5.779152] systemd[1]: systemd-udev-trigger.service: cgroup is empty
    [ 5.779481] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 5.779740] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 5.786928] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 5.790217] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 5.790280] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 5.790338] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 5.796880] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 5.807799] systemd-journald[128]: systemd-journald running as pid 128
    [ 5.808306] systemd[1]: Got notification message for unit systemd-journald.service
    [ 5.808312] systemd[1]: systemd-journald.service: Got message
    [ 5.808318] systemd[1]: systemd-journald.service: got STATUS=Processing requests...
    [ 6.246284] EXT4-fs (sda2): re-mounted. Opts: (null)
    [ 6.247294] systemd[1]: Received SIGCHLD from PID 118 (systemd-remount).
    [ 6.247328] systemd[1]: Got SIGCHLD for process 118 (systemd-remount)
    [ 6.247396] systemd[1]: Child 118 died (code=exited, status=0/SUCCESS)
    [ 6.247401] systemd[1]: Child 118 belongs to systemd-remount-fs.service
    [ 6.247419] systemd[1]: systemd-remount-fs.service: main process exited, code=exited, status=0
    [ 6.247721] systemd[1]: systemd-remount-fs.service changed start -> exited
    [ 6.247733] systemd[1]: Job systemd-remount-fs.service/start finished, result=done
    [ 6.247797] systemd[1]: local-fs-pre.target changed dead -> active
    [ 6.247805] systemd[1]: Job local-fs-pre.target/start finished, result=done
    [ 6.317889] systemd[1]: About to execute: /bin/mount tmpfs /tmp -t tmpfs -o nodev,nosuid
    [ 6.319475] systemd[1]: Forked /bin/mount as 140
    [ 6.319523] systemd[1]: tmp.mount changed dead -> mounting
    [ 6.319680] systemd[1]: About to execute: /usr/lib/systemd/systemd-random-seed load
    [ 6.323401] systemd[1]: Forked /usr/lib/systemd/systemd-random-seed as 141
    [ 6.323546] systemd[1]: systemd-random-seed-load.service changed dead -> start
    [ 6.347887] systemd[1]: tmp.mount changed mounting -> mounting-done
    [ 6.347901] systemd[1]: Job tmp.mount/start finished, result=done
    [ 6.348383] systemd[1]: Received SIGCHLD from PID 140 (mount).
    [ 6.348417] systemd[1]: Got SIGCHLD for process 140 (mount)
    [ 6.348489] systemd[1]: Child 140 died (code=exited, status=0/SUCCESS)
    [ 6.348493] systemd[1]: Child 140 belongs to tmp.mount
    [ 6.348504] systemd[1]: tmp.mount mount process exited, code=exited status=0
    [ 6.348515] systemd[1]: tmp.mount changed mounting-done -> mounted
    [ 6.349779] systemd[1]: Accepted connection on private bus.
    [ 6.350675] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Agent.Released() on /org/freedesktop/systemd1/agent
    [ 6.351301] systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
    [ 6.433691] systemd[1]: dev-ttyS2.device changed dead -> plugged
    [ 6.433715] systemd[1]: sys-devices-platform-serial8250-tty-ttyS2.device changed dead -> plugged
    [ 6.434762] systemd[1]: dev-ttyS3.device changed dead -> plugged
    [ 6.434780] systemd[1]: sys-devices-platform-serial8250-tty-ttyS3.device changed dead -> plugged
    [ 6.439475] systemd[1]: Received SIGCHLD from PID 141 (systemd-random-).
    [ 6.439513] systemd[1]: Got SIGCHLD for process 141 (systemd-random-)
    [ 6.439

    Should I file a bug report? If so, with Arch or upstream?

  • Event ID: 5014, 5004 The DFS Replication Service is stopping communication with partner / Error 1726 (The remote procedure call failed.)

    I'm replicating between two servers in two sites (Server A - Server 2012 R2 STD, Server B - Server 2008 R2) over a VPN (Sonicwall Firewall).  Though the initial replication seems to be
    happening it is very slow (the folder in question is less than 3GB).  I'm seeing these in the event viewer every few minutes:
    The DFS Replication service is stopping communication with partner PPIFTC for replication group FTC due to an error. The service will retry the connection periodically.
    Additional Information:
    Error: 1726 (The remote procedure call failed.)
    and then....
    The DFS Replication service successfully established an inbound connection with partner PPIFTC for replication group FTC.
    Here are all my troubleshooting steps (keep in mind that our VPN is going through a SonicWall <--I increased the TCP timeout to 24 hours):
    -Increased TCP Timeout to 24 hours 
    -Added the following values on both sending and receiving members and rebooted server
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
    Value =DisableTaskOffload
    Type = DWORD
    Data = 1
    Value =EnableTCPChimney
    Type = DWORD
    Data = 0
    Value =EnableTCPA
    Type = DWORD
    Data = 0
    Value =EnableRSS
    Type = DWORD
    Data = 0
    ---------------------------------more troubleshooting--------------------------
    -Disabled AntiVirus on both members
    -Made sure DFSR TCP ports 135 & 5722 are open
    -Installed all hotfixes for 2008 R2 (http://support.microsoft.com/kb/968429) and rebooted
    -Ran NETSTAT –ANOBP TCP and the DFS executable results are listed below:
    Sending Member:
    [DFSRs.exe]
      TCP    10.x.x.x:53            0.0.0.0:0             
    LISTENING       1692
    [DFSRs.exe]
      TCP    10.x.x.x:54669        
    10.x.x.x:5722          TIME_WAIT       0
      TCP    10.x.x.x:54673        
    10.x.x.x:5722          ESTABLISHED     1656
     [DFSRs.exe]
      TCP    10.x.x.x:64773        
    10.x.x.x:389           ESTABLISHED     1692
    [DFSRs.exe]
      TCP    10.x.x.x:64787        
    10.x.x.x:389           ESTABLISHED     1656
     [DFSRs.exe]
      TCP    10.x.x.x:64795        
    10.x.x.x:389           ESTABLISHED     2104
    Receiving Member:
    [DFSRs.exe]
      TCP    10.x.x.x:56683        
    10.x.x.x:389           ESTABLISHED     7472
     [DFSRs.exe]
      TCP    10.x.x.x:57625        
    10.x.x.x:54886         ESTABLISHED     2808
    [DFSRs.exe]
      TCP    10.x.x.x:61759        
    10.x.x.x:57625         TIME_WAIT       0
      TCP    10.x.x.x:61760        
    10.x.x.x:57625         TIME_WAIT       0
      TCP    10.x.x.x:61763        
    10.x.x.x:57625         TIME_WAIT       0
      TCP    10.x.x.x:61764        
    10.x.x.x:57625         TIME_WAIT       0
      TCP    10.x.x.x:61770        
    10.x.x.x:57625         TIME_WAIT       0
      TCP    10.x.x.x:61771        
    10.x.x.x:57625         TIME_WAIT       0
      TCP    10.x.x.x:61774        
    10.x.x.x:57625         TIME_WAIT       0
      TCP    10.x.x.x:61775        
    10.x.x.x:57625         TIME_WAIT       0
      TCP    10.x.x.x:61776        
    10.x.x.x:57625         TIME_WAIT       0
      TCP    10.x.x.x:61777        
    10.x.x.x:57625         TIME_WAIT       0
      TCP    10.x.x.x:61778        
    10.x.x.x:57625         TIME_WAIT       0
      TCP    10.x.x.x:61779        
    10.x.x.x:57625         TIME_WAIT       0
      TCP    10.x.x.x:61784        
    10.x.x.x:52757         ESTABLISHED     7472
    [DFSRs.exe]
      TCP    10.x.x.x:63661        
    10.x.x.x:63781         ESTABLISHED     4880
    ------------------------------more troubleshooting--------------------------
    -Increased Staging to 32GB
    -Opened the ADSIedit.msc console to verify the "Authenticated Users" is set with the default READ permission on the following object:
    a. The computer object of the DFS server
    b. The DFSR-LocalSettings object under the DFS server computer object
    -Ran
    ping <var>10.x.x.x</var> -f -l 1472 and got replies back from both servers
    -AD replication is successful on all partners
    -Nslookup is working so DNS is working
    -Updated NIC drivers on both servers
    - I ran the following to set the Primary Member:
    dfsradmin Membership Set /RGName:<replication group name> /RFName:<replicated folder name> /MemName:<primary member> /IsPrimary:True
    Then Dfsrdiag Pollad /Member:<member name>
    I'm seeing these errors in the dfsr logs:
    20141014 19:28:17.746 9116 SRTR   957 [WARN] SERVER_EstablishSession Failed to establish a replicated folder session. connId:{45C8C309-4EDD-459A-A0BB-4C5FACD97D44} csId:{7AC7917F-F96F-411B-A4D8-6BB303B3C813}
    Error:
    + [Error:9051(0x235b) UpstreamTransport::EstablishSession upstreamtransport.cpp:808 9116 C The content set is not ready]
    + [Error:9051(0x235b) OutConnection::EstablishSession outconnection.cpp:532 9116 C The content set is not ready]
    + [Error:9051(0x235b) OutConnection::EstablishSession outconnection.cpp:471 9116 C The content set is not ready]
    ---------------------------------------more troubleshooting-----------------------------
    I've done a lot of research on the Internet and most of it is pointing to the same stuff I've tried.  Does anyone have any other suggestions?  Maybe I need to look somewhere
    else on the server side or firewall side? 
    I tried replicating from a 2012 R2 server to another 2012 server and am getting the same events in the event log so maybe it's not a server issue. 
    Some other things I'm wondering:
    -Could it be the speed of the NICs?  Server A is a 2012 Server that has Hyper-V installed.  NIC teaming was initially setup and since Hyper-V is installed the NIC is a "vEthernet
    (Microsoft Network Adapter Multiplexor Driver Virtual Switch) running at a speed of 10.0Gbps whereas Server B is running a single NIC at 1.0Gbps
    -Could occasional ping timeout's cause the issue?  From time to time I get a timeout but it's not as often as the events I'm seeing.  I'm getting 53ms pings.  The folder
    is only 3 GB so it shouldn't take that long to replicate but it's been days.  The schedule I have set for replication is mostly all day except for our backup times which start at 11pm-5am.  Throughout the rest of the time I have it set anywhere from
    4Mbps to 64 Kbps.  Server A is on a 5mb circuit and Server B is on a 10mb circuit. 

    I'm seeing the same errors, all servers are running 2008 R2 x64. Across multiple sites, VPN is steady and reliably.
    185 events from 12:28:21 to 12:49:25
    Events are for all five servers (one per office, five total offices, no two in the same city, across three states).
    Events are not limited to one replication group. I have quite a few replication groups, so I don't know for sure but I'm running under the reasonable assumption that none are spared.
    Reminder from original post (and also, yes, same for me), the error is: Error: 1726 (The remote procedure call failed.)
    Some way to figure out what code triggers an Event ID 5014, and what code therein specifies an Error 1726, would extremely helpful. Trying random command line/registry changes on live servers is exceptionally unappealing.
    Side note, 1726 is referenced here:
    https://support.microsoft.com/kb/976442?wa=wsignin1.0
    But it says, "This RPC connection problem may be caused by an unstable WAN connection." I don't believe this is the case for my system.
    It also says...
    For most RPC connection problems, the DFS Replication service will try to obtain the files again without logging a warning or an error in the DFS Replication log. You can capture the network trace to determine whether the cause of the problem is at the network
    layer. To examine the TCP ports that the DFS Replication service is using on replication partners, run the following command in a
    Command Prompt window:
    NETSTAT –ANOBP TCP
    This returns all open TCP connections. The connections in question are "DFSRs.exe", which the command won't let you filter for.
    Instead, I used the NETSTAT command as advertised, dumping output to info.txt:
    NETSTAT -ANOBP TCP >> X:\info.txt
    Then I opened Excel and manually opened the .TXT for the open wizard. I chose fixed-width fields based on the first row for each result, and then added a column:
    =IF(A3="Can not", "Can not obtain ownership information", IF(LEFT(A3,1) = "[", A3&B3&C3, ""))
    Dragging this down through the entire file let me see that row (Row F) as the file name. Some anomalies were present but none impacted DFSrs.exe results.
    Finally, you can sort/filter (I sorted because I like being able to see everything, should I choose to) to get just the results you need, with the partial rows removed from the result set, or bumped to the end.
    My server had 125 connections open.
    That is a staggering number of connections to review, and I feel like I'm looking for a needle in a haystack.
    I'll see if I can find anything useful out, but a better solution would be most wonderful.

  • Tried deleting an admin on my Macbook Pro, has been 'Deleting Account' for 4 days now, will not let me shut down, log out or cancel the action, what can I do?

    Clicked to delete an admin account, but when I realised it was failing to do so, I tried to close System Preferences / log out / shutdown my mac and this is what comes up:
    'System Preferences is busy and can't be closed.
    Users & Groups preferences is removing a user account and saving the Home directory to a disk image.'
    It has been attempting to delete the account for a few days now and I need to access a different User on my Mac and can't!
    Please can someone tell me what do I do?
    Thank you!

    http://www.apple.com/support/macbookpro-videoissues/

  • Transactional replication very slow with indexes on Subscriber table

    I have setup Transactional Replication for one of our databases where one table with about 5mln records is replicated to a Subsriber database. With every replication about 500-600.000 changed records are send to the Subscriber.
    Since one month I see very strange behaviour when I add about 10 indexes to the Subscriber table. As soon as I have added the indexes replication speed becomes extremely slow (almost 3 hours for 600k records). As soon as I remove the indexes the replication
    is again very fast, about 3 minutes for the same amount of records.
    I've searched a lot on the internet to solve this issue but can't find any explaination for this strange behaviour after adding the indexes. As far as I know it doesn't have to be a problem to add indexes to a Subscriber table, and it hasn't been before on
    another replication configuration we use.
    Some information from the Replication Log:
    With indexes on the Subscriber table
    Total Run Time (ms) : 9589938 Total Work Time : 9586782
    Total Num Trans : 3 Num Trans/Sec : 0.00
    Total Num Cmds : 616245 Num Cmds/Sec : 64.28
    Total Idle Time : 0 
    Writer Thread Stats
    Total Number of Retries : 0 
    Time Spent on Exec : 9580752 
    Time Spent on Commits (ms): 2687 Commits/Sec : 0.00
    Time to Apply Cmds (ms) : 9586782 Cmds/Sec : 64.28
    Time Cmd Queue Empty (ms) : 5499 Empty Q Waits > 10ms: 172
    Total Time Request Blk(ms): 5499 
    P2P Work Time (ms) : 0 P2P Cmds Skipped : 0
    Reader Thread Stats
    Calls to Retrieve Cmds : 2 
    Time to Retrieve Cmds (ms): 10378 Cmds/Sec : 59379.94
    Time Cmd Queue Full (ms) : 9577919 Full Q Waits > 10ms : 6072
    Without indexes on the Subscriber table
    Total Run Time (ms) : 89282 Total Work Time : 88891
    Total Num Trans : 3 Num Trans/Sec : 0.03
    Total Num Cmds : 437324 Num Cmds/Sec : 4919.78
    Total Idle Time : 0 
    Writer Thread Stats
    Total Number of Retries : 0 
    Time Spent on Exec : 86298 
    Time Spent on Commits (ms): 282 Commits/Sec : 0.03
    Time to Apply Cmds (ms) : 88891 Cmds/Sec : 4919.78
    Time Cmd Queue Empty (ms) : 1827 Empty Q Waits > 10ms: 113
    Total Time Request Blk(ms): 1827 
    P2P Work Time (ms) : 0 P2P Cmds Skipped : 0
    Reader Thread Stats
    Calls to Retrieve Cmds : 2 
    Time to Retrieve Cmds (ms): 2812 Cmds/Sec : 155520.63
    Time Cmd Queue Full (ms) : 86032 Full Q Waits > 10ms : 4026
    Can someone please help me with this issue? Any ideas? 
    Pim 

    Hi Megens:
    Insert statement might be slow with not only indexes and few others things too
    0) SQL DB Blocking during inserts
    1) If any insert triggers are existed
    2) Constraints - if any
    3) Index fragmentation
    4) Page splits / fill factor
    Without indexes inserts will be fast because, each time when new row going to insert to the table, SQL Server will do
    1) it will check for the room, if no room page splits will happen and record will placed at right place
    2) Once the record updated all the index should be update
    3) all these extra update work will cause can make insert statement bit slow
    Its better to have index maintenance jobs frequently to avoid fragmentation.
    If every thing is clear on SQL Server Side, you need look up on DISK IO, N/W Latency between the servers and so on
    Thanks,
    Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

  • Recover database without controlfile and redo logs

    Hi guys,
    I am doing a testing with an Oracle Database 11.1.0.7.0, I want recover a database in this scenario without using RMAN:
    -All controlfiles are missing
    -All redo logs are missing
    -I have a Backup Controlfile To Trace Resetlogs (bkp_controlfile.sql)
    -The database is in archivelog mode
    -The database was created with OMF (Oracle Managed Files)
    So I have done this steps:
    1) When the database was opened I rename all controlfiles and all redo logs
    2) Shutdown Abort
    3) I run the bkp_controlfile.sql, here I have a problem...
    The database put in NOMOUNT, the controlfile was created and started the RECOVER DATABASE USING BACKUP CONTROLFILE, but when run ALTER DATABASE OPEN RESETLOGS; appear this:
    ERROR at line 1:
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1:
    '/u02/app/oracle/oradata/OMF/datafile/o1_mf_system_68hzcb2z_.dbf'I wasn´t expect this because I don´t want recover a datafile, I only want open with resetlogs.
    Any suggestion to help me?
    Thanks a lot.

    Excelent! Thanks for your answers Markus and Hemant.
    In conclusion...
    - If we have all redo logs availables we can recreate the control file and recover the database without any problems using backup controlfile to trace noresetlogs*.
    - if we haven´t all redo logs availables, there are 2 situations:
    1) If the database shutdown properly:_ We will be able to open the database using recover database using backup controlfile until cancel*.
    2) If the database doesn´t shutdown properly:_ We won´t be able to open the database with only a backup controlfile to trace.
    With all this I close this thread. Was very good experience.
    If anyone would add something will be welcome.
    Thanks for all
    I wish add the results of one of my tests: if I did all the steps in only one session of sqlplus I can shutdown properly the database, but if do the shutdown immediate* in a new session I can´t shutdown properly the database. Here I post the output:
    ALL IN ONE SESSION*
    [oracle@prueba ~]$ $ORACLE_HOME/bin/sqlplus / as sysdba
    SQL*Plus: Release 11.1.0.7.0 - Production on Wed Sep 22 13:58:10 2010
    Copyright (c) 1982, 2008, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> ALTER SYSTEM SWITCH LOGFILE;
    System altered.
    SQL> SHUTDOWN IMMEDIATE
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> STARTUP
    ORACLE instance started.
    Total System Global Area  631914496 bytes
    Fixed Size                  1315224 bytes
    Variable Size             377491048 bytes
    Database Buffers          247463936 bytes
    Redo Buffers                5644288 bytes
    Database mounted.
    Database opened.
    SQL> SHUTDOWN IMMEDIATE
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> @/home/oracle/bkp_controlfile.sql
    ORACLE instance started.
    Total System Global Area  631914496 bytes
    Fixed Size                  1315224 bytes
    Variable Size             377491048 bytes
    Database Buffers          247463936 bytes
    Redo Buffers                5644288 bytes
    Control file created.
    SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL;
    ORA-00279: change 398764 generated at 09/22/2010 14:09:49 needed for thread 1
    ORA-00289: suggestion :
    /u02/app/oracle/flash_recovery_area/OMF/archivelog/2010_09_22/o1_mf_1_40_%u_.arc
    ORA-00280: change 398764 for thread 1 is in sequence #40
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    CANCEL
    Media recovery cancelled.
    SQL> ALTER DATABASE OPEN RESETLOGS;
    Database altered.
    SQL> ALTER TABLESPACE TEMP ADD TEMPFILE '/u02/app/oracle/oradata/OMF/datafile/o1_mf_temp_69n3z3vv_.tmp' SIZE 50331648  REUSE AUTOEXTEND ON NEXT 655360  MAXSIZE 32767M;
    Tablespace altered.
    SQL>
    ALL IN DIFERENT SESSIONS*
    [oracle@prueba ~]$ $ORACLE_HOME/bin/sqlplus / as sysdba
    SQL*Plus: Release 11.1.0.7.0 - Production on Wed Sep 22 13:55:47 2010
    Copyright (c) 1982, 2008, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS '/home/oracle/bkp_controlfile.sql' RESETLOGS;
    Database altered.
    SQL> SHUTDOWN IMMEDIATE
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> STARTUP MOUNT
    ORACLE instance started.
    Total System Global Area  631914496 bytes
    Fixed Size                  1315224 bytes
    Variable Size             377491048 bytes
    Database Buffers          247463936 bytes
    Redo Buffers                5644288 bytes
    Database mounted.
    SQL> ALTER DATABASE ARCHIVELOG;
    Database altered.
    SQL> ALTER DATABASE OPEN;
    Database altered.
    SQL> ALTER SYSTEM SWITCH LOGFILE;
    System altered.
    SQL> ALTER SYSTEM SWITCH LOGFILE;
    System altered.
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    [oracle@prueba ~]$ $ORACLE_HOME/bin/sqlplus / as sysdba
    SQL*Plus: Release 11.1.0.7.0 - Production on Wed Sep 22 13:58:10 2010
    Copyright (c) 1982, 2008, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> SHUTDOWN IMMEDIATE
    ORA-00210: cannot open the specified control file
    ORA-00202: control file: '/u02/app/oracle/oradata/OMF/controlfile/o1_mf_69n3x6n5_.ctl'
    ORA-27041: unable to open file
    Linux Error: 2: No such file or directory
    Additional information: 3

  • About a dropped archived log.

    Hello every body.
    I have this big problem:
    An archived log of my standby was dropped, so I restored that archived log at primary database and didn´t go to standby database.
    I copied it to standby and I was try to register it manual:
    SQL: alter database register logfile ´....´;
    But a ora shows me that archived log already exists and it can´t register it.
    So how can I resolve this problem?
    Thanks a lot

    First investigate that for you actually need this log for standby database recovering? Also how happen dropping ? from just OS level then that is right you will get an error.To checking execute below script from standby database
    select max(sequence#) from v$archived_log where applied='YES'; If above result is bigger than from your losing archivelog sequence then do not worry else after copying this archive log from primary to standby then execute below command on standby database and apply this log
    recover standby database until cancel;
    /*Then apply this log and*/
    shutdown immediate;
    startup mount;
    alter database recover managed standby database;

Maybe you are looking for