Graphic failure after full on memory consumption
After few hours of usage mostly after a high memory consumption, my mac starts doing these lines. Now i never had this issue before maverick upgrade. Can someone let me know what is going on. Rebooting fixes the issue for now.
MacBook Pro
15-inch, Mid 2010
Processor 2.53 GHz Intel Core i5
Memory 4 GB 1067 MHz DDR3
Graphics Intel HD Graphics 288 MB
Yup, same thing happening here. Just upgraded to 10.9 Mavericks.
2010 MBP 15-inch, i5 2.4GHz.
Kind of odd that all that all of us have the same model Mac. I hope this isn't related to another issue described over here: http://support.apple.com/kb/TS4088
I just spent money to get my logic board replaced because of that issue, as the diagnostic test said I "passed" even though I was still getting kernel panics occasionally. Now I upgrade to 10.9 and see video artifacts everywhere.
Random video/graphics glitches appear all over the place after a while. Sometimes it's minor, other times it makes the system unusable as you can't see anything. Usually goes away again if you restart, but it's obvious there's some kind of graphics issue with 10.9.
the 2010 15-inch MBP.
Similar Messages
-
Total, permanent graphics failure after xrandr --scale
I have a 13" late 2013 retina macbook pro and have just had this issue come up a second time. Given the rather large resolution of the laptop's screen, I prefer to scale the display to 1440x900 (using this script, which is essentially a wrapper for the scale command, modified for my 2560x1600 resolution). This usually works, but occasionally it results it a blank screen — the computer does not hang, as I can definitely input commands and turn it off via the power button, however, I can't see anything. The particularly awful part is that now whenever I boot after that, the screen goes permanently blank partway through loading the system. Nothing I do seems to affect it after this, and I still have no idea what changed in the first place. The only relevant entry from dmesg that I can find is as follows:
Conflicting fb usage inteldrmfb vs EFI VGA - removing generic driver
fb0: inteldrmfb frame buffer device
drm: registered panic notifier
This has happened to me twice for seemingly no reason. I'm particularly confused about its persistence, as xrandr --scale shouldn't set anything permanent, as far as I know. Once this happens, though, there appears to be no going back. The only way I fixed it last time was to reinstall Arch entirely. What can I do to fix this? I'd really like to keep using Arch on this computer but if it just stops working like this I simply can't do so.
EDIT: nomodeset allows me to boot to the virtual console but X does not start. Furthermore, I have an Intel card, so I really can't go without KMS in the long run.
Edit2: acpi_backlight=vendor plus kernel 3.12 (just released, IIRC) seems to have fixed the problem, at least temporarily... I will wait a bit to see if it happens again, however...
Last edited by DrKillPatient (2013-11-18 05:47:26)Do you have early KMS set up? Without it, I have seen all kinds of weirdness with Intel graphics.
-
Mac graphics failure after updating
Sometimes, if I'm playing a game with demanding graphics, my entire screen freezes except for the mouse. I tried SSH connecting to the computer, and it works fine. I can issue commands and open stuff without problems. The computer doesn't freeze, it's the graphics or something. Also, it only happens with games, not anything else like Final Cut Express or VirtualBox running a virus-ridden Windows XP.
I am pretty sure that this is an OS problem because it started happening once I updated to 10.5.8 from 10.5.0.
P.S. I don't really like the new discussions interface, although there are some good points to it-Deleted-
-
Environment:
MAC OSX 10.9.5
Firefox 32.0.3
Firefox keeps consuming lot of memory when you keep refreshing a tab after an interval.
I opened a single tab in my firefox and logged into my gmail account on that. At this stage the memory consumption was about 400MB. I refreshed the page after 10 seconds and it went to 580MB. Again i refreshed after 10 seconds and this time it was 690MB. Finally, when i refreshed 3rd time after 10 seconds, it was showing as 800MB.
Nothing was changed on the page (no new email, chat conversation, etc. nothing). Some how i feel that the firefox is not doing a good job at garbage collection. I tested this use case with lot of other applications and websites and got the similar result. Other browsers like Google chrome, safari, etc. they just work fine.
For one on of my application with three tabs open, the firefox literally crashed after the high memory consumption (around 2GB).
Can someone tell me if this is a known issue in firefox? and is firefox planning to fix it? Right now, is there any workaround or fix for this?Hi FredMcD,
Thanks for the reply. Unfortunately, i don't see any crash reports in about:crashes. I am trying to reproduce the issue which will make browser to crash but somehow its not happening anymore but the browser gets stuck at a point. Here is what i am doing:
- 3 tabs are open with same page of my application. The page has several panels which has charts and the javascript libraries used for this page are backbone.js, underscore.js, require.js, highcharts.js
- The page automatically reloads after every 30 seconds
- After the first loading of there three tabs, the memory consumption is 600MB. But after 5 minutes, the memory consumption goes to 1.6GB and stays at this rate.
- After sometime, the page wont load completely for any of the tabs. At this stage the browser becomes very slow and i have to either hard refresh the tabs or restart the browser. -
4S has wifi failing erratically over last few days. Have restored, also upgraded iOS from 6.1.3 to 7. 0.4 all with no improvement. Fails after on for a few minutes. As in one support doc, wifi slider dimmed. Support actions taken and NG. support doc says contact apple, but w/o ACare, no indication of cost outcome or amount of help for price. What is termed "rare" occurrence seems to have no successful outcomes I'Ve spotted.
This a hardware issue and any reasonable cost fix?
Note. When wifi fails, initially would be back after full shutdown restart. Now only very occasionally is back and only after hours of shutdown, and usually not at all. Can see some flicker and on & off wifi in strong signal area in few minutes it does work. Cellular reception OK.Hi Curmud,
Thanks for visiting Apple Support Communities.
It sounds like you have tried all of the troubleshooting steps recommended by the article iOS: Wi-Fi settings grayed out or dim.
Based on the information you have provided, it sounds like your iPhone needs to be serviced. The following link should help you get started with the process and has links with additional information on topics such as warranty and service pricing, battery replacement, and express replacement service.
http://support.apple.com/kb/index?page=servicefaq&geo=United_States&product=ipho ne
Best,
Jeremy -
Integration Builder Memory Consumption
Hello,
we are experiencing very high memory consumption of the Java IR designer (not the directory). Especially for loading normal graphical idoc to EDI mappings, but also for normal idoc to idoc mappings. examples (RAM on client side):
- open normal idoc to idoc mapping: + 40 MB
- idoc to edi orders d93a: + 70 MB
- a second idoc to edi orders d93a: + 70 MB
- Execute those mappings: no additional consumption
- third edi to edi orders d93a: + 100 MB
(alle mappings in same namespace)
After three more mappings RAM on client side goes on 580 MB and then Java heap error. Sometimes also OutOfMemory, then you have to terminate the application.
Obviously the mapping editor is not quite will optimized for RAM usage. It seems to not cache the in/out message structures. Or it loads for every mapping very much dedicated functionality.
So we cannot really call that fun. Working is very slow.
Do you have similar experiences ? Are there workarounds ? I know the JNLP mem setting parameters, but the problem is the high load of each mapping, not only the overall maximum memory.
And we are using only graphical mappings, no XSLT !
We are on XI 3.0 SP 21
CSYHii
Apart from raising tablespace..
Note 425207 - SAP memory management, current parameter ranges
you have configure operation modes to change work processes dynamically using rz03,rz04.
Please see the below link
http://help.sap.com/saphelp_nw04s/helpdata/en/c4/3a7f53505211d189550000e829fbbd/frameset.htm
You can Contact your Basis administrator for necessary action -
J2EE Engine memory consumption (Usage)
Dear experts,
We have J2EE Engine (a Jawa stack). When I run routine monitoring via the browser and read the memory consumption I am meet with a chart that show a sawtooth like graph. Every hour from 19:00 to 02:00 the memory consumption will rise with approx. 200 MB after 7 hours all of a sudden the memory consumption drops down to normal idel levvel and start over again. I can inform that at the time there are no user on the system.
My question is what are the J2EE doing? since there is no user activity.Are the J2EE engine running some system applications? is it filling up the log files and then empty(storing) them.
I hope some of the experts can answer.
I just want to undertand what's going on, on the system. If there is some documentation/white paper on how to interpret/read the J2EE monitor I will great full if you drop the information or link here.
MikeHi Mike
To understand what exactly is being executed in Java engine, I'd suggest you perform Thread dump analysis as per:
http://help.sap.com/saphelp_smehp1/helpdata/en/10/3ca29d9ace4b68ac324d217ba7833f/frameset.htm
Generally 4-5 thread dumps are triggered at the interval of 20-25 seconds for better analysis.
Here's some useful SAP notes related to thread dump analysis:
710154 - How to create a thread dump for the J2EE Engine 6.40/7.0
1020246 - Thread Dump Viewer for SAP Java Engine
742395 - Analyzing High CPU usage by the J2EE Engine
Kind regards,
Ved -
hi,
after full update and reboot i got to emergency mode.
journalctl -xb
-- Logs begin at Mon 2014-03-03 11:19:31 IST, end at Sun 2014-06-08 01:13:42 IDT. --
Jun 08 01:12:02 up systemd-journal[135]: Runtime journal is using 8.0M (max allowed 100.9M, trying to leave 151.3M free of 1001.1M available → current limit 100.9M).
Jun 08 01:12:02 up systemd-journal[135]: Runtime journal is using 8.0M (max allowed 100.9M, trying to leave 151.3M free of 1001.1M available → current limit 100.9M).
Jun 08 01:12:02 up kernel: Initializing cgroup subsys cpuset
Jun 08 01:12:02 up kernel: Initializing cgroup subsys cpu
Jun 08 01:12:02 up kernel: Initializing cgroup subsys cpuacct
Jun 08 01:12:02 up kernel: Linux version 3.14.5-1-ARCH (nobody@var-lib-archbuild-testing-i686-tobias) (gcc version 4.9.0 20140521 (prerelease) (GCC) ) #1 SMP PREEMPT Sun Jun 1 07:38:50 CEST 2014
Jun 08 01:12:02 up kernel: e820: BIOS-provided physical RAM map:
Jun 08 01:12:02 up kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Jun 08 01:12:02 up kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Jun 08 01:12:02 up kernel: BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
Jun 08 01:12:02 up kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007fedffff] usable
Jun 08 01:12:02 up kernel: BIOS-e820: [mem 0x000000007fee0000-0x000000007fee2fff] ACPI NVS
Jun 08 01:12:02 up kernel: BIOS-e820: [mem 0x000000007fee3000-0x000000007feeffff] ACPI data
Jun 08 01:12:02 up kernel: BIOS-e820: [mem 0x000000007fef0000-0x000000007fefffff] reserved
Jun 08 01:12:02 up kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f3ffffff] reserved
Jun 08 01:12:02 up kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000ffffffff] reserved
Jun 08 01:12:02 up kernel: Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
Jun 08 01:12:02 up kernel: SMBIOS 2.4 present.
Jun 08 01:12:02 up kernel: DMI: System manufacturer System Product Name/M2N-E, BIOS ASUS M2N-E ACPI BIOS Revision 1401 04/01/2008
Jun 08 01:12:02 up kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jun 08 01:12:02 up kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Jun 08 01:12:02 up kernel: e820: last_pfn = 0x7fee0 max_arch_pfn = 0x100000
Jun 08 01:12:02 up kernel: MTRR default type: uncachable
Jun 08 01:12:02 up kernel: MTRR fixed ranges enabled:
Jun 08 01:12:02 up kernel: 00000-9FFFF write-back
Jun 08 01:12:02 up kernel: A0000-BFFFF uncachable
Jun 08 01:12:02 up kernel: C0000-C7FFF write-protect
Jun 08 01:12:02 up kernel: C8000-FFFFF uncachable
Jun 08 01:12:02 up kernel: MTRR variable ranges enabled:
Jun 08 01:12:02 up kernel: 0 base 0000000000 mask FF80000000 write-back
Jun 08 01:12:02 up kernel: 1 base 007FF00000 mask FFFFF00000 uncachable
Jun 08 01:12:02 up kernel: 2 disabled
Jun 08 01:12:02 up kernel: 3 disabled
Jun 08 01:12:02 up kernel: 4 disabled
Jun 08 01:12:02 up kernel: 5 disabled
Jun 08 01:12:02 up kernel: 6 disabled
Jun 08 01:12:02 up kernel: 7 disabled
Jun 08 01:12:02 up kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jun 08 01:12:02 up kernel: found SMP MP-table at [mem 0x000f5a10-0x000f5a1f] mapped at [c00f5a10]
Jun 08 01:12:02 up kernel: Scanning 1 areas for low memory corruption
Jun 08 01:12:02 up kernel: initial memory mapped: [mem 0x00000000-0x01bfffff]
Jun 08 01:12:02 up kernel: Base memory trampoline at [c009b000] 9b000 size 16384
Jun 08 01:12:02 up kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
Jun 08 01:12:02 up kernel: [mem 0x00000000-0x000fffff] page 4k
Jun 08 01:12:02 up kernel: init_memory_mapping: [mem 0x37000000-0x373fffff]
Jun 08 01:12:02 up kernel: [mem 0x37000000-0x373fffff] page 2M
Jun 08 01:12:02 up kernel: init_memory_mapping: [mem 0x30000000-0x36ffffff]
Jun 08 01:12:02 up kernel: [mem 0x30000000-0x36ffffff] page 2M
Jun 08 01:12:02 up kernel: init_memory_mapping: [mem 0x00100000-0x2fffffff]
Jun 08 01:12:02 up kernel: [mem 0x00100000-0x003fffff] page 4k
Jun 08 01:12:02 up kernel: [mem 0x00400000-0x2fffffff] page 2M
Jun 08 01:12:02 up kernel: init_memory_mapping: [mem 0x37400000-0x377fdfff]
Jun 08 01:12:02 up kernel: [mem 0x37400000-0x377fdfff] page 4k
Jun 08 01:12:02 up kernel: BRK [0x01798000, 0x01798fff] PGTABLE
Jun 08 01:12:02 up kernel: RAMDISK: [mem 0x7fbaf000-0x7fedefff]
Jun 08 01:12:02 up kernel: Allocated new RAMDISK: [mem 0x374ce000-0x377fd275]
Jun 08 01:12:02 up kernel: Move RAMDISK from [mem 0x7fbaf000-0x7fede275] to [mem 0x374ce000-0x377fd275]
Jun 08 01:12:02 up kernel: ACPI: RSDP 000f77a0 000024 (v02 Nvidia)
Jun 08 01:12:02 up kernel: ACPI: XSDT 7fee3100 00004C (v01 Nvidia ASUSACPI 42302E31 AWRD 00000000)
Jun 08 01:12:02 up kernel: ACPI: FACP 7feeac80 0000F4 (v03 Nvidia ASUSACPI 42302E31 AWRD 00000000)
Jun 08 01:12:02 up kernel: ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Pm1aEventBlock: 32/8 (20131218/tbfadt-603)
Jun 08 01:12:02 up kernel: ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Pm1aControlBlock: 16/8 (20131218/tbfadt-603)
Jun 08 01:12:02 up kernel: ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/PmTimerBlock: 32/8 (20131218/tbfadt-603)
Jun 08 01:12:02 up kernel: ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block: 64/8 (20131218/tbfadt-603)
Jun 08 01:12:02 up kernel: ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe1Block: 128/8 (20131218/tbfadt-603)
Jun 08 01:12:02 up kernel: ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aEventBlock: 8, using default 32 (20131218/tbfadt-684)
Jun 08 01:12:02 up kernel: ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aControlBlock: 8, using default 16 (20131218/tbfadt-684)
Jun 08 01:12:02 up kernel: ACPI BIOS Warning (bug): Invalid length for FADT/PmTimerBlock: 8, using default 32 (20131218/tbfadt-684)
Jun 08 01:12:02 up kernel: ACPI: DSDT 7fee3280 007985 (v01 NVIDIA AWRDACPI 00001000 MSFT 03000000)
Jun 08 01:12:02 up kernel: ACPI: FACS 7fee0000 000040
Jun 08 01:12:02 up kernel: ACPI: SSDT 7feeaec0 0001C4 (v01 PTLTD POWERNOW 00000001 LTP 00000001)
Jun 08 01:12:02 up kernel: ACPI: HPET 7feeb100 000038 (v01 Nvidia ASUSACPI 42302E31 AWRD 00000098)
Jun 08 01:12:02 up kernel: ACPI: MCFG 7feeb180 00003C (v01 Nvidia ASUSACPI 42302E31 AWRD 00000000)
Jun 08 01:12:02 up kernel: ACPI: APIC 7feeadc0 000098 (v01 Nvidia ASUSACPI 42302E31 AWRD 00000000)
Jun 08 01:12:02 up kernel: ACPI: Local APIC address 0xfee00000
Jun 08 01:12:02 up kernel: 1158MB HIGHMEM available.
Jun 08 01:12:02 up kernel: 887MB LOWMEM available.
Jun 08 01:12:02 up kernel: mapped low ram: 0 - 377fe000
Jun 08 01:12:02 up kernel: low ram: 0 - 377fe000
Jun 08 01:12:02 up kernel: BRK [0x01799000, 0x01799fff] PGTABLE
Jun 08 01:12:02 up kernel: Zone ranges:
Jun 08 01:12:02 up kernel: DMA [mem 0x00001000-0x00ffffff]
Jun 08 01:12:02 up kernel: Normal [mem 0x01000000-0x377fdfff]
Jun 08 01:12:02 up kernel: HighMem [mem 0x377fe000-0x7fedffff]
Jun 08 01:12:02 up kernel: Movable zone start for each node
Jun 08 01:12:02 up kernel: Early memory node ranges
Jun 08 01:12:02 up kernel: node 0: [mem 0x00001000-0x0009efff]
Jun 08 01:12:02 up kernel: node 0: [mem 0x00100000-0x7fedffff]
Jun 08 01:12:02 up kernel: On node 0 totalpages: 523902
Jun 08 01:12:02 up kernel: free_area_init_node: node 0, pgdat c15fc640, node_mem_map f64ce020
Jun 08 01:12:02 up kernel: DMA zone: 32 pages used for memmap
Jun 08 01:12:02 up kernel: DMA zone: 0 pages reserved
Jun 08 01:12:02 up kernel: DMA zone: 3998 pages, LIFO batch:0
Jun 08 01:12:02 up kernel: Normal zone: 1744 pages used for memmap
Jun 08 01:12:02 up kernel: Normal zone: 223230 pages, LIFO batch:31
Jun 08 01:12:02 up kernel: HighMem zone: 2318 pages used for memmap
Jun 08 01:12:02 up kernel: HighMem zone: 296674 pages, LIFO batch:31
Jun 08 01:12:02 up kernel: Using APIC driver default
Jun 08 01:12:02 up kernel: Detected use of extended apic ids on hypertransport bus
Jun 08 01:12:02 up kernel: ACPI: PM-Timer IO Port: 0x1008
Jun 08 01:12:02 up kernel: ACPI: Local APIC address 0xfee00000
Jun 08 01:12:02 up kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jun 08 01:12:02 up kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jun 08 01:12:02 up kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled)
Jun 08 01:12:02 up kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
Jun 08 01:12:02 up kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jun 08 01:12:02 up kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jun 08 01:12:02 up kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jun 08 01:12:02 up kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jun 08 01:12:02 up kernel: ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
Jun 08 01:12:02 up kernel: IOAPIC[0]: apic_id 4, version 17, address 0xfec00000, GSI 0-23
Jun 08 01:12:02 up kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jun 08 01:12:02 up kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jun 08 01:12:02 up kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
Jun 08 01:12:02 up kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
Jun 08 01:12:02 up kernel: ACPI: IRQ0 used by override.
Jun 08 01:12:02 up kernel: ACPI: IRQ2 used by override.
Jun 08 01:12:02 up kernel: ACPI: IRQ9 used by override.
Jun 08 01:12:02 up kernel: ACPI: IRQ14 used by override.
Jun 08 01:12:02 up kernel: ACPI: IRQ15 used by override.
Jun 08 01:12:02 up kernel: Using ACPI (MADT) for SMP configuration information
Jun 08 01:12:02 up kernel: ACPI: HPET id: 0x10de8201 base: 0xfefff000
Jun 08 01:12:02 up kernel: smpboot: Allowing 4 CPUs, 2 hotplug CPUs
Jun 08 01:12:02 up kernel: nr_irqs_gsi: 40
Jun 08 01:12:02 up kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jun 08 01:12:02 up kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000effff]
Jun 08 01:12:02 up kernel: PM: Registered nosave memory: [mem 0x000f0000-0x000fffff]
Jun 08 01:12:02 up kernel: e820: [mem 0x7ff00000-0xefffffff] available for PCI devices
Jun 08 01:12:02 up kernel: Booting paravirtualized kernel on bare hardware
Jun 08 01:12:02 up kernel: setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:4 nr_node_ids:1
Jun 08 01:12:02 up kernel: PERCPU: Embedded 14 pages/cpu @f648a000 s33792 r0 d23552 u57344
Jun 08 01:12:02 up kernel: pcpu-alloc: s33792 r0 d23552 u57344 alloc=14*4096
Jun 08 01:12:02 up kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
Jun 08 01:12:02 up kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 522126
Jun 08 01:12:02 up kernel: Kernel command line: root=/dev/sda5 ro initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux
Jun 08 01:12:02 up kernel: PID hash table entries: 4096 (order: 2, 16384 bytes)
Jun 08 01:12:02 up kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Jun 08 01:12:02 up kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Jun 08 01:12:02 up kernel: Initializing CPU#0
Jun 08 01:12:02 up kernel: allocated 4191992 bytes of page_cgroup
Jun 08 01:12:02 up kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jun 08 01:12:02 up kernel: Initializing HighMem for node 0 (000377fe:0007fee0)
Jun 08 01:12:02 up kernel: Initializing Movable for node 0 (00000000:00000000)
Jun 08 01:12:02 up kernel: Memory: 2062936K/2095608K available (4445K kernel code, 470K rwdata, 1280K rodata, 568K init, 956K bss, 32672K reserved, 1186696K highmem)
Jun 08 01:12:02 up kernel: virtual kernel memory layout:
fixmap : 0xfff15000 - 0xfffff000 ( 936 kB)
pkmap : 0xff800000 - 0xffc00000 (4096 kB)
vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB)
lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB)
.init : 0xc160f000 - 0xc169d000 ( 568 kB)
.data : 0xc1457b12 - 0xc160ebc0 (1756 kB)
.text : 0xc1000000 - 0xc1457b12 (4446 kB)
Jun 08 01:12:02 up kernel: Checking if this processor honours the WP bit even in supervisor mode...Ok.
Jun 08 01:12:02 up kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Jun 08 01:12:02 up kernel: Preemptible hierarchical RCU implementation.
Jun 08 01:12:02 up kernel: RCU dyntick-idle grace-period acceleration is enabled.
Jun 08 01:12:02 up kernel: Dump stacks of tasks blocking RCU-preempt GP.
Jun 08 01:12:02 up kernel: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
Jun 08 01:12:02 up kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
Jun 08 01:12:02 up kernel: NR_IRQS:2304 nr_irqs:712 16
Jun 08 01:12:02 up kernel: CPU 0 irqstacks, hard=f5808000 soft=f580a000
Jun 08 01:12:02 up kernel: spurious 8259A interrupt: IRQ7.
Jun 08 01:12:02 up kernel: Console: colour VGA+ 80x25
Jun 08 01:12:02 up kernel: console [tty0] enabled
Jun 08 01:12:02 up kernel: hpet clockevent registered
Jun 08 01:12:02 up kernel: tsc: Fast TSC calibration using PIT
Jun 08 01:12:02 up kernel: tsc: Detected 2009.051 MHz processor
Jun 08 01:12:02 up kernel: tsc: Marking TSC unstable due to TSCs unsynchronized
Jun 08 01:12:02 up kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 4019.52 BogoMIPS (lpj=6696836)
Jun 08 01:12:02 up kernel: pid_max: default: 32768 minimum: 301
Jun 08 01:12:02 up kernel: ACPI: Core revision 20131218
Jun 08 01:12:02 up kernel: ACPI: All ACPI Tables successfully acquired
Jun 08 01:12:02 up kernel: Security Framework initialized
Jun 08 01:12:02 up kernel: Yama: becoming mindful.
Jun 08 01:12:02 up kernel: Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
Jun 08 01:12:02 up kernel: Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
Jun 08 01:12:02 up kernel: Initializing cgroup subsys memory
Jun 08 01:12:02 up kernel: Initializing cgroup subsys devices
Jun 08 01:12:02 up kernel: Initializing cgroup subsys freezer
Jun 08 01:12:02 up kernel: Initializing cgroup subsys net_cls
Jun 08 01:12:02 up kernel: Initializing cgroup subsys blkio
Jun 08 01:12:02 up kernel: CPU: Physical Processor ID: 0
Jun 08 01:12:02 up kernel: CPU: Processor Core ID: 0
Jun 08 01:12:02 up kernel: mce: CPU supports 5 MCE banks
Jun 08 01:12:02 up kernel: LVT offset 0 assigned for vector 0xf9
Jun 08 01:12:02 up kernel: process: using AMD E400 aware idle routine
Jun 08 01:12:02 up kernel: Last level iTLB entries: 4KB 512, 2MB 8, 4MB 4
Last level dTLB entries: 4KB 512, 2MB 8, 4MB 4, 1GB 0
tlb_flushall_shift: 6
Jun 08 01:12:02 up kernel: Freeing SMP alternatives memory: 16K (c169d000 - c16a1000)
Jun 08 01:12:02 up kernel: ftrace: allocating 18915 entries in 37 pages
Jun 08 01:12:02 up kernel: Enabling APIC mode: Flat. Using 1 I/O APICs
Jun 08 01:12:02 up kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jun 08 01:12:02 up kernel: smpboot: CPU0: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ (fam: 0f, model: 4b, stepping: 02)
Jun 08 01:12:02 up kernel: Performance Events: AMD PMU driver.
Jun 08 01:12:02 up kernel: ... version: 0
Jun 08 01:12:02 up kernel: ... bit width: 48
Jun 08 01:12:02 up kernel: ... generic registers: 4
Jun 08 01:12:02 up kernel: ... value mask: 0000ffffffffffff
Jun 08 01:12:02 up kernel: ... max period: 00007fffffffffff
Jun 08 01:12:02 up kernel: ... fixed-purpose events: 0
Jun 08 01:12:02 up kernel: ... event mask: 000000000000000f
Jun 08 01:12:02 up kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jun 08 01:12:02 up kernel: CPU 1 irqstacks, hard=f58d8000 soft=f58da000
Jun 08 01:12:02 up kernel: x86: Booting SMP configuration:
Jun 08 01:12:02 up kernel: .... node #0, CPUs: #1
Jun 08 01:12:02 up kernel: Initializing CPU#1
Jun 08 01:12:02 up kernel: x86: Booted up 1 node, 2 CPUs
Jun 08 01:12:02 up kernel: smpboot: Total of 2 processors activated (8039.48 BogoMIPS)
Jun 08 01:12:02 up kernel: devtmpfs: initialized
Jun 08 01:12:02 up kernel: PM: Registering ACPI NVS region [mem 0x7fee0000-0x7fee2fff] (12288 bytes)
Jun 08 01:12:02 up kernel: pinctrl core: initialized pinctrl subsystem
Jun 08 01:12:02 up kernel: RTC time: 1:11:55, date: 06/08/14
Jun 08 01:12:02 up kernel: NET: Registered protocol family 16
Jun 08 01:12:02 up kernel: cpuidle: using governor ladder
Jun 08 01:12:02 up kernel: cpuidle: using governor menu
Jun 08 01:12:02 up kernel: node 0 link 0: io port [a000, ffff]
Jun 08 01:12:02 up kernel: TOM: 0000000080000000 aka 2048M
Jun 08 01:12:02 up kernel: node 0 link 0: mmio [a0000, bffff]
Jun 08 01:12:02 up kernel: node 0 link 0: mmio [80000000, efffffff]
Jun 08 01:12:02 up kernel: node 0 link 0: mmio [f4000000, fe02ffff]
Jun 08 01:12:02 up kernel: node 0 link 0: mmio [f0000000, f02fffff]
Jun 08 01:12:02 up kernel: bus: [bus 00-02] on node 0 link 0
Jun 08 01:12:02 up kernel: bus: 00 [io 0x0000-0xffff]
Jun 08 01:12:02 up kernel: bus: 00 [mem 0x000a0000-0x000bffff]
Jun 08 01:12:02 up kernel: bus: 00 [mem 0x80000000-0xf3ffffff]
Jun 08 01:12:02 up kernel: bus: 00 [mem 0xf4000000-0xffffffff]
Jun 08 01:12:02 up kernel: ACPI: bus type PCI registered
Jun 08 01:12:02 up kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jun 08 01:12:02 up kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf0000000-0xf3ffffff] (base 0xf0000000)
Jun 08 01:12:02 up kernel: PCI: MMCONFIG at [mem 0xf0000000-0xf3ffffff] reserved in E820
Jun 08 01:12:02 up kernel: PCI: Using MMCONFIG for extended config space
Jun 08 01:12:02 up kernel: PCI: Using configuration type 1 for base access
Jun 08 01:12:02 up kernel: bio: create slab <bio-0> at 0
Jun 08 01:12:02 up kernel: ACPI: Added _OSI(Module Device)
Jun 08 01:12:02 up kernel: ACPI: Added _OSI(Processor Device)
Jun 08 01:12:02 up kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Jun 08 01:12:02 up kernel: ACPI: Added _OSI(Processor Aggregator Device)
Jun 08 01:12:02 up kernel: ACPI: Interpreter enabled
Jun 08 01:12:02 up kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131218/hwxface-580)
Jun 08 01:12:02 up kernel: ACPI: (supports S0 S1 S3 S4 S5)
Jun 08 01:12:02 up kernel: ACPI: Using IOAPIC for interrupt routing
Jun 08 01:12:02 up kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jun 08 01:12:02 up kernel: ACPI: No dock devices found.
Jun 08 01:12:02 up kernel: ACPI: \_PR_.C002: failed to get CPU APIC ID.
Jun 08 01:12:02 up kernel: ACPI: \_PR_.C003: failed to get CPU APIC ID.
Jun 08 01:12:02 up kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
Jun 08 01:12:02 up kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jun 08 01:12:02 up kernel: acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jun 08 01:12:02 up kernel: acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
Jun 08 01:12:02 up kernel: PCI host bridge to bus 0000:00
Jun 08 01:12:02 up kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
Jun 08 01:12:02 up kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
Jun 08 01:12:02 up kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
Jun 08 01:12:02 up kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jun 08 01:12:02 up kernel: pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000dffff]
Jun 08 01:12:02 up kernel: pci_bus 0000:00: root bus resource [mem 0x7ff00000-0xfebfffff]
Jun 08 01:12:02 up kernel: pci 0000:00:00.0: [10de:0369] type 00 class 0x050000
Jun 08 01:12:02 up kernel: pci 0000:00:01.0: [10de:0360] type 00 class 0x060100
Jun 08 01:12:02 up kernel: pci 0000:00:01.1: [10de:0368] type 00 class 0x0c0500
Jun 08 01:12:02 up kernel: pci 0000:00:01.1: reg 0x10: [io 0xfc00-0xfc3f]
Jun 08 01:12:02 up kernel: pci 0000:00:01.1: reg 0x20: [io 0x1c00-0x1c3f]
Jun 08 01:12:02 up kernel: pci 0000:00:01.1: reg 0x24: [io 0x1c40-0x1c7f]
Jun 08 01:12:02 up kernel: pci 0000:00:01.1: PME# supported from D3hot D3cold
Jun 08 01:12:02 up kernel: pci 0000:00:02.0: [10de:036c] type 00 class 0x0c0310
Jun 08 01:12:02 up kernel: pci 0000:00:02.0: reg 0x10: [mem 0xfe02f000-0xfe02ffff]
Jun 08 01:12:02 up kernel: pci 0000:00:02.0: supports D1 D2
Jun 08 01:12:02 up kernel: pci 0000:00:02.0: PME# supported from D0 D1 D2 D3hot D3cold
Jun 08 01:12:02 up kernel: pci 0000:00:02.0: System wakeup disabled by ACPI
Jun 08 01:12:02 up kernel: pci 0000:00:02.1: [10de:036d] type 00 class 0x0c0320
Jun 08 01:12:02 up kernel: pci 0000:00:02.1: reg 0x10: [mem 0xfe02e000-0xfe02e0ff]
Jun 08 01:12:02 up kernel: pci 0000:00:02.1: supports D1 D2
Jun 08 01:12:02 up kernel: pci 0000:00:02.1: PME# supported from D0 D1 D2 D3hot D3cold
Jun 08 01:12:02 up kernel: pci 0000:00:02.1: System wakeup disabled by ACPI
Jun 08 01:12:02 up kernel: pci 0000:00:04.0: [10de:036e] type 00 class 0x01018a
Jun 08 01:12:02 up kernel: pci 0000:00:04.0: reg 0x20: [io 0xf000-0xf00f]
Jun 08 01:12:02 up kernel: pci 0000:00:05.0: [10de:037f] type 00 class 0x010185
Jun 08 01:12:02 up kernel: pci 0000:00:05.0: reg 0x10: [io 0x09f0-0x09f7]
Jun 08 01:12:02 up kernel: pci 0000:00:05.0: reg 0x14: [io 0x0bf0-0x0bf3]
Jun 08 01:12:02 up kernel: pci 0000:00:05.0: reg 0x18: [io 0x0970-0x0977]
Jun 08 01:12:02 up kernel: pci 0000:00:05.0: reg 0x1c: [io 0x0b70-0x0b73]
Jun 08 01:12:02 up kernel: pci 0000:00:05.0: reg 0x20: [io 0xdc00-0xdc0f]
Jun 08 01:12:02 up kernel: pci 0000:00:05.0: reg 0x24: [mem 0xfe02d000-0xfe02dfff]
Jun 08 01:12:02 up kernel: pci 0000:00:05.1: [10de:037f] type 00 class 0x010185
Jun 08 01:12:02 up kernel: pci 0000:00:05.1: reg 0x10: [io 0x09e0-0x09e7]
Jun 08 01:12:02 up kernel: pci 0000:00:05.1: reg 0x14: [io 0x0be0-0x0be3]
Jun 08 01:12:02 up kernel: pci 0000:00:05.1: reg 0x18: [io 0x0960-0x0967]
Jun 08 01:12:02 up kernel: pci 0000:00:05.1: reg 0x1c: [io 0x0b60-0x0b63]
Jun 08 01:12:02 up kernel: pci 0000:00:05.1: reg 0x20: [io 0xc800-0xc80f]
Jun 08 01:12:02 up kernel: pci 0000:00:05.1: reg 0x24: [mem 0xfe02c000-0xfe02cfff]
Jun 08 01:12:02 up kernel: pci 0000:00:05.2: [10de:037f] type 00 class 0x010185
Jun 08 01:12:02 up kernel: pci 0000:00:05.2: reg 0x10: [io 0xc400-0xc407]
Jun 08 01:12:02 up kernel: pci 0000:00:05.2: reg 0x14: [io 0xc000-0xc003]
Jun 08 01:12:02 up kernel: pci 0000:00:05.2: reg 0x18: [io 0xbc00-0xbc07]
Jun 08 01:12:02 up kernel: pci 0000:00:05.2: reg 0x1c: [io 0xb800-0xb803]
Jun 08 01:12:02 up kernel: pci 0000:00:05.2: reg 0x20: [io 0xb400-0xb40f]
Jun 08 01:12:02 up kernel: pci 0000:00:05.2: reg 0x24: [mem 0xfe02b000-0xfe02bfff]
Jun 08 01:12:02 up kernel: pci 0000:00:06.0: [10de:0370] type 01 class 0x060401
Jun 08 01:12:02 up kernel: pci 0000:00:06.0: System wakeup disabled by ACPI
Jun 08 01:12:02 up kernel: pci 0000:00:06.1: [10de:0371] type 00 class 0x040300
Jun 08 01:12:02 up kernel: pci 0000:00:06.1: reg 0x10: [mem 0xfe024000-0xfe027fff]
Jun 08 01:12:02 up kernel: pci 0000:00:06.1: PME# supported from D3hot D3cold
Jun 08 01:12:02 up kernel: pci 0000:00:06.1: System wakeup disabled by ACPI
Jun 08 01:12:02 up kernel: pci 0000:00:08.0: [10de:0373] type 00 class 0x068000
Jun 08 01:12:02 up kernel: pci 0000:00:08.0: reg 0x10: [mem 0xfe02a000-0xfe02afff]
Jun 08 01:12:02 up kernel: pci 0000:00:08.0: reg 0x14: [io 0xb000-0xb007]
Jun 08 01:12:02 up kernel: pci 0000:00:08.0: reg 0x18: [mem 0xfe029000-0xfe0290ff]
Jun 08 01:12:02 up kernel: pci 0000:00:08.0: reg 0x1c: [mem 0xfe028000-0xfe02800f]
Jun 08 01:12:02 up kernel: pci 0000:00:08.0: supports D1 D2
Jun 08 01:12:02 up kernel: pci 0000:00:08.0: PME# supported from D0 D1 D2 D3hot D3cold
Jun 08 01:12:02 up kernel: pci 0000:00:08.0: System wakeup disabled by ACPI
Jun 08 01:12:02 up kernel: pci 0000:00:0f.0: [10de:0377] type 01 class 0x060400
Jun 08 01:12:02 up kernel: pci 0000:00:0f.0: PME# supported from D0 D1 D2 D3hot D3cold
Jun 08 01:12:02 up kernel: pci 0000:00:0f.0: System wakeup disabled by ACPI
Jun 08 01:12:02 up kernel: pci 0000:00:18.0: [1022:1100] type 00 class 0x060000
Jun 08 01:12:02 up kernel: pci 0000:00:18.1: [1022:1101] type 00 class 0x060000
Jun 08 01:12:02 up kernel: pci 0000:00:18.2: [1022:1102] type 00 class 0x060000
Jun 08 01:12:02 up kernel: pci 0000:00:18.3: [1022:1103] type 00 class 0x060000
Jun 08 01:12:02 up kernel: pci 0000:00:06.0: PCI bridge to [bus 01] (subtractive decode)
Jun 08 01:12:02 up kernel: pci 0000:00:06.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
Jun 08 01:12:02 up kernel: pci 0000:00:06.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
Jun 08 01:12:02 up kernel: pci 0000:00:06.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
Jun 08 01:12:02 up kernel: pci 0000:00:06.0: bridge window [mem 0x000c0000-0x000dffff] (subtractive decode)
Jun 08 01:12:02 up kernel: pci 0000:00:06.0: bridge window [mem 0x7ff00000-0xfebfffff] (subtractive decode)
Jun 08 01:12:02 up kernel: pci 0000:02:00.0: [10de:0392] type 00 class 0x030000
Jun 08 01:12:02 up kernel: pci 0000:02:00.0: reg 0x10: [mem 0xfa000000-0xfaffffff]
Jun 08 01:12:02 up kernel: pci 0000:02:00.0: reg 0x14: [mem 0xe0000000-0xefffffff 64bit pref]
Jun 08 01:12:02 up kernel: pci 0000:02:00.0: reg 0x1c: [mem 0xfb000000-0xfbffffff 64bit]
Jun 08 01:12:02 up kernel: pci 0000:02:00.0: reg 0x24: [io 0xac00-0xac7f]
Jun 08 01:12:02 up kernel: pci 0000:02:00.0: reg 0x30: [mem 0xfcfe0000-0xfcffffff pref]
Jun 08 01:12:02 up kernel: pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
Jun 08 01:12:02 up kernel: pci 0000:00:0f.0: PCI bridge to [bus 02]
Jun 08 01:12:02 up kernel: pci 0000:00:0f.0: bridge window [io 0xa000-0xafff]
Jun 08 01:12:02 up kernel: pci 0000:00:0f.0: bridge window [mem 0xfa000000-0xfcffffff]
Jun 08 01:12:02 up kernel: pci 0000:00:0f.0: bridge window [mem 0xe0000000-0xefffffff 64bit pref]
Jun 08 01:12:02 up kernel: pci_bus 0000:00: on NUMA node 0
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LNK1] (IRQs 5 7 9 10 11 14 15) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LNK2] (IRQs 5 7 9 10 11 14 15) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LNK3] (IRQs 5 7 9 10 11 14 15) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LNK4] (IRQs 5 7 9 10 11 14 15) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LNK5] (IRQs 5 7 9 10 11 14 15) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LNK6] (IRQs 5 7 9 10 *11 14 15)
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LNK7] (IRQs 5 7 9 10 11 14 15) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LNK8] (IRQs 5 7 9 10 11 14 15) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LP2P] (IRQs 5 7 9 10 11 14 15) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LUBA] (IRQs 5 7 9 *10 11 14 15)
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LMAC] (IRQs 5 7 9 *10 11 14 15)
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LAZA] (IRQs 5 7 9 *10 11 14 15)
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LPMU] (IRQs 5 7 9 10 11 14 15) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LSMB] (IRQs *5 7 9 10 11 14 15)
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LUB2] (IRQs 5 7 9 10 *11 14 15)
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LIDE] (IRQs 5 7 9 10 11 14 15) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LSID] (IRQs *5 7 9 10 11 14 15)
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LFID] (IRQs 5 7 9 *10 11 14 15)
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [LSA2] (IRQs 5 7 9 10 *11 14 15)
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APC1] (IRQs 16) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APC2] (IRQs 17) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APC3] (IRQs 18) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APC4] (IRQs 19) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APC5] (IRQs 16) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APC6] (IRQs 16) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APC7] (IRQs 16) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APC8] (IRQs 16) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22 23) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22 23) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APMU] (IRQs 20 21 22 23) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [AAZA] (IRQs 20 21 22 23) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APCS] (IRQs 20 21 22 23) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22 23) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22 23) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22 23) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APSI] (IRQs 20 21 22 23) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APSJ] (IRQs 20 21 22 23) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [ASA2] (IRQs 20 21 22 23) *0, disabled.
Jun 08 01:12:02 up kernel: ACPI: Enabled 1 GPEs in block 20 to 5F
Jun 08 01:12:02 up kernel: vgaarb: device added: PCI:0000:02:00.0,decodes=io+mem,owns=io+mem,locks=none
Jun 08 01:12:02 up kernel: vgaarb: loaded
Jun 08 01:12:02 up kernel: vgaarb: bridge control possible 0000:02:00.0
Jun 08 01:12:02 up kernel: PCI: Using ACPI for IRQ routing
Jun 08 01:12:02 up kernel: PCI: pci_cache_line_size set to 64 bytes
Jun 08 01:12:02 up kernel: e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
Jun 08 01:12:02 up kernel: e820: reserve RAM buffer [mem 0x7fee0000-0x7fffffff]
Jun 08 01:12:02 up kernel: NetLabel: Initializing
Jun 08 01:12:02 up kernel: NetLabel: domain hash size = 128
Jun 08 01:12:02 up kernel: NetLabel: protocols = UNLABELED CIPSOv4
Jun 08 01:12:02 up kernel: NetLabel: unlabeled traffic allowed by default
Jun 08 01:12:02 up kernel: HPET: 3 timers in total, 0 timers will be used for per-cpu timer
Jun 08 01:12:02 up kernel: hpet0: at MMIO 0xfefff000, IRQs 2, 8, 31
Jun 08 01:12:02 up kernel: hpet0: 3 comparators, 32-bit 25.000000 MHz counter
Jun 08 01:12:02 up kernel: Switched to clocksource hpet
Jun 08 01:12:02 up kernel: pnp: PnP ACPI init
Jun 08 01:12:02 up kernel: ACPI: bus type PNP registered
Jun 08 01:12:02 up kernel: system 00:00: [io 0x1000-0x107f] has been reserved
Jun 08 01:12:02 up kernel: system 00:00: [io 0x1080-0x10ff] has been reserved
Jun 08 01:12:02 up kernel: system 00:00: [io 0x1400-0x147f] has been reserved
Jun 08 01:12:02 up kernel: system 00:00: [io 0x1480-0x14ff] has been reserved
Jun 08 01:12:02 up kernel: system 00:00: [io 0x1800-0x187f] has been reserved
Jun 08 01:12:02 up kernel: system 00:00: [io 0x1880-0x18ff] has been reserved
Jun 08 01:12:02 up kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
Jun 08 01:12:02 up kernel: system 00:01: [io 0x04d0-0x04d1] has been reserved
Jun 08 01:12:02 up kernel: system 00:01: [io 0x0800-0x087f] has been reserved
Jun 08 01:12:02 up kernel: system 00:01: [io 0x0290-0x0297] has been reserved
Jun 08 01:12:02 up kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
Jun 08 01:12:02 up kernel: pnp 00:02: [dma 4]
Jun 08 01:12:02 up kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0200 (active)
Jun 08 01:12:02 up kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
Jun 08 01:12:02 up kernel: pnp 00:04: Plug and Play ACPI device, IDs PNP0b00 (active)
Jun 08 01:12:02 up kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0800 (active)
Jun 08 01:12:02 up kernel: pnp 00:06: Plug and Play ACPI device, IDs PNP0c04 (active)
Jun 08 01:12:02 up kernel: pnp 00:07: [dma 2]
Jun 08 01:12:02 up kernel: pnp 00:07: Plug and Play ACPI device, IDs PNP0700 (active)
Jun 08 01:12:02 up kernel: pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jun 08 01:12:02 up kernel: pnp 00:09: Plug and Play ACPI device, IDs PNP0400 (active)
Jun 08 01:12:02 up kernel: system 00:0a: [mem 0xf0000000-0xf3ffffff] has been reserved
Jun 08 01:12:02 up kernel: system 00:0a: Plug and Play ACPI device, IDs PNP0c02 (active)
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0x000cde00-0x000cffff] has been reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0x000f0000-0x000f7fff] could not be reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0x000f8000-0x000fbfff] could not be reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0x000fc000-0x000fffff] could not be reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0xfefff000-0xfefff0ff] has been reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0x7fee0000-0x7fefffff] could not be reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0xffff0000-0xffffffff] has been reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0x00000000-0x0009ffff] could not be reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0x00100000-0x7fedffff] could not be reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0xfec00000-0xfec00fff] could not be reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0xfee00000-0xfeefffff] has been reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0xfefff000-0xfeffffff] could not be reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0xfff80000-0xfff80fff] has been reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0xfff90000-0xfffbffff] has been reserved
Jun 08 01:12:02 up kernel: system 00:0b: [mem 0xfffed000-0xfffeffff] has been reserved
Jun 08 01:12:02 up kernel: system 00:0b: Plug and Play ACPI device, IDs PNP0c01 (active)
Jun 08 01:12:02 up kernel: pnp: PnP ACPI: found 12 devices
Jun 08 01:12:02 up kernel: ACPI: bus type PNP unregistered
Jun 08 01:12:02 up kernel: pci 0000:00:06.0: PCI bridge to [bus 01]
Jun 08 01:12:02 up kernel: pci 0000:00:0f.0: PCI bridge to [bus 02]
Jun 08 01:12:02 up kernel: pci 0000:00:0f.0: bridge window [io 0xa000-0xafff]
Jun 08 01:12:02 up kernel: pci 0000:00:0f.0: bridge window [mem 0xfa000000-0xfcffffff]
Jun 08 01:12:02 up kernel: pci 0000:00:0f.0: bridge window [mem 0xe0000000-0xefffffff 64bit pref]
Jun 08 01:12:02 up kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
Jun 08 01:12:02 up kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
Jun 08 01:12:02 up kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
Jun 08 01:12:02 up kernel: pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000dffff]
Jun 08 01:12:02 up kernel: pci_bus 0000:00: resource 8 [mem 0x7ff00000-0xfebfffff]
Jun 08 01:12:02 up kernel: pci_bus 0000:01: resource 4 [io 0x0000-0x0cf7]
Jun 08 01:12:02 up kernel: pci_bus 0000:01: resource 5 [io 0x0d00-0xffff]
Jun 08 01:12:02 up kernel: pci_bus 0000:01: resource 6 [mem 0x000a0000-0x000bffff]
Jun 08 01:12:02 up kernel: pci_bus 0000:01: resource 7 [mem 0x000c0000-0x000dffff]
Jun 08 01:12:02 up kernel: pci_bus 0000:01: resource 8 [mem 0x7ff00000-0xfebfffff]
Jun 08 01:12:02 up kernel: pci_bus 0000:02: resource 0 [io 0xa000-0xafff]
Jun 08 01:12:02 up kernel: pci_bus 0000:02: resource 1 [mem 0xfa000000-0xfcffffff]
Jun 08 01:12:02 up kernel: pci_bus 0000:02: resource 2 [mem 0xe0000000-0xefffffff 64bit pref]
Jun 08 01:12:02 up kernel: NET: Registered protocol family 2
Jun 08 01:12:02 up kernel: TCP established hash table entries: 8192 (order: 3, 32768 bytes)
Jun 08 01:12:02 up kernel: TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
Jun 08 01:12:02 up kernel: TCP: Hash tables configured (established 8192 bind 8192)
Jun 08 01:12:02 up kernel: TCP: reno registered
Jun 08 01:12:02 up kernel: UDP hash table entries: 512 (order: 2, 16384 bytes)
Jun 08 01:12:02 up kernel: UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
Jun 08 01:12:02 up kernel: NET: Registered protocol family 1
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APCF] enabled at IRQ 23
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APCL] enabled at IRQ 22
Jun 08 01:12:02 up kernel: pci 0000:00:05.0: Enabling HT MSI Mapping
Jun 08 01:12:02 up kernel: pci 0000:00:05.1: Enabling HT MSI Mapping
Jun 08 01:12:02 up kernel: pci 0000:00:05.2: Enabling HT MSI Mapping
Jun 08 01:12:02 up kernel: pci 0000:00:06.0: Enabling HT MSI Mapping
Jun 08 01:12:02 up kernel: pci 0000:00:06.1: Enabling HT MSI Mapping
Jun 08 01:12:02 up kernel: pci 0000:00:08.0: Enabling HT MSI Mapping
Jun 08 01:12:02 up kernel: pci 0000:00:0f.0: Enabling HT MSI Mapping
Jun 08 01:12:02 up kernel: pci 0000:02:00.0: Boot video device
Jun 08 01:12:02 up kernel: PCI: CLS 32 bytes, default 64
Jun 08 01:12:02 up kernel: Unpacking initramfs...
Jun 08 01:12:02 up kernel: Freeing initrd memory: 3264K (f74ce000 - f77fe000)
Jun 08 01:12:02 up kernel: apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
Jun 08 01:12:02 up kernel: apm: disabled - APM is not SMP safe.
Jun 08 01:12:02 up kernel: Scanning for low memory corruption every 60 seconds
Jun 08 01:12:02 up kernel: futex hash table entries: 1024 (order: 4, 65536 bytes)
Jun 08 01:12:02 up kernel: bounce pool size: 64 pages
Jun 08 01:12:02 up kernel: HugeTLB registered 4 MB page size, pre-allocated 0 pages
Jun 08 01:12:02 up kernel: zbud: loaded
Jun 08 01:12:02 up kernel: VFS: Disk quotas dquot_6.5.2
Jun 08 01:12:02 up kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Jun 08 01:12:02 up kernel: msgmni has been set to 1717
Jun 08 01:12:02 up kernel: Key type big_key registered
Jun 08 01:12:02 up kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jun 08 01:12:02 up kernel: io scheduler noop registered
Jun 08 01:12:02 up kernel: io scheduler deadline registered
Jun 08 01:12:02 up kernel: io scheduler cfq registered (default)
Jun 08 01:12:02 up kernel: pcieport 0000:00:0f.0: irq 40 for MSI/MSI-X
Jun 08 01:12:02 up kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jun 08 01:12:02 up kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jun 08 01:12:02 up kernel: GHES: HEST is not enabled!
Jun 08 01:12:02 up kernel: isapnp: Scanning for PnP cards...
Jun 08 01:12:02 up kernel: isapnp: No Plug & Play device found
Jun 08 01:12:02 up kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
Jun 08 01:12:02 up kernel: 00:08: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jun 08 01:12:02 up kernel: rtc_cmos 00:04: RTC can wake from S4
Jun 08 01:12:02 up kernel: rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
Jun 08 01:12:02 up kernel: rtc_cmos 00:04: alarms up to one year, y3k, 242 bytes nvram, hpet irqs
Jun 08 01:12:02 up kernel: ledtrig-cpu: registered to indicate activity on CPUs
Jun 08 01:12:02 up kernel: TCP: cubic registered
Jun 08 01:12:02 up kernel: NET: Registered protocol family 10
Jun 08 01:12:02 up kernel: NET: Registered protocol family 17
Jun 08 01:12:02 up kernel: Using IPI No-Shortcut mode
Jun 08 01:12:02 up kernel: registered taskstats version 1
Jun 08 01:12:02 up kernel: Magic number: 2:319:154
Jun 08 01:12:02 up kernel: acpi device:21: hash matches
Jun 08 01:12:02 up kernel: rtc_cmos 00:04: setting system clock to 2014-06-08 01:11:56 UTC (1402189916)
Jun 08 01:12:02 up kernel: PM: Hibernation image not present or could not be loaded.
Jun 08 01:12:02 up kernel: Freeing unused kernel memory: 568K (c160f000 - c169d000)
Jun 08 01:12:02 up kernel: Write protecting the kernel text: 4448k
Jun 08 01:12:02 up kernel: Write protecting the kernel read-only data: 1284k
Jun 08 01:12:02 up kernel: random: systemd-tmpfile urandom read with 0 bits of entropy available
Jun 08 01:12:02 up systemd-udevd[47]: starting version 213
Jun 08 01:12:02 up kernel: i8042: PNP: No PS/2 controller found. Probing ports directly.
Jun 08 01:12:02 up kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Jun 08 01:12:02 up kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Jun 08 01:12:02 up kernel: Floppy drive(s): fd0 is 1.44M
Jun 08 01:12:02 up kernel: ACPI: bus type USB registered
Jun 08 01:12:02 up kernel: usbcore: registered new interface driver usbfs
Jun 08 01:12:02 up kernel: usbcore: registered new interface driver hub
Jun 08 01:12:02 up kernel: usbcore: registered new device driver usb
Jun 08 01:12:02 up kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jun 08 01:12:02 up kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jun 08 01:12:02 up kernel: ohci-pci: OHCI PCI platform driver
Jun 08 01:12:02 up kernel: ohci-pci 0000:00:02.0: OHCI PCI host controller
Jun 08 01:12:02 up kernel: ohci-pci 0000:00:02.0: new USB bus registered, assigned bus number 1
Jun 08 01:12:02 up kernel: ohci-pci 0000:00:02.0: irq 23, io mem 0xfe02f000
Jun 08 01:12:02 up kernel: SCSI subsystem initialized
Jun 08 01:12:02 up kernel: ehci-pci: EHCI PCI platform driver
Jun 08 01:12:02 up kernel: libata version 3.00 loaded.
Jun 08 01:12:02 up kernel: FDC 0 is a post-1991 82077
Jun 08 01:12:02 up kernel: hub 1-0:1.0: USB hub found
Jun 08 01:12:02 up kernel: hub 1-0:1.0: 10 ports detected
Jun 08 01:12:02 up kernel: ehci-pci 0000:00:02.1: EHCI Host Controller
Jun 08 01:12:02 up kernel: ehci-pci 0000:00:02.1: new USB bus registered, assigned bus number 2
Jun 08 01:12:02 up kernel: ehci-pci 0000:00:02.1: debug port 1
Jun 08 01:12:02 up kernel: ehci-pci 0000:00:02.1: cache line size of 32 is not supported
Jun 08 01:12:02 up kernel: ehci-pci 0000:00:02.1: irq 22, io mem 0xfe02e000
Jun 08 01:12:02 up kernel: ehci-pci 0000:00:02.1: USB 2.0 started, EHCI 1.00
Jun 08 01:12:02 up kernel: hub 2-0:1.0: USB hub found
Jun 08 01:12:02 up kernel: hub 2-0:1.0: 10 ports detected
Jun 08 01:12:02 up kernel: hub 1-0:1.0: USB hub found
Jun 08 01:12:02 up kernel: hub 1-0:1.0: 10 ports detected
Jun 08 01:12:02 up kernel: sata_nv 0000:00:05.0: version 3.5
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APSI] enabled at IRQ 21
Jun 08 01:12:02 up kernel: sata_nv 0000:00:05.0: Using SWNCQ mode
Jun 08 01:12:02 up kernel: scsi0 : sata_nv
Jun 08 01:12:02 up kernel: scsi1 : sata_nv
Jun 08 01:12:02 up kernel: ata1: SATA max UDMA/133 cmd 0x9f0 ctl 0xbf0 bmdma 0xdc00 irq 21
Jun 08 01:12:02 up kernel: ata2: SATA max UDMA/133 cmd 0x970 ctl 0xb70 bmdma 0xdc08 irq 21
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [APSJ] enabled at IRQ 20
Jun 08 01:12:02 up kernel: sata_nv 0000:00:05.1: Using SWNCQ mode
Jun 08 01:12:02 up kernel: scsi2 : sata_nv
Jun 08 01:12:02 up kernel: scsi3 : sata_nv
Jun 08 01:12:02 up kernel: ata3: SATA max UDMA/133 cmd 0x9e0 ctl 0xbe0 bmdma 0xc800 irq 20
Jun 08 01:12:02 up kernel: ata4: SATA max UDMA/133 cmd 0x960 ctl 0xb60 bmdma 0xc808 irq 20
Jun 08 01:12:02 up kernel: ACPI: PCI Interrupt Link [ASA2] enabled at IRQ 23
Jun 08 01:12:02 up kernel: sata_nv 0000:00:05.2: Using SWNCQ mode
Jun 08 01:12:02 up kernel: scsi4 : sata_nv
Jun 08 01:12:02 up kernel: scsi5 : sata_nv
Jun 08 01:12:02 up kernel: ata5: SATA max UDMA/133 cmd 0xc400 ctl 0xc000 bmdma 0xb400 irq 23
Jun 08 01:12:02 up kernel: ata6: SATA max UDMA/133 cmd 0xbc00 ctl 0xb800 bmdma 0xb408 irq 23
Jun 08 01:12:02 up kernel: pata_amd 0000:00:04.0: version 0.4.1
Jun 08 01:12:02 up kernel: scsi6 : pata_amd
Jun 08 01:12:02 up kernel: scsi7 : pata_amd
Jun 08 01:12:02 up kernel: ata7: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000 irq 14
Jun 08 01:12:02 up kernel: ata8: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xf008 irq 15
Jun 08 01:12:02 up kernel: ata3: SATA link down (SStatus 0 SControl 300)
Jun 08 01:12:02 up kernel: ata5: SATA link down (SStatus 0 SControl 300)
Jun 08 01:12:02 up kernel: usb 2-4: new high-speed USB device number 4 using ehci-pci
Jun 08 01:12:02 up kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jun 08 01:12:02 up kernel: ata1.00: ATA-8: WDC WD6400AAKS-00A7B0, 01.03B01, max UDMA/133
Jun 08 01:12:02 up kernel: ata1.00: 1250263728 sectors, multi 1: LBA48 NCQ (depth 31/32)
Jun 08 01:12:02 up kernel: hub 2-4:1.0: USB hub found
Jun 08 01:12:02 up kernel: hub 2-4:1.0: 4 ports detected
Jun 08 01:12:02 up kernel: ata1.00: configured for UDMA/133
Jun 08 01:12:02 up kernel: scsi 0:0:0:0: Direct-Access ATA WDC WD6400AAKS-0 01.0 PQ: 0 ANSI: 5
Jun 08 01:12:02 up kernel: ata2: SATA link down (SStatus 0 SControl 300)
Jun 08 01:12:02 up kernel: usb 1-2: new low-speed USB device number 2 using ohci-pci
Jun 08 01:12:02 up kernel: ata4: SATA link down (SStatus 0 SControl 300)
Jun 08 01:12:02 up kernel: hidraw: raw HID events driver (C) Jiri Kosina
Jun 08 01:12:02 up kernel: sd 0:0:0:0: [sda] 1250263728 512-byte logical blocks: (640 GB/596 GiB)
Jun 08 01:12:02 up kernel: sd 0:0:0:0: [sda] Write Protect is off
Jun 08 01:12:02 up kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Jun 08 01:12:02 up kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jun 08 01:12:02 up kernel: usbcore: registered new interface driver usbhid
Jun 08 01:12:02 up kernel: usbhid: USB HID core driver
Jun 08 01:12:02 up kernel: input: Microsoft Comfort Curve Keyboard 3000 as /devices/pci0000:00/0000:00:02.0/usb1/1-2/1-2:1.0/0003:045E:0780.0001/input/input2
Jun 08 01:12:02 up kernel: hid-generic 0003:045E:0780.0001: input,hidraw0: USB HID v1.11 Keyboard [Microsoft Comfort Curve Keyboard 3000] on usb-0000:00:02.0-2/input0
Jun 08 01:12:02 up kernel: input: Microsoft Comfort Curve Keyboard 3000 as /devices/pci0000:00/0000:00:02.0/usb1/1-2/1-2:1.1/0003:045E:0780.0002/input/input3
Jun 08 01:12:02 up kernel: hid-generic 0003:045E:0780.0002: input,hidraw1: USB HID v1.11 Device [Microsoft Comfort Curve Keyboard 3000] on usb-0000:00:02.0-2/input1
Jun 08 01:12:02 up kernel: sda: sda1 sda2 sda3 < sda5 sda6 sda7 > sda4
Jun 08 01:12:02 up kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Jun 08 01:12:02 up kernel: usb 1-3: new low-speed USB device number 3 using ohci-pci
Jun 08 01:12:02 up kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jun 08 01:12:02 up kernel: ata6.00: ATA-7: WDC WD2500KS-00MJB0, 02.01C03, max UDMA/133
Jun 08 01:12:02 up kernel: ata6.00: 488397168 sectors, multi 1: LBA48
Jun 08 01:12:02 up kernel: ata6.00: configured for UDMA/133
Jun 08 01:12:02 up kernel: scsi 5:0:0:0: Direct-Access ATA WDC WD2500KS-00M 02.0 PQ: 0 ANSI: 5
Jun 08 01:12:02 up kernel: sd 5:0:0:0: [sdb] 488397168 512-byte logical blocks: (250 GB/232 GiB)
Jun 08 01:12:02 up kernel: ata8: port disabled--ignoring
Jun 08 01:12:02 up kernel: sd 5:0:0:0: [sdb] Write Protect is off
Jun 08 01:12:02 up kernel: sd 5:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Jun 08 01:12:02 up kernel: sd 5:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jun 08 01:12:02 up kernel: sdb: sdb1 sdb4
Jun 08 01:12:02 up kernel: sd 5:0:0:0: [sdb] Attached SCSI disk
Jun 08 01:12:02 up kernel: input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:02.0/usb1/1-3/1-3:1.0/0003:046D:C025.0003/input/input4
Jun 08 01:12:02 up kernel: hid-generic 0003:046D:C025.0003: input,hidraw2: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:02.0-3/input0
Jun 08 01:12:02 up kernel: random: nonblocking pool is initialized
Jun 08 01:12:02 up kernel: EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
Jun 08 01:12:02 up systemd[1]: RTC configured in localtime, applying delta of 180 minutes to system time.
Jun 08 01:12:02 up systemd[1]: systemd 213 running in system mode. (+PAM -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ +SECCOMP -APPARMOR)
Jun 08 01:12:02 up systemd[1]: Detected architecture 'x86'.
Jun 08 01:12:02 up systemd[1]: Set hostname to <up>.
Jun 08 01:12:02 up systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
Jun 08 01:12:02 up systemd[1]: Started Forward Password Requests to Wall Directory Watch.
Jun 08 01:12:02 up systemd[1]: Starting Remote File Systems.
Jun 08 01:12:02 up systemd[1]: Reached target Remote File Systems.
Jun 08 01:12:02 up systemd[1]: Starting Encrypted Volumes.
Jun 08 01:12:02 up systemd[1]: Reached target Encrypted Volumes.
Jun 08 01:12:02 up systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
Jun 08 01:12:02 up systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
Jun 08 01:12:02 up systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
Jun 08 01:12:02 up systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
Jun 08 01:12:02 up systemd[1]: Starting Paths.
Jun 08 01:12:02 up systemd[1]: Reached target Paths.
Jun 08 01:12:02 up systemd[1]: Starting Swap.
Jun 08 01:12:02 up systemd[1]: Reached target Swap.
Jun 08 01:12:02 up systemd[1]: Expecting device dev-sda6.device...
Jun 08 01:12:02 up systemd[1]: Starting Root Slice.
Jun 08 01:12:02 up systemd[1]: Created slice Root Slice.
Jun 08 01:12:02 up systemd[1]: Starting User and Session Slice.
Jun 08 01:12:02 up systemd[1]: Created slice User and Session Slice.
Jun 08 01:12:02 up systemd[1]: Starting Delayed Shutdown Socket.
Jun 08 01:12:02 up systemd[1]: Listening on Delayed Shutdown Socket.
Jun 08 01:12:02 up systemd[1]: Starting Device-mapper event daemon FIFOs.
Jun 08 01:12:02 up systemd[1]: Listening on Device-mapper event daemon FIFOs.
Jun 08 01:12:02 up systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
Jun 08 01:12:02 up systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
Jun 08 01:12:02 up systemd[1]: Starting udev Kernel Socket.
Jun 08 01:12:02 up systemd[1]: Listening on udev Kernel Socket.
Jun 08 01:12:02 up systemd[1]: Starting udev Control Socket.
Jun 08 01:12:02 up systemd[1]: Listening on udev Control Socket.
Jun 08 01:12:02 up systemd[1]: Starting LVM2 metadata daemon socket.
Jun 08 01:12:02 up systemd[1]: Listening on LVM2 metadata daemon socket.
Jun 08 01:12:02 up systemd[1]: Starting Journal Socket.
Jun 08 01:12:02 up systemd[1]: Listening on Journal Socket.
Jun 08 01:12:02 up systemd[1]: Starting System Slice.
Jun 08 01:12:02 up systemd[1]: Created slice System Slice.
Jun 08 01:12:02 up systemd[1]: Starting File System Check on Root Device...
Jun 08 01:12:02 up systemd[1]: Starting system-systemd\x2dfsck.slice.
Jun 08 01:12:02 up systemd[1]: Created slice system-systemd\x2dfsck.slice.
Jun 08 01:12:02 up systemd[1]: Mounting Temporary Directory...
Jun 08 01:12:02 up systemd[1]: tmp.mount: Directory /tmp to mount over is not empty, mounting anyway.
Jun 08 01:12:02 up systemd[1]: Starting system-getty.slice.
Jun 08 01:12:02 up systemd[1]: Created slice system-getty.slice.
Jun 08 01:12:02 up systemd[1]: Starting Set Up Additional Binary Formats...
Jun 08 01:12:02 up systemd[1]: Starting udev Coldplug all Devices...
Jun 08 01:12:02 up systemd[1]: Mounting Huge Pages File System...
Jun 08 01:12:02 up systemd[1]: Mounting Debug File System...
Jun 08 01:12:02 up systemd[1]: Starting Load Kernel Modules...
Jun 08 01:12:02 up systemd[1]: Mounting POSIX Message Queue File System...
Jun 08 01:12:02 up systemd[1]: Starting Create list of required static device nodes for the current kernel...
Jun 08 01:12:02 up systemd[1]: Starting Setup Virtual Console...
Jun 08 01:12:02 up systemd[1]: Starting Apply Kernel Variables...
Jun 08 01:12:02 up systemd[1]: Starting Journal Service...
Jun 08 01:12:02 up systemd[1]: Started Journal Service.
Jun 08 01:12:02 up kernel: vboxdrv: Found 2 processor cores.
Jun 08 01:12:02 up kernel: vboxdrv: fAsync=1 offMin=0x20125 offMax=0x20125
Jun 08 01:12:02 up kernel: vboxdrv: TSC mode is 'asynchronous', kernel timer mode is 'normal'.
Jun 08 01:12:02 up kernel: vboxdrv: Successfully loaded version 4.3.12_OSE (interface 0x001a0007).
Jun 08 01:12:02 up systemd-journal[135]: Journal started
-- Subject: The Journal has been started
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- The system journal process has been starting up, opened the journal
-- files for writing and is now ready to process requests.
Jun 08 01:12:02 up systemd[1]: Starting Slices.
-- Subject: Unit slices.target has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit slices.target has begun starting up.
Jun 08 01:12:02 up systemd[1]: Reached target Slices.
-- Subject: Unit slices.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit slices.target has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd[1]: Mounted Temporary Directory.
-- Subject: Unit tmp.mount has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit tmp.mount has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd[1]: Started Setup Virtual Console.
-- Subject: Unit systemd-vconsole-setup.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-vconsole-setup.service has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd[1]: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 126 (systemd-binfmt)
Jun 08 01:12:02 up systemd[1]: Mounting Arbitrary Executable File Formats File System...
-- Subject: Unit proc-sys-fs-binfmt_misc.mount has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit proc-sys-fs-binfmt_misc.mount has begun starting up.
Jun 08 01:12:02 up systemd[1]: Mounted Huge Pages File System.
-- Subject: Unit dev-hugepages.mount has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit dev-hugepages.mount has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd[1]: Mounted Arbitrary Executable File Formats File System.
-- Subject: Unit proc-sys-fs-binfmt_misc.mount has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit proc-sys-fs-binfmt_misc.mount has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd[1]: Mounted POSIX Message Queue File System.
-- Subject: Unit dev-mqueue.mount has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit dev-mqueue.mount has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd[1]: Mounted Debug File System.
-- Subject: Unit sys-kernel-debug.mount has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit sys-kernel-debug.mount has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd[1]: Started Apply Kernel Variables.
-- Subject: Unit systemd-sysctl.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-sysctl.service has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd-modules-load[130]: Inserted module 'vboxdrv'
Jun 08 01:12:02 up systemd[1]: Started Create Static Device Nodes in /dev.
-- Subject: Unit systemd-tmpfiles-setup-dev.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-tmpfiles-setup-dev.service has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd[1]: Started Load Kernel Modules.
-- Subject: Unit systemd-modules-load.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-modules-load.service has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd[1]: Mounted FUSE Control File System.
-- Subject: Unit sys-fs-fuse-connections.mount has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit sys-fs-fuse-connections.mount has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd[1]: Mounting Configuration File System...
-- Subject: Unit sys-kernel-config.mount has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit sys-kernel-config.mount has begun starting up.
Jun 08 01:12:02 up systemd[1]: Starting udev Kernel Device Manager...
-- Subject: Unit systemd-udevd.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-udevd.service has begun starting up.
Jun 08 01:12:02 up systemd-fsck[121]: /dev/sda5: Superblock last write time is in the future.
Jun 08 01:12:02 up systemd-fsck[121]: (by less than a day, probably due to the hardware clock being incorrectly set). FIXED.
Jun 08 01:12:02 up systemd[1]: Mounted Configuration File System.
-- Subject: Unit sys-kernel-config.mount has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit sys-kernel-config.mount has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd[1]: Started udev Kernel Device Manager.
-- Subject: Unit systemd-udevd.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-udevd.service has finished starting up.
-- The start-up result is done.
Jun 08 01:12:02 up systemd-udevd[153]: starting version 213
Jun 08 01:12:02 up systemd-udevd[153]: invalid key/value pair in file /etc/udev/rules.d/50-embedded_devices.rules on line 8,starting at character 97 ('')
Jun 08 01:12:03 up kernel: input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input5
Jun 08 01:12:03 up kernel: ACPI: Power Button [PWRB]
Jun 08 01:12:03 up kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input6
Jun 08 01:12:03 up kernel: ACPI: Power Button [PWRF]
Jun 08 01:12:03 up kernel: ACPI: [Package] has zero elements (f5bfc400)
Jun 08 01:12:03 up kernel: ACPI: Invalid passive threshold
Jun 08 01:12:03 up kernel: thermal LNXTHERM:00: registered as thermal_zone0
Jun 08 01:12:03 up kernel: ACPI: Thermal Zone [THRM] (40 C)
Jun 08 01:12:03 up kernel: ACPI: Fan [FAN] (on)
Jun 08 01:12:03 up kernel: k8temp 0000:00:18.3: Temperature readouts might be wrong - check erratum #141
Jun 08 01:12:03 up kernel: input: PC Speaker as /devices/platform/pcspkr/input/input7
Jun 08 01:12:04 up kernel: microcode: AMD CPU family 0xf not supported
Jun 08 01:12:04 up kernel: kvm: Nested Virtualization enabled
Jun 08 01:12:04 up kernel: ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 22
Jun 08 01:12:04 up kernel: hda_intel: msi for device 1043:81f6 set to 0
Jun 08 01:12:04 up kernel: microcode: AMD CPU family 0xf not supported
Jun 08 01:12:04 up kernel: powernow-k8: fid 0xc (2000 MHz), vid 0xc
Jun 08 01:12:04 up kernel: powernow-k8: fid 0xa (1800 MHz), vid 0xe
Jun 08 01:12:04 up kernel: powernow-k8: fid 0x2 (1000 MHz), vid 0x12
Jun 08 01:12:04 up kernel: powernow-k8: Found 1 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ (2 cpu cores) (version 2.20.00)
Jun 08 01:12:04 up kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jun 08 01:12:04 up kernel: parport_pc 00:09: reported by Plug and Play ACPI
Jun 08 01:12:04 up kernel: parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP]
Jun 08 01:12:04 up kernel: forcedeth: Reverse Engineered nForce ethernet driver. Version 0.64.
Jun 08 01:12:04 up kernel: ACPI: PCI Interrupt Link [APCH] enabled at IRQ 21
Jun 08 01:12:04 up kernel: ppdev: user-space parallel port driver
Jun 08 01:12:04 up kernel: Linux agpgart interface v0.103
Jun 08 01:12:04 up kernel: forcedeth 0000:00:08.0: ifname eth0, PHY OUI 0x5043 @ 1, addr 00:1a:92:20:f8:d7
Jun 08 01:12:04 up kernel: forcedeth 0000:00:08.0: highdma csum vlan pwrctl mgmt gbit lnktim msi desc-v3
Jun 08 01:12:04 up kernel: i2c i2c-0: nForce2 SMBus adapter at 0x1c00
Jun 08 01:12:04 up kernel: ACPI Warning: SystemIO range 0x00001c40-0x00001c7f conflicts with OpRegion 0x00001c40-0x00001c45 (\_SB_.PCI0.SM01) (20131218/utaddress-258)
Jun 08 01:12:04 up kernel: ACPI Warning: SystemIO range 0x00001c40-0x00001c7f conflicts with OpRegion 0x00001c40-0x00001c45 (\_SB_.PCI0.SM00) (20131218/utaddress-258)
Jun 08 01:12:04 up kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jun 08 01:12:04 up kernel: nv_tco: NV TCO WatchDog Timer Driver v0.01
Jun 08 01:12:04 up kernel: nv_tco: Watchdog reboot not detected
Jun 08 01:12:04 up kernel: nv_tco: initialized (0x1440). heartbeat=30 sec (nowayout=0)
Jun 08 01:12:05 up mtp-probe[205]: checking bus 1, device 2: "/sys/devices/pci0000:00/0000:00:02.0/usb1/1-2"
Jun 08 01:12:05 up mtp-probe[204]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:02.0/usb1/1-3"
Jun 08 01:12:05 up mtp-probe[204]: bus: 1, device: 3 was not an MTP device
Jun 08 01:12:05 up mtp-probe[205]: bus: 1, device: 2 was not an MTP device
Jun 08 01:12:05 up kernel: nvidia: module license 'NVIDIA' taints kernel.
Jun 08 01:12:05 up kernel: Disabling lock debugging due to kernel taint
Jun 08 01:12:05 up kernel: ACPI: PCI Interrupt Link [APC6] enabled at IRQ 16
Jun 08 01:12:05 up kernel: vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=io+mem,decodes=none:owns=none
Jun 08 01:12:05 up kernel: NVRM: loading NVIDIA UNIX x86 Kernel Module 304.121 Tue Mar 4 19:50:35 PST 2014
Jun 08 01:12:05 up kernel: mousedev: PS/2 mouse device common for all mice
Jun 08 01:12:06 up kernel: input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:06.1/input/input9
Jun 08 01:12:07 up kernel: input: HDA NVidia Line Out Side as /devices/pci0000:00/0000:00:06.1/sound/card0/input15
Jun 08 01:12:07 up kernel: input: HDA NVidia Line Out CLFE as /devices/pci0000:00/0000:00:06.1/sound/card0/input14
Jun 08 01:12:07 up kernel: input: HDA NVidia Line Out Surround as /devices/pci0000:00/0000:00:06.1/sound/card0/input13
Jun 08 01:12:07 up kernel: input: HDA NVidia Line Out Front as /devices/pci0000:00/0000:00:06.1/sound/card0/input12
Jun 08 01:12:07 up kernel: input: HDA NVidia Line as /devices/pci0000:00/0000:00:06.1/sound/card0/input11
Jun 08 01:12:07 up kernel: input: HDA NVidia Rear Mic as /devices/pci0000:00/0000:00:06.1/sound/card0/input10
Jun 08 01:12:07 up systemd[1]: Starting Sound Card.
-- Subject: Unit sound.target has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit sound.target has begun starting up.
Jun 08 01:12:07 up systemd[1]: Reached target Sound Card.
-- Subject: Unit sound.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit sound.target has finished starting up.
-- The start-up result is done.
Jun 08 01:12:09 up systemd-fsck[121]: /dev/sda5: 175829/1228800 files (1.0% non-contiguous), 2992507/4907849 blocks
Jun 08 01:12:09 up systemd[1]: Started File System Check on Root Device.
-- Subject: Unit systemd-fsck-root.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-fsck-root.service has finished starting up.
-- The start-up result is done.
Jun 08 01:12:09 up systemd[1]: Starting Remount Root and Kernel File Systems...
-- Subject: Unit systemd-remount-fs.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-remount-fs.service has begun starting up.
Jun 08 01:12:09 up systemd[1]: Started Remount Root and Kernel File Systems.
-- Subject: Unit systemd-remount-fs.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-remount-fs.service has finished starting up.
-- The start-up result is done.
Jun 08 01:12:09 up systemd[1]: Starting Load/Save Random Seed...
-- Subject: Unit systemd-random-seed.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-random-seed.service has begun starting up.
Jun 08 01:12:09 up systemd[1]: Starting Local File Systems (Pre).
-- Subject: Unit local-fs-pre.target has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit local-fs-pre.target has begun starting up.
Jun 08 01:12:09 up systemd[1]: Reached target Local File Systems (Pre).
-- Subject: Unit local-fs-pre.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit local-fs-pre.target has finished starting up.
-- The start-up result is done.
Jun 08 01:12:09 up kernel: EXT4-fs (sda5): re-mounted. Opts: (null)
Jun 08 01:12:09 up systemd[1]: StIt sounds like a known bug for which a fix is already in [testing] and other information is available here on the forums.
Is your hardware clock set to UTC? and/or do you dual boot with Windows? -
I have 24GB of RAM in my 64 bit Windows 7 system running on RAID 5 with an i7 CPU.
A while ago I updated from Premiere CS5 to CC and then from Premiere CC to CC 2014. I updated all my then current projects to the new version as well.
Most of the projects contained 1080i 25fps (1080x1440 anamorphic) MPEG clips originally imported (captured from HDV tape) from a Sony HDV camera using Premiere CS5 or CC.
Memory consumption during re-indexing.
When updating projects I experienced frequent crashes going from CS5 to CC and later going from CC to CC 2014. Updating projects caused all clips in the project to be re-indexed. The crashes were due to the re-indexing process causing excessive RAM consumption and I had to re-open each project several times before the re-index would eventually complete successfully. This is despite using the setting to limit the RAM consumed by Premiere to much less than the 24GB RAM in my system.
I checked that clips played; there were no errors generated; no clips showed as Offline.
Some Clips now Offline:Importer CC 2014
Now, after some months editing one project I found some of the MPEG clips have been flagged as "Offline: Importer" and will not relink. The error reported is "An error occurred decompressing video or audio".
The same clips play perfectly well in, for example, Windows Media Player.
I still have the earlier Premiere CC and the project file and the clips that CC 2014 importer rejects are still OK in the Premiere CC version of the project.
It seems that the importer in CC 2014 has a bug that causes it to reject MPEG clips with which earlier versions of Premiere had no problem.
It's not the sort of problem expected with a premium product.
After this experience, I will not be updating premiere mid-project ever again.
How can I get these clips into CC 2014? I can't go back to the version of the project in Premiere CC without losing hours of work/edits in Premiere CC 2014.
Any help appreciated. Thanks.To answer my own question: I could find no answer to this myself and, with there being no replies in this forum, I have resorted to re-capturing the affected HDV tapes from scratch.
Luckily, I still had my HDV camera and the source tapes and had not already used any of the clips that became Offline in Premiere Pro CC 2014.
It seems clear that the MPEG importer in Premiere Pro CC 2014 rejects clips that Premiere Pro CC once accepted. It's a pretty horrible bug that ought to be fixed. Whether Adobe have a workaround or at least know about this issue and are working on it is unknown.
It also seems clear that the clip re-indexing process that occurs when upgrading a project (from CS5 to CC and also from CC to CC 2014) has a bug which causes memory consumption to grow continuously while it runs. I have 24GB RAM in my system and regardless of the amount RAM I allocated to Premiere Pro, it would eventually crash. Fortunately on restarting Premiere Pro and re-loading the project, re-indexing would resume where it left off, and, depending on the size of the project (number of clips to be indexed), after many repeated crashes and restarts re-indexing would eventually complete and the project would be OK after that.
It also seems clear that Adobe support isn't the greatest at recognising and responding when there are technical issues, publishing "known issues" (I could find no Adobe reference to either of these issues) or publishing workarounds. I logged the re-index issue as a bug and had zero response. Surely I am not the only one who has experienced these particular issues?
This is very poor support for what is supposed to be a premium product.
Lesson learned: I won't be upgrading Premiere again mid project after these experiences. -
High memory consumption in XSL transformations (XSLT)
Hello colleagues!
We have the problem of a very high memory consumption when transforming XML
files with CALL TRANSFORMATION.
Code example:
CALL TRANSFORMATION /ipro/wml_translate_cls_ilfo
SOURCE XML lx_clause_text
RESULT XML lx_temp.
lx_clause_text is a WordML xstring (i.e. it is a Microsoft Word file in XML
format) and can therefore not be easily splitted into several parts.
Unfortunately this string can get very huge (e.g. 50MB). The problem is that
it seems that CALL TRANSFORMATION allocates memory for the source and result
xstrings but doesn't free them after the transformation.
So in this example this would mean that the transformation allocates ~100MB
memory (50MB for source, ~50MB for result) and doesn't free it. Multiply
this with a couple of transformations and a good amount of users and you see
we get in trouble.
I found this note regarding the problem: 1081257
But we couldn't figure out how this problem could be solved in our case. The
note proposes to "use several short-running programs". What is meant with
this? By the way, our application is done with Web Dynpro for ABAP.
Thank you very much!
With best regards,
Mario DüsselHi,
q1. how come the Ram consumption is increased to 99% on all the three boxes?If we continue with the theory that network connectivity was lost between the hosts, the Coherence servers on the local hosts would form their own clusters. Prior to the "split", each cache server would hold 1/12 of the primary and 1/12 of the backup (assuming you have one backup). Since Coherence avoids selecting a backup on the same host as the primary when possible, the 4 servers on each host would hold 2/3 of the cache. After the spit, each server would hold 1/6 of the primary and 1/6 of the backup, i.e., twice the memory it previously consumed for the cache. It is also possible that a substantial portion of the missing 1/3 of the cache may be restored from the near caches, in which case, each server would then hold 1/4 of the primary and 1/4 of the backup, i.e., thrice the memory it previously consumed for the cache.
q2: where is the cache data stored in the coherence servers?on which memory?The cache data is typically stored in the jvm's heap memory area.
Have you reviewed the logs?
Regards,
Harv -
Memory consumption of queries in workbooks
We have an issue with the exceution of a Workbook which contains several queries. The queries require very much memory which finally leads to a shortdump (TSV_TNEW_PAGE_ALLOC_FAILED). We found that during execution of the workbook the memory is not released after a query has been executed and therfore at some point of time the dump occurs. However, if the queries are refreshed manually one after the other in the workbook the memory is relaesed and finally the workbook can be executed by this workaround.
My question is, if anyone has an idea, if it is possible to apply a setting somewhere that the queries relaese the memory after execution when they are all refreshed together in the workbook?
Thanks a lot in advance for any hint & Kind regards,
Hans-JörgHi,
Try this,
You may be able to workaround the problem by increasing free memory avaiable, parameter em/initial_size_MB (contact your Basis team or refer note 835474).
Also concenrate on parameter ztta/roll_extension (Refer note 146289)
Try increasing the parameter, abap/heap_area_dia from tcode RZ11.
Also check the following notes in detail as well,
649327 Analysis of memory consumption
425207 SAP memory management, current parameter ranges
369726 TSV_TNEW_PAGE_ALLOC_FAILED
185185 Application: Analysis of memory bottlenecks
If the issue persist, please review SAP Note 779123 and query design.
check this,
http://scn.sap.com/thread/288222
http://www.sapfans.com/forums/viewtopic.php?f=3&t=109557
regards,
anand. -
Memory Consumption: Start A Petition!
I am using SQL Developer 4.0.0.13 Build MAIN 13.80. I was praying that SQL Developer 4.0 would no longer use so much memory and, when doing so, slow to a crawl. But that is not the case.
Is there a way to start a "petition" to have the SQL Development team focus on the products memory usage? This is problem has been there for years now with many posts and no real answer.
If there isn't a place to start a "petition" let's do something here that Oracle will respond to.
Thank youYes, at this point (after restarting) SQL Developer is functioning fine. Windows reports 1+ GB of free memory. I have 3 worksheets open all connected to two different DB connections. Each worksheet has 1 to 3 pinned query results. My problem is that after working in SQL Developer for a a day or so with perhaps 10 worksheets open across 3 database connections and having queried large data sets and performing large exports it becomes unresponsive even after closing worksheets. It appears like it does not clean up after itself to me.
I will use Java VisualVM to compare memory consumption and see if it reports that SQL Developer is releasing memory but in the end I don't care about that. I just need a responsive SQL Developer and if I need to close some worksheets at times I can understand doing so but at this time that does not help. -
[SOLVED]X start failure after upgrade: dri3,present modules missing
I start X with ~.xinitrc from console, which won"t work after last upgrade --first in two weeks.
(EE) Server terminated with error (1).Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
Xorg.log.0 :
[51:778] (EE) intel: Failed to load module "dri3" (module does not exist, 0)
[51:779] (EE) intel: Failed to load module "present" (module does not exist, 0)
Installed packages (EDIT: completed):
xf86-video-intel-2.99.{914-4,916-1}-i686 and also tried with xf86-video-intel-git, with "SNA" acceleration.
intel-dri 10-2.7-3
dri2proto 2.8-2
dri3proto 1.0-1
xf86driproto 2.1.1-3
Linux 3.15.5-2-ARCH i686
Linux CK Atom 3.16.2-1
Issue occurred after upgrading from v2.99.912-1 to v2.99.914+. I was going to try downgrade xf86-video-intel to v2.99.912-1 (as in the first thread in Refs) but went in a dependency conflict, with the older intel driver requiring glamor-egl which conflicts with xorg-server ':-|
Atom netbook
lspci:
00:02.0 VGA compatible controller: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller
Some refs :
» [SOLVED] X start failure after upgrade https://bbs.archlinux.org/viewtopic.php?pid=1426837
» [Solved] xf86-video-Intel-2.99.912-1 breaks xorg https://bbs.archlinux.org/viewtopic.php?id=182932
Last edited by kozaki (2014-09-12 09:45:53)The issue occurred after upgrading from xf86-video-intel-v2.99.912-1 to v2.99.914+ and xorg-server-1.15.2-1 to 1.16.0-6 (and -devel).
same issue if:
- Switching accelaration method to "UXA" as per https://bugs.archlinux.org/task/40860
- Adding Option "DRI" "False"
Digged a bit:
- same modules errors but appears to be a Gnome bug (X starts): https://bbs.archlinux.org/viewtopic.php?pid=1441716
- same modules errors but X starts up without problems http://www.linuxquestions.org/questions … 175511372/
makes me doubt if this issue is related to the modules not found. Which is the single indication I found so far x-/
Any light on where can the issue comes from? hardware is pretty much standard even if getting a bit old. Never had Xorg related issue so far on this pancake.
Last edited by kozaki (2014-09-11 11:05:42) -
Memory Consumption in Multidimensional Arrays
Hi,
I've noticed that the memory consumption of multidimensional arrays in Java is sometimes far above one could expect for the amount of data that is being stored. For example, here is a simple program which stores a table containing only integers and reports the memory consumption after it is filled:
public static void main(String[] args) {
int tableSize = 1000000;
int noFields = 10;
Random rnd3 = new Random();
int arr[][] = new int[tableSize][noFields];
for (int i = 0; i < tableSize; i++) {
for (int j = 0; j < noFields; j++) {
arr[i][j] = rnd3.nextInt(100);
Runtime.getRuntime().gc();
Runtime.getRuntime().gc();
Runtime.getRuntime().gc();
// Ensures table's data is still referenced
System.out.println(arr[rnd3.nextInt(arr.length)]);
long totalMemory = Runtime.getRuntime().totalMemory();
long usedMemory = totalMemory-Runtime.getRuntime().freeMemory();
System.out.println("Total Memory: " + totalMemory/(1024.0*1024) + " MB.");
System.out.println("Used Memory: " + usedMemory/(1024.0*1024) + " MB.");
Output:
Total Memory: 866.1875 MB.
Used Memory: 62.124053955078125 MB.
In this case the memory consumption was around 20MB above the expected 38MB required for storing 10M integers. The interesting thing is that the memory consumption varies when the numbers of rows and columns are changed, even though the total amount of items is kept fixed (see below):
Rows:100; Cols:100000 -> Used Memory: 43,05 MB
Rows:1000; Cols:10000 -> Used Memory: 43,07 MB
Rows:10000; Cols:1000 -> Used Memory: 43,24 MB
Rows:100000; Cols:100 -> Used Memory: 44,96 MB
Rows:1000000; Cols:10 -> Used Memory: 62,15 MB
Rows:10000000; Cols:1 -> Used Memory: 192,15 MB
Any ideas about the reasons for that behavior?
Thanks,
Marcelomrnm wrote:
In this case the memory consumption was around 20MB above the expected 38MB required for storing 10M integers.That's only the expected value if you assume that a 2D array of ints is nothing more than a bunch of ints lined up end to end. This is not the case. A "2D" array in java is really just a plain ol' array whose component type is "reference to array".
The interesting thing is that the memory consumption varies when the numbers of rows and columns are changed, even though the total amount of items is kept fixed (see below):That's because, e.g., new int[200][100] creates 200 array objects (and references to each of them), each of which holds 100 ints, while new int[100][200] creates 100 array objects (and references to each of them), each of which holds 200 ints.
Edited by: jverd on Feb 24, 2010 11:17 AM -
Memory consumption when computer locked?
I noticed something strange with my app. If I leave it open and switch to login screen, it's memory consumption raises up to gigabyte. I discover this in Activity Monitor when logging in back. But just after I logged back in, process's working set size begins slowly going back to normal, and then there're no leaks reported, and app works just normal.
Other apps dont issue this. Besides ordinary Cocoa GUI, my app makes use of multithreading, sockets and webcam capture (sequence grabber).
Looks like there's something specific to fast user switching feature that I don't know, maybe some buffer is infinitely filled until there's chance to display, or something.
Does anyone have idea what it could be?
Message was edited by: kasymAnother point that I wanted to mention...
As a mentioned, we are looping with our application through a resultset and "processing" each record. If we simply disconnect the sqlca object (the transaction object the PowerBuilder application uses to connect to the database) and then simply re-connect, say, every 100 records or so... the problem goes away. We simply disconnect, re-connect, and pick up at the point where we left off. This shows me the memory gets flushed every time the session is disconnected.
This is the effect that I want... for the memory to be flushed every so many records, so it can continue looping through each record in the resultset as if it were doing the first one each time. I understand there may be a performance impact as it flushes the memory for each record (or every hundred or so), but I'm willing to sacrifice that to keep it from running out of memory altogether.
I'd appreciate feedback on this point.
Maybe you are looking for
-
Virtual QWERTY vs. Touchscreen
In the online Verizon comparison chart of the two new Windows 8 phones keyboards, the 8X has "Virtual QWERTY" and the Nokia is "Touchscreen". What is the difference?
-
JMS Module, Foreign Server: Destination unreachable
Hi, In our OSB setup we have 2 weblogic domains (on RHEL5), one for hosting the OSB services and one that is used solely for the purpose of JMS messsaging. Therefore we have configured a Foreign Server in our JMS Module on the OSB Domain with followi
-
Hi, I have a internal table T. when the t-zuonr is blank, the ALV look like: t-zuonr document no data 200630303 AB 2007.08.31 200627855 AB 2007.06.30
-
I have a Sony A6000 camera and can't seem to get Lightroom 5.6 to recognize the files and download them on a PC running Windows 8. No problem on a Mac. The Windows PC will see it with windows explorer but can't seem to get Lightroom to recognize t
-
The same connection I used to watch netflix yesterday isn't working today. I get a message saying that it can't support it and that if I'm using "airplay" I need to turn off mirrors. I've got the cookies set correctly. I've never used air play. Ha