Power off before swapping EtherCAT hardware?

NI has provided the ScanEngine API to allows user's the ability to discover C-series and EtherCAT chassis dynamically and I really like it. This allows me to "hot swap" hardware and my software can just adapt dynamically based on the discovered modules. Is turning off my etherCAT chassis prior to doing this recommended anywhere?
In otherwords, I like the idea of putting the ScanEngine in Configuration Mode then pulling out C-series modules and replacing them with new ones without powering off the chassis. Could this potentially harm my hardware? Does NI strictly advise against this?
Thanks,
Craig

Hi Craig,
NI CompactRIO is a small rugged industrial control and acquisition system, and all the NI C-Series modules used in this system are hot-swappable industrial I/O modules. That’s being said, when using a CompactRIO (no matter it’s a cRIO controller or an expansion backplane like NI 9144 EtherCAT slave chassis) with modules in the slots, it is NOT necessary to power down the device.  CompactRIO was designed with this feature in mind.
A slight deference a CompactRIO RT Controller (e.g. NI 9074) and NI 9144 is that, when you swap (even an identical) C-Series IO module on NI 9144, the slave device will report an emergency data to your host system, which might disturb your system if it’s running. The emergency will disappear when you manually or programmatically switch Scan Engine to Active Mode again. But anyhow, this is all for software side; it will not harm your hardware.
Hope it answers your question!
Josiane Zhou
NI-IndComm for EtherCAT

Similar Messages

  • I have been able to wake my macmini by hitting the space bar - but since installing 10.7.4 using the 1.4Gb combo this wake method no longer works. Now the macmini shuts down, and I have to switch mains power off and on again before powering up the macmini

    Since purchase of my macmini (2011 model) I have been able to wake it from sleep by hitting the (wired) keyboard space bar.
    However, I recently updated the OS to 10.7.4 using the combo (1.4Gb) update, since when I cannot wake the macmini in that way.
    Now, after putting the macmini to sleep, pressing the spacebar causes it to shut down.
    I then have to switch mains power off and on again at the wall socket, after which the macmini starts up from shutdown condition.
    I am by no means an expert, and have not been fiddling with settings, so I am in need of advice on what could need resetting to allow me to return to the previous simple 'wake up' approach!
    Thanks.

    Reset the SMC > Intel-based Macs: Resetting the System Management Controller (SMC)
    1. Shut down the computer.
    2. Unplug the computer's power cord.
    3. Wait fifteen seconds.
    4. Attach the computer's power cord.
    5. Wait five seconds, then press the power button to turn on the computer.
    Followed by resetting the PRAM > Resetting your Mac's PRAM and NVRAM
    1. Shut down the computer.
    2. Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
    3. Turn on the computer.
    4. Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
    5. Hold the keys down until the computer restarts and you hear the startup sound for the second time.
    6. Release the keys.
    Then if those do not fix the problem, you may need to reset your Energy Saver and Keyboard Preferences by readjusting them.

  • HT2309 Do I need to power off the iphone 4s  before remove the sim card?

    Do I need to power off the iphone 4s  before remove the sim card?

    Thanks, I think so, too.
    But  Apple says  "When changing the SIM card, power off the device prior to opening the SIM tray" in http://support.apple.com/kb/ht2309.

  • [Solved] Random Freezes Requiring Manual Power off

    Since I built this system, I've been getting random freezes that force me to have to manually power off and back on the entire system.  I have no idea what's causing it and I've tried everything under the sun that I can think of to resolve it to no avail.  I posted about this a while back in another forum, but I'm hoping I'll have better luck here.
    Symptoms:
    Entire system will completely freeze.  No input is recognized, keyboard controls do not function (numlock, caps lock, etc.), cannot switch to another TTY, nothing.  There appears to be no rhyme or reason to when the freezes occur.  Sometimes the machine will be sitting idle and freeze in the middle of the night and I'll come in in the morning and find it frozen, other times I'll be in the middle of using it and it will freeze (as just happened).  Every time I have to hold down the power button to shut off, then turn it back on.
    What I've tried so far:
    Swapping out all the RAM
    Completely wiping the entire system and re-installing from the ground up (twice now I've done this)
    Unplugging various USB devices and seeing if leaving those unplugged helps (it does not).
    I'm at my wits end.  This has been going on for months and I have no idea what to do at this point. This is the most stumped I've ever been. 
    The thing that drives me the most nuts is that I have an almost *identical* system at home (the one that's freezing is my work computer).  Same CPU, same motherboard, same SSD partitions and layout, virtually the exact same software installed as well.  The only differences are a different GPU, different band of RAM, different brand of SSD, and a different case.  The specs from my home computer are in my signature and I can provide exact hardware info on the work system if anyone thinks it'll help.
    I'm willing to provide whatever information anyone can suggest to help troubleshoot the issue.  I've got a bunch of log output from journalctl from various times it's crashed, but I haven't been able to make sense of it with regards to finding patterns or useful troubleshooting information.  Below is the most recent log from a few minutes before and after the crash.  You'll see the reboot at 17:51:40
    (sudo journalctl --since 17:45:00)
    -- Logs begin at Mon 2015-04-06 13:26:57 EDT, end at Thu 2015-05-07 18:01:46 EDT. --
    May 07 17:45:07 workArchPC kdeinit5[794]: powerdevil: Released inhibition with cookie 10
    May 07 17:45:07 workArchPC kdeinit5[794]: powerdevil: Restoring DPMS features after inhibition release
    May 07 17:45:07 workArchPC kdeinit5[794]: powerdevil: Added inhibition from an explicit DBus service, ":1.83" , with cookie 11 from "/usr/bin/google-chrome-stable" with "Playing Video"
    May 07 17:45:07 workArchPC kdeinit5[794]: powerdevil: Added change screen settings
    May 07 17:45:07 workArchPC kdeinit5[794]: powerdevil: Added interrupt session
    May 07 17:45:07 workArchPC kdeinit5[794]: powerdevil: Disabling DPMS due to inhibition
    May 07 17:45:11 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:45:18 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:45:19 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:45:22 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:45:26 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:45:31 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:45:40 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:45:40 workArchPC kdeinit5[794]: powerdevil: Released inhibition with cookie 11
    May 07 17:45:40 workArchPC kdeinit5[794]: powerdevil: Restoring DPMS features after inhibition release
    May 07 17:45:40 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:45:40 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:45:45 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:45:50 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:45:56 workArchPC kdeinit5[794]: powerdevil: Added inhibition from an explicit DBus service, ":1.84" , with cookie 12 from "/usr/bin/google-chrome-stable" with "Playing Video"
    May 07 17:45:56 workArchPC kdeinit5[794]: powerdevil: Added change screen settings
    May 07 17:45:56 workArchPC kdeinit5[794]: powerdevil: Added interrupt session
    May 07 17:45:56 workArchPC kdeinit5[794]: powerdevil: Disabling DPMS due to inhibition
    May 07 17:45:57 workArchPC kdeinit5[794]: powerdevil: Released inhibition with cookie 12
    May 07 17:45:57 workArchPC kdeinit5[794]: powerdevil: Restoring DPMS features after inhibition release
    May 07 17:45:57 workArchPC kdeinit5[794]: powerdevil: Added inhibition from an explicit DBus service, ":1.85" , with cookie 13 from "/usr/bin/google-chrome-stable" with "Playing Video"
    May 07 17:45:57 workArchPC kdeinit5[794]: powerdevil: Added change screen settings
    May 07 17:45:57 workArchPC kdeinit5[794]: powerdevil: Added interrupt session
    May 07 17:45:57 workArchPC kdeinit5[794]: powerdevil: Disabling DPMS due to inhibition
    May 07 17:46:03 workArchPC kdeinit5[794]: powerdevil: Released inhibition with cookie 13
    May 07 17:46:03 workArchPC kdeinit5[794]: powerdevil: Restoring DPMS features after inhibition release
    May 07 17:46:03 workArchPC kdeinit5[794]: powerdevil: Added inhibition from an explicit DBus service, ":1.86" , with cookie 14 from "/usr/bin/google-chrome-stable" with "Playing Video"
    May 07 17:46:03 workArchPC kdeinit5[794]: powerdevil: Added change screen settings
    May 07 17:46:03 workArchPC kdeinit5[794]: powerdevil: Added interrupt session
    May 07 17:46:03 workArchPC kdeinit5[794]: powerdevil: Disabling DPMS due to inhibition
    May 07 17:46:04 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:46:04 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:46:19 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:46:19 workArchPC kdeinit5[794]: powerdevil: Released inhibition with cookie 14
    May 07 17:46:19 workArchPC kdeinit5[794]: powerdevil: Restoring DPMS features after inhibition release
    May 07 17:46:20 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:46:26 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:46:40 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:46:42 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:46:48 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:46:55 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:47:08 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:47:11 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:47:15 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:47:16 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:47:17 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:47:46 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:47:54 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:47:56 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:47:57 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:48:25 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:48:26 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:48:34 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:48:35 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:48:39 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    May 07 17:48:43 workArchPC kdeinit5[794]: powerdevil: Added inhibition from an explicit DBus service, ":1.87" , with cookie 15 from "/usr/bin/google-chrome-stable" with "Playing Video"
    May 07 17:48:43 workArchPC kdeinit5[794]: powerdevil: Added change screen settings
    May 07 17:48:43 workArchPC kdeinit5[794]: powerdevil: Added interrupt session
    May 07 17:48:43 workArchPC kdeinit5[794]: powerdevil: Disabling DPMS due to inhibition
    May 07 17:51:40 workArchPC kwin_x11[918]: kwin_core: Raising: Belongs to active application
    -- Reboot --
    May 07 17:54:22 workArchPC systemd-journal[263]: Runtime journal is using 8.0M (max allowed 1.5G, trying to leave 2.3G free of 15.6G available → current limit 1.5G).
    May 07 17:54:22 workArchPC systemd-journal[263]: Permanent journal is using 1.4G (max allowed 3.3G, trying to leave 4.0G free of 23.3G available → current limit 3.3G).
    May 07 17:54:22 workArchPC systemd-journal[263]: Time spent on flushing to /var is 4.536ms for 2 entries.
    May 07 17:54:22 workArchPC kernel: Initializing cgroup subsys cpuset
    May 07 17:54:22 workArchPC kernel: Initializing cgroup subsys cpu
    May 07 17:54:22 workArchPC kernel: Initializing cgroup subsys cpuacct
    May 07 17:54:22 workArchPC kernel: Linux version 4.0.1-1-ARCH (builduser@tobias) (gcc version 5.1.0 (GCC) ) #1 SMP PREEMPT Wed Apr 29 12:00:26 CEST 2015
    May 07 17:54:22 workArchPC kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=c215d6d6-d557-43a8-9801-f632e7f25e33 rw quiet
    May 07 17:54:22 workArchPC kernel: tseg: 00bd800000
    May 07 17:54:22 workArchPC kernel: e820: BIOS-provided physical RAM map:
    May 07 17:54:22 workArchPC kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009e7ff] usable
    May 07 17:54:22 workArchPC kernel: BIOS-e820: [mem 0x000000000009e800-0x000000000009ffff] reserved
    May 07 17:54:22 workArchPC kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
    May 07 17:54:22 workArchPC kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000ba70afff] usable
    May 07 17:54:22 workArchPC kernel: BIOS-e820: [mem 0x00000000ba70b000-0x00000000bab3efff] reserved
    May 07 17:54:22 workArchPC kernel: BIOS-e820: [mem 0x00000000bab3f000-0x00000000bab4efff] ACPI data
    May 07 17:54:22 workArchPC kernel: BIOS-e820: [mem 0x00000000bab4f000-0x00000000bb956fff] ACPI NVS
    May 07 17:54:22 workArchPC kernel: BIOS-e820: [mem 0x00000000bb957000-0x00000000bca33fff] reserved
    May 07 17:54:22 workArchPC kernel: BIOS-e820: [mem 0x00000000bca34000-0x00000000bca34fff] usable
    May 07 17:54:22 workArchPC kernel: BIOS-e820: [mem 0x00000000bca35000-0x00000000bcc3afff] ACPI NVS
    May 07 17:54:22 workArchPC kernel: BIOS-e820: [mem 0x00000000bcc3b000-0x00000000bd082fff] usable
    May 07 17:54:22 workArchPC kernel: BIOS-e820: [mem 0x00000000bd083000-0x00000000bd7f3fff] reserved
    May 07 17:54:22 workArchPC kernel: BIOS-e820: [mem 0x00000000bd7f4000-0x00000000bd7fffff] usable
    May 07 17:54:22 workArchPC kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
    May 07 17:54:22 workArchPC kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
    May 07 17:54:22 workArchPC kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
    May 07 17:54:22 workArchPC kernel: BIOS-e820: [mem 0x00000000fec20000-0x00000000fec20fff] reserved
    May 07 17:54:22 workArchPC kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
    May 07 17:54:22 workArchPC kernel: BIOS-e820: [mem 0x00000000fed61000-0x00000000fed70fff] reserved
    May 07 17:54:22 workArchPC kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
    May 07 17:54:22 workArchPC kernel: BIOS-e820: [mem 0x00000000fef00000-0x00000000ffffffff] reserved
    May 07 17:54:22 workArchPC kernel: BIOS-e820: [mem 0x0000000100001000-0x000000083effffff] usable
    May 07 17:54:22 workArchPC kernel: NX (Execute Disable) protection: active
    May 07 17:54:22 workArchPC kernel: SMBIOS 2.7 present.
    May 07 17:54:22 workArchPC kernel: DMI: To be filled by O.E.M. To be filled by O.E.M./SABERTOOTH 990FX R2.0, BIOS 2301 01/06/2014
    May 07 17:54:22 workArchPC kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    May 07 17:54:22 workArchPC kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    May 07 17:54:22 workArchPC kernel: AGP: No AGP bridge found
    May 07 17:54:22 workArchPC kernel: e820: last_pfn = 0x83f000 max_arch_pfn = 0x400000000
    May 07 17:54:22 workArchPC kernel: MTRR default type: uncachable
    May 07 17:54:22 workArchPC kernel: MTRR fixed ranges enabled:
    May 07 17:54:22 workArchPC kernel: 00000-9FFFF write-back
    May 07 17:54:22 workArchPC kernel: A0000-BFFFF write-through
    May 07 17:54:22 workArchPC kernel: C0000-CEFFF write-protect
    May 07 17:54:22 workArchPC kernel: CF000-EBFFF uncachable
    May 07 17:54:22 workArchPC kernel: EC000-FFFFF write-protect
    May 07 17:54:22 workArchPC kernel: MTRR variable ranges enabled:
    May 07 17:54:22 workArchPC kernel: 0 base 000000000000 mask FFFF80000000 write-back
    May 07 17:54:22 workArchPC kernel: 1 base 000080000000 mask FFFFC0000000 write-back
    May 07 17:54:22 workArchPC kernel: 2 base 0000BD800000 mask FFFFFF800000 uncachable
    May 07 17:54:22 workArchPC kernel: 3 base 0000BE000000 mask FFFFFE000000 uncachable
    May 07 17:54:22 workArchPC kernel: 4 disabled
    May 07 17:54:22 workArchPC kernel: 5 disabled
    May 07 17:54:22 workArchPC kernel: 6 disabled
    May 07 17:54:22 workArchPC kernel: 7 disabled
    May 07 17:54:22 workArchPC kernel: TOM2: 000000083f000000 aka 33776M
    May 07 17:54:22 workArchPC kernel: PAT configuration [0-7]: WB WC UC- UC WB WC UC- UC
    May 07 17:54:22 workArchPC kernel: e820: update [mem 0xbd800000-0xffffffff] usable ==> reserved
    May 07 17:54:22 workArchPC kernel: e820: last_pfn = 0xbd800 max_arch_pfn = 0x400000000
    May 07 17:54:22 workArchPC kernel: Scanning 1 areas for low memory corruption
    May 07 17:54:22 workArchPC kernel: Base memory trampoline at [ffff880000098000] 98000 size 24576
    May 07 17:54:22 workArchPC kernel: Using GB pages for direct mapping
    May 07 17:54:22 workArchPC kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
    May 07 17:54:22 workArchPC kernel: [mem 0x00000000-0x000fffff] page 4k
    May 07 17:54:22 workArchPC kernel: BRK [0x01b1b000, 0x01b1bfff] PGTABLE
    May 07 17:54:22 workArchPC kernel: BRK [0x01b1c000, 0x01b1cfff] PGTABLE
    May 07 17:54:22 workArchPC kernel: BRK [0x01b1d000, 0x01b1dfff] PGTABLE
    May 07 17:54:22 workArchPC kernel: init_memory_mapping: [mem 0x83ee00000-0x83effffff]
    May 07 17:54:22 workArchPC kernel: [mem 0x83ee00000-0x83effffff] page 2M
    May 07 17:54:22 workArchPC kernel: BRK [0x01b1e000, 0x01b1efff] PGTABLE
    May 07 17:54:22 workArchPC kernel: init_memory_mapping: [mem 0x820000000-0x83edfffff]
    May 07 17:54:22 workArchPC kernel: [mem 0x820000000-0x83edfffff] page 2M
    May 07 17:54:22 workArchPC kernel: init_memory_mapping: [mem 0x800000000-0x81fffffff]
    May 07 17:54:22 workArchPC kernel: [mem 0x800000000-0x81fffffff] page 2M
    May 07 17:54:22 workArchPC kernel: init_memory_mapping: [mem 0x00100000-0xba70afff]
    May 07 17:54:22 workArchPC kernel: [mem 0x00100000-0x001fffff] page 4k
    May 07 17:54:22 workArchPC kernel: [mem 0x00200000-0x3fffffff] page 2M
    May 07 17:54:22 workArchPC kernel: [mem 0x40000000-0x7fffffff] page 1G
    May 07 17:54:22 workArchPC kernel: [mem 0x80000000-0xba5fffff] page 2M
    May 07 17:54:22 workArchPC kernel: [mem 0xba600000-0xba70afff] page 4k
    May 07 17:54:22 workArchPC kernel: init_memory_mapping: [mem 0xbca34000-0xbca34fff]
    May 07 17:54:22 workArchPC kernel: [mem 0xbca34000-0xbca34fff] page 4k
    May 07 17:54:22 workArchPC kernel: BRK [0x01b1f000, 0x01b1ffff] PGTABLE
    May 07 17:54:22 workArchPC kernel: init_memory_mapping: [mem 0xbcc3b000-0xbd082fff]
    May 07 17:54:22 workArchPC kernel: [mem 0xbcc3b000-0xbcdfffff] page 4k
    May 07 17:54:22 workArchPC kernel: [mem 0xbce00000-0xbcffffff] page 2M
    May 07 17:54:22 workArchPC kernel: [mem 0xbd000000-0xbd082fff] page 4k
    May 07 17:54:22 workArchPC kernel: BRK [0x01b20000, 0x01b20fff] PGTABLE
    May 07 17:54:22 workArchPC kernel: init_memory_mapping: [mem 0xbd7f4000-0xbd7fffff]
    May 07 17:54:22 workArchPC kernel: [mem 0xbd7f4000-0xbd7fffff] page 4k
    May 07 17:54:22 workArchPC kernel: init_memory_mapping: [mem 0x100001000-0x7ffffffff]
    May 07 17:54:22 workArchPC kernel: [mem 0x100001000-0x1001fffff] page 4k
    May 07 17:54:22 workArchPC kernel: [mem 0x100200000-0x13fffffff] page 2M
    May 07 17:54:22 workArchPC kernel: [mem 0x140000000-0x7ffffffff] page 1G
    May 07 17:54:22 workArchPC kernel: RAMDISK: [mem 0x36e78000-0x37733fff]
    May 07 17:54:22 workArchPC kernel: ACPI: Early table checksum verification disabled
    May 07 17:54:22 workArchPC kernel: ACPI: RSDP 0x00000000000F0490 000024 (v02 ALASKA)
    May 07 17:54:22 workArchPC kernel: ACPI: XSDT 0x00000000BAB47070 00005C (v01 ALASKA A M I 01072009 AMI 00010013)
    May 07 17:54:22 workArchPC kernel: ACPI: FACP 0x00000000BAB4E110 00010C (v05 ALASKA A M I 01072009 AMI 00010013)
    May 07 17:54:22 workArchPC kernel: ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20150204/tbfadt-649)
    May 07 17:54:22 workArchPC kernel: ACPI: DSDT 0x00000000BAB47168 006FA8 (v02 ALASKA A M I 00000000 INTL 20051117)
    May 07 17:54:22 workArchPC kernel: ACPI: FACS 0x00000000BB951F80 000040
    May 07 17:54:22 workArchPC kernel: ACPI: APIC 0x00000000BAB4E220 00009E (v03 ALASKA A M I 01072009 AMI 00010013)
    May 07 17:54:22 workArchPC kernel: ACPI: FPDT 0x00000000BAB4E2C0 000044 (v01 ALASKA A M I 01072009 AMI 00010013)
    May 07 17:54:22 workArchPC kernel: ACPI: MCFG 0x00000000BAB4E308 00003C (v01 ALASKA A M I 01072009 MSFT 00010013)
    May 07 17:54:22 workArchPC kernel: ACPI: HPET 0x00000000BAB4E348 000038 (v01 ALASKA A M I 01072009 AMI 00000005)
    May 07 17:54:22 workArchPC kernel: ACPI: IVRS 0x00000000BAB4E6E0 0000F8 (v01 AMD RD890S 00202031 AMD 00000000)
    May 07 17:54:22 workArchPC kernel: ACPI: SSDT 0x00000000BAB4E3D8 000304 (v01 AMD POWERNOW 00000001 AMD 00000001)
    May 07 17:54:22 workArchPC kernel: ACPI: Local APIC address 0xfee00000
    May 07 17:54:22 workArchPC kernel: No NUMA configuration found
    May 07 17:54:22 workArchPC kernel: Faking a node at [mem 0x0000000000000000-0x000000083effffff]
    May 07 17:54:22 workArchPC kernel: NODE_DATA(0) allocated [mem 0x83eff6000-0x83eff9fff]
    May 07 17:54:22 workArchPC kernel: [ffffea0000000000-ffffea0020ffffff] PMD -> [ffff88081e600000-ffff88083e5fffff] on node 0
    May 07 17:54:22 workArchPC kernel: Zone ranges:
    May 07 17:54:22 workArchPC kernel: DMA [mem 0x0000000000001000-0x0000000000ffffff]
    May 07 17:54:22 workArchPC kernel: DMA32 [mem 0x0000000001000000-0x00000000ffffffff]
    May 07 17:54:22 workArchPC kernel: Normal [mem 0x0000000100000000-0x000000083effffff]
    May 07 17:54:22 workArchPC kernel: Movable zone start for each node
    May 07 17:54:22 workArchPC kernel: Early memory node ranges
    May 07 17:54:22 workArchPC kernel: node 0: [mem 0x0000000000001000-0x000000000009dfff]
    May 07 17:54:22 workArchPC kernel: node 0: [mem 0x0000000000100000-0x00000000ba70afff]
    May 07 17:54:22 workArchPC kernel: node 0: [mem 0x00000000bca34000-0x00000000bca34fff]
    May 07 17:54:22 workArchPC kernel: node 0: [mem 0x00000000bcc3b000-0x00000000bd082fff]
    May 07 17:54:22 workArchPC kernel: node 0: [mem 0x00000000bd7f4000-0x00000000bd7fffff]
    May 07 17:54:22 workArchPC kernel: node 0: [mem 0x0000000100001000-0x000000083effffff]
    May 07 17:54:22 workArchPC kernel: Initmem setup node 0 [mem 0x0000000000001000-0x000000083effffff]
    May 07 17:54:22 workArchPC kernel: On node 0 totalpages: 8362748
    May 07 17:54:22 workArchPC kernel: DMA zone: 64 pages used for memmap
    May 07 17:54:22 workArchPC kernel: DMA zone: 21 pages reserved
    May 07 17:54:22 workArchPC kernel: DMA zone: 3997 pages, LIFO batch:0
    May 07 17:54:22 workArchPC kernel: DMA32 zone: 11886 pages used for memmap
    May 07 17:54:22 workArchPC kernel: DMA32 zone: 760672 pages, LIFO batch:31
    May 07 17:54:22 workArchPC kernel: Normal zone: 118720 pages used for memmap
    May 07 17:54:22 workArchPC kernel: Normal zone: 7598079 pages, LIFO batch:31
    May 07 17:54:22 workArchPC kernel: ACPI: PM-Timer IO Port: 0x808
    May 07 17:54:22 workArchPC kernel: ACPI: Local APIC address 0xfee00000
    May 07 17:54:22 workArchPC kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x10] enabled)
    May 07 17:54:22 workArchPC kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x11] enabled)
    May 07 17:54:22 workArchPC kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x12] enabled)
    May 07 17:54:22 workArchPC kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x13] enabled)
    May 07 17:54:22 workArchPC kernel: ACPI: LAPIC (acpi_id[0x05] lapic_id[0x14] enabled)
    May 07 17:54:22 workArchPC kernel: ACPI: LAPIC (acpi_id[0x06] lapic_id[0x15] enabled)
    May 07 17:54:22 workArchPC kernel: ACPI: LAPIC (acpi_id[0x07] lapic_id[0x16] enabled)
    May 07 17:54:22 workArchPC kernel: ACPI: LAPIC (acpi_id[0x08] lapic_id[0x17] enabled)
    May 07 17:54:22 workArchPC kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
    May 07 17:54:22 workArchPC kernel: ACPI: IOAPIC (id[0x09] address[0xfec00000] gsi_base[0])
    May 07 17:54:22 workArchPC kernel: IOAPIC[0]: apic_id 9, version 33, address 0xfec00000, GSI 0-23
    May 07 17:54:22 workArchPC kernel: ACPI: IOAPIC (id[0x0a] address[0xfec20000] gsi_base[24])
    May 07 17:54:22 workArchPC kernel: IOAPIC[1]: apic_id 10, version 33, address 0xfec20000, GSI 24-55
    May 07 17:54:22 workArchPC kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    May 07 17:54:22 workArchPC kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
    May 07 17:54:22 workArchPC kernel: ACPI: IRQ0 used by override.
    May 07 17:54:22 workArchPC kernel: ACPI: IRQ9 used by override.
    May 07 17:54:22 workArchPC kernel: Using ACPI (MADT) for SMP configuration information
    May 07 17:54:22 workArchPC kernel: ACPI: HPET id: 0x43538210 base: 0xfed00000
    May 07 17:54:22 workArchPC kernel: smpboot: Allowing 8 CPUs, 0 hotplug CPUs
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0xba70b000-0xbab3efff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0xbab3f000-0xbab4efff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0xbab4f000-0xbb956fff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0xbb957000-0xbca33fff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0xbca35000-0xbcc3afff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0xbd083000-0xbd7f3fff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0xbd800000-0xf7ffffff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0xfec01000-0xfec0ffff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0xfec10000-0xfec10fff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0xfec11000-0xfec1ffff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0xfec20000-0xfec20fff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0xfec21000-0xfecfffff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfed00fff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0xfed01000-0xfed60fff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0xfed61000-0xfed70fff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0xfed71000-0xfed7ffff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0xfed80000-0xfed8ffff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0xfed90000-0xfeefffff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0xfef00000-0xffffffff]
    May 07 17:54:22 workArchPC kernel: PM: Registered nosave memory: [mem 0x100000000-0x100000fff]
    May 07 17:54:22 workArchPC kernel: e820: [mem 0xbd800000-0xf7ffffff] available for PCI devices
    May 07 17:54:22 workArchPC kernel: Booting paravirtualized kernel on bare hardware
    May 07 17:54:22 workArchPC kernel: setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:8 nr_node_ids:1
    May 07 17:54:22 workArchPC kernel: PERCPU: Embedded 31 pages/cpu @ffff88083ec00000 s86168 r8192 d32616 u262144
    May 07 17:54:22 workArchPC kernel: pcpu-alloc: s86168 r8192 d32616 u262144 alloc=1*2097152
    May 07 17:54:22 workArchPC kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7
    May 07 17:54:22 workArchPC kernel: Built 1 zonelists in Node order, mobility grouping on. Total pages: 8232057
    May 07 17:54:22 workArchPC kernel: Policy zone: Normal
    May 07 17:54:22 workArchPC kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=c215d6d6-d557-43a8-9801-f632e7f25e33 rw quiet
    May 07 17:54:22 workArchPC kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
    May 07 17:54:22 workArchPC kernel: xsave: enabled xstate_bv 0x7, cntxt size 0x340 using standard form
    May 07 17:54:22 workArchPC kernel: AGP: Checking aperture...
    May 07 17:54:22 workArchPC kernel: AGP: No AGP bridge found
    May 07 17:54:22 workArchPC kernel: AGP: Node 0: aperture [bus addr 0xf8000000-0xfbffffff] (64MB)
    May 07 17:54:22 workArchPC kernel: Memory: 32838936K/33450992K available (5601K kernel code, 835K rwdata, 1776K rodata, 1160K init, 1152K bss, 612056K reserved, 0K cma-reserved)
    May 07 17:54:22 workArchPC kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
    May 07 17:54:22 workArchPC kernel: Preemptible hierarchical RCU implementation.
    May 07 17:54:22 workArchPC kernel: RCU dyntick-idle grace-period acceleration is enabled.
    May 07 17:54:22 workArchPC kernel: RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=8.
    May 07 17:54:22 workArchPC kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
    May 07 17:54:22 workArchPC kernel: NR_IRQS:8448 nr_irqs:1032 16
    May 07 17:54:22 workArchPC kernel: spurious 8259A interrupt: IRQ7.
    May 07 17:54:22 workArchPC kernel: Console: colour dummy device 80x25
    May 07 17:54:22 workArchPC kernel: console [tty0] enabled
    May 07 17:54:22 workArchPC kernel: hpet clockevent registered
    May 07 17:54:22 workArchPC kernel: tsc: Fast TSC calibration failed
    May 07 17:54:22 workArchPC kernel: tsc: Unable to calibrate against PIT
    May 07 17:54:22 workArchPC kernel: tsc: using HPET reference calibration
    May 07 17:54:22 workArchPC kernel: tsc: Detected 4715.820 MHz processor
    May 07 17:54:22 workArchPC kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 9435.62 BogoMIPS (lpj=15719400)
    May 07 17:54:22 workArchPC kernel: pid_max: default: 32768 minimum: 301
    May 07 17:54:22 workArchPC kernel: ACPI: Core revision 20150204
    May 07 17:54:22 workArchPC kernel: ACPI: All ACPI Tables successfully acquired
    May 07 17:54:22 workArchPC kernel: Security Framework initialized
    May 07 17:54:22 workArchPC kernel: Yama: becoming mindful.
    May 07 17:54:22 workArchPC kernel: Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
    May 07 17:54:22 workArchPC kernel: Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
    May 07 17:54:22 workArchPC kernel: Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
    May 07 17:54:22 workArchPC kernel: Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
    May 07 17:54:22 workArchPC kernel: Initializing cgroup subsys blkio
    May 07 17:54:22 workArchPC kernel: Initializing cgroup subsys memory
    May 07 17:54:22 workArchPC kernel: Initializing cgroup subsys devices
    May 07 17:54:22 workArchPC kernel: Initializing cgroup subsys freezer
    May 07 17:54:22 workArchPC kernel: Initializing cgroup subsys net_cls
    May 07 17:54:22 workArchPC kernel: CPU: Physical Processor ID: 0
    May 07 17:54:22 workArchPC kernel: CPU: Processor Core ID: 0
    May 07 17:54:22 workArchPC kernel: mce: CPU supports 7 MCE banks
    May 07 17:54:22 workArchPC kernel: LVT offset 1 assigned for vector 0xf9
    May 07 17:54:22 workArchPC kernel: Last level iTLB entries: 4KB 512, 2MB 1024, 4MB 512
    May 07 17:54:22 workArchPC kernel: Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 512, 1GB 0
    May 07 17:54:22 workArchPC kernel: Freeing SMP alternatives memory: 20K (ffffffff819f4000 - ffffffff819f9000)
    May 07 17:54:22 workArchPC kernel: ftrace: allocating 21221 entries in 83 pages
    May 07 17:54:22 workArchPC kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    May 07 17:54:22 workArchPC kernel: smpboot: CPU0: AMD FX(tm)-9590 Eight-Core Processor (fam: 15, model: 02, stepping: 00)
    May 07 17:54:22 workArchPC kernel: Performance Events: Fam15h core perfctr, AMD PMU driver.
    May 07 17:54:22 workArchPC kernel: ... version: 0
    May 07 17:54:22 workArchPC kernel: ... bit width: 48
    May 07 17:54:22 workArchPC kernel: ... generic registers: 6
    May 07 17:54:22 workArchPC kernel: ... value mask: 0000ffffffffffff
    May 07 17:54:22 workArchPC kernel: ... max period: 00007fffffffffff
    May 07 17:54:22 workArchPC kernel: ... fixed-purpose events: 0
    May 07 17:54:22 workArchPC kernel: ... event mask: 000000000000003f
    May 07 17:54:22 workArchPC kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    May 07 17:54:22 workArchPC kernel: x86: Booting SMP configuration:
    May 07 17:54:22 workArchPC kernel: .... node #0, CPUs: #1 #2 #3 #4 #5 #6 #7
    May 07 17:54:22 workArchPC kernel: x86: Booted up 1 node, 8 CPUs
    May 07 17:54:22 workArchPC kernel: smpboot: Total of 8 processors activated (75483.00 BogoMIPS)
    May 07 17:54:22 workArchPC kernel: devtmpfs: initialized
    May 07 17:54:22 workArchPC kernel: PM: Registering ACPI NVS region [mem 0xbab4f000-0xbb956fff] (14712832 bytes)
    May 07 17:54:22 workArchPC kernel: PM: Registering ACPI NVS region [mem 0xbca35000-0xbcc3afff] (2121728 bytes)
    May 07 17:54:22 workArchPC kernel: pinctrl core: initialized pinctrl subsystem
    May 07 17:54:22 workArchPC kernel: RTC time: 21:54:19, date: 05/07/15
    May 07 17:54:22 workArchPC kernel: NET: Registered protocol family 16
    May 07 17:54:22 workArchPC kernel: cpuidle: using governor ladder
    May 07 17:54:22 workArchPC kernel: cpuidle: using governor menu
    May 07 17:54:22 workArchPC kernel: ACPI: bus type PCI registered
    May 07 17:54:22 workArchPC kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
    May 07 17:54:22 workArchPC kernel: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
    May 07 17:54:22 workArchPC kernel: PCI: not using MMCONFIG
    May 07 17:54:22 workArchPC kernel: PCI: Using configuration type 1 for base access
    May 07 17:54:22 workArchPC kernel: PCI: Using configuration type 1 for extended access
    May 07 17:54:22 workArchPC kernel: mtrr: your CPUs had inconsistent variable MTRR settings
    May 07 17:54:22 workArchPC kernel: mtrr: probably your BIOS does not setup all CPUs.
    May 07 17:54:22 workArchPC kernel: mtrr: corrected configuration.
    May 07 17:54:22 workArchPC kernel: ACPI: Added _OSI(Module Device)
    May 07 17:54:22 workArchPC kernel: ACPI: Added _OSI(Processor Device)
    May 07 17:54:22 workArchPC kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
    May 07 17:54:22 workArchPC kernel: ACPI: Added _OSI(Processor Aggregator Device)
    May 07 17:54:22 workArchPC kernel: ACPI: Executed 2 blocks of module-level executable AML code
    May 07 17:54:22 workArchPC kernel: ACPI: Interpreter enabled
    May 07 17:54:22 workArchPC kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20150204/hwxface-580)
    May 07 17:54:22 workArchPC kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150204/hwxface-580)
    May 07 17:54:22 workArchPC kernel: ACPI: (supports S0 S3 S4 S5)
    May 07 17:54:22 workArchPC kernel: ACPI: Using IOAPIC for interrupt routing
    May 07 17:54:22 workArchPC kernel: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
    May 07 17:54:22 workArchPC kernel: PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
    May 07 17:54:22 workArchPC kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    May 07 17:54:22 workArchPC kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    May 07 17:54:22 workArchPC kernel: acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
    May 07 17:54:22 workArchPC kernel: acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
    May 07 17:54:22 workArchPC kernel: PCI host bridge to bus 0000:00
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x03af window]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:00: root bus resource [io 0x03e0-0x0cf7 window]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:00: root bus resource [io 0x03b0-0x03df window]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000dffff window]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:00: root bus resource [mem 0xc0000000-0xffffffff window]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:00.0: [1002:5a14] type 00 class 0x060000
    May 07 17:54:22 workArchPC kernel: pci 0000:00:00.2: [1002:5a23] type 00 class 0x080600
    May 07 17:54:22 workArchPC kernel: pci 0000:00:02.0: [1002:5a16] type 01 class 0x060400
    May 07 17:54:22 workArchPC kernel: pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
    May 07 17:54:22 workArchPC kernel: pci 0000:00:02.0: System wakeup disabled by ACPI
    May 07 17:54:22 workArchPC kernel: pci 0000:00:04.0: [1002:5a18] type 01 class 0x060400
    May 07 17:54:22 workArchPC kernel: pci 0000:00:04.0: PME# supported from D0 D3hot D3cold
    May 07 17:54:22 workArchPC kernel: pci 0000:00:04.0: System wakeup disabled by ACPI
    May 07 17:54:22 workArchPC kernel: pci 0000:00:05.0: [1002:5a19] type 01 class 0x060400
    May 07 17:54:22 workArchPC kernel: pci 0000:00:05.0: PME# supported from D0 D3hot D3cold
    May 07 17:54:22 workArchPC kernel: pci 0000:00:05.0: System wakeup disabled by ACPI
    May 07 17:54:22 workArchPC kernel: pci 0000:00:09.0: [1002:5a1c] type 01 class 0x060400
    May 07 17:54:22 workArchPC kernel: pci 0000:00:09.0: PME# supported from D0 D3hot D3cold
    May 07 17:54:22 workArchPC kernel: pci 0000:00:09.0: System wakeup disabled by ACPI
    May 07 17:54:22 workArchPC kernel: pci 0000:00:0a.0: [1002:5a1d] type 01 class 0x060400
    May 07 17:54:22 workArchPC kernel: pci 0000:00:0a.0: PME# supported from D0 D3hot D3cold
    May 07 17:54:22 workArchPC kernel: pci 0000:00:0a.0: System wakeup disabled by ACPI
    May 07 17:54:22 workArchPC kernel: pci 0000:00:0b.0: [1002:5a1f] type 01 class 0x060400
    May 07 17:54:22 workArchPC kernel: pci 0000:00:0b.0: PME# supported from D0 D3hot D3cold
    May 07 17:54:22 workArchPC kernel: pci 0000:00:0b.0: System wakeup disabled by ACPI
    May 07 17:54:22 workArchPC kernel: pci 0000:00:0d.0: [1002:5a1e] type 01 class 0x060400
    May 07 17:54:22 workArchPC kernel: pci 0000:00:0d.0: PME# supported from D0 D3hot D3cold
    May 07 17:54:22 workArchPC kernel: pci 0000:00:0d.0: System wakeup disabled by ACPI
    May 07 17:54:22 workArchPC kernel: pci 0000:00:11.0: [1002:4391] type 00 class 0x010601
    May 07 17:54:22 workArchPC kernel: pci 0000:00:11.0: reg 0x10: [io 0xf040-0xf047]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:11.0: reg 0x14: [io 0xf030-0xf033]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:11.0: reg 0x18: [io 0xf020-0xf027]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:11.0: reg 0x1c: [io 0xf010-0xf013]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:11.0: reg 0x20: [io 0xf000-0xf00f]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:11.0: reg 0x24: [mem 0xfe60b000-0xfe60b3ff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:12.0: [1002:4397] type 00 class 0x0c0310
    May 07 17:54:22 workArchPC kernel: pci 0000:00:12.0: reg 0x10: [mem 0xfe60a000-0xfe60afff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:12.0: System wakeup disabled by ACPI
    May 07 17:54:22 workArchPC kernel: pci 0000:00:12.2: [1002:4396] type 00 class 0x0c0320
    May 07 17:54:22 workArchPC kernel: pci 0000:00:12.2: reg 0x10: [mem 0xfe609000-0xfe6090ff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:12.2: supports D1 D2
    May 07 17:54:22 workArchPC kernel: pci 0000:00:12.2: PME# supported from D0 D1 D2 D3hot
    May 07 17:54:22 workArchPC kernel: pci 0000:00:12.2: System wakeup disabled by ACPI
    May 07 17:54:22 workArchPC kernel: pci 0000:00:13.0: [1002:4397] type 00 class 0x0c0310
    May 07 17:54:22 workArchPC kernel: pci 0000:00:13.0: reg 0x10: [mem 0xfe608000-0xfe608fff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:13.0: System wakeup disabled by ACPI
    May 07 17:54:22 workArchPC kernel: pci 0000:00:13.2: [1002:4396] type 00 class 0x0c0320
    May 07 17:54:22 workArchPC kernel: pci 0000:00:13.2: reg 0x10: [mem 0xfe607000-0xfe6070ff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:13.2: supports D1 D2
    May 07 17:54:22 workArchPC kernel: pci 0000:00:13.2: PME# supported from D0 D1 D2 D3hot
    May 07 17:54:22 workArchPC kernel: pci 0000:00:13.2: System wakeup disabled by ACPI
    May 07 17:54:22 workArchPC kernel: pci 0000:00:14.0: [1002:4385] type 00 class 0x0c0500
    May 07 17:54:22 workArchPC kernel: pci 0000:00:14.2: [1002:4383] type 00 class 0x040300
    May 07 17:54:22 workArchPC kernel: pci 0000:00:14.2: reg 0x10: [mem 0xfe600000-0xfe603fff 64bit]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:14.2: PME# supported from D0 D3hot D3cold
    May 07 17:54:22 workArchPC kernel: pci 0000:00:14.2: System wakeup disabled by ACPI
    May 07 17:54:22 workArchPC kernel: pci 0000:00:14.3: [1002:439d] type 00 class 0x060100
    May 07 17:54:22 workArchPC kernel: pci 0000:00:14.4: [1002:4384] type 01 class 0x060401
    May 07 17:54:22 workArchPC kernel: pci 0000:00:14.4: System wakeup disabled by ACPI
    May 07 17:54:22 workArchPC kernel: pci 0000:00:14.5: [1002:4399] type 00 class 0x0c0310
    May 07 17:54:22 workArchPC kernel: pci 0000:00:14.5: reg 0x10: [mem 0xfe606000-0xfe606fff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:14.5: System wakeup disabled by ACPI
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.0: [1002:43a0] type 01 class 0x060400
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.0: supports D1 D2
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.0: System wakeup disabled by ACPI
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.1: [1002:43a1] type 01 class 0x060400
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.1: supports D1 D2
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.1: System wakeup disabled by ACPI
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.2: [1002:43a2] type 01 class 0x060400
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.2: supports D1 D2
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.2: System wakeup disabled by ACPI
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.3: [1002:43a3] type 01 class 0x060400
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.3: supports D1 D2
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.3: System wakeup disabled by ACPI
    May 07 17:54:22 workArchPC kernel: pci 0000:00:16.0: [1002:4397] type 00 class 0x0c0310
    May 07 17:54:22 workArchPC kernel: pci 0000:00:16.0: reg 0x10: [mem 0xfe605000-0xfe605fff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:16.0: System wakeup disabled by ACPI
    May 07 17:54:22 workArchPC kernel: pci 0000:00:16.2: [1002:4396] type 00 class 0x0c0320
    May 07 17:54:22 workArchPC kernel: pci 0000:00:16.2: reg 0x10: [mem 0xfe604000-0xfe6040ff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:16.2: supports D1 D2
    May 07 17:54:22 workArchPC kernel: pci 0000:00:16.2: PME# supported from D0 D1 D2 D3hot
    May 07 17:54:22 workArchPC kernel: pci 0000:00:16.2: System wakeup disabled by ACPI
    May 07 17:54:22 workArchPC kernel: pci 0000:00:18.0: [1022:1600] type 00 class 0x060000
    May 07 17:54:22 workArchPC kernel: pci 0000:00:18.1: [1022:1601] type 00 class 0x060000
    May 07 17:54:22 workArchPC kernel: pci 0000:00:18.2: [1022:1602] type 00 class 0x060000
    May 07 17:54:22 workArchPC kernel: pci 0000:00:18.3: [1022:1603] type 00 class 0x060000
    May 07 17:54:22 workArchPC kernel: pci 0000:00:18.4: [1022:1604] type 00 class 0x060000
    May 07 17:54:22 workArchPC kernel: pci 0000:00:18.5: [1022:1605] type 00 class 0x060000
    May 07 17:54:22 workArchPC kernel: pci 0000:01:00.0: [10de:1381] type 00 class 0x030000
    May 07 17:54:22 workArchPC kernel: pci 0000:01:00.0: reg 0x10: [mem 0xfd000000-0xfdffffff]
    May 07 17:54:22 workArchPC kernel: pci 0000:01:00.0: reg 0x14: [mem 0xc0000000-0xcfffffff 64bit pref]
    May 07 17:54:22 workArchPC kernel: pci 0000:01:00.0: reg 0x1c: [mem 0xd0000000-0xd1ffffff 64bit pref]
    May 07 17:54:22 workArchPC kernel: pci 0000:01:00.0: reg 0x24: [io 0xe000-0xe07f]
    May 07 17:54:22 workArchPC kernel: pci 0000:01:00.0: reg 0x30: [mem 0xfe000000-0xfe07ffff pref]
    May 07 17:54:22 workArchPC kernel: pci 0000:01:00.1: [10de:0fbc] type 00 class 0x040300
    May 07 17:54:22 workArchPC kernel: pci 0000:01:00.1: reg 0x10: [mem 0xfe080000-0xfe083fff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:02.0: PCI bridge to [bus 01]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:02.0: bridge window [io 0xe000-0xefff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:02.0: bridge window [mem 0xfd000000-0xfe0fffff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:02.0: bridge window [mem 0xc0000000-0xd1ffffff 64bit pref]
    May 07 17:54:22 workArchPC kernel: pci 0000:02:00.0: [1b21:0612] type 00 class 0x010601
    May 07 17:54:22 workArchPC kernel: pci 0000:02:00.0: reg 0x10: [io 0xd050-0xd057]
    May 07 17:54:22 workArchPC kernel: pci 0000:02:00.0: reg 0x14: [io 0xd040-0xd043]
    May 07 17:54:22 workArchPC kernel: pci 0000:02:00.0: reg 0x18: [io 0xd030-0xd037]
    May 07 17:54:22 workArchPC kernel: pci 0000:02:00.0: reg 0x1c: [io 0xd020-0xd023]
    May 07 17:54:22 workArchPC kernel: pci 0000:02:00.0: reg 0x20: [io 0xd000-0xd01f]
    May 07 17:54:22 workArchPC kernel: pci 0000:02:00.0: reg 0x24: [mem 0xfe500000-0xfe5001ff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:04.0: PCI bridge to [bus 02]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:04.0: bridge window [io 0xd000-0xdfff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:04.0: bridge window [mem 0xfe500000-0xfe5fffff]
    May 07 17:54:22 workArchPC kernel: pci 0000:03:00.0: [1b21:0612] type 00 class 0x010601
    May 07 17:54:22 workArchPC kernel: pci 0000:03:00.0: reg 0x10: [io 0xc050-0xc057]
    May 07 17:54:22 workArchPC kernel: pci 0000:03:00.0: reg 0x14: [io 0xc040-0xc043]
    May 07 17:54:22 workArchPC kernel: pci 0000:03:00.0: reg 0x18: [io 0xc030-0xc037]
    May 07 17:54:22 workArchPC kernel: pci 0000:03:00.0: reg 0x1c: [io 0xc020-0xc023]
    May 07 17:54:22 workArchPC kernel: pci 0000:03:00.0: reg 0x20: [io 0xc000-0xc01f]
    May 07 17:54:22 workArchPC kernel: pci 0000:03:00.0: reg 0x24: [mem 0xfe400000-0xfe4001ff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:05.0: PCI bridge to [bus 03]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:05.0: bridge window [io 0xc000-0xcfff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:05.0: bridge window [mem 0xfe400000-0xfe4fffff]
    May 07 17:54:22 workArchPC kernel: pci 0000:04:00.0: [1b21:1142] type 00 class 0x0c0330
    May 07 17:54:22 workArchPC kernel: pci 0000:04:00.0: reg 0x10: [mem 0xfe300000-0xfe307fff 64bit]
    May 07 17:54:22 workArchPC kernel: pci 0000:04:00.0: PME# supported from D3cold
    May 07 17:54:22 workArchPC kernel: pci 0000:00:09.0: PCI bridge to [bus 04]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:09.0: bridge window [mem 0xfe300000-0xfe3fffff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:0a.0: PCI bridge to [bus 05]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:0b.0: PCI bridge to [bus 06]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:0d.0: PCI bridge to [bus 07]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:14.4: PCI bridge to [bus 08] (subtractive decode)
    May 07 17:54:22 workArchPC kernel: pci 0000:00:14.4: bridge window [io 0x0000-0x03af window] (subtractive decode)
    May 07 17:54:22 workArchPC kernel: pci 0000:00:14.4: bridge window [io 0x03e0-0x0cf7 window] (subtractive decode)
    May 07 17:54:22 workArchPC kernel: pci 0000:00:14.4: bridge window [io 0x03b0-0x03df window] (subtractive decode)
    May 07 17:54:22 workArchPC kernel: pci 0000:00:14.4: bridge window [io 0x0d00-0xffff window] (subtractive decode)
    May 07 17:54:22 workArchPC kernel: pci 0000:00:14.4: bridge window [mem 0x000a0000-0x000bffff window] (subtractive decode)
    May 07 17:54:22 workArchPC kernel: pci 0000:00:14.4: bridge window [mem 0x000c0000-0x000dffff window] (subtractive decode)
    May 07 17:54:22 workArchPC kernel: pci 0000:00:14.4: bridge window [mem 0xc0000000-0xffffffff window] (subtractive decode)
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.0: PCI bridge to [bus 09]
    May 07 17:54:22 workArchPC kernel: pci 0000:0a:00.0: [10ec:8168] type 00 class 0x020000
    May 07 17:54:22 workArchPC kernel: pci 0000:0a:00.0: reg 0x10: [io 0xb000-0xb0ff]
    May 07 17:54:22 workArchPC kernel: pci 0000:0a:00.0: reg 0x18: [mem 0xd2104000-0xd2104fff 64bit pref]
    May 07 17:54:22 workArchPC kernel: pci 0000:0a:00.0: reg 0x20: [mem 0xd2100000-0xd2103fff 64bit pref]
    May 07 17:54:22 workArchPC kernel: pci 0000:0a:00.0: supports D1 D2
    May 07 17:54:22 workArchPC kernel: pci 0000:0a:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.1: PCI bridge to [bus 0a]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.1: bridge window [io 0xb000-0xbfff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.1: bridge window [mem 0xd2100000-0xd21fffff 64bit pref]
    May 07 17:54:22 workArchPC kernel: pci 0000:0b:00.0: [1b21:1142] type 00 class 0x0c0330
    May 07 17:54:22 workArchPC kernel: pci 0000:0b:00.0: reg 0x10: [mem 0xfe200000-0xfe207fff 64bit]
    May 07 17:54:22 workArchPC kernel: pci 0000:0b:00.0: PME# supported from D3cold
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.2: PCI bridge to [bus 0b]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.2: bridge window [mem 0xfe200000-0xfe2fffff]
    May 07 17:54:22 workArchPC kernel: pci 0000:0c:00.0: [1b21:1142] type 00 class 0x0c0330
    May 07 17:54:22 workArchPC kernel: pci 0000:0c:00.0: reg 0x10: [mem 0xfe100000-0xfe107fff 64bit]
    May 07 17:54:22 workArchPC kernel: pci 0000:0c:00.0: PME# supported from D3cold
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.3: PCI bridge to [bus 0c]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.3: bridge window [mem 0xfe100000-0xfe1fffff]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:00: on NUMA node 0
    May 07 17:54:22 workArchPC kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 4 7 10 11 14 15) *0
    May 07 17:54:22 workArchPC kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 4 7 10 11 14 15) *0
    May 07 17:54:22 workArchPC kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 4 7 10 11 14 15) *0
    May 07 17:54:22 workArchPC kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 10 11 14 15) *0
    May 07 17:54:22 workArchPC kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 4 7 10 11 14 15) *0
    May 07 17:54:22 workArchPC kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 4 7 10 11 14 15) *0
    May 07 17:54:22 workArchPC kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 4 7 10 11 14 15) *0
    May 07 17:54:22 workArchPC kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 4 7 10 11 14 15) *0
    May 07 17:54:22 workArchPC kernel: ACPI: Enabled 1 GPEs in block 00 to 1F
    May 07 17:54:22 workArchPC kernel: ACPI : EC: GPE = 0xa, I/O: command/status = 0x66, data = 0x62
    May 07 17:54:22 workArchPC kernel: vgaarb: setting as boot device: PCI:0000:01:00.0
    May 07 17:54:22 workArchPC kernel: vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
    May 07 17:54:22 workArchPC kernel: vgaarb: loaded
    May 07 17:54:22 workArchPC kernel: vgaarb: bridge control possible 0000:01:00.0
    May 07 17:54:22 workArchPC kernel: PCI: Using ACPI for IRQ routing
    May 07 17:54:22 workArchPC kernel: PCI: pci_cache_line_size set to 64 bytes
    May 07 17:54:22 workArchPC kernel: e820: reserve RAM buffer [mem 0x0009e800-0x0009ffff]
    May 07 17:54:22 workArchPC kernel: e820: reserve RAM buffer [mem 0xba70b000-0xbbffffff]
    May 07 17:54:22 workArchPC kernel: e820: reserve RAM buffer [mem 0xbca35000-0xbfffffff]
    May 07 17:54:22 workArchPC kernel: e820: reserve RAM buffer [mem 0xbd083000-0xbfffffff]
    May 07 17:54:22 workArchPC kernel: e820: reserve RAM buffer [mem 0xbd800000-0xbfffffff]
    May 07 17:54:22 workArchPC kernel: e820: reserve RAM buffer [mem 0x83f000000-0x83fffffff]
    May 07 17:54:22 workArchPC kernel: NetLabel: Initializing
    May 07 17:54:22 workArchPC kernel: NetLabel: domain hash size = 128
    May 07 17:54:22 workArchPC kernel: NetLabel: protocols = UNLABELED CIPSOv4
    May 07 17:54:22 workArchPC kernel: NetLabel: unlabeled traffic allowed by default
    May 07 17:54:22 workArchPC kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
    May 07 17:54:22 workArchPC kernel: hpet0: 3 comparators, 32-bit 14.318180 MHz counter
    May 07 17:54:22 workArchPC kernel: Switched to clocksource hpet
    May 07 17:54:22 workArchPC kernel: pnp: PnP ACPI init
    May 07 17:54:22 workArchPC kernel: system 00:00: [mem 0xe0000000-0xefffffff] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
    May 07 17:54:22 workArchPC kernel: system 00:01: [io 0x040b] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: [io 0x04d6] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: [io 0x0c00-0x0c01] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: [io 0x0c14] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: [io 0x0c50-0x0c51] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: [io 0x0c52] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: [io 0x0c6c] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: [io 0x0c6f] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: [io 0x0cd0-0x0cd1] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: [io 0x0cd2-0x0cd3] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: [io 0x0cd4-0x0cd5] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: [io 0x0cd6-0x0cd7] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: [io 0x0cd8-0x0cdf] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: [io 0x0800-0x089f] could not be reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: [io 0x0b20-0x0b3f] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: [io 0x0900-0x090f] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: [io 0x0910-0x091f] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: [io 0xfe00-0xfefe] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: [mem 0xfec00000-0xfec00fff] could not be reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: [mem 0xfee00000-0xfee00fff] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: [mem 0xfed80000-0xfed8ffff] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: [mem 0xfed61000-0xfed70fff] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: [mem 0xfec10000-0xfec10fff] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: [mem 0xfed00000-0xfed00fff] could not be reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: [mem 0xff800000-0xffffffff] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 07 17:54:22 workArchPC kernel: system 00:02: [io 0x0290-0x02af] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 07 17:54:22 workArchPC kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
    May 07 17:54:22 workArchPC kernel: system 00:04: [io 0x04d0-0x04d1] has been reserved
    May 07 17:54:22 workArchPC kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 07 17:54:22 workArchPC kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 07 17:54:22 workArchPC kernel: pnp 00:06: Plug and Play ACPI device, IDs PNP0303 PNP030b (active)
    May 07 17:54:22 workArchPC kernel: pnp 00:07: [dma 0 disabled]
    May 07 17:54:22 workArchPC kernel: pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
    May 07 17:54:22 workArchPC kernel: system 00:08: [mem 0xfeb20000-0xfeb23fff] could not be reserved
    May 07 17:54:22 workArchPC kernel: system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 07 17:54:22 workArchPC kernel: system 00:09: [mem 0xfec20000-0xfec200ff] could not be reserved
    May 07 17:54:22 workArchPC kernel: system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
    May 07 17:54:22 workArchPC kernel: pnp: PnP ACPI: found 10 devices
    May 07 17:54:22 workArchPC kernel: pci 0000:00:02.0: PCI bridge to [bus 01]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:02.0: bridge window [io 0xe000-0xefff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:02.0: bridge window [mem 0xfd000000-0xfe0fffff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:02.0: bridge window [mem 0xc0000000-0xd1ffffff 64bit pref]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:04.0: PCI bridge to [bus 02]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:04.0: bridge window [io 0xd000-0xdfff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:04.0: bridge window [mem 0xfe500000-0xfe5fffff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:05.0: PCI bridge to [bus 03]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:05.0: bridge window [io 0xc000-0xcfff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:05.0: bridge window [mem 0xfe400000-0xfe4fffff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:09.0: PCI bridge to [bus 04]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:09.0: bridge window [mem 0xfe300000-0xfe3fffff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:0a.0: PCI bridge to [bus 05]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:0b.0: PCI bridge to [bus 06]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:0d.0: PCI bridge to [bus 07]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:14.4: PCI bridge to [bus 08]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.0: PCI bridge to [bus 09]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.1: PCI bridge to [bus 0a]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.1: bridge window [io 0xb000-0xbfff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.1: bridge window [mem 0xd2100000-0xd21fffff 64bit pref]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.2: PCI bridge to [bus 0b]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.2: bridge window [mem 0xfe200000-0xfe2fffff]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.3: PCI bridge to [bus 0c]
    May 07 17:54:22 workArchPC kernel: pci 0000:00:15.3: bridge window [mem 0xfe100000-0xfe1fffff]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x03af window]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:00: resource 5 [io 0x03e0-0x0cf7 window]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:00: resource 6 [io 0x03b0-0x03df window]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:00: resource 7 [io 0x0d00-0xffff window]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff window]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:00: resource 9 [mem 0x000c0000-0x000dffff window]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:00: resource 10 [mem 0xc0000000-0xffffffff window]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:01: resource 1 [mem 0xfd000000-0xfe0fffff]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:01: resource 2 [mem 0xc0000000-0xd1ffffff 64bit pref]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:02: resource 0 [io 0xd000-0xdfff]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:02: resource 1 [mem 0xfe500000-0xfe5fffff]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:03: resource 0 [io 0xc000-0xcfff]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:03: resource 1 [mem 0xfe400000-0xfe4fffff]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:04: resource 1 [mem 0xfe300000-0xfe3fffff]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:08: resource 4 [io 0x0000-0x03af window]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:08: resource 5 [io 0x03e0-0x0cf7 window]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:08: resource 6 [io 0x03b0-0x03df window]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:08: resource 7 [io 0x0d00-0xffff window]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:08: resource 8 [mem 0x000a0000-0x000bffff window]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:08: resource 9 [mem 0x000c0000-0x000dffff window]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:08: resource 10 [mem 0xc0000000-0xffffffff window]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:0a: resource 0 [io 0xb000-0xbfff]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:0a: resource 2 [mem 0xd2100000-0xd21fffff 64bit pref]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:0b: resource 1 [mem 0xfe200000-0xfe2fffff]
    May 07 17:54:22 workArchPC kernel: pci_bus 0000:0c: resource 1 [mem 0xfe100000-0xfe1fffff]
    May 07 17:54:22 workArchPC kernel: NET: Registered protocol family 2
    May 07 17:54:22 workArchPC kernel: TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
    May 07 17:54:22 workArchPC kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
    May 07 17:54:22 workArchPC kernel: TCP: Hash tables configured (established 262144 bind 65536)
    May 07 17:54:22 workArchPC kernel: TCP: reno registered
    May 07 17:54:22 workArchPC kernel: UDP hash table entries: 16384 (order: 7, 524288 bytes)
    May 07 17:54:22 workArchPC kernel: UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
    May 07 17:54:22 workArchPC kernel: NET: Registered protocol family 1
    May 07 17:54:22 workArchPC kernel: pci 0000:01:00.0: Video device with shadowed ROM
    May 07 17:54:22 workArchPC kernel: PCI: CLS 64 bytes, default 64
    May 07 17:54:22 workArchPC kernel: Unpacking initramfs...
    May 07 17:54:22 workArchPC kernel: Freeing initrd memory: 8944K (ffff880036e78000 - ffff880037734000)
    May 07 17:54:22 workArchPC kernel: AMD-Vi: Found IOMMU at 0000:00:00.2 cap 0x40
    May 07 17:54:22 workArchPC kernel: AMD-Vi: Interrupt remapping enabled
    May 07 17:54:22 workArchPC kernel: AMD-Vi: Lazy IO/TLB flushing enabled
    May 07 17:54:22 workArchPC kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
    May 07 17:54:22 workArchPC kernel: software IO TLB [mem 0xb670b000-0xba70b000] (64MB) mapped at [ffff8800b670b000-ffff8800ba70afff]
    May 07 17:54:22 workArchPC kernel: perf: AMD NB counters detected
    May 07 17:54:22 workArchPC kernel: microcode: CPU0: patch_level=0x06000822
    May 07 17:54:22 workArchPC kernel: microcode: CPU1: patch_level=0x06000822
    May 07 17:54:22 workArchPC kernel: microcode: CPU2: patch_level=0x06000822
    May 07 17:54:22 workArchPC kernel: microcode: CPU3: patch_level=0x06000822
    May 07 17:54:22 workArchPC kernel: microcode: CPU4: patch_level=0x06000822
    May 07 17:54:22 workArchPC kernel: microcode: CPU5: patch_level=0x06000822
    May 07 17:54:22 workArchPC kernel: microcode: CPU6: patch_level=0x06000822
    May 07 17:54:22 workArchPC kernel: microcode: CPU7: patch_level=0x06000822
    May 07 17:54:22 workArchPC kernel: microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
    May 07 17:54:22 workArchPC kernel: LVT offset 0 assigned for vector 0x400
    May 07 17:54:22 workArchPC kernel: perf: AMD IBS detected (0x000000ff)
    May 07 17:54:22 workArchPC kernel: Scanning for low memory corruption every 60 seconds
    May 07 17:54:22 workArchPC kernel: futex hash table entries: 2048 (order: 5, 131072 bytes)
    May 07 17:54:22 workArchPC kernel: Initialise system trusted keyring
    May 07 17:54:22 workArchPC kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
    May 07 17:54:22 workArchPC kernel: zpool: loaded
    May 07 17:54:22 workArchPC kernel: zbud: loaded
    May 07 17:54:22 workArchPC kernel: VFS: Disk quotas dquot_6.5.2
    May 07 17:54:22 workArchPC kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    May 07 17:54:22 workArchPC kernel: Key type big_key registered
    May 07 17:54:22 workArchPC kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    May 07 17:54:22 workArchPC kernel: io scheduler noop registered
    May 07 17:54:22 workArchPC kernel: io scheduler deadline registered
    May 07 17:54:22 workArchPC kernel: io scheduler cfq registered (default)
    May 07 17:54:22 workArchPC kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    May 07 17:54:22 workArchPC kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
    May 07 17:54:22 workArchPC kernel: vesafb: mode is 1920x1080x32, linelength=7680, pages=0
    May 07 17:54:22 workArchPC kernel: vesafb: scrolling: redraw
    May 07 17:54:22 workArchPC kernel: vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
    May 07 17:54:22 workArchPC kernel: vesafb: framebuffer at 0xd1000000, mapped to 0xffffc90013600000, using 8128k, total 8128k
    May 07 17:54:22 workArchPC kernel: Console: switching to colour frame buffer device 240x67
    May 07 17:54:22 workArchPC kernel: fb0: VESA VGA frame buffer device
    May 07 17:54:22 workArchPC kernel: GHES: HEST is not enabled!
    May 07 17:54:22 workArchPC kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    May 07 17:54:22 workArchPC kernel: 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
    May 07 17:54:22 workArchPC kernel: Linux agpgart interface v0.103
    May 07 17:54:22 workArchPC kernel: rtc_cmos 00:03: RTC can wake from S4
    May 07 17:54:22 workArchPC kernel: rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
    May 07 17:54:22 workArchPC kernel: rtc_cmos 00:03: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
    May 07 17:54:22 workArchPC kernel: ledtrig-cpu: registered to indicate activity on CPUs
    May 07 17:54:22 workArchPC kernel: TCP: cubic registered
    May 07 17:54:22 workArchPC kernel: NET: Registered protocol family 10
    May 07 17:54:22 workArchPC kernel: NET: Registered protocol family 17
    May 07 17:54:22 workArchPC kernel: Loading compiled-in X.509 certificates
    May 07 17:54:22 workArchPC kernel: registered taskstats version 1
    May 07 17:54:22 workArchPC kernel: Magic number: 15:637:954
    May 07 17:54:22 workArchPC kernel: memory memory7: hash matches
    May 07 17:54:22 workArchPC kernel: rtc_cmos 00:03: setting system clock to 2015-05-07 21:54:20 UTC (1431035660)
    May 07 17:54:22 workArchPC kernel: PM: Hibernation image not present or could not be loaded.
    May 07 17:54:22 workArchPC kernel: Freeing unused kernel memory: 1160K (ffffffff818d2000 - ffffffff819f4000)
    May 07 17:54:22 workArchPC kernel: Write protecting the kernel read-only data: 8192k
    May 07 17:54:22 workArchPC kernel: Freeing unused kernel memory: 532K (ffff88000157b000 - ffff880001600000)
    May 07 17:54:22 workArchPC kernel: Freeing unused kernel memory: 272K (ffff8800017bc000 - ffff880001800000)
    May 07 17:54:22 workArchPC kernel: random: systemd-tmpfile urandom read with 1 bits of entropy available
    May 07 17:54:22 workArchPC kernel: device-mapper: uevent: version 1.0.3
    May 07 17:54:22 workArchPC kernel: device-mapper: ioctl: 4.30.0-ioctl (2014-12-22) initialised: [email protected]
    May 07 17:54:22 workArchPC kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
    May 07 17:54:22 workArchPC kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
    May 07 17:54:22 workArchPC kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
    May 07 17:54:22 workArchPC kernel: SCSI subsystem initialized
    May 07 17:54:22 workArchPC kernel: ACPI: bus type USB registered
    May 07 17:54:22 workArchPC kernel: usbcore: registered new interface driver usbfs
    May 07 17:54:22 workArchPC kernel: usbcore: registered new interface driver hub
    May 07 17:54:22 workArchPC kernel: usbcore: registered new device driver usb
    May 07 17:54:22 workArchPC kernel: libata version 3.00 loaded.
    May 07 17:54:22 workArchPC kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    May 07 17:54:22 workArchPC kernel: QUIRK: Enable AMD PLL fix
    May 07 17:54:22 workArchPC kernel: xhci_hcd 0000:04:00.0: xHCI Host Controller
    May 07 17:54:22 workArchPC kernel: xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 1
    May 07 17:54:22 workArchPC kernel: ehci-pci: EHCI PCI platform driver
    May 07 17:54:22 workArchPC kernel: ohci_hcd: USB

    My thinking is that Plasma is not "playing" nicely with nvidia, I have two systems in my pc, one with kde4 and the other one (my testing system) with plasma, kde4 runs as it should, no lags, no freezes, no redrawing problems, fast and smooth. My plasma system is really not there, I tweak both systems the same, 20-nvidia.config on the xorg.d folder created by the nvidia settings, same where I also tweak all settings to juice my video card to its fullest (a really weak one by the way, a fanless gt430) and the triple buffering enabled for kde. I do have freezes with Plasma that lock the whole system, no keyboard input, and its been more or less the same since its release (for me that is), I am keep waiting to see if the "next" release would do, 5.3 still not yet. I also notice that compositing effects makes things worst, for example, snapping a window to a corner or to maximize when wobbly effect is on is a sure shot for a freeze for my system, I just update today the linux kernel and the nvidia driver, would see if that helps a little. My advice, for a stable system stick to kde4 still.
    Edit: Note, I have a good old amd phenom 6 cores and I always run it with some over-clocking, never have issues with that on my previous install or my main system.
    Last edited by RJQ (2015-05-08 15:43:16)

  • I am loosing configuration when I power off my Cisco 857 router

    I bought new Cisco 857 router from the shop. Router must have been used before as I couln't go in with default username/password cisco/cisco.
    Well I followed instruciton and reset password to username and password. Now I finally connected to the Cisco CP express over my IE browser.
    I found out that somebody was using a router from the shop so this is why I coun't log to it in the first place. Anyway problem is that when I changed configuration and applied settings it remembers it until I power it off. When I power it on again it remembers all settings from that shop.
    It reverts everything back: IP address, previous level 15 account and password - everything like after password reset.
    I tried it again and it again lost settings. So I found following instruction:
    http://www.cisco.com/en/US/products/hw/routers/ps233/products_tech_note09186a00800a65a5.shtml
    I followed it and changed again all settings on the router. My settings are again lost after power off/on. I noticed that when I do first bit it does show
    0x2102 not 0x2142 like they think that is password reset mode.
    Here is my output from Hyper Terminal:
    =============================
    Cisco#enableCisco#show startUsing 3359 out of 131072 bytes!version 12.4no service padservice timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!hostname Cisco!boot-start-markerboot-end-marker!logging buffered 51200 warningsenable secret 5 $1$hpKF$Rc1tl6r45J8iHG7EN5jSk.!no aaa new-model!crypto pki trustpoint TP-self-signed-3185909327 enrollment selfsigned subject-name cn=IOS-Self-Signed-Certificate-3185909327 revocation-check none rsakeypair TP-self-signed-3185909327!!crypto pki certificate chain TP-self-signed-3185909327 certificate self-signed 01 nvram:IOS-Self-Sig#5.cerdot11 syslogno ip dhcp use vrf connectedip dhcp excluded-address 10.10.10.1!ip dhcp pool ccp-pool   import all   network 10.10.10.0 255.255.255.248   default-router 10.10.10.1   lease 0 2!!ip cefno ip domain lookupip domain name molinary.com!!!username admin privilege 15 secret 5 $1$jD3j$r6ROikgGsIlcMTGjkxFQ6.username username privilege 15 password 0 password!!archive log config  hidekeys!!!!!interface ATM0 no ip address shutdown no atm ilmi-keepalive dsl operating-mode auto!interface ATM0.1 point-to-point description $ES_WAN$ ip nat outside ip virtual-reassembly pvc 0/38  encapsulation aal5mux ppp dialer  dialer pool-member 1 !!interface FastEthernet0!interface FastEthernet1!interface FastEthernet2!interface FastEthernet3!interface Vlan1 description $ETH-SW-LAUNCH$$INTF-INFO-HWIC 4ESW$$ES_LAN$ ip address 10.10.10.1 255.255.255.248 ip nat inside ip virtual-reassembly ip tcp adjust-mss 1452!interface Dialer0 ip address dhcp encapsulation ppp dialer pool 1 dialer-group 1 no cdp enable ppp authentication chap pap callin ppp chap hostname [email protected] ppp chap password 0 netgear01 ppp pap sent-username [email protected] password 0 netgear01!ip forward-protocol nd!ip http serverip http access-class 23ip http authentication localip http secure-serverip http timeout-policy idle 60 life 86400 requests 10000ip nat inside source list 1 interface ATM0.1 overload!access-list 1 remark INSIDE_IF=Vlan1access-list 1 remark CCP_ACL Category=2access-list 1 permit 10.10.10.0 0.0.0.7dialer-list 1 protocol ip permitno cdp run!control-plane!banner exec ^C% Password expiration warning.-----------------------------------------------------------------------Cisco Configuration Professional (Cisco CP) is installed on this deviceand it provides the default username "cisco" for  one-time use. If you havealready used the username "cisco" to login to the router and your IOS imagesupports the "one-time" user option, then this username has already expired.You will not be able to login to the router with this username after you exitthis session.It is strongly suggested that you create a new username with a privilege levelof 15 using the following command.username <myuser> privilege 15 secret 0 <mypassword>Replace <myuser> and <mypassword> with the username and password youwant to use.-----------------------------------------------------------------------^Cbanner login ^CAuthorized access only! Disconnect IMMEDIATELY if you are not an authorized user!^C!line con 0 login local no modem enableline aux 0line vty 0 4 privilege level 15 login local transport input telnet ssh!scheduler max-task-time 5000endCisco#Cisco#Cisco#Cisco#Cisco#Cisco#Cisco#Cisco#Cisco#show versionCisco IOS Software, C850 Software (C850-ADVSECURITYK9-M), Version 12.4(15)T12, RELEASE SOFTWARE (fc3)Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2010 by Cisco Systems, Inc.Compiled Fri 22-Jan-10 14:46 by prod_rel_teamROM: System Bootstrap, Version 12.3(8r)YI4, RELEASE SOFTWARECisco uptime is 20 minutesSystem returned to ROM by power-onSystem image file is "flash:c850-advsecurityk9-mz.124-15.T12.bin"This product contains cryptographic features and is subject to UnitedStates and local country laws governing import, export, transfer anduse. Delivery of Cisco cryptographic products does not implythird-party authority to import, export, distribute or use encryption.Importers, exporters, distributors and users are responsible forcompliance with U.S. and local country laws. By using this product youagree to comply with applicable laws and regulations. If you are unableto comply with U.S. and local laws, return this product immediately.A summary of U.S. laws governing Cisco cryptographic products may be found at:http://www.cisco.com/wwl/export/crypto/tool/stqrg.htmlIf you require further assistance please contact us by sending email [email protected] 857 (MPC8272) processor (revision 0x400) with 59392K/6144K bytes of memory.Processor board ID FCZ140792J5MPC8272 CPU Rev: Part Number 0xC, Mask Number 0x104 FastEthernet interfaces1 ATM interface128K bytes of non-volatile configuration memory.20480K bytes of processor board System flash (Intel Strataflash)Configuration register is 0x2102Cisco#Cisco#Cisco#Cisco#endTranslating "end"% Unknown command or computer name, or unable to find computer addressCisco#reloadProceed with reload? [confirm]*Mar  1 01:19:27.786: %SYS-5-RELOAD: Reload requested  by username on console. Reload Reason: Reload Command.System Bootstrap, Version 12.3(8r)YI4, RELEASE SOFTWARETechnical Support: http://www.cisco.com/techsupportCopyright (c) 2006 by cisco Systems, Inc.C850 series (Board ID: 2-149) platform with 65536 Kbytes of main memoryBooting flash:/c850-advsecurityk9-mz.124-15.T12.binSelf decompressing the image : ############################################## [OK]              Restricted Rights LegendUse, duplication, or disclosure by the Government issubject to restrictions as set forth in subparagraph(c) of the Commercial Computer Software - RestrictedRights clause at FAR sec. 52.227-19 and subparagraph(c) (1) (ii) of the Rights in Technical Data and ComputerSoftware clause at DFARS sec. 252.227-7013.           cisco Systems, Inc.           170 West Tasman Drive           San Jose, California 95134-1706Cisco IOS Software, C850 Software (C850-ADVSECURITYK9-M), Version 12.4(15)T12, RELEASE SOFTWARE (fc3)Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2010 by Cisco Systems, Inc.Compiled Fri 22-Jan-10 14:46 by prod_rel_teamImage text-base: 0x8002007C, data-base: 0x814E7240This product contains cryptographic features and is subject to UnitedStates and local country laws governing import, export, transfer anduse. Delivery of Cisco cryptographic products does not implythird-party authority to import, export, distribute or use encryption.Importers, exporters, distributors and users are responsible forcompliance with U.S. and local country laws. By using this product youagree to comply with applicable laws and regulations. If you are unableto comply with U.S. and local laws, return this product immediately.A summary of U.S. laws governing Cisco cryptographic products may be found at:http://www.cisco.com/wwl/export/crypto/tool/stqrg.htmlIf you require further assistance please contact us by sending email [email protected] 857 (MPC8272) processor (revision 0x400) with 59392K/6144K bytes of memory.Processor board ID FCZ140792J5MPC8272 CPU Rev: Part Number 0xC, Mask Number 0x104 FastEthernet interfaces1 ATM interface128K bytes of non-volatile configuration memory.20480K bytes of processor board System flash (Intel Strataflash)no ip dhcp use vrf connected               ^% Invalid input detected at '^' marker.SETUP: new interface NVI0 placed in "shutdown" statePress RETURN to get started!*Mar  1 00:00:03.952: %VPN_HW-6-INFO_LOC: Crypto engine: onboard 0  State changed to: Initialized*Mar  1 00:00:03.960: %VPN_HW-6-INFO_LOC: Crypto engine: onboard 0  State changed to: Enabled*Mar  1 00:00:07.244: %LINK-3-UPDOWN: Interface FastEthernet0, changed state toup*Mar  1 00:00:08.413: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to up*Mar  1 00:00:08.821: %SYS-5-CONFIG_I: Configured from memory by console*Mar  1 01:19:27.072: %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to up*Mar  1 01:19:27.352: %SYS-5-RESTART: System restarted --Cisco IOS Software, C850 Software (C850-ADVSECURITYK9-M), Version 12.4(15)T12, RELEASE SOFTWARE (fc3)Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2010 by Cisco Systems, Inc.Compiled Fri 22-Jan-10 14:46 by prod_rel_team*Mar  1 01:19:27.352: %SNMP-5-COLDSTART: SNMP agent on host Cisco is undergoinga cold start*Mar  1 01:19:27.436: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF*Mar  1 01:19:27.436: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF*Mar  1 01:19:27.540: %LINEPROTO-5-UPDOWN: Line protocol on Interface NVI0, changed state to down*Mar  1 01:19:28.072: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1, changed state to up*Mar  1 01:19:28.484: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up*Mar  1 01:19:28.484: %LINK-5-CHANGED: Interface ATM0, changed state to administratively down*Mar  1 01:19:28.848: %LINK-5-CHANGED: Interface NVI0, changed state to administratively down*Mar  1 01:19:28.932: %LINK-3-UPDOWN: Interface FastEthernet3, changed state toup*Mar  1 01:19:28.936: %LINK-3-UPDOWN: Interface FastEthernet2, changed state toup*Mar  1 01:19:28.940: %LINK-3-UPDOWN: Interface FastEthernet1, changed state toup*Mar  1 01:19:29.484: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down*Mar  1 01:19:29.932: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet3, changed state to down*Mar  1 01:19:29.936: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet2, changed state to down*Mar  1 01:19:29.940: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet1, changed state to down*Mar  1 01:19:29.948: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to upAuthorized access only!===========================================
    Please help me as I am stuck and can't go any further....

    Hi David White,
    Alternatively, after password recovery you can modify the configuration to be what you want, and then issue:
       write memory
    to save the configuration.  You can then verify that your changes have been saved to the startup config by issuing:
       show startup-config"
    The only good thing is that when I switch off a router it erase configuration except my new password which I created after password reset. Everything else is getting vanished (ADSL settings, DHCP, routing ) everything. Even new admin accounts I created.
    Well have a question to your above comments. I am new in Cisco so please put as much detail as you can for me to understand. When you say modify configuration do you mean to go to Cisco CP Express graphical interface and then connect router to hyper terminal and execute above commands?
    Why router doesn't remember this anyway. There must be some option to change in configuration to make thing permanent when I hit apply changes in Cisco CO Express otherwise it is pointless to heve it.
    Phillip
    write memory
    is
    copy running-config startup-config"
    Can't this be done via Cisco CP Express or set up router to copy this every time I change this in graphical interface rather going to command line to achnoledge it?
    I understand your concern about this router and somebodie's configuration details as you want things to be un-used when you buy them - true. ADSL details belongs to the shop which sold me the router so that is why I don't make a big problem about this. We take most of hardware from this shop and have discount and many good deals with them so I think they have been just testing it and forgot to erease their config. It might be that someone has returned router to the shop and they have repaired it and tested it.
    I hope this is a normal behaviour of this router as I have option to replace it in case this is a fault.
    Could you please write me step by step guide how can I make changed options stay permanently on router?
    thank you
    Dragan

  • My iPhone 4S has started to turn off before its out of battery. There is no pattern it is completely random so I don't know when it will turn off, when I try to turn it back on it says it needs to be charged.

    As soon as I plug it in to the charger it reboots to the same percent it was originally on before it turned off for example today it turned off on 10% I tried to turn it back in and it said out of battery so I plugged it in to the charger and it immediately rebooted showing the apple logo and the phone was on 10% when it was fully rebooted.
    I was wondering do I need a battery replacement or is this something more serious.
    Many thanks.

    Hi Lukeohiggins,
    If you are having issues with your iPhone unexpectely powering off, you may want to try the troubleshooting listed under Power/Battery > Will not turn on, will not turn on unless connected to power, or unexpected power off in the following article:
    iPhone: Hardware troubleshooting
    http://support.apple.com/kb/ts2802
    Cheers,
    - Brenden

  • Unable to Connect to WiFi after iPhone power off; WiFi &amp; internet are working with MBP; common problem, no solutions?

    Here's my setup: Internet <> Comcast/xFinity supplied cable modem <> new Apple Time Capsule <> iPhone 4 & MacBook Pro (see below for hardware details)
    Internet on my iPhone 4 has been acting slow since yesterday evening. My MacBook Pro was running fine, but just to be sure I checked the Comcast website to see that I have only used 50GB of my allotted 250 GB of data for the month, so it's not that.
    I decided it must be a problem with just my iPhone, so I opened up the multitasking bar and quit everything in there manually, and then I held the on/off button, and slid the slider to power off. When I started back up, I could not connect to the same WiFi I had just been using. I tried to reconnect and nothing. I tried to forget the network and try again, nothing. I tried to reset all network settings, nothing.
    I have tried all the steps listed here: http://support.apple.com/kb/TS1398 "iOS: Troubleshooting Wi-Fi networks and connections"
    Toggled WiFi off and back on
    Made sure I am in range of the router (it's about 8 feet away and my iPhone reports full signal from the network)
    Made sure all the hardware is connected and on
    Checked other devices (I'm successfully connected with my MacBook Pro right now)
    Checked for router firmware upgrades (I have a new Time Capsule from Apple with the current 7.5.2 firmware which I've been using for a month)
    Restarted my device (again)
    Checked that the network is available (it does show on my iPhone)
    Restarted my Time Capsule
    Checked my router configuration as described here: http://support.apple.com/kb/TS3727 "Wi-Fi: Unable to connect to an 802.11n Wi-Fi network" which involves simply checking to see that WMM is turned on, also stating that WMM cannot be enabled or disabled for Apple's AirPort products.
    Reset my network settings (again)
    I have searched and searched for fixes to this problem, and I have additionally tried:
    Enabling/disabling Airplane Mode
    Disabling any network password protection/encryption (no luck), re-enabling it (no luck)
    Changing the network password
    Checking for hardware addresses present in iOS Settings > General > About (they are present and not zero'ed out)
    Switching Bluetooth off (nothing) and back on (nothing)
    ....and probably a few other things I can't think of right now
    I have yet to try:
    The "Freezer Trick" which apparently involves chilling the iPhone to get a temporary fix?
    Restoring the iPhone (I would really rather not)
    A different WiFi network (other than my own Time Capsule home network or guest network, both of which give the same Unable to Connect error)
    So, after all of that, are there any more ideas? Is there a reliable solution to this issue? So far I've just seen a lot of "mess with the settings," "the freezer trick worked," and "blame it on the iOS 4 update."
    Here are my hardware details:
    iPhone 4; iOS 5; 32GB; AT&T; no cellular data plan (July 2011)
    TimeCapsule6,113; Firmware 7.5.2; 2TB (September 2011)
    MacBook Pro 3,1; Mac OS X (10.7.2); 2.4 GHz Intel Core 2 Duo; Hi-Res Display; 4GB RAM; 500GB HD (August 2007)
    ...and the Time Capsule config:
    http://cl.ly/BCUt

    Ugh. Apparently "messing with it" is still the answer. I decided to try the LinkSys router I was using before I bought the Time Capsule, and my iPhone connected with no problem.
    I went through the steps again, and after rebooting my Time Capsule this time, I can connect again. The troubling thing it that this started with a power-off of my iPhone. No changes or installations, just a reset. Am I going to have to reboot my Time Capsule (which has no power switch, just a cord I have to unplug) every time I reboot my iPhone?
    Jinkies.

  • Why does iPhone randomly power off?

    My iPhone powers off at, seemingly, random times. It should not power off at all unless I power it off. Any explanations as to why?

    Without more specific information it's hard to assist you.
    First thing is it may be hardware failure which means you will have to take it to Apple store and see a genius expert. You will need an appointment first though.
    There a several things to try first though as I have seen, and also experienced iPhones where the operating system appeared to lock up at what appeared to be random times which would eventually cause the phone to eventually reboot.
    Usually though, if you pay enough attention as to what might be causing it, I was able to determine that it was a troublesome website or an application that caused iPhone OS to lock up.
    You can usually try several things to fix this.
    First try to work out what might be causing the problem by seeing if you can replicate what you were coin immediately before it happened. If it's an app that's causing the problem then remove it. If you can't work out what's triggering it then try a soft reset by pressing the home and power/sleep buttons til the phone reboot (you'll see the Apple logo reappear after the phone shuts down).
    If this doesn't work then try doing a restore on the phone and first set it up as a new phone, then test the phone and see whether this has fixed it.
    If this does fix it then you can try doing a restore again and instead of setting it up as a new phone use the option to restore from a backup. If the problem returns after you do this, then your software backup is somehow corrupted and you'll need to restore as a new phone and start resetting it up with all your old settings.
    Anyways I hope this helps you in some way

  • Power-off on x86?

    Hi everybody!
    Does somebody knows how to tell Solaris 8 to turn-off the machine/power-supply on a ATX x86 machine when doing a complete shutdown?
    Is this possible? Would be great.
    Thanks for your help!!
    Regards,
    Stefano

    I�m currently having the same problem. I have Solaris 8 on Intel. Usually Halt works just fine from the terminal, it turns the machine off completely. But I wanted to turn off the machine for the weekend on friday night, so I put the adecuate line with crontab, but IT DOES NOT WORK: the machine just shuts down, and asks the operator to press a key to continue before it boots again, but it does not power off.
    I would find it very useful if someone finds a solution, even a hardware solution (maybe an intelligent UPS would do the work, but the again, which one?)
    Thank you very much
    Adrian Will

  • Mac pro too slow to use, spinning ball, no finder response, only hard power off, installing system stalls at 18 minutes left.

    mac pro too slow to use, spinning ball, no finder response, only hard power off, installing system stalls at 18 minutes left.
    It is taking an hour to power up and mac apple logo appear onscreen. No finder controls or "clicks" are being recognized. Spinning beachball all the time.
    Using hard power off and holding the mouse down, I was able to open the optical drive and then restart with "c" and ask the dvd to reinstall the system, but it has stalled before finishing the installation.
    This happened about 4 days ago, first it started responding slowly, and then it just keeps spinning the beachball. I can't find hardware test. I did run etrecheck, it did not have any error messages, but I can't copy or move the data anywhere.... I am not able to access the mac pro with another machine, and now I am stuck in install freeze, so I can't copy etrecheck by hand onto a piece of paper.
    Without being able to finish a reinstall, what can I try?
    After it got bad, and before it got REALLY bad, I managed to repair permissions, but it took a long time. Most of a day. When I restarted from that, things were only worse.
    Mac Pro 1,1 , 11 GB ram, 7300, 5TB hard drives, OS 10.6.8,  the drive containing the system folder is/was 700 used, 290 free. While I could get commands to respond, I put Activity monitor on the desktop and watched it.  System memory was 3.31 GB used, about 7 free, and some wired. No app was using a huge amount.
    what should I try next? I put a bid on a new/old machine so that I could move the 4 hard drives over.

    Thank you for all your suggestions. Please correct me as I articulate this.
    I have three versions( 5, 6, CC) of the Adobe Master Collection which I keep active for different clients. I have final cut and motion. I have Office 365. I have a collection of graphic apps that are individually not too big but in all, my app folder is 65GB and my bootcamp partition is 61GB. I can't fit all this on 120 ssd and a 256 will be full once I install, correct? drives should be half open?
    Somehow I did not make it clear enough that I was trying to copy onto a 2TB drive I had just initiallized in order to try and save files from my startup drive. I don't use time machine. I take a day or a few days worth of documents and physically move them to another drive at night.  If a series is finished I make two dvd's as well. The second black drive that was failing was the drive I moved my backup documents onto. At no point was I trying to backup onto the failing drives. I was trying to copy off both of them onto the other two drives, a third aux backup that has been there for a while, and a newish 2 TB which I designated as the startup drive when all this trouble started.
    I wondered if there were any good techniques for trying to get the data off the failing drive. Thanks for the suggestion of Data Rescue 3. I don't have it yet, but I will try it as soon as I get it. I was never trying to repair in place.
    I am very interested in getting a pci bracket and an ssd, but I may wait until I can afford the larger one. If I get an older bracket that is compatible with my old mac pro 1,1  ,  I'd like to be able to move it to a mac pro 3,1 if I get one. Will the larger ssd drives be compatible with the sata in a pci bracket that can work in my mac pro 1,1 ? sata 2 versus something else? If 240 or 256 is my size limit, how much more than my 65 and 61 GB partitions can I put on there? How much of a scratch disc can I make if I leave another 39 GB of headroom on my bootcamp partition? I'm filling 165 GB without making any allowance for temp files.
    You have said that 120 is enough for any system. I think I must be misunderstanding something. Are you saying that assuming that most people run office and photoshop and maybe lightroom?
    I have and use 4 HDD in this machine, mostly for document storage in two places.
    I took out all but the group of 2GB ram chips I bought a year and a half ago. The old ram had passed the hardware test the last time I had access to the hardware test. Two black drives failed, one was a year old and one was a year and a half old, and that it may have been exacerbated by the heat wave. I don't know why the video and the monitor were affected save that the startup drive was failing. I am trying to replace the card.
    With all this said, I am also looking at a used mac pro 3,1 with a better video card since a newer machine will likley be compatible through another OS upgrade. If a machine costs only a little more than a new card, it might be a better way to go.
    I don't have any sources that offer an ssd for 100. ( of a size that is useful)
    How large is your application folder?

  • Unable to power off via init 5 on Solaris 10 5/09

    I installed Solaris 10 5/09 at my home PC. The mother board is Asus P5QL-EM. I have checked that all major hardware/chipsets are on HCL.
    Now I have problem power off the machine via 'init 5'. 'Init 5' will stop all services, sync file system then leaves the machine in a state of black screen, no keyboard response. But the machine is still powered on, fans are running.
    If I bring the system to single user mode by 'init s', then 'init5' from single user mode, sometimes I can power it off completely but not every time.
    I guess the problem is between the bios acpi interface and the kernel drivers, but just do know from where to start the investigation. Any idea?

    Sun's ACPI support is really sucks.
    After I applied the latest kernel patch 141415-09, the trick I found stopped working. Any attempt to power off the system will just end up with a black screen. The last message I saw before the screen went black was
    sync file system ... done
    I then tested the Solaris 10 on another of my pc, that is about 3 years old. After the installation without apply any patch or tricks, system can be powered off properly. However, once I applied patch 141415-09, "init 5" stopped working.
    All the pc I tested Solaris 10 here are able to be powered off properly by number of linux distro or even as simple as grub. So I created a work around it.
    I created a small jfs partition and installed just GNU grub(no the grub from Sun) on it, then install Solaris 10 on the second fdisk partition. I created menu.lst
    default saved
    timeout 5
    title Solaris
    savedefault 1
    rootnoverify (hd0,1)
    chainloader +1
    title Power off
    savedefault 0
    halt
    The idea is to use GNU grub chain load Solaris grub and set default menu entry to "Power off" at the same time. When I need to power off the system, I issue "init 6" to reboot the system, then GNU grub will power off the system and at same time it set the default menu entry back to "Solaris". So next time, when the system waked up on Lan by the magic packet, it will boot Solaris. The down side of this solution is that I last the ability to reboot system.
    It is really shame of Sun that as simple as grub is able to interact with ACPI and power off the system correctly.

  • T530 Win 8 optical drive power off issue resolved

    I found that my optical drive would power off & couldn't power it on (like many of you)  when it arrived md Nov.
    Did a bunch of research & tried a lot of things and it finally stayed on.
    A few days ago it was powered off again. Finally noticed that the day before I got an auto download of Lenovo's power manager.
    I 'uninstalled' it & the drive stays on.
    Needless to say I turned off auto updates.
    Hope this helps someone out there.

    mobal wrote:
    What is the solution? How to revert to a pervious Intel Rapid Storage driver?
    Yes. You need to install the 11.2.0.1006 version of the Intel Rapid Storage driver. Here's the manual install process from the README file:
    Installing files
    12. Select Start.
    13. [Windows 7/Vista]
    Right-click Computer, and then select Properties. At the left pane, select
    Device Manager.
    [Windows XP]
    Right-click My Computer, select Properties, select the Hardware tab, and
    then select Device Manager.
    14. Double-click/double-tap the IDE ATA/ATAPI controllers or Storage
    controllers category.
    15. Double-click/double-tap either of the following devices;
    Standard AHCI 1.0 Serial ATA Controller
    Intel(R) 7 Series Chipset Family SATA AHCI Controller
    Intel(R) 5 Series 6 Port SATA AHCI Controller
    Intel(R) Mobile Express Chipset SATA AHCI Controller
    16. Select the Driver tab, then select Update Driver Software...
    17. Select Browse my computer for driver software.
    18. Select Browse..., then point to driver location specified in step 9.
    19. Make sure the checkbox next to "Include subfolders" is checked and select
    Next.
    20. Follow the instructions on the screen to complete installation and restart
    the computer.
    Delete the file saved in the step 4.

  • IPad won't power off and tends to spontaneously reboot

    When I try to power off my iPad (pressing the sleep button then sliding the "slide to power off" slider), it displays the wait progress indicator, goes black just briefly, then the silver Apple boot up logo appears as the device reboots which results in the device remaining on.
    Worse yet, the device tends to frequently spontaneously reboot, often when the home screen is displayed and not performing any user operation.
    I really don't want to restore the iPad as this results in metadata loss for thousands of audio files (Apple really needs to address this inadequacy and provide a Time Machine back up option for us users who choose to manually manage files on iOS). Is a device restore my only recourse?

    It sounds like something is crashing your iPad resulting in this spontaneous reboot. Without knowing what you're running or if you've done anything unusual to your iPad, it's hard to say. There is a remote possibility that it's hardware related, but I would go the software route first. The only way to find the culprit, without completely restoring (which I would actually recommend here) is to one by one delete program apps and see if the problem ceases.
    If you completely restore and the problem disappears, then it was software related. If you backed up your iPad before restoring, you should be able to restore it from the backup thus retaining any data you had stored previously. Of course, this would also reinstall the offending app that was causing this behavior in the first place, but at least you'd know it is software and not hardware related which obviates a visit to your local Apple Store.

  • Crash Power Off

    My Mac mini is repeatedly powering off at random. I was using it for about 3 hours last night and it randomly powered off about 4 or 5 times. I have tried eliminating different applications by not running them and I am now under the impression it is hardware related. It seems to happen when I am running a few different apps at the same time - so maybe it is processor related. I have only had it a few weeks and am really surprised as I thought Mac's didn't do this sort of thing. Any help greater appreciated.
    Thanks.

    Welcome to Apple Discussions!
    Does the system seem to power off faster when it is warmer than when it is cold? The reason for asking is that the mini is designed to go into a protective shutdown mode if it begins to overheat, caused by heavy loading of the CPU of decreased airflow. However, in those circumstances you would normally hear the fan spin up to full speed for a period before the shutdown occurs as the system tries to keep itself cool. Do you notice any fan activity?
    You could try monitoring the system with Activity Monitor (in Applications>Utilities) to see if the shutdowns are associated with heavy and/or prolonged CPU load, and also look at the system logs by running Console (also in Applications>Utilities) to see if there is anything listed there to indicate the cause.
    Ultimately if the fan isn't working and you are not operating the system in a overly hot environment, it should not be shutting down prematurely and would warrant the unit being examined by an approved service provider.

  • K8MM3-V Random Crashes / Power Offs / Video Problems

    This is kinda lengthy so I'll apologize from the beginning.
    Recently put together a K8MM3-V (MS-7181-050) installed with Win XP Pro SP2.
    After installing all my apps (MS Office, Firefox, some games, Avid Xpress, Photoshop) and using the machine for a day or two, I discovered it likes to completely power off seemingly at random.
    It usually happens (but not always) while I'm reading my mail via Thunderbird, browsing the net or editing video in Avid (the three most common things I do.)
    I also have an issue where my screen occasionally goes black for about 10 seconds, then returns and all my windows and icons get reloaded.
    I *pretty much* resolved that issue by rolling back to a prior version of my ATI Radeon 9600 graphics drivers, the ones without the Catalyst control panel.
    I loaded the latest BIOS and drivers files from MSI Live Update 3...and my XP pro has the latest patches from Microsoft.
    Has anyone seen this before? Could this be a BIOS/settings issue?
    Here is my hardware:
    K8MM3-V
    1.5GB memory (1-1GB Kingston stick, 1-512MB Corsair Value Select stick)
    Rosewill AGP 128MB ATI Radeon 9600
    ADS Tech Pyro Basic DV Firewire Card on the PCI Bus (the only thing installed on the slots)
    Sempron 3100 Proc (Socket 754)
    Using Latest BIOS
    And getting really frustrated!! 

    "1.5GB memory (1-1GB Kingston stick, 1-512MB Corsair Value Select stick)"
    leave only one memory stick in DIMM slot close to CPU socket. mixing memory sticks as different brand and specifications are always bad idea.
    then get a copy of Memtest86 and test memory for errors,
    use test N:5 and N8, lets loop at each one 20 times, ensure no errors will come. (details can be found here: https://forum-en.msi.com/index.php?topic=103598.msg760534#msg760534)
    re-test.
    other possibilities, (or you may have more than one problem in same time)
    weak or failure PSU:
    list PSU details as well(they can be found into PSU sticker).
    overharing issue:
    check CPU underload temp,(with prime95,toast,orthos can be found here: https://forum-en.msi.com/index.php?topic=107133.0), observe CPU temp with:
    Coretemp http://www.thecoolest.zerobrains.com/CoreTemp/CoreTemp.zip
    or
    Coretemeter http://cbid.amdclub.ru/files/corterm.zip
    and ensure CPU temp is in normal acceptable range, if its high:
    re-seat the CPU, clean the CPU socket from any dust around, apply new thermal paste,(but don't put too much paste), ensure Heatsink FAN is in good condition, ensure CPU Heatsink makes good contact with CPU surface.

Maybe you are looking for

  • Not able to pick PO text via READ_TEXT when PO is created by copy.

    Hi, I am not able to pick PO texts from READ_TEXT function module for PO's which are created via Copy of another PO as entries for that PO texts are not found in STXH table.However after creating PO if I do some modification in any text and save PO a

  • How to connect to Internet through a LAN

    Hi everybody !!! Please show me how to connect to Internet through a LAN (through another computer). On Windows XP system, i use the following informations to do that: + My IP: 192.168 .1.45 +subnet mask: 255.255.255.0 +default getway: 192.168.1.12 (

  • Switching to a different workspace in Netbeans 6.1

    I have my workspace for Netbeans set to my laptop hard drive but now I would like to put it on my external hard drive. 1. What do I have to worry about? 2. Whats the best way to do it? Thanks

  • Redeem code for Mountain Lion in the App Store

    I input my redeem code for Mountain Lion in the App Store and it said it was downloading, but nothing happend.  How do I know if the upgrade has been completed?

  • How to manage music from WD My Cloud in iTunes

    I'm using a Western Digital My Cloud and stored the main part of my music collection at this place. With iTunes I am able to play these files but I can not manage them. I can't copy them or add informations or covers. Furthermore I cannot delete file