My i5 occur unexpected power off/ on

My iPhone was crack and I replaced front and back housing. The unexpected power on/off problem occur. How do I solve this? When charging the battery not show the correct amount but still charging. After I restart then show the correct amount

See here for tips of improving battery life and performance.
http://www.apple.com/batteries/ipods.html
To shut down the iPod Touch, press and hold the Sleep/Wake button until you see the Slide to Power Off option. Then slide the switch to power it off.
B-rock

Similar Messages

  • E66 camera, "Unexpected error occured. Power off t...

    Hi,
    I purchased my E66 a week ago and there is this problem that is really annoying me, whenever I try using the camera for the second time (i.e. after taking a picture then turning the camera off) the error pops that "Unexpected error occured. Power off the device and restart". I think I've restarted it thousands of time but the problem is never solved. Can anyone kindly guide me through this problem and a solution for it? I'll be very obliged. Thanks

    1. backup everything in your memory card to your pc
    2. backup your phone memory to your memory card
    3. reset/format your phone
    4. try if the camera works
    5.
    a) either setup your phone settings and programs again
    b) or restore your backup from the memory card to your phone
    6. check to see if the cam works now
    for backing up the phone to the memory card, go to the "memory" program in the tools, and press the options to see the backup phone line.
    Good luck...
    And do not hesitate to ask further
    For the reset / format part I copied the following from the web. I never tried the 3rd one. My personal choice is the 2nd. If anyone has an idea I'd love to hear as well..
    *#7780# - Reset to the original settings; some informations are also deleted and need to be re-entered.
    *#7370# - Soft format - this will resets all the phone memory (like re-format a disk); make sure to have full battery charged !
    [dial] + [3] + [*] during a power on performs a hard format : this will return the phone like you have received; make sure to have full battery charged !
    Message Edited by sodalimon on 23-Aug-2008 03:39 PM

  • AIR-LAP-1142N-E-K9 unexpected power offs

    Hi we have two seperate Cisco wireless networks both based around the same infrastructure.
    Cisco 5508 WLC/s running 7.4.100 Firmware in our datacentre, with AIR-LAP-1142N-E-K9 LAPS distributed at site offices.
    This infrastructure has been running well until recently when we have had a spate of the LAPS appearing to power off.
    The LAP appears to be off with no LED status light as if it has been powered off, but the power supplies are still connected and the LAPS are often warm to the touch as if drawing power even when they have been "off" for a couple of days.
    Unplugging the power supply (at the LAP) and re-applying brings the LAP back on.
    The LAPS involved all used the recommended Cisco manufactured power supplies as there was no POE/power injector infrastructure.
    The LAPS vanish from the WLC as if disconnected, without any apparent errors in the WLC logs.
    There are no crash logs for the LAPS which have powered off.
    Console output from a LAP which has powered off on startup just shows the AP coming back from a "cold start".
    LAPS operate normally after restart, but after avariable period, typically 2-7 days will power off again.
    This is happening across multiple sites, to LAPS connected to different WLCs.
    Has anyone seen this issue before?

    The LAP appears to be off with no LED status light as if it has been powered off, but the power supplies are still connected and the LAPS are often warm to the touch as if drawing power even when they have been "off" for a couple of days.
    Gareth,
    Just want to make sure you are using a power brick/power injector.  Can you please confirm?
    Had issues with 7.4 when I noticed that some of my APs, running in PoE, would suddenly get "lost".  They would suddenly reboot and they wouldn't negotiate PoE properly.  I had to manually shut down the ports for at least 5 seconds.  If I don't leave it off for that long the APs simply won't boot up.
    Ever since I've moved to 7.5, I haven't seen this happen.
    There is a well-known bug, can't seem to find it, about 1140 and WLC firmware 7.4.  If I remembered correctly, the bug describes what you are seeing.
    You may want investigate in using 7.5.

  • Unexpected power off now mac mini want boot up pass the grey screen

    i have a mac mini the power went off when it came back on and i tryd to cut mini back on it only went to gray apple screen them goes out the monitor says not supported i need to get class assignments off of it.

    Take each of these steps that you haven't already tried. Stop when the problem is resolved.
    Step 1
    The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
    There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
         a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
    b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
    c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
    d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
    Step 2
    If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
    Step 3
    Sometimes a startup failure can be resolved by resetting the NVRAM.
    Step 4
    If you use a wireless keyboard, trackpad, or mouse, replace or recharge the batteries. The battery level shown in the Bluetooth menu item may not be accurate.
    Step 5
    If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
    Step 6
    Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
    Step 7
    If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
    Start up in safe mode. Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Post for further instructions.
    Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
    The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
    If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
    If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
    Step 8
    Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
    This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
    Step 9
    If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.   
    Step 10
    Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
    Step 11
    Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
    Step 12
    This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
    Step 13
    If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

  • HT201412 Apple iTouch5 Unexpected Power-Off

    Hi. My iTouch5 unexpectedly shut down about an hour ago & it was on full battery, It's been charging for over 30 minutes now & it still hasn't restarted. I tried the sleep/wake button & it still hasn't powered on or appeared with the apple logo. I've had this iTouch for over 2 years now & I can't afford to buy a new one at the moment. Can somebody tell me what to do?

    Try:                                               
    - iOS: Not responding or does not turn on           
    - Also try DFU mode after try recovery mode
    How to put iPod touch / iPhone into DFU mode « Karthik's scribblings
    - If not successful and you can't fully turn the iOS device fully off, let the battery fully drain. After charging for an least an hour try the above again.
    - Try another cable              
    - Try on another computer                                                       
    - If still not successful that usually indicates a hardware problem and an appointment at the Genius Bar of an Apple store is in order.
    Apple Retail Store - Genius Bar                                     

  • N95 front camera : Unexpected error occurred. Powe...

    When I try to use my N95 front camera it just says "Unexpected error occurred. Power off the device and restart."
    I tried everything. Updated the firmware, replaced the flex cable and the front camera, restarted the phone, etc. and nothing happened.
    Can someone help me ?

    gdegas001, I'm inclined to your suggestion.
    I'm not using the N95, but my N82 is spitting the same error message.
    I think I have the latest firmware V31.0.016 (not sure if this is latest or not).
    I have also done *#7370# follow by 12345 to reset the phone.
    I have also changed the following: from silver to black to gold and now back to black housing!  Of course in doing that, I've changed several keypad flexes.
    Ok I'll cut to the chase, I think I've demaged the flash (or it's flex) after changing the facet 4 times!
    It is on my latest N82 face change that I received the "Unexpected error...".  And of course it is the first time I notice the blinking flash battery (in the manual, this means the flash is charging!). Now it is ok if the flash is charging after it fired a few times, but a blinking flash indicator followed by the "Unexpected error.." is likely to mean that the flash is not charging or dead.
    I'm going to buy the flash unit (about $30 on eBay) for replacement and see if my (or your's) suspicion is correct.  Will update you all soon.
    Of course the "Unexpected error.." can mean many things, the flash issue is just one of them.  So don't even think about changing the flash unless you always see the blinking flash indicator first.  Another reason for getting the "Unexpected error..." is if you have changed your housing for your phone at least 3 times, by yourself! 

  • Unexpected my apple iphone 4s power off

    my apple i phone power off unexpected ..ring tune and mesge tune is listen but not show nny disply only black screen show its show power off mobile.plz help me

    Hey there amna,
    It sounds like the phone turned off unexpectedly. I found this article to help you troubleshoot it that issue named:
    iPhone: Hardware troubleshooting
    http://support.apple.com/kb/ts2802
    Will not turn on, will not turn on unless connected to power, or unexpected power off
    Verify that the Sleep/Wake button functions. If it does not function, inspect it for signs of damage. If the button is damaged or is not functioning when pressed, seek service.
    Check if a Liquid Contact Indicator (LCI) is activated or there are signs of corrosion. Learn about LCIsand corrosion.
    Connect the iPhone to the iPhone's USB power adapter and let it charge for at least ten minutes.
    After at least 30 minutes, if:
    The home screen appears: The iPhone should be working. Update to the latest version of iOS if necessary. Continue charging it until it is completely charged and you see this battery icon in the upper-right corner of the screen . Then unplug the phone from power. If it immediately turns off, seek service.
    The low-battery image appears, even after the phone has charged for at least 20 minutes: See "iPhone displays the low-battery image and is unresponsive" symptom in this article.
    Something other than the Home screen or Low Battery image appears, continue with this article for further troubleshooting steps.
    If the iPhone did not turn on, reset it while connected to the iPhone USB power adapter.
    If the display turns on, go to step 4.
    If the display remains black, go to next step.
    Connect the iPhone to a computer and open iTunes. If iTunes recognizes the iPhone and indicates that it is in recovery mode, attempt to restore the iPhone. If the iPhone doesn't appear in iTunes or if you have difficulties in restoring the iPhone, see this article for further assistance.
    If restoring the iPhone resolved the issue, go to step 4. If restoring the iPhone did not solve the issue, seek service.
    Thank you for using Apple Support Communities.
    All the very best,
    Sterling

  • Update 7.1.2 caused permanent iphone 4 power off

    I have updated to ios 7.1.2 my iphone 4. Now after it locked the keyboard, sometimes it power off. Only cable connection helps to boot up. Hard reset does not help. Your suggestions?

    Hello there, arturfrommoscowcity.
    The following Knowledge Base article offers up some great, in-depth steps for troubleshooting issues with not being able to power on your iOS device:
    iPhone: Hardware troubleshooting
    http://support.apple.com/kb/ts2802
    Particularly:
    Will not turn on, will not turn on unless connected to power, or unexpected power off
    Verify that the Sleep/Wake button functions. If it does not function, inspect it for signs of damage. If the button is damaged or is not functioning when pressed, seek service.
    Check if a Liquid Contact Indicator (LCI) is activated or there are signs of corrosion. Learn about LCIsand corrosion.
    Connect the iPhone to the iPhone's USB power adapter and let it charge for at least ten minutes.
    After at least 30 minutes, if:
    The home screen appears: The iPhone should be working. Update to the latest version of iOS if necessary. Continue charging it until it is completely charged and you see this battery icon in the upper-right corner of the screen . Then unplug the phone from power. If it immediately turns off, seek service.
    The low-battery image appears, even after the phone has charged for at least 20 minutes: See "iPhone displays the low-battery image and is unresponsive" symptom in this article.
    Something other than the Home screen or Low Battery image appears, continue with this article for further troubleshooting steps.
    If the iPhone did not turn on, reset it while connected to the iPhone USB power adapter.
    If the display turns on, go to step 4.
    If the display remains black, go to next step.
    Connect the iPhone to a computer and open iTunes. If iTunes recognizes the iPhone and indicates that it is in recovery mode, attempt to restore the iPhone. If the iPhone doesn't appear in iTunes or if you have difficulties in restoring the iPhone, see this article for further assistance.
    If restoring the iPhone resolved the issue, go to step 4. If restoring the iPhone did not solve the issue, seek service.
    Thanks for reaching out to Apple Support Communities.
    Cheers,
    Pedro.

  • HT1414 when i update iOS 7.1.1 in iphone 5s then my iphone always power off

    when i update ios7.1.1 then my iphone 5s sometime turn on n sometimes off

    Hello there, godpray2049.
    The following Knowledge Base article provides some great steps for troubleshooting the issue you're describing:
    iPhone: Hardware troubleshooting
    http://support.apple.com/kb/ts2802
    Particularly:
    Will not turn on, will not turn on unless connected to power, or unexpected power off
    Verify that the Sleep/Wake button functions. If it does not function, inspect it for signs of damage. If the button is damaged or is not functioning when pressed, seek service.
    Check if a Liquid Contact Indicator (LCI) is activated or there are signs of corrosion. Learn about LCIsand corrosion.
    Connect the iPhone to the iPhone's USB power adapter and let it charge for at least ten minutes.
    After at least 30 minutes, if:
    The home screen appears: The iPhone should be working. Update to the latest version of iOS if necessary. Continue charging it until it is completely charged and you see this battery icon in the upper-right corner of the screen . Then unplug the phone from power. If it immediately turns off, seek service.
    The low-battery image appears, even after the phone has charged for at least 20 minutes: See "iPhone displays the low-battery image and is unresponsive" symptom in this article.
    Something other than the Home screen or Low Battery image appears, continue with this article for further troubleshooting steps.
    If the iPhone did not turn on, reset it while connected to the iPhone USB power adapter.
    If the display turns on, go to step 4.
    If the display remains black, go to next step.
    Connect the iPhone to a computer and open iTunes. If iTunes recognizes the iPhone and indicates that it is in recovery mode, attempt to restore the iPhone. If the iPhone doesn't appear in iTunes or if you have difficulties in restoring the iPhone, see this article for further assistance.
    If restoring the iPhone resolved the issue, go to step 4. If restoring the iPhone did not solve the issue, seek service.
    My issue is still not resolved. What do I do next?
    Contact Apple Support.
    Thanks for reaching out to Apple Support Communities.
    Cheers,
    Pedro.

  • HT201401 iPhone 4S will not power off.

    Phone will power back on by itself. Can not get it to stay off.

    Hello 7Milebch,
    Thanks for using Apple Support Communities.
    From what I understand from your post is that your iPhone 4s is restarting on its own.  I definitely see how this is a frustrating experience, and I would also want this to be resolved.  I'm not sure of the steps you have taken in TS2802 already, but lets make sure to do steps 5-7 of this section of the article:
    Will not turn on, will not turn on unless connected to power, or unexpected power off
    Verify that the Sleep/Wake button functions. If it does not function, inspect it for signs of damage. If the button is damaged or is not functioning when pressed, seek service.
    Check if a Liquid Contact Indicator (LCI) is activated or there are signs of corrosion. Learn about LCIs and corrosion.
    Connect the iPhone to the iPhone's USB power adapter and let it charge for at least ten minutes.
    After at least 30 minutes, if:The home screen appears: The iPhone should be working. Update to the latest version of iOS if necessary. Continue charging it until it is completely charged and you see this battery icon in the upper-right corner of the screen . Then unplug the phone from power. If it immediately turns off, seek service.
    The low-battery image appears, even after the phone has charged for at least 20 minutes: See "iPhone displays the low-battery image and is unresponsive" symptom in this article.
    Something other than the Home screen or Low Battery image appears, continue with this article for further troubleshooting steps.
    If the iPhone did not turn on, reset it while connected to the iPhone USB power adapter.
    If the display turns on, go to step 4.
    If the display remains black, go to next step.
    Connect the iPhone to a computer and open iTunes. If iTunes recognizes the iPhone and indicates that it is in recovery mode, attempt to restore the iPhone. If the iPhone doesn't appear in iTunes or if you have difficulties in restoring the iPhone, see this article for further assistance.
    If restoring the iPhone resolved the issue, go to step 4. If restoring the iPhone did not solve the issue, seek service.
    iPhone: Hardware troubleshooting
    http://support.apple.com/kb/TS2802
    Take care,
    Alex H.

  • My bookmarks are lost after turning off the computer unexpectedly (power problem),how can it recovers?

    My bookmarks are lost after turning off the computer unexpectedly (power problem),how can it recovers？ Thanks a lot !!!!
    我的书签在电脑突然被断电之后全部丢失了，我该怎么办呢？？谢谢啦！！~~~~

    This can also be a problem with the file places.sqlite that stores the bookmarks and the history.
    * http://kb.mozillazine.org/Locked_or_damaged_places.sqlite
    * http://kb.mozillazine.org/Lost_bookmarks

  • My e9107c desktop goes to sleep and them in a few hours or minutes has an unexpected power failure.

    My computer goes to sleep, will wake up and run fine.  It never fails while using it for hours.  Once I leave it, it will go to sleep.  If I come back and it is asleep it will come back on and work fine.  However if while its asleep it has an unexpected power failure I have to turn on the computer and it will restate and work fine.  Its like it goes to sleep and forgets it needs power and shuts off but doesn't shut down the operating system and causes a kernal 41 error. 
    If it were a power supply failure or an over heating problem I would expect it to occure while using the system, not during sleep mode when everything powers down.  It used to work fine but the last few months the problem showed up.  If I shut down the computer and them come back and turn it on it works fine.  So I just don't let it go to sleep and turn it on and off.
    Any idea why it would loss power while sleeping?

    I think I have resolved my problem by uninstalling my cell phone software : Sony Ericsson PC Companion 2.0  I found that this program was interfering with windows when I wanted to turn off my computer and stopped shut down.  It interfered more after two recent upgrades.  I don't think Sony Ericsson has very good programer, because the more they upgrade the program the more it conflicted with Windows 7 64 bit OS  I had this program on my system for a long time before the problem arose.  I uninstalled the program and noticed my system ran better.  It shut down without forcing any program to end.  Since there was such a dramatic change in how the system worked, I tried to reset my computer to go to sleep and not shut it down.  It works a designed and no longer loses power while sleeping.  I didn't think an installed program could affect this feature but apparently it can.

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

  • Connect to iTunes required after every power off of Ipad 64GB wifi

    My Ipad 64GB wifi model continually prompts to "connect to iTunes" every time I power off and power back on. This is extremely frustrating and the Apple Customer Care has asked that I return my iPad. I would rather find a solution since I am working Iraq and my Ipad is my e-book reader (in place of a Kindle. Steps taken thus far:
    Reset iPad (Erase All Content and Settings)
    Reset Network settings
    Reset All Settings (content not erased)
    I've read that this problem sometimes occurs with some third-party applications installed (like Jailbird) . I do not have any of those applications installed. If anyone can offer a solution I would greatly appreciate it.
    Danielle

    Since you erased all content and reinstalled the OS and this still happens, sounds like a hardware failure. You need to take the iPad back to an Apple store for an exchange.

  • Random Power Off mini core 2 duo

    This is an on going problem for the last few months..
    Basically I could be working on anything and the power will just drop out, as if someone has pulled the cable out. It is rarely under heavy load, and the time between power outs can vary between a few minutes, days or weeks! It is always without warning.
    As an example the mac had been unplugged from the mains power supply for a few hours. I plugged it in, booted up, started browsing, then off within a minute. Powered it back on, then it was off within a few minutes. On again and still on for the last 20 mins...
    This is a freshly re-installed machine with minimal software installed and running.
    I have tried running it from 2 different UPS's.
    I have run all supplied testing software including Tech Tools.
    Nothing was found.
    It was in the Mac Service Centre and no problem found.
    I don't think it even powered off while it was there! :-o
    It stayed powered on continuously for 2.5 weeks once I got it back, then the problem started to re-occur.
    ..any ideas.. anyone...?
    Also as a first tonight I had expose' set to power off the monitor. It came out of it fine. I left it for an hour or two... when it came out of it only the outline of the mouse pointer was visible. I could move the mouse, but nothing else would appear. No keyboard action would 'wake' the display..?

    Weird as it sounds....could be memory if you recently done an upgrade.
    We run our office on Mac mini's. Recycling and product liquidation, so can get all kinds of cool stuff. I bought a ton of new memory for everyone and we all had this issue. It's been a while so I don't remember if they were just turning off, randomly rebooting or a combination. I know that I did run ram test and all passed flying colors. Just my two cents.

Maybe you are looking for

  • File download with JSP

    I have found some code within this forum that I have been attempting to use to allow customers to download text files to their PC's. The code below is what I have come up with from my understandings on exactly how it should work, but it just will not

  • Vendor Holidays

    If vendor will close his business every year between Nov 20 to Dec 31st. Where we can maintain this information in SAP? My requirement is Buyer should not place any Purchase order during this period. MRP should not select this buyer during this perio

  • How to: Get a list of mail users by using the Exchange Management Shell

    Hello every one, quick question: When I run this code below for VB, how will I see the results of the program? Is there anyway I can make the results appear in a message box? Function GetUsersUsingBasicAuth( _     ByVal LiveIDConnectionUri As String,

  • Will whatsapp be removed from iPhone 4 after the launch of iPhone 6?

    Will whatsapp be removed from iPhone 4 after the launch of iPhone 6?

  • Par file upload

    Hi, I made changes to par file after importing in on NWDS. Now Im unable to export the file due to an error in the NWDS: " Operation failed: Please make sure the server is running or check log for more details ". Can someone can tell me what the prob