Aperture 3.4.5 lagging
Hi , I have the latest iMac 3.4 i7 ,2gig graphics ,8 gig mem and 1tera Fusion hd . OS X 10.8.3 . Aperture 3.4.5
I am having lagging with brush's . When turning a photo to Black and white and then brushing away back to colour .
At first when I got the spinning ball of death , I just thought , him a small glitch . Then as I began brushing away back to colour it began taking awhile for the effect to catch up ??? Oh and mag at 100% at 200% it lags a tad slower. I have a 3d program Poser Pro 2012 and it renders ok as expected. As does Final Cut Pro X works so far with no probs.
The hard drive is virtually empty , as it is a new purchase , So there's no excuse for anyone saying it's because the hard drive is nearly full .
It is most certainly repeatable , so got to be a bug of some sort . I had not expected lagging with a power iMac . Unless of corse , you just have to wait while the iMac catch's up ?
This is my first mac computer , and so far not so impressed . I expect a mac expert will know just what I'm doing wrong. Please advise if possible. . .
Newbie to this so I hope I've posted in the right place , will check ,but in case . . .
Good to hear you are doing ok with your computer . Like everything new , I just don't see Aperture as a pro app when I can repeat the same thing over and over . It's not like Aperture has A.I and is learning how and when , is it. Ok , for your spec it runs fine , happy for you . This was happening in 2010 , and has been sorted I would think for yours. As the one we have is so new ,and getting lagging and spinning ball, then there is obviously something .... Not quite right for my spec .
The photo I used was less than 6 meg ? I had the Activity monitor open and CPU was less than 1% and tons of mem and disk space . Only finder , safari and the monitor running , repeated several times. And also ,found when exporting as a tiff , it did not keep black and white ,however it was evident the photo had been worked on as you can see the edges where I had brushed away and feathered left a yellow tinge in the saved version .Also on one occasion, when duplicating, it did not ,it just did a colour version ? , let alone the screen going total speckle, like screen was full of grain. Guess it's the 2gig graphics card after that. .
. Might be a nice iMac to look at , taken years to put the cash together and near finishing work . So purchased it believing what I loosely read .
However , will persevere , thank you for replying , I am going to support and see what they say . . .
Similar Messages
-
Looking to purchase Mac Pro (dual CPU) for Aperture/Photoshop
My first question is: Will I be able to upgrade the CPU later on? If I were to get the dual 2.26Ghz setup which is currently the base processor (and, the most affordable option), would I be able to purchase the 2.93Ghz CPUs few years down the line and install them?
I certainly know that memory can be upgraded, but I'd like this machine (which, is in itself a considerable expense) to last for at least six years with upgrades.
I currently use 2.16Ghz Core Duo MBP with 2Gb RAM (maximum it can take) and my Aperture and Photoshop have trouble running simultaneously while editing 12 megapixel files from my camera.
Thanks a million guys!I came from a MacBook, the very first MacBook ever, also maxed out at 2 GB (shared RAM), so I can completely relate to your frustration.
I'm running PS CS3 and Aperture 2 on the Mac Pro with the dual quads and am quite happy. My XSi also generates 12 MP RAW files. 6 GB of RAM is more than enough to run Aperture and PS simultaneously. I can do things like HDR processing with multiple 16-bit TIFF outputs and process them using masking without quitting Aperture. It's just beautiful how much it can do.
The GT 120 seems to be quite capable of making lots of adjustments in Aperture simultaneously without perceivable lag. For most of my non-studio work, I'm retouching, adjusting wb, colors, levels, enhance, and changing exposure settings all at the same time. The GT 120 seems to keep everything I've been able to throw at it, and I throw a lot. It's even speedy while zoomed in at 100%.
At the Apple store, I played with the single quad-core version and was blown away by it's performance as well. Honestly, I didn't perceive any difference between the dual and the single quad versions as far as performance in Aperture and Photoshop. Of course, with half the RAM, you won't be able to have as many layers. When I used the one at the store, I was so blown away, I was afraid the dual quad version was a waste of money.
I wouldn't count on being able to upgrade the processors later, but my biggest concern is that we won't ever be able to really take advantage of all the power the Mac Pro already offers. When you output from Aperture, it's really not that fast, the machine just spends all it's time waiting for the hard drive anyway. The Mac Pro is a server-grade machine through and through. As a still photographer, I can assure you, you'll be blown away by the power of Nehalem and bummed at your inability to use it anywhere near it's full potential. It'll take YEARS for Intel's consumer-grade processors (like the i7) to catch up with the Xeons, and even then, they probably won't support ECC RAM. And each core can handle two sets of instructions at the same time, so virtually, the dual-quad has 16 cores.
With the amount of focus being placed upon harnessing the power of GPU, the power of the CPU is likely to have less and less impact on the speed of your machine as time passes. If you're worried about the RAM ceiling of the single quad Mac Pro, buy the dual-quad, but I wouldn't worry so much about the clockspeed. You should keep in mind, Aperture can't handle the multiple graphics cards, so I'd get a single GT 120 and consider buying something more substantial later, *after you get Snow Leopard*. Snow Leopard is going to use the GPU in ways we've never seen before and I predict it will be a game-changing release.
I'd also check out the refurbs! Hope this helps! -
Waiting for "Adjustments" To Load
Am I the only one who notices that the first time you attempt to load the Adjustment panel the beach ball raises its head and you have to wait.
I am running A3, 3.03 to be exact, on a very fast iMac, i7 with 8GB of memory. Obviously I got good horsepower. What is happening in the background that makes me wait? Why can't those files or frameworks load initially when Aperture loads?
Also, how come no splash screen when A3 loads?Hi Michael
I encountered this issue when I installed two presets from MacCreate, the Neutral and Graduated Density Adjustment preset and the Noise Adjustment preset. The first time I attempt to use the Adjustment panel after launching Aperture there is a lag of 3 to 5 seconds and an occasional glimpse of the beach ball.
As soon as I delete these presets the problem goes away. Re-installing one or both presets and the problem comes back. I have been in contact with the folk at MacCreate and while they have been very understanding and concerned they have not been able to reproduce the problem.
So if you have installed any third party presets you may want to try deleting them one by one to see whether that fixes the problem for you.
I am using an Early 2008 Mac Pro 3.2 with 16 GB RAM so, like you, horsepower should not be an issue. -
Hi
I have the macbook retina 15' 16 Go RAM and i see that Aperture makes lag when i switch with Mail for exemple.
If i active low resolution in 'information' of application, the lags disappear :
I hope that aperture know this problem, and will resolve it soon because APERTURE WITHOUT HIGH RESOLUTION on RETINA is simply not tolerate.
thanks
franckI have a similar problem. when accessing the dock, hot corners, my pointer in some apps as well as other system animations. this seems to be a common problem with MBPR. Restarting doesnt help.
Any ideas or solutions would be great.
cheers -
I am relatively new to the mac, but with cameras that shoot in RAW (and presuming Aperture would be the leading product - I went with it over Aperture) and better editing features, went with Aperture.
However now, with the new features in iPhoto I wonder if Aperture is really the right choice for me. Afterall, the two main basics needed by me in photo management software (raw support and non destructive editing) are supported in iPhoto (aren't they?). And the other features in iPhoto (events, faces, places) are so useful... I just would like Aperture (as the premium pro product) to be more leading in innovation. Also, having no idea when we might expect to see Aperture 3 (at least the iLife suites are most likely annual), I am seriously considering a switch back to iPhoto.
Thoughts on this?
Message was edited by: adammloweiPhoto is exactly what it says on the tin. It’s a photo organiser aimed at the home user, and shines pretty well when used with a point and shoot. For RAW photographers it’s a little clunky. When you import a RAW it makes a JPEG Preview, and yes you can edit the RAW in either iPhoto or an external editor. The edits are saved as jpegs. The non-destructive editing is actually quite good, you never lose any generations on pics edited in iPhoto (see here for details). The library size isn’t that much larger than an Aperture Library with good quality previews. And of course you can run the library from an external if disk space is an issue.
Compared to Aperture? There is no comparison. Iphoto is definitely the little brother. That said, my 20k+ family library is in iPhoto, and used by all the family. It’s robust and scores very well on ease-of-use.
Regards
TD -
I upgraded to Leopard a few weeks ago and was using Time Machine and included Aperture backups while Aperture was running. I've since read that there's a problem with this, so I stopped Time Machine backups of my Aperture Library.
But now, every time I try to edit text on a page of a book, Aperture hangs. If I type 25 characters, for example, it will lag behind... showing one character every 5 MINUTES or so until it catches up with my typing... which would take about two hours for the 25 characters. I have to force quit. I've tried restarting and repairing permissions. No help.
Do I have a corrupt library? If so, what do I do? I have 3 vaults, all created in the last day or two.Delete Aperture, open App Store > Purchases and download Aperture. This should fix your issue
-
Aperture 2.1.2 crashing constantly, will not allow me to move library/ create vaults
Hi, I've searched for threads on this, but nothing came up with my particular situation. First, I'll state my specs
iMac 24" (aluminum)
3.06GHz Core2 Duo
4GB RAM
500GB HDD
So, after much procrastinating, I decided this weekend that I would organize my photos better, and move my growing Aperture library off my internal drive in hopes of speeding up my recently lagging computer. I migrated from iPhoto to Aperture back in August of 2008 and have always been meaning to make a vault of all my old work and just store that offsite somewhere so I don't have to worry about the disk space or losing the files. But I never got around to it.
So now my Aperture library is 35,000 photos large, and weighs in at 302GB.
The first thing I tried to do (before I even knew Aperture was going to start crashing) was to move the Aperture Library file from its default location in the users/pictures folder to one of my external 1.5TB drives. However, the transfer would fail around 6GB in and say "some files could not be read or written." I tried several times to no avail.
Giving up that route, I read around online and decided that I could just make a vault of my entire library on the external drive, then create a new library there, and restore from the vault.
So I open Aperture to try and make a vault. It "unexpectedly quits" right when the interface loads. I tried again and got as far as naming the new vault, then it crashed again. Now it crashes even if I am trying to just view my images. I went on a short roadtrip with friends and got back last night, and it crashed halfway through the import of 400 images, but finished importing when I reopened it. I don't know if that's what started off the whole thing.
Anyway, I noticed that I only had 4(!)GB of space left on my internal drive, so I did some quick cleaning and rearranging to external drives and freed up about 45GB of space. I figured that would give the app plenty of room to breathe.
Nope. Still crashes.
Rebooted several times, no help.
Reset PRAM several times, nada.
I am in real trouble here. I'm a photography student with three studio classes this quarter and I can't have this happening. I paid top dollar for this machine less than six months ago and now it's puttering along like it's 2 or 3 years old. When Aperture is open (when it would still work) the rest of the computer would just slow to a crawl. I have 4GB of RAM, why doesn't Aperture use more? I was reading that it would only use 1 or 2GB max. Why?
But that part is not important.
I need to get this fixed, so ANY help is GREATLY appreciated! I have the crash report saved from the last crash, so if anyone wants to see any part of it, let me know. It told me which thread caused the crash but it looked like generic usage stuff, nothing special (I was just trying to look at my trip photos).
Thanks in advance,
Screaming in Savannah
(Chris)This is awkward. Right... I have used Aperture since it came out.
In fact, after all these failures, you should try the rebuilding your library first.
Hold down Option and Command when launching Aperture, though you couldn't back up your files... which was recommended by Apple before you rebuild it.
It should correct and repair any broken links or permissions. See if it works.
After, you can simply COPY and not MOVE the library to the external HD. Do you use Firewire? It's much better and reliable. After the library is copied, point Aperture to use the external HD in preference. Close and reopen, it should open the library from the external HD.
The better bet is to make sure you are using an external HD with Firewire 800. I have some experience with USB2 drives when Aperture crashes a lot. It may seem some kind of bandwidth problem which I couldn't understand. It seems find with small jpg files but if you start importing RAW or do something with the RAW files, USB drives always fail.
I have moved my library to an external drive since Aperture 2 as my library has grown beyond the internal capacity. My standard practice is now, after working the files, export them in TIFF or JPG, export the 'Project' with the RAW files to DVDs, remove from the library and re-import the JPGs back to keep the library size. Also I keep two faults in separate locations.
I hope it works.
J -
Aperture 3.1 takes incredibly long time to start
Since after the upgrade from 3.0.x to 3.1 Aperture takes a long time to start up. I click on the Aperture icon in the dock, the icon bounces for almost a minute, then it stays still for more than a minute, doing nothing and without the "light bulb" indicator that the app is running. It's just sitting there in the dock. After a total of 2-5 minutes, the Aperture window opens and I can start working.
I tried many things suggested in the forums to speed up Aperture:
I turned off Faces
I turned off sharing of previews with iLife and iWork
I turned off using embedded JPEGs from camera
I deleted all Aperture preferences as I thought there might be a corruption after upgrade
I removed all plugins from Aperture plugin folder to make sure nothing is interfering
I used the Aperture rebuild and repair options on the library
I created a new Aperture library and imported my photos from the old library into a fresh one
I downloaded and installed the Aperture 3.1 update again to make sure nothing got corrupted during update installation
Nothing helped. Aperture takes 2-3 minutes to fully start.
Plugins in use: NIK Software's Viveza 2 and HDR Efex Pro, Tiltshift for Aperture. That's it. And, as I said, it doesn't help if I take them out of Aperture's plugin folder so they don't get loaded. Problem still remains.
My library isn't that big: 29GB in 8230 items. Is 2-3 minutes a normal startup time?
Has anyone experienced a similar problem after upgrading? As I literally exchanged everything underneath Aperture (deleted preference files, created new library and imported photos from old lib) I don't know what else I could try. Totally uninstall Aperture and re-install it again?
Any suggestions what this could be?
On a sidenote, interestingly Logic Pro takes about the same amount of time to start. The icon bounces in the dock for almost 1 minute, then I hear the harddisk working for another minute until the splash screen finally appears. Logic Pro is loaded after 2 minutes and 20 seconds. I could boot my whole Mac 4x in that timeframe.To everybody having this problem. I found out what the culprit was. As a documentation here is what it was.
I read some posts here on the forums that mounted USB sticks or flash cards would make Aperture super slow while importing photos. I have Boot Camp installed and have a Windows 7 partition on the same drive as my MacOS. So, out of curiosity, I forced it to unmount as the partition automatically gets mounted by the OS.
Voilà! That seems to have been the culprit! Now both Aperture and Logic (which also had to think 2 minutes before it decided to start) display the splash screen in seconds and start like they are supposed to.
Make sure you have no drives mounted when starting these applications. This helped bringing down the starting time from 2 minutes and 20 seconds to just a few seconds. Of course, if you have your library on another drive you have to have it mounted. Maybe it only takes so long when you have Boot Camp and an NTFS partition. But if you experience lags starting these apps, try unmounting what you don't need. -
since I did an upgrade yesterday (sept 20th 12) my macbook crashed and does an autoantic restart when doing a upgrade. It occurs doing so for iPhoto, MSoffice or Aperture.
Can someone help me on this issue?My late 2009 13" Macbook is now very laggy. For example, the cursor won't respond until many seconds after I place a finger on the touchpad. When I use the keyboard to increase or decrease volume or screen brightness, there is a noticeable lag between my inputs and what I see. Every time I pause between typing words, I find the keyboard won't respond until I wait a few more seconds. This is very disappointing. I need to roll back until Apple are able to look into any potential issues. I didn't have any such problems prior to upgrade.
-
Can i make Aperture run faster ?
To help those struggling to understand why their computer is running Aperture slowly, let me add a few thoughts to help out. I've been using the application since 1.0, bought a G5 quad to run it (launched on same day) with the stock video card. My Photographic interest was Landscape and macro work in film (hobby) and been using digital since 94 and now turned Pro adding Portrats and Weddings to my interest.
How do i run Aperture at a decent speed ?
1. Invest in good hardware. In any of Apple's product line max-out the graphics card option (except perhaps expensive Quadro fx4500), max out CPU option then the RAM. Invest as much as possible in the non-upgradeable components. Over time you can add more ram, but don't underestimate the importance of RAM in OSX. Keep your boot/application and data drives below 70% capacity as above this they start to slow down.
2. Use the vaults and backup the library (don't forget any referenced images).
3. When editing images, don't whang the sliders freely left to right. Be a crafstman, use the number adjustment arrows, with the modifier keys for fine tunng SHIFT and ALT. This is faster.
4. If an image has a lot of spot'n'patches, do this first before any other adjustments (or untick their box in the HUD). Similarly for strighten, do this before H&S or exposure mods.
5. Switch off previews, for marginal improvements.
6. Don't use full-screen mode, its lovely, but with my awful graphic card it kills it when adjusting. Remove the projects window W and control bar D. Toggle the adjustments with I. Real estate is arranged better with the browser on LHS.
7. Try culling the rejects with the viewer off V and maximise the thumbnail size. Suprisingly fast and effective when only going for rejects.
8. After culling use the auto stack feature to reduce the number of images your viewing into 'like' shots. Helps when choosing your story for output.
9. Setup some presets for varying degrees of edge sharpen and White balance as this helps get you get in the vacinity of where you want the adjustment. eg. I have five increasing degrees of edge sharpening intensity and six white balance settings (daylight, cloudy, shade, flash, tungsten, flourescent) which gets me closer to a good WB faster than playing with multiple sliders.
10. Learn the keyboard shortcut.
11. Use Aperture feedback. If your unsatisfied with anything then tell apple as well as the forums. So far we have seen big improvements in Aperture, some were really alpha/beta issues but it is clear Apple is serious about investing in this young Application. I hope they invest in the pixel-pushing, local editing, masks and layers abilities, but do it true to an intuitave workflow platform that Aperture has become.
12. RTFM as well as buy a book - invest in your skills, become better, faster and ultimately more productive.
13. Don't believe in bad luck !
The reason for Aperture running sluggish when using specific adjustments is because i need to upgrade my video card. Fortunately, i can, but might invest in a MP for more storage.If You go to the Aperture site page for basic requirements needed to run it, It will state a Powerbook in fairly basic design will run the Application.
And before I purchased Aperture, and as you can see I updated my RAM to 2 GB.
I ordered this laptop with the top line of all hardware possible.
So I could run also run a 20" screen.
And no, I didn't pack the 20" in my suitcase.
It's amazing how far you have to make sure people don't take one word and run with it.
Not ONLY Aperture, but DDP (Digital Photo Professional), as I hate when people only use abbreviations for everything, and the person trying to learn something is slammed out the door for even looking.
But both applications run pig azz slow. So much so, and I also use the Activity Monitor to keep watch over things in realtime.
When things run this slow to the point you can't see a live change in the view,
You don't learn much, and you can't complete a simple project.
Like one person suggested earlier, just tweak the image one mark at a time.
Well hey, we don't have 6 hours to make one adjustment.
The processor is running at 100% and never backs off till you kill the application.
Making the move from Canon G5, to a Canon 30D and a few thou in lenses, is about the biggest joke while in Europe. Yea, drag all this stuff you don't see to Europe, with 2 portable hard drives to keep the Mac hard drive happy.
It all adds up to roughly a $7000 dollar mistake.
The ads are a total farce. Get this, and do stuff beyond the norm.
Yea Right, like your going to bring a G5 tower in a suitcase.
Oh sure, I'll struggle with the software till get through with 20 images, and
what if you have 300?
Now, one question... Who's next , as far as an application that runs RAW images with no lag. With out all the BS.
Power Book G4-1.67-2GB, Bluetooth Mouse & Keys Mac OS X (10.4.8) 20" screen for dual view. -
Lag/Pause believed to be caused by RAID [SOLVED]
I have installed arch about 4 months back and ever since been experience and Lag/Freezing issue which occurs anywhere from 1-30 seconds at a time. I have been looking for solutions and fixing issues I have found with my system in order to find a solution. It does not seem to be any issue with the hardware, everything is new. I have even gone so far as to swapping out certain parts such as the memory and have even updated the bios firmware.
I believe this is an issue with the way the raid is setup, as harddrive I/O will cease when this happens. If there is something else that may be causeing this issue then I am unsure what it could be.
I have posted my dmesg, mdstat and mdadm.conf files below. Also my system is still experience two bugs. The first one is the RAID initalization failed message durring systm initialization even though the raid array was assembled fine by the kernel. And the other on is the error message from LVM2 durring initalization "File-based locking initialisation failed". That error has supposively been fixed from an update though I am still getting it.
dmesg
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 2.6.33-ARCH (thomas@evey) (gcc version 4.5.0 (GCC) ) #1 SMP PREEMPT Mon Apr 26 19:31:00 CEST 2010
Command line: root=/dev/array/root ro
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 00000000cfbe0000 (usable)
BIOS-e820: 00000000cfbe0000 - 00000000cfbe1000 (ACPI NVS)
BIOS-e820: 00000000cfbe1000 - 00000000cfbf0000 (ACPI data)
BIOS-e820: 00000000cfbf0000 - 00000000cfc00000 (reserved)
BIOS-e820: 00000000f4000000 - 00000000f8000000 (reserved)
BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
BIOS-e820: 0000000100000000 - 0000000130000000 (usable)
NX (Execute Disable) protection: active
DMI 2.4 present.
No AGP bridge found
last_pfn = 0x130000 max_arch_pfn = 0x400000000
MTRR default type: uncachable
MTRR fixed ranges enabled:
00000-9FFFF write-back
A0000-BFFFF uncachable
C0000-CCFFF write-protect
CD000-EFFFF uncachable
F0000-FFFFF write-through
MTRR variable ranges enabled:
0 base 000000000 mask F00000000 write-back
1 base 0E0000000 mask FE0000000 uncachable
2 base 0D0000000 mask FF0000000 uncachable
3 base 100000000 mask FC0000000 write-back
4 base 130000000 mask FF0000000 uncachable
5 disabled
6 disabled
7 disabled
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
e820 update range: 00000000d0000000 - 0000000100000000 (usable) ==> (reserved)
last_pfn = 0xcfbe0 max_arch_pfn = 0x400000000
e820 update range: 0000000000001000 - 0000000000010000 (usable) ==> (reserved)
Scanning 1 areas for low memory corruption
modified physical RAM map:
modified: 0000000000000000 - 0000000000001000 (usable)
modified: 0000000000001000 - 0000000000010000 (reserved)
modified: 0000000000010000 - 000000000009f800 (usable)
modified: 000000000009f800 - 00000000000a0000 (reserved)
modified: 00000000000f0000 - 0000000000100000 (reserved)
modified: 0000000000100000 - 00000000cfbe0000 (usable)
modified: 00000000cfbe0000 - 00000000cfbe1000 (ACPI NVS)
modified: 00000000cfbe1000 - 00000000cfbf0000 (ACPI data)
modified: 00000000cfbf0000 - 00000000cfc00000 (reserved)
modified: 00000000f4000000 - 00000000f8000000 (reserved)
modified: 00000000fec00000 - 0000000100000000 (reserved)
modified: 0000000100000000 - 0000000130000000 (usable)
initial memory mapped : 0 - 20000000
found SMP MP-table at [ffff8800000f5630] f5630
init_memory_mapping: 0000000000000000-00000000cfbe0000
0000000000 - 00cfa00000 page 2M
00cfa00000 - 00cfbe0000 page 4k
kernel direct mapping tables up to cfbe0000 @ 16000-1c000
init_memory_mapping: 0000000100000000-0000000130000000
0100000000 - 0130000000 page 2M
kernel direct mapping tables up to 130000000 @ 1a000-20000
RAMDISK: 37d4d000 - 37feff2b
ACPI: RSDP 00000000000f6ff0 00014 (v00 GBT )
ACPI: RSDT 00000000cfbe1040 00040 (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
ACPI: FACP 00000000cfbe10c0 00074 (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
ACPI: DSDT 00000000cfbe1180 042C4 (v01 GBT GBTUACPI 00001000 MSFT 0100000C)
ACPI: FACS 00000000cfbe0000 00040
ACPI: HPET 00000000cfbe55c0 00038 (v01 GBT GBTUACPI 42302E31 GBTU 00000098)
ACPI: MCFG 00000000cfbe5640 0003C (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
ACPI: EUDS 00000000cfbe5680 00560 (v01 GBT 00000000 00000000)
ACPI: TAMG 00000000cfbe5be0 00A32 (v01 GBT GBT B0 5455312E BG?? 53450101)
ACPI: APIC 00000000cfbe54c0 000BC (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
ACPI: SSDT 00000000cfbe6640 02F8C (v01 INTEL PPM RCM 80000001 INTL 20061109)
ACPI: Local APIC address 0xfee00000
(13 early reservations) ==> bootmem [0000000000 - 0130000000]
#0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
#1 [0001000000 - 00016d6b38] TEXT DATA BSS ==> [0001000000 - 00016d6b38]
#2 [0037d4d000 - 0037feff2b] RAMDISK ==> [0037d4d000 - 0037feff2b]
#3 [00016d7000 - 00016d70f6] BRK ==> [00016d7000 - 00016d70f6]
#4 [00000f5640 - 0000100000] BIOS reserved ==> [00000f5640 - 0000100000]
#5 [00000f5630 - 00000f5640] MP-table mpf ==> [00000f5630 - 00000f5640]
#6 [000009f800 - 00000f0d00] BIOS reserved ==> [000009f800 - 00000f0d00]
#7 [00000f0edc - 00000f5630] BIOS reserved ==> [00000f0edc - 00000f5630]
#8 [00000f0d00 - 00000f0edc] MP-table mpc ==> [00000f0d00 - 00000f0edc]
#9 [0000010000 - 0000012000] TRAMPOLINE ==> [0000010000 - 0000012000]
#10 [0000012000 - 0000016000] ACPI WAKEUP ==> [0000012000 - 0000016000]
#11 [0000016000 - 000001a000] PGTABLE ==> [0000016000 - 000001a000]
#12 [000001a000 - 000001b000] PGTABLE ==> [000001a000 - 000001b000]
[ffffea0000000000-ffffea00043fffff] PMD -> [ffff880001800000-ffff8800051fffff] on node 0
Zone PFN ranges:
DMA 0x00000000 -> 0x00001000
DMA32 0x00001000 -> 0x00100000
Normal 0x00100000 -> 0x00130000
Movable zone start PFN for each node
early_node_map[4] active PFN ranges
0: 0x00000000 -> 0x00000001
0: 0x00000010 -> 0x0000009f
0: 0x00000100 -> 0x000cfbe0
0: 0x00100000 -> 0x00130000
On node 0 totalpages: 1047408
DMA zone: 56 pages used for memmap
DMA zone: 107 pages reserved
DMA zone: 3821 pages, LIFO batch:0
DMA32 zone: 14280 pages used for memmap
DMA32 zone: 832536 pages, LIFO batch:31
Normal zone: 2688 pages used for memmap
Normal zone: 193920 pages, LIFO batch:31
ACPI: PM-Timer IO Port: 0x408
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x02] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] enabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x05] lapic_id[0x03] enabled)
ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled)
ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled)
ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x04] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x05] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x06] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x07] dfl dfl lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a201 base: 0xfed00000
SMP: Allowing 8 CPUs, 0 hotplug CPUs
nr_irqs_gsi: 24
PM: Registered nosave memory: 0000000000001000 - 0000000000010000
PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
PM: Registered nosave memory: 00000000cfbe0000 - 00000000cfbe1000
PM: Registered nosave memory: 00000000cfbe1000 - 00000000cfbf0000
PM: Registered nosave memory: 00000000cfbf0000 - 00000000cfc00000
PM: Registered nosave memory: 00000000cfc00000 - 00000000f4000000
PM: Registered nosave memory: 00000000f4000000 - 00000000f8000000
PM: Registered nosave memory: 00000000f8000000 - 00000000fec00000
PM: Registered nosave memory: 00000000fec00000 - 0000000100000000
Allocating PCI resources starting at cfc00000 (gap: cfc00000:24400000)
Booting paravirtualized kernel on bare hardware
setup_percpu: NR_CPUS:16 nr_cpumask_bits:16 nr_cpu_ids:8 nr_node_ids:1
PERCPU: Embedded 29 pages/cpu @ffff880005400000 s89176 r8192 d21416 u262144
pcpu-alloc: s89176 r8192 d21416 u262144 alloc=1*2097152
pcpu-alloc: [0] 0 1 2 3 4 5 6 7
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1030277
Kernel command line: root=/dev/array/root ro
PID hash table entries: 4096 (order: 3, 32768 bytes)
Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Checking aperture...
No AGP bridge found
Calgary: detecting Calgary via BIOS EBDA area
Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Memory: 4046176k/4980736k available (3449k kernel code, 791104k absent, 142528k reserved, 1818k data, 480k init)
SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:768
Console: colour VGA+ 80x25
console [tty0] enabled
allocated 41943040 bytes of page_cgroup
please try 'cgroup_disable=memory' option if you don't want memory cgroups
hpet clockevent registered
Fast TSC calibration using PIT
Detected 1998.531 MHz processor.
Calibrating delay loop (skipped), value calculated using timer frequency.. 3998.60 BogoMIPS (lpj=6661770)
Security Framework initialized
Mount-cache hash table entries: 256
Initializing cgroup subsys ns
Initializing cgroup subsys cpuacct
Initializing cgroup subsys memory
Initializing cgroup subsys devices
Initializing cgroup subsys freezer
Initializing cgroup subsys net_cls
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
mce: CPU supports 9 MCE banks
CPU0: Thermal monitoring enabled (TM1)
CPU 0 MCA banks CMCI:2 CMCI:3 CMCI:5 CMCI:6 CMCI:8
using mwait in idle threads.
Performance Events: Nehalem/Corei7 events, Intel PMU driver.
... version: 3
... bit width: 48
... generic registers: 4
... value mask: 0000ffffffffffff
... max period: 000000007fffffff
... fixed-purpose events: 3
... event mask: 000000070000000f
ACPI: Core revision 20091214
Setting APIC routing to flat
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
CPU0: Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz stepping 05
Booting Node 0, Processors #1
CPU 1 MCA banks CMCI:2 CMCI:3 CMCI:5 SHD:6 SHD:8
#2
CPU 2 MCA banks CMCI:2 CMCI:3 CMCI:5 SHD:6 SHD:8
#3
CPU 3 MCA banks CMCI:2 CMCI:3 CMCI:5 SHD:6 SHD:8
#4
CPU 4 MCA banks SHD:2 SHD:3 SHD:5 SHD:6 SHD:8
#5
CPU 5 MCA banks SHD:2 SHD:3 SHD:5 SHD:6 SHD:8
#6
CPU 6 MCA banks SHD:2 SHD:3 SHD:5 SHD:6 SHD:8
#7 Ok.
CPU 7 MCA banks SHD:2 SHD:3 SHD:5 SHD:6 SHD:8
Brought up 8 CPUs
Total of 8 processors activated (31988.63 BogoMIPS).
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf4000000-0xf7ffffff] (base 0xf4000000)
PCI: MMCONFIG at [mem 0xf4000000-0xf7ffffff] reserved in E820
PCI: Using configuration type 1 for base access
bio: create slab <bio-0> at 0
ACPI: EC: Look up EC in DSDT
ACPI: Interpreter enabled
ACPI: (supports S0 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI Warning: Incorrect checksum in table [TAMG] - 10, should be 0F (20091214/tbutils-314)
ACPI: No dock devices found.
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci_root PNP0A03:00: ignoring host bridge windows from ACPI; boot with "pci=use_crs" to use them
pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7] (ignored)
pci_root PNP0A03:00: host bridge window [io 0x0d00-0xffff] (ignored)
pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff] (ignored)
pci_root PNP0A03:00: host bridge window [mem 0x000c0000-0x000dffff] (ignored)
pci_root PNP0A03:00: host bridge window [mem 0xcfc00000-0xfebfffff] (ignored)
pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
pci 0000:00:03.0: PME# disabled
pci 0000:00:1a.0: reg 20: [io 0xff00-0xff1f]
pci 0000:00:1a.1: reg 20: [io 0xfe00-0xfe1f]
pci 0000:00:1a.2: reg 20: [io 0xfd00-0xfd1f]
pci 0000:00:1a.7: reg 10: [mem 0xfbfff000-0xfbfff3ff]
pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1a.7: PME# disabled
pci 0000:00:1b.0: reg 10: [mem 0xfbff8000-0xfbffbfff 64bit]
pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1b.0: PME# disabled
pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.0: PME# disabled
pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.1: PME# disabled
pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.2: PME# disabled
pci 0000:00:1d.0: reg 20: [io 0xfc00-0xfc1f]
pci 0000:00:1d.1: reg 20: [io 0xfb00-0xfb1f]
pci 0000:00:1d.2: reg 20: [io 0xfa00-0xfa1f]
pci 0000:00:1d.3: reg 20: [io 0xf900-0xf91f]
pci 0000:00:1d.7: reg 10: [mem 0xfbffe000-0xfbffe3ff]
pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.7: PME# disabled
pci 0000:00:1f.2: reg 10: [io 0xf800-0xf807]
pci 0000:00:1f.2: reg 14: [io 0xf700-0xf703]
pci 0000:00:1f.2: reg 18: [io 0xf600-0xf607]
pci 0000:00:1f.2: reg 1c: [io 0xf500-0xf503]
pci 0000:00:1f.2: reg 20: [io 0xf400-0xf40f]
pci 0000:00:1f.2: reg 24: [io 0xf300-0xf30f]
pci 0000:00:1f.3: reg 10: [mem 0xfbffd000-0xfbffd0ff 64bit]
pci 0000:00:1f.3: reg 20: [io 0x0500-0x051f]
pci 0000:00:1f.5: reg 10: [io 0xf100-0xf107]
pci 0000:00:1f.5: reg 14: [io 0xf000-0xf003]
pci 0000:00:1f.5: reg 18: [io 0xef00-0xef07]
pci 0000:00:1f.5: reg 1c: [io 0xee00-0xee03]
pci 0000:00:1f.5: reg 20: [io 0xed00-0xed0f]
pci 0000:00:1f.5: reg 24: [io 0xec00-0xec0f]
pci 0000:01:00.0: reg 10: [mem 0xf9000000-0xf9ffffff]
pci 0000:01:00.0: reg 14: [mem 0xd0000000-0xdfffffff 64bit pref]
pci 0000:01:00.0: reg 1c: [mem 0xee000000-0xefffffff 64bit pref]
pci 0000:01:00.0: reg 24: [io 0xcf00-0xcf7f]
pci 0000:01:00.0: reg 30: [mem 0x00000000-0x0007ffff pref]
pci 0000:01:00.1: reg 10: [mem 0xfaffc000-0xfaffffff]
pci 0000:00:03.0: PCI bridge to [bus 01-01]
pci 0000:00:03.0: bridge window [io 0xc000-0xcfff]
pci 0000:00:03.0: bridge window [mem 0xf9000000-0xfaffffff]
pci 0000:00:03.0: bridge window [mem 0xd0000000-0xefffffff 64bit pref]
pci 0000:02:00.0: reg 10: [io 0xaf00-0xaf07]
pci 0000:02:00.0: reg 14: [io 0xae00-0xae03]
pci 0000:02:00.0: reg 18: [io 0xad00-0xad07]
pci 0000:02:00.0: reg 1c: [io 0xac00-0xac03]
pci 0000:02:00.0: reg 20: [io 0xab00-0xab0f]
pci 0000:02:00.0: reg 24: [mem 0xfbcff000-0xfbcff7ff]
pci 0000:02:00.0: reg 30: [mem 0x00000000-0x0000ffff pref]
pci 0000:02:00.0: PME# supported from D3hot
pci 0000:02:00.0: PME# disabled
pci 0000:00:1c.0: PCI bridge to [bus 02-02]
pci 0000:00:1c.0: bridge window [io 0xa000-0xafff]
pci 0000:00:1c.0: bridge window [mem 0xfbc00000-0xfbcfffff]
pci 0000:03:00.0: reg 10: [io 0xde00-0xdeff]
pci 0000:03:00.0: reg 18: [mem 0xfbeff000-0xfbefffff 64bit pref]
pci 0000:03:00.0: reg 20: [mem 0xfbef8000-0xfbefbfff 64bit pref]
pci 0000:03:00.0: reg 30: [mem 0x00000000-0x0001ffff pref]
pci 0000:03:00.0: supports D1 D2
pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:03:00.0: PME# disabled
pci 0000:00:1c.1: PCI bridge to [bus 03-03]
pci 0000:00:1c.1: bridge window [io 0xd000-0xdfff]
pci 0000:00:1c.1: bridge window [mem 0xfbb00000-0xfbbfffff]
pci 0000:00:1c.1: bridge window [mem 0xfbe00000-0xfbefffff 64bit pref]
pci 0000:04:00.0: reg 10: [mem 0xfbdfe000-0xfbdfffff 64bit]
pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
pci 0000:04:00.0: PME# disabled
pci 0000:00:1c.2: PCI bridge to [bus 04-04]
pci 0000:00:1c.2: bridge window [mem 0xfbd00000-0xfbdfffff]
pci 0000:05:05.0: reg 10: [io 0xbf00-0xbf07]
pci 0000:05:05.0: reg 14: [io 0xbe00-0xbe03]
pci 0000:05:05.0: reg 18: [io 0xbd00-0xbd07]
pci 0000:05:05.0: reg 1c: [io 0xbc00-0xbc03]
pci 0000:05:05.0: reg 20: [io 0xbb00-0xbb0f]
pci 0000:00:1e.0: PCI bridge to [bus 05-05] (subtractive decode)
pci 0000:00:1e.0: bridge window [io 0xb000-0xbfff]
pci_bus 0000:00: on NUMA node 0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX1._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 11 *12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs *3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
vgaarb: loaded
PCI: Using ACPI for IRQ routing
PCI: pci_cache_line_size set to 64 bytes
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
HPET: 8 timers in total, 5 timers will be used for per-cpu timer
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 24, 25, 26, 27, 28, 0
hpet0: 8 comparators, 64-bit 14.318180 MHz counter
hpet: hpet2 irq 24 for MSI
hpet: hpet3 irq 25 for MSI
hpet: hpet4 irq 26 for MSI
hpet: hpet5 irq 27 for MSI
hpet: hpet6 irq 28 for MSI
Switching to clocksource tsc
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 14 devices
ACPI: ACPI bus type pnp unregistered
system 00:01: [io 0x04d0-0x04d1] has been reserved
system 00:01: [io 0x0290-0x029f] has been reserved
system 00:01: [io 0x0800-0x087f] has been reserved
system 00:01: [io 0x0290-0x0294] has been reserved
system 00:01: [io 0x0880-0x088f] has been reserved
system 00:0a: [io 0x0400-0x04cf] has been reserved
system 00:0a: [io 0x04d2-0x04ff] has been reserved
system 00:0b: [mem 0xf4000000-0xf7ffffff] has been reserved
system 00:0c: [mem 0x000cd600-0x000cffff] has been reserved
system 00:0c: [mem 0x000f0000-0x000f7fff] could not be reserved
system 00:0c: [mem 0x000f8000-0x000fbfff] could not be reserved
system 00:0c: [mem 0x000fc000-0x000fffff] could not be reserved
system 00:0c: [mem 0xcfbe0000-0xcfbeffff] could not be reserved
system 00:0c: [mem 0x00000000-0x0009ffff] could not be reserved
system 00:0c: [mem 0x00100000-0xcfbdffff] could not be reserved
system 00:0c: [mem 0xcfbf0000-0xcfbfffff] has been reserved
system 00:0c: [mem 0xfec00000-0xfec00fff] could not be reserved
system 00:0c: [mem 0xfed10000-0xfed1dfff] has been reserved
system 00:0c: [mem 0xfed20000-0xfed8ffff] has been reserved
system 00:0c: [mem 0xfee00000-0xfee00fff] has been reserved
system 00:0c: [mem 0xffb00000-0xffb7ffff] has been reserved
system 00:0c: [mem 0xfff00000-0xffffffff] has been reserved
system 00:0c: [mem 0x000e0000-0x000effff] has been reserved
pci 0000:00:1c.0: BAR 15: assigned [mem 0xf0000000-0xf01fffff pref]
pci 0000:00:1c.2: BAR 15: assigned [mem 0xf0200000-0xf03fffff 64bit pref]
pci 0000:00:1c.2: BAR 13: assigned [io 0x1000-0x1fff]
pci 0000:01:00.0: BAR 6: assigned [mem 0xe0000000-0xe007ffff pref]
pci 0000:00:03.0: PCI bridge to [bus 01-01]
pci 0000:00:03.0: bridge window [io 0xc000-0xcfff]
pci 0000:00:03.0: bridge window [mem 0xf9000000-0xfaffffff]
pci 0000:00:03.0: bridge window [mem 0xd0000000-0xefffffff 64bit pref]
pci 0000:02:00.0: BAR 6: assigned [mem 0xf0000000-0xf000ffff pref]
pci 0000:00:1c.0: PCI bridge to [bus 02-02]
pci 0000:00:1c.0: bridge window [io 0xa000-0xafff]
pci 0000:00:1c.0: bridge window [mem 0xfbc00000-0xfbcfffff]
pci 0000:00:1c.0: bridge window [mem 0xf0000000-0xf01fffff pref]
pci 0000:03:00.0: BAR 6: assigned [mem 0xfbe00000-0xfbe1ffff pref]
pci 0000:00:1c.1: PCI bridge to [bus 03-03]
pci 0000:00:1c.1: bridge window [io 0xd000-0xdfff]
pci 0000:00:1c.1: bridge window [mem 0xfbb00000-0xfbbfffff]
pci 0000:00:1c.1: bridge window [mem 0xfbe00000-0xfbefffff 64bit pref]
pci 0000:00:1c.2: PCI bridge to [bus 04-04]
pci 0000:00:1c.2: bridge window [io 0x1000-0x1fff]
pci 0000:00:1c.2: bridge window [mem 0xfbd00000-0xfbdfffff]
pci 0000:00:1c.2: bridge window [mem 0xf0200000-0xf03fffff 64bit pref]
pci 0000:00:1e.0: PCI bridge to [bus 05-05]
pci 0000:00:1e.0: bridge window [io 0xb000-0xbfff]
pci 0000:00:1e.0: bridge window [mem disabled]
pci 0000:00:1e.0: bridge window [mem pref disabled]
pci 0000:00:03.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:03.0: setting latency timer to 64
pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:1c.0: setting latency timer to 64
pci 0000:00:1c.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
pci 0000:00:1c.1: setting latency timer to 64
pci 0000:00:1c.2: enabling device (0006 -> 0007)
pci 0000:00:1c.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
pci 0000:00:1c.2: setting latency timer to 64
pci 0000:00:1e.0: setting latency timer to 64
pci_bus 0000:00: resource 0 [io 0x0000-0xffff]
pci_bus 0000:00: resource 1 [mem 0x00000000-0xffffffffffffffff]
pci_bus 0000:01: resource 0 [io 0xc000-0xcfff]
pci_bus 0000:01: resource 1 [mem 0xf9000000-0xfaffffff]
pci_bus 0000:01: resource 2 [mem 0xd0000000-0xefffffff 64bit pref]
pci_bus 0000:02: resource 0 [io 0xa000-0xafff]
pci_bus 0000:02: resource 1 [mem 0xfbc00000-0xfbcfffff]
pci_bus 0000:02: resource 2 [mem 0xf0000000-0xf01fffff pref]
pci_bus 0000:03: resource 0 [io 0xd000-0xdfff]
pci_bus 0000:03: resource 1 [mem 0xfbb00000-0xfbbfffff]
pci_bus 0000:03: resource 2 [mem 0xfbe00000-0xfbefffff 64bit pref]
pci_bus 0000:04: resource 0 [io 0x1000-0x1fff]
pci_bus 0000:04: resource 1 [mem 0xfbd00000-0xfbdfffff]
pci_bus 0000:04: resource 2 [mem 0xf0200000-0xf03fffff 64bit pref]
pci_bus 0000:05: resource 0 [io 0xb000-0xbfff]
pci_bus 0000:05: resource 3 [io 0x0000-0xffff]
pci_bus 0000:05: resource 4 [mem 0x00000000-0xffffffffffffffff]
NET: Registered protocol family 2
IP route cache hash table entries: 131072 (order: 8, 1048576 bytes)
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
UDP hash table entries: 2048 (order: 4, 65536 bytes)
UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
NET: Registered protocol family 1
pci 0000:01:00.0: Boot video device
PCI: CLS 64 bytes, default 64
Unpacking initramfs...
Freeing initrd memory: 2699k freed
PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Placing 64MB software IO TLB between ffff880005bdd000 - ffff880009bdd000
software IO TLB at phys 0x5bdd000 - 0x9bdd000
Scanning for low memory corruption every 60 seconds
audit: initializing netlink socket (disabled)
type=2000 audit(1272807521.273:1): initialized
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
msgmni has been set to 7909
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
pcieport 0000:00:03.0: setting latency timer to 64
pcieport 0000:00:03.0: irq 29 for MSI/MSI-X
pcieport 0000:00:1c.0: setting latency timer to 64
pcieport 0000:00:1c.0: irq 30 for MSI/MSI-X
pcieport 0000:00:1c.1: setting latency timer to 64
pcieport 0000:00:1c.1: irq 31 for MSI/MSI-X
pcieport 0000:00:1c.2: setting latency timer to 64
pcieport 0000:00:1c.2: irq 32 for MSI/MSI-X
aer 0000:00:03.0:pcie02: AER service couldn't init device: no _OSC support
Linux agpgart interface v0.103
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
input: Macintosh mouse button emulation as /devices/virtual/input/input0
PNP: No PS/2 controller found. Probing ports directly.
Failed to disable AUX port, but continuing anyway... Is this a SiS?
If AUX port is really absent please use the 'i8042.noaux' option.
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
cpuidle: using governor ladder
cpuidle: using governor menu
TCP cubic registered
NET: Registered protocol family 17
PM: Resume from disk failed.
registered taskstats version 1
Initalizing network drop monitor service
Freeing unused kernel memory: 480k freed
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.17.0-ioctl (2010-03-05) initialised: [email protected]
SCSI subsystem initialized
libata version 3.00 loaded.
pata_it8213 0000:05:05.0: version 0.0.3
pata_it8213 0000:05:05.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
pata_it8213 0000:05:05.0: setting latency timer to 64
scsi0 : pata_it8213
scsi1 : pata_it8213
ata1: PATA max UDMA/66 cmd 0xbf00 ctl 0xbe00 bmdma 0xbb00 irq 19
ata2: DUMMY
ata_piix 0000:00:1f.2: version 2.13
ata_piix 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
ata_piix 0000:00:1f.2: setting latency timer to 64
scsi2 : ata_piix
scsi3 : ata_piix
ata3: SATA max UDMA/133 cmd 0xf800 ctl 0xf700 bmdma 0xf400 irq 19
ata4: SATA max UDMA/133 cmd 0xf600 ctl 0xf500 bmdma 0xf408 irq 19
ata_piix 0000:00:1f.5: PCI INT B -> GSI 19 (level, low) -> IRQ 19
ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
ata_piix 0000:00:1f.5: setting latency timer to 64
scsi4 : ata_piix
scsi5 : ata_piix
ata5: SATA max UDMA/133 cmd 0xf100 ctl 0xf000 bmdma 0xed00 irq 19
ata6: SATA max UDMA/133 cmd 0xef00 ctl 0xee00 bmdma 0xed08 irq 19
ata6: SATA link down (SStatus 0 SControl 300)
ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata5.00: ATAPI: HL-DT-ST BDDVDRW CH08LS10, 1.00, max UDMA/133
ata5.00: configured for UDMA/133
ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.01: SATA link down (SStatus 0 SControl 300)
ata4.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata4.01: SATA link down (SStatus 0 SControl 300)
ata3.00: ATA-8: WDC WD15EARS-00Z5B1, 80.00A80, max UDMA/133
ata3.00: 2930277168 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata3.00: configured for UDMA/133
scsi 2:0:0:0: Direct-Access ATA WDC WD15EARS-00Z 80.0 PQ: 0 ANSI: 5
ata4.00: ATA-8: WDC WD15EARS-00Z5B1, 80.00A80, max UDMA/133
ata4.00: 2930277168 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata4.00: configured for UDMA/133
scsi 3:0:0:0: Direct-Access ATA WDC WD15EARS-00Z 80.0 PQ: 0 ANSI: 5
scsi 4:0:0:0: CD-ROM HL-DT-ST BDDVDRW CH08LS10 1.00 PQ: 0 ANSI: 5
sd 2:0:0:0: [sda] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
sd 3:0:0:0: [sdb] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
sd 3:0:0:0: [sdb] Write Protect is off
sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdb:
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 sda2 sda3
sd 2:0:0:0: [sda] Attached SCSI disk
sdb1 sdb2 sdb3
sd 3:0:0:0: [sdb] Attached SCSI disk
sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 4:0:0:0: Attached scsi CD-ROM sr0
md: md0 stopped.
md: bind<sdb1>
md: bind<sda1>
md: raid1 personality registered for level 1
raid1: raid set md0 active with 2 out of 2 mirrors
md0: detected capacity change from 0 to 295960576
md0: unknown partition table
md: md1 stopped.
md: bind<sdb2>
md: bind<sda2>
raid1: raid set md1 active with 2 out of 2 mirrors
md1: detected capacity change from 0 to 1497954975744
md1: unknown partition table
md: md2 stopped.
md: bind<sdb3>
md: bind<sda3>
raid1: raid set md2 active with 2 out of 2 mirrors
md2: detected capacity change from 0 to 2048000000
md2: unknown partition table
EXT4-fs (dm-0): mounted filesystem with ordered data mode
rtc_cmos 00:04: RTC can wake from S4
rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one month, 242 bytes nvram, hpet irqs
udev: starting version 151
sd 2:0:0:0: Attached scsi generic sg0 type 0
sd 3:0:0:0: Attached scsi generic sg1 type 0
sr 4:0:0:0: Attached scsi generic sg2 type 5
iTCO_vendor_support: vendor-support=0
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.05
iTCO_wdt: Found a P55 TCO device (Version=2, TCOBASE=0x0460)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
Monitor-Mwait will be used to enter C-1 state
Monitor-Mwait will be used to enter C-2 state
Monitor-Mwait will be used to enter C-3 state
ahci 0000:02:00.0: version 3.0
ahci 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
ahci 0000:02:00.0: irq 33 for MSI/MSI-X
ahci 0000:02:00.0: AHCI 0001.0200 32 slots 8 ports 6 Gbps 0xff impl SATA mode
ahci 0000:02:00.0: flags: 64bit ncq pio
ahci 0000:02:00.0: setting latency timer to 64
scsi6 : ahci
scsi7 : ahci
scsi8 : ahci
scsi9 : ahci
scsi10 : ahci
scsi11 : ahci
scsi12 : ahci
scsi13 : ahci
ata7: SATA max UDMA/133 abar m2048@0xfbcff000 port 0xfbcff100 irq 33
ata8: SATA max UDMA/133 abar m2048@0xfbcff000 port 0xfbcff180 irq 33
ata9: SATA max UDMA/133 abar m2048@0xfbcff000 port 0xfbcff200 irq 33
ata10: SATA max UDMA/133 abar m2048@0xfbcff000 port 0xfbcff280 irq 33
ata11: SATA max UDMA/133 abar m2048@0xfbcff000 port 0xfbcff300 irq 33
ata12: SATA max UDMA/133 abar m2048@0xfbcff000 port 0xfbcff380 irq 33
ata13: SATA max UDMA/133 abar m2048@0xfbcff000 port 0xfbcff400 irq 33
ata14: SATA max UDMA/133 abar m2048@0xfbcff000 port 0xfbcff480 irq 33
input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
ACPI: Power Button [PWRB]
input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
ACPI: Power Button [PWRF]
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
ata13: SATA link down (SStatus 0 SControl 300)
ata8: SATA link down (SStatus 0 SControl 300)
ata10: SATA link down (SStatus 0 SControl 300)
ata14: SATA link up <unknown> (SStatus FFFFFF93 SControl 300)
ata9: SATA link down (SStatus 0 SControl 300)
ata12: SATA link down (SStatus 0 SControl 300)
ata11: SATA link down (SStatus 0 SControl 300)
ata7: SATA link down (SStatus 0 SControl 300)
ata14.00: ATAPI: MARVELL VIRTUALL, 1.09, max UDMA/66
ata14.00: configured for UDMA/66
scsi 13:0:0:0: Processor Marvell 91xx Config 1.01 PQ: 0 ANSI: 5
scsi 13:0:0:0: Attached scsi generic sg3 type 3
nvidia: module license 'NVIDIA' taints kernel.
Disabling lock debugging due to kernel taint
parport_pc 00:09: reported by Plug and Play ACPI
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
Floppy drive(s): fd0 is 1.44M
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18
ehci_hcd 0000:00:1a.7: setting latency timer to 64
ehci_hcd 0000:00:1a.7: EHCI Host Controller
ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1a.7: debug port 2
ehci_hcd 0000:00:1a.7: cache line size of 64 is not supported
ehci_hcd 0000:00:1a.7: irq 18, io mem 0xfbfff000
xhci_hcd 0000:04:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
xhci_hcd 0000:04:00.0: setting latency timer to 64
xhci_hcd 0000:04:00.0: xHCI Host Controller
xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 2
xhci_hcd 0000:04:00.0: irq 18, io mem 0xfbdfe000
usb usb2: config 1 interface 0 altsetting 0 endpoint 0x81 has no SuperSpeed companion descriptor
xHCI xhci_add_endpoint called for root hub
xHCI xhci_check_bandwidth called for root hub
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 4 ports detected
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
r8169 0000:03:00.0: setting latency timer to 64
r8169 0000:03:00.0: irq 34 for MSI/MSI-X
eth0: RTL8168d/8111d at 0xffffc90000068000, 6c:f0:49:02:e2:c1, XID 083000c0 IRQ 34
FDC 0 is a post-1991 82077
lp: driver loaded but no devices found
ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
ehci_hcd 0000:00:1d.7: setting latency timer to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 3
ehci_hcd 0000:00:1d.7: debug port 2
ehci_hcd 0000:00:1d.7: cache line size of 64 is not supported
ehci_hcd 0000:00:1d.7: irq 23, io mem 0xfbffe000
uhci_hcd: USB Universal Host Controller Interface driver
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 8 ports detected
i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
uhci_hcd 0000:00:1a.0: setting latency timer to 64
uhci_hcd 0000:00:1a.0: UHCI Host Controller
uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1a.0: irq 16, io base 0x0000ff00
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
uhci_hcd 0000:00:1a.1: setting latency timer to 64
uhci_hcd 0000:00:1a.1: UHCI Host Controller
uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1a.1: irq 21, io base 0x0000fe00
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
uhci_hcd 0000:00:1a.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
uhci_hcd 0000:00:1a.2: setting latency timer to 64
uhci_hcd 0000:00:1a.2: UHCI Host Controller
uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 6
uhci_hcd 0000:00:1a.2: irq 18, io base 0x0000fd00
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
uhci_hcd 0000:00:1d.0: setting latency timer to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 7
uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000fc00
hub 7-0:1.0: USB hub found
hub 7-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
uhci_hcd 0000:00:1d.1: setting latency timer to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 8
uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000fb00
hub 8-0:1.0: USB hub found
hub 8-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
uhci_hcd 0000:00:1d.2: setting latency timer to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 9
uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000fa00
hub 9-0:1.0: USB hub found
hub 9-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.3: PCI INT D -> GSI 16 (level, low) -> IRQ 16
uhci_hcd 0000:00:1d.3: setting latency timer to 64
uhci_hcd 0000:00:1d.3: UHCI Host Controller
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 10
uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000f900
hub 10-0:1.0: USB hub found
hub 10-0:1.0: 2 ports detected
ppdev: user-space parallel port driver
lp0: using parport0 (interrupt-driven).
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
HDA Intel 0000:00:1b.0: irq 35 for MSI/MSI-X
HDA Intel 0000:00:1b.0: setting latency timer to 64
input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input3
HDA Intel 0000:01:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
hda_intel: Disable MSI for Nvidia chipset
HDA Intel 0000:01:00.1: setting latency timer to 64
usb 9-2: new low speed USB device using uhci_hcd and address 2
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nvidia 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
nvidia 0000:01:00.0: setting latency timer to 64
vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
NVRM: loading NVIDIA UNIX x86_64 Kernel Module 195.36.15 Fri Mar 12 00:29:13 PST 2010
input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.2/usb9/9-2/9-2:1.0/input/input4
logitech 0003:046D:C517.0001: input,hidraw0: USB HID v1.10 Keyboard [Logitech USB Receiver] on usb-0000:00:1d.2-2/input0
logitech 0003:046D:C517.0002: fixing up Logitech keyboard report descriptor
input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.2/usb9/9-2/9-2:1.1/input/input5
logitech 0003:046D:C517.0002: input,hiddev0,hidraw1: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:1d.2-2/input1
kjournald starting. Commit interval 5 seconds
EXT3-fs (md0): using internal journal
EXT3-fs (md0): mounted filesystem with writeback data mode
Adding 1999992k swap on /dev/md2. Priority:-1 extents:1 across:1999992k
r8169: eth0: link up
r8169: eth0: link up
it87: Found IT8720F chip at 0x290, revision 8
it87: VID is disabled (pins used for GPIO)
it87: in3 is VCC (+5V)
fuse init (API version 7.13)
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
/etc/mdadm.conf
ARRAY /dev/md0 metadata=0.90 UUID=d3dade34:d68c8182:644d3026:471d4918
ARRAY /dev/md1 metadata=0.90 UUID=c8e3ea5d:7be896ac:a45d145b:781c14fa
ARRAY /dev/md2 metadata=0.90 UUID=5c868358:21748aa6:5b20e486:491c0ca6
# Emails sent on faults
MAILADDR [myemailaddress]
/proc/mdstat
Personalities : [raid1]
md2 : active raid1 sda3[0] sdb3[1]
2000000 blocks [2/2] [UU]
md1 : active raid1 sda2[0] sdb2[1]
1462846656 blocks [2/2] [UU]
md0 : active raid1 sda1[0] sdb1[1]
289024 blocks [2/2] [UU]
unused devices: <none>
Also I am not sure about the "unknown partition table" messages in the dmesg output. I am not sure if they are somthing I should be concerned about or could be a contributing factor.
If you need more information about my problem just ask an I will post it.
Last edited by KrimReaper (2010-08-05 18:44:01)I have been doing some searching around and have found some new information.
https://raid.wiki.kernel.org/index.php/Performance
I found there were some fixes for the "apparent pauses in the stream of IO" that I believed I was experiencing as well. I had in the meantime changed my raid array to raid 5 to increase the read performance which had helped with my lag issue but it was still apparent. So I did two of the optimizations listed on the page. But before I did I ran a benchamark on my current raid 5 array.
Unoptimized Raid 5 array
Version 1.03e ------Sequential Output------ --Sequential Input- --Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
media 8G 43161 66 34106 4 19897 1 48765 65 156367 7 412.4 1
------Sequential Create------ --------Random Create--------
-Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP
16 +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++
media,8G,43161,66,34106,4,19897,1,48765,65,156367,7,412.4,1,16,+++++,+++,+++++,+++,+++++,+++,+++++,+++,+++++,+++,+++++,+++
Set read-ahead from 512 to 65536 on all md devices, seems to be a minor improvement
Version 1.03e ------Sequential Output------ --Sequential Input- --Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
media 8G 38289 58 36708 4 22971 2 70054 93 185402 5 407.9 1
------Sequential Create------ --------Random Create--------
-Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP
16 +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++
media,8G,38289,58,36708,4,22971,2,70054,93,185402,5,407.9,1,16,+++++,+++,+++++,+++,+++++,+++,+++++,+++,+++++,+++,+++++,+++
Set stripe-cache_size for RAID5 from 512 to 16384, massive improvement
Version 1.03e ------Sequential Output------ --Sequential Input- --Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
media 8G 65835 98 126321 11 48050 4 70850 95 184347 5 370.4 1
------Sequential Create------ --------Random Create--------
-Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP
16 +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++
media,8G,65835,98,126321,11,48050,4,70850,95,184347,5,370.4,1,16,+++++,+++,+++++,+++,+++++,+++,+++++,+++,+++++,+++,+++++,+++
After changing the stripe cache size it looks like there has been a massive improvement in output speeds. Though I have not used the desktop environment of the computer yet nor have I been watching movies/downloading or doing anything I/O heavy yet of this change. I think this may have been the root of my problem. When I have used the computer for a few more weeks I will report here again whether or not lag/pause problem has been solved. -
Will Graphics Card Help Aperture on Mac Pro?
I've been using Aperture for many years on a variety of Mac hardware. I have 5 or 6 image libraries, ranging in size from 50gb to 250gb. I have no referenced images, do not use "faces" or other CPU-intensive features, and often perform tasks which reportedly improve Aperture performance (deleting caches, repairing/rebuilding libraries, defragging hard drives. deleting prefs). While these tricks often result in a snappy experience on relaunch, Aperture returns to its sluggish ways after a few minutes of work.
My workflow is very simple -- I plug in my camera, download photos to the HD, and then edit them, which consists of adjustments such as exposure, white balance, sharpening, rotating, cropping. I don't do much retouching, red eye, or other fancy editing. Occasionally I use the "external" edit feature to retouch in Photoshop. I shot for many years with a Canon Rebel, 14MP I believe, and recently got a Nikon D800. I am finding the performance going through D800 raw files (not even editing, just flipping through them) unacceptable. For example, if I go to hybrid list/preview view, and press the "down" key 10 or 15 times, by the 5th image, there is a very noticeable lag, and often the display beachballs for 10 seconds or more before it gets to the bottom of the list. Basic tasks such as cropping or rotating often lock the display for long periods of time.
For many years, I blamed Aperture's awful performance on my hardware. I worked on a series of Mac laptops. Although I usually had the latest hardware, they were no desktop. Recently, I bought a Mac Pro with a 3.2GHz Quad-Core Xeon processor, 16GB of ram, an OWC SSD (for the system -- the libraries are on a 7200RPM drive), and a ATI Radeon HD 5770 graphics card. I was dismayed to find out that Aperture is STILL unbearably slow. If I can't simply flip through some photos on a top of the line Mac Pro, what is this program good for?
My question now is, would I see a significant performance gain if I were to upgrade yet again to a faster graphics card, such as the Radeon 7950? I've been reading up on these cards, and it seems like native support is coming in 10.8.3. While I hesitate to pour more money into my quest for a useable Aperture system, I wonder if this would finally show some significant performance gains. I've read conflicting reports from other users who've upgraded the graphics card. Is the advantage mainly for 3D or gaming applications or would this help Aperture too?
Thanks in advance for any replies!In the past Aperture has been very GPU-dependent. The very best G5 tower would bog on Aperture unless the stock GPU card had been upgraded. I expect current Aperture also to benefit from a stronger GPU but I do not have absolute info on that. And your existing 5770 is not a lame card.
I know 16 GB RAM seems like a lot, but with D800 files and an Aperture/Photoshop workflow you may still be paging out to disk. My Aperture/Photoshop workflow paged out at 8 GB RAM with files 1/3 the size of the D800 files.
You should evaluate whether or not you have adequate RAM:
Look at the Page Outs number under System Memory on the Activity Monitor app before starting a typical Aperture/Photoshop work session and write the number down. Recheck the Page Outs count after working for a few hours and write the number down again. If the page outs change (manual calculation of ending page outs number minus starting page outs number) is not zero your workflow is RAM-starved.
Ignore the pie charts and other info in Activity Monitor because they are often misleading regarding RAM usage. For RAM analysis, count page outs.
If your test shows that page outs increase at all during operation you should add RAM. RAM is dirt cheap and use of additional RAM a very desirable characteristic for an Aperture/Photoshop workflow. If it was me I would double to 32 GB RAM and set PS (PS Preferences/Performance/Memory) to use 16 GB of RAM.
Hard drives slow as they fill so make sure none of your hard drives are overfilled. I suggest 70% full as an arbitrary maximum but even less full is preferable for speed. If your Library drive exceeds 60% full I suggest setting a RAID 0 array on two or more identical drives to get extra capacity and speed. Of course pay careful attention to frequent Library backup.
Some apps like browsers are notorious for "leaking" memory so when doing serious images work keep non-essential applications closed. A SSD drive for boot helps because when apps open in just 3 seconds there is no reason to keep extraneous apps open.
HTH
-Allen
P.S. I strongly recommend that original images be fully backed up before importing into Aperture or any other images management application.
P.P.S. Makhe sure you have a properly set PS Scratch Disk assigned on a fast underfilled drive, and empty the scratch disk routinely. -
Aperture 2 and 3 and Snow Leopard
My system with Aperture 2 was perfect.
Then I believe that Snow Leopard killed Aperture 2.
When I first installed Snow Leopard my machine felt like new again but slowly and slowly over the last few months the whole system seems to feel less and less snappy.
I don't use many video-intensive applications - my main one is Aperture 2, so this is where I find my main cause for concern.
Painfully slow adjustments with lagging, beach-balling, CPU-hogging, and RAM theft.
The main culprits seem to be Highlights/Shadows, Straighten, Crop, and Retouching… although my open mind says that could simply be because they form the latter part of my tweaking process.
There seems to be a thumbnail generation issue. Every adjustment that is made generates a new thumbnail - as you work through your tweaks that process seems to get backed up and slow everything down.
There seems to also be a video issue. Tweaking horizontal photos in full screen causes twice as much lag as a vertical image. Why? Take a look - it's obvious - in full screen edit a vertical image is about half the size of a horizontal one.
There seems to be a memory issue. Aperture seems to use a large amount of processor and RAM and sometimes doesn't let go of it or it gets caught in some kind of a loop. I've no idea what I'm talking about here. All I know is when I look at Activity Monitor the numbers are going through the roof and I can barely concentrate on them because of the noise from my fans.
There have been various and quite diverse suggestions on this and other forums as to what the underlying problem is and I have done my best to look into those and see what can help.
I have an early-2008 MBP 4,1 - 2.6 Intel Core 2 Duo - 4GB (factory-fitted) RAM - GeForce 8600M (512MB) GT.
I have done everything possible: all software totally up-to-date, re-installed combo updates, rebuilt Aperture libraries, run consistency checks, fresh Aperture install, fresh Snow Leopard install, repaired permissions, booted in 32bit, booted in 64bit, run hardware tests, deleted plists, cleared caches, downloaded and run applications like Onyx and Snow Leopard Cache Cleaner (amongst others) to ensure everything is in ship-shape along with various test applications to gauge if components like my hard drive are dying.
I keep my system clean and tidy. I have now stripped out bloat. I even took out iPhoto in case its 'iLife' browser link to Aperture was an issue. I have 85GB free on a 200GB. All components are original as factory-fitted by Apple.
Everything that any seemingly intelligent person on any decent forum has suggested has been done - in particular I thank the many users here on the Apple forum for all their information sharing… I try to read them all.
From what I see on the forums, I am not alone.
Nothing has fixed this problem.
I (and no doubt many others) have fed this information back to Apple.
Aperture 2 and/or Snow Leopard has a problem that has not been fixed.
Aperture 3 got released and I trialled it and swiftly uninstalled it because the exact same problems are there - even with one single photo in it.
My concern is that Apple will not fix the cause of the problem which seems to lie outside of Aperture.
If Apple concentrate on making Aperture 3 work better inside a possibly shaky Snow Leopard then I will be very disappointed.
I'm not forking out for a new version of software just because Apple broke my current software. Don't get me wrong - I do actually WANT to buy Aperture 3 because it has functional improvements and advancements that I would love to be using providing it works properly - and for me (and it appears for 'quite a few' others as well) it just simply doesn't… and neither does Aperture 2 any more.
I am no technical expert (as you've probably noted already) but a MAJOR bug seems to lie in the relationship between Snow Leopard, graphics cards, and the way it handles memory - and so in turn graphically-intensive applications like Aperture are high-lighting these problems more than others.
I am sure there are people without these problems. Perhaps these problems relate to specific hardware configurations. My configuration is Apple standard. I really shouldn't have these problems.
Until Apple fix this major bug I cannot remotely consider Aperture 3.
Until Apple fix this major bug I could never buy Apple again.
Up until Snow Leopard you had a VERY happy camper. I had a perfect machine and I was shouting Mac from the rooftops to anyone that would listen.
And then it seems Snow Leopard broke my machine.
What a shame.
I really want to use Apple, I actually really like Snow Leopard, I really want to use Aperture, I really want to carry on telling people how wonderful the Apple Mac experience is (or was...) but Apple are currently making it very difficult for me to continue doing so.
Please fix Snow Leopard.
This will hopefully fix Aperture 2 and Aperture 3.
Unless anyone else has a fix?
Sincere apologies to all for banging on for so long !!Thanks for your input setwart.
When I make adjustments I do want Aperture to provide me with a new version so that I can see the original image and also that I have a version which I have already adjusted. I've previously tried changing that preference before with no improvement in performance unfortunately, but it's not really what I was referring to.
Versions, thumbnails and previews were very confusing terms to me for a while… actually, in some ways, they still are but my understanding is 'a little' better now.
That said, I probably used the wrong term.
What I meant was that every time you make an adjustment Aperture seems to produce a 'record' or 'snap-shot' of your image including that latest adjustment. In so doing you have an entire history of each adjustment you have made. In my head I picture this like a movie film-strip with each frame differing slightly. You increase your saturation by a single point? Another snap-shot. Fancy another single point on your saturation? Another snap-shot… and so on.
It is typical that I will make a bare minimum of 20 adjustments on each image, and that's before even thinking about straightening, cropping, and retouching… and then maybe I'll go back and tweak everything again !!
Somehow, my system is having difficulty in keeping up to speed with all of those snap-shots of individual adjustments. Certain adjustments will drastically slow things down more than others, and then I get to play with the beach-balls.
But - it used to handle these things just fine and that's what I'm trying to get back to.
Thanks again for getting involved. -
Is there a way to transfer video from Aperture 3 to FCP 7?
When i first recieved my SLR i transferred all my video to aperture 3, thinking it'd be easy to connect it to FCP 7...while it is, i realize the codec differences/it lagging when i try to edit the footage. it's frustrating! I've since realized that Logging and Transferring is the way to go, editing is a lot smoother that way.
Is there any way I can get those video from aperture (v3) to Final Cut Pro 7? I don't have the original files anymore so the ones in the Aperture Library is all i've got left!
please help!Not within iTunes, no. You'd need to use other software to do that (QT Pro, for example).
-
I just purchased Aperture and have 20,000 + photos in my iPhoto Library. I see that I can create a unified library between the two. I am wondering if I can import only certain events from iPhoto (like only 2014 events) into Aperture or do I have to merge the whole iPhoto library? Are there any benefits to bringing the whole iPhoto library over to Aperture (iPhoto is SO SLOW for me, I wonder if it is because I have so many photos). Or, any detriment to only bring a few events over?
And, if I don't merge the two libraries, I assume that means I cannot do it at a later date?
Help. My local Apple store has had very few Aperture workshops, and the next one is like 2 months away.Thank you so much for this information. Here are some responses/comments:
Disk space - it says 114.43 GB out of 499.25 GB free. I have no idea if that is enough.
iPhoto version is 9.5.1
Again, I am not sure how to know if I have 3rd party software...but I don't think I do. Is 3rd party software anything non-apple?
I will try rebuilding the library. if that doesn't help, maybe I need more memory...? That is what Apple suggested, but that, of course, means buying something else. I've already bought APERTURE, on their recommendation...
It wasn't, and they told me it was slow because I had too many photos for iPhoto to handle and that I should buy Aperture. Which I did.
What is your iPhoto version? Are you using the most recent version 9.5.1?
iPhoto can handle 20000 photos, no problem. Your computer can be slow for several reasons:
The most common problem for slowness - insufficient disk space. Don't let your free disk space drop below 20 GB of free space, better more. If the operating system does not have enough working space and the applications you are using, you will notice a very lagging behaviour.
Older or incompatible softweare can cripple your mac. Do you have any older third-party software installed, that might have installed incompatible kernel extensions?
Aperture might be slow or keep crashing, if you imported a corrupted image or incompatible video, that cannot be processed. Then Aperture will try over and over again to create previews and never succeed. You could test for this situation, by launching Aperture with the Shift-key held down. This will defer the generation of previews. If Aperture will launch and work better this way, you probably have some bad media in your photo library.
Another problem to check for is a corruption of your Aperture/iPhoto library. You have run the First Aid Tools to repair the iPhoto Library, but have you ever tried to rebuild the library? See this post by Old Toad: Rebuild iPhoto Version 11
Maybe you are looking for
-
Hi CRM gurus, Can anyone advice where can setup the copy control for activities in the IMG. Since the system defaulted lots of transactions in the activity followup, we need to disable some of them from the list. Thanks in advance. Rgs. Michelle
-
Getting an error when working with Responsive Design Output: MasterThemeSchema.xml
When generating a Responsive Design HTML 5 output, I'm getting this error: "MasterThemeSchema.xml file has invalid data." I am unable to access the manage layout features now to continue my customizations. I had imported a customized font before s
-
Adobe Acrobat XI is compatible with MAC OS 10.9.4?
I want to know if Adobe ACrobat XI is compatible with MAC OS 10.9.4. Because I can't install the trial version. Can anyone tell me if there is a compatible and available version for my MAC? Thank you
-
Bluetoothctl successfully pairs with device but cannot connect
Hello, I'm trying to get my phone (nexus 4) to connect to my computer. I have bluez and bluez-utils installed. I've been able to successfully pair the device with my phone, but I can't connect to it. Here's some output from bluetoothctl: $ bluetoothc
-
Hangs on BIOS sign-on with buzz
First my stats: K8N - 3 memory sticks (2x 512Mb pc3200 + 256Mb pc2100) - Radeon 9600 - ATI HDTV - 3 HD - 1 DVD-RW. Recently installed new memory, but everything worked fine, except for a periodical blue screen at startup, which was no problem to me.