"Power off retract count" is WAAAAAAy too high!

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

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

Similar Messages

  • Power consumption in Connected Standby Mode too high with no obvious cause even in airplane mode

    My Windows 8.1 tablet is draining at a rate of about 3% per hour or 833mW drain while in connected standby mode.
    I have muted the sound and set the system to airplane mode, but still receive 3% drain per hour.
    The PEP PRE-VETO rate and COUNT are 0. The DRIPS Histopgram has 100% at 32s. The top 5 offenders are all green with 0% active time.
    The only value I am unsure about is IR TRUNCATE PERCENTAGE which on Microsoft's examples is always 0, but on my device it is 91% or higher. What does this mean?
    Also is there anyway to find out why even though the sleepstudy looks fine I am getting such a high battery drain even with everything off in airplane mode?

    Hi Tesmond
    We might need more details about your device such as mode and Manufacturers.
    And please keep your system, device driver and firmware up to date for good measure.
    I think you are using sleep study to trace power usage. I didn’t found any information about IR TRUNCATE PERCENTAGE. I am supposing IR stand for Infrared. So we suggest you check if these is infrared port/connection device on your tablet.
    Also confirm this issue with manufacturers to check if it is known issue caused by firmware or device driver.
    Regards
    D. Wu

  • Mac OSX 10.6.8 Garage Band '11. This error happens occasionally : I am forced to power-off-on.  Pop-up states that error info will be sent to apple. I never hear back from apple. Second prob: Fan sometimes comes on, runs high speed, then slowly stops.

    Garage Band '11: pop-up error forces me to power off-on. Message states that info will be sent to Apple.
    I never hear back from anyone about this.
    Second prob: Fan sometimes comes on, runs high speed, then slowly runs down and stops running.

    First thing to do is a SMC Reset, you can find instructions at:
    http://support.apple.com/kb/HT3964
    READ THE INSTRUCTIONS CAREFULLY!!!!
    Then try Repairing Disk Permissions, do this at least 2x. You will find this in Disk Utility which is located in Applications - Utilities - Disk Utility.
    Finally you may need to uninstall Garage Band and reinstall. You may have to use Pacifist to do this, you can find it at:
    http://www.macupdate.com/app/mac/6812/pacifist

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

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

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

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

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

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

  • IPod Touch play count WAY too high

    My 16GB 2G iPod Touch has a play count which is far too high. It is like 1500 for songs I have added today. Any way to solve this?
    I have tried resetting the play counts, skip counts and restoring my iPod. No luck.

    I'm having the same issue. I've got an iPod Touch 1G, fully updated. I'm seeing tracks that I've literally not played in weeks maybe even MONTHS come up with hundreds, and songs i've played maybe once or twice come up with thousands. I reset all the play counts to try again but it didn't make a difference, next thing i knew, a whole load of new tracks were up there in the thousands.
    It's REALLY annoying, cause I've got a Most Played smart playlist, which doesn't really work in the first place as it doesn't update itself no matter how many times i plug my iPod into the computer, and even if it DID work, it wouldn't be very accurate, and I'd have a load of Janet Jackson interludes clogging up my most played, which gets annoying after a while, no matter how entertaining they are when they're part of the album!
    What can we do?!

  • KDEMod3 is taking too long to log out or power off

    KDEMod3 is taking too long to log out or power off...and I swear I've had less stuff running than my previous install before my computer broke O____o How can I fix this?
    Last edited by ShadowKyogre (2009-04-16 05:43:39)

    I think you should head over to the kdemod forum:
    http://chakra-project.org/bbs/index.php

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

  • IMac Hard Drive expectations, Are mine too high?

    Hey everyone.
    I have a 27" iMac i5. Its around 22 months old now and its being used as a personal PC at home.
    Lately, I have been experiencing HDD related issues, It hangs, load times are poor, OS takes ages to boot (windows and OSX)
    I backed up all my data to external drives and did a clean OS restore to Lion. No help, first boot with the OS was just as bad as a boot full of clutter. Loading Windows on the win partition also sometimes gives me the "cannot find OS boot disk" error which is scary.
    Anyway's doing research its all sure tell-tale signs of a failing HDD and ironically last night on my Win7 partition, I got the windows error message saying my "windows detected a hard disk problem, back up all data and contact your manufacture".
    Now, back on topic. Is this reasonable? a $2000+ computer suffering from a hardware fault like this when the HDD has never had more than 30% of the 1TB used in its life? (everything I keep backed up on externals.)
    I was honestly expecting a few more years out of this, **** even my 5 year old Macbook has never had an issue in its life and its been bagged around more places I can think of in its lifetime. How does a computer that sits on a desk suffer for a hardware failure such as this?
    From day one, I had a faulty power board inside, it caused a loud electronic buzzing noise. I did not get this fixed for aroun 9 months as tbh, it sounded normal but in the last month leading upto the replacement, it got much louder over a few days. This was replaced by Apple and I was sent on my way happy it was fixed. could this have caused something to overload?
    I am a little bit bitter which I am sure you can understand, but was my expectation of this hard drive just too high? or am I in my right to be a little upset by this?
    And before anyone askes, I was OS when my warranty ran out, my Macbook, iPad 3XiPhones and Mac Mini are all covered by their own Apple Care. the only thing that isnt is the iMac.. just my luck!
    Edit: the old link for the power board.
    https://discussions.apple.com/thread/2737002

    Thanks guys.
    Just got off the phone to Applecare.
    they confirmed my drive is faulty. Im just a little upset it died like this. I have never had a drive fail before. Id rather my externals go than the internal.
    Spoke to Apple, they said that he spoke to his Tech Specalist and they would not offer a free replacement. I agree is its 10 months out of warranty, but even the Apple rep I was speaking too said he would not be impressed either if it was his personal computer
    Oh well. Time to look at HDD Upgrade options! Not that I am totally impressed about it.

  • Battery Wear-Level overnight feels too High!

    Hi,
    Usually i rarely use battery (always put the battery out after charging it) except when i need to take my 4-months-old B480 laptop outside (which is rarely happened)
    Yesterday i leave my battery with ac adapter plugged-in while downloading a large file from internet, i set start charging threshold at 75% and stop at 95% (as many people said it's better not to fully charge the battery), and on the next day i see my battery wear-level became 13% O.o while cycle count is only 5
    I think it's too high for a one-night charging, my old laptop (non-Lenovo) didn't gets this high even when i leave it with ac adapter for days.
    Is this wear-level normal for a one-night charging? (at-least for lenovo laptop that is)
    Does warranty covers an abnormal battery wear-level?
    PS: one of the reason i choose lenovo laptop is because it has customizable-battery charging threshold feature which many people said can be used to prolonged battery lifespan(minimizing wear-level by not fully-charging it and not discharging it too low) even when used with ac adapter, while not many other brands have this kind of feature.

    hi AdamN,
    A usual sign of an imminent battery failure is when it wears out the charge in an abnormal rate (battery goes down to less than 20% overnight after a full charge when unit is off or in sleep state). Sometimes heat can also be a factor to shorten the battery life as discussed in this article.
    To further test the health of the battery, You can try Passmark's BatteryMon. If the battery is failing, you may contact Lenovo for a battery replacement. Support phone list here.
    Hope this helps.
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
    Follow @LenovoForums on Twitter!

  • K8N FSR AGP voltage too high w 6800GT?

    Hi guys !
    I've been having trouble oc:ing my 6800GT and one guy told me that the problem is related to my AGP voltage. It's too high thus preventing the GT from running normally at higher speeds.
    The symptoms of oc:ing are 1-3 sec freezings in 3DMark05/03/01 plus crashes "expolrer.exe & drwtsn32.exe". It's not a heat-related problem because I have a NV Silencer 5 mounted on the core which also covers all mem chips. My temp indicator shows me 45-50C idle 60-65C full-load.
    I've heard that the GT requires 1.3V AGP voltage. Unfortunately you cannot lower AGP voltage in BIOS.
    Any suggestions ??

    i have almost teh same setup.  when i first got my 6800 i had same issueso/c and i watercool.
    it wasnt until i swapped my 430true power to wifes 350 enermax that it was straightened out.  ex has like 32a on 12v line
    cpu used to use the 5v line but now almost your whole system rides the 12v line all peripheral cpu and your gt juce sucker.  so those old powersupplies cant keep up with big systems like ours
    also with a64 some games you need to turn cool and quiet off during because the way the code is written it doesnt keep cpu at 100% so the cpu keeps throttling down and up.  i just shortcut in my toolbar for the power control from control panel. it works nicely
    agp 1.5v.  6800gt core voltage is 1.3 ultra is 1.4.
    those numbers are not really related.  your friend may be connecting numbers which are not related.  dont forget 6800 has its whole own mobo essentially with a core and ram and other chips sitting on it. thats what the agp 1.5v goes to.
    hope this helps

  • P4 Temp over 140f isn't this too high?

    I was checking out the CPU temp with the PC Alert III and got a temp over 140f. The Chassis is 96f without any overclocking. Isnt this too high?

    Quote
    Originally posted by jdurg
    I have a 1.8A running at 2.52 GHz on an 845 Ultra-ARU, and I too see quite high temperatures.  My CPU idles at 50 degrees Celsius, and reaches 67-68 degrees under a full load.  My chassis temperature is about 35 degrees C on idle, and goes up maybe four or five degrees under a load.  (My ambient room temperature is about 23 degrees Celsius.)  My heatsink is making solid contact with my CPU, as evidenced by the fact that when I tested it by putting a strip of paper on the IHS before putting the heatsink on, the paper would not budge.  (I obviously removed the paper before starting up the computer, and have a nice, even layer of AS3 forming a haze over the CPU.)  I have two 80mm intake fans (one in the front and one on the side of the case), the exhaust fan on the bottom of my power supply which is right above the CPU, and an 80mm exhaust fan on the back of the case.  If I pull the cover of the case off, the temperatures do not change at all, so my airflow in the case is as good as it can get.  
    If I touch the heatsink while the CPU is under a full load, it feels warm, but not 67-68 degrees Celsius warm.  So I'm thinking that the temperature sensor on my motherboard is about 7 or 8 degrees Celsius too high.  (Perhaps even ten degrees.)  However, I have not had any crashes or any instability caused by these "high" temperatures, so that furthers my theory that the temperature sensor is messed up.  I'd like to see it get fixed in a BIOS update, but I doubt MSI would do that, and I also doubt that MSI would ever update the BIOS for the 6398 motherboard ever again.   X(   (I'd also like to see some memory ratios for this board, but again, I'd bet my life on the fact that MSI will never give us any memory options on an otherwise good board.)
    Get an external probe to measure and bear in mind that P4's thermal throttling kicks in @ > 66 (roughly there)

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

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

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

  • HT1547 My mac book pro is 3 yrs old and today while watching something on it, it got power off suddenly. And power button is not working, left side round button to battery is not working but when I plugg in to charge it, then this round button shows 4 gre

    I am having MacBook Pro 3 yrs old and today while I was watching some movie on it suddenly it got power off and when I am trying to start it, it's power button is not working even the round button on external left side is not showing battery lights. But when I connect it to chrger then Charger only gives green light and even the external round button only shown 4 green lights (if charger connected). I don't know what to do now

    Sounds like you need a #1SMC Reset
    1. SMC reset
    >>Instructions to reset SMC
    Disconnect other non-Apple and external hardware except (if applicable) a mouse and keyboard until your finished repairing your machine.
    Problems solved: Fans blowing with no activity, machine is not booting, power button pressed and nothing happens, problems with indicators, Magsafe has wrong lights, battery is not charging, monitor and graphics issues etc.  If the battery is not charged (from like letting it sleep too long), let the Mac charge up awhile afterwards.
    Will not hurt the machine resetting if it's not broken.
    Other related hardware problems (optional):
    Check battery status: Hold option/alt key down while clicking on the battery icon in the menu bar, top right corner.
    Magsafe: Use the correct/matching power supply charger with your Mac, not a less powered one from another Mac.
    Apple: Laptop won't power up   Apple: Computer won't power up  Troubleshooting optical drive
    Magsafe problems   Magsafe problems more

  • I have an iMac running Lion and W7 with boot camp . It has been operating flawlessly until I went to reboot into Mac tonight. Screen went black, and system is unresponsive. I've tried force quitting and turning power off. Hard drive starts but that's it..

    I have a 5 month old  iMac running Lion and W7 with the latest version of boot camp . It has been operating flawlessly until I went to reboot into Mac tonight. Screen went black, and system is unresponsive. I've tried force quitting and turning power off. Hard drive starts, there's a small amount of drive activity and that's it. 

    Hi Jane, your info may still be there, look in the Users folder at root of the drive, how many users are there there?
    It sounds like this may have happened...
    Return to default desktop, apparent "loss" of home directory, (it can happen spontaneously too)...
    http://docs.info.apple.com/article.html?artnum=107854

Maybe you are looking for

  • Setting Photoshop CC 2014 as my "Default Program" to open JPEG files in Windows 7

    I just installed Photoshop CC 2014 on my Windows 7 computer. I had set Photoshop as my "Default Program" to open up JPEG files. Now whenever I double-click a JPEG file, Photoshop CC will launch instead of Photoshop CC 2014. I have noticed that the ex

  • Exporting to Flash without embedding music files

    I had to create a music player for a website, and really didn't want to make a flash player from scratch again. So I had an epiphany and opened Keynote. I created a slideshow: the first page was a "Click on song to play" and every page after the firs

  • Google Search Keyboard Shortcut Missing in Safari

    I've noticed that the keyboard shortcut for "search with Google" keyboard shortcut (command+shift+L) has been replaced by opening the new Reading List drawer.  The shortcut still works in other cocoa apps, but has been superceeded by the new reading

  • Search Engine Optimization - SEO

    I am very biased creating an all flash site, as opposed to using html or aspx etc. But as we all know, the search engine spiders can't tap into swfs. Does anyone know how to optimize an all flash site, other than using meta tags in the html? I have s

  • Changing the Path

    How do I change the path on Windows XP, and what do I change it to.