Manual Power Save on BT Home Hub 4

Hi. I know the BT Home Hub 4 automatically has Power save. But. I would like there to be a maunual opton like the BT Home Hub 3 where you select what time for the hub to power down. Maybe this could be included in the next firmware update?

Dean235 wrote:
Hi. I know the BT Home Hub 4 automatically has Power save. But. I would like there to be a maunual opton like the BT Home Hub 3 where you select what time for the hub to power down. Maybe this could be included in the next firmware update?
Hi.
I've noticed some oddities in the Home Hub 4, received by Royal Mail yesterday.
I put another post in the "other broadband queries" section, wrongly, perhaps, as we'll be muddled by all the posts. My post was on diagnostics.
My query has drawn no repsonse, but will have to wait. It's early days.
As for power save, the only way that I can see is to inhibit connection to wifi devices within specified hours.
Power consumtion: I have a true reading kWatt meter, but don't want to start disconnecting evething yet.
There's also an energy meter installed, at the main meter - a clamp device. Indications are that the HH4 doesn't draw more power than the HH2. The energy meter, or course, only measures VA and not true watts, as it can't measure power factor. A rough guess would be around 3 watts, just left in standby. i.e 72 watt hours per day, 2.23 kWh per month. 

Similar Messages

  • Power cycle a BT Home Hub 1.0

    Every time I turn off my laptop completely and restart I have no broadband signal via a wireless connection from my Hub. BT Desktop Help tells me to unplug my hub power supply, leave for 30 seconds, and power up again. This restablishes the connection. It is tedious having to do this everytime after I shut down my laptop. Should I change my Hub settings or anything else?

    get it here and install on lappy
    Download Inssider2 for free from http://www.metageek.net/products/inssider/download
    it  l show you any wifi around you that could cause problems
    and the channel they use just pick a free one
    If any post helps tick the star box on the left
    Just cause Im paranoid dont mean they are not out to get me

  • POWER SAVE ON NEW HUB 3

    Hi. I always used to switch off my hub at the wall socket every night but have  been advised by a BT engineer this is not a good thing and to leave it on 24 seven. This seems to have solved some of my problems.  However,, I now have a new Home Hub 3 with this power save facility, if I switch off my hub at the button on the Hub will this have the same affect as switch it off at the wall.

    I know all this sort of stuff is very confusing at times
    The hub3 is currently the best type regarding electricity consumption as it uses less than the previous hubs.
    If you turn off all devices connected to the hub, the hub will automatically go in to power save mode, thus using even less than what it does when it's running with devices connected.
    Ideally you should leave the hub connected 24/7, but you should be able to turn it off once every 24 hours without any problems. It's if you switch it on and off multiple times that you will run in to problems.
    The link I gave you above will tell you all about the auto power save mode - you do nothing except turn off all the devices connected to it or how to set a manual power save mode - you set this via the hub manager - type bthomehub.home in to your browser
    -+-No longer a forum member-+-

  • Ask the Experts Live Chat - Home Hub 4

    Hello,
    Stephanie and I are pleased to announce our next live discussion with some of our BT experts! It's about one of our latest new products, the Hub 4. This will be a great chance to get our Hub 4 experts onto the community to tell you a bit more about that and answer any questions you may have.
    We have added the Chat transcript below for any of you guys who missed this event.
    7:02
    JacquiBT: 
    Hello everyone.
    Thank for you joining our ‘Ask the Experts’ Live chat. I would like to introduce Dave, Sam and Emma who are our hub 4 experts and will be answering your questions tonight. I would like to invite you to ask your questions now.
    7:03
    [Comment From imjolly imjolly : ] 
    why are there no adsl stats available on the HH4
    7:04
    [Comment From DS DS : ] 
    evening all. Are the antennae omni directional?
    7:05
    Sean Donnelly: 
    Thanks for the question, Emma will respond
    to that question Imjolly
    7:05
    JacquiBT: 
    Thanks DS, Dave will respond to your question now
    7:05
    Dave: 
    Hi DS, yes they are
    7:05
    [Comment From Steve Steve : ] 
    Are there any plans for new firmware on the hub 4 to bring new features?
    7:06
    JacquiBT: 
    Thanks Steve, Dave is answering that question for you
    7:07
    Dave: 
    Hi Steve - yes there are. There will be more information available about this - and any new features - before each firmware drop.
    7:07
    [Comment From Steve Steve : ] 
    why can you not opt out of BT WIFI on the home hub 4?
    7:07
    Dave: 
    Hi Steve - you should have no problem doing this through the Hub Manager
    7:09
    JacquiBT: 
    Some great questions coming through, the experts are typing up responses now
    7:09
    [Comment From DS DS : ] 
    Personal testing - Why is the 2.4GHz range less than the HH3 when at a distance from the hub, but better close up than the HH3?
    7:10
    JacquiBT: 
    Thanks DS, Dave is answering this now for you
    7:10
    [Comment From George George : ] 
    Will the 'Home Network' page show a HH4 instead of the Current image of the HH3?
    7:11
    JacquiBT: 
    Thanks George, Sam will answer that for you
    7:11
    Sam: 
    Hi George, the HH4 image will be displayed in place of the HH3 in the next firmware release
    7:12
    Dave: 
    Thanks again DS - you shouldn't find that, but this can depend on a lot of different factors in the home. I've found mine to be a bit better actually! But it should be pretty much the same for most customers.
    7:12
    Sean Donnelly: 
    Did you know the Hub 4 has Smart Setup?
    Easy set up in just a few minutes. No CD or computer needed, it's all online and works on any device. Set up your Hub 4 router and access all your free extras like BT Cloud and BT Family Protection in just a few clicks.
    7:12
    [Comment From DS DS : ] 
    Is it possible for BT to allow us to move the BTWifi SSID's to another channel, leaving our own SSID on a less congested channel?
    7:12
    Dave: 
    Hi imjolly, sorry for the delay, Emma asked me to reply on her behalf. We have made the stats in the Hub manager simpler for customers to understand, we were reacting to feedback that it was too general for the wide range of customers and tech understandings.
    7:12
    JacquiBT: 
    Hi DS, Sam is replying to you now
    7:14
    [Comment From JamesS JamesS : ] 
    What speeds can I achieve over wifi, assuming I'm connected to 5ghz? Thanks.
    7:14
    Sean Donnelly: 
    Did you know the hub offers Easy Wireless?
    Connect wirelessly by selecting your BT Home Hub connection on any compatible device and just push a button on the Hub and you're connected. It's that simple. No passwords needed.
    7:14
    JacquiBT: 
    Hi JamesS. Dave will reply to your question
    7:14
    Emma: 
    Hi imjolly, we have made the stats in the Hub manager simpler for customers to understand, we were reacting to feedback that it was too general for the wide range of customers and tech understandings.
    7:15
    Sam: 
    Hi DS, moving BT Wifi SSID's to another channel is not possible on the HH4. However, we are looking closely at the wi-fi SSID's the hub broadcasts to see whether we can improve this experience.
    7:15
    Dave: 
    Hi James, 5GHz maximum data transfer rate of 300Mb/s; this will tend to translate as an optimal actual speeds of up to 100 Mb/s - depending on lots of factors in your home
    7:15
    [Comment From George George : ] 
    Why did you remove the built in plastic wireless info tab with a card?
    7:15
    JacquiBT: 
    Hi George, Dave is going to reply to that question
    7:16
    Dave: 
    Hi George - this was part of the design process, we've tried to make it even easier for customers to find their wireless information. Now it's not integrated it's a little bit more accessible.
    7:16
    [Comment From thebennyboy thebennyboy : ] 
    I currently have the HH3 and would like to know what noticable difference it will make having a HH4 over a HH3? We use the ethernet ports and the wireless.
    7:17
    JacquiBT: 
    Hi Bennyboy. Emma is going to reply to that question.
    7:17
    [Comment From Paul Paul : ] 
    How much faster is the processor in the home hub 4, compared to previous versions? how will this effect my online experience?
    7:18
    JacquiBT: 
    Hi Paul. Sam will answer that for you
    7:18
    Sam: 
    Hi Paul, the processor is a staggering 3x faster compared to the HH3
    7:19
    [Comment From Guest Guest : ] 
    Although opted out of BT wifi the hub still shows as being active
    7:19
    JacquiBT: 
    Hi Guest, could we ask that you post this on the community so the moderators can pick this up
    7:19
    Sean Donnelly: 
    Did you know that the hub 4 offers Dual band frequency which makes for a more reliable wireless connection?
    Smart dual-band technology reduces wireless interference and drop out’s giving you a reliable connection for all your devices.
    7:20
    [Comment From Guest Guest : ] 
    When you opt out of BT WIFI it appears to only opt out on the 2.4ghz channel and not the 5ghz channel. Are you looking into this?
    7:20
    JacquiBT: 
    Hi Guest. Dave will reply to your question
    7:21
    Dave: 
    Hi - thanks for this feedback, we'll definitely look in to it for you
    7:21
    Sean Donnelly: 
    Excellent questions coming through folks
    7:21
    Sean Donnelly: 
    Our experts are typing answers so please keep them coming
    7:22
    [Comment From Josh Josh : ] 
    Is it a known issue that the HomeHub 4 has problems identify the Xbox 360 as a media center extender when connected through a wired connection?
    7:23
    JacquiBT: 
    Hi Josh. Sam is replying to your question
    7:23
    [Comment From Winston Winston : ] 
    How much power does the home hub 4 use?
    7:24
    JacquiBT: 
    Hi Winston. Dave will respond to your question
    7:24
    Sam: 
    Hi Josh, we are aware of this issue. This is a problem with the Xbox rather than the HH4 but something we are reviewing together.
    7:24
    Emma: 
    Hi the bennyboy, the main advantages of the hub 4 are the faster processor (3 x faster) and 5 GHz wifi. There is no interference with 5GHz so you get better performance and as the range isn't as wide you dont have to share the bandwidth with neighbours etc. the hub still has 2.4 GHz so you still have the range you have withhub 3 too!
    7:24
    Dave: 
    Hi Winston, I am afraid there's no simple answer as it really depends on what features are in use. But the Hub 4 meets the latest Broadband Equipment Energy Code of Conduct targets for energy consumption.
    7:25
    [Comment From Mel Mel : ] 
    Why did you ignore your existing customers loyalty by charging them for a new hub, don't they pay enough already in their monthly fees?
    7:25
    JacquiBT: 
    Hi Mel, Dave will reply to your question
    7:25
    [Comment From Winston Winston : ] 
    How long did it take you to design and develop the home hub 4?
    7:26
    JacquiBT: 
    Hi Winston, Emma will reply to your question
    7:27
    [Comment From George George : ] 
    Will we get manual power save back?
    7:27
    JacquiBT: 
    Hi Gerorge. Sam will answer your question
    7:28
    [Comment From Jade Jade : ] 
    Does the home hub 4 support ip6 through a future upgrade?
    7:28
    Emma: 
    Hi Winston, It was about 2 years when we first started the project with the first ideas and concepts
    7:29
    JacquiBT: 
    Hi Jade. Emma will reply to your question.
    7:29
    Emma: 
    Hi Jade, thats something we are working on so yes something for the future
    7:30
    Sam: 
    Hi George. With regards to the manual power save feature, we have looked to make this automatic for all of our customers. However, you are able to change the brightness of the lights as an additional step.
    7:30
    Dave: 
    Hi Mel - we've made a lot of changes for our existing customers since the launch of the Hub 3 a couple of years ago. Our customer offer for the Hub 4 only £35 - a really big discount compared to the full price of £109! We've also created a range of recontracting deals that contain a Hub 4 for only the cost of delivery. If you're out of contract or in the last 3 months, you could take advantage of those offers as well. We really want all of our customers to be able to take advantage of these options!
    7:31
    Sean Donnelly: 
    Did you know the Hub 4 has a faster processor? Inside the BT Home Hub 4 router is our latest Broadband processor – the brains of your Hub. It allows you to pass information between connected devices quicker than ever. So if you are transferring files from one computer to another or watching a film streamed from another device, the BT Home Hub 4 won't slow you down.
    7:31
    [Comment From thebennyboy thebennyboy : ] 
    Our house has very thick stone walls and the wireless is weak in certain rooms. We have a few devices in our house that support 5Ghz Wi-Fi. Does the HH4 also work ok with home plugs that use your power cables to provide network connectivity?
    7:32
    JacquiBT: 
    Hi thebennyboy. Sam will respond to your question
    7:32
    [Comment From Calvin Calvin : ] 
    What future developments are in the works for home hub 4?
    7:33

    DS wrote:
    Not many of my Q's are showing either. Could be busy I guess......
    yeah I can tell, I know your quesitons are pretty good but if you notice that JacquiBT is deliberately choosing the questions she wants to go through. The whole chat is based around the fact that they have added 5ghz. I am appauled as I was hoping to at least ask one question. 

  • Home hub 3 orange power light and speed problem

    Hi, I have posted this again as I think I posted in the wrong place last time being new to the site!
    Hi, I have a Home Hub 3 Version A. Orange power light constantly on.
    I came across this site while looking for answers and quickly registered to post this.
    I have tried all suggestions including a neighbours power supply (Version A as well) to no avail.
    Background to help with replies.
    I have been had option 3 since 2003.
    In that time I have had
    H H 1 (failed)
    H H 1 replacement (failed)
    Netgear – weak wireless and does not like Vodafone suresignal
    H H 2 constant dropouts
    Back to Netgear
    H H 3 Version A lasted 24hrs
    Back to Netgear.
    For the last 5 months we have been having line problems, regular dropouts.
    BT Openreach have been out 4 times, changed virtually everything and traced line back to Exchange.
    The last engineers conclusion was line at my home is capable of 12meg and was being throttled as he called it to around 6meg.
    He suggested trying a H H 3 and contacting BT for line to be opened up.
    For two reasons.
    With a faster speed line fault would be easier to locate.
    Line was capable of so much more.
    Several LONG calls to BT answering all the format questions first, (to be fair 0800 so no cost) each time first being told my speed was within contract stated speeds, then after my explanation regarding BT Openreach engineers views I was told an engineer would be contacted to improve line speed.
    Needless to say nothing happened.
    The frustrating point being each new call generated the same response – NOTHING on their system to show a previous call had been made by me.
    Hence the reason for this post.
    I feel the helpline, whilst free, achieves nothing except a long time on the phone answering repetitive questions answered before.
    I am loathe to phone again as I will undoubtedly be told there is no record of any previous calls or action and I want to resolve the H H 3 Version A problem so it can be used.
    Any help appreciated

    Hi John46 and thanks for the reply.
    Can't try H H 3 it is dead.
    i saw somewhere on the forums when i first found you about a route that simplifies action from BT.
    Have looked since and cannot locate it.
    Do you know where it is?
    With the Netgear which I have no option but to use,
    ADSL on reports
    Multiplex  VC-BASED
    VPI 0
    VCI 38
    Speedtester result............
    1. Best Effort Test:  -provides background information.
    Download  Speed
    6667 Kbps
    0 Kbps
    7150 Kbps
    Max Achievable Speed
     Download speedachieved during the test was - 6667 Kbps
     For your connection, the acceptable range of speeds is 2000-7150 Kbps.
     Additional Information:
     Your DSL Connection Rate :8128 Kbps(DOWN-STREAM), 448 Kbps(UP-STREAM)
     IP Profile for your line is - 7170 Kbps
    2. Upstream Test:  -provides background information.
    Upload Speed
    367 Kbps
    0 Kbps
    448 Kbps
    Max Achievable Speed
    >Upload speed achieved during the test was - 367 Kbps
     Additional Information:
     Upstream Rate IP profile on your line is - 448 Kbps
    Wall socket - tested by engineer and renewed AND RF filter fiited, just 'incase'.
    Noise test also done.
    Thank you for pointing me to the test, even if I had a game with Java before I could use it (New PC)!
    As I read the results I am under 8meg. Openreach engineer said line was being 'throttled' as it was capable of circa 12meg this distance from the exchange. I am meant to be on 20meg contract.
    Chhers,
    I will watch out for a reply.
    Any pointers on the H H 3 complaint route would be appreciated, i am begining to think I imagined it!!!
    ps Where is the rating star? I can't see it here ?

  • Home Hub 3 Power Supply

    I've just been given a Home Hub 3 but there is no power supply with it.
    Does anyone one know what the rated input of the hub is and where I might obtain the correct plug?

    Hi Geoff, just checked my HH3 plug and it's as follows:
    BT switching power supply
    Model No S018SB1200100
    P/N: 253371437
    Input 230v 50Hz 300mA
    Output 12.0v 1000mA
    For use with BT Home Hub 3.0 Type A
    On the HHub 3 itself
    Rated Input 12V 1A
    If that helps you
    Can't check HH2 at present as i put this in the loft, these i've seen on the sites as toekneem suggested but i have not seen the HH3 power supplies on there own only with HH3's. BT do supply a returns address if you want to return your old Hubs when upgrading but i can't find that at present, that might help if anyone has a contact for them, otherwise call BT direct?
    Good luck

  • Lost power plug for Home Hub 3

    Hi everyone! We somehow managed to lose our power supply plug for our Home Hub 3 and BT don't sell replacements...
    So I was going to ask if someone could possible measure the dimensions of their barrel connector on their HH 3 power plug, if we have the plug dimensions then we can just order a replacement plug from Amazon/eBay... We'd need the internal diameter, and the outer diameter of the connector. 
    If someone could do that it would be awesome and we'd be very grateful as we could then use the HH  
    Many thanks everyone,
    -Al
    P.S I did speak to live chat and was told that the techincal support team didn't have this sort of information 
    Solved!
    Go to Solution.

    Hi
    You may be better off going to that well known internet auction site and get the correct one (check type A, B) you could end up buying an incorrect one and ruining your hub.
    You would also have a spare hub.
    (If I have helped you in any way to say "Thank You" please click on the star next to the message. Thank You)
    If I have solved your Issue please click the "Mark as accepted solution" button.

  • Orange Power Light Home Hub 2

    for the last couple of days i have been randomly disconnected from my Internet but then a few minute after it reconnects. but today my internet just Disconnected and didnt come back on so i went to go an reset it. 
    when i went to reset the homehub i realised all the lights were off but the Power light was still on , but was flashing orange. i jsut thought it may have been my socket so i tried another one. and the same thing.
    i have Treid to reset it and reset to Defaults but nothing has worked. could this be a problem with the HUb itself.
    i need to find out what is causing this. any help would be really appreciated.
    thanks in advanced.

    This is help page for the 2 http://bt.custhelp.com/app/answers/detail/a_id/11397/~/what-do-the-lights-on-my-bt-home-hub-2.0-mean...
    See if it helps if not then need to contact CS and expain you have done the test and hub faulty and you need a replacement
    If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on the left-hand side of the post.
    If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

  • Manual Firmware Update for Home Hub 2?

    Due to a seperate problem mentioned on another thread, I am having to use my Home Hub 2 as an additional wireless AP with my Home Hub 3 as primary router.
    My HH2 is on an outdated firmware version but doesn't get updated as it is not directly connected to the ADSL connection, only via ethernet to my HH3.
    Is there a way I can apply the lastest firmware to my HH2 without having to use it as my primary router for a period of time?

    Hi unfortunately no the only way is with them on-line
    If you want to say thanks for a helpful answer,please click on the Ratings star on the left-hand side If the reply answers your question then please mark as ’Mark as Accepted Solution’

  • Is My Home Hub Outputting Too Much Power?

    My Home Hub 2 is currently outputting 7.9 dBm down and 1.6 dBm up. Is that too high? Is there anything I can do to reduce it?
    If my answer was helpful, please give me a star by clicking the star on the left hand side.
    Thank you.

    No, it's part of the DSLAM/MSAN to router negotiation process, to bring a solution to the line connection.

  • BT home hub 4 wireless connection issue on the Xbo...

    Hi all,
    It has been flagged to us that there may be an issue when connecting an Xbox 360 to the new BT home hub 4.
    As many of you are aware the new BT home hub 4 has dual wireless bands broadcasting in the  2.4 GHz and 5 GHz range.
    It seems that when connecting an Xbox 360 wirelessly to the hub 4, the Xbox will state that there is an error, like the one below.
    “There is more than one network in range that has this SSID, please change your router SSID before proceeding”
    This issue seems to be due to the fact then when the Xbox scans for the available wireless networks, it sees both SSID's  and insists that one of them must be changed in case of a conflict.
    This is an Xbox 360 issue and not a hub 4 problem
    When Xbox 360 was released some 8 years ago dual band routers were very uncommon; so the Xbox has not been setup to deal with this type of connection.
    To correct this issue we have some steps that you can follow so that you can connect to the hub. You will need to log into the BT home hub manager  and change the SSID on the 5 GHZ band being broadcasted from the hub.
    Steps to do this are as follows…….
    Log in to the Hub 4 in the normal manner setting up a new password or using the custom password that has been setup by the customer then navigate to the Advanced Settings
    Then select continue to advanced setting
    Then select wireless
    Then select 5GHZ
    After that you will need to change Sync with 2.4 from yes to NO
    After this has been done you will then be able to change the SSID of the 5GZ band adding a number or a letter to the end
    After all this has been done you will then need to click apply to save the changes
    You will now be able to connect the Xbox in the normal way using the default wireless key 
    BTCare Community Mod
    If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on the left-hand side of the post. If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

    Try changing the wireless channel in the hub. Enter 192.168.1.254 then go to wireless switch to manual and try another channel. You can try downloading inssider3 which will show netwrorks and their channels round about you
    If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on the left-hand side of the post.
    If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

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

  • Home Hub 3-- Re-activating BTWIFI and BTFON signal...

    I have a Home Hub 3 and some days ago I had to do a factory reset on it. After that I had lost the BTWIFI and BTWIFI-with FON hotspot signals from the hub.
    When I logged in to the hub it said “You aren't currently part of the BT FON WiFi Community”.
    I found this page on your website: http://bt.custhelp.com/app/answers/detail/a_id/12987/~/i%27ve-changed-my-bt-home-hub-and-my-bt-wi-fi...
    I carried out the instructions to opt out and to opt in again, but after 3 days nothing had happened. There were still no hotspot signals from the hub and if I looked at the hub it still said “You aren't currently part of the BT FON WiFi Community”, despite the fact that if I checked my status online it said “opted in”.
    I then called the support number 0800 022 3322 recommended on this forum and got the Indian call centre who told me that home hubs do not have a dedicated hotspot signal and that the problem was due to a lack of hotspots in my area….!!!
      I then sent a support message using the BT support contact form describing the above problem and asking if they could re-instate the signals manually. This is the reply I received:
    “*removed
    This reply was also from India and needless to say, I did not phone the help desk as suggested, as this was the same number that had failed me previously. It is obvious that BT staff in India are not aware of how BT provide hotspots in the UK.
     I opted out and in again once more at that point, but it is now 5 days since my opt in and nothing has happened at the hub.
      So my question is, is there a way of contacting someone in BT in the UK who understands the problem and can arrange for the hotspot signals to be re-activated on the hub.
     After all, they were de-activated inadvertently, and you would think that it would be in BT’s interests to activate them again as soon as possible.
     I have no complaints about the BT broadband service, and I can understand the need for them to use an inexpensive call centre to filter out most of the simple queries, but in situations where the staff do not understand or cannot help they should refer the customer back to someone in the UK qualified to solve the problem.
    Solved!
    Go to Solution.

    All power to the Mods! I had a letter from Stuart this morning saying he had checked my hub status and that it was queued for activation and that it should happen within 48 hours, but by the time I read his letter it was already activated. He thinks it was a combination of luck and co-incidence, but I blame divine intervention.
      So I have marked SJTP’s post as the accepted solution. Thank you.
      However, it should not be necessary to resort to these forums and the mods to resolve a problem like this, so I am going to suggest the following to any BT employees who might be interested.
      While having a call centre in India is an inexpensive way of dealing with most of the problems raised by BT’s clients, there will always be some problems that are not resolved or are advised badly due to the limited training of call centre staff.  At present BT send a customer satisfaction survey after any query of their call centre, but the results are used for their own purposes. What I would suggest is that any unresolved issues at that point should result in the client being given a contact to a UK based technical team so they can have some hope that their issue would be resolved.
      This would create a huge boost to BT’s image amongst users and would probably greatly reduce the number of issues on this forum, particularly the ones resulting in negative press for BT.

  • Fed up with resetting my BT Home Hub 3 and it's so...

    I keep having to reset my BT Home Hub 3 because of problems with wireless connections.
    The Hub is close to all the equipment.
    I have lots of things connected to it:
    -          iPhones - Slow not much better that 3G
    -          Blackberrys
    -          Macbook - Very fast
    -          2 Dell Laptops - Slow
    -          New model Panasonic TV – Viera ST50 Series – Has Wireless inbuilt – New this year - Slow + buffering problems
    -          Sky Box connected via Netgear WN2000RPT Wifi Range Extender - Slow + buffering problems
    -          Hard wired PC - Very fast
    All worked fine with my old Netgear Router (before I changed to BT).
    When I first had this Hub (it’s my 2nd) all was OK for a couple of weeks.
    After a while (usually a few days after resetting BT Home Hub) the older Dell Laptop will keep losing its connection.   Once the problem starts the laptop might last for 5 or 10 minute intervals, lose connection and then automatically reconnect, etc, etc.
    I'm will to accept that the Laptop is old, but when the Laptop is playing up the TV plays up too.    The Internet on the TV’s also fails.
    The answer is to reboot the BT Home Hub.   The Laptop and TV are then both OK (for a few days).
    I’m getting fed up with resetting the Hub.   Especially as it has dropped out while watching online TV.
    All the other devices appear OK (maybe slow but remain connected).   Only the older laptop and the TV actually lose connection.   But resetting the BT Hub fixes the problem for a few days.   So the hub is at fault.
    Recently I’ve been getting other problems.   Now whenever I need to reset the BT Home Hub I need to disconnect the Netgear WN2000RPT.   If I don’t  disconnect the Netgear the BT Home Hub appears to start up and connect OK and everything appears to connect to the Hub OK.  But then none of the Internet content works.   Websites don’t work, TV reports no content.
    Now whenever I reset the BT Home Hub I must first turn off the Netgear WN2000RPT.   Previously this never used to be a problem.
    In case compatibility with the Netgear WN2000RPT is an issue I now usually leave it unplugged.   I only turn it on for Internet content from Sky.
    But the problems described above continue even when Netgear WN2000RPT is turned off.
    When playing up the Laptop sometimes shows “Unsecure Connection”.  I wonder if it’s picked up the BT FON connection (but it shows the normal connection).    I suspect the start of the problems may have coincided with the activation of BT FON on the box (could this have taken 2 weeks?).   I’m sure that it was BT FON that completely broke my first BT Home Hub 3, we had had it about a week, then wifi would not connect from anything, after hours on the phone to BT support we could not establish a wireless connection to the Hub, but strangely all was OK on the FON connection.
    We have BT Infinity.
    Hub is generally slow.   Wired Internet is lightning fast.   New Macbook (using Chrome) via wifi is lightning fast.   Everything else disappointingly slow.   TV and Sky both have buffering issues.
    Any ideas?
    Solved!
    Go to Solution.

    Ludite60
    The HH3 has the ability to hop around the various Wireless Channels (of which there are 14, see http://en.wikipedia.org/wiki/List_of_WLAN_channels for indepth info) to enable the hub to pick the best channel for you, taking into account any cordless phones, mobile phones, microwaves etc, all of which could interfere with your wireless signal.
    By reseting you HH3 you are forcing it back to its factory default channel (Channel 7 I guess).  Over a period of days, the HH3 may decide that its default channel isn't the most appropriate and select another channel based on what interference it 'sees'- clearly if it gets this wrong (as my HH3 did) then you potentially get wireless reception issues.
    Consequently, I decided to manually find out what the best channel was by install a wireless scanner (free @ http://www.metageek.net/products/inssider/), then:
    1.  Manually change the HH3 Channel (via its settings)
    2.  Check the wireless reception 'power' using inSSider installed on the laptop around your house, ie next to your TV etc.
    3.  When you find the channel that gives you the best wireless reception, tell the HH3 to remain on that Channel by disabling the 'Smart Wireless' feature (there's some info on this @ http://bt.custhelp.com/app/answers/detail/a_id/322​36/~/how-do-i-change-the-wireless-channel-on-my-bt​...)
    As I say, my HH3's range was useless until I forced it to stick to a set Channel, now I have reliable coverage all around the house.  Hope this is some help.

  • Xbox 360: How To Open Your BT Home Hub Ports!

    If you use a BT Home Hub and Xbox Live, you may need to open ports for a better connection, even if your NAT tests as Open. Some issues that this will fix:
    Friends list Voice chat
    Joining friends list games
    Joining some games such as Call of Duty 3 (could not connect to all players error), or host in some games such as Gears of War. 
    I suggest backing up your router's settings after you make these changes if it works for you, and maybe before you start in case you mess something up!
    1. First lets reset our BT Home Hub to its factory settings:Link
    2. Go into your BT Home Hub and disable UPnP
    Go to http://bthomehub.home
    Click on Settings
    Log in with your Hubs defult Admin password.
    Click on Advanced Settings.
    Click on Continue to advanced settings.
    Click on Applications Sharing.
    Click on UPnP.
    Turn UPnP off and click apply.
    UPnP
    Universal Plug and Play. Great Idea. Not so good in the real world. In theory, you should disable UPnP if you set up forwarding rules. The purpose of UPnP is to automatically detect the ports that need to be opened, and open them for you. Unfortunately it doesn't always do it as efficiently as you could do it yourself. On the other hand sometimes a router with forwarding rules set up seems to connect better with UPnP enabled. Toggle both ways, remember to reboot the router after any changes you make. CONCLUSION ABOUT UPnP: Disable it before the first time you ever turn on your 360. 
    3. Lets make our Xbox IP address is static:
    In your 360's dashboard, go to the "System" blade and select "Network Settings", and then click "Edit Settings". You're now in the "Basic Settings" screen.
    Select the "IP settings" section. (later you'll also have to adjust the "DNS Settings" section right below it.). Change it from Automatic to Manual. You'll have to change all three things listed here:
    IP Address
    Subnet Mask
    Gateway
    Make the IP address about 20 numbers higher for the last three digits. For example, if your IP address is 192.168.0.101, you can use 192.168.0.121
    What numbers do I use?
    a) You can simpily write them down from the xboxes dashboard while you have it set to automatic.
    b) You can get this info from your PC. Go to start>>Run>>cmd. Now in the DOS interface, type ipconfig. The DNS is the same number as your gateway.
    When you entered all three items, click "done" and it will prompt you to do an Xbox Live test. You will fail it, but you have to test to continue (You can cancel the test before it ends).
    Now hit done again and back out to the Basic Settings, and select the DNS settings section, right under the IP Settings section. Change from Automatic to Manual. You only need to enter the Primary DNS server, leave the Secondary DNS server the way it is (blank). For the DNS server, you're going to use whatever you used for the Gateway.
    That's it. Now back out, do an xbox live test (otherwise it won't save) and you'll probably still get a moderate or strict NAT, or even Open. But even if it tests as open, that doesn't mean your ports are open. But it's a good sign.
    4. Open Your Ports
    Portforward.com is an excellent resource for this information. Select your BT Home Hub, next follow the tutorials to open the ports for Xbox live etc and the games you play!

    glad you solved your problem
    If you want to say thanks for a helpful answer,please click on the Ratings star on the left-hand side If the reply answers your question then please mark as ’Mark as Accepted Solution’

Maybe you are looking for

  • IE10 Compatibility with EPM workspace 11.1.2.2

    Hi, We are upgrading our browser from IExplore 8 to IExplore 10,Could any one please suggest does the EPM 11.1.2.2 Workspace supports IE 10. We are using EPM workspace for IR Reporting, also please confirm about IR Web Client Compatibility. Thanks, G

  • My bluetooth on r007 tx is not working

    please help me out my bluetooth is no functioning it doest show bluetooth icon in control panel also

  • Ipod touch5 gen freeze

    Hello and Happy New Year every one ! I have an Ipod touch 5 Gen which I like very much and I do all my graphic and photo works with it. Last night It was very buggy and crashing an specific app all the time so I decided to close and restart the devic

  • HT1296 my iTunes will not load podcasts onto my iPhone.  Everything stays in the cloud for streaming!  HelP!

    my itunes will not load podcasts on my iphone for review later.  everything stays up in the cloud and wants to stream  I want to download the content to the iphone.  HELP!  Never had this problem before IOS 7

  • Ocx in forms6i

    We are planning to undertake the development of a large Enterprise Application System in Developer 2000 Forms 6i. We also want to keep an option open to be able to migrate our application at a later date to Forms 9i. We understand that in Forms 9i, s