Dma timeout
Hello Vitaly Filatov,
It looks like you did not get my response to your questions because I had some trouble loggin in to the sun forum. So I am posting it again.
thanks
Aspiration
thank you for your response. Here is the info you wanted.
On Ultra 60 (where my driver works fine)
uname -srvmpi produces the following output:
SunOS 5.9 Generic_117171-07 Sun4u sparc sunw, ultra-60
and .version proudces the following output:
Release 3.31 Version 0 created 2001/7/25 20:31
OBP: 3.31.0 2001/7/25 20:31
POST: 2.0.3 2000/7/31 15:28
On Sunblade 2500 where my driver crashes, uname produces
sunos 5.9 Generic_117171-07 sun4u sparc sunw, sun-blade-2500
and .version produces
Release 4.13.5 created 2004/5/27 17:31
OBP: 4.13.5 2004/5/27 17:31 sunblade 2500, sunfire v250
OBDIAG: 4.13.5 2004/5/27 17:33
POST: 4.13.0 2004/1/16 12:39
Please note that due to the very high speed acquisition rate of the ADC board, DMA is used to transfer data from ADC onboard memory to user space.
thanks
Aspiration
I'm having the same problem. My scanner is a HP ScanJet 8250. I'm using Adobe Pro Extended & Windows Fax & Scan programs. Currently running Windows 7 (64 bit) Professional on an Intel i7-2600 CPU with 4x2.00GB of DDR3-1333 RAM
When using the feeder tray, it will either feed 3/4 of a page before timing out or it will not scan anything at all. When using the flatbed, the scanning bulb will move down the glass but then stop at the end and timeout.
I did have this scanner fuctioning properly on another computer using Windows 7 (64 bit) Ultimate but the hardware specs elude me at this point in time. I saw there was a firmware update for previous generations of Windows but nothing for Windows 7.
So far I have tried uninstalling & reinstalling the driver. Switching through every USB port on the tower. And I've swapped out the USB cable.
Any help would be greatly appreciated.
Similar Messages
-
Changing to XP-64Bit, I installed the software for my HP Scanjet 8270, and haven't been able to scan ever since. I continuously get a DMA Timeout error. If I let it sit for a while, eventually I get an HP-CUE Scanning Flow Component error, and then an automatic application/shutdown error window with the AppName: hpqkygrp.exe, AppVer: 9.0.0.257 details. After 2 solid weeks of back and for with the pathetic HP non-Support, I haven't gotten anywhere. I have uninstalled/re-installed, downloaded their latest FULL version, this thing just doesn't work. It doesn't work with the XP scan wizard either. It gets about a 1/3 of the page and then just hangs in the scanner with a DMA Timeout error. Please help !!!
I'm having the same problem. My scanner is a HP ScanJet 8250. I'm using Adobe Pro Extended & Windows Fax & Scan programs. Currently running Windows 7 (64 bit) Professional on an Intel i7-2600 CPU with 4x2.00GB of DDR3-1333 RAM
When using the feeder tray, it will either feed 3/4 of a page before timing out or it will not scan anything at all. When using the flatbed, the scanning bulb will move down the glass but then stop at the end and timeout.
I did have this scanner fuctioning properly on another computer using Windows 7 (64 bit) Ultimate but the hardware specs elude me at this point in time. I saw there was a firmware update for previous generations of Windows but nothing for Windows 7.
So far I have tried uninstalling & reinstalling the driver. Switching through every USB port on the tower. And I've swapped out the USB cable.
Any help would be greatly appreciated. -
1473R DMA timeout at high speed?
I'm using a 1473R with a Basler line camera spl2048-140km. I managed to modify the example to run the camera on both 8 tap 8 bit mode and 4 tap 12bit mode. Both run well at low speed. However, there are two issues when I try to run it at high speed.
If I set the frame trigger at relatively high speed before I start the acquiring (like 30kHz), a DMA timeout error will jump out as soon as I start it (error -8999). If I set it at low speed (like 100Hz), it will run fine as I increase it to 30kHz after it starts.
Another issue is, when I try to push the speed of the camera to its limit, which is 70kHz for single channel mode and 140kHz for dual channel mode, I will always have the error -8999. It happens when the speed reaches 100kHz in 8 tap 8 bit mode, and 50kHz at 4 tap 12 bit mode. I wonder where the bottle neck is and if there will be a way to solve it.
Thanks!I'm not that familiar with the FPGA code for the 1473R, but I am fairly sure that the DRAM example has been tested with fairy fast cameras. That said, it seems from looking at it that it does not have a good feedback mechanism if PCIe bandwidth is not available. It's only feedback seems to be if the host DMA buffer fills up (e.g. host code doesn't read it fast enough). Since PCIe/memory bandwidth is extremely host-dependent, it is quite possible this example is not well tested with the combination of very fast cameras and some systems that have more jittery PCIe bandwidth. I'm not sure of the specifics of the DMA FIFO behavior, but my assumption is that the number of elements remaining really only concerns itself with host space available. For most situations, the minimal amount of FIFO built into the DMA engine likely makes this work fine.
First, I'd try instrumenting the code to figure out which specific part in the FPGA code is timing out. The example doesnt seem to track all the error cases well.
Assuming it is the host DMA that times out AND it always reports that there is free space available, my suggestion would be to modify the code to let the DMA step retry with the same data the next clock cycle on a Timeout and let the data back-up in DRAM as needed.
Eric -
Rt fpga dma timeout not waiting
Hello
I have a Target to Host DMA between. The read function sits in a while loop with a 2000ms timeout. Upon timeout it loops round and recalls the read function. On the second, and subsequent calls, it does not wait for the timeout time. I assume that this is because it was already itemed out. The error is wired to a shift register.
Does the timeout result in an error on the error line?
Is there a way to clear the timeout?
If i change it to an indefinite wait, is there a way to force the read to wake up?
Thanks
Solved!
Go to Solution.jonnnnnnn wrote:
Hello
I have a Target to Host DMA between. The read function sits in a while loop with a 2000ms timeout. Upon timeout it loops round and recalls the read function. On the second, and subsequent calls, it does not wait for the timeout time. I assume that this is because it was already itemed out. The error is wired to a shift register.
Does the timeout result in an error on the error line?
Is there a way to clear the timeout?
If i change it to an indefinite wait, is there a way to force the read to wake up?
Thanks
Does the timeout result in an error on the error line? Yes, errro -54000 if memory serves correctly. Did you try highlighting execution to see this...
Is there a way to clear the timeout? Don't wire -1, I got burned by this. The DMA actually polls in the background (I think but I never verified) so a negative timeout can slam your processor. You can maybe try interrupts, although I didn't use this method I just threw a not-too-long timeout on there and cleared the error if it was -54000
If i change it to an indefinite wait, is there a way to force the read to wake up? The read will only return when data is there, unless you have a timeout.
CLA, LabVIEW Versions 2010-2013 -
Error -1074397150 occurred at IMAQ Snap.vi
Hi.
(Sorry if my English is wrong )
I want to snap a picture - from a camera that was designed in my lab - and save it in a BMP file.
I use the "IMAQ PCI-1428" to accomplish this task and the "HL snap&save to BMP.vi".
But, as I try to run the VI I'm getting this error - "Error -1074397150 occurred at IMAQ Snap.vi", afterward I'm getting
another massage - "ERROR(DMA Timeout): The system is unable to capture all of the incoming video data....".
What should I do, to resolve this problem?
ThanX.Hi elbit,
Here is a link to Error
Codes with NI-IMAQ. You error is
addressed there and that information may be helpful to you.
I noticed you were using the PCI-1428 framegrabber card. This card supports Camera Link cameras. In order to tell the PCI-1428 how to
communicate with the camera, the NI-IMAQ driver uses a camera file that
contains camera specific information for configuration. You will need to have a properly configured
camera file for you camera that you have created.
NI has a large number of camera files that are created and
certified to support popular industrial grade cameras. In cases where a custom camera file is needed,
NI provides the NI-Camera
File Generator as a utility for camera file creation. Keep in mind that custom camera files are not
supported by National Instruments Applications Engineers.
Good luck with your camera design. Please let us know if you have any further
questions or concerns.
Regards,
Luke H -
Hello,
I am working with a device driver for a high speed PCI ADC board, that works well on all sun computers except a sunblade 2500 server. On any system except a sunblade 2500 server, I can keep acquiring data for days together without any problem. However on a sunblade 2500, the computer hangs within a few minutes after starting the acquisition.
In kadb, the command $<msgbuf displays the following message just prior to the crash:
pcisch1 (pci@1c,600000): pbm dma sync 4000e781a1e, 40000 00000000 timeout
The (pci@1c,600000) refers to my PCI ADC board.
What does this message mean and what can I do to fix this problem?
thanks for helping
aspirationHello Vitaly Filatov,
thank you for your response. Here is the info you wanted.
On Ultra 60 (where my driver works fine)
uname -srvmpi produces the following output:
SunOS 5.9 Generic_117171-07 Sun4u sparc sunw, ultra-60
and .version proudces the following output:
Release 3.31 Version 0 created 2001/7/25 20:31
OBP: 3.31.0 2001/7/25 20:31
POST: 2.0.3 2000/7/31 15:28
On Sunblade 2500 where my driver crashes, uname produces
sunos 5.9 Generic_117171-07 sun4u sparc sunw, sun-blade-2500
and .version produces
Release 4.13.5 created 2004/5/27 17:31
OBP: 4.13.5 2004/5/27 17:31 sunblade 2500, sunfire v250
OBDIAG: 4.13.5 2004/5/27 17:33
POST: 4.13.0 2004/1/16 12:39
Please note that due to the very high speed acquisition rate of the ADC board, DMA is used to transfer data from ADC onboard memory to user space.
thanks
Aspiration -
Hi,
I am currently doing continuous data acquisition with the NI 5112 using an sample rate of 2*20 MSamples/s (using fetchBinary8) for software defined radio. I transfer the data from the 5112 into the main memory in real-time and it works fine.
However, this continouos data transfer needs much CPU performance of nearly 100% of one 3 GHz P4 (I have a dual-processor system) and I would need this CPU also to process the data. I don't understand that since DMA transfer should not require CPU cycles. Has anyone an explanaition of that?
thanks, thomasWhat is the "chunk size" when you are continuously fetching data? If
you're using LabVIEW and you leave the number of points to fetch as -1
in the read/fetch VI, the VI will return as soon as it finds a non-zero
number of points to fetch. Depending on how fast your computer is and
your sample rate, you may be getting only a few points per iteration in
the loop. Setting the number of points to a larger value, say 1M for
example, may improve your CPU usage. Also, be sure to set a non-zero
timeout value because if the timeout is zero, the available points are
returned regardless of the number of points requested. Also, is this system in PCI or PXI?
The CPU usage may still be higher than you expect because we DMA the
data from the board to a temporar
y buffer before copying it to your
buffer. We do this because we can only transfer a minimum of 256 bytes
at a time with DMA. If an acquisition is less than that size or a
non-multiple of 256 bytes, some of the points at the beginning and end
of the acquisition will be invalid. Since we don't want to make the
user have to think about all that stuff, we return a buffer that is
exactly what was asked for. Unfortunately, that requires an extra copy
of the data. We may add direct DMA to the user buffer in a future
release of NI-SCOPE.
I'd be interested to hear how well your application still runs after you
add your processing algorithms into your program. You may find that the
CPU yields time and it still works ok. If not, check back with us and
we can look at alternative ways to improve the performance. -
Xorg timeout at boot - ASUS N550JV
Hello everybody,
I've become an Arch user since only a few months and this is the first time I
write on this forum, so forgive me for any mistake on the section I have to use.
I was not sure if I had to post this problem here or in the "Kernel & Hardware"
section, since it seems to be quite serious.
My problem is that, randomly at boot, Xorg and other services give an error
message regarding a timeout that has been reached and obviously this prevents
KDM from starting. I have tried to figure out what the problem is analyzing both
"dmesg" output and "Xorg.0.log".
The result is that I have found some error messages but I'm not able to figure
out which is the true cause of my problem.
The problems I have are related with:
Nouveau: My ASUS N550JV has an Nvidia Optimus configuration on a GeForce 750M
which creates many error messages, but those are the same whether the system boots
up correctly or it doesn't.
ELAN Touchscreen: My touchscreen keeps connecting and disconnecting about 20
times during boot and then it start working. This leads to various messages
regarding it. (It is always on port 10 of usb bus 1 or 3)
systemd-logind: In Xorg I get an error regarding this process.
I have tried to set the touchscreen as unauthorized through a udev rule but the
only result is that I have an infinite series of connections and disconnections
instead of only 20.
Here are my logs:
dmesg - correct boot:
[ 0.000000] CPU0 microcode updated early to revision 0x1c, date = 2014-07-03
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 3.17.2-1-ARCH (builduser@thomas) (gcc version 4.9.1 20140903 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Oct 30 20:49:39 CET 2014
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=890c99f6-7784-4c48-8533-624b3c868983 rw quiet splash acpi_osi=
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000059000-0x000000000009dfff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009e000-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000b9bbbfff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000b9bbc000-0x00000000b9bc2fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000b9bc3000-0x00000000ba3fafff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000ba3fb000-0x00000000ba680fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ba681000-0x00000000c98eafff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000c98eb000-0x00000000c9af2fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000c9af3000-0x00000000c9e25fff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000c9e26000-0x00000000cab25fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000cab26000-0x00000000caf59fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000caf5a000-0x00000000caffefff] type 20
[ 0.000000] BIOS-e820: [mem 0x00000000cafff000-0x00000000caffffff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000cbc00000-0x00000000cfdfffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000042f1fffff] usable
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] efi: EFI v2.31 by American Megatrends
[ 0.000000] efi: ACPI 2.0=0xc9eae000 ACPI=0xc9eae000 SMBIOS=0xcaf58418
[ 0.000000] efi: mem00: type=7, attr=0xf, range=[0x0000000000000000-0x0000000000058000) (0MB)
[ 0.000000] efi: mem01: type=0, attr=0xf, range=[0x0000000000058000-0x0000000000059000) (0MB)
[ 0.000000] efi: mem02: type=7, attr=0xf, range=[0x0000000000059000-0x000000000009e000) (0MB)
[ 0.000000] efi: mem03: type=0, attr=0xf, range=[0x000000000009e000-0x00000000000a0000) (0MB)
[ 0.000000] efi: mem04: type=2, attr=0xf, range=[0x0000000000100000-0x0000000001053000) (15MB)
[ 0.000000] efi: mem05: type=7, attr=0xf, range=[0x0000000001053000-0x0000000002000000) (15MB)
[ 0.000000] efi: mem06: type=2, attr=0xf, range=[0x0000000002000000-0x0000000002f53000) (15MB)
[ 0.000000] efi: mem07: type=7, attr=0xf, range=[0x0000000002f53000-0x0000000037832000) (840MB)
[ 0.000000] efi: mem08: type=2, attr=0xf, range=[0x0000000037832000-0x0000000037c11000) (3MB)
[ 0.000000] efi: mem09: type=7, attr=0xf, range=[0x0000000037c11000-0x0000000084a72000) (1230MB)
[ 0.000000] efi: mem10: type=2, attr=0xf, range=[0x0000000084a72000-0x00000000b67a0000) (797MB)
[ 0.000000] efi: mem11: type=7, attr=0xf, range=[0x00000000b67a0000-0x00000000b9b9f000) (51MB)
[ 0.000000] efi: mem12: type=1, attr=0xf, range=[0x00000000b9b9f000-0x00000000b9bbc000) (0MB)
[ 0.000000] efi: mem13: type=10, attr=0xf, range=[0x00000000b9bbc000-0x00000000b9bc3000) (0MB)
[ 0.000000] efi: mem14: type=4, attr=0xf, range=[0x00000000b9bc3000-0x00000000b9d17000) (1MB)
[ 0.000000] efi: mem15: type=3, attr=0xf, range=[0x00000000b9d17000-0x00000000ba3bc000) (6MB)
[ 0.000000] efi: mem16: type=4, attr=0xf, range=[0x00000000ba3bc000-0x00000000ba3d8000) (0MB)
[ 0.000000] efi: mem17: type=3, attr=0xf, range=[0x00000000ba3d8000-0x00000000ba3f2000) (0MB)
[ 0.000000] efi: mem18: type=4, attr=0xf, range=[0x00000000ba3f2000-0x00000000ba3fb000) (0MB)
[ 0.000000] efi: mem19: type=6, attr=0x800000000000000f, range=[0x00000000ba3fb000-0x00000000ba681000) (2MB)
[ 0.000000] efi: mem20: type=4, attr=0xf, range=[0x00000000ba681000-0x00000000ba690000) (0MB)
[ 0.000000] efi: mem21: type=7, attr=0xf, range=[0x00000000ba690000-0x00000000c709a000) (202MB)
[ 0.000000] efi: mem22: type=4, attr=0xf, range=[0x00000000c709a000-0x00000000c7342000) (2MB)
[ 0.000000] efi: mem23: type=7, attr=0xf, range=[0x00000000c7342000-0x00000000c7372000) (0MB)
[ 0.000000] efi: mem24: type=4, attr=0xf, range=[0x00000000c7372000-0x00000000c73a5000) (0MB)
[ 0.000000] efi: mem25: type=7, attr=0xf, range=[0x00000000c73a5000-0x00000000c73be000) (0MB)
[ 0.000000] efi: mem26: type=4, attr=0xf, range=[0x00000000c73be000-0x00000000c8c8c000) (24MB)
[ 0.000000] efi: mem27: type=7, attr=0xf, range=[0x00000000c8c8c000-0x00000000c9624000) (9MB)
[ 0.000000] efi: mem28: type=3, attr=0xf, range=[0x00000000c9624000-0x00000000c98eb000) (2MB)
[ 0.000000] efi: mem29: type=0, attr=0xf, range=[0x00000000c98eb000-0x00000000c9965000) (0MB)
[ 0.000000] efi: mem30: type=0, attr=0xf, range=[0x00000000c9965000-0x00000000c9af3000) (1MB)
[ 0.000000] efi: mem31: type=7, attr=0xf, range=[0x00000000c9af3000-0x00000000c9e1c000) (3MB)
[ 0.000000] efi: mem32: type=2, attr=0xf, range=[0x00000000c9e1c000-0x00000000c9e26000) (0MB)
[ 0.000000] efi: mem33: type=10, attr=0xf, range=[0x00000000c9e26000-0x00000000caaee000) (12MB)
[ 0.000000] efi: mem34: type=10, attr=0xf, range=[0x00000000caaee000-0x00000000cab09000) (0MB)
[ 0.000000] efi: mem35: type=10, attr=0xf, range=[0x00000000cab09000-0x00000000cab0d000) (0MB)
[ 0.000000] efi: mem36: type=10, attr=0xf, range=[0x00000000cab0d000-0x00000000cab10000) (0MB)
[ 0.000000] efi: mem37: type=10, attr=0xf, range=[0x00000000cab10000-0x00000000cab26000) (0MB)
[ 0.000000] efi: mem38: type=6, attr=0x800000000000000f, range=[0x00000000cab26000-0x00000000cae83000) (3MB)
[ 0.000000] efi: mem39: type=6, attr=0x800000000000000f, range=[0x00000000cae83000-0x00000000caf5a000) (0MB)
[ 0.000000] efi: mem40: type=5, attr=0x800000000000000f, range=[0x00000000caf5a000-0x00000000caf7b000) (0MB)
[ 0.000000] efi: mem41: type=5, attr=0x800000000000000f, range=[0x00000000caf7b000-0x00000000cafff000) (0MB)
[ 0.000000] efi: mem42: type=4, attr=0xf, range=[0x00000000cafff000-0x00000000cb000000) (0MB)
[ 0.000000] efi: mem43: type=7, attr=0xf, range=[0x0000000100000000-0x000000042f200000) (13042MB)
[ 0.000000] efi: mem44: type=0, attr=0x8000000000000000, range=[0x00000000cbc00000-0x00000000cfe00000) (66MB)
[ 0.000000] efi: mem45: type=11, attr=0x8000000000000001, range=[0x00000000f8000000-0x00000000fc000000) (64MB)
[ 0.000000] efi: mem46: type=11, attr=0x8000000000000001, range=[0x00000000fec00000-0x00000000fec01000) (0MB)
[ 0.000000] efi: mem47: type=11, attr=0x8000000000000001, range=[0x00000000fed00000-0x00000000fed04000) (0MB)
[ 0.000000] efi: mem48: type=11, attr=0x8000000000000001, range=[0x00000000fed1c000-0x00000000fed20000) (0MB)
[ 0.000000] efi: mem49: type=11, attr=0x8000000000000001, range=[0x00000000fee00000-0x00000000fee01000) (0MB)
[ 0.000000] efi: mem50: type=11, attr=0x8000000000000001, range=[0x00000000ff000000-0x0000000100000000) (16MB)
[ 0.000000] SMBIOS 2.7 present.
[ 0.000000] DMI: ASUSTeK COMPUTER INC. N550JV/N550JV, BIOS N550JV.208 11/19/2013
[ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000000] AGP: No AGP bridge found
[ 0.000000] e820: last_pfn = 0x42f200 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-DFFFF uncachable
[ 0.000000] E0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 0000000000 mask 7C00000000 write-back
[ 0.000000] 1 base 0400000000 mask 7FE0000000 write-back
[ 0.000000] 2 base 0420000000 mask 7FF0000000 write-back
[ 0.000000] 3 base 00E0000000 mask 7FE0000000 uncachable
[ 0.000000] 4 base 00D0000000 mask 7FF0000000 uncachable
[ 0.000000] 5 base 00CC000000 mask 7FFC000000 uncachable
[ 0.000000] 6 base 00CBC00000 mask 7FFFC00000 uncachable
[ 0.000000] 7 base 042F800000 mask 7FFF800000 uncachable
[ 0.000000] 8 base 042F400000 mask 7FFFC00000 uncachable
[ 0.000000] 9 base 042F200000 mask 7FFFE00000 uncachable
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] e820: update [mem 0xcbc00000-0xffffffff] usable ==> reserved
[ 0.000000] e820: last_pfn = 0xcb000 max_arch_pfn = 0x400000000
[ 0.000000] Scanning 1 areas for low memory corruption
[ 0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
[ 0.000000] Using GB pages for direct mapping
[ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
[ 0.000000] [mem 0x00000000-0x000fffff] page 4k
[ 0.000000] BRK [0x02b2f000, 0x02b2ffff] PGTABLE
[ 0.000000] BRK [0x02b30000, 0x02b30fff] PGTABLE
[ 0.000000] BRK [0x02b31000, 0x02b31fff] PGTABLE
[ 0.000000] init_memory_mapping: [mem 0x42f000000-0x42f1fffff]
[ 0.000000] [mem 0x42f000000-0x42f1fffff] page 2M
[ 0.000000] BRK [0x02b32000, 0x02b32fff] PGTABLE
[ 0.000000] init_memory_mapping: [mem 0x42c000000-0x42effffff]
[ 0.000000] [mem 0x42c000000-0x42effffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x400000000-0x42bffffff]
[ 0.000000] [mem 0x400000000-0x42bffffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x00100000-0xb9bbbfff]
[ 0.000000] [mem 0x00100000-0x001fffff] page 4k
[ 0.000000] [mem 0x00200000-0x3fffffff] page 2M
[ 0.000000] [mem 0x40000000-0x7fffffff] page 1G
[ 0.000000] [mem 0x80000000-0xb99fffff] page 2M
[ 0.000000] [mem 0xb9a00000-0xb9bbbfff] page 4k
[ 0.000000] init_memory_mapping: [mem 0xb9bc3000-0xba3fafff]
[ 0.000000] [mem 0xb9bc3000-0xb9bfffff] page 4k
[ 0.000000] [mem 0xb9c00000-0xba1fffff] page 2M
[ 0.000000] [mem 0xba200000-0xba3fafff] page 4k
[ 0.000000] BRK [0x02b33000, 0x02b33fff] PGTABLE
[ 0.000000] init_memory_mapping: [mem 0xba681000-0xc98eafff]
[ 0.000000] [mem 0xba681000-0xba7fffff] page 4k
[ 0.000000] [mem 0xba800000-0xc97fffff] page 2M
[ 0.000000] [mem 0xc9800000-0xc98eafff] page 4k
[ 0.000000] BRK [0x02b34000, 0x02b34fff] PGTABLE
[ 0.000000] init_memory_mapping: [mem 0xc9af3000-0xc9e25fff]
[ 0.000000] [mem 0xc9af3000-0xc9bfffff] page 4k
[ 0.000000] [mem 0xc9c00000-0xc9dfffff] page 2M
[ 0.000000] [mem 0xc9e00000-0xc9e25fff] page 4k
[ 0.000000] init_memory_mapping: [mem 0xcafff000-0xcaffffff]
[ 0.000000] [mem 0xcafff000-0xcaffffff] page 4k
[ 0.000000] init_memory_mapping: [mem 0x100000000-0x3ffffffff]
[ 0.000000] [mem 0x100000000-0x3ffffffff] page 1G
[ 0.000000] RAMDISK: [mem 0x37832000-0x37c10fff]
[ 0.000000] ACPI: Early table checksum verification disabled
[ 0.000000] ACPI: RSDP 0x00000000C9EAE000 000024 (v02 _ASUS_)
[ 0.000000] ACPI: XSDT 0x00000000C9EAE090 0000A4 (v01 _ASUS_ Notebook 01072009 AMI 00010013)
[ 0.000000] ACPI: FACP 0x00000000C9EC1100 00010C (v05 _ASUS_ Notebook 01072009 AMI 00010013)
[ 0.000000] ACPI: DSDT 0x00000000C9EAE248 012EB5 (v02 _ASUS_ Notebook 00000012 INTL 20120711)
[ 0.000000] ACPI: FACS 0x00000000CAB23080 000040
[ 0.000000] ACPI: APIC 0x00000000C9EC1210 000092 (v03 _ASUS_ Notebook 01072009 AMI 00010013)
[ 0.000000] ACPI: FPDT 0x00000000C9EC12A8 000044 (v01 _ASUS_ Notebook 01072009 AMI 00010013)
[ 0.000000] ACPI: ECDT 0x00000000C9EC12F0 0000C1 (v01 _ASUS_ Notebook 01072009 AMI. 00000005)
[ 0.000000] ACPI: SSDT 0x00000000C9EC13B8 00019D (v01 Intel zpodd 00001000 INTL 20091112)
[ 0.000000] ACPI: SSDT 0x00000000C9EC1558 000539 (v01 PmRef Cpu0Ist 00003000 INTL 20051117)
[ 0.000000] ACPI: SSDT 0x00000000C9EC1A98 000AD8 (v01 PmRef CpuPm 00003000 INTL 20051117)
[ 0.000000] ACPI: MCFG 0x00000000C9EC2570 00003C (v01 _ASUS_ Notebook 01072009 MSFT 00000097)
[ 0.000000] ACPI: HPET 0x00000000C9EC25B0 000038 (v01 _ASUS_ Notebook 01072009 AMI. 00000005)
[ 0.000000] ACPI: SSDT 0x00000000C9EC25E8 000298 (v01 SataRe SataTabl 00001000 INTL 20091112)
[ 0.000000] ACPI: SSDT 0x00000000C9EC2880 0042F6 (v01 SaSsdt SaSsdt 00003000 INTL 20091112)
[ 0.000000] ACPI: SSDT 0x00000000C9EC6B78 001699 (v01 SgRef SgPeg 00001000 INTL 20091112)
[ 0.000000] ACPI: BGRT 0x00000000C9EC8218 000038 (v00 _ASUS_ Notebook 01072009 ASUS 00010013)
[ 0.000000] ACPI: DMAR 0x00000000C9EC8250 0000B8 (v01 INTEL HSW 00000001 INTL 00000001)
[ 0.000000] ACPI: SSDT 0x00000000C9EC8308 0019E3 (v01 OptRef OptTabl 00001000 INTL 20120711)
[ 0.000000] ACPI: MSDM 0x00000000C9AF1E18 000055 (v03 _ASUS_ Notebook 00000000 ASUS 00000001)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] No NUMA configuration found
[ 0.000000] Faking a node at [mem 0x0000000000000000-0x000000042f1fffff]
[ 0.000000] Initmem setup node 0 [mem 0x00000000-0x42f1fffff]
[ 0.000000] NODE_DATA [mem 0x42f1f5000-0x42f1f8fff]
[ 0.000000] [ffffea0000000000-ffffea0010bfffff] PMD -> [ffff88041e800000-ffff88042e7fffff] on node 0
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x00001000-0x00ffffff]
[ 0.000000] DMA32 [mem 0x01000000-0xffffffff]
[ 0.000000] Normal [mem 0x100000000-0x42f1fffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x00001000-0x00057fff]
[ 0.000000] node 0: [mem 0x00059000-0x0009dfff]
[ 0.000000] node 0: [mem 0x00100000-0xb9bbbfff]
[ 0.000000] node 0: [mem 0xb9bc3000-0xba3fafff]
[ 0.000000] node 0: [mem 0xba681000-0xc98eafff]
[ 0.000000] node 0: [mem 0xc9af3000-0xc9e25fff]
[ 0.000000] node 0: [mem 0xcafff000-0xcaffffff]
[ 0.000000] node 0: [mem 0x100000000-0x42f1fffff]
[ 0.000000] On node 0 totalpages: 4164398
[ 0.000000] DMA zone: 64 pages used for memmap
[ 0.000000] DMA zone: 22 pages reserved
[ 0.000000] DMA zone: 3996 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 12839 pages used for memmap
[ 0.000000] DMA32 zone: 821650 pages, LIFO batch:31
[ 0.000000] Normal zone: 52168 pages used for memmap
[ 0.000000] Normal zone: 3338752 pages, LIFO batch:31
[ 0.000000] Reserving Intel graphics stolen memory at 0xcbe00000-0xcfdfffff
[ 0.000000] ACPI: PM-Timer IO Port: 0x1808
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x05] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled)
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
[ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
[ 0.000000] smpboot: Allowing 8 CPUs, 0 hotplug CPUs
[ 0.000000] PM: Registered nosave memory: [mem 0x00058000-0x00058fff]
[ 0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000fffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xb9bbc000-0xb9bc2fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xba3fb000-0xba680fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xc98eb000-0xc9af2fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xc9e26000-0xcab25fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xcab26000-0xcaf59fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xcaf5a000-0xcaffefff]
[ 0.000000] PM: Registered nosave memory: [mem 0xcb000000-0xcbbfffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xcbc00000-0xcfdfffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xcfe00000-0xf7ffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
[ 0.000000] e820: [mem 0xcfe00000-0xf7ffffff] available for PCI devices
[ 0.000000] Booting paravirtualized kernel on bare hardware
[ 0.000000] setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:8 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 29 pages/cpu @ffff88042ee00000 s86848 r8192 d23744 u262144
[ 0.000000] pcpu-alloc: s86848 r8192 d23744 u262144 alloc=1*2097152
[ 0.000000] pcpu-alloc: [0] 0 1 2 3 4 5 6 7
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 4099305
[ 0.000000] Policy zone: Normal
[ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=890c99f6-7784-4c48-8533-624b3c868983 rw quiet splash acpi_osi=
[ 0.000000] ACPI: _OSI method disabled
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340 using standard form
[ 0.000000] AGP: Checking aperture...
[ 0.000000] AGP: No AGP bridge found
[ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
[ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
[ 0.000000] Memory: 16272992K/16657592K available (5381K kernel code, 909K rwdata, 1712K rodata, 1140K init, 1176K bss, 384600K reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
[ 0.000000] Dump stacks of tasks blocking RCU-preempt GP.
[ 0.000000] RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=8.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
[ 0.000000] NR_IRQS:8448 nr_irqs:488 0
[ 0.000000] Console: colour dummy device 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] allocated 67108864 bytes of page_cgroup
[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[ 0.000000] hpet clockevent registered
[ 0.000000] tsc: Fast TSC calibration using PIT
[ 0.000000] tsc: Detected 2394.695 MHz processor
[ 0.000022] Calibrating delay loop (skipped), value calculated using timer frequency.. 4791.94 BogoMIPS (lpj=7982316)
[ 0.000025] pid_max: default: 32768 minimum: 301
[ 0.000030] ACPI: Core revision 20140724
[ 0.014782] ACPI: All ACPI Tables successfully acquired
[ 0.017374] Security Framework initialized
[ 0.017379] Yama: becoming mindful.
[ 0.018076] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes)
[ 0.020270] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes)
[ 0.021205] Mount-cache hash table entries: 32768 (order: 6, 262144 bytes)
[ 0.021217] Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes)
[ 0.021395] Initializing cgroup subsys memory
[ 0.021399] Initializing cgroup subsys devices
[ 0.021401] Initializing cgroup subsys freezer
[ 0.021402] Initializing cgroup subsys net_cls
[ 0.021404] Initializing cgroup subsys blkio
[ 0.021420] CPU: Physical Processor ID: 0
[ 0.021420] CPU: Processor Core ID: 0
[ 0.021423] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
[ 0.022200] mce: CPU supports 9 MCE banks
[ 0.022210] CPU0: Thermal monitoring enabled (TM1)
[ 0.022220] Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 1024
Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 1024, 1GB 4
[ 0.022294] Freeing SMP alternatives memory: 20K (ffffffff81a02000 - ffffffff81a07000)
[ 0.023649] ftrace: allocating 20675 entries in 81 pages
[ 0.029965] dmar: Host address width 39
[ 0.029967] dmar: DRHD base: 0x000000fed90000 flags: 0x0
[ 0.029973] dmar: IOMMU 0: reg_base_addr fed90000 ver 1:0 cap c0000020660462 ecap f0101a
[ 0.029974] dmar: DRHD base: 0x000000fed91000 flags: 0x1
[ 0.029978] dmar: IOMMU 1: reg_base_addr fed91000 ver 1:0 cap d2008020660462 ecap f010da
[ 0.029978] dmar: RMRR base: 0x000000c9a8a000 end: 0x000000c9a96fff
[ 0.029979] dmar: RMRR base: 0x000000cbc00000 end: 0x000000cfdfffff
[ 0.030045] IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1
[ 0.030045] HPET id 0 under DRHD base 0xfed91000
[ 0.030046] Queued invalidation will be enabled to support x2apic and Intr-remapping.
[ 0.030163] Enabled IRQ remapping in x2apic mode
[ 0.030163] Enabling x2apic
[ 0.030164] Enabled x2apic
[ 0.030169] Switched APIC routing to cluster x2apic.
[ 0.030563] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.063596] smpboot: CPU0: Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz (fam: 06, model: 3c, stepping: 03)
[ 0.063602] TSC deadline timer enabled
[ 0.063619] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
[ 0.063633] ... version: 3
[ 0.063634] ... bit width: 48
[ 0.063635] ... generic registers: 4
[ 0.063635] ... value mask: 0000ffffffffffff
[ 0.063636] ... max period: 0000ffffffffffff
[ 0.063637] ... fixed-purpose events: 3
[ 0.063637] ... event mask: 000000070000000f
[ 0.083734] x86: Booting SMP configuration:
[ 0.083736] .... node #0, CPUs: #1
[ 0.094859] CPU1 microcode updated early to revision 0x1c, date = 2014-07-03
[ 0.097826] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
[ 0.104507] #2
[ 0.115604] CPU2 microcode updated early to revision 0x1c, date = 2014-07-03
[ 0.125265] #3
[ 0.136363] CPU3 microcode updated early to revision 0x1c, date = 2014-07-03
[ 0.146023] #4 #5 #6 #7
[ 0.221935] x86: Booted up 1 node, 8 CPUs
[ 0.221938] smpboot: Total of 8 processors activated (38330.58 BogoMIPS)
[ 0.227804] devtmpfs: initialized
[ 0.229810] PM: Registering ACPI NVS region [mem 0xb9bbc000-0xb9bc2fff] (28672 bytes)
[ 0.229812] PM: Registering ACPI NVS region [mem 0xc9e26000-0xcab25fff] (13631488 bytes)
[ 0.230475] pinctrl core: initialized pinctrl subsystem
[ 0.230507] RTC time: 19:54:52, date: 11/04/14
[ 0.230569] NET: Registered protocol family 16
[ 0.230644] cpuidle: using governor ladder
[ 0.230646] cpuidle: using governor menu
[ 0.230666] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[ 0.230667] ACPI: bus type PCI registered
[ 0.230668] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 0.230718] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
[ 0.230719] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
[ 0.230778] PCI: Using configuration type 1 for base access
[ 0.244674] ACPI: Added _OSI(Module Device)
[ 0.244676] ACPI: Added _OSI(Processor Device)
[ 0.244677] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.244678] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.246723] ACPI : EC: EC description table is found, configuring boot EC
[ 0.248536] ACPI: Executed 2 blocks of module-level executable AML code
[ 0.334600] ACPI: Dynamic OEM Table Load:
[ 0.334606] ACPI: SSDT 0xFFFF8804180FB800 0003D3 (v01 PmRef Cpu0Cst 00003001 INTL 20051117)
[ 0.348067] ACPI: Dynamic OEM Table Load:
[ 0.348072] ACPI: SSDT 0xFFFF880418179000 0005AA (v01 PmRef ApIst 00003000 INTL 20051117)
[ 0.361297] ACPI: Dynamic OEM Table Load:
[ 0.361301] ACPI: SSDT 0xFFFF880418146000 000119 (v01 PmRef ApCst 00003000 INTL 20051117)
[ 0.375728] ACPI: Interpreter enabled
[ 0.375735] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20140724/hwxface-580)
[ 0.375740] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20140724/hwxface-580)
[ 0.375753] ACPI: (supports S0 S3 S4 S5)
[ 0.375754] ACPI: Using IOAPIC for interrupt routing
[ 0.375770] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.394125] ACPI Error: [_OSI] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359)
[ 0.394128] ACPI Error: Method parse/execution failed [\_SB_.BTKL._STA] (Node ffff88041e43b1e0), AE_NOT_FOUND (20140724/psparse-536)
[ 0.394139] ACPI Error: [_OSI] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359)
[ 0.394141] ACPI Error: Method parse/execution failed [\_SB_.BTKL._STA] (Node ffff88041e43b1e0), AE_NOT_FOUND (20140724/psparse-536)
[ 0.394992] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
[ 0.394995] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[ 0.395340] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
[ 0.395683] PCI host bridge to bus 0000:00
[ 0.395685] pci_bus 0000:00: root bus resource [bus 00-3e]
[ 0.395687] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
[ 0.395688] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
[ 0.395689] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
[ 0.395690] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000c3fff]
[ 0.395691] pci_bus 0000:00: root bus resource [mem 0x000c4000-0x000c7fff]
[ 0.395692] pci_bus 0000:00: root bus resource [mem 0x000c8000-0x000cbfff]
[ 0.395693] pci_bus 0000:00: root bus resource [mem 0x000cc000-0x000cffff]
[ 0.395694] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff]
[ 0.395695] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff]
[ 0.395695] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff]
[ 0.395696] pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff]
[ 0.395697] pci_bus 0000:00: root bus resource [mem 0xcfe00000-0xfeafffff]
[ 0.395703] pci 0000:00:00.0: [8086:0c04] type 00 class 0x060000
[ 0.395762] pci 0000:00:01.0: [8086:0c01] type 01 class 0x060400
[ 0.395788] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[ 0.395822] pci 0000:00:01.0: System wakeup disabled by ACPI
[ 0.395851] pci 0000:00:02.0: [8086:0416] type 00 class 0x030000
[ 0.395858] pci 0000:00:02.0: reg 0x10: [mem 0xf7400000-0xf77fffff 64bit]
[ 0.395863] pci 0000:00:02.0: reg 0x18: [mem 0xd0000000-0xdfffffff 64bit pref]
[ 0.395866] pci 0000:00:02.0: reg 0x20: [io 0xf000-0xf03f]
[ 0.395919] pci 0000:00:03.0: [8086:0c0c] type 00 class 0x040300
[ 0.395925] pci 0000:00:03.0: reg 0x10: [mem 0xf7a14000-0xf7a17fff 64bit]
[ 0.396003] pci 0000:00:14.0: [8086:8c31] type 00 class 0x0c0330
[ 0.396019] pci 0000:00:14.0: reg 0x10: [mem 0xf7a00000-0xf7a0ffff 64bit]
[ 0.396072] pci 0000:00:14.0: PME# supported from D3hot D3cold
[ 0.396098] pci 0000:00:14.0: System wakeup disabled by ACPI
[ 0.396124] pci 0000:00:16.0: [8086:8c3a] type 00 class 0x078000
[ 0.396141] pci 0000:00:16.0: reg 0x10: [mem 0xf7a1e000-0xf7a1e00f 64bit]
[ 0.396197] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
[ 0.396257] pci 0000:00:1a.0: [8086:8c2d] type 00 class 0x0c0320
[ 0.396275] pci 0000:00:1a.0: reg 0x10: [mem 0xf7a1c000-0xf7a1c3ff]
[ 0.396354] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
[ 0.396391] pci 0000:00:1a.0: System wakeup disabled by ACPI
[ 0.396419] pci 0000:00:1b.0: [8086:8c20] type 00 class 0x040300
[ 0.396433] pci 0000:00:1b.0: reg 0x10: [mem 0xf7a10000-0xf7a13fff 64bit]
[ 0.396494] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.396522] pci 0000:00:1b.0: System wakeup disabled by ACPI
[ 0.396546] pci 0000:00:1c.0: [8086:8c10] type 01 class 0x060400
[ 0.396605] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 0.396635] pci 0000:00:1c.0: System wakeup disabled by ACPI
[ 0.396660] pci 0000:00:1c.1: [8086:8c12] type 01 class 0x060400
[ 0.396719] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
[ 0.396770] pci 0000:00:1c.2: [8086:8c14] type 01 class 0x060400
[ 0.396829] pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
[ 0.396859] pci 0000:00:1c.2: System wakeup disabled by ACPI
[ 0.396883] pci 0000:00:1c.3: [8086:8c16] type 01 class 0x060400
[ 0.396942] pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
[ 0.396971] pci 0000:00:1c.3: System wakeup disabled by ACPI
[ 0.397004] pci 0000:00:1d.0: [8086:8c26] type 00 class 0x0c0320
[ 0.397022] pci 0000:00:1d.0: reg 0x10: [mem 0xf7a1b000-0xf7a1b3ff]
[ 0.397101] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
[ 0.397138] pci 0000:00:1d.0: System wakeup disabled by ACPI
[ 0.397167] pci 0000:00:1f.0: [8086:8c49] type 00 class 0x060100
[ 0.397304] pci 0000:00:1f.2: [8086:8c03] type 00 class 0x010601
[ 0.397317] pci 0000:00:1f.2: reg 0x10: [io 0xf0b0-0xf0b7]
[ 0.397324] pci 0000:00:1f.2: reg 0x14: [io 0xf0a0-0xf0a3]
[ 0.397330] pci 0000:00:1f.2: reg 0x18: [io 0xf090-0xf097]
[ 0.397337] pci 0000:00:1f.2: reg 0x1c: [io 0xf080-0xf083]
[ 0.397343] pci 0000:00:1f.2: reg 0x20: [io 0xf060-0xf07f]
[ 0.397349] pci 0000:00:1f.2: reg 0x24: [mem 0xf7a1a000-0xf7a1a7ff]
[ 0.397382] pci 0000:00:1f.2: PME# supported from D3hot
[ 0.397428] pci 0000:00:1f.3: [8086:8c22] type 00 class 0x0c0500
[ 0.397440] pci 0000:00:1f.3: reg 0x10: [mem 0xf7a19000-0xf7a190ff 64bit]
[ 0.397458] pci 0000:00:1f.3: reg 0x20: [io 0xf040-0xf05f]
[ 0.397546] pci 0000:01:00.0: [10de:0fe4] type 00 class 0x030200
[ 0.397553] pci 0000:01:00.0: reg 0x10: [mem 0xf6000000-0xf6ffffff]
[ 0.397559] pci 0000:01:00.0: reg 0x14: [mem 0xe0000000-0xefffffff 64bit pref]
[ 0.397566] pci 0000:01:00.0: reg 0x1c: [mem 0xf0000000-0xf1ffffff 64bit pref]
[ 0.397570] pci 0000:01:00.0: reg 0x24: [io 0xe000-0xe07f]
[ 0.397575] pci 0000:01:00.0: reg 0x30: [mem 0xf7000000-0xf707ffff pref]
[ 0.397610] pci 0000:01:00.0: System wakeup disabled by ACPI
[ 0.401292] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.401294] pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
[ 0.401297] pci 0000:00:01.0: bridge window [mem 0xf6000000-0xf70fffff]
[ 0.401300] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xf1ffffff 64bit pref]
[ 0.401365] acpiphp: Slot [1] registered
[ 0.401370] pci 0000:00:1c.0: PCI bridge to [bus 02]
[ 0.401445] pci 0000:00:1c.1: PCI bridge to [bus 03]
[ 0.401529] pci 0000:04:00.0: [168c:0032] type 00 class 0x028000
[ 0.401555] pci 0000:04:00.0: reg 0x10: [mem 0xf7900000-0xf797ffff 64bit]
[ 0.401608] pci 0000:04:00.0: reg 0x30: [mem 0xf7980000-0xf798ffff pref]
[ 0.401677] pci 0000:04:00.0: supports D1 D2
[ 0.401678] pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.401705] pci 0000:04:00.0: System wakeup disabled by ACPI
[ 0.407973] pci 0000:00:1c.2: PCI bridge to [bus 04]
[ 0.407979] pci 0000:00:1c.2: bridge window [mem 0xf7900000-0xf79fffff]
[ 0.408064] pci 0000:05:00.0: [10ec:8168] type 00 class 0x020000
[ 0.408083] pci 0000:05:00.0: reg 0x10: [io 0xd000-0xd0ff]
[ 0.408112] pci 0000:05:00.0: reg 0x18: [mem 0xf7800000-0xf7800fff 64bit]
[ 0.408130] pci 0000:05:00.0: reg 0x20: [mem 0xf2100000-0xf2103fff 64bit pref]
[ 0.408223] pci 0000:05:00.0: supports D1 D2
[ 0.408224] pci 0000:05:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.408257] pci 0000:05:00.0: System wakeup disabled by ACPI
[ 0.414653] pci 0000:00:1c.3: PCI bridge to [bus 05]
[ 0.414656] pci 0000:00:1c.3: bridge window [io 0xd000-0xdfff]
[ 0.414660] pci 0000:00:1c.3: bridge window [mem 0xf7800000-0xf78fffff]
[ 0.414665] pci 0000:00:1c.3: bridge window [mem 0xf2100000-0xf21fffff 64bit pref]
[ 0.414691] acpi PNP0A08:00: Disabling ASPM (FADT indicates it is unsupported)
[ 0.415376] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 11 12) *0, disabled.
[ 0.415417] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 12) *0, disabled.
[ 0.415456] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 12) *0, disabled.
[ 0.415494] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 12) *0, disabled.
[ 0.415531] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 12) *0, disabled.
[ 0.415568] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 12) *0, disabled.
[ 0.415605] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 12) *0, disabled.
[ 0.415643] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 12) *0, disabled.
[ 0.415672] ACPI Error: [_OSI] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359)
[ 0.415675] ACPI Error: Method parse/execution failed [\_SB_.BTKL._STA] (Node ffff88041e43b1e0), AE_NOT_FOUND (20140724/psparse-536)
[ 0.415871] ACPI: Enabled 5 GPEs in block 00 to 3F
[ 0.415938] ACPI : EC: GPE = 0x19, I/O: command/status = 0x66, data = 0x62
[ 0.416020] vgaarb: setting as boot device: PCI:0000:00:02.0
[ 0.416022] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
[ 0.416025] vgaarb: loaded
[ 0.416026] vgaarb: bridge control possible 0000:00:02.0
[ 0.416090] PCI: Using ACPI for IRQ routing
[ 0.417339] PCI: pci_cache_line_size set to 64 bytes
[ 0.417394] e820: reserve RAM buffer [mem 0x00058000-0x0005ffff]
[ 0.417395] e820: reserve RAM buffer [mem 0x0009e000-0x0009ffff]
[ 0.417395] e820: reserve RAM buffer [mem 0xb9bbc000-0xbbffffff]
[ 0.417396] e820: reserve RAM buffer [mem 0xba3fb000-0xbbffffff]
[ 0.417397] e820: reserve RAM buffer [mem 0xc98eb000-0xcbffffff]
[ 0.417398] e820: reserve RAM buffer [mem 0xc9e26000-0xcbffffff]
[ 0.417399] e820: reserve RAM buffer [mem 0xcb000000-0xcbffffff]
[ 0.417400] e820: reserve RAM buffer [mem 0x42f200000-0x42fffffff]
[ 0.417465] NetLabel: Initializing
[ 0.417466] NetLabel: domain hash size = 128
[ 0.417467] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.417474] NetLabel: unlabeled traffic allowed by default
[ 0.417493] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
[ 0.417496] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
[ 0.419526] Switched to clocksource hpet
[ 0.422883] pnp: PnP ACPI init
[ 0.422937] system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
[ 0.422939] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
[ 0.423093] system 00:01: [io 0x0680-0x069f] has been reserved
[ 0.423094] system 00:01: [io 0xffff] has been reserved
[ 0.423095] system 00:01: [io 0xffff] has been reserved
[ 0.423096] system 00:01: [io 0xffff] has been reserved
[ 0.423097] system 00:01: [io 0x1c00-0x1cfe] has been reserved
[ 0.423099] system 00:01: [io 0x1d00-0x1dfe] has been reserved
[ 0.423100] system 00:01: [io 0x1e00-0x1efe] has been reserved
[ 0.423101] system 00:01: [io 0x1f00-0x1ffe] has been reserved
[ 0.423102] system 00:01: [io 0x1800-0x18fe] could not be reserved
[ 0.423103] system 00:01: [io 0x164e-0x164f] has been reserved
[ 0.423105] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.423123] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
[ 0.423154] system 00:03: [io 0x1854-0x1857] has been reserved
[ 0.423155] system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
[ 0.423184] system 00:04: [io 0x04d0-0x04d1] has been reserved
[ 0.423186] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.423206] system 00:05: [io 0x0240-0x0259] has been reserved
[ 0.423207] system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.423243] pnp 00:06: Plug and Play ACPI device, IDs ETD0105 SYN0a00 SYN0002 PNP0f03 PNP0f13 PNP0f12 (active)
[ 0.423267] pnp 00:07: Plug and Play ACPI device, IDs ATK3001 PNP030b (active)
[ 0.423500] system 00:08: [mem 0xfed1c000-0xfed1ffff] has been reserved
[ 0.423501] system 00:08: [mem 0xfed10000-0xfed17fff] has been reserved
[ 0.423502] system 00:08: [mem 0xfed18000-0xfed18fff] has been reserved
[ 0.423503] system 00:08: [mem 0xfed19000-0xfed19fff] has been reserved
[ 0.423505] system 00:08: [mem 0xf8000000-0xfbffffff] has been reserved
[ 0.423506] system 00:08: [mem 0xfed20000-0xfed3ffff] has been reserved
[ 0.423507] system 00:08: [mem 0xfed90000-0xfed93fff] could not be reserved
[ 0.423508] system 00:08: [mem 0xfed45000-0xfed8ffff] has been reserved
[ 0.423510] system 00:08: [mem 0xff000000-0xffffffff] has been reserved
[ 0.423511] system 00:08: [mem 0xfee00000-0xfeefffff] could not be reserved
[ 0.423512] system 00:08: [mem 0xf7fef000-0xf7feffff] has been reserved
[ 0.423513] system 00:08: [mem 0xf7ff0000-0xf7ff0fff] has been reserved
[ 0.423515] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.423558] system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.423655] ACPI Error: [_OSI] Namespace lookup failure, AE_NOT_FOUND (20140724/psargs-359)
[ 0.423658] ACPI Error: Method parse/execution failed [\_SB_.BTKL._STA] (Node ffff88041e43b1e0), AE_NOT_FOUND (20140724/psparse-536)
[ 0.423737] pnp: PnP ACPI: found 10 devices
[ 0.429555] pci 0000:00:1c.1: bridge window [io 0x1000-0x0fff] to [bus 03] add_size 1000
[ 0.429557] pci 0000:00:1c.1: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000
[ 0.429559] pci 0000:00:1c.1: bridge window [mem 0x00100000-0x000fffff] to [bus 03] add_size 200000
[ 0.429572] pci 0000:00:1c.1: res[14]=[mem 0x00100000-0x000fffff] get_res_add_size add_size 200000
[ 0.429573] pci 0000:00:1c.1: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
[ 0.429574] pci 0000:00:1c.1: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
[ 0.429578] pci 0000:00:1c.1: BAR 14: assigned [mem 0xcfe00000-0xcfffffff]
[ 0.429584] pci 0000:00:1c.1: BAR 15: assigned [mem 0xf2200000-0xf23fffff 64bit pref]
[ 0.429585] pci 0000:00:1c.1: BAR 13: assigned [io 0x2000-0x2fff]
[ 0.429587] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.429588] pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
[ 0.429591] pci 0000:00:01.0: bridge window [mem 0xf6000000-0xf70fffff]
[ 0.429592] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xf1ffffff 64bit pref]
[ 0.429595] pci 0000:00:1c.0: PCI bridge to [bus 02]
[ 0.429604] pci 0000:00:1c.1: PCI bridge to [bus 03]
[ 0.429606] pci 0000:00:1c.1: bridge window [io 0x2000-0x2fff]
[ 0.429610] pci 0000:00:1c.1: bridge window [mem 0xcfe00000-0xcfffffff]
[ 0.429614] pci 0000:00:1c.1: bridge window [mem 0xf2200000-0xf23fffff 64bit pref]
[ 0.429618] pci 0000:00:1c.2: PCI bridge to [bus 04]
[ 0.429622] pci 0000:00:1c.2: bridge window [mem 0xf7900000-0xf79fffff]
[ 0.429629] pci 0000:00:1c.3: PCI bridge to [bus 05]
[ 0.429631] pci 0000:00:1c.3: bridge window [io 0xd000-0xdfff]
[ 0.429635] pci 0000:00:1c.3: bridge window [mem 0xf7800000-0xf78fffff]
[ 0.429639] pci 0000:00:1c.3: bridge window [mem 0xf2100000-0xf21fffff 64bit pref]
[ 0.429644] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
[ 0.429645] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
[ 0.429646] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
[ 0.429647] pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000c3fff]
[ 0.429648] pci_bus 0000:00: resource 8 [mem 0x000c4000-0x000c7fff]
[ 0.429649] pci_bus 0000:00: resource 9 [mem 0x000c8000-0x000cbfff]
[ 0.429650] pci_bus 0000:00: resource 10 [mem 0x000cc000-0x000cffff]
[ 0.429651] pci_bus 0000:00: resource 11 [mem 0x000d0000-0x000d3fff]
[ 0.429652] pci_bus 0000:00: resource 12 [mem 0x000d4000-0x000d7fff]
[ 0.429653] pci_bus 0000:00: resource 13 [mem 0x000d8000-0x000dbfff]
[ 0.429654] pci_bus 0000:00: resource 14 [mem 0x000dc000-0x000dffff]
[ 0.429655] pci_bus 0000:00: resource 15 [mem 0xcfe00000-0xfeafffff]
[ 0.429656] pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
[ 0.429657] pci_bus 0000:01: resource 1 [mem 0xf6000000-0xf70fffff]
[ 0.429659] pci_bus 0000:01: resource 2 [mem 0xe0000000-0xf1ffffff 64bit pref]
[ 0.429660] pci_bus 0000:03: resource 0 [io 0x2000-0x2fff]
[ 0.429661] pci_bus 0000:03: resource 1 [mem 0xcfe00000-0xcfffffff]
[ 0.429662] pci_bus 0000:03: resource 2 [mem 0xf2200000-0xf23fffff 64bit pref]
[ 0.429663] pci_bus 0000:04: resource 1 [mem 0xf7900000-0xf79fffff]
[ 0.429664] pci_bus 0000:05: resource 0 [io 0xd000-0xdfff]
[ 0.429665] pci_bus 0000:05: resource 1 [mem 0xf7800000-0xf78fffff]
[ 0.429666] pci_bus 0000:05: resource 2 [mem 0xf2100000-0xf21fffff 64bit pref]
[ 0.429683] NET: Registered protocol family 2
[ 0.429836] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.429977] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[ 0.430077] TCP: Hash tables configured (established 131072 bind 65536)
[ 0.430088] TCP: reno registered
[ 0.430101] UDP hash table entries: 8192 (order: 6, 262144 bytes)
[ 0.430138] UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes)
[ 0.430194] NET: Registered protocol family 1
[ 0.430204] pci 0000:00:02.0: Video device with shadowed ROM
[ 0.430531] PCI: CLS 64 bytes, default 64
[ 0.430562] Unpacking initramfs...
[ 0.469892] Freeing initrd memory: 3964K (ffff880037832000 - ffff880037c11000)
[ 0.469905] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[ 0.469907] software IO TLB [mem 0xc309a000-0xc709a000] (64MB) mapped at [ffff8800c309a000-ffff8800c7099fff]
[ 0.470107] RAPL PMU detected, hw unit 2^-14 Joules, API unit is 2^-32 Joules, 4 fixed counters 655360 ms ovfl timer
[ 0.470140] microcode: CPU0 sig=0x306c3, pf=0x20, revision=0x1c
[ 0.470145] microcode: CPU1 sig=0x306c3, pf=0x20, revision=0x1c
[ 0.470152] microcode: CPU2 sig=0x306c3, pf=0x20, revision=0x1c
[ 0.470157] microcode: CPU3 sig=0x306c3, pf=0x20, revision=0x1c
[ 0.470163] microcode: CPU4 sig=0x306c3, pf=0x20, revision=0x1c
[ 0.470168] microcode: CPU5 sig=0x306c3, pf=0x20, revision=0x1c
[ 0.470173] microcode: CPU6 sig=0x306c3, pf=0x20, revision=0x1c
[ 0.470178] microcode: CPU7 sig=0x306c3, pf=0x20, revision=0x1c
[ 0.470208] microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
[ 0.470225] Scanning for low memory corruption every 60 seconds
[ 0.470411] futex hash table entries: 2048 (order: 5, 131072 bytes)
[ 0.470425] Initialise system trusted keyring
[ 0.470652] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 0.471462] zpool: loaded
[ 0.471463] zbud: loaded
[ 0.471577] VFS: Disk quotas dquot_6.5.2
[ 0.471598] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 0.471674] msgmni has been set to 31868
[ 0.471710] Key type big_key registered
[ 0.471832] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 0.471874] io scheduler noop registered
[ 0.471875] io scheduler deadline registered
[ 0.471892] io scheduler cfq registered (default)
[ 0.471993] pcieport 0000:00:01.0: irq 26 for MSI/MSI-X
[ 0.472084] pcieport 0000:00:1c.0: irq 27 for MSI/MSI-X
[ 0.472180] pcieport 0000:00:1c.1: irq 28 for MSI/MSI-X
[ 0.472279] pcieport 0000:00:1c.2: irq 29 for MSI/MSI-X
[ 0.472374] pcieport 0000:00:1c.3: irq 30 for MSI/MSI-X
[ 0.472437] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
[ 0.472438] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
[ 0.472439] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
[ 0.472451] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
[ 0.472454] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
[ 0.472465] pcieport 0000:00:1c.1: Signaling PME through PCIe PME interrupt
[ 0.472468] pcie_pme 0000:00:1c.1:pcie01: service driver pcie_pme loaded
[ 0.472479] pcieport 0000:00:1c.2: Signaling PME through PCIe PME interrupt
[ 0.472480] pci 0000:04:00.0: Signaling PME through PCIe PME interrupt
[ 0.472483] pcie_pme 0000:00:1c.2:pcie01: service driver pcie_pme loaded
[ 0.472494] pcieport 0000:00:1c.3: Signaling PME through PCIe PME interrupt
[ 0.472495] pci 0000:05:00.0: Signaling PME through PCIe PME interrupt
[ 0.472498] pcie_pme 0000:00:1c.3:pcie01: service driver pcie_pme loaded
[ 0.472508] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 0.472537] pciehp 0000:00:1c.1:pcie04: Slot #1 AttnBtn- AttnInd- PwrInd- PwrCtrl- MRL- Interlock- NoCompl+ LLActRep+
[ 0.472563] pciehp 0000:00:1c.1:pcie04: service driver pciehp loaded
[ 0.472565] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 0.472587] efifb: probing for efifb
[ 0.472602] efifb: framebuffer at 0xd0000000, mapped to 0xffffc90005c00000, using 8128k, total 8128k
[ 0.472603] efifb: mode is 1920x1080x32, linelength=7680, pages=1
[ 0.472603] efifb: scrolling: redraw
[ 0.472604] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 0.475552] Console: switching to colour frame buffer device 240x67
[ 0.478798] fb0: EFI VGA frame buffer device
[ 0.478804] intel_idle: MWAIT substates: 0x42120
[ 0.478805] intel_idle: v0.4 model 0x3C
[ 0.478805] intel_idle: lapic_timer_reliable_states 0xffffffff
[ 0.479023] GHES: HEST is not enabled!
[ 0.479072] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 0.479377] Linux agpgart interface v0.103
[ 0.479427] rtc_cmos 00:02: RTC can wake from S4
[ 0.479529] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
[ 0.479555] rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
[ 0.479563] Intel P-state driver initializing.
[ 0.479725] ledtrig-cpu: registered to indicate activity on CPUs
[ 0.479981] TCP: cubic registered
[ 0.480204] NET: Registered protocol family 10
[ 0.480721] NET: Registered protocol family 17
[ 0.481506] Loading compiled-in X.509 certificates
[ 0.481536] registered taskstats version 1
[ 0.482885] Magic number: 6:238:950
[ 0.482926] tty tty7: hash matches
[ 0.482995] cpu cpu5: hash matches
[ 0.483018] memory memory3: hash matches
[ 0.483093] rtc_cmos 00:02: setting system clock to 2014-11-04 19:54:52 UTC (1415130892)
[ 0.483290] PM: Hibernation image not present or could not be loaded.
[ 0.485249] Freeing unused kernel memory: 1140K (ffffffff818e5000 - ffffffff81a02000)
[ 0.485252] Write protecting the kernel read-only data: 8192k
[ 0.489838] Freeing unused kernel memory: 752K (ffff880002544000 - ffff880002600000)
[ 0.491668] Freeing unused kernel memory: 336K (ffff8800027ac000 - ffff880002800000)
[ 0.504803] random: systemd-tmpfile urandom read with 1 bits of entropy available
[ 0.507092] systemd-udevd[77]: starting version 216
[ 0.524055] i8042: PNP: PS/2 Controller [PNP030b:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
[ 0.527632] i8042: Detected active multiplexing controller, rev 1.1
[ 0.529011] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 0.529023] serio: i8042 AUX0 port at 0x60,0x64 irq 12
[ 0.529025] serio: i8042 AUX1 port at 0x60,0x64 irq 12
[ 0.529027] serio: i8042 AUX2 port at 0x60,0x64 irq 12
[ 0.529028] serio: i8042 AUX3 port at 0x60,0x64 irq 12
[ 0.530334] ACPI: bus type USB registered
[ 0.530352] usbcore: registered new interface driver usbfs
[ 0.530360] usbcore: registered new interface driver hub
[ 0.530397] usbcore: registered new device driver usb
[ 0.530948] SCSI subsystem initialized
[ 0.530969] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.531185] ehci-pci: EHCI PCI platform driver
[ 0.531330] ehci-pci 0000:00:1a.0: EHCI Host Controller
[ 0.531336] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
[ 0.531347] ehci-pci 0000:00:1a.0: debug port 2
[ 0.531967] libata version 3.00 loaded.
[ 0.535264] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
[ 0.535282] ehci-pci 0000:00:1a.0: irq 16, io mem 0xf7a1c000
[ 0.542977] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[ 0.543147] hub 1-0:1.0: USB hub found
[ 0.543153] hub 1-0:1.0: 2 ports detected
[ 0.543377] ehci-pci 0000:00:1d.0: EHCI Host Controller
[ 0.543382] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
[ 0.543393] ehci-pci 0000:00:1d.0: debug port 2
[ 0.547295] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
[ 0.547305] ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7a1b000
[ 0.556323] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[ 0.556509] hub 2-0:1.0: USB hub found
[ 0.556514] hub 2-0:1.0: 2 ports detected
[ 0.556739] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 0.556747] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3
[ 0.556840] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
[ 0.556860] xhci_hcd 0000:00:14.0: irq 31 for MSI/MSI-X
[ 0.557073] hub 3-0:1.0: USB hub found
[ 0.557091] hub 3-0:1.0: 14 ports detected
[ 0.559496] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 0.559498] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4
[ 0.559706] hub 4-0:1.0: USB hub found
[ 0.559716] hub 4-0:1.0: 4 ports detected
[ 0.560402] ahci 0000:00:1f.2: version 3.0
[ 0.560543] ahci 0000:00:1f.2: irq 32 for MSI/MSI-X
[ 0.560575] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 4 ports 6 Gbps 0x14 impl SATA mode
[ 0.560577] ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part ems apst
[ 0.566854] scsi host0: ahci
[ 0.567019] scsi host1: ahci
[ 0.567141] scsi host2: ahci
[ 0.567252] scsi host3: ahci
[ 0.567341] scsi host4: ahci
[ 0.567374] ata1: DUMMY
[ 0.567375] ata2: DUMMY
[ 0.567378] ata3: SATA max UDMA/133 abar m2048@0xf7a1a000 port 0xf7a1a200 irq 32
[ 0.567379] ata4: DUMMY
[ 0.567381] ata5: SATA max UDMA/133 abar m2048@0xf7a1a000 port 0xf7a1a300 irq 32
[ 0.583513] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
[ 0.849986] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 0.886643] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 0.886662] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 0.888182] ata3.00: ATAPI: MATSHITADVD-RAM UJ8C2 S, 1.00, max UDMA/133
[ 0.889544] ata3.00: configured for UDMA/133
[ 0.890893] scsi 2:0:0:0: CD-ROM MATSHITA DVD-RAM UJ8C2 S 1.00 PQ: 0 ANSI: 5
[ 0.893237] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[ 0.893255] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[ 0.893257] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[ 0.899594] ata5.00: ATA-8: ST1000LM024 HN-M101MBB, 2AR20002, max UDMA/133
[ 0.899597] ata5.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 0.906204] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[ 0.906208] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[ 0.906210] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[ 0.912602] ata5.00: configured for UDMA/133
[ 0.912727] scsi 4:0:0:0: Direct-Access ATA ST1000LM024 HN-M 0002 PQ: 0 ANSI: 5
[ 0.925609] sr 2:0:0:0: [sr0] scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
[ 0.925611] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 0.925730] sr 2:0:0:0: Attached scsi CD-ROM sr0
[ 0.925834] sd 4:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 0.925837] sd 4:0:0:0: [sda] 4096-byte physical blocks
[ 0.925856] sd 4:0:0:0: [sda] Write Protect is off
[ 0.925858] sd 4:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 0.925869] sd 4:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 0.973953] hub 1-1:1.0: USB hub found
[ 0.974048] hub 1-1:1.0: 6 ports detected
[ 0.984057] sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
[ 0.984721] sd 4:0:0:0: [sda] Attached SCSI disk
[ 1.080102] usb 2-1: new high-speed USB device number 2 using ehci-pci
[ 1.204162] hub 2-1:1.0: USB hub found
[ 1.204272] hub 2-1:1.0: 8 ports detected
[ 1.363749] usb 3-3: new full-speed USB device number 2 using xhci_hcd
[ 1.473732] tsc: Refined TSC clocksource calibration: 2394.455 MHz
[ 1.541050] hidraw: raw HID events driver (C) Jiri Kosina
[ 1.544660] usbcore: registered new interface driver usbhid
[ 1.544662] usbhid: USB HID core driver
[ 1.545882] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-3/input2
[ 1.598252] input: Logitech Unifying Device. Wireless PID:1025 as /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.2/0003:046D:C52B.0003/0003:046D:C52B.0004/input/input5
[ 1.598295] logitech-djdevice 0003:046D:C52B.0004: input,hidraw1: USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:1025] on usb-0000:00:14.0-3:1
[ 1.697277] usb 3-5: new full-speed USB device number 3 using xhci_hcd
[ 2.030900] usb 3-7: new high-speed USB device number 4 using xhci_hcd
[ 2.106192] random: nonblocking pool is initialized
[ 2.142430] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null)
[ 2.467952] usb 3-8: new high-speed USB device number 5 using xhci_hcd
[ 2.474803] Switched to clocksource tsc
[ 2.801571] usb 3-10: new full-speed USB device number 6 using xhci_hcd
[ 2.976444] usb 3-10: ep 0x2 - rounding interval to 64 microframes, ep desc says 80 microframes
[ 4.590179] systemd-readahead[174]: Bumped block_nr parameter of 8:0 to 20480. This is a temporary hack and should be removed one day.
[ 4.909080] EXT4-fs (sda8): re-mounted. Opts: data=ordered
[ 5.079193] usb 3-10: USB disconnect, device number 6
[ 5.364273] vboxdrv: Found 8 processor cores.
[ 5.364722] vboxdrv: fAsync=0 offMin=0x1a7 offMax=0x8e8f
[ 5.364769] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
[ 5.364770] vboxdrv: Successfully loaded version 4.3.18_OSE (interface 0x001a0008).
[ 5.386896] usb 3-10: new full-speed USB device number 7 using xhci_hcd
[ 5.485195] systemd-udevd[207]: starting version 216
[ 5.562316] usb 3-10: ep 0x2 - rounding interval to 64 microframes, ep desc says 80 microframes
[ 5.696307] vboxpci: IOMMU not found (not registered)
[ 7.665644] usb 3-10: USB disconnect, device number 7
[ 7.975717] usb 3-10: new full-speed USB device number 8 using xhci_hcd
[ 8.150721] usb 3-10: ep 0x2 - rounding interval to 64 microframes, ep desc says 80 microframes
[ 8.524128] wmi: Mapper loaded
[ 8.880804] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input6
[ 8.882110] ACPI: Lid Switch [LID]
[ 8.882160] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input7
[ 8.882163] ACPI: Sleep Button [SLPB]
[ 8.882302] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input8
[ 8.882304] ACPI: Power Button [PWRF]
[ 8.925656] ACPI: AC Adapter [AC0] (off-line)
[ 8.945894] ACPI: Battery Slot [BAT0] (battery present)
[ 9.120666] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 9.121374] thermal LNXTHERM:00: registered as thermal_zone0
[ 9.121376] ACPI: Thermal Zone [THRM] (49 C)
[ 9.279861] EDAC MC: Ver: 3.0.0
[ 9.311386] rtc-efi rtc-efi: rtc core: registered rtc-efi as rtc1
[ 9.339936] input: PC Speaker as /devices/platform/pcspkr/input/input9
[ 9.514276] EDAC ie31200: No ECC support
[ 9.527077] ACPI Warning: SystemIO range 0x000000000000f040-0x000000000000f05f conflicts with OpRegion 0x000000000000f040-0x000000000000f04f (\SMB0) (20140724/utaddress-258)
[ 9.527083] ACPI Warning: SystemIO range 0x000000000000f040-0x000000000000f05f conflicts with OpRegion 0x000000000000f040-0x000000000000f04f (\_SB_.PCI0.SBUS.SMBI) (20140724/utaddress-258)
[ 9.527086] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 9.571525] mei_me 0000:00:16.0: irq 33 for MSI/MSI-X
[ 9.977435] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 9.977442] r8169 0000:05:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 9.984309] r8169 0000:05:00.0: irq 34 for MSI/MSI-X
[ 9.984487] r8169 0000:05:00.0 eth0: RTL8168g/8111g at 0xffffc900018d8000, ac:22:0b:02:e5:73, XID 0c000800 IRQ 34
[ 9.984489] r8169 0000:05:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 10.233442] iTCO_vendor_support: vendor-support=0
[ 10.254345] usb 3-10: USB disconnect, device number 8
[ 10.304926] r8169 0000:05:00.0 enp5s0: renamed from eth0
[ 10.328363] systemd-udevd[241]: renamed network interface eth0 to enp5s0
[ 10.328555] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[ 10.328584] iTCO_wdt: Found a Lynx Point TCO device (Version=2, TCOBASE=0x1860)
[ 10.328676] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 10.501711] cfg80211: Calling CRDA to update world regulatory domain
[ 10.536029] psmouse serio4: elantech: assuming hardware version 4 (with firmware version 0x361f03)
[ 10.551690] psmouse serio4: elantech: Synaptics capabilities query result 0x10, 0x14, 0x0e.
[ 10.564444] usb 3-10: new full-speed USB device number 9 using xhci_hcd
[ 10.627348] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio4/input/input13
[ 10.739506] usb 3-10: ep 0x2 - rounding interval to 64 microframes, ep desc says 80 microframes
[ 10.842138] asus_wmi: ASUS WMI generic driver loaded
[ 10.842217] snd_hda_intel 0000:00:1b.0: Applying patch firmware 'alsa/n550-bass'
[ 10.861070] AVX2 version of gcm_enc/dec engaged.
[ 10.888780] mousedev: PS/2 mouse device common for all mice
[ 11.001716] snd_hda_intel 0000:00:1b.0: irq 35 for MSI/MSI-X
[ 11.012548] sound hdaudioC1D0: autoconfig: line_outs=2 (0x14/0x1a/0x0/0x0/0x0) type:speaker
[ 11.012550] sound hdaudioC1D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 11.012551] sound hdaudioC1D0: hp_outs=1 (0x15/0x0/0x0/0x0/0x0)
[ 11.012552] sound hdaudioC1D0: mono: mono_out=0x0
[ 11.012553] sound hdaudioC1D0: inputs:
[ 11.012554] sound hdaudioC1D0: Mic=0x1b
[ 11.012556] sound hdaudioC1D0: Internal Mic=0x12
[ 11.019145] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card1/input14
[ 11.019195] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card1/input15
[ 11.453185] [drm] Initialized drm 1.1.0 20060810
[ 11.463616] asus_wmi: Initialization: 0x1
[ 11.463642] asus_wmi: BIOS WMI version: 7.9
[ 11.463673] asus_wmi: SFUN value: 0x6a0877
[ 11.464347] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input16
[ 11.471973] asus_wmi: Backlight controlled by ACPI video driver
[ 11.645480] input: ELAN Touchscreen as /devices/pci0000:00/0000:00:14.0/usb3/3-10/3-10:1.0/0003:04F3:010C.0008/input/input17
[ 11.645667] hid-multitouch 0003:04F3:010C.0008: input,hiddev0,hidraw2: USB HID v1.10 Device [ELAN Touchscreen] on usb-0000:00:14.0-10/input0
[ 11.736055] [drm] Memory usable by graphics device = 2048M
[ 11.736057] [drm] Replacing VGA console driver
[ 11.736059] checking generic (d0000000 7f0000) vs hw (d0000000 10000000)
[ 11.736060] fb: switching to inteldrmfb from EFI VGA
[ 11.736083] Console: switching to colour dummy device 80x25
[ 11.755427] i915 0000:00:02.0: irq 36 for MSI/MSI-X
[ 11.755436] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 11.755437] [drm] Driver supports precise vblank timestamp query.
[ 11.755455] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 11.792893] [drm] VBT doesn't support DRRS
[ 11.922147] [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2
[ 11.936510] fbcon: inteldrmfb (fb0) is primary device
[ 11.982666] Bluetooth: Core ver 2.19
[ 11.982675] NET: Registered protocol family 31
[ 11.982675] Bluetooth: HCI device and connection manager initialized
[ 11.982679] Bluetooth: HCI socket layer initialized
[ 11.982680] Bluetooth: L2CAP socket layer initialized
[ 11.982683] Bluetooth: SCO socket layer initialized
[ 12.006298] usbcore: registered new interface driver rtsx_usb
[ 12.040642] ath: phy0: Set parameters for CUS198
[ 12.040642] ath: phy0: Set BT/WLAN RX diversity capability
[ 12.046590] ath: phy0: Enable LNA combining
[ 12.047749] ath: EEPROM regdomain: 0x60
[ 12.047750] ath: EEPROM indicates we should expect a direct regpair map
[ 12.047750] ath: Country alpha2 being used: 00
[ 12.047751] ath: Regpair used: 0x60
[ 12.049373] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 12.049594] ieee80211 phy0: Atheros AR9485 Rev:1 mem=0xffffc90005d00000, irq=18
[ 12.145834] usbcore: registered new interface driver btusb
[ 12.155846] MXM: GUID detected in BIOS
[ 12.155922] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140724/nsarguments-95)
[ 12.155973] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140724/nsarguments-95)
[ 12.156192] pci 0000:01:00.0: optimus capabilities: enabled, status dynamic power,
[ 12.156193] VGA switcheroo: detected Optimus DSM method \_SB_.PCI0.PEG0.PEGP handle
[ 12.598418] ath9k 0000:04:00.0 wlp4s0: renamed from wlan0
[ 12.620359] media: Linux media interface: v0.10
[ 12.626127] systemd-udevd[232]: renamed network interface wlan0 to wlp4s0
[ 12.699457] Linux video capture interface: v2.00
[ 12.843252] usb 3-10: USB disconnect, device number 9
[ 13.003038] Console: switching to colour frame buffer device 240x67
[ 13.006511] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 13.006513] i915 0000:00:02.0: registered panic notifier
[ 13.015741] intel_rapl: Found RAPL domain package
[ 13.015746] intel_rapl: Found RAPL domain core
[ 13.015748] intel_rapl: Found RAPL domain uncore
[ 13.015751] intel_rapl: Found RAPL domain dram
[ 13.016857] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS
[ 13.045017] ACPI: Video Device [PEGP] (multi-head: yes rom: yes post: no)
[ 1I have figured out how to solve part of the problem. It was completely Xorg related, as you can see from the Xorg.0.log. I removed nouveau and installed Nvidia proprietary driver, in this way X doesn't timeout anymore but now I still have a problem with the time it takes X to start up. As you can see from these lines:
[ 20.141] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 20.141] (II) Loader magic: 0x818d80
[ 20.141] (II) Module ABI versions:
[ 20.141] X.Org ANSI C Emulation: 0.4
[ 20.141] X.Org Video Driver: 18.0
[ 20.141] X.Org XInput driver : 21.0
[ 20.141] X.Org Server Extension : 8.0
[ 44.585] (EE) systemd-logind: failed to get session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[ 44.585] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 44.586] (--) PCI:*(0:0:2:0) 8086:0416:1043:11cd rev 6, Mem @ 0xf7400000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64
[ 44.586] (--) PCI: (0:1:0:0) 10de:0fe4:1043:11cd rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 44.586] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 44.586] (II) LoadModule: "glx"
There is quite a jump in the timestamps just where an error related with logind occurs. Is it normal or I have a problem? BTW, Xorg doesn't timeout anymore it seems.
Is there anyone who can help me? Maybe I have simply posted in the wrong section of the forum?
Last edited by Aliverix (2014-11-06 22:47:24) -
Ata driver timeout and Solaris 10 10/08
Good day,
My Solaris 10 10/08 installation is suffering from ata driver timeouts. The error messages are exactly the same as those documented in OpenSolaris Bug ID 6586621 (abort request,abort device,reset target,reset bus,early timeout in quick succession followed by "Vendor 'Gen-ATA ' error code: 0x3".
The underlying disks are QEMU disks in a XenServer HVM and the VM has two CPUs. Since the disks are actually files on an underlying RAID 10 array that is reported as healthy by the RAID controller, I would exclude hardware faults (other VMs run faultlessly).
The suggestion at http://justindthomas.wordpress.com/2008/12/22/xenserver-5-and-opensolaris-0811/ regarding the disabling of DMA use by the ata driver has not been effective.
Any pointer is welcome. I would also appreciate an evaluaton of the validity to my case of workaround 5 suggested at http://docs.sun.com/app/docs/doc/820-5245/fhknh?a=view (Solaris 10 10/08 release notes).
Many thanks for any help.
Cheers!From what I have seen these errors are generated from the dvd-rom (ide device) not coming online fully or failing during boot. Sometimes the errors go away with a simple reboot, but they might re-appear on the next reboot. The only sure way to resolve this issue is to disconnect the dvd drive.
I am trying to find a an alternative to physically disconnecting the dvdroms, looking for a way way to disable the dvd from being detected. -
Passing data from RT host to FPGA through DMA FIFO
Hello,
I am trying to write some data from an RT host to FPGA target using DMA FIFO then process this data and then read them back from the FPGA target to the RT host through another DMA FIFO. I am working on NI PXIe chassis 1062Q, with NI PXIe-8130 embedded RT controller and NI PXIe-7965R FPGA target.
The problem I am facing is that I want to send three different arrays, two of the same size and the third one with different size, and I need the smaller one to be sent to the FPGA first. I tried using flat sequece with two frames in the FPGA VI. In the first frame I read and write the first array in a while loop which is finite (i.e., finite number of iterations). The second frame contains the process of reading and writing the second two arrays (of the same size) in a while loop that can be finite or infinite (according to a control). The problem is that this didn't work. The 2 arrays are displayed on the front panel of the RT host VI and are working fine, however, the array that should have been read in the first sequence doesn't show up on the front panel of the RT host VI. This doesn't make sense because if it is not passed from the host to the fpga and vice versa then the second frame shouldn't have been executed. Note that I am wiring (-1) to the timeout to block the while loop iterations till the passing of each element is complete. Thus the first while loop has 3 iterations only. Could someone help me undersdtand why this happens and how to solve this problem?
I am attaching a picture of both the host and the fpga vi.
Thank you.
Solved!
Go to Solution.
Attachments:
RT host vi.png 102 KB
FPGA vi.png 28 KBNo need to initalize the arrays with values that you will immediately overwrite. Here's what I believe to be equivalent code:
The array outputs should be wired directly to the FPGA FIFO writes. Do not use local variables when you can wire directly.
If you know that you want to transfer the Temp Data Array first, why not make your code do that? Eliminate the sequence structure, and put the functions in the order in which you want them to execute. Use the FPGA reference and error wires to enforce that order. You might consider writing the Temp Data Array, reading it back, then writing the Real and Imag A arrays, to see if that gets you the results you expect. Run the code in simulation (in the project, right-click on the FPGA target and execute on the host with simulated IO) so that you can use execution highlighting and probes to see what is happening. Wire the error wires through and see if you get an error anywhere. Make sure you're not missing something simple like looking at the wrong starting array index. -
DMA FIFO number of elements to read mismatch in FPGA and RT
Hi all
I am using myRIO , LV14 to run my application.
Application: I have to continuously acquire data via FPGA and process in RT host once every 2000 samples are collected. I use DMA FIFO (size 8191) to acquire data, use timeout property at the FPGA to eliminate buffer overflow. I had followed cRIOdevguide to implement this part. A snippet of what I have implemented is attached. Whole code runs in SCTL at 50MHz.
Issue: Twice or thrice I encountered with this strange behaviour, that the FPGA FIFO is giving continous timeout and the RT is unable to read the FIFO. The number of elements to write propery in FPGA VI gives 0 showing that FIFO is full and no more can be written, but at the RT, elements remaining is giving 0, hence it is reading 0 (no) elements.
Workaround: I put a case where I will write to FIFO (as per the code) and if the number of elements to write is nonzero. It seems to work fine, as of now.
What confuses me is that my FPGA VI says that FIFO is full (FIFO number of elements to write = 0) and gives a timeout error, but RT VI says that number of elements remaining in FIFO is 0 and hence no data is read. Any idea why it is so? My FPGA and RT VIs continues to run, but with no data being acquired or read.
I saw this behaviour within minutes after running the code. Any idea as to why it is happening? I am trying to reproduce the behaviour and will update if i again encounter with it. Sorry, I cannot post my code here, but i guess the code snippets explain it to some extend.
Thanks
Arya
Edit: Even with the mentioned workaround, the problem persists, now that the FPGA does not write to FIFO at all. And the RT VI is not able to read any elements as it sees 0 elements in the FIFO. The FIFO continues to be in timeout state. So i guess the problem is with the RT side.
Solved!
Go to Solution.
Attachments:
cRIOdevguide_FIFOreadwrite.PNG 107 KB
FPGA_FIFO_write.PNG 41 KB
RT_FIFO_read.PNG 39 KBHi Nathan
Yes, I could have replaced it with an OR. Regarding my application, I want to acquire data in chunks of 2000 samples. If at all I receive a timeout error, I want to discard that chunk of 2k samples and start all over again. So my logic was like this, I acquire the data, if there is a timeout, the reset is triggered, and the system waits to comeback from reset, and it starts acquiring again. Btw, I tried removing the multiple FIFO reads in RT, but the error is still the same.
I have a small doubt as well, if I do not want to obtain stale data at alI, I would just check if timeout occurs, empty my FIFO and start acquiring data again (no reset button), isnt it? This was my original logic, but I saw that after a while, it stopped acquiring data and timeout led was on. I was thinking that FPGA and RT was simultaneously trying to acquire FIFO which might cause timeout. Somehow, I now feel that, as you have pointed out, my code is overly complicated. I will modify it and update the results. Thank you!
Arya -
Hi all,
My application involves grabbing images from a 3-taps, 16-bit camera using FlexRIO. The PXI controller I am using is Windows-based while the FlexRIO module that I have is a PXI-7954 + NI 1483 adapter. The size of the image I am grabbing is 2560 x 2160, U16 and the clock cycle is 100 MHz. I've been trying for over a week and up to today, I still am not able to get the image from the camera as I kept on getting the DMA Write Timeout error. Right now, the DMA size in the FPGA is set at 130k but whenever I tried to increase this further, I get a compilation error. I've tried to have the host program to grab 100k data points from the FPGA DMA at every milisecond but it seems that, I am capped at about 10-15ms. Perhaps, Windows has its own limitation...
Attached is the program that I am using, modified from the LabVIEW shipped example. Please advice, how do move forward from here? or, is it possible to further increase the DMA buffer size up 10x higher than the current limit?
Attachments:
1-Tap 10-Bit Camera with Frame Trigger.zip 1684 KBHi Shazlan
Apologies for taking so long to reply to you.
You are correct in saying that the latest driver is IMAQ 4.6.4 and this can be downloaded from our website if you have not done so already.
If you have already installed the IMAX 4.6.4 driver, has this managed to resolve your issue?
Also, have you tried to run the compilation again and obtained a report outlining the problems?
As a side note - I have been looking into the possibility of downloading some sort of driver for the Samos camera you are using from Andorra. While National Instruments have not created a driver for this device, Andorra do have a Software Development Kit (SDK) which they say works with LabVIEW. You may find it useful to have this so that you no longer have to write the driver yourself. This may then save resources on the FPGA.
Keep me updated on your progress and I will continue to look into this issue for you.
Regards
Marshall B
Applications Engineer
National Instruments UK & Ireland -
Kernel ata_piix DMA issues [solved]
this is the first time that such a message appeared (i think after a kernel update); something is wrong, cause there are about 15 such messages (different want values) each and every boot.
Feb 3 10:47:23 localhost attempt to access beyond end of device
Feb 3 10:47:23 localhost sdb: rw=0, want=40017915, limit=39062500
but thats not too bad, because it doesn't even add a second to the boot time, and the performance hasn't noticeably changed.
but then, upgrading to 2.6.20, I got this somewhat related message:
Feb 6 21:55:19 localhost scsi2 : ata_piix
Feb 6 21:55:19 localhost ata2.00: ATAPI, max UDMA/33
Feb 6 21:55:19 localhost ata2.01: ATAPI, max UDMA/33
Feb 6 21:55:19 localhost ata2.01: device is on DMA blacklist, disabling DMA
Feb 6 21:55:19 localhost ata2.00: qc timeout (cmd 0xef)
Feb 6 21:55:19 localhost ata2.00: failed to set xfermode (err_mask=0x4)
Feb 6 21:55:19 localhost ata2.00: limiting speed to UDMA/25
Feb 6 21:55:19 localhost ata2: failed to recover some devices, retrying in 5 secs
Feb 6 21:55:19 localhost ata2.01: device is on DMA blacklist, disabling DMA
Feb 6 21:55:19 localhost ata2.00: qc timeout (cmd 0xef)
Feb 6 21:55:19 localhost ata2.00: failed to set xfermode (err_mask=0x4)
Feb 6 21:55:19 localhost ata2.00: limiting speed to PIO0
Feb 6 21:55:19 localhost ata2: failed to recover some devices, retrying in 5 secs
Feb 6 21:55:19 localhost ata2.01: device is on DMA blacklist, disabling DMA
Feb 6 21:55:19 localhost ata2.00: qc timeout (cmd 0xef)
Feb 6 21:55:19 localhost ata2.00: failed to set xfermode (err_mask=0x4)
Feb 6 21:55:19 localhost ata2.00: disabled
Feb 6 21:55:19 localhost ata2: failed to recover some devices, retrying in 5 secs
Feb 6 21:55:19 localhost ata2.01: device is on DMA blacklist, disabling DMA
Feb 6 21:55:19 localhost ata2.01: failed to set xfermode (err_mask=0x40)
Feb 6 21:55:19 localhost ata2.01: limiting speed to PIO3
Feb 6 21:55:19 localhost ata2: failed to recover some devices, retrying in 5 secs
Feb 6 21:55:19 localhost ata2.01: device is on DMA blacklist, disabling DMA
Feb 6 21:55:19 localhost ata2.01: configured for PIO3
it clearly adds a lot of time to boot up, so if DMA really isn't supported for my intel 815 chipset, then what do I tell the kernel so that it doesn't waste time checking for DMA support?
These two signs seem to be related somehow, I think.
This is all from my second hdd, that doesn't get stressed much, so I wouldn't notice a slowdown if there were one.
Last edited by vogt (2008-02-20 03:07:22)Hi guys,
I havnt updated arch for a long while because last time i tried i had similar sorts of problems like above. This also happened with other distros i use with the new kernel.
If i put a cd in the cdrom drive, the problem went away and it would boot fine (it also worked if i used to ide-legacy option), but forgetting to put a cd in the drive meant a long wait so i wanted to find a fix for it.
So here i am and after a few months wait i thought there may be some changes and somebody may have fixed it. A simple solution i found was to simply add the word irqpoll to the append line in lilo, the slow boot goes away (well it did for me anyway) and problem fixed (or at least i dont have to worry about putting a cd in the drive before boot lol)
So now im back and using an up to date arch once again
Hope this helps
Kane -
DMA Error in Acquisition of Image from 1473R
Hiii...
I am using Frame Grabber NI PCIe-1473R to acquire images from a dragster camera over CamLink interface. I am using “1-Tap 10-Bit Camera with Frame Trigger” example code to acquire images. When I am running the above example code to acquire the images sometimes I am getting blurred images & most of the times I am getting timeout error for DMA FIFO. I have not made any changes in the code.
I am attaching the snapshots of errors & the camera file (for Awaiba Dragster 2x 2k_9_8_14). Please have a look on the scenario & suggest changes to acquire the images properly.
Attachments:
Error 1.png 85 KB
Error 2.png 623 KBPlease suggest me any document or tutorial for programming & configuration of other paramters of NI PCIe-1473R
-
Strange FPGA FIFO DMA behaviour
Hi all,
let me warn that 1) the post is long, and 2) I'm conscious that the problem I'm having has many workarounds (some I know, some I don't, some I think to know...). However, I woul like to understand exactly why it's happening, both to be able to find the most efficient solution and for personal "culture"...
So, I have a very simple VI running on an FPGA: at each cyle, it reads 8 ADC channels and build an an array of 9 elements (time+8 channels). I'll refer to one fo this 9-element array as a "data vector". Because I have to pass this data vector to the host VI, I set up a DMA FIFO in which I write the elements in order: time, ch0, ch2 ... ch7, time, ch0, ch2... etc (I can't directly wirte arrays in the DMA FIFO).
The host VI opens a reference to the fpga VI, invokes the start method and then enters a timed loop. On the first iteration it attempts to read 0 elements, obtaining the info on how many elements remain in the FIFO. Then using a feedback node it passes this information (N) to the next cycle, in which it reads K = 9*floor(N/9) elements (i.e., a integer number of data vectors) and reshape them in a Kx9 array. Finally, it formats the array and write it to a text file. Then the cycle repeats using the number of remaining element obtained from the previous iteration.
Now, the problem is that in the host VI the user has the ability ot set both the sampling frequency of the FPGA and the timed loop frequency. While this allows to find the preferred match of sampling frequency and wiriting (to file) interval, it may happen that the values are such that the FIFO saturates (i.e. the timed loop that empties the FIFO executes too slowly compared to the FPGA acquisition that fills it), and this has two main consequences. One is loss of data, that I don't care in this case as long as I notify the user that he is loosing data. The other one is that, even when i set the parameters back to a combination that allows the buffer not to be filled, I've lost trace of the "first element" of my data vector.
Now, I thought I had an explanation for that: when the buffer saturates, the "FIFO write" in the FPGA code will keep timing out untill the buffer is (at least partially) freed, that can happen in any moment of its cycle. Let's suppose that it found the FIFO full when it was trying to write ch3, and then resumed (because it found free space in the FIFO) when trying to write ch0: this would result in an incorrect sequence of data (time, ch0, ch1, ch2, ch0, ch1, ch2, ch3...) that would compromise any subsequent reading.
However, I'm observing another behaviour on another routine that makes me doubt about this explanation. (I told you the post was long!).
So, actually (I layed you before...) the FPGA code is writing two identical FIFO (FIFO2), not just one. This is because I want onether routine to run and visualize data independently from the one that writes them to file. This "visualization routine" opens a reference to the FPGA code, doesn't invoke the start methode and enters a loop that is almost identical to the one of the host VI, except that it sends the shaped array to some graph and similar instead of writing it to file. Now, because this routine is meant to be run as the user needs to watch the data, it often happens that it is started with big delay with respect to the FPGA code, resulting in FIFO2 being full. Thus, as expected, the reconstructed array is screwed up because the first element is no more what it is expected to be. However, stopping and restarting this rountine whithin an interval shorter than the time needed to fill the FIFO2 buffer (that is only possible if the sampling frequency is relatively slow, as stopping and restarting a routine takes at least a couple of seconds) makes it work. This doesn't match to what I would expect from my previous explanation, because stopping this rountine doesn't stop the FPGA code (i don't want to) and doesn't reset the FIFO2 buffer, so if there is a shift in the order of the elements from a previous timout, it should be maintaned...
Understanting why this is happening is interesting to me not only because it demontrates that I don't really understand how this FIFO thing works, but also because it would probably suggest me a simple solution to implement in both routines when I detect a write timeout from the FOGA code.
Does all this make sense to you?
Thanks
GiacomoI had some time today and I thought this was an interesting question so based on your description I went ahead and created a LabVIEW project template of how I would implement this application. I used one DMA FIFO in a producer loop on the host then use queues to send the data to two seperate consumer queues. Check out the atachment and let me know what you think.
FPGA VI
Host VI
-Hunter
Attachments:
FIFO Example Program.zip 127 KB
Maybe you are looking for
-
How do i get the menu bar back as it has disappeared somehow?
so i dont have an address bar or the buttons for going back and forward amongst pages, tried looking through the firefox options but couldn't find anything to bring it back. also have tried right clicking on the tab bar and that doesn't bring up anyt
-
Rebate accrual up to certain quantiy
Hi, We have an requirement where in rebate needs to be accrued only for certain quanity. For Eg:- Material A, Quantity is 1600 PCs, so rebate should accrue for all customers for specific materail only for 1600 pcs . Once system reaches 1600 pcs accr
-
Weblogic 7.0 deploy exception and Connection Pooling
Hi, I am using weblogic 7.0 When I delpoy my application in the server I get the following exception when deployed through webLogic builder deploy tool <Aug 24, 2004 1:26:32 PM IST> <Error> <Deployer> <149201> <The Slave Deployer failed to complete t
-
Hi guru, after installed BCM and IA and imported the certificates I can't connect IA. When I try to insert user and password the IA remains in Online (view-only) mode. I reinstalled everything that IA is approved, but the problem does not change I in
-
I use Blackboard, which is a platform for online teaching. I make updates/changes to the site, but I am unable to see the changes. This only happens with Firefox. How do I enable updates?