Protecting VMs against host power-offs

Every now and then and for numerous reasons, my Windows 8 desktop encounters a loss of power. I am running a Debian 6 virtual machine via HyperV and when I restore power, the VM kernel panics every single time. Rebooting the VM results in the disk being
set to read-only mode, and fixing it takes quite a long time. I have a number of snapshots from states such as these.
Is there a feature of HyperV that makes VMs more tolerant to sudden host power-offs? I could script something together to take periodic snapshots of my VMs and revert to those should I encounter a loss of power, but I wonder if there is something already
present in HyperV to facilitate such protection.
I have one of the simplest of simplest setups: Windows 8, HyperV with two VMs (Solaris and Debian), each with a single attached drive and network adaptor. I have no clustering setup nor do I use any HyperV integration (the Debian kernel module leads to more
kernel panics, and I don't have time to debug that at the moment).
Is there something already present, or should I just write a script to take periodic snapshots?
Edit: I now realize this is the Windows Server forums, yet my setup uses Windows 8. Is there a more appropriate forum for my post?

Every now and then and for numerous reasons, my Windows 8 desktop encounters a loss of power. I am running a Debian 6 virtual machine via HyperV and when I restore power, the VM kernel panics every single time. Rebooting the VM results in the disk being
set to read-only mode, and fixing it takes quite a long time. I have a number of snapshots from states such as these.
Is there a feature of HyperV that makes VMs more tolerant to sudden host power-offs? I could script something together to take periodic snapshots of my VMs and revert to those should I encounter a loss of power, but I wonder if there is something already
present in HyperV to facilitate such protection.
I have one of the simplest of simplest setups: Windows 8, HyperV with two VMs (Solaris and Debian), each with a single attached drive and network adaptor. I have no clustering setup nor do I use any HyperV integration (the Debian kernel module leads to more
kernel panics, and I don't have time to debug that at the moment).
Is there something already present, or should I just write a script to take periodic snapshots?
Edit: I now realize this is the Windows Server forums, yet my setup uses Windows 8. Is there a more appropriate forum for my post?
The only reliable way to go would be:
1) having at least two individual hosts running server versions of Windows with Hyper-V role enabled (technically you can have ANY hypervisor but this is Windows forum)
2) configure guest VM cluster between VMs you have (yes, that would require some sort of a physical or virtual shared storage, typically...)
That would be very low RTO (virtually no downtime) and RPO (virtually no data loss). See:
Guest VM Cluster for HA
http://technet.microsoft.com/en-us/library/dn440540.aspx
Using some third-party software like VEEAM will get you reasonable RTO and RPO but no transparent failover. This one is not free but may work with a desktop version of Windows (never checked). Free Hyper-V is definitely supported. See:
VEEAM Backup & Replication
http://www.veeam.com/blog/rdp-rsat-free-hyper-v-server-2012-r2-remote-desktop-appliance-linux.html
Hyper-V Replica may also work (2012 R2 req'd). See:
Hyper-V Replica Explained
http://blogs.technet.com/b/yungchou/archive/2013/01/10/hyper-v-replica-explained.aspx?utm_source=feedburner
Hyper-V Replica Overview
http://technet.microsoft.com/en-us/library/jj134172.aspx
Good luck!
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Similar Messages

  • DAG member, PF database host, and hub maintenance (6hr power-off)

    Hello, 
    We have an EPO test coming up in one of our data centers that requires me to power off 2 of our 4 DAG members. In preparation for this I’ve been reading up on DAG member maintenance best practice as well as deconstructing the Start[Stop]DagServerMaintenance.ps1
    script. After testing in my lab I noticed that the iteration of Suspend-MailboxDatabaseCopy is followed by the parameter -ActivationOnly and sets ActivationSuspended to True. Why only suspend copy activation and not database copy processes? Does the script
    assume that DAG member maintenance does not include server shutdown or is suspending database copy processes not actually necessary? 
    Also, one of the DAG members I have to power off serves 1 of 3 of our PF databases. I’ve noticed that the Start[Stop]DagServerMaintenance.ps1 scripts do nothing for PF databases. Should I just unmount it and rely on standard PF replication to update it when
    I mount it back? Do I need to change my databases over to use a different PF database?
    The power-off duration is 6 hours so I'm not too worried about log build up. Our CAS servers are VMs and will be “motioned” to our other data center. We have two Hub Transport servers, I plan to simply power one of them off. Am I missing anything?
    Thanks!

    Belinda, 
    Your understanding and the article you provided on Managing Database Availability Groups seems to be inline with what I've described. However,
    just our of curiosity can you or anyone else explain why the script StartDagServerMaintenance.ps1
    only runs Suspend-MailboxDatabaseCopy -ActivationOnly? In other words, why does the script only suspend copy activation and not the copy process? 
    "Did the two Hub Transport servers locate in the same AD site?", yes they are in the same
    AD site but different physical locations. The article on HSS helped explain HT HA. 
    Thanks again! 

  • Passcode lock protection" prior to power-off for mobile Apple devices

    I would like to make a suggestion for an enhanced security operating procedure for Apple devices, with the purpose of detecting a device after it has been stolen.
    This idea has occurred to me after an unfortunate personal experience. In particular, two months ago there was an incident where my backpack with four Apple devices belonging to myself and my wife (two iphones and two ipads) was stolen.
    Immediately after the theft, within the next 10 minutes, I managed to gain access to a computer.
    Although I had activated the service “find my iphone” and “find my ipad” respectively, I soon found out that the devices were already offline, which means that the first thing that the thieves did was to power them off.  Please note that all devices were “passcode lock protected”.
    The enhanced security proposal I would like make is the following:
    A command to be added to the operating system according to which, in order to be able to power-off the device, the user will have to give the valid passcode. In other words, I am suggesting a “passcode lock protection” prior to power-off and not just prior to power-on. By means of this arrangement, and as long as batteries last, the stolen devices may be located.
    Thank you for your time.
    Best regards
    George Paidas

    http://www.apple.com/feedback/ipad.html

  • [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

  • 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.

  • I have had my iMac for 55 days now and twice I had to power off/on and then It does not power up correctly.  I verified my disk and found errors that could not be repaired.  I erased the drive and restored system back to the previous day.

    I have had my iMac for 55 days now and twice I had to power off/on and then It does not power up correctly.  I verified my disk and found errors that could not be repaired (errors were associated with boot drive)  I erased the drive and restored system back to the previous day.  Has anyone else experienced this problem?

    Since it's a new machine, contact Apple's Support and let them deal with it. Allen's already recommended an Apple repair station visit. Do note that if you have AppleCare's protection plan and you're within 50 miles (80 KM) of an Apple repair station, you might be eligible for an onsite repair since yours is a desktop machine (depends on where you're located).  BTW, the AppleCare Protection Plan's the best warranty policy available for desktop machines. Get it if you don't have it before contacting Apple.
    27" i7 iMac (Mid 2011) refurb, OS X Mavericks (10.9.4), ML & SL, G4 450 MP w/Leopard, 9.2.2

  • Mac Pro early 2008 power off suddenly alone and gives a long beep on startup

    Hello everyone! Can you resolve the problem reported? I have 6 equipaments identical to those with the same problem, some worse than others, and only two barely functioning, others are stopped. They power normally and suddenly alone they power off , and after that I only can power on again , after hours waiting or only the next day , and when it's power on , on startup , they give me a long beep , before the chime , then I can work for a time (minutes or long time , it's not secure)
    I talked with Apple Computer (from USA) and they do not assume that the problem exists and that many users have the same problem, worldwide.
    If you're not satisfied with the result of Apple, we will have to press them to assume the defect and promote a recall on these equipments. We have many users with the same issue (MacPro off alone)

    All places where I have my equipments (they are in 4 different places, but I have tested them in all four locations), are electrically grounded, the electrical networkstabilized, reviewed annually and I use UPS minimum of 1.5 KVA (I have two UPS of 3.75 KVA) . I tested with the original HDD , with all the applications that I use installed , only with the system installed and the same procedure on a new HDD and got the same result . So , it is not eletrical problem . I have iMacs , MacBooks , G5 and MacPro early 2009 working in the same places with no problems . I tested all the sites with three different electricians and all
    approved my Electric networks . As I know, all Apple equipment have
    surge protection, precisely to prevent thecomponents from being damaged
    by electrical problems. Again , it is not eletrical problem .

  • Is it better to put Mac in sleep or just power off?

    Hi there,
    I am a new user for Mac, (i just have one Macbook Pro) would very much to know the suggestion: either we should close the lip, put the mac in sleep mode or power off every day when finished the work?
    which one is better for computer? someone says better not turning on and off every day, do so unless you will not use Mac for days. but I also found people says keep the computer in sleep mode might have trouble to wake it up later...
    any experts suggestion?
    thanks,

    I would not regard myself as expert and you are going to get opinions for both approaches. I have just passed on a 3 year-old MacBook Pro that has never been off, apart from updating when restarts are required. Similarly, my iMac sleeps (protected by UPS) and is not turned off. I am happy this way.
    I would take slight exception to your process, however. In my opinion, I put the MacBook Pro to sleep by using OptionCommandDelete (or the Apple menu) and wait until the power light pulses before closing the lid.

  • My iPhone 5 having a problem that I can open my lock screen but I cannot slide open my phone even Slide to power off too, It just cannot slide.

    My iPhone 5 having a problem that I can open my lock screen but I cannot slide open my phone even Slide to power off too, It just cannot slide.

    Hello MarvanCheong,
    Thanks for using Apple Support Communities.
    For more information on this, take a look at:
    iPhone, iPad, iPod touch: Troubleshooting touchscreen response
    http://support.apple.com/kb/ts1827
    Restart your device
    Hold the On/Off button until "slide to power off" appears. Slide to power off your device. When it is off, press the On/Off button to turn it back on.
    If you can't restart your device, reset it by pressing and holding the Sleep/Wake button and the Home button at the same time for a least ten seconds, until the Apple logo appears.
    Clean the screen with a soft, slightly damp, lint-free cloth.
    Avoid using the device while wearing gloves, with wet hands, or immediately after applying hand lotion.
    If you have a protective case, or if you are using a plastic sheet or film on the display, try removing them and testing the device without it.
    Best of luck,
    Mario

  • My 4th generation ipod touch will not power off and the volume buttons do not work, any suggestions?

    My ipod's power off and volume buttons are not working. It's as if the volume down button is constantly being pressed. Both buttons "work" as far as I can press them in, but there is no response from the ipod. Any suggestions? I have updated the software, but that did not help.
    Thank you!

    I have the exact same problem!!
    please let me know if you have found a fix / soution
    email me at [email protected] or just reply, any help would be great
    thanks.

  • Osx10.6 keeps freezing how can I fix without turning power off?

    osx10.6 keeps freezing how can I fix without turning power off?  It has happened a dozen times in the last ten days -
    Force Quit will not respond
    When the freeze occurs the cursor will move, but not activate any application
    The only way to restore activity is to turn off MacBook with power button
    I do not like doing this, and am happy that so far Time Machine has not stopped functioning when I turn power back on.

    Yesterday my macbook pro freezed again, two times in 20 minutes!!!
    When i restarted the computer there was this message (maybe it is useful for resolving my problem):
    Interval Since Last Panic Report:  29598 sec
    Panics Since Last Report:          2
    Anonymous UUID:                    0C2CFCCA-8A3F-445F-89D3-99573F5C31AA
    Fri Jun  3 19:26:42 2011
    panic(cpu 1 caller 0x9cdc8f): NVRM[0/1:0:0]: Read Error 0x00002500: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0x92000000 0x36a0c000 0x084700a2, D0, P0/4
    Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
    0xe036b8 : 0x21b510 (0x5d9514 0xe036ec 0x223978 0x0)
    0xe03708 : 0x9cdc8f (0xbe323c 0xc53840 0xbf23cc 0x0)
    0xe037a8 : 0x15c7a7d (0x6255c04 0x6cd3004 0x2500 0x6cd3004)
    0xe037e8 : 0x15b8d5e (0x6cd3004 0x2500 0x0 0x0)
    0xe03868 : 0x15af132 (0x6cd3004 0x6d95004 0x41 0xe038a0)
    0xe03988 : 0xad3b45 (0x6cd3004 0x6d95004 0x996500c 0x200)
    0xe039c8 : 0xb52a66 (0x6cd3004 0x6d95004 0x7bcc52c 0x7bcc504)
    0xe03a78 : 0xb542d7 (0x6cd3004 0x6d9d404 0x0 0x0)
    0xe03b08 : 0x15adf19 (0x6cd3004 0x6d9d404 0x6 0x2)
    0xe03b88 : 0x15b7f8e (0x6cd3004 0x6d95004 0x1010 0xe03c9c)
    0xe03cf8 : 0x15ef33e (0x6cd3004 0x6d95004 0x0 0x0)
    0xe03e28 : 0xb07250 (0x6cd3004 0x6d13004 0x0 0x0)
    0xe03e68 : 0x9d6e23 (0x6cd3004 0x6d13004 0x0 0x0)
    0xe03f08 : 0x55125b (0x0 0x63d1780 0x1 0x29f562)
    0xe03f58 : 0x55028c (0x63d1780 0x1 0xe03f88 0x54fe43)
    0xe03f88 : 0x5506e6 (0x63b73c0 0x6805b7c 0x16808f71 0xffffffff)
    0xe03fc8 : 0x2a06dc (0x63b73c0 0x0 0x10 0x66b87a4)
          Kernel Extensions in backtrace (with dependencies):
             com.apple.nvidia.nv50hal(6.2.6)@0x14c5000->0x18d9fff
                dependency: com.apple.NVDAResman(6.2.6)@0x967000
             com.apple.NVDAResman(6.2.6)@0x967000->0xc54fff
                dependency: com.apple.iokit.IOPCIFamily(2.6)@0x927000
                dependency: com.apple.iokit.IONDRVSupport(2.2)@0x95a000
                dependency: com.apple.iokit.IOGraphicsFamily(2.2)@0x938000
    BSD process name corresponding to current thread: kernel_task
    Mac OS version:
    10J869
    Kernel version:
    Darwin Kernel Version 10.7.0: Sat Jan 29 15:17:16 PST 2011; root:xnu-1504.9.37~1/RELEASE_I386
    System model name: MacBookPro3,1 (Mac-F4238BC8)
    System uptime in nanoseconds: 702931547147
    unloaded kexts:
    com.apple.driver.AppleFileSystemDriver          2.0 (addr 0x102a000, size 0x12288) - last unloaded 112769797938
    loaded kexts:
    com.vmware.kext.vmnet          3.0.0 - last loaded 49645686211
    com.vmware.kext.vmioplug          3.0.0
    com.vmware.kext.vmci          3.0.0
    com.vmware.kext.vmx86          3.0.0
    com.sophos.kext.sav          7.3.0
    com.bresink.driver.BRESINKx86Monitoring          8.0
    com.apple.driver.AppleHWSensor          1.9.3d0
    com.apple.filesystems.autofs          2.1.0
    com.apple.driver.AppleHDA          1.9.9f12
    com.apple.kext.AppleSMCLMU          1.5.0d3
    com.apple.driver.AppleUpstreamUserClient          3.5.4
    com.apple.driver.AppleMCCSControl          1.0.17
    com.apple.driver.AirPort.Atheros21          424.14.5
    com.apple.driver.AppleIntelMeromProfile          19.1
    com.apple.driver.AppleBacklight          170.0.34
    com.apple.driver.SMCMotionSensor          3.0.0d4
    com.apple.driver.ACPI_SMC_PlatformPlugin          4.5.0d5
    com.apple.driver.AudioAUUC          1.54
    com.apple.GeForce          6.2.6
    com.apple.driver.AppleLPC          1.4.12
    com.apple.Dont_Steal_Mac_OS_X          7.0.0
    com.apple.iokit.CHUDUtils          364
    com.apple.iokit.CHUDProf          366
    com.apple.driver.AudioIPCDriver          1.1.6
    com.apple.driver.AppleUSBTrackpad          200.3.2
    com.apple.driver.AppleUSBTCKeyEventDriver          200.3.2
    com.apple.driver.AppleUSBTCKeyboard          200.3.2
    com.apple.driver.AppleIRController          303.8
    com.apple.iokit.SCSITaskUserClient          2.6.5
    com.apple.BootCache          31
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
    com.apple.driver.AppleUSBHub          4.1.7
    com.apple.iokit.IOAHCIBlockStorage          1.6.3
    com.apple.driver.AppleSmartBatteryManager          160.0.0
    com.apple.driver.AppleIntelPIIXATA          2.5.1
    com.apple.driver.AppleAHCIPort          2.1.5
    com.apple.driver.AppleFWOHCI          4.7.1
    com.apple.driver.AppleUSBEHCI          4.1.8
    com.apple.driver.AppleUSBUHCI          4.1.5
    com.apple.iokit.AppleYukon2          3.2.1b1
    com.apple.driver.AppleEFINVRAM          1.4.0
    com.apple.driver.AppleRTC          1.3.1
    com.apple.driver.AppleHPET          1.5
    com.apple.driver.AppleACPIButtons          1.3.5
    com.apple.driver.AppleSMBIOS          1.6
    com.apple.driver.AppleACPIEC          1.3.5
    com.apple.driver.AppleAPIC          1.4
    com.apple.driver.AppleIntelCPUPowerManagementClient          105.13.0
    com.apple.security.sandbox          1
    com.apple.security.quarantine          0
    com.apple.nke.applicationfirewall          2.1.11
    com.apple.driver.AppleIntelCPUPowerManagement          105.13.0
    com.apple.driver.DspFuncLib          1.9.9f12
    com.apple.iokit.IOFireWireIP          2.0.3
    com.apple.driver.AppleHDAController          1.9.9f12
    com.apple.iokit.IOHDAFamily          1.9.9f12
    com.apple.iokit.IO80211Family          314.1.1
    com.apple.driver.AppleProfileReadCounterAction          17
    com.apple.driver.IOPlatformPluginFamily          4.5.0d5
    com.apple.nvidia.nv50hal          6.2.6
    com.apple.NVDAResman          6.2.6
    com.apple.iokit.IONDRVSupport          2.2
    com.apple.driver.AppleProfileTimestampAction          10
    com.apple.driver.AppleProfileThreadInfoAction          14
    com.apple.driver.AppleProfileRegisterStateAction          10
    com.apple.driver.AppleProfileKEventAction          10
    com.apple.driver.AppleProfileCallstackAction          20
    com.apple.iokit.IOSurface          74.2
    com.apple.iokit.IOGraphicsFamily          2.2
    com.apple.iokit.IOBluetoothSerialManager          2.4.0f1
    com.apple.iokit.IOSerialFamily          10.0.3
    com.apple.driver.AppleSMC          3.1.0d3
    com.apple.iokit.CHUDKernLib          365
    com.apple.iokit.IOAudioFamily          1.8.0fc1
    com.apple.kext.OSvKernDSPLib          1.3
    com.apple.iokit.AppleProfileFamily          41.4
    com.apple.driver.CSRUSBBluetoothHCIController          2.4.0f1
    com.apple.driver.AppleUSBBluetoothHCIController          2.4.0f1
    com.apple.iokit.IOBluetoothFamily          2.4.0f1
    com.apple.iokit.IOUSBHIDDriver          4.1.5
    com.apple.driver.AppleUSBMergeNub          4.1.8
    com.apple.driver.AppleUSBComposite          3.9.0
    com.apple.iokit.IOSCSIMultimediaCommandsDevice          2.6.5
    com.apple.iokit.IOBDStorageFamily          1.6
    com.apple.iokit.IODVDStorageFamily          1.6
    com.apple.iokit.IOCDStorageFamily          1.6
    com.apple.driver.XsanFilter          402.1
    com.apple.iokit.IOATAPIProtocolTransport          2.5.1
    com.apple.iokit.IOSCSIArchitectureModelFamily          2.6.5
    com.apple.iokit.IOUSBUserClient          4.1.5
    com.apple.iokit.IOATAFamily          2.5.1
    com.apple.iokit.IOAHCIFamily          2.0.4
    com.apple.iokit.IOFireWireFamily          4.2.6
    com.apple.iokit.IOUSBFamily          4.1.8
    com.apple.iokit.IONetworkingFamily          1.10
    com.apple.driver.AppleEFIRuntime          1.4.0
    com.apple.iokit.IOHIDFamily          1.6.5
    com.apple.iokit.IOSMBusFamily          1.1
    com.apple.kext.AppleMatch          1.0.0d1
    com.apple.security.TMSafetyNet          6
    com.apple.driver.DiskImages          289
    com.apple.iokit.IOStorageFamily          1.6.2
    com.apple.driver.AppleACPIPlatform          1.3.5
    com.apple.iokit.IOPCIFamily          2.6
    com.apple.iokit.IOACPIFamily          1.3.0
    Model: MacBookPro3,1, BootROM MBP31.0070.B07, 2 processors, Intel Core 2 Duo, 2.4 GHz, 2 GB, SMC 1.16f11
    Graphics: NVIDIA GeForce 8600M GT, GeForce 8600M GT, PCIe, 256 MB
    Memory Module: global_name
    AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x87), Atheros 5416: 2.1.14.5
    Bluetooth: Version 2.4.0f1, 2 service, 19 devices, 1 incoming serial ports
    PCI Card: pci168c,24, sppci_othernetwork, PCI Slot 5
    Serial ATA Device: WDC WD5000BEVT-00A0RT0, 465,76 GB
    Parallel ATA Device: MATSHITADVD-R   UJ-857E
    USB Device: Built-in iSight, 0x05ac  (Apple Inc.), 0x8502, 0xfd400000
    USB Device: Bluetooth USB Host Controller, 0x05ac  (Apple Inc.), 0x8205, 0x1a100000
    USB Device: Apple Internal Keyboard / Trackpad, 0x05ac  (Apple Inc.), 0x021b, 0x5d200000
    USB Device: IR Receiver, 0x05ac  (Apple Inc.), 0x8242, 0x5d100000
    Any ideas?

  • "Power off retract count" is WAAAAAAy too high!

    I just purchased a refurbished (Black) Macbook 2.4 ghz with a 250 gig FUJITSU MHY2250BH HDD.
    HDD passes SMART.
    HDD often makes a subtile clicking noise. Sometimes the click is ever few seconds, sometimes it does not happen at all.
    I used an application called "SMART Utility" to look at the particulars of the drive.
    I FOUND SOMETHING VERY ODD:
    the HDD's "Power off retract count" is very high. The actual number is 458,760.....yes, almost half of a million.
    Can anyone help me or add some information about this?

    Hi Kappy, thanks for the info.
    I did a bit more reading of the FAQ for the app. "SMART Utility" and that huge number might not be the actual number.
    To quote the FAQ:
    "Q4. What are the differences between threshold, worst, value, and raw numbers in the attributes window, and why do some attributes show a super high value, like 426900000?
    A4. The raw number is the actual, real value of the attribute. How the drive measures it is up to the manufacturer. Some put the data in a human readable format (for example, 50 in Temperature Celsius for 50 degrees Celsius), while others have a proprietary format for the data, which may be display as an extremely high number. This varies for each attribute, some are human readable, some are not. So if a number is unusually high, it's possibly not a human readable number. So how does one figure out if an attribute is okay if the raw number is in a proprietary format?
    Well, that's where the other three numbers come in: “threshold”, “worst”, and “value”. “value” is the normalized equivalent of the raw data, converted internally to a number between 0 and 255 and displayed. The manufacturer defines a threshold number against which the “value” is compared, and if the “value” drops below that threshold, SMART reports that attribute as FAILING_NOW, and sets the overall health as FAILED. That is how SMART determines the status of the drive. Sometimes the “value” falls below the “threshold”, but then rises again. This is shown as an Inthepast failure, and SMART Utility marks this as a FAILING status. The final number, “worst”, shows how low the value actually got. This is probably the best way to tell just how bad the raw number is. If it is close to the threshold, the drive may be failing."
    However, what lead me to use this utility is a subtile, yet irritating "click" that my HDD often makes. The sound could be described as "a ping pong ball being dropped on a hard surface." If one looks around in this forum and on the greater web, it seems others are baffled about this "Mystery sound." It is often attributed to the "head(s) parking" on the HDD. What is odd is that some people hear the sound and others do not. What is also odd, for me in particular, is that I took some steps to minimize the "head parking" of my HDD by temporarily installing "hdapm" and this did absolutely nothing to minimize the click sound of the "heads parking." So I also tried another temporary experiment and completely disabled the "sudden motion sensor" because I read that this feature may cause the noisy click of the heads parking. This measure, also, did absolutely nothing to minimize the click of the heads parking.
    So, I am at a loss. However I am still annoyed by the noise of the somewhat loud click(s) of my HDD's head parking which may be caused by an over aggressive power saving mechanism that may be built into the drive itself.
    If anyone can add to this discussion, I'll be happy to soak up the info.

  • Wake on lan from power OFF

    It appears that Mac's don't provide wake on lan from complete power off. I have no problem powering up my Mac from sleep, but it won't turn on from power off (like every PC I've tried). This is not difficult to do, as every $200 PC on the market w/ WOL does it.
    I have my Mac on a large shared UPS with serveral other computers and network gear, etc.
    There is a linux server which actually communicates with the UPS. During a power failure, that linux box will connect to ever other machine on the network sharing this UPS and tell them to SHUT OFF, not sleep, because hard power failure is emminent. When all remote machines are off, the linux machine shuts off, and the UPS powers off it's outlets.
    On power recovery, the UPS waits until it's batteries are sufficiently recharged, and turns back on, powering up it's protected outlets. All the machines see power come back on, and are set to reboot.
    Here is the problem. If the power comes back on AFTER the remote machines are shut down, but before the linux box turns off, the linux box sees power recovery, and the UPS never shuts off it's protected outlets. Now all the remote machines are off, and won't ever see their power cut off, and then recover, so they don't turn back on.
    The PCs are easy... hit them with a wake-on-lan packet and they reboot from complete power off... but not the trusty Mac because Apple didn't implement that part of the wake-on-lan standard!
    So... I'm faced with abandoning wake on lan for all the machines and building an interface with a big relay to KILL power to all remote machines to power them back on. Isn't this more than just a little silly? Apple... why not just make your machine comply with the standard so that it plays nicely in a mixed environment!
    Providing wake on lan from sleep, and power on with power recovery, but no wake on lan from OFF is just ridiculous.
    I welcome any ideas...
    PowerMac G5 Dual 2.0   Mac OS X (10.4.8)  

    Malcolm,
    If I make it sleep, then I'm forcing it to crash when the power turns off. The idea here is for a graceful shutdown before emminent power failure when the UPS battery runs out.
    The only reason it's getting shut down is that the main power has failed and the UPS battery is running low.
    I agree that with no power they can't interpret packets and react... but that's why proper wake-on-lan implementations keep the NIC powered up to watch for WOL packets.
    Thanks,
    -Russ

  • 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.

Maybe you are looking for

  • Can't delete app which is no longer existed on my mountain lion

    I kept got notificaiton for update of an app called chopper 2 even though I never bought it. And the even weirder thing is that the account that apple says I bought this app with is not mine. The tragic thing now is that because it was not bought by

  • My iphone wont charge can the charging port be repaired or replaced

    my iphone wont charge can the charging port be replaced or repaired

  • Iphone charger replacement program

    Anyone know if is Apple offering the third party iPhone charger replacement program in Canada? I was told by the local outlet in BC, it's for the US and other part of the world only. She said she verified with he co workers, even I told her it was re

  • Printing Japanese characters: ABAP List

    Dear all, How to setup so that my ABAP list can show japanese characters on printers? We can see it on screen but could not print on printer. I setup a printer type of HP1160. When In print out from let's MS word to this printer, japanese characters

  • SharePoint 2013 Unit Tests

    Hi,    I am interesting in creating unit tests in sharepoint 2013. Could you give me some information, which tools should I use to make this one? Is there aby good practise for SP? Regards Kamil