Certificate Weirdness

RoboHelp HTML Version 8
I've been generating my AIRHelp to a folder on the local network for ages with no problem. I've been using a self-signed certificate (p12 format). Today, I switched to a "real" certificate from Verisign (pfx format), but for some strange reason, towards the end of the generation process, I get this error:
Adobe AIR
Adobe AIR output could not be generated.
'\\company.local\Local_Storage\Corporate_Organization\All_Departments\live-docs\xxx\xxx\files'
OK  
...then I click OK, everything stops, and no Help is generated. The files folder does get populated with quite a few files, but for some reason the process stops there.
If I switch back to the old certificate, everything works fine again.
Any ideas?

I had problems with changing the extension to P12 but using PFX worked fine.
I have now added detailed instructions on the procedure at http://www.grainge.org/pages/authoring/air/8/air_rh8.htm
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Similar Messages

  • Device enrolment and push notification certificates weirdness

    Really hope someone can help me with this one.
    After a fierce fight with my server I decided to do a clean install to make sure everything is in it's intended place and state.
    Besides many, many other issues (suddenly disappearing of Open Directory, weird profile manager errors, binding issues etc etc) this is the one I really don't understand.
    All settings are good and tested (DNS, IP's etc).
    Enrolment of devices seems to go well. I can install trust profiles on my macbook pro, macmini, iphone and ipad. All lights green there. Enrollment of non-ios devices all work fine, but when I enroll more than one ios device something weird happens. It doesn't matter if I enroll the iphone or the ipad first. The first enrolled device works fine, push notifications also works fine for this one.
    The second one just doesn't stick. It sort of shows up in the web based profile manager but doesn’t carry the correct name. It just says ‘New Device’. In the web based enrollment environment (server.domain.com/mydevices) the dysfunctional ios device appears and disappears randomly. I can't push anything toward it.
    I added some images.
    Also weird! Although I did a clean install, my push certificates are all ‘signed by an unknown authority’. The rest of the certificates (they are all there) are healthy. I have seen these certificates before when they where nice and green saying that they where trusted. Is this a problem on Apple’s side?
    Hope someone relieves some of my struggle.
    Thanks!

    THANK YOU...I have been putting off creating new certificates foR weeks, because the process drives me nuts! (I'm just a designer.)
    Thank you ADOBE for making the certificate instructions in the companion guides better...too bad this bug had me just about pulling my hair out because I know I was following the directions step by step!

  • Installing SSL Certificates on OS X 10.7 Lion Server

    Is there anybody out there that has gotten this to work.
    Have been at this for 3 days. Now on 10th clean install.
    Have tried different SSL certificates from different CA vendors. All on clean installs.
    Can install along with intemediate certificates.
    Differnet SSL checkers report differing results. Some will report as fine whilst others will report that the chain is broken.
    Some examples:
    https://knowledge.rapidssl.com/support/ssl-certificate-support/index?page=conten t&id=SO9556&actp=LIST&viewlocale=en_US
    Will report a double entry
    http://www.digicert.com/help/
    will report a break between the server certificate and the first intermediate certificate which it recognises as the same server certificate (weird!)
    https://www.ssllabs.com/ssldb/analyze.html
    Will report "incorrect order"
    http://www.sslshopper.com/ssl-checker.html
    Seems to report as fine although you will notice the server certificate twice in the chain again first as Server then first link in chain
    I assure you have only installed certificates once (1 for purchased cert and 1 for intermediate) at the beginning of a clean install.
    At a loss with this and very frustrated after 3 days getting no where.
    Anyone able to help?

    https://certs.godaddy.com/ccp/tools/sslinstallvalidator.seam
    Will report "Chain of Trust broken!"
    All this despite being able to access the server over SSL just fine. Need to get this to work properly though to make use of profile manager.

  • IPhone 6+ weird certificate keeps popping out

    Hello all, I am having troubles with the certificate verification pops out in my iphone 6+.
    My phone is a iphone 6+ with iOS 8.1.1
    Starting last week, whenever i unlocked my phone or in the middle of using my phone, this weird certificate verificaton pops out (pls see attached images), and this really is annoying because it pops out quite often now. I never clicked continue nor turst the certificate because i dont know where they are from, but when i clicked details to understand, it shows very weird websites sources that worries me and cocerns about my phone's security issue. I've never seen these websites nor ever visited them before.
    Can someone please help me to clarify this situation and offer a solution?
    Thank you so so muh!

    Where did you get the phone 'repaired"?

  • SSL certificate selection weirdness in iCal server config

    I have a wildcard certificate installed via the certificate manager on a 10.5 server, and it's working perfectly with dynamic virtual hosts in apache, with mail via POP3, IMAP and SMTP. However, something odd happens in iCal admin. The certificate popup menu contains:
    No certificate
    Custom Configuration...
    *.example.com
    Default
    Manage Certificates...
    So, I select my installed certificate and click save. The certificate popup immediately changes to "Custom Configuration..." and I'm asked whether I want to restart iCal for the change, which I accept.
    Connections to iCal work when SSL is off, but if I use an SSL URL like:
    https://ical.example.com:8443/principals/users/myname/
    I get this error:
    Account information not found
    Unexpected secure name resolution error (code -9844). The server name ical.example.com may be incorrect.
    When SSL is on, non-secure requests just don't respond.
    Nothing appears in the iCal server log.
    If I select the custom config from the certificate menu, it just shows me the same certificate and key path that the certificate manager does, so I've no idea why it's reverting in the menu when it doesn't in other service admin panels.
    The necessary firewall ports are open, though I've tried it with the firewall off just to check.
    I've heard that if DNS doesn't have matching forward and reverse resolution the first time iCal is configured, it can screw things up, and I did that, but I've no idea what effect it has.
    Any ideas?
    (names have been changed to protect the innocent!)
    Message was edited by: Marcus Bointon
    Message was edited by: Marcus Bointon

    Sounds like you're looking at the access log.
    The error log is the one that would have the funny business listed.
    Try switching logs through the dropdown at the bottom of the server-admin ical logs screen.
    When I enable SSL and try to visit the page via https://host:8443/ the error log for the ical service shows a number of processes dying with the following error: (replaced real date/time to save time!)
    pydir] date/time marking host ('127.0.0.1', 8444) down ([Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionRefusedError'>: Connection was refused by other side: 61: Connection Refused.
    pydir] date/time ])
    pydir] date/time retrying with ('127.0.0.1', 8445)
    Then it goes on to repeat the error with 8445 and so on until it reaches 8451. (they look like PID numbers.. not port numbers. see below.) Afterwards I receive:
    pydir] date/time no working servers, manager -> aggressive
    pydir] date/time re-adding ('127.0.0.1', 8449) automatically
    Message was edited by: noneoftheabove - cleaned up error msgs

  • Weird Javascript problem on Safari and other web browsers

    Hello,
    this is actually pretty weird. For the past several weeks I have been dealing with a very strange problem which I believe relates to JavaScript. To be more specific I have an issue with two websites: Macuser.gr and Facebook.com.
    As far as Macuser.gr is concerned this is how it's supposed to look:
    http://f.cl.ly/items/0j1J123Y2D0t1C2U3b1f/Screen%20Shot%202013-02-06%20at%202.25 .04%20PM.jpg
    and this is how Safari renders it:
    http://f.cl.ly/items/3N0V3I1c0Q0a1r0K0e1C/Screen%20Shot%202013-02-06%20at%202.25 .40%20PM.jpg
    The problem is with the preview images as you can see.
    Now, in Facebook there's this annoying white line where it isn't supposed to be:
    http://f.cl.ly/items/0k0i2c0T0q1h3t2j2s3e/Screen%20Shot%202013-02-06%20at%202.25 .52%20PM.jpg
    I have tried and tested everything (Guest user, different browsers etc) and all it comes down to is JavaScript. Disabling Javascript seems to fix everything immediately. Enabling it again and this mess occurs. Also, this happens with the latest versions of Safari, Chrome and Firefox BUT not with Camino 2.1.2 although it has JavaScript enabled in it.
    This is really frustrating and it appeared out of the blue one day. I did not have this problem from day 1. Any ideas?

    Boot into Recovery by holding down the key combination command-R at the startup chime. Release the keys when you see a gray screen with a spinning dial.
    Note: You need an always-on Ethernet or Wi-Fi connection to the Internet to use Recovery. It won’t work with USB or PPPoE modems, or with proxy servers, or with networks that require a certificate for authentication.
    From the OS X Utilities screen, select Get Help Online. A clean copy of Safari will launch. No plugins, such as Flash, will be available. While in Recovery, you'll have no access to your saved bookmarks or passwords, so make a note of those before you begin, if they're needed for the test.
    Test. After testing, reboot as usual and post the results.

  • Verification failed certificate for this server is invalid

    I attempt to log into the iCloud on my iPod over a WiFi connection and it gives me the Verification Failed. The certificate for this server is invalid. You might be connecting to a server that is pretending to be "setup.icloud.com" which could put your confidential information at risk.
    Why am I getting this and how can I access the iCloud to backup my files?

    This happened to me because my router was configured to use Open DNS servers (Primary 208.67.222.222, Secondary 208.67.220.220). Temporarily adjusting the DNS settings on the router to 4.2.2.1 and 4.2.2.2 did the trick. Open DNS does weird things with certain certificates. Even if your router is configured to used something else, try the ones listed above to see if it makes a difference.

  • PKI SCCM Client Certificate Template not viewable by Windows 7 and Server 2008 workgroup machines.

    Hello everyone,
    I’m having issues with workgroup computers, not domain systems when I request a certificate.
    It’s extremely weird. It has something to do with Windows 7 and Windows 2008 machines. In 2003 server I can request a certificate manually with certutil and it see the certificate template. I copy over the exact command
    on windows 7 and it can’t see the certificate template.
    I have the following configuration:
    CA Enterprise
    I have created the SCCM Client Certificate
    I have created the SCCM Web Server Certificate
    I have created the SCCM Distribution Point Certificate
    GPO is configured
    SCCM 2012 R2 CU2 configured to do HTTP and HTTPS
    Installed SCCM Client Certificate
    Installed SCCM Web Server Certificate
    Installed Distribution Point Certificate
    Deployed to a domain computer good on PKI
    Workgroup Computers:
    I’m having issues with deploying certificates
    Windows 7 –
    (ERROR) not successful
    Windows Server 2008 R2 –
    (ERROR) not successful
    Windows Server 2003 - successful
    Windows XP – successful
    How I’m getting the certs for the clients is by utilizing the following scripts from this URL.
    http://www.ithierarchy.com/ITH/node/48
    I did find a couple of errors in the code, but if it’s working on my Server 2003, then it should work on the others. Windows 7 and Windows 2008 R2 seem to have the same issue. The error I’m getting is the following:
    Command line requesting the cert ---- CertReq –new –f testcomputer.home.pvt.inf c:\client\testcomputer.home.pvt.req
    Error --- Template not found.
    SCCMClientCertificate (this is my template)

    Just to give an update on what’s happening with this. I found out this format is unsupported by MS with Windows Vista and newer OS’s.
    Instead you must utilize two other additional roles on the CA to have this work. The caviate is, I’m down to the testing and it’s not working as in the document. I have MS Support
    working with me to resolve this issue since it was written by MSFT.
    http://blogs.technet.com/b/askds/archive/2010/05/25/enabling-cep-and-ces-for-enrolling-non-domain-joined-computers-for-certificates.aspx
    and use this doc for similar workgroup computers for rolling out certs. This was written for RT devices, however, it should work once I get to that point.
    http://blogs.technet.com/b/pki/archive/2012/12/11/certificate-for-winrt-devices-and-non-domain-member-devices.aspx

  • PKI Client Certificate Template not viewable by Windows 7 and Server 2008 workgroup machines.

    Hello everyone,
    I’m having issues with workgroup computers, not domain systems when I request a certificate.
    It’s extremely weird. It has something to do with Windows 7 and Windows 2008 machines. In 2003 server I can request a certificate manually with certutil and it see the certificate template. I copy over the exact command
    on windows 7 and it can’t see the certificate template.
    I have the following configuration:
    CA Enterprise
    I have created the SCCM Client Certificate
    I have created the SCCM Web Server Certificate
    I have created the SCCM Distribution Point Certificate
    GPO is configured
    SCCM 2012 R2 CU2 configured to do HTTP and HTTPS
    Installed SCCM Client Certificate
    Installed SCCM Web Server Certificate
    Installed Distribution Point Certificate
    Deployed to a domain computer good on PKI
    Workgroup Computers:
    I’m having issues with deploying certificates
    Windows 7 –
    (ERROR) not successful
    Windows Server 2008 R2 –
    (ERROR) not successful
    Windows Server 2003 - successful
    Windows XP – successful
    How I’m getting the certs for the clients is by utilizing the following scripts from this URL.
    http://www.ithierarchy.com/ITH/node/48
    I did find a couple of errors in the code, but if it’s working on my Server 2003, then it should work on the others. Windows 7 and Windows 2008 R2 seem to have the same issue. The error I’m getting is the following:
    Command line requesting the cert ---- CertReq –new –f testcomputer.home.pvt.inf c:\client\testcomputer.home.pvt.req
    Error --- Template not found.
    SCCMClientCertificate (this is my template)

    Just to give an update on what’s happening with this. I found out this format is unsupported by MS with Windows Vista and newer OS’s.
    Instead you must utilize two other additional roles on the CA to have this work. The caviate is, I’m down to the testing and it’s not working as in the document. I have MS
    Support working with me to resolve this issue since it was written by MSFT.
    http://blogs.technet.com/b/askds/archive/2010/05/25/enabling-cep-and-ces-for-enrolling-non-domain-joined-computers-for-certificates.aspx
    and use this doc for similar workgroup computers for rolling out certs. This was written for RT devices, however, it should work once I get to that point.
    http://blogs.technet.com/b/pki/archive/2012/12/11/certificate-for-winrt-devices-and-non-domain-member-devices.aspx

  • Weird UEFI-releated 3.17.1 kernel bug (rtc-efi?)

    Yesterday I updated to the last core/linux kernel, and I'm having a weird behaviour that leads to a complete system lock a minute or two after booting, but only on cold boots (i.e. plugging the  AC adapter, turning on the machine and booting the kernel, not on reboots).
    This is the kernel trace i've extracted from journalctl, with some columns removed to make the log a bit less large:
    09:50:03 kernel: Command line: initrd=\intel-ucode.img initrd=\initramfs-linux.img rw root=PARTUUID=8919781b-f582-49ff-9a79-d252bc62775c rcutree.rcu_idle_gp_delay=1 quiet resume=/dev/disk/by-partuuid/563ee90f-7f47-4c44-93ed-23c8278957f5
    09:50:03 kernel: e820: BIOS-provided physical RAM map:
    09:50:03 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
    09:50:03 kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
    09:50:03 kernel: BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x0000000020200000-0x0000000040003fff] usable
    09:50:03 kernel: BIOS-e820: [mem 0x0000000040004000-0x0000000040004fff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x0000000040005000-0x00000000c9747fff] usable
    09:50:03 kernel: BIOS-e820: [mem 0x00000000c9748000-0x00000000c9d48fff] ACPI NVS
    09:50:03 kernel: BIOS-e820: [mem 0x00000000c9d49000-0x00000000c9d4bfff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x00000000c9d4c000-0x00000000c9d61fff] usable
    09:50:03 kernel: BIOS-e820: [mem 0x00000000c9d62000-0x00000000c9d67fff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x00000000c9d68000-0x00000000c9d69fff] usable
    09:50:03 kernel: BIOS-e820: [mem 0x00000000c9d6a000-0x00000000c9d73fff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x00000000c9d74000-0x00000000c9f07fff] usable
    09:50:03 kernel: BIOS-e820: [mem 0x00000000c9f08000-0x00000000c9f0bfff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x00000000c9f0c000-0x00000000c9f54fff] usable
    09:50:03 kernel: BIOS-e820: [mem 0x00000000c9f55000-0x00000000c9f7afff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x00000000c9f7b000-0x00000000c9f7dfff] usable
    09:50:03 kernel: BIOS-e820: [mem 0x00000000c9f7e000-0x00000000c9f7ffff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x00000000c9f80000-0x00000000c9f96fff] usable
    09:50:03 kernel: BIOS-e820: [mem 0x00000000c9f97000-0x00000000c9f9cfff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x00000000c9f9d000-0x00000000c9fa4fff] usable
    09:50:03 kernel: BIOS-e820: [mem 0x00000000c9fa5000-0x00000000c9fa5fff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x00000000c9fa6000-0x00000000c9fb4fff] usable
    09:50:03 kernel: BIOS-e820: [mem 0x00000000c9fb5000-0x00000000c9fb5fff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x00000000c9fb6000-0x00000000c9fc0fff] usable
    09:50:03 kernel: BIOS-e820: [mem 0x00000000c9fc1000-0x00000000c9fc5fff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x00000000c9fc6000-0x00000000c9ff1fff] usable
    09:50:03 kernel: BIOS-e820: [mem 0x00000000c9ff2000-0x00000000c9ff2fff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x00000000c9ff3000-0x00000000ca002fff] usable
    09:50:03 kernel: BIOS-e820: [mem 0x00000000ca003000-0x00000000ca029fff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x00000000ca02a000-0x00000000ca03cfff] usable
    09:50:03 kernel: BIOS-e820: [mem 0x00000000ca03d000-0x00000000ca03dfff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x00000000ca03e000-0x00000000ca03efff] usable
    09:50:03 kernel: BIOS-e820: [mem 0x00000000ca03f000-0x00000000ca040fff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x00000000ca041000-0x00000000ca041fff] usable
    09:50:03 kernel: BIOS-e820: [mem 0x00000000ca042000-0x00000000ca046fff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x00000000ca047000-0x00000000ca05dfff] usable
    09:50:03 kernel: BIOS-e820: [mem 0x00000000ca05e000-0x00000000ca601fff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x00000000ca602000-0x00000000ca881fff] ACPI NVS
    09:50:03 kernel: BIOS-e820: [mem 0x00000000ca882000-0x00000000ca886fff] ACPI data
    09:50:03 kernel: BIOS-e820: [mem 0x00000000ca887000-0x00000000ca887fff] usable
    09:50:03 kernel: BIOS-e820: [mem 0x00000000ca888000-0x00000000ca8cafff] ACPI NVS
    09:50:03 kernel: BIOS-e820: [mem 0x00000000ca8cb000-0x00000000cacd7fff] usable
    09:50:03 kernel: BIOS-e820: [mem 0x00000000cacd8000-0x00000000caff3fff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x00000000caff4000-0x00000000caffffff] usable
    09:50:03 kernel: BIOS-e820: [mem 0x00000000cbc00000-0x00000000cfdfffff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
    09:50:03 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000022f1fffff] usable
    09:50:03 kernel: NX (Execute Disable) protection: active
    09:50:03 kernel: e820: update [mem 0xbe713018-0xbe729057] usable ==> usable
    09:50:03 kernel: e820: update [mem 0xbe744018-0xbe754057] usable ==> usable
    09:50:03 kernel: e820: update [mem 0xbe706018-0xbe712057] usable ==> usable
    09:50:03 kernel: extended physical RAM map:
    09:50:03 kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009efff] usable
    09:50:03 kernel: reserve setup_data: [mem 0x000000000009f000-0x000000000009ffff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x0000000000100000-0x000000001fffffff] usable
    09:50:03 kernel: reserve setup_data: [mem 0x0000000020000000-0x00000000201fffff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x0000000020200000-0x0000000040003fff] usable
    09:50:03 kernel: reserve setup_data: [mem 0x0000000040004000-0x0000000040004fff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x0000000040005000-0x00000000be706017] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000be706018-0x00000000be712057] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000be712058-0x00000000be713017] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000be713018-0x00000000be729057] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000be729058-0x00000000be744017] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000be744018-0x00000000be754057] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000be754058-0x00000000c9747fff] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000c9748000-0x00000000c9d48fff] ACPI NVS
    09:50:03 kernel: reserve setup_data: [mem 0x00000000c9d49000-0x00000000c9d4bfff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x00000000c9d4c000-0x00000000c9d61fff] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000c9d62000-0x00000000c9d67fff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x00000000c9d68000-0x00000000c9d69fff] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000c9d6a000-0x00000000c9d73fff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x00000000c9d74000-0x00000000c9f07fff] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000c9f08000-0x00000000c9f0bfff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x00000000c9f0c000-0x00000000c9f54fff] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000c9f55000-0x00000000c9f7afff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x00000000c9f7b000-0x00000000c9f7dfff] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000c9f7e000-0x00000000c9f7ffff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x00000000c9f80000-0x00000000c9f96fff] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000c9f97000-0x00000000c9f9cfff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x00000000c9f9d000-0x00000000c9fa4fff] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000c9fa5000-0x00000000c9fa5fff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x00000000c9fa6000-0x00000000c9fb4fff] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000c9fb5000-0x00000000c9fb5fff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x00000000c9fb6000-0x00000000c9fc0fff] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000c9fc1000-0x00000000c9fc5fff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x00000000c9fc6000-0x00000000c9ff1fff] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000c9ff2000-0x00000000c9ff2fff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x00000000c9ff3000-0x00000000ca002fff] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000ca003000-0x00000000ca029fff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x00000000ca02a000-0x00000000ca03cfff] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000ca03d000-0x00000000ca03dfff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x00000000ca03e000-0x00000000ca03efff] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000ca03f000-0x00000000ca040fff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x00000000ca041000-0x00000000ca041fff] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000ca042000-0x00000000ca046fff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x00000000ca047000-0x00000000ca05dfff] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000ca05e000-0x00000000ca601fff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x00000000ca602000-0x00000000ca881fff] ACPI NVS
    09:50:03 kernel: reserve setup_data: [mem 0x00000000ca882000-0x00000000ca886fff] ACPI data
    09:50:03 kernel: reserve setup_data: [mem 0x00000000ca887000-0x00000000ca887fff] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000ca888000-0x00000000ca8cafff] ACPI NVS
    09:50:03 kernel: reserve setup_data: [mem 0x00000000ca8cb000-0x00000000cacd7fff] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000cacd8000-0x00000000caff3fff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x00000000caff4000-0x00000000caffffff] usable
    09:50:03 kernel: reserve setup_data: [mem 0x00000000cbc00000-0x00000000cfdfffff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
    09:50:03 kernel: reserve setup_data: [mem 0x0000000100000000-0x000000022f1fffff] usable
    09:50:03 kernel: efi: EFI v2.31 by American Megatrends
    09:50:03 kernel: efi: ACPI=0xca852000 ACPI 2.0=0xca852000 SMBIOS=0xf04c0 MPS=0xfd4d0
    09:50:03 kernel: efi: mem00: type=3, attr=0xf, range=[0x0000000000000000-0x0000000000008000) (0MB)
    09:50:03 kernel: efi: mem01: type=2, attr=0xf, range=[0x0000000000008000-0x000000000000e000) (0MB)
    09:50:03 kernel: efi: mem02: type=7, attr=0xf, range=[0x000000000000e000-0x000000000005e000) (0MB)
    09:50:03 kernel: efi: mem03: type=4, attr=0xf, range=[0x000000000005e000-0x0000000000060000) (0MB)
    09:50:03 kernel: efi: mem04: type=3, attr=0xf, range=[0x0000000000060000-0x000000000009f000) (0MB)
    09:50:03 kernel: efi: mem05: type=6, attr=0x800000000000000f, range=[0x000000000009f000-0x00000000000a0000) (0MB)
    09:50:03 kernel: efi: mem06: type=7, attr=0xf, range=[0x0000000000100000-0x0000000001000000) (15MB)
    09:50:03 kernel: efi: mem07: type=2, attr=0xf, range=[0x0000000001000000-0x0000000001100000) (1MB)
    09:50:03 kernel: efi: mem08: type=7, attr=0xf, range=[0x0000000001100000-0x0000000002000000) (15MB)
    09:50:03 kernel: efi: mem09: type=2, attr=0xf, range=[0x0000000002000000-0x0000000002f53000) (15MB)
    09:50:03 kernel: efi: mem10: type=7, attr=0xf, range=[0x0000000002f53000-0x0000000020000000) (464MB)
    09:50:03 kernel: efi: mem11: type=0, attr=0xf, range=[0x0000000020000000-0x0000000020200000) (2MB)
    09:50:03 kernel: efi: mem12: type=7, attr=0xf, range=[0x0000000020200000-0x0000000040004000) (510MB)
    09:50:03 kernel: efi: mem13: type=0, attr=0xf, range=[0x0000000040004000-0x0000000040005000) (0MB)
    09:50:03 kernel: efi: mem14: type=7, attr=0xf, range=[0x0000000040005000-0x000000007fb8e000) (1019MB)
    09:50:03 kernel: efi: mem15: type=2, attr=0xf, range=[0x000000007fb8e000-0x0000000080000000) (4MB)
    09:50:03 kernel: efi: mem16: type=7, attr=0xf, range=[0x0000000080000000-0x00000000bc400000) (964MB)
    09:50:03 kernel: efi: mem17: type=1, attr=0xf, range=[0x00000000bc400000-0x00000000be353000) (31MB)
    09:50:03 kernel: efi: mem18: type=7, attr=0xf, range=[0x00000000be353000-0x00000000be706000) (3MB)
    09:50:03 kernel: efi: mem19: type=2, attr=0xf, range=[0x00000000be706000-0x00000000be72a000) (0MB)
    09:50:03 kernel: efi: mem20: type=1, attr=0xf, range=[0x00000000be72a000-0x00000000be741000) (0MB)
    09:50:03 kernel: efi: mem21: type=7, attr=0xf, range=[0x00000000be741000-0x00000000be744000) (0MB)
    09:50:03 kernel: efi: mem22: type=2, attr=0xf, range=[0x00000000be744000-0x00000000be755000) (0MB)
    09:50:03 kernel: efi: mem23: type=4, attr=0xf, range=[0x00000000be755000-0x00000000be76e000) (0MB)
    09:50:03 kernel: efi: mem24: type=7, attr=0xf, range=[0x00000000be76e000-0x00000000be777000) (0MB)
    09:50:03 kernel: efi: mem25: type=4, attr=0xf, range=[0x00000000be777000-0x00000000be92d000) (1MB)
    09:50:03 kernel: efi: mem26: type=7, attr=0xf, range=[0x00000000be92d000-0x00000000be92e000) (0MB)
    09:50:03 kernel: efi: mem27: type=2, attr=0xf, range=[0x00000000be92e000-0x00000000be933000) (0MB)
    09:50:03 kernel: efi: mem28: type=4, attr=0xf, range=[0x00000000be933000-0x00000000bec76000) (3MB)
    09:50:03 kernel: efi: mem29: type=2, attr=0xf, range=[0x00000000bec76000-0x00000000bec77000) (0MB)
    09:50:03 kernel: efi: mem30: type=4, attr=0xf, range=[0x00000000bec77000-0x00000000c909e000) (164MB)
    09:50:03 kernel: efi: mem31: type=7, attr=0xf, range=[0x00000000c909e000-0x00000000c9722000) (6MB)
    09:50:03 kernel: efi: mem32: type=3, attr=0xf, range=[0x00000000c9722000-0x00000000c9748000) (0MB)
    09:50:03 kernel: efi: mem33: type=10, attr=0xf, range=[0x00000000c9748000-0x00000000c9d49000) (6MB)
    09:50:03 kernel: efi: mem34: type=5, attr=0x800000000000000f, range=[0x00000000c9d49000-0x00000000c9d4c000) (0MB)
    09:50:03 kernel: efi: mem35: type=3, attr=0xf, range=[0x00000000c9d4c000-0x00000000c9d62000) (0MB)
    09:50:03 kernel: efi: mem36: type=5, attr=0x800000000000000f, range=[0x00000000c9d62000-0x00000000c9d68000) (0MB)
    09:50:03 kernel: efi: mem37: type=3, attr=0xf, range=[0x00000000c9d68000-0x00000000c9d6a000) (0MB)
    09:50:03 kernel: efi: mem38: type=5, attr=0x800000000000000f, range=[0x00000000c9d6a000-0x00000000c9d74000) (0MB)
    09:50:03 kernel: efi: mem39: type=3, attr=0xf, range=[0x00000000c9d74000-0x00000000c9f08000) (1MB)
    09:50:03 kernel: efi: mem40: type=5, attr=0x800000000000000f, range=[0x00000000c9f08000-0x00000000c9f0c000) (0MB)
    09:50:03 kernel: efi: mem41: type=3, attr=0xf, range=[0x00000000c9f0c000-0x00000000c9f55000) (0MB)
    09:50:03 kernel: efi: mem42: type=5, attr=0x800000000000000f, range=[0x00000000c9f55000-0x00000000c9f5c000) (0MB)
    09:50:03 kernel: efi: mem43: type=6, attr=0x800000000000000f, range=[0x00000000c9f5c000-0x00000000c9f69000) (0MB)
    09:50:03 kernel: efi: mem44: type=5, attr=0x800000000000000f, range=[0x00000000c9f69000-0x00000000c9f7b000) (0MB)
    09:50:03 kernel: efi: mem45: type=3, attr=0xf, range=[0x00000000c9f7b000-0x00000000c9f7e000) (0MB)
    09:50:03 kernel: efi: mem46: type=5, attr=0x800000000000000f, range=[0x00000000c9f7e000-0x00000000c9f80000) (0MB)
    09:50:03 kernel: efi: mem47: type=3, attr=0xf, range=[0x00000000c9f80000-0x00000000c9f97000) (0MB)
    09:50:03 kernel: efi: mem48: type=5, attr=0x800000000000000f, range=[0x00000000c9f97000-0x00000000c9f9d000) (0MB)
    09:50:03 kernel: efi: mem49: type=3, attr=0xf, range=[0x00000000c9f9d000-0x00000000c9fa5000) (0MB)
    09:50:03 kernel: efi: mem50: type=5, attr=0x800000000000000f, range=[0x00000000c9fa5000-0x00000000c9fa6000) (0MB)
    09:50:03 kernel: efi: mem51: type=3, attr=0xf, range=[0x00000000c9fa6000-0x00000000c9fb5000) (0MB)
    09:50:03 kernel: efi: mem52: type=5, attr=0x800000000000000f, range=[0x00000000c9fb5000-0x00000000c9fb6000) (0MB)
    09:50:03 kernel: efi: mem53: type=3, attr=0xf, range=[0x00000000c9fb6000-0x00000000c9fc1000) (0MB)
    09:50:03 kernel: efi: mem54: type=5, attr=0x800000000000000f, range=[0x00000000c9fc1000-0x00000000c9fc6000) (0MB)
    09:50:03 kernel: efi: mem55: type=3, attr=0xf, range=[0x00000000c9fc6000-0x00000000c9ff2000) (0MB)
    09:50:03 kernel: efi: mem56: type=5, attr=0x800000000000000f, range=[0x00000000c9ff2000-0x00000000c9ff3000) (0MB)
    09:50:03 kernel: efi: mem57: type=3, attr=0xf, range=[0x00000000c9ff3000-0x00000000ca003000) (0MB)
    09:50:03 kernel: efi: mem58: type=5, attr=0x800000000000000f, range=[0x00000000ca003000-0x00000000ca02a000) (0MB)
    09:50:03 kernel: efi: mem59: type=3, attr=0xf, range=[0x00000000ca02a000-0x00000000ca03d000) (0MB)
    09:50:03 kernel: efi: mem60: type=5, attr=0x800000000000000f, range=[0x00000000ca03d000-0x00000000ca03e000) (0MB)
    09:50:03 kernel: efi: mem61: type=3, attr=0xf, range=[0x00000000ca03e000-0x00000000ca03f000) (0MB)
    09:50:03 kernel: efi: mem62: type=5, attr=0x800000000000000f, range=[0x00000000ca03f000-0x00000000ca041000) (0MB)
    09:50:03 kernel: efi: mem63: type=3, attr=0xf, range=[0x00000000ca041000-0x00000000ca042000) (0MB)
    09:50:03 kernel: efi: mem64: type=5, attr=0x800000000000000f, range=[0x00000000ca042000-0x00000000ca047000) (0MB)
    09:50:03 kernel: efi: mem65: type=3, attr=0xf, range=[0x00000000ca047000-0x00000000ca05e000) (0MB)
    09:50:03 kernel: efi: mem66: type=6, attr=0x800000000000000f, range=[0x00000000ca05e000-0x00000000ca0be000) (0MB)
    09:50:03 kernel: efi: mem67: type=5, attr=0x800000000000000f, range=[0x00000000ca0be000-0x00000000ca0d8000) (0MB)
    09:50:03 kernel: efi: mem68: type=6, attr=0x800000000000000f, range=[0x00000000ca0d8000-0x00000000ca0db000) (0MB)
    09:50:03 kernel: efi: mem69: type=6, attr=0x800000000000000f, range=[0x00000000ca0db000-0x00000000ca0e3000) (0MB)
    09:50:03 kernel: efi: mem70: type=6, attr=0x800000000000000f, range=[0x00000000ca0e3000-0x00000000ca0e5000) (0MB)
    09:50:03 kernel: efi: mem71: type=6, attr=0x800000000000000f, range=[0x00000000ca0e5000-0x00000000ca102000) (0MB)
    09:50:03 kernel: efi: mem72: type=0, attr=0xf, range=[0x00000000ca102000-0x00000000ca46a000) (3MB)
    09:50:03 kernel: efi: mem73: type=0, attr=0xf, range=[0x00000000ca46a000-0x00000000ca602000) (1MB)
    09:50:03 kernel: efi: mem74: type=10, attr=0xf, range=[0x00000000ca602000-0x00000000ca6b2000) (0MB)
    09:50:03 kernel: efi: mem75: type=10, attr=0xf, range=[0x00000000ca6b2000-0x00000000ca86a000) (1MB)
    09:50:03 kernel: efi: mem76: type=10, attr=0xf, range=[0x00000000ca86a000-0x00000000ca86c000) (0MB)
    09:50:03 kernel: efi: mem77: type=10, attr=0xf, range=[0x00000000ca86c000-0x00000000ca882000) (0MB)
    09:50:03 kernel: efi: mem78: type=9, attr=0xf, range=[0x00000000ca882000-0x00000000ca887000) (0MB)
    09:50:03 kernel: efi: mem79: type=4, attr=0xf, range=[0x00000000ca887000-0x00000000ca888000) (0MB)
    09:50:03 kernel: efi: mem80: type=10, attr=0xf, range=[0x00000000ca888000-0x00000000ca8cb000) (0MB)
    09:50:03 kernel: efi: mem81: type=4, attr=0xf, range=[0x00000000ca8cb000-0x00000000caa17000) (1MB)
    09:50:03 kernel: efi: mem82: type=3, attr=0xf, range=[0x00000000caa17000-0x00000000cacaf000) (2MB)
    09:50:03 kernel: efi: mem83: type=4, attr=0xf, range=[0x00000000cacaf000-0x00000000cacbf000) (0MB)
    09:50:03 kernel: efi: mem84: type=3, attr=0xf, range=[0x00000000cacbf000-0x00000000cacd1000) (0MB)
    09:50:03 kernel: efi: mem85: type=4, attr=0xf, range=[0x00000000cacd1000-0x00000000cacd8000) (0MB)
    09:50:03 kernel: efi: mem86: type=6, attr=0x800000000000000f, range=[0x00000000cacd8000-0x00000000caff4000) (3MB)
    09:50:03 kernel: efi: mem87: type=4, attr=0xf, range=[0x00000000caff4000-0x00000000cb000000) (0MB)
    09:50:03 kernel: efi: mem88: type=7, attr=0xf, range=[0x0000000100000000-0x000000022f200000) (4850MB)
    09:50:03 kernel: efi: mem89: type=0, attr=0x8000000000000000, range=[0x00000000cbc00000-0x00000000cfe00000) (66MB)
    09:50:03 kernel: efi: mem90: type=11, attr=0x8000000000000001, range=[0x00000000f8000000-0x00000000fc000000) (64MB)
    09:50:03 kernel: efi: mem91: type=11, attr=0x8000000000000001, range=[0x00000000fec00000-0x00000000fec01000) (0MB)
    09:50:03 kernel: efi: mem92: type=11, attr=0x8000000000000001, range=[0x00000000fed00000-0x00000000fed04000) (0MB)
    09:50:03 kernel: efi: mem93: type=11, attr=0x8000000000000001, range=[0x00000000fed1c000-0x00000000fed20000) (0MB)
    09:50:03 kernel: efi: mem94: type=11, attr=0x8000000000000001, range=[0x00000000fee00000-0x00000000fee01000) (0MB)
    09:50:03 kernel: efi: mem95: type=11, attr=0x8000000000000001, range=[0x00000000ff000000-0x0000000100000000) (16MB)
    09:50:03 kernel: SMBIOS 2.7 present.
    09:50:03 kernel: DMI: ASUSTeK COMPUTER INC. N56VZ/N56VZ, BIOS N56VZ.217 05/22/2013
    09:50:03 kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    09:50:03 kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    09:50:03 kernel: AGP: No AGP bridge found
    09:50:03 kernel: e820: last_pfn = 0x22f200 max_arch_pfn = 0x400000000
    09:50:03 kernel: MTRR default type: uncachable
    09:50:03 kernel: MTRR fixed ranges enabled:
    09:50:03 kernel: 00000-9FFFF write-back
    09:50:03 kernel: A0000-BFFFF uncachable
    09:50:03 kernel: C0000-CFFFF write-protect
    09:50:03 kernel: D0000-DFFFF uncachable
    09:50:03 kernel: E0000-FFFFF write-protect
    09:50:03 kernel: MTRR variable ranges enabled:
    09:50:03 kernel: 0 base 000000000 mask E00000000 write-back
    09:50:03 kernel: 1 base 200000000 mask FE0000000 write-back
    09:50:03 kernel: 2 base 220000000 mask FF0000000 write-back
    09:50:03 kernel: 3 base 0E0000000 mask FE0000000 uncachable
    09:50:03 kernel: 4 base 0D0000000 mask FF0000000 uncachable
    09:50:03 kernel: 5 base 0CC000000 mask FFC000000 uncachable
    09:50:03 kernel: 6 base 0CBC00000 mask FFFC00000 uncachable
    09:50:03 kernel: 7 base 22F800000 mask FFF800000 uncachable
    09:50:03 kernel: 8 base 22F400000 mask FFFC00000 uncachable
    09:50:03 kernel: 9 base 22F200000 mask FFFE00000 uncachable
    09:50:03 kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    09:50:03 kernel: e820: update [mem 0xcbc00000-0xffffffff] usable ==> reserved
    09:50:03 kernel: e820: last_pfn = 0xcb000 max_arch_pfn = 0x400000000
    09:50:03 kernel: found SMP MP-table at [mem 0x000fd810-0x000fd81f] mapped at [ffff8800000fd810]
    09:50:03 kernel: Scanning 1 areas for low memory corruption
    09:50:03 kernel: Base memory trampoline at [ffff880000097000] 97000 size 24576
    09:50:03 kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
    09:50:03 kernel: [mem 0x00000000-0x000fffff] page 4k
    09:50:03 kernel: BRK [0x02b2f000, 0x02b2ffff] PGTABLE
    09:50:03 kernel: BRK [0x02b30000, 0x02b30fff] PGTABLE
    09:50:03 kernel: BRK [0x02b31000, 0x02b31fff] PGTABLE
    09:50:03 kernel: init_memory_mapping: [mem 0x22f000000-0x22f1fffff]
    09:50:03 kernel: [mem 0x22f000000-0x22f1fffff] page 2M
    09:50:03 kernel: BRK [0x02b32000, 0x02b32fff] PGTABLE
    09:50:03 kernel: init_memory_mapping: [mem 0x22c000000-0x22effffff]
    09:50:03 kernel: [mem 0x22c000000-0x22effffff] page 2M
    09:50:03 kernel: init_memory_mapping: [mem 0x200000000-0x22bffffff]
    09:50:03 kernel: [mem 0x200000000-0x22bffffff] page 2M
    09:50:03 kernel: init_memory_mapping: [mem 0x00100000-0x1fffffff]
    09:50:03 kernel: [mem 0x00100000-0x001fffff] page 4k
    09:50:03 kernel: [mem 0x00200000-0x1fffffff] page 2M
    09:50:03 kernel: init_memory_mapping: [mem 0x20200000-0x40003fff]
    09:50:03 kernel: [mem 0x20200000-0x3fffffff] page 2M
    09:50:03 kernel: [mem 0x40000000-0x40003fff] page 4k
    09:50:03 kernel: BRK [0x02b33000, 0x02b33fff] PGTABLE
    09:50:03 kernel: BRK [0x02b34000, 0x02b34fff] PGTABLE
    09:50:03 kernel: init_memory_mapping: [mem 0x40005000-0xc9747fff]
    09:50:03 kernel: [mem 0x40005000-0x401fffff] page 4k
    09:50:03 kernel: [mem 0x40200000-0xc95fffff] page 2M
    09:50:03 kernel: [mem 0xc9600000-0xc9747fff] page 4k
    09:50:03 kernel: init_memory_mapping: [mem 0xc9d4c000-0xc9d61fff]
    09:50:03 kernel: [mem 0xc9d4c000-0xc9d61fff] page 4k
    09:50:03 kernel: init_memory_mapping: [mem 0xc9d68000-0xc9d69fff]
    09:50:03 kernel: [mem 0xc9d68000-0xc9d69fff] page 4k
    09:50:03 kernel: init_memory_mapping: [mem 0xc9d74000-0xc9f07fff]
    09:50:03 kernel: [mem 0xc9d74000-0xc9f07fff] page 4k
    09:50:03 kernel: init_memory_mapping: [mem 0xc9f0c000-0xc9f54fff]
    09:50:03 kernel: [mem 0xc9f0c000-0xc9f54fff] page 4k
    09:50:03 kernel: init_memory_mapping: [mem 0xc9f7b000-0xc9f7dfff]
    09:50:03 kernel: [mem 0xc9f7b000-0xc9f7dfff] page 4k
    09:50:03 kernel: init_memory_mapping: [mem 0xc9f80000-0xc9f96fff]
    09:50:03 kernel: [mem 0xc9f80000-0xc9f96fff] page 4k
    09:50:03 kernel: init_memory_mapping: [mem 0xc9f9d000-0xc9fa4fff]
    09:50:03 kernel: [mem 0xc9f9d000-0xc9fa4fff] page 4k
    09:50:03 kernel: init_memory_mapping: [mem 0xc9fa6000-0xc9fb4fff]
    09:50:03 kernel: [mem 0xc9fa6000-0xc9fb4fff] page 4k
    09:50:03 kernel: init_memory_mapping: [mem 0xc9fb6000-0xc9fc0fff]
    09:50:03 kernel: [mem 0xc9fb6000-0xc9fc0fff] page 4k
    09:50:03 kernel: init_memory_mapping: [mem 0xc9fc6000-0xc9ff1fff]
    09:50:03 kernel: [mem 0xc9fc6000-0xc9ff1fff] page 4k
    09:50:03 kernel: init_memory_mapping: [mem 0xc9ff3000-0xca002fff]
    09:50:03 kernel: [mem 0xc9ff3000-0xca002fff] page 4k
    09:50:03 kernel: init_memory_mapping: [mem 0xca02a000-0xca03cfff]
    09:50:03 kernel: [mem 0xca02a000-0xca03cfff] page 4k
    09:50:03 kernel: init_memory_mapping: [mem 0xca03e000-0xca03efff]
    09:50:03 kernel: [mem 0xca03e000-0xca03efff] page 4k
    09:50:03 kernel: init_memory_mapping: [mem 0xca041000-0xca041fff]
    09:50:03 kernel: [mem 0xca041000-0xca041fff] page 4k
    09:50:03 kernel: init_memory_mapping: [mem 0xca047000-0xca05dfff]
    09:50:03 kernel: [mem 0xca047000-0xca05dfff] page 4k
    09:50:03 kernel: init_memory_mapping: [mem 0xca887000-0xca887fff]
    09:50:03 kernel: [mem 0xca887000-0xca887fff] page 4k
    09:50:03 kernel: init_memory_mapping: [mem 0xca8cb000-0xcacd7fff]
    09:50:03 kernel: [mem 0xca8cb000-0xca9fffff] page 4k
    09:50:03 kernel: [mem 0xcaa00000-0xcabfffff] page 2M
    09:50:03 kernel: [mem 0xcac00000-0xcacd7fff] page 4k
    09:50:03 kernel: init_memory_mapping: [mem 0xcaff4000-0xcaffffff]
    09:50:03 kernel: [mem 0xcaff4000-0xcaffffff] page 4k
    09:50:03 kernel: init_memory_mapping: [mem 0x100000000-0x1ffffffff]
    09:50:03 kernel: [mem 0x100000000-0x1ffffffff] page 2M
    09:50:03 kernel: RAMDISK: [mem 0x7fb8e000-0x7fffffff]
    09:50:03 kernel: ACPI: Early table checksum verification disabled
    09:50:03 kernel: ACPI: RSDP 0x00000000CA852000 000024 (v02 _ASUS_)
    09:50:03 kernel: ACPI: XSDT 0x00000000CA852080 00007C (v01 _ASUS_ Notebook 01072009 AMI 00010013)
    09:50:03 kernel: ACPI: FACP 0x00000000CA865DF0 00010C (v05 _ASUS_ Notebook 01072009 AMI 00010013)
    09:50:03 kernel: ACPI: DSDT 0x00000000CA852190 013C5A (v02 _ASUS_ Notebook 00000013 INTL 20091112)
    09:50:03 kernel: ACPI: FACS 0x00000000CA87F080 000040
    09:50:03 kernel: ACPI: APIC 0x00000000CA865F00 000092 (v03 _ASUS_ Notebook 01072009 AMI 00010013)
    09:50:03 kernel: ACPI: FPDT 0x00000000CA865F98 000044 (v01 _ASUS_ Notebook 01072009 AMI 00010013)
    09:50:03 kernel: ACPI: ECDT 0x00000000CA865FE0 0000C1 (v01 _ASUS_ Notebook 01072009 AMI. 00000005)
    09:50:03 kernel: ACPI: MCFG 0x00000000CA8660A8 00003C (v01 _ASUS_ Notebook 01072009 MSFT 00000097)
    09:50:03 kernel: ACPI: SLIC 0x00000000CA8660E8 000176 (v01 _ASUS_ Notebook 01072009 ASUS 00000001)
    09:50:03 kernel: ACPI: HPET 0x00000000CA866260 000038 (v01 _ASUS_ Notebook 01072009 AMI. 00000005)
    09:50:03 kernel: ACPI: SSDT 0x00000000CA866298 000632 (v01 AhciR1 AhciTab1 00001000 INTL 20091112)
    09:50:03 kernel: ACPI: SSDT 0x00000000CA8668D0 00049E (v01 AhciR2 AhciTab2 00001000 INTL 20091112)
    09:50:03 kernel: ACPI: SSDT 0x00000000CA866D70 00090A (v01 PmRef Cpu0Ist 00003000 INTL 20051117)
    09:50:03 kernel: ACPI: SSDT 0x00000000CA867680 000B18 (v01 PmRef CpuPm 00003000 INTL 20051117)
    09:50:03 kernel: ACPI: Local APIC address 0xfee00000
    09:50:03 kernel: No NUMA configuration found
    09:50:03 kernel: Faking a node at [mem 0x0000000000000000-0x000000022f1fffff]
    09:50:03 kernel: Initmem setup node 0 [mem 0x00000000-0x22f1fffff]
    09:50:03 kernel: NODE_DATA [mem 0x22f1ef000-0x22f1f2fff]
    09:50:03 kernel: [ffffea0000000000-ffffea0008bfffff] PMD -> [ffff880226800000-ffff88022e7fffff] on node 0
    09:50:03 kernel: Zone ranges:
    09:50:03 kernel: DMA [mem 0x00001000-0x00ffffff]
    09:50:03 kernel: DMA32 [mem 0x01000000-0xffffffff]
    09:50:03 kernel: Normal [mem 0x100000000-0x22f1fffff]
    09:50:03 kernel: Movable zone start for each node
    09:50:03 kernel: Early memory node ranges
    09:50:03 kernel: node 0: [mem 0x00001000-0x0009efff]
    09:50:03 kernel: node 0: [mem 0x00100000-0x1fffffff]
    09:50:03 kernel: node 0: [mem 0x20200000-0x40003fff]
    09:50:03 kernel: node 0: [mem 0x40005000-0xc9747fff]
    09:50:03 kernel: node 0: [mem 0xc9d4c000-0xc9d61fff]
    09:50:03 kernel: node 0: [mem 0xc9d68000-0xc9d69fff]
    09:50:03 kernel: node 0: [mem 0xc9d74000-0xc9f07fff]
    09:50:03 kernel: node 0: [mem 0xc9f0c000-0xc9f54fff]
    09:50:03 kernel: node 0: [mem 0xc9f7b000-0xc9f7dfff]
    09:50:03 kernel: node 0: [mem 0xc9f80000-0xc9f96fff]
    09:50:03 kernel: node 0: [mem 0xc9f9d000-0xc9fa4fff]
    09:50:03 kernel: node 0: [mem 0xc9fa6000-0xc9fb4fff]
    09:50:03 kernel: node 0: [mem 0xc9fb6000-0xc9fc0fff]
    09:50:03 kernel: node 0: [mem 0xc9fc6000-0xc9ff1fff]
    09:50:03 kernel: node 0: [mem 0xc9ff3000-0xca002fff]
    09:50:03 kernel: node 0: [mem 0xca02a000-0xca03cfff]
    09:50:03 kernel: node 0: [mem 0xca03e000-0xca03efff]
    09:50:03 kernel: node 0: [mem 0xca041000-0xca041fff]
    09:50:03 kernel: node 0: [mem 0xca047000-0xca05dfff]
    09:50:03 kernel: node 0: [mem 0xca887000-0xca887fff]
    09:50:03 kernel: node 0: [mem 0xca8cb000-0xcacd7fff]
    09:50:03 kernel: node 0: [mem 0xcaff4000-0xcaffffff]
    09:50:03 kernel: node 0: [mem 0x100000000-0x22f1fffff]
    09:50:03 kernel: On node 0 totalpages: 2067864
    09:50:03 kernel: DMA zone: 64 pages used for memmap
    09:50:03 kernel: DMA zone: 25 pages reserved
    09:50:03 kernel: DMA zone: 3998 pages, LIFO batch:0
    09:50:03 kernel: DMA32 zone: 12848 pages used for memmap
    09:50:03 kernel: DMA32 zone: 822266 pages, LIFO batch:31
    09:50:03 kernel: Normal zone: 19400 pages used for memmap
    09:50:03 kernel: Normal zone: 1241600 pages, LIFO batch:31
    09:50:03 kernel: Reserving Intel graphics stolen memory at 0xcbe00000-0xcfdfffff
    09:50:03 kernel: ACPI: PM-Timer IO Port: 0x408
    09:50:03 kernel: ACPI: Local APIC address 0xfee00000
    09:50:03 kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    09:50:03 kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
    09:50:03 kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
    09:50:03 kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
    09:50:03 kernel: ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled)
    09:50:03 kernel: ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled)
    09:50:03 kernel: ACPI: LAPIC (acpi_id[0x07] lapic_id[0x05] enabled)
    09:50:03 kernel: ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled)
    09:50:03 kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
    09:50:03 kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
    09:50:03 kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
    09:50:03 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    09:50:03 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    09:50:03 kernel: ACPI: IRQ0 used by override.
    09:50:03 kernel: ACPI: IRQ9 used by override.
    09:50:03 kernel: Using ACPI (MADT) for SMP configuration information
    09:50:03 kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000
    09:50:03 kernel: smpboot: Allowing 8 CPUs, 0 hotplug CPUs
    09:50:03 kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000fffff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0x20000000-0x201fffff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0x40004000-0x40004fff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xbe706000-0xbe706fff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xbe712000-0xbe712fff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xbe713000-0xbe713fff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xbe729000-0xbe729fff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xbe744000-0xbe744fff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xbe754000-0xbe754fff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xc9748000-0xc9d48fff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xc9d49000-0xc9d4bfff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xc9d62000-0xc9d67fff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xc9d6a000-0xc9d73fff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xc9f08000-0xc9f0bfff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xc9f55000-0xc9f7afff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xc9f7e000-0xc9f7ffff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xc9f97000-0xc9f9cfff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xc9fa5000-0xc9fa5fff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xc9fb5000-0xc9fb5fff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xc9fc1000-0xc9fc5fff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xc9ff2000-0xc9ff2fff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xca003000-0xca029fff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xca03d000-0xca03dfff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xca03f000-0xca040fff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xca042000-0xca046fff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xca05e000-0xca601fff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xca602000-0xca881fff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xca882000-0xca886fff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xca888000-0xca8cafff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xcacd8000-0xcaff3fff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xcb000000-0xcbbfffff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xcbc00000-0xcfdfffff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xcfe00000-0xf7ffffff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
    09:50:03 kernel: PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
    09:50:03 kernel: e820: [mem 0xcfe00000-0xf7ffffff] available for PCI devices
    09:50:03 kernel: Booting paravirtualized kernel on bare hardware
    09:50:03 kernel: setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:8 nr_node_ids:1
    09:50:03 kernel: PERCPU: Embedded 29 pages/cpu @ffff88022ee00000 s86848 r8192 d23744 u262144
    09:50:03 kernel: pcpu-alloc: s86848 r8192 d23744 u262144 alloc=1*2097152
    09:50:03 kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7
    09:50:03 kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 2035527
    09:50:03 kernel: Policy zone: Normal
    09:50:03 kernel: Kernel command line: initrd=\intel-ucode.img initrd=\initramfs-linux.img rw root=PARTUUID=8919781b-f582-49ff-9a79-d252bc62775c rcutree.rcu_idle_gp_delay=1 quiet resume=/dev/disk/by-partuuid/563ee90f-7f47-4c44-93ed-23c8278957f5
    09:50:03 kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
    09:50:03 kernel: xsave: enabled xstate_bv 0x7, cntxt size 0x340 using standard form
    09:50:03 kernel: AGP: Checking aperture...
    09:50:03 kernel: AGP: No AGP bridge found
    09:50:03 kernel: Calgary: detecting Calgary via BIOS EBDA area
    09:50:03 kernel: Calgary: Unable to locate Rio Grande table in EBDA - bailing!
    09:50:03 kernel: Memory: 7876432K/8271456K available (5381K kernel code, 909K rwdata, 1712K rodata, 1140K init, 1176K bss, 395024K reserved)
    09:50:03 kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
    09:50:03 kernel: Preemptible hierarchical RCU implementation.
    09:50:03 kernel: RCU dyntick-idle grace-period acceleration is enabled.
    09:50:03 kernel: Dump stacks of tasks blocking RCU-preempt GP.
    09:50:03 kernel: RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=8.
    09:50:03 kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
    09:50:03 kernel: NR_IRQS:8448 nr_irqs:488 0
    09:50:03 kernel: Console: colour dummy device 80x25
    09:50:03 kernel: console [tty0] enabled
    09:50:03 kernel: allocated 33554432 bytes of page_cgroup
    09:50:03 kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
    09:50:03 kernel: hpet clockevent registered
    09:50:03 kernel: tsc: Fast TSC calibration using PIT
    09:50:03 kernel: tsc: Detected 2294.820 MHz processor
    09:50:03 kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 4591.87 BogoMIPS (lpj=7649400)
    09:50:03 kernel: pid_max: default: 32768 minimum: 301
    09:50:03 kernel: ACPI: Core revision 20140724
    09:50:03 kernel: ACPI: All ACPI Tables successfully acquired
    09:50:03 kernel: Security Framework initialized
    09:50:03 kernel: Yama: becoming mindful.
    09:50:03 kernel: Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
    09:50:03 kernel: Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
    09:50:03 kernel: Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
    09:50:03 kernel: Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
    09:50:03 kernel: Initializing cgroup subsys memory
    09:50:03 kernel: Initializing cgroup subsys devices
    09:50:03 kernel: Initializing cgroup subsys freezer
    09:50:03 kernel: Initializing cgroup subsys net_cls
    09:50:03 kernel: Initializing cgroup subsys blkio
    09:50:03 kernel: CPU: Physical Processor ID: 0
    09:50:03 kernel: CPU: Processor Core ID: 0
    09:50:03 kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
    ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
    09:50:03 kernel: mce: CPU supports 9 MCE banks
    09:50:03 kernel: CPU0: Thermal monitoring enabled (TM1)
    09:50:03 kernel: Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
    Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
    09:50:03 kernel: Freeing SMP alternatives memory: 20K (ffffffff81a02000 - ffffffff81a07000)
    09:50:03 kernel: ftrace: allocating 20674 entries in 81 pages
    09:50:03 kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    09:50:03 kernel: smpboot: CPU0: Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz (fam: 06, model: 3a, stepping: 09)
    09:50:03 kernel: TSC deadline timer enabled
    09:50:03 kernel: Performance Events: PEBS fmt1+, 16-deep LBR, IvyBridge events, full-width counters, Intel PMU driver.
    09:50:03 kernel: ... version: 3
    09:50:03 kernel: ... bit width: 48
    09:50:03 kernel: ... generic registers: 4
    09:50:03 kernel: ... value mask: 0000ffffffffffff
    09:50:03 kernel: ... max period: 0000ffffffffffff
    09:50:03 kernel: ... fixed-purpose events: 3
    09:50:03 kernel: ... event mask: 000000070000000f
    09:50:03 kernel: x86: Booting SMP configuration:
    09:50:03 kernel: .... node #0, CPUs: #1
    09:50:03 kernel: CPU1 microcode updated early to revision 0x1b, date = 2014-05-29
    09:50:03 kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    09:50:03 kernel: #2
    09:50:03 kernel: CPU2 microcode updated early to revision 0x1b, date = 2014-05-29
    09:50:03 kernel: #3
    09:50:03 kernel: CPU3 microcode updated early to revision 0x1b, date = 2014-05-29
    09:50:03 kernel: #4 #5 #6 #7
    09:50:03 kernel: x86: Booted up 1 node, 8 CPUs
    09:50:03 kernel: smpboot: Total of 8 processors activated (36731.00 BogoMIPS)
    09:50:03 kernel: devtmpfs: initialized
    09:50:03 kernel: PM: Registering ACPI NVS region [mem 0xc9748000-0xc9d48fff] (6295552 bytes)
    09:50:03 kernel: PM: Registering ACPI NVS region [mem 0xca602000-0xca881fff] (2621440 bytes)
    09:50:03 kernel: PM: Registering ACPI NVS region [mem 0xca888000-0xca8cafff] (274432 bytes)
    09:50:03 kernel: pinctrl core: initialized pinctrl subsystem
    09:50:03 kernel: RTC time: 7:50:00, date: 10/23/14
    09:50:03 kernel: NET: Registered protocol family 16
    09:50:03 kernel: cpuidle: using governor ladder
    09:50:03 kernel: cpuidle: using governor menu
    09:50:03 kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
    09:50:03 kernel: ACPI: bus type PCI registered
    09:50:03 kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
    09:50:03 kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
    09:50:03 kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
    09:50:03 kernel: PCI: Using configuration type 1 for base access
    09:50:03 kernel: ACPI: Added _OSI(Module Device)
    09:50:03 kernel: ACPI: Added _OSI(Processor Device)
    09:50:03 kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
    09:50:03 kernel: ACPI: Added _OSI(Processor Aggregator Device)
    09:50:03 kernel: ACPI : EC: EC description table is found, configuring boot EC
    09:50:03 kernel: ACPI: Executed 1 blocks of module-level executable AML code
    09:50:03 kernel: [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
    09:50:03 kernel: ACPI: Dynamic OEM Table Load:
    09:50:03 kernel: ACPI: SSDT 0xFFFF8802232EA000 000853 (v01 PmRef Cpu0Cst 00003001 INTL 20051117)
    09:50:03 kernel: ACPI: Dynamic OEM Table Load:
    09:50:03 kernel: ACPI: SSDT 0xFFFF880223283800 000303 (v01 PmRef ApIst 00003000 INTL 20051117)
    09:50:03 kernel: ACPI: Dynamic OEM Table Load:
    09:50:03 kernel: ACPI: SSDT 0xFFFF8802232D5600 000119 (v01 PmRef ApCst 00003000 INTL 20051117)
    09:50:03 kernel: ACPI: Interpreter enabled
    09:50:03 kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20140724/hwxface-580)
    09:50:03 kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20140724/hwxface-580)
    09:50:03 kernel: ACPI: (supports S0 S3 S4 S5)
    09:50:03 kernel: ACPI: Using IOAPIC for interrupt routing
    09:50:03 kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    09:50:03 kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
    09:50:03 kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
    09:50:03 kernel: acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug PME]
    09:50:03 kernel: acpi PNP0A08:00: _OSC: OS now controls [AER PCIeCapability]
    09:50:03 kernel: PCI host bridge to bus 0000:00
    09:50:03 kernel: pci_bus 0000:00: root bus resource [bus 00-3e]
    09:50:03 kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
    09:50:03 kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    09:50:03 kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    09:50:03 kernel: pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff]
    09:50:03 kernel: pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff]
    09:50:03 kernel: pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff]
    09:50:03 kernel: pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff]
    09:50:03 kernel: pci_bus 0000:00: root bus resource [mem 0xcfe00000-0xfeafffff]
    09:50:03 kernel: pci 0000:00:00.0: [8086:0154] type 00 class 0x060000
    09:50:03 kernel: pci 0000:00:01.0: [8086:0151] type 01 class 0x060400
    09:50:03 kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
    09:50:03 kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
    09:50:03 kernel: pci 0000:00:02.0: [8086:0166] type 00 class 0x030000
    09:50:03 kernel: pci 0000:00:02.0: reg 0x10: [mem 0xf7400000-0xf77fffff 64bit]
    09:50:03 kernel: pci 0000:00:02.0: reg 0x18: [mem 0xd0000000-0xdfffffff 64bit pref]
    09:50:03 kernel: pci 0000:00:02.0: reg 0x20: [io 0xf000-0xf03f]
    09:50:03 kernel: pci 0000:00:14.0: [8086:1e31] type 00 class 0x0c0330
    09:50:03 kernel: pci 0000:00:14.0: reg 0x10: [mem 0xf7a00000-0xf7a0ffff 64bit]
    09:50:03 kernel: pci 0000:00:14.0: PME# supported from D3hot D3cold
    09:50:03 kernel: pci 0000:00:14.0: System wakeup disabled by ACPI
    09:50:03 kernel: pci 0000:00:16.0: [8086:1e3a] type 00 class 0x078000
    09:50:03 kernel: pci 0000:00:16.0: reg 0x10: [mem 0xf7a1a000-0xf7a1a00f 64bit]
    09:50:03 kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
    09:50:03 kernel: pci 0000:00:1a.0: [8086:1e2d] type 00 class 0x0c0320
    09:50:03 kernel: pci 0000:00:1a.0: reg 0x10: [mem 0xf7a18000-0xf7a183ff]
    09:50:03 kernel: pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
    09:50:03 kernel: pci 0000:00:1a.0: System wakeup disabled by ACPI
    09:50:03 kernel: pci 0000:00:1b.0: [8086:1e20] type 00 class 0x040300
    09:50:03 kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xf7a10000-0xf7a13fff 64bit]
    09:50:03 kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    09:50:03 kernel: pci 0000:00:1b.0: System wakeup disabled by ACPI
    09:50:03 kernel: pci 0000:00:1c.0: [8086:1e10] type 01 class 0x060400
    09:50:03 kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    09:50:03 kernel: pci 0000:00:1c.1: [8086:1e12] type 01 class 0x060400
    09:50:03 kernel: pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
    09:50:03 kernel: pci 0000:00:1c.3: [8086:1e16] type 01 class 0x060400
    09:50:03 kernel: pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
    09:50:03 kernel: pci 0000:00:1c.3: System wakeup disabled by ACPI
    09:50:03 kernel: pci 0000:00:1d.0: [8086:1e26] type 00 class 0x0c0320
    09:50:03 kernel: pci 0000:00:1d.0: reg 0x10: [mem 0xf7a17000-0xf7a173ff]
    09:50:03 kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
    09:50:03 kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
    09:50:03 kernel: pci 0000:00:1f.0: [8086:1e59] type 00 class 0x060100
    09:50:03 kernel: pci 0000:00:1f.2: [8086:1e03] type 00 class 0x010601
    09:50:03 kernel: pci 0000:00:1f.2: reg 0x10: [io 0xf0b0-0xf0b7]
    09:50:03 kernel: pci 0000:00:1f.2: reg 0x14: [io 0xf0a0-0xf0a3]
    09:50:03 kernel: pci 0000:00:1f.2: reg 0x18: [io 0xf090-0xf097]
    09:50:03 kernel: pci 0000:00:1f.2: reg 0x1c: [io 0xf080-0xf083]
    09:50:03 kernel: pci 0000:00:1f.2: reg 0x20: [io 0xf060-0xf07f]
    09:50:03 kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xf7a16000-0xf7a167ff]
    09:50:03 kernel: pci 0000:00:1f.2: PME# supported from D3hot
    09:50:03 kernel: pci 0000:00:1f.3: [8086:1e22] type 00 class 0x0c0500
    09:50:03 kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xf7a15000-0xf7a150ff 64bit]
    09:50:03 kernel: pci 0000:00:1f.3: reg 0x20: [io 0xf040-0xf05f]
    09:50:03 kernel: pci 0000:01:00.0: [10de:0fd1] type 00 class 0x030000
    09:50:03 kernel: pci 0000:01:00.0: reg 0x10: [mem 0xf6000000-0xf6ffffff]
    09:50:03 kernel: pci 0000:01:00.0: reg 0x14: [mem 0xe0000000-0xefffffff 64bit pref]
    09:50:03 kernel: pci 0000:01:00.0: reg 0x1c: [mem 0xf0000000-0xf1ffffff 64bit pref]
    09:50:03 kernel: pci 0000:01:00.0: reg 0x24: [io 0xe000-0xe07f]
    09:50:03 kernel: pci 0000:01:00.0: reg 0x30: [mem 0xf7000000-0xf707ffff pref]
    09:50:03 kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
    09:50:03 kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
    09:50:03 kernel: pci 0000:00:01.0: bridge window [mem 0xf6000000-0xf70fffff]
    09:50:03 kernel: pci 0000:00:01.0: bridge window [mem 0xe0000000-0xf1ffffff 64bit pref]
    09:50:03 kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
    09:50:03 kernel: pci 0000:03:00.0: [168c:0032] type 00 class 0x028000
    09:50:03 kernel: pci 0000:03:00.0: reg 0x10: [mem 0xf7900000-0xf797ffff 64bit]
    09:50:03 kernel: pci 0000:03:00.0: reg 0x30: [mem 0xf7980000-0xf798ffff pref]
    09:50:03 kernel: pci 0000:03:00.0: supports D1 D2
    09:50:03 kernel: pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    09:50:03 kernel: pci 0000:03:00.0: System wakeup disabled by ACPI
    09:50:03 kernel: pci 0000:00:1c.1: PCI bridge to [bus 03]
    09:50:03 kernel: pci 0000:00:1c.1: bridge window [mem 0xf7900000-0xf79fffff]
    09:50:03 kernel: pci 0000:04:00.0: [1969:1091] type 00 class 0x020000
    09:50:03 kernel: pci 0000:04:00.0: reg 0x10: [mem 0xf7800000-0xf783ffff 64bit]
    09:50:03 kernel: pci 0000:04:00.0: reg 0x18: [io 0xd000-0xd07f]
    09:50:03 kernel: pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    09:50:03 kernel: pci 0000:04:00.0: System wakeup disabled by ACPI
    09:50:03 kernel: pci 0000:00:1c.3: PCI bridge to [bus 04]
    09:50:03 kernel: pci 0000:00:1c.3: bridge window [io 0xd000-0xdfff]
    09:50:03 kernel: pci 0000:00:1c.3: bridge window [mem 0xf7800000-0xf78fffff]
    09:50:03 kernel: acpi PNP0A08:00: Disabling ASPM (FADT indicates it is unsupported)
    09:50:03 kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12)
    09:50:03 kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 12)
    09:50:03 kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *10 12)
    09:50:03 kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 10 12)
    09:50:03 kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 12) *0, disabled.
    09:50:03 kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 12) *0, disabled.
    09:50:03 kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs *3 4 5 6 7 10 12)
    09:50:03 kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 *4 5 6 7 10 12)
    09:50:03 kernel: ACPI: Enabled 4 GPEs in block 00 to 3F
    09:50:03 kernel: ACPI : EC: GPE = 0x19, I/O: command/status = 0x66, data = 0x62
    09:50:03 kernel: vgaarb: setting as boot device: PCI:0000:00:02.0
    09:50:03 kernel: vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
    09:50:03 kernel: vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=none,locks=none
    09:50:03 kernel: vgaarb: loaded
    09:50:03 kernel: vgaarb: bridge control possible 0000:01:00.0
    09:50:03 kernel: vgaarb: no bridge control possible 0000:00:02.0
    09:50:03 kernel: PCI: Using ACPI for IRQ routing
    09:50:03 kernel: PCI: pci_cache_line_size set to 64 bytes
    09:50:03 kernel: e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
    09:50:03 kernel: e820: reserve RAM buffer [mem 0x40004000-0x43ffffff]
    09:50:03 kernel: e820: reserve RAM buffer [mem 0xbe706018-0xbfffffff]
    09:50:03 kernel: e820: reserve RAM buffer [mem 0xbe713018-0xbfffffff]
    09:50:03 kernel: e820: reserve RAM buffer [mem 0xbe744018-0xbfffffff]
    09:50:03 kernel: e820: reserve RAM buffer [mem 0xc9748000-0xcbffffff]
    09:50:03 kernel: e820: reserve RAM buffer [mem 0xc9d62000-0xcbffffff]
    09:50:03 kernel: e820: reserve RAM buffer [mem 0xc9d6a000-0xcbffffff]
    09:50:03 kernel: e820: reserve RAM buffer [mem 0xc9f08000-0xcbffffff]
    09:50:03 kernel: e820: reserve RAM buffer [mem 0xc9f55000-0xcbffffff]
    09:50:03 kernel: e820: reserve RAM buffer [mem 0xc9f7e000-0xcbffffff]
    09:50:03 kernel: e820: reserve RAM buffer [mem 0xc9f97000-0xcbffffff]
    09:50:03 kernel: e820: reserve RAM buffer [mem 0xc9fa5000-0xcbffffff]
    09:50:03 kernel: e820: reserve RAM buffer [mem 0xc9fb5000-0xcbffffff]
    09:50:03 kernel: e820: reserve RAM buffer [mem 0xc9fc1000-0xcbffffff]
    09:50:03 kernel: e820: reserve RAM buffer [mem 0xc9ff2000-0xcbffffff]
    09:50:03 kernel: e820: reserve RAM buffer [mem 0xca003000-0xcbffffff]
    09:50:03 kernel: e820: reserve RAM buffer [mem 0xca03d000-0xcbffffff]
    09:50:03 kernel: e820: reserve RAM buffer [mem 0xca03f000-0xcbffffff]
    09:50:03 kernel: e820: reserve RAM buffer [mem 0xca042000-0xcbffffff]
    09:50:03 kernel: e820: reserve RAM buffer [mem 0xca05e000-0xcbffffff]
    09:50:03 kernel: e820: reserve RAM buffer [mem 0xca888000-0xcbffffff]
    09:50:03 kernel: e820: reserve RAM buffer [mem 0xcacd8000-0xcbffffff]
    09:50:03 kernel: e820: reserve RAM buffer [mem 0xcb000000-0xcbffffff]
    09:50:03 kernel: e820: reserve RAM buffer [mem 0x22f200000-0x22fffffff]
    09:50:03 kernel: NetLabel: Initializing
    09:50:03 kernel: NetLabel: domain hash size = 128
    09:50:03 kernel: NetLabel: protocols = UNLABELED CIPSOv4
    09:50:03 kernel: NetLabel: unlabeled traffic allowed by default
    09:50:03 kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
    09:50:03 kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter
    09:50:03 kernel: Switched to clocksource hpet
    09:50:03 kernel: pnp: PnP ACPI init
    09:50:03 kernel: system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
    09:50:03 kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
    09:50:03 kernel: system 00:01: [io 0x0680-0x069f] has been reserved
    09:50:03 kernel: system 00:01: [io 0x1000-0x100f] has been reserved
    09:50:03 kernel: system 00:01: [io 0xffff] has been reserved
    09:50:03 kernel: system 00:01: [io 0xffff] has been reserved
    09:50:03 kernel: system 00:01: [io 0x0400-0x0453] could not be reserved
    09:50:03 kernel: system 00:01: [io 0x0458-0x047f] has been reserved
    09:50:03 kernel: system 00:01: [io 0x0500-0x057f] has been reserved
    09:50:03 kernel: system 00:01: [io 0x164e-0x164f] has been reserved
    09:50:03 kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
    09:50:03 kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
    09:50:03 kernel: system 00:03: [io 0x0454-0x0457] has been reserved
    09:50:03 kernel: system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
    09:50:03 kernel: system 00:04: [io 0x04d0-0x04d1] has been reserved
    09:50:03 kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
    09:50:03 kernel: pnp 00:05: Plug and Play ACPI device, IDs ETD0108 SYN0a00 SYN0002 PNP0f03 PNP0f13 PNP0f12 (active)
    09:50:03 kernel: pnp 00:06: Plug and Play ACPI device, IDs ATK3001 PNP030b (active)
    09:50:03 kernel: system 00:07: [mem 0xfed1c000-0xfed1ffff] has been reserved
    09:50:03 kernel: system 00:07: [mem 0xfed10000-0xfed17fff] has been reserved
    09:50:03 kernel: system 00:07: [mem 0xfed18000-0xfed18fff] has been reserved
    09:50:03 kernel: system 00:07: [mem 0xfed19000-0xfed19fff] has been reserved
    09:50:03 kernel: system 00:07: [mem 0xf8000000-0xfbffffff] has been reserved
    09:50:03 kernel: system 00:07: [mem 0xfed20000-0xfed3ffff] has been reserved
    09:50:03 kernel: system 00:07: [mem 0xfed90000-0xfed93fff] has been reserved
    09:50:03 kernel: system 00:07: [mem 0xfed45000-0xfed8ffff] has been reserved
    09:50:03 kernel: system 00:07: [mem 0xff000000-0xffffffff] has been reserved
    09:50:03 kernel: system 00:07: [mem 0xfee00000-0xfeefffff] could not be reserved
    09:50:03 kernel: system 00:07: [mem 0xcfe00000-0xcfe00fff] has been reserved
    09:50:03 kernel: system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
    09:50:03 kernel: system 00:08: [mem 0xcfe00000-0xcfe00fff] has been reserved
    09:50:03 kernel: system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
    09:50:03 kernel: system 00:09: [mem 0x20000000-0x201fffff] has been reserved
    09:50:03 kernel: system 00:09: [mem 0x40004000-0x40004fff] has been reserved
    09:50:03 kernel: system 00:09: Plug and Play ACPI device, IDs PNP0c01 (active)
    09:50:03 kernel: pnp: PnP ACPI: found 10 devices
    09:50:03 kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
    09:50:03 kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
    09:50:03 kernel: pci 0000:00:01.0: bridge window [mem 0xf6000000-0xf70fffff]
    09:50:03 kernel: pci 0000:00:01.0: bridge window [mem 0xe0000000-0xf1ffffff 64bit pref]
    09:50:03 kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
    09:50:03 kernel: pci 0000:00:1c.1: PCI bridge to [bus 03]
    09:50:03 kernel: pci 0000:00:1c.1: bridge window [mem 0xf7900000-0xf79fffff]
    09:50:03 kernel: pci 0000:00:1c.3: PCI bridge to [bus 04]
    09:50:03 kernel: pci 0000:00:1c.3: bridge window [io 0xd000-0xdfff]
    09:50:03 kernel: pci 0000:00:1c.3: bridge window [mem 0xf7800000-0xf78fffff]
    09:50:03 kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    09:50:03 kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    09:50:03 kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    09:50:03 kernel: pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000d3fff]
    09:50:03 kernel: pci_bus 0000:00: resource 8 [mem 0x000d4000-0x000d7fff]
    09:50:03 kernel: pci_bus 0000:00: resource 9 [mem 0x000d8000-0x000dbfff]
    09:50:03 kernel: pci_bus 0000:00: resource 10 [mem 0x000dc000-0x000dffff]
    09:50:03 kernel: pci_bus 0000:00: resource 11 [mem 0xcfe00000-0xfeafffff]
    09:50:03 kernel: pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
    09:50:03 kernel: pci_bus 0000:01: resource 1 [mem 0xf6000000-0xf70fffff]
    09:50:03 kernel: pci_bus 0000:01: resource 2 [mem 0xe0000000-0xf1ffffff 64bit pref]
    09:50:03 kernel: pci_bus 0000:03: resource 1 [mem 0xf7900000-0xf79fffff]
    09:50:03 kernel: pci_bus 0000:04: resource 0 [io 0xd000-0xdfff]
    09:50:03 kernel: pci_bus 0000:04: resource 1 [mem 0xf7800000-0xf78fffff]
    09:50:03 kernel: NET: Registered protocol family 2
    09:50:03 kernel: TCP established hash table entries: 65536 (order: 7, 524288 bytes)
    09:50:03 kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
    09:50:03 kernel: TCP: Hash tables configured (established 65536 bind 65536)
    09:50:03 kernel: TCP: reno registered
    09:50:03 kernel: UDP hash table entries: 4096 (order: 5, 131072 bytes)
    09:50:03 kernel: UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
    09:50:03 kernel: NET: Registered protocol family 1
    09:50:03 kernel: pci 0000:00:02.0: Video device with shadowed ROM
    09:50:03 kernel: pci 0000:04:00.0: set MSI_INTX_DISABLE_BUG flag
    09:50:03 kernel: PCI: CLS 64 bytes, default 64
    09:50:03 kernel: Unpacking initramfs...
    09:50:03 kernel: Freeing initrd memory: 4552K (ffff88007fb8e000 - ffff880080000000)
    09:50:03 kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
    09:50:03 kernel: software IO TLB [mem 0xba706000-0xbe706000] (64MB) mapped at [ffff8800ba706000-ffff8800be705fff]
    09:50:03 kernel: RAPL PMU detected, hw unit 2^-16 Joules, API unit is 2^-32 Joules, 3 fixed counters 163840 ms ovfl timer
    09:50:03 kernel: microcode: CPU0 sig=0x306a9, pf=0x10, revision=0x1b
    09:50:03 kernel: microcode: CPU1 sig=0x306a9, pf=0x10, revision=0x1b
    09:50:03 kernel: microcode: CPU2 sig=0x306a9, pf=0x10, revision=0x1b
    09:50:03 kernel: microcode: CPU3 sig=0x306a9, pf=0x10, revision=0x1b
    09:50:03 kernel: microcode: CPU4 sig=0x306a9, pf=0x10, revision=0x1b
    09:50:03 kernel: microcode: CPU5 sig=0x306a9, pf=0x10, revision=0x1b
    09:50:03 kernel: microcode: CPU6 sig=0x306a9, pf=0x10, revision=0x1b
    09:50:03 kernel: microcode: CPU7 sig=0x306a9, pf=0x10, revision=0x1b
    09:50:03 kernel: microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
    09:50:03 kernel: Scanning for low memory corruption every 60 seconds
    09:50:03 kernel: futex hash table entries: 2048 (order: 5, 131072 bytes)
    09:50:03 kernel: Initialise system trusted keyring
    09:50:03 kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
    09:50:03 kernel: zpool: loaded
    09:50:03 kernel: zbud: loaded
    09:50:03 kernel: VFS: Disk quotas dquot_6.5.2
    09:50:03 kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    09:50:03 kernel: msgmni has been set to 15744
    09:50:03 kernel: Key type big_key registered
    09:50:03 kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    09:50:03 kernel: io scheduler noop registered
    09:50:03 kernel: io scheduler deadline registered
    09:50:03 kernel: io scheduler cfq registered (default)
    09:50:03 kernel: pcieport 0000:00:01.0: irq 24 for MSI/MSI-X
    09:50:03 kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    09:50:03 kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
    09:50:03 kernel: efifb: probing for efifb
    09:50:03 kernel: efifb: framebuffer at 0xd0000000, mapped to 0xffffc90004f00000, using 3072k, total 3072k
    09:50:03 kernel: efifb: mode is 1024x768x32, linelength=4096, pages=1
    09:50:03 kernel: efifb: scrolling: redraw
    09:50:03 kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
    09:50:03 kernel: Console: switching to colour frame buffer device 128x48
    09:50:03 kernel: fb0: EFI VGA frame buffer device
    09:50:03 kernel: intel_idle: MWAIT substates: 0x21120
    09:50:03 kernel: intel_idle: v0.4 model 0x3A
    09:50:03 kernel: intel_idle: lapic_timer_reliable_states 0xffffffff
    09:50:03 kernel: GHES: HEST is not enabled!
    09:50:03 kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    09:50:03 kernel: Linux agpgart interface v0.103
    09:50:03 kernel: rtc_cmos 00:02: RTC can wake from S4
    09:50:03 kernel: rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
    09:50:03 kernel: rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
    09:50:03 kernel: Intel P-state driver initializing.
    09:50:03 kernel: ledtrig-cpu: registered to indicate activity on CPUs
    09:50:03 kernel: TCP: cubic registered
    09:50:03 kernel: NET: Registered protocol family 10
    09:50:03 kernel: NET: Registered protocol family 17
    09:50:03 kernel: Loading compiled-in X.509 certificates
    09:50:03 kernel: registered taskstats version 1
    09:50:03 kernel: Magic number: 2:282:825
    09:50:03 kernel: rtc_cmos 00:02: setting system clock to 2014-10-23 07:50:00 UTC (1414050600)
    09:50:03 kernel: PM: Checking hibernation image partition /dev/disk/by-partuuid/563ee90f-7f47-4c44-93ed-23c8278957f5
    09:50:03 kernel: PM: Hibernation image not present or could not be loaded.
    09:50:03 kernel: Freeing unused kernel memory: 1140K (ffffffff818e5000 - ffffffff81a02000)
    09:50:03 kernel: Write protecting the kernel read-only data: 8192k
    09:50:03 kernel: Freeing unused kernel memory: 752K (ffff880002544000 - ffff880002600000)
    09:50:03 kernel: Freeing unused kernel memory: 336K (ffff8800027ac000 - ffff880002800000)
    09:50:03 kernel: random: systemd-tmpfile urandom read with 2 bits of entropy available
    09:50:03 systemd-udevd[78]: starting version 216
    09:50:03 kernel: [drm] Initialized drm 1.1.0 20060810
    09:50:03 kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
    09:50:03 kernel: ACPI: Lid Switch [LID]
    09:50:03 kernel: input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
    09:50:03 kernel: ACPI: Sleep Button [SLPB]
    09:50:03 kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
    09:50:03 kernel: ACPI: Power Button [PWRF]
    09:50:03 kernel: [drm] Memory usable by graphics device = 2048M
    09:50:03 kernel: [drm] Replacing VGA console driver
    09:50:03 kernel: checking generic (d0000000 300000) vs hw (d0000000 10000000)
    09:50:03 kernel: fb: switching to inteldrmfb from EFI VGA
    09:50:03 kernel: Console: switching to colour dummy device 80x25
    09:50:03 kernel: i915 0000:00:02.0: irq 25 for MSI/MSI-X
    09:50:03 kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
    09:50:03 kernel: [drm] Driver supports precise vblank timestamp query.
    09:50:03 kernel: vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=none:owns=io+mem
    09:50:03 kernel: fbcon: inteldrmfb (fb0) is primary device
    09:50:03 kernel: [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A
    09:50:03 kernel: [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun
    09:50:03 kernel: Console: switching to colour frame buffer device 170x48
    09:50:03 kernel: i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
    09:50:03 kernel: i915 0000:00:02.0: registered panic notifier
    09:50:03 kernel: ACPI: Video Device [PEGP] (multi-head: yes rom: yes post: no)
    09:50:03 kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:02/LNXVIDEO:00/input/input3
    09:50:03 kernel: ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
    09:50:03 kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input4
    09:50:03 kernel: [drm] Initialized i915 1.6.0 20140725 for 0000:00:02.0 on minor 0
    09:50:03 kernel: bbswitch: version 0.8
    09:50:03 kernel: bbswitch: Found integrated VGA device 0000:00:02.0: \_SB_.PCI0.GFX0
    09:50:03 kernel: bbswitch: Found discrete VGA device 0000:01:00.0: \_SB_.PCI0.PEG0.PEGP
    09:50:03 kernel: ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140724/nsarguments-95)
    09:50:03 kernel: bbswitch: detected an Optimus _DSM function
    09:50:03 kernel: pci 0000:01:00.0: enabling device (0000 -> 0003)
    09:50:03 kernel: bbswitch: Succesfully loaded. Discrete card 0000:01:00.0 is on
    09:50:03 kernel: i8042: PNP: PS/2 Controller [PNP030b:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
    09:50:03 kernel: i8042: Detected active multiplexing controller, rev 1.1
    09:50:03 kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
    09:50:03 kernel: serio: i8042 AUX0 port at 0x60,0x64 irq 12
    09:50:03 kernel: serio: i8042 AUX1 port at 0x60,0x64 irq 12
    09:50:03 kernel: serio: i8042 AUX2 port at 0x60,0x64 irq 12
    09:50:03 kernel: serio: i8042 AUX3 port at 0x60,0x64 irq 12
    09:50:03 kernel: ACPI: bus type USB registered
    09:50:03 kernel: usbcore: registered new interface driver usbfs
    09:50:03 kernel: usbcore: registered new interface driver hub
    09:50:03 kernel: usbcore: registered new device driver usb
    09:50:03 kernel: SCSI subsystem initialized
    09:50:03 kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    09:50:03 kernel: ehci-pci: EHCI PCI platform driver
    09:50:03 kernel: xhci_hcd 0000:00:14.0: xHCI Host Con

    Scimmia wrote:https://bugs.archlinux.org/task/42509
    The workaround suggested solves the bootup problems but I still can't shutdown properly. now there's a message from cgroup
    cgroup : option or name mismatch, new: 0x0 "", old: 0x4 "systemd
    Found https://bbs.archlinux.org/viewtopic.php?id=174979 but no solution
    Last edited by yungtrizzle (2014-11-13 14:50:53)

  • Lync 2013 Error - Certificate could not be published in the database associated with User Services Cluster

    Hi Lync gurus,
    I have a weird issue:
    Just installed a Lync Standard 2013. 
    Everything works except I keep getting this error in Log: every 30 minute or so.
    First an Error:  Event 47067
    A server did not respond to HTTP request
    Server lyncserver.domain.local did not respond to HTTP request PublishCertRequest targeted at
    https://lyncserver.domain.local:444/LiveServer/UserPinService.
    Cause: Server might be down or the network path between servers might not be properly configured.
    Resolution:
    Please ensure that the server can be connected on the target port using telnet and then re-try.
    Then I get a Warning: Event 47068
    GetAndPublish web service failed.
    Certificate could not be published in the database associated with User Services Cluster [lyncserver.domain.local ]. Request Details - Entity: [[email protected]], Device Id: [6BB30A3E-2923-553A-8E5F-0B2FB2CEA330], Authenticated User: [sip:[email protected]].
    Additional Context: [Publish_Failure: OtherFailure;HttpNoResponse:"lyncserver.domain.local "]
    Cause: This could be due to network connectivity issues with the remote server, or because the database is down.
    Resolution:
    Please ensure that the user services is reachable and the database is up and running.
    Thanks for any help

    Please check you can telnet port 443 and port 444 on Lync Front End Serve from client.
    Try to regenerate a new certificate for Lync Front End Server.
    Check all the services on Lync Front End Server are started.
    Check the option “Enable all purposes for this certificate” is checked for the trusted root CA certificate.
    For the detailed steps:
    Run MMC--Add\Remove Snap-ins--certificates--Local Computer--Trusted Root Certificate Authorities--Certificates, find the Root CA certificate you installed--Properties--General, check the "Enable all purposes for this certificate".
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Lync front end connectivity test fails (SSL certificate / URL problem)

    We have a weird problem in our installation where Lync keeps complaining about connectivity issues to external reach proxy on our front end server.
    The event log error codes are 41024 and 41026.
    Here's the error from the snooper utility: 
    TL_ERROR(TF_COMPONENT) [0]1A14.0EE4::12/12/2014-10:31:30.901.0000000d (DataMCURunTime,DataProxies.ProcessResponse:1197.idx(601))
    (0000000001595A27)Failed poking Proxy error=[The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.], type=[ExternalReachProxy], url=[https://dunords36.du.local:4443/Reach/DataCollaborationRelayWebService.svc]
    The problem is that it makes the test with the INTERNAL FQDN (dunords36.du.local) and thus the SSL trust fails as the certificate is for our EXTERNAL FQDN on the front end server! I have verified this by testing the above URL with the external address and
    the internal one. With the external one the certificate is OK.
    If you're wondering; we do not use a reverse proxy. Instead we just have the firewall change the port and forward the traffic to our front end server. Our lync setup is a NAT'ed setup.
    I know about the security risks so this is not what the discussion is about.
    I can't find anywhere where i can change the above behaviour and tell lync to make the test on the correct, external FQDN. The settings in the topology builder all seems to be OK. And as you can see it does make the test on port 4443 which in our topology
    builder is configured for our external FQDN.

    Hi,
    Would you please elaborate your Lync Server environment (Standard Edition or Enterprise Edition)?
    Please double check if you enter the correct external base URL on Lync Topology.
    Please also check if the SAN of FE Server certificate correctly.
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Steps to create your own self signed certificate with java plugin working

    You need two tools that comes with your jdk which are keytool and jarsigner.
    Steps explain below in detail. Don't use netscape signtool, it will NEVER work!
    * keytool -genkey -keyalg rsa -alias tstkey -keypass 2br2h2m -dname "cn=Test Object Signing Certificate, o=AI Khalil, ou=Java Products, c=AU"
    cn = Certificate name
    o = organistation
    ou = organistation unit
    c = country (first two letters)
    If don't put the -dname, you can fill it line by line.
    The -keypass has to be verify at the end, and you have to wait for it to create the rsa signing keys.
    On NT by default it will put the alias information at D:\WINNT\Profiles\Administrator (if log in as administrator) with the default file called ".keystore". Windows 98 etc, don't know, search for .keystore
    file. When you update it, check for the timestamp change and you know if you at the right spot.
    You can store your alias information via the -storepass option to your current directory you work on, if you don't want to update the default .keystore file?
    The .keystore contains a list of alias so you don't have to do this process again and again.
    Another tip if you want your certificate encryption validity to be more than the default one month is simply
    add the -validity <valDays>, after the -genkey option, to make your certificate usage for encryption to last much longer.
    Note: You MUST use the -keyalg rsa because for starters the rsa encyption alogorthim is supported on ALL browsers instead of the default DSA and the other one SHA. Java plugins must work with the RSA algorthim when signing applets, else you will get all sorts of weird errors :)
    Do not use signtool because thats a browser dependant solution!! Java plugin is supposed to work via running it owns jre instead of the browser JVM. So if you going to use netscape signtool, it starts to become a mess! ie certificate will install, but applet won't start and give you funny security exception errors :)
    * keytool -export -alias tstkey -file MyTestCert.crt
    It will read the alias information in the .keystore information picking up the rsa private/public keys info and
    create your self sign certificate. You can double click this certificate to install it? But don't think this step is needed but maybe for IE? Someone else can check that part.
    If you make a mistake with the alias, simply keytool -delete -v -alias <your alias key>
    If not in default .keystore file, then simply keytool -delete -v -alias <your alias key> -keystore <your keystore filename>
    * Put your classes in your jar file, my example is tst.jar.
    * jarsigner tst.jar tstkey
    Sign your testing jar file with your alias key that supports the RSA encryption alogorthim.
    * jarsigner -verify -verbose -certs tst.jar
    Check that its been verified.
    The last step is the most tricky one. Its to do with having your own CA (Certified Authority) so you don't
    have to fork out money straight away to buy a Verisign or Twarte certificate. The CA listing as you see in
    netscape browsers under security/signers, is NOT where the plugin looks at. The plugin looks at a file called
    CACERTS. Another confusion is that the cacerts file is stored in your jre/lib/security AND also at your
    JavaSoft/Jre/<Java version>/lib/security. When you install the Java plugin for the first time in uses your
    JavaSoft folder and its the cacerts file that has to be updated you add your own CA, because thats where
    the plugin look at, NOT THE BROWSER. Everything about plugin is never to do with the browser!! :)
    * keytool -import -file MyTestCert.crt -alias tstkey -keystore "D:\Program Files\JavaSoft\JRE\1.3.1\lib\security/cacerts"
    Off course point to your own cacerts file destination.
    Password to change it, is "changeit"
    Before you do this step make a copy of it in its own directory in case you do something silly.
    This example will add a CA with alias of my key called "tstkey" and store to my example destination.
    * keytool -list -v -keystore "E:/jdk/jdk1.3/jre/lib/security/cacerts"
    List to see if another CA is added with your alias key.
    Your html, using Netscape embed and Internet explorer object tags to point to the java plugin,
    your own self sign applet certificate should work
    Cheers
    Abraham Khalil

    I follow Signed Applet in Plugin, and it's working on
    my computer. Thanks
    But When I open my applet from another computer on
    network, why it does not work ..?
    How to make this applet working at another computer
    without change the policy file ..?
    thanks in advance,
    AnomYou must install the certificate on that computers plugin. Can this be done from the web? can anyone suggest a batch file or otherwise that could do this for end users?
    I want a way for end users to accept my cert as Root or at least trust my cert so I dont have to buy one. I am not worried about my users refusing to accept my cert. just how do I make it easy for them? IE you can just click the cert from a link, but that installs for IE, and not the plugin where it needs to be.

  • DNS, Certificates, and Active Directory - School Setup Issues

    Our school has been piloting a small iPad depolyment.  I have been struggling with getting Profile Manager to work correctly since August of last year. Here's the setup:
    1. Active Directory DNS/DHCP server (set as "school.local"--yes, I know .local is bad form, but it was set before I got here). I have changed the "Digest" to "Basic" setting
    2. Mac Mini server that has its own external IP and hostname ("mac.school.org") and is also bound to the AD server for user authentication for services (Profile Manager, WebDAV, wiki, etc.). I have a self-signed SSL certificate installed under the name "mac.school.org"
    3. About 90 iPads, and a handfull of Mac desktops
    In a perfect world, users would be able to login (with their AD credentials) to the Profile Manager self-service portal using the external hostname of the mac server ("mac.school.org/mydevices"), install the Trust Profile, and enroll the device (iPad, Mac, etc).
    However, this is not the case.  The setup seems to work for awhile; quite perfectly in fact. But then for reasons unknown to me, everything just "breaks" and Profile Manager ceases to work like it should. Here are some of issues I am seeing:
    a.) DNS service on the Mac server turns itself ON randomly.  DNS should NOT be running this server, correct? All DNS lookups internally are done by the AD server. I've used changeip and everything matches (both say "mac.school.org")
    b.) Whenever we use VPN, and at other seemingly random times, the server's hostname changes from "mac.school.org" to "mac.school.local" I would make the server external only, but it needs to have an internal IP to talk to the AD server.
    c.) AD binding breaks randomly and I have to rebind the server to AD
    d.) When enrolling devices, Profile Manager starts rejecting certificates (not a trusted source, etc.) and I have to destroy OD and PM and start all over again.
    I know this is a lot and I'm not necessarily expecting anyone to answer all of these questions. I guess I'm wondering if anyone could point me in the right direction? I've looked for help with these issues all over the place, but none of the environments I read about are quite like the one I'm in.

    Yes, I am not giving the real domain name here.
    No prob. just checking, sometimes people have weird domain names never know if they are real or they expect them to be real or they put domain names owned by someone else on their internal network eek.
    Not really needed to use mac.school.org internally, that is in local LAN. The thing to understand about DNS is the scope for which a DNS zone is relevant WRT a client machine — inside LAN or on Internet, and which DNS server is authoritative for a domain. Authoritative in the sense of 'the final word'.
    Go to Network Utility on your mac, type in your real domain name (whatever you are changing to school.org to hide it) what comes back. On my server I see the below (I have replaced my real, Internet legal domain, to 'example.com')
    In my setup I have, on the LAN, setup the Mac server to be authoritative for domain 'example.com'. On the Internet however it is another external DNS server.
    So you have set DNS forwarders on the Mac machine?
    I really don't believe that the machine's hostname is changing, it is statically configured. What I believe is happening is that DNS name resolution is telling you different things at different times because you are using different DNS servers.
    On mac machine terminal type $less /etc/resolv.conf and copy paste what it says. In server app Services | DNS right side does it say you have forwarders?
    Still it is not good to have two DNS domains in your internal LAN, there is no need to have school.org on the mac DNS unless it is going to be fully setup to be authoritative in the internal LAN for the domain school.org. You can have school.org on the Internet (Internet scope of users point 1) and school.local on internal machine (LAN scope of users).
    Lookup has started…
    Trying "example.com"
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53292
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
    ;; QUESTION SECTION:
    ;example.com.                   IN        ANY
    ;; ANSWER SECTION:
    example.com.     10800          IN        SOA          example.com. admin.example.com. 2013010907 3600 900 1209600 86400
    example.com.     10800          IN         NS          server.example.com.
    example.com.     10800          IN         MX          10 server.example.com.
    ;; ADDITIONAL SECTION:
    server.example.com. 10800       IN          A          192.168.1.20
    Received 145 bytes from 127.0.0.1#53 in 2 ms

  • Partner claiming no certificate attached in SOAP call

    Having a weird situation here. Trying to send an outbound SOAP call to a 3rd party. They claim that the reason we continue to get forbidden error is because there are no certificates attached with the message. We are reaching their server so it's not a firewall issue.
    I have setup the receiver SOAP adapter and tried specifying the client authentication by choosing the private key that's in the key store in Visual Admin.
    Ive also tried selecting web services security and configuring the receiver agreement. In the logs I continue to see the below message.
    "Attempting to create outgoing ssl connection without trusted certificates"
    This seems to back up what the partner is saying. Why would this occur?

    This scenario is slightly different. All certificates are loaded in the keystore.
    In order to authenticate thru their gateway, we provided them with our public key. We then need to use that public key when sending the message. Slightly different from the normal way this works but it shouldnt make a difference as long as we select the right cert in the ID.
    I confirmed in the logs it's trying to load the keystore view and entry I specify, yet they still don't see any certificate in the request. I can't seem to verify this on my own as I can't see what's actually being sent to them.
    Another thing I noticed is that the selection help in the receiver soap adapter only lists the private key entries vs the public key entries. You have to manually type in the right entry.

Maybe you are looking for

  • PreLoad ALL images within a site?

    My ImageReady rollover preloads are working fine (per page). However, can someone please provide script that I can place in my index page, that downloads every single image in my site? Thanks.

  • HR Mini Master for beginners...

    Hi, I need some hr mini master overview tutorial. I am mini master beginner with many questions. What are Mini Master basic infotypes, basic transaction... I tried to find on forum, google, but I have no complete view of HR MM. Please help!

  • Picklist Descriptions not reflected

    Hi, I modified some of the Picklist descriptions for 2 Picklists already present on the Account detail object. When I generated a report including these 2 Picklists only their old descriptions are being displayed and not the newly modified ones. This

  • Automated Balance Sheet Reconciliation

    Hi I have a user requirement in terms of automated balance sheet recs. The key consideration is that the recs are identified on an exception basis and secondly the we can flag the reconciling items so that they are identifiable on a month to month ba

  • About Oracle applications (Questions)

    Hi All, What is purpose of Attribute columns, Segment Columns, & Reference Columns in Oracle applications tables (oracle e-business suite tables)? Any help would appreciate Thanks, [email protected]