Faulty device

I have had service with Verizon since the end May of this year using the Jetpack 890L. It drops its connection on average a dozen times each day. Each time, I must switch the unit off and back on again in order to re-connect. All the computers in my household maintain a local connection with the device itself, but it does not maintain a connection with the tower.
I have called technical support 16 times, spoken to supervisors, and the manufacturer via the Verizon supervisor. I have received a replacement device and they have tried to replace the SIM card (in the store) as well.
The Tech support has told me this is a known issue with the firmware in this device and the only effective solution has been to place the SIM card into some other active device (other than the Jetpack) and then place it back into the device. My local Verizon store has no other devices that use this standard SIM card and neither the store nor the Verizon office is willing to receive my SIM card and plug it into an active device or send me an activated SIM card. My device still does not even show up as activated on their system. They're confused as to how I'm getting any connection at all. Of course, they have no difficulty monitoring my usage and billing me accordingly
I have exhausted all options at this point. Verizon will neither allow me to get a different device nor let me out of my contract. My only option, I'm told, is to continue to get replacements of the same device (which I have already done, and even though the faulty component is the firmware, which will be the same in each) or wait until the manufacturer finds the problem in the firmware and creates an update. Up until my last my last call to Verizon, I have been very patient. I understand that with any technology, these things are bound to occur. What I do not understand is if this device has a known issue and they are unable to fix it, why I can not get another device that does work?
Thank you for your time.

I'm speechless as well.

Similar Messages

  • Faulty Devices - Blackberry Z10

    Our company recently renewed the corporate mobile phone contract with Maxis and we received Blackberry Z10 Smart Phones as free device for the plan that we signed up.
    We received 58 units of Blackberry Z10 in June 2014, out of which to-date, several units (40%) have proven to be faulty and warranty claims were made. The claims were handled by IXSUN SDN BHD – Blackberry Service Centre at Tropicana City Mall.
    The type of claims varies from hardware reset, faulty battery, keypad not working, system hang etc…
    Our business is IT based and we depend a lot on the Smart Phone, accessing to e-mails and as 80% of our employees are Consultants, they should always be reachable on phone. The faulty devices cost the company additional expenses (admin costs – mileage and toll) and a waste of billable time. We are extremely disappointed and unhappy with the quality of device sent and demand that all the units be replaced with a new batch of devices – all 58 units in total.
    We are also surprised with your Service Centre policy whereby no hardcopy is given as supporting document for the warranty claim. Only Acknowledgement Job Card is given and upon receiving the repaired phone, the form is retained by the Service Centre and for record, we are requested to take photo of the form instead!
    Please find enclosed, copies of the photo shots taken of the forms, last batch of phones sent in for warranty claim last week.
    This is a serious allegation and do revert with your solution to our problem within 14 days of the date of this letter, failing which we will cancel the corporate plan with Maxis and return all the phones back to you and seek monetary compensation for the breach of contract in furnishing faulty devices.
    Should you have any queries, please contact Ms Sue at 03 56369016 ext 138 or 012 3242137.

    This is a volunteer run forum we do not have anything to do with BB.

  • Quite posibly the most unstable device I've ever had the misfortune to use.

    I'm in utter rage at the performance and stability of the iPhone 3G.
    My 8GB model constantly crashes, freezes, music stutters and I am experiencing REGULAR slowdown on the device.
    I gave up a perfectly functioning N95 after having a positive experience with the iPod touch and I finally wanted to have the touch experience with the 3G. How wrong was I to get this phone.
    To top this all off, I know someone who has the same 8GB iPhone 3G and he has told me that his one has never slowed down or crashed.
    After my above rant, is he lying or could I have a faulty device? The old 1.14 software on my iPod touch was rock solid with the odd crash in safari but i never did experience the laggyness as I am on the 3G.
    Am I experiencing the norm with these issues or is my friend correct that the iPhone 3G is as stable as he tells me?
    Thanks for reading,
    Chaz.

    Chaz_UK wrote:
    To top this all off, I know someone who has the same 8GB iPhone 3G and he has told me that his one has never slowed down or crashed.
    After my above rant, is he lying or could I have a faulty device?
    You could have a faulty device. My daughter has the 3G iPhone and says she has no problems and loves it (she is also coming from an iPod Touch). I've had the original iPhone for a bit over a year and have had no problems -- even after upgrading to OS 2.0 on July 11.
    Phil

  • Replace Faulty IronPort ESA in a Cluster

    I have a cluster of 2 IronPort ESA appliances and one of these is faulty and will not boot. I am awaiting a replacement from Cisco.
    I cannot find an exact guide that explains how to re-instate the new appliance to cluster and therefore am making an assumption that the easiest way to do this is as follows:-
    1) Physically connect the new device.
    2) Login with console and ensure the new device has centralised management feature and all other keys.
    3) Configure the management interface with the original machine level IP address from the old configuration of the faulty device.
    4) Use Clusterconfig command to join new device to cluster.
    The only thing I am concerned about is licensing and serial numbers. I seem to remember that the primary cluster device will check the serial number at some point and therefore if its a new device then it will not join the cluster. If this is the case then I assume we would have to remove the orignal device from cluster and add the new one as a brand new one. This would mean all other machine level configuration would be lost such as IP addresses of Data interfaces and DNS names etc.
    Can anyone clarify please. Also can anyone point me to which configuration is required for machine level only.
    Regards
    Paul Tribe

    So - to help out - yes... it would be pretty much...
    1) Once you get the RMA appliance, rack and cable the appliance, and bring it online with the quickstart guide.  We'll call this ESA3.
    2) Once ESA3 is online - you'll need to make sure that you get the RMA on the same matching AsyncOS version as ESA1.  (*This may mean you'll need to upgrade ESA1 to get a compairible revision running...)  Also, just go ahead and make the IP and hostname the same as you had for ESA2... if not done @ quickstart.
    3) Once the version is matching - just transfer over the license/feature keys from the old ESA2 to your new ESA3 (RMA unit):
    http://www.cisco.com/c/en/us/support/docs/security/email-security-appliance/118000-technote-esa-00.html
    4) Once licnesing is completed - just join to cluster.  (*If you are running 8.5.6 --- clustering is included in the release --- just run clusterconfig on the CLI to assure operation.)  From ESA1, running clusterconfig and removemachine - choosing ESA2.  From ESA3, clusterconfig and join cluster:
    http://www.cisco.com/c/en/us/support/docs/security/email-security-appliance/118174-technote-esa-00.html
    I hope this helps!
    -Robert
    (*If you have received the answer to your original question, and found this helpful/correct - please mark the question as answered, and be sure to leave a rating to reflect!)

  • When is the new MIFI device scheduled to be released?

    OK I've had quite a bit of experience with faulty tech and dealing with tech support people. I'm no programmer or expert but my gut is telling me I'm not going to see a fix for the MIFI 4510L.
    SO
    When is the new model set to be released?
    AND
    Will Verizon allow their business customers to turn in the 4510L devices for the new devices. Your faulty device has caused our company to lose money. Your customers deserve compensation.
    I have looked at all the "workarounds" and "fixes" it is clearly obvious that they do not work. I should be able to:
    Plug the device into the charger
    Turn on the device
    Connect to the device with my computer
    I should have uninterrupted internet access all day long (10-12hrs) provided I don't leave the signal area.
    This is the way it should be and until VZ meets these expectations I will not be satisfied.

    Good morning ipodjockey,
    I had the opportunity to read your original post about the mifi 4510L and I see you have several questions about the functionality of the device. As you may know, we try to report any and all issues that customers may be experiencing with any device in our portfolio. I'm pleased to advise that as of 11/1, there has been a new software release for the mifi 4510L. This update provides several enhancements to the device, like connection improvements in 3G and 4G LTE areas. Below is a link to the website with information and instructions on how to complete the software update. 
    http://support.verizonwireless.com/system_update/mifi4510l.html
    Although the website says Coming Soon, you can click on Software Update Instructions (*PDF) to access the link to the software download. As far as new mifis launch dates & availability, here a link to stay in the know for on our upcoming products and services.
    https://email.vzwshop.com/servlet/formlink/f?NFOQU&SOURCEID=WEB_DGF_VZW_SUPPORTNAV
    Once you have completed the software update, please test the connectivity & reply with your findings. As always, we are available to assist you.
    Thank you...

  • "Kernel panic - not syncing: Attempted to kill init!" on shutdown

    For several years now, I've been happily using Arch. I'm quite a seasoned user. I've solved countless errors and problems with my systems on 3 different machines, but I don't know how to fix this one. I've searched the forum and asked google -- got no answer.
    Since systemd upgrade on my Asus laptop, shutdown and reboot broke down. The other machine with Arch works fine (systemd installed), but that's a stationary computer.
    I don't know what may be wrong... The system is upgraded to the full. The error displayed by kernel is as follows:
    Kernel panic - not syncing: Attempted to kill init!
    And photo of it happening: http://i.imgur.com/kewfbYv.jpg
    This happens every time I try to shut down or reboot the laptop. (I'm using the poweroff and reboot commands). I have to press the power button for a while to force poweroff. It's really annoying.
    Everything works just fine except this kernel panic. I'm using catalyst drivers. Other than that - nothing "unusual".
    Boot journal:
    -- Logs begin at Mon 2012-12-31 05:00:25 CET, end at Sat 2013-01-26 12:27:00 CET. --
    Jan 26 12:20:45 further systemd-journal[145]: Allowing runtime journal files to grow to 171.5M.
    Jan 26 12:20:45 further kernel: Initializing cgroup subsys cpuset
    Jan 26 12:20:45 further kernel: Initializing cgroup subsys cpu
    Jan 26 12:20:45 further kernel: Linux version 3.7.4-1-ARCH (tobias@T-POWA-LX) (gcc version 4.7.2 (GCC) ) #1 SMP PREEMPT Mon Jan 21 23:05:29 CET 2013
    Jan 26 12:20:45 further kernel: Command line: root=/dev/sda6 ro nomodeset init=/sbin/init rootfstype=ext4
    Jan 26 12:20:45 further kernel: e820: BIOS-provided physical RAM map:
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x0000000000100000-0x000000008f6bffff] usable
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f6c0000-0x000000008f702fff] ACPI NVS
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f703000-0x000000008f711fff] ACPI data
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f712000-0x000000008f828fff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f829000-0x000000008f838fff] ACPI NVS
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f839000-0x000000008f867fff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f868000-0x000000008f868fff] usable
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f869000-0x000000008f871fff] ACPI NVS
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f872000-0x000000008f883fff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f884000-0x000000008f891fff] ACPI NVS
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f892000-0x000000008f893fff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f894000-0x000000008f89afff] ACPI NVS
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f89b000-0x000000008f89dfff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f89e000-0x000000008f8a6fff] ACPI NVS
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f8a7000-0x000000008f8cdfff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008f8ce000-0x000000008fad0fff] ACPI NVS
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008fad1000-0x000000008fd45fff] usable
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008fd46000-0x000000008fef6fff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x000000008fef7000-0x000000008fefffff] usable
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x00000000fed61000-0x00000000fed70fff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
    Jan 26 12:20:45 further kernel: BIOS-e820: [mem 0x0000000100001000-0x000000014effffff] usable
    Jan 26 12:20:45 further kernel: NX (Execute Disable) protection: active
    Jan 26 12:20:45 further kernel: DMI 2.7 present.
    Jan 26 12:20:45 further kernel: DMI: ASUSTeK Computer Inc. K43TA/K43TA, BIOS 214 04/06/2012
    Jan 26 12:20:45 further kernel: e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
    Jan 26 12:20:45 further kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    Jan 26 12:20:45 further kernel: No AGP bridge found
    Jan 26 12:20:45 further kernel: e820: last_pfn = 0x14f000 max_arch_pfn = 0x400000000
    Jan 26 12:20:45 further kernel: MTRR default type: uncachable
    Jan 26 12:20:45 further kernel: MTRR fixed ranges enabled:
    Jan 26 12:20:45 further kernel: 00000-9FFFF write-back
    Jan 26 12:20:45 further kernel: A0000-BFFFF write-through
    Jan 26 12:20:45 further kernel: C0000-CEFFF write-protect
    Jan 26 12:20:45 further kernel: CF000-E7FFF uncachable
    Jan 26 12:20:45 further kernel: E8000-FFFFF write-protect
    Jan 26 12:20:45 further kernel: MTRR variable ranges enabled:
    Jan 26 12:20:45 further kernel: 0 base 0000000000 mask FF80000000 write-back
    Jan 26 12:20:45 further kernel: 1 base 0080000000 mask FFF0000000 write-back
    Jan 26 12:20:45 further kernel: 2 base 008FF00000 mask FFFFF00000 uncachable
    Jan 26 12:20:45 further kernel: 3 disabled
    Jan 26 12:20:45 further kernel: 4 disabled
    Jan 26 12:20:45 further kernel: 5 disabled
    Jan 26 12:20:45 further kernel: 6 disabled
    Jan 26 12:20:45 further kernel: 7 disabled
    Jan 26 12:20:45 further kernel: TOM2: 000000014f000000 aka 5360M
    Jan 26 12:20:45 further kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Jan 26 12:20:45 further kernel: e820: update [mem 0x8ff00000-0xffffffff] usable ==> reserved
    Jan 26 12:20:45 further kernel: e820: last_pfn = 0x8ff00 max_arch_pfn = 0x400000000
    Jan 26 12:20:45 further kernel: found SMP MP-table at [mem 0x000fce90-0x000fce9f] mapped at [ffff8800000fce90]
    Jan 26 12:20:45 further kernel: initial memory mapped: [mem 0x00000000-0x1fffffff]
    Jan 26 12:20:45 further kernel: Base memory trampoline at [ffff880000097000] 97000 size 24576
    Jan 26 12:20:45 further kernel: Using GB pages for direct mapping
    Jan 26 12:20:45 further kernel: init_memory_mapping: [mem 0x00000000-0x8fefffff]
    Jan 26 12:20:45 further kernel: [mem 0x00000000-0x7fffffff] page 1G
    Jan 26 12:20:45 further kernel: [mem 0x80000000-0x8fdfffff] page 2M
    Jan 26 12:20:45 further kernel: [mem 0x8fe00000-0x8fefffff] page 4k
    Jan 26 12:20:45 further kernel: kernel direct mapping tables up to 0x8fefffff @ [mem 0x1fffd000-0x1fffffff]
    Jan 26 12:20:45 further kernel: init_memory_mapping: [mem 0x100001000-0x14effffff]
    Jan 26 12:20:45 further kernel: [mem 0x100001000-0x1001fffff] page 4k
    Jan 26 12:20:45 further kernel: [mem 0x100200000-0x14effffff] page 2M
    Jan 26 12:20:45 further kernel: kernel direct mapping tables up to 0x14effffff @ [mem 0x8fefc000-0x8fefffff]
    Jan 26 12:20:45 further kernel: RAMDISK: [mem 0x37d07000-0x37feffff]
    Jan 26 12:20:45 further kernel: ACPI: RSDP 00000000000f0450 00024 (v02 _ASUS_)
    Jan 26 12:20:45 further kernel: ACPI: XSDT 000000008f703068 00054 (v01 _ASUS_ Notebook 01072009 AMI 00010013)
    Jan 26 12:20:45 further kernel: ACPI: FACP 000000008f70f1a0 000F4 (v04 _ASUS_ Notebook 01072009 AMI 00010013)
    Jan 26 12:20:45 further kernel: ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20120913/tbfadt-598)
    Jan 26 12:20:45 further kernel: ACPI: DSDT 000000008f703150 0C050 (v02 _ASUS_ Notebook 00000000 INTL 20091112)
    Jan 26 12:20:45 further kernel: ACPI: FACS 000000008f89af80 00040
    Jan 26 12:20:45 further kernel: ACPI: APIC 000000008f70f298 00072 (v03 _ASUS_ Notebook 01072009 AMI 00010013)
    Jan 26 12:20:45 further kernel: ACPI: MCFG 000000008f70f310 0003C (v01 _ASUS_ GMCH945. 01072009 MSFT 00000097)
    Jan 26 12:20:45 further kernel: ACPI: HPET 000000008f70f350 00038 (v01 _ASUS_ Notebook 01072009 AMI 00000004)
    Jan 26 12:20:45 further kernel: ACPI: SSDT 000000008f70f388 00726 (v01 _ASUS_ POWERNOW 00000001 AMD 00000001)
    Jan 26 12:20:45 further kernel: ACPI: SSDT 000000008f70fab0 0190A (v02 _ASUS_ ALIB 00000001 MSFT 04000000)
    Jan 26 12:20:45 further kernel: ACPI: Local APIC address 0xfee00000
    Jan 26 12:20:45 further kernel: No NUMA configuration found
    Jan 26 12:20:45 further kernel: Faking a node at [mem 0x0000000000000000-0x000000014effffff]
    Jan 26 12:20:45 further kernel: Initmem setup node 0 [mem 0x00000000-0x14effffff]
    Jan 26 12:20:45 further kernel: NODE_DATA [mem 0x14effc000-0x14effffff]
    Jan 26 12:20:45 further kernel: [ffffea0000000000-ffffea00053fffff] PMD -> [ffff88014ae00000-ffff88014e5fffff] on node 0
    Jan 26 12:20:45 further kernel: Zone ranges:
    Jan 26 12:20:45 further kernel: DMA [mem 0x00010000-0x00ffffff]
    Jan 26 12:20:45 further kernel: DMA32 [mem 0x01000000-0xffffffff]
    Jan 26 12:20:45 further kernel: Normal [mem 0x100000000-0x14effffff]
    Jan 26 12:20:45 further kernel: Movable zone start for each node
    Jan 26 12:20:45 further kernel: Early memory node ranges
    Jan 26 12:20:45 further kernel: node 0: [mem 0x00010000-0x0009cfff]
    Jan 26 12:20:45 further kernel: node 0: [mem 0x00100000-0x8f6bffff]
    Jan 26 12:20:45 further kernel: node 0: [mem 0x8f868000-0x8f868fff]
    Jan 26 12:20:45 further kernel: node 0: [mem 0x8fad1000-0x8fd45fff]
    Jan 26 12:20:45 further kernel: node 0: [mem 0x8fef7000-0x8fefffff]
    Jan 26 12:20:45 further kernel: node 0: [mem 0x100001000-0x14effffff]
    Jan 26 12:20:45 further kernel: On node 0 totalpages: 911563
    Jan 26 12:20:45 further kernel: DMA zone: 64 pages used for memmap
    Jan 26 12:20:45 further kernel: DMA zone: 6 pages reserved
    Jan 26 12:20:45 further kernel: DMA zone: 3911 pages, LIFO batch:0
    Jan 26 12:20:45 further kernel: DMA32 zone: 16320 pages used for memmap
    Jan 26 12:20:45 further kernel: DMA32 zone: 567679 pages, LIFO batch:31
    Jan 26 12:20:45 further kernel: Normal zone: 5056 pages used for memmap
    Jan 26 12:20:45 further kernel: Normal zone: 318527 pages, LIFO batch:31
    Jan 26 12:20:45 further kernel: ACPI: PM-Timer IO Port: 0x808
    Jan 26 12:20:45 further kernel: ACPI: Local APIC address 0xfee00000
    Jan 26 12:20:45 further kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    Jan 26 12:20:45 further kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
    Jan 26 12:20:45 further kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
    Jan 26 12:20:45 further kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x04] disabled)
    Jan 26 12:20:45 further kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
    Jan 26 12:20:45 further kernel: ACPI: IOAPIC (id[0x03] address[0xfec00000] gsi_base[0])
    Jan 26 12:20:45 further kernel: IOAPIC[0]: apic_id 3, version 33, address 0xfec00000, GSI 0-23
    Jan 26 12:20:45 further kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    Jan 26 12:20:45 further kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
    Jan 26 12:20:45 further kernel: ACPI: IRQ0 used by override.
    Jan 26 12:20:45 further kernel: ACPI: IRQ2 used by override.
    Jan 26 12:20:45 further kernel: ACPI: IRQ9 used by override.
    Jan 26 12:20:45 further kernel: Using ACPI (MADT) for SMP configuration information
    Jan 26 12:20:45 further kernel: ACPI: HPET id: 0xffffffff base: 0xfed00000
    Jan 26 12:20:45 further kernel: smpboot: Allowing 4 CPUs, 2 hotplug CPUs
    Jan 26 12:20:45 further kernel: nr_irqs_gsi: 40
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000000009d000 - 000000000009e000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000000009e000 - 00000000000a0000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f6c0000 - 000000008f703000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f703000 - 000000008f712000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f712000 - 000000008f829000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f829000 - 000000008f839000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f839000 - 000000008f868000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f869000 - 000000008f872000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f872000 - 000000008f884000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f884000 - 000000008f892000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f892000 - 000000008f894000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f894000 - 000000008f89b000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f89b000 - 000000008f89e000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f89e000 - 000000008f8a7000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f8a7000 - 000000008f8ce000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008f8ce000 - 000000008fad1000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008fd46000 - 000000008fef7000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 000000008ff00000 - 00000000e0000000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000e0000000 - 00000000f0000000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000f0000000 - 00000000fec00000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fec00000 - 00000000fec01000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fec01000 - 00000000fec10000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fec10000 - 00000000fec11000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fec11000 - 00000000fed00000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fed00000 - 00000000fed01000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fed01000 - 00000000fed61000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fed61000 - 00000000fed71000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fed71000 - 00000000fed80000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fed80000 - 00000000fed90000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000fed90000 - 00000000ff000000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 00000000ff000000 - 0000000100000000
    Jan 26 12:20:45 further kernel: PM: Registered nosave memory: 0000000100000000 - 0000000100001000
    Jan 26 12:20:45 further kernel: e820: [mem 0x8ff00000-0xdfffffff] available for PCI devices
    Jan 26 12:20:45 further kernel: Booting paravirtualized kernel on bare hardware
    Jan 26 12:20:45 further kernel: setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:4 nr_node_ids:1
    Jan 26 12:20:45 further kernel: PERCPU: Embedded 28 pages/cpu @ffff88014ec00000 s84544 r8192 d21952 u524288
    Jan 26 12:20:45 further kernel: pcpu-alloc: s84544 r8192 d21952 u524288 alloc=1*2097152
    Jan 26 12:20:45 further kernel: pcpu-alloc: [0] 0 1 2 3
    Jan 26 12:20:45 further kernel: Built 1 zonelists in Node order, mobility grouping on. Total pages: 890117
    Jan 26 12:20:45 further kernel: Policy zone: Normal
    Jan 26 12:20:45 further kernel: Kernel command line: root=/dev/sda6 ro nomodeset init=/sbin/init rootfstype=ext4
    Jan 26 12:20:45 further kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
    Jan 26 12:20:45 further kernel: __ex_table already sorted, skipping sort
    Jan 26 12:20:45 further kernel: Checking aperture...
    Jan 26 12:20:45 further kernel: No AGP bridge found
    Jan 26 12:20:45 further kernel: Calgary: detecting Calgary via BIOS EBDA area
    Jan 26 12:20:45 further kernel: Calgary: Unable to locate Rio Grande table in EBDA - bailing!
    Jan 26 12:20:45 further kernel: Memory: 3508092k/5488640k available (4832k kernel code, 1842388k absent, 138160k reserved, 4077k data, 808k init)
    Jan 26 12:20:45 further kernel: SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
    Jan 26 12:20:45 further kernel: Preemptible hierarchical RCU implementation.
    Jan 26 12:20:45 further kernel: RCU dyntick-idle grace-period acceleration is enabled.
    Jan 26 12:20:45 further kernel: Dump stacks of tasks blocking RCU-preempt GP.
    Jan 26 12:20:45 further kernel: RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=4.
    Jan 26 12:20:45 further kernel: NR_IRQS:4352 nr_irqs:712 16
    Jan 26 12:20:45 further kernel: Extended CMOS year: 2000
    Jan 26 12:20:45 further kernel: Console: colour VGA+ 80x25
    Jan 26 12:20:45 further kernel: console [tty0] enabled
    Jan 26 12:20:45 further kernel: allocated 14680064 bytes of page_cgroup
    Jan 26 12:20:45 further kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
    Jan 26 12:20:45 further kernel: hpet clockevent registered
    Jan 26 12:20:45 further kernel: tsc: Fast TSC calibration using PIT
    Jan 26 12:20:45 further kernel: tsc: Detected 1896.600 MHz processor
    Jan 26 12:20:45 further kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 3794.25 BogoMIPS (lpj=6322000)
    Jan 26 12:20:45 further kernel: pid_max: default: 32768 minimum: 301
    Jan 26 12:20:45 further kernel: Security Framework initialized
    Jan 26 12:20:45 further kernel: AppArmor: AppArmor disabled by boot time parameter
    Jan 26 12:20:45 further kernel: Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
    Jan 26 12:20:45 further kernel: Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
    Jan 26 12:20:45 further kernel: Mount-cache hash table entries: 256
    Jan 26 12:20:45 further kernel: Initializing cgroup subsys cpuacct
    Jan 26 12:20:45 further kernel: Initializing cgroup subsys memory
    Jan 26 12:20:45 further kernel: Initializing cgroup subsys devices
    Jan 26 12:20:45 further kernel: Initializing cgroup subsys freezer
    Jan 26 12:20:45 further kernel: Initializing cgroup subsys net_cls
    Jan 26 12:20:45 further kernel: Initializing cgroup subsys blkio
    Jan 26 12:20:45 further kernel: tseg: 008ff00000
    Jan 26 12:20:45 further kernel: CPU: Physical Processor ID: 0
    Jan 26 12:20:45 further kernel: CPU: Processor Core ID: 0
    Jan 26 12:20:45 further kernel: mce: CPU supports 6 MCE banks
    Jan 26 12:20:45 further kernel: [120B blob data]
    Jan 26 12:20:45 further kernel: Freeing SMP alternatives: 16k freed
    Jan 26 12:20:45 further kernel: ACPI: Core revision 20120913
    Jan 26 12:20:45 further kernel: ftrace: allocating 18585 entries in 73 pages
    Jan 26 12:20:45 further kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    Jan 26 12:20:45 further kernel: smpboot: CPU0: AMD A4-3300M APU with Radeon(tm) HD Graphics (fam: 12, model: 01, stepping: 00)
    Jan 26 12:20:45 further kernel: Performance Events: AMD PMU driver.
    Jan 26 12:20:45 further kernel: ... version: 0
    Jan 26 12:20:45 further kernel: ... bit width: 48
    Jan 26 12:20:45 further kernel: ... generic registers: 4
    Jan 26 12:20:45 further kernel: ... value mask: 0000ffffffffffff
    Jan 26 12:20:45 further kernel: ... max period: 00007fffffffffff
    Jan 26 12:20:45 further kernel: ... fixed-purpose events: 0
    Jan 26 12:20:45 further kernel: ... event mask: 000000000000000f
    Jan 26 12:20:45 further kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    Jan 26 12:20:45 further kernel: smpboot: Booting Node 0, Processors #1
    Jan 26 12:20:45 further kernel: Brought up 2 CPUs
    Jan 26 12:20:45 further kernel: smpboot: Total of 2 processors activated (7589.50 BogoMIPS)
    Jan 26 12:20:45 further kernel: devtmpfs: initialized
    Jan 26 12:20:45 further kernel: PM: Registering ACPI NVS region [mem 0x8f6c0000-0x8f702fff] (274432 bytes)
    Jan 26 12:20:45 further kernel: PM: Registering ACPI NVS region [mem 0x8f829000-0x8f838fff] (65536 bytes)
    Jan 26 12:20:45 further kernel: PM: Registering ACPI NVS region [mem 0x8f869000-0x8f871fff] (36864 bytes)
    Jan 26 12:20:45 further kernel: PM: Registering ACPI NVS region [mem 0x8f884000-0x8f891fff] (57344 bytes)
    Jan 26 12:20:45 further kernel: PM: Registering ACPI NVS region [mem 0x8f894000-0x8f89afff] (28672 bytes)
    Jan 26 12:20:45 further kernel: PM: Registering ACPI NVS region [mem 0x8f89e000-0x8f8a6fff] (36864 bytes)
    Jan 26 12:20:45 further kernel: PM: Registering ACPI NVS region [mem 0x8f8ce000-0x8fad0fff] (2109440 bytes)
    Jan 26 12:20:45 further kernel: NET: Registered protocol family 16
    Jan 26 12:20:45 further kernel: ACPI: bus type pci registered
    Jan 26 12:20:45 further kernel: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
    Jan 26 12:20:45 further kernel: PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
    Jan 26 12:20:45 further kernel: PCI: Using configuration type 1 for base access
    Jan 26 12:20:45 further kernel: bio: create slab <bio-0> at 0
    Jan 26 12:20:45 further kernel: ACPI: Added _OSI(Module Device)
    Jan 26 12:20:45 further kernel: ACPI: Added _OSI(Processor Device)
    Jan 26 12:20:45 further kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
    Jan 26 12:20:45 further kernel: ACPI: Added _OSI(Processor Aggregator Device)
    Jan 26 12:20:45 further kernel: ACPI: EC: Look up EC in DSDT
    Jan 26 12:20:45 further kernel: ACPI: Executed 1 blocks of module-level executable AML code
    Jan 26 12:20:45 further kernel: ACPI: Interpreter enabled
    Jan 26 12:20:45 further kernel: ACPI: (supports S0 S3 S4 S5)
    Jan 26 12:20:45 further kernel: ACPI: Using IOAPIC for interrupt routing
    Jan 26 12:20:45 further kernel: [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness
    Jan 26 12:20:45 further kernel: [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness
    Jan 26 12:20:45 further kernel: ACPI: EC: GPE = 0x3, I/O: command/status = 0x66, data = 0x62
    Jan 26 12:20:45 further kernel: ACPI: No dock devices found.
    Jan 26 12:20:45 further kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    Jan 26 12:20:45 further kernel: \_SB_.PCI0:_OSC request failed
    Jan 26 12:20:45 further kernel: _OSC request data:1 8 1f
    Jan 26 12:20:45 further kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    Jan 26 12:20:45 further kernel: PCI host bridge to bus 0000:00
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x03af]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: root bus resource [io 0x03e0-0x0cf7]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: root bus resource [io 0x03b0-0x03df]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: root bus resource [io 0x1778-0xffff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000dffff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: root bus resource [mem 0xb0000000-0xffffffff]
    Jan 26 12:20:45 further kernel: pci 0000:00:00.0: [1022:1705] type 00 class 0x060000
    Jan 26 12:20:45 further kernel: pci 0000:00:01.0: [1002:9648] type 00 class 0x030000
    Jan 26 12:20:45 further kernel: pci 0000:00:01.0: reg 10: [mem 0xb0000000-0xbfffffff pref]
    Jan 26 12:20:45 further kernel: pci 0000:00:01.0: reg 14: [io 0xf000-0xf0ff]
    Jan 26 12:20:45 further kernel: pci 0000:00:01.0: reg 18: [mem 0xfeb00000-0xfeb3ffff]
    Jan 26 12:20:45 further kernel: pci 0000:00:01.0: supports D1 D2
    Jan 26 12:20:45 further kernel: pci 0000:00:01.1: [1002:1714] type 00 class 0x040300
    Jan 26 12:20:45 further kernel: pci 0000:00:01.1: reg 10: [mem 0xfeb44000-0xfeb47fff]
    Jan 26 12:20:45 further kernel: pci 0000:00:01.1: supports D1 D2
    Jan 26 12:20:45 further kernel: pci 0000:00:02.0: [1022:1707] type 01 class 0x060400
    Jan 26 12:20:45 further kernel: pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
    Jan 26 12:20:45 further kernel: pci 0000:00:04.0: [1022:1709] type 01 class 0x060400
    Jan 26 12:20:45 further kernel: pci 0000:00:04.0: PME# supported from D0 D3hot D3cold
    Jan 26 12:20:45 further kernel: pci 0000:00:05.0: [1022:170a] type 01 class 0x060400
    Jan 26 12:20:45 further kernel: pci 0000:00:05.0: PME# supported from D0 D3hot D3cold
    Jan 26 12:20:45 further kernel: pci 0000:00:10.0: [1022:7812] type 00 class 0x0c0330
    Jan 26 12:20:45 further kernel: pci 0000:00:10.0: reg 10: [mem 0xfeb48000-0xfeb49fff 64bit]
    Jan 26 12:20:45 further kernel: pci 0000:00:10.0: PME# supported from D0 D3hot D3cold
    Jan 26 12:20:45 further kernel: pci 0000:00:11.0: [1022:7801] type 00 class 0x010601
    Jan 26 12:20:45 further kernel: pci 0000:00:11.0: reg 10: [io 0xf140-0xf147]
    Jan 26 12:20:45 further kernel: pci 0000:00:11.0: reg 14: [io 0xf130-0xf133]
    Jan 26 12:20:45 further kernel: pci 0000:00:11.0: reg 18: [io 0xf120-0xf127]
    Jan 26 12:20:45 further kernel: pci 0000:00:11.0: reg 1c: [io 0xf110-0xf113]
    Jan 26 12:20:45 further kernel: pci 0000:00:11.0: reg 20: [io 0xf100-0xf10f]
    Jan 26 12:20:45 further kernel: pci 0000:00:11.0: reg 24: [mem 0xfeb4d000-0xfeb4d7ff]
    Jan 26 12:20:45 further kernel: pci 0000:00:12.0: [1022:7807] type 00 class 0x0c0310
    Jan 26 12:20:45 further kernel: pci 0000:00:12.0: reg 10: [mem 0xfeb4c000-0xfeb4cfff]
    Jan 26 12:20:45 further kernel: pci 0000:00:12.2: [1022:7808] type 00 class 0x0c0320
    Jan 26 12:20:45 further kernel: pci 0000:00:12.2: reg 10: [mem 0xfeb4b000-0xfeb4b0ff]
    Jan 26 12:20:45 further kernel: pci 0000:00:12.2: supports D1 D2
    Jan 26 12:20:45 further kernel: pci 0000:00:12.2: PME# supported from D0 D1 D2 D3hot
    Jan 26 12:20:45 further kernel: pci 0000:00:14.0: [1022:780b] type 00 class 0x0c0500
    Jan 26 12:20:45 further kernel: pci 0000:00:14.2: [1022:780d] type 00 class 0x040300
    Jan 26 12:20:45 further kernel: pci 0000:00:14.2: reg 10: [mem 0xfeb40000-0xfeb43fff 64bit]
    Jan 26 12:20:45 further kernel: pci 0000:00:14.2: PME# supported from D0 D3hot D3cold
    Jan 26 12:20:45 further kernel: pci 0000:00:14.3: [1022:780e] type 00 class 0x060100
    Jan 26 12:20:45 further kernel: pci 0000:00:14.4: [1022:780f] type 01 class 0x060401
    Jan 26 12:20:45 further kernel: pci 0000:00:14.7: [1022:7806] type 00 class 0x080501
    Jan 26 12:20:45 further kernel: pci 0000:00:14.7: reg 10: [mem 0xfeb4a000-0xfeb4a0ff 64bit]
    Jan 26 12:20:45 further kernel: pci 0000:00:18.0: [1022:1700] type 00 class 0x060000
    Jan 26 12:20:45 further kernel: pci 0000:00:18.1: [1022:1701] type 00 class 0x060000
    Jan 26 12:20:45 further kernel: pci 0000:00:18.2: [1022:1702] type 00 class 0x060000
    Jan 26 12:20:45 further kernel: pci 0000:00:18.3: [1022:1703] type 00 class 0x060000
    Jan 26 12:20:45 further kernel: pci 0000:00:18.4: [1022:1704] type 00 class 0x060000
    Jan 26 12:20:45 further kernel: pci 0000:00:18.5: [1022:1718] type 00 class 0x060000
    Jan 26 12:20:45 further kernel: pci 0000:00:18.6: [1022:1716] type 00 class 0x060000
    Jan 26 12:20:45 further kernel: pci 0000:00:18.7: [1022:1719] type 00 class 0x060000
    Jan 26 12:20:45 further kernel: pci 0000:01:00.0: [1002:6741] type 00 class 0x030000
    Jan 26 12:20:45 further kernel: pci 0000:01:00.0: reg 10: [mem 0xc0000000-0xcfffffff 64bit pref]
    Jan 26 12:20:45 further kernel: pci 0000:01:00.0: reg 18: [mem 0xfea20000-0xfea3ffff 64bit]
    Jan 26 12:20:45 further kernel: pci 0000:01:00.0: reg 20: [io 0xe000-0xe0ff]
    Jan 26 12:20:45 further kernel: pci 0000:01:00.0: reg 30: [mem 0xfea00000-0xfea1ffff pref]
    Jan 26 12:20:45 further kernel: pci 0000:01:00.0: supports D1 D2
    Jan 26 12:20:45 further kernel: pci 0000:00:02.0: PCI bridge to [bus 01]
    Jan 26 12:20:45 further kernel: pci 0000:00:02.0: bridge window [io 0xe000-0xefff]
    Jan 26 12:20:45 further kernel: pci 0000:00:02.0: bridge window [mem 0xfea00000-0xfeafffff]
    Jan 26 12:20:45 further kernel: pci 0000:00:02.0: bridge window [mem 0xc0000000-0xcfffffff 64bit pref]
    Jan 26 12:20:45 further kernel: pci 0000:02:00.0: [10ec:8168] type 00 class 0x020000
    Jan 26 12:20:45 further kernel: pci 0000:02:00.0: reg 10: [io 0xd000-0xd0ff]
    Jan 26 12:20:45 further kernel: pci 0000:02:00.0: reg 18: [mem 0xd0004000-0xd0004fff 64bit pref]
    Jan 26 12:20:45 further kernel: pci 0000:02:00.0: reg 20: [mem 0xd0000000-0xd0003fff 64bit pref]
    Jan 26 12:20:45 further kernel: pci 0000:02:00.0: supports D1 D2
    Jan 26 12:20:45 further kernel: pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    Jan 26 12:20:45 further kernel: pci 0000:00:04.0: PCI bridge to [bus 02]
    Jan 26 12:20:45 further kernel: pci 0000:00:04.0: bridge window [io 0xd000-0xdfff]
    Jan 26 12:20:45 further kernel: pci 0000:00:04.0: bridge window [mem 0xd0000000-0xd00fffff 64bit pref]
    Jan 26 12:20:45 further kernel: pci 0000:03:00.0: [168c:002b] type 00 class 0x028000
    Jan 26 12:20:45 further kernel: pci 0000:03:00.0: reg 10: [mem 0xfe900000-0xfe90ffff 64bit]
    Jan 26 12:20:45 further kernel: pci 0000:03:00.0: supports D1
    Jan 26 12:20:45 further kernel: pci 0000:03:00.0: PME# supported from D0 D1 D3hot D3cold
    Jan 26 12:20:45 further kernel: pci 0000:00:05.0: PCI bridge to [bus 03]
    Jan 26 12:20:45 further kernel: pci 0000:00:05.0: bridge window [mem 0xfe900000-0xfe9fffff]
    Jan 26 12:20:45 further kernel: pci 0000:00:14.4: PCI bridge to [bus 04] (subtractive decode)
    Jan 26 12:20:45 further kernel: pci 0000:00:14.4: bridge window [io 0x0000-0x03af] (subtractive decode)
    Jan 26 12:20:45 further kernel: pci 0000:00:14.4: bridge window [io 0x03e0-0x0cf7] (subtractive decode)
    Jan 26 12:20:45 further kernel: pci 0000:00:14.4: bridge window [io 0x03b0-0x03df] (subtractive decode)
    Jan 26 12:20:45 further kernel: pci 0000:00:14.4: bridge window [io 0x1778-0xffff] (subtractive decode)
    Jan 26 12:20:45 further kernel: pci 0000:00:14.4: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
    Jan 26 12:20:45 further kernel: pci 0000:00:14.4: bridge window [mem 0x000c0000-0x000dffff] (subtractive decode)
    Jan 26 12:20:45 further kernel: pci 0000:00:14.4: bridge window [mem 0xb0000000-0xffffffff] (subtractive decode)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.BR14._PRT]
    Jan 26 12:20:45 further kernel: \_SB_.PCI0:_OSC request failed
    Jan 26 12:20:45 further kernel: _OSC request data:1 1f 1f
    Jan 26 12:20:45 further kernel: pci0000:00: ACPI _OSC support notification failed, disabling PCIe ASPM
    Jan 26 12:20:45 further kernel: pci0000:00: Unable to request _OSC control (_OSC support mask: 0x08)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN24] (IRQs *24)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN25] (IRQs *25)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN26] (IRQs *26)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN27] (IRQs *27)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN28] (IRQs *28)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN29] (IRQs *29)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN30] (IRQs *30)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN31] (IRQs *31)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN32] (IRQs *32)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN33] (IRQs *33)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN34] (IRQs *34)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN35] (IRQs *35)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN36] (IRQs *36)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN37] (IRQs *37)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN38] (IRQs *38)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN39] (IRQs *39)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN40] (IRQs *40)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN41] (IRQs *41)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN42] (IRQs *42)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN43] (IRQs *43)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN44] (IRQs *44)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN45] (IRQs *45)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN46] (IRQs *46)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN47] (IRQs *47)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN48] (IRQs *48)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN49] (IRQs *49)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN50] (IRQs *50)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN51] (IRQs *51)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN52] (IRQs *52)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN53] (IRQs *53)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN54] (IRQs *54)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LN55] (IRQs *55)
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 4 5 7 10 11 14 15) *0
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 4 5 7 10 11 14 15) *0
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 4 5 7 10 11 14 15) *0
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 4 5 7 10 11 14 15) *0
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 4 5 7 10 11 14 15) *0
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 4 5 7 10 11 14 15) *0
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 4 5 7 10 11 14 15) *0
    Jan 26 12:20:45 further kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 4 5 7 10 11 14 15) *0
    Jan 26 12:20:45 further kernel: vgaarb: device added: PCI:0000:00:01.0,decodes=io+mem,owns=io+mem,locks=none
    Jan 26 12:20:45 further kernel: vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=none,locks=none
    Jan 26 12:20:45 further kernel: vgaarb: loaded
    Jan 26 12:20:45 further kernel: vgaarb: bridge control possible 0000:01:00.0
    Jan 26 12:20:45 further kernel: vgaarb: no bridge control possible 0000:00:01.0
    Jan 26 12:20:45 further kernel: PCI: Using ACPI for IRQ routing
    Jan 26 12:20:45 further kernel: PCI: pci_cache_line_size set to 64 bytes
    Jan 26 12:20:45 further kernel: e820: reserve RAM buffer [mem 0x0009d800-0x0009ffff]
    Jan 26 12:20:45 further kernel: e820: reserve RAM buffer [mem 0x8f6c0000-0x8fffffff]
    Jan 26 12:20:45 further kernel: e820: reserve RAM buffer [mem 0x8f869000-0x8fffffff]
    Jan 26 12:20:45 further kernel: e820: reserve RAM buffer [mem 0x8fd46000-0x8fffffff]
    Jan 26 12:20:45 further kernel: e820: reserve RAM buffer [mem 0x8ff00000-0x8fffffff]
    Jan 26 12:20:45 further kernel: e820: reserve RAM buffer [mem 0x14f000000-0x14fffffff]
    Jan 26 12:20:45 further kernel: NetLabel: Initializing
    Jan 26 12:20:45 further kernel: NetLabel: domain hash size = 128
    Jan 26 12:20:45 further kernel: NetLabel: protocols = UNLABELED CIPSOv4
    Jan 26 12:20:45 further kernel: NetLabel: unlabeled traffic allowed by default
    Jan 26 12:20:45 further kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
    Jan 26 12:20:45 further kernel: hpet0: 3 comparators, 32-bit 14.318180 MHz counter
    Jan 26 12:20:45 further kernel: Switching to clocksource hpet
    Jan 26 12:20:45 further kernel: pnp: PnP ACPI init
    Jan 26 12:20:45 further kernel: ACPI: bus type pnp registered
    Jan 26 12:20:45 further kernel: pnp 00:00: [bus 00-ff]
    Jan 26 12:20:45 further kernel: pnp 00:00: [io 0x0cf8-0x0cff]
    Jan 26 12:20:45 further kernel: pnp 00:00: [io 0x0000-0x03af window]
    Jan 26 12:20:45 further kernel: pnp 00:00: [io 0x03e0-0x0cf7 window]
    Jan 26 12:20:45 further kernel: pnp 00:00: [io 0x03b0-0x03df window]
    Jan 26 12:20:45 further kernel: pnp 00:00: [io 0x1778-0xffff window]
    Jan 26 12:20:45 further kernel: pnp 00:00: [mem 0x000a0000-0x000bffff window]
    Jan 26 12:20:45 further kernel: pnp 00:00: [mem 0x000c0000-0x000dffff window]
    Jan 26 12:20:45 further kernel: pnp 00:00: [mem 0xb0000000-0xffffffff window]
    Jan 26 12:20:45 further kernel: pnp 00:00: [mem 0x00000000 window]
    Jan 26 12:20:45 further kernel: pnp 00:00: Plug and Play ACPI device, IDs PNP0a03 (active)
    Jan 26 12:20:45 further kernel: pnp 00:01: [mem 0xe0000000-0xefffffff]
    Jan 26 12:20:45 further kernel: system 00:01: [mem 0xe0000000-0xefffffff] has been reserved
    Jan 26 12:20:45 further kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c01 (active)
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0010-0x001f]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0022-0x003f]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0063]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0065]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0067-0x006f]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0072-0x007f]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0080]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0084-0x0086]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0088]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x008c-0x008e]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0090-0x009f]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x00a2-0x00bf]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x00b1]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x00e0-0x00ef]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x04d0-0x04d1]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x040b]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x04d6]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0c00-0x0c01]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0c14]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0c50-0x0c51]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0c52]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0c6c]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0c6f]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0cd0-0x0cd1]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0cd2-0x0cd3]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0cd4-0x0cd5]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0cd6-0x0cd7]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0cd8-0x0cdf]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0800-0x089f]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0000-0xffffffffffffffff disabled]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0000-0x000f]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0b20-0x0b3f]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0900-0x090f]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0910-0x091f]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0xfe00-0xfefe]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0060-0x005f disabled]
    Jan 26 12:20:45 further kernel: pnp 00:02: [io 0x0064-0x0063 disabled]
    Jan 26 12:20:45 further kernel: pnp 00:02: [mem 0xfec00000-0xfec00fff]
    Jan 26 12:20:45 further kernel: pnp 00:02: [mem 0xfee00000-0xfee00fff]
    Jan 26 12:20:45 further kernel: pnp 00:02: [mem 0xfed80000-0xfed8ffff]
    Jan 26 12:20:45 further kernel: pnp 00:02: [mem 0xfed61000-0xfed70fff]
    Jan 26 12:20:45 further kernel: pnp 00:02: [mem 0xfec10000-0xfec10fff]
    Jan 26 12:20:45 further kernel: pnp 00:02: [mem 0xfed00000-0xfed00fff]
    Jan 26 12:20:45 further kernel: pnp 00:02: [mem 0xff000000-0xffffffff]
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x04d0-0x04d1] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x040b] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x04d6] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0c00-0x0c01] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0c14] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0c50-0x0c51] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0c52] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0c6c] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0c6f] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0cd0-0x0cd1] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0cd2-0x0cd3] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0cd4-0x0cd5] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0cd6-0x0cd7] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0cd8-0x0cdf] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0800-0x089f] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0b20-0x0b3f] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0900-0x090f] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0x0910-0x091f] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [io 0xfe00-0xfefe] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [mem 0xfec00000-0xfec00fff] could not be reserved
    Jan 26 12:20:45 further kernel: system 00:02: [mem 0xfee00000-0xfee00fff] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [mem 0xfed80000-0xfed8ffff] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [mem 0xfed61000-0xfed70fff] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [mem 0xfec10000-0xfec10fff] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [mem 0xfed00000-0xfed00fff] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: [mem 0xff000000-0xffffffff] has been reserved
    Jan 26 12:20:45 further kernel: system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active)
    Jan 26 12:20:45 further kernel: pnp 00:03: [dma 4]
    Jan 26 12:20:45 further kernel: pnp 00:03: [io 0x0000-0x000f]
    Jan 26 12:20:45 further kernel: pnp 00:03: [io 0x0081-0x0083]
    Jan 26 12:20:45 further kernel: pnp 00:03: [io 0x0087]
    Jan 26 12:20:45 further kernel: pnp 00:03: [io 0x0089-0x008b]
    Jan 26 12:20:45 further kernel: pnp 00:03: [io 0x008f]
    Jan 26 12:20:45 further kernel: pnp 00:03: [io 0x00c0-0x00df]
    Jan 26 12:20:45 further kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0200 (active)
    Jan 26 12:20:45 further kernel: pnp 00:04: [io 0x0070-0x0071]
    Jan 26 12:20:45 further kernel: pnp 00:04: [irq 8]
    Jan 26 12:20:45 further kernel: pnp 00:04: Plug and Play ACPI device, IDs PNP0b00 (active)
    Jan 26 12:20:45 further kernel: pnp 00:05: [io 0x0061]
    Jan 26 12:20:45 further kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0800 (active)
    Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x0010-0x001f]
    Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x0022-0x003f]
    Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x0044-0x005f]
    Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x0072-0x007f]
    Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x0080]
    Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x0084-0x0086]
    Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x0088]
    Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x008c-0x008e]
    Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x0090-0x009f]
    Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x00a2-0x00bf]
    Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x00e0-0x00ef]
    Jan 26 12:20:45 further kernel: pnp 00:06: [io 0x04d0-0x04d1]
    Jan 26 12:20:45 further kernel: system 00:06: [io 0x04d0-0x04d1] has been reserved
    Jan 26 12:20:45 further kernel: system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
    Jan 26 12:20:45 further kernel: pnp 00:07: [io 0x00f0-0x00ff]
    Jan 26 12:20:45 further kernel: pnp 00:07: [irq 13]
    Jan 26 12:20:45 further kernel: pnp 00:07: Plug and Play ACPI device, IDs PNP0c04 (active)
    Jan 26 12:20:45 further kernel: pnp 00:08: [io 0x1770-0x1777]
    Jan 26 12:20:45 further kernel: system 00:08: [io 0x1770-0x1777] has been reserved
    Jan 26 12:20:45 further kernel: system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
    Jan 26 12:20:45 further kernel: pnp 00:09: [irq 12]
    Jan 26 12:20:45 further kernel: pnp 00:09: Plug and Play ACPI device, IDs ETD0102 PNP0f13 (active)
    Jan 26 12:20:45 further kernel: pnp 00:0a: [io 0x0060]
    Jan 26 12:20:45 further kernel: pnp 00:0a: [io 0x0064]
    Jan 26 12:20:45 further kernel: pnp 00:0a: [irq 1]
    Jan 26 12:20:45 further kernel: pnp 00:0a: Plug and Play ACPI device, IDs PNP0303 PNP030b (active)
    Jan 26 12:20:45 further kernel: pnp 00:0b: [mem 0x00000000-0xffffffffffffffff disabled]
    Jan 26 12:20:45 further kernel: pnp 00:0b: [mem 0x00000000-0xffffffffffffffff disabled]
    Jan 26 12:20:45 further kernel: system 00:0b: Plug and Play ACPI device, IDs PNP0c02 (active)
    Jan 26 12:20:45 further kernel: pnp 00:0c: [mem 0xfed00000-0xfed003ff]
    Jan 26 12:20:45 further kernel: pnp 00:0c: Plug and Play ACPI device, IDs PNP0103 (active)
    Jan 26 12:20:45 further kernel: pnp: PnP ACPI: found 13 devices
    Jan 26 12:20:45 further kernel: ACPI: ACPI bus type pnp unregistered
    Jan 26 12:20:45 further kernel: pci 0000:00:02.0: PCI bridge to [bus 01]
    Jan 26 12:20:45 further kernel: pci 0000:00:02.0: bridge window [io 0xe000-0xefff]
    Jan 26 12:20:45 further kernel: pci 0000:00:02.0: bridge window [mem 0xfea00000-0xfeafffff]
    Jan 26 12:20:45 further kernel: pci 0000:00:02.0: bridge window [mem 0xc0000000-0xcfffffff 64bit pref]
    Jan 26 12:20:45 further kernel: pci 0000:00:04.0: PCI bridge to [bus 02]
    Jan 26 12:20:45 further kernel: pci 0000:00:04.0: bridge window [io 0xd000-0xdfff]
    Jan 26 12:20:45 further kernel: pci 0000:00:04.0: bridge window [mem 0xd0000000-0xd00fffff 64bit pref]
    Jan 26 12:20:45 further kernel: pci 0000:00:05.0: PCI bridge to [bus 03]
    Jan 26 12:20:45 further kernel: pci 0000:00:05.0: bridge window [mem 0xfe900000-0xfe9fffff]
    Jan 26 12:20:45 further kernel: pci 0000:00:14.4: PCI bridge to [bus 04]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x03af]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: resource 5 [io 0x03e0-0x0cf7]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: resource 6 [io 0x03b0-0x03df]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: resource 7 [io 0x1778-0xffff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: resource 9 [mem 0x000c0000-0x000dffff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:00: resource 10 [mem 0xb0000000-0xffffffff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:01: resource 1 [mem 0xfea00000-0xfeafffff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:01: resource 2 [mem 0xc0000000-0xcfffffff 64bit pref]
    Jan 26 12:20:45 further kernel: pci_bus 0000:02: resource 0 [io 0xd000-0xdfff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:02: resource 2 [mem 0xd0000000-0xd00fffff 64bit pref]
    Jan 26 12:20:45 further kernel: pci_bus 0000:03: resource 1 [mem 0xfe900000-0xfe9fffff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:04: resource 4 [io 0x0000-0x03af]
    Jan 26 12:20:45 further kernel: pci_bus 0000:04: resource 5 [io 0x03e0-0x0cf7]
    Jan 26 12:20:45 further kernel: pci_bus 0000:04: resource 6 [io 0x03b0-0x03df]
    Jan 26 12:20:45 further kernel: pci_bus 0000:04: resource 7 [io 0x1778-0xffff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:04: resource 8 [mem 0x000a0000-0x000bffff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:04: resource 9 [mem 0x000c0000-0x000dffff]
    Jan 26 12:20:45 further kernel: pci_bus 0000:04: resource 10 [mem 0xb0000000-0xffffffff]
    Jan 26 12:20:45 further kernel: NET: Registered protocol family 2
    Jan 26 12:20:45 further kernel: TCP established hash table entries: 524288 (order: 11, 8388608 bytes)
    Jan 26 12:20:45 further kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
    Jan 26 12:20:45 further kernel: TCP: Hash tables configured (established 524288 bind 65536)
    Jan 26 12:20:45 further kernel: TCP: reno registered
    Jan 26 12:20:45 further kernel: UDP hash table entries: 2048 (order: 4, 65536 bytes)
    Jan 26 12:20:45 further kernel: UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
    Jan 26 12:20:45 further kernel: NET: Registered protocol family 1
    Jan 26 12:20:45 further kernel: pci 0000:00:01.0: Boot video device
    Jan 26 12:20:45 further kernel: PCI: CLS 64 bytes, default 64
    Jan 26 12:20:45 further kernel: Unpacking initramfs...
    Jan 26 12:20:45 further kernel: Freeing initrd memory: 2980k freed
    Jan 26 12:20:45 further kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
    Jan 26 12:20:45 further kernel: software IO TLB [mem 0x8b6c0000-0x8f6bffff] (64MB) mapped at [ffff88008b6c0000-ffff88008f6bffff]
    Jan 26 12:20:45 further kernel: LVT offset 0 assigned for vector 0x400
    Jan 26 12:20:45 further kernel: perf: AMD IBS detected (0x000000ff)
    Jan 26 12:20:45 further kernel: audit: initializing netlink socket (disabled)
    Jan 26 12:20:45 further kernel: type=2000 audit(1359202838.726:1): initialized
    Jan 26 12:20:45 further kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
    Jan 26 12:20:45 further kernel: VFS: Disk quotas dquot_6.5.2
    Jan 26 12:20:45 further kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    Jan 26 12:20:45 further kernel: msgmni has been set to 6857
    Jan 26 12:20:45 further kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    Jan 26 12:20:45 further kernel: io scheduler noop registered
    Jan 26 12:20:45 further kernel: io scheduler deadline registered
    Jan 26 12:20:45 further kernel: io scheduler cfq registered (default)
    Jan 26 12:20:45 further kernel: GHES: HEST is not enabled!
    Jan 26 12:20:45 further kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    Jan 26 12:20:45 further kernel: Linux agpgart interface v0.103
    Jan 26 12:20:45 further kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
    Jan 26 12:20:45 further kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
    Jan 26 12:20:45 further kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
    Jan 26 12:20:45 further kernel: mousedev: PS/2 mouse device common for all mice
    Jan 26 12:20:45 further kernel: rtc_cmos 00:04: RTC can wake from S4
    Jan 26 12:20:45 further kernel: rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
    Jan 26 12:20:45 further kernel: rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
    Jan 26 12:20:45 further kernel: cpuidle: using governor ladder
    Jan 26 12:20:45 further kernel: cpuidle: using governor menu
    Jan 26 12:20:45 further kernel: drop_monitor: Initializing network drop monitor service
    Jan 26 12:20:45 further kernel: TCP: cubic registered
    Jan 26 12:20:45 further kernel: NET: Registered protocol family 10
    Jan 26 12:20:45 further kernel: NET: Registered protocol family 17
    Jan 26 12:20:45 further kernel: Key type dns_resolver registered
    Jan 26 12:20:45 further kernel: PM: Hibernation image not present or could not be loaded.
    Jan 26 12:20:45 further kernel: registered taskstats version 1
    Jan 26 12:20:45 further kernel: rtc_cmos 00:04: setting system clock to 2013-01-26 12:20:39 UTC (1359202839)
    Jan 26 12:20:45 further kernel: Freeing unused kernel memory: 808k freed
    Jan 26 12:20:45 further kernel: Write protecting the kernel read-only data: 8192k
    Jan 26 12:20:45 further kernel: Freeing unused kernel memory: 1300k freed
    Jan 26 12:20:45 further kernel: Freeing unused kernel memory: 492k freed
    Jan 26 12:20:45 further kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
    Jan 26 12:20:45 further systemd-udevd[46]: starting version 197
    Jan 26 12:20:45 further kernel: ACPI: bus type usb registered
    Jan 26 12:20:45 further kernel: usbcore: registered new interface driver usbfs
    Jan 26 12:20:45 further kernel: usbcore: registered new interface driver hub
    Jan 26 12:20:45 further kernel: SCSI subsystem initialized
    Jan 26 12:20:45 further kernel: usbcore: registered new device driver usb
    Jan 26 12:20:45 further kernel: sdhci: Secure Digital Host Controller Interface driver
    Jan 26 12:20:45 further kernel: sdhci: Copyright(c) Pierre Ossman
    Jan 26 12:20:45 further kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    Jan 26 12:20:45 further kernel: ehci_hcd 0000:00:12.2: EHCI Host Controller
    Jan 26 12:20:45 further kernel: ehci_hcd 0000:00:12.2: new USB bus registered, assigned bus number 1
    Jan 26 12:20:45 further kernel: QUIRK: Enable AMD PLL fix
    Jan 26 12:20:45 further kernel: ehci_hcd 0000:00:12.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
    Jan 26 12:20:45 further kernel: ehci_hcd 0000:00:12.2: debug port 1
    Jan 26 12:20:45 further kernel: ehci_hcd 0000:00:12.2: irq 17, io mem 0xfeb4b000
    Jan 26 12:20:45 further kernel: ACPI: bus type scsi registered
    Jan 26 12:20:45 further kernel: libata version 3.00 loaded.
    Jan 26 12:20:45 further kernel: ehci_hcd 0000:00:12.2: USB 2.0 started, EHCI 1.00
    Jan 26 12:20:45 further kernel: hub 1-0:1.0: USB hub found
    Jan 26 12:20:45 further kernel: hub 1-0:1.0: 5 ports detected
    Jan 26 12:20:45 further kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    Jan 26 12:20:45 further kernel: ohci_hcd 0000:00:12.0: OHCI Host Controller
    Jan 26 12:20:45 further kernel: ohci_hcd 0000:00:12.0: new USB bus registered, assigned bus number 2
    Jan 26 12:20:45 further kernel: ohci_hcd 0000:00:12.0: irq 18, io mem 0xfeb4c000
    Jan 26 12:20:45 further kernel: hub 2-0:1.0: USB hub found
    Jan 26 12:20:45 further kernel: hub 2-0:1.0: 5 ports detected
    Jan 26 12:20:45 further kernel: xhci_hcd 0000:00:10.0: xHCI Host Controller
    Jan 26 12:20:45 further kernel: xhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 3
    Jan 26 12:20:45 further kernel: xhci_hcd 0000:00:10.0: irq 18, io mem 0xfeb48000
    Jan 26 12:20:45 further kernel: xhci_hcd 0000:00:10.0: irq 40 for MSI/MSI-X
    Jan 26 12:20:45 further kernel: xhci_hcd 0000:00:10.0: irq 41 for MSI/MSI-X
    Jan 26 12:20:45 further kernel: xhci_hcd 0000:00:10.0: irq 42 for MSI/MSI-X
    Jan 26 12:20:45 further kernel: xHCI xhci_add_endpoint called for root hub
    Jan 26 12:20:45 further kernel: xHCI xhci_check_bandwidth called for root hub
    Jan 26 12:20:45 further kernel: hub 3-0:1.0: USB hub found
    Jan 26 12:20:45 further kernel: hub 3-0:1.0: 2 ports detected
    Jan 26 12:20:45 further kernel: xhci_hcd 0000:00:10.0: xHCI Host Controller
    Jan 26 12:20:45 further kernel: xhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 4
    Jan 26 12:20:45 further kernel: xHCI xhci_add_endpoint called for root hub
    Jan 26 12:20:45 further kernel: xHCI xhci_check_bandwidth called for root hub
    Jan 26 12:20:45 further kernel: hub 4-0:1.0: USB hub found
    Jan 26 12:20:45 further kernel: hub 4-0:1.0: 2 ports detected
    Jan 26 12:20:45 further kernel: sdhci-pci 0000:00:14.7: SDHCI controller found [1022:7806] (rev 0)
    Jan 26 12:20:45 further kernel: Registered led device: mmc0::
    Jan 26 12:20:45 further kernel: mmc0: SDHCI controller on PCI [0000:00:14.7] using ADMA
    Jan 26 12:20:45 further kernel: ahci 0000:00:11.0: version 3.0
    Jan 26 12:20:45 further kernel: ahci 0000:00:11.0: irq 43 for MSI/MSI-X
    Jan 26 12:20:45 further kernel: ahci 0000:00:11.0: AHCI 0001.0300 32 slots 3 ports 3 Gbps 0x7 impl SATA mode
    Jan 26 12:20:45 further kernel: ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part sxs
    Jan 26 12:20:45 further kernel: scsi0 : ahci
    Jan 26 12:20:45 further kernel: scsi1 : ahci
    Jan 26 12:20:45 further kernel: scsi2 : ahci
    Jan 26 12:20:45 further kernel: ata1: SATA max UDMA/133 abar m2048@0xfeb4d000 port 0xfeb4d100 irq 43
    Jan 26 12:20:45 further kernel: ata2: SATA max UDMA/133 abar m2048@0xfeb4d000 port 0xfeb4d180 irq 43
    Jan 26 12:20:45 further kernel: ata3: SATA max UDMA/133 abar m2048@0xfeb4d000 port 0xfeb4d200 irq 43
    Jan 26 12:20:45 further kernel: usb 1-3: new high-speed USB device number 2 using ehci_hcd
    Jan 26 12:20:45 further kernel: ata3: SATA link down (SStatus 0 SControl 300)
    Jan 26 12:20:45 further kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Jan 26 12:20:45 further kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    Jan 26 12:20:45 further kernel: ata2.00: ATAPI: MATSHITADVD-RAM UJ8B0, 1.00, max UDMA/100
    Jan 26 12:20:45 further kernel: ata1.00: ATA-8: WDC WD5000BPVT-80HXZT3, 01.01A01, max UDMA/133
    Jan 26 12:20:45 further kernel: ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
    Jan 26 12:20:45 further kernel: ata1.00: failed to get Identify Device Data, Emask 0x1
    Jan 26 12:20:45 further kernel: ata2.00: configured for UDMA/100
    Jan 26 12:20:45 further kernel: ata1.00: failed to get Identify Device Data, Emask 0x1
    Jan 26 12:20:45 further kernel: ata1.00: configured for UDMA/133
    Jan 26 12:20:45 further kernel: scsi 0:0:0:0: Direct-Access ATA WDC WD5000BPVT-8 01.0 PQ: 0 ANSI: 5
    Jan 26 12:20:45 further kernel: scsi 1:0:0:0: CD-ROM MATSHITA DVD-RAM UJ8B0 1.00 PQ: 0 ANSI: 5
    Jan 26 12:20:45 further kernel: sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
    Jan 26 12:20:45 further kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks
    Jan 26 12:20:45 further kernel: sd 0:0:0:0: [sda] Write Protect is off
    Jan 26 12:20:45 further kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
    Jan 26 12:20:45 further kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Jan 26 12:20:45 further kernel: sda: sda1 sda2 sda3 < sda5 sda6 sda7 sda8 >
    Jan 26 12:20:45 further kernel: sd 0:0:0:0: [sda] Attached SCSI disk
    Jan 26 12:20:45 further kernel: sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
    Jan 26 12:20:45 further kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
    Jan 26 12:20:45 further kernel: sr 1:0:0:0: Attached scsi CD-ROM sr0
    Jan 26 12:20:45 further kernel: usb 1-5: new high-speed USB device number 4 using ehci_hcd
    Jan 26 12:20:45 further kernel: tsc: Refined TSC clocksource calibration: 1896.550 MHz
    Jan 26 12:20:45 further kernel: Switching to clocksource tsc
    Jan 26 12:20:45 further kernel: Initializing USB Mass Storage driver...
    Jan 26 12:20:45 further kernel: usbcore: registered new interface driver usb-storage
    Jan 26 12:20:45 further kernel: USB Mass Storage support registered.
    Jan 26 12:20:45 further kernel: usb 2-4: new full-speed USB device number 2 using ohci_hcd
    Jan 26 12:20:45 further kernel: EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
    Jan 26 12:20:45 further systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
    Jan 26 12:20:45 further systemd[1]: systemd 197 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
    Jan 26 12:20:45 further systemd[1]: Set hostname to <further>.
    Jan 26 12:20:45 further systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.
    Jan 26 12:20:45 further systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
    Jan 26 12:20:45 further systemd[1]: Started Forward Password Requests to Wall Directory Watch.
    Jan 26 12:20:45 further systemd[1]: Starting Remote File Systems.
    Jan 26 12:20:45 further systemd[1]: Reached target Remote File Systems.
    Jan 26 12:20:45 further systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
    Jan 26 12:20:45 further systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
    Jan 26 12:20:45 further systemd[1]: Starting Delayed Shutdown Socket.
    Jan 26 12:20:45 further systemd[1]: Listening on Delayed Shutdown Socket.
    Jan 26 12:20:45 further systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
    Jan 26 12:20:45 further systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    Jan 26 12:20:45 further systemd[1]: Starting udev Kernel Socket.
    Jan 26 12:20:45 further systemd[1]: Listening on udev Kernel Socket.
    Jan 26 12:20:45 further systemd[1]: Starting udev Control Socket.
    Jan 26 12:20:45 further systemd[1]: Listening on udev Control Socket.
    Jan 26 12:20:45 further systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
    Jan 26 12:20:45 further systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
    Jan 26 12:20:45 further systemd[1]: Starting Encrypted Volumes.
    Jan 26 12:20:45 further systemd[1]: Reached target Encrypted Volumes.
    Jan 26 12:20:45 further systemd[1]: Expecting device dev-disk-by\x2duuid-f71c0eee\x2da4ec\x2d43a0\x2d89c7\x2d51f13a79169a.device...
    Jan 26 12:20:45 further systemd[1]: Expecting device dev-disk-by\x2duuid-26f87130\x2d99b7\x2d4a00\x2d997c\x2de177c335f448.device...
    Jan 26 12:20:45 further systemd[1]: Expecting device dev-disk-by\x2duuid-6c6af8e9\x2dbd25\x2d463b\x2dae87\x2dc894d7b092b5.device...
    Jan 26 12:20:45 further systemd[1]: Starting Journal Socket.
    Jan 26 12:20:45 further systemd[1]: Listening on Journal Socket.
    Jan 26 12:20:45 further systemd[1]: Started File System Check on Root Device.
    Jan 26 12:20:45 further systemd[1]: Starting Remount Root and Kernel File Systems...
    Jan 26 12:20:45 further systemd[1]: Starting Load Kernel Modules...
    Jan 26 12:20:45 further systemd[1]: Mounting Huge Pages File System...
    Jan 26 12:20:45 further systemd[1]: Starting udev Coldplug all Devices...
    Jan 26 12:20:45 further systemd[1]: Started Set Up Additional Binary Formats.
    Jan 26 12:20:45 further systemd[1]: Starting Setup Virtual Console...
    Jan 26 12:20:45 further systemd[1]: Mounting POSIX Message Queue File System...
    Jan 26 12:20:45 further systemd[1]: Starting udev Kernel Device Manager...
    Jan 26 12:20:45 further systemd[1]: Starting Apply Kernel Variables...
    Jan 26 12:20:45 further systemd[1]: Mounting Debug File System...
    Jan 26 12:20:45 further systemd[1]: Starting Journal Service...
    Jan 26 12:20:45 further systemd[1]: Started Journal Service.
    Jan 26 12:20:45 further systemd-udevd[142]: starting version 197
    Jan 26 12:20:45 further systemd-journal[145]: Journal started
    Jan 26 12:20:45 further systemd[1]: Started Apply Kernel Variables.
    Jan 26 12:20:45 further systemd[1]: Mounted Debug File System.
    Jan 26 12:20:45 further systemd[1]: Mounted Huge Pages File System.
    Jan 26 12:20:45 further systemd[1]: Started udev Coldplug all Devices.
    Jan 26 12:20:45 further systemd[1]: Mounted POSIX Message Queue File System.
    Jan 26 12:20:45 further systemd[1]: Started udev Kernel Device Manager.
    Jan 26 12:20:45 further kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
    Jan 26 12:20:45 further kernel: ACPI: Power Button [PWRB]
    Jan 26 12:20:45 further kernel: input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
    Jan 26 12:20:45 further kernel: ACPI: Sleep Button [SLPB]
    Jan 26 12:20:45 further kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input3
    Jan 26 12:20:45 further kernel: ACPI: Lid Switch [LID]
    Jan 26 12:20:45 further kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
    Jan 26 12:20:45 further kernel: ACPI: Power Button [PWRF]
    Jan 26 12:20:45 further kernel: AMD IOMMUv2 driver by Joerg Roedel <[email protected]>
    Jan 26 12:20:45 further kernel: AMD IOMMUv2 functionality not available on this system
    Jan 26 12:20:45 further kernel: EXT4-fs (sda6): re-mounted. Opts: barrier=0
    Jan 26 12:20:45 further systemd[1]: Started Remount Root and Kernel File Systems.
    Jan 26 12:20:45 further systemd[1]: Starting Local File Systems (Pre).
    Jan 26 12:20:45 further systemd[1]: Reached target Local File Systems (Pre).
    Jan 26 12:20:45 further systemd[1]: Mounting /tmp...
    Jan 26 12:20:45 further systemd[1]: Starting Load Random Seed...
    Jan 26 12:20:45 further systemd[1]: Mounted /tmp.
    Jan 26 12:20:45 further kernel: fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
    Jan 26 12:20:45 further kernel: Disabling lock debugging due to kernel taint
    Jan 26 12:20:45 further systemd-modules-load[136]: Inserted module 'fglrx'
    Jan 26 12:20:45 further kernel: <6>[fglrx] Maximum main memory to use for locked dma buffers: 3278 MBytes.
    Jan 26 12:20:45 further kernel: <6>[fglrx] vendor: 1002 device: 9648 count: 1
    Jan 26 12:20:45 further kernel: <6>[fglrx] vendor: 1002 device: 6741 count: 2
    Jan 26 12:20:45 further kernel: <6>[fglrx] ioport: bar 1, base 0xf000, size: 0x100
    Jan 26 12:20:45 further kernel: <6>[fglrx] ioport: bar 4, base 0xe000, size: 0x100
    Jan 26 12:20:45 further kernel: pci 0000:01:00.0: enabling device (0000 -> 0003)
    Jan 26 12:20:45 further kernel: <6>[fglrx] Kernel PAT support is enabled
    Jan 26 12:20:45 further kernel: <6>[fglrx] module loaded - fglrx 9.1.11 [Dec 19 2012] with 2 minors
    Jan 26 12:20:45 further systemd[1]: Started Load Kernel Modules.
    Jan 26 12:20:45 further systemd[1]: Mounted FUSE Control File System.
    Jan 26 12:20:45 further systemd[1]: Mounted Configuration File System.
    Jan 26 12:20:45 further systemd[1]: Started Load Random Seed.
    Jan 26 12:20:45 further

    During boot there is a problem with your fglrx driver. It tries to use MSI interrupts instead of old pin-based method, but it is allready enabled and it warns you http://lxr.linux.no/linux+v3.7.4/drivers/pci/msi.c#L811 in line 828
    And during shutdown there is a problem with pci_msi_shutdown. Maybe this problems related with each other?
    try to disable globaly msi by adding nomsi to kernel options. If this help try to disable msi just for catalyst after boot by echo 0 in /sys/bus/pci/devices/[faulty device]/msi_bus
    try to raise debug level to see message dev_dbg(dev, "shutdown\n"); here http://lxr.linux.no/linux+v3.7.4/drivers/base/core.c#L , open an entry in bugzilla
    try do upgrade or downgrade catalyst if possible
    switch to open source driver

  • New to Apple have some questions.

    Im looking into getting a portable music device with a large capacity. So far the Ipod Classic is the best as far as price goes but i had a few more questions about its performance and such.
    First and for most Ive heard lots of people complain their Ipod broke down once they got it home or shortly there after, or they had any of a long list of troubles with the software. are these common issues or just the few speaking for the many?
    Also my friends and i swap music a lot so right now my collection is only at 10 gigs but im expecting it to grow quite rapidly, can i load all of the stuff i already have into Itunes or will i have to buy new songs from Itunes? ive never had that bit explained fully too me before. How does the Apple brand hold up to some of the other makers of large capacity mp3 players such as Zune and Creative Zen? And lastly are there any other issues i should be aware of as a newcomer to ipods? Thanks to all that can help answer my questions and give me a bit of advice.

    are these common issues or just the few speaking for the many?
    There are tens of millions of iPod owners. These are just a few vocal users who've been unlucky enough to receive a faulty device. Same goes for any electronic device - out of tens of millions of devices made, there's always a tiny chance one may have manufacturing defects - but the chances of getting one are miniscule.
    I've upgraded through 4 various iPod models over the years, and never had a problem with any of them. My old iPods are still in use by the people who I passed them onto. I've also bought a few iPods as gifts, and they're still going strong too.
    Also my friends and i swap music a lot
    Well, that's illegal as you don't own the copyright to the music to share it, so you probably shouldn't broadcast that fact!
    can i load all of the stuff i already have into Itunes
    Yes.
    How does the Apple brand hold up to some of the other makers of large capacity mp3 players such as Zune and Creative Zen?
    Well, I think the popularity of the iPod should speak for itself. If it wasn't a good product it would not have become so successful. iPods consistently get very high review scores.
    As you've only got 10gb of music at the moment, why not get a 32 or 64gb iPod touch? There'll be plenty of space for your music library to grow into, plus you get the best touchscreen mobile internet, email, wi-fi device on the planet. Everyone raves about the iPod touch - just Google for some reviews.

  • LVM Volumes not available after update

    Hi All!
    I haven't updated my system for about two months and today I updated it. Now I have the problem that I cannot boot properly. I have my root partition in an LVM volume and on boot I get the message
    ERROR: device 'UUID=xxx' not found. Skipping fs
    ERROR: Unable to find root device 'UUID=xxx'
    After that I land in the recovery shell. After some research I found, that "lvm lvdisplay" showed that my volumes where not available and I had to reenable them with "lvm vgchange -a y".
    Issuing any lvm command also produced the following warning:
    WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
    Anyway, after issuing the commands and exiting the recovery shell, the system booted again. However, I would prefer being able to boot without manual actions.
    Thanks in advance!
    Further information:
    vgdisplay
    --- Volume group ---
    VG Name ArchLVM
    System ID
    Format lvm2
    Metadata Areas 1
    Metadata Sequence No 3
    VG Access read/write
    VG Status resizable
    MAX LV 0
    Cur LV 2
    Open LV 1
    Max PV 0
    Cur PV 1
    Act PV 1
    VG Size 232.69 GiB
    PE Size 4.00 MiB
    Total PE 59568
    Alloc PE / Size 59568 / 232.69 GiB
    Free PE / Size 0 / 0
    VG UUID SoB3M1-v1fD-1abI-PNJ3-6IOn-FfdI-0RoLK5
    lvdisplay (LV Status was 'not available' right after booting)
    --- Logical volume ---
    LV Path /dev/ArchLVM/Swap
    LV Name Swap
    VG Name ArchLVM
    LV UUID XRYBrz-LojR-k6SD-XIxV-wHnY-f3VG-giKL6V
    LV Write Access read/write
    LV Creation host, time archiso, 2014-05-16 14:43:06 +0200
    LV Status available
    # open 0
    LV Size 8.00 GiB
    Current LE 2048
    Segments 1
    Allocation inherit
    Read ahead sectors auto
    - currently set to 256
    Block device 254:0
    --- Logical volume ---
    LV Path /dev/ArchLVM/Root
    LV Name Root
    VG Name ArchLVM
    LV UUID lpjDl4-Jqzu-ZWkq-Uphc-IaOo-6Rzd-cIh5yv
    LV Write Access read/write
    LV Creation host, time archiso, 2014-05-16 14:43:27 +0200
    LV Status available
    # open 1
    LV Size 224.69 GiB
    Current LE 57520
    Segments 1
    Allocation inherit
    Read ahead sectors auto
    - currently set to 256
    Block device 254:1
    /etc/fstab
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/mapper/ArchLVM-Root
    UUID=2db82d1a-47a4-4e30-a819-143e8fb75199 / ext4 rw,relatime,data=ordered 0 1
    #/dev/mapper/ArchLVM-Root / ext4 rw,relatime,data=ordered 0 1
    # /dev/sda1
    UUID=72691888-a781-4cdd-a98e-2613d87925d0 /boot ext2 rw,relatime 0 2
    /etc/mkinitcpio.conf
    # vim:set ft=sh
    # MODULES
    # The following modules are loaded before any boot hooks are
    # run. Advanced users may wish to specify all system modules
    # in this array. For instance:
    # MODULES="piix ide_disk reiserfs"
    MODULES=""
    # BINARIES
    # This setting includes any additional binaries a given user may
    # wish into the CPIO image. This is run last, so it may be used to
    # override the actual binaries included by a given hook
    # BINARIES are dependency parsed, so you may safely ignore libraries
    BINARIES=""
    # FILES
    # This setting is similar to BINARIES above, however, files are added
    # as-is and are not parsed in any way. This is useful for config files.
    FILES=""
    # HOOKS
    # This is the most important setting in this file. The HOOKS control the
    # modules and scripts added to the image, and what happens at boot time.
    # Order is important, and it is recommended that you do not change the
    # order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
    # help on a given hook.
    # 'base' is _required_ unless you know precisely what you are doing.
    # 'udev' is _required_ in order to automatically load modules
    # 'filesystems' is _required_ unless you specify your fs modules in MODULES
    # Examples:
    ## This setup specifies all modules in the MODULES setting above.
    ## No raid, lvm2, or encrypted root is needed.
    # HOOKS="base"
    ## This setup will autodetect all modules for your system and should
    ## work as a sane default
    # HOOKS="base udev autodetect block filesystems"
    ## This setup will generate a 'full' image which supports most systems.
    ## No autodetection is done.
    # HOOKS="base udev block filesystems"
    ## This setup assembles a pata mdadm array with an encrypted root FS.
    ## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
    # HOOKS="base udev block mdadm encrypt filesystems"
    ## This setup loads an lvm2 volume group on a usb device.
    # HOOKS="base udev block lvm2 filesystems"
    ## NOTE: If you have /usr on a separate partition, you MUST include the
    # usr, fsck and shutdown hooks.
    HOOKS="base udev autodetect modconf block lvm2 filesystems keyboard fsck"
    # COMPRESSION
    # Use this to compress the initramfs image. By default, gzip compression
    # is used. Use 'cat' to create an uncompressed image.
    #COMPRESSION="gzip"
    #COMPRESSION="bzip2"
    #COMPRESSION="lzma"
    #COMPRESSION="xz"
    #COMPRESSION="lzop"
    #COMPRESSION="lz4"
    # COMPRESSION_OPTIONS
    # Additional options for the compressor
    #COMPRESSION_OPTIONS=""
    /boot/grub/grub.cfg
    # DO NOT EDIT THIS FILE
    # It is automatically generated by grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    ### BEGIN /etc/grub.d/00_header ###
    insmod part_gpt
    insmod part_msdos
    if [ -s $prefix/grubenv ]; then
    load_env
    fi
    if [ "${next_entry}" ] ; then
    set default="${next_entry}"
    set next_entry=
    save_env next_entry
    set boot_once=true
    else
    set default="0"
    fi
    if [ x"${feature_menuentry_id}" = xy ]; then
    menuentry_id_option="--id"
    else
    menuentry_id_option=""
    fi
    export menuentry_id_option
    if [ "${prev_saved_entry}" ]; then
    set saved_entry="${prev_saved_entry}"
    save_env saved_entry
    set prev_saved_entry=
    save_env prev_saved_entry
    set boot_once=true
    fi
    function savedefault {
    if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
    fi
    function load_video {
    if [ x$feature_all_video_module = xy ]; then
    insmod all_video
    else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
    fi
    if [ x$feature_default_font_path = xy ] ; then
    font=unicode
    else
    insmod part_msdos
    insmod lvm
    insmod ext2
    set root='lvmid/SoB3M1-v1fD-1abI-PNJ3-6IOn-FfdI-0RoLK5/lpjDl4-Jqzu-ZWkq-Uphc-IaOo-6Rzd-cIh5yv'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint='lvmid/SoB3M1-v1fD-1abI-PNJ3-6IOn-FfdI-0RoLK5/lpjDl4-Jqzu-ZWkq-Uphc-IaOo-6Rzd-cIh5yv' 2db82d1a-47a4-4e30-a819-143e8fb75199
    else
    search --no-floppy --fs-uuid --set=root 2db82d1a-47a4-4e30-a819-143e8fb75199
    fi
    font="/usr/share/grub/unicode.pf2"
    fi
    if loadfont $font ; then
    set gfxmode=auto
    load_video
    insmod gfxterm
    fi
    terminal_input console
    terminal_output gfxterm
    if [ x$feature_timeout_style = xy ] ; then
    set timeout_style=menu
    set timeout=5
    # Fallback normal timeout code in case the timeout_style feature is
    # unavailable.
    else
    set timeout=5
    fi
    ### END /etc/grub.d/00_header ###
    ### BEGIN /etc/grub.d/10_linux ###
    menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-2db82d1a-47a4-4e30-a819-143e8fb75199' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 72691888-a781-4cdd-a98e-2613d87925d0
    else
    search --no-floppy --fs-uuid --set=root 72691888-a781-4cdd-a98e-2613d87925d0
    fi
    echo 'Loading Linux linux ...'
    linux /vmlinuz-linux root=UUID=2db82d1a-47a4-4e30-a819-143e8fb75199 rw quiet
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-linux.img
    submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-2db82d1a-47a4-4e30-a819-143e8fb75199' {
    menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-2db82d1a-47a4-4e30-a819-143e8fb75199' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 72691888-a781-4cdd-a98e-2613d87925d0
    else
    search --no-floppy --fs-uuid --set=root 72691888-a781-4cdd-a98e-2613d87925d0
    fi
    echo 'Loading Linux linux ...'
    linux /vmlinuz-linux root=UUID=2db82d1a-47a4-4e30-a819-143e8fb75199 rw quiet
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-linux.img
    menuentry 'Arch Linux, with Linux linux (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-2db82d1a-47a4-4e30-a819-143e8fb75199' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 72691888-a781-4cdd-a98e-2613d87925d0
    else
    search --no-floppy --fs-uuid --set=root 72691888-a781-4cdd-a98e-2613d87925d0
    fi
    echo 'Loading Linux linux ...'
    linux /vmlinuz-linux root=UUID=2db82d1a-47a4-4e30-a819-143e8fb75199 rw quiet
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-linux-fallback.img
    ### END /etc/grub.d/10_linux ###
    ### BEGIN /etc/grub.d/20_linux_xen ###
    ### END /etc/grub.d/20_linux_xen ###
    ### BEGIN /etc/grub.d/30_os-prober ###
    ### END /etc/grub.d/30_os-prober ###
    ### BEGIN /etc/grub.d/40_custom ###
    # This file provides an easy way to add custom menu entries. Simply type the
    # menu entries you want to add after this comment. Be careful not to change
    # the 'exec tail' line above.
    ### END /etc/grub.d/40_custom ###
    ### BEGIN /etc/grub.d/41_custom ###
    if [ -f ${config_directory}/custom.cfg ]; then
    source ${config_directory}/custom.cfg
    elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
    source $prefix/custom.cfg;
    fi
    ### END /etc/grub.d/41_custom ###
    ### BEGIN /etc/grub.d/60_memtest86+ ###
    ### END /etc/grub.d/60_memtest86+ ###
    Last edited by Kirodema (2014-07-16 07:31:34)

    use_lvmetad = 0
    lvm2-lvmetad is not enabled or running on my system. Shall I activate it?
    # This is an example configuration file for the LVM2 system.
    # It contains the default settings that would be used if there was no
    # /etc/lvm/lvm.conf file.
    # Refer to 'man lvm.conf' for further information including the file layout.
    # To put this file in a different directory and override /etc/lvm set
    # the environment variable LVM_SYSTEM_DIR before running the tools.
    # N.B. Take care that each setting only appears once if uncommenting
    # example settings in this file.
    # This section allows you to set the way the configuration settings are handled.
    config {
    # If enabled, any LVM2 configuration mismatch is reported.
    # This implies checking that the configuration key is understood
    # by LVM2 and that the value of the key is of a proper type.
    # If disabled, any configuration mismatch is ignored and default
    # value is used instead without any warning (a message about the
    # configuration key not being found is issued in verbose mode only).
    checks = 1
    # If enabled, any configuration mismatch aborts the LVM2 process.
    abort_on_errors = 0
    # Directory where LVM looks for configuration profiles.
    profile_dir = "/etc/lvm/profile"
    # This section allows you to configure which block devices should
    # be used by the LVM system.
    devices {
    # Where do you want your volume groups to appear ?
    dir = "/dev"
    # An array of directories that contain the device nodes you wish
    # to use with LVM2.
    scan = [ "/dev" ]
    # If set, the cache of block device nodes with all associated symlinks
    # will be constructed out of the existing udev database content.
    # This avoids using and opening any inapplicable non-block devices or
    # subdirectories found in the device directory. This setting is applied
    # to udev-managed device directory only, other directories will be scanned
    # fully. LVM2 needs to be compiled with udev support for this setting to
    # take effect. N.B. Any device node or symlink not managed by udev in
    # udev directory will be ignored with this setting on.
    obtain_device_list_from_udev = 1
    # If several entries in the scanned directories correspond to the
    # same block device and the tools need to display a name for device,
    # all the pathnames are matched against each item in the following
    # list of regular expressions in turn and the first match is used.
    preferred_names = [ ]
    # Try to avoid using undescriptive /dev/dm-N names, if present.
    # preferred_names = [ "^/dev/mpath/", "^/dev/mapper/mpath", "^/dev/[hs]d" ]
    # A filter that tells LVM2 to only use a restricted set of devices.
    # The filter consists of an array of regular expressions. These
    # expressions can be delimited by a character of your choice, and
    # prefixed with either an 'a' (for accept) or 'r' (for reject).
    # The first expression found to match a device name determines if
    # the device will be accepted or rejected (ignored). Devices that
    # don't match any patterns are accepted.
    # Be careful if there there are symbolic links or multiple filesystem
    # entries for the same device as each name is checked separately against
    # the list of patterns. The effect is that if the first pattern in the
    # list to match a name is an 'a' pattern for any of the names, the device
    # is accepted; otherwise if the first pattern in the list to match a name
    # is an 'r' pattern for any of the names it is rejected; otherwise it is
    # accepted.
    # Don't have more than one filter line active at once: only one gets used.
    # Run vgscan after you change this parameter to ensure that
    # the cache file gets regenerated (see below).
    # If it doesn't do what you expect, check the output of 'vgscan -vvvv'.
    # If lvmetad is used, then see "A note about device filtering while
    # lvmetad is used" comment that is attached to global/use_lvmetad setting.
    # By default we accept every block device:
    filter = [ "a/.*/" ]
    # Exclude the cdrom drive
    # filter = [ "r|/dev/cdrom|" ]
    # When testing I like to work with just loopback devices:
    # filter = [ "a/loop/", "r/.*/" ]
    # Or maybe all loops and ide drives except hdc:
    # filter =[ "a|loop|", "r|/dev/hdc|", "a|/dev/ide|", "r|.*|" ]
    # Use anchors if you want to be really specific
    # filter = [ "a|^/dev/hda8$|", "r/.*/" ]
    # Since "filter" is often overridden from command line, it is not suitable
    # for system-wide device filtering (udev rules, lvmetad). To hide devices
    # from LVM-specific udev processing and/or from lvmetad, you need to set
    # global_filter. The syntax is the same as for normal "filter"
    # above. Devices that fail the global_filter are not even opened by LVM.
    # global_filter = []
    # The results of the filtering are cached on disk to avoid
    # rescanning dud devices (which can take a very long time).
    # By default this cache is stored in the /etc/lvm/cache directory
    # in a file called '.cache'.
    # It is safe to delete the contents: the tools regenerate it.
    # (The old setting 'cache' is still respected if neither of
    # these new ones is present.)
    # N.B. If obtain_device_list_from_udev is set to 1 the list of
    # devices is instead obtained from udev and any existing .cache
    # file is removed.
    cache_dir = "/etc/lvm/cache"
    cache_file_prefix = ""
    # You can turn off writing this cache file by setting this to 0.
    write_cache_state = 1
    # Advanced settings.
    # List of pairs of additional acceptable block device types found
    # in /proc/devices with maximum (non-zero) number of partitions.
    # types = [ "fd", 16 ]
    # If sysfs is mounted (2.6 kernels) restrict device scanning to
    # the block devices it believes are valid.
    # 1 enables; 0 disables.
    sysfs_scan = 1
    # By default, LVM2 will ignore devices used as component paths
    # of device-mapper multipath devices.
    # 1 enables; 0 disables.
    multipath_component_detection = 1
    # By default, LVM2 will ignore devices used as components of
    # software RAID (md) devices by looking for md superblocks.
    # 1 enables; 0 disables.
    md_component_detection = 1
    # By default, if a PV is placed directly upon an md device, LVM2
    # will align its data blocks with the md device's stripe-width.
    # 1 enables; 0 disables.
    md_chunk_alignment = 1
    # Default alignment of the start of a data area in MB. If set to 0,
    # a value of 64KB will be used. Set to 1 for 1MiB, 2 for 2MiB, etc.
    # default_data_alignment = 1
    # By default, the start of a PV's data area will be a multiple of
    # the 'minimum_io_size' or 'optimal_io_size' exposed in sysfs.
    # - minimum_io_size - the smallest request the device can perform
    # w/o incurring a read-modify-write penalty (e.g. MD's chunk size)
    # - optimal_io_size - the device's preferred unit of receiving I/O
    # (e.g. MD's stripe width)
    # minimum_io_size is used if optimal_io_size is undefined (0).
    # If md_chunk_alignment is enabled, that detects the optimal_io_size.
    # This setting takes precedence over md_chunk_alignment.
    # 1 enables; 0 disables.
    data_alignment_detection = 1
    # Alignment (in KB) of start of data area when creating a new PV.
    # md_chunk_alignment and data_alignment_detection are disabled if set.
    # Set to 0 for the default alignment (see: data_alignment_default)
    # or page size, if larger.
    data_alignment = 0
    # By default, the start of the PV's aligned data area will be shifted by
    # the 'alignment_offset' exposed in sysfs. This offset is often 0 but
    # may be non-zero; e.g.: certain 4KB sector drives that compensate for
    # windows partitioning will have an alignment_offset of 3584 bytes
    # (sector 7 is the lowest aligned logical block, the 4KB sectors start
    # at LBA -1, and consequently sector 63 is aligned on a 4KB boundary).
    # But note that pvcreate --dataalignmentoffset will skip this detection.
    # 1 enables; 0 disables.
    data_alignment_offset_detection = 1
    # If, while scanning the system for PVs, LVM2 encounters a device-mapper
    # device that has its I/O suspended, it waits for it to become accessible.
    # Set this to 1 to skip such devices. This should only be needed
    # in recovery situations.
    ignore_suspended_devices = 0
    # ignore_lvm_mirrors: Introduced in version 2.02.104
    # This setting determines whether logical volumes of "mirror" segment
    # type are scanned for LVM labels. This affects the ability of
    # mirrors to be used as physical volumes. If 'ignore_lvm_mirrors'
    # is set to '1', it becomes impossible to create volume groups on top
    # of mirror logical volumes - i.e. to stack volume groups on mirrors.
    # Allowing mirror logical volumes to be scanned (setting the value to '0')
    # can potentially cause LVM processes and I/O to the mirror to become
    # blocked. This is due to the way that the "mirror" segment type handles
    # failures. In order for the hang to manifest itself, an LVM command must
    # be run just after a failure and before the automatic LVM repair process
    # takes place OR there must be failures in multiple mirrors in the same
    # volume group at the same time with write failures occurring moments
    # before a scan of the mirror's labels.
    # Note that these scanning limitations do not apply to the LVM RAID
    # types, like "raid1". The RAID segment types handle failures in a
    # different way and are not subject to possible process or I/O blocking.
    # It is encouraged that users set 'ignore_lvm_mirrors' to 1 if they
    # are using the "mirror" segment type. Users that require volume group
    # stacking on mirrored logical volumes should consider using the "raid1"
    # segment type. The "raid1" segment type is not available for
    # active/active clustered volume groups.
    # Set to 1 to disallow stacking and thereby avoid a possible deadlock.
    ignore_lvm_mirrors = 1
    # During each LVM operation errors received from each device are counted.
    # If the counter of a particular device exceeds the limit set here, no
    # further I/O is sent to that device for the remainder of the respective
    # operation. Setting the parameter to 0 disables the counters altogether.
    disable_after_error_count = 0
    # Allow use of pvcreate --uuid without requiring --restorefile.
    require_restorefile_with_uuid = 1
    # Minimum size (in KB) of block devices which can be used as PVs.
    # In a clustered environment all nodes must use the same value.
    # Any value smaller than 512KB is ignored.
    # Ignore devices smaller than 2MB such as floppy drives.
    pv_min_size = 2048
    # The original built-in setting was 512 up to and including version 2.02.84.
    # pv_min_size = 512
    # Issue discards to a logical volumes's underlying physical volume(s) when
    # the logical volume is no longer using the physical volumes' space (e.g.
    # lvremove, lvreduce, etc). Discards inform the storage that a region is
    # no longer in use. Storage that supports discards advertise the protocol
    # specific way discards should be issued by the kernel (TRIM, UNMAP, or
    # WRITE SAME with UNMAP bit set). Not all storage will support or benefit
    # from discards but SSDs and thinly provisioned LUNs generally do. If set
    # to 1, discards will only be issued if both the storage and kernel provide
    # support.
    # 1 enables; 0 disables.
    issue_discards = 0
    # This section allows you to configure the way in which LVM selects
    # free space for its Logical Volumes.
    allocation {
    # When searching for free space to extend an LV, the "cling"
    # allocation policy will choose space on the same PVs as the last
    # segment of the existing LV. If there is insufficient space and a
    # list of tags is defined here, it will check whether any of them are
    # attached to the PVs concerned and then seek to match those PV tags
    # between existing extents and new extents.
    # Use the special tag "@*" as a wildcard to match any PV tag.
    # Example: LVs are mirrored between two sites within a single VG.
    # PVs are tagged with either @site1 or @site2 to indicate where
    # they are situated.
    # cling_tag_list = [ "@site1", "@site2" ]
    # cling_tag_list = [ "@*" ]
    # Changes made in version 2.02.85 extended the reach of the 'cling'
    # policies to detect more situations where data can be grouped
    # onto the same disks. Set this to 0 to revert to the previous
    # algorithm.
    maximise_cling = 1
    # Whether to use blkid library instead of native LVM2 code to detect
    # any existing signatures while creating new Physical Volumes and
    # Logical Volumes. LVM2 needs to be compiled with blkid wiping support
    # for this setting to take effect.
    # LVM2 native detection code is currently able to recognize these signatures:
    # - MD device signature
    # - swap signature
    # - LUKS signature
    # To see the list of signatures recognized by blkid, check the output
    # of 'blkid -k' command. The blkid can recognize more signatures than
    # LVM2 native detection code, but due to this higher number of signatures
    # to be recognized, it can take more time to complete the signature scan.
    use_blkid_wiping = 1
    # Set to 1 to wipe any signatures found on newly-created Logical Volumes
    # automatically in addition to zeroing of the first KB on the LV
    # (controlled by the -Z/--zero y option).
    # The command line option -W/--wipesignatures takes precedence over this
    # setting.
    # The default is to wipe signatures when zeroing.
    wipe_signatures_when_zeroing_new_lvs = 1
    # Set to 1 to guarantee that mirror logs will always be placed on
    # different PVs from the mirror images. This was the default
    # until version 2.02.85.
    mirror_logs_require_separate_pvs = 0
    # Set to 1 to guarantee that cache_pool metadata will always be
    # placed on different PVs from the cache_pool data.
    cache_pool_metadata_require_separate_pvs = 0
    # Specify the minimal chunk size (in kiB) for cache pool volumes.
    # Using a chunk_size that is too large can result in wasteful use of
    # the cache, where small reads and writes can cause large sections of
    # an LV to be mapped into the cache. However, choosing a chunk_size
    # that is too small can result in more overhead trying to manage the
    # numerous chunks that become mapped into the cache. The former is
    # more of a problem than the latter in most cases, so we default to
    # a value that is on the smaller end of the spectrum. Supported values
    # range from 32(kiB) to 1048576 in multiples of 32.
    # cache_pool_chunk_size = 64
    # Set to 1 to guarantee that thin pool metadata will always
    # be placed on different PVs from the pool data.
    thin_pool_metadata_require_separate_pvs = 0
    # Specify chunk size calculation policy for thin pool volumes.
    # Possible options are:
    # "generic" - if thin_pool_chunk_size is defined, use it.
    # Otherwise, calculate the chunk size based on
    # estimation and device hints exposed in sysfs:
    # the minimum_io_size. The chunk size is always
    # at least 64KiB.
    # "performance" - if thin_pool_chunk_size is defined, use it.
    # Otherwise, calculate the chunk size for
    # performance based on device hints exposed in
    # sysfs: the optimal_io_size. The chunk size is
    # always at least 512KiB.
    # thin_pool_chunk_size_policy = "generic"
    # Specify the minimal chunk size (in KB) for thin pool volumes.
    # Use of the larger chunk size may improve performance for plain
    # thin volumes, however using them for snapshot volumes is less efficient,
    # as it consumes more space and takes extra time for copying.
    # When unset, lvm tries to estimate chunk size starting from 64KB
    # Supported values are in range from 64 to 1048576.
    # thin_pool_chunk_size = 64
    # Specify discards behaviour of the thin pool volume.
    # Select one of "ignore", "nopassdown", "passdown"
    # thin_pool_discards = "passdown"
    # Set to 0, to disable zeroing of thin pool data chunks before their
    # first use.
    # N.B. zeroing larger thin pool chunk size degrades performance.
    # thin_pool_zero = 1
    # This section that allows you to configure the nature of the
    # information that LVM2 reports.
    log {
    # Controls the messages sent to stdout or stderr.
    # There are three levels of verbosity, 3 being the most verbose.
    verbose = 0
    # Set to 1 to suppress all non-essential messages from stdout.
    # This has the same effect as -qq.
    # When this is set, the following commands still produce output:
    # dumpconfig, lvdisplay, lvmdiskscan, lvs, pvck, pvdisplay,
    # pvs, version, vgcfgrestore -l, vgdisplay, vgs.
    # Non-essential messages are shifted from log level 4 to log level 5
    # for syslog and lvm2_log_fn purposes.
    # Any 'yes' or 'no' questions not overridden by other arguments
    # are suppressed and default to 'no'.
    silent = 0
    # Should we send log messages through syslog?
    # 1 is yes; 0 is no.
    syslog = 1
    # Should we log error and debug messages to a file?
    # By default there is no log file.
    #file = "/var/log/lvm2.log"
    # Should we overwrite the log file each time the program is run?
    # By default we append.
    overwrite = 0
    # What level of log messages should we send to the log file and/or syslog?
    # There are 6 syslog-like log levels currently in use - 2 to 7 inclusive.
    # 7 is the most verbose (LOG_DEBUG).
    level = 0
    # Format of output messages
    # Whether or not (1 or 0) to indent messages according to their severity
    indent = 1
    # Whether or not (1 or 0) to display the command name on each line output
    command_names = 0
    # A prefix to use before the message text (but after the command name,
    # if selected). Default is two spaces, so you can see/grep the severity
    # of each message.
    prefix = " "
    # To make the messages look similar to the original LVM tools use:
    # indent = 0
    # command_names = 1
    # prefix = " -- "
    # Set this if you want log messages during activation.
    # Don't use this in low memory situations (can deadlock).
    # activation = 0
    # Some debugging messages are assigned to a class and only appear
    # in debug output if the class is listed here.
    # Classes currently available:
    # memory, devices, activation, allocation, lvmetad, metadata, cache,
    # locking
    # Use "all" to see everything.
    debug_classes = [ "memory", "devices", "activation", "allocation",
    "lvmetad", "metadata", "cache", "locking" ]
    # Configuration of metadata backups and archiving. In LVM2 when we
    # talk about a 'backup' we mean making a copy of the metadata for the
    # *current* system. The 'archive' contains old metadata configurations.
    # Backups are stored in a human readable text format.
    backup {
    # Should we maintain a backup of the current metadata configuration ?
    # Use 1 for Yes; 0 for No.
    # Think very hard before turning this off!
    backup = 1
    # Where shall we keep it ?
    # Remember to back up this directory regularly!
    backup_dir = "/etc/lvm/backup"
    # Should we maintain an archive of old metadata configurations.
    # Use 1 for Yes; 0 for No.
    # On by default. Think very hard before turning this off.
    archive = 1
    # Where should archived files go ?
    # Remember to back up this directory regularly!
    archive_dir = "/etc/lvm/archive"
    # What is the minimum number of archive files you wish to keep ?
    retain_min = 10
    # What is the minimum time you wish to keep an archive file for ?
    retain_days = 30
    # Settings for the running LVM2 in shell (readline) mode.
    shell {
    # Number of lines of history to store in ~/.lvm_history
    history_size = 100
    # Miscellaneous global LVM2 settings
    global {
    # The file creation mask for any files and directories created.
    # Interpreted as octal if the first digit is zero.
    umask = 077
    # Allow other users to read the files
    #umask = 022
    # Enabling test mode means that no changes to the on disk metadata
    # will be made. Equivalent to having the -t option on every
    # command. Defaults to off.
    test = 0
    # Default value for --units argument
    units = "h"
    # Since version 2.02.54, the tools distinguish between powers of
    # 1024 bytes (e.g. KiB, MiB, GiB) and powers of 1000 bytes (e.g.
    # KB, MB, GB).
    # If you have scripts that depend on the old behaviour, set this to 0
    # temporarily until you update them.
    si_unit_consistency = 1
    # Whether or not to display unit suffix for sizes. This setting has
    # no effect if the units are in human-readable form (global/units="h")
    # in which case the suffix is always displayed.
    suffix = 1
    # Whether or not to communicate with the kernel device-mapper.
    # Set to 0 if you want to use the tools to manipulate LVM metadata
    # without activating any logical volumes.
    # If the device-mapper kernel driver is not present in your kernel
    # setting this to 0 should suppress the error messages.
    activation = 1
    # If we can't communicate with device-mapper, should we try running
    # the LVM1 tools?
    # This option only applies to 2.4 kernels and is provided to help you
    # switch between device-mapper kernels and LVM1 kernels.
    # The LVM1 tools need to be installed with .lvm1 suffices
    # e.g. vgscan.lvm1 and they will stop working after you start using
    # the new lvm2 on-disk metadata format.
    # The default value is set when the tools are built.
    # fallback_to_lvm1 = 0
    # The default metadata format that commands should use - "lvm1" or "lvm2".
    # The command line override is -M1 or -M2.
    # Defaults to "lvm2".
    # format = "lvm2"
    # Location of proc filesystem
    proc = "/proc"
    # Type of locking to use. Defaults to local file-based locking (1).
    # Turn locking off by setting to 0 (dangerous: risks metadata corruption
    # if LVM2 commands get run concurrently).
    # Type 2 uses the external shared library locking_library.
    # Type 3 uses built-in clustered locking.
    # Type 4 uses read-only locking which forbids any operations that might
    # change metadata.
    # N.B. Don't use lvmetad with locking type 3 as lvmetad is not yet
    # supported in clustered environment. If use_lvmetad=1 and locking_type=3
    # is set at the same time, LVM always issues a warning message about this
    # and then it automatically disables lvmetad use.
    locking_type = 1
    # Set to 0 to fail when a lock request cannot be satisfied immediately.
    wait_for_locks = 1
    # If using external locking (type 2) and initialisation fails,
    # with this set to 1 an attempt will be made to use the built-in
    # clustered locking.
    # If you are using a customised locking_library you should set this to 0.
    fallback_to_clustered_locking = 1
    # If an attempt to initialise type 2 or type 3 locking failed, perhaps
    # because cluster components such as clvmd are not running, with this set
    # to 1 an attempt will be made to use local file-based locking (type 1).
    # If this succeeds, only commands against local volume groups will proceed.
    # Volume Groups marked as clustered will be ignored.
    fallback_to_local_locking = 1
    # Local non-LV directory that holds file-based locks while commands are
    # in progress. A directory like /tmp that may get wiped on reboot is OK.
    locking_dir = "/run/lock/lvm"
    # Whenever there are competing read-only and read-write access requests for
    # a volume group's metadata, instead of always granting the read-only
    # requests immediately, delay them to allow the read-write requests to be
    # serviced. Without this setting, write access may be stalled by a high
    # volume of read-only requests.
    # NB. This option only affects locking_type = 1 viz. local file-based
    # locking.
    prioritise_write_locks = 1
    # Other entries can go here to allow you to load shared libraries
    # e.g. if support for LVM1 metadata was compiled as a shared library use
    # format_libraries = "liblvm2format1.so"
    # Full pathnames can be given.
    # Search this directory first for shared libraries.
    # library_dir = "/lib"
    # The external locking library to load if locking_type is set to 2.
    # locking_library = "liblvm2clusterlock.so"
    # Treat any internal errors as fatal errors, aborting the process that
    # encountered the internal error. Please only enable for debugging.
    abort_on_internal_errors = 0
    # Check whether CRC is matching when parsed VG is used multiple times.
    # This is useful to catch unexpected internal cached volume group
    # structure modification. Please only enable for debugging.
    detect_internal_vg_cache_corruption = 0
    # If set to 1, no operations that change on-disk metadata will be permitted.
    # Additionally, read-only commands that encounter metadata in need of repair
    # will still be allowed to proceed exactly as if the repair had been
    # performed (except for the unchanged vg_seqno).
    # Inappropriate use could mess up your system, so seek advice first!
    metadata_read_only = 0
    # 'mirror_segtype_default' defines which segtype will be used when the
    # shorthand '-m' option is used for mirroring. The possible options are:
    # "mirror" - The original RAID1 implementation provided by LVM2/DM. It is
    # characterized by a flexible log solution (core, disk, mirrored)
    # and by the necessity to block I/O while reconfiguring in the
    # event of a failure.
    # There is an inherent race in the dmeventd failure handling
    # logic with snapshots of devices using this type of RAID1 that
    # in the worst case could cause a deadlock.
    # Ref: https://bugzilla.redhat.com/show_bug.cgi?id=817130#c10
    # "raid1" - This implementation leverages MD's RAID1 personality through
    # device-mapper. It is characterized by a lack of log options.
    # (A log is always allocated for every device and they are placed
    # on the same device as the image - no separate devices are
    # required.) This mirror implementation does not require I/O
    # to be blocked in the kernel in the event of a failure.
    # This mirror implementation is not cluster-aware and cannot be
    # used in a shared (active/active) fashion in a cluster.
    # Specify the '--type <mirror|raid1>' option to override this default
    # setting.
    mirror_segtype_default = "raid1"
    # 'raid10_segtype_default' determines the segment types used by default
    # when the '--stripes/-i' and '--mirrors/-m' arguments are both specified
    # during the creation of a logical volume.
    # Possible settings include:
    # "raid10" - This implementation leverages MD's RAID10 personality through
    # device-mapper.
    # "mirror" - LVM will layer the 'mirror' and 'stripe' segment types. It
    # will do this by creating a mirror on top of striped sub-LVs;
    # effectively creating a RAID 0+1 array. This is suboptimal
    # in terms of providing redundancy and performance. Changing to
    # this setting is not advised.
    # Specify the '--type <raid10|mirror>' option to override this default
    # setting.
    raid10_segtype_default = "raid10"
    # The default format for displaying LV names in lvdisplay was changed
    # in version 2.02.89 to show the LV name and path separately.
    # Previously this was always shown as /dev/vgname/lvname even when that
    # was never a valid path in the /dev filesystem.
    # Set to 1 to reinstate the previous format.
    # lvdisplay_shows_full_device_path = 0
    # Whether to use (trust) a running instance of lvmetad. If this is set to
    # 0, all commands fall back to the usual scanning mechanisms. When set to 1
    # *and* when lvmetad is running (automatically instantiated by making use of
    # systemd's socket-based service activation or run as an initscripts service
    # or run manually), the volume group metadata and PV state flags are obtained
    # from the lvmetad instance and no scanning is done by the individual
    # commands. In a setup with lvmetad, lvmetad udev rules *must* be set up for
    # LVM to work correctly. Without proper udev rules, all changes in block
    # device configuration will be *ignored* until a manual 'pvscan --cache'
    # is performed. These rules are installed by default.
    # If lvmetad has been running while use_lvmetad was 0, it MUST be stopped
    # before changing use_lvmetad to 1 and started again afterwards.
    # If using lvmetad, the volume activation is also switched to automatic
    # event-based mode. In this mode, the volumes are activated based on
    # incoming udev events that automatically inform lvmetad about new PVs
    # that appear in the system. Once the VG is complete (all the PVs are
    # present), it is auto-activated. The activation/auto_activation_volume_list
    # setting controls which volumes are auto-activated (all by default).
    # A note about device filtering while lvmetad is used:
    # When lvmetad is updated (either automatically based on udev events
    # or directly by pvscan --cache <device> call), the devices/filter
    # is ignored and all devices are scanned by default. The lvmetad always
    # keeps unfiltered information which is then provided to LVM commands
    # and then each LVM command does the filtering based on devices/filter
    # setting itself.
    # To prevent scanning devices completely, even when using lvmetad,
    # the devices/global_filter must be used.
    # N.B. Don't use lvmetad with locking type 3 as lvmetad is not yet
    # supported in clustered environment. If use_lvmetad=1 and locking_type=3
    # is set at the same time, LVM always issues a warning message about this
    # and then it automatically disables lvmetad use.
    use_lvmetad = 0
    # Full path of the utility called to check that a thin metadata device
    # is in a state that allows it to be used.
    # Each time a thin pool needs to be activated or after it is deactivated
    # this utility is executed. The activation will only proceed if the utility
    # has an exit status of 0.
    # Set to "" to skip this check. (Not recommended.)
    # The thin tools are available as part of the device-mapper-persistent-data
    # package from https://github.com/jthornber/thin-provisioning-tools.
    # thin_check_executable = "/usr/bin/thin_check"
    # Array of string options passed with thin_check command. By default,
    # option "-q" is for quiet output.
    # With thin_check version 2.1 or newer you can add "--ignore-non-fatal-errors"
    # to let it pass through ignorable errors and fix them later.
    # thin_check_options = [ "-q" ]
    # Full path of the utility called to repair a thin metadata device
    # is in a state that allows it to be used.
    # Each time a thin pool needs repair this utility is executed.
    # See thin_check_executable how to obtain binaries.
    # thin_repair_executable = "/usr/bin/thin_repair"
    # Array of extra string options passed with thin_repair command.
    # thin_repair_options = [ "" ]
    # Full path of the utility called to dump thin metadata content.
    # See thin_check_executable how to obtain binaries.
    # thin_dump_executable = "/usr/bin/thin_dump"
    # If set, given features are not used by thin driver.
    # This can be helpful not just for testing, but i.e. allows to avoid
    # using problematic implementation of some thin feature.
    # Features:
    # block_size
    # discards
    # discards_non_power_2
    # external_origin
    # metadata_resize
    # external_origin_extend
    # thin_disabled_features = [ "discards", "block_size" ]
    activation {
    # Set to 1 to perform internal checks on the operations issued to
    # libdevmapper. Useful for debugging problems with activation.
    # Some of the checks may be expensive, so it's best to use this
    # only when there seems to be a problem.
    checks = 0
    # Set to 0 to disable udev synchronisation (if compiled into the binaries).
    # Processes will not wait for notification from udev.
    # They will continue irrespective of any possible udev processing
    # in the background. You should only use this if udev is not running
    # or has rules that ignore the devices LVM2 creates.
    # The command line argument --nodevsync takes precedence over this setting.
    # If set to 1 when udev is not running, and there are LVM2 processes
    # waiting for udev, run 'dmsetup udevcomplete_all' manually to wake them up.
    udev_sync = 1
    # Set to 0 to disable the udev rules installed by LVM2 (if built with
    # --enable-udev_rules). LVM2 will then manage the /dev nodes and symlinks
    # for active logical volumes directly itself.
    # N.B. Manual intervention may be required if this setting is changed
    # while any logical volumes are active.
    udev_rules = 1
    # Set to 1 for LVM2 to verify operations performed by udev. This turns on
    # additional checks (and if necessary, repairs) on entries in the device
    # directory after udev has completed processing its events.
    # Useful for diagnosing problems with LVM2/udev interactions.
    verify_udev_operations = 0
    # If set to 1 and if deactivation of an LV fails, perhaps because
    # a process run from a quick udev rule temporarily opened the device,
    # retry the operation for a few seconds before failing.
    retry_deactivation = 1
    # How to fill in missing stripes if activating an incomplete volume.
    # Using "error" will make inaccessible parts of the device return
    # I/O errors on access. You can instead use a device path, in which
    # case, that device will be used to in place of missing stripes.
    # But note that using anything other than "error" with mirrored
    # or snapshotted volumes is likely to result in data corruption.
    missing_stripe_filler = "error"
    # The linear target is an optimised version of the striped target
    # that only handles a single stripe. Set this to 0 to disable this
    # optimisation and always use the striped target.
    use_linear_target = 1
    # How much stack (in KB) to reserve for use while devices suspended
    # Prior to version 2.02.89 this used to be set to 256KB
    reserved_stack = 64
    # How much memory (in KB) to reserve for use while devices suspended
    reserved_memory = 8192
    # Nice value used while devices suspended
    process_priority = -18
    # If volume_list is defined, each LV is only activated if there is a
    # match against the list.
    # "vgname" and "vgname/lvname" are matched exactly.
    # "@tag" matches any tag set in the LV or VG.
    # "@*" matches if any tag defined on the host is also set in the LV or VG
    # If any host tags exist but volume_list is not defined, a default
    # single-entry list containing "@*" is assumed.
    # volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
    # If auto_activation_volume_list is defined, each LV that is to be
    # activated with the autoactivation option (--activate ay/-a ay) is
    # first checked against the list. There are two scenarios in which
    # the autoactivation option is used:
    # - automatic activation of volumes based on incoming PVs. If all the
    # PVs making up a VG are present in the system, the autoactivation
    # is triggered. This requires lvmetad (global/use_lvmetad=1) and udev
    # to be running. In this case, "pvscan --cache -aay" is called
    # automatically without any user intervention while processing
    # udev events. Please, make sure you define auto_activation_volume_list
    # properly so only the volumes you want and expect are autoactivated.
    # - direct activation on command line with the autoactivation option.
    # In this case, the user calls "vgchange --activate ay/-a ay" or
    # "lvchange --activate ay/-a ay" directly.
    # By default, the auto_activation_volume_list is not defined and all
    # volumes will be activated either automatically or by using --activate ay/-a ay.
    # N.B. The "activation/volume_list" is still honoured in all cases so even
    # if the VG/LV passes the auto_activation_volume_list, it still needs to
    # pass the volume_list for it to be activated in the end.
    # If auto_activation_volume_list is defined but empty, no volumes will be
    # activated automatically and --activate ay/-a ay will do nothing.
    # auto_activation_volume_list = []
    # If auto_activation_volume_list is defined and it's not empty, only matching
    # volumes will be activated either automatically or by using --activate ay/-a ay.
    # "vgname" and "vgname/lvname" are matched exactly.
    # "@tag" matches any tag set in the LV or VG.
    # "@*" matches if any tag defined on the host is also set in the LV or VG
    # auto_activation_volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
    # If read_only_volume_list is defined, each LV that is to be activated
    # is checked against the list, and if it matches, it as activated
    # in read-only mode. (This overrides '--permission rw' stored in the
    # metadata.)
    # "vgname" and "vgname/lvname" are matched exactly.
    # "@tag" matches any tag set in the LV or VG.
    # "@*" matches if any tag defined on the host is also set in the LV or VG
    # read_only_volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
    # Each LV can have an 'activation skip' flag stored persistently against it.
    # During activation, this flag is used to decide whether such an LV is skipped.
    # The 'activation skip' flag can be set during LV creation and by default it
    # is automatically set for thin snapshot LVs. The 'auto_set_activation_skip'
    # enables or disables this automatic setting of the flag while LVs are created.
    # auto_set_activation_skip = 1
    # For RAID or 'mirror' segment types, 'raid_region_size' is the
    # size (in KiB) of each:
    # - synchronization operation when initializing
    # - each copy operation when performing a 'pvmove' (using 'mirror' segtype)
    # This setting has replaced 'mirror_region_size' since version 2.02.99
    raid_region_size = 512
    # Setting to use when there is no readahead value stored in the metadata.
    # "none" - Disable readahead.
    # "auto" - Use default value chosen by kernel.
    readahead = "auto"
    # 'raid_fault_policy' defines how a device failure in a RAID logical
    # volume is handled. This includes logical volumes that have the following
    # segment types: raid1, raid4, raid5*, and raid6*.
    # In the event of a failure, the following policies will determine what
    # actions are performed during the automated response to failures (when
    # dmeventd is monitoring the RAID logical volume) and when 'lvconvert' is
    # called manually with the options '--repair' and '--use-policies'.
    # "warn" - Use the system log to warn the user that a device in the RAID
    # logical volume has failed. It is left to the user to run
    # 'lvconvert --repair' manually to remove or replace the failed
    # device. As long as the number of failed devices does not
    # exceed the redundancy of the logical volume (1 device for
    # raid4/5, 2 for raid6, etc) the logical volume will remain
    # usable.
    # "allocate" - Attempt to use any extra physical volumes in the volume
    # group as spares and replace faulty devices.
    raid_fault_policy = "warn"
    # 'mirror_image_fault_policy' and 'mirror_log_fault_policy' define
    # how a device failure affecting a mirror (of "mirror" segment type) is
    # handled. A mirror is composed of mirror images (copies) and a log.
    # A disk log ensures that a mirror does not need to be re-synced
    # (all copies made the same) every time a machine reboots or crashes.
    # In the event of a failure, the specified policy will be used to determine
    # what happens. This applies to automatic repairs (when the mirror is being
    # monitored by dmeventd) and to manual lvconvert --repair when
    # --use-policies is given.
    # "remove" - Simply remove the faulty device and run without it. If
    # the log device fails, the mirror would convert to using
    # an in-memory log. This means the mirror will not
    # remember its sync status across crashes/reboots and
    # the entire mirror will be re-synced. If a
    # mirror image fails, the mirror will convert to a
    # non-mirrored device if there is only one remaining good
    # copy.
    # "allocate" - Remove the faulty device and try to allocate space on
    # a new device to be a replacement for the failed device.
    # Using this policy for the log is fast and maintains the
    # ability to remember sync state through crashes/reboots.
    # Using this policy for a mirror device is slow, as it
    # requires the mirror to resynchronize the devices, but it
    # will preserve the mirror characteristic of the device.
    # This policy acts like "remove" if no suitable device and
    # space can be allocated for the replacement.
    # "allocate_anywhere" - Not yet implemented. Useful to place the log device
    # temporarily on same physical volume as one of the mirror
    # images. This policy is not recommended for mirror devices
    # since it would break the redundant nature of the mirror. This
    # policy acts like "remove" if no suitable device and space can
    # be allocated for the replacement.
    mirror_log_fault_policy = "allocate"
    mirror_image_fault_policy = "remove"
    # 'snapshot_autoextend_threshold' and 'snapshot_autoextend_percent' define
    # how to handle automatic snapshot extension. The former defines when the
    # snapshot should be extended: when its space usage exceeds this many
    # percent. The latter defines how much extra space should be allocated for
    # the snapshot, in percent of its current size.
    # For example, if you set snapshot_autoextend_threshold to 70 and
    # snapshot_autoextend_percent to 20, whenever a snapshot exceeds 70% usage,
    # it will be extended by another 20%. For a 1G snapshot, using up 700M will
    # trigger a resize to 1.2G. When the usage exceeds 840M, the snapshot will
    # be extended to 1.44G, and so on.
    # Setting snapshot_autoextend_threshold to 100 disables automatic
    # extensions. The minimum value is 50 (A setting below 50 will be treated
    # as 50).
    snapshot_autoextend_threshold = 100
    snapshot_autoextend_percent = 20
    # 'thin_pool_autoextend_threshold' and 'thin_pool_autoextend_percent' define
    # how to handle automatic pool extension. The former defines when the
    # pool should be extended: when its space usage exceeds this many
    # percent. The latter defines how much extra space should be allocated for
    # the pool, in percent of its current size.
    # For example, if you set thin_pool_autoextend_threshold to 70 and
    # thin_pool_autoextend_percent to 20, whenever a pool exceeds 70% usage,
    # it will be extended by another 20%. For a 1G pool, using up 700M will
    # trigger a resize to 1.2G. When the usage exceeds 840M, the pool will
    # be extended to 1.44G, and so on.
    # Setting thin_pool_autoextend_threshold to 100 disables automatic
    # extensions. The minimum value is 50 (A setting below 50 will be treated
    # as 50).
    thin_pool_autoextend_threshold = 100
    thin_pool_autoextend_percent = 20
    # While activating devices, I/O to devices being (re)configured is
    # suspended, and as a precaution against deadlocks, LVM2 needs to pin
    # any memory it is using so it is not paged out. Groups of pages that
    # are known not to be accessed during activation need not be pinned
    # into memory. Each string listed in this setting is compared against
    # each line in /proc/self/maps, and the pages corresponding to any
    # lines that match are not pinned. On some systems locale-archive was
    # found to make up over 80% of the memory used by the process.
    # mlock_filter = [ "locale/locale-archive", "gconv/gconv-modules.cache" ]
    # Set to 1 to revert to the default behaviour prior to version 2.02.62
    # which used mlockall() to pin the whole process's memory while activating
    # devices.
    use_mlockall = 0
    # Monitoring is enabled by default when activating logical volumes.
    # Set to 0 to disable monitoring or use the --ignoremonitoring option.
    monitoring = 1
    # When pvmove or lvconvert must wait for the kernel to finish
    # synchronising or merging data, they check and report progress
    # at intervals of this number of seconds. The default is 15 seconds.
    # If this is set to 0 and there is only one thing to wait for, there
    # are no progress reports, but the process is awoken immediately the
    # operation is complete.
    polling_interval = 15
    # Report settings.
    # report {
    # Align columns on report output.
    # aligned=1
    # When buffered reporting is used, the report's content is appended
    # incrementally to include each object being reported until the report
    # is flushed to output which normally happens at the end of command
    # execution. Otherwise, if buffering is not used, each object is
    # reported as soon as its processing is finished.
    # buffered=1
    # Show headings for columns on report.
    # headings=1
    # A separator to use on report after each field.
    # separator=" "
    # Use a field name prefix for each field reported.
    # prefixes=0
    # Quote field values when using field name prefixes.
    # quoted=1
    # Output each column as a row. If set, this also implies report/prefixes=1.
    # colums_as_rows=0
    # Comma separated list of columns to sort by when reporting 'lvm devtypes' command.
    # See 'lvm devtypes -o help' for the list of possible fields.
    # devtypes_sort="devtype_name"
    # Comma separated list of columns to report for 'lvm devtypes' command.
    # See 'lvm devtypes -o help' for the list of possible fields.
    # devtypes_cols="devtype_name,devtype_max_partitions,devtype_description"
    # Comma separated list of columns to report for 'lvm devtypes' command in verbose mode.
    # See 'lvm devtypes -o help' for the list of possible fields.
    # devtypes_cols_verbose="devtype_name,devtype_max_partitions,devtype_description"
    # Comma separated list of columns to sort by when reporting 'lvs' command.
    # See 'lvs -o help' for the list of possible fields.
    # lvs_sort="vg_name,lv_name"
    # Comma separated list of columns to report for 'lvs' command.
    # See 'lvs -o help' for the list of possible fields.
    # lvs_cols="lv_name,vg_name,lv_attr,lv_size,pool_lv,origin,data_percent,move_pv,mirror_log,copy_percent,convert_lv"
    # Comma separated list of columns to report for 'lvs' command in verbose mode.
    # See 'lvs -o help' for the list of possible fields.
    # lvs_cols_verbose="lv_name,vg_name,seg_count,lv_attr,lv_size,lv_major,lv_minor,lv_kernel_major,lv_kernel_minor,pool_lv,origin,data_percent,metadata_percent,move_pv,copy_percent,mirror_log,convert
    # Comma separated list of columns to sort by when reporting 'vgs' command.
    # See 'vgs -o help' for the list of possible fields.
    # vgs_sort="vg_name"
    # Comma separated list of columns to report for 'vgs' command.
    # See 'vgs -o help' for the list of possible fields.
    # vgs_cols="vg_name,pv_count,lv_count,snap_count,vg_attr,vg_size,vg_free"
    # Comma separated list of columns to report for 'vgs' command in verbose mode.
    # See 'vgs -o help' for the list of possible fields.
    # vgs_cols_verbose="vg_name,vg_attr,vg_extent_size,pv_count,lv_count,snap_count,vg_size,vg_free,vg_uuid,vg_profile"
    # Comma separated list of columns to sort by when reporting 'pvs' command.
    # See 'pvs -o help' for the list of possible fields.
    # pvs_sort="pv_name"
    # Comma separated list of columns to report for 'pvs' command.
    # See 'pvs -o help' for the list of possible fields.
    # pvs_cols="pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free"
    # Comma separated list of columns to report for 'pvs' command in verbose mode.
    # See 'pvs -o help' for the list of possible fields.
    # pvs_cols_verbose="pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,dev_size,pv_uuid"
    # Comma separated list of columns to sort by when reporting 'lvs --segments' command.
    # See 'lvs --segments -o help' for the list of possible fields.
    # segs_sort="vg_name,lv_name,seg_start"
    # Comma separated list of columns to report for 'lvs --segments' command.
    # See 'lvs --segments -o help' for the list of possible fields.
    # segs_cols="lv_name,vg_name,lv_attr,stripes,segtype,seg_size"
    # Comma separated list of columns to report for 'lvs --segments' command in verbose mode.
    # See 'lvs --segments -o help' for the list of possible fields.
    # segs_cols_verbose="lv_name,vg_name,lv_attr,seg_start,seg_size,stripes,segtype,stripesize,chunksize"
    # Comma separated list of columns to sort by when reporting 'pvs --segments' command.
    # See 'pvs --segments -o help' for the list of possible fields.
    # pvsegs_sort="pv_name,pvseg_start"
    # Comma separated list of columns to sort by when reporting 'pvs --segments' command.
    # See 'pvs --segments -o help' for the list of possible fields.
    # pvsegs_cols="pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,pvseg_start,pvseg_size"
    # Comma separated list of columns to sort by when reporting 'pvs --segments' command in verbose mode.
    # See 'pvs --segments -o help' for the list of possible fields.
    # pvsegs_cols_verbose="pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,pvseg_start,pvseg_size,lv_name,seg_start_pe,segtype,seg_pe_ranges"
    # Advanced section #
    # Metadata settings
    # metadata {
    # Default number of copies of metadata to hold on each PV. 0, 1 or 2.
    # You might want to override it from the command line with 0
    # when running pvcreate on new PVs which are to be added to large VGs.
    # pvmetadatacopies = 1
    # Default number of copies of metadata to maintain for each VG.
    # If set to a non-zero value, LVM automatically chooses which of
    # the available metadata areas to use to achieve the requested
    # number of copies of the VG metadata. If you set a value larger
    # than the the total number of metadata areas available then
    # metadata is stored in them all.
    # The default value of 0 ("unmanaged") disables this automatic
    # management and allows you to control which metadata areas
    # are used at the individual PV level using 'pvchange
    # --metadataignore y/n'.
    # vgmetadatacopies = 0
    # Approximate default size of on-disk metadata areas in sectors.
    # You should increase this if you have large volume groups or
    # you want to retain a large on-disk history of your metadata changes.
    # pvmetadatasize = 255
    # List of directories holding live copies of text format metadata.
    # These directories must not be on logical volumes!
    # It's possible to use LVM2 with a couple of directories here,
    # preferably on different (non-LV) filesystems, and with no other
    # on-disk metadata (pvmetadatacopies = 0). Or this can be in
    # addition to on-disk metadata areas.
    # The feature was originally added to simplify testing and is not
    # supported under low memory situations - the machine could lock up.
    # Never edit any files in these directories by hand unless you
    # you are absolutely sure you know what you are doing! Use
    # the supplied toolset to make changes (e.g. vgcfgrestore).
    # dirs = [ "/etc/lvm/metadata", "/mnt/disk2/lvm/metadata2" ]
    # Event daemon
    dmeventd {
    # mirror_library is the library used when monitoring a mirror device.
    # "libdevmapper-event-lvm2mirror.so" attempts to recover from
    # failures. It removes failed devices from a volume group and
    # reconfigures a mirror as necessary. If no mirror library is
    # provided, mirrors are not monitored through dmeventd.
    mirror_library = "libdevmapper-event-lvm2mirror.so"
    # snapshot_library is the library used when monitoring a snapshot device.
    # "libdevmapper-event-lvm2snapshot.so" monitors the filling of
    # snapshots and emits a warning through syslog when the use of
    # the snapshot exceeds 80%. The warning is repeated when 85%, 90% and
    # 95% of the snapshot is filled.
    snapshot_library = "libdevmapper-event-lvm2snapshot.so"
    # thin_library is the library used when monitoring a thin device.
    # "libdevmapper-event-lvm2thin.so" monitors the filling of
    # pool and emits a warning through syslog when the use of
    # the pool exceeds 80%. The warning is repeated when 85%, 90% and
    # 95% of the pool is filled.
    thin_library = "libdevmapper-event-lvm2thin.so"
    # Full path of the dmeventd binary.
    # executable = "/usr/sbin/dmeventd"

  • Being ignored

    My name is David and I've been a Verizon Wireless customer for the past few years. A couple of months ago, I began having issues with a brand new jetpack device. The device was using absurd amounts of data and I had no clue why. I contacted customer service and eventually got in touch with (removed) Smith, a supervisor. We talked about three times over the phone, on separate occasions, trying to figure out what was causing the problem. We reset the device, changed the password, etc., but nothing was fixing the problem. In the meantime, I had taken multiple steps to make sure nothing was using the data on my end. I set up a metered connection, which tracked exactly how much data went through my computer and it was not even close to what the jetpack was saying, despite being the only device connected to it. Ms Smith gave me her email address to stay in closer contact with her while we were trying all of the steps to fix the issue, so I could let her know exactly what I was seeing. The email address she gave me was (removed) Our contact first started in November and she sent me the first email on 12/1/13. The device began using even more data, now at a very alarming rate. In one night, it used 12.5 GBs of data. I spoke with her again on 12/14/13 when I first noticed how much data it had been using. She eventually sent me a new device, stating that the one I had was faulty and she wanted me to let her know when I got the new one so she could monitor the activity and see if it was following the same pattern or if it was acting normal. It ended up working 100% fine and not like the faulty device I had sent back in. She had told me over the phone that she would fix all of the overage charges from when I first got the device since it was messed up. She gave me credit for the total of overage from the first 3 months with the device, but she hadn't fixed the bill that had used 55 GBs of data, which was the last cycle in which I had that particular device.
    The last time I heard from Ms. Smith was on 12/31/13 when she had told me she was going to fix the charges. In the meantime, I was left waiting to hear that the fourth and final month had been taken care of, so the $460 worth of overages was still sitting on my bill. On 12/31/13, she emailed me asking for my number to reach me on so she could call me that day. I responded with my number, but never received a call. A week later on 1/6/14, I emailed her again with my number, telling her that I wasn't sure if she had received my email or not, but I was still waiting. As of 1/21/14, I had still not received a call, so I emailed her again telling her I needed to talk to her ASAP so we could get everything resolved and I could pay my bill. I also mentioned that I needed to have my data plan changed back to normal (16 GBs) rather than the 30 GB plan because it was too much. I had been bumped up to 30 GBs during that big month of overages, to try and prevent extra charges. A little less than a week later on 1/26/14, I emailed Ms. Smith once again, telling her I was worried about my service getting cut off and I needed to speak with her ASAP. I mentioned that I did not want to have to start from scratch with someone else.
    On 2/6/14, I woke up to discover that my service had indeed been turned off. I called and spoke with someone in customer service, explaining what had been going on. I was told by that representative that her supervisor would call me between 8-10 PM that night, but in the meantime my service would be temporarily restored. I never received a call. Around 10:30, I called back to try and speak with someone else. I was put through to another representative, once again having to explain what had been going on. This representative told me that I would have to wait for a call back from his supervisor, because he would be leaving at 11:00 PM. I explained to the representative that I was already promised a call back that night and didn't receive a call, so I had to have it taken care of because my service was shut off. His supervisor took my call and told me that there wasn't much they could do, because Ms. Smith had already started my case. He said they would send her an email, telling her she needs to contact me. He told me that he would have someone from his team call me back within 24-48 hours to see if she got in touch with me and if not, I would start from scratch with them.
    In the meantime, I sent Ms. Smith an email the next day on 2/7/14, telling her my service had been shut off and I tried calling the night before to speak with someone else, but they couldn't do much for me because she had already been working with me. Again, I never did get a response.
    Monday 2/10/14 had come along and once again my service was turned back off. I never did receive a call from the supervisor I spoke with on 2/6/14, who had promised me his team would call me back no later than 48 hours. So, again, I called to try and speak with someone else. I eventually got through to another supervisor, but after I explained to him what had been going on, the call was disconnected. I waited for about 30 minutes to see if he'd call back, but he didn't. Once again, I called to try and speak with someone else. I was directed towards the financial department and I explained to them that I was just talking with someone and was disconnected, so I was hoping to get back to them. I was told that there was no way to trace me back to the man I was speaking with. I then explained to that representative what was going on and she told me that if I paid the actual monthly access portion of my outstanding bill, my service would be restored and she would promise to put a note on my account to not turn it off again, because I was working to have the charges fixed. I paid the monthly access and she then transferred me to technical support to have someone in that department help me further. I then explained my story to the technical representative and she told me that her supervisor was not on-duty at the time, but she was preparing an email to send to her and she would definitely get back to me by the end of the week. That was two weeks ago from today and I've yet to receive a call from anyone.
    Once again, I woke up today to find that my service had again been shut off. I called in and spoke with financial services and explained to them what has been going on and she said if I went ahead and paid my bill that had just come due for last month, she could turn it on. So, that's what I did, but I'm still left in the dark as for the future.
    I am so beyond frustrated with this entire situation, that I have no clue what to do. I've told this story to at least ten people and I've gotten no where. To say that I feel like I'm being ignored, is an understatement. I can send y'all the entire transcript of emails with myself and Ms. Smith, proving that I've been trying to contact her for the past month and a half. This whole situation has gone further than the simple problem of the overage charges. It has now risen to a ridiculous level that I am being ignored by what seems like the entire company as a whole. How many times do I have to call to where I can finally work with one person who will help fix the problem? How many times can one customer be told that he will be contacted and he never receives a call? At this point, I am more than prepared to go over to Sprint and cancel my service with Verizon. The $460 that I am being raked trough the coals for will be nothing compared to not having my business for years to come. I am also prepared to contact and file complaints with the FCC or BBB for the fact that I have done absolutely everything in my power, including going in to a local store, to speak with someone about my issues. Like I said, I have the emails proving that I've been ignored and I can show them to y'all or to them. I don't know what to do anymore and I'm tired of calling and starting over with a new representative then being transferred around in loops where I have to re-tell the entire story again, so this is my last resort. If I don't get help by the end of the day, I'll be somewhere else tomorrow.
    Private info removed as required by the Terms of Service.
    Message was edited by: Admin Moderator

    Hi Barry,
    I am sorry about the mix up with the order, could you send me a PM of your contact details? Please include the email address you used to contact support.

  • Keyboard keys not working?

    I am wondering if anybody has ANY ideas for me. It started off the trackball not tracking to the right. I cleaned the TB, and fixed that problem. Then all of the keys went random. The call button went to "y" and "i" all of the time. I did a hard reset (after many soft resets), and that fixed most of the keys. Then randomly the "3/R" key quit working, and the "L" key also quit working.
    Any ideas? I am exactly thirty days out of warrenty....
    God bless,
    John

    Hi,
    How did you "clean" the trackball?
    I guess you've got water damage so follow sdgardne's steps for de-hydrating the device -  stick the devcie only (no battery,etc) in a bag of rice for three days (DO NOT REMOVE OR "TEST"!)
    If this doesnt work then do an OS reload.
    If it still doesnt work then youve got a faulty device and you'll have to go through a repair/replacement.
    Checked out my Blackberry FAQ's and Links to Needed Articles here
    http://darkeen.homelinux.com/index.php/Blackberryfaq

  • If I buy a Mac and iPad online, will I still be able to claim warranty at an Apple Authorized Service Provider?

    If I buy a Mac and iPad online, will I still be able to claim warranty at an Apple Authorized Service Provider?
    I am going to buy a Macbook Pro w/ Retina Display and iPad from www.topbuy.com.au . It's a legit website, but they say the items have topbuy warranties, not apple ones. They say I have to send off my faulty device to them, and they will fix it, but I don't want to do that. I just want to walk into an Apple store, tell them the problem and have a happy ending, like what's supposed to happen. Will I be able to do this?
    Thanks

    Apple warranty is good at any Apple service provider, AASP or store.
    But you seem to be reaching far to defend that "it's a legit website", especially when they seem to be directing you from seeking certified Apple service.
    As the saying goes: If it looks like a duck, and it sound like a duck, it's quackers to bypass an Apple store or Apple online to save a few $$.  Well, something like that.

  • In my first iPhone 5, the speaker didn't work and people could not hear me on Speaker phone when I used it. When I used the video recording it did not record sound at all only a hissing/static sound, no voice.

    In my first iPhone 5, the speaker didn't work and people could not hear me on Speaker phone when I used it. When I used the video recording it did not record sound at all only a hissing/static sound, no voice. I wished for a software fix. I did a hard reset, nothing. I did a full restore to factory settings not putting my backup on and the problem persisted.
    i have been provided with this info
    You can find troubleshooting tips, how-to articles, and moderated
    > > discussion forums on our support website:
    > >
    > > www.apple.com/support
    > >
    > > iPhone: Basic troubleshooting
    > > http://support.apple.com/kb/HT1737
    > >
    I did every step in the link that i have been provided with (thank you), but I’m
    still experiencing the same issue. My experience with Apple has been
    excellent and this has been the first time I have experienced something
    like this with an Apple product. I hope we can find a quick solution.
    In order to get the iPhone 5 as soon as it launched (being a major fan of
    Apple products!), I purchased my iPhone 5 from the UK through a friend of
    mine who lives there.
    My question is: can I have the faulty device replaced within Saudi by one
    of the official resellers here (we have 3: STC, Mobily and Zain)? I want to
    avoid the disruption, complication and expense of sending it back to the
    UK.
    Could you advise whether this is possible or not, and if not how should I
    go about having the device replaced?
    Thank you in advance for your cooperation.

    Nice try! Take a hike.

  • IPod Touch 4G and iTunes 10.2.2 sync issues on mac?

    Hey,
    I recently purchased an iPod Touch 4G 32GB as a replacement for my iPod Touch 2G 8GB, I plugged it into iTunes on the first boot up of the iPod, like normal, and expected to be presented with the usual set of prompts about how I would like to set up my iPod. However, the iPod appeared in the sidebar, but nothing happened to the main portion of the program, and upon unplugging the iPod, iTunes simply crashed, and I was presented with an error message. I put the iPod into DFU mode, and tried a manual restore, then had to restore from a separate firmware file I downloaded for 4.3.2.
    I assume from the failure of all of these methods, there must be some sort of problem with iTunes 10.2.2 for Mac and iOS 4.3.2 for iPod Touch 4G. In the end, i managed to get the iPod operational on my PC in an older version of iTunes, however, it still does not sync properly, and if I try to sync movies to the iPod, iTunes crashs like it did before. Is there a known fix for this problem? Or have I got a faulty device? Also, the sync messages are all distorted.
    Thanks!

    Marissaur, try:
    Mac OS X v10.6 or later: iOS device not recognized in iTunes after restart

  • Clicking on firefox icon causes blue screen crash

    This began Friday, Feb. 25, about mid day. The only changes to the system that morning were an update to an Adobe plugin, either Flash player or Shockwave, I'm not sure, and an update to the Scottrade Elite desktop trading app. Both of those changes occurred about 0900. The problems began about 1130 when the system, Windows 7 Home Premium had a blue screen crash. From that time on, I have uninstalled each of the apps mentioned. I cannot open Firefox to work on the plugins becuase every time I click on the icon I get a blue screen crash with the words "Page fault in non paged area" at the top. I've also uninstalled and reinstalled the Firefox app with no apparent beneficial effect. The Scottrade trading app has been reinstalled and works well, causing no further probs.

    Hello mrcart,
    i think it is unlikely that firefox itself is causing an operating system crash, i had some time back an similar issue where a system of a friend of mine was crashing while using IE - thats the only app he used ... the system in his case had faulty ram, and i suspect you are facing some sort of hardware problem or faulty device driver.
    Please read this (also lists steps what you can do):
    http://technet.microsoft.com/en-us/library/cc957625.aspx
    (personally) I would suggest you start by checking your ram, you can do this in two ways:
    Search in your Windows 7 Start Menu for "ram", you should find something like "Diagnose your computer´s memory problems"
    ... Or, you use the memtest86+ tool from here (e.g. download the iso, burn it and boot from the cd):
    http://www.memtest.org/
    Check your eventlog for errors (e.g. disk errors, timeouts, etc).
    If you cannot track the problem down (i would suspect a hardware problem or faulty device driver ... e.g. it could be your video card driver doing something wrong) you should seek help at your computer manufacturer, an experienced friend, or using some forum.
    kind regards,
    John Kirk.

  • (Win8.1 Pro) Blue Screen of Death: IRQL_NOT_LESS_OR_EQUAL

    I'm getting intermittent BSODs, usually with the message "IRQL_NOT_LESS_OR_EQUAL". It doesn't appear to be tied to a specific activity - sometimes it will happen when I'm not at the computer. I tried doing a Memory Diagnostic test and it found
    no errors. As per one of the suggestions on the forum here, I tried running the Driver Verifier process, but then it couldn't boot into Windows at all (had to go in in safe mode and reset the verifier). A couple of weeks ago, I had a few BSODs with the message
    "DPC_WATCHDOG_VIOLATION" though that appears not to have happened for a while.
    Any help would be appreciated - I'm sort of out of my depth here. DMP and Sysinfo Link below..
    https://www.dropbox.com/sh/cajd7ozeb7zxzez/Gs76gj28z2
    System: Windows 8.1 Pro
    Computer: DELL INSPIRON N5010 / Processor: Intel Core i5 / Memory: 8GB / System Type: 64-bit
    Cheers, 
    C

    Hi,
    We have a ton of crash dumps here, and I went through what I can.
    MEMORY_MANAGEMENT (1a)
    This indicates that a severe memory management error occurred.
    BugCheck 1A, {41287, 61d00125f640, 0, 0}
    The 1st parameter of the bug check is 41287 which indicates an illegal page fault occurred while holding working set synchronization.
    DPC_WATCHDOG_VIOLATION (133)
    This bug check indicates that the DPC watchdog executed, either because it detected a single long-running deferred procedure call (DPC), or because the system spent a prolonged time at an interrupt request level (IRQL) of DISPATCH_LEVEL or above.
    I need a kernel-dump to debug this type of bug check.
    IRQL_NOT_LESS_OR_EQUAL (a)
    This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high. The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
    2: kd> k
    Child-SP RetAddr Call Site
    ffffd000`22e8d338 fffff801`dbbd57e9 nt!KeBugCheckEx
    ffffd000`22e8d340 fffff801`dbbd403a nt!KiBugCheckDispatch+0x69
    ffffd000`22e8d480 fffff801`dbb62e71 nt!KiPageFault+0x23a
    ffffd000`22e8d610 fffff801`dbab0452 nt!MiReplenishPageSlist+0x139
    ffffd000`22e8d680 fffff801`dbaad342 nt!MiRemoveAnyPage+0x202
    ffffd000`22e8d740 fffff801`dbaa9f07 nt!MiGetPage+0x3f2
    ffffd000`22e8d810 fffff801`dbaaf762 nt!MiResolveMappedFileFault+0x3b7
    ffffd000`22e8d930 fffff801`dbaae4fb nt!MiResolveProtoPteFault+0x642
    ffffd000`22e8d9d0 fffff801`dbab8124 nt!MiDispatchFault+0x9ab
    ffffd000`22e8db00 fffff801`dbbd3f2f nt!MmAccessFault+0x364
    ffffd000`22e8dc40 00007ffc`cae945cd nt!KiPageFault+0x12f
    0000009e`cc89be60 00000000`00000000 0x00007ffc`cae945cd
    nt!MiReplenishPageSlist calls a pagefault, and prior to this we have various memory related routines as well.
    This looks like faulty RAM to me, so please go ahead and start by running Memtest for NO LESS than ~8 passes (several hours):
    Memtest86+:
    Download Memtest86+ here:
    http://www.memtest.org/
    Which should I download?
    You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary
    files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).
    Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).
    How Memtest works:
    Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.
    The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because
    of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.
    Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance
    is error-free with these faster settings.
    Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.
    This information, if available to the program, can be displayed via a menu option.
    Any other questions, they can most likely be answered by reading this great guide here:
    http://forum.canardpc.com/threads/28864-FAQ-please-read-before-posting
    Regards,
    Patrick
    “Be kind whenever possible. It is always possible.” - Dalai Lama

Maybe you are looking for

  • Outline View missing in Pages 5.0

    Pages looses half of its functionality if you cannot use outling when you write. I see how to make headings and bulleted lists but no way to collapse and expand them. Does anyone know if this is still possible?  There used to be a menu item called Ou

  • CTRL+SHIFT+O does not work

    WHen i attempt to save a record in an infopath form, I receive an error that the form cannot be submitted and to press CTRL+SHIFT+O to identify errors.  This does nothing!  Is  there any other means to identify the errors on the form or to show the u

  • Servlets only running, not compileing

    Recently installed Tomcat on an old Win ME machine. The pre compiled servlet are running fine. However I am not able to compile any new ones. Anyone know what might be wrong? Thanks Andreas

  • Embedded font doesn't display the same at runtime

    Hi, For whatever reason, I have chosen Aerial Black for some read-only TLF text (anti-alias = "readability"), but at runtime, it looks more like Times Roman. Any idea? Regards, Ron

  • How many photos

    Hi Does anyone know approximately how many photos I can import into iDVD and then burn on to a DVD? And what resolution I should used. Thanks