Hp mini fails to boot

My hp mini when press the start up button it starts but it just be loading showing microsoft corporation and after about 5 minutes it will go off and restarts itself. how can this problem be fixed?

HP laptops use BIOSes with the whitelist. It means that only supported devices can be used in these laptops. Go to the HP download webpage and find a maintenance and service guide for the laptop. All compatible components are listed in it. The Intel Advanced-N 6200 is not supported by the whitelist and you always get the 104 error. However, you may try to bypass the whitelist by a small changing in the BIOS. It's not recommended because you can brick the laptop and loose warranty as well..
Dv6-7000 /Full HD/Core i5-3360M/GF 650M/Corsair 8GB/Intel 7260AC/Samsung Pro 256GB
Testing - HP 15-p000
HP Touchpad provided by HP
Currently on Debian Wheeze
*Please, help other users with the same issue by marking your solved topics as "Accept as Solution"*

Similar Messages

  • Mini fails to boot

    I have a mini which gets stuck at the boot screen and never loads the OS. Normally I would put a snow leopard disk in to use the disk utility but it's not booting off of disc nor am I able to successfully network boot. I tried resetting the PRAM and NVRAM with no success. Is there anything else I could try?

    Hi, My Mac Mini stopped about 2 min before finishing (the last?) cycle in installing the Yosemite OS X. The HD went completely silent for dozens of minutes. I have then decided to reboot the unresponsive Mini and it eventually hung up again at the screen saying that about 2 min remain to finish the installation. I do not know what to do. I left my Mini at work for the weekend in this state (2 min to finish the installation, but apparently in a dead state, unresponsive). Importantly, although the Yosemite download is said to be about 5.3 Gb in size, I eventually got the message that there was not enough space on my HD to finish the installation. I have Mac Mini with 1 TB Fusion drive, 16Gb of RAM, about 2 years old. There was about 450 Gb of free space before installation. Any suggestions anybody about what should I do next? Thanks, Zed
    P.S. Is the installation process truly dead because of the lack of space on my HD? Could there be a glitch in the installation procedure so that the HD is getting filled with the installation files and eventually fill a space of 450 Gb? Is it possible that the installation procedure initiated several parallel processes which would not erase the previously downloaded files, thereby filling up the HD eventually?

  • Mac mini doesn't booting

    I got a problem with my late 2012 mac mini ( intel core i5 processor, 500GB HDD). I was playing "Call of Duty" when it stopped working(freezed). I tried to press any button on the keyboard but nothing happened. Then I shutted it down by pressing power button. But when I press the power button once again, my mac mini failed to boot. The indicator light is on but there isn't boot sound and the screen is blank either. I tried to restart several times but its still didnt boot. Anyone here can help me? thanks.

    Troubleshooting: My computer won't turn on

  • Mac Mini won't boot after 10.6.6 / Airport update

    I just reinstalled 10.6.3 on a unibody Mac Mini, updated to 10.6.6 - and it booted fine. I ran another software update, and it suggested two more updates - which I believe was an Airport Utility update and a Java update. Now the Mac Mini fails to boot, stopping at the Apple logo.
    The last lines of verbose startup goes like this:
    Airport: Link Down on en1. Reason 8 (Disassociated because station leaving).
    Aut result for: (MAC address) succeded
    AirPort: Link Up on en1
    AirPort: RSN handshake complete on en1
    AppleBCM5701Ethernet: 0 0 setFixedSpeed - logic error, speed any?
    Suggestions?
    H

    I experienced a similar problem today after a recent upgrade to 10.6.6. I ran Tech Tool Pro 5 on the machine, which reported everything as just dandy after about 6 hours of testing, but it still wouldn't boot. Next, I tried booting in Verbose mode, which revealed that my iMac was hanging on:
    AppleBCM5701Ethernet: 0 0 setFixedSpeed - logic error, speed any?
    I used Safe Single User mode (turn on power, then immediately press and hold Shift-Command-S until text starts appearing) to boot to a command line. Single User mode provides instructions on how to mount the file system read/write. I executed the `fsck` command as instructed, and after a few minutes it reported that it had made changes to the file system. At that point, I skipped the `mount` command and went directly to `exit` to continue the boot process, which completed. I turned AirPort back on (I had it turned off), then rebooted normally without any trouble.

  • Mac Mini won't boot after failed XP installation

    Recently upgrade HD to 320GB 7200 rpm and 3GB ram. Running 10.5.8 fine.
    I tried to install Windows XP through Boot Camp, but wasn't successful, I terminated the installation. Then Mac Mini won't boot up. When powered on, you heard the chime, then grey screen showed and stayed. Tried starting with "C" (boot from CD), "OPT" (boot option), "T" (target), and reset PRAM. None of them worked.
    What should I try next?
    Thanks
    Message was edited by: Yijian Cao

    If you install XP on Bootcamp, your startup disc will be changed to XP Windows partitioned you did. To restore your startup disc back to Mac OS, make sure your Mac is turned off. 1. Plug the power back and press the power button ON. When you hear the power On sound, press and hold the ALT key on your keyboard until you see the hardrives. 2. Select the HD that says MAc OS, then your mac will boot back to Mac OS.
    Let me know if you have more problems, maybe I can help.
    Abel

  • IBook G4 fails to boot with internal HD installed, works when removed

    The short version: My iBook started failing to boot via any method (gray screen) and the boot menu (Option during startup) would freeze. Replaced HD, things were better. Six months into new HD, nearly the same symptoms appear again. Removed HD, now running off different HD via FireWire.
    The long version–
    Back in late 2008-12, my iBook started failing to boot up. Usually it would refuse to boot from any source. Booting the internal disk (10.4.11) would get to a gray screen without any logo and stay there. Holding down Option, the boot menu would come up, but it would usually freeze before it displayed any volumes. Booting from CD (AHT, or OS install disc) would fail in nearly the same way as booting from the internal drive. Target Disk Mode would start, but once the other machine tried to access the drive, the FireWire logo would stop moving and the drive would never show up on the other computer. Very rarely, the machine would get a bit further through one of the boot mechanisms, but it usually froze while booting or just after login.
    This machine has gone through three logic boards in the past, so I suspected that was the problem again. I took it to a local Genius Bar and the Genius explained that it was probably the hard drive. He said that sometimes, depending on the way the drive fails, it can "take out" other parts of the system due to drawing too much current, etc.
    I was a bit skeptical, but it was going to be much cheaper to replace the HD myself than it would be to send it in for a MLB replacement. So I ordered a new HD (80G) and a USB-to-ATA/SATA adapter. I hoped that I would be able to use the adapter to savlage a bit more data off the drive (it originally failed right before a backup!).
    After extracting the HD (40G), I connected it to the USB adapter and was able to access the drive just fine. I used another machine to run another backup from the recently removed HD (40G) to one of my FireWire backup drives and proceeded to put the iBook back together with the new HD (80G).
    Once it was all back together, the new HD worked fine. I was able to restore the recent backup from my FireWire drive to the internal, and it worked fine. The only oddity I noticed was that the new drive was apparently trying to sleep several times a minute. I used smartctl (installed via MacPorts) to adjust the power management setting on the drive, and that seemed to help. I also started running smartd (also via MacPorts) to better monitor the new drive.
    Recently, a bit more than six months after the new HD was installed, the new HD started showing errors in the system.log. I never found any errors in the logs after the previous HD failed (even though I could look through the logs just fine with the drive attached through the ATA-USB adapter).
    Jul 2 18:04:40 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 2 18:33:43 Blinky smartd\[217]: Device: disk0, ATA error count increased from 0 to 30\n
    Jul 3 02:03:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 30 to 31\n
    Jul 3 03:03:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 31 to 32\n
    Jul 6 23:33:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 32 to 33\n
    Jul 7 00:33:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 33 to 34\n
    Jul 7 12:42:24 Blinky smartd\[217]: Device: disk0, ATA error count increased from 34 to 36\n
    Jul 7 13:17:59 Blinky kernel\[0]: disk0s3: I/O error.
    +same error message a bit faster than one every 3 seconds+
    Jul 7 13:23:00 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 13:33:44 Blinky smartd\[217]: Device: disk0, ATA error count increased from 36 to 615\n
    Jul 7 21:17:05 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:17:12 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:17:12 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:17:12 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:17:15 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:17:18 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:17:21 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:17:23 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:17:29 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:18:17 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:19:21 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:19:23 Blinky kernel\[0]: disk0s3: I/O error.
    I did not notice the errors until the afternoon of the 7th when the problem became evident. The events around 13:00 happened when I was trying to run a backup. The first backup failed in an odd way (when I came back to check on it later that evening, SuperDuper! seemed to have quit running). So I restarted the backup and started looking around in the logs. That is when I noticed the kernel I/O error messages. When I asked smartctl to query the drive, it showed that many errors had been occurring and it displayed the drive's log of the last five or so errors (alas, I did not save this output). Meanwhile the re-run of SuperDuper! was having problems again. It seemed to have hung (no SDAgent or SDCopy processes were running, but the main UI was still there). Since the backup was not getting anywhere, I decided to shutdown for a while and try again later.
    When I did try again later, I was back in the situation of six months ago. It would not boot at all (no internal, no FireWire, no CD/DVD, boot menu hangs, Target Disk Mode hangs). So, I opened up the system, removed the HD and put it back together without an internal HD. The machine is now able to boot and run from FireWire. Again, the (6 month old, 80G) HD "works fine" via the USB adapter. If SMART were available through the USB adapter, I could check to see if the drive is continuing to have problems. I used SuperDuper! to copy the HD to a volume on my FireWire drive which is how I an now running the system.
    Has anyone had any similar problems? Any idea why my iBook seems to be killing/rejecting hard drives? (I say killing because, while the drive is connected internally, it certainly seems to be dying. I say rejecting because once the drive is out of the system, both the drive and the system seem to "recover".) I have read messages there where others report success having their iBook MLB resoldered ("reball"). Has anyone experienced substantially similar issues that were solved with a resolder repair?
    Thanks!

    I was able to test my “failing” ATA drives in a G4 Mac mini (I had to take the mini apart because its drive had finally failed). I was able to successfully boot the Mac mini with either of my iBook drives installed. Once booted, +Disk Utility+ said that each one's SMART Status was Verified. I used smartctl to pull the full SMART info while I had them installed in the Mac mini.
    Since the drives were still “good”, I think this emphasizes that the problem is with the ATA interface on my iBook's logic board. Maybe it is broken, or maybe it just needs to be resoldered. For now I am happy just booting off an external Firewire drive.
    BTW, I ended up installing the 6 month old 80G drive in the mini. It has been working OK for 10 days now. As long as it continues to operate normally in the mini, it will serve as evidence that my iBook's HD ATA controller is borked. I just hope the ATA controller is more capable of accepting its fallibility than was HAL.
    There is a minor problem with the 80G in the mini in that I am unable to use hdapm to change the aggressive head unloading that the drive suffers. I was able to adjust it with hdapm while it was in my iBook. I am able to adjust it with hdparm under Linux on the mini. Luckily the change I made while booted in Linux "sticks" after rebooting back into Mac OS X (I hear it will be lost if the drive is completely powered off though).

  • Mac Mini Won't Boot with VGA Monitor Connected

    I have a new Mac Mini connected to an older VGA monitor using the Apple brand VGA adapter.  The mini is fully up to date and runs perfectly when booted.  However, if I reboot the mini with the VGA monitor connected, it fails to boot.  I just hear the faint chime sound every other second.  There is no output to the monitor and the only way I can get it to boot is to disconnect the monitor and then power cycle the mini.  I can reconnect the monitor just seconds after powering back on and it finishes booting properly.
    Anyone else experience this?  It is very frustrating.  I've also tested with an HDMI connected monitor (without the VGA adapter) and it boots just fine and the display works properly.
    Thanks!

    Okay, I'm back with good news: I have found two remedies for the problem which will hopefully solve it for you as well.
    Given that the issue only occurs when certain monitors are connected, I concluded that the root of it must be a bug in the Mac's firmware related to DDC (Display Data Channel) handling, and that the most promising way to address it should be to just disable the DDC.
    Workaround #1: If your monitor has BNC connectors, use a VGA to BNC cable.
    In this configuration the DDC pins are not connected to the monitor at all. This did indeed fix the problem - my Mac mini booted without a problem with the monitor connected. However, I was not completely satisfied with this solution, because VGA to BNC cables are usually quite heavy and inflexible, and do no go together well with Apple's MDP to VGA adapter and the Mini Displayport/Thunderbolt port which has no locking mechanism.
    Workaround #2: Remove pin 12 of the VGA plug.
    Pin 12 of the VGA plug connects the serial data line of the DDC. Pulling out this pin with a pair of needle nose pliers will effectively disable DDC. I hesitated to do this to my cable (a direct MDP to VGA cable which eliminates the need for a separate adapter dangling from the Mac) and therefore bought a tiny VGA male to female adapter (also called port saver, e.g. Delock 65250) to perform the surgery on that. This has done the trick and my Mac mini has started up fine ever since.
    Of course, without DDC the Mac won't know the model name and capabilities of the attached monitor and thus offer some resolution and frequency settings which the monitor may not support, but that's a small drawback compared to having to pull out the monitor cable everytime you turn on or restart your Mac.

  • Mac Mini Won't Boot or Internet Restore - Hard Drive Boots on Macbook

    Late 2012 Mac Mini. I cloned my 10.10.2 installation of Yosemite over from my Macbook pro 6,2 to a 1TB Samsung 840 SSD. It booted with no issues besides the keychain being lost and all passwords having to be re-entered.
    After a week of going perfectly, it stops recognizing the USB keyboard after I unplugged it and plugged it back in. So I rebooted and get the dreaded stop sign after the boot failed. Oops. I enabled trim before I cloned, but forgot to check if it was working in the cloned drive (seems it was in the end). Since there was no recovery partition, I booted into Internet Recovery, but that hung using both WPA and WPA2 router logins. It obviously was syncing with router, but I got error -2002f in every configuration I tried. It also didn't seem to recognize an ethernet connection. Weird stuff.
    I remembered I had an issue with a previous Mac Mini of the same model and the permissions after a clone. I repaired permissions and that was that. This is different because it wouldn't boot into Safe Mode. Resetting the PRAM did bring back an audible chime at least.
    I pulled the SSD out of the Mac Mini and alt booted in from my Macbook 6,2. No issues (except the keychain thing again( and it loaded quickly. Nothing seemed to be wrong.
    Then I put it back in the Mac Mini and tested it with known working RAM. Still the same thing. So now I am going to sleep on it and try to figure it out. It is unlikely to be a hardware failure as the Mac Mini was made in May 2014 and I bought factory refurbished.  It seems to be an issue relating to the SSD as it boots other drives.
    Any ideas?

    Fix The Bugs Please wrote:
    It is unlikely to be a hardware failure as the Mac Mini was made in May 2014 and I bought factory refurbished.  It seems to be an issue relating to the SSD as it boots other drives.
    Any ideas?
    Is this SSD an additional drive added to your Mac Mini or did you replace the HDD with it? If it's an additional drive and since it's a Samsung, depending where you purchased your drive doubler kit (iFixit or OWC) you can try swapping the drives in the bays. I know for a fact that Samsung SSDs do not work right with the iFixit drive doubler kit's SATA cable. But it does work correctly with the Apple supplied SATA cable. If it's the OWC SATA cable, I know for a fact those are much more reliable with Samsung, OWC, Intel, Crucial SSDs. Another thing, I would NOT enable TRIM (my opinion) using a 3rd party trim enabler if you're running Yosemite. There are issues with trim enablers and Yosemite. Just let the built-in Garbage Collection take care of things.
    If it's not an additional drive that was added, does your Mac Mini boot and work fine with the stock drive that it came with? Even though it's a 2012 model, if you purchased it refurbished from Apple in May 2014, you're still under warranty (same 1yr as new Macs) and if it's having same or similar issues working with the stock drive, you can take it to a local Apple Store for warranty repair. You would need to have only the stock drive installed (no SSD) before you setup an appointment.

  • Mac mini won't boot after RAM upgrade.

    Tried installing new RAM in my Mac Mini, 512MB stock to 2GB of Crucial. Followed the directions to a T, grounded myself the whole time.
    Things I've tried so far:
    1. Resetting the PRAM, no luck.
    2. Holding option at start-up, shows no icon.
    3. Holding shift, no luck.
    4. Holding X, nothing.
    How do I get it to accept a CD if it won't boot?

    Welcome to Apple Discussions!
    You clearly have a problem, but you don't describe exactly what that is other than that your mini won't boot after the upgrade. What happens when it starts up? Does it attempt to start and hang up on the grey or blue screens, or does it start beeping at you almost immediately after you try and start it up, and also flash the power light?
    If the former, then you may have dislodged a connector while working inside the system, in which case opening it up and checking that everything is firmly connected would be the first thing to do. If the latter, then the beeping/light flashing is the system telling you it has failed the power-on self test and the pattern of beeps/lights indicates why. In your case likely the system can't find workable memory. In that instance, opening the system and ensuring that the RAM is firmly and fully seated would be a good step, and if the mini continues to fail, then replacing the new RAM with the original to test that the system will then start.
    It is not likely that anything had damaged your MacOS install in the process of upgrading, thus normally no reason to need to boot to CD as a result of a RAM issue.

  • 2005 PPC 1.5 GHz mini won't boot

    I have a problem similar to another recent poster.
    My wife's mini won't boot up. We just get a gray screen and then the flashing folder/OS/question mark icon. I tried keyboard shortcuts at start-up with no effect. I can hear the HD hiccuping and starting and stopping. She had come back from lunch and the screensaver would not go away. Reboots brought the grey screen.
    I've had similar issues and it sounds like the HD died. Does anyone think it is worth installing a new HD into this old Mini? Trying to save data off the HD? Thoughts appreciated.

    credit card is the last resort of the desperate
    but mostly works. but as you're going to open it up anyway...
    i don't like these slot-in drives at all, as this stuck disk thing happens far too often. they should have stuck to tray loading drives. no problem to get a stuck CD out there. meanwhile i mostly use an external dvd burner for my macbook and mini anyway. faster and more reliable.
    if the DVD drive functioned before, maybe it's just accidental, that the DVD got stuck at this moment. stuck disks are quite common.
    you don't know if it's the same problem as the other poster had. looks the same at first glance, but you can only make sure by getting the stuck DVD out and retry with the correct one. you've to find out, if the mini can boot from another device. if that fails, then you may be in for more trouble (logic board etc.) and if that's the case, it's probably best to go directly for a new mini or maybe a used one in good condition on ebay.

  • Random I/O errors (hdd) and failing to boot, Windows not affected

    I'm experiencing lots of I/O errors when booting and running my Linux partition. I am dual booting Windows 7 (x86_64) and Arch Linux (i686) on a single HDD.
    Im using a Lenovo Ideapad G505s with a Seagate ST1000LM HDD and an SDD currently not in use.
    Partition layout:
    NAME FSTYPE LABEL UUID MOUNTPOINT
    sda
    ├─sda1 ntfs System Reserved D8B40750B4073094
    ├─sda2 ntfs 00EA107FEA107360
    └─sda3 ext3 b753e7d2-6a23-4c20-8fa7-bf281a4a09e4 /
    sr0
    All three are primary partitions. Using ext4 yields the exact same result.
    The problem is easy to reproduce:
    Install Windows 7 to first half of HDD and Arch on the second half
    At first Arch works fine but over the next couple of days increasingly more I/O errors show up and at some point the system fails to boot
    Windows seems to work just fine
    Dmesg output:
    [ 0.000000] Initializing cgroup subsys cpuset
    [ 0.000000] Initializing cgroup subsys cpu
    [ 0.000000] Initializing cgroup subsys cpuacct
    [ 0.000000] Linux version 3.16.2-1-ARCH (nobody@var-lib-archbuild-testing-i686-tobias) (gcc version 4.9.1 (GCC) ) #1 SMP PREEMPT Sat Sep 6 13:13:35 CEST 2014
    [ 0.000000] e820: BIOS-provided physical RAM map:
    [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009f3ff] usable
    [ 0.000000] BIOS-e820: [mem 0x000000000009f400-0x000000000009ffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000009555dfff] usable
    [ 0.000000] BIOS-e820: [mem 0x000000009555e000-0x0000000095d5efff] reserved
    [ 0.000000] BIOS-e820: [mem 0x0000000095d5f000-0x0000000095dbbfff] usable
    [ 0.000000] BIOS-e820: [mem 0x0000000095dbc000-0x00000000966bbfff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000966bc000-0x000000009f8befff] usable
    [ 0.000000] BIOS-e820: [mem 0x000000009f8bf000-0x000000009fabefff] reserved
    [ 0.000000] BIOS-e820: [mem 0x000000009fabf000-0x000000009fbbefff] ACPI NVS
    [ 0.000000] BIOS-e820: [mem 0x000000009fbbf000-0x000000009fbfefff] ACPI data
    [ 0.000000] BIOS-e820: [mem 0x000000009fbff000-0x000000009fbfffff] usable
    [ 0.000000] BIOS-e820: [mem 0x000000009fc00000-0x00000000cfffffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000fed80000-0x00000000fed80fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000ffc00000-0x00000000ffffffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000022effffff] usable
    [ 0.000000] Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
    [ 0.000000] SMBIOS 2.7 present.
    [ 0.000000] DMI: LENOVO 20255/Lenovo G505s, BIOS 83CN35WW(V2.05) 12/06/2013
    [ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
    [ 0.000000] e820: last_pfn = 0x9fc00 max_arch_pfn = 0x100000
    [ 0.000000] MTRR default type: uncachable
    [ 0.000000] MTRR fixed ranges enabled:
    [ 0.000000] 00000-9FFFF write-back
    [ 0.000000] A0000-BFFFF uncachable
    [ 0.000000] C0000-FFFFF write-through
    [ 0.000000] MTRR variable ranges enabled:
    [ 0.000000] 0 base 000000000000 mask FFFF80000000 write-back
    [ 0.000000] 1 base 000080000000 mask FFFFE0000000 write-back
    [ 0.000000] 2 base 00009FBBD000 mask FFFFFFFFF000 uncachable
    [ 0.000000] 3 base 0000FFC00000 mask FFFFFFC00000 write-protect
    [ 0.000000] 4 disabled
    [ 0.000000] 5 disabled
    [ 0.000000] 6 disabled
    [ 0.000000] 7 disabled
    [ 0.000000] TOM2: 000000022f000000 aka 8944M
    [ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    [ 0.000000] found SMP MP-table at [mem 0x000fe1b0-0x000fe1bf] mapped at [c00fe1b0]
    [ 0.000000] Scanning 1 areas for low memory corruption
    [ 0.000000] initial memory mapped: [mem 0x00000000-0x01bfffff]
    [ 0.000000] Base memory trampoline at [c009b000] 9b000 size 16384
    [ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
    [ 0.000000] [mem 0x00000000-0x000fffff] page 4k
    [ 0.000000] init_memory_mapping: [mem 0x37000000-0x373fffff]
    [ 0.000000] [mem 0x37000000-0x373fffff] page 2M
    [ 0.000000] init_memory_mapping: [mem 0x30000000-0x36ffffff]
    [ 0.000000] [mem 0x30000000-0x36ffffff] page 2M
    [ 0.000000] init_memory_mapping: [mem 0x00100000-0x2fffffff]
    [ 0.000000] [mem 0x00100000-0x003fffff] page 4k
    [ 0.000000] [mem 0x00400000-0x2fffffff] page 2M
    [ 0.000000] init_memory_mapping: [mem 0x37400000-0x377fdfff]
    [ 0.000000] [mem 0x37400000-0x377fdfff] page 4k
    [ 0.000000] BRK [0x01798000, 0x01798fff] PGTABLE
    [ 0.000000] RAMDISK: [mem 0x7fcaf000-0x7fffffff]
    [ 0.000000] Allocated new RAMDISK: [mem 0x374ad000-0x377fd0d0]
    [ 0.000000] Move RAMDISK from [mem 0x7fcaf000-0x7ffff0d0] to [mem 0x374ad000-0x377fd0d0]
    [ 0.000000] ACPI: Early table checksum verification disabled
    [ 0.000000] ACPI: RSDP 0x000FE020 000024 (v02 LENOVO)
    [ 0.000000] ACPI: XSDT 0x9FBFE120 000094 (v01 LENOVO CB-01 00000001 01000013)
    [ 0.000000] ACPI: FACP 0x9FBFB000 00010C (v05 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: DSDT 0x9FBEA000 00CA66 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: FACS 0x9FB7C000 000040
    [ 0.000000] ACPI: SLIC 0x9FBFD000 000176 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: UEFI 0x9FBFC000 000236 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: HPET 0x9FBFA000 000038 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: APIC 0x9FBF9000 000084 (v03 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: MCFG 0x9FBF8000 00003C (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: ASF! 0x9FBF7000 0000A5 (v32 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: BOOT 0x9FBE9000 000028 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: WDRT 0x9FBE8000 000047 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: WDAT 0x9FBE7000 0001AC (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: FPDT 0x9FBE5000 000044 (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: MSDM 0x9FBE4000 000055 (v03 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: SSDT 0x9FBE3000 000B9C (v01 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: SSDT 0x9FBE1000 001F6E (v02 LENOVO CB-01 00000001 ACPI 00040000)
    [ 0.000000] ACPI: Local APIC address 0xfee00000
    [ 0.000000] 1668MB HIGHMEM available.
    [ 0.000000] 887MB LOWMEM available.
    [ 0.000000] mapped low ram: 0 - 377fe000
    [ 0.000000] low ram: 0 - 377fe000
    [ 0.000000] BRK [0x01799000, 0x01799fff] PGTABLE
    [ 0.000000] Zone ranges:
    [ 0.000000] DMA [mem 0x00001000-0x00ffffff]
    [ 0.000000] Normal [mem 0x01000000-0x377fdfff]
    [ 0.000000] HighMem [mem 0x377fe000-0x9fbfffff]
    [ 0.000000] Movable zone start for each node
    [ 0.000000] Early memory node ranges
    [ 0.000000] node 0: [mem 0x00001000-0x0009efff]
    [ 0.000000] node 0: [mem 0x00100000-0x9555dfff]
    [ 0.000000] node 0: [mem 0x95d5f000-0x95dbbfff]
    [ 0.000000] node 0: [mem 0x966bc000-0x9f8befff]
    [ 0.000000] node 0: [mem 0x9fbff000-0x9fbfffff]
    [ 0.000000] On node 0 totalpages: 649053
    [ 0.000000] free_area_init_node: node 0, pgdat c161c180, node_mem_map f60b5020
    [ 0.000000] DMA zone: 32 pages used for memmap
    [ 0.000000] DMA zone: 0 pages reserved
    [ 0.000000] DMA zone: 3998 pages, LIFO batch:0
    [ 0.000000] Normal zone: 1744 pages used for memmap
    [ 0.000000] Normal zone: 223230 pages, LIFO batch:31
    [ 0.000000] HighMem zone: 3337 pages used for memmap
    [ 0.000000] HighMem zone: 421825 pages, LIFO batch:31
    [ 0.000000] Using APIC driver default
    [ 0.000000] ACPI: PM-Timer IO Port: 0x408
    [ 0.000000] ACPI: Local APIC address 0xfee00000
    [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x10] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x11] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x12] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x13] enabled)
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
    [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
    [ 0.000000] ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
    [ 0.000000] IOAPIC[0]: apic_id 4, version 33, address 0xfec00000, GSI 0-23
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
    [ 0.000000] ACPI: IRQ0 used by override.
    [ 0.000000] ACPI: IRQ2 used by override.
    [ 0.000000] ACPI: IRQ9 used by override.
    [ 0.000000] Using ACPI (MADT) for SMP configuration information
    [ 0.000000] ACPI: HPET id: 0x10228210 base: 0xfed00000
    [ 0.000000] smpboot: Allowing 4 CPUs, 0 hotplug CPUs
    [ 0.000000] nr_irqs_gsi: 40
    [ 0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
    [ 0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
    [ 0.000000] e820: [mem 0xd0000000-0xf7ffffff] available for PCI devices
    [ 0.000000] Booting paravirtualized kernel on bare hardware
    [ 0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:4 nr_node_ids:1
    [ 0.000000] PERCPU: Embedded 14 pages/cpu @f6071000 s33344 r0 d24000 u57344
    [ 0.000000] pcpu-alloc: s33344 r0 d24000 u57344 alloc=14*4096
    [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
    [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 647277
    [ 0.000000] Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/sda3 rw radeon.dpm=1 initrd=../initramfs-linux.img
    [ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
    [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
    [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
    [ 0.000000] Initializing CPU#0
    [ 0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
    [ 0.000000] allocated 5234680 bytes of page_cgroup
    [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
    [ 0.000000] Initializing HighMem for node 0 (000377fe:0009fc00)
    [ 0.000000] Initializing Movable for node 0 (00000000:00000000)
    [ 0.000000] Memory: 2558328K/2596212K available (4512K kernel code, 483K rwdata, 1328K rodata, 568K init, 824K bss, 37884K reserved, 1687300K highmem)
    [ 0.000000] virtual kernel memory layout:
    fixmap : 0xfff16000 - 0xfffff000 ( 932 kB)
    pkmap : 0xff800000 - 0xffc00000 (4096 kB)
    vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB)
    lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB)
    .init : 0xc1630000 - 0xc16be000 ( 568 kB)
    .data : 0xc146853a - 0xc162ec80 (1817 kB)
    .text : 0xc1000000 - 0xc146853a (4513 kB)
    [ 0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok.
    [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
    [ 0.000000] Preemptible hierarchical RCU implementation.
    [ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
    [ 0.000000] Dump stacks of tasks blocking RCU-preempt GP.
    [ 0.000000] RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
    [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
    [ 0.000000] NR_IRQS:2304 nr_irqs:712 16
    [ 0.000000] CPU 0 irqstacks, hard=f5408000 soft=f540a000
    [ 0.000000] Console: colour VGA+ 80x25
    [ 0.000000] console [tty0] enabled
    [ 0.000000] hpet clockevent registered
    [ 0.000000] tsc: Fast TSC calibration using PIT
    [ 0.000000] tsc: Detected 1896.408 MHz processor
    [ 0.000028] Calibrating delay loop (skipped), value calculated using timer frequency.. 3794.85 BogoMIPS (lpj=6321360)
    [ 0.000032] pid_max: default: 32768 minimum: 301
    [ 0.000037] ACPI: Core revision 20140424
    [ 0.009582] ACPI: All ACPI Tables successfully acquired
    [ 0.015209] Security Framework initialized
    [ 0.015217] Yama: becoming mindful.
    [ 0.015230] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
    [ 0.015233] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
    [ 0.015472] Initializing cgroup subsys memory
    [ 0.015491] Initializing cgroup subsys devices
    [ 0.015498] Initializing cgroup subsys freezer
    [ 0.015502] Initializing cgroup subsys net_cls
    [ 0.015507] Initializing cgroup subsys blkio
    [ 0.015528] [Firmware Info]: CPU: Re-enabling disabled Topology Extensions Support.
    [ 0.015531] CPU: Physical Processor ID: 0
    [ 0.015532] CPU: Processor Core ID: 0
    [ 0.015536] mce: CPU supports 7 MCE banks
    [ 0.015551] Last level iTLB entries: 4KB 512, 2MB 1024, 4MB 512
    Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 512, 1GB 0
    tlb_flushall_shift: 6
    [ 0.015678] Freeing SMP alternatives memory: 16K (c16be000 - c16c2000)
    [ 0.016347] ftrace: allocating 19356 entries in 38 pages
    [ 0.023471] Enabling APIC mode: Flat. Using 1 I/O APICs
    [ 0.023812] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    [ 0.056821] smpboot: CPU0: AMD A8-4500M APU with Radeon(tm) HD Graphics (fam: 15, model: 10, stepping: 01)
    [ 0.162662] Performance Events: Fam15h core perfctr, AMD PMU driver.
    [ 0.162668] ... version: 0
    [ 0.162670] ... bit width: 48
    [ 0.162671] ... generic registers: 6
    [ 0.162672] ... value mask: 0000ffffffffffff
    [ 0.162674] ... max period: 00007fffffffffff
    [ 0.162675] ... fixed-purpose events: 0
    [ 0.162676] ... event mask: 000000000000003f
    [ 0.179472] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    [ 0.186176] CPU 1 irqstacks, hard=f554a000 soft=f554c000
    [ 0.186179] x86: Booting SMP configuration:
    [ 0.186182] .... node #0, CPUs: #1
    [ 0.218942] Initializing CPU#1
    [ 0.218972] [Firmware Info]: CPU: Re-enabling disabled Topology Extensions Support.
    [ 0.226174] CPU 2 irqstacks, hard=f5570000 soft=f5572000
    [ 0.226179] #2
    [ 0.258736] Initializing CPU#2
    [ 0.258760] [Firmware Info]: CPU: Re-enabling disabled Topology Extensions Support.
    [ 0.266174] CPU 3 irqstacks, hard=f559a000 soft=f559c000
    [ 0.266180] #3
    [ 0.276300] Initializing CPU#3
    [ 0.277268] [Firmware Info]: CPU: Re-enabling disabled Topology Extensions Support.
    [ 0.279379] x86: Booted up 1 node, 4 CPUs
    [ 0.279384] smpboot: Total of 4 processors activated (15177.40 BogoMIPS)
    [ 0.280484] devtmpfs: initialized
    [ 0.280769] PM: Registering ACPI NVS region [mem 0x9fabf000-0x9fbbefff] (1048576 bytes)
    [ 0.281973] pinctrl core: initialized pinctrl subsystem
    [ 0.282053] RTC time: 22:28:26, date: 09/21/14
    [ 0.282107] NET: Registered protocol family 16
    [ 0.282225] cpuidle: using governor ladder
    [ 0.282228] cpuidle: using governor menu
    [ 0.282436] ACPI: bus type PCI registered
    [ 0.282439] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
    [ 0.282552] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
    [ 0.282556] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
    [ 0.282558] PCI: Using MMCONFIG for extended config space
    [ 0.282559] PCI: Using configuration type 1 for base access
    [ 0.293370] ACPI: Added _OSI(Module Device)
    [ 0.293374] ACPI: Added _OSI(Processor Device)
    [ 0.293376] ACPI: Added _OSI(3.0 _SCP Extensions)
    [ 0.293378] ACPI: Added _OSI(Processor Aggregator Device)
    [ 0.297280] ACPI: Executed 1 blocks of module-level executable AML code
    [ 0.301911] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
    [ 0.323484] ACPI: Interpreter enabled
    [ 0.323495] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20140424/hwxface-580)
    [ 0.323501] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20140424/hwxface-580)
    [ 0.323519] ACPI: (supports S0 S3 S4 S5)
    [ 0.323522] ACPI: Using IOAPIC for interrupt routing
    [ 0.323762] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    [ 0.324136] [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness
    [ 0.324308] [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness
    [ 0.324511] [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness
    [ 0.335527] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    [ 0.335534] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
    [ 0.335540] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
    [ 0.335709] acpi PNP0A08:00: ignoring host bridge window [mem 0x000cc000-0x000cffff] (conflicts with Video ROM [mem 0x000c0000-0x000cf1ff])
    [ 0.335713] acpi PNP0A08:00: ignoring host bridge window [mem 0x000d0000-0x000d3fff] (conflicts with Adapter ROM [mem 0x000cf800-0x000d07ff])
    [ 0.335718] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
    [ 0.335971] PCI host bridge to bus 0000:00
    [ 0.335974] pci_bus 0000:00: root bus resource [bus 00-ff]
    [ 0.335977] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
    [ 0.335985] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    [ 0.335988] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    [ 0.335990] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000c3fff]
    [ 0.335992] pci_bus 0000:00: root bus resource [mem 0x000c4000-0x000c7fff]
    [ 0.335994] pci_bus 0000:00: root bus resource [mem 0x000c8000-0x000cbfff]
    [ 0.335996] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff]
    [ 0.335998] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff]
    [ 0.336000] pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff]
    [ 0.336001] pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff]
    [ 0.336003] pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff]
    [ 0.336005] pci_bus 0000:00: root bus resource [mem 0x000e8000-0x000ebfff]
    [ 0.336007] pci_bus 0000:00: root bus resource [mem 0x000ec000-0x000effff]
    [ 0.336009] pci_bus 0000:00: root bus resource [mem 0xd0000000-0xf7ffffff]
    [ 0.336011] pci_bus 0000:00: root bus resource [mem 0xfc000000-0xfed3ffff]
    [ 0.336013] pci_bus 0000:00: root bus resource [mem 0xfed45000-0xffffffff]
    [ 0.336022] pci 0000:00:00.0: [1022:1410] type 00 class 0x060000
    [ 0.336199] pci 0000:00:01.0: [1002:9903] type 00 class 0x030000
    [ 0.336211] pci 0000:00:01.0: reg 0x10: [mem 0xd0000000-0xdfffffff pref]
    [ 0.336217] pci 0000:00:01.0: reg 0x14: [io 0x4000-0x40ff]
    [ 0.336224] pci 0000:00:01.0: reg 0x18: [mem 0xf0300000-0xf033ffff]
    [ 0.336266] pci 0000:00:01.0: supports D1 D2
    [ 0.336358] pci 0000:00:01.1: [1002:9902] type 00 class 0x040300
    [ 0.336369] pci 0000:00:01.1: reg 0x10: [mem 0xf0344000-0xf0347fff]
    [ 0.336417] pci 0000:00:01.1: supports D1 D2
    [ 0.336509] pci 0000:00:02.0: [1022:1412] type 01 class 0x060400
    [ 0.336560] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
    [ 0.336710] pci 0000:00:04.0: [1022:1414] type 01 class 0x060400
    [ 0.336759] pci 0000:00:04.0: PME# supported from D0 D3hot D3cold
    [ 0.336812] pci 0000:00:04.0: System wakeup disabled by ACPI
    [ 0.336867] pci 0000:00:05.0: [1022:1415] type 01 class 0x060400
    [ 0.336916] pci 0000:00:05.0: PME# supported from D0 D3hot D3cold
    [ 0.336970] pci 0000:00:05.0: System wakeup disabled by ACPI
    [ 0.337102] pci 0000:00:10.0: [1022:7814] type 00 class 0x0c0330
    [ 0.337124] pci 0000:00:10.0: reg 0x10: [mem 0xf0348000-0xf0349fff 64bit]
    [ 0.337221] pci 0000:00:10.0: PME# supported from D0 D3hot D3cold
    [ 0.337272] pci 0000:00:10.0: System wakeup disabled by ACPI
    [ 0.337330] pci 0000:00:11.0: [1022:7801] type 00 class 0x010601
    [ 0.337347] pci 0000:00:11.0: reg 0x10: [io 0x4118-0x411f]
    [ 0.337356] pci 0000:00:11.0: reg 0x14: [io 0x4124-0x4127]
    [ 0.337364] pci 0000:00:11.0: reg 0x18: [io 0x4110-0x4117]
    [ 0.337373] pci 0000:00:11.0: reg 0x1c: [io 0x4120-0x4123]
    [ 0.337382] pci 0000:00:11.0: reg 0x20: [io 0x4100-0x410f]
    [ 0.337390] pci 0000:00:11.0: reg 0x24: [mem 0xf034e000-0xf034e7ff]
    [ 0.337516] pci 0000:00:12.0: [1022:7807] type 00 class 0x0c0310
    [ 0.337528] pci 0000:00:12.0: reg 0x10: [mem 0xf034d000-0xf034dfff]
    [ 0.337617] pci 0000:00:12.0: System wakeup disabled by ACPI
    [ 0.337703] pci 0000:00:12.2: [1022:7808] type 00 class 0x0c0320
    [ 0.338061] pci 0000:00:12.2: reg 0x10: [mem 0xf034c000-0xf034c0ff]
    [ 0.340177] pci 0000:00:12.2: supports D1 D2
    [ 0.340179] pci 0000:00:12.2: PME# supported from D0 D1 D2 D3hot D3cold
    [ 0.340285] pci 0000:00:13.0: [1022:7807] type 00 class 0x0c0310
    [ 0.340299] pci 0000:00:13.0: reg 0x10: [mem 0xf034b000-0xf034bfff]
    [ 0.340392] pci 0000:00:13.0: System wakeup disabled by ACPI
    [ 0.340458] pci 0000:00:13.2: [1022:7808] type 00 class 0x0c0320
    [ 0.340887] pci 0000:00:13.2: reg 0x10: [mem 0xf034a000-0xf034a0ff]
    [ 0.343004] pci 0000:00:13.2: supports D1 D2
    [ 0.343006] pci 0000:00:13.2: PME# supported from D0 D1 D2 D3hot D3cold
    [ 0.343116] pci 0000:00:14.0: [1022:780b] type 00 class 0x0c0500
    [ 0.343284] pci 0000:00:14.2: [1022:780d] type 00 class 0x040300
    [ 0.343303] pci 0000:00:14.2: reg 0x10: [mem 0xf0340000-0xf0343fff 64bit]
    [ 0.343360] pci 0000:00:14.2: PME# supported from D0 D3hot D3cold
    [ 0.343454] pci 0000:00:14.3: [1022:780e] type 00 class 0x060100
    [ 0.343595] pci 0000:00:14.4: [1022:780f] type 01 class 0x060401
    [ 0.343659] pci 0000:00:14.4: System wakeup disabled by ACPI
    [ 0.343722] pci 0000:00:18.0: [1022:1400] type 00 class 0x060000
    [ 0.343802] pci 0000:00:18.1: [1022:1401] type 00 class 0x060000
    [ 0.343878] pci 0000:00:18.2: [1022:1402] type 00 class 0x060000
    [ 0.343955] pci 0000:00:18.3: [1022:1403] type 00 class 0x060000
    [ 0.344036] pci 0000:00:18.4: [1022:1404] type 00 class 0x060000
    [ 0.344112] pci 0000:00:18.5: [1022:1405] type 00 class 0x060000
    [ 0.344337] pci 0000:01:00.0: [1002:6663] type 00 class 0x038000
    [ 0.344355] pci 0000:01:00.0: reg 0x10: [mem 0xe0000000-0xefffffff 64bit pref]
    [ 0.344367] pci 0000:01:00.0: reg 0x18: [mem 0xf0200000-0xf023ffff 64bit]
    [ 0.344375] pci 0000:01:00.0: reg 0x20: [io 0x3000-0x30ff]
    [ 0.344388] pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0001ffff pref]
    [ 0.344446] pci 0000:01:00.0: supports D1 D2
    [ 0.344449] pci 0000:01:00.0: PME# supported from D1 D2 D3hot
    [ 0.349478] pci 0000:00:02.0: PCI bridge to [bus 01]
    [ 0.349488] pci 0000:00:02.0: bridge window [io 0x3000-0x3fff]
    [ 0.349493] pci 0000:00:02.0: bridge window [mem 0xf0200000-0xf02fffff]
    [ 0.349498] pci 0000:00:02.0: bridge window [mem 0xe0000000-0xefffffff 64bit pref]
    [ 0.349615] pci 0000:02:00.0: [1969:10a0] type 00 class 0x020000
    [ 0.349642] pci 0000:02:00.0: reg 0x10: [mem 0xf0100000-0xf013ffff 64bit]
    [ 0.349653] pci 0000:02:00.0: reg 0x18: [io 0x2000-0x207f]
    [ 0.349752] pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    [ 0.356148] pci 0000:00:04.0: PCI bridge to [bus 02]
    [ 0.356157] pci 0000:00:04.0: bridge window [io 0x2000-0x2fff]
    [ 0.356162] pci 0000:00:04.0: bridge window [mem 0xf0100000-0xf01fffff]
    [ 0.356295] pci 0000:03:00.0: [168c:0036] type 00 class 0x028000
    [ 0.356334] pci 0000:03:00.0: reg 0x10: [mem 0xf0000000-0xf007ffff 64bit]
    [ 0.356393] pci 0000:03:00.0: reg 0x30: [mem 0xffff0000-0xffffffff pref]
    [ 0.356487] pci 0000:03:00.0: supports D1 D2
    [ 0.356490] pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    [ 0.362836] pci 0000:00:05.0: PCI bridge to [bus 03]
    [ 0.362848] pci 0000:00:05.0: bridge window [mem 0xf0000000-0xf00fffff]
    [ 0.363018] pci 0000:00:14.4: PCI bridge to [bus 04] (subtractive decode)
    [ 0.363032] pci 0000:00:14.4: bridge window [io 0x0000-0x0cf7] (subtractive decode)
    [ 0.363036] pci 0000:00:14.4: bridge window [io 0x0d00-0xffff] (subtractive decode)
    [ 0.363039] pci 0000:00:14.4: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
    [ 0.363041] pci 0000:00:14.4: bridge window [mem 0x000c0000-0x000c3fff] (subtractive decode)
    [ 0.363044] pci 0000:00:14.4: bridge window [mem 0x000c4000-0x000c7fff] (subtractive decode)
    [ 0.363047] pci 0000:00:14.4: bridge window [mem 0x000c8000-0x000cbfff] (subtractive decode)
    [ 0.363049] pci 0000:00:14.4: bridge window [mem 0x000d4000-0x000d7fff] (subtractive decode)
    [ 0.363052] pci 0000:00:14.4: bridge window [mem 0x000d8000-0x000dbfff] (subtractive decode)
    [ 0.363054] pci 0000:00:14.4: bridge window [mem 0x000dc000-0x000dffff] (subtractive decode)
    [ 0.363057] pci 0000:00:14.4: bridge window [mem 0x000e0000-0x000e3fff] (subtractive decode)
    [ 0.363059] pci 0000:00:14.4: bridge window [mem 0x000e4000-0x000e7fff] (subtractive decode)
    [ 0.363062] pci 0000:00:14.4: bridge window [mem 0x000e8000-0x000ebfff] (subtractive decode)
    [ 0.363064] pci 0000:00:14.4: bridge window [mem 0x000ec000-0x000effff] (subtractive decode)
    [ 0.363067] pci 0000:00:14.4: bridge window [mem 0xd0000000-0xf7ffffff] (subtractive decode)
    [ 0.363069] pci 0000:00:14.4: bridge window [mem 0xfc000000-0xfed3ffff] (subtractive decode)
    [ 0.363072] pci 0000:00:14.4: bridge window [mem 0xfed45000-0xffffffff] (subtractive decode)
    [ 0.363129] pci_bus 0000:00: on NUMA node 0
    [ 0.366581] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 10 11 12 14 15) *0
    [ 0.366668] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 10 11 12 14 15) *0
    [ 0.366752] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 10 11 12 14 15) *0
    [ 0.366834] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 10 11 12 14 15) *0
    [ 0.366902] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 10 11 12 14 15) *0
    [ 0.366953] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 10 11 12 14 15) *0
    [ 0.367003] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 10 11 12 14 15) *0
    [ 0.367062] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 10 11 12 14 15) *0
    [ 0.367177] ACPI: Enabled 5 GPEs in block 00 to 1F
    [ 0.367230] ACPI : EC: GPE = 0x3, I/O: command/status = 0x66, data = 0x62
    [ 0.367446] vgaarb: device added: PCI:0000:00:01.0,decodes=io+mem,owns=io+mem,locks=none
    [ 0.367456] vgaarb: loaded
    [ 0.367458] vgaarb: bridge control possible 0000:00:01.0
    [ 0.367505] PCI: Using ACPI for IRQ routing
    [ 0.369255] PCI: pci_cache_line_size set to 64 bytes
    [ 0.369352] e820: reserve RAM buffer [mem 0x0009f400-0x0009ffff]
    [ 0.369355] e820: reserve RAM buffer [mem 0x9555e000-0x97ffffff]
    [ 0.369357] e820: reserve RAM buffer [mem 0x95dbc000-0x97ffffff]
    [ 0.369358] e820: reserve RAM buffer [mem 0x9f8bf000-0x9fffffff]
    [ 0.369360] e820: reserve RAM buffer [mem 0x9fc00000-0x9fffffff]
    [ 0.369516] NetLabel: Initializing
    [ 0.369518] NetLabel: domain hash size = 128
    [ 0.369519] NetLabel: protocols = UNLABELED CIPSOv4
    [ 0.369532] NetLabel: unlabeled traffic allowed by default
    [ 0.369583] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
    [ 0.369588] hpet0: 3 comparators, 32-bit 14.318180 MHz counter
    [ 0.371730] Switched to clocksource hpet
    [ 0.378213] pnp: PnP ACPI init
    [ 0.378231] ACPI: bus type PNP registered
    [ 0.378374] system 00:00: [mem 0xfec00000-0xfec00fff] could not be reserved
    [ 0.378377] system 00:00: [mem 0xfee00000-0xfee00fff] has been reserved
    [ 0.378381] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.378616] pnp 00:01: Plug and Play ACPI device, IDs PNP0b00 (active)
    [ 0.378678] pnp 00:02: Plug and Play ACPI device, IDs MSF0001 PNP0303 (active)
    [ 0.378740] pnp 00:03: Plug and Play ACPI device, IDs ETD061b ETD0001 PNP0f13 (active)
    [ 0.378836] system 00:04: [io 0x0400-0x04cf] could not be reserved
    [ 0.378839] system 00:04: [io 0x04d0-0x04d1] has been reserved
    [ 0.378841] system 00:04: [io 0x04d6] has been reserved
    [ 0.378844] system 00:04: [io 0x0680-0x06ff] has been reserved
    [ 0.378846] system 00:04: [io 0x077a] has been reserved
    [ 0.378848] system 00:04: [io 0x0c00-0x0c01] has been reserved
    [ 0.378850] system 00:04: [io 0x0c14] has been reserved
    [ 0.378853] system 00:04: [io 0x0c50-0x0c52] has been reserved
    [ 0.378855] system 00:04: [io 0x0c6c] has been reserved
    [ 0.378857] system 00:04: [io 0x0c6f] has been reserved
    [ 0.378859] system 00:04: [io 0x0cd0-0x0cdb] has been reserved
    [ 0.378862] system 00:04: [io 0x0840-0x0847] has been reserved
    [ 0.378864] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.378944] system 00:05: [mem 0x000e0000-0x000fffff] could not be reserved
    [ 0.378947] system 00:05: [mem 0xffc00000-0xffffffff] has been reserved
    [ 0.378950] system 00:05: Plug and Play ACPI device, IDs PNP0c01 (active)
    [ 0.382206] pnp: PnP ACPI: found 6 devices
    [ 0.382211] ACPI: bus type PNP unregistered
    [ 0.420296] pci 0000:03:00.0: can't claim BAR 6 [mem 0xffff0000-0xffffffff pref]: no compatible bridge window
    [ 0.420325] pci 0000:01:00.0: BAR 6: assigned [mem 0xf0240000-0xf025ffff pref]
    [ 0.420328] pci 0000:00:02.0: PCI bridge to [bus 01]
    [ 0.420331] pci 0000:00:02.0: bridge window [io 0x3000-0x3fff]
    [ 0.420335] pci 0000:00:02.0: bridge window [mem 0xf0200000-0xf02fffff]
    [ 0.420339] pci 0000:00:02.0: bridge window [mem 0xe0000000-0xefffffff 64bit pref]
    [ 0.420343] pci 0000:00:04.0: PCI bridge to [bus 02]
    [ 0.420346] pci 0000:00:04.0: bridge window [io 0x2000-0x2fff]
    [ 0.420349] pci 0000:00:04.0: bridge window [mem 0xf0100000-0xf01fffff]
    [ 0.420355] pci 0000:03:00.0: BAR 6: assigned [mem 0xf0080000-0xf008ffff pref]
    [ 0.420357] pci 0000:00:05.0: PCI bridge to [bus 03]
    [ 0.420361] pci 0000:00:05.0: bridge window [mem 0xf0000000-0xf00fffff]
    [ 0.420366] pci 0000:00:14.4: PCI bridge to [bus 04]
    [ 0.420377] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    [ 0.420380] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    [ 0.420382] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    [ 0.420384] pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000c3fff]
    [ 0.420386] pci_bus 0000:00: resource 8 [mem 0x000c4000-0x000c7fff]
    [ 0.420388] pci_bus 0000:00: resource 9 [mem 0x000c8000-0x000cbfff]
    [ 0.420391] pci_bus 0000:00: resource 10 [mem 0x000d4000-0x000d7fff]
    [ 0.420393] pci_bus 0000:00: resource 11 [mem 0x000d8000-0x000dbfff]
    [ 0.420395] pci_bus 0000:00: resource 12 [mem 0x000dc000-0x000dffff]
    [ 0.420397] pci_bus 0000:00: resource 13 [mem 0x000e0000-0x000e3fff]
    [ 0.420399] pci_bus 0000:00: resource 14 [mem 0x000e4000-0x000e7fff]
    [ 0.420401] pci_bus 0000:00: resource 15 [mem 0x000e8000-0x000ebfff]
    [ 0.420403] pci_bus 0000:00: resource 16 [mem 0x000ec000-0x000effff]
    [ 0.420405] pci_bus 0000:00: resource 17 [mem 0xd0000000-0xf7ffffff]
    [ 0.420407] pci_bus 0000:00: resource 18 [mem 0xfc000000-0xfed3ffff]
    [ 0.420409] pci_bus 0000:00: resource 19 [mem 0xfed45000-0xffffffff]
    [ 0.420411] pci_bus 0000:01: resource 0 [io 0x3000-0x3fff]
    [ 0.420413] pci_bus 0000:01: resource 1 [mem 0xf0200000-0xf02fffff]
    [ 0.420416] pci_bus 0000:01: resource 2 [mem 0xe0000000-0xefffffff 64bit pref]
    [ 0.420418] pci_bus 0000:02: resource 0 [io 0x2000-0x2fff]
    [ 0.420420] pci_bus 0000:02: resource 1 [mem 0xf0100000-0xf01fffff]
    [ 0.420422] pci_bus 0000:03: resource 1 [mem 0xf0000000-0xf00fffff]
    [ 0.420425] pci_bus 0000:04: resource 4 [io 0x0000-0x0cf7]
    [ 0.420427] pci_bus 0000:04: resource 5 [io 0x0d00-0xffff]
    [ 0.420429] pci_bus 0000:04: resource 6 [mem 0x000a0000-0x000bffff]
    [ 0.420431] pci_bus 0000:04: resource 7 [mem 0x000c0000-0x000c3fff]
    [ 0.420433] pci_bus 0000:04: resource 8 [mem 0x000c4000-0x000c7fff]
    [ 0.420435] pci_bus 0000:04: resource 9 [mem 0x000c8000-0x000cbfff]
    [ 0.420437] pci_bus 0000:04: resource 10 [mem 0x000d4000-0x000d7fff]
    [ 0.420439] pci_bus 0000:04: resource 11 [mem 0x000d8000-0x000dbfff]
    [ 0.420441] pci_bus 0000:04: resource 12 [mem 0x000dc000-0x000dffff]
    [ 0.420443] pci_bus 0000:04: resource 13 [mem 0x000e0000-0x000e3fff]
    [ 0.420445] pci_bus 0000:04: resource 14 [mem 0x000e4000-0x000e7fff]
    [ 0.420447] pci_bus 0000:04: resource 15 [mem 0x000e8000-0x000ebfff]
    [ 0.420449] pci_bus 0000:04: resource 16 [mem 0x000ec000-0x000effff]
    [ 0.420451] pci_bus 0000:04: resource 17 [mem 0xd0000000-0xf7ffffff]
    [ 0.420453] pci_bus 0000:04: resource 18 [mem 0xfc000000-0xfed3ffff]
    [ 0.420455] pci_bus 0000:04: resource 19 [mem 0xfed45000-0xffffffff]
    [ 0.420484] NET: Registered protocol family 2
    [ 0.420674] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
    [ 0.420689] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
    [ 0.420717] TCP: Hash tables configured (established 8192 bind 8192)
    [ 0.420733] TCP: reno registered
    [ 0.420736] UDP hash table entries: 512 (order: 2, 16384 bytes)
    [ 0.420742] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
    [ 0.420798] NET: Registered protocol family 1
    [ 0.420831] pci 0000:00:01.0: Boot video device
    [ 1.038734] pci 0000:02:00.0: set MSI_INTX_DISABLE_BUG flag
    [ 1.038759] PCI: CLS 64 bytes, default 64
    [ 1.038818] Unpacking initramfs...
    [ 1.112669] Freeing initrd memory: 3396K (f74ad000 - f77fe000)
    [ 1.112753] Simple Boot Flag at 0x44 set to 0x1
    [ 1.113077] perf: AMD NB counters detected
    [ 1.113122] LVT offset 0 assigned for vector 0x400
    [ 1.113138] perf: AMD IBS detected (0x000000ff)
    [ 1.113149] apm: BIOS not found.
    [ 1.113200] Scanning for low memory corruption every 60 seconds
    [ 1.113689] futex hash table entries: 1024 (order: 4, 65536 bytes)
    [ 1.114240] HugeTLB registered 4 MB page size, pre-allocated 0 pages
    [ 1.116388] zbud: loaded
    [ 1.116669] VFS: Disk quotas dquot_6.5.2
    [ 1.116720] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    [ 1.116962] msgmni has been set to 1707
    [ 1.117034] Key type big_key registered
    [ 1.117325] bounce: pool size: 64 pages
    [ 1.117370] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    [ 1.117448] io scheduler noop registered
    [ 1.117452] io scheduler deadline registered
    [ 1.117524] io scheduler cfq registered (default)
    [ 1.118017] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    [ 1.118037] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
    [ 1.118114] GHES: HEST is not enabled!
    [ 1.118129] isapnp: Scanning for PnP cards...
    [ 1.513691] isapnp: No Plug & Play device found
    [ 1.513876] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    [ 1.514746] rtc_cmos 00:01: RTC can wake from S4
    [ 1.515007] rtc_cmos 00:01: rtc core: registered rtc_cmos as rtc0
    [ 1.515032] rtc_cmos 00:01: alarms up to one month, 114 bytes nvram, hpet irqs
    [ 1.515076] ledtrig-cpu: registered to indicate activity on CPUs
    [ 1.515246] TCP: cubic registered
    [ 1.515386] NET: Registered protocol family 10
    [ 1.515657] NET: Registered protocol family 17
    [ 1.516096] Using IPI No-Shortcut mode
    [ 1.516269] registered taskstats version 1
    [ 1.516866] Magic number: 14:856:502
    [ 1.516927] rtc_cmos 00:01: setting system clock to 2014-09-21 22:28:27 UTC (1411338507)
    [ 1.517032] PM: Hibernation image not present or could not be loaded.
    [ 1.517281] Freeing unused kernel memory: 568K (c1630000 - c16be000)
    [ 1.517350] Write protecting the kernel text: 4516k
    [ 1.517388] Write protecting the kernel read-only data: 1332k
    [ 1.527560] random: systemd-tmpfile urandom read with 0 bits of entropy available
    [ 1.529660] systemd-udevd[57]: starting version 216
    [ 1.549349] i8042: PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:MSSG] at 0x60,0x64 irq 1,12
    [ 1.568048] ACPI: bus type USB registered
    [ 1.568103] usbcore: registered new interface driver usbfs
    [ 1.568141] usbcore: registered new interface driver hub
    [ 1.568537] SCSI subsystem initialized
    [ 1.574578] usbcore: registered new device driver usb
    [ 1.593572] serio: i8042 KBD port at 0x60,0x64 irq 1
    [ 1.593667] serio: i8042 AUX port at 0x60,0x64 irq 12
    [ 1.593746] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    [ 1.594746] ehci-pci: EHCI PCI platform driver
    [ 1.594935] QUIRK: Enable AMD PLL fix
    [ 1.594970] ehci-pci 0000:00:12.2: EHCI Host Controller
    [ 1.594980] ehci-pci 0000:00:12.2: new USB bus registered, assigned bus number 1
    [ 1.594989] ehci-pci 0000:00:12.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
    [ 1.595002] ehci-pci 0000:00:12.2: debug port 1
    [ 1.595055] ehci-pci 0000:00:12.2: irq 17, io mem 0xf034c000
    [ 1.595121] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    [ 1.595830] ohci-pci: OHCI PCI platform driver
    [ 1.601895] ehci-pci 0000:00:12.2: USB 2.0 started, EHCI 1.00
    [ 1.602284] libata version 3.00 loaded.
    [ 1.602306] hub 1-0:1.0: USB hub found
    [ 1.602325] hub 1-0:1.0: 5 ports detected
    [ 1.602883] ehci-pci 0000:00:13.2: EHCI Host Controller
    [ 1.602893] ehci-pci 0000:00:13.2: new USB bus registered, assigned bus number 2
    [ 1.602899] ehci-pci 0000:00:13.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
    [ 1.602912] ehci-pci 0000:00:13.2: debug port 1
    [ 1.602945] ehci-pci 0000:00:13.2: irq 17, io mem 0xf034a000
    [ 1.612011] ehci-pci 0000:00:13.2: USB 2.0 started, EHCI 1.00
    [ 1.612308] hub 2-0:1.0: USB hub found
    [ 1.612317] hub 2-0:1.0: 5 ports detected
    [ 1.612814] xhci_hcd 0000:00:10.0: xHCI Host Controller
    [ 1.612828] xhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 3
    [ 1.613042] xhci_hcd 0000:00:10.0: irq 40 for MSI/MSI-X
    [ 1.613048] xhci_hcd 0000:00:10.0: irq 41 for MSI/MSI-X
    [ 1.613052] xhci_hcd 0000:00:10.0: irq 42 for MSI/MSI-X
    [ 1.613056] xhci_hcd 0000:00:10.0: irq 43 for MSI/MSI-X
    [ 1.613060] xhci_hcd 0000:00:10.0: irq 44 for MSI/MSI-X
    [ 1.613374] hub 3-0:1.0: USB hub found
    [ 1.613388] hub 3-0:1.0: 2 ports detected
    [ 1.613609] xhci_hcd 0000:00:10.0: xHCI Host Controller
    [ 1.613614] xhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 4
    [ 1.616754] hub 4-0:1.0: USB hub found
    [ 1.616768] hub 4-0:1.0: 2 ports detected
    [ 1.617093] ohci-pci 0000:00:12.0: OHCI PCI host controller
    [ 1.617107] ohci-pci 0000:00:12.0: new USB bus registered, assigned bus number 5
    [ 1.617152] ohci-pci 0000:00:12.0: irq 18, io mem 0xf034d000
    [ 1.645460] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
    [ 1.673072] hub 5-0:1.0: USB hub found
    [ 1.673098] hub 5-0:1.0: 5 ports detected
    [ 1.673547] ohci-pci 0000:00:13.0: OHCI PCI host controller
    [ 1.673554] ohci-pci 0000:00:13.0: new USB bus registered, assigned bus number 6
    [ 1.673585] ohci-pci 0000:00:13.0: irq 18, io mem 0xf034b000
    [ 1.729803] hub 6-0:1.0: USB hub found
    [ 1.729831] hub 6-0:1.0: 5 ports detected
    [ 1.730166] ahci 0000:00:11.0: version 3.0
    [ 1.730351] ahci 0000:00:11.0: irq 45 for MSI/MSI-X
    [ 1.730404] ahci 0000:00:11.0: AHCI 0001.0300 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
    [ 1.730409] ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part
    [ 1.731131] scsi0 : ahci
    [ 1.731321] scsi1 : ahci
    [ 1.731403] ata1: SATA max UDMA/133 abar m2048@0xf034e000 port 0xf034e100 irq 45
    [ 1.731407] ata2: SATA max UDMA/133 abar m2048@0xf034e000 port 0xf034e180 irq 45
    [ 1.962152] usb 1-4: new high-speed USB device number 3 using ehci-pci
    [ 2.115336] tsc: Refined TSC clocksource calibration: 1896.456 MHz
    [ 2.215395] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    [ 2.215424] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [ 2.216948] ata2.00: ATAPI: MATSHITADVD-RAM UJ8C2, 1.00, max UDMA/133
    [ 2.218438] ata2.00: configured for UDMA/133
    [ 2.274381] ata1.00: ATA-9: ST1000LM014-1EJ164, LVD3, max UDMA/133
    [ 2.274386] ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
    [ 2.318651] ata1.00: configured for UDMA/133
    [ 2.318844] scsi 0:0:0:0: Direct-Access ATA ST1000LM014-1EJ1 LVD3 PQ: 0 ANSI: 5
    [ 2.320735] scsi 1:0:0:0: CD-ROM MATSHITA DVD-RAM UJ8C2 1.00 PQ: 0 ANSI: 5
    [ 2.337991] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
    [ 2.337996] sd 0:0:0:0: [sda] 4096-byte physical blocks
    [ 2.338079] sd 0:0:0:0: [sda] Write Protect is off
    [ 2.338085] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
    [ 2.338151] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 2.338885] sda: sda1 sda2 sda3
    [ 2.339411] sd 0:0:0:0: [sda] Attached SCSI disk
    [ 2.348995] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
    [ 2.348999] cdrom: Uniform CD-ROM driver Revision: 3.20
    [ 2.349240] sr 1:0:0:0: Attached scsi CD-ROM sr0
    [ 2.395434] usb 3-1: new low-speed USB device number 2 using xhci_hcd
    [ 2.438944] ata1.00: exception Emask 0x0 SAct 0x80 SErr 0x0 action 0x6
    [ 2.438989] ata1.00: irq_stat 0x40000008
    [ 2.439030] ata1.00: failed command: READ FPDMA QUEUED
    [ 2.439074] ata1.00: cmd 60/08:38:18:08:00/00:00:00:00:00/40 tag 7 ncq 4096 in
    res 41/84:08:18:08:00/00:00:00:00:00/00 Emask 0x410 (ATA bus error) <F>
    [ 2.439127] ata1.00: status: { DRDY ERR }
    [ 2.439166] ata1.00: error: { ICRC ABRT }
    [ 2.439207] ata1: hard resetting link
    [ 2.555934] usb 3-1: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
    [ 2.555943] usb 3-1: ep 0x82 - rounding interval to 64 microframes, ep desc says 80 microframes
    [ 2.559635] hidraw: raw HID events driver (C) Jiri Kosina
    [ 2.586950] usbcore: registered new interface driver usbhid
    [ 2.586953] usbhid: USB HID core driver
    [ 2.588065] input: Microsoft Comfort Curve Keyboard 3000 as /devices/pci0000:00/0000:00:10.0/usb3/3-1/3-1:1.0/0003:045E:0780.0001/input/input2
    [ 2.588153] hid-generic 0003:045E:0780.0001: input,hidraw0: USB HID v1.11 Keyboard [Microsoft Comfort Curve Keyboard 3000] on usb-0000:00:10.0-1/input0
    [ 2.594030] input: Microsoft Comfort Curve Keyboard 3000 as /devices/pci0000:00/0000:00:10.0/usb3/3-1/3-1:1.1/0003:045E:0780.0002/input/input3
    [ 2.594150] hid-generic 0003:045E:0780.0002: input,hidraw1: USB HID v1.11 Device [Microsoft Comfort Curve Keyboard 3000] on usb-0000:00:10.0-1/input1
    [ 2.662213] usb 2-2: new high-speed USB device number 2 using ehci-pci
    [ 2.915446] usb 5-1: new low-speed USB device number 2 using ohci-pci
    [ 2.925441] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [ 3.039928] ata1.00: configured for UDMA/133
    [ 3.039955] ata1: EH complete
    [ 3.081259] input: USB Mouse as /devices/pci0000:00/0000:00:12.0/usb5/5-1/5-1:1.0/0003:05E3:1205.0003/input/input4
    [ 3.081368] hid-generic 0003:05E3:1205.0003: input,hidraw2: USB HID v1.10 Mouse [USB Mouse ] on usb-0000:00:12.0-1/input0
    [ 3.089081] ata1.00: exception Emask 0x0 SAct 0x40000 SErr 0x0 action 0x6
    [ 3.089128] ata1.00: irq_stat 0x40000008
    [ 3.089168] ata1.00: failed command: READ FPDMA QUEUED
    [ 3.089212] ata1.00: cmd 60/08:90:78:28:03/00:00:00:00:00/40 tag 18 ncq 4096 in
    res 41/84:08:7c:28:03/00:00:00:00:00/00 Emask 0x410 (ATA bus error) <F>
    [ 3.089265] ata1.00: status: { DRDY ERR }
    [ 3.089304] ata1.00: error: { ICRC ABRT }
    [ 3.089346] ata1: hard resetting link
    [ 3.115583] Switched to clocksource tsc
    [ 3.575598] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [ 3.694602] ata1.00: configured for UDMA/133
    [ 3.694621] ata1: EH complete
    [ 3.809120] ata1.00: exception Emask 0x0 SAct 0x1e00 SErr 0x0 action 0x6
    [ 3.809168] ata1.00: irq_stat 0x40000008
    [ 3.809208] ata1.00: failed command: READ FPDMA QUEUED
    [ 3.809251] ata1.00: cmd 60/08:48:10:08:00/00:00:00:00:00/40 tag 9 ncq 4096 in
    res 41/84:08:10:08:00/00:00:00:00:00/00 Emask 0x410 (ATA bus error) <F>
    [ 3.809305] ata1.00: status: { DRDY ERR }
    [ 3.809343] ata1.00: error: { ICRC ABRT }
    [ 3.809385] ata1: hard resetting link
    [ 4.295566] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    [ 4.404835] ata1.00: configured for UDMA/133
    [ 4.404858] ata1: EH complete
    [ 4.453715] ata1.00: exception Emask 0x0 SAct 0x1fe000 SErr 0x0 action 0x0
    [ 4.453760] ata1.00: irq_stat 0x40000008
    [ 4.453799] ata1.00: failed command: READ FPDMA QUEUED
    [ 4.453842] ata1.00: cmd 60/80:68:80:08:00/01:00:00:00:00/40 tag 13 ncq 196608 in
    res 41/40:80:b8:09:00/00:01:00:00:00/00 Emask 0x409 (media error) <F>
    [ 4.453894] ata1.00: status: { DRDY ERR }
    [ 4.453932] ata1.00: error: { UNC }
    [ 4.637639] ata1.00: configured for UDMA/133
    [ 4.637688] sd 0:0:0:0: [sda] Unhandled sense code
    [ 4.637691] sd 0:0:0:0: [sda]
    [ 4.637693] Result: hostbyte=0x00 driverbyte=0x08
    [ 4.637695] sd 0:0:0:0: [sda]
    [ 4.637697] Sense Key : 0x3 [current] [descriptor]
    [ 4.637700] Descriptor sense data with sense descriptors (in hex):
    [ 4.637702] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 4.637710] 00 00 09 b8
    [ 4.637714] sd 0:0:0:0: [sda]
    [ 4.637716] ASC=0x11 ASCQ=0x4
    [ 4.637718] sd 0:0:0:0: [sda] CDB:
    [ 4.637719] cdb[0]=0x28: 28 00 00 00 08 80 00 01 80 00
    [ 4.637727] end_request: I/O error, dev sda, sector 2488
    [ 4.637786] Buffer I/O error on device sda1, logical block 55
    [ 4.637826] Buffer I/O error on device sda1, logical block 56
    [ 4.637866] Buffer I/O error on device sda1, logical block 57
    [ 4.637905] Buffer I/O error on device sda1, logical block 58
    [ 4.637945] Buffer I/O error on device sda1, logical block 59
    [ 4.637984] Buffer I/O error on device sda1, logical block 60
    [ 4.638024] Buffer I/O error on device sda1, logical block 61
    [ 4.638063] Buffer I/O error on device sda1, logical block 62
    [ 4.638105] Buffer I/O error on device sda1, logical block 63
    [ 4.638188] ata1: EH complete
    [ 4.879313] ata1: limiting SATA link speed to 3.0 Gbps
    [ 4.879320] ata1.00: exception Emask 0x0 SAct 0x4000 SErr 0x0 action 0x6
    [ 4.879364] ata1.00: irq_stat 0x40000008
    [ 4.879404] ata1.00: failed command: READ FPDMA QUEUED
    [ 4.879448] ata1.00: cmd 60/08:70:50:2b:03/00:00:00:00:00/40 tag 14 ncq 4096 in
    res 41/84:08:50:2b:03/00:00:00:00:00/00 Emask 0x410 (ATA bus error) <F>
    [ 4.879502] ata1.00: status: { DRDY ERR }
    [ 4.879540] ata1.00: error: { ICRC ABRT }
    [ 4.879583] ata1: hard resetting link
    [ 5.365653] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
    [ 5.469816] ata1.00: configured for UDMA/133
    [ 5.469845] ata1: EH complete
    [ 5.582799] ata1.00: exception Emask 0x0 SAct 0x80 SErr 0x0 action 0x6
    [ 5.582859] ata1.00: irq_stat 0x40000008
    [ 5.582900] ata1.00: failed command: READ FPDMA QUEUED
    [ 5.582943] ata1.00: cmd 60/08:38:18:0b:00/00:00:00:00:00/40 tag 7 ncq 4096 in
    res 41/84:08:19:0b:00/00:00:00:00:00/00 Emask 0x410 (ATA bus error) <F>
    [ 5.582997] ata1.00: status: { DRDY ERR }
    [ 5.583036] ata1.00: error: { ICRC ABRT }
    [ 5.583078] ata1: hard resetting link
    [ 6.069015] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
    [ 6.191135] ata1.00: configured for UDMA/133
    [ 6.191166] ata1: EH complete
    [ 6.256026] ata1.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x6
    [ 6.256073] ata1.00: irq_stat 0x40000008
    [ 6.256114] ata1.00: failed command: READ FPDMA QUEUED
    [ 6.256158] ata1.00: cmd 60/08:78:00:38:03/00:00:00:00:00/40 tag 15 ncq 4096 in
    res 41/84:08:02:38:03/00:00:00:00:00/00 Emask 0x410 (ATA bus error) <F>
    [ 6.256212] ata1.00: status: { DRDY ERR }
    [ 6.256250] ata1.00: error: { ICRC ABRT }
    [ 6.256292] ata1: hard resetting link
    [ 6.742436] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
    [ 6.845773] ata1.00: configured for UDMA/133
    [ 6.845806] ata1: EH complete
    [ 6.986177] ata1.00: exception Emask 0x0 SAct 0x80000 SErr 0x0 action 0x6
    [ 6.986223] ata1.00: irq_stat 0x40000008
    [ 6.986264] ata1.00: failed command: READ FPDMA QUEUED
    [ 6.986308] ata1.00: cmd 60/08:98:b0:f8:b5/00:00:58:00:00/40 tag 19 ncq 4096 in
    res 41/84:08:b0:f8:b5/00:00:58:00:00/00 Emask 0x410 (ATA bus error) <F>
    [ 6.986360] ata1.00: status: { DRDY ERR }
    [ 6.986399] ata1.00: error: { ICRC ABRT }
    [ 6.986440] ata1: hard resetting link
    [ 7.472592] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
    [ 7.578097] ata1.00: configured for UDMA/133
    [ 7.578124] ata1: EH complete
    [ 7.587216] random: nonblocking pool is initialized
    [ 7.602800] ata1: limiting SATA link speed to 1.5 Gbps
    [ 7.602806] ata1.00: exception Emask 0x0 SAct 0x800000 SErr 0x0 action 0x6
    [ 7.602850] ata1.00: irq_stat 0x40000008
    [ 7.602889] ata1.00: failed command: READ FPDMA QUEUED
    [ 7.602931] ata1.00: cmd 60/08:b8:c8:58:b6/00:00:58:00:00/40 tag 23 ncq 4096 in
    res 41/84:08:cc:58:b6/00:00:58:00:00/00 Emask 0x410 (ATA bus error) <F>
    [ 7.602982] ata1.00: status: { DRDY ERR }
    [ 7.603020] ata1.00: error: { ICRC ABRT }
    [ 7.603061] ata1: hard resetting link
    [ 8.089174] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 8.188490] ata1.00: configured for UDMA/133
    [ 8.188517] ata1: EH complete
    [ 8.216300] ata1.00: exception Emask 0x0 SAct 0x2000000 SErr 0x0 action 0x6
    [ 8.216361] ata1.00: irq_stat 0x40000008
    [ 8.216402] ata1.00: failed command: READ FPDMA QUEUED
    [ 8.216446] ata1.00: cmd 60/08:c8:d0:78:b6/00:00:58:00:00/40 tag 25 ncq 4096 in
    res 41/84:08:d0:78:b6/00:00:58:00:00/00 Emask 0x410 (ATA bus error) <F>
    [ 8.216500] ata1.00: status: { DRDY ERR }
    [ 8.216539] ata1.00: error: { ICRC ABRT }
    [ 8.216581] ata1: hard resetting link
    [ 8.702603] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 8.809726] ata1.00: configured for UDMA/133
    [ 8.809758] ata1: EH complete
    [ 8.836250] ata1.00: exception Emask 0x0 SAct 0x8000000 SErr 0x0 action 0x6
    [ 8.836295] ata1.00: irq_stat 0x40000008
    [ 8.836335] ata1.00: failed command: READ FPDMA QUEUED
    [ 8.836377] ata1.00: cmd 60/08:d8:d8:98:b6/00:00:58:00:00/40 tag 27 ncq 4096 in
    res 41/84:08:d8:98:b6/00:00:58:00:00/00 Emask 0x410 (ATA bus error) <F>
    [ 8.836429] ata1.00: status: { DRDY ERR }
    [ 8.836467] ata1.00: error: { ICRC ABRT }
    [ 8.836507] ata1: hard resetting link
    [ 9.322654] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 9.430994] ata1.00: configured for UDMA/133
    [ 9.431018] ata1: EH complete
    [ 9.664088] EXT4-fs (sda3): mounting ext3 file system using the ext4 subsystem
    [ 9.686362] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
    [ 9.837482] ata1.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x6
    [ 9.837542] ata1.00: irq_stat 0x40000008
    [ 9.837583] ata1.00: failed command: READ FPDMA QUEUED
    [ 9.837626] ata1.00: cmd 60/08:28:20:08:89/00:00:5e:00:00/40 tag 5 ncq 4096 in
    res 41/84:08:20:08:89/00:00:5e:00:00/00 Emask 0x410 (ATA bus error) <F>
    [ 9.837680] ata1.00: status: { DRDY ERR }
    [ 9.837719] ata1.00: error: { ICRC ABRT }
    [ 9.837761] ata1: hard resetting link
    [ 10.322740] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 10.515900] ata1.00: configured for UDMA/133
    [ 10.515972] sd 0:0:0:0: [sda]
    [ 10.515975] Result: hostbyte=0x00 driverbyte=0x08
    [ 10.515978] sd 0:0:0:0: [sda]
    [ 10.515979] Sense Key : 0xb [current] [descriptor]
    [ 10.515983] Descriptor sense data with sense descriptors (in hex):
    [ 10.515984] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 10.515992] 5e 89 08 20
    [ 10.515997] sd 0:0:0:0: [sda]
    [ 10.515998] ASC=0x47 ASCQ=0x0
    [ 10.516001] sd 0:0:0:0: [sda] CDB:
    [ 10.516002] cdb[0]=0x28: 28 00 5e 89 08 20 00 00 08 00
    [ 10.516010] end_request: I/O error, dev sda, sector 1586038816
    [ 10.516148] ata1: EH complete
    [ 10.529733] ata1.00: limiting speed to UDMA/100:PIO4
    [ 10.529740] ata1.00: exception Emask 0x0 SAct 0x7fffff1f SErr 0x0 action 0x6
    [ 10.529786] ata1.00: irq_stat 0x40000008
    [ 10.529826] ata1.00: failed command: READ FPDMA QUEUED
    [ 10.529870] ata1.00: cmd 60/08:40:d0:08:89/00:00:5e:00:00/40 tag 8 ncq 4096 in
    res 41/84:08:d4:08:89/00:00:5e:00:00/00 Emask 0x410 (ATA bus error) <F>
    [ 10.529924] ata1.00: status: { DRDY ERR }
    [ 10.529962] ata1.00: error: { ICRC ABRT }
    [ 10.530004] ata1: hard resetting link
    [ 11.016129] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 11.139673] ata1.00: configured for UDMA/100
    [ 11.139723] sd 0:0:0:0: [sda]
    [ 11.139725] Result: hostbyte=0x00 driverbyte=0x08
    [ 11.139728] sd 0:0:0:0: [sda]
    [ 11.139730] Sense Key : 0xb [current] [descriptor]
    [ 11.139733] Descriptor sense data with sense descriptors (in hex):
    [ 11.139735] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 11.139743] 5e 89 08 d4
    [ 11.139747] sd 0:0:0:0: [sda]
    [ 11.139749] ASC=0x47 ASCQ=0x0
    [ 11.139751] sd 0:0:0:0: [sda] CDB:
    [ 11.139753] cdb[0]=0x28: 28 00 5e 89 08 d0 00 00 08 00
    [ 11.139761] end_request: I/O error, dev sda, sector 1586038992
    [ 11.139889] ata1: EH complete
    [ 11.153122] ata1.00: exception Emask 0x0 SAct 0x7fffffc1 SErr 0x0 action 0x6
    [ 11.153169] ata1.00: irq_stat 0x40000008
    [ 11.153210] ata1.00: failed command: READ FPDMA QUEUED
    [ 11.153253] ata1.00: cmd 60/08:30:28:08:89/00:00:5e:00:00/40 tag 6 ncq 4096 in
    res 41/84:08:28:08:89/00:00:5e:00:00/00 Emask 0x410 (ATA bus error) <F>
    [ 11.153306] ata1.00: status: { DRDY ERR }
    [ 11.153345] ata1.00: error: { ICRC ABRT }
    [ 11.153386] ata1: hard resetting link
    [ 11.639485] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 11.749884] ata1.00: configured for UDMA/100
    [ 11.749918] sd 0:0:0:0: [sda]
    [ 11.749920] Result: hostbyte=0x00 driverbyte=0x08
    [ 11.749923] sd 0:0:0:0: [sda]
    [ 11.749925] Sense Key : 0xb [current] [descriptor]
    [ 11.749928] Descriptor sense data with sense descriptors (in hex):
    [ 11.749930] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 11.749938] 5e 89 08 28
    [ 11.749942] sd 0:0:0:0: [sda]
    [ 11.749944] ASC=0x47 ASCQ=0x0
    [ 11.749946] sd 0:0:0:0: [sda] CDB:
    [ 11.749948] cdb[0]=0x28: 28 00 5e 89 08 28 00 00 08 00
    [ 11.749956] end_request: I/O error, dev sda, sector 1586038824
    [ 11.750093] ata1: EH complete
    [ 11.763159] ata1.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x6
    [ 11.763206] ata1.00: irq_stat 0x40000008
    [ 11.763247] ata1.00: failed command: READ FPDMA QUEUED
    [ 11.763290] ata1.00: cmd 60/08:28:c8:08:89/00:00:5e:00:00/40 tag 5 ncq 4096 in
    res 41/84:08:c8:08:89/00:00:5e:00:00/00 Emask 0x410 (ATA bus error) <F>
    [ 11.763343] ata1.00: status: { DRDY ERR }
    [ 11.763382] ata1.00: error: { ICRC ABRT }
    [ 11.763424] ata1: hard resetting link
    [ 12.249523] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 12.360321] ata1.00: configured for UDMA/100
    [ 12.360370] sd 0:0:0:0: [sda]
    [ 12.360372] Result: hostbyte=0x00 driverbyte=0x08
    [ 12.360375] sd 0:0:0:0: [sda]
    [ 12.360377] Sense Key : 0xb [current] [descriptor]
    [ 12.360380] Descriptor sense data with sense descriptors (in hex):
    [ 12.360381] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 12.360390] 5e 89 08 c8
    [ 12.360394] sd 0:0:0:0: [sda]
    [ 12.360395] ASC=0x47 ASCQ=0x0
    [ 12.360398] sd 0:0:0:0: [sda] CDB:
    [ 12.360399] cdb[0]=0x28: 28 00 5e 89 08 c8 00 00 08 00
    [ 12.360407] end_request: I/O error, dev sda, sector 1586038984
    [ 12.360543] ata1: EH complete
    [ 12.369958] ata1.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x6
    [ 12.370005] ata1.00: irq_stat 0x40000008
    [ 12.370045] ata1.00: failed command: READ FPDMA QUEUED
    [ 12.370090] ata1.00: cmd 60/08:28:38:08:89/00:00:63:00:00/40 tag 5 ncq 4096 in
    res 41/84:08:3a:08:89/00:00:63:00:00/00 Emask 0x410 (ATA bus error) <F>
    [ 12.370143] ata1.00: status: { DRDY ERR }
    [ 12.370182] ata1.00: error: { ICRC ABRT }
    [ 12.370224] ata1: hard resetting link
    [ 12.856285] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 12.959379] ata1.00: configured for UDMA/100
    [ 12.959426] sd 0:0:0:0: [sda]
    [ 12.959429] Result: hostbyte=0x00 driverbyte=0x08
    [ 12.959432] sd 0:0:0:0: [sda]
    [ 12.959433] Sense Key : 0xb [current] [descriptor]
    [ 12.959437] Descriptor sense data with sense descriptors (in hex):
    [ 12.959438] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 12.959447] 63 89 08 3a
    [ 12.959462] sd 0:0:0:0: [sda]
    [ 12.959464] ASC=0x47 ASCQ=0x0
    [ 12.959466] sd 0:0:0:0: [sda] CDB:
    [ 12.959468] cdb[0]=0x28: 28 00 63 89 08 38 00 00 08 00
    [ 12.959476] end_request: I/O error, dev sda, sector 1669924920
    [ 12.959616] ata1: EH complete
    [ 12.973195] ata1.00: limiting speed to UDMA/33:PIO4
    [ 12.973202] ata1.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x6
    [ 12.973247] ata1.00: irq_stat 0x40000008
    [ 12.973287] ata1.00: failed command: READ FPDMA QUEUED
    [ 12.973331] ata1.00: cmd 60/08:30:c0:08:89/00:00:5e:00:00/40 tag 6 ncq 4096 in
    res 41/84:08:c0:08:89/00:00:5e:00:00/00 Emask 0x410 (ATA bus error) <F>
    [ 12.973384] ata1.00: status: { DRDY ERR }
    [ 12.973423] ata1.00: error: { ICRC ABRT }
    [ 12.973464] ata1: hard resetting link
    [ 13.459735] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 13.569691] ata1.00: configured for UDMA/33
    [ 13.569750] sd 0:0:0:0: [sda]
    [ 13.569753] Result: hostbyte=0x00 driverbyte=0x08
    [ 13.569755] sd 0:0:0:0: [sda]
    [ 13.569757] Sense Key : 0xb [current] [descriptor]
    [ 13.569761] Descriptor sense data with sense descriptors (in hex):
    [ 13.569763] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 13.569771] 5e 89 08 c0
    [ 13.569775] sd 0:0:0:0: [sda]
    [ 13.569777] ASC=0x47 ASCQ=0x0
    [ 13.569779] sd 0:0:0:0: [sda] CDB:
    [ 13.569781] cdb[0]=0x28: 28 00 5e 89 08 c0 00 00 08 00
    [ 13.569789] end_request: I/O error, dev sda, sector 1586038976
    [ 13.569933] ata1: EH complete
    [ 13.583315] ata1.00: exception Emask 0x0 SAct 0x7fffff9f SErr 0x0 action 0x6
    [ 13.583360] ata1.00: irq_stat 0x40000008
    [ 13.583399] ata1.00: failed command: READ FPDMA QUEUED
    [ 13.583441] ata1.00: cmd 60/08:38:30:08:89/00:00:63:00:00/40 tag 7 ncq 4096 in
    res 41/84:08:30:08:89/00:00:63:00:00/00 Emask 0x410 (ATA bus error) <F>
    [ 13.585478] ata1.00: status: { DRDY ERR }
    [ 13.585516] ata1.00: error: { ICRC ABRT }
    [ 13.585558] ata1: hard resetting link
    [ 14.069688] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 14.180020] ata1.00: configured for UDMA/33
    [ 14.180069] sd 0:0:0:0: [sda]
    [ 14.180072] Result: hostbyte=0x00 driverbyte=0x08
    [ 14.180074] sd 0:0:0:0: [sda]
    [ 14.180076] Sense Key : 0xb [current] [descriptor]
    [ 14.180079] Descriptor sense data with sense descriptors (in hex):
    [ 14.180081] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 14.180089] 63 89 08 30
    [ 14.180094] sd 0:0:0:0: [sda]
    [ 14.180095] ASC=0x47 ASCQ=0x0
    [ 14.180098] sd 0:0:0:0: [sda] CDB:
    [ 14.180099] cdb[0]=0x28: 28 00 63 89 08 30 00 00 08 00
    [ 14.180108] end_request: I/O error, dev sda, sector 1669924912
    [ 14.180245] ata1: EH complete
    [ 14.190091] ata1.00: exception Emask 0x0 SAct 0x7fffffe3 SErr 0x0 action 0x6
    [ 14.190153] ata1.00: irq_stat 0x40000008
    [ 14.190193] ata1.00: failed command: READ FPDMA QUEUED
    [ 14.190237] ata1.00: cmd 60/a8:28:70:08:89/00:00:63:00:00/40 tag 5 ncq 86016 in
    res 41/84:a8:80:08:89/00:00:63:00:00/00 Emask 0x410 (ATA bus error) <F>
    [ 14.190290] ata1.00: status: { DRDY ERR }
    [ 14.190328] ata1.00: error: { ICRC ABRT }
    [ 14.190371] ata1: hard resetting link
    [ 14.676439] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 14.779168] ata1.00: configured for UDMA/33
    [ 14.779214] sd 0:0:0:0: [sda]
    [ 14.779216] Result: hostbyte=0x00 driverbyte=0x08
    [ 14.779218] sd 0:0:0:0: [sda]
    [ 14.779220] Sense Key : 0xb [current] [descriptor]
    [ 14.779223] Descriptor sense data with sense descriptors (in hex):
    [ 14.779225] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 14.779233] 63 89 08 80
    [ 14.779237] sd 0:0:0:0: [sda]
    [ 14.779239] ASC=0x47 ASCQ=0x0
    [ 14.779241] sd 0:0:0:0: [sda] CDB:
    [ 14.779243] cdb[0]=0x28: 28 00 63 89 08 70 00 00 a8 00
    [ 14.779251] end_request: I/O error, dev sda, sector 1669924976
    [ 14.779391] ata1: EH complete
    [ 14.793467] ata1.00: exception Emask 0x0 SAct 0x3fffffe0 SErr 0x0 action 0x6
    [ 14.793513] ata1.00: irq_stat 0x40000008
    [ 14.793554] ata1.00: failed command: READ FPDMA QUEUED
    [ 14.793597] ata1.00: cmd 60/08:28:28:08:89/00:00:63:00:00/40 tag 5 ncq 4096 in
    res 41/84:08:28:08:89/00:00:63:00:00/00 Emask 0x410 (ATA bus error) <F>
    [ 14.793651] ata1.00: status: { DRDY ERR }
    [ 14.793690] ata1.00: error: { ICRC ABRT }
    [ 14.793733] ata1: hard resetting link
    [ 15.279789] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 15.378218] ata1.00: configured for UDMA/33
    [ 15.378240] sd 0:0:0:0: [sda]
    [ 15.378243] Result: hostbyte=0x00 driverbyte=0x08
    [ 15.378245] sd 0:0:0:0: [sda]
    [ 15.378247] Sense Key : 0xb [current] [descriptor]
    [ 15.378250] Descriptor sense data with sense descriptors (in hex):
    [ 15.378252] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 15.378260] 63 89 08 28
    [ 15.378264] sd 0:0:0:0: [sda]
    [ 15.378266] ASC=0x47 ASCQ=0x0
    [ 15.378268] sd 0:0:0:0: [sda] CDB:
    [ 15.378269] cdb[0]=0x28: 28 00 63 89 08 28 00 00 08 00
    [ 15.378277] end_request: I/O error, dev sda, sector 1669924904
    [ 15.378427] ata1: EH complete
    [ 15.390101] ata1.00: exception Emask 0x0 SAct 0x7fffff SErr 0x0 action 0x6
    [ 15.390148] ata1.00: irq_stat 0x40000008
    [ 15.390188] ata1.00: failed command: READ FPDMA QUEUED
    [ 15.390232] ata1.00: cmd 60/08:00:10:08:89/00:00:63:00:00/40 tag 0 ncq 4096 in
    res 41/84:08:10:08:89/00:00:63:00:00/00 Emask 0x410 (ATA bus error) <F>
    [ 15.390285] ata1.00: status: { DRDY ERR }
    [ 15.390324] ata1.00: error: { ICRC ABRT }
    [ 15.390366] ata1: hard resetting link
    [ 15.876541] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 15.977410] ata1.00: configured for UDMA/33
    [ 15.977500] ata1: EH complete
    [ 15.986870] ata1.00: exception Emask 0x0 SAct 0x7f807fff SErr 0x0 action 0x6
    [ 15.986916] ata1.00: irq_stat 0x40000008
    [ 15.986957] ata1.00: failed command: READ FPDMA QUEUED
    [ 15.987000] ata1.00: cmd 60/08:b8:20:08:89/00:00:63:00:00/40 tag 23 ncq 4096 in
    res 41/84:08:20:08:89/00:00:63:00:00/00 Emask 0x410 (ATA bus error) <F>
    [ 15.987054] ata1.00: status: { DRDY ERR }
    [ 15.987093] ata1.00: error: { ICRC ABRT }
    [ 15.987135] ata1: hard resetting link
    [ 16.473350] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 16.576437] ata1.00: configured for UDMA/33
    [ 16.576509] sd 0:0:0:0: [sda]
    [ 16.576511] Result: hostbyte=0x00 driverbyte=0x08
    [ 16.576514] sd 0:0:0:0: [sda]
    [ 16.576516] Sense Key : 0xb [current] [descriptor]
    [ 16.576519] Descriptor sense data with sense descriptors (in hex):
    [ 16.576520] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 16.576529] 63 89 08 20
    [ 16.576533] sd 0:0:0:0: [sda]
    [ 16.576534] ASC=0x47 ASCQ=0x0
    [ 16.576537] sd 0:0:0:0: [sda] CDB:
    [ 16.576538] cdb[0]=0x28: 28 00 63 89 08 20 00 00 08 00
    [ 16.576546] end_request: I/O error, dev sda, sector 1669924896
    [ 16.576642] ata1: EH complete
    [ 16.586801] ata1.00: exception Emask 0x0 SAct 0x7fff803f SErr 0x0 action 0x6
    [ 16.586847] ata1.00: irq_stat 0x40000008
    [ 16.586886] ata1.00: failed command: READ FPDMA QUEUED
    [ 16.586928] ata1.00: cmd 60/08:78:50:08:89/00:00:5e:00:00/40 tag 15 ncq 4096 in
    res 41/84:08:54:08:89/00:00:5e:00:00/00 Emask 0x410 (ATA bus error) <F>
    [ 16.586980] ata1.00: status: { DRDY ERR }
    [ 16.587018] ata1.00: error: { ICRC ABRT }
    [ 16.587058] ata1: hard resetting link
    [ 17.073307] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 17.175907] ata1.00: configured for UDMA/33
    [ 17.175963] sd 0:0:0:0: [sda]
    [ 17.175965] Result: hostbyte=0x00 driverbyte=0x08
    [ 17.175968] sd 0:0:0:0: [sda]
    [ 17.175970] Sense Key : 0xb [current] [descriptor]
    [ 17.175973] Descriptor sense data with sense descriptors (in hex):
    [ 17.175974] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    [ 17.175983] 5e 89 08 54
    [ 17.175987] sd

    I have only Arch installed, 64 bit, UEFI boot.
    The things got worse for me. Today I barely managed to boot the laptop. It was throwing a lot of errors at me:
    Sep 24 06:13:59 kernel: ata6.00: irq_stat 0x40000008
    Sep 24 06:13:59 kernel: ata6.00: failed command: READ FPDMA QUEUED
    Sep 24 06:13:59 kernel: ata6.00: cmd 60/a8:00:40:0e:00/00:00:00:00:00/40 tag 0 ncq 86016 in
    res 41/84:a8:87:0e:00/00:00:00:00:00/00 Emask 0x410 (ATA bus error) <F>
    Sep 24 06:13:59 kernel: ata6.00: status: { DRDY ERR }
    Sep 24 06:13:59 kernel: ata6.00: error: { ICRC ABRT }
    Sep 24 06:13:59 kernel: ata6: hard resetting link
    Sep 24 06:13:59 kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
    Sep 24 06:13:59 kernel: ata6.00: configured for UDMA/133
    Sep 24 06:13:59 kernel: sd 5:0:0:0: [sda]
    Sep 24 06:13:59 kernel: Result: hostbyte=0x00 driverbyte=0x08
    Sep 24 06:13:59 kernel: sd 5:0:0:0: [sda]
    Sep 24 06:13:59 kernel: Sense Key : 0xb [current] [descriptor]
    Sep 24 06:13:59 kernel: Descriptor sense data with sense descriptors (in hex):
    Sep 24 06:13:59 kernel: 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    Sep 24 06:13:59 kernel: 00 00 0e 87
    Sep 24 06:13:59 kernel: sd 5:0:0:0: [sda]
    Sep 24 06:13:59 kernel: ASC=0x47 ASCQ=0x0
    Sep 24 06:13:59 kernel: sd 5:0:0:0: [sda] CDB:
    Sep 24 06:13:59 kernel: cdb[0]=0x28: 28 00 00 00 0e 40 00 00 a8 00
    Sep 24 06:13:59 kernel: end_request: I/O error, dev sda, sector 3648
    Sep 24 06:13:59 kernel: ata6: EH complete
    Sep 24 06:14:30 kernel: ata6.00: exception Emask 0x1 SAct 0x7fffffff SErr 0x0 action 0x6 frozen
    Sep 24 06:14:30 kernel: ata6.00: irq_stat 0x40000008
    Sep 24 06:14:30 kernel: ata6.00: failed command: WRITE FPDMA QUEUED
    Sep 24 06:14:30 kernel: ata6.00: cmd 61/08:00:00:08:24/00:00:41:00:00/40 tag 0 ncq 4096 out
    res 40/00:a8:87:0e:00/00:00:00:00:00/00 Emask 0x5 (timeout)
    Sep 24 06:14:30 kernel: ata6.00: status: { DRDY }
    Sep 24 06:14:30 kernel: ata6.00: failed command: READ FPDMA QUEUED
    Sep 24 06:14:30 kernel: ata6.00: cmd 60/a8:08:60:0f:00/00:00:00:00:00/40 tag 1 ncq 86016 in
    res 40/00:10:08:10:00/00:00:00:00:00/40 Emask 0x1 (device error)
    Sep 24 06:14:30 kernel: ata6.00: status: { DRDY }
    Sep 24 06:14:30 kernel: ata6.00: failed command: READ FPDMA QUEUED
    Sep 24 06:14:30 kernel: ata6.00: cmd 60/14:10:08:10:00/00:00:00:00:00/40 tag 2 ncq 10240 in
    res 40/00:10:08:10:00/00:00:00:00:00/40 Emask 0x1 (device error)
    Sep 24 06:14:30 kernel: ata6.00: status: { DRDY }
    Sep 24 06:14:30 kernel: ata6.00: failed command: READ FPDMA QUEUED
    Sep 24 06:14:30 kernel: ata6.00: cmd 60/01:18:24:0f:00/00:00:00:00:00/40 tag 3 ncq 512 in
    res 40/00:10:08:10:00/00:00:00:00:00/40 Emask 0x1 (device error)
    Sep 24 06:14:30 kernel: ata6.00: status: { DRDY }
    Sep 24 06:14:30 kernel: ata6.00: failed command: READ FPDMA QUEUED
    Sep 24 06:14:30 kernel: ata6.00: cmd 60/01:20:25:0f:00/00:00:00:00:00/40 tag 4 ncq 512 in
    res 40/00:10:08:10:00/00:00:00:00:00/40 Emask 0x1 (device error)
    Sep 24 06:14:30 kernel: ata6.00: status: { DRDY }
    Sep 24 06:14:30 kernel: ata6.00: failed command: READ FPDMA QUEUED
    Sep 24 06:14:30 kernel: ata6.00: cmd 60/01:28:26:0f:00/00:00:00:00:00/40 tag 5 ncq 512 in
    res 40/00:10:08:10:00/00:00:00:00:00/40 Emask 0x1 (device error)
    Sep 24 06:14:30 kernel: ata6.00: status: { DRDY }
    Sep 24 06:14:30 kernel: ata6.00: failed command: READ FPDMA QUEUED
    Sep 24 06:14:30 kernel: ata6.00: cmd 60/01:30:27:0f:00/00:00:00:00:00/40 tag 6 ncq 512 in
    res 40/00:10:08:10:00/00:00:00:00:00/40 Emask 0x1 (device error)
    Sep 24 06:14:30 kernel: ata6.00: status: { DRDY }
    Sep 24 06:14:30 kernel: ata6: hard resetting link
    Sep 24 06:14:30 kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
    Sep 24 06:14:30 kernel: ata6.00: configured for UDMA/133
    Sep 24 06:14:30 kernel: sd 5:0:0:0: [sda]
    Sep 24 06:14:30 kernel: Result: hostbyte=0x00 driverbyte=0x08
    Sep 24 06:14:30 kernel: sd 5:0:0:0: [sda]
    Sep 24 06:14:30 kernel: Sense Key : 0xb [current] [descriptor]
    Sep 24 06:14:30 kernel: Descriptor sense data with sense descriptors (in hex):
    Sep 24 06:14:30 kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    Sep 24 06:14:30 kernel: 00 00 10 08
    Sep 24 06:14:30 kernel: sd 5:0:0:0: [sda]
    Sep 24 06:14:30 kernel: ASC=0x0 ASCQ=0x0
    Sep 24 06:14:30 kernel: sd 5:0:0:0: [sda] CDB:
    Sep 24 06:14:30 kernel: cdb[0]=0x28: 28 00 00 00 0f 60 00 00 a8 00
    Sep 24 06:14:30 kernel: end_request: I/O error, dev sda, sector 3936
    Sep 24 06:14:30 kernel: sd 5:0:0:0: [sda]
    Sep 24 06:14:30 kernel: Result: hostbyte=0x00 driverbyte=0x08
    Sep 24 06:14:30 kernel: sd 5:0:0:0: [sda]
    Sep 24 06:14:30 kernel: Sense Key : 0xb [current] [descriptor]
    Sep 24 06:14:30 kernel: Descriptor sense data with sense descriptors (in hex):
    Sep 24 06:14:30 kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    Sep 24 06:14:30 kernel: 00 00 10 08
    Sep 24 06:14:30 kernel: sd 5:0:0:0: [sda]
    and so on... It somehow booted, but now journalctl says:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
    184 End-to-End_Error 0x0032 099 099 099 Old_age Always FAILING_NOW 1
    while the Error hasn't occured yet.
    I think I wil take the emergency procedure, and start backing up my files and system ...
    I don't recall when this error first showed up, and I unluckily deleted my journal before noticing the problem, for it was getting big, so I can't trace back. But I have it in the journal since then (11.september). At begining only from time to time, but now things are getting worse.

  • New Windows server 2003 Hyper-V guest fails to boot

    Hello,
    I'm currently doing some virtualization experiments on my new server hardware. The host hardware is:
    IBM x3650 M4
    x2 Xeon E5-2609
    32GB RAM
    x2 480 GB SSDs
    Server OS: Windows server 2012
    I'd like to test some legacy app virtualization. I've configured a VM and have installed Windows server 2003. The install is done via DVD. The issue at hand is that after the initial installation, the server fails to boot. The VM goes into a reboot loop
    and so far the only error logging I'm able to find is in the hosts event log. 
    Log Name: Microsoft-Windows-Hyper-V-Worker-Admin
    Source: Microsoft-Windows-Hyper-V-Worker
    Date: 7/8/2014 2:14:48 PM
    Event ID: 18560
    Task Category: None
    Level: Critical
    Keywords:
    User: NT VIRTUAL MACHINE\A0D20FA4-B27B-4B58-85C1-87D74B0ADD2D
    Computer: CCSTS1.cnet2k.cornerstonecredit.net
    Description:
    'LegacyTS' was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault. If the problem persists, contact Product Support. (Virtual machine ID A0D20FA4-B27B-4B58-85C1-87D74B0ADD2D)
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-Hyper-V-Worker" Guid="{51DDFA29-D5C8-4803-BE4B-2ECB715570FE}" />
    <EventID>18560</EventID>
    <Version>0</Version>
    <Level>1</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2014-07-08T21:14:48.544007000Z" />
    <EventRecordID>159</EventRecordID>
    <Correlation />
    <Execution ProcessID="1512" ThreadID="3536" />
    <Channel>Microsoft-Windows-Hyper-V-Worker-Admin</Channel>
    <Computer>CCSTS1.cnet2k.cornerstonecredit.net</Computer>
    <Security UserID="S-1-5-83-1-2698121124-1264104059-3615998341-769460811" />
    </System>
    <UserData>
    <VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
    <VmName>LegacyTS</VmName>
    <VmId>A0D20FA4-B27B-4B58-85C1-87D74B0ADD2D</VmId>
    <Rax>0x0</Rax>
    <Rbx>0x0</Rbx>
    <Rcx>0x0</Rcx>
    <Rdx>0x0</Rdx>
    <Rsp>0x804de00c</Rsp>
    <Rbp>0x0</Rbp>
    <Rsi>0x0</Rsi>
    <Rdi>0x0</Rdi>
    <R8>0x0</R8>
    <R9>0x0</R9>
    <R10>0x0</R10>
    <R11>0x0</R11>
    <R12>0x0</R12>
    <R13>0x0</R13>
    <R14>0x0</R14>
    <R15>0x0</R15>
    <Rip>0x80547c7c</Rip>
    <Rflags>0x10046</Rflags>
    <FpControlStatus>7F030000000000000000000000000000</FpControlStatus>
    <XmmControlStatus>0000000000000000801F0000FFFF0000</XmmControlStatus>
    <Cr0>0x8001003d</Cr0>
    <Cr2>0x804ddffc</Cr2>
    <Cr3>0xa02000</Cr3>
    <Cr4>0x20</Cr4>
    <Cr8>0xf</Cr8>
    <Xfem>0x1</Xfem>
    <Dr0>0x0</Dr0>
    <Dr1>0x0</Dr1>
    <Dr2>0x0</Dr2>
    <Dr3>0x0</Dr3>
    <Dr6>0xffff0ff0</Dr6>
    <Dr7>0x400</Dr7>
    <Es>0000000000000000FFFFFFFF2300F3C0</Es>
    <Cs>0000000000000000FFFFFFFF08009BC0</Cs>
    <Ss>0000000000000000FFFFFFFF100093C0</Ss>
    <Ds>0000000000000000FFFFFFFF2300F3C0</Ds>
    <Fs>00F0DFFF00000000FF1F0000300093C0</Fs>
    <Gs>0000000000000000FFFFFFFF00000000</Gs>
    <Ldtr>00000000000000000000000000000000</Ldtr>
    <Tr>90685580000000006800000050008B00</Tr>
    <Idtr>000000000000FF0700F4038000000000</Idtr>
    <Gdtr>000000000000FF0300F0038000000000</Gdtr>
    <Tsc>0x148e4294</Tsc>
    <ApicBase>0xfee00900</ApicBase>
    <SysenterCs>0x0</SysenterCs>
    <SysenterEip>0x0</SysenterEip>
    <SysenterEsp>0x0</SysenterEsp>
    </VmlEventLog>
    </UserData>
    </Event>
    My VM config
    <?xml version="1.0" encoding="UTF-16" standalone="yes"?>
    <configuration>
    <_24984ed0-bdad-4b90-82b2-5d59f874e91e_>
    <ChannelInstanceGuid type="string">{E4E9CD0E-4BBF-4C1B-B655-715781690655}</ChannelInstanceGuid>
    </_24984ed0-bdad-4b90-82b2-5d59f874e91e_>
    <_7d80d3db-61ee-4879-8879-5609f1100ad0_>
    <address type="string">5353,00000000,00</address>
    <version type="integer">1</version>
    </_7d80d3db-61ee-4879-8879-5609f1100ad0_>
    <_83f8638b-8dca-4152-9eda-2ca8b33039b4_>
    <controller0>
    <drive0>
    <pathname type="string">E:\Hyper-V\VHD\LegacyTS.vhdx</pathname>
    <pool_id type="string"></pool_id>
    <type type="string">VHD</type>
    </drive0>
    <drive1>
    <pathname type="string"></pathname>
    <type type="string">NONE</type>
    </drive1>
    </controller0>
    <controller1>
    <drive0>
    <pathname type="string">SCSI\CDROM&amp;VEN_IBM_SATA&amp;PROD_DEVICE_81Y3681\4&amp;1864BF9E&amp;0&amp;010000</pathname>
    <pool_id type="string"></pool_id>
    <type type="string">ISO</type>
    </drive0>
    <drive1>
    <pathname type="string"></pathname>
    <type type="string">NONE</type>
    </drive1>
    </controller1>
    <version type="integer">5</version>
    </_83f8638b-8dca-4152-9eda-2ca8b33039b4_>
    <_8e3a359f-559a-4b6a-98a9-1690a6100ed7_>
    <port0>
    <connection type="string"></connection>
    </port0>
    <port1>
    <connection type="string"></connection>
    </port1>
    <version type="integer">2</version>
    </_8e3a359f-559a-4b6a-98a9-1690a6100ed7_>
    <_8f0d2762-0b00-4e04-af4f-19010527cb93_>
    <controller0>
    <drive0>
    <pathname type="string"></pathname>
    <type type="string">VFD</type>
    </drive0>
    </controller0>
    <version type="integer">1</version>
    </_8f0d2762-0b00-4e04-af4f-19010527cb93_>
    <_a80e9c62-750a-4a6b-9548-d46677e806be_>
    <ChannelInstanceGuid type="string">{23c9c636-93de-4aec-9bef-220766177a24}</ChannelInstanceGuid>
    <Connection>
    <AltPortName type="string">Dynamic Ethernet Switch Port</AltPortName>
    <AltSwitchName type="string">Intel(R) I350 Gigabit Network Connection - Virtual Switch</AltSwitchName>
    <AuthorizationScope type="string"></AuthorizationScope>
    <ChimneyOffloadWeight type="integer">0</ChimneyOffloadWeight>
    <Feature_C885BFD1-ABB7-418F-8163-9F379C9F7166>
    <DisplayName type="string"></DisplayName>
    <Flags type="integer">0</Flags>
    <Setting_97274751-A1EC-4DC2-941D-B7F9A1AED814>
    <Data type="bytes">AAIAAGQAAAAAAAAAAQAAAAAAAAA=
    </Data>
    <Version type="integer">256</Version>
    </Setting_97274751-A1EC-4DC2-941D-B7F9A1AED814>
    <Settings>
    <Id type="string">97274751-A1EC-4DC2-941D-B7F9A1AED814</Id>
    </Settings>
    </Feature_C885BFD1-ABB7-418F-8163-9F379C9F7166>
    <Features>
    <Id type="string">C885BFD1-ABB7-418F-8163-9F379C9F7166</Id>
    </Features>
    <HostResources>
    <HostResource type="string">8758EB1A-9687-41FC-9319-AE867D46BA5C</HostResource>
    </HostResources>
    <PoolId type="string"></PoolId>
    <PreventIPSpoofing type="bool">False</PreventIPSpoofing>
    <TestReplicaPoolId type="string"></TestReplicaPoolId>
    <TestReplicaSwitchName type="string"></TestReplicaSwitchName>
    </Connection>
    <FriendlyName type="string">Network Adapter</FriendlyName>
    <IsConnected type="bool">True</IsConnected>
    <MacAddress type="string">00-15-5D-01-18-02</MacAddress>
    <MacAddressIsStatic type="bool">False</MacAddressIsStatic>
    <PortName type="string">E7F02418-A1EB-4FF9-84F8-BF461B2D00C6</PortName>
    <SwitchName type="string">8758EB1A-9687-41FC-9319-AE867D46BA5C</SwitchName>
    <VpciInstanceGuid type="string">{E9444985-111B-404A-82FE-48608A397676}</VpciInstanceGuid>
    </_a80e9c62-750a-4a6b-9548-d46677e806be_>
    <_ac6b8dc1-3257-4a70-b1b2-a9c9215659ad_>
    <base_board>
    <serial_number type="string">9595-3600-2199-6834-7686-3927-30</serial_number>
    </base_board>
    <bios_guid type="string">{B54BE7B5-05A4-4C4A-A2BD-D63272C7CCCD}</bios_guid>
    <bios_serial_number type="string">9595-3600-2199-6834-7686-3927-30</bios_serial_number>
    <boot>
    <device0 type="string">Optical</device0>
    <device1 type="string">HardDrive</device1>
    <device2 type="string">Network</device2>
    <device3 type="string">Floppy</device3>
    </boot>
    <chassis>
    <asset_tag type="string">8437-8592-0329-9603-9215-1886-12</asset_tag>
    <serial_number type="string">9595-3600-2199-6834-7686-3927-30</serial_number>
    </chassis>
    <num_lock type="bool">False</num_lock>
    <version type="integer">2</version>
    </_ac6b8dc1-3257-4a70-b1b2-a9c9215659ad_>
    <_db8b9818-b4bb-4725-b99d-b4612716b6b4_>
    <version type="integer">0</version>
    </_db8b9818-b4bb-4725-b99d-b4612716b6b4_>
    <global_settings>
    <devices>
    <allow_reduced_fc_redundancy type="bool">False</allow_reduced_fc_redundancy>
    <generation_id type="string">883d11122d9b7b2c521be0c045ef3760</generation_id>
    <storage_allow_full_scsi_command_set type="bool">False</storage_allow_full_scsi_command_set>
    </devices>
    <disk_merge_pending type="bool">False</disk_merge_pending>
    <metrics>
    <devicetype>
    <deviceinstance>
    <guid type="string">B637F346-6A0E-4DEC-AF52-BD70CB80A21D</guid>
    <metric>
    <enabled type="bool">False</enabled>
    <lastcomputedtime type="integer">0</lastcomputedtime>
    <peaktime type="integer">0</peaktime>
    <poolid type="string"></poolid>
    <resourcetypeid type="string">B637F347-6A0E-4DEC-AF52-BD70CB80A21D</resourcetypeid>
    <starttime type="integer">0</starttime>
    <typecode type="string">3F6F1051-C8FC-47EF-9821-C07240848748;0</typecode>
    <value type="integer">0</value>
    </metric>
    </deviceinstance>
    <guid type="string">B637F346-6A0E-4DEC-AF52-BD70CB80A21D</guid>
    </devicetype>
    <devicetype>
    <deviceinstance>
    <guid type="string">4764334D-E001-4176-82EE-5594EC9B530E</guid>
    <metric>
    <enabled type="bool">False</enabled>
    <lastcomputedtime type="integer">0</lastcomputedtime>
    <peaktime type="integer">0</peaktime>
    <poolid type="string"></poolid>
    <resourcetypeid type="string">4764334E-E001-4176-82EE-5594EC9B530E</resourcetypeid>
    <starttime type="integer">0</starttime>
    <typecode type="string">394DCE66-458F-4895-AE56-41D7C9602A49</typecode>
    <value type="integer">0</value>
    </metric>
    <metric>
    <enabled type="bool">False</enabled>
    <lastcomputedtime type="integer">0</lastcomputedtime>
    <peaktime type="integer">0</peaktime>
    <poolid type="string"></poolid>
    <resourcetypeid type="string">4764334E-E001-4176-82EE-5594EC9B530E</resourcetypeid>
    <starttime type="integer">0</starttime>
    <typecode type="string">FF85EA46-9933-4436-BE5D-C96827399966</typecode>
    <value type="integer">0</value>
    </metric>
    <metric>
    <enabled type="bool">False</enabled>
    <lastcomputedtime type="integer">0</lastcomputedtime>
    <peaktime type="integer">0</peaktime>
    <poolid type="string"></poolid>
    <resourcetypeid type="string">4764334E-E001-4176-82EE-5594EC9B530E</resourcetypeid>
    <starttime type="integer">0</starttime>
    <typecode type="string">04BDF59E-580D-4441-8828-FFFE44472D2D</typecode>
    <value type="integer">0</value>
    </metric>
    </deviceinstance>
    <guid type="string">4764334D-E001-4176-82EE-5594EC9B530E</guid>
    </devicetype>
    <devicetype>
    <deviceinstance>
    <guid type="string">83F8638B-8DCA-4152-9EDA-2CA8B33039B4</guid>
    <metric>
    <enabled type="bool">False</enabled>
    <lastcomputedtime type="integer">0</lastcomputedtime>
    <peaktime type="integer">0</peaktime>
    <poolid type="string"></poolid>
    <resourcetypeid type="string">70BB60D2-A9D3-46AA-B654-3DE53004B4F8</resourcetypeid>
    <starttime type="integer">0</starttime>
    <typecode type="string">AD29978B-AAB6-44AE-81CD-0609BF929F18;0\0\L</typecode>
    <value type="integer">0</value>
    </metric>
    </deviceinstance>
    <guid type="string">83F8638B-8DCA-4152-9EDA-2CA8B33039B4</guid>
    </devicetype>
    </metrics>
    <owner>
    <sid type="string">S-1-5-21-1940488291-1951097212-1584025624-1392</sid>
    </owner>
    <power>
    <host_shutdown>
    <action type="integer">1</action>
    </host_shutdown>
    <host_startup>
    <action type="integer">1</action>
    </host_startup>
    </power>
    <snapshots>
    <list>
    <size type="integer">0</size>
    </list>
    </snapshots>
    <unexpected_termination>
    <action type="integer">1</action>
    </unexpected_termination>
    <vhd_path_acled type="bool">True</vhd_path_acled>
    </global_settings>
    <manifest>
    <size type="integer">11</size>
    <vdev001>
    <device type="string">58f75a6d-d949-4320-99e1-a2a2576d581c</device>
    <flags type="integer">1</flags>
    <instance type="string">58F75A6D-D949-4320-99E1-A2A2576D581C</instance>
    <name type="string">Microsoft Synthetic Mouse</name>
    </vdev001>
    <vdev002>
    <device type="string">197f74e3-b84b-46de-8ae6-82f1cd181cdc</device>
    <flags type="integer">1</flags>
    <instance type="string">197F74E3-B84B-46DE-8AE6-82F1CD181CDC</instance>
    <name type="string">Microsoft Synthetic Keyboard</name>
    </vdev002>
    <vdev003>
    <device type="string">f3cf6965-e8d3-44a9-9b7d-a04245ea7525</device>
    <flags type="integer">1</flags>
    <instance type="string">F3CF6965-E8D3-44A9-9B7D-A04245EA7525</instance>
    <name type="string">Microsoft Synthetic Video</name>
    </vdev003>
    <vdev004>
    <device type="string">84eaae65-2f2e-45f5-9bb5-0e857dc8eb47</device>
    <flags type="integer">1</flags>
    <instance type="string">84EAAE65-2F2E-45F5-9BB5-0E857DC8EB47</instance>
    <name type="string">Microsoft Heartbeat Component</name>
    </vdev004>
    <vdev005>
    <device type="string">2a34b1c2-fd73-4043-8a5b-dd2159bc743f</device>
    <flags type="integer">1</flags>
    <instance type="string">2A34B1C2-FD73-4043-8A5B-DD2159BC743F</instance>
    <name type="string">Microsoft Key-Value Pair Exchange Component</name>
    </vdev005>
    <vdev006>
    <device type="string">9f8233ac-be49-4c79-8ee3-e7e1985b2077</device>
    <flags type="integer">1</flags>
    <instance type="string">9F8233AC-BE49-4C79-8EE3-E7E1985B2077</instance>
    <name type="string">Microsoft Shutdown Component</name>
    </vdev006>
    <vdev007>
    <device type="string">2497f4de-e9fa-4204-80e4-4b75c46419c0</device>
    <flags type="integer">1</flags>
    <instance type="string">2497F4DE-E9FA-4204-80E4-4B75C46419C0</instance>
    <name type="string">Microsoft Time Synchronization Component</name>
    </vdev007>
    <vdev008>
    <device type="string">5ced1297-4598-4915-a5fc-ad21bb4d02a4</device>
    <flags type="integer">1</flags>
    <instance type="string">5CED1297-4598-4915-A5FC-AD21BB4D02A4</instance>
    <name type="string">Microsoft VSS Component</name>
    </vdev008>
    <vdev009>
    <device type="string">6c5addb9-a11a-4e8e-84cb-e6208201db63</device>
    <flags type="integer">1</flags>
    <instance type="string">6C5ADDB9-A11A-4E8E-84CB-E6208201DB63</instance>
    <name type="string">Microsoft RDV Component</name>
    </vdev009>
    <vdev010>
    <device type="string">2fc216b0-d2e2-4967-9b6d-b8a5c9ca2778</device>
    <flags type="integer">1</flags>
    <instance type="string">A80E9C62-750A-4A6B-9548-D46677E806BE</instance>
    <name type="string">Synthetic Ethernet Port</name>
    </vdev010>
    <vdev011>
    <device type="string">d422512d-2bf2-4752-809d-7b82b5fcb1b4</device>
    <flags type="integer">1</flags>
    <instance type="string">24984ED0-BDAD-4B90-82B2-5D59F874E91E</instance>
    <name type="string">Synthetic SCSI Controller</name>
    </vdev011>
    <version type="integer">260</version>
    </manifest>
    <properties>
    <global_id type="string">B37E54CD-FFBB-44DA-8B7C-322B922EAD72</global_id>
    <highly_available type="bool">False</highly_available>
    <last_powered_off_time type="integer">130493284127496105</last_powered_off_time>
    <last_powered_on_time type="integer">130493284065876653</last_powered_on_time>
    <last_state_change_time type="integer">130493284127496105</last_state_change_time>
    <name type="string">LegacyTS</name>
    <notes type="string"></notes>
    <type_id type="string">Virtual Machines</type_id>
    <version type="integer">1024</version>
    </properties>
    <settings>
    <global>
    <logical_id type="string">B37E54CD-FFBB-44DA-8B7C-322B922EAD72</logical_id>
    </global>
    <memory>
    <bank>
    <dynamic_memory_enabled type="bool">True</dynamic_memory_enabled>
    <limit type="integer">1048576</limit>
    <priority type="integer">5000</priority>
    <reservation type="integer">512</reservation>
    <size type="integer">4096</size>
    <target_memory_buffer type="integer">20</target_memory_buffer>
    </bank>
    <vnuma>
    <max_size_per_node type="integer">14770</max_size_per_node>
    </vnuma>
    </memory>
    <processors>
    <count type="integer">1</count>
    <features>
    <limit type="bool">False</limit>
    </features>
    <limit type="integer">100000</limit>
    <limit_cpuid type="bool">False</limit_cpuid>
    <reservation type="integer">0</reservation>
    <vnuma>
    <count_per_node>
    <max type="integer">4</max>
    </count_per_node>
    <node_per_socket>
    <max type="integer">1</max>
    </node_per_socket>
    </vnuma>
    <weight type="integer">100</weight>
    </processors>
    <stopped_at_host_shutdown type="bool">False</stopped_at_host_shutdown>
    <vnuma>
    <enabled type="bool">False</enabled>
    </vnuma>
    </settings>
    </configuration>
    If its relevant, the host is not yet activated license wise. I downloaded the demo version so I could test my idea before making a purchase to go ahead with full implementation. 
    As it stands right now I'm not sure how to troubleshoot this. Many searches on google have not turned up any helpful info. Does anyone have any ideas?
    Thanks,
    D

    Hi ,
    First , please refer to the supported guest OS of windows 2012 hyper-v :
    http://technet.microsoft.com/library/hh831531.aspx
    2003/R2 should be with sp2 and max 2 virtual processors .
    "'LegacyTS' was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault."
    If the issue is not due to the above items , you can try to check the "CPU compatibility " in that VM settings for troubleshooting:
     Hope it helps
    Best Regards
    Elton Ji
    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.

  • [SOLVED] Arch Linux Duke (2007) Fails to Boot

    Folks, I have a unique and challenging problem that has exhausted my Arch Linux skills, and so I am now turning to you.
    I have a vintage Pentium Pro 200 system (that’s 200 MHz folks! – 200 MHz 686 architecture – the original 686!), two CPUs, running a dual boot between Windows NT 4.0 and Arch Linux Duke (2007). It has 512 MB of RAM and a 120 GB hard drive, partitioned up between Windows NT and Linux. I built this system new in 2007, hence the dated version of Arch.  It has run like a charm all these years, granted not getting that much use. After about a year of no use at all, I fired the system up last week to help with a little research for a blog post I was writing on networking Windows NT 4.0 and Mac OS 8.6. Windows NT 4.0 fired right up with no issue, and after I was done testing what needed to be tested I tried to boot over to Arch.
    After a year of disuse, Arch unexpectedly and stubbornly refused to boot. The boot process started up just fine, but towards the end, it declared that it could not mount the root file system on the root device and took a kernel panic and stopped. My Arch skills have gotten a bit rusty in the last few years, but I dusted them off and went to work. My guess was a file system or superblock error. Arch wouldn’t boot, but I dragged out my trusty RIPLinux 2.9 Rescue Live CD and fired it up. It came right up and ran, and I was able to mount the Arch partition and view all the files… everything seemed to be there; it just wouldn’t boot. Windows NT 4.0 AND RIPLinux both boot and run on the machine, so the hardware is fine as well.
    A little information on the disk layout. Windows NT 4.0 is in the first partition on the hard drive. The extended partition has a second Windows NT 4.0 partition (sort of a /home partition for Windows NT 4.0), followed by the main Arch partition (the one I am trying to boot), followed by a swap partition and then the largest partition, which I use to share data between Arch and Windows NT 4.0 (I have loaded an ext2/3 driver into Windows NT 4.0 and it happily accesses the Linux partitions on the box).
    RIPLinux’s e2fsck did find some issues with the Arch partition and I had it repair them all. I checked again afterwards that all the files were still there, and they were. With the partition now known to be clean, and the superblock repaired from one of the backups, all should have been well. However, Arch still wouldn’t (and still won’t) boot.
    RIPLinux has a kind of a chain loader function, so I had it attempt to start up Arch for me. However, this was flummoxed by the fact that Arch addresses all my hard drive partitions as /dev/sdax and RIPLinux addresses them as /dev/hdax. Hence, without a common language, it was hard to get the one to start the other. Still, using this function, I have been able to get a crippled version of Arch running on the machine again. No modules had been loaded, and so it couldn’t do almost anything, but there it was (and is), Arch Linux Duke, at the CLI level. From there, I can see all the files, I can move freely in and out of my user account and the root account, but I can’t make the thing actually boot properly.
    If you have read this far, you are a trooper.  Summarizing what I know, the hardware is good, the file system is clean, the superblock is good, I can mount it cleanly from a live CD and I can chain load a crippled version of Arch. Here is the boot process blow-by-blow. When I try to do a normal boot, the Windows NT 4.0 loader passes control to the Lilo boot sector I have placed on hda1 (sda1 in Duke’s parlance). Lilo takes over, present a menu and when I select Duke, takes off. Arch Linux Duke starts to boot. It gets a good long way along, all the way along to:
    :: Loading udev events                [Pass]
    :: Mount root Read-only
    :: Checking file systems
    This is where it stops.
    The next thing I see is:
    /dev/sda6
    The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else) then the superblock is corrupt and you might try running e2fsck with an alternate superblock:
        E2fsck –b 8193 <device>
    I then get a sort of character based splash screen that says
    **********FILE SYSTEM CHECK FAILED ****************************
    *   Please repair manually and reboot. Note that the root file system
    *   is currently mounted read-only. To remount it read-write, type:
    *   mount –n –o remount,rw /.  When you exit the maintenance
    *   shell, the system will reboot automatically
    Give root password for maintenance
    At this point, I give the root password and enter the maintenance shell as root. I typed in “mount” and the first entry I got back is
    /dev/sda6 on / type ext3 (rw)
    This is exactly the root partition that the start up complains about. It is clearly there.  I can see it, I can walk around it… it is clearly there. Why won’t it boot? Despite the message, the superblock is fine – it passes every test e2fsck can throw at it.
    At this point, I did a “e2fsck /dev/hda6 (which is how RIPLinux would have passed it into Arch” and it says it is “clean”. I suspect that the Superblock message is because Arch sees root as sda6, while RIP passed it in as hda6...
    Deciding to see what Arch would be seeing as it tried to set things up in the boot sequence, I tried the following next:
    # mknod “/dev/root2” b 3 6   
    (“3” because RIPLinux refers to my hard drive as IDE, while Arch refers to it by major number “8”, which is SCSI. By the way, it IS an IDE drive – not sure why Arch insists on using the sdx nomenclature instead of hdx)
    Then I entered “mount /dev/root2 /mnt/hda6” and “ls /mnt/hda6”
    All was well. I can make the node, I can mount it, and I can see the contents. All is clearly well, but something is clearly wrong enough that Arch can’t boot.
    I am totally out of ideas. I have tried every trick I know and am out of tricks. I would welcome any insights as to what I could try to get this venerable Arch installation back on its legs.
    By the way, the key section of the /etc/lilo.conf file (lest anyone want to know) is:
    image = /boot/vmlinuz26
       root = /dev/sda6
       label = ArchLinux-Duke
       initrd = /boot/kernel26.img
       read-only
    I am stumped. Thanks in advance for any and all pointers you may be able to offer.
    Last edited by mac57 (2014-06-02 17:42:21)

    Folks, thanks for all your helpful comments, and I wanted to report back to you that I finally overcame the issue, and ArchLinux-Duke (2007) is once again executing flawlessly on my old Pentium Pro 200 system. I won't bother reporting here all the blind allies I went down as I tried to figure out what was wrong, but in the end, literally moments before I was about to give up and overwrite my Arch installation with a new Linux variant (antiX seemed well suited for such old and low power hardware), my attention was drawn to a note I had made in my files back in 2007 about a problem with similar symptoms. In that case, I had just deleted ZenWalk Linux from the hard drive (both Arch and Zen had been on the drive), and merged several partitions to make use of the newly free space. This had changed Arch's view of the drive lettering, and what had been its /dev/sddx root device was now /dev/sdcx. Arch failed to boot, throwing off the same errors I was seeing now. I wish I had recalled that note a month or so ago! It would have saved me a lot of work and a lot of frustration.
    At any rate, as a last step, and testing the idea that maybe the drive lettering had changed for some reason, I repeatedly manually booted Arch, specifying root=/dev/sda6, then /dev/sdb6, then /dev/sdd6, and finally, /dev/sdc6. Eureka! Arch now considered itself to be on /dev/sdc6 whereas previously it had been on /dev/sda6. This got me part way there, but the boot failed at the filesystem check stage and threw me into root. I disabled the file system check in /etc/rc.sysinit and got farther. Then I cleaned up /etc/fstab to agree with the new sdc naming, and I was back on the air fully.
    So, what had happened was that Arch had changed its view of the drive it was on from sda6 to sdc6. While I could not understand why this "sudden" change had occurred, at least I had a solution, and had Arch back up and running.
    Trolling through the rest of my notes, I found the answer. In 2012, the Tekram SCSI card in the machine failed, and I ultimately replaced it with an Adaptec card. The Tekram card did not have a BIOS segment on it. The Adaptec card did. My guess is that this caused the two internal SCSI devices I have built into the system (Iomega ZIP and Jaz respectively) to be enumerated first, claiming the "sda" and "sdb". device names. That left "sdc" for the root device, and that is where Arch went next.  This is my guess anyway.
    I should have caught this issue back in 2012, at the time, but from my notes, I can see that I tested the new card thoroughly using the  Windows NT 4.0 side of the machine, but never thought to bring up Arch as well. Hence, this problem lay dormant for two years, before I attempted to fire up Arch last month and blundered right into it.
    It has not all been bad. I have learned more about the ext2 and ext3 file systems and superblocks in the intervening time than I will ever need to use. I have learned how to manually boot Linux on a machine whose BIOS is so old that it cannot address the disk cylinder that the kernel is on and I have completely refreshed the many general Linux skills that used to just flow from my finger tips. It has been a frustrating experience, but ultimately a successful and useful one.
    Just wanted to let everyone know that this is now [SOLVED]. I would mark the post as such, but I don't see any obvious way to do that. Thanks again everyone.

  • Restored 10.6 OS from CD and fails to Boot after Combo upgrade

    I have a clean install of Lion on my internal drive and an external clone of the HD from the previous Snow Leopard install. The Clone worked until I updated via the latest auto update. I have App's and other settings to transfer to Lion from this clone so want to get it working so I can ensure all the App's are upgraded to work on Lion or are deleted.
    After the external drive failed to boot I reinstalled the system from my Snow Leopard Install CD, not the 24-inch iMac (Mid 2007) restore CD.
    I then used Auto updater to install the combo and other updates to 10.6.8 this booted fine until I upgraded Safari 5.1 and Java - the last items that came up on the software updater. Upon restart, the boot failed in the last portion of the boot and at this point the Apple emblem went away and the round circle with diaginoal line apeared.
    On starting with the option key down, the clone disk 10.6.8 shows as being available, along with the internal Drive, for booting.
    Starting with "command + S" gets through to the last line of the process then states "waiting on Root"
    When compaired to a Snow OS that boots OK it is the last line of code before the curser is ready for entering a command.
    Can anyone tell me what to look for or how to repair this error so that I can get my data across to Lion. Thanks

    Well, in case anyone else has a similar problem I managed to fix the system by the following process:
    I reinstalled 10.6.0 from the retail Snow Leopard CD. The drive Booted OK but I needed to be upgraded to 10.6.8 to use the migration tool so I then upgraded using the Software Update utility. Boot failed again at this point and could not be fixed by anything I did.
    I then reinstalled 10.6.0 from the CD to try again, but the HD would not boot this time around.
    I downloaded CleanApp by Synium Software (http://www.syniumsoftware.com/cleanapp/) on a commendation from the famous eBook, "Take Control of installing Lion" by Joe Kissell of TidBits. I used this from my Lion HD to remove all orphan files, PPC files and Apps, and other junk. Snow Leapard still not Booting after repairs by various disk repair utilities including Apples.
    I Booted from my internal HD using Lion and ran SuperDuper to make a new Clone of the failed HD on a second external HD. Took a day and a night to run while I was at work, but the new clone would not boot at this stage so I ran SuperDuper again using the "Smart Update Backup" option. This just adds changed files or missing files to the clone. At the end of this process I had a running Clone that would boot on 10.6.0.
    I Booted from the second Clone and used the Software Update utility then to up grade in the two stages the Auto system used to bring my OS up to 10.6.8. This was successful and I had a Bootable Snow Leopard with no old Apps from which to Migrate my data.

  • Compaq Notebook CQ-45 137TX fails to boot

    Hello,
    I own a Compaq CQ-45 137TX (Intel Core 2 Duo P7350, 3 GB RAM, 320GB HDD, nVidia GeForce 9200M GS, Windows 7(upgraded from Vista)) with a broken LCD Screen. Since repairing the screen made no sense for such an old laptop, I started using it as a desktop by attaching an external monitor and input devices. The computer worked fine for the past few months.
    Upon restarting the computer after a hiatus of a week or so, the computer failed to boot and display anything on the external monitor. I think it is failing POST.
    The laptop gives out multiple beeps continually (not continuous, multiple beeps that don't end).
    I thought that the RAM is faulty and tried to reboot the machine by trying one RAM stick at a time (since the laptop has two). It didn't work for either of the two sticks tried in both slots individually.
    I think both the RAM sticks may be faulty, however, I am unable to borrow a RAM stick to test on it.
    Before buying a new one, I would like someone to clarify or point out other hardware that may faulty in this laptop. I have had people tell me that my Graphic Card may have given up.
    Thank you for your assistance.

    Hello @root123 ,
    Welcome to the HP Forums!
    I understand you're unable to boot up your CQ-45 notebook.
    It's unlikely to be RAM if neither card worked in either of the two DIMM slots. It is possible that both cards or slots have failed, but highly unlikely.
    The beeping should tell you exactly what the error is. Try looking through this document which should help you identify the error: Computer Does Not Start and the LEDs Blink or the Computer Beeps.
    You may also want to try this document as well: Troubleshooting Black Screen Displays with No Error Messages During Startup or Boot.
    Let me know if you're able to identify the failure with the beep code and we'll go from there.
    Please click the "Kudos, Thumbs Up" at the bottom of this post if you want to say "Thanks" for helping!
    Please click "Accept as Solution" if you feel my post solved your issue, it will help others find the solution.
    The Great Deku Tree
    I work on behalf of HP.

Maybe you are looking for